android on diam500!!!

[mswlogo]

Why is the Vogue so far ahead on android than the diamond.

Since the screen and buttons have been figured out isn't the differences just a few config parameters that have been mostly already figured out. What's holding things back?

Why can't we drop the Hero build on our phone like Vogue was able to do?

Be fun to play with, but the present build for diamond is in no way useable on a daily basis.

[MrObvious]

I'm not sure why but I guess enough people aren't working on it.

[ydoucare]

At the rate this is progressing, I'll probably have a native Android phone by the time it's usable.

[basilray]

Anyone's on screen keyboards just whacky? You almost have to click the button to the right of one to get the key you want?

[toastcfh]

Originally Posted by ydoucare

At the rate this is progressing, I'll probably have a native Android phone by the time it's usable.

I won the war against Sprint and there refurbished shot phones. I went though 4 diamonds and all 4 the vibrate failed. Finally talked to a manager at the Sprint store. I explained my issue and he gave me a choice. A brand new diamond or a hero. If chose the diamond I would have to drive back to the store in a day or so to pick up the phone.the store is 30 + miles from my house. Or I got the hero I would het it right then. So I went and played with the hero and got it. But... I do miss my diamond. The hero is better IMHO. But after all the tweaking and nodding I did on my diamond. I really loved that phone. But yeah... the problem with the Android diamond port is the lack of cdma development. I felt hopeless tryin to contribute. Almost no one had a clue or interest in helping any of the cdma users. Phh was really the only dev that would even really try to help me figure out what my kernel was missing. I can tell u if it tryin to use WiFi or any of the new features. ur gonna need a newer kernel then the one mrpippy posted. I've tried almost everything to get WiFi working with that kernel with no event. I had started going through the commits and checking the changes against the September 3rd commit that works. Maybe someone can go from there. Good luck guys

[agentmikeyd]

Originally Posted by toastcfh

I won the war against Sprint and there refurbished shot phones. I went though 4 diamonds and all 4 the vibrate failed. Finally talked to a manager at the Sprint store. I explained my issue and he gave me a choice. A brand new diamond or a hero. If chose the diamond I would have to drive back to the store in a day or so to pick up the phone.the store is 30 + miles from my house. Or I got the hero I would het it right then. So I went and played with the hero and got it. But... I do miss my diamond. The hero is better IMHO. But after all the tweaking and nodding I did on my diamond. I really loved that phone. But yeah... the problem with the Android diamond port is the lack of cdma development. I felt hopeless tryin to contribute. Almost no one had a clue or interest in helping any of the cdma users. Phh was really the only dev that would even really try to help me figure out what my kernel was missing. I can tell u if it tryin to use WiFi or any of the new features. ur gonna need a newer kernel then the one mrpippy posted. I've tried almost everything to get WiFi working with that kernel with no event. I had started going through the commits and checking the changes against the September 3rd commit that works. Maybe someone can go from there. Good luck guys

is this dead now that toast has left us for Droid? hopefully some development is going on - anyone know?

thanks!

[toastcfh]

Originally Posted by agentmikeyd

is this dead now that toast has left us for Droid? hopefully some development is going on - anyone know?

thanks!

No I don't think is dead. Mrpippy, tenny, and a couple others are still working on it I believe. If u got any skills in tinkering with Linux based platforms. then I say head to the forum and to the irc channels and start asking questions. For sure don't just expect it to get ported to ur device. The foam500 users need all the help they can get. Good luck

[mclaser]

I believe that I followed the instruction from the 1st post correctly, except that I used the latest 20091103 instead of the recommended one 0909 (I think). I can't get it to come up. I get a the Penguin logo and a bunch of small text, then it seems to get stuck in an endless loop filling the screen with "[xxx.xxx] msm_i2c msm_i2c.o: Warning bus was busy (x)". Has anyone tried this with the 1103 build?

Update 11/13:
Hey, got it working! I needed a different zImage which I found on Connect-UTB (search for diam500). It runs pretty slow and the screen cal seems to be way off, but it's kind of a cool experiment! Text msg works, but no data it appears. I can make a call and hear, but the mic doesn't seem to work (as others reported, I think). Cool stuff!

[CranberrySauce]

Originally Posted by mclaser

... screen cal seems to be way off ...

I think that can be fixed via startup.txt

[toenail]

incase you havent been keeping up a lot of progress has been going on.. check ur common sites