yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] mastamoon:
Have you tested ^? Let me know if you have better results.

Try this.. removed..

was causing FC's on my phone.. ill mess with it tomorrow.
[Verizon Samsung Galaxy S III] airmaxx23:
Has the Pandora issues been figured out at all?
[Verizon Samsung Galaxy S III] Hybridnoob:
Works fine here...

---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------

Everything is running great! Thanks for the build!
[Verizon Samsung Galaxy S III] airmaxx23:
Try searching for a new station in the search area.
[Verizon Samsung Galaxy S III] Hybridnoob:
Fair enough. I see what you're saying. I'm not adding any these days, so I didn't notice. That may be an app issue, but either way, I would think that should be handled on the official thread.
[Verizon Samsung Galaxy S III] airmaxx23:
Its something with the build for our GS3, I have official cm10.1 on my N7 and search works fine. It works fine on my wife's GNex running cm10.1 as well. Hopefully they can get it figured out.
[Verizon Samsung Galaxy S III] PerCompLLC:
Just noticed. Camera lockscreen widget doesn't work on 4/29. It just freezes. It did work on 4/26 and earlier builds. Otherwise the camera works perfectly.
[Verizon Samsung Galaxy S III] airmaxx23:
If you mean swiping left to open the camera mine is working fine.
[Verizon Samsung Galaxy S III] PerCompLLC:
Really... Okay, good to know. I'll try clearing data on the camera / gallery.

Edit: Nope, didn't work. Anyone have any ideas?
[Verizon Samsung Galaxy S III] mastamoon:
Launch in portrait then when camera is fully launched rotate. If you launch in landscape or rotate to landscape before it's fully launched, it seems to force close.
[Verizon Samsung Galaxy S III] airmaxx23:
I can't get mine to force close by launching it in landscape or rotating before it's fully open.
[Verizon Samsung Galaxy S III] mastamoon:
Nice. What build you on?
[Verizon Samsung Galaxy S III] PerCompLLC:
Mine doesn't force close. It just freezes. And it doesn't matter whether I have it in portrait or landscape. And it's only from the lockscreen. As I said before, it worked fine on 4/26.
[Verizon Samsung Galaxy S III] airmaxx23:
Your 4/29 build, thanks for your work, I really appreciate it.
[Verizon Samsung Galaxy S III] mastamoon:
I don't remember mine really ever working correctly so I tend not to even bother with it.

Wonder what the variable is.
[Verizon Samsung Galaxy S III] airmaxx23:
One thing I noticed that is working now but stopped working peviously is swiping left from the camera to open the gallery. It's opened to a blank gallery from around the 4/19ish build until the 4/29 build.
[Verizon Samsung Galaxy S III] ugachris:
Didn't make any difference. Thanks for looking into it.
[Verizon Samsung Galaxy S III] PerCompLLC:
Camera update... Noticed that the Gallery2.apk in 4/29 is 5.62MB and the Gallery2.apk in 4/26 is 5.59MB. Copied the Gallery2.apk from 4/26 to the 4/29 build and everything works as it is supposed to. Not sure exactly what changed (it looks like there were several camera commits), but my phone doesn't like the change.

So if you are having the same issue with opening the camera from the lockscreen widget, the Gallery2.apk from the 4/26 build will fix it.
[Verizon Samsung Galaxy S III] prototype7:
To quote Steve, "OH GOD PLEASE WORK"
[Verizon Samsung Galaxy S III] mastamoon:
Hopefully fixed in today's build.. https://github.com/CyanogenMod/andr...mmit/3a4ab873c3cec846efabcfe47716ab59b74de5d5
[Verizon Samsung Galaxy S III] daytonahemi08:
I've been using 04/25 wit no issues just the flicker but haven't seen it do that in 2 days. Lovin it!
[Verizon Samsung Galaxy S III] gcutter:
2nd it

:good:
[Verizon Samsung Galaxy S III] forsakenredog:
Just curious, but has anyone noticed way better battery life due to awesomely low "screen on" times.

My screen bar on the battery section has fallen below the cell stand by for the first time in a long time (that i can remember).

Using 4/29 + LK 5.6

-R
[Verizon Samsung Galaxy S III] Hybridnoob:
Um, are you using your phone less? That would affect the screen on time...
[Verizon Samsung Galaxy S III] forsakenredog:
No more/less than usual. Last night i managed to make it home with 60% battery when it's usually at 40%. And right now it's at 87% when it should be closer to 70%.

Maybe it's just confirmation bias on my part.

-R
[Verizon Samsung Galaxy S III] greekstile:
wifi battery drain

Anyone else have bad battery drain while on wifi? I'm on the 4/29 build, but it's pretty much been bad since CM10.1 dropped, as far as I can remember.
[Verizon Samsung Galaxy S III] goldsmitht:
au contraire, i usually get better battery life on wifi, as it's not searching for a signal.

might make sure you don't have any partial wakelocks keeping your phone awake, or maybe an apk running loose.

:cyclops:
[Verizon Samsung Galaxy S III] airmaxx23:
The lower "screen on" time just means your screen isn't on as much which would save battery in the long run. With a stock battery I get over 24 hours on a charge with about 5 hours screen on time while connected to 3G constantly. I'm running TK747 kernel with some mods, HERE is a link to my battery stats in another thread.
[Verizon Samsung Galaxy S III] Hybridnoob:
With that, I've had good luck using an app called Greenify.
[Verizon Samsung Galaxy S III] mastamoon:
4/30 build in OP

-- back to CM10.1 kernel

-- brought back GPS revert to see how it effects my phone now that I have run for awhile without it.

-- reverted a commit that might have brought some flicker back

-- repo sync @ 3:15 PM EST
[Verizon Samsung Galaxy S III] greekstile:
Exactly, this has always been the case. Until recently, or around the time of CM10.1. There are no wakelocks keeping my phone awake. Phone deep sleeps fine. There is nothing obvious. I get twice the battery life on 4G that I get on wifi.
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm getting GPS lock in 2 seconds on yesterday's build!
[Verizon Samsung Galaxy S III] mastamoon:
Yeah mine was fine also. Wanted to see if this made it any better after seeing what my GPS was like without it for a few days.
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm not sure you can improve perfect :thumbup:
[Verizon Samsung Galaxy S III] mastamoon:
True, and doesn't look like it helped anything anyway now.
[Verizon Samsung Galaxy S III] airmaxx23:
After opening the camera by swiping left on the lockscreen you can no longer access the gallery properly by swiping left on the camera on the 4/30 build. It works fine on the 4/29 build though.

if you open the camera through the app swiping left on the camera will open the gallery just fine.
[Verizon Samsung Galaxy S III] PerCompLLC:
Actually it works perfectly for me now. I can swipe to the left on my lockscreen to open the camera. Then if of I swipe again I get a lock icon, which is what I should get because I have a pin lock set up. If I tap the lock the pin screen comes up. After I enter my pin the gallery opens as expected.

Seems to me that is the way it's supposed to work. Does yours do something different?
[Verizon Samsung Galaxy S III] Gordon Ramsay:
So I need some advice. Any aosp rom I try with this new kernel is a disaster. Frozen screens and reboots and horrible data/wifi/reception. This includes the build invisiblek posted today. It seems though that you guys are happy enough with it to start using it as your daily driver and that confuses me. I wipe multiple times including internal sd and all that using twrp 2.5 so if it's something I'm doing its unknown to me. My brother is having identical issues. Thanks for all your efforts and hoping like crazy any of you guys have any insight.
[Verizon Samsung Galaxy S III] VinBertinelli:
Dude send me a nandroid of your system or something, that is unheard of for me! I get max 2 1/2 hours screen time over 12 hours or so.
[Verizon Samsung Galaxy S III] airmaxx23:
I can't access the gallery that way but I don't have a pin set up either. It works fine using the camera app. This is what I get from the lockscreen:

Edit: I just tried the 4/29 build again then went back to the 4/30 build and now I can't get it to work through opening the camera app directly.

Edit 2: It just started working in the app and on the lock screen and I haven't changed anything.

Have you tried a different kernel?

If you want I can tell you how mine is set up, it's pretty simple.
[Verizon Samsung Galaxy S III] Gordon Ramsay:
Yes I have also tried the KT 3.4 kernel and that made it worse.
[Verizon Samsung Galaxy S III] mastamoon:
You must have a rogue app or are restoring data on something you shouldn't.
[Verizon Samsung Galaxy S III] Gordon Ramsay:
So although your comment was seemingly short I think it might have just ended my 5 days of misery. It turns out that selecting the options to restore my phone from Google and back up to Google were seemingly the culprit. I never had many apps to begin with but apparently something it was doing was causing these freezes and reboots.

I installed the latest nightly and tried everything I could to make it fail...Spotify, live wall, flip board, GPS, Bluetooth all at once and it performed flawlessly and locked to 8 meters.

I feel silly that this never occurred to me but you bringing it up brought me back in the game so thank you ;)

I wonder if this is causing anyone else reboot issues?
[Verizon Samsung Galaxy S III] travisX:
I'm interested in trying this.... Masta, can you think of any reason one would need/want these enabled? I hadn't even thought about it but I guess I had it set up do to this automatically. Any problems that could come from disabling?
[Verizon Samsung Galaxy S III] mastamoon:
I leave automatic install off, but keep backup on. I use titanium backup to restore apps if/when I data wipe. Market it to slow.
[Verizon Samsung Galaxy S III] mastamoon:
5/01 build in OP

-- removed GPS revert, noticed no difference

-- added InvisibleK's Screen Color Temp Changing Mod. Settings in System Settings>Advanced. May or May not be working right now though.

-- repo sync @ 1:15PM EST
[Verizon Samsung Galaxy S III] PerCompLLC:
Nice! After you posted I actually removed my pin and set the lockscreen to slide just to see if I could recreate your issue. But it worked fine even without the pin. Glad you got it working (even though you didn't do anything)!
[Verizon Samsung Galaxy S III] mastamoon:
sorry yall.. new build incoming... old build runs fine but I think I fixed the non working color temp picker stuff.

Ill fix the link when its uploaded. Sorry if you already downloaded and flashed.. only need to reflash this if you want the color picker. Everything else should be the same.
[Verizon Samsung Galaxy S III] mastamoon:
OK.. Updated the OP with the new build.

The screen color temp chooser works.. everything else is buttah.
[Verizon Samsung Galaxy S III] eppo12-:
Mastamoon, i have to commend you on an awesome build, keep up the great work, and thank you for all of the time you dedicate to developing for the SGS3.

for some reason I get MANY random reboots when using your rom with the stock kernel, it seems that you don't have any issues, i'm not sure why i am. Since the update to kernel 3.4, i've been sticking with the 3/13 rom, which works great for me. I tried yesterdays, and got probably 5 random reboots within 10 minutes. installed the latest LeanKernel and all is well. (figured i would post this to see if anyone had any input)

(i might want to give a clean install a shot, those activation issues are gone, correct?)

keep doing what your doing Mastamoon, your making a lot of people happy, Great Job!
[Verizon Samsung Galaxy S III] mastamoon:
The fix for this is in the works. Cyanogen himself along with countless others have been chasing this demon for weeks. All I can say for now is use what works for you. If another kernel works for you, use that until CM is fixed up.

I have had 0 reboot issues, but many many are including an awesome bunch of devs so it will be squashed. Most likely sooner than later :victory:

And yes, I believe the activation issues are gone, but wiping data doesnt seem to help if your are stuck in this nasty reboot plague.
[Verizon Samsung Galaxy S III] cesium:
Been on your 4/16 build which has been FANTASTIC! 0 issues and over 10 days uptime. Have there been many substantive changes since, other than wifi driver (and color temp obv)?
[Verizon Samsung Galaxy S III] mastamoon:
I personally think that the builds are getting better by the day. As long as you don't have the reboot issue, I would stay with the latest. Phone has never felt faster and battery life is golden.
[Verizon Samsung Galaxy S III] cesium:
Makes sense. I've been lucky enough to not have any reboot, GPS, etc. issues *knock on wood*. Will have to give this a try tonight! :good:
[Verizon Samsung Galaxy S III] airmaxx23:
Should the color temperature settings be really noticeable? I'm not seeing a difference at all.
[Verizon Samsung Galaxy S III] mastamoon:
Are you using the 2nd build I posted? First one didn't work. Also you have to turn the screen off then back on again for the settings to work. It should be as noticeable as using the BMS kernel with the morific color tweak.
[Verizon Samsung Galaxy S III] airmaxx23:
It's the second build you posted and I've turned the screen off then back on. I'm just not seeing a difference going from cold to hot or anything in between. Would it be because I'm using a different kernel?
[Verizon Samsung Galaxy S III] mastamoon:
Yeah I would bet that would do it. :p
[Verizon Samsung Galaxy S III] airmaxx23:
I just flashed it again without a different kernel and I can see the difference now.
[Verizon Samsung Galaxy S III] rutger1413:
Just a heads up, I have severe screen flicker when using Facebook chat heads(from messenger, not Facebook home). Great build though. Everything is smooth as butter.
[Verizon Samsung Galaxy S III] mastamoon:
Word I was chatting with a few heads tonight and saw no flicker at all.

Stock kernel?
[Verizon Samsung Galaxy S III] iofthestorm:
I use Plume every day and it only started flickering today, seems like it's not really consistently happening with any particular app. Thought it was gone for a while.
[Verizon Samsung Galaxy S III] rutger1413:
Stock kernel, dirty flash from a much older build 3/12.
[Verizon Samsung Galaxy S III] mastamoon:
I have 0 flicker now.. hmm.

Maybe try wiping /system then reflash rom and gapps? Clean install might be in order.
[Verizon Samsung Galaxy S III] PerCompLLC:
No flicker here either...
[Verizon Samsung Galaxy S III] fromthesticks:
I've only seen the flicker once. Started my camera up to take pictures and couldn't see anything.

Still ended up taking a couple shots, turned off screen and flicker went away and the pictures I took were fine
[Verizon Samsung Galaxy S III] rutger1413:
Wiped system and reinstalled the rom and gapps. Everything is perfect now. Thanks!
[Verizon Samsung Galaxy S III] mastamoon:
:victory:
[Verizon Samsung Galaxy S III] mastamoon:
5/02 build in the OP

-- repo sync @ 11:15 AM EST

if anything good gets merged/fixed I may do another build.
[Verizon Samsung Galaxy S III] ugachris:
Is anyone noticing a delay for screen-on? It seems like there is a longer delay (that I hadn't noticed before) between when I hit the power button and when the screen turns on.
[Verizon Samsung Galaxy S III] mastamoon:
My lock and unlock are both laggy.
[Verizon Samsung Galaxy S III] goldsmitht:
try going into developer options and lowering your animation scales; i turn mine off, so i don't see any lag at all

might help, ymmv

:cyclops:
[Verizon Samsung Galaxy S III] ddggttff3:
I am on the 5/1 2nd build, and have no issues at all. Smoothest ROM yet for CM 10.1
[Verizon Samsung Galaxy S III] ugachris:
Thanks for the suggestion, but this doesn't seem to help.
[Verizon Samsung Galaxy S III] airmaxx23:
The 5/1 build has been working great so far. I usually use a different kernel but decided to give the stock one a try today. So far I have 58% battery left with 2h10m screen on time after 9h52m total use with the stock battery under-clocked to 1.35GHz. I've been connected to 3G the whole time.
[Verizon Samsung Galaxy S III] ddggttff3:
just noticed a bug in the 5/1 build. When you send a MMS with text and a photo, the stock messaging app will crash, but the message will still send.
[Verizon Samsung Galaxy S III] airmaxx23:
Mine's working fine.
[Verizon Samsung Galaxy S III] mastamoon:
Fixed in today's build I believe.
[Verizon Samsung Galaxy S III] billquinn1:
OK , I feel like an idiot but... I can't find some of the normal stuff. Any kind of cyanogen ROM control. Developer options? Where is any of that stuff? Any help would be appreciated.
[Verizon Samsung Galaxy S III] Hybridnoob:
About phone - Tap build number 7 times. That will unlock dev options. While you're at it, check advanced reboot if you want to have the option to reboot into recovery using the power button.
[Verizon Samsung Galaxy S III] PVLMTREE:
After doing a full wipe/clean install on 5.01.13 build, my battery life has been really good and impressive. I've been using my phone less than normal but I can surely tell that, for sure, battery life has improved.
[Verizon Samsung Galaxy S III] stearic:
I had almost 4 hours screen time today on the 4/20 build (i know, slacking on updating). 3h45min with 13% battery left. I'm pretty happy with this rom.
[Verizon Samsung Galaxy S III] dpaine88:
I do
[Verizon Samsung Galaxy S III] mastamoon:
5/03 build in OP

-- switched to commits in gerrit for the screen color temp modder (no functional change)

-- couple kernel tweaks invisiblek wanted tested

-- removed the power.c/hispeed_freq mod

-- repo sync 10:15AM EST
[Verizon Samsung Galaxy S III] ddggttff3:
Thanks, running great, but still has the MMS force close. Just waiting for CM to patch that. Thanks again for these daily builds!
[Verizon Samsung Galaxy S III] mastamoon:
Yeah I saw a few commits/comments talking about the issue, so hopefully it will get fixed soon.
[Verizon Samsung Galaxy S III] goldsmitht:
what "FC'ing"? haven't had any problems so far

:cyclops:
[Verizon Samsung Galaxy S III] airmaxx23:
I guess it's sending a picture with text in the message. I've tried it a few times and didn't have any FC'ing issues.
[Verizon Samsung Galaxy S III] razorloves:
MMS fc if you send a pic attached with any text you typed

Ninjad. Lol. Yeah, what airmax said
[Verizon Samsung Galaxy S III] xHoLyx:
Masta, is flickering a kernel issue or rom?
[Verizon Samsung Galaxy S III] masri1987:
Will there be another build coming today or should I flash this morning build?
[Verizon Samsung Galaxy S III] airmaxx23:
Does it force close for you? I've sent several text messages with pics attached and haven't had a problem.
[Verizon Samsung Galaxy S III] razorloves:
Yep. Every time I've tried. Are you using any MMS mod or theme, or is it just the plain stock MMS apk?
[Verizon Samsung Galaxy S III] mastamoon:
Nothing new has merged that's important to us since this rom was built, so flash away!
[Verizon Samsung Galaxy S III] airmaxx23:
I'm using the Cobalt Inferno system theme with no mods. I'm going to reapply the stock theme then reboot and see if MMS crashes.

Edit: It works fine with the stock theme as well, I do have a different kernel installed but I don't think that would make a difference.
[Verizon Samsung Galaxy S III] mastamoon:
I haven't seen any flickering personally. There is a glitch here n there, but no flicker.
[Verizon Samsung Galaxy S III] masri1987:
K will do! Also is there anyway we can make 4 tiles per row in quicksettings?
[Verizon Samsung Galaxy S III] ddggttff3:
looks like a patch may be out for the MMS crashing. Fingers Crossed it gets out of review!

http://review.cyanogenmod.org/#/c/36820/
[Verizon Samsung Galaxy S III] mastamoon:
Try this.. http://truelinux.net/sch-i535/mastamoon/other/Mms.apk

I cherry picked that commit and built Mms.apk

Let me know if it works.

Thanks
[Verizon Samsung Galaxy S III] ddggttff3:
Replaced the MMS apk, rebooted, and tested. It fixes the FC's! :)

Push it!
[Verizon Samsung Galaxy S III] mastamoon:
Awesome! Ill add it to the cherrypick list for monday, but Id hope it would get merged before that.

Thanks for testing!
[Verizon Samsung Galaxy S III] ddggttff3:
anything to help make this rom rock solid! Thanks for making the apk
[Verizon Samsung Galaxy S III] V3TTOO:
So, the MMS thing, does it only affect the stock MMS, or all 3rd party apps too? I think I sent a pic today with Handcent and had no issues. Going to try it again.

Also, I think I figured out what was causing people to not be able to use the camera on the lock screen when on landscape mode. I installed a Photosphere APK and that caused me to have the camera issue on lock screen. http://xdaforums.com/showthread.php?t=1966426
[Verizon Samsung Galaxy S III] PerCompLLC:
Thanks but it has already been fixed with a commit that was merged yesterday.
[Verizon Samsung Galaxy S III] stkiswr:
I have it nailed down pretty well now and it takes less than a few mins to build it and sign it. I can't really update the MMS on every single nightly but if you have a request I can patch it up. I wish it could just vet submitted and merged because it has sent a received perfect on vzw.

Now if the limit is too large for other networks I couldn't verify that but I could adjust it down because I set the limit to Verizon.

Full 1.2mb max. I also adjust the size in height and width. Adjust so you can send ogg files with no issues.

Since I really don't know anyone not on Verizon where I live I would obviously need testers but if you flash every nightly then I would need to repack each one. If you have a nightly you love then you would be my perfect tester. I also could not guarantee that an MMS from another nightly could just continue on working?
[Verizon Samsung Galaxy S III] stkiswr:
I picked and chose from here https://android.googlesource.com/de...rlay/packages/apps/Mms/res/xml/mms_config.xmlif you have apk tool and signapk setup its super easy

Like I said. I went from receiving MMS at >50k on each pic and set crappy to other devices and of course myself.

After these line edits you will be sending large MMS and receiving large. I think a few sent at 1200k and received at over 700k.
[Verizon Samsung Galaxy S III] airmaxx23:
MMS was not crashing for me when attaching a pic to a text message but it is crashing on the 5/3 build now. It actually only crashed once and hasn't done it since.
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm on 5/3. On the MMS topic, anyone else unable to open previous MMS (group) messages? Messages stops each time I try.
[Verizon Samsung Galaxy S III] Stealth111:
For the last week or so I have been stuck with a FC with one particular sender. He said he attached a vcard to the text. Now I am stuck, as soon as I click on his name in messages, I get a FC. I don't want to really delete the thread from him either. I know I can get sms backup, but I want all the pics as well. Haven't looked into many apps yet, hoping issue just gets resolved eventually.

Sent using Tapatalk
[Verizon Samsung Galaxy S III] stkiswr:
Use helium backup(used to be called carbon)

Its extremely easy and always fully restores all my SMS and my user defined words
[Verizon Samsung Galaxy S III] wrippel82:
are the random reboots ironed out yet?
[Verizon Samsung Galaxy S III] xHoLyx:
I may be the lucky guy, but I've been dirty flashing all April - May builds and yet to have a random reboot.

If you are having one, you should do a clean install.
[Verizon Samsung Galaxy S III] Reborn627:
I haven't had a reboot in weeks, maybe a month. But I've also not experienced most of the issues others have. Add me to the lucky one club.

Ray
[Verizon Samsung Galaxy S III] mastamoon:
If we can be sure the settings work all the time I can roll them into my builds. The only way the settings would ever get merged is if we are sure it doesn't break sending or receiving to any other phone/carrier.

I can also easily make 1 off MMS.apk for testing various settings. Takes all of 1 minute or less on my build machine.
[Verizon Samsung Galaxy S III] ddggttff3:
hay mastamoon, just wondering if there is a chance for a build today. changelog on CM looks like its full of goodies :) thanks