PPCGeeks

PPCGeeks (http://forum.ppcgeeks.com/index.php)
-   Android On TP2 Development (http://forum.ppcgeeks.com/forumdisplay.php?f=319)
-   -   NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery (http://forum.ppcgeeks.com/showthread.php?t=134598)

natemcnutty 10-29-2010 05:33 PM

Re: NAND Boot Testing - Auto-brightness Testing: 10-28. Automatic Keyboard Detection!
 
Quote:

Originally Posted by [ACL] (Post 1984030)
Yeah... sounds like a solid plan. I'll commit those changes.

Awesome :)

Also, not sure if it matters, but line 14 of makexip.sh - tinboot-linux-msm in Tinboot for linux-msm - Gitorious should be -f instead of -a

and line 28 of http://gitorious.org/tinboot-for-lin...ter/makenbh.sh should be wine tools/yang.exe instead of just yang :)

damage_them 10-29-2010 10:06 PM

Re: NAND Boot Testing - Auto-brightness Testing: 10-28. Automatic Keyboard Detection!
 
ohh yeaa!! nice!! some progress..ready to test soon as this drops!!..keep up the good work you guys :)

[ACL] 10-30-2010 03:52 AM

Re: NAND Boot Testing - Auto-brightness Testing: 10-28. Automatic Keyboard Detection!
 
Quote:

Originally Posted by natemcnutty (Post 1984038)
Awesome :)

Also, not sure if it matters, but line 14 of makexip.sh - tinboot-linux-msm in Tinboot for linux-msm - Gitorious should be -f instead of -a

and line 28 of makenbh.sh - tinboot-linux-msm in Tinboot for linux-msm - Gitorious should be wine tools/yang.exe instead of just yang :)

ahh.. well it doesnt make a diff according to this.

Bash Reference Manual

But -a is apparently deprecated and -e must be used. So i guess ill make that change.

also we have a yang that does not use wine. I don't think its uploaded. so ill take care of that as well.Thanks a lot bro for pointing that out.

I dont think wozzer and i ever expected others to get this involved. So we made a messy job just getting the basics up there for tinboot. Glad you guys get to fine tune it to perfection. Also once you guys get comfy with the code, feel free to play around with it or ask me any specifics. The more we have people looking into the kernel the faster we can fix that mammoth as well.

natemcnutty 10-30-2010 03:52 PM

Re: NAND Boot Testing - Auto-brightness Testing: 10-28. Automatic Keyboard Detection!
 
Quote:

Originally Posted by [ACL] (Post 1984317)
ahh.. well it doesnt make a diff according to this.

Bash Reference Manual

But -a is apparently deprecated and -e must be used. So i guess ill make that change.

also we have a yang that does not use wine. I don't think its uploaded. so ill take care of that as well.Thanks a lot bro for pointing that out.

I dont think wozzer and i ever expected others to get this involved. So we made a messy job just getting the basics up there for tinboot. Glad you guys get to fine tune it to perfection. Also once you guys get comfy with the code, feel free to play around with it or ask me any specifics. The more we have people looking into the kernel the faster we can fix that mammoth as well.

Yeah, I figured you guys actually put the linux yang in your var path. I ended up grabbing the linux yang originally, but I started using the .exe when you put that one up on tinboot :P

Out of curiosity, where did we leave off on moving modules to the nand? That is one thing I would love to take a look at, but like you and Wozz, I'm concerned about bricking my phone. :)

pts69666 10-30-2010 07:33 PM

Re: NAND Boot Testing - Auto-brightness Testing: 10-28. Automatic Keyboard Detection!
 
Quote:

Originally Posted by natemcnutty (Post 1984487)
Yeah, I figured you guys actually put the linux yang in your var path. I ended up grabbing the linux yang originally, but I started using the .exe when you put that one up on tinboot :P

Out of curiosity, where did we leave off on moving modules to the nand? That is one thing I would love to take a look at, but like you and Wozz, I'm concerned about bricking my phone. :)

im not worried bout bricking mine if you need any testing =P i have the insurance and a backup. I can play stupid with sprint, ive done it before =P

edwill 10-31-2010 09:27 PM

Startup cycles
 
I followed the instructions but the phone shows the TP2 logo, Vibrates twice, shows a small amout of code, fades to black then reboots in this cycle contiously. I have to go to the boot loader to keep it from cycling.

I have the package from 10/29
I have a Rhod210 (T-Mo TP2)
4GB Class4 HC SD card ( this the 3rd card)

natemcnutty 10-31-2010 09:35 PM

Re: Startup cycles
 
Quote:

Originally Posted by edwill (Post 1985072)
I followed the instructions but the phone shows the TP2 logo, Vibrates twice, shows a small amout of code, fades to black then reboots in this cycle contiously. I have to go to the boot loader to keep it from cycling.

I have the package from 10/29
I have a Rhod210 (T-Mo TP2)
4GB Class4 HC SD card ( this the 3rd card)

Make sure that you are using the modified rootfs as that will keep your backlight enabled. The problem is that it still doesn't turn back on properly once you turn it off. There is something with the panel init code that needs to be worked on, and I think ACL was going to be looking into it over the weekend if he had time.

edwill 10-31-2010 10:11 PM

Re: Startup cycles
 
Quote:

Originally Posted by natemcnutty (Post 1985078)
Make sure that you are using the modified rootfs as that will keep your backlight enabled.


The one I am using is 201028-36b2308 from the first page. Is there another one?

[ACL] 10-31-2010 10:51 PM

Re: Startup cycles
 
Quote:

Originally Posted by natemcnutty (Post 1985078)
Make sure that you are using the modified rootfs as that will keep your backlight enabled. The problem is that it still doesn't turn back on properly once you turn it off. There is something with the panel init code that needs to be worked on, and I think ACL was going to be looking into it over the weekend if he had time.

i ve been looking at it and when i had to disable autobacklight we are ok. But now im running into the same issue that when we power down the lcd, we cant wake back up. So its to rethink this strategy. Autobacklight has nothing to do with panel down and up by the way.. Just that wistilt mixed them both into the same commit. Eventually it will be separated again.

Ive tried the topaz init which we thought might work.. well it doesnt .. so need to get back to emwe and wistilt on that. Ive also been working on the clock code again to see why the hell our framebuffer is so damn slow. Cant say for sure but other devices like the g1 have faster frame buffers which make no sense. Something in our code is slowing it down.

what about you guys? anything fun? i dont know if yall noticed but i pushed those changes to tinboot

natemcnutty 11-01-2010 10:58 AM

Wirelessly posted (Opera/9.80 (Windows Mobile; Opera Mini/5.1.21594/21.529; U; en) Presto/2.5.25 Version/10.54)

Quote:

Originally Posted by [ACL
]
Quote:

Originally Posted by natemcnutty (Post 1985078)
Make sure that you are using the modified rootfs as that will keep your backlight enabled. The problem is that it still doesn't turn back on properly once you turn it off. There is something with the panel init code that needs to be worked on, and I think ACL was going to be looking into it over the weekend if he had time.

i ve been looking at it and when i had to disable autobacklight we are ok. But now im running into the same issue that when we power down the lcd, we cant wake back up. So its to rethink this strategy. Autobacklight has nothing to do with panel down and up by the way.. Just that wistilt mixed them both into the same commit. Eventually it will be separated again.

Ive tried the topaz init which we thought might work.. well it doesnt .. so need to get back to emwe and wistilt on that. Ive also been working on the clock code again to see why the hell our framebuffer is so damn slow. Cant say for sure but other devices like the g1 have faster frame buffers which make no sense. Something in our code is slowing it down.

what about you guys? anything fun? i dont know if yall noticed but i pushed those changes to tinboot

We all appreciate the hard work ACL :)

I've been tinkering with the 3.5mm auto-detect by using printk's as recommended by jonpry. Not really sure what I'm doing, but I'm learning :P

Is there anything that is working on haret that people really want to see on nand?


All times are GMT -4. The time now is 07:56 PM.

Powered by vBulletin® ©2000 - 2025, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com


Content Relevant URLs by vBSEO 3.6.0