Hi All,
I'm having this odd battery drain. I've installed Battery History and saw that under partial wake usage, "Maps" is top on the list. Even higher than "Android System".
Now, does this "Maps" refer directly to the Maps app? Or does any other app also reports as "Maps" on battery history?
Odd is that even after reboot, it still gets high partial wake usage but checking Samsung's task manager, the Maps app is not running, or at least not visible on the current tasks.
Does anyone has experienced this? I'm using Doc's ROM v9.9.5 (JS8) with Damian's Kernel and Crysis Revolution Theme, if that can be of help.
A second question: If I was to go back to an Eclair stock ROM, that would upgrade through KIES to Froyo, which version would I use? My product code is HKDXEU. Also, do I need to change bootloader if I was to do such thing? Or does Gingerbread's bootloader would work on Eclair?
I was thinking of reverting back to Eclair (repartition, 512.pit), then upgrade through Kies and then go to Doc's ROM again. Kind of really reseting from "as much original" as it could be.
tfvaldo said:
Hi All,
I'm having this odd battery drain. I've installed Battery History and saw that under partial wake usage, "Maps" is top on the list. Even higher than "Android System".
Now, does this "Maps" refer directly to the Maps app? Or does any other app also reports as "Maps" on battery history?
Odd is that even after reboot, it still gets high partial wake usage but checking Samsung's task manager, the Maps app is not running, or at least not visible on the current tasks.
Does anyone has experienced this? I'm using Doc's ROM v9.9.5 (JS8) with Damian's Kernel and Crysis Revolution Theme, if that can be of help.
A second question: If I was to go back to an Eclair stock ROM, that would upgrade through KIES to Froyo, which version would I use? My product code is HKDXEU. Also, do I need to change bootloader if I was to do such thing? Or does Gingerbread's bootloader would work on Eclair?
I was thinking of reverting back to Eclair (repartition, 512.pit), then upgrade through Kies and then go to Doc's ROM again. Kind of really reseting from "as much original" as it could be.
Click to expand...
Click to collapse
hi. I had this problem with my HTC Desire 2.3.3 Oxygen Rom by adamg. why don't you try to signing out of latitude? it seemed to work for me..
I never logged in on Latitude (or can't remember doing so). But I'll check this. Thanks for the tip.
tfvaldo said:
I never logged in on Latitude (or can't remember doing so). But I'll check this. Thanks for the tip.
Click to expand...
Click to collapse
I thought I solved my random battery drains with 2.3.3 but I think Maps is another factor. Anytime I use a Maps related App (like MyTracks a few days ago or Places + Navigation today) not the Maps app would show up in the battery history, but "Android OS" is rising and sucking the battery dry. The CPU never goes to "deep sleep" until I restart the phone
I signed off latitude some weeks ago, but i looks like some parts of Maps causes problem with the system :-(
Try uninstall and fresh install from the market
GTi9000 insanitycm010/insaneglitch
Related
Hi people,
This is my first post, forgive me if I'm doing it wrong or in the in wrong place...
I have an annoying issue with my Galaxy S that I have googled and cannot find any information about or whether other people are also having the same problem.
When I set the time on my device in sync with the time I get from googling the time in my location, within a day my device is already 10 minutes behind the time google says is the time in my location. (other devices synced with google's time remain synced, its just the Galaxy S that does this).
A bit of information on my Galaxy S:
I am running Android 2.2(beta) I9000XXJP3,
kernel version 2.6.32.9,
build number FRF91.372
Ext3 speed fix running on phone
I am an electronics engineer, so my first guess as to what the problem is is that the phones real-time clock is not keeping time accurately (if in fact it has a hardware real-time clock!).
If theres no real-time clock then I am guessing it may be a problem with a software implementation of the real-time clock.
Has anyone else experienced this problem? Is it a problem perhaps with running the EXT3 speed fix that is causing the software to not keep time accurately? (as i understand it, the EXT3 speed fix and modified kernel reduces the number of writes to the Samsung RFS? Could the reduced number of writes be causing the software real-time clock to not be updated on its regular intervals?)
Any help is much appreciated. I have already been late for a couple appointments because of this problem lol
Thanks peeps
install clocksync that will take care of the time problem if any
http://forum.xda-developers.com/showpost.php?p=8027593&postcount=31
in a way i think the clock problem reported by some people might be lag related
i never have lag on my phone, and coincidentally i have no problem with time being delayed
running stock JH2, no lag fix as it's not necessary, GPS quick lock in 5 sec, no jumping around or to the next lane or next street
Excellent
Thanks a bunch. I may have to consider downgrading back to a working version of 2.1.
From all of my experiences with Android 2.1 on the Galaxy S (and I have tried about 8 different releases) is that I constantly get the "black screen of despair". Installing Froyo fixed that problem to a degree, and I rarely see the black screen with the speed fix. The phone is much faster.
From others' experiences, which firmware do you guys use? Or a more relevant question, which firmware have you found to be the most stable and usable firmware?
Cheers
TeRm!n8oR said:
I am running Android 2.2(beta) I9000XXJP3,
Click to expand...
Click to collapse
There's your problem.
I'm using the JPH Froyo firmware with a lagfix. Works great for me although it has a minor lag now and then.
I'm pretty sure there is a clock in the phone. I don't think there is any phone out there without a real-time clock. I don't see what lag or file system has to do with the clock... Most likely your problem is a syncing issue. Set your time manually and turn off all auto syncing options, maybe there is problem with your operator’s clock or in the app you are using to sync.
Actually, JP3 seems to have a known issue with time keeping. I'd be guessing maybe it runs a NTP daemon with an incorrect clock skew (guessing though). Either way, heard it many times for JP3, but never any other firmware.
The reality is though, only developers should be using beta versions of froyo anyway.
Maddmatt said:
There's your problem.
I'm using the JPH Froyo firmware with a lagfix. Works great for me although it has a minor lag now and then.
Click to expand...
Click to collapse
Are there any significant improvements between JP3 and JPH? Or is JPH just a more matured development from JP3? Are there changelogs/bug fix reports anywhere available for these?
PhoenixFx said:
I'm pretty sure there is a clock in the phone. I don't think there is any phone out there without a real-time clock. I don't see what lag or file system has to do with the clock... Most likely your problem is a syncing issue. Set your time manually and turn off all auto syncing options, maybe there is problem with your operator’s clock or in the app you are using to sync.
Click to expand...
Click to collapse
I'd imagine there would be a hardware real-time clock too. What got me thinking that it may be implemented some other way is that I turned off all syncing and manually set the time last night. I made sure i had wifi off, cellular data off, GPS off, roaming disabled, etc. prior to manually setting the time through the inbuilt clock.
I woke up the next morning to find that overnight the clock had somehow offset itself 5 minutes backwards from the time kept by google for my region. This was what initially made me think perhaps the time was being kept in software with an internal battery backup or something (I haven't cracked open my phone yet to see whats under the hood in fear of hurting it ).
Weird problem however you look at it. Although I don't think the problem occurred under Android 2.1, it seems to be a recent thing (post install 2.2 + Speed Fix).
TeRm!n8oR said:
Are there any significant improvements between JP3 and JPH? Or is JPH just a more matured development from JP3? Are there changelogs/bug fix reports anywhere available for these?
Click to expand...
Click to collapse
Matured. But some people are having probs with JPH corrupting their IMEI's.. But there are no changelogs (because it's a leak). I haven't heard any complaints about the clock being wrong in JPH.
Rule of thumb is to use Eclair unless you are a developer though. Pre-release firmware isn't a good thing to use on a phone you rely on
andrewluecke said:
Matured. But some people are having probs with JPH corrupting their IMEI's.. But there are no changelogs (because it's a leak). I haven't heard any complaints about the clock being wrong in JPH.
Rule of thumb is to use Eclair unless you are a developer though. Pre-release firmware isn't a good thing to use on a phone you rely on
Click to expand...
Click to collapse
Funny you'd say that though, I've had less problems with Froyo JP3 (other than the time problem ^) than I did with any version of Eclair. Especially when it came to the black screen of despair. I could not find a way to minimise its frequency, let alone get rid of it completely with Eclair. Mind you, at the time when i put JP3 on my phone, Eclair was only up to JM6 I believe.
Maybe it'd be worth giving JM7 or JM8 a go...
After i installed Froyo i noticed my battery life was drained faster than usual, on eclair i had ~48 hours, now on froyo max 24h.Just to note, i have stock Froyo+z4root+z4mod.
After playing around it for a bit, i entered battery history, and under Network usage tab, i have a process named 0, wich usess 100%, and kills my battery. When i try to click it i get a force close from application settings and nothing happens.
Anybody has any ideea what this is? or how to fix it or something
Are you using any lagfix?
I have already mentioned i'm using Z4root+Z4mod.
I have the same problem on stock ZSJPD and Speedmod k9a. Any help would be appreciated.
I have the same problem too. Someone please help.
Wow I have this same issue
Sent from my GT-I9000 using XDA App
After looking around in this forum i found that there are others that have this problem with HTC smartphones, so its not SGS exclusive, wich probably means its either somehow a linux process, or, its an application that does this.
Tryied using Droid Wall to kill most apps from internet acces(not all) the process is stil there and eating away my battery >.<
Bumpiti bump, is there a way to even try to diagnose this?
im having the same issue but not only the 0 process , i have UID 10007 and dialer also competing with 0 . all of them are hurting the batt bad. couldn't get to find what the 0 process is , im guessing its something from samsungs side thats buggy and it doesn't showup on ATK too ..... i know that samsung service center over here r not qualified regarding such technical matters and all they'll do if format the phone and give it back with a fresh install of 2.2
any devs/techs around that can find or lead us towards the culprit ?
Hmm, bump, have this problem too. On doc's bujp8 and hardcore's k9a kernel if that's any use.
Having the same problem now on JPU, was fine on JP6 earlier.
Guys please help !!!
bump,same prob!
Apparently '0' is the linux root process
It looks like at least some of you (most? all?) are running non-standard firmwares.
I live in Canada and am using the SGS on Bell Canada. Examples of my native firmwares are JH2 (2.1) and JK3 (2.2). I was having TERRIBLE battery performance when I flashed a non-native firmware and didn't get back to anything decent until I flashed the right modem for my region and enabled the 850 band which wasn't enabled by default by the firmware I had flashed.
Also, look into your WIFI sleep policy. This can have a huge impact. I leave mine as "sleep when screen turns off". I don't recall what the 2.2 default setting is.
Menu > Settings > Wireless and network > WIFI settings > menu / Advanced > WIFI sleep policy > edit & menu/Save
I have stock froyo that came with kies(not patched or anything), so the first part of your statement is irelevant.
Sinsst said:
I have stock froyo that came with kies(not patched or anything), so the first part of your statement is irelevant.
Click to expand...
Click to collapse
They're simply tips and suggestions. I'll try and be less helpful next time.
I know, thanks for the suggestions, the thing is that our problem is just frustrating(with the unknown battery draining processes) and not something that can be solved by using the search button
Hi all!
I tried searching the forum for similar issues. Sorry if exists.
I have a Galaxy S (I9000XXJPP) which i updated to 2.2 Froyo through Kies. Everything went well, Froyo seems to be running ok but i do have a big problem: battery performance. It drains in only a few hours. in standby it goes from 100% to 10-15% over the night. Before the update it took more than 2-3 days.
I looked on other forums and there are others with the same problem.
Some said it was because of the Wifi sleep policy which i changed to "When screen turns off" but in vain.
Of course i don't have any apps that drain the battery.
Anyone got to the problem and solved it?
Its probaby the Gallery sensor problem
Go replace the Gallery app with a fixed/bugfree version. Need root and root explorer to do it. Its all over the forums just look
so this sensor works in the background and drains the battery this much?
sorry but i didn't find any thread similar...
Gallery and email seem be causing the most issues. Its very common and appears to happen on quite a few different ROMS.
SGS tools has a fix for an alternative gallery.apk which you can try (you will need to be rooted though). You can download SGS tools from the market.
_dsk_ said:
Gallery and email seem be causing the most issues. Its very common and appears to happen on quite a few different ROMS.
SGS tools has a fix for an alternative gallery.apk which you can try (you will need to be rooted though). You can download SGS tools from the market.
Click to expand...
Click to collapse
i wouldn't root it. might be problems with the warranty after.
anyway not sure what i did but may battery is back to normal. stopped the auto rotation for a while then activated it back and didn't use the gallery.
ikst8 said:
i wouldn't root it. might be problems with the warranty after.
anyway not sure what i did but may battery is back to normal. stopped the auto rotation for a while then activated it back and didn't use the gallery.
Click to expand...
Click to collapse
z4root allows you to do a temporary root, but again thats up to you.
Your best solution, if it is the gallery causing the issue is to simply not use the gallery and find an alternative in the market to download.
i did just that. stopped auto rotation, downloaded just pictures from the market but still the other night went again from 70-80% to 0. it's weird sometime the battery is drained like hell but sometimes it's normal. i need to find the cause.
any way to get back to 2.1?
You can download a generic 2.1 ROM from samfirmware.com and flash it with ODIN.
Also, if there isnt an official Froyo for your product code yet, you can use the KIES Reg hack application to restore it back to 2.1.
same problem - battery drains extremly fast (Froyo 2.2).
diasbled push mail - battery still drains..
have no idea what to do.......
I faced the same "over-night" problem...I thought that background apps done that, but it seems that after turning off data network the life-time of my battery almost went from less than a day to about 4 full days. Maybe the signal strength was an important issue (indoor, I have about 2-3 signal lines). Also mail/calendar/weather/etc continuous updates drain the battery...
To summerise, If you have battery draining problem just root your device and install SGS Tools 4.0x and goto Patched Stock Apps in it and install the Gallery3d app which will replace your stock but buggy gallery. Also the Camera update is great imho as it allows you to use power button as camera shutter. Now If you do not want to root or so anythign drastic then just NEVER use Gallery and download JustPicutres! from market (Free) and use that from now on. Easy
I had this same issue. After updating froyo via Kies, battery life dropped from normal 2 days to less than 24 hours. With 3G disabled as well as sync.
But, what's even more strange, is that when I got frustrated enough and flashed back to JM2 with Odin, the same problem still existed! Only 24 hours or less, every time. Same happened with JM9 I tried after that.
Been trying these battery resets and stuff without success. Has anyone come into any sort on conclusion, what could be the reason for these battery-draining issues, especially AFTER updating/flashing?
Hi people!
On my Galaxy S i9000 I have on Juwe 5.3 (JVR) with Semaphore 1.6.0.
I have the following problem: my GPS works (good accuracy and locking speed) only when the screen is on. As soon as the screen goes off, I lose the fix and precision, while using tracking apps like Runkeeper or My Tracks and diagnostic ones like GPS Status.
I've tried to force the CPU on 1000 MHz with Voltage Control but the problem remains so I'm guessing it's not a performance issue.
Any ideas?
Everything else works fine.
Thanks!
The same happens on my phone (albeit w/ CM7), but I don't mind, since that would eat the battery. I can see how that would render certain apps useless, though. I've used a few ROMs in my day, and never noticed GPS staying locked while the screen was off. I'm interested in how you'd achieve this as well.
Hi.
Yes in fact when I was on stock the gps worked as expected but I was on froyo.
Than I updated to a beta GB and then to Juwe.
I'd prefer not to put a froyo rom just to test if possible. I'll wait for someone to come with some idea
Thanks!
Some updates:
- It seems not to be kernel releated (tried with both semaphore and CF-Root, will try also TalonDEV)
- Not rom releated also (from Juwe JVR to Simplicity JVT, passing thru stock JVT).
Any ideas?
Is there someone whose GPS stays locked even if the screen is off?
Thanks.
Interested as well. Anyone?
Hmm, my gps would always lose lock if i turned off screen (froyo too).. thought that was normal behaviour
i thought that depends on the app. navigon has a setting which says to keep gps on or off when minimised.
oswade said:
i thought that depends on the app. navigon has a setting which says to keep gps on or off when minimised.
Click to expand...
Click to collapse
Probably this is right. Should be app-related.
I used to have a lot of GPS problems, but I solved them connecting GPS for the first time with WiFi on google maps, after that, GPs worked great without wifi being necessary anymore.
gtluis said:
Probably this is right. Should be app-related.
I used to have a lot of GPS problems, but I solved them connecting GPS for the first time with WiFi on google maps, after that, GPs worked great without wifi being necessary anymore.
Click to expand...
Click to collapse
I will try that.
It seems that also other phones are affected by this problem/feature, after the update to Gingerbread.
Little update: the navigation app does not let the screen to turn off to not to lose gps fix.
Sent from my GT-I9000 using XDA App
All of a sudden today in my battery usage, "Media Server" is 2nd only to the display and the phone temp will climb from 89f to 120f or more just sitting there not in use. I looked to see what was running but nothing out of the ordinary shows up under running services. I also can't quite figure out what "media server" is or what would make it run like that. Any ideas or links would be really appreciated.
running GB continuum rom with the latest talon.
Check for updates to your apps, also have you installed any new apps?
mrhaley30705 said:
Check for updates to your apps, also have you installed any new apps?
Click to expand...
Click to collapse
I did install a few games and I also tried the gps fixes I found here: http://forum.xda-developers.com/showthread.php?t=1272141[/URL] .
After I noticed the heat from the phone I looked at batt usage, saw the "media server" and immediately uninstalled the games. then I rebooted into recovery and cleared caches and volt settings (just in case) and rebooted. It instantly started to climb in temp after the phone was done loading up.
Since it says "media" I also cleared app cache for the music app and for the video app but no change. Have also pulled the battery a few times.
I would try flashing shomans revert file from the continuum site (use the one for the version of continuum you are running). If that doesn't work, only thing I know to try would be reflashing the ROM.
Still having this issue off and on with no real pattern. I would appreciate any info on "media server" what it is, does or what app might use it.