yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] mastamoon:
First/Clean flash will take forever for the radio to come up... Dirty flashes are a bit faster but still lag behind everything else coming up.. even with just a reboot, the radio takes a bit to come up.

I think that ZIP is just incorrectly named.. the correct baseband is NE1 which you are using.
[Verizon Samsung Galaxy S III] mastamoon:
My recents works while in an app. Long press, it vibrates, then pulls up the recents. Maybe its just a certain app that is causing the interference?
[Verizon Samsung Galaxy S III] mastamoon:
I havent used a theme in a bit... maybe try uninstalling the theme and reinstalling? Maybe uninstall theme, wipe theme manager app data, then reinstall? Maybe its that theme in particular?

Theme Engine is a work in progress at the moment, I would expect bugs.
[Verizon Samsung Galaxy S III] Master Cylinder:
I found some show up in the 'Theme Packs' section and some don't. The one's that I have that don't, have very little themeing going on.

They're tweaking the theme engine constantly at the moment it seems, looking at the changelogs. I'm just not finding any interesting themes - (not interested in anything 'dark.')
[Verizon Samsung Galaxy S III] meskes:
Nah, I copied the baseband version to here, wrong. I've just never seen a radio take that long to come online, even with the official CM releases. I guess what I was asking, is, is this particular radio known to contribute to stability and random reboot issues, and if so, which radio would be the best version to downgrade to, to minimize this. I know this is alpha, and that these things are to be expected but, if I could help minimize it by downgrading radios, that would be great. Even the CM11 milestone releases were panicking more than they should have, so that may help there as well, should I decide I want to downgrade in the future.

M
[Verizon Samsung Galaxy S III] mastamoon:
NE1 is the radio I use and therefore recommend. I dont see any random reboots or anything that would be caused by radio.. And I believe you need to be on it for proper GPS functionality also.
[Verizon Samsung Galaxy S III] meskes:
All I'm getting with it, after yesterdays release, is a kernel panic, and reboot
[Verizon Samsung Galaxy S III] mastamoon:
I would imagine most here are using this radio, I have been for months and months.. if that stuff was related to what baseband you were on, I think it would be a bit more widespread. I ran yesterdays build all day before releasing it, and most of the day today till about an hour ago.. NO reboots/panics found.
[Verizon Samsung Galaxy S III] meskes:
I'm talking about the GPS. Every time it tries starting the GPS module, the phone panics and reboots. I'm driving ATM, so o can't pull logs
[Verizon Samsung Galaxy S III] mastamoon:
Well thats the first time you said GPS in any of your posts. In any case, I am able to open any GPS app and dont have any issues with panics/reboots. What GPS app are you using? Google Maps? If so, random reboots with Google Maps is an old bug. Ive had it forever really, after navigating for an hour or so,.. but its hit or miss. Generally I reboot my phone before I need to use Google Navigation and try not to do other stuff at the same time.
[Verizon Samsung Galaxy S III] meskes:
I'm not thinking it's software tho, I'm starting to think its hardware

---------- Post added at 01:54 PM ---------- Previous post was at 01:46 PM ----------

You kinda reminded me, when you mentioned the GPS bit, was all. I should have been specific about it. Didn't know this was a Google Nav specific bug. I'll keep that in mind, and try another app.

M
[Verizon Samsung Galaxy S III] faehsemc:
It was working just fine up to the 1-23 build and then it just decided to stop.. Its whatever though, not a big deal obviously because it is a WIP. was just wondering if it was a change or me. I did reinstall it, also reflashed ROM update fresh. I might just pulling the ap from the 1-23 build and replace it
[Verizon Samsung Galaxy S III] shwise:
This recents glitch been bugging me for the last two builds. I've got no third-party apps at all. Did you do a clean install? Maybe that's our issue?
[Verizon Samsung Galaxy S III] Master Cylinder:
Your confusing me a little. Holding the home button is what activates "recents" for you, right? (EDIT - I guess you could have it changed in a custom launcher...)

I have just been testing and recents doesn't behave in a way I would've expected. Maybe I never noticed before but if I hold the 'home' button for recents within an app, it brings them up, showing the home screen in the background with a Google search bar (which don't exist on any of my home screens because I disabled them in Nova.) Then there are a series of functionality with a combo of button pushes. See below.

Within app:

Hold 'home' => recents, then

Press 'return' => home screen, then

Hold 'home' => recents,

Press 'return' => original app. No more recents from within that app without closing it..

If I choose a new app with recents, I can't pull recents back up within that app but must press once for home screen first.

I don't think this is a bug but a series of button combos that provide some more functionality. Also, some apps may not be written yet to work properly with this new functionality. Here's something I found:

https://developer.android.com/about/versions/android-5.0.html

"Concurrent documents and activities in the recents screen

In previous releases, the recents screen could only display only one task for each app that the user interacted with most recently. Now your app can open more tasks as needed for additional concurrent activities for documents. This feature facilitates multitasking by letting users quickly switch between individual activities and documents from the recents screen, with a consistent switching experience across all apps. Examples of such concurrent tasks might include open tabs in a web browser app, documents in a productivity app, concurrent matches in a game, or chats in a messaging app. Your app can manage its tasks through the ActivityManager.AppTask class.

...

Tasks in the recents screen can be set to persist across reboots. To control the persistence behavior, use the android:persistableMode attribute. You can also change the visual properties of an activity in the recents screen, such as the activity’s color, label, and icon, by calling the setTaskDescription() method."
[Verizon Samsung Galaxy S III] razorloves:
lots of people complaining about this recents glitch in the opo and nexus section too.

started when several activitymanager commits merged on the 28th.

looks like they just reverted the one that causes it.

http://review.cyanogenmod.org/#/c/87224/
[Verizon Samsung Galaxy S III] XdrummerXboy:
Hmm... I did a dirty flash of yesterdays (1-28), and dirty flash of todays (1-29). I had/have issues on both. I was coming from a clean install of a nightly about a week ago, didn't have issues on that one.

I hold the home button, it vibrates like normal, but it will stay on the current screen.

***

EDIT: Then, pressing home will do nothing. I must press home AGAIN (twice) to actually go home.

***

Then if I hold home again, it will bring up recents BUT it animates the screen as if my last activity was still active, as in it pulls the activity bar from the top as opposed to from whatever is normal (middle or bottom maybe?)

Also, separate issue unrelated, but related because it deals with recents. There's many times when not ALL activities will show up in recent apps. Sometimes it will take a couple tries for them all to show up. Its been an issue since CM11, and I've learned to deal with it so its not a bit deal. Just thought I'd bring it up... Haha
[Verizon Samsung Galaxy S III] kidhudi:
i found out why my phone keeps rebooting.. my power button keeps sticking. on TW the restart box keeps showing.

sucks that it makes lollipop reboot. i guess i will wait till verizon sells the nexus and upgrade. i heard feb 26 is the release date but who knows.

i am also contemplating swapping out the switch. they are cheap and i am pretty decent at soldering :)
[Verizon Samsung Galaxy S III] mastamoon:
Ive heard this is a common issue with these phones... and no joke.. a simple fix is hitting that side of the phone, near the powerbutton against like a table or something. Dont wanna go full force on the stupid thing of course.. but you can find videos and other people claiming this fixes their reboot problems with their power button.

Yeah im hearing the 26th also. Im just not 100% positive if I want to stay with vzw.. ill be losing my unlimited data at that point anyway. :silly:
[Verizon Samsung Galaxy S III] bitemeoftn:
If you buy the phone outright from ebay or elsewhere you can keep your unlimited. They tried getting me to give it up quite a few times, but I use my phone too much to be limited to 2 or 4 GB.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah I just dont have the cash to buy it outright and feels weird spending 700 bucks on a phone. I know you end up paying that plus some, but stretched over the 20/24 months. Another issue is I really would want the 64GB White version (for the silver border).. but thats like impossible to come by thus far.
[Verizon Samsung Galaxy S III] Deliquified:
I had this exact problem at one point. I smacked mine off the wrist pad support on my mousepad and it fixed my issues.
[Verizon Samsung Galaxy S III] Blaiser47:
There are ways to upgrade and keep unlimited data. Just google verizon keep unlimited upgrade slickdeals.net
[Verizon Samsung Galaxy S III] kidhudi:
I am back on masta's build. Woohoo. I smacked my phone on my kitchen table and haven't rebooted in like 2 hours.

My new mantra.... Don't touch the power button... Don't touch the power button...

Thanks masta for the tip.
[Verizon Samsung Galaxy S III] TheDiabolicaL1:
Rom runs great on the lady friends phone. I bought her a new phone and she doesn't want it this rom runs so well for her. Great work! Thanks!

Funniest thing I've read on xda to date.

Sent from my Nexus 7
[Verizon Samsung Galaxy S III] rougedragon:
Mines that I gave my lady friends screen still turns on and off cause its so sensitive
[Verizon Samsung Galaxy S III] NoCrAppleHere:
CM11:

Camera apps aren't working at all now. Nothing of the usual fixes aren't helping. Any ideas? Thanks
[Verizon Samsung Galaxy S III] XdrummerXboy:
Did you try to flash back to stock/Touchwiz for the drivers and such? Use scottsRoms.com 4.3 unlocked bootloader.

Not a guaranteed fix, but could work.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Weird stuff, couldn't get any camera apps to work, build in, goog camera, Camera Zoom, etc, though all the others just auto FC'd, Camera Zoom actually stayed open until I tried to take a pic, then FC'd. After multiple fails at fixing this, I said let me try to go front facing and see what happens. Well, front worked fine and when I went back to rear, it worked too and has not given me a prob yet. Very odd, but hopefully it continues to work. ?
[Verizon Samsung Galaxy S III] malcalevak:
Sorry if I missed something, but if you're talking about a Nexus 6, Motorola has a payment plan option that I believe didn't even add interest. In hindsight, because of the lack of interest, I probably should've gone that route myself!
[Verizon Samsung Galaxy S III] Deliquified:
Did you try the app "a better camera"? Works for me.
[Verizon Samsung Galaxy S III] stevet86:
I've tried all of the mentioned camera apps and the one that works for my phone is is camera 51. The others will work at first but then stop after one or two pictures being taken. Not sure what the issue may be.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] mastamoon:
I've been using camera zoom fx for a bit. Seems to work good.. Took about 20 shots last night, no problem.
[Verizon Samsung Galaxy S III] shwise:
[MENTION=2963287]mastamoon[/MENTION] The recent's bug was patched in today's nightly. When do you expect to post the next build?
[Verizon Samsung Galaxy S III] mastamoon:
Monday most likely. I had a problem with the build on Friday so couldn't post it.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Ahhh good news!
[Verizon Samsung Galaxy S III] mastamoon:
Note:

When I booted this build, I had no radio.. I had a "NO SIM" message that eventually went away. I let it hang for another 5 or maybe even 10 minutes and radio never came up. I rebooted, all has been well since. Ive rebooted a handfull of times.. no problems.

Just wanted to mention it. Was probably just my device/boot. LMK if you guys see the same thing.
[Verizon Samsung Galaxy S III] meskes:
It must have just been your hardware. The radio came right up, for me. Great work, my friend.

Now if invisiblek can sort out the camera issues, we can go official. He is still the device maintainer, isn't he?
[Verizon Samsung Galaxy S III] mastamoon:
Good to hear!

Yes he is. He's hoping somebody else wants to take it off his hands though. He also maintains 2 other devices and hates Samsung now too.

I still can't call myself a maintainer, if **** actually hits the fan, I'd be pretty lost. It sucks that the d2vzw crowd has pretty much been the main device for d2 development. Nobody really stepped up and did major stuff on any other d2s.

Unless somebody really can take over d2, idk if it will ever go official.
[Verizon Samsung Galaxy S III] meskes:
Yeah, I remember his sentiment toward Samsung, and I can't say I blame him..

As far as taking it over, I wish I could, but I don't have the time nor knowledge, myself...
[Verizon Samsung Galaxy S III] dranyam:
Charging issue?

I installed the latest build today and had super fast battery drain which I thought was odd... So I plugged it in to charge and now it says something like 11 hours to a full charge? It would appear that it isn't charging, it has been there all night and is still saying 11 hours until full. Anyone else experience anything like this?
[Verizon Samsung Galaxy S III] XdrummerXboy:
Thanks for the heads up!
[Verizon Samsung Galaxy S III] dranyam:
Sorry I goofed on the img code should be fixed now.... look at that drop
[Verizon Samsung Galaxy S III] XdrummerXboy:
Wow, that's crazy... I would be surprised if something with the update would legitimately cause things like Facebook and Instagram to take up that much battery... But who knows.

Have you tried restarting?
[Verizon Samsung Galaxy S III] dranyam:
Yeah that is the weirdest part..... I wasn't even really using the phone during that time. And yeah I tried restarting a couple times.
[Verizon Samsung Galaxy S III] Rushead:
Uninstall FB & Instagram
[Verizon Samsung Galaxy S III] rougedragon:
That is pretty fishy

Sent XDA Free mobile app
[Verizon Samsung Galaxy S III] XdrummerXboy:
Yeah, I would probably try that. Uninstall / reinstall.

Probably won't do anything, but worth a shot.
[Verizon Samsung Galaxy S III] DubleJayJ:
You'd be surprised. Those apps drain battery hard, especially Facebook.
[Verizon Samsung Galaxy S III] mastamoon:
You were getting a slow charge rate because your phone thought you were connected to a USB port on your PC or something, werent getting the full charge rate you get from a charger.

That on top of a wakelock will cause large charging times. Looks like you had a Google Services wakelock, likely a network location wakelock, you could have probably rebooted your phone and got back on track. I ran the same build all day without any wakelock issues.

EDIT: saw you did reboot a few times.... strange. Did you just reboot or do a battery pull? Sometimes a battery pull works wonders :)
[Verizon Samsung Galaxy S III] rhymestealer:
official CM12 GApps

Saw an entry for CM12 GApps posted yesterday to the official CyanogenMod wiki article (sorry I can't post links yet):

wiki.cyanogenmod.org/w/Google_Apps
[Verizon Samsung Galaxy S III] mastamoon:
Oh finally! Thanks for the heads up. Ill likely add it to the OP, though I do like having more up to date Gapps when I decide to clean install. But official is the easiest way to keep everybody on the same page.
[Verizon Samsung Galaxy S III] meskes:
Your USB cable is going out. That's the exact same thing that happens to me, when mine starts to die.
[Verizon Samsung Galaxy S III] Shakes The AssClown:
Not judging at all because I think it's awesome how you guys do this. Just wondering what is making the camera such a problem? That's the only thing holding me back. Doing an awesome job!!
[Verizon Samsung Galaxy S III] drdiehl:
Phone process

My phone process keeps stopping. I must re-flash phone modem to restore. This has happened many times. Any ideas?

---------- Post added at 08:12 PM ---------- Previous post was at 07:58 PM ----------

I use Greenify to hibernate my social apps so they don't run in the background. It really helps me.
[Verizon Samsung Galaxy S III] rougedragon:
Greenify is good except it turns notifications off
[Verizon Samsung Galaxy S III] mastamoon:
Its "easily tweakable" from the device actually.

You will want to edit snd_soc_msm_2x in /system/etc/snd_soc_msm, the SectionDevice "Voice Earpiece" shown below,

SectionDevice
Name "Voice Earpiece"
Comment "Handset Rx device for voice call"

EnableSequence
'PRI_RX Channels':0:eek:ne
'RX1 MIX1 INP1':0:RX1
'EAR PA Gain':0:POS_6_DB
'DAC1 Switch':1:1
[COLOR="Red"] [B] 'RX1 Digital Volume':1:70%[/B][/COLOR]
EndSequence

DisableSequence
'RX1 MIX1 INP1':0:ZERO
'DAC1 Switch':1:0
'EAR PA Gain':0:ZERO
'RX1 Digital Volume':1:0
EndSequence

ACDBID 7:1
EffectsMixerCTL "SRS TruMedia"

EndSection

edit the % of "RX1 Digital Volume':1:70%" up or down to suit your needs. Its currently being built at 74%, in the example above, I set it to 70%. Here is the example above as a file you can download and drop in that directory, then reboot. If everybody agrees its to loud, I can make the change in the build, or I can make a flashable zip you would need to flash every time you flash a new build.

File: https://www.dropbox.com/s/2r37zvn1tzzpwv9/snd_soc_msm_2x?dl=0
[Verizon Samsung Galaxy S III] mastamoon:
I got a PM from another user that said...

So you may want to try that and see if it calms your volume down. I havent noticed it being overly loud, so maybe it is something like this.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
What's the difference between these and the ones in the op link, pa gapps signed 5.0 the full package? What's the easiest way now to get myself back to stock these days or best way to start from scratch without a bunch of hobknob? Ik I can odin to stock, use causal tool, etc but I am wondering if anything else is as useful. Ty
[Verizon Samsung Galaxy S III] XdrummerXboy:
Is your goal the 4.4 ota? Meaning locked boot loader?
[Verizon Samsung Galaxy S III] mastamoon:
About gapps.. I like to use what the CM guys are using for troubleshooting purposes. PA Gapps isnt just a gapps installer.. it does some more **** in the background that could lead to some issues/confusion when troubleshooting.

Going back to stock.. Usually you can just flash any Stock Based Rom (except for the NE1 roms out there).. ODIN is the way to go 100% unmodified stock though.
[Verizon Samsung Galaxy S III] Prack:
I'm on the 1/15 build, clean install with pa gapps from around the same time. For whatever reason I can't do a dirty flash of any of the nightlies after. It boots to the samsung galaxy s3 splash screen and the blue light blinks but I never see the CM boot animation. I tried letting the phone sit for almost an hour and it never did boot/reboot or anything. I eventually end up going back to my 1/15 build. Any ideas?
[Verizon Samsung Galaxy S III] mastamoon:
I would make a backup, factory reset/data wipe and see if you get any further.

Strange.
[Verizon Samsung Galaxy S III] Prack:
I just tried a dirty flash again, but wiped system, seems to be booting now. I know the boot animation changed between then but I didn't see anything else that may affect the boot.
[Verizon Samsung Galaxy S III] mastamoon:
Damnit, I was going to say just system wipe... :fingers-crossed:
[Verizon Samsung Galaxy S III] neolink1:
Has anyone seen any camera related commits lately? I wonder if we'll ever be able to use the stock camera & video.
[Verizon Samsung Galaxy S III] Prack:
Well it booted but I ended up with no data. Tried again and no matter what I do I can't dirty flash 2/4 over my 1/15 and keep data. I really don't want to do a full wipe unless I have to. If this was dirty after dirty I would understand but my 1/15 install was a full clean install. Haven't done even one dirty flash :(
[Verizon Samsung Galaxy S III] NoCrAppleHere:
No, you are misunderstanding, I just want to start fresh from stock, root etc and then install Cm12. Btw, you mentioned once before to try a scottsroms.com rom bc of issues I was having but nothing was there for the GS3. It mentioned something about retired devices may they rest in peace or something like that. Lol, but yeah, I didn't see anything.
[Verizon Samsung Galaxy S III] mastamoon:
Did you reboot after no data? Ive had no data after a flash before, reboot has fixed.

You can pull some logs if you like, will have to set up your PC to do adb logging, then get a boot log for us to look at. Do you have any mods or 3rd party kernel installed in 1/15?
[Verizon Samsung Galaxy S III] Prack:
Yup, rebooted a few times thinking the same thing. No 3rd party kernel or mods installed. I can do a clean install I just hate to setup everything again. Other than themes, new boot animation and a few other fixes I don't see a huge difference between the two so I'm surprised I can't dirty flash. I was on call for work so it sat on 1/15 for a while otherwise I would have been keeping up to date. I don't play with my rom during on call lol.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Ahh, that's unfortunate!

I am currently uploading the ROM I downloaded from his site to my dropbox.

I will post a link when it's done.

---------- Post added at 03:14 PM ---------- Previous post was at 02:52 PM ----------

EDIT:

Here is the file. I forgot that it was nearly 1GB when I started uploading it, so it took quite a while. I *THINK* this is the closest you can get to the most current stock ROM without locking your bootloader. It's such a large file because it includes all drivers, and I'm sure TW is a decent chunk of that too.

Anyways, this is a flashable ZIP. Back everything up, wipe everything just like you would any other ROM, flash this, and you should be good to go. Pretty sure Gapps are included, but I can't remember. First boot will take a LONG time. As some have mentioned, it could be a good idea to get a solid GPS and Data lock before going back to Cyanogenmod. Also, root is already taken care of in this ROM. And I apologize, but I don't have any MD5 to verify the file. I could check the MD5 of the file on my PC if you wish.

ScottsRoms.com 4.3 Unlocked Bootloader for VZW GS3
[Verizon Samsung Galaxy S III] NoCrAppleHere:
You didn't tag me but I'm sure this was in reply to my post. I'll give it a try before I go back to stock and reroot, have no patient for that. Lol. Thanks
[Verizon Samsung Galaxy S III] meskes:
Holy ****. We have the camera.

[MENTION=2963287]mastamoon[/MENTION]
[Verizon Samsung Galaxy S III] DubleJayJ:
On the 2/5 build? I haven't flashed it yet, figured nothing of importance was on it but if camera is finally working I'll have to flash
[Verizon Samsung Galaxy S III] meskes:
On today's build. Fully functional.

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

@mastamoon I love you, and I love Dan. That is all.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Whaaaaat. GREAT news!!!

Is a clean flash recommended?
[Verizon Samsung Galaxy S III] meskes:
I just did a straight update, followed by the usual cache wipe. Nothing more.