yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] jonas916:
Would that work on a clean install? My concern was how to enable adb during the set up. Is it on by default until its logged in? My understanding was that it was disabled by default.
[Samsung Galaxy Nexus] conceptxo:
EXPERIMENTAL build 9/9 now available.

Put this through every pace. Test everything. Specifically radio stuff, but no, really, test EVERYTHING. Leave no rock unturned. Fair warning: com.android.phone crashes and then immediately respawns in some instanses; appears to be during transitions. Please, please log. I personally am seeing aggressive attempts to establish mobile network connections of both kinds(voice/data) - and they appear to be working, and quite well. (Other than the crashing of com.android.phone, which again, respawns very, VERY quickly.)

I am also building a standard NIGHTLY now, as some of these issues may put off more general users, which is understandable; I intend NIGHTLY builds to be as normal and workable as possible for the end user. But there's issues that require more pressing attention, hence new EXPERIMENTAL builds.

The idea here is to have resolved 3G/4G and 4G/3G transitions, and doing so with great speed(ie. no waiting for 45+ seconds for data to reconnect). There's probably still work to be done, but it needs to be noted. So, one last please - PLEASE give detailed information about what's going on for you, and include logs. If you can't include a log, I apologize, but don't bother reporting it - at this point, I need lots of detailed information to get any idea if and when we can do all the fixes necessary to go official again. I want it just as bad as the rest of you.

I'll post again with the normal NIGHTLY.

Edit: last thing: If you report an issue and don't include which build you are using (NIGHTLY vs. EXPERIMENTAL) I will ignore the hell out of you. and you'll curse my name forever. And it will be all you fault.

;)
[Samsung Galaxy Nexus] conceptxo:
!! Hm, you may be right - either try to see if it logs until login (lockscreen), or I could make an ENG (engineering) build to log these kinds of issues.
[Samsung Galaxy Nexus] phishfi:
Skip adding your Google account until after you go to developer options and enable it. So just select No on every option when you first boot to android then go to something like gmail and add your google account.
[Samsung Galaxy Nexus] dwreck420:
cm account?

so i skipped the creation of CM account when it came up on first boot, now i want to set it up but cant seem to locate the option. any ideas?

[edit] nevermind, i found it under accounts
[Samsung Galaxy Nexus] GoSooners345:
I'm tempted to come on over from 4.2

The boss is here
[Samsung Galaxy Nexus] GoSooners345:
Why is text messages not going through if data is turned off?

There is a bug in the patch relating to MMS and SMS Transfer. If data is off SMS Doesn't send or receive. The problem is Text messages aren't supposed to rely on the data connection.

This pic is what i am talking about
[Samsung Galaxy Nexus] jesusice:
Are you using Voice+? Because that routes SMS through data.
[Samsung Galaxy Nexus] dwreck420:
am i the only one experiencing this on 9/9? i had to flash back to 9/5 and the problem stopped...
[Samsung Galaxy Nexus] jjhrrsn:
No I'm getting it as well but no log as I'm going golfing
[Samsung Galaxy Nexus] Wickster:
Are there any reliable log collector apps out there? Cause I'm mostly at work all day, so I have no access to a machine that can generate a log for me.
[Samsung Galaxy Nexus] conceptxo:
NIGHTLY 9/10 now available. Does not include experimental radio fixes as seen in 9/9 EXPERIMENTAL.

Please use pastebin for posting any kind of log.

9/9 EXPERIMENTAL users: com.android.phone is supposed to die, a lot. It is supposed to reconnect right afterwards. One user posted they never reconnected, I looked at the log posted and didn't quite see what happened. Another / more context would be very helpful.

If you have access to a machine to take logs, I recommend using

adb logcat -b radio

to capture relevant radio information.
[Samsung Galaxy Nexus] Ep3n3wp:
Does 9/10 have cm account?
[Samsung Galaxy Nexus] tommy1121:
i am getting 3g trying to connect after phone calls and the only way i can get it connected is reboot. i couldn't get lte connection. i did a profile and prl, also reflashed the radios. i did not format system on install on experimental. i would do more diagnostics but my charger port died and am waiting for new phone to arrive. when was on 3g it seemed that i had little to no internet. i have attached the link to my log for reference. its about 9000 lines long

http://pastebin.com/wFjzgbU3
[Samsung Galaxy Nexus] conceptxo:
Yes. It's been added to the build system.

Try doing another one with adb logcat -b radio. There's a lot of stuff going on there, some of which is confusing. I'm on 9/10 on LTE, also did calls on 3G earlier, and I dirty flashed from EXPERIMENTAL.
[Samsung Galaxy Nexus] chasew83:
flashed exp this morning and its running great! dont have lte here and i did have one 3g drop when my work wifi network was reset. i do drive through a lot of lte on my way home, so i will start running a radio log before i leave work to get all transitions. but so far so good on the actual rom running well.
[Samsung Galaxy Nexus] Wickster:
9/9 Experimental has been running good for me so far today. I have seen it switch between 4G to 3G and back to 3G in quick succession...all with no error messages popping up. I've been sending SMS all day as well and so far it has gone through without a hitch. I have Google Voice installed but I have the SMS route through Sprint in the settings since I only use it for voicemail and it hasn't bothered me with SMS errors so far.

Of course I haven't made much phone calls today. I think I had only made one phone call while running 9/9 experimental and I was observing if it would cause an error after the phone call, but it just took a few seconds to connect back to 3G with no problems.

Probably the only difference I have with everybody here is that I'm running Fancy Kernel R40 4.3 Standard...which I installed yesterday and today when I was having RAM problems and it seemed to fix it. But I don't know if that has anything to do with 9/9 Experimental running okay here.
[Samsung Galaxy Nexus] dwreck420:
yes, at least in my case it was coming back right after. maybe shoulda added that, 9/9 is fine
[Samsung Galaxy Nexus] chasew83:
got some logs on the way home. not good from just messing with it during the logs. though things handed off ok, in general, there were some problems

log 1: https://www.dropbox.com/s/tq0dq7hbrn17sn5/Log_2013-9-10_18-42-02.txt ....got solid wifi to 3g and 3g to wifi handoffs but when it went from 3g to 4g and back i totally lost data. made a phone call and data seemed to come back fine. had to reboot to get data back.

log 2: https://www.dropbox.com/s/j0vki2h2z296cvi/Log_2013-9-10_19-00-02.txt ... once again got data drop on handoffs and when i got home i noticed a phone fc error. wifi hooked up fine though.

hopefully these will help, btw stayed on stock kernel even though i prefer fancy r40. oh and i was on the 9/3 nightly and data was basically flawless, noticed a couple times it disappeared and had to reboot, didnt get logs of that sorry.

edit: just saw the paste bin comment. gotta try and figure that out. sorry
[Samsung Galaxy Nexus] riggsandroid:
Pastebin comment was I'm sure just to prevent thousands of lines of log in the thread. Sure OP won't mind your links.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] phishfi:
So, at first I was like "NOOOOOooooo" but now I'm like "YEEEEEEEEESSSSS"...

I updated to the experimental this morning and everything *seemed* alright. I left the phone in the car (can't bring it into the building in which I'm working) and when I came out for lunch I couldn't get data to save my life (COULD be exaggerating, but still, it wouldn't work). Anyways, it stayed that way, SMS and calls only, until about an hour ago when I wiped system and reinstalled the experimental build and gapps. Haven't lost signal at all yet, and I'm getting a slightly better signal than I have been lately (considering the fact that I'm staying in a building with serious cement walls).

Thanks so much Concept, you're awesome!
[Samsung Galaxy Nexus] conceptxo:
Yeah, I just didn't want to wade through debug soup in the thread. I'll take a look at those, thanks.

Well me and everyone at CM gerrit are still trying to iron out all the CDMA stuff, so every report helps. There's some good progress though on a variant of the 9/9 fix.

In other news, Sean, and another, Michael Limb, are setting up a cm-10.2 branch for toroplus so our compatibility fix can be accepted. Making data not hell is still an official requirement(more or less), so we still have some work ahead.

I'll read over all this later this morning, thanks.
[Samsung Galaxy Nexus] chasew83:
i had to go to my nandroid, data just wasnt being reliable. seems like things took a step back from the nightly i have been running.
[Samsung Galaxy Nexus] conceptxo:
Were you using experimental still? I would ask if you would flash onto 9/10 nightly, it's an update to that style of builds (no experimental radio changes) and includes new features/fixes unrelated to mobile data.

You could dirty flash or:

1. Wipe System

2. Wipe Caches

3. Leave data alone

4. Reflash nightly + gapps + su
[Samsung Galaxy Nexus] chevlar:
Here's a radio log of my commute this morning. Went from home Wi-Fi to a walk & bus ride through patchy 3g/4g and back to Wi-Fi at work. Data seemed to drop, and I couldn't get it back with airplane mode toggle. It did ultimately return on work Wi-Fi. Running version 9-9 experimental.

http://db.tt/8cEQ5mbk
[Samsung Galaxy Nexus] chasew83:
yes i was still on experimental. i can give 9/10 a go though.
[Samsung Galaxy Nexus] Wickster:
I'm curious to know what Sprint CDMA/LTE Radio is everyone here using? And if it matters with the Experimental build on about getting good data transfers and aquisition.

I'm using the GA02 Radio and as I've mention before, the 9/9 Experimental has been really good to me. No data drops, no WiFi->3G->4G->3G->WiFi delays or issues.
[Samsung Galaxy Nexus] phishfi:
I completely lost data for a time portion of the Afternoon today. Only fix was to re flash the experimentally nightly, which but everything running well again. I'll test it out on the same drive tomorrow afternoon and see what changes.
[Samsung Galaxy Nexus] tommy1121:
Had a 3g time out and a launcher crash. Other than that seems solid great hand shakes for 4g to 3g. I think we are 95+% to bring official again

P.s. got new phone and flashed this ruin only made a twrp backup of stock and I'll be saving it to my Google drive later on today if anyone needs a complete stock recovery. I didn't login to Google either. Just unlocked boot loader then loaded so I could reboot to get into recovery. Doesn't include stock recovery.

http://pastebin.com/Jc7N7C85

Update: lost data after post and had to reboot. (Lol, foot in mouth)

http://pastebin.com/hBx05zq9
[Samsung Galaxy Nexus] Scaribay:
I'm in the same boat as you. Data is pretty solid. An occasional drop, but never got more then a few seconds. No issues going from wifi-4g, I even think I had 3g minute before it went back to 4g. Love the rom. Thank to conceptxo for the hard work and dedication.
[Samsung Galaxy Nexus] Garridon:
The area behind the blue squiggly line, is that what the system is using? If so, why is it using so much!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] poo706:
Looks like a crude pot leaf.

[poo]
[Samsung Galaxy Nexus] Garridon:
It was supposed to be an arrow with a line :banghead:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jrotert:
Data works on 09/10 nightly!

Sorry for the all-caps in title, but this is the first 4.3 ROM I have flashed where data hand-offs actually work. I toggled 4g, 3g, airplane mode, wifi repeatedly as well as drove around town switching b/w towers and data works as it should. Maybe a 10--15 second delay before regaining blue bars sometimes (but sometimes there was a similar delay on my stock 4.1.1 Toroplus ROM).

For everyone waiting for a TP 4.3 ROM with actual working data, this one seems to be the one.

Much thanks to conceptxo and devs at CM.

And I am running latest GA02 radios.

Nandroided back to stock 4.1.1 for now; have to wait for days off from work to properly flash CM 10.2 ROM with SD Card migration issues and such.
[Samsung Galaxy Nexus] conceptxo:
Yeah, the blue part of the bar is currently-in-use RAM, which means the system may be reserving it, or an app may be using it.

SD Card migration issues? Please enlighten me.

New builds will be out today, both NIGHTLY and EXPERIMENTAL - which will feature a new version of the patch we've been testing in experimental. No more com.android.phone closures.

EDIT: Also, a big thank you to everyone who has posted logs and information.
[Samsung Galaxy Nexus] jrotert:
SD Card migration issues? Please enlighten me.

Nothing to do w/ your ROM in particular, just what is involved in flashing from any pre-4.2/4.3 ROM, i.e., moving stuff from sdcard to sdcard/0. In my case, about 20gb worth of music, a gb or so of TB backup files, and assorted ringtones.

Just wanted to make sure I had working data before doing all of the above.
[Samsung Galaxy Nexus] silver03wrx:
Where i live i get constant switching from 3g/4g when i go up or down stairs and if im out front or out back. So ill let u know how the new experimental does once its uploaded
[Samsung Galaxy Nexus] sasidhar79:
How did u capture that screen shot ?

got it , thank u
[Samsung Galaxy Nexus] GoSooners345:
How is the official status progress coming along

The boss is here
[Samsung Galaxy Nexus] conceptxo:
Slow.

Anyways, I was a little busy yesterday, builds for 9/13 will be posted this afternoon.
[Samsung Galaxy Nexus] xvanwilderx:
Hopefully not a dumb question. I'm currently on the Vanir 4.3 rom. If I want to try this rom out, do I need to do a clean install (wipe data)?
[Samsung Galaxy Nexus] Asmodicus:
Well, it is kind of a dumb question, but I'll answer anyways.

Yes. A clean wipe is always recommended when moving from one ROM to another. Even when going from one build to an updated build of the same ROM, I always do a clean flash because it helps avoid potential problems. Best to be fresh!
[Samsung Galaxy Nexus] conceptxo:
I'm actually going to chime in here, and say that this is incorrect.

While trying to keep this as short as possible, Android has "data partition formats" that each version expects. On an OTA update, there is a script included to migrate your data partition over to the new arrangement, which is why people who OTA from lets say, 4.2 to 4.3, don't have to wipe their data.

Once you've moved over, or in other words, once your data partition is in the correct arrangement, you can flash in-between ROMs that use the same version of Android without wiping data. When you do this, however, you must wipe /system, /cache, and /dalvik-cache. Whatever copy of Android you load up next goes through your data partition, sees your installed apps and your /data/media area, and begins to dexopt(Android is upgrading....Optimizing App x of y...).

There are only a few, rare exceptions to this case.

Edit: Asmodicus, if you're truly wiping clean each time - do yourself a favor and stop. Especially when moving between my releases, you can just dirty-flash or do a system&cache wipe.

There's no reason to blow up your data and resync your apps so often.
[Samsung Galaxy Nexus] conceptxo:
Builds are uh, still building, but there's far better news: our compatibility patch has been accepted and merged into CM. Once the branch setup is complete, we're(to my understanding) ready for official.

http://review.cyanogenmod.org/50222

A public thank you to everyone involved that helped to achieve this. Sean, Michael, Richard, and far more: you're awesome.

Stay tuned for the future of toroplus CM.

EDIT: 9/13 nightly is uploading.
[Samsung Galaxy Nexus] Asmodicus:
Well, that was just what I have been told was best to do ever since I got into rooting and custom firmware and whatnot. It's just something that I believe it helps me to avoid having any problems after flashing. Maybe I'm being to anal about it, but I don't don't care. It makes me feel better when moving between any build and I haven't had hardly a single problem that I couldn't fix pretty quick in all the time I've had my gnex.

The majority of the time when I'm flashing and have to resync my apps, I do so over wifi. Even if I didn't I have unlimited data and usually around -65dbm LTE where I live, so blowing up my data isn't something I actively worry about.​

;)
[Samsung Galaxy Nexus] conceptxo:
You're all good.

Nightly 9/13 now available.
[Samsung Galaxy Nexus] something15525:
Yeah, hopefully we'll have official nightlies here soon. I keep bugging developer relations for CM, since I'd really like to take over as the toroplus device maintainer. Now that Sean and I's change has been merged, hopefully that will happen soon!

Fingers crossed :)
[Samsung Galaxy Nexus] conceptxo:
Well hey there! If you need an number two, well, you know who to contact. :) I've been busy with Richard and Shareef working on CDMA telephony.
[Samsung Galaxy Nexus] something15525:
Oh, are you talking about the legacy repo to improve 3g/4g switching?
[Samsung Galaxy Nexus] conceptxo:
I am! Its essentially changing detection stuff for legacy CDMA stuff, which, apparently, even includes the S3 on Verizon. (Trying to make appropriate evaluation statements that work across the weird range of possible return values for certain functions inside telephony bring up)

I guess I just being up this because I just never got around to making CFLAG stuff - in part because of the degraded learning experience that the IDE generation(me included) got in terms of build tools. (I am embarrassed at how much I still have to learn about GNU make and the makefile system). If and when more work arises for our platform, I am more than able to contribute in a significant fashion.

Sorry to bother. Have a wonderful evening!
[Samsung Galaxy Nexus] something15525:
Yeah haha, you aren't the only one who's learning on their toes here. I just jumped in to the whole Android development thing here a little over a year ago, and I haven't looked back since! :) And now I have my own ROM that's running on a bunch of devices. I still have so much to learn though, and it's pretty exciting haha

---------- Post added at 07:08 AM ---------- Previous post was at 07:07 AM ----------

That's weird, it didn't quote you the first time :P
[Samsung Galaxy Nexus] conceptxo:
Yeah, I'm essentially in the same boat - started in some form or another with Android development about a year ago. My current favorite personal achievement has been doing system and sensor bring up on a raspberry pi I made run Android as a basis for an autonomous robot I built last year as a research endeavor. Getting a working compass and accelerometer was, well, an epic challenge. I live for this stuff, so again, I'm around and available. Feel free to email me if there's more to be done for our device's situation.

Thanks again!
[Samsung Galaxy Nexus] jrotert:
Update

Dirty-flashed 09/13 Nightly over 09/10 Nightly last night. Ran all night (I work nights at a job which entails a lot of driving, i.e., a lot of data hand-offs) and experienced no major hiccups. An occasional data drop now and then, but would always regain blue bars a short time after (5--30 seconds) with no input from me, e.g., toggling airplane, 4G, network mode settings, etc.

Keep up the good work.

Now that 4.4 is slated for release mid-October, I have to ask: will the 4.3 telephony fix carry over to 4.4 or will esteemed devs have to start from square one again?
[Samsung Galaxy Nexus] jesusice:
I don't think anyone knows the answer to that until 4.4 is released.

---------- Post added at 02:24 PM ---------- Previous post was at 02:19 PM ----------

This is new to me as well, how sure are you about this? I mean, in /data is not just user installed apps but also stored information about system settings, such as custom lock screen targets for example. Wouldn't having this information hang around potentially cause problems? What if the new ROM doesn't even have those features that data is retained for?

I always full wipe if I'm changing ROMs and just like dude said I've never experienced the problems that other users seem to. (Blowing up data is not a concern, that's what Titanium Backup is for)
[Samsung Galaxy Nexus] conceptxo:
Hey! You bring up a great point. In the example of lock screen shortcuts, its my understanding that that would setting/property would essentially lie dormant until the system attempted to read it again. So, for example, if you moved to AOSP from CM and back again, AOSP would never notice/care about those values, because there's no code in there to look it up. Once you reinstalled CM, it would find the property again during its normal boot-up process.

I suppose there is the possibility of moving between different custom ROMs that provide the same functionality(ie. Lock screen shortcuts) but implemented or saved in a different manner causing issues. I'd actually be interested to see what happens on a technical level here.
[Samsung Galaxy Nexus] Wickster:
Just thought I'd ask. Are the experimental radio changes being merged with the new nightlies now or are we getting a separate experimental build in the future?

And thanks for the hard work (you and all those involved), it only does keep getting better and better.
[Samsung Galaxy Nexus] conceptxo:
Haha I completely forgot. Yeah we'll have a 9/14 experimental, the new version of the patch wasn't quite ready at build time last night.

And thanks!
[Samsung Galaxy Nexus] something15525:
Do you have a repository pushed to GitHub (or somewhere else) that I could check out for the legacy CDMA telephony? It would be much appreciated :)
[Samsung Galaxy Nexus] conceptxo:
There actually isn't really a separate repo where work is being done, it's really more in the form of individual patches/cherry-picks.

The ones in questions are(Where the first in the list are dependencies for those further down the list):

http://review.cyanogenmod.org/#/c/50035/

http://review.cyanogenmod.org/#/c/50036/

I assume the reason for this is the hectic changes constantly occurring here as more devices are tested - it's better to just centralize it on gerrit than to try and split it out to some repo on GitHub.

If you're personally interested in my github, however, it's linked in my profile. Not a whole lot interesting there, other than parts of my robot, and private repos for projects that people are paying me for. :)
[Samsung Galaxy Nexus] conceptxo:
Eh, hell. You've inspired me Michael - I'll throw up repos for the new CDMA stuff - they'll be around tomorrow.(EDT) (Yes, I know I'm lazy)
[Samsung Galaxy Nexus] something15525:
Haha, no worries man! I thought it just might be based off some non cm repo so that's why I thought it would not be just a change, you know? Hit me up with a link when you get it on github though :)
[Samsung Galaxy Nexus] moon_man_e:
Maybe its just me but my Google calendar won't sync. Anyone else having this problem or have a resolution?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] something15525:
Well if you download the calendar from the play store, it doesn't replace the AOSP one for some stupid reason. I personally removed the AOSP calendar from my ROM so they wouldn't conflict, cause when the are both present it screws up the sync for the calendar.
[Samsung Galaxy Nexus] moon_man_e:
I only have one installed but it seems it won't sync. I was thinking it's a gapps problem. I used the one provided. Should I use the one released by Google instead? Also would that get rid of focal...I actually like focal lol
[Samsung Galaxy Nexus] something15525:
No, it shouldn't get rid of focal :).

Just use the one at goo.im/gapps for cm-10.2
[Samsung Galaxy Nexus] Scaribay:
I use jorte calendar and then just sync it to my Gmail account...it does the job for me...