yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] tatnai:
dzo, your update really increased my battery life to a whole new level. I now have the battery life I used to have running NFSFANs ROMs - all day minimal use (10-15 texts) from 6am, still have battery in the 70s at 9pm. thanks for this.

as far as the full market goes, I have been running 240x320 for probably a month now with full market without refreshing my google account by flashing back to 320x480. a few releases ago, plemen made a "full market" donut evolution rom with some wacky settings in build.prop that broke google voice; I happened to refresh my google account using that build.prop (backed up my old data.img, created a new data.img at 320x480 with it and signed into the market, then returned to my old data.img at 240x320). I've been running a couple of other ROMs since, and I've used the market at least every other day since then, and I have ALL apps present still with the same old data.img at 240x320. I don't know if the build.prop was the only thing that was different, and I don't know why it works, but I won't be getting rid of this data.img anytime soon.
[Touch CDMA Android Development] gedster314:
I don't if this is the thread to post in or not. It is Kernel related but may need to be in another thread.

I downloaded the Vogue kernel, dated 3-8-10, from here:

http://it029000.massey.ac.nz/vogue/files/?C=M;O=D

I just want to report that I am occasionally getting sdcard errors but then the Android has no issues retrieving information from the sdcard. Someone else reported the same issue. I can't find the particular thread now, I'm hoping it was in this thread. I just wanted to report; me too. Is there anything you want to look at when it happens again?

I will probably roll back to the previous kernel. I will say that this kernel does seem to do a lot better on battery life but then it has been a lite day on phone usage.
[Touch CDMA Android Development] tatnai:
after running the 3-8 .nbh for about 36h, it started not accessing my SD card properly. It could see stuff on it (say in astro), but listed all files and folders' names as strange characters (as boxes with ? in between, no letters). could not play media or alarms. in settings > sdcard, it showed it as still mounted. rebooting quickly fixed this. any log I can get you if this happens again? thx dzo.
[Touch CDMA Android Development] Brad_J:
Regarding the reboot issue in airplane mode:

I had 4 flights yesterday. Each and every time I would turn on airplane mode when the door of the aircraft closed. About 20-30 minutes later the phone would reboot in my pocket.

Here is the error log for my phone, I hope it helps!

Note: On my last reboot, the phone was in airplane mode and I tried to open an application called Palmary weather.
[Touch CDMA Android Development] jnadke:
Perhaps it has to do with towers being unavailable when in Airplane mode (i.e., it's not truly going into Airplane mode). I put the device into airplane mode for well over an hour yesterday and it never reboot.

I have a metal locker here at work, I'll try sticking it in there....

Though, I don't think those fatal error messages are normal. If it's some kind of watchdog resetting the device, then it should do it after the same amount of time every time.
[Touch CDMA Android Development] srwalter:
[ 434.803088] msm_irq_exit_sleep1 smem=(40000 0) INT=(0 0) FIQ=(0 0) EN=(34181bf 7)

[ 434.803088] GPT Interrupt

[ 434.803138] Modem Status:

[ 434.803153] [MSM] FATAL_ERROR-T:DOG ,F:,L:0,R:0,SYSTIME: 10,03,09,03,50,09,-,20

[ 434.803281] ~w<6><SM 00000929 00010929>

That doesn't look good.
[Touch CDMA Android Development] timmey:
i have i small problem with my polaris. the phone turned off because the battery was empty, but when i pluged in the charger and turned the phone on again, it showed the battery as 100% charged. i can see in the log that it´s actually charging, but i can´t see it in the statusbar, on the logscreen or in the phone-statusmenu.

i´m running Myn’s Warm Donut build3 with zImage-08-03-10 from nand. (created my own polaris nbh to update the kernel)
[Touch CDMA Android Development] manu33xtro:
Hi, I have me too a Polaris... I use it with the Polyrhytmic build -> very good :) with the latest nbh of DZO for Pola (320*480) with 140 for lcd.density.

Can you post your nbh to update the kernel ? Because all of DZO nbh are for Vogue only :o.

Thanks if you can or help to make one ...

Cheers.
[Touch CDMA Android Development] polyrhythmic:
Hi dzo,

BT is working on Kaiser (regular, not high-speed of course), thanks again!!!! I was able to pair with my desktop and send a file.

I'd also like to report that soft-reset works better than it used to, it actually boots from a soft reset but I get a ton of these errors throughout boot:

msm_i2c: IRQ but nothing to do!

I have a couple questions, if you get the time to answer them ;):

Since Polaris is also MSM7200, should BT work for Polaris as well?

I see that clock-scaling was disabled by default in the recent updates, can I enable it to get better battery life?

I've been running a 528Mhz overclock for days with the SF 20-Feb build, and haven't had any clock-related problems (that I can tell).
[Touch CDMA Android Development] dzo:
I just got high speed working on kaiser and soft reset should be fixed now too.

BT probably won't work on polaris because the gpios will be different. Shouldn't be hard to fix. Clock scaling doesn't help battery life at all, definitely not on vogue anyway. Overclocking should still be enabled in recent kernels.

New kaiser and vogue NBHs are on my site.
[Touch CDMA Android Development] dzo:
I just fixed the wired headset for vogue, the mic works now and you can plug it in during a call.

New NBHs and zImage on my site.
[Touch CDMA Android Development] inertone:
dzo youre the best!
[Touch CDMA Android Development] JM-PDA:
Dzo,

Thank you for this and everything you do!!!
[Touch CDMA Android Development] JM-PDA:
Dzo,

Just tested and confirmed that your "vogue headset, mic fix" works perfectly.

Thank you!
[Touch CDMA Android Development] manu33xtro:
Hi DZO,

Very good work and thanks for time spent :)

I hope you can make a new nbh for Polaris to fix BT works for us... We wait for ;)

Thanks again.

Cheers.
[Touch CDMA Android Development] *M*:
Do you not get freezes when coming out of sleep?, I get this with the vogue when overclocking.
[Touch CDMA Android Development] sshark:
Mssmison has a kernel specifically for NBH is his new Eclair thread.

What are difference in code-base and do you guys plan to merge them in sometime soon in future. Because I want HW3D for Eclair that Mssmison has and also would like all enhancements that DZO has been making!

BTW, last couple of months have been really phenomenal for this project! Thanks to everyone!
[Touch CDMA Android Development] jnadke:
The kernel msmission posted is (likely) from dzo. There is only one kernel repository. HW3D works on these kernels that dzo posts. It has since January. Works on Myn's Donut too.
[Touch CDMA Android Development] mssmison:
Yup, we all work on the same kernel base. The difference with DZO's and mine is just that mine is the eclair version. (set in the config). I'll have an update out today with the latest patches.

It would be great though (and I know you don't use it yet) DZO if you could build the eclair HW3D kernel at the same time as the donut ones? I think it's great when everyone has a central repository to get the new kernels from?
[Touch CDMA Android Development] bri3d:
That makes sense since the clock rate is applied when you come out of sleep. Your hardware probably just doesn't overclock as well - mine is stable at 528 but I bet plenty of people's hardware isn't.
[Touch CDMA Android Development] *M*:
Yea the thing is though it can operate @ 590 for like an hour at max cpu load fine, then when if I sleep > wake if freezes after a second.

528 does not exibit this problem though so I guess its a stability issue.
[Touch CDMA Android Development] bri3d:
Are you sure it's actually operating at 590? It takes a full sleep -> resume cycle to set the new clock, not just updating the sys entry. 590 is a lot further than mine will go.
[Touch CDMA Android Development] acegolfer:
I just flashed with 3-11 NBH. It's not rebooting. I got white screen. Did I brick mine? What can I do?

I tried the boot loader and got the white screen, too.

EDIT: Could get the bootloader screen. Reverted it back to 3-4 NBH. Now it's booting. That was scary.
[Touch CDMA Android Development] bri3d:
Reflash from the boot ROM. It sounds like the open source bootloader got flashed but not the kernel. If you can't get into the boot ROM (the 3-color screen) you're well and truly bricked, but I *really* don't think that's possible with an Android NBH (it doesn't overwrite that part).
[Touch CDMA Android Development] acegolfer:
Thanks. Reflashed to 3-4 build.
[Touch CDMA Android Development] *M*:
I set it through the default.txt, and benchmarked it too so its definitely 590 stable until sleep/resume.
[Touch CDMA Android Development] acegolfer:
Which version? 8-3 or 11-3?

11-3 didn't boot. 8-3 killed my BT.
[Touch CDMA Android Development] mssmison:
removed, all squared away :)
[Touch CDMA Android Development] cmus:
Is there any place I can find a kaisimg-tilt-eclair-320 nbh file with the latest updates?

your progress is amazing dzo.
[Touch CDMA Android Development] cp0020:
I am having that problem where any button wakes up the phone. it use to be if you wait 10 seconds after putting it in sleep it wouldn't do that. but it was in sleep mode for over an hour and the camera button woke it up. using 3/12/10 nbh.
[Touch CDMA Android Development] Reddog80p:
I'm using the same dated NBH and only the power button wakes after 5 seconds. Are you running the eclair NBH or donut?
[Touch CDMA Android Development] cp0020:
donut .nbh
[Touch CDMA Android Development] sshark:
Partial wake lock has been addressed in both donut and eclair properly. From what I have known, partial wake lock issues are build-related. So I am going to call these two bugs as userland issues.

See which app has large partial wake lock time using the SpareParts app. and try uninstalling/clearing your /data/dalvik-cache and system/dalvik-cache (I don't remember exact location of system app's dalvik-cache).
[Touch CDMA Android Development] cp0020:
I had lockbot pro installed and that's what was causing the problem. stupid me :/
[Touch CDMA Android Development] polyrhythmic:
Hi dzo,

Thanks again, soft reset and highspeed BT are working great! (tested with file transfer, I don't have a working headset).

I do get this new error:

A N D R O I D
...
snd_set_device(1,1,1)
[RR] Error: no local ept for prog 02000031 but replying anyway!!

I assume this has to do with the headset audio and you might already know, but I thought it might help.
[Touch CDMA Android Development] osilvan:
Hi dzo

Thank you for your awesome work in kaiser last weeks. Kaiser and polaris are very similar devices, are you planning on improving also polaris kernel?
[Touch CDMA Android Development] sshark:
I saw that new files are uploaded to site with time stamp of 3/16. What changes were made, just curious?
[Touch CDMA Android Development] mrkite38:
Looks mostly like changes made by magister for titan.

Oh - also, something about iptables or netfilter, see that thread.
[Touch CDMA Android Development] mrkite38:
I was looking into a couple of random reboots and noticed:

[ 981.552164] Slept for 8 seconds
[ 981.552369] msmrtc_resume: alarm=1268677582, now=1268677582
[ 981.552392] msm_rtc: Generating alarm event (src 2)
[ 981.570442] SDCC Resume
[ 981.572134] Restarting tasks ... done.
[ 981.714239] android_power_suspend: exit suspend, ret = 0 (2010-03-15 18:26:22.639685000 UTC)
[ 981.720312] active wake lock android_alarm, time left 498
[ 981.780312] USB Disconnected
[ 981.786592] msm_hsusb_set_vbus_state(0)
[ 982.505842] Battery: ID=2 V=3797 Iin=0 Iout=153 T=4300 I=35 Vi=3832
[ 982.520389] Battery [204 70c e12 4 1b6] =, 58%
[ 982.567734] select 2613 (app_process), adj 14, size 3566, to kill
[ 982.580344] select 2820 (app_process), adj 14, size 3671, to kill
[ 982.590277] select 3031 (app_process), adj 14, size 3677, to kill
[ 982.600302] select 3076 (app_process), adj 15, size 3667, to kill
[ 982.610269] send sigkill to 3076 (app_process), adj 15, size 3667
[ 983.349361] save exit: isCheckpointed 1
[ 983.350454] android_power_suspend: enter suspend
[ 983.360274] PM: Syncing filesystems ... done.
[ 983.388201] Freezing user space processes ... (elapsed 0.00 seconds) done.
[ 983.394436] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
[ 983.395024] Suspending console(s)
[ 983.396189] TS Suspend
[ 983.396526] RTC Suspend: Current time=18:26:27
[ 983.397029] Wake up in 894 seconds
[ 983.397029] sleep_delay=0
[ 983.397029] msm_irq_exit_sleep1 smem=(0 0) INT=(0 0) FIQ=(0 0) EN=(34181bf 7)
[ 983.397029] Modem Status:
[ 983.397049] [MSM] FATAL_ERROR-T:HDRMC,F:HDRMC,L:110,R:0,SYSTIME: 10,03,15,14,25,00,-,28
[ 983.397179] [MSM] FATAL_ERROR-T:HDRRX,F:hdrmc.c,L:851,R:0,SYSTIME: 10,03,15,14,25,03,-,28
[ 983.397339] <SM 00000929 00010929>
[ 983.397403] Unexpected Timer interrupt
[ 983.397459] RTC Resume: Current time=18:26:39
[ 983.398656] Slept for 12 seconds
[ 983.398871] msmrtc_resume: alarm=1268678481, now=1268677599
[ 983.410286] SDCC Resume
[ 983.423476] Restarting tasks ... Battery: ID=2 V=3714 Iin=0 Iout=468 T=3800 I=123 Vi=3837
/[ 983.434821] Battery [1f7 6ff dc3 4 535] =, 59%
[ 983.449684] done.

It's the fatal error pieces caught my eye... does it mean anything to anybody:?
[Touch CDMA Android Development] wdbanks:
Im having a weird issue.

When talking on the phone I hear everything fine, but the person Im talking to complains of an echo coming from their own voice. I dont hear it. It doesnt happen when I have the phone on the winmo side - only when its booted on the Android side. I have partitioned my sd card and I am running Myns latest build. Any idea what could be causing this and how it can be fixed? It wasnt always like this.

Thanks
[Touch CDMA Android Development] jnadke:
Did you try turning the earpiece volume down (using the volume button)?

It's possible, if you have it loud enough, there could be feedback into the microphone (and if it's distorted enough the filtering algorithms may not remove all of the speaker feedback).

There are parameters for adjusting the various settings of the microphone sensitivity and earpiece volume range, however they are currently hard-coded into the kernel. I don't know when the parameters were last revised, but I don't have any issues.

Then again, I run my earpiece volume at the 50% mark (or below). Plenty loud for me.
[Touch CDMA Android Development] wdbanks:
This happens when I am not using a headset at all...Im stumped:mad:
[Touch CDMA Android Development] jnadke:
Not talking about headset. The earpiece (speaker) on the phone. Not speakerphone either. Turn the volume down on the regular old earpiece.

If that doesn't fix it, then its a network issue.
[Touch CDMA Android Development] polyrhythmic:
Speakerphone on Kaiser started working from the 13 Mar commits, nice surprise! Thanks again dzo.

Edit: Looks like there are more BT updates... looking forward to testing them.
[Touch CDMA Android Development] mssmison:
The BT updates are for eclair, not 100% yet but on the way for sure :)
[Touch CDMA Android Development] wdbanks:
Thanks for the tip. I tried it and I am still told by others that they are hearing themselves in an echo. Once again I dont hear it and I am not echoing either. Weird. I dont understand how it could be a network issue if it doesnt happen on winmo.
[Touch CDMA Android Development] manu33xtro:
Hi DZO,

just to tell you that your latest version of March 18 gives the same result (no sound) as my post for Poly http://xdaforums.com/showpost.php?p=5903573&postcount=2627

... Is there a difference with the eclair version? For I see you in vogue to do both ...

For cons, the bluetooth part works very well and is very fast : don't touch anything on this part :)

Thanks again for your work.

Cheers.
[Touch CDMA Android Development] loserskater:
So with the new kernels, we can just add hw3d.version= to our cmdline/tinboot in order to make them donut/eclair compatible correct? And I'm assuming hw3d.version=0 is donut and 1 is eclair? Just wanted to make sure, because if so it would make it MUCH easier for everybody.
[Touch CDMA Android Development] dzo:
Yes, exactly. Default is 0 so you only need to add it for eclair.
[Touch CDMA Android Development] jnadke:
Perhaps try upgrading to a 3.42.50 radio if you haven't:

http://forum.ppcgeeks.com/showpost.php?p=389964&postcount=8

That's what most everyone uses around here.

Edit: Dzo mentioned in Myn's thread he recently fixed it. Use a new zImage/NBH.
[Touch CDMA Android Development] loserskater:
Awesome! Makes life much easier. Thanks. And as always, great work!
[Touch CDMA Android Development] dzo:
I've fixed the bluetooth bug where, after playing a tone, the audio would be garbled. Took me all day to figure out what the problem was. I've also increased the size of the buffer that the high speed serial port uses which might help with some of the BT problems.
[Touch CDMA Android Development] manu33xtro:
Hi DZO,

Thanks for help for BT works better... But now it works perfectly for files transfert :) We wait for audio ;)

For users of Polaris, can you also make an eclair versions of nbh ?

Thanks again.

Cheers.
[Touch CDMA Android Development] xport:
Music actually played without skipping for a few minutes, but it dropped off.

Verizon XV6900 - Jaybird BT Headset
[Touch CDMA Android Development] JeckyllHavok:
Same for me, plays fine for aprox. 10 minutes and then it simply stops audio, but the player continues with playing
[Touch CDMA Android Development] berardi:
I've had about the same experience too. Glad it's not just me lol

On a separate issue I've been having some freeze / reboots lately. Should I check dmesg for error messages or the culprit?

EDIT: I'm on Myn's rls 4 if it matters.
[Touch CDMA Android Development] mrkite38:
Me, too. Been using mssmison's eclair 6a but I also has some on myn's with the new ril.
[Touch CDMA Android Development] xport:
sooooooo close, we are almost there!
[Touch CDMA Android Development] dzo:
Great, I just love bugs that only happen after 10 mins!!! I'll see if I can find a way to reliably trigger it.

If you ever get a freeze, soft reset and then get /proc/last_kmsg, it's the kernel messages from before the crash. Post it here with some info about what you were doing at the time if possible. If you look at it now it should still hold details of your last crash.
[Touch CDMA Android Development] berardi:
I've tried to observe when it happens, but can't really replicate the circumstances. In my experience it's been somewhat random (to my eyes at least). Sorry I know that makes it harder to go after =/ If there's anything I can check / try to help, let me know!

Ok I found the last_kmsg. What I should look for to indicate the reboot? I posted it if you need. One thing I've noticed is that the reboots tend to happen more often when I am actually NOT using the phone actively. A few times though, it's happened after something screwy has happened with bluetooth (like the BT device reports being connected, but the phone does not, or vice versa) Come to think of it, the majority of the reboots have been after messing with BT.

OOOO hmmm I noticed that "binder: BC_ATTEMPT_ACQUIRE not supported" kept popping up. I googled it and I saw some references to AD2P failures

http://www.google.com/search?num=10...ot+supported+ad2p&aq=f&aqi=&aql=&oq=&gs_rfai=

I'm not knowledgeable enough to determine what they're saying or the cause, but perhaps this is a lead? I have a theory I'm going to test on my car ride home today. :)
[Touch CDMA Android Development] berardi:
Ok so my hunch was that it might work better if connecting was initiated by the phone - but it failed! lol scratch that.
[Touch CDMA Android Development] dzo:
I've made another BT fix, this seems to stop it dropping for me, I've been playing a2dp for about 30mins now. Try the new NBHs or zImage from my site, they have the same name as those from this morning so just download again.

The problem was the interrupts as usual.
[Touch CDMA Android Development] xport:
well 90 minutes now and playing perfectly!

via music, and pandora

Bye Bye WinMo!

dzo, you are the man!

Ill keep playing and update here. :D
[Touch CDMA Android Development] Lintegras:
dzo,

I am currently bouncing around like a giddy little child, beating my head to some music, with a huge and stupid smirk that I can't wipe from my face.

Thank you so much for figuring out and remedying the AD2P issues. It's only been one song thus far, but I will be strapping up my running shoes and heading out for a jog now that I have my music back. Kudos, grats, thanks, huzzah!
[Touch CDMA Android Development] jkimod:
i updated my nbh to 3-26 and i still get choppy audio on music.
[Touch CDMA Android Development] acegolfer:
Did you do init.rc fix?
[Touch CDMA Android Development] jkimod:
i'm so sorry - i don't know how to do that. please advise.

edit: maybe i took the long way but the only way i could get get my edited sysinit.rc into my system folder was:

extracted out of tar w/ winrar, edited the file w/ notepad, put it into a tmp directory on my sd card, then used root explorer to copy and paste/replace into the system folder.

astra wouldn't save the edit/changes.

now BT audio for music sounds great. thank you thank you thank you !!!
[Touch CDMA Android Development] tatnai:
FYI the voguimg-240x320-eclair-26-03-10.nbh posted to sourceforge is actually 320x480 resolution.
[Touch CDMA Android Development] tatnai:
last_kmsg after one of the frequent freezes i've been having lately. this time was after enabling bluetooth (this situation is the only one that is reproducible). it has also occurred while using google nav, after turning on syncing, after a phone call. started after using mssmision v7, with 22-3-10 and 26/3/10 .nbh. don't know if it is userspace or kernel.

second kmsg associated with BT also; haven't gotten kmsg of random freezes that are not associated with BT yet.
[Touch CDMA Android Development] tylerwhall:
I wasn't able to get ADB to work on the Kaiser as of the 3-26 build. I've tracked it down to

f37753dbe5afe17254cb9e996e343a1ba1d1f461 - Use IRQ for polaris charge detection, still not working when fully charged.

I removed this change and it's working again.

- msm_proc_comm(PCOM_SET_USB_DPLUS,1); // set usb dplus=1
+ if(is_msm7500())
+ msm_proc_comm(PCOM_SET_USB_DPLUS,1); // set usb dplus=1

Just a heads up if anyone is having trouble.
[Touch CDMA Android Development] dzo:
This is with eclair I guess, I think eclair uses the bt drivers in a different way to donut and that's the problem. I made some changes to the ll drivers in commit 4b3bbf0d64f07f0ac3012b7d45d1d7dde7d403fd which probably aren't necessary, you could try reverting that entire commit and see if it makes a difference.
[Touch CDMA Android Development] tatnai:
sorry, yes, did not mention that this is with mssmison's eclair. I can't build kernel's right now, will probably roll back a couple of kernel builds for now.
[Touch CDMA Android Development] tatnai:
still mssmison's eclair, nand, eclair nbh from 26-3, apps2sd. kmsg from freeze unrelated to BT. was running google nav, it lost signal, I hit menu > exit and it did so appropriately, however the gps icon remained on. i check my astro process manager, and there was no navigation or gps process showing. made a phone call, worked fine, hung up. redialed again, and the phone froze; had to soft reset. no kernel panic in this one, I can't see what caused it to freeze.

going to switch back to 22-3 nbh and see if all my problems go away.
[Touch CDMA Android Development] kallt_kaffe:
I can confirm that reverting this change does make a difference. I can start bluetooth and see other bluetooth devices now. Haven't tried teaming up with anything but I assume that will work once I try it.