Hey all
Having a few troubles with my gyroscope. Here's the story so far.
I first noticed the issue when seeing significant sensor usage by 'Android System' - see screenshot of GSam. I started digging what part of 'Android System' it could be. GSam Battery monitor confirmed that the Gyroscope is always on during any screen on activity - see screenshot. This never used to be the case, as a month or so back I never had any sensor time used in this app. So something is holding my sensor on. Using BBS, and conferring which packages are included in 'Android System', I can narrow it down to 'system', 'com.android.systemui', or 'surfaceflinger'. (I think.) - see screenshot. Note: during screen off times, the sensor is not active at all.
I've thoroughly googled/searched xda for correlations of these to the gyroscope. This is where I've come to a dead end. I can't find any info on what it actually is that's forcing my gyro sensor to stay on.
The sensor is on with the screen regardless of auto rotation, all 'flip to mute', 'flip to silence'...etc off. Also in chrome, the tilt to scroll is off. I'm stumped.
These links are links which I've read, but nothing seems to bite me with a solution:
http://forum.cyanogenmod.org/topic/38291-orientation-sensor-is-using-a-lot-of-cpu-time/
http://developer.android.com/guide/topics/sensors/sensors_motion.html
http://forum.xda-developers.com/showthread.php?t=1755180
Any bright ideas? All suggestions are appreciated.
(Note that in one of the screenshots, '....androsensor..' has nothing to do with the forcing of the sensor on. It was an app I was hoping to log the sensor use with. It was useless.)
Does it happen with stock (or a clean install of the rom & kernel you're using) ? Could be something unknown that's funky in your current install. Could be the sensor itself on the fritz if it does happen with both of those as well.
MistahBungle said:
Does it happen with stock (or a clean install of the rom & kernel you're using) ? Could be something unknown that's funky in your current install. Could be the sensor itself on the fritz if it does happen with both of those as well.
Click to expand...
Click to collapse
Mmm not too sure about stock. It's been a looooong time since I've been stock. Might have to try a clean install of Rootbox first though. I already flashed back one of my reliable nandroids which I always revert to if I have issues, so I'd kind of neglected that side of things and just assumed that my bullet-proof nandroid would fix it if that was the issue. I'll try a clean install of RB though. Just annoying coz there should be a way to figure out what's actually using the sensor, but I haven't found one.
Yep that's an unusual one, you would have thought you'd have nailed it given everything you've looked at (and you've been pretty thorough).
MistahBungle said:
Yep that's an unusual one, you would have thought you'd have nailed it given everything you've looked at (and you've been pretty thorough).
Click to expand...
Click to collapse
Thanks for the compliment, especially coming from you I'll have to re-flash tomorrow, I'm on 13% battery now... better charge a bit before flashing or I could face worse issues than a gyro stuck on will report back when I know more.
Hopper8 said:
will report back when I know more.
Click to expand...
Click to collapse
Ok, so I flashed a clean install of Rootbox 4.0 with dorimanx 9.16. (flashed gapps as well). Gyroscope was still stuck on with the screen on. As a last thing to try before full stock, I flashed the kernel that comes bundled with rootbox. Fixed!... But what about Dorimanx? I've used that kernel for about 3 months now. 9.16 I've used literally since it was released, with no dramas.
To make sure that it was the problem, I flashed back Dorimanx 9.16. Gyro on. Reflash Stock kernel: gyro off. Using the stock kernel isn't really an option. Dorimanx allows so much more tweaking plus bln etc
I'd post in the Dorimanx thread, but I imagine it won't be received too well. @MistahBungle any ideas?
Edit: And yes, I've tried searching both the Dorimanx dev and discussion threads for similar issues. No luck
UPDATE: So, with more screwing around with kernel wipe scripts, I managed to make the gyro turn off with both dori and stock rootbox kernels. All was going well until it turned back on a few hours later. I don't know why. Now I can't get it to turn off at all.
Before it turned on, I'd only been tapatalking. A while later I played a bit of hill climb racing (game), then checked GSam to see if the gyro was active, and it was. The game doesn't actually use the gyro, so this is a long shot... Is anyone able to check for me if this also makes their gyroscope turn on (check using GSam battery monitor as in OP screenshot). Much appreciated.
Since then I've uninstalled hill climb racing, wiped, reflashed dori, & stock kernel, but nothing has made it turn off.
Stumped again.
Sent from my GT-P7510 using Tapatalk 4 Beta
Got me stumped as well Hopper, narrowing it down to a Dorimanx-specific issue looked promising, but that's now obviously not the case.
I'd do that clean install of stock (take your pick re: ICS or JB, just stay away from 4.0.4) I was talking about yesterday.
MistahBungle said:
Got me stumped as well Hopper, narrowing it down to a Dorimanx-specific issue looked promising, but that's now obviously not the case.
I'd do that clean install of stock (take your pick re: ICS or JB, just stay away from 4.0.4) I was talking about yesterday.
Click to expand...
Click to collapse
Literally had just turned wifi on to download a stock firmware. I will attempt to flash with mobile Odin (first time) so I can everroot.... Can't have an unrooted phone might flash the 4.1.2 I was on before root. Again, I'll post updates as I know more
Sent from my GT-I9100 using Tapatalk 4 Beta
Great minds eh ? ;-D Yep I hear ya re: having a rooted phone. Let us know how you go; this is a really interesting problem & makes a nice change from the 'OMGZ ! I broke my phone because I couldn't be bothered learning or taking proper care !' threads we usually get on here
Tell you what, if you still find the problem persist on stock, I'll DL that game (or something similar that makes use of the gyro) & see if I can replicate it on my phone (running RB 3.9.1 & Dori 9.12; Yes, I know I'm a bit behind. I like stability ). I must admit I don't play games that make use of it on my phone, so I've never really noticed anything wrong like this before.
Yep well I'm kind of enjoying it too. Now I have an excuse to buy & use mobile Odin alright, thanks! You've got yourself a deal. I won't get a chance till tomorrow, but I'll post my findings!
Sent from my GT-I9100 using Tapatalk 4 Beta
Hopper8 said:
I'll post my findings!
Click to expand...
Click to collapse
Ok, so the fun of Mobile Odin made me flash stock tonight. Aaaaand gyroscope is on still, but only when screen is on (see screenshot). This is with: stock LSH (4.1.2) firmware (rooted using Everroot in mobile odin during flash). Everything (I mean everything) is unchanged, apart from installing GSam to see if the gyro was being used.
The only conclusions I can think of:
- My hardware is faulty
- The gyroscope is always on, checking to see if I'm in landscape mode for videos (as in how the device doesn't need to be on auto rotate to watch a youtube video etc. in landscape). If this were the case, then wouldn't everyone's gyro's be on 100% of the time though?
Any enlightenment appreciated.
Edit: now I remember why I hate touchwiz :/
OK Hopper
Firstly, I hate you. I couldn't stop playing that goddamn game ! (I had to freeze it).
Secondly, I played it for 25-30 mins solid & no sign of gyro in GSam (I also have screen rotation, all the flip options in alarms turned off, etc).
So that doesn't seem to be the culprit.
I
MistahBungle said:
OK Hopper
Firstly, I hate you. I couldn't stop playing that goddamn game ! (I had to freeze it).
Secondly, I played it for 25-30 mins solid & no sign of gyro in GSam (I also have screen rotation, all the flip options in alarms turned off, etc).
So that doesn't seem to be the culprit.
Click to expand...
Click to collapse
Many many thanks for that and apologies for your addiction hmmm. Well I literally have no idea what to try now, I'm completely out of ideas.
Any bright ideas to try? Or a way of logging what is actually using the gyro? I couldn't find one.
Ps. Try to unlock the monster truck as soon as you can
Sent from my GT-I9100 using Tapatalk 4 Beta
Alright, so maybe time for a bit more drastic action... I'm thinking of disabling the gyroscope. I don't use tilt at all, so I have no need of it. Only problem being, I can't find a way to disable it. I've searched xda, as well as plain google. @MistahBungle, I don't suppose you've come across a way to do that in your vast experience?
Sent from my GT-I9100 using Tapatalk 4 Beta
Logcat during the period the gyro seems to be most in use might be helpful, but I'm no dev & not really au fait with deciphering them (Hopefully someone else who is might read this thread).
No. I can't say I've seen a problem like this or seen a way to disable the gyroscope. You'd need to talk to a dev I reckon. Given you've been using RB & Dori, maybe try the discussion threads for those, assuming the dev(s) read them & ask the specific question there, both about whether logcat would be useful & whether the sensor can be disabled by some kind of hack.
Sorry I haven't been able to help more I'm sure this is really frustrating for you & will be keeping an eye on the thread to see how this thing progresses & if you eventually find some kind of solution (Also happy to test anything else out at this end again that might help).
Well if that's the case, all I need to do is logcat for a minute while my screen is on. Guaranteed the gyro will be on! I will take some time & post in those threads. Thanks so much for your help! I will let you know if I manage to fix it, or if there's something else to test thanks again!
Sent from my GT-I9100 using Tapatalk 4 Beta
No worries, happy to help If you need me to try anything else let me know & keep us posted on how you go with it in this thread.
Update :
Since posting here, I posted in the dorimanx discussion thread, no replies (not that I really expected any). No progress with the problem, until yesterday.
I flashed NeatROM out of curiosity to see what it was like, with Apolo kernel. Gyroscope is off. I have no idea why, seeing as gyro was locked on with stock ROM. Now I'm even more confused... I would have thought it was possibly a problem which arose & is a result of flashing a 4.2.2 ROM, but @MistahBungle, you don't have this issue.
Apart from knowing that it is possible for my gyro to be off, it hasn't helped at all, unless I'm missing something....?
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
MistahBungle said:
No worries, happy to help If you need me to try anything else let me know & keep us posted on how you go with it in this thread.
Click to expand...
Click to collapse
AHA!! I think I might have a solution.... @MistahBungle, are you still ok to test something?
I managed to make the gyroscope go off by using hawkerpaul's ROMNuke script, and flashing stock. Then, I used the script again and flashed Rootbox, and the gyro stayed off. I flashed Dori 9.16, sensor was off. I set up Dorimanx in Stweaks how I usually do, and my gyro was on.
I started configuring Stweaks one setting at a time, checking with GSam battery monitor to see if the gyro was turned on. The gyro turned on when I configured the 'Screen' tab, specifically:
Set the 'min_bl_level' to 100 and set my brightness to 'Auto'
I re-nuked my ROM, and did the same test, with exactly the same result. I have since found that setting brightness to 'Auto' will trigger the gyroscope. Note this is only on Dorimanx, it won't trigger on any other kernels. Although it won't trigger on another kernel, the gyro will sometimes seem to stay on, as if the trigger is 'carried over' from another kernel. I don't know when or why though.
Summary:Setting brightness to 'Auto' triggers the gyroscope on Dorimanx. MistahBungle, could you confirm this? If not, next step is to flash a heap of different Dorimanx's kernels and see if some don't trigger it.
I've just turned my phone on auto-brightness, running Dorimanx 9.12. I'll check GSam in a couple of hours to see if the gyro has been running for any length of time (and I won't do anything with the phone that actually requires the use of the gyro).
Related
Hello,
I recently rooted my phone first time and installed passion 10.6. I had a few questions and problems and was wondering if someone could help?
1. My battery only lasts for 3 hours and in the Battery settings page the chart shows that the Android system has taken up 50% of the battery. Drilling down into that I see that most of that is due to 'Keep Awake'.I see other users report 20 hours of life on this forum.
2. My GPS navigation does not work at all though the places application call mark my location in seconds.
3. The four touch buttons come on after any notification on the phone and stay lit. For example, if I get an e-mail they come on and stay lit.
4. The phone signal bars show an H next to it and not 3g like I used to see on the stock Samsung 2.2 OS.
Any solutions to this?
This is such a great OS and I wish someone could help solve these issues.
Number 3 & 4 are features, not issues, the gps is always hit it miss on any rom, works for some, not all. Places find your location based on the network, doesn't necessarily need the gps. With the battery your phones not going into deep sleep, not sure why, i used to have to reboot every time i charged to get my phone to sleep right.
Sent from my SGH-T959 using XDA App
Thanks. I guess. I'll just try out another ROM now that I'm hooked and try passion back in a few days.
There are many different takes throughout the thread to fix your GPS and deep sleep concern. GPS will work but not after your phone goes into deep sleep.
Download CPU SPY and review if your phone is entering 'deep sleep' at all. If not, read through some of the later pages in the thread to visit options.
Thanks for the comment. Ill research this and post a solution if I find one.
I have a question. This from is do smooth and works beautifully most of the time but I'm having trouble with the unresponsive lock screen. :/ anybody have any tip or tricks to work around this? Thanks!
Sent from my SGH-T959 using Tapatalk
This ROM is is in testing phase so the issues posted here are known and solutions will be addressed in the future, I hope. You guys should ask the question on the link related to this ROM.
I have this ROM too but I only use it 1 day a week just to play around but it is not stable enough for my need. I kept going back to CM7
Thanks. Is there an issues of a bugs page in this forum? It would be easy to search and provide feedback. We are all beta testers after all!
Camera issues on ICS Passion 10.6
Has anybody else had issues with the camera not connecting. I have tried installing camera zoom fx to see if that worked and it didnt and the other way I can fix the camera is to shut the phone off and do a battery pull. It works one time and then cuts out again. I tried cache clearing and running permission fix and nothing. Anybody have a clue how to fix this issue.
For the 4 capacative buttons staying lit up, you can disable it by unchecking "Pulse notification" in Settings>Display.
As for the "H", this means you're getting faster speeds.
For GPS, try this to see if it helps http://forum.xda-developers.com/showthread.php?t=1447925
idotdot said:
Hello,
I recently rooted my phone first time and installed passion 10.6. I had a few questions and problems and was wondering if someone could help?
1. My battery only lasts for 3 hours and in the Battery settings page the chart shows that the Android system has taken up 50% of the battery. Drilling down into that I see that most of that is due to 'Keep Awake'.I see other users report 20 hours of life on this forum.
2. My GPS navigation does not work at all though the places application call mark my location in seconds.
3. The four touch buttons come on after any notification on the phone and stay lit. For example, if I get an e-mail they come on and stay lit.
4. The phone signal bars show an H next to it and not 3g like I used to see on the stock Samsung 2.2 OS.
Any solutions to this?
This is such a great OS and I wish someone could help solve these issues.
Click to expand...
Click to collapse
Thanks a lot. I'll try this. Right now I'm back to bionix
idotdot said:
Thanks a lot. I'll try this. Right now I'm back to bionix
Click to expand...
Click to collapse
Try going back to ICS Passion. v11 improves on the already great battery life, adds a little more speed, and other useful fixes, such as camera zoom.
Dmkjr said:
There are many different takes throughout the thread to fix your GPS and deep sleep concern. GPS will work but not after your phone goes into deep sleep.
Download CPU SPY and review if your phone is entering 'deep sleep' at all. If not, read through some of the later pages in the thread to visit options.
Click to expand...
Click to collapse
I've read through the ROM threads a bunch and OP's issue may be different than the main thread issue regarding Deep Sleep and Maps. I believe my issue the same as OP's.
When I boot up the phone and let it sit, it will go to Deep Sleep. As soon as I really USE the phone though (Maps, internet, etc) the phone will not go BACK into Deep Sleep, and battery drains rapidly. It takes a reboot to get the Deep Sleep working again. Android System is always the culprit. I have had the same problem on three different ROMs recently (ICS Passion, MIUI NB and MIUI Lithium Volt). It sure makes me think it's not the ROM...but I have no idea what else it would be since I wipe and reformat my phone before flashing.
I have been trying to figure this issue out for a while now, to no avail. Help would be greatly appreciated.
I wanted to see if I can post something without getting ridiculed. Seriously doubt that now cause I accidentally posted this in the general Q&A first and did not know how to move it or delete it so i am posing again here. Hopefully a moderator can just take care of that stray posting I made in the general area.
I am on my second ATT SGS2. First one had a GPS issue. Tried everything and finally convinced ATT warranty services that the problem was hardware. They said they would advance replace the handset. So I got it back to stock in every way except the flash counter,this was in December so long before I was aware of mobile odin. Flash counter was at about 12 when I was done trying different ROMs,mostly just try to get the GPS to work. It was in perfect shape, bone stock except for the counter. I cannot imagine I will have an issue, but has anyone ever heard of someone getting charged on a return to stock phone that had a flash counter above stock? Ill update once I know for sure the outcome.
My real question, does everyones SGH-I777 crash on occasion? If so how often? I so happy with the current code that is running on the phone with the exception that it sometimes sleeps and wont wake up, and sometimes it just plain crashes hard, locks up and has to be hard rebooted. Usually this happens about twice a day one or the other. I wiped before installing current kernel. The only reason I am not stock is cause I wanted the CKK6, 2.3.6 update to work and to keep root privaledges, but also needed my wifi cause ATT is throttling me down to dial up speeds when I reach 2GB. So wrong!!! Anyway thats another thread.
I loaded shostock with siyah kernel 2.6.35.14. after wiping everything including both caches. The GPS is solid now, phone is fast, battery is egh, I keep a charger with me... but it crashes hard from one to three times a day. Locks up playing tunes, or wont wake up with out being plugged in or hard booted. Do I have another defective handset or should I just go back to 2.3.4 and UKH7 or should I just deal with it and consider the crashes, "excellent opportunities to reboot."?
Thanks for the all the hours of fun, u know who you are.
I honestly don't remember my phone crashing at all. If it's crashing, it aint stable. Did it crash when it was stock?
yeah I mean duh right? The new handset was updated, rooted, downreved and flashed with the custom rom before it was put under any load, so I do not know if it would have crashed before. I have wiped, re downloaded, checked with hashtab and re flashed my current kernel, so it seems like it has to be hardware, again... ugh. Especially since no one else is having issues with shostock and siyah. I wonder how hard it is going to be to get warranty services to replace the second phone in 3weeks!? Lol.
Try going back to stock and run it for a couple hours to see if it still crashes. If it still crashes then more than likely hardware issues.
Sent from my SAMSUNG-SGH-I777 using xda premium
If it's crashing on stock without SetCPU to set a screen-off profile, you have a hardware problem.
I haven't had a crash, freeze, or spontaneous reboot in ages - despite running kernels that a few others have reported stability problems with (and I have effectively halted my kernel until I can get to the bottom of those reports...)
Too often is when it happens regularly, period.
I'm running CyanogenMod 9 and have almost no crashes, despite it being experimental.
Sent from my GT-I9100 using XDA App
I reverted to stock last night shortly after posting this. Ran fine until re loaded SHOstock v1.9.2-UCKK6. It is not "crashing" but it will go to sleep and not want to wake up again. I can sometimes plug in the charger and that will wake it up but other times I have to hard reboot. So no more crashing, but will not wake from sleep about 10% of the time. Not a huge deal, but its a bit weird because I know that the code I am running is ok, and it seems the hw is ok, so... not sure why this is happening. Anyway thanks all for your suggestions etc.
silashj said:
I reverted to stock last night shortly after posting this. Ran fine until re loaded SHOstock v1.9.2-UCKK6. It is not "crashing" but it will go to sleep and not want to wake up again. I can sometimes plug in the charger and that will wake it up but other times I have to hard reboot. So no more crashing, but will not wake from sleep about 10% of the time. Not a huge deal, but its a bit weird because I know that the code I am running is ok, and it seems the hw is ok, so... not sure why this is happening. Anyway thanks all for your suggestions etc.
Click to expand...
Click to collapse
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
I had the same problem using the latest siyah kernel, but never with entropy's. I would suggest flashing a new kernel.
Sent from my GT-I9100 using Tapatalk
1. To answer the OP question, I have experienced ONCE that was when I tried to run the Andy's TI-83 emulator on my virgin stock ROM. The result is either my fault or the application isn't compatible with the running OS.
2. With bone stock, it shouldn't crash at all. If it does, RMA.
3. If the owner(s) have "some fun" around it such rip it off, hack it up, install different kernels, different ROMs, ...... then please DO NOT complain the device is suck.
I've seen a lot of knuckleheads who tried to mod their devices, screw them up then claim "they're suck".
dandrumheller said:
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
Click to expand...
Click to collapse
Thanks this sounds like a plan. I have to do something things have gotten worse. About 3 out of ten times I go to put the phone to sleep now, instead of blinking out the phone takes a screen shot. My fingers are no where near any of the other buttons and it takes a screen shot over and over when I press the power button. I have to move around from screen to screen, hit the home button and then hit the power button to put it to sleep. Weird stuff, could be worse though. Did I say that I thought the phone sucks? I thought I read in one of the replies up there something like that. Aside from the GPS issue that was hardware related, and problems I have brought on myself because stock wasnt good enough, this is hands down the most awesome piece of electronics I have ever owned. iPhone smyphone. I just need to find the perfect turbo charged, rooted but as stock as possible configuration that is stable and I will be set. I really like where I am, hopefully the kernel you suggested does not change much but fixes the problems. Thanks again all.
Grab one of Entropy's DD Kernels and flash it with CWM. I'd suggest getting one from Jan or earlier. His latest ones are trying to track down a issue.
dandrumheller said:
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
Click to expand...
Click to collapse
axis01 said:
Grab one of Entropy's DD Kernels and flash it with CWM. I'd suggest getting one from Jan or earlier. His latest ones are trying to track down a issue.
Click to expand...
Click to collapse
Ok the noob is going to shine through here... but you say to flash with CWM. With my current config, when I enter recovery mode I am taken to the siyah kernel recovery console. Are we talking the same difference here, and when I go to flash as you mentioned can I do so with Siyah recovery or shall I flash with something that will give me back cwm first and then flash the config that you mentioned in your reply?
silashj said:
Ok the noob is going to shine through here... but you say to flash with CWM. With my current config, when I enter recovery mode I am taken to the siyah kernel recovery console. Are we talking the same difference here, and when I go to flash as you mentioned can I do so with Siyah recovery or shall I flash with something that will give me back cwm first and then flash the config that you mentioned in your reply?
Click to expand...
Click to collapse
That recovery will work. After installing the DD kernel, CWM will change.
Sent from my Galaxy SII
I get a crash here and there everyday...
Sent from my SGH-I777 using xda premium
Have only ever crashed while messing with voltages or clock speeds. if it's crashing something is wrong.
A few people's phones just do not play well with Siya kernal. Most of those people flash Entropy's DD and the sleep deaths go away... give it a try, I bet it will help!
Mine crashes a few times a day if I'm cycling through a lot of apps or installing things. (Stock+root) the other day my phone would crash anytime I tried, to watch a video in web browser. (Either mxplayer or phone)
Sent from my SAMSUNG-SGH-I777 using XDA App
T90 said:
A few people's phones just do not play well with Siya kernal. Most of those people flash Entropy's DD and the sleep deaths go away... give it a try, I bet it will help!
Click to expand...
Click to collapse
With Siyah I crashed more often than I do know with DD...
Sent from my SGH-I777 using xda premium
Ok flashed the DD from 01-30-2012
Thanks for all the help. I will post again when I know if things are better.
Hi guys, I'm running the latest version of Slim Bean with stock modem XXLE8 and whatever kernel comes with Slim. I've noticed that there is a 1.5-2 second delay upon hitting the power or home button to the screen turning on and being ready to use. It's pretty annoying as you can imagine, I've actually figured out what the problem is, my phone is going to deep sleep too early and is taking up to 2 seconds to wake up, I wouldn't mind this if the phone has been left alone for 2 hours or so, but if I leave my phone for 5 minutes I shouldn't have to wait 2 seconds to unlock it. I came to this conclusion by using the app softlocker from the market, which disables sleep, and the lockscreen is perfectly fine with no lag, so should I try a new modem or a new kernel or is there something else I have to try to solve this issue?
There are already some discussions about that problem:
http://forum.xda-developers.com/showthread.php?t=1687328
http://forum.xda-developers.com/showthread.php?t=1636680
It is a very annoying problem and I don't really understand how a top range device like the Galaxy S3 has such a problem.
I was hopping that the official Jelly Bean update would fix it... If it does not, I will contact Samsung (as should everyone who is annoyed by the wake up lag).
DeadVirus said:
There are already some discussions about that problem:
http://forum.xda-developers.com/showthread.php?t=1687328
http://forum.xda-developers.com/showthread.php?t=1636680
It is a very annoying problem and I don't really understand how a top range device like the Galaxy S3 has such a problem.
I was hopping that the official Jelly Bean update would fix it... If it does not, I will contact Samsung (as should everyone who is annoyed by the wake up lag).
Click to expand...
Click to collapse
I've read both but neither seem to provide much of a solution. It is pretty ridiculous a phone like the S3 with such powerful hardware suffers from unlock lag. My HTC Desire Z used to unlock instantly... Kinda disappointing.
I'm totally annoyed because of this problem, too.
isn't there a kernel or something where this doesnt happen??
No issues with Omega v34, instant
Sent from my GT-I9300 using xda premium
theslashy said:
I'm totally annoyed because of this problem, too.
isn't there a kernel or something where this doesnt happen??
Click to expand...
Click to collapse
I've been looking but can't seem to find one. The delay is about 1.5-2 seconds on Siyah, was about the same with YANK kernel.
jj92942000 said:
No issues with Omega v34, instant
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hmmmmm I might flash a stock rom and check it out because I don't remember it happening when I was running stock, tho that was for a grand total of 3 days lol.
This has always been a particular issue surrounding the Android software in terms of the optimisation of the OS...Keep in mind that kernels and ROMs with plently of adjustment may also mean plenty of variables, as small settings adjustments may alter and cause detrimental lags and issues as such. I use Phenomenal which is pretty good as there is little adjustments, disabled logs and undervolted...very good battery and response...I would recommend looking at something like that...unfortunately, should you wish not to root your device and keep it as standard, you may look at if there is an app that might be causing your the issue...but please note that slow unlocking/wake is because the device is in deep sleep.
0semaj0 said:
This has always been a particular issue surrounding the Android software in terms of the optimisation of the OS...Keep in mind that kernels and ROMs with plently of adjustment may also mean plenty of variables, as small settings adjustments may alter and cause detrimental lags and issues as such. I use Phenomenal which is pretty good as there is little adjustments, disabled logs and undervolted...very good battery and response...I would recommend looking at something like that...unfortunately, should you wish not to root your device and keep it as standard, you may look at if there is an app that might be causing your the issue...but please note that slow unlocking/wake is because the device is in deep sleep.
Click to expand...
Click to collapse
sure, but i own quite a view other android phones and none behaves like the s3, not even the superlow-budget htc one v
i installed the omega 4.2 AOKP rom today, but the lag is there, too....i got back to arhd for now...
theres a app called softlocker, but with that the cpu never gets to deepsleep, my s3 gets warm and the battery drains badly
When I got my SGS3, I could have it on for about 2 days (with minimal use and bluetooth and gps off and such), but ever since I updated to 4.1.2 (from ICS to JB), it looks like the battery drains a lot faster. So I got Titanium Backup and removed most of Samsung's' bloatware, disabled Google now and finally got BetterBatteryStats to pinpoint the source. I found some minor things and disabled them too... I've optimized all settings across the board, yet I still can't get much longer than one day.
Now I get that one day is nice, and most people charge every day, but when you're used to having 2 days (or at least 1.5 on normal use), 1 day is just.. less
So, I am kind of hoping that someone with more knowledge than me (basically everyone here ) would have a look at my BBS dump file, because I'm kind of at a loss.
It would be much appreciated!
Try turning off "Use wifi for location" in Location settings.
Arfman said:
Try turning off "Use wifi for location" in Location settings.
Click to expand...
Click to collapse
Do you mean "Location determined by wi-fi and/or mobile networks"? Isn't that used (among other things) to find the GPS sattelites way faster (because if it knows where you are, it knows where the sattelites are)? Because I use my phone for car navigation, I really would prefer not to wait 5 minutes while my phone searches the sky for GPS...
I'll turn the option off for now, but do you really think that's the main problem? Because I had the option on before this update.
Still, thank you for your suggestion
Location by wifi is unrelated to GPS location, it's just a way of roughly fixing your location by the networks and wifi around you.
It's a battery hog and doesn't matter AGPS, which is used to speed up GPS fixes but gets downloaded via your data connection.
I found JB to be better for battery life that ICS, even on a stock ROM. Since changing to a minimumcustom ROM based on the latest stock I get two days use with around 6hr screen on time.
If you are still on stock that was updated from ICS then you might be better off wiping the phone and flashing a fresh install, even if you only use the stock JB ROM for your country, as things might have become corrupted over time.
boomboomer said:
Location by wifi is unrelated to GPS location, it's just a way of roughly fixing your location by the networks and wifi around you.
It's a battery hog and doesn't matter AGPS, which is used to speed up GPS fixes but gets downloaded via your data connection.
I found JB to be better for battery life that ICS, even on a stock ROM. Since changing to a minimumcustom ROM based on the latest stock I get two days use with around 6hr screen on time.
If you are still on stock that was updated from ICS then you might be better off wiping the phone and flashing a fresh install, even if you only use the stock JB ROM for your country, as things might have become corrupted over time.
Click to expand...
Click to collapse
I turned it off, but in the past 4 hours it ate 20% battery, so didn't help anything. I guess I could go for a fresh install, but how would I do that? I'm assuming a factory reset won't do it... If you could point me to a guide or at least a location to get up to date stock roms, it would be much appreciated
Thanks!
DeltaBlast said:
I turned it off, but in the past 4 hours it ate 20% battery, so didn't help anything. I guess I could go for a fresh install, but how would I do that? I'm assuming a factory reset won't do it... If you could point me to a guide or at least a location to get up to date stock roms, it would be much appreciated
Thanks!
Click to expand...
Click to collapse
Would someone please point me in the right direction for up-to-date stock roms? Pretty please?
I think your issue is fast dormancy as you have the secril_fd wakelock.
There is an app on playstore that can toggle fast dormancy on or off on the Galaxy S3.
Give it a try and see if things improve.
Sent from my SGS3 using Tapatalk
ROM Sotmax Ultimate V14
Kernel Yank555.lu-V3.1c
corrsea said:
I think your issue is fast dormancy as you have the secril_fd wakelock.
There is an app on playstore that can toggle fast dormancy on or off on the Galaxy S3.
Give it a try and see if things improve.
Sent from my SGS3 using Tapatalk
ROM Sotmax Ultimate V14
Kernel Yank555.lu-V3.1c
Click to expand...
Click to collapse
Ok, I've installed it and turned FD off... I'll do a full charge now and see how long that keeps. Thanks for your suggestion! Is FD a new feature since JB? Because I haven't changed providers so if this has always been the case, it's probably still a seperate problem.
To be completely sure, I'd still like to do the complete reinstall, so I would really appreciate it if someone would point me in the direction of official updated stock roms. Thanks!
DeltaBlast said:
Ok, I've installed it and turned FD off... I'll do a full charge now and see how long that keeps. Thanks for your suggestion! Is FD a new feature since JB? Because I haven't changed providers so if this has always been the case, it's probably still a seperate problem.
To be completely sure, I'd still like to do the complete reinstall, so I would really appreciate it if someone would point me in the direction of official updated stock roms. Thanks!
Click to expand...
Click to collapse
You can reset it completely through Kies if you go to Tools>Firmware Upgrade and Installation and follow the instructions this will flash the latest firmware and reset your phone, do any backups you need first like contacts etc, then root the phone again or do whatever you want afterwards.
FD is not new. It just depends whether you provider supports it or not. If it is not supported and switched on it can cause battery drain.
Saying that my network does support it but when I first upgraded to XELLA I started getting the secril_fd wakelock. Switching off FD solved it at the time. Since then I have made a few changes, including modem and have switched it back on again without issue.
I noticed you've also got the Multipdp wakelock. A modem change sorted that one for me.
As I say I've since moved back to XELLA without issue and neither wakelock has returned.
Sent from my SGS3 using Tapatalk
ROM Sotmax Ultimate V14
Kernel Yank555.lu-V3.1g
I've found all the JB ROMs that I've tried to consume alot more battery than ICS, with the same set of apps running and the same location/sync settings. I eventually reverted to CheckROM 3.5 (ICS) to get decent battery life again.
corrsea said:
FD is not new. It just depends whether you provider supports it or not. If it is not supported and switched on it can cause battery drain.
Saying that my network does support it but when I first upgraded to XELLA I started getting the secril_fd wakelock. Switching off FD solved it at the time. Since then I have made a few changes, including modem and have switched it back on again without issue.
I noticed you've also got the Multipdp wakelock. A modem change sorted that one for me.
As I say I've since moved back to XELLA without issue and neither wakelock has returned.
Click to expand...
Click to collapse
Ok, thanks for the info. I don't think that's my problem though: my provider hasn't changed, the only thing that changed is that I upgraded to JB. Either way, I tested it: with FD off I still have pretty much the same result (maybe a bit better, but I need to properly test that. Yet it's definitely not the problem ). Too bad, it was a good suggestion.
ag4751 said:
You can reset it completely through Kies if you go to Tools>Firmware Upgrade and Installation and follow the instructions this will flash the latest firmware and reset your phone, do any backups you need first like contacts etc, then root the phone again or do whatever you want afterwards.
Click to expand...
Click to collapse
Thank you! I just did this. I expected that all my settings would be gone, but apparently that's not the case. All my apps remain, so I wonder if this wiped it properly? I did lose root though. Well, I'll charge it to 100% and we'll see what happens from there. Thanks!
Perhaps rolling back to your previous modem would help.
Sent from my SGS3 using Tapatalk
ROM Sotmax Ultimate V14
Kernel Yank555.lu-V3.1g
DeltaBlast said:
Ok, thanks for the info. I don't think that's my problem though: my provider hasn't changed, the only thing that changed is that I upgraded to JB. Either way, I tested it: with FD off I still have pretty much the same result (maybe a bit better, but I need to properly test that. Yet it's definitely not the problem ). Too bad, it was a good suggestion.
Thank you! I just did this. I expected that all my settings would be gone, but apparently that's not the case. All my apps remain, so I wonder if this wiped it properly? I did lose root though. Well, I'll charge it to 100% and we'll see what happens from there. Thanks!
Click to expand...
Click to collapse
overnight it lost 25% in 11h42m, so I'd say that's a definite improvement. It didn't see any use in this time, but it should last me at least 1.5 day now, so I guess the problem was in the update after all. The battery of my (6 months newer) SGS3 still holds out longer, but I think that's the battery itself: hers also charges faster than mine.
Thank you all, for helping to think up solutions and get it working for me again! :victory:
Edit: Multipdp is now a lot higer up in the list (it's the top partial wakelock), maybe I should change modems. Can someone tell me how?
You can download a flashable zip from here.
http://forum.xda-developers.com/showthread.php?t=2076857
[REF] Galaxy S3 RIL+Modem CWM Flashable Collection
just flash it from recovery.
XDLID is a good one to start with.
Sent from my SGS3 using Tapatalk
ROM Sotmax Ultimate V14
Kernel Yank555.lu-V3.1h
Running Sho3. Was running fine, then yesterday started noticing screen time out wasn't working (set to 30 seconds like always). The screen still dims like when your not touching it for a couple seconds, but then it stays like that. Tried reflashing, wiping etc. I pulled the battery and that worked, but then just noticed I got a text and it stayed on, checked the browser and same thing, won't time out (but still dims).
I'm stumped... and this is annoying as I gotta keep manually doing it which I don't since not used to that all these years lol, so battery keeps draining faster.
surf1 said:
Running Sho3. Was running fine, then yesterday started noticing screen time out wasn't working (set to 30 seconds like always). The screen still dims like when your not touching it for a couple seconds, but then it stays like that. Tried reflashing, wiping etc. I pulled the battery and that worked, but then just noticed I got a text and it stayed on, checked the browser and same thing, won't time out (but still dims).
I'm stumped... and this is annoying as I gotta keep manually doing it which I don't since not used to that all these years lol, so battery keeps draining faster.
Click to expand...
Click to collapse
Running Shostock3 as well and I am not having this problem..but i'm wondering....Do you have smart stay checked under settings/display? Maybe checked it accidently?
Sent from my SGH-I777 using xda premium
Yeh its unchecked, that was one of the first things I thought of lol
surf1 said:
Yeh its unchecked, that was one of the first things I thought of lol
Click to expand...
Click to collapse
Lol...I did it before that's why I asked. Have you changed kernels? I'm on Ajk 1.52s running good.
Sent from my SGH-I777 using xda premium
EQ2192012 said:
Lol...I did it before that's why I asked. Have you changed kernels? I'm on Ajk 1.52s running good.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
No same kernal that came with it, Jeboo v1.3b. I'm honestly stumped, pulling the battery was the only thing that worked but that was only temporary for like an hour or 2. Nothing shows out of wack in BBS
surf1 said:
No same kernal that came with it, Jeboo v1.3b. I'm honestly stumped, pulling the battery was the only thing that worked but that was only temporary for like an hour or 2. Nothing shows out of wack in BBS
Click to expand...
Click to collapse
Jeboo was running good for me to. Sooooo....uhhhh...er..um..you got me stumped to. Lol. Someone will come along that has a better idea. Good luck!
Sent from my SGH-I777 using xda premium
Tried a reflash with a new download, worked perfect yesterday. Then this morning it was still working, got a text, and now screen time out doesn't work again (doubt it's text related as a I got a ton yesterday and had no probs).
Flashed AJs kernel to see if there was a difference but screen time out still doesn't work. I've searched and searched on XDA and no clue what the issue could be, the only threads about this are the normal fixes that are common sense (uncheck something etc).
this sucks lol
surf1 said:
Tried a reflash with a new download, worked perfect yesterday. Then this morning it was still working, got a text, and now screen time out doesn't work again (doubt it's text related as a I got a ton yesterday and had no probs).
Flashed AJs kernel to see if there was a difference but screen time out still doesn't work. I've searched and searched on XDA and no clue what the issue could be, the only threads about this are the normal fixes that are common sense (uncheck something etc).
this sucks lol
Click to expand...
Click to collapse
This is not a rom issue. Best guess, from a distance of course, is that some installed app is at fault. Have you flashed back to stock to verify that the problem goes away? You would need to wipe and install stock without any additional apps to be sure.
If it works normally on stock, then go back and wipe data/factory reset and install Sho3 without reinstalling anything, and see if you have the problem. That will tell you if it's an app.
Also you can turn off the screen turn on when you get a text option in messaging. May help.
creepyncrawly said:
This is not a rom issue. Best guess, from a distance of course, is that some installed app is at fault. Have you flashed back to stock to verify that the problem goes away? You would need to wipe and install stock without any additional apps to be sure.
If it works normally on stock, then go back and wipe data/factory reset and install Sho3 without reinstalling anything, and see if you have the problem. That will tell you if it's an app.
Click to expand...
Click to collapse
Yeh I had tried that and it seemed fine (then again Sho3 runs fine and then out of nowhere like a day or two later the screen won't time out), but the odd thing is all the apps I have are the apps I normally use. Checking wakelocks etc, everything seems a-ok, nothing unusual. I've always ran Sho's roms. Haven't downloaded any new app's, only 1 in the last month (Scramble), had installed that to re-check but the issue still happened, don't run widgets either.
I've did find a few threads as well as searching online about people having similar problems and looks like nobody could figure this out as a fix was never given. Seems to be all JB users though reporting this, especially with GSIII where even turning off stay awake etc doesn't help, some said they just had to keep rebooting the phones or hard reset removing the battery but that's only temporary fix.
Phalanx7621 said:
Also you can turn off the screen turn on when you get a text option in messaging. May help.
Click to expand...
Click to collapse
OK wtf LOL... I always actually keep that off as it's useless to me. But I just checked and it was on, but I know I had it off with Jeboo, AJs must have turned it back on?
This looks to of fixed the problem, I don't know why since this is a text setting, but I could of been in the browser, email, game, music, even the lock screen and it would stay on.... no clue how that option in text affects everything???
I'll update if any changes but as of now turned it off and screen timed out when I opened the browser and left as is.
thanks!
Np man, glad you got it fixed