I voted because I want to see what the update brings
Can't wait to use thisi already started uploading...
Update stock kernel to 25-March-2018
Upstream merge until 25-March-2018
Ramdisk and kernel updates
Update to r81
Hack the Nougat kernel into Marshmallow
Device tree edits on odex speedup
Mark as EOL
Update Snap camera
Bravo me tis 25 martiou! Arxontas! Axios!i already started uploading...
- Update stock kernel to 25-March-2018
- Upstream merge until 25-March-2018
- Spectrum support
- Ramdisk and kernel updates
- Update to r81
- Hack the Nougat kernel into Marshmallow
- Security patches
- Final wallpaper
- Device tree edits on odex speedup
- Mark as EOL
- Update Snap camera
* Your warranty is now void. * * We're 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. *
OPTIMIZED CM13 ROM (Android 6.0.1)
By JDC TEAM using TWRP RECOVERY
I will not be held responsible for you messing up your phone. It worked for me.. It SHOULD work for you.
This does trip your Knox Warranty Bit. This does void your warranty.
*NOTE: The lines marked for Windows 7 is only that single line.. the rest of the instructions are for ANY versions of Windows.
= Windows 7 ONLY: Download to your PC: Samsung KIES3 - found [HERE].
= Download to your PC: ODIN 3 v3.10.7 - found [HERE]
= Download to your PC: TWRP Recovery 3.0.*-jfltexx.img.tar - found [HERE].
= Download to your Phones External MicroSD Card: Optimized CM13.0 ROM - found [HERE].
= Download to your Phones External MicroSD Card: Open GApps 6.0 - found [HERE]- (Look for "open_gapps-arm-6.0-pico-[DATE].zip")
= Power ON your phone and boot into the normal system.
= CHARGE YOUR PHONE TO AT LEAST 80%.. if your battery runs out while your flashing or loading you will be in trouble!!
= Windows 7 ONLY: Install KIES3 on your PC -- You must install KIES3 in order to install the Samsung phone drivers -- You do not actually need to use it. (Windows 8/8.1/10 does this automatically on the next step).
= Win 7/8/8.1/10: Plug your phone into your PC via USB cable.. WAIT for your PC to finish installing drivers.
= TRANSFER all the needed files to your phone now.. put the files in a 'ROM' folder on your External MicroSD Card.
= Unplug your phone from your PC.
= Power OFF your phone.
= Boot your phone into DOWNLOAD MODE (While Powered OFF - HOLD Power, Home, and Volume DOWN buttons for 6 secs, let go as soon as the screen changes).. then press the Vol UP button.
= Run ODIN3-v3.10.7 on your PC -- use "Run as Administrator".
= Plug in your phone (phone is still in Download Mode) via USB cable to your PC.
= In ODIN3: Make sure you see "COM #" and "ADDED!!" -- SEE HELP IMAGE HERE
* If you Do NOT see the 'COM#' and 'ADDED!!' then Samsung Drivers is Installed INCORRECTLY!
* If you DO see the 'COM#' and 'ADDED!!' then you Can Continue Below to the Next Step.
= Insert the 'twrp-3.0.*-jfltexx.img.tar' file in "AP" - Click START -- SEE HELP IMAGE HERE
= Wait for your phone to reboot into system.
= You can unplug your USB cable now.
= Power OFF your phone.
* Your custom recovery is now successfully installed!
= Boot into TWRP Recovery (While Powered OFF - HOLD Power, Home, and Volume UP buttons for 6 secs).. Let go of the buttons after the vibrate but just before you see the small blue writing appear at the top.. I was holding mine down for too long and it would just boot like normal and not recovery mode.
= MAKE A CURRENT BACKUP: Tap 'Select Storage' near the bottom > Select "Micro SDCard" > then "OK"
= Backup: Tick (enable): EFS Only > Swipe to Backup -- Hint: Change the filename from 'Auto-Generate' to 'EFS-ONLY'
* Note: You should only backup EFS by itself.. You only need to backup EFS one (1) time ever.
= Backup: Tick (enable): Boot, System, Data > Swipe to Backup -- Hint: You may change the filename from 'Auto-Generate' but its optional.
= Go back to Main Menu
= 'WIPE' > 'ADVANCED WIPE' > Tick (enable): Dalvik/ART Cache, Cache, Data, Internal Storage, and System.
= 'SWIPE TO WIPE'
= Go back one menu then 'FORMAT DATA' - type 'YES' and press blue checkmark.
= Go back to Main Menu
= Install Optimized CM13 ROM by Clicking 'INSTALL' > Find your Optimized CM13 ROM you downloaded. --> 'Select Storage' (near the bottom) > 'Micro SDCard' > 'OK'.
= Install Open GApps by Clicking 'ADD MORE ZIPS' > Find your Open GApps you downloaded.
= 'SWIPE to Confirm Flash'.
= Wait for completion.
= 'Wipe Cache and Dalvik'.
= 'REBOOT' into system.
* Your System is now successfully Installed!
* After your initial setup you need to tweak a few things:
= Settings > Location > Change to 'Device Only'.
= Settings > Location > 3-Dots > Scanning > DISABLE (untick) Wifi Scanning and Bluetooth Scanning.
= Pull-Down Notification Panel > GPS (Device Only) changed to disabled.
= App Drawer > Google > 3-Lines > Settings > Now Cards > Turn OFF
= App Drawer > Google > 3-Lines > Settings > Voice > OK GOOGLE Detection > Turn OFF
* You should setup SuperSU first thing.
= Go to Settings > Optimized CM Settings > Developer Options > Root Access > Turn ON (enable) 'APPS and ADB'.
= Install SuperSU by Chainfire from the Play Store and Update Binaries. (See SuperSU notes below)
* SuperSU Notes: A basic Superuser is pre-installed with this Rom (called 'Privacy Guard)'. It does Not give you any control. You will be able to use the traditional SuperSU from the Play Store (updating the SuperSU binaries will be Successful). After you have updated the binaries it will work great with our phones. SuperSU Pro Key can be installed from the Play Store. BUSYBOX SHOULD NOT BE INSTALLED. ITS ALREADY PRE-BUILT INTO THIS ROM.
When Privacy Guard prompts you in SuperSU for access, click 'Remember my choice' and hit 'ALLOW'.
You will never be prompted like this again. SuperSU will now take over control.
* IF YOU HAVE ANY PROBLEMS WITH MOBILE DATA, PHONE CALLS, OR TEXT MESSAGES ALWAYS CHECK YOUR APN SETTINGS! *
The following actions are made by me . they are not necessary for everyone.this is what i do and seems to work fine..replies like "lol omg wtf u say.nightly is not like that" etc are not needed. Get your brain work properly first. U may got skills but got sense?
Some notes/results etc about this update...This update is a critical update.contains big and risky kernel & ramdisk changes.first of all i removed the qmuxd logging...test team found a leak of qmuxd that makes the CPU0 stuck at a high freq producing extreme heat!...i found no way to fix that. @Chibbo said that ,this bug exists since years.
When does it happens ? it happens when u turn logcat off ,from stweaks.
Happens everytime ? No...doesnt happen on me but happens at @Chibbo .
So its random ? i think no.something has to be done with connection of basebandqmuxdyour country
another big issue...even if we have stabilize the BT somehow,there is always something new that will come and break our BT.i personally cant predict it.why?firstly cuz i am not that skilled secondly cuz i believe that any change coming to my upstream merge affects latest devices.so that ,it fcks our old bt device.Just like camera ,bt is a never-winning war.we just try to make it crash as less times as we can.current kernel has got old bt sources but is updated.
Think about that even Touchwiz stock has got bugged bt [emoji14]
I personally think bt crashes because it never closes,even if u kill the bt app...i dont know why that happens.
a reboot every 2-3 days with cleared cache/data of bt app MAY reduce our disconnects/reconnects
Ah....dat camera.camera is the hardest thing to make it work perfect like stock.why ?cuz we dont have the camera sources from samsung.as i have said again,we use an "emulator" of driver for camera.so even if camera is fine we got to find a camera app that will support our hardware/drivers/custom rom.sadly not many people are able to hack samsungs camera lib.also think about s4 is an old device.who would spend that time ? all i personally know is that camera bugs due to memory leak.thats means a function is called but never returns OR the functions that we want to be called ,CANT be called.nevermind...dont expect stable camera .i think that Open Camera HDR uses some custom stuff but its a paid app
member of test team said that busybox comes preinstalled to ROM.thats true....UNTIL NOW.
We changed that....why ?some apps was recognizing our busybox but couldnt run even it was installed.so users was installing
busybox from playstore and was overwriting ours.yes but our busybox was built to serve our kernel/stweaks
overwriting it was messing issues...
So what happent?
We added a custom directory of busybox at sbin/bb/busybox
This busybox is our busybox ,specially made for our rom/kernel/ramdisk scripts/stweaks
if a user want to install an app that requires busybox,he can simply download busybox from playstore just like he would do if he hadnt install it...changing the directory let us "hide" our busybox from default directories
Build CLANG with -O3 flag
clang is the new prebuilt that google switched to ,to build roms....its a c++ compiler ,newer than GCC
so -O3 flag is actually meaning to optimize the source code increasing the size of ROM (it gave +8mb to us).
Theoritically it will give us a better UI response,a better RAM writes,and overall performance