Database Users

[Rom] Mokee 7.1.2 for Lenovo Vibe Shot

https://download.mokeedev.com/?device=zoom

Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..

X10MINISTER said:
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
Click to expand...
Click to collapse
Rom works but it wasn't maintained. No new bug correction from february.

stuccamelo said:
Rom works but it wasn't maintained. No new bug correction from february.
Click to expand...
Click to collapse
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this

X10MINISTER said:
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
Click to expand...
Click to collapse
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good

stuccamelo said:
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
Click to expand...
Click to collapse
So, it mean that u also facing the hotspot problem.?

Can u change/install fonts in mokee roms? Cause I have an issue with changing font style using iFont apps..its say installed but after reboot font style doesnt change. Any solution?

linux shall eternally bloat all search engines with expired ?=
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.

Dr Tungsten said:
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Click to expand...
Click to collapse
There are a lot of recent updates for this rom. I flashed the most recent (2017-11-21 date). I didn't make a lot of testing but the problem you refered has been solved and the performance and stability seems good.
The only issue I noticed so far is that the phone does not start automatically from the shutdown state when an alarm is set.

@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..

GeorgeTsak said:
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
Click to expand...
Click to collapse
This is not my main phone right now so I spend very limited time using or testing it but you are right, I have just checked that with this ROM the device is unable to pass the SafeNet test so far. On the other hand I have not problems at all playing videos with youtube app or rooting the device. I'm using supersu v2.82 and TRWP-3.0.2-0 for lenovo 6.0 by wzsx150 (didn't try Magisk)

has anyone managed to install this ROM?
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.

mrtowel said:
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
Click to expand...
Click to collapse
I think you need a different TWRP version. Try this one:
https://drive.google.com/file/d/0B1Sms71Oe6FIQnl4STlhSk96b0E/view?usp=sharing

Help me!
I'm new to these things. Installing roms and ****s. Can someone help me with the step by step procedure of installing this room on my Lenovo vibe shot. Thanks in advance.

The same probvlem with TWRP
piccolo2k2 said:
I think you need a different TWRP version. Try this one:
Click to expand...
Click to collapse
I have exactly the same problem.
Did you resolved it? Tried also mentioned "Twrp by rahul.rar", but the same problem - unable to mount /system partition.
Thanks for reply,
st

bug fix?
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?

hhaekal said:
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
Click to expand...
Click to collapse
Im using it right now.. Im still have the problem with:
-hotspot tethering,bluetooth tethering
-usb mtp
-suddenly shutdown when on wifi
Have someone had the problem with delay in receiving whatsapp messages?

Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?

Alex_135 said:
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Click to expand...
Click to collapse
Hi,
I'm using the release and there is no bug with WIFI.

Linaxx said:
Hi,
I'm using the release and there is no bug with WIFI.
Click to expand...
Click to collapse
How about wifi tethering problem? Does it remain error when wifi tethering are enabled?

Experience : successful Resurrection Remix NEM-L51 - Meticulus's ROM v5.8.5-20171214

Hi all XDA's members and Meticulus's RR ROM contributors,
I would like to share my experience with Meticulus's RR ROM for Honor 5C.
First I tried Elite V6 with no success : bootloop, F2FS or EXT4 nothing to do ; the Elite V7 is available from Christmas but I see that there are bugs to fix for Hassan, so I gave up and restored a backup of my STOCK system.
The restore was not good as my camera and audio no longer worked...
Before I get back to the STOCK update NEM-L51C432B357, I decided to try Meticulus's RR. It was a very good idea as I now have a renamed Honor 5c to hi6250 (...) working with no bug up to now.
LTE OK, SMS OK, GPS OK, SDCARD OK, AUDIO OK, VIDEO OK, GAPPS OK, MTP OK, etc
Adaway OK, Afwall+ OK, Magisk v14 OK
+ Bonus : Evie Launcher working as it was not using with STOCK ROM (icon size issue) !
Many thanks to Meticulus and contributors for sharing this very good work.
---
To be more precise for Honor 5C owners :
DEVICE : HONOR 5C
ROM STOCK BUILD : NEM-L51C432B350
MODDED RECOVERY .. : TWRP-3.1.1-0-hi6250-v5.2.zip
ROM INSTALLED .... : RR-N-v5.8.5-20171214-hi6250-Meticulus.zip
GAPPS INSTALLED .. : open_gapps-arm64-7.1-pico-20171225.zip
---
Steps of my successful installation with SDCARD and no SIM CARD :
1- FASTBOOT the TWRP then reboot to the TWRP RECOVERY
2- Wipe all except external SDCARD
3- Install the ROM
4- Reboot to TWRP RECOVERY
5- Install the GAPPS
6- Reboot to system (RR)
7- During RR Android setup, when asked insert the SIM CARD.
It would perhaps also have been successful with the SIM CARD inserted from the beginning...
---
Questions/feature requests :
- On Resurrection Remix site, I have not found your great ROM why ?
- On XDA Dev, there is no thread "Resurrection Remix For The Honor 5C [METICULUS]" but a "[ROM][7.1.2] Resurrection Remix For The Honor 6x [METICULUS]" one, this is why I put my comments here and in the Elite thread for those like me unable to get Elite V6 or V7 working with their Honor 5C.
- One thing is really missing to me (not found in settings) : the scheduled start/stop that worked very well with the STOCK ROM.
Do you think that this useful feature could be added on a future version ?
- The double TAP for screen wake up, would be a great bonus feature (was not provided in the STOCK ROM).
- Not tested the OTG, I will tell it in this thread.
Thanks again.
---
Meticulus's replies :
1. It is unlikely that any device with a kirin processor will get "official support" for LineagOS and therefore Resurrection Remix. There just isn't enough source.
2. Just because there is no "Honor 5c" thread doesn't mean you should come here and confuse information. It makes the water muddy. There is nothing stopping you from creating a thread in the "Honor 5c General" and post your experienced there.
3. Scheduled device start and sleep is not something I will work on.
4. DoubleTap 2 Wake only works on some P9 Lite's. Other devices with different touchscreens simply do not have the hardware capability.
5. I'm glad you like the ROM but please re-post your experiences in the Honor 5c section. I intend to delete these posts...

Is working dual sim and volte
Is works dual sim and volte

Sim working fine??

What do you think solved the audio issue?
Reverting to Stock Rom backup could have helped somehow.
Renaming it maybe ? And how did you rename it? After installing this rom mine became hi6250.
I own a nmo-l31 and ever since installing EliteRom v7 i could not get the audio working. Installed EliteRom v6 , applied l-31 patch,nothing.
Trying to switch to stock rom with dload gave error
Directly flashing boot,system,cust,recovery from firmware packages didnt change anything on the userspace ,literally.My files,homescreen etc. remained the same and only recovery changed. I think i made a mistake there but who knows.
Now installed this ResurrectionRemix twrp and rom after seeing this thread.Audio still refuses to work .

thatwasmyfakeacc said:
What do you think solved the audio issue?
Click to expand...
Click to collapse
I had the same problem on my NEM-L51. The problem is (or at least i think it is), that the vendor partition is somehow corrupted.
Short explaination, the vendor partition holds some drivers which are not open source (therefore not in the android kernel) and also aren't shipped in the custom roms (because of copyright stuff). So you always need to have them, if the custom rom depends on them (and most/all of the honor 5c custom roms do so). That's also the reason why you always have to flash the custom rom over your emui5.x and if you screwed your whole system, you first need to flash a backup or get back to emui on a different way before you can flash a working custom rom again.
So that's the explaination part. I installed twrp on my device, took a complete backup, flashed aosp from meticulus, everything worked except of Audio/Videos. Flashed LineageOS from Hassan, everything worked except of audio/video playback. Flashed backup, everything worked except audio/video. WTF. I don't know why, but i believe that the backups made with TWRP were somehow not complete, because flashing all partitions (the backup was over all partitions, triple checked, made new backups from stock) didn't solve audio issues, not even on the stock backup. What I now did was getting back to stock with the dload method, and flashed again directly the lineageos from hassan, which then worked. I had a try before where i first accidentially flashed aosp again, and same problems occured again. Also the now stock backup again didn't work. That's why i think that the TWRP backups for Honor 5c NEM-L51 are somehow not right.
Tl;dr if you have audio/video playback issues, try to get back to stock (make sure those features work on your stock rom) and flash again. If it still doesn't work, custom rom is maybe not compatible with nem-l51 (only experienced that with meticulus roms, hassans work great).
thatwasmyfakeacc said:
I own a nmo-l31 and ever since installing EliteRom v7 i could not get the audio working. Installed EliteRom v6 , applied l-31 patch,nothing.
Trying to switch to stock rom with dload gave error
Directly flashing boot,system,cust,recovery from firmware packages didnt change anything on the userspace ,literally.My files,homescreen etc. remained the same and only recovery changed. I think i made a mistake there but who knows.
Click to expand...
Click to collapse
Try again with the dload method, maybe use another UPDATE.zip. I had to try it several times, device booted sometimes for ever, and suddenly it worked. No idea why, but maybe try it again.

Custom Roms is good but overal it lacks supports for long terms and quality of pictures taken are not as nice as stock ones

stevedat said:
Custom Roms is good but overal it lacks supports for long terms and quality of pictures taken are not as nice as stock ones
Click to expand...
Click to collapse
also system collect trash files that slows you down. i used to be all in for custom roms but now i dont use them because they will break in time and standby batterydrain will increase rapidly.

thelous said:
also system collect trash files that slows you down. i used to be all in for custom roms but now i dont use them because they will break in time and standby batterydrain will increase rapidly.
Click to expand...
Click to collapse
Rite, it's just for fun.

shankarjdhv125 said:
Is works dual sim and volte
Click to expand...
Click to collapse
Hi,
Dual SIM not tested, Volte I don't know if it works using my ISP (free.fr) and don't know how to check this.
An advice, don't update Magisk, I have done it on several rr (honor 5c, idol3 5.5), the result was bootloop.

Pixel System Image (Oreo & P Preview) booted successfully on Essential PH-1

It appears that a couple of people tried flashing the Pixel 2 XL system.img onto the Essential PH-1, and was able to boot it, and have (almost) everything working:
https://forum.xda-developers.com/es...ashed-img-pixel-2-xl-opm2-171026-006-t3805921
This didn't used to be the case when the PH-1 was on 8.0. The people there mentioned that they went directly from having official Essential 8.1 June firmware installed and just flashing the Pixel system.img. All it took from that point on was a data wipe and it (allegedly) booted (almost) flawlessly. Some folks there also mentioned that Pixel 2's Android P DP3 system.img booted successfully as well.
@phhusson thoughts?

It boots the same right after oreo or P. There is no mobile data, so no calls or text. I fixed the camera, which was the other bug. I tried flashing my phones vendor images and modem over top of this and it still doesnt fix it. Must be in the system some place. I may try to swap out some lib, or hw files. Then maybe look at the build prop

i have done thins as well...boots flawlessly but as stated, no service or wifi for me...how was the camera fixed?

BakedTator said:
i have done thins as well...boots flawlessly but as stated, no service or wifi for me...how was the camera fixed?
Click to expand...
Click to collapse
I kept a folder of all camera related lib files from our Android p stock, then after booting this, i just used trial and error till i got the camera working. I am certain i could replicate but until we fix the no service probs i stopped messing with it. Just wasnt worth it. I moved on to flashing as many treble gsi's as i could. They all work mostly except for play store issues.

it also works on the Leeco Pro 3 X7272/720
Everything works. Except for call sound

tsongming said:
it also works on the Leeco Pro 3 X7272/720
Everything works. Except for call sound
Click to expand...
Click to collapse
Flash Pixel2XL's A/B system.img to A-only LePro3 directly???

qqzwc said:
Flash Pixel2XL's A/B system.img to A-only LePro3 directly???
Click to expand...
Click to collapse
System A only
However, unless this file has been updated you are better off following the GSI instructions in my signature.
or here: https://forum.xda-developers.com/le...nstall-gsi-t3843142/post77636477#post77636477

Android 10 GSI

Note: Make sure your phone is decrypted and do not turn on the secure boot feature where you need to put in your pattern to boot system!
So as I'm currently without a PC and can't restore the stock images I wanted to share the best method for using Android 10 I've found.
Get the latest phh gsi image v210 is what I used.
Get the latest Lineage OS GSI 17.1 image.
Get the Trinity v2 kernel (beta is what I used).
Get the latest Android 10 pico or nano gapps from opengapps. (I used nano)
Boot to recovery and factory reset.
Install phh gsi IMG to system. When finished don't reboot. (I do this to keep security patches as up to date as possible)
Install LineageOS IMG (DIRTY FLASH).
Install Trinity Kernel to Boot
Reboot system
(Optional once you fully boot you can reboot recovery and flash the f2fs zip from Arter Kernel then reboot recovery and wipe data. When you reboot system you may freeze during setup just reboot by holding the power in until the phone restarts. It will finish setup this time.)
Reboot recovery and flash gapps. If you get error 70 resize the system partition. It will work after resizing once or twice.
When it boots you can do your traditional setup.
Reboot recovery and Install Magisk v20.3.zip
Reboot system and Install Magisk Modules Busybox for Android NDK and Magisk Hide Props Config.
Install terminal app of choice following Reboot
Type su in terminal and hit enter
Type props in terminal and hit enter
Change the fingerprint to Razer Android v9 and Reboot following the prompts.
Congratulations you now have LineageOS Android 10 and are passing safetynet.
Notes:
You can Install v4a if you want.
I highly suggest installing the l'speed module from Magisk as it stabilizes the freezing/kernel.
You can also Install EdXposed and the beta for GravityBox Q ... Still passing safetynet.
Logo++ will fix your Razer logo on the rear of device.
Bluetooth works fine as does everything I've tested.
Downloads needed:
Latest phh GSI for AOSP Android 10
Latest LineageOS 17.x GSI Image
Trinity Kernel (v2)
Magisk v20.3
Pico or Nano GAPPS from OpenGapps
Optional:
V4A (requires the Magisk Module Audio Modification Library)
EdXposed Riru - Core (Magisk Module)
EdXposed - Sandhook Beta / Canary (Installed from manager)
EdXposed - Latest Manager (do not use Taichi)
GravityBoxQ Beta (gives you a lot of customization like the battery icon in statusbar)
Logo+
LSpeed Module for Magisk (lspeed-master.zip)
F2FS_FSTAB.zip from ArterKernel Thread
***Note*** this isn't flawless but when using the LSpeed Magisk Module it's very close**"
**"" LineageOS Freezes every now and then where the AOSP GSI doesn't but I can't get the AOSP to pass safetynet***

Screenshots
Note I changed the font to Comfortaa via Magisk Font Changer Module

SafetyNet

Magisk modules I personally use. Ignore older versions of the same module.

Change the fingerprint to Razer Android v9 and Reboot following the prompts.
Click to expand...
Click to collapse
Will game booster work in cortex app?

I'm on T-mobile, and with every 10 Gsi I've tried, I've installed the required ims.apk. Unfortunately, I can only send sms, not recieve. Do you not have this problem?

Can you receive text messages through LTE? I can't seem to get it to work on T-mobile.

Reznor7 said:
I'm on T-mobile, and with every 10 Gsi I've tried, I've installed the required ims.apk. Unfortunately, I can only send sms, not recieve. Do you not have this problem?
Click to expand...
Click to collapse
Try moving the ims.apk to /vendor/overlay and see if that works.

Generic123. said:
Can you receive text messages through LTE? I can't seem to get it to work on T-mobile.
Click to expand...
Click to collapse
Generic123. said:
Try moving the ims.apk to /vendor/overlay and see if that works.
Click to expand...
Click to collapse
I've re-imaged my phone too many times already, losing countless hours going back to stock when the GSI doesn't work. I'll let someone else give it a shot.

Reznor7 said:
I'm on T-mobile, and with every 10 Gsi I've tried, I've installed the required ims.apk. Unfortunately, I can only send sms, not recieve. Do you not have this problem?
Click to expand...
Click to collapse
Reznor7 said:
I've re-imaged my phone too many times already, losing countless hours going back to stock when the GSI doesn't work. I'll let someone else give it a shot.
Click to expand...
Click to collapse
No doubt I'm through with flashing back to stock countless times.....so over it
Wish I had more time and knew more about Android to bake us up a solid AOSP ROM for this phone. Great hardware to work with here and like I've said before I can't believe there is not one Dev in this community to pick this phone up as cheap as it is and get something going

JDBarlow said:
No doubt I'm through with flashing back to stock countless times.....so over it
Wish I had more time and knew more about Android to bake us up a solid AOSP ROM for this phone. Great hardware to work with here and like I've said before I can't believe there is not one Dev in this community to pick this phone up as cheap as it is and get something going
Click to expand...
Click to collapse
I feel like it's the nature of ROM developers sticking to the devices they have. They are currently developing for other phones, and don't want to have to move/develop for a new phone, nor do they have the time to develop for another phone. To be fair, we are not completely in the dark; f(x)THaxxorX seems to be working on patched versions of popular GSIs that are more suited for the hardware of the RP2:
f(x)THaxxorX said:
What my real plan is to make patch into the GSI Sources before Building it.. Those patches include voLTE fix and other features. Integrate APTX coming from Razer GSI system.img.. and many more..
Click to expand...
Click to collapse

Generic123. said:
I feel like it's the nature of ROM developers sticking to the devices they have. They are currently developing for other phones, and don't want to have to move/develop for a new phone, nor do they have the time to develop for another phone. To be fair, we are not completely in the dark; f(x)THaxxorX seems to be working on a patched version of popular GSIs that are more suited for the hardware of the RP2:
Click to expand...
Click to collapse
Oh nice!
I'll try to contain myself and be a little more patient
So true, I can just imagine the time spent to be a developer for so many devices that are out there!
Happy Valentine's Day

Ugh. I don't know why I keep trying. SMS doesn't work over LTE on TMobile using this method either. OP, your profile says you're on TMobile. Have you solved this problem somehow?

Reznor7 said:
Ugh. I don't know why I keep trying. SMS doesn't work over LTE on TMobile using this method either. OP, your profile says you're on TMobile. Have you solved this problem somehow?
Click to expand...
Click to collapse
Are you still trying to use a Q GSI? If you are willing to go back to a Pie-based GSI, installing ims.apk and moving the apk to "/vendor/overlay/" works every time for me.

Generic123. said:
Are you still trying to use a Q GSI? If you are willing to go back to a Pie-based GSI, installing ims.apk and moving the apk to "/vendor/overlay/" works every time for me.
Click to expand...
Click to collapse
From my experience, Pie ROMs have issues with the fingerprint scanner reliability, and media in a lot of games seems to have buffering issues as it frequently cuts out.

Reznor7 said:
From my experience, Pie ROMs have issues with the fingerprint scanner reliability, and media in a lot of games seems to have buffering issues as it frequently cuts out.
Click to expand...
Click to collapse
I have the same problems on ArrowOS(the fingerprint sensor problem is pretty rare. The speaker issue is really annoying, but it only happens at low volumes), but I guess it depends on how much you're willing to take. If you want to keep to use Q GSIs, our best option is just to wait for patched GSIs by f(x)THaxxorX that might be coming out at some point(Soon™).

Reznor7 said:
From my experience, Pie ROMs have issues with the fingerprint scanner reliability, and media in a lot of games seems to have buffering issues as it frequently cuts out.
Click to expand...
Click to collapse
I think the speaker itself might have issues as I even had this issue with Android 9 GSIs, from what I remember. At first I suspected buffer-related issues but after some testing it doesn't seem to be the only issue. Setting the media volume to at least 50% would allow most of the audio to get out of the speaker, but at max volume the speaker can be really loud (to the point that I feel the speaker could be potentially damaged) so I usually set it to at most 80% when I need to place the phone a bit far from where I am.
Also, I haven't gotten aptX working on Android 10 GSIs due to a strange null pointer dereference bug which would crash the entire Bluetooth stack. Only SBC works as intended. As I noticed that the author of gjf_bt Magisk module (which adds aptX libraries as well as SBC tweaks) recently blacklisted Android 10 and onwards, I think the issue might have more to do with the Android 10 system itself.

Hey! Can anyone confirm if LDAC is working on this? I have never rooted a phone before just doing it to enable LDAC. Also, does this OS support setting for Refresh rate?

I love Lineage OS 17, but I noticed that I don't receive text messages anymore. I could receive text messages when I first flashed it, and after a couple of hours, I could not. Then, I could send messages and I could send and receive calls. I could use data. I could not receive text messages. Is there a fix for this problem? I tried using Lineage 16, but I still could not receive text messages. I am back to stock, for the moment. Does anyone know how to fix this? I'm using AT&T service.

Lorelily said:
I love Lineage OS 17, but I noticed that I don't receive text messages anymore. I could receive text messages when I first flashed it, and after a couple of hours, I could not. Then, I could send messages and I could send and receive calls. I could use data. I could not receive text messages. Is there a fix for this problem? I tried using Lineage 16, but I still could not receive text messages. I am back to stock, for the moment. Does anyone know how to fix this? I'm using AT&T service.
Click to expand...
Click to collapse
It's a known issue, and unfortunately there is no reliable fix yet.

UNOFFICIAL LineageOS 17.1 "SeLinux enforce mode" (Samsung Galaxy S6 - SM-G920F)

UNOFFICIAL LineageOS 17.1 "SeLinux enforce mode" (Samsung Galaxy S6 - SM-G920F)
Note:================
Tested ==> Samsung S6 (SM-G920F)(Zerofltexx)
========================
LineageOS is an operating system for smartphones, tablet computers, and set-top boxes, based on Android with mostly free and open-source software
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.
I've built this operating system with select userdebug .
It's unnoficial LineageOS17.1 for Galaxy S6 (ZEROFLTEXX)(SM-G920F).
I strongly recommend to perform a backup of your current rom before installation.
Tested ==> Samsung S6 (SM-G920F)(Zerofltexx)
SeLinux run in enforce mode,
also you can opt to have SeLinux run in permissive mode.
Installation process from stock rom
01. Boot into the download mode.
02. flash TWRP with Odin (comes in AP). The hooks at Auto Reboot and F. Reset Time out.
03. disconnect USB cable after flash, battery out and in again.
04. boot into recovery -> Allow Modifications
05. Advanced Wipe: Dalvik/ART Cache, System, Data, Internal Storage, Cache (lasts a while)
06. install -> select lineage image, then add more zips and gapps, then flash
07. patching system image unconditionally runs through with progress bar
08. Open Gapps are flashed, progress bar runs through
09. when done, tap reboot system, Swipe to install TWRP app (or not, if you don't need it)
10th reboot
11. Lot 17.1 boots. (quite a while ^^)
12. type through the facility
13. ready
Download:
==> tajaribsoft-en.blogspot.com/2020/09/unofficial-lineageos-171-samsung-galaxy.html
Because i'm new , i can't create link

Hi gapps included in ur ROM?
And can I install other boot.img files? I have tried that.
I know it won't work but a question..
Still will download and test..
---------- Post added at 07:25 AM ---------- Previous post was at 06:32 AM ----------
Almost everything works except Volume control while calling the same problem on 17.1 ROMs but everything else works fine I can just adjust volume from my file I'll just patch it with profile text lol thanks.. Very nice work ??????☎?

Yup this is my other account here.
and only on my laptop..
But i managed to get my favourite Kernel to be installed thanks to this beautiful work and kernel i installed is enforced and my ( favourite Kernel )
is pemissive so it depends on kernel and i don`t give a f... nice work man.. Thanks..
I can`t say thank you enough because i have tried other roms to get my thing install`d lol THANK YOU..

Are there any issues with audio on incoming or outgoing calls? Did you manage to get both the front and back cameras working? Most other custom roms have a combination of issues there.
EDIT: I just noticed Johannes did mention a call volume issue

add support 925f zeltexx pls

AnErare said:
Are there any issues with audio on incoming or outgoing calls? Did you manage to get both the front and back cameras working? Most other custom roms have a combination of issues there.
EDIT: I just noticed Johannes did mention a call volume issue
Click to expand...
Click to collapse
It has that same sound software problem.
But I think everything else is working. I try to restore boot from my previous backup it works but (sim not showing).
I try to restore other backup stuff but, of course did not working.
But it amazing i can use other kernel just by restoring from backup
They might be better ways to use other Rom's kernel.
I will use it like that soon without any possibility to have Sim card
I like my kernel lol..
This phone ( I ) use is near death so let end it Battery life with that Kernel I use... Lol
I'll test permissive only file download soon and try to restore boot from backup. And see
Or I should try to install Boot.img from the zip
Edit: It didn't work but first with enforcing SE always boot up no matter what i restore from my backup boot/cache/data/efs. I didn't test other rom enough yet.
And I will test more soon for fun..
Btw.. I got 3 mods installed on my backup so I'm gonna have to test new install's from all rom's and re-test from all over.. Or from start lol..
I want to know you guy's have any mods to make system faster or battery-friendly mods
I have added some text to build.prop and installed 3 mods I think. Maybe not all installs patches:
First for Fullscreen Gesture (Q) from Magisk modules.
Because my ROM is old and I removed some system apps.
And then I install kernel mod from this site. Lol (kTweak) it can be seen from Magisk
And 1 patch from here XDA post few days ago
And my build.prop tweak it looks funny:
ro.min_pointer_dur=0
ro.max_pointer_dur=40
wifi.supplicant_scan_interval=9000000000
windowsmgr.min_events_per_sec=0
windowsmgr.max_events_per_sec=60
debug.sf.nobootanimation=1
logcat.live=disable
ro.media.enc.jpeg.quality=100
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.mot.eri.losalert.delay.delay=1000000000
ro.kernel.checkjni=0
ro.kernel.android.checkjni=0
persist.android.strictmode=0
ro.config.nocheckin=1
That it if I didn't forget something
And make Settings less cpu hog or how to say make it CPU friendly lol .
1 more thing I have edited Sound mixer from System files
You can search it on my comments on my other account Johannes Davidsen
On Enezusun's 17.1 Lineage Os Multitarget rom
I couldn't post attachment's so I have to copied text
That all.
Here, there are 3 sections i think : https://forum.xda-developers.com/showpost.php?p=83187603&postcount=310

This ROM has still the sound volume issues, but camera is working here, right?
This one https://github.com/enesuzun2002/lineageos-ota/releases (28. Feb build) has working call volume and also working cameras, right?
The 13. April build of it has sound issues again and fast battery drain?
It's hard to keep track of what's working in each ROM build and what's not.

About Enes ROM
0x0rbit said:
This ROM has still the sound volume issues, but camera is working here, right?
This one https://github.com/enesuzun2002/lineageos-ota/releases (28. Feb build) has working call volume and also working cameras, right?
The 13. April build of it has sound issues again and fast battery drain?
It's hard to keep track of what's working in each ROM build and what's not.
Click to expand...
Click to collapse
Why don`t you test them by yourself sometimes same device have different problem with same rom and it is very confusing..
For me all of them have working camera and all of them have, calling sound software problem that i just fix by editing sound file..
Have a nice day..
And yes cam is working on this new august build,
same on sound problem too
---------- Post added at 08:13 AM ---------- Previous post was at 08:02 AM ----------
AnErare said:
Are there any issues with audio on incoming or outgoing calls? Did you manage to get both the front and back cameras working? Most other custom roms have a combination of issues there.
EDIT: I just noticed Johannes did mention a call volume issue
Click to expand...
Click to collapse
For me cam is working, only problem i so is the same software problem when trying to lowèr volume on calling or say on earpiece i`ll just replace sound file with the file i already have edited but it is very low.
You can test it i have commented on Enesuzun`s rom i think it started on page: 31 or 32 there are 3 comment sections i use for text
Here: https://forum.xda-developers.com/ga...ageos-17-1-t4053959/post83187603#post83187603

good

Nice work. Thanks for that selinux enforcing rom. Unfortuately I cannot enable encryption. After set in security settings the boot in a bootloop.

schlombie said:
Nice work. Thanks for that selinux enforcing rom. Unfortuately I cannot enable encryption. After set in security settings the boot in a bootloop.
Click to expand...
Click to collapse
I have exactly the same problem. And are there any other things to do to make the device even more secure? Some Modules ?

bemek01 said:
I have exactly the same problem. And are there any other things to do to make the device even more secure? Some Modules ?
Click to expand...
Click to collapse
My dirty trick to enable encryption was, I installed e rom for the device. Enabled encryption without a pin direct after the installation.
Than I installed the 17.1rom without format data. Only wipe system, data and the caches. The rom boot up allready encrypted.
I only set a pin and thats it.

hello or a little problem with the download link, just don't have the link, can you try s create a link on mega or google drive ???
to another thing i wanted to say, i am surprised that you are creating a rom for android 10 with the SElinux Enforcing, i wanted it a lot to increase the security, but the problem of this that lead to lose some battery, however i am interested to try this rom on my samsung galaxy s6 SM-920F i just have to understand where the link lol.
in my opinion, however, thanks to the rom with the SElinux Enforcing maybe this rom could become official if you want, and put on the lineage os website, but honestly I don't know how it works, this is just my opinion
I wanted to say another thing, that second it was better to do lineage os 16.1 because it is much more stable for this device, in fact existing official resurrection remix with android 9 that I use that not a bug, or tried official evolution x with android 10 but the problem of the wi fi that turns off and that you can disable it on the lock screen, and this and these 2 are a big problem, and that problem also exists in the lineage os 17.1 of another creator, everything to see if in the future when there will be lineage os 18.1 for this device with android 11 maybe the wi fi and lock screen security will work prevent you from turning off the wi fi from the lock screen
i am using google translator, hope the translation is right

schlombie said:
Than I installed the 17.1rom without format data. Only wipe system, data and the caches.
Click to expand...
Click to collapse
A wipe basically formats a partition, so what exactly do you mean, that you wiped the encryption too?
I'm sure this ROM doesn't support whatever encryption /e/ may support that you're suggesting.
But maybe I've got this all wrong

schlombie said:
My dirty trick to enable encryption was, I installed e rom for the device. Enabled encryption without a pin direct after the installation.
Than I installed the 17.1rom without format data. Only wipe system, data and the caches. The rom boot up allready encrypted.
I only set a pin and thats it.
Click to expand...
Click to collapse
Thanks. It works for me.
I have one problem with this rom. Bluetooth headphones don't work. I can connect to the phone but the conection is unstable and stop working. it something like: connected, not connected , connected, not connected each 10 seconds or so.
Sorry for my English thanks a lot for your attention.

gerardomare said:
Thanks. It works for me.
I have one problem with this rom. Bluetooth headphones don't work. I can connect to the phone but the conection is unstable and stop working. it something like: connected, not connected , connected, not connected each 10 seconds or so.
Sorry for my English thanks a lot for your attention.
Click to expand...
Click to collapse
Someone please can explain to me step by step how do this trick for enable encryption ?
I've tried 6 times and nothing works maybe I'm misleading something.

Hi, i just wanted to ask how you compiled lineageos for the s6. I tried to compile los 17.1 with the files provided by enesuzun and have massive problems with lunch detecting the files. Many are missing and even if i collect all it just acts weird. Since enes provided many working images these file should work to compile, don't they? Do you know any good tutorial? Most of them are only either for official builds or completely new unsupported devices.
Thank you in advance.
Chasbrot

What gapps? opengapps is provided for 10.0 only...
I have LOS 16.0 from enes but wanted to give it a try.
After wiping (system, cache, data) and installing this rom with opengapps 10.0 and magisk zips,
the reboot stucked in boot loop.

szazs89 said:
What gapps? opengapps is provided for 10.0 only...
I have LOS 16.0 from enes but wanted to give it a try.
After wiping (system, cache, data) and installing this rom with opengapps 10.0 and magisk zips,
the reboot stucked in boot loop.
Click to expand...
Click to collapse
For LOS 16, which is Android 9, you have to use the OpenGApps for Version 9. You can download them at the OpenGApps Project Homepage.
Try one step at a time when flashing or try the newest version from enes.

Chasbrot said:
For LOS 16, which is Android 9, you have to use the OpenGApps for Version 9. You can download them at the OpenGApps Project Homepage.
Try one step at a time when flashing or try the newest version from enes.
Click to expand...
Click to collapse
Oh, I mean: what gapps does this ROM (17.1) need? (with opengapps 10.0 I got into bootloop)