Related
Wizard G3,
ROM cooked by MFrazz, (WM6)
SPL/IPL DOWNgraded from 3.08 to 2.26 (not sure why or what this does?) GSM 2.47.11
I tried to install Launcher partially because I am a nerd who wants an iPhone screen for the shock value. I also installed the slider though I can't quite figure out where it has installed as it SEEMS to be in the folder (my folder) where Launcher is as opposed to in its own folder?? (which it should be if it is a stand-alone application?) In any event I don't use it as I cant get it (the most recent version) to stay on while Launcher is operating (and it doesn't seem to have been written with the Wizard landscape/portrait modes in mind) so I don't bother. Also the unit gets quite hot while launcher is on so I didn't want it to get any hotter!
In any event, looking in the log I see that Launcher.exe seems to have caused these curious access violations AND was giving the error message: CANNOT ALLOCATE VARIABLE LPARAM$, NOT ENOUGH MEMORY, (which I don't believe).
Is this some incompatibility with the ROM or something or does anyone know what is causing this please?
The only other problem with the unit is one which I have asked a few times (and a few people have reported) and no one knows the answer: The ear piece/speakerphone doesn't work on VoIP. I wouldn't imagine that is related to this error message.
Is there possibly a different ROM which would be more compatible with the software (and VoIP service) which doesn't incorporate things like the EDGE and Windows Today services which I don't use? I thought I was reasonably happy with this MFrazz one which seems OTHERWISE quite trouble free? Oh, and the battery heats up a bit and sometimes turns the screen white: On which eventuality you cant turn it on, - you have to plug in the USB cable again. (I turned the clock back to 195 from 221 to see if it did anything for this: If I cant get VoIP working just yet there doesn't seem to be any point in over-clocking it? And Mfrazz's ROM seems to work well at any clock speed! Except possibly for the codecs, if that is what it is )
I get nervous when I see access violations but this all occurred on July 7th.
Does it sound serious to anyone?
Hey all! Long time XDA-er, but I don't post much. Anyways...
Recently the WiFi on my Cingular 8525 has been quite problematic. I have gone through many custom ROM's recently searching for one that fits me, and I eventually settled on CRC's most recent build, TouchFlo2D running on top, and am very happy with the speed and usability of my phone. I always make a point of checking all hardware after a flash and at the time the WiFi worked fine. However, recently I noticed that when disabled, WiFi enables itself automatically every ten seconds for a short instant, then shuts off again. This change is reflected in the Comm Manager, the Taskbar, the WiFi configuration - everywhere. However if I turn WiFi on, it stays on, and works just fine. This has been causing me a lot of headache, mainly when using CPU-intensive applications, since every time it enables itself the CPU gets pegged, frames are dropped and virtual lives are lots. It also now takes FOREVER for 3G or HSDPA to connect, and I have noticed a slight decrease in battery life since I discovered the problem.
My device has the most recent HardSPL. I have tried flashing multiple radios, re-flashing the ROM, different ROM's, and every combination of settings I can think of. I searched everywhere I can think of, (posting is my last life-line) and I just can't find anyone else with this exact problem. I assure you there is no software trying to activate the WiFi and the phone is set up to use 3G for data by default. The registry is clean and there are no other problems, hardware or software-wise (aside from the touchscreen issue present on all Hermes). I am completely baffled, I can't find any logical reason for it to behave this way. I am considering a solution in an old thread by pof, an EEPROM trick where you acquire an image from one Hermes with working WiFi, hex edit the MAC address to be different, then flash to the affected device's EEPROM, however this is only reported to fix non-functioning WiFi, and I'm not convinced my EEPROM is corrupt, plus I can't seem to find the thread anymore. I am pulling my hair out over this! Even bouncing around ideas would help, all replies will be considered.
P.S. On a side note, I have been seeing a lot of threads lately calling the Hermes dead. I recently "downgraded" from a Touch Diamond to the Hermes, and I am extremely glad I did. Aside from the QVGA screen and lack of working GPS, I find the Hermes superior in most if not all ways, and I use my phone for just about everything. Long live the Hermes!
I'd like to know if anyone is having the same lag problems as I am getting from time to time..
The lag happens for no reason and comes at different times while doing different things.
I downloaded Watchtower from the Android Market to monitor what was happening. When the phone is running fast the /INIT process is showing as 0%..as soon as the lag starts to happen I check Watchtower again and the /INIT process is at anywhere from 70% to 100% CPU usage.
I dont use an app killer but I donwloaded one to try and see if it would correct the problem, it doesn't. The only way to solve the lag is to Restart the phone, then its fine for the rest of the day, sometimes two days but it always comes back.
I sold my SGS because of the lag issue and now it seems I have it with the DHD..
I did google this and I found that it maybe something to do with android itself..looks like /INIT is an android process..
If you notice your DHD lagging then download Watchtower and I'd bet you will see the /INIT process killing your phone..
------------------------------------------------------------------------------------------------------------------------------------
EDIT - A fix has been found to stop the /Init process lagging the phone.
On your phone go to..
Menu/settings/applications/development/now turn on Usb debugging..
This seems to keep the / init process at 0% CPU usage, it also works when the /INIT problem starts, turning USB debugging on will make the /INIT process drop back to 0%, very nice to see.
Ive contacted the Dev to find out if he can tell us why this method has fixed the problem.
Still need an update from Htc but at least we can use our phones again..
There doesn't seem to be any negative effects from turning this option on, the only thing to note is turning it off to connect to your pc could bring the /init process back and lag your phone. You can download Android Manager from the market for free which will allow you to transfer data from your pc using Wi-Fi, using this app you can keep the USB Debugging on.
-------------------------------------------------------------------------------------------------------------------------------------
EDIT 2 - It looks like you can connect to the pc via USB cable with the debugging turned on without problems, the only difference is that it will try and install additional drivers...because of the debugging mode..
Im using windows 7 and the ABD driver wont install...you need to download Htc Sync on your pc which downloads the ABD driver !!
We should also watch the battery as this may actually increase battery life...
-------------------------------------------------------------------------------------------------------------------------------------
EDIT 3 - Not one single person has come back to me and said that the /INIT problem has returned after this fix...lets hope it stays that way.. 10/11/10
---------------------------------------------------------------------------------------------------------------------------------------------------
EDIT 4 - A lot of people including myself have found that this fix improves their battery life quite a bit.
-----------------------------------------------------------------------------
Last EDIT before thread is locked just for reference and to help people !!!
For people that have the com.htc.bgp process that loads the CPU it stays at 80-90% all the time, and i have autosync on, if you stop auto sync the process goes out....
So here is the final fix in the link below (post 7)
http://forum.xda-developers.com/showthread.php?t=659325
Thank you to everyone in this thread for there efforts...amazing response.
Thanks to all the XDA Community...Including the Devs and Mods
Thread Closed
nednapalm said:
I'm getting the problem.
No apps installed except the flash and maps update, oh and OS Monitor.
Have turned off "Fast Boot" and removed battery to reset, ok for now. Very scared to start installing more apps, nearly unusable when it is lagging
Click to expand...
Click to collapse
I also tried the "turn off fast boot and it was ok for 2 days, it came back this morning though..It is very worrying and yes, the phone is unusable until it is Restarted..Thanks for the reply.
sanju007 said:
LAG WHAT?
I hope not, the samsung galaxy s have lag issus and its very bad and i sold de sgs
And now the DHD gets also lag problems ?
Ik hope not, then i will not buy this phone
Maybe an good task killer wil help ?
More people have lag issus ?
Can you make a video ?
Click to expand...
Click to collapse
An app killer doesn't solve the problem and Im unsure how many people are having this problem, to my understanding its not many...that's why I started this thread to try and find out.
I wouldn't worry yet...
I will make a video when it happens again...it may take a few days to come back....but it always does...a video added to this thread would be most useful...just have to wait till it rears its ugly head again.
So it seems that /init is a core process regarding the initialisation of the Android system and userspace hence the fact it cannot be killed using OSMonitor. It is always the first process that runs on Linux systems after boot and acts as a parent process which itself initialises then processes needed to get the OS going.
Here is a description of the Android Init Process from elinux,
'init'
A key component of the Android bootup sequence is the program 'init', which is a specialized program for initializing elements of the Android system. Unlike other Linux systems (embedded or otherwise), Android uses its own initialization program. (Linux desktop systems have historically used some combination of /etc/inittab and sysV init levels - e.g. /etc/rc.d/init.d with symlinks in /etc/rc.d/rc.[2345]). Some embedded Linux systems use simplified forms of these -- such as the init program included in busybox, which processes a limited form of /etc/inittab, or a direct invocation of a shell script or small program to do fixed initialization steps.
The init program processes two files, executing the commands it finds in them, called 'init.rc' and 'init.<machine_name>.rc', where <machine_name> is the name of the hardware that Android is running on. (Usually, this is a code word. The name of the HTC1 hardware for the ADP1 is 'trout', and the name of the emulator is 'goldfish'.
the 'init.rc' file is intended to provide the generic initialization instructions, while the 'init.<machine_name>.rc' file is intended to provide the machine-specific initialization instructions.
The Bug
The /init bug has presented itself on numerous handsets including the HTC Desire, Nexus One and Droid X models. It seems to be specific to Android 2.2 and reports the same symptoms on all handsets. Primarily this is due the 99% CPU usage causing system slowdown and left unchecked, high battery usage. It is not specific to HTC Sense ROMs as it also presents itself on stock releases. The only solution so far is a reboot. Hard Reboots and altering system settings seem to have no effect on the reproduction of this bug.
I can only speculate to what is causing the issue and hopefully a Dev can shed some more light.
Logically it seems as though a 'rogue' process is triggering /init to resume its primary function in regards to checking filesystems and attempting to spawn other system process. Due to some form of miscommunication between the processes in question, /init continues to perform these post boot tasks in a constant loop.
Think of it like this, if you try perform tasks straight after boot, the phone is unresponsive while the SD is mounted/checked and all other processes are fired up. The /init process is responsible for these tasks. If it were to loop, you would experience the symptoms we are having.
I found this on Wikipedia:
After /init has spawned all of the processes specified, init goes dormant, and waits for one of three events to happen:- processes it started to end or die, a power failure signal[clarification needed], or a request via /sbin/telinit to further change the runlevel.
So our trigger should hopefully be narrowed down to these three events.
Regarding what I posted before, the connection between sync and the bug has proven itself to be a false one.
I've also noticed that sometimes the bug can be present, however there is little impact on the responsiveness of the OS. It can seem as though everything is ok yet the CPU load can be extremely high, resulting in poor battery performance.
Anyway, hopefully more people can contribute to this thread so we can build up a better picture of what is going on. I will also try and grab a Logcat and ask anyone else near their PC when it happens to do the same.
There is a thread here which has users complaining of the same problems, yet no solutions are presented. Hopefully we can make a bit more noise and get some definitive answers.
Regards.
Hey guys some great feedback here, as with my link on starting this thread the /INIT is an android 2.2 process, auto sync on/off doesn't solve the problem neither does a hard reset, taking the battery out ect...
The guy in the link says his method worked for him, can't say the same for myself, I have a feeling his problem will be back...but if it did fix it for him then thats great, just cant say the same for me
http://forum.xda-developers.com/show...3&postcount=42
I have gone 5 days without the problem coming back and then Oh no its back, sometimes it happens twice a day, all the above doesn't fix this problem im afraid from what I have experience anyway.
The /INIT process is only 132k, something so small causes the phone to be basically unusable....very frustrating.
The 1.32.405.6 update also doesn't solve this problem, I updated yesterday and 10 min later I had the dreaded /INIT problem...
The so called "turn off fast boot doesn't fix the problem either, I have had the /INIT lag problem with it switched on and off...
What I find to be the most strangest thing is that if this is indeed an android process which it most likely is then why doesn't every DHD phone have this lag from time to time???.....why only certain phones??..
I haven't had the problem since yesterday (around 12 midday), when it occurs again I will be posting a video as requested...
The mystery continues.......There is NO solution as yet that fixes this problem.
Thanks to Lynxboy, your posts give some good information.
I wonder if this has any relevance to the problem from a linux based PC..
It seems that /INIT uses the same Process ID - 1 (found from using watchtower)
http://www.yolinux.com/TUTORIALS/LinuxTutorialInitProcess.html
BigMango said:
You purchased it from ebay, but did you buy it from a shop or from an individual (second hand)?
If you got it from an ebay shop they should give you a receipt. If it was from an individual, he should give you his original receipt (that's when the warranty started).
Anyway, the phone has a 2 years warranty, so you are covered for the next 2 years minus 1 or 2 weeks. And the paypal transaction is a valid payment receipt (it can be verified directly with paypal); so even without the receipt from the first owner HTC should cover you since the phone can't be 2 years old.
Get in touch with HTC directly, they should replace it. But the tricky part is that the problem must happen when they check it out, for this reason I would also make a video of the problem the next time it happens and send it to them by email so they can keep it on file with your RMA.
Click to expand...
Click to collapse
Thanks for the advice, Im going to contact the seller, he had it on upgrade and shipped it to me the following day..he seemed a nice guy so It should be ok...Now its just a matter of waiting for MR INIT to show up haha....wonder if he wears a hoodie LOL
bimmerfox said:
I'm not wrong because I see it with my own eyes. Even my DHD had the same problems as described. After the update no more /INIT at 90% and it keeps running smooth now.
Try to keep your patience before quoting a person who is willing to help others.
Click to expand...
Click to collapse
What?? Why do you think I made this thread...to help myself and others...as we do at XDA....the update doesn't fix the problem....just because yours hasn't lagged since the update doesn't mean its fixed....I've gone 5 days with no lag and it came back...like yours probably will.
Ridiculous....
EDIT- You can't post a statement that the problem as been fixed when numerous people have done the update and still experienced the /INIT problem...how can it be fixed??...and since the update only came out yesterday you have no way of knowing this for sure... its way to early to say that.. Try reading through posts in the forum and gather some information next time.... the update was for the youtube fix, we're not even sure that HTC were aware of the problem at the time.
Hi guys,
Just finished work and have caught up with the thread since I last posted and wanted to clarify a few things. I would also ask any new readers to find my previous post which covers much of the nature of the /init process.
The problem is solely software based. The hardware is NOT at fault!
The /init process is the parent process of Android/Linux, hence the PID 1 in OS Monitor. Imagine it as the ignition system in your car. You need to turn the ignition to fire up the other systems and that technically is the role /init takes.
It is not a rogue process in itself. It cannot be killed or closed via a task manager.
The latest update was not a fix nor does it resolve the issue.
The bug IS a Froyo bug and affects numerous devices not just the DHD although it is not present in all Froyo ROMs.
It is possible the memory management is to blame however I have run many Froyo based ROMs from FRF55 and not experienced it before; they all use the same memory management.
The three triggers for /init to awaken after its boot tasks are completed are specified in my previous post. These are the most likely causes for our issue and are in my mind triggered by some rogue process interactions.
A logcat will only really be useful if it captures the event taking place. A logcat taken when the /init process has started will report back specifically that.
Just because you haven't experienced the bug in 2days doesn't mean you are bug free, nor is there a bad batch of phones as this would indicate a hardware issue.
Continuing this thought, it is possible if you are on a branded operator ROM you may be bug free.
The /init bug is extremely annoying.
Regards.
Yes off topic...
Im asking the mod to still keep this a sticky but to lock the thread as there is really nothing left to discuss and its just here for people that are still having the /init problem as a reference...
EDIT - Thread being locked soon so....
Agian thanks to all xda community !!
Is this stickie needed anymore? Has this been corrected by any software update?
I've had this problem since the day I got the phone (December 2010) and got it again today. Once I see the obvious lag of everything, I just restart.
If it can help...
I have noticed this phenomenon the first time just after installing 2 things in my DHD :
- creating the HTCSense account (and keeping it synchronized one a day)
- installing the HTC plugin for Picasa Web Albums in the Album application.
Maybe coïncidence, maybe not.
I have disabled all HTC Sense stuff I can see. It always happens when performing some action, like opening a new app. It seems to occur so randomly, it happened again the day after my last post, but has been fine since then.
Problems with calendar after removing cache and program data.
I had major problems with com.htc.bgp using up to about 90% of my processor from time to time. When I searched the forums I found this thread.
I tried what is stated in the top post and went ahead and cleared the calendar data and the gmaill data. This is all fine, I don't seem to get any more warnings about com.htc.bgp reaching the 90% mark. One slight problem that occured though is that now when I'm syncing my calendar back to what it was, it either does not search or does not find all the other calendars that I have. The list is just totally empty. Strange as it is, It does find and sync with the default [email protected] Gmail's working fine and syncing properly though.
Since I rely on the calendar I really need this to be fixed as soon as possible.
I don't want to put words in your mouths, but I figured I might need to factory reset the phone. No biggie, but a time consumer, since I need to recustomize everything again (not rooted, not titanium).
Are there any ways of luring the calendar back on track. Jumpstarting it without a factory reset?
Thanks in advance.
Henrik
So apparently all it needed was a full night of syncing, because now it works again.
It seems though that I got rid of the annoying com.HTC.bgp that drained my processor.
Thanks to the thread
Sent from my Desire HD using XDA App
Have not experienced this since the 2.3.3 upgrade, problem solved!
I'm having this problem on my Defy after installing SetVsel, setting any values, after time the cpu stuck at 100. Watchdog lite didn't show nothing but 100%, not any process higher than 50 even. I turned on in the watchdog to show system processes and ther it showed that:
init
Linux process
Had most the time the highest percent used
I googled and found this topic. The
Menu/settings/applications/development/now turn on Usb debugging.
Click to expand...
Click to collapse
solution solved my problem. The proc isn't anymroe stuck at 100%.
I starting a bounty for fixing the android os bug.
Anyone that fixes this bug gets the bounty. (not samsung or google tho)
Donations so far:
Doc 30$
dan13l 30$
TML1504 30$
Has anyone checked to see if its google maps chewing it up? It did this on some other phones with the latest update.
neubauej said:
Has anyone checked to see if its google maps chewing it up? It did this on some other phones with the latest update.
Click to expand...
Click to collapse
Keep the discussions in the other threads.
But maps is not the cause.
Switch Wifi sleep policy to "never sleep"
From the page for this issue on Google Code (others have linked to this page already but apparently no one here has bothered to actually read it):
code.google.com/p/android/issues/detail?id=15057
There appear to be two main causes of extreme battery consumption by the Android OS process.
#1 is the Wifi sleep policy of "wifi off when screen off", which is usually the default. If you haven't made a point of changing yours, it's probably still on this setting. In the Wifi settings page (where the SSID list is), press menu, then advanced, then Wifi sleep policy. Change it to "Never". A more blunt-force solution is to keep Wifi switched off all the time.
#2 is some combination of Google Latitude and location services (GPS and Wifi). This one seems to be less common and many people say it's definitely not the problem. It may be related to #1 in that a problem with the Wifi is causing location requests to fail, somehow causing extra processing.
Comment 23:
The increased consumption only occurs, when I have the wifi sleep policy set to "sleep while display is off". In this case the battery consumption is very high while the display is off.
Comment 31:
Only changing Wi-Fi sleep policy to Never from "Never when plugged in" fixed this for me for now.
Comment 40:
I can confirm that "Always on" WiFi policy solves the problem for me
Comment 53:
By putting "always on" to the wifi sleep policy, I'm now at 25% battery after 1 day 7 hours of usage (since last charge)
Comment 54:
The recommendation of changing the wifi sleep setting to 'Never' appears to have worked for me as well.
Comment 88:
Both "always on wifi" as well as "turning wifi off manually" work for me. The heavy battery drain only occurs in combination with the "wifi sleep while screen is off" policy.
Comment 90:
I have 'never sleep' policy for WiFi, and battery life is just fine.
Phone easily can sustain a day with some 40% battery remaining.
Click to expand...
Click to collapse
And so on...
A poll to see whether these solutions work for everyone would be good. I probably can't make it because I just registered.
Disclaimer: I have ordered but not yet received my Galaxy S II. The info in this post is not my firsthand knowledge, just some quick research.
ninewise said:
From the page for this issue on Google Code (others have linked to this page already but apparently no one here has bothered to actually read it):
code.google.com/p/android/issues/detail?id=15057
There appear to be two main causes of extreme battery consumption by the Android OS process.
#1 is the Wifi sleep policy of "wifi off when screen off", which is usually the default. If you haven't made a point of changing yours, it's probably still on this setting. In the Wifi settings page (where the SSID list is), press menu, then advanced, then Wifi sleep policy. Change it to "Never". A more blunt-force solution is to keep Wifi switched off all the time.
#2 is some combination of Google Latitude and location services (GPS and Wifi). This one seems to be less common and many people say it's definitely not the problem. It may be related to #1 in that a problem with the Wifi is causing location requests to fail, somehow causing extra processing.
And so on...
A poll to see whether these solutions work for everyone would be good. I probably can't make it because I just registered.
Disclaimer: I have ordered but not yet received my Galaxy S II. The info in this post is not my firsthand knowledge, just some quick research.
Click to expand...
Click to collapse
These fixes wont cure it for sgs 2.
See attached. It's not the wifi policy.
I too will pledge $30 for a working fix once I've verified that the problem is solved.
Sent from my GT-I9100 using XDA Premium App
dan13l said:
See attached. It's not the wifi policy.
I too will pledge $30 for a working fix once I've verified that the problem is solved.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
Nice, i will update 1st post with all the findings so far.
"android os" bug is NOT:
Wifi bug (always on)
Maps bug
Any installed apps bug
Operator bug
Latitude bug
count me in with $30 as well
DocRambone said:
Nice, i will update 1st post with all the findings so far.
"android os" bug is NOT:
Wifi bug (always on)
Maps bug
Any installed apps bug
Operator bug
Latitude bug
Click to expand...
Click to collapse
I had similar issue on SGS, my problem was because aparently I got a faulty modem file, I noticed my signal bar going up and down continously.
Has anyone tried changing modem?? I don't have a SGS2 so I don't really know if there are modems to choose from...
Good Luck Doc.
gtluis said:
I had similar issue on SGS, my problem was because aparently I got a faulty modem file, I noticed my signal bar going up and down continously.
Has anyone tried changing modem?? I don't have a SGS2 so I don't really know if there are modems to choose from...
Good Luck Doc.
Click to expand...
Click to collapse
Getting a good idea now, a first setup on 3g network (no wifi), avoid the dir 655 routers and you be fine.
Wifi policy is set to "never" by default, so I can't see why it would help anyway.
That said with KE1 and a factory reset, although I have higher than would usually be expected AOS usage, my battery drain issue hasn't been all that bad - from a full charge today (7hr 15 on battery) to 83% with maybe 20 minutes angry birds, and the occasional checking of emails, texts and facebook and playing around with it a bit...
Screen on time 31 minutes... Android OS at 20% now and Wifi Sharing(!?) on 13%.
So not too bad, but it could be better IMHO - equates to about one and a half days of light use - definitely room for improvement.
There are so many threads about battery so not sure which one I should post it but..
I saw some strange things in Logcat. I get alot of those errors :
E/lights ( 2701): write_int: path /sys/class/backlight/pwm-backlight/brightness, value 170
E/lights ( 2701): write_int: path /sys/class/leds/blue/brightness, value 0
I don't exactly know what the error means(well they are related to the menu and return backlight I think), but the E/ stands for error in case you didn't knew.
Do you guys get the same kind of errors in logcat?
I've noticed 2 things:
If I wake it up, the cpu frequency doesn't go below 800mHz. (with only 4% load)
Only after I've started an app (not a widget etc.) it went down to 200.
(look at the "Temp+CPU V2" widget on the screenshot)
And the camera seems to run further if you don't go back out.
After a shot in school, I pressed the power button and at home, it felt VERY hot (front and back) and the battery level went down in 3% steps every 1-2 minutes.
But the camera wasn't listed in the battery stats, only Android OS, which was eating 70%.
Screenshot
Android OS Battery bug
Hi!
1. Install SystemPanelLite Task Manager from the market.
2. Run SystemPanel and open settings and check the "System processes" option. Close settings.
3. Scroll down in the process list until you find the process "android.process.media". If you have a CPU usage of more then 10-30s and the process usage gauge to the left moves up and down you probably have the Android OS battery bug.
At this point you can try the following;
- Shut down your phone. (Not just turn it of. The complete shut-down-power-off-thingy)
- Remove your external SD card.
- Start up your phone again.
- When the scan media is complete, do step 3 above again. If you don't see the problem at step 3 your SD card has a corrupt filesystem. And needs to be reformated. Follow these steps;
- Backup your data first!!!
- Settings -> SD card & phone storage
- Unmount SD card
- Format SD card
- Restore files from your backup.
If the problem persists your internal SD card might have a corrupt filesystem and needs to be reformated. Follow these steps;
- Backup your data first!!!
- Settings -> SD card & phone storage
- Format internal storage
- Restore files from your backup.
More details; What happens when you have a corrupt filesystem is that android.process.media tries to read a file but fails over and over again. The filesystem might not look corrupt to you. And you can read and write files on the SD card without problems. But at some point the android.process.media failes to read the files and loops like crazy, draining your battery.
I had a corrupt filesystem (FAT32) on my external SD card. I also had Android OS battery usage of 60-70% and a fast draining battery. I hope this can help others.
Best regards,
/Pontus
My android.process.media is 27 secs. Is this in the acceptable range?
Hi!
It's a bit high I'd say. I've got like 2000+ photos and I'm at 9 s after a days use.
Take a look here;
Settings -> Applications -> Battery usage
If Android OS is above 50% then you should consider my suggestions.
Most importans, does your phone get hot and use a lot of battery without heavy use?
Removing your external SD card and rebooting your device isn't that much work. If that gets rid of your problems, then reformat your SD card.
FAT32 isn't the most robust filesystem.
Best regards,
/Pontus
how can i remove the languages which i dont need?
what's causing the battery drain inside Android OS
After doing further investigations with watchdog, the Android OS battery drain is caused in stand-by by:
1. suspend (linux process)
2. events/0 (linux process)
They use heavily the processor while in standby... I've seen alert of up to 80% of CPU in both processes.
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