yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] shotta35:
"We are the CM Borg, resistance is futile!"

Hehe, another one joines, yay. And for your flashing pleasure I present:

http://mirror.teamdouche.net/get/passion/cm_passion_full-188.zip

Built 188 ready for consumption! Dig in!
[Nexus One Android Development] makelegs:
Always faster the second time I run it. I don't do airplane mode or anything. Usually wifi and bt on. I maybe do clear cache first, tho.
[Nexus One Android Development] shotta35:
Hmm, getting FCs right away, i did an "upgrade" for the first time and i'm seeing dialer and messaging FC. I'll wipe and do it to see what's going on.

Ooops, that was my fault, bad file :D
[Nexus One Android Development] SiNJiN76:
First... 188 lol. I guess not.

anyway... zoom in the camera still doesn't work well much. Also... it's takes a few tries to get into camcorder mode... the slider keeps sliding back to camera.
[Nexus One Android Development] makelegs:
Wow.....is it just me, or is 188 running terribly?
[Nexus One Android Development] andyandrwew:
should i run 188 or not?
[Nexus One Android Development] makelegs:
I guess here's an example of how quadrant scores may not mean all that much.... 188 just pulled 1681 for me.... but it took damn near forever for quad to actually finish. Froze at the top of the stairs on a single frame for about 3 minutes straight before eventually finishing. So....pretty decent score, but really crappy performance. Lotta good that does me.
[Nexus One Android Development] andyandrwew:
did you flash direct or did u wipe cache?
[Nexus One Android Development] makelegs:
ya....I wiped everything before I flashed 188. Rolling back to 186, now. Maybe I'll re-flash again just to see. It was giving me a lotta FC's and just functioning at a snail's pace. No worries.

How's it working for everyone else?
[Nexus One Android Development] irishrally:
I've had no issues with 188 yet.
[Nexus One Android Development] makelegs:
Well, crap....now 186 is running slow, too. Looks like I gotta do a full wipe. Hate that! Whatsapp tried to upgrade and ended up being a disaster, earlier. Is it possible that it messed something up??
[Nexus One Android Development] simms22:
no issues with 188. no fc's. everything works :)
[Nexus One Android Development] paolobacci:
it's rc1 with improvements and not a tagged version.
[Nexus One Android Development] fitsnugly:
Latest nightly seems to improve the speed of the widgets being available after a reboot... nothing on the SU "set on boot" issue tho.
[Nexus One Android Development] crimsondr:
Which gapps should we be using?
[Nexus One Android Development] prettyboy85712:
It's in the first post.
[Nexus One Android Development] crimsondr:
Okay I asked my question poorly. I've already flashed the gapps from the OP.

What I want to know is what's the difference between these:

gapps-hdpi-FRF91-2-signed.zip

gapps-hdpi-FRF91-signed.zip

gapps-passion-FRF91-signed.zip
[Nexus One Android Development] Smokeaire:
Good question. I'd like to know the answer to that also.
[Nexus One Android Development] notxel21:
I thought it would be fixed in the latest nightly but I guess not. :confused:

I'll quote myself:

:cool:
[Nexus One Android Development] THATTON:
Do you use Autokiller. I figured out a kind of "workaround" for the su permissions if you do.
[Nexus One Android Development] notxel21:
I use it. Would you mind sharing? :confused:

Thanks! :cool:
[Nexus One Android Development] leyvatron:
You can use any spoof phone and itll fix the pic resolution but...

the MMS is not up to par... I'm also having problems with sending an attached pic (not picking from my gallery) but taking a pic while in text mode. They constantly receive a black screen.
[Nexus One Android Development] akaine2001:
Can i?

Can you flash the nightlies over the RC1 or should I wipe, then flash nightly from scratch... and FTLOG how do i wipe just "cache" because i don't think thats the Dalvik-cache they are talkin about... or is it
[Nexus One Android Development] bskim23:
+1 been wondering as well
[Nexus One Android Development] THATTON:
As soon as the phone boots, click on Autokiller to open the app, accept the message and select a preset. Within seconds, all of your widgets will have loaded and SU will have granted any root apps permissions. I don't know why or how this works but it does. Please report back if it works for you as well. :)
[Nexus One Android Development] notxel21:
You can flash Nightly's over RC1. I'm on my third nightly after RC1! :eek:

You don't have to wipe unless you have issues after reboot.

You can wipe "just cache" from recovery if your using Amon_Ra's not sure about others. :cool:
[Nexus One Android Development] notxel21:
I just did what you noted above and I have no problems taking pics with my camera while in the messaging app. :cool:
[Nexus One Android Development] paolobacci:
I just installed the last nightly build but I can't send MMS too... I get a notification that the message could not be sent about 15mins later.
[Nexus One Android Development] knightnz:
I can send full-resolution MMS's from the camera just fine using the NexusOne custom user agent, but incoming MMS's still fail when I press the "Download" button. Stops the gf from being able to send me stuff that she shouldn't which is possibly good.

The error it's spitting out is:

E/RetrieveTransaction( 1721): java.lang.RuntimeException: Value length > LENGTH_QUOTE!
E/RetrieveTransaction( 1721): at com.google.android.mms.pdu.PduParser.parseValueLength(PduParser.java:913)
E/RetrieveTransaction( 1721): at com.google.android.mms.pdu.PduParser.parsePartHeaders(PduParser.java:1558)
E/RetrieveTransaction( 1721): at com.google.android.mms.pdu.PduParser.parseParts(PduParser.java:776)
E/RetrieveTransaction( 1721): at com.google.android.mms.pdu.PduParser.parse(PduParser.java:128)
E/RetrieveTransaction( 1721): at com.android.mms.transaction.RetrieveTransaction.run(RetrieveTransaction.java:137)
E/RetrieveTransaction( 1721): at java.lang.Thread.run(Thread.java:1096)
E/RetrieveTransaction( 1721): Retrieval failed.

So it looks like something is trying to send a bigger chunk of data than the MMS subsystem can cope with.
[Nexus One Android Development] leyvatron:
@ notxel21 It's not actually taking the pic, its having the other person receive it....they always say its a black screen.

@knightnz same here. my gf sends me a pic from her incredible and my download looks like its doing something... but after like 5-10 sec it clears out. *shrugs*
[Nexus One Android Development] paolobacci:
I'm testing right now with custom agent = NexusOne if it sends the mms.
[Nexus One Android Development] dudebro:
the app antennas allows you to check towers in your area... could give it a shot.
[Nexus One Android Development] katiepea:
You're right, it's dramatically different in different areas of la, the only thing is in my apt prior to the HSPA+ upgrade I was always connected to H and got 1.5mb down consistently, now I'm always on EDGE and if out DOES go to H it's slow as dirt.
[Nexus One Android Development] whoisthedrizzle:
Yeah that's more or less what happens to me around work (****ton of satellite and radio broadcasting equipment not to mention tons of other electronics that love to mess with signal). Sounds like your signal is just hovering over the threshold at which the phone probably just says "**** it" to HSPA and falls back to edge long enough for a brief signal gain bouncing back to HSPA just in time to drop below the threshold again and fall back on edge before actually accomplishing anything. The korean radio seemed to help me with the bouncing back and forth in lower signal areas, but was whoring my battery. Signal was overall more consistent, but my speeds took a slight hit with that radio too.
[Nexus One Android Development] dharani1234:
New Nightly posted

New Nightly posted ...

cm_passion-07242010-001928.zip

Has somebody tried it yet ?
[Nexus One Android Development] rori~:
It´s just uploaded...
[Nexus One Android Development] prettyboy85712:
Running it now without issue.
[Nexus One Android Development] rori~:
Nice:cool:

..and here´s notifications in succession. Compiled against latest CM6 source right now [Nightly24/07]

Edit: trackball move in camera is fixed!
[Nexus One Android Development] irishrally:
It was fixed in last nightly also.
[Nexus One Android Development] Enndr:
Installed but I haven't noticed any new features. Maybe a stability and bug fix night?
[Nexus One Android Development] massari90:
Stable as ever
[Nexus One Android Development] dale_cooper:
heh... I've had GPS on - thats not the issue....

kalin - did you area recently switch to HSPA+? I went to the local tmo store after work - they admitted there are some sort of network issues going on becuase the rep's personal phone - samsung vibrant was trying to connect to modesto CA server and had terrible speeds as well. So its a network thing, not the nexus, not this rom.

I'm guessing your local network is having the same problem...
[Nexus One Android Development] dudebro:
my area just recently switched to HSPA+. I'll admit my speeds were off before the upgrade

and after I guess they sorted things out, my speeds were fixed plus a boost.
[Nexus One Android Development] bobtentpeg:
Anyone else have SMSPopup die on them after 0723 nightlies
[Nexus One Android Development] Bamdroid:
Yeah same here..hadn't noticed anything new..runs like an effing champ.
[Nexus One Android Development] kalinusa:
I don't know guys. How do I know if they changed or not? Is there a site with upgraded locations. I can go to the T-mo store but what if they ask me to see my phone. The whole CM6 rooted thing, would they mind? Or I can just ask to see one of the reps phones?
[Nexus One Android Development] jlevy73:
This is something they can do over the phone, no need to go into the store.
[Nexus One Android Development] kalinusa:
Ok guys here is the site:

http://t-mobile-coverage.t-mobile.com/

you can check which cities are LIVE with HSPA+. So apparently they did upgrade Pittsburgh. So what does this mean??? I think I still need to go and check out one of the reps phones!

P.S. I am still going to flash the Rodriguez rom tomorrow and check the speed with it.
[Nexus One Android Development] triciopa:
Do you usually wipe before these? I don't, but I am now caught inside a boot loop and I thought it might be because of not wiping
[Nexus One Android Development] damanrico:
Wipe cache + dalvik cache.
[Nexus One Android Development] katiepea:
Couldn't take the wonky froyo apps 2sd anymore, went back to eclair. Might try again when cm6 has ext support, but as I went back to 2.1 I'm realizing I think I like it a lot better anyway. No glitches, more support, better performance.
[Nexus One Android Development] bosshog187:
wow thanks for the great response
[Nexus One Android Development] trismegistos:
With wifi enabled?
[Nexus One Android Development] andrewv88:
How to configure the camera app .. i have bad pictures coz the new Contrast/Sharpness modes
[Nexus One Android Development] leoccc:
188 everything fine for me and Goggles work now! cool!
[Nexus One Android Development] makelegs:
After flashing a couple of times....188 seems fine for now. For the record, though... 184 is the only ROM I've been able to use to dload the new carhome from the market. Had to flash from 188 back to 184 just to install carhome again, before re-flashing 188 with a wipe or 2 in between. What gives?? And when I flashed down to 184, my security pin was no longer recognized, requiring yet another wipe. Does that happen often to you guys? It was a first for me!

Thank god for backups!
[Nexus One Android Development] xguntherc:
Nandroid restore
[Nexus One Android Development] BritSwedeGuy:
I'm on 183 and have not been able to get Car Home to install - especially annoying as I'd used Titanium to delete the previous version! Good to know that there might be a way forward.
[Nexus One Android Development] McGilljam:
How Come?

Rom Manager - Nightly Update - Download and install.

How come that a download and install of a nightly rom, using Rom Manager for everything, removes Google Apps?

That does'nt happens if you download the rom using browser in phone and then reboot in recovery.

And then.. if Google Apps are removed, I've got an error trying to download and install Google Apps Froyo using Rom Manager...

Why? :confused:
[Nexus One Android Development] :
Time for me to get my first nightly! 188 seems to be very stable, reading the comments....I actually have CM6.0.0 stable....do you have some tips & tricks? just flash nightly 188 and then gapps?
[Nexus One Android Development] bryanchapman9999:
Yeah, I found this out this morning after paying for it :rolleyes:
[Nexus One Android Development] shmigao:
i would always wipe cache and dalvik-cache before flashing
[Nexus One Android Development] :
so no data/factory reset? :cool:
[Nexus One Android Development] krisnielsen:
you still can't take photos using the trackball, unless you scroll it first :(
[Nexus One Android Development] Autinhyeu:
The same problem :)

but sometimes its work :eek:
[Nexus One Android Development] spyz88:
Chris Soyars fixed the issue late last night with ROM Manager not downloading Google Apps also.
[Nexus One Android Development] Autinhyeu:
TA Ebuddy Messenger app still dont work in this ROM (latest nightly)...

Wifi network seem slower some ROM another...
[Nexus One Android Development] automatek:
Anybody else having the issue:

I'll be browsing the web, and then click a link and it's like the internet connection will stop working. (No more webpages will load) If I close out of the browser and then launch it again still nothing. Then by changing my 3g connection to a 2g only, it then works again. Also if I enable 3g again it will work again for a breif time and then stop again.

Came from CM 6.0.0 Stable to build 186 after a cache and dalvik-cache wipe. Nothing extra loaded except the new 9/30 gapps.

Didn't have this problem on the 6.0.0 Stable with same setup.

Any ideas?
[Nexus One Android Development] icon57:
so far 188 is running perfect for me...very fast, better than cm6
[Nexus One Android Development] Smokeaire:
I used to have the very same issue. It was very frustrating. This is what seemed to fix it. Go into applications, camera, then clear data. I know, very weird, I did this because of fc with the camera but after I did that I noticed my data was working fine and I haven't had to do the 3g to 2g and back since. Maybe a coincidence..who knows... but I didn't do anything else. Give it a shot. I'll be curious how it works out for you.
[Nexus One Android Development] SiNJiN76:
Not quite like you, but I noticed that links sometimes take a longer press to get it going. Sometimes not responsive at all. Wonder if it's something similar. Also this (my) problem is not Rom specific, so it's probably Froyo.
[Nexus One Android Development] automatek:
THANKS!! After clearing the Camera data, I've been browsing for the last 15 mins and everything has been loading up normally.

Weird that the camera data has any impact on connectivity. But for now it's working.

Thanks!
[Nexus One Android Development] myn1:
I would consider that a feature now. (∩_∩)
[Nexus One Android Development] shotta35:
Ok, yeah i'm on drugs. LOL

Anyways, c'mon guys - hangovers don't last that long!
[Nexus One Android Development] gaeng4665:
hi, i just flashed and set up the latest nightly (built 188), was on cm6 stable before. i usually replace adw launcher with launcher pro 0.8.1.0 in /system/app.

But unfortunately launcher pro is really laggy with my previous settings used on cm 6 stable (memory usage high, build cache, keep in memory etc.).

On cm6 it was blazing smooth.

Anybody any advice how i can fix that on the nightlies???

thx
[Nexus One Android Development] pwig:
I have found that sometimes you have to go delete all of the data and cache and force stop launcher pro and start over for some reason. Then it works brilliantly again.
[Nexus One Android Development] Smokeaire:
I hope it continues to work for you.

I'm not an expert at this stuff but I think I read somewhere that the camera and radio are some how linked. Maybe a poster more knowledgeable can enlighten.
[Nexus One Android Development] gaeng4665:
thx tried it but unfortunately it didn't work out...
[Nexus One Android Development] carnegie0107:
Did you wipe between versions? Coming from a stable release to a nightly you should definitely do a full wipe. You can use titanium to restore apps, but don't restore any system data. You'll have to set all that up again manually. If you use a nightly with old data left over from the stable release, you're going to see bugs--the least of which is laginess.
[Nexus One Android Development] aiewolf:
Just download it from rom manager and when it asks you to install or whatever it says, just click cancel. Reboot it to recovery and flash rom from there. Google apps should be Fine. Apparently koush knows about it, so expect it to be fixed soon.
[Nexus One Android Development] SiNJiN76:
Maybe the fix is in 189?
[Nexus One Android Development] obscure.detour:
Flashed 188 after having CM6 stable, wiped cache and dalvik. First time, my screen was unresponsive as was the touch buttons. Could only unlock phone with trackball wake. No navigation except with ball.

Repeated steps before, everything seems fine now. Seems more responsive and snappier than CM6 stable. Everything has been fine all day until I realized my phone has been off for the last couple hours. Not sure why, was just writing a paper.

Everything seems great other than that weird hiccup :)
[Nexus One Android Development] makelegs:
TSQ! (Tonight's Stupid Question)

I noticed today that I'm not getting ANY vibrate alerts for anything. Not gmail, gtalk, whatsapp, touchdown email.....nada. I have 'vibrate always' set on pretty much all of the apps and in main settings. Most ringtones set to silent or default. I really wanna blame one of the nightlies for this, but something tells me that I'm probably just a dumbass. Is this something that comes up from time to time.... where you clear data on something somewhere and then it magically works again???

Any help is appreciated....

edit: already on 189.... didn't fix it.
[Nexus One Android Development] shmigao:
Since build 188 haptic feedback stops after a while (e.g. on typing)
[Nexus One Android Development] makelegs:
Haptic seems fine.... vibrates every time I hit a button that should vibrate. Just doesn't vibrate when I receive messages.
[Nexus One Android Development] makelegs:
Crisis averted! I AM a dumbass! Turns out it was Audio Manager's fault (there's actually a separate box for vibrate alerts that apparently supercedes system settings). Guess I should have searched before I asked here. Beg everyone's pardon.
[Nexus One Android Development] lojden:
Hm, i've got bootloop with both HDPI and MDPI but not with MDPI tiny :confused: allways been like that. Anyone know how to fix that?
[Nexus One Android Development] gaeng4665:
i did what you said and it is now smooooooooooooth as before...

thx a lot
[Nexus One Android Development] gaeng4665:
so my next question is, if i'd like to update to a newer nigthly somewhen in the future without having to redo all those settings.

I know it can be done be just flashing the new nightly over the previous one and clear cache and dalvic-cache in advance. But how if someone runs the old a2sd chachesd with darktremors a2sd 2.7.5.2?
[Nexus One Android Development] trismegistos:
reset dalvic-cache with the darktrem utils in the terminal? type a2sd help to get the commands
[Nexus One Android Development] gaeng4665:
true, but if a newer nightly will be flashed, then it erases the simlinks made by darktremors a2sd script in system/app (for the dalvic cache i don't remember where the simlink is). So what do i need to do after the flash of the new nightly? and where do i need to do it (e.g. commands in recovery or over terminal)?
[Nexus One Android Development] mik101:
Did anyone elses google talk break after flashing from 188 to 189? Wiped cache and dalvik and reinstalled gapps to no avail.

Will wait for 190 before I bother to wipe but unless someone else can repeat it, then thats probably what ill have to do.

Edit, restored my backup and flashed to 189 again and all is fine... not sure what happened the first time. False alarm. :)
[Nexus One Android Development] trismegistos:
if you flash the nightly you must flash after this directly the darktremtor aps2sd zip file. the a2sd ist enabled in the new nightly. if you start your phone you can use the a2sd cachesd command to move the cache back to the sdcard. i know there is an option to reset the cache and after an other reboot a2sd build it new. type a2sd hel to get the command options in the adb shell
[Nexus One Android Development] mooselander:
Google Voice Push Notification

Have Google Voice notifications been working for everyone else? Mine have completely stopped, messages are now only received after hitting the refresh button within the app.

Did a full wipe and re-installed 189. Still no real time notifications.
[Nexus One Android Development] MarkM83:
Where did the FM radio go ?
[Nexus One Android Development] mik101:
ADW settings at the bottom when the context button is pressed at the the main screen is gone too.
[Nexus One Android Development] rickytenzer:
Where did it go? It was never in! Not yet at least.
[Nexus One Android Development] simms22:
#190 is up http://mirror.teamdouche.net/get/passion/cm_passion_full-190.zip
[Nexus One Android Development] irishrally:
My Google voice notifications are working fine. I missed a call earlier today and the icon showed up in status bar.

I'm on 189, for 5 more minutes.
[Nexus One Android Development] rammaggot:
I have a problem with twitter. I cant connect with twitter app or any twitter client

Im in the 189
[Nexus One Android Development] simms22:
ive had nooo problem with twitter on 189 or now 190. believe me, i live there. maybe its just an issue with twitter right now?
[Nexus One Android Development] mafiaboy01:
Anyone know when quick boot is going to be added?
[Nexus One Android Development] cmarti:
Well because of the lack of updates lately from Cyan I jump in this [NIGHTLY] [ROM] 190 FULL and will give it a try.

Well see how it works.
[Nexus One Android Development] irishrally:
Daily updates :)
[Nexus One Android Development] SiNJiN76:
Are you talking about the app? Isn't it available on the market?
[Nexus One Android Development] warren2781:
this is done in terminal or adb shell.

"a2sd check"

"a2sd reinstall"

"a2sd zipalign"

"a2sd cachesd or cachepart depending on where you want your davilk-cache"

if you do a full wipe you do have to install a2sd from recovery.
[Nexus One Android Development] irishrally:
I think he meant the quick "new sense" reboot.
[Nexus One Android Development] traxxus:
Build 190 works fine here.

Is there any chance team douche will integrate rSAP support?

Many radios in european cars have rSAP for contatsync over bluetooth.
[Nexus One Android Development] BritSwedeGuy:
Car Home

How many people are having problems installing Car Home from the Market?

It doesn't appear in the app screen and won't open from the Market with every nightly I've tried, and 6.0.
[Nexus One Android Development] Smokeaire:
This has been discussed in this thread, if you downloaded Car Home it will show up when you connect the phone to the car dock. There won't be a short cut unless you have the installer.apk. Do a search in this thread for better, complete explanations and instructions.

Start here: http://xdaforums.com/showthread.php?t=723844&page=590
[Nexus One Android Development] dark79:
I haven't had any trouble with darktremor's a2sd-ext and updating nightlies. My process for nightlies is:

1. Wipe cache

2. Wipe dalvik-cache

3. Nandroid

4. Flash Nightly

5. Flash Darktremor's A2SD

6. Flash gapps

After android boots, I use the "a2sd cachesdreset" command in terminal to get the dalvik cache back onto the sd card.
[Nexus One Android Development] maedox:
There is no point in flashing gapps if you don't wipe system first, because nightly will back it all up.