The one thing I've hated about DJ05, DL09, and now our Froyo releases is that the timeouts on the capacitive touchkey backlights have gotten longer and longer. In DI01 it was a couple of seconds, in DJ05 it was the length of your screen timeout, and by EB01 and beyond it's now the length of your screen timeout AND reset every time you touch *anything*.
Well, I've finally gotten around to figuring out where the change was (setScreenOffTimeoutsLocked() in PowerManagerService.smali in services.jar) and modding it back. Now, as in DI01, the keys will only light up for a few seconds after you press one. I haven't reverted the recent change of regular screen touches resetting this time after the touchkeys have gone on, though: since the baseline is very short, this isn't a big issue.
Note that the version of services.jar on which this is based is from Super Clean 2.9.2. However, a diff seems to show that the only difference between adrynalyne's services.jar and the stock EB01 is the inclusion, in the former, of the battery notification/data throttling removal mods. So it *should* work with any deodexed EB01-based framework, though I've only tested on the self-customized SC292 I'm running.
The mod does *not* interfere with BLN.
UPDATE 4/28: I've removed the previous EC01/ED01 versions because they were turning on the lights a bit too often (screen press as well as button press). Instead, here are two fixed Edify-script versions for ED01.
Evil Fascination/stock ED01 folks should use shortlight-evil341, which basically just includes the light fix and the sbrissen mods. Community ROM folks should use shortlight-community12, which has a couple of other options unique to that framework.
The new files include a permissions fix, so just install the zip and reboot. (Those installing the original file -- SC292/EB01 and Amend only -- still need to manually mount /data and /dbdata and run the fix permissions script in CWM 2.5 after installation.) First boot will take a while.
UPDATE 5/17: From version 3.5 forward, Evil Fascination folks should use the community zip as well. Evil341 is still good for stock ROM users.
UPDATE 6/13: New version (shortlight-cROM2) uploaded for Community ROM 2.0. Edify only, like the 4/28 version.
UPDATE 8/31: New version for Powerwashed (ED05). Edify only.
To be honest I like it when the keys are lit up. Especially in the dark and you're trying to hit one of those buttons. But I do agree that they shouldn't be on after you lock the screen....
Syn Ack said:
To be honest I like it when the keys are lit up. Especially in the dark and you're trying to hit one of those buttons. But I do agree that they shouldn't be on after you lock the screen....
Click to expand...
Click to collapse
Do your keys really stay lit up after you lock the screen? What rom are you using these days?
I'm running Adyn's latest superclean (2.92) and jt's ec10 kernel (TW_kernel-0327-2) and haven't seen this issue. I'm wondering if there is a bug somewhere that is causing this issue with other people.
I don't have a problem with their time staying on..I do wish they weren't so bright..
Has anyone noticed that the in-call "buzz" is related to the soft-key lights being on? I haven't used a Touchwiz ROM in a while (including Superclean), but this is something I've noticed running other ROMs.
This fix might help with that.
Awesome!! Thanks, I can't stand the long backlight time. This is perfect!
DeezNotes said:
Has anyone noticed that the in-call "buzz" is related to the soft-key lights being on?
Click to expand...
Click to collapse
Yep.
It's funny, a bunch of people like the long lights -- and it's their complaints, I think, that made Samsung edit the behavior in later firmwares. But I'm also sure there are a bunch of people who don't, so now there's a choice.
I also think if the lights were as muted as they are on, say, a Captivate, things might be different.
I tried this out. If I wake up my phone the lights stay off but as soon as I press one they never go off until the phone goes to sleep again.
Sent from my Fascinate
Superclean 2.9.1
EB16 voodoo kernel
EA28 radio
No current theme
s44 said:
I also think if the lights were as muted as they are on, say, a Captivate, things might be different.
Click to expand...
Click to collapse
Yea, the lights help locate the buttons in the dark, but they are so bright that they almost overpower the screen. As handy as they are, I'd rather do without them all together personally. But this is a great compromise.
scarfman4 said:
I tried this out. If I wake up my phone the lights stay off but as soon as I press one they never go off until the phone goes to sleep again.
Click to expand...
Click to collapse
You sure it flashed? This is basically the standard behavior.
s44 said:
You sure it flashed? This is basically the standard behavior.
Click to expand...
Click to collapse
I believe so. I booted into CWM, wiped data and cache twice, flashed it and rebooted.
Sent from my Fascinate
Superclean 2.9.1
EB16 voodoo kernel
EA28 radio
No current theme
Yikes, you wiped data!
Don't do that, this is a tiny framework change. (I think I'll add that to the OP.)
Not sure what could be off -- I assume the framework didn't change between 2.9.1 and 2.9.2. You used Red clockwork and not Orange, right? Maybe try reflashing...
(Since you're also in the SC thread, note that flashing any ROM will undo this change.)
Thanks! I have been looking for this!
Superclean 2.9.2
EC10 voodoo
s44 said:
Don't do that, this is a tiny framework change.
Click to expand...
Click to collapse
It worked perfectly for me, and I didn't wipe anything - data, cache or dalvic.
thank you very much s44, I've always wanted this!
This by far is the best mod yet. Not to dis the other great developers but I really hate that the backlights are brighter than my screen and always on.
Sent from my SCH-I500 using XDA App
s44 said:
Yikes, you wiped data!
Don't do that, this is a tiny framework change. (I think I'll add that to the OP.)
Not sure what could be off -- I assume the framework didn't change between 2.9.1 and 2.9.2. You used Red clockwork and not Orange, right? Maybe try reflashing...
(Since you're also in the SC thread, note that flashing any ROM will undo this change.)
Click to expand...
Click to collapse
My mistake, I didn't wipe data, only cache and dalvik (that's what I get for typing in a hurry).
I have Red clockwork, the latest from 3/30. I'll try again after my battery finishes charging.
Bizarrely, the lights seem to revert to "always on after touch" mode while the screen is in power-low super dim mode. Not sure if or how I can do anything about this.
s44 said:
Bizarrely, the lights seem to revert to "always on after touch" mode while the screen is in power-low super dim mode. Not sure if or how I can do anything about this.
Click to expand...
Click to collapse
I bet that was why it wasn't working for me. I was only at about 5% battery when I tried this.
Works perfectly for me.
Nice job.
Also just a heads up for any noob. My first reboot after took extra long but went fine. No problems.
Sent through mental telepathy
Related
http://adrynalyne.us/files/fascinate/gps.zip
Mirror: http://galaxysense.com/adrynalyne/gps.zip
Looking for some users to test GPS lock times with this.
Requirements: DI01 software and modem.
Credit: PhoenixPath
Make a backup in Clockwork first. This installs with clockwork!
I would love to test this but i don't know what "modem"
Means.
Sent from my stupidfast Fascinate
if you are running DI01, you will be fine.
If you don't know what modem is... at this point in time you are probably fine
It still took around 2 mins to latch.
Sent from my SCH-I500 using XDA App
Strange business. Multiple reboots and a battery pull and I am still getting instalock. Just the modifications listed in my sig plus the dj05 gpssetup.apk.
Sent from my stupidfast blackish hole...
slvrevoix said:
It still took around 2 mins to latch.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
about the same here
dj05 gpssetup.apk?
Holy $h!T! This is the real deal GPS fix! I can lock 3 sats indoors, in a basement - never locked indoors before with this phone. Furthermore, I can lock 7 sats just walking outside. Gets initial lock in like 10 seconds from a cold start. Did have to shut off my wifi for some reason before it would turn on GPS at all. And, once GPS is turned on, the toggle in the pulldown for GPS stops working, always shows it as being turned on. Have to enable/disable it thru the settings->Location menu.
But that's a small trade off for how well this works!
My baseband is dio1 so i am downloading now.
Sent from my stupidfast Fascinate
Worked for me. Installation was a little scary, got stuck on bootscreen but a battery pull later, it loaded up just fine. Locking onto GPS sats indoors and outdoors very fast. Rebooted a couple of times and it locked on again very well.
GPS icon in the notification bar acts a little weird when trying to turn it off/on, but if you must toggle it, the "Power Control" widget does the trick. I never turn mine off since it doesn't run unless you use an app that utilizes it.
Perfect! Thanks Adrynalyne!!!
Initially looking good! Got a lock fairly quickly indoors. Will restart and test it outside. Thanks!
Edit tested outside after a reboot and lock was instant! This is the best fix by far!
Edit 2: Tested while moving on the road. Lock was slower, but where before GPS Test showed 10 in view and maybe 0-1 in use, the number in use climbed steadily and lock was about 30 seconds
For those of you noting the inability to turn on/off gps through notifications, I believe that is an issue with the latest StupidFast kernel. I run a stock system and my friend runs SuperDark and we both had that issue, after I reverted to an older StupidFast kernel I got my notification GPS control back.
Yup this works! I got a lock within 10 seconds indoors. Thanks for this.
CrushD said:
For those of you noting the inability to turn on/off gps through notifications, I believe that is an issue with the latest StupidFast kernel. I run a stock system and my friend runs SuperDark and we both had that issue, after I reverted to an older StupidFast kernel I got my notification GPS control back.
Click to expand...
Click to collapse
Good call. That's what I was using! Thanks!
hey guys, I wanna try this out but 1 question-
Is this fix pulled from the DJ05 release, or is it a mod of the DI01? How does it work? thanks
aroy002 said:
hey guys, I wanna try this out but 1 question-
Is this fix pulled from the DJ05 release, or is it a mod of the DI01? How does it work? thanks
Click to expand...
Click to collapse
believe it is pulled from dj05 however i dont know for sure...do know that it works great on blackhole 1.3 with stupidfast kernel...got a lock in 10 seconds if that!
This is great thank you.
Tried maps and navigation and saw no improvement.
Hope this helps.
Sent from my stupidfast Fascinate
aroy002 said:
hey guys, I wanna try this out but 1 question-
Is this fix pulled from the DJ05 release, or is it a mod of the DI01? How does it work? thanks
Click to expand...
Click to collapse
It is the DJ05 gpssetup.apk, pulled directly from the /system/apps folder.
I've been running the new Trigger 2.9.2 ROM for a couple days now and it's got a few bugs I was wondering if someone could tell the ROM vendor about. (I'm new to XDA and I don't have 10 posts yet so I can't post directly on the thread.)
-The battery often displays the incorrect percentage remaining (if you reboot often on the ROM it will change as much as 30% either going up or down, and will sort of hang at that percentage until you reboot) (this happens in battery widgets, the "about settings" menu, and on the battery icon in the notification).
-There is no voicemail icon
Suggestion for update:
-BLN kernel mod?
P.S. I am NOT trolling here. Trigger is awesome and I am trying to get some advice about some serious problems I am having with the ROM... and yes I have tried wiping the cache/dalvik cache and fixing permissions and disabling and re-enabling voodoo.
Thread I'm talking about:
http://forum.xda-developers.com/showthread.php?t=921453
Thanks everyone!
You can flash one of the overstock kernels and have BLN.
Trigger 2.9.2
Did you by chance uninstall visual voicemail? Or freeze it thru titanium backup?
Trigger 2.9.2
30000 said:
I've been running the new Trigger 2.9.2 ROM for a couple days now and it's got a few bugs I was wondering if someone could tell the ROM vendor about. (I'm new to XDA and I don't have 10 posts yet so I can't post directly on the thread.)
-The battery often displays the incorrect percentage remaining (if you reboot often on the ROM it will change as much as 30% either going up or down, and will sort of hang at that percentage until you reboot) (this happens in battery widgets, the "about settings" menu, and on the battery icon in the notification).
-There is no voicemail icon
Suggestion for update:
-BLN kernel mod?
P.S. I am NOT trolling here. Trigger is awesome and I am trying to inform the vendor about some serious issues that don't really become evident to people until major problems occur... and yes I have tried wiping the cache/dalvik cache and fixing permissions and disabling and re-enabling voodoo.
Thread I'm talking about:
http://forum.xda-developers.com/showthread.php?t=921453
Thanks everyone!
Click to expand...
Click to collapse
It sounds like the 2 bugs you speak of aren't bugs otherwise they would affect everyone and many more people would be complaining.
The battery percentage is the reason why they give specific instructions on flashing with your battery at 100% as well as wiping battery stats at 100% and going through at least 3 full battery cycles. (Full charge then full discharge)
Voicemail icon is not showing probably because voicemail is not set correctly. Did you odin to JFD before you flashed?
If not it could have some strange hiccups like this because of it. Or if you want to try and fix it yourself go to Settings, Call Settings, Voicemail and make sure your settings are correct.
30000 said:
I've been running the new Trigger 2.9.2 ROM for a couple days now and it's got a few bugs I was wondering if someone could tell the ROM vendor about. (I'm new to XDA and I don't have 10 posts yet so I can't post directly on the thread.)
-The battery often displays the incorrect percentage remaining (if you reboot often on the ROM it will change as much as 30% either going up or down, and will sort of hang at that percentage until you reboot) (this happens in battery widgets, the "about settings" menu, and on the battery icon in the notification).
-There is no voicemail icon
Suggestion for update:
-BLN kernel mod?
P.S. I am NOT trolling here. Trigger is awesome and I am trying to inform the vendor about some serious issues that don't really become evident to people until major problems occur... and yes I have tried wiping the cache/dalvik cache and fixing permissions and disabling and re-enabling voodoo.
Thread I'm talking about:
http://forum.xda-developers.com/showthread.php?t=921453
Thanks everyone!
Click to expand...
Click to collapse
LOL if your trying to inform the Rom designer about Trigger 2.9.2, why are you posting your complaints here...
Post it under the Trigger 2.9.2 thread where he will be sure and see it... ????
Makes since to me.
30000 said:
I've been running the new Trigger 2.9.2 ROM for a couple days now and it's got a few bugs I was wondering if someone could tell the ROM vendor about. (I'm new to XDA and I don't have 10 posts yet so I can't post directly on the thread.)
-The battery often displays the incorrect percentage remaining (if you reboot often on the ROM it will change as much as 30% either going up or down, and will sort of hang at that percentage until you reboot) (this happens in battery widgets, the "about settings" menu, and on the battery icon in the notification).
-There is no voicemail icon
Suggestion for update:
-BLN kernel mod?
P.S. I am NOT trolling here. Trigger is awesome and I am trying to inform the vendor about some serious issues that don't really become evident to people until major problems occur... and yes I have tried wiping the cache/dalvik cache and fixing permissions and disabling and re-enabling voodoo.
Thread I'm talking about:
http://forum.xda-developers.com/showthread.php?t=921453
Thanks everyone!
Click to expand...
Click to collapse
I have a voicemail icon and no problems with my battery percentage. Maybe a bad flash? Try to reflash
30000 said:
-There is no voicemail icon
Click to expand...
Click to collapse
Freezing or uninstalling Visual Voicemail will cause this.
Thanks guys. I'm pretty sure I odined to stock JFD before I flashed. Also, do you guys know why alarm clocks wouldn't be working correctly? I just found that out. Additionally, the phone no longer has the battery charging icon that shows up on the screen when the phone is off and plugged in.
I would download the rom again, odin to jfd and reflash with the fresh download of 2.9.2
My market turned green today.
..in Trigger 2.9.1 with Overstock 2.2.1
b21bballer said:
..in Trigger 2.9.1 with Overstock 2.2.1
Click to expand...
Click to collapse
Get your new market in your favorite color here....http://forum.xda-developers.com/showthread.php?t=957331
I have this annoying bug in my Trigger 2.9.2. I think someone has the same issue as me in the forum but it seems not solved yet.
The bug is when you make call to USSD code. The notification sound volume will changed back to 30% (Default) no matter how many times you setup the notification volume level in the sound setting. However, SMS notification didn't affected at all.
Don't know whether this only happen to 2.2 ROM but I tested some 2.2.1 ROM it seems no sound came out & the volume level is the same as you set.
Anyone has this issue too?
My screen occasionally will not sleep. It does not even Dim.
I don't have any background apps installed like setcpu, oc etc.
Just straight apps. Calculator, weather bug (with backgroud updates turned off), etc.
It does not happen all the time. Just occassionally.
Sometimes even after a reboot it will just stay on and not sleep.
Some times just hitting the power button to force sleep fixes it. I wake it and then it goes to sleep fine.
I posted this problem in CleanROM thread and Scott (the CleanROM author) said he occasionally sees it to and does not know the cause.
I was curious if this occurred in other ROMs and if anyone might know the cause.
I'm running the Kernel that came with Clean ROM 2.9.5 by mwalt2 (with the DIM buttons and always on until cleared notification LED).
I also tried restoring CleanROM 2.5 and it did it too (I think it uses the same kernel).
Please use the Q&A Forum for questions Thanks
Moving to Q&A
mswlogo said:
My screen occasionally will not sleep. It does not even Dim.
I don't have any background apps installed like setcpu, oc etc.
Just straight apps. Calculator, weather bug (with backgroud updates turned off), etc.
It does not happen all the time. Just occassionally.
Sometimes even after a reboot it will just stay on and not sleep.
Some times just hitting the power button to force sleep fixes it. I wake it and then it goes to sleep fine.
I posted this problem in CleanROM thread and Scott (the CleanROM author) said he occasionally sees it to and does not know the cause.
I was curious if this occurred in other ROMs and if anyone might know the cause.
I'm running the Kernel that came with Clean ROM 2.9.5 by mwalt2 (with the DIM buttons and always on until cleared notification LED).
I also tried restoring CleanROM 2.5 and it did it too (I think it uses the same kernel).
Click to expand...
Click to collapse
Try reflashing the rom after doing a full wipe, and don't try to restore anything. I would also maybe try out a different kernel and see if that doesn't fix the issue.
#Winning# said:
Try reflashing the rom after doing a full wipe, and don't try to restore anything. I would also maybe try out a different kernel and see if that doesn't fix the issue.
Click to expand...
Click to collapse
I never restore anything after a wipe. Defeats the purpose of a "wipe"
I think it might be the Kernel.
People are to quick to say, I have no idea, so wipe it.
If I had to do that every time someone at work had a computer problem I'd be fired.
I'm running the CM9 beta 0.2.0 by jokersax11 ([Ics] cm9 beta with camera CDMA/GSM/UMTS/HSDPA/WCDMA/roaming 2/22/12) and my capacitive touch buttons at the bottom of the screen*(Menu, Home, Back and Search) are not lighting up at all! I can't figure it out at all and I really need these buttons to light up, due to my recent switch from the LG Optimus S, and before that I had an AT&T HTC Inspire 4g (which have the home and menu buttons reversed). I use my phone alot at night and I desperately need to get this fixed! Is there something in the CM9 settings I'm overlooking? Or is there an app or mod that I could use to get control of them and get them working again? PLEASE HELP! I WOULD REALLY APPRECIATE ANY ADVICE OR ANY INFO ON HOW TO GET THESE BUTTONS TO LIGHT UP AGAIN! This is really frustrating!
Click the link below for the answer ...
http://forum.xda-developers.com/showthread.php?t=1526546
EDIT - Well that was fun. If you haven't figured it out, the link above goes to the other thread you started, with the same title, and the same body, in the same forum .... You should not create duplicate threads. For future reference best practice is create 1 thread and wait a minimum of 24 hours between bumps.
With that out of the way my actual advice is as follows, i dont believe the capacitive buttons are an issue with jokers CM build although i dont personally use it. This would indicate the answer lies in a) something you did b) something you didnt do c) something you installed
1. You can eliminate a and b without losing any info by going into your custom recovery and wiping cache and dalvik cache then doing a dirty flash on the rom (dirty flash = don't wipe data/factory). In this case there would be no reason to reflash gapps.
2. If that doesn't work, do a full wipe (data factory/system/dalvik) and reflash the ROM, then gapps. Be slow to in stall your apps and test the capicitive buttons frequently to ensure you haven't done anything to break them
Set the phone's brightness to Automatic.. Fixed..
People are so over dramatic sometimes lol.
Sent from my MB855 using Tapatalk
Thanks, that pointed me in the right direction. My auto brightness isn't working. I'm gonna do a "dirty flash" and see if that helps. Oh and btw,the second post was an accident and you can't delete your own thread.So, sorry about that.
eszumlas1985 said:
Thanks, that pointed me in the right direction. My auto brightness isn't working. I'm gonna do a "dirty flash" and see if that helps. Oh and btw,the second post was an accident and you can't delete your own thread.So, sorry about that.
Click to expand...
Click to collapse
Please come back and update the thread on if it works or not. Others may experience the same issue in the future and this thread could assist them.
Cheers!
i just now notices mine dont light up but o well my thumb pretty much know ware to push
Well, it's fixed. Don't know what the heck was going on but reflashed my CM9 & Google apps and voila my automatic brightness switch in settings started working again. No more problems and capacitive buttons work fine. Strange but at least it's fixed
Sent from my MB855 using xda premium
And sorry to anyone that needed a fix to this. I was involved in the tornado that hit Branson, Missouri and was unable to keep phone charged due to the power outage that lasted over a week, and had bigger things to worry about at the time, like getting shelter and food. But everything is ok now and hope this thread helps anyone that has this problem. Check to see if your automtic brightness switch is working under settings (mine wasn't working) So if it isn't working just reboot into recovery, wipe dalvik cache & /cache, and reflash your rom and gapps, then check in your settings to see if your automatic brightness is now working. If so your problem should be fixed and your capcitive buttons should now light up. It worked for me, hopefully it will work for you.
Sent from my MB855 using xda premium
eszumlas1985 said:
Check to see if your automtic brightness switch is working under settings (mine wasn't working) So if it isn't working just reboot into recovery, wipe dalvik cache & /cache, and reflash your rom and gapps, then check in your settings to see if your automatic brightness is now working. If so your problem should be fixed and your capcitive buttons should now light up. It worked for me, hopefully it will work for you.
Click to expand...
Click to collapse
Thanks man i just had to set the screen brightness to automatic and reboot once. It worked like a charm
My BLN lights are always on w/out any notifications being present. IE: When the phone screen goes off, the touckey lights are permanently lit up. This goes away if I disable BLN. No notifications are present.
This wasn't the case when I first flashed.
Is this a common problem on this phone (flashed this phone for a friend).
That's strange, I haven't heard of that happening before. Might be helpful if you posted what rom/kernel/etc this issue is happening with.
TSM/KGB..
Strange indeed...
Sorry, my knowledge of touchwiz roms/kernels is pretty lacking. I thought there was maybe a KGB app that was made to accompany the kernel? No idea if it includes BLN controls, but that's about all I can think of.
Known behavior for TSM - BLN will turn off only once you pull down the notification bar. To change it so that BLN turns off when the screen is turned on, replace /system/framework/services.jar with the same file from the GeeWiz ROM. At least, that's how I fixed it.
sujaanj said:
Known behavior for TSM - BLN will turn off only once you pull down the notification bar. To change it so that BLN turns off when the screen is turned on, replace /system/framework/services.jar with the same file from the GeeWiz ROM. At least, that's how I fixed it.
Click to expand...
Click to collapse
adb in recovery and push services.jar from geewiz.. correct? (not going to be able to replace that while booted i assume)
Sputnikk23 said:
adb in recovery and push services.jar from geewiz.. correct? (not going to be able to replace that while booted i assume)
Click to expand...
Click to collapse
I used ES File Explorer to replace it while booted.
sujaanj said:
I used ES File Explorer to replace it while booted.
Click to expand...
Click to collapse
i see.. thank you. on a side note, said friend mentioned he has problems w/ swype and flash player not working? any chances those are common issues?
Edit: Skype, not swype. sorry