Search results

Same here, face unlock suddenly stopped working a couple of hours ago, I deleted face data and tried setting it up again - receiving error message that face unlock enrollment didn't work

If the only thing concerning you about the OP6 is the camera (in comparison to 5X) - having both devices I can reassure you OP6 camera is miles better than Nexus 5X. And I wouldn't suggest buying Huawei to anyone. I think the oneplus offers the most nexus like software experience between all the...

There is a telegram group: https://telegram.me/XperiaXDA

I wrote it earlier

Greetings :) Factory reset does not wipe userdata (a.k.a internal storage), so OTA zip file was left intact :)

I was running omnirom with twrp, so I just downloaded the full OTA zip, did a factory reset and flashed the OTA zip from twrp. I have to note that twrp did not survive the update, I had to reflash it. Another question from me - is there any way to extract vendor.img from OTA zip or from running...

I've tested that d'n'b mix someone posted here on OmniRom with stock mixer path values (there is no low sound problem). No distortions on max volume

I guess they didn't want to just revert that change because it would affect multiple devices, even the ones which were not affected in a bad way by this change

Someone else reported distortion on 88 too, that's exactly the reason why I don't agree that this is a proper fix. LG d802 also has low volume on cm13 - if you edit mixer_paths to match the volume of stock ROM, there are noticeable distortions too

Well, if they proposed to go with that, I'm glad I got rid of CM in favor of OmniRom on my nexus. The speed and sound is on whole another level. I still remember when CM used to be like that, though

Nope, it didn't help at all. It's more likely that the update to android 6.0.1_r43 triggered this bug

Well I'm running the 20160621 nightly right now and it really doesn't feel like fixed

No, you are not. I just created an issue in cyanogenmod jira - https://jira.cyanogenmod.org/browse/NIGHTLIES-2973. Please vote and comment on it, if you have anything to add

I flashed 05.05 build right after spending a week with a 04.27 and noticed immediately, that sound has become much more silent. Like 50% more silent on max volume setting. Has anyone else noticed that?

Okay, I can answer to that myself already. Flashed bootloader and radio from mhc19j - everything's OK. But with this vendor.img it throws an error at startup. Tried mmb29v vendor.img too - result is the same. So, latest working vendor is from mmb29q with 2016 03 09 nightly

Has anyone tried MHC19J vendor.img, bootloader and radio on CM13? Does it boot? Does it feel any different from MMB29Q?

24 build is up. Going to test it right now UPD: Nothing's fixed, it's unusable just like 21 build. 18 build still way to go

20151118-UNOFFICIAL has working camera, GPS works too I think (from my home it sees one satellite). Sensors are not working, facebook is force closing, unless you delete libsslx.so on every boot.

I've tried it. Simcard is not recognized, so no cellular networks. Probably related to latest RIL changes in CM13 branch. Also system lags really bad. Camera is working just as in 20151118-UNOFFICIAL build, sensors still don't work, facebook still crashes

All sensors are not working - proximity, light, accelerometer, compass. I remember the same was with CM12.1 if wrong bootstack was used (there was no sound too, though). But here we can not try different bootstacks, as ROM is not booting at all with a different one.

Oh :) I suppose it does the same thing :)

If you are able to boot into ROM, but recovery installation is failing using autorec, you could install twrp using dd directly, when android is booted EDIT: look, I've even found a post telling how to do this exactly: http://forum.xda-developers.com/showpost.php?p=63632954&postcount=1890

AFAIK it installs recovery, using which you can install bumped twrp 2.8.7.3 and continue installing non bumped images then.

I've flashed recommended bootstack, but does it include recommended modem? Which one are you using?

I don't know if this is a known bug, but auto-rotation doesn't work for me (tried 17 and 18 builds)

I believe I've had JB bootloader, KK modem alone just wasn't enough to solve this

Just tried it, it works for me too! Awesome! :)

http://pastebin.com/HBcar2Vu log of device starting...Maybe you'll find something useful in it

I have tried this one today: http://forum.xda-developers.com/lg-g2/orig-development/aospa-5-paranoid-android-t2962766 Audio was working for sure, rotation too. Gonna try to provide some logs now...

No, I have never flashed any stock LP on mine. The only LP was CM12 Reboot not working like that: you press reboot screen goes black, then nothing long press power button - screen flashes long press power button again - starts booting normally

Doesn't work for me either :( Links from the second page given by varund7726 are dead :( ---------- Post added at 01:11 AM ---------- Previous post was at 01:08 AM ---------- Is audio working for you? Sensors, reboot do not work here too, plus audio. I have used CloudyG3 (KK) for some...

Thank you for your answers. I'm on d802. Tried to flash: LGD802_10B_EUR_RADIO dr87-D802_EUR_KKMODEM_AOSP Modem-D802_JB_Radio_KK_Baseband in that order. Unfortunately, none of those helped with this issue. Have to say, CM12 was working fine before flashing any of those, so was AOSPA+ (android 5.1)

Hi guys! I've installed this ROM (v 5.4.6) fresh (full wipe), but I have no sound and auto rotation is not working. Tried to flash JB modem - did not help. What could be the problem?

I've tried this on Lollipop CM12. It fails with "L Camera is not supported on your device" message. Checked the source code: val capabilities = characteristics.get(REQUEST_AVAILABLE_CAPABILITIES) val requiredCapabilities = List( REQUEST_AVAILABLE_CAPABILITIES_MANUAL_SENSOR...

SOD's are back for me, just had 2 in a couple of hours :(

Don't know is it just me, but it seems that starting with 0306 build SOD's are gone! Had 4-5 per day of those, now after two days still had none. Can anyone confirm this?

Cool, shazam is working on alpha 3 :) It didn't on alpha 2 :)

You have pushed it with a wrong name, so loki-flash does not find it :) you wrote: adb push openrecovery-twrp-2.6.3.3-g2att.img /data/local/tmp/openrecovery -twrp-2.6.3.3-openrecovery-twrp-2.6.3.3-g2att.img you need to write: adb push openrecovery-twrp-2.6.3.3-g2att.img...

Nope, it was on GB and ICS, but I believe vendors could have implemented triple buffering on their own, before google did it

D/SECHWC_LOG( 1879): Dump Window Information D/SECHWC_LOG( 1879): win->fd = 24 D/SECHWC_LOG( 1879): win->size = 1536000 D/SECHWC_LOG( 1879): win->rect_info.x = 0 D/SECHWC_LOG( 1879): win->rect_info.y = 0 D/SECHWC_LOG( 1879): win->rect_info.w = 480 D/SECHWC_LOG( 1879): win->rect_info.h = 800...

HTC Tattoo -> HTC Magic -> Huawei U8800Pro -> Samsung Galaxy S2 :)

Because the one you're trying to flash is for Galaxy Nexus, not for Galaxy S2

You can adb when bootlooping, or when in recovery. And do anything with the filesystem then

We need to annoy huawei's client support service further

You mean no kernel source available. That's right, you can't do OC kernel without source

That goes for 5.0.2.6 recovery too (it's u8800 only). And I believe you did the same thing with CM7 for U8800, not Pro

Haha, you wish. It only has the same look, hardware is completely different. C8800 is a lot worse

Sorry, I think it's not ready yet to be on the first post

Nah, it's the froyo one. But will do for now

You can put it if you like, but you don't have to