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

[ROM][UNOFFICIAL][8.1.0] LineageOS 15.1 [I9515][I9515L] - Galaxy S 4 General

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 ........

Related

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

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.

[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][DISCONTINUED][9] LineageOS 16.0 [deb][flo]

{
"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, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
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: I am seeing Error 7 when trying to flash a GApps package.
A: This is due to the system partition being too small to fit both the rom and the GApps package. You need to re-partition it with a tool such as the one created by Clamor (linked below). You will only need to do this once.
Q: When will any of the variants receive official builds from LineageOS?
A: Not before all the issues listed under "Bugs" below are fixed.
Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.
Q: What will some of the differences be between unofficial and official builds?
A: The following technical changes will take effect:
- Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
- Phone status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
- The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
Note: Each official build will be cooked and released by LineageOS on their schedule and only if no major unexpected bug is introduced into the source code. The developers will announce if and when their source code will be submitted to Lineage for official support and when we can expect to see the first official builds.
Q: How often will new builds be released?
A: About once a week for both deb and flo, as soon as possible after each new Android security patch level is merged, and of course whenever a new feature is added or a bug is fixed.
[REPARTITION] Nexus 7 (2013) Repartition [FLO/DEB] [16GB/32GB] [UA TWRP]
ROMs
pitrus-
- LTE: deb
- Wi-Fi: flo
LineageOS Extras
- addonsu-16.0-arm-signed.zip
- addonsu-remove-16.0-arm-signed.zip
Magisk
Open GApps
How to flash LineageOS and Open GApps1. Move any files you want to keep to your computer or flash drive via a USB OTG cable – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Boot into Recovery Mode (Hold volume up and Power button until you see TWRP's splash screen),
4. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
5. Swipe to Wipe at Bottom of Screen,
6. Back to Main start screen,
7. Wipe > Format Data,
8. Type 'Yes' and press blue checkmark at the bottom-right corner,
9. Go Back to Main Start Screen,
10. Move your LineageOS Rom and GApps Package to the internal storage,
11. Install > select a zip file to flash (optionally, Add More Zips > select another zip file to flash),
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
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
- Encryption does not work at all. Upon encrypting your tablet, you will be unable to reboot into System. This is a bug in all AOSP-based custom Pie roms for deb and flo.
- You tell us!
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
- Every open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for deb and flo.
Sources
- deb device tree
- flo device tree
- kernel
- blobs
XDA:DevDB Information
LineageOS 16.0, ROM for the Nexus 7 (2013)
Contributors
ripee, followmsi, pitrus-, flex1911, Clamor
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: System partition large enough to accommodate the rom and GApps.
Version Information
Status: Stable
Current Stable Version: 9
Stable Release Date: 2019-08-11
Created 2019-02-22
Last Updated 2019-11-10

Reserved

Reserved

Awesome! Keep up the great work and thank you for keeping this devices development alive

JT1510365 said:
Awesome! Keep up the great work and thank you for keeping this devices development alive
Click to expand...
Click to collapse
All credit to followmsi and flex1911

oh yeah maga
make android great again

Is this the same ROM you can find in followmsi androidfilehost directory?
https://androidfilehost.com/?w=files&flid=289297
Yesterday I try the Ressurection Remix 7.0
Everything works fine.
But in Kodi i cannot use the h264 hardware decoder.
Have this Rom the same issue?

DaCl88 said:
Is this the same ROM you can find in followmsi androidfilehost directory?
https://androidfilehost.com/?w=files&flid=289297
Yesterday I try the Ressurection Remix 7.0
Everything works fine.
But in Kodi i cannot use the h264 hardware decoder.
Have this Rom the same issue?
Click to expand...
Click to collapse
Since the sources I linked are followmsi's, yes this is the same rom, but built more recently to take advantage of the lineage commits added since followmsi's last build. Because of this, it will have the same h.264 bug in Kodi.

Rom is working very well but I cannot flash Gapps. I chosen Pico 9.0 arm. Which one should I use ? Thank you !

gaja22 said:
Rom is working very well but I cannot flash Gapps. I chosen Pico 9.0 arm. Which one should I use ? Thank you !
Click to expand...
Click to collapse
Did you re-partition the memory, as described in the FAQ's in the OP?

ripee said:
All credit to followmsi and flex1911
Click to expand...
Click to collapse
Of course

To a person who has installed this ROM, I have one question. If the orientation is locked to Landscape, when you turn on the screen, does the screen start from landscape mode, or does it start from portrait mode and quickly rotates to landscape mode?
It does not happen on the official LOS 14.1, but it did happen with unofficial LOS 15.1. This rotation is problematic, because it often causes a significant delay when I turn on the screen, depending on the app I had been using.

Thx!
Will test this ROM!

yourrealking said:
To a person who has installed this ROM, I have one question. If the orientation is locked to Landscape, when you turn on the screen, does the screen start from landscape mode, or does it start from portrait mode and quickly rotates to landscape mode?
It does not happen on the official LOS 14.1, but it did happen with unofficial LOS 15.1. This rotation is problematic, because it often causes a significant delay when I turn on the screen, depending on the app I had been using.
Click to expand...
Click to collapse
Hello, my lock screen will be temporarily displayed in portrait then rotates to landscape.

Quick question. A full data wipe? As in a full data partition wipe including rom backups, pictures, videos, personal files? Cant say I have ever hear of a rom requesting this and I have been flashing roms for a decade. Perhaps I am missing something. Is this only the first time I flash and then a dirty flash for daily builds?

hlxanthus said:
Quick question. A full data wipe? As in a full data partition wipe including rom backups, pictures, videos, personal files? Cant say I have ever hear of a rom requesting this and I have been flashing roms for a decade. Perhaps I am missing something. Is this only the first time I flash and then a dirty flash for daily builds?
Click to expand...
Click to collapse
A full data wipe cleans the data partition on which user apps and system settings reside. Your personal files are on the internal storage partition, which does NOT get wiped by TWRP when factory wiping.
Yes, clean flash prior to the first flash, then dirty flash subsequent builds.

ripee said:
A full data wipe cleans the data partition on which user apps and system settings reside. Your personal files are on the internal storage partition, which does NOT get wiped by TWRP when factory wiping.
Yes, clean flash prior to the first flash, then dirty flash subsequent builds.
Click to expand...
Click to collapse
Read the OP's instructions again. It clearly says to wipe data and internal storage.

Hi and thanks for (the) pie. It works great for the main user but i have a strange problem with a secondary (or guest) user:
Whenever i switch to the secondary user the navigation bar (three buttons) disappears. The bar is not just hidden but seems to be really gone/killed. When switching back to the main user the bar is still missing and i need to restart to get it back. Any ideas?

The pie ROM works great on my Nexus. Thank you so much. It's amazing. I hope you plan to add the security patches every month. Thx.

hlxanthus said:
Read the OP's instructions again. It clearly says to wipe data and internal storage.
Click to expand...
Click to collapse
Yes, I have read the OP. Wiping both data and internal storage is for the sake of less experienced users who should be starting fresh no matter what rom they're coming from. As you have more experience, please use your judgment to wipe whatever you know needs to be wiped.

[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 !!

[ROM][DISCONTINUED][10] LineageOS 17.1 [deb][flo]

{
"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, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
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-17.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.3. Simply flash the linked below version 3.3 or higher, reboot back into recovery, and flash the rom zip again.
Q: I am seeing Error 7 when trying to flash a GApps package.
A: This is due to the system partition being too small to fit both the rom and the GApps package. You need to re-partition it with a tool such as the one created by Clamor (linked below). You will only need to do this once.
Q: When will any of the variants receive official builds from LineageOS?
A: There are no plans to submit these builds for official LineageOS support, but it should not matter. What is most important is that these unofficial builds be stable enough for daily usage, which they are, thanks to followmsi's tireless work in porting Android 10 to these venerable old tablets.
Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.
Q: Even if neither dev nor flo will ever receive official LineageOS support, just out of curiosity, what are some of the differences be between unofficial and official builds?
A: The following technical changes are in effect:
- Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
- Tablet status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
- The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
Q: How often will new builds be released?
A: About once a week for both deb and flo, as soon as possible after each new Android security patch level is merged, and of course whenever a new feature is added or a bug is fixed, as per followmsi's advice.
[REPARTITION] Nexus 7 (2013) Repartition [FLO/DEB] [16GB/32GB] [UA TWRP]
ROMs
pitrus-
- LTE: deb
- Wi-Fi: flo
Magisk
Open GApps
How to flash LineageOS and Open GApps1. Move any files you want to keep to your computer or flash drive via a USB OTG cable – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Boot into Recovery Mode (Hold volume up and Power button until you see TWRP's splash screen),
4. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
5. Swipe to Wipe at Bottom of Screen,
6. Back to Main start screen,
7. Wipe > Format Data,
8. Type 'Yes' and press blue checkmark at the bottom-right corner,
9. Go Back to Main Start Screen,
10. Move your LineageOS Rom and GApps Package to the internal storage,
11. Install > select a zip file to flash (optionally, Add More Zips > select another zip file to flash),
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
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 us!
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
- Every open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for deb and flo.
Sources
- deb device tree
- flo device tree
- kernel
- blobs
XDA:DevDB Information
LineageOS 17.1, ROM for the Nexus 7 (2013)
Contributors
ripee, followmsi, pitrus-, flex1911, Clamor
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: System partition large enough to accommodate the rom and GApps.
Version Information
Status: Stable
Current Stable Version: 10
Stable Release Date: 2020-01-21
Created 2020-01-21
Last Updated 2020-04-14

I was just curious about GApps for this ROM. Going to the link you provided and just simply going to opengapps.org/ does not show a gapps version for Android 10. Is it ok to use one for Android 9?
EDIT: I was searching around for a GApps package for Android 10 and found this.... https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/
I installed your ROM with the GApps above and it is working great so far. Thank you for the work you put in making this for all of Nexus 7 owners!

Is LineageOS seperated from AospExtended in the other thread?
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
Viking8 said:
I was just curious about GApps for this ROM. Going to the link you provided and just simply going to opengapps.org/ does not show a gapps version for Android 10. Is it ok to use one for Android 9?
EDIT: I was searching around for a GApps package for Android 10 and found this.... https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/
I installed your ROM with the GApps above and it is working great so far. Thank you for the work you put in making this for all of Nexus 7 owners!
Click to expand...
Click to collapse
Use the latest beta, some bugs were fixed.
https://sourceforge.net/projects/opengapps/files/arm/beta/20200116/

edison0354 said:
Is LineageOS seperated from AospExtended in the other thread?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=81555475&postcount=2938
Lineage-17.1
Like mentioned before .. I did plan to handover Lineage-17.1 beginning of 2020.
That's done now.
@ripee will continue to build regular lineage-17.1 builds for flo/deb.
If there are some code changes in the next time .. we test on AEX first and apply changes to Lineage sources later on.
Thanks to @ripee for taking over !
Cheers

Nice job

I would like to use microG with this ROM. Any chance to include signature spoofing into the ROM? Or do you know of any other method to use microG with this ROM?

Changelog
Build 0122 for both variants
* NFC is fixed, courtesy of followmsi.
* Synced with LineageOS sources.

Thanks ripee for the quick update!
But for flo, I still see the 21 version?!?

rho-bot said:
Thanks ripee for the quick update!
But for flo, I still see the 21 version?!?
Click to expand...
Click to collapse
I post changelogs while the builds are still cooking or uploading, in case I forget to do so later.
flo 0122 is up right now.

Happy to see Q ROM for this wonderful but old N7. I'm on 8.1 Validus and want to try your build. Do i need to wipe internal storage and why ?

Vincent_40 said:
Happy to see Q ROM for this wonderful but old N7. I'm on 8.1 Validus and want to try your build. Do i need to wipe internal storage and why ?
Click to expand...
Click to collapse
I am also curious. My USB port is not functional so I need to always keep one or two OS zip files on internal storage.

1st post tell us that we need a repartition to have enough space to install gapps. During this step /data partition is erased.
---------- Post added at 11:24 PM ---------- Previous post was at 11:00 PM ----------
WackyDoo said:
I am also curious. My USB port is not functional so I need to always keep one or two OS zip files on internal storage.
Click to expand...
Click to collapse
It's time to try to fix that USB port !
I've done it twice. The first time I tightened the ground contour with a small pair of pliers. The 2nd time I managed to redo the soldering with a sharp soldering iron.

Vincent_40 said:
Happy to see Q ROM for this wonderful but old N7. I'm on 8.1 Validus and want to try your build. Do i need to wipe internal storage and why ?
Click to expand...
Click to collapse
No, only wipe system, cache, dalvik, and data.

ripee said:
Changelog
Build 0122 for both variants
* NFC is fixed, courtesy of followmsi.
* Synced with LineageOS sources.
Click to expand...
Click to collapse
Cool downloading now does substratum work with this ROM though?

having a lot of trouble installing. I am not sure if it is user error. crying
when can we have ota?

Flo clean flash from 01/09 version w/beta gapps pico 01/16 & latest magisk.
No issues, nice easy upgrade. Looking forward to dirty flashing going forward.
Many thanks to both maintainers! Appreciate the option of latest roms on our devices.

I haven't tested yet with LOS17.1, but new Open GApps are working with Setup Wizard on Havoc. I'm using Pico.
https://www.xda-developers.com/open-gapps-android-10-roms/
Edit: Tried it on LOS17.1 and it's working great!

Thanks for this ROM.
Works fine on that old device ?.
Do you think it's possible to implement smart charging feature ?

Another happy user here, i even mamaged to load credits to my public transport card via NFC.

dealpapa1 said:
having a lot of trouble installing. I am not sure if it is user error. crying
when can we have ota?
Click to expand...
Click to collapse
I'm sorry to hear that. Which part of the installation process are you stuck on?

Database Info

welcome