yashsingh1/xdaforums huggingface dataset:
[Droid RAZR M Q&A, Help & Troubleshooting] rekids:
Not sure if it works for the M but .... A root exploit has been released today for the newer motos on 4.4 & 4.4.2 (pre April 30th for Ultras).

This release was brought to us by none other then Jcase.

Please help and contribute to the bounty for all the work and talent he has shared over time here on XDA.

Root exploit is in the Moto X forum.
[Droid RAZR M Q&A, Help & Troubleshooting] GnatGoSplat:
Didn't work on the M.
[Droid RAZR M Q&A, Help & Troubleshooting] rekids:
Well there goes that idea. Worth a shot.
[Droid RAZR M Q&A, Help & Troubleshooting] Galchonok:
Any way to adopt that root for our device? Or again we have no such exploit?
[Droid RAZR M Q&A, Help & Troubleshooting] RikRong:
You can't just "adopt" root.

This is a direct quote from this thread http://www.droidrzr.com/index.php/topic/46155-info-status-of-root-for-kitkat-build-182183/ on Droidrzr.com about why it doesn't work on the older Razrs:

^^^This patch is the one that's talked about on the XDA front page.
[Droid RAZR M Q&A, Help & Troubleshooting] Galchonok:
Oh Sh~t..I think I'll sell my Razr M and buy something more flexible for rooting.
[Droid RAZR M Q&A, Help & Troubleshooting] GnatGoSplat:
Problem is, if you want a small Android with decent specs, and I don't mean just one with a smaller screen, but also with a smaller body/bezels, Motorola's pretty much the only game in town.

For $47 shipped, I picked up what I HOPE is a BL unlocked RAZR M. In my free time, I waded through hundreds of eBay auctions till I found an M with a screenshot of something other than stock ROM and found one with CM on it.
[Droid RAZR M Q&A, Help & Troubleshooting] Strife89:
Nice find! Razr Ms are still going for no less than $100 on Swappa, so hopefully you got a sweet deal. :good:

I only wish I was so lucky. :/
[Droid RAZR M Q&A, Help & Troubleshooting] GnatGoSplat:
Normally they don't go that cheap. Part of the reason might be because it has a cracked camera lens, but I bought a new one for $8.95. Possibly people also get scared off when they see a non-stock ROM because they want something that hasn't been tampered with. It's not the first time I've seen an M with CM on it that went for lower than average.

Hopefully the phone turns out to be BL unlocked and not safe-strapped. Seller said he was 99% sure it was BL unlocked. If not, no biggie, I should at least be able to get my money back if I resell it.

I might still keep looking because the phone I bought was white and I really prefer black.
[Nexus 5 Q&A, Help & Troubleshooting] Jason78729:
What are the advantages and/or disadvantages of enabling "force GPU rendering" and "disable HW overlays"?
[Nexus 5 Q&A, Help & Troubleshooting] Hammer_Of_The_Gods:
Hi,

You can test easily by yourself and see if you see any advantages and/or disadvantages, right? Just tick/untick and even no need for a reboot... It tends to make some old apps smoother.

If it helps you, here are two quotes that summarize well.

About "force GPU rendering":

About "HW overlays":

I have force GPU rendering enabled since years, it helps about smoothness in XDA app for example, on my side never encountered any side effects, at least for me.
[Nexus 5 Q&A, Help & Troubleshooting] Jason78729:
Thanks, that was exactly what I was looking for. I usually keep force GPU rendering on as well but always had mixed results with disable HW overlays. The definitions helped make sense of that.
[Nexus 5 Q&A, Help & Troubleshooting] dec1153:
Hi. I'm rooted with xposed- stock os. I know that I can no longer enable art so i am wondering if this is the same.... Can I enable the GPU HW and rendering without a brick or bootloop
[Nexus 5 Q&A, Help & Troubleshooting] Hammer_Of_The_Gods:
Hi,

No, it's not the same thing, about ART: http://xdaforums.com/google-nexus-5/general/dedicated-runtime-thread-art-vs-dalvik-t2516646.

And yes you can enable them without any issue, nothing related to Xposed (unless an Xposed module breaks something related to those options but I highly doubt). If you want to be sure then make a Nandoid backup before (in any case the "Disable HW overlays" doesn't persist at boot).
[T-Mobile Samsung Galaxy S 5] koolboyztn:
and yr question is ????
[T-Mobile Samsung Galaxy S 5] aooga:
Are you asking how to enable it? You might want to actually write that.

Go into settings>about device>tap on build number 7 times
[General Questions and Answers] msystem_xda:
Hello.

From some weeks on my mobile "cubot x6" I have some problem with the facebook app, during the navigation, opening a post o picture albun the app turns off automaticaly or in some case the sistem say me that is not responding and give the choice of closed or wait. I've install again the app, delete the folder on th ememory, reset the mobile on the factory setting but is alaways the same, give me this problem when I'm in wifi like 3G.

What I can do ??? HELP
[General Questions and Answers] shubhojit89:
You are not the only one m also facing it.. Its related to app.. Not related to phone..:good:
[General Questions and Answers] msystem_xda:
So we need only to wait Facebook developers that solve it :eek:
[General Questions and Answers] shubhojit89:
Yes.. We have to wait..
[General Questions and Answers] Slain-Muabdib:
I have the same problem, dont worry
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.

The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.

All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.

SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:

The Real Dark Slim

Full system-wide dark interfaces. - If you like it smooth and classy.

Custom Shortcuts. Everywhere.

Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.

System-Wide Keyboard Controls

Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.

SlimCenter

Downloads, contact information, system app removal. - More fun than you can shake a stick at.

Camera Features

Trueview, Smart Capture. - Capture life moments with ease.

Important links:

slimroms.net - The official webpage where you find everything you need to know about SlimRoms.

(Official) Downloads - Download the rom, gapps and other addons.

MondrianWifi downloads:

Archive:

Slim-mondrianwifi-4.4.2.build.5.4-UNOFFICIAL-20140528-2305

Slim-mondrianwifi-4.4.2.build.5.4-UNOFFICIAL-20140529-0951

Slim-mondrianwifi-4.4.3.build.5.7-UNOFFICIAL-20140609-0914

Slim-mondrianwifi-4.4.4.build.5.10-UNOFFICIAL-20140624-1709

Slim-mondrianwifi-4.4.4.build.6.6-UNOFFICIAL-20140721-1012

Slim-mondrianwifi-4.4.4.build.6.9-UNOFFICIAL-20140729-0821

Slim-mondrianwifi-4.4.4.build.7.4-UNOFFICIAL-20140822-1723

Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.

Latest Changelog - Read here if you want information on changes in latest build.

FAQ - The most frequent asked questions with answers.

Kernel Source - The source of your device's kernel.

Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.

Google+

Twitter

Facebook

Forum

Disclaimer: SlimRoms are not responsible for any damages to your device.

Contributors

[MENTION=3857343]crpalmer[/MENTION]

SlimRoms

ROM OS Version: 4.4.x KitKat

ROM Kernel: Linux 3.4.x

Based On: AOSP
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
Bugs​

Bluetooth won't enable... seems permissions related?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
As usual, this wouldn't be possible without all the hard work from [MENTION=3857343]crpalmer[/MENTION] and the CM team in general.

In fact he already did most of the bringup for Slim, so apologies for dragging on this one - I know people were waiting for it.

Enjoy! I am thinking I can keep up with the weekly schedule Slim does, I'll try to coordinate my builds with their weeklies as best I can.

Let me know!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
OK, audio was easily fixed... just needed to add audio-caf ;)

Other issues are still present.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] pemati:
Good news! Thank you very much for bringing SlimBean to us! ☺
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JaylanPHNX:
Awesome. Of course this drops right as I'm heading out of town and can't flash, but that's how my life goes. If you're not sure you've got the right repo and such, ask the guys in the N5 thread. They often help people trying to make their own builds. Friendly bunch there. Thanks for your work on this (and of course crpalmer!).

From my Pro Tab 8.4
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
See the post I quoted, it's fixed.

I've also fixed the keyboard issue... I guess I should play with different values, but the values used for CM didn't work... default is 4, crpalmer adjusted to 5... which worked for other ROM's. I just tried 15 for fun, and it worked.

Going to attempt 6 and see if that is good enough. I'm not sure what the negative effect would be of turning up this divider tho?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JaylanPHNX:
I finally got a chance to flash this and though I haven't tested everything possible, so far I've not encountered a single issue. I'm just thrilled to death. It's just like on my Nexus 5. I can't thank you, [MENTION=420530]arrrghhh[/MENTION] (and of course [MENTION=3857343]crpalmer[/MENTION] for his device wizardry) enough.

From my Pro Tab 8.4
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] xpdragon:
Can't turn on bluetooth

I can't turn on bluetooth. I don't know if I did anything wrong.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JaylanPHNX:
I can confirm, Bluetooth will not turn on. As I said earlier, haven't tested everything yet.

From my Pro Tab 8.4
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
I've never used BT on my tab, never saw the need...

I'll try it later. Thanks for the report.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JaylanPHNX:
I would never use it either if it weren't for my MOGA controller and Dead Trigger 2.

Sent from my Slim Nexus 5 with smoothness by Faux.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] micmars:
If using the Tab for WiFi calls (Groove IP, &c), Bluetooth becomes a useful feature to have.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] manigault:
Seems pretty smooth, but holy cow is the status bar tiny. It's a good thing I'm not elderly.?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
I didn't say it was useless, I just didn't see a need for it.

Also, isn't GrooveIP basically dead now that Google removed support for third parties?

I wish Hangouts was as good on Android as it was on iOS... sad really. But I digress, I'll look at the issue...

lol, Slim likes to use a different DPI. I believe Slim is working towards a DPI updater on-the-fly... otherwise you'll have to adjust it in the build.prop.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] micmars:
No Doubt...

Understood as to your statement of its utility, inasmuch as one person's feature is another's bloat. As to Groove IP rendered dead, it was given another span of life via the entity Ring.to. Swift to establish, and a host of additional numbers to grab. Works flawlessly.

I as you am dumbfounded by the superior quality of Hangouts for iOS.

Thanks for all you do.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] manigault:
I've never messed with Dpi before, but you learn something new every day. Lookin good now!! Thanks!!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JaylanPHNX:
I've noticed apps seem to treat the tablet as though it has a menu button. No three dot button in UI or menu button appears in soft keys. Is there a build.prop edit or something that can fix this?

From my Pro Tab 8.4
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] SomeGuyDude:
All I want for Christmas is a rom on the 10.1... :(
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JaylanPHNX:
And it may take till Christmas to get one. The Exynos processor in it makes it harder to work with, from what I understand. The 8.4 has the better supported Snapdragon 800 and is not too different from the Note 3.

From my Pro Tab 8.4
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] SomeGuyDude:
Is that what it is? Hm. Now I'm genuinely curious and might swap.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Shyonnu:
Please keep going wonderful. I am rooted and have the twrp mondrianwifiue installed - do i need kernel (which one) and is slimkat stable yet for beginners like me or better wait a little?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
Kernel is included.

It's fairly stable - so far there is an issue with BT, so if you need BT, then I would flash CM.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JaylanPHNX:
I'd give it a B+ for stability. Couple little things here and there, but definitely daily driver material (unless somehow BT is super critical for you). One small but strange thing is I get vibrations for everything properly except for Swype keyboard. I checked all settings in ROM and app and it should be vibrating in key press. Also the three dot menu issue I mentioned earlier. Like I said, little stuff.

Sent from my Slim Nexus 5 with smoothness by Faux.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JaylanPHNX:
Okay, found another bug. Some video playback is all jacked up (that's a technical developer term, right?). YouTube definitely has this issue and I encountered it on a website but I don't know if that video was YouTube based (didn't look like it). My vids from Google Drive play fine, as well as one I found on G+ (though that one looked for half a second as though it would mess up too). Here's an example recorded from my tab. Bad colors.: http://youtu.be/qZtS7atKGzw

Edit: Doing some looking, it seems as though the CM builds were having YouTube issues as well a while back, that have since been fixed. Maybe it's time to resynch with the CM-based parts and build another SlimKat?

From my Pro Tab 8.4
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
I noted the YouTube issues in the list already...

As for your question about syncing, that is the plan. My last attempt failed, not sure if it was related to the 4.4.3 merge and I caught the source at a bad time... or what happened, but I wasn't able to build and didn't have time to look at the error.

I will attempt a complete rebuild based on the latest sources from CM and Slim... just no promises as to 'when' ;)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JaylanPHNX:
My bad. It's been a week since I read the first couple posts and I totally forgot it was a known issue. I feel like a noob. Any ideas about the three dot menu button not showing up in the UI or on the nav bar?

From my Pro Tab 8.4
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
No worries.

I forgot to respond to your 3-dot menu question - is it specific apps? For example, wifi settings and BT settings have 3-dot menus here... YouTube also has the 3-dot menu in the top right...
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JaylanPHNX:
I'm seeing it in some and not in others. Specifically, it's not in Chrome, and there's no menu button in Titanium Backup (even though that doesn't use the three dots). I do see it in many other apps. And of course some use the hamburger menu, but that's irrelevant. I think that some apps still attempt to dynamically change whether or not they have the menu in UI based on device, while others just use it at all times. That's why my first thought was maybe it's a build.prop thing.

Sent from my Slim Nexus 5 with smoothness by Faux.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] tvlovers:
Does it work on SM-T520 ?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JaylanPHNX:
Title says mondrianwifi, that's T-320. Period. Sorry.

From my Pro Tab 8.4
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
+1, it's what I have so it's what I build for...
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JaylanPHNX:
Even in unofficial form, Slim kicks @$$ and takes names on the battery front.

From my Pro Tab 8.4
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
Wow, nice!!

So I just saw a post in the CM thread - I wonder if the 3-dot menu issue is related to the launcher (Slim uses Nova by default).

http://xdaforums.com/showpost.php?p=53257852&postcount=324

Also, I think I found my problem and am working on rebuilding :)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JaylanPHNX:
I've been following the CM thread, too. That issue was with being able to assign the menu function to the recents button, something Slim does in a very different way. It works for Slim. I have a double tap of recents capacitive key set to menu for those apps not showing menu.

Good luck with the new build.

Sent from my Slim Nexus 5 with smoothness by Faux.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
Hm, I'm actually a bit worse now with the new msm8974-common change...

https://dl.dropboxusercontent.com/u/12691845/Android/logcat_gtab.txt

[MENTION=3857343]crpalmer[/MENTION], sorry to ping you but if you wouldn't mind giving me some suggestions.... Bluetooth was broken previously, but now wifi is as well:

01-01 01:54:56.140 E/WifiHW ( 368): Failed to open wlan fw path param (No such file or directory)
01-01 01:54:56.140 E/SoftapController( 368): Softap fwReload failed
01-01 01:54:56.140 E/WifiStateMachine( 857): Failed to reload STA firmware java.lang.IllegalStateException: command '1 softap fwreload wlan0 STA' failed with '400 1 SoftAP command has failed'
01-01 01:54:56.140 W/CommandListener( 368): Failed to retrieve HW addr for wlan0 (No such device)

I've updated with the prima definition and matched the dependencies you have for CM, plus a few required for Slim...

and for BT, I saw this and thought a kernel issue?

E/bt_upio ( 3554): init_rfkill : open(/sys/class/rfkill/rfkill0/type) failed: No such file or directory (2)

Thanks!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] crpalmer:
You can ignore the rfkill error. I've never bothered to look and see if I can stop it from trying to use that (we don't need or have it).

For the wifi, my guess is that your device tree isn't right. Do you have:

TARGET_MSM8974_COMMON_WLAN_VARIANT := prima

before including the msm8974-common board config? It looks like it's not using the right "firmware" path and hitting that path is what causes wlan0 to be initialized.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
Yep, I mentioned that too:

"I've updated with the prima definition..."

So that definition is in my device tree... hmmm. Y'know, you mention before including the common board config. That may be the derp, I include the common board config before I define prima. Let me swap that, thanks for the tip!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
Boom, and wifi works.

Thanks again [MENTION=3857343]crpalmer[/MENTION]... would you mind looking at my lolcat for any clues on BT? If it's not the RFKill issue, what about this debacle:

01-01 01:56:07.349 D/BluetoothHeadset( 1060): java.lang.Throwable
01-01 01:56:07.349 D/BluetoothHeadset( 1060):	at android.bluetooth.BluetoothHeadset.phoneStateChanged(BluetoothHeadset.java:825)
01-01 01:56:07.349 D/BluetoothHeadset( 1060):	at com.android.phone.BluetoothPhoneService.handleQueryPhoneState(BluetoothPhoneService.java:346)
01-01 01:56:07.349 D/BluetoothHeadset( 1060):	at com.android.phone.BluetoothPhoneService.access$300(BluetoothPhoneService.java:55)
01-01 01:56:07.349 D/BluetoothHeadset( 1060):	at com.android.phone.BluetoothPhoneService$1.handleMessage(BluetoothPhoneService.java:187)
01-01 01:56:07.349 D/BluetoothHeadset( 1060):	at android.os.Handler.dispatchMessage(Handler.java:102)
01-01 01:56:07.349 D/BluetoothHeadset( 1060):	at android.os.Looper.loop(Looper.java:136)
01-01 01:56:07.349 D/BluetoothHeadset( 1060):	at android.app.ActivityThread.main(ActivityThread.java:5034)
01-01 01:56:07.349 D/BluetoothHeadset( 1060):	at java.lang.reflect.Method.invokeNative(Native Method)
01-01 01:56:07.349 D/BluetoothHeadset( 1060):	at java.lang.reflect.Method.invoke(Method.java:515)
01-01 01:56:07.349 D/BluetoothHeadset( 1060):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795)
01-01 01:56:07.349 D/BluetoothHeadset( 1060):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:611)
01-01 01:56:07.349 D/BluetoothHeadset( 1060):	at dalvik.system.NativeStart.main(Native Method)

I'll be honest, I am not so good at reading logcats - getting better, but nothing is jumping out at me for this BT issue...

Thanks again (again!) :)

Edit - new build uploading regardless, YouTube is definitely fixed with this version :)

Edit 2 - a friend caught this:

01-01 01:56:07.359 I/bt-btu ( 1488): btu_task pending for preload complete event
01-01 01:56:07.359 I/bt_userial_vendor( 1488): userial vendor open: opening /dev/ttyO1
01-01 01:56:07.359 E/bt_userial_vendor( 1488): userial vendor open: unable to open /dev/ttyO1
01-01 01:56:07.359 E/bt_userial( 1488): userial_open: wrong numbers of open fd in vendor lib [0]!
01-01 01:56:07.359 E/bt_userial( 1488): userial_open: HCI UART expects only one open fd

I don't seem to have a tty01 (or O1?)... the permissions for BT are straight from CM, I wonder if Slim needs different perms / in a different place... hmmm
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] crpalmer:
You're using the wrong vendor implementation of bluetooth. That's the brcm version. If you have wifi working and haven't changed any BT config then this should also be working. In msm8974-common the wifi variant also selects the right bluetooth variant.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
Shoot. I'm definitely using the msm8974-common repo, as well as the latest patches from CM to update the device tree to the new -common (removed a lot of stuff, which I'm assuming is just duplicated in -common).

https://github.com/arrrghhh/android...mmit/f15807d8e63d7d9a474f1d1662c3e4b39cc7300e

https://github.com/arrrghhh/android_device_samsung_msm8974-common/tree/slim-kk4.4

Had to make some adjustments to this -common for Slim... I don't think that would have affected it, because the previous build I was using msm8960-common and I didn't need to make any changes for it...

Will keep poking, thanks for the suggestion!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JaylanPHNX:
Ha! For some reason I didn't realize you'd posted the 4.4.3 build you'd made. Just flashed it. I it's a shame the Bluetooth is still giving you problems, but hey, YouTube videos seem to be playing just fine, now. Thanks for that.

From my Pro Tab 8.4
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] crpalmer:
The msm8974-common changes don't look necessary to me.

Have you done a mka clobber or make clean recently? Maybe your build is stuck in some kind of funky state?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] arrrghhh:
I (almost) always clobber.... Definitely have tried that.

Got a wild hair and have a crazy idea. Going to test a theory, bbiab :)

Edit - hm... didn't work out like I had hoped. I spoke to some guys in the Slim IRC, and they said I should be using the 'caf' branches... which I already was. Audio didn't work until I added the audio-caf branch, but I am not finding anything missing like that for Bluetooth...

Edit2 - and I a bit lazily commented out the preferred_network_mode_choices_cm - but those are not available in Slim ;) I spose I should properly delete them.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kcallis:
Is this already rooted or will I have to re-root?