yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] :
Thanks T

I am dl'ing 7.1 atm
[Nexus One Android Development] meteora:
can you please provide me with step by step procedure of migrating from DT a2sd to S2E? (e.g. wipe system and data then flash CM7.1 and then reboot without doing anything to A2SD? S2E has an import function from A2SD, does it work for my situation?)

btw I have a back up of my whole apps by TB.
[Nexus One Android Development] bassmadrigal:
temasek recently switched his over, and if I remember right, it is fairly straightforward (I wiped everything when I switched, so I never used the import function).

Nandroid.

Install S2E.

Configure S2E.

Use the import function.

Install CM 7.1 (which will wipe any traces of DT's a2sd).

Done.

I think this is all it takes (maybe temasek can chime in with his actual instructions, which seemed longer than mine).
[Nexus One Android Development] thomasgatt:
Is anyone else having this problem? I'm running 7.1.0 and still has this issue.
[Nexus One Android Development] navahoo:
jap, had that too. not other solution than full wipe worked it out for me!
[Nexus One Android Development] temasek:
U using leaked Google+ 2.0? Its the cause of that probably.
[Nexus One Android Development] DaXmax:
Uninstall the leaked G+ v2.0... Is a problem to contacts.apk
[Nexus One Android Development] Chahk:
Confirmed. Leaked G+ 2.0 app is the culprit.
[Nexus One Android Development] DaXmax:
Few pages ago, i have paste a logcat... Is already confirmed that this was the culprit after i flash miui... That day...
[Nexus One Android Development] britoso:
Thanks for the info, here is the logcat of the FC while opening some contacts (i'm using the leaked google+ 2.0)

I/ActivityManager( 313): Starting: Intent { act=android.intent.action.VIEW dat=content://com.android.contacts/contacts/lookup/950i556771408.3886i573f388d0dbb0f
1e/1199 cmp=com.android.contacts/.ViewContactActivity (has extras) } from pid 10112
I/ActivityManager( 313): Displayed com.android.contacts/.ViewContactActivity: +132ms
D/AndroidRuntime(10112): Shutting down VM
W/dalvikvm(10112): threadid=1: thread exiting with uncaught exception (group=0x40107560)
E/AndroidRuntime(10112): FATAL EXCEPTION: main
E/AndroidRuntime(10112): java.lang.IllegalStateException: Top level element must be ContactsSource
E/AndroidRuntime(10112): at com.android.contacts.model.ExternalSource.inflate(ExternalSource.java:133)
E/AndroidRuntime(10112): at com.android.contacts.model.ExternalSource.inflate(ExternalSource.java:104)
E/AndroidRuntime(10112): at com.android.contacts.model.ContactsSource.ensureInflated(ContactsSource.java:99)
E/AndroidRuntime(10112): at com.android.contacts.model.Sources.getInflatedSource(Sources.java:323)
E/AndroidRuntime(10112): at com.android.contacts.ViewContactActivity.buildEntries(ViewContactActivity.java:953)
E/AndroidRuntime(10112): at com.android.contacts.ViewContactActivity.bindData(ViewContactActivity.java:532)
E/AndroidRuntime(10112): at com.android.contacts.ViewContactActivity.considerBindData(ViewContactActivity.java:525)
E/AndroidRuntime(10112): at com.android.contacts.ViewContactActivity.access$400(ViewContactActivity.java:107)
E/AndroidRuntime(10112): at com.android.contacts.ViewContactActivity$2.onPostExecute(ViewContactActivity.java:386)
E/AndroidRuntime(10112): at com.android.contacts.ViewContactActivity$2.onPostExecute(ViewContactActivity.java:355)
E/AndroidRuntime(10112): at android.os.AsyncTask.finish(AsyncTask.java:417)
E/AndroidRuntime(10112): at android.os.AsyncTask.access$300(AsyncTask.java:127)
E/AndroidRuntime(10112): at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:429)
E/AndroidRuntime(10112): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(10112): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime(10112): at android.app.ActivityThread.main(ActivityThread.java:3835)
E/AndroidRuntime(10112): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(10112): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime(10112): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:847)
E/AndroidRuntime(10112): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:605)
E/AndroidRuntime(10112): at dalvik.system.NativeStart.main(Native Method)
[Nexus One Android Development] DaXmax:
Yep the same problem as i had... Revert to v1.0.8... Then ur problems is gone...
[Nexus One Android Development] ultraviolet74:
please make Italy default APN:

mobile.vodafone.it

instead of:

web.omnitel.it
[Nexus One Android Development] erikclaw:
Is there any reason I shouldn't be able to receive pics? Used to be Iphones were an issue but couldn't receive any from an android device the other day either.
[Nexus One Android Development] yojlik:
Are you using the MMS APN?
[Nexus One Android Development] baseballfanz:
Are you able to send mms?
[Nexus One Android Development] obscure.detour:
I haven't had any issues. Try changing your user agent to N95 within messaging settings.
[Nexus One Android Development] Atento:
Are your bluetooth working correctly? I mean my bluetooth isn't pairing with no devices. For example every time I try to connect my N1 with my car stereo it ask me the pin code even if I have done this before.

Do you know how to fix it?

Thank you.
[Nexus One Android Development] Menelkir:
I know that someone maybe has already asked for this but, its a cosmetic feature: Can you guys put colored icons in settings? I mean, like tons of cm7-based roms out there, there's colored icons, and looks much more better than B/W ones (IMHO).
[Nexus One Android Development] FaithCry:
lol why not just modify a theme so that it edits that?
[Nexus One Android Development] musashiken:
Cool, looks like the the next nightly will solve the slow USB transfers to sd card.
[Nexus One Android Development] erikclaw:
Sorry been offline lately. Yes I can send mms and sms.
[Nexus One Android Development] erikclaw:
Mms apn? Not sure what that means.
[Nexus One Android Development] baseballfanz:
MMS APN = MMS Access point. Some carrier you need to set up an APN for data and a seperate APN for MMS. Only other thing like mentioned is try setting Custom User Agent.

Stock messaging app, Settings>Custom User Agent> try Nokia N95
[Nexus One Android Development] erikclaw:
Not using stock messaging app, using Go SMS pro. Was using launcher pro but changed a month or two ago. Can't tell you if that made a difference or not, don't send or receive a lot of mms.

---------- Post added at 08:17 PM ---------- Previous post was at 08:14 PM ----------

I was looking at the mms settings, I can fill in the APN manually but asks for MMSC, MMS Proxy and MMS port.

Could freezing the stock sms, mms app cause this problem? I did that so I would only get one notification when receiving a msg.
[Nexus One Android Development] tnicko:
What's the problem? You say here you can send mms :confused:
[Nexus One Android Development] N1_Fan:
Just turn off notifications in the stock messenger app and leave them on in GO SMS.
[Nexus One Android Development] erikclaw:
I can send them, but not receive them lately. With I phones I have always had a problem sending and receiving.

I defrosted it, changed the settings to what you recommended. I will turn off notifications and see what happens. Thanks
[Nexus One Android Development] quick_:
Having an issue with last couple nightlies, phone will be completely dead randomly.... Screen won't turn on, won't charge, completely dead. Have to remove the battery to get it to turn on again.

Not using anything special, stock kernel etc... Also ROM free space shows 10mb free (in titanium backup).

Also today my phone would boot then go dead or completely lock up, took me three battery removals to get the phone to work normal again.

This started happening in the last couple builds before 7.1.0 and especially with 7.1.0.

Have been flashing nightlies since cm6 and never had this problem before. I always wipe everything and restore settings and apps with titanium backup.

Anyone know what can cause this?

Thanks

Edit: I've noticed this problem only happens right after rebooting/boot.
[Nexus One Android Development] tnicko:
Ah ok. You had me confused there because you had said you could do both.

I'm using GoSMS Pro as well and the other day I had trouble sending an MMS to my wife. For the life of me I couldn't get it to work and have never had any issues with MMS before. On any ROM. I then just gave up and used the stock messaging app and it went out just fine. So I know my MMS APN was fine. Perhaps GoSMS Pro isn't utilizing the APN settings properly. Maybe that's why they allow to specify them n the app itself. But I've never had to do that before.

Did you see if the message that you're trying to receive would come thru in the stock messaging app?
[Nexus One Android Development] baseballfanz:
That's your problem right there if you "froze" the stock messaging app. It's needed to handle mms.

Defrost and turn off notification to stock app
[Nexus One Android Development] yojlik:
I'm having the same problem and on another board I frequent users there are suffering as well. I tried deleting the pairing and rediscovering and the phone never detects any devices. My laptop also cannot discover the phone in discovery mode.

I asked about it here and two people responded that they can pair just fine which means it's one of those hard to track down bugs.

I tried a full wipe and fresh install without even logging into my Google account (since that restores Bluetooth pairings) and it still failed. I didn't feel like wiping /system just to see if that would make any difference, nor did I try flashing an older build I know worked (it's been a while that it hasn't for me, I'd probably have to get RC1 to test). I didn't grab a log of it failing yet but after Tuesday when I can see how long it will be for the Nexus Prime Galaxy Nexus I'll see if it's worth it to go through the trouble of filing a bug report.
[Nexus One Android Development] mslatter:
Blank SMS

I'm having a random problem with my SMS and can't find anything in my searches. Every now and again, when I start typing a SMS message, nothing populates in the text box and the "send" button remains greyed out. If I do "speech to text" I get the same thing. The only way I can get SMS to allow me to type again is rebooting the phone. I use SMS Popup, but "believe" that's more for notifications and the core messaging app is having issues. I should mention I'm running #220.

Any ideas other than a full wipe?

Cheers,

Mark.
[Nexus One Android Development] yojlik:
Have you tried toggling the Input Method?
[Nexus One Android Development] baseballfanz:
Doesn't hurt to try and freeze the SMS pop up app to see of it's the culprit. You can always use temasek's system only wipe file.
[Nexus One Android Development] mslatter:
Hi Yojlik,

Thanks for the response. I did try that but when I select input method, I only have one option, "Android Keyboard"....so can't really toggle to anything else. So I reboot and everything works again.

I really appreciate the try to help!

Mark.
[Nexus One Android Development] DaXmax:
Do anyone use Kick Ass Kernelizer in nightlies?
[Nexus One Android Development] DaXmax:
Can i use Ch33kybutt's 2.6.38.8 SavagedZen kernel?
[Nexus One Android Development] Atento:
I tried a full wipe too, but no luck.

I will continue trying solve this problem. I'm currently changing some configs files...
[Nexus One Android Development] Navik57:
I've been noticing for the past 20 or so nightlies (it's probably before that too I just haven't paid attention) that the gmail sync will uncheck itself randomly?

I usually notice that I'm not getting any Gmail notifications, and when I go to accounts and sync, the gmail option is unchecked. Any ideas?

Also, is there any way I can set the MMS agent to default to the Nokia option? It seems my stock messaging app likes to freeze up randomly when I try to access the options. (I don't use stock anymore, just handcent, but it seems I need to set it anyway)
[Nexus One Android Development] :
Navik57

Have you tried clearing cache and data

Or, uninstall/reinstall app

Don't use MMS, sorry
[Nexus One Android Development] erikclaw:
My gmail notifications unchecks itself all the time. I always check it when installing new nightly or randomly at times if I rebooted.
[Nexus One Android Development] bassmadrigal:
If your gmail keeps unchecking the sync option, make sure that the app is stored on the internal/phone memory. If it is stored on the sdcard, it will uncheck itself upon every reboot.
[Nexus One Android Development] Navik57:
Oh, this is after wipes, system wipes, gapps reinstalls. Just haven't been able to pin down this issue yet.

---------- Post added at 07:23 PM ---------- Previous post was at 07:21 PM ----------

Good catch. Didn't realize it was installed on sd-card. Tried moving. We shall see. Thanks! =-)
[Nexus One Android Development] B1ny:
Not true. I have it on SD and it only uncheck now and then at new nightlies, but never at reboots.
[Nexus One Android Development] mslatter:
Since nobody had any other ideas on this, I did a full wipe and spent hours reloading apps from Titanium on nightly 221.... 6 hours later, same problem. I type a text, the keyboard reacts to my presses, but no text shows in the message box...and Send button remains greyed out like nothing is being typed. I reboot and it all works fine.... I've wiped cache, dalvik and fixed permissions. Not sure what else would be causing this?

Cheers,

Mark
[Nexus One Android Development] mtw4991:
I would guess that SMS Popup is conflicting with the native messaging app. I would suggest you un-install it for the time being, run fix_permissions in terminal, reboot recovery and run fix_uid mismatches in recovery, wipe cache and dalvik, then reboot. Use the native messaging app for awhile and see if the problem persists. If it does, try flashing Temasek's format-system-only.zip. It usually cures all #gremlins
[Nexus One Android Development] ahmedraza:
if i am going back to stable from nightly version then full wipe is must or just wipe cache and dalvik cache????
[Nexus One Android Development] baseballfanz:
Just flash on top of nightly, no need to wipe dalvik or cache but it doesn't hurt if it make you feel better.
[Nexus One Android Development] mslatter:
Thanks for the suggestion mtw4991... I will give it a shot! Cheers!
[Nexus One Android Development] bnguyen1983:
Had a very weird problem today. Phone died and when I got it back to a charger and turned it on, it was stuck in a reboot loop. Recovery was still fine so I tried reflashing the rom and it was still like that. Tried full wipe, cache, and dalvik cache with both the latest nightly and the release 7.1. I ended up picking a different random rom to see if it works and sure enough it did..

Any ideas?
[Nexus One Android Development] samarium:
adb logcat when you are boooting the phone may help you see what is going on

was it actually rebooting the kernel or just the gui?

it it was a kernel crash maybe you could try a different kernel like pershoot's

hopefully full wipe means you wiped system as well

---------- Post added at 06:24 PM ---------- Previous post was at 06:23 PM ----------

Have you tried going into Manage Applications and doing a Clear Data on the SMS apps and maybe the keyboard?
[Nexus One Android Development] thatguy123:
I've had this same problem. Please help! Tried reflashing everything multiple times with full wipes and can't solve the problem. Never had an issue with this before 7.1, so as of now I might have to go back to 7.0.3.
[Nexus One Android Development] quick_:
Since I had that problem I've tried a few things, first wiped and then flashed the 220 nightly. Then switched my home launcher from Launcher Pro Plus to Go Launcher Ex, and I haven't had the problem since, however the phone is still acting weird locking up, slow at times but not crashing the phone completely though.
[Nexus One Android Development] bnguyen1983:
It would go to the main screen and start loading the sd card and scanning network for about 5 seconds and then reboot. I didnt change the kernel when I loaded up a non cm rom and it worked.
[Nexus One Android Development] sitinon327:
I'm having same issue. Started out of the blue. Stock kernel...nothing fancy. Suddenly, phone completely "dead" and I have to battery pull. Mine isn't after a reboot..its just random. Starting to get annoying. Also can't figure out why kb's randomly stop reacting similar to another posters issue. I can tap/swype letters, but nothing appears....no matter which kb I use.
[Nexus One Android Development] baseballfanz:
I would at lest take a look at system space. might or might not be a problems but these rom are getting bigger and bigger.

maybe delete some un use sysytem app. worth a try
[Nexus One Android Development] sitinon327:
17 MB free in system. I usually flash system-remover script or manually delete what I don't use (Cyanbread ect). Can't pinpoint when issue started, but I'm not doing anything differently than when before it started happening. I've already tried a full-wipe (which was my first in nearly 6 months)
[Nexus One Android Development] samarium:
Hopefully your full wipe included a format of /system.

If installing a ROM results in /system filling then you may have problems later irrespective of running system_app_remover as it only free up space after you would have needed it.
[Nexus One Android Development] sitinon327:
I ran both of temasek's scripts just to be sure (nuke wipe and system-only format). I always run his system-only when flashing a nightly
[Nexus One Android Development] temasek:
Your symptoms seems to have nothing to do with insufficient /system space.
[Nexus One Android Development] quick_:
Just to follow up, after the really bad lag and constant freezing of my phone (I noticed the process that was locking up was "system") I went back to 211 nightly and my phone is back to normal again very smooth, went back to launcher pro as well... Going to hold off for a while till whatever is causing this is fixed.
[Nexus One Android Development] ViperFred:
Hi,

I'm experiencing some problems updating to the latest nightly(s) since my S2E is not working after upgrading. Didn't have these problems for builds <= 218.

Anybody else?
[Nexus One Android Development] temasek:
Roboto Fonts from ICS. Add some spice to our CM7 Nightly :p

http://xdaforums.com/showpost.php?p=18556168&postcount=10148
[Nexus One Android Development] :
No problems at all. cm7 and s2e is a great combination and running super smooth at my device.

Sent from my Nexus One
[Nexus One Android Development] temasek:
Np here too.

I'm kinda looking forward for ICS to our old but legendary N1.

I'll keep this N1 till the end of its life!

Btw roboto fonts the more I look at it the more I'm loving it. Its very readable for mobile device.
[Nexus One Android Development] DaXmax:
Me too... It looks perfect on miui but waiting for someone to port ics theme to cm or miui

Sent from my Nexus One using MIUI 1.10.14 AND IT LOOKS LIKE ICS
[Nexus One Android Development] ctfrommn:
Roboto fonts are best ever.....so clear and easy to read. Def need an ICS theme that is more mature than early releases.
[Nexus One Android Development] temasek:
Don't go over excited on off-topic. We better stop......I meant I better stop. :)
[Nexus One Android Development] ctfrommn:
Too easy to get sucked in when nothing new in nightlies.....but your right.....sorry mods, I'll be good now:)
[Nexus One Android Development] imfloflo:
@temasek Yeah good choice ;) Thanks for the font and the off-topic now back on topic guys.

Please.

Changelog bump to 7.1.0.1
[Nexus One Android Development] ctfrommn:
Why are nightlies so sporadic lately? They used to come out every morning like clockwork and ever since 7.1 came out it has been hit and miss. Not complaining....just curious.
[Nexus One Android Development] gregferns:
Yes, am wondering that too. Earlier there was the buildbot site which used to show when the next build will be out,,, now that cyanogen team has started building nightlies from github,,, any chance of knowing where this data can be found out ?

thanks in advance.
[Nexus One Android Development] temasek:
That's what we used to call buildbot waterfall....I think. Dried up, no longer available.

Now u check this

http://cm-nightlies.appspot.com/?device=passion
[Nexus One Android Development] soder:
Can I flash this on my N1 running the stable 7.1.0 ?

/Söder
[Nexus One Android Development] imfloflo:
@soder can you stop restart off topic please. BTW you can flash it at your own risk.
[Nexus One Android Development] soder:
Sorry!

/Söder
[Nexus One Android Development] sitinon327:
Have you tried partitioning SD card again from recovery?

when I wiped recently, my S2E wasns't working either. Re-running partition fixed it (back up contents of SD just in-case)

Sidenote: I listened to Google talk about thier new "Roboto font" last night and thought "meh..its FONT..who cares". Well, I just flashed it on N1 and GOT DAMN does it make a difference! Roboto = Retina Display??!! lol

....end off topic!!!
[Nexus One Android Development] musashiken:
Whoa whoa what is with the huge chunk of commits to be in the next nightly?? :D

http://cm-nightlies.appspot.com/?device=passion

Looks like the next nightly is going to be a huge one :)
[Nexus One Android Development] amolji:
might be this causing delay in appearance of next nightly :D

and yeah !! Update to 7.1.0.1 (android_vendor_cyanogen)
[Nexus One Android Development] imfloflo:
Maybe the new repo settings can be responsible of delay too.

BTW lot of bug fix nice update.
[Nexus One Android Development] temasek:
Roboto Fonts from ICS - 2nd Release. Now with Clock Font changed.

Exception granted from imfloflo (I think :p)

Pls let me know if the clock font isn't right.

Mirror: http://www.mediafire.com/?izyhjb19jnyi7pm
[Nexus One Android Development] Yoz182:
#227 is up :)
[Nexus One Android Development] musashiken:
Cool... but the changelog isn't updated yet.. so we can't be 100% sure all the recommended changes are there.
[Nexus One Android Development] temasek:
100% will be.

The last commit was hrs ago.
[Nexus One Android Development] musashiken:
Lol, I'll flash away anyway :D
[Nexus One Android Development] temasek:
I had that hrs ago (my own Kang) :p

Forgotten to upload to my folder b4 I went for wedding dinner...

*burp* ...*hiccups*.....*burp*
[Nexus One Android Development] ctfrommn:
What changes from nightly in your Kang?
[Nexus One Android Development] temasek:
Not the right place to reply. Maybe a short comment.

I don't cherry pick cuz I'm lazy (not difficult actually). I just compile early than the buildbot. Usually for my own use and I just upload to my sharefolder when it is available.
[Nexus One Android Development] ctfrommn:
Do you have a thread for this?
[Nexus One Android Development] temasek:
KANG builds w/o cherry picks are not popular so ....no don't have one.

Edit: So lazy .... my time on Xda I've only created few threads, one is quite good tip...."How to speed up new market 3.xx over wifi?"
[Nexus One Android Development] Atento:
The clock font changed after flash this file. Thank you once more. It is better to read now.
[Nexus One Android Development] ctfrommn:
Which clock? Lockscreen? Widget?
[Nexus One Android Development] temasek:
Lockscreen clock. Font from ICS. Some early ICS for our N1.

Hmm..... lets talk back nightly. I tested airplane mode I can standby over 10 days. Omfg......

Battery life on cm7 with N1 is damn fantastic now.
[Nexus One Android Development] ctfrommn:
New build running smoooooooth...
[Nexus One Android Development] temasek:
Try the nightly with Juwe11's Ram Optimization Script....

My recommendation.
[Nexus One Android Development] ctfrommn:
I was using that....dumped in favor of Zep's Supercharger scripts.
[Nexus One Android Development] kaiser_tytnii:
is #227 gonna become 7.1.0.1 bugfix if I did not misread the changelog?
[Nexus One Android Development] soder:
+1 on that. I've also noticed a better battery life the latest weeks...

/Söder
[Nexus One Android Development] ctfrommn:
Hmmm haven't been using stock kernel for a while now. maybe I will keep it next flash. Tiamat is very good alternative for battery though.