Post your Uptime Records! - Samsung Galaxy Note 10+ Guides, News, & Discussion

This is the place to brag about the longest amount of time you've ever gone without rebooting your Ten Plus. Proof is encouraged, but not required. I'll be rebooting today due to the inability to charge from the Samsung power supply (all others are fine) and to attempt to solve choppiness in playback from Music Choice and Shazam software.
My current uptime today is 2,927 hours.

I don't see the point of doing this. Especially when the system cache can't be cleared without rebooting. I reboot every 1-3 days.
A better mile marker be OS load lifespan. The current load on this heavily used Pie variant will be 2 yo in June. Still fast, stable with minimal maintenance.

blackhawk said:
I don't see the point of doing this. Especially when the system cache can't be cleared without rebooting. I reboot every 1-3 days.
A better mile marker be OS load lifespan. The current load on this heavily used Pie variant will be 2 yo in June. Still fast, stable with minimal maintenance.
Click to expand...
Click to collapse
It's arguably very useful for finding out which stock rom builds are the most stable, and for benchmarking the overall software quality of the device (and even Samsung as a whole). I used to have to reboot my Note 2 every several days because the MC2 stock rom lost its ability to do gravity-based screen rotation. It was infuriating, and part of the reason why I got rid of it. As far as OS "load lifespan," anybody can stay on any build for as long as they want, so I fail to see why this would be relevant.

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

Post your uptime

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).

[Q] Nexus slows down after a week or two.....

All,
I'm currently on the Crossbreed Rom with Franco Kernel. Overall, its a great set up and smooth, until say a week of regular using my phone, I can see it would slow down/lag from switching apps, typing, scrolling and the problem won't fix itself until I reboot. I'm looking at the battery logs and don't see anything unusual, the Android OS is always top then the screen. And again, after a reboot, thing is great until another week or 2 then reboot again. I don't believe I need to reboot all the time.
Any pointers? Could it be an app that is slowing it down?
Thanks for any info!
Well, I usually reboot my phone every now and then. Maybe thats all it takes?
Sent from my Galaxy Nexus using xda premium
You should reboot your phone every week, no big deal.
Try clearing the Dalvik and any very large text message threads.
Shouldn't be happening. Doesn't happen to me on stock.
WiredPirate said:
You should reboot your phone every week, no big deal.
Click to expand...
Click to collapse
Shouldn't at all be necessary, and is not a requirement of owning this (or any) phone.
I agree with martonikaj, we really shouldn't need to reboot every week on our phones.
Nutzzer said:
I agree with martonikaj, we really shouldn't need to reboot every week on our phones.
Click to expand...
Click to collapse
This is a problem with your current setup, as it is not an issue on stock. You need to do some investigation.
I'm not sure if my opinion is going to matter here - but I thought it was good practise to fully drain your devices battery once in a 14 day period - just to keep the calibration fresh.
In saying that - I doubt that this timeline is normal - I saw a comment in another thread that made sense, you have a Windows box, leave it on 24/7 (most of the time in stand-by) but you'll notice it getting slower and slower and the cache builds up and RAM gets chewed and you resolve it by rebooting the machine. It is VERY easy to see that from about 2010, mobile devices ARE pocket sized computers.
It makes sense that you'd have to power cycle every now and then.
shayla28 said:
I'm not sure if my opinion is going to matter here - but I thought it was good practise to fully drain your devices battery once in a 14 day period - just to keep the calibration fresh.
Click to expand...
Click to collapse
This is proven to not be effective, and constantly draining your battery to flat-out 0% can actually damage it.
In saying that - I doubt that this timeline is normal - I saw a comment in another thread that made sense, you have a Windows box, leave it on 24/7 (most of the time in stand-by) but you'll notice it getting slower and slower and the cache builds up and RAM gets chewed and you resolve it by rebooting the machine. It is VERY easy to see that from about 2010, mobile devices ARE pocket sized computers.
It makes sense that you'd have to power cycle every now and then.
Click to expand...
Click to collapse
Not at all necessary on these devices. The windows analogy doesn't really come into play here. I can counter that by pointing to about every single Mac owner (myself included) that will go months on end without shutting down or rebooting the computer with absolutely 0 ill effects.
And if you do "need" to reboot, it should not be as frequent as every two weeks. Especially on a mobile device. Sure, it may be good practice, but should not have to be done out of necessity to keep properly using the phone.
I usually go 3 weeks PR so without rebooting. Around 700 hours of up time or more, and never have slow down issues.
Every option I have available has already been answered here. What I noticed was that when I have very FEW apps installed, the battery stays on for longer and my ICS doesn't slow down at all. I'm running GummyNex with Franco kernel milestone 2. I'm running facebook etc in my browser instead of using the app. I'm using as few apps as possible just to keep it clean.
-Kim
Clear the cache
Sent from my Gnex

Battery problems?

I know, our device has really great battery life and I don't have anything to complain about that, but a friend of mine just got himself a new phone and his values make me a bit jealous and most of all: surprised and stunned.
He got himself a Xiaomi Redmi Note 4 (SD 625 variant, MKT variant really sucks), it has the same processor, same display and not even 700 mAh more (4100 mAh) and he got with some "dev rom" (made by Xiaomi, seems to just be the beta of that ugly MIUI 9, based on Andorid 7.0) 6h of SOT, doze seems to haven't really kicked in in that time. in their forum in the SOT thread I see people getting normally about 8-10 with up to over 12 h of SOT, most of them on stock ROM without any additions. And I'm quite irritated about that huge of a difference with not that much more battery. And he seems quite convinced that it's not on the cost of performance, you should notice that quickly on such a heavily skinned ROM.
Now my question is: how in hell is that even possible? I mean our devices seem quite comparablewith just a slight bump in battery but near-stock AOSP Android against pretty much an iOS clone. Does anyone have any idea what could cause that big of a difference? And if it's software based could that be done on our device? Because my experience and from different posts our device lasts about 5-6 h normally.
I mean I'm already lucky about my 2 days of usage with up to about 2.5 days on some weekends where I have a lot of stuff to do. But I wouldn't mind a bit of extra. But my biggest problem with that is as simple as: how? I could really use some explaination right now...
I don't have issues with device.. stock 7.1.1 with dec.patch, unlocked bootloader, with latest magisk. Also installed greenify.
Then you are one of very rare cases. My experience is about half of that.
And I also meant on stock ROM, without any modifications. So I don't know which apps you greenified, but that was not the point. I use Greenify too but more for apps that aren't supposed to run constantly in background when I only use it very seldomly.
The norm for this phone is 8+ hours SOT. Sometimes I get 10 and a few have had up to 12. Unless you're gaming 8 should be easy. 5 hours means something is wrong with your phone hardware, you have a rogue battery eating app or you're gaming. I rarely charge my phone over the weekend even when I use it a lot.
Well, neither of that is the case and I rarely see people claiming more than 6h of SOT
So the answer to your question is, it's the wrong question. The question should be, why does my battery not last very long and what apps or usage causes me to have such poor battery life? Compared to the Redmi Note 4 the Z Play is exactly where it should be.
Here's a link to the SOT thread: https://forum.xda-developers.com/moto-z-play/review/screen-time-t3643959
gsmarena battery life test 100h endurance rating: https://www.gsmarena.com/battery-test.php3?idPhone=8310#show
Here's an app to help diagnose battery condition (Accubattery): https://play.google.com/store/apps/details?id=com.digibites.accubattery&hl=en
also betterbatterystats is really helpful.
I sincerely hope you get it sorted out!
Well, gsam isn't detecting any app that's off even with root so I don't think there is any. I installed that AccuBattery app, let's see what it has to say
Removed because of ****ty q&a system...
Oh, and another thing I noticed: I get very randomly reboots, and every time the battery percentage drops massively. Just had a 30% drop. And after the reboot the battery percentage seems like frozen. Now I rebooted and plugged in the cable and got 44% again... No fast charging. Do that detection seems very off
Motorola forum isn't helpful at all. Clearing cache and dalvik didn't change anything and running around for a week in secure mode (that's how random they mostly are) or even doing a factory reset without restoring apps is out of question for obvious reasons.
That's pretty weird. Did you try a factory reset and after restore your apps? There's not a lot you can do if you're not rooted, but you shouldn't need to do much anyway on stock rom.
Only other option is full RSD lite OS restore as a last resort.
I am rooted for long, that's why I use Greenify. I know it also works without but then it's a joke. As RSD lite is, it just refuses for everyone to detect anything on Windows 10.
Factory reset is out of question for the moment, it takes way too long to do it properly (with titanium and NANDroid backup first) and I won't have that much time probably for the whole of this month. Otherwise I would most likely already have went off to the next best custom ROM since Motorola just can't get their **** together and still work on 8.0 in test for 2.5 month with searching testers for another one.
I think the next thing I'll do is to try the good old battery calibration, just have to find the file storing the statistics. I know many say that won't work but that's rubbish, it worked for me already a few times
Update: no, no change. Don't know if that funky battery percentage bug on random reboots still happen since I haven't had any again yet, but they come too random and unpredictable.
And that AccuBattery just proves to be worthless. It tries to estimate the rest capacity, but then it even fails to detect original capacity by 500 mAh. The battery sucker stats are also unrealistic. It puts chrome first with 10%, while GSam with root puts it 5th at 4.6% after kernel, Spotify, Android system and fight services. Android itself even puts it 9th with screen, phone idle, cell standby, Android OS and Bluetooth in-between.
So let's see what happens first. Motorola releasing 8.0, which I will flash through the .xml.zip, this time using flashfile.xml which should force a factory reset... Or me finding the time to switch to a custom ROM
Edit: so I got another one, bit this time no crazy battery drop. But the other times I killed of the soft reboot sequence because Magisk can have some problems with that. This time I didn't
Yesterday I was finally able to do the factory reset since those darn random reboots became too annoying and Moto's support is had just the most ridiculous ideas... In the worst way.
Either way, now OTA looks better, let's see how it will turn out in the next days

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