![]() |
Re: Linux/Android on CDMA Touch Pro (RAPH800)
Quote:
|
Re: Linux/Android on CDMA Touch Pro (RAPH800)
This is awesome! Between rootrom and this I have a brand new phone to play with.
|
Re: Linux/Android on CDMA Touch Pro (RAPH800)
Want the one from the Hero? lol
|
Re: Linux/Android on CDMA Touch Pro (RAPH800)
I am running the newest compile and the market loads but nothing seems to want to download from it, bluetooth is still not working, unless there is a step im missing, and WiFi is not on automatically like it was before for me. The sensitivity of the screen seems good though
|
Re: Linux/Android on CDMA Touch Pro (RAPH800)
New build is up guys
|
Re: Linux/Android on CDMA Touch Pro (RAPH800)
Quote:
|
Re: Linux/Android on CDMA Touch Pro (RAPH800)
From here http://xdandroid.southcape.org and I was just downloading the new March 1st one just before you posted about it heh
The Raph800 startup file needs to be edited because it does not have the line breaks in proper and everything is jumbled up |
Re: Linux/Android on CDMA Touch Pro (RAPH800)
The startup text for the Raph800 should look like this
Code:
set ramsize 0x6000000 Code:
set ramsize 0x10000000 |
Re: Linux/Android on CDMA Touch Pro (RAPH800)
I am running the March 1st build and it shows 3g connected and it auto setup the CDMA network but I am unable to actually get an internet connection I have not dropped a command prompt yet to see whats going on but just trying to setup my google account and sync or open a browser has not been working
|
Re: Linux/Android on CDMA Touch Pro (RAPH800)
raph800 startup.txt looks fine on my end -- probably is not DOS formatted, which is why the line breaks don't show up for you. Grab Notepad++ to edit it (and everything else, it's a stellar piece of open source software). Or just use the formatted version TWiST posted right there. Or grab it here.
The difference between the startup.txt files is... the... differences between them. The parts that are different. I'm a bit confused by the question. the raph800 version sets a different machine type (machtype/mtype), which allows the kernel to know which specific code to execute. And it sets some different values in the cmdline (the g sensor has different axes than on the raph100, for instance). Haven't tested the new build, but I have some thoughts about data connection troubles. Hint: it all comes down to APNs. ...I hate APNs. |
All times are GMT -4. The time now is 08:11 PM. |
Powered by vBulletin® ©2000 - 2025, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com