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

**arrrghhh** · #**2731** (**permalink**) 06-08-2010, 02:17 PM

Quote:

Originally Posted by mrkite38

Looks like it's ext2 partition to me (as opposed to an .img file). There are some nice advantages to that over sqsh, r/w, speed, etc. but definitely nothing new!

Oh no, nothing "new" really. Just a different way of doing things, wanted to see if anyone had done it and how significant the difference was (if at all)...

hamagc · #**2732** (**permalink**) 06-08-2010, 02:26 PM

i saw a diam500 user saying it was really fast. thats about it. thedeadcpu said he was going to try it but i don't know if he ever did or not.

mrkite38 · #**2733** (**permalink**) 06-08-2010, 02:37 PM

Quote:

Originally Posted by arrrghhh

Oh no, nothing "new" really. Just a different way of doing things, wanted to see if anyone had done it and how significant the difference was (if at all)...

It was a nice improvement on vogue back when we did it, 2nd only to nand. I'd rank them, from slow to fast,
sqsh
ext .img on fat32
ext part
nand

there should be no surprises there, though - the more layers you remove between android and the hardware, the faster it goes!

hamagc · #**2734** (**permalink**) 06-08-2010, 02:39 PM

how much faster would you say? it seems pretty fast as is in our build.

**makkonen** · #**2735** (**permalink**) 06-08-2010, 02:46 PM

Quote:

Originally Posted by tdcrone

- I had an odd bug: I wasn't doing anything significant - clicked the 'phone' phyiscal button, I think - and Android got stuck for a minute or so, and then went to the colored X screen. Booted up from the X as usual, found Sprint and signal, but no data. The oddity is that the phone itself did not reset and did not go into WM, Android just jumped to X for no clear reason (watchdog?) and then got into this Android-with-no-data.

When it drops back to the boot animation and then comes back (it's happened to me a number of times) it means that the kernel hasn't panicked, the low level stuff is ok... but Android crashed and restarted. Sometimes it'll go from there into a boot loop... sometimes it'll come back up and run fine.

Since Android restarted, but the modem didn't reinitialize, it probably had trouble figuring out how to bring up a network connection. It's possible going into and out of airplane mode (or manually dropping 3G and then bringing it up again, though I think you need a 3rd party widget to do that) would resolve it, but I'm not sure.

Quote:

Originally Posted by 88fingerslukee

I'm having issues with getting GPS signal locks. I see the satellites right away so I know it's working but it takes somewhere between 5 and ∞ te tell me where I am. That said, I don't think the Location feature has ever worked running Android before, not even the IP location feature.

Is aGPS enabled for Bell Mobility in Android? Is there some .conf file that I can simply add the servers to (wishful thinking)?

Some folks have mentioned turning on GPS and trying to get a lock in WinMo before booting into Android. Something about having the ephemeris updated helping to get locks quicker.

I still haven't played with it, so I have no idea. I gather that if people are getting locks in under 15-20 minutes, aGPS in general must be functioning. It would seem that if it works at all, it should work on Bell.

mrkite38 · #**2736** (**permalink**) 06-08-2010, 02:57 PM

Quote:

Originally Posted by hamagc

how much faster would you say? it seems pretty fast as is in our build.

good point - and with the significant difference in memory and proc speed between TP and vogue, the difference may not be that noticeable. i'm new to the tp side and i've got a 500 so haven't had much time to get familiar with the speed, etc. I've asked myn if he'd sqsh up his new warm eclair for me so i can get a side-by-side comparison for my own reference.

**makkonen** · #**2737** (**permalink**) 06-08-2010, 02:59 PM

oh yeah, re: sqsh vs ext2 vs ext2 partition, I found there to be no speed difference. I don't know if TP vs Vogue one is more IO bound and the other more processor or memory bound or whatever, but it just didn't seem to provide any boost.

In addition, the partition seemed more prone to corruption, in my case; no one has duplicated my problems on that count, though, so it could just be me.

hamagc · #**2738** (**permalink**) 06-08-2010, 03:05 PM

phh said the reason we went with a fat32 and sqsh system is because fat32 is better for big linear files. but that both suck lol.

mrkite38 · #**2739** (**permalink**) 06-08-2010, 03:29 PM

Quote:

Originally Posted by hamagc

phh said the reason we went with a fat32 and sqsh system is because fat32 is better for big linear files. but that both suck lol.

lol sounds just like something dzo would say - those guys always seem to have the answers...

**arrrghhh** · #**2740** (**permalink**) 06-08-2010, 03:38 PM

Hrm. Yea, doesn't really sound worth it. These builds are plenty fast (for me) it's just the random crashes & battery life that I'd like to improve. I didn't think the ext2 system would either, so there ya go.

I haven't tested it either, I'm at work and my Ubuntu vm is giving me guff...