yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] pitmanr2003:
Does this have the nav bar. I love cm but use aokp cause I can't live with out nav

Bar
[Verizon Samsung Galaxy S III] wctaylor79:
Masta.. Yesterday and today build. The phone won't work with wired headset. Works on official not on yours. Any idea?
[Verizon Samsung Galaxy S III] gcutter:
I installed the download from Post 143 BT Music Streaming works great the best it has ever worked. I haven't tried transferring files or Phone Audio. I dirty flashed over Mastamoon Post 82 2nd build. Everything working great so far. I had problems with LSmooth Beta 2 GPS on my CardioTrainer doubling my distance and the BT faded out after a while on LD beta2. I have been running the 1/16 build from Post 143 for 20 hours pretty hard without a single issue no reboots or SODs or lags.

Rock On!
[Verizon Samsung Galaxy S III] WhammyDroid:
Masta, thoughts on adding these two commits:

http://xdaforums.com/showpost.php?p=36810898&postcount=993
[Verizon Samsung Galaxy S III] PerCompLLC:
Not sure. So, when in doubt...backup.
[Verizon Samsung Galaxy S III] minnysota:
Has anyone else experienced this?
[Verizon Samsung Galaxy S III] dbornack:
Yeah, I just did.. I was able to just back out of it and get to my home screen though.

One thing I do notice.. it takes a good 60-90 seconds to get into 3G/4G data after my home screen comes up. Maybe the ROM thinks the phone isn't activated yet because of that.
[Verizon Samsung Galaxy S III] mastamoon:
Will be in today's build.

This is common. Usually you can tap the 4 corners from top left, clockwise, to bottom left. Or what others have mentioned is installing the rom alone, booting, after done booting, reboot and install gapps.
[Verizon Samsung Galaxy S III] Mean Sixteen:
When I enable profiles my ringer stops working completely. If I turn them off ringer works again. Did this on liquid as well.

Any thoughts?

Sent through mental telepathy...or my unlocked SGS3
[Verizon Samsung Galaxy S III] OaklandZoo:
Just flashed the latest build from this thread and it's running fantastically. I flashed over from CleanRom (TouchWiz) and this AOSP rom has better battery life and it is crazy responsive. I've not had any network handoff issues, noticed no flickering yet, and it appears perfectly stable. I'm so pleased that I switched. Thank you for the unofficial build. I'm very very happy with it.:good:

Edit: In addition, I was never asked to reactivate, even after a reboot.
[Verizon Samsung Galaxy S III] Recon0212:
Just clean flashed 1/16, was fine until I rebooted and got the "activation screen" which I backed out of, and got the 0 dBm glitch again :/

Maybe it was a fluke though, I'll have to try it again later.
[Verizon Samsung Galaxy S III] minnysota:
Thanks for the quick response, Mastamoon. So it's nothing to worry about (i.e. there's not an activation process running in the background)?

And what is the 0 dBm glitch? There are times when I'll have a poor connection (0 bars), but retain the 4G icon. Then when I check the dBm it's at 0. Is that what you're referring to?
[Verizon Samsung Galaxy S III] yznhmr:
Cleared data on SMSpro and on Messaging, and rebooted, cleared cashe and DC.. still not sending Pic form text..
[Verizon Samsung Galaxy S III] Recon0212:
Yeah, when that happens I can still call/text just data is really slow.
[Verizon Samsung Galaxy S III] mangler1055:
is there any way to get rid of the quick panel thing? i tried turning it of in settings without luck.

is there any difference between it and the power widget.. besides the size of the icons?
[Verizon Samsung Galaxy S III] wappowe1:
Settings - System - Quick Settings Panel - Quick Pulldown = off
[Verizon Samsung Galaxy S III] bluezr1:
The only problem I'm having now is we (being the wife and two kids) all have the same phones, with mine being the only one rooted and running a custom rom. And now for some reason in my house I'm the only one who's phone prefers 3g over 4g. I would toggle airplane mode on and off until I picked up 4g, and then with my phone and the wife's phone I would walk around the house and where mine would within a few feet would switch back to 4g. This happens even if I go outside it'll stay on 3g. This has been going on with the last two builds. I'll be leaving soon for work where I always get 4g and see what happens.

Otherwise its been pretty flawless with not a single reboot.
[Verizon Samsung Galaxy S III] soapinmouth:
Happened to me to I just hit home button out of it and everything working fine.

Sent from my liquid smooth gs3
[Verizon Samsung Galaxy S III] mangler1055:
yeah, that takes care of which side of the notification bar i pull down to get there automatically.

i want to get rid of the icon in the notification panel. it's currently in the top left which is where the "clear all" icon has always been.

is that possible?

Thanks.
[Verizon Samsung Galaxy S III] mastamoon:
Here is my 1/17 afternoonly. All the standard stuff as before for working A2DP. Picked an update to LockClock/Chronos just because. Might get a Chronos FC upon first boot, didn't get one on second so should be ok. Added invisiblek's 2 commits and 2 compiler commits. Repo Sync as of 3pm EST.

Please keep an eye on the 3G/4G handoff for me.. let me know if you have more/less issues where your phone loses connection.

Download: http://d-h.st/p9M

Cherry Picks:

GPS - http://review.cyanogenmod.org/#/c/29349/

RIL - http://review.cyanogenmod.org/#/c/28195/

RIL - http://review.cyanogenmod.org/#/c/29653/

RIL - http://review.cyanogenmod.org/#/c/29654/

RIL - http://review.cyanogenmod.org/#/c/30428/

RIL - http://review.cyanogenmod.org/#/c/30427/

Bluetooth - http://review.cyanogenmod.org/#/c/29952/

Bluetooth - http://review.cyanogenmod.org/#/c/29951/

Bluetooth - http://review.cyanogenmod.org/#/c/29950/

LockClock - http://review.cyanogenmod.org/#/c/29912/

Compiler - http://review.cyanogenmod.org/#/c/29800/

Compiler - http://review.cyanogenmod.org/#/c/29799/

Reverts:

Audio - http://review.cyanogenmod.org/#/c/29175/ - Fixes Bluetooth/A2DP Streaming *thanks mkasick

Audio - http://review.cyanogenmod.org/#/c/29174/ - Fixes Bluetooth/A2DP Streaming *thanks mkasick

Audio - http://review.cyanogenmod.org/#/c/29661/ - Fixes In Call Volume Adjustment *thanks termleech

As always check here to see what my repo sync may have missed: CM Gerrit - Merged

Enjoy!

NOTE: I haven't disabled LPA in either of these builds. I haven't had any wake-lock issues and its easy enough to do yourself with any root file manager. If your having battery/wakelock issues, disable LPA in your build.prop by editing the line lpa.decode=true to lpa.decode=false *thanks termleech
[Verizon Samsung Galaxy S III] invisiblek:
fyi: those two are not strictly kernel-related

they are compiler optimizations
[Verizon Samsung Galaxy S III] mastamoon:
I actually had the description as compiler stuff then switched it lol..
[Verizon Samsung Galaxy S III] stearic:
Are you able to get into the settings for the app? I get a force close every time.
[Verizon Samsung Galaxy S III] Reborn627:
Same here. System app?

Ray

EDIT: Installed to system and still force closes. Guessing there are dependencies not found in CM. Probably need TW for full function.
[Verizon Samsung Galaxy S III] craigbailey1986:
No I assume because its a tw bases app. The settings for the app is actually in settings on the gs4 so I've read.
[Verizon Samsung Galaxy S III] ausman89:
I hate to continue to bring this up again, but I'm still having issues with the activation problem...

I change the subscription back to ruim/sim, reboot to recovery, wipe dalvik, dirty flash the same CM build (right now, Masta's 3-27). Sometimes it works for a couple boots and sometimes it only lasts for 1 reboot.

This is the way I thought was the most successful in clearing the issue through multiple reboots.

Anyone have another better way that they are more sure works to clear the issue through multiple reboots?
[Verizon Samsung Galaxy S III] mastamoon:
I dirty flash, no wipes, daily with no issue. Really strange.
[Verizon Samsung Galaxy S III] razorloves:
same here man. i've tried all the suggested things. doesn't help. still a great rom though. i just avoid rebooting. lol
[Verizon Samsung Galaxy S III] Chris123NT:
Try wiping the cache partition AND dalvik cache, not just dalvik. I think you need to do both for it to work.
[Verizon Samsung Galaxy S III] ausman89:
Balls.

I tried both and in different orders and it didn't seem to make a difference...Thanks though.

Anybody know for sure how far back would be "safe"? I think the latest one I found absolutely no activation issue with was 2-15. Can any confirm/deny or have another version?
[Verizon Samsung Galaxy S III] goldsmitht:
are you coming from another ROM, or just trying to do a clean flash? CM10.1 is pretty stable, and clean flashing not really needed if on it already

:cyclops:
[Verizon Samsung Galaxy S III] ausman89:
It's a new phone, so coming from stock.

Even tried today (again) to odin back to 4.0.4 stock and start the whole root/unlock/etc. process over. This time I immediately flashed to the 3-27 Masta build.
[Verizon Samsung Galaxy S III] mastamoon:
3/28 build is in OP

- msm_otg wakelock fix was merged

- repo sync at 3:10pm EST

Probably wont have a build up till Monday. Happy Easter everybody.

P.S. with detule's guidance I built a kernel that moves our ram console back to where it was in 3.0. Thought maybe it might help with some freezing or issues in general (I think :P) If you want to try it, here it is http://bit.ly/XK4gQT
[Verizon Samsung Galaxy S III] Reborn627:
I'll give it a rip, what the hey ;) I've been running the Gideon 3.4.y kernel for the last 36 hours or so, with your 3-26 build, with great luck. 19.5 hours with 32% battery remaining. No lockup, hangs, reboots. I'll flash this build and kernel and see where I end up tomorrow afternoon. Thanks again for all the work you do!

Peace,

Ray
[Verizon Samsung Galaxy S III] anacree:
I'd been on the 3/07 build for a while, and finally updated to 3/25 or somewhere around there. Now I'm having the SystemUI crash on me, which means the screen freezes and I have to reboot. It actually pops up a notification that says SystemUI (or one time it said Trebuchet) had stopped responding. Is this what everyone else means when they say "freezing".

Since updating, I haven't had any SOD issues (where the screen won't turn back on, but the touch buttons illuminate).

Thanks
[Verizon Samsung Galaxy S III] V3TTOO:
Try going into recovery and FORMAT, not wipe /system, /data, /cache /sdcard, and /data and /data/media. This is assuming you are on CWM 6.0.3.0. Once you are done with that, reboot to make sure nothing happens. Restart and go into recovery, do it one more time, then install Masta's ROM from your external SD card. Factory restore, wipe cache and dalvik, and fix permissions, just in case. That is what I pretty much did and it fixed the issues I had. Make sure you have GAPPS and the ROM on your card. I did notice that I couldn't activate without GAPPS for some reason, since I forgot to put it on my SD card.

Hope that helps.
[Verizon Samsung Galaxy S III] imtoomuch:
Does format erase the whole drive or just the system partition?
[Verizon Samsung Galaxy S III] Reborn627:
Ok, I have run into a couple of things. They may or may not be related. On my way home from work I attempted to make a call to the radio station that I listen to via the bluetooth in my car. When I finally got through I cod not be heard. My first thought was bad cell signal. So, I then decided to call my home phone and leave a message. This way I cod be sure if I cod be heard. It seems that there was a significant delay, roughly 4 seconds. I know this because the message that I had left for myself on my machine began half way into what I had left. Is this making sense? Prior to this last flash I've only received calls via blue tooth. I haven't had any trouble with those calls. I'm restoring the backup I made a couple hours ago and I'll test to see if the same problem exists. I also experienced a lockup and reboot just before posting here. It's the first time I've experienced either. Not sure if it's really rom or the kernel. I'll post back with what I find.

Peace,

Ray
[Verizon Samsung Galaxy S III] V3TTOO:
Formatting erases anything on the partition you format. So if you format /system, it is just the system partition. /sdcard is where your saved info usually is. /data I am not sure, but I assume it is where app data and maybe some apps are held. I recommend it all since wipe only clears out system and cache, while format you can do data and sdcard as well, which will be a more "clean" install than just a factory wipe. Wipe implies it goes back to factory settings, not that the files got erased. So in turn formatting will erase everything compared to resetting it to an image. If that make any sense. :p

---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------

Hey, is anyone having issues with audio when doing things, like checking emails/text/web? Every time I am on Pandora, I will get static sounds when I try to use things. I also tested it through the headphones and I get the same problem. For some reason, I have issues with my car BT where it happens all the time.
[Verizon Samsung Galaxy S III] Reborn627:
Ok, after restoring my backup I found a 2 second delay just using the phone and no delay at all with bluetooth in my car. Doesn't make a lot of sense to be honest. Is there anyone else who could test sending calls on and off bluetooth with today's release and mastamoon new kernel. I'm currently, back to, the 3-26 build and the GideonX kernel from yesterday. Could have been a fluke. Tough to tell without bouncing back and forth.

Thanks,

Ray
[Verizon Samsung Galaxy S III] mikejr83:
So I've been out of the thread a little while. My phone made a disappearance on a Delta flight last week. I guess it's now flying the friendly skies.

Anyhow, I tried to do my best catching up on the dozen or so pages or so since I last read. Normally read all the posts from my phone for the last day while getting ready for bed. I can't seem to make heads or tails if the issue with activation has been fixed.

Is there a definitive answer on whether the activation issue is no longer in the latest build? When I got my replacement phone I went from TW 4.1.1 (what was on it when it came from Asurion) to mastamoons 2/28 build; the last known build before the activation issue. I still see there may be some issues with the 3.4 kernel, but other than that is there any concern to dirty flash to the latest?
[Verizon Samsung Galaxy S III] goldsmitht:
No issues here; some have problems with reboots using stock kernel, but I'm on LK 5.04 exp @ and having no issues at all. Dirty flash is recommended tho

:thumbup:

:D
[Verizon Samsung Galaxy S III] goldsmitht:
Had a SOD today, not sure if it was ROM or kernel related, so figure I'll post in both.

http://db.tt/oQmbkrX7

Other than this, really haven't had any problems
[Verizon Samsung Galaxy S III] bobby janow:
Naturally, you do not want to format your sdcard unless you want to return your phone or you have every bit of data on a computer hard drive backed up. The way I think of it is like this. From the wipe menu. the Factory reset option will wipe out any programs you have installed and return the phone to the state of a fresh install of the existing rom you have on the phone as of the wipe function. So if you factory reset while on Liquid Version x.x then on reboot you will have a clean boot of that x.x with no programs installed. You would then have to either reinstall or restore via titanium or any other program like that.

A system/format will wipe the rom but leave the programs intact. So if you wipe system/format then you can't boot the phone until you install another rom or restore a nandy. If you then install another rom over that you're asking for trouble. If you install another version of the same rom then it's called a dirty flash.

If you do both, factory reset and system/format then you have nothing and need a rom to flash and a way to restore all your programs with the data still residing on your sdcard. Titanium backup - restore of app+data is the way I do it, but ymmv.
[Verizon Samsung Galaxy S III] ugachris:
Looks like Steve found what's causing the crashes:

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

You wouldn't be able to drop a new build, would you?
[Verizon Samsung Galaxy S III] prototype7:
I might be able to later today, anything you wanted cherry picked?
[Verizon Samsung Galaxy S III] PerCompLLC:
The masta reverts and cherry picks would be good from the OP. :fingers-crossed:
[Verizon Samsung Galaxy S III] prototype7:
Will do, unfortunately SSH isn't working so it'll be around 5 (EST) before I can get it done and uploaded, check back then.
[Verizon Samsung Galaxy S III] Restola:
Awesome!

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] ctsail410:
I'll have a build up in the Linaro thread incorporating this in around 45 min or so for those who are desperate (see OP).

EDIT: Found here http://d2vzw.ct-sail.com/ROM/CM10.1-LINARO/

I can build a non-linaro shortly afterwards if folks would rather try that.
[Verizon Samsung Galaxy S III] ausman89:
I don't really get the whole linaro thing... I know it is supposedly faster, but are there any downsides to using a linaro build then?
[Verizon Samsung Galaxy S III] ctsail410:
Essentially the difference is that the C/C++ portions of the ROM (including Kernel) are compiled with a higher level of compiler optimization. However, a LOT of Android is written in Java and Linaro has no effect on that.

Some swear it's faster, others swear it's just Voodo black-magic. It used to make a big difference, but really doesn't do too much (in my opinion) with CM10.1. Some people prefer it, though, so I build with it.

The down-side is that in theory with higher levels of optimization there could be some more buggy aspects, but I haven't really noticed any. YMMV.
[Verizon Samsung Galaxy S III] ctsail410:
Here are two 3/29 builds for you guys (with Steve's latest kernel commit):

Non-Linaro Build: http://d2vzw.ct-sail.com/ROM/CM10.1/

Linaro Build: http://d2vzw.ct-sail.com/ROM/CM10.1-LINARO/

Same cherry-picks as masta. You can find the MD5s there as well.
[Verizon Samsung Galaxy S III] prototype7:
Cool. Saved me a bit of work, hopefully this works.
[Verizon Samsung Galaxy S III] masri1987:
Anybody see this?

https://github.com/CyanogenMod/andr...mmit/1e7d08721e373fecd7a39db34a8cc8cbec10a02c
[Verizon Samsung Galaxy S III] GideonX:
Yup, it's been seen.
[Verizon Samsung Galaxy S III] ctsail410:
Yep, it's included in the build I posted a few up. So far so good...
[Verizon Samsung Galaxy S III] sithdroid2187:
Everything is running great on the most recent build. Loving it!
[Verizon Samsung Galaxy S III] fromthesticks:
Also running well for me, was having to reboot every 1-2 hours before. I rebooted twice yesterday after the new build and have been using it all day today with no issues
[Verizon Samsung Galaxy S III] eppo12-:
You guys are taking about the non-linaro build that ctsail410 posted? Or the last mastamoon build?
[Verizon Samsung Galaxy S III] fromthesticks:
I've been using only the linaro build the past week or two

Edit : I thought I was posting in the linaro thread before , that's why I didn't specify
[Verizon Samsung Galaxy S III] Reborn627:
Linaro thread can be found here http://xdaforums.com/showthread.php?t=2181743. The OP has the link listed also.

Peace,

Ray
[Verizon Samsung Galaxy S III] sithdroid2187:
Non linaro here
[Verizon Samsung Galaxy S III] fromthesticks:
I understand , I follow both threads and made a mistake
[Verizon Samsung Galaxy S III] sdana:
Any updates on getting pie controls working?
[Verizon Samsung Galaxy S III] ctsail410:
There were a couple new kernel commits and a couple display-related cherry-picks out there so I did a 3/30 build for y'all.

EDIT: Removed link to fix
[Verizon Samsung Galaxy S III] Reborn627:
Is this built off of Mastamoon's previous build or is this something else?

Peace,

Ray
[Verizon Samsung Galaxy S III] GideonX:
Should be just about the same as mastamoon's build with all the same cherry picks.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Reborn627:
And your kernel?
[Verizon Samsung Galaxy S III] ctsail410:
Same picks as masta, same 3.4 kernel. Did anyone flash it? My phone refused to boot. Thinking the display Cherry-Picks messed it up. Wondering if I should pull the link...
[Verizon Samsung Galaxy S III] GideonX:
Nope, stock kernel. You can of course flash BMS afterwards.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] eppo12-:
Yes, refused to boot for me too. Getting random reboots on 3/29.
[Verizon Samsung Galaxy S III] craigbailey1986:
Same here for both issues. I am using official cm10.1 3.30.13 and I don't have any issues so far. I just updated from the ROM updater.
[Verizon Samsung Galaxy S III] ctsail410:
Fixed the issue and I'm rebuilding now. I'll let you know when it's back up!
[Verizon Samsung Galaxy S III] ctsail410:
OK, working build is back up here (now 3/31): http://d2vzw.ct-sail.com/ROM/CM10.1/

Same picks as 3/29. There are a handful of new kernel commits included.
[Verizon Samsung Galaxy S III] pyrostic:
I'm replying to this while on this ROM. Ill know tomorrow if it is done locking up on me.
[Verizon Samsung Galaxy S III] chaplngrillsgt:
I flashed LK and was still getting random reboots and SOD on 3/29...ill give the new one a try.
[Verizon Samsung Galaxy S III] ctsail410:
I'm not sure what Imo has included in whatever version of LK you're using. I assume it's the latest?
[Verizon Samsung Galaxy S III] goldsmitht:
i'm on 3/28, LK 5.1 and no SOD, stutters, nothing. is working great, and trying to let settle so battery life can build up.
[Verizon Samsung Galaxy S III] mastamoon:
4/1 build in OP

- dropped a few commits, explanation in OP

- added a few commits for boot splash screen and wifi driver update

- repo sync @ 3:15pm EST
[Verizon Samsung Galaxy S III] V3TTOO:
Downloading it now. Last build kept causing screen locks and having to reboot. Hopefully some of the new stuff fixes that.

Thanks again Masta.
[Verizon Samsung Galaxy S III] Neverender326:
If you're getting reboots try renaming thermaid to thermaid.bak
[Verizon Samsung Galaxy S III] GideonX:
On stock mastamoon, this doesn't help reboots if you are getting them. All it does is lift the thermal protection.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] V3TTOO:
So far I have not had any issues on the 4/1 build.
[Verizon Samsung Galaxy S III] dpaine88:
So there are still freezes and reboots?

I had heard it was fixed on CM(I'm coming from Liquid)
[Verizon Samsung Galaxy S III] goldsmitht:
not a bit here, running 4/1 with LK's 5.1 stable kernel and nothing but buttery smoothness, no reboots, freezes, SOD's, bluetooth works (well, it does with my bluetooth earbud) call volume is great and adjustable...

hell, even cleared up my acne, and i get better gas mileage to boot!

:cyclops:
[Verizon Samsung Galaxy S III] Hybridnoob:
I can report the same on the stock kernel. Hooray!
[Verizon Samsung Galaxy S III] travisX:
You, sir, get thanks just for your username/avatar.
[Verizon Samsung Galaxy S III] ugachris:
On yesterday's Masta build, I'm seeing Falcon Pro and Google Play Music force close. In Falcon Pro, it takes about three swipes before the app just quits and I go back to the homescreen. In Play Music, the first time I tap on an album the app quits and it goes back to the homescreen. Is anyone seeing similar behavior? I'm wondering if this isn't caused by the tap/touch latency cherry pick (or if this is just me).
[Verizon Samsung Galaxy S III] Hybridnoob:
I did have that with the Play store and another app, but it eventually stopped doing it and is normal now. Give it time and see if it resolves itself...
[Verizon Samsung Galaxy S III] goldsmitht:
+1 was just going to report the same thing, thought it was just the apps, so forcestopped, cleared cache and data, even booted into recovery and cleared cache and dalvik (not sure if i fixed permissions - will try that now)

could be, hasn't happened on any of the other apps so far, ESPN works fine, and i think pay store is good as well

:confused: