yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
I did a clean flash of Rom and Gapps, and I've been having a few reboot problems. Occasionally the boot will not complete. I'll do a battery pull, and then it works. I'm also getting a "systemui has stopped" message after reboot, but later the system seems to work okay.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Please let's not have a detailed discussions on Kernels here. It can be on the Kernel's thread or in a thread of its own.

This is derailing this ROM Thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kinjo1023:
That was detailed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hwy28spur:
WiFi Reconnect Issue

First, I've had this issue since Build 6.8. I was hoping a Clean Install using Philz Touch Recovery v6.48.4, which is the latest, and selected Wipe Data and select Clean to install new ROM which Formats /data, /cache, /system. I also wiped Dalvik.

Once completed I did the following:

Clean Install of Slim-d2lte-4.4.4.build.7.0-OFFICIAL-5979

I then installed

Slim_full_gapps.BETA.4.4.4.build.7.x-190

Rebooted and waited for SlimKat to boot-up. WiFi/Data both full scale. Everything Restored just fine and things are running smooth.

Then after running a few errands outside of WiFi Range, I returned home within WiFi range only to find out that WiFi had not reconnected. It tells a WiFi connection is available but will not reconnect to it. So I go into Setting and select WiFi and tried to manually reconnect. It says connecting and then goes back to Saved Connection without connecting. This same thing on other WiFi connections such as McDonald's or other open WiFi Connections.

I then do a re-boot and everything is back to normal. WiFi connects without issue and again things are fine and running smooth.

Every time I leave WiFi range and then return within WiFi range, the problem re-occurs. A Re-Boot and everything back to normal.

One thing I've always noticed when doing a Clean Install as stated above, all of my previously stored WiFi connection are still there. Same on Ringtone/Notification Tones.

With the problem I'm having, could it be something that is not being wiped/cleared out during the Clean Install process. Or wondering if it could be somehow that the WiFi Radio has gotten corrupted.

I have also tried different Kernels but again the result is the same.

Hope this is not too much of a noob question and I have searched about everything I can think of. Wondering if anyone has had this problem or have any ideas of what could cause the problem.

I really hope I can get this figured out. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Do you turn off Wi-Fi when you are out of range, it do you keep it on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hwy28spur:
Nope. Never turn it off unless flying or something like that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
I do feel that it could be one of the apps or widgets you have installed that might be interfering. Can you please freeze all the user apps you have installed and then reboot ? Or do a clean flash and do not restore anything from a backup ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hwy28spur:
I have not added any new apps for a long time. Nothing different in that respect since way before the problem occurred.

I do not restore from a file or program. When I do a clean install, everything is wiped from my phone, then I setup everything from start. I let all the apps re-download from Google Play Store.

Not for sure what you are asking me to do by "Can you please freeze all the user apps you have installed and then reboot ?" If I reboot the WiFi connection is restored. It just won't reconnect on it's own.

Hope this makes sense.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
Did you update Google Play Services?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Yes matr

Sent from my SAMSUNG-SGH-I747

---------- Post added at 10:33 AM ---------- Previous post was at 10:27 AM ----------

Edit: got it working already! Solution is to uninstall system app and install one's in the play store

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Why can't i get the google camera to work? Stucks up while taking pictures and stuff

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigfoot.kom:
Hello. You may want to try these gapps. If your not already. Hope it helps.

http://xdaforums.com/showthread.php?t=2012857
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Edit: fixed it by flashing the compatibility fix in the slim website...

Another problem, i can't seem to find Asphalt 8 in the play store... Tried wiping data/cache of play store and tried changing DPI, still none ?

Sent from my SAMSUNG-SGH-I747

---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------

Fixed it already, thanks btw, only problem is some apps are not showing in my playstore... Using slim aio gapps anyways

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] designfears:
I had problems getting a GPS signal initially. Fixed it by changing the value LPP_PROFILE = 0 to LPP_PROFILE = 1 in gps.conf located in /system/etc/gps.conf

I still get only like 7/18 lock on satellites though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brianray14:
I tried a few times finding asphalt 8 in play store to no avail. Found the apk and side loaded it. It installed and opened but I was immediately kicked out. Apparently it isn't compatible

---------- Post added at 01:09 PM ---------- Previous post was at 01:04 PM ----------

Only fix I've found to work in the past taking into account that you actually do have the space available is using lucky patcher. In toolbox, you'll see odex sys files and in ( ) you'll see more space to int
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Good thing it's not only me, I've found an apk also but i can play it flawlessly, just the play store thingy is the issue, thanks for reproducing the problem btw

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KefkaticFanatic:
I get the same issue with Candy Crush.. oh well, at least it helps curb the addiction.... :P

For now my major problem is with nav. When starting up nav on gmaps, the whole phone will lag terribly, having a super hard time even keeping up with the location and updating it onscreen, as well as lagging to commands and touches. I've even had it outright crash a few times... is this something I should get logs for, or is it a known issue? If logs, then how would I capture logs for when it gets sluggish..?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hwy28spur:
Found my answer. I had to do a clean install and all is good now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dieselrellim:
Flashed 5.4 and its running perfectly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
5.4 running great with dkp!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GhostIsBaked:
For those who have problems with games not loading up, are you guys using Dalvik or ART?

Also, does Slimkat use the new Theme Chooser?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crewzta:
Having issues on Rogers have tried dirty flash, and clean wipe format everything etc.

Getting random reboots all the time.

I have tried restoring data apps with and without data and still getting the same issues.

I absolutely love slim ROMs anyone having the same issues?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hyewiz:
I'm on Rogers S3 I747M so far no reboots at all using weekly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grey.ghost:
So the d2lte is the same as d2att?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
D2lte is for all us s3 variants

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Judman:
Whats the deal with USB audio out? ie Samsung multimedia dock.

Is it functional within this rom? If so how?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Thanks for clarifying. In order for us to get a clear Logcat, it is necessory that you do a clean flash and don't let any app to be installed from play store. Then you can run a logcat and try to reproduce this behavior. That will help pin down the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Synthetic.Nightmare:
Actually could you pull a dmesg after it refuses to reconnect as well?

I ask because it seems like it might be this: http://review.cyanogenmod.org/#/c/69771/

EDIT: reworded so it didn't seem I was trying to go over what Perseus said

lol sorry if it might have seemed that way. ;p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hwy28spur:
Sure I'll get back with you later since it'll take awhile.

---------- Post added at 10:27 AM ---------- Previous post was at 10:26 AM ----------

Sure I'll do this as well. May take a bit of time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hwy28spur:
Which is the best app to do this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Synthetic.Nightmare:
I recommend syslog: https://play.google.com/store/apps/details?id=com.tortel.syslog
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
It did not appear that way to me. :) Glad you traced it to a in progress commit.

+1 ^^
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
I redid the clean flash, and the issues seem to have gone away. I had restored my copy of Spirit Rom and clean flashed from it. I guess maybe there was something screwy with the first one. If at first you don't succeed...

Update: While I haven't had any boot issues since the clean flash, I am in fact still getting the "systemui has stopped" message. It appears to occur when I undock the phone. I keep it docked at my work desk, with KK Widget (a hybrid of Dashclock) running in Daydream. It doesn't happen all the time, but sometimes when I remove the device from the dock, I'll get the message. After I close it, the system will revert back to the lock screen. I'll unlock, and it seems to work okay.

I've had dock issues with CM-based Roms, e.g. Carbon and Spirit, where the phone won't ring on an incoming call, though it will vibrate. When I try to answer the call, neither can I hear the calling party nor can they hear me, though the phone app indicates that the call is connected. Thus far, that issue has not occurred with SlimKat, though this one has arisen.

There must be some oddities with KitKat and Galaxy S3 docking. Strange.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Try to hit Home screen before undocking.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
Just gave it a shot. I run Action Launcher, and this time, it generated the message that Action Launcher had stopped. It then displayed window to select a launcher. I re-selected it, and it came back up. Still something odd.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Launcher is not persisting in Memory. That indicates you running out of memory. Any chance you are doing any Kernel mods ? Specifically Governor Mods ?

Add the following entry to your Build.Prop with Build.prop Editor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
I had run BMS, but not since re-flashing. Sometimes with 3rd party kernels, I'll undervolt a little, but generally not with Slim, since settings (via Rom Toolbox) don't survive a reboot. I'll make that setting and report back. What does it do? Thanks for the help!

Update: I've rebooted twice since making that change to Build.Prop, and I now get both the systemui and launcher messages on reboot. After closing the messages, it seems to work okay.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Has that setting survived reboot ? It prevents launcher from Crashing.

There are some bugs with Daydream. Check if turning that off helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
It survived. I haven't had any issues with Daydream until recently. Maybe newer Rom versions are hosing it up. I'll try disabling for a while. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
If that does the trick then please run me a logcat from before the FC happens to just after FC happened.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chiquito3:
I'm wondering if there is any way for me to mod the keyboard of this rom to be like the one on the S4 or the Note 2 with the line of numbers on top of the keyboard?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brokeddid It:
Follow the instruction in that thread's OP for install. Over 100 keyboards

http://xdaforums.com/showthread.php?t=2387785
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] diakonos:
Where do I find settings to manage WEA (wireless emergency alerts) messages in SlimKat? I went to the SMS Messaging settings and did not see the Emergency Alerts option as described on the AT&T FAQ page for Samsung ( http://www.att.com/esupport/article.jsp?sid=KB422723#fbid=7_TabJcBW9G). I received an amber alert last night about 1:30am and today cannot find a way to choose which alerts to receive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krycus21:
There is just not a menu item for the setting, This is the only way I know how to change it

Download Google hangouts > Settings > Wireless Alerts > Settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] todorcim:
Two questions for you guys #1 is this compatible with the Canadian bell s3?

And does it have Bluetooth internet tethering?

I don't own a s3, this for a friend of mine who I've finally convinced that touchwiz sucks and custom Roms are the way to go. I'm normally in the n4 threads, so looking around in these thread is kinda confusing.

Any help would be greatly appreciated

Thanks guys
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Absolutely it is compatible with all the major Canadian carriers.

Not sure about bluetooth tethering. WiFi works for sure on Rogers, so I would assume it works on Bell, but have never tried Bluetooth tethering.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] todorcim:
Trying now with philz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] diakonos:
Found I also had to make Hangouts my default SMS app to allow access to the settings I needed. Thanks. (I reset back to default SMS afterwards)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevefxp:
Just installed the stable 7 version but I cannot seem to activate Wifi. Anyone having issues?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evolver10:
Yeah, WiFi was broken with lean kernel 9.8 and 9.9. Went back to stock kernel and fixed it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JaylanPHNX:
If you're going to use a third party kernel, you need one that's been updated (for moduless WiFi) in the last couple weeks. I know Quantum works.

From my Tab Pro 8.4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CanuckinPA:
Just flashed it on my S3 -- like what I see here.

One question -- can the lockscreen wallpaper be changed to something different than the homescreen image?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JaylanPHNX:
No, not without something like Xposed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ansh4friend:
Front camera in whatsapp not working properly

Awesome rom, i love it, but i am facing a problem. front camera in whatsapp doesn't work properly. it is not smooth. anyone facing this issue?

any solution?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
That's a Whatsapp issue I believe. Try some other app like snapchat t osee if you can reproduce the lag.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
New weekly is up.

http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1185-d2lte
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
........and performing flawlessly for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fr3d0x:
Slimkat the best rom,7.2 working good
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
I now encounter an issue, both with clean-flashed 7.0 and dirty-flashed 7.2, that "Unfortunately, the process com.android.systemui has stopped." Usually this happens at reboot, and I acknowledge the message and continue, with the system loading the home page without further issues. It just happened again, and the screen went blank, though the wallpaper still appeared. I was able to reboot, get the message again, and continue. I've also found that if I don't acknowledge the message before the screen times out, I have to do a battery pull. Does anyone have insight as to why this is occurring and how it can be remedied? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Are you booting after rom zip or after rom and gapp zip? I cleaned flased 7.2 with no problems at all. Very smooth and fast.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
It occurred with 7.0, when I clean-flashed both rom and gapps. It happened with 7.2 when I dirty-flashed rom only, did not re-flash gapps. Don't think that's the culprit based on the former action. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Just thinking of flashing the Rom only and see if it gives the error without the gapps??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
I somehow seems to have did something wrong.

I have been flashing various custom ROMS (CM11/Slim/Task/TW ...) But just couple days ago, I noticed this issue.

I flashed Dirty Unicorns and noticed signal drop at regular interval. Thought it is due to DU. moved to Pac ROM, same pattern

Now a few hours ago, flashed slimkat 7.2 I still see the same issue (as you can see from the battery screen shot. at exact regular interval, signal gets dropped

(i get black triangle for a few seconds to minute or so) and signal comes back on its own.

I tried various APN settings as well. Can someone guide me, what did i do wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
I'm not the dev, however without a totally clean flash there is no way any of us can help you, there are too many variables.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
I thought, I made it clear from my posting. I HAVE BEEN DOING CLEAN FLASH ALL ALONG.

Complete wipe everything, before any new ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
What recovery? Any aftermarket kernel? Any xposed modules? Wipe system cache and dalvik every time? When was the last time you fully wiped data?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
TWRP latest

No aftermarket kernel at all

I usually use xposed. But also tried without any xposed, still same behaviour

Yes, Systemcache/Dalvik Cache wiped every time

Full data is not wiped during these installs. (I last wiped data may be 5-6 days ago)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
Again I'm not the dev but you've definitely got something going weird, eh? Any battery saving apps like greenify or anything? Dev will probably want a log and, I suspect, for you to nandroid, wipe data, clean install, and verify that it persists. Can't hurt regardless.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
As I mentioned already, DID everything again and again. In fact the last flash, I even formatted sdcard. Still the same
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
Sorry then. You said you hadn't wiped data in 5 days, from my perspective that isn't a full wipe. I guess I misunderstood you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
May be time to Odin stock and start over......pain but it may clear your problem?????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
I may give that a try today if I get a chance. I've gone back to Spirit for the time being to avoid the error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Yes, you will have to battery pull if SystemUI FCs. Please wipe dalvik and cache after the flash but before rebooting normally. If that continues, please see what system apps you are installing or restoring.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
I'll give it a shot. I don't think it's the system apps, because I run the same apps with Spirit Rom, and I'm not having the issue with that Rom. Thanks.

---------- Post added at 02:13 PM ---------- Previous post was at 01:14 PM ----------

Well, I had an odd situation. I backed up Spirit Rom, restore SlimKat 7.2, then performed a factory reset, cache wipe, and dalvik wipe. When reflashing the Rom, the system started to boot up on its own in the middle of the flash. I did a battery pull to stop it, restored Spirit, and booted.

The only other time I had a similar boot situation was when my data directory got corrupted and the system wouldn't complete a restore, starting to boot before the restore was complete because it couldn't restore data. In that case, I used Odin to flash the stock firmware and was able to restore. That's not the case here, because I was able to restore both Roms.

Should I try to re-download 7.2 and flash again?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Yes. But do a Factory reset first from within the Recovery. Remember to wipe Dalvik and cache after the flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
I did a factory reset from within recovery prior to flashing. I never got to "after the flash", since the system started to reboot on its own prior to that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Could have been low battery or bad download.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
Wasn't a low battery. I'm trying again, but the one I flashed is the same one that I had successfully dirty-flashed over 7.0. Odd.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
May be it was the Flux Capacitor or the Cosmic rays. :D Try formatting /system and /data before flashing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
That's what I thought, too! I actually did those formats last time, when the most recent issue occurred.. I'm trying again with a new download. Rather than restoring the SlimKat backup, I'm going to just do a complete clean flash, including Gapps. Maybe my device is possessed by daemons, or demons. That might explain why it works okay with "Spirit" Rom, huh? ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
You know what ? Do one thing for me. Get the DiskInfo app or something similar. Find out your Current Partition File System type. Make sure its EXT4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
I'm restoring missing apps from Titanium now. If the clean flash eliminated the problem, should this still be done? Thanks.

Update: I downloaded and ran that app. Yes, the type is "ext4".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
I just wanted to check in case that was the issue. Considering you are coming off of stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
Just rebooted, and got the systemui message. Maybe it's something I restored from Titanium, but they're the same apps I restore for Spirit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
On Sprint they have Touchwiz version of System Files. This is a primary cause of a lot of similar issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
Two oddities:

1. I didn't encounter this issue until 7.0.

2. I don't encounter it with Spirit Rom.

If it were some sort of Touchwiz system file issue, wouldn't it have occurred before now? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Depends on your Setup, the process which you used to flash prior versions and what you had Before them. Sprint Rom has made changes given 4.4. The code changes have not been fully explored yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
When I get a chance, I may try to flash a pre-7 version and see if I still get the error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fr3d0x:
there's a 7.2.1 update
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
No dice. I get the error with the earlier version, but not with Spirit.