|
||||
Re: [1/25/2010] Google Android for TP2 CDMA [In Dev]
Not even close. The only resemblence is you mentioning it.
|
This post has been thanked 2 times. |
|
||||
Re: [1/25/2010] Google Android for TP2 CDMA [In Dev]
Quote:
*edit: like 10 mins after i posted this i used civics tp2_defconfig and made a working zImage with the linux-msm kernel Last edited by ghost_deini; 02-11-2010 at 11:47 AM. |
|
||||
Re: [1/25/2010] Google Android for TP2 CDMA [In Dev]
Hehe... I was just thinking the same thing.
On topic: Civic, have you been following the developments on the GSM side? There have been some significant improvements. Will it be possible to merge some of those changes with yours (or vice versa) at some point after you complete work on the RIL? |
|
||||
Re: [1/25/2010] Google Android for TP2 CDMA [In Dev]
It starts small and ends big, and its how it happened in the HSPL thread. Kinda like cancer fellas, it doesn't fully metastasize out of no where; there is a beginning...
|
|
||||
Re: [1/25/2010] Google Android for TP2 CDMA [In Dev]
again i say patience is a virtue....the TP2's work fine now. But this will greatly increase that feeling.=D>
|
|
||||
Re: [1/25/2010] Google Android for TP2 CDMA [In Dev]
Quote:
I do not think there will ever be a way to stop someone from asking for an ETA. It kind of gives people hope and lets them know the progress that the developer is expecting to see if things go there way. As long as people can take the dissapointment when the milestone dates do not hit....... Civic gave an ETA on when he thought the data would be completed. He ran into some trouble and will not hit that date. I didn't see anyone complaining here because of that, actually quite the opposite, everyone was fully supportive and looking to help in any way they can....... Last edited by eman; 02-11-2010 at 02:24 PM. |
|
||||
Re: [1/25/2010] Google Android for TP2 CDMA [In Dev]
Can there be anything gained by using info from the TP1 builds?
|
|
||||
Re: [1/25/2010] Google Android for TP2 CDMA [In Dev]
I was thinking this too since the hardware is almost identical
|
|
||||
Re: [1/25/2010] Google Android for TP2 CDMA [In Dev]
Actually, the problem is that the hardware is NOT almost identical, at least not where it counts.
One of the biggest differences is the new radio chips- don't you guys remember how one of the selling points of the TP2 was that the new wireless chips don't heat up as much with use as the TP1 (which you could fry an egg on after a long phone call)? If they were more identical, we'd have gotten the MS Bluetooth stack working since many people are unhappy with the Widcomm one. Sadly, Widcomm is the only stack that works with this chipset at the moment. I believe all the wireless services are on the same chip now (WiFi, CDMA, GSM, BT), and since the TP1 doesn't support GSM and the bluetooth control is different, I'd say they aren't actually similar enough. I'm wondering if there are any Android phones that use our chipset... Someone mentioned the Eris, but I'm actually not sure anymore. Anyone know?
__________________
Techcitement.com - I write for these guys pretty regularly. A Blog about tech that makes people excited.
Diary of a Mobile Enthusiast - My personal blog... haven't had time to update it.... *sigh* Hey, if I've helped you in any way, click the ads on my blog so I can make some $$!! |
|
Tags |
android, cdma, sprint, touch pro 2, tp2 |
|
|