yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] gray_zx6r:
metro WAP and MMS settings

Ok i had installed windows mobile 6.5 on my HTC touch that i flashed from sprint to metropcs, i configured the setting to enable Wap and MMS DiDn't like 6.5 so

installed linux android on my HTC touch i can't seem to get my Wap and MMS working HELP ? and on great job with Android dudes,
[Touch CDMA Android Development] DrGit:
dzo, is there any reason you didn't try upgrading the kernel from 2.6.25 to 2.6.{current} before it got too hard? I can see now that it would take a very long time to upgrade the Vogue kernel to 2.6.33 or later, which is unfortunate considering what's been added to the mainline kernel since 2.6.25. I'm now running Debian Lenny on my XV6900 - Sid, Gentoo, Fedora, Slackware, Ubuntu, and others would also work, but they require a >= 2.6.27 kernel due to their udev packages requiring signalfd() starting with version 142. I'm currently having problems starting X, and I tried to get SSH working so I could debug it, but that unfortunately depends on USB gadget serial/Ethernet, which always gives me a kernel panic. I also can't replace udev in Sid now because the latest Xorg is moving from HAL to direct udev access. That stinks because Lenny doesn't have E17 packaged, and half the X11 apps I want are missing. I'm assuming you don't want to do the upgrade because it's not really worth it for Android, but in any case, thank you for doing the hard work of actually making the kernel boot for us! If I find motivation and the skill/time to do it, I'll attempt the port myself. (I have a little experience - I got my iPAQ H2210 to boot my 2.6.32 kernel without LCD support, which I ported from the last kernel [2.6.21] by handhelds.org.)
[Touch CDMA Android Development] mssmison:
Yes there was work put into the 2.6.27 kernel however there were issues with a random lockups which couldn't be resolved.
[Touch CDMA Android Development] guillefix:
Will it work in the HTC Cruise 09? And, sorry for the IGNORANCE, but will it still run Windows mobile, I mean, with this I can install Android Os, no?, but I doesn't take off WM ?
[Touch CDMA Android Development] jnadke:
Yeah, I've been thinking about refactoring and putting in a proper board support package. Though, my spare time is rather limited lately.

If we port to anything, we should use the official Android MSM tree:

http://android.git.kernel.org/?p=kernel/msm.git;a=summary

They seem to sync it to the patched RC versions every month or so (and I'd assume test it).
[Touch CDMA Android Development] DrGit:
Since I'm using Debian, I decided to instead port it to the current non-Android mainline git kernel - 2.6.33-rc6 as I'm writing this - and I'm about 10% finished overall. I have the main board code and non-working LCD code mostly ported, but everything else will take me a while after I have the LCD stuff working. I actually found out that my 2.6.25 kernel does work with udev, but I still want a newer kernel because half the other drivers I need were written for Android - Camera, GPS, audio, 3D... I think it would be beneficial to have standard Linux drivers instead of Android-specific ones (case in point: the ADSP audio drivers), because the standard Linux drivers/frameworks (i.e. ALSA and Video4Linux) are better maintained. They also have the benefit of working on any Linux distro people want to put on their phone (a lot of people like Debian) as well as on Android - AxDroid and NITdroid (Android for Dell Axims and Nokia Internet tablets) use this driver model. All of that probably won't happen unless I do it... I have a lot of work to do!
[Touch CDMA Android Development] dzo:
I made some improvements to the camera, if you press volume up/down when the camera is on, it will change the exposure settings. Use volume down if it's dark or you can hold the camera very steady, volume up gives you a shorter exposure time.

I know this type of thing shouldn't be in the kernel but it's much easier to do it this way rather that have to modify the userspace camera library and camera apps.

I agree that it would be nice to rewrite these drivers to use the standard interfaces but it would also mean rewriting the android userspace libs.

I think the codeaurora includes alsa and v4l drivers, perhaps you could modify them.
[Touch CDMA Android Development] superninjapirate:
After I put all the files on my card and run haret, the little window that says 'booting linux' comes up, but then a bunch of really small text looking stuff comes on my screen then fades to black and nothing happens after that. What am I doing wrong?

vogue-android.googlecode.com/files/android-1.5-2009-08-08.zip

i used those files
[Touch CDMA Android Development] dzo:
That's very out of date and doesn't do panel autodetection, either put the correct panel type in default.txt or use something more recent.
[Touch CDMA Android Development] *M*:
Nice work on the camera DZO, looks much better!
[Touch CDMA Android Development] hexto:
Thanks. A better camera is greatly appreciate it.

Any reason this thread hasn't been moved to the new Android Development section?

Edit: Finally did this and the camera is definitely a nice upgrade
[Touch CDMA Android Development] plemen:
What are the changes in the Feb 11 vogue 240x320 nbh? And what happened to your other thread DZO?
[Touch CDMA Android Development] mrkite38:
Dude, you have magic powers! ;)
[Touch CDMA Android Development] hexto:
lol. Glad to see this thread in its rightful home
[Touch CDMA Android Development] cp0020:
I can't use dzo's newer kernels. 2/02/2010-2/11/2010. Everytime I run haret it says, failed to load storage card/andboot/Zimage. So I'm stuck with the 1/14/2010 kernel. Any suggestions
[Touch CDMA Android Development] dzo:
I've made some changes to the clock code to slow down the clock and lower the cpu voltage when the display is off (vogue only at the moment). I've put vogue NBHs and a kernel in the usual place. I haven't tested this a lot and it may not make any difference but it might make the battery last a bit longer. If you have any lockups with this kernel, let me know.
[Touch CDMA Android Development] sshark:
I think my Vogue is getting old.

I get following errors while booting:

[] Block 86 is bad

[] Block 87 is bad

.

.

.

[] Block 288 is bad

Anyways to fix this?
[Touch CDMA Android Development] dzo:
NAND does have limited lifetime (about 100,000 writes/block i think) but these blocks were probably marked bad when it was made. As long as there aren't a huge number of them it shouldn't be a problem.
[Touch CDMA Android Development] tatnai:
flashed it, will post back later.
[Touch CDMA Android Development] cp0020:
6th time asking

Can someone pease help me. I can't use dzo's latest kernels. I can use the 1/14/2010 but verything after that won't work, it just says- failed to load storage card/andbooot/zimage. Its spelled corectly. I am using nomorootfs off sd.
[Touch CDMA Android Development] moekind:
DZO your latest kernel and .NBH causes the touch screen to stop working. It only works on the top on the notification area, and that too barely. Also,

it takes long to wake up from sleep.
[Touch CDMA Android Development] loserskater:
check your default.txt and make sure its spelled zImage. then make sure your andboot folder is spelled exactly like that and is in the root of your sd. in that andboot folder should be everything including a zImage, spelled just like that including capitalization. no date or anything else on the end of it either.

zimage ≠ zImage ≠ Zimage ≠ ZImage

Make sure its zImage
[Touch CDMA Android Development] cp0020:
Just tried it and still no go :( can you maybe upload yours? Thank you for your help :)
[Touch CDMA Android Development] mrkite38:
I feel like I have to press (much) harder to get the home screens to flip left / right. Scrolling up / down is a little harder than previous.

dzo, I commented in myn's thread that the 2/14/10 nbh made the screen beautifully responsive, that feeling is definitely lost with the 2/16/10 nbh. Can that be accounted for?

EDIT: just flashed back to be sure, there is a marked difference between the two.
[Touch CDMA Android Development] jnadke:
Make sure you're using the latest 2/16 kernel, looks like he may have posted two of them... it should be marked 23:16. The one earlier in the day had a Touchscreen edge trigger IRQ problem. Re-download it from his site.

He added in halving the processor speed when the touchscreen is off (saves a lot of battery life). D'oh, I was gonna work on getting cpufreq scaling working....

I'm not sure how tested it is, I suppose the processor speed could not be going back to normal. In a terminal do 'cat /proc/cpuinfo', you should see about 350-400 BogoMIPs.
[Touch CDMA Android Development] mrkite38:
Will do on both counts and post results... I grabbed it almost immediately after he posted, so I probably got the 'bad' one.
[Touch CDMA Android Development] margosmark:
Hey I am running the latest 2-16 240X320. I am checking the cpuinfo, and even when the screen is off its at 383.38 and when it is on.However, if I turn off the screen and check at that moment its at 191.69. Oh I am talking about BogoMIPS. So it seems to scale down for a sec then goes back up. I am running Myns Donut, and I do have phonePrioritizer going, perhaps thats forcing the scaling up.
[Touch CDMA Android Development] jnadke:
The latest one would be some 7 hours ago from now, so you probably have the 'good' one. I'm probably assuming incorrectly that he did post 2 of them.

Still, other than the cpu scaling, I don't see anything that could affect things majorly.
[Touch CDMA Android Development] jnadke:
I'm not sure what the proper code path is, but looks like in the arch_idle function he's scaling it down and then scaling it back up to full. So looks like the display is off but as soon as a task is scheduled it ramps up and never ramps back down.

It's slightly messy, so I'm not sure what's really going on.
[Touch CDMA Android Development] dzo:
Yes, you're right, what was I thinking! I'll fix it asap.
[Touch CDMA Android Development] mrkite38:
After reflashing the potentially newer 2/16, it's still not as good as 2/14. I didn't bother checking my cpu rate based on the other posts.
[Touch CDMA Android Development] *M*:
Is it possible to do the opposite and take the MSM7500 beyond its 400MHz stock speed?
[Touch CDMA Android Development] jnadke:
Maybe.

The PLL we're using is 800Mhz, and only integer dividers can be used.

Other devices (Diamond/TP/Hero) have another PLL that is ~1.0Ghz. I don't know if our device has one, but I intended to find out for cpu freq scaling support. If it did, that would mean the maximum we could safely go is 528Mhz. Even then, safe is relative, that's a pretty high overclock, so your chip could overheat and leave you with a bricked vogue :-/ Other devices run a relatively cooler 65nm, as opposed to our 90nm one.

The biggest power savings of this code is actually reducing voltage. Power = V^2 / R. R stays relatively the same (does go up with temperature), but reducing the processor voltage benefits greatly. It's roughly 20% going from the Max voltage to the Min Voltage.

I suppose Dzo could answer the 1Ghz PLL question...
[Touch CDMA Android Development] dzo:
Yes, there is a spare PLL and with the old clock code you can set it to any speed you like, just add clock_7x00.a11=528 (or higher) to the cmdline. You'll also have to change the ahb bus divider with clock_7x00.ahb_div=4.

I got rid of this in the current kernel because it's fun to play with but probably not really something you want to use all the time.

I just fixed the cpu clock scaling on idle and also added a fix for the ts to save some power. Kernel and NBHs are in the usual place.
[Touch CDMA Android Development] *M*:
I got a spare vogue for 75 on trademe so I don't mind testing this out, which kernel version was the last to have the old clock code?
[Touch CDMA Android Development] polyrhythmic:
Also, is it possible to change the values after boot, for example:

echo 528 > /sys/module/clock_7x00/parameter/a11

Or do they have to be set at boottime?
[Touch CDMA Android Development] mrkite38:
Touch sensitivity is still not as good as 2/14 in my opinion. Perhaps another clue - when I boot 2/14, the banner says 'VOGUE ANDROID', not just 'ANDROID', which is what I see with 2/16 & 2/17.

Edit: also, it any button will wake the phone, which isn't supposed to happen, right?
[Touch CDMA Android Development] dzo:
Yes, that will work, it takes affect after a resume from power collapse, should work on all kernels before 14/02/10.
[Touch CDMA Android Development] dzo:
That means it's not sleeping correctly. Could be a problem with your userspace rather than the kernel. Look through the logs to see what's keeping it awake.
[Touch CDMA Android Development] mrkite38:
It seems to be working correctly now, sorry. Something must still have been chugging from bootup.

It must take a few seconds to fall asleep - if I hit end, then another button quickly, it wakes up. If I wait a minute then only power will wake it up.

Thanks as always, dzo.
[Touch CDMA Android Development] *M*:
Okay, tested OCing and it seems all good. Seemed faster at an oc of 528MHz but I thought I should run some benchmarks just to make sure it wasnt a placebo, I did three tests for each:

CaffieneMark:

Stock -419,423,413

528oc -522,552,557

590oc -602,620,621

SoftWeg Benchmark:

Stock

CPU 104, 122, 120

Graphic 17.6, 17.8, 17.2

OC 528

CPU 134, 167.2, 166

GPU 22.9, 21.4, 22.4

OC 590

CPU 179.4, 173.6, 173.6

GPU 25.6, 23.8, 25.3

Anything over 590 becomes unstable, so I would say 400-550 seems a safe OC range.
[Touch CDMA Android Development] myn:
It's freezing cold here in Columbus. OCing could be a good thing, turning our vogues into pocket warmers :)

Is the OCing really that noticeable or just a slight improvement?

Long term I am guessing this would eventually burn out our cpu's?
[Touch CDMA Android Development] jnadke:
Not really. Long term damage won't be different unless the voltage is bumped up, which it isn't.

It will cause extra heating, and that could burn out your cpu, short-term. Long-term wouldn't be any different.
[Touch CDMA Android Development] moisha:
@dzo

On the power management note - neither of halt / poweroff / reboot works on my Kaiser booted with Haret. Is this kernel or userland related ? TIA
[Touch CDMA Android Development] polyrhythmic:
Regular 400 Mhz gives me a 380 average on Caffeine Mark on Kaiser.

528 OC gives me a 520 average score.

Eventually the OC freezes and I have to pull the battery and hard boot... needs more testing.
[Touch CDMA Android Development] bri3d:
@moisha - Eclair does the same thing on Vogue, and it's userland. If you're not running Eclair, it might be kernel.
[Touch CDMA Android Development] *M*:
I've also had lockups, though they seem to be related to the phone entering/exiting sleep mode. Gonna keep it on ac for a while running an app that keeps CPU at 100% to test stability.

Update: ran CPU maxed for about an hour, took pictures, made a call etc. No problems.

As soon as the phone enters sleep however it does not come out, so the instability must be something to do with sleep.

Changing the pm.sleep_mode to something other than 0 helps the phone come out of sleep but freezes soon after.
[Touch CDMA Android Development] jnadke:
The arch_idle function I talked about earlier was setting the frequency to 400Mhz manually, like I talked about in the old code. It does this in all of the old kernels, not just the new ones.

Unless the 528Mhz setting is somehow overriding this hard-coded value, I could see how something may be getting confused. It's possible it's not switching to the right PLL for 400Mhz, and locking up there, or something else.

I'll try writing a cpufreq driver when I get time and add in OC'ing capability. This way the kernel can decide how much to slow down the processor and get better battery life.
[Touch CDMA Android Development] daprince402:
Ok I just downloaded the latest version of android to my vogue but for some reason my picture mail is not going thru. Anybody have a solution?
[Touch CDMA Android Development] tatnai:
there is a thread either here or in the touch cdma general forum that talks about the reason for this, jnadke posted the answer in there, search all of his posts to find it.
[Touch CDMA Android Development] dzo:
I've put the overclocking code back in the latest kernel, for me it works fine up to about 500MHz. It takes effect immediately but only after the first power collapse has been completed. Some devices don't idle correctly on boot so idle is only enabled after the first power collapse.
[Touch CDMA Android Development] grktaurus83:
I wanted to bring up the issue of severe battery drainage happening when there are missed calls/notifications. I remember this issue being brought up sometime in the last few weeks but I can't for the life of me find it.

Did we determine what the cause of this issue is?

If so, is there any way to fix it?

I had my phone basically die on me today after a few hours because of this issue and I've seen massive dips in battery life every so often when I don't notice I've missed a message.

I'm almost getting to the point of being paranoid that I'm missing notifications... Haha!
[Touch CDMA Android Development] myn:
Thanks.

I just tested zImage-18-02-10 with the 02-14-2010 basefiles. Volume Up doesn't seem to be acknowledged on boot anymore. Has this been changed to another key for vogues?
[Touch CDMA Android Development] grktaurus83:
It might be the "center button" or "up" on the D-Pad now.
[Touch CDMA Android Development] myn:
Thanks.

Confirmed. It's now center button for vogue.
[Touch CDMA Android Development] tatnai:
I don't think it was ever addressed. I think two acknowledged the potential issue, but no one else really confirmed this. I still think this is happening, but maybe more people need to confirm this before it really gets looked at.
[Touch CDMA Android Development] grktaurus83:
I completely agree that this definitely is happening. The difference is huge.

At first I thought it was because I was in a place with crappy reception so the phone was constantly looking for signal, but recently I saw otherwise.

I've seen this issue happen when I left my phone on my desk for a few hours (with great reception) while I was lying down. I woke up to find an almost drained battery.
[Touch CDMA Android Development] dzo:
I've never seen this happen. Can you post (or send me) logs please.

logcat -v time > /sdcard/log

logcat -v time -b radio > /sdcard/log1

logcat -v time -b events > /sdcard/log2

dmesg > /sdcard/log3

Thanks
[Touch CDMA Android Development] tatnai:
will go through the day with some unanswered notifications today or tomorrow and post back with this.

EDIT: though come to think of it, if the processor keeps running for some reason while there is an active notification and the phone is sleeping, hopefully the new processor changes to the kernel during sleep should help.

EDIT 1: attached
[Touch CDMA Android Development] mirth18:
I have noticed the same thing with 2-14 nbh, battery drains a lot quicker than it used to.

If you need more logs I can try to help out too.
[Touch CDMA Android Development] dzo:
I can see why it's draining the battery, it's only ever sleeping for about 40 seconds at a time. Looks like it's the keyguard, it keeps saying:

"D/KeyguardUpdateMonitor( 176): We've updated the battery level!"

Is this eclair or donut? The donut I'm running doesn't do this.

I could perhaps work around it by not reporting the battery level from the kernel as often but I think its a userspace problem really.
[Touch CDMA Android Development] mssmison:
This is eclair I bet that's doing this. I have a patch that I'm looking to impliment to the eclair source that should fix this, unless it's donut, either way the patch I'm looking at should help.
[Touch CDMA Android Development] grktaurus83:
I won't get a chance to generate some logs for at least a few days because of my schedule, but I'm running donut so I'm guessing it's not just an eclair issue.
[Touch CDMA Android Development] tatnai:
No, I'm running plemen's donut. My battery life was the same on myn's though, and all other roms. Could the notification being active cause this?
[Touch CDMA Android Development] tatnai:
Btw, definitely some improvement in battery life with the 10-2-17 .nbh.
[Touch CDMA Android Development] dzo:
I've spent the last few days rewriting the battery driver. It should be much better now and should be very similar to the value WM gives.

For me, it reads a bit higher than before which is good because it means more battery life.

I can't easily compare it with the WM value, perhaps somebody running from SD can try it and see.

I also haven't tested it with different temperatures and a very low battery.

Changes are pushed to git, kernel and NBHs are in the usual place.
[Touch CDMA Android Development] ThomasHW:
I just flashed the new .nbh. I'll post if I see any significant improvements!
[Touch CDMA Android Development] mirth18:
Flashed the 2-19 nbh last night.. MUCH BETTER battery life today! You ROCK!
[Touch CDMA Android Development] polyrhythmic:
Sounds great dzo, one of these days I'll have to rework the Kaiser battery code too. Do you know if they are at all related?

Also, would you mind posting md5's for your NBHs? I suspect Android browser corrupts some of my downloads.

Thanks again for the great work, I've had my Kaiser flashed all week and it rocks. Further thanks are in your paypal :D
[Touch CDMA Android Development] ThomasHW:
The battery level is definitely reading higher now. The battery temperature is also far more realistic (it's now hovering around 20 degrees Celsius, whereas before it was around 130 degrees Celsius.)

Good work!
[Touch CDMA Android Development] cp0020:
I flashed the new nbh file earlier and I don't think its reading the battery right. I unplugged it at 100% and used it for 40 minutes, browsing the internet and playing around with market and apps and it wrnt down 4%!!!??? But when I plugged it in it said that the battery was at 76%.
[Touch CDMA Android Development] dzo:
It's not very accurate when plugged in and different batteries have different full charge values, it reports anything over 100% as 100% so it could be that you started at over 100%.

I ran a battery down to 10% yesterday and it seemed to work fine.

At least it's better than the previous code and I'm sure I can improve it further.
[Touch CDMA Android Development] incubus26jc:
you are doing fantastic work man. Keep it up. You are a smart man. The new nbh is working great for me. Thanks alot
[Touch CDMA Android Development] Reddog80p:
I noticed about a 20% difference. Before the new NBH after 12 hours of light use (calls, text, little browsing) i'd be down about 40% today I sat @ 60% :)
[Touch CDMA Android Development] tatnai:
Much better battery life for me with 2-19-10 .nbh. thx dzo.
[Touch CDMA Android Development] incubus26jc:
will this have any effect on how our phones charge? will it be better about knowing when its 100%?
[Touch CDMA Android Development] mrkite38:
Battery life seems much better, I'm not visibly losing anything while my phone sits idle overnight anymore. :) thanks dzo.
[Touch CDMA Android Development] sshark:
Battery life is much better with 2-19. Phone sleeps properly and while slept not loosing power or loosing at much much lower rate compared to previous kernels.

For example, in a usual day, I would loose around 40-45% of battery by lunch (from a full charge from 7am - no talking and 20-30 mins of surfing).

Now I am still at 77% after roughly 15-20 min of talking and probably an hour of surfing.

ymmv