yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] goldsmitht:
here's hoping that fixes the ongoing issue with bluetooth earbuds as well. some work, some don't even show up.
[Verizon Samsung Galaxy S III] dbornack:
Am I the only one not seeing the Masta build in this thread? Where can I download?
[Verizon Samsung Galaxy S III] Rudy_Ruettiger:
Its in the official cm 10.1 thread
[Verizon Samsung Galaxy S III] dbornack:
So an UN-Official build isn't in the UN-Official thread, but is in the Official thread. Makes sense. :)
[Verizon Samsung Galaxy S III] NegativeOne:
http://xdaforums.com/search.php?searchid=128151415

This should narrow it down for you.
[Verizon Samsung Galaxy S III] bobby janow:
Is this an April fools joke?

From the OP: As requested/mentioned by a few people, I created this thread to hold our unofficial builds to keep the [OFFICIAL]CM10.1 Official Nightlies for D2VZW GSIII thread clean.

How does that say the unofficial builds are in the Official thread? Please someone, tell me what I'm missing.
[Verizon Samsung Galaxy S III] dbornack:
Don't know why it's there, but it's in the OP
[Verizon Samsung Galaxy S III] Restola:
Post 82. I'm still running the second one he posted in that post.

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] PerCompLLC:
Hey masta. Will you be posting another unofficial any time soon? Just curious...
[Verizon Samsung Galaxy S III] PerCompLLC:
Have a BLAST with the family! Thanks for everything!
[Verizon Samsung Galaxy S III] PVLMTREE:
New discovery Masta haha.

So, firstly, you're correct, that it's not the 1.25.13 Official NIGHTLY. After pulling several telephony-common.jar from each NIGHTLIES, I've discovered that the 1.27.13 NIGHTLY is where it stops working.

I have looked at the changelog and discovered it's probably this commit and merge that caused it to ignore GSM/Global Networks:

* frameworks/opt/telephony
[COLOR="DarkRed"]5343f09 PhoneProxy: On v6 or greater RIL, when LTE_ON_CDMA is TRUE[/COLOR],
b929c2c Telephony: Correct the typo in RIL.java
f428be2 Reset data stall watch dog after doing recovery

Github: https://github.com/CyanogenMod/android_frameworks_opt_telephony/commit/5343f09

Visuals: After overwriting with 1.27.13's jar, APN settings disappear and Global/GSM Network options vanished. Resulting in a solid greyed triangle in status bar.

Extra Info: With all these tests, I am using T-Mobile's apns-config.xml file.
[Verizon Samsung Galaxy S III] mastamoon:


Awesome! That's the one I thought may have done it. But being in framework that should be in the T-mobile build also. Have you taken a T-mobile telephony common from a T-mobile build and dropping it in a latest d2vzw nightly?
[Verizon Samsung Galaxy S III] GideonX:
No need to be in the directory, git revert is smart enough.

You can also do a git reset --hard HEAD or SHA-1. Lots of choices to kill a commit :)
[Verizon Samsung Galaxy S III] landale:
Interesting. So basically if this is indeed the case it looks global support only existed because the phone wasn't properly enabling CDMA/LTE service in the first place. When this was corrected global support went away.

Since this patch has been included in Masta's builds for quite some time I don't recall how much of a difference it had on CDMA/LTE data but it seems like without a reworking of how the phone handles service we might have a situation where this would need to be reverted for gsm service but merged for proper CDMA/LTE service. I guess we can't have everything :(

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

It would be in the T-Mobile telephony common too but the d2tmo wouldn't trigger the "LTE_ON_CDMA" part of this since it's a GSM device, same would apply for the d2att I imagine as well. This would explain why only the d2vzw is impacted.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Does the newest build of yours have today's wpa fix or the old one still? Also, is there anything in this build that would provide better signal over the official, once today's commits go live?

Thanks!
[Verizon Samsung Galaxy S III] GideonX:
Doesn't really make a difference, it's the same fix.

Sent from my Nexus 7
[Verizon Samsung Galaxy S III] PVLMTREE:
You're correct. Just for curiosity, I did also try T-Mobile's jar, and it functions like any other Carrier's jar. Hope there can be a fix or something in the near future. The work-around is annoying to do every time I flash a new build, haha.
[Verizon Samsung Galaxy S III] dpaine88:
You guys think theres anything in the other ROMs that would make them faster than CM? Or is it mostly based on the kernel and android version?
[Verizon Samsung Galaxy S III] PVLMTREE:
CM just implemented new bionic enhancements, making CM performance even smoother, haha. But kernels do help overclock.

Plus all the other AOSP ROMs are based off of CM's trees, so they should perform similar.
[Verizon Samsung Galaxy S III] dpaine88:
Thanks for the quick reply!

Another easy question, regarding specifically flashing nightlies daily or every 2-3 days. They always say to break in a ROM/kernel for a few days to really get accurate and good battery life. Would flashing new builds every day prevent the ROM/battery/kernel from ever truely settling out?
[Verizon Samsung Galaxy S III] PVLMTREE:
Well, the S3 has a lithium-ion battery, so that means battery life will quickly adapt to your phone's consumption, etc. It shouldn't be a problem with battery life if you update daily. Especially if you use a type of "conservative" governor for your kernel, your battery life will be smooth throughout the day. (:
[Verizon Samsung Galaxy S III] invisiblek:
I actually kinda opposed this commit to begin with. The Touchwiz RIL doesn't do this so I was pretty sure we didnt need it. The testing I did didn't seem to make a difference so I never brought it up.

I can roll unofficials if you guys want them while mastamoon is gone. I'll need a list of picks and reverts to build with though.

EDIT: nvm, /me reads the OP

I'll have a build up shortly for testing
[Verizon Samsung Galaxy S III] mastamoon:
Thanks man! Hopefully that's all that is needed and if it doesn't cause any other issue, get it reverted. :thumbup:
[Verizon Samsung Galaxy S III] PVLMTREE:
You two are my heroes. c:
[Verizon Samsung Galaxy S III] invisiblek:
Let's see what happens. At the very least we can look at ifdef'ing it.

My builds will be automated, they'll kick off at 3:00pm CST.

Once uploaded, there will be a tweet spit out here with a link to download: https://twitter.com/invisiblek_cm

They'll have all the same picks and reverts as mastamoon's along with reverting this: https://github.com/CyanogenMod/android_frameworks_opt_telephony/commit/5343f09

Let's see what happens...

It wont be as personal as it is with mastamoon, because I don't stick to the forums as closely, so its up to you guys to keep up with what changes via http://10.1.cmxlog.com/?device=d2vzw or https://play.google.com/store/apps/...yLDEsImNvbS5pbnZpc2libGVrLmNtLm5pZ2h0bGllcyJd

Just kicked a build off now, so assuming my script is still working, it should be uploaded in a bit.
[Verizon Samsung Galaxy S III] rampantandroid:
Yeah, I flash whenever I see a new build that has stuff I care about working. I average 24 hours of battery life with 2-3 hours of screen on time.
[Verizon Samsung Galaxy S III] WhammyDroid:
Thanks Dan for doing this!

Do you know anything about why the CodeAurora GPS commit got reverted? Do you know if anyone is or are you able to determine the conflicts and get this revert re-implemented? Running Masta's unofficial is the only I can get the GPS to work on CM10.1. I would love to be back on the official nightly however this reverted commit is the reason why I am not.

Thanks again!
[Verizon Samsung Galaxy S III] invisiblek:
From what I understand, it broke GPS for other devices.
[Verizon Samsung Galaxy S III] aatrek:
Is there a way to take a Photosphere image with the current build? Maybe I just can't find the option...
[Verizon Samsung Galaxy S III] s'pht:
PhotoSphere is a Nexus 4 only thing right now. It uses closed source stuff so CM can't/won't include it. There are a bunch of flashable zips that you can *add* it to any 4.2 install but I tried it and it didn't work very well. Ostensibly when 4.2 starts coming out on other devices it might get open sourced and then be included.

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

FYI: I tested the Car Dock home button thing this morning - works perfectly!
[Verizon Samsung Galaxy S III] PerCompLLC:
No sir... Photosphere is not included in CM, although you could add the correct Gallery.apk to your /system/app folder and get it to work. Information on how to do this is definitely available in other threads.

Edit: s'pht beat me to it.
[Verizon Samsung Galaxy S III] s'pht:
Or you could use this: http://www.androidcentral.com/photosphere-installer-easy-way-flash-photosphere-rooted-devices
[Verizon Samsung Galaxy S III] goldsmitht:
NO

well, there is; you have to find a copy of 4.2 gapps that has the photoshpere capable camera, and install them.

THEN you have to remember to tap the screen to focus each time you try to use that camera, or the camera will FC, requiring a reboot to re-enable camera function.

:cyclops:

edit: DAMN... double ninja'd!!!
[Verizon Samsung Galaxy S III] mastamoon:
So did the revert fix GSM?
[Verizon Samsung Galaxy S III] Masterfisto:
I used the zip from here:

http://forums.androidcentral.com/ve...830-jelly-bean-4-2-camera-20.html#post2283346

Photosphere works perfectly for me after flashing the zip and I disabled the regular camera app to avoid confusion.

Sent from my Cm10.1 Galaxy S3
[Verizon Samsung Galaxy S III] PVLMTREE:
With the revert, the APN and other network options came back! After inputting the right APN settings (or you can just use the other apns-config.XML, GSM works! Cheers!
[Verizon Samsung Galaxy S III] mastamoon:
Awesome! Just have to test effects on normal usage now.
[Verizon Samsung Galaxy S III] alee:
So other than switching in Phone Info to CDMA/GSM/LTE, I can just stick in another SIM, add APN data and it should go?
[Verizon Samsung Galaxy S III] invisiblek:
Bleh...

New build is up, filename is the same as last night's, but it IS updated, would have been synced about a half hour ago

http://invisiblek.org/sch-i535/roms/cm10.1/cm-10.1-20130301-UNOFFICIAL-d2vzw.zip

md5sum: 12197ff6098cdf357c11d0986f3db67a

Guess its time to modify the script to check for ones named the same and add a number at the end accordingly...
[Verizon Samsung Galaxy S III] V3TTOO:
Thanks. Any changes from the last build, besides repo?
[Verizon Samsung Galaxy S III] MG386:
Does anyone's GPS actually work better without the code aurora commit? Mine is better on official where its reverted. I've been watching this for weeks going back and forth...
[Verizon Samsung Galaxy S III] jlokos:
I don't know if it works better. On the latest build (3/01), it identifies my location precisely and quickly.
[Verizon Samsung Galaxy S III] icon123:
I think they added a lte button to

quick settings.

I haven't noticed a difference between the 2. My GPS works fast with either.
[Verizon Samsung Galaxy S III] mastamoon:
I've had a few users of my unofficial builds say it's the only one that has working GPS. I haven't tested both myself.
[Verizon Samsung Galaxy S III] juancaperez2000:
i was running AOKP and also Carbon i guess those are running latest gps commit and i got problems with my GPS then i flash to TW rom make it lock flash your rom and bam my GPS is working perfect again even better thanTW rom
[Verizon Samsung Galaxy S III] PVLMTREE:
1. Pop in sim

2. Phone Info to GSM/CDMA, or CDMA/GSM/LTE

3. Add APN data, or swap apns-config.xml file

4. Reboot

Profit. :D
[Verizon Samsung Galaxy S III] WhammyDroid:
Yep. I am one of them. Without it, GPS locks takes forever if not locks at all.
[Verizon Samsung Galaxy S III] PVLMTREE:
I do get a lot of phone process stopped someone calls me though @mastamoon and @invisible.

Full wipe and fixed permission. I think its a 4.2.2 issue, not the telephony-common.jar itself.
[Verizon Samsung Galaxy S III] Secretwar1:
Any one else notice that the brightness panel in the quick settings menu isn't working in invisibleks build posted yesterday?
[Verizon Samsung Galaxy S III] icon123:
Yep. Just not his build either. Happened on my own build. Probably something to do with adding the lte or they also reworked the quick settings as well. I tried to revert them but it gave me an error. I'm new to all this so I'm sure I'm probably not doing the reverts right. Anyways, just confirming. Also, I don't think the quick pull down cherry pick is working either.

Edit: Just saw they fixed the brightness tile. Next build should have it in. However, they do not want the quick settings pull down merged, so that might be a no go unless someone else fixes it.

Edit2: I was wrong about the quick setting pull down. It still works but I don't think it will get merged.
[Verizon Samsung Galaxy S III] ctsail410:
It isn't working with my own builds as well. After doing some digging I think it is related to this change: http://review.cyanogenmod.org/#/c/30528/

I'm doing a build now with the clean-up reverted, so I'll let you know.

EDIT: Fix already merged this morning; just repo-sync. https://github.com/CyanogenMod/andr...mmit/8bbd689a1e2880c16bacc0f15aef91b1321f5c41
[Verizon Samsung Galaxy S III] loldi:
Managed to go 113 hours of uptime until I got the "home button long press issue". Running ktoonez kernel 2/19/13. Does this only happen using something other than the stock kernel that comes with these unofficials?
[Verizon Samsung Galaxy S III] alee:
No it happens even with the stock kernel. Usually about 2 days before it manifests itself.
[Verizon Samsung Galaxy S III] goldsmitht:
Anyone ever see an issue with VZW GPS where GPS doesn't work in certain areas? Tried a couple AOSP ROMs, as we as TW, and GPS will continually put me way off. But only happens in a certain area, and on VZW towers. WIFI will put me where I am.

Was curious if this was a phone issue, or maybe system error
[Verizon Samsung Galaxy S III] invisiblek:
new build up, sorry, the script bombed out due to the changes i made yesterday

all fixed now and should be back on schedule for builds

same commits as before + upstream changes

http://invisiblek.org/sch-i535/roms/cm10.1/
[Verizon Samsung Galaxy S III] stearic:
Is anyone having problems receiving mms? I've cleared both cache files, deleted data/cache for the mms app as well. I'm not sure what else to to short of doing a complete wipe.
[Verizon Samsung Galaxy S III] jlokos:
No problem on the latest build.
[Verizon Samsung Galaxy S III] stearic:
Any suggestions of what i might try sans a complete wipe?
[Verizon Samsung Galaxy S III] Obaterista93:
Hey guys, I'm on the xda app and we all know the search blows, so my question is does anyone have a solution for the mediaserver wake lock? It absolutely destroyed my battery today. Six hours of wake lock O_o
[Verizon Samsung Galaxy S III] david_hume:
Is it your first time using the ROM?
[Verizon Samsung Galaxy S III] sivarticus85:
I've noticed this problem ever since ICS. I only get it when I'm streaming media on YouTube and thru Google Music, and when listening to music from my SD card. I've tried googling it but I didn't have any luck.
[Verizon Samsung Galaxy S III] NegativeOne:
I have never had a problem I have never tried this, but can clear data on media server and that helps, or it might be media storage. Try both and let me know if that helps? Sorry if there are typos, I am dictating this with my eyes closed closed because I'm still half asleep
[Verizon Samsung Galaxy S III] goldsmitht:
not sure why this works, but seems to:

make sure you are NOT on silent or vibrate only when you reboot, and will not have wake lock.

don't know why, but eliminates it for me.

:cyclops:
[Verizon Samsung Galaxy S III] jlokos:
Try reflashing the rom.
[Verizon Samsung Galaxy S III] Obaterista93:
I don't wanna take up half a page by quoting everyone, so no I've been on the nightlies since January. Never had it til yesterday. And I'm rarely ever on vibrate or silent, so I can't picture that being an issue. I did notice that for a really long time that Apollo wouldn't see all of my music, and now it does. *shrugs* and I had a nandroid that had a corrupt /data partition. I deleted the FUBARed nandroid and I'm hoping that fixed it.
[Verizon Samsung Galaxy S III] nbaj2k:
(Deleted)
[Verizon Samsung Galaxy S III] dpaine88:
I am coming from another ROM and miss a few features but am curious if there is any possibility of adding them.

1) Being able to swipe horizontally across the pulldown bar under the quick settings and having it swap between notifications and the quick panel.

2) Hiding the lockscreen blinders that show on the sides of the screen when you turn the screen on.

3) Option to reboot into recovery

Not sure if these have been mentioned but I did a search without much luck.

Thanks
[Verizon Samsung Galaxy S III] GideonX:
1 As Hybridnoob said below, swipe across the carrier label. I must have fat fingers, this took me forever to trigger :T

2 Isn't native to CM afaik.

3 is an available option. Go into dev options and tick advanced reboot.

Edit: #1
[Verizon Samsung Galaxy S III] Hybridnoob:
#1 is possible - just slide your finger across the carrier bar at the bottom of the notification shade.
[Verizon Samsung Galaxy S III] dpaine88:
thank you very much, the ROM I was on previously worked from anywhere on the screen, never would have thought of only touching the carrier bar.

So then I am stuck with just the white lines on the screen when you turn it on, I can live with that.
[Verizon Samsung Galaxy S III] Hybridnoob:
You're welcome; enjoy! I'm a big fan of this ROM. One other hidden feature is long pressing the volume rocker while the screen is off and audio is playing to skip tracks, etc.
[Verizon Samsung Galaxy S III] dpaine88:
I am running into an issue all of a sudden after doing a clean wipe to the latest build by Invisablek.

I cannot get my phone to stick on RU/SIM in the mobile data settings. I get the activation screen every boot and go in and change it back from NV to SIM but each reboot it switches itself back.

I just tried to flash Liquid ROM and it let the SIM settings stick and works fine so I am not sure whats going on.

I also did the 2 recommendations in the CM FAQ without any luck.

EDIT: Seemed to fix it by flashing the last build by Moon
[Verizon Samsung Galaxy S III] stearic:
You know, i'm not sure why i didn't think of doing that. I'll do that and if it doesn't work them i'm afraid that i'll be having to do a full wipe and start from scratch.

Edit: Looks like i'll be having to start from scratch. Flashing the rom again didn't fix it.
[Verizon Samsung Galaxy S III] NegativeOne:
No new builds since Friday right?
[Verizon Samsung Galaxy S III] PerCompLLC:
InvisibleK posted one on Saturday evening. http://xdaforums.com/showpost.php?p=38681737&postcount=1426
[Verizon Samsung Galaxy S III] NegativeOne:
Crap, sorry. I missed that post. I was looking in the original place he said he'd be pushing them to. Many thanks.
[Verizon Samsung Galaxy S III] jlokos:
I'm sorry it didn't work.
[Verizon Samsung Galaxy S III] luv2increase:
Are any of the unofficials built with the Linaro toolchain yet?

Sent via Crossbreeded, 100% V6 Supercharged. KT747'd and Linaro Built Paranoid Android 3.10
[Verizon Samsung Galaxy S III] PerCompLLC:
As I recall, somebody posted an unofficial a few days ago with Linaro. But I've looked for the post and can't seem to find it. It might've been termleech (or not).
[Verizon Samsung Galaxy S III] MWFD:
I am not receiving any notifications for MMS messages. Anybody have any idea why this is? Tried turning on/off notifications in stock MMS app and Sliding Messaging Pro, but neither app will notify me if I receive an MMS, but my SMS notifications are fine.
[Verizon Samsung Galaxy S III] masri1987:
Running invisiblek March 1 build, mms quality is super low
[Verizon Samsung Galaxy S III] mastamoon:
Just pull the mms from one of my nightlies.. He doesn't have my manual edits for mms stuff.
[Verizon Samsung Galaxy S III] Stupifier:
Masta, Could you put a link to the suggested Gapps to flash along with your nightlies in the OP. I've heard talk about using new Gapps specifically for Android 4.2.2. Posting up some brief information about Gapps in the OP would clarify any confusion for people.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah, but for now, download goo manager from the play store and download with that. It's also on cms wiki I would guess.
[Verizon Samsung Galaxy S III] julesism:
I grab Gapps from here -> http://goo.im/gapps/

There is a newer version from a couple days ago that is 4.2.2.
[Verizon Samsung Galaxy S III] PerCompLLC:
Just out of curiosity, don't gapps update automatically if you already have them installed? Or so I thought... I realize that this doesn't help for a clean flash, but for dirty flashes.
[Verizon Samsung Galaxy S III] icon123:
When you get back from vacation, can you share your MMS tweaks for those of us that build from source? Thanks and have a good time.
[Verizon Samsung Galaxy S III] ctsail410:
I do build dailies with Linaro and try to keep them as close to Masta's as possible. If there's interest I can start posting them.

I did post one a week or so ago before some of the volume fixes were merged.

EDIT: Here's a link if anyone is interested: http://d2vzw.ct-sail.com/ROM/CM10.1-LINARO/
[Verizon Samsung Galaxy S III] PerCompLLC:
Sorry man. I couldn't remember who was doing the Linaro builds.
[Verizon Samsung Galaxy S III] ctsail410:
No worries!
[Verizon Samsung Galaxy S III] julesism:
I believe the apps update themselves like any app does, but I clean flash a few times a month so I check that site for newer gapps to flash with ROMs.
[Verizon Samsung Galaxy S III] invisiblek:
No unofficial today guys

I'm going to recommend the M2 release here:

http://get.cm/get/jenkins/21614/cm-10.1-20130304-EXPERIMENTAL-d2vzw-M2.zip

Please try it out and post bugs to: CM's Jira:

https://jira.cyanogenmod.org/

Make sure you check that your bug doesn't already exist before posting.
[Verizon Samsung Galaxy S III] rpxz:
Forgive me for this rather noobish question. I haven't kept up with CM for a while. I was rocking a cm10 build roughly 6 months old or so now.

What is the difference between the "M" cm10.1 and just the regular nighties?

Thank you.
[Verizon Samsung Galaxy S III] rampantandroid:
Battery live on the 2/27 build running kt747 with the ktoonservative governor. Nearly 3 hours of phone calls on this, and phone calls accounted for 50% of my battery drain.

Thanks so much for the ROM, Masta. The only change I really care about right now is getting the back button to work properly/not bug out after a day or so (I have yet to get a solid repro) and show presses as holds. Otherwise I have no complaints, more stable for me than 4.1 ever was.
[Verizon Samsung Galaxy S III] rpxz:
Anyway to disable CRT screen lock? I can't stand that animation lol. I have already tried all the settings in developer options.
[Verizon Samsung Galaxy S III] PVLMTREE:
Do you think CM will ever include a fix for GSM invisiblek? If not, I'll just need to make a copy of telephony-common.jar of your revert for future builds.
[Verizon Samsung Galaxy S III] invisiblek:
What exactly are we talking about here? The ability to throw in another carrier's SIM? Or like global roaming? I can see global roaming being a reason. I doubt carrier switching will be anything they'd want to go near.
[Verizon Samsung Galaxy S III] PVLMTREE:
Global Roaming will allow GSM networks (T-Mobile). But, basically them making an exception to the commit, which broke Global/GSM in the first place. I'm just wondering if they will ever fix the Global Roaming issue. Due to that your revert fixed it.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Anyone know why sometimes when in a phone call and you pull the phone away to pres end call the screen will keep flickering and go black BEFORE you can press it?