yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] invisiblek:
http://invisiblek.org/sch-i535/roms/cm10.1/cm-10.1-20130421-UNOFFICIAL-d2vzw.zip

synced up as of about noon today

has the new options for vibration intensity (now merged):

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

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

wifi pulls:

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

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

newer wifi blobs:

https://github.com/invisiblek/propr...mmit/a3ba4ada070cd346905fc00b39aaab994b4cb745

caf-rebase branches for display-caf and audio-caf:

https://github.com/CyanogenMod/android_hardware_qcom_audio-caf/tree/caf-rebase

https://github.com/CyanogenMod/android_hardware_qcom_display-caf/tree/caf-rebase

(masta: you should start using these on your builds until they get moved to the master branch)
[Verizon Samsung Galaxy S III] dpaine88:
Thanks Dan!
[Verizon Samsung Galaxy S III] SymbioticGenius:
So far so good on invisiblek build. I totally forgot that battery bar went away since my last build. I have a question as far as lock screen goes, CM 7 used to have a Swype unlock feature where you could make you're own gesture. Is there any way I can help implement that in this build?
[Verizon Samsung Galaxy S III] stearic:
Is anyone still having issues with stereo bluetooth streaming? Just installed the last nightly and cleared chache/dalvik and i'm still getting static while streaming. Is there something else i should be clearing data or cache on? While i've read here i've seen some say they still have it and some that don't so i'm not sure if it's fixed or not.
[Verizon Samsung Galaxy S III] PerCompLLC:
Anyone else experiencing major graphical stuttering on invisiblek's build from today? Didn't have them on yesterday's build from masta...
[Verizon Samsung Galaxy S III] odub303:
No. His build from today is actually the smoothest one I've used in a long time.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] PerCompLLC:
Well I guess I'm the anomaly then. Oh well...
[Verizon Samsung Galaxy S III] SymbioticGenius:
did you clean flash?
[Verizon Samsung Galaxy S III] dpaine88:
I've gotten some
[Verizon Samsung Galaxy S III] masri1987:
i'm running latest liquid with latest kt kernel and i'm getting screen glitches too

d2vzw
[Verizon Samsung Galaxy S III] Restola:
I'm on invisiblek s since last night without noticing any issues yet.

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] mastamoon:
here is a 4/22 build.

-- check out the new haptic vibration settings in Settings>Advanced>Haptic thanks to Hrubak and InvisibleK

-- back to the old wifi drivers for a minute.. cherry pick was being an asshole on them for some reason

-- switched to a different ril as a test. Data/phone/sms work.. should be ok, let me know if you see any good/bad stuff. (you can switch back to the old ril by replacing SamsungQualcommUiccRIL with SamsungCDMAQualcommRIL in the build.prop (ro.telephony.ril.class)

-- repo sync @ 3pm EST

Download -- http://bit.ly/12CwnXd

Going to leave 4/20 up until tomorrow.

Had some great battery life on my 4/20 build this weekend. I remember when 2 hours SoT was a lot! :victory:
[Verizon Samsung Galaxy S III] Hybridnoob:
I hate to ask, but do you have the hash for this build?
[Verizon Samsung Galaxy S III] mastamoon:
http://truelinux.net/sch-i535/masta...22-UNOFFICIAL-d2vzw-reverts-adreno.zip.md5sum
[Verizon Samsung Galaxy S III] mikejr83:
Masta, do you think the adreno blobs will make it into the official? I've been following along but I don't really understand where this build is with these changes. Not saying that I don't know what is/isn't included just not sure what the path is for each of the differences for the cherry picks and reverts. Would you mind briefly giving a "status of your build" post? I am interested in seeing what we're waiting on to be merged into source and what you've reverted for testing or functionality.

I'm a big fan of the KT kernel and want to have the best kernel on the best cm build.
[Verizon Samsung Galaxy S III] Hybridnoob:
Thanks, I had checked the regular build section, but didn't think to check the test section (never tried one before now).
[Verizon Samsung Galaxy S III] AdMire:
I have as well, still.
[Verizon Samsung Galaxy S III] goldsmitht:
Had some screen flickering on bottom half of screen playing a game. But clicked on the disable hardware... And it went away. Back on Moons 4/19 and alls well
[Verizon Samsung Galaxy S III] PerCompLLC:
No screen flicker for me on masta's 4/22... :thumbup:
[Verizon Samsung Galaxy S III] Gatanater:
Is the new 4/22 stable enough that I can use the newest LeanKernel instead of Masta's custom one built for the reboots?
[Verizon Samsung Galaxy S III] sivarticus85:
My wife was unable to hang up on her end when she places a call with the new RIL edit. Switching to the old edit fixed this problem.
[Verizon Samsung Galaxy S III] Desterly:
The goal is to have newer adreno blobs in place but I'm not sure if it will be these ones. Cyanogen is pretty convinced still that these are buggy and waiting for new drops from QCOM before putting in place (last i heard).

AFAIK, all cherry picks/reverts that masta does is in the first post of the thread.

Right now there are two major outstanding issues effecting a lot of people: 1) random reboots 2) ION memory issues.

Cyanogen is also experiencing problems with #1 so I know we'll get that one fixed ASAP (maybe even got merged last night, not sure)

#2 is one that effects less people but should be next on the list.
[Verizon Samsung Galaxy S III] HMkX2:
I'd like to mention one other bug that affects CM10.1 in general, but since I am using Masta's build I don't want to report it in that thread -- and can't afford to reflash vanilla CM10.1 just yet.

EXT4 support was merged March 4th here ( http://review.cyanogenmod.org/#/c/31215/ )... I ran into the issue while working on my script that adds exfat/ntfs-3g/ext4 support.

Since the patch, CM10.1 correctly detects and mounts EXT4 cards through FUSE (mounts the vold:176:33 device under /mnt as EXT4, then uses "sdcard" binary to mount that to /storage/sdcard1 stripped of permissions).

However, the sdcard binary does not terminate cleanly if the card is unmounted. I created a test FUSE mount in an ADB shell using "sdcard /storage/myext4mounteddir /cache/testmount 2>&1 &", then unmounted it. Problem is, the sdcard process didn't terminate -- and started spewing non-stop fuse errors to STDERR.

This SAME problem happens when you unmount using regular CM10.1 -- you can verify with "ps|grep sdcard". Each time you eject and remount an EXT4 card, another error-spewing "sdcard" zombie process is created, and it lags out the phone. If you kill the processes, the phone becomes responsive again.

Anyone know how I'd go about reporting this? I also found an issue with the current (read-only) NTFS support in Ntfs.h, but again, am not sure whom to report it to.
[Verizon Samsung Galaxy S III] funnyperson1:
I think CM only accepts bug reports on stable/M builds so you would need to verify the bug exists on the M3 build (http://download.cyanogenmod.org/get/jenkins/24820/cm-10.1-20130411-EXPERIMENTAL-d2vzw-M3.zip) and submit a bug report to their bug tracker:

https://jira.cyanogenmod.org/secure/Dashboard.jspa

That said, since you posted here maybe mastamoon or invisiblek can take a look at it.

I'm also curious why we even need FUSE for ext4, obviously EXT4 support is built into the kernel, why can't we just natively mount our sdcard that way? I was dissapointed when I found you could only mount FAT32 or exFAT, thanks for your work HMk.
[Verizon Samsung Galaxy S III] HMkX2:
Thanks, that's exactly what I was looking for. Also, I wasn't responsible for vold support, Daniel Hillenbrand deserves credit for that. My method is more of a hack.

The FUSE wrapper was a byproduct of the Google's shift from a separate (FAT) Data and (EXT4) System partitions to a single unified (EXT4) partition. Basically, people were running out of space to install apps, so the FUSE-vfat wrapper was added as "legacy emulation" to fully utilize the internal-sd flash chip. It was a simple thought to repurpose it for doing the same to external-sd.

Without it, an app may "accidentally" create a file as root:root, so it might be inaccessible to regular users. Most people just don't want to deal with the extra complexity, but others do for the >4GB limit.
[Verizon Samsung Galaxy S III] Silvares:
Has any of you had the issue that SMS, if longer than 160 characters is not received in order by the recipient?
[Verizon Samsung Galaxy S III] mastamoon:
4/23 build in OP

-- this is a non-"adreno" based build. Trying out the new display and audio caf-rebase branches.

-- repo sync @ 3:30pm EST
[Verizon Samsung Galaxy S III] landale:
Just flashed 4/23 and so far no flickering issues here. I flashed over the 4/17 build and never had any flickering there either FWIW. Eager to see if all of these new RIL commits help at all in low signal areas.
[Verizon Samsung Galaxy S III] mastamoon:
I had major flickering just sitting at the home screen. :banghead:
[Verizon Samsung Galaxy S III] PerCompLLC:
On which build? That's exactly what I was experiencing on invisiblek's build from the other day... But no flickering at all on your build from yesterday.
[Verizon Samsung Galaxy S III] mastamoon:
On the one I just posted.

I'll have to work on getting the adreno build to build again. Something merged today that broke it.
[Verizon Samsung Galaxy S III] PerCompLLC:
Gotcha
[Verizon Samsung Galaxy S III] Gatanater:
Can the most recent build run the most recent lean kernel without reboots?

---------- Post added at 06:03 PM ---------- Previous post was at 05:39 PM ----------

Can the most recent build run the most recent lean kernel without reboots?
[Verizon Samsung Galaxy S III] mastamoon:
You should be able to use leankernel with this build, I doubt it cures the reboot issue.

Though I have had 0 reboots during this outbreak.
[Verizon Samsung Galaxy S III] PerCompLLC:
I have to say, I have yet to have a reboot...
[Verizon Samsung Galaxy S III] DRW315:
After breaking the screen on my old S3, I installed masta's 4/20 build directly after rooting my replacement. I haven't had a reboot since. Its been running great! I still have Bluetooth random skipping bug, which I haven't seen mentioned in awhile, but no display flickering or reboots! Thanks to masta, Invisiblek, et. al.!
[Verizon Samsung Galaxy S III] Hybridnoob:
I almost thought you produced the perfect build, but I finally got the screen flickering too (on my home screen as well). One other (bigger) issue I've noticed is the camera doesn't work... While open, the whole screen flashes green about three times a second and once a picture is captured, the gallery force closes. Fixing permissions and clearing app data doesn't help. I'm wondering if anyone else is experiencing that. I used the camera a couple of days (and builds) ago without issue.

I look forward to the next build because signal and data speeds did seem better for me on today's build. Keep up the good work, Masta!
[Verizon Samsung Galaxy S III] goldsmitht:
OK, MAJOR flickering using camera on latest build. Constant green screen flashing while trying to taken picture. And got a "gallery not responding" and no picture when taking picture.

:mad: :what: :screwy:
[Verizon Samsung Galaxy S III] landale:
Yup, I can confirm the camera is major messed up on the 4/23 build. Green flickering. Reverting back for now.
[Verizon Samsung Galaxy S III] goldsmitht:
I will admit that it seems like my signal strength was better n new build
[Verizon Samsung Galaxy S III] Gatanater:
Anyone have a link for 4/22?
[Verizon Samsung Galaxy S III] Gibscreen:
http://db.tt/zaXuhU1m

Uploaded a copy i have.
[Verizon Samsung Galaxy S III] termleech:
Could very well be. There were a number of commits for d2vzw for "better data" which definitely could lead to better signal.

---------- Post added at 09:03 AM ---------- Previous post was at 09:01 AM ----------

Masta I noticed that in display-caf they brought back the build.prop to limit the device to three layers. Looks like the old 4 layer overrun is back. Might try sticking that in your build.prop and see if that resolves some of the issues.
[Verizon Samsung Galaxy S III] goldsmitht:
but... but... wait, the TV says more is better and better is better, and we all want more, right?

noticed the data being a bit better, but didn't really notice if my wifi signal was better. Wife has a Razr M, and she can get wifi signals where i can't. Understand the radio diffrences and all, but was hoping the changes would help.

hate it when the wife gets more than i do.

:p :mad:
[Verizon Samsung Galaxy S III] termleech:
Lol it's not the size of the boat but the motion of the ocean :)

Honestly the d2 has stuck as 3 layers for a long time and only recently was able to do 4. I never noticed any problems with 3 but have seen a lot of issues with 4.

I don't think the build.prop stuff that was added will do anything for wifi. It was all for initialization stuff for the cell radio.
[Verizon Samsung Galaxy S III] goldsmitht:
went back and tested a version that IMO posted on this forum; has the shakes, but not the camera issue. SOMETHING between those two builds was what did it.

hope that helps narrow it down.

:cyclops:
[Verizon Samsung Galaxy S III] mastamoon:
4/24 build in the OP

-- GPS commit that might kill the need for the gps revert I have been using

-- repo-sync at 2:30 PM EST

Let me know if you guys have flicker and/or GPS issues. :D

*** If you are one of the unlucky folk out there with constant reboots, please install http://invisiblek.org/sch-i535/roms/cm10.1/dragons_ahead/cm-10.1-20130424-UNOFFICIAL-d2vzw.zip and let us know if this kills them ***
[Verizon Samsung Galaxy S III] Hybridnoob:
Did you have any camera issues on the yesterday's build? I know a few of us did. Other than that and the occasional screen flickering, it's been the best build yet!
[Verizon Samsung Galaxy S III] mastamoon:
Yes I did. No camera issues yet on this one. I added a build.prop to see if it kills the flicker for now.
[Verizon Samsung Galaxy S III] goldsmitht:
Is this built with the new drivers?
[Verizon Samsung Galaxy S III] landale:
The 4/24 build seems to have fixed the camera issue from 4/23 but the new GPS commit doesn't work for me. I am now unable to get a GPS lock with it.
[Verizon Samsung Galaxy S III] goldsmitht:
Everything's seems to be working good, no shakes, green camera shakes are gone, and GPS seems to be working for me. Never has been spot on, but is usable for what I need.

Once again, smoooove as buttttaahhh!

:cool:

Oh Yeh, is built with new drivers, I see

:D.
[Verizon Samsung Galaxy S III] mastamoon:
Ill check mine out in a few.. no problems adding in the other revert if necessary. This commit seems more likely to get merged so I was hoping it was just as good. :-\
[Verizon Samsung Galaxy S III] landale:
Yeah, I was hoping it would work too. Just in case I rebooted and downloaded GPS Status and it won't show any satellites let alone get a fix, I had no GPS issues on the previous builds. Oh well :(
[Verizon Samsung Galaxy S III] PerCompLLC:
Weird... I just fired up GPS Status after reading your post and got a lock in 4 seconds sitting on my couch inside! I'm on masta's latest (4/24). What gives? Why would it work on some and not others? Interesting...
[Verizon Samsung Galaxy S III] mastamoon:
GPS seems to work fine for me too.

Walked outside, this is like 5 seconds in.

http://db.tt/HtZKQvwX
[Verizon Samsung Galaxy S III] mastamoon:
I know the fix for this has been flash to touchwiz, get GPS lock, then flash back. But if the revert works for you I can see if the can both be used.
[Verizon Samsung Galaxy S III] landale:
I will play around with it. Hopefully I can get it working again.
[Verizon Samsung Galaxy S III] PerCompLLC:
But I did just get a significant screen flicker playing a game... :eek:
[Verizon Samsung Galaxy S III] Hybridnoob:
Same here. Camera now works, but GPS doesn't. Unable to locate a single satellite. Haven't noticed any screen flickering so far. This is the first build I've experienced any GPS issues, so that revert may still be necessary.
[Verizon Samsung Galaxy S III] landale:
Glad it's not just me. Without the GPS revert I have never gotten GPS to work for me on any AOSP ROM which is why I have always stuck with Mastamoon's unofficials. Hopefully we can get it back in tomorrow's build.
[Verizon Samsung Galaxy S III] funnyperson1:
Are you talking about invisiblek's patch for initializing the RIL values? I looked at the recent changelogs and that was the only one I saw pertaining to RIL/data. Or do you think that the improved signal being reported is from the RIL test build that Mastamoon made?
[Verizon Samsung Galaxy S III] iofthestorm:
I think it's always been the case that it works for some and not others, because I've never had to use mastamoon's builds to get GPS to work, it always worked for me.
[Verizon Samsung Galaxy S III] landale:
Consider yourself lucky. I just reverted back to the 4/20 build and went from 0 satellites on the 4/24 build to instantly seeing 21 and locking to 11 of them within seconds, all in the same location at my desk at work.
[Verizon Samsung Galaxy S III] Reborn627:
Flawless here for the last 2 hours running mastamoon's build with GideonX's latest 3.4. GPS Status grabs 10 of 18 in under 20 seconds sitting on my couch. No flicker & camera works great. As always, quite pleased. Thanks!

Ray
[Verizon Samsung Galaxy S III] PerCompLLC:
Just for the record, the only time I saw a flicker was on an older side loaded game - BubbleBuster
[Verizon Samsung Galaxy S III] WhammyDroid:
Downloaded the 4/24 build a few hours ago. I am also seeing the new GPS commit break the GPS functionality. I could not get signal being outside standing around for 5 minutes. Usually (with the normal GPS revert) it is an instant lock.
[Verizon Samsung Galaxy S III] SilentAce07:
Flashed 4/22 and have no issues so far. Activation bug finally went away though.
[Verizon Samsung Galaxy S III] goldsmitht:
Sorry, flickers are back
[Verizon Samsung Galaxy S III] mastamoon:
Nothing here yet. 7.5 hours of uptime. 1 hour of screen on time.
[Verizon Samsung Galaxy S III] alee:
Just wanted to throw a global roaming update... been using the 4/12 build for my Europe trip, and the phone has not skipped a beat while roaming out here. Battery life though is extremely poor though (8 hrs or so from full to empty with very light use) and in the battery settings, it shows "voice calls" in use the entire time the phone is running in GSM mode.

Not sure if that's necessarily the reason for the poor battery life though. I am roaming with the Verizon SIM and the intl data plan. Anyone else have similar experiences on the roaming piece w/battery life?
[Verizon Samsung Galaxy S III] landale:
I used my phone in Europe last month on this ROM and it worked great with no problems. I however used local SIM cards as Verizon's rate of $25 per 100MB is highway robbery compared to the local rates (in London I paid £10 for a SIM with 500MB and in Amsterdam €2 for a SIM with 1GB of data) . My phone didn't say anything about voice calls in use and unlike when roaming in the US on ATT or Tmobile HSPA worked so I had solid 3G service as well. What mode do you have your phone set at for Mobile Networks? I used WCDMA prefered on mine.
[Verizon Samsung Galaxy S III] goldsmitht:
flickers are intermittent, and mostly when i was playing games and looking at twitter for over an hour or so of screen on time. might be why.

but none today, so far, except for one or two, nothing major like before.

as for GPS, at home with wifi on, it picked up what side of the couch i was sitting on. tested it last night on 4G, in an area i've not tested before, and it was well within "tollerable" limits.

:cyclops:
[Verizon Samsung Galaxy S III] termleech:
Curious did you dirty flash or clean flash? I'm having GPS issues but its a clean flash so trying to narrow it down.
[Verizon Samsung Galaxy S III] Gatanater:
I clean flashed a build that GPS works for all, then dirty flashed 4/24. It seems as like you dirty off of a good build, the good traits will stay.
[Verizon Samsung Galaxy S III] landale:
I don't think it works that way. At least not for me. I dirty flashed off a ROM where GPS worked to 4/24 and GPS didn't work for me. Hopefully the regular revert is back in today's build.
[Verizon Samsung Galaxy S III] goldsmitht:
Dirty, sorry. But it seems to depend on how good my service is. Better service, better accuracy, of course. :screwy:
[Verizon Samsung Galaxy S III] :
Sorry if this is a little OT, but I've had pretty consistent reboots when I am tethering, have more than one device attached, and am pulling a good amount of data.

I'm not knowledgeable on how to pull a logcat from a rebooted phone, other than using the SysLog app to pull a last_kmsg log. I've attached one that I (think) I grabbed from my last reboot after the described issue. I'm not sure if I did that right either....

Thanks. Please let me know if there is a better way to help solve the issue. Appreciate it.
[Verizon Samsung Galaxy S III] mastamoon:
4/25 build in OP

-- brought back the GPS revert for all ya'll that have non functioning GPS on my last build. Let me know if its all good now.

-- using the CM10.1-rebase kernel to hopefully quiet down the random reboot issue

-- debug.mdpcomp.maxlayer=3 added to build.prop to quiet down the flicker

-- repo sync @ 2:30PM EST

No more 'adreno' builds needed as the new drivers are included in the official nightlies now. Things should be very smooth. Phone is going to rock when cyanogen and the team kill the random reboots and flicker. Shouldn't be long now.

Enjoy! :good:
[Verizon Samsung Galaxy S III] ddggttff3:
Thanks man! Finally found a good build to replace the 4.20 nightly :P So far its rock solid!
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm still not able to get any satellites on this build. I have no idea why. I even reverted to 4/20 and confirmed working GPS before dirty flashing over top. Anyone else who had problems have it working now? I wish I had better news. Sorry, Masta (your builds are still the best!).

Do I need to consider a clean install now?
[Verizon Samsung Galaxy S III] landale:
I can confirm the same. GPS is still broken for me on 4/25. I am guessing the new commit somehow overrides the revert. Nandroiding back again....
[Verizon Samsung Galaxy S III] mastamoon:
Damn GPS. Tomorrow I will a few builds, with a few combos of the GPS stuff.
[Verizon Samsung Galaxy S III] odub303:
GPS isn't broken, it just isn't working for you. It's fine for many many people.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] landale:
Understood, I thought based on my quoting and previous posts it was implied I was just reporting my personal findings. I do realize many people don't have GPS problems with any AOSP ROM but there are quite a few people who can't get their GPS to work at all without this particular revert which is why we have turned to this ROM in the first place. I like many have tried numerous fixes without any luck so I just wanted to alert these people before they went through the trouble of flashing the 4/25 build thinking it would work like prior builds did when it comes to GPS. Regardless I will edit my earlier post to be more clear.
[Verizon Samsung Galaxy S III] odub303:
Just out of curiosity, have you cleared data in Google services framework and rebooted? Have you downloaded GPS test from the market and used it to clear and redownload agps data? In my experience, I have had the most success using that app to reset agps data. Please note that you may have to go outside and let the app run for up to 10 minutes in order to get a lock. I've had situations where I thought it was hopeless only to have it start working after that long.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] landale:
Those are actually the first two things I did after I flashed and failed to get a GPS lock. I also uninstalled and reinstalled Maps. Sadly this is just how it's been for a long time for me on AOSP ROM's except with that one particular revert. When that revert is in there even on a clean flash I get instant GPS locks, without it zero satellites show up.