yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] ugachris:
It's been happening since 8pm last night, so I'm not sure how long to wait before declaring it an issue. I just wiped cache and dalvik and fixed permissions, and same thing happened in Falcon Pro afterwards.
[Verizon Samsung Galaxy S III] mastamoon:
I'm having the same issues in Falcon Pro. I wiped its app data and it cleared it up for a bit, but looks like it came back. :(
[Verizon Samsung Galaxy S III] goldsmitht:
+1, same again

first issue, and after i said it was issue free... LOL! otherwise, all is sweet!

by the way, what kernel are you using if you are having issues? just want to cover all bases

:confused:
[Verizon Samsung Galaxy S III] ugachris:
Stock kernel from the Masta build..
[Verizon Samsung Galaxy S III] goldsmitht:
so, definitely NOT kernel related, i'm on LK 5.1

AND of course, i was trying to clean up my sdcard, and deleted my backup! OH well, it works fine, just this issue with falcon pro

guess i'll wait and see what today's build brings

:confused:
[Verizon Samsung Galaxy S III] mastamoon:
just had a random reboot too.. :rolleyes:

https://dl.dropbox.com/u/13144052/last_kmsg_1.log
[Verizon Samsung Galaxy S III] goldsmitht:
no reboots here, but i'm on LK 5.1

:cyclops:
[Verizon Samsung Galaxy S III] xHoLyx:
Hey Mastamoon,

I think I remember you from Fascinate era ;)

Just bought s3 and was wondering if cm supports multiwindow
[Verizon Samsung Galaxy S III] V3TTOO:
I do have issues with Play Music not staying open. It will just close, no error or notification of any sort.

I have been having issues with audio since 3.4, but I thought it was only BT. After trying headphones, I see it is not that case. Anytime I am listening to Pandora, it will make crackling noises when I do things on the phone, like check messages or go online. Anyone been having these issues?
[Verizon Samsung Galaxy S III] Hybridnoob:
I checked my Play Music app and it force closed the first two times I opened it (without a message as you described), but I then cleared the app cache and it worked fine. I'll keep checking it, but that may have fixed it... No SOD or reboots so far (stock kernel).
[Verizon Samsung Galaxy S III] goldsmitht:
So far think multiwindow is only supported on TW roms; SYNERGY has it working
[Verizon Samsung Galaxy S III] thefuzz4:
Confirmed cleared out the cache/app data and all is now well.
[Verizon Samsung Galaxy S III] mastamoon:
4/2 build in OP

- re-enabled the pull down commits. Still had the half a pull down once in awhile issue with them left out.

- repo sync @ 3:00pm EST
[Verizon Samsung Galaxy S III] goldsmitht:
How is the falcon pro issue on this build?
[Verizon Samsung Galaxy S III] mastamoon:
I have opened and closed it a few times, refreshed my time line, scrolled up and down a bunch.. hasn't vanished on me yet. Cant say for sure its fixed but so far so good?!
[Verizon Samsung Galaxy S III] goldsmitht:
Still having issues, with it and play store. Can't get thru more than a couple swipes

Dirty flash, lk 5.1 kernel, but doesn't seem to be kernel related
[Verizon Samsung Galaxy S III] mastamoon:
Have you wiped falcon pro data?
[Verizon Samsung Galaxy S III] mastamoon:
I was just having the issue with the play store too. I wiped it's data and still had the issue. I opened it again, pressed apps, and was able to scroll without a problem. Backed back to main play screen and was able to scroll without problem.
[Verizon Samsung Galaxy S III] goldsmitht:
Still having problems. Force stopped, deleted data, and even uninstalled and still having issues.

Gonna try another ROM to see if that is it

Edit: have deleted, cleared, wiped, and force closed.

Falcon pro and Google play just will not stay open.

It worked on tw with no problems, just not cm. Neither official or unofficial, not sure what got added, but something isn't working.

But otherwise, alls working good
[Verizon Samsung Galaxy S III] mastamoon:
I guess its time to roll back to previous builds and figure out when it started. I think it was on 4/1 and 4/2.. my last build was 3/29, not sure if it was happening on 3/30 & 3/31 official.
[Verizon Samsung Galaxy S III] mastamoon:
Im going to guess its one of these display related merges..

http://review.cyanogenmod.org/#/q/s...ogenMod/android_hardware_qcom_display-caf,n,z

Going by not remembering it happening on my 3.29 build, I would reckon its one of the 3/31 merges.
[Verizon Samsung Galaxy S III] Reborn627:
Just got a reboot about 5 minutes ago. The phone was in my pocket so it doesn't seem app related unless it's something in the background. First definite reboot since I've flashed any CM10 build. Been running yesterday's build since about 4pm with the GideonX Easter release. Probably not helpful to say without a log cat file or something, yes?

Peace,

Ray
[Verizon Samsung Galaxy S III] GideonX:
Pull a last_kmsg and pastebin it.

cat /proc/last_kmsg > /sdcard/last_kmsg

PM or in the BMS thread so as to not clutter up this thread, thx.
[Verizon Samsung Galaxy S III] Reborn627:
OK, I did this in terminal emulator and got "No such file or directory" Does this need to be done via adb from my PC? Sorry, a little new to this side of things.

Peace,

Ray
[Verizon Samsung Galaxy S III] GideonX:
That means it didn't get a chance to write the file before it crashed or it wasn't caused by the kernel.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] mastamoon:
4/3 build in OP

- added cLock location fix

- repo sync @ 3pm EST
[Verizon Samsung Galaxy S III] mastamoon:
I'm sure I'm going to jinx myself here but so far no app closing issues so far on today's build.
[Verizon Samsung Galaxy S III] goldsmitht:
Out now, but will test when I get home. Clean or dirty flash?

:cool:
[Verizon Samsung Galaxy S III] mastamoon:
Dirty with caches wipes.
[Verizon Samsung Galaxy S III] mastamoon:
You idiot! What did you go and say that for? Enjoy your disappearing apps.

Issue is back :(:banghead:
[Verizon Samsung Galaxy S III] ugachris:
I wonder if Invisiblek knows about this issue? I haven't seen the CM devs talk about it.
[Verizon Samsung Galaxy S III] mastamoon:
He mentioned something about it on Monday in IRC.
[Verizon Samsung Galaxy S III] theoreticaljerk:
While all seems to be well outside of this one problem, I can't seem to fix this one issue.

Whenever the phone boots up, I get the Waiting for Activation screen and it just goes and goes never going away. If I hit the home button the phone seems to work fine but I don't know what it's doing in the background so not sure what to think of it.

I made sure to change CDMA subscription to RUIM/SIM but that didn't fix it. EDIT: Actually, just realized that every time I reboot, it's switching back to NV. Hmmm

Any ideas?

EDIT2: Stupid me, seems as soon as I complained...I found the solution that worked for me.

1. Change CDMA subscription to RUIM/SIM.

2. Boot into Recovery

3. Wipe Cache

4. Wipe Dalvik Cache

5. Dirty flash the ROM again

6. Boot on up and enjoy not getting the Activation screen.
[Verizon Samsung Galaxy S III] goldsmitht:
flashed the latest, and as usual, smooth, fast, and no issues!

except: Falcon Pro just will NOT stay open. works for a while, then boom, enstead of scrolling through my TL, i'm pulling down the notification bar and trying to figure out where Twitter feed went.

DM'd the dev, hopefully it is something they can figure out, other wise it is back to PLUME

:confused:

:cyclops:
[Verizon Samsung Galaxy S III] mastamoon:
Ill have a new build up with a possible fix in a moment :)
[Verizon Samsung Galaxy S III] mastamoon:
The moment.... has come! http://bit.ly/YymcSk

DOESNT FIX THE APP CLOSING ISSUE. Can still use it as today's daily if you like though.
[Verizon Samsung Galaxy S III] goldsmitht:
let me download and backup current, and i'll let you know what happens. Otherwise, like i said, i'm starting to think it is app related, and i'll just go back to PLUME. wasn't using before, so may just be that app.

thanks, everything else is, well, smooooooth!

:D
[Verizon Samsung Galaxy S III] masri1987:
Is that gonna be today's build or will there be another?
[Verizon Samsung Galaxy S III] mastamoon:
It happens to me in Falcon Pro, Facebook and Play Store so I don't think its the app.

Ill watch the merges from now till 3pm.. If nothing new gets merged that's 'worthwhile' that can be today's build. No sense in rebuilding if a few translations get merged or something.
[Verizon Samsung Galaxy S III] Restola:
The build you just posted does not fix the weird fc issues in the play store or tunein pro for me.

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] mastamoon:
Dang. :mad:
[Verizon Samsung Galaxy S III] austin1227:
Does this have Navbar? Also what about headset controls?
[Verizon Samsung Galaxy S III] Restola:
Flashing 3/31 official nightly fixes the issue.

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] WhammyDroid:
Agreed.
[Verizon Samsung Galaxy S III] blempka:
No dice on the fix here either.
[Verizon Samsung Galaxy S III] mastamoon:
Dang Dang :(
[Verizon Samsung Galaxy S III] goldsmitht:
still having them on playstore, when trying to use app to go into "apps" section. IF i go to my apps, then go through apps, no issues. not sure why that works.

seems to be touchy; like i don't have to touch only hover. Frankly, not a fan of that upgrade that is being touted; my fingers are too big, and i'll be launching everything i don't want to , just because my fingers "hovered"

and unfortunately, falcon pro seems to be closing as well.

is there a way to pull a log to show what is happening when it occurs, or with no message would there even be anything?
[Verizon Samsung Galaxy S III] mastamoon:
There are logcats out there already showing the issue. I installed TuneIn Radio and its really bad, can barely get the app to start without it dying.

Thankfully cyanogen popped up in the commit that I was reverting and asked for a log so hopefully he will be able to figure it out soon.
[Verizon Samsung Galaxy S III] illyfilly:
I was gonna move on over to this, but it seems as though this issue is on most nightly builds since it's on Rootbox as well.

dang
[Verizon Samsung Galaxy S III] Hybridnoob:
Supposedly, it's not an issue on 3/31.
[Verizon Samsung Galaxy S III] Restola:
3/31 brings back the random freezes though. May want to return to 3/17 or 3M.

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] sivarticus85:
3M? Was there a 3rd Milestone build? I don't see one on the CM website...
[Verizon Samsung Galaxy S III] Hybridnoob:
Or use another kernel. KT747 is my go to and LeanKernel is solid too.
[Verizon Samsung Galaxy S III] Restola:
I mean March milestone.

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] masri1987:
So basically, latest nightlies have been unusable?
[Verizon Samsung Galaxy S III] luis86dr:
Somewhat. Running 4/4 with latest kt747 kernel and has been fine minus the random app fc. Doesn't happen that often with me, but it is still an issue. Hopefully the team gets to it on next nightly.

Team Kernelizers; Kernel tweaking at its finest.
[Verizon Samsung Galaxy S III] invisiblek:
cyanogen says he knows what's causing it the app crashes. i'll throw up an unofficial once he pushes something

EDIT: http://review.cyanogenmod.org/#/c/35154/

merged

building...

EDIT2: rofl

EDIT3: flash away, tested working, github app no longer disappears for me

http://invisiblek.org/sch-i535/roms/cm10.1/cm-10.1-20130405-UNOFFICIAL-d2vzw.zip
[Verizon Samsung Galaxy S III] xHoLyx:
Looks like he merged it into the git.
[Verizon Samsung Galaxy S III] invisiblek:
nevermind.....

(Ignore this post)
[Verizon Samsung Galaxy S III] xHoLyx:
Did it resurface?

Looks like cyanogen merged in few, but I wouldn't know

timestamp is 10

http://review.cyanogenmod.org/#/q/status:merged,n,z
[Verizon Samsung Galaxy S III] invisiblek:
sorry, no, that's not what that was all about.

i had posted a rom that wasn't booting, i needed to clobber the build in order to get it booting (i'll have a new one up shortly)

cyanogen pushed a bunch of goodies tonight and i wanted to get a build up for you guys

it'll be up shortly

the build i posted a few posts ago is solid, i highly recommend it

EDIT: here's a fresh sync with all the new adreno goodies included: http://invisiblek.org/sch-i535/roms/cm10.1/cm-10.1-20130405-UNOFFICIAL-d2vzw-2.zip

(100% stock cm, NO cherrypicks)

now it's time for bed...i need to get up for work in about 4 hrs :eek:
[Verizon Samsung Galaxy S III] iofthestorm:
Should be the same as the nightly right? Here's hoping the nightly boots lol.

Edit: official nightly booted fine.
[Verizon Samsung Galaxy S III] mastamoon:
Ill have a build up just as soon as github fixes its server. Having issues doing a repo sync right now.
[Verizon Samsung Galaxy S III] goldsmitht:
whatever they committed worked for the force closes on Falcon Pro and Play Store for me; so can't wait to see you work your magic and add back in your cherry picks

:cyclops:
[Verizon Samsung Galaxy S III] mastamoon:
Here is the 4/5 morningly build. No app disappearing act anymore! http://bit.ly/11wve2F

- MMS emoji button is back!

- Repo sync at 9:10am EST

If nothing else good gets merged this will be the build for today, if something good gets merged ill do my usual build around 3pm EST.

As always, please let me know if you see anything HERE that you would like included.
[Verizon Samsung Galaxy S III] tcsac:
For anyone having lockup issues, I'm still on the linaro build from 3/29 and have not had a single lockup or app issue yet. Bluetooth works great, play store works great, basically anything I've tried works as expected.

Builds here:

http://xdaforums.com/showpost.php?p=39713373&postcount=2011
[Verizon Samsung Galaxy S III] RED ZMAN:
Masta, just wanted to drop you a quick note to tell you thank you for your work on this wrong. I thank every post I can, but thought it would be interesting to share that I'm running the March 8 build.

I have 17 days of uptime, and I'm a very heavy user.

Bravo brotha, bravo.

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] mastamoon:
Thanks for the kind words RED ZMAN :)

That's an old build alright but glad its working for you! This latest build has a bunch of kernel updates and updated display drivers built in.. 3.4 builds are almost 100% compared to the 3.0 builds. Give your setup a backup and flash something newer. You might be surprised. :D
[Verizon Samsung Galaxy S III] goldsmitht:
WOOO HOOO!!! Everything is running suhweeeeet on this verson! thanks for all the work, cuz for some reason, your versions always run better. plus the added tweaks you cherry pick make it that much better!

no app shut downs, and everything is running buttery smooth. thanks again!

:cyclops:
[Verizon Samsung Galaxy S III] mastamoon:
Thanks!

Should be a good enough build to hold me over for the weekend :P
[Verizon Samsung Galaxy S III] Reborn627:
As usual, a very good build. Thanks to invisiblek, mastamoon and any others who were involved in the fixes that we're now enjoying. I'm curious if you know of any progress made on the Bluetooth MAP functionality. I realize it's more than likely a low priority but curious non-the-less.

Peace,

Ray
[Verizon Samsung Galaxy S III] Restola:
Masta, do you think you can take a look at recording volume (whatever you know, its more than I know!)? When I was PMing a little in december with mkasick he was working on this file and asked me to drop it in /system/etc/snd_soc_msm to test:

snd_soc_msm_2x

But once he fixed stereo recording and record volume was boosted a little, that was the last I heard from him. I got my first little one on the way and I'd rather not flash back to TW just to get the videos I know I need to take :)
[Verizon Samsung Galaxy S III] odub303:
I have a little one and the volume on my recordings is more than adequate, and has been for a while.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Ty07allstar:
Has anybody been able to get hdmi out to work? I'm using the latest nightly.
[Verizon Samsung Galaxy S III] eppo12-:
Have had 2 random reboots on the latest. Not sure if it's a coincidence or not but after the reboot an app updates.
[Verizon Samsung Galaxy S III] RED ZMAN:
I usually update till my problems ate give and battery life is good, then I hold of for big stuff, decided to see how long it had been and was shocked. LOL

I'll probably update on Monday though. Thanks for the hard work.

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] Hybridnoob:
Thank you for all of your hard work and excellent builds!

Confirmation Number: 8TV20203YU288270V
[Verizon Samsung Galaxy S III] bobby janow:
Something weird, probably not related to the rom but it's what I'm running now. When I make a call I can't hear the phone ringing in the earpiece. The call goes through but it's like dead air until someone picks up or it goes to vm. Perhaps a setting?
[Verizon Samsung Galaxy S III] invisiblek:
I'd appreciate some testing on some kernel patches.

I've patched in wifi updates from google (our bcmdhd driver is a mess!)

All seems to be fine here

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

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

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

download: http://invisiblek.org/sch-i535/kernels/kernel_3.4_bcmdhd-update_4-6-13.zip

(i'd recommend being on a rom build from today or yesterday)

If it breaks your wifi for some reason (shouldn't), just re-flash your rom or whatever other kernel you are using

EDIT: Tethering is broken, beware!
[Verizon Samsung Galaxy S III] Restola:
Flashed along with 4/6 (coming from 4/5). It connects to my wifi just like before, no immediate problems.
[Verizon Samsung Galaxy S III] Reborn627:
Flashed and connected. I'll let you know if I have any problems.
[Verizon Samsung Galaxy S III] bobby janow:
Initial boot no problems with wifi. Locked on immediately with official nightly 04-06. Turned off wifi, 4G came right up, back to wifi instant. I'll post some more later.
[Verizon Samsung Galaxy S III] Ty07allstar:
Does anybody know if there is a way to get hdmi out working with the MHL adapter?
[Verizon Samsung Galaxy S III] Reborn627:
I'm guessing that it isn't something that's been implemented as it isn't a standard feature on the GS3. Yes, I realize that you can get a USB to HDMI adapter but because it's not terribly common, and would more than likely require the developer to have the adapter as well, you'll find some difficulty getting it worked in. Not trying to discourage you but I know this isn't your first time asking.

Peace,

Ray
[Verizon Samsung Galaxy S III] Ty07allstar:
It is a standard feature on the GS3. Samsung sells the adapter for it. I guess I'll have to go back to a TW rom. Thanks
[Verizon Samsung Galaxy S III] iofthestorm:
I don't know why he said it's not a standard feature, it is a standard feature and it did used to work though I don't use it often at all so I don't know when it broke (well, I'm assuming you tried it and it didn't work, I don't know if it's broken). Samsung does use a slightly different adapter but that shouldn't matter.
[Verizon Samsung Galaxy S III] fromthesticks:
Was working for me 2-3 weeks ago. Just got a mhl adapter back in march. Will try in an hour or so when I get home. But I'm guessing it should still work.

Edit: got home plugged in adapter and phone acted like it was going to display. ( went landscape and changed resolution) but never displayed on the tv
[Verizon Samsung Galaxy S III] Reborn627:
I'm sorry, maybe I should clarify. To me, and maybe I'm way off here, a standard feature is one that functions straight out of the box with that which comes in the box. In the case of the usb to hdmi, the phone may have the capability out of the box but it requires a premium item, the adapter that must be purchased from Samsung. Much like OnStar from GM. The car may have the capability to use OnStar, and may include a "free" trial, but will require and additional purchase, or subscription, in order to use it. That's all. I apologize if I seemed to offer inaccurate information.

Ray
[Verizon Samsung Galaxy S III] jasonfreeland:
Just wanted to say thanks Masta, your lattest build has solved an issue that had my ebook pages turning by themselves. Quite annoying when trying to read. Good workl
[Verizon Samsung Galaxy S III] iofthestorm:
Oh I get what you mean now, makes sense. I thought you mean it wasn't a feature that all Galaxy S3s had or something. The way I see it the feature is always there it's just the hardware doesn't come with the phone. It is definitely one of the less used features so it sometimes gets broken randomly and takes a while to be fixed.

At least we have it usually though, I think for the Exynos powered S3s they probably will never get it because of Samsung's crappy source releases. My tablet suffers because of that :(
[Verizon Samsung Galaxy S III] NegativeOne:
invisiblek, I flashed your 4/6 build over a previous mastamoon build (mid march) and it bricked me. No boot loop, just shows the samsung logo, then black. Can't seem to get into recovery either. I have to do a battery pull just to get it to show anything at all again.

edit: disastrophy averted. I finally managed to get into recovery. Not sure why I couldn't do it at first. If anyone else experiences this, I did the following:

* booted into download mode first and went into it

* plugged phone in

* battery pull

* unplug

* plug back in

* booted into download mode again but canceled out of it

* booted into recovery successfully

I'm sure these steps are probably coincidental because I can't think of any reason they should work, but if you land in my boat, maybe worth a shot.

Anyone else try this build? Do I have to be on CWM 6.0.3.0? Because i'm on CWMTouch 6.0.2.8

edit2: I think something went wrong with my recovery. I used rommanager to trigger a backup and flash. after I restored my backup it took me to the welcome screen of android, and it looks like my /data/apps (probably whole data partition) didn't get restored correctly. Even though as I'm doing it right now i'm watching it restore data. so... something is really screwed up here and i'm not 100% sure what happened.

I've been flashing CM10/CM10.1 since august and I haven't bricked even once.
[Verizon Samsung Galaxy S III] mastamoon:
Mid March could have been a 3.0 kernel based rom so that would explain the booting issue. His build was just a kernel I believe. A 3.4 kernel.
[Verizon Samsung Galaxy S III] SilentAce07:
Alright so I came back from PA and still getting the activation bug. I even tried setting to RUIM/SIM and getting my number back, booting to recovery, and dirty flashing the rom again (with and without dalvik and cache wipes).

What gives?

I mean, it takes away the bug for the next boot, but not any after. And that same process can be done just by solely wiping cache and dalvik.
[Verizon Samsung Galaxy S III] GideonX:
You didn't brick your phone if you can still get into download or recovery.

Like mastamoon said, it sounds like you flashed invisiblek's 3.4 test kernel on top of a 3.0 cm build. You could have fixed it by just reflashing the original rom you were using.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] invisiblek:
Yea, sorry if I didn't make that clear enough, that was just a kernel, not a full rom. It was a 3.4 kernel too so it should probably cause breakage on roms that are more than a few days old due to recent updates. Regardless, its not really ideal to flash it anyway now, since there is some breakage in the bcmdhd driver which causes tethering to not work.

mastamoon - how long have you been building with this commit? http://review.cyanogenmod.org/#/c/34928/

I haven't heard of a single wifi problem, so I think I'll merge this unless someone has an objection.

The next major updates to bcmdhd might take a bit, they are nasty...

Like this one: http://review.cyanogenmod.org/#/c/35221/ (+15227, -9399)

Surprisingly tethering is the only thing that breaks with that.

Hdmi out won't probably work since the 3.4 kernel change. I'm not sure what it would take to get that working, and I don't have the means to test anything with it either.