yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Perseus:
There are significant changes between the previous version and this Weekly. You have to do a clean install and not restore any data. Custom Kernels might make you loose data. Esp Lean Kernel makes Sprint users loose Data.
[Verizon Samsung Galaxy S III] motocrossmann:
Well, that may just explain it. I did dirty flash it over 8.2.
[Verizon Samsung Galaxy S III] dpeeps74:
Work is slow today so I'll give it a whirl and provide an update.

Same result with a full wipe...wiped system/data/cache/dalvik...still no data at all. I'm also in the office so I don't have Wi-Fi as an option but I just did a bugreport. I'll restore my nandroid and upload it. Also, it shows baseband unknown which I suspect is where the issue lies.
[Verizon Samsung Galaxy S III] dpeeps74:
Bug report attached. I know that the Website says to put it in their forum but for some reason it didn't come up for me. This is on 8.6,clean install, stock kernel, MF1 firmware with NE1 modem. Wiped system, data, dalvik, and cache. I also previously tried toggling airplane mode and the ML1 modem. In about phone, baseband shows as unknown. Restore back to 8.0 and everything works normally.
[Verizon Samsung Galaxy S III] Perseus:
Please bear with me. I am with T-Mo so I have really hard time keeping up with the names of VZW firmware updates. Would MF1 be the update you got from 4.3 and ML1 be the Kitkat Modem ?
[Verizon Samsung Galaxy S III] dpeeps74:
MF1 should be one of the last unlocked bootloaders for us, JB era I believe but no idea if it was 4.3 specifically. ML1 and NE1 are both kit kat era and in this case modem only.
[Verizon Samsung Galaxy S III] Perseus:
Thanks. Good to know. I will take a look into this.
[Verizon Samsung Galaxy S III] dpeeps74:
I'm already on MF1. You can only be on one of 2 firmwares and be unlocked. I just flash the modem. A modem can be flashed any time. There might be some gotchas on mixing firmwares/modems I'm not aware of because I've never been on the older firmware.
[Verizon Samsung Galaxy S III] AdMire:
Yeah, that's what I mean. By flashing the ROM, you're already on MF1 modem/firmware. So in that case, you just flash the NE1 modem.

I just didn't know after you flash the ROM, you need to flash the MF1 firmware package (for whatever reason) THEN the modem, if that makes sense.
[Verizon Samsung Galaxy S III] dpeeps74:
Your firmware and modem are both separate and do not change when installing a rom.
[Verizon Samsung Galaxy S III] AdMire:
Thanks. Clean flashed 8.6 just now and no data. And apparently lost my backup I made minutes before flashing. Time to find 8.0 and start over.
[Verizon Samsung Galaxy S III] Perseus:
Some Recoveries make backup on internal SD Card by Default. So you'd have to changed to External SD Card as the Default path. I'd go look for 8.2 instead of 8.0

Also please wait till tonight or early tomorrow. Jenkins is rebuilding this weekly into 8.6.1
[Verizon Samsung Galaxy S III] dpeeps74:
8.6.1 already dropped. I gave it a whirl and it appears that the same problem is there for me. No service/data. I went ahead and pulled another bug report. It seems that it's not reading the block where imei and things of that nature are stored as they all show as unknown, not like they've been wiped or overwritten. Just my guess.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Slightly off here.

Bootloader is unlockable:

ICS VRALF2 to VRALG1 4.0.4

VRBMB1 JB 4.1.2

VRBMF1 JB 4.1.2

Bootloader locked firmware, we can only flash their modems:

VRUCML1 JB 4.3

VRUCNC1 JB 4.3

VRUDNE1 KitKat 4.4.2
[Verizon Samsung Galaxy S III] dpeeps74:
Hahaha I knew you'd know that better. I can't imagine too many not being on MB1 or MF1 firmware at this point. MF1 is actually the only one I could get working when I had to fix my IMEI recently after digging through the threads and finding files last month.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I can't imagine that either. I'm still on the 8.4 custom build but might flash 8.6 to see if Mobile data fails for me too. I'm using the VRBMF1 firmware and VRUDNE1 modem as well.
[Verizon Samsung Galaxy S III] dpeeps74:
I may make a liar out of myself. My bootloader is root@android:/ # getprop ro.bootloader

I535VRALE6

I swear I flashed this MF1 firmware zip I have. Once my phone gets some charge I'm going to make sure I did. Not messing with it at 3% no matter how eager I am. None of the files I downloaded even say that version.

Don't know. This MF1 firmware zip I have has more than just a modem but leaves the bootloader alone. All beyond my comprehension.
[Verizon Samsung Galaxy S III] Blaiser47:
Read the first post here http://xdaforums.com/showthread.php?t=1788313 you have not been updating your boot loader all along, just everything else. The aboot stays the same unlocked version. With the newer firmwares additional things are locked down so now all we can do is update modem.
[Verizon Samsung Galaxy S III] meandg5:
My BT works in my car for calls and media. When I hook up my BT OBD2 device to monitor the car, that won't connect. It pairs but refuses to connect. I've tried 3 different programs. None of them will connect!
[Verizon Samsung Galaxy S III] :
Thank you so much for this rom! It's on my Nexus 7 and S3...but in reference to the S3 here, I have a Jawbone Era...I'm noticing the Bluetooth sound is delayed/clipping a bit with this latest JSS15Q build? Unlike last, it seems to be staying connected though, so we're certainly improving!
[Verizon Samsung Galaxy S III] samsgun357:
Maybe move all the stuff you don't want to lose to ext SD or a PC and format SD. Then flash the ROM, do a backup and see if its still so big.

Eat Play Google
[Verizon Samsung Galaxy S III] Stolly08:
Thank you! This worked!
[Verizon Samsung Galaxy S III] DerDerBrown:
Your welcome.
[Verizon Samsung Galaxy S III] hexcorev2:
Dirty flash from week 2 to week 3, everything is running smooth.
[Verizon Samsung Galaxy S III] TokedUp:
Seems like the ppl using TWRP are having issues. What does TWRP have that's worth all this trouble? I've never tried it and was wondering if I should.
[Verizon Samsung Galaxy S III] samsgun357:
The functions of it are pretty much the same but it has a nice UI. I still prefer cwm touch. Never had issues with it so I'm good!

Eat Play Google
[Verizon Samsung Galaxy S III] droidxxxxx:
I tried both, and still same problem..only a fresh Odin and start from scratch fixed it. I'm on twrp again and all is good. I like them both, but twrp is more useful in my opinion. I don't think my problem stemmed from what recovery.
[Verizon Samsung Galaxy S III] dunlap92:
Settings...advanced options....device...hepatic tab
[Verizon Samsung Galaxy S III] gadgetguy08:
Formatted the SD, clean Flashed. Nandroid is around 4 gig (better than 6-7 gig) -- but still about 2x larger than 4.2 ROMs.
[Verizon Samsung Galaxy S III] samsgun357:
This is very strange, I don't know why your backups would be larger on 4.3. I'm going to keep investigating this.

Eat Play Google
[Verizon Samsung Galaxy S III] RayMcGrath:
I just checked my slim 4.3 nandroid backup and it's only 1.17 gig.
[Verizon Samsung Galaxy S III] samsgun357:
I just made a backup, I have 63 apps, between system and user in my app drawer, no games though, and my backup was just over 1gb.
[Verizon Samsung Galaxy S III] m_s_ifland:
I am using CMW, I have 250 apps and my backup is 2.7 gigs.
[Verizon Samsung Galaxy S III] tvl76:
84 apps, my backup is 1.19 g
[Verizon Samsung Galaxy S III] Wi1son:
FYI - Operation Killjoy seems to work well on my Verizon S3 i535.

Latest Test Version
[Verizon Samsung Galaxy S III] PsiPhiDan:
I use TWRP and have zero issues.
[Verizon Samsung Galaxy S III] TheBurgh:
What scripts are you running? Want to give it a go but trying to narrow things down.
[Verizon Samsung Galaxy S III] samsgun357:
Holy **** that's a lot of apps! I frequently go through and delete apps I'm not using, I can always redownload them.
[Verizon Samsung Galaxy S III] dpeeps74:
Ah, which is just what I seemed to find when I just reflashed MF1 firmware. Makes more sense now that I'm actually paying attention to it and re-read that.

So I've been looking at the logs I provided. Does the RIL interact with qcom-common? Wondering if that's the case if maybe that's not where part of the problem is since both were updated. Just trying to be helpful.

Well hell, seems it's working for some. Is anyone here able to use 8.6.1?
[Verizon Samsung Galaxy S III] Fivecent:
So I'm trying to go from 7.8 to 8.6.1 and I can't get GPS to survive a clean or dirty flash. I've been going through the process I always do; Get GPS lock, reboot to recovery, factory reset, flash ROM and Gapps, reboot system.

When 8.6.1 comes up, it will not find any GPS sats. I'm not saying that it won't lock, it just won't even recognize that there are satellites around period.

No bueno as the rest of the ROM seems to have solved a lot of other problems I was having.

P.S. It was running just fine on the BMB1 firmware. Made and received calls.
[Verizon Samsung Galaxy S III] dpeeps74:
Well, maybe my phone is an anomaly with the new build. I tried other things like airplane mode, reboot, clearing cache airplane mode off...global vs lte with reboots. Hope it can be resolved but 8.0 runs flawlessly so that's where I'll remain for now.
[Verizon Samsung Galaxy S III] dpeeps74:
I don't really know but a cm11 user is saying that he can't get a lock unless he unplugs his aux cable apparently. If you have headphones or an aux cable plugged in it may be worth trying. His thread is in Q&A and he appeared to try most of the normal solutions. It definitely seems most of the problems out there cropped up from cm changes.
[Verizon Samsung Galaxy S III] Blaiser47:
I get same thing, no service, no data, shows unknown for baseband. Bug report here https://www.dropbox.com/s/fm29snuao60lbd6/bugreport.zip?dl=0
[Verizon Samsung Galaxy S III] Fivecent:
I never had anything plugged into the headset jack. That's a really bizarre fix though and I'm not sure how it could work, but hell, I'll try it.

That's really interesting because I've been running on the BMB1 firmware after having run into the glitch in this thread [Q] SMS won't send. Can receive/send MMS calls and Data

I initially flashed 8.6.1 and Gapps, then wanted to try an upgrade to newer firmware to see if it would work so I flashed the MF1 AIO and then the NE1 modem afterwards in the flash-queue. When the phone booted I had no service and the baseband said "Unknown" I thought I just had a bad zip of the NE1 modem. I did a nandroid back to my 7.8 and downgraded back with the BMB1 AIO then re-flashed and the radios picked up just fine and the baseband was reported accurately (this may require a reset after first boot, I can't 100% recall). I can confirm that the BMB1 baseband has been functional on all of the other CM roms I've tried up to this point, maybe it would work for you?
[Verizon Samsung Galaxy S III] JOLiu:
Hi all, I've read through a bunch of pages, including the SlimROM website but can't seem to find the information I'm looking for.

I currently run the Bonestock ROM (running TW 4.1.2) and was looking at AOSP ROMS. I have tried prior versions of CM10 and CM11 but there were always issues - the volume defaulting to max volume, BT not working/disconnecting/reconnecting, battery life being terrible, cell reception issues, etc.

I have no issues w/ the TW ROM and I can easily go a full day w/ my work push e-mail going all day. It seems like there continues to be issues w/ CM11 and so I am considering Slimkat.

My questions are these:

(1) which version of SlimKat is the most stable such that I can use it as a daily driver w/o having to reflash every week or two weeks? Should I be using Stable 7.0 or one of the 8.0 weeklies?

(2) what bugs can I expect? I do need BT, wifi, SMS/MMS, e-mail all working.

(2) If I go from stable 7.0 to one of the new weeklies, do I need to clean flash?

(3) Since this is an AOSP ROM, will my cell reception be worse than on a TW ROM?

(4) What kind of battery life can I expect when compared to a TW ROM? On the TW ROM, I just use the standard kernel and don't do any over/under-clocking, and I usually get a battery drain of between 4-5% per hour, depending on on-screen time (my daily on-screen time is usually around 1-1.5 hours).

I know that these are newb questions but any assistance would be greatly appreciated. Thank you!
[Verizon Samsung Galaxy S III] Blaiser47:
Hmm interesting. I'm on ne1 modem on build 8 and it works fine but no go on 9.6.1. Are you saying build 8.6.1 works with older modems then, maybe just not ne1? Maybe newer builds don't like the new modem? Suppose I could go down a modem and try 8.6.1 again but would be nice for it to work on all modems. I'll report back if I have time to try this.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
1) SlimKat stable 7.0. Stable releases are what you'll want to stick with if you want everything stable and no problems.

2a) GPS, LTE, wifi, BT all work. BUT some people on AOSP roms have been enduring the 1 sms issue. Essentially after sending one sms, all others would fail unless they reboot or toggle airplane mode. They would still only be able to send 1 sms. If this happens for you, given that you'd use stable 7.0, you would need to have VRBMB1 firmware installed in order to have working sms/mms. I had this issue for the last 7 months and I have been good using VRBMB1 firmware. There's no way to pre-determine who would be impacted, it just sucks if you do have it. Weekly 8.4 posted in this thread corrects the 1 sms issue for all firmware but I'm reading in CM threads that mms does not send.

2b) Yes, always clean flash. You do not have to clean flash, but you will be ignored if you post any bug reports after dirty flashing.

3) Depends. If you live in strong signal strength area, you may not notice a difference. I will say this, in areas with so so signal strength, you may spend more time on the lesser data speed i.e. 3g instead of 1 bar of LTE or 1x instead of 1 bar of 3g if this makes sense. AOSP just doesn't handle data as well as TouchWiz.

4) Same battery life aka nothing worse. If primarily a wifi user, expect 2-4 hours of screen on same as TW. If primarily a 3g/LTE user, expect 1.5-2.5 hours of screen on. That's all with the stock battery.
[Verizon Samsung Galaxy S III] JOLiu:
SlipSnoopOS, thank you for the detailed reply. Sounds like Stable 7.0 is the one for me. I'll give this a whirl this weekend.

Another dumb question, but it is my understanding that Slimkat is based on CM. If so, wouldn't the bugs present in CM also be present in Slimkat?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I have no idea. That's something [MENTION=3639717]Perseus71[/MENTION] would have to answer as he builds the rom. I know the SlimRom team pulls some commits from CM based on their gerrit. All I can say, based on following CM official and unofficial and Slim threads, some issues do transfer over from CM.
[Verizon Samsung Galaxy S III] Fivecent:
Please let me know the results from this. Also, when you were checking 8.6.1, were you able to get a GPS lock?
[Verizon Samsung Galaxy S III] Perseus:
Was that a clean flash before pulling the Report and NOTHING Restored ?

So far as you CLEARLY understand the distinction between TW's 4G Indication and AOSP's H+/4G, you should be good. Please always remember we are ALL Newbs at some time. You should never feel afraid to ask.

Since SlimSnoop was gracious enough to answer, I am not repeating.

I am supposed to take umbrage to that! ;) But I won't. Let's just say Internet Explorer works the fastest on Windoz 'cause its integrated. You can guess the rest. :D

Not typically. For Example, recently CM Rom's Perofomance on AnTuTu plummeted on some of the Nighties. Slim's performance has typically been upwards of 16 to 18000. Of course assuming you didn't flash anything on top of that.
[Verizon Samsung Galaxy S III] JOLiu:
Another question, this time regarding the e-mail app. Does the e-mail app that comes w/ SlimKat have the TW features such as the out of office settings, delayed sending, or priority? For out of office, I know there's an app on the playstore, but it would be even better if it was all baked into the ROM or the e-mail app.

Thanks!
[Verizon Samsung Galaxy S III] Perseus:
I don't use Email. So can't say for a fact. Try K9 Email Client.
[Verizon Samsung Galaxy S III] tvl76:
AquaMail is my preference.
[Verizon Samsung Galaxy S III] tedkord:
A couple of years ago I called VZW tech support. The guy not only could tell I was rooted, he could tell what ROM I had installed. He knew one of the team of developers who had created my ROM, but he was really cool about it. He said he had never denied anyone warranty based on rooting/romming. The only knowledgeable Verizon rep I've ever spoken with.
[Verizon Samsung Galaxy S III] Blaiser47:
Yup perfectly clean, everything wiped no custom kernel etc. Simply wiped all, flashed rom, then gapps, booted up, no service, made bug report.
[Verizon Samsung Galaxy S III] savagebunny:
Still have a camera not working which is weird. Flashed OEM over to see if the Camera driver would fix it, but even in 4.1.2 build the Camera still wouldn't load, nor would the front camera.
[Verizon Samsung Galaxy S III] Blaiser47:
OK so retried 8.6.1 on mf1 modem and data works!! So it looks like what ever the fix was to get things working in 8.6.1 doesn't play nice with ne1 modem. Haven't tried GPS yet, inside late and rainy. I'll try that tomorrow, and try to now update to ne1 and see if I lose data.
[Verizon Samsung Galaxy S III] Magicman500:
AOSP camera isn't great from my experience. Using the flash puts colored lines all over the picture. I almost want to go back to TW just for the camera, but I can't bring myself to do it.
[Verizon Samsung Galaxy S III] dpeeps74:
I just did a dirty but I can confirm that I can get signal on the MF1 modem with 8.6.1. I do seem to not be able to get a location as others are reporting. I can try to do a clean flash and grab another report tomorrow.
[Verizon Samsung Galaxy S III] Blaiser47:
OK tried location now on 8.6.1 and I confirm, GPS does not work at all. No satellites even show up, let alone lock. It's like it is not even aware there is a GPS, no comunicado. The log cat I provided before is a clean flash that had this problem. Back to 8.0 and ne1, which is still flawless. Maybe it's just best to stick on 8.0 until slimpop drops.
[Verizon Samsung Galaxy S III] lepa71:
How is the battery life and signal strength on Slim compare to TW, if somebody can share? Thanks
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I keep a nandroid of TouchWiz 4.3 on me at all times for this reason. I don't take photos often so if I travel somewhere or go to an event like a concert, I switch to that backup just for pics and videos if I know I will be taking a lot. You should too if you are not a frequent photographer like myself and others. Now if you have kids, then toss this advice out of the window :p
[Verizon Samsung Galaxy S III] Magicman500:
I've been looking at the S3 Multi Boot for this, but I haven't had the time to go through all the threads and see what the potential risks and such are.

Edit: Right on cue, there's a portal post about camera apps.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
XDA has a sense for these type of things haha
[Verizon Samsung Galaxy S III] kentedman:
Try Nine https://play.google.com/store/apps/details?id=com.ninefolders.hd3. It has everything for Exchange. Out-of-office, sync SMS, syncs calendar, tasks, and notes. Rich text compose and signature. Conversation view, pebble and Android wear support. . It's everything the mail app should be, and more feature rich than touchwiz mail.
[Verizon Samsung Galaxy S III] Perseus:
FYI All - There will be no Weekly this week. I need more time to test for the Non-Working GPS issue. It will not be fixed in time for the Weekly build tonight. I might put out a test build later in the week. But Don't consider as a weekly.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Barnacles! Seriously though, take the time you need to put out another quality build. Thank you for always keeping us involved in the process. :good::good:
[Verizon Samsung Galaxy S III] Perseus:
[MENTION=3576831]SlimSnoopOS[/MENTION]

All,

Be Kind and test this build for me.

https://www.androidfilehost.com/?fid=95747613655049091

I'd want to know if

you can get LTE despite whatever Modem or bootloader you may have.

GPS works.

You can still send sms and mms without trouble

Appreciate if you can.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I'll be flashing this tonight. I'm expecting a big phone call this week so I can't flash anything in the daytime that might affect this.
[Verizon Samsung Galaxy S III] matt_man:
I clean flashed your newest test build along with the newest beta GAPPS on my SCH-S986C (this is the Straight Talk variant of the I535 Verizon S3). I still have no data. This is with the stock modem. Here's a link to the syslog I took after booting and trying to send an MMS in the stock messaging app.

https://drive.google.com/file/d/0B_8dzo3SQO5XRGVyZURjQ09KV28/view?usp=sharing
[Verizon Samsung Galaxy S III] matt_man:
I also tried swapping out apns-config.xml with a backup from the stock ROM and I still don't have 3G.
[Verizon Samsung Galaxy S III] Perseus:
Thanks. I can't look at Google Drive now, but will look at it from home. Were you able to make calls ? If you don't have data, MMS won't work either.
[Verizon Samsung Galaxy S III] matt_man:
I can make phone calls but can't hang up an active call.
[Verizon Samsung Galaxy S III] Perseus:
Ahhh. That's a good Pointer. Thanks.
[Verizon Samsung Galaxy S III] matt_man:
If there is anything else I can do to help troubleshoot this just let me know. There are a bunch of SCH-S986C users that would love to have a fully functional KitKat ROM.
[Verizon Samsung Galaxy S III] Perseus:
There is another build I'd have. But I will have to re-host it after work.
[Verizon Samsung Galaxy S III] Fivecent:
Do you have functioning GPS? Also, another user and I reported that the radio problems cleared up if you flashed back to MB1 baseband.

I'll be testing this later today, but it world be awesome to have a second person to verify.
[Verizon Samsung Galaxy S III] matt_man:
I'm not sure it would be safe to flash a different Verizon modem on a Straight Talk phone. I didn't think to test GPS and I have already flashed back to stock. I'll reflash SlimKat after work tonight and try out GPS.
[Verizon Samsung Galaxy S III] samsgun357:
That not being able to hang up bug was an issue in build 8.4 I believe. They reverted something back in 8.6.1 and that issue was fixed. The problem I'm currently having on 8.6.1 is my phone won't go into deep sleep and no gps lock. MB1 baseband should fix the issue with MMS and SMS not sending that's if you have data of course. Looking forward to testing some builds.

Thanks

Watch, as I combine all the juice from my mind...
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I tried this test build last night and I was able to send sms, however I was unable to test mms, outgoing calls, or GPS. I will try these tonight. I was able to receive numerous calls from my home phone but I did not try dialing out due to the time of day. Even after a proper sync, I noticed my incoming calls to my S3 from my home phone all displayed as "Unknown" instead of stating the contact.

You'll want to test the newer test build from above, [MENTION=4625647]samsgun357[/MENTION]
[Verizon Samsung Galaxy S III] matt_man:
I tested GPS and found that it does not work. It looks like it can't find any satellites.
[Verizon Samsung Galaxy S III] lennyjew:
Edit: fixed
[Verizon Samsung Galaxy S III] FastEddie422:
I've been on PA for awhile now but I'd like to switch back. Can anyone tell me the last build that isn't suffering from all these issues as of late? (i.e. GPS, LTE/data, SMS, MMS, and BT all working fine)
[Verizon Samsung Galaxy S III] Perseus:
Try Weekly 8.2 or 7 Stable.

To All -

Please note, there will be a weekly coming up. This weekly may have issues with GPS (or not). That's just a headsup. Please let me know if you continue to have issues with SMS/MMS afterwards.

Do not Post a Bug Report/Logcat if you did Dirty Flash.