yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] Perseus:
What is your APN set to ? (Settings > More > Network > Access Point Names). Also check Preferred network type.
[Sprint Samsung Galaxy S III] nimaim:
I have no need for hangouts as I don't use Google talk on my phone (which drains the battery like crazy anyway). However the default messaging app only takes 160 chars before it doesn't let you type anymore (even if you tell it to force split and not send it as an MMS). I know this has been brought up before but was there a solution to this? Pretty annoying problem to have to manually send more than one message at a time. Thanks. Weekly 5.8 is rock solid for me with LeanKernel 9.7 btw.
[Sprint Samsung Galaxy S III] zman519:
I have not installed this ROM yet, but I'm thinking about it. Dose 5.6 android 4.4.2 also have this problem?

Sent from a thing running on Electrons
[Sprint Samsung Galaxy S III] wallythander:
Yeah, this is still not fixed, it is kind of annoying. It hasn't been working for a good while now. I have a friend or two who I have political debates with over text. It is hard to go on a cohesive looking rant when you have to split them up by hand.
[Sprint Samsung Galaxy S III] hayzooos:
This made me chuckle just because of the nature of your messages (I can relate), but this was an issue with Hangouts previously and I thought they fixed it a few months back, shortly after their big push to make Hangouts the default SMS app. I haven't had any issues with it recently. I'm using version 2.1.224 right now and I'm able to send SMS messages of more than 160 characters just fine.
[Sprint Samsung Galaxy S III] wallythander:
Oh no, I don't use Hangouts, I use the Messaging app. Bloviating does not lend itself to brevity. I should find a new app to use at some point, I don't like Hangouts.
[Sprint Samsung Galaxy S III] matrixzone:
Slim v5.9 weekly is up:<br />

<br />

http://slimroms.net/index.php/downl.../11463-slim-d2lte-4-4-3-build-5-9-weekly-4992<br />

<br />

Changelog:<br />

Linux 3.4.93<br />

Bluetooth/USB fixes<br />

Add color values for ease of TRDS theming<br />

fixed quick record on specific languages<br />

Telephony: Glowpad transparency setting easier to find now<br />

Updated blobs<br />

<br />

Detailed change log(for geeks)<br />

http://slimroms.net/jdownloads/slim...lte-4.4.3.build.5.9-WEEKLY-4992_CHANGELOG.txt<br/>
[Sprint Samsung Galaxy S III] hayzooos:
Nah, you were both right, I just totally misread what you guys were saying. I saw 'Hangouts' listed, then read about the problem and somehow missed the part where you mentioned it was the stock messaging app that was having the problem. Apologies!
[Sprint Samsung Galaxy S III] sixgunmojo:
Go into settings for the messaging app make sure Split SMS and Multi-part SMS are unchecked. This should send SMS messages over 160 characters as an MMS message. If this doesn't work, (I've never sent a text that long) I would try Kik, or an app like it. It is an IM app (I think) with the advantage of not having to use your phone number just a user name that you create.

Crap responded to wrong post! This is for [MENTION=3721547]wallythander[/MENTION]. Sorry Hayzooos
[Sprint Samsung Galaxy S III] Perseus:
Slimkat Weekly Release 5.9 is out.

Release Highlights -

Additional Options to Recents list.

The prior reported bug for Bluetooth and Location Service interconnection has been addressed.

Minor modifications to Dialer Settings.

Basics of Theming started.

Bug fixing on Hotplugging of CPU Cores.

Several Changes to USB Playback.

Bluetooth Support added for Quiet a lot of Devices with chipsets based on

Sony Vaio T-Series

Mediatek Bluetooth device

IMC Networks

GC-WB300D PCIe

Foxconn/Hon Hai AR5BBU22

BCM20702A0

Atheros Based devices

Support for Hardware based encryption where supported.

Updates to AAC Encoder.

Minor changes to IPV6

More Translations.

Full Change Log - Here

Rom - Here

Gapps - Here
[Sprint Samsung Galaxy S III] nimaim:
It was fixed in Hangouts but was never fixed in the Messaging app afaik. Hangouts is overly bloated for me and I don't need it (plus it will randomly sign me on to Google Talk and I won't even know about it). I guess since the default Android messaging app is now Hangouts, they won't fix the Messaging app? That would be a shame. TW messaging app works fine on TW based ROMs for very long messages.
[Sprint Samsung Galaxy S III] hayzooos:
Yeah, I made the plunge into Hangouts just because it seems to be the least of all evils since the stock piece wasn't working quite right. It's a bummer too as I used it for quite a long time. There are a slew of SMS/MMS apps out there, but all of them seem to have a ton of extra bells and whistles I don't need.

The one thing I do like about Hangouts is the ability to mute notifications on specific threads. Really comes in handy on some of those group messages you want to be a part of but don't want your phone constantly blowing up!
[Sprint Samsung Galaxy S III] zman519:
Dam this sms thing you guys are taking about is a deal breaker for me. Is there a stock app from another aosp ROM that would work. Even on 4.4.2 ?

Sent from a thing running on Electrons
[Sprint Samsung Galaxy S III] Perseus:
You can take the 4.4.2 Rom Zip file and extract the APK from there.
[Sprint Samsung Galaxy S III] zman519:
Yes I understand that. So dose the >160 work on the 4.4.2 ROM?

Sent from a thing running on Electrons
[Sprint Samsung Galaxy S III] Perseus:
I'd think so.
[Sprint Samsung Galaxy S III] solis888:
I updated from"5.4 to 5.6 yesterday, and my apps are not asking for root permission. Anyone know a fix?
[Sprint Samsung Galaxy S III] Perseus:
Did you do Dirty Flash ? If yes then this is expected. CM Superuser app will "Remember" previously granted permissions.
[Sprint Samsung Galaxy S III] solis888:
Yes I dirty flashed. What if I want to give permission to a new app?
[Sprint Samsung Galaxy S III] rambleon84:
How has the battery been for everyone else the last couple of weeks? Mine has been draining faster than previously..At 16% after 9 hours light use today (1 hour 7 min of on screen and 25min of headphone music) and that has been normal the over the last few weekly's. I havent flashed this weeks yet, will be later today after charging.

The rom itself is working bug free, not noticing any issues since going to 4.4.3 either. (i run the latest on my gf's toroplus and my flo, battery seems to be draining faster on those as well, more so toroplus than flo though.)
[Sprint Samsung Galaxy S III] Perseus:
Just launch that app. If it needs one, you will get a prompt for permission. You can see all the currently granted permissions in Settings > Advanced > Superuser

ROMs are not responsible for your battery Drain. The apps you have installed are the only ones responsible battery drain. In oter words, how you use the phone, how long is the screen on, is the Location On, etc also determine battery Drain.
[Sprint Samsung Galaxy S III] solis888:
I looked in Super user and it showed no apps as given permission. I clean flashes 5.9, and after flashing, the recovery said that root was lost and if I wanted to reapply root. Apps still don't ask for root permission. Any fix?
[Sprint Samsung Galaxy S III] kjjm:
You have to enable root in developer options when you first install Slim.
[Sprint Samsung Galaxy S III] sixgunmojo:
I think you can get away with just re-flashing the rom (dirty flash). When you reboot out of recovery do not allow the recovery to reset root. It is still there. Re-enable root the usual way. I allowed my recovery (Philz) to reset root once and it caused all kinds of weird behavior with it, pretty much what you are describing. I have actually disabled that function (check for root) in my recovery cause I got tired of having to remember to say no.. If that doesn't work you may have to clean flash again.
[Sprint Samsung Galaxy S III] wallythander:
Yeah, I don't use Hangouts, but it sounds like this problem is definitely only for the GI Joe Messaging App. Sorry, I don't mean to scare anyone who is new to Slim and reading through the posts. If I didn't like typing long ranty texts in the Messaging App, I would have 0 problems with Slim or anything that comes with it. I agree, nimaim, I find Hangouts to be annoyingly bloated. I didn't even know you could use it for SMS without being signed into Google Talk, I thought that you just couldn't use it without being signed in, which is 100% a deal breaker for me, even if it wasn't too bloated for me to use. I was thinking about GoSMS, I have that installed already as a backup, but there are things about it I don't like, namely that it is kinda fancy schmancy, I want something simpler.

Also, what is the deal with the new, as they write it on the Slim site, Addons BETA? Is it what they are going to be using for the weekly gapps updates now? I am downloading the newest under that heading, will install them with a clean install of 5.9 I plan to do later tonight.
[Sprint Samsung Galaxy S III] solis888:
Dirty flashed and said no to root check. What is the "usual" way to re-enable root?

Edit: Found it in developers options.
[Sprint Samsung Galaxy S III] sixgunmojo:
Settings > scroll down to About Phone > tap the build number about 7 -8 times to enable developer options. Back out into settings, find developer options (up 2 from About Phone) and enter. Under debugging , first choice should be root access, tap and enable root at least for apps (some enable apps and adb). Should be good to go.

---------- Post added at 11:11 PM ---------- Previous post was at 11:03 PM ----------

I poked around the site a little but didn't find any explanation. I flashed the latest (there are 2) earlier and have no apparent problems, but I use minimal and remove anything that is not the play store
[Sprint Samsung Galaxy S III] JaylanPHNX:
These are test Gapps uploaded by [MENTION=1277872]dankoman[/MENTION] (the new Gapps maintainer). This allows him to keep up with mid-week app updates. They get the beta tag because they haven't been as thoroughly tested as the official Gapps.

From my Pro Tab 8.4
[Sprint Samsung Galaxy S III] nimaim:
New weekly and beta gapps running great here with the latest leankernel. Just installed my Qi receiver to my battery too so happily wirelessly charging away with my Nokia Qi charging plate.
[Sprint Samsung Galaxy S III] kuhl_man:
Anyone else having problems with Bluetooth connecting on weekly 5.9? On 5.8 my phone would connect automatically to my car stereo but on 5.9 it searches and never finds it. I've reset all settings on both the phone and radio and still nothing.
[Sprint Samsung Galaxy S III] Perseus:
Its a known bug and reported. It will be fixed in the next Release.
[Sprint Samsung Galaxy S III] SirHustlerEsq:
Did anyone ever the address the issue where we "cannot connect to the camera"?
[Sprint Samsung Galaxy S III] Perseus:
Never had that issue. Can you elaborate ?
[Sprint Samsung Galaxy S III] SirHustlerEsq:
When I run any of the SlimRoms on this refurb phone I cannot use the camera and I'm promted "cannot connect to the camera". I tried swapping files from the OEM TW ROM with a working camera, but that does not fix the problem.

log:

http://xdaforums.com/showthread.php?p=50605662#post50605662

You can also search through my last 10 forum posts or so because they are all related to this problem.
[Sprint Samsung Galaxy S III] Perseus:
Can you tell me if you go back to Stock firmware, does the camera work ? It could be that you have different or older drivers for the camera. Going back to Stock with Odin would help. Once the Camera is working fine there, you can do a factory reset and flash Slim rom. Do not restore any backups or else the problem will repeat.
[Sprint Samsung Galaxy S III] SirHustlerEsq:
I've gone back to an OEM ROM and the camera works. Clean installs do not (factory reset, clear cache, clear dalvik, instal, clear cache, clear dalvik, boot) after switching back to an OEM ROM. Thanks for taking a look at the problem.
[Sprint Samsung Galaxy S III] Perseus:
That's indeed Curious. Are you sure you have a genuine Samsung Phone and there have been no Operations been performed on it such as hardware replacement ?
[Sprint Samsung Galaxy S III] SirHustlerEsq:
It's a refurb replaced through insurance so I assume the camera is not OEM Samsung.
[Sprint Samsung Galaxy S III] Perseus:
I'd say the motherboard won't be either. Which is why the Rom's drivers are not working. Have you tried another AOSP Rom such as CM or C-Rom or LiquidSmooth?
[Sprint Samsung Galaxy S III] SirHustlerEsq:
Yes, I tried probably 7-8 different ROMS, all with the camera problem. I'm back to my status of "given up". I plan to get a Nexus 6, whatever that may be.
[Sprint Samsung Galaxy S III] Perseus:
I had seen other cases where insurance replacements were Frankenstein phones with some other motherboard. You want to ask them about this.
[Sprint Samsung Galaxy S III] *BTK*:
nd8?

Still new to the s3. Can I flash on nd8?
[Sprint Samsung Galaxy S III] sixgunmojo:
As long as you have an up-to-date custom recovery (Philz, CWM, TWRP, etc) you may flash any rom you want. What you cannot do is downgrade your bootloader (usually done with odin), and until further notice you probably want to stay away from flashing modems.
[Sprint Samsung Galaxy S III] hayzooos:
Does anyone here use ART as their runtime over Dalvik? Just curious as it seems like that's going to be the standard in AOSP moving forward, so wanted to see if anyone using Slim on Sprint S3 has done so already and any thoughts around it.
[Sprint Samsung Galaxy S III] zhiwlin:
Using ART now, working well. Everything seems to work.
[Sprint Samsung Galaxy S III] hayzooos:
Thanks for the response. I tried it for a bit, and it seemed pretty slow and lagging (although, I'm still running 5.4 weekly w/ stock kernel) so I jumped back to dalvik. Just wanted to see if anyone had tried it and what their results were.
[Sprint Samsung Galaxy S III] Perseus:
Don't think that would be the case anytime soon for AOSP. Given that there are quiet a few apps kludgy at ART and Garbage Collector of ART is even more kludgier.
[Sprint Samsung Galaxy S III] hayzooos:
It may not be official official, but it seems like it's coming:

http://www.androidpolice.com/2014/0...l-removed-android-art-officially-takes-place/

http://androidandme.com/2014/06/news/next-version-of-android-officially-to-run-art-by-default/
[Sprint Samsung Galaxy S III] kuhl_man:
How do you get ART to stick? On 5.8 and after reboot it stays on dalvik.
[Sprint Samsung Galaxy S III] arrogant437:
Where are you guys downloading the latest builds from for d2spr? The only one I can find is build 5 from may 12th
[Sprint Samsung Galaxy S III] JaylanPHNX:
Are you using Xposed? Xposed forces dalvik because it doesn't work on ART.

From my Tab Pro 8.4
[Sprint Samsung Galaxy S III] kuhl_man:
Yep. Forgot about that. Thanks
[Sprint Samsung Galaxy S III] rambleon84:
The weekly's section

http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1185-d2lte
[Sprint Samsung Galaxy S III] nimaim:
Very stable here on ART and been running it for some time now. It seems a bit snappier too as it should be as the apps are precompiled. Battery theoretically should be better.as well. I have no problems with any of the apps I have installed. I just miss Xposed which only works on dalvik but hoping rovo can do his magic to make it work on ART some day.

Keep in mind that if you switch from dalvik to ART, first bootup takes forever because of all the apps it has to precompile, so be patient.

---------- Post added at 11:01 PM ---------- Previous post was at 10:59 PM ----------

Forgot to mention, I am running the latest weekly with LeanKernel OC'd to 1.6 GHz and UV'd -50mv every step with TricksterMod and getting great results.
[Sprint Samsung Galaxy S III] nimaim:
I finally got around to enabling Privacy Guard for all my user apps (in addition to having most of them Greenified) and my battery is really kicking ass now. It used to suck on all KitKat ROMs and was excellent on JB but Privacy Guard and Greenify help a lot (in addition to enabling things like holding back to kill apps that like to linger around forever like Whatsapp). Now I know apps won't be accessing location and other things when I don't want them to. Only Maps has access to my location now. I'm not sure how effective it is vs. other offerings but seems to be working well here. Just an FYI.
[Sprint Samsung Galaxy S III] SirHustlerEsq:
I believe the motherboard is Samsung, so I ordered a $10 Samsung camera. I'll pop that in later this week and see what happens. I'd like to keep this phone because I'll miss the 32GB SD card if I switch to a Nexus 5, and I also would hate to pay full retail for a year-old phone.
[Sprint Samsung Galaxy S III] nimaim:
I had a Nexus 5 for about a week (got it on Swappa). Long story short, prior to that I had dropped my S3 and shattered it so it was done so went on Swappa to get a Nexus 5 (in case I ever switched providers in the future since it supports all carriers except for Verizon). When it arrived, I saw it was purchased from the Tmobile store, so the IMEI was not in Sprint's database and they would not activate it. So I played around with it for a week or so and resold it there and picked up a good condition S3 again on Ebay.

It's a great phone but I wouldn't pay full retail for it right now, especially when Google I/O is coming up and they'll be announcing their new product line. It was super snappy though and the display was gorgeous. Things I didn't like though was that there was no microSD card and notorious for the Nexus line: a non-removable battery. The battery life was pretty weak and there'd be no way to pop in a larger one. It was also too big in the hand. I think ~4.5" inches is the ideal size (I feel even the S3 a bit too large since I can't comfortably do everything with it with one hand, but the Nexus 5 felt considerably larger). I'll be honest: my S3 with SlimKat, and Leankernel OC'd to 1.6 ghz and with ART was as every bit as fast as the Nexus 5 for routine tasks. I didn't feel the need for anything top of the line and that's why I went back to this phone (that and I know Slim ROM has great support for it). Just my personal opinion. Unless it's anything ground-breaking, I won't be upgrading for a while, even though my contract is up in the fall. I'd jump on Tmobile's $30 plan in a heartbeat if there was service at my workplace (I tested their LTE at home on an LG F6 and it was blazing fast).
[Sprint Samsung Galaxy S III] hayzooos:
The first time rolling through it is a pain setting all the permissions the way you want. However, now they're all set and anytime I install a new app, the first thing I do is go to Privacy Guard to see what it's doing. If it doesn't need it, no dice. I agree, battery life is better when only the things you want accessing location are actually doing so.

One small note that might help someone too.....if you ever backup your SMS/MMS messages through Titanium, make sure you give it the correct permissions in PG so it can access them, or it obviously won't work ;). Took me a minute to figure out why TB wasn't backing up my messages so when I flashed a new ROM, I didn't lose them all.
[Sprint Samsung Galaxy S III] LightC:
Why is there no ro.product.device in the build.prop for SlimKat? I'm trying to get my phone recognized as a Nexus 5 in order to get some advanced autoawesome functionality in Google+ but can't seem to get it to work.

Adding ro.product.device to the build.prop doesn't seem to work for Google+ where it does on my HP Touchpad.

Thanks in advance for any help.
[Sprint Samsung Galaxy S III] sixgunmojo:
I very rarely have anything bad to say about SlimKat but for reasons that I won't waste time explaining I actually installed the Xposed module AppOpsXposed. All I can say is Privacy Guard in SK is seriously crippled. AppOps will give you the same type of control over all apps including system apps.

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

Well this is odd. My build.prop file has a comment in it that says " #ro.build.product is obsolete; use ro.product.device " aaaannd right under that it says " ro.build.product=d2lte ". Somebody needs to make up their mind. I would (if you haven't) change that and give it a whirl. If that doesn't work, I got nuthin
[Sprint Samsung Galaxy S III] Perseus:
Try the Privacy Guard in the Rom instead of App Ops. You need to have ro.build.product for backward compatibility of ancient apps.
[Sprint Samsung Galaxy S III] LightC:
by default in this ROM, i don't see ro.build.device in the build.prop. Also, I can't get google+ to recognize the device as a Nexus 5 using either ro.build.product or ro.build.device. I'm going to try the Slim Gapps and see if that will work
[Sprint Samsung Galaxy S III] Perseus:
There's couple of other ones you need to change before you can fool apps or whatever you are trying to fool.

ro.product.model

ro.product.brand

ro.product.name
[Sprint Samsung Galaxy S III] sixgunmojo:
I do use Privacy Guard, have since it first came out. Trust me, compared to AppOps it is crippled.
[Sprint Samsung Galaxy S III] zman519:
Why don't you guys use XPrivacy?

The Dev MB66 said the other day he has it running on android 4.4.4

Sent from a thing running on Electrons
[Sprint Samsung Galaxy S III] sixgunmojo:
I've given XPrivacy several tries and I get a better understanding of it every time I do. I really like the fine control that it gives you over permissions. The biggest problems I have with it are;

1) I haven't found easily understood definitions for the permissions. The android developer pages that everyone seems to link to are a little to esoteric to me as I am neither a dev or a programmer. I'm not stupid but while reading those pages I spend half my time thinking "wtf does that mean in english?".

2) I haven't found a good resource that can tell me why an app needs certain permissions. My natural tendency is to deny everything, so I tend to deny any permission that makes no sense to me. This, as you can imagine, leads me to spend a lot of time trying to figure out exactly what off the wall permissions an app needs to actualy work since it seems that most apps want access to damn near everything. Complicated by #1 above

3) If you combine 1 & 2 after 30-40 mins of dicking around I get frustrated. I pretty sure that if I understood templates better this wouldn't be such a big deal but I still haven't had my "ooooh now I get it moment".

4) On SK 5.8 it was giving me some weird behavior. When I would enter and leave certain system settings (display, apps, etc) it would turn on location and Google would be asking for permission to collect location data (ummmm, hell no). It also caused TiBu to force close even though I never gave it any restrictions. The location thing appears to be fixed on 5.9 but the TiBu thing is still there. I'm thinking (hoping) it's one of those quirks that will get ironed out as 4.4.3 and 4.4.4 get better integrated.

Since I tend to give it another try when I'm getting ready to flash a new weekly/rom (in case I seriously eff something up) I'm hoping I have it figured out in a month or two.
[Sprint Samsung Galaxy S III] zman519:
Ya I hear you I'm in IT but not a programer.

Iv just been using it for a while now, as the app started to grow up and mature

Sent from a thing running on Electrons
[Sprint Samsung Galaxy S III] Perseus:
I understand your frustration. I don't use Xprivacy so can't help there. Please understand that, controlling access permissions is fine. Please do not try to control wake permissions of an app. That will land you in heap of trouble. Yes SlimKat did have synchronous Bluetooth and Location connection bug. It's fixed in 5.9 but a new one for BT was introduced. That will be fixed in the next release.

As to your frustration with the definition of permissions, can you please post here one of them that is hard to follow ? Some elaboration will help. I can help interpret them for you or answer any questions you may have.