[ROM][d2refreshspr][6.0.1]Team OctOS Oct-M
{
"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"
}
Disclaimer: OctOs is a WIP. It has been evaluated as being stable, and is suitable for daily use in most cases. While it may be considered stable, there may be unknown bugs. The development team is not responsible for any damage to your device or your information.
Click to expand...
Click to collapse
Team OctOs presents Oct-M.
We maintain a current release record and change-log on our website: http://www.teamoctos.com
- Please Do Not Mirror our files without talking to us. We can do that ourselves should we desire to. -
Team OctOs would like to thank Team Blackout for the use of their Blacked Out Nexus Launcher & for saving eyes one app at a time!
You can get all the TBO goodies here as well as the TBO Updater http://teamblackedout.com/ #whiteuimustdie
TBO thread http://forum.xda-developers.com/showthread.php?p=41545802
Frequently Asked Questions
Q: Is this Android 6 (Marshmallow)?
A: Yes, this is Android 6.0.1
Q: What code is OCT-M based on?
A: Starting with Oct-L, we've rebased OctOs on the CyanogenMod 12.1 code. Oct-M is based on CyanogenMod 13.
Q: What happened to AOSP?
A: All Android code is based on the Android Open Source Project (AOSP). Under previous releases, we tried very hard to limit the number of "Not from Google directly" repositories that we used. Unfortunately, issues with devices, the need for Code Aurora Foundation (CAF) repositories for Qualcomm devices, and compatibility issues meant fighting code more often than not. We decided that since the code-base for many repositories were the same across most ROMs, picking a starting point to build the user experience on outweighed the desire to craft code from scratch, or fix broken code to make it work with other changes we already had.
Q: Why isn't there XYZ feature.
A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it
Q: But XYZ and all the others have..
A: ROM developers build something they want to use. The ROM developer that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't include (or don't want to include), feel free to use XYZ ROM, or build your own custom version of Oct-M.
Q: Superuser or SuperSU?
A: Team OctOs uses SuperSU and is installed automatically.
Bugs:
Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.
Logs, Logcat, and the Android Debugging Bridge (ADB)
Like any other OS, Android has multiple log files that are generated and record the goings-on of the system. As a user, you have two basic ways to view and pull these to send to us. Without the information in the logfiles, there simply is not a whole lot of information to go on.
Log file APKs
Team OctOs recommends SysLog from the Android Market. This application will allow you to selectively pick any (or all) of the system logs, compress them into a .ZIP file, and allow you to save, email, move to your Copy/DropBox/Cloud Storage account, etc.
ADB Logcat
The Android Debugging Bridge (ADB) is a powerful tool available from Google as part of the Android Software Development Kit (SDK). Used for many things, being able to selectively see, in real-time, what your device is doing cannot be downplayed. While there is more setup involved, if you are doing consistent ROM flashing, you really should invest the time to get setup properly to do it.
ADB Logcat tutorial here: How to create a logcat log
Basic Instructions:
Download ROM .zip file and MD5 file, and grab your favourite Opengapps package http://opengapps.org/
Reboot to Recovery (Note: Use Reboot to Recovery from Power Menu, Hardware-based boot to recovery, or adb reboot recovery - ROM Manager or similar software is NOT supported)
--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---
Factory Reset from TWRP
Flash ROM and GApps .ZIP files
Reboot
FOR SPH-L710T
Install: TO INSTALL
Please download Our twrp recovery made for the Spark S3 https://www.teamoctos.com/supported-devices/samsung/galaxy-s3/sprint-galaxy-s3-triband-d2refreshspr/twrp-recovery/
with out this recovery you can not use the d2refreshspr rom. to flash other roms you will need to continue to use the d2spr recovery until they decide to use our device trees.
install rom https://www.teamoctos.com/supported-devices/samsung/galaxy-s3/sprint-galaxy-s3-triband-d2refreshspr/rom/ this does have an aroma installer for you to pick your carrier you might have to toggle AIRPLANE mode after flash.
I hope I dont have to explain more on how to flash a rom.
Starting with Oct-M we have removed the aroma installer. It was causing issues across carriers. We're trying to figure it out. All carriers should have working data with the exception of "possibly" sprint prepaid.
!NOTE! This ROM is for the d2refreshspr! Also known as the "SPARK/Tri-band"! The standard d2spr has it's own thread!
DOWNLOADS
Release builds:
https://www.teamoctos.com/release/
Weeklies can be found here:
https://www.teamoctos.com/weekly-builds/
Gapps:
http://opengapps.org/
The Oct-M ROM installation script will automatically wipe /system, /cache, and /data/dalvik-cache. There is no need to do these before or after flashing the ROM unless you are instructed to by your GApps Provider
The foundation of the Android OS is the fact that is it open-source. We have all code we use internally in the creation of Oct-M available on our GitHub repositories.
Unless otherwise specified, all Oct-M builds use the device's stock CyanogenMod 13 kernel.
Kraken kernel source code can be found here: https://github.com/Oct-mm
Team OctOs GitHub - http://www.github.com/Team-OctOs
Team OctOs Gerrit Review - http://www.teamoctos.com:8080
Team OctOs GPLv2 License - http://www.teamoctos.com/license/
Team OctOs Patreon Campaign - https://www.patreon.com/TOctOs
Want To Build Your Own?
Check out the ReadMe on our GitHub for Instructions
Special thanks to
Our testers, without which, there would be no public releases for OctOs
We would also like to thank
Opengapps
CyanogenMod
OmniROM
LiquidSmooth
TeamBlackout
Anyone else who has ever submitted Open-Source code
Click to expand...
Click to collapse
Follow Us at the various websites below!
XDA:DevDB Information
Oct-M, ROM for the Sprint Samsung Galaxy S III
Contributors
bthorne79, CjKacz, canodroid15, hedwig34
Source Code: http://www.github.com/Team-OctOs
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod 13
Version Information
Status: Stable
Current Stable Version: OCT-M R2
Created 2015-07-14
Last Updated 2016-08-27
I'm sure there are spark s3 users everywhere jumping out of their seats with excitement right now.
Nice work.
So nice to be a part of this team. Thanks for everybody's hard work.
First of all just wanted to say thanks for the hard work. Been using this rom for a while now. I must say the new recovery makes things easier. Only problem I have is data won't stick. I have to toggle data after boot in order for it to work. Plus I can't receive mms on 4g on vm. Can anyone confirm mms working on vm 4g? Once again thanks for your hardwork. Imo this is the best rom out there
lilrich17892 said:
First of all just wanted to say thanks for the hard work. Been using this rom for a while now. I must say the new recovery makes things easier. Only problem I have is data won't stick. I have to toggle data after boot in order for it to work. Plus I can't receive mms on 4g on vm. Can anyone confirm mms working on vm 4g? Once again thanks for your hardwork. Imo this is the best rom out there
Click to expand...
Click to collapse
MMS has to do with apns i would check to make sure they are correct if I remember they followed the ones from the zip y'all had to flash
Sent from my SGH-T999 using XDA Free mobile app
bthorne79 said:
MMS has to do with apns i would check to make sure they are correct if I remember they followed the ones from the zip y'all had to flash
Sent from my SGH-T999 using XDA Free mobile app
Click to expand...
Click to collapse
I didn't see an option to check the apn settings. Couldn't I back up my apn settings and restore them after I flash this Rom?
lilrich17892 said:
I didn't see an option to check the apn settings. Couldn't I back up my apn settings and restore them after I flash this Rom?
Click to expand...
Click to collapse
Settings/ mobile network / access point names
Sent from my SGH-T999 using XDA Free mobile app
Nice.
I cannot say enough positive things about this rom. It is buttery smooth and everything works. Stable and feature rich. I really like Team OctOS philosophy and greatly appreciate the support of our triband. Thank you much.
lilrich17892 said:
First of all just wanted to say thanks for the hard work. Been using this rom for a while now. I must say the new recovery makes things easier. Only problem I have is data won't stick. I have to toggle data after boot in order for it to work. Plus I can't receive mms on 4g on vm. Can anyone confirm mms working on vm 4g? Once again thanks for your hardwork. Imo this is the best rom out there
Click to expand...
Click to collapse
The data seems to not stick ONLY if we keep the LTE as preferred. If we switch to 3g (or 1x, but nobody cares about that) as the preferred network and reboot, the phone will connect back to 3g (or 1x) automatically after reboot. However, if its LTE preferred, the data won't stick after reboot. I don't know if the devs can do anything about this. but it is not that big of deal anyway. I got used to it
As for the MMS, I can confirm it's working on 4g on vm. I followed installation instructions step by step (including factory reset) and picked virgin in the aroma options. I didnt need to touch APNs.
Everything else is just perfect. thanks a lot!
just installed this on virgin mobile and I can only send mms it will not let me receive it can someone please point me in the right direction on l710t not sure what to do also theres a new build up m4 how do I flash so I don't lose all of my stuff? is there a way? sorry for noob questions
hilla_killa said:
just installed this on virgin mobile and I can only send mms it will not let me receive it can someone please point me in the right direction on l710t not sure what to do also theres a new build up m4 how do I flash so I don't lose all of my stuff? is there a way? sorry for noob questions
Click to expand...
Click to collapse
Updates usually you can just flash and wipe cache and dalvik. Unless the dev suggests a clean flash.
Sent from my Nexus 9
madbat99 said:
Updates usually you can just flash and wipe cache and dalvik. Unless the dev suggests a clean flash.
Sent from my Nexus 9
Click to expand...
Click to collapse
Ckean flash this build, too much has changed since the last one
hilla_killa said:
just installed this on virgin mobile and I can only send mms it will not let me receive it can someone please point me in the right direction on l710t not sure what to do also theres a new build up m4 how do I flash so I don't lose all of my stuff? is there a way? sorry for noob questions
Click to expand...
Click to collapse
I'm going to try downloading the rom again but weird issue. In the aroma installer it would terminate because it said I have the spr model. Which I definitely don't.
Kreatur3 said:
I'm going to try downloading the rom again but weird issue. In the aroma installer it would terminate because it said I have the spr model. Which I definitely don't.
Click to expand...
Click to collapse
Have you odin flashed the sprint .tar? Like nd8 or nj2? That's likely why.
Sent from my Nexus 9
madbat99 said:
Have you odin flashed the sprint .tar? Like nd8 or nj2? That's likely why.
Sent from my Nexus 9
Click to expand...
Click to collapse
I might have ages ago. So if I had I would flash the d2spr version?
I have the L710T currently running NF4
Kreatur3 said:
I might have ages ago. So if I had I would flash the d2spr version?
I have the L710T currently running NF4
Click to expand...
Click to collapse
Did you flash our new TWRP? Its on the website with the ROM.
madbat99 said:
Have you odin flashed the sprint .tar? Like nd8 or nj2? That's likely why.
Sent from my Nexus 9
Click to expand...
Click to collapse
canodroid15 said:
Did you flash our new TWRP? Its on the website with the ROM.
Click to expand...
Click to collapse
Yes. I flashed the required recovery prior to trying to flash the rom.
@Kreatur3 did you odin the new d2refresh twrp or just flash it? and what version of twrp are you coming from? already running a custom rom or freshly rooted?
canodroid15 said:
@Kreatur3 did you odin the new d2refresh twrp or just flash it? and what version of twrp are you coming from? already running a custom rom or freshly rooted?
Click to expand...
Click to collapse
I flashed it coming from philz. That part went fine. Was able to boot back into recovery and TWRP was there. Running a custom rom now. I could odin flash the stock boost tar.
@Kreatur3 I need to know exactly what ROM you're on now please
Related
This is an unofficial build of Omni Rom based on KitKit 4.4.2. There is no official support for the d2 variants. Props to androidsftw for picking apart what was needed for our d2s.
I am not the dev of this rom, all I did was add in necessary device/vendor/d2 files for d2. This is not a port, everything has been built from source.
As with all things root, I am not responsible for anything that happens while flashing this rom. You take responsibility for your actions. Nandroid is your friend.
----------------------------------
Downloads:
Omni Rom for the D2LTE - Droidhype Roms
GAPPS 4.4.2 - PA 0-Day
SuperSU - Chainfire
Kernel (optional) - BMS
----------------------------------
Installing for the first time? Grab the newest full zip from the D2LTE directory. For future updates, just go to Settings -> System Updates and let the magic happen.
HOW TO INSTALL
1. Factory Data reset
2. Wipe System/Data/Dalvik/Cache
3. Install ROM zip from Sdcard
4. Install GAPPS zip from Sdcard
5. Install SuperSU from Sdcard
6. Reboot to home screen to confirm good flash
7. (Optional) Reboot to recovery and flash kernel
TO USE DELTAS, YOU HAVE TO USE TWRP OR PHILZ RECOVERY. CWM WILL NOT WORK BECAUSE IT DISABLES SCRIPTING CAPABILITIES BY DEFAULT. If there's anything that you want the updater to flash automatically after it flashes your update, put the file(s) in the FlashAfterUpdate directory inside your Opendelta folder in your internal storage.
Join the BMS G+ community which will have quicker release info in the future for all things BMS and roms.
Enjoy!
Cherry-picks:
- Multi-window
This build is unofficial, so I don't exactly carry around a changelog. However, you can always check cmxlog for omni and see what's been changed with each version of one of their nightlies. It won't be exact as some have specific device merges, but it will give you a good idea. The dates on my builds will correspond with the officials listed on cmxlog.
You can also check their gerrit or git to see what's been merged.
This question gets posted pretty frequently so if some users could please bookmark this post, we can just repost it when needed. Here are all the links you can peruse for your changelog/update enjoyment.
cmxlog - http://omni.cmxlog.com/4.4/
gerrit - https://gerrit.omnirom.org/#/q/status:merged,n,z
github - https://github.com/omnirom/
G+ - https://plus.google.com/u/0/communities/102450203113748251717
XDA - http://forum.xda-developers.com/omni
XDA:DevDB Information
Omni Rom for the d2tmo, a ROM for the T-Mobile Samsung Galaxy S III
Contributors
GideonX
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: Omni
Version Information
Status: Beta
Created 2014-02-18
Last Updated 2014-02-18
Reserved
FIRST!
Thanks, Will try!
2nd haha anyways will give this a try when i get home c:
Sent from my SGH-T999 using xda app-developers app
Hell yes finally, thanks for this for sure
Sent from my SGH-T999 using Tapatalk
So what I'm getting is that a d2lte build will work on all d2 variants, no updater-script editing required?
Screenies??
As GideonX has said, these builds support all the d2 variants. Everything is automatically done during flashing. You don't need to do anything but flash like normal
downloaded and working
Except for su recconising apps. have tried manual install also just can't seem to make it work. appreciate this rom otherwise. will keep trying. thanks:good:
Is anyone having problems with swipe typing?
trofmoc said:
Except for su recconising apps. have tried manual install also just can't seem to make it work. appreciate this rom otherwise. will keep trying. thanks:good:
Click to expand...
Click to collapse
4.4 needs special twrp jyst in case you restored back on to tw or never updated.
Anyways seems like the rom had little to offer in my personal opinion. I decided to just go an restore previous rom instead
Sent from my SGH-T999 using xda app-developers app
I just installed the Rom! Working great! Thank you.
Wp4Wp4:good:
twrex82 said:
Is anyone having problems with swipe typing?
Click to expand...
Click to collapse
Try PA's gapps. If you're talking about how no letters actually get inputted on the screen even though it is showing the swipe, then that's what you need.
http://forum.xda-developers.com/showthread.php?t=2397942
New D2LTE 2014-02-21 Build - http://goo.gl/zJwFzA
- Had some opendelta issues. Please flash this entire zip this time around, thanks.
- Screen rotation is in settings now.
where are the screen shots for this rom?
Thank you for this rom and one quick question, can't Sync facebook contacts info anymore on the last build?
"Envoyé depuis mon SGH-T999 avec Tapatalk"
Can someone on tmobile verify uploading pictures and video works with this rom in instagram? it may be a kitkat issue with instagram but previously I have gotten a lot of freezes, FC, and reboots while trying to upload video. anybody willing to test this on the latest release?
Dude sorry but are u spamming the threads with the same question?
Sent from my SGH-T999 using xda app-developers app
Anyone have OpenDelta mess up their phone? Every time I booted into recovery it would install the update. Then lost root and my gapps. It was hell trying to get it all back.
Purplezigar said:
Anyone have OpenDelta mess up their phone? Every time I booted into recovery it would install the update. Then lost root and my gapps. It was hell trying to get it all back.
Click to expand...
Click to collapse
I'm using Philz recovery, opendelta updates work as expected. What's your setup?
{
"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
I BUILD ABANDON A TWRP!
THIS PROJECT IS ABANDONED (2015-12-06)
Blastagator's 2.8.7.3 release fixes the problem that started my quest: the sepolicy squashing that damaged the gapps permissions on CM-12 OS updates. Given that I had many more issues that came from my choice of CM-12.1 as a base (instead of whatever TWRP wanted) and that I lacked the time, inclination or expertise to pursue the issues, I have chosen to abandon this project. If it worked for you and you didn't need the extra features that were buggy, then by all means enjoy. However this project is no longer supported.
What is it?
It's TWRP! It's for a number of the G2's! Which ones? The ones supported by whatever the current CyanogenMod is. GSM: D800/1/2/3, CDMA: LS980, VS980. This is because, despite the TWRP documentation, I use CyanogenMod as a base, and if CyanogenMod doesn't currently support the given model, then I won't be supporting it with my TWRP. This TWRP is built with hints from (and thanks for) @blastagator's TWRP.
README.FIRST / DISCLAIMER
THERE BE DRAGONS HERE!!! USE THIS AT YOUR OWN RISK!!!
This is your one AND ONLY warning. I am not responsible for whatever happens to your phone. This software has the feature set to let you backup all of your partitions, but it also has the power TO BOTCH each and every partition on your device. This includes your EFS and other sensitive things. It is entirely possible that you may end up bricking your device. I really hope that doesn't happen, but I am also not responsible if it does. Please, behave responsibly and know that if you've taken the time to get this installed, well... your warranty is void.
Features
Flashes Gapps properly so that it doesn't crash on reboot
Thermal Support
Material Theme
{
"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"
}
Known Issues / Red Flags
I've only really tested on the D800 because that's what I have access to. However I've reports that it works fine on the other variants.
Reports that it doesn't work with blastagator's hybrid LP bootstack. (User says reboots into bootloader)
F2FS Support currently a bit borked. (User's say formatting doesn't work and causes ROM to bootloop, or is very slow and doesn't work.)
Users using AROMA will have issues installing things. Something about the installation process causes the recovery to reboot.
Cherry Picks / Links
Device Repo: https://github.com/dr4stic/twrp_device_lge_g2-common
CyanogenMod / 89474: Make recovery permissive (manually applied) - (20151003 - current)
TWRP / 12728: [WIP] gui: stock theme rework - (20151015 - current)
CyanogenMod / 110402: f2fs: Import latest F2FS + AIO Optimization - (upcoming)
TWRP / 14355: Fix broken fsflags support (upcoming)
TWRP / 14462: Support resuming block based OTAs (upcoming)
Releases / Changelog:
2.8.7.0 - 20151015
Added directives to tell twrp where our media REALLY is (blastagator suggested bad things happen if I don't)
Cherry picked a more material like theme because Rashed97 whined about ugliness
D800: twrp-2.8.7.0-20151015-d800.zip - 11.6 MB (MD5 Sum: 7e46ea96fed69a5cde9da73e26d6742e)
D801: twrp-2.8.7.0-20151015-d801.zip - 11.4 MB (MD5 Sum: 7a71cda865b0f32c1403938eb76eeb5e)
D802: twrp-2.8.7.0-20151015-d802.zip - 11.4 MB (MD5 Sum: 52143681915a53b910040fb6501dd324)
D803: twrp-2.8.7.0-20151015-d803.zip - 11.4 MB (MD5 Sum: e8ee2f05ca06be1924a45e49da29e439)
LS980: twrp-2.8.7.0-20151015-ls980.zip - 11.4 MB (MD5 Sum: f76642bd7f5bb2b0eb8bb2a20e4adfed)
VS980: twrp-2.8.7.0-20151015-vs980.zip - 11.4 MB (MD5 Sum: bdfdb1e2132ab08a8f7e42c06e3699a4)
2.8.7.0 - 20151003
Initial release
Download 2.8.7.0 - 20151003: D800 | D801 | D802 | D803 | LS980 | VS980
Thanks To:
The TWRP Development Team
@blastagator
@Rashed97
dr4stic said:
Hello folks,
I BUILD A TWRP!
Click to expand...
Click to collapse
When I see how many projects are done for the G2, I really think I should give a try... Anyway, !gg mate, I'll try this recovery .
What did you change? Or did you just build my repos and post a new thread?
blastagator said:
What did you change? Or did you just build my repos and post a new thread?
Click to expand...
Click to collapse
It's not just a download and rebuild, if that's what you're asking (and, I'm not trying to upset the apple cart or anything).
The build started as the end of my trying to figure out what the problem was with CM and Gapps that required it to be re-flashed each time a rom update was flashed. I experimented with running commands by hand, dissecting upgrade scripts, found that contexts were either not being set or being lost, etc... etc... And at some point the only answer I could come up with was that it was the recovery. I tried the CM recovery, which is worse than the black death, and it worked fine. Since your TWRP is the latest, I didn't understand why it wasn't keeping contexts. At that point I decided to build my own TWRP, so I started from the only official docs I could find. That's what my base started as.... the cm-10.1 repos they have on their github for g2.
After realizing that simply wasn't going to work, I started re-working and basing off of CM. I didn't necessarily want to look at your work because in my mind yours was done right and based on latest CM. I eventually looked at it for some hints (hence my attribution). It wasn't until I realized your device repos looked odd to me that I realized what happened. Your device repos were based from back when the G2 stuff was barely starting out on CM-12.1... it was still very 12.0 (which, in itself was a ball of vomit for the g2). It lacked the selinux stuff (which is why it was losing contexts) and you also used an alternate kernel (unsurprisingly, cuz the CM stuff was still in a state of vomit). There are no judgements. At the time you built the recovery, it's what was available and working. I don't think the G2 got selinux turned up until some time in very early August.
So, I decided to fork copies of the latest CM device repos which all work now, base everything off the current CM kernel (I figured this was safest for compatibility). I actually looked through the TWRP sources to hunt for actual BoardCommonConfig.mk settings (the docs seemed VERY lacking) and an understanding of how they all interacted. I looked at your repo for hints, but I didn't just copy it. As a result I use more current settings (a few of yours are actually deprecated). I'm assuming because of the age of your repo that your builds were lokified and you bumped them after the fact. Mine have all the changes that came with 12.1 including a lack of loki and being bumped as part of the build process. The rc files are all stock CM. Many things simply don't exist from your version because the recovery environment seems REALLY restricted once it's built. The few things that I did borrow, I moved into more appropriate locations and file names to be more respectful of the build process.
So, to answer your question: it started as a rather long and annoying bug hunt, then turned into a long but fruitful learning experience, and once I had a version that worked, I posted it for the few folks on the CM forum for whom this is a real pain in the ass.
It certainly wasn't a quick process and a grab for glory.... hell, once I realized that the CM build process needed to build a full ROM to get all the appropriate files into the recovery image, each one of those device builds took over an hour to build.
I started a new thread because I wanted to have a specific place where I could respond to issues if they arose, or at least tell people that I didn't care about their piddly little problems. I wanted a little more control over the support process, to be able to modify the OP with pertinent issues and links as they came up. It's something I wish had happened with CM-12.1 "official" threads.
There are things that I'm not sure of, and I try to indicate as much in the OP. The thread regulars indicated the history of needing thermal support, but I'm not sure if I got it right. Neither your recovery nor mine actually got the thermal libraries or binary included in the file system, however the process seems to be running. Nor are the configuration files included on the file system. f2fs support seems to simply be an additional package, and since the official G2 repos theoretically have f2fs support, I added that and moved along. The tools seem to be included on the file system.
I'm in the process of posting my changes to github, probably tomorrow since I'm still sorta learning to do that and I have things to do tonight. You can see them then. If you post an updated version of your recovery with my modifications, I'll happily close this thread.
@dr4stic
There's no "thermal support" official twrp uses their kernel, which blasts all cores on max freq, generating needless amounts of heat.
From the sounds of it, you're using the stock cm12.1 kernel, so there should be no heat issues. If the CPU gets hot, it will throttle as it is supposed to.
So that's what his twrp means when it says thermal support. It uses our phones kernel so it operates like it would on a ROM.
Lawlrus said:
There's no "thermal support" official twrp uses their kernel, which blasts all cores on max freq, generating needless amounts of heat.
From the sounds of it, you're using the stock cm12.1 kernel, so there should be no heat issues. If the CPU gets hot, it will throttle as it is supposed to.
So that's what his twrp means when it says thermal support. It uses our phones kernel so it operates like it would on a ROM.
Click to expand...
Click to collapse
@Lawlrus, thank you for the explanation! After I investigated I assumed that's what was going on, but I didn't want to assume and then tell people something I wasn't sure about. I noticed that mine gets a slight toastier than blastagator's, but not a significant difference. I attributed it more to kernel tuning with the finalized CM kernel than anything else.
dr4stic said:
It's not just a download and rebuild, if that's what you're asking (and, I'm not trying to upset the apple cart or anything).
I'm in the process of posting my changes to github, probably tomorrow since I'm still sorta learning to do that and I have things to do tonight. You can see them then. If you post an updated version of your recovery with my modifications, I'll happily close this thread.
Click to expand...
Click to collapse
Nah man, I'm not upset. I made it so easy (or tried to make it easy, at least) to build my source so other people could muck with it. My curiosity stems from wanting to add any improvements in to my build.
I briefly messed with cm12 device trees but didn't have luck the first go around so I didn't bother going down that road. Will definitely keep an eye on this thread.
My builds are built with the Omni 4.4 Source, and these changes:
https://github.com/blastagator/cm_device_lge_g2-common/blob/cm-11.0/blastagator_g2-common.xml
The device trees are actually based on cm-11, not 12.
As for SELinux, issues probably stem from this: https://github.com/blastagator/aicp...mmit/85953d0cf8dd3d33406ad8a745ced99e5039f766. When I committed it I thought it set SELinux to permissive. However, it actually completely disables SELinux, so the kernel won't automatically preserve contexts, etc. This seems like the most likely culprit for your issue. I will run a test build and revert that commit, if you'd like it to test.
As to cm-12, in general: I'm certainly interested in moving up, I just never really had a reason to spend any time on it.
blastagator said:
Nah man, I'm not upset. I made it so easy (or tried to make it easy, at least) to build my source so other people could muck with it. My curiosity stems from wanting to add any improvements in to my build.
I briefly messed with cm12 device trees but didn't have luck the first go around so I didn't bother going down that road. Will definitely keep an eye on this thread.
Click to expand...
Click to collapse
PM me with your email. I'll shoot you the diff I made. The only reason I haven't posted it to github is that I wanna show the changes piecemeal instead of in one big diff. If you can call it big... it's really just 4 changes
Honestly, I'm not sure why they recommend against building on CM. Despite their documentation being utter crap, the build itself was easy once I figured out where the pieces were all supposed to go.
And yeah... CM 12.1 at the time you built things was an absolute mess. But the stuff in the official repo's is really rock solid now. Well, maybe not tonight, it seems there were a bunch of g2 changes and one in particular is gonna break the build for tonight
Tried the d800. Device went into fastboot mode, doesn't boot into recovery. Back to blastagators.
dr4stic said:
PM me with your email. I'll shoot you the diff I made. The only reason I haven't posted it to github is that I wanna show the changes piecemeal instead of in one big diff. If you can call it big... it's really just 4 changes
Honestly, I'm not sure why they recommend against building on CM. Despite their documentation being utter crap, the build itself was easy once I figured out where the pieces were all supposed to go.
And yeah... CM 12.1 at the time you built things was an absolute mess. But the stuff in the official repo's is really rock solid now. Well, maybe not tonight, it seems there were a bunch of g2 changes and one in particular is gonna break the build for tonight
Click to expand...
Click to collapse
Github makes tracking all of this better. My suggestion is that you first create a "fork" of blastgator's repo on Github, and then "clone" the repo on your local machine. Apply your diffs to it. Commit and Push (to your fork). Then issue a pull request to Blastgator.
sandys1 said:
Github makes tracking all of this better. My suggestion is that you first create a "fork" of blastgator's repo on Github, and then "clone" the repo on your local machine. Apply your diffs to it. Commit and Push (to your fork). Then issue a pull request to Blastgator.
Click to expand...
Click to collapse
Thanks for your suggestion. I'm already talking to blastagator. The problem is that his current build isn't actually based on CM-12, we are working from different sources.
jacoghi said:
Tried the d800. Device went into fastboot mode, doesn't boot into recovery. Back to blastagators.
Click to expand...
Click to collapse
I have a few d800's, it's the device I use. Which bootloader are you on? JB? KK? LP?
I have the hybrid LP bootstack, from blastagator, which includes the KK aboot. Blastagator's twrp works without hitches
jacoghi said:
I have the hybrid LP bootstack, from blastagator, which includes the KK aboot. Blastagator's twrp works without hitches
Click to expand...
Click to collapse
Just a few things...
Are you talking about the "Bump LP" bootstack on this page?
Are you sure you downloaded the d800 recovery?
If you did, could you verify the md5 of the file you downloaded against the one I list in the OP?
Thanks.
dr4stic said:
Just a few things...
Are you talking about the "Bump LP" bootstack on this page?
Are you sure you downloaded the d800 recovery?
If you did, could you verify the md5 of the file you downloaded against the one I list in the OP?
Thanks.
Click to expand...
Click to collapse
Yep to all of them. I flashed your image using blastagators twrp and got the fastboot mode. Let me know should you need any extra info. Thanks
jacoghi said:
Yep to all of them. I flashed your image using blastagators twrp and got the fastboot mode. Let me know should you need any extra info. Thanks
Click to expand...
Click to collapse
Do you use cm-12.1? Which ROM do you use (and version) if you don't mind me asking.
dr4stic said:
Do you use cm-12.1? Which ROM do you use (and version) if you don't mind me asking.
Click to expand...
Click to collapse
I'm using cloudy 3.3 right now with xceeds kernel. After I got the fastboot mode, I could boot my system normally, if that helps. Rebooted again, got fastboot once more. Then booted system up again and installed autorec, which corrected the problem.
Well, messed around with this for a bit, decided to format /data to f2fs.
Dont do that. Not on this recovery. Formatting to f2fs takes forever (probably hangs entirely as i waited at least 10 minutes before rebooting)
Then noticed my /data wouldnt mount on reboot, causing my rom to bootloop and, even worse, the recovery to bootloop.
Due to a (probably unrelated) bug the lg flash tool didnt work either, so had to open up the device to boot in qhsusb mode and manually format /data to ext4.
This is the closest I've been to a complete brick on this phone since I got it.
Please update the OP to warn people about f2fs.
Nice work on the kernel update, but I personally am going to avoid this recovery until the above issue is solved
My problem is that it would not reboot nor power off while in this recovery. But it works by pressing power button.
It is ok now by removing the theme file ui.zip.
{
"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"
}
Being a SlimRoms fan, I looked everywhere for up to date versions of Slim5 or Slim6, and after I couldn't find any newer Slim ROM for my SGH-M919, I decided to compile one. By God's grace, it worked! I hope that other's can enjoy this ROM too, so I put it here to share it with you!
**** This is an UNOFFICIAL ROM. Install at your own risk! ****
Downloads:
Rom Download link:
http://www.mediafire.com/download/3irz4n9kzrawux1/slimlp-jf-20160818.zip
Gapps link:
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
I have personally tried the Slim_zero_gapps.BETA.5.1.build.0.x-20160429.zip file, which worked flawlessly. Be sure to slap their thanks button for the Gapps!
Old Rom without hand updated Critical Security patches download link:
http://www.mediafire.com/download/4liij279jjx7pd4/Slim-jf-5.1.1-UNOFFICIAL-20160721-aklu.zip
This Rom has been very stable for me. Be sure to follow these installation steps very carefully, as they may be different then what you are used to.
Installation instructions:
-Download ROM and gapps, and put them on your phone or external storage.
-Reboot into recovery mode - TWRP (I personnally am using 2.8.7.0).
-Backup what you had. (Just to be safe.)
-Wipe.
-Install Rom.
-Wipe Cache and Davlik. <--VERY IMPORTANT!
-Install Gapps. - Optional.
-Wipe Cache and Davlik again! <--VERY IMPORTANT! Or WiFi may not work first boot. Will work thereafter.
-Reboot to system and enjoy!
Code:
What works:
-So far everything that I have tried works, such as
- Phone calls/receiving
- Data 2g/3g/LTE
- Bluetooth
- WiFi
- MTP
- GPS
etc....
What doesn't:
- I have not found any big errors, fault crashes, or problems yet. Please let me know if you find an issue!
- I have posted a few notes in Post #2 below.
Change log:
Code:
20160818
-Added May 2016 Security updates (Critical updates only) by hand. See posts for more information. May not be perfectly secure.
-Edited updater-script so zip may be flashed on any JFLTE phone. Built for JFLTETMO though. Use with caution!
20160815
-Added April 2016 Security updates (Critical updates only) by hand. See posts for more information. May not be perfectly secure.
-Edited updater-script so zip may be flashed on any JFLTE phone. Built for JFLTETMO though. Use with caution!
20160805
-Added March 2016 Security updates (Critical updates only) by hand. See posts for more information. May not be perfectly secure.
-Edited updater-script so zip may be flashed on any JFLTE phone. Built for JFLTETMO though. Use with caution!
20160721
-Added GPU overclock kernel - control with Kernel Adiutor app.
-Edited updater-script so zip may be flashed on any JFLTE phone. Built for JFLTETMO though. Use with caution!
20160711
-Removed NFCPU in favor of Kernel Aduitor
-Synced with SlimLP source - Note: They do not appear to be updating thier security patches, since Feb, 2016.
-Edited updater-script so zip may be flashed on any JFLTE phone. Built for JFLTETMO though. Use with caution!
20160707
-Added Kernel Aduitor app to build.
-Added Fast Charge to kernel.
-Edited updater-script so zip may be flashed on any JFLTE phone. Built for JFLTETMO though. Use with caution!
20160623:
-Added the Lionheart and SmartMax governors to the kernel.
-Added "No Frills CPU" app to build.
-Edited updater-script so zip may be flashed on any JFLTE phone. Built for JFLTETMO though. Use with caution!
20160618:
-Synced with SlimLP source.
-Edited updater-script so zip may be flashed on any JFLTE phone. Built for JFLTETMO though. Use with caution!
20160512:
-First release.
Disclaimer: SlimRoms is not responsible for any damages to your device.
In the Rom, I left the original SlimLP boot animation, however, I have made a couple of simpler custom boot animations for SlimRoms, which you can find here if you would like to use one of them instead:
http://forum.xda-developers.com/slimroms/general/homemade-slimroms-boot-animation-t3377271
This SlimLP ROM was built for the JFLTETMO, the T-Mobile Samsung Galaxy S 4. However, The updater script has been modified, and it would allow itself to be installed on any of the Galaxy S 4 devices. I have not tried this on any other device, but you are welcome to try it AT YOUR OWN RISK.
A huge thanks to the SlimRoms team!
SlimRoms XDA Forum: http://forum.xda-developers.com/slimroms
Source Code: http://github.com/SlimRoms/
Official websites: http://www.slimroms.net/ or http://slimroms.org/
ROM OS Version: 5.1.1 Lollipop
ROM Kernel: Linux 3.4.112
Based On: AOSP
Device Tree: https://github.com/alaskalinuxuser/
Features the AKLU kernel:
http://forum.xda-developers.com/gal.../kernel-marshmallow-lollipop-kernels-t3411543
Created 2016-05-12
Last Updated 2016-12-20
All of my work is completely available for any who wish to use or modify it. I didn't make SlimRoms, the device trees, or vendor blobs. I simply used and edited existing material. A huge thanks should go to those who actually created this stuff.
Notes: a place for notes about the ROM.
Background image
The futuristic and really cool background images used in this rom were provided by The Quiet Learner, you can visit his website for more information and more really great pictures. https://qlfiles.net/
Security Updates
As of February 2016, the SlimRoms team has stopped updating SlimLP with security updates. I have decided to continue updating SlimLP, but only with Critical security updates from the Android Security Bulletins: https://source.android.com/security/bulletin/index.html. Please note that I am only updating Critical updates, not High, Moderate, or Low security threats. I am doing this by hand and may miss one update. Please be advised that this rom is not as secure as Marshmallow roms that are kept up to date. I am doing my best, but I may also be a little behind the bulletins. Please be patient. I decided Critical updates were better than none, but I can only do Critical updates, as this sometimes takes editing over 800 files per monthly bulletin.
Camera
Every now and then, when I use the built in camera app, it will take 2 or 3 pictures, and then the camera picture button will be grayed out, and you must exit and re-open the camera app to take more pictures. This does not happen with Open Camera app, which is available online or at the play store. Overall the camera seems to be working great, I'm not sure why the built in app sometimes has this issue.
GPS
GPS seems to take an unusually long time to get a fix, even outdoors in the open sky. It does work and stay locked for me, but I thought I would share, in the event others noticed this as well. @redx64 has pointed out that you can speed up the GPS by downloading GPS Status and toolbox and use fastergps to update your GPS config file to your region.
Gapps or no Gapps?
For those who do not wish to install, or who are prohibited from installing Gapps, there are some great alternatives. Aptoide works really well in general, and I did take some time to test it with this ROM. As for my apps, Aptoide had all but 2 of the apps I use available, and many alternative apps as well. If you wish to forgo Gapps, but still want a login, app searching, automatic updating (or not, depending on your settings), user friendly tool, then you might want to give Aptoide a try.
The best way to use layers successfully with this ROM:
After doing some testing of the layers on SlimLP, I learned a few helpful tips.
1. The PlayStore Layer Manager App is too "new" for SlimLP. The 4.+ version available from the PlayStore will not let you undo the layers, and hense you cannot go back to stock. Use this older version (3.5) instead, which allows you to install, apply, delete, and undo changes:
https://www.mediafire.com/download/q94w8j7xuyhpudz
2. The PlayStore layers themes are often incompatible with version 3.5 of the layer manager app. Don't worry though, there are tons to choose from here on XDA:
http://forum.xda-developers.com/showthread.php?t=3011075
This Mega thread has tons of them to choose from. If you want these, only download the ones that are zip files for best compatibility. The zips should show up in your download folder, which you can move anywhere and use from the app.
The app has an option to "delete" layers, which actually means "undo" that layer, not actually delete the zip file.
If you still wish to use the PlayStore app and themes, keep in mind that you cannot "undo" your choice of theme. And sometimes themes have an undesired side effect. Two themes from the PlayStore that I have successfully used were BluSky theme, and Elixium theme, both of which worked well, with the exception of the systems -> battery settings chart looked funny.
If you use the themes, I highly recommend doing a TWRP backup first, to make sure that you can always go back!
Governors:
If you want to save battery life, I recommend that you use the "No-frills CPU Control" app and set your Governor to something like Powersave or SmartMax, and your I/O scheduler to Noop. This may affect performance slightly, but will save on some battery power.
If you want to increase performance, I recommend that you use the "No-frills CPU Control" app and set your Governor to Lionheart, Ondemand, or Performance, and your I/O scheduler to CFQ. This will boost performance slightly, but will have a negative impact on battery power.
Powersaving <----------> Performance:
Powersave, SmartMax, Conservative, Interactive, Lionheart, Ondemand, Performance.
Fast Charge:
To use Fast Charge, you must enable it in the Kernel Adiutor app. If you want to set custom settings, you will need to get another app from the Play Store, such as Device Manager or other apps that allow you to control the fast charge settings. Note that some fast charge settings apps do not change the appropriate values to function. The lockscreen may still say "slow charge" as the rom itself does not natively support fast charge, even though the kernel does.
Also, if you have any questions or comments (even if you didn't like it) about this ROM you are welcome to post them in this thread. SlimRoms is not for everyone, since it is rather "slim". No sense starting a Q&A thread for this ROM when we already have a thread here...
Thanks for your work on this. Really miss having a SlimRom, used to run on my SG4. With all the BT issues plaguing MM ROMS currently, I may give this a whirl.
Thanks for this. . Keeping it in my back pocket
Sent from my SGH-M919V using XDA-Developers mobile app
christoophat said:
Thanks for your work on this. Really miss having a SlimRom, used to run on my SG4. With all the BT issues plaguing MM ROMS currently, I may give this a whirl.
Click to expand...
Click to collapse
Thanks. I did test the Bluetooth, but I do not use it much. It would be good to know if this Bluetooth is rock solid when it comes to headphones, speakers, and such.
Sent from my SGH-M919 using XDA-Developers mobile app
kazzxtrismus said:
Thanks for this. . Keeping it in my back pocket
Sent from my SGH-M919V using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks! Does this ROM work on the SGH-M919V as well?
Sent from my SGH-M919 using XDA-Developers mobile app
AlaskaLinuxUser said:
Thanks. I did test the Bluetooth, but I do not use it much. It would be good to know if this Bluetooth is rock solid when it comes to headphones, speakers, and such.
Sent from my SGH-M919 using XDA-Developers mobile app
Click to expand...
Click to collapse
I should think BT is fine, as devs had it working pretty much 100% for the LP ROMS.
MM seems to have changed something that hasn't quite been solved yet.:silly:
AlaskaLinuxUser said:
Thanks! Does this ROM work on the SGH-M919V as well?
Sent from my SGH-M919 using XDA-Developers mobile app
Click to expand...
Click to collapse
It should be fine.. Wind apn might need added tho
Sent from my SGH-M919V using XDA-Developers mobile app
Any chance of you doing. Dirty unicorn build 6.0 mm
immorality said:
Any chance of you doing. Dirty unicorn build 6.0 mm
Click to expand...
Click to collapse
If I am not mistaken, that has already been done:
http://forum.xda-developers.com/showthread.php?t=3292806
Please let me know if I am wrong, but can't we use this version also?
Be sure to slap their thanks button if you enjoy their ROM!
Edited: I now see that it does not work on the M919. I am currently pursuing SlimRoms 6.0, but perhaps I can look into it. No promises, though.
Sent from my SGH-M919 using XDA-Developers mobile app
AlaskaLinuxUser said:
If I am not mistaken, that has already been done:
http://forum.xda-developers.com/showthread.php?t=3292806
Please let me know if I am wrong, but can't we use this version also?
Be sure to slap their thanks button if you enjoy their ROM!
Edited: I now see that it does not work on the M919. I am currently pursuing SlimRoms 6.0, but perhaps I can look into it. No promises, though.
Click to expand...
Click to collapse
Its a rough build with little updates
As you know you cannot flash jfltexx versions of the ROM
If you want to you need to flash a xx recovery
Could you add super user to settings
(I feel dirty unicorn covered the most ground with its settings menu
Feels like slim always misses something so I finished testing an went back to a previous ROM
AlaskaLinuxUser said:
If I am not mistaken, that has already been done:
http://forum.xda-developers.com/showthread.php?t=3292806
Please let me know if I am wrong, but can't we use this version also?
Be sure to slap their thanks button if you enjoy their ROM!
Edited: I now see that it does not work on the M919. I am currently pursuing SlimRoms 6.0, but perhaps I can look into it. No promises, though.
Sent from my SGH-M919 using XDA-Developers mobile app
Click to expand...
Click to collapse
Actually, I'd welcome an SLim MM ROM more!
Does this ROM currently use CM Theme engine?
christoophat said:
Actually, I'd welcome an SLim MM ROM more!
Does this ROM currently use CM Theme engine?
Click to expand...
Click to collapse
No, SlimLP does not use the CM theme engine.
-AlaskaLinuxUser
https://thealaskalinuxuser.wordpress.com
immorality said:
Feels like slim always misses something so I finished testing an went back to a previous ROM
Click to expand...
Click to collapse
Slim is certainly slim. I do like some of the built in features, like the ability to remap hardware buttons in the settings menu, the built in screenshot tool, slim pie, and the slim recent apps bar when you hold down the home key. So I think that Slim has lots of "subtle" features that most folks are unaware of.
No worries though, thanks for trying the ROM out.
Edit: I finally figured out how to take a screenshot while the slim pie controls were open.
-AlaskaLinuxUser
https://thealaskalinuxuser.wordpress.com
Hey guys, I'm new to the ROM scene, this is my first go. Well, second time trying to flash a rom. Anyway it flashed and booted fine but on first boot its having trouble with all the gapps, I assume I used the wrong version of the gapps zip file. Should I just try different versions one at a time? Could that brick it?
Thanks
karovamilkbar said:
Hey guys, I'm new to the ROM scene, this is my first go. Well, second time trying to flash a rom. Anyway it flashed and booted fine but on first boot its having trouble with all the gapps, I assume I used the wrong version of the gapps zip file. Should I just try different versions one at a time? Could that brick it?
Thanks
Click to expand...
Click to collapse
First and foremost, thanks for giving SlimLP a try!
Second, as for the Gapps, trying different ones wont brick it, but you will need to do a fresh wipe, install the rom and then gapps, as per the first post instuctions. I recommend that you try this one:
https://www.androidfilehost.com/?fid=4996500813288308963
I hope that gets you going, good luck and have fun with SlimLP!
-AlaskaLinuxUser
https://thealaskalinuxuser.wordpress.com
karovamilkbar said:
Hey guys, I'm new to the ROM scene, this is my first go. Well, second time trying to flash a rom. Anyway it flashed and booted fine but on first boot its having trouble with all the gapps, I assume I used the wrong version of the gapps zip file. Should I just try different versions one at a time? Could that brick it?
Thanks
Click to expand...
Click to collapse
Open gapps is my go to,
Then it's dynamic gapps
But here we have 100s of gapps (well like 5-10 to choose from)
Rome are tricky learn everything you can before the flash (read some issue reports by users and don't forget to post yours (log is best)
I've been around since sidekick 4g /.o I miss the keyboard never had to look at it to type
Loving this rom. Most stable and fast compared to the Dirty unicorn and Pacrom I tried before. If anyone is having problem with GPS , i reccomend the following. Download GPS Status and toolbox and use fastergps to update your gps config file to your region.
Here is a screenshot of the benchmark with this ROM using the linaro 4.7 tool chain. I was hoping to try a few other tool chains to see if it makes a difference. So far the kernel build fails with the linaro 4.9 tool chain.
-AlaskaLinuxUser
https://thealaskalinuxuser.wordpress.com
By the way, you can set the display to 320 DPI to get the most out of your screen, too. It is in the settings menu as LCD density.
Sent from my SGH-M919 using XDA-Developers mobile app
Nothing would be possible without the work of @MrColdbird and the help of @Franssen
{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and we are now based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
If there are any bugs, either we will sort them out or the GZOSP team, if it concerns their code base. This ROM isn't GZOSP supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Firmware Version 9.9.3
Download link: https://drive.google.com/open?id=142PC3GNCnfrp4h5RGGSn-qV9aSZFE5M0
Latest Stable Release Version 14.0
Download link: https://mega.nz/#!C1tDyIBB!-2cpzfdKYDA05U6-SfQHqXpnzGgyHqqsbtopZjQntTY
Mirror: https://drive.google.com/open?id=1BJ1QtmPNF8Rqx80xsw_IUfKjHq0yOy0_
Google Apps:
(link the best one for your device, there are several variants out there right now, nano/micro GApps from opengapps.org is almost always a good choice though)
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. Xposed is not yet released for Pie, however you can try to use edxposed .
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Pie. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the FIRMWARE then ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work) and Magisk (root).
6. Reboot and set up your device,
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 17.2 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
Kernel source:
https://github.com/rr-mario/msm-4.4./stable
Device tree source:
https://github.com/Skyllery/device_xiaomi_nitrogen/tree/aicp-pie
Vendor source:
https://github.com/Black-Seraph/vendor_xiaomi_nitrogen/pie
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds[/B]
Contributors:
@MrColdbird @Franssen @Mario_R and my testers (Gryphon_D)
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
AICP, ROM for the Xiaomi Mi Max 3
Contributors
Skyllery, MrColdbird, Franssen
Source Code: https://github.com/Skyllery/device_xiaomi_nitrogen/tree/aicp-pie
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: 9.9.3
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 14.0
Stable Release Date: 2019-09-21
Created 2019-09-21
Last Updated 2019-10-17
Finally, AICP is out.
Great job, currently best Rom, it would be nice if you could change the icons
for Accu, Wlan, Mobile Data and Clock and Provider Color, then the Rom would
be absolutely perfect
rudiratlos57 said:
Great job, currently best Rom, it would be nice if you could change the icons
for Accu, Wlan, Mobile Data and Clock and Provider Color, then the Rom would
be absolutely perfect
Click to expand...
Click to collapse
Currently best ROM? Please explain why..
GEoMaNTiK said:
Currently best ROM? Please explain why..
Click to expand...
Click to collapse
The other roms Like Aoisp, havoc, Fest, lineage and the rest of it, always after a couple hours of usage, always start lagging to open apps and other. This one i have 24 Hrs, and still strong whit no problem. Don't ask me why but, for me right now, its perfect.
rudiratlos57 said:
Great job, currently best Rom, it would be nice if you could change the icons
for Accu, Wlan, Mobile Data and Clock and Provider Color, then the Rom would
be absolutely perfect
Click to expand...
Click to collapse
Sorry but didn't understand what you mean. BTW i'm mostly a builder and modding AICP source code is far from my knowledge.
Regards
eloyho said:
The other roms Like Aoisp, havoc, Fest, lineage and the rest of it, always after a couple hours of usage, always start lagging to open apps and other. This one i have 24 Hrs, and still strong whit no problem. Don't ask me why but, for me right now, its perfect.
Click to expand...
Click to collapse
I'm using Revenge and it's as snappy as I've found... I've also underclocked my CPU and its quick!!!
GEoMaNTiK said:
I'm using Revenge and it's as snappy as I've found... I've also underclocked my CPU and its quick!!!
Click to expand...
Click to collapse
Remember we use the same device tree to build everything, GismoBe, Me, etc. It's mostly rom reputation and usage. There's no best or worst, we build as anyone can find what works for him.
Regards
@Skyllery your Revenge OS is very good but i dont see a thread for it. also see mi max 3 Miui 11 beta leak is out so gonna try that. its on Telegram :good:
shingers5 said:
@Skyllery your Revenge OS is very good but i dont see a thread for it. also see mi max 3 Miui 11 beta leak is out so gonna try that. its on Telegram :good:
Click to expand...
Click to collapse
It's because Revenge OS is not build by me ^^ It's Franssen (GismoBe on Telegram) but he's not much on XDA these days. I already tell him why there's not all their ROMS (AOSMP, Revange, etc) but he don't have much time.
Not tried it already .. open beta seems to be on 27th. I think i'll wait to xiaomi.eu or try to go on 10 gsi to see how it is. (Didn't look at this for the moment)
Regards
Skyllery said:
It's because Revenge OS is not build by me ^^ It's Franssen (GismoBe on Telegram) but he's not much on XDA these days. I already tell him why there's not all their ROMS (AOSMP, Revange, etc) but he don't have much time.
Not tried it already .. open beta seems to be on 27th. I think i'll wait to xiaomi.eu or try to go on 10 gsi to see how it is. (Didn't look at this for the moment)
Regards
Click to expand...
Click to collapse
i am trying it now guess xiaomi.eu will translate.and release soon. i like it and.the changes are nice. not bad for forst beta
shingers5 said:
i am trying it now guess xiaomi.eu will translate.and release soon. i like it and.the changes are nice. not bad for forst beta
Click to expand...
Click to collapse
On my side still on aex for the moment, in fact my preferred ROM builded by me. (Specially for battery backup)
Will try the beta tomorrow look promising .. but miui have some little things which kept me away to use it more than two days.
Sim activation by sending a sms to china (paid)
Region limitation for community access and theme options..
Poor theming compared to custom ROMs.
But it looks promising will give it a chance.
Regards
Sent from my MI MAX 3 using XDA Labs
shingers5 said:
@Skyllery your Revenge OS is very good but i dont see a thread for it. also see mi max 3 Miui 11 beta leak is out so gonna try that. its on Telegram :good:
Click to expand...
Click to collapse
Where to find the beta leak, what is the telegram page? Oh wow XDA posted them all as twrp recovery files.
Skyllery said:
On my side still on aex for the moment, in fact my preferred ROM builded by me. (Specially for battery backup)
Will try the beta tomorrow look promising .. but miui have some little things which kept me away to use it more than two days.
Click to expand...
Click to collapse
Tries AEX a few weeks back, it cannot run my banking apps, even with Magisk Hide. Malaysia Maybank and Singapore DBS, no choice but to give it up. Any changes since then? Any idea how to fix it? Thanks.
Awesome ROM.. have been using for a little under 24hrs.
I had a problem with Revenge, out of the blue my Mi Max 3 went into a bootloop.. did nothing different and no idea why...
One thing I've noticed since going to AICP,, my 5GHz wirelsss network keeps coming up as Disabled, after it briefly connects. The 2.4GHz network is working without problems and stays connected.
Anyone else having this problem or can help with what it might be?
All other custom ROMs haven't had an issue with 5GHz.
Wmateria said:
Where to find the beta leak, what is the telegram page? Oh wow XDA posted them all as twrp recovery files.
Click to expand...
Click to collapse
its a proper full flashable zip. its the Nitrogen Cloud telegrsm group. its Mi Max 3 specific.
https://t.me/NitrogenCloud/1879
GEoMaNTiK said:
Awesome ROM.. have been using for a little under 24hrs.
I had a problem with Revenge, out of the blue my Mi Max 3 went into a bootloop.. did nothing different and no idea why...
One thing I've noticed since going to AICP,, my 5GHz wirelsss network keeps coming up as Disabled, after it briefly connects. The 2.4GHz network is working without problems and stays connected.
Anyone else having this problem or can help with what it might be?
All other custom ROMs haven't had an issue with 5GHz.
Click to expand...
Click to collapse
Yes got the same here
Regards
Sent from my MI MAX 3 using XDA Labs
Skyllery said:
Yes got the same here
Regards
Sent from my MI MAX 3 using XDA Labs
Click to expand...
Click to collapse
Okay I just tried something and so far it's working...
I deleted the 5GHz saved network from my phone, rebooted my wifi router, entered 5GHz network details again and no probs after about 30mins so far.
Will report back if it drops out again.
---------- Post added at 08:00 AM ---------- Previous post was at 07:41 AM ----------
GEoMaNTiK said:
Okay I just tried something and so far it's working...
I deleted the 5GHz saved network from my phone, rebooted my wifi router, entered 5GHz network details again and no probs after about 30mins so far.
Will report back if it drops out again.
Click to expand...
Click to collapse
Ohh damn, typed too soon ... The 5GHz connection just dropped out again and can't get it back on.
2.4GHz working without issue still.
GEoMaNTiK said:
Okay I just tried something and so far it's working...
I deleted the 5GHz saved network from my phone, rebooted my wifi router, entered 5GHz network details again and no probs after about 30mins so far.
Will report back if it drops out again.
---------- Post added at 08:00 AM ---------- Previous post was at 07:41 AM ----------
Ohh damn, typed too soon ... The 5GHz connection just dropped out again and can't get it back on.
2.4GHz working without issue still.
Click to expand...
Click to collapse
You use correct firmware provided in op or some modded one ?
It didn't happen to me since a while. It's on every ROM but not so often. Or try to flash modem fix.ysl.zip on channel or group you'll find it. To restart modem.
Regards
Sent from my MI MAX 3 using XDA Labs
Skyllery said:
You use correct firmware provided in op or some modded one ?
It didn't happen to me since a while. It's on every ROM but not so often. Or try to flash modem fix.ysl.zip on channel or group you'll find it. To restart modem.
Regards
Click to expand...
Click to collapse
Have just moved to the latest Xtended ROM and have no issues with 5GHz wifi, same as the previous Revenge ROM with no issues.
Very strange.