yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] geenyous:
Or freeze one half of the user apps (I would go with user apps first, after checking maps of course) and then test. If you have no more drain, then unfreeze half of the frozen half and check, if you still have drain the culprit is in the unfrozen half, so unfreeze the initially frozen half and then freeze half of the initially unfrozen half and check. Continue until you found the issue. This is way faster and the most efficient way to check ;)

Or, do what I did, just don't bother and update to ICS CM9 v1.2 by tytung, I had a very nasty ~101mA drain every 4-6 mins when on cellular data while on GB, now on ICS with all the same apps everything is good. :confused:

I have no idea what it was as I have made several fresh installs on GB, but at the end of the day I am really glad I didn't waste more time on that issue. Especially, since ICS is brilliant anyway :D
[HD2 Android NAND Development] Germypan:
Hi DM. Thanks, i tried your 3.9 kernel, but as 3.8 version, it crashed on boot animation with my CM7 rom. Have you any ideas? with 3.3 version i don't have problem and my rom is very smooth and fast.

Sorry for my bad english

Germy
[HD2 Android NAND Development] corrsea:
I've just experienced a 60 - 70 mha battery drain. Better battery stats indicates 'proximity' as a kernel wakelock.
[HD2 Android NAND Development] themadproducer:
Normally I would agree. But if you have many apps (eg 150-200) as many of us do...including system apps, then freezing smaller groups may get you there faster. Last time it happened to me....and my 200 apps, I froze a group of 1-10, and then 11-20 and boom...drain was gone. it was 11-20, and YES it was Google Maps/Nav ironically. Could have worked against me if I started at the opposite end! :D

Wait...unless Titanium allows BATCH freezing? if it does, then hands down, go 50/50 all the way. In any case....you WILL find the culprit(s) using the FREEZE method.

---------- Post added at 02:12 AM ---------- Previous post was at 02:07 AM ----------

So, geenyous, how is ICS? I mean, we've been chasing the "fixit" carrot for Froyo and GB for a long time and I have followed Tytung's thread every now and then, and although th OP says everything works,...users seem to be constantly reporting bugs...not that they are all valid...maybe many user based issues... but it sure seems like there are many. (not to get off topic here)

---------- Post added at 02:13 AM ---------- Previous post was at 02:12 AM ----------

Perhaps one of your apps that uses Proximity Sensor is responsible.
[HD2 Android NAND Development] Bologna:
Using system tuner pro and setcpu I've noticed that I can never reach 96 mhz even if choosed as minimum freq...Opening your cpu voltage script I've seen why...but I can't understand if it's a choise made for other rom stability or if I can add a code line to make it work for ICS...

I'm going to test adding this line and report back
[HD2 Android NAND Development] havard20009:
big battery drain :( 68 mlA

back to 3.8 :(
[HD2 Android NAND Development] bmans:
можно ли реализовать в ядре затухание экрана перед его выключением?

is it possible to include in the core fade screen before it turning off?
[HD2 Android NAND Development] geenyous:
Yes, TB does allow batch freeze of course, otherwise it would be a real pain ;)

Well, what shall I say, I once again love my HD2 even more than before :D

ICS is great, you can check our Wiki below for any issues, but most if not all of them are very minor to me and a workaround solution exists for all of them, except Flash playback of web content due to HW acceleration and YouTube LQ playback (oddly enough, HQ works). You will of course also loose some CM functions as permission revoking (I am using droidwall instead to cut off internet access of apps I don't fully trust or I think they don't need it) and some of your apps might not be ICS compatible (I heard viber to be one of them), but all of mine work.

EDIT: Oh yeah, camcorder is not working propperly, but I only use cam, not camcorder.

I'd suggest you make a nandroid backup, flash a 200/5 cLK or MAGLDR partiton and give it a try. I for one would never go back to GB again.

Enough OT, visit us in tytungs ICS thread for more info and who knows, maybe soon our boss tweaker will also have an ICS ROM in his collection? ;)

Maybe I don't understand you but I could choose 96 in ICS and it was also using it as setCPUs Time in State tab confirmed. SmartassV2 btw.
[HD2 Android NAND Development] Bologna:
Thanks to you I've monitored again...

now 96 mhz works fine without any changes :confused:

Yesterday I've never reached less then 126 (ondemand)

Checked now with smartassv.2 and 96 works!

switched again to ondemand and 96 is still reachable ...

thank you for avoiding me a new flash :)
[HD2 Android NAND Development] Yank555:
Hi,

About battery drain, forget my previous post, it is not (directly) bluetooth induced !

I ust place a call (no bluetooth involved), the wakelock is there again !! And I have been wakelock free for the whole moring, received and sent SMSs / Emails, but no call.

It is not bluetooth induced, but placing the call via bluetooth had the same effect obviously ! Sorry for my mistake !

No proximity in BatteryStats yet (which I had in the top-list of wakelocks the first time, this being the 3rd wakelock in less than 24 hours of 3.9).

I will leave the wakelock going for a little bit longer, I just set a custom ref point in BetterBatteryStats.

Will report back as soon as I have more.

JP.

-----------------

Edit : Find attached a BetterBatteryStats dump file.

See this under Kernel Wakelocks :

"proximity" (): 5 m 13 s (313 s) Cnt: (c/wc/ec)2/0/2 79.8%
[HD2 Android NAND Development] cheetaoncocain:
1600 mah battery support?

What needs to be done to support 1600MAH battery on HD2 with Dorimanx rom and Kernel (3.0.7 - 3.9 respectively)?

Thanks in advance for your help, i bought 2 batts on e-bay, but they show up as 1230MAH on all battery apps and statistics.
[HD2 Android NAND Development] Hinnne:
i like google maps but why does it always start without useing. how can we stop it without deinstalling it? i do not want to use auto start manager or any other system app to stop it from starting.

thx
[HD2 Android NAND Development] vlad2277:
I had a lot of battery drains, but BT drain is not aonly kernel related but also ROM, I'm using latest Dorimax ROM, on CLK, and 3.9 Kernel, T-Mobile HD2, no extras(Swap/Overclock)

HAVE NO BT DRAIN AT ALL, VERY LOW POWER, After switchich to his ROM and Kernel, 2 days ago, I'm really surprised.

I had random reboots, but hopefully it solved, with manual network selection, good for almost a day now, really smooth.
[HD2 Android NAND Development] dertester123:
I think its linked to location services that most apps use.

Try unchecking location services, reboot and let it settle a few minutes. Then turn back on and wait a while.

Also configuring the google news/weather app can prevent this app from draining.

Helped me most of the times now with standby drain.
[HD2 Android NAND Development] corrsea:
I can confirm that there is a kernel wakelock of 60 produced by any app that utilises the proximity sensor (includes phone calls obviously). I have easily reproduced it with a number of sensor a apps from market.
[HD2 Android NAND Development] themadproducer:
As vlad2277 stated, it is not necessarily simply a Kernel issue.

I do not have high drain wakelocks (60-70ma) with either Proximity Sensor usage or BT Calling. (Running Typhoon 3.7.6) I have never had it with any of the Dorimanx Kernel releases. What rom are you using Corrrsea?
[HD2 Android NAND Development] corrsea:
Nexus 1 hd2. However I've tested every dorimanx kernel since 2.6 on this ROM and never experienced this particular kernel wakelock before. It does not occur with tytungs or fikrets kernels either so I doubt its the ROM.
[HD2 Android NAND Development] themadproducer:
So, there could be a change in the Kernel that the Typhoon rom is not affected by, whereas your Nexus 1 rom is! Did you try wiping dalvik and partition caches?

---------- Post added at 02:36 PM ---------- Previous post was at 02:16 PM ----------

Hey Dorimanx,

Did we lose FAST CHARGING ability in one of the recent Kernel updates. The reason I ask, is that my buddy told me his is not charging at high rate recently. So I checked my HD2 on 3 chargers (2 of which I hand wired for fast charge) and my HD2 is sitting at around 50%....and normally, a fast charge will bring 850ma give or take, whereas I am stuck around 300-400ma. UPDATE: actually it's even lower than that...125-200ma in Standby. (2 Kernels tested... 2.6 and 3.9)
[HD2 Android NAND Development] warrenb213:
on my 35 git i was considering removing the "china" battery detect. that should allow all chargers to fast charge as much as they can.
[HD2 Android NAND Development] themadproducer:
LOL....Warren, I just happen to be using my backup battery...same with the other hd2....and they happen to be non stock "China" battery. So, I am about to test with the stock battery and report back. If that is the case, then +1 to remove the detection code.

UPDATE:

I took out one of the 1600mah Jin Dian batteries and placed it in my desktop cradle charger. The charging light did NOT change from blue to RED as it normally would. So I pulled out my Volt Meter and tested the battery. It's rated 3.7v but had a charge of 4.1v. So indeed it was already max charged AND THEN SOME. So the HD2 was still trying to charge at a much higher rate than a typical Trickle Charge. I pulled out the other HD2 Jin Dian battery, pretty much the same thing. I can't test the charging rates for the stock batteries right now because they are ALREADY fully charged. I will update later.

UPDATE:

Warren and Dorimanx,

I'm back to the stock battery, I drained it down to 80% then placed it on one of my chargers.

BAMM...800ma+ no problem, back to normal charging rate. CONFIRMED. (and now it's at 96% charged and 200ma charge rate...perfect) (99% @66ma now) (100% @ 36ma) (now 100% @17ma)

So there is code that potentially could be disasterous for those using "China" batteries. The Jin Dian batteries have always worked flawlessly for me and charged pretty much normally in the past. I know switching from 1200, to 1600, to 2400mah batteries can cause calibration issues, but never slow charging...or in this specific case, it resembled OVERCHARGING. If it was overcharging as it seemed, we should be CONCERNED. My Desktop Cradle charger seems to recognize that the Jin Dian battery is fully charged to the MAX,...whereas the HD2 did not...and seemingly...continued to charge at over 100ma+. I say seemingly because it showed this figure in Current Widget.
[HD2 Android NAND Development] corrsea:
Yes wiped both caches and fixed permissions. Can't reproduce it on pure CM7 ROM. Wonder if its just HD2 nexus 1 or all aosp roms?
[HD2 Android NAND Development] cheetaoncocain:
china batt recognition (feipusi)?

Does your HD2 show the 1600MAH on any application? I am Using battery monitor pro, and all batts show up as 1230MAH.

Do you know what can be done so the phone will detect the 1600?

Thanks in advance
[HD2 Android NAND Development] sam razzy:
Everything is fine using this Kernel ..

EDIT : waiting for new 4.0 version :)
[HD2 Android NAND Development] Yank555:
Don't know for other AOSP, but since I'm using NexusHD2, I'm back to 3.2 which works just fine, but unforunately has higher drain then 3.9 (when not wakelock'ed) and isn't as fast...

A pitty, waiting for 4.0 in the hope it will solve this issue.

On the other Hand, what could be the problem with the proximity sensor ? Would there be some lib to change ?

JP.
[HD2 Android NAND Development] Elmar1801:
Except zram no problems with V3.9.

- bluetooth works fine with my car kit

- battery drain normal (gps, bt, wifi on)

- charging with standard and chinese (1500mAh) battery ok (up to 850mA)

- small wake up lag as ever with all other roms and kernels

waiting for new 4.0 version with fixed zram, but theres no hurry.
[HD2 Android NAND Development] themadproducer:
I have not checked but if the problem with charging gets fixed, then I will personally test the 1600 and 2400 batteries out and give a report.

Guessing from experience, I would think that if you use a 1600mah battery, you may need to calibrate it first to maximize it's potential as the OS doesn't immediately know how much capacity it is. PLEASE...someone feel free to correct me if I am wrong.

Further more, if you swap batteries often, it may be beneficial to stick with 2 or more of the same brand, capacity and the same age. An older battery will not hold as much as a new one .....and unless I am mistaken, it's the calibration action that informs the OS as to the battery's true capacity. There are free calibration app at the market. No two batteries are identical even if they are the same rating.
[HD2 Android NAND Development] corrsea:
Battery monitor widget pro allows you to store profiles for multiple batteries. I've found it quite useful. I can't remember if its available on the free version.
[HD2 Android NAND Development] themadproducer:
I would like to summarize these possible issues with 3.9:

- chinese battery charge rate and overcharge issue (at least with Typhoon rom)

- Zram (if you think you don't have Zram issues, try loading 2 or 3 heavy games into ram...like Angry Birds at 60-80mb, and you will experience the freezing issues...and not because your running out of free ram)

- 60-70ma wake lock for some Roms due to Proximity sensor based on user reports

- after fresh boot, cpu scaling values are not matching those of Setcpu....I believe due to Hard Coding (Dx mentioned this) My boot boost scripts are customized to settle on 96-998mhz after boot but it doesn't work. I end up with 245-xxx? The workaround is to move the SetCpu sliders up and down and it will catch and resolve.

- Certain overclocked freqs are now unstable for me at least with Typhoon rom. Quadrant tests can easily trigger the OS to freeze on these OC speeds. I haven't tested them all, but I know earlier kernel versions where stable for me. I always use(d) SmartAssV2.

---------- Post added at 01:31 AM ---------- Previous post was at 01:29 AM ----------

Hey, that sounds good. But does it relay this information to the OS....meaning when the OS says you have 50% battery left, can the OS know which battery you are using based on Battery Monitor's widget? Ultimately, it's the OS that needs the battery capacity info!!
[HD2 Android NAND Development] corrsea:
I've always assumed so. You do have to manually switch profiles when you switch batteries though.
[HD2 Android NAND Development] themadproducer:
Perhaps you can test it and report back.

It would have to specifically rewrite the file that holds the battery info for GingerBread. (I can't remember what the name of the system file is)

Here is a line from the feature list...

Manually resets battery calibration/statistics on rooted phone

That's a bit misleading grammar wise. Does it mean you have to MANUALLY press a reset button to store new measured battery calibration from the widget to the OS?
[HD2 Android NAND Development] djsolidsnake86:
3.9 and miui v4: headset don't work
[HD2 Android NAND Development] Specktäter:
Hello, since I have updated from Dorimanx 3.2 to Dorimanx 3.8 with my Typhoon CM7, LCD Density doesnt work anymore. The Display stays black and the Phone reboots after a while without changed density. With 3.9 I have to remove the Battery. Is this a known Issue? What am I doing wrong?

MfG
[HD2 Android NAND Development] Axel85:
Yes I have the same problem.The solution is to manually edit the build.prop...
[HD2 Android NAND Development] icke:
+1

Same on IceCreamTosti v0.3.
[HD2 Android NAND Development] fuorionda:
My report

Langhtang latest miui with dorimanx kernel 3.8 3 - 8 mA on standby

same rom with kernel 3.9 60mA on standby

reverted to 3.8 3 - 8 mA

Ps. CLK
[HD2 Android NAND Development] cheetaoncocain:
I am currently trying to calibrate and will keep testing several different scenarios to find the correct way to do this.

Thanks for your time to answer.

Cheers
[HD2 Android NAND Development] mech5243:
A lot of people are reporting high drain.... i dont have such problems... on standby i get 4-5 mA while in stand by with wifi on i get something like 14mA... I am using typhoon 3.7.6 with 3.9 dorimanx kernel...
[HD2 Android NAND Development] xjjk:
I also have not noticed high drain. Using the latest version of Dorimanx ROM. I didn't like the lag when cpu was set to on demand so I switched to smartassV2 and now it seems quite smooth and responsive. No connectivity issues or robot calls yet.
[HD2 Android NAND Development] petbede:
Hi there.

Kind u pls kindly tell me the SETTINGS u use using DorimanX Kernel 3.9 with TyphooN 3.7.6

Thanks.

PEACE!!!
[HD2 Android NAND Development] Hinnne:
after installing an app phone freezes with k.3.9

had to pull the battery.

so hope this will be solved in 4.0

back to 3.8
[HD2 Android NAND Development] Looki75:
On Typhoon v3.7.0 (CM7.1), using kernel v3.9, I have only issues with zram as already longly discussed in this thread.

No wakelock or 50-60mA drain in standby... Actually it's the contrary: very consistent and good battery drain: with 3G phone network with occasional 3G DATA connection and occasional wifi, it drains 1.5% per hour average over 10 hours, which is not bad for me, with 2 e-mail programs syncing each 30min / 1h.

Also, I regularly use BT car system, with voice speed dial, and this does not cause any subsequent drain.

Looking forward to test kernel v4.0! :)
[HD2 Android NAND Development] petbede:
Hi there.

Pls can u tell me the SETTINGS you select when installing DorimanX Kernel 3.9 on you TyphooN 3.7.0

Thanks.

PEACE!!!
[HD2 Android NAND Development] maxpiva1:
Hi could you please help me?

Using dorimanx last rom with kernel 3.9

Not sure when it happened since first installation of the rom but suddendly audio results incorrect, not bad quality just higher frequencies, seems like voice and music go faster!!! This happens with voip apps and music!

What's happened? Cleaned cache and dalvik,reinstalled the rom but still issue exist!

Don't know what to do more..

Please help! Thanks
[HD2 Android NAND Development] Looki75:
I select:

1/ NO-2WAY REC

2/ CM7

3/ Yes

4/ Yes

5/ NO ZRAM (because kernel 3.9 has a zram issue)

6/ Busybox YES

7/ Fix VPN YES
[HD2 Android NAND Development] petbede:
Hi there.

Thanks. I also click the THANKS Button.

PEACE!!!
[HD2 Android NAND Development] oleg1242:
it work's too fast and smoth! tnx for that! But

have problem with 2G/3G

=> it doesn't work on any kernel (3.1;3.6;3.9)

I select:

1/ NO-2WAY REC

2/ CM7/Miui

3/ Miui

4/ cLk

5/ NO ZRAM

6/ Busybox YES

7/ Fix VPN YES
[HD2 Android NAND Development] chris5s:
Using this kernel with MIUI 2. 1. 20 and it is very stable @ 1. 3ghz.

Drain on standby is 2-4ma, good enough for me.

Thanks for your work on this kernel, much appreciated.

Peace

Sent from my HD2
[HD2 Android NAND Development] dorimanx:
kernel 4.0 is online,

i hope i have fixed to drain.

have fun.

Sent from my HD2 development phone.
[HD2 Android NAND Development] Faith_G:
I've got 4.0 running with xylograph's ice cream tosti ROM. Seems OK so far. :)
[HD2 Android NAND Development] ric69:
Hi, I think something is wrong on 4.0 with cLk/miui --> no 3G and robotic voice.

Now I'm back to 3.3 all is fine :o
[HD2 Android NAND Development] corrsea:
Same on nexus1hd2 Clk. No data, wifi fine though. Don't know about robotic voice as I did not make any calls. The proximity wakelock is gone though :-)
[HD2 Android NAND Development] Hinnne:
k.4.0 rom3.0.8

no mobile data 3g or h.

nothing happens if i turn data on off. no icon appears.

wifi data working.

back to k.3.8

please fix this
[HD2 Android NAND Development] Elmar1801:
After testing V4.0 half a day:

MAG / CM / BUSYBOX / ZRAM / NO VPN

- zram not working like before

- apps sometimes fc on start (facebook, gps status, market, maps...)

- bt fc on some boot

- fast!

- no high drain

Back to V3. 9
[HD2 Android NAND Development] Dam4rusxp:
Like the others I have no mobile data connection with v4.0. I looked through the log and this came up every few seconds:

E/pppd ( 2057): Couldn't set tty to PPP discipline: Invalid argument

I'm on CLK 1.5-r1 with Typhoon CM7 3.7.6. Back to 3.8... hope this gets fixed soon.
[HD2 Android NAND Development] jolas:
Running kernel 4.0 for a couple of hours, without problems! :)

EDIT:

As for zram, I don't know if it is really working ot not, because in zram_stats, I always get the same results (read and write numbers are 1, etc)...
[HD2 Android NAND Development] jack928:
can i remove the swap in your kernel?can you ad this option in the zip?

the data connection in miui don't work in the 4.0 can you fix it?
[HD2 Android NAND Development] legolas93:
Me too :(

Dori..this kernel it's amazing with its speed :) but in tytung Ics data don't work
[HD2 Android NAND Development] Yank555:
+1 on Tyting's NexusHD2 GB v3.2a no data (MAGLDR)
[HD2 Android NAND Development] dorimanx:
Uploaded new Kernel 4.1

I think i fixed the CLK DATA connection!

And added some more boost :)

Have fun and report back!
[HD2 Android NAND Development] jack928:
how i can remove the swap?

in the tytung r14 if i write ''free'' in the terminal emulator don't compare swap in your yes .....the swap it's in the sd card?
[HD2 Android NAND Development] dorimanx:
if you have CM7 then go to settings > cm7 mod > performance > compcache and set to 0

if you have any other roms,

and you installed the extra zram 357mb ram patch, then go to /system/etc/init.d/

and delete the 131MBzram

reboot, and no swap any more.
[HD2 Android NAND Development] jack928:
tnx i think you can add this in the kernel...
[HD2 Android NAND Development] Yank555:
Thanx Dorimanx ;)

I also had the Data issue, but I'm on MAGLDR ?!

Will install 4.1 and report back as soon as I'm done :D

JP.
[HD2 Android NAND Development] Dam4rusxp:
Works again for me. Thanks!
[HD2 Android NAND Development] Looki75:
Thanks Dori!

Could you tell us: did you change something about zram?

If not yet, do you plan to fix zram (not properly working from v3.8)?

Thanks

PS: if you need details about the bug, I can PM you detailed report!
[HD2 Android NAND Development] dertester123:
Hi,

i use clk 1.5 on Hyperdroid CM7 and each time i install the kernel i am booting back into hboot with "boot image heador" error.

Our initrd.gz in initrd-Custom folder...

I choose.

-no 2-way-rec

-cm7

-same

-same

-clk version

No zram/busybox/vpnfix.

I already asked in clk thread and on suggesion about bad blocks i moved boot partition ( i think kernel is there?) and made it bigger... Still the same..
[HD2 Android NAND Development] madsponge26:
downloading and testing.. seems good kernel in my miui v5.1 stable..
[HD2 Android NAND Development] sam razzy:
Is this v4.1 support ICS Rom?
[HD2 Android NAND Development] Mappazza:
...don't work on my HD2 with Hyperdroid and custom initrd.gz...no data, and the device freeze...3.9 was perfect...back to past...
[HD2 Android NAND Development] dorimanx:
zram wasn't changed...

only global settings...

what is the problem? all working ok for me..
[HD2 Android NAND Development] sprongebob:
On my ndt miui freez with 4.1

Back to 3.8 i have no freez
[HD2 Android NAND Development] jjmmll:
+1

3.9 or 4.0 work well
[HD2 Android NAND Development] Yank555:
Hi,

On NexusHD2 GB v3.2a using kernel v4.1 Data is working fine again.

As for wakelock in 3.9, I've simulated what caused it systematically, it's gone as well !!!!

Thanx so much for your great work :D :D :D

JP.
[HD2 Android NAND Development] nemuro:
Tried 4.0 with the redux gb rom in my signature. Worked fine.

Rebooted after I updated to 4.1 and when it booted up, the starting wizard came back up as if it were a clean install of the rom. The apps seem to still be installed but they would all fc upon startup. Launcher pro, yahoo messenger, facebook, everything.

I rebooted in recovery again and flashed 4.0 back. Now it it is back to normal except for google maps that fc upon startup. I tried installing zram in both scenarios.