yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] NMEAGENT:
I'm using the stock kernel. Have you clean flashed or dirty flashed? Also I know its a little old but have you tried the stable build to see if it works for you?
[Verizon Samsung Galaxy S III] Magicman500:
Another IME reboot. This time I was using Skype, if that matters at all.

http://pastebin.com/raw.php?i=BHx42483
[Verizon Samsung Galaxy S III] deuce237bblock:
Thanks this worked for me.

The only problem with this solution is it disables vibration on all instances, like nav bar, app drawer, notifications, quick settings, and what ever else the system uses for vibration.

Sent by me.
[Verizon Samsung Galaxy S III] savagebunny:
It was a clean flash, and I did the weekly flash. It's working for me now since I did those two things from the edits
[Verizon Samsung Galaxy S III] 996:
I am currently on 6.0 stable. My battery life is alright. I was wondering which kernels some of you may have flashed to improve it at all?

Any suggestions would be greatly thanked and appreciated!
[Verizon Samsung Galaxy S III] deuce237bblock:
I have been on stable 6 since it released and have tried stock kernel, KT kernel and BMS kernel and I get the best battery life with stock SlimKat kernel, but I didn't do very much tweaking with the custom kernels.

Sent by me.
[Verizon Samsung Galaxy S III] savagebunny:
I've always had great battery life with KT, DKP imo. I tweak a bit more on top of what's already tweaked for myself and get even more battery life. Remember each phone is different for the CPU gov for battery life so you just gotta play it out and see which one works best for you
[Verizon Samsung Galaxy S III] savagebunny:
I was bored, did a Dalvik vs ART storage benchmark. I don't like fake results, so both of these are my BEST ones with Dalvik and ART after running them multiple times, and having consist speeds.

Dalvik

https://www.dropbox.com/s/grhv6hyv3gaio3d/Screenshot_2014-07-20-21-07-16.png

ART

https://www.dropbox.com/s/ew6n5nnw3jb0xbs/Screenshot_2014-07-20-21-07-40.png

Kernel: KT747 7-11 Build

CPU GOV- Dance Dance (Untouched)

3072 Internal/External Size - FIFO untouched
[Verizon Samsung Galaxy S III] Perseus:
Good work. Although your second picture isn't showing the actual results like the 1st one.
[Verizon Samsung Galaxy S III] infsoul:
I. Cannot find. The weekly for. My model I swear I saw it earlier can a link be posted I have the model listed in my signature
[Verizon Samsung Galaxy S III] savagebunny:
Ya my bad, I'm mentally challenged at times. The second one I couldn't do like the first because the first one was right after the run. I'll do the same pics now

Dalvik- https://www.dropbox.com/s/saidi0xtgpls81e/Screenshot_2014-07-21-08-15-05.png

ART - https://www.dropbox.com/s/l8686mely8ioem0/Screenshot_2014-07-21-08-15-23.png
[Verizon Samsung Galaxy S III] Perseus:
All S3 varients are merged into D2LTE. Please use the links in OP.

Bummer. Firewall blocked Dropbox where I am now.
[Verizon Samsung Galaxy S III] savagebunny:
Since I'm bored and nice, here's imgur for your needs lol

Dalvik

ART
[Verizon Samsung Galaxy S III] Perseus:
Good comparison. Thanks for rehosting.

Be kind and use HIDE tags.
[Verizon Samsung Galaxy S III] savagebunny:
Used the tags, forgot about using those. All hidden.

Ya Mine was the same way, I just let it keep booting. Guess just a long setup, but boots fast now after letting it settle
[Verizon Samsung Galaxy S III] Perseus:
Please use the app Startup manager and see for yourself how many apps want to start at boot. Half of them probably won't need to start at boot. If you uncheck there, it doesn't mean the app will be frozen. You can still manually lauch it just fine. Its just that your boot time will be improved.

Not proven but you might just might get slightly better battery.
[Verizon Samsung Galaxy S III] savagebunny:
Ah I was speaking in terms of the initial boot right after installing the ROM. After 1 reboot it was normal. Gonna go into Startup manager and see what I can disable, I've noticed my phone is pegged to 1512 Mhz for about 2 minutes into booting
[Verizon Samsung Galaxy S III] Stolly08:
Yessir stock Samsung battery! Hour anda half screen on time... All data.. No WiFi...
[Verizon Samsung Galaxy S III] annoyingduck:
I forgot to mention to reset it to calibrated it after you enter the date
[Verizon Samsung Galaxy S III] Droid316:
What's the difference between this and the one Cordell makes
[Verizon Samsung Galaxy S III] juancaperez2000:
Cordell is not longer the d2vzw maintainer, he has a different device now
[Verizon Samsung Galaxy S III] jakereeves31:
You really asked this in both threads? Smh...
[Verizon Samsung Galaxy S III] Droid316:
Aww is your feel good hurt?

I so sorry for asking twice.

I'm new to slim so I wanted to make sure.
[Verizon Samsung Galaxy S III] Stolly08:
Anyone know how to make the keyboard quit vibrating when I type?! This is my first Slim ROM and the settings are a bit diff then my normal ROMs like PAC and Liquid Smooth etc...
[Verizon Samsung Galaxy S III] Droid316:
I think that's usually settings in the keyboard your using.
[Verizon Samsung Galaxy S III] droidxxxxx:
For some reason on this new version it loads and everything goes good as soon as I try to restart it it hangs so I'm back to the previous backup I made. I upgraded to the new TWRP and tried putting the files on the SD card before installing after a good clean wipe but still no luck with this one
[Verizon Samsung Galaxy S III] Droid316:
I use quick boot to reboot/recovery it does it so much faster than hitting the power button and rebooting, try using this program from the market

Sent From My Galaxy S3 Powered By Zerolemon 7000mAh
[Verizon Samsung Galaxy S III] jakereeves31:
Yes, I hate you.
[Verizon Samsung Galaxy S III] meandg5:


---------- Post added at 12:55 PM ---------- Previous post was at 12:53 PM ----------

Why don't you two start your own love/hate thread! Just saying!
[Verizon Samsung Galaxy S III] Droid316:
We're just busting balls.It's all good.

Sent From My Galaxy S3 Powered By Zerolemon 7000mAh
[Verizon Samsung Galaxy S III] Stolly08:
And where do I go for that?
[Verizon Samsung Galaxy S III] annoyingduck:
Settings/sound/vibrate on touch...

---------- Post added at 01:18 PM ---------- Previous post was at 01:16 PM ----------

Best post in this thread hands down. Sarcasm, truth, who knows? Perfect.
[Verizon Samsung Galaxy S III] Stolly08:
Its unchecked.... It doesn't vibrate when I press anything else like an app etc only during typing....
[Verizon Samsung Galaxy S III] uberbdon:
Anyone...? I can't be the only one using Cerberus.
[Verizon Samsung Galaxy S III] jakereeves31:
Never heard of it. Haha
[Verizon Samsung Galaxy S III] imjehh:
Anyone else having trouble using AC!D soundmod and Noozoxide addon with this 4.3? They work fine on slimbean 4.2.2 but on 4.3 I get a force close from noozoxide...
[Verizon Samsung Galaxy S III] Jayydude_SGP:
Somehow I lost root access and can't change the phone's DPI for some reason... Help?!?
[Verizon Samsung Galaxy S III] RedRumy3:
Got a quick question anyone know why my Gmail isn't loading any pictures?

I attached a screenshot
[Verizon Samsung Galaxy S III] nicklovell23:
Can someone using TWRP thats having slow boot times flash and test this build and shoot me an email with the results.

Email is: nicklovell23@gmail.com

rom download:http://d-h.st/L26
[Verizon Samsung Galaxy S III] savagebunny:
Weird, even with me stopping apps from Start Up, my phone still takes about 2-5 minutes to boot up, depending on what it feels like doing. Not sure what's hanging

on the 6.4 weekly, latest KT 7-11

EDIT: Well, I have no idea what's going on, the phone just keeps hot rebooting now. After I did the KT747 flash, thought it was the kernel causing the hot reboots, threw DKP back on it, and it never changed the boot.img which was weird. Now running 6.6 right now, and the phone still fails to boot sometimes, and then I gotta pull the battery.

EDIT 2: Noticed that it hot reboots when I just now unplugged the charger off the wall charger, and computer... Weird
[Verizon Samsung Galaxy S III] motocrossmann:
Has anyone had a problem with Bluetooth phone book access? My phone connects fine to my car for audio purposes, but the phone book in my car only can access a partial list of contacts from the phone. My car is one of those models where it accesses the contacts "on demand", and does not store them in the car's memory. Previously this had been working fine on other roms. I have tried moving to the most recent weekly build, but the problem still persists.
[Verizon Samsung Galaxy S III] Perseus:
Have you guys turned on Download Attachment option in Gmail settings ?

Do you have any Kernel related tweaks applied ? Also can you take a backup and the do a factory reset ? Don't restore anything but just check if the reboots persists. Typically these are caused by some runaway app hogging Ram and writing somewhere it shouldn't. that is if you don't have any CPU Frequency or Voltage mods.

Just tested with 2 different vehicles. No issues. Unpair the phone from the car. This should be done on phone as well as car. Then reboot the phone and pair the phone again. This time wait full 3 minutes after the phone has paired. In those 3 minutes, there will be a popup requesting permission to allow the car to access phonebook. Say Yes to always allow.
[Verizon Samsung Galaxy S III] savagebunny:
I was dumb and didn't make a backup as usual, but since I went from TW to AOSP, I'm assuming some files were still lingering. I have now flashed 6.6 on it, and I upped my voltage by 25 across the board via trickster cause I think with this ROM it didn't like it this low how I normally ran it. I made a Nandroid backup now too. But to answer your question, nope no kernel tweaks. Just the upped voltage by 25mV
[Verizon Samsung Galaxy S III] Perseus:
Extreme undervolting will cause reboots. Any large resource intensive apps will cause reboots on even smaller undervolting.
[Verizon Samsung Galaxy S III] savagebunny:
Ya I'm just monitoring it right now and seeing how it goes. Right now it's going good on the stock 2100mAH battery. Once I know it's good gonna throw my ZL in.
[Verizon Samsung Galaxy S III] :
I looked and i have Download attachments to when I'm on wifi always since i am always on wifi

images: always show

I've even tried it when i said to prompt me to download and still nothing.
[Verizon Samsung Galaxy S III] Perseus:
I just tried and can't reproduce. Please post on the Gapps thread.
[Verizon Samsung Galaxy S III] Perseus:
If that were the case, there would have been a flurry of reports here. As I said, I wasn't able to reproduce either.
[Verizon Samsung Galaxy S III] savagebunny:
I'm on 6.6, checked my gmail and its loading my attachments and rendering my HTML newsletters. Also that hot reboot I would get, it would only happen on Dalvik which is weird... On ART and no hot reboots. Only downside is Camera is broken still on ART
[Verizon Samsung Galaxy S III] RedRumy3:
Weird how my Gmail is not displaying any images just shows a broken image icon instead. I did a clean install and installed full gapps as well and nothing still :'(
[Verizon Samsung Galaxy S III] savagebunny:
I'm using the mini gapps install too for myself. After you installed the gapps, have you updated gmail and Google Play Services?
[Verizon Samsung Galaxy S III] Farabomb:
No image/attachment issue here.

Still random reboots but I'm blaming that on waze.
[Verizon Samsung Galaxy S III] dpeeps74:
I haven't been keeping up with the thread much but if you can't load Gmail attachments are you running an ad blocker or is your hosts file being modified by some app?
[Verizon Samsung Galaxy S III] jonny30bass:
I think I found out what was making SlimKat take so long to boot for me. I think that it is related to the dpi setting. Before changing the dpi it would take roughly 10 minutes to restart my phone. Then after I changed the dpi to 320, it only takes around 1-2 minutes for it to boot.

---------- Post added at 09:13 PM ---------- Previous post was at 08:48 PM ----------

What's wrong with your camera on ART? It seems to be working just fine for me on ART. I'm using the stock SlimKat kernel though.
[Verizon Samsung Galaxy S III] RedRumy3:
I haven't touch adblock or host file yet just a clean install with rom and gapps and my gmail isn't displaying any pictures at all. Newegg, bestbuy etc etc just shows broken image icon. I am trying another 4.4.4 rom to see if it still does it. Rom is so good to just this gmail issue driving me crazy lol.

install cm11 4.4.4 and its loading gmail so I am going to try another install of slimkat

installed slimkat again and still same issue oh well I guess I will just deal with it for now lol.
[Verizon Samsung Galaxy S III] Fivecent:
Any repositories for older version of slim? I've been running into a lot of strange problems on 4.4.4 even after multiple clean installs. I had a lot better success on the 4.4.2 builds, but the download repository only goes as far back as the 4.4.3 weeklies.

If anyone could point me in the right direction I'd really appreciate it.

edit: Tried the 6.6 weekly just in case and the issue with the stock browser not being able to access Google sites has returned.
[Verizon Samsung Galaxy S III] infsoul:
Anyone know of a way to get smartscreen for pausing when you look away and sysyingvon while your viewing
[Verizon Samsung Galaxy S III] jonny30bass:
F2FS Support?

Does this ROM work with F2FS? If so, how do I do it?
[Verizon Samsung Galaxy S III] AdMire:
I may have to look into that because it's getting old with these 10 min reboots.
[Verizon Samsung Galaxy S III] jonny30bass:
If you want to change it, use an app called Root Browser and edit the build.prop file that's located in /system. It's the only way that I could change the dpi because all other 3rd party apps did not work when it came to changing the dpi.
[Verizon Samsung Galaxy S III] Perseus:
the only repository is

http://slimroms.net/index.php/downloads/dlsearch/viewcategory/440-oldreleases/downloads/dlsearch

Can you try Last Stable of the SlimKat ? If that didn't work, go to the one before that.

What happens when you access Gmail with a Browser like on a PC ? Never mind the Gmail app.

Yes it does. Unfortunately TWRP hasn't released F2FS Support. Well v 2.7.1.0 is supposed to support it, but at least not on my D2TMO.

I am checking on CWM and Philz. Will be back.

To your Suggestion/question with reagards to the Long Boot times, Can you please elaborate on the DPI Changes ? Are you saying that after DPI Changes, it takes long to boot ?
[Verizon Samsung Galaxy S III] RedRumy3:
Pc no issues loads images fine. SlimKat for some reason is not loading images in my Gmail. I tried CM 4.4.4 and it loads images in Gmail App fine so I don't know why it's not working in SlimKat :confused:Hopefully it gets fixed somehow from a new weekly if not oh well I will just deal with it for now.
[Verizon Samsung Galaxy S III] Perseus:
I meant use a browser on the phone and go to gmail.com. Log in there.
[Verizon Samsung Galaxy S III] RedRumy3:
Oh it loads fine with browser.
[Verizon Samsung Galaxy S III] jonny30bass:
I'm saying that on the default dpi of 245 it takes forever to boot. However, with a dpi of 320 it only takes a minute or two to boot. It could just be a coincide that it started to boot up a lot faster after changing the dpi to 320, but i haven't tested the theory by changing back to 245 yet.

Oh and I use PhilZ recovery. If it supports F2FS could you let me know how to use it?
[Verizon Samsung Galaxy S III] Perseus:
Are you really sure,

Good to know. I never had boot problems. So I can't very well test it. Would you mind going back and see what happens if you go back to 245 ?

Yes I will let you know what happens with Philz. As of now, TWRP only supports EXT4.
[Verizon Samsung Galaxy S III] RedRumy3:
Looks like im having the same issue as this guy

http://forum.slimroms.net/topic/2362-weekly-build-510-native-browser-error/

native browser doesnt even let me go to gmail it gives me the same error he gets but dolphin browser loads gmail and images fine.
[Verizon Samsung Galaxy S III] jonny30bass:
I just went back to 245 dpi, and the boot time is still fast. So another theory is that you only need to change the dpi one time to get rid of the long boot times. The only way to test that would be to reinstall the rom. I can test it later.

And when I change the dpi, I directly edit and save the build.prop. So another theory is that you just need to edit and save build.prop once and then the long boot time will go away.
[Verizon Samsung Galaxy S III] Perseus:
So you have issue with the TRDS GMail and Stock Browser. Is that correct ? Can you please post that in [GAPPS][4.4.x] Official Slim GApps TRDS (Slimkat) [2014-07-22]

Ok Good to know. Please see bellow.

THOSE WITH ISSUE OF LONG BOOT TIMES -

I had been deeply investigating this issue for today and yesterday. I went through quiet a chore and laundry list of Scenarios. I formatted to different File System Combos, tried several versions of the Recoveries as well. I even formatted to F2FS even though I haven't converted the Rom Zip on my SD Card.

It turns out, in the end, that this could possibly be related to recovery. Also possibly related to DPI as mentioned by @jonny30bass above this one.

Will you be kind to post What Recovery and which version have you got there ? Is it possible that you have Philz or CWM ?
[Verizon Samsung Galaxy S III] jonny30bass:
I am using PhilZ 6.48.4

I honestly believe that it has something to do with the build.prop file. I tried editing it with so many different programs, but none of them would work. So then I tried to use ES File Explorer to edit build.prop, but then it gave me an error when trying to save it. Then I found the program called Root Browser by jrummy apps, and it was the only program that allowed me to edit and save build.prop. Then once I changed the dpi via that program, my boot times were a lot shorter.
[Verizon Samsung Galaxy S III] Perseus:
Let me give it a try. Next time use build.Prop Editor
[Verizon Samsung Galaxy S III] jonny30bass:
Ok so I did 4 clean installs of the latest weakly and gapps. Each time had a long initial boot (roughly 8-10 minutes). Each time I changed the lcd density, I used Root Browser to edit and save build.prop. On the first clean install I changed the dpi directly after the initial boot, and the next time I booted up it only took around 1 minute.

On the next clean install, I rebooted once before changing the dpi in build.prop. The reboot still took around 10 minutes to boot back up. Then after I rebooted once, I changed the dpi and rebooted, and it only took around 1 minute to boot.

On the next clean install, I rebooted two times before changing the dpi in build.prop. Each reboot took around 10 minutes. Then after I changed the dpi in build.prop, it only took around a minute to boot. The next clean install I waited three reboots before changing the dpi. Each reboot took around 10 minutes. Then after changing the dpi in build.prop it only took around a minute to boot.

So this temporary fix was definitely replicable for me.

I have tried using build.Prop Editor before and it didn't work, but I'm going to do another clean install and try it out. I will report back.

Update: This is what happens when using build.prop Editor:

---------- Post added at 12:54 AM ---------- Previous post was at 12:03 AM ----------

UPDATE:

Well...I just made an important discovery when it comes to the long boot times. It depends on if I choose to reboot or power off. If I choose to reboot, then the boot time is ridiculously long. If I choose to power off and then manually turn it back on, then it will boot up fast. The same goes for if I choose to reboot recovery before clean installing the rom. If I choose to reboot recovery before clean installing the rom, then the initial boot will take forever; however, if I choose to power off and then manually enter the recovery before clean installing the rom, then the initial boot will be fast. If I edit the build.prop to change the dpi, then it will reboot fast from there on out.

Edit: After further testing, my previous update no longer seems to be true for some reason. It has a mind of its own.
[Verizon Samsung Galaxy S III] nicklovell23:
johnny30bass I sent you a PM.
[Verizon Samsung Galaxy S III] nicklovell23:
Ok what I need exactly is: A complete clean flash, factory reset,wipe cache,dalvik, and format system manually. Flash rom then gapps, Get a logcat of the full boot up put it on pastebin then change the dpi to 320 get another full logcat and put it on pastebin. email me both pastebins. email is nicklovell23@gmail.com. If you can do this it would be greatly appreciated.thanks!
[Verizon Samsung Galaxy S III] Fivecent:
I had this problem before and wanted to 100% verify that this is a TRDS Gapps problem. I just clean installed the 6.6 weekly with PA gapps and this is no longer an issue.

edit: Looks like I'm completely wrong. I went from a CM nightly, factory reset in TWRP, installed 6.6, then PA Gapps, then LK 9.8 and it worked. trying to replicate now.

E2: Nevermind. I can't replicate this at all, but all I know is that I have a spare phone where this worked somehow.

E3: So I am completely baffled. I took a nandroid of the setup I had working on my backup phone, moved it over to my main phone, recovered it, and then the issue started again. I literally opened the stock browser on both phones, went to google, and watched one work while the other one didn't. The only thing it could mean is some kind of hardware issue, but that doesn't make a lot of sense...
[Verizon Samsung Galaxy S III] jonny30bass:
I made a couple splash screens to go along with this rom. I don't like when custom kernels replace the splash screen, so I made some splash screens that match the rom. I used the tool on this page to make the flashable splash screen zips: http://xdaforums.com/showthread.php?t=1927751, and I used MS Paint and Photoshop to make the splash screen images.

SlimKat Boot Logo V1:

http://www.mediafire.com/download/2td01lkdw43bqye/SIII_Boot_Logo_SlimKat_V1.zip

SlimKat Boot Logo V2:

http://www.mediafire.com/download/66cqz5l0d4x76pj/SIII_Boot_Logo_SlimKat_V2.zip
[Verizon Samsung Galaxy S III] NMEAGENT:
+1 for the bottom one with the Kat.
[Verizon Samsung Galaxy S III] savagebunny:
These hot reboots really suck now a days. Having at least 5 hot reboots a day. Verified its not low voltage to the CPU or super memory intensive apps, as I only had tapatalk opened up 10 minutes ago and it hot rebooted. I got a logcat but I don't think it will show anything :/

Changed my DPI to 320 and no change either.

https://www.dropbox.com/s/mrvb5bhatr1ahyy/Log_2014-07-25_01-24-21.txt
[Verizon Samsung Galaxy S III] AdMire:
So after doing what jonny30bass suggested, I went from the 245 to 320 and when I saved and exited, I rebooted and the phone took maybe 30 seconds to reboot. I then went into recovery and cleared cache/dalvik for the hell of it and rebooted, took under a minute.

I don't care for the big icons/text so I'm switching back but very interested test, thanks for pointing that out.
[Verizon Samsung Galaxy S III] Perseus:
Thanks for such an extensive testing. Please see Nick's PM.
[Verizon Samsung Galaxy S III] jonny30bass:
I updated the SlimKat V2 boot logo. I made the kat logo a little darker grey because on the SIII screen it looks a lot lighter in color.

http://www.mediafire.com/download/3kzo1n31ljwbwxy/SIII_Boot_Logo_SlimKat_V2.zip

---------- Post added at 09:37 PM ---------- Previous post was at 09:34 PM ----------

No problem. I want to help make my favorite rom better.
[Verizon Samsung Galaxy S III] Perseus:
Is that a Boot Animation or Wallpaper ? Sorry I have firewall problems.
[Verizon Samsung Galaxy S III] jonny30bass:
Neither. It's a splash screen. It shows up for around 5 seconds right before the boot animation.
[Verizon Samsung Galaxy S III] SwaySwayJoy:
Wallpaper

Is there a option to change only lockscreen wallpaper?
[Verizon Samsung Galaxy S III] Droid316:
Anyone else not able to get the dialer pad to come up when opening the phone app? Mine just shows the contacts but no dialpad
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Mine shows up just fine.