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

mecpfirst · #**271** (**permalink**) 01-23-2010, 02:00 PM

ok .... booted 1/22 package with the xda files for raph(500) .... this is nice. have text both ways, can make and recieve calls. i cant talk but i can hear. interface works well and seems to speed up and slow down. when it is running best it is FAST and usually pops up a force close error right after it slows down. no wifi, no data at this time tho the icon at the top bounces between "3g" and a capital letter "E" ... when i try to turn on wifi it almost immediately says unable to start wifi

peterm20 · #**272** (**permalink**) 01-23-2010, 02:14 PM

Quote:

Originally Posted by mecpfirst

ok .... booted 1/22 package with the xda files for raph(500) .... this is nice. have text both ways, can make and recieve calls. i cant talk but i can hear. interface works well and seems to speed up and slow down. when it is running best it is FAST and usually pops up a force close error right after it slows down. no wifi, no data at this time tho the icon at the top bounces between "3g" and a capital letter "E" ... when i try to turn on wifi it almost immediately says unable to start wifi

Are you using the modules/zimage from the first post? Data and wifi work for me here on the sprint TP.

mecpfirst · #**273** (**permalink**) 01-23-2010, 03:36 PM

verizon touch pro is a very different animal. a lot of the basic stuff is the same but a lot of the drivers are different. not as many people with the di vices so slower going with getting everything up and running.

Yibrushn · #**274** (**permalink**) 01-23-2010, 04:29 PM

So does anyone know if it will be helpful now that htc has released the kernel source for the HTC Hero (sprint). I'm assuming that a lot of the hardware is similar?
Thanks

Yibrushn · #**275** (**permalink**) 01-23-2010, 04:46 PM

Another quick question is everyone using the module and zimage from the first post here or from the Xda site?

Kevets · #**276** (**permalink**) 01-23-2010, 09:22 PM

I used all the files listed in the first post here and it works fine.

pierocksmysocks · #**277** (**permalink**) 01-24-2010, 12:55 PM

I've been using the files from the first post here rather than xda. In the past I had issues using files posted on xda, so I was sticking with what worked. Just loaded 1-24 build and am trying to get it up and running. Looks like the calibration is all kinds of jacked up. However, the ui in general was a lot more responsive..

peterm20 · #**278** (**permalink**) 01-24-2010, 02:16 PM

Quote:

Originally Posted by pierocksmysocks

I've been using the files from the first post here rather than xda. In the past I had issues using files posted on xda, so I was sticking with what worked. Just loaded 1-24 build and am trying to get it up and running. Looks like the calibration is all kinds of jacked up. However, the ui in general was a lot more responsive..

Did you load the eclare.conf from the first page in this post? It helps a lot I have not noticed the calibration too much. Seems like its off on the extreme corners of the screen. Also the rootfs.img on XDA isn't really for us I guess. I wouldn't put it on there unless you are having problems with wifi/data.

EvgeniX · #**279** (**permalink**) 01-24-2010, 03:16 PM

Quote:

Originally Posted by peterm20

Did you load the eclare.conf from the first page in this post? It helps a lot I have not noticed the calibration too much. Seems like its off on the extreme corners of the screen. Also the rootfs.img on XDA isn't really for us I guess. I wouldn't put it on there unless you are having problems with wifi/data.

bur where you take rootfs.img for us?

breity · #**280** (**permalink**) 01-24-2010, 05:06 PM

Jan 24th build works great with the CDMA files here. System is MUCH faster and battery life seems better.

Only problem with that build is the calendar does not work. CalendarProvider.apk won't install. So hopefully someone will have a fix for that soon.

I'm also using a customized eclair.user.conf, which has my personal screen settings, as computhug outlined in post 181. Ever since I followed those instructions, screen calibration has been almost flawless.