yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] PerCompLLC:
In my experience, it is usually because the proximity sensor is overly sensitive. You may have already done this, but make sure that your fingers aren't anywhere near the proximity sensor when you are trying to manipulate the phone.
[Verizon Samsung Galaxy S III] invisiblek:
Well, if reverting this fixes global data, I'll definitely look at getting a patch submitted to ifdef this.
[Verizon Samsung Galaxy S III] anacree:
In general, what are the differences between the new Monthly build and Masta's unofficials?
[Verizon Samsung Galaxy S III] ctsail410:
In general, it'd be any of the "cherry-picks" or "reverts" listed in the OP. It's a little out of date at the moment due to his time away.

Compared to what has merged the remaining differences are:

- improved GPS

- battery bar

- quick settings pull-down

- home dock button
[Verizon Samsung Galaxy S III] anacree:
cool, thanks. I guess the bluetooth improvements in masta's builds have been merged? or are there still bluetooth issues?
[Verizon Samsung Galaxy S III] ctsail410:
Well, I think so, but he's probably the only one who can say for sure. The best I can tell you is that everything I was using in my own builds are merged now...and that was everything I could find in Gerrit.
[Verizon Samsung Galaxy S III] NegativeOne:
I'm running the unofficial from 3/3 and today I noticed that my ADB stopped working. OK. So I realized it's the whole RSA thing from Android 4.2.2. I updated, got it working mostly (it's buggy, hangs, and disconnects... woo hoo). Also it looks like Chrome remote debug tools broke.

My question: Why am I seeing this now? I've been flashing pretty regularly (at least once a week). Did this security stuff JUST get merged? My previous build was 3/1, but I don't remember if I had tried ADB on that one. I do know that it worked last week at some point.

Other question... is chrome debug broken for anybody?

This may need to go into the Q&A section of the main thread, but I dunno.
[Verizon Samsung Galaxy S III] ctsail410:
For those who may be interested, I've posted a 3/5 daily compiled with Linaro here: http://d2vzw.ct-sail.com/ROM/CM10.1-LINARO/

Same cherry-picks and reverts as mastamoon (GPS, Battery Bar & Pull-down) plus Linaro-required picks (http://review.cyanogenmod.org/#/q/status:open+branch:cm-10.1+topic:linaro,n,z).

I took a stab at including a MMS size increase. It might not match what mastamoon has, but should be better than stock.

There are some new merges included that affect bluetooth voice dialing and a bump in the bitrate for A2DP playback quality.
[Verizon Samsung Galaxy S III] iofthestorm:
M builds occur once a month and it seems like they try to do a feature freeze in the days before an M release so theoretically there would be less broken stuff than a nightly, though I don't think they actually branch from the main branch for an M so realistically the nightlies a couple days before the M build also have fewer feature additions than normal. Though CM is relatively conservative with new features so it's not like nightlies are ever super unstable anyway. The nice thing is that they provide a good point to provide bug reports on rather than a moving target and for people who don't want to flash multiple times a week it can be a better option.
[Verizon Samsung Galaxy S III] rpxz:
Thank you for your response! I am running the latest M build and so far haven't had any issues.
[Verizon Samsung Galaxy S III] Obaterista93:
To be completely fair, the only issue I've really had with any of the nighlies was the random screen of death issue. I think that's been fixed(haven't gotten it in a few days) so I haven't had any real problems at all.
[Verizon Samsung Galaxy S III] landale:
I see the BT voicedial issue was finally fixed today so hopefully we can get a new unofficial build today to test it out.
[Verizon Samsung Galaxy S III] odub303:
Check post 1478

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] biyobe:
I just tried Carbon ROM and the voicemail sound is playing through the headset like it is supposed to. Not sure how/why; but there it's functional like it should be if you're able to take it out??
[Verizon Samsung Galaxy S III] PVLMTREE:
I encourage you invisiblek.

Commit

[COLOR="Red"]5343f09[/COLOR] PhoneProxy: On v6 or greater RIL, when LTE_ON_CDMA is TRUE

was the reason Global Roaming/Data was and still unusable on the Official CM10.1.

Your Unofficial is the only NIGHTLY that supports GSM/Global Roaming. Very much appreciated!
[Verizon Samsung Galaxy S III] jlokos:
For us noobs, assuming this commit was incorporated into CM10.1, we would be able to use our S3's overseas with an appropriate SIM card like those with TW roms?
[Verizon Samsung Galaxy S III] Masterfisto:
Does the monthly build fix the home button sticking if you are using custom hardware buttons?

Sent from my Cm10.1 Galaxy S3
[Verizon Samsung Galaxy S III] icon123:
Yes. You would have to setup gsm in phone info and change your apns.
[Verizon Samsung Galaxy S III] landale:
In order to make global roaming work this commit needs to be removed. You also then need to dial *#*#4636#*#* from your phone to adjust your phone to GSM mode but once you do that you're all set.
[Verizon Samsung Galaxy S III] jlokos:
I flashed your build yesterday; the only issue I had is that after a reboot, the phone keeps trying to activate itself. I noticed in settings>more>mobile networks>CDMA subscriptions, NV was checked. Ruim/SIM doesn't seem to hold after a reboot. Otherwise, very nice build and thanks for your work.
[Verizon Samsung Galaxy S III] ctsail410:
Well that's frustrating. I can't say that's ever happened to me, and I've been running my own builds for a month or so. Did anyone else here have the same issue?

Do you have an IMEI? If so, does it go back to normal if you flash one of the other non-Linaro unofficials?

There are a few alternates to try here if you're still stuck:

http://xdaforums.com/showpost.php?p=35600769&postcount=2&nocache=1
[Verizon Samsung Galaxy S III] jlokos:
Sorry I wasn't clear. I just checked the cancel activation box and then went into settings and checked the box for RUIM/SIM and that solved the problem. It just has happened periodically on reboots. IMEI and phone # were fine. This has occurred on some of the AOKP roms but not on CM10.1.
[Verizon Samsung Galaxy S III] Obaterista93:
Anybody else unable to send MMS on the latest(official) nightly?

*cache and dalvik wipe fixed it
[Verizon Samsung Galaxy S III] stearic:
What app are you using for your txt msging?
[Verizon Samsung Galaxy S III] Obaterista93:
The stock messaging.

I think something may have just been weird from the previous nightly to this one.
[Verizon Samsung Galaxy S III] invisiblek:
The 3.4 kernel is getting pretty solid guys. I'd like some of you to test it out for us if you would.

I've been running it for at least a couple weeks now, seems pretty good.

detule squashed a couple more bugs in the last couple days and its getting pretty solid.

Here's an app to use for logging: http://goo.gl/y0x96

If you get a hard reboot, use that app to grab the "Last Kernel Log" and put it up on pastebin or somewhere.

Here's a spreadsheet where we can log this info: http://goo.gl/pCpjg

Please use that for reporting bugs, and pasting crash dumps, this thread is NOT the place for posting bugs for this kernel. I've only hijacked it for this because of the exposure to the most people =P

Latest build: http://invisiblek.org/sch-i535/kernels/kernel_3.4_msm-jb_2.5_20130306_d2vzw.zip

Source code: https://github.com/invisiblek/linux-msm-d2
[Verizon Samsung Galaxy S III] -Maverick-:
I'll try it with the latest build. Thank you! :good:
[Verizon Samsung Galaxy S III] WhammyDroid:
Dan, no new unofficial ROM build?
[Verizon Samsung Galaxy S III] invisiblek:
Damn...was hoping nobody noticed =P

I'll get one up shortly for you guys...

EDIT:

Here you go: http://invisiblek.org/sch-i535/roms/cm10.1/cm-10.1-20130307-UNOFFICIAL-d2vzw.zip

FYI, there are new gapps available too as of 03/01: http://goo.im/gapps/gapps-jb-20130301-signed.zip

Picks:

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

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

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

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

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

^^ Not sure how close mastamoon is following, but he'll probably want to include this one in his build when he comes back. At least until the kernel bug is found.

Reverts:

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

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

^ I'll try to work on a patch to disable this for us this over the weekend, shouldn't be too hard to implement.
[Verizon Samsung Galaxy S III] goldsmitht:
so... is the "GPS" revert in this? I'm a little confused as to whether Mastamoon was reverting to when the GPS was fixed, or was reverting to fix the "fix" that didn't "fix" GPS?

and am now more confused. Anyway, only way i get GPS to really work is with his builds, so hopefully this one is on the same page as his normal "unofficial" builds.

:cyclops: :confused:
[Verizon Samsung Galaxy S III] ThaSik1:
I know this prolly isn't the place to do this but I would love to see a dev cherry pick/port the cm7 render effect if possible..one of the best features on android in my opinion! :) Other than that, thanks for all the work masta and invis!!

Sent from my GS3 suffering from SuGaR sHoCk!!!
[Verizon Samsung Galaxy S III] NegativeOne:
re: http://review.cyanogenmod.org/#/c/33383/

Interesting, and awesome. Do you have any idea what that settings is intended to do ? Also, i wonder if this has anything to do with how our device reports incorrect system time on boot. To clarify for everyone, this is not a kernel fix, so you should be able to use a custom kernel w/ this.

re: reverts... I forget, what were these fixese trying to do, and why do they cause problems for us? I can't seem to find it, but I also haven't had my coffee yet :P

Thanks for the build sir!
[Verizon Samsung Galaxy S III] invisiblek:
It reverts the revert, double-negative =P

Basically it adds our GPS fixes back in that broke other devices. In theory, it should be giving us better GPS.

I've not researched this at all. According to the Jira issue its something we can disable temporarily, but we do want it long-term. Its not related to our time issue in recovery though.

From cyanogen: "Keep at it, I'm pretty sure this is the issue. We can disable this in the short term, since it's just an optimization. Longer term I'll debug the kernel side and find out why it's drifting."

This fix is not a kernel fix, it will work regardless of your kernel. When the bug is found in the kernel, other devs will need to pick it.

The reverts fix gps and global data roaming.

EDIT: Build up: http://xdaforums.com/showpost.php?p=38862635&postcount=1499
[Verizon Samsung Galaxy S III] eikoo:
Is there a commit to fix using the microphone when the phone is docked and being used for usb audio out?
[Verizon Samsung Galaxy S III] iofthestorm:
Out of curiosity is Steve or any other d2 maintainer working on a 3.4 kernel? Or will your 3.4 kernel eventually become the kernel for all d2 devices? I flashed it last night and I think I'll avoid flashing anything until I see the long press issue come up in case the bug is gone in that kernel, unless you've already experienced it with 3.4. That JIRA ticket is pretty interesting, I didn't realize the long press time was decreasing over time.
[Verizon Samsung Galaxy S III] shadrach47:
Any word on if mp3 tag profiles are going to work with bluetooth? I know on cm10 and touchwiz they work, but not cm10.1. Bluetooth audio is obviously more important to focus on but just wanted to see if metadata will get supported or looked at? It's a nice feature to have and haven't heard any word about it before.
[Verizon Samsung Galaxy S III] invisiblek:
Please do test out the long press thing on 3.4, I've not run long enough to thoroughly test it.

I'd say 3.4 is the logical way to go. Steve mentioned that he plans to work on 3.4 when he gets some time.

I've seen it talked about. I'd say its on someone's radar.
[Verizon Samsung Galaxy S III] shadrach47:
Awesome, all I needed to hear.
[Verizon Samsung Galaxy S III] s'pht:
can you add in http://review.cyanogenmod.org/#/c/31988/ too - it's on the OP list

.... or I could notice that it was merged yesterday - DERP!
[Verizon Samsung Galaxy S III] invisiblek:
That's been merged already =)
[Verizon Samsung Galaxy S III] Masterfisto:
Anyone, this happens to me daily and is getting really annoying...

Sent from my Cm10.1 Galaxy S3
[Verizon Samsung Galaxy S III] woolbeo:
My power button doesn't work with kernel_3.4_msm-jb_2.5_20130305_d2vzw.zip or kernel_3.4_msm-jb_2.5_20130306_d2vzw.zip. I would have posted it on the gdoc, but nothing shows up in the logs.
[Verizon Samsung Galaxy S III] shadrach47:
Anyone else having trouble with trying to get the in-system superuser app to work? I was using supersu and went through the options to allow another SU app but I can't get the in-system to update the binary. I even installed the playstore version then uninstalled it, but that still can't get it to work. Now I get website redirects to install the playstore koush app when root is requested and can't get the in-system to work. Any ideas?
[Verizon Samsung Galaxy S III] iofthestorm:
I had the exact same issue. I'm guessing you installed the backup script to keep SuperSU installed through nightly flashes. Unfortunately for some reason the option to switch superuser app doesn't remove that script or the files it restores, I think it assumes that you'll install a different standalone app rather than have something provided by the ROM. The solution I used was to delete the backup script from /system/addons.d and then reinstall SuperSU and then pick the "completely unroot" option which should get rid of everything (might not be necessary, strictly speaking just killing the backup script and re flashing the ROM should be enough).
[Verizon Samsung Galaxy S III] shadrach47:
Thanks, that did it. I deleted the script then re flashed.
[Verizon Samsung Galaxy S III] ctsail410:
M2 does not include a fix, however Invisiblek's daily for today does. The fix was also merged this evening so it will be included in the next official nightly as well.
[Verizon Samsung Galaxy S III] ctsail410:
New Linaro daily (03/08) posted at http://d2vzw.ct-sail.com/ROM/CM10.1-LINARO/

Cherry-Picks

- http://review.cyanogenmod.org/#/c/31061/ (Pull-down)

- http://review.cyanogenmod.org/#/c/31062/ (Pull-down)

- http://review.cyanogenmod.org/#/c/31912/ (Battery Bar)

- http://review.cyanogenmod.org/#/c/31913/ (Battery Bar)

- http://review.cyanogenmod.org/#/q/status:open+branch:cm-10.1+topic:linaro,n,z (Linaro)

Reverts

- http://review.cyanogenmod.org/#/c/31616/ (GPS)

- http://review.cyanogenmod.org/#/c/26060/ (GSM)

Misc

- Includes MMS picture size increase

- Includes home button fix (merged)

Between work, the wife, and the kid it took a few days to fix everything that some new merges broke...
[Verizon Samsung Galaxy S III] NegativeOne:
Thanks ctsail. Please consider including http://review.cyanogenmod.org/#/c/33383/ in the next one :). Removes some optimization that causes the longpress issue.
[Verizon Samsung Galaxy S III] RED ZMAN:
It had already been merged...

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] WhammyDroid:
ctsail, could you please create your own thread? thanks!
[Verizon Samsung Galaxy S III] ctsail410:
Sure, no problem folks. I have no issue doing that...I'd rather do what's useful instead of cluttering up a thread!
[Verizon Samsung Galaxy S III] Hybridnoob:
The OP states all kangers are welcome to post their builds...
[Verizon Samsung Galaxy S III] ctsail410:
I know, that's why I posted it in this thread, especially since it's essentially identical to Mastamoon's just with Linaro added. But, I understand the desire to not clutter :D I'll do whatever is most helpful for the community!

Original intent was to provide something as close as possible for those who are interested in performance of one flavor versus the other. The Linaro toolchain and optimizations can add in their own little bugs, though...

---------- Post added at 10:31 AM ---------- Previous post was at 10:30 AM ----------

Linaro thread moved here unless there are objections: http://xdaforums.com/showthread.php?p=38904446
[Verizon Samsung Galaxy S III] SymbioticGenius:
I object, from what I understand this is not just Mastamoon's thread, but the unofficial build thread. I see no reason why you shouldn't be allowed to post your build here when others have done so previously. I feel it's best to keep all the unofficial builds in this thread especially since for the most part they don't deviate much from the official builds. just merging cherry picks before they are approved.
[Verizon Samsung Galaxy S III] funnyperson1:
I think this is what invisiblek wanted too. It's impossible for him to track five different threads for cm bugs. If I recall correctly he didn't like that this thread split off in the first place.
[Verizon Samsung Galaxy S III] ctsail410:
Yea the bug tracking is my major concern. How about I leave the new thread for now and inquire with Invisiblek and mastamoon and we go from there?
[Verizon Samsung Galaxy S III] invisiblek:
Someone who can test global roaming, please PM me.

I put together a patch for it but I have no way of testing it.

Thanks.

EDIT:

http://review.cyanogenmod.org/33465

and

http://review.cyanogenmod.org/33466
[Verizon Samsung Galaxy S III] ctsail410:
Your code makes all the sense in the world to me, assuming system.prop sets the variable correctly :)
[Verizon Samsung Galaxy S III] invisiblek:
system.prop gets added as part of our build.prop during compilation. That's where SystemProperties gets its information about our device and basically how our build.prop is used throughout android.
[Verizon Samsung Galaxy S III] ctsail410:
I follow...I should have been clearer. I see no obvious flaw in your code, which is about as straight-forward and clean as possible. I just can't verify that it all works!
[Verizon Samsung Galaxy S III] luv2increase:
Linaro is AWESOME! Masta didn't know how to get linaro working so unofficial cm10.1 builds compiled with the linaro toolchain are most welcome!

Sent via Crossbreeded, 100% V6 Supercharged. KT747'd and Linaro Built Paranoid Android 3.10
[Verizon Samsung Galaxy S III] goldsmitht:
but if i don't use built in kernel - i'm partial to KT747 - doesn't that negate the linaro build? thought that was controled by the kernel, and not the ROM?

:cyclops:
[Verizon Samsung Galaxy S III] ctsail410:
The rest of the ROM is built using O3 optimization (versus O2) as well, so there are some performance improvements with those binaries too...in theory.
[Verizon Samsung Galaxy S III] invisiblek:
new patch via noobnl:

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

This would nullify my two patches.

You'll need to go into your data settings and switch it to GSM Global Roaming

Someone please test this, it will be in my daily build today.
[Verizon Samsung Galaxy S III] SilentAce07:
Flashed your ROM and everything is super smooth and fast.

I kept getting the activation screen after a reboot though. I reflashed and I haven't seen it again.

Also, minor issue but music gets crackled and stops for a second anytime a system sound is supposed to happen. You can easily fix it by turning off touch sounds on the system volume options.
[Verizon Samsung Galaxy S III] ctsail410:
Sadly this is/was somewhat common with AOSP, although I have flashed countless times and haven't seen the issue myself. You're the second person who's mentioned an issue with the activation screen with the Linaro builds, and I believe a reflash fixed it for him too.

Do you have the latest gapps (20130301)?

If it becomes persistent I also read that a quick fix is to go to Manage Apps > All and disable Setup Wizard.apk
[Verizon Samsung Galaxy S III] jlokos:
I haven't had the activation screen issue after flashing your 3/8 version. When I got it on your earlier version, I went into settings>wireless & networks>more>mobile networks> CDMA subscription and changed it from NIV to RUIM/Sim and rebooted and it appeared to solve the issue.
[Verizon Samsung Galaxy S III] luv2increase:
Incorrect. The ROM itself is compiled using the Linaro toolchain. That has nothing to do with the kernel. You can have a Linaro GCC toolchain compiled ROM but Google GCC toolchain compiled kernel. You can have a Google GCC compiled ROM and Linaro GCC compiled kernel. You can have both be Google GCC or both Linaro GCC.

I have both the ROM and kernel compiled using the Linaro GCC toolchain. I feel this gives the ultimate best possible experience using our phones.

Masta doesn't mess with the kernel. He just deals with the ROM itself.

Sent via Crossbreeded, 100% V6 Supercharged. KT747'd and Linaro Built Paranoid Android 3.10
[Verizon Samsung Galaxy S III] ctsail410:
Correct. In my case I build both the ROM and Kernel with the Linaro 4.7 GCC toolchain and -O3 optimization.
[Verizon Samsung Galaxy S III] invisiblek:
The majority of the ROM is java, linaro's toolchain is only for C/C++

Although there is some C++ in the ROM, it's not nearly as much as there is java, so its not like its going to give you a substantial amount of performance.

Since when mastamoon builds a rom, it does build a kernel from source, I'd say he deals with the kernel just as much as he deals with the ROM
[Verizon Samsung Galaxy S III] ctsail410:
OK guys, my point in posting these is not to create a giant battle between Linaro vs non-Linaro and drag the whole thread down. I post these so that those who do care can test them and do whatever else they want.

Please let's not go down this path again. I had been keeping these to myself for weeks just because I feared this would happen.

Those who want to use it, use it. Those who don't, don't. In the end it's all about trying to provide the best ROM we can.

---------- Post added at 08:40 PM ---------- Previous post was at 08:34 PM ----------

^^ this

As I've said, I don't post these because I think it's better than any other. I provide it so that others may test and improve.
[Verizon Samsung Galaxy S III] V3TTOO:
Sorry if you feel this is what is going on. The issue isn't Linario, it was the fact that one of the users would constantly preach about it, even though anyone that did make ROMs wasn't interested in building with it. Keep on doing what you are doing. More builds to test things out is always great, and thank you. :good:
[Verizon Samsung Galaxy S III] PVLMTREE:
Hey invisiblek, I was wondering what did you change in your 3.08.13 build?
[Verizon Samsung Galaxy S III] invisiblek:
All the same patches as before, I took out the revert for GSM roaming and added noobnl's patch:

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

This requires the user to enable GSM Roaming by going:

System Settings > More > Mobile Networks > Network Mode >

and choosing GSM Global Roaming

I do need someone to test that before we can merge it.
[Verizon Samsung Galaxy S III] PVLMTREE:
Well, I wasn't sure if it's me, but I tried it and seemed to block my data compatibility. Though, I am running on a T-Mobile sim.

Not sure.

EDIT: Even if I tried other Network Preferred option under Phone Info, problem persist.
[Verizon Samsung Galaxy S III] jayharper08:
I'll be here shortly to clean up.

In the meantime I suggest calming down and letting it go. Thank you.

---Jay--- Moderating from the Slim'd GS3™
[Verizon Samsung Galaxy S III] ctsail410:
Well I did need to patch a few more things in mm-video the other day that don't exist in Gerrit...does that make you angry? :D

By the way, your 3.4 kernel has been running pretty well for me. A few random reboots here and there (for which I posted a bug report). Keep up the good work!