Re: NAND Boot File Repository - Keyboard Mapping Fixed
 

Haven't had a chance to download the modules, but I just flashed it anyways. It took a little while to boot the first time, but yeah, I'm in and everything looks great so far.

I'll get the first post updated tomorrow. Gonna head to bed and just download the modules later. I'll get it all tossed up on Dropbox so we don't have a timer :)

Also, the rootfs.img that I generated totally takes care of the keyboard mapping :)

Re: NAND Boot File Repository - Keyboard Mapping Fixed
 

good work on the rootfs. Now we need to find out why your build is failing. I'm uploading more stuff soon so we can try tomorrow again. :-)

Re: NAND Boot File Repository - Keyboard Mapping Fixed
 

i just downloaded the stuff from [ACL]..dloaded the nbh from pc and modules from my phone..i couldn't wait 30 mins :D..this is really awesum!!! finally 3D!! ive tested it to confirm 3d works..great work!!

Re: NAND Boot File Repository - Keyboard Mapping Fixed
 

Installed the new 10/3.

I removed the zImage as you mentioned it uses whatever is in the nbh file.

I did NOT use the rootfs file as I have a RHOD500.

Booted and froze on animation. Double checked I deleted the old modules. Verified were new ones. Still freezes.

I dunno. I'll try with the rootfs.img.

Update:
I must been confused on the .kb file.
Tried with new rootfs.
Still froze. I'll leave it set for a while see if it recovers. If not I might wipe my data.img and try again

Video corruption on bootup animation, goes to blank screen. No response.

Re: NAND Boot File Repository - Keyboard Mapping Fixed
 

So, the builds ever since hw3d has been enabled haven't been working when I compile them. the rootfs and data files have nothing to do with that.

The NBH and modules that ACL uploaded work perfect, but since he is on rhod400, your keyboard will map to that unless you use the modified rootfs.img and put a file named rhod500.kb in your andboot folder. Realistically, I can change where and what it looks for to determine what keyboard you want, but I wanted an easy way to test keyboards by just adding the .kb to the end of the files.

I am still doing a little research to see if there is something that I can use to differentiate between models so it can be automated, but that will be a project as I have time.

Re: NAND Boot File Repository - Keyboard Mapping Fixed
 

I have no problem doing that for kb if needed.

I switched back to 9/25 build so I can have a functional phone.

I'm sure you'll get it. No pressure. Biggest complaint for me is sleep mode isn't turning off screen. But I've been able to keep a full day with my extended battery.

Re: NAND Boot File Repository - Keyboard Mapping Fixed
 

I have updated the first post with ACL's files. This enables 3D and has the improved battery readings. I know the devs were interested to hear how the new battery algorithm does on extended batteries too, so maybe you can test that out and let them know on IRC ;)

Re: NAND Boot File Repository - Keyboard Mapping Fixed
 

Booted just fine. Thanks to both of you!

3d had always worked but glad it is working for everyone and even new code for battery!

Update:
USB drivers attempting to load
USB charging status works - actual charging I dunno yet I would figure as it worked before with ACL/Camro Kernel


Looking good.

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

Thanks for the hard work on this guys!

Is lcd.density still set to 210 or can it be changed?

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

It appears to be at 210. Probably needs to be rebuilt in nbh file.

Might be able to set it via your Froyo.conf file but I'd go with what Nate or ACL has to say.

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

ok heres my initial findings:

1. Battery charges on usb, but the indicator actually shows the battery going down?
2. Battery status indicator is leaps and bounds better! It actually shows a pretty accurate reading!
3. On standby my LED indicator flickers A LOT, but im sure thats not too big of a deal

as soon as the screen backlight can be turned off completely on standby I am jumping ship to this full time, amazing work everyone, thank you!

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

Im still crafting a clever way to change this without making an nbh each time. Right now we are running our own rootfs so we can probably modify it the same way. I promise the next kernel we put out will have the option..

:-)

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

There are some final changes to the batt code so hopefully they fix the issue you reported.

LED indicator may need to be revisitied. Put some code in there to control LEDs but now we have the christmas light effect where all the colors show up.

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

Final batt code was uploaded for both nand/haret. fyi.

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

acl where is the final batt code located and thx for the info making sure i hit the thx button

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

Thx for pushing the update ACL.

Nate, I have some info for you from jonpry:

I hope that helps!

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

Is there any workaround in getting the headphone jack to work running NAND like in the storage card?

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

Wozzer has the code and it was never committed. Still trying to get that pushed.

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

I was digging around in wifi-nvram.txt last night and was trying to see if anything in there was different. I would love to get that automated for keyboard control but still allow an override by using the .kb file (for testing purposes).

Unfortunately, my wife is sick right now, so I've been taking care of a lot of extra work around the house. I'll get a compile going on the updated battery code ACL pushed to the nand, but I have a feeling I'm still going to have issues with the 3d patch since nothing has changed in there.

Also, ACL, if I wanted to start researching turning off the backlight, where should I start looking?

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

ahh.. im in the process of getting crown on a root canal so im kinda out of it myself. Back-light is related to panel which jonpry and tmzt are working on. We can turn it off but we cant turn it back on. They will probably need a nand tester since sometimes wince f*cks sh*t up. So you can always help them.

I'm not sure what to attack next. I wanted to implement a blit scaler similar to what dzo did for the vogue. It would allow us to run our device at different resolutions so we dont need to worry about certain roms not fitting properly (like sense ui). If this works, we can in theory run the 2.2 froyo from the wildfire without modifying anything since the gpu will scale it for us. Or if you dont mind an old release, run the hero/eris 2.1 sense ui. If i dont tackle that, i guess i can start looking at something more useful, headset? hmm maybe seeing if we can squeeze more ouf of the gpu. Not sure.. or i can help join the fight against .35 now thats a big project

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

Good luck with that crown. I'll see what I can do to help them out with the screen. And Jonpry pointed me in the right direction for keyboard auto-detection, so I should have a modified rootfs that does it all for us. Apparently the models are stored in /sys/class/htc_hw/machine_variant.

If someone on a tilt2, rhod400, or rhod210 could confirm their ID's, that would be great. Just hook up to ADB and run "cat /sys/class/htc_hw/machine_variant" and let me know what yours is. I'll get the modded rootfs as soon as I can :)

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

How transparent would a scaler like that work? Even on the latest kernel, when running something in Nesoid, if it's scaled at all the lag is quite heavy. If it's only doubled (which should really be a very simple operation) the lag is bad, if it's actually scaled to the screen resolution, the lag is really bad.

What're the benefits of moving to a .35 kernel?

Obviously you're always free to work on whatever, but the headset would be an amazing improvement, not just to be able to use it, but since there aren't many other devs that are in a position to work on it.

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

my computer picks up the usb but it never installs..just shows its connected..i have vista

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

I assume this remains the same across builds? I'm currently running Neopeek's from Haret, and there isn't a file machine_variant but there is a file machtype in htc_hw.

I ran cat on machtype from the terminal (not from ADB) on my Rhod400 and it output:
2292

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

there is a machine_variant but in terminal it said it cant be found..and i dont know whats up with my usb its not connecting at all so i cant try adb..is there something that i didnt download for the pc?

Install the HTC Sync if you have a 32 bit os.

I have Windows 7 64bit. I had to manually install the drivers from android sdk. ADB works on mine


Sent from my HTC Touch Pro 2 on Android with Tapatalk Pro.

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

Yeah, I had to force the driver on my work machine too.

Personally, I'd recommend Droid Explorer for Windows based machines. It takes care of everything for you and lets you run the console from inside it. Grab it here: Droid Explorer

Thanks, but unfortunately the feedback from terminal emulators will give you userland results, and I need to make sure it returns the values pulled on startup (which should be RHOD40000 hopefully). :)

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

have you been able to compile and run the last kernel at all? more changes coming :-). i want to make sure we fixed the issue you were having before.

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

How is Nesoid actually scaling? i want the actual gpu to do the scaling for us not it be handled by a library or android. Android itself will think its running a completely different resolution.

.35? haha.. new kernel. We are running .27 while everyone else is probably running .32. We would run on cleaner code and about 2.5 years worth of improvements. Not to mention bragging rights. You can actually tell someone "your kernel is dog shit.. .35 bitch !!!"

turns our blackstone has headset working, so im going to see if we can use the same code for rhod. Lets cross our fingers.

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

Is anyone working on overall UI smoothness? A few people have mentioned how much more smooth the experience is on neopeek than on XDA; any way we can incorporate whatever neo did?

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

Sorry ACL, had to do a ton of stuff tonight. I'm starting the compile right now, had to re-clone the git. I was messing with pmem yesterday trying to learn, then bash froze when I went to reset the repo. Anyway, it's compiling now, but I won't have a chance to test until tomorrow.

I'm also doing a little testing with that modified rootfs, and it looks to be working great on my phone for auto-detecting the model. I'll get that posted up tomorrow as well for people to test.

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

OK, now I'm really going to bed. I haven't had a chance to test the new NBH, but I went ahead and posted it in the first post for others to mess with if they want. I also uploaded the new rootfs. I would rename your existing rootfs and test this one out.

For the new rootfs, it will use the .kb file if you have one in the andboot. I left that in there so we can override the keyboard layout for those that want to do so. Please delete any .kb files in your andboot folder and let me know if it correctly identifies your keyboard layout :)

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

10-6 didnt detect the right keyboard..and got stuck on animation screen..and thanks for the droid explorer link..ill try it out..i cant get the explorer goin at all to synch with the phone

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

its a completely different build. Its not like just a few changes here and there. Also neopeek is based of cyanogen but im not sure what changes he has made.

Someone should talk to Reef about this. There is nothing really stopping him from going directly to CM source and compiling it himself. It would be nice if we had to make 0 changes so we can rely on the CM team to do the maintenance.

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

Yeah, it seemed to be working for me, but once I started adding ECHO's for debugging, I realized it isn't finding any values there which means it isn't initialized yet.

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

The OS onnEo is smoother, but many apps run much slower. Handsent being a really good example of Neo's weakness. It is much faster on xda. Actually, with the excpetion of Angry Birds, I prefer XDA for all around speed and reliabilty.

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

Yeh, let's don't make any knee-jerk reactions until we know whatever neopeek does differently is actually better. For me, the UI is a tiny bit sluggish but it's definitely not an issue for me (especially when overclocked). It's 10x faster than WM even when not over clocked.

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

I think the reason that cyanogen is a little smoother is that cyanogen is a little smoother on android phones themselves. cyanogen is a real android rom developed for android phones. there team sped it up and made it faster for real androids and all neopeek did was make it so that it can run on our phones. they use the same kernels we do for xdandroid. cyanogen is not the only one there is. I believe he is porting over a bunch of different android roms to run on our phones, all of which are originally tweaked and modded for speed and performance on real androids.

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

That's a great idea--I'll drop him a message. I think Android for the TP2 has made amazing strides, and if we can get the code properly tweaked for performance, I will have (in my opinion) the best non-4G Android phone around. Considering how smoothly Froyo runs on my wife's Touch, given how much beefier our device is, I think we can make this thing scream.

Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update
 

i think we are done with the CM talk. Not nand related.

ive decided to find the good fight on the panel. Others have been asking for headset but i think panel gets priority.