yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] SuperJMN:
100% agree. I'm sticking with the older kernel because the new one produces FS corruption every now and then. The problem with us is that our models are superior in terms of hardware comparing to Vogue, and we've got all the extra features either not working or working only partially. For example, the camera doesn't have auto-focus, and indoors it takes awful pictures. Our FM radio is totally dead under Android. The front camera, not usable at all. The headset is not detected dynamically when plugging it in or out...

It's a pitty that we reached this stage, but now we're quickly falling down. I though about selling my Polaris for the first time in months.
[Touch CDMA Android Development] cnigro1279:
Thanks DZO

I'd just like to reiterate the sentiments of the last couple of posters...I've only had my Kaiser for about a year and the main reason I wanted this device was that it was heavily supported here at XDA. I had intended on trying different WinMo Rom's at first but was floored when I saw the development of Android and how far it had come. XDA is my Mobile Device Encyclopedia with such great authors as you DZO, and Kalt, Incubus, Myn, Zenity, and everyone who puts in the time and effort. I can only hope that someone else continues the development for our Kaisers or I'm sure that Ebay will be flooded with em.

Thanks again to all of you...
[Touch CDMA Android Development] n2rjt:
Thank you dzo for all you have done. Android works amazingly well on these phones designed for Windows Mobile 6.

Regarding Kaiser support, hopefully kallt_kaffe can help, and thanks to l1q1d as well. Also, I only arrived on the scene recently but can probably help if dzo and others can point me in the right direction from time to time. So, I don't think Kaiser support is stopped just yet.

:)
[Touch CDMA Android Development] tiagoclc:
Nand

Nand is not fixed... :(

Still getting yaffs error and losing my contacts.
[Touch CDMA Android Development] thoughtlesskyle:
why dont you switch to the kernel that l1q1d has been working on its based on the old kernel so it doesnt have the nand driver issue
[Touch CDMA Android Development] flinx42:
Can do, although I seem to recall having (other) issues with that kernel as well. Certainly sporadic hangers.

Where is that kernel published, if not at the same place as dzo's?

Is there a seperate thread for that already?
[Touch CDMA Android Development] thoughtlesskyle:
the thread for it is here

http://xdaforums.com/showthread.php?t=782501

i know there are random hangups but i would rather those than data loss also i would try using milanche's CM6 build, i havent heard as much about hang issues with that
[Touch CDMA Android Development] flinx42:
Thanks I've bookmarked that thread.

While I agree that data loss is worse than a simple hanger, the latter is still bad as you don't notice WHEN it happens and as from that moment on your phone is not receiving calls/other anymore nor doing the calendar reminder.

As I do seem to remember a few issues with the old kernel apart from hangers (Location/GPS at least), I'll probably keep an eye on the thread and only try it over the weekend when I don't need the phone as badly.

Incidentally I had a few missed calls yesterday morning, due to the phone not ringing anymore. Maybe related to the non-perfect headset plugging/unplugging, but hadn't got the time to test. Switching to vibrate and back didn't help, so have gone back to WM for the mo out of desperation.
[Touch CDMA Android Development] l1q1d:
I did another attempt to solve the problem of nand.

Has been tested for now, with success on the kaiser. Please test it on other devices
[Touch CDMA Android Development] l1q1d:
I'm trying to fix nand, i need to know if you have a fs problem (these warning are less important now)

I didn't find the cause yet, maybe dzo could take a look...
[Touch CDMA Android Development] samjam:
Sure. I regularly get the fs problem so I'll be able to tell you in a couple of days for sure. I find that I am more likely to get the problem the more often I restart the phone, so I'll do my best to generate it for you.
[Touch CDMA Android Development] SuperJMN:
I'll try it in my Polaris. Is this the .NBH I have to flash? http://it029000.massey.ac.nz/vogue/files/voguimg-240x320-2.6.32-froyo-28-09-10_22-testing.nbh
[Touch CDMA Android Development] l1q1d:
No my version.... (look in this post)
[Touch CDMA Android Development] artex92:
On this kernel Volume Up buton doesn't work on Kaiser. No wakeup problems. NAND isn't crashing at the moment, so probably it's fixed ;)
[Touch CDMA Android Development] l1q1d:
i change the binding on the top wheel.
[Touch CDMA Android Development] artex92:
I see it, but Vol Down is still working :)
[Touch CDMA Android Development] n2rjt:
With one of the recent changes, my Tilt's keyboard light turns on whenever the screen turns off and the keyboard is closed. However, when the keyboard is opened, the light stays off. . The only way I can charge the phone without lots of heat is to keep the keyboard open. This is a recent development. Any ideas?

EDIT: Found it, in board_kaiser_keypad.c.
[Touch CDMA Android Development] l1q1d:
I'm going to fix keyboard light for kaiser today.

Next release has a minor change for polaris's wheel.
[Touch CDMA Android Development] SuperJMN:
Does your wifi work? I've tried to enable it and the system hangs completly! I don't know if it's my fault. Just want to have a second opinion :)

EDIT: I installed the new build again and it's the same, wifi doesn't work. Reverting to the older build.
[Touch CDMA Android Development] l1q1d:
Works on kaiser and as i can see there is no problem in polaris's dmesg.
[Touch CDMA Android Development] n2rjt:
Using wifi now, just to test. I'm using current kernel except my battery code and a modification of the keypad code. I suggest try again.
[Touch CDMA Android Development] n2rjt:
When you reverted to an older build (of Fresh Froyo) did you also change the kernel, or not? Of course if you did not change the kernel, and wifi works, we need to look at Fresh Froyo for the problem, and that of course is not the subject of this thread.
[Touch CDMA Android Development] alexinc:
i cross-checked on my orbit2: with .25-kernel wifi is working with l1qu1ds androidupdate (as of lateley)... using .32-kernel its not working same with camera (we already know) ;)
[Touch CDMA Android Development] l1q1d:
Did you use the correct set of modules?
[Touch CDMA Android Development] scottter:
Having a user error here, I've been running off of SD card for a while and I currently have super froyo rls 13.

I've been vaguely keeping an eye on this forum, and it seems like there have been alot of changes recently, so I wanted to update to rls16. The problem is, I can't find all the base files on the new sourceforge. http://androidhtc.git.sourceforge.net/git/gitweb-index.cgi

I have the rls16 itself, I have the new haret for 2.6.32, I have the new zimage from here and I have a default.txt from last time. I think all that I'm missing is a new initrd.gz. Unless my current one is compatible with the new kernal?
[Touch CDMA Android Development] thoughtlesskyle:
on dzo's site its intrid.lzma looks like the latest one is from the beginning of september i dont know if l1q1d has a newer one in his thread
[Touch CDMA Android Development] n2rjt:
IRQ lost

This morning, as I was checking the news headlines, my phone froze. I woke up, picked up the phone, and saw that I had no messages. So, I went to the XDA Developers app, but it wouldn't load because I didn't have data 3G or 2G. Well, that was strange, so I enabled wifi. After the icon appeared, I went into the news and weather app, and it showed no new stories since three hours ago. Then I hit the "menu" button (the Windows logo button on my kaiser Tilt). Nothing happened, and the phone was frozen from that point.

Since the LEDs were still blinking, I knew it wasn't a crash, so I hooked up to the PC and probed. "adb logcat" shows that things looked normal but suddenly stopped. "adb shell dmesg" shows a similar halt of messages around the time of the freeze, with an IRQ error:

[43387.555572] irq 26: nobody cared (try booting with the "irqpoll" option)

[43387.555725] [<c002bb18>] (unwind_backtrace+0x0/0xd8) from [<c00895b0>] (__report_bad_irq+0x30/0x88)

[43387.555816] [<c00895b0>] (__report_bad_irq+0x30/0x88) from [<c0089750>] (note_interrupt+0x148/0x1d0)

[43387.555847] [<c0089750>] (note_interrupt+0x148/0x1d0) from [<c008a010>] (handle_edge_irq+0x16c/0x1c0)

[43387.555938] [<c008a010>] (handle_edge_irq+0x16c/0x1c0) from [<c0026068>] (asm_do_IRQ+0x68/0x84)

[43387.555999] [<c0026068>] (asm_do_IRQ+0x68/0x84) from [<c0026acc>] (__irq_svc+0x4c/0x90)

[43387.556030] Exception stack(0xc5c99dd0 to 0xc5c99e18)

[43387.556060] 9dc0: 00000000 01e84800 00000981 06c66530

[43387.556091] 9de0: c5c569a0 20000013 00000011 c5c56800 c5c5b684 00000000 c5c99e90 00000000

[43387.556121] 9e00: c5c99e2c c5c99e18 c01d5338 c01d5368 60000013 ffffffff

[43387.556213] [<c0026acc>] (__irq_svc+0x4c/0x90) from [<c01d5368>] (msmsdcc_request+0x24c/0x288)

[43387.556243] [<c01d5368>] (msmsdcc_request+0x24c/0x288) from [<c01cc6d8>] (mmc_wait_for_req+0x114/0x12c)

[43387.556304] [<c01cc6d8>] (mmc_wait_for_req+0x114/0x12c) from [<c01cc754>] (mmc_wait_for_cmd+0x64/0x74)

[43387.556365] [<c01cc754>] (mmc_wait_for_cmd+0x64/0x74) from [<c01d2ab0>] (mmc_blk_issue_rq+0x37c/0x5e8)

[43387.556396] [<c01d2ab0>] (mmc_blk_issue_rq+0x37c/0x5e8) from [<c01d3320>] (mmc_queue_thread+0x100/0x104)

[43387.556488] [<c01d3320>] (mmc_queue_thread+0x100/0x104) from [<c00681cc>] (kthread+0x78/0x80)

[43387.556518] [<c00681cc>] (kthread+0x78/0x80) from [<c00278dc>] (kernel_thread_exit+0x0/0x8)

[43387.556549] handlers:

[43387.556579] [<c01d53a4>] (msmsdcc_irq+0x0/0x330)

[43387.556640] Disabling IRQ #26

I sync and build regularly, so I've been getting the board-kaiser-keypad.c changes. I also note that someone else has reported his phone freezing with a recent kernel after he enabled wifi. Since the keypad code has been changing recently, I suspect it, but I haven't yet looked up IRQ #26. It could be wifi, or something unrelated. But it did freeze after I hit a key, and within a minute of when I enabled wifi.

I did notice yesterday in the dmesg logs some other IRQ warnings coming from the keypad code. I do not see those warnings this morning, even after the required reboot. Bizarre.

:confused:
[Touch CDMA Android Development] scottter:
I can't find a link for that file, do you have one?
[Touch CDMA Android Development] thoughtlesskyle:
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D its on there like the 20th line
[Touch CDMA Android Development] mt1976:
Kernel 2.6.32 with Nand fix on Kaiser

@l1q1d

I made a test with Kernel 2.6.32 with your Nand fix on Kaiser (Nand) and latest fresh froyo and all seems to work well and was very fast at the first moment. But the Kaiser lost 50% battery capacity in only 8 hours during standby without wifi enabled and with only 2G mode enabled without data. I never had such a high power consumption before in such a short time with older versions from Kernel 2.6.32. So I think in your last changes for the Nand fix is something wrong.

Now I switched back to Kernel 2.6.25 with the latest battery fix and the wifi update with the latest fresh froyo. The system is now slower but the power consumption is really much better and all works well and stable, but slower.

Is there a problem with the kernel 2.6.32 and the last changes on the kaiser because the power consumption is too high?
[Touch CDMA Android Development] l1q1d:
It wasn't the power consumption but the different battery system.

The battery life is the same but with the 2.6.25 probably the power drain isn't correct.

@scottter:

Use the latest initrd.lzma from here it works both for 2.6.32 and 2.6.25 (my version)
[Touch CDMA Android Development] samjam:
The keyboard LEDs don't turn off properly.

You must turn on the phone, slide open the keyboard, slide closed the keyboard and check the the LEDs have gone out, then turn the phone off.

The LED's *should* turn off whenever the LCD backlight goes off or whenever the keyboard is closed.
[Touch CDMA Android Development] samjam:
No NAND problems yet from me.
[Touch CDMA Android Development] SuperJMN:
What NBH is the most up-to-date? I flashed this one: http://androidhtc.git.sourceforge.n...=2.6.32/VOGUIMG-320-FROYO-10-4-10.NBH;hb=HEAD

But the touch-screen didn't process taps correctly and I had to come back to this .NBH: http://xdaforums.com/showpost.php?p=8385928&postcount=5730
[Touch CDMA Android Development] scooter1556:
Yaffs2 Update

I have been playing around with kernels recently, i tried updating to the latest yaffs2 code and compiling it into the kernel which worked fine and i was able to install the system without any errors apart from the usual couple of bad blocks but when android tries to boot it is unable find a /system or /data partition. I'm guessing some other files need to be modified in the 'mtd' part of the kernel but if anyone has any pointers that would be great :-)
[Touch CDMA Android Development] l1q1d:
my latest kernel has yaffs2 problem already solved, the problem was in mtd part.
[Touch CDMA Android Development] scooter1556:
Yes, I am using your latest kernel now and the nand errors seem to be fixed, i just realised that the yaffs version in our kernel is quite out of date and wondered what improvements the latest builds might have.
[Touch CDMA Android Development] samjam:
keyboard LEDs

They keyboard LED's come on when the dpad LEDs come one (even if the keyboard is ****), but they only go off when the keyboard transitions to the shut state. If the keyboard is already shut then the keyboard leds stay on, even when the dpad leds go off, even when the backlight goes off.

So these triggers should turn off keyboard leds:

dpad leds go off

lcd backlight goes off

keypad slides shut

this condition before the keyboard leds can go on:

keyboard is open
[Touch CDMA Android Development] VulpesFoxnik:
Has this latest been fixed on Kaiser on your build server, or will I have to git and build it myself?
[Touch CDMA Android Development] scooter1556:
It's fixed on the latest kernel from here : http://androidhtc.git.sourceforge.n...it;h=f0af7837ce8946716841ccbfdd03019dd4d9cb07
[Touch CDMA Android Development] 4ultratech:
Kernel Link

How is the above link different from dzo's?

Is it only for Kaiser or is it for Vogue also?

Thanks....
[Touch CDMA Android Development] dzo:
Well, I finally disconnected my Vogue from the CDMA network today so I could move my number to another carrier. Quite sad...

As a consolation for this I spent some time rewriting the USB driver to use the gadget framework, it seems to work OK and I've pushed the changes. This should allow a few things to work better, mass storage and usb networking perhaps. Also, psfreedom should be easy to port now. Only tested on Vogue, you'll have to build your own kernel to try it.
[Touch CDMA Android Development] scooter1556:
As always, any time you spend on our devices is very much appreciated, your a star. It's a sad day for the vogue, still, bet the new phone is pretty awesome! I'll move on once i've got every last bit of life out of my Kaiser!!
[Touch CDMA Android Development] thoughtlesskyle:
thank you for everything you have done martin

this is a sad but inevitable day
[Touch CDMA Android Development] mcongosto:
This kernel don't work on my kaiser, it keeps rebooting. Any idea why? thanks!
[Touch CDMA Android Development] ProgMaq:
Hello, i have got the same problem with my Polaris.

"yaffs tragedy: no more erased blocks", and I can't boot.

My setup:

- Device: Polaris 100

- Kernel: VOGUIMG-320-FROYO-10-4-10.NBH (Change to Polaris & Panel 1)

- Radio: 1.65.38.14

- Android: Thoughtlesskyle's Not So Super Froyo [RLS 16] [10/6/2010]

- Update: WIFI update.

- Flash: Yesterday (Only 1 day work)

Anyone can help me?

Sorry my bad level of english.
[Touch CDMA Android Development] mrkite38:
thank you, martin - rndis has been a coveted feature since the early days! it's nice that we'll be able to have some kind of connectivity after we all move on...

ironically, i also noticed that the vogue forum moved to the 'legacy devices' group today. :( sad, but true, i'm afraid.

i think we can say we've had a good run... the vogue will be remembered as a prolific smartphone!

i'm on to the droid 2 (cheap as ever! lol). see you guys around. :)
[Touch CDMA Android Development] SuperJMN:
4-Oct-2010 VOGUE .NBH:

The system got corrupted after rebooting. I think the NAND driver is still failing. I used my headset before and the system was installed a few minutes ago.

It happened to me 4 times since yesterday.
[Touch CDMA Android Development] scooter1556:
This kernel has the latest fixes from L1q1d for NAND etc... which were commited after dzo compiled the latest kernel on his site.

Also, because of the NAND changes it is likely that you will have to reinstall the system after this kernel update and wipe data. There are still some NAND issues but it is much more stable then before.
[Touch CDMA Android Development] derringdo:
My vogue finally experienced the dead kernel again after a few days of blissful use, and I managed to pull the last kmsg. Hope this helps.
[Touch CDMA Android Development] n2rjt:
USB not working on Kaiser

The USB change leaves me unable to connect my Kaiser to either Linux or Windows. I usually can use adb to transfer files, get logcat, or get a shell prompt. Now instead I get error: device not found.

I am using the latest sources, with the last commit having the comment "Tidy up usb driver and add a delay to the reset code." I compiled with these commands:

make vogue_defconfig ARCH=arm

make ARCH=arm

My PC's dmesg log is:

[ 1424.988139] usb 3-1: new full speed USB device using uhci_hcd and address 30

[ 1425.190334] usb 3-1: not running at top speed; connect to a high speed hub

[ 1425.190351] usb 3-1: no configurations

[ 1425.190362] usb 3-1: can't read configurations, error -22

[ 1425.300100] usb 3-1: new full speed USB device using uhci_hcd and address 31

[ 1425.438334] usb 3-1: not running at top speed; connect to a high speed hub

[ 1425.438349] usb 3-1: no configurations

[ 1425.438360] usb 3-1: can't read configurations, error -22

[ 1425.548100] usb 3-1: new full speed USB device using uhci_hcd and address 32

[ 1425.578337] usb 3-1: not running at top speed; connect to a high speed hub

[ 1425.578351] usb 3-1: no configurations

[ 1425.578363] usb 3-1: can't read configurations, error -22

[ 1425.688097] usb 3-1: new full speed USB device using uhci_hcd and address 33

[ 1425.718336] usb 3-1: not running at top speed; connect to a high speed hub

[ 1425.718352] usb 3-1: no configurations

[ 1425.718364] usb 3-1: can't read configurations, error -22

[ 1425.720352] hub 3-0:1.0: unable to enumerate USB device on port 1
[Touch CDMA Android Development] dzo:
The defconfig wasn't quite up to date, try enabling the rndis gadget or getting the commit I just pushed.
[Touch CDMA Android Development] n2rjt:
It works beautifully, thank you! :D
[Touch CDMA Android Development] samjam:
n2rjt, please could you post your NBH - thanks!
[Touch CDMA Android Development] mcongosto:
maybe i didn't explain myself, when I install the NHB successfully the phone reboots just after the splash screen, i cannot get to the point of installing the system.

Maybe I am doing something wrong? whit other NHB it works fine, but just the first couple of days, once it starts crashing and rebooting it gets corrupted.

thank you!
[Touch CDMA Android Development] scooter1556:
New Kernel 8-10-10

Here's the latest kernel with the latest usb fixes by dzo, for vogue make sure you edit it in ATools. I've done some code clean-up too so hopefully nothing is broken but if it is i'm sure a new kernel will be posted officially soon.
[Touch CDMA Android Development] SuperJMN:
I've tested it with my Pola100 and the USB connection is as crazy as always. The mass storage doesn't pop up when I activate it using the Notification (the little droid with a USB arm).

What should I do to make it work?

Edit: when I plug it to the USB, my Windows 7 Ultimate x64 states "This device can perform faster if connected to a USB 2.0 port" or something like that.
[Touch CDMA Android Development] scooter1556:
To be honest i never use the USB side of things, i was just happy that my SD card now mounts and unmounts without having to restart the phone on my Kaiser so i always use adb to copy stuff across or take the SD card out and use a card reader, but out of curiosity i just tried it on my Ubuntu install and it worked perfectly. I've heard many complaining about android and windows 7 though! I'll give it a go later on my Windows 7 install.
[Touch CDMA Android Development] natelust:
Thanks alot!

I just started using this image and it works great, especially with the sd card support working. I have a sprint touch, and the data connection is still hit or miss on it. Also is the battery status monitor working for anyone else? I have been a long time gentoo user, so to have windows on my phone is a big deal to me
[Touch CDMA Android Development] natelust:
also

Also, is there anyway to get a shell prompt on the phone? SSH anywhere is cool
[Touch CDMA Android Development] unsungboxer:
yup both known issues. however data connectivity seems to have gotten worse w this release but it's hard to say.

the thing to remember is that martin is making incredible progress on this esp considering he seems to be the only one working this port.

the sd card support is a huge win !
[Touch CDMA Android Development] dzo:
Hi,

Get this initrd:

http://cs-alb-pc3.massey.ac.nz/vogue/initrd.gz

Then boot up and find the ip of your phone from somewhere like whatsmyip.com and you will be able to telnet to it. username root, password vogue.

(assuming no firewalls in the way)

then:

chvt 1

will get you to the console

chvt 2

goes back to the ui

It's probably possible to make a little app to do this by writing to /sys

There's no ssh there yet but no reason why you can't compile one, I just wanted to keep the image small.
[Touch CDMA Android Development] natelust:
Thanks

Thanks for the replies, and yes, I am supper appreciative. I was wondering more if there is a terminal application for android, so that I can ssh out from my phone to my home computer. I suppose I can try to compile say xterm for arm and make an apk if no one knows of one already
[Touch CDMA Android Development] bose1970:
just wondering if anyone can add some apps to this

androids cool but it has no features like calculator messenger music ect ect

i was running a custom build that someone had put together with apps incuded

but no sd suport

thanks

Bose.
[Touch CDMA Android Development] unsungboxer:
I have added a number of apps to android from www.android-freeware.org. Sadly a large number of them do not even appear in the menu for me to determine if they work or not. Feel free to replace your data.img file with the one that I have constructed (back yours up). http://www.fileqube.com/shared/AdsmpV614

Files that are present and DO appear in menu:

android global time

geomata

manag 1.2

minispacewar

operamini

sms

toodo 1.6

xlive

Files that are present but do not appear in menu:

android file browser

hello activity

lunar lander

metosphere

notepad

puluwai

skeletonapp

snake

spacebugsdemo

I am testing apps by putting them in /data/apps. (For testing purpopses, I have created a subfolder called "notworking" to see if there was some limit on the number of apps.).

Martin, any idea why some appear in the menu, while others don't?
[Touch CDMA Android Development] dzo:
I think those apps are for the previous SDK, they need to be recompiled with a few changes.
[Touch CDMA Android Development] uiucryan:
No problem - it would be much appreciated if you updated the wiki once you have had your question answered. If we all did this it would be a great place to have these questions answered before the are asked (and re-asked) in the forums.

--Ryan