Sunday, December 27, 2009

How to fix LG tumble dryer error "EHE" or "ELE"

My LG brand tumble drier, model TD-C70210E, suddenly gave me error "EHE" just seconds after start. And of course the warranty period was passed just with one week, how likely is that?!

After testing, and after some "EHE" errors I also began to got "ELE" error code. The manual and internet didn't give any DIY solution for these, just advice to call LG repair service engineer. I also tried the "leave the drier door open and leave it like that for about one hour" solution, but it didn't work.

But luckily I solved my "EHE" error with this amazingly simple trick, that I found out myself.

1. Start the drier normally
2. Before the "EHE" error appears, open the drier door!
3. Because the door was opened during program, "dE" error is shown
4. Close the door and press "start/pause" to continue
5. Program will continue normally; problem fixed!

Before calling repair service, you should first try and test this really simple trick. It may also work for you!

Check out Angry Birds soda cans

Friday, March 20, 2009

Installing signed Java midlet with Nokia Application Installer, midlet appears not to be signed


I had the following problem: my Java midlet was signed, but when using Nokia Application Installer (comes with Nokia PC Suite), it showed the midlet as coming from not trusted 3rd party.

The jad-file clearly showed me that it actually was signed, but the installer in the phone told me that it was not.

And as the midlet appeared not signed, it was constantly nagging about read/write/connection permissions. That was not acceptable.


I then sent the files, BOTH jad and jar, to the phone via bluetooth. When installing the midlet with jad sent over bluetooth, the installer recognized the certificates, and the application was installed nicely.

Then the reason to the problem hit me: the jad had different filename as the jar! The jad was named MyApplication.jad, and the midlet was named MySpecialApplication.jar.

It seems that the Nokia Application installer does not read jad-files, and then discover the mentioned jar-files, but actually it reads first the jar files, and then tries to find jads with the same filename.


A) Just rename the jad, to be able to install the midlet with Nokia Application Installer. Or even better, change your project settings in Eclipse (or in whatever IDE you are using), to produce correctly named files.


B) Stop using application installer, and start sending the jad and jar files to the phone via bluetooth yourself.