Quote:
Originally Posted by Mazzakre
How do we get this loading up from the Android folder? I was able to do it with the download from Civic's thread but when I tried with this one it just gave me the cant find system.img error
|
The android folder no longer works. (It was conflicting with apps that created their own android folder in the sdcard, so it was changed.) If you still want to segregate your android files, change the android folder to 'andboot'.
Or you can add rel_path=whatever to your cmdline (in startup.txt) and then use whatever directory. (You need the
latest initrd.gz for this to work correctly, though.)
Quote:
Originally Posted by reekotubbs
What should be the values of the ts-calibration file I have the following:
831,897,204,879,196,876,478,524,827,177
but everything is way off on my touch screen
edit: the calibration is time sensitive, so you need to touch the "+" signs quickly
|
It is not time sensitive, it's just touch sensitive... that is, very touch sensitive. If you look at what you have there, it's 5 sets of x,y coordinates, and your second and third pair are essentially the same. Meaning it read the second point twice, making the third and fourth points wrong.
If you have trouble with the calibration, just reboot to winmo and delete ts-calibration from your android folder on your sdcard. It will run the calibration again on the next boot.
Quote:
Originally Posted by bytethegroove
This pulled from ppcgeeks orignal android thread....first post
which that thread got me here
|
I would take that link down, simply because it confuses the issue. That's 95-Civic's old build, which contains a few out-of-tree hacks. This is the new one that's a little closer to lining up with the mainline development.
Quote:
Originally Posted by kawaiius
I love this and am very appreciative of MrPippy for doing this but i dont think ill be trying it till he gets cdma data working for Verizon. Can't wait till then!
|
I know post 1 says Sprint only, but I'd try it with Verizon anyway. The problem (at least as I know it, I haven't spoken with MrPippy about it) tends to be with carriers that require a username and password to connect to data, and I don't actually think Verizon does so. I know a few months ago when people were getting up and running with the RAPH500, it could connect to data without all the trouble that USCC et al were giving.
I could be wrong on that count, though. (There are a number of other issues that could cause a problem.) Can anyone confirm, up or down, whether data's working on Verizon?