Possibly by using a Sony apps module on magisk then downloading the Mirrorlink apk. Or try and find a zip fileWorkaround like how? I am very interested in that
Possibly by using a Sony apps module on magisk then downloading the Mirrorlink apk. Or try and find a zip fileWorkaround like how? I am very interested in that
Lineage OS does not have substratumSubstratum do not work, better chippa_a's prevous builds
I wasn't used a long time LineageOS, cuz i broke my Yuga. So when i was used it chippa_a has added support for substratum, all old users know datLineage OS does not have substratum
Yeah I was the first person on the thread to complain about the same thing aha ?I wasn't used a long time LineageOS, cuz i broke my Yuga. So when i was used it chippa_a has added support for substratum, all old users know dat![]()
maybe, i wasn't search for datYeah I was the first person on the thread to complain about the same thing aha
Tested new nightly lineage-14.1-20171020 and audio with headphones works fine. I don't know what went wrong with previous nightly update: maybe I forgot to clean cache/dalvik after installation?There are no changes related to audio configurations.
Please test with different headphone?
I would be on the same place for contacting :good:
Hi @Daedroza, Im sorry to bother you again. Here is an other last_kmsg from last rebooting since I did what you asked. Thanks.If you're available, please let me know. I have personally messaged you and I want you to run some test for fixing your reboot problem.
Thanks!
audios not working
I know, it was 1st. release, like preview version. Have bugs, not for daily use for now, and Dev/Assist. Is removed post, so it's just a first look , how it looks, will be enough changes, but one thing is certain, hes commingaudios not working
lag on recent app
search settings fc
sensor not working
camera not tested
I tried to flash TWRP:
Code:fastboot flash recovery twrp-3.0.2-0-yuga.img
Googled about this issue, looked like a locked bootloader; actually it was unlocked before installing LineageOS, I unlocked it again successfully (but this caused a factory reset to the phone), but when I retried to flash TWRP as above... same error.
At the end, I discovered that TWRP can be flashed in rooted devices via its own app from Play Store and this allowed me to install TWRP recovery quickly and easily.
Kind regards
Aldo
can next update upload for testing rom ?I know, it was 1st. release, like preview version. Have bugs, not for daily use for now, and Dev/Assist. Is removed post, so it's just a first look , how it looks, will be enough changes, but one thing is certain, hes comming![]()
Thank you, I guess it should work, but for the time being it's better not to start flash tests again with the risk to screw everything up again.fastboot flash boot <filename>.img
using the same nightly lineage-14.1-20171020 official builds updated via phone, tested on two phones(both xperia z) with two "different" headsets/earplugs yet still no voice from neither sides, before updating one of the phones to the latest build(20171020) i tried to call on build 20171007 yet still no voice from me nor other phone that is xepria z also.Tested new nightly lineage-14.1-20171020 and audio with headphones works fine. I don't know what went wrong with previous nightly update: maybe I forgot to clean cache/dalvik after installation?
Kind regards
Aldo
Unfortunately I am just an user so I can't give you smart hints.using the same nightly lineage-14.1-20171020 official builds updated via phone, tested on two phones(both xperia z) with two "different" headsets/earplugs yet still no voice from neither sides, before updating one of the phones to the latest build(20171020) i tried to call on build 20171007 yet still no voice from me nor other phone that is xepria z also.
what do u guys suggest me to do to solve this?
i rly enjoy using headsets to hear the call & not removing it every call.
No it wasn't like that, why do you claim such things without knowledge. Please stop this, this creates unnecessary rumbling and delays work. It was the first successful build of a dev, who auto uploaded it to androidfilehost and someone found the link and made it public. The consequence is no more auto uploads (this means work)I know, it was 1st. release, like preview version. Have bugs, not for daily use for now, and Dev/Assist. Is removed post, so it's just a first look , how it looks, will be enough changes, but one thing is certain, hes comming![]()
It is not in a state where even semi public testing would help.can next update upload for testing rom ?
No it wasn't like that, why do you claim such things without knowledge. Please stop this, this creates unnecessary rumbling and delays work. It was the first successful build of a dev, who auto uploaded it to androidfilehost and someone found the link and made it public. The consequence is no more auto uploads (this means work).
I do not know what you want to say? Someone (developer) made a first rom, for testing. ok? and he published into base of android things... ok? for test, for people who are a testers? like me, or you... and i did, and send into wide area of internet, who dont know what is that, but i was write a description, first build or release, or just first look. "not for daily use". did you understand? u do not need to clear all your data for that, and again reverse into last rom. You can just watch and see what you will have when that version of new rom be upgraded into stable and for daily use. Look, I wanted to see something like that, when I could not do it. But now i can, and you do not need to wipe your data, just to see what new build of rom offers... Look at that on the brighter side, and if u think like that, go to General, and Oreo for Z, and read. for sure will be some uploads, maybe from different Developers, but it will be
The problem with that ROM is incorrect credits and we're not just giving out 15.0 (8.0.0) as it not usable as of yet. There are some standards we adhere too, if you want to test for development purpose let us know. But we also expect logs, and right now, people are just hungry for new update and rarely reply anything useful. I guess most of the Z users just want to flash a stable build and get on with their life. Let me tell you, this is a "DEV" thread. "DEV" thread where development takes place and things are broken. If you think other devices get faster builds, go check their "DEV" groups, and look at how people are providing logs and not posting crap.No it wasn't like that, why do you claim such things without knowledge. Please stop this, this creates unnecessary rumbling and delays work. It was the first successful build of a dev, who auto uploaded it to androidfilehost and someone found the link and made it public. The consequence is no more auto uploads (this means work).
I do not know what you want to say? Someone (developer) made a first rom, for testing. ok? and he published into base of android things... ok? for test, for people who are a testers? like me, or you... and i did, and send into wide area of internet, who dont know what is that, but i was write a description, first build or release, or just first look. "not for daily use". did you understand? u do not need to clear all your data for that, and again reverse into last rom. You can just watch and see what you will have when that version of new rom be upgraded into stable and for daily use. Look, I wanted to see something like that, when I could not do it. But now i can, and you do not need to wipe your data, just to see what new build of rom offers... Look at that on the brighter side, and if u think like that, go to General, and Oreo for Z, and read. for sure will be some uploads, maybe from different Developers, but it will be