yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] berardi:
2-19-2010 battery is definitely reporting more accurately. Previously my battery would drop very quickly to a low % and then hover there for some time. Now it drops slowly throughout the day and doesn't spend so long at low. Good job and thanks!

This is sort of unrelated, and possibly purely coincidental, but last night with my Navigation, the GPS signal dropped off several times in use. Once it dropped off, the first time I rebooted and it worked, and dropped off again. Then I tried backing out to maps, and it worked fine there, went back in and then it worked again. I may have messed something else up, but this is the most recent change I made so I figured I'd put it out there. I'll post again if the GPS droppage continues if anyone wants.
[Touch CDMA Android Development] tatnai:
this is being discussed in the GPS thread, it is a known issue
[Touch CDMA Android Development] tatnai:
ran this a second time. this time, unlike the last time, no notifications were left unattended. last logcat was with plemen's donut, kernel from 2-17. this one is with myn's donut, kernel 2-20 from sourceforge - so with the new battery changes.
[Touch CDMA Android Development] dzo:
This is better, it's only waking up every 30mins. This will still drain the battery more than it should. I'm guessing you have email set to check every half hour or a widget checking for news or weather.

If you look through the kernel messages (with dmesg) the messages that says "Wake up in X seconds", tells you how long it wants to sleep for. X should usually be very large, if not it means an app has asked to be woken up.
[Touch CDMA Android Development] tatnai:
hmm, thx. my I have everything set to off as far as syncing, notifying, etc; email x 2, facebook, google voice; only widgets at this point were power control and a battery status widget (which I usually don't run). any way to determine what it is, cause i religiously turn everything off. thx for looking at it, btw.
[Touch CDMA Android Development] polyrhythmic:
@tatnai: try commands dumpsys power and cat /proc/wakelocks to see what is keeping your device from sleeping.

@dzo and devs,

The latest 20-Feb Kaiser Eclair .nbh is working great on my Kaiser, I even successfully had it overclocked to 528 for about an hour and a half before it locked up -- the OC is an incredible speed improvement for Eclair!

I'm no longer running from HaRET, so I'm not sure how to dump the crash dmesg out of memory after rebooting. What can I do to debug the crash, and how else can I help make the OC more stable?
[Touch CDMA Android Development] dzo:
After a reboot the previous kernel messages will be in /proc/last_kmsg if power hasn't gone off. Unfortunately on my kaiser you have to pull the battery to reboot so that doesn't work. OC is fun but it does draw more power, the most stable OC is probably to keep the ahb divider at 3 and not push the clock too much.
[Touch CDMA Android Development] incubus26jc:
how do we overclock on the vogue?
[Touch CDMA Android Development] dzo:
It's the same for all devices, use a recent kernel and do:

echo 4 > /sys/module/clock_7x00/parameters/ahb_div

echo 500 > /sys/module/clock_7x00/parameters/a11

a11 is the cpu clock speed in MHz, adb_div is the bus speed divided from this value. Defaults are 400 and 3.
[Touch CDMA Android Development] tatnai:
thx polyrhythmic
[Touch CDMA Android Development] derringdo:
Has any headway been made on the sensitivity problem? I and a few others who are using Myn's latest warm donut with the 2-20-2010 kernel have noticed this too. It's much harder to scroll through the home screens, and scrolling through the application drawer is a pain since apps constantly accidentally launch if I don't swipe hard enough.

Myn's previous release used what looks like the 1-28-2010 kernel and it's buttery smooth compared to this latest version. I've gone back and forth (subjectively) testing the sensitivity of the two releases and it looks pretty conclusive :(
[Touch CDMA Android Development] ThomasHW:
Have you tried the 'calibrate screen' app?

And did you press 'menu --> save' after you calibrated?
[Touch CDMA Android Development] bri3d:
I think it's commit a33f907104e2972b37a246440d443e7fc862114c "Fix idle clock ramp down and power down ts between samples on vogue." which adds a digitizer powerdown between samples. While supposedly the sampling interval didn't change, I suspect the powerdown might cause the less-smooth behavior. I think it saves battery life though. Obviously dzo would know more since it's his code.
[Touch CDMA Android Development] polyrhythmic:
Here's something I haven't brought up before:

Compcache seems to be necessary on my Eclair build so that at least a small amount of programs can be kept in memory -- it makes switching often-used apps noticeably faster. However, when I use backing_swap the cc_disksize limit seems to be completely ignored. Also, when I load compcache on boot it complains that my kernel version is wrong. Should I be using a compcache module that's been compiled against the newest kernel? And if so, has anyone already compiled cc for the new kernels?
[Touch CDMA Android Development] dzo:
I made some changes to the ts code and fixed a problem with the battery too. Hopefully this will help people with ts problems. NBHs and kernel in the usual place.
[Touch CDMA Android Development] mrkite38:
thanks dzo - this seems more like the 2/14 feel to me, very smooth between home screens and in the apps menu.
[Touch CDMA Android Development] grktaurus83:
Agreed.

Thanks Martin.
[Touch CDMA Android Development] derringdo:
Scrolls beautifully once again, thank you dzo!
[Touch CDMA Android Development] dmulligan:
Are there any quantitative results on the power savings possible with this nbh?
[Touch CDMA Android Development] a5ehren:
No one has gone an bench-marked it, no. If I had to make up a number, I'd say it's about 15-20% better.
[Touch CDMA Android Development] berardi:
This was a great update!

#1 My battery life must have at LEAST doubled. In the past, at 1 PM I was at around 15%. Now my battery at 1 PM is at about 60%. Great news!

#2 I agree on the scrolling, it is perfect now

#3 A strange issue that I was having has been resolved. I haven't seen anyone else have this issue- I had access to both paid apps and 480 resolution apps, yet I was unable to access the "top paid" menu in market - only "top free". I know that I had access to paid apps because market enabler was done and I could access paid apps by searching or clicking just in. Either way, whatever the root of this strange bug, it's been squashed with this update.

Great work!!! Thanks a lot
[Touch CDMA Android Development] sshark:
Battery life and scrolling is very impressive with 2-23 build.

Has anyone else experienced issues with dialer? Mine takes too much time to load usually and to respond when there is an incoming call.

DZO, any changes that were made affected may dialer function? I am just thinking it might be one of apps that I was installed?!
[Touch CDMA Android Development] prairiefire:
I'm trying to find an answer to this but can't find it in search or on the FAQ. I am using android on the NAND (great btw) and have selected to store my data on nand. I've backed up my data and notice the databackup.img file but am wondering where my data.img file is located. I've searched using the program ASTRO for a 'data.img' file looking from the root directory (which i assume is nand, since /sdcard is a subdirectory) but cannot find a data.img file anywhere (/data folder looks empty and i have searched for hidden files). Any thoughts?

cheers
[Touch CDMA Android Development] sshark:
databackup will be under /sdcard/andboot
[Touch CDMA Android Development] prairiefire:
I know where the databackup file is. Is that not the backup? What i'm searching for is the actual data file, not the backup
[Touch CDMA Android Development] plemen:
There is no data.img file - there is a partition in nand that is used for data. The data.img acted as a mountable partition in non nand configurations.
[Touch CDMA Android Development] tatnai:
I think that this is more likely to be userland (i.e. in the system, ROM) rather than kernel. are you using myn? update to wysie's 2.8 contacts and see if that helps.
[Touch CDMA Android Development] mrkite38:
replace kernel in old nbh

I'm switching back to sensehero for exchange support, but it still requires rootfs. I'd like to have the nice features of the newer kernels (since I'll be going back about 3 weeks) but this means I'd have to put a new kernel into the old nbh (due to the changes in partition layout.)

Something tells me this is the sort of question where if you need to ask you shouldn't, but can this be done with a moderate amount of setup / effort?
[Touch CDMA Android Development] polyrhythmic:
It might be easier to port the build to no-rootfs than to use an old kernel. What build are you using that doesn't have exchange support? If all you're missing is Calendar I have a MotoCal that will sync Calendar for you.
[Touch CDMA Android Development] mrkite38:
sensehero (jamezelle) just waiting on him to get a new vogue so he can do the fixes. I was using myn's rel3, I had mail but need calendar/contacts and I'm such a cheap sob... ;)
[Touch CDMA Android Development] polyrhythmic:
You can give this a shot: MotoCal

I don't use exchange so I've never fully tested it, but others seem to like it.
[Touch CDMA Android Development] moisha:
I did have that today - missed an incoming call twice.
[Touch CDMA Android Development] c0d3w4lk3r:
SIM Lock

Hey All

I'm new to the forum and PDA tweaking so please bear with me.

I managed to install the port of Android to my HTC Touch Dual. However when I booted into Android I'm getting a SIM Lock on a device that isn't SIM locked. When I enter the PIN code I'm getting the message that the PIN is incorrect. When I boot into WM6.5 there is no problem.

I removed the SIM to see if Android itself is working...and it is! :D It even runs smoother then I thought.

Is there a way to avoid the SIM lock so I can test the full functionality of Android? If you need more info just tell me what you need to know (and where I can find the info).

Thanks in advance!

[Edit]

I found the solution. It seems that the use of PIN has to be disabled in WM6.5. I disabled the PIN and now Android doesn't give the SIM lock warning anymore.

The only thing I have to do now is see if I can get the data connection working :/

[/Edit]
[Touch CDMA Android Development] bandur:
Battery issues

I know the battery driver is worked on, I hope this report is helpful.

I run éclair with Vilords 20/2-10 nbh on Kaiser 130.

I have two batteries for my Kaiser. If I run down one battery, shut it down and pull the battery for about 5 min and then change to the fresh one android will report that there is no juice left on the fresh battery. If I then shutdown, pull the battery again for about 5 min and boot, android will report battery status correctly.

Additionally, yesterday after using about 1/3 of the battery Android suddenly reported out of battery. After a while it reported fully charged battery. About 8 hours later it continued to report fully charged and when I tried to charge the battery it would not charge. This morning (waiting an additionally 8 hours) it continued to report the battery fully charged. Suddenly it dropped, and shut off.

Regards,
[Touch CDMA Android Development] berardi:
Update on my strange market issue - where I have access to paid apps and all resolution apps via search, but there is no "top paid" button to sort by top paid apps.

The 18-2-10 version produced the problem, the 19-2-10 version fixed it, and the 23-2-10 version produced the problem again. I can't imagine why this is, but this has been my experience. Not a big deal, I can access everything by searching - just reporting. :)
[Touch CDMA Android Development] jnadke:
Try the 2/23 kernel. Dzo fixed some battery reporting stuff between 2/20 and 2/23.
[Touch CDMA Android Development] dzo:
Those fixes were only for Vogue, I haven't changed the kaiser code at all.
[Touch CDMA Android Development] egzthunder1:
Hey dzo,

Just sent you a pm...
[Touch CDMA Android Development] slm4996:
This should work for you to make your battery show correctly:

http://xdaforums.com/showpost.php?p=5695425&postcount=126
[Touch CDMA Android Development] dzo:
I've got the High Speed UART working now, this means A2DP should work. I don't have any A2DP devices so can't test it but it should work better than it did at least.

To try it, get the latest kernel and make the following change to /system/sysinit.rc.

After the word texas in the hciattach parameters, add 4000000

so this:

service hciattach /system/bin/hciattach \
-n -s 115200 /dev/ttyMSM0 texas
user bluetooth
group bluetooth net_bt_admin
disabled

becomes this:

service hciattach /system/bin/hciattach \
-n -s 115200 /dev/ttyMSM0 texas 4000000
user bluetooth
group bluetooth net_bt_admin
disabled

Obviously you need to remount /system rw to do this.

This tells the bluetooth fw loader to switch to 4Mbps after it has started.

You will need to reboot after changing this line. Without the change BT will work, but it won't run at full speed.

To check that it's running at full speed look for the following in dmesg:

[ 570.196523] clk_set_rate 34:1843200

[ 570.196561] Setting the msm_serial_hs clock

[ 570.196586] Set clock PLL

[ 570.221271] clk_set_rate 34:64000000

[ 570.221333] Setting the msm_serial_hs clock

[ 570.221361] Set clock PLL

1843200 is low speed, 64000000 is high speed.

The reason it wasn't working before is that the clocks weren't set up correctly and also there seems to be a problem with the hardware because it never sends a TX_READY interrupt. I worked around it by using the TXLEV interrupt instead.
[Touch CDMA Android Development] mrkite38:
I saw the commits last night! Awesome and thanks as usual.
[Touch CDMA Android Development] cp0020:
Hey dzo how do I do this? I have it flashed to my phone. Do I just put that in the terminal? The way you have it or all on one line? I really have no clue what to do. Thanks :)
[Touch CDMA Android Development] slm4996:
First get your current sysinit.rc from your phone /system/sysinit.rc

Assuming you don't have ADB setup and have astro file manager installed

on phone in terminal emulator:

cp /system/sysinit.rc /sdcard/sysinit.txt

Open astro and find and "Open in text editor" the sysinit.txt

Locate the lines dzo posted and make the changes

Bring up your menu and choose save

on phone in terminal emulator:

su
mount -o remount,rw /system
cp /sdcard/sysinit.txt /system/sysinit.rc
mount -o remount,ro /system

Then reboot
[Touch CDMA Android Development] bri3d:
New high-speed UART is working perfectly for me. Updated my init, saw the clock up, saw the "High speed" message, and stereo bluetooth is working as well as stereo bluetooth ever does on any device (so not great, but not skipping like it was before either).

It's definitely very CPU sensitive (as expected), I'm testing with Pandora and it's going fine as long as Pandora's all that's running but touching the CPU with any other app makes it cut out.
[Touch CDMA Android Development] cp0020:
thanks! :) now what should I do to see if its working? And what exactly does this do?
[Touch CDMA Android Development] polyrhythmic:
Ok, now I am even more jealous of you Vogue guys ;)

I've been talking with phh and others in #htc-linux, DIAM now has working BT in Eclair 2.1, I want to get into what it takes to get BT on Kaiser.

If I ls in /dev/ I don't see either ttyMSM0 or (what works for DIAM, ttyHS1), is that because the serial port doesn't get initialized in the kernel? During the beginning of boot I do see several messages about Bluetooth .

Please excuse my kernel-n00bishness here but I'd like to get the ball rolling. Kaisers have the same TI BT chip as these other devices, so how can I help?
[Touch CDMA Android Development] mrkite38:
try...

hciattach ttyMSM0 -s 115200 texas

in terminal and tell us what happens
[Touch CDMA Android Development] dzo:
Won't work on anything but vogue because the gpios aren't set up correctly.
[Touch CDMA Android Development] cp0020:
Hey everyone, i posted this on my tips/tricks thread but i found an app called root explorer. It gives you the option to mount/remount, edit texts, exc... its a hell of alot easier than better terminal
[Touch CDMA Android Development] cp0020:
Hey dzo i have an idea for the button layout. Power is power/wakeup, volume is volume, left d-pad is back, right d-pad is forward, up d-pad is menu, down d-pad to go home, center d-pad for something lol one tap camera goes to camera and long press camera goes to landscape. Is there anyway you could do that? Or is tjere anything i can edit to do this? Thanks! :)
[Touch CDMA Android Development] incubus26jc:
what buttons would navigate through the widgets and browser ect.. on screen? I dropped my phone once and my screen is messed up sometimes (Unresponsive) and screen taps do not work without tapping on the back of the phone to get the screen to be responsive again. I know this isnt a problem most people have but i would use dpad alot even if i didnt have this problem
[Touch CDMA Android Development] cp0020:
Your finger lol im not sure. I never use the d-pad so it would be good for me
[Touch CDMA Android Development] cp0020:
Oh. I dont know but i want my own button layout man lol i wonder if there working on a way to make our own button layout
[Touch CDMA Android Development] incubus26jc:
i seen from your sig lol. I kinda like having back as my camera because i hold the phone with my left hand and a simple squeeze of my palm is all i have to do. I didnt like it at firrst because i was used to windows mobile but after having it a few months, I wouldnt wanna go back now.
[Touch CDMA Android Development] ThomasHW:
I wouldn't mind messing around with the button layout, if it's possible.
[Touch CDMA Android Development] incubus26jc:
this is a quote from tatnai

Note: we do not currently have a button mapped to pull up the running applications, as we are short a few buttons on the vogue. the keylayout is modifiable, but you have to edit some of the system files, which is outside the scope of my knowledge. there was previously talk of making an application to allow end users to alter the keymap themselves, but this has not yet been completed.
[Touch CDMA Android Development] drewden123:
I would love a button layout as cp0020 described. That one seems to fit much better to me. For those who like the current one, maybe there could be separate androidupdate.tar's to change it, or i guess it would have to be separate kernel's (i.e. voguimg-240x320-buttonlayoutA-2-26-10) or something like that.
[Touch CDMA Android Development] cp0020:
Exactly right!!!! I know these guys are working there butts of and the last thing on there mind is to make a button layout for me. But i would love to have that button layout.
[Touch CDMA Android Development] jnadke:
How would you want the buttons?

The only thing I could see, is having the wake-up double-up as back, then having the camera button be the menu button. This I actually would like.

The d-pad needs to be the d-pad. Dpad center needs to be select. Talk and End need to be Talk and End. I like having end-call be power off, it just makes sense.

We could possibly add a kernel parameter that, like I said, swaps the functionality of the camera and top/power buttons. That's really about it as far as customizing you can do.
[Touch CDMA Android Development] cp0020:
It would be cool to have it like this. Power is power/ wakeup, volume is volume, left d-pad is back, right d-pad is forward, up d-pad is menu, down d-pad to go home, center d-pad for something lol one tap camera goes to camera and long press camera goes to landscape.
[Touch CDMA Android Development] incubus26jc:
it is impossible for that to work. you need a dpad and center button the way it is. Imagine what that layout would do for games like pacman ect...

Everything would be effected. You would constantly run into problems with this layout.

The only way i could see a change in layout would be like this

Power button for Power

Red end button for <-- back and hold it for home

Camera button for settings and landscape

Everything else the same
[Touch CDMA Android Development] berardi:
I personally love the way the buttons have been laid out, it's really grown on me. At first I was like ??? then I was like :)
[Touch CDMA Android Development] incubus26jc:
agreed. Dont change, they have grown on me too. but if we have to, what i wrote earlier would be the only way i would want to do it.

Power button for Power

Red end button for <-- back and hold it for home

Camera button for settings and landscape

Everything else the same
[Touch CDMA Android Development] drewden123:
I hardly use my dpad, it is very seldom. This is why there could be separate kernels or separate androidupdate tars. Then there would be a choice for those who use a dpad frequently and a choice for those who never do. The one cp0020 described would be perfect for those who never use a dpad
[Touch CDMA Android Development] cp0020:
That would be nice. I am pretty used to the current button layout but i would much prefer the way i said. But beggers cant be choosers.
[Touch CDMA Android Development] berardi:
I agree with you about the D-Pad, I don't use it much either, but I think a problem would be about the installer... need d-pad for that
[Touch CDMA Android Development] cp0020:
Not anymore. With the latest kernels/nbh they made the installer usable as a touch screen. So the screen is one big d-pad
[Touch CDMA Android Development] berardi:
oh nice didnt know that
[Touch CDMA Android Development] grktaurus83:
Just wanted to comment again on how great it is to have a more reliable battery reading and a much more consistent battery life. Now I realized that this issue ate away at me more than I thought it did.

Thanks Martin!
[Touch CDMA Android Development] berardi:
I'm having an issue with bluetooth with the update - often I have to turn bluetooth on and then off and on again to get a device that is already paired to actually connect after it's been dormant (like overnight).
[Touch CDMA Android Development] drkow19:
Thank you so much!!! I commented in a different thread how the newest kernel doesn't help my bluetooth, but I didn't know about this fix. Audio is streaming to my little BT boombox without any delay!!! Love it.
[Touch CDMA Android Development] mrkite38:
dzo - I produced some nbh files with the system and data partition sizes reversed so I could squeeze hero in... seems to be working ok so far but I was wondering what the partition_layout file is / does and if it needs to be modified to match?
[Touch CDMA Android Development] dzo:
No, the partition layout file is just to keep the spl happy and think it's loading a very small imgfs. You can make the system and data partitions any size you like. Make sure people know this will wipe their data though.
[Touch CDMA Android Development] moekind:
Dzo any development on the call waiting issue?

Switching between calls doesn't work, and the caller id

freezes to the last person that called you, assuming you didn't pick up.
[Touch CDMA Android Development] cmus:
Hey dzo,

the most recent NBH files on your page are all for vogue. Are there updates in the 2-26 versions that are pertinent to Kaiser users? Are other Kaiser users out there still using the 2-15 or 2-20 versions on sourceforge?

Thanks for all your work...
[Touch CDMA Android Development] mrkite38:
Thank you. I don't plan on sharing at this point. ;) And the symlink to /data/app_s has been a good workaround, so it's not really necessary. Just messing around.
[Touch CDMA Android Development] polyrhythmic:
From the Kaiser forum:

I would like to add this in to our kernel ASAP... I've just never compiled a kernel before. Any volunteers?
[Touch CDMA Android Development] incubus26jc:
if they feel it will solve the problem, they will put it in. No need to try and do it. Just wait and see what they say. They always do it ASAP:)