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

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)

Re: NAND Boot Testing - 12-14: Panel power on and off working on some devices

Ooh, I don't think so. The display is still very flaky, even with the 2.32 radio. Could having the slot cycle index set to 0 have any effect? I know that the standard is 2, any thoughts by anyone?

Is it possible to enter qualcomm diagnostic mode without having to be in Windows Mobile?

Re: NAND Boot Testing - 12-14: Panel power on and off working on some devices

No go on the 2.32 radio, I got it to work on 1.96 once. On 2.32 not even once... :(

What about non-unlocked radio? Would that make a difference? I'll try and report back...

EDIT: ** An idea ** Can someone post 2 screen shots of END button LONG PRESS screens so we can have an idea where to press when turning off device, that way we don't blow up the android build on the SDCARD?

Aparently on all radios it says GSM phone found and GSM Rhodium a few lines below..

On 2.32WF first boot it turned off phone (I am guessing when it reached Android after boot animation)
Not sure if radio has anything to do with it...I got same results...

Re: NAND Boot Testing - 12-14: Panel power on and off working on some devices

Yes what you are experiencing is exactly what I am getting.

Re: NAND Boot Testing - 12-14: Panel power on and off working on some devices

I aplogize but I have no experience using logcat or any debugging experience in android. I connected to my device and executed 'logcat'

I also did the same but used 'dmesg'

Here is what I got back when I tried to power on the screen:
Is any of this useful, or can I provide any useful info with this tool?

logcat:

D/KeyguardViewMediator( 1273): wakeWhenReadyLocked(3)
D/KeyguardViewMediator( 1273): handleWakeWhenReady(3)
D/KeyguardViewMediator( 1273): pokeWakelock(5000)
I/power ( 1273): *** set_screen_state 1
D/Sensors ( 1273): sensors activate returing 1
D/lights ( 1273): Setting brightnessMode=0 brightness=6
D/lights ( 1273): Setting brightnessMode=0 brightness=13
D/lights ( 1273): Setting brightnessMode=0 brightness=20
D/lights ( 1273): Setting brightnessMode=0 brightness=27
D/lights ( 1273): Setting brightnessMode=0 brightness=34
D/lights ( 1273): Setting brightnessMode=0 brightness=40
D/lights ( 1273): Setting brightnessMode=0 brightness=47
D/lights ( 1273): Setting brightnessMode=0 brightness=54
D/lights ( 1273): Setting brightnessMode=0 brightness=61
D/lights ( 1273): Setting brightnessMode=0 brightness=68
D/lights ( 1273): Setting brightnessMode=0 brightness=74
D/lights ( 1273): Setting brightnessMode=0 brightness=81
D/lights ( 1273): Setting brightnessMode=0 brightness=88
D/lights ( 1273): Setting brightnessMode=0 brightness=95
D/lights ( 1273): Setting brightnessMode=0 brightness=102
D/lights ( 1273): Setting brightnessMode=0 brightness=95
D/lights ( 1273): Setting brightnessMode=0 brightness=88
D/lights ( 1273): Setting brightnessMode=0 brightness=81
D/lights ( 1273): Setting brightnessMode=0 brightness=74
D/lights ( 1273): Setting brightnessMode=0 brightness=67
D/lights ( 1273): Setting brightnessMode=0 brightness=61
D/lights ( 1273): Setting brightnessMode=0 brightness=54
D/lights ( 1273): Setting brightnessMode=0 brightness=47
D/lights ( 1273): Setting brightnessMode=0 brightness=40
D/lights ( 1273): Setting brightnessMode=0 brightness=33
D/lights ( 1273): Setting brightnessMode=0 brightness=27
D/lights ( 1273): Setting brightnessMode=0 brightness=20
D/lights ( 1273): Setting brightnessMode=0 brightness=13
D/lights ( 1273): Setting brightnessMode=0 brightness=6
D/lights ( 1273): Setting brightnessMode=0 brightness=0
I/power ( 1273): *** set_screen_state 0
D/Sensors ( 1273): sensors activate returing 1
W/BatteryStatsImpl( 1273): Couldn't get kernel wake lock stats
E/Tethering( 1273): attempting to remove unknown iface (usb0), ignoring
D/dalvikvm( 1390): GC_EXPLICIT freed 369 objects / 15848 bytes in 130ms
W/BatteryStatsImpl( 1273): Couldn't get kernel wake lock stats

dmesg:

[ 1369.269317] request_suspend_state: wakeup (3->0) at 1334350000000 (2010-12-31 17:15:44.170000000 UTC)
[ 1369.269500] htc_pwrsink: ID 0, Util 38%, Total 38000 uA
[ 1369.269531] novtec_resume
[ 1369.269622] htcrhod_mddi_power_client (on)
[ 1369.276123] microp-klt: Setting lcd-backlight brightness2 to: 0/10
[ 1369.276763] msm_i2c msm_i2c.0: error, status 63c8
[ 1369.276855] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 1369.294860] micropklt, i2c write retry
[ 1369.294982] mddi_resumed
[ 1369.386718] microp-klt: Setting lcd-backlight brightness2 to: 0/10
[ 1369.406097] hw3d_late_resume: resuming
[ 1369.406188] tssc_manager_resume(): ts->use_irq=1
[ 1369.406249] Sending arm9_low_speed 7
[ 1369.416442] microp-klt: Setting lcd-backlight brightness2 to: 0/10
[ 1369.456726] microp-klt: Setting lcd-backlight brightness2 to: 0/10
[ 1369.476898] microp-klt: Setting lcd-backlight brightness2 to: 1/10
[ 1369.485870] novtec_unblank
[ 1369.486297] micropklt_panel_resume
[ 1369.510498] microp-klt: Setting lcd-backlight brightness2 to: 1/10
[ 1369.527313] microp-klt: Setting lcd-backlight brightness2 to: 1/10
[ 1369.547821] microp-klt: Setting lcd-backlight brightness2 to: 1/10
[ 1369.568511] microp-klt: Setting lcd-backlight brightness2 to: 2/10
[ 1369.589080] microp-klt: Setting lcd-backlight brightness2 to: 2/10
[ 1369.609680] microp-klt: Setting lcd-backlight brightness2 to: 2/10
[ 1369.630310] microp-klt: Setting lcd-backlight brightness2 to: 2/10
[ 1369.650939] microp-klt: Setting lcd-backlight brightness2 to: 3/10
[ 1369.671478] microp-klt: Setting lcd-backlight brightness2 to: 3/10
[ 1369.692108] microp-klt: Setting lcd-backlight brightness2 to: 3/10
[ 1374.378448] microp-klt: Setting lcd-backlight brightness2 to: 3/10
[ 1374.397247] microp-klt: Setting lcd-backlight brightness2 to: 3/10
[ 1374.417816] microp-klt: Setting lcd-backlight brightness2 to: 2/10
[ 1374.437927] microp-klt: Setting lcd-backlight brightness2 to: 2/10
[ 1374.458343] microp-klt: Setting lcd-backlight brightness2 to: 2/10
[ 1374.478759] microp-klt: Setting lcd-backlight brightness2 to: 2/10
[ 1374.499176] microp-klt: Setting lcd-backlight brightness2 to: 1/10
[ 1374.519622] microp-klt: Setting lcd-backlight brightness2 to: 1/10
[ 1374.539886] microp-klt: Setting lcd-backlight brightness2 to: 1/10
[ 1374.560272] microp-klt: Setting lcd-backlight brightness2 to: 1/10
[ 1374.580841] microp-klt: Setting lcd-backlight brightness2 to: 0/10
[ 1374.601104] microp-klt: Setting lcd-backlight brightness2 to: 0/10
[ 1374.621582] microp-klt: Setting lcd-backlight brightness2 to: 0/10
[ 1374.641601] microp-klt: Setting lcd-backlight brightness2 to: 0/10
[ 1374.661712] microp-klt: Setting lcd-backlight brightness2 to: 0/10
[ 1374.682037] request_suspend_state: sleep (0->3) at 1339670000000 (2010-12-31 17:15:49.490000000 UTC)
[ 1374.682159] Sending arm9_low_speed 2
[ 1374.702117] novtec_blank
[ 1374.702209] micropklt_panel_suspend
[ 1374.842163] novtec_suspend
[ 1374.913513] htcrhod_mddi_power_client (off)
[ 1374.942718] mddi_suspended
[ 1374.942749] htc_pwrsink: ID 0, Util 7%, Total 7000 uA
[ 1374.952392] active wake lock PowerManagerService
[ 1374.952423] active wake lock vbus_present

Re: NAND Boot Testing - 12-14: Panel power on and off working on some devices

yea, nothing everyone else hasn't already debugged bro. you're like a month behind haha
try lookin for tut places first, this place is like step8, and you sound like you're on step3 brutha

Dude on boost with dope phone: use 2.XX stock radio, not f-ed up or anything. keep touching screen when bootani is almost done. get screen on by using a combo of end and menu and touching the screen. once up, go to display brightness and set to auto quickly. screen is "all good as it gets" now. plugged in, works fiiiiine. unplugged, after 2-3 good on/offs, its stuck to just backlight and a reboot is neccesary. just soft reset, i've done it roughly 4,678 times and my phones perfectly fine mang.

P.S. ::mumble mumble:: friggin' hd2 guys... ::mumble mumble::
maybe there's something we can learn from? hopefully, cuz they are crazy on top of it

makexip.sh: 24: arm-eabi-as: not found
makexip.sh: 25: arm-eabi-objcopy: not found
mv: cannot stat `tinbootxip': No such file or directory
rm: cannot remove `tinboot.o': No such file or directory

also, my tinboot doesn't work now.... updated it to 30th....

Re: NAND Boot Testing - 12-14: Panel power on and off working on some devices

Quote:

Originally Posted by MassStash (Post 2027321)

I really don't think the Radio is going to affect the display. Hopefully ACL has some good stuff coming soon. As for tinboot, I have always had to modify the script to make it work.

Quote:

Originally Posted by m4f1050 (Post 2027255)

Happy Holidays to all! Sold my EVO and HD2, back on Touch Pro2 :D

Had a lot to catch up on... downloaded the latest and going to test now!

BTW, I have a Sprint version... 1.96WU radio (unlocked sim for GSM, but using CDMA side)

EDIT: 1st boot phone rebooted. Noticed it says GSM phone found and a few lines below GSM Rhodium detected, how can I switch it to CDMA?

A thought... Can we use ADB in case screen doesn't come up and reboot phone via ADB? <----- NO GO

Ok, phone booted, but I started pressing END and POWER trying to get the screen back on, it came on for a split second when pressing END and now it won't come on at all... On ADB SHELL I tried to reboot and NO GO... Also when I do an ls I get what looks like VT100 code? Any way of seeing these colors on Windows ADB?

Don't know if phone is in CDMA or GSM mode, will try batt pull and trying again..

Ok, this time I left it alone for a while, then I pressed END and there was the lock screen but went away. Apparently if you start pressing buttons you lock it up... Oh and screen goes to sleep on boot animation...that's why I started pressing the buttons. Another finding... If you press POWER first you get the 2 screen flashes and screen doesn't come back up.

If you are using the reference build, don't worry about the GSM phone found. It will always say that, but then later it should say CDMA phone found. If you are using the experimental build, it could be something wrong with the new rootfs.

Also, I usually have it reboot on my for some reason after the first boot, but then it seems to work (of course the panel is still finnicky).

Re: NAND Boot Testing - 12-14: Panel power on and off working on some devices

Touching screen while boot animation does nothing, I tried it many times. Will try the other suggestions though..

Noticed something weird now.... The xdandroid animation at the beginning was flashing (turning on and off very fast, like 4 to 6 times a second)

Pressing both MENU and END got my screen on, went to MENU, SETTINGS, DISPLAY and AUTOMATIC BRIGHTNESS was OFF, turned it on and it stayed on. When I tried turning it off the screen turned off! :O
AUTO BRIGHTNESS is back on...that seemed to fix it...

EDIT: Let it sleep and when tried to turn screen back on it didn't want to, not even with MENU and END.... :/

EDIT 2: Is there a way to reboot android propperly? reboot -f is just a soft reset sort-of... I want it to go through the init and not to leave partition "dirty"...

For now I installed VNC server and DYN IP update utility to connect to phone and be able to see what's on the screen... LOL

Re: NAND Boot Testing - 12-14: Panel power on and off working on some devices

ACL:

Are the attached disptools.dll files from the ROM image I use on my rhod400 for windows similar to the ones that you used for your display code?

Re: NAND Boot Testing - 12-14: Panel power on and off working on some devices

Quote:

Originally Posted by natemcnutty (Post 2027184)

ACL, I tried to dump the ROM without having to flash it to my device. Unfortunately, I must not be using the right tools to pull the DLL out. I basically did the NBH to NB to payload to imgfs to dump, and I used a kitchen for one decompile and the actual tools manually for the second method. I have uploaded the results of both, and hopefully they are helpful (but I'm betting I'll need to flash the actual OS to pull the compiled file out for you).

Also, kind of odd no one has reported anything on the new patches or the experimental build I put up. I'll be playing around with that a bunch more tomorrow since I have the day off :)

I dunno whats up with this file. I just need the dll itself. I saw a bunch of s00 and other stuff in here. Not sure what to do with it.

Re: NAND Boot Testing - 12-14: Panel power on and off working on some devices

Quote:

Originally Posted by mpannen (Post 2027465)

ACL:

Are the attached disptools.dll files from the ROM image I use on my rhod400 for windows similar to the ones that you used for your display code?

i have a rhod400 so this is prob the same one i have. i need the gsm version for those poor rhod100 folk.