Related
I just got my S II a few days ago and I flashed CM9. I've noticed the soft key back light is messed up and won't turn on after I get a notification, I read a post where someone suggested an app but that didn't work for me. Does anyone else have a suggestion? Is there a similar problem with other AOSP roms? Thanks
ponygon101 said:
I just got my S II a few days ago and I flashed CM9. I've noticed the soft key back light is messed up and won't turn on after I get a notification, I read a post where someone suggested an app but that didn't work for me. Does anyone else have a suggestion? Is there a similar problem with other AOSP roms? Thanks
Click to expand...
Click to collapse
I am running Cm9 stable and I haven't had any issues, make sure its enabled in settings/display and play around a bit with the settings. Otherwise I would recommend a reflash. That is all I can really think of.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Octane70 said:
I am running Cm9 stable and I haven't had any issues, make sure its enabled in settings/display and play around a bit with the settings. Otherwise I would recommend a reflash. That is all I can really think of.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Its actually pretty much a common issue. With both CM10 and CM9, i had only heard of it being perfect on AOKP ICS. I too had this, i ended up disabling BLN due to a wake lock drastically draining the battery. I miss the old static BLN cause that didnt use a wake lock. It just woke it once to allow them to come on then went back to deep sleep.
elesbb said:
Its actually pretty much a common issue. With both CM10 and CM9, i had only heard of it being perfect on AOKP ICS. I too had this, i ended up disabling BLN due to a wake lock drastically draining the battery. I miss the old static BLN cause that didnt use a wake lock. It just woke it once to allow them to come on then went back to deep sleep.
Click to expand...
Click to collapse
Well I installed AOKP ICS, and it works like a charm with the exception that it still doesn't really work with BLN but I didn't realty care much for that.
Ok so I've been using a few different versions of the CM10 ROM and I've noticed a new problem. On occasion, when I go to wake the device, it will not wake. The keys light up, but thats it, the screen doesn't come on. The only way to get it working again is to hold down the power button and wait till it restarts. It's happened twice so far, not too frequently but annoying none-the-less.
Is there something I can do to fix this?
screwregi said:
Ok so I've been using a few different versions of the CM10 ROM and I've noticed a new problem. On occasion, when I go to wake the device, it will not wake. The keys light up, but thats it, the screen doesn't come on. The only way to get it working again is to hold down the power button and wait till it restarts. It's happened twice so far, not too frequently but annoying none-the-less.
Is there something I can do to fix this?
Click to expand...
Click to collapse
I thought you said you noticed a new problem...
Sent from my LG-P930 using xda premium
lordcheeto03 said:
I thought you said you noticed a new problem...
Sent from my LG-P930 using xda premium
Click to expand...
Click to collapse
I meant new to me! Though I looked around like crazy, cant find anything on this problem so I figured it was unique to my device.
screwregi said:
I meant new to me! Though I looked around like crazy, cant find anything on this problem so I figured it was unique to my device.
Click to expand...
Click to collapse
Nah, I'm mostly just giving you a hard time The CM10 nightly thread has gotten to be a beast to look through; seriously though... that problem is pretty old, and like you said; the only way to get around it is to hold power or do a battery pull. Just wait until you have an alarm go off in the morning and you can't turn it off!
Try the 2013 nightly, it does not appear to have this issue
Nz
notzippy said:
Try the 2013 nightly, it does not appear to have this issue
Nz
Click to expand...
Click to collapse
Maybe not, but it probably has other issues instead!
I can confirm that these issues still exist in the NIGHTLY (1/20) version. Just had it happen. Doesn't appear to be quite as frequent, but definitely still happening. I think it MAY have something to do with notifications, not sure though. Seems to often happen when I get a notification, I'll go turn it on and it wont wake from sleep.
screwregi said:
I can confirm that these issues still exist in the NIGHTLY (1/20) version. Just had it happen. Doesn't appear to be quite as frequent, but definitely still happening. I think it MAY have something to do with notifications, not sure though. Seems to often happen when I get a notification, I'll go turn it on and it wont wake from sleep.
Click to expand...
Click to collapse
Just saying; but there's already a thread for discussing CM10...
I have tried searching for this problem but I must be using the wrong terms... so sorry in advance if I missed a post that addressed this issue.
My sprint S3 does this twitchy/glitching thing on every touchwhiz based jellybean rom (does not do it on TW ICS ROMS) I have tried. It basically makes it nearly impossible to do sliding animations, IE it can actually get stuck and start flashing halfway between screens, or when pulling down the top menu, however you can open new programs just fine if you are already on the right screen for them. Luckily it does not do this all the time, but when it happens it keeps doing for 10 minutes or so and its annoying as hell.
I figured this must be a rare issue even though it effects both my wifes phone and mine, since I have never read anything about it, however I just got a new replacement phone and it does the exact same thing, even on dead stock TW JB ROM.
Oddly enough I discovered last night that if I turn on my screen filter app it stops completely, but it starts right back up when I turn off screen filter..... any ideas how to fix this?
Try grabbing cache clear from the play store and set it to run every 12 hours. It helped my phone a good bit.
Sent from my SPH-L710 using xda premium
No one else ever has this issue?
joelespinoza said:
No one else ever has this issue?
Click to expand...
Click to collapse
I had it dude, but it was just on the CleanBean ROM, it was annoying as hell!
So I changed the ROM, Its weird that its happening on a Stock ROM, any suspicious app?
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
I works on the 2/26/13 Nightly of CM10.1. You wanna try and clean flash it? If it doesn't work then it's just a problem with your phone hardware instead of the software. Might be a buddy bluetooth adapter or such.
zxstyle07 said:
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
Click to expand...
Click to collapse
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yup, this helped for my JB-MR build 4!
no more having to reboot to enable bluetooth
wbexpress said:
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Click to expand...
Click to collapse
http:// http://forum.xda-developers.com/showthread.php?t=2158329
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Well, what seems to happen is it is fine for 15-30 minutes after I've freshly installed the ROM, then it just turns off. When I then try to turn it back on it hangs at "turning on" and then goes back to off. At that point when I click "turn on", it doesn't even move. I'm a gonna try the fix, nothing to lose at this point...
Nuts. It fast moves to on and immediately goes back to off. White flag, thanks to all.
Apply the fix and delete all you devices then try turning it on and off with nothing on it...if it works then add devices one by one...if you have devices married to it the patch might not work also I think my computer dongle was the culprit
Sent from my SAMSUNG-SGH-T989 using xda premium
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
wbexpress said:
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
Click to expand...
Click to collapse
Your exactly right...
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
wbexpress said:
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
Click to expand...
Click to collapse
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
bluetooth issues
djtheraven said:
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Not a perfect answer...
RandyToe said:
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Click to expand...
Click to collapse
I found one thing that at least gets it working again without rebooting is to activate airplane mode. Its faster than rebooting. Wish I had a better answer...
Anyone else getting many touches for one touch? For instance if I type "STUPID", I may end up with "STUUUPIIDDD". It's not quite that excessive, but wanted to get the point across. One touch results in multiple letters/clicks every now and then.
Think this is a hardware issue, or something they may be able to tweak with an update?
How 'bout you?
Yea. Not bothersome though.
Sent from my Nexus 7 using xda app-developers app
Crooke356 said:
Yea. Not bothersome though.
Click to expand...
Click to collapse
Oh, it's hella-bothersome. Could be worse if it did it more, but it's still far too much for a "flagship" device.
i bet it's a 4.3 issue or something they overlooked..i remember when there were touch issues back on 4.1 i think ti was...remember on the Gnex, when after you'd touch recent apps, touch sensitivty would drop like crazy and you'd have to shut the screen off and turn it back on?
probably something stupid like that lol
jayochs said:
i bet it's a 4.3 issue or something they overlooked...
probably something stupid like that lol
Click to expand...
Click to collapse
I think/hope you're right! :good:
I took the update bc I was having problems with touch problems with notifications, seems to have fixed it (I think)
IamPro said:
I took the update bc I was having problems with touch problems with notifications, seems to have fixed it (I think)
Click to expand...
Click to collapse
I'm all updated, still seeing it. Not a lot, but enough to be irritating.
I'm having this problem as well. Just got my nexus about 2 hours ago and trying to set it up I'm seeing that long presses are sometimes hard to perform and sometimes scrolling lists will perform a button click on items when I was in the middle of a swipe gesture. I'm also seeing the keyboard issue. I thought it might be a stock keyboard problem but switched it out to thumb keyboard and I'm having the same issue.
My device forced an update right after I turned it on. It connected to wifi and then rebooted, ran the update, then restarted and had to go through the wizard again. Got into the OS and it said there was another system update. Checked version and it was 4.3 but did the update again. Still 4.3 after update. Was strange.
This keyboard issue is annoying enough that I'm thinking about RMA already. The device is pretty amazing other than that
Haven't seen that yet, but I'm using the latest phone version of SwiftKey.
Edit: I'm on JSS15J
Sent from my Nexus 7 using Tapatalk 4 Beta
Haven't experienced this at all
Sent from my Nexus 7 using Tapatalk 4 Beta
I think its just that the screen is super sensitive. I am finding it very difficult to type without having these issues. However I am getting used to it, so my typing is getting better and faster.
I bet in a month or so once you fully "learn" the response of the tablet you won't have these issues anymore.
Sent from my Nexus 7 using xda premium
^^ Exactly. it'll take a bit of time to get used to it. Plus, "SSSTTTTUUUPPIIIIDDD" sounds nice... wonder if its the problem with STUPID only... or some other words too
I thought I was going crazy for a little bit. I'm getting the same thing on Swype.
Sent from my Nexus 7