ROM dedicated for All Quark (Moto MAXX/Turbo and Droid Turbo - XT1225, XT1250 and XT1254)
This ROM is the LineageOS from https://lineageos.org/ with specific changes to improve the experience for Quark that is why the ROM has the MOD type, all modification are in the changelog
Download:
ROM:
Sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Gapps:
Open GApps :
Open Gapps Click Here
Choose Platform: ARM, Android: 10.0, and a Variant the one that have all you need, I recommend the nano pack but it may not have all you need so check before download.
TWRP For Quark:
TWRP Use laste Mod version that I release Click Here
Installation:
Make sure you are running latest MOD TWRP from xda TWRP thread
Download the latest ROM and GApps**.
Reboot to recovery (recommended make a backup)
Coming from different ROM? Then Always wipe Data (without media aka without internal memory)
Wipe System*
Flash the latest build and GApps **
Reboot and enjoy!
* Wipe of Dalvik Cache and Cache not demanding but may help with some random minor bug that show after a update
** Gapps not demanding the ROM works perfect without it but if you plan to use gapps you need to flash it on a clean install with the ROM, In a ROM updates a "dirty flash" if you already have gapps always flash gapps again with the ROM update
Changelogs:
LineageOS - 17.1 source and Quark Changelog (Click Here)
What's working :
Everything minus VoLTE support for XT1254 (1225 doesn't have this featuring).
Known Android 10 issues :
Not PRE-ROOTED, ROOT solution is available read this thread second post
Old issue maybe resolved on latest TWPR update but... TWRP may not be able to backup or decrypt data encrypted on Oreo or Up: no know workaround, one day TWRP will support it.
Can't swipe/draw the pattern in lock screen : Screen lock pattern is set with the extra option of patterns "Directly show pattern view" and ambient display enable all at the same time, will bug ambient display for the wave or pick featuring of gestures, this doesn't bug when you received a notification, disable one or the other until the bug is fixed.
General bug help/fix in second post or some were in the thread, use XDA building "Search Thread" option to find general help for this thread project...
Source:
LineageOS Source
Device Tree
Kernel tree
Vendor tree
Mod Kernel Adiutor tree
XDA:DevDB Information
[ROM][All Quark][10.x]LineageOS ROM for Quark
Contributors
Felipe Leon (fgl27) is the main contributor (as I'm the one making it).
But the XDA community the quark user base plus the open source community from XDA, github and the LineageOS team is what make this project so good, thank you all :good:.
ROM OS Version: 10.x
ROM Kernel: Linux 3.10.x
Based On: LineageOS 17.x
Version Information
Status: Stable
Created 2020-24-01
Last Updated Check Changelog click here
Below are some of the helps and or workarounds for the most occurring issues.
ROOT Use Magiks
GPS / Radio:
Changing/Updating the ROM may cause GPS lock problem, there is two separated help
option 1) Install "GPS Status & Toolbox" , open the app, slide the left option and open "Manage A-GPS state" click in Reset, after repete the process and now click in Download, close the app after receive the OK, wait a few seconds and try a gps lock using the same app, if that doesn't help try again after a reboot, if that doesn't help go to option 2 below
option 2) If the above doesn't help you can try to erase all the radio status
Erase the radio status also applies to the case you have No SIM Card or no Cell Signal level in status bar.
To erase the radio status is very simple just flash this zip "Clean_modem_status.zip" via TWRP no wipe is need, is also recommended to try option 1 after this if you flashed because of a GPS problem.
If after flashing the cleaner you find any problem related to lost of signal, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version via fastboot (aka "via bootloader")
Code:
mfastboot flash radio radio.img
find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)
Random Power off or reboots?
To identify if the device random reboot or simply power it self off there is two ways.
1) If after the device goes black you can't power it up again without plunging the charger, then is because the battery is dead, even if yours battery had good % left before it shutdown yours battery is probably damage doesn't matter if the device/battery is new a battery can go bad simply by charging the device wrong, a wrong way to do it is let the device constantly go bellow 20% as low you let it get worse yours battery will be with time.
2) Check the boot reason prop "ro.boot.bootreason" :
Using the app BHB27 Kernel Audiutor > logs section > search in a log > mark getprop > search keyword "reason".
If the result is power_key_press the device didn't reboot it power off.
Code:
[ro.boot.bootreason]: [power_key_press]
On this case, is recommended to set the battery "Automatic power saver" from default 15% to a higher value then the one yours device is power it self off.
-----------------------------
If the result is reboot the device reboot it self
Code:
[ro.boot.bootreason]: [reboot]
On this case, is recommended to just share a log, do as is recommended on next post.
Bootloop to TWRP after a Factory Reset (Settings/System/Reset option/Factory reset):
This is a Nougat and up problem, it only happens if you are using a TWRP from the official site (with is not update to properly support Nougat and Up Android versions) or a old version of TWRP, to fix it just flash latest MOD TWRP version from the TWRP xda.
TWRP xda thread Click Here
Pictures access, view, sharing or related:
One thing that I notice regarding permission is if you have a app that access a folder that was created in older OS this app may be able to access this folder but not fully access the files like the below example.
You take a picture or a screenshot and can't see or share it with some apps, the simple fix is just erased/delete the folder with that problem for example the DCIM (camera folder) and or Pictures (Screenshot) folder under Main storage (or any folder were you face a picture or file access related problem), of course you can backup the files to another folders first using a file explorer that can see the files (maybe necessary one with ROOT access), then let the OS service recreate the folder, it will automatic recreates after you take a new picture or screenshot (or manually make the new folder if is a custom folder mane by you), test to see if the problematic app can see after.
USB OTG player:
On latest android version Nougat and above, to play anything from a USB OTG device is needed proper permission, that is not simple to give as the app must request it to be given, so to play anything from a USB driver find a app like this one
VVM XT1254 only
VVM app (VVM may only be accessible via play with the link, click here and chose open with play), VVM may not work correctly google has it on version is free and seems to work 100% Google voice, the in the phone app of b this ROM also has a dedicated option for voice calls
Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand or reproduced I can't fix.
Always post a bug with @fgl27 and a log .zip generated by the app
BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP (ROOT is needed for this)...
Even after a random reboot share a log
If is a Reboot/Power off related bug make the log as soon the device finishes boot up
duplicated
Really nice! Getting a battery replacement for my Droid so that it can work as a backup phone. Tysm for Android 10!
Won't stay on long enough to do hardly anything. Reboots into recovery on its own, thankfully. What am I missing?
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Won't stay on long enough to do hardly anything. Reboots into recovery on its own, thankfully. What am I missing?
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
Inform what you are doing
The ROM is much much smoother than pie ROMs...Thank you so much bro ......Android 10 on this 6 year old handset is just unbelievable....
fgl27 said:
Inform what you are doing
Click to expand...
Click to collapse
Full wipe, except internal storage, Flashing rom, gapps, onto xt1254, in twrp 3.2.3mod4, reboot. About a minute into setup, phone powers down & reboots into recovdry
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Full wipe, except internal storage, Flashing rom, gapps, onto xt1254, in twrp 3.2.3mod4, reboot. About a minute into setup, phone powers down & reboots into recovdry
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
And just the ROM? What happens
fgl27 said:
And just the ROM? What happens
Click to expand...
Click to collapse
Same thing. This ain't my first rodeo, and I'm stumped!
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Same thing. This ain't my first rodeo, and I'm stumped!
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
The odd thing is what is doing the call to recovery? it doesn't just go to recovery because of a fail to boot something is calling it.
Maybe a problem on data partition don't know but is a odd behavior.
Try to log that, adb is enable but you must give permission connect the usb cable during boot try to connect "adb shell" will refuse as is missing permission, as soon as the device finishes boot do again "adb shell" give the permission, next boot after the bootanimation start, you will be able to "adb shell" but before enable ROOT for adb "adb root" then after connect "adb shell" open two windows one do a "logcat" another "dmesg -w"
share the log information.
Thanks / Flashlight issue
Thank you for your invaluable contributions. Keep up the good work!
So far, the ROM has been working fine except for two bugs: the flashlight function is not working (I took a photo with flash so the leds on the device are OK), and the home/launcher app (Trebuchet) keeps crashing.
Kind regards!
fgl27 said:
The odd thing is what is doing the call to recovery? it doesn't just go to recovery because of a fail to boot something is calling it.
Maybe a problem on data partition don't know but is a odd behavior.
Try to log that, adb is enable but you must give permission connect the usb cable during boot try to connect "adb shell" will refuse as is missing permission, as soon as the device finishes boot do again "adb shell" give the permission, next boot after the bootanimation start, you will be able to "adb shell" but before enable ROOT for adb "adb root" then after connect "adb shell" open two windows one do a "logcat" another "dmesg -w"
share the log information.
Click to expand...
Click to collapse
Yoiks! Not quite that tech savy. Even tried after a full wipe & zip-by-zip install. If I have to be happy with RR Pie, so be it. Not all that bad. My Turbo has some miles on it, rebuilt twice already. Got one last battery & display in the wings. Best, last phone Motorola made. Don't waste your time, further, on what's likely a hardware flaw.
Sent from my LM-V405 using Tapatalk
I think your not using latest twrp
newbe1droidx said:
I think your not using latest twrp
Click to expand...
Click to collapse
Looks like I wasn't. I thought 3.2.3mod4 was the last best available.
Update: Um, yeah, still no luck. Used 331m1. My Turbo has a weird glitch, apparently. [emoji34]
Sent from my LM-V405 using Tapatalk
Kinzhal said:
Thank you for your invaluable contributions. Keep up the good work!
So far, the ROM has been working fine except for two bugs: the flashlight function is not working (I took a photo with flash so the leds on the device are OK), and the home/launcher app (Trebuchet) keeps crashing.
Kind regards!
Click to expand...
Click to collapse
Trebuchet doesn't crash for me try to share a log.
On next build flashlight is OK
Einsteindks said:
Looks like I wasn't. I thought 3.2.3mod4 was the last best available.
Update: Um, yeah, still no luck. Used 331m1. My Turbo has a weird glitch, apparently. [emoji34]
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
twrp doesn't affect this I tested And 10 on it before making 331 was all fine...
does the custom kernel I share works for you on Pie?
fgl27 said:
Trebuchet doesn't crash for me try to share a log.
On next build flashlight is OK
twrp doesn't affect this I tested And 10 on it before making 331 was all fine...
does the custom kernel I share works for you on Pie?
Click to expand...
Click to collapse
Overall answer; I don't know. I've stopped trying for now. It doesn't stay on long enough to access the logs. There's a pop up saying a certain file has stopped working. I'll look into that this weekend and post that information. I can only think that it's something to do with my phone's Hardware, one small minor flaw is screwing the whole thing up.
Update: well, I had a little time to kill. I reinstalled just the ROM only. 'com.android.phone keeps stopping' Would not having a SIM card installed be related to this error?
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Overall answer; I don't know. I've stopped trying for now. It doesn't stay on long enough to access the logs. There's a pop up saying a certain file has stopped working. I'll look into that this weekend and post that information. I can only think that it's something to do with my phone's Hardware, one small minor flaw is screwing the whole thing up.
Update: well, I had a little time to kill. I reinstalled just the ROM only. 'com.android.phone keeps stopping' Would not having a SIM card installed be related to this error?
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
noting crashing to me, sim or no sim.
I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 17.1 source and Quark Changelog (Click Here)
Related
This is a CyanogenMod 12.1 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y). Support for G800M is untested so far.
DO NOT USE IT FOR G800H OR YOU WILL BRICK YOUR DEVICE
Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
Hence please do not ask for support or ROMs for the G800H.
Working features
Receiving and making calls
Hardware sensors (Light, Orientation, Compass, Proximity, Acceleration)
Audio
Bluetooth (audio in HFP seems to be distorted with at least some headset devices)
Wifi
HW accelerated GUI
USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
Camera (pictures+video: Back+Front)
MTP storage
IR
GPS
NFC
Non-working features:
Fingerprint scanner (no app for tests found)
Pulse sensor + Step counter (no app for tests found)
Hall sensor
SELinux
Known issues:
See the Bug Report section of this thread
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 2.8.7.0 recovery image [08/07/2015] (AndroidFileHost Mirror)
CM 12.1 ROM for G800F/M/Y (AndroidFileHost Mirror)
Google Apps (contains Google Play, ...) for Android 5.1.1 from Jajb (Recommended) or the one that suits you best from Consolidated GApps.
Install recovery:
Reboot your device into Odin mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select PDA and select the recovery image (recovery.tar.md5)
Check that only "Auto Reboot" and "F. Reset Time" is set
Click on "Start": the kernel image should be flashed now and the device should reboot afterwards. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device. If not restart into Download mode and flash again or flash the stock rom.
Before you flash:
You need the latest TWRP recovery (see above). Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 12.1.
Flash CyanogenMod:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and CyanogenMod zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM 12.1 ROM zip-package
Install the GApps zip-package
Reboot the system and enjoy a Lollipop
How to root:
No SuperSu is needed as CyanogenMod already comes with integrated root support. Root access is disabled by default.
You normally do not need root access. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest ROM for the G800F you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM12 is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
15/08/2015:
* Synchronize with newest CM 12.1 sources (contains stagefright patches)
08/07/2015:
* Update to latest CM-12.1 sources (LMY48G)
* Camera app supports saving pictures to external SD-cards
* Partition sizes of system and data slightly reduced to avoid "unable to mount /system" failure during installation on some variants of the G800 (e.g. G800Y)
19/05/2015:
* Update to CyanogenMod 12.1 (Android 5.1.1)
* Merged Kernel-sources from G800FXXU1ANL1
* Re-enabled NFC
* TWRP update
11/04/2015:
* Update to CyanogenMod 12.1 (Android 5.1)
* Update to TWRP 2.8.6.0
* Fixed blinking capacitive touchkey lights
* Fixed unresponsive touchscreen on wake-up
* Added support for Automatic Brightness control
* Added advanced touchscreen settings (Glove and Hovering mode)
* Use open-source Light-HAL, Power-HAL and IR-HAL implementations
* Updated Power-Profiling
23/03/2015:
* Fixed non-working mic on incoming call issue
* Fixed non-working menu-button
* Synchronized with latest CyanogenMod sources
This section is for developers:
A README file with build instructions can be found here:
Code:
https://github.com/cm-3470/patcher_kminilte
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
https://github.com/cm-3470/android_vendor_samsung_kminilte
https://github.com/cm-3470/android_kernel_samsung_kminilte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Developers welcome
At the moment the G800F/M/Y specific port of this ROM is only done by one person (hennymcc). Although Unjustified Dev also works on this ROM he does not own an Galaxy S5 Mini but a Galaxy Light which has a similar base but is different when it comes to camera, nfc and other components (maybe even slightly when it comes to audio and radio).
Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.
Thanks to Unjustified Dev from Team Regular. As the S5 mini (G800F/M/Y) and the Galaxy Light are quite similar we worked on this together.
XDA:DevDB Information
[G800F/M/Y][ROM][5.1.1][LMY48G] CyanogenMod 12.1 for G800F/M/Y [Alpha 15/08/2015], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, Unjustified Dev
Source Code: https://github.com/cm-3470
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version from 15/08/2015]
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-04-15
Last Updated 2015-09-22
FAQ:
Question:
I'm trying to flash this rom but it says to me: "This package is for kmniltexx, kminiltedv, kminilteub; this device is kminilte. E:Error executing updater binary zip ...."
Answer:
The device names were changed with the newest CM12 build to be able to distinguish between G800F (kmniltexx), G800Y (kminiltedv) and G800M (kminilteub) as all of them are kminilte devices. The new builds of TWRP and CM12 detect the correct device at runtime.
Older TWRP releases (for example that of RVR in another XDA thread) still detect the device as kminilte (instead of kmniltexx,...) and hence are not able to install the new CM 12 releases so please do not install RVR's TWRP if you want to install CM 12. Always use the TWRP image linked in the first post of this thread.
Reserved
As none of the pre-alpha testers reported any issues with NFC, I assume that the broken NFC of LS97 and me was caused by electrostatic discharge while removing and re-inserting the battery (at least I did this hundreds of times). In addition we already broke our NFC some weeks ago after having used 5.0.2 for some while, so this ROM should be at least as safe as 5.0.2 and there is no direct link between the custom ROM and the broken NFC.
Just as a precaution: to avoid damage of the NFC-chip (which is connected to the antenna in the battery) by electrostatic discharge, use the power button to reboot the smartphone instead of removing the battery.
What a nice first post for this new ROM
Are the links above the same like the ones you posted into the comments in your 5.0.2 thread? Just so i know if something has changed in thos links obove.
CTXz said:
Are the links above the same like the ones you posted into the comments in your 5.0.2 thread? Just so i know if something has changed in thos links obove.
Click to expand...
Click to collapse
Exactly the same.
hennymcc said:
Exactly the same.
Click to expand...
Click to collapse
Ok thanks. Also have you figured out whats up with the screen turning on after locking delay since turning off nfc didn't result changes. Also it doesn't happen always. Only sometimes
CTXz said:
Ok thanks. Also have you figured out whats up with the screen turning on after locking delay since turning off nfc didn't result changes. Also it doesn't happen always. Only sometimes
Click to expand...
Click to collapse
I haven't looked any deeper into this so far.
So how is the Final version going to look like if this is Alpha... Damn [emoji41]
I have a small problem, everytime i touch the screen my capacitive buttons light up. I already tried disabling this in the settings but it doesn't let me do that.
Anyone have soms advice ?
Nielsieboy said:
I have a small problem, everytime i touch the screen my capacitive buttons light up. I already tried disabling this in the settings but it doesn't let me do that.
Anyone have soms advice ?
Click to expand...
Click to collapse
Hey. What i did is just rather turn them off completely.
Settings > Buttons > Backlight > Uncheck Illuminate buttons
Else there is no fix, due cm12.1 universality it doesn't work with the buttons like the stock ROM did.
CTXz said:
Hey. What i did is just rather turn them off completely.
Settings > Buttons > Backlight > Uncheck Illuminate buttons
Else there is no fix, due cm12.1 universality it doesn't work with the buttons like the stock ROM did.
Click to expand...
Click to collapse
Well tried that but The setting just changes back to the default.
Nielsieboy said:
Well tried that but The setting just changes back to the default.
Click to expand...
Click to collapse
Ok thats wierd. Have you wiped all partitions you needed to like said above ( dalvik cache, cache, system, data )
If it gets verry anoying you might give a reflash a try. Also i know this sounds funny but did you atleast try rebooting the device?
---------- Post added at 08:55 PM ---------- Previous post was at 08:50 PM ----------
Also did you give this a shot https://play.google.com/store/apps/details?id=com.deskangel.kblight
There are many more apps on gplay for button backlight. Just search it
i've flashed it yesterday over the old buidl (without full wipe). so i got FC's on several google apps.
after flashing several different gapps for lolipop 5.1 the errors with the FCs are still stere.
then i've made a full clean install with full wipe and installed the pa gapps from the 04-10-2015 and now everything works fine & smooth.
tommorrow ill gonna test the bluetooth cause on the old build there were sond errors....
but for now it looks very good
I've discovered something. If you enable LiveDisplay the device will lag a bit.
And when you think I did a full wipe and reflashed the ROM, just to find out that my problem was related to this little feature...
@henny: can you confirm that this mod will work on your build ?
It sounds very good
Nielsieboy said:
I have a small problem, everytime i touch the screen my capacitive buttons light up. I already tried disabling this in the settings but it doesn't let me do that.
Anyone have soms advice ?
Click to expand...
Click to collapse
it doesnt let you do that? why not? for me it worked...(i hate those lights too)
DerMoeJoe said:
@henny: can you confirm that this mod will work on your build ?
It sounds very good
Click to expand...
Click to collapse
I personally don't see a lot of advantages in it and would not recommend it, especially for this phone, regardless of whether or not it's compatible.
LS97 said:
I personally don't see a lot of advantages in it and would not recommend it, especially for this phone, regardless of whether or not it's compatible.
Click to expand...
Click to collapse
Why not. I use it for daily use and i have to say i have less bugs than my stock rom had.
With that it boosted my phone like hell and there is no more lagg when oppening apps, going to the homescreen, scrolling through apps and no more touchwiz. Plus you got the newest android up to date. That fixed some app issues with my phone ( i no longer got the app not compatible error after lolipop. Oh yeah and no more bubble sounds when pressing on something Thaankk you! There are many other things that i preffer over the stock rom. So i see so much potential in this ROM and would preffer it as much as i can if you got a s5 mini g800f.
CTXz said:
Why not. I use it for daily use and i have to say i have less bugs than my stock rom had.
With that it boosted my phone like hell and there is no more lagg when oppening apps, going to the homescreen, scrolling through apps and no more touchwiz. Plus you got the newest android up to date. That fixed some app issues with my phone ( i no longer got the app not compatible error after lolipop. Oh yeah and no more bubble sounds when pressing on something Thaankk you! There are many other things that i preffer over the stock rom. So i see so much potential in this ROM and would preffer it as much as i can if you got a s5 mini g800f.
Click to expand...
Click to collapse
The only way to find out if it works is to try it. So if you want this feature you can flash that mod and report if it works .
I personally do not need it as I want the phone to turn off when I "power it off".
Note that the mod could cause stability issues. So before reporting bugs here you should reinstall CM 12.1 first with a full wipe and check if the problem is still present.
Edit:
this was supposed to be an answer to DerMoeJoe's question about the QuickBoot mod
This is a LineageOS 14.1 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y).
DO NOT USE IT FOR G800H OR YOU WILL BRICK YOUR DEVICE
Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
Hence please do not ask for support or ROMs for the G800H.
Important note: It is possible that flashing this ROM can cause efs partition issues. Therefore it is strongly recommended to make a backup of your efs partition before flashing this ROM. This can be done via TWRP.
Working features
HW accelerated GUI
Camera (pictures+video: Back+Front) (switching between camera and video-recording might crash the camera-app)
MTP storage
Flash Light
Bluetooth (A2DP, HFP, HID)
IR
Sound
SMS
Initiate and receive calls
Wifi
Mobile Data
USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
NFC
Hardware sensors (Orientation, Compass, Proximity, Acceleration, Hall sensor, Step counter)
Light sensor (needed for auto-brightness)
Pulse sensor (preliminary and very inaccurate. Works with Apps like Kardiograph)
SD-Card as internal storage (new Android M feature)
GPS
Fingerprint scanner
SELinux
Non-working features:
Known issues:
Camera crashes when switching from camera to video. Use Google camera or Open camera to solve camera issues.
See the Bug Report section of this thread.
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 3.0.0 recovery image [25/03/2016] (AndroidFileHost Mirror)
LineageOS 14.1 ROM for G800F/M/Y
Latest build by hennymcc: Android File Host
There might be a more up-to-date (OTA enabled) build by ayke: https://aykevl.nl/android
There are monthly builds and recent bootloaders and modems by Panzerknakker: https://androidfilehost.com/?w=files&flid=201249
Google Apps (contains Google Play, ...) for Android 7.1. The following is recommended:
Open GApps Project, Platform:ARM, Android:7.1, Variant: whatever you prefer (e.g. "mini" or "nano")
Install recovery:
Reboot your device into Download mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select "PDA" (in newer versions: "AP") and select the recovery image (recovery.tar.md5)
Check that only "F. Reset Time" is set. "Auto Reboot" should be disabled to avoid a reboot into stock ROM.
Click on "Start": the recovery image should be flashed now. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device, wait a few seconds and reboot into recovery mode (see instructions below).
Important: make sure not to boot into stock ROM, otherwise the stock ROM might remove the custom recovery again. If this happens, flash the recovery image again.
Before you flash:
You need the latest TWRP recovery (see above). Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 14.1.
Flash ROM:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and the ROM zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM ROM zip-package
Install the GApps zip-package
How to root:
LineageOS does not have root support integrated by default. You have to download addonsu-arm-signed.zip for 14.1 from the Lineageos Extras download page and install it with TWRP.
After that root access is still disabled by default. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest ROM for the G800F you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
Changelog:
19/08/2017:
* SELinux policy update
* Update to newest LineageOS sources
02/06/2017:
* Firefox crash&reboot fixed (thanks to Spookcity)
* Enabling the fingerprint reader does not cause bootloops anymore (thanks to Spookcity)
* Ambient display option added (disabled by default)
28/05/2017:
* [COLOR="red"]Note: ROM is stuck in bootloop when fingerprint reader is enabled. ROM removed.[/COLOR]
* Enabled selinux (thanks to mirhciulica for fixing all those selinux denials). If you encounter problems check for "avc: denied" messages in logcat (see: https://source.android.com/security/selinux/validate)
* Fixed Snapchat and SafetyNet problems (Snapchat reported server errors, Safetynet Helper reported a 1970 timestamp): Kernel patch was necessary.
* Updated kernel to 3.4.107
* Applied most of the patches from [URL="https://android.googlesource.com/kernel/common/+/deprecated/android-3.4"]kernel/common/deprecated/android-3.4[/URL]
* Updated LineageOS sources
* FlipFlap added to support smart flip covers: shows a screen with the current time in the window of the smart cover. Note that this relies on the magnetic sensor at the bottom of the phone. So magnets near the sensor can trigger this behavior too.
* Replaced the buggy Gello webbrowser with Jelly - the new LineageOS default browser
* Replaced the buggy Snap camera with the LineageOS default camera app
* Replaced the Samsung battery charger app (lpm) with healthd (looks uglier but at least works with selinux)
20/02/2017:
* Fixed Youtube scaling issue on window resizing
* Compass fixed (thanks to mirhciulica for figuring out what's wrong)
* cpufreq config added
* Charge mode fixed (starts when plugging USB into a powered-off phone)
* USB-Tethering and Wifi SoftAP (Hotspot) fixed
* Camera doesn't crash when switching between camera and video (but might still crash sometimes)
* Fingerprint libs reverted from MM to LP (maybe that fixes the fingerprint issues - please test)
01/02/2017:
* conversion to LineageOS
* updated some libs with stock MM versions
* fixed robotic voice problem
* fixed silence on first call
07/11/2016:
* Initial test build
This section is for developers:
A README file with build instructions can be found here:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
https://github.com/cm-3470/android_vendor_samsung_kminilte
https://github.com/cm-3470/android_kernel_samsung_kminilte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Developers welcome
At the moment the G800F/M/Y specific port of this ROM is only done by two persons (CTXz and hennymcc). Although Unjustified Dev also works on this ROM he does not own an Galaxy S5 Mini but a Galaxy Light which has a similar base but is different when it comes to camera, nfc and other components (maybe even slightly when it comes to audio and radio).
Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.
Thanks to CTXz, Psyafter, spookcity138, ayke and mirhciulica for working on this ROM.
XDA:DevDB Information
[G800F/M/Y][ROM][7.1][NJH47F] LineageOS 14.1 for G800F/M/Y [Beta 19/08/2017], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, Panzerknakker, spookcity138, psyafter, ayke
Source Code: https://github.com/cm-3470
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version >= 15/08/2015]
Based On: LineageOS
Version Information
Status: Beta
Created 2017-02-01
Last Updated 2018-08-18
CostasGr said:
henny, what is ur baseband at the moment?
Click to expand...
Click to collapse
My baseband is G800FOJV1CPK1 at the moment.
Thx!!!
Fingerprint sometimes does not works: No response from the sensor. :crying:
hennymcc said:
My baseband is G800FOJV1CPK1 at the moment.
Click to expand...
Click to collapse
So Marroco Baseband is working in Germany?
Cool .... So ... Stock 6.0.1(Marroco Baseband) will also work in Germany, right?
?
Everything's working perfect right now besides the fingerprint sensor sometimes not getting any input and the "Cast" option for streaming on Smart TV's is broken as well ("Unfortunately, Settings stopped working", when connecting). YouTube still has this weird resizing problem on >=360p...
Thanks anyway for providing free software with regular updates!
EDIT: Are OTA-Updates active in this build or do we have to install them via TWRP-flash?
installing the root didnt work
edit: oh does seem to work, although TWRP says installation failed
edit2: although app says i have no root
wogooo said:
installing the root didnt work
Click to expand...
Click to collapse
Whats your error? What zip flashed? For me it worked at the first time
The problem with the videos is almost solved, it seems a bit slow and it is necessary to play the video, go to the menu and go back
---------- Post added at 09:01 PM ---------- Previous post was at 08:59 PM ----------
Mystixor said:
Everything's working perfect right now besides the fingerprint sensor sometimes not getting any input and the "Cast" option for streaming on Smart TV's is broken as well ("Unfortunately, Settings stopped working", when connecting). YouTube still has this weird resizing problem on >=360p...
Thanks anyway for providing free software with regular updates!
Click to expand...
Click to collapse
If you put the video to 720 and press the home button and you return, the bug disappears for a moment and you can see it normally, once time per video
PS: I use the google translator, I do not speak English
Mrdream94 said:
Whats your error? What zip flashed? For me it worked at the first time
Click to expand...
Click to collapse
You have to download addonsu-arm-signed.zip for 14.1 from the Lineageos Extras download page and install it with TWRP.
Error 7.
operation not supported on transport endpoint
set metadata: some changes failed
Try this zip. For me is working 100%
thanks for the work,great rom, everthing smooth, rooting worked with SR3-SuperSU-v2.79-SR3-20170114223742.zip (can't link it i am new )
only problem for me is the tethering. wifi tethering gives me an error, usb/bluetooth tethering is working but then there is no internet access with my laptop
@hennymcc I saw message here about wierd YouTube video resizing. In galaxy note 3 exynos development section there was same problem in Laos 14.1 ROM and op of that thread fixed it. His name is tincho5588.
Could you look into the Snapchat bug? When loging in it shows: Connection failed.
It only does that on CM14.1 and LineageOS14.
I Tried to log in on my tablet and backup/ restore the APP, didnt work.
Edit: tried everything availible on the Internet. Snapchat wont work
derhunt said:
thanks for the work,great rom, everthing smooth, rooting worked with SR3-SuperSU-v2.79-SR3-20170114223742.zip (can't link it i am new )
only problem for me is the tethering. wifi tethering gives me an error, usb/bluetooth tethering is working but then there is no internet access with my laptop
Click to expand...
Click to collapse
I'm loving my first taste of nougat - the rom is super smooth for me.
Unfortunately I also have a problem with the wifi hotspot. It starts to open the hotspot but a second later says 'error'.
Sent from my SM-G800Y using XDA-Developers Legacy app
Mrdream94 said:
Try this zip. For me is working 100%
Click to expand...
Click to collapse
worked! thx!!
information
anyone has noticed some problems with the battery life?
Ala1101 said:
anyone has noticed some problems with the battery life?
Click to expand...
Click to collapse
Yes, in my case it was the cell phone standby. I had it set to LTE. After switching to 3G battery live is much better because cell phone's energy consumption gets much much lower
Gesendet von meinem SM-G800F mit Tapatalk
No Root Access
There is no option for app root access, only for ADB
Ala1101 said:
anyone has noticed some problems with the battery life?
Click to expand...
Click to collapse
yesterday i've installed lineage, today I had huge battery-drain with 35% Media-Server, now I think it's better
Hey people,
I am glad to introduce my new Kernel to you guys,
Entangled Kernel​
Currently, I have not added any extra feature, except that you can use your phone as a USB keyboard and mouse on your PC,
for that you need to have an app that can work with it.(check out this Github Repo for more info: https://github.com/pelya/android-keyboard-gadget)
I have enabled F2FS on this kernel as well,
Currently, I need people to test out its battery backup and provide feedback about performance and bugs
Currently Known Bugs:
Random Reboots(fixed in V1.1)
You tell me if you find more!
Instruction are just as usual, if you need help, head to the "Post #3" of this Thread.
Update Logs are available in "Post #2" of this Thread.
Download Links are over at Android File Host!
Feature requests are welcome, you can post your feature requests here, or head over to github and open a new issue for bug report and/or feature requests.
XDA:DevDB Information
Entangled Kernel, Kernel for the LeEco Le 1S
Contributors
sscsps
Source Code: https://github.com/Le1s/android_kernel_leeco_x3
Kernel Special Features: Fully upstreamed with Google's updates
Version Information
Status: Alpha
Created 2018-01-07
Last Updated 2018-02-26
INSTALLATION INSTRUCTIONS:
Okay, I think it is understood that since this is not a stable build, there can be some hickups here and there. If you want to install it and help me with making it Stable, go ahead and try it out, test what you want and if you find any issue, grab Logs and give them to me.
NOTE: it is highly recommended that you create a backup of your boot partition before flashing this. You would need it to recover in case anything goes south.
If you have other plans, that's fine too, but I recommend to have a backup.
Steps to create a BACKUP:
1. Go to recovery
2. Select backup
3. Select the boot partition(or more if you want to, you know better).
4. Swipe to backup.
This will take a short while to back it all up, just wait and it'll be ready.
Once you have created the backup, you are ready to Install, follow these
Steps to Install the KERNEL:
1. Go to recovery, select "INSTALL",
2. Find the zip file,
3. Flash it.
4. Reboot to system.
FETCHING LOGS
After installing the kernel, if you think you have found any bug, please explain how it goes, grab a logcat, dmesg and/or last_kmsg
Grab LOGCAT by following these steps:
1. Connect the device to PC
2. Open adb and check if the device is detected(run "adb devices", it should list your device there)(if it is not detected, you'll need to get proper drivers).
3. Run this: adb shell logcat > logcat.txt
This will get the logcat in the file logcat.txt, located in the present working directory, you can change the name of that file if you want.
Provide this file.
grab DMESG by following these steps:
As soon as you think the bug occurs, follow these steps:
2. connect the device to PC.
3. open ADB and ensure that the device is connected.
4. Run this: adb shell su dmesg > dmesg.txt
This will get the dmesg in the file dmesg.txt, located in the present working directory, you can change the name if you want to.
Provide this file.
grab LAST_KMSG by following these steps:
Reboot to recovery as soon as you think the bug occur, or if the device auto reboots and follow these steps:
1. connect the device to PC.
2. open ADB and ensure that the device is connected.
3. Run this: adb shell cat /proc/last_kmsg > last_kmsg.txt
This will get the last_kmsg in the file last_kmsg.txt, located in the present working directory, you can change the name if you want to.
Provide this file.
If you have a way to reproduce the bug, reproduce the bug and take logs again.
All I need to fix the bug is the logs that will have to provide of that bug/crash.
After you are done taking logs, If you might feel like you want to remove my kernel(pls dont! :/ ), you might want to restore your backup, if you know how to, or if you want to keep my kernel installed, you are good to go, but if you need help with removing my kernel, here are the steps:
Follow these steps to restore your boot partition :
1. Go to recovery
2. Go to backup and restore.
3. Select the backup that you created before installing the kernel, to restore it(most likely, there will be just 1 unless you have made backups earlier).
It'll take a short while to restore, and after restoration is done, you can just reboot to system and you'll have your previous kernel as nothing happened
Releases
V1.1.2
Third Release! (26th Feb, 2018)
Slight modifications in some drivers.
Merged more upstream by google.
File is available at HERE
Older Releases (With Change logs):
V1.1
Second Release! (14th Jan, 2018)
Fixed the auto reboot issue when inactive!
Merged more upstream by google.
File is available at HERE
V1.0
First Release! (7th Jan, 2018)
This is the first release,
We have f2fs support,
Upstream with google's latest commits for 3.10 kernel version,
Upstream to 3.10.108 kernel version.
File is available at HERE
Is it suggested to test 'alpha' builds? I mean why is it posted here if it isn't stable?
rahulrishi said:
Is it suggested to test 'alpha' builds? I mean why is it posted here if it isn't stable?
Click to expand...
Click to collapse
alpha + testing -> stable
only problem is , phone reboots when inactive !
It rebooted many times last night and was discharged from 31% to 0% in morning.
release fixed version of entangled soon!
pnkj7890 said:
only problem is , phone reboots when inactive !
It rebooted many times last night and was discharged from 31% to 0% in morning.
release fixed version of entangled soon!
Click to expand...
Click to collapse
Thank you for your feedback, The bug has been fixed.
BTW, I had that bug listed in the knows issues.
I suggest that next time when you want to post a bug report, first look in the known issues, and if it is not in the known bugs list, then get logs(check #3 post of this thread for instructions).
Yes you mentioned the random reboots. I presented to you an instance with my phone(reboots when kept inactive ) with entangled v1 installed. I hoped that it might be of some use. No need to be rude, just trying to help. I do appreciate your work. Thank you!
pnkj7890 said:
Yes you mentioned the random reboots. I presented to you an instance with my phone(reboots when kept inactive ) with entangled v1 installed. I hoped that it might be of some use. No need to be rude, just trying to help. I do appreciate your work. Thank you!
Click to expand...
Click to collapse
My intention was not to be rude, but to let you know that when ever you report bugs, logs are VERY important thing.
Because without logs, we cant do anything!
Thanks for understanding. No intention of being rude.
Try out the V1.1, that bug has been fixed.
Leeco le 1s supports monitor mode ?
It is possible to add support for monitor mode for kali-nethunter
I installed the kernel by twrp recovery. Iam unable to boot in system my stuck at leeco logo screen. I tried it 3 and more times same result
Then I rebooted into recovery and saved logs ( Dmesg, recovery) by twrp recover
Where to upload the files ?
Mahendar01 said:
I installed the kernel by twrp recovery. Iam unable to boot in system my stuck at leeco logo screen. I tried it 3 and more times same result
Then I rebooted into recovery and saved logs ( Dmesg, recovery) by twrp recover
Where to upload the files ?
Click to expand...
Click to collapse
Here in XDA obviously. There's an option to upload stuff,use that.
rahulrishi said:
Here in XDA obviously. There's an option to upload stuff,use that.
Click to expand...
Click to collapse
Logs - https://drive.google.com/folderview?id=1gmGb1BrboTmKGy5tJM7xJuVVtRrDW6U-
Mahendar01 said:
Logs - https://drive.google.com/folderview?id=1gmGb1BrboTmKGy5tJM7xJuVVtRrDW6U-
Click to expand...
Click to collapse
There's an option to upload files on XDA,
Or you can use hastebin.com
Thank for helping
Mahendar01 said:
Leeco le 1s supports monitor mode ?
It is possible to add support for monitor mode for kali-nethunter
Click to expand...
Click to collapse
Not a right place to ask
New Update have been released.
I have been super busy lately, hadnt got enough time to work on anything dev related!
This update merged more updates from google and some slight modification in some drivers, should improve user experience
Check post 2 for links to download the new kernel.
Same has 1.1
It's doesn't boot up
It's stuck on leeco logo
Mahendar01 said:
Same has 1.1
It's doesn't boot up
It's stuck on leeco logo
Click to expand...
Click to collapse
Lol what, which device do you have and which ROM?
It is not compatible with eui, if you have that, sorry it's not compatible.
sscsps said:
Lol what, which device do you have and which ROM?
It is not compatible with eui, if you have that, sorry it's not compatible.
Click to expand...
Click to collapse
I use leeco 1s indian version 19s
Please Suggested me best rom to try on it
Source code: (Unmodified)
Device tree: https://github.com/DevelopedInside/android_device_wileyfox_marmite
Kernel: https://github.com/DevelopedInside/android_kernel_wileyfox_msm8937
Vendor: https://github.com/DevelopedInside/proprietary_vendor_wileyfox
New Rom
http://www.mediafire.com/file/dv69tdgx9r99e3f/crDroidAndroid-9.0-20200219-marmite-v5.11.zip
crDroidAndroid-9.0-20200312-marmite-v5.12
New Rom
March security update
lineageOS String updated to 5.12
http://www.mediafire.com/file/gejbk30o1lev8vs/crDroidAndroid-9.0-20200312-marmite-v5.12.zip/file
Robin..what it's working? And what not?
Tnx :All it's OK!
I find a bug//
in Whatsapp its having a problem with recording an audio message// ??*
ciobaneasca said:
I find a bug//
in Whatsapp its having a problem with recording an audio message// ??*
Click to expand...
Click to collapse
Suppect its a Whatsapp problem (Facebook you know) Try a lineage 16.0 rom and see if it works there?
robin0800 said:
Suppect its a Whatsapp problem (Facebook you know) Try a lineage 16.0 rom and see if it works there?
Click to expand...
Click to collapse
I think so too...
I found a 2 bug..with Google pixel launcher..it's crushing system ui on first load after restart device..when I press button to see which apss are opened..
ciobaneasca said:
I think so too...
I found a 2 bug..with Google pixel launcher..it's crushing system ui on first load after restart device..and press button to see which apss are opened..
Click to expand...
Click to collapse
I will build a linage 16.0 rom and upload it probably tomorrow.
robin0800 said:
I will build a linage 16.0 rom and upload it probably tomorrow.
Click to expand...
Click to collapse
An clean build of Los?
This is version of Pixel Launcher..
/lineage-16.0-20200322-UNOFFICIAL-marmit
Not the right pla\ce but here it is.
http://www.mediafire.com/file/ails9jgqwbr0kcq/lineage-16.0-20200322-UNOFFICIAL-marmite.zip/file
robin0800 said:
Not the right pla\ce but here it is.
http://www.mediafire.com/file/ails9jgqwbr0kcq/lineage-16.0-20200322-UNOFFICIAL-marmite.zip/file
Click to expand...
Click to collapse
You test it? Or just compiled?
ciobaneasca said:
You test it? Or just compiled?
Click to expand...
Click to collapse
I tested it.... Whatsapp still does not record.
But yes I just compiled I am not a developer
robin0800 said:
I tested it.... Whatsapp still does not record.
But yes I just compiled I am not a developer
Click to expand...
Click to collapse
OK..tnx for information..
Then...I'm not installing it.. Because I have cR Droid..with the same bugs..
Sow..Robin..what we have? 2 Roms with the same bugs?
1). Bug with the Sound ( WhatsApp no rec. Sound messages, and Distorted sound in phone when you make a call in speaker mode)
2). Bug with Pixel Launcher ..crushing system Ui ( When press button to see history off opened apps)
3). Battery drain.
4). Hot device when watching video on youtube or facebook.
Who can fix that..??
crDroidAndroid-9.0-20200426-marmite-v5.12
New Rom With April Security Patch
https://www.mediafire.com/file/f0xevve8oew6f99/crDroidAndroid-9.0-20200426-marmite-v5.12.zip/file
robin0800 said:
New Rom With April Security Patch
https://www.mediafire.com/file/f0xevve8oew6f99/crDroidAndroid-9.0-20200426-marmite-v5.12.zip/file
Click to expand...
Click to collapse
@robin0800 will you be making an update to the lineage 16 ROM or was that a one off? thanks.
crDroidAndroid-9.0-20200511-marmite-v5.12
New Rom with May security patch
http://www.mediafire.com/file/xmuq9irqi3tat38/crDroidAndroid-9.0-20200511-marmite-v5.12.zip/file
Rom review
robin0800 said:
New Rom with May security patch
Selinux doesn't work but o well never really care about whether it is enforced or disabled much anyway I did once manage to get selinux working through prop edits... or once using an app but fingerprint stopped working
Most other things seems to be working fine which is great
Official crdroid for Marmite has same issue but it is older version
Sometimes the torch stop working reboot fixes it and restarting system ui crashes the entire os repeatedly so this requires a reboot using the actual buttons
This is probably the best Android 9 rom for the swift 2 so much cool functionality and it would be sik to use a stable crdroid 6 Marmite rom
Click to expand...
Click to collapse
this phone its so old, and i play again nice, thank for dev
how install the magisk ? thank
Allow OEM unlocking from developer options first
Cedoresti said:
this phone its so old, and i play again nice, thank for dev
how install the magisk ? thank
Click to expand...
Click to collapse
READ EVERYTHING FIRST NOT IN CHRONOLOGICAL ORDER Assuming you're on marmite you will have to go to XDA and go on Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Other Development then click on lineage 15.1 rom download TWRP 3.2.3 from the link near to it this TWRP is the best one coz it can read the internal storage official TWRP is 3.3.1 but doesn't support internal storage so its not good once you have done that go to magisk.me and then download the magisk 20.4 flashabke zip file. Then next part is annoyimg. You will need a pc there is an app on the phone but i have never tested it and you probably not gonna have 2 phones in he first place maybe a tablet but anyway you will have download minimal adb and fastboot from any site that you think is appropriate your phones drivers should automatically install unless you have a bad os or something if they don't you will need to look into how to find your phones driver with research but you may not find them even after doing that anyway so assuming you have minimal adb and fastboot running and your phone s drivers are installed to confirm whether it has worked type in adb devices and press enter your device should come up as connected also I forgot to mention you need to on to about phone on settings system on build number a few times to unlock developer options the go to settings system developer options Enable Android debugging back to before once you have typed in adb devices a popup may come in your phone press yes allow in future option if you trust the device you're using once you press yes your device is usable you need to enable USB mass storage and copy twrp to your computer now for Windows 10 as I've only done this on windows 10 press on start and locate minimal adb and fastboot right click on it and press open file location if it comes up with the shortcut which I'm guessing it has right click on minimal adb shortcut and then open file location you will need to copy the TWRP file to there and rename the TWRP IMG to twrp.img go back to minimal adb and fastboot and also put your phone in fastboot mode now I think as soon as you turn your phone off it should go to fastboot mode if not then search how to do it coz I can't be asked writing every detail. Your phone will be factory data reset in the process this is for data security we'll come back to that later you may lose your warranty but that's not a problem if you know how to take care of your phone now on minimal and and fastboot type in fastboot oem unlock you should backup your data first go on settings system backup assuming you have Google services and play installed which I'm pretty sure you do all your data will be backed up and restored once you restore from cloud on the setup process after resetting coz of unlocked bootloader. Once you have accepted the bootloader unlock and it has been successfully unlocked turn if the device plug it in computer and type in on minimal
ADB and fastboot type in fastboot flash recovery
twrp.img now if you copied the files
In the correct directory as described before the recovery should have installed in a few seconds one problem is at the start the recovery might be getting replaced by stock recovery but after entering it a few times using power button and volume down button simultaneously should take you to the recovery you are going to see a message on your phone saying bootloader unlocked blah blah blah wait a few seconds or press power button and you will be in the recovery now your device may be encrypted type in your phone password/pin and you will be able to read internal storage press on select storage internal storage and press on download folder and then press on the magisk file you downloaded the swipe to install and you are installing root using magisk you should keep your device encrypted for security purposes now that you have twrp it can be used to bypass your screen unlock unless you have encrypted your device my marmite device encrypted the device automatically on the stock operating system another thing is that if you want to use your banking app go onto settings hide magisk manager option press ok and then the name of the magisk manager app should now be manager also go back to the settings and snake magisk hide option then restart the app and then go to the menu icon and magisk hide and then press in the app you want access to it should now be ticked and root should be hidden from the app my guide isn't perfectly layed but should have the important information you need know was writing it from the top of my head without punctuation:good:
i have ready 3.2.3-0. ONLY 3.2.2 ITS OK ?
ROM dedicated for All Quark (Moto MAXX/Turbo and Droid Turbo - XT1225, XT1250 and XT1254)
This ROM is the LineageOS from https://lineageos.org/ with specific changes to improve the experience for Quark that is why the ROM has the MOD type, all modification are in the changelog
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Gapps:
Open Gapps
Choose Platform: ARM, Android: 11.0, and a Variant the one that have all you need, I recommend the Nano pack, but it may not have all you need so check before download, if any problem with a diferent version try the Nano before reporting issues.
TWRP For Quark:
TWRP Use laste Mod version from xda
Installation:
Make sure you are running latest MOD TWRP from xda TWRP thread
Download the latest ROM and GApps**.
Reboot to recovery (recommended make a backup)
Coming from different ROM? Then Always wipe Data (without media aka without internal memory)
Wipe System*
Flash the latest build and GApps **
Reboot and enjoy!
* Wipe of Dalvik Cache and Cache not demanding but may help with some random minor bug that show after a update
** Gapps not demanding the ROM works perfect without it but if you plan to use gapps you need to flash it on a clean install with the ROM, In a ROM updates a "dirty flash" if you already have gapps always flash gapps again with the ROM update
Changelogs:
LineageOS - 18.1 source and Quark Changelog (Click Here)
What's working :
Everything minus VoLTE support for XT1254 (1225 doesn't have this featuring).
Known Android 11 issues :
Not PRE-ROOTED, ROOT solution is available read this thread second post
Old issue maybe resolved on latest TWPR update but... TWRP may not be able to backup or decrypt data encrypted on Oreo or Up: no know workaround, one day TWRP will support it.
General bug help/fix in second post or some were in the thread, use XDA building "Search Thread" option to find general help for this thread project...
Source:
LineageOS Source
Device Tree
Kernel tree
Vendor tree
Mod Kernel Adiutor tree
XDA:DevDB Information
[ROM][All Quark][Android 11] LineageOS 18.1 for Quark
Contributors
Felipe Leon (fgl27) is the main contributor (as I'm the one making it).
But the XDA community, quark user base plus the open source community from XDA, github and the LineageOS team is what make this project so good, thank you all :good:.
ROM OS Version: 10.x
ROM Kernel: Linux 3.10.x
Based On: LineageOS 18.x
Version Information
Status: Stable
Created 2021-30-05
Last Updated Check Changelog click here
Below are some of the helps and or workarounds for the most occurring issues.
ROOT Use Magiks
GPS / Radio:
Changing/Updating the ROM may cause GPS lock problem, there is two separated help
option 1) Install "GPS Status & Toolbox" , open the app, slide the left option and open "Manage A-GPS state" click in Reset, after repete the process and now click in Download, close the app after receive the OK, wait a few seconds and try a gps lock using the same app, if that doesn't help try again after a reboot, if that doesn't help go to option 2 below
option 2) If the above doesn't help you can try to erase all the radio status
Erase the radio status also applies to the case you have No SIM Card or no Cell Signal level in status bar.
To erase the radio status is very simple just flash this zip "Clean_modem_status.zip" via TWRP no wipe is need, is also recommended to try option 1 after this if you flashed because of a GPS problem.
If after flashing the cleaner you find any problem related to lost of signal, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version via fastboot (aka "via bootloader")
Code:
mfastboot flash radio radio.img
find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)
Random Power off or reboots?
To identify if the device random reboot or simply power it self off there is two ways.
1) If after the device goes black you can't power it up again without plunging the charger, then is because the battery is dead, even if yours battery had good % left before it shutdown yours battery is probably damage doesn't matter if the device/battery is new a battery can go bad simply by charging the device wrong, a wrong way to do it is let the device constantly go bellow 20% as low you let it get worse yours battery will be with time.
2) Check the boot reason prop "ro.boot.bootreason" :
Using the app BHB27 Kernel Audiutor > logs section > search in a log > mark getprop > search keyword "reason".
If the result is power_key_press the device didn't reboot it power off.
Code:
[ro.boot.bootreason]: [power_key_press]
On this case, is recommended to set the battery "Automatic power saver" from default 15% to a higher value then the one yours device is power it self off.
-----------------------------
If the result is reboot the device reboot it self
Code:
[ro.boot.bootreason]: [reboot]
On this case, is recommended to just share a log, do as is recommended on next post.
Bootloop to TWRP after a Factory Reset (Settings/System/Reset option/Factory reset):
This is a Nougat and up problem, it only happens if you are using a TWRP from the official site (with is not update to properly support Nougat and Up Android versions) or a old version of TWRP, to fix it just flash latest MOD TWRP version from the TWRP xda.
TWRP xda thread Click Here
Pictures access, view, sharing or related:
One thing that I notice regarding permission is if you have a app that access a folder that was created in older OS this app may be able to access this folder but not fully access the files like the below example.
You take a picture or a screenshot and can't see or share it with some apps, the simple fix is just erased/delete the folder with that problem for example the DCIM (camera folder) and or Pictures (Screenshot) folder under Main storage (or any folder were you face a picture or file access related problem), of course you can backup the files to another folders first using a file explorer that can see the files (maybe necessary one with ROOT access), then let the OS service recreate the folder, it will automatic recreates after you take a new picture or screenshot (or manually make the new folder if is a custom folder mane by you), test to see if the problematic app can see after.
USB OTG player:
On latest android version Nougat and above, to play anything from a USB OTG device is needed proper permission, that is not simple to give as the app must request it to be given, so to play anything from a USB driver find a app like this one
VVM XT1254 only
VVM app (VVM may only be accessible via play with the link, click here and chose open with play), VVM may not work correctly google has it on version is free and seems to work 100% Google voice, the in the phone app of b this ROM also has a dedicated option for voice calls
Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand or reproduced I can't fix.
Always post a bug with @fgl27 and a log .zip generated by the app
BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP (ROOT is needed for this)...
Even after a random reboot share a log
If is a Reboot/Power off related bug make the log as soon the device finishes boot up
Everything was working great, until this weekend. I was in an old hotel that gets terrible signal, so i used WIFI the whole time. When i left to head in to work this morning, i noticed that my data never came back. I can make calls, send texts, get on WIFI, use bluetooth... but the 4g LTE icon is not on my top bar, and im getting "No internet connection" errors. --- I verified that Data is turned on, i have something along the lines of "LTE/CDMA/EvDo" selected, ive restarted the phone, and ive tried popping out my SIM card and reinstalling it. -- Any suggestions?
imcensored1 said:
Everything was working great, until this weekend. I was in an old hotel that gets terrible signal, so i used WIFI the whole time. When i left to head in to work this morning, i noticed that my data never came back. I can make calls, send texts, get on WIFI, use bluetooth... but the 4g LTE icon is not on my top bar, and im getting "No internet connection" errors. --- I verified that Data is turned on, i have something along the lines of "LTE/CDMA/EvDo" selected, ive restarted the phone, and ive tried popping out my SIM card and reinstalling it. -- Any suggestions?
Click to expand...
Click to collapse
I figured it out. I started playing with all the network settings, and i found one that allowed me to set the "access point". I found the access point somehow was set to "Xfinity", once i changed it to "Verizon" my data came back. I am not sure how it changed or why it changed, as it was working before I entered the no coverage zone.
I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 18.1 source and Quark Changelog
I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 18.1 source and Quark Changelog
fgl27 said:
Below are some of the helps and or workarounds for the most occurring issues.
ROOT Use Magiks
GPS / Radio:
Changing/Updating the ROM may cause GPS lock problem, there is two separated help
option 1) Install "GPS Status & Toolbox" , open the app, slide the left option and open "Manage A-GPS state" click in Reset, after repete the process and now click in Download, close the app after receive the OK, wait a few seconds and try a gps lock using the same app, if that doesn't help try again after a reboot, if that doesn't help go to option 2 below
option 2) If the above doesn't help you can try to erase all the radio status
Erase the radio status also applies to the case you have No SIM Card or no Cell Signal level in status bar.
To erase the radio status is very simple just flash this zip "Clean_modem_status.zip" via TWRP no wipe is need, is also recommended to try option 1 after this if you flashed because of a GPS problem.
If after flashing the cleaner you find any problem related to lost of signal, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version via fastboot (aka "via bootloader")
Code:
mfastboot flash radio radio.img
find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)
Click to expand...
Click to collapse
I tried these fixes for the GPS a few times but no luck. Do you have any other ideas?
Thank you.
It's been awhile since I've had to deal with this issue. I forget exactly what I went through to get it resolved. Have you tried an absolute cold raw reinstall? Wipe everything in the phone except internal memory, from TWRP.
SecretPotatoChip said:
I tried these fixes for the GPS a few times but no luck. Do you have any other ideas?
Thank you.
Click to expand...
Click to collapse
Sorry I was busy didn't check xda for a while.
If those don't help the best option is to try Einsteindks from above post
On Android was added a update to the GPS libs that fixed most of the issue, that is way most don't have any issue anymore, but if you have one is probably something very odd that need a full clean to resolve.
Active display is not working. How do I turn it on?
DobrRk said:
Active display is not working. How do I turn it on?
Click to expand...
Click to collapse
Active display is a Motorola name.
Use Ambient display, enable it on settings -> system -> actions
fgl27 said:
Active display is a Motorola name.
Use Ambient display, enable it on settings -> system -> actions
Click to expand...
Click to collapse
Thank you very much. It is a pity that it does not work as on the old motorola, with a separate processor under this option. I really liked the firmware.
Power Functions was an awesome option on Motorolas, at one point. Shame they didn't carry over. At least other options exist. Neat idea, though. Good to see the display stuff be standard, albeit under different names.
Verizon just sent me this text. (Advanced Calling /HD Voice). I feel like I enabled this years ago. I went to search to turn it on and I see it's not an option. Is this something that was coded out of Lineage?
I know you have to activate it on your phone and then Verizon has to activate it on their end.
imcensored1 said:
Verizon just sent me this text. (Advanced Calling /HD Voice). I feel like I enabled this years ago. I went to search to turn it on and I see it's not an option. Is this something that was coded out of Lineage?
I know you have to activate it on your phone and then Verizon has to activate it on their end.
Click to expand...
Click to collapse
I believed HD voice needs VoLTE something that doesn't work in custom ROM
opengapps release they version for Android 11, I updated OP with the link.
Sometimes after not using my device from a few hours it became very slow the first few minutes I try to use it, some apps freeze giving me that warning "app is freeze kill it" or something like that, I notice that a lot of service don't run as they did on old version of android regularly on background, but they sometimes run all together when you wake the device up.
Most are service from google apps and frameworks, to improve this I'm using this new battery option that show on each app info, that allows you to enable "Background restriction" see attached.
You have to manually set to restrict each individually app that you wanna to be restricted, after I did to almost all available apps, notifications are working as expected and I don't have slows down at least not from service on the background.
If anyone has some issue related try to use those options to improve.
I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 18.1 source and Quark Changelog
Einsteindks said:
It's been awhile since I've had to deal with this issue. I forget exactly what I went through to get it resolved. Have you tried an absolute cold raw reinstall? Wipe everything in the phone except internal memory, from TWRP.
Click to expand...
Click to collapse
I went into TWRP, and wiped everything except internal storage and usb otg. My gps still does not work.
SecretPotatoChip said:
I went into TWRP, and wiped everything except internal storage and usb otg. My gps still does not work.
Click to expand...
Click to collapse
Next step would be to save internal on an OTG, along with ROM & Gapps, Titanium Backup, etc, eject/remove OTG. Get into TWRP, wipe ALL, plug in OTG, reboot into TWRP, install ROM, Gapps & modem reset zips after selecting OTG as source. Double check yourself along the way, trust me! It's easy to forget a step and have to re copy files onto the OTG from computer backup.