Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS! - Page 365

xlarkascendingx · #**3641** (**permalink**) 09-22-2010, 05:50 PM

I'm looking up u2nl right now and autostart, hopefully I can get this to work. Then I'll try to find a way to make Android boot FASTER! haha

**arrrghhh** · #**3642** (**permalink**) 09-22-2010, 06:02 PM

Quote:

Originally Posted by makkonen

do a google search for u2nl and autostart. It should work fine on our kernel, as we've got full netfilter support. It tunnels ('u 2nl', get it?) everything over the proxy port. Good luck; I don't think anyone has actually tried it with xdandroid yet. (at least, not that I've heard of.)

Don't see why GPS wouldn't be working already.

You are full of awesome Makk.

xlarkascendingx · #**3643** (**permalink**) 09-22-2010, 06:13 PM

I suck

Why can't the settings just be easily accessible? Darn Linux :'(

**arrrghhh** · #**3644** (**permalink**) 09-22-2010, 09:11 PM

Quote:

Originally Posted by xlarkascendingx

I suck

Why can't the settings just be easily accessible? Darn Linux :'(

Better than being completely inaccessible!

xlarkascendingx · #**3645** (**permalink**) 09-22-2010, 09:47 PM

yeah i cant find shit on u2nl or autostart

komgol · #**3646** (**permalink**) 09-23-2010, 01:02 PM

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.

**arrrghhh** · #**3647** (**permalink**) 09-23-2010, 01:21 PM

Quote:

Originally Posted by komgol

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.

Uhm... dude? It looks like you've got a RAPH500 - Verizon, right? mtype should be 2182.

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

That's the startup.txt from the AIO on the first post for the RAPH500...

chrialex · #**3648** (**permalink**) 09-23-2010, 01:23 PM

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?

**arrrghhh** · #**3649** (**permalink**) 09-23-2010, 01:29 PM

Quote:

Originally Posted by chrialex

Arrrghhh: How did Makk and I both miss that?

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.

**makkonen** · #**3650** (**permalink**) 09-23-2010, 05:00 PM

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'.