yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] cTrox:
I'm getting some freezes with 134. Yesterday I had my Desire Plugged-In to the USB and rebooted and after entering the pin-code it froze and I had to pull the battery. Later I wanted to start navigating, it froze. And it froze a third time, when I was in Layar (Agumented Reality App).

I can't reproduce it now that I got it plugged in to the PC and have logcat running.

Oh and once I had the wakeup-bug... :(

Edit: I just reproduced a freeze while I was in Layar. Here's my Log, I hope it helps somehow.

Edit2: I think this has to do with my GPS, had a crash in Maps Navigation:
[Desire Android Development] StuMcBill:
I don't really understand step 7. Do you adb shell and then type everything from the $ onwards?

Also, if I do this can I install roms normally from then on?

And can I easily go back to the standard partition table'd HBOOT?

Sent from my Amiga 500 using Workbench
[Desire Android Development] marinierb:
I believe for step 7 you can use the "wipe dalvik-cache" option from the recovery menu.
[Desire Android Development] X-dark:
Launch adb shell and type this:

for file in $(ls /cache/dalvik-cache/); do rm /data/dalvik-cache/$file; done;
[Desire Android Development] Kali-:
no "wipe cache" wipe /cache

step 7) remove duplicated entry on /data/dalvik-cache (~45MB)
[Desire Android Development] marinierb:
I'm sorry. I meant "advanced->Wipe Dalvik Cache" in ClockworkMod. That one definitely clears /data/dalvik-cache.
[Desire Android Development] fenderf4i:
We're already doing that in step 5. Step 7 clears something else out of the dalvik cache folder.

Edit: I had thought that clear cache also clears dalvik, but maybe not?
[Desire Android Development] Kali-:
but u have to reinstall all application if u do that

better to follow fenderf4i instruction if u dont want loose anything
[Desire Android Development] frocee:
the problem fixed itself somehow when i tried again, dunno what went wrong the first 3 times i tried that caused gapps not to work :/

thanks anyways :)
[Desire Android Development] df9517:
I will reply on my own post because now my phone is superstable again and I know what the problem is.

A few weeks back i got inspired and deleted a few apk's such as amazonmp3 using adb in recovery . I thought it was safe but that is actually the reason for my phone to crash and be unstable.

Sollution: just reinstall Google apps package.

Sorry for being a noob but perhaps this can help a few of you with same problem out!
[Desire Android Development] iinga:
I always remove apps i don't like and mine is perfectly stable. I think your issue may be somewhere else.
[Desire Android Development] df9517:
No its definately that, but I don't know which apk that actually caused it.
[Desire Android Development] iinga:
http://wiki.cyanogenmod.com/index.php?title=Barebones lists the apks that can safely be removed. Perhaps you accidentally removed an essential one.
[Desire Android Development] jayk32:
Can someone pls tell me the difference between CM6.0.2 & Nightly version? Currently I'm using CM6.0.2 on my Desire.

Thanks in advance :-)
[Desire Android Development] fridlack:
new nightly and noone say nothing... grrrr... cm_bravo_full-142.zip

http://mirror.teamdouche.net/?device=bravo

EDIT: Just instaled last nightly and camers is gone... i can see it in /system/app, but is not in the dragger... no camera app :(

EDIT2: flashed 135 again, camera is back :P
[Desire Android Development] MasterOSX:
Use the apk from the 135 waiting for a new nightly.
[Desire Android Development] Twau:
Same issue here. :-)

Sent from my HTC Desire
[Desire Android Development] Kali-:
http://github.com/CyanogenMod/android_vendor_cyanogen/blob/froyo/CHANGELOG.mkdn

this is linked in the first post of 6.0.2 thread
[Desire Android Development] fridlack:
I put the Camera.apk from 135 over 142, camera is back :P

Thanks for the tip

EDIT: the new toggles in notificatin bar looks amazing! hope you can fix the touch to focus new feature :)
[Desire Android Development] jayk32:
Thank you for fast response!!!!! :cool:
[Desire Android Development] bemymonkey:
This should work fine with any recovery, right? So I'd be perfectly fine with fine with AmonRA R5?

And does it play nice with Darktremor 2.7.5 RC1 (or was it RC3?) with a2sd cachesd?

-edit- Just tried it - works perfectly with Darktremor and AmonRA R5. :)
[Desire Android Development] Narfx:
Loving the new radio skin and the notification power widget :)
[Desire Android Development] fridlack:
Seens like coverage indicator is gone too... only the H/3g, battery and hour in my notification bar, no coverage streght indicator...
[Desire Android Development] Narfx:
Yep, I hadn't noticed it.
[Desire Android Development] typhex:
how can i replace camera.apk from 135 to 142?
[Desire Android Development] fridlack:
Seens its not my fault then, I flash back 135 and wait for new nightly :), great work in the new features
[Desire Android Development] mr_dinosaur:
Actually I haven't flashed the new build yet but one way to keep up with what changes are made is to follow CyanogenMod Source on twitter (http://twitter.com/#!/cmsrc). If you follow it, you'll see that the signal indicator is not really removed, it is just disabled if you have dBm enabled so I bet if you disable dBm, you get the signal indicator back. I am only guessing because I haven't flashed the new build yet, but that might be why you don't see the signal indicator.
[Desire Android Development] Kali-:
camera apk is on 142, but i didnt tested 142

anyway, i have built a newer one and this problem sames already fixed
[Desire Android Development] fridlack:
I dont have the "show dBm" option checked, never uses it, and no signal indicator, hope kali- will fix it in the next nightly
[Desire Android Development] Narfx:
No, I had the dBm indicator disabled and I didn't see anything besides the battery indicator and the clock.

I'll test 143 and see if it's solved. (edit) Nope, unsolved in 143.
[Desire Android Development] cTrox:
My Phone is always freezing, when in GPS after a few minutes. The Screen just freezes and stays on, the button lights too. I have experienced this in 135 and 142. Am I the only one?

I did a full wipe and I still got the problem...
[Desire Android Development] mr_dinosaur:
Ok just flashed the build 142 and I found out that if you go to Settings>>CyanogenMod Settings>>User Interface>>Status Bar and the tick the "Hide Signal Strength" checkbox, it actually brings back the Signal Strength icon on the notification bar hehehe. They got it the wrong way round lol.
[Desire Android Development] serverless:
Lovin' the new Galaxy S Style Power Widget in the status bar! Great addition, so niiice, even configurable!
[Desire Android Development] bemymonkey:
Screeny? :eek:
[Desire Android Development] frocee:
hahahahahaha, prolly a wrong number in the if() :D
[Desire Android Development] kevinye:
I didn't find dalvik.vm.dexopt-data-only=1 in the build.prop of 142 build.

Does it mean that we don't need do anything if we want to keep the n1 table after 142 build?
[Desire Android Development] mr_dinosaur:
Yup! I highly recommend if you're a CyanogenMod flash-a-holic like me to follow CyanogenMod Source at http://twitter.com/#!/cmsrc, that way you know what Kali- pushed to git or what other devs have changed or added so you know what to expect in the next build.

Dunno about you, but I always check Twitter on my phone to see what I may be getting in tomorrow's build.
[Desire Android Development] sookster54:
Just installed 143 and the pulldown widget is wicked. Only problem is the cell radio icon disappeared. :(
[Desire Android Development] bemymonkey:
For the love of God, someone post a screenshot before I faint! :p :D
[Desire Android Development] steve4130:
Well this is odd.

Ive been using CM nightlies since the early days of CM6 being ported to the Desire, and never had a problem.

Today I tried updating to build 142 and got stuck in a boot loop. Then I tried updating to build 143, and again got stuck in a boot loop. Then tried the older 135 build and everything is ok again!

Has something changed on the latest 2 builds (todays ones) that could cause this?

I always wipe everything between updates, so that shouldn't be causing any problems.

Oh, i'm still using the original partition sizes too.

Thanks for any help :)
[Desire Android Development] Ricky`:
With 143 i'm also getting boot loop. Here the logcat http://pastebin.com/P9KnexVD

Around line 1080 there is an exception and after it the loop restarts.
[Desire Android Development] sookster54:
LOL and the market is missing in 143.
[Desire Android Development] Kali-:
for user with boot loop in #142/143

reboot into recovery

wipe cache partition

adb shell

mount /system

echo "dalvik.vm.dexopt-data-only=1" >> /system/build.prop

umount /system
[Desire Android Development] serverless:
The screenshot of the new widgets in the notification bar is in the attachment.

By the way the 143 build screwed my call history, infact phone numbers are no longer associated with contact list.
[Desire Android Development] Ricky`:
Worked :) thanks Kali-

Did you install gapps?
[Desire Android Development] Twau:
Also have that problem with the contact list.

Sent from my HTC Desire
[Desire Android Development] serverless:
My market is still there, I have only the problem with the call history. I've just received a call, even when ringing it doesn't recognize the contact from the number anymore...maybe just me or anyone else has this annoyance?
[Desire Android Development] Narfx:
Mine works ok.

My main problem is that I can't modify framework-res.apk to my liking :(. I used to modify some pngs and xmls (for example, to show the battery percentage also WHILE CHARGING -it seems I'm the only one who likes to ALWAYS see the battery percentage and not some 5-frame animation-) but it seems apktool breaks something in the last framework-res.apk.

In fact if I simply do an apktool d followed by an apktool b (i.e., decompile and compile) and move the new .apk to the phone, I enter in a bootloop.

Does anyone know any other way to modify the .xml files in framework-res.apk?
[Desire Android Development] fridlack:
Same here, with "hide signal strenght" marked i see signal strenght :P

And call history died with 142/143 update, but works nice with new calls, and not having any problem with my contacts

Hope someone will find a way to fix the "if" error with signal strenght icon :P
[Desire Android Development] sookster54:
Yes other gapps was working, I'll reflash again and see what happens.

As for call history, how about wiping the history and seeing if new calls are working?
[Desire Android Development] sjgore:
I've just experienced "the" wake-up bug (takes several presses to wake-up and then the screen is unresponsive) for the first time

ever

with the 135 nightly. I've been using the nightlies since the middle of August and never experienced it before. The last few nightlies I used before this were 129, 122, and 09302010 (I flash about once a week). Nothing has changed on my phone for about the last month, no new apps, just the same ones.

Oh, and also:

CALL SCREEN GUI BUG

When I receive a call, the contact's number is displayed under their picture as it should be, but when I make a call, underneath the contact's picture it says "Slide to the right to answer" instead of the number that I have rung. I don't know when this started happening, only noticed it today.

Thanks!

Steve.
[Desire Android Development] bemymonkey:
Thanks guys. Looks cool :)

Are those customizable?
[Desire Android Development] serverless:
Already done with no success. Waiting for the next nightly to see if the problem will be solved
[Desire Android Development] serverless:
Yes, they are. You need to go to cyanogen prefs > user interface> widget buttons. However the widget is still a bit buggy, it sometimes disappears after pressing a button.
[Desire Android Development] cTrox:
Am I really the only one with GPS problems?

Maybe it's a Hardware defect.
[Desire Android Development] cinajohn:
Still getting boot loop even after following the above numerous times as well as wiping pretty much everything. Also tried doing the above from both a NANDroid backup of last stable CM and also right after trying to install 143 and getting boot loop.

Most recent ROM is 6.0.2. HBOOT .80 Clockwork 2.5.0.7 [S-ON]

Any ideas? Thanks

EDIT: I have sorted this. I was reflashing rom after doing the above, tried just booting after and all was happy. Thanks
[Desire Android Development] adancau:
build 143 works perfectly after following the instructions from here:

http://xdaforums.com/showthread.php?t=806321
[Desire Android Development] Amber-Willow:
I'm loving this latest rom, after fixing the dalvik cache problem

there's just one thing, my home button doesn't seem to be working anymore, and the dBM indicator is gone as well (the G/3G/H indicator DOES work, and i can still call.. its just not shown).

both are pretty minor things as far as i'm concerned, did anyone else run into this as well though?
[Desire Android Development] adancau:
Show dBM doesn't work for me either (just tried enabling it), but at the moment i'm connected to my wifi so i'm not sure if it should display it. I've never used it so far so I don't know if it should show when wifi is connected or not.

My home button works as well, though I'm not using ADW Launcher, I've switched to Launcher Pro. But long press home works as expected.

I've done a clean install however, after resizing my partitions as per the instructions here http://xdaforums.com/showthread.php?t=806321

I've used 110MB for /system (I usually remove a lot of apps from either CM and the Google pack) and 35MB for /cache. That left me with ~293MB for the /data partition. Some of the Google apps that get updated more often I've installed from Market (e.g. Maps, Gmail, Facebook). Everything works perfectly, including the Call Log. Did not have to do anything abt the dalvik-cache since the has been removed in the latest nightly.

One bug I've noticed is that enabling [Application settings > Development > Stop app via long-press] doesn't seem to work. It used to work in build 135 and before. Now long pressing it behaves the same as short pressing it.
[Desire Android Development] mr_dinosaur:
Stock Music Player Causing Extreme Lag and Reboots?

Sorry if this has be brought to the attention Kali- already and the rest of the CyanogenMod team but I have always had this problem on all builds including the lastest (build 143 at the time of writing).

When I use the music app there is a lot of lag, scrolling on the home screen, and application drawer. Opening other apps concurrent to the music might slow down the phone and sometimes causes reboots.

So, that's the problem and now I am wondering if people have solutions. What if I download and install Eliot Stocker's modified stock Music App from the Market? I think it's the same one used in CM builds right? I wonder if that would fix it.
[Desire Android Development] mr_dinosaur:
Long-press back button to terminate app

I think someone already mentioned this one a few pages back, just reporting that it still happens on build 144 (the latest build at the time of writing).

Settings>>Applications>>Development and then ticking the "Stop app via long-press" checkbox does nothing. Apps running in the foreground just goes into the background when long pressing the back key.
[Desire Android Development] StuMcBill:
I am using darktremor a2sd so I imagine I would have to put an a2sd remove command in there somewhere?

Sent from my Amiga 500 using Workbench
[Desire Android Development] adancau:
flashed 144 over 143 and now gettong the same call log issue that has been mentioned here (numbers shown instead of names). also when calling/receiving a call. have tried clearing the log, wiping cache+dalvik, same issue persists. i didn't have this problem on a clean 143 install yesterday.
[Desire Android Development] Rudolfje:
Should be fixed in new nightly:

http://forum.cyanogenmod.com/topic/...n-of-nightlies/page__view__findpost__p__74396
[Desire Android Development] gapone:
CM 6.1 apps2sd to sd-ext?

Is it coming to CM 6.1 or some other future rls?
[Desire Android Development] serverless:
Installed 144. The call log problem seems gone and the network bars are back in the status bar.

The function never stopped working here, but it's necessary to press the back button for 5 seconds, at first implementation was 2 seconds
[Desire Android Development] frocee:
long press button to kill apps doesnt seem to work, anyone else notice the same thing?
[Desire Android Development] adancau:
For me the call log problem just arrived after installing 144. I didn't have it in 143 :) 143 was a clean install though
[Desire Android Development] adancau:
Apparently it works, but you need to press the back button much longer (about 5-6s)
[Desire Android Development] mr_dinosaur:
You're absolutely right. And It does need 5 seconds which seems like an eternity haha. Some programs goes straight to background though because the long press is... well... long and before the kill foreground application command can fire, it's already in the background so you end up killing LauncherPro or whatever launcher you're using.

Actually, this isn't a big deal for me, I just find it somewhat useful especially with misbehaving apps which isn't so often.
[Desire Android Development] Narfx:
Same here. Call log worked in 143 and stopped working in 144 :/

(edit) Cleared contact storage, resynced, works again :)
[Desire Android Development] mad-murdock:
Just an info: over at the evo forum, cyanogen said 6.1 RC1 will be available on Tuesday...
[Desire Android Development] adancau:
Thanks, that did the trick for me as well :)
[Desire Android Development] marinierb:
Is the light sensor working properly in the latest builds? I'm on build 134 and the sensor seems a lot less sensitive to light than before and reports 10 lux even under medium light conditions.
[Desire Android Development] frocee:
oh ya, you're right. the kill app function was quite convenient to exit camera tho.
[Desire Android Development] terryhau:
I am using the N1 partition sizes and removed "dalvik.vm.dexopt-data-only=1".

The cache for system apps is now in /cache/dalkvik-cache. However the cache for user apps is still in /data/dalvik-cache.

Is that normal?
[Desire Android Development] Murd0ck:
Nice with an FM radio.. now i´m just wondering. now that MIUI figured out how to do an FM radio i wonder if it would be posseble in the future to have a scanner app for radio on the mobile.

i´m thinking is the hardware limited to a set of freq or is it fully costum in the programming so maybe we could do from 0.1Mhz to 1000Mhz or even more fun change bands AM LM and such and maybe listen in on truckers and police radios..
[Desire Android Development] Latty:
Ditto, I'm one of the few others that have noticed this issue for the builds in the last couple weeks.
[Desire Android Development] StuMcBill:
OK I just tried to do this, and I managed it up to step 6, and my phone wouldn't boot. It would show the HTC splash1 screen as normal, then reboot, show the HTC splash1 screen again and then go to recovery.

I then pressed reboot system now, and it did the same again?

Am I missing something?

I have now flashed back to original partition table and restored my Nandroid.

Is it anything to do with darkTremor Apps2SD?
[Desire Android Development] bemymonkey:
Worked fine with DarkTremor here...
[Desire Android Development] sookster54:
^^

YAY! Getting closer for everybody :D
[Desire Android Development] fenderf4i:
Had you removed that line from build.prop before rebooting?
[Desire Android Development] StuMcBill:
Yes I pulled the file using ADB, edited it on my PC and pushed it back.

I can only assume it worked? Is there a better way to do it?

Stu
[Desire Android Development] fenderf4i:
That's how you do it. The new hboot loaded correctly, and you're using a stock version of clockwork or amonra?
[Desire Android Development] StuMcBill:
Not a stock Clockwork, but PSFreedom, which still uses the standard partition tables.
[Desire Android Development] mad-murdock:
After flashing hboot, try full wipe, reboot recovery, format partitions, then restore android backup.

The reboot recovery step is important.
[Desire Android Development] sookster54:
Some pleasant fixes in 144, hope ADW 1.2.0 gets added soon (well I flash Launcher2 anyways).
[Desire Android Development] fridlack:
ADW.Launcher 1.2.0 is on 144... check the version number :P
[Desire Android Development] StuMcBill:
OK, I will give it a go tomorrow!

Thanks

Stu
[Desire Android Development] sookster54:
DOH, well I flashed Launcher2 over it lol, already got the ADW from the market earlier.
[Desire Android Development] Narfx:
Still cannot modify framework-res.apk since 142 to add new resources. Has anyone managed to decompile and compile framework-res.apk to add custom resources/xmls? Apktool (tested 1.3.1 and 1.3.2) doesn't give any errors, but the recompiled .apk causes bootloops, even with an unmodified framework-res.
[Desire Android Development] JonesWTF:
I've just updated to #145 and it all seems to be running smoothly. Well, all except for one tiny piece I just noticed. The text and icons on the power menu seem to be out of alignment.

Nothing major, just thought you'd like to know :)
[Desire Android Development] adancau:
Yep, confirm. The icons are bottom-aligned, which MIGHT work (clumsily) if Reboot and Power off had small-font status indicators as Silent and Airplane mode do, but as it stands now they look out of place. Icons should be aligned to the top of each cell, on the same level as the large-font labels.
[Desire Android Development] frocee:
+1

the icons alignment is still the same actually, but the text is aligned to the top, instead of middle.

edit: yea, the icons seems to be bottom left aligned.

I'd like to ask for the "quick" task killing to be back also, it's more useful that way imo.
[Desire Android Development] adancau:
+1 on this as well :) pressing a button for 6s is not the best way to kill a misbehaving task :)
[Desire Android Development] frocee:
Did anyone notice that you can bring up the shutdown menu when you phone is locked? that means you can shutdown a locked phone :P
[Desire Android Development] mr.r9:
Hello guys, I have a question.

Can someone look at this script? I usually use it to odex apks to save space but it doesn't work on CM nightly.

It keeps telling me 'dexopt-wrapper: not found'.

*Note: Rename the *.txt to *.sh to use on device.
[Desire Android Development] VK7HSE:
I'm only new to CM but the error is self explanatory, the function your calling isn't included ... please correct me if I'm wrong ;-)
[Desire Android Development] dakdroid:
Are the builds mirrored somewhere ?

Because the link from 1st page is down...

Edit: there:

http://mirror.teamdouche.net/
[Desire Android Development] mad-murdock:
Couldn't resist tonight. Finally on nightly. So expect me to troll around here now. By the way, official thread states, rc1 is delayed since too much work left.

One question: I use a slightly modified version of dark tremors a2sd so I wouldn't notice when apps2ext comes alive... would be nice if you highlight this here
[Desire Android Development] bemymonkey:
I saw that on Twitter, but which official thread are you talking about? Could you post a link? :)
[Desire Android Development] iinga:
Just like you can battery pull a locked phone
[Desire Android Development] mad-murdock:
links are hard on tipatalk, but now i can

something else: when i go to settings->sound, my settings app crashes. is it only me (because i did a titanium restore of CM 6.02 settings) or do you have that problem, too?

also i miss the adw settings inside the main settings app - sure its still accessible via homescreen->menu, but was nice to see inside settings itself
[Desire Android Development] frocee:
oh yes, that'll be a hardware problem. No wonder iPhone 'sealed' their battery :D
[Desire Android Development] Rohaq:
I always thought it was to force upgrades for those with dying batteries! All is forgiven, Apple, thank you for making me secure, come back to me! ;)