Related
http://www.addictivetips.com/mobile...-issue-on-a-rooted-android-device/#more-50317
check this out .. but the problem is when i load into recovery those same options dnt come .. if ne1 can do this procedure please explain me ..
rrohanjs said:
http://www.addictivetips.com/mobile...-issue-on-a-rooted-android-device/#more-50317
check this out .. but the problem is when i load into recovery those same options dnt come .. if ne1 can do this procedure please explain me ..
Click to expand...
Click to collapse
Check this out:
# Wipe Battery Stats. The following screenshots demonstrate how to wipe battery stats in ClockworkMod Recovery v2.5.0.7. Select advanced > Wipe Battery Stats > Yes – Wipe Battery Stats.
Click to expand...
Click to collapse
AFAIK, ClockworkMod Recovery is not available for Milestone.
Alternatively delete it manually.
Search for batterystat in milestone forum there's a lot to read.....
Good luck,
scholbert
Hi,
If you are root on your device you can use the terminal emulator to remove the batterystats.bin file yourself...
su [enter]
rm data/system/batterystats.bin [enter]
Beware, for the first few charge cycles your battery life may actually be worse, but it will improve. Ensure that you reboot straight after too.
Thanks for the tip.
Sent from my Milestone using XDA App
Sometimes 100% charged is not really 100% but actually it is only 60% charged. This mismatch happens when flashing new rom. Have you done the battery calibration either using zeppelinrox's method
http://forum.xda-developers.com/showpost.php?p=11803458&postcount=10
or my method below:
Step 1:
Boot up your phone normally and charge your phone as how you would normally do until it says "charged".
Step 2:
Once your phone charging status says "charged", unplug the wall socket cable from the phone. Shut the phone off.
Step 3:
While the phone is still off, plug back in the wall charger cable. Switch on the power of the wall charger.
Step 4:
You should then see the M logo for a while and then it shows the 100% green battery icon in the middle of the screen.
Step 5:
Open the battery cover and pull out the battery and wait for awhile until you see the "?" icon in the middle of the LCD screen.
Step 6:
Put the battery back in.
Step 7:
If your battery is OK (properly calibrated) then it would show 100%. If it is not properly calibrated, then it would show 60% and it will continue to charge your battery until 100%.
Step 8:
Once your battery has reached 100% (while phone is still off), leave it there to charge for another 15 minutes or until the battery is no longer hot. When the battery is cool to the touch, it means the charger has stopped charging the battery.
Step 9:
Unplug the charging cable and do the "3 finger boot" (x button + camera button + power button) to boot into recovery and flash the new ROM.
Doing so will calibrate the new ROM to the current state of the battery as 100% charged.
Somebody actually posted a video of it... I think it was androidve.com
I should find it again and update my post hehe
Ah... http://androidve.com/2011/03/androidcast-episodio-ocho-calibrando-la-bateria/
ther aint ne folder called system in the data folder .. i cnt find the batterystats.bin file to delete
you can use clockworkmod on milestone
just copy update.zip to /sdcard/OpenRecovery/update and run it
Dear Friends
i have galaxy tab 8.9 inch 32Gb
i need to downgrade from 4.0.4 to 3.2 because of battery problem
i did to 3.2 but still the same
now i need to flash 3.1
but
my device is 32gb should i use the same PIT.file labled P7300_P7310_p5_0614.pit or what
if i used former one it will not decreast the internal SD from 32 to 16 g
where i can get 32g pit file
thanks
For battery problem, switching roms won't help. Its a waste of time. The soln to this its here in the general section.
http://forum.xda-developers.com/showthread.php?t=1861229
Sent from my GT-P7300 using XDA Premium HD app
lrcquest said:
For battery problem, switching roms won't help. Its a waste of time. The soln to this its here in the general section.
http://forum.xda-developers.com/showthread.php?t=1861229
Sent from my GT-P7300 using XDA Premium HD app
Click to expand...
Click to collapse
Nothing usefull from that
Can u elaborate abt the battery pblm?
Sent from my GT-N7000 using xda premium
lrcquest said:
Can u elaborate abt the battery pblm?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i did but the battery voltage show 0.004V
i think there is a problem my be fixed with full rom
Inside android or in recovery? How did it get this low? Have u charged with phone off? Have u tried to take volt measurement in adb after charging?
Sent from my GT-N7000 using xda premium
lrcquest said:
Inside android or in recovery? How did it get this low? Have u charged with phone off? Have u tried to take volt measurement in adb after charging?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i did inside android
many program show this results as shown
Have u charged with phone off?
yes i did many times after i discovered this matter
Have u tried to take volt measurement in adb after charging?
yes correct measurement of voltage appear in 50% appear 3881
The adb measurement seems to be ok as the range is 3400 to 4100. U can get to recovery & wait / reboot till the voltage drops to near 3400. I have done this Eden faced with problems of battery on the stock ics twice.
Sent from my GT-N7000 using xda premium
lrcquest said:
The adb measurement seems to be ok as the range is 3400 to 4100. U can get to recovery & wait / reboot till the voltage drops to near 3400. I have done this Eden faced with problems of battery on the stock ics twice.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i don't knew how to measure voltage in recovery mode using adb ?
i think there is problem
the command in my tab results in 3680 in 3% battery percentage ( only 4 digit)
but when i tried on my galaxy s2 results 3853750 in 42% ( 7 digit )
somaare said:
i don't knew how to measure voltage in recovery mode using adb ?
i think there is problem
the command in my tab results in 3680 in 3% battery percentage ( only 4 digit)
but when i tried on my galaxy s2 results 3853750 in 42% ( 7 digit )
Click to expand...
Click to collapse
first u need android sdk in your pc. download & install the same. it will be in "C:\Program Files (x86)\Android\android-sdk" in an 64 bit pc. in the command prompt go to this location. "C:\Program Files (x86)\Android\android-sdk\platform-tools"
from this point u can use the adb commands.
first check with the command "adb help"
u will get some responses.
u have to mount the system (in the cwm recovery) in the mount & storage section. then only will the device communicate with the pc in adb.
now connect the equipment (which is now in recovery mode) to the pc & use the command "adb devices"
u will get some sort of numbers instead of the 7300 or galaxy tab etc.
use the following command to know the voltage. "adb shell cat /sys/class/power_supply/battery/voltage_now"
pls note that there is a space in between "cat & /sys"
now follow the steps.
1. in CWM/recovery let it sit till battery in terminal will show less then 3700. The less you can get it the better. 3400 is probably absolute minimum.
2. shut down tab and let it sit for 1 hour. (this is needed for the first measurement)
3. plug it to charger and charge it for 5 hours.
4. disconnected charger and let it sit for 1 hour. (this is needed for the second measurement)
5. boot up your tab and test it, it your battery still not calibrated you can flash back your backup and repeat calibration procedure.
this is definitely a laborious process, but there is no option but to follow this.
hope this helps.
lrcquest said:
first u need android sdk in your pc. download & install the same. it will be in "C:\Program Files (x86)\Android\android-sdk" in an 64 bit pc. in the command prompt go to this location. "C:\Program Files (x86)\Android\android-sdk\platform-tools"
from this point u can use the adb commands.
first check with the command "adb help"
u will get some responses.
u have to mount the system (in the cwm recovery) in the mount & storage section. then only will the device communicate with the pc in adb.
now connect the equipment (which is now in recovery mode) to the pc & use the command "adb devices"
u will get some sort of numbers instead of the 7300 or galaxy tab etc.
use the following command to know the voltage. "adb shell cat /sys/class/power_supply/battery/voltage_now"
pls note that there is a space in between "cat & /sys"
now follow the steps.
1. in CWM/recovery let it sit till battery in terminal will show less then 3700. The less you can get it the better. 3400 is probably absolute minimum.
2. shut down tab and let it sit for 1 hour. (this is needed for the first measurement)
3. plug it to charger and charge it for 5 hours.
4. disconnected charger and let it sit for 1 hour. (this is needed for the second measurement)
5. boot up your tab and test it, it your battery still not calibrated you can flash back your backup and repeat calibration procedure.
this is definitely a laborious process, but there is no option but to follow this.
hope this helps.
Click to expand...
Click to collapse
thanks i will try again today
lrcquest said:
first u need android sdk in your pc. download & install the same. it will be in "C:\Program Files (x86)\Android\android-sdk" in an 64 bit pc. in the command prompt go to this location. "C:\Program Files (x86)\Android\android-sdk\platform-tools"
from this point u can use the adb commands.
first check with the command "adb help"
u will get some responses.
u have to mount the system (in the cwm recovery) in the mount & storage section. then only will the device communicate with the pc in adb.
now connect the equipment (which is now in recovery mode) to the pc & use the command "adb devices"
u will get some sort of numbers instead of the 7300 or galaxy tab etc.
use the following command to know the voltage. "adb shell cat /sys/class/power_supply/battery/voltage_now"
pls note that there is a space in between "cat & /sys"
now follow the steps.
1. in CWM/recovery let it sit till battery in terminal will show less then 3700. The less you can get it the better. 3400 is probably absolute minimum.
2. shut down tab and let it sit for 1 hour. (this is needed for the first measurement)
3. plug it to charger and charge it for 5 hours.
4. disconnected charger and let it sit for 1 hour. (this is needed for the second measurement)
5. boot up your tab and test it, it your battery still not calibrated you can flash back your backup and repeat calibration procedure.
this is definitely a laborious process, but there is no option but to follow this.
hope this helps.
Click to expand...
Click to collapse
thanks alot
i did that using my current installation just need to mount system to work on recovery mod
i downgrade to 3.1 using 5 files and update to 3.2
and i did the previous instruction and the battery now is very good and no fake percentage
But still fake voltage even using adb
see the attachment
i think my be some fail in files measure voltage
today morining to disconnect battery for 10 minute but the same problem
any program for the battery show voltage in MVor 0.00? V
U can use battery monitor widget. Always good measurements & worth timeline also.
The second voltage from the s2 might be divided by 1000 to get the right value.
Sent from my GT-N7000 using xda premium
Hello and welcome to this thread.
Here I will answer some of the most common issues related to this phone.
Q: I installed Nameless ROM v7.2 and...
A:
Change now. Its extremely outdated. Swap either to any CM10 ROM, Sensational V4, or Revolution. They are the most recent so far.
Q: What are the bugs in CM10 ROMs?
A:
Instant messenger voice messages;
Wi-Fi Hotspot.
Q: My WiFi keeps disconnecting.
A:
>Download this app
>Start the app
>Click on any of the non selected behaviors (Default or On During Sleep if plugged)
>The app will close
>Open the app and click on advanced options
>Enable workaround 2
>On the main screen chose Always on
>The app will close
>You are good to go
Q: My phone is stuck in a bootloop, what do I do?
A:
Did you install the correct kernel? NOPE only works on CM10.
Did you try a lower frequency?
Did you do a full wipe when installing a new ROM?
If the answer to all of these is yes, message me on Facebook so I can assist you.
Q: Can you implement [Name a thing] in your kernel?
A:
Help me find the patch and I will.
Q: How do I install a ROM/Kernel?
A:
Please read this carefully.
Q: What is the best ROM/Kernel
A:
There is no such thing. It has been mentioned a lot of times that this a dreaded question. You try and you chose the one that appeals to you the most.
Q: My battery doesn't last as long, what measures can I take to increase uptime?
A:
If you are aiming for battery life probably the most effective way to do that is by turning off WiFi, and MobileData when you are not using them (pretty logical isn't it?)
Get an app called Greenify and hibernate most of the apps that are recommended. Play services, Facebook and such are not necessary processes in the background. They will drain battery. So that will suspend them until you start the given app.
I recommend /not/ using taskers or triggers. The simple fact of having an app scanning the state of your phone, detecting the conditions and completing the task uses more battery than you doing regular maintenance yourself.
The only exception I can add here is SetCPU. Get it. And make profiles. Night mode and Screen off are a must. Just note for regular screen off don't set it lower than 300 or it might make your music stutter in case you are listening to any.
Use your battery wisely, don't waste it on games/internet if you are going to need it.
Buy an emergency charger online. I am probably going to do this soon.
Q: How do I unlock my bootloader?
A:
Follow >this guide< It's pretty detailed and has pictures and green stuff. Automatically better than anything I will be able to post here.
Note: Using a toolkit will damage your learning process. I recommend not doing it that way. You will be needing the experience later on.
Q: How do I flash a ROM?
A:
Download the desired ROM and save it to (a folder in) your SD card.
Reboot to your preferred recovery.
Make. A. Backup.
Please.
Wipe Dalvik, Cache and Data. Or factory reset, I have been sticking to the same ROM for a long time, so I kinda have forgotten. NOTE: This will delete your apps and settings.
Locate the ROM and install it. Proceed to puke some rainbows.
Make sure you have the correct kernel for the rom. You CANNOT use NOPE kernel for Sense ROMs.
Q: How do I flash a kernel?
A:
You need to have ADB. I will assume that you have it already because you have your bootloader unlocked.
Download the kernel and place it your platform-tools folder.
Reboot your phone to bootloader.
Connect it to the PC using the cable.
Open a command prompt (Hold shift and right click inside the the platform-tools folder (Not on any specific file, just inside it) and click Open command window here)
Make sure your device is recognized. (One time is enough)
Code:
fastboot devices
Erase the cache. (Optional but I do it anyway)
Code:
fastboot erase cache
Flash the kernel.
Code:
fastboot flash boot [File name].img
Where you replace [File name] with the name your kernel has. For example if your kernel is named boot800 the command will be "fastboot flash boot boot800.img"
Q: How do I flash a kernel?
A:
You need to have ADB. I will assume that you have it already because you have your bootloader unlocked.
Download the kernel and place it your platform-tools folder.
Reboot your phone to bootloader.
Connect it to the PC using the cable.
Open a command prompt (Hold shift and right click inside the the platform-tools folder (Not on any specific file, just inside it) and click Open command window here)
Erase the cache. (Optional but I do it anyway)
Code:
fastboot erase cache
Flash the recovery.
Code:
fastboot flash recovery [File name].img
Where you replace [File name] with the name your recovery has. For example if your recovery is named TeamWin the command will be "fastboot flash recovery TeamWin.img"
Copy>Pasted this part and changed some stuff. Not even sorry.
P.S. You can suggest FAQs and I will add them ASAP. It's still a WIP.
What is the best ROM?
A:
There is none. Pick the one that is right for u!
Add this to op please! :3
Also you should get this thread stickied
Sent from my HTC Desire C using xda app-developers app
uchihasparky said:
What is the best ROM?
A:
There is none. Pick the one that is right for u!
Add this to op please! :3
Also you should get this thread stickied
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
I tried getting it stickied but they refused, I need more info =3
me4488 said:
I tried getting it stickied but they refused, I need more info =3
Click to expand...
Click to collapse
Yeah.. getting sticky-ed is a tough job.
On topic - you can add the procedure to change from one ROM to another "the right way" (backup, wipe, flash rom, flash kernel) in a little detail. Almost none of the problems would occur if people just follow this simple thing.
Q: my battery lasts less than when I was on stock, what can I do?
A: It depends on how much you want to invest:
1) turn off data when not in use - FREE
2) dim screen - FREE
3) use airplane mode while you sleep - FREE
4) use Greenify to hibernate non-critical apps that use wakelocks for sync and update - FREE
5) set a screen-off profile with low frequency with SetCPU - PAID (there's a free version for XDA members)
6) set a Tasker profile to activate Mobile Data at specific intervals only (i.e. every 15 mins) - PAID
I'll add more battery saving measures later
Sent from my HTC Desire C using xda app-developers app
I added some new stuff, hopefully its helpful. More suggestions are welcome =3
Show some love to my suggestion perhaps?
Sent from my HTC Desire C using xda app-developers app
Anyone using the new 1.17.40.1234 update please post your impressions and more particularly any bugs encountered.
Overheating, system slowdown and poor battery life have been mentioned by a number of users on other sites.
phone is overheating whenever I am using whatsapp or simply playing games. Is there anyway to rollback to W1.16.40.763 ?
souravipc53 said:
phone is overheating whenever I am using whatsapp or simply playing games. Is there anyway to rollback to W1.16.40.763 ?
Click to expand...
Click to collapse
Do you have 1.17.40.1234 or 1.17.40.1106 ?
I think that they might have corrected the issues with the 1234 version.
If you want to rollback just copy the update in the phone renaming it with a upper version, for example 1.18.40.763, remember that the procedure is at your own risk.
reddevilx said:
Do you have 1.17.40.1234 or 1.17.40.1106 ?
I think that they might have corrected the issues with the 1234 version.
If you want to rollback just copy the update in the phone renaming it with a upper version, for example 1.18.40.763, remember that the procedure is at your own risk.
Click to expand...
Click to collapse
On the asus forums a number of users said the latest 1234 update made the overheating and battery much worse.
reddevilx said:
If you want to rollback just copy the update in the phone renaming it with a upper version, for example 1.18.40.763, remember that the procedure is at your own risk.
Click to expand...
Click to collapse
.
method doesn't work. Even though updater notifies me about new update but fails . Shows older version cannot be used or something like that.
souravipc53 said:
.
method doesn't work. Even though updater notifies me about new update but fails . Shows older version cannot be used or something like that.
Click to expand...
Click to collapse
From the asus forum try this:
1. Download the firmware to your PC
2. Rename it to MOFD_SDUPDATE, enable the view extension of the files option and check that the file has only .zip, .zip.zip is not accepted and the procedure will fail. (you should have MOFD_SDUPDATE.zip)
3. Now format the sd card in windows with default settings (fat32)
4. Copy the MOFD_SDUPDATE.zip on the newly formatted sd card
5. Shut down your phone and insert the sd card
6. To boot in recovery mode you need to:
a. Hold the power button and volume down key all together
b. When the first Asus logo appears, release the keys.
7. Go to update from sd card and located the MOFD_SDUPDATE.zip
8. Then flash
9. You can format the cache partition if you like (recommended)
cheers
heywheelie said:
From the asus forum try this:
1. Download the firmware to your PC
2. Rename it to MOFD_SDUPDATE, enable the view extension of the files option and check that the file has only .zip, .zip.zip is not accepted and the procedure will fail. (you should have MOFD_SDUPDATE.zip)
3. Now format the sd card in windows with default settings (fat32)
4. Copy the MOFD_SDUPDATE.zip on the newly formatted sd card
5. Shut down your phone and insert the sd card
6. To boot in recovery mode you need to:
a. Hold the power button and volume down key all together
b. When the first Asus logo appears, release the keys.
7. Go to update from sd card and located the MOFD_SDUPDATE.zip
8. Then flash
9. You can format the cache partition if you like (recommended)
cheers
Click to expand...
Click to collapse
Tried this method. Doesnt work. Better use cyanogen mod and TWRP
Or try this:
1.0 [Preparation of your PC]
Download the ADB Tool HERE.
Click on the setup executable and type in "Y" for all the entries. (for the prompt on driver installation, simply click "Next", "Install", followed by "Finish").
1.1
Download the ASUS Software Update HERE.
Once completed, move the update file to C:\adb (where C: is the root drive where the ADB Tool was installed at).
2.0 [Preparation of Device]
Turn off your phone.
Press the "Volume Down" button followed by the "Power" button.
Keep holding the two buttons until the recovery screen appears, then release both AT THE SAME TIME.
Plug your phone into the PC.
On your phone, press the "Volume Down" button to select the option "apply update from adb".
Then, press the "Power" button once to select.
3.0 [Flashing]
Open the command prompt (Windows Key + R, type in "CMD" and enter).
Type in cd C:\adb (take note).
Then, type in adb sideload "downloaded file name".zip
4.0 [Finish]
Upon completion, make sure that the option "reboot system now" is selected on your phone.
Then, press the "Power" button once.
Is anyone using this update that is not experiencing any problems especially battery and heating?
No feedback anyone?
Sent from my GT-S7582 using Tapatalk
Seems that very few have updated to this firmware. I haven't and won't until a stable update comes out. In the meantime I'm happy with 1.16.40.763
heywheelie said:
Seems that very few have updated to this firmware. I haven't and won't until a stable update comes out. In the meantime I'm happy with 1.16.40.763
Click to expand...
Click to collapse
I downgraded to V1.16 due to bugs and lag on v1.1.7.40.1234
Posted using a calculator and delayed by AT&T.
---------- Post added at 01:31 PM ---------- Previous post was at 01:29 PM ----------
shubham41 said:
No feedback anyone?
Sent from my GT-S7582 using Tapatalk
Click to expand...
Click to collapse
Mine keeps on overheating and it lags very bad. I downgraded mine to v1.16.
Posted using a calculator and delayed by AT&T.
shubham41 said:
No feedback anyone?
Sent from my GT-S7582 using Tapatalk
Click to expand...
Click to collapse
I've only been using it for a week on my ZOOTD but I haven't noticed any overheating or significant loss of battery life
UPDATE: I don't know if it was caused by the update or not but I was on a call and the flashlight came on and Firefox and Settings opened.
willcall said:
I've only been using it for a week on my ZOOTD but I haven't noticed any overheating or significant loss of battery life
Click to expand...
Click to collapse
Thanks. I wonder if the overheating and battery life problems only affects the Z00LD?
heywheelie said:
Seems that very few have updated to this firmware. I haven't and won't until a stable update comes out. In the meantime I'm happy with 1.16.40.763
Click to expand...
Click to collapse
Judging by the fact that a new update has not been released for quite some time now, the next update *should and hopefully, be marshmallow.
Sent from my ASUS_Z00LD using XDA-Developers mobile app
heywheelie said:
Anyone using the new 1.17.40.1234 update please post your impressions and more particularly any bugs encountered.
Overheating, system slowdown and poor battery life have been mentioned by a number of users on other sites.
Click to expand...
Click to collapse
No issues on my ze550kl, no heating issue, no major bugs on 1.17.40.1234. But it becomes warm when I don't close any game and tap home button but that's normal.
1.17.40.1234 came with Wi-Fi and carrier network improvements. I guess people from certain region might be facing heating issue due to changes in modem. I am from India. No issues for me
I can confirm there is an issue. I just got the phone and immediately updated it the latest firmware. I am getting abysmal battery life and the phone does get quite warm at times. I charged my phone last night and when I went to bed it was at 95% battery. When I woke up the battery was at 33%. I looked at the battery logs and the flashlight app and cell standby consumed 22% each. I have no clue why the flashlight app would be using battery for no reason.
dominati said:
I can confirm there is an issue. I just got the phone and immediately updated it the latest firmware. I am getting abysmal battery life and the phone does get quite warm at times. I charged my phone last night and when I went to bed it was at 95% battery. When I woke up the battery was at 33%. I looked at the battery logs and the flashlight app and cell standby consumed 22% each. I have no clue why the flashlight app would be using battery for no reason.
Click to expand...
Click to collapse
Try using the auto-start manager and making sure the flashlight app does not start automatically then reboot the phone. High standby usage can sometimes be caused by a faulty microsd card. If you have one, try unmounting and then remountiing it and see if that helps. If it doesn't try reformatting it.
Battery life on 12 Pro is probably one of the worst I have experienced. My phone is literally sucking battery life to a level I have not seen on any phone. Light usage, FB, Insta, emails, etc and Im down 40% in like 2 hours.
I did all sorts of resets, firmware updates, etc ( although latest Xiaomi EU has made it even worse in my opinion)
The solution I found, and its working amazing ( my batter life is gone from bad to super good) Same usage, same style and there is basically no drain.
The solution is to under clock the CPU. For the the phone must be rooted for the software to allow underclocking. Apk name is called 3C Cpu Manager
I basically run the CPU at around 60% of its max power. This is totally not noticeable for day to day use unless you use the phone for gaming or heavy CPU progarms.
The Snapdragon is very power hungry, all tasks are made with its using the full power which creates unecessary heat and battery drain. Its a pitty that Xiaomi doesn't have the CPU optimized better like some other phones using the same cpu with better battery life.
See images before and after battery usage and CPU settings for under locking
Hello there
I was wondering would ram management be affected after underclocking the processor? As many apps gets restarted when I do multitasking, like payment page gets refreshed when I switch app and then the payment made fails at device end.
I regret buying this super expensive brick whose ram sucks at just basic apps like chrome and gpay.
Kindly guide, as I want to improve battery life as well
It would have been more interesting to post 2 identical diagrams, ie without battery charge.
Wi-Fi is more energy intensive than data.
Is that true? Making connection to cell towers can't be more energy efficient than a close by router not can it? Especiallywhen in the move the reconnecting with and the searching for the network drains more energy I believe
NOSS8 said:
It would have been more interesting to post 2 identical diagrams, ie without battery charge.
Wi-Fi is more energy intensive than data.
Click to expand...
Click to collapse
Danacy said:
Is that true? Making connection to cell towers can't be more energy efficient than a close by router not can it? Especiallywhen in the move the reconnecting with and the searching for the network drains more energy I believe
Click to expand...
Click to collapse
Especially for streaming and downloads.
https://www.scienceabc.com/innovation/does-mobile-battery-drain-faster-on-mobile-data-or-wi-fi.html
NOSS8 said:
Especially for streaming and downloads.
https://www.scienceabc.com/innovation/does-mobile-battery-drain-faster-on-mobile-data-or-wi-fi.html
Click to expand...
Click to collapse
Interesting, tnx for sharing
Hi. What method did you use to root the phone?
I searched online but couldn't do it. I really want to increase my battery life. Yesterday I had only 4:40 hrs SoT with only social apps and web browsing.
[email protected] said:
Hi. What method did you use to root the phone?
I searched online but couldn't do it. I really want to increase my battery life. Yesterday I had only 4:40 hrs SoT with only social apps and web browsing.
Click to expand...
Click to collapse
I tried 3C Cpu Manager and saw no real improvement.
May be a little early to tell but with the latest Xiaomi EU rom A13, it displays 10 hours more at 100% which becomes 6 hours in the end.
Root:
1. Find or redownload the TGZ file for your current ROM
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V23?)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot flash boot_ab magiskXXXX.img
Once it's completed, run command fastboot reboot and the phone should boot and be rooted.
NOSS8 said:
I tried 3C Cpu Manager and saw no real improvement.
May be a little early to tell but with the latest Xiaomi EU rom A13, it displays 10 hours more at 100% which becomes 6 hours in the end.
Root:
1. Find or redownload the TGZ file for your current ROM
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V23?)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot flash boot_ab magiskXXXX.img
Once it's completed, run command fastboot reboot and the phone should boot and be rooted.
Click to expand...
Click to collapse
Hi. Thanks for the reply.
How was your battery life before compared to the 6 hrs you have now with xiaomi.eu A13??
[email protected] said:
Hi. Thanks for the reply.
How was your battery life before compared to the 6 hrs you have now with xiaomi.eu A13??
Click to expand...
Click to collapse
24 hours, I did a full charge this morning and I will post to let you know whether or not there is really an improvement after 48 hours.
NOSS8 said:
24 hours, I did a full charge this morning and I will post to let you know whether or not there is really an improvement after 48 hours.
Click to expand...
Click to collapse
Great. I will be waiting for your feedback.
Hey. This module is all you need: https://forum.xda-developers.com/t/...ife-more-than-sufficient-performance.4450435/
Try it now and you will feel the effect immediately. No more heat. No battery draining. It's perfect.
I confirm the battery life is improved with A13.
vietbt said:
Hey. This module is all you need: https://forum.xda-developers.com/t/...ife-more-than-sufficient-performance.4450435/
Try it now and you will feel the effect immediately. No more heat. No battery draining. It's perfect.
View attachment 5786745
Click to expand...
Click to collapse
Thank you for the suggestion. I will give it a try
NOSS8 said:
I confirm the battery life is improved with A13.
Click to expand...
Click to collapse
Thanks for the confirmation. I will give it a try later as my phone is rotted.
I prefer to have xiaomi.eu
vietbt said:
Hey. This module is all you need: https://forum.xda-developers.com/t/...ife-more-than-sufficient-performance.4450435/
Try it now and you will feel the effect immediately. No more heat. No battery draining. It's perfect.
View attachment 5786745
Click to expand...
Click to collapse
Which zip you prefer to flash for our Xiaomi 12 Pro 8Gen1 ?
lontu said:
Which zip you prefer to flash for our Xiaomi 12 Pro 8Gen1 ?
Click to expand...
Click to collapse
I recommend the Kirin 980 and SD778G modules.
vietbt said:
I recommend the Kirin 980 and SD778G modules.
Click to expand...
Click to collapse
Are you sure it works for an 8Gen1 when it seems to be more intended for the Snapdragon 888?
vietbt said:
I recommend the Kirin 980 and SD778G modules.
Click to expand...
Click to collapse
this feels like a bad idea try at your own risk,
trinadhchinna7 said:
this feels like a bad idea try at your own risk,
Click to expand...
Click to collapse
Yep, none of these mods is made for the 8Gen 1.