[ROM][6.0.1_r10][UNOFFICIAL] CyanogenMod 13.0 [2016-01-23]

[ROM][6.0.1_r10][UNOFFICIAL] CyanogenMod 13.0 [2016-01-23] - YU Yuphoria

Bug reports:
CyanogenMod 13 is in development and has several small bugs and missing translations. Complaints/demands/bug reports without logs will be ignored.
Explain how to reproduce the bug and attach logcat and dmesg (if you had a random reboot, also attach last_kmsg). If you don't know how to get those, you can use this app. Please, do not report bugs if you use any kind of mods (like xposed) or third party kernel.
Frequently Asked Questions:
Q) Will I get facebook/messenger app fc?
A) You shouldn't! Adreno blobs are now updated and now no dirty hacks required to boot up which in turn broke something.
Q) Where are Developer options?
A) Go to Settings > About phone, and press five times on Build number.
Q) How can I enable root access?
A) Go to Settings > Developer options > Root access, and enable it for apps, adb or both.
Q) I don't like superuser icon in statusbar, can I install SuperSU?
A) Ok yes, but read this. First enable root access from Developer options. Then flash SuperSU zip. Now open SuperSU app. It will say, 'SuperSU binary not installed'. So use TWRP/CWM method to install binaries. (This worked for me)
Q) How can I set 3G only network mode?
A)Method 1: Open Settings, Cellular Networks, now you can select LTE/3G/2G modes in 'Preferred network type' menu.
Method 2: Open dialer, dial *#*#4636#*#* , open first option "Phone Information", there you can set your preferred network mode.
Q) How do I update Gapps? (Also useful if you have Gapps related problems).
A) Reboot to recovery. Wipe System, Cache and Dalvik Cache. Install ROM + Gapps. (Yep, at a time) Reboot.

Reserved

Finally!! Great work

Solved : Gapps not able to flash
which gapps works best for this rom?arm,arm64 or x86.Im unable to flash open gapps.Please help.
Solved : Flashed ARM64-6.0-pico.Now it works great.Thanks developer for the wonderful ROM.Keep up your good work

Great Work!

Uc browser not working......

jayent said:
Uc browser not working......
Click to expand...
Click to collapse
Download UC Browser from here

please help
Hey I am facing problem while flashing thus ROM. Please help please

sahil314 said:
Hey I am facing problem while flashing thus ROM. Please help please
Click to expand...
Click to collapse
wipe/factory reset

Yash98 said:
wipe/factory reset
Click to expand...
Click to collapse
"GPS" not working.. phone getting restarted
---------- Post added at 04:59 AM ---------- Previous post was at 04:58 AM ----------
TheStrix said:
Bug reports:
CyanogenMod 13 is in development and has several small bugs and missing translations. Complaints/demands/bug reports without logs will be ignored.
Explain how to reproduce the bug and attach logcat and dmesg (if you had a random reboot, also attach last_kmsg). If you don't know how to get those, you can use this app. Please, do not report bugs if you use any kind of mods (like xposed) or third party kernel.
Frequently Asked Questions:
Q) Will I get facebook/messenger app fc?
A) You shouldn't! Adreno blobs are now updated and now no dirty hacks required to boot up which in turn broke something.
Q) Where are Developer options?
A) Go to Settings > About phone, and press five times on Build number.
Q) How can I enable root access?
A) Go to Settings > Developer options > Root access, and enable it for apps, adb or both.
Q) I don't like superuser icon in statusbar, can I install SuperSU?
A) Ok yes, but read this. First enable root access from Developer options. Then flash SuperSU zip. Now open SuperSU app. It will say, 'SuperSU binary not installed'. So use TWRP/CWM method to install binaries. (This worked for me)
Q) How can I set 3G only network mode?
A)Method 1: Open Settings, Cellular Networks, now you can select LTE/3G/2G modes in 'Preferred network type' menu.
Method 2: Open dialer, dial *#*#4636#*#* , open first option "Phone Information", there you can set your preferred network mode.
Q) How do I update Gapps? (Also useful if you have Gapps related problems).
A) Reboot to recovery. Wipe System, Cache and Dalvik Cache. Install ROM + Gapps. (Yep, at a time) Reboot.
Click to expand...
Click to collapse
"GPS" not working.. phone getting restarted

Update!
CyanogenMod 13.0 R2 Update:
Download: http://goo.gl/h7CkVJ
Changelog:
AOSP 6.0.1_r10 tag.
January 2016 security patches.
Fix offline charging issue (Screen didn't go completely off while offline charging earlier).
Fix Google+ app installation bug present in previous build.
Increased in-call volume speaker gain (reported by some users).
Updated build fingerprint from YU's latest COS release.
Some Wi-Fi updates.
Fix for external SD Card in CM file manager.
Replaced Toybox with Busybox (This may cause some root apps to crash, but CM now uses Toybox!).
Latest CyanogenMod sources with much new patches..

CyanogenMod 13.0 Jan 23rd update:
Download: https://www.androidfilehost.com/?fid=24385658843824514
Just don't hurry up. Read the whole post for once!
Changelog:
Support for F2FS for /data and /cache
Update audio configs to cope up with CyanogenMod's latest changes in audio HAL.
Switch to qcom libhealthd.msm standard library for offline charging (Also it shows battery % now while offline charge)
Switch to Snap camera
Enable USB MIDI support
RIL and connectivity updates
Update new regenerated blobs from crackling
CyanogenMod updates. (CM API v5, new wallpaper, etc. find out own ) [Many changes are made in CyanogenMod repo everyday, so of course can't list all]
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Damn, that was just copy paste from wikipedia and I just didn't get it! So what is F2FS in our language?
It a better file system than ext4 in terms of performance.
Useful Link: http://www.xda-developers.com/f2fs-put-to-the-test-against-ext4/
To get a better idea, XDA forum have a dedicated thread highlighting F2FS features and a very detailed comparison between EXT4 (file system we use by default) and F2FS!
Have a look here: http://forum.xda-developers.com/showthread.php?t=2697069
So, I liked F2FS and wanna try it! But, how do I?
First of all, backup your internal SD Card as it will be wiped if you are switching to F2FS.
So, to start with, first you'll need a new recovery. I compiled modified TWRP recovery with F2FS support and some other cool features like pressing power button will now switch device display off, also wiping the partitions should not take much time now as it did earlier! (EXT4 users can use the same recovery. I just made it for my convenience)
1. Download TWRP: https://www.androidfilehost.com/?fid=24385658843824749
2. In recovery, go to 'wipe' -> 'Advanced Wipe'
3. Check only 'Data' and tap on 'Repair or Change File System' -> 'Change File System'
4. Here select 'F2FS' and Swipe to Change
5. Repeat step 3 and 4 for 'Cache' by checking only 'Cache' in Wipe menu.
6. Reboot! Enjoy!
I want to get back to EXT4 again from F2FS, how should I?
Again, while you are changing your file system, the partition gets wiped. So do backup your data of Internal SD Card and proceed!
1. In recovery, go to 'wipe' -> 'Advanced Wipe'
2. Check only 'Data' and tap on 'Repair or Change File System' -> 'Change File System'
3. Here select 'EXT4' and Swipe to Change
4. Repeat step 2 and 3 for 'Cache' by checking only 'Cache' in Wipe menu.
5. Reboot
PS: Only support for F2FS is added on /data and /cache. It still uses EXT4 by default and is just same as it was in previous builds!

first of all
its an amazing rom
but would absolutely love it if i know how to activate power save mode
and a small request " can you add the theme engine from cyanogen os??????"
i really hate the cm theme engine

hello, why cm13 isn't official because there aren't no bugs?

aminvishwas said:
which gapps works best for this rom?arm,arm64 or x86.Im unable to flash open gapps.Please help.
Solved : Flashed ARM64-6.0-pico.Now it works great.Thanks developer for the wonderful ROM.Keep up your good work
Click to expand...
Click to collapse
Can't we use the gap 6.0 Full

problm in 5.0.2 ?
there is problm of wake up while charging that it may not happen while m charging phone sir can u pls tell me to fix this problm it will be appreciated could you help me pls....??

sahil314 said:
Hey I am facing problem while flashing thus ROM. Please help please
Click to expand...
Click to collapse
bro before flashing the zip file.
do following in TWRP
wipe davlik
wipe data
wipe cache
wipe system
and install the zip file the above error will not appear

reserved

sahil314 said:
Hey I am facing problem while flashing thus ROM. Please help please
Click to expand...
Click to collapse
wipe data and system and install and that will fix the error and one more thing can you make a system backup with twrp and give me i need this rom but my devices is irulu v3 and i try cm12 but its old now.

Related

[GearCM][i9500][6.0.x] Optimized CyanogenMod 13.0 for Samsung Galaxy S4 [20161203]

Use this thread =>http://goo.gl/6kTvJu for questions or discussions.
Only Bug Reports & Feedbacks are allowed here. Penalty: Post Removal by Moderators
{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
ROM Downloads
All not-working RenderServer hosted files can be found here: https://androidfilehost.com/user/?w=settings-dev-files&flid=50874
<< Stable >>
20161203 Build: https://www.androidfilehost.com/?fid=601300970940399905
<< Misc. (Modem & Recovery) >>
GearRecovery (based on TWRP Recovery) 20160220: https://www.androidfilehost.com/?fid=24421527759883765 <= Highly Recommended
I9500XXUHOD4 LL Modem: https://basketbuild.com/filedl/devs...s And Bootloaders/I9500-XXUHOD4-MODEM_CWM.zip <= Russian Modem, Recommended
I9500DDUHOA1 LL Modem: http://forum.xda-developers.com/attachment.php?attachmentid=3165311&d=1423927137 <= Indian Modem, use it if you're experiencing problems with Russian variant
Previous Releases:
20160828 Build: https://www.androidfilehost.com/?fid=24591000424960632
20160711 Build: https://www.androidfilehost.com/?fid=24591000424946159
20160710 Build: https://www.androidfilehost.com/?fid=24591000424945760
GearRecovery (based on TWRP Recovery) 20151003: https://www.androidfilehost.com/?fid=24052804347828835 <= Highly Recommended
<< Beta >>
20160502 Build: https://www.androidfilehost.com/?fid=24531172553916653
<< Alpha >>
20160101 Build: https://www.androidfilehost.com/?fid=24352994023703667
Google Apps (add-on)
http://opengapps.org/ <== Recommended <> Micro/Mini Modular Package. Do not choose Stock
Installation
3-button-combo = "Volume Up/+" + "Home/Center" + "Power/Lock"
- First time flashing GearCM 13.0 to your Galaxy S4 (or coming from TouchWiz/Stock Based ROMs)?
Root your device and install latest GearRecovery
Reboot into Recovery using 3-button-combo
Do a Backup!
WIPE (wipe data/factory reset + wipe cache partition + format /system partition)
Install the ROM from internal/external sdcard
Optionally install Google Addon
Done! You can now reboot the phone to enjoy the rom
- Upgrading from Official CM10.2/CM11/CM12/CM12.1 or GearCM 11/12/12.1?
Reboot into Recovery using 3-button-combo
Do a Backup!
Install latest GearRecovery
Reboot into new Recovery using 3-button-combo (if needed)
WIPE (wipe data/factory reset + wipe cache partition + format /system partition)
Install the ROM from internal/external sdcard
Optionally install the Google Addon
Done! You can now reboot the phone to enjoy the rom
- Upgrading from another build of GearCM 13.0?
Reboot into Recovery using 3-button-combo
Do a Backup!
Install latest GearRecovery
Reboot into new Recovery using 3-button-combo (if needed)
Install the ROM from internal/external sdcard
WIPE Dalvik/ART Cache (wipe cache partition + wipe dalvik cache)
Done! You can now reboot the phone to enjoy the rom
Known Issues (regarding latest available build)
Please do not report bugs if it is already listen in the list of known issues
Audio HAL isn't working correctly, causing VOIP issues, HDMI audio instabilities and mixer paths conflicts
STK Toolkit isn't working yet, SMSs aren't properly sent (RIL issue)
SELinux policies are almost complete, with just some minor missing rules
Wireless Display (or Miracast if you like) stream is corrupted, buffer issues
Adoptable Storage isn't stable, crashes while encrypting the external storage (Kernel Panic). Read Here: http://goo.gl/0w6DPt
Device Encryption isn't stable for the same issue that affects Adoptable Storage
Reporting Bugs
First of all, read this: http://www.chiark.greenend.org.uk/~sgtatham/bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Code:
What is your--
Phone model:
Radio (baseband) version:
GearCM version:
GearCM download url:
Google Apps version:
Did you--
wipe data/factory reset:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance Settings (other than stock):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Changelog
20161203:
Updated CM Sources
All missing features (that i have accidentally removed in the previous build) are back
Some Audio HAL stability improvements
Removed that dangerous Soft Reboot option
KERNEL: some updates here and there
Check my GearCM Github for more information
Previous Releases:
20160828:
Updated CM Sources (nice improvements are here)
Added new features for Screen Power Saving, play with LiveDisplay settings!
Enabled HDMI CEC support
Wireless Display & Screen Recording should work better now, but nothing guaranteed
20160711:
Updated CM Sources
Improved built-in Camera Latency with Flashlight
KERNEL: Fixed Battery Capacity
20160710:
Switched to Stable Release
Updated CM Sources
Fixed Wireless Display (even if not completely)
Fixed random Graphics Glitches
Fixed WiFi issues
Fixed Battery Drain
Fixed Camera Instabilities (no more crashes)
SELinux is now enabled, but on permissive mode.
DRM-dependent apps should be working fine now
Maxed Out ART Runtime Performance
OTA Updates are back, but with download links (AndroidFileHost limit)
Adoptable Storage is now working, but unstable. "Known Issues" explains why
Optimized Network Performance (WiFI & 3G)
Restored Android Marshmallow Doze Mode (power-saving)
Using latest INU OK2 proprietaries
KERNEL: switched to a whole new, and stabler, kernel
KERNEL: using latest INU OK2 kernel sources
KERNEL: enabled all features that might be required by some apps
20160502:
No Changelog provided yet, will be added soon.
20160101:
First Release (Alpha)
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[GearCM][i9500][6.0.x] Optimized CyanogenMod 13.0 for Samsung Galaxy S4, ROM for the Samsung Galaxy S4
Contributors
Alberto96, NBruderman, intervigil, codeworkx
Source Code: https://github.com/GearCM
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest Modem, TWRP or GearRecovery, and a working brain to manage GearCM features
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 20161203
Stable Release Date: 2016-12-03
Current Beta Version: 20160502
Beta Release Date: 2016-05-02
Created 2016-01-01
Last Updated 2016-12-03

Reserved
Important! Read this before any other question/doubt.
If someone doesn't like my ROMs, or doesn't like me, or even better, doesn't want to like/appreciate my works, then you can just go ahead and use/follow someone else works. Easy, not against XDA rules, and smart.
I'm not here for "fame" (or "glory" as someone in this forum said) unlike someone else, neither this is my job. I'm working on this device just because TW is far than usable (at least for me) on every Samsung device, not because someone else requested me to do it.
Click to expand...
Click to collapse
Differences between GearCM (Optimized CyanogenMod) and Official CyanogenMod (NIGHTLY):
Degrated Shadow said:
Enough of those dumb questions..
The Official CM rom is maintained by @Alberto96 and @intervigil
He makes the very recent changes here relating to performance...which are then in time pushed (even if partially) to CM Official Sources. The kernel is different because it has seLinux disabled and few minor tweaks you might not even notice...this GearCM ROM will have more performance. But CM will have their updated base changes which are included here with each update.
What I mean is you probably wont even notice what's different in terms of user interface. GearCM will have more performance. Official CM will have updated sources. But it will include GearCM's changes in time as @Alberto96 pushes them to CM
You can decide by a simple choice..more performance and not-nightly updated sources or similar/worse performance (improving with nightly updates) with updated sources. I would choose GearCM because of the reasons i mentioned above. Do what you will...and let this be a note to everybody who ask this again and again and again. Don't spam the thread with same question in every alternate page...because there are other people who might have different problems they need to ask. Read at least 15 previous pages and the first post Changelog before asking the question. Reading most of the times will give you a solution and if not most of the info you will read will help you anyway.
Click to expand...
Click to collapse

Reserved
FAQ (Frequently asked questions)
If there a procedure that i should follow in order to have a clean base to start from?
Yes, follow this procedure and you shouldn't have any issue.
Flash latest Stock ROM Odin package | http://www.sammobile.com/firmwares/download/55812/I9500XXUHOH7_I9500MBCHOF1_MBC | using latest Odin3 Flasher | http://forum.xda-developers.com/attachment.php?attachmentid=3446301&d=1440131361 | and Standard (not Chinese) .pit file. | http://forum.xda-developers.com/attachment.php?attachmentid=2343320&d=1382462885 |
After First Boot, Shutdown your device and Boot into recovery mode using 3 buttons combo (Volume +, Home, Power)
Wipe Data/Factory Reset using Volume Keys and Power Button (on Stock Recovery)
Flash latest TWRP 2.8.7.0 | https://dl.twrp.me/i9500/twrp-2.8.7.0-i9500.img.tar | using Odin3 | previously linked | (Untick Auto Reboot to avoid any issue)
Shutdown your device (pull off your battery)
Boot into recovery mode using 3 buttons combo | Volume +, Home, Power | (TWRP will boot now)
Flash latest GearRecovery (on TWRP)
Reboot into recovery mode using TWRP on-screen buttons | Home => Reboot => Recovery | (GearRecovery will boot now)
Clean completely your device (Format Data and Wipe All Partitions)
Reboot into recovery mode as did before (GearRecovery will boot again now)
Flash latest GearCM ROM
Home => Reboot => System
Where is "Developer Options" category?
To activate 'Developer Options' category in Settings you need to tap 7 times on 'Build number' located into Settings -> About Phone.
What can i do to fix VOIP audio calls?
There's not a real fix yet, so i found this useful workaround that could help you.
If you need to make a VOIP call:
1) Play something using stock music player (also third-party music players SHOULD be fine)
2) Do not pause audio playback
3) Make a call using your preferred VOIP app.
Or you can just use a Wired Headphone/Headset | BT Headphone/Headset.
This workaround should work also for incoming VOIP calls.
How can i solve problems with Hebrew language?
Go to "Developer Options" in Settings and check "Force RTL layout direction".
What can i do to reduce the "echo effect" while in-call?
Try to reduce in-call earpiece volume (if possible). Shouldn't be required on latest builds.
I'm having problems with battery life, what can i do?
1) Use "Greenify" to hibernate all apps with a "little cloud + 'Gcm' word inside" on the right of each app's name. Donation version is recommended because it allows deeper hibernation of apps
2) Disable "Location" or set it to mode "Battery Saving" (Settings -> Location)
3) Make sure that your 2G/3G mobile network signal level isn't always low or unstable
4) Deny "Wake Up" and "Keep Awake" permissions to Google and third-party apps. (Settings -> Privacy -> Privacy Guard -> Press menu button and check "Show built-in apps" -> Press menu button again and go to Advanced -> Horizontal Scroll to Device)
5) Disable "Sync" or sync only useful stuff like Contacts
6) Disable "Auto-rotate screen" (Settings -> Display & lights -> Rotation)
7) Use one of the latest Modem/Baseband listed on first post.
8) Disable Ambient Display
9) Install Xposed Framework and configure Amplify
If this isn't enough then replace your battery and/or reduce your phone usage. :silly:
Is GearCM OTA supported?
Yes (Since 20150707 Build)
Why is my phone over-heating while playing heavy-games or running heavy-apps?
Use a bit your brain to explain why. High CPU and GPU usage = high heat production. Your phone will automatically throttle CPU when needed so don't worry, it is safe and normal.
Can I use another kernel instead of the one included in the zip?
No. Only use the included kernel for 100% compatibility, bug reports with non-standard kernel will be ignored.
Can i disable S-View cover features (lock/unlock)?
Not yet.
*** IR Remote app isn't working anymore/was working on previous builds/causes my phone to crash, what can i do?
Contact *** IR Remote app developer.

woooww .. new topic .. good luck

30 Minutes left to the end of the upload (and don't worry, this isn't a placeholder)
Known Bugs:
- Camera
- Compass (untested)
- Synapse (not supported)
- OTA Updates (support will be added later)

GearCM 13 Alpha Build is up!
Enjoy

Alberto96 said:
GearCM 13 Alpha Build is up!
Enjoy
Click to expand...
Click to collapse
Thank you for your effort, downloading now , hope camera is fixed soon

Great job man thank you downloading now

can i dirty flash or must i clean install @Alberto96?

Bilal_503 said:
can i dirty flash or must i clean install @Alberto96?
Click to expand...
Click to collapse
You know that i'll always answer with two simple words: "CLEAN FLASH".

Thanks Alberto..
YOU ARE AMAZING!!!

Alberto96 said:
30 Minutes left to the end of the upload (and don't worry, this isn't a placeholder)
Known Bugs:
- Camera
- Compass (untested)
- Synapse (not supported)
- OTA Updates (support will be added later)
Click to expand...
Click to collapse
The Synapse 0.44 added support to Android M.
---------- Post added at 10:15 PM ---------- Previous post was at 10:14 PM ----------
Alberto96 said:
GearCM 13 Alpha Build is up!
Enjoy
Click to expand...
Click to collapse
Best New Year's gift!

treborbr said:
The Synapse 0.44 added support to Android M.
Click to expand...
Click to collapse
CM13 isn't using anymore Busybox so it isn't compatible for real. I need to compare Busybox & Toybox to check the differences.

I download and I've tested. sound problem resolved but could be better. not disturbin
thanks alberto. I hope to be much more beautiful

Downloading and gonna dual boot! Thanks a lot @Alberto96

Wow, that's what I had been looking for in the past months. Thank you for your hard work, and happy new year! :laugh:

Thanks man, I have been waiting for this for so long.

Does it support f2fs ?
Just to make sure there is no compatibility issues..
---------- Post added at 01:03 AM ---------- Previous post was at 12:27 AM ----------
After testing for 2 ours.. I can say there are no major bugs in the rom
Everything is working except for camera and it's much smoother than cm12.1

Is this latest build booting?
Sent from my GT-I9500 using Tapatalk

Mo0s said:
Is this latest build booting?
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
Yes, indeed.. That's why this thread..!
Sent from my GT-I9500 using Tapatalk

[ROM] [ 8.1.0 ] Official madOS - Vernee Thor [MT6753]

Reserved
First time Install Instructions
0) Preparation
0.1) Backup your important data to PC
0.2) Download “twrp_vernee_thor_oreo.img“:
http://www.mediafire.com/file/m58f5ifmopyb209/twrp_vernee_thor_oreo.img
0.3) Download “madOS_8.1.0_thor_2018xxyy.zip“ https://www.facebook.com/MediatekAndroidDevelopers/
0.4) Optional, Download “Google Apps (aka Gapps)“: http://opengapps.org/. Choose: “ARM64“, “Android 8.1“, “nano“ or “pico“ package
1) Flash the recovery and boot to it. (choose option a) if you don't have another TWRP already installed, else choose b))
1.1a) Boot in the BOOTLOADER mode (using ADB: "adb reboot-bootloader").
Then execute command “fastboot flash boot twrp_vernee_thor_oreo.img”;
and then “fastboot reboot” (this is a trick to directly bring you to the newly flashed recovery. You can't boot up your current/stock rom at this point anymore).
1.1b) Boot to your current TWRP. Choose install --> image, and select twrp_vernee_thor_oreo.img“. Then choose “recovery“ as the target. After few seconds, and succesful installation, hit “back“ several times, then go to “reboot --> recovery“
2) Install
2.0) Optional, but recommended: Go to "Wipe --> Advanced Wipe", click "Cache" and then "Repair or Change File system". Then select "Change File system" and choose "F2FS". Swipe to confirm.
Hit "back" three times (you can again choose a partition to change now). Choose "Data" and do as above.
Hit "back" several times, to get back to the main menu. Choose "Reboot --> Recovery".
2.1) While already in recovery (TWRP), connect your phone to pc, and copy “madOS_8.1.0_thor_2018xxyy.zip“ and the Google Apps to your phone.
2.2) Go to "Wipe", and directly slide the slider to the right.
2.3) Get back to main menu with the "back" button
2.4) Go to "Install" and hit “madOS_8.1.0_thor_2018xxyy.zip“, then uncheck all boxes and hit "Add more zips", now choose the Google Apps.
Confirm installation by swiping the slider to the right.
2.5) Reboot System
Click to expand...
Click to collapse
Follow up Install Instructions
Download rom and gapps
boot to recovery
flash rom and gapps
optional: flash superSu/Magisk
reboot system
General F.A.Q.
Q: What the hell is madOS ?
A: madOS, (M.A.D. Team OS), is a ROM based on pure A.O.S.P. with extended capabilities and customizations made by or merge/adapted by M.A.D. Team.
Q: Can I install this rom on any other device, than the one mentioned in the title/description?
A:
WTF! Of course not! It is not mentioned in the title/description for some reason...how stupid can one be?!
If you still come to my thread and ask this stupid question, I'll answer some random nonsense. Don't come to me to complain when you break your device!
Q: Which recovery should I use for this ROM?
A: Latest M.A.D. TWRP 3.2.1-0 recovery for OREO 8.1.0
Q: How do i flash new recovery ?
A:
1: You can flash it with a scatter file
2: You can simply flash it from the existing twrp recovery: Install> Install image> Select Oreo TWRP> Select "Recovery" as partition to flash.
Reboot to recovery to use new one
Q: Do i need to make full wipes?
A: YES, dont come crying at me, if you didn't .... ;p
Q: What is "full wipes" ?
A: To Wipe : Cache; System; DATA ...
Q: What should i use f2fs or ext4?
A: Both are supported, choose the one you desire
Q: Does this rom have any Theme support
A: Yup, We have working Theme Engine (madOS extras)
Update: On Oreo 8.1.0:
- We have extended Theme support even further ( madLauncher, messaging, etc)
- As well as many fixes
Q: Some translations are missing for my language, can I help?
A: Sure you can, please check our translations repo available here , you can either do a pull request, or if you don't know how to work with git, sent us the XML. Strings for your language ( Check Readme on repo).
Q: I want to report a bug(s) do you have an issue tracker?
A: Yeah... madOS issue tracker
Q: What's working ?
A: Check first Post for current status
Q: App "x" doesn't work, why?
A: Probably not compatible with OREO yet, feedback is welcome
Q: Is the rom rooted?
A: NO, But you can easily root with :
1: Magisk ( v14 onwards.)
2: Super SU ( v2.82 onwards)
IF there are problems in rooting, you need to report it to the root-threads...There's nothing we can do
Q: Should i root together with rom ?
A: Not advised.. mainly the Magisk that gives some weird issues...
Flash ROM and GAPPS (if you use gapps), after first boot get back to recovery and flash your desire rooting method
Q: Does xposed work?
A: Is there Xposed for O? ... then no ;p
Q: How is battery life with Oreo?
A: Pretty awesome
Q: Does this build support Vulcan?
A: No....duh! v
Q: Does doze work in this build?
A: Yup
Q: when will (feature/issue here) be fixed?
A: NO ETA , please
Porting F.A.Q.
No porting support, no port questions allowed on this thread, and porting PMs will be auto-deleted, porting replies will be reported as well
G.APPS F.A.Q.
Q:What GAPPS package should I use?
A: openGapps arm64 nano/pico
Q: How to properly install GAPPS?
A:Flash Rom + Flash Gapps at once
CREDITS and Thanks
madOS Team
Our translators, credits list here
A.O.S.P.
Pure Nexus
AOSPA
DU (Dirty Unicorns)
Omni
HELP supporting madOS
We do this on our free time, however we do have costs on maintaining this :/
Any donation is highly appreciated
You can donate by using
this link
If the above doesn't work in your country, then you can directly donate by using this e-mail adress: [email protected]
About madOS Proprietary Apps
You are NOT allowed by any means, to use our madOS apps on any other build, your rom
This is exclusively for OFFICIAL madOS ROM releases
@To Moderators: Feel free to clean the thread, whenever users start spamming, severe OT, or questioning about porting...

Reserved

Can I install it on my K4 Note?

Pritam Tumma said:
Can I install it on my K4 Note?
Click to expand...
Click to collapse
Can you read?

Is it possible to roolback to nougat (7.1.2) after install this update?

drifeter said:
Is it possible to roolback to nougat (7.1.2) after install this update?
Click to expand...
Click to collapse
Yes, you would need to flash the N twrp, wipe and flash the N rom

"Size of image is larger than target device" trying to flash new recovery. I just wiped everything, now I'm out of OS for this moment xD
Can you help me?
I used your last OS on this phone. It's before october(received it on may of that year) and MT6753
I have twrp 3.0.... from megthebest
Thank you for your patience
--
EDIT: Can I wipe "internal storage"? I didn't wipe everything :v

ZeDdYRov said:
"Size of image is larger than target device" trying to flash new recovery. I just wiped everything, now I'm out of OS for this moment xD
Can you help me?
I used your last OS on this phone. It's before october(received it on may of that year) and MT6753
I have twrp 3.0.... from megthebest
Thank you for your patience
--
EDIT: Can I wipe "internal storage"? I didn't wipe everything :v
Click to expand...
Click to collapse
I'll check the size error in a bit...
Of course you can wipe internal storage, but keep in mind that this is where your pictures are.
edit: checked/flashed the twrp_vernee_thor_oreo.img.... all fine with it...its size is 13.4mb, the recovery partition is 16mb. i suppose this 'megTheBest recovery' just isn't the best....

DerTeufel1980 said:
I'll check the size error in a bit...
Of course you can wipe internal storage, but keep in mind that this is where your pictures are.
Click to expand...
Click to collapse
Thank you for your quick response!
I wiped internal storage, data, cache, and system. Do I should wipe anything more in order for this to work? I'm still stuck on the error. I go to Install - Install Image, pick the twrp_vernee_thor_oreo.img file on Recovery Partition, and receive the message on the comment above.

ZeDdYRov said:
Thank you for your quick response!
I wiped internal storage, data, cache, and system. Do I should wipe anything more in order for this to work? I'm still stuck on the error. I go to Install - Install Image, pick the twrp_vernee_thor_oreo.img file on Recovery Partition, and receive the message on the comment above.
Click to expand...
Click to collapse
Since you already removed everything, I'd suggest to just install the stock 6.0 rom with flashtool and 'firmware upgrade' option

DerTeufel1980 said:
I'll check the size error in a bit...
Of course you can wipe internal storage, but keep in mind that this is where your pictures are.
edit: checked/flashed the twrp_vernee_thor_oreo.img.... all fine with it...its size is 13.4mb, the recovery partition is 16mb. i suppose this 'megTheBest recovery' just isn't the best....
Click to expand...
Click to collapse
lol, I just gave the name of the dev because could help you figure it out. I'm n00b on this :V
I just did sh** with the files. I was trying to flash with a file called twrp_blablabla.img that was 422MB. For some reason I missclicked on the file while saving :v
EDIT: SORRY and Thank you

Yeahhhhhh finally 8.1 on our Thor.... So great!
Thank you so much Mad-team.
Weeeeeeeeeeeeee!!!

DerTeufel1980
Thank you for your work
Everything works without problems.
:good:

I'm on madOS for 40min and I'm loving it. This is fully customize as you want this machine working. Well played!!! LOVE YOU MAD TEAM

Hello again! Software buttons get bugged when we enter on opened apps menu, and its has a ghost start buttons I'm n00b and I found a bug: D

ZeDdYRov said:
Hello again! Software buttons get bugged when we enter on opened apps menu, and its has a ghost start buttons I'm n00b and I found a bug: D
Click to expand...
Click to collapse
I am using softbuttons for a long time and they always work good. Maybe you can try to go back to default settings... Wipe cache/dalvik and try again

This is for the first revision, is it possible for you to make it for the second? Please...

RalphMalph said:
I am using softbuttons for a long time and they always work good. Maybe you can try to go back to default settings... Wipe cache/dalvik and try again
Click to expand...
Click to collapse
If I could be able to change what buttons do... the back button on soft button is on the right, and I'm used to it on the left. There's any option on madOS to change what I'm telling to you?
EDIT: I read second time and notice what you said. I'll try! Thank you for the tip

ppdua said:
This is for the first revision, is it possible for you to make it for the second? Please...
Click to expand...
Click to collapse
Re-read at least the first ten lines of the first post, before asking things like this

[ROM][UNOFFICIAL]LineageOS-16.0[Evert][Moto G6 Plus]

{
"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"
}
LIneageOS is a free, community built, after-market firmware distribution of Android re-branded CyanogeMod, which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project and CyanogenMod with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS please visit Gerrit Code Review.
Warning!!!
BackUp EFS partition before installing. .If you lose IMEI , use this backup to retrieve it in future.
Installation
Boot the newest TWRP .img
Flash copy-partitions-AB.zip from second post. (This will prevent device from getting bricked if you are coming from stock rom for the first time. It takes a backup of active slot to inactive slot)
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest build
Reboot to fastboot and do fastboot -w via terminal
Boot into "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - Only MindTheGApps arm64 are compatible, OpenGApps are not compatible with A/B yet: MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Downloads
Warning
If you are coming from stock ROM and it's your first time flashing lineage, flash copy-partition zip (See second post) unless your device will brick and I'm not responsible
- LineageOS : Unoffical Builds
- TWRP : Get here
Bugs
You tell me
Reporting bugs
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modifies system files
DO NOT report bugs if you've installed xposed and/or other mods
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Code:
adb logcat > logcat.txt
Code:
adb shell dmesg > dmesg.txt
If it is a random reboot, grab kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Code:
adb shell cat /sys/fs/pstore/console-ramoops
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs reported in the lastest 5 pages of this thread. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* LineageOS version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
F.A.Q.
ROOT! ROOT! Give me root or i'll die!!! Where root is???
First of all DO NOT flash any SuperSu/SuperUser/SuperMan zip package to get root. Go to Settings>Developement Settings>Root access and select "Apps Only"
Why no nightly today?
Build failed. Check again tomorrow
When do I have to wipe data?
You must wipe data only when you're switching from another rom or migrating to Snapshot branch from Nightly and vice versa. You don't need to wipe data when you update in the same release channe (this applies to 13.0 -> 14.1 upgrades too)
Will you add <insert awesome feature here>?
I won't. If you write it, submit a commit to gerrit, where it will be reviewed.
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Kernel Source : Here
XDA:DevDB Information
LineageOS, ROM for the Moto G6 Plus
Contributors
rahulsnair, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP
Based On: LineageOS
Version Information
Status: Stable
Created 2018-10-22
Last Updated 2018-12-28

Copy Partition- Initial Setup
Flash the attachement via TWRP

Fantastic, can't wait to try this! :good: The copy-partition zip seems to be missing though? :crying:

Awesome! Thank you, can't wait to try it out.
Is the copy partitions zip the same as the one on the Lineage OS 15.1 thread?

Daniel47833 said:
Awesome! Thank you, can't wait to try it out.
Is the copy partitions zip the same as the one on the Lineage OS 15.1 thread?
Click to expand...
Click to collapse
Yes.

"Pixel setup keeps stopping" after flashing Mindthegapps. Which version exactly, am I supposed to use?

Mara-X said:
"Pixel setup keeps stopping" after flashing Mindthegapps. Which version exactly, am I supposed to use?
Click to expand...
Click to collapse
When that app stop working select app info, force stop and clear app data.
And try again it'll work
And when you want to restore your stuff it'll show another error: "data transfer stop working" (I don't remember exact name) do the same force stop and clear data but this time allow all the permissions (storage, calls, etc)
Sent from my g(6) plus using XDA Labs

RokCruz said:
When that app stop working select app info, force stop and clear app data.
And try again it'll work
And when you want to restore your stuff it'll show another error: "data transfer stop working" (I don't remember exact name) do the same force stop and clear data but this time allow all the permissions (storage, calls, etc)
Sent from my g(6) plus using XDA Labs
Click to expand...
Click to collapse
Hmm. Clear data is greyed out, can only clear cache and that doesn't help.

Mara-X said:
Hmm. Clear data is greyed out, can only clear cache and that doesn't help.
Click to expand...
Click to collapse
Try with opengapps nano package
Sent from my g(6) plus using XDA Labs

Mara-X said:
Hmm. Clear data is greyed out, can only clear cache and that doesn't help.
Click to expand...
Click to collapse
? The data transfer tool and Pixel set up both require notification access. Should solve the issue. ??

ksk35695 said:
The data transfer tool and Pixel set up both require notification access. Should solve the issue.
Click to expand...
Click to collapse
Hello, how can I give notification access to the pixel set up? I can't find the option


Daniel47833 said:
Hello, how can I give notification access to the pixel set up? I can't find the option
Click to expand...
Click to collapse
Goto Apps & notifications, scroll down to Special app access, There's the noticfication access around the middle of the list.
Always has worked for me in this senario. Good luck.

Nice work! Congratulations @rahulsnair + everybody on the team. Wow, did You receive the device on Monday this week?
So, I flashed and I'm writing the journey here and keep editing as I go:
- Is Emergency calling working, can you connect? You can test by calling there and saying that you wanted to test.
- Moto actions - Working!
- Is the camera quality the same-ish? I'd say yes.
- Can I install Moto Camera 2 (Stock)? Yes.
- Tethering (yes) / Hotspot (working) / Bluetooth calling (working) / Casting (working) / NFC (working).
- Since "Copy A -> B Partitions zip" makes a copy of the current ROM to another slot (correct?), how to restore from there? I know how to restore from twrp backup.
[STROKE] EDIT: At the moment I'm getting "Pixel Setup keeps stopping" Cleared cache. Did not help. I have no navbar. For some reason Gapps didn't flash correctly I think. Trying again from there.[/STROKE]
EDIT2: You have the wrong link in OP. It points to 8.x MindTheGapps
Here's the 9.x version:
https://androidfilehost.com/?w=file...0cea2c259bd6b42b84ebd97a7d581187be08d20207d94
The same error manifests in 9.0 MindTheGapps. I got a little further though. But it's possible to plough through. Just reboot if you get stuck like I did and you will get there.
* Still no navbar during setup. (This might possibly be remedied by enabling on-screen navbar before flashing gapps, maybe: "settings -> system -> buttons).
* When connecting to wifi at setup, it will connect, but nothing happens, no "next" button"
* Not able to skip restoring backup from Google account.
* Data Migration Tool shows that its pixel version. Give permissions by clicking "App Info", "Permissions", check all.
* I have a strong feeling I have flashed MindTheGapps for Pixel :silly::highfive::laugh:
Wohoo! Made it through the setup, and I have a NavBar! And a working ROM! Super! (Some time later) - It's an awesome smooth driver. Absolutely beautiful.
* TWRP is suddenly showing garbled folders in sdcard. There was a post about that... Lemme see -- Ok so the problem is force_encryption. For that I'd need help, how to change that?
* Computer does not see external sd anymore
* Integrated E-mail app couldn't log to Gmail
* Music player didn't see external SD - fixed by magisk module "ExSdcard Access Enabler".
* Audio Fx didn't change anything - there's a fix to try clearing the data and cache and see if it starts working - I installed Viper4Android FX through Magisk Manager, works.

weazie said:
Nice work! Congratulations @rahulsnair + everybody on the team. Wow, did You receive the device on Monday this week?
So, I flashed and I'm writing the journey here and keep editing as I go:
- Is Emergency calling working, can you connect? You can test by calling there and saying that you wanted to test.
- Moto actions - Working!
- Is the camera quality the same-ish? I'd say yes.
- Can I install Moto Camera 2 (Stock)? Yes.
- Tethering (yes) / Hotspot (working) / Bluetooth calling (working) / Casting (working) / NFC (working).
- Since "Copy A -> B Partitions zip" makes a copy of the current ROM to another slot (correct?), how to restore from there? I know how to restore from twrp backup.
[STROKE] EDIT: At the moment I'm getting "Pixel Setup keeps stopping" Cleared cache. Did not help. I have no navbar. For some reason Gapps didn't flash correctly I think. Trying again from there.[/STROKE]
EDIT2: You have the wrong link in OP. It points to 8.x MindTheGapps
Here's the 9.x version:
https://androidfilehost.com/?w=file...0cea2c259bd6b42b84ebd97a7d581187be08d20207d94
The same error manifests in 9.0 MindTheGapps. I got a little further though. But it's possible to plough through. Just reboot if you get stuck like I did and you will get there.
* Still no navbar during setup. (This might possibly be remedied by enabling on-screen navbar before flashing gapps, maybe: "settings -> system -> buttons).
* When connecting to wifi at setup, it will connect, but nothing happens, no "next" button"
* Not able to skip restoring backup from Google account.
* Data Migration Tool shows that its pixel version. Give permissions by clicking "App Info", "Permissions", check all.
* I have a strong feeling I have flashed MindTheGapps for Pixel :silly::highfive::laugh:
Wohoo! Made it through the setup, and I have a NavBar! And a working ROM! Super! (Some time later) - It's an awesome smooth driver. Absolutely beautiful.
* TWRP is suddenly showing garbled folders in sdcard. There was a post about that... Lemme see -- Ok so the problem is force_encryption. For that I'd need help, how to change that?
* Computer does not see external sd anymore
* Integrated E-mail app couldn't log to Gmail
* Music player didn't see external SD - fixed by magisk module "ExSdcard Access Enabler".
* Audio Fx didn't change anything - there's a fix to try clearing the data and cache and see if it starts working - I installed Viper4Android FX through Magisk Manager, works.
Click to expand...
Click to collapse
I'm not going to test emergency services.
Moto actions do work-and this is why you don't see a navbar on setup. Fingerprint gestures, swipe right to left to go back,tap for home, left to right for recent, long press for assistant.
Copy partions- this should let you dual boot roms. So los15.1 on slot a and slot b can have Los16. The twrp reboot screen can allow you to choose your boot slot.
Gapps-you can use any gapps really just be sure to flash them if you flash a rom update. I like opengapps arm64 nano builds myself. Then install Google apps from play store.
Twrp- we have to wait for devs to deal with this. It will be fixed in time if it's not fixed with the new official twrp(I haven't tested it yet). It only applies to internal storage. SD card won't be scrambled.
SD card-the mount point is wrong. I think it was /run/media/sdcard or something similar. Some apps can find the path and some can't.
Sent from my Moto G6 Plus using XDA Labs

Xplorer4x4 said:
Moto actions do work-and this is why you don't see a navbar on setup.
SD card-the mount point is wrong. I think it was /run/media/sdcard or something similar. Some apps can find the path and some can't.
Click to expand...
Click to collapse
Great, thanks for clarifying
My post above is written as I go through the setup, therefore a mess.
External SD resides at /mnt/media_rw/(sd_card_name).
Easiest way to fix (most apps) to recognize it is to load ExSdCard Access Enabler module in Magisk Manager.

Just to clear up something the reason mavnar isn't shown is you need to use fingerprint gestures. Swipe left to right for recent, tap for home, swipe left to right to go back. Then you can activate navbar in settings after set up.
Sent from my Moto G6 Plus using XDA Labs

weazie said:
Easiest way to fix (most apps) to recognize it is to load ExSdCard Access Enabler module in Magisk Manager.
Click to expand...
Click to collapse
This method unfortunately doesn't work in Lightroom. "Use SD Card" in "Device Info & Storage" is still grayed out.

Alpetrus said:
This method unfortunately doesn't work in Lightroom. "Use SD Card" in "Device Info & Storage" is still grayed out.
Click to expand...
Click to collapse
yes, it seems so. I asked this question in Adobe Support, but didn't get a satisfactory answer.

Is anyone else having a problem enabling the microphone in Gboard? It's not a big issue as I'm able to switch to Google Voice typing on the fly. I was just wondering if it's something I did, or if it is something with this ROM.
For reference I installed Nano Gapps, and Gboard from the store.

DocFallingApart said:
Is anyone else having a problem enabling the microphone in Gboard? It's not a big issue as I'm able to switch to Google Voice typing on the fly. I was just wondering if it's something I did, or if it is something with this ROM.
For reference I installed Nano Gapps, and Gboard from the store.
Click to expand...
Click to collapse
Have you enabled microphone permissions from settings - apps?

[ROM][UNOFFICIAL][8.1.0] LineageOS 15.1 [I9515][I9515L]

Code:
* [B][U]Your warranty is now void.[/U][/B]
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)Q: Whenever I try flashing any lineage-15.1 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.2. Simply flash version 3.2 or higher, reboot back into recovery, and flash the rom zip again.
Q: Why is my phone warmer/hotter and the battery noticeably drained after flashing a build?
A: The wipe process that is a part of the installation procedure deletes some important configuration data, ie. BATTERYSTATS, which keep track of the battery's power level. These data ensure a balanced power management profile for all the hardware components of your phone. This is normal and nothing to worry about at all. Your battery drain will return to normal within a day or two.
If, however, you notice increased battery drain over a few days, check your signal. Android automatically re-directs battery power to the antennas to compensate for a weak signal from the tower to which your phone is connected at that time. If your signal is strong, check the following:
1) You missed one of the Wipe steps in the flashing procedure.
2) You are running an old bootloader or modem. Flash the most recent one listed for your variant either under the links below. Note: Use the "AP" button in Odin to flash ripee's combined BL_CP tar files.
3) How old is your battery? Official replacement Samsung batteries typically last around 1 year if you recharge them regularly, ie. once a day. Since the Galaxy S4 Value Edition over 4 years old, it is normal for your original battery to start failing, but official Samsung batteries should not cost more than USD 20 nowadays.
4) If all else fails, start over! Go through the entire installation procedure, including flashing a stock Marshmallow build, and going from there. Do NOT skip any steps this time!
Q: Will the jfvelte ever receive official builds from LineageOS?
A: In short, no. The reason is that, in order to get a modern version of Android working properly on an ageing device, some recent commits needed to have been reverted and some legacy commits needed to have been re-introduced into the current source branch. These include a fix for something as fundamental as video recording with both the AOSP and 3rd party camera apps.
Q: How often will new builds be released?
A: At least once per month: as soon as possible after each new Android security patch level is merged and whenever a new feature is added or a bug is fixed.
If the first Oreo build you are flashing is 0220 or later, please clean flash it, as some users have reported problems with dirty flashing builds from 0220 or later over top of builds older than 0220.
ROMs
Exodusnick
Build files downloaded with the OTA updater can be found in /data/lineageos.updater. New builds are released weekly.
-
YouTube Video
Magisk
recommended Gapps Pico or Nano ARM 8.1
If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS, CyanogenMod, or any other custom ROM, you must perform a clean install of LineageOS 15.1!
How to flash LineageOS and Open GAppsFULL WIPE (with external microsd card)
1. Move any files you want to keep to your External MicroSD Card – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the external MicroSD storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with NO Home PC access)
1. Move any files you want to keep to a safe folder - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with Home PC access)
1. Move any files you want to keep to your Home PC - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibrate),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
13. Once first boot is completed you can safely move your files back onto your Internal Storage.
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
Bluetooth calls
- You tell us!
Changelog
All major features and bug fixes are discussed by Exodusnick and ripee in this thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- sombree and every other open source developer and tester who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the jfvelte.
Join us on Telegram[/URL], courtesy of Exodusnick!
Sources
XDA:DevDB Information
LineageOS 15.1, ROM for the Samsung Galaxy S4
Contributors
Exodusnick
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: Stock KitKat for your variant.
Version Information
Status: Stable
Current Stable Version: 8.1.0
Stable Release Date: 2019-05-17
Created 2018-12-29
Last Updated 2019-06-19

Reserved

Reserved

deleted

Thanks . Can you please build rom with Android GO configuration enabled because I think it will improve performance of this device.

adarshadhungel1 said:
Thanks . Can you please build rom with Android GO configuration enabled because I think it will improve performance of this device.
Click to expand...
Click to collapse
You are no doubt correct, but at this stage we are re-building the sources in the lineage-15.1 branch, for which there are currently none. Once we figure that out, we'll take a look at Go.

wifi is not working.
Is there a workaround for it ?

blunatic said:
wifi is not working.
Is there a workaround for it ?
Click to expand...
Click to collapse
Read the OP please. This rom is a WIP.

hello I have this very good equipment the update towards lack since android already goes for its version 9 if I would like to know the wifi for when it will be?? thanks.

hello such thanks for the contribution, the following when I try to install I do all the procedure as it appears in the indications, but when restarting the phone freezes in the logo of lineage and re-start from there does not pass does not arrive nor to how to configure the rom that can be due?

Kelbimiguel said:
hello such thanks for the contribution, the following when I try to install I do all the procedure as it appears in the indications, but when restarting the phone freezes in the logo of lineage and re-start from there does not pass does not arrive nor to how to configure the rom that can be due?
Click to expand...
Click to collapse
Which build did you try installing?

Don't installation
with this ROM I observed that it is the most recent

lineage-15.1-20181226-UNOFFICIAL-jfve "this rom does not install"

Kelbimiguel said:
lineage-15.1-20181226-UNOFFICIAL-jfve "this rom does not install"
Click to expand...
Click to collapse
Ok thank you for your feedback. I will delete this build.
When I am ready with another build, I will let you know.

Installed
Ready installed and running, wifi does not work or read the Micro SD, I'm still trying ...

Kelbimiguel said:
Ready installed and running, wifi does not work or read the Micro SD, I'm still trying ...
Click to expand...
Click to collapse
Yes, this build works, unfortunately we lost the copy of the sources, and I'm trying to re-create exactly what we did to make 1208 work.

lineage-15.1-20181226-UNOFFICIAL-jfvelte.zip

hello install the rom that you just published the lineage-15.1-20181226-UNOFFICIAL-jfvelte.zip and when installed, the screen does not react to touch it, you can not configure or do anything...

Kelbimiguel said:
hello install the rom that you just published the lineage-15.1-20181226-UNOFFICIAL-jfvelte.zip and when installed, the screen does not react to touch it, you can not configure or do anything...
Click to expand...
Click to collapse
Yes, I suspected as much, this is a known bug. I will keep working on it.

delete my thread immediately thank you ........

[ROM][DISCONTINUED][9] LineageOS 16.0 [I9515][I9515L]

Code:
* [B][U]Your warranty is now void.[/U][/B]
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)Q: Whenever I try flashing any lineage-16.0 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.2. Simply flash the linked below version 3.2 or higher, reboot back into recovery, and flash the rom zip again.
Q: Why is my phone warmer/hotter and the battery noticeably drained after flashing a build?
A: The wipe process that is a part of the installation procedure deletes some important configuration data, ie. BATTERYSTATS, which keep track of the battery's power level. These data ensure a balanced power management profile for all the hardware components of your phone. This is normal and nothing to worry about at all. Your battery drain will return to normal within a day or two.
If, however, you notice increased battery drain over a few days, check your signal. Android automatically re-directs battery power to the antennas to compensate for a weak signal from the tower to which your phone is connected at that time. If your signal is strong, check the following:
1) You missed one of the Wipe steps in the flashing procedure.
2) You are running an old bootloader or modem. Flash the most recent one listed for your variant under the links in the TWRP thread. Note: Use the "AP" button in Odin to flash ripee's combined BL_CP tar files.
3) How old is your battery? Official replacement Samsung batteries typically last around 1 year if you recharge them regularly, ie. once a day. Since the Galaxy S4 Value Edition over 5 years old, it is normal for your original battery to start failing, but official Samsung batteries should not cost more than USD 20 nowadays.
4) If all else fails, start over! Go through the entire installation procedure, including flashing a stock Marshmallow build, and going from there. Do NOT skip any steps this time!
Q: Will jfvelte ever receive official builds from LineageOS?
A: YES! The first official Pie build was released on 0818!
Q: How often will new builds be released?
A: There will be no further unofficial builds on a regular basis, only whenever a new feature or bug fix is being tested. Please discuss all future unofficial builds with me via pm or on Telegram.
ROMs
ripee
- GT-I9515/L: jfvelte
LineageOS Extras
- addonsu-16.0-arm-signed.zip
- addonsu-remove-16.0-arm-signed.zip
Magisk
Open GApps
If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS, CyanogenMod, or any other custom ROM, you must perform a clean install of LineageOS 16.0!
How to flash LineageOS and Open GAppsFULL WIPE (with external microsd card)
1. Move any files you want to keep to your External MicroSD Card – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the external MicroSD storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with NO Home PC access)
1. Move any files you want to keep to a safe folder - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with Home PC access)
1. Move any files you want to keep to your Home PC - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibrate),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
13. Once first boot is completed you can safely move your files back onto your Internal Storage.
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
- You tell me!
Changelog
All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- arco68, npjohnson, and every open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for jfvelte.
Sources
- android_device_samsung_jf-common
- android_device_samsung_jfvelte
- android_kernel_samsung_jf
XDA:DevDB Information
LineageOS 16.0, ROM for the Samsung Galaxy S4
Contributors
ripee, Exodusnick, PixelBoot, sonic_sakthivel123, chingoboy, Roberto.caramia, sombree
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Stock KitKat for your variant.
Version Information
Status: Stable
Current Stable Version: 9
Stable Release Date: 2019-08-17
Created 2019-07-13
Last Updated 2019-08-17

Reserved
Mod Edit:. Development must be primarily accomplished via Xda. TG group traffic not permitted without any development on Xda.
OP Edit: Sources updated.

Reserved

I'm using this ROM since one month and I can say that is the smoothest I ever run on my phone.
So I would say thank you to @ripee for his hard work and to let me being part of the testing.

Thanks to @ripee , my phone is back from its dead!

* * * Thread Cleaned * * *
Let's keep the comments related to development of this Rom, not snarky, disguised attacks on other members.
If you believe someone has violated Forum Rules, simply REPORT the comment. Making your argument in the development thread is not only prohibited, it shows poor character and clutters Xda with useless rubbish.
This will be the only courtesy warning those involved will receive.
Please, follow the rules when posting, and take the appropriate course of action to report any violations.
Thanks for your cooperation.

Changelog
Build 0716
* BT calling is fixed!
* Synced with LineageOS sources.

app startup option
I can't find the app stop option at startup as lineage os 14.1

Diabolik2770 said:
I can't find the app stop option at startup as lineage os 14.1
Click to expand...
Click to collapse
I don't fully understand what you mean. I don't remember if this was a feature in 14.1, but if it was, it has been removed in 16.0.
If you want to disable an app so that it's hidden, you have to do it in its settings. You have to do this for every app you want to hide.

How is the battery drain and the speed on this ROM? Stability?
I have not changed the ROM on this phone for a very long time!
Currently I am still using CM13, which (except for a sometimes rather buggy camera access) works pretty well. The battery drain and speed is not perfect, but who expects this on a phone this old. It is enough to use it daily without pain.
But I can already say thank you very much for this ROM and for keeping this device alive. I am really suriprised to see a rather uncommon device still supported after so many years.

5g BUG
Wifi 5G signal is too weak, can't stay connected for long...

Changelog
Build 0810
* Sources changed to official jfvelte and jf-common repos: one step closer to official support!
* Synced with LineageOS sources.
In order to build your own, use this roomservice:
Code:
. build/envsetup.sh
repopick -f 250250 253025
brunch jfvelte

bootloop in i9515L
I am installing the rom correctly but I get a message "Set Warranty Bit: Kernel" and it is in boot loop does anyone know how to solve?

"Set Warranty Bit: Kernel"
is normal .
The first boot process can take up to 10 minutes.

Exodusnick said:
"Set Warranty Bit: Kernel"
is normal .
The first boot process can take up to 10 minutes.
Click to expand...
Click to collapse
I think I wrote it wrong sorry for the English. After the screen written "GALAXY S4 I9515L" the screen goes black and restarts, should I wait then?

@WevsSW
S4 I9515L I can't say anything because I don't own the device, sorry
but normally it should work on the device, too.

Strange that only lineage 15 and 16 don't work for me. All the other custom roms I tested worked, including lineage 14.1... Even so, thank you very much and sorry for the inconvenience

Its over 36hrs+ that I installed this rom & I didnt have any issue, its amazing and thanks to everyone who is making this happen.
Diabolik2770 said:
I can't find the app stop option at startup as lineage os 14.1
Click to expand...
Click to collapse
You need to enable Developer options by going to Settings > About phone > scroll to the end and tap 7 or so times on Build number.
Then go back to Settings > System > Advanced > Developer options > Memory > Apps started on boot...
Then you can enable and disable for each individual apps including other permissions.

Respect and appreciate your efforts @ripee for making ROM for this device on Pie:good::victory:
Using your 1st build since a week and the device works without issues. Battery is definitely better than Oreo.
Thanks for release!

adammanson said:
Its over 36hrs+ that I installed this rom & I didnt have any issue, its amazing and thanks to everyone who is making this happen.
You need to enable Developer options by going to Settings > About phone > scroll to the end and tap 7 or so times on Build number.
Then go back to Settings > System > Advanced > Developer options > Memory > Apps started on boot...
Then you can enable and disable for each individual apps including other permissions.
Click to expand...
Click to collapse
found
Thank You !!

Database Info

welcome