yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] obscure.detour:
I also have no issues with the dewonk app installed. Without, it is conisistently getting better by each nightly it seems.

But first of all, let me get this straight, because I've been trying to figure it out for a while. Because what you said confuses me. :confused: The kernel (2.6.35) that will be included in the ~final CM7 DOES NOT have an Audio Boost? Which would say that all previous CM7 releases using the 2.6.35 kernel does not have an audio boost, correct? And all the CM7 releases with kernel 2.6.35+ DO include an Audio Boost of some kind?

And second of all what does this Audio Boost consist of? Is it simply for N1 users? And does it effect the external speaker as well as the internal ear headset speaker?

Accept my apologies for the barrage of questions, but I have loathed the audio boost that I believe probably happened around that time. Seems like RC1~2ish but I don't remember! All these nightlies start to blur :p I have to hold the phone away from my head to have a conversation with anyone, but especially my gf (she's loud) :eek:

Thanks in advance for any clarification, but will try to look back. Flashing 34.

Good to know because I am in the same boat. And thanks for all your work! ;) On to 34.
[Nexus One Android Development] rickytenzer:
I think you're WAY beyond addiction ;)

Then again, so are we.

"Hi, I'm Ricky and I have a problem..."
[Nexus One Android Development] SiNJiN76:
Second nightlie in a row having to reflash gapps. 34
[Nexus One Android Development] debay:
same here - pretty annoying
[Nexus One Android Development] vaystikh:
Hi guys.

Can anyone help me with battery issue?

Form RC2 till now (#34), I face in massive battery drain, and its temp. always more than 29 deg. C / 86 deg. F

Already tried every possible kernel.

Tons of full formats (repartition SD) and extreme wipes form Temasek

But without any success...

Any ideas? :confused:
[Nexus One Android Development] RogerPodacter:
I thought the audio boost has always existed since cyan 5, and that it would still be present on the previous kernel he will use. Unless its a different audio boost we're talking about. It increases ear piece and back speaker volume I believe. I hope it stays with the reverted kernel, cause stock volume is not usable for many.
[Nexus One Android Development] ratson:
if i reflash gapps it still wont work, google framework keeps fcing... :| any solutions?
[Nexus One Android Development] Basil 123:
perhaps you could use one of the apps that monitor battery useage, and also an app to calibrate the battery? There are a few mentioned in the forum....

HTH
[Nexus One Android Development] Basil 123:
I really enjoy using the extended notification widget bar, just a suggestion - can the sound widget have sound+vibrate/silent as an option?

Thanks
[Nexus One Android Development] temasek:
Bad battery drain usually occur due to

1. Apps that wont sleep even if your phone is put to sleep. Such apps put serious strain to your battery. Such apps we called Rogue apps.

2. Legit apps that keep polling your location up-to-date, eg latitude. There may be other similar apps around. If u don't use it, logout of such apps.

3. GPS bug that keeps polling and don't turn itself off. If it doesn't turn off after app closes, either turn off gps and open map and close map. GPS icon should disappear but if it doesn't, reboot.

Usually after a full wipe, I suggest selective restore of your apps and settings. Especially for system settings and cm settings, its a no no for restoring.
[Nexus One Android Development] bunnahabhain:
Hi temasek,

would you like to explain your Signature? I am flashing the nightlys every time and i think my storage is now smaller than it was before. is this format.zip deleting everything on my storage or what? Will AmonRas Recovery survive that?

Thanks in advance :D
[Nexus One Android Development] temasek:
Its a complete wipe solution. 1 flash format all partitions, including system, boot, data and cache.

Just flash my Extreme Wipe from recovery and you are naked clean. Its simple, convenient and effective. :)
[Nexus One Android Development] navahoo:
flashed #33 coming from rc4 on a desire device and lost all apps too.

today i ve flashed my n1 from rc4 to #34 and no problem at all!

as usual i did a nandroid first and then wiped cache and dalvik on both

phones.

curious what will happens if i m going to update the desire to #34...

+1 and one of the most helpful tools ever! :cool:
[Nexus One Android Development] bunnahabhain:
Very interesting! THANKS temasek!!!

JUST ANOTHER QUESTION:

What is planned for CM7.1? Where can i find daily information about that? Is there a Thread on xda or are this informations from a chat on IRC? I am just curious
[Nexus One Android Development] temasek:
I love to know that too. :D
[Nexus One Android Development] unknownrebelx:
On the gerrit some of the stuff in the "open" section alludes to 7.1. Pretty much anything Fitsnugly has cherry picked right now is assumed to be a 7.1 feature if you want to check it out ahead of time :D
[Nexus One Android Development] XxSilent22xX:
I don't think there is a list anywhere but I'm sure if you buy him a few beers you could get him to talk :D

Sent from my Nexus One
[Nexus One Android Development] temasek:
Some of his cherry picks had been abandoned. Its something that fit's unable to control over the status of his cherry picks. Fits is doing a wonderful job over at his thread.
[Nexus One Android Development] fitsnugly:
I disagree. He sucks.

So is the new stock kernel wonking for anyone?
[Nexus One Android Development] temasek:
Lol :)

Btw for sometime since mid #20 nightly. I have not a single wonk. I'm on #34 now with IR .38.2 kernel.
[Nexus One Android Development] makelegs:
+1.......:D
[Nexus One Android Development] SiNJiN76:
I flashed the gapps dated 20110307.zip ...

If you keep getting an FC reflash an older nightlie on top of current.
[Nexus One Android Development] neopbm:
So it will format everything except the memory card, is that correct ?

Need to be sure, before testing it ;)

Sorry for my poor English
[Nexus One Android Development] apratomo:
Will it work on clockwork recovery?
[Nexus One Android Development] fcisco13:
Correct no worries it will NOT format sd.

N1
[Nexus One Android Development] richua:
You don't need to use it with CWM because there are options to wipe the same partitions that temasek's file wipes. Amon Ra does not yet have these options. You can use it (I have successfully), just don't need to.
[Nexus One Android Development] hooman64:
Call functionallity not working!

I seem to have problems calling anybody, either with Google Voice or the stock dialpad ... after 5 seconds the call ends automatically ... any idea's how to fix it?

p.s: I can receive calls but cannot make one!
[Nexus One Android Development] neopbm:
Thanks ! :-)
[Nexus One Android Development] temasek:
Correct! It will never format external storage (including sd-ext) and recovery partition.
[Nexus One Android Development] ch33kybutt:
Comment 154 by project member steve.ko...@gmail.com, Today (44 minutes ago)
[Nexus One Android Development] momomok:
Will it format .android-secure then?
[Nexus One Android Development] temasek:
That folder resides in your fat32 sdcard. So no, it won't format that folder.

The options in Amon_Ra recovery includes wiping android_secure folder and wiping sd-ext partition.
[Nexus One Android Development] intersectRaven:
Just a noob question (really don't know anything about this one), if I partitioned my sd card so I can get ext4 (sd-ext) does CM use it automatically or do I have to use a app-to-sd script? :o
[Nexus One Android Development] temasek:
U have to use other scripts like DT A2SD to enable that.

DT SCRIPTS FOR EXT4

http://xdaforums.com/showpost.php?p=12533976&postcount=1314
[Nexus One Android Development] beankid:
Was there a point when the Wifi N profile was left out of the rom? I am on build 28 and have not been able to get my phone to connect to wifi N when I know the hardware supports it and I thought 2.2 brought this driver to the phone. I could be wrong about this though.
[Nexus One Android Development] temasek:
N1 supports only wifi N 2.4 ghz and not the 5 ghz (from what I understand)
[Nexus One Android Development] RogerPodacter:
What is his comment about exactly? Is this rolling back to avoid the call bug, or something else? What bugs...
[Nexus One Android Development] temasek:
Read for yourself.

http://code.google.com/p/cyanogenmod/issues/detail?id=2863#c141
[Nexus One Android Development] Mokurex:
But wireless n can run in both 2.4Ghz and 5Ghz isn't it? So the frequency doesn't really tell if it supports wireless n or not. Correct me if i'm wrong.

EDIT: And that's what you said. Wow I'm getting blurred, ignore me, lol.
[Nexus One Android Development] SiNJiN76:
GPS icon wont go away. Gotta open/close maps several times.
[Nexus One Android Development] baseballfanz:
What build u on? That should have been fixed a while back.
[Nexus One Android Development] SiNJiN76:
On 34. Maybe I need a wipe? Well...I'm going to hold out for the wonk to be fixed first. Annoying, but bearable. Thanks for confirming that it was a bug that's already been fixed.
[Nexus One Android Development] richua:
I'm on RC4 and also have this problem sometimes. I did some digging and I think the fix from before only corrects the problem where the icon would stick and then GPS wouldn't pick up again when turned back on. Currently when my icon sticks, I'm still able to get a lock when I turn GPS back on and I just open/exit an app that uses GPS and the icon goes away.

I think there's two separate but maybe related problems here: one has been fixed and one doesn't affect too many users.
[Nexus One Android Development] temasek:
I thought it was fixed but it happened to me too. A reflash of rom solved it.

Fyi
[Nexus One Android Development] makelegs:
Would you say that GPS is acting "gonky" ???

(god help us)

:D
[Nexus One Android Development] intersectRaven:
Please don't add another word idea... :p
[Nexus One Android Development] temasek:
One more funny word and cyanogen will really throw his n1 into the garbage bin. :p
[Nexus One Android Development] makelegs:
#justsayin ;)
[Nexus One Android Development] Basil 123:
I'm beginning to worry about you guys:-http://en.wikipedia.org/wiki/Neologism

Back on topic - I notice that the kernel has been changed from "Revert kernel to 2.6.35 for stability." to "Back to 2.6.37, with a few bugfixes in power collapse code".

Could this be the beginning of the end of the wonk? I hope so.
[Nexus One Android Development] temasek:
Steve aka cyanogen is still trying his best to kill this bug (wonk). From what I understand, .35 kernel also wonks. Probably that's why the new update.

We should buy him some beers :)
[Nexus One Android Development] Basil 123:
#35 is up...
[Nexus One Android Development] bunnahabhain:
i will skip that one i think - :D

Bug or no bug:

When i answer a call i got a 1 second delay of the mic. So when i swipe the screen to answer the call people are not able to here me immediately. Thats a bit akward some times because i have to say hello again.

I had this on every CM7-ROM is tested so far...
[Nexus One Android Development] RogerPodacter:
I also had this issue back around #31, but it only happened once after the initial flash.
[Nexus One Android Development] midyat47:
I have 'gonky' problem toooo!!
[Nexus One Android Development] olavjunior:
Wiped and flashed, so far so good regards to my issues with the black scree (sleepy display, awaken phone). I sure hope it lasts! (I believe it's related to the wonk, since that one is some kind of a sleepy problem).

After two hours with turning the display off in any way, it has lit perfectly normal every time I've awaken it. And that has NOT been the case since I started flashing CM7. #19 or 18 was the last, nearly stable, I've had with regards to this issue.

EDIT: It still goes black, but actually it seems to wake up after a couple of attempts. This is really the best build so far, so I'm getting optimistic! :)It happened after a call, so I really think it' related to the prox sensors or something.

One other bug, there seems to be an issue with the wifi not beeing as stbale as it used to. But no big deal.
[Nexus One Android Development] slava86:
yup got it also ... I always say "halo" twice ... realty annoying

no USB storage with #35
[Nexus One Android Development] RiNo808:
The one thing i would like to see in the camera is the point focusing...BTW does enomothers have that?
[Nexus One Android Development] katiepea:
The htc cam does, as well as working iso controls and 720p video, it takes amazingly better pictures
[Nexus One Android Development] MontAlbert:
Well, that is your opinion mate and you are entitled to it- personally i prefer ADW. I prefer the options it has and the functionality it offers. I have no problems at all with it working fine on this nightly. Have you tried playing with settings (Anderwebs said to unselect the keep in memory button which helps apaprently) plus a few other things can help.

BUT it doesnt matter at this stage because Launcher Pro is not open source and thus can never be made into a system app and system apps work much better for theming etc.
[Nexus One Android Development] :
I dont have any problem with it either, but i just love Launcher Pro's Sense widgets, but anyway.. Back to the task at hand, that was a comment a few hours back.... it was discussed and the discussion is over..;)

Well for me it is anyway;)

JD
[Nexus One Android Development] MontAlbert:
so this bug you are speaking of relates to Launcher Pro and not the actual CM rom... maybe you should state that first...
[Nexus One Android Development] :
With a sense rom it does as well;)

Its exactly the same camera as the N1;)

JD
[Nexus One Android Development] katiepea:
No, its a completely different camera, have you ever flashed the htc version over a stock build? There's a huge amount if people waiting for this to be ported.
[Nexus One Android Development] myakove:
When try to export XML of "User Interface" I get error:

"D/XMLOUTPUT(*1004):*java.io.IOException:*Permission*denied"
[Nexus One Android Development] MontAlbert:
lol

well, a few hours ago i was asleep mate- its 8am here. :P
[Nexus One Android Development] harmohn:
...I get an error in writing the xml file too - had it for a number of nightly's.
[Nexus One Android Development] :
I'm going to NZ next year, supposed to be very pretty, but we are all going on a backpack tour of south asia. :-)

JD

Sent from my Cy Powerhouse Nexus One.....
[Nexus One Android Development] :
It's the same hardware I mean.. I had a desire before a nexus, the difference is not in how the photo is taken, but how it is presented:-) sense has more clarity than stock..

JD

Sent from my Cy Powerhouse Nexus One.....
[Nexus One Android Development] pwig:
New nightly up.

08062010
[Nexus One Android Development] BootsSiR:
I just submitted a patch to CM6 for the following feature. Dunno if it'll make the cut or not.

Basically allows you to tweak how long after the screen goes off does the screen lock enable. I find it handy if you're using the phone a lot to set it to 30 seconds or so to give you some time to use the phone again without having to unlock it.
[Nexus One Android Development] ram130:
Its a great idea!
[Nexus One Android Development] ax0r:
setting up new nightly now.

I honestly can't get a good working external app install configuration going. I set it up on the cyanogen settings but every time i wipe, flash etc i end up having to sync and download everything again. Can anybody maybe explain to me what im doing wrong?

I'll let you guys know how it goes for me after i test it a bit
[Nexus One Android Development] BootsSiR:
Don't wipe when you flash nightlies. I never do and they always work great.
[Nexus One Android Development] katiepea:
I concur, I don't wipe between nightlies either and don't have problems. Wiping is too much work without ext support
[Nexus One Android Development] ax0r:
I have been back and forth between my enom nandroid backup and the nightly builds. i prefer to wipe. any other suggestions
[Nexus One Android Development] katiepea:
Yeah, then flash a nandroid backup of a nightly that's set up, then flash the newer one

If you have to wipe there's no other option, we don't have ext support
[Nexus One Android Development] pokey9000:
Works for me.
[Nexus One Android Development] Skyheartblue:
Same. Started to grow an habit of waiting 1 sec b4 saying hi..... :-P
[Nexus One Android Development] richua:
Got a nasty random soft reboot with #35, going to wipe and see if that fixes it.
[Nexus One Android Development] Spakainz:
What about slow USB transfer speed? Maybe in #35 it's fixed?
[Nexus One Android Development] Rimher:
With the lastest IntersectRaven's kernel the issue with usb speeds seems to be fixed for good! =)
[Nexus One Android Development] 3bs:
Holy crap. All this time I thought it was just me. I just thought that that's how it was. Never really considered it a bug and I couldn't remember if it has always been that way. Glad to know I'm not alone.
[Nexus One Android Development] FishFan319:
THIS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Has happened to me since the build 15 or so.
[Nexus One Android Development] EnhancerFIN:
OMG :D..Please explain me your version of call wonkiness? That is exactly that, delay on the mic etc. Been an issue for as long as CM7 has been, and now u guys start talking about it :D
[Nexus One Android Development] rickytenzer:
There's an amazing mod that increases the read/write speed of the SD card:

http://xdaforums.com/showthread.php?t=1010807

I wonder if CM will swallow this up! :D
[Nexus One Android Development] 3bs:
I never paid much attention to it because I thought the short delay was normal. Like I was just starting to talk too fast. It was never more than a second so I never worried about it.

I used to get a frozen black screen when trying to make outgoing calls and assumed that was the wonk everybody was talking about. It went away and I just assumed I was a lucky one.
[Nexus One Android Development] shorza:
I get this too, I just assumed it was a delay in the dewonkificator.
[Nexus One Android Development] RogerPodacter:
The wonk is a 30 second issue, and also sometimes applies to anything that uses the Mic. The 1 second pause is not the same thing I don't believe, but is a bug in itself. It partially existed on froyo too I believe.

Also, is the rumor that track ball wake is working on OTA ROMs now? Like the miUI guys I heard got it working...
[Nexus One Android Development] bunnahabhain:
The delay is not the wonk, its the wonks younger brother...
[Nexus One Android Development] negroplasty:
I also have the one second delay, I don't consider it a bug, and you sure as hell won't hear me complaining about it like it's the end of the world.

I vaguely remember there being a slight delay with Froyo as well. Regardless, it doesn't bother me the slightest bit. I, for one, am just thankful to have support from the CM team a year and four months after our phone's release. Some of you complain like you're paying for a service or something, it's a free modified firmware and our phones are well over a year old... if it bothers you so much, go back to stock and complain to Google about every little thing that isn't up to your standards.
[Nexus One Android Development] bunnahabhain:
Oh man you are the instance of morality.

I just reported something that COULD be a bug and others confirmed that. Perhaps it is easy to iron that out?? Who knows... But it has to be mentioned, shouldn't it? If nobody had ever reported such things cyanogen mod on the nexus one would be buggy as hell.

That thing has nothing to do with any lack of appreciation for this great project.

I would understand your point if we had all complained unproductively or spam around. But thats not the case. And the fact that the delay does not bother you (because you just call you mom :p) does not justify to to think that it is annoying to others.

Lets be productive and don't blame each other wrongful reasons!
[Nexus One Android Development] slava86:
for me the delay is most anoying thing in the N1
[Nexus One Android Development] negroplasty:
You're right. My apologies, I was having a stressful day and got a little carried away... I don't mean to take it out on you fellow XDAers. Note I did say some people, although none of you in this particular situation, there have been times in the past when I ask myself why Cyanogen and the team even bother for nothing more than street cred as we become more and more needy and less grateful. Were it not for CMmod, my Nexus would probably be nothing but a sexy paperweight by now, the only thing I'd like to convey is my gratitude and occasional donation when I can afford it. Sorry guys, and thanks Cyanogen and co for all your hard work!
[Nexus One Android Development] PacoBell:
Ditto on the horrible static on the receiver side. I can hear the other party just fine. Toggling bluetooth in-call demonstrates it's not my headset(s) making that noise and built-in mic functions fine. This needs to be looked into seriously. I can't believe we're already into RC4 with a bug this big.
[Nexus One Android Development] bunnahabhain:
no hard feelings... and i totally agree with the rest. Next donation on 12th of april when fresh money hits my account :D
[Nexus One Android Development] chowlala:
I don't have any problems with my bluetooth. Have you tried repairing the devices?
[Nexus One Android Development] RogerPodacter:
here's how i handle the slight delay. i just answer, and wait till you see the timer on the screen to start counting. that is when the phone call begins in my experience. or alternative, you answer and simply wait till you hear the background noise from the other call kick in, like a low hiss. its easy to hear the dead silence switching to low hiss = call initiated. then i say hello, or "word up", or whatever people say nowadays!
[Nexus One Android Development] :
It's "Allo Allo"
[Nexus One Android Development] SheridanJohn:
I also have this ever since I joined CM7 at RC1. Starts suddenly after several calls without it. Only reboot helps, switching Bluetooth does not help. I use a Plantronics Voyager Pro. I will trying to re-pair if it happens next time.

@negroplasty: I agree to your words, liked reading them.
[Nexus One Android Development] EnhancerFIN:
If the 1-5 second delay is not the wonk, then I havent wonked in 40 builds a single time. I had times at first, maybe 10 first CM7 builds, when my screen went black and did not come back until the call ended.

That stopped, and now if the other end can´t hear me in the beginning of the phone call, I click mute and then unmute and everything is ok.

Weird thing is, my old co-worker had got a black HTC desire which was S-OFF, and had serial number written under the search button in front of the phone. He got the phone from htc management office here in Finland, and came to me asking whether I could update the phone because the screen goes black when on a phone call. I did update that phone, to latest official rom with sense **** etc. but that did not fix the problem. Only thing I could say was, that the phones proximity sensor was faulty. Maybe, but it was the only thing in mind that time, because over that the phone worked like a charm, phone calls were just a bit diffucult.

Every symptom was still exactly the same, as CM7-Nexus early days.
[Nexus One Android Development] :
36 is up :)
[Nexus One Android Development] :
anyone have a problem with camera

sometime when I take a picture it look like this
[Nexus One Android Development] shorza:
Yeh, mine does that occasionally. Has for a while now.
[Nexus One Android Development] chowlala:
Nope. Not EVER since I got the phone and moved into custom roms.

For those of you having plenty of issues, a full wipe and reinstallation really helps.

Every major revision, a full wipe is a good thing. Especially when moving from like 6 to 7.

Once you move up and have no issues, you should be good to continue.

But when you face weird stuff in the opening and now and then, try the good ol' wipe and flash.