Protect your topaz from hardware damage while running android (guide) - Touch Diamond2, Pure Android Development

Android, is it really 'safe' to run on topaz with haret.exe?
Not really.
I know people will say "dude, dont test builds out if you are scared. I love android". I do love topaz android too. i hope this will help to prolong your topaz's hardware lifespan.
Possible hardware damage caused by buggy topaz android
1. Battery
2. sdcard
3. Possibly decrease in performance in other parts of the phone
Why is current buggy state of android harmful to topaz? Well,
1. constand read/write on sdcard with constant power supplied(never shuts off for power saving) - decrease life span of sdcard
2. Li-ion battery SHOULD NOT BE SUBJECTED to high drain situations if possible. This will decrease battery capacity significantly.Currently, battery drain is significant, due to unnecessary devices are left turned on etc.
3. Carging while high drain situation with BUGGY BATTERY METTER can stress our battery significantly even if there is protecting ic chip to protect battery from overcharging.
The problem is : Heat
Li-ion batteries lose their capacity if subjected to high temperature. Charging it is just suppling heat to our poor topaz battery, since battery will function like resistor ;D note topaz cannot directly be powered from usb. i.e. power socket->battery->topaz not power socket->topaz
4.Heat makes other parts of system subjected to lower lifespan and possibly, damage them
5. Remember android on topaz currently dont have 100 percent control over hardware, meaning unnecessary stuff can be running at all times.
Suggested way of using android on topaz
1. Have at least two batteries and swap them as you use topaz for both normal and android situations. This is good for li-ion batteries in general
2.Do not charge while you use topaz and if possible, stop it before battery is lower than 40%. In anycase, do not let it shut down because of low battery. If you really want to charge, consider downclock/full radio off/screen off to try to minimise stress battery goes through.
3. If possible, run android in cool, shady environment like your bedroom P)
4. Try to minimise running test builds like branch of test build for camera . This may stress your phones hardware unknowingly.
5. Becareful of android corrupting your sdcard anytime. Unknowingly, it performs a lot of read and write which is not recommended for flash memory in general.(sd cards are not ssd people)
6. Dont game or run benchmarks as much as possible
That is it. This guide applies to haret-android devices in general.
This guide will not be needed as much in situation of:
1. Nand build
2. Ram-mounted android build ( still danger of fring your sd card )
3. properly calibrated battery meter
provided their builds are stable and not as stressful as current build.
Happy android-ing. XD
Post your feedback. Please dont post things like I should not try it etc. This is just tips ,come on.

Yeah I've definitely thought about how bad the heat is for the battery and the phone itself
But I'm running it on a pure, so I almost don't care if I destroy my phone in the process. Would just give me an excuse to switch over to verizon for a droid or pick up an iPhone.
Good guide for newbs

I'm alxo running XD Android on my pure, but mostly just for the novelty.. Should I be switching batteries every time I want to run android? Should We all just wait for a flashable droid rom?
Does haret run on top of windows?

Link for Russia
http://xdandroid.at.ua/news/zashhitite_svoj_diamond_2_ot_povrezhdenij_v_android/2011-02-14-21
made by ME

Umm just to clarify
1. you do not need to set aside android battery. Just swap whenever possible even when running winmo. 2 Li-ion can last 3 years instead of 1 year for 1 battery
2. no. android is stand alone os
3. enjoy your android. Nand build is comming as DFT decided to port HD2 android boot utilites to Topaz and Rhoium. XD
4.Thanks for russian translation haha

My SD-card crashed
Hmmmm, my SD-card crashed today, and I did a lot off Android testing last two months ....
(my card is 2,5 years old)
This thread has an important warning: SD-cards are not made for this....

Related

question on wm6 and battery

Hi all,
I have installed the WM6.1 ROM 6.1.2a16CS by C. Shekhar on my qtek2020.
It is very cool and gave a second life to my qtek. I am just a bit surprised by the duration of the main battery. It is running out of bat very fast.
As I haven't used my qtek for month before installing the new ROM, I can't tell if it's a battery problem or because this new ROM is consuming more resources. Have you noticed such behavior on your machines?
For further info I am not using my qtek as cell phone. I am thinking about using it back as a phone, but I have first to fix this battery aspect.
Moreover I have read s/t about a battery fix, that I haven't installed yet. Can s/o tell me more about this fix and what it is doing?
Anyway this ROM is a great one.
Thx for your answers
Marc
I dont know about the battery fix but i have never installed any sort of fix like that either for wm5 or wm6.x. Are you sure there isnt some background process that keeps on continuously running? It could be a battery problem if the battery had discharged alot during the non-operational period. I changed by himas battery about 7-8months back because the last battery had gotten abit too old and was discharging very quickly.
i think you are talking about SD card fix..its a registery fix that makes the battery consumption by SD-card low
well, WM5 and WM6.x IMHO are battery consuming ROMs, i can attest to this,
experiment no. 1:
same xda, same battery (1200mAH original battery)
-with WM2003SE at normal use, XDA turns off approx after 36 hrs of use including standby.
-with WM5 and WM6.x, XDA turns off WM5-18hrs, WM6.x-25hrs of use including standby.
experiment no. 2:
two xda, different OS, both with brand new 3600mAH extended life battery.
in 1 day (at heavy texting use from 7am to 7pm):
WM2003SE XDA2 - battery from 100% to 58%
WM6.X XDA2 - battery from 100% to 35%
possible explanation:
WM6.x (WM5) uses more CPU time and Memory resources, plus it probably uses more power in maintaining the persistent storage, hard and soft reset persistent memory.
MODS PLEASE REMOVE THIS POST
ather90 said:
i think you are talking about SD card fix..its a registry fix that makes the battery consumption by SD-card low
Click to expand...
Click to collapse
Ather, is this fix already in all/most recent releases? If not, can you give us a link? Never heard of it.
I have no battery problems, quite the contrary. My battery life is amazing me. To be honest I tweaked a lot when I started using WM6.x, too much to remember, too much to tell you.
but some parts:
I don't need 24/7 phone connection, Phone Alarm takes care of this for me
Use a bare minimum of today plug-ins
Avoid animations
Close programs except when you seriously do need them in the background
Heya Maggy...its long time since i saw u here.. think maybe month
welcome back ny ways
well that fix was in the Imate website..i have it
having some problem attaching on xda : http://www.2shared.com/file/3591354/873d3f18/SD-Card_Patch.html

Battery life between leaked Captivate Froyo and custom ROMs

I noticed battery life on ae leaked Captivate Froyo 2.2 build (with AT&T bloatwares intact) was stellar!!! The battery life nearly doubled the custom ROMs that I have tried (the latest Cognition 2.3b8 and Axura 2.3 ROms).
I have tried all three on a regular work schedule from 8am - 4pm in a same location. I left all the ROMs installed as is. Here are the battery life meter findings at the end of my shift listed by ROM:
1. Leaked Captivate Froyo 2.2 --- Battery Life (92%)
2. Axura 2.3 --- Battery Life (69%)
3. Cognition 2.3b8 --- Battery Life (65%)
Anyone know why is this? Don't get me wrong, I love the Axura new functions and all that extras built-in. However, the battery life is discouraging.
did you recalibrate the battery and delete the batterystats.bin each time you changed to a different ROM? also, im not sure but the different modems could be the cause of the battery drain.
I almost want to say this is common sense. If you load something that increases your phones speed with a lagfix, gives you stronger reception and faster download speeds with using a different modem, and has many more enabled options would you not think battery may be effected?
All this being said I can get 20 hrs of moderate use on my current configuration. I do not need much more then that
Sent from my SAMSUNG-SGH-I897 using XDA App
mcord11758 said:
I almost want to say this is common sense.
Click to expand...
Click to collapse
*almost*
I have questioned this myself sometimes, then realizing that there is a lagfix installed. it's like buying a Vette for the gas mileage.. not gonna happen.
Hence, some custom ROM's do have damn good battery life with lagfixes! So, it's just a matter of finding what suits your needs.
The issue I've been seeing with the latest builds of most of the ROMs in the Dev Forums are:
Using customized i9000 Kernels and Modems. These are hacks/tweaks (and very good ones) to work with Captivate phones.
OC/UV Kernels that offer awesome overclocking/voltage capabilities but at a price - battery usage.
Using a Vibrant build for Captivate phones.
Custom "Captivate Kernels" (sorry the quotes aren't there for sarcasm just emphasis) that are still in beta or development.
All of the above cause battery issues as they are not optimized for our phone, missing some bits in the software that handle the OS/battery life, or straight up bleed the battery to death as your OVERCLOCKING YOUR PHONE.
And to make it worse utilizing different modems just exacerbates the problem.
Lag Fixes - SHOULD NOT AFFECT BATTERY LIFE AS THEY ARE JUST CHANGING YOUR EXISTING FILE STRUCTURE IN YOUR PHONE.
So it does make sense that while using a "stock" ROM you would get better battery life.
Now.. on to battery life/usage:
Calibrating the battery helps at least keep a more accurate track of how your phone's battery performance is doing.
You can do a few things to optimize your battery usage:
Of course Calibrate your battery - removing battery stats on your phone, doing the drain it down to 0% and re-charge to 100% to ensure you have an accurate idead of true battery usage is always helpful. I delete battery stats right after every flash to a new ROM.
Turning off Wireless/GPS/Data etc. while not in use. This does NOT mean to use a task killer since if you have an errant app running it will just make battery life worse not better.
If your using an OC kernel - then the usually install Voltage Control is a must! I have heard great things about tweaking these settings and people getting great battery life from their devices. Now.. mind you you don't have to overclock if your running the OC kernel. It's just there if you want it.
Also - being careful of what you have installed on your phone is one of the biggest ones most people miss. If it's trying to do a push every 3 seconds that is utilizing your battery/proc and that will be killing your phone.
With all that being said though? The custom ROMs are all awesome and I'm very glad we have them - even if it means I sacrifice a little bit of battery performance (which to me is horrid to begin with). I use a little common sense and I can at least get through an entire day with average usage (txts, email, calls, xda, angry birds etc..) without having to throw it on a charger.
Sorry.. long post - too much coffee and 90 wpm does that to me sometimes
cachookaman said:
did you recalibrate the battery and delete the batterystats.bin each time you changed to a different ROM? also, im not sure but the different modems could be the cause of the battery drain.
Click to expand...
Click to collapse
whats the easiest way to do this?
vuoflfan said:
whats the easiest way to do this?
Click to expand...
Click to collapse
For battery stats - you go into the advanced Clockwork Recovery Menu - go to Advanced - and you should see Clear Battery Stats there.
I would make sure that your phone is charged to 100% before doing this.
There is another trick you can do also that works for some people.
Charge your phone in.. as SOON as you get the notification stating to unplug your phone you should unplug it - wait 30 seconds then plug it back in. If it wasn't calibrated correctly you will see the percentage on your battery typically at around 97% instead of the reported 100%.
The improved battery life can probably be most attributed to the difference between the Java interpreter in 2.1 and Froyo's JIT.
In short, when Java does interpretation, it reads a single application instruction, decides what to do with it, does it, and repeats. If the same function is encountered again, the interpreter still has to re-read the instructions, decide what to do again, and do it.
In comparison, when Froyo's JIT encounters an application function, it reads the instructions in a large batch, decides what all of them should do, and records the result in the processor's "native-language". If the same function is encountered again, the processor just does it without needing to make all of those decisions again.
The speed difference is more than 30x. Running application code is only a small fraction of the total "working time", so benchmarks typically only see about 3x improvement. For the parts that are running applications (including even the home screen), Froyo is ultimately running 1 operation that used to take 30 operations - that means fewer electrons are wasted on the processor.
Also, Samsung's crappy filesystem decision certainly will impact battery life, since the format they chose (a relative of the old DOS format) performs seeks optimized for linear mechanical devices (like hard drives), not from FLASH, which suffers on fractional block reads and excels at non-linear reads. Lots of electrons will be wasted interacting with FLASH unnecessairily, but that kind of interaction is rare compared to other battery consumers.
- Kipp
Embedded Systems Hardware and Software Engineer

[Q] Winmo influence on Android?

hi guys (and girls?)
i've tried a couple of android builds an kernels and well everything haha
what i find strange is that some people only have a drain of 1% an hour and some of 7 or more. and i am not talking about different builds just one build....
so what i am wondering about does your winmo rom influence android in any way? is winmo still in the background or something... i tried to find the awnser myself but no luck. so help this newbie out!
(i know radio's influence battery life and data and gps and............ so on)
1. is because we run android in SDcard, it take more battery to access and read, write data than phone storage.
2. is all build until now still in beta, not final! so it run don't like office build ! and eat battery more than!
3. is our device to old, so battery not good like when we buy, so, some people have more battery life, some short than!
4. How they use phone? more, normal or litle? ...
and more things to make battery life difference with each people! ^^!

Poor Battery Life On Overcome Jupiter

Hi,
I don't have sufficient posts to be able to participate directly in that forum, so have no other choice but to raise my queries here.
I've just flashed over from Overcome "Hermes" to "Jupiter". All's well except that the battery performance is quite drastically affected for me.
I've been reading the improved battery life "Jupiter" gets over earlier versions of the Overcome ROMs, but I seem to be experiencing the opposite.
Already did the batt stat wipe via recovery menu. Do I need to so call "run-in" before it reflects correctly? Even if accuracy is one thing... but dropping 3% just on bootup.... is this typical of an uncalibrated battery?
Appreciate any advise here on what I should do. (Apart from a fresh wipe install )
Thanks
I appreciate the enthusiasm these coding geniuses have in rolling out update after updates in the ROMS yet I am apprehensive about the effect of these frequent flashing on the Galaxy Tab components itself. This includes the battery.
My job involves electronic repair and there is a so called number of hours before an equipment goes for a thorough check(preventive maintenance) say for example 1000 hours on a meter. Unfortunately the galaxy tab (or any tablet) does not have this. So if you frequently do a flashing on your tab you subject the electronic components to unnecessary stress,thereby affecting the life of the components like the battery.
In "normal" everyday use of the tab you will seldom do any restart/reboot of your tab,yet in flashing ROMs as many as 3 reboots is needed. As I don't know how to measure the surge in current during reboot, I can just imagine how high an initial current during startup is generated, thus putting a big strain on the battery.
Unfortunately the battery is not user detachable.
There was an author here in XDA describing himself/herself as an "flashing addict"(or something similar). I would like to appeal to everyone-please don't be a flashing addict.
As for battery issue read here
JUST MY FEW CENTS!
PCdumb said:
Hi,
I don't have sufficient posts to be able to participate directly in that forum, so have no other choice but to raise my queries here.
I've just flashed over from Overcome "Hermes" to "Jupiter". All's well except that the battery performance is quite drastically affected for me.
I've been reading the improved battery life "Jupiter" gets over earlier versions of the Overcome ROMs, but I seem to be experiencing the opposite.
Already did the batt stat wipe via recovery menu. Do I need to so call "run-in" before it reflects correctly? Even if accuracy is one thing... but dropping 3% just on bootup.... is this typical of an uncalibrated battery?
Appreciate any advise here on what I should do. (Apart from a fresh wipe install )
Thanks
Click to expand...
Click to collapse
According to the Tweaks section at the team overcome website, it will take several charge cycles before you notice an improvement after the stat wipe. Try giving it a few days before going any further.
PS Not to question your ability to follow instructions (sometimes we miss things) but did you charge to 100% with the tab off?
Yes, I did charge to 100% with the Tab off.
Now upon reading the instructions once more..... I might have conducted it slightly different from the written procedure.
I unplugged the Tab from the mains, then only booted up and wiped the batt stats before re-booting. Hmmm.... maybe I'll go try booting up while still plugged into the mains, do the batt stat wipe, and re-boot. (all while plugged into the mains). Then only unplug the charger.
Wonder is there any diff in doing so.....
Would definitely try re-doing it with the tab plugged in while doing the stat wipe. And if it doesn't seem to fix it, do go through a few cycles before reverting back to a previous ROM.
It's important to completely drain your battery before recharging it to 100% in order to complete a cycle.
Hope you fix it. Battery life results vary between tab's even if they are used very similarly, I'm running the OVERCOME Jupiter ROM with IMPROVED battery life. I keep my Bluetooth, Wifi and GPS on all the time. I also flash quite often and have not seen a decrease in overall battery life. It seams that each tab is a bit different, hardware wise, than one another. Everything from battery to board it seems is slightly different coming out of the manufacturing process.
Thanks. Will try that out.
But it just seems strange coming from Overcome ver 1.4 (Froyo) which had no batt drain problem.... to Hermes which was better in batt performance.... to Jupiter which I'm experiencing heavy drain.
As I did a NoWipe install, all apps and setting are similar (except the new market app).
I was able to run 2 movies back to back (about 3 hours total) and still have at least 40% life left (usually about 45 to 50%). Now on Jupiter, just fiddling around testing the various features for functionality, plus maybe an hour of NFS (total about 3 hours as well).... the batt drops to about 10% life.
Anyway, I'll re-do the calibration and and give it some time to "settle in". Hopefully, that is all that is needed. (I would hate to have to do a full wipe install... and re-installing all apps)
PCdumb said:
Thanks. Will try that out.
But it just seems strange coming from Overcome ver 1.4 (Froyo) which had no batt drain problem.... to Hermes which was better in batt performance.... to Jupiter which I'm experiencing heavy drain.
As I did a NoWipe install, all apps and setting are similar (except the new market app).
I was able to run 2 movies back to back (about 3 hours total) and still have at least 40% life left (usually about 45 to 50%). Now on Jupiter, just fiddling around testing the various features for functionality, plus maybe an hour of NFS (total about 3 hours as well).... the batt drops to about 10% life.
Anyway, I'll re-do the calibration and and give it some time to "settle in". Hopefully, that is all that is needed. (I would hate to have to do a full wipe install... and re-installing all apps)
Click to expand...
Click to collapse
As mentioned in the Tweaks section, perform the Stat wipe and then two full recharge cycle
recharge to 100% (while the Tab is closed) then drain the battery till it is off then repeat the cycle and you will enjoy it man
Please tell me if you need anything
bongski55 said:
I appreciate the enthusiasm these coding geniuses have in rolling out update after updates in the ROMS yet I am apprehensive about the effect of these frequent flashing on the Galaxy Tab components itself. This includes the battery.
My job involves electronic repair and there is a so called number of hours before an equipment goes for a thorough check(preventive maintenance) say for example 1000 hours on a meter. Unfortunately the galaxy tab (or any tablet) does not have this. So if you frequently do a flashing on your tab you subject the electronic components to unnecessary stress,thereby affecting the life of the components like the battery.
In "normal" everyday use of the tab you will seldom do any restart/reboot of your tab,yet in flashing ROMs as many as 3 reboots is needed. As I don't know how to measure the surge in current during reboot, I can just imagine how high an initial current during startup is generated, thus putting a big strain on the battery.
Unfortunately the battery is not user detachable.
There was an author here in XDA describing himself/herself as an "flashing addict"(or something similar). I would like to appeal to everyone-please don't be a flashing addict.
As for battery issue read here
JUST MY FEW CENTS!
Click to expand...
Click to collapse
where you were hiding this all ? i bet you were so damn angry to say all of this , i never saw you writing more than 3-4 lines , chill out buddy .
@The OP flashing custom roms means battery need to re-life back
bongski55 said:
I appreciate the enthusiasm these coding geniuses have in rolling out update after updates in the ROMS yet I am apprehensive about the effect of these frequent flashing on the Galaxy Tab components itself. This includes the battery.
My job involves electronic repair and there is a so called number of hours before an equipment goes for a thorough check(preventive maintenance) say for example 1000 hours on a meter. Unfortunately the galaxy tab (or any tablet) does not have this. So if you frequently do a flashing on your tab you subject the electronic components to unnecessary stress,thereby affecting the life of the components like the battery.
In "normal" everyday use of the tab you will seldom do any restart/reboot of your tab,yet in flashing ROMs as many as 3 reboots is needed. As I don't know how to measure the surge in current during reboot, I can just imagine how high an initial current during startup is generated, thus putting a big strain on the battery.
Unfortunately the battery is not user detachable.
There was an author here in XDA describing himself/herself as an "flashing addict"(or something similar). I would like to appeal to everyone-please don't be a flashing addict.
As for battery issue read here
JUST MY FEW CENTS!
Click to expand...
Click to collapse
Viewed purely from an engineering perspective, I'm unable to see any significant connection between the flashing of the ROM and a degradation of battery capacity. Further, in the event that the TAB was connected to a charger during the flashing, I can see absolutely no connection at all! Please help me understand your logic.
Ok Back on topic. PCdumb (dude what's with the username lol). Check your app list. It could a new app you or an old app you updated or an app you didnt use before but you use now that is being a battery hog. A small trick I learned is checking apps running services in the background. Go to Settings, applications, running services and check (why is skype working after Isigned out its not a battery drainer but I hope you got the picture).
Thanks for the advise. That was one of the 1st few things I did to check that there's nothing out of the ordinary running in the background and taking up the juice.
Mine's actually draining alot when in usage. Not too sure about when in standby.... will check later.
If after a few charge cycles and the drain is still bad, guess my only next best option is to do a full wipe, re-stock and re-install.....
I did not get any effect from Battery calibration. As expeced. Anybody did actually?
The background services instead might have an effect on power consumption, I agree. But needs numerous testing...
Batt recal did not give me better battery life. There's no difference in the battery performance after 3 recharge cycles.
My tab can at most get slightly more than 5 hours of continuous usage compared to about close to 7 hours on hermes. This is when i dial down the OC from smartass mode to conservative and also put the min freq to 200 instead of 400 which was the setting i was using all the while.
Doesn't seem to be anything else running in the background. On standby overnight, i only lose about 3% which is not too bad. But when in use, that's where the Batt drains fast. Just for comparison, i only lost 1% at most for overnight standby of about 7 hours when running hermes.
Guess I'll have to live with this if i want the speed and smoothness. Still contemplating whether to restock and do a clean flash.
PCdumb said:
Batt recal did not give me better battery life. There's no difference in the battery performance after 3 recharge cycles.
My tab can at most get slightly more than 5 hours of continuous usage compared to about close to 7 hours on hermes. This is when i dial down the OC from smartass mode to conservative and also put the min freq to 200 instead of 400 which was the setting i was using all the while.
Doesn't seem to be anything else running in the background. On standby overnight, i only lose about 3% which is not too bad. But when in use, that's where the Batt drains fast. Just for comparison, i only lost 1% at most for overnight standby of about 7 hours when running hermes.
Guess I'll have to live with this if i want the speed and smoothness. Still contemplating whether to restock and do a clean flash.
Click to expand...
Click to collapse
If you want to confirm that JUPITER is the reason that you are experiencing poor battery life, try re-installing a previous version that you feel worked better for you. Maybe reverting back to a previous version may yield better battery results, and I sure hope so, this way you will know if it's the ROM or other elements affecting the abnormal battery drain.
If you do see an increase in battery life, try flashing JUPITER again, see what the results are. I don't know if flashing and re-flashing will have a negative long term effect on your SGT, I know that I flash every time a new release is out (Stock safe, cooked ROM, Kernel) and if i'm not happy with the release i go back to a proven one by flashing another three times (stock safe, cooked ROM, Kernel) and so far I have not had any (knock on wood) abnormal battery activity.
It's worth giving it a shot (if you haven't already).
EDIT: I know, I know the proper sequence is stock safe, kernel, rom.
after week of using the Overcome ROM i can confirm that the battery performance is between 85 and 90% from the Orignial stock ROM performance
No problem since this is normal as we are using a cooked ROM
bongski55 said:
I appreciate the enthusiasm these coding geniuses have in rolling out update after updates in the ROMS yet I am apprehensive about the effect of these frequent flashing on the Galaxy Tab components itself. This includes the battery.
My job involves electronic repair and there is a so called number of hours before an equipment goes for a thorough check(preventive maintenance) say for example 1000 hours on a meter. Unfortunately the galaxy tab (or any tablet) does not have this. So if you frequently do a flashing on your tab you subject the electronic components to unnecessary stress,thereby affecting the life of the components like the battery.
In "normal" everyday use of the tab you will seldom do any restart/reboot of your tab,yet in flashing ROMs as many as 3 reboots is needed. As I don't know how to measure the surge in current during reboot, I can just imagine how high an initial current during startup is generated, thus putting a big strain on the battery.
Unfortunately the battery is not user detachable.
There was an author here in XDA describing himself/herself as an "flashing addict"(or something similar). I would like to appeal to everyone-please don't be a flashing addict.
As for battery issue read here
JUST MY FEW CENTS!
Click to expand...
Click to collapse
WOW ! This was an eye opener for me...
Thanks for clarifying this...... I didn't know this was so bad for the hardware ....
Sent from my GT-I9003 using Tapatalk
PCdumb said:
Batt recal did not give me better battery life. There's no difference in the battery performance after 3 recharge cycles.
My tab can at most get slightly more than 5 hours of continuous usage compared to about close to 7 hours on hermes. This is when i dial down the OC from smartass mode to conservative and also put the min freq to 200 instead of 400 which was the setting i was using all the while.
Doesn't seem to be anything else running in the background. On standby overnight, i only lose about 3% which is not too bad. But when in use, that's where the Batt drains fast. Just for comparison, i only lost 1% at most for overnight standby of about 7 hours when running hermes.
Guess I'll have to live with this if i want the speed and smoothness. Still contemplating whether to restock and do a clean flash.
Click to expand...
Click to collapse
After reading all this superb discussion....
I would just recommend you to go back to your older rom.....
Its forbthe best....
Sent from my GT-I9003 using Tapatalk
I do get 4 to 5 hours of continuous use with overcome Jupiter, mostly browsing the web over
WLAN or umts. Hermes release didn't gave me so much more juice, probably 5 hours.
In the background I have emai push, contacts and calendar sync and some instant messaging apps, if I switch off all that I might get an hour or so more.
PCdumb said:
...On standby overnight, i only lose about 3% which is not too bad. But when in use, that's where the Batt drains fast. Just for comparison, i only lost 1% at most for overnight standby of about 7 hours when running hermes...
Click to expand...
Click to collapse
Wow, maybe your tab is one of the ones with a battery from the bad batch, and it's finally on its way out. I upgraded from the stock AT&T Rom to Overcome Jupiter, and on Airplane Mode with all stock settings (no overclock or undervolt), mine only drops 1% in standby over 14 hours and I can get about 5 hours of video watching straight with the brightness on max before it dies!
DarkPal said:
A small trick I learned is checking apps running services in the background. Go to Settings, applications, running services and check (why is skype working after Isigned out its not a battery drainer but I hope you got the picture).
Click to expand...
Click to collapse
I also been experiencing a major increase in battery drain even after doing a couple wipes exactly according to the tweak guide. I went from about 24 hour normal use down to 6-8 hours normal use.
Checked the services as per your suggestion above and found a couple major battery drainers running. Skype and Yahoo but also Google+. What I dont understand is why Skype and Yahoo would be running even though I had not started either since at least several re-boots ago. I had Skype and Yahoo installed for quite a while Google+ is a new one. Anyway I killed all of them and now and will see what happens next.
Not sure thought that this is all there is to the issue. Recahrging is finiky as well. I can turn off the tab and let it charge all night just to find that it charged to about 70% if I re-plug it might charge to 90%-95% and then if re-plug it might get to 100%. The drain from 100% to 60%-70% is extremely fast and still quite fast from there. On one occasion after complete drain I couldnt get it to start charging at all for about 5-10 minutes. I was checking power, cables, connections and starting to panic when all of a sudden it started to charge.
Any advice on possible reasons or solution woud be appreciated. Not sure I want to go beck to stock ROM and un-root just to take it to service center for repairs.

Z1 - no offline cores

Is it normal that on Android 5.1.1 .236 with stock kernel are always available online all 4 cores? For earlier versions of Android cores they were excluded or included depending on demand. After replacing the battery, the phone works normally, up to 4 working days and ~ 4h enabled screen. The problem, however, is notorious heat up the phone. Temperatures of 60-70 ° C when creating a backup in recovery rather should not occur. Maybe a custom kernel?https://forum-lw-1.xda-cdn.com/images/smilies/rolleyes.gif
Hi,
If the cores are always working at a reasonable speed something is not right with your mobile. A custom kernel would be of good use though, I've been using one to disable two cores always -- since my Z1 became a backup device -- and that made it heat up a bit less and the battery last a little longer.
Another possibility of the heat is that when you replaced the battery you didn't seal it off well, or somehow caused some damage to the heat dissipation, if that also happened before I mean. So if you could try remembering how it was before the battery replacement, it'd be of good help.
All the best,
~Lord

Categories

Resources