yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] mr_dinosaur:
I tried doing the same thing, I am sitting at a desk near a window and found that the GPS was having a hard time locating me. So, I downloaded and flashed RIL module patch for our specific radio version and rebooted. The GPS found me in about 5 seconds.

Try flashing the attached after doing a nandroid backup and see if it helps.

Edit:

I decided to test again after flashing the RIL modules still sitting at the same place near a window and it's been 5 minutes and counting and the GPS is still trying to find me. Oh well... maybe it'll work for you
[Desire Android Development] RedSkyRoad:
Tried flashing : Got the following error message - "Wrong digest : system/lib/libhtc_ril.so... Verification Failed"

Where can I get the latest stand-alone Radio for Desire?
[Desire Android Development] lazarost:
For fast GPS locking try the GPS status app on the market.

Do a "Clear A-GPS State" and "Download A-GPS assistance" and with enough view of the sky you should be locking 8/10 satellites within seconds.

The most important thing is to have an active internet connection to download the assistance files, makes a world of difference whatever the radio in use.

Edit: I also noticed that it helps when you have enabled the location service through the wireless networks.
[Desire Android Development] mad-murdock:
the current kernel seams perfect!

no screen tearing, no lagging. i listend to music about 30 minutes this morning (f'ing snow shoveling :), used the phone after this and everything seams stable, smooth and fast. anyone got some issue with 201?
[Desire Android Development] bemymonkey:
Working well here.

Updated WiFi module is in sig, in case anyone needs it :)

-edit- Is it normal that a little bit of snow (not that much, it's just coming down normally) has a huge impact on GPS performance? Taking ages to get a fix indoors (usually takes about 10 seconds where the phone is right now, and when I put it on my desk, where it usually gets a fix after about 40-60 seconds, GPS Status can't see a single satellite :eek:)...
[Desire Android Development] mad-murdock:
can you explain what those wifi modules are about? never noticed them, since i usually read this forum with tapatalk and dont see signatures
[Desire Android Development] lazarost:
Cloudy weather indeed has a huge impact on the GPS performance. GPS needs as clear sky as it can get to work properly.
[Desire Android Development] mad-murdock:
random kernel reboot

this one is different from the random reboots i reported before with 2.6.35.7 - but it just happend

i was playing a 2d tower defence game when it happend, but that probably doesn't matter

[ 3369.407257] binder: 243:1415 transaction failed 29201, size 225260-4
[ 3377.410980] STA disconnect received 6
[ 3378.541870] STA connect received 1
[ 3383.867584] ALS value: 0x0, level: 0 #
[ 3385.917694] ALS value: 0x4, level: 2 #
[ 3390.553680] ARM9 has CRASHED
[ 3390.553863] smem: DIAG '[WCDMA] 09:22:23 FATAL: DOG (SM-TM:00000) (0)
[ 3390.553863] '
[ 3390.554168]
[ 3390.554290] Restarting Linux version 2.6.35.9-cyanogenmod (chrissoyars@fembot) (gcc version 4.4.0 (GCC) ) #2 PREEMPT Thu Dec 2 03:07:50 UTC 2010

full last_kmsg attached
[Desire Android Development] cTrox:
Does that mean, I don't have to use Vorkkernel to make it smooth anymore?
[Desire Android Development] mad-murdock:
yes! use cyanogen kernel from build 201+

tearing fixed, lag issues fixed. kali did great work. and cyanogen works best with cyanogen kernel (:
[Desire Android Development] Kali-:
thank's for your patience

credit goes to cyanogen for point me into the right place
[Desire Android Development] terryhau:
Normally, when screen goes off, wifi speed drops to something very low like 1kB/s.

The modded wifi module lets it go at full speed with the screen off.
[Desire Android Development] terryhau:
Thanks.

Gonna try the new nightly/kernel.
[Desire Android Development] mr_dinosaur:
You need to disable verification from recovery but it looks like lazarost posted a pretty good solution just after your post. Try his solution first.
[Desire Android Development] mr_dinosaur:
Seems as good as it's ever been but only with launcherpro. ADW still lags though.
[Desire Android Development] bemymonkey:
Correct. Also, latency skyrockets when the screen goes off, making things like VoIP apps (SIP baby!) unusable.

OK, then I guess things should be fine. 5 satellites at the window after ~30 seconds should be alright for snowy & cloudy weather, right? :)
[Desire Android Development] cTrox:
Awesome!

Updating it tonight.
[Desire Android Development] RedSkyRoad:
If i download the latest radio, do i just put in on the sd card and flash zip from recovery?
[Desire Android Development] sjgore:
Yes, but it's safer to do it via fastboot.
[Desire Android Development] sjgore:
I don't understand this, because when I'm downloading a large file (such as the nightly builds, for example) I start the download and then switch the screen off. A few minutes later, the download has completed. Download speed doesn't seem to be affected?
[Desire Android Development] lazarost:
You should be more than happy ;)
[Desire Android Development] guidojusto:
I'm having troubles regarding random reboots while testing Quadrant scores. Right now using SetCPU with the highest value and Performance mode. Anybody with the same issue?
[Desire Android Development] juanjo7812:
Latest build(#201) deleted my alarms. Is this "normal" ?
[Desire Android Development] bemymonkey:
Interesting, mine are gone too. Thanks for the heads-up!
[Desire Android Development] juanjo7812:
With SetCPU with highest value I always got random reboots. Just put high slider to 1075200 (instead 1113600) and no more reboots.
[Desire Android Development] fenderf4i:
Fantastic work on the kernel Kali. Keep it up, we appreciate it!
[Desire Android Development] marinierb:
Indeed! Big thanks!
[Desire Android Development] fenderf4i:
Something a friend noticed is that when you set a lockscreen gesture to link directly to a contact, it initiates a force close when you try it. She's on an EVO, and it happens on my Desire also when I try it.
[Desire Android Development] mad-murdock:
if you got AMOLED and your phone gets pretty warm while doing quadrant, you probably got one of the first phone revisions, which reset in overheating. worst thing: this happens more and more often until you cannot do anything but unroot and send to customer support for exchange of mainboard.

friend of mine had this problems - and your description sounds a bit like it

if thats not your problem, then the cpu cant stand 1118mhz. not all cpu's are the same. some can go further, others cannot. mine runs just great with 1152.
[Desire Android Development] guidojusto:
I'm not sure at all if it is my CPU or if it is an issue related to CyanogenMod kernel, because until now (201 Nightly) I was using vorkKernel (19 November release) pushing the CPU at 1152 Mhz value and not issues at all. Strangely, issues started with 201 Nightly. Now I'm trying the recent release of vorkKernel (2 December with the tearing issue fixed for SLCD) and also, not issues at all pushing the CPU further than what I used to do with 201 Nightly.

(My device is an SLCD HTC Desire so i do not think it is an issue regarding with the first revision of the phone, also it does not even get warm when I do the test)

Just for the record, all the test I'm running on the device, they are performed in Performance mode on SetCPU.

Thanks for answering.
[Desire Android Development] mad-murdock:
i also got a slcd desire (pvt3), did a quadrant at 1118 performance settings, no reboot at all - ran it twice
[Desire Android Development] marinierb:
High Battery Drain

I installed 201 last night and experienced pretty high battery drain today. When I got back from work I had 30% left on my battery. Usually, it's at 80% after about 10 hours. So I've got 7% per hour instead of the usual 2% per hour. The phone is much warmer than usual, too.

I don't know at which build the battery drain started for me, but pretty much every build I tried in the last few weeks is bad.

So I'm going back to build 170 again. That one works well for me.

:(
[Desire Android Development] cTrox:
Something I noticed in a few nightly builds, my USB to SD card write speed is extremely slow. I just got about 600kb/s with a class 10 (!) 16GB SD. Can someone confirm that?

Oh and with the App "SD Card Speed Test" I have about 4MB/s write speed and 12MB/s read. It isn't that fast either but much better than with Computer to SD.
[Desire Android Development] ziggy1001:
Are you sure it's not something running on your phone? i'm on 197 now and have used most but not all of the last few weeks of nightly builds and standby/light use they virtually all give me <1% an hour drain
[Desire Android Development] marinierb:
I'm sure. I have the same apps, same settings, etc. As a matter of fact, I can flash back and forth, no wipe, and 170 is always good and the others bad.
[Desire Android Development] mad-murdock:
i "benchmark" battery stuff at nights with juice plotter. sync, wifi, 3g off, so no data communication.

best i ever had was 1% in 2 hours... the last test a few days back with vork was 1% in 1 hour. will test tonight, if i dont forget it...

right now, i have about 6% an hour, with wifi policy always on and some push clients in the background (k9 with 5 minutes interval, pingchat, tapatalk checking forum pm's regularly and probably more which uses my internetz) - i think, thats okay with that high usage...

also, marinierb, which govonor did you use? different govenors set with setCPU can have impact on battery drain
[Desire Android Development] marinierb:
I have BlueTooth and WiFi on all the time, with WiFi sleep policy set to "Never when plugged in". I also use the CPU defaults (998/245 ondemand). I don't use SetCPU at all. With build 170, I get about 2% per hour battery drain. More recent builds are not very good. Exact same settings all around.
[Desire Android Development] rdgate:
I have the problem that looks like.:(

Wifi sleep policy set to "When screen turns off". Wifi connected and go to sleep, (I think this means both 3G data and Wifi sleep)

recent nightly: 4~5%/h (40~50mA by CurrentWidget)
build #180 : <1%/h (2~6mA)
recent nightly + recent vorkKernel: 4~5%/h (40~50mA)
recent nightly + r8 vorkKernel : <1%/h (2~6mA)
[Desire Android Development] bemymonkey:
@marienrb: You should try a wiped install of the latest nightlies. I'm getting 4-5mA of standby battery drain with WiFi and Bluetooth on... might be your settings or your apps.
[Desire Android Development] mad-murdock:
i just did my murdock-standarized-test (: i had 3% in 5,5 hours with all turned off - thats the best it can get. build 201 that was.

if you got wifi to "never when plugged in", it will switch off (including bt) some minutes after screen turned off. the 6% i discribed yesterday were with wifi on all the time - since i use my phone for informing me about important stuff while i use my pc.

yet pretty interesting you get so much other results than i do with same build (201)

OMG - no nightly build today for us. guess build-botty found an error in the sources!?!

edit: after i read bemy's reply, he might be right. perhaps its some settings which you cannot import from 170 to 201 - wipe, fresh install and titanium restore apps (not settings) might give a clue
[Desire Android Development] marinierb:
Did that already.
[Desire Android Development] Roscopcoletrain:
wish I got 2% per hour lol. its been about 2hrs since I took it off the charger and Im at 89% now. and its sat for probably 1.5hrs of that. Standby, phone is great, but using it, it drops fassst. The other day I went out with some buds. So of course I had to show off a few things. I got 7hrs out it. ouch. Thank you spare battery lol.
[Desire Android Development] X-dark:
Where do you set this ?
[Desire Android Development] ziggy1001:
Settings....Wireless & networks.......Wifi settings (press menu button) select Advanced..... Wifi sleep policy 3 options;)
[Desire Android Development] Roscopcoletrain:
Curious, if you're trying to conserve data, you'd want to leave wifi on all the time no?
[Desire Android Development] ziggy1001:
Yeah never really tested it out but my subjective impression is wifi uses far less juice than 3G

Whoops you were talking about data:o
[Desire Android Development] terryhau:
Same thing here.
[Desire Android Development] mad-murdock:
never do battery measuring above 90% - or even better 85%... if your battery isnt absolutly precisely calibrated, thats the area which will not be very accurate
[Desire Android Development] mad-murdock:
me haz made theme forz nighltyz 201:

http://xdaforums.com/showpost.php?p=9564846&postcount=69

lookz sweetz - me likez the dialogz animazionz - creditz go to sonnysekhonz and djdarknight96z

peaze
[Desire Android Development] Roscopcoletrain:
Yeah, it wont much matter. It drops fast regardless ;) Im at 54% now (1:24pm) and have been off the charger since about 6am. Ive used the device for about 45min total lol. And thats just small spurts here in there. The rest its just sitting there.

I know what you're saying though.
[Desire Android Development] cTrox:
Can anyone confirm this?
[Desire Android Development] RedSkyRoad:
Hey :)

So, I got 201 and downloaded the FROST theme... How do I apply it?
[Desire Android Development] worstenbrood:
That theme looks sweet man ! Thx. Wish we had a theming system like miui, flashed 203 now and i'm to lazy to replace all the stuff in framework-res
[Desire Android Development] adancau:
Quick question: will the jump at the end of a list when scrolling without lifting your finger with overscrolling enabled be fixed? 203 and it's still there, unfortunately. and it's very annoying when reading something and you basically scroll the article slowly.
[Desire Android Development] mad-murdock:
It sure will be fixed. Over scrolling got some more problems. Miui over scrolling is perfect. Lets just wait until some dev got the time to fix this...

Swyped with HTC Desire. Excuse typos.
[Desire Android Development] guidojusto:
Right now testing 203 Nightly and i'm having issues with SMS/MMS ringtone. I have chosen Heaven as the ringtone for this application and each time I recive a message the sound from the speaker will sound satured. This does not happen on 201 or earlier versions.

I also tried to lower ringtone sound, but this does not help either. It is like the sound skips half a second or less in the middle of the ringtone.

Does anybody noticed the same issue?
[Desire Android Development] Roscopcoletrain:
Hmm had two random reboots tonight. On 201. Just outta the blue. Will try an updated nightly.
[Desire Android Development] adancau:
205: items in the notification list are oversized vertically
[Desire Android Development] unattached:
hello, got a problem since installing rc2 over rc1, also using the latest nightly didnt fix it: loosing data connection almost every time the phone goes to sleep. it always shows the hsdpa upload notification, but never 3g and download doesn't happen.. any help or do i have to wipe?
[Desire Android Development] bemymonkey:
Ummm... wha? Nothing here... Screenshot?

-edit- Damn, just had a spontaneous reboot on nightly 205. Back to 201, I guess :(
[Desire Android Development] worstenbrood:
Np here, try to reset ui tweaks to default in cyanogenmod, had the same problem before and that fixed it.
[Desire Android Development] adancau:
Thanks, that did the trick :)
[Desire Android Development] mad-murdock:
Do you have / can you upload the /proc/last_kmsg file? I am still pretty interested in random reboot an this file contains the reason... Until you reboot again :)

Swyped with HTC Desire. Excuse typos.
[Desire Android Development] bemymonkey:
I was in a hurry so didn't get the file, but the last time I tried, I couldn't find a last_kmsg in /proc... is there a trick to that?
[Desire Android Development] mad-murdock:
No trick at all. It's always there, even when you do a normal reboot. Don't know about flashing new/different kernels, but right now it's here for me like usual. Last reboot was to flash 205

Swyped with HTC Desire. Excuse typos.
[Desire Android Development] sjgore:
I'm getting strange charging behaviour from 195 onwards. If I charge the phone without using it whilst charging, it gets to 100% as normal. If I use the phone whilst charging, it jumps to 100% from whatever it's at when I start using it.

Just now, it was at 89% when I unlocked it. Within a few seconds, it had jumped to 100% and stopped charging. Yesterday, it jumped from 93% to 100% in the same way. Interestingly, when the charge dropped to 15% earlier today, I got the low battery warning message as usual, but then it powered down just a few seconds later, like it usually does at about 8%.

So something's not right. Anybody else get this?
[Desire Android Development] bemymonkey:
Crap, I just had another reboot. Got the last_kmsg this time:

http://www.multiupload.com/6Y4ZM8SIRC

:(

This part looks to be relevant:

[46264.383727] suspend: enter suspend
[46264.383850] PM: Syncing filesystems ... done.
[46264.385131] Freezing user space processes ... (elapsed 0.01 seconds) done.
[46264.400634] Freezing remaining freezable tasks ...
[46264.400970] active wake lock wlan_wake
[46264.401306]
[46264.401428] Freezing of tasks aborted
[46264.401946]
[46264.402069] Restarting tasks ... done.
[46264.408233] suspend: exit suspend, ret = -16 (2010-12-05 16:25:49.935347560 UTC)
[46264.408477] active wake lock wlan_wake
[46264.408599] suspend: abort suspend
[46265.410766] wake lock wlan_rx_wake, expired
[46265.414001] suspend: enter suspend
[46265.414428] PM: Syncing filesystems ... done.
[46265.418121] Freezing user space processes ... (elapsed 0.03 seconds) done.
[46265.452545] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[46265.473663] msm_pm_wait_state(1, 0, 0, 0) failed 11004
[46265.662628] ARM9 has CRASHED
[46265.663085] smem: DIAG '[WCDMA] 16:25:51 FATAL: DOG (SM-TM:00000) (0)
[46265.663116] '
[46265.663879]
[46265.664581] Restarting Linux version 2.6.35.9-cyanogenmod (chrissoyars@fembot) (gcc version 4.4.0 (GCC) ) #2 PREEMPT Thu Dec 2 03:07:50 UTC 2010
[46265.664642]

No errors detected
[Desire Android Development] Kali-:
try to revert to stock bcm modules
[Desire Android Development] bemymonkey:
Will do. Any idea why that could be causing it?
[Desire Android Development] :
Google Sign-in show enter password every time when i reboot.

What to do not let it show ?
[Desire Android Development] mad-murdock:
Doesn't for me. Did you try a fresh install?

Swyped with HTC Desire. Excuse typos.
[Desire Android Development] mcampbellsmith:
Reboot today while looking at Google Maps... running 207.

What logs should I get for debugging? /proc/last_kmsg ?
[Desire Android Development] ziggy1001:
HOW TO REPORT BUGS OR PROBLEMS?

- Was it a hard reboot? Go into recovery and dump the "/proc/last_kmsg" file.

- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get send the full output.

- Pastebin links preferred

- Please use the issue tracker whenever possible!
[Desire Android Development] mcampbellsmith:
It was a hard reboot while viewing Google Maps version nightly 207

last_kmsg, extracted with adb, here: http://pastebin.com/TAv4Pahe

Extract:

[ 7766.592468] capella_cm3602_ioctl cmd 1

[ 7766.592590] lightsensor_ioctl get enabled status: 1

[ 7813.330535] batt: 33%, 3684 mV, -480 mA (-445 avg), 36.8 C, 456 mAh

[ 7826.549987] kernel BUG at /home/chrissoyars/slave/cm6/build/kernel-msm/mm/slab.c:498!

[ 7826.550201] Unable to handle kernel NULL pointer dereference at virtual address 00000000

[ 7826.550384] pgd = daab8000

[ 7826.550506] [00000000] *pgd=3b3cf031, *pte=00000000, *ppte=00000000

[ 7826.550903] Internal error: Oops: 817 [#1] PREEMPT

[ 7826.551116] last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

[ 7826.551208] Modules linked in: ipv6 [last unloaded: bcm4329]

[ 7826.551727] CPU: 0 Not tainted (2.6.35.9-cyanogenmod #8)

[ 7826.551849] PC is at __bug+0x20/0x2c

[ 7826.552032] LR is at release_console_sem+0x1c8/0x240

[ 7826.552154] pc : [<c002a718>] lr : [<c005bc90>] psr: 60000093

[ 7826.552154] sp : dab51de0 ip : dab51cf8 fp : dab51dec

[ 7826.552459] r10: 48383000 r9 : dab50000 r8 : c0027104

[ 7826.552642] r7 : a0000013 r6 : d50047e0 r5 : 00000010 r4 : d5fe57c0

[ 7826.552764] r3 : 00000000 r2 : 00000000 r1 : dab51cf8 r0 : 0000005f

[ 7826.552947] Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user

[ 7826.553070] Control: 10c5787d Table: 3aab8019 DAC: 00000015
[Desire Android Development] Murd0ck:
If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
[Desire Android Development] X-dark:
Thanks, never noticed the menu button was of use there.
[Desire Android Development] ziggy1001:
Whoops sorry copy and pasted that without fully reading it:o
[Desire Android Development] wgery:
Unlocking problem

Im on build#207

if I lock the phone with power and after a while I press power and I slide it to unlock it always opens an app automatically (e.g.: facebook,3g watchdog or whatever) this means when I slide it to unlock it won't drop me to the HOME SCREEN.

When I lock the phone I'm always close or kill those apps.
[Desire Android Development] jsel:
Seems like you've put some lock screen gestures on your phone.
[Desire Android Development] mad-murdock:
just read your last_kmsg file, and its the same thing i called "random reboot", reported on issue tracker and was thinking to be gone with 2.6.35.9 - but its not.... seams i was just lucky not to run into this reboot.

if you have out of the blue "kernel bug in /blah/blupp/slap.c", then its the random reboot which terrorizes some (not all) people for quite a while now
[Desire Android Development] mad-murdock:
to the guys who experienced android 2.1->2.2 update.

how did cyanogen handle the os-release update last time? since 6.1 final is out now, can we expect to be nightlies android 2.3 soon, or will the source be forked and it takes a while until a new stable build with 2.3 makes its way into nightlies?

please share your experiences from last time, when this happend (:
[Desire Android Development] wgery:
I'm interested in that too so please share the infromation with us:P
[Desire Android Development] bemymonkey:
Very good question, I can't wait to get a CyanogenMod nightly with all the new Gingerbread features (especially SIP VoIP! :D) :)
[Desire Android Development] fenderf4i:
2.3 source needs to be released before they can even start thinking about building it.
[Desire Android Development] bemymonkey:
When was the 2.2 source released? With the SDK or with the N1 OTA?

-edit- Looks like there was a while between SDK and source release:

http://www.slashgear.com/google-release-android-2-2-froyo-sdk-for-devs-2086468/

http://phandroid.com/2010/06/23/froyo-source-code-released-to-developer-community/

:(
[Desire Android Development] mad-murdock:
I didn't know, sdk and source are two different release dates. So right now, only phone manufacturers and the nexus one guys have any advantages from the new version? All the rest of us can only "enjoy"the emulator...

Swyped with HTC Desire. Excuse typos.
[Desire Android Development] bemymonkey:
It seems that a few of the new features (the SIP stuff, for instance) are missing from the emulator... so I guess playing around with that isn't going to be very satisfying :(

New UI looks nice though...
[Desire Android Development] typhex:
i cant download any nightly... is there a problem with the servers?
[Desire Android Development] sjgore:
Post deleted, wrong thread!

Sorry!
[Desire Android Development] sjgore:
Just out of interest, although there have now been 3 nightly builds since 6.1.0 stable, have there been any changes/fixes, or is the build bot just merrily compiling away to itself every night?

I'm wondering if the ear-bleeding high call volume has been fixed, or if the recent high battery usage (as discussed in the stable thread) has been fixed?