Originally Posted by [ACL] (Post 1966839)

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

Originally Posted by [ACL] (Post 1966839)

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

Originally Posted by natemcnutty (Post 1966844)

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 :)

Originally Posted by manekineko (Post 1966877)

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 from the terminal (not from ADB) on my Rhod400 and it output:
2292

Originally Posted by damage_them (Post 1966874)

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

Originally Posted by coolsilver (Post 1966974)

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.

Originally Posted by damage_them (Post 1966882)

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?

Originally Posted by manekineko (Post 1966877)

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

Originally Posted by natemcnutty (Post 1966844)

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 :)

Originally Posted by manekineko (Post 1966869)

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.

Originally Posted by [ACL] (Post 1967025)

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 !!!"