Related
hi.....everyone
i have a problem on my 8125....when i use the camera to take pictures .. after sometime the screen turns white and will not give it up for some time....does anyone knows why is this happening......do suggest some tricks and tips to solve this problem......thanks in advance
battery status...
Are you by any chance overclocking your wizard?
no....i have not over clocked....the clock speed is 185 mhz
For me, when I wake up my phone, sometimes the camera program randomly turns on. I don't know why.
this issues is happening all the time...when ever the phone goes into power saving mode...the camera screen turns white...i wont be able to take pictures....it will take couple of minutes to return to the original screen...or in some cases a soft reset is the only solution ...
i have same situation when phone rings - still cannot find out what is a reason - rom change is not working...
i am using bs, but machine is not overclocked.
HARDWARE?
If the problem exists with different operating system builds I would have to think it is a hardware issue. Unless of course on each build you implement the same third party application in which case the Software could be causing it....What type of software do you run? What is running in memory normally? This is what i would be looking at.
i am running XM6r5.... the memory is normal and i am able to many applications simultaneously....as soon as the screen turns while....when i hold it against a object for sometime....the screen gains some colorness and turns to normal...i didn't have this problem with the ROMs that i used earlier...i guess this requires some fix....
Despite setting the WiFi sleep policy to "never", HD2 becomes unpingable when the screen goes off, causing applications such as Fring/Skype/etc to lose connection. After turning the screen back on, the WiFi reconnects, and does it rather quickly, but having it off while the screen off meaning no incoming Fring/Skype calls possible on WiFi.
Any ideas ?
NOTE: i am currently using this build.
Same problem. Wi-Fi goes to sleep when screen goes off, even if Wi-Fi tethering is running. It's a reason of losing connection via Wi-Fi tethering. BUT! If at least one network service is active (ping, for example), Wi-Fi doesn't goes to sleep. I think that some of background services (Wi-Fi routing!) stops or becomes idle when screen goes off. It's a priority or policy bug, maybe... Not in a particular ROM, but in Android OS.
Using MDJ's CyanogenMod 7 NAND ROM (Android 2.3.2 Gingerbread).
or may be in power saving option check there .it looks like it saving your battery power.
shahnowaz said:
or may be in power saving option check there .it looks like it saving your battery power.
Click to expand...
Click to collapse
It is not power saving options because it also happens to my mdj 2.6 build with battery full. Power saving starts on 15% on my battery and also wifi and background data has been unchecked.
When this happens, no email updates, voip, and other app updates that needs data(because mobile data is intermittent in my area).
yeah, actually happens with all builds
I solved with this app, enabling all workarounds
http://www.appbrain.com/app/wi-fi-keep-alive/com.shantz.wifikeepalive
Enabling all workarounds would keep the device fully awake, this is not really a solution.
Tbh, this issue smells like a power management related bug in a wifi module/driver.
Also, if you google a bit, you can see it being talked about on nexus one, mentioning cyamogen roms as ones not having this issue.
Any idea what module/driver is responsible for wifi ? Is it a part of the kernel ? Or is it a module we may try replacing ?
rafpigna said:
yeah, actually happens with all builds
I solved with this app, enabling all workarounds
http://www.appbrain.com/app/wi-fi-keep-alive/com.shantz.wifikeepalive
Click to expand...
Click to collapse
Thanks much, just installed.
The offending driver seems come in a separate module, "bcm4329.ko". Here is a Nexus One thread mentioning the issue on one of the Nexus One stock builds, and actually presenting an updated module for that stock build.
Since HD2 uses the very same BCM4329 chip, it should be possible to compile the updated module for an HD2 kernel.
Any kernel guys up to the task ?
InfX said:
The offending driver seems come in a separate module, "bcm4329.ko". Here is a Nexus One thread mentioning the issue on one of the Nexus One stock builds, and actually presenting an updated module for that stock build.
Since HD2 uses the very same BCM4329 chip, it should be possible to compile the updated module for an HD2 kernel.
Any kernel guys up to the task ?
Click to expand...
Click to collapse
We need the commit used to do the change. I looked at the thread and found a commit but I dont think that is the right one.. Anyway I will try to see if can be included in my kernel asap and check if the situation improves.
rafpigna said:
We need the commit used to do the change. I looked at the thread and found a commit but I dont think that is the right one.. Anyway I will try to see if can be included in my kernel asap and check if the situation improves.
Click to expand...
Click to collapse
I checked, and the fix is already there... So at this point I think this is not our problem. I will try to address this to markinus or danijel that are far more experienced than me in kernel stuff
rafpigna said:
I checked, and the fix is already there... So at this point I think this is not our problem. I will try to address this to markinus or danijel that are far more experienced than me in kernel stuff
Click to expand...
Click to collapse
Maybe, just maybe, it's already fixed in your latest kernel, that uses the latest code base ? Note that i did NOT try & check it with every kernel available, i've only checked this with one that came with the build i am using (i think it was MDJ there, newer version uses yours, but i am not yet running it).
Anyone using latest rafpinga kernel, can you please test and respond ?
Update, rafpigna 1.7 installed, identical WiFi behaviour.
Looks like this is the solution for Desire:
http://forum.xda-developers.com/showthread.php?t=752856
Hopefully someone could adopt this to HD2.
Nice... Rafpigna, the diffs are at this post, can you apply and compile the patched "bcm4329.ko" for us to try ?
Sorry for being too dumb to do it myself, i just never ever happened to compile a linux kernel, not even once in my entire life
InfX said:
Nice... Rafpigna, the diffs are at this post, can you apply and compile the patched "bcm4329.ko" for us to try ?
Sorry for being too dumb to do it myself, i just never ever happened to compile a linux kernel, not even once in my entire life
Click to expand...
Click to collapse
It's not our problem
Note: This isn't related to the sleep mode wifi disconnections caused by MAC addresses that don't begin 00, so far as i'm aware that's been patched for a while now. Wifi remains connected fine in standby mode, but the throughput is only suitable for very light traffic.
Click to expand...
Click to collapse
I know its not our problem, but this may still be our solution. Our problem, seemingly, starts when the driver it going down into the deepest power saving state it can. It is supposed to sustain connectivity in it, though, but it seemingly doesn't. Avoiding this deepest state (PM_MAX) may solve the problem while having little to no side effects. Well, obviously, i do understand it's going to consume more power with WiFi on, but its better than being unable to keep it on at all.
Again, i know this is not exactly our problem, but again, this CAN be our solution anyway.
InfX said:
I know its not our problem, but this may still be our solution. Our problem, seemingly, starts when the driver it going down into the deepest power saving state it can. It is supposed to sustain connectivity in it, though, but it seemingly doesn't. Avoiding this deepest state (PM_MAX) may solve the problem while having little to no side effects. Well, obviously, i do understand it's going to consume more power with WiFi on, but its better than being unable to keep it on at all.
Again, i know this is not exactly our problem, but again, this CAN be our solution anyway.
Click to expand...
Click to collapse
I think it's definitely worth a try...
mishik said:
I think it's definitely worth a try...
Click to expand...
Click to collapse
Hello!
Unfortunately, I have tried this (to my detriment; I have code due tomorrow still!), and basically replaced the equivalent of this in the RAF 1.7 code (dhd_cdc.c and wl_iw.c have the PM_MAX vs PM_FAST thing).
My zImage came out almost a whole MB smaller (probably a toolchain thing), but the wifi problem while sleeping still exists, at least the symptoms that are linked in http://code.google.com/p/cyanogenmod/issues/detail?id=2403 with the similar fix of PM_MAX vs PM_FAST. That is to say, if I open the terminal and ping google.com, when the screen is off I get 300ms pings and when the screen is on I can get 3ms pings.
This happens whether I change PM_MAX or PM_FAST.
So this isn't the fix for what it's supposed to fix (or maybe I'm doing it wrong, toolchain's wrong, something), but I'll give it a few days to figure out whether my wifi drops more or less. Hopefully less.
(My symptoms are that, on campus, I have no problems with wifi, but sometimes if I leave the wifi zone and then come back, it'll report still having an IP lease and everything, but all pings and connectivity-type things such as web browsing will time-out. Not sure if this is what is being discussed here, but I thought it might help!)
Thanks,
Jeff
PS If you want the zip just to give it a spin, pm me or I might attach it here. That said, it might break everything! No obvious problems on my phone yet, though, so...
EDIT!: Of course, I invite anyone (especially rafpigna; perhaps you've tested this already?) to double check my work. It's possible I might've misplaced something!
I didn't do anything advanced; just pick up the CodeSourcery toolchain (free) for ARM (not GNU/Linux) and then install it on a Linux machine (it's possible with Windows, probably, but it'll be harder with the RAF build.sh). Then, make sure you have make and gcc packages on your Linux machine and then put your sources in the right directory and then try running the build.sh! rafpigna documents his work very well. Thanks rafpigna!
Did you remember to actually replace the .ko module, not just zimage ?
Hello,
Did you remember to actually replace the .ko module, not just zimage ?
Click to expand...
Click to collapse
Of course.
Hi,
i noticed months ago the following on my IDEOS X5 (german) concerning bad battery life. It could be the reason why there are so many different reports regarding bettery lifetime of the U8800.
First - why did I start to investigate: because the phone sucked about 5-10% per hour while not beeing used / lying on my desk, so after max 20 hours the battery was empty. But this did/does not always happen....
What I did: it took some time to get used to android (its my first droid) and learn how to troubleshoot. A month after I got this phone I learned that the GSM-code *#*#4636#*#* will show you very useful information concenring battery/phone usage. I started to play around with the phone (factory reset, install/remove apps, enable/disable different options like 2G/3G/WLAN etc...) always keeping an eye on the 4636-infos.
Result: When I use WLAN the phone simetimes enters an "state" when it never again enters "sleep state" and the battery gets sucked as stated above. I switched off WLAN for a week and this did not occur while standby time increased to 48 hours and 4636 stated an "phone awake" percentage of below 20% (normal usage). Once I reenabled WLAN again it took about an day of WLAN usage to reproduce the bug and "phone awake" time increased to 100% while standby time decreased to below 20 hours. ONLY rebooting the device recovers from this "state". I further noticed that this does not happen if just WLAN is available but no 2G/3G (phone had no SIM). My conclusion is, that the
"You May Be Charged"-Popup is the culprit. It does lock the phone to this "state" for some reason, mybe when the WLAN connection is dropped while the phone is not used (traveling). Can someone reproduce this on his phone (maybe not german)?
Resolution: IMHO none. I send the device twice to reseller for service. First time the complete mainboard was changed without success regarding the battery drain. Second time nothing was done - they just returned the device to me.
Thanks.
This is a known problem, that already has a thread...
http://forum.xda-developers.com/showthread.php?t=1043760
This is affecting ALL Froyo Roms, if you want battery life, install Oxygen or CM7...which are based on Gingerbread.
There is no point in discussing this issue anymore, this is a very well known problem and Huawei doesn't care.
Sending the phone back to manufacturer won't help at all.
Thank you for the hint - it realy looks like the same issue. Knowing more about the nature of this issue could give people not willing to install custom roms a possible solution. Can someone move this thread over to that one?
katu2006 said:
This is a known problem, that already has a thread...
http://forum.xda-developers.com/showthread.php?t=1043760
This is affecting ALL Froyo Roms, if you want battery life, install Oxygen or CM7...which are based on Gingerbread.
There is no point in discussing this issue anymore, this is a very well known problem and Huawei doesn't care.
Sending the phone back to manufacturer won't help at all.
Click to expand...
Click to collapse
But Huawei is about to release official 2.3 in Q3 atleast I hope...
andreasha said:
But Huawei is about to release official 2.3 in Q3 atleast I hope...
Click to expand...
Click to collapse
Everyone is looking forward to official 2.3, but we'll have to wait and see if the "sleep" bug will be sorted.
katu2006 said:
Everyone is looking forward to official 2.3, but we'll have to wait and see if the "sleep" bug will be sorted.
Click to expand...
Click to collapse
I hope some more bugs are straightened out like headphones and internal mic at the same time. Headset button to work. Battery time!
none of my android phones could use the phone's mic when headphones were plugged in
I saw a solution for the mic-with-headphones-problem a few days ago, either here or at modaco (do not know if it is confirmed working though).
fajabird, I know that you want this to work with the ROMs provided by Huawei. Huawei obviously does not care too much about providing the community with updates (they do not even have gingerbread-support by now). This is the downside of this low priced phone.
Let me just say this: It took me about one hour to understand the ultimate-guide at modaco. It took me another hour to decide which ROM I want to use. If anything goes wrong at the installation I can easily start over again. Now I have a fully working phone with Android 2.3.5 with a battery that lasts at least 2 days, sometimes 3(if I do not play any games within that time). Of course I understand that you are probably very pissed at Huawei for providing a ROM with a bug that serious.
if you find that fix again, let us know where to look
darkado said:
if you find that fix again, let us know where to look
Click to expand...
Click to collapse
It is to be found at the Android-development-section, right here. Note that you cannot use the mic of your headset after applying this
too bad, it would be awesome to be able to use both
XphX said:
I saw a solution for the mic-with-headphones-problem a few days ago, either here or at modaco (do not know if it is confirmed working though).
fajabird, I know that you want this to work with the ROMs provided by Huawei. Huawei obviously does not care too much about providing the community with updates (they do not even have gingerbread-support by now). This is the downside of this low priced phone.
Let me just say this: It took me about one hour to understand the ultimate-guide at modaco. It took me another hour to decide which ROM I want to use. If anything goes wrong at the installation I can easily start over again. Now I have a fully working phone with Android 2.3.5 with a battery that lasts at least 2 days, sometimes 3(if I do not play any games within that time). Of course I understand that you are probably very pissed at Huawei for providing a ROM with a bug that serious.
Click to expand...
Click to collapse
Hi, thank you for sharing your experience with me. I always wanted to update to some custom roms but the time I started investigating this issue there was no stable one out there. On the other hand I thought there might be a dev interessted in more details regarding this issue helping him to sort out this nasty bug for whatever reason.
Can someone tell me, if his U8800 also has the ambient light sensor but like mine does: it won't reduce the brightness, just increase works. Thanks.
fajabird said:
Hi, thank you for sharing your experience with me. I always wanted to update to some custom roms but the time I started investigating this issue there was no stable one out there. On the other hand I thought there might be a dev interessted in more details regarding this issue helping him to sort out this nasty bug for whatever reason.
Can someone tell me, if his U8800 also has the ambient light sensor but like mine does: it won't reduce the brightness, just increase works. Thanks.
Click to expand...
Click to collapse
Mine reduces brightness but does it quite weird sometimes like adjusting several times without the light around me changing...
Mine always adjusts it way too low. If I am inside the brightness is always on minimum. I use the power-widget on the homescreen. I only change it at night, it is on max. for the whole day (the max. brightness is still kinda low, especially if it's sunny).
fajabird said:
Hi,
i noticed months ago the following on my IDEOS X5 (german) concerning bad battery life. It could be the reason why there are so many different reports regarding bettery lifetime of the U8800.
First - why did I start to investigate: because the phone sucked about 5-10% per hour while not beeing used / lying on my desk, so after max 20 hours the battery was empty. But this did/does not always happen....
What I did: it took some time to get used to android (its my first droid) and learn how to troubleshoot. A month after I got this phone I learned that the GSM-code *#*#4636#*#* will show you very useful information concenring battery/phone usage. I started to play around with the phone (factory reset, install/remove apps, enable/disable different options like 2G/3G/WLAN etc...) always keeping an eye on the 4636-infos.
Result: When I use WLAN the phone simetimes enters an "state" when it never again enters "sleep state" and the battery gets sucked as stated above. I switched off WLAN for a week and this did not occur while standby time increased to 48 hours and 4636 stated an "phone awake" percentage of below 20% (normal usage). Once I reenabled WLAN again it took about an day of WLAN usage to reproduce the bug and "phone awake" time increased to 100% while standby time decreased to below 20 hours. ONLY rebooting the device recovers from this "state". I further noticed that this does not happen if just WLAN is available but no 2G/3G (phone had no SIM). My conclusion is, that the
"You May Be Charged"-Popup is the culprit. It does lock the phone to this "state" for some reason, mybe when the WLAN connection is dropped while the phone is not used (traveling). Can someone reproduce this on his phone (maybe not german)?
Resolution: IMHO none. I send the device twice to reseller for service. First time the complete mainboard was changed without success regarding the battery drain. Second time nothing was done - they just returned the device to me.
Thanks.
Click to expand...
Click to collapse
Hey there friend, I've detailed much of this and been through a lot of troubleshooting. It did not appear to be the "You may be charged" popup as I disabled that whenever I changed ROMs. I never did get a solution for any of the Huawei ROMs, it just seemed like bad code as Dzo pointed out with the WiFi driver.
A very simple solution for me was installing one of the 2.3 ROMs, they are quite stable at the moment, especially Oxygen (although I use MIUI). You will find much better battery life with these.
Best of luck,
Ryan
My stock rom 2.2.1 Shows Android System 97% battery usage and battery drains 50% in 19minutes! With wi-fi, 3g, Bluetooth, everything is off and even i do not use it.
Flash latest official 2.2.2, wait for official 2.3, flash the custom 2.2.2 rom void or flash a custom 2.3 rom. I would recommend flashing the latest 138 or 162 to get the latest modem baseband or manually install the AMSS.bin.
Sent from my Ideos x5
andreasha said:
Flash latest official 2.2.2, wait for official 2.3, flash the custom 2.2.2 rom void or flash a custom 2.3 rom. I would recommend flashing the latest 138 or 162 to get the latest modem baseband or manually install the AMSS.bin.
Sent from my Ideos x5
Click to expand...
Click to collapse
I can't because phone do not use my external SD card somehow. In android i see files but in recovery-it does not use external sd.. I ask in forum why-but nobody answers
Backup ur data on it and format it. If that doesnt work ill send you a guide how i fixed mine, its just a partition error.
Sent from my Ideos x5
andreasha said:
Backup ur data on it and format it. If that doesnt work ill send you a guide how i fixed mine, its just a partition error.
Sent from my Ideos x5
Click to expand...
Click to collapse
I formated it via phone, then via PC - it works in powered on phone in android, but in recovery it doesn't it only sees sdcard as internal memory, if i try mount sd-ext shows error, can't mount.
Also i have problem if i use pc to copy some files to internal memory-phone switches storage mode OFF! and i can't copy files to internal 2GB memory..strange
Hello!
I bought Nexus 10 at nearly two weeks, and since the beginning i have noticed an issue i thought would be Software related. As the device is on idle, everything works pretty well. Watching movies, web surfing, etc. Doesn't matter if it's for 5mins or 5 hours. But when it goes to sleep mode (automatically or forced by me), it just turns off consequently. I would say 90% of the times. An then Nexus just turn back to life after a long power button press, like 10 secs or more.
First i read about some people who have problems caused by autosleep function related with some cases. When i remove my tablet from the Poetic case, it keeps going off.
Then i read about Location services. It's turned off too. Such as the wi-fi in sleep mode. Didn't solve either.
Any idea?
PS: I'm from Portugal and my English is not the best. Sorry about that.
nando_pt said:
Hello!
I bought Nexus 10 at nearly two weeks, and since the beginning i have noticed an issue i thought would be Software related. As the device is on idle, everything works pretty well. Watching movies, web surfing, etc. Doesn't matter if it's for 5mins or 5 hours. But when it goes to sleep mode (automatically or forced by me), it just turns off consequently. I would say 90% of the times. An then Nexus just turn back to life after a long power button press, like 10 secs or more.
First i read about some people who have problems caused by autosleep function related with some cases. When i remove my tablet from the Poetic case, it keeps going off.
Then i read about Location services. It's turned off too. Such as the wi-fi in sleep mode. Didn't solve either.
Any idea?
PS: I'm from Portugal and my English is not the best. Sorry about that.
Click to expand...
Click to collapse
You can view my profile for my posts I've been working on that problem for over month. Sorry this is short reply - pressed for time right now.
bigmatty said:
You can view my profile for my posts I've been working on that problem for over month. Sorry this is short reply - pressed for time right now.
Click to expand...
Click to collapse
Thanks for the response anyway.
Is that thread about freezing? My Nexus is not freezing.
Hello! Yes, that is one of the threads Im talking about. I found it to hard to find people who posted with as good of detail as you did, so I had to "latch on" to the biggest group that was vocal about their problems. But mine manifests itsself almost always as sleep of death, and NOT reboot - just like yours. Here are some links:
Google: https://groups.google.com/a/googleproductforums.com/d/msg/mobile/-/GFnACv1nC0MJ
On of the XDA: http://forum.xda-developers.com/showthread.php?t=1998496&page=39
As I say on the Google thread:
My thoughts on the error:
1) The most logical explanation I've heard yet is the memory leak that B has been posting about
2) I think this memory leak/problem can manifest its self as crash, reboot, or sleep of death
Right now I am trying Stock 4.2.2, rooted, using KTmanta kernal. This is the second day Im on a non-stock kernal, too early to post any useful info.
Good luck on this,
bm
---------- Post added at 02:09 PM ---------- Previous post was at 02:05 PM ----------
say, quick question since you are in same boat as me - does your device's serial # start with R32C or R32D?
My device is R32D.
I guess i will call the seller tomorrow and figure out if it's possible to return the tablet. At this point, it's completely unusable.
nando_pt said:
My device is R32D.
I guess i will call the seller tomorrow and figure out if it's possible to return the tablet. At this point, it's completely unusable.
Click to expand...
Click to collapse
I agree that the inability of this device to reliably stay powered on is a deal breaker, at least in a work scenario.
I actually bought mine "just for games", but have been really concerned about trying to resolve this issue to verify its not a hardware issue and I miss my warranty period. I cant honestly say I think its a harware issue, so I am really trying to find a ROM/Kernal/settings combo that resolves this.
I have a lot of faith in the dev community for ROMs and kernels, but I think its absolutely scandalous and horrible that I have to click past a warning that says 'may void your warranty' to install softare on my device to make it perform AS IT SHOULD HAVE direct from Google.
If not for all these issues I would have NEVER gone custom recovery, root, and new kernel. Im glad this has forced me to do so because Ive loved finally having a justification for "risking" my expensive device, but again that learning experience is NOT what Google is taking $500 payments for here https://play.google.com/store/devices/details?id=nexus_10_32gb so Google should be SHAMED!
Thanks for the info on your serial number, that actually relieves a concern of mine that somehow the 'newer' units werent having this problem. Mine's a C.
bm
just bought my nexus 10 yesterday. it also turning off when sleepmode. but when i update it to 4.2.2 its gone.
jamir5 said:
just bought my nexus 10 yesterday. it also turning off when sleepmode. but when i update it to 4.2.2 its gone.
Click to expand...
Click to collapse
I hope it stays that way for you. It will take a few more days with the device to know for sure. If the problem comes back it'd be worth noting here for troubleshooting. :good:
I called back the seller, and they will do the return. Really bad situation...
i left my n10 in my house and its idle with 41% on battery i just got home and open the device it consume only 1% without random reboots. hope itll stay this way ill root this and install crom maybe nextweek.
So - now I am 2.5 days into testing 4.2.2 OS with a different kernel. And so far, NO sleep of death! AND I've been using the tablet a lot more than my "minimal use" in my other tests! This of course is the ultimate test - I'm posting/talking about it on the internet so certainly if its going to blow up in my face, now would be the time. But as of right now - it looks like the alternate kernal is better for my device than Google's...
I am using the KTmanta kernel.
It is important to note that the issue described in this thread does NOT involve the device turning itself off. Rather the issue is that the device is unresponsive when in sleep mode. You can tell this is the case in a few ways, but two obvious ones are that the notification light continues to function and the device requires a 10-second power button reset (the procedure for forcibly rebooting the device).
Personally, I am on CM10.1 night lies with Ktmanta kernel and still experiencing this problem.
Bigmatty, can you tell me what governor, i/o scheduler and clock settings you are using? Thanks.
neatchee said:
It is important to note that the issue described in this thread does NOT involve the device turning itself off. Rather the issue is that the device is unresponsive when in sleep mode. You can tell this is the case in a few ways, but two obvious ones are that the notification light continues to function and the device requires a 10-second power button reset (the procedure for forcibly rebooting the device).
Personally, I am on CM10.1 night lies with Ktmanta kernel and still experiencing this problem.
Bigmatty, can you tell me what governor, i/o scheduler and clock settings you are using? Thanks.
Click to expand...
Click to collapse
Well, the majority of the complaint threads do not specifically or mainly focus on the device turning its self off, but this thread actually does.
My sleep- of- death problem on my old unit persisted on any scheduler/clock settings I tried, and I tried a lot w/ KTmanta. But it was RMA my device to get a new one that fixed my SoD.
Oh, and the LED flashing does not mean the unit is actually on, you can test that by plugging in a charger before attempting a long (power on) press = if you get instant battery charge indicator your unit was actually off.
bigmatty said:
Well, the majority of the complaint threads do not specifically or mainly focus on the device turning its self off, but this thread actually does.
My sleep- of- death problem on my old unit persisted on any scheduler/click settings I tried, and I tried a lot w/ KTmanta. But it was RMA my device to get a new one that fixed my SoD.
Click to expand...
Click to collapse
That's REALLY weird, because based on a number of findings by a number of people, it turns out that this issue is related to a bug in the GPU driver that is causing a massive memory leak. You can check by opening a Terminal Emulator and running the command "ps su" This will show the memory usage for the "surfaceflinger" application, which is where the memory leak manifests. Memory usage should never go above ~70mb for that application, but on the N10 it balloons up above ~300mb before the system locks up.
Apparently we're all waiting on Samsung to fix the problem :\
neatchee said:
That's REALLY weird, because based on a number of findings by a number of people, it turns out that this issue is related to a bug in the GPU driver that is causing a massive memory leak. You can check by opening a Terminal Emulator and running the command "ps su" This will show the memory usage for the "surfaceflinger" application, which is where the memory leak manifests. Memory usage should never go above ~70mb for that application, but on the N10 it balloons up above ~300mb before the system locks up.
Apparently we're all waiting on Samsung to fix the problem :\
Click to expand...
Click to collapse
After my two months of trouble shooting I feel strongly that there are two main issues: memory leak and "something to do with power". Likely a software/driver/OS problem on the memory leak like the majority says. BUT - not everyone has the power problems. I think the power problems are hardware related.
Only a couple other users have talked about experiencing the power problems...
If I was going to place a bet, I'd say based on your description of symptoms you too have the power problem. Ask the others in threads you are following if they have the LED thing, I'm guessing they don't.
Rxnelson on these forms does. He's seen it on two physical units. For me, it didn't appear on my second physical unit.
Good luck!!
"LED thing?" The LED thing is just the notification light continuing to flash even when surfaceflinger has locked the system. Don't really see how that's related to power in any way. The way that LED notification lights work is that the system sends an "on" signal to the LED control chip which then just runs the notification light pattern in a loop until it receives the "off" signal from the system. If you don't have any notifications prior to surfaceflinger going ballistic, or if you have the notification light disabled (many people do) you'd never notice this particular symptom.
Also please note the tip I shared about diagnosing if it's off or on via the charger I posted above, handy trick another user taught me.
---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------
neatchee said:
"LED thing?" The LED thing is just the notification light continuing to flash even when surfaceflinger has locked the system. Don't really see how that's related to power in any way. The way that LED notification lights work is that the system sends an "on" signal to the LED control chip which then just runs the notification light pattern in a loop until it receives the "off" signal from the system. If you don't have any notifications prior to surfaceflinger going ballistic, or if you have the notification light disabled (many people do) you'd never notice this particular symptom.
Click to expand...
Click to collapse
Not quite what it seems. If the unit was on, plugging in the charger would not instantly,w/out delay, display the powered off charging indicator.
Ahh, okay, bit of a miscommunication. I'm not referring the power-on notification light. I'm referring to the notification light flashing that occurs when you have a notification waiting (new email, new gTalk message, etc). The charging light is something different, and not what I was referencing
NOTE: This is a function of CyanogenMOD 10.1 that is not present in the stock ROM, I think, so that may be where the confusion lies. Sorry about that
neatchee said:
Ahh, okay, bit of a miscommunication. I'm not referring the power-on notification light. I'm referring to the notification light flashing that occurs when you have a notification waiting (new email, new gTalk message, etc). The charging light is something different, and not what I was referencing
NOTE: This is a function of CyanogenMOD 10.1 that is not present in the stock ROM, I think, so that may be where the confusion lies. Sorry about that
Click to expand...
Click to collapse
Yes dude, I understand. Just test what I am saying. When I saw my white gmail led flash, but then couldn't turn on I thought the exact same thing you typed. Then while discussing w/power users someone told me to try that. Next time it happened I tried it, was SHOCKED to see what happened, knew I had a problem (that was not just shell reboot.)
My tablet just started doing this as well. It's never done it before, it started about a week ago. What could be causing this? I just factory reset to see if it'll fix the problem. I'll report back in a few days to see if this fixes the issue.
Sent from my Nexus 10 using xda app-developers app
Currently running timurs rom but it crashes a lot. Are there other roms that allow fast charge, sleep/wake with power, on screen volume etc.
Any help greatly appreciated
adamsilver1987 said:
Currently running timurs rom but it crashes a lot. Are there other roms that allow fast charge, sleep/wake with power, on screen volume etc.
Any help greatly appreciated
Click to expand...
Click to collapse
I've been running Timur's ROM as well and I really want an alternative as well as I've been facing issues with the ROM, and it looks like Timur has discontinued development on the 2012 model.
From what I've seen so far though CM11 should support USB DACs so I'm keen to try that out.
Some notes:
Fast charge - that's a kernel setting so any custom kernel should allow that.
Sleep/Wake on power - After many months of usage, sleep or even firm sleep has been a hit or miss for me. When it works, it works really well but sometimes a some random app might cause a wakelock, draining the battery. Even otherwise, there are many other issues such as USB audio doesn't resume. Plus the battery tends to drains quicker + looses health because of being in a hot car.
So instead, what I'm planning to do, is to just completely shutdown/boot up a tablet on power. Some notes:
- Bootup time is fairly quick - about 30 seconds, upto a minute, which is acceptable for me. You can reduce the startup time even further by using apps like BootManager to prevent unnecessary apps from starting up. Perhaps we can slim down the ROM further by deleting unnecessary apks etc.
- Fresh start is always a better option - you don't want your tablet to crash while driving right? I've had to reboot many times before or during driving, and it annoys me to say the least.
- USB audio always works fine when booted (well, with Timur's ROM anyways, need to test with CM11/others)
- No battery drain due to device standby or wakelocks
- No overheating and loss of battery health
- For shutdown on power loss, we can use Tasker. Maybe make a script to first turn the screen off, and after say 10 minutes of idle turn off the device completely (this will give us a chance to resume quickly in case we stopped the car for some reason).
- For startup on power, we can use the fastboot oem command to make the device automatically power up
On-Screen Volume: From daily usage, this hasn't been very practical in reality. I mean if you're driving, you really shouldn't be looking at the screen and trying to aim at the tiny buttons. Instead, a better option would be to use gestures to control the volume. There are heaps of apps for this, eg: All In One Gestures, Tasker, Gesture Navigation, GMD GestureControl, etc. You could use a single-swipe down and swipe-up to increase the volume up/down. Swipe left/right to change tracks. Two finger swipes to switch between apps. Just use your imagniation.
Might seem like a lot of work initially, but IMHO it'll be worth it, at least to get a stable ROM which is updated regularly (not to mention, you get to use the newest GApps!).
My only concern is to get the DAC working on startup. Might have to look into Timur's startup scripts to see how he does it - maybe even port the FHD scripts over to 2012 if necessary.
do you have a link to any fast charge kernels ? all i can find is Timurs ?
thanks
adamsilver1987 said:
do you have a link to any fast charge kernels ? all i can find is Timurs ?
thanks
Click to expand...
Click to collapse
Kang-aroo kernel.
http://forum.xda-developers.com/showthread.php?t=2558717
Supports fastcharge, OTG, hotplug DAC, firm sleep, multiboot and more.
thanks. this may sounds stupid ( im new to this rooting thing etc ) i am running paranoidandroid ROM. seems to run smoothly. i have flashed/installed that kernel and nothing is different. no extra settings etc? am i doing something wrong ?
thanks again
adamsilver1987 said:
thanks. this may sounds stupid ( im new to this rooting thing etc ) i am running paranoidandroid ROM. seems to run smoothly. i have flashed/installed that kernel and nothing is different. no extra settings etc? am i doing something wrong ?
thanks again
Click to expand...
Click to collapse
Use a kernel tweaking app, like TricksterMod.
ok downloaded that and it means nothing to me im afraid. how would i turn on fast charge for example or OTG host mode, firm sleep etc ?
only thing i can find where i assume you can set things is the " SysCtrl Editor" but it jsut comes up with a huge list of stuff that i have no idea about.
i assume i need to find fast charge in sysctrl and change it from 0 to 1... but cant find anything under the search. not a clue what id be looking for
starting to think Timurs rom was simple compared to this. haha
thanks for the help
Use PowerEventManager:
http://forum.xda-developers.com/showthread.php?p=50265682#post50265682
i saw that, but yet again. dont know how to use it ? where do i place it on the tablet. it doesnt show up in recovery mode
You have to install it. Copy it to your device and then use a file manager to open and install it. It will create an icon in your drawer. When you open it, you'll have options to configure firm-sleep etc.
Done. Worked at first but now I've reverted to timurs rom. The tablet froze loads. Wouldnt open some apps at all and power on/off with ignition wasn't reliable. Sometimes it woke, sometimes it didnt. Will give it another go when i habe more time i think.
On a related note, I haven't had much luck with getting my DAC to work with other ROMs - even with Kang-aroo kernel. I'll have to try CM11 with _crue_'s USB audio patches and Netfluke's kernel this weekend and see how it goes.
Edit: No luck. Maybe because it's I'm on tilapia. Even with cm11, Netfluke's latest kernel, and _crue_'s updated audio patches for cm11, couldn't get it to work. And it's a Fiio E17, which I've had no issues with on Timur's ROM.
And no, I'm not going back to Timur's CM10 - it's old. I can't use any of the newer GApps on it, and the ROM is buggy.
I think I'll swap my tilapia with my 2013 deb and use that as a car device instead. It looks like Timur just updated his kernel to v1.0 which fixes a lot of bugs - at least it's being actively developed. As for my tilapia, I'll switch to a more stable/mainstream ROM like Omni and forget about USB audio for now.
Where did u get timurs updated kernel? Cant find a link
adamsilver1987 said:
Where did u get timurs updated kernel? Cant find a link
Click to expand...
Click to collapse
Oh, you'll have to donate for now, but it should be made public soon.
How much and where?
Thanks