yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] AngelDeath:
Glad to be of service, and glad the variation between me and Warlock (He's such a putz lol!) worked out for you. Thats what I like to hear :)

I will double check after my testing of this kernel, and post back the results.

Thanks for hitting the thanks button, and my pleasure, thats what a community is for, to help each other out before we throw our phones to the wall. Always here to help when I can, knew much more about SlowMo, but learning little by little with trial and error with android.

Actually believe it or not, Both Warlock and Mine work, but obviously the variation he came up with could be the sweet spot so to speak, I'll test it out soon as well and see what I get, the only thing that I have to look at is the "Supl_Port" is that makes a difference and if its based on different regions of the US.

And so far my results of the "Unknown Kernel" battery performance ONLY is being tested, and let me explain how: This phone is on my test phone, it was fully charged and disconnected at 5am and been sitting on my desk since. The only thing that has been running and connected is the wifi to my router, no other apps are running except the default desire HD live wallpaper. All other kernels I have tried doing this test in less then 12 hours have burned 3-4 bars off the battery in this same state. As of right now, this kernel has burned in 20 1/2 hours in standby 1 bar. I honestly did not expect this from this test I expected that it would have burned through just about as many bars as the others but hasnt. I did do one test, and that was sending MMS which it did just to make sure it would send.

I am still testing this till the morning sitting on my desk, I just want to see how much more it will burn thru for the next 8 hours. I know this isnt a real functioning test, but the key here is in the middle of the night when the phone isnt being used when we are a sleep, it should not burn through that many bars by morning. I will reveal the kernel tomorrow after I am satisfied with my testing. And No credit is to me, The credit goes to the original kernel creator. I'm just here to add his name if all goes well to the list of kernels to try, all credit is his, i'm just his voice.
[HD2 Android NAND Development] A11-STAR:
Oh... Ah well. Let me know if I can be of any use. :D
[HD2 Android NAND Development] secano:
WOW! First time opening Google Navigation and got a lock in 25 seconds. Closed Navigation, reopened and locked in 5 seconds. Thank you very much!! I'm in NYC btw.
[HD2 Android NAND Development] steve austin:
YAHOO e-mail settings anyone?

my yahoo e-mail was working fine until the last 2 days. First, the number of emails- indicator that bubbles on top the widget would never change after I opened the e-mail. Second, I would try to send e-mails and it would tell me the message was unable to be sent and the I had to reconfigure it again. this happened 9 times in a two day period.

I typically used this video to help me get my mail account set up on other ROM's. I filled in all the fields and now I can't establish any account. the file server is unable to connect. I did not write down the old settings cuz i thought my old standby remedy would work...not so much.

Would anyone mind filling in the empty fields below so I can get back to the default settings? I would be greatly appreciative. And if anyone knows why the e-mail notification is not working or has experienced it that would help as well. Thanks in advance!

Incoming Settings

* username= xxxxxxxxxxxxx

* password = xxxxxxxxxxxxx

* protocol =

* IMAP server=

* security type =

* server port =

Outgoing Settings

*log in required = (is it checked or unchecked please)

* username= xxxxxxxxxxxxx

* password = xxxxxxxxxxxxx

* stmp server =

* security type =

* server port =

* optional = blank
[HD2 Android NAND Development] Nemesis1278:
Excellent let me know. I even reloaded all of the modules to see if maybe some were corrupt some how when the kernel installed. Oh and I am updating kernels via clockwork.

I am noticing a little bit of a higher battery drain myself so far but it is still a bit early for me to tell if I just need to reset the phone a few times or if it is the kernel itself. I will try to update if I remember.
[HD2 Android NAND Development] WarlockW:
Delete Everything .. and try ..

Incoming Setting

User Name:User@yahoo.com

Password: Password of your yahoo mail

Incoming mail server: imap.n.mail.yahoo.com

Mailbox Name: Yahoo

Mailbox type: IMAP4

Security(Ports): Off

Port: 143

Outgoing Setting

Email Address:User@yahoo.com

User Name:User@yahoo.com

Password: Password of your yahoo mail

Outgoing mail server:smtp.mobile.mail.yahoo.com

Security(Ports): Off

Port:587

Thats what I use works fine ..
[HD2 Android NAND Development] Nemesis1278:
Incoming Settings

* username= xxxxxxxxxxxxx

* password = xxxxxxxxxxxxx

* protocol =IMAP

* IMAP server= imap.mail.yahoo.com

* security type =ssl (should set port automatically when ssl is selected.)

* server port = 995

Outgoing Settings

*log in required = Checked

* username= xxxxxxxxxxxxx

* password = xxxxxxxxxxxxx

* stmp server =smtp.mail.yahoo.com

* security type = ssl(should set port automatically when ssl is selected.)

* server port = 465

* optional = blank

These are the settings that should work enter username and password as you would normally and email is obviously youremail@yahoo.com
[HD2 Android NAND Development] geek_seeds:
i like the bootsplash :D

very original & stock :p

that can proof it is HTC phone LOL

next build keep this bootsplash please :)

i have some trouble..

HTC sense always FC:confused: :confused:

i use tmous & latest partition setup on first page
[HD2 Android NAND Development] steve austin:
thank you for your suggestion. unfortunately it did not work. Before I gummed up the works I believe that in the server field CMY had the word "android" somewhere in it. I also don't have an "imap4" option. my account info is still not being recognized.
[HD2 Android NAND Development] Nemesis1278:
In the username field try it without the @yahoo.com, just the username itself. If it still doesn't work try my settings. If that still does not work check your internet to make sure that you are connected and transmitting/receiving.
[HD2 Android NAND Development] dipaolnv:
Steve, are you using the yahoo app, or trying to set up the android mail client to connect to your yahoo account?

Here are the settings from yahoo's site:

Incoming Server - imap.mail.yahoo.com

Outgoing Server - smtp.mail.yahoo.com

Incoming Port - 993 (requires SSL)

Outgoing Port - 465 (requires SSL)

Username: full email address (bill@yahoo.com)

Password: is the password you login to Yahoo! with

I saw that one of the previous posts had 995 as the incoming port.
[HD2 Android NAND Development] MartyLK:
If you are using the Android email app, use these settings, which come from WP7. If you are using the "ymail.com" version, input that in the user ID area but leave the other fields as shown. Make note of the ports as well.
[HD2 Android NAND Development] cherni:
CMYLXGO,

With the original settings, it took between 3-5 mins to get a GPS lock. I used this configuration and now it came down to 1m or less.

NTP_SERVER=south-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
CURRENT_CARRIER=common
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_SSL_ENABLE=FALSE
ENABLE_WIPER=0

note that south-america.pool.ntp.org should be changed for north-america.pool.ntp.org or whatever.

Hope it helps!
[HD2 Android NAND Development] kev0153:
Is there a link to a tutorial on how to tweak Supl_Port for tuning into your region? Can't see to find the right search terms in google to turn up anything.

Thanks
[HD2 Android NAND Development] urfavoritemazn:
I'm getting really high battery drain while using apps. But my standby is great but my drain while using apps is ~1% a minute.
[HD2 Android NAND Development] steve austin:
thank you both. much appreciated. I got the connection to come back. i deleted both accounts and i pressed "manual install". All the settings came back and auto populated the fields. (Tried that earlier and it didn't work). The connection is back and I am receiving e-mails again and can review the account. yes! The only problem now is that the notification indicator is not working at all instead of reading it wrong. Oh well. You can't have it all I guess...thanks again.
[HD2 Android NAND Development] steve austin:
I am drawing in between 5-7 with bluetooth on. I have never got a 2 even with background data off and no bluetooth or wifi. I actually, for the first time ever got 10 hours out of the battery. However, It was in use for one hour (texts, 3 phone calls and Tower raiders Gold [man that thing is addictive]) and 9 hours in sleep mode.

Its when using the phone that the thing starts to burn. 230-450 over the past 3 days. I am also noticing that at random points, during sleep, the usage goes up to 60-70 for extended periods and there are no apps running. I am using the 10.40 kernel that came with it. I am waiting to see what is yielded from the others who are testing other kernels now
[HD2 Android NAND Development] urfavoritemazn:
same exact thing with me. while using it it goes to 250-430ma which is crazy.

i am also using the default kernel
[HD2 Android NAND Development] cmylxgo:
Added 3 more kernels to the first post. I would love if someone could do a write up and comparison of the kernels on my ROM. This way I can make a better determination what kernel to use as a base.

Thanks.

-CMYLXGO
[HD2 Android NAND Development] AngelDeath:
Thats a question to ask slbenz apparently he found it.But I'd also be interested in hearing the answer.

Update The kernel is still running, I am going to let it run till 5pm which would make 36 hours, as of right now only 2 bars, Either its a fluke or this is going to be the kernel I use. I will test this kernel on my test phone under useage for the next two days and see if the results are similar under useage, but I'll post the kernel after 5pm. Just want to see where it will end up at 36hours.
[HD2 Android NAND Development] tigerz0202:
I'm getting pretty good life out of the gpc 215 kernel , quadrant scores are about the same with highest being in the 1350 range , stable , I think this is the first one I've actually got the 1-2 mah an hour ,loving it so far , tytung made my phone freak out with this build with random reboots
[HD2 Android NAND Development] slbenz:
AngelDeath,

Here is what I found related to the use of SUPL_PORT using either 7275 or 7276. According to Google Support, if you are using SUPL_HOST=supl.google.com then you should use 7276. It supposed to give you the most accuracy. I tested both and yes, 7276 gives the most accuracy, especially with the compass direction on the GPS Status app. Actually, it is spot on comparing it to my high-end hiking compass I have. I did find out that you can use 7275 using the t-mobile script but I found an even better script that adds to the supl.google.com script. Adding SUPL_SECURE_PORT=7275 seems to speed up the process more. I also did changes to the NTP_SERVER and XTRA_SERVER command lines to see changes those made a difference. It didn't seem to as long as you were consistent and added all the additional server pools.

But adding the enablers made the most difference and this time I changed ENABLE_WIPER=1 to enable WiFi for location. Zero deactivates WiFi to help with location. Seems activating it slowed it down to lock and made it less accurate when I used Car Home. So this is what I am using right now and it seems to work really fast and accurately, especially for the compass. GPS in general never was really that accurate with altitude to begin with.

NTP_SERVER=us.pool.ntp.org

XTRA_SERVER_1=http://1.us.pool.ntp.org

XTRA_SERVER_2=http://2.us.pool.ntp.org

XTRA_SERVER_3=http://3.us.pool.ntp.org

SUPL_HOST=supl.google.com

SUPL_PORT=7276

SUPL_SECURE_PORT=7275

DEFAULT_AGPS_ENABLE=TRUE

DEFAULT_SSL_ENABLE=FALSE

ENABLE_WIPER=0

Again, these are setting I am using for my location in the Silicon Valley area of San Francisco Bay Area. I assume it would be just as fast if I replace the (us.) with a (North-America) or any other country code for that matter. The additional command lines after the XTRA_SERVER command line I suspect are general enough for everyone to use but adds enough additional support to the SUPL_HOST line for google. Using Car Home or GPS Status, I am now getting a lock within 3-8 pulses of the GPS symbol after first lock with an accurate compass. Let me know if you find another combination that works even better.
[HD2 Android NAND Development] WarlockW:
Well I gave yours a try .. Idk .. but seems to make it worse :(

NTP_SERVER=north-america.pool.ntp.org

XTRA_SERVER_1=0.north-america.pool.ntp.org

XTRA_SERVER_2=1.north-america.pool.ntp.org

XTRA_SERVER_3=2.north-america.pool.ntp.org

XTRA_SERVER_4=3.north-america.pool.ntp.org

SUPL_HOST=lbs.geo.t-mobile.com

SUPL_PORT=7275

DEFAULT_AGPS_ENABLE=TRUE

DEFAULT_SSL_ENABLE=FALSE

ENABLE_WIPER=0

Still Seems to be the best for me anyway ..

Have you tried with out the http:// ???

NTP_SERVER=us.pool.ntp.org

XTRA_SERVER_1=1.us.pool.ntp.org

XTRA_SERVER_2=2.us.pool.ntp.org

XTRA_SERVER_3=3.us.pool.ntp.org
[HD2 Android NAND Development] slbenz:
I took the http:// off and it made it worse for me. Will try some other combinations to see if things stay the same or get better.
[HD2 Android NAND Development] AngelDeath:
Thanks forthe info, now that I look at this, I also noticed something after reading Warlocks post which I also added here, since he was complaining about a slower lock and asking about the http:// Now if my understanding on how the GPS works, the HTTP:// is used by the wifi NOT the GPS, if im wrong someone please correct my way of thinking, cause in the outside with no wifi, or the use of agps the web servers would be irrelevant in locking to a satelite.

Also if you happen to notice that in my original gps.conf there was no mention of google.com for the supl_host. The reason for this is cause mine was setup for ATT since I am not on t-mobile. I believe thatthe supl_host=supl_google.com is generic to use googles location service, I dont know exactly what the fqdn that att uses is pointed to.

But I believe that the ntp servers are used when outside but the http:// is used for agps and also for when near a wifi network for a quicker pickup, that would explain why the setting doesnt work for warlock but could for others in a hotspot area. Warlock lives in the boondocks at -40F so nothing functions right there :p

Okay and I know that everyone is probably fed up of hearing me about this kernel but 36 hours later total loss of battery drain, 3 bars. The kernel is from RaiderX303's Radroid 1.2 rom. After I got kernels to load I believe thanks to carl's post about larger partitions, I started ripping kernels, and this was one that I thought why not try, it was good for me with his rom, so I thought it wouldnt hurt to try with this rom. And the result is at least in standby outstanding. So I have attached to this post his kernel for anyone to try, its in zip format, so you dont unzip it, just put it on your sdcard and choose install zip from sdcard and update it.

I hope this gives good results for anyone wanting to try, I am going to try my test phone under normal use and see what type of battery performance I get under daily use, after the standby test my expectations are obviously high.

Post results if you use this. All credit and work is RaiderX's.

Just as an FYI, I also found the Bluetooth Mac Address fix, but no one is willing to help figure out how to get it to work in nand/zip kernels, its the only kernel made for sdcards that actually either pulls the correct mac address or a unique one, something no kernel is doing currently, and I would think that someone could port the infor from the zimage. If anyone is willing to take a stab let me know, again the kernel isnt mine, but I found the fix over a month ago!
[HD2 Android NAND Development] cmylxgo:
Shoot me a pm with the info...I'll take a look at it.

-CMY
[HD2 Android NAND Development] AngelDeath:
CG try the one one page back last post I just posted, curious to see your result.

Warlock and slbenz try adding this to your gps.conf file:

ACCURACY_THRES=5000

Add it after the supl_port=7275

See if it shortens your lock, I found a ton of new commands regarding gps.
[HD2 Android NAND Development] slbenz:
AngelDeath,

So I experimented some more. Tried different ways to change the command lines for the NTP and XTRA SERVER. Seems the most consistent for me in compass direction and lock time was to add the various NTP SERVERS and go back to the XTRA_SERVER with the http:// command lines. It seemed to more consistently obtain my correct address using Car Home and not my neighbor's address. I also tried using WarlockW's SUPL_HOST using the lbs.geo.t-mobile.com command line he uses. Comparing it to the google.com and me adding the SUPL_SECURE_PORT=7275, WarlockW's command line was a bit slower, 5 pulses vs. 3 pulses of the GPS symbol and had one less satellite with slightly weaker signals for the rest. I think it makes sense since I am asking both 7275 and 7276 ports to assist in GPS lock.

Unlike WarlockW as you imply, I have a clear view of the satellites with my WiFi in the background with the assist and it is about 70 degrees ABOVE zero in Silicon Valley. I do want to comment on the use of PORT=7275. Upon further investigation, I find this is the correct code needed if you use anything other than SUPL_HOST=supl.google.com. So for both you and WarlockW, whether he on T-Mobile or you on ATT, 7275 is the correct code to use.

I still think that adding the DEFAULT_AGPS.... command lines is what is causing much of the speed to get a lock. So now, this is the revised command lines I am using and probably will stay with for a while.

NTP_SERVER=us.pool.ntp.org

NTP_SERVER=0.us.pool.ntp.org

NTP_SERVER=1.us.pool.ntp.org

NTP_SERVER=2.us.pool.ntp.org

NTP_SERVER=3.us.pool.ntp.org

XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin

XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin

XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin

SUPL_HOST=supl.google.com

SUPL_PORT=7276

SUPL_SECURE_PORT=7275

DEFAULT_AGPS_ENABLE=TRUE

DEFAULT_SSL_ENABLE=FALSE

ENABLE_WIPER=0
[HD2 Android NAND Development] h3llfire741:
can someone pm me instructions and dl link on switching kernels to Rafpigna v1.7?
[HD2 Android NAND Development] Nemesis1278:
I think I will try Rapfinga kernel tomorrow to see if it works well for me.....so far gpc 215 kernel is working great for me. My phone has been unplugged for about 12 hours and down to about 40%. With few calls and text messages.
[HD2 Android NAND Development] curiousGeorge:
An accurate compass is what I would REALLY appreciate. If this works for everyone, a kick-ass GPS with an accurate compass (previously, Locations was unusable with the atrocious compass), this is more than reason enough for an update. That and a new kernel.

I'll give the kernel linked to a few messages back a try, but it looks almost identical to the huanyu branch, so I really don't expect any differences between it and gpc#215...
[HD2 Android NAND Development] curiousGeorge:
Push to appropriate location (zimage-style, include modules) via adb or scriptable root browser... OR put the zip on your sd card, reboot holding power, choose AD recovery, choose zip from sdcard, select the zip you put on, click "yes -- install", press back, press "reboot device."
[HD2 Android NAND Development] slbenz:
AngelDeath,

Just tried your ACCURACY_THRES=5000 suggestion but after my SUPL_SECURE_PORT=7275 command line. It does make my lock faster. Went from 3-8 pulses to lock now down to 3-6 pulses. Relock was 3 pulses now it is 2 pulses. I just shut off my phone just now and turned it back on. Relock from that state was a quick 5 pulses using GPS Status. I hope WarlockW can concur. You may have a winner here.
[HD2 Android NAND Development] gilbert11231123:
i used this kernel for my battery and my hd2 got stock on go go go! all the time had to hard reset .........
[HD2 Android NAND Development] WarlockW:
Hmmm .. Idk Guys .. I tried this config .. and could not get a lock LOL

This however..

NTP_SERVER=north-america.pool.ntp.org

XTRA_SERVER_1=0.north-america.pool.ntp.org

XTRA_SERVER_2=1.north-america.pool.ntp.org

XTRA_SERVER_3=2.north-america.pool.ntp.org

XTRA_SERVER_4=3.north-america.pool.ntp.org

SUPL_HOST=lbs.geo.t-mobile.com

SUPL_PORT=7275

ACCURACY_THRES=5000

DEFAULT_AGPS_ENABLE=TRUE

DEFAULT_SSL_ENABLE=FALSE

ENABLE_WIPER=0

Got a lock in about 30-45 secs LOL

So I have no Idea ..
[HD2 Android NAND Development] curiousGeorge:
Added to the kernel review.

Also, would like to try GL's kernel. If it is added to the first post, it can easily replace tytung, because it is an updated version of the same repo built with specialized config, OC, and the latest patches/GIT updates.
[HD2 Android NAND Development] cmylxgo:
Thanks...this is the data I've been looking for...I just don't have the time to do this with all the other crap I have going on. I will add this to one of my first 3 posts.

Now...if we can get some data speed tests and overall battery tests besides current draw.

-CMY
[HD2 Android NAND Development] cmylxgo:
First post updated with kernel review :)
[HD2 Android NAND Development] curiousGeorge:
Great! Hopefully I can get my hands on GLv5, too. Then it would be complete (and the "long-phase" testing can begin). Ah, and some data figures would be good...
[HD2 Android NAND Development] AngelDeath:
Try adding that ACCURACY_THRES=5000 to your current setup and see if it makes any difference, my suspicision is it will.

Curious (no pun intended) based on the draw of the battery your showing, I would think a 3mA draw at standby would that go along the fact that the Raidroid kernel is in my test phone and has been in standby for 40 hours with only wifi on and connected and only has lost 4 out of 10 bars? Checking this from settings about phone battery? Because as i said I am just right now testing this for battery performance, and I really havent seen this little draw in a standby state from alot of the kernels.

Also I am working on a new gps.conf for the gps with the new command codes I just found, I would post them here, but I dont want to confuse or screw up anyones mind up with all the new codes and have someone mess up, But Warlock and slbenz I'll pm them to you and if you want to fiddle with them.
[HD2 Android NAND Development] cmylxgo:
I tried GL v5...wont boot on my build...gets stuck right before boot animiation. I'll try again tomorrow if I have time.

-CMY
[HD2 Android NAND Development] curiousGeorge:
Long-term figures are simply temporal projections of localized current draw. It is a function that represents the integral of controlled instantaneous draw over time. That said, a 40% drain over 40hrs on standby (essentially 1%/hour) isn't too surprising. The problem with long-scale draw tests is battery calibration. What seems like a power-sipping kernel may actually be drawing very little current from the battery, and vice versa. Also, beware of buggy battery drivers. RaiderX303 uses a tree I cannot find (GPL violation?), so there's the possibility he's using the old battery driver, which was notoriously inaccurate and suffered from rather extreme calibration issues. Remember the notorious "auto-shutoff at 9%" issues, random jumps in discharge, etc? Besides, that particular kernel is very feature-stripped, has G-sensor calibration issues, and does not incorporate OC or the latest patches/fixes.
[HD2 Android NAND Development] civicsi89:
These solved my slow gps lock. Best results I've had.
[HD2 Android NAND Development] kev0153:
yep this one is the best one for me so far. I got a lock inside my house in about 10 - 15 seconds.