yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Facegarden:
Actually, its not that simple... But I figured it out!

It turns out that the wallpapers are *not* just in a folder in the zips. That was the first thing I tried before I even posted here.

But I looked again and under the "apps" folder, I saw "CMwallpapers.apk", and since .apk files are just like zip files, I just renamed it and extracted it. All the wallpapers are there, and I found the one I wanted!

I've attached it just so you guys will know what I was talking about. It was a great wallpaper!

-Taylor
[Nexus One Android Development] RogerPodacter:
i dont see no boobies in there though!! teeheehoo
[Nexus One Android Development] Facegarden:
Oh you... ;)
[Nexus One Android Development] andi_1984:
bt headset static sound issue

hey.

i tried the newest redstar and intersectravens kernel, but same problem again.

i tried the audio.conf as well :(

any idea?
[Nexus One Android Development] Tiberx:
The browser closes it self automatically. Using 39# been having that for the past releases now.

I went to radio 5.08 it seem to clear the random static while on calls i think.

Other issues before is home radius was too big detect a quarter of the screen. One finger touch turn onto two blue and red dot in tester. Keyboard messed up while the screen isn't detecting correctly before 38#. Not sure if it is still doing that. A reboot was need to clear it happens random.
[Nexus One Android Development] triciopa:
Hey I flashed 39 and now I have a problem. If I receive a call after the phone has been sleeping for a long time, I cannot answer. It just rings but stays at the lockscreen and I can't imputed anything. Anyone?
[Nexus One Android Development] fcisco13:
r u serious.....

N1
[Nexus One Android Development] drigerott:
i have the same problem
[Nexus One Android Development] makelegs:
Someone should give that problem a name......wish I could think of a good one.....
[Nexus One Android Development] chowlala:
Hrmmm.. *thinks really hard*

Why don't we call it The Wonk!!
[Nexus One Android Development] momomok:
how about....

Wonk Mk. II? :D
[Nexus One Android Development] triciopa:
HA but no!! I'm not nearly fool enough to post something like that if it was the wonk. Believe me, I know the wonk very well in all of its forms of presentations.

This is different.
[Nexus One Android Development] RogerPodacter:
I finally installed 39 and now been having the black screen issue in apps sometimes. May go back to rc4.
[Nexus One Android Development] elban:
I've been having it on rc3, rc4 as well as 7.0.0 final.

Same for Gmail scaling problem.
[Nexus One Android Development] chowlala:
I had that too last night.

Flashed a new kernel and it stopped showing up.

On redstar's latest 1190 oc kernel. Heh.

Edit: ok. I take that back. Just happened again. I'm gonna call this one The Bonk.
[Nexus One Android Development] makelegs:
My latest recurring problem has been a real PITA.... I'll try to keep the description brief:

All of the sudden, out of nowhere, my launcher starts hanging and giving the fc/wait option. Whichever 3rd party twitter app I'm using will also do the same thing. The launcher crash is a show stopper. It doesn't matter if I'm using stock adw, or EX, or LPP. I've seen them all do it.

I can wipe (nuclear) and get everything running smooth again, but it never lasts more than a day before freaking out again. The wonk is nowhere near as obnoxious as this.

Any others seeing some manifestation of what I'm describing, here??
[Nexus One Android Development] :
I'm seeing it as well.
[Nexus One Android Development] Autinhyeu:
#40 online now :)
[Nexus One Android Development] ZhekaS:
Can't flash #40 via Amon_Ra. Getting

assert failed: write_raw_image("/tmp/boot.img",boot)
[Nexus One Android Development] Autinhyeu:
the same issue :)
[Nexus One Android Development] diz127:
Mine flashed no problems :)

Maybe you should try redownloading it.
[Nexus One Android Development] slimfady:
Damn!!

I only flashed #39 10 minutes ago...
[Nexus One Android Development] Hyena:
wifi

The wifi not works with the #40 nightly for me.

It was ok with #39...
[Nexus One Android Development] temasek:
Same. Hope we are not "force" to use clockwork recovery :p
[Nexus One Android Development] rickytenzer:
I also can't flash #40. First time I've failed to flash a nightly!
[Nexus One Android Development] rekrapg:
same issue here, but i've tried both amon_ra and clockwork, no dice each way. Also redownloaded 3 times over an hour to make sure not bad download, and used download manager.

Back to 39!
[Nexus One Android Development] temasek:
I believe its just Amon_Ra recovery users are affected.

Edit: doh ....clockwork users also?
[Nexus One Android Development] temasek:
No need to reflash 39 if 40 failed. U still can bootup 39
[Nexus One Android Development] sitinon327:
Whew...thought it was just me....back on #39
[Nexus One Android Development] Basil 123:
error flashing, re-downloaded #40, checked the Mdsum - still wont flash with RA.

Guess if I really want it, will have to use CWM recovery?

Hope that the recently released image helps to sort out the wonking and bonking.....
[Nexus One Android Development] :
I had absolutely no problems flashing #40 with Amon_Ra 2.2.1 ...
[Nexus One Android Development] :
Weird, I had problems with it.. Amon RA, Redstar's kernel, newest radio, upgrading from 39 --> 40.
[Nexus One Android Development] Mayday_XL:
I get an error, when i install the nightly40 with Amon RA.
[Nexus One Android Development] hahahaa:
Me either, cannot flash to 40 :confused:
[Nexus One Android Development] imfloflo:
Just wipe cache and dalvik + flash rom no problem with #39 -> #40 all seems fine for me right now.
[Nexus One Android Development] retaliator:
I did the same but have that problem too. Could it be something with Darktremor or with libsqlite.so tweak?
[Nexus One Android Development] Hyena:
Wifi problems on #40 for anyone else?
[Nexus One Android Development] Stoo85:
#40 installation aborted...
[Nexus One Android Development] henrypeter:
no luck for the #40 installation...being aborted
[Nexus One Android Development] Rinegpeace:
Same with me. Wifi error.
[Nexus One Android Development] temasek:
Flashed #40 earlier got an error on boot.img with installation aborted so I just forget about it and rebooted but just checked the cm version I had and it read as 20110416-NIGHTLY-N1

That sounds like #40 ....
[Nexus One Android Development] temasek:
I had flashed #40 with installation aborted also. I'm on DT with libsqlite tweak. After installation aborted, I just reboot my n1. Only not long ago I saw my n1 already build 40.
[Nexus One Android Development] navahoo:
Also unable to flash #40 and after reboot wifi function was gone.

Reflashed latest IR kernel and got it back working.

Now i ve checked my build and im on 20110416 too... :confused:
[Nexus One Android Development] chowlala:
Weird. Why you guys getting flash failure.

Mine flashed without any problems.

So far, so good.

Haven't experienced The Bonk or Wonk yet either.

EDIT:

I'm on radio 5.12, with CWM 2.x, booted up on stock kernel, no problem, flashed redstars 1190 OC kernel, no problems, wifi also works.

I downloaded via the nightly web page instead of Rom Manager or something.
[Nexus One Android Development] bunnahabhain:
My n1 gets very HOT on mobile data. I am on #39. Can Anybody confirm?
[Nexus One Android Development] baseballfanz:
40 flash fine for me. Amon ra
[Nexus One Android Development] temasek:
What hboot u using?
[Nexus One Android Development] :
Flashing, running without problems from #39 to #40:

using

* HBOOT-0.35.0017

* Radio 5.12

* RA v2.2.1

Hope that helps.
[Nexus One Android Development] celloin:
Unable to flash #40 +1
[Nexus One Android Development] sitinon327:
Like others, I flashed #40 and got the abort error, so I just rebooted. When I did, I'd also lost the ability to connect to wifi on CM stock kernel. I flashed IR's Kernel via recovery and wifi came back. I'm now on #40, but all my info was gone, even though I only wiped data and davlik and I'm reinstalling all my apps via TB (good thing I'm used to reapplying everything...)
[Nexus One Android Development] celloin:
I'm lucky since I backup all data every time before flashing new rom using nandoid backup
[Nexus One Android Development] fcisco13:
Exactly because you wiped DATA, supposed to only wipe cache and dalvik...

N1
[Nexus One Android Development] :
Yes, can't turn wifi on.

Yes, now you say it, my phone has been pretty warm the last couple of days..
[Nexus One Android Development] baseballfanz:
Hboot-0.35.0017

Write cache and dalvik cache like always.

Using DT and wifi app.
[Nexus One Android Development] mtw4991:
No need to wipe cache or dalvik when flashing nightlys guys. ;p
[Nexus One Android Development] sitinon327:
Flash another kernel
[Nexus One Android Development] temasek:
Thanks.

I'm still wondering what's the common thing that users have that resulted in status 7 installation aborted but still 99% completed flashing build #40. All but wifi module wasnt completed.

First time encounter such weirld nightly. :)
[Nexus One Android Development] fitsnugly:
Offending commit was reverted, next build should be fine.

Drama queens :p
[Nexus One Android Development] :
40 ok here

.35hboot

always wipe dalvik/cache
[Nexus One Android Development] baseballfanz:
True but it's an extra 30 secs to do so I do it more out of habit

than needs.:D
[Nexus One Android Development] superg81:
flashing with a different kernel works. same thing is happening with crespo builds.
[Nexus One Android Development] Paul22000:
Yep, nightly 40 is 100% FUBAR'd:

Downloaded nightly 40.

md5 check matches perfectly.

Wiped all data.

Wiped cache.

Wiped Dalvik-cache.

Flashed nightly 40 and this happens:

Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: write_raw_image("tmp/boot.img", "boot")
E:Error in /sdcard/cm_passion_full-40.zip (Status 7)

Installation aborted.

Wiped again and downloaded/installed the N1 stable and no problems at all. Just booted, connected to wifi, signed into Google account, and Market. Working flawlessly.
[Nexus One Android Development] sitinon327:
It actually installed, even though it said it aborted. If you check your version, you would have seen you were on nightly #40 and if you use CM stock kernel, you'll notice wifi won't work
[Nexus One Android Development] navahoo:
LMAO! :p

+1
[Nexus One Android Development] Paul22000:
What is the CM stock kernel and where can I get more information about it?
[Nexus One Android Development] sitinon327:
If you flashed CM and didn't flash another kernel, then you're using CM stock...
[Nexus One Android Development] SimFox3:
When do you actually need to wipe cache and dalvik? I've tried wiping between flashing a few different roms and also tried flashing with no wipes, but saw no difference.
[Nexus One Android Development] SimFox3:
With the latest nightly, the swype keyboard gets unselected on reboot. To enable I have to go into settings, language and keyboard, and enable swype. Is anyone experiencing this too?
[Nexus One Android Development] baseballfanz:
You need to move the keyboard back to internal storage and not sd card
[Nexus One Android Development] k_myk:
Hey there,

did anybody on latest nightlies (#39, #40) notice wakelock with "google services"? That is an issue for me on "stable" :(
[Nexus One Android Development] houzuoguo:
i got the same error saying assertion failed, and then i flashed IR's kernel... now trying to boot, hope everything's fine~
[Nexus One Android Development] baseballfanz:
No problems here with Stable or 39 and 40
[Nexus One Android Development] darock159:
Flashed #40 with no problems. Running smooth as silk here
[Nexus One Android Development] richua:
I see this too (assuming you're looking at Spare Parts) but don't know what it's affecting, if anything. Battery life has been great with #39; normally wakelock drains battery.
[Nexus One Android Development] SimFox3:
Thanks baseballfanz! That did the trick
[Nexus One Android Development] germandark:
I had the issue with broken wifi on #40 using redstar 1150 with boost. I went back #39 with same kernel and wifi came back. I wasn't around to watch flash of #40. Idk if any issue.
[Nexus One Android Development] Basil 123:
I look forward to the final perfect stable CM7 release. Thanks to the team for all the hard work, Temasek for his kind words for wisdom

Cheers

Baz
[Nexus One Android Development] c3k:
I've just meet the bonk:

- phone ringing

- black screen with notification bar only (regularly working with the green handset)

- lock and unlock screen

- response

- big wonk (biggest for my experiece in the last month, 10 seconds i think)

- little "croak" then the call starts

i'm on #39
[Nexus One Android Development] rascarlo:
Boot Animation. TUX is Surfing the Cyan Wave

I had some time off and I finally cooked something I was thinking about since long time.

The CM7 Boot Animation is pretty neat. I liked it a lot, but I wanted to add something: TUX.

I took the original CM7 Boot Animation and added Tux surfing the cyan wave around Android.

Hope you like it, this is the video of the PNG sequence

[YOUTUBE]A3xmH2O0hQQ[/YOUTUBE]

Files can be found on my blog here.

All comments welcome.

If you like it, drop a comment and share.

If you like it, use thanks button
[Nexus One Android Development] ggrant3876:
The only problem I'm having with the nightlies is when I try to mount the phone it goes into a short reboot 2 -3 times before it finally mounts. Been doing this for the last several months.
[Nexus One Android Development] gururise:
#40 is borked... attempting to flash results in:

assert failed: write_raw_image("/tmp/boot.img","boot") ERROR!
[Nexus One Android Development] ggrant3876:
Flashed it this morning, no problems.
[Nexus One Android Development] henrypeter:
#41 is up now...
[Nexus One Android Development] Autinhyeu:
flashing #41 fine now???
[Nexus One Android Development] RogerPodacter:
does anyone know if the recent image released by HTC is being incorporated into the cyanogen source repository, i.e. so we can squash that wonk among other things? i've been checking the commits daily on the repo but havent seen anything so far. just curious...
[Nexus One Android Development] lazzy81:
Why are pictures still distorted from mms, only when I click on them
[Nexus One Android Development] obscure.detour:
This has been an ongoing issue that has a simple fix. Go into the messaging app and go to settings, scroll down to Custom Agent.

Some use iPhone, or Nokia N95 (I used this in CM6, this might still work), but "Default Android" does not seem to work correctly, so scroll down and select "Custom."

There should be "Android-Mms/2.0" already in this field, if not type this in. Hit ok. And you should be good to go. Hope this helps.
[Nexus One Android Development] metallicant:
Did you go into the messenger settings and in user agent select Nokia N95?
[Nexus One Android Development] c3k:
again, without wonk
[Nexus One Android Development] BrotherG:
Im interested in this too
[Nexus One Android Development] traxxus:
flashed #41 without problems.
[Nexus One Android Development] traxxus:
I wish cyanogen would add an option to change the lockscreen wallpaper in the background menu :cool:

(I don't want mess around with metamorph or so)
[Nexus One Android Development] SiNJiN76:
This is probably a Google bug/fault...but Gmail doesn't really sync correctly, huh? If I sync on the phone...then go to laptop and delete some mail...go back to phone and sync again...the Unread count is correct, but the actual emails that I've deleted from the laptop is still in bold and listed on the phone. Also, if I delete something off the phone...it's still unread and listed on laptop.

Just wanting to know if anybody else notices this.
[Nexus One Android Development] redrim:
I have noticed some odd syncing behavior.

Other times I see unread messages in the Inbox and have to manually search for "is:unread" in order to see them. Wiping the gmail data and resyncing seems to set it straight, but it seems like it has been happening more recently in the later builds even after re-flashing gapps.

(I am currently on #39)
[Nexus One Android Development] :
This happened to me on occasion with every Android OS (stock) version and customized version, especially when I made a nandroid restore. Seems CM isn't responsible for that behaviour ... Wiping Gmail data is the simplest solution.

Hope that helps.
[Nexus One Android Development] c3k:
i've some small problems with the market, they are here for a long time:

- no more automatic (daily?) update notification. when I open the market, the notification appear

- when I press install in the web the app download on the phone but at the end it didn't start to install (see logcat after), I have to press again install on the web market, download again and everything is fine now

Tried to clear cache/data, from titanium backup too

Any suggestions?

I/vending ( 7410): [13] DownloadManagerBroadcastReceiver.handleDownloadCompletedAction(): Looked up null asset for download URI:content://downloads/my_downloads/234-- ignoring.
[Nexus One Android Development] temasek:
Try this

1. Manually remove vending.apk and delete com.android.vending folder from /data/data. Reboot.

2. Boot to recovery and flash market or tiny gapps again.

Market 2.3.6

http://www.mediafire.com/download.php?mpkjaqs7f95i3ua
[Nexus One Android Development] cb474:
If you're having the call delay problem (note this is not the wonk, that's a different problem), please star the issue here:

http://code.google.com/p/android/issues/detail?id=16230

Google recently declined this known Gingerbread bug, saying it was "device specific" (to the Nexus One).

However this problem is also being reportedly widely on the HTC Desire, as well as Samsung Galaxy devices. I have posted a new issue above and not attributed it to a specific device.

Please comment and star this issue. And please specificy especially if your device is not the Nexus One, so that Google gets this message that this is a widespread Gingerbread bug, which has nothing to do with the device.

Thanks.
[Nexus One Android Development] SiNJiN76:
So is Google saying that since it's Device specific to N1, they don't really care?
[Nexus One Android Development] cb474:
I think their point was that since it was only being reported on the Nexus One (which was not true, they just didn't read all the comments in the bug report), it was a problem with the device and not the Android source code.

So that's why I created another bug report to make it clear this bug is not a problem with the device, but with the Gingerbread source (since it's also appearing on the Desire and Galaxy and I saw one report on the Atrix).

Google's claim was dumb, because there aren't that many devices with Gingerbread yet. And the Nexus One (and less common Nexus S) was first to get Gingerbread, so of course it's showing up there first.

Star it here:

http://code.google.com/p/android/issues/detail?id=16230
[Nexus One Android Development] imfloflo:
#41 flash al is good except having some FC with FB apps when going in to Profile or Message even after wiping data of FB apps. Dunno if it's related to the #40 #41 update or kernel problem with lastest FB 1.5.3
[Nexus One Android Development] baseballfanz:
It's a problem on fb 1.5.3 side not cm7. Many are reporting it.

I went back to 1.5.2 and all is fine again.
[Nexus One Android Development] kip2001:
Running into the same problem here, assume it's a fb problem since everything worked fine before update.
[Nexus One Android Development] Ertavarez:
Is official no more WONK ?
[Nexus One Android Development] baseballfanz:
Stol wonk for some yes.
[Nexus One Android Development] kelddaug:
Don't you think that ringtones is very low, I can't figure out what the problem is, everything is on max.

Does any of you have a idea.?

I'm on cm7 41 nightly, std cm kernel.!

Sent from my Nexus One
[Nexus One Android Development] richua:
Do you use DT apps2sd or data2sd?
[Nexus One Android Development] drigerott:
reboot since your volume turns normal or wipe dalvik-cache
[Nexus One Android Development] kelddaug:
I use DT, moved dalvik to SD, wiped and moved.!

I'll try to reboot.

Edit: Reboot didn't help.

Sent from my Nexus One
[Nexus One Android Development] richua:
If you are using any of the 2.7.5.3 betas, just keep rebooting until you get the correct volume. 3, 4, 5+ reboots is not uncommon. The volume error occurs during startup so you just have to boot until it gets it right.

The recommendation is to downgrade to 2.7.5.2 stable which does not have this bug.

Please visit the DT thread here: http://xdaforums.com/showthread.php?t=715940 and post all further DT questions there so we can keep this thread on topic. The volume issue is very common and you should be able to search the thread or have your question answered quickly.
[Nexus One Android Development] kelddaug:
Thanks I'll look at it....I didn't have that issue before, although I use beta 4, didn't see that one coming.

Funny bug, irritating though.

Sent from my Nexus One
[Nexus One Android Development] RogerPodacter:
the stock cm kernel does not have to full audio boost, it only increases volume slightly. you have to install an audio boost kernel to get the full volume increase.
[Nexus One Android Development] celloin:
Nexus One delays more than 8 seconds. :mad:
[Nexus One Android Development] cb474:
That's a little long for the call delay bug, from what I've read. Are you using CyanogenMod 7? You may be experiencing the "wonk." See:

http://code.google.com/p/cyanogenmod/issues/detail?id=2863

http://forum.cyanogenmod.com/topic/20881-psa-lets-define-wonk-so-we-are-on-the-same-page/
[Nexus One Android Development] cb474:
The Google employee following up on the call delay issue, in the Google support forums, is asking people to fill out the following form, to gather information about how people are affected and on what devices.

http://goo.gl/10HJ1
[Nexus One Android Development] jocaferlo:
I am having this problem sometimes even using DT 2.7.5.2. Reboot solves the problem normally.
[Nexus One Android Development] SiNJiN76:
Rarely do I not use my N1 enough for it to last over 24 hours and still have 40+% battery life. Unfortunately, the clock went bonkers and my alarm didn't go. Lockscreen time was correct...Status Bar time was off by 40 minutes (also the live wallpaper's time)...In Settings ... I've got automatic checked...and the greyed out was the correct time.

Guess the N1 wasn't used to staying up so late! Usually gets a restart approx...every 12 hours or so.
[Nexus One Android Development] RogerPodacter:
i think that's a new bug, cause i let my n1 run for 3 weeks at a time between reboots, and its my morning alarm too! 540 hours running:)
[Nexus One Android Development] temasek:
Issue 15135: Blank screen when returning to Home screen

For those who still having black screen, it was posted a test fix in the above Google Issue Tracker #15135

There are 2 possible "fixes" mentioned in the posts, namely libEGL.so and libsurfaceflinger.so

I've merged both "test fixes" into 1 flashable zip file for whoever wishes to test it. I've also include a revert CM zip for those who wishes to revert back to CM original files.

libEGL+libsurfaceflinger-signed.zip

Mirror

libEGL+libsurfaceflinger-RevertCM-signed.zip

Mirror

Comment by bassmadrigal from cyanogenmod forum

These fixes "suppose" to fix it.

If u flash a new nightly rom, you have to reflash this fix (if u wanna continue testing it) or else it will be overwritten by the new rom unless u have these files inputed into the "custom_backup_list.txt" in your /system/etc

Hopefully these fixes or possibly CM's own fixes will be merged into the nightly soon :D
[Nexus One Android Development] elban:
thanks very much!

flashing now and will report in this thread.

I'll need some days to test because on my phone the bug is difficult to reproduce, but happens periodically.
[Nexus One Android Development] temasek:
The blackie still comes and goes even after CM7 stable. I came aross this Google Issue tracker 15135 and the test fixes so I just wanna test it out. Since I'm testing, why not let others to test too :D