Lineage OS 14.1 for Moto Razr M JBBL
{
"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"
}
Hi all!
I'm have ported LineageOS 14 for the xt907_jbbl
lineage-14.1-20170707-port-ilichva-xt907_jbbl
lineage-14.1-20170804-port-ilichva-xt907_jbbl
Enjoy.
XDA:DevDB Information
Lineage OS 14 for Moto Razr M_JBBL, ROM for the Motorola Droid RAZR M
Contributors
ilichva
ROM OS Version: Android 7.1.2 Nougat
Version Information
Status: Nightly
Created 2017-03-23
Last Updated 2017-08-05
Thank you so much for this! Even though it's a bit sad it's only for JBBL...
Do you know what are the differences between both bootloaders? I mean, why ROMs made for one don't boot in the other one?
trivialPotato said:
Thank you so much for this! Even though it's a bit sad it's only for JBBL...
Do you know what are the differences between both bootloaders? I mean, why ROMs made for one don't boot in the other one?
Click to expand...
Click to collapse
Rom JBBL (4.1) - kernel 3.0
Rom KKBL (4.4.2) - kernel 3.4
ilichva said:
Rom JBBL (4.1) - kernel 3.0
Rom KKBL (4.4.2) - kernel 3.4
Click to expand...
Click to collapse
Hm... Interesting... That means that a custom kernel would allow them to boot, right?
The custom kernel can be JB (3.0) or KK (3.4)
Therefore, the Lineage OS KKBL must have a core of 3.4
If you replace only the core, the ROM will not work.
ilichva said:
The custom kernel can be JB (3.0) or KK (3.4)
Therefore, the Lineage OS KKBL must have a core of 3.4
If you replace only the core, the ROM will not work.
Click to expand...
Click to collapse
Hm, I didn't get that, replacing the kernel would not allow them to boot? They'd need to be built from scratch?
Hello ilichva, big thanks. And what about root???
mastnacek said:
Hello ilichva, big thanks. And what about root???
Click to expand...
Click to collapse
Install SuperSU...
ilichva said:
Install SuperSU...
Click to expand...
Click to collapse
I just found this thread. When I flashed this ROM, I installed Magisk for root and haven't noticed anything negative, but have found benefits (e.g. installing/running Viper, work around for failing init.d etc). It also appears to be the choice on other devices, in newer ROMs .
@ilichva is there any specific reason you suggested SuperSU? or is it just that you haven't personally tested Magisk?
Originally I was kind of worried that the vanilla style of Lineage OS would bug me (as I am used to ROM's with a lot of customisations). However, I have Magisk (the apparent latest way to root), V4A, a Linux Swap Partition and have Xposed the...err...heck! out of the ROM (8 Xposed modules), including "Settings Editor" which enables you to add things to the settings menu that makes the additions (eg Viper) appear like they are actually part of the ROM.:good:
ilichva said:
Install SuperSU...
Click to expand...
Click to collapse
Thanks, works. In CM13 was supersu already. Good work.
I'm using supersu2.76 zip and install viperatmos stock5.4 and using exposed too, all working well on enforcing mode
dedik46 said:
all working well on enforcing mode
Click to expand...
Click to collapse
Do you have or are you using any boot scripts? ie init.d
DiamondJohn said:
Do you have or are you using any boot scripts? ie init.d
Click to expand...
Click to collapse
No...i didn't use init d or any script
dedik46 said:
No...i didn't use init d or any script
Click to expand...
Click to collapse
I think you may of misunderstood me. I was *not* asking if you used any init.d scripts to achieve viper & enforcing, but if you used init.d scripts for anything at all eg to set up the cache amount on your sd card, disable IO logging, instance a file/partition swap etc.
I have seen an su.d directory on my previous builds (instanced from flashing a viper install) but it was not being called/triggered by the SuperSU installed on the previous CM 13 build.
DiamondJohn said:
I think you may of misunderstood me. I was *not* asking if you used any init.d scripts to achieve viper & enforcing, but if you used init.d scripts for anything at all eg to set up the cache amount on your sd card, disable IO logging, instance a file/partition swap etc.
I have seen an su.d directory on my previous builds (instanced from flashing a viper install) but it was not being called/triggered by the SuperSU installed on the previous CM 13 build.
Click to expand...
Click to collapse
I've never try to use any script on init.d and i don't know if init.d is working or not, maybe i will try to use magisk for the next update..
dedik46 said:
I've never try to use any script on init.d and i don't know if init.d is working or not
Click to expand...
Click to collapse
And that's what I was checking. init.d does not work in this lineage ROM, nor in another devices (Nexus 5) lineage based ROM; ie Resurection Remix on N5. I am really surprised how little attention this artifact is getting.
dedik46 said:
maybe i will try to use magisk for the next update..
Click to expand...
Click to collapse
Although not an issue for me, it has extra features such as allowing some apps that wont run on rooted phones, to have su hidden from them. I like the fact that is has pre-built modules to support extra's such as V4A. I also liked the fact that it has its own init.d functionality that I use since the ROM's init.d does not work. And it appears to be the direction newer custom ROM's are heading for root.
Really, your already thinking about the next build? I am more thinking about the method/steps I did wrong or could of done better from the flash of the last build.
Wifi issue is not only our device
Some people have noted an issue with Wifi. I too have had the issue with the wifi loosing its connection and not automatically re-connecting. even though the Wifi is available and well within range.
I looked into it a little further (created a quick app that logged numerous broadcast messages, and logged them to a file), and as part of that I also tested the "pass" situation on my spare Nexus 5 phone, also connected top my Wifi. However, it too failed! it was however better in that it didn't randomly loose the wifi.
With the N5, if I was connected to Wifi (very strong signal), went into settings, turned off the wifi. When I turned the wifi back on, it did NOT automatically re-connect.
The N5 is running a MM Resurrection Remix (one of the latest builds, based on Lineage I think)
So, It would appear that this wifi issue is not specific to our devices. I am not sure if thats a good or bad thing.
Anyway, I have my logging test app running, and like a watched kettle, it hasn't lost its Wifi connection
Has anyone else had their "Recents" button on the NavBar fail to pull up recents? :crying:
It has happened to me randomly once before, and then it just came back randomly as well a few days later.
I am thinking it may be caused/triggered by the fact that I have a customized NavBar, and am using Xposed (Gravity box is one which modifies the NavBar) as well.
DiamondJohn said:
Has anyone else had their "Recents" button on the NavBar fail to pull up recents? :crying:
It has happened to me randomly once before, and then it just came back randomly as well a few days later.
I am thinking it may be caused/triggered by the fact that I have a customized NavBar, and am using Xposed (Gravity box is one which modifies the NavBar) as well.
Click to expand...
Click to collapse
I got the recents working again.
I tried turning all my xposed modules off (including a couple that affected the navbar), but it was still failing.
Then I noticed that for the first minute or so it would work every boot, but then eventually stop. So I thought it was some installed app/config that only started later in the boot sequence. This "app" must have root to do such damage, so I went down that path. Thought it might be Magisk (since I appear to be one of the only on it). So I uninstalled Magisk, and flashed SuperSU. Still failed.
Anyway, I got it working again by turning off Super User access to all apps individually (after a restore back to my original starting point), then turning it back on (with a few reboots between). I couldn't identify exactly which caused it, but now it all works :highfive:, and I have a technique to hopefully correct it in the future.:good:
and downloading now!
http://4pda.ru/forum/index.php?showtopic=403669&st=21880#entry60269538
Thank you @ilichva:good::good::good:
-------------edit
just noticed the link is in the first post
Related
Impacted ROM
version 1
Will there be a KitKat update of this ROM?
Read here.
Latest JB Samsung TouchWiz
XXUBNB3 (28th February 2014), Android 4.2.2
Why this ROM?
I was using CM-based ROMs since ever, because of their customisability and poweruser options I required. However, I always missed the better camera quality of the TW rom.
Finally, I decided to quit compromising and so I put this ROM together.
Features:
Knox kicked to the curb, along with its apps
rooted
BusyBox and init.d
Zipaligned
odexed (for better performance)
compatible with modern recoveries (like PhilZ)
Extras included:
Xposed framework + Wanam + XuiMod - enables customization of TouchWiz rom on the level comparable with custom AOSP/CM roms. But make sure you know how to use it!
GPS modified for faster lock and better performance
AdAway
How to flash:
Get into recovery (I use PhilZ, but any should work)
Flash the ROM
Reboot and let it bootloop for a minute. It will not boot, and this is normal.
Force reboot into recovery
Flash Vikinger kernel (for BLN support) or f4ktion kernel (for overclocking/undervolting). Warning: f4ktion kernels has a bug - read here. Let me know if it is not affecting you, should you decide to try f4ktion kernel.
Reboot.
Steps 3 and 4 might not be necessary. See for yourself and report back if skipping them works for you.
First proper boot may take several minutes as the phone comes to grips with how awesome ROM it will now run.
Extra steps for those who want to get max performance out of their phones with f4ktion kernel:
7. Edit file /system/etc/init.d/90hardlimit - change HARDLIMIT_VALUE to 2052000
8. Use program like Trickstermod to overclock and/or undervolt. My i9195 works on 2052 MHz with all voltages lowered by 150mV
In terms of looks, it starts just as regular TouchWiz,
{
"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"
}
and then you can make it look what you want.
This is mine:
Yes, it has battery bar.
Enjoy and prosper.
ROM DOWNLOAD
****************************************
UPDATE:
ROM usage statistics since publication: http://forum.xda-developers.com/showpost.php?p=56442984&postcount=73
,
flashed it today. looks good so far. thank you for your work.
Awesome to see a new rom
Since I'm more a visual guy - can we have some screenshots just to see how the best of two worlds looks like?
charliebigpot said:
Awesome to see a new rom
Since I'm more a visual guy - can we have some screenshots just to see how the best of two worlds looks like?
Click to expand...
Click to collapse
Done. But as I mentioned - it starts just as regular TouchWiz. It just gives you options to customize the crap out of it.
Reboot isn't working properly. Most of the time when I hit "reboot" the device just shuts down.
junkyde said:
Reboot isn't working properly. Most of the time when I hit "reboot" the device just shuts down.
Click to expand...
Click to collapse
Are you using Xposed 4-way reboot? I noticed it, too, and I think it's the module problem.
But it doesn't bother me. Reboot to recovery and download mode should work fine.
Yes I am using it. But when I used it on ML1 and other versions before, there where no issues. It also happend to me when I hit reboot from inside of other apps where I made some changes and a popup told me I need to reboot.
junkyde said:
Yes I am using it. But when I used it on ML1 and other versions before, there where no issues. It also happend to me when I hit reboot from inside of other apps where I made some changes and a popup told me I need to reboot.
Click to expand...
Click to collapse
Can you try removing the framework and module, and then reinstalling it form Playstore?
seems nice.
after deinstalling wanam xposed reboot worked, but with a huge delay. luckily the lights where off so after hitting the reboot button I could see that the display was still glowing, otherwise I would thought the device has shut down. Then I also deinstalled the framework and xposed installer. Reboot was still working (but with the delay). Afterwards I installed everything as it was before and now reboot doesn't work anymore.
Hmm... Perhaps you should disable the module tweaks before removing the modules. Did you try that?
I think so... but I am not quite sure.
junkyde said:
I think so... but I am not quite sure.
Click to expand...
Click to collapse
You could also try flashing Vikinger kernel. If that doesn't help, then most likely it is the NB3 doing that, OR the ML1 kernel is not 100% compatible with NB3.
I flashed Vikinger Kernel, because BLN didn't work with f4ktions. After flashing Vikinger, BLN started working. Then I flashed f4ktion again und now BLN is working with f4ktion. But I don't remember if the reboot problem persisted with Vikinger... And I am too lazy to test it again, because it's not a huge issue for me :laugh:
Prompt for I9190 fit?
Sent from my GT-I9190 using xda app-developers app
woow ! thank !
removed "bloats" ? all unused Samsung apps and some features completely useless .....and with "XS" google apps
what is the most updated and stable kernel between F4k and wikinger ? (with best ratio "good perf / life battery")
Well,i have to much reboots with this rom.Could be the f4ktion-kernel or the framework (i used the rom-integrated and a new one over the xposeapp update).I deinstalled the updated framework and switched the kernel,but with vikinger i can't activate wifi.
Gesendet von meinem GT-I9195 mit Tapatalk
junkyde said:
I think so... but I am not quite sure.
Click to expand...
Click to collapse
NikePershing said:
Well,i have to much reboots with this rom.Could be the f4ktion-kernel or the framework (i used the rom-integrated and a new one over the xposeapp update).I deinstalled the updated framework and switched the kernel,but with vikinger i can't activate wifi.
Click to expand...
Click to collapse
I haven't experienced any reboots. Perhaps the source is one of your programs, or overclocking, if any.
NikePershing said:
but with vikinger i can't activate wifi
Click to expand...
Click to collapse
that's because the f4ktion kernel changes the wifi modules. if you are going from f4ktion to another kernel, you need to replace them with the ones from stock rom. You can read in the f4ktion kernel thread about that issue and you will find the needed files there
I had to replace 3 files in system/etc/firmwares/wlan/prima folder with stock ones.Now wifi works with vikinger after f4ktion.
Gesendet von meinem GT-I9195 mit Tapatalk
Hi All,
As with my previous devices I've always looked out for the useless but still cool, screen off animation (remember the CRT animation on the old phones? ) as it has not yet been created for our device our only other option is to use Xposed.
Thanks to @zst123 for creating the Xposed module.
Cheers :good:
I've tested this to work with most ROMs, however it should work on any other ROM running android 6.0.XXX
Requirements
Root Access
A device running Android 6.0.XXX Marshmallow
A custom recovery (TWRP)
1. Go here and download this http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
This is the alpha apk
2. Go here and download this http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v81-sdk23-arm64.zip
This is the framework
3. Go here and download this http://dl-xda.xposed.info/framework/uninstaller/xposed-uninstaller-20150831-arm64.zip
This is the Xposed uninstaller just in case you want to remove it.
You now have everything you'll need for now
4. Install the Alpha APK and reboot to recovery.
5. Once in recovery, flash the Xposed Framework, once installed, reboot system, this may take a while, a few minutes is not uncommon.
Once back in the android system, you'll find that it indexes all your apps, this is normal, allow it to finish.
6. Open the Xposed Alpha app and click download.
7. Search for and download the ScreenOffAnimation module and enable it under modules within the Xposed app.
8. Reboot your device.
9. Open the ScreenOffAnimation app and enable an animation. Reboot, again this may take a few minutes although it should be quicker than the framework reboot, no application indexing should take place.
10. Done and Enjoy
You will need to reboot to fully implement any new changes to this app, it also hasn't been updated for a while so the current version is v1.3, however it is functional and should work as expected.
You might be able to squeeze this whole process with maybe a few less reboots, however this is how I first did it and how it worked for me so it should (if you follow to the letter) work for you
At the time of writing the versions used are as follows.
Alpha APK v3.0alpha4
Framework v80sdk23 for ARM64 devices.
ScreenOffAnimation v 1.3
Any questions, please ask and I'll do what I can to assist.
Great idea, I loved this CRT Screen Off animation but I´ve stopped using Xposed a while ago. I remember having problems with it on Android 5.1.1 and I guess that it´s still buggy with ART ? If Xposed is the only way to get this old animation again, I will have to pass on this one.
Gorgtech said:
Great idea, I loved this CRT Screen Off animation but I´ve stopped using Xposed a while ago. I remember having problems with it on Android 5.1.1 and I guess that it´s still buggy with ART ? If Xposed is the only way to get this old animation again, I will have to pass on this one.
Click to expand...
Click to collapse
exactly the same as me mate, I was avoiding xposed for so long but thought I'd try it, and maybe make a little tutorial to go with it.
up until now, no excessive drain, no issues.
I also haven't installed any other modules either. I'm very sure that this can be done without xposed , however until that time, this will do.
but I do agree with you. if I could get this mod without xposed I would.
there's also an uninstaller too so no need to worry
Xposed has been running great for me on 6.0.1
Gorgtech said:
Great idea, I loved this CRT Screen Off animation but I´ve stopped using Xposed a while ago. I remember having problems with it on Android 5.1.1 and I guess that it´s still buggy with ART ? If Xposed is the only way to get this old animation again, I will have to pass on this one.
Click to expand...
Click to collapse
Any chance you're talking about the storage issue that appeared from ART?
I can't run my device without Xposed, lmfao. I set the apps I need with Xposed to not update unless it's compatible with the Xposed modules I run.
Sent from my Nexus 6P using Tapatalk
Gorgtech said:
Great idea, I loved this CRT Screen Off animation but I´ve stopped using Xposed a while ago. I remember having problems with it on Android 5.1.1 and I guess that it´s still buggy with ART ? If Xposed is the only way to get this old animation again, I will have to pass on this one.
Click to expand...
Click to collapse
Exposed is ruining great on mm
Have to say, after my first day. I've not had a single change in battery, hadn't even dropped by 1% overnight
This doesn't work for me. I'm on stock ROM and kernel with Xposed.
Edit: Although it does work with Cataclysm mod/ROM.
Krunk83 said:
This doesn't work for me. I'm on stock ROM and kernel with Xposed.
Edit: Although it does work with Cataclysm mod/ROM.
Click to expand...
Click to collapse
Had you already had xposed installed ? I can't see why it would make a difference so long as you're rooted, have twrp and can successfully install xposed. Also check your version vs the one I used.
I've never installed xposed on a stock ROM so can't comment but I'd have thought it would have worked.
dladz said:
Had you already had xposed installed ? I can't see why it would make a difference so long as you're rooted, have twrp and can successfully install xposed. Also check your version vs the one I used.
I've never installed xposed on a stock ROM so can't comment but I'd have thought it would have worked.
Click to expand...
Click to collapse
Yeah, everything was installed correctly it just didn't work for some reason. It's all good because I just flashed the Cat mod and it worked.
Krunk83 said:
Yeah, everything was installed correctly it just didn't work for some reason. It's all good because I just flashed the Cat mod and it worked.
Click to expand...
Click to collapse
Cat mod?
Also I'd have to verify if it definitely doesn't work on stock ROMs and find out why to update the OP. Might be the version you've got installed.
FYI, try Franco kernel. Apparently xposed plays nicely with it.
I don't mess with custom kernels anymore. Too buggy. The cat mod is a mod to flash over stock to give you the Cataclysm settings. It's not the full cat ROM. So no system wipe/restore needed.
{
"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"
}
Sent from my Nexus 6P
Krunk83 said:
I don't mess with custom kernels anymore. Too buggy. The cat mod is a mod to flash over stock to give you the Cataclysm settings. It's not the full cat ROM. So no system wipe/restore needed.
Sent from my Nexus 6P
Click to expand...
Click to collapse
Interesting. So it actually has xposed as part of it. Nice. Will check it out.
Nice module, working fine on Screw'd ROM. I have several xposed mods running & have no issue with battery usage or glitches.
I like the random feature & choosing duration - an excellent find thanks
tweeny80 said:
Nice module, working fine on Screw'd ROM. I have several xposed mods running & have no issue with battery usage or glitches.
I like the random feature & choosing duration - an excellent find thanks
Click to expand...
Click to collapse
Very welcome mate, the vertu one is spot on
The module has not been updated since 2014 or am I looking at the wrong one?
May I ask, if I have all system animations disabled via developer options, will this still work?
EarlZ said:
The module has not been updated since 2014 or am I looking at the wrong one?
Click to expand...
Click to collapse
No you are correct, the thing is it really doesn't matter. It works perfectly.
cd993 said:
May I ask, if I have all system animations disabled via developer options, will this still work?
Click to expand...
Click to collapse
Yes it does, functions as expected whilst everything else is off..just tested now.
dladz said:
Yes it does, functions as expected whilst everything else is off..just tested now.
Click to expand...
Click to collapse
That's great, many thanks for helping out
---------- Post added at 06:42 PM ---------- Previous post was at 06:24 PM ----------
Really like this! Favourite so far would be Fade set at 250ms
Introduction
Hello everyone! This is an incredibly simple module to enable sdcardfs on any Nougat 7.x ROM (SDK 24 or higher). sdcardfs is a replacement file system for FUSE, used to mount the /sdcard partition; you can read about this change here.
Some notes
sdcardfs is in constant development (at least two to three patches per week on average), meaning it could become unstable at any point. Certain apps do not play with sdcardfs, which can lead to crashes and corruption. Enable it at your own risk!
Your kernel MUST have sdcardfs support for this to work. Please ask your kernel/ROM developer if they have included all of the proper support commits for it to work. They can be found in AOSP's kernel/common repo (or a quick search of the AOSP Gerrit).
You MUST have this system/core commit. There is no reason that every 7.x ROM should not have this commit as it comes straight from Google but you never know.
Frequently Asked Questions
1.1 Q: How do I use this?
1.1 A: Flash it in recovery or add it in Magisk Manager > Modules.
1.2 Q: How do I check if the module works?
1.2 A: Go into a terminal emulator and type the following:
Code:
su
df -t sdcardfs
If you see something like the following, the module worked! If not, it is most likely because you either don't have sdcardfs support in your kernel OR you do not have the system/core commit I mentioned above.
{
"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"
}
1.3 Q: I'm having xyz issue.
1.3 A: Great! Please give me a logcat, dmesg, and Magisk log and I'll be happy to assist.
Changelog
Version 3.0:
Update template to v4 and use system.prop instead of post-fs-data.sh
Version 2.1:
Improve print_modname so it looks right while flashing in recovery
Don't install on anything less than Nougat (thanks @veez21)
Version 2.0:
Add logging to Magisk log
v13 snapshot support
Version 1.0:
Initial support
Downloads
Primary | Mirror
Source
Hooray for bleeding edge break my phone stuff!
Sent from my Nexus 6 using Tapatalk
Hahahaha. I'm not sure I should try that on my stock MM Rom. Even with Firekernel.
Enviado de meu MotoG3 usando Tapatalk
Uploaded version 2.0 which adds some info in Magisk's log and adds support for the unified magisk binary in the v13 snapshot builds floating around.
The Flash said:
Uploaded version 2.0 which adds some info in Magisk's log and adds support for the unified magisk binary in the v13 snapshot builds floating around.
Click to expand...
Click to collapse
do we update by just flashing the newer build over the existing one?
xflowy said:
do we update by just flashing the newer build over the existing one?
Click to expand...
Click to collapse
Yes.
The Flash said:
Uploaded version 2.0 which adds some info in Magisk's log and adds support for the unified magisk binary in the v13 snapshot builds floating around.
Click to expand...
Click to collapse
Cheers for doing this. Glad I could test it for you.
@The Flash U just broke my MM installation cause I was tested blind, I don't know what happende I just didn't read it was only for sdk24 +
I seem it after I flashed it, I didn't restarted and was going to uninstall on magisk, but then magisk lost root (wasn't happened before on the stock rom), I had to restart, I deleted it from magisk.img using the magisk mount module, and now it stays on Android is starting forever, and does not start up. :/
You can blame me xD But, can help me?
What files I have to edit/delte so I can completely disable it?
justjr said:
@The Flash U just broke my MM installation cause I was tested blind, I don't know what happende I just didn't read it was only for sdk24 +
I seem it after I flashed it, I didn't restarted and was going to uninstall on magisk, but then magisk lost root (wasn't happened before on the stock rom), I had to restart, I deleted it from magisk.img using the magisk mount module, and now it stays on Android is starting forever, and does not start up. :/
You can blame me xD But, can help me?
What files I have to edit/delte so I can completely disable it?
Click to expand...
Click to collapse
The script doesn't actually fire if you are on Marshmallow: https://github.com/nathanchance/magisk-modules/blob/sdcardfs/common/post-fs-data.sh#L32
Even then, that prop doesn't actually do anything on Marshmallow or below. Your issue is unrelated to this. Dirty flashing your ROM should fix it.
The Flash said:
The script doesn't actually fire if you are on Marshmallow: https://github.com/nathanchance/magisk-modules/blob/sdcardfs/common/post-fs-data.sh#L32
Even then, that prop doesn't actually do anything on Marshmallow or below. Your issue is unrelated to this. Dirty flashing your ROM should fix it.
Click to expand...
Click to collapse
@The Flash, check this out
https://github.com/nathanchance/magisk-modules/pull/1/commits
@The Flash - May I know your keyboard name??? ?
mkshakya said:
@The Flash - May I know your keyboard name??? ?
Click to expand...
Click to collapse
It's Gboard themed with Deep Darkness for Substratum, coming soon.
The Flash said:
....
Click to expand...
Click to collapse
edit
Hello, do you know if EX kernel supports sdcardfs? Sorry if I asked here but I thought you know since I always see you on all of the forums :silly:
RonnellTapawan said:
Hello, do you know if EX kernel supports sdcardfs? Sorry if I asked here but I thought you know since I always see you on all of the forums :silly:
Click to expand...
Click to collapse
Yes: https://github.com/flar2/bullhead/commits/ElementalX-4.00/fs/sdcardfs
It does not have all of the AOSP upstream commits but it should be fine without them.
I strongly suggest you to remove this. sdcardfs is still in development by the Android Kernel team and it's not ready for production. sdcardfs's only advantage is reduced overhead compared to FUSE when there's system calls to & from the sdcards. Users will think they know better (they don't) and they'll spam everyone and everything about sdcardfs without knowing what it is or what it does.
franciscofranco said:
I strongly suggest you to remove this. sdcardfs is still in development by the Android Kernel team and it's not ready for production. sdcardfs's only advantage is reduced overhead compared to FUSE when there's system calls to & from the sdcards. Users will think they know better (they don't) and they'll spam everyone and everything about sdcardfs without knowing what it is or what it does.
Click to expand...
Click to collapse
Why does my dog do back flips?
franciscofranco said:
I strongly suggest you to remove this. sdcardfs is still in development by the Android Kernel team and it's not ready for production. sdcardfs's only advantage is reduced overhead compared to FUSE when there's system calls to & from the sdcards. Users will think they know better (they don't) and they'll spam everyone and everything about sdcardfs without knowing what it is or what it does.
Click to expand...
Click to collapse
While I agree that users tend to be less informed than developers are, I have made it fairly clear in the OP that this is experimental and to enable at their own peril. I like bleeding edge and many other users do as well, knowing fully the risk of it. I'll take to heart the concern though, thank you.
To any kernel developer (and users): If your users start complaining about crashes and such, please let me know and I'll remove the module.
Hey, I complained but stated that was my fault. Now I installed DU after my data partition gone to hell, and found out the same prop was already set to true on that ROM. And nobody gone there to ask them to take the ROM down. Pocketcasts complained a little but I managed to make it work. No problems.
franciscofranco said:
I strongly suggest you to remove this. sdcardfs is still in development by the Android Kernel team and it's not ready for production. sdcardfs's only advantage is reduced overhead compared to FUSE when there's system calls to & from the sdcards. Users will think they know better (they don't) and they'll spam everyone and everything about sdcardfs without knowing what it is or what it does.
Click to expand...
Click to collapse
WTF franco.. .I thought this was a development friendly forum..
Bleeding edge and experimentation should be applaud, not criticize.
PS I know that this forum turn into anything else but developer friendly, but still, you should've known better than asking another developer that.
Mokee OS 8.1
{
"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"
}
Thanks to the developers of the Mokee OS group
https://download.mokeedev.com/file.php
download link :
https://download.mokeedev.com/?device=albus
install gaaps nano
Here you can find some extras like magisk, Gaaps and root:
https://download.mokeedev.com/extras
XDA:DevDB Information
Moke OS, ROM for the Moto Z2 Play
Contributors
lsolis293
ROM OS Version: 2.3.x Gingerbread
ROM Kernel: Linux 3.x
Version Information
Status: Nightly
Beta Release Date: 2018-12-24
Created 2018-12-25
Last Updated 2018-12-24
Who is the maintainer of this?
Cupcake 1.5 said:
Who is the maintainer of this?
Click to expand...
Click to collapse
It doesn't have, we are lucky to have a well treble implemented rom scheme, thanks to rahuls nair, and based on that mokee makes blind builds. I mean they only need to compile a system everyday, hardware and major changes aren't needed due to treble (that work is done).
It's a fork of LineageOS after all.
By the way, been using this rom since the day LineageOS died for Z2 play and zero bugs, hope this helps.:good:
moonlightdrive said:
It doesn't have, we are lucky to have a well treble implemented rom scheme, thanks to rahuls nair, and based on that mokee makes blind builds. I mean they only need to compile a system everyday, hardware and major changes aren't needed due to treble (that work is done).
It's a fork of LineageOS after all.
By the way, been using this rom since the day LineageOS died for Z2 play and zero bugs, hope this helps.:good:
Click to expand...
Click to collapse
No reboots? I had some reboot issues when I tried the latest nightly earlier today. Clean install, wiped even internal, pico gapps with magisk 18.
Cupcake 1.5 said:
No reboots? I had some reboot issues when I tried the latest nightly earlier today. Clean install, wiped even internal, pico gapps with magisk 18.
Click to expand...
Click to collapse
No reboots, i am on 20-Feb nightly (I update once time every 2 weeks aprox), will try today's nightly to see if reboot happens to me too.
moonlightdrive said:
No reboots, i am on 20-Feb nightly (I update once time every 2 weeks aprox), will try today's nightly to see if reboot happens to me too.
Click to expand...
Click to collapse
All ok now, it was gapps it seems. I used the recommendation of nano and all is running perfect, smooth, up to date, mods working, awesome. This Rom should be pinned, not getting noticed by anyone and, it's the only one getting nightlies.
Cupcake 1.5 said:
All ok now, it was gapps it seems. I used the recommendation of nano and all is running perfect, smooth, up to date, mods working, awesome. This Rom should be pinned, not getting noticed by anyone and, it's the only one getting nightlies.
Click to expand...
Click to collapse
Mods are working?
Which ones?
MusicAlleyInc said:
Mods are working?
Which ones?
Click to expand...
Click to collapse
Well, I only have one so I can't say others. I have the JBL speaker mod. As far as I am aware, any mod that works with linage will work on mokee.
Cupcake 1.5 said:
Well, I only have one so I can't say others. I have the JBL speaker mod.
Click to expand...
Click to collapse
Is the Moto Mod Manager installed, or is it linked to google play/updatable?
MusicAlleyInc said:
Is the Moto Mod Manager installed, or is it linked to google play/updatable?
Click to expand...
Click to collapse
It is installed and shown in settings. I can update in play store, it shows update. Tried to update and it fails.
Cupcake 1.5 said:
It is installed and shown in settings. I can update in play store, it shows update. Tried to update and it fails.
Click to expand...
Click to collapse
Ok, that is probably because play store can't update it as a system/priv app.
MusicAlleyInc said:
Ok, that is probably because play store can't update it as a system/priv app.
Click to expand...
Click to collapse
Confirmed, it is in System/priv-app
Cupcake 1.5 said:
Confirmed, it is in System/priv-app
Click to expand...
Click to collapse
Perhaps the apk can be downloaded and installed there using a flashable zip installer, just don't know if that would mess anything up.
https://android-apk.org/com.motorola.modservice/44014886-moto-mods-manager/
MusicAlleyInc said:
Perhaps the apk can be downloaded and installed there using a flashable zip installer, just don't know if that would mess anything up.
https://android-apk.org/com.motorola.modservice/44014886-moto-mods-manager/
Click to expand...
Click to collapse
Fails to install. I assume projector mod will work also because that apk is in System, if that is one you need to work.
Cupcake 1.5 said:
Fails to install. I assume projector mod will work also because that apk is in System, if that is one you need to work.
Click to expand...
Click to collapse
Well the update adds some settings for mods sometimes, not sure which version the ROM is at , but the change log mentions something about allowing the turbopower mods efficiency setting to be edited with the new update (control at what percentage the mod starts charging phone)
I might mess around with system app install tricks later.
MusicAlleyInc said:
Well the update adds some settings for mods sometimes, not sure which version the ROM is at , but the change log mentions something about allowing the turbopower mods efficiency setting to be edited with the new update (control at what percentage the mod starts charging phone)
I might mess around with system app install tricks later.
Click to expand...
Click to collapse
Latest version: 02.05.018
Installed version: 02.05.002
Is this rom based on 8.1 oreo? Is the signal good? NFC work?
muritipo said:
Is this rom based on 8.1 oreo? Is the signal good? NFC work?
Click to expand...
Click to collapse
Everything works. Is just a fork of LineageOS with a few addons. Recommended :good:.
And yes... it's 8.1 with most recent security patches available and updated nightly, with incremental updates available for a small donation.
OP can you update the description to inform people that this ROM supports Moto Mods, I am sure that would make many users very happy.
---------- Post added at 12:51 AM ---------- Previous post was at 12:49 AM ----------
[/COLOR]
MusicAlleyInc said:
And yes... it's 8.1 with most recent security patches available and updated nightly, with incremental updates available for a small donation.
OP can you update the description to inform people that this ROM supports Moto Mods, I am sure that would make many users very happy.
Click to expand...
Click to collapse
really works? What motomods did you test?
This is real?
{
"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"
}
Google Pixel 3a XL
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Google Pixel 3a XL.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
bonito
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.9
Going to try it now.
Thank you!
npjohnson said:
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Click to expand...
Click to collapse
syntax error Are we talking about the Kernel being bundled?
ssurell said:
syntax error Are we talking about the Kernel being bundled?
Click to expand...
Click to collapse
What? No, firmware, like modem, bootloader, etc.
Question:
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
So are you saying if we root there is no support? As most of us coming from stock would at least need root temporarily to restore all our apps.
Can anyone confirm if root even works on this build. I woudnt see any reason not but would like to know cause of the above reason.
UPDATE: Decided to just go for it and everything is working great so far. Took a little work to get google apps working instead of the included aosp ones (phone calendar and contacts) and a bt more work to get it to pass safteynet but its all working 100% now. Also tested this build with both ex kernel and mvk and they both seem to work just fine as well. Will report back if anything changes as have only been running it.a few hours but so far no issues or complaints at all.
Great job LOS team
What is the official way to obtain root access? or is there one any more?
cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
Based on the above statement i quoted sounds like root is not "officially" supported at all. That said to get root i followed the process by which you patch a boot image file with magisk manager. Making it pass safteynet net took additional steps.
If you need more details on either process just post back and i can be more detailed
adm1jtg said:
If you need more details on either process just post back and i can be more detailed
Click to expand...
Click to collapse
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!
cliffordd said:
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!
Click to expand...
Click to collapse
sent you a private
cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
i flashed the version of Magisk (v21.4) via the LineageOS recovery using the adb sideload and just updated to v22 via the app. I haven't had any issues with root since installing.
First off, I want to say thank you for all the hard work on these builds.
I have came across one issue that isn't working for me, but might not be something everyone else uses a lot. My "squeeze" for Assistant isn't working, but I can change it to take a screenshot of any other option, except the Assistant. Am I doing something wrong or is there another settings need to activate for it to work?
Thanks!
Really want to try this, but can't "fastboot boot twrp.img" or "fastboot flash boot twrp.img" in Android 11 to backup my partitions. What's the point of Android OS if I can't backup my system? I can boot into Lineage OS Recovery, enable adb, figure out the partition names, dd the partitions from shell or pull with adb? But good grief, kinda ridiculous if you ask me.
Haven't been able to use twrp since Android 9 far as i know
lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.
Nevermind, user error.
ssurell said:
lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.
Click to expand...
Click to collapse
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.
npjohnson said:
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.
Click to expand...
Click to collapse
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1
ssurell said:
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1
Click to expand...
Click to collapse
weird - we don't have MTG builds for 17.1 though, sadly.
How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.
ssurell said:
How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.
Click to expand...
Click to collapse
Why do you want encryption disabled?
It's hardware backed, and FBE, so very little gain from running unencrypted...
"Trust" has nothing to do with encryption, it can be on, off, trust just reports it to the user.
Why do you want TWRP? Lineage Recovery does the job just fine. What do you mean "/data (formerly userspace)"? That statement doesn't make much sense.
Regardless of all the above, the disabel force encrypt zip, followed by `fastboot -w` to format userdata ought to do it - but be warned, if you set a PIN, Android (AOSP, not a lineage thing specifically) will re-encrypt you... hence there being no point.