Re: Next for Android on TP2
 

It's all perception. I perceived him to be whining about battery, and you perceived me to be whining about him. I wasn't whining, just telling him to STFU unless he has some fixes that can be pushed.

Besides, you just look like another nobody who hasn't contributed anything. Meaning what you have to say, really doesn't matter to me. Not that I like being perceived as a whiner, but from you... it's pretty meaningless.

Re: Next for Android on TP2
 

ok .. you guys just flooding this post now. To help end this pissing contest, this is how it actually works.

We work on whatever we can work on. Every part of the system has already been looked into but either we didnt have enough information at the time or we simply failed so we move on to the next broken piece. So even if everyone wants camera, that hurdle that stopped us in the past will stop us again unless we figure out something new.

Also here is the status on whats going on with what everyone wants.

BT - probably last on the list right now since we have bigger issues
OpenGL - i tried for about a month and im stuck at the same place. We arent getting any interrupts which is needed for the 3d to actually work.
Camera - There is some work being done right now. Android itself is ready but the kernel part is still missing. Memory issues appear to the be root cause.
Battery Meter - Topaz devs made a new battery algorithm. I have the source once i can confirm with our values from the wince drvs are the same, then we can probably test.
Speed: ?? we are running debug kernels so id wait on this until the end.

No one mentioned power management ? Thats probably more important that some of the stuff above.

Re: Next for Android on TP2
 

How about a working Build.prop Fingerprint?

Battery/Power management to me go hand in hand.

I think that should be a priority but as you said whatever is able to get working.

Re: Next for Android on TP2
 

Thanks for that post [ACL].

Hopefully people will start to understand that you guys are aware of the issues... I think there is some confusion that the devs don't know what's not working, when in reality 99.9999% you guys are fully aware of, you just don't know how to fix 'em. Keep up the good work, and ignore the haters.

Re: Next for Android on TP2
 

The one item that I consider most important isn't listed in the poll here - the headphone jack. When I get into the car, the first thing I do is to plug the phone audio into the aux input on my car radio - for both music and calls. Obviously, I can't do that with Android at present. Am I in the minority in finding that to be a show stopper?

Though this is my first week trying Android on my TP2, I've been following this project with great interest from the start. I'm very impressed with the work being done here.

Re: Next for Android on TP2
 

I've heard a couple of fixes that I'm going to test today. The first is a modification to the startup.txt, and the second involves plugging into the headphone jack while in WinMo, call voicemail, then boot Android while the call is running.

I'll let you know how they both work. I've heard the startup.txt method does not work, but it'd be nice if it did :D

Re: Next for Android on TP2
 

Yes, I've heard about both of those. I put "snd.force_headset=2" into my startup file, but it didn't make the headset work (though it DID prevent the speaker from working :) ). As for activating the headset in WinMo, that might work, but it's hardly a fix. And once you boot into Android in that mode, then the headset is the ONLY thing that will work. So it's not much of a workaround.

Anyway, good luck. Let me know if you come up with anything.

Re: Next for Android on TP2
 

So yes, it does break the speakerphone... and basically you have to do both. Put that snd.force statement in your startup, and boot Android with a call to VM going & a set of headphones plugged into the 3.5mm jack. I now get audio thru the headphones... and only thru the headphones.

I guess I should've seen what happened on a call, if any sound would play thru either speaker... Haha testing that now.

I'll admit, not the best solution, but a workaround is a workaround... it does come with the risk of breaking other functionality :p

Bah, it completely borks sound for anything but the 3.5mm headphone jack... I even get that odd staticy feedback from the speaker when stuff is playing thru the headphones...

Re: Next for Android on TP2
 

:-( Thanks for trying that out. I know that we might not be high on the dev's priority list, because Sprint's the only one that has the headphone jack.

Re: Next for Android on TP2
 

Why do you Sprint types always forget us Verizon users? C'mon -- we're CDMA cousins!

Re: Next for Android on TP2
 

Power management would definitely be the highest priority for me. I'm fortunate in that I can keep my phone docked most of the day so I run Android probably 75% of the time now. However, there's no way I could use it all day if I wasn't constantly plugged in. (and I'm assuming keyboard backlighting would also be a function of this?)

After that I'd probably say camera for the vast majority of folks. It's not something most people use a lot but it's really notable when you need it and it's not there. Sounds like you're getting fairly close here though.

For us CDMA users a more thorough solution to the headphone jack would be particularly nice. However, for those of us on Sprint with the TP2 I'd imagine a pretty sizable percentage are on SERO and now licking their chops waiting for 10/1 to roll around. I'm trying to decide if I'm going to jump immediately or maybe wait it out with my TP2 for a little while longer to see what the holiday season brings. Either way, I'm holding on to my TP2 though so I'll definitely continue to follow its Android development.

Re: Next for Android on TP2
 

Why? What's happening at Sprint/SERO for October 1st? I guess I'm out of the loop.

Re: Next for Android on TP2
 

On 10/1 SERO users will finally be eligible to upgrade to Android/WebOS/etc devices. They're going to call it SERO Premium and you will have to pay a bit extra per month depending on the type of device you buy. $10 extra per month for entry/mid-level non-4G devices like Pre, Hero, etc. Another $10 extra per month on top of that if you get one of the high-end 4G devices (Epic/Evo.)

You don't HAVE to upgrade obviously. But they're finally offering a decent middleground upgrade path for those of on SERO who would otherwise cling to our cheap plans for dear life rather than nearly triple our monthly bill.

Re: Next for Android on TP2
 

Tried spamming interrupts to get it to go?

Re: Next for Android on TP2
 

8 days. Not that I'm counting. Oh wait, yes I am. "DaysUntil Widget" in the market.

I would totally wait I had sero. After all this time whats another month or 2 to see what is coming out? Maybe someone will port 7 to you guys.

Sent from my fast as hell phone that you can only wish you had