So I was looking through the developers site located HERE: http://developer.nvidia.com/tegra-250-tango-development-kits & found this;
"In certain power saving configurations, touching the screen or "Android buttons" at the top of the device is not adequate to wake the device. To work around this, try inserting or ejecting the SD Card to wake the device. Failing that, you will need to reset or power cycle the Tango. Alternatively, please set the screen timeout to 30 minutes (Menu->Settings->Display->Screen Timeout)."
Seems like the BSOD issues are in the 'Tango' version of the Tegra 2 processor & this (which was located in the Known Issues section) is Nvidia's solution. So I plan on testing this workaround (re-inserting micro SD) to see if this can replace a battery pull. As most of us know the other way of preventing BSOD is by setting the sleep mode to never & this seems to work for some & is recommended by Nvidia. So if you can give this a try, Plz let us know the results.
Sent from my LG-P999 using Tapatalk
Does never sleep, effect batt life or conflict with set cpu?
Thanks for your informative post.
Sent from my LG-P999 using xda premium
missaellpzchvz said:
So I was looking through the developers site located HERE: http://developer.nvidia.com/tegra-250-tango-development-kits & found this;
"In certain power saving configurations, touching the screen or "Android buttons" at the top of the device is not adequate to wake the device. To work around this, try inserting or ejecting the SD Card to wake the device. Failing that, you will need to reset or power cycle the Tango. Alternatively, please set the screen timeout to 30 minutes (Menu->Settings->Display->Screen Timeout)."
Seems like the BSOD issues are in the 'Tango' version of the Tegra 2 processor & this (which was located in the Known Issues section) is Nvidia's solution. So I plan on testing this workaround (re-inserting micro SD) to see if this can replace a battery pull. As most of us know the other way of preventing BSOD is by setting the sleep mode to never & this seems to work for some & is recommended by Nvidia. So if you can give this a try, Plz let us know the results.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
I just reboot my phone before I go to sleep. It's a lot easier and is more of a preventative option.
Sent from my LG-P999 using xda premium
shovelhead83 said:
Does never sleep, effect batt life or conflict with set cpu?
Thanks for your informative post.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
No problem. Yes it could, depending on your settings for both SetCPU & how your charging your phone. The thing with setting your phone to not sleep while charging is that it's only a workaround so that if you charge your phone overnight your phone will have less probability of turning off during the night so that you won't suffering from the alarm never going off & or you having to battery pull. Charging overnight is never recommended for Lithium Ion Batteries but for some people its the only time they have to charge their phone and so this trick is useful to them. So unless you potentially need this then by all means use it but take notice of your SetCPU settings & how your charging your phone so that you don't have even more issues.
Sent from my LG-P999 using Tapatalk
set charging profile in SetCPU to 400-500Mhz
I was getting the SOD while charging quite frequently only after I rooted, not once did I get it before root. I did the never sleep trick about a week ago, no problems since, still have my fingers crossed, as this is my alarm clock.
I just start the clock and put it in "Night mode" before I goto bed and never have any issues.
I set to never sleep and have not had a BSOD since, thank you. Now if I could just stop the random reboots. This phone is frustrating.
Sent from my LG-P999 using xda premium
shovelhead83 said:
I set to never sleep and have not had a BSOD since, thank you. Now if I could just stop the random reboots. This phone is frustrating.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I can't really solve your random reboots but I can give you a suggestion. I recommend a complete reset of what ever rom your using (data, cache, clean system, ex: no themes, apps & or just a fresh install) then install one by one each app, unless you absolutely need an app, maybe an app install per day or every few hours, this is to pick out the app that might be the cause for random reboots. A fresh install might even solve your issues. Also, refrain from using titanium backup batch restore or even app data restore unless it's absolutely necessary (ex:game data, logins or settings you absolutely need). Lastly here are some apps that I have found that have created this reboot issue on my phone and that you may what to test first: seekdroid (or any app that request administrator permissions), large games (mostly games that rely on sdcard files to run), and system modification apps (apps that ask for superuser permissions & modify system data).
Sent from my LG-P999 using Tapatalk
thanks
missaellpzchvz said:
"In certain power saving configurations, touching the screen or "Android buttons" at the top of the device is not adequate to wake the device. To work around this, try inserting or ejecting the SD Card to wake the device. Failing that, you will need to reset or power cycle the Tango. Alternatively, please set the screen timeout to 30 minutes (Menu->Settings->Display->Screen Timeout)."
Seems like the BSOD issues are in the 'Tango' version of the Tegra 2 processor & this (which was located in the Known Issues section) is Nvidia's solution. So I plan on testing this workaround (re-inserting micro SD) to see if this can replace a battery pull. As most of us know the other way of preventing BSOD is by setting the sleep mode to never & this seems to work for some & is recommended by Nvidia. So if you can give this a try, Plz let us know the results.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Thank you very much for the information. Ill start testing 30minutes timeout now, this way locking the screen using the power button to save battery.
Related
Hi All,
I have a mt4g which is rooted with S=Off. I switch between the Sense launcher and Launcher Pro Plus. Usual apps on the phone, not too many.
For last week or so, I have been seeing that sometimes the phone gets really really laggy and Norton Util tells me that the CPU is 100%.
Also, I think most of the times, when this happens, I see a Sync icon up top. I do not sync a lot, just 2 GMail Inboxes and weather (every 6 hours). But I do see that Sync icon most of the times when this lagging happens.
I have tried removing apps, but this still seems to be a problem. I have see somewhere that turning the USB debugging to ON has helped many, but did not work for me.
I tried CM7 RC1 when it was out, but didnt like it (stock camera etc...) and I restored back to my stock ROM. Could this have done something?
Thanks
Ravneet
On your home screen hit menu key. Go to settings. Select accounts and sync. See what all is listed there. Chances are something with sense is constantly syncing.
Disable everything from syncing. See if the problem goes away. If so turn on one thing at a time until you find the culprit.
Hope that puts you in the right direction.
Sent from my HTC Glacier using XDA App
Have tried that. When I go there nothing is synching. Strange.
I have tried to remove all accounts from synch but still see the problem.
Went into recovery and wiped the cache about a hour ago. So far so good. Hope it stays this way.
Sent from my HTC Glacier using XDA App
I've noticed that there are apps that as soon as i download them, and open them that my cpu will go to 100% until I reboot my phone. System panel is a good app that isn't too obtrusive that will tell you exactly what app is doing what.
Have you installed anything new lately?
I uninstalled everything new.
Moreover I think every time this happens the battery is less than 30%. Maybe in low battery profile there are some apps which are over utilizing the CPU.
Sent from my HTC Glacier using XDA App
There's a couple threads like this. The stock Rom seems to have issues running rooted. Best bet would be to flash a different rom
Sent from my HTC Glacier using XDA Premium App
Turn on USB Debugging... See if that does anything
USB debugging is set to ON.
Sent from my HTC Glacier using XDA App
@NicGraner: Why would the stock ROM have problems with being rooted?
I am still having this problem. Uninstalled everything that is not important.
The phone just becomes unusable and I have to reboot. Un-installed Watchdog Lite too, as I thought since it is monitoring, it is taking up some CPU in background too.
No widgets on the home screens.
I guess I am gonna do a full refresh using the PDxxx.zip and go back to stock stock and then see what happens. not sure if I will lose my root once I do that.
Try the royal glacier rom it's solid stable and the sh!t
http://www.thepetitionsite.com/2/stop-t-mobile-from-being-bought-by-att/.......
I returned 5 phones for this exact problem, then I finally got one where the usb debugging trick actually worked. Before that I was just using OSmonitor from the market to see when I was hitting 100% then I would have to yank the battery as that was the only thing that would make it stop.
When I got this new phone I installed os monitor and waited for it to happen again, which it did, then I turned on usb debugging and watched my cpu usage graph drop to 0%. SUCCESS! Unfortunately since this was my 6th phone this solution seems to be the exception rather than the rule.
I did a lot of poking around on google trying to fix this and found a lot of people with different results. Try disabling t mobile sync and go to the myaccount app in the market and uninstall the updates. If that doesn't work try getting a new sim card and sd card, or just keep returning phones until t mobile offers to send you a g2x...
Also if you search around you'll see that this isn't just a problem with the mt4g. I found multiple threads where this happens on the nexus one, and several galaxy s phones. I really hope google is aware of this.
Sent from my HTC Glacier using XDA App
@johnsmith970: Thanks for the info. I will try calling TMO tonight and see what they say.
I am really bugged by this now. The phone gets totally unusable once this happens.
They will say to do a factory reset. Every tech support person I talked to told me to do that. This didn't solve the problem for me at all. It still exhibited the same symptoms on a fresh reset and not even signed in to google.
I would advise calling htc support just to let them know you are having this problem. Sending back a half a dozen phones per customer can't be good for anyones wallet or their peace of mind.
Sent from my HTC Glacier using XDA App
I have no idea why the stock rom doesn't like being rooted it's just what's been said and the solution which is most widely given (and mostly worked unless theres an underlying problem) is to flash a custom rom.
OK! I have more information for anyone interested.
I am tracking processes now in OS Monitor app from Market.
Most of the times it is the bluetooth daemon (bluetoothd) that goes bonkers. I was connected to my GPS in my car while driving, and when I came out of the car...the bluetoothd is going bonkers...looks like it may be trying to 'find' the device it was connected to. At the same time logcat2 process is also utilizing 30+% of the CPU.
I turned off Bluetooth and both the processes went away
So let me see if this sticks for couple of days.
Thanks
Nicgraner said:
I have no idea why the stock rom doesn't like being rooted it's just what's been said and the solution which is most widely given (and mostly worked unless theres an underlying problem) is to flash a custom rom.
Click to expand...
Click to collapse
I wasn't even rooted.
If you want to keep stock rom this is what I did and its absolutely solid.
Install this stock rom:
http://forum.xda-developers.com/showthread.php?t=1042586
After installing this rom flash faux123 first time kernel. After its all booted up reboot back into recovery and flash faux123 cfs rc3 kernel. I have my cpu set at 1200mhz and everything is gravy.
Sent from my HTC Glacier using XDA App
So I just got my g2x, rooted,nv and cwm. Flashed cm7 and I keep getting s.o.d(screen of death). I thought was rom problem so I.changed rom and im on xdblasters 1.1.0 and keep on getting them. Any solution orhelp would be appreciated.
Sent from my LG-P999 using XDA App
Not sure I know of a rom for g2x called xdblasters.
Also, what kernal are you using? Are you overclocking or undervolting? Are you using setcpu or pimpmycpu? What is your max and min cpu settings? When you flashed, what was your procedure for wiping? Did you fix permissions after flashing? Did you use a program to restore apps? Did you use that program to restore system settings? Did you choose to restore apps and settings from google account?
The answers to all of these questions could help determine what you've got going on.
I apologize, its x boarders. And well I am using fauxs newest kernel currently using 1.1 overclock but it would also happen while at stock cpu with previous rom.i don't restore with google but I use titanium backup for batch. When I do new roms I always follow the clean slate rule;Wipe data,cache,dalvik,bat stats. occasionally I forget fixing permissions but I do when I get alot of force closes.
Sent from my LG-P999 using XDA App
I didnt' see you mention formatting /system under mounts and storage. This is a critical step.
If it were me, I would try to keep everything as basic as I could each step of the way so that i could try to pinpoint the issue. Start by wiping everything (including sd card...just backup your user added stuff to your pc) and install a stock rom/kernal. See if it occurs stock...who knows? It's possible your phone is bad. Then if it doesn't misbehave with stock, then I would wipe everything again, including sd cards (interal and external), and flash cm7 (keeping cm7 kernal). I would try manually installing apps again, rather than using titanium backup or google restore. Just hook up to wi-fi (so you don't waste your data mileage) and go to market/myapps and redownload (hopefully you have a list of what you have).
But something to point out. On my phone, when I use CM7 (with stock kernal), I have to increase my minimum cpu frequency to either 312 or 456 instead of the default 216....216 seems to cause my phone to get stuck with the black screen also. The same thing happens when I run an undervolt kernal. So I've learned that my phone simply doesn't like undervolting, overclocking, or lettign the cpu run lower than 400MHz. Maybe that might help you out.
i was about to back up my sd and reformat it for that reason.I already tried formatting eemc mount or internal mem, and nothing. I also stopped using uv kernels and i kept my cpu min at 506 to keep it from doing, but with no result.I just flashed the newest release of xboarders 1.1.1 and i already got 3 sod while the rom is stock with nothing added. I am starting to think phone is bad. I bought the phone on Craigslist, so i might be S.O.L. i Appreciate
what should my mounts look like when i do a system format?
thrashingdeth said:
i was about to back up my sd and reformat it for that reason.I already tried formatting eemc mount or internal mem, and nothing. I also stopped using uv kernels and i kept my cpu min at 506 to keep it from doing, but with no result.I just flashed the newest release of xboarders 1.1.1 and i already got 3 sod while the rom is stock with nothing added. I am starting to think phone is bad. I bought the phone on Craigslist, so i might be S.O.L. i Appreciate
Click to expand...
Click to collapse
I just traded my sensation for a g2x off CL, sure glad mines had no reboots or sod, actually the best g2x if had out of my 4..
Thats good news. So I wiped system and using xboarders 1.1.1 and so far since last night no sod. I hope it sticks.
Sent from my LG-P999 using XDA App
thrashingdeth said:
Thats good news. So I wiped system and using xboarders 1.1.1 and so far since last night no sod. I hope it sticks.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Awesome, hope it stays good.
guess i spoke to soon. Was running fine all day till around 2 i installed setcpu and configured it. Or so i think, so i uninstalled and reset but when i am charging it it keeps turning off. AHHHH headache with this phone. When it runs, its smooth and so fast, i love it, but i dont know whats wrong with it.
I think I'm done with this. Can't figure out a away around this. Awesome phone but overwhelming problems. Appreciate the help everybody.
Sent from my LG-P999 using XDA App
have you tried a new battery? I believe most of the G2x problems are likely due to a bad batch of batteries.. why you ask I have come to this conclusion? If I OC heavily OR run the LED light when the battery gets low >30%, my phone will shut off. This would conclude the battery cannot supply the needed current for the phone at the lower battery levels... this is my particular battery but I wouldn't doubt there are worse batteries out there AND/OR reported battery levels that are much higher than actual and getting the same problem I have encountered. Food for thought.
Black6spdZ said:
have you tried a new battery? I believe most of the G2x problems are likely due to a bad batch of batteries.. why you ask I have come to this conclusion? If I OC heavily OR run the LED light when the battery gets low >30%, my phone will shut off. This would conclude the battery cannot supply the needed current for the phone at the lower battery levels... this is my particular battery but I wouldn't doubt there are worse batteries out there AND/OR reported battery levels that are much higher than actual and getting the same problem I have encountered. Food for thought.
Click to expand...
Click to collapse
I agree with him... I had worst case of s.o.d with my g2x. Atleast 3 times a day I had to take battery out... but I solved it by doing the following
1. Increase min cpu speed 300 or more.
2. Discharging the phone completely and then recharging it completely.
I barely get s.o.d. may be once in 2 weeks. And whenever I do get em. I give my phone a discharge recharge cycle... then its good for next two weeks
Sent from my LG-P999 using XDA Premium App
What "Screen of Death" are you guys referring to? Never experienced such a thing...
Phone wont wake? Or what? A quick google search for "android screen of death" and "g2x screen of death" revealed pretty much nothing.
Have you pulled a logcat?
I always fully charge and discharge battery for proper calibration. Doesn't seem to be helping in any matter. I also stopped using any CPU management because I thought that was.
bshakil said:
I agree with him... I had worst case of s.o.d with my g2x. Atleast 3 times a day I had to take battery out... but I solved it by doing the following
1. Increase min cpu speed 300 or more.
2. Discharging the phone completely and then recharging it completely.
I barely get s.o.d. may be once in 2 weeks. And whenever I do get em. I give my phone a discharge recharge cycle... then its good for next two weeks
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App
The problem is when phone sleeps and doesn't wake up. I have not pulled one, been thinking its hardware related.
AdamHart612 said:
What "Screen of Death" are you guys referring to? Never experienced such a thing...
Phone wont wake? Or what? A quick google search for "android screen of death" and "g2x screen of death" revealed pretty much nothing.
Have you pulled a logcat?
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App
Only happened. Twice today. Bahamas improvement I guess.
Sent from my LG-P999 using XDA App
Its hardware defect. No matter what ROM you put on the phone, it will continue. Youve gotta call TMO and get a replacement. Sorry if thats not what you wanted to hear.
I agree with the battery theory. I purchased two generic batteries from ebay and they last 3 times as long and have resolved many of the resetting and SOD issues that I was having. Also, updated ROMS seemed to help, and not letting it fall asleep while you are playing games or something memory intensive.
Well I bought a battery, hoping that helps a bit. So far its a lil better than usual. Using stock voltage kernel. When I get new battery I will test
Sent from my LG-P999 using XDA App
Hi guys,
So I'm not sure if the term "deep sleep" is correct here, but I'll use it anyway since it highly describes the case.
I bought the Tab 7.7 P6800 a few months back, it was on HoneyComb. 2 days later I upgraded to stock Samsung ICS. So I have no knowledge if the issue I'll describe was on HoneyComb as well or not. All I know is that I've been seeing this since stock ICS.
I moved from stock ICS to Nexus 7.7 then to Paranoid Android 2.22... all showing the same problem. So here goes.
From time to time when I go to use the Tab, I press the power button to wake it up... nothing would happen. Screen stays off and doesn't turn on. After a few quick tries I would hold down the power button to force a reboot.
The device is charged when this happens, and there is no specific duration after which this happens. Sometimes I would go to sleep and encounter this the next morning, and sometimes I'd leave it for lunch and then encounter this problem.
Last night for example when I came to use it, I had to force a reboot. I checked the battery stats under Settings, and this is what I found (screenshot taken today): please check attached screenshot. The red area is from last night.
Are there any logs that I could look into once this happens or any help from anyone around? Has anyone else encountered this? I've seen online posts about the same case but for another tab, the Transformer I believe.
Please do let me know your thoughts or from where to start debugging the problem.
Thanks all
//M
Hi, sorry to hear about your issues. Download logcat and look for Errors, if you have a terminal app installed, try and type: top - it will show you what processes is currently chewing cpu cycles..it might require busybox wich mean root is needed..
I had this issue but on the older Tab7 where the phone part would eat battery even in flightmode, no simcard and IMEI was missing, so flashing a different modem.bin file solved it, but you might have a different problem..
Thanks for ur quick answer.
I'll check the logs and see...
Sent from my GT-N7000 using xda app-developers app
Well, I'm not sure if I've solved the issue or not, but turning auto brightness off seems to keep the Tab in a usable state for the past day or so. Didn't encounter any problems waking it up...
Sent from my GT-P6800 using xda app-developers app
Looking at the attached image, it looks very much the same as mine, screen first 65-75% then android 9% so on.. no irregularities.
Also a try CPUspy so you can see where it hovers, also a betterbatterystat might help, think there is a free version here on xda..
I think https://play.google.com/store/apps/details?id=eu.thedarken.wl / Wake Lock is the answer to anyone facing SODs...
Sent from my GT-P6800 using xda app-developers app
I had similar experience.
I have similar experience with my tab.
It was good when i use P6800XXLQ1_CSC_ATO but it has occur with stock P6800DXLP8_CSC_XSE and SKYHigh rom 4.0. then i have back to P6800XXLQ2_CSC_ATO.
I have to try with others tools with my tab.
thank you...
The best solution so far and this hasn't failed me once for the past month or so, is stock 4.0.4 + EzyICS kernel and setCPU from the Play store! No SODs whatsoever again!!
Sent from my GT-P6800 using xda app-developers app
I'm at work so I'll make my initial post brief. I just got a year old Tab 7.7 and even if I put it in airplane mode with all radios off and no sim installed I lose at least 30% battery overnight. Night before last i went to bed with 75% and at 5pm yesterday had 6% left. Everything stock ics AFAIK
Probably some rogue app you installed using CPU cycles. Since you're not rooted, many good options (apps and methods) for finding the culprit are excluded. There are some that don't require root privileges though, but can't find wakelocks.
You need to take a look at the apps you installed and what changes you made during setup etc
Personally, before doing anything;
1. I'd just factory reset,
2. don't install or setup anything (except the very basic setup at first boot),
3. drain tab to around 5/10 %
4. recharge UNINTERRUPTED to Full and
5. immediately unplug.
This will hopefully clean your system and recalibrate the battery (if needed).
6. Lastly, check again before any further setup or installation of apps.
Sent from my GT-I9500 using xda premium
---------- Post added at 07:25 AM ---------- Previous post was at 07:15 AM ----------
A couple of non-root apps apps to try;
* Watchdog Task Manager
* GSam Battery Monitor
Edit: But the time potentially used to track down the culprit could be far greater than my first suggestion
Sent from my GT-I9500 using xda premium
That's the thing. I just got it and I did a factory restore on it right away as the previous owner left all his info on it. All I've really installed is Facebook chrome and a few other basic things. I am using widget locker but I also use it on my S3 without issue. It never enters deep sleep. This is my 5 android device and I've never had this issue.
SumCanadianGuy said:
Today's the thing. I just got it and I did a factory restore in it right away as the previous owner left all his info on it. All I've really installed is Facebook chrome and a few other basic things. I am using widget locker but I also use it on my S3 without issue.
Click to expand...
Click to collapse
Most probably what you've installed setup.....
Remove them and see what happens?
Else, try an app like I posted previously to (maybe help) track down your problem. Otherwise, my first suggestion......
Sent from my GT-I9500 using xda premium
UpInTheAir said:
Most probably what you've installed setup.....
Remove them and see what happens?
Else, try an app like I posted previously to (maybe help) track down your problem. Otherwise, my first suggestion......
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
I had used battery stats plus and cpu spy. Here are some screenshots
Obviously your device isn't going into deep sleep. Leaving the charger connected (once full) will also prevent this, but not usually a huge drain as you described.
There is a wakelock, and you'll need to track it down by trial & error, or, as I suggested, start fresh and work from there ....
Best of luck
Sent from my GT-I9500 using xda premium
UpInTheAir said:
Obviously your device isn't going into deep sleep. Leaving the charger connected (once full) will also prevent this, but not usually a huge drain as you described.
There is a wakelock, and you'll need to track it down by trial & error, or, as I suggested, start fresh and work from there ....
Best of luck
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Much to my dismay I did a complete wipe with no change... Here is my CPU stats with nothing installed except CPU spy in airplane mode unplugged overnight. Lost 30% battery while in airplane mode wifi and Bluetooth off sitting on my table for 7 hours. I went camping last weekend and with my galaxy S3 in airplane mode I lost 12% in 24 hours while using it for music. So this can't be normal....
Please define "complete wipe"? Your steps,?
Did you install anything else other than CPU spy app?
What did you setup/config or install after initial boot?
There will be something you've done (causing the wakelock).
As I said, do nothing after wiping, or just use the CPU spy app and watchdog to see what app is preventing deep sleep. You need to rule things out.
Sent from my GT-I9500 using xda premium
I entered recovery mode and selected wipe data factory reset and rebooted and went through the setup. Downloaded cpu spy, charged to full, put in airplane mode, Unplugged went to bed.
Don't know. Sounds like you have done everything correctly.
The only two things left I can suggest are: the non-root battery calibration (as previously described) and re-flash the latest official firmware with Odin.
There are many guides on how to use Odin, and official firmware can be found at sammobile.com or samsung-updates.com
If you're unfamiliar with Odin, NEVER tick the re-partition box in Odin unless you are using a PIT file. In your case, you don't need a PIT file. There are users here that i have seen "recommend" to do that (maybe even deliberately !?) and doing so most likely will brick your device. So just tick "auto reboot" and "reset time" along with "PDA" (correct device firmware).
Sent from my GT-I9500 using xda premium
Thanks for all your help so far. Maybe I'm better off rooting. I don't need anything fancy. Just a stock based ics or stable jb. Are there any options that can disable the 4g so I don't have to constantly be in airplane mode and also remove the Verizon branding and bloatware?
SumCanadianGuy said:
Thanks for all your help so far. Maybe I'm better off rooting. I don't need anything fancy. Just a stock based ics or stable jb. Are there any options that can disable the 4g so I don't have to constantly be in airplane mode and also remove the Verizon branding and bloatware?
Click to expand...
Click to collapse
No problem.
Just make sure you flash the correct firmware for your device model.
P6800 and P6810 firmware won't work for Verizon.
There may be more info for Verizon in the forums.
Cheers,
UITA
Sent from my GT-I9500 using xda premium
UpInTheAir said:
Don't know. Sounds like you have done everything correctly.
The only two things left I can suggest are: the non-root battery calibration (as previously described) and re-flash the latest official firmware with Odin.
There are many guides on how to use Odin, and official firmware can be found at sammobile.com or samsung-updates.com
If you're unfamiliar with Odin, NEVER tick the re-partition box in Odin unless you are using a PIT file. In your case, you don't need a PIT file. There are users here that i have seen "recommend" to do that (maybe even deliberately !?) and doing so most likely will brick your device. So just tick "auto reboot" and "reset time" along with "PDA" (correct device firmware).
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Here is the latest. During this time period airplane mode was on and 40% battery was lost
if you posses root, installing logcat might reveal the offending prosess.. Install the app - reboot - launch logcat let it run for 5 min, save log and upload here..or try with adb if its familiar.
biopsin said:
if you posses root, installing logcat might reveal the offending prosess.. Install the app - reboot - launch logcat let it run for 5 min, save log and upload here..or try with adb if its familiar.
Click to expand...
Click to collapse
Looks like I might have fixed it. I installed CWM and rooted and did a backup. nstalled Titanium Backup and did a backup of system apps then uninstalled anything related to Verizon, sim card, or phone/dialer the I did a battery calibration. I still dont know if the drainage percentage is what it should be.
Then again maybe not. This is my stats after telling it to keep wifi on during sleep never then switching it back to always.
Here is a log cat file.
SumCanadianGuy said:
Here is a log cat file.
Click to expand...
Click to collapse
Could you kill the exchange app and check deep sleep after 10 min, are you on stock jb?
biopsin said:
Could you kill the exchange app and check deep sleep after 10 min, are you on stock jb?
Click to expand...
Click to collapse
Stock ICS. I think I found the problem, but I'm not sure why. If I leave my wifi on all the time it's fine. I. Went to bed last night with 58% battery remaining after 17 hours on battery. But if I turn wifi of then back on, no deep sleep. It just confuses me that it will deep sleep with wifi on, but not with it off. If I reboot after I toggle wifi it goes back to normal with deep sleep.
I have an o3d that has a battery percentage problem it displays what it wants when it wants. Such as 70% one minute an 5 mins later its gone to 0% and shut down making it useless unless on charge. It is not a bad battery as i have 7 various batterys that work fine in my other o3d. I have tried the battery calibration apps which delete battery stats .bin and big surprise it did nothing. So i used link to sd to freeze power off
.apk and now my phone stays turned on even when at 0%! This does cause a couple of problems though such as going through usual shutdown precedure only reboots phone (i dont mind though this is handy to reboot). If you reboot whilst percentage is low it wont restart without inserting charger. Phone can still be turned off by holding power button for approx 10 seconds. The worst problem is when 0% is reached the status bar usually force closes (which is a real pain using android without status bar). And camera and a few apps wont work as battery is always low but at least i can use phone. I have learnt so much from xda so i thaught i would share this in case it can help someone. Please share if this was helpfull and if you have any tips on how to fix errors caused by this.
Sent from my LG-P920 using xda app-developers app
And also if anyone knows what may be causing my problem in the first place any help would be greatly appreciated. I have already tried a re flash of standard rom and a couple of different custom gb roms. And a custom kernal. I am currently trying to work out how to flash ics to try and fix this properly. I do not know how this problem first occured as i brought this phone off ebay second hand. The problem first occured when this phone was unlocked so i was told. I did notice that even though it was sold as o3d and the sticker on the back confirmed this, that it said p925 in about phone not p920. Not sure if this is related. So again if you have an un-usable phone i hope the above can help you out. And thanks again to anybody that could help fix this once and for all.
Sent from my LG-P920 using xda app-developers app
+1
Sent from my LG-P920 using xda app-developers app
+1