Hi Everyone,
This is a recompiled version of Hastarin’s HD2 Android kernel that can be applied to most HTC HD2 RAM Android builds including DarkStone’s SuperRAM 1.5 build. The additional benefits over most existing builds is the inclusion of CIFS, or the ability to use CIFSManager to mount and unmount shared folders on your local network.
Download, installation instructions, and FAQ
If anyone needs any other version, non-oldcam, etc, just let me know and I'll add it to the downloads.
Thanks,
B.
will try this asap
Nice, cifs is very useful for me.
Thank you for compiling.
I should also point this out just in case, though I don't think it had anything to do with a kernel switch, as I was changing a million different things as I built the kernel. When I started using SuperRAM 1.5, my HD2 idled at about 7MA. Once I updated the kernel, and did a million other things, I was idling at about 60MA. After resetting back to the original data.img from SuperRAM 1.5, it dropped back to 7MA. All of this was using the same, attached, kernel.
So, as stated, it's obviously not anything to do with the active kernel, but in case anyone else has the problem, I would recommend going back to the original data.img and re-setting up.
Thanks,
B.
this work for Cedesmith new Initrd?
Thanks heaps ^_^
Sent from my HTC Desire using XDA App
Thanks! I do have something to ask, though - could cifs be compiled as a module so we could load it externally via insmod?
I don't know whether this is related to kernel or not.
I love the latest RAM builds, but with all these builds, my SE Bluetooth stereo headset hard buttons aren't working. Can u fix this issue.
Because of this small issue I cannot use these builds. Thanks in advance
Sent from my HTC DesireHD2 using XDA app
Good job !
This is useful for me, and how about "nls_utf8.ko" module?
We need utf8 for CIFS manager.
Is this build the same as darkstone superram
Sent from my HTC Desire using XDA App
Fmstrat said:
I should also point this out just in case, though I don't think it had anything to do with a kernel switch, as I was changing a million different things as I built the kernel. When I started using SuperRAM 1.5, my HD2 idled at about 7MA. Once I updated the kernel, and did a million other things, I was idling at about 60MA. After resetting back to the original data.img from SuperRAM 1.5, it dropped back to 7MA. All of this was using the same, attached, kernel.
So, as stated, it's obviously not anything to do with the active kernel, but in case anyone else has the problem, I would recommend going back to the original data.img and re-setting up.
Thanks,
B.
Click to expand...
Click to collapse
I have been testing SuperRam 1.5 with current kernel patch from original thread last couple of days, and I have been monitoring current usage since yesterday evening with different options. From what I have seen so far it will stay 6/7/8amp for some time and if you use the HD2 (browser/maps) for few minutes and put it in standby again, it might go back to 60amp. I reproduced this several times.
The most reliable I got was when I disabled mobile data, auto sync, GPS, BT, Wifi, but 3g is on. it consistently gives 7amp so far.
Current widget is set to log every 180sec.(if you set lower this widget might itself will interfere with readings as it has to write to SD card)
I think there is a bug in sync or mobile data which is causing this, it can't be just any change in data.img.
windroidHD said:
I have been testing SuperRam 1.5 with current kernel patch from original thread last couple of days, and I have been monitoring current usage since yesterday evening with different options. From what I have seen so far it will stay 6/7/8amp for some time and if you use the HD2 (browser/maps) for few minutes and put it in standby again, it might go back to 60amp. I reproduced this several times.
The most reliable I got was when I disabled mobile data, auto sync, GPS, BT, Wifi, but 3g is on. it consistently gives 7amp so far.
Current widget is set to log every 180sec.(if you set lower this widget might itself will interfere with readings as it has to write to SD card)
I think there is a bug in sync or mobile data which is causing this, it can't be just any change in data.img.
Click to expand...
Click to collapse
+1 to this. I have the exact same experience after days of testing. If I leave the phone alone in airplane mode with only wifi enabled, the phone lasts for like 5 days, and keeps 3-7mA idle readings. If I refresh the browser, it stays at 60mA for a while, but then eventually lowers back to 6/7mA after a while.
I'm also on Froyo RAM edition 1.5.
Is extended battery supported in this kernel?
windroidHD said:
I have been testing SuperRam 1.5 with current kernel patch from original thread last couple of days, and I have been monitoring current usage since yesterday evening with different options. From what I have seen so far it will stay 6/7/8amp for some time and if you use the HD2 (browser/maps) for few minutes and put it in standby again, it might go back to 60amp. I reproduced this several times.
The most reliable I got was when I disabled mobile data, auto sync, GPS, BT, Wifi, but 3g is on. it consistently gives 7amp so far.
Current widget is set to log every 180sec.(if you set lower this widget might itself will interfere with readings as it has to write to SD card)
I think there is a bug in sync or mobile data which is causing this, it can't be just any change in data.img.
Click to expand...
Click to collapse
In regular SuperRam (and other builds i think) I notice 60ma or 20ma standby drain after using the browser for a few minutes, especially if I was watching flash content, but it eventually settles down to 7ma. I have not added this kernel or tried it yet, I am just mentioning this because what you described there is what I see with my config normally.
will try this out! Thanks!
Can you also post the non-oldcam version? cifs supports works ver well.
Thanks!
pablo71 said:
In regular SuperRam (and other builds i think) I notice 60ma or 20ma standby drain after using the browser for a few minutes, especially if I was watching flash content, but it eventually settles down to 7ma. I have not added this kernel or tried it yet, I am just mentioning this because what you described there is what I see with my config normally.
Click to expand...
Click to collapse
Agreed, I noticed this running SuperRAM 1.5 prior to changing kernels as well.
Renegade_Rulez said:
Is extended battery supported in this kernel?
Click to expand...
Click to collapse
Yes. oldcam_eb stands for "Old camera library files with extended battery support."
Renegade_Rulez said:
Can you also post the non-oldcam version? cifs supports works ver well.
Thanks!
Click to expand...
Click to collapse
What build would this be for? Just want to make sure I include the right things.
Thanks,
B.
Related
Was getting several data freezes every day (5 to 7 every day). I installed a free app from the Android Market called DATA ON DEMAND which is supposed to switch your data from 3G to 2G in order to conserve battery when phone is idle in sleep mode (screen off). This app did not work on my device. It would kill the data completely after phone was put to sleep and data nor voice would restore unless the phone was restarted. Needless to say, I uninstalled the app and rebooted my phone and strangely, my phone has not dropped data even ONCE in 5 DAYS. I have tested this on 3 other HD2's and all followed the same pattern. I have only tested them for the last 3 days though. My exact setup as far as OS's is:
Windows Mobile Rom: Omega v14 WWE XT CHT
Radio: 2.14.50.04
Android Rom: mattcevoleo1.0.1
Kernel: [email protected] (r1)
Please post if this works for you if you decide to try it. I am curious. That was probably the only real downside to my daily HD2/Android usage.
When you say data freeze, do you mean the issue with the up data arrow getting stuck?.
my build too i am using mattc 1.8 with sense and when data is on the arrow stops and i lose data happen to me 5 time a day
cardoflex said:
my build too i am using mattc 1.8 with sense and when data is on the arrow stops and i lose data happen to me 5 time a day
Click to expand...
Click to collapse
Same here, I've also noticed the phone uses a lot more battery power when the data connection is on. Maybe its linked?
Thanks to the OP for the possible solution.
tkato said:
When you say data freeze, do you mean the issue with the up data arrow getting stuck?.
Click to expand...
Click to collapse
yes, that is what I am refering to. sometimes both arrows would get stuck.
Since updating to hastrian 7.1 I don't see any improvements to my battery life and data like everyone is taking about is still a problem, if some one could correct this it would be three best setup ever
It not solve my data connexion problem, i have installed the apps, set it to AUTO, reboot, delete the apps, and now everything is same than before i install the apps... nothing better...
using the Mdeejay eVo Sense v. 1.0 Warm|3.29.651.5|[kernel: hastarin R7.1] release with the libhtc_ril_wrapper.zip updated (9/28)
Ill try this on my 1.8 and my evo 1.0.1, will report back
k2trill said:
Was getting several data freezes every day (5 to 7 every day). I installed a free app from the Android Market called DATA ON DEMAND which is supposed to switch your data from 3G to 2G in order to conserve battery when phone is idle in sleep mode (screen off). This app did not work on my device. It would kill the data completely after phone was put to sleep and data nor voice would restore unless the phone was restarted. Needless to say, I uninstalled the app and rebooted my phone and strangely, my phone has not dropped data even ONCE in 5 DAYS. I have tested this on 3 other HD2's and all followed the same pattern. I have only tested them for the last 3 days though. My exact setup as far as OS's is:
Windows Mobile Rom: Omega v14 WWE XT CHT
Radio: 2.14.50.04
Android Rom: mattcevoleo1.0.1
Kernel: [email protected] (r1)
Please post if this works for you if you decide to try it. I am curious. That was probably the only real downside to my daily HD2/Android usage.
Click to expand...
Click to collapse
How long were you running michy's r1 kernal before you installed that app? Reason I asked is because installing michy's r1 kernal and rebooting is what solved my data issue.
*minus the winmo rom i have the same exact set up as you
xuix said:
It not solve my data connexion problem, i have installed the apps, set it to AUTO, reboot, delete the apps, and now everything is same than before i install the apps... nothing better...
using the Mdeejay eVo Sense v. 1.0 Warm|3.29.651.5|[kernel: hastarin R7.1] release with the libhtc_ril_wrapper.zip updated (9/28)
Click to expand...
Click to collapse
will3k14 said:
Ill try this on my 1.8 and my evo 1.0.1, will report back
Click to expand...
Click to collapse
Try this kernel
http://forum.xda-developers.com/showthread.php?t=791584
Solutions?
Any new solutions to this item, I attempted the above fix and didn't quite fix it. I have a good feeling this fix has a lot to do with the rom/radio combination.
malzubai said:
Any new solutions to this item, I attempted the above fix and didn't quite fix it. I have a good feeling this fix has a lot to do with the rom/radio combination.
Click to expand...
Click to collapse
I concur. Thats why I was wondering how long had he used that set up before downloading the app. I have almost the same exact set up and my data connectivity has been excellent (this is without downloading that app)
I can confirm this has worked for me, after updating my kernel to hastarin 7.1
i started having data disconnections, then this came along
thanks for sharing
My attempt ...
Until now, any build that uses PPP would not work without at least one flaw in the data connection every half hour or less... Terrible...
I then decided to try a combination of the tips that I've been reading in the forum.
First, I edited the build.prop in system folder and changed the last two lines in the file, the primary and secondary DSN. I used Namebench, a free program to find the indication of which DNSuse for my region (I live in northern Brazil). I run the Namebench on my laptop and copied the two recommended DNS addresses.
Then followed another tip, and using the *#*#4636#*#*, changed the network configuration for GSM auto.
And finally, in the phone settings, I changed from GSM/WCDMA auto to GSM only...
It's five hours straight without any disconnection !!!!!! It is true that the connection is slower because of GSM, but it is steady and reliable!
My next step will be to change this last parameter for WCDMA Only and just see what happens
Sorry about my English, hope you can understand!
k2trill said:
Try this kernel
http://forum.xda-developers.com/showthread.php?t=791584
Click to expand...
Click to collapse
Thanks for the help I tried this fixit doenst work. I'll do what you suggest K2trill thanks. btw any fix for the voice rail issue on the evo 1.0.1?
lkrfn5283 said:
How long were you running michy's r1 kernal before you installed that app? Reason I asked is because installing michy's r1 kernal and rebooting is what solved my data issue.
*minus the winmo rom i have the same exact set up as you
Click to expand...
Click to collapse
I'd been running it since its release... few days
malzubai said:
Any new solutions to this item, I attempted the above fix and didn't quite fix it. I have a good feeling this fix has a lot to do with the rom/radio combination.
Click to expand...
Click to collapse
+1. Had freq. dropouts when on 2.09 radio, 2.10 caused the entire radio to dropout and 2.11 was fairly stable but still freq. dropout. 2.14 was been the most stable radio for me so far, only 2-3 dropouts max per day.
Of course, the early radio dropouts could've been caused by the older buggy ril wrapper library, so I might revert back just to experiment around a bit more.
Using Mdeejay Evo Sense 2.4.2 I Managed to resolve my data drops... at least in the last 24 hours.
I still haven't gotten one freeze on any of the 3 phones I'm testing since I did this. maybe I'm lucky...
liaquila said:
My attempt ...
Until now, any build that uses PPP would not work without at least one flaw in the data connection every half hour or less... Terrible...
I then decided to try a combination of the tips that I've been reading in the forum.
First, I edited the build.prop in system folder and changed the last two lines in the file, the primary and secondary DSN. I used Namebench, a free program to find the indication of which DNSuse for my region (I live in northern Brazil). I run the Namebench on my laptop and copied the two recommended DNS addresses.
Then followed another tip, and using the *#*#4636#*#*, changed the network configuration for GSM auto.
And finally, in the phone settings, I changed from GSM/WCDMA auto to GSM only...
It's five hours straight without any disconnection !!!!!! It is true that the connection is slower because of GSM, but it is steady and reliable!
My next step will be to change this last parameter for WCDMA Only and just see what happens
Sorry about my English, hope you can understand!
Click to expand...
Click to collapse
Ok. Just to give a feed back...
With GSM only, no drops at all!!!!
When I changed to WCDMA only, overall it's more stable than before, but I had a few drops last night and this mornig...
So, for me, I'm switching back to GSM only. I do prefer a more slower connection but with no drops !!!
I'm using 2.14 radio, with FroyoStoneSense v3.1 (Darkstone) !
Hello, I have been installing android builds on my HD2 for months now, and have to say the recent development has really left me with a great android phone.
One problem I find I have consistently is that I can never get the kind of battery usage others speak of. Mine trends at 350mA right now which seems wrong cause my battery life isnt THAT bad. and I have never had a build thats had better than 10%->hour.
I'm using ShubCRAFT 2.0 with the hastarian r8 kernel, chunkydroid ROM and 02.12 something radio, i also have an australian HD2.
I keep my screen quite dim, wifi and bluetooth off, no over or underclock (since r8 doesnt support it), no auto task killer.
And while I'm at it my wifi tethering should work based on my build and kernel but every time i check it it says "Error" and third party apps are a no go either.
Any insight would be greatly appreciated.
Also to all the devs, I love you, I want to carry your children.
i always make setcpu, max 619mhz min 254, screen off: max & min 254, auto task killer when screen off and i disable all auto sync, like facebook gmail etc.... im getting acceptable result, around 2 days with normal use
See the FAQ link in my signature. I put some tips there that may help.
Sent from my HTC HD2
hastarin said:
See the FAQ link in my signature. I put some tips there that may help.
Sent from my HTC HD2
Click to expand...
Click to collapse
I had just finished reading that list and forgot to try the 3sec. boot which helped. I'm at 10mA now it makes no mention of the wifi tethering problem, any idea on the subject??
EDIT: It flew back up to 200+ after 5 minutes and hasnt gone back down since.
I get 14 Hours standby, but the phone is 4 hours aktivate! I use also chuckydroid. My radio rom is 2.12 and I use Froyostone series !
Sent from my HTC HD2 using XDA App
If you're like me, a subpar or incomplete Android 2.2 on HD2 experience was NOT an option. I've been through pretty much every combination, followed everyone's advice and always ended up unhappy for one of several reasons :
1. The ROM I installed was missing features, like the camera or other features that crashed.
2. The dreaded "Sleep of Death"
Not to say anything against any of the ROM chefs, because these guys are hard-working geniuses and they do this for free... for us...
But having said that, I had to keep trying. I'm obsessive compulsive when it comes to my gadgets and once I had a taste of Android on the HD2, I knew I wouldn't be happy until I found that elusive combination that made it work the way I wanted it to.
If you're having trouble making Android work on your HD2, listen up... Because now mine works like a charm and here's how it happened...
1. You absolutely HAVE to get rid of the stock Windows Mobile 6.5 that comes on your HD2. I never found a way around that. Until I flashed a custom ROM, it never worked 100%. To do this you need to flash HSPL to your HD2. This allows the installation of custom ROMs.
2. You have to strip Windows Mobile down to next to nothing. If you plan on using Android 2.2 as your daily operating system, you don't need it anyway. I tried lots of versions, but face it - you won't need WinMo anymore once you get Android working 100%. For this, use Chuckydroid, hands down. It is stripped down to next to nothing - no Sense 2.5, nothing fancy in Windows Mobile. BARE. BONES. Chuckydroid can also be set up to autoboot into Android!
3. After installing Chuckydroid, I also flashed Radio 2.15 just to have the latest radio. I've heard people talk against it, but again - I'm working 100%, so I'm happy.
4. For my Android ROM, I chose Mdj revolution 1.5, and updated to the S1 Linux kernel. It was one of few builds that had all features working as they should. The S1 kernel patches a lot of issues that might arise with the MDJ build.
5. Lastly, I noticed I didn't have 3G signal after all this and discovered that at some point my APN information (which tells the phone how to connect to data services) had been wiped out. I am a TMoUSA customer, so I found the information for the USA servers and added it manually to the phone. (System/Wireless & Networks/Mobile Networks/Access Point Names)
I know this isn't every piece of information you need, but if you read each point and investigate on your own, you'll find there's a wealth of information out there to guide you through each step, but to clarify :
1. Flash HSPL (I used HSPL 3, but follow the directions when you find it)
2. Install Chuckydroid (No other custom ROM worked and I tried them all)
3. Flash Radio 2.15
4. MDJ Revolution 1.5 w/ S1 kernel (Most stable and complete I could find)
5. Manually configure APN
Again I'll close with the fact that I have a fully-working Android 2.2 HD2 device. All features, all functions, no errors, no robot voice, no SOD, no gremlins... It just works. Good luck! If you have any additions to this plan, let me know! I'd like to know that I was using the newest 100% WORKING(!!!) Android built with all the best features.
I'd also like to add that, given my luck, now that it's taken me over a week to get Android 2.2 working flawlessly on my HD2, in the next day or so we'll see one of four things :
1. A flashable Android 2.2 ROM that completely replaces WinMo as the Operating system
2. A flashable Android 2.3 (3.0) Gingerbread ROM
3. A flashable Windows Phone 7 ROM
4. The return of Christ
Zaron3d said:
4. The return of Christ
Click to expand...
Click to collapse
That's it That's all...
funny
before 1,2,3,4 you can also try:
0. replace kernel with s2 also made by mdeejay. they say it's very good
thinking better i don't belive this thread belong to this section
noris08 said:
funny
before 1,2,3,4 you can also try:
0. replace kernel with s2 also made by mdeejay. they say it's very good
thinking better i don't belive this thread belong to this section
Click to expand...
Click to collapse
Well I tried a lot of these "quick shortcuts" to make things work and nothing did. Believe me, I've been down every road to make this happen...
and yeah I guess I put this in the wrong section now that I look at it. Sorry!
Yep, this thread have to be moved into the Android General Discussions section.
Just let me know if you have a constantly data transfer on on your "working-like-charm" Leo and I'll immediately flash ChuckyROM (which version?), 'cause I've tried EVERYTHING, my battery lasts 3,5/4 hours running Android and I have to recharge it twice everyday...
vysus said:
Yep, this thread have to be moved into the Android General Discussions section.
Just let me know if you have a constantly data transfer on on your "working-like-charm" Leo and I'll immediately flash ChuckyROM (which version?), 'cause I've tried EVERYTHING, my battery lasts 3,5/4 hours running Android and I have to recharge it twice everyday...
Click to expand...
Click to collapse
try this combo:
- wm - energy nov 8 21684 cht 1.8.5
- radio - 2.15
- android - mdeejay revolution 1.5
- kernel - mdeejay s2
i have only 6% battery drop over 9 hours of standby, all data transfers closed and gsm only, not 3g
all things i tested works flawless
i think you missed the most important thing...
--> hard format your SD card before trying
Camillo
Format or not the SD makes non differences, I have huge battery drain in every situation.
I've had several issues running mdeejay builds, so I prefer FroyoStone 3.2 by Darkstone. I've never tried Chucky ROMs before, so I'd like to flash the brand new one
@camillo
no i didn't forget format card. i just don't do that, formatted first time and never again since then
@vysus
do whatever you want. i just suggested a combo that works very well for me
noris08 said:
@vysus
do whatever you want. i just suggested a combo that works very well for me
Click to expand...
Click to collapse
You're welcome
Unfortunately, NRG ROMs and PPP builds are not suitables for italian providers: using the first ones I had battery drain, trying the seconds I have had continuos data drops, missed calls & SMS, HUGE and nearly incredible battery drain.
I still would like to know which version of Chucky fits better with android, it's the last chance, after that I prefer to let go...
i think an correctly configured setcpu is the most important fact for battery life.
my combo:
winmob:http://forum.xda-developers.com/showthread.php?t=793814
radio: 2.12.50
Droid: hyperdroid 1.7 (nexusHD2 since yesterday cuz of new harastin kernel)
sdcard: transcent class6 sdhc
battery drain without setcpu (overnight, 8h): 40%
with : 3%
TBH I have found no difference between a fully featured winmo rom (laurentius V4 or Energy nov 8th) versus Ozdroid which was stripped down.
I have found that of course the kernel makes the most difference - currently on S2 and it seems rather peachy.
As for battery drain I have found that it is fine even without setcpu on this kernel - however - once in a while, especially at the end of the day, the battery drains super fast - I believe there is an errant process or data transfer that messes it up (perhaps whatsapp?).
I stillhowever have PPP disconnects regardless.
I haven't had one since I disabled the stock widget though.
i only have ppp disconnects if i kill all my tasks. if not, it works fine
I start off my android adventure few weeks back and now I found my treasure and have stop searching.
Here is my combination,
WM ROM: vbn clarity
Android rom: mdj froyo revolution 1.5
Kernel: mdj s2
I have tried some other build and the battery life can only last me half a day but with this combination after more than 12 hours of usage, I still have 40%. (Usage: check email every 30 mins, check xda app every 30mins, moderate web surfing, a few calls)
So for those still struggling to find the combination, you might want to try my combination. Enjoy
Sent from my HTC HD2 using XDA App
A different spin on Android Issues
I too was having issues with SOD, random freezing/rebooting, robot voice etc and basically gave up on having a usable version of Android working on my device.
But then I had a slight lapse in judgement and came up with another hair-brained idea... I decided to attempt to get T-Mobile to let me just switch to a different phone like the Galaxy S / G2 / or MyTouch 4G.
So I task 29'ed the phone, flashed back to the OEM rom, then removed HSPL while not at work... Over the next 2 hours I began to notice that I was having issues even on the default OEM rom.
I got curious, removed the SD card, re-installed HSPL, re-downloaded the T-Mobile Official Rom from their website, and task 29'ed the phone again, reinstalled the OEM rom, and removed HSPL again just to make sure that I hadn't just got a corrupt download or something.
Within 20 mins of loading the T-Mobile rom back on the phone, my phone randomly rebooted itself. Later while I was in the middle of a phone call the phone just made a weird buzzing sound and froze. The buzzing sound would not go away until I removed the battery and restarted. I was also having many of the issues I was seeing in all of the Android builds that I had tried like the screen taking forever to come back on after being locked, the screen being non-responsive etc...
I had attributed all of these problems to the Android roms I was using and Android not being 100% and stil too buggy for the HD2 when it actually was a problem with the device itself.
I went to T-Mobile last night and they are sending me a new phone (probably a refurb) by the beginning of next week. I'm hoping that the new device will clear up all of the issues.
Just thought I would share my experiences, maybe some of you that are having issues with the Android builds could actually just have a bad device like I did...
Zaron3d said:
After installing Chuckydroid, I also flashed Radio 2.15 just to have the latest radio. I've heard people talk against it, but again - I'm working 100%, so I'm happy.
Click to expand...
Click to collapse
Followed your suggest, flashed latest Chucky GTX, did anything else, switched to Android, unplugghed my phone at 2.30 PM, some calls and SMS, few calls received, battery is 42%, over 10% per hour that turns to 12 and over using the device, now I'm hopeless
vysus said:
Followed your suggest, flashed latest Chucky GTX, did anything else, switched to Android, unplugghed my phone at 2.30 PM, some calls and SMS, few calls received, battery is 42%, over 10% per hour that turns to 12 and over using the device, now I'm hopeless
Click to expand...
Click to collapse
Uhhh... what? It depends on what you have running I guess. Mine seems to be running fine. Off the charger for about 3 hours and only down to 90%.
Since I've just had my HD2's screen replaced, I'm still on the stock ROM from when I got the phone back from HTC. I just popped my SD card back in and off I went. The stock ROM works perfectly with Android for me. The radio is the one they installed (see sig).
I'm not sure that WM ROM has that much effect tbh. With the ppp wrapper patched and running the S2 kernal from MDJ, I managed a 320 mile trip with Google Navigate running the entire time. I never had a single data drop or problem with the phone. I was connected to my car stereo via bluetooth too.
Hi Guys,
I have been using gingerbread build's for some time. I notice battery drain sometimes battery drain suddenly spikes to 58mAh for sometime (without Wifi or BT)..for around 10-15mins and then comes back to normal after 10-20mins(<10mAh). I experienced this issue first in MDJ Cm7 2.6 build..I thought that time must be build specific..so I switched to Desire HD build which was free of this issue...however I don't like sense anymore, so moved back to typhoon's CM7 build.But again I encountered the same issue. I changed the kernel to gauner's kernel, since the desire HD build I was using was using this kernel and free of the issue, but again it surfaced back.
Now I switched to pongster's hyperdroid build. This build has a very low power drain...most of the time its < 4mah on this build...Also I haven't installed any widgets (except for current widget) and have still the stock ADW launcher (to rule out the possibility of this bug caused by any s/w)...but again the drain jumped to 58mAh .Is it just me or other gingerbread users face this drain also randomly. could it be due to SD card, I am using ext4 data partition.
Mafioso said:
Hi Guys,
I have been using gingerbread build's for some time. I notice battery drain sometimes battery drain suddenly spikes to 58mAh for sometime (without Wifi or BT)..for around 10-15mins and then comes back to normal after 10-20mins(<10mAh). I experienced this issue first in MDJ Cm7 2.6 build..I thought that time must be build specific..so I switched to Desire HD build which was free of this issue...however I don't like sense anymore, so moved back to typhoon's CM7 build.But again I encountered the same issue. I changed the kernel to gauner's kernel, since the desire HD build I was using was using this kernel and free of the issue, but again it surfaced back.
Now I switched to pongster's hyperdroid build. This build has a very low power drain...most of the time its < 4mah on this build...Also I haven't installed any widgets (except for current widget) and have still the stock ADW launcher (to rule out the possibility of this bug caused by any s/w)...but again the drain jumped to 58mAh .Is it just me or other gingerbread users face this drain also randomly. could it be due to SD card, I am using ext4 data partition.
Click to expand...
Click to collapse
Try turning sync off and seeing if that is what causes the spikes
XsceneXhippieX said:
Try turning sync off and seeing if that is what causes the spikes
Click to expand...
Click to collapse
yes, I thought of that...and have removed facebook sync but I do need my gmail sync..I don't have any other sync's enabled except contacts and gmail...lol, is it too much to ask ? and i don't have any issues in sense builds where I have gmail, weather and facebook sync on
Mafioso said:
yes, I thought of that...and have removed facebook sync but I do need my gmail sync..I don't have any other sync's enabled except contacts and gmail...lol, is it too much to ask ? and i don't have any issues in sense builds where I have gmail, weather and facebook sync on
Click to expand...
Click to collapse
hmmm, I don't know, maybe its an install issue, I have everything always syncing, but I also have only 2g connection (at&t's terrible network) and I haven't had this issue using both pongsters and mdj's builds
XsceneXhippieX said:
hmmm, I don't know, maybe its an install issue, I have everything always syncing, but I also have only 2g connection (at&t's terrible network) and I haven't had this issue using both pongsters and mdj's builds
Click to expand...
Click to collapse
Hmmm ok...I don't think its an install issue..i always do a task 29 before switching builds from different devs..and follow the CWM settings as recommended by the dev....rest the builds are running so smoothly especially pongsters without any FC's or such...
BTW why are using AT&T...t-mob is cheaper and faster(3g)
It happens to me too sometimes. What I do is disable wifi and gps wait two minutes and battery drain on standby becames 5mA again. When I enable both again, it stays on 5mA. Don't know what's causing it, but I have it too.
I have this Problem if I use Livewallpapers.
Now i use normal Wallpapers and it is gone.
edit: 5-8 mA with normal Wallpaper
Well for me, it turned out to be the sync indeed as XsceneXhippieX mentioned.
I turned off all sync just for the heck of it and the problem hasn't come back for last 2 days...I enabled Background Sync (not auto sync) and problem resurfaced within few hours...so i'm pretty sure..Its the sync which is causing this Guess I need to go back to Sense ROM now...
And BTW i'm not using live wallpapers..
Also one more interesting fact...phone conusmes more battery on 2G networks than on 3G. I forced to phone to use 2G network and idle power drain was >5mAh all the time...while on 3g its 2-5mAh mostly...
58 mah on Ginger is usually the GPS. Turn it on then off again, somehow if you use it or any app use it, even if the app closes the GPS chip doesnt turn off.
Just turn it off using the widget or in settings.
If that doesnt fix it, make sure Bluetooth is off. it consumes 58-59 mah, even if it is not connected, its a known issue on Ginger. Bluetooth never goes to sleep, gotta turn it off manually.
Hope it helps!.
Zephyrot said:
58 mah on Ginger is usually the GPS. Turn it on then off again, somehow if you use it or any app use it, even if the app closes the GPS chip doesnt turn off.
Just turn it off using the widget or in settings.
If that doesnt fix it, make sure Bluetooth is off. it consumes 58-59 mah, even if it is not connected, its a known issue on Ginger. Bluetooth never goes to sleep, gotta turn it off manually.
Hope it helps!.
Click to expand...
Click to collapse
Thanks for the help, but I'm sure its due to sync...I turned off the sync and for last 3 days there hasn't been a single occurrence of 60mAh drain.
gonna try turning off sync cause ive been having this issue.
just tried second gingerbread rom and it began immediately,
and this is with data, wifi, bt, gps all off.
hopefully sync does it
turning background data off didnt help.. still getting 70 to 80 drain.
and playing music in standby had me up to 110 which is higher than usual too
lbhocky19 said:
turning background data off didnt help.. still getting 70 to 80 drain.
and playing music in standby had me up to 110 which is higher than usual too
Click to expand...
Click to collapse
Is it a spike or continous drain? Also which ROM/kernel are you using?
its a spike, other weird thing is since i got on gingerbread, currentwidget has sucked at getting a continuous read. it has big gaps in the log.
http://forum.xda-developers.com/showthread.php?t=905060
thats the one im on now and i was on clean gingerbread before that
lbhocky19 said:
its a spike, other weird thing is since i got on gingerbread, currentwidget has sucked at getting a continuous read. it has big gaps in the log.
http://forum.xda-developers.com/showthread.php?t=905060
thats the one im on now and i was on clean gingerbread before that
Click to expand...
Click to collapse
Yes currentwidget don't give a continuous read for me too...but its the same behavior in froyo based sense build also...
Anyway, are you using any widgets installed which sync? Disable them and see, though i'll advice to disable all widgets (not only ones which sync) and see
score mobile and stock weather i have. but if i turned off background data and autosync they shouldnt be able to do anything i thought?
il give it a try
and currentwidget always did minute by minute for me in froyo. on sense at least i cant remember the last time i used a stock build
lbhocky19 said:
score mobile and stock weather i have. but if i turned off background data and autosync they shouldnt be able to do anything i thought?
il give it a try
and currentwidget always did minute by minute for me in froyo. on sense at least i cant remember the last time i used a stock build
Click to expand...
Click to collapse
Well I had fancy widget installed in which I had set weather to be updated always (irrespective of background data option) once a day and only on Wi-Fi..yet it still caused 58mAh drain....try disabling them for a while and see...
just deleted score mobile and deactivated weather.
after a few minutes turned it on. 85ma...
You can change the kernel to see if it helps...try Gauner's or RAFPIGNA
or better switch to froyo build...i'm switching myself..there's not much use to smartphone if you turn off syncs anyway
yeah i guess back to froyo. whats the best stock one? def dont want sense anymore.
and has anyone made an app or something to do the awesome shutoff animation from 2.3?
I am using CMYLXGO's NAND stock Desire HD build. Its great. However, I am having so many lag issues. I seem to be one of the few that is experiencing this with the build so i turn to some of you to see if you have had similar issues with your phones.
Problems:
1. when auto populating apps (like using installer, uninstaller, managing applications in the system tab) the phone will take forever to pull up all the apps , the screen will cut off (because the screen times out) and when I hit the home button or any button to cut the phone back on it stays black.
2. every action makes the cpu run high. adding a widget to the home screen (apps populating issue again), changing screens really fast and other assorted minor processed.
I have stopped auto sync
I do not use auto rotate any more
I do not have any rogue processes for the most part
I don't understand why I seem to have these lag issues. Everyone else talks about how fast and fluid the build is. I am under the impression that with the build NOT being run from the memory card NAND would add to speed. This is not happening for me. If anyone has any idea why this is happening. I am convinced it is something on my end but I don't know where to start. I am open to suggestions.
I have 2.15 radio, 16 gig class 2 memory card.
Hmmm, not sure but have you tried another ROM similar to see if it does the same? You can also go into MAGLDR and wipe dalvik cache. I used this ROM and all was good for me. I have sense been using this one which is also working very well.
http://forum.xda-developers.com/showthread.php?t=976384&page=1
every version of this build has been tried. That is the part that gets me. differnt kernels don't help either. i have even used SetCPU and overcloced to try and get through some of the lag. it works, but it is only when I play games not when I need to perform uninstall or widget selection for the home pages. I use SeePU which is ususally shows my cpu strain in the bright orange (for high use). most of my processes/actions raise the cpu use to high levels. I never really operate in a green (or low) usage level no matter what the action is. I would really like to capitalize on the speed NAND is supposed to offer.
Personally I would try something else (a totally different ROM) and see if you are still getting the same results, maybe even revert back to a windows mobile rom just to see if you are still getting the hang up. Last option would be to restore your phone to stock and start over, reinstall HSPL 2.08 new radio, etc...etc...
do you use an app killer?
XthelordinatorX said:
do you use an app killer?
Click to expand...
Click to collapse
yeah. but i did not at first. however, it is needed to stop some of the rogue processes. android.process.acore comes to mind.
I personally think this is one of the most stable builds around. I would rarely experience any lag, and if I did it would only last for seconds.
WorldWide60 said:
I personally think this is one of the most stable builds around. I would rarely experience any lag, and if I did it would only last for seconds.
Click to expand...
Click to collapse
Believe me, I know. Everything is working in his build. GPS, MMS, easy to install - the works. This is why i really want this to work properly so I can use it, without the hiccups, as my daily build. It has to be something with my phone but I can't figure out what it is yet....
On Cmylxgo's build, the first time I loaded it, I had the laggy and unresponsiveness you described for the same reasons. What I found is that rebooting the system to off/on a couple of times when I first loaded the build, addressed the first initial lag and unresponsiveness. After doing a couple of reboots, I found the build as smooth as everyone says it is. I am now trying the GL Core v11 kernel and it gives an extra 300 pts to the Quadrant Score and seems to be a bit quicker than the Rafpigna 1.8 kernel that comes with the build. Also, standby battery drain seems to be a bit better with the hourly peaks at half what I see with Rafpigna. If rebooting a couple of times doesn't do it for you, I know trying another build which may not have all the bells and whistles as Cmylxgo, but it is worth a try to see if it makes a difference. For me at least Cmylxgo's stock Desire (HD)2 build is much faster and smoother than any of the MDJ SD builds I was using.