yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] draexo:
Have you tried the usual stuff? Factory Reset, clean install with a fresh download? Did you download the correct ROM? I bricked my S3 years ago flashing the wrong carrier's ROM onto it. (Hint: don't flash when you are half awake). I've heard that if you flash a Note ROM onto an S3 you can over volt the hardware that reads the screen interactions and fry it. You can always ODIN back as a last resort.
[Verizon Samsung Galaxy S III] Blaiser47:
Yeah i did all the normal, flashed with cwm, twrp, clean, dirty, redownloaded 3 times, formatted, installed from internal and external, 3rd party kernel was the only fix for me and since I was not the only one to have the exact same issue, seems like the kernel might just not like a few phones. I know the some of the recent cm updates to the kernel of been hit or miss for people in other threads to, not sure if those are all in the stock slim kernel or not but...

Anyway, all up and running now, just need me some bms juice i guess...
[Verizon Samsung Galaxy S III] draexo:
So it seems for some people, the stock kernel is causing touchscreen to not work?

---------- Post added at 12:04 PM ---------- Previous post was at 11:56 AM ----------

First problem:

Settings -> Interface -> Notification and QS Drawer results in

"Unfortunately, Settings has stopped."

Any ideas? I had changed things in Notification and QS Drawer settings before this.

UPDATE: Ohh... I have no sounds on incoming on text messages OR incoming calls. Sound does work as I can play music.

UPDATE 2: wiped cache and dalvik. Rebooted. Everything is fine. Must have been TiBu. I only restored a few things.
[Verizon Samsung Galaxy S III] Blaiser47:
weird, this doesn't happen to me, I can change those settings just fine..., this with a clean install?
[Verizon Samsung Galaxy S III] draexo:
Wiped cache and dalvik and everything is fine. I restored some app data with TiBu. I think that did it.

Does Google restore wallpaper? My original custom wallpaper returned after a reboot and this was a very clean install.
[Verizon Samsung Galaxy S III] kidruk:
stay far far away from TiBu!
[Verizon Samsung Galaxy S III] BattsNotIncld:
Titanium Backup has never given me issues. Just don't restore any system apps/data.
[Verizon Samsung Galaxy S III] kidruk:
You know I have never taken that route... That might have been my problem all along.

My boOped s3!
[Verizon Samsung Galaxy S III] NMEAGENT:
Ugh! I can only send 1 text per hour. I saw a while back this problem was bugging a couple of people and I seem to have gotten it. I didn't do anything new to my phone. I don't remember if there was a fix.
[Verizon Samsung Galaxy S III] wizzardeel:
Any way I can change the stock lockscreen (slide) wallpaper and/or transparency?

Thank you Slim Team for an amazing ROM once again. Running Build 4 with dkp kernel (freelunch/sio) and ART runtime and it is buttery smooth no lag at all.

P.S. In case you didn't know, if you want to kill all recent apps, pinch zoom out on the recent apps bar itself.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Potential 1sms bug fix is here. I tried it twice and it did not work for me the first time cuz I flashed the VRBMF1 firmware shortly after and the second time it just did not hold up past a reboot. I have reluctantly switched to TW to have a working phone for the time being.
[Verizon Samsung Galaxy S III] timothydonohue:
update completely borked my phone. had to revert to a backup. wish i had backed up immediately before i installed, lol. damn my trust...

update caused my phone to initially have no touch response at all. then, after a reboot, it simply wouldn't, caught at boot screen with no animation at all.
[Verizon Samsung Galaxy S III] draexo:
I use it for some app data that's not stored on cloud.

Sent from my Beanified S3!
[Verizon Samsung Galaxy S III] Blaiser47:
For everyone who has trouble with installing build 4...(won't boot, stuck at boot screen forever, boots but not responding to touch)

It seems to be the kernel. That is why it gets stuck at the first boot screen which is set by the kernel not the rom. In your initial flash, flash rom, gapps, and then kernel of your choice (I go bms), and that should work, did for me at least. Should see whatever boot screen your kernel uses and then the flashing slim logo and your all set.
[Verizon Samsung Galaxy S III] cstone1991:
Sorry I haven't been on here in a few days. My SD cards are from HTC, Motorola, Samsung, TigerDirect, Walmart, and one that I found on the sidewalk. I could see the one I found being counterfeit or just a bad SD card, but I know the others are legit. You could also argue that I just happened to get a bunch of bad SD cards, but the fact that they have worked perfectly fine in other devices tells me that is not the case. When I went looking for a fix I found TONS of threads and articles on Samsung phones corrupting SD cards, especially relating to the S3 and the Note 2. I also found numerous confirmed cases of this happening on the S4 and Note 3 despite being right around when they were released.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] wizzardeel:
Did you read any previous post where myself and another xda'er mentioned how it is kernel related and all you have to do is flash a different kernel after a fresh install?

---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------

I can confirm this. Flashed dkp after a flash install and it works great. Used to get stuck at welcome screen with no touch functionality after a long boot.
[Verizon Samsung Galaxy S III] hexcorev2:
Weird people are getting a problem I just flashed it and everything booted up fine.
[Verizon Samsung Galaxy S III] nicklovell23:
4.1 build up should fix touchscreen issue
[Verizon Samsung Galaxy S III] AdMire:
I haven't had many issues with any weekly. Just curious, when you guys flash these, do you all clean install? Like FORMAT DATA clean install? I've done that with every update and I've had pretty good luck. I know it's tedious setting up the phone every week, but I think it would help alleviate some of these issues.
[Verizon Samsung Galaxy S III] nmh5001:
Getting crazy frequent random reboots on Build 4.1. Wiped cache and system, as usual, but it was a dirty flash from 4.0. Thinking of trying a different kernel. Any recommendations?
[Verizon Samsung Galaxy S III] wizzardeel:
Anybody getting this?
[Verizon Samsung Galaxy S III] Prack:
Does anyone have a mirror to slimkat 4.1 stable? I've been trying to download it from the site for a while and it just won't go.
[Verizon Samsung Galaxy S III] dpeeps74:
It's from forward or reverse lookup. I see it too with 1 number. I haven't tried changing providers.
[Verizon Samsung Galaxy S III] wizzardeel:
I know what its from. Tried turning off reverse, forward lookup and force closing the phone app in between. No go. Ill try changing providers.

EDIT: Tried changing providers, clearing data under Phone app, still same issue. Anybody else?
[Verizon Samsung Galaxy S III] dpeeps74:
Ah, yeah, when you turn it off I would imagine that it's still in the call log. Possibly something in cache too.
[Verizon Samsung Galaxy S III] Blaiser47:
I never report an issue unless it was a clean flash, wipe everything, and format so for me this didn't fix it, only changing kennel did.
[Verizon Samsung Galaxy S III] Tylonhh:
I have exact the same issue. Did u get any solutions?
[Verizon Samsung Galaxy S III] daturkel:
not yet. also started experiencing similar issues with facebook that would go away if i cleared data but then eventually come back. i'm flashing the 4.1 update right now
[Verizon Samsung Galaxy S III] thelangosta:
So it's probably obvious but I can't find how to change the dpi and I'm certain it's in the settings somewhere. Can anyone help please because I'm starting to go cross eyed looking at this small font. Thanks
[Verizon Samsung Galaxy S III] sweeds:
You can manually edit the build.prop

I prefer to use a simple app, like this https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi
[Verizon Samsung Galaxy S III] BrUhNiGGs:
For those running kt kernel, Is the blue led issue still there after booting up?
[Verizon Samsung Galaxy S III] AdMire:
I typically don't flash other kernels but I did flash koonsez yesterday before flashing 4.1 just because and yes, the blue LED is still there.
[Verizon Samsung Galaxy S III] thelangosta:
Thanks, I'll check that out. I thought they had a setting built into the Rom and was going crazy trying to find it.
[Verizon Samsung Galaxy S III] RandomXDAUser:
Great ROM, i have 2 minor issues:

1) MMS doesn't work when WiFi is connected

2) Bluetooth metadata info (artist/track info) doesn't seem to transmit.
[Verizon Samsung Galaxy S III] Farabomb:
I dirty flashed from 3 without issues.

MMS and WiFi works fine here.

Also Dropbox works fine, just saw someone with that issue.
[Verizon Samsung Galaxy S III] eksoccer99:
What happened to

Settings > Security > Lock screen > Slider Targets
[Verizon Samsung Galaxy S III] Magicman500:
Settings > Security > Slider targets and shortcuts > Slider targets
[Verizon Samsung Galaxy S III] Sean Z:
I don't think 4.4 ROMs show metadata. I connect my phone to my car through Bluetooth and it never shows it aside from the name of the device.
[Verizon Samsung Galaxy S III] brockkk:
my mms sends fine when connected to wifi. car also displays artist or track just fine.
[Verizon Samsung Galaxy S III] ECrispy:
Has anyone had bad reception/dropped calls with Slim compared to TW? I know this depends on radios but just want to make sure. I have the VRUCML1 radios (but not firmware), 4.1 will work on that right?
[Verizon Samsung Galaxy S III] msternig:
Battery Percent Stuck

Running the latest stable 4.1 with BMS fast charge enabled and noticed that while charging (AC) my battery percentage does not change. I am currently displaying the battery as the circle and percentage in the status bar. If I take my phone off the charger and reboot, the battery percent is updated. For example, my phone sat on the charger for two hours and never changed from 59%. After the reboot, immediately it displayed 84%. Anyone else see this?
[Verizon Samsung Galaxy S III] nmh5001:
I can send on wifi, but not receive. And Play Music is rather hit and miss with sending info to my car.

---------- Post added at 01:52 PM ---------- Previous post was at 01:49 PM ----------

I always see a drop in signal and network speeds with AOSP roms. I'm starting to think Verizon is somehow wise to the fact the phone isn't on a ROM they approve of.
[Verizon Samsung Galaxy S III] draexo:
Prior to this ROM my phone would switch to WiFi when I came home. Now I'm having to manually switch it. I thought this was in all Roms. I know it's not a big deal. Any ideas how I get Slim to do this.

So far no camera or Bluetooth issues!

Sent from my Beanified S3!
[Verizon Samsung Galaxy S III] Tylonhh:
Can someone handle with this?

Spoiler content hidden.

---------------

gesendet vom Barhocker
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Spoiler content hidden.
[Verizon Samsung Galaxy S III] Tylonhh:
Thanks for your suggestions.

I posted it here because I found one other use with the same problem.

I was on ART for some month ago, but not anymore and I had several flashes after switching back to dalvik. So I'm not on ART.

So I'm not really in the wrong thread?!?!

---------------

gesendet vom Barhocker
[Verizon Samsung Galaxy S III] Sean Z:
Do you connect your phone to your car through BT? and rc and ffc works if you swap back and forth?
[Verizon Samsung Galaxy S III] jcurley:
I am running 3.0 stable (just have not had time to flash) and my Bluetooth on the car shows song title, artist info and time regardless of the music app I am running. It just doesn't show the pictures through Pandora. But everything else works as promised.

Hope this helps.
[Verizon Samsung Galaxy S III] draexo:
Blue tooth audio in car. Bluetooth earpiece also. No issues. Stock kernel as I haven't had time to mess with another kernel yet

Sent from my Beanified S3!

---------- Post added at 10:22 AM ---------- Previous post was at 10:20 AM ----------

First bug.... The toggle for mute/vibrate/sound/sound and vibrate. When I select sound and vibrate I only get vibrate.

Sent from my Beanified S3!
[Verizon Samsung Galaxy S III] meandg5:
Radio

What does seem to be the best radio to run with this ROM? Well for somebody living in the boonies in a real fringe area? Thanks, Howie:confused:
[Verizon Samsung Galaxy S III] Sean Z:
Which specific build are you talking about? And that's great! I've always worried if bluetooth works because I need it for my HandsFreeLink for my car.

Are you talking about the latest nightly build? And does camera work?
[Verizon Samsung Galaxy S III] draexo:
I'm talking latest stable build. 4.1.

I've used camera and bluetooth with no issues.

Sent from my Beanified S3!
[Verizon Samsung Galaxy S III] :
Are old features from Slim Bean still being worked on and going to be baked in? A lot of the small stuff is missing.

Things like

Can't turn off the battery indicator

Can't adjust the trigger area for pie controls

Remapping the hardware buttons on the lockscreen

Changing the lock screen background

These features aren't really make or break, but it would be nice to have them.

I do miss toggles at the top of the notification shade though.
[Verizon Samsung Galaxy S III] kidruk:
I'm actually running ktoonz. Pretty stable with great battery life.

My boOped s3!
[Verizon Samsung Galaxy S III] tvl76:
DKP freelunch / row
[Verizon Samsung Galaxy S III] wizzardeel:
dkp freelunch/sio. No flashing led issue
[Verizon Samsung Galaxy S III] dpeeps74:
Looks like we're about to be on unified builds.
[Verizon Samsung Galaxy S III] kidruk:
I really had that blue flash of death for a few minutes on first boot. Hasn't bothered me since wheatley/row.

My boOped s3!
[Verizon Samsung Galaxy S III] wizzardeel:
If you flashed 4.1 on top of 4 it will flash the kernel as well. you need to flash the custom kernel after you flash the rom.
[Verizon Samsung Galaxy S III] tvl76:
What does this mean?
[Verizon Samsung Galaxy S III] dpeeps74:
It means that d2 devices are all the same build.
[Verizon Samsung Galaxy S III] tvl76:
More specifically, where can I find the build for my gs3 ?
[Verizon Samsung Galaxy S III] MrBrady:
My experience exactly.

VZW SGSIII
[Verizon Samsung Galaxy S III] samsgun357:
I remember reading about someone having issues with the calendar. I just realized after my last install I don't have a calendar. I went into system/app and the calendar apk was there. I pressed it and it gave me an option to install but wouldn't install. Me being the savvy guy that I am, I changed the name of it to calendar1.apk and boom it immediately installed itself. Nice inverted calendar!

And for what its worth, I've never known a "clean install" to mean formatting your internal SD. That's just overkill to me. That info has zippy to do with the ROM itself. Its a different partition. Only time I might do that is jumping between aosp and TW ROMs.

Eat Play Google
[Verizon Samsung Galaxy S III] annoyingduck:
Out of curiosity, for people that experienced the non-boot issue, how did you flash your recovery? And have you ever been on the official full current firmware?

My device currently is an insurance replacement (due to an alcohol related incident:p), and I started over fresh from the current f1 firmware. Where as my old phone I flashed each aio file as they came out. I used goo manager for my recovery, not some of the other methods people have been using.

I wonder if I would have the same issues on my old phone...
[Verizon Samsung Galaxy S III] cuban11182:
Backed up my phone and copied this version to the Internal. Clean flash after doing factory reset 3 times. It's been about 4 minutes so far, hanging on boot. This is from a clean install of slim beta 2 and it's GAPPS from the internal storage.

Edit:

I waited 11 minutes and no boot at all. It's quite a pain poping off my Lifeproof Nude case every time I need to pull the battery. I wish this ROM would work on my phone.
[Verizon Samsung Galaxy S III] droidxxxxx:
Wiped..moved to SD and crack flashed from there..seems to not be hanging on restart for me. I'm actually glad I was able to learn that feature in twrp..
[Verizon Samsung Galaxy S III] Stolly08:
Now y'all are making me nervous... I got PAC to run off the external with a full wipe....
[Verizon Samsung Galaxy S III] cuban11182:
Don't be nervous, just try it. Make sure you backup your current setup beforehand. I'll wait to see if there is a cure for us that have the hang on boot gets fixed for my particular phone before i try it again.
[Verizon Samsung Galaxy S III] Stolly08:
Did it lol

Whoever said you don't need to do a full wipe including internal is a dummy...

I've always CLEAN flashed when switching between different ROMs... Wipe data twice and a factory reset... No wiping dalvik or cache...

Worked great... On 4.3 with no issue the boot screen prob only took literally 1min....

---------- Post added at 10:19 AM ---------- Previous post was at 10:15 AM ----------

Also why do I not see halo??? I really started liking it after despising it in the beginning BC of its slow laggyness but most devs have it down super smooth now, I want on here!
[Verizon Samsung Galaxy S III] cuban11182:
So yours survived a reboot? I'll try it once more when I get back home.
[Verizon Samsung Galaxy S III] Stolly08:
Reboot? You saying you put it on without issues and on a reboot it didn't work or you saying the initial boot didn't work?
[Verizon Samsung Galaxy S III] cuban11182:
Mine survived the initial boot. I setup without doing anything to the Rom except let it settle. I then tried to reboot, but it hung forever.
[Verizon Samsung Galaxy S III] Stolly08:
O snap! Well I haven't tried a second boot... Here we go... Now I am nervous lol

---------- Post added at 10:42 AM ---------- Previous post was at 10:39 AM ----------

Its still alive! Hung at the Android Alien for prob 15secs then at the Slim screen for another 15secs then back up...
[Verizon Samsung Galaxy S III] cuban11182:
I'll try it again.

Edit

Mine will not survive a reboot. To add insult to injury I just folded the plastic housing of my Lifeproof Nude when taking it off. Theres another 80 bucks.
[Verizon Samsung Galaxy S III] Stolly08:
Dang man! Weird.... Did you do full wipe including internal?

Also anyone know how to get the cLock that when you add the widget its written in blue? I love that clock on my homepage with the weather in it...
[Verizon Samsung Galaxy S III] cuban11182:
I did 3 factory resets and 2 data wipes with newest TWRP.
[Verizon Samsung Galaxy S III] Stolly08:
Dang that's so weird!!!
[Verizon Samsung Galaxy S III] Rrrracer:
Mine did the same exact thing and I thought it wasn't going to work for me; Dearborn pointed out that he had to let his sit for ~10 minutes before it would finally go, so I tried again and it worked (I didn't let mine sit that long the first try, but I bet it took at least 10 minutes so you might give it a little longer).

Hope this helps, mine has been working just about flawlessly since.

Edit: I just checked out that Nuud case because I had never seen one, they look awesome. Sorry about your luck on that :(
[Verizon Samsung Galaxy S III] cuban11182:
I let mine sit for 11 this morning. I'm done trying to get this ROM to work. I'll come back once it works.
[Verizon Samsung Galaxy S III] droidxxxxx:
I was able to get pac and slim running off the external SD card.. But I will admit it seems better running of the internal sd card..
[Verizon Samsung Galaxy S III] Stolly08:
Its working....

Trollolololol..

How bout you redownload both then try again :)
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Its on the Slim home page

Edit: I misunderstood. For all future downloads, it looks like the d2lte is residing at the bottom of the list of devices, for the Unstable 4.4 releases. I'm guessing it will be re-alphabetized soon?
[Verizon Samsung Galaxy S III] Jan1torEarl:
Preformed a clean flash of 4.1 and experienced multiple reboots, Google Maps fc's and dropped mobile data connection. Tried bms kernel with no improvement. Going back to 3.10 until i have time to play with it some more. ?
[Verizon Samsung Galaxy S III] Prack:
Had the same issue but gave it 24 hours to settle in and now I have no issues. Been using it for a few days now.
[Verizon Samsung Galaxy S III] draexo:
How clean was the flash?

Sent from my Beanified S3!

---------- Post added at 04:18 PM ---------- Previous post was at 04:13 PM ----------

One build to rule them all!

Sent from my Beanified S3!
[Verizon Samsung Galaxy S III] Jan1torEarl:
Factory reset, wiped cache, wiped dalvik, formatted system.
[Verizon Samsung Galaxy S III] tvl76:
So...... For my Verizon gs3 (sch-1535), I download from the d2lte folder, correct?
[Verizon Samsung Galaxy S III] studpuppy102:
I may regret starting this but I am new to AOSP on the galaxy s3. Besides kt747 kernel what kernel seems to be doing the best? I have the LED blue pulse when using KT747 kernel and I'm not sure how to make it stop. I seem to have a bit of battery drain relating to time without signal using stock kernel, may be no correlation there at all. DKP kernel has some type of install issue with my phone, but these two kernels seem to be the most popular. I am also running ML1 on the latest slimkat, clean install, including sdcard format
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Yes indeed my friend. I flashed it earlier today for a few minutes.
[Verizon Samsung Galaxy S III] Droid316:
Have someone or yourself text yourself that should make it stop
[Verizon Samsung Galaxy S III] cab354:
Anyone else having serious battery drain after about 40%?

This was my battery graph, the steep drop at the end is from 5-8pm with almost no usage, screen off, on WiFi.
[Verizon Samsung Galaxy S III] Prack:
Plug it in for a second and unplug it and it will stop. Or if you get an email/text or anything that changes the color of the light it will go away. I'm not sure why people still have this problem because it's been fixed for me for a long time.

kt747 is my favorite kernel right now but these are also good:

bms, found here on xda

dkp, haven't used it but have read good things.

leankernel, found on rootz
[Verizon Samsung Galaxy S III] dpeeps74:
On the latest build my led flashes during boot and then goes away. When I first flashed I put on BMS kernel and thought it was the cause but since it would go away before finishing boot I didn't care really. I found though that my phone was freaking out, hanging, laggy touches. I then dirty flashed the ROM to get the stock kernel and now my phone is working awesome. Never had an issue with BMS before so I'm not sure what the deal was. Also, led still flashes blue during boot but about halfway through turns off.
[Verizon Samsung Galaxy S III] wizzardeel:
Are you on the stock kernel? Try dkp, ktoonz or bms with other governor/scheduler combo.
[Verizon Samsung Galaxy S III] wizzardeel:
Is anyone experiencing this? I have been since Build 3: after taking a picture and swiping left to go see the photos, they are blurry unless I zoom in on them and they look clear. If I open them in Gallery, they are sharp and not blurry.

Also when I open the gallery, I think the pictures on the sdcard are black and when I try to click Details on them, I get a Force Close on Gallery.
[Verizon Samsung Galaxy S III] RandomXDAUser:
Using the latest d2lte build, I'm still not able to send/receive MMS when WiFi is connected.

I'm using PagePlus, which only has 3G, not 4g/LTE, not sure if that matters.
[Verizon Samsung Galaxy S III] draexo:
That's odd. Here's mine. No such thing with me.

Sent from my Beanified S3!

---------- Post added at 10:29 PM ---------- Previous post was at 10:16 PM ----------

Though the display is still not always turning off.

Sent from my Beanified S3!

---------- Post added at 10:44 PM ---------- Previous post was at 10:29 PM ----------

Well great.... Now the display won't turn off at all!

Sent from my Beanified S3!
[Verizon Samsung Galaxy S III] cab354:
Are we ever going to see the return of the power widget in the notification drawer?

I miss it :crying: