[ROM+KERNEL][CAN-L11][UNOFFICIAL] LineageOS 13.0 [11.08.2017] - Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &

[ROM+KERNEL][CAN-L11][UNOFFICIAL] LineageOS 13.0 [11.08.2017] - Huawei Nova/Nova Plus ROMs, Kernels, Recoveries, &

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[COLOR=167c80]LineageOS 13.0 for Huawei Nova CAN-L11[/COLOR]
DISCLAIMER:
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
NOTES - MUST READ
1. All credits goes to @Grarak for making the sources. I've only built LOS using his sources. Also I've been able to build by using Google Cloud platform since my PC is crap... It took me 1h 30m to build with Google Cloud platform, while with my PC was still building after 7h of building and then got an error regarding my PC (was too slow or out of memory).
2. Don't use encryption. I don't know why, but Grarak mentioned this on his twitter at the last build for CAN-L01.
Click to expand...
Click to collapse
[COLOR=167c80]Requirements[/COLOR]
- Huawei Nova CAN-L11
- EMUI 4.1 (Android 6.0). I've flashed it successfully from EMUI 5 ( Android 7.0) too and I didn't encounter any problems.
- Unlocked bootloader ( here's a guide about how to unlock it)
- TWRP by @Grarak. I've been on his TWRP while flashing LOS. I don't know if it works with other TWRP.
Click to expand...
Click to collapse
[COLOR=167c80]Installation[/COLOR]
Make sure you meet the requirements listed above.
1. Download the ROM and put it on sdcard. If you want GAPPS too, then download Open Gapps too (choose arm64, 6.0 and pico).
2. Reboot in TWRP by pressing all 3 buttons (Volume UP + Volume Down + Power).
3. Wipe system, data, cache and dalvik-cache.
4. Flash the ROM from the directory where you've placed it.
5. Flash GAPPS (OPTIONALLY).
6. Reboot.
Click to expand...
Click to collapse
[COLOR=167c80]Download[/COLOR]
ANDROIDFILEHOST | MEDIAFIRE
[COLOR=167c80]Sources[/COLOR]
Device https://github.com/skinzor/android_device_huawei_can/tree/cm13.0 (it's the same device tree made by Grarak, just that I've corrected the partition sizes for CAN-L11).
Vendor: https://github.com/skinzor/proprietary_vendor_huawei/tree/cm13.0
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953/tree/cm13.0
Click to expand...
Click to collapse
[COLOR=167c80]Credits[/COLOR]
@Grarak for the sources
@FrozenCow
@franciscofranco
@flar2
@Sultanxda
@ Google for their cloud platform and free trial
@ LineageOS
@ Huawei
XDA:DevDB Information
[ROM+KERNEL][CAN-L11][UNOFFICIAL] LineageOS 13.0 [11.08.2017], ROM for the Huawei Nova/Nova Plus
Contributors
#Henkate, Grarak
Source Code: https://github.com/skinzor/android_kernel_huawei_msm8953/tree/cm13.0
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: Unlocked bootloader, TWRP, EMUI 4.1 (Android 6.0)
Version Information
Status: Stable
Stable Release Date: 2017-08-11
Created 2017-05-26
Last Updated 2017-08-11

Changelog & bugs
Bugs
- FM-Radio
- signal icon becomes empty / gray when you are using 3G, but the network is working
- camera recording / video playback issues (sometimes, when you play the recorded video it gets stuck / frozen)
If you've found a bug, please report it along with a logcat.
Changelog
11.08.2017
ROM:
- 1 July 2017 security patch
- switched to Snap Camera (quality seems to be much better as I've said in one of my previous posts)
- added microG support (signature spoofing)
- fixed NFC
- fixed Dual SIM - thanks to @Yohannj who for this
- ROOT is now included (LOS`s root)
- added more blobs: OMX, IMS, CNE / DPM
- disabled LiveDisplay by default
- got rid of CM Updater since we don't have official LOS
- bluetooth name was set to "HUAWEI Nova" as default
- increased ZRAM to 1gb and applied other changes/settings as EMUI 5 (in my opinion, multitasking seems to be better)
- added ext4 support for /data
- added f2fs support for /cache
KERNEL:
- re-enabled cleancache and zcache
- applied a patch to allow 200 swappiness (for zram)
Click to expand...
Click to collapse
02.06.2017
ROM:
- sdcard problem was fixed (in first release, the sdcard wasnt recognized in other apps other than Documents app and neither MTP)
- added glove mode (Settings > Display > High Touch Sensitivity)
KERNEL:
- CRC toggle; enabled by default (disable it for 30% performance improvement at the risk of data corruption, according to its description)
- FSYNC toggle; enabled by default (disable it to possibly increase performace at the risk of data corruption
- CPU Boost toggle; disabled by default
- KCAL: Advanced color control (RGB, Saturation, Value, Contrast, Hue)
- Vibration intensity control
- SafetyNet pass
- I/O schedulers: added SIO, SIOPLUS, FIOPS, ZEN, BFQ, tripndroid
- governors: added blu_active
- DriveDroid support: allows you to boot your PC from ISO/IMG files stored on your phone [UNTESTED]
- QuickWakeup driver: Allow kernel driver to do periodic jobs without resuming the full system. It can increase the battery life.
- Zen-tune: Tunes the kernel for responsiveness at the cost of throughput and power usage.
- enabled Power Efficient Workqueues: it should increase the battery life. There is also a toggle.
- enabled advanced TCP congestions: Westwood, HSTCP, HYBLA, HTCP, Vegas, Veno, Scalable, LP, Yeah, Illinois
- misc fixes
Click to expand...
Click to collapse
26.05.2017
- initial build
Click to expand...
Click to collapse

Reserved

It goes fine on my AL10, and the SD card issue I had was solved with:
Code:
sm storage-force-adaptable yes
I posted that in the other lineage thread.
My question would now be how is this different than the other build?
---------- Post added at 06:06 AM ---------- Previous post was at 05:59 AM ----------
Only other thing I will mention, I use gravity box for minor status bar tweaks (the percent seems to not natively stay in the circle) and pie control with no nav bar (more screen for me). If you touch lockscreen stuff in gravity box you will make your lockscreen insecure. It will be a simple swipe in order to get to your phone. I know gravity box should not be used with lineage, but I mention it as I encountered it.

wangdaning said:
It goes fine on my AL10, and the SD card issue I had was solved with:
Code:
sm storage-force-adaptable yes
I posted that in the other lineage thread.
Click to expand...
Click to collapse
Thanks for this tip. I understand that this command enables adoptable storage, but I don't want to use adoptable storage as it may slow down the phone. Also, by using this command, the sdcard gets formatted too?
My question would now be how is this different than the other build?
Click to expand...
Click to collapse
The CAN-L01 build couldn't be flashed on CAN-L11 because the partition sizes defined in BoardConfig.mk were L01 ones which were bigger than L11 ones and upon flashing L01 build I was getting an error saying that it's too big.
I've corrected the partition sizes for L11 and built it. That's the only change.

It seems that the sdcard can be accessed through /mnt/media_rw/9016-4EF8, assuming you're rooted.
I'm still trying to figure out what's wrong.

I see, when I ran the command posted above my SD card was visible in other file explorers.

wangdaning said:
I see, when I ran the command posted above my SD card was visible in other file explorers.
Click to expand...
Click to collapse
Ive just fixed the sdcard issue. It seems that the problem was in fstab.qcom.
Ill make some other changes and then ill make a new build.

Good man, just wonder if your build will run on my device.

hi
tnx for your work.can we (owner of nova plus)use this rom?

wangdaning said:
Good man, just wonder if your build will run on my device.
Click to expand...
Click to collapse
It should work as long as it flash successfully. It's the same ROM as L01 one just that it has the partition sizes modified for L11, so it should work. If it gets stuck in recovery while flashing, then it means that the L11 partition sizes "doesn't fit" your model.
at.great said:
hi
tnx for your work.can we (owner of nova plus)use this rom?
Click to expand...
Click to collapse
I don't know, you can try to flash and report whether it works or not. As always, take a backup before.

coool!!!NOVA user's appreciation

Hello
Does anybody have the camera working?

I will give it a shot next weekend, kind of need my phone to work during the week. I wonder if we start a partition table thread if that would be helpful. It was my understanding that most of the partitions are the same except userdata, which is based on variant.

Wahbax said:
Hello
Does anybody have the camera working?
Click to expand...
Click to collapse
Yes, the camera is working. The bugs are mentioned in post #2.
wangdaning said:
I will give it a shot next weekend, kind of need my phone to work during the week. I wonder if we start a partition table thread if that would be helpful. It was my understanding that most of the partitions are the same except userdata, which is based on variant.
Click to expand...
Click to collapse
Well, i guees that would be helpful assuming people will post their partition table. Here I've wrote how to check the partition sizes.

#Henkate said:
Yes, the camera is working. The bugs are mentioned in post #2.
Click to expand...
Click to collapse
Thanks for the quick response. I followed the guide step by step and I always get this message in camera app "Camera Error Can't connect to camera".
Also no third party camera app is working, I tried restarting, re flashing Gapps and re flashing the rom. still the same error.
attached is a screen shot.

Wahbax said:
Thanks for the quick response. I followed the guide step by step and I always get this message in camera app "Camera Error Can't connect to camera".
Also no third party camera app is working, I tried restarting, re flashing Gapps and re flashing the rom. still the same error.
attached is a screen shot.
Click to expand...
Click to collapse
That's weird. It's working fine for me and there's no issues.
Can you try to wipe Internal storage too? But make a backup of internal memory before doing that.
I haven't flashed GAPPS as I'm not using them, but it shouldn't affect the camera in any way.
I've just tried Open Camera and works fine too.

#Henkate said:
That's weird. It's working fine for me and there's no issues.
Can you try to wipe Internal storage too? But make a backup of internal memory before doing that.
I haven't flashed GAPPS as I'm not using them, but it shouldn't affect the camera in any way.
I've just tried Open Camera and works fine too.
Click to expand...
Click to collapse
I wiped internal storage, didn't flash gapps
Unfortunatly, Camera still not working

Wahbax said:
I wiped internal storage, didn't flash gapps
Unfortunatly, Camera still not working
Click to expand...
Click to collapse
Which Nova do you own?

#Henkate said:
Which Nova do you own?
Click to expand...
Click to collapse
CAN-L11

Related

Aosp - Nougat 7.0.X - No MultiSim [BETA-OFFICIAL]

Reserved
Build Download Links
Aosp - Build 20160930
Changelog:
Updated Audio config to N
HDR Mode now working
Updated sources to Nougat 7.0.0-R6
Aosp - Build 20160927
Changelog:
- DeskClock Fixed (no more resets)
- Arsenic Kernel V19 as default
- Updated sources
----
Gps flashable zip fix here
To correctly set the kernel: after the boot, go into Kernel Adiutor (download it from store) and into CPU section, set interactive (yes, I know it's already setted, but set it again).
Go into Thermal section and enable core control, then enable the apply on boot.
Reboot phone and go back into kernel adiutor.
Go into CPU section and check if the min core online are 2. If it's still one, set again as interactive and reboot.
If your min. cores on are 2, then set:
CPU Boost = 20 ms and sync treshold to 1267 MHz
Input boost freq. = 883 MHz.
Toggle on the apply on boot and you're ready to use the Aosp!
I suggest also as I/0 the choice noop scheduler for internal memory and deadline for ext SD, both at 512 kb
2016/09/24
Changelog:
First Release

Great job guys. But before you upload the ROM tell me the MOBILE DATA is working or not. Please!

sundhar88 said:
Great job guys. But before you upload the ROM tell me the MOBILE DATA is working or not. Please!
Click to expand...
Click to collapse
I suggest you to read better the first post

I will try it when tri-state works

FabioSan said:
I suggest you to read better the first post
Click to expand...
Click to collapse
Yeah I got it
You said
ROM Firmware Required: Unlocked Bootloader, Custom Recovery (TWRP preferred), a Brain.
A brain? Yes I got it.
Now I am asking you twice, because a cm14 build says RIL is working in description but not working.
Please dude don't get angry on me. Is mobile data stable and working?
Just say Yes or No.
Thanks

sundhar88 said:
Yeah I got it
You said
ROM Firmware Required: Unlocked Bootloader, Custom Recovery (TWRP preferred), a Brain.
A brain? Yes I got it.
Now I am asking you twice, because a cm14 build says RIL is working in description but not working.
Please dude don't get angry on me. Is mobile data stable and working?
Just say Yes or No.
Thanks
Click to expand...
Click to collapse
On the "working" voice there is the answer [emoji14]
Anyway yes, it's working
Tested of course by myself
Inviato dal mio X utilizzando Tapatalk

Aw hell yeah !

Nice, was waiting for a aosp 7.0 rom. Just to clarify something i wasn't 100% sure, there aren't any gesture available right? Not even double tap? Or did you mean that double tap is already there but no other gesture will be added?
Thanks for the rom!

migueldbr said:
Nice, was waiting for a aosp 7.0 rom. Just to clarify something i wasn't 100% sure, there aren't any gesture available right? Not even double tap? Or did you mean that double tap is already there but no other gesture will be added?
Thanks for the rom!
Click to expand...
Click to collapse
Double tap works natively. (even twrp has double tap to wake lol)
Others may be added soon

migueldbr said:
Nice, was waiting for a aosp 7.0 rom. Just to clarify something i wasn't 100% sure, there aren't any gesture available right? Not even double tap? Or did you mean that double tap is already there but no other gesture will be added?
Thanks for the rom!
Click to expand...
Click to collapse
Double Tap is included and working
The other gestures will not be added because aren't AOSP native (it's also a terrible weird job to do)

Joshwin Aranha said:
Aw hell yeah !
Click to expand...
Click to collapse
Hey index dude! Add this ROM to the index man.

Just to be totally clear. There will never be an option to toggle on screen navbar like on nexus devices right?

Woww, Thanks devs. AOSP is love. <3

bunnahabhain said:
Just to be totally clear. There will never be an option to toggle on screen navbar like on nexus devices right?
Click to expand...
Click to collapse
Honestly, no at 95% dude :/
Inviato dal mio X utilizzando Tapatalk

Damn, it's CM for me then. Keep it up anyway brahh.

Awesome rom. Just noticed one bug until now, going into alarm clock settings and changing values, when going back to clock the app resets and the config goes back to default. No big deal, i will download google clock app from the play store
EDIT: scratch that, downloading the clock app from google also has the same behaviour

migueldbr said:
Awesome rom. Just noticed one bug until now, going into alarm clock settings and changing values, when going back to clock the app resets and the config goes back to default. No big deal, i will download google clock app from the play store
EDIT: scratch that, downloading the clock app from google also has the same behaviour
Click to expand...
Click to collapse
Maybe Timely would save you until it gets fixed.

Javinotfound said:
Maybe Timely would save you until it gets fixed.
Click to expand...
Click to collapse
Was just about to try that, will report in a few minutes if it works=)
EDIT: timely works great

migueldbr said:
Awesome rom. Just noticed one bug until now, going into alarm clock settings and changing values, when going back to clock the app resets and the config goes back to default. No big deal, i will download google clock app from the play store
EDIT: scratch that, downloading the clock app from google also has the same behaviour
Click to expand...
Click to collapse
Oh God xD
If you can make a logcat of this weird bug, would be helpful
Inviato dal mio X utilizzando Tapatalk

[ROM][UNOFFICIAL][7.1.2 r29] CYPHER OS 4.1.1 [OMS]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is Cypher. An extension to pure Android. Cypher tries to maintain the purity of Android while offering useful features for users. The goal is to give the highest level of performance whilst achieving simplicity.
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Click to expand...
Click to collapse
Note: Builds are updated as soon as possible. There is no build cycle. Information pertaining to your device is displayed
Accordingly. The current build is the latest for your device. If your device is
scheduled to release on a certain day, but the new build isn't displaying, contact
your device maintainer for more information but wait at least 72 h. Please know builds are updated by 12am
EST.
Become apart of our G+ community - JOIN
Quote:
REMINDER
If you're having issues and want to submit a report (Logcat) please make sure you are reporting from the stock kernel, not a modified kernel. Modified kernels can break or fix, even improve things. It depends. I can't get a full clue of the issue when you're not running the original kernel.
Click to expand...
Click to collapse
Features:
- Status bar Customization
- Changeable icons
- Quick pulldown
- Smart pulldown
- Notification count
- Clock position
- Seconds in clock
- Date design
- Quick Settings
- Brightness slider
- Brightness icon
- Tile tap customization
- System
- Screenshot partial and full
- Scrolling cache customization
- Power menu customization
- One-handed mode
INSTALLATION INSTRUCTIONS
- Download the latest build of AOSCP (CypherOS)
- Download Gapps (Optional)
- Take a Nandroid backup
- Recommended - Full wipe and factory reset
- Flash ROM using TWRP
- Flash GApps (Optional)
- Flash Magisk (If you want root)
- Reboot.
- Enjoy!
-UPDATE INSTRUCTIONS-
- Download the latest build of AOSCP (CypherOS)
- Take a Nandroid backup
- Flash ROM using recovery
- Flash GApps.
- Flash Magisk (If you want root)
- Wipe cache
- Wipe dalvik cache
- Reboot
- Enjoy!
BUGS
- Srill don't know and you tell me
DOWNLOADS:
- Helium:
7/15/2017: v4.0.5 Android 7.1.2 r27
8/14/2017: v4.1 Android 7.1.2 r29
8/28/2017: v4.1.1 Android 7.1.2 r29 (lastest source, Cypher version, kernel: Fix torch flash when controled by camera Part-2)
- Hydrogen:
7/15/2017: v4.0.5 Android 7.1.2 r27
8/14/2017: v4.1 Android 7.1.2 r29
8/28/2017: v4.1.1 Android 7.1.2 r29 (lastest source, Cypher version, kernel: Fix torch flash when controled by camera Part-2)
DOWNLOAD ROMS: https://www.androidfilehost.com/?w=files&flid=198962
- Gapps: Here
- Magisk: Here
Credits
CypherOS
LineageOS
Ground Zero Rom
AICP
PureNexus
AOKP
Dirty Unicorns
Paranoid Android
and more....
Source Code: https://github.com/CypherOS/platform_manifest
Contributors
Dungphp
ROM OS Version: 7.x Nougat
Version Information:
Good

OMS???? WOW????

I can't find the clock position...also is there a way to make battery as text ?

wow! sounds a good rom, will have a try, thank you for so great work!

m1n15s said:
I can't find the clock position...also is there a way to make battery as text ?
Click to expand...
Click to collapse
Date and Time -- > Others setting

thanks，Try it all right
---------- Post added at 01:43 AM ---------- Previous post was at 01:43 AM ----------
Everything is fine

CySieben said:
thanks，Try it all right
---------- Post added at 01:43 AM ---------- Previous post was at 01:43 AM ----------
Everything is fine
Click to expand...
Click to collapse
Double tap anywhere to Sleep in this rom

@dungphp I'm having issue with screenshots.. doesn't capture it. Also I remember we had some issues with reading inbuilt storage a while back and a fix was released, not sure if it is related to that... Also doing a clean install and full restore, will report issues if i find any....

Nice to see this rom for our max.
But I have an error, can't install (Helium.)
Just me?

onderduiker said:
Nice to see this rom for our max.
But I have an error, can't install (Helium.)
Just me?
Click to expand...
Click to collapse
And your error during install is....?

something with "checking modem version"
Updater process ended with error 7
Error installing zip file '/sdcard/Download/aosp.......zip

onderduiker said:
something with "checking modem version"
Updater process ended with error 7
Error installing zip file '/sdcard/Download/aosp.......zip
Click to expand...
Click to collapse
Your modem is old.
Now you can fix problem for personal
- extract rom to a folder name as rom name
- delete line 2
assert(xiaomi.verify_modem("1.c1-00012-STD.PROD-1") == "1");
Click to expand...
Click to collapse
in updater-script then save
- zip everythings in folder. Copy to your phone, flash

Deleted !

Neo.Collin said:
@dungphp I'm having issue with screenshots.. doesn't capture it. Also I remember we had some issues with reading inbuilt storage a while back and a fix was released, not sure if it is related to that... Also doing a clean install and full restore, will report issues if i find any....
Click to expand...
Click to collapse
I havent has problem with screenshots. Other bugs i will fix soon

dungphp said:
Your modem is old.
Now you can fix problem for personal
- extract rom to a folder name as rom name
- delete line 2 in updater-script then save
- zip everythings in folder. Copy to your phone, flash
Click to expand...
Click to collapse
Thank you, used totalcommander and install went ok.

There is a big chance to talk with a loudspeaker instead of a handset
---------- Post added at 12:23 PM ---------- Previous post was at 12:22 PM ----------
扬声器发出声音，而不是听筒

In Magisk Manager ctsprofile check fails. Also, it would be good if ambient display options like wake when pulled out of pocket and network traffic indicator were implemented.

Just a humble question: What apps and services are affected by this Magisk/cts failure?
I ask because I want to know what to avoid (I have a principle of avoiding every app that has any kind of opinion about my system configuration since that's none of their business).

E90 Commie said:
Just a humble question: What apps and services are affected by this Magisk/cts failure?
I ask because I want to know what to avoid (I have a principle of avoiding every app that has any kind of opinion about my system configuration since that's none of their business).
Click to expand...
Click to collapse
AFAIK Netflix, Super Mario Run and Pokeman Go are the apps which doesn't run if CTS Mismatch.. there also maybe some Banking apps which may not work run.

E90 Commie said:
Just a humble question: What apps and services are affected by this Magisk/cts failure?
I ask because I want to know what to avoid (I have a principle of avoiding every app that has any kind of opinion about my system configuration since that's none of their business).
Click to expand...
Click to collapse
All my work related apps don't work with root..
---------- Post added at 04:35 AM ---------- Previous post was at 04:12 AM ----------
dungphp said:
I havent has problem with screenshots. Other bugs i will fix soon
Click to expand...
Click to collapse
Screenshots work after clean install.. things I've noticed so far
*I love the fact that this ROM is super fast and super light
*I love that it only has very minimal features, only ones I use
* I see there are 3 launchers preinstalled... Do we really need that many?
* Storage access is an issue, even in camera, downloads (doesn't show option of phone and SD card)
* Magisk doesn't work even with clean install (just ROM and gapps)
* Camera stutters like skipping frames when I move to focus on to a subject, happens after I click a picture, the clicked picture doesn't show up.. should be related to storage access itself. I tried disabling & enabling storage access.. one photo was ok, but after that kept giving green blank color images and freezes up camera.. not sure if RR camera fix will fix this issue!!
---------- Post added at 04:38 AM ---------- Previous post was at 04:35 AM ----------
lckjosh said:
In Magisk Manager ctsprofile check fails. Also, it would be good if ambient display options like wake when pulled out of pocket and network traffic indicator were implemented.
Click to expand...
Click to collapse
Did you check gestures section?? Lifting phone works...

[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 [25.05.2018]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 14.1 for Huawei Nova CAN-L11
DISCLAIMER:
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
NOTES
1) If you've found a bug, please report it along with a logcat.
2) If you experience a random reboot, please share /sys/fs/pstore/console-ramoops.
3) It should work on all models, just like LOS 13.
4) Lineage`s root is included (Settings > Developer Options > Root Access. If you want to install Magisk or something else, please uninstall Lineage`s root by flashing addonsu-remove-14.1-arm64-signed.zip in TWRP before installing Magisk or something else.
5) I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
Click to expand...
Click to collapse
LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's working :
Boots
Wifi
Bluetooth
Camera and Camcorder(video recorder)
Video Playback
RIL (Calls, SMS, Data)
Audio ( Recording and Playback )
Sensors
Fingerprint
Notification LED
FM Radio
GPS
NFC
Hotspot
What's not working / bugs:
Camera is / looks zoomed when recording a video (it seems to be same on stock)
HDR?
IMS/Volte
Requirements
Huawei Nova CAN-L11 (should work on the other models too)
Unlocked bootloader ( here's a guide about how to unlock it)
TWRP. The TWRP made by @Grarak is also working fine. You can find it here.
Click to expand...
Click to collapse
Installation
Starting with January 2018 builds you need Nougat /product partition otherwise you'll get bootloop. To get Nougat product partition, you must install / flash EMUI 5 or restore this TWRP backup of Nougat /product partition (more details here). You don't know how to restore that backup? Check the steps from this post.
Make sure you meet the requirements listed above.
Download the ROM and put it on sdcard. If you want GAPPS too, then download Open Gapps too (choose arm64, 7.1 and pico).
Reboot in TWRP by pressing all 3 buttons (Volume UP + Volume Down + Power).
Wipe system, data, cache and dalvik-cache.
Flash the ROM from the directory where you've placed it.
Flash GAPPS (OPTIONALLY).
Reboot.
Click to expand...
Click to collapse
Download
ANDROIDFILEHOST | MEDIAFIRE
Sources
LineageOS: https://github.com/LineageOS
Device: https://github.com/skinzor/android_device_huawei_hwcan
Vendor: https://github.com/skinzor/proprietary_vendor_huawei
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953-1
Click to expand...
Click to collapse
Donations
You don't have to, but if you like my work and you wish to support the development:
Donate via PayPal:
https://www.paypal.me/Henkate
https://forum.xda-developers.com/donatetome.php?u=4471434
I would use the money to upgrade my PC, so i can build with my own PC instead relaying on Google Cloud Platform.
Credits
@Grarak
@gt_o
@abhishek987
@crpalmer
@FrozenCow
@franciscofranco
@flar2
@Sultanxda
@zx2c4
@ Google for their cloud platform and free trial
@ LineageOS
@ Huawei
XDA:DevDB Information
[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 [25.05.2018], ROM for the Huawei Nova/Nova Plus
Contributors
#Henkate, Grarak, gt_o
Source Code: https://github.com/skinzor/android_kernel_huawei_msm8953-1
ROM OS Version: 7.x Nougat
ROM Firmware Required: Unlocked bootloader, TWRP
Version Information
Status: Stable
Created 2017-11-13
Last Updated 2018-05-25

Changelog
25 May 2018
* security patch level 5 May 2018
The development has been resumed and is possible thanks to @wangdaning who helped me to get a new Nova. Thank you!
Click to expand...
Click to collapse
15 February 2018
Read this small, but important F.A.Q.
* synced Lineage sources
* security patch level 5 February 2018
* switched to enforcing selinux
Click to expand...
Click to collapse
25 January 2018
ROM
* synced Lineage sources
* security patch level 05.01.2018
* fixed in-call volume slider, mic/sound recorder (it's louder now) thanks to @gt_o. Read more here.
* updated audio configs to B382 and synced few audio props with stock ones
* show "HUAWEI NOVA" instead "Android" when phone is plugged to PC
* removed substratum support.
* added two blobs to fix two errors in logcat
* added the missing device_qcom_common (i don't know how i haven't noticed that till now lol). Now there are 5 profiles: powersave, efficiency, balanced (default), quick and performance. This can be configured at battery settings. As an idea, the powersave profile seems to turn off 3 cores (the cores doesn't seems to turn on when there is a high load though), while the performace one sets all cores to 2ghz. The power hal being used is the one of msm8937, which is also an octa core CPU. This is defined in the power hal's makefile on Lineage's repo (if the processor is msm8953, use the power hal of msm8937). I recommend it to keep the balanced profile (which is enabled by default), but it's up to you.
Kernel
* merged stock kernel source into the CAF one (tag LA.UM.5.6.r1-01300-89xx.0 as this one semeed to be the closest to stock, but also based on the Adreno log)
* got rid of many drivers from Huawei. You can see the commits here. Thanks to @gt_o, huawei's bootfail monitor (HWBFM) has also been removed. Although HWBFM was disabled till now, it was better to get rid of it, to get a cleaner kernel, but also being easier to merge the stock source into CAF.
* cpuset updates (also in ramdisk)
* added WireGuard support, thanks to @zx2c4. WEBSITE | XDA
* removed fsync/crc toggles as it's better to not mess with them
Click to expand...
Click to collapse
9 December 2017
ROM
* synced Lineage sources
* added Substratum support
* fixed blinking mode of notification light
* allow minimum brightness 1 (it was 4 before)
* possibly fixed the power usage reported by bluetooth ( i can't test right now as phone is charging and can;t reset the battery stats)
* Reverted this commit (more details there)
Kernel
* fixed hotspot
* cleaned ramdisk
Click to expand...
Click to collapse
25 November 2017
ROM
* security patch 6 November 2017
* fixed signal icon on 3G (it isnt empty / gray anymore)
* fixed flac audio playback
* updated media configs to N B382
* hide sRGB toggle in developer options
* increased the number of voice call steps from 5 to 8, and media volume steps
from 15 to 20
* increased the handset volume from the default (84) to 88 to improve UX with voice calls
* added ext4 support for /data
* added f2fs support for /cache
* added glove mode (Settings > Display > High touch sensitivity)
* from now on, Lineage`s root is included (Settings > Developer Options > Root Access. If you want to install Magisk or something else, please uninstall Lineage`s root by flashing addonsu-remove-14.1-arm64-signed.zip in TWRP before installing Magisk or something else.
Kernel
* fixed logd/klogd issue (the high cpu usage)
* disabled HUAWEI_DEBUG_MODE config
* added DriveDroid support: allows you to boot your PC from ISO/IMG files stored on your phone [UNTESTED]
* added USB HID gadget support
* CRC toggle; enabled by default (disable it for 30% performance improvement at the risk of data corruption, according to its description)
* FSYNC toggle; enabled by default (disable it to possibly increase performace at the risk of data corruption
Click to expand...
Click to collapse
13 November 2017
* initial release
Click to expand...
Click to collapse

Reserved

Dowloanding ^^
As soon as I can, I'll report back =)

Thank You #Henkate for keeping Nova alive!

Hi, i was waiting for LOS14 so much, thank you for the hard work <3. I just have a few concerns about the unlocking bootloader/rooting/twrping stuff of my MLA-L11, since noone of the methods has been confirmed to work on that model.. And i simply can't risk a 300 € brick. I'm confident with modding, the method seems crystal clear.. Just asking the Dev if he thinks it should works for me. Also, if i should take some cautions and how. Android 7, EMUI 5, full stock. Of course modding is always a risk, but.. you know what i mean. Thanks in advance, i hope that's not off the topic!

Works fine here, thanks a lot for the hard work !!!

Will give it a shot this weekend. I am a teacher and students are doing mid term exams this week, so I kind of need my phone.

For some reason, I can't get it to boot. It is on LOS bootanimation and doesn't boot =/ can't even get a log.
Clean format always, I tried with stock open gapps, pico open gapps, without open gapps. It seems something is wrong with my phone.
then i thought the issue could be I'm coming from EMUI 5.
Then I tried to restore bluesmoothie backup and put LOS over it, nothing =/
I don't know why =/

To all people: I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
GertFromTheWell said:
Hi, i was waiting for LOS14 so much, thank you for the hard work <3. I just have a few concerns about the unlocking bootloader/rooting/twrping stuff of my MLA-L11, since noone of the methods has been confirmed to work on that model.. And i simply can't risk a 300 € brick. I'm confident with modding, the method seems crystal clear.. Just asking the Dev if he thinks it should works for me. Also, if i should take some cautions and how. Android 7, EMUI 5, full stock. Of course modding is always a risk, but.. you know what i mean. Thanks in advance, i hope that's not off the topic!
Click to expand...
Click to collapse
Hi there!
Thank you too for the kind words!
I don't know if it'll work, but it has been confirmed that MLA-L03 has been unlocked with the same method. Theoretically, it should work on your MLA-L11 too since it's one of MLA series.
Also, the process of unlocking bootloader is "general", it isn't meant only for one or two phones/models. If I'm not mistaken, I think you can't even brick a phone when you're trying to unlock the bootloader.
If you'll unlock the bootloader and by any chance LOS14 isn't booting on your model, you'll have to relock the bootloader, download EMUI 5 firmware from Firmware Finder and install it.
LOS 13 could be flashed from EMUI 5, so it shouldn't matter for LOS 14 neither.
Vinnom said:
For some reason, I can't get it to boot. It is on LOS bootanimation and doesn't boot =/ can't even get a log.
Clean format always, I tried with stock open gapps, pico open gapps, without open gapps. It seems something is wrong with my phone.
then i thought the issue could be I'm coming from EMUI 5.
Then I tried to restore bluesmoothie backup and put LOS over it, nothing =/
I don't know why =/
Click to expand...
Click to collapse
What's your Nova model? I've forgot .
Did you take a look at the recovery log after you're flashing LOS 14 or the output from recovery itself? Does it really gets flashed properly?
LOS 13 could be flashed from EMUI 5 too, so that shouldn't matter neither with LOS 14.
I'll make an eng boot.img later (when I'll get access to PC), so you'll be able to take a logcat during booting.

#Henkate said:
To all people: I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
Hi there!
Thank you too for the kind words!
I don't know if it'll work, but it has been confirmed that MLA-L03 has been unlocked with the same method. Theoretically, it should work on your MLA-L11 too since it's one of MLA series.
Also, the process of unlocking bootloader is "general", it isn't meant only for one or two phones/models. If I'm not mistaken, I think you can't even brick a phone when you're trying to unlock the bootloader.
If you'll unlock the bootloader and by any chance LOS14 isn't booting on your model, you'll have to relock the bootloader, download EMUI 5 firmware from Firmware Finder and install it.
LOS 13 could be flashed from EMUI 5, so it shouldn't matter for LOS 14 neither.
What's your Nova model? I've forgot .
Did you take a look at the recovery log after you're flashing LOS 14 or the output from recovery itself? Does it really gets flashed properly?
LOS 13 could be flashed from EMUI 5 too, so that shouldn't matter neither with LOS 14.
I'll make an eng boot.img later (when I'll get access to PC), so you'll be able to take a logcat during booting.
Click to expand...
Click to collapse
Mine is CAZ-TL10 (chinese). I'll try again (today I won't be able to, maybe thursday or friday) and take the recovery.log which I forgot :/
However, the twrp output was fine. I had some bad lines:
Failed to mount /cust (always have it)
E: unknown command (two lines of this message after flashing the ROM)
Enviado de meu HUAWEI CAN usando Tapatalk

Vinnom said:
Mine is CAZ-TL10 (chinese). I'll try again (today I won't be able to, maybe thursday or friday) and take the recovery.log which I forgot :/
However, the twrp output was fine. I had some bad lines:
Failed to mount /cust (always have it)
E: unknown command (two lines of this message after flashing the ROM)
Enviado de meu HUAWEI CAN usando Tapatalk
Click to expand...
Click to collapse
I see.
I have the second error too, after flashing the ROM. I haven't checked why, but it doesn't seems to affect anything.
As I've said, i'll provide an eng boot.img later, so you'll be able to take a logcat during boot.

#Henkate said:
As I've said, i'll provide an eng boot.img later, so you'll be able to take a logcat during boot.
Click to expand...
Click to collapse
@Vinnom
Here you go. Install it from recovery.

I have a MLA-L03 and I was on LOS13, followed the steps and everything works fine for me.

sk8buoy said:
I have a MLA-L03 and I was on LOS13, followed the steps and everything works fine for me.
Click to expand...
Click to collapse
Are you having the no sim card bug as well ?
Vive le quebec !!!:good:

icutzo said:
Are you having the no sim card bug as well ?
Vive le quebec !!!:good:
Click to expand...
Click to collapse
Nope, this bug is gone now. When I'm on LTE the icon don't show LTE (it show only the signal strength) but data works fine.

I thought it would be possible for me to try and flash again only in thursday, but I could today.
I tried to different ways:
Clear flashing;
Formating data;
Neither worked.
I took 2 recovery logs, before and after formating data.
I took a logcat while booting, thanks to the eng boot.img provided.
The logs can be found here.
I don't have a clue why it doesn't boot =/
I took a look at the logs, everything seems to be flashed without any problem and I can't understand right the logcat. I hope it can be useful

Runs good in MLA-L11 with some issues:
The camera stop ramdon
-the front camera have issues with post processing.
Using the OP Camera works good.
-all the cores are 2.02ghz all the time the phone is active
-When you get the kernel CAF will be a perfect ROM. thanks for the hard work hetanke !

Vinnom said:
I thought it would be possible for me to try and flash again only in thursday, but I could today.
I tried to different ways:
Clear flashing;
Formating data;
Neither worked.
I took 2 recovery logs, before and after formating data.
I took a logcat while booting, thanks to the eng boot.img provided.
The logs can be found here.
I don't have a clue why it doesn't boot =/
I took a look at the logs, everything seems to be flashed without any problem and I can't understand right the logcat. I hope it can be useful
Click to expand...
Click to collapse
The recovery logs looks fine. I see that you have also installed Magisk and a Titanium Backup zip. Just to be clear, you have tried to install it without anything else too?
1) Did you wait about 5 mins ( although i dont think that much time is required)?
2) Can you take a kernel log too?
Run the following command, while booting (let it run few seconds after you think that you have got bootloop):
Code:
adb shell "cat /dev/kmsg"
I cant find anything wrong in logcat neither. I think the stock kernel may not be compatible with your model, so i will need to use the kernel source for your model or compare the two sources and import changes from CAZ-TL10 source into the one im using now.
The stock kernel source which is being used right now is CAZ_NG_EMUI5.0_opensource. According to Huawei`s website, it is meant for:
HUAWEI Nova,HUAWEI Nova Plus, CAN-L10, L11, MLA-L01,L11,L12,L13, Android 7.0, EMUI 5.0
Click to expand...
Click to collapse
When i search for "CAZ" on their website, i find nothing. But there seems to be:
Cannes-AL10_TL10 HUAWEI nova, Cannes-AL10, TL10, Android 7.0, EMUI 5.0
Click to expand...
Click to collapse
Perhaps thats the right one for CAZ-TL10 too?

imkoma said:
Runs good in MLA-L11 with some issues:
The camera stop ramdon
-the front camera have issues with post processing.
Using the OP Camera works good.
-all the cores are 2.02ghz all the time the phone is active
-When you get the kernel CAF will be a perfect ROM. thanks for the hard work hetanke !
Click to expand...
Click to collapse
Thank you too for your words!
By the way, its Henkate. You can also call me Robert .
1) When exactly camera is stopping and how? I didnt encounter this on my CAN-L11
2) What kind of issues does have front camera? My Nova`s front camera got damaged / broken when my Nova has been damaged, therefore i cant use it nor test it.
3) Regarding the cores, ive wrote at "notes" in first post:
The first thing you want to do after first reboot is to install a file manager and rename /system/bin/logd to "logd.bak" and reboot. You have to do this in order to get rid of the high CPU load. Consider this a workaround until the issue gets solved. Note that this breaks logcat, so you'll have to rename it back to "logd" and reboot to be able to take a logcat.
Click to expand...
Click to collapse
Would be nice if you could share a logcat regarding 1) and 2).

[ROM][v6.7][OFFICIAL] CrDroid [TEN][non-unified]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Changelog
- Initial crDroid 6.7 code
- June Security Patch
- Added OOS style notification dismiss button
- Added toggle to disable sensor usage for some apps
- Added option for brightness slider in QuickQS panel
- Added 6 new clock styles
- Fixed disappearing date section on custom clock in some cases
- Improvements for weather on lockscreen
- Fixed Android crash with RGB wallpaper
- Added new font - Accuratist
- Added new and working stock calendar app
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
Reboot to recovery
Normal 5 wipes
Again reboot to recovery
Flash ROM and gapps
(Optional) Flash magisk
Reboot to system
Update installation:
Reboot to recovery
Normal wipes (exclude internal and data)
Again reboot to recovery
Flash rom and gapps
(Optional) Flash magisk
Reboot to system
Sources:
ROM: https://github.com/crdroidandroid
Kernel: kernel url
Download:
ROM https://crdroid.net/rolex
Changelog: https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/10.0/changelog_rolex.txt
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
Support device maintainer
XDA:DevDB Information
CrDroid, ROM for the Xiaomi Redmi 4a
Contributors
adi153
ROM OS Version: Android 10
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 6.7
Stable Release Date: 2020-06-07
Created 2020-01-06
Last Updated 2020-06-07

Device time changes to incorrect after rebooting,
Plz add double tap to ambient display feature in next update

Installed last night. Running smooth and stable. Performance is great. Only problem I've noticed is the camera won't save to SD card. Any quick fix for that? Please let me know. Thanks! Great work!

digidad said:
Installed last night. Running smooth and stable. Performance is great. Only problem I've noticed is the camera won't save to SD card. Any quick fix for that? Please let me know. Thanks! Great work!
Click to expand...
Click to collapse
The camera does actually save to SD card, but it goes to a very strange destination, if you go to your SD card > Android > data then you'll find a folder called org.lineageos.snap, in that folder (when you've taken a photo) you'll find a folder named files and in that folder you'll find your photo. I've tried many things to try to direct my photos to my SD card and then to the camera folder, but never had any luck. I just leave at phone storage then move them to SD card > camera using my gallery app.

Paul T said:
The camera does actually save to SD card, but it goes to a very strange destination, if you go to your SD card > Android > data then you'll find a folder called org.lineageos.snap, in that folder (when you've taken a photo) you'll find a folder named files and in that folder you'll find your photo. I've tried many things to try to direct my photos to my SD card and then to the camera folder, but never had any luck. I just leave at phone storage then move them to SD card > camera using my gallery app.
Click to expand...
Click to collapse
Is there a way to make the Gallery app display photos from this location (org.lineageos.snap)?

digidad said:
Is there a way to make the Gallery app display photos from this location (org.lineageos.snap)?
Click to expand...
Click to collapse
I'm using simple gallery pro and it does allow you to include 'other' folders to display. I've just tested it and set the camera to save to SD card then SGP has in it's setting to manage included folders, which you can then point it to org.lineageos.snap

Paul T said:
I'm using simple gallery pro and it does allow you to include 'other' folders to display. I've just tested it and set the camera to save to SD card then SGP has in it's setting to manage included folders, which you can then point it to org.lineageos.snap
Click to expand...
Click to collapse
Thanks, That worked as an option.
The thread below suggests that this is fixed in the newest Lineageos 16.0 builds. Pictures will be shown in Gallery stored in Android/data/org.lineageos.snap/files
https://gitlab.com/LineageOS/issues/android/issues/268

wasay.65 said:
Have you flashed the Pixel launcher addon?.When i flash pixel launcher the other launcher don't work.
I tried the rom. It is great. Also adoptable storage worked after 4 tries. However, i think that the battery and the time logo in the status bar are too much near the end of display. Is there any option to move them a little away from the screen border.
Click to expand...
Click to collapse
I haven't tried Pixel launcher addon. The status bar is fully customizable in the CrDroid settings.

digidad said:
I haven't tried Pixel launcher addon. The status bar is fully customizable in the CrDroid settings.
Click to expand...
Click to collapse
OK. Anyways i have flashed the pixel launcher cuz i didn't like the stock launcher. It is working fine. Why is it in beta state, everything is fine till now. I would say it is better stable then PE.

wasay.65 said:
OK. Anyways i have flashed the pixel launcher cuz i didn't like the stock launcher. It is working fine. Why is it in beta state, everything is fine till now. I would say it is better stable then PE.
Click to expand...
Click to collapse
I agree - not sure why it is Beta status. I have less issues with this ROM so far than PE9 (which I previously thought was pretty great). With PE9, I had very slow download speeds and would often need to reboot my phone to 'automatically' rejoin a saved Wifi network. CrDroid seems pretty solid - especially for a 10 ROM. :good: :good:

Anyone notice the volume with bluetooth speaker. I have kept it an seven steps. On the third step, the volume is like 40% and on the fourth step it is 80%. I have tried 15 steps and the same result. On the fith and above the audio is too luod on my headphones.

A few qustions:
1. Can i dirty flash the new update Found it in the main post
2. I have adoptable storage. Does dirty flash damage adoptable storage.
3. What are the steps for dirty flash. Do gapps remain after dirty flash.
Thanks in advance

See comments on 6.0 thread. Several have reported issues with networking including WiFi, Data and Bluetooth not working after installing 6.2. Caution advised.

digidad said:
See comments on 6.0 thread. Several have reported issues with networking including WiFi, Data and Bluetooth not working after installing 6.2. Caution advised.
Click to expand...
Click to collapse
Is the WiFi working now on the 01-13 update (dirty flash)? Also OP why are there 3 separate threads for the same ROM lol

WiFi is working fine. I was on 1/3 build and updated using the 'check for updates' feature which reboots to TWRP. I guess that would be a 'dirty flash'.

Help
Wrong Thread

wasay.65 said:
Hello. Unfortunately my redmi 4a screen broke. But touch is working fine. Only some cracks. Should i leave it like that or replace my screen. If possible can i put on a screen protector. I know its out of topic but please help.
Click to expand...
Click to collapse
I don't know about where you live, but here it would probably cost around the same to repair as it would to purchase another used phone with better specs.
If you really want a Redmi 4A, eBay might be an option. For example: https://www.ebay.com/itm/Xiaomi-Red...rbished-Smartphone-2-16GB-3-32GB/184083855252

DELETED

Fast charge is not working.

Fast charging problem and it is using 90% of the storage on my 16gb model

[ROM][10][ARM64][A320] crDroid v6.21 for Galaxy A3 2017 [10.08.2021]

IMPORTANT, PLEASE READ THIS
This is a ROM built from source and not a GSI!
Fix Camera stretch & force close for some camera apps
You can do it editing /vendor/build.prop file using MiXplorer (you’ll need ROOT).
Search for the line “vendor.camera.hal1.packagelist”
After the = are the name of different apps. Delete one of these and put the package name of the app that you want to fix. For example, com.facebook.orca is the Facebook package name.
Per default, the ROM comes with Whatsapp, ZOOM, Snapchat and Instagram added. Maximum 4 Apps are allowed in this line and must be separated by comma ",".
If you don’t understand, open this link to see visual steps.
Fix Camera stuck
Sometimes, the camera can get inaccessible if an app was failed. If it happen, follow this:
Install this app. Open it and tap "Kill camera", then give it ROOT permissions. Done! Camera is working again.
Take in mind that if the camera is broken and you didn't do this, the audio in calls maybe not work.
GCam
This ROM can run GCam. Download a modded version for Exynos HERE. Thanks to Leonardo Estacio for his mod.
Games: this ROM works so good for gaming and can run ARM64 apps/games. If you feel lags, go to Settings > Battery > Battery Saver and performance > Performance Profile and set it to High Performance.
Video Review: if you want to see gaming performance and how this ROM are, you can watch this review video of the ROM in the J7 2016 (the ROM is the same for other Exynos7870 variants):
For close, i want to give a huge thanks to @Astrako - Without him this ROM haven't be possible <3
Also a huge thanks to Peter Schiek for his €50 donation

Changelog:
android_vendor_crDroidOTA/changelog_j7xelte.txt at 10.0 · crdroidandroid/android_vendor_crDroidOTA
OTA configuration for crDroidOTA (make your device official) - android_vendor_crDroidOTA/changelog_j7xelte.txt at 10.0 · crdroidandroid/android_vendor_crDroidOTA
github.com
===== 17-04-2021 =====
- crDroid 6.17
- Fixed Live Display
- Added Night Light
- April Security Patch
- Deleted ConfigStore hal
===== 11-02-2021 =====
- crDroid 6.15 build
- Repartition script updated. Now you can get more userdata space.
- XDA release build
===== 24-01-2021 =====
- Fixed offline charging
- Added vibration intensity control
- Latest crDroid sources (v6.14 with January security patch)
- Initial a3y17lte private build for testing

GonicTEAM said:
Fix Camera stuck
Sometimes, the camera can get inaccessible if an app was failed. If it happen, follow this:
Install this app. Open it and tap "Kill camera", then give it ROOT permissions. Done! Camera is working again.
Click to expand...
Click to collapse
Thanks for your build.
Do you use LineageOS tree for A3 2017 by Martin (@Sap1k) ? Because it doesnt have the problem with camera.
Also crDroid 6.9 by Atrasko doesnt have this problem too. But since 6.12, there is this problem with camera.

Very nice to see a new ROM for the A3.
Did anyone test if bluetooth calls are working correctly and if recorded videos with apps other than Footej, are saved correctly?

SuperDeformed86 said:
Thanks for your build.
Do you use LineageOS tree for A3 2017 by Martin (@Sap1k) ? Because it doesnt have the problem with camera.
Also crDroid 6.9 by Atrasko doesnt have this problem too. But since 6.12, there is this problem with camera.
Click to expand...
Click to collapse
I use Astrako's device trees for crDroid, not LineageOS ones. I will see what was change, thanks!

What is the differenc beetween crdroid 6.15 and crdroid 6.9?

hi,
nice job. The ROM doesn't detect my SIM CARD. How to fix that point? Thanks for any help.

Can i use Twrp to flash this Rom and the cr droid partitionierer

Is adoptable storage something that works on this ROM? The tiny 16GB of internal storage are crippling this otherwise still capable device...

Crim Soukyuu said:
Is adoptable storage something that works on this ROM? The tiny 16GB of internal storage are crippling this otherwise still capable device...
Click to expand...
Click to collapse
It does say in the first page that BT calling is still broken in this ROM.
crDroid is awesome on this phone but the lack of BT calling sucks and I don't think there is developer motivation to fix.

nonsub said:
It does say in the first page that BT calling is still broken in this ROM.
crDroid is awesome on this phone but the lack of BT calling sucks and I don't think there is developer motivation to fix.
Click to expand...
Click to collapse
That's good to know, but I didn't ask about BT...

Hello, on my A3 2017 (a3y17lte), when install crdroid, it says:
Code:
updater process ended with error7
error installing zip file '/external-sdcard/crDroidAndroid-10.0-20210211-a3y17lte-v6.15.zip'
this is with last twrp, because with your orangeFox, i can't intall it, because it is for j7y17lte

yeye.phone said:
Hello, on my A3 2017 (a3y17lte), when install crdroid, it says:
Code:
updater process ended with error7
error installing zip file '/external-sdcard/crDroidAndroid-10.0-20210211-a3y17lte-v6.15.zip'
this is with last twrp, because with your orangeFox, i can't intall it, because it is for j7y17lte
Click to expand...
Click to collapse
It should work with this orangefox.
[OFFICIAL][TWRP][A320FL/F/Y] OrangeFox Recovery Project [R11.0]
DISCLAIMER I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it...
forum.xda-developers.com

LuChaos said:
It should work with this orangefox.
[OFFICIAL][TWRP][A320FL/F/Y] OrangeFox Recovery Project [R11.0]
DISCLAIMER I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok i will try with this Version.I think it's better suited.

isaacragui said:
hi,
nice job. The ROM doesn't detect my SIM CARD. How to fix that point? Thanks for any help.
Click to expand...
Click to collapse
same here...any solutions? Tried different SIM cards and flashed ROM 2-3 times

Cheers @GonicTEAM,
Thanks for the crDroid release, hope to see more updates to this rom.
Tested the rom on a SM-A320F/DS, can confirm what other users have mentioned above, and some others:
SIM slots dont work, tested both slots. Ive added a logcat to the post. SDcard (SIM2 slot) works fine, no issue there.
Settings > Display > LiveDisplay: Cant edit the settings for bluelight filter.
Settings > Display > Lock screen display > Ambient display: To edit Ambient display settings this way does not work, either nothing happens or it jumps back to Display settings. To edit Ambient display settings, have to go through -> Settings > crDroid Settings > User Interface (tab) > Ambient display. Not a huge issue, just fyi.
Camera works fine with the native app, I use OpenCamera though and with the build.prop edit mentioned in 2nd post it works without issue.
Bluetooth/NFC seem to work, though I havent tested in depth due to sim issue.
Wifi works fine aswell, only annoyance is after reboot sometimes aireplane mode is activated and wifi off, even though it was on before reboot. But thats a small issue, not priority.
Phone encryption working aswell, no issue there as far as i can see.
Battery, havent tested per usual usage, though it does drain faster at first look.
Best regards and lookin forward to future releases,
yass

yass said:
Cheers @GonicTEAM,
Thanks for the crDroid release, hope to see more updates to this rom.
...
Click to expand...
Click to collapse
Thanks for the feedback. I don't have this device, but i compile the ROM anyway using the Astrako's device trees. I will try to fix this things if i can.

SuperDeformed86 said:
Thanks for your build.
Do you use LineageOS tree for A3 2017 by Martin (@Sap1k) ? Because it doesnt have the problem with camera.
Also crDroid 6.9 by Atrasko doesnt have this problem too. But since 6.12, there is this problem with camera.
Click to expand...
Click to collapse
GonicTEAM said:
I use Astrako's device trees for crDroid, not LineageOS ones. I will see what was change, thanks!
Click to expand...
Click to collapse
Please dont use this device tree from martin .This Device Tree have the Problem that adobtabel storage dont work
This is very bad for this device because it have only 16gb internal storage

Crim Soukyuu said:
Is adoptable storage something that works on this ROM? The tiny 16GB of internal storage are crippling this otherwise still capable device...
Click to expand...
Click to collapse
my english is not so good
Yes it works but it was disabeld but you can enabeled it with a few commands
1.enabeled devolper options (tap 5 times on build number)
2.enabeled usb-debuging in devolper options
3.install minimal adb and fasboot on your pc
4.start minimal adb and fastboot
5.type adb devices and type yes on the prompt on your phone
6.type adb shell
7.type sm set-force-adoptable true
8.go to setting/storage/sdcard/format as internal storage

Database Develop

welcome