yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] TokedUp:
You're sure living up to ur name. Lol just joking. I've never checked XDA so much ever! The unofficial CM11 thread is so annoying. Everyone is trolling and there's so many builds I don't know which one to try. Patiently waiting for Slim Kat to purr on my S3. At least Masta is starting his CM11 builds soon. F5! F5!
[Verizon Samsung Galaxy S III] annoyingduck:
Yeah, I'm only going to run an original developed rom on my phone from trusted devs. There's a ton of ports, kang builds floating around (for my N7) that are less than stellar. Not taking that chance because I need my phone to actually work! Judging from this latest Slimkat 1.1 build, I think whatever gets released for our phone from slim is going to be a solid performer.
[Verizon Samsung Galaxy S III] annoyingduck:
Check out the new wallpaper..
[Verizon Samsung Galaxy S III] stevo11:
Just flashed stable 2 and it is running really smoothly so far. Only issue is the Google now app. Any time I search something or click a card the app force closes. Completely clean flash with the aroma gapps.

Edit: uninstalled Google now with titanium backup and reflashed the gapps package but chose the toggleable version, seems to work now. One question since I am a little unfamiliar with the slim specific gapps packages. If a new version of the app is published by Google to the app store can I update normally or do I have to wait for a new gapps package to be published?
[Verizon Samsung Galaxy S III] mefistofel666:
4.4 for verizon...

come on guys. I am a bit tired of waiting for 4.4 version. on a more personal note, just kidding. I just can't wait. You guys are doing such an amazing job. I kept going to different roms from time to time just to see if there's anything better, and so far I always come back.

Again just wanted to say what an amazing job you guys are doing.
[Verizon Samsung Galaxy S III] annoyingduck:
If you want Slims toggle-able version, you'll need to wait for an updated slim 4.3 gapps package. They will generally have single update packages available that you just flash, but I'm sure the priority is on 4.4, so it may take longer than usual.
[Verizon Samsung Galaxy S III] stevo11:
Got it, makes sense. In that case, is anyone else having issues with the non-toggleable google now app in the AIO aroma package (constantly force closing when being used)? Only the toggleable one works.

Is there a different gapps package i should be using?
[Verizon Samsung Galaxy S III] annoyingduck:
Well, an easy fix is to uninstall the slim google now w/ a root app, REBOOT, then install the playstore one. I wasn't having any Gnow issues, but that'll fix it.
[Verizon Samsung Galaxy S III] griz.droidx:
I think someone mentioned data not switching a while back on build 2. I know there's nothing we can do about it now. It's out, we have 1.9 and 2, and the others for that matter.. But yesterday, trying build 2 again, I noticed while out of town where there's usually good signal compared to here, that I had to reboot once to get messaging to work. It would just keep saying sending with about 97 - 98db/m which is usually good enough for me to send texts of any size. I can't wait for slimkat too, or a decent 4.4 rom for that matter.. As you guys mentioned it'll be good if/when they release it.

I got bored and flashed ChaOS the other day just because wiz was working on it, and his MIUI and bootloader for the X were pretty slick as I'm sure most of you know.

---------- Post added at 11:52 AM ---------- Previous post was at 11:47 AM ----------

I think someone mentioned data not switching a while back on build 2. I know there's nothing we can do about it now. It's out, we have 1.9 and 2, and the others for that matter.. But yesterday, trying build 2 again, I noticed while out of town where there's usually good signal compared to here, that I had to reboot once to get messaging to work. It would just keep saying sending with about 97 - 98db/m which is usually good enough for me to send texts of any size.

I can't wait for slimkat too, or a decent 4.4 rom for that matter.. As you guys mentioned it'll be good if/when they release it. It seems development on the sgs3 is kinda slow at the moment. Maybe I'm wrong.. Maybe people are crunching away, and I'm sure there are some who are but when there's such a flood of new bad ass phones out development is going to get slower I'd assume as people transition to newer or better devices. But it being well over a year old, I think it's still going pretty good and for that for anything done on these devices I am extremely grateful don't get me wrong.. And I've been wrong more than once so...

I got bored and flashed ChaOS the other day just because wiz was working on it, and his MIUI and bootloader for the X were pretty slick.
[Verizon Samsung Galaxy S III] TokedUp:
Dammit! I updated to the new Goog Now and now its not inverted. I keep forgetting not to do that! Its just too tempting.
[Verizon Samsung Galaxy S III] tyleras3:
But the new Google Now is awesome so it's a fair trade off (:
[Verizon Samsung Galaxy S III] TokedUp:
True but the black looks so good with it. I'm sure we'll have it with Slim Kat eventually. Im hoping for the day of 4's Friday, PS4 and 4.4
[Verizon Samsung Galaxy S III] tyleras3:
I definitely cannot wait for SlimKat. If there's a ROM I can always count on for stability its Slim.
[Verizon Samsung Galaxy S III] trips555:
Not trying to start ANY sort of competitiveness/aggressive one-upping, but I need to know. Does this Rom have any broken features? If so, what are they. I know that in order to make roms, things get broken, but I use my phone so much that stability is more important than features or speed, or anything else. It's a bit difficult on these forums to find out what works or doesn't because people usually respond "OH IT'S COMPLETELY FLAWLESS" and the camera doesn't work, or the bluetooth doesn't work, which yields a response of "Oh, yeah, well except for that, it's flawless." Again, I get when builds gotta be in transitional stages to add things, but I'm looking for this, or another COMPLETELY functional rom. I'm sure this and all of them will be amazing, but is there any rom that's 99.99% STABLE? I'm asking here cause I've heard this one is pretty stable.
[Verizon Samsung Galaxy S III] CZ Eddie:
The new Google Now fixes some real issues. Especially if you were having problems using Utter (the voice app).

Otherwise, Google Now crashing after ROM re-flash is pretty common across all ROM's. The trick is to simply go to play store. Search for Google Now. Uninstall it from that page.

Reboot and then install Google Now from Playstore.

Reboot and it should work.

You can probably apply the same method to the toggle or other versions. But basically a clean uninstall/reboot/install works great. Or sometimes you have to clean uninstall/reboot/install/reboot/uninstall/reboot/install. That's kinda rare though.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I'm fairly certain BT is not 100% for any AOSP rom compared to TW. Been that way since day one on this device. One thing I notice is that with my headset, turning off BT in Settings before turning off my headset causes the on/off toggle bug requiring reboot or patience. Works fine if I turn off the headset first. BT is fine when I use my headset but idk about BT quality when streaming or syncing with vehicles. Camera quality is fine. I just think the UI is terrible and that is all on Google not the SB team in any way, shape, or form. I just prefer the TW camera.

I'll say this, if SB stable 2 does not work for you via TWRP then I encourage you to flash with CWM and see if its not a recovery issue. Some users have reported issues with successfully booting past the splash screen on first boot ore after a reboot and that seems to happen on other AOSP 4.3 roms too. Definitely take other users' responses to your question into consideration as well. I don't have random reboots or FCs to answer your question.

CZ Eddie,

I haven't ran into that GN issue but I think that's cuz Google Search is excluded from the Slim minimal Gapps. I always flash those so I have no input there. I do like the GN 3.1.8 though. Running fine (so far!) for the last few hours.
[Verizon Samsung Galaxy S III] Relentless D:
99.99% stable and stability more important than features or speed? I think this is what you are looking for.
[Verizon Samsung Galaxy S III] Aggraxis:
Build 2 official, clean wipe. Flashed both with TWRP and CWMod. Getting random reboots and hard locks that require a battery pull. I grabbed a last_kmsg, but the file was completely full of this same message:

pn544_dev_read: i2c_master_recv returned -6

What in the bananabeans is that? A quick Google search didn't turn up anything helpful.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Care to post that last_kmsg via Pastebin or attachment? Just wanted to take a look myself, no promises that I'll see anything.
[Verizon Samsung Galaxy S III] Aggraxis:
Here it is... basically some 38,000 or so lines of the same message over and over. The last random reboot happened while I was playing an MP3 in Google Play Music. Sometimes it randomly reboots or locks in the middle of the night.... like last night. Thank goodness my wife sets a backup alarm in the morning! :D
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I can't make heads or tails of what that log means lol I'm not a dev by any means btw so I'd have to see "error" or "failed" a few times to be able to see anything in there. Best I could see is that "pn544_dev_read" points to something in drivers/misc based on google searches but that's from looking at someone's Github.
[Verizon Samsung Galaxy S III] Aggraxis:
Yeah I have no clue. I'll let you know if I learn anything fun, though.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Found this also but idk if it helps at all. If another last_kmsg has a different output then it might be more telling. Are you on the VRBMF1 firmware in Settings/About Phone?
[Verizon Samsung Galaxy S III] Aggraxis:
DOH. No. It says I535VRBMB1... I guess it's search time again!

Edit - Found it, flashed. I feel uber dumb right now. I'll keep you posted. Thanks again for the help!!!
[Verizon Samsung Galaxy S III] annoyingduck:
It also doesn't hurt to Odin back to stock every now and then. Cleans your system right up, installs the current firmware. I did it about 4 months ago and do not experience any of the "unknown" bugs that get reported.

This is also why I hate Verizon. Using my N7 with fastboot (samsung does not have this) is a root users dream, was looking forward to the N5:mad:! Much easier than odin, flashing a factory image through fastboot retains your unlocked bootloader and root is just flashing or downloading super su. 10min tops...
[Verizon Samsung Galaxy S III] SlimSnoopOS:
No problem, hope that helps out!

I bet it is man, I'm looking forward to switching to an unlocked GSM device but preferably a Nexus next year.
[Verizon Samsung Galaxy S III] Capt. Napalm:
4.3 Roms reboot problem

For what its worth, this is the EXACT problem I had with my S3, no 4.3 rom would boot a second time. I finally got them working (CM, Beanstalk & Slim) by flashing the root66 ODIN file from here:

http://xdaforums.com/showthread.php?t=1762204

Followed by this:

http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw

I had to flash the Root66 file twice in ODIN before it would boot, fyi.

Hope this helps anyone in the same spot.
[Verizon Samsung Galaxy S III] Aggraxis:
Had another random reboot in the car about 30 mins ago. The last kmsg attached looksba lot different this time.
[Verizon Samsung Galaxy S III] MrBrady:
I've noticed on 4.3, apps that are running on the background often have a system notification.

Did example Pandora. You get the standard 'What's playing' notification bit also a 'Pandora is running' notification.

I see you can disable app notifications in app Settings but then it removes the What's playing notification as well. Any way to remove only the background app running notification?

Sent from my Anthrax-powered VZW Galaxy S3
[Verizon Samsung Galaxy S III] texaswickedtoys:
Ok I have a question I have been running this for a few days now and no major issues but I keep getting a sms message that says "vzwmn:1" anybody kniw what this is
[Verizon Samsung Galaxy S III] glman1:
https://community.verizonwireless.com/thread/775205
[Verizon Samsung Galaxy S III] Eyalkn:
I got it a long time ago and Verizon couldn't help me so I got rid of it on my own by installing smsblocker from the play store. And now when I log in Sms blocker I can see that I have stopped receiving them all together so it doesn't block them anymore.
[Verizon Samsung Galaxy S III] danstar:
This is caused by the verizon backup assistant. You need to go into your verizon account, go to backup assistant, and delete the email address you have associated with backup assistant. This will stop the text messages.
[Verizon Samsung Galaxy S III] carpdeeem:
Best as I could tell from the 4.2 forum, the stock Slim Bean kernel doesn't have MicroSD exFAT support. Could somebody confirm whether this is still the case with 4.3 (or if I was wrong to begin with)? Amazon has SanDisk MicroSDs on sale today and I'd jump on it as long as they would work. Thanks!
[Verizon Samsung Galaxy S III] tvl76:
I bought a San Disk 64 g last winter. It did not work well with my phone. Kept crashing, fail to read, etc.

I'm not using it anymore. Using a Samsung 32g now, Works perfect.
[Verizon Samsung Galaxy S III] annoyingduck:
Not sure about 4.3 and exfat, but I have the exact 64g card on sale today. I formatted it to fat32 and it works great. Only drawback to formatting to fat32 is you can't transfer any SINGLE file bigger than 4gig. I just bought another one today and I'll be doing the same thing....
[Verizon Samsung Galaxy S III] annoyingduck:
Fyi (devs), cm10.2 official that just dropped has a fully functioning 4.3 camera, including front camera. Focal is still broken though. If that helps solving our slim issue...
[Verizon Samsung Galaxy S III] nicklovell23:
Already in the works :)
[Verizon Samsung Galaxy S III] annoyingduck:
Figured as much....:cool:
[Verizon Samsung Galaxy S III] dbornack:
Can we hack it for External Storage?
[Verizon Samsung Galaxy S III] annoyingduck:
I'm backing up.....and constantly hitting refresh:cool:
[Verizon Samsung Galaxy S III] RayMcGrath:
Crazy anticipation :eek::p
[Verizon Samsung Galaxy S III] nicklovell23:
Don't break your f5 keys lol. Still having some camera issues trying to get fixed before the weekly rolls of the press.
[Verizon Samsung Galaxy S III] icon123:
New build is up!
[Verizon Samsung Galaxy S III] d1ez3:
Downloading now.. I'm thinking of a dirty flash from 8/10 beta. Any issues I'll clean flash.

Edit: First thing I noticed was LTE instead of 4g now on the signal bars

Had a reboot going to front camera.. Will need to clean flash build now (was on the camera fixed weekly beta 1 before)
[Verizon Samsung Galaxy S III] m_s_ifland:
Stupid question, I can't for the life of me remember where to turn off the keyboard notification in the status bar, can someone remind me please? Thank you.
[Verizon Samsung Galaxy S III] juancaperez2000:
Dirty flash, front camera still not working
[Verizon Samsung Galaxy S III] GideonX:
Settings, language, advanced
[Verizon Samsung Galaxy S III] daturkel:
Just flashed this the other day and really loving it. Do you guys generally keep the kernel that comes with the rom or is something else preferred?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I think a lot of us use the stock kernel. That's great performance with it too. Some try out LK, KT747, BMS, etc and have solid performance. Can't go wrong either way so long as the kernel is dated 10-19 or newer.
[Verizon Samsung Galaxy S III] ryanstfl:
I typically use a recently updated kernel for two reasons:

1) FauxSound usually isn't most-up-to-date

2) (assuming) newer = newer commits and thus probably better performance

currently running BMS
[Verizon Samsung Galaxy S III] blestsol:
I searched the thread and couldn't find info so I'll ask away. Has anyone figured out how to get tethering to work properly.

I have 4G unlimited hot-spot but when I use the mobile hot-spot my Nexus7 logs off it and never logs back on. But it connects to my home wifi and work wifi. I'm currently using LK kernel. And I'm unsure if that's the issue.

Any input?
[Verizon Samsung Galaxy S III] gt43aw:
running hot

So,

i've flashed and run this for a few days. Everything works (bluetooth, wifi, mms, sms, callling, speaker, etc....). And battery overall seems much better than stock. One thing though, when I'm playing candy crush saga (haven't tried other games yet), or am in a similarly demanding application, it seems to run HOT. Much hotter than stock. It's also much smoother (i used to notice delays all the time in screen redraws, and a 3x slow down in speed of game play i dont see anymore). But it's still HOT. Has anyone experienced this? I'm on slimbean with default kernel, default governor, etc.... If you have experienced this, any suggestions on cooling it down a bit? another govenor/io scheduler? kernel?

Brian
[Verizon Samsung Galaxy S III] gt43aw:
So i tested hot spot extensively today, and it all worked. Not useful for your issues, I know.... Sorry..... I am on stock slim beans rom/kernel/etc..... I used WPA2 PSK. 8 digit alapha-numeric password.

Also tested various combinations of bluetooth this morning... works well too.....

The heat issues when playing games is weird though. I don't mean warm, i really do mean HOT.

Brian
[Verizon Samsung Galaxy S III] griz.droidx:
I remember reading something about a bug with candy crush. Or maybe candy crush with 4.3 ROMs. I love slim. But in on another ROM at the moment just to get my flash fix.
[Verizon Samsung Galaxy S III] daturkel:
after maybe three or four days now I've been getting pretty good performance with the stock kernel, which is convenient! might give kt747 a try but don't necessarily see the need for tweaking if i can continue to get good out-of-the-box battery
[Verizon Samsung Galaxy S III] tvl76:
dkp works great for me (freelunch / sio)
[Verizon Samsung Galaxy S III] kentedman:
I also use wifi tethering quite often without an issue. I'm also on stock kernel. Nexus 7, laptop and HP printer all connect without issue. WPA2 PSK.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I can't see heads or tails what caused it. There's a lot of

repeated messages in there as well as

I saw this but idk what to make of it. I think "kgsl" is a graphics driver" and this happens before the camera was opened? I see it mentioned in the same area as a few camera lines as well:

What were you doing just before it rebooted? At the end of the logcat I saw this was a kernel panic. Again, I'm a novice at reading these so someone else's input would help.

---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------

I can't see heads or tails what caused it. There's a lot of

repeated messages in there as well. I saw this but idk what to make of it. I think "kgsl" is a graphics driver" and this happens before the camera was opened? I see it mentioned in the same area as a few camera lines as well.

What were you doing just before it rebooted? At the end of the logcat I saw this was a kernel panic. Again, I'm a novice at reading these so someone else's input would help.

Edit: Well, my post got butchered. I promise this was a rational thought before it got chopped up.
[Verizon Samsung Galaxy S III] Aggraxis:
Watching video on YouTube of all things, though the link had been on Facebook, then processed via chrome before the YouTube app picked it up. Got about 3 mins in before the screen locked. Tried BMS latest... Got something random too. I went looking up the kernel not being able to page virtual address blahblahblah message and found a ton of stuff where nexus 4 people have been hating life with 4.3. I need to sit down a t a proper computer later. Just got home from a weekend at the Hosp. Baby boy #3 was born at 409 am Saturday morning :)
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm, maybe the kgsl was in reference to that then? Guess that makes sense given how it rebooted.

Congrats on the newborn!
[Verizon Samsung Galaxy S III] blestsol:
Thanks for the input.. It could be the kernel.
[Verizon Samsung Galaxy S III] kude87:
How's the signal/data hand offs in this Rom? I've always had those issues with every Aosp rom, but haven't tried this.
[Verizon Samsung Galaxy S III] WettbackMartyr:
Hand offs are no fuss on my device. Have been with Slim since 4.3 stable build 1 dirty and clean flashed using TWRP.
[Verizon Samsung Galaxy S III] Aggraxis:
Hooray for all night newborn fun! :)

Sometime between midnight or so and 5-something in the morning my phone did one of its mysterious 'hey i'm going to turn the LED green and be locked up until you pull the battery' tricks. My phone is clean flashed back to build 2 official with the stock kernel running the VRBMF1 baseband. It was just chilling on the charger when it locked up for this log entry, but the phone did this to me twice yesterday while I was on the go. I'd pull it out and PFFT. nothing. dead until a battery pull. I've got another last_kmsg that has some different messages in it than before, but it's all Greek to me. I need to find a resource to teach myself more about the kernel and these output logs.

Anyhow, just thought I'd share the data in case it helps. Also, is it possible that a particular app may be causing this behavior? If so, how should I begin the troubleshooting process?

Thanks!
[Verizon Samsung Galaxy S III] Aggraxis:
Dirty flashed back to build 1. All is stable right now. Looked at build 2 official change log, but it wasn't very helpful. Something bad happened between build 1 and build 2 for this device. Recent nightly of AOKP also performed without the weird locks and reboots. :/
[Verizon Samsung Galaxy S III] danstar:
In the last 3 months, I have had nothing but reboots and freezes where I had to pull battery to restart. Not just slimrom, but every 4.3, 4.3.1 rom I have tried. I have even odined back to complete stock and tried again. No fix. I've had to go back to running a 4.1.2 rom so my phone is stable.
[Verizon Samsung Galaxy S III] :
I can tell you all the weeklys, even 1.9 were more than tolerable...sure maybe a hiccup or two every few weeks but never a phone crash/reboot. With "Stable Build 2" even after completely wiping the phone and clean flashing, I'm getting lockups during GPS use at random. I can tell you it's moreso during the use of my iBolt Cardock app (which is nifty and I really use/need it) and sometimes with even Google Maps. The phone won't even complete a boot if it's still sitting in the dock when it goes to reboot on it's own after a crash. Very odd cause none of this ever happened with 1.9 Weekly or any of them before. I really think I'm gonna try Stable Build 1 as I read before and see how it goes. I'm not saying the Cyanogenmod kernel we switched to last minute (Slim that is, as we) is to blame, but it was a fundamental last-minute change which after months of weeklys should not have been done and then stamped "stable" IMHO. I'll admit it nets more battery life, but I look for simplicity, only the options that are useful, responsiveness and battery life.
[Verizon Samsung Galaxy S III] draexo:
Yes. Same thing here. It just occurs when backing out of menus. I just clean flashed and I am having this issue AND another:

The icons/widgets/Google Search Bar and Notification Bar are shrunk! The keyboard and wallpaper appear fine though! No idea why. I thought it had to do with the default DPI or the font. The DPI is 245 which seems to be the default. I increased the font size, which helped with the menu texts. It did not change the Notification Bar size at all. It is not really usable like this long term as it would cause way too much eye strain.

I am running stable build 2 (which seems to be most recent)
[Verizon Samsung Galaxy S III] WettbackMartyr:
245 is default DPI for Slim. For all other ROMs (for the most part) default DPI for d2 devices is 320. Try a DPI change following every step, one by one... Should solve your issue.