yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] polyrhythmic:
Well, I've been out of the game for a while, and this is why: my Kaiser won't boot Linux anymore. One day it just decided it wasn't going to boot at all, then gave me the tri-color screen, and refused to flash almost anything so I was forced to go all the way back to OEM Carrier ROM.....Haven't had the time to debug it until now.

So I finally flashed back the updates and tried booting Linux again but it won't boot from .NBH or HaRET, it hangs always at the nearly the same point: after detecting the SD partitions. When using .NBH it hangs at "Press Dpad to enter Install...", when using HaRET it hangs in fscking my FAT partition at step 2: "Checking Clusters..."

So, any guesses? It runs Carrier WM ROM and WM6.1 Solace ROM as if nothing is wrong. I'm looking already for a newer Android device but it would be nice to put out one last ROM. Following is the dmesg dump from HaRET after reboot:

...
[ 2.130000] SD Init
[ 2.158455] mmc_sd_init_card: Delay 250 ms
[ 2.419281] clk_set_rate 21:25000000
[ 2.422053] set sd clock - 0 1
[ 2.527081] mmc1: host does not support reading read-only switch. assuming write-enable.
[ 2.530206] SD Init Retry
[ 2.533266] mmc1: new SD card at address b7a6
[ 2.541075] mmcblk0: mmc1:b7a6 SU02G 1985024KiB
[ 2.546428] mmcblk0: p1 p2
[ 133.150075] INFO: task rpcrouter:15 blocked for more than 120 seconds.
[ 133.155798] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 133.160083] rpcrouter D c024ec20 0 15 2
[ 133.165673] [<c024e884>] (schedule+0x0/0x414) from [<c003ddb8>] (rpc_smd_read+0x11c/0x138)
[ 133.175683] [<c003dc9c>] (rpc_smd_read+0x0/0x138) from [<c003e518>] (do_read_data+0x24/0x27c)
[ 133.185907] [<c003e4f4>] (do_read_data+0x0/0x27c) from [<c006b784>] (run_workqueue+0xd0/0x174)
[ 133.195915] [<c006b6b4>] (run_workqueue+0x0/0x174) from [<c006bbec>] (worker_thread+0x104/0x118)
[ 133.200058] [<c006bae8>] (worker_thread+0x0/0x118) from [<c006f868>] (kthread+0x58/0x94)
[ 133.210042] r7:00000000 r6:c67d38c0 r5:c006bae8 r4:c67d8000
[ 133.220055] [<c006f810>] (kthread+0x0/0x94) from [<c005d424>] (do_exit+0x0/0x668)
[ 133.229033] r7:00000000 r6:00000000 r5:00000000 r4:00000000
[ 133.232995] INFO: task kadspd:16 blocked for more than 120 seconds.
[ 133.240033] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 133.250030] kadspd D c024ec20 0 16 2
[ 133.255927] [<c024e884>] (schedule+0x0/0x414) from [<c003e294>] (msm_rpc_read_command+0x100/0x1e4)
[ 133.260035] [<c003e194>] (msm_rpc_read_command+0x0/0x1e4) from [<c0047e58>] (adsp_rpc_thread+0x24/0x290)
[ 133.270033] [<c0047e34>] (adsp_rpc_thread+0x0/0x290) from [<c006f868>] (kthread+0x58/0x94)
[ 133.280033] [<c006f810>] (kthread+0x0/0x94) from [<c005d424>] (do_exit+0x0/0x668)
[ 133.290038] r7:00000000 r6:00000000 r5:00000000 r4:00000000
...
[Touch CDMA Android Development] Dukenukemx:
Holy ****, it's polyrhythmic!

Oh, and try kallt_kaffe's kernel and see if you get the same results. That's what I'm using and have no problems.
[Touch CDMA Android Development] loserskater:
Have you tried starting from scratch using a freshly formatted fat32 SD with only the andboot folder? or maybe using a different sd card?
[Touch CDMA Android Development] kallt_kaffe:
Sorry for the delay... I've been asleep (GMT+1), changes have been pushed now.
[Touch CDMA Android Development] kallt_kaffe:
Bad SD card or something wrong the with the SD-card slot? If you boot without an SD-card will it show the "waiting for SD-card" message where you normally get the "Press Dpad" message?
[Touch CDMA Android Development] manu33xtro:
More perfect...

Hi Poly, nice to see you :)

And hi DZO.

I installed the last version of your kernel (28-05-10) with the Loserskater tool (for modify panel type).

I have to say : it's beautiful now because everything (not all of course but more and more) working véry good for Polaris, in association with the last build of Aqtrans :) See my thread http://xdaforums.com/showthread.php?t=690338

Thanks again.

Cheers.
[Touch CDMA Android Development] kallt_kaffe:
dzo, I noticed that you added some parameters to try out AGPS and I thought I should add some more explanation to the comments I left in the Kaiser code. I found those things out by changing parameters in the windows registry and then dumping the smem buffer like you instructed me to do.

This is how the Kaiser do it in WinMo but it's likely similar on the Vogue.

msg.msg[5]: This is called GPSMode in the registry. Regardsless what the registry says 0x1 is used unless AGPS is turned on. When AGPS mode is turned on GPSMode=1 becomes 0x3 in the RPC call. GPSMode=2 becomes 0x2 and GPSMode=4 becomes 0x8.

However after the first RPC call it falls back to 0x1 and I believe that happens when AGPS fails, like a fallback routine to default value (standalone mode). I haven't tried with the Google AGPS IP and port in WinMo. Perhaps the results would be different.

Also the AGPS, AGPS IP and AGPS port goes back to default values on the second RPC command (in WinMo). One difference between WinMo 6.0 and 6.1 is that QoSPerformance becomes 0x2 in "fallback" mode in 6.1 while it keeps it's registry value, 0x59, in 6.0. However I haven't seen any effect on changing the value so I think it is only used for AGPS. (This behaviour may be why you have 0x2 in GPS_enable(), and 0x1 in GPS_tickle() on the Vogue. On the Kaiser I removed the redundant code in GPS_Enable() and calls GPS_Tickle instead. I wouldn't be surprised if that also would work just fine on the Vogue).

As for msg[10]. I might have been imaging it but I had really quick fix times when I had it changed. I was driving my car and removed the battery from my Kaiser for 2 minutes, then booted up and started "GPS Test" and the fix was either instant or within 3 seconds. But when I was using the setting while walking the dog once I was like 30-40 meters off so I'm not sure what 's the deal with it. And my fix times are often very quick even with using the default value so it might just have been a coincidence.

And another thing that may be doable. The QuickGPS application in WinMo. I'm pretty sure it downloads xtra.bin from one of these:

XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin

XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin

XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin

If we just figure out how to send it to the GPS (propably with some AT command) it would be possible to write a Android QuickGPS application and prime the GPS for quicker fix times)
[Touch CDMA Android Development] myn:
Just wanted to report in. Tried 05-29-2010 zImage with Warm Eclair. Still not able to adb into it. Device Not Found.

05-24-2010 zImage has no adb issues for me.
[Touch CDMA Android Development] mnjm9b:
have you tried flashing with pc/usb instead of sdcard?
[Touch CDMA Android Development] polyrhythmic:
Thanks for the suggestions, everyone!! I sometimes can flash from SD but it doesn't always work, in which case I flash from USB. Regardless of how I flash -- yes I did try kalt_kaffe's files -- I haven't been able to boot Linux yet. It's definitely my SD reader, popping in and out my SD card for testing in WM today has caused a) soft resets b) system freezes c) the screen sometimes refuses to stay shutoff (as if the SD card insert/remove detection is constantly being triggered and d) now it will only read the card occasionally.

So it looks like no Android for me on this Kaiser. Well, I sure have gotten my money's worth. I had a great time while it lasted! Many thanks to all involved.
[Touch CDMA Android Development] manu33xtro:
Thanks...

Really it is a pleasure. I hope you will can repair or change your phone.

Good luck.

Cheers.
[Touch CDMA Android Development] Dukenukemx:
Have you tried a different SD card yet? Also, could it be that your sd card slot needs cleaning? Worse case scenario, the solder joints for the SD card slot are lose and need to be re-soldered.

I'd recommend using TV-Tuner/Control Cleaner & Lubricant on your SD card slot first. This stuff works miracles on any electrical contact.
[Touch CDMA Android Development] thebulletfromhell:
Everybody is having phone problem this month. Incubus broke is vogue 2.(But we got him a new one.)
[Touch CDMA Android Development] Dukenukemx:
Polyrhythmic's work is amazing, and I'm sure if you told people about your problem with your Kaiser that people would have helped. Hell, someone gave Incubus a Kaiser. :eek:

Question is, does polyrhythmic want another Kaiser?
[Touch CDMA Android Development] thebulletfromhell:
True. But who doesn't want a kaiser. I already got a couple of school mate offering to swap it for hero and dream.
[Touch CDMA Android Development] Shidell:
I'm interested in learning more about how our Kernel is modified and flashed to our phones. Can anyone post some quick instructions/details on obtaining the modified source, compiling it and turning it into a flashable NBH?
[Touch CDMA Android Development] Dukenukemx:
Nowadays it's all about the Nexus One and HD2. Oddly, both don't have keyboards, which would drive me crazy.
[Touch CDMA Android Development] thebulletfromhell:
Yeah. I want to get the mytouch slide but its tmobile only. Oh well, there's still the vision.
[Touch CDMA Android Development] thebulletfromhell:
Look up building the kaiser kernel. Its in the wiki
[Touch CDMA Android Development] manu33xtro:
Problem with battery incator

Hi DZO,

I wrote that the battery indicator tell to me the good value (I'm sure it was correct) because when I flash for the first time the kernel (28-05) and in the same time I installed the version 1.2 of Aqtrans.

But I have charge the phone last night (I keep it all the night) and now I have all the time 100% !!! I don't know why.

Would you like a last_kmsg ?

I try to charge again and it's yet the same effect : 100%...

Thanks if you have an idea.

Cheers.
[Touch CDMA Android Development] Shidell:
Thank you. :)
[Touch CDMA Android Development] loserskater:
This usually works for me:

If you run the battery down until it's almost dead, you should get a warning saying that the battery is below a certain level. Then plug it in and let it charge all the way up. When you unplug and start using it, you should see that the battery is displaying the correct level.
[Touch CDMA Android Development] manu33xtro:
Maybe a mistake...

Yes I do it because I've got the alarm "4%", I plug and now... I do it last night and after unplug I get 100% all the time when I use it today ?!?

I test it now, I unplug with 34%, waiting a few minutes and plug it again : it's ok now I've 34% : I remember I've unpluged last day when the charge is 100%, maybe I've keep my phone in charge too long !!

tomorrow I talk to you if it's ok...

We are tomorrow

:) It works perfectly because I unplug and a few minutes after the first call, I can see 99%... I don't know what's happend the first time.

Thanks to reply and good job your tool for NBH.

Cheers.

:)
[Touch CDMA Android Development] xport:
Camera

I got a chance to really run the camera through its paces this weekend, and I have to say dzo, THANK YOU, its really much improved.

If I had to add one last thing to my "wish list" it would be AVRCP for BT Audio. Thanks so much for all your hard work. :-)
[Touch CDMA Android Development] Dukenukemx:
BT audio works for me, but it's erratic at times. For example, pickup up my phone with it will not always go to my stereo BT head set. Yesterday, I had trouble disabling BT whiled connected, as it would reset Android back to the startup animation.
[Touch CDMA Android Development] xport:
Same here, just tap it down one or two notches, that seems to be just fine for me.
[Touch CDMA Android Development] myn:
Hey dzo,

I noticed that in Eclair builds the standby and sleep modes are a little different then in Donut.

Every morning on the way to work I connect my Vogue to a usb to stereo adapter which plugs into my car. I proceed to play some podcasts and listen to streaming radio using "a online player".

In Warm Donut the screen goes black after a few mins and music continues to play until I shut it off.

In Warm Eclair the screen doesn't go black unless I hit the end key and force it. And after I do force it, after about 20 or so mins the audio stops until I wake up the device. It's almost like it's shutting down things after a specific period. It does however go black if the USB to stereo adapter isn't plugged in but I am not sure about the music stopping after 20mins as I never have tested this.

Is the sleep code different for eclair? Does the presence of a usb effect this?

I'd love to see it working like it was in Donut.

Thanks

PS. If this doesn't make sense let me know.
[Touch CDMA Android Development] Dukenukemx:
Does the Vogue also have a extusb port? Cause I have Myn's Warm Donut and I can't get any audio out of mine using the extusb port, with my adapter. Could be just a Kaiser thing. Good thing there's bluetooth audio to connect my phone to my car. :D
[Touch CDMA Android Development] thebulletfromhell:
Stop the music, turn off the screen, plug the headphone in, turn on the screen and play the music. ALways work
[Touch CDMA Android Development] myn:
This workaround certainly works. I just am kinda sick of the workaround, you know?
[Touch CDMA Android Development] Dukenukemx:
Lol, next thing you know we'll need to do an Indian dance around our kaiser to send a text message.
[Touch CDMA Android Development] tatnai:
lol. will indian dance around my unboxed evo when I get it just for fun... one last indian dance for kicks. . .
[Touch CDMA Android Development] fldash:
myn, I had this issue on Donut and it was caused by JuiceDefender. When the data connection is closed, all audio is disabled. Not sure why. I ended up disabling JuiceDefender when I wanted to listen to music/podcasts.
[Touch CDMA Android Development] Dukenukemx:
The BT audio using Myn's is extremely buggy. Don't know if it's the kernel or Myn's Donut. Sometimes audio will play through the BT Stereo, and sometimes it doesn't. Sometimes it'll just play through the internal speaker. Once it would crash Android when activating BT, cause the next thing I would see is the animated startup screen.

Anyone know what's the cause of this buggy BT audio?
[Touch CDMA Android Development] kallt_kaffe:
dzo, I think one of your latest changes causes sleep/wakeup freezes. At least it seems to that on my Kaiser.

I added msm-sdcc.vreg_off_on_suspend=0 to my startup.txt and it seems to have fixed the problem.
[Touch CDMA Android Development] wdbanks:
I was getting major sleep/wake up freezes with Myn's Warm Eclair on Nand with the latest eclair nbh from DZO. I flashed back to the Warm Donut and vogue nbh and I dont have that issue anymore.
[Touch CDMA Android Development] margosmark:
Yep my vogue with Myn's Eclair and the 240x320 eclair kernel from the 29th did not sleep properly either.
[Touch CDMA Android Development] kallt_kaffe:
Latest code also causes freeze when turning on bluetooth (once again, Kaiser with Myns Warm Eclair).

last_kmsg says this:

Bluetooth 1

High Speed

clk_set_rate 34:1843200

clk_set_rate 34:1843200

clk_set_rate 34:1843200

clk_set_rate 34:1843200
[Touch CDMA Android Development] dzo:
I see the problem, I had forgotten to update the defconfig. It needs unsafe resume enabled or it doesn't power up the card. I don't know about BT, that may still be broken. The wifi driver might also need to be recompiled.
[Touch CDMA Android Development] yoblin:
I'm also getting it from NAND
[Touch CDMA Android Development] kallt_kaffe:
Yes, resume works again. BT still broken. Wifi seems to be working.

EDIT: last_kmsg after a BT freeze looks exactly like last time (se above)
[Touch CDMA Android Development] Dukenukemx:
Had a problem today where talking on the phone cut out any audio. Both me and the other person couldn't hear each other. This is the second time this happened, and both were long over an hour conversations. Had to restart to fix it.
[Touch CDMA Android Development] wdbanks:
Another Vogue Bites The Dust..

Hey DZO,

I wanna thank you for all your hard work and contribution to this community of vogue lovers. Mine died the other day and I found a Samsung Moment real cheap on craigslist so I wont be using your great work anymore. I guess another vogue bites the dust (ala Queen...lol)

Just wanted to say thanks. Anyone need a vogue let me pm me. I got my hands on one through ebay before I found my Moment.

Best wishes!
[Touch CDMA Android Development] Betho180:
thanks a lot
[Touch CDMA Android Development] dzo:
I've rewritten the touchscreen driver and now vogue, kaiser and polaris all share the same driver, the old driver was horrible! I also made some panel changes to vogue and polaris which save lots of power during suspend on my pola200. Audio input is still broken on kaiser and polaris. New NBHs for all devices are on my site.
[Touch CDMA Android Development] JM-PDA:
Dzo,

Downloading now.

Thank you very much ! ! !
[Touch CDMA Android Development] myn:
Hey dzo,

I just gave zImage-16-06-10 a try.

It seems as though the touch input isn't as sensitive and responsive as it was previously for me on the vogue using Warm Eclair.

It seemed as though upon rebooting into Android the first minute of use the touch input was not responding. I let it sit and it got better but it still seems a little off. I find myself tapping on things I didn't mean to touch and double tapping things that didn't activate. For example the notification bar seems harder to pull down now. I used to be able to flick it down really fast. I find myself having to click on the home screen launcher and keys on the keyboard multiple times to activate them.

I'd love to hear other peoples experiences with the new touchscreen driver.
[Touch CDMA Android Development] uiucryan:
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
[Touch CDMA Android Development] wmvdg123:
Works great on my sprint touch, thx dzo.
[Touch CDMA Android Development] 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!
[Touch CDMA Android Development] etiger13:
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/14-files/3-cab-file-for-automatic-install
[Touch CDMA Android Development] dzo:
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.
[Touch CDMA Android Development] uiucryan:
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
[Touch CDMA Android Development] 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?
[Touch CDMA Android Development] 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.
[Touch CDMA Android Development] Balkar:
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.
[Touch CDMA Android Development] yirong:
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.
[Touch CDMA Android Development] etiger13:
go ahead and try it out

its even easier to give it a test go now that there is a simple installer/uninstaller. Since it installs through a cab file, it shows up in the Remove Programs menu. It also has a nice shortcut in the Programs folder too. It wont harm/change your phone so there really is no reason not to play around with it.

Get the CAB or Windows installer from here: http://www.myhtcphone.com/downloads/14-files/3-cab-file-for-automatic-install
[Touch CDMA Android Development] etiger13:
new link that is even easier to remember to get to the installer: http://www.myhtcphone.com/installer

Easy right?

If anybody has any videos or screenshots of Android running, please send me a message letting me know so I can get them posted up.
[Touch CDMA Android Development] itsallsubliminal:
this is great, now we have a cab!

thanks balkar!

is there any progress on an easier way to port the our contacts over??
[Touch CDMA Android Development] qwho:
Give it a try... you'll see how this isn't reliable enough to use for more than a quick test. I think it is much more of a priority to get the software up and running at level that doesn't crash every time you get a couple texts, or when you happen to get a phone call and you are in any app...

I'm sure someone will figure out a way to dl them off an exchange server at some point, if that feature isn't supported natively eventually.
[Touch CDMA Android Development] itsallsubliminal:
its just sad how we can't get wm6.1 to have the page transitions and smoothness that this android emu has... you can't go off and say wm is not capable of it cuz its proven with this android app...

how hard could it be to get wm6.1 to behave more like this android app?
[Touch CDMA Android Development] RMJ250:
Anyone know if this would work on an o2 Orbit? (Artemis OMAP850 cpu), excited to see people have got it working on real phones! Wondered if I could join in on the fun :)
[Touch CDMA Android Development] etiger13:
Its not reliable enough yet because Android itself isnt reliable enough yet. it is still being developed. Google hasn't officially released it yet which means it is still in BETA stages, if it is even that far. Once it is officially released, it will probably be more stable than WM. And since it is open source, there will probably be a lot more available for it and it will be completely customizable, in ways WM could never be.

Point is, this is an early look at Android that someone was kind enough to port for us. Thank you very much Martin.