Related
Just noticed this when playing with LG cam app and stock cam app.
If you want to test it yourself, do the following:
1. reboot the phone.
2. use it for a while but DO NOT open camera app.
3. goto Settings > About Phone > Battery Use
4. notice there are NO camera listed.
5. now open and close camera app (stock or LG doesn't matter, no need to take pictures or video)
6. use it again for a while
7. go back to Settings > About Phone > Battery Use
8 notice the camera app is listed and battery use is WAY HIGHER than all other apps/system components.
9. Also notice that the camera is warmer than before.
This means the camera is NOT COMPLETELY off when you close the camera app. This probably one of the source of over-heating.
ROM version at the time of this post:
Updated from froyo to GB through LG update tool without any problem.
Flashed xboarder56's rooted GB ROM through CWM.
I'm not convinced. The camera probably draws more battery because it's an extra doohicky. Duh, you activate another part of the phone and it draws more battery. But I'm thinking that the camera probably draws a little more. I also read (sorry, can't source it) that the modem is in that general area as well. The combined draw might be enough to explain the heat gain. And in the battery drain screen, does the drain remain over time? If the camera/battery usage persists over a longer duration, then there is for sure a problem. But I'd guess that with time the percentages will drop to expected levels. I'd think a similar situation would occur with memory. Recording high-def video ain't easy. Even if the phone isn't actually recording video I'll bet it's reserving enough memory so that it can without stuttering.
All of this is pure speculation, I have nothing to back it up..
adampdx said:
I'm not convinced. The camera probably draws more battery because it's an extra doohicky. Duh, you activate another part of the phone and it draws more battery. But I'm thinking that the camera probably draws a little more. I also read (sorry, can't source it) that the modem is in that general area as well. The combined draw might be enough to explain the heat gain. And in the battery drain screen, does the drain remain over time? If the camera/battery usage persists over a longer duration, then there is for sure a problem. But I'd guess that with time the percentages will drop to expected levels. I'd think a similar situation would occur with memory. Recording high-def video ain't easy. Even if the phone isn't actually recording video I'll bet it's reserving enough memory so that it can without stuttering.
All of this is pure speculation, I have nothing to back it up..
Click to expand...
Click to collapse
I hope you read my post again.
It's not about camera draining battery when taking pictures/video. It's opposite: drianing battery when you are NOT using camera: i.e. camera app is closed.
Since people are not convinced, I'll change the test procedure to this:
1. reboot the phone.
2. leave your phone IDLE. DO NOT use it for 5 minutes.
3. goto Settings > About Phone > Battery Use
4. notice there are NO camera listed.
5. now OPEN and CLOSE (use task killer) camera app (stock or LG doesn't matter, no need to take pictures or video)
6. leave your phone IDLE. DO NOT use it for 5 minutes.
7. go back to Settings > About Phone > Battery Use
8. notice the camera app is listed and battery use is WAY HIGHER than all other apps/system components.
9. Also notice that the camera is warmer than before.
OK, following instructions and currently running EB 2.3.3 1.6.
1. Rebooted phone.
2. Started Camera app and pushed back twice to close the app.
3. Verified with Android running processes and Taskiller Free that camera has been nullified.
4. Waited 5 minutes.
Results: Right after I closed the camera app I saw that it had used 2% of total battery. After 5 minutes camera is at 21% usage and climbing. Heating...negligible. But after a few more minutes that could easily change. Just checked again as I write and we're up to 24% usage.
By Jove, I think you're on to something. Sorry for doubting. What now?
adampdx said:
OK, following instructions and currently running EB 2.3.3 1.6.
1. Rebooted phone.
2. Started Camera app and pushed back twice to close the app.
3. Verified with Android running processes and Taskiller Free that camera has been nullified.
4. Waited 5 minutes.
Results: Right after I closed the camera app I saw that it had used 2% of total battery. After 5 minutes camera is at 21% usage and climbing. Heating...negligible. But after a few more minutes that could easily change. Just checked again as I write and we're up to 24% usage.
By Jove, I think you're on to something. Sorry for doubting. What now?
Click to expand...
Click to collapse
I'm no dev but I know if anything seems unusual.
We can do nothing other than hoping incompetent LG software engineers acknowledge this problem.(just acknowledge, not solving)
edit: I think we can do a comparison of the battery drain.
it might be that i'm just lucky. i tried your steps. closed camera after testing it. then killed the process using absolute system root. camera doesn't even show up for me under battery use. ??? even if i keep the camera running for a few minutes. plus, i was outside today recording my boy out in the yard for 15-20 minutes. never noticed anything odd about my battery use. running eaglesblood 1.0.6 and the lg cam ver.1.2 ported for gb 2.3.3. not calling out the op. just sayin.
crazythunder said:
it might be that i'm just lucky. i tried your steps. closed camera after testing it. then killed the process using absolute system root. camera doesn't even show up for me under battery use. ??? even if i keep the camera running for a few minutes. plus, i was outside today recording my boy out in the yard for 15-20 minutes. never noticed anything odd about my battery use. running eaglesblood 1.0.6 and the lg cam ver.1.2 ported for gb 2.3.3. not calling out the op. just sayin.
Click to expand...
Click to collapse
Depends on whether you rebooted or not.
rebooting clears the battery use statistics since last reboot. Makes it easier to see which app is draining battery.
Yes, I noticed this the other day. It got me worried thinking I had been hacked and a program was accessing my camera. Any way, I think it was fast reboot I used and then the camera usage was no longer on my battery stats. I'm not sure but I'll try it again and see.
richteralan said:
Depends on whether you rebooted or not.
rebooting clears the battery use statistics since last reboot. Makes it easier to see which app is draining battery.
Click to expand...
Click to collapse
i said i tried your steps,meaning, i followed instructions. but you can't say that this is happening to everyone. there are too many variables involved,different roms,software etc.
while i'm sure it is happening to you, it's not happening to everyone. and judging by the lack of responses here, i'd assume it's not happening to most. only time will tell.
My battery usage has continued. Now I'm at 45% but its been a while and other things have been running as well. Very strange. Anyone notice this on any Froyo ROMs?
Just checked, no issue here..
crazythunder said:
i said i tried your steps,meaning, i followed instructions. but you can't say that this is happening to everyone. there are too many variables involved,different roms,software etc.
while i'm sure it is happening to you, it's not happening to everyone. and judging by the lack of responses here, i'd assume it's not happening to most. only time will tell.
Click to expand...
Click to collapse
Would you mind telling me what ROM/Kernel you have?
p.s. I'm on rooted stock GB update.
crazythunder said:
it might be that i'm just lucky. i tried your steps. closed camera after testing it. then killed the process using absolute system root. camera doesn't even show up for me under battery use. ??? even if i keep the camera running for a few minutes. plus, i was outside today recording my boy out in the yard for 15-20 minutes. never noticed anything odd about my battery use. running eaglesblood 1.0.6 and the lg cam ver.1.2 ported for gb 2.3.3. not calling out the op. just sayin.
Click to expand...
Click to collapse
But you manually killed the camera all. That's not what the test was. And voids any useful info. You shouldn't have to manually close the camera app.
Sent from my LG-P999 using XDA Premium App
eaglesblood 1.0.6 , no custom kernel.
i've had my g2x from day 1. battery was never really an issue for me. call tmo and complain about your situation. they'll probably send you a new battery and let you keep the old one.
eagle1967 said:
But you manually killed the camera all. That's not what the test was. And voids any useful info. You shouldn't have to manually close the camera app.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
5. now OPEN and CLOSE (use task killer) camera app (stock or LG doesn't matter, no need to take pictures or video)
i know how to read
crazythunder said:
eaglesblood 1.0.6 , no custom kernel.
i've had my g2x from day 1. battery was never really an issue for me. call tmo and complain about your situation. they'll probably send you a new battery and let you keep the old one.
Click to expand...
Click to collapse
I don't know but you seem like to assume a lot.
I haven't got any problem with my g2x and I do not plan to complain just to get some stuff for free.
If these kind of thread bothers you too much, I suggest you ignore me.
richteralan said:
I don't know but you seem like to assume a lot.
I haven't got any problem with my g2x and I do not plan to complain just to get some stuff for free.
If these kind of thread bothers you too much, I suggest you ignore me.
Click to expand...
Click to collapse
put some of that college education to use and realize i was trying to help. wtf
noone was telling you to scam anyone out of anything. lighten up. go have a drink. or get laid or something. that's what i get for suggesting you might have a legitimate battery issue. tell you what....i hope it explodes on you now and battery acid oozes out of your screen, causing it to be useless. then YOU cannot post your myths here anymore. have a great day.....dude
crazythunder said:
put some of that college education to use and realize i was trying to help. wtf
noone was telling you to scam anyone out of anything. lighten up. go have a drink. or get laid or something. that's what i get for suggesting you might have a legitimate battery issue. tell you what....i hope it explodes on you now and battery acid oozes out of your screen, causing it to be useless. then YOU cannot post your myths here anymore. have a great day.....dude
Click to expand...
Click to collapse
I guess you failed to read my first line in my first post.
My G2x battery is fine since froyo. Thanks for asking.
And for the rest of your post, I guess you think either it's funny or make me rage.
Well, I did both, cookie for you?
richteralan said:
I guess you failed to read my first line in my first post.
My G2x battery is fine since froyo. Thanks for asking.
And for the rest of your post, I guess you think either it's funny or make me rage.
Well, I did both, cookie for you?
Click to expand...
Click to collapse
well you're a horrible troubleshooter then.
and, the most interesting man in the world does not eat cookies.
My Charge has seen decreasing performance. I'm running 2.3.6, the last TBH leak, and I was initially getting Quadrant scores as high as the 1400's. Now, I'm down around 700! Needless to say, the phone has gotten laggy.
I'm using OSMonitor to look at what processes are busy, and I keep seeing k3g_wq running, using anywhere from 20% to just under 40%. Never used to see it before. I figure it's a system process, as if I kill it, it starts back right away and always has the PID of 54.
I've searched here and with Google and I can't find anything about what this process is. From the name, I might guess it has something to do with 3g access, but it's running like that even when I go into airplane mode.
Thanks for any info.
just a suggestion but since GB has officially been released i would wipe cashe,dalvik and data. Then flash infinity, tweak stock or danalo's stock debloated/deoxided rom. Then flash imoseyon's repacked voodoo kernel. you will get a quadrant score of around 2000. Im currently running infinity ext4 without tsm, imoseyon's kernel and v6 script. its been pretty good for me so far. i have no complaints.
But if anybody else has a better setup. I myself would like to know as well
Wow, that's quite a prescription! For now, I'd just like to know what that process is and why it's running, so I can try to get it to back down.
Thanks for the tips. BTW, I was running voodoo lagfix back in the day, and it got me quadrant scores similar to what I was getting with this GB ROM (not 2K, but 1600 wasn't unusual); I'd like to get back to that point. Without necessarily starting over.
You're basically going to have to. The TBH leak is really old.
Sent from my SCH-I510 using xda premium
The TBH leak isn't that old (I downloaded it on Nov 7th), and the age of it doesn't make kernel processes run away. It's GB 2.3.6, basically the same as the latest OTA. And it only started doing this recently.
I'm afraid either something I've installed recently is triggering this (the better option, as I can start uninstalling stuff until the problem goes away), or there is something gone wonky with the hardware itself that the kernel is reacting to (obviously the worst case). That wouldn't surprise me, as this is my 3rd Charge, the first two having had lost their minds, running really hot and then rebooting every few minutes (this on the stock OS, rooted with the voodoo lagfix kernel).
More data (if there's anyone out there who actually knows what that kernel process is): OS Monitor's "messages" list is flooded with this:
"k3g_work_func: fifo entries are less than we want"
I get dozens of these PER SECOND.
Again, if anyone has any insight on what that process is about, glad to hear from you. Those who say "Nuke and pave!", not so much.
Fifo is an io scheduler if I remember correctly. Try changing it and seeing what happens.
"Nuke and pave" still seems like the best option.
Sent from my SCH-I510 using xda premium
kvswim said:
Fifo is an io scheduler if I remember correctly. Try changing it and seeing what happens.
Click to expand...
Click to collapse
Fifo is a general term for a queue -- "first in/first out". Many kernel processes live their lives managing queues. This one is complaining about it's queue being shorter (fewer entries) than it thinks it should have.
Did I see your name attached to a thread about trying to compile a kernel? If so, would you do me a favor, so I don't have to get all into git so I can get to the AOSP code, and grep for "k3g" and/or "k3g_wq" (still sounds to me like like "kernel 3g worker queue") and see if you can see what it does? Nothing in depth, just in general what it handles.
kvswim said:
"Nuke and pave" still seems like the best option.
Click to expand...
Click to collapse
Funny thing happened today. It was getting worse and worse. Battery stats showed a shocking thing--for the first time ever, Display wasn't the biggest battery hog, it was Android OS!
So I decided to just reboot, to see if I could get it back to good enough to do backups and start the nuke-n-pave process. I had rebooted a few times over the last few days, and it didn't solve anything. Today it did! Back to normal, and I ran Quadrant twice and got a 16xx on the second run. Nice. A few hours later, and it's still good. Keeping my fingers crossed.
Oh, I had also uninstalled DropBox (which I wasn't using yet anyway) and this massive Gameloft game, "Tintin". Those didn't help, before reboot. But maybe those, coupled with the reboot, did.
I may still nuke and pave, but probably with the stock GB and just root after that. And keep hoping the CyanogenMod comes out with a ROM for it.
Thanks.
I'm gonna revive this thread because I have a similar problem. My dad's charge is fully stock. He has never messed with anything. It was fine the whole time he had it except today. He has not used it at all today (10m screen time in 12 hours, and half of that was me trying to fix it) and the battery drained down to 30% all by itself. Me being the tech guy, he gave it to me and I checked battery usage. Android OS was reported to be using 89%. Cell standby was at 3%, and display came in last at 2%.
Since "Android OS" is very generic, I used adb to put the xda version of betterbatterystats on his phone, and under process, there is this thing called "k3g_wq" with almost a full bar. Under other, it shows the phone being awake 98.2% of the time. This problem only arose today. As he has not used the phone at all, there would be no rogue apps unless something just turned up. I disabled automatic updates in the market since the stock tunewiki app updated its permissions to read SMS (spyware???).
Does anyone have a solution to this besides factory reset?
K3G is a sensor, specifically the level sensor. Not sure why it would take up system resources, but I would think turning off auto screen rotation may be one method to try and limit its use and battery drain.
See my posts on k3g_wq above. Note that I found error log message about it not having enough entries--thus my supposition that wq == worker queue. If imnuts says it's a level sensor, then that's got to be it; from the name, I figured k was for kernel and 3g was...well...3g.
In my case, I was able to see it using OS Monitor (free in the market), using consistently about 30% of the CPU, which resulted in the OS being the largest consumer of battery.
And, for me, it finally just stopped doing it, after one more reboot. Hasn't come back. But every time the phone gets a bit laggy, I go look at that process list.
On another note, we're using my Charge at work as a test phone for our Android app, as it makes it blow up like no other device we have.
I have noticed a sensor leak associated with google maps. Try opening maps in that phone, exit out of it and see if sensor usage persists. I hadn't mentioned it before assuming it was unique to my device.
Sent from my SCH-I510 using Tapatalk
I also notice runaway usage of k3g_wq in the last week. I have stock OTA EP4 and it had been running fine for many weeks with no issue. So there has to be something that changed recently. My guesses are the new version of Google Maps, or new version of Tiny Flashlight with the "shake on lockscreen" feature. I don't see Tiny Flashlight running any services, but since I disabled the shake on lockscreen feature my k3g_wq usage seems to be OK.
I factory reset the phone and the problem disappeared.
Sent from my pocket-sized, Linux-based computer using electromagnetic radiation.
Ooooh, I just had the k3g_wq high usage issue while actively using my phone. OS Monitor showed it using 40% of processor all the time. So I tried the following:
1) disable auto-rotation. No impact.
2) started and exited maps. No impact.
3) Unistalled maps update and tiny flashlight. No impact.
3) Turned off wifi, GPS, data, BT. No impact.
4) Killed every running service that would stay killed. No impact.
5) Rebooted. This fixed it for now.
This makes me think back to the flash destroying early leak of GB for the Fascinate. This ROM would also have a similar process that got stuck using lots of CPU. On that dirty ROM, auto rotation needed to be enabled to see the issue. However once you had the problem, it wouldn't go away until reboot. The only safe thing was to disable auto rotation, reboot, and never reenable. Perhaps the Charge is now the same.
My opinion of Android and Samsung is not improving. In fact I do have some anger issues.
Give me a freaking iPhone at this point, I'll do anything for a quality engineered and tested device that actually works out of the box. Android and Google are sloppy if nothing else. Open sloppy mind you.
Scrappy1 said:
Ooooh, I just had the k3g_wq high usage issue while actively using my phone. OS Monitor showed it using 40% of processor all the time. So I tried the following:
1) disable auto-rotation. No impact.
2) started and exited maps. No impact.
3) Unistalled maps update and tiny flashlight. No impact.
3) Turned off wifi, GPS, data, BT. No impact.
4) Killed every running service that would stay killed. No impact.
5) Rebooted. This fixed it for now.
This makes me think back to the flash destroying early leak of GB for the Fascinate. This ROM would also have a similar process that got stuck using lots of CPU. On that dirty ROM, auto rotation needed to be enabled to see the issue. However once you had the problem, it wouldn't go away until reboot. The only safe thing was to disable auto rotation, reboot, and never reenable. Perhaps the Charge is now the same.
My opinion of Android and Samsung is not improving. In fact I do have some anger issues.
Give me a freaking iPhone at this point, I'll do anything for a quality engineered and tested device that actually works out of the box. Android and Google are sloppy if nothing else. Open sloppy mind you.
Click to expand...
Click to collapse
Must resist urge to flame... Seriously though, I think it's just good practice to get used to flashing ROMs, making backups, and learning to mod your phone. I've had some curious problems that only a reflash would solve. In any case, the only thing worth a damn on the iPhone 4S is the camera. The internals are fast, but what's the point?
xdadevnube said:
Must resist urge to flame... Seriously though, I think it's just good practice to get used to flashing ROMs, making backups, and learning to mod your phone. I've had some curious problems that only a reflash would solve. In any case, the only thing worth a damn on the iPhone 4S is the camera. The internals are fast, but what's the point?
Click to expand...
Click to collapse
If you're a geek and have time to flash and mod, that's great for you. I used to be in this camp. Now I just want my phone to work without contanstaintly modifying it, babysitting process and battery life. I want a phone I could recommended to ANY friend or parent without worrying. The Charge definately isn't it.
My brief history in Android:
Samsung Fascinate: got tired of poor battery life and runaway processes.
Samsung Charge: got tired of poor battery life and runaway processed. Also, voice quality is horrendous.
Samsung Galaxy Nexus: Tons of reviews of runaway "Android OS" proccessed during idle. Voice quality is bad and outbound audio drops.
With each generation, problems weren't fixed and Google/Samsung continue their careless ways. To me its just sloppy, sloppy, execution.
Scrappy1 said:
I'll do anything for a quality engineered and tested device that actually works out of the box. Android and Google are sloppy if nothing else. Open sloppy mind you.
Click to expand...
Click to collapse
You're running a leaked, unofficial build that was part of the testing process, not the result of the testing process. If it's a software related problem (either due to a rogue app or to a bug with the leaked build), there's no one to blame but yourself for installing it. If it's a hardware related issue on the other hand, there's probably warranty coverage that would cover the problem.
Go back to stock, OTA, unrooted. See if the problem persists. Reinstall your apps. See if the problem persists. If it does, your phone will be "stock" and you can pursue a warranty claim.
charlie_c said:
You're running a leaked, unofficial build that was part of the testing process, not the result of the testing process. If it's a software related problem (either due to a rogue app or to a bug with the leaked build), there's no one to blame but yourself for installing it. If it's a hardware related issue on the other hand, there's probably warranty coverage that would cover the problem.
Go back to stock, OTA, unrooted. See if the problem persists. Reinstall your apps. See if the problem persists. If it does, your phone will be "stock" and you can pursue a warranty claim.
Click to expand...
Click to collapse
No man, i already mentioned, I'm stock OTA EP4. I'm also unrooted.
Scrappy1 said:
No man, i already mentioned, I'm stock OTA EP4. I'm also unrooted.
Click to expand...
Click to collapse
Sorry, thought you were OP
Sent from my SCH-I510 using Tapatalk
k3g_wq ... it came back, and then I killed it, I think
OP here.
Today I was looking at my Charge and marveling at how I was getting pretty good performance but better battery life due to my latest tweaks in SetCPU, when I looked at battery usage: Android OS was creeping up on Display as juice-user No. 1.
Uh oh.
So back to OS Monitor, and sure enough, there's k3g_wq on a steady 25-30% of the CPU.
Opened and closed Maps--no luck.
Killed its process in the process list in OS Monitor (it appeared to be swapped out, but what the heck)--no luck.
Opened another cool app called Elixir that shows you sensors, and lets you enable/disable them. Hrm...gyroscope, rotation and orientation sensors. All were off; turned each on, then back off.
Looked in OS Monitor and...YES! k3g_wq is gone!
Wild guess time, but apparently the start-up/shut-down of whichever sensor it is doesn't always work right, and leaves that service looking for its momma (that's a highly technical description of the problem, sniff).
Anyway, if you're seeing k3g_wq running wild, give that a try. Next time I do, I'll try them one at a time, see which one does the trick (assuming it's only one).
LDog
PS -- Kudos again to imnuts for letting us know it's the level sensor. Or sensors.
Hi,
I installed the software from Alcatel's site on my windows 7 32bit, and then I let One Touch Upgrade work last night. I woke up just now and I noticed that it's still working. That means that it's been working for well over six hours. Is this normal? I'm starting to get a bit worried.
The phone looks shut down, with the lights on for Options, Search, and Back buttons. I don't want to touch it and cause any more damage, but I'm not sure if the damage has already been done.
I can't see quite what is the percentage on the installer, it got kinda smeared from the apps I was currently using, but I think that it's still working, it's responsive.
What I remember from last night, it was really slow in terms of completing the procedure, like 22%... 23%.... 24%.... for over an hour.
I did rooted it, but that's it, wasn't changing ROM or doing anything really, not yet at least.
I don't know what to do :C
Some help would be really appreciated. Thanks in advance and cheers!
edit: Oh, and just to add, I went and observed the net traffic that was made during the last 10 hours. I was amazed - it downloaded less than 100 MB and uploaded more than 300 MB! Why would this software do that? Also, the download rate is really bad, dunno why, I have 6 Mbit/s connection.
I am very confused right now. Please help.
So I've had a T-Mo S7 for about a year and a half now. It's incredibly slow/unresponsive and I've spent a really long time troubleshooting.
I've done full factory resets, and direct ODIN OS installs with data wipes. Whenever I do this, the phone starts out, with all current apps installed, extremely fast/responsive. I have a somewhat limited app library, and I haven't added anything since the phone slowed down noticeably.
About two months ago, the Samsung Device Maintenance app, which until then only reported battery draining, said "Some apps or processes are overloading the system (CPU)" and the app it reported was something like com.android/google.searchbar" which I assume is the google search bar widget. I thought, "awesome, the device app is actually doing something." I told it to kill the app and my phone sprung to life. My phone was super fast for a long time, but is now back to being super slow again. I searched "Apps" in device settings and can't find any apps/processes that sound anything like search bar. Also, how is there not a system resource monitor in system settings!? Clearly, an app is hogging resources, because I've experienced periods of responsiveness. Is there no direct way to figure this out without doing the safe mode process of elimination?
Can someone help shed some light or suggest further troubleshooting steps? Thanks in advance.
I got mine on black friday 2 years ago and I've been having the same issue. Of course my battery doesn't last very long being it's over 2 years old. I'm guessing it may have some.thing to do with the battery voltage being so weak after so long. I'm due for an upgrade obviously but I'd be fine using my S7 for another year if a battery replacement did the trick. I believe I was told in chat that I could go into the store and they'd only charge me $5 but I assume they'd have to send the phone out unless they just swap it out for a refurbished one. I've had no other problems with mine at all so not really the route I want to take.
Anyone else familiar with this process? Has anyone else had their battery replaced or phone swapped and notice if the fresher battery helps or is it just a symptom of it "can't" handle the newer OS properly? Any feedback would be appreciated. Hopefully it helps us both out. Didn't mean to hijack the thread!
tony yayo said:
I got mine on black friday 2 years ago and I've been having the same issue. Of course my battery doesn't last very long being it's over 2 years old. I'm guessing it may have some.thing to do with the battery voltage being so weak after so long. I'm due for an upgrade obviously but I'd be fine using my S7 for another year if a battery replacement did the trick. I believe I was told in chat that I could go into the store and they'd only charge me $5 but I assume they'd have to send the phone out unless they just swap it out for a refurbished one. I've had no other problems with mine at all so not really the route I want to take.
Anyone else familiar with this process? Has anyone else had their battery replaced or phone swapped and notice if the fresher battery helps or is it just a symptom of it "can't" handle the newer OS properly? Any feedback would be appreciated. Hopefully it helps us both out. Didn't mean to hijack the thread!
Click to expand...
Click to collapse
So I promise it's not the battery because I had it factory replaced by Samsung. To answer your question, yeah you have to send it in. With the waterproofing they have to do it at a repair center. However, for me it was 100% worth it. I think I was without the phone for about 10 days. But having a brand new battery life was incredible.
Also, as I was working with the phone slow for a while, it immediately and dramatically became quick after device maintenance killed that process. But a few months later, I'm back to suuuuper slow.
The S7 is getting old. Old things slow down. It's planned obsolescence. I've gotten to the point of turning notifications off for all apps and only using badge numbers to tell me when to check something. I also use do not disturb a lot when gaming instead of game tools because game tools is another app but do not disturb is more of an internal process. As soon as my taxes come back I'm probably going to get a S8+
Hello.
It's my very second post on XDA Forums, so If I'm posting this on a wrong section, please tell me so I can correct/move it to the correct area.
I've been using a J7 (SM G-J700H), that my mom left me when she switched to a newer one, for experimental purposes (monitoring, hacking, rooting, etc).
But I've encountered an issue with the battery: it's not reading it properly, like, whenever I see my phone it is F.E. at 70%, but after rebooting the phone 2 or 3 minutes after the first reading, it drops to 25%, and if I do another reboot It drops down/ goes up to another % far higher/lower than the previous one.
So, I thought maybe the battery was dying (the cellphone has ages of use, but still works and looks fine, like new) and then changed it for a new Samsung original one, but got the same problem.
A good thing to add to this mess is that the battery life of the phone, when charged to 100%*, is correct: it stays on for a day and a half or two (no SIM, just WiFi and stand-by operations).
* = I make sure that it gets charged by connecting it to the power-line for hours xD
So I'm wondering what's causing this reading issues?
What I've done so far to try and fix this was (and obviously failed to):
Factory-Resetting the phone (even flashed the Stock firmware again, thus it was already flashed)
Samsung's battery calibration code
Rooting the phone for further HW analysis.
Checking Temperature (it's normal both on battery or CPU).
Just to avoid questions: I have a small homemade Electronics lab at home, so doing some repairings is not an issue for me.
I have some experience with SMD reflow/soldering, so If it has anything to do with the hardware, just tell me what to do and I'll be able to do so.
By the other hand, if it is a software issue, feel welcome to advice me too because I'm a software technician, so I would catch up with everything you say.
Thank you all who reply to this post in advantage.