[ROM] LegacyHuawei CyanogenMod 11.0 - Huawei Ideos X5 U8800

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?

Related

Elelinux-7.0.0-Hero-v2.0 - issues

I am writing on this thread as i still cannot add to the development thread yet
I am using Elelinux-7.0.0-Hero-v2.0. Thanks Ele for a great rom.
So far the only problem i have had is once the unlock screen went invisible on me.
I had to use the patch which worked fine. no black screen. everything else works great so far.
Just trying to contribute to the developers what i can to help.
Any one else has any issue yet.
Elelinux-7.0.0-Hero-v2.0
RADIO VERSION:63.18.55.06SU_6.35.17.03
Kernel: Herokernel-12a
I've had the same issue with the lockscreen but like yourself it was a once off.
Generally the ROM is great (however, this is the first ROM that I've flashed to my hero)
The only other issue im getting is with linking facebook with my contacts; for some reason FB keeps crashing. But keep in mind that I'm a retard in comparison to what you lads know about custom roms etc..... but slowly learning!
Sent from my Hero using XDA App
same problems
I have had the same problems as you. lock screen went invisible a couple of times. and my facebook does not work quite right.
Apart from that has been very stable. no problems or reboots. works great.
Running gingerbread with honeycomb theme on my hero. running at 691mhz is well good.
I have got widgets running on every screen to.
Elelinux RC4 version 7.0 V2.0
kernel 12a
691mhz
clockworkmod.
Thanks Ele for a great rom
After installed 2.0 patch, I still get blank screen (wall paper ok, no any widgets).
The only way to solve is restart
Any thing wrong with my installation? (same spec as above post)
The Bug seems to affect some phones and not others. Might be due to different hardware but not sure.
I am a network engineer. Not a developer.
There is a patch that fixes the black screen bug which might help. You might have to delete dalvik cache first though. But as said not a developer.
I just wanted to try some different roms and loaded cronos rom yesterday and is very good. So running that at the moment.
It is really fast and stable. The fastest i have used so far. But i have not tested everything yet like GPS. But admit i am becoming a cronos fan.
Cheers.
P.s i always backup my phone first and do a complete wipe before trying a new rom. Otherwise could get problems.
I use clockwork mod.
Unfortunately the bug your getting with black screens, invisible menus etc.. is an aosp bug that affects some devices which Google are unable to fix, if you had read through the thread you would have seen this. Ele is working hard on a fix for this but as CM no longer support the hero, its unlikely many cm7 roms will see many updates.
Sent from my HTC Hero using XDA App
Everyone is hoping that Google will fix the memleak and invisible manus problem. To fix it, one needs to undersatand the big picture on how these things are managed. I think it can be done only by experienced coder.
It's a real shame. i love gingerbread and did not want to go back to 2.1 or 2.2.
But might have to if they do not fix it.
I know Ele is working hard on a fix. using his rom at the moment. Was using cronos. But suddenly started getting random reboots and battery started only lasting a few hours and could not find out why.
Thanks to all devs and help.
Elelinux 7.0 v2.1 GPS reboot issue
Hi all,
I found Elelinux 7.0 v2.1 to be almost perfect.
The only major issue so far for me is that when running applications such as sportstracker that use GPS and are running in the background, that as soon as the GPS connection is lost (for whatever reason) the phone always seems to crash.
I wonder whether anyone else has seen this issue and whether there's a way to investigate it.
E.g. is it possible ot redirect logcat to the sdcard and then analyze the log file?
Regards,
MJ
Her0 V2.1 - USB problem
This is a weird one...
I flashed to Elelinux 's fab 2.1 the usual way....
I booted into the ClockworkMod Recovery V2.5.0.7
-- wipe cache partition
-- Advanced - Wipe Dalvik Cache
-- reboot
Then again within Clockwork Recovery I choose 'Install zip from sdcard'
I select the Hero rom and it flashes perfectly...
Now the problem ----> I cant get the usb port working to enable transfer of files?
When the phone boots up it shows 'preparing sd card'
Then when i connect usb lead to pc it shows 'usb connected'
When i then pull the screen down, i see 'usb connected - select to copy files to/from your computer'
When i select that tab, it just crashes back to the home page?
I see the icon at the top of the screen but when i pull down the screen and select as above, it crashes back to home screen again?
In settings, i have both USB debugging and USB debugging notify - all enabled.
Can anyone provide a solution to this issue for me..
thank you
The only way around this problem i think is to mount usb storage from recovery.
Sent from my HTC Hero using XDA App

[TELUS T959D Fascinate]-Running ONECOSMIC'S ICS

Hello.
This is where you can look at the tutorial and get the files to install if you feel like jumping into it ...
ICS Step by step and files
Note: if you do flash this and it hangs at the boot screen, pull the battery and flash it again and it should work. Some have had to do it 3 times.
I take no credit for this ROM and full props go to the developers of the above post and all those working to make this happen.
First the look and feel of ICS is nothing short of superb. The speed as of now is similar to all the other ROMS I have tried with a little chop here and there but nothing major.
Yes lots of little issues and items that do not work like the camera and GPS but not a huge deal for me so I am willing to stick to it.
Battery so far is decent. 13 hours and 43 min. on the first charge to calibrate and sitting at 24% still. This included allot of playing with the phone and reboots to test jigs
As for the issues that are somewhat bothersome, they include the following.
1. No home or search button. I know same as usual when installing an i9000 ROM but the key mappings from the GB ROMS does not work.
2. BLN (issue all around) will remain lit until you wake the phone to get the notification.
3. They had to do some funky stuff to get 3G to work so it lags to start. Not a huge deal cause it does start and remain working.
I will be continuing to use this ROM and hopefully everything will be working soon (these guys are flying. Also I have been told that the folks over at Glitch are already working on the kernels for the ICS port so that is promising as well.
If there are any other out there running this on our phone chime in with your thoughts or fixes if you have any.
Thanx
Bucky
Thanks for starting this thread. Can't wait to hear about your progress.
Alpha 7
Hey here is the update ...
Installed the Alpha 7 update today and I have to say this rom is fantastic.
1. Camera is fixed and works like a charm.
2. GPS locked in seconds and accurate indoors!! Big improvment over all other roms I have used.
3. HW Acceleration is fixed and working from what I can tell
4. You Tube is fixed and can watch video
Still on the not working list
1. Can not plug the phone in while off as it just restarts. this is a work in progress and known issue
2. Can not record video
3. Will not read a SIM card for contacts and so on (thank god for Google sync)
4. Still no home or search buttons (I think I may need to work on that on myself unless a kernel is released)
SO my review so far ...
No real issues with the general use of the phone. Text, phone, email and web are solid, I have installed apps from the market with no issues and not one FC yet. Battery life is good and nothing is taking over. I have been able to use the phone all day and still have lots left over before going to bed and plugging in. I have not been through a full battery as of yet but that is what I am working on now.
Memory - Last I looked I had 174MB of memory remaining which is the highest I have seen.
ICS is really smooth and fast while moving around. I am going to continue to play with it and report back here for everyone.
I don't use a whole lot of apps so there won't be much regarding those.
Thanx for stopping by and I will post pics when I can.
Bucky
Nevermind
Sent from my SCH-I500 using XDA App
Thanks for the update. From your review, it sounds like an awesome rom. Can't wait to try it but need them to fix the video recording first. Although I might just cave and try it out just to see what the fuss is all about
Can always restore my current setup... lol.
Update ...
been getting the SOD today and not sure why, I mentioned above that the HW acceleration was working, I misunderstood and it is not fully working yet.
I found that the system partition is very small. There was an update which required copying libs and there was not enough space left to do this (2MB). Not too sure if this is due to coming from MIUI or just a ROM issue.
Alpha 8 was released but had quite a few issues so not flashing that one.
Daily use has been great so far (except for the SOD) with no reception or data issues.
I am still working on the home and search buttons but I think that will get fixed with a kernel update. I tried the keymap file but these buttons do not even register in recovery so I get nothing in the ROM either.
More to come ...
Haven't tried this (likely won't as I need the phone for work) but buck have you tried the manual key fix - some directions in our thread on putting on Darkys 10.3.
Sent from T959D running Miui
Yup been there done that no go
Sent from my GT-I9000 using XDA App
Hey buck , was doing some searching in teamhacksung's thread about their ICS port, and someone suggested to change the following and then the key mapping for our phones will work properly. Not sure if the file system is the same for both, but definitely a bit of info if it isn't!
All you have to do is change this part on**arch/arm/mach-s5pv210/mach-aries.c*
*Original**(line 1216~1221)
static const int touch_keypad_code[] = {
#if defined (CONFIG_SAMSUNG_GALAXYS) || defined (CONFIG_SAMSUNG_GALAXYSB)
KEY_MENU,
KEY_BACK,
*0,*
*0*
----------------------------------------------------------------------------*
*Edited*
static const int touch_keypad_code[] = {
#if defined (CONFIG_SAMSUNG_GALAXYS) || defined (CONFIG_SAMSUNG_GALAXYSB)
KEY_MENU,
KEY_BACK,
*KEY_HOME,*
*KEY_SEARCH*
Sent from my GT-I9000 (T959 mod) using XDA App
Thank for the input. After flashing bata 1 all the buttons are working. More to come: )
Sent from my GT-I9000 using XDA App
Hey, have a telus fascinate too. Know how to flash and all that fun stuff. Just don't fully follow where you make the changes for key mapping...if you could just guide me in the right direction, I can figure the rest out...
changes in the kernel zip? the beta zip? after flashing? something completely different?
thanks a lot!
There are no changes to be made with this ROM, they are built in. Just flash and all good.
I will post update tonight after work.
Sent from my GT-I9000 using XDA App
yeah sorry realized that immediately after posting / flashing to the new rom.
have you tried out BT audio? I can connect to different devices but audio won't stream
havoksupertwit said:
yeah sorry realized that immediately after posting / flashing to the new rom.
have you tried out BT audio? I can connect to different devices but audio won't stream
Click to expand...
Click to collapse
There are allot of BT related posts in the QA. I personally do not use any BT but I do have a headset that I will try when I get home.
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
bucknetbucky said:
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
Click to expand...
Click to collapse
Calibrated my phone this morning. Heavy use today configuring everything but about 52% now (sooo 5 hours or use?)
Why god! Whhyyy!!
bucknetbucky said:
There are allot of BT related posts in the QA. I personally do not use any BT but I do have a headset that I will try when I get home.
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
Click to expand...
Click to collapse
AT LEAST YOU GUYS HAVE IT RUNNING!!
I am having a hell of a time trying to get it to work. I have tried so many different ways to get it up and running but no luck.
I've tried installing it from MIUI 3 times but all I get when trying to boot into ICS for the first time is a Black Screen after the FuguMod boot screen.
The funny thing is that the 4 soft buttons at the bottom light up still.
So I then decided to try the JVT way:
-Flashed JVT DARKYROM (ODIN)
-Lagfix OFF
-FULL WIPEs (factory reset, cache, dalvik)
-FLASHED CM7.1 STABLE
-FULL WIPEs (factory reset, cache, dalvik)
-Flash ICS BETA1
-Flash kernel
-FOR THE SECOND TIME:
-Flash ICS BETA1 AGAIN
-Flash kernel AGAIN
Same issue, black screen after the FuguMod boot screen, buttons still light up.
So i tried a couple more times in a few different ways based off what I have already tried, but this time, before booting into ICS for the first time, I installed the 'Superuser-3.0.6-efgh-signed.zip' package.
Same issue. I'm not having any luck here.
iwebsource said:
AT LEAST YOU GUYS HAVE IT RUNNING!!
I am having a hell of a time trying to get it to work. I have tried so many different ways to get it up and running but no luck.
I've tried installing it from MIUI 3 times but all I get when trying to boot into ICS for the first time is a Black Screen after the FuguMod boot screen.
The funny thing is that the 4 soft buttons at the bottom light up still.
So I then decided to try the JVT way:
-Flashed JVT DARKYROM (ODIN)
-Lagfix OFF
-FULL WIPEs (factory reset, cache, dalvik)
-FLASHED CM7.1 STABLE
-FULL WIPEs (factory reset, cache, dalvik)
-Flash ICS BETA1
-Flash kernel
-FOR THE SECOND TIME:
-Flash ICS BETA1 AGAIN
-Flash kernel AGAIN
Same issue, black screen after the FuguMod boot screen, buttons still light up.
So i tried a couple more times in a few different ways based off what I have already tried, but this time, before booting into ICS for the first time, I installed the 'Superuser-3.0.6-efgh-signed.zip' package.
Same issue. I'm not having any luck here.
Click to expand...
Click to collapse
OK so here is what I did ...
Started from MIUI 1.11.18
1. Do a nandroid backup
2. download all the files to the SD card. This includes the ROM, Kernel and super user fix
Links:
Kernel:http://ice-cream-sandwich-sgs.googlecode.com/files/FuguModICS_GT-I9000_update.zip
ROM:http://ice-cream-sandwich-sgs.googlecode.com/files/ICS_4.0.1_r1-Beta1-i9000.zip
Super User:http://ice-cream-sandwich-sgs.googlecode.com/files/Superuser-3.0.6-efgh-signed.zip
3. Boot to recovery and do factory reset, wipe cache and davlik cache
4. Install the Kernel first and reboot now
5. Boot into recovery factory reset and wipe cache and Davlik and Install the ROM then reboot now
6 Boot back to recovery and install the Kernel again with out the wipe
7. If after reboot you do not have root then boot to recovery and flash super user fix
8. reboot and it should be working at least it was for me
It seems to me that you are missing the first flash of the kernel before the ROM. It sets up the file system from what I gather
Note: If needed flash the kernel and rom then kernel again with all the wipes as mentioned above.
I know there are allot of folks having issues getting it to run. Not too sure if it was the way I installed MIUI that might have made the difference.
My battery is charging now so I can calibrate it and see how it goes after that (it drained pretty quick today) lol.
I hope you can get it going cause it truly is awesome
Still not working:
Can not charge with the phone off
Google TTS stops working
Phone will not vibrate for SMS or email when in silent mode
BLN stays on for notifications until the phone is taken out of sleep (can be turned off)
Compass is why off (have not attempted to calibrate yet though)
11 MB left in the system partition (not much but I do not think there will be many changes there)
Video play back is choppy and some will not play
Bucky
regarding the black screen:
- had that too... I let it sit on the black screen for 2-3 minutes and then it went to the boot screen animation (a multi-coloured )...that for a few minutes...then finally booted.
How i got it working:
a) Started on MIUI...booted into clockwork
b) Backup
c) Wipe data / factory reset and cache and dalvik cache
d) Install rom and then kernel
e) Restart
f) Install rom and then kernel
g) Restart and wait very patiently for a little while
h) Once it all works, can reboot into clockwork and install superuser
Good luck! I really think the rom is nearly stable enough for daily use...
-------
Also have the no vibrate on silent... haven't tried the other stuff yet.
Oh and TTS hasn't crashed on this version yet for me...
Astrid glitches a little to a lot.
Changing from google tts to picco tts solves the problem there. As for the other stuff it is all reported as known.
I am using as a daily on my phone and no issues with general use. Still testing battery and that seems to be a bit of an issue with regard to Android OS as usual
Sent from my GT-I9000 using XDA App
So to install this ROM I would just have to install it as per totallydubbed's instructions? I don't want to flash miui if I don't have to to try this out.
Sent from my GT-I9000 (T959 mod) using XDA App

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

Most stable Lollipop/Marshmallow ROM?

Hi! I think I've tried every Lollipop/Marshmallow ROM out there, but I haven't found one as stable as KitKat ROMs (CM11/Stock). I just want a Lollipop/Marshmallow ROM that doesn't hang every time I open YouTube from recents (many apps suffer of that too), and with working WiFi (had this problem with CM13), and with decent battery life. CM13 is actually one of the most stable ROMs I've tried, but it had serious WiFi problems (it simply disconnects from the WiFi and then reconnects saying it doesn't have internet access, very annoying), some kind of TV-like static when booting and sometimes when unlocking the phone, and the recents cards sometimes got cut off (though this is not really a deal breaker). The only Marshmallow ROMs I haven't tried are BeanStalk and Mokee because they are based on CM, so I supposed they have the same problems. So, what's the most stable Lollipop/Marshmallow ROM you have tried? And can that ROM be used as daily driver?
Thanks!
Sorry for my English lol.
Which other Roms have you tried?
MuhammadBilal said:
Which other Roms have you tried?
Click to expand...
Click to collapse
Exodus (5.0, will try 5.1), BlissPop, DirtyUnicorns, dhacker's unofficial CM12, Mokee (5.1), ResurrectionRemix, unofficial CM13...
EDIT: Tried Exodus 5.1, really slow.
MoKee
So far, so good (It's only been 24 hours since I've installed it) on the 17-01-29 build of Mokee here
Wifi has been solid with no issues, rom seems stable, and YouTube ran fine from recents.
Update: Had strange problem with downloading email attachments with both gmail and Yahoo mail. Back to stock KK for the time being.
Update: Turns out the above email problems had to do with permissions.
beeewell said:
So far, so good (It's only been 24 hours since I've installed it) on the 17-01-29 build of Mokee here
Wifi has been solid with no issues, rom seems stable, and YouTube ran fine from recents.
Update: Had strange problem with downloading email attachments with both gmail and Yahoo mail. Back to stock KK for the time being.
Click to expand...
Click to collapse
It doesn't even boot here, first time it booted but it said that encrypting my device failed (WTF?) and then rebooted to do a factory reset, and it wiped the system partition. xD
I installed it again without Gapps and now it won't do anything, it justs sits there in the bootanimation for several minutes and then reboots. Perhaps​ I didn't downgrade correctly? How did you downgrade? I used RSD Flasher, and it has worked fine for me in the past.
trivialPotato said:
It doesn't even boot here, first time it booted but it said that encrypting my device failed (WTF?) and then rebooted to do a factory reset, and it wiped the system partition. xD
I installed it again without Gapps and now it won't do anything, it justs sits there in the bootanimation for several minutes and then reboots. Perhaps​ I didn't downgrade correctly? How did you downgrade? I used RSD Flasher, and it has worked fine for me in the past.
Click to expand...
Click to collapse
It took me awhile to find the procedure and files that I used to downgrade/upgrade, but I finally did. Thanks to Nobe1976, this method of going back and forth from KK to JB doesn't require a PC; There are 2 zip files that you can flash w/ TWRP to go back and forth. Here's the procedure and file links: http://www.droidrzr.com/topic/50096-how-tomobile-downgrader-flash-back-10-09-14-14/
I too thought Exodus was stable, but slow. I liked using MoKee 5.1, but I had an annoying problem with it that I couldn't solve: Every time I picked up my phone, there was a notification to sign back onto my WiFi network. It did so without asking for any credentials, but it got too annoying for me.
Right now, I'm using PacMan Rom (4.4.4), and it's been performing very well and is stable. Here's the link in case you wanna try: https://s.basketbuild.com/devs/pacman/moto_msm8960/KK/release
beeewell said:
It took me awhile to find the procedure and files that I used to downgrade/upgrade, but I finally did. Thanks to Nobe1976, this method of going back and forth from KK to JB doesn't require a PC; There are 2 zip files that you can flash w/ TWRP to go back and forth. Here's the procedure and file links: http://www.droidrzr.com/topic/50096-how-tomobile-downgrader-flash-back-10-09-14-14/
I too thought Exodus was stable, but slow. I liked using MoKee 5.1, but I had an annoying problem with it that I couldn't solve: Every time I picked up my phone, there was a notification to sign back onto my WiFi network. It did so without asking for any credentials, but it got too annoying for me.
Right now, I'm using PacMan Rom (4.4.4), and it's been performing very well and is stable. Here's the link in case you wanna try: https://s.basketbuild.com/devs/pacman/moto_msm8960/KK/release
Click to expand...
Click to collapse
Thank you so much! That will save me so much headaches lol.
I'm using lastest CM11 snapshot, working fine, but I find the battery doesn't last as much as in CM12.1.
EDIT: I'm writing from Mokee 6.0! That method for downgrading works flawlessly!
Mokee feels better than CM12.1 except by that TV-like interference when you unlock the device, and I haven't tried the WiFi, but it looks okay.
Thing to remember while reading all of the below, I have an XT905, with a JBBL.
I'm currently using "cm-13.0-20161205-ilichva-xt907_jbb.zip" for my daily. The only repeated "fails" I have is where WiFi will disconnect, however, it only happens if I am not using it and the phone is asleep. One thing I have noticed is that this is the only ROM that actually does go into deep sleep for me. I'm only on Wifi at home for extended periods (ie when phone goes to sleep). This may be the reason the other ROMs don't loose WiFi, because they don't go into deep sleep for me. My Wifi disconnects, and never is connected without internet. I just go into Wifi, select my network and say connect, and its all good again.
Previously (a few years back) I was using BlissPop (Lollipop), but did not use the latest build. I had better luck with "BlissPop-v3.9-moto_msm8960_jbbl-OFFICIAL-20150829-1751.zip"
Others I have used (Lollipop) and found pretty stable (ie used as daily for some time) were:
CARBON-5.1.1-Final-moto_msm8960_jbbl.zip
Resurrection-Remix-LP-v5.5.8-moto_msm8960_jbbl.zip
and for KitKat
LS-KK-MileStone-3.2-moto_msm8960_jbbl.zip
With the CM13 ROM I have a 64GB SDCard, F2FS cache partition, Xposed, Viper, a Linux Swap Partition (512mb) and personally find it to be the most stable ROM I have used (apart from WiFi) on the phone. Some of the Lollipop (bliss pop included) could not run my live wallpaper (Celestial Bodies). I have also noticed that at least one app using the CPU (a Solitaire game attempting to find a winnable deal manually) actually runs a lot faster in CM13 than in the others.
If YouTube bothers you, maybe you should try the alternatives such as New Pipe or OGYouTube etc etc. Actually, I just tried YouTube from the recents,and it worked fine for me.
As for the TV Static on boot (just before animation) I have had that since I first unlocked the bootloader; I thought It was normal. It has been independent of any ROMs and it happens for me on every ROM.
Mokee 5.1
Sorry for going off-topic but would any of you guys happen to have a copy of the last LP Mokee build that was released on 4PDA ?
MK51.1-xt907_jbbl-20160420-ilichva.zip
The link is unfortunately dead and I can't find a mirror anywhere. I'd like to save a copy just in case anyone asks in the future. If any of you have, would you please share privately with me? Thanks a lot!
DiamondJohn said:
Thing to remember while reading all of the below, I have an XT905, with a JBBL.
I'm currently using "cm-13.0-20161205-ilichva-xt907_jbb.zip" for my daily. The only repeated "fails" I have is where WiFi will disconnect, however, it only happens if I am not using it and the phone is asleep. One thing I have noticed is that this is the only ROM that actually does go into deep sleep for me. I'm only on Wifi at home for extended periods (ie when phone goes to sleep). This may be the reason the other ROMs don't loose WiFi, because they don't go into deep sleep for me. My Wifi disconnects, and never is connected without internet. I just go into Wifi, select my network and say connect, and its all good again.
Previously (a few years back) I was using BlissPop (Lollipop), but did not use the latest build. I had better luck with "BlissPop-v3.9-moto_msm8960_jbbl-OFFICIAL-20150829-1751.zip"
Others I have used (Lollipop) and found pretty stable (ie used as daily for some time) were:
CARBON-5.1.1-Final-moto_msm8960_jbbl.zip
Resurrection-Remix-LP-v5.5.8-moto_msm8960_jbbl.zip
and for KitKat
LS-KK-MileStone-3.2-moto_msm8960_jbbl.zip
With the CM13 ROM I have a 64GB SDCard, F2FS cache partition, Xposed, Viper, a Linux Swap Partition (512mb) and personally find it to be the most stable ROM I have used (apart from WiFi) on the phone. Some of the Lollipop (bliss pop included) could not run my live wallpaper (Celestial Bodies). I have also noticed that at least one app using the CPU (a Solitaire game attempting to find a winnable deal manually) actually runs a lot faster in CM13 than in the others.
If YouTube bothers you, maybe you should try the alternatives such as New Pipe or OGYouTube etc etc. Actually, I just tried YouTube from the recents,and it worked fine for me.
As for the TV Static on boot (just before animation) I have had that since I first unlocked the bootloader; I thought It was normal. It has been independent of any ROMs and it happens for me on every ROM.
Click to expand...
Click to collapse
The TV-like static seems to be something with the JBBL, it happens even in recovery for me (when the recovery locks and turns off the screen). About the WiFi, it disconnected even if I was playing a game or using the internet, but I live in a place where I don't have WiFi anymore, so it's not a problem.
Indeed, Mokee 6.0 and CM13 are the most stable ROMs I've tried, even more than CM11, except for the bugs said above, even the battery lasts more.
BTW, how do you increment swap? I've tried several methods, but it still shows 256MB.
trivialPotato said:
The TV-like static seems to be something with the JBBL, it happens even in recovery for me (when the recovery locks and turns off the screen).
Click to expand...
Click to collapse
I only get it when I reboot, but get it every time.
trivialPotato said:
About the WiFi, it disconnected even if I was playing a game or using the internet, but I live in a place where I don't have WiFi anymore, so it's not a problem.
Click to expand...
Click to collapse
I personally have only seen it happen when the I wake the device up. Never has it occurred while I am using it.:angel: Last night I was searching for another thing in Xposed, and I saw a lot of Wifi type modules. Though most were about turning wifi off when the screen goes off; but I wasn't looking for Wifi stuff, so maybe you could find something that helps.
trivialPotato said:
Indeed, Mokee 6.0 and CM13 are the most stable ROMs I've tried, even more than CM11, except for the bugs said above, even the battery lasts more.
Click to expand...
Click to collapse
I tried Mokee, and I cant remember why, but it wasn't OK as a daily for me. To be honest, I would find it hard to go back to a ROM (ie less than MM) that does not have privacy guard. I also forgot to mention on my phone I have Adaway and Lucky Patcher and > 10 boot scripts (such as swap, IO optimisations, trim command, disabling media scanner on boot ... etc etc etc)
trivialPotato said:
BTW, how do you increment swap? I've tried several methods, but it still shows 256MB.
Click to expand...
Click to collapse
I am guessing by "increment" you really mean implement? Assuming that, I use a boot script. Currently I use a swap partition, so, for that I:
1. create a linux swap partition on the SDCard using Minitool Partition Wizard
2. Put the card into my phone, boot it and Find out the partition details (eg "/dev/block/mmcblk1p2" on my card now)
3. create a boot script to enable it on boot. The meat of the script is:
Code:
swapon /dev/block/mmcblk1p2;
Previously I have used a swap file, which is actually more complex. Something like:
Code:
location=/mnt/media_rw/sdcard1/data/local/tmp;
file_name=swapfile.dat;
desiredsizemb=512;
dd if=/dev/zero of=$location/$file_name bs=1048576 count=$desiredsizemb;
swapon -p 16000 $location/$file_name;
Hope the above helps, and let me know if you get it working.
DiamondJohn said:
I only get it when I reboot, but get it every time.
I personally have only seen it happen when the I wake the device up. Never has it occurred while I am using it.:angel: Last night I was searching for another thing in Xposed, and I saw a lot of Wifi type modules. Though most were about turning wifi off when the screen goes off; but I wasn't looking for Wifi stuff, so maybe you could find something that helps.
I tried Mokee, and I cant remember why, but it wasn't OK as a daily for me. To be honest, I would find it hard to go back to a ROM (ie less than MM) that does not have privacy guard. I also forgot to mention on my phone I have Adaway and Lucky Patcher and > 10 boot scripts (such as swap, IO optimisations, trim command, disabling media scanner on boot ... etc etc etc)
I am guessing by "increment" you really mean implement? Assuming that, I use a boot script. Currently I use a swap partition, so, for that I:
1. create a linux swap partition on the SDCard using Minitool Partition Wizard
2. Put the card into my phone, boot it and Find out the partition details (eg "/dev/block/mmcblk1p2" on my card now)
3. create a boot script to enable it on boot. The meat of the script is:
Code:
swapon /dev/block/mmcblk1p2;
Previously I have used a swap file, which is actually more complex. Something like:
Code:
location=/mnt/media_rw/sdcard1/data/local/tmp;
file_name=swapfile.dat;
desiredsizemb=512;
dd if=/dev/zero of=$location/$file_name bs=1048576 count=$desiredsizemb;
swapon -p 16000 $location/$file_name;
Hope the above helps, and let me know if you get it working.
Click to expand...
Click to collapse
Mokee has be running pretty solid here, I'll try CM13 and/or BeanStalk in a few days, though.
About swap, if I run "free" in the Terminal it shows it has swap memory, and I tried several methods (well, apps) to increment it but no luck. I'll try yours in a few days.
About the WiFi and the TV-like static, I bet is some difference between xt905 and xt907.
trivialPotato said:
Mokee has be running pretty solid here, I'll try CM13 and/or BeanStalk in a few days, though.
About swap, if I run "free" in the Terminal it shows it has swap memory, and I tried several methods (well, apps) to increment it but no luck. I'll try yours in a few days.
About the WiFi and the TV-like static, I bet is some difference between xt905 and xt907.
Click to expand...
Click to collapse
Well, the swap you currently see is ZRam, which is a compressed partition of memory used as a swap partition. ie not a file or physical partition on an sdcard (as I use above, in addition to ZRam). To increase ZRam, you loose available memory. That can be simply changed with the following lines:
Code:
echo 1 > /sys/block/zram0/reset;
OR
swapoff /dev/block/zram0;
echo "201326592" > /sys/block/zram0/disksize;
mkswap /dev/block/zram0;
swapon /dev/block/zram0;
The number is 1024*1024*target_size (MB eg 600). I think you have to do it at boot time or you end up with device or resource busy messages.
Or you could use Kernel Adiutor - Virtual Memory
That actually reminds me, one bug I have noticed on all the CM13 ROMs I tried, was that the init.d did not work, I had to use Kernel Adiutor to implement it; and I have a lot of scripts.
Currently running the new Lineage ROM http://forum.xda-developers.com/showthread.php?t=3577746. Thanks to Ilichva...
So far, so good !!! Performing very well with no issues found yet. :thumbup:
It still has the WiFi disconnecting when asleep for me.
beeewell said:
Currently running the new Lineage ROM http://forum.xda-developers.com/showthread.php?t=3577746. Thanks to Ilichva...
So far, so good !!! Performing very well with no issues found yet. :thumbup:
Click to expand...
Click to collapse
Performing well here, too! It has the same bugs CM13 had, but I feel is a bit snappier.
Is it just me, or is the default swappiness set at 100? (cat /proc/sys/vm/swappiness)
I actually tried lowering it to the android default of 60, and the ROM felt less "snappy", so put it back at 100
DiamondJohn said:
Is it just me, or is the default swappiness set at 100? (cat /proc/sys/vm/swappiness)
I actually tried lowering it to the android default of 60, and the ROM felt less "snappy", so put it back at 100
Click to expand...
Click to collapse
Indeed, is set at 100.
Possible Wifi fix?
trivialPotato said:
I just want a Lollipop/Marshmallow ROM ... and with working WiFi (had this problem with CM13), and with decent battery life. CM13 is actually one of the most stable ROMs I've tried, but it had serious WiFi problems (it simply disconnects from the WiFi and then reconnects saying it doesn't have internet access, very annoying).
Click to expand...
Click to collapse
DiamondJohn said:
...I'm oly on Wifi at home for extended periods (ie when phone goes to sleep). This may be the reason the other ROMs don't loose WiFi, because they don't go into deep sleep for me. My Wifi disconnects, and never is connected without internet. I just go into Wifi, select my network and say connect, and its all good again.
Click to expand...
Click to collapse
I have made a change to build.prop, which APPEARS to have bettered my Wifi stability.
Now, its only been a few hours, so its pretty early to say :fingers-crossed: it has definitely fixed it, but normally within this time, I would of expected to loose my Wifi connection, but it hasn't. :highfive:
Also, the change I made, I have read is actually only set at build time and thereby built into the ROM and not read from the build.prop.
The build.prop setting is: wifi.supplicant_scan_interval. My RAZR had it set to 30, while my N5 was set to 15. I have set it down to 5 (for testing purposes ) Searching the net will bring up heaps of explanation of what the setting is for (and also info saying its only a build time property)
So in summary, I have set the following build.prop
Code:
wifi.supplicant_scan_interval=5
And my WiFi has been solid for the past 3 hrs (normally in sleep except for being woken every 10 minutes to check its still ok ). Let me know if it works for you.
DiamondJohn said:
I have made a change to build.prop, which APPEARS to have bettered my Wifi stability.
Now, its only been a few hours, so its pretty early to say :fingers-crossed: it has definitely fixed it, but normally within this time, I would of expected to loose my Wifi connection, but it hasn't. :highfive:
Also, the change I made, I have read is actually only set at build time and thereby built into the ROM and not read from the build.prop.
The build.prop setting is: wifi.supplicant_scan_interval. My RAZR had it set to 30, while my N5 was set to 15. I have set it down to 5 (for testing purposes ) Searching the net will bring up heaps of explanation of what the setting is for (and also info saying its only a build time property)
So in summary, I have set the following build.propAnd my WiFi has been solid for the past 3 hrs (normally in sleep except for being woken every 10 minutes to check its still ok ). Let me know if it works for you.
Click to expand...
Click to collapse
Will try this next weekend (I don't have WiFi right now). I hope it works lol.
EDIT: It didn't. :crying:

[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.

Categories

Resources