|
||||
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
Quote:
|
|
||||
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
I suck
![]() Last edited by xlarkascendingx; 09-22-2010 at 06:38 PM. |
|
||||
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
Quote:
![]() |
|
||||
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
I changed the mtype from 2040 to 2039 -- same problem.
To clarify, it's hanging after the HaRET progress bar completes. The bar disappears and the system freezes. By the way -- thank you for everyone helping to troubleshoot this. |
|
||||
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
Quote:
Code:
set ramsize 0x10000000 set ramaddr 0x10000000 set mtype 2182 set KERNEL zImage set initrd initrd.gz set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 acpuclock.force_turbo=1" boot |
|
||||
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
Just looked at my startup and compared it to what you had posted. With the exception of a couple lines, yours is the same. I have rel_path, hw3d forced, overclocked, and physkeyboard all in mine as well, but those should NOT have any impact on this issue. Only thing I can think of is to try posting over in the main thread at XDA and see if anyone there can help you.
EDIT: Or change it to 2182. Arrrghhh: How did Makk and I both miss that? Last edited by chrialex; 09-23-2010 at 01:26 PM. |
|
||||
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
LOL I don't know... More coffee maybe? I didn't want to jump in until I knew what the issue was, I knew it had to be something with the startup tho
![]() You might've also assumed he was using the correct startup to begin with... I'm kinda curious what was up with that. |
|
||||
Re: Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!
OK. Right at the beginning, he asked which startup config to use. I said Raph500. He said ok. From that point on, I didn't consider that he might have been using the wrong one. And I don't look at the files often enough anymore to identify based on the mtypes.
Yikes. I think we call this phenomenon 'perceptual blindness'. ![]() |
![]() |
|
Tags |
android, donut, eclair, linux |
|
|