I am pretty sure this fix uses the light sensor, so when your in a dark or dimly lit area it will turn on. I actually think that is better then just always being on.
Upvote
0
Agreed. Mine does the same...not necessarily a bad thing?One thing I have noticed since applying the keyboard light fix. If my phone is locked, when I open the keyboard it unlocks. Don't believe was the behavior with 2.0.1.
Agreed, and honestly if they are dropping this update in less than a month anyway I can wait.I'm sticking with 0.0.1 for now, the brightness at near 100% will drain the battery so quickly, wifi tether isn't worth it to me either.
One thing I have noticed since applying the keyboard light fix. If my phone is locked, when I open the keyboard it unlocks. Don't believe was the behavior with 2.0.1.
I am pretty sure this fix uses the light sensor, so when your in a dark or dimly lit area it will turn on. I actually think that is better then just always being on.
you running version 03? I like the little tether app but dam I cant take the screen and near full brightness.
I reverted back for now. Brightness > wifi tether to me lol.
Agreed. Mine does the same...not necessarily a bad thing?
I've got a question for all with the 2.1 update. When in landscape with the keyboard open, is your app drawer all effed? It just isn't the right layout. Does not matter MUCH to me since I use it in portrait for the most part but still, anyone else notice this?
+Known Issues (ongoing) and their statuses
-Keyboard Backlight - still not responding all that well to keypress and stays on longer than it should. Working on these issues...
-menu drawer glitch - low priority
-Upgrade ROM delivery method to SirPsychoS new tarball method - Medium priority. Maybe next release.
-System crashes with live wallpapers running. - Current state: unstable but moderately functional. We need to fill in missing libs and or modify the ones in the current release. As I know little about this particular topic, I will leave it to it's developers who posted the fixes to tinker with it for now.
Agreed, and honestly if they are dropping this update in less than a month anyway I can wait.
I meant I'm using 2.1 V0.0.1, not 2.0.1. I haven't heard a single word about the January update being 2.1 besides other members here claiming it will be, with the Nexus One coming out about that time and having it I would imagine they will wait a month or 2 before letting other devices get it so to draw more people to buying the N1.
Also if you use 2.1 V0.0.1 you can set the brightness to whatever you want, it's only 0.0.3 that has the bug of not being able to change it.
I'm not sure enough people have really thanked you for the news, so thanks for posting this. It's been driving me crazy when it won't light up. I hated the keyboard at first but I've grown to like it and am pretty quick at it.No problem... glad I could help!
OFFICIAL NEWS - The problem with the keyboard lights has been fixed.
(If anyone else has an easier way, let me know. This is just how I did it.)
As always - Proceed at your own risk.
libhw.zip
Most people suggest taking steps to back up your phone, but lets face it... at this point in the game, anyone who would be doing this has probably got everything backed up with Nandroid anyway, so I am just going to skip it.
First, plug your phone into your PC and mount the SD card. Extract contents of the zip folder to the root of your SD card. (Not inside the folder... each file individually.) Unmount the card. (Make sure your phone is plugged in and in debug mode)
Open a command window, switch to adb shell
Here are the commands to type out as follows:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
busybox cp -R /sdcard/gralloc.default.so /system/lib/hw
busybox cp -R /sdcard/gralloc.omap3.so /system/lib/hw
busybox cp -R /sdcard/lights.sholes.so /system/lib/hw
busybox cp -R /sdcard/overlay.omap3.so /system/lib/hw
busybox cp -R /sdcard/sensors.sholes.so /system/lib/hw
cd /system/lib/hw
chmod 644 gralloc.default.so
chmod 644 gralloc.omap3.so
chmod 644 lights.sholes.so
chmod 644 overlay.omap3.so
chmod 644 sensors.sholes.so
sync
reboot
The ZIP was provided by Greek35T at Alldroid. All thanks go to him.
I'm not sure enough people have really thanked you for the news, so thanks for posting this. It's been driving me crazy when it won't light up. I hated the keyboard at first but I've grown to like it and am pretty quick at it.
I'm an insomniac and I work the graveyard shift, so I'm just about always in the dark, so the light up is pretty important. So, once again, thank you.
No problem... I love helping people.
I know exactly what you mean with the keyboard. I am a courier and I work nights as well. At first I thought I would still be fine, but I actually ended up going back to 2.0.1 for a while. Actually, I switched back and fourth about 3 times. The patch for the backlight on the keyboard was the tipping point that kept me at 2.1 this last time around. I'm VERY happy they finally got it solved, even if it is still a little buggy.
Unsure - You live in Boston specifically or just the area? I'm out west on Rt 2 in a little crap town called Athol (still get 3G with VZW though, 2.4mbps at that!).
jmccarthy14 - I think it is much faster all around, especially homescreens though. No browser lag at all for me either.
Unsure, did you do format: system? You need to do all 3 each time. I don't know why your getting so much lag and so many errors, I haven't seen anyone else with as many problems as you've had.
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.