Post your uptime - Samsung Galaxy Nexus

I have made a concerted effort to not reboot my phone for any reason so I can try to get an idea of if there are any performance differences in the phone after it being on without a reboot for an extended period of time. Some phones I've had in the past (such as the Sensation) would slow down after about 5 days of uptime, while other phones rarely could make it 5 days of uptime due to random reboots. Since I've decided to see how much uptime I could get on this phone without any performance differences, I've gotten to 150 hours. I haven't noticed any performance differences at all, and I have to say I am happy with the results thus far. What's your uptime, and have you noticed any changes in performance with longer uptime?

On my nexus one I regularly got up to 450 hours of up time with zero issues. After a while I just ignored the test as it could go for over a month. I made a thread and all with lots of responses.
I'd guess that this galaxy nexus will be even better by far. They really seemed to have got android mature and stable.

At present 263:27:25

Scottatron said:
At present 263:27:25
Click to expand...
Click to collapse
I'm assuming you haven't experienced any performance differences either?

Nope, haven't noticed any slow downs / issues.

My buddy hasn't rebooted since we got our GSM versions.. I actually used his uptime to figure out how long I've had the phone haha, he's at 648 hours and still chugging along

I'd be surprised if I made it past 48 hours any time soon with all these sweet kernels and ROMs to play with.

It's very encouraging to hear so many long uptimes with no performance slowdown. It's also great because the long uptimes are a testament to how stable the phone is. The only time I've had a crash was when I installed something on the phone that didn't seem to play nice with ICS (can't remember which app it was).

Related

big mistake updating to 2.2

ever since I updated to 2.2, no matter what rom I'm using..performance has been so poor compared to 2.1. I wish I never updated. My battery runs out quick, temperature goes up to 100F even when idle and my phone hangs every time I turn on wifi. Hopefully I find out a solution soon, i've been flashing and uninstalling roms all day these past two days. I love the phone though don't get me wrong =\
That sounds quite odd.
Are you using an unmodified SBF, or are you using a release where the author/publisher has made a lot of changes? When having problems, it may be best to stick to one release and try to narrow down your problems, instead of trying many different releases and introducing new variables into the mix.
Are you overclocking your phone - perhaps it's causing the rise in temperature? Or are you running a lot of widgets? There may be some widgets that use the system too aggressively, causing too much strain/heat.
Hi! Did you do "wipe" before and after flashing?
That is very odd. I am on Froyo and performance has been phenomenal ever since the flash.
I agree with naenee, check the ROM you're flashing...
i flashed the UK 3.4.2-117 and right now using Pay's 2.1 rom. I remember that I did wipe data/cache before flashing and after flashing. IDK, im just not having problem's with this particular rom..it seems like it happens on all the other ones im trying. I get random freezes and especially when I toggle on wifi. I recently installed setVEL and will see if battery improves, this means i don't need milestone right? I'm also using setCPU.
I might try to flash 3.4.2_131-003 PL version. Will it cause any trouble and can I go back down to UK 3.4.2-117?
Seeing as it uses the same kernel, you should be able to do so...
bkuu said:
I might try to flash 3.4.2_131-003 PL version. Will it cause any trouble and can I go back down to UK 3.4.2-117?
Click to expand...
Click to collapse
I have been using the orange 2.2 for several days and no specific problem is noted.
well I reinstalled pays rom first and everything is working good. No more hang ups or freezes but I still can't get the battery to last as long.My phone is mostly idled, running on 2G, just one widget, and everything in settings turned down to the least minimal settings..im talking about battery saver, screen brightness all the way down..everything off! 6 hours in and im already on 70%. I can live with that but I'm using setVsel and I know it could do better. Anyone know another way I can make my battery last longer?
I'm running Pays latest rom based on the UK 3.4.2 and it runs great. I'm also using setvsel (as every defy user should) and optimized all my vsels ([email protected], [email protected], [email protected]) using stability test. I haven't had a 'normal' day of use yet, but with heavy use (installing apps, web browsing, flashing rom) I've gotten at least a full day (~15 hrs) out of a charge.
I recommend minimizing your vsels using setvsel, then judging your battery life. Check out the setvsel thread for more help.
Sent from my MB525 using XDA App
And remember this is a smart phone, some people report getting 2 to 3 days of use out of it. That's basically idle time tho. These new smart phones are just that, and use much more battery than the Dumbphone.
Dewman4life said:
And remember this is a smart phone, some people report getting 2 to 3 days of use out of it. That's basically idle time tho. These new smart phones are just that, and use much more battery than the Dumbphone.
Click to expand...
Click to collapse
Even if that's the case (and I dispute it, I use my phone a fair amount in the ~3 days the battery averages), it still doesn't explain why the OP's phone is dropping 30% in 6 hours while idling.
When I updated to froyo, my battery life went from about 15 hours of use to 21 hours between charges. So I'm thinking the op has an app doing the draining.
Sent from my MB525 using XDA App
Unfortunately, this is a characteristic of Android.... Ridiculously inconsistent in the battery department.
Wife's phone is on official froyo, has been amazing since updated (a few weeks ago) but since yesterday some weird reason it's been super glitchy and freezing up. Not sure why...haven't changed anything to it and she's only downloaded an app or two (such as pandora) in the last couple days...I was playing around with it trying to figure out what was up...can't figure it out. I went into titanium backup to freeze some apps thinking maybe some blur crap was freezing it up but TB froze up so I can't even get in there. Also, same as OP, the battery has been heating up really quick lately, especially when on wifi.
Not sure what's up here...but I'm hoping nothing serious! Will keep you all updated on this...we'll see if there is a trend going on here.
bkuu said:
ever since I updated to 2.2, no matter what rom I'm using..performance has been so poor compared to 2.1. I wish I never updated. My battery runs out quick, temperature goes up to 100F even when idle and my phone hangs every time I turn on wifi. Hopefully I find out a solution soon, i've been flashing and uninstalling roms all day these past two days. I love the phone though don't get me wrong =\
Click to expand...
Click to collapse
check your cpu usage... if it's constantly arround 99%, you may experience the "usb-plug/unplug"-bug.
try enabling usb debug and restart your phone.
hah2110 said:
Unfortunately, this is a characteristic of Android.... Ridiculously inconsistent in the battery department.
Click to expand...
Click to collapse
I would rather say it is a characteristic of people using android, to have widely different usage patterns, causing differences in how long a charge lasts for each.
Hi there. Have you tried to recalibrate the battery? There is an app on the marke called Battery Calibrator. From what I understand if you play with roms the battery can give you problems so it need to be calibrated again. I hope this can help.
For those interested... I'm having a problem, I don't know yet if it's a bug or a hardware defect.
My phones wastes A LOT of battery while it should be suspended.
I've tracked the problem to, apparently, Motorola's SIM driver. From what I've discovered so far, the SIM isn't accepting the suspend state and therefore the "suspend" process uses too much CPU time... all of this when the phone is, supposedly, saving battery.
As I can't get a motorola engineer involved, I can't say for sure if this is the true cause... but it's the closer I've got to a diagnostic, so far.
Your problem might or not be related to this, but if you're interested about what I've found or what my kernel log looks like so you can compare with your own problem... this is the thread at motorola's owner forum:
https://supportforums.motorola.com/thread/47721

[Q] JB Development Status and Bugs

So, I've been running JB for almost 2 days now. As far as I'm concerned battery life is great, speed is awesome, I had no FC or crashes of any kind, I found no particular evidence of this being a development build.
I sincerely don't think that 15 days from now JB is going to be any different from this. Heck, 15 days may only be the time it takes for Google to pack the OTA for all the variants and prepare its servers to push it to millions of phones.
But that's just my thought. Has any of you encountered bugs that are associated to the "development/preview" status of JB?
Like Apple GMs, they leak 2 weeks before and 99% of the time it's the same build that gets released.
Let's share some thoughts
PS: I'm asking this also because there are many people here saying "don't complain about development builds". That is true, one should not complain about dev builds, but it's also true that 15 days can't be enough to solve every bug in the world
Iam using it as daily driver, i thinks its great. I also think the ota we get will be even better, maybe a better kernel, there is one bug happening to me as i am typing, ironicly lol.
Does not happen all the time though.
Sent from my Galaxy Nexus using xda premium
as far as I'm concerned this is totally amazing and I really love it so I use it as a daily driver and I think the final version will not be different from this . however battery life is not good for me but maybe that's because I'm using too much the phone he he
Sent from my Galaxy Nexus using xda app-developers app
First I notice is after I flash jb I can't see media (photo/videos) in gallery.. but fixed after a new flash without clearing DATA..
Second is I can't connect sixaxis controller..
Sent from my Galaxy Nexus using XDA Premium App
My GPS is not working. Everything else is great.
Sent from my Galaxy Nexus using xda premium
You're entirely right. Less then a month out from deployment this is clearly a release candidate. If their final release has any differences they will be very minor.
Stability in JB is top notch. Not a single app crash.
However, my battery drain is about 3x more than normal, especially on standby. My phone's been getting hot and that rarely happens with regular use (non-gaming activities).
And the NFC kernal wakelock is on and quite active, even with NFC disabled...
EP2008 said:
Stability in JB is top notch. Not a single app crash.
However, my battery drain is about 3x more than normal, especially on standby. My phone's been getting hot and that rarely happens with regular use (non-gaming activities).
And the NFC kernal wakelock is on and quite active, even with NFC disabled...
Click to expand...
Click to collapse
I have to say that my Nexus is getting hotter than usual when using it intensively, unlike ICS. Still, battery drain on standby is the same (if not less) than ICS, about 3-5% every 6 hours.
However, while it gets hot during normal use, battery drain seems pretty similar to 4.0.4.
I think it may be due to Project Butter making the GPU work harder, thus warming up the phone. OR, since it gets hot near the top of the device, it may be the new radio being set to a higher wifi/3g transmit power setting.
As far as the OS goes, after a couple more days of use, I'd be surprised if the final version turns out not to be JRN84D
Camazza said:
PS: I'm asking this also because there are many people here saying "don't complain about development builds". That is true, one should not complain about dev builds, but it's also true that 15 days can't be enough to solve every bug in the world
Click to expand...
Click to collapse
Well it depends when this build that was put on the I/O Nexii was finished. It could have been finalized a couple weeks ago and there are other things since then that'll be coming in the official OTA.
I'd be surprised if there were large glaring bugs with WiFi, GPS, and UI elements on the official release. You're right they probably can't change anything major, but they've got a few weeks to tweak small things. Not to mention that they can easily follow up with a bugfix OTA a month after it comes out if needed. Remember the GSM models got 4.0.2 and 4.0.4 in relatively quick succession.

CM10 Performance

I've been running the 9/15 nightly, and while I haven't had excellent battery life, it has typically lasted around 8 hours or more. Today was a little different; with only an hour of screen time, my battery was down to 30%. On top of that, it usually takes 3 or 4 presses of the home button to wake my phone up.
EDIT: I forgot to add that my screen usage usually accounts for 60%, or more, of my battery usage--and that's with minimal usage. It always seemed like my screen was draining the battery even when it was off. It is much less now.
I read on the forums that a simple increase of the minimum frequency can resolve the waking issue. However, it didn't; instead, my battery life improved dramatically. I'm used to a pretty jagged and sharp battery graph, but now it's as smooth and linear as I have ever seen it.
Can anyone explain why raising the min freq improved my battery life?
Sent from my SAMSUNG-SGH-I747 using xda premium
Why don't you update? Its Oct 5th. Maybe give that a try? Old build man.
Well, I've considered it, but I always check the main thread first. It always seems like people are having LTE or GPS issues with the new build. Everything, aside from the battery life and screen waking, has been working exceptionally well. Not to mention, school and work hasn't given me enough free time to experiment with the new builds. I might try this tonight though.
Sent from my SAMSUNG-SGH-I747 using xda premium
DStevens5833 said:
Well, I've considered it, but I always check the main thread first. It always seems like people are having LTE or GPS issues with the new build. Everything, aside from the battery life and screen waking, has been working exceptionally well. Not to mention, school and work hasn't given me enough free time to experiment with the new builds. I might try this tonight though.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
The rom actually updates EVERY DAY you have missed many many updates here is a changelog http://changelog.bbqdroid.org/#d2att/cm10/1349329973
well all devices are not created equal. i suppose its possible that the ideal minimum frequency for your device is a above stock (or whatever you had it at before). raising the minimum frequency can improve cell connection, screen flickering issues, ect (things that cause battery drain).
also i advise you to update your cm build. either that or switch to cm monthly or another rom that doesn't push out critical updates every night. Try a rom that is considered stable like liquidsmooth, slimbean..
On the Oct 3 build and it's very fast. Batter life has been quite bad, have to charge it twice a day. Had a lot of crashing yesterday, phone decided to reboot continuously. Apollo has stopped error persisted until I cleared cache, and keep getting email/exchange devices have stopped errors until I disabled email.
Battery is the only thing that really bugs me though
Not sent from my toilet with a soap bar.
@nccu_eagles & @jefferson9: To be honest, I never realized the minimum frequency affected so many different elements outside of power saving. I admit I haven't kept it up-to-date; I'm always afraid to update after seeing some of the bugs people post. Perhaps I would be better off with a more stable release--at least until the semester is over, which will leave me with much more time to dabble. If I finish my homework in time, I might try a few different roms tonight.
@adammur: Those are the type of bugs that keep me from updating.
On another note, today's battery life has been great. My battery would normally drain between 12-20% an hour. Today, I'm averaging 5% an hour with similar usage. :good: Anyways, thank you guys for the replies. I'll see if I can't find something to better suit me.... for now :fingers-crossed:.
Before playing with the TouchWiz Jellybean Milestone 5 (Firefly) ROM by Drew Garen, I was running the JellyBro's euroskank October 3rd nightly along with LeanKernel as well as JuiceDefender Ultimate...
My Galaxy S3 could literally last 2 days with that setup. It was UNREAL.
The problem is, I really actually do like the TouchWiz interface (I know I know, I'm one of the few).
But if ultimate battery life is your goal with the Samsung Galaxy S3... Do a factory reset / cache wipe and install the Oct 3rd version of JellyBro's euroskank for the d2att... Then go ahead and install yourself the tmobile / AT&T version of leankernel...
You WILL NOT be sorry!
DStevens5833 said:
I've been running the 9/15 nightly, and while I haven't had excellent battery life, it has typically lasted around 8 hours or more. Today was a little different; with only an hour of screen time, my battery was down to 30%. On top of that, it usually takes 3 or 4 presses of the home button to wake my phone up.
EDIT: I forgot to add that my screen usage usually accounts for 60%, or more, of my battery usage--and that's with minimal usage. It always seemed like my screen was draining the battery even when it was off. It is much less now.
I read on the forums that a simple increase of the minimum frequency can resolve the waking issue. However, it didn't; instead, my battery life improved dramatically. I'm used to a pretty jagged and sharp battery graph, but now it's as smooth and linear as I have ever seen it.
Can anyone explain why raising the min freq improved my battery life?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
What did you increase it to, if you don't mind me asking?
I normally use up-to-the-moment builds (downloading 10/07 ad I write) and my battery life has been reasonable - up to two days total with light use. Seems to me to be a matter of making sure you're not running too many (any?) battery-hogging apps (BetterBatteryStats has been enormously helpful in this respect).
Unfortunately, I was unable to play with anything last night due to homework. I did, however, purchase and install BBS and JD. I'm actually at work right now, so I can't really post much other than a few screenshots.
Sent from my SAMSUNG-SGH-I747 using xda premium
Cuddlesy said:
What did you increase it to, if you don't mind me asking?
Click to expand...
Click to collapse
I increased it from 384 to 486. So far it seems to have helped a lot. I'm actually about to try a couple different ROMs and see how they go. Wish me luck :cyclops:
dpav02 said:
The problem is, I really actually do like the TouchWiz interface (I know I know, I'm one of the few).
Click to expand...
Click to collapse
You are not alone, I enjoy the functions/features of the OTA ROMs.
Notification accessible when in full screen apps, the multi-window screen lets you "clear all" and access task manager&Google Now, the stock dialer has more efficient functions(Displays all calls from a contact if selected, slide right/left to call/send sms)
But going back on topic, I set my cpu to be conservative but I'm not sure if that'll save battery.
I want to be able to game when at work but not have the power-saving setting limit it yet still be able to last me a day. The OTA ROMs' power-saving feature was able to do that.

Phone seems generally smoother after October Security Update to me

So after nearly giving up in this phone after it being almost unusable between March -August ish... I found that the September update made it pretty good again...
And have had the October Security Update (and bug fixes it says) for a few days now, and I feel like this phone is back to how good it was when I first got it smoothness wise.
Liking it again, came so close to buying a pixel, but will save myself a few hundred quid and stay with this. I was also looking at putting on the Pixel Experience ROM, and may still do in the future, but the way the phone is now it feels fine as it is.
Anybody else think it has improved a lot the last 2 updates ?
I think it comes and goes. The other day I had a game stay in memory for over 4 hours despite using other apps, including a browser.
But the phone had only been running for a day at that point. It's generally closer to a week of uptime before things get really bad for me, but sometimes as short as 2 days.
If I reboot in the morning it's fine all day. I've been doing that a bit lately as a bit of pre-emptive maintenance...
These security updates will surely stop soon and then I'll jump onto a custom ROM. Or maybe get a Pixel 4a. But this phone is still fine when it's not killing apps randomly
Is it still running smooth at this time? Without restarting it?
I strongly disagree. My device still begs me to restart it after more than 24h of use.
No, laggy after about 10 hours of uptime.
I'm selling mine today. Shame about this, it was perfect phone for price. I will use Redmi S2 for now and buy Pixel 4a when prices drop.

Question Phone Overheating - Is There a Fix?

I'm on Android 13 and was hoping this would sort out the overheating problem I had with Android 12 (I read in a few places that it would), but it did not. The phone gets very warm when charging, and hot when streaming video, and just generally through simple use, nothing particularly demanding. I haven't rooted this phone because I did not see the need, but I would consider it if it was the only way to fix the problem. Is anyone experiencing the same, and does anyone have a solution?
I could be wrong but generally speaking in my experience, going from one major upgrade to another the phone works a bit harder to re-train itself to your use patterns. I just did my upgrade yesterday and experienced some slight to moderate heat as well. I also noticed that battery is draining a bit faster which I think again is part of the process. I'm going to give it a week or so and if I'm right it should improve.
I'm biased because I've had my Pixel 6 Pro rooted (and updated every month) since last November, and I also use Kirisakura custom kernel with its companion apps and currently have the one app set to the maximum battery savings.
So I can't really compare to 100% stock unrooted with the stock kernel, as I'm only briefly on the stock unrooted kernel each month after I manually flash the latest update.
Several others have commented, and I've experienced too, that with Android 13, we've no longer experienced as severe higher temperatures when charging. I don't remember if the others were rooted and using the same custom kernel, or if these were general Android 13 comments, so your mileage may vary. Sorry I can't give you any more concrete information.
Good luck!
Granted this is for my 4a5g but I wouln't be suprised if/when I get a 6 that its battery performance would be less than stellar after a good days use of phone and/or screen and radio/network. i.e. stock. Before I went to Lineage on my 4a5g I think my battery would cut a good 30-50+ percent each day. I put lineage on it and I poop you not, can go from a 75% to around 20% in about 5-6+ days. I tend to have my screen brightness around a little less than 1/4th on the slider bar.
When I had an HTC M8, after around 2 or so years (this was around 2016/7 or so. got phone oct '14) on the stock firmware the phone couln't keep it on for more than a day. Ran ViperRom for a bit then switched to cm/lineage and that stretched my usability of the phone another 5 years. It got to the point where the phone would shut off when it got to around %50 charge and go ding dong and turn off--without pluggin it in I had about 8 hours run time on it. My battery was beyond gone and no way would I have gotten that usability on the stock rom.
So, to answer your question, yes, trying different roms and kernels (rooting) could be to your advantage to prolong the life and performance of your phone.
Even if you choose to run the stock OS, with root, you could disble any bloat running in background. Kill any programs/services leeching CPU (and hence battery) cycles. You could definately make it run more efficient for YOU. Maybe not for the next guy who needs his facebook, twitter, ticktok apis and stuff loaded and at the ready. Everyone is different. But they tend to make the phones (they think) for everyone. in mind and as a result, device performance and lifespan become affected.
I definitely have heating issues and this is on a warranty exchange. The 2 previous P6Ps had all the same issues as this current device.
My phone was hot on A12 (41/45°) and since i clean flashed A13 and wiped it is cold (32/35°) for the same usage.
Greetings.
Good topic.
I have bought this phone a day before. I'm facing device heating even under simple tasks like scrolling messengers, browsing etc.
Previously I had OnePlus 7 Pro (Snapdragon 855), that one was cold all time except while charging or playing games.
However, Pixel looks warm or even hot even upon light using.
I'm a bit confused about that.
Is it a common problem of this device? Or probably exactly my device is affected?
I haven't faced overheating or alerts about that, however, it feels hot for my hands that got used to feel a cold phone while low load.
Currently, I have about 37-38 degrees while browsing on XDA and writing this post.
Just wondering that digits you have?
I did a warranty exchange on my P6P for a different issue and I'm glad I did. My replacement device has much better thermals than my original. My original one would get quite hot while charging and restoring apps and was almost uncomfortable to hold and to the touch. Could always try a warranty exchange and see if the replacement device is better for you. Also, Kiri kernel has been reported to help with the thermals. I've seen several reports of users commenting that their device runs cooler. Good luck!
I had heating issues and battery issues when I first received my P6P. Once I got it out of the box, I set it up and restored backups, rooted it, updated to android 13 without wiping, rooted again, and then flashed the Kirisakura kernel. I decided to try and flash android 13 again but keeping the -w flag to wipe userdata and didnt restore my backups and I've had amazing battery life and no overheating. If you haven't yet, try doing a factory reset. As simple as it sounds it may very well help
My fully stock P6P (on A12) gave an overheat warning yesterday while we were having a day out, it was only 22°C although we were in and out of the sun as the clouds rolled by but the phone was showing 46°C after being sat in my pocket.
I think Google have released the worlds hottest running phone, i have never owned a phone that heats up so much and so fast.
MrBelter said:
I think Google have released the worlds hottest running phone, i have never owned a phone that heats up so much and so fast.
Click to expand...
Click to collapse
Try OnePlus 9 Pro
darkness4every1 said:
Try OnePlus 9 Pro
Click to expand...
Click to collapse
Thing is I have never experienced overheating on any phone (that i have owned) in UK before, using an Exynos as the basis of Tensor and then whacking an extra big core in it was a pretty bad idea unless you live in a fridge.

Categories

Resources