This post has been thanked 1 times. |
|
||||
Re: NAND Boot Testing - Auto-brightness Testing: 10-28. Automatic Keyboard Detection!
Quote:
As far as installing a ROM, you can't because Android is partially running from the internal NAND where the ROM would be stored. USB storage doesn't work because the SD card is mounted in Android. You can use Droid Explorer or something similar to browse the SD Card though. LCD backlight should be turning off completely, but it does have a difficulty turning back on. Keyboard LED's not working is a known issue as well. As far as remapping the buttons, it's a very simple change, but ACL hasn't committed those changes to the NAND tree. He's got a lot more important things he's working on, but I will test making the changes to my local repo and create a patch for him to apply whenever he feels like it. I get all night to myself, so I'll be testing importing all rhodium related commits one at a time and creating patches if they work properly on nand. Hoping to revisit 3.5mm headphones and mess around with panel init code. Unfortunately, my coding skills are quite limited, so I have to resort to borrowing code from elsewhere |
|
||||
Re: NAND Boot Testing - Auto-brightness Testing: 10-28. Automatic Keyboard Detection!
Awesome!
1/2 hour later (and after installing mightyrom (smallest rom I had) and setting up my MIN/MDN and M.IP stuff then Tinboot back on NAND) I got 3G working perfect and at superb speeds (1414 kbit/sec) dslreports.com/mspeed 1mb test.... Good luck with your playing around tonight. BTW, how do I get the backlight to work? Is it in the 1st page? Or are there instructions on how to do it elsewhere? EDIT: What is CDC ACM Data? Last edited by m4f1050; 11-05-2010 at 08:50 PM. |
|
||||
Wirelessly posted (Opera/9.80 (Windows Mobile; Opera Mini/5.1.21594/21.549; U; en) Presto/2.5.25 Version/10.54)
Quote:
|
|
||||
Re: NAND Boot Testing - Auto-brightness Testing: 10-28. Automatic Keyboard Detection!
I still can't get the backlight to turn off... It is black but you can tell the LCD part is lit...you see a real dark grey background on the phone. What can I do to resolv this?
|
|
||||
Right now the latest version the screen turns off but will not turn on. They are looking into some registers and things that Haret sets from windows mobile. With this we can get the nand kernels working and with the framebuffer conversion probably loads better.
Sent from my HTC Touch Pro 2 on Android with Tapatalk Pro. |
|
||||
Wirelessly posted (Opera/9.80 (Windows Mobile; Opera Mini/5.1.21594/21.549; U; en) Presto/2.5.25 Version/10.54)
Quote:
I've had the latest couple of nand builds on my device for at least 8 hours each and have had the opposite of what you are reporting. |
|
||||
Re: NAND Boot Testing - Auto-brightness Testing: 10-28. Automatic Keyboard Detection!
hmm... I just noticed my GPS never gets a fix anymore.
Probably some minor bug. |
|
||||
Re: NAND Boot Testing - Auto-brightness Testing: 10-28. Automatic Keyboard Detection!
Quote:
Issue is that Google and CodeAurora have completely different framebuffers. The one im specifically working on is from Google (HTC uses google FB). But other devices like samsung use CA. Now we haven't had success yet in getting the CA FB to work. There is a big possibility this may be a faster FB which will make the tp2 fly... but thats all in the works. This is a big change (prob bigger than the USB), so it will take a while to iron everything out.
__________________
|
This post has been thanked 3 times. |
|
||||
Re: NAND Boot Testing - Auto-brightness Testing: 10-28. Automatic Keyboard Detection!
Quote:
And thanks for keeping us up-to-date. I still haven't had a chance to look at any commits that were made to linux-msm that weren't applied to nand. Got kind of sick over the weekend, and I still haven't quite recovered. |
|
|
|