Database Users

Defy Green Lense MB525 bootloops/camera problems on Feb/Mar 2014 CM10.2/11 nightlies

I've had the trouble described in
http://forum.xda-developers.com/showpost.php?p=49962954&postcount=1775
What's worse, more recent builds have a kernel that bootloops for me. This thread has a solution.
Originally I was unsatisfied with CM11 nightly, because the camera crashed with a hard reset - heavy use of the gallery or taking a photo after a long time had triggered this hard reset reliably. So this problem was reproducable.
I upgraded CM11 nightly to latest 2014-03-30, just to find out recent kernels won't start at all or bootloop the green lense defy.
After that I wiped anything - flash SBF, Framaroot, 2ndinit, twrp_recovery_2.6.3.0.zip.
To confirm the device was working I flashed a couple of roms (CM9, CM10) builds from October 2013, they worked.
While testing I realized that these roms were a lot snappier than the CM11 one I was dissatisfied with, noticing that besides hard reset on camera usage I also had a lagging UI. I assume that SELinux might be one of the reasons for the camera hard resets I experienced, but have no proof for this..
Then I spent a couple of days debugging the problem and it turns out, that all of the problems arise indeed from the kernel used.
Atm, I run a butter smooth CM10.2 nightly rom dating 2014-03-31, but running on a kernel dating 2014-01-20 (ripped out of CM11-nightly!).
For this to happen, simply exchange zImage under /system/bootmenu/2nd-boot/
Extract zImage from 2014-01-20 rom beforehand, put it on sdcard.
After installing the latest rom, before rebooting, do
- Mount /system with TWRP
- Go to Tools > Filemanager
- Select the 2014-01-20 zImage in TWRP Filemanager
- Let TWRP copy it to /system/bootmenu/2nd-boot/ (overwriting the one that's in there)
- Wipe cache/dalvik
- Reboot
I have tested this setup and it runs amazingly! I tested GPS turning on an off, Camera works (except video with stock app), Wifi works - no reboots and the UI is a breeze. It simply behaves as it should. Neither zRAM or zCache is activated, battery consumption is low, as is CPU usage.
Conclusion: The latest nightly kernels suck hard for green lense defy, but I still do not know exactly why.
Fazit: Can confirm that zImage from 2014-01-20 is tried and tested.
===================================
How solution was found: I read in the forums, that update-recovery.zip contains a kernel. Since after flash of CM10.2-2014-03-31 I had bootloop problem, I went to TWRP recovery on blue led, which still worked, and installed update-recovery.zip AFTER rom. Normally, you do not do this, since this DOWNGRADES kernel. But if latest kernel does not work, there is a chance succeeding with this method.
Ok, after flashing update-recovery.zip zImage dating 2013-11-07 was in place and phone booted with CM10.2-2014-03-31 image. I thouhgt I had found the solution, but soon noticed, that this kernel had issued with GPS (it would hang and not turn off, once activated). The immediate next step was to look for a kernel built after 2013-11-07 - I tried with 2014-01-20, since this was the latest version offered by defy.bytekiste.de here:
http://defy.bytekiste.de/cm11-nightly-defy+/
Since, on defy.bytekiste.de CM10.2 listing stopped at 2013-10-30, and with update-recovery.zip I already had a kernel from 2013-11-07, I jumped to CM11 roms, as I did not know about existence of defy.svolkov.name at that time.
defy.svolkov.name lists CM10.2 nightly builds from 2014-01-09 on. One could probably try the kernels directly from these roms. However, I think the difference in kernels between CM10.2 and CM11 is neglectible. What matters is the timestamp of the builds - different timestamp, different kernel config and that seems to decide whether it's working on defy green lense or not.
===================================
I did not further bisect the problem yet, i.e. trying each nightly kernel built after 2014-01-20 in succession to see which build first caused the bootloop problem. However I've checked some of the roms and the file structure on quarx2k.ru and defy.bytekiste.de (you can find complete structure of both on http://defy.svolkov.name/), it's borked:
versions for cm-11-20131229-NIGHTLY-mb526.zip
886b1bfdeadada2f45c695e34e126d0c http://defy.bytekiste.de/cm11-nightly-defy+/cm-11-20131229-NIGHTLY-mb526.zip
886b1bfdeadada2f45c695e34e126d0c http://defy.svolkov.name/quarx2k.ru/cm11.0-nightly-defy+/cm-11-20131229-NIGHTLY-mb526.zip
versions for cm-11-20140117-NIGHTLY-mb526.zip
a936c82ad55fa488079b2a8796838678 http://defy.bytekiste.de/cm11-nightly-defy+/cm-11-20140117-NIGHTLY-mb526.zip
a936c82ad55fa488079b2a8796838678 http://defy.svolkov.name/quarx2k.ru/cm11.0-nightly-defy+/cm-11-20140117-NIGHTLY-mb526.zip
6e05a8e9205f30a212be5aafc6e4bc01 http://defy.svolkov.name/quarx2k.ru/roms/defy-cm11.0/cm-11-20140117-NIGHTLY-mb526.zip
now, from the above, if you thought
"defy.bytekiste.de/cm11-nightly-defy+" and
"defy.svolkov.name/quarx2k.ru/cm11.0-nightly-defy+"
were mirrors wrt same-named files, think again.
versions for cm-11-20140120-NIGHTLY-mb526.zip
0602c6090ffa169dcf249b49f3c1d2be http://defy.bytekiste.de/cm11-nightly-defy+/cm-11-20140120-NIGHTLY-mb526.zip (appears to have a different ramdisk-recovery, other files in 2nd-boot dir are identical to rom below)
d9a88dde07c06474d60dc353c53babc8 http://defy.svolkov.name/quarx2k.ru/cm11.0-nightly-defy+/cm-11-20140120-NIGHTLY-mb526.zip
also note,
"defy.svolkov.name/quarx2k.ru/roms/defy-cm11.0/"
holds the most recent list of nightlies, while the listing starts with
20140109 version, and continues until
20140117 version (see versions above)
it omits 20140120 completely, and then continues from
20140123 version.
===================================
I actually wanted to post this in dev forums CM10.2 on defy thread, but do not have more than 10 posts on xda-dev, so are not allowed to. This is why I post it here.

Thanks!
cmuelle8 said:
...
- Let TWRP copy it to /system/bootmenu/2nd-boot/ (overwriting the one that's in there)
...
I tried with 2014-01-20, since this was the latest version offered by defy.bytekiste.de here:
h t t p : / / d efy.bytekiste.d e/cm11-nightly-defy+/
...
Click to expand...
Click to collapse
Thanks for posting your findings. I first thought "it will be fixed soon" when my camera didn't work after a update. Then, because no one was complaining, i thought the camera in my Defy is broken.
I have almost done the same and now the camera is working again
1) extracted the zImage from 2014-01-20
2) "adb push" it to the sdcard
3) mount -o remount,rw /dev/block/mmcblk1p21 /system/
4) cd /system/bootstrap/2nd-boot
5) cp /sdcard/zImage .
6) reboot
7) happy

Any later kernels that show the same stability?
Edit: My Defy will not boot after replacing the kernel. I'm on cm-11-20140611 now.

I think you are refering to camera bug #44?
I have the same with my Defy green lense (MB525). I've found out that the bug was introduced in CM11 with the ROM from 2014-03-15. So the camera worked for me without problem until the ROM from 2014-03-13. Since then I have to set the minimum frequency at least to 600MHz. Below that value e.g. 500MHz I get indeed bootloopss when using camera or gallery. Disabling the HWA settings for the most apps (besides the camera) delayes only the unavoidably bootloop for some seconds.
Do you think it's possible to use the newest CM11 nightly ROM together with the last working ROM from 2014-03-13?

The camera-bug #44 still exists since the ROM_2014-03-15. But I think I could narrow down the problem a little. It seems to be the kernel, means the file "zImage" under /bootstrap/2nd-boot. When I took that file from the last working ROM_2014-03-13 and apply it to a later problematic ROM, then the bug #44 is gone (for me). I've successfully tested this workaround until the ROM-version from 2014-03-25. Since ROM_2014-04-01 and later this doesn't work because the phone wont start, maybe to much has changed within the ROM. The replacement (camera2.apk, MediaProvider.apk) or the deletion (wallpapper, etc.) of some system-apps leads to no success. Deactivating the autofocus-function or the GPS-tagging for the pictures doesnt help either. However, until now the phone reboots fairly fast when I scroll the taken pictures within the camera-app. Maybe it has something to do with my sdcard (read performance, whatever)?!?!? But the chance is very small, because it had worked outstanding until the ROMs before 2014-03-14 ;-(

[ROM][UNOFFICIAL] LineageOS 13.0 for Alcatel ONETOUCH IDOL 3 4.7

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

[ROM] LineageOS 14.1 w/ SonyLOS 7.1 binaries, AOSP Kernel, Viper4Android, Apollo

Hi,
in my spare free time I compiled a new unofficial LineageOS 14.1 ROM on my beloved Phenom II system with ECC RAM and made it available to you for 90 days from
https://www.filefactory.com/file/5fqmz223n9gx/lineage-14.1-20170403-UNOFFICIAL-SonyLOS-kugo.zip
https://www.filefactory.com/file/121p40o8v8gb/lineage-14.1-20170403-UNOFFICIAL-SonyLOS-kugo.zip.md5sum
The ROM can be installed through a recovery like TWRP. I also applied some modifications, in particular:
- the SonyLOS kernel has been replaced with the Sony AOSP version which seemed to be more up to date
- using some 7.1 binaries of Sony AOSP instead of the 7.0 binaries used earlier enabling some more features (?)
- replaced the LineageOS camera with the Simple Camera app
- integrated Total Commander, Apollo music player v2, SELinux permission changer and Viper4Android apps since I need them
Consequently,
- patchlevel now is March 5th, 2017
- the fingerprint sensor now seems to be usable to unlock your device
- the FM radio works (however, you have to manually scan through the stations once because automatically finding the stations initially still does not seem to work completely)
- the selfie camera image no longer will be upside down (seemed to be an issue with the LineageOS camera app, also will work correctly with i.e. Focal if you prefer a sophisticated app instead of Simple Camera)
- I can now use Apollo again as I did on the Z1 compact with CM 12
- the bass boost and equalizer are back with Viper, you just need to invoke the SELinux changer on the rooted device and install the drivers initially through Viper itself
Thanks fly out to Sony AOSP, SonyLOS and the app providers. Feedback is also very welcome.
Regards,
jtk_de
@admin: Could we please move this thread and my previous one to the ROM section ? I'm still not allowed to post something there

Great to see you're still updating your ROM. Don't understand why you upload at filefactory (sloooow download) instead of androidfilehost for example. Will flash your ROM tomorrow.
- should I flash a stock ROM first or does it not matter which version I'm coming from
- what do I need the .md5sum file for?
- gapps are not included, right?

I tried to use androidfilehost but my uploads got interrupted so I had to stick with filefactory for now. You don't need to flash the stock ROM first, just wipe the system, cache etc. partitions in your recovery and flash the .zip.
The md5sum checksum file is there to ensure the ROM integrity and is not needed for the flash, however, TWRP optionally can read it and veryify that the ROM has been correctly downloaded and copied to your phone's storage. Gapps is not included since I use alternative apps, hence it must be installed separately.
Root access is integrated already and can be controlled via the developer settings. The only issue I experienced so far is that the volume cannot be altered yet during phone calls

I don't get viper4android to work. I install the drivers, reboot my device and then viper4android prompts me to install the drivers again. Am I doing something wrong?

Micka84 said:
I don't get viper4android to work. I install the drivers, reboot my device and then viper4android prompts me to install the drivers again. Am I doing something wrong?
Click to expand...
Click to collapse
You need to enable root first and start the SELinuxModeChanger installed with the ROM and set SELinux to "Permissive". Then the Viper drivers can be installed which can take quite long (a minute or so). If an Android dialog pops up because of this confirm that you would like to wait longer. Then reboot as indicated and enjoy the bass

That worked for me thank you

Hey,
many thanks for that ROM. Unfortunately i end up in a never ending boot animation. If i get in recovery (TWRP) and tell him to reboot, it tells me that no OS is installed. Any hints how this can be solved?
Thanks for any advice!

dreadavi said:
Hey,
many thanks for that ROM. Unfortunately i end up in a never ending boot animation. If i get in recovery (TWRP) and tell him to reboot, it tells me that no OS is installed. Any hints how this can be solved?
Thanks for any advice!
Click to expand...
Click to collapse
Hi!
I think there aren't any os on your device, thats wha twrp sad that... because, your systems encrypted. You could remove it. Try to flash again twrp from fastboot, than clear cache ( fastboot format cache ) and userdata ( fastboot format userdata ) from flashtools too. After that boot to twrp, than you could mount system, than flash the whole cm rom again. After that, i think it will boot correctly.

lba810701 said:
Hi!
I think there aren't any os on your device, thats wha twrp sad that... because, your systems encrypted. You could remove it. Try to flash again twrp from fastboot, than clear cache ( fastboot format cache ) and userdata ( fastboot format userdata ) from flashtools too. After that boot to twrp, than you could mount system, than flash the whole cm rom again. After that, i think it will boot correctly.
Click to expand...
Click to collapse
Thanks for the hint. Did what you said, but i cant mount system in recovery. It cant be selected in the list. Any other suggestions? Ok solved it. had to flash stock rom and boot.img before the steps you asked me to try. Thank you!

Thank you for putting this ROM together! There are the following problems on the OmniROM:
1. Incall speaker volume is not controllable
2. Slight incall echo on receiving side
3. Double tap to wake doesn't work
Is this still the case for your Lineage ROM?

avion540 said:
Thank you for putting this ROM together! There are the following problems on the OmniROM:
1. Incall speaker volume is not controllable
2. Slight incall echo on receiving side
3. Double tap to wake doesn't work
Is this still the case for your Lineage ROM?
Click to expand...
Click to collapse
1. Yes, the volume can't be changed during phonecalls
2. Didn't notice any echos so far
3. True

Could you try uploading to mega.nz? FileFactory is so slow

minimum Brightness
Hey!
i was just wondering if its possible to lower the minimal brightness a bit more. because minimal brightness is quite bright still. Im using this ROM for a few days now. Everything works pretty fine, but the battery life is a bit short for what i was expecting. If i dont use extreme battery saving mode its always around 24 hours. i barely do phone calls and i use it not very intensively... Highest Consumer is standby with 5%, which i think is wierd, isn´t it?

:good: Kudos. Everything seems to work well aside from the Bluetooth Audio cutting out after a few minutes. Overall I am really happy with it - happy enough that it's my daily driver.

Hi!
ROM will be better and better. Thanks.
Battery charging speed a bit slow, and if I'm using a mobil net, it's draining a little fast, plus in the evening, with wifi on, it goes down nearly 5%>. Camera is good. But, im using open cam software from google play. Fingerprint sensor working good, just a little hard to configure it. I'm using substratum theme engine, and i can theme most of the base and google apps. ( Except fingerprint sensor, with themed settings, the fingerprint setup screen cracked... but inthinknits theme problem ) And about bluethooth.. yes, it's dropping the connection after a few secs. But, if you left it, then reconnect automatically and just after that, it goes good. Until you turn it off. I used a sony sbh70 wireless headset with power amp.
And echo sound in calling. I can't hear echo, but other peoples in line, they sad it. They hear onselfs twice.. :/
If you would like it, maybe i can upload a logfile ( with matlog ) about the bluethooth problem.
Anyway, thanks foe thiese rom for our x compact.

It's good to see some other people are using the ROM and testing things that I can't test
According to my own experience battery lifetime is around 2-3 days when surfing via wi-fi, listening to music and calling from time to time. Battery charging with the Sony AC adapter coming with the phone is quite quick compared to the Z1C although the battery capacity is higher.
If I make another build I'll upload it to some faster provider though.

hello all,
give it some news there? Last entry April 2017.....

Hi all, are there some updates? I love Lineage OS

I'm wondering why there isn't an official build for the Xperia X Compact yet ? If I google "kugo lineageos" I get a hit for a stats page:
https://stats.lineageos.org/model/kugo
Which just says the page isn't rendered yet, but obviously someone has been devoting his/her time to the kugo. What could be the hold up? Same goes for the lack of other roms btw. It seems Sony is quite open towards the community but somehow this hasn't resulted in the overwhelming amount of roms I was hoping for ... It's quite underwhelming in fact. Could it be not enough (knowledgable) people own an Xperia X Compact ?

harryharryharry said:
It seems Sony is quite open towards the community but somehow this hasn't resulted in the overwhelming amount of roms I was hoping for ... It's quite underwhelming in fact. Could it be not enough (knowledgable) people own an Xperia X Compact ?
Click to expand...
Click to collapse
Sony gives us a sliver of what is needed for AOSP to run, camera, bluetooth, wifi, and radio band stuff all has to be manually made to work. The z3 line was the ONLY xperia line to ever get mainstream AOSP support from devs. If you bought your xperia thinking Sony's AOSP program was good you were sadly mistaken.

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.

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)