yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bisbers:
Excellent. Did you create a flashable zip or just push the files? Mind uploading the ones you used?
[Samsung Galaxy Nexus] bigbear6708:
Nope

---------- Post added at 03:51 PM ---------- Previous post was at 03:50 PM ----------

Or just install the euroskank nightlie and flash back to cm when its fixed..I go back and forth all the time. I wipe system with each flash...no probs yet!!
[Samsung Galaxy Nexus] PDR447:
I didn't create a flashable(yet...) but here are the files in a simple zip archive:

https://dl.dropboxusercontent.com/u/14472274/telephony-archive.zip

I might get around to a flashable zip later. going to lunch now.
[Samsung Galaxy Nexus] bill.allrobots.org:
I adapted your files to a flashable:

https://www.dropbox.com/s/cd7yuy4j9k2398r/fix_telephony.zip

[Edit: okay, link put back since it's still useful to other roms.]
[Samsung Galaxy Nexus] hotrodwinston:
I'm traveling and will be going thru a lot of LTE/cdma/evdo handoffs so will report if it works.
[Samsung Galaxy Nexus] bisbers:
I just pushed the framework and it works great - phone #, MMS, etc.
[Samsung Galaxy Nexus] JeeperDon:
I'll remember this the next time something breaks that you can't live without that I never use. :D

It's just general principals to me that everything should work. In this case, the MMS issue is not really an MMS issue, but a symptom of a different problem, which may byte you in the arse some other way.
[Samsung Galaxy Nexus] hotrodwinston:
Update : LTE / CDMA handoff with posted telephony fix works perfect - will post back once I hit 1x (roaming on sprint network - where most of my issues have happened)
[Samsung Galaxy Nexus] aeidian:
Can't get nudes if we can't dl the message, duh.
[Samsung Galaxy Nexus] bigshotproducer:
Worked wonders! Thanks!!!!!
[Samsung Galaxy Nexus] swyecso:
Haha flashed and my phone went crazy with a backlog of pics and group messages. All is well in the universe again (It didn't really bother me that much)
[Samsung Galaxy Nexus] bigbear6708:
Haven't flashed a nightlie since 8/18...has battery life gotten any better since??
[Samsung Galaxy Nexus] bigdjeff:
I haven't noticed a difference, however I am a power user. I've been getting about 3 hours out of each battery, I have 3. 8/30 build... What kind of battery life are people seeing these days with their toro, any as bad as mine? Any better? I'm using the standard 1850 mah. battery?

---------- Post added at 05:16 PM ---------- Previous post was at 05:11 PM ----------

Is anyone else having problems with random apps force closing? Bleacher report and titanium backup to be more specific on 8/30 build? I've tried force GPU rendering on/off without success.
[Samsung Galaxy Nexus] hotrodwinston:
Update 2: after leaving Verizon signal things continued to work ok ( considering I was in almost no signal) but noticed once I got back in vzw signal I did have to reboot to connect to data. But on the bright side no battery draining activation call loop on roaming with no data.
[Samsung Galaxy Nexus] kuronosan:
That file doesn't flash for me in TWRP.
[Samsung Galaxy Nexus] bill.allrobots.org:
assuming you mean mine... any error?

---------- Post added at 08:15 PM ---------- Previous post was at 08:06 PM ----------

I re-wrote it in edify. Let me know how it goes:

https://www.dropbox.com/s/sjow1uak8nwt0n2/fix_telephony2.zip
[Samsung Galaxy Nexus] kuronosan:
Latest version of twrp. Just says failed. Maybe I'm doing something wrong. I'll try the second one.
[Samsung Galaxy Nexus] eyekyu:
I just noticed after upgrading to 10.2 the my PRL, MIN & My phone number all list Unknown
[Samsung Galaxy Nexus] bill.allrobots.org:
We've been actively talking about this problem for a while (it's the MMS bug). Summary: Flash the zip I posted above or wait until the next nightly (the fix was already merged).
[Samsung Galaxy Nexus] eyekyu:
awesome, thanks for the quick reply.
[Samsung Galaxy Nexus] mwalt2:
You probably don't have to reboot. Toggle airplane mode or data. That usually works for me. I think this problem exists on all toro 4.3 roms and I have not seen a 'true' fix for it yet.
[Samsung Galaxy Nexus] kuronosan:
Yea still a no go for me guys. Ah well.
[Samsung Galaxy Nexus] bill.allrobots.org:
Weird. No idea what's going wrong without more information. The only thing I can even think of is signature verification (the package is intentionally not signed), but that shouldn't be causing it to fail. Luckily, a new build should be coming today with the fix in place (Jenkins died yesterday or it would be there already).

Edit: I just booted TWRP 2.6.1.0 and installed with no issue. Sorry I can't help more.
[Samsung Galaxy Nexus] tattedupboy:
I just did a clean install of the 8/30 build and it's not prompting me to sign in to my cyanogenmod account (which I set up on my computer prior to flashing). How do I sign in to my cyanogenmod account on my phone?
[Samsung Galaxy Nexus] bill.allrobots.org:
CM account is not merged into the nightlies yet.
[Samsung Galaxy Nexus] kuronosan:
It might be what I'm downloading with. I'll try again.

Edit: yea apparently es downloader thinks the link you gave is an active zip but it keeps downloading the webpage instead.
[Samsung Galaxy Nexus] tdiman:
Just compiled the latest nightly (10.2-20130901) and the PRL, MIN and Phone Number issues are fixed. I haven't tested with an actual MMS yet.

Does anyone know what the deal is with the updated 4.3 binaries here: https://developers.google.com/android/nexus/drivers#torojwr66v

They aren't in the latest CM-10.2 build, and I guess I'm unsure if they're any different than the 10.1 binaries. I wonder if those would also help with any of the lingering issues.

-tdi

EDIT: confirmed MMS came through fine. I did wipe system/cache/data manually before the install.
[Samsung Galaxy Nexus] underwaterjr:
If you go to TheMuppets github you can see that the updated binaries are being used to build 10.2.
[Samsung Galaxy Nexus] tdiman:
Thanks, I spot checked a few of the subdirectories and indeed you are correct.

Luckily TheMuppets is what I used to build in the first place. However I did have to add the github muppets projects myself to the build --

Do the CM10.2 nightlies also use TheMuppets?

-tdi
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
From what I understand, the binaries are the exact same as they were before. Nothing was changed for 4.3. At least, that's what the Shiny dev said.
[Samsung Galaxy Nexus] TuxDroid:
What's TheMuppets repo used for? I haven't heard of it before now.
[Samsung Galaxy Nexus] tdiman:
It is a repo that keeps the latest proprietary binaries. It is used in place of keeping a phone plugged in and manually running extract-files.sh

See https://github.com/TheMuppets

To use, in my /android/system/.repo/local_manifests I've got a file roomservice.xml that I put together as a compilation from various example versions online (see below)

I should note that I haven't seen others use widevine or nxp in other copies of roomservice.xml I could find online, but since they're part of the google binaries I'm not quite sure why they aren't included always. My copy compiled just fine. Again, I don't know what the official CM uses. If someone wants to pull out the cm manifest it would be worth comparing. get.cm should have the updated version within a few minutes, it is compiling now.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="http://github.com/" name="gh" revision="master" />
<remote fetch="https://github.com/TheMuppets/[/url]" name="TheMuppets" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="gh" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_imgtec" path="vendor/imgtec" remote="gh" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_broadcom" path="vendor/broadcom" remote="gh" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_invensense" path="vendor/invensense" remote="gh" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_widevine" path="vendor/widevine" remote="gh" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_nxp" path="vendor/nxp" remote="gh" revision="cm-10.2" />
<project name="CyanogenMod/android_device_samsung_toro" path="device/samsung/toro" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_tuna" path="kernel/samsung/tuna" remote="github" />
<project name="CyanogenMod/android_device_samsung_tuna" path="device/samsung/tuna" remote="github" />
<project name="CyanogenMod/android_device_sample" path="device/sample" remote="github" />
</manifest>

-tdi
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
So is there anything on the 8/18 build that DOESN'T work? It seems very stable from my use and I haven't encountered any bugs. May just stay on it until the monthly or stable builds start...
[Samsung Galaxy Nexus] tdiman:
Sure there's things that don't work. The question is whether those things are meaningful. See http://changelog.bbqdroid.org/#/toro/ and the merges between 8/18 and 9/1 -- if any of them seem meaningful to you, go for the newest one. Considering a large number of people have been on 8/18 with little complaints, its at least probably a safe place to hold for awhile. Maybe hold there until the CM Account stuff merges?

I just updated because I was on a very early August build and the delays with reconnecting to the 4g network were driving me nuts, and I was also on a pre- goo.im gapps that was working but a bit wonky. My work happens to be in one of the few places that barely has any network connection.

I'll find out Tuesday if the current build helps out. Some rudimentary testing from home (good network here) appears to me to show fast network reconnecting when going in and out of airplane mode in the 9/1 build.

-tdi
[Samsung Galaxy Nexus] hotrodwinston:
I Tried airplane mode toggle and data no joy - only reboot fixed it. Anybody have any data issues with 902 yet? Test MMS?
[Samsung Galaxy Nexus] underwaterjr:
I'm pretty sure all the official nightly builds are done with TheMuppets proprietary repos. That's what I use when I build for myself. That way they are always up to date if something new gets pushed to github.
[Samsung Galaxy Nexus] midgarsormr:
The mms issue seems to be fixed for me on the 9/02 nightly. Great work!
[Samsung Galaxy Nexus] silfa718:
I have had a bunch of MMS come through, but my stock app still shows 9 messages

???? any ideas
[Samsung Galaxy Nexus] t1.8matt:
anyone know if the MMS flashable zip fix will work on other CM based roms back on page 364 i think?
[Samsung Galaxy Nexus] carpenter311:
Data handoff seems horrible. I'm stuck between 3G/4G/WiFi a lot. Reboots will fix . airplane isn't this time
[Samsung Galaxy Nexus] ExodusC:
Pretty much. I've had this since switching over to 10.2 from 10.1 nightlies.

I speculate that the people claiming to not have connectivity issues might not be constantly bouncing between lots of different towers like many of us do.

If I stay at home, I can have a solid LTE connection, no problems. If I go somewhere where I bounce onto 3G, I completely lose data connectivity (despite my phone reporting a 3G connection). So I wonder if the issue is with 3G connectivity.

Anyways, I just hope it's something that doesn't require a radio update from Verizon to fix, because if that's the case, we might be screwed.

We just have to play the waiting game and watch the commits, I guess (unless someone wants to ask our device maintainer about the issue).
[Samsung Galaxy Nexus] johnhimm:
The consensus the data drops will and 3g/4g hand-off lag will not be fixed until Verizon release new LTE radios.
[Samsung Galaxy Nexus] JeeperDon:
A more interesting question is... if the hand-offs worked fine in 4.2.2, why did Google have to dork with in 4.3 such that we now need VZW intervention to get back to where we were in 4.2.2? :confused:
[Samsung Galaxy Nexus] zandroid:
From what I have seen reported in the CM based ROM threads, Carbon, CRDroid, etc., it is working.
[Samsung Galaxy Nexus] bill.allrobots.org:
Shouldn't new builds of these ROMs include the fix? Or do they not do nightlies?
[Samsung Galaxy Nexus] zandroid:
Yes, you are right. Carbon does a nightly and includes the fix. CRDroid, I think, does something closer to a weekly or when CM includes a substantial fix in a nightly, like the most recent that fixed MMS. I just used those two as an example of ones that reported it working. Other CM based ROMs may not be updated as often, and the fix would still be useful.
[Samsung Galaxy Nexus] bill.allrobots.org:
Eh, okay, I guess I should restore the link, then---I removed it when I thought it was no longer necessary (to avoid confusion).
[Samsung Galaxy Nexus] hotrodwinston:
Maybe they were fixing something in the way Android handles tower handoffs and it just does not mesh with the old drivers? Maybe once we get new drivers it will work better than 4.2.2? At least that's what I hope.
[Samsung Galaxy Nexus] mouf32:
9.2.13 Nightlie fixed MMS.
[Samsung Galaxy Nexus] ejkeebler:
does it need a fresh wipe? cause my wife and I's are both still not sending or receiving MMS.
[Samsung Galaxy Nexus] mark manning:
A great rule of thumb is that when you're having issues that other people don't have or have issues that other people report to be fixed. Wipe!
[Samsung Galaxy Nexus] greyhd:
Another rule should be to always do a clean install. Yes it's more work but the chances of running into errors is very low.
[Samsung Galaxy Nexus] TuxDroid:
Frequently, a middle road works great:

Reboot to recovery

Wipe /system, cache, & dalvik

Flash ROM

Flash GApps

Reboot

You don't lose any settings or data but nothing gets carried forward from the previous version either.
[Samsung Galaxy Nexus] underwaterjr:
This is what I do every time and I have far fewer issues than reported in this thread.
[Samsung Galaxy Nexus] pitchdarkice:
sounds like an ideal option. tibu helps with less work, but sometimes i see weird behavior when using it to increment nightlies
[Samsung Galaxy Nexus] mouf32:
Same. I was using TiBu for a few things but have resorted to Nandroid Manager to restore text messages and seem to be having far less issues.
[Samsung Galaxy Nexus] cujo6801:
That's what I use...

Works great...

sent from the DOG pound
[Samsung Galaxy Nexus] erodriguez87:
My gnex isn't booting to CM with the 9.6.2013 nightly. I did a clean install. Anyone else running into that issue?

It isn't a big deal since i can just go back to the 09.04.2013 one but wanted to leave a note :).
[Samsung Galaxy Nexus] ejkeebler:
Same, i dirty flashed, it would show the google logo and then just die, no boot animation or anything. Wiped everything, clean install, same result, back on 9/4 for the time being :)
[Samsung Galaxy Nexus] JeeperDon:
Issues with 9/6 may have something to do with it being 6MB smaller? Might just be a bad build?
[Samsung Galaxy Nexus] TuxDroid:
Just for clarity, Titanium & Nandroid Manager are not needed with my method as user data is not removed. After reading the responses, I was not sure that was clear.
[Samsung Galaxy Nexus] mfdemicco:
The consensus the data drops will and 3g/4g hand-off lag will not be fixed until Verizon release new LTE radios.

It would seem that all 4.3 roms would have this same problem, however I'm not seeing this talked about in the other rom threads.

---------- Post added at 06:03 AM ---------- Previous post was at 05:59 AM ----------

Just for clarity, Titanium & Nandroid Manager are not needed with my method as user data is not removed. After reading the responses, I was not sure that was clear.

That's basically dirty flashing by not wiping /data. Flashing a rom automatically wipes /system anyway.
[Samsung Galaxy Nexus] jaredsleboeuf:
I follow the Shiny, EuroSkank, PA, etc threads (here and on Rootzwiki) and most of those mention it. The only one I haven't actually seen talking about the data drops, etc. is PA, but it exists on that ROM too. I think a lot of people have simply accepted that radios/APNs are the problem (and there's not really anything that can be done about it unless VZW steps in).
[Samsung Galaxy Nexus] donutzman:
Same here. Computer does notice a USB device plugged/unplugged after the Google bootloader logo, but that's about the only feature you get with the 9/6 nightly it appears :)
[Samsung Galaxy Nexus] ArnieG:
9/6 won't boot for me either on toro or grouper.
[Samsung Galaxy Nexus] mouf32:
Same for me.... Had to Odin back to ICS. Booting back up now.
[Samsung Galaxy Nexus] PrettyPistol555:
No different here.... :crying:
[Samsung Galaxy Nexus] gpzbc:
I just got on here to report the same issue. I should have checked here first.
[Samsung Galaxy Nexus] underwaterjr:
Why did you have to go back to ICS? Why didn't you just boot back into recovery and flash the last nightly that worked?

---------- Post added at 10:34 AM ---------- Previous post was at 10:08 AM ----------

I did a build last night and synced up at 6pm Central time. It boots fine. The only difference between the nightlies is I cherry picked some commits to try and get trim working. Jury is still out on that. If anybody wants it to hold them over until they fix the booting problem on the official nightlies.
[Samsung Galaxy Nexus] jlvlawrence:
Is this problem specific to toro or all Verizon phones? I was messing with a buddies note 2 running 10.2 last night and the LTE to 3g switch is WAY faster than my toro.
[Samsung Galaxy Nexus] mouf32:
My phone took a bath a few months back and the down volume button doesn't work :D

And ICS was the first Odin files I could fine. Was at work and didn't want to spend a lot of time looking. I did install the factory 4.2.2 image after I got it up and running. I ended up losing 4G out of the deal. Not sure if I need to flash radios or not, but in About Phone it says I have the latest.

**Update** 3 restarts later 4G is back on the stock 4.2.2 build. Perhaps I will try tomorrows nightlie :D
[Samsung Galaxy Nexus] underwaterjr:
Ouch well that explains it. Sorry about your phone.
[Samsung Galaxy Nexus] ExodusC:
What's that now? I have been under the impression TRIM is functioning properly on toro.
[Samsung Galaxy Nexus] underwaterjr:
I don't think it is. When running this command with my N7 I get an output but not with my gnex.

adb logcat -d | grep -i fstrim

Try it and see what you get.
[Samsung Galaxy Nexus] craigacgomez:
Does anyone else have any problems with the Amazon AppStore on build after 09/02? It keeps asking me to re-login every time the app is killed (either forcefully, or OOM, or a reboot). It seems to be unable to retrieve the login information. If I downgrade to 09/02, it works fine again! This is the logcat error..

E/AmazonAppstore.AndroidLogRecordCollector( 2434): AmazonAppstore.SimpleObfuscator Error preparing data. 9fe52dbb PropertyMap:{ Name:Log RecordType:Log LogLevel:Error device.systemTime:1378497337322 device.sdkVersion:18 device.hardware:tuna LogTag:SimpleObfuscator device.androidRelease:4.3 device.manufacturer:Samsung device.brand:Google device.model:Galaxy Nexus MessageContents:Error preparing data. 9fe52dbb };
E/AmazonAppstore.ConfigurationServiceImpl( 2434): Error when handling SharedPreferencesChangeListener notification
E/AmazonAppstore.ConfigurationServiceImpl( 2434): java.lang.NullPointerException
E/AmazonAppstore.ConfigurationServiceImpl( 2434):	at com.amazon.mas.client.framework.configuration.ConfigurationServiceImpl$FeatureConfigurationChangedListener.onSharedPreferenceChanged(ConfigurationServiceImpl.java:64)
E/AmazonAppstore.ConfigurationServiceImpl( 2434):	at com.amazon.mas.client.util.persistence.EncryptedPreferences$1.onSharedPreferenceChanged(EncryptedPreferences.java:55)
E/AmazonAppstore.ConfigurationServiceImpl( 2434):	at android.app.SharedPreferencesImpl$EditorImpl.notifyListeners(SharedPreferencesImpl.java:475)
E/AmazonAppstore.ConfigurationServiceImpl( 2434):	at android.app.SharedPreferencesImpl$EditorImpl.access$600(SharedPreferencesImpl.java:303)
E/AmazonAppstore.ConfigurationServiceImpl( 2434):	at android.app.SharedPreferencesImpl$EditorImpl$3.run(SharedPreferencesImpl.java:483)
E/AmazonAppstore.ConfigurationServiceImpl( 2434):	at android.os.Handler.handleCallback(Handler.java:730)
E/AmazonAppstore.ConfigurationServiceImpl( 2434):	at android.os.Handler.dispatchMessage(Handler.java:92)
E/AmazonAppstore.ConfigurationServiceImpl( 2434):	at android.os.Looper.loop(Looper.java:137)
E/AmazonAppstore.ConfigurationServiceImpl( 2434):	at android.app.ActivityThread.main(ActivityThread.java:5289)
E/AmazonAppstore.ConfigurationServiceImpl( 2434):	at java.lang.reflect.Method.invokeNative(Native Method)
E/AmazonAppstore.ConfigurationServiceImpl( 2434):	at java.lang.reflect.Method.invoke(Method.java:525)
E/AmazonAppstore.ConfigurationServiceImpl( 2434):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:739)
E/AmazonAppstore.ConfigurationServiceImpl( 2434):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:555)
E/AmazonAppstore.ConfigurationServiceImpl( 2434):	at dalvik.system.NativeStart.main(Native Method)

I've tried to retrace commits, but I cannot seem to narrow this down!
[Samsung Galaxy Nexus] donutzman:
I think I've seen this too, 9/4 nightly. I wonder if it's related to the recent issue with Secure Settings as well? http://xdaforums.com/showpost.php?p=45328199&postcount=1343
[Samsung Galaxy Nexus] fendee1:
Do not download 9/6. I let the phone rest for an hour or two it killed my battery. The phone is running because in pitch black there is a very low light on. Just boot into recovery and reload 9/4 always keep a version or two on the phone. Remember we are running nightly. It could wipeout your phone one day. Keep backing up daily. Or just stick with stable. Sh#t happens.
[Samsung Galaxy Nexus] TechSavvy2:
So...you've officially confirmed the last 10 pages. Thanks :thumbs up:
[Samsung Galaxy Nexus] RaiderX29:
Official from the desk of cyanogenmod do not flash the 9/7 nightly either. It's still broken. Hopefully this will avoid another 10 pages of posts stating it's not working.

https://plus.google.com/117962666888533781522/posts/ArqL2Yw8tun
[Samsung Galaxy Nexus] flytechguy:
9/7 does not work either despite the flash warning. FYI.
[Samsung Galaxy Nexus] JeeperDon:
I still say the size is a big indicator. The ROM file magically got 6 meg smaller than before and is now very broken. Something is shtako in the build.
[Samsung Galaxy Nexus] PDR447:
I have an N7 and Gnex. Just tried this and I got an output on both. Gnex is running 9/4. N7 9/2
[Samsung Galaxy Nexus] underwaterjr:
Ok thanks for testing
[Samsung Galaxy Nexus] TechSavvy2:
This was my exact thoughts. Never seen a jump that size occur.
[Samsung Galaxy Nexus] hotrodwinston:
I'm assuming 908 for toro failed to build?
[Samsung Galaxy Nexus] jlvlawrence:
09/08 is running on my nexus 7. I think it's good to go for all devices.
[Samsung Galaxy Nexus] hotrodwinston:
Yeah it published a few minutes after I posted - downloading now.
[Samsung Galaxy Nexus] chazzdjr:
Let me know if the hand off has improved... I'm waiting to jump back over to cm.
[Samsung Galaxy Nexus] TuxDroid:
What are you using in the meantime?
[Samsung Galaxy Nexus] chazzdjr:
Pure Toro ROM... It's handoff isn't perfect. But it's a good ROM.
[Samsung Galaxy Nexus] TuxDroid:
So, can anyone tell me what the statuses of CM Account and SELinux are on toro? I saw commits recently about SELinux and Enforcing status apparently being working at least in some fashion. Thanks!
[Samsung Galaxy Nexus] craigacgomez:
OK, I did some digging through and figured out thee reason for this issue... It is related to the SecureRandom patches recently merged... The first part of the patch (commit) was merged on Sept 3... but the second part (commit) was only merged on Sept 7... this gap between the 2 merges caused problems with Amazon's settings encryptions... As of Sept 8, this is not longer an issue!!
[Samsung Galaxy Nexus] ba_hamilton:
Not that you asked me but I've been on Tiny's rom.
[Samsung Galaxy Nexus] johnhimm:
Any update to this question?
[Samsung Galaxy Nexus] chazzdjr:
I couldn't wait for an answer... So I flashed it. Handoff is awful still. Restored back to PURE Toro ROM. The modded version has a bunch of cm stuff and halo.