yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] goldsmitht:
Try one more step. Once you get it to dirty flash with no problems, make another backup of that settings, and see if that works. And delete any old nandroids you have on that version. May force the correct settings to hold.

I've done it before, and they've always kept everything and I boot a couple times a day for one reason or another

:screwy:
[Verizon Samsung Galaxy S III] SilentAce07:
You are saying to make a nandroid once everything works and somehow that would force the settings to stay when I reboot a few times?

This is honestly the most frustrating issue I've ever had and with KLP only coming to custom roms apparently on the US S3, I'm worried that this wont ever be fixed.

I'm driving myself mad with this.

---------- Post added at 06:43 PM ---------- Previous post was at 06:18 PM ----------

From the official CM thread:

Glad to know it's not just me and it's truly not fixed by this method. Again. Angry and I refuse to waste my time on this any longer. Somebody PM me when it's fixed, otherwise I'm done trying to fix this.
[Verizon Samsung Galaxy S III] mastamoon:
Since my 4/1 build invisiblek. Haven't seen any issues and tethering works fine.
[Verizon Samsung Galaxy S III] goldsmitht:
Its an issue, but a lot have had success following what was suggested. You see about 5-6 people who are having issues, out of probably hundreds who don't. Like life, all answers don't work for everyone.

And go ahead, I'm SURE someone is going to pm you when its fixed.

Its a free ROM, that for most, is very stable and has no issues. If its not for you, be respectful of the hard work these devs put in, for FREE, and move on to another ROM.

:screwy:
[Verizon Samsung Galaxy S III] mastamoon:
Try not wiping caches.
[Verizon Samsung Galaxy S III] odub303:
You've been flashing nightly builds. If you can't deal with issues then stick to the stable releases or stock roms. Otherwise, please be a little more respectful.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] NegativeOne:
Well, at first I couldn't get to recovery :P. It's probably my own fault for not reading carefully enough. Oh well, will try again later.

Is there gonna be a 3/7 build, or should I just do the 3/5 build ?
[Verizon Samsung Galaxy S III] tv31284:
I seem to be getting the disappearing app issue on chrome on the latest build. Anyone else seeing this?
[Verizon Samsung Galaxy S III] mastamoon:
Next build from me will be tomorrow.

Haven't seen it myself since cyanogen pushed the fix. Maybe reflash and wipe caches? Strange.
[Verizon Samsung Galaxy S III] tv31284:
Just tried it and it didn't help. The weird thing is that I've never installed a build with the problem. I mean the build I came from was from before the offending code was committed and I only updated to the newest build yesterday.
[Verizon Samsung Galaxy S III] SilentAce07:
I apologize if I came off as being disrespectful. I'm not upset with the devs, and I thought I made that clear. I'm frustrated with the issue and said that I couldn't let myself waste any more time trying fixes because I've done everything that I can throughout the past month or so to no avail. I'm well aware and grateful for the work the devs do. Hopefully someone figures it out eventually. I don't have the ability to keep up with this thread all the time, so I may miss when/if a fix is implemented.

That is all.

@mastamoon, I tried both with and without wiping caches and had no success. I'm hoping that when a new build goes up that an OTA update will somehow resolve the issue as people have reported at times. No idea how or why that would be so. I even thought about switching back and forth between TWRP and CWMT and checking if that'd make a difference.

Thanks for the suggestion though. Seriously, the reason I'm so frustrated is that these roms are incredible pieces of work and would be next to perfect if the activation bug didn't appear. Thanks a ton.
[Verizon Samsung Galaxy S III] Ty07allstar:
Thanks for the response Invisiblek. If you know of anybody that has any ideas about a fix, let me know and I can test them for you. Any chance that I could use the 3.0 kernel on the latest builds?
[Verizon Samsung Galaxy S III] odub303:
No, the kernel won't boot the recent builds.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] cbrehob:
Ok, so maybe I got lucky but.

The 31 March nightly is by far the most stable ROM for me ever. I am scared to move on, I actually tried the 4 April one and things started going ****ty fast.

If anyone needs a stable one to fall back on, try 31 Mar.
[Verizon Samsung Galaxy S III] sandhuxda:
Random reboots on 04/07 nightly. Crash log is attached (too long to paste).
[Verizon Samsung Galaxy S III] sandhuxda:
Another reboot/crash. Crash log attached.
[Verizon Samsung Galaxy S III] goldsmitht:
Try using lean kernel 5.2; I'm on mastamoon's latest and lk 5.2exp1 and having no issues

:D

Sent from my SCH-

I535 using Tapatalk 2
[Verizon Samsung Galaxy S III] Restola:
Just FYI that build had the fc/disappearing app issue.

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] mastamoon:
Weird I'm at 70 hours up time, not a single issue.
[Verizon Samsung Galaxy S III] goldsmitht:
I had one SOD, but think it was cuz my lower was set at 196; reset to 384 and alls working great, no problems.
[Verizon Samsung Galaxy S III] NegativeOne:
I'm now on Masta 4/5 and invisiblek kernel 4/6. So far okay, but one thing i've noticed is that LMT's "ISAS" feature stopped working. Would this have anything to do with the kernel?

ISA = invisible swipe area. gives you swipe gestures from the corners of the screen. It worked yesterday, on 3/14 unofficial w/ stock cm10.1 - linux 3.0 kernel
[Verizon Samsung Galaxy S III] dpaine88:
Just had a random reboot myself on 4/5 build with Gideon's BMS latest kernel. New to CM10.1 though so not sure if that would be ROM or kernel related
[Verizon Samsung Galaxy S III] eppo12-:
Based on some of the responses on this thread in going to try leankernel along with 4/5. A while back I started reading up on governors and could configuration and it was too much. Does anyone know of a place that has settings that just work on our phone? Or maybe a down and dirty explanation of the settings in reverence to the sgs3?
[Verizon Samsung Galaxy S III] Reborn627:
Either I'm not paying attention or I'm not having any troubles since last weeks nightmare. I've been running mastamoon's builds since rooting my GS3 a month or so ago. The last couple of weeks I've been using GideonX's 3.4.y kernel. Other than the few problems with a couple of the builds last week my phone has been running brilliantly and getting better with each update. Over the weekend I actually got 36+ hours out of my battery. Granted, much of that time was connected to wifi but it beats my previous up-times by about 50%. I do "dirty" flash each update, whether it be the ROM or the kernel, but I would think a "dirty" flash would be more of a potential problem. I have to wonder if many of the problems that others are experiencing have to do with other modifications that have been done above and beyond the ROM or kernel updates. Just my $.02 and with inflation that doesn't count for a lot. Oh, and I'm running the VRBMB1 modem with the corresponding RPM file. Not sure if that makes a difference.

Peace,

Ray

---------- Post added at 09:53 AM ---------- Previous post was at 09:47 AM ----------

On a side note, I disabled all of google maps location reporting and history and went back to the stock mms rather than handcent. This may account for a bit of the increased battery life along with the kernel tweaks that have been coming down.

Ray
[Verizon Samsung Galaxy S III] mastamoon:
new 4/8 build in OP

-- no significant changes

-- repo sync at 1pm EST

*** somebody do a camcorder recording volume test. I was messing with the config file, but personally cant tell if anything changed. Sounds the same to me so probably didn't change anything lol ***
[Verizon Samsung Galaxy S III] goldsmitht:
Using this build?
[Verizon Samsung Galaxy S III] mastamoon:
Me? Yeah. Or do you mean test using this build.. ? Yes. :P
[Verizon Samsung Galaxy S III] iofthestorm:
Is anyone experiencing the weird scroll up/down thing in apps like browsers and twitter apps, and maybe the Kindle app too? Some people in the official thread reported it and someone mentioned that there might be a patch for it in one of your builds. I have a small suspicion that it's not actually a fake touch event causing the app to scroll up and down but rather somehow an old frame is being drawn rather than the current frame. Otherwise it doesn't make sense that it affects some apps arbitrarily but always reverts itself.

Edit: referring to this http://xdaforums.com/showthread.php?p=40011903
[Verizon Samsung Galaxy S III] V3TTOO:
See, I knew it would help to put some info on what you did to each build, in case we needed that info. :p

So, any major developments since Thursday's build? I am reading the info right now.
[Verizon Samsung Galaxy S III] anacree:
Yes, every time I have a forced reboot (screen freezes, either on or blank, and I have to volume down+home+power to get it to reboot) google play updates apps when the ROM comes back up. May be coincidence, but it happens every time.
[Verizon Samsung Galaxy S III] V3TTOO:
I found out you only need to use VolDown + Power and it will reboot. No need to use home button.
[Verizon Samsung Galaxy S III] masri1987:
Running mastas build from Friday, started getting random fc today, during bt streaming of music, also bt streaming was choppy and inconsistent. Using latest kt kernel
[Verizon Samsung Galaxy S III] goldsmitht:
Try switching kernels, LK 5.3 working great for me

---------- Post added at 07:05 PM ---------- Previous post was at 07:04 PM ----------

Have had the same thing; old frame pops up on twitter, Facebook or crone, and then goes right back. Annoying, but not deal breaker
[Verizon Samsung Galaxy S III] WhammyDroid:
Yes, I am having the same issue.
[Verizon Samsung Galaxy S III] V3TTOO:
Ok, where do I find this? I look online and I only find Galaxy Nexus version. I can't seem to find one for our phone.
[Verizon Samsung Galaxy S III] kinnerful:
http://imoseyon.host4droid.com/s3/aosp/
[Verizon Samsung Galaxy S III] kyuubi08:
ive been having issues with the dialer force closeing. ive tried to fix permissions, wiped the dalvik, and the cache, and it still force closes. is there an easy fix for this or is it a known issue?
[Verizon Samsung Galaxy S III] soapinmouth:
Should we not use other kennels with this build?

Sent from my liquid smooth gs3
[Verizon Samsung Galaxy S III] PerCompLLC:
Easy fix. Manage Apps > all programs and clear data on the phone app.

---------- Post added at 05:09 PM ---------- Previous post was at 05:06 PM ----------

This build is basically a kang of CM10.1 (with cherry picks and reverts courtesy of Mastamoon). Any AOSP 4.2 kernel should work. And if the kernel fails to boot, simply boot into recovery and reflash the ROM.
[Verizon Samsung Galaxy S III] kyuubi08:
Tried that
[Verizon Samsung Galaxy S III] PerCompLLC:
Then I dunno... It worked for me when I had that issue.
[Verizon Samsung Galaxy S III] kyuubi08:
Think of I went back to stock out would fix the issue
[Verizon Samsung Galaxy S III] jguns112:
I had this issue when I flashed an official build not too long ago. I had to wipe cache/dalvik and fix permissions all at one time in recovery. However, this would only fix it until I rebooted.

I went back to a TW ROM for awhile and then flashed Mastamoons build and the problem went away. So, maybe try flashing something else and coming back later if absolutely nothing else works..
[Verizon Samsung Galaxy S III] dpaine88:
Getting a lot of Chronus FC even after a reboot
[Verizon Samsung Galaxy S III] mastamoon:
Clear data on it?
[Verizon Samsung Galaxy S III] dpaine88:
Not yet, ran into some SD issues since I was coming from TW , despite being on latest recovery.

I have noticed my 4g going down to 3g for a few minutes and sometimes back to 4g, sometimes not.

On TW before I flashed it in this exact spot, it was holding 4g pretty well.
[Verizon Samsung Galaxy S III] mpetruzz:
OK I looked at the change log and tried to comprehend it, which was unsuccessful. My question is, if 1-16 is running awesome for me are there enough changes to flash 1-17?

sent from my blue police box flying through time!!!
[Verizon Samsung Galaxy S III] mastamoon:
No. If your not the experimental type stay with what works for ya.
[Verizon Samsung Galaxy S III] mpetruzz:
Thanks for the quick answer. I have to say again, I've flashed every 4.2 ROM and this is the only one where everything works. Friggin GPS locked in like 2 seconds!! Signal has been strong and absolutely no FCs!!!

sent from my blue police box flying through time!!!
[Verizon Samsung Galaxy S III] jguns112:
The only issue I've ran into on yesterday's build is the camera crashed and gave me a can't connect error. This has only happened once though and a reboot fixed it. However, a couple of times it crashed and made the phone run extremely laggy for awhile.
[Verizon Samsung Galaxy S III] dpaine88:
Cleared data and still getting FC on Chronus when in its settings and randomly
[Verizon Samsung Galaxy S III] mastamoon:
I just played around in settings and had no problem. Try deleting and re adding the widget to where ever you have it.
[Verizon Samsung Galaxy S III] kyuubi08:
Question. Have you tried compiling this with linaro yet
[Verizon Samsung Galaxy S III] sparkerjc:
Searched the thread for "GPS" and found a lot of stuff... but what I am wondering is why Google Maps fiinds me exactly within 2 seconds but when I hit navigation I get "Searching for GPS" for about 15-30 second before it goes and then my locations starts jumping around like crazy? Just me?

And sorry I had like 20 tabs open, I meant to ask this in the Q & A Thread. Don't hate me. :)
[Verizon Samsung Galaxy S III] PVLMTREE:
Happens to me too. Haha.
[Verizon Samsung Galaxy S III] PerCompLLC:
FYI... Handoff issues have completely disappeared for me with mastamoon's unofficial builds... Not sure if the official builds are fixed yet, but I was having significant problems prior to the 1/16 unofficial. Just sayin...
[Verizon Samsung Galaxy S III] Hybridnoob:
http://rootzwiki.com/topic/32286-ke...leankernel-minimalistic-kernel/page__st__1720
[Verizon Samsung Galaxy S III] eppo12-:
Anyone having issues with apps going into landscape. So far I've seen it with maps and YouTube. When I turn my phone the view flips upside down. I'm on 4/5 with the latest LK.

I guess it's all of them Tapatalk does it to.
[Verizon Samsung Galaxy S III] sivarticus85:
No changes here with volume. What are you modifying to do this? I'd like to take stab at it myself.
[Verizon Samsung Galaxy S III] toddley:
This has to be the case as sometimes dolphin shows the last page you've visited. The bug isn't always just scrolling up
[Verizon Samsung Galaxy S III] invisiblek:
This stuff should be fixed in tomorrow's build.

The adreno blobs have been reverted

Apparently these blobs are broken on mako too, cyanogen is working on it...
[Verizon Samsung Galaxy S III] V3TTOO:
Thank you both for the info.
[Verizon Samsung Galaxy S III] NegativeOne:
Invisiblek - I'm seeing a problem I recall seeing when I tried one of the first 3.4 kernel builds... It seems like my phone is not alerting me of push notifications properly anymore.

I'll unlock my phone and only then receive notifications of Talk messages sent to me while the phone was off.

Edit: also seeing random rebooting
[Verizon Samsung Galaxy S III] odub303:
Log?

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] slambert27:
+1 on this. I'm glad this issue is starting to gain some visibility but also understand why it has been tabled for now. Hoping to take a look at this myself too.

---------- Post added at 03:20 PM ---------- Previous post was at 03:04 PM ----------

+1 on this. I'm glad this issue is starting to gain some visibility but also understand why it has been tabled for now. Hoping to take a look at this myself too.

Sorry for the double post. Keep forgetting to quote.
[Verizon Samsung Galaxy S III] NegativeOne:
What log can I give you of a phone rebooting? I'm not sure how.

As for the other thing, it's sporadic - mail think it happens when the phone has gone to sleep
[Verizon Samsung Galaxy S III] mastamoon:
its a file called snd_soc_msm_2x

Thanks for testing, I didn't think it did anything either.
[Verizon Samsung Galaxy S III] goldsmitht:
might check your off screen clock speed, or your minimum CPU Freq. had that once at 196, but once i raised to 384 (or used base on LK 5.3) haven't had it happen again

:cyclops:
[Verizon Samsung Galaxy S III] NegativeOne:
My min freq is already 384. I'm getting reboots on the 4/8 build with stock kernel. Still not sure how I can provide a meaningful log - anybody?
[Verizon Samsung Galaxy S III] RED ZMAN:
Well, I finally had to reboot my phone. 20.5 days without a reboot. Was having some problems with Bluetooth, tethering, and Dolphin Browser. I cant ask for too much more than that.

So, now that I finally rebooted, what's the latest version I should be installing noting that I need tethering via WiFi?

I read that there are some problems with the new 3.4 kernel I think?

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] mastamoon:
4/9 build in OP

-- added 2 general clean up commits by invisiblek

-- removed my camcorder test hackery edits

-- repo sync @ 2pm EST

cyanogen rolled us back to our old display drivers, so hopefully all the graphical glitches and maybe random reboots will stop. Runs smoothly.
[Verizon Samsung Galaxy S III] goldsmitht:
go for the latest build; i'm having great luck with LK 5.3 (http://rootzwiki.com/topic/32286-kernel-aosp-jb-v53-4713-leankernel-minimalistic-kernel/) so would go with that.

otherwise everything is running SMOOOOOOOOTH!!!!!

:cyclops:
[Verizon Samsung Galaxy S III] sivarticus85:
Thanks bro. I've been all over the interwebs trying to find out how to do this. Hopefully we can get this baby going. :thumbup:
[Verizon Samsung Galaxy S III] mastamoon:
It might not be the end all file, but anytime somebody has modified volumes or sensitivity it has revolved around this file so have at it. Let me know if you figure it out. :)
[Verizon Samsung Galaxy S III] goldsmitht:
Looks good so far, don't have the jumping around on display on latest. And everything else is working great

:D
[Verizon Samsung Galaxy S III] mastamoon:
would it normally happen right after a flash or did it take a bit to manifest itself?
[Verizon Samsung Galaxy S III] npro1464:
Thinking of retrying this rom again tonight. What's the most stable build? Thanks!!
[Verizon Samsung Galaxy S III] odub303:
The one in the op

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] iofthestorm:
Huh it's happening to me on the latest official nightly which should have the revert. I'll try formatting mastamoon's build and see if that helps. Pretty odd though, it's actually happening to me more frequently now.
[Verizon Samsung Galaxy S III] npro1464:
The 3/13 or the 4/9?
[Verizon Samsung Galaxy S III] V3TTOO:
I would try 4/9. as it is stable. 3/13 might be more stable for some tasks, but try them and see what you like.

---------- Post added at 01:51 PM ---------- Previous post was at 01:51 PM ----------

Do I need to install LK each time I flash a new ROM?
[Verizon Samsung Galaxy S III] Hybridnoob:
Yes, you have to reinstall custom kernels each time.
[Verizon Samsung Galaxy S III] Reborn627:
Only if you don't want to use the kernel that comes with the ROM.
[Verizon Samsung Galaxy S III] s'pht:
Installed 4/9 mort audio books doesn't have audio, oddly everything else does. Yesterday's build worked

Tried lean kernel 5.3, no joy.

EDIT: I flashed back to 4/8 and everything is working fine again
[Verizon Samsung Galaxy S III] V3TTOO:
Thanks for the info.
[Verizon Samsung Galaxy S III] goldsmitht:
Honestly don't remember when, just that it did. And now it didn't. Well, hasn't so far

:D:thumbup:
[Verizon Samsung Galaxy S III] cesium:
Dumb question. Is it possible to flash ktoonsez' 3.0 kernel over this? Or must I flash the 3.4 one?
[Verizon Samsung Galaxy S III] jlokos:
Nope, it must be a 3.4 kernel. I use LK's latest, and it always works well.
[Verizon Samsung Galaxy S III] Hybridnoob:
You can flash it... It just won't boot! Yes, you must use 3.4 if the ROM uses it. :)
[Verizon Samsung Galaxy S III] iofthestorm:
Gah I was on 4/9 official and still had the problem, so I formatted system and flashed your latest build and I'm still getting random jumping around in apps. It started happening in Gmail now too :( this is so weird.

Edit: checked and I do have the reverted libs o_O
[Verizon Samsung Galaxy S III] sivarticus85:
That's fine. At least it's a place to start.
[Verizon Samsung Galaxy S III] rampantandroid:
Any comment on the current 3.4 LK vs KT? On yesterday's unofficial from Masta with KT I've already seen a hot boot (where you see the CM boot logo without fully rebooting)

Thanks!
[Verizon Samsung Galaxy S III] NegativeOne:
No reboots on 4/9 but I'm still not getting notifications from Talk or email when the phone is sleeping. It's sporadic though so I can't get a log.

My min frequently is 382 so it shouldn't be that the I think. Anyone else getting this?
[Verizon Samsung Galaxy S III] goldsmitht:
haven't used the latest KT, as i have been getting better battery life with LK than i did with KT. But both are good, and as always, ymmv.

:cyclops:

---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------

ok, started to get a few of the screen glitches, where it will jump a little, but still not like before, and mostly only on chrome. still not horrible, and and definitely NOT a deal buster. Yours is still my daily driver.

:good::good::good:

:cyclops:
[Verizon Samsung Galaxy S III] ugachris:
I noticed the screen jumping around, just a little bit, in Falcon Pro.

I also noticed that Bluetooth didn't seem to want to hold a connection. I was listening to audio in my car and after about a minute it would disconnect. This was fixed before I flashed yesterday's build, so I'm wondering what caused it.
[Verizon Samsung Galaxy S III] RED ZMAN:
Is Wi-Fi Tethering wiring working in this kernel?

Going to DL it in a few.

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] mastamoon:
Yeah, tethering is fine.
[Verizon Samsung Galaxy S III] goldsmitht:
i'm not certain if it is or isn't with the LK kernel; I don't use it. Guess it is working with the ROM tho

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

-- repo sync @ 3PM EST
[Verizon Samsung Galaxy S III] goldsmitht:
Looked at change log, did you add anything new? Also, what effect would that ril update do for us, isn't it just Sony? Or did I read it wrong?
[Verizon Samsung Galaxy S III] mastamoon:
Nothing new on my end. And no, that RIL stuff had nothing to do with us.
[Verizon Samsung Galaxy S III] rampantandroid:
So, since moving to the 3.4 kernel versions of this rom, my battery life has absolutely tanked. I'm using roughly 10% of battery per hour when the phone just idles. BetterBatteryStats is showing that AudioOut_2 is holding a constant partial wakelock, when I have zero apps open.

Beyond that, RILJ seems to be using up a lot of time too. Picking up my phone after an hour of idling and it feels warm as if I've been playing games on it for a while.

Has anyone else had battery issues, or seen that partial wakelock?

Edit: did a full format and installed ONE app: betterbatterystats

With zero apps installed beyond what is in the rom (I don't even have gapps) I'm chewing through 20% per hour right now.
[Verizon Samsung Galaxy S III] goldsmitht:
If you're on stock kernel, try switching to latest leankernel
[Verizon Samsung Galaxy S III] ausman89:
Are you running the experimental or the stable version?
[Verizon Samsung Galaxy S III] LLStarks:
https://github.com/cyanogenmod/andr...mmit/810c8e0d786317f0f75219d1702df2ebb3d344db

Most recent battery issue is solved in the 4/10 builds