Related
I am on Note 4 Alpha S6 Revolution rom, with NK1 baseband and 3.4.0-Motion V2 kernel by aapav.
For Private Mode, I tried a few things like reinstalling by copying PersonalPageService.apk in system apps, using XSecureStorage in Xposed, after that tried with uninstalling Xposed.
But none of them could get it worked.
Each time after turning it on, it says "Failed to enable Private Mode. Try again".
I've googled and searched a lot of forums also but there's no solution, maybe some of you can help me.
Because the other rom which operates on almost same features and firmware kitkat has the private mode running smoothly(i.e. S6 Styled S5 Port Rom),
I'm unable to understand the difference, if some of you can help or give some tips, it would be nice.
Must reply.
Thanks.
Status:
It still needs some polishing and cleaning up, and there are unresolved issues but nothing serious (check below). Based on user reports this is pretty usable. Battery and performance are both at least as good as stock, with the added benefit of having doze support, being less bloated, coming rooted etc.
Credits:
This wouldn't be possible without DeckerSU's post with an official MM rom. I've used his file to extract the binary stuff.
I've also cloned his device tree to build TWRP on omnirom since I was having a hard time building it on CM.
I started by cloning pivoq's device tree for CM12.1. So credit goes out to him too.
Those are just the things I've used directly but looking at other people's code also helped a ton to figure things out. So I guess credits goes also to the whole community/ecosystem.
Known Issues:
Smart lock isn't preserving settings across reboots. (If anyone is willing to test this and contact me, it can probably be fixed easily)
The bundled camera app (Snap) works well. Stock camera app works well as well (doesn't come with the ROM, maybe I'll provide a zip in the future). But some cam apps have issues.
Not Working / Enabled / Unknown:
Flip cover.
Drm?
Fastdormancy?
No NFC icon on statusbar. ** Won't fix ** - AOSP or CyanogenMod do not have such an icon. Some vendors add it. As such I don't think ROM should come with it by default. Either there's an exposed module for it that people can install, or a flashable zip can be made to add it. I think that's the better route rather than have the ROM come with it.
CNE - ** Won't fix ** - Disabled by choice. It's an anti-feature in my opinion.
Notes:
Doze: Officially doze requires a special motion sensor that our device does not have. Motion will not keep the device from dozing, or awake it. Also, doze by default takes a long time to kick in (about ~1h), and I would advise people to tweak those timings to their usage patterns with Doze Settings Editor (http://forum.xda-developers.com/android/apps-games/root-doze-settings-editor-android-t3235130), or some other app like Greenify / Nap time. Lastly doze is supposed to work with GCM, which isn't available on the ROM by default unless you install google apps or an adequate substitute.
XPosed: works with v87+.
SELinux: I've seen a lot of people setting selinux to permissive, often because of some xposed module. SELinux is an integral part of android's security. Things are already pretty bad with it, disabling it isn't recommended. While there will still be many security bugs, often selinux limits their scope or makes it so that multiple bugs will be required for successful explotation. No xposed module is worth that.
Download:
LineageOS 09/04/2017:
https://www.androidfilehost.com/?fid=745425885120723074
TWRP 3.1.0:
https://www.androidfilehost.com/?fid=817550096634753196
- The recovery has support for encryption and adopted storage (including mixed mode).
ROM Changelog:
** 09/04/2017 **
Code:
- April security patch level
- Kernel sync to 1.2.7-rb1.41
** 25/03/2017 **
Code:
- March security patch level
**13/03/2017**
Code:
- Move on to LineageOS
- Fix wifi tethering
- Fix OpenGapps issues
- February 01 security patch level
- Sync kernel to LA.BR.1.2.7_rb1.40
** 16/12/2016 **
Code:
- December 01 security patch level
** 09/12/2016 **
Code:
- Updated kernel for CVE-2016-5195 (November 06 security patch level now).
- Added ZEN IO Scheduler
- Tweaked cpu governor, 200Mhz+ clock (from 533).
- Added zram.
** 25/11/2016 **
Code:
- Fixed SIM regression for dual sim variants.
- Added F2FS support for data and cache (Beware recovery linked above wasn't updated)
- Tweaked minimum brightness setting
- Added 533Mhz as lowest frequency for cpu (from 800Mhz).
- Removed wifi dual band (device doesn't support 5Ghz).
- Compatible with microG/UnifiedNLP:
Permission for signature spoofing (don't give this to apps unless you know what you're doing).
Added location overlays for UnifiedNlp.
** 23/11/2016 **
Code:
- Fixed reported regressions. Unsure about the SIM one,hopefully it's fixed too.
** 21/11/2016 **
Code:
- Fixed modem battery drain
- Fixed FM radio (new app)
- Fixed camera (new app, Snap). As far as i've noticed everything's working under this app.
- Enabled Doze.
- Fixed operator name showing as numerical ID.
- Changed LTE label to 4G.
- November 5 security patch level.
** 09/11/2016 **
Code:
- Fixed wrong power accounting for bluetooth
- Updated wlan firmware blob
** 08/11/2016 **
Code:
- Fixed leds regression
- Fixed location battery drain
- FM radio kind of working:
(to hear sound you need to turn bluetooth on, you can turn it off again afterwards)
- Front camera isn't dark anymore but still crashes with HDR. Cam still has issues but is usable.
- Post processing daemon isn't crashing anymore, which was leading to some hiccups.
- Advanced reboot should be working for everyone now
- IRQ Balancing
- Added cne/dpm vendor libs. Haven't tested further so CNE might be working.
- Minor tweaks/fixes, some selinux stuff.
** 30/10/2016 **
Code:
- Correct variant should now be detected and multisim set up accordingly.
- Built without microG patch (which was incompatible with google apps)
** 27/10/2016 **
Code:
- Fixed camera. Had made a mistake while building previous rom.
(This is not a fix for the front camera darkness issue.)
Recovery Changelog:
**14/03/2017**
Code:
- Update to twrp 3.1.0
**21/01/2017**
Code:
- Update to twrp 3.0.3, fixes .img flashing.
- Removed superfluous mouse pointer.
- Updated kernel with current f2fs support.
Code:
I'm currently creating my first github account etc. As I find the time to clean up the commit history and set things up properly I'll update the post with links to the device tree and kernel sources.
I've decided to post now, perhaps prematurely, because I'm very limited on time I can spend on this (can't afford it). I'm also unsure if there's even many people interested. So the best way forward if there's interest is either other people joining in and carrying this further, or supporting development with some donations.
Donations:
So far got 9 donations.
$50 < Total donations < $100.
Thanks to anyone who's donated and has shown appreciation!.
reserved.
Cool nice to see devrlopment to the 4.7 idol, I'm still waiting for the official marshmallow update (europeu representativas on Twitter and Facebook keep saying its coming) but if that takes too long I might get to use this rom
wow, i never thought that we will ever get cm13! thank you for your hard work! please, don't give up!
Rom is Very good.
downloading it now, i'll have time to flash the rom tonight
does xposed work?
basic functions like phone, sms, 2g, wifi work without any problem?
what about battery?
jani0417 said:
downloading it now, i'll have time to flash the rom tonight
does xposed work?
basic functions like phone, sms, 2g, wifi work without any problem?
what about battery?
Click to expand...
Click to collapse
I noticed I made a mistake on this build and as such the camera is broken. I'm gonna make a new build in a couple hours.
Never tried xposed.
Basic functions are all working for me. At least for the 6039Y I think it should work but we'll find out if people leave feedback. My guess is that it's probably working, with the exception of maybe dual sim variants.
Wifi should be working. Qualcomm CNE isn't, and I'm unsure if I even want it as a feature, need to research on it.
I haven't thought of a way to measure battery performance but I'm using it on my phone daily. If it's worse than it should be it's not by a very large margin. I also haven't run any kind of benchmark. (Too early for that in my opinion).
Thx,
for your work on CM13 for 4,7" Variant. If you upload new build with fixed camera i will test it on my europe 6039Y and leave feedback here.
Have a nice day
alecbl said:
I noticed I made a mistake on this build and as such the camera is broken. I'm gonna make a new build in a couple hours.
Click to expand...
Click to collapse
thank you, i'll check it tonight before flashing. i'd do it now but i'm waiting for important calls
Basic functions are all working for me. At least for the 6039Y
Click to expand...
Click to collapse
perfect i also have an 6039Y (2AALWE7)
Wifi should be working. Qualcomm CNE isn't, and I'm unsure if I even want it as a feature, need to research on it.
Click to expand...
Click to collapse
as for me, i hate it.
i'm using profiles to make sure that when my wifi is on, data is off and vice versa. earlier i had surprising phone bills because of this feature :silly:
I haven't thought of a way to measure battery performance but I'm using it on my phone daily
Click to expand...
Click to collapse
perfect :good:
and again: THANK YOU :good:
Updated original post. Cam should be working now.
Thank you very much! I really liked the hardware, but missing the MM update. But CM13 is even better:good::good:
First time I got into a bootloot updating from CM12.1, had to change data and cache filesystem back to ext4, don't forget.
Gonna test it now, hopefully you can merge the latests @Unjustified Dev commits when he makes them public aswell
Phantom410 said:
First time I got into a bootloot updating from CM12.1, had to change data and cache filesystem back to ext4, don't forget.
Gonna test it now, hopefully you can merge the latests @Unjustified Dev commits when he makes them public aswell
Click to expand...
Click to collapse
Yes, I haven't enabled f2fs support yet. I intend to do it at some point. Pivoq had a kernel source tree in which he updated f2fs, supporting xattr etc. I haven't figured out where did he import those changes from yet. I wanted to do the same, but didn't want to import from him because that's not being kept in sync with upstream.
What commits are you talking about?
Xposed work perfectly.
Nice,
i have installed at this time incl. xposed , but without gapps. After first setup all OK. In the next days i test with all my apps and give you feedback. I`m hopefully. :good:
This is the greatest thing to ever happen to my Idol.
Thank you so much. Root and Xposed work fine. Latest version of Busybox installed fine.
Flashed Gapps Pico successfully.
Seems to be really smooth but time will tell. Themes work perfectly.
Using the advanced reboot menu to try and reboot into recovery doesn't work. Granted i'm not using the recovery linked in the original post. I'm using the recovery made by DeckerSU.
What recovery is linked in your post? Is it Cyanogenmod recovery or TWRP and if so, what version?
EDIT: Not even "Adb reboot recovery" will get the device to boot into recovery anymore. Hmm...
Wow, just wow. You did more in one day, than some of the "DEV's" here for their entire time good job man.
Sparkey159 said:
This is the greatest thing to ever happen to my Idol.
Thank you so much. Root and Xposed work fine. Latest version of Busybox installed fine.
Flashed Gapps Pico successfully.
Seems to be really smooth but time will tell. Themes work perfectly.
Using the advanced reboot menu to try and reboot into recovery doesn't work. Granted i'm not using the recovery linked in the original post. I'm using the recovery made by DeckerSU.
What recovery is linked in your post? Is it Cyanogenmod recovery or TWRP and if so, what version?
EDIT: Not even "Adb reboot recovery" will get the device to boot into recovery anymore. Hmm...
Click to expand...
Click to collapse
I have a very good idea of why that's happening. Did you happen to change your bootloader at any point? Alcatel's kernel source has a non standard way of handling reboot, what's more, it's not exactly the same in their lollipop vs marshmallow sources.
The recovery in the post is twrp 3.0.2 with support for encryption and adopted storage. It's using the same kernel, so if you flash that recovery what I expect will happen is that you wont be able to reboot into bootloader or reboot into recovery from the recovery either. The decision of where to reboot into is done by the bootloader and precedes the kernel, just so you know. Changing the recovery can't fix that. Of course you can always do so using power+volume keys, until I fix it.
alecbl said:
I have a very good idea of why that's happening. Did you happen to change your bootloader at any point? Alcatel's kernel source has a non standard way of handling reboot, what's more, it's not exactly the same in their lollipop vs marshmallow sources.
The recovery in the post is twrp 3.0.2 with support for encryption and adopted storage. It's using the same kernel, so if you flash that recovery what I expect will happen is that you wont be able to reboot into bootloader or reboot into recovery from the recovery either. The decision of where to reboot into is done by the bootloader and precedes the kernel, just so you know. Changing the recovery can't fix that. Of course you can always do so using power+volume keys, until I fix it.
Click to expand...
Click to collapse
I don't think I've changed the bootloader since I got the device. I don't have access to fastboot commands. My idol was a O2 branded one that I brought quite recently. I haven't been able to use Petrov.0's method of restoring the fastboot commands either. I don't really mind losing the ability to reboot into recovery from the system since its worth it for Android Marshmallow.
Thanks, I'll be using your recovery from now on too since its more updated. :good:
Flashed, tested
-unlocked 6039Y 2AALWE7
-tap to wake/sleep works
-sms, phone, wifi works
-gapps works
-front camera in photo mode really dark, in video mode is okay
-tried Google Camera from play store, it crashes everytime, when switching from video to photo mode
-so far I love this rom
Hi everyone!
We've got three Redmi Pro in our family (two 3/64 GB and one 4/128 GB) - and unfortunately, two of them have the very same MAC-Adress. And this causes constant WiFi-Problems!
I tried almost every App and the Engeneer Mode to change the WLAN-MAC-Adress on my Redmi Pro Exclusive 4/128 GB (MIUI 8.3 from xiaomi.eu, TWRP 3.1.1, SuperSu 2.82, Xposed Framework, BusyBox, SELinux Toggler,....) - but nothing worked.
In another thread somebody with a Redmi Note 4 (MTK X20) succeded with changing SELinux to permissive and then using ChameleMAC and/or Engeneer Mode. This made me optimistic, because the CPU is quite similar to our MTK X25....
But ChameleMAC says "Device not supported" and in Engeneer Mode, I can't change the adress either (also I "write" a new MAC-Adress several times...)
Any ideas or solutions? Every help is greatly appreciated!
UPDATE!
I could install the SELinux Toggler by flashing the ZIP with TWRP... and could finally change the WLAN-MAC-Adress (after a few attempts) with SELinux set to permissive and writing a new MAC-Adress within the Engeneer Mode...
The only strange thing is, that after the first reboot the MAC-Adress changed again to a completely new one. But since then, it stays the same so far...
If you haven't already, try a MAC spoofer - it won't change your mac permanently, but will temporarily change it to something else. Here's a tutorial.
Finally succeded in changing my WLAN-MAC-Adress....but
theOriginalSuperl2 said:
If you haven't already, try a MAC spoofer - it won't change your mac permanently, but will temporarily change it to something else. Here's a tutorial.
Click to expand...
Click to collapse
Thanks for the tipp - but none of the MAC spoofers worked either...
But somehow I managed to change my WLAN-MAC-Adress with SELinux changed to permissive and writing a new MAC-Adress within the Engeneer Mode...
The only thing that is strange is, that after a reboot, I have a different (complete new) MAC-Adress...!?
Solutionman said:
Hi everyone!
We've got three Redmi Pro in our family (two 3/64 GB and one 4/128 GB) - and unfortunately, two of them have the very same MAC-Adress. And this causes constant WiFi-Problems!
I tried almost every App and the Engeneer Mode to change the WLAN-MAC-Adress on my Redmi Pro Exclusive 4/128 GB (MIUI 8.3 from xiaomi.eu, TWRP 3.1.1, SuperSu 2.82, Xposed Framework, BusyBox, SELinux Toggler,....) - but nothing worked.
In another thread somebody with a Redmi Note 4 (MTK X20) succeded with changing SELinux to permissive and then using ChameleMAC and/or Engeneer Mode. This made me optimistic, because the CPU is quite similar to our MTK X25....
But ChameleMAC says "Device not supported" and in Engeneer Mode, I can't change the adress either (also I "write" a new MAC-Adress several times...)
Any ideas or solutions? Every help is greatly appreciated!
UPDATE!
I could install the SELinux Toggler by flashing the ZIP with TWRP... and could finally change the WLAN-MAC-Adress (after a few attempts) with SELinux set to permissive and writing a new MAC-Adress within the Engeneer Mode...
The only strange thing is, that after the first reboot the MAC-Adress changed again to a completely new one. But since then, it stays the same so far...
Click to expand...
Click to collapse
for the snapdragon series (mido) is not permanent using change mac or the type of application in the play store ..., when restarting android he will return as before. you have to use QPTS to be permanent .. i have reset several times and its result is permanent. i think problem mac macress error can be resolved.
Hello there!
I recently came out on a post about Dual Boot your android device.
This seems really handy to me so i was willing to try it.
I rooted my S7 Edge, i have Magisk installed and the Dual Boot Patcher.
I tried tons of roms like: DOTOS, RR, LineageOS, Ice Projects and so on.
Everytime when i try to flash the zip i patched it gives me an error.
But every time another error.
For example with Dot.OS i got:
Failed to copy /raw/data/,system.img.tmp to /raw/system/multiboot/dual/system
But when i try for example LineageOS the app just stops working.
Also i tried some other roms which gave an error about the system check. If my device was compatbale with the ROM.
I saw alot of issues about that online so i tried all those fixes but nothing seems to help.
I tried to delete the Asserts line from the updater-script. How ever only 1 rom i downloaded got these lines in the file.
I am really stuck and have no idea what to do now.
Is this because of my phone? Do i need to install another APP or anything to fix this issue?
I really wanna install this Dual Boot. And i saw many people successfully flashing on S7 Edge. So its pretty strange it doesnt work for me...
If there is some one with a solution or maybe someone that wanna take a look with me to fix my issue woukd be highly apprecieted!
Also i dont mind to pay a few bucks to a dev or anyone with more knowledge to take a look and try to fix this issue with me if no one else can!
Thank you in advance! Please let me know if you need more information about these issues and please tell me which info.
As i had no idea what to all post here to make it easier to locate the issue.
Thank you all!
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)