NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

**[ACL]** · #1 (**permalink**) 12-30-2010, 12:41 PM

Nate: i commited some changes last night. Unfortunately i passed out while writing the sharp panel portion for the 0x13 id. But should be done tonight so those poor rhod100 folk can help test.

Since camera is around the corner i guess i will begin concentrating on true nand next. I wish we had a winmo chef since they would know how wince handles all that stuff. Once we have that figured out its just a matter of filling in tinboot with the necessary info.

MassStash · #2 (**permalink**) 12-30-2010, 01:59 PM

Quote:

Originally Posted by [ACL]

Nate: i commited some changes last night. Unfortunately i passed out while writing the sharp panel portion for the 0x13 id. But should be done tonight so those poor rhod100 folk can help test.

Since camera is around the corner i guess i will begin concentrating on true nand next. I wish we had a winmo chef since they would know how wince handles all that stuff. Once we have that figured out its just a matter of filling in tinboot with the necessary info.

i tweeted this post to NRGZ energyrom dude.... idk? haha

btw, Nates files from 29th are working amazing with panel, sometimes. And speed is the lotto again

lemeiux, just soft reset 3 more times

Booting mods n kernel 01224 right now....

lemeiux1 · #3 (**permalink**) 12-30-2010, 02:28 PM

Quote:

Originally Posted by MassStash

i tweeted this post to NRGZ energyrom dude.... idk? haha

btw, Nates files from 29th are working amazing with panel, sometimes. And speed is the lotto again

lemeiux, just soft reset 3 more times

ok did you just switch out the modules and flash the NBH? for some reason its like always unusably slow for me. I might try and just reformat and start fresh with that package, it may be something in my data.img or something

EDIT: Nevermind it was Swype haha, I killed it and boom! everything is super snappy now thanks guys

MassStash · #4 (**permalink**) 12-30-2010, 03:15 PM

Quote:

Originally Posted by lemeiux1

ok did you just switch out the modules and flash the NBH? for some reason its like always unusably slow for me. I might try and just reformat and start fresh with that package, it may be something in my data.img or something

EDIT: Nevermind it was Swype haha, I killed it and boom! everything is super snappy now thanks guys

lol niiiice, i haaaate when that happens

Kernel and modules 2.6.27.46-01224-gdcb0700
http://www.lantowcorporations.com/an...nd12302010.zip

**natemcnutty** · #5 (**permalink**) 12-30-2010, 08:14 PM

Quote:

Originally Posted by [ACL]

Nate: i commited some changes last night. Unfortunately i passed out while writing the sharp panel portion for the 0x13 id. But should be done tonight so those poor rhod100 folk can help test.

Since camera is around the corner i guess i will begin concentrating on true nand next. I wish we had a winmo chef since they would know how wince handles all that stuff. Once we have that figured out its just a matter of filling in tinboot with the necessary info.

I saw the commits. You had a busy night! F22 reminded me to think Hex cause I gave you the wrong vendor for 0x13. It should have been AUO since 0x13 is 19.

I'm compiling two versions right now. One will be the reference where I leave force_cdma=1, no overclock, and have pm.sleep_mode=1. I'm also going to do an experimental version where I removed force_cdma=1, set an overclock to 710 MHz, set pm.sleep_mode=1, and moved the relative path to the root of the SD card. This will be a good test to see if my auto-detect CDMA/GSM works and see if removing the parsing of the andboot folder actually does help performance as we've seen in some of the HW3D threads.

tpdjr · #6 (**permalink**) 12-30-2010, 08:28 PM

Quote:

Originally Posted by natemcnutty

I saw the commits. You had a busy night! F22 reminded me to think Hex cause I gave you the wrong vendor for 0x13. It should have been AUO since 0x13 is 19.

I'm compiling two versions right now. One will be the reference where I leave force_cdma=1, no overclock, and have pm.sleep_mode=1. I'm also going to do an experimental version where I removed force_cdma=1, set an overclock to 710 MHz, set pm.sleep_mode=1, and moved the relative path to the root of the SD card. This will be a good test to see if my auto-detect CDMA/GSM works and see if removing the parsing of the andboot folder actually does help performance as we've seen in some of the HW3D threads.

Hey nate are you going to post that kernel tonight?

**natemcnutty** · #7 (**permalink**) 12-30-2010, 08:29 PM

Quote:

Originally Posted by tpdjr

Hey nate are you going to post that kernel tonight?

Already updated the first post with the reference build. The experimental build is compiling right now and will be uploading shortly.

Edit: Experimental build is up now.

tpdjr · #8 (**permalink**) 12-30-2010, 09:03 PM

Quote:

Originally Posted by natemcnutty

Already updated the first post with the reference build. The experimental build is compiling right now and will be uploading shortly.

Edit: Experimental build is up now.

Thx nate u rock going to test now.

**[ACL]** · #9 (**permalink**) 12-30-2010, 09:47 PM

Quote:

Originally Posted by natemcnutty

I saw the commits. You had a busy night! F22 reminded me to think Hex cause I gave you the wrong vendor for 0x13. It should have been AUO since 0x13 is 19.

I'm compiling two versions right now. One will be the reference where I leave force_cdma=1, no overclock, and have pm.sleep_mode=1. I'm also going to do an experimental version where I removed force_cdma=1, set an overclock to 710 MHz, set pm.sleep_mode=1, and moved the relative path to the root of the SD card. This will be a good test to see if my auto-detect CDMA/GSM works and see if removing the parsing of the andboot folder actually does help performance as we've seen in some of the HW3D threads.

oo you are right. But i have another issue that 0x13 doesnt have an init in my dll. So the init that was dumped on haret doesnt match anything. So i need to get my hands on the disptools.dll from the rhod100. I need that to get the correct timing for the delays. Right off the batt it looks really similar to topaz init but i cant say yet since i dont have the dll. Any ideas where i can get it ?

**natemcnutty** · #10 (**permalink**) 12-30-2010, 10:33 PM

Quote:

Originally Posted by [ACL]

oo you are right. But i have another issue that 0x13 doesnt have an init in my dll. So the init that was dumped on haret doesnt match anything. So i need to get my hands on the disptools.dll from the rhod100. I need that to get the correct timing for the delays. Right off the batt it looks really similar to topaz init but i cant say yet since i dont have the dll. Any ideas where i can get it ?

Honestly, I wouldn't spend a lot of time on it. One of the two that have the rhod100 over there sold his already. I will try extracting that file for you from one of the ROM's here: HTC Rhodium/Shipped Roms - XDA-Developers

I'm heading out to dinner with my wife as soon as she finishes doing her hair. I'll be back in a few hours, and I'll take a look at it then