Originally Posted by dzo

Hi,

I've put a new zImage and initrd-android on the site, there's no big changes here but the sms app works a bit better. I made the notification icon 1 pixel wide so you can have about 6 active notifications before the runtime crashes. Networking should be a bit smoother, I found a problem with the interrupt code that meant the data channel wasn't always being notified by the modem. I have almost got the SD driver working, it goes for a while and then crashes, I'll enable it when it's usable. I've also updated the kernel to the latest android-msm-2.6.25.

Enjoy

I look forward to trying the new release. I hope the weird touch screen problems I was having are resolved. Again thanks for all your hard work!

Does the SD driver mean that we can format our cards and load the filesystem onto it, or do we still need to use initrd images? If we can load the filesystem off the card, could you share what parameters need to be passed to the kernel to load it?

--Ryan

Works great on my sprint touch, thx dzo.

I am still having trouble with my touch-screen.

DZO - last time I mentioned it you said:
"It does this if it misses a ts interrupt, this shouldn't happen but I'll put some code in the ts event loop to check for missed interrupts."

Any update on this?

Thanks!

I updated the cab file to include the new changes. I also have added a Windows installer so you dont have to copy the cab file to the device.

I'll also keep the date updated on the article of when I last updated the files.

Again, the files are located at:
http://www.myhtcphone.com/downloads/...omatic-install

Hi, I did add some code but looks like that's not the problem, perhaps the pressure values from the touchscreen also need calibrating.
Can you download:
http://cs-alb-pc3.massey.ac.nz/vogue/initrd.gz
copy it to your phone and change default.txt by putting a # at the start of the line that says "set initrd initrd-android"

Boot as normal and you should get a text console.
Now do the touchscreen calibration by pressing the camera button and then touching the screen. You will see some messages scrolling up the screen. If its the pressure that is not calibrated you won't need to touch the screen.
Let me know what the last number in the messages is, it should say "TouchScreen Calibration: MIN=(..,..) MAX=(..,..) P=.."
I need to know the P value.

Thanks.

Originally Posted by uiucryan

I am still having trouble with my touch-screen.

DZO - last time I mentioned it you said:
"It does this if it misses a ts interrupt, this shouldn't happen but I'll put some code in the ts event loop to check for missed interrupts."

Any update on this?

Thanks!

Originally Posted by dzo

Boot as normal and you should get a text console.
Now do the touchscreen calibration by pressing the camera button and then touching the screen. You will see some messages scrolling up the screen. If its the pressure that is not calibrated you won't need to touch the screen.
Let me know what the last number in the messages is, it should say "TouchScreen Calibration: MIN=(..,..) MAX=(..,..) P=.."
I need to know the P value.

Thanks.

The P value did not remain constant. I saw numbers as low as high as 408 and as low as 29. Please note I did have to touch the screen to make this happen.
Please shoot me a PM or send me an email if you would like to take this offline.

Thanks,
Ryan

I really want to try this out... But i am unsure of me

I see in the first post what is working... But now, what isnt working with android? Stil some major bug really annoying?

Originally Posted by Balkar

I really want to try this out... But i am unsure of me

I see in the first post what is working... But now, what isnt working with android? Stil some major bug really annoying?

Balkar-
You should really give it a try.
It does not harm or modify anything on your phone and appears to work for most people (I currently have a touch screen problem).
I list some of the limitations of the port here -> http://www.androidgeeks.net/wiki/HTCVoguePort.
But many important features do work, like data, sms, phone calls, etc...
It is a great demo.

Originally Posted by uiucryan

Balkar-
You should really give it a try.
It does not harm or modify anything on your phone and appears to work for most people (I currently have a touch screen problem).
I list some of the limitations of the port here -> http://www.androidgeeks.net/wiki/HTCVoguePort.
But many important features do work, like data, sms, phone calls, etc...
It is a great demo.

Thanks for the response! I totally forgot that you did not need to hard reset your device when installing android! I'll give it a try tonight, i heard a lot of good from this developing explotation system.

Thanks for the hardworking, it's amazing!

I installed on my Bell Touch. It's working perfectly for Browsing (in fact it's the best browser on mobile device I have ever used!). I do noticed when using the phone fuction, the voice quality is not as good as it under WM. We may to work on some tweaks to improve it.