Develop Bugs

Cannibal Open Touch v2.1 (latest update: 12/1/2012)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Project Open Cannibal presents...
Cannibal Open Touch v2.1 for Amazon Kindle Fire (first generation)​
About Cannibal Open Touch:
Cannibal Open Touch is the next generation of custom recoveries. Jam-packed with cool and useful features, it can handle just about anything you can throw at it.
Warning: Does NOT currently support KitKit
Main Features:
1. Theme support
2. Touch screen button controls!
3. GooManager support!
4. Advanced Backup
5. Delete old backups!
6. Persistent settings
7. User-defined backup locations!
8. ADB Sideload
9. Touchscreen calibration
10. Backported “retouch binaries” patch for ICS/JB compatibility
11. Backported extfs tools for better ICS/JB management
Why the name Cannibal Open Touch?
Because we can. The name also embodies everything that Cannibal Open Touch is. It is no longer just a variant of ClockworkMod Recovery, it is it's own recovery by itself. Combining features from ClockworkMod 5, Team UtterChaos' Sony Xperia recovery, AmonRa 3.0.6, Xionia CWMA and a heaping helping of our own special enhancements it is truly revolutionary.
What to do when an error occurs:
DO NOT simply say "xxxx doesn't work" as that is highly unhelpful and will probably be ignored. Instead, post the recovery log! To grab a log when an error occurs, simply open a terminal (or command prompt if on Windows), "cd" to an easily accessible directory and execute:
Code:
adb pull /tmp/recovery.log
Paste the log as an attachment (don't paste the text inside, as it can be quite lengthy), or paste it on pastebin.com.
WARNING!
If you are upgrading from a previous version of Cannibal Open Touch you must delete the settings.ini file located in the cotrecovery folder on your sdcard!
Flashing instructions:
Flashing instructions can be found at the download link below.
Main Recovery Screenshots:
Main Gallery (external link) (Nexus 7 screen shots; will update soon)
Available Themes:
Themes Gallery (external link) (Again, Nexus 7 images shown here)
Download Cannibal Open Touch v2.1:
Note: The below link is an external link to the Project Open Cannibal forums. We do not require registration to download any public release, but we'd sure appreciate it if you stopped by to say hello
Cannibal Open Touch Download (external link)
For those of you who are either uncomfortable or incapable of using fastboot for some reason webdroidmt has done an updated Smirkit 2.1 for y'all, please see the original Smirkit release page for usage instructions.
XDA:DevDB Information
Cannibal Open Touch v2.1, a Tool/Utility for the Amazon Kindle Fire
Contributors
Sblood86, drewwalton19216801, thenameisnigel
Version Information
Status: Stable
Current Stable Version: 2.1
Stable Release Date: 2012-12-01
Created 2013-09-04
Last Updated 2013-11-28

Good to see you posting COTR here! Thanks.
Mike T

Just made a nandroid & it seemed faster than 2.02, maybe placebo. :laugh: Didn't flash any roms , as I don't have anything new to flash...yet! I like the overall simplicity and the functions in plain language terms.
Couple of questions, where can I read up on how to install a theme? Is that something that the COTR android app does or will do? Also, as stated in the OP, I deleted my current .ini file but can I still restore older COTR nandroids, say from 2.02 with this version? I'm figuring yes but want to be sure.
Thanks again for an alternative to TWRP. Btw, when the skull logo first came up, I thought I got a virus or something. LOL Looks cool.
Mike T

webdroidmt said:
Just made a nandroid & it seemed faster than 2.02, maybe placebo. :laugh: Didn't flash any roms , as I don't have anything new to flash...yet! I like the overall simplicity and the functions in plain language terms.
Click to expand...
Click to collapse
I can't imagine what would effect speed but cool
webdroidmt said:
Couple of questions, where can I read up on how to install a theme? Is that something that the COTR android app does or will do? Also, as stated in the OP, I deleted my current .ini file but can I still restore older COTR nandroids, say from 2.02 with this version? I'm figuring yes but want to be sure.
Click to expand...
Click to collapse
Previous backups should work just fine yes as for themes we don't have a lot yet but there is an outline for creating them on both github and the POC forums. The apps capabilities are limited to Drew's java capabilities as I find java to be; well, it's unsavory, we'll leave it at that
To that end I'm not sure but maybe.
webdroidmt said:
I thought I got a virus or something.
Click to expand...
Click to collapse
Love it!

Thank you Sblood86 this is a great Christmas gift awesome work. Updated index.

I assume this replaces twrp. Would I install this along side twrp? Will firefirefire offer a choice of recovery?
Sent from my Amazon Kindle Fire using xda app-developers app

Sblood, is there a way in settings to change the time? Thanks.
Mike T

webdroidmt said:
Sblood, is there a way in settings to change the time? Thanks.
Mike T
Click to expand...
Click to collapse
Not at this time (no pun intended); requires an offset which varies a bit by location so it's a bit of a hack. Haven't done it yet but we may add a function for it in the future.

Sblood86 said:
Not at this time (no pun intended); requires an offset which varies a bit by location so it's a bit of a hack. Haven't done it yet but we may add a function for it in the future.
Click to expand...
Click to collapse
Thanks for your reply, obviously it would be nice for proper timestamping of the nandroids, as now it reads 5 hours ahead for me.. But even without that, I've previously been enjoying using COTR and this new version with themes gives me a little something extra to play with.
Started messing around with the themes I d/l from the git, took the devildroid one and substituted the devildroid background out with the droid jellybean machine that's been floating around the web. Simple but looks pretty nice, I like green :laugh: and gives me a better idea how to work with the themes going forward. Gonna' work with the HTML color picker to see what other combos I can come up with.
Btw, just for the heck of it, I updated my smirkit with COTR 2.1 and flashed it instead of fast booting it.
Anyway, thanks again for this update.
Mike T

Ixthusdan said:
I assume this replaces twrp. Would I install this along side twrp? Will firefirefire offer a choice of recovery?
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
There can be only one.

flashable zip?

smirkit with COTR 2.1
For those not comfortable using fastboot, I've updated smirkit with COTR 2.1. You can find the download link on the smirkit thread here:
http://forum.xda-developers.com/showpost.php?p=34974869&postcount=325
Mike T

portezbie said:
flashable zip?
Click to expand...
Click to collapse
Hmm; suppose it wouldn't be a bad idea I just didn't really consider it lol...
webdroidmt said:
For those not comfortable using fastboot, I've updated smirkit with COTR 2.1. You can find the download link on the smirkit thread here:
http://forum.xda-developers.com/showpost.php?p=34974869&postcount=325
Mike T
Click to expand...
Click to collapse
I almost messaged him in regards to that but I knew he didn't have a KF so I figured we'd leave it be lol
Edit: linked to the OP as well.

great work, but..
I love new stuff and really want to try this -- it sounds great -- but with the past mis-flash issues with all versions of CWM and similar problems with many of the later TWRP versions on the KF device, I'm, to say the least, a little gun-shy. (the name also adds to my unease - but so would a pink unicorn heh)
Perhaps when I see folks posting multiple (2-3) successful flashes of different roms with this, I will jump on board with both feet. As clunky or ugly as it is, TWRP 2.1.1.1 works flawless for me and has for months so, as much as I like the latest/greatest, I'm holding off for now.
Many thanks to the OP and all the other fine Android developer volunteers here as well. :highfive: Your efforts are immensely appreciated - especially when you innovate a new solution like this one. Unfortunately I'm a relative android n00b and have scant confidence in unbricking my device should that occur, and even, as low as prices are, less ability to replace it as I'm on fixed income that almost covers living expenses. Sorry..

dadeo1111 said:
I love new stuff and really want to try this -- it sounds great -- but with the past mis-flash issues with all versions of CWM and similar problems with many of the later TWRP versions on the KF device, I'm, to say the least, a little gun-shy. (the name also adds to my unease - but so would a pink unicorn heh)
Perhaps when I see folks posting multiple (2-3) successful flashes of different roms with this, I will jump on board with both feet. As clunky or ugly as it is, TWRP 2.1.1.1 works flawless for me and has for months so, as much as I like the latest/greatest, I'm holding off for now.
Many thanks to the OP and all the other fine Android developer volunteers here as well. :highfive: Your efforts are immensely appreciated - especially when you innovate a new solution like this one. Unfortunately I'm a relative android n00b and have scant confidence in unbricking my device should that occur, and even, as low as prices are, less ability to replace it as I'm on fixed income that almost covers living expenses. Sorry..
Click to expand...
Click to collapse
I'm on board with you, I've become complacent with the ease of use the developers have granted us with flashing roms for the Kindle Fire. Much of what I learned when I first started messing with the Kindle Fire has been left in a dusty part of my brain because I haven't needed to use it. If I was still able to confidently unbrick the KF (or at least know i'd have a good shot at it) i'd give this recovery a try, but my confidence isn't there and neither is my funding for a new KF should I void the warrenty.

dadeo1111 said:
I love new stuff and really want to try this -- it sounds great -- but with the past mis-flash issues with all versions of CWM and similar problems with many of the later TWRP versions on the KF device, I'm, to say the least, a little gun-shy. (the name also adds to my unease - but so would a pink unicorn heh)
Perhaps when I see folks posting multiple (2-3) successful flashes of different roms with this, I will jump on board with both feet. As clunky or ugly as it is, TWRP 2.1.1.1 works flawless for me and has for months so, as much as I like the latest/greatest, I'm holding off for now.
Many thanks to the OP and all the other fine Android developer volunteers here as well. :highfive: Your efforts are immensely appreciated - especially when you innovate a new solution like this one. Unfortunately I'm a relative android n00b and have scant confidence in unbricking my device should that occur, and even, as low as prices are, less ability to replace it as I'm on fixed income that almost covers living expenses. Sorry..
Click to expand...
Click to collapse
isaiahhhhh said:
I'm on board with you, I've become complacent with the ease of use the developers have granted us with flashing roms for the Kindle Fire. Much of what I learned when I first started messing with the Kindle Fire has been left in a dusty part of my brain because I haven't needed to use it. If I was still able to confidently unbrick the KF (or at least know i'd have a good shot at it) i'd give this recovery a try, but my confidence isn't there and neither is my funding for a new KF should I void the warrenty.
Click to expand...
Click to collapse
I understand the reluctance but also can state fairly plainly that IF you had been following CWM issues closely you would know that the only issues that CWM ever had with the kindle was Flashing 3.y kernels (resolved a long time ago with the first iteration of my recovery {before we renamed it}) and the super bricks with the ICS+ based recovery (solved by removing the EMMC wipe calls); this is a gingerbread hybrid so the last of those 2 isn't even remotely possible...
A fairly moderate amount of research would prove both of those statements; I would NOT release something that I wasn't confident worked. The only risk to bricking your devices while using this recovery is improper usage and/or flashing or doing something you shouldn't be doing...
Just to reinforce that statement I haven't used TWRP since last December when I rooted my Kindle Fire; it has always ran a variation of CWM or similar and guess what; it still works
I also have a jellybean based recovery for us; works flawlessly (I've been running it on my kindle for months without any emmc crashes {yes I do have the faulty samsung emmc so if there were still erase issues I would have a brick sitting on my desk; again, I don't }) apart from USB mass storage (which is the only reason we released the hybrid instead of the jellybean based recovery).
Now I know you guys are going to make up your own minds and so forth and I wouldn't ask for anything less; part of the reason I love Android devices is the Open Source nature and the fact that you aren't required to use one specific program so if you don't like the recovery that is entirely your right. Having said that I'd hate for fear to be the only thing that kept y'all from trying something new; read the recovery discussion in Hashcode and DooMLoRDs old recovery threads if you would like to know more on the subjects, also my CM7 thread discusses the my original iteration of CWM based 'hybrid' (gingerbread-ics) recovery (the release of which overshadowed as Hashcode released his ICS based recovery at the same time and people did have issues with it do to kernel wipe errors: these never occurred for those using the hybrid recovery and I'm sure you guys could find a few people to confirm that).
One final thought; instead of looking for posts saying it works, try finding one saying it doesn't (I personally never post when something works as it's implied in the fact that noone has screamed out saying it doesn't)
Edit: I forgot to mention we released 3 dev previews and a release candidate of this to our beta testers at the POC forums long before a public release (the rc was actually only out for a week but that was mainly to make sure we hadn't broken anything {layout related} since dev3).

COTR
A vote of confidence here for COTR. Don't get me wrong, I like TWRP with all its features, "pretty" UI and I especially like renaming my backups from within the recovery. But I had posted back in the summer that TWRP was becoming consistently unreliable for me in flashing ICS & JB roms, usually resulting in a flash failed error. At first I thought it was just bad downloads but this was with the MD5 matching and it would eventually flash after rebooting and reflashing on the second or third try. In a nutshell, every time I flashed a rom, I wondered if it was going to flash or bomb out on me.
With CWM not being a viable option, I was very happy to see Sblood release COTR and I've been using this as my recovery since August. I like supporting Sblood's work but more importantly I have confidence that my zips are going to flash every time as long as they are not corrupt.
Let me just say, I'm a flashaholic. I generally test just about every rom in this forum and I'm running nandroids just about every other day. Matter of fact, I maintain 3 different roms on this forum with 3 different Google accounts...they're cheap :laugh: Since I've been using COTR, I've not had one bad flash and I've backed up and restored more times than I can count without issue.
Now, if only the next version of COTR allows for renaming the nandroids. LOL Actually, I see from the COTR forum that it's on the to-do list. Well, that's my two cents and I guess we should all use what we're comfortable with in the long run.
Mike T

Looks promising. I flashed it using my favorite tool dd and it worked so far with my own unsigned zip file that resets all my custom tweaks via goo manager. I haven't tried any other features yet.

How do we make it portrait?
Sent from my Nexus 7 using XDA Premium HD app

firered365 said:
How do we make it portrait?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
It's controlled in the screen firmware and driver controller in the kernel; simply put, you don't/can't. Sorry.

Sprint Galaxy S3 FAQ updated 5/27/2013

[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2] Sprint Galaxy S3[/SIZE]​
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. [/SIZE]
[SIZE=+1]Q1: How do I root the Sprint galaxy s3?[/SIZE]
All things root can be found in the link below, including all files (including the drivers) you will need and a step by step video! Make sure to visit the sticky in development and thank qbking77 for his root thread (this method works with 4.1.1 and 4.1.2)
ROOTING GUIDE WITH VIDEO​
[SIZE=+1]Q2: I have bricked my device/my phone won't boot, what is the best way to fix it? (Use the Odin method for bringing your phone back to unrooted stock to bring in for repair)[/SIZE]
First, if you can get into recovery or download mode, you are not bricked, just sponged! If you can get into recovery, download and transfer a rom to your sd card and flash in recovery. If You can get into download mode you will need a stock .tar and Odin to "unbrick". The easiest way is to follow the link below for qbking77 guide on how to unroot/unbrick. Again, make sure you go to development and thank qbking77
unroot/unbricking guide with files and how to video​
[SIZE=+1]Q3: What is a custom recovery?[/SIZE]
A custom recovery takes the place of Samsung's stock recovery once you root your phone. There are two custom recoveries (team win recovery project), The other is CWMR (ClockworkMod Recovery). When choosing which recovery to use, read the ROM/kernel op that you want to flash, most of the time they will tell you which recovery is sorted for their project. In most cases both recoveries work just fine, so ultimately the choice is up to you, but if you decide to go with a recovery that the developer did not recommend, you still not receive support within that developers thread!
Link to Both custom recoveries and stock recovery can be found here ​
[SIZE=+1]Q4: What is the best/most stable Rom/Kernel (question that should never be asked)[/SIZE]
This is simple, there is no best/most stable Rom/Kernel for this device! They are all excellent and the devs have spent countless hours trying to perfect them all. The only way to decide what is best/most stable for you is to try them all out until you find one that suits your needs. In post #2 and 3 of this thread I have included links to all Roms and kernels on xda! Happy flashing!​
[SIZE=+1]Q5: Which Rom/Kernel will give me the best performance/battery life (this is another question that should never EVER be asked)?[/SIZE]
Please don't ever ask this in the forum, there is no best. Things like battery life and performance largely depend on the end users interaction with the phone. No two people use their phone in exactly the same way, so nobody can tell you which Rom/Kernel will work best for your needs. Many things affect battery life, including but not limited to, what and how often you sync things, signal, apps installed, widgets running, just to name a few. This is largely an opinion and for every 50 answers you receive you're likely to receive at least 30 different answers, so please, just don't ask it, it's a waste of everyone's time, including yours because you still never receive a straight answer​
[SIZE=+1]Q6: What is the proper way to install a Rom?[/SIZE]
In almost every case the proper instructions for flashing a custom Rom will be posted in the Rom threads 1st post. Some roms will say dirty flashing is fine, I avoid this to minimize problems. Download Rom, transfer to external storage (sd card). Boot into recovery, factory reset (which wipes data and cache) and wipe dalvik cache. Go to install, find the Rom you've downloaded and flash. Please remember that if you choose to format data (you'll see this option in twrp (completely unnecessary in most situations) ) will erase things on your internal memory, so make sure your music, photos, backups, and everything else important is on your external storage! DO NOT POST BUG REPORTS IF YOU HAVE DONE A DIRTY FLASH, start clean and if the bug persists after a clean flash then you may report the bug. Be prepared to provide a log cat and to be able to explain how to reproduce said bug if necessary (log cats explained later in this FAQ) just to clarify, factory reset and wrong dalvik cache is what's necessary for a clean install of a Rom!​
[SIZE=+1]Q7: What is ADB and how do I use it?[/SIZE]
Please see this thread for everything ADB
FULL ADB GUIDE​
[SIZE=+1]Q8: How to do a logcat from ADB and what the heck is a logcat?[/SIZE]
For setting up ADB see Q7!
logcat allows us to log what the OS is doing, and possibly delve information for when things are not working
its quite simple Reading it is another.
To use logcat
Code:
adb shell
logcat
To logcat to a certain file do
Code:
adb shell
logcat -d > /sdcard/whatevertextfileyoulike.txt
Obviously using the name of a text file of your choice, not "whatever text file you like"
For further explanation follow the link in Q6​
[SIZE=+1]Q9: Is there an app that will help me pull a logcat from the phone?[/SIZE]
Actually, yes, there is... but it does have its limitations, if you're stuck in a bootloop, the app will do you no good, you will have to use ADB for this, but if you're data is not connecting on a certain Rom, or something similar within the already booted OS this app can be rather handy and simpler for those who don't understand ADB. Link for app below
ALOGCAT APP​
[SIZE=+1]Q10: Can I flash any modem on any ROM or do the versions have to match?[/SIZE]
Modems/basebands are completely independent of the roms, so you can run any modem on any ROM! (They do have to be for the device you are using though)​
[SIZE=+1]Q11: Method to update prl without flashing back to a TOUCHWIZ ROM. Also how to enable baseband diagnostic mode. How to acquire MSL. (Not yet working on 3.4 kernels, which includes most updated aosp roms) [/SIZE]
Despite the common misconception that you have all probably heard, you have to be on a TOUCHWIZ ROM to update your prl, that is actually not true. The thread linked below will explain how and will also show you how to aquire your MSL and how to enable baseband diagnostics mode
See this thread for everything above​
[SIZE=+1]Q12: How do I backup my IMEI and do I have to do it?[/SIZE]
The thread linked below will explain everything IMEI, along with how and why you should do it!
click here for all the needed info​
[SIZE=+1]Q13: I have seen better battery stats (BBS for short) mentioned everywhere, what is this and why do I need it?[/SIZE]
BBS is an app made by an awesome XDA member that will help you identify what is keeping your phone from entering deep sleep (or wakelocks, which are explained below)
Thread for BBS​
[SIZE=+1]Q14: What is a wakelock and how do I get rid of them?[/SIZE]
This is the most involved and comprehensive guide I have ever seen on XDA involving wakelocks, if you're having problems with wakelocks, please go here and read posts 1-3 it will help you tremendously! Make sure you thank this guy as he obviously spent tons of time on this guide
T.J. BENDERS FULL GUIDE TO WAKELOCKS​
[SIZE=+1]Q15:I'm sure I'm following all the guides correctly, why does Odin still fail on me?[/SIZE]
The most common explanation for this is your data cable! Always, I repeat ALWAYS use a heavy duty data cable when Odin is at use. BlackBerry cables seen to be the most popular to use among Odin users and are very cheap online, save yourself some headaches and frustration in the future and pick one up!​
[SIZE=+1]Q16: I am rooted and just received an OTA update message, should I accept it and if I do will I lose root?[/SIZE]
Cnexus has wrote a great FAQ for all things OTA please read his FAQ for everything you need to know Cnexus OTA FAQ To kill the update notification for good you can also refer to this thread how to stop the update notification by Galaxys3man30​
[SIZE=+1]Q17:Is there a reference somewhere to explain all the different kernel governors and I/O schedulers?[/SIZE]
why, yes, yes there is! This is the best reference that I have found on xda Governors, I/O Schedulers and more reference​
[SIZE=+1]Q18:??????..............................................[/SIZE]
Replace this block of text with a short answer for the above question. If the answer is complicated or otherwise lengthy, avoid the temptation to provide a full answer here. If the answer is truly that involved, this should be answered in another thread outside of this document. The answer then should provide a brief summary or overview and direct the reader to the document providing a full coverage of the topic​
*​
Special thanks to these guys for helping through the process of creating this thread! If not for them this would be half of what it is, go find a post of theirs and hit that thanks button please!
Tazfanatic
Mw86
Rompnit
CNexus
Kennyglass123 (big thanks, you know why )
GalaxyS3Man30
Swiggs98
Adamdelozier
Edfunkycold
Orlzzt
And last but certainly not least, every Rom and kernel developer, including the awesome members who made all of these mods available to us!
Forum Rules | New Users Guide | XDA Tour | Report Posts​

Re: Sprint GS3 FAQ [WIP] (place holder)
TW ROMS
MB1 odexed blue
MD4 wicked sensations Rom
jellybomb rom
TPR (the people's Rom)
M.O.A.R
clean bean
MSG & CHUBBZ
Blazer Rom
Goodness reborn
MD4 Stock rooted
XPlod a Sony
whiplashh Rom
free gs3
Antivenom Rom
galaxy s fre3
Team Rejects md4 black hole
AOSP ROMS
Slim Bean
Carbon Rom
CM10.1 Nightly builds
LiquidSmooth
AOKP Rom
Sons of Android
BAKED BLACK BEAN
MROM
PARANOID ANDROID
PAC-man Rom
HellyBean
Ubuntu Touch (purely experimental at this point, virtually nothing works yet, but when it does it should be AWESOME! It's worth making a backup and flashing just to get the feel for it)
Vanilla RootBox

Re: Sprint GS3 FAQ [WIP] (place holder)
TW KERNELS
AGAT's Kernel
DeviantKernel
ZEUS Kernel [Deviant Development]
Ktoonsez' KT747
Q&A for ktoonz Thread Here
AOSP KERNELS
BMS Kernel
dkp - d2spr & friends
Ktoonsez' KT747
Q&A for ktoonz Thread Here.

Re: Sprint GS3 FAQ [WIP] (place holder)
MODS
Multi-View
morphology (theming tool)
4 in 1 reboot and volume keys to skip tracks
PRL write enabler
volume keys dedicated camera shutter
uncompressed mms
app2extsd2
home button wake on or off
long press menu to kill apps mod
Device Status= Normal
MB1/MD4 Native Hotspot!!!!
4.2 camera with photosphere flash in recovery. You will have two cameras and two galleries in your app drawer
Completely remove Sprint connections optimizer!

Re: Sprint GS3 FAQ [WIP] (place holder)
PRLs and PRL info
PRLs and info
RADIOS aka MODEMS
LJ7, LI3, LG8, LG2, LEN, LF9 radios found here
MA6 radio, just download and flash in recovery
MB1 radio, just download and flash in recovery
If you see anything I may have missed, please bring it to my attention! I would love for this thread to be a one stop shop, from all the questions that one may have, to every Rom found for this phone and so on. (xda roms/kernels only) I will do my best to keep everything here as to to date as possible
Please don't be afraid to pm me with suggestions, and I love constructive criticism! Thank you to the whole Sprint galaxy S3 community, the best community on xda!

Re: Sprint GS3 FAQ [WIP] (place holder)
Wifi tether
Most "stable" rom / "best" rom
Roms with multiwindow, etc
What it means to be "bricked"
"My phone wont boot up, please help! emergency 911! NOOB!!" - those sorts of thread and common fixes (bad flash, bad download, flashing a rom for another carrier or for the international version)
Sent from my PG06100

Re: Sprint GS3 FAQ [WIP] (place holder)
CNexus said:
Wifi tether
Most "stable" rom / "best" rom
Roms with multiwindow, etc
What it means to be "bricked"
"My phone wont boot up, please help! emergency 911! NOOB!!" - those sorts of thread and common fixes (bad flash, bad download, flashing a rom for another carrier or for the international version)
Sent from my PG06100
Click to expand...
Click to collapse
I like those, except there is no such thing as best or most stable Rom, that is an opinion and will not be touched in this FAQ... I will have links to all roms and kernels available for this device though... thanks for the suggestions... I also will not include what features roms have, it is up to the end user to read the roms op to figure out and understand all the features of roms

Re: Sprint GS3 FAQ [WIP] (place holder)
flastnoles11 said:
I like those, except there is no such thing as best or most stable Rom, that is an opinion and will not be touched in this FAQ... I will have links to all roms and kernels available for this device though... thanks for the suggestions... I also will not include what features roms have, it is up to the end user to read the roms op to figure out and understand all the features of roms
Click to expand...
Click to collapse
Hahaha, you misunderstood :laugh:
Thats why they're in quotes What I meant was to touch on that only so far as to say that asking that is a big no no and that you should read and flash and blah blah all that good stuff
Sent from my PG06100

Re: Sprint GS3 FAQ [WIP] (place holder)
CNexus said:
Hahaha, you misunderstood :laugh:
Thats why they're in quotes What I meant was to touch on that only so far as to say that asking that is a big no no and that you should read and flash and blah blah all that good stuff
Sent from my PG06100
Click to expand...
Click to collapse
Gotcha, yes I will have this covered also... if you didn't notice,I got some free time and decided to go ahead and start posting things to it now...

Alternate carriers
Not sure if there is alternate carriers thread/s but maybe roll them up in this?

Re: Sprint GS3 FAQ [WIP] (place holder)
tazfanatic said:
Not sure if there is alternate carriers thread/s but maybe roll them up in this?
Click to expand...
Click to collapse
All of the carriers have or will have their very own FAQ! If they don't get done soon or have not been done already, I will also help them out over there

flastnoles11 said:
All of the carriers have our will have their very own FAQ! If they don't get done soon our have not been done already, I will also help them out over there
Click to expand...
Click to collapse
Okay was thinking like the OG with porting to US Cellar etc....
How about PRL's and modems?

Re: Sprint GS3 FAQ [WIP] (place holder)
tazfanatic said:
Okay was thinking like the OG with porting to US Cellar etc....
How about PRL's and modems?
Click to expand...
Click to collapse
That's a good thing for post 4, Thank you#

LOVE it! Can we get link to latest drivers? And maybe a rollup to themes?

Re: Sprint GS3 FAQ [WIP] (place holder)
orlzzt said:
LOVE it! Can we get link to latest drivers? And maybe a rollup to themes?
Click to expand...
Click to collapse
I will see what I can do, the drivers can be found in the rooting guide, themes I will add to the post with the modems and prl

CNexus said:
Hahaha, you misunderstood :laugh:
Thats why they're in quotes What I meant was to touch on that only so far as to say that asking that is a big no no and that you should read and flash and blah blah all that good stuff
Sent from my PG06100
Click to expand...
Click to collapse
So that should be a seperate section "What not to ask....EVER!"
Nice job Mr. Flastnoles11! Thread stuck.

Re: Sprint GS3 FAQ [WIP] (place holder)
kennyglass123 said:
So that should be a seperate section "What not to ask....EVER!"
Nice job Mr. Flastnoles11! Thread stuck.
Click to expand...
Click to collapse
Thanks Kenny! Up to 8 questions, I'm sure there are more, but I'm tired now... Roms, kernels, themes list and the like coming tomorrow (may be in the hospital most of the day, so maybe Wednesday)
Edit-updated

Re: Sprint GS3 FAQ [WIP]
Nice work excellent resource you have compilled flastnoles11
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Re: Sprint GS3 FAQ [WIP]
mw86 said:
Nice work excellent resource you have compilled flastnoles11
Click to expand...
Click to collapse
thank you! Just trying to help everyone out! I'm sure there is plenty more that I can add, and will add as I find them
Sprint GS3 FAQ THREAD

Re: Sprint GS3 FAQ [WIP]
flastnoles11 said:
thank you! Just trying to help everyone out! I'm sure there is plenty more that I can add, and will add I find them
Sprint GS3 FAQ THREAD
Click to expand...
Click to collapse
Well you are doing a wonderful job and we hope to see you often in the Kernelizer thread. If its okay by Gman you can be a part of Team Kernelizers itself too. You organize very well and I hope to see this thread flourish.

[ROM][PORT][GB 2.3.8?]_-*CyanMobileX*-_1.1.2 [OCT.22.13]

Welcome Fellow Visionaries to CyanMobileX Gingerbread 2.3.8!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a source build of CyanX - which is CM7 based with added modification from AOSP and AOKP and MORE!!!!
This goes above and beyond your standard CM7 build, added features are:
As you can see this is Gingerbread with so much ICS and Jellybean backported that it has been upgraded 2.3.8 (oh so many options and so little time!)
Notes
- I have not tried the splash screens; It may brick your device because they are form a different device, but It also may work since it is the same screen size
- Dont select any kernel it tells you to in recovery, I will be adding another test version of the rom which has darkside and other GB kernels.
- Can't really think of anything off the top of my head
Bugs
- Settings Won't open? (If you get this problem, please give me a logcat... I tell you how to get one somewhere in this thread)
Original Thread
This rom was ported from the Desire Z Forums. It was source built by @demkantor. Give him a thanks over at his thread
---> http://forum.xda-developers.com/showthread.php?t=2403216
If you're ready for the CyanMobile Experience than lets get to it!!
(SCREENSHOTS WILL BE ADDED LATER)

Downloads & Changelogs
How To Flash This ROM
This ROM is equipped with AROMA INSTALLER , a handy script that allows the user to choose what s/he wants in their new ROM.
The Quick Answer:
Download ROM from link below
Put on root of SD card
Boot into your custom recovery
Wipe all partitions (not always needed but always recommended)
Choose flash zip from SD
Once Aroma begins, select the options you would like
When complete (may take a few minuets) reboot!
Your Done! Enjoy! (First boot may be a little slow)
Past Downloads and Latest Build
Latest Build
Code:
http://goo.gl/qJVaYa
Test Build
Code:
One is coming maybe sometime this week
Changelog
Code:
[B]CyanX-1.0.1[/B]
Initial Public Release (considered Beta)
[B]CyanX-1.0.3[/B]
Fixed annoying keyboard bug (where screen faced portrait when keyboard out)
Updated some apps
Fixed some scripting
General bug fixes
[B]CyanX-1.1.2[/B]
Added Launchers
Added Browsers
Updated Apps
Fixed Some Scripting Bugs
Opening keyboard no longer unlocks phone
Removed Download Mode From Reboot Options
Bypassed Battery Full Bug
As always, Happy Flashing!

Credits and Thank You's
There are many to thank, and yes I will thank the obvious first...
XDA
Google
HTC
Linux and the Open Source Apache License
And the real heroes
Squadzone (Original Creator of CyanMobile)
The Rest of the team
EmoBoiix3
Phiexz
OldDroid
Tj-style
Speed_bot
Psyke83
WillingMagic
Motafoca
TaichiN
island3r
Keyur2Maru
ardX
thekraven
ezeteze
And of last but not least
sellers86 for helping me fix that last damn build error!
and the rest of the helpful people all across XDA that has taught me so much over the years
And Now for the People at the Glacier Threads
ElginSk8r
Coderzs
Cnote74 (This Guy taught me how to port )
Synthetic.Nighmare
Lindinsata (Sorry About the Spelling, I'll change it )
Saranhai
If I've missed you I am REALLY sorry, just tell me and I'll include your name
NOTE
Thanks for reading all this and I hope you enjoy this ROM!
Happy Flashing!

FAQs, Q&A, and Troubleshooting
I know I already posted a 'how to' on flashing this ROM, but I feel I should go into more detail for anyone experiencing bugs
Overly Detailed Method of Flashing CyanX to Your HTC Glacier
Yes the above is overkill, but if you are experiencing an sort of problems this should be your first step before posting bug reports.
I am ocd when it comes to wiping clean and restore very little between ROMs, and it is super rare that I have any issues.
speaking of bug reports....
How To Submit a Bug Report in a Developer Forum
Code:
Prerequisites
Have a rooted HTC Glacier
Have S-off and an engineering bootloader
Have 4ext Recovery
Have a working knowledge of adb and fastboot
Click to expand...
Click to collapse
Steps to flash
Download latest version from second post
Check MD5sum (Windows) - (Linux)
Put on root of SDcard (not in any folder)
Boot to bootloader (fastboot mode specifically)
# fastboot erase system -w # More info on fastboot
# fastboot erase boot
boot to recovery
choose wipe/format > format all partitions (except sdcard)
now flash superwipeG2+ and or AIO Wipe/format tool
Reboot recovery
choose install zip from sdcard
choose CyanXxxx.zip
when Aroma installed ui appears choose what you want
let it flash rom + gapps + whatever
save log when finished
reboot
PROFIT!
Click to expand...
Click to collapse
Yes the above is overkill, but if you are experiencing an sort of problems this should be your first step before posting bug reports.
I am ocd when it comes to wiping clean and restore very little between ROMs, and it is super rare that I have any issues.
speaking of bug reports....
How To Submit a Bug Report in a Developer Forum
Before You Press Submit...
Make sure you can reproduce the bug on a clean flash (yes clean like above)
Make sure you meet all requirements for ROM (very little for this one)
Capture any log possible of event, Aroma log and logcat specifically (explained below)
Post as much detail as you can along with the log (pastebin or .txt or code wraps)
List all info on your bootloader screen
Anything else you can think of that may be causing your problem (that rouge app you installed, when you dropped your phone in the bath, when you through it at the beehive outside school)
And of course know that I'm not being a ****, I want to help you, and I want you to enjoy this ROM. I just need good information to make sure you are problem free!
How To Logcat Like A Pro!!
Simple way, download app from market... but not as helpful
What your after is more than just
Code:
adb logcat myproblem.txt
This is nice but something more helpful
Code:
adb shell dmesg ; adb logcat -b system -b radio -b events -b main
also if there was a reboot or something to this extent
Code:
adb shell cat /proc/last_kmsg > kmsg.txt
Here are some more tips if your unsure
Being I am here to help I don't mind you asking, "Hey this happened and I would like to help find out why, can you help me get a log? etc... etc..."
Common Q & As...
Q. What is that bar on the bottom? How do I get rid of it or change it?
A. Probably referring to the navigation bar, this is found under settings> CyanMobile settings> Interface> Interface tweaks> Navbar tweaks.
Q. Getting annoyed with the boot sound! How do I remove it or change it?
A. CyanMobile settings> Performance Enable boot sound. Or CyanMobile settings> Interface> Choose/Restore bootsound
Q. Ummm... There's no root access for adb... Why?
A. Its off by default, go to Settings> Development> Root access and take your pick.
Q. So I just choose xxx splash screen in Aroma, I don't like it, I don't like the others, how do i get original back?
A. Either flash your original through fastboot or If you want I have another Aroma installer with over 40 more choices including both the G2 and DZ original splash screens Located Here
Q. Just flashed this ROM and saw the bootanimation just run for like 10 minuets... Fix this please!
A. This has been happening with some builds and it depends on what modification you choose in aroma. The ROM will always boot after the initial run through.
Simply plug in phone to computer and it will reboot and go strait to ROM (or reboot otherwise) This is a bug I'm tracking down, just know after first boot there is no issue here.

Last one I think

Great job! PM me about those splash screens so they don't cause anyone trouble!
Sent from my Nexus 4 using XDA Premium 4 mobile app

:victory:
Downloading, installing...... NOW.
---------- Post added at 11:20 AM ---------- Previous post was at 10:22 AM ----------
.....So I can confirm that splash screen will not brick the device.....
But the ROM won't boot either. or maybe I selected one of the kernels.. IDK.
looks pretty wicked. need to play with it. I think it needs to settle down after installing. quickpic seems to crash... definitely need to OC.
---------- Post added at 11:21 AM ---------- Previous post was at 11:20 AM ----------
.....So I can confirm that splash screen will not brick the device.....
But the ROM won't boot either. or maybe I selected one of the kernels.. IDK.
looks pretty wicked. need to play with it. I think it needs to settle down after installing. quickpic seems to crash... definitely need to OC.
Nice ROM! Nice port!

bertscookie said:
:victory:
Downloading, installing...... NOW.
---------- Post added at 11:20 AM ---------- Previous post was at 10:22 AM ----------
.....So I can confirm that splash screen will not brick the device.....
But the ROM won't boot either. or maybe I selected one of the kernels.. IDK.
looks pretty wicked. need to play with it. I think it needs to settle down after installing. quickpic seems to crash... definitely need to OC.
---------- Post added at 11:21 AM ---------- Previous post was at 11:20 AM ----------
.....So I can confirm that splash screen will not brick the device.....
But the ROM won't boot either. or maybe I selected one of the kernels.. IDK.
looks pretty wicked. need to play with it. I think it needs to settle down after installing. quickpic seems to crash... definitely need to OC.
Nice ROM! Nice port!
Click to expand...
Click to collapse
Lol thanks for trying the splash screens.
Also I'm going to release a more tweaked version which will also remove the Kernels that aren't for our device and replace it with ones that are.
The rom will boot if you pick don't change any Kernels
Sent from my HTC Glacier

Hey Nice Job!
Glad there is still some guys working this phone.

I'm glad to see this in the development section. This has some awesome tweaks for a gb ROM. I really hope to see this one get some updates. Either way thanks for the time you put into this port for us.

I'll update this soon. But for rom updates I'll have to rely on the Desire Z maintainer.
Also I'll continue to update it if people really like it. Because there's really no point if no one is going to use it
Sent from my HTC Glacier

Damn nice bro wish I had my mt4g to try it I wanted to try this ROM out before
Sent from my Nexus 4 using Tapatalk

Ok I'm having trouble finding the download link
Sent from my Glacier using xda app-developers app

tinodollar said:
Ok I'm having trouble finding the download link
Sent from my Glacier using xda app-developers app
Click to expand...
Click to collapse
It's in the second post.
Under past downloads and latest build.
It's a goo.gl url.
Sent from my HTC Glacier

tinodollar said:
Ok I'm having trouble finding the download link
Sent from my Glacier using xda app-developers app
Click to expand...
Click to collapse
http://goo.gl/qJVaYa <----Link
Also, does anyone want a update on this? I won't mind blowing it up with tweaks and messing with the kernels, but only if people are going to be using it, otherwise I'm just wasting time

N_otori0us_ said:
http://goo.gl/qJVaYa <----Link
Also, does anyone want a update on this? I won't mind blowing it up with tweaks and messing with the kernels, but only if people are going to be using it, otherwise I'm just wasting time
Click to expand...
Click to collapse
I would like a update. I always keep a gb backup to fall back on when I'm going out and would like this to be it if its at least running near 100%

N_otori0us_ said:
http://goo.gl/qJVaYa <----Link
Also, does anyone want a update on this? I won't mind blowing it up with tweaks and messing with the kernels, but only if people are going to be using it, otherwise I'm just wasting time
Click to expand...
Click to collapse
I would like an update as well. Good ROM man, I guess you need a fix for the not being able to get into settings bug though.
Sent from my myTouch 4G using xda app-developers app

[ROM][4.4.4][KTU84Q][DISCONTINUED][SlimKat - Hercules][OFFICIAL+Weeklies]

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 will find everything you need to know about SlimRoms.
Slim Downloads - Download the ROM, GApps and other Addons.
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 frequently asked questions with answers.
Kernel Source - The source of your device's kernel.
See Post #2 for Known Issues and Installation Notes.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Special thanks to (in no particular order):
The Slim Team
CyanogenMod
prbassplayer
wantowan2
kintwofan
Disclaimer: SlimRoms are not responsible for any damages to your device.

I do not own the SGH-T989, but I do have 3 SGH-i727 Skyrockets, and the Hercules is almost identical. My time is limited, but due to several requests for this, I wanted to share. Please help each other out, and keep the thread friendly and informative.
Installation:
Install a 4.4 compatible recovery, and reboot to recovery afterwards.
Format /system, /data and /dalvik cache.
Flash a compatible radio (see below).
Flash the ROM.
Flash GApps.
Reboot and enjoy!
Known Issues:
Power-off charging animation not working.
You tell me...
Reporting Issues:
Do NOT report issues here if you're running a non-stock kernel, Xposed and/or modules, or any other non-stock mods.
For bug reporting (stock Slim ROM/kernel/GApps only), please use the Slim Bugreport tool, accessible through Settings > SlimCenter > Bugreport to produce a zip file in the phone's storage which you then can upload to the SlimROMs Hercules Subforum for review. Please see Reporting Bugs on the Slim web site for more information.
Any issues please explain with specific details, how to reproduce the problem, and provide a Slim Bug Report (preferred, in the ROM), or a logcat. Good feedback is ESSENTIAL.
Installation Notes:
Radios: Make sure you are running a JellyBean radio or newer (T989: UVMC6 | T989D: TLMC4), and follow the installation instructions linked to in post #1. A thread for flashable radios is here.
Recovery: Recommended recovery: CWM or TWRP.
Superuser: The Slim Team has made it so the Superuser App is not enabled by default, requiring users to intentionally turn on Root access. To enable it, navigate to Settings > Developer Options > Root Access and choose Apps and ADB (even though it may appear selected). For this to work, you need to first go to Settings > About Phone and tap on Build Number several times to gain access to the Developer Options.
Also see here: http://slimroms.net/faq/slimbean/441-how-do-i-enable-root
Kernel: The kernel is based on the Moretz CM-11.0 kernel, but overclocking has been disabled to enhance stability. For sweep2wake, fast charge, and CPU freq/governor control features, I'd recommend [ROOT] Kernel Tweaker from the Play store.
Wi-Fi: Wi-Fi connection dropping issues? Check your region code in Settings > Wi-Fi > (menu key) > Advanced > Wi-Fi region code. It may be set to Europe by default, which uses a different set of Wi-Fi channels than the United States or Canada.
DPI: For information on changing the screen DPI, see here: How to change the screen density (DPI). Beware that some apps may not play nice with custom values, although normally the Slim GApps are modified to tell the Play Store and a couple of other apps that the phone's DPI is always 240.
Enjoy!

(reserved)

Initial test build: http://www.androidfilehost.com/?fid=23578570567714111

Welcome to the Hercules forum and thanks for bringing this ROM back to us. I will be testing this later this evening after work. Also I will get the word out on G+.

big fan of slim cant wait to see what this brings

Initial Impressions
OK after a few hours of testing, here is what I found:
First of all, the instruction to not change the governor on the stock kernel apparently applies to Wild! V6 as well. After installation, boot was just fine. Thinking I could change the governor because this was a custom kernel, I changed the governor to Intellidemand. No problem then either, but after a reboot the phone boot looped. Re-installing the kernel fixed that, but then it happened again. Also the wi-fi setting was not saving my password either. So after getting the phone to boot up (had to install the kernel once more), I set the governor to Interactive. No more boot loops after three reboots. So that was taken care of.
The other issues I encountered were extremely slow charging (only 1% charge in about a 45 minute time frame) and Google Now FCd every time I tried to open it (even after I wiped data & cache). Upon those problems I had to restore my nandroid for now. I do also want to mention some positives. The ROM really does fly, and with Slim mini gapps over 200mb of free ROM space is available so the ROM lives up to its name of "less is more". Video recording was perfect and without any delay. I have been out of the loop for a bit on changelogs, but for those who don't know the new theme engine is still not included in this ROM as of yet. The real dark Slim does work though.
Bottom line this is not yet ready for a DD IMHO, but with tweaking, could be the fastest ROM we have available. I really was almost willing to deal with the bugs because I was so impressed with the speed. The screen wake lag that plagues all the other ROMs did not happen for me here. Thanks again @NoSpamDan, I'll be happy to try future builds as well.

ArtfulDodger said:
OK after a few hours of testing, here is what I found:
First of all, the instruction to not change the governor on the stock kernel apparently applies to Wild! V6 as well. After installation, boot was just fine. Thinking I could change the governor because this was a custom kernel, I changed the governor to Intellidemand. No problem then either, but after a reboot the phone boot looped. Re-installing the kernel fixed that, but then it happened again. Also the wi-fi setting was not saving my password either. So after getting the phone to boot up (had to install the kernel once more), I set the governor to Interactive. No more boot loops after three reboots. So that was taken care of.
The other issues I encountered were extremely slow charging (only 1% charge in about a 45 minute time frame) and Google Now FCd every time I tried to open it (even after I wiped data & cache). Upon those problems I had to restore my nandroid for now. I do also want to mention some positives. The ROM really does fly, and with Slim mini gapps over 200mb of free ROM space is available so the ROM lives up to its name of "less is more". Video recording was perfect and without any delay. I have been out of the loop for a bit on changelogs, but for those who don't know the new theme engine is still not included in this ROM as of yet. The real dark Slim does work though.
Bottom line this is not yet ready for a DD IMHO, but with tweaking, could be the fastest ROM we have available. I really was almost willing to deal with the bugs because I was so impressed with the speed. The screen wake lag that plagues all the other ROMs did not happen for me here. Thanks again @NoSpamDan, I'll be happy to try future builds as well.
Click to expand...
Click to collapse
Thanks, I appreciate the testing and feedback!
Let me first say that details are everything, especially when I don't have a test phone available...
I am looking for bugs that exist in the as-built ROM, and therefore I am unable to provide any support for 3rd party kernels... This could have caused most of the issues you experienced.
Was there a problem with the stock CM-11.0 kernel bundled into the ROM, aside from the known governor switching issue? If so, the built-in Slim Bug Report tool (Settings > SlimCenter > Bugreport) will produce a zip file you can upload here for the time being for review. Please see Reporting Bugs on the Slim web site for more information.
For random reboots (RR's), you can also try using Bootlog Uptime to automatically dump /proc/last_kmsg for you to review/upload.
The Google Now issue shouldn't have anything to do with the ROM itself, that is in GApps. And if you were using the mini-gapps package, did you install Google Search separately? According to the TRDS GApps thread, it's not included in the mini package, and you could have been missing some key library files from the GApps package.
What version of KK4.4 GApps did you install? You said mini, but was it v155, v157, v160?
For now, I would recommend using the beta GApps with Unofficial builds until an Official ROM version is released. Please bear in mind that @dankoman has been producing new beta TRDS GApps versions quite often. His discussion thread is here.
What I really need are bug reports and logs using only the stock Slim ROM/kernel/GApps... Unfortunately, without these, I won't be able to provide effective support to try and make this ROM better, much less try to get the Hercules officially supported on the Slim site.
Thanks again!

NoSpamDan said:
Thanks, I appreciate the testing and feedback!
Let me first say that details are everything, especially when I don't have a test phone available...
I am looking for bugs that exist in the as-built ROM, and therefore I am unable to provide any support for 3rd party kernels... This could have caused most of the issues you experienced.
Was there a problem with the stock CM-11.0 kernel bundled into the ROM, aside from the known governor switching issue? If so, the built-in Slim Bug Report tool (Settings > SlimCenter > Bugreport) will produce a zip file you can upload here for the time being for review. Please see Reporting Bugs on the Slim web site for more information.
For random reboots (RR's), you can also try using Bootlog Uptime to automatically dump /proc/last_kmsg for you to review/upload.
The Google Now issue shouldn't have anything to do with the ROM itself, that is in GApps. And if you were using the mini-gapps package, did you install Google Search separately? According to the TRDS GApps thread, it's not included in the mini package, and you could have been missing some key library files from the GApps package.
What version of KK4.4 GApps did you install? You said mini, but was it v155, v157, v160?
For now, I would recommend using the beta GApps with Unofficial builds until an Official ROM version is released. Please bear in mind that @dankoman has been producing new beta TRDS GApps versions quite often. His discussion thread is here.
What I really need are bug reports and logs using only the stock Slim ROM/kernel/GApps... Unfortunately, without these, I won't be able to provide effective support to try and make this ROM better, much less try to get the Hercules officially supported on the Slim site.
Thanks again!
Click to expand...
Click to collapse
Yeah I was afraid you might bring the logs up, and rightfully so. Reason that I did not use the built in kernel is that I have NEVER had good experiences with stock kernels from CM. Plus with the limited governor availability, I was hoping Wild! would eliminate that problem. I was also unaware of Bootlog Uptime or I would have used it to help with this situation.
On Gapps, I used these from the Slim ROMs web site: http://slimroms.net/index.php/downloads/dlsearch/viewdownload/1150-addons4-4/12060-slim-mini-gapps-4-4-4-build-6-112
Google Now wasn't included so I restored it via Titanium Backup. After the FCs, I wiped the data. Still no luck. I tried to uninstall it but when I checked settings/apps, it was still showing as installed. I should have just fresh installed it from Play or better yet, used the Banks Gapps I already had. At any rate, I know I could have fixed that problem if I had tried other things.
Any idea what might have caused the slow charging? I've had that happen on official CM as well.

ArtfulDodger said:
On Gapps, I used these from the Slim ROMs web site: http://slimroms.net/index.php/downloads/dlsearch/viewdownload/1150-addons4-4/12060-slim-mini-gapps-4-4-4-build-6-112
Google Now wasn't included so I restored it via Titanium Backup.
Click to expand...
Click to collapse
Yeah, those GApps are pretty outdated, but should still work. TiBu on the other hand, can be pure evil sometimes...
After the FCs, I wiped the data. Still no luck. I tried to uninstall it but when I checked settings/apps, it was still showing as installed. I should have just fresh installed it from Play or better yet, used the Banks Gapps I already had. At any rate, I know I could have fixed that problem if I had tried other things.
Click to expand...
Click to collapse
OK. Now (Quicksearchbox.apk) is a System App, so yeah, I can see trouble with it if restored.
Any idea what might have caused the slow charging? I've had that happen on official CM as well.
Click to expand...
Click to collapse
Not off-hand. I take it you've tried different chargers/cables...? There's an app on XDA here called Skyrocket Charger Test that, while it's labeled 'Skyrocket', based on what it queries for information, might work on the Herc to check the charging rate and type. I believe it also works on the Note 1 SGH-i717... Worth a shot to test chargers and cables for issues. It's saved me many times.

NoSpamDan said:
Yeah, those GApps are pretty outdated, but should still work. TiBu on the other hand, can be pure evil sometimes...
OK. Now (Quicksearchbox.apk) is a System App, so yeah, I can see trouble with it if restored.
Not off-hand. I take it you've tried different chargers/cables...? There's an app on XDA here called Skyrocket Charger Test that, while it's labeled 'Skyrocket', based on what it queries for information, might work on the Herc to check the charging rate and type. I believe it also works on the Note 1 SGH-i717... Worth a shot to test chargers and cables for issues. It's saved me many times.
Click to expand...
Click to collapse
Well thing is, on other ROMs like PA or Beanstalk 4.4 builds I get about 40% an hour charge. I use two different chargers at home & work, both Samsung with no issues. The slow charging issue is one I've only encountered with official CM (especially 4.4 nightlies), an old Beanstalk 4.3 ROM and unofficial Carbon 4.2 build back from last fall.
On TB it really is both a blessing and a curse sometimes!

Only issue is found is SD card usage. I don't have external SD card btw
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

smokenbiskits said:
Only issue is found is SD card usage. I don't have external SD card btw
View attachment 2858649
Click to expand...
Click to collapse
Thanks for the report.
I take it you did wipe /data or perform a factory reset upon installation? This will not wipe your internal SD card (music/photos/etc)...
Sometimes just a dalvik and cache wipe from recovery fixes this. A log/bugreport might help. Did you try clicking on that SDCard entry to see what app or process it says is running? Do you have Outlook installed or Exchange mail configured?
And I couldn't help but notice, are you running Juice Defender? FYI many have reported worse battery life on KitKat with that... I purchased the full version myself back when I switched from GB to ICS, but ended up ditching it when JB came along, and never looked back.
Everyone's usage/situation is different...

NoSpamDan said:
Thanks for the report.
I take it you did wipe /data or perform a factory reset upon installation? This will not wipe your internal SD card (music/photos/etc)...
Sometimes just a dalvik and cache wipe from recovery fixes this. A log/bugreport might help. Did you try clicking on that SDCard entry to see what app or process it says is running? Do you have Outlook installed or Exchange mail configured?
And I couldn't help but notice, are you running Juice Defender? FYI many have reported worse battery life on KitKat with that... I purchased the full version myself back when I switched from GB to ICS, but ended up ditching it when JB came along, and never looked back.
Everyone's usage/situation is different...
Click to expand...
Click to collapse
Yes to wipe everything except internal SD.
I will try a dalvik/cache wipe/battery stats and see if it helps.
Don't have either of those email clients installed.
Clicking on SD card entry in battery just shows cpu uptime for SD Card, not specific process.
I'll remove juice defender after the wipes above work/don't work, don't want too many variables changing while trying to troubleshoot. :angel:

LOL, yes, one step at a time is good. else you can end up with no clue at all

Oh, I just saw "battery stats"... and wiping those has no effect in Android 4.4. Google debunked that some time ago. See here. Recharging the device will reset the battery usage stats in Settings > Battery.
I used to wipe the battery stats myself, and I honestly didn't know there were still recoveries that still had that built in (TWRP maybe) since I've been on PhilZ Touch CWM recovery myself for a long time. No Fix Permissions either, wouldn't you know (not a bad thing, actually)...
I sure did like my placebo effect, though. I still miss it, lol.

The Dalvik/cache wipe fixed SD card issue... Thanks

First, thanks for helping us all out and working on bringing us this ROM. Tried it out today and was impressed by how fast it booted and its responsiveness. Flashed through TWRP 2.7.1.0 along with newest beta slim mini gapps. Full wipe/clean install. A few things I noticed:
1) Native superuser doesn't function. Tried going into settings>advanced options>superuser and auto-allowing apps permissions...no go. Unable to create logcat/bugreport for this issue as they both require root. Fixed by flashing Chainfires SuperSU zip through TWRP
2) Battery charge speed seemed normal here
3) I live in US and wifi region code was set to Europe after install.
4) In your OP you mention radios not related to our model. The newest radio for T989 is T989UVMC6
5) Something not specific to your ROM, but with all recent ROMs (CM related?) stock messaging app no longer turns data on to send/receive MMS messages. Again, nothing on your end, just felt the need to bring attention to it.
Thanks again for your work

ive been on this all day today without any problems! slims as good it was before

HipHopAnonymous3 said:
First, thanks for helping us all out and working on bringing us this ROM. Tried it out today and was impressed by how fast it booted and its responsiveness. Flashed through TWRP 2.7.1.0 along with newest beta slim mini gapps. Full wipe/clean install. A few things I noticed:
1) Native superuser doesn't function. Tried going into settings>advanced options>superuser and auto-allowing apps permissions...no go. Unable to create logcat/bugreport for this issue as they both require root. Fixed by flashing Chainfires SuperSU zip through TWRP
2) Battery charge speed seemed normal here
3) I live in US and wifi region code was set to Europe after install.
4) In your OP you mention radios not related to our model. The newest radio for T989 is T989UVMC6
5) Something not specific to your ROM, but with all recent ROMs (CM related?) stock messaging app no longer turns data on to send/receive MMS messages. Again, nothing on your end, just felt the need to bring attention to it.
Thanks again for your work
Click to expand...
Click to collapse
Thank you much for the feedback.
1) You have to enable Superuser through Developer options. See installation notes in post #2, with a link to Slim's FAQ on it.
2) Good!
3) I've seen this before, and will look into it, although as you said, if you drill into the Wifi > Advanced > Region code settings, you can change it to whatever. So, low priority.
4) I'll look at the assert script for the radio version. Can you link the radio thread please?
5) I haven't heard of this. I don't believe it affects the Skyrocket...? Does this happen on the recommended radios?
I have a new build compiling with a "stock-ish" version of the Moretz kernel (no over clock/undervolting).
It has sweep2wake, fast charge, more governors, and reportedly better Bluetooth support (with SR users).
I'll post it for testing when it's ready for those interested...
I don't have any volunteers for testing (yet). . If you want to volunteer, you should be able and willing to clean flash at times 3-4 builds in a day, be able to capture logs and send them. Normal testing would be occasional builds, unless there was a major issue.
Looking for 3 or so testers to help possibly get this into the Slim weekly cycle.
Cheers!

[ROM] [OFFICIAL] CYANIDE L RC-20.0[5.1.1r18] (09/25/15)-FLOAT-WINDOW ROM-D2ATT

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WELCOME TO CYANIDE L
ROM INFORMATION
Cyanide L is the brainchild of XDA member @rogersb11. Based on CyanogenMod, and packed full of features from the wonderful custom ROM teams we have all come to know and love. This ROM is just getting started and I will update frequently as things progress along into the beast we know this will be.
I (TheGeekyNimrod) will be your d2att device maintainer and working on the theming of the ROM as well. It is important to note, that I have built this specifically for d2att and can be used on d2tmo (see info near the bottom of this post). I do not know if it will work for any other device, and cannot provide support for you if you have flashed it on another d2 variant.
KERNEL INFORMATION
Cyanide L comes packaged with the latest Shift Kernel, also built by @rogersb11. With the latest from CM, as well as his special touch, Shift has what it takes to get the job done. Note, that if you report bugs or issues with the ROM, I will not provide support if issues are related to using a different kernel with the ROM. Kernel specific thread can be found right here.
FEATURES LIST
Code:
App Circle Bar
*Gesture Anywhere
*Gesture Lockscreen
*Heads Up Notifications
*Shift Kernel by @rogersb11 built with Linaro
*Cyanide L Material Dark UI (Work in Progress)
*CustomToast, System, and ListView Animations
*Custom Power Menu Options
*Custom Quick Settings Tiles
*Colorized Statusbar Icon Options
*Colorized Notification Headers and Icons Options
*Screen Recorder
*Custom Navbar with custom actions and shorcuts
*Theme Engine
*PIE Controls (WIP)
*MIUI Style Custom Carrier Label in Statusbar
*Long Click Support in Statusbar Header
*Cyanide Dungeon
*Much Much MUCH More...
GOOGLE PLUS COMMUNITY - This is where you will find the latest changelogs and other info and discussion about Cyanide L ROM. Device specific changes I will always list right here in the thread. But general changelogs will always be posted in our G+ community.
DOWNLOADS
**Special note to d2tmo users: Due to unforeseen issues building for your device specifically, the build below will be the only one I have for you. It will flash, it will work. Only difference is your phone will show that you have an SGH-I747. You can edit this in your build.prop through RootExplorer or similar apps if you want to change it.**
CYANIDE L ROM D2ATT and D2TMO - Get the latest build here. (Current build RC-20.0) ... Older builds can be found in the same folder. Just click CyanideL and you can see all previous builds.
Developer Edition
If you use Cyanide Blackout this is a small theme to supplement it and fix some black text on black background issues. It also themes some other apps but main purpose is so be used with Blackout option. This is purely an Add-on theme made for Cyanide Blackout in the ROM Blackout Add-on Theme
Gapps - Use the Gapps of your choice. Personally, I test this ROM with these Gapps (BaNkS 3/28), but it should work just fine with most Gapps.
Extra: CyanideBlue Theme for Theme Engine - Grab this awesomeness here
DISCLAIMER
You are choosing to install this ROM on your own merit. It is up to you to know the ins and outs, and know how to properly handle issues that may crop up. Neither Cyanide, your neighbor, or the Starbucks barista can be held liable for the following including, but not limited to: Exploding batteries, spontaneous combustion, soft brick, hard brick, one brick, two brick, red brick, blue brick.
ROM INSTALLATION
IF COMING FROM ANY OTHER ROM
1) WIPE DATA/FACTORY RESET
2) WIPE SYSTEM
3) Wipe Cache/Dalvik Cache
4) Flash the ROM and Gapps.
5) Reboot and PROFIT!!!!
6) Enjoy
IF UPDATING FROM OLDER VERSION OF CYANIDE
1) Wipe Dalvik, Cache, (system maybe)
2) Flash ROM & Gapps
3) Reboot and PROFIT!!!!
KNOWN BUGS
Same as CM and also THIS POST RIGHT HERE - Please also read Post #3 before reporting bugs.
NOTE: The stock camera is currently not working. This means that Snapchat, Instagram, and others may not be able to take pictures from within the app itself. Most third party apps from the PlayStore such as Open Camera will work for pictures. There is NO VIDEO RECORDING with any apps currently. IF YOU COMPLAIN ABOUT THE CAMERA ISSUES WHILE THIS RED TEXT STILL EXISTS IN THE OP, I WILL MOCK YOU AND LAUGH YOU OUT OF THE THREAD. Seriously, it's been done to death, and I'm no longer tolerating it by being quiet. I will laugh at you openly.
ALSO NEEDS TO BE NOTED that yes, apparently Xposed for Lollipop is a thing now. BUT PAY ATTENTION TO THIS PART RIGHT HERE: Under NO CIRCUMSTANCES should we ever see a bug report or complaint if you are using Xposed. It is well known that Xposed doesn't always play nicely, and if you are using it and complain about some kind of bug, I will laugh you out of the thread. I hate being crass, but after dealing with so many repeat moronic questions, I felt like I should go ahead and state this now.
,
Thank you and enjoy!!
If you like our work, then maybe you would like giving a small donation? :victory:
Donate to @rogersb11
Donate to @TheGeekyNimrod
​
XDA:DevDB Information
Cyanide L, ROM for the AT&T Samsung Galaxy S III
Contributors
TheGeekyNimrod, rogersb11
Source Code: https://github.com/CyanideL
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Nightly
Current Stable Version: RC-7.5
Stable Release Date: 2015-03-15
Beta Release Date: 2014-12-21
Created 2014-12-21
Last Updated 2015-09-25

Screenshots
SCREENSHOTS
Home Screen
Settings
CyanideMods
Cyanide Central
App Circle Bar
Pie
Notification Drawer

FAQ, Troubleshooting, Bug Reporting
Frequently Asked Questions
Q: Does this ROM work on [insert device name here]?
Answer: This ROM is currently only supporting d2att and partially, d2tmo. If you choose to flash this on any other device, may Android have mercy on your soul.
Q: Why aren't my CM12 themes looking right?
Answer: Theme Chooser is still in its early stages and more and more items are being exposed for theming. So it's possible that some things may not look quite right still when applying a theme. Try going to the default system theme, reboot, apply your CM12 theme, and reboot once more.
Q: When will the next update be out?
Answer: When it's out and the OP is updated. Do not expect nightly builds or even weekly builds. I'm not going to run a build a day when it will make virtually nothing different. When I update, there will be good reason and timing for it. So please, don't ask.
Q: Can I use a custom kernel with this ROM?
Answer: Yes, you may. Though this rom comes packaged with the Shift kernel, you may run other kernels instead. HOWEVER, please pay attention to the troubleshooting section below concerning kernel use.
Q: Can you add [insert feature here]?
Answer: We are always open to feature suggestions. HOWEVER: Keep in mind that feature you have come to love in previous iterations of Android may not be ported forward for use in Lollipop yet. If you see a feature you want, and can point to somewhere that it's being used in a Lollipop rom, then we can definitely look into it. Otherwise, patience young grasshopper.
TROUBLESHOOTING
This ROM is still in the early stages of development, so you can expect some bugs to pop up here and there. Here are some guidelines to remember when reporting bugs to this thread. Please read carefully.
**Before reporting a bug, be sure you have tried the following:
1) If you dirty flashed, go back and clean flash first.
2) If you are running a custom kernel, flash the Shift kernel from the OP and see if that solves your issues.
3) If the issue seems app related, uninstall the app and reinstall from the PlayStore. I won't give any help if your apps mess up from using TiBu. This doesn't constitute a clean install of an app.
4) Read through the thread to see if your issue has been addressed before and if their is currently a solution for it.
BUG REPORTNG
**I WILL NOT LOOK AT BUG REPORTS THAT HAVE NOT TRIED THE PREVIOUSLY LISTED STEPS OR LOGS THAT COME FROM A COMBINATION OF ANYTHING OTHER THAN THE ROM AND THE SHIFT KERNEL COMBO. I WILL ALSO NOT TAKE BUGS FROM PEOPLE WHO HAVE FLASHED THIS ON AN UNSUPPORTED DEVICE**
When you report a bug, be detailed about it. Simply stating "This is not working right" does not help me any at all, and I will probably just ignore the post. Be prepared to grab a logcat if asked or to provide me with the steps to reproduce the issue on my own device. If you don't know how to get a logcat, Google is your friend and there are multiple ways to do so. Also, search the thread, and search it again before reporting a bug, to be sure it hasn't already been addressed. No need to clog the thread with 10 people saying "This isn't working right".
PLEASE REFRAIN FROM PERSONAL GRIEVANCES IN THE THREAD. WE HAVE HAD RECENT ISSUES WITH THIS AND IT HAS BEEN SHOWN THAT IT WILL NOT BE TOLERATED ANYMORE.

Does this work with f2fs?
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

gvsukids said:
Does this work with f2fs?
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
I built the included kernel for this and it should support f2fs just fine. Has all cm features with faux sound mod and net tweaks. It'll include OC/UC, OV/UV in the near future

Does this ROM have pie controls? I would be soooooo happy :angel:

MrBigWaffles said:
Does this ROM have pie controls? I would be soooooo happy :angel:
Click to expand...
Click to collapse
Not yet, but will in the future. This ROM is just coming together (as are so many LP builds). And new features will be introduced quite often in future releases.
Stick around, it's going to get awesome.
Sent from my SAMSUNG-SGH-I747

MrBigWaffles said:
Does this ROM have pie controls? I would be soooooo happy :angel:
Click to expand...
Click to collapse
Have you seen a lollipop rom with pie yet? Serious question. I've been looking but haven't seen it brought up to 5.0 yet. I haven't had time to try and bring it up myself but if you know a rom with it already I'll look into it

Great working ROM
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

gvsukids said:
Great working ROM
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
Great to hear :thumbup:
Sent from my SAMSUNG-SGH-I747

VERY smooth so far, appreciate the work put into this rom and look forward to the updates.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

So I'm guessing there's camera issues in this ROM as well?

Purplezigar said:
So I'm guessing there's camera issues in this ROM as well?
Click to expand...
Click to collapse
I don't have this device but @TheGeekyNimrod said that it half works. Most times it's ok but sometimes it crashes and he said something about the video recording but I can't remember what. It's a CM bug. I always stay up on Slim and CM source so I'm constantly looking for a fix. Camera is a stability issue all over AOSP L at the moment. Works on my Note 2 great but gps is wonky lol. It's always something but it's VERY early in the Lollipop game so bugs are to be expected. All in all it's pretty sweet so far. I didn't think it would be as polished as it is just yet.

Purplezigar said:
So I'm guessing there's camera issues in this ROM as well?
Click to expand...
Click to collapse
I use nexus camera or camera fx and there is no video recording, and sometimes I press twice for a picture and sometimes the flash stays on
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

Purplezigar said:
So I'm guessing there's camera issues in this ROM as well?
Click to expand...
Click to collapse
Camera is hit and miss like it is with most L ROMS. No solid, one and done fix yet.
Sent from my SAMSUNG-SGH-I747

Dang! Can't believe I didn't see this last night! I know what I'll be doing when I get home today When I flash ROM and gapps, do I needed to flash SuperSU or is it built in?

jondroid2 said:
Dang! Can't believe I didn't see this last night! I know what I'll be doing when I get home today When I flash ROM and gapps, do I needed to flash SuperSU or is it built in?
Click to expand...
Click to collapse
Superuser is built in.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

gvsukids said:
Superuser is built in.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
jondroid2 said:
Dang! Can't believe I didn't see this last night! I know what I'll be doing when I get home today When I flash ROM and gapps, do I needed to flash SuperSU or is it built in?
Click to expand...
Click to collapse
Yes, thankfully I think we're past having to flash the update SuperSU every time lol. Always good to have on hand, but also good to have one less thing to flash

AOSP keyboard force closes.

bloodstorm666 said:
AOSP keyboard force closes.
Click to expand...
Click to collapse
What gapps did you flash? The one in op does not have this issue.
Sent from my SAMSUNG-SGH-I747 using Xparent Cyan Tapatalk 2