[ASSISTANCE][GUIDE]Solutions, Tips and Tricks[H2OS][O2OS][CUSTOM MM ROMs]

[ASSISTANCE][GUIDE]Solutions, Tips and Tricks[H2OS][O2OS][CUSTOM MM ROMs] - OnePlus 2 General

Okay guys, development on OnePlus 2 is happening with lot of troubles, vexed with questions, rather less than a war. This is one thread to wipe them all(most of them). I'm providing a thread or repo kind of thing to avoid all repeated questions and provide a simplified solution to newbies. Most of the problems are already existing or already been posted and solved. So please use this thread or search button up top. If anyone wants to contribute to this thread, please feel free to ask me. Donate to developers they are really doing hard work bringing all these features. Thanks.
Answers in post #2
[INDEX] OnePlus 2 [13 Mar 2016] by benkxda
TWRP recovery
Quick Links:
[GUIDE] Unlock/Root/Flash for OnePlus Two by Heisenberg
[UKM for OP2] Install synapse and tune you kernel for your needs! [Works on CM13/HOS] by urgali
[FirstAid] [MM] [H2OS] [OOS] Stuck in Fastboot after H2OS MM BETA flash Solution! by deletescape
[ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates by Spannaa
[GUIDE][RESET][UNTAMPER][UNBRICK] Stock Reset to OxygenOS 2.2.0 by fareed_xtreme
[GUIDE] Return OP2 to 100% Stock / Unbrick Soft Bricked OP2 by Naman Bhalla
[PROFILES][BOEFFLA KERNEL][UNOFFICIAL]Boeffla Kernel Profiles for OnePlus 2 by v7
[Guide] OnePlus 2 Home Button Dead Solutions by regalstreak
[GUIDE] Disable selinux to allow Xposed framework for Oneplus 2 by cr1cr1 on OxygenOS
[GUIDE][OFFICIAL OP2 FILES][OOS 2.1.1] Unbrick/Recover OnePlus 2 Back to stock 100% by paultje162
[PROFILES][Benschholds Custom Kernel][UNOFFICIAL]Benschhold Kernel Profiles by Xendetor
[ASK!] Which ROMs Do You'll Want? by regalstreak
[GUIDE] [LINUX/UBUNTU] Extract/Modify/Rebuild Lollipop ROMs ! by Yash98
[DISCUSSION] [layers/RRO] [INDEX] share your compatible layers for oxygen OS by vergilbt
[GUIDE] Installing Xposed Framework on Stock ROM after ROOT for Oneplus 2 by thebuginyou
[MEGA-THREAD][PICS]Pictures taken with OnePlus 2 by v7
^This thread is a bonus.
This is the list of Custom ROMs(*not in oder*) we have for codename: oneplus2,
[Unofficial] [AOKP] [6.0.1] OnePlus2 by @King_lilrowrow
[ROM][6.0.1][--OFFICIAL--] Mokee Open Source Project @[email protected]
[ROM][6.0.1][--OFFICIAL--] Resurrection Remix v5.6.x @regalstreak
[ROM][6.0.1][UNOFFICIAL] TEMASEK'S CM 13 @benschhold
[ROM][6.0.1][UNOFFICIAL] CyanogenMod 13.0 @Seraph08
[ROM][6.0.1][--OFFICIAL--] Exodus Android 6 for @Raja.M
[ROM][6.0.1][--OFFICIAL--] AICP 11.0 @Trafalgar Square
[ROM][6.0.1][UNOFFICIAL] BLISS ROM @benschhold
[ROM][6.0.1][UNOFFICIAL] CyanPop v5.9 @Taker18
[ROM][6.0.1][UNOFFICIAL] crDroid @Taker18
This is the list of Stock based ROMs(*not in oder*) we have for codename: oneplus2,
[ROM] [LP/MM] HydrogenOS H2OS v1.2.0 | ALL SENSORS! | +ADDONS | BLOAT REMOVER @Yash98
[ROM][EP/EP-L U2 Beta][2.2.1] - OxySlim - [Now Screaming in Dark, Just a lot more] @sewer56lol
[ROM]SkyDragon v3.3 |5.1.1|OOs|2.2.0|Aroma|Battery,Smooth and Fast! @matitorres07
[ROM]SkyDragon|6.0.1|H2Os|Sensed|v4a|Battery,Smooth and Fast! @matitorres07
Flyme OS 4.5 Based On H2Os [BETA][FP WORKING] @jjbro007
This is the list of Custom Kernels(*not in oder*) we have for codename: oneplus2,
[KERNEL][CM13]Benschholds Custom Kernel v1.9 @benschhold
[KERNEL][CM13]Sandy Kernel v1.4 @Santhosh M
I Have added some info & removed dates and stuff to make it look linear and clean hope you all don't mind, if so please ask me I'll add them.
also, didn't include some ROMs because I'm not sure with their source(not git source).
List of FAQs:
I have a bug
Which modem/firmware should I flash before I install this ROM?
Which Gapps should I flash?
Can I dirty flash?
Now on Tap is missing, please help.
Battery drain is heavy, please help.
WiFi drains heavy battery, why?(please be polite)
Noise in mic, please help.
Is there a way to disable the sim that is not being use?
Viper4Android not working?
Kcal configuration?
I'm having bootloop, stuck at logo
Which Super User should I use?
My WiFi is not stable
Swap buttons missing
Installation fails or stuck at patching system image
Manually switch carrier
How do I enable encryption
My WiFi mac address is shown all 0s or wrong.
Answers in post #2
Last but not least, Thank every person who helped, let us make XDA and world a beautiful place.
Thanks to all developers and people who tried to help others and me when we had problem.
Donate to developers they are really doing hard work bringing all these features
NOTE: Not all these solutions or fixes are by myself, this is contribution of community.
Will be adding as many as possible and currently in editing.
Here is a nice song, Gareth Emery feat. Christina Novelli - Concrete Angel [Official Music Video]
Hope this thread helps.

So this is the answers section,
First of all most of bugs sometimes are caused when we install any mods or any piece of software other than ROM, so I recommend do a clean flash and then report a bug. Thank y'all!
0. I have bug, it's itching me.
This is very normal. You go to doctor and say I have problem. Will he solve it? He needs information like what's your exact problem, where you have that problem, right? So please provide a log cat.
starkly_raving said:
How to get good logs...
http://forum.xda-developers.com/showthread.php?t=1726238
Or...
http://forum.xda-developers.com/showthread.php?t=2274119
And if you don't have a PC... **shivers at the thought**
https://play.google.com/store/apps/details?id=scd.lcex
Or...
https://play.google.com/store/apps/details?id=com.anrapps.ultimatelogcat
Click to expand...
Click to collapse
1. Which modem/firmware should I flash before I install this ROM?
This is question raised by many people who have security settings crash or bootloop. So I wanted to write upon this in two ways.
If you are coming from Leaked H2OS Marshmallow ROM then,
First, you need to flash the revert2lollipop zip from here How to revert back to Lollipop by Yash98 if not your device will be in boot loop.
Below are the ROMs you can flash directlywhen you come from Leaked H2OS MM or Based ROMs after flashing revert2lollipop zip.
ROM][6.0.1][UNOFFICIAL] CyanogenMod 13.0 __Seraph08
[ROM][6.0.1][UNOFFICIAL] Blissrom __benschhold
[ROM][6.0.1][UNOFFICIAL] crDroid __taker18
[ROM][6.0.1][UNOFFICIAL] Temasek CM 13 __benschhold
[ROM][6.0.1][UNOFFICIAL] CyanPop v5.9 __taker18
[ROM][6.0.1][--OFFICIAL--] Resurrection Remix v5.6.x __regalstreak
[ROM][6.0.1][--OFFICIAL--] AICP 11.0 __Trafalgar Square
[ROM][6.0.1][--OFFICIAL--] Mokee Open Source Project [email protected]
[ROM][6.0.1][--OFFICIAL--] Exodus Android 6 for __Raja.M
Click to expand...
Click to collapse
If you are coming from OxygenOS/HydrogenOS Lollipop ROM then,
I installed O2OS every time for testing I changed ROM, it really is a hectic task.
Below are the ROMs you can flash directlywhen you come from OxygenOS
[ROM][6.0.1][UNOFFICIAL] CyanogenMod 13.0 __Seraph08
Click to expand...
Click to collapse
Install *new*modem from https://androidfilehost.com/?w=files&flid=49404 for below ROMs
[ROM][6.0.1][UNOFFICIAL] Blissrom __benschhold
[ROM][6.0.1][UNOFFICIAL] crDroid __taker18
[ROM][6.0.1][UNOFFICIAL] Temasek CM 13 __benschhold
[ROM][6.0.1][UNOFFICIAL] CyanPop v5.9 __taker18
[ROM][6.0.1][--OFFICIAL--] Resurrection Remix v5.6.x __regalstreak
[ROM][6.0.1][--OFFICIAL--] AICP 11.0 __Trafalgar Square
[ROM][6.0.1][--OFFICIAL--] Mokee Open Source Project [email protected]
[ROM][6.0.1][--OFFICIAL--] Exodus Android 6 for __Raja.M
Click to expand...
Click to collapse
2. Which Gapps should I flash?
Download them from: http://opengapps.org/
{
"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"
}
3. Now on Tap is missing, please help.
Please download the full Gapps from http://opengapps.org/
4. Battery drain is heavy, please help.
First of all no one on *XDA* creates something that makes your battery drain.
Tips:
If you are a person who need to save battery you better uninstall Facebook apps first.
Clean install will resolve your battery issues.
Switch off sync when not used.
Switch off Ambient display and gestures.
Do a clean flash and see, battery drains happen when an app is in sync loop also.
Report something with Screenshots of stock battery activity or better battery stats.
5. WiFi drains heavy battery, why?(please be polite)
Sometimes battery consumption by WiFi is calibrated.
Also if you have a drain with number starting with 9 or so, that is a pid of process that used WiFi.
Be polite to everyone, only then you will be helped.
Tips:
Giox92 said:
Hi, I have solved it going to Settings -> Backup & Reset -> Network settings and Reset Settings. After this, restarts your OnePlus and reconnect it to your WiFi. I hope I have solved this annoying issue because I have fixed with this method. Sorry for my bad English !
Click to expand...
Click to collapse
Disable scanning in location.
Location>three dot menu>scanning hen disable WiFi and Bluetooth scanning.
Clear your battery stats.
Code:
TWRP>File manager>Data>System>batterystats.bin,
then wipe cache/dalvik cache,
then reboot.
check for this battery cycle and report back.
If the issue is not solved, clean flash.
6. Noise in mic, please help.
Many people reported noise in-call.
To solve this go to System>build.prop find and set these values to it.
Code:
persist.audio.fluence.voicecall=false
ro.qc.sdk.audio.fluencetype=none
7. Is there a way to disable the sim that is not being use like on OxygenOS?
Right now, no, not on Custom ROMs. Only way is to remove SIM card, sorry!
8. Viper4Android not working?
This is ROM specific so, when the SELinux is set to enforcing Viper4Android doesn't work properly.
Take backup and try this
Flash this http://forum.xda-developers.com/showpost.php?p=65604632&postcount=1623
then this *if you have issues*http://forum.xda-developers.com/showpost.php?p=65762130&postcount=2814
9. Kcal configuration?
Kcal configuration is not possible on stock CyanogenMod kernel,
please install custom kernels and
install Syanpse to tune your Kcal.
[UKM for OP2]Install synapse and tune you kernel for your needs! [Works on CM13/HOS] by urgali
10. I'm having bootloop, stuck at logo
This is rarely developers mistake. Most of the times this is solely users mistake.
Please clean flash.
Clean flash means, wiping everything except internal storage from TWRP Wipe option.
11. I'm having Google apps force close continuously
Install Gapps immediately after installing ROM.
12. Which Super User should I use?
You can user the in built root manager or install the latest SuperSU by chainfire from his thread.
13. My WiFi is not stable.
Dividium said:
So I decided to try something different regarding the wifi problem.
With someone suggesting the INI file I decided to get get the one I had on OOS. (/etc/wifi/WCNSS_qcom_cfg.ini)
I've replaced the current one and rebooted.
So far things seem better, though it's too early to tell for sure.
I did notice, while comparing the file, that there were some comments in some settings from OnePlus regarding having certain settings to cut down on disconnects...
Mind you i did experience one disconnect while typing this, but it does seem better. Could be just my imagination though.
I've attached the OOS file.
Click to expand...
Click to collapse
check below link for attachment, don't forget to remove ".txt" as extension.
(http://forum.xda-developers.com/showpost.php?p=65883989&postcount=3581)
daninantro said:
people having wifi problems please try this
Using any root explorer, go to /system/etc/wifi and find a file 'WCNSS_qcom_cfg.ini'
Open it using a text editor and change the following lines:
1) McastBcastFilter=3 to McastBcastFilter=0 and
2) isAndroidPsEn=0 to isAndroidPsEn=1 and then save the file and reboot.
Try this, i have done this and my wifi drops have gone and wifi speed is good most of the times I cant guarantee if this is a fix for wifi issues but this worked for me..
If any on you know any different mods to improve wifi connectivity then please suggest
Click to expand...
Click to collapse
Settings>WiFi>Keep WiFi on during sleep to always.
Change the WiFi frequency band
Change the WiFi region code to you country or continent.
If not resolved, this is a known CyanogenMod issue so don't worry, it has been addressed.https://www.reddit.com/r/cyanogenmod/comments/441b9m/wifi_issues_on_cm13_nightlies/
14. Swap buttons missing.
http://forum.xda-developers.com/oneplus-2/general/cm-based-roms-swap-buttons-oneplus-2-t3336661
15. Download stuck at patching system image or download fails.
Possibly due to incomplete download.
Download the complete build and check MD5
Use PC to download a build
wipe system and data partition too in TWRP
ref: https://www.reddit.com/r/cyanogenmod/comments/3z7c2i/stuck_on_patching_system_image_unconditionally/
16. Can't switch carrier manually
I live in India and we don't do this, if someone can guide me on this, I'll update here.
17. How do I enable encryption?
Information below.
airtower said:
In case anyone is thinking about enabling encryption on these builds, I thought I'd share my findings as it's not well covered for this device.
Encrypting the device was straightforward (security -> encryption). Doing so requires a nearly full battery and you must be plugged in and charging on USB. It warns it will take an hour or more, but it only took 15-20 minutes for me. The device reboots in to a recovery/bootloader-like screen and encrypts the device from there. The estimated time remaining isn't very accurate. It reboots and everything is more or less transparent at that point. I don't notice any performance hit, but I don't run benchmarks or games so YMMV.
Here's what I've noticed since then, in order of importance to me:
TWRP (assuming CWM as well) cannot mount encrypted /data in recovery. It prompts for a password, but I have only a PIN defined. Neither the PIN nor the lollipop "default_password" will decrypt /data which has several implications:
You cannot flash updates entirely "on device". As /data is encrypted and TWRP (both 3.0.0.0-2 and 2.8.7.0 can't get the partition decrypted at this point, it can't see the files on your sdcard. It has no problem mounting /system, so if you can find a way for recovery to see the ROM, you can flash it. This can be done by moving the ROM to a USB-OTG device or as I do - use ADB sideload. I've heard some people with other devices being able to use /cache, but there wasn't enough free space there for these builds. I did seem to notice the flashing and cache rebuild process taking a little longer after encryption, but that may just be because I was slightly nervous doing my first update.
If you decide to factory reset (not sure if this would even work in recovery), you can't exclude /data/media from the wipe as all of /data is encrypted, so your sdcard data will have to go too. Backup with TiBu (or maybe TWRP live backup?) and move the backup off the device to a PC or USB-OTG.
You can't unencrypt. Once encrypted, the menu item under Security does nothing. I haven't done it yet, but I believe the only way to unencrypt is to factory reset. Not sure if you can do this through recovery or what but just be aware.
The battery light LED will stay on if you reboot with the device plugged in
The device boots up in two phases, and you are prompted to unlock the device after the first phase. I have a PIN set so it asks for it, but presumably if you're locked with another method it will ask for that. FPS isn't an option here, so it will use the "backup" method. I have the option to prompt for a PIN enabled, but I believe you'll be asked to unlock regardless. If you have problems with random reboots, this could be worth noting as presumably if your device rebooted in the middle of the night, you're not going to get an alarm in the morning. Hasn't been a problem yet for me, but fingers crossed.
tl;dr - encryption works so if you really want or need it, go for it. If you're a flashaholic and do so without a PC or USB-OTG device, you may want to hold off until TWRP can successfully decrypt and mount /data.
Click to expand...
Click to collapse
Thanks to @airtower
18. My WiFi Mac address is 0s or wrong.
Tips:
sahil chandel said:
Try this:
Go into terminal emulator (while system is running)
Type following:
su
mount -o remount,rw /system
ln -sf /persist/wlan_mac.bin /system/etc/firmware/qca_cld/wlan_mac.bin
mount -o remount,ro /system
reboot
Click to expand...
Click to collapse
Code:
Reboot into recovery.
Use Terminal (adb shell or builtin terminal from TWRP) type in:
mount system
ln -sf /persist/wlan_mac.bin system/etc/firmware/wlan/qca_cld/wlan_mac.bin
then reboot
by Grarak
My solution is the following:
1. Install a file explorer with root functionality (I took ES file explorer)
2. Navigate to /persist/ folder
3. backup wlan_mac.bin
4. edit wlan_mac.bin (open as text, choose ES note editor)
5. you'll see something like this:
Code:
Intf0MacAddress=AABBCC998867
Intf1MacAddress=AABBCC998877
Intf2MacAddress=00FFEE556623
Intf3MacAddress=00FFEE556633
END
(of course with other addresses)
Change the Intf0MacAddress to your desired one, safe, reboot, enjoy.
by @obermeier
Flash Stock OxygenOS ROM and then flash Custom ROM.
19. No mobile data issue
Update on my mobile data issue:
I had the problem that mobile data (3g/H+ ...) wouldn't stay connected for longer than a few minutes. I now successfully fixed that by deleting all APNs and manually entering the data provided by my sim card provider. Now it stays connected and i even get LTE, which it wouldn't do before.
This however doesn't resolve my one sim card loosing signal from time to time. But I now guess that this might be due to crappy network, as my other sim card stays connected at the same time and it happens to the sim card no matter which slot it is in.
by @PhatUgly
Fixed it by typing www into the APN in APN settings. Leave the other settings alone, they are detected automatically. Don't know the cause.
by @knpk13
Will be adding as many as possible and currently in editing.

@krishna442
In these moment you killed the forum[emoji13] [emoji13] [emoji13]
All is answered and nobody should have an question...
Top![emoji106]

vergilbt said:
@krishna442
In these moment you killed the forum[emoji13] [emoji13] [emoji13]
All is answered and nobody should have an question...
Top![emoji106]
Click to expand...
Click to collapse
Thank you so much for support!
:good:

Thank you, really appreciated! Only one thing to notice. In the answer 10, when you say to wipe everything except internal underline that this should be done before flashing, otherwise some user will definitely have no OS installed ahah
Cheers ?

WaxLarry said:
Thank you, really appreciated! Only one thing to notice. In the answer 10, when you say to wipe everything except internal underline that this should be done before flashing, otherwise some user will definitely have no OS installed ahah
Cheers ��
Click to expand...
Click to collapse
Haha! yes, added thank you! I can't use thanks button, 8 limit!

added to http://forum.xda-developers.com/showpost.php?p=64789545&postcount=3

Wooow nice thread...

yes you're a killer. you killed'em all with one wipe. great going mate. I hope now no one needs to wait for a solution

Flashed 3/13 build, APNs now present, but mobile signal keeps fluctuating and dropping to no signal.
Here is my Radio log http://pastebin.com/u4p1eHZ0

psicomantis said:
Flashed 3/13 build, APNs now present, but mobile signal keeps fluctuating and dropping to no signal.
Here is my Radio log http://pastebin.com/u4p1eHZ0
Click to expand...
Click to collapse
Hi, thanks for the log. I will report this to @Seraph08 and @Grarak on his Twitter as well. Thanks for log again. Hope they will look into it.
https://mobile.twitter.com/krishnas1433/status/709375221724217344
Thank you @raghu0421
Sent from my ONE A2003 using Tapatalk

Thank you very much @krishna442 , I really appreciate it.

Wifi mac address changes
Every time i flash custom rom my mac address changes to 02:00:00:00 something i need fix for it but cant find can anyone help on oxygen os or hydrogen os its same as original but on cm roms it changes to like that...

@krishna442 thanks for making this thread, hopefully word will get around and we will see less redundant and irrelevant posts in development thread!
Just one thing, I'm using the XDA premium app with dark mode enabled and the first post of this thread is hard to read because of font color...

jetfin said:
@krishna442 thanks for making this thread, hopefully word will get around and we will see less redundant and irrelevant posts in development thread!
Just one thing, I'm using the XDA premium app with dark mode enabled and the first post of this thread is hard to read because of font color...
Click to expand...
Click to collapse
I see. I'll update it when I'm home and can use my PC. Right now travelling.
sahil chandel said:
Every time i flash custom rom my mac address changes to 02:00:00:00 something i need fix for it but cant find can anyone help on oxygen os or hydrogen os its same as original but on cm roms it changes to like that...
Click to expand...
Click to collapse
Hi. In the meantime try this,
http://forum.xda-developers.com/showpost.php?p=64224824&postcount=542
Sent from my ONE A2003 using Tapatalk

krishna442 said:
I see. I'll update it when I'm home and can use my PC. Right now travelling.
Hi. In the meantime try this,
http://forum.xda-developers.com/showpost.php?p=64224824&postcount=542
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
tried not working for me

@jetfin please check with colors now. Thanks for reporting.
Sent from my ONE A2003 using Tapatalk

krishna442 said:
@jetfin please check with colors now. Thanks for reporting.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Perfect, thanks!

Thank you @krishna442 for this great summary!
I stumbled across a question in my post here:
Does the CM13 build from Seraph08 work with the new modem?
And is it difficult to downgrate it or is it just flashing an other zip file?
thanks!

obermeier said:
Thank you @krishna442 for this great summary!
I stumbled across a question in my post here:
Does the CM13 build from Seraph08 work with the new modem?
And is it difficult to downgrate it or is it just flashing an other zip file?
thanks!
Click to expand...
Click to collapse
Hi buddy, thank you first of all.
Seraph08's build works with both the modems, I'm really confused about it.[Let me test again]
But, I can only give you one suggestion. Try installing OxygenOS, check your fingerprint from 808 menu and then flash CM13. This will make your fingerprint unlock normal again.
Report back, I'll help you.
And don't forget, the golden rule. Back up.

Related

[lt03wifi][P600][ROM][CM13.0][6.0.1]CM13.0 UNOFFICIAL Builds -

Joshndroid's UNOFFICIAL CM13.0 BUILDS
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
This thread is currently under maintenance. Should there be any inaccurate information, please PM me. Images and formatting will be handled at a future date.
{
"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"
}
...not ready yet
I use my TWRP version linked in Second post
Clean Install
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM. <<-- You don't have to do this unless you want too
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. Reboot Device.
Dirty Flash
1. Download the appropriate ROM using links provide in the second post.
2. WIPE CACHE/DALVIK. (I find wiping /SYSTEM can stop some issues with play store F/C’s)
3. Install the zip from recovery.
4. Install GApps (ensure that they are from the same build, otherwise you must do a clean installation when using a newer GApps package)
3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
5. Reboot Device.
More:
Screenshot 2
screenshot 3
probably others i havn't found as yet
@RaymanFX - without him there would be no original trees for our device, simple.
@ShevT - without him there would be no cm-13.0 for our device, simple.
Source
Joshndroid Source
Note 10.1 Device Tree
Note 10.1 Kernel
Note 10.1 Vendor Files
CyanogenMod
Rom Source

Shared Google Drive Device Folder (have Rom shared directly to your Google Drive Folder)
see here for further - http://forum.xda-developers.com/showpost.php?p=65753816&postcount=4
Alternate Download - Basketbuild Download
https://s.basketbuild.com/devs/Joshndroid/CM13.0/lt03wifi
GApps - 6.0 GApps Package
http://opengapps.org/ (select ARM & 6.0)
I have be extremely pleased with Open Gapps and you can even download daily packages, I have tried the micro, mini and nano packages with good success so far - All credit to their team and original thread source can be found here for important information and updates - http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
SuperSU for flashing via recovery - Credit to @Chainfire
http://download.chainfire.eu/supersu

Joshndroid's TWRP with F2FS support
https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
F2FS is called the 'flash friendly file system.' Realistically it has been developed to assist mobile type devices with EMMC get better read speeds, among other things, to achieve a better user experience.
Still want to know a bit more check this out – https://en.wikipedia.org/wiki/F2FS. Further have a look here for benchmarks completed on another device - http://forum.xda-developers.com/show....php?t=2697069
So, how do I get F2FS?
Firstly, your going to need to have partitions that are in F2FS format and with that you need a recovery which is capable of doing that. In the second post you will see a link for an F2FS supported recovery.
Secondly, your going to need a ROM that supports it. That means, the ROM itself to support mounting partitions correctly, etc. as well as the KERNEL so it can utilise the partitions and actually boot the device.
Yeah okay, so its entirely intertwined, now what?
Well, we now have the recovery, ROM and kernel all working with F2FS we need to put it in to practice
Follow these steps (you will need a micro sdcard inserted into your device)
Complete these steps in their entirety and accurately (if I find out you didn't complete a step or skipped one because you 'know better', leading to a bricked device, I wont be happy). They might seem condescending, but hey 2 extra minutes/step may make the difference.
1. Go to https://dl.twrp.me/lt03wifiue/ and download the appropriate stock TWRP (I recommend 2.8.6.0 now) .IMG file AND .zip of your recovery and place onto your EXTERNAL SD CARD (these are in case something doesn't work)
2. While at https://dl.twrp.me/lt03wifiue/ download the same IMG.TAR and place those files into your usual ODIN directory (in case we REALLY need to flash back a recovery) - If you need Odin, download that as well.
3. Download my latest ROM zip anything from V17.6 will be supporting f2fs unless stated otherwise. Place this file into your EXTERNAL SDCARD also.
4. Download your latest version of gapps and have a supersu zip handy (latest). Place these files into your EXTERNAL SDCARD
5. Okay download my f2fs supported recovery signified by F2FS in the name (ZIP or IMG will work in TWRP 2.8.6.0). Link in second post or https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
6. Place the F2FS supported recovery into your EXTERNAL SDCARD
7. BACKUP all important files from your device's INTERNAL SDCARD as it will be WIPED when formatting to a new partition type (and I mean it will be GONE)
8. reboot into your recovery
9. select the F2FS IMG file or ZIP and flash as necessary.
10. If successful reboot back to recovery. (if not see below, it may be to do with your current twrp version)
11. BACKUP EVERYTHING to EXTERNAL SDCARD (this will save partition info, boot/userdata/system). If super keen, transfer a copy to computer
12. Okay now the partitioning
- Go to wipe
- Go to advanced wipe
- click on cache
- click on repair or change file system
- click on change file system
- click on F2FS
- swipe to confirm
- click back till you get to the partition selection again
- Repeat step 12 changing 'cache' for 'data' and then for 'system'
13. Go back to the main menu
14. Flash ROM zip, Gapps and Super Su
15. Reboot
Optionals
16. Download a free app called 'disk info' from play store
17. check your partitions are now listed as F2FS. if they list as EXT4, you've done something wrong and need to try it again.
QUICK FAQ
Is this safe?
Yes, provided you do it correctly you wont have any issues.
Do it need to do it each time I flash my ROM?
No, you only need to convert once. Then each ROM flash will see your partitions as F2FS and format accordingly.
But I know the device formats system or other partitions during ROM flash, why do I have to do it manually?
Because the ROM zip detects the partition file system type. It will then format it with the correct tool. If you don't essentially set the file system to F2FS how does it know to format with F2FS.
Does my favourite kernel support F2FS?
probably not, check with the developer and ask them to support F2FS. If they are stuck, point them in my direction I will help.
I followed the steps correctly and get a black screen after booting?
You have probably messed something up, this seems to be kernel related. If you tried to flash a custom kernel, don't. Use only the bundled kernel until you know your favourite custom kernel supports f2fs.
Can I have some partitions as EXT4 and some as F2FS?
Probably, but I don't recommend it. Don't half complete this mod, either go full F2FS or remain at EXT4.
What about other partitions I see/know about? Can these be F2FS too?
No, they are not supported
Only System, Data (userdata) and Cache are supported, these are the typical partitions supported by other ROM devs for other devices.
So I don't have a recovery, or when I reboot to recovery it goes straight to the ROM, or I just get a blank screen?
Your recovery isn't working or didn't flash correctly. Your going to have to flash TWRP 2.8.6.0 with ODIN and try the steps again (I've tested 2.8.6.0 with the F2FS supported IMG and the ZIP file and both work)
I don't like/want F2FS can I go back?
Yes, follow the steps once again and where it says F2FS in step 12, change it to EXT4.
Can I revert to an old backup, but it was before I changed to F2FS?
Yes you can, but FIRST you MUST re-partition back to EXT4 before restoring your old backup. If that means using an older TWRP (not mine) it will still format your device back to EXT4, just do it BEFORE you restore.
Can I just restore a backup of F2FS?
Yes, but see the above ^^^ you will need to format to F2FS before restoring.
Will EXT4 still be supported?
Yes
Is F2FS better?
Not really sure, I haven't had enough time to play with it. It doesn't feel much 'faster' maybe im just being cynical lol.
I really broke/bricked my device, HELP?
if you have a stock firmware your best solution is to flash that with Odin.
Where's your TWRP source?
here - https://github.com/Joshndroid/androi...ung_lt03wifiue
Can I build my own TWRP?
Yes, but you need omnirom source so its not really worth doing it.

Google Shares
Rules -
1. I WILL NOT be keeping your PM or your email address anywhere once you have been added to the share, i WILL be respecting privacy so I expect the same in return.
2. I WILL however, be creating a google doc (probably in each rom folder) to signify by XDA username only who is in the share. (This is for a couple reasons, 1 - because I can keep track of who I have added to the share, 2 - people can see if they have been added or not to the share to either remind, 3 - It keeps people accountable when their, somewhat, online identity is linked to something.)
3. Do NOT spam me with PM's if I dont get to add you within a day. I am very active on the forums due to mobile access, but to add to the share I will need to be at home. If you have not been added and see your username in the google doc after 2 days, politely PM me again.
4. If you do not use the below template (as it has all the information I will be requiring on my end to add you), You wont be added (so 2 days will pass, you wont see your name or a rom and then check the info u sent me).
5. First download for yourself is going to be rather big (about 4 roms worth). I want to keep atleast a couple roms in the share so that if something is wrong, I can pull a download or whatever at it will not affect anything to severely.
6. You will not have any access to modify or delete the files. I am the owner and you guys will only be able to download/view (which is all you need).
Okay so how can you let me know your in.
First PM me using this template:
XDA Username -
Email (google drive account) -
Rom -
Devices (some have more than one) -
I will add you to the share, I will add you to the local google doc, you will get a device folder and your files will start to sync locally to your PC.
Couple quick FAQ's
How do you know when a new rom is on the share?
You could check it manually, I also was toying with a solution that I could share within the drive that would conduct periodic checks, problem is is that it would rely on a generated file as well as direct links (something that is hard to come by on file sharing services to firstly predict and script & usually requires you to manually click a share button to get a link).
However, there is a google chrome based extention that will notify you by tracking a folder when something new has been added to a google drive folder - https://chrome.google.com/webstore/detail/folder-notifications-for/pamfobflonhoblkekglgpplpibfnckna
This will only track and send an email based on tracking 1 folder.
I am looking into the paid version myself ($2 - http://ez34.net/ezdrive/folder-notif) that will track 10 folders (which is a lot).
Can I get roms from the other locations?
Yes. I have done this setup to quicken my workflow to get roms out, the quicker you guys get them, the happier you's are. Now the primary issue I have it sync'ing to other file services to ensure I limit my bandwidth in uploading (to reduce wait times) and to keep things concurrent across. If i upload to google drive first and sync to other locations on my end, its quicker than me manually uploading to locations.
Remember the first few days I will be spammed with PM's to add everyone who wants to join, I may be a bit slow. But once that is out of the way it will be back to usual and we will then see the benefit of it. I am big on automation, the more I can automate, including checks and failsafes, the more we become something like can be provided by big rom providers.

so;
why did i make a new thread?
Well, i was tired of spamming the other thread that is of a nightly status with these unofficial builds. I pretty much run these builds each time i run a temasek build so they will be frequent enough.
Why havnt you just submitted to CM your the maintainer?
Well, everything is not fixed yet i have been looking at the camera and once that is fixed will probably submit it for nightly status for cm-13.0
what will happen then?
This will be the main thread for cm-13.0 as it continues on, through these unofficial builds and hopefully on to nightlies once the camera is done.
what about android N?
Waaaaaaaay to early to speculate about that yet.
Anything different to base cm-13.0?
Slightly, as the rom is built using UBERTC 4.9 for the rom, the kernel specifially is untouched (unlike temasek builds)

New build March 10 2016 is up on basketbuild and google shares... cheers
Further for some rom updates whatever/follow me on twitter (DW i don't spam) - @joshndroid

Thanks you for the ROM!
This is This is stable or beta or testing? Thanks

Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?

TruThug407 said:
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
Click to expand...
Click to collapse
I prefer to use the temasek build, because of the temasek settings and the omniswitch support, but i think both releases are stable.

TruThug407 said:
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
Click to expand...
Click to collapse
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom

joshndroid said:
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
Click to expand...
Click to collapse
Thanks bruh just makin sure....

joshndroid said:
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
Click to expand...
Click to collapse
Are you planning to keep maintaining the updates on both? I currently have your Temasek version but if you are looking to focus your time on this one then I'll switch

Sy Borg said:
Are you planning to keep maintaining the updates on both? I currently have your Temasek version but if you are looking to focus your time on this one then I'll switch
Click to expand...
Click to collapse
Temasek is his main project so it will get updated more often than dis one I think he started dis one to get it goin to nightly once da camera is fixed....

Gapps for temasek cm13 - difficulty
I flashed the temasek cm13 to my 600. Works cool, except I can't find a gapps 6.0 package that works. Every time I flash the gapps, I get two errors that take over the tablet: "unfortunately setup wizard has stopped" and "unfortunately google play services has stopped." I've tried the recommended gapps here, and the a-gapps package.
Any ideas on getting gapps to work here? Any other recommended gapps packages?
Thanx in advance...
...joe

jaypea500 said:
I flashed the temasek cm13 to my 600. Works cool, except I can't find a gapps 6.0 package that works. Every time I flash the gapps, I get two errors that take over the tablet: "unfortunately setup wizard has stopped" and "unfortunately google play services has stopped." I've tried the recommended gapps here, and the a-gapps package.
Any ideas on getting gapps to work here? Any other recommended gapps packages?
Thanx in advance...
...joe
Click to expand...
Click to collapse
Bro I have a perfectly fine gapps package linked in second post (opengapps.org)...
These packages work fine for 7 devices I use.

yeah, I fixed it. it wasn't the gapps package. I keep forgetting that when flashing a new rom you need to immediately flash gapps without rebooting in between. the older I get, the more drips out of my colander-brain...

New build 18032016 is up on basketbuild and Google shares

Preparing SD card causes black screen
I had a drop down when said a new sd card had been detected. I could either use it for photos or make it non removable (guess that means Linux format). I requested the sd card be configured and not make removable. I got an instant black screen, which i left over night , the tablet was no longer frozen but the partition table on the sdcard was corrupt.
Any ideas how to get this to work ?

XDAdeveloperHTC said:
I had a drop down when said a new sd card had been detected. I could either use it for photos or make it non removable (guess that means Linux format). I requested the sd card be configured and not make removable. I got an instant black screen, which i left over night , the tablet was no longer frozen but the partition table on the sdcard was corrupt.
Any ideas how to get this to work ?
Click to expand...
Click to collapse
Don't use that... Just use it as external storage.

drm problem
Hi,
i've installed the latest version and get a DRM Error. DRM Widevine is missing...
Thx for a reply
JMF

[ROM] [UNOFFICIAL] LineageOS 13.0 for the M.O.J.O.

{
"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 13 is a free, community built, aftermarket firmware distribution of Android 6.0.1 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Changelog:
Code:
[20180127]:
Improved powerHAL, fix hdmi audio issue and new libbt-vendor.
[20180122]:
New powerHAL from molly, should give better cpu management.
New libAudio from molly: AudioFX now working!
[20180106]:
Added NTFS support, thanks to K-Project for issue repport
[20180105]:
Updated Proprietary blobs (mainly video driver) from Jide ultratablet (LMY47V 5.1.1)
Remove nvcpud (NVidia cpu speed daemon)
Some cleanup
[20180102]:
Some cpu tweaks
Added buttons (and navbar) config in settings
Updated bluetooth config thanks to carp_be
[20171228]:
Initial build
Instructions :
Download the latest build and gapps
Reboot to recovery (newest TWRP 3.2.1-0 prefered)
Go Wipe->Advanced->Select system,cache and data partition (not required if coming from previous version)
Flash the latest build and gapps (gapps not required if coming from previous version)
Reboot
Downloads :
Builds : Google Drive folder Choose the latest
Root addon : https://download.lineageos.org/extras Required for full root! Without it you'll only have adb root, that's how LineageOS is made
Google Apps : http://opengapps.org/
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console_ramoops. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Working:
Allmost all, including Google WideVine and Microsoft DxDrm. Android System WebView installation is mandatory to avoid issues like bootloop when installing apps that use drm.
Not working:
AudioFx
XDA:DevDB Information
LineageOS 13.0 for the M.O.J.O., ROM for the Mad Catz M.O.J.O.
Contributors
nono2lozere, Unjustified Dev, carp_be
Source Code: https://github.com/nono2lozere
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Testing
Current Beta Version: 13.0
Beta Release Date: 2017-12-28
Created 2017-12-28
Last Updated 2018-01-27

Wowzers, you really did it! Thanks for putting some life into this marvellous device (or trying to anyway)!
Anyway, I've installed it. I used the older TWRP 2.8.2.0. Not sure if I need to be using something more recent now, but it worked.
Code:
What is your--
LineageOS version: 13
LineageOS Download: https://drive.google.com/open?id=1NJCHZo58BnZIyELYBqlx-0Fy61uBWCAO
Gapps version: open_gapps-arm-6.0-nano-20171228
Did you--
wipe: YES
restore with titanium backup: NO
reboot after having the issue: NO
Installed nicely and with no upset. It takes a while on first boot for those of you giving this a go, so allow a moment or two while it gets things together.
Got to say I am very impressed. It's Lineage 13! On the MOJO! Yes AudioFX doesn't work as you say, but it seems the rest does! However, I'm having a couple of issues you may be able to help with. Firstly, I tried rooting the device in the same way I did CM 12.1, basically by going into developer options and selecting root access. However, there's only an option to root via ADB, no apps access. Is this intentional? I was unable to install my quick reboot app meaning one has to hard shut down (i.e. pull the plug) on the device which is never an elegant way to do things. What is the best solution to root this please? Many thanks.
I also notice that when trying to use a browser, be it Firefox or Chrome, to download something it gives you an error. I tried to download a simple file and Firefox just failed, but luckily Chrome was a bit more verbose and explains why. It said it did not have access to the internal storage despite me confirming all the options after installing it. Not sure what's happening here.
Other than these things, at this early stage the only other thing I noticed was some tearing of the screen on animated transitions. Occasionally it seems to pull and break up a bit when whipping around.
I think I speak for everyone here when I say - THANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOU!!! I look forward to further adventures with this ROM!

K-Project said:
Wowzers, you really did it! Thanks for putting some life into this marvellous device (or trying to anyway)!
Anyway, I've installed it. I used the older TWRP 2.8.2.0. Not sure if I need to be using something more recent now, but it worked.
Code:
What is your--
LineageOS version: 13
LineageOS Download: https://drive.google.com/open?id=1NJCHZo58BnZIyELYBqlx-0Fy61uBWCAO
Gapps version: open_gapps-arm-6.0-nano-20171228
Did you--
wipe: YES
restore with titanium backup: NO
reboot after having the issue: NO
Installed nicely and with no upset. It takes a while on first boot for those of you giving this a go, so allow a moment or two while it gets things together.
Got to say I am very impressed. It's Lineage 13! On the MOJO! Yes AudioFX doesn't work as you say, but it seems the rest does! However, I'm having a couple of issues you may be able to help with. Firstly, I tried rooting the device in the same way I did CM 12.1, basically by going into developer options and selecting root access. However, there's only an option to root via ADB, no apps access. Is this intentional? I was unable to install my quick reboot app meaning one has to hard shut down (i.e. pull the plug) on the device which is never an elegant way to do things. What is the best solution to root this please? Many thanks.
I also notice that when trying to use a browser, be it Firefox or Chrome, to download something it gives you an error. I tried to download a simple file and Firefox just failed, but luckily Chrome was a bit more verbose and explains why. It said it did not have access to the internal storage despite me confirming all the options after installing it. Not sure what's happening here.
Other than these things, at this early stage the only other thing I noticed was some tearing of the screen on animated transitions. Occasionally it seems to pull and break up a bit when whipping around.
I think I speak for everyone here when I say - THANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOU!!! I look forward to further adventures with this ROM!
Click to expand...
Click to collapse
I personaly use TWRP-2.8.7.0.
For full root you need to install root addon, it's how Lineage is made.
And try to reboot or force close chrome or firefox, sometimes it doesn't take permission at first launch, hope it works because I didn't try chrome.
Have you made an advanced wipe? because without format system the install script will backup some garbage of the previous rom witch can cause issue.

Thanks for replying.
Yes I did an advanced wipe. I wanted to be sure that this was cleanly done.
I'm not familiar at all with Lineage so I had no idea about root addons. I think I've found them now, so I'll reflash the device and post back later. Thanks for the heads up.
I didn't attempt to reboot either Chrome or Firefox so I'll give that another go too after the reflash.

Code:
What is your--
LineageOS version: 13
LineageOS Download: [url]https://drive.google.com/open?id=1NJCHZo58BnZIyELYBqlx-0Fy61uBWCAO[/url]
Gapps version: open_gapps-arm-6.0-pico-20171228
Did you--
wipe: YES FULL
restore with titanium backup: NO
reboot after having the issue: NO
Youtube works perfect (my "test" video plays) :highfive:
Still two other crashes is here View attachment 2017-12-28-20-39-36e.txt
Process ru.norgen.homevideo (pid 3189) has died
Process com.lolapp.lolapptv (pid 3527) has died
Nice work - looks very promissing

This is amazing , wow , thanks so much ,I will try it asap

Nice, next week I have again a good internet connection so I can sync the lineageos tree. I'll then will try to port androidTV

Very impressed with the WiFi so far. No issues that I've discovered, though of course this is an early stage. It works even when booting with an SD card in.
OK, so reflash... I switched to TWRP 2.8.7.0 as you said.
Following your reply I grabbed the Lineage AddonSu package that seemed relevant, but unfortunately this would not flash. It gave me an error message 4 and said there was a problem with the binary. I tried it twice but no luck. However, I had an older Super Su package I kept from a while ago (2.46) and flashed this. It worked fine and even updated from the Play Store OK. This allowed me to install and use the reboot app just fine. So I set about installing some apps.
As you stated, after a reboot of Firefox it downloads fine. Simply permit it access to your storage, and then close and reopen. This works.
I installed both Kodi and Retroarch but I am getting no sound at all. At first I thought I'd done something wrong in the settings for both apps and the device but it appears not. There's no sound at all. I will attempt a reboot again but it didn't work after a couple of reboots. Is this expected at this stage or is there something I need to do? Please let me know.
Anyway, my thanks again for a great update. I really hope you carry on the work and I look forward to continuing with this OS. I hope my posts are helping rather than causing any problem.
---------- Post added at 10:52 PM ---------- Previous post was at 10:47 PM ----------
Only other thing I noticed was the MOJO seems to get very warm and does seem to lag a little bit with the mouse after half an hour. I checked the memory usage and it seemed OK, so perhaps it's hammering the CPU? I dunno, but thought it worth mentioning to see if other folks notice the same thing.

awesome thanks for this

[Sorry for multiple posts]
Sound is back today. Not sure what happened but it's working fine. I've decided to just set everything up as I normally have it and really see how it goes. So far everything seems to be working as it should.
Awesome!
However, I am definitely experiencing some lag once the device has been on for some time. I've been playing with the MOJO all morning and there's definitely screen tearing and some lagginess in transitions over time. It seems better after a reboot, but it's not long before it creeps back in again. I'll be curious to see if anyone else has this issue.

K-Project said:
Very impressed with the WiFi so far. No issues that I've discovered, though of course this is an early stage. It works even when booting with an SD card in.
OK, so reflash... I switched to TWRP 2.8.7.0 as you said.
Following your reply I grabbed the Lineage AddonSu package that seemed relevant, but unfortunately this would not flash. It gave me an error message 4 and said there was a problem with the binary. I tried it twice but no luck. However, I had an older Super Su package I kept from a while ago (2.46) and flashed this. It worked fine and even updated from the Play Store OK. This allowed me to install and use the reboot app just fine. So I set about installing some apps.
---------- Post added at 10:52 PM ---------- Previous post was at 10:47 PM ----------
[/COLOR]Only other thing I noticed was the MOJO seems to get very warm and does seem to lag a little bit with the mouse after half an hour. I checked the memory usage and it seemed OK, so perhaps it's hammering the CPU? I dunno, but thought it worth mentioning to see if other folks notice the same thing.
Click to expand...
Click to collapse
I havn't seen su addon issue before because I havn't try it yet! the issue is in twrp, so I have two option: make a compatible addon or a new twrp recovery.
I'm going for the new twrp solution because it will also allow Lineage 14.1 install if i want to try it.
For the lags I need to check clocking parameters, maybe they are wrong.

nono2lozere said:
I havn't seen su addon issue before because I havn't try it yet! the issue is in twrp, so I have two option: make a compatible addon or a new twrp recovery.
I'm going for the new twrp solution because it will also allow Lineage 14.1 install if i want to try it.
For the lags I need to check clocking parameters, maybe they are wrong.
Click to expand...
Click to collapse
I was testing with TWRP 2.8.2 and addonsu-13.0-arm-signed.zip - everything was fine.
Only Lineage SU was forgetting "allow" after reboot...
P.S. TWRP 2.8.7 was doing something wrong with CM builds or OpenGapps or SuperSU installation - only don't remember what... Now long time sitting on 2.8.2 - everything OK :angel:

nono2lozere said:
I havn't seen su addon issue before because I havn't try it yet! the issue is in twrp, so I have two option: make a compatible addon or a new twrp recovery.
I'm going for the new twrp solution because it will also allow Lineage 14.1 install if i want to try it.
For the lags I need to check clocking parameters, maybe they are wrong.
Click to expand...
Click to collapse
Not sure if there's a better way to check CPU, but I notice when using KODI it runs at 100% all the time. I use an external drive with my media files, and while they would play you could tell it was struggling. Lots of stutter, despite changing the settings etc.
rahsoft said:
I was testing with TWRP 2.8.2 and addonsu-13.0-arm-signed.zip - everything was fine.
Only Lineage SU was forgetting "allow" after reboot...
P.S. TWRP 2.8.7 was doing something wrong with CM builds or OpenGapps or SuperSU installation - only don't remember what... Now long time sitting on 2.8.2 - everything OK :angel:
Click to expand...
Click to collapse
I'd be curious to know what the difference is. Like I say, I ended up using TWRP 2.8.7.0-mojo and then flashed the older SuperSu 2.46 zip. This seems to work and has done the job, but I wonder if it there's an incompatibility that is causing my lag issues...?

Don't know if anyone can help here. Installed this and it just upgraded my CM 12.0 I had installed.
I lost root so couldn't boot back into recovery using an app.
I went to boot into recovery using PC and a male to male (which I did originally when flashing CM 12.0 but it just sends me to a boot loop with the liniage os intro scene.
If I boot again normally I get back to Lineage OS. Problem is I wanted to install this as all my apps were crashing constantly after a year of no issues (with CM12).
They're still crashing with Lineage OS but I can't get it to recovery mode for a fresh install.

TrentLane said:
Don't know if anyone can help here. Installed this and it just upgraded my CM 12.0 I had installed.
I lost root so couldn't boot back into recovery using an app.
I went to boot into recovery using PC and a male to male (which I did originally when flashing CM 12.0 but it just sends me to a boot loop with the liniage os intro scene.
If I boot again normally I get back to Lineage OS. Problem is I wanted to install this as all my apps were crashing constantly after a year of no issues (with CM12).
They're still crashing with Lineage OS but I can't get it to recovery mode for a fresh install.
Click to expand...
Click to collapse
Are you sure you've plugged the male-to-male USB cable into the right slot? It has to be in the USB2 one or the MOJO will continue to boot as normal. I know this as I did exactly the same thing very recently. Plug your mouse into the blue USB3 slot instead.
You cannot brick the MOJO unless the hardware has failed. It can always be rescued by connecting it to a PC/laptop and reflashing TWRP then ROM etc. I posted here not so long ago that my MOJO suddenly and for no real reason decided to plunge into a bootloop just as it was installing some simple updates from the Play store. It had been absolutely fine for nearly two years. Nevertheless I was able to connect it to the laptop and reflash and run TWRP. There I completely erased the device and installed Lineage 13 as the timing couldn't have been more perfect.

TrentLane said:
Installed this and it just upgraded my CM 12.0 I had installed.
Click to expand...
Click to collapse
Wait... so can I upgrade from CM 12.1 without losing anything?!

EdoNINJA93 said:
Wait... so can I upgrade from CM 12.1 without losing anything?!
Click to expand...
Click to collapse
don't think so
Instructions :
Download the latest build and gapps
Reboot to recovery
Go Wipe->Advanced->Select system,cache and data partition
Flash the latest build and gapps
Reboot
Click to expand...
Click to collapse

Wmapa said:
don't think so
Click to expand...
Click to collapse
It would have been too good to be true...
From his message it seemed that all the apps remained untouched... :/

EdoNINJA93 said:
Wait... so can I upgrade from CM 12.1 without losing anything?!
Click to expand...
Click to collapse
You can try but make a backup before, I don't know if it's possible.

First post updated.
Enjoy new build!

[ROM][10.0]BETA[PORTED][UNOFFICIAL] Havoc 3.0 [UGGLITE] V2 2019-12-06

HAVOC 3.0 ROM V2 2019-12-06
Project ended.
This is BETA version, USE STABLE crDroid or GoogleDroid ROMs.
Your warranty is now void.
There's no guarantee, don't use it if you don't know what you're doing!
Android quota removed. (Easy back 7.x-9.x ROMs)
Make sure you have a custom recovery installed (TWRP (or clones) is the preferred recovery) My TWRP: LINK
Boot into recovery
Wipe dalvik, system, data, cust (vendor), cache partitions
If your /data partition secured, maybe need format /data.
Flash Rom (sideload or copy SD)
Flash Google Apps package (Optional) LINK
Flash Magisk Root (Optional) LINK
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 40 sec to 1 minutes.
Boot time 30 sec.
There are many tiny, unpleasant bugs in Havoc system, NOT recommended for daily use, maybe just for fanatics.
DOWNLOAD V2 ROMDon't need wipe data if upgrade previous Havoc 3.
NEW: FM radio fixer LINK (If not working FM radio, install this fixer in TWRP)
NEW: dt2w fixed : LINK (Install in TWRP.)
V2 Changelog:
Power off (offline) charging bug fixed
Some camera bug fixed
Many system bug fixed
Energy consumption is very good
The Android system seems stable and fast (Havoc Os not so much )
Know bugs: - no double touch wake up (?)
- FM radio
- power off charge
Update: I found some permission issues.
I'm trying to fix it.
The camera app does not save images to the SD card...
Gallery Go does not handle SD card properly...
They don't even ask for permission...
Workaround: USE INTERNAL STORAGE for photography, and sometimes move images to SD.
*
Screenshots: LINK
ROM source xda: LINK
Havoc-OS source: LINK
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.x
ROM info: mido OFFICIAL port, Q10 system_root partition
Created 2019-11-26 V0 version
Last Updated 2019-12-06 to V2 version

It looks like I have solved two serious problems.
(dex2oat didn't work and neither did ashmem)
The system boot is twice as fast, etc.
I soon publish the new ROM.
Upgrade Out. More stable, fast.

Reboots into fastboot mode
My device automatically reboots into fastboot mode after I flashed this.
---------- Post added at 09:48 AM ---------- Previous post was at 09:45 AM ----------
I am using pixel experience ROM currently. When I flashed this my device end up in bootloop. Do I have to be in miui for installing this..??

Redminote5a8 said:
My device automatically reboots into fastboot mode after I flashed this.
I am using pixel experience ROM currently. When I flashed this my device end up in bootloop. Do I have to be in miui for installing this..??
Click to expand...
Click to collapse
Thank you your response, ROM V1 fixed, downloadable.
(The system partition on my phone was slightly disintegrated, I had to fix it.)
Pixel E. ROM is on 4PDA, downloadable.
Use a suitable TWRP, pls.

If anybody have downloaded V1, delete it because it is defective.
ROM named *V1fix.img works.
Sorry. I apologize for the inconvenience.

Hahaha, the camera bug very funny: LINK
The camera app save images to folder: sdcard - /Android/data/org.lineageos.snap/files
Thnx ****ing org.lineageos.snap app, and i suck...

offline charging bug

Hafitz Setya said:
offline charging bug
Click to expand...
Click to collapse
Thank you your responde, i know this bug, i will deal with it, i hope soon.

HAVOC 3.0 ROM V2 2019-12-06
V2 out.

I ended this job for the time being here, I don't got much feedback and thnx (respect the exceptions), and a lot of time goes with it. Sry, bye.

that is a great work
hey szanalmas we all on ugglite telegram appreciate your hard and excellent work for bringing stable Q to ugglite
thanks is few for you on Xda beacuse almost ugglite useres are on telegram groupe
they all ask you to join the group on telegram
:good::good::good::good:

szanalmas said:
I ended this job for the time being here, I don't got much feedback and thnx (respect the exceptions), and a lot of time goes with it. Sry, bye.
Click to expand...
Click to collapse
i told u to use telegram, people most activates in therre they report bug in telegram

FM radio fixer out. LINK

Dt2w fixer placed out.
According to Hafitz Setya, he also works with the my dt2w fixer on Havoc OS. Use it gladly: LINK (Install in TWRP.)

Is this rom work in ugg?

szanalmas said:
Dt2w fixer placed out.
According to Hafitz Setya, he also works with the my dt2w fixer on Havoc OS. Use it gladly: LINK (Install in TWRP.)
Click to expand...
Click to collapse
It don't work. Only for ambition display. Rom is good, but sometimes slowly. Not work gestures If someone can fix it, I will be happy.. Bluetooth works unstable

Manager_of_Gulag said:
It don't work. Only for ambition display. Rom is good, but sometimes slowly. Not work gestures If someone can fix it, I will be happy.. Bluetooth works unstable
Click to expand...
Click to collapse
Try execute 10goodix & turn on emulate init.d in kernel adiutor and reboot and turn off this
Sent from my Xiaomi Redmi Note 5A using XDA Labs

Manager_of_Gulag said:
It don't work. Only for ambition display. Rom is good, but sometimes slowly. Not work gestures If someone can fix it, I will be happy.. Bluetooth works unstable
Click to expand...
Click to collapse
1. workaround dt2w: download Ravenge OS (TWRP save) and restore ONLY VENDOR. I integrated dt2w to vendor, but only for PE and subsequent ROMs.
2. workaround (full ROM installer): change the vendor.transfer.list and vendor.new.dat.br files from PixelE to HavocOS (or Arrows, or crDroid) in to the installer zip file. After no need patch for dt2w. Only copy two files to ROM installer zip file.
If you want dt2w, you have to disable the double tap on ambient display because two identical functions cannot be interpreted at the same time.
Dt2w will be good in every new ROM.
I have already stated that Official ROM development is chaotic.
The Havoc bug to this day:
- no flashing LED for missed calls
- Doesn't work with two buttons navigation back sweeping
- there is a problem with the bluetooth call
- applications are chaotic and inconsistent, with each developer trying their own solutions
- etc
- developers do not receive meaningful feedback
The situation is similar for all AOSP-based ROMs, which may be due to the lack of an official Lineage 17.
Google ****ed up sd card permissions.
I don't know when a stable AOSP ROM will be available, just wait now...

Hey.
After flashing the system asks for a password ??
What the hell?

Repixel said:
Hey.
After flashing the system asks for a password ??
What the hell?
Click to expand...
Click to collapse
1. If your phone data was encrypted, you may need to format the data partition. Save all your data first.
2. If a quota was applied to the data partition, it must be removed or formatted.
To remove a quota from TWRP:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
(If you then install a ROM that uses a quota, you will need to uninstall it again to use the quota-free ROM.)
3. Or, put the previous ROM from your backup on your phone and keep using it.

[ROM][UNOFFICIAL][9] LineageOS4Microg 16.0 (by Bernie_nix)

Rom Built by Bernie_nixKnown issues:
USB-C headphones work for music, watching videos, etc. They don't work in the phone app...yet. (working on this)
Some users report VOIP calls don't work properly. YMMV. Skype, Whatsapp, Nextcloud Talk, working great for me.
Automatic updates not yet implemented but will be in a future build.
You tell me.
Install Instructions(If coming from stock or another rom):
Prerequisites: Coming from stock rom with bootloader unlocked, Developer settings enabled, android debugging enabled.
(1) ADB reboot bootloader,
(2) Fastboot boot twrp.img
(3) Install copy A/B partitions zip,
(4) Select Wipe button, Advanced Wipe, Choose: Dalvik/ART Cache, Data, Internal Storage, System. Then Swipe to Wipe all of these.
(5) Select Back arrow button
(6) Select Format Data Button. Type yes
(7) Select Install button. Choose rom zip. Swipe to confirm flash.
(8) Press back arrow button 2x to get back to main screen. Select Wipe button. Select format data button. Type yes.
(9) Reboot. Phone will mention "no os installed." Ignore it. Proceed with reboot. Phone will boot twice, then take you to the lineage recovery screen. Use volume down button to select Factory data reset, press power button, select yes to delete data. Phone will reboot into lineageos4microg.
DO NOT install twrp installer/orange fox installer until after phone boots into lineageos4microg or it will not boot. After you have setup lineageos, you can then reboot into twrp and install orange fox or twrp and magisk if you choose. Do not ever install any GAPPS on this ROM.
Upgrade Instructions(If coming from one of my previous builds):
(1) ADB reboot bootloader,
(2) Fastboot boot twrp.img
(3) Select Install button. Choose rom zip. Swipe to confirm flash.
(4) Select Wipe button, Advanced Wipe, Choose: Dalvik/ART Cache
(5) Reboot(6) If you had Magisk installed, you can then reboot into TWRP/Ofox and flash magisk.zip
Tips for Use
1. Root can be enabled in this build by going to Developer Settings->Root Access->Apps and ADB
2. To turn off battery led when charging, Settings>Apps & notifications>Notifications>Battery Light
3. To set up Microg,
(1) open MicroG app,
(2) press self-check, press battery optimizations ignored and allow,
(3) go back one screen, select unified nlp settings, configure location backends, press the checkbox next to mozilla location service and ok, configure address lookup backends, press checkbox next to nominatum and ok,
(4) then go through Google services from top to bottom and enter your information.
(5) Enable location from pull-down shade. Open maps, get your location. Go back to Microg. Run self-check. All boxes should show a check.
(6) Microg is setup in less than 5 minutes and fully working.
(7) Turn off location from pull-down shade bc they're tracking you 4. Want a better GPS experience? Install Deja Vu Location Service, GSM Location Service and Radiocells.org Unified Network Location Provider Backend from F-Droid. Works great with Google Maps or OSM.
5. Looking for a great camera? Try Hypercam for Moto G7 from gcambrasil at https://gcambrasil.com.br/motorola
1. After installing, go to internal storage, create folder "gcam" (without quotes), create folder "Configs" inside of "gcam," and place the Pixelmod_byJGB.xml (attached) file in that folder.
2. Open up Hypercam, double tap on black space near camera button, load Pixelmod_byJGB.xml file.
Reporting bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed.
Please report bugs in this thread.
Logcats are helpful but not required. Grab a full logcat right after the problem has occurred.
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Thread Purpose & LimitsThis thread has been created to discuss the installation and use of this rom. If you have questions about building roms, this thread is not the place to do it. Please create a thread under Q/A and/or visit the Telegram group https://t.me/mG7Power. I'm happy to help but going to the telegram group or opening a Q/A thread allows many users to assist you and will help to keep this thread on-topic. Failure to follow this request will result in a warning followed by report to XDA if continued. Some excellent resources for building microg include https://lineage.microg.org/ and https://8192.one/post/lineage_build_with_docker/.
Download:
Change log
1. Latest March security update
Status: Stable
ROM OS Version: 9.x Pie
Android Security Patch Level: Mar. 5, 2020
Download link: https://www.androidfilehost.com/?fid=4349826312261741637
MD5: 54b467570f65ce85f164bd8e99943ab7
Older Versions:
Change log
1. Latest sources
2. Root option enabled in development settings
Status: Stable
ROM OS Version: 9.x Pie
Android Security Patch Level: Feb. 5, 2020
Download link: https://androidfilehost.com/?fid=4349826312261727435
MD5: aeb4aa1141c6d74ac016e8fba797c245
Next update news...:
Mar 10, 2020 - Currently working on USB-C audio during phone calls, increasing audio volume. Once USB-C audio gets fixed, I'll enable OTA updates.
Source and Additional Links
https://github.com/LineageOS
https://github.com/LineageOS/android...otorola_sdm632
Telegram group for additional ROMS, files and support: https://t.me/mG7Power
Rom Last Updated Mar. 10, 2020
Thread Info Last Updated Mar. 10, 2020
Guide on how to build your own posted here: https://forum.xda-developers.com/g7...d-lineageos4microg-16-0-t4070079#post82069641

hi im really interested in this rom but If twrp is already my permanent recovery, this rom won't install correctly?
edit.. tried it anyway since this is a secondary phone, figured i didnt have much to lose, followed instructions to the TEE, and it installed just fine.

clarkkentxda said:
hi im really interested in this rom but If twrp is already my permanent recovery, this rom won't install correctly?
edit.. tried it anyway since this is a secondary phone, figured i didnt have much to lose, followed instructions to the TEE, and it installed just fine.
Click to expand...
Click to collapse
I should have another update with OTA server and a few other fixes soon. It's also super quick to update from current build. Stay tuned and enjoy!

Bernie_nix said:
I should have another update with OTA server and a few other fixes soon. It's also super quick to update from current build. Stay tuned and enjoy!
Click to expand...
Click to collapse
Thanks for your efforts, I've been enjoying it, it's hard to find a rom that offers a little privacy from google, most things are working just fine, one thing I've noticed is that video is super super dark, No matter if it's stock camera or open camera but that's all I've came across in the issues department so far

clarkkentxda said:
Thanks for your efforts, I've been enjoying it, it's hard to find a rom that offers a little privacy from google, most things are working just fine, one thing I've noticed is that video is super super dark, No matter if it's stock camera or open camera but that's all I've came across in the issues department so far
Click to expand...
Click to collapse
Thanks for your feedback! No problems with video if using a different app. Try Hypercam version 1.3.030119.0645build-6.1.021

Bernie_nix said:
Thanks for your feedback! No problems with video if using a different app. Try Hypercam version 1.3.030119.0645build-6.1.021
Click to expand...
Click to collapse
Hypercam works like a charm, thank you for the suggestion! does hyper cam rely on anything google related like services or frameworks or binarys? (not sure what to call it since im not a developer) i'm wondering because I own a pixel 3a and im thinking of installing graphene os but any apps that rely on those ran on those will not work on graphene

clarkkentxda said:
Hypercam works like a charm, thank you for the suggestion! does hyper cam rely on anything google related like services or frameworks or binarys? (not sure what to call it since im not a developer) i'm wondering because I own a pixel 3a and im thinking of installing graphene os but any apps that rely on those ran on those will not work on graphene
Click to expand...
Click to collapse
Hypercam is ported from gcam so YMMV. Given that it works on this ROM with microg, if it has any hooks they probably aren't deep. I'd give it a go

I've been a user of root explorer (pro) for seven+ years or so now. I side loaded the apk that I extracted from a previous setup on my phone and it works perfect. Some may already know that but just figured I'd share. Awesome job on this rom! Appreciate you sharing your builds!! :good:

flash713 said:
I've been a user of root explorer (pro) for seven+ years or so now. I side loaded the apk that I extracted from a previous setup on my phone and it works perfect. Some may already know that but just figured I'd share. Awesome job on this rom! Appreciate you sharing your builds!! :good:
Click to expand...
Click to collapse
Glad you like it and thanks for your feedback; tip on root explorer pro.

Bernie_nix said:
Glad you like it and thanks for your feedback; tip on root explorer pro.
Click to expand...
Click to collapse
Couple questions.. What busy box are you using and where did you get it? I've been using Osmosis’s magisk module busy box for so long idk where to even begin. haha. I attempted to install one from fdroid but it failed install. Can I flash his busy box in recovery? Probably not because we are using the LOS built in root instead of magisk correct? Would all hell break loose if I flashed magisk root now and something would possibly get messed up? Thinking if that's what I wanted I would have had to flash it in the beginning so it would over ride the other root...?
This rom runs better than anything besides ugly stock moto on my device. I was off work yesterday so I started messing with my device, hours went by and my battery barely moved at all. Not having Google play services really saves a good bit of juice. Havoc has spoofing now too. I vote that it becomes mandatory for all roms to have signature spoofing. :victory: Should call it the ImNOtgoingback rom or something. I’ve used micro g and fdroid before on previous devices but never for as long as I've been using this. Im like a binge crackflasher nowadays instead -vs- back when Euroskank CM10 bacon was on and popping every morning at around 6am central time the world would all flash. One last thing.. Do you decrypt your data or leave it encrypted? Reason I ask is I was wondering what method you do or would do if you wanted to decrypt?
This rom really runs great! Anyone who hasn't tried this yet should!
Edit
Ps: I've used many great gcams but HyperCam is most definitely at the top of my list. It reminds me of the pictures my Pixel XL used to take. Awesome camera app! Thanks for recommending it and sharing links!

not being picky, but can we have a regular LOS build please? I mean, without microG.
The last syberhexen one is dated 2019-10-01 so it would be nice to have an update to it.

DanAlucard said:
not being picky, but can we have a regular LOS build please? I mean, without microG.
The last syberhexen one is dated 2019-10-01 so it would be nice to have an update to it.
Click to expand...
Click to collapse
You're right, but it's not easy to be a maintainer - and use your free time to resolve problems for others.
Maybe you should try to create your own build using code created by more advanced users synced with latest LineageOS repo.
If you're interested in that, here's an attached manifest file which would build working LineageOS 16.0 for ocean with February security patch - I'm using such one right now(built 3 days ago), but with microg. It's all possible thanks to LineageOS team and Dark98 (and many others) work, as you can see.
Good luck

robson_89 said:
You're right, but it's not easy to be a maintainer - and use your free time to resolve problems for others.
Maybe you should try to create your own build using code created by more advanced users synced with latest LineageOS repo.
If you're interested in that, here's an attached manifest file which would build working LineageOS 16.0 for ocean with February security patch - I'm using such one right now(built 3 days ago), but with microg. It's all possible thanks to LineageOS team and Dark98 (and many others) work, as you can see.
Good luck
Click to expand...
Click to collapse
Thanks a lot. Will have a look at it. Who knows, maybe I end up maintaining it

DanAlucard said:
Thanks a lot. Will have a look at it. Who knows, maybe I end up maintaining it
Click to expand...
Click to collapse
That would be great!
In the meantime, i've built and updated my LOS 16 as attached - forgot to add screenshot previously.

DanAlucard said:
not being picky, but can we have a regular LOS build please? I mean, without microG.
The last syberhexen one is dated 2019-10-01 so it would be nice to have an update to it.
Click to expand...
Click to collapse
Not from me. I build this for personal use, share it and have no interest in a vanilla los build. Robson is correct. Go with his build of you don't want microg.

flash713 said:
Couple questions.. What busy box are you using and where did you get it? I've been using Osmosis’s magisk module busy box for so long idk where to even begin. haha. I attempted to install one from fdroid but it failed install. Can I flash his busy box in recovery? Probably not because we are using the LOS built in root instead of magisk correct? Would all hell break loose if I flashed magisk root now and something would possibly get messed up? Thinking if that's what I wanted I would have had to flash it in the beginning so it would over ride the other root...?
This rom runs better than anything besides ugly stock moto on my device. I was off work yesterday so I started messing with my device, hours went by and my battery barely moved at all. Not having Google play services really saves a good bit of juice. Havoc has spoofing now too. I vote that it becomes mandatory for all roms to have signature spoofing. :victory: Should call it the ImNOtgoingback rom or something. I’ve used micro g and fdroid before on previous devices but never for as long as I've been using this. Im like a binge crackflasher nowadays instead -vs- back when Euroskank CM10 bacon was on and popping every morning at around 6am central time the world would all flash. One last thing.. Do you decrypt your data or leave it encrypted? Reason I ask is I was wondering what method you do or would do if you wanted to decrypt?
This rom really runs great! Anyone who hasn't tried this yet should!
Edit
Ps: I've used many great gcams but HyperCam is most definitely at the top of my list. It reminds me of the pictures my Pixel XL used to take. Awesome camera app! Thanks for recommending it and sharing links!
Click to expand...
Click to collapse
Thank you for your kind words! I use busybox from osmosis via magisk module; yes, I enjoy magisk on this rom. Busybox (osmosis) actually makes apps like Titanium Backup work great if you've purchased a non-Google play license file from them. This rom is my personal build that I uploaded to xda and shared, and I plan on maintaining it for some time. So...Magisk flashed via twrp/ofox works great, and so does busybox magisk.
+1 on your comment about Hypercam. Completely agree about hypercam. I've tested a lot on this device and of course am open to suggestions.
I will update this rom via the Lineageos patches, however, the Feb update hasn't been pushed yet so no new rom for now. I have isolated a few bugs, e.g. usb-c for calls and am working on OTA, however, I am going to release a surprise test build in the next couple of days (hopefully). It's building as we speak, and I will test before releasing. Stay tuned, and I look forward to yours and others feedback and questions.
P.S. I am a linux user and believe in the power of open-source. If you or others have any questions or comments, feel free to reach me via the telegram link in the 1st post; I usually answer a bit quicker there but also answer on here. Best wishes and thanks again!
P.S.S. Welcome Robson to our open-source team! If any of you are looking for a lineageos build without microg, check out his post a couple of posts above.

generally audio is lower quality than stock rom, it's not as loud and not as clear.

clarkkentxda said:
generally audio is lower quality than stock rom, it's not as loud and not as clear.
Click to expand...
Click to collapse
Did you try the audiofx app that is included?

Bernie_nix said:
Did you try the audiofx app that is included?
Click to expand...
Click to collapse
Indeed sir, it doesn't help all that much for me though.

rottenwheel said:
I accompany this sentiment. It happens with most Motorola Moto G devices I own and use: if kept with stock builds both camera and audio have a far better quality than custom ROMs do. Motorola engineers do hell of a job when working on their OEM firmware. It is a real shame yet not so far from reality that we need to take these tradeoffs to obtain better privacy.
An idea that comes to mind is for us to debloat the stock build, bake in microG and possibly update security patches as they come out. Motorola Moto G1 (falcon) has something alike with IDCrisis - https://forum.xda-developers.com/moto-g/development/rom-identity-crisis-6-t3324595
Thank you for the heads-up, though. I definitely love the audio on stock.
Click to expand...
Click to collapse
Unfortunately you can't do that with stock. Microg requires signature spoofing enabled in the ROM which is a patch applied when building a ROM. You could try patching stock to enable signature spoofing with a tool like Heystack but it most likely won't work on stock. Another route is using another ROM with signature spoofing support e.g. crdroid or omni, applying signature spoofing patch if necessary and then patching in twrp with something like nanodroid patcher.
That being said I am working through desired edits and bugs in this ROM but can't provide any ETAs. I encourage anyone with a bit of coding experience or interest to build their own and learn. Making changes to rom builds is not hard, just time consuming and unfortunately doesnt pay the bills...so its done in hobby time. I do plan on maintaining this ROM for some time though and will probably be on Pie longer than most users until 10 is ready; right now 10 has way too many bugs for me to use or build for daily driver material.

[ROM][UNOFFICIAL][matisse][millet] crDroid 6.27 (Discontinued)

{
"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"
}
https://crdroid.net/
crDroid is a LineageOS-based CustomRom.
This one is based on LOS 17.1.
Special Thanks to matteo0026, who is maintaining the device sources and TWRP.
Disclaimer
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions or a nuclear war that comes as a result of flashing this ROM. Please make also be sure that you have always a full backup ready. Best to use: Nandroid Backup via TWRP
Installation instructions :
Be sure to have installed the latest TWRP recovery (you can find it in downloads)
Download the latest build and GApps (ARM, 9.0, I advice pico package) and copy it to your external SD-Card
Make a full Backup of your Data and copy it to your external SD-Card or USB-OTG
Boot to recovery mode
Wipe > Advanced wipe > Select system, data, cache and dalvik/art cache (and, if you want to clean more, select even internal storage, which deletes all the content in /sdcard) and do swipe to wipe. Format /data. When it's finished go to home page
Install > select ROM zip file > swipe to flash and when it's finished go to home page
Do the same thing to flash GApps and Root (if needed)
Reboot > System
Update instructions :
Be sure to have installed latest TWRP build
Download the latest build
Boot to recovery mode
Install > select ROM zip file > swipe to flash and, when it's finished go to home page
Reboot > System
Known issues :
crDroid 5.12 (discontinued)
This ROM is discontinued because of not fixable bugs.
Matisse is working but better use 6.xx or 7.xx
All Millet Devices -> Camera is not working, no fix so far.
crDroid 6.xx
Camera is working at all Devices
Face Unlock is working at all Devices
Downloads :
crDroid 5.12 (discontinued)
matisse (10.1) devices: Androidfilehost, Mega
millet (8.0) devices: Androidfilehost, Mega
crDroid 6.xx
matisse (10.1) devices: Androidfilehost, Mega
millet (8.0) devices: Androidfilehost, Mega
Other Stuff
TWRP Recovery Matisse and Millet: XDA, Mega, Matisse, Millet
GApps: https://opengapps.org/ (ARM, 10)
Magisk: https://github.com/topjohnwu/Magisk
Contributors:
crazydrive22, matteo0026 and all the S3NEO devs that provided the base for developing Pie on Tab 4
Source Code:
https://github.com/lineageos for samsung msm8226 common device and kernel source, with some patches coming from Gerrit for device source
https://github.com/s3neo for matisse and millet and specific variants device and vendor source
Thread started at 2021-01-31
Thread updated at 2022-06-25

will test this rom on my smtt330nu millet wifi, on the weekend when i have some free time.

Love your work! It works perfect on my matissewifi! No known issues! Have a lot of thanks, crazydrive22!

New Builds with February Security Patch are online.
There's still no fix for the broken Camera at Millet-Devices.

thanks excellent ROM on sm-t530

.. regular updates! I like it!

crazydrive22 said:
New Builds with February Security Patch are online.
There's still no fix for the broken Camera at Millet-Devices.
Click to expand...
Click to collapse
HI Crazydrive22,
Just downloaded latest Feb update for MilletWifi.
This build has some major issues, same as original crROM Version.
1. When updating using dirty flash, or clean version. Using TWRP v3.4.0-4 millet version, Nandroid backup does backup, Boot partition that is Rooted with Magisk 20.4. Your Rom overwrites Boot partition. Therefore Magisk Root is removed, therefore needs to restored.
2. After flashing both crROM versions released in Jan and now Feb. Require latest version GAPPS Nano, to be reflashed again, to stop Google Play services, crashing every minute or so. Reflash Gapps fixed that , as well other random Google apps, also crashing continuously.
3. After finally getting things back to normal, on latest crROM Version, needed a couple of restarts, as Tab4 was slow to respond, to some apps to operate at normal speed, compared to Matteo's builds. I have been using for 12 months now.
4. Then found internal memory is running out of space. Had plenty of spare, before using this ROM. Needs more research to find cause. Originally did a Wipe then clean flash and reinstalled all 100 odd apps, via Google Cloud.
5. I restored previous Matteo, Jan 21 build Nandroid backup with same number apps, plenty of internal memory left.
6. Tried to install your LOS16 Dec build, to compare with Matteo version. Downloaded from both sources, listed above in Post 1. Zip file crashes each time.
Found I needed to repair it , to allow me to open it. That is why, TWRP flash failed.
I did MD5 compare, that passes each time. So I suggest you need to upload again, a recompiled LOS16 ROM.
7. I have been working with Matteo, to help solve the Millet version CAMERA issues, over the last few months. But Matteo, has run out of ideas, at the moment.
8. So I decided to try crROM build by you.
But sadly still got issues with saving photos, but video front and rear camera works.
Panorama works saving photos. But photo saving crashes Camera app, with same unknown message, same as Matteo's ROM.
SO I suggest you have a look at the issues mentioned, and keep trying to resolve the camera issues with Matteo.
Great work so far, thanks for your effort to add another ROM for these OLD Devices.
Hope that helps you with some feedback, I have found some minor issues, that I had managed to fix easily.
Cheers
BeeJ1109

BeeJ1109 said:
HI Crazydrive22,
Just downloaded latest Feb update for MilletWifi.
This build has some major issues, same as original crROM Version.
1. When updating using dirty flash, or clean version. Using TWRP v3.4.0-4 millet version, Nandroid backup does backup, Boot partition that is Rooted with Magisk 20.4. Your Rom overwrites Boot partition. Therefore Magisk Root is removed, therefore needs to restored.
2. After flashing both crROM versions released in Jan and now Feb. Require latest version GAPPS Nano, to be reflashed again, to stop Google Play services, crashing every minute or so. Reflash Gapps fixed that , as well other random Google apps, also crashing continuously.
3. After finally getting things back to normal, on latest crROM Version, needed a couple of restarts, as Tab4 was slow to respond, to some apps to operate at normal speed, compared to Matteo's builds. I have been using for 12 months now.
4. Then found internal memory is running out of space. Had plenty of spare, before using this ROM. Needs more research to find cause. Originally did a Wipe then clean flash and reinstalled all 100 odd apps, via Google Cloud.
5. I restored previous Matteo, Jan 21 build Nandroid backup with same number apps, plenty of internal memory left.
6. Tried to install your LOS16 Dec build, to compare with Matteo version. Downloaded from both sources, listed above in Post 1. Zip file crashes each time.
Found I needed to repair it , to allow me to open it. That is why, TWRP flash failed.
I did MD5 compare, that passes each time. So I suggest you need to upload again, a recompiled LOS16 ROM.
7. I have been working with Matteo, to help solve the Millet version CAMERA issues, over the last few months. But Matteo, has run out of ideas, at the moment.
8. So I decided to try crROM build by you.
But sadly still got issues with saving photos, but video front and rear camera works.
Panorama works saving photos. But photo saving crashes Camera app, with same unknown message, same as Matteo's ROM.
SO I suggest you have a look at the issues mentioned, and keep trying to resolve the camera issues with Matteo.
Great work so far, thanks for your effort to add another ROM for these OLD Devices.
Hope that helps you with some feedback, I have found some minor issues, that I had managed to fix easily.
Cheers
BeeJ1109
Click to expand...
Click to collapse
Thanks for your Feedback. Unfortunately I don't own a Millet Device and can't reproduce this errors atm. I'm looking to buy one in the next time.
Could you please dl and test my latest LOS16 Build i uploaded today? This should be exactly the same as Matteos, cause i'm using his Device Tree.
Cheers

crazydrive22 said:
Thanks for your Feedback. Unfortunately I don't own a Millet Device and can't reproduce this errors atm. I'm looking to buy one in the next time.
Could you please dl and test my latest LOS16 Build i uploaded today? This should be exactly the same as Matteos, cause i'm using his Device Tree.
Cheers
Click to expand...
Click to collapse
Hi crazydrive22,
I will try LOS16 Build for you.
Another issue with crROM.
Adding extra Icons on Home screen. Work OK. But I save them to lawn chair option on internal memory and extSD card for backup. Backups produced OK on both locations. But Restore only restored original icons on 3 screens, but not newly added icons on any of the 3 screens including Home screen. Tried a few times, created extra backup files on internal and ext SD card. Available in Restore list. Copied files created between both. File size increases as I add more icons to Home or other screens. Just not showing up when I restore any created file.
I want to use this option, by installing the crdroid home 9 app. On Matteo ROMs, so I can Restore icons, on all screens, after a re-flash of any ROM. Would really be useful, save heaps of time, as I have some 100 odd apps.
Any ideas.
Cheers BeeJ1109

Hi Crazydrive22,
Sorry Tried LOS16 Latest version. Boot loops everytime.
Let it go until TWRP reboots as Recovery.
Re flashed a couple times, wiped cache, dalvik , system a few times, no change, still boot looping.
Cheers. BeeJ1109

Working perfect! No bugs!
When update to Android 10.0?
My Tablet: SM-T530
Before Andrdoid 5.0.2 and now Android 9.0!

Hi,
Flash does not work with twrp 3.0.0, but this is the latest official twrp.
Can you suggest a TWRP version for this ROM?

Hi All,
TWRP 3.4.0-4 by Matteo works. My device is Milletwifi.
Reflashed again after doing tests on Stock ROM for Matteo, did Wipe Cache, Dalvik & System, then reflashed this latest version.
Booted OK This Time. Instability with Google Play Service, So reflashed Nano Gapps. Fixed instability. But WiFi had issues, would not accept Password on several of my WiFi connections on both 2.4 or 5Ghz channels being Routers, Repeater, or Extenders.
Still using Stock EFS & Modem, same partitions, have not been overwritten. WiFi D.L was > 54Mbps, U.L > 18Mbps. Works great on Stock ROM.
So this ROM LOS16 Feb Build has issues. Camera does not work, same as Matteo's LOS 16. In fact this ROM appears to be identical to Matteo's LOS16. Apart from being compiled, by Crazydrive22. Therefore different title in About. Not sure what Crazydrive22 is trying to achieve here, apart from proving the Compile works, using the same repository sources as Matteo.
So I have restored back to Matteo ROM Feb Build. WiFi is back to same as before.
So I attached files.
Cheers BJ

ufa said:
Hi,
Flash does not work with twrp 3.0.0, but this is the latest official twrp.
Can you suggest a TWRP version for this ROM?
Click to expand...
Click to collapse
Its works with 3.5.0.9

Thank you all. Unofficial TWRP from Matteo worked.

makin17 said:
Working perfect! No bugs!
When update to Android 10.0?
My Tablet: SM-T530
Before Andrdoid 5.0.2 and now Android 9.0!
Click to expand...
Click to collapse
I'm planning to go to 10 and also 11 but there's no ETA atm. I'm working with Matteos Device Sources, so as soon he's ready, i'll be, too.

ufa said:
Hi,
Flash does not work with twrp 3.0.0, but this is the latest official twrp.
Can you suggest a TWRP version for this ROM?
Click to expand...
Click to collapse
BeeJ1109 said:
Hi All,
TWRP 3.4.0-4 by Matteo works. My device is Milletwifi.
So this ROM LOS16 Feb Build has issues. Camera does not work, same as Matteo's LOS 16. In fact this ROM appears to be identical to Matteo's LOS16. Apart from being compiled, by Crazydrive22. Therefore different title in About. Not sure what Crazydrive22 is trying to achieve here, apart from proving the Compile works, using the same repository sources as Matteo.
Click to expand...
Click to collapse
Sorry Guys, i was very busy the last time.
Matteo decided to go to LOS17 and LOS18, so I will build LOS16 for the future.
That's why we are building side by side, to check if everything is working well.
And as you've seen, it was a good idea.
With the next build (around 5th of March) everything should work on Millet, except the Camera.

god to know.

crazydrive22 said:
I'm planning to go to 10 and also 11 but there's no ETA atm. I'm working with Matteos Device Sources, so as soon he's ready, i'll be, too.
Click to expand...
Click to collapse
Update with OTA update or reinstall new ROM with Android 10?

makin17 said:
Update with OTA update or reinstall new ROM with Android 10?
Click to expand...
Click to collapse
If you switch the Version always clean flash with TWRP.
Updates as long as it is BETA via TWRP.
Maybe i'll go to OTA later, but there's no ETA so far.

Better Mobile App

welcome