Database Users

[ROM] LegacyHuawei CyanogenMod 11.0

Installation
https://github.com/LegacyHuawei/local_manifests/wiki/Installation
Bugs
https://github.com/LegacyHuawei/local_manifests/wiki/Status
Downloads
https://basketbuild.com/devs/LegacyHuawei
Changelog
https://github.com/LegacyHuawei/local_manifests/wiki/CM11.0-changelog
If you have any bugs to report, open new issue at https://github.com/LegacyHuawei/local_manifests/issues

Readme
Use the standard Torch app wherever possible, it only enables flashlight. Other apps from Play Store are designed to use the camera interface, which means camera will use additional power.
For more RAM: Settings->Performance->Memory management.
Do not enable KSM, as video encoder/decoder stops working.
HuaweiSettings
Charge current - allows you to set custom charging current. While this actually limits the current input, it effectively decreases or increases the available current transferred to the battery. This is useful in multiple ways:
Slower, but more effective charging. Your battery will last longer.
Faster charging when connected to USB. For example, USB charging is limited to 500mA, but newer PCs allow drawing up to 800mA or even more. This can be configured via the setting.
Manual override of non-standard charger allowing to draw more than 500mA.
Magnetic sensor calibration - lets you delete previous calibration information. This is useful to recalibrate the compass (when it's inaccurate). Just tap the item & then open any compass up to recalibrate your sensor.
If the phone reboots unexpectedly, crash log is found at /data/dontpanic .
To report bugs, use this app: https://play.google.com/store/apps/details?id=com.tortel.syslog

Thank you, i'll try

wow, downloaded...

Many thanks, good job!

after installing cm11 and gapps, the phone always reboot to recovery

ggunzio said:
after installing cm11 and gapps, the phone always reboot to recovery
Click to expand...
Click to collapse
Did you do a factory reset before?
And does it show the cm logo or just boot to recovery?
Sent from my IDEOS X5 using Tapatalk

Blefish said:
Did you do a factory reset before?
And does it show the cm logo or just boot to recovery?
Sent from my IDEOS X5 using Tapatalk
Click to expand...
Click to collapse
before installing the rom, i've wiped everything, data, cache, system and dalvkit cache, reboot recovery. After installed the rom, and right after, installed the gapps. Then, in recovery, reboot system and after it show the huawei logo, it enters recovery without showing the CM logo.
EDIT: i will install ble_part stock, and them install again the B518, repartition again and try to install CM again.

Booted and installed just fine after doing Blepart and using your recovery. It's slow as molasses, probably in great part due to the fact that the display glitches are still there, but it certainly works, and it's as much KitKat as my Moto G. Something worth mentioning, your recovery has some sort (the same?) of display glitch as well in which the screen only seems to update after a couple of presses of the volume button, not immediately.

ROM and GAPPS, everything works fine.
No glitches for me.
Great job, thanks!

faekplastik3s said:
Booted and installed just fine after doing Blepart and using your recovery. It's slow as molasses, probably in great part due to the fact that the display glitches are still there, but it certainly works, and it's as much KitKat as my Moto G. Something worth mentioning, your recovery has some sort (the same?) of display glitch as well in which the screen only seems to update after a couple of presses of the volume button, not immediately.
Click to expand...
Click to collapse
Thanks.
I don't have any devices to compare it with so it feels "fast" to me. Its great to know the recovery suffers same display bugs, it confirms that its in fact kernel side problem. Though, kernel side does not have BLT enabled, which I thought would be the problem. I'll debug the registers, and see if I can find something odd. It could also be a clock hz issue, it was changed in 3.4.
Sent from my IDEOS X5 using Tapatalk

Blefish said:
Thanks.
I don't have any devices to compare it with so it feels "fast" to me. Its great to know the recovery suffers same display bugs, it confirms that its in fact kernel side problem. Though, kernel side does not have BLT enabled, which I thought would be the problem. I'll debug the registers, and see if I can find something odd. It could also be a clock hz issue, it was changed in 3.4.
Sent from my IDEOS X5 using Tapatalk
Click to expand...
Click to collapse
Well, it stutters a lot, and it's not nearly as smooth as something like Aurora or even stock Huawei ROMs, but I'm sure it's related to the display issues or another issue like that because even scrolling through the Settings app or the little animation in the notification drawer that flips into the shortcuts stutters like hell and drags around, which shouldn't be an issue for this device and wasn't a problem with other ROMs, and overclocking and other user-level optimizations do nothing to alleviate it.
I did also notice black screens when waking the device from lockscreen (digitizer still works) almost every time, requiring multiple attempts until the display finally wakes. I know you squashed this one multiple times, but here it is again.
It's a miracle for this to happen to begin with, so I can't help to be amazed seeing KitKat on this device. Thank YOU so much, Blefish.

do i need to have my phone rooted?

faekplastik3s said:
It's a miracle for this to happen to begin with, so I can't help to be amazed seeing KitKat on this device. Thank YOU so much, Blefish.
Click to expand...
Click to collapse
This. If some months ago anyone told me I'd be installing 4.4 on this device I'd tell them they were crazy.
Thanks for your amazing work, Blefish

Here its works as it should be, you are awesome blefish
Sent from my SM-T210 with rocketTab 2.1 + MK1 kernel using tapatalk v4

Finally i could get it to boot.
probably i broke something, i've installed the oficial rom and then, with 5.5.0.4 recovery wiped everything. Next installed the blepart, new recovery and its working
Good job sir
Thank you!

faekplastik3s said:
I did also notice black screens when waking the device from lockscreen (digitizer still works) almost every time, requiring multiple attempts until the display finally wakes. I know you squashed this one multiple times, but here it is again.
Click to expand...
Click to collapse
Yes, I have waking problems too.

Install everything (partition, 6 recovery, cm11 rom and gapps) and works pretty well so far.
Fantastico. :good::highfive:

lemene said:
Install everything (partition, 6 recovery, cm11 rom and gapps) and works pretty well so far.
Fantastico. :good::highfive:
Click to expand...
Click to collapse
is anyone having problems to connect to wifi networks? i cant connect
EDIT: i guess that is a problem with the wireless definition of the rom, im thinking this, because i can connect to open networks, but when i change the segurity of the wlan to wpa or wpa2, i can't connect to it.
Could you look at this @Blefish?
Im not sure if its a bug or not, maybe something is broken in wpa.supplicant
[]

I have flashed BlePart recovery, i have rebooted the recovery and i have flashed blepart 2.2 then i have flashed CVM Version 6.0.4.6. The phone rebooted and now i cant open the phone or recovery. I tried to install offical 2.3 from sd card but i coudn't. How can i recover my phone?

[Q] S4 i9506 solk2 port - thanks, and issues observed

Hi - I'm very new to the forum and less new to custom ROMs and software.
In the last few days I installed solk2's unofficial CyanogenMod port, 20140711 root build. Went well; overjoyed to be rid of Samsung's bloatware. Thanks!
Since then, updated to first 20140808 and now 20140813. Used CWM recovery (installed via theunlockr dot com/2013/12/09/install-custom-recovery-samsung-galaxy-s4-gt-i9506shv-e330s/) directly instead of CM Updater - updater downloads the builds but when it reboots into recovery to apply them the process there cannot find the build file to install.
I've noticed:
1) When making / receiving calls, the face sensor doesn't appear to work any more - before CM, the sensor would notice when the phone is held to my cheek and blank the display, and light it up when I move the phone away. No longer.
2) The front start button doesn't appear to wake up the device from sleep any more (maybe I've missed a setting to toggle for that?)
3) the CM updater doesn't appear to work, as mentioned above
4) CyanDelta doesn't know about this set of nightlies I think - I've tried it a couple of times and it doesn't pick up deltas
5) the power button doesn't wake the device when it has darkened due to being on a call; instead it may cause the device to flash its screen up but then immediately darken again
1 & 5 make it quite difficult to control the phone during calls. Initially I thought this might have to do with ShakeCall, but the issues persist after uninstalling that.
I've cleared my cache and dalvik cache after the most recent flash to 0813.

I should say, this is relating to http://forum.xda-developers.com/showthread.php?t=2767448 and I'd have posted there but I cannot yet.

This is still an issue for me with cm-11-20140909.
Is there anything I can do to help find and fix these items?

Is this the right place to ask, even? Does @solk2 work?

pfm102 said:
This is still an issue for me with cm-11-20140909.
Is there anything I can do to help find and fix these items?
Click to expand...
Click to collapse
Proximity sensor fixed a long ago. There something wrong in yours phone. Install this recovery. Then try clean install of latest nightly or SNAPSHOT-M10 and set update recovery in Developer settings. Recovery you have has different mount points so thats why it can't find updates.
Delta updates isn't supported though.

solk2 said:
Proximity sensor fixed a long ago. There something wrong in yours phone. Install this recovery. Then try clean install of latest nightly or SNAPSHOT-M10 and set update recovery in Developer settings. Recovery you have has different mount points so thats why it can't find updates.
Delta updates isn't supported though.
Click to expand...
Click to collapse
Thank you very much - I'm running 20140914 and the proximity sensor now works during calls.

Home button not working at all (tried several fixes)

(Edit 1) Found a fix already! Read post 2!!!
Hello there,
I've been having a OnePlus Two since 4 months already, and had like 2 or 3 home button not working issues.
They used to fixed by themselves after a couple of days of not working, but not this last time.
I tried already the reinstalling system (after formatting system via TWRP), clean it several times, hard reset (hold power button for more than 20 seconds), complete drain battery and fully charge it again, force stop fingerprint service, take out the tempered glass screen protector, and none of those solutions worked.
I here attach (copy the link, can't upload a video directly to this post) a video in which you can see that whenever I power on the screen (still locked), the home button works for several times, but as soon as I unlock it (pattern lock) it stops working. This makes me think that the problem is software, not hardware, but as I said before, already tried reinstalling OOS 3.0, wiping system, cache, data, internal storage, etc.
I compressed the video so it wouldnt be too big, but quality is good enough, just rise the volume so you can listen to the "vibration" that the home button produce.
Any help would be appreciated.
Sincerely,
Daniel Castro

Fix for the issue!
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro

I have the same problem
Tomorrow i'll try your method
I've posted a questione about this issue,
I think the One plus team should find a solution to this problem that afflict many users

Also, don't forget to rotate your phone 720 degrees, counter clock wise! ? hocus pocus....

DCastro555 said:
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro
Click to expand...
Click to collapse
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk

these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.

LOL9988 said:
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
It will erase everything, make a backup before starting the process.

faustin95 said:
these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.
Click to expand...
Click to collapse
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.

pitrus- said:
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.
Click to expand...
Click to collapse
If it works, its worth a try . And yeah, but we are not in any OnePlus Forum, neither debating about if they are gonna do anything about their own issue, we are trying to fix what an irresponsable company wont.

can we make together an official request to one plus to give us an answer or explanation about this? a lot of users are facing this issue, it's not normal
This is my second opt I bought that this problem has happened
sorry for my english

I had also tried lot of things but home button is not responsive at all.. H2os,exodus,oxygen 2.1 ,3.0 same everywhere
---------- Post added at 04:01 AM ---------- Previous post was at 03:59 AM ----------
Error is: when i open fingerprint setting
Enrollment not working try differnt finger or try again ... Nd fingerprint autotest not starting also

i've turned to stock i've updated to oxygen 3.0 bet and the button worked again

i think rooting installing twrp and installing different roms may be the cause of this issue

faustin95 said:
i think rooting installing twrp and installing different roms may be the cause of this issue
Click to expand...
Click to collapse
Unfortunately that is not the case, it's a hardware design bug.
However you can f-k up your finger scanner by damage your persistant-partition if you flash up and down between different ROM/bootloader revisions. But it's easily fixed by flashing the image file for that partition again.

pitrus- said:
Unfortunately that is not the case, it's a hardware design bug.
Click to expand...
Click to collapse
it's a driver issue

faustin95 said:
it's a driver issue
Click to expand...
Click to collapse
50/50 moisture sensitivity and driver issue.

Home button has been working fine for a year, installed 3.0.1 today and suddenly home button only works in OOS 3.0.1. No longer works in CM 13, yet works fine in OOS 3.0.1. Definitely a driver issue.
Tried installing OOS 2.2.1, wiping, then installing Grarak's CM 13 and home button refuses to work. Wiped system, data, cache, installed OOS 3.0.1 and home button works again. Tried wiping again and installed CM 13, home button stopped working. Wiped and reinstalled OOS 3.0.1, home button works again.

Odd thing, my phone will only work with CM13 roms and OOS 2.2.0 or less for fps and home button. Nothing will fix or ever work.

For me, the home button stopped working for a short while on Graraks, then it just jumped back to life again and I haven't had any more home button blackouts after that. If it's a driver issue, it's an extremely intermittent one.
The fingerprint scanner has stopped working from time to time at lockscreen, but this is acceptable for an official hackjobb supported scanner until official sources are released ?

Need Help with this!
Hi everyone!
I have a OP 2 for more than one and a half years now and never had any issues with it(stayed stock...) until recently. I didnt update the phone to the latest version and was putting it off, and today in the afternoon when I tried to unlock my phone it said the 'Fingerprint hardware is not available' and after unlocking the phone with the pattern, it IMMEDIATELY LOCKS ITSELF BACK !!! after split second it just locks the screen while everything is working like connection, wifi, messages, notifications, etc. but due to this I cannot access anything on the phone, can't go to settings and switch to onscreen nav bar buttons, can't force stop/wipe cache the com.fingerprints.serviceext either, tried restarting it several times, downloaded the update but can't even install it because the phone just locks! I have no idea what would fix it and I am avoiding a full reset and wipe on the phone(also based on all i have read, dont think it would fix it anyways)
If anyone knows whats the problem or has dealt with it or knows someone who has, please help me out here on how to fix this and what to do. I did not root it or flash custom ROM's on it yet so literally dont know why it happened.
Thanks,
Max

Screen Rotate and Auto brightness issue after flashing lineage 14.1

Just as the title says, after flashing the bootstack, rom and gapps countless times, i still dont have auto rotate or auto brighness. all the sensors seem to be dead except for wifi, gps and mobile network. did anyone else experience this? how did you resolve it??? please help!!

I had the same problem after dirty flashing from 13.1. I did a factory reset and reflashed and all was well.

whoiswes said:
I had the same problem after dirty flashing from 13.1. I did a factory reset and reflashed and all was well.
Click to expand...
Click to collapse
thanks for the reply. i did a clean flash. didnt work.
i flashed the boostack, rebooted back to recovery, flashed the rom and gapps, wiped cache and rebooted. it boots fine. but then i still dont have auto rotate. seems like the drivers werent installed or something

Obvious questions, but did you check the rotation settings inside the display menu? Also, is Adaptive brightness toggled on?

MiMtnBiker said:
Obvious questions, but did you check the rotation settings inside the display menu? Also, is Adaptive brightness toggled on?
Click to expand...
Click to collapse
i did. i installed an app that checks the phones sensors. they are all undetected. i think its a driver issue. i'm at my wits end

crazynitro said:
i did. i installed an app that checks the phones sensors. they are all undetected. i think its a driver issue. i'm at my wits end
Click to expand...
Click to collapse
Check the md5 on your download to make sure it is not bad Install twrp 3.0.4.0 you could also move everything you want to keep to a sdcard so you can do a total wipe. Now install rom and gapps only and check to see how everything works before adding root or apps.

crazynitro said:
Just as the title says, after flashing the bootstack, rom and gapps countless times, i still dont have auto rotate or auto brighness. all the sensors seem to be dead except for wifi, gps and mobile network. did anyone else experience this? how did you resolve it??? please help!!
Click to expand...
Click to collapse
This is an old thread, but I am hoping you found a fix for these issues. I am having the same issue. If you have a solution to share I would greatly appreciate it.

lkiefer said:
This is an old thread, but I am hoping you found a fix for these issues. I am having the same issue. If you have a solution to share I would greatly appreciate it.
Click to expand...
Click to collapse
I lost my phone so i currently have another one. i can t remember what i did to fix it though

crazynitro said:
I lost my phone so i currently have another one. i can t remember what i did to fix it though
Click to expand...
Click to collapse
That's a drag. Thanks for the quick response though.

Hello, I also have an issue with the accelerometer (and by consequence the auto rotate function).
I am on full stock Nougat B09 (no root) and the issue was also present on B06.
Rebooting the device solve the issue, and factory reset does not make this bug disappear.
That being said, I think I located the root cause.
The magnetometer seems to be never working, even after a reboot. When an app wants to use the magnetometer (like Google map, or the compass), it make the accelerometer crash....
Anyone else having this issue ?
Does you magnetometer works flawlessly ?
Thanks.

@arachneon,
Hi, you can change it in the tools---compass, and in that compass you can waggle the phone in the way of "8", if all that cannot fixed you can also seek help in the nearby ZTE after sales service repair center. Thanks!

Can't pull down quick settings

Hello,
I have noticed since I have flashed the universal bootloader for LineageOS 14.1, that sometimes I am unable to perform the pull down action on the notification bar in order to open the quick settings.
Sometimes, this is fixed by locking the screen by pressing the power button and unlocking it after. This does not always work though. A more reliable way to "fix" this is to completely reboot the phone.
Can someone please advise if there's a known, more permanent, fix for this issue?
PS I went back to stock through EDL (shis should overwrite the boostack, right?), and the issue is present on stock rom too (2017G B10 7.1.1)
thanks a lot in advance!

rzarectha said:
Hello,
I have noticed since I have flashed the universal bootloader for LineageOS 14.1, that sometimes I am unable to perform the pull down action on the notification bar in order to open the quick settings.
Sometimes, this is fixed by locking the screen by pressing the power button and unlocking it after. This does not always work though. A more reliable way to "fix" this is to completely reboot the phone.
Can someone please advise if there's a known, more permanent, fix for this issue?
PS I went back to stock through EDL (shis should overwrite the boostack, right?), and the issue is present on stock rom too (2017G B10 7.1.1)
thanks a lot in advance!
Click to expand...
Click to collapse
Wait what? So you flashed the universal bootloader AFTER installing Lineage, and presumably using it?
If you installed an EDL ROM and the problem persists, it's definitely not the bootstack. are you sure there's nothing else that you installed both on stock and los?

Choose an username... said:
Wait what? So you flashed the universal bootloader AFTER installing Lineage, and presumably using it?
If you installed an EDL ROM and the problem persists, it's definitely not the bootstack. are you sure there's nothing else that you installed both on stock and los?
Click to expand...
Click to collapse
I definitely did not flash the bootloader after flashing lineage, I do not believe it's possible; my apologies if my wording was off.
As you said, it is possible that the switch to Lineage was just a coincidence.
You make a good point though, I did restore the same titanium backup apps on both ROMs. I should factory reset and see if it solves it.
cheers

rzarectha said:
I definitely did not flash the bootloader after flashing lineage, I do not believe it's possible; my apologies if my wording was off.
As you said, it is possible that the switch to Lineage was just a coincidence.
You make a good point though, I did restore the same titanium backup apps on both ROMs. I should factory reset and see if it solves it.
cheers
Click to expand...
Click to collapse
Yeah, I just didn't know what you meant. I guess it might be a root app or something. I used Material Notification Shade on stock but it had a couple of problems that i didn't figure out until some time ago (it was pretty obvious though)

And for something physical, have you fitted a screen protector lately? I had one that interfered with pull down.