yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] n2rjt:
Kaiser Battery

Kallt_Kaffe checked in a change to the battery code, changing a constant from 10 to 15. Note that this changes the current, so we probably don't want to declare the battery full at 200mA charge current ... that's pretty high. I'd suggest 50mA instead. The old comment said that 10 was "from the maths". I always wondered what maths, and have been suspecting that the value was not correct. That, plus the logic that sets the capacity low when voltage drops below 3.3, and the logic that sets capacity high when voltage > 4.1 and current <= 200 would all contribute to a battery that seems either nearly full or nearly empty all the time.

I suspect that the constant change might also affect the proper battery capacity to configure. I've gotten good results by changing from 2850 to 1700 with the new code, for my 1600 mAh Lithium Polymer battery.

I also experimented with enabling the "#if 0" code. It seems useful for discovering the best values to use, but I'm unsure of the value of dynamically changing battery_capacity. If it ever gets enabled, the logic inside could use some cleaning up.
[Touch CDMA Android Development] samjam:
yaffs tragedy

Twice I've had the case of my phone hung, and after a restart I get lots of messages on text console (before graphics mode) like:

block was not erased ...

no more erased blocks ...

allocator out...

The cure is to backup the data (from the initrd menu), erase the data and restore the data.

So I wonder why yaffs isn't erasing as it goes along.
[Touch CDMA Android Development] samjam:
Also, I note with 2.6.32 my wifi loses connection more often and doesn't re-associate so easily when I go into range - I often have to disable & re-enable wifi to prompt it to associate.
[Touch CDMA Android Development] dzo:
I've seen this before on a kaiser but never on a vogue, I'm thinking that perhaps some of the kaiser nand has mpu protection enabled. When I get some time I'll investigate.
[Touch CDMA Android Development] gt!:
I had this problem and it was happening at least once every 2nd day. The last time it happened I setup the Exchange account through the system settings menu instead of from the email app. I don't know if it was this, or updated kernels, but I haven't had this problem since then (about 3-4 days).

-GT
[Touch CDMA Android Development] samjam:
I wonder if this relates to the "missing icons" problem where the data-on-nand (on earlier froyo and earlier kernels) used to revert and lose some icons and data.

I had thought that was just cos journaling/checkpointing wasn't working
[Touch CDMA Android Development] dertester123:
I had this on a pola200 too. Was after the device shut down due to battery empty.

I had this before, one time it was doing this ?scan? and than started i think but with app crashes and so on, last time it was doing it permanently.
[Touch CDMA Android Development] htc_vogue:
I just tried on my Vogue and getting "mdp_dma_to_mddi: busy" on the last step. Any fix for that?
[Touch CDMA Android Development] htc_vogue:
I was using a 4GB microSD card and that seemed to be the problem. Switched to 2GB and it worked fine.
[Touch CDMA Android Development] Gersonian:
320x480

I have been checking the kernels pretty regularly, and am wondering, are you done posting 320x480 resolution kernels? I personally prefer them and really relied on your making them because my experiences with nbh editor were terrible. Would love to get those posted again if possible.

Thanks!
[Touch CDMA Android Development] dzo:
The nbh editor should work fine, if not you could always just use a hex editor to change the resolution. I haven't tested any of the recent kernels with anything other than 320x240 and there's really no need to use anything else since very few apps don't work with qvga.
[Touch CDMA Android Development] 4ultratech:
Overclock

Is their a cmd line arg for CPU overclocking?

I currently overclock to 520Mhz.

Rogue Tools is becoming a pain to set on every reboot.

When I fresh boot my phone the CPU speed is 383Mhz.

If I overclock with Rogue to 520Mhz it shows 498Mhz.

Is the variance just a multiplier or is my CPU locked lower

than most, I thought they were 400Mhz.

Thanks....
[Touch CDMA Android Development] dzo:
383 is the BogoMIPS CPU speed, a linux speed measure found on boot by timing the execution of a short loop. Your CPU is running at 400MHz.

To overclock on boot, add clock_7x00.a11=520 to the cmdline.
[Touch CDMA Android Development] 4ultratech:
I use QuickSystemInfo Pro program to read the CPU speed.

When I boot and until I run Rogue Tools to overclock it shows the

CPU speed at 383Mhz and then after I run Roque with 520Mhz is shows

CPU speed at 498Mhz. Are they reading the BogoMIPS or is the variance

standard.

Thanks for the help all of the work you have done on the Vogue is amazing.
[Touch CDMA Android Development] dzo:
Sounds like it's reading BogoMIPS, the CPU speed isn't reported by our kernel so it can't be correct.
[Touch CDMA Android Development] samjam:
lots of hanging 6th Sept Kernel

I'm using the 6th September Kernel from http://it029000.massey.ac.nz/vogue/files/?C=M;O=D on a kaiser.

For the last couple of days I get many times a day the condition where the screen stays black; but adb commands work

it just happened now, so I took a logcat.

In the recent entries you can see it claim to turn the screen on or off, but it doesn't actually turn on or off as I can see it.

Is there a shell command that will reboot the phone nicely?

halt, and halt -f, don't do power off.

Sam
[Touch CDMA Android Development] samjam:
Further more, the yaffs-tragedy of un-erased blocks is occuring more and more often after the recover technique of backing up data, erasing data and restoring data.
[Touch CDMA Android Development] jrs007:
Wifi Froyo

Hello, I have system-Froy-02-09-10_17 but the WiFi does not work, it appears only "error" when I turn it on.

I wonder if anyone here has any Froy the wifi work on the HTC Kaiser and to make available the link to download

I thank you guys!
[Touch CDMA Android Development] samjam:
Which kernel do you have?

You might also want the latest kernel from: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
[Touch CDMA Android Development] scooter1556:
Had good experience with the new kernel so far. Calls etc.. seem stable to me. My kaiser has refused to obtain an i.p. address on wireless with the last couple of kernels running Froyo so i've had to set a static i.p. which is strange and not something i have seen others complaining of.

The main thing i wanted to know is peoples experience with GPS on the latest kernels (2.6.32). I have tried it a couple of times and it gets a signal but i have only had it working for 10 minutes at most before either the phone crashes or the app closes. Seems fine while it is working though, but be great when GPS gets to the stage where it is as stable as it was in 2.6.25.
[Touch CDMA Android Development] samjam:
I find mine takes a few tries before it gets an address. I will disable/enable the network a few tries and it will work eventually.

Sam
[Touch CDMA Android Development] Gersonian:
Ok so you were right. However, I would say I have a decent amount of glitches. I have tried the 9/2, 9/6 and 9/9 kernels.

I get a backwards or inverted screen often on wake up, sometimes the phone will not come out of sleep, sometimes it freezes, but shows a constantly running script very faintly on the screen, and maybe one or two other things.

thanks for the help and hard work!
[Touch CDMA Android Development] samjam:
When my phone refuses to wake, it still vibrates (with messges); and the battery gets warm.

just now it has hung while on USB with the screen on. No keys work; adb shows me that /system/bin/mediaserver keeps restarting and quitting.

I get lots of this:

[39199.163909] request_suspend_state: wakeup (0->0) at 39199729702631 (2010-09-17 09:25:18.985809355 UTC)

[39199.175842] init: untracked pid 8105 exited

[39200.108734] snd_set_device(1,1,1)

[39200.108825] snd_set_device 1 1 1

[39200.108886] rpc_write(7f,0,2,30000002,0,1,0,0,0,0,1,1,1,3,0,)

[39200.109832] rpc_read_command(pm=80f60034,78,0,2,31000002,0,3,0,0,0,0,3,0,0,)

[39200.109954] [RR] ERROR no local ept for prog 02000031 replying anyway!!

[39200.109985] rpc_write(78,1,0,0,0,0,)

[39200.110107] rpc_read_reply(7f,1,0)

[39200.124267] Setting function 4 for gpio 68 that I don't own!

[39200.124328] Setting function 0 for gpio 69 that I don't own!

[39200.124389] Setting function 0 for gpio 70 that I don't own!

[39200.124420] Setting function 0 for gpio 71 that I don't own!

[39200.126373] set volume of 256 to 5

I'm sure that the untracked pid is:

8169 1013 22200 S /system/bin/mediaserver

This command shows that the parent id is 1:

# cat /proc/`ps | grep medi[a]server | sed 's/^ *//;s/ .*//'`/stat

8637 (mediaserver) R 1 8637 0 0 -1 4194560 1064 0 0 0 81 10 0 0 20 0 1 0 3943996 17485824 874 4294967295 32768 34876 3198037200 3198036744 2952814584 0 0 4 38120 0 0 0 17 0 0 0 0 0 0

So I can't easily stop whatever keeps launching media server, or work out why it is un-tracked.

I ran this loop:

while : ; do cat /proc/`ps | grep medi[a]server | sed 's/^ *//;s/ .*//'`/stat | sed 's/.*) [^ ]* //;s/ .*//' ; done

to see if I could ever catch what launched media server, but could not - the answer was always 1
[Touch CDMA Android Development] mrkite38:
mediaserver is launched as a service called media from sysinit.rc. if so you might be able to stop it with the service command (at your own risk, if course.) Pid 1 is probably init.android.
[Touch CDMA Android Development] samjam:
Thanks for the tip. Reading up about media server, I've decided to take that widget off my homescreen - maybe that will save some battery use and crashing.
[Touch CDMA Android Development] Gersonian:
sleeping

I noticed the last several days that my battery keeps running down about half way through the day. I checked under the battery monitor in spare parts and it claims that the phone has not gone into sleep in over 5 hours. However, the screen continues to turn off.

I do not know if this is a kernel issue or an issue with inc's rls15. It may also be an issue with my settings, but I do not see anything I have done to cause that to happen.

Any ideas?

One more thought: I could be using the phone more heavily than in the past, but I really do not think that is it.
[Touch CDMA Android Development] thoughtlesskyle:
What kernel are you using I know some of the older ones had a problem with the power collapse
[Touch CDMA Android Development] samjam:
I'm wondering if my new HTC magnet-catch holster case is causing my kernel troubles.

It is a tight fit and sometimes presses buttons when it is in the case.

So it may be that if a button is pressed for too long, the GUI crashes and the display never re-lights.

I'll do some experiments to see.
[Touch CDMA Android Development] uriahheep:
Hello,

I've built a custom kernel (based on latest 2.6.32 git) with a few extra modules added to the default vogue config, including an untested implementation of ALSA.

My problem is that the zImage is 1.9MB in size, which doesn't fit with the current tinboot, and just changing XIP_END to a larger value causes the RUU to give an error 270 (corrupted rom). So, I was wondering, what would need to be changed in tinboot to build a functioning NBH?

Thanks,

uriah
[Touch CDMA Android Development] mrkite38:
holy crap

this thread just passed 1,000,000 views! amazing.
[Touch CDMA Android Development] dzo:
You could lzma compress the kernel, I think I saw a patch somewhere for arm that allows this. Also, to make the initrd a bit smaller, take init.android out, it's in /system now.
[Touch CDMA Android Development] uriahheep:
Hey dzo,

Thanks for the tip! Removing init.android from initrd did the trick.

However, now for some reason data is not working at all... Do you think this might be related to the removal of init.android? Must I also add something to an init script linking init.android to the correct location?

Cheers,

uriah

[EDIT] I solved my data connection issue by reverting to the previous version of initrd.lzma (the one that l1q1d commited to the tinboot git repo on 2010-09-03)... Also, since this initrd.lzma was smaller, it was able to fit in its entirety along with my custom kernel. [/EDIT]
[Touch CDMA Android Development] Gersonian:
Previously I was using 9/2

Right now I am using 9/9.

However my bigger issue now is that my phone just sort of freezes up and the screen wont come back on. It even happens in the middle of calls. This might be inc's rls15, but I dunno. The most recent kernels just do not seem so stable to me.
[Touch CDMA Android Development] samjam:
All my recent crashes (many times a day) seem to be down to my new holster case being too tight and holding down some of the buttons.

Sam
[Touch CDMA Android Development] *M*:
Not sure if its the same prob, but mine does that when I charge off AC, it shows full charged but within 2 mins off the charger its already dropped a bar then half-way after a few hours, if I charge off usb it charges properly & I can get a few days out of it.
[Touch CDMA Android Development] mssmison:
You may need to remove some uneeded modules. I haven't compiled the vogue kernel in a while, but last time I did there was lots that could be disabled in the config.
[Touch CDMA Android Development] thoughtlesskyle:
good seeing you again mssmison
[Touch CDMA Android Development] mssmison:
:) thanks, Admittedly I still pop into the vogue section from time to time to see how things are coming along :)
[Touch CDMA Android Development] wondercow:
back button

I mentioned this in the Fresh Froyo thread, but with a troubleshooting suggestion by derringdo, it looks like this is a kernel issue.

I'm running Fresh Froyo on SD with ext2 on a Vogue. With every zImage released after zImage-2.6.32-froyo-24-08-10 (the original 2.6.32 release), the back button doesn't respond the first time I press it after power collapse. After I press it once initially, it works fine. If the phone goes into power collapse and I wake it up again, the problem returns.

This was not a problem on the original 24-08-10 zImage release, but it is on all subsequent kernels. Does anyone else besides myself and derringdo have this issue?
[Touch CDMA Android Development] bohbviolet:
I feel very sorry to trouble you，but i have found almost the all threats about flash android on NIKE（Touch Dual）but never find the way to install android on NAND for not an .NBH film could be use. could you help to build a film for the user of NIKE？

sorry for my bad English.
[Touch CDMA Android Development] dzo:
As far as I know, nobody has booted Nike from nand yet. You will have to modify Tinboot and possibly the kernel too. Good luck.
[Touch CDMA Android Development] thoughtlesskyle:
Good to see you still are on here from time to time Martin
[Touch CDMA Android Development] 4ultratech:
Status

Is Development on this Dead?

Any update would be great.

Thanks....
[Touch CDMA Android Development] dzo:
No, it's not dead, I'm very busy at work at the moment so I haven't had much time to devote to this. I've been running the latest kernel on Vogue for a few weeks now without any crashes or problems.

I'm not going to be doing any more work on Kaiser and Polaris because my Polaris has stopped working and I really don't have time to support anything other than Vogue.

I still read this thread so let me know if something doesn't work (Vogue only).
[Touch CDMA Android Development] vellowax:
Thank you very much Dzo.
[Touch CDMA Android Development] l1q1d:
Hi, dzo, could you please tell me wheere i can find some documentation about nand drivers?

I want to fix nand driver in 2.6.32 kernel
[Touch CDMA Android Development] cnigro1279:
Kaiser Lock up...

So I've been running Fresh Froyo with the Kernel from 9-9 and have been dealing with black screen of death issues. I'd restore my data time and time again but the problem persisted. I decided to try ADW Launcher instead of Launcher Pro and have not had crashes since....Maybe Launcher Pro is unstable with our new Kernel? Just a thought....Maybe someone else could try this same experiment to see if it is not an isolated issue....
[Touch CDMA Android Development] scooter1556:
I have to say that i have been using ADW launcher which i rip from the cyanogenmod nightly builds and put in my app folder before installing and suffer rarely from many of the lockup/wake issues people have talked about on here. I do suffer from the nand driver instability corrupting data on the 2.6.32 kernels however which can cause some strange issues such as calls going straight to answer phone etc... Frequent data backups and wipes! Be great to get the nand driver sorted l1q1d, only thing keeping me on your 2.6.25 kernels!
[Touch CDMA Android Development] derringdo:
Hey dzo, great to hear from you. Here are a few things that I've noticed with the latest kernel running on Vogue (Haret)

1) After waking the phone up from sleep, I have to press the back button twice before it registers. The first press does nothing, only subsequent presses do. Wondercow is experiencing this issue as well.

2) The email app seems to get reset randomly, as in it loses all of my Exchange information. I can't seem to figure out what is causing it to get wiped.

3) I still get the sleep of death issue - I don't know what's causing this either. I have a feeling I should try a fresh install with no apps to see if something is causing it to hang.
[Touch CDMA Android Development] SuperJMN:
As a Polaris user, I couldn't be more afflicted. It has been finally left out. Well, it's the key of progress. Soon or late, technology becomes obsolete.

Sad news.
[Touch CDMA Android Development] dzo:
1) Odd, this doesn't happen to me, can you attach a kmesg log from just after wakeup. ("dmesg > /sdcard/kmsg" from adb or a terminal)

2) Not a kernel problem

3) Is this a dead kernel (back button doesn't change leds if you keep it pressed) or userspace (scrolling text). If the kernel dies, try to get a kmsg from before it died (reboot and do "cat /proc/last_kmsg > /sdcard/last_kmsg")

p.s. what panel type do you have?
[Touch CDMA Android Development] wondercow:
Hi dzo,

Attached is the dmesg output immediately after waking my phone up from power collapse, when I have to tap the back button twice to get it to respond. I had to get it from terminal because using adb prevented my phone from going into power collapse and I couldn't replicate the behavior while plugged in.

Maybe useful troubleshooting info: the D-pad shares this unresponsive behavior. After waking up from power collapse, neither the back button nor the D-pad work on the first press, and the green/red lights don't come on when I press the first time. After you have pressed a button once, the second press works normally. I can mix and match between buttons too (ie press the D-pad once, phone doesn't respond, but now the back button will respond).

It's been a long time since I had to specify panel type--it's not in my default.txt any more, but I think back in my Donut days I had to use type 2? Or maybe 3? I have a US Sprint Vogue in case that narrows down the possibilities.
[Touch CDMA Android Development] dzo:
Hi,

Nothing unusual there, can you try:

echo 1 > /sys/module/board_vogue/parameters/button_wakeup

and see if this makes a difference.
[Touch CDMA Android Development] dzo:
If this doesn't help, try:

echo 1 > /sys/module/board_vogue/parameters/debug

and then get another kmsg after the cam button doesn't work.

Thanks
[Touch CDMA Android Development] wondercow:
Sorry, no success with echo 1 > /sys/module/board_vogue/parameters/button_wakeup run as superuser. I rebooted the phone just to be sure, but the problem persisted.

Attached are 2 kmsg files from after I ran echo 1 > /sys/module/board_vogue/parameters/debug

The file kmsg was obtained first after a fresh reboot after the phone was woken up from its second power collapse. Then, I tapped the camera button (no lights came on) and then I got kmsg2. Maybe the difference between the files will be helpful?

Thanks again for all your support!
[Touch CDMA Android Development] dzo:
Looks like it's getting the interrupt but ignoring it because the pm code reads a different value after power collapse. Can you try this kernel:

http://cs-alb-pc3.massey.ac.nz/vogue/files/voguimg-240x320-2.6.32-froyo-28-09-10_22-testing.nbh

Thanks.
[Touch CDMA Android Development] wondercow:
I'd be glad to, but I have been using the zImage version of the kernel via HaRET (as has, I believe, derringdo, who also had this problem). Would it be possible for you to provide a zImage?

Many thanks.
[Touch CDMA Android Development] dzo:
Ahh, makes sense now. Wince sets up some things for power collapse that I don't, so if you boot from haret it's slightly different. Try this:

http://cs-alb-pc3/vogue/files/zImage-2.6.32-froyo-29-09-10_10-testing

If this doesn't work you could always flash to nand!
[Touch CDMA Android Development] derringdo:
Looks like it's a dead kernel. There's no scrolling text (although I seem to recall experiencing this too, I'll make a note of it if it happens again). The screen stays black, and the only button that will do anything is the back button, which turns on the call/end buttons but nothing else.

I can't remember what panel type I have since I don't have any default.txt's going back far enough to require a panel type - however, I think it was panel type 1. I'm using a Bell vogue if that tells you anything. Is there any way to check?
[Touch CDMA Android Development] derringdo:
Looks like this fixed the back button issue! Your url seems to be broken though... Awesome work with the fix!! :)
[Touch CDMA Android Development] wondercow:
Awesome! Thanks, dzo, that new zImage fixed it perfectly. I really appreciate your support!

You mentioned that power collapse is a little different from NAND than booting from WinMo. I was under the impression that once I clicked on HaRET.exe, everything was 100% the same in Android's eyes. Am I mistaken about this?

I've been waiting to flash to NAND because I can't upgrade my phone until October 1 if I mess anything up, but October 1 is almost here and so I'm ready to be a little more daring with the ol' Vogue. Are there differences behind the scenes between the HaRET and NAND versions that might result in different stability experiences? I always assumed they were the same except for the extra step in bootup.
[Touch CDMA Android Development] 4ultratech:
Test Kernel

Running new testing kernel zimage on Vogue CDMA using haret for a couple of hours now.

The camera button problem was very annoying but I can confirm it is fixed.

Also seams to run alot faster and smoother. Will keep testing.

I keep thinking I'm going to buy a new Droid X but I can't believe how well this works

and I just can't bring myself to pay the $30 extra a month for the data plan.

Wish I knew more so I could help out but thanks for all the work.
[Touch CDMA Android Development] flinx42:
No more Kaiser support

I appreciate that this thread is under Touch, not Kaiser, but as there is no equivalent one there, i would still like to know:

Is anybody else still (intending) to do dev on the kernel for Kaiser?

e.g. Kallt_Kaffe?

If not, then it looks to me to be the time to sell the Kaiser, as the last kernel/build versions are still not stable enough for "serious" use.

I.e. I loose data connection once a day or so and every 2-3 days it needs a restore of /data as it seems to completely corrupt that fs. -> No incoming calls anymore as one of the main problems of that.

Without these issues I'd be happy to stay on the current version for another year, before getting another phone. But like this I will have to go back to WM as I require a phone that is at least able to receive calls at any time. :(

Thanks for all your hard work dzo, it was fun watching it get as far as it got.
[Touch CDMA Android Development] l1q1d:
I'm testing now new version on kaiser (if nand is fixed) i'm going to tell you if it works