yashsingh1/xdaforums huggingface dataset:
[Xperia Z Original Android Development] ISPG:
Hi maftul:

About your comment of GPS. I agree with you. I also have some problems with GPS in this phone. Mainly with the new ROMs. Originally I don't remember any problem with it, and the connection

was instantly. But it is only with some apps. For example, I normally use Jogtracker for measuring my walkings and runnings, and with this app happens what you comment. A very long time to

obtain a good accuracy, even with many satellites. But once obtained the GPS is stable and doesn't lose the signal. But with other apps, for example Maps or Go (Tomtom), the GPS is fast, almost

instantly. So, I know that a device with more six years (mine is from 2013 February) is not the same that current devices, but is enough for me, on spite of these minor troubles. In the other hand, is

very amazing to have a phone that operates and is totally functional with these ROM. Almost a vintage phone ... :) Heating and drain battery are for me the main problems actually.

Regards,
[Xperia Z Original Android Development] samhhmobil:
Yes, that's it.

It seems to me, that using a microSD card (64GB SDXC SanDisk extreme pro) as "adoptable storage" drains the battery MUCH faster and overheats the CPU, as when I'm using it without SDcard.

But I cannot proof that really. Can someone second that?

samhhmobil

PS

Due to the fact, that I need more storage as only 16GB, this nice device is useless to me without adoptable storage... sigh...
[Xperia Z Original Android Development] truefriendcz:
CrDroid i am a not recommended. It is highly buggy. 14.1 builds and 15.x and 16.x not changing screen brightness. Build 14.x and 15.x randomly reboots and randomly stopped/stayed on bootlogo with neverending time.
[Xperia Z Original Android Development] S.N.A.P:
try Mokee Oreo then
[Xperia Z Original Android Development] ProtonCar:
Hello everyone,

I was also able to reproduce the GPS Problem. It seems the device sometimes finds GPS - but looses the connection right away. My device was not able to show me my current position on a map or the current speed. Nevertheless the prediction when the destination will be arrived was correct when navigation was restarted.
[Xperia Z Original Android Development] Zerikwan:
I can't enter TWRP on the latest official. It boot to LOS recovery instead. Anyone know how to enter TWRP?
[Xperia Z Original Android Development] S.N.A.P:
try install latest TWRP using dd install method

then reboot, wait for the SONY logo and then the LED, after that spamming vol up and vol down button

I used to do that way and it worked
[Xperia Z Original Android Development] Zerikwan:
Done, but doesn't work. Either vol up or vol down, always entered LOS recovery.
[Xperia Z Original Android Development] Flounderist:
Try installing latest twrp using official twrp app. Then restart device and push on vol+ right after the pink/purple LED blink on restart.

You should get a gold/yellow LED blinking and then you should access to recovery.
[Xperia Z Original Android Development] holywar:
while the phone is OFF, press the power button ON, wait until it vibrates then immediately release it, sony logo will appear and also the led light then immediately click the volume up key 2-3 times (DONT press and hold the the volume up key) the phone will vibrate again and the TWRP will show up,
[Xperia Z Original Android Development] Zerikwan:
[MENTION=7193743]Flounderist[/MENTION]

[MENTION=5326040]holywar[/MENTION]

Guys, I know how to enter the recovery.

The thing is, with the latest build (20190430) somehow it always entering LOS recovery, not TWRP. Either with vol up or vol down.

I've tried the 3.2.3-0 and 3.3.0-0 version, with official TWRP app and dd install method. None of them work.

This problem never occured with the previous build (20190423).
[Xperia Z Original Android Development] holywar:
[MENTION=7465143]Zerikwan[/MENTION]

thank you, im using 20190430 build and 3.2.1-0 TWRP (dd install method) volume up works to me (for TWRP recovery), and volume down for LOS recovery,
[Xperia Z Original Android Development] Flounderist:
I am sorry but I can't provide any feedback here, my device is running Pie build.
[Xperia Z Original Android Development] Zerikwan:
Don't worry, man. I found the culprit. It's because of magisk 19.1. Thanks for reply.

And thanks to you [MENTION=5326040]holywar[/MENTION]

Your feedback helped me a lot.
[Xperia Z Original Android Development] Flounderist:
Latest magisk stable (19.1) updated flawlessly on my device running LOS 16.

Let me check if twrp broke :cowboy:

Well: TWRP is broken also for me. [MENTION=7465143]Zerikwan[/MENTION] did you sorted uninstalling latest Magisk?
[Xperia Z Original Android Development] Zerikwan:
I didn't. I just wipe everything, start it over, and flash magisk 18.1.
[Xperia Z Original Android Development] Flounderist:
Using Los recovery? :mad:

Edit: I uninstalled magisk from manager apk and restarted device. So I was able to access to twrp again and I restored a backup.

Now I am on 18.1
[Xperia Z Original Android Development] Zerikwan:
No, using TWRP. I flash TWRP on boot partitionusing TWRP app, then flash the TWRP again on FOTA partition using TWRP.
[Xperia Z Original Android Development] Flounderist:
OK. I mean uninstalling magisk and restoring a backup is more straight away process, luckily.

By the way, magisk 19 should break the way the device reboots to recovery, not the recovery itself.

I will try for some support in magisk main thread.
[Xperia Z Original Android Development] ISPG:
Hi:

Since I installed Nightly I also downloaded Lineage Downloader, it is better that the updater included in the version, and you can

check if any new version has been released. You can also download from this app the last nightly, whole zip or only the new changes.

And after downloading, the app offers you the option to flash inmediately the ROM, in that case, the app reboots directly in TWRP.

As comment about the TWRP troubles.
[Xperia Z Original Android Development] Zerikwan:
Yeah, I know. But I don't have a backup at that time. And I forgot about uninstaller.

So, we just stick to magisk 18.1, right? Thanks man.
[Xperia Z Original Android Development] Flounderist:
So far...just ignore the update nag.
[Xperia Z Original Android Development] Zerikwan:
Magisk 19.2 also broke the recovery on the latest version.

I read about this problem too on the Z3 carbon thread, but the dev already fixed the problem by now. Could you guys investigate it please, [MENTION=5906831]Daedroza[/MENTION] [MENTION=5405613]CyberWalkMaN[/MENTION] ?
[Xperia Z Original Android Development] TwinkieMurf:
Hi! I'm using lineage os with microg, is it possible to upgrade to the latest build of this rom without losing microg support? or do I have to wait until the support for that lineage version is updated?
[Xperia Z Original Android Development] ISPG:
[MENTION=7465143]Zerikwan[/MENTION]

Just it happened to me. Magisk v19.X broke my recovery and device. I had to install the only version that the phone allowed.

Android 5.1.1 (10.7.A.0.222), but I'm not able to access to any recovery. CMW or TWRP. I have rooted with Kingroot and apparently

my bootloader is unlock (in device indicates YES in configuration). I have tried with different apps for installing any recovery in

order to install my previous nightlies, but it is impossible. I suspect that the boot partition is bad in any way, but I don't know how

to repair or reinstall it.

Any way in these forums has helped me about to install a recovery.

In the other hand, with this old version 5.1.1, I have checked that certains troubles in 8.1 aren't present. For example, Wi-Fi in 5 GHz

works good, and the connection with GPS is instant.
[Xperia Z Original Android Development] samhhmobil:
At first... actual stock rom is 10.7.A.0.228, but that's not really important. And yes... in stock rom you'll not find any recovery.

For installing LOS again, the easiest way is to flash TWRP in the boot(!) partition at first! Then the phone will boot into recovery only.

C:\adb> fastboot flash boot twrp.img

When in TWRP, you can access the data partition of your phone via your PC, and you can copy the LOS zip into the root directory of that data partition (and OpenGapps and Magisk 18.1(!) zip files). Now you can install LOS (and OpenGapps and Magisk) in TWRP. After that install, the boot partition is overwritten by the LOS-boot-image and TWRP-recovery is away again (it's just only LOS-recovery there). But now you can boot into LOS, and in any command-line-shell you can "su", and you can with "dd" install twrp.img into the FOTAKernel-partition, and that's it.

Much luck,

samhhmobil
[Xperia Z Original Android Development] Flounderist:
You should have just go to Magisk manager, tap uninstall and then reboot in recovery to restore a backup.
[Xperia Z Original Android Development] kapibara:
This thing caught me off guard as a long time passed between flashing Magisk v19* and attempting to update LOS.

Easy downgrade steps if anyone's struggling:

Open Magisk Manager

Choose Uninstall → Restore Images

adb reboot recovery

In TWRP, go to Advanced and then ADB Sideload

Download Magisk v18.1

Download the uninstaller for your currently installed Magisk version (v19, v19.1, v19.2)

adb sideload Magisk-uninstaller-*.zip

adb sideload Magisk-v18.1.zip

adb reboot

Download the latest Magisk Manager

adb install MagiskManager-v7.2.0.apk

Optionally disable notications from Magisk Manager for now if you don't want to be nagged. Hopefully this'll be fixed soon-ish though.

Edit: Forgot to include Magisk uninstaller.
[Xperia Z Original Android Development] Flounderist:
In order to fix the Magisk issue, rom dev should merge this commit:

https://github.com/CarbonROM/androi...mmit/3a7de02a325a2e499d7d47bc91d670e3b3e88ccf

[MENTION=5405613]CyberWalkMaN[/MENTION]
[Xperia Z Original Android Development] ISPG:
[MENTION=8300892]samhhmobil[/MENTION]

Thanks for your help but unfortunately, I haven't been able to update to LOS.

The problem is that I can't install TWRP in boot. I have tried from the apk, marking to boot partition, but it fails.

And in fastboot from the PC, is impossible to connect with the phone. It always says "waiting for device", the phone correctly connected

with blue LED, but also with the typical message in Control Panel, Other devices, yellow triangle in device SD1 Boot Fastboot.

Sure that is due to a trouble with boot partition, because with other phones, the connection is good, with ADB drivers installed.

In ADB mode, the phone is detected perfectly, but in Fastboot not ... :( So, without TWRP, I´m not able to install the other files.

[MENTION=7193743]Flounderist[/MENTION]

Hi Cork ... ;) It was the first thing that I did. To run the uninstalling of Magisk, and it was what broke the recovery and device. After rebooting

... nothing. Thanks for your comment.

[MENTION=2360363]kapibara[/MENTION]

I have tried with your indication, but unfortunately, as you can read, the problem is to install any recovery in the boot, without fastboot mode.

With some apks, Flashify, Xperia recovery, etc. apparently is possible to format Boot partition or FOTAKernel, but after that, everything is the same.

Thanks also in any case.
[Xperia Z Original Android Development] samhhmobil:
[MENTION=8045130]ISPG[/MENTION]

Is your bootloader correctly unlocked?

What's (with blue led on) the result of

"fastboot devices"?

Are you running "fastboot" on your PC with administrator privileges? (It's a must!)

samhhmobil
[Xperia Z Original Android Development] Flounderist:
Magisk Is messing twrp because It Is located in FOTAKernel partition. When I discovered this issue I tapped on uninstall in manager app and then reboot to recovery using button combo. No weird behaviours and so on.
[Xperia Z Original Android Development] ISPG:
[MENTION=8300892]samhhmobil[/MENTION]

Is your bootloader correctly unlocked?

I think that it is. I enter in configuration menu, I can see

Rooting status:

Bootloader unlocked: Yes

What's (with blue led on) the result of "fastboot devices"?

Nothing, simply a return. In fastboot mode, the phone isn't detected.

Are you running "fastboot" on your PC with administrator privileges? (It's a must!)

Yes, of course.

Even, I found a tool called Sony Bootloader Unlock, that in theory performs the whole process for you,

even retrieving the unlock code from Sony, but when reboot the phone, this shows the blue LED, and

the process remains so for ever.

So, impossible to access to bootloader or install a new recovery. I don't know if with a factory reset, the bootloader

went lock again, and CWM recovery. Thanks anyway

samhhmobil[/QUOTE]
[Xperia Z Original Android Development] maftul:
In the end I ended up reverting back to the last version of LineageOS 14.1 which was released for this phone and all my phone's sensors are working correctly now and I can get a GPS fix in a few seconds. I guess I will stick with 14.1 until I buy a new phone.
[Xperia Z Original Android Development] ISPG:
Hi guys

Finally I got to install TWRP in boot partition afterwards I don't remember how many attempts.

With that I recovered a backup and to install again LOS 15.1. The problem was that in that backup was still Magisk

with 19100, and although I flashed 18100 and Magisk Manager 7.0.0, the app showed that Magisk wasn't installed, and

indeed the device wasn't rooted.

I decided to cross my fingers and install 19300 (apparently Magisk had solved the problems with bootloader and loops)

and Magisk Manager 7.2.0, and it worked !!!

So, I have again the phone with root and last Nightlies. Thanks to both for your comments.
[Xperia Z Original Android Development] samhhmobil:
So you got back a running system, but nevertheless you cannot access TWRP-recovery located in FOTAKernel partition now again.

samhhmobil
[Xperia Z Original Android Development] ISPG:
Exactly [MENTION=1761081]samhh[/MENTION]movil, I checked it after your comment. Because after recover the backup, I installed TWRP successfully,

but now it is as you indicate. I suspect that this has happened after install Magisk again.

But the thing is that TWRP is correctly installed, I can flash succesully the .img file to recovery, but after in reboot recovery the

screen is dark, and is necessary to reboot again in system. This looks as neverending story :(

How could I install next Nightly?
[Xperia Z Original Android Development] samhhmobil:
You just only can downgrade to Magisk 18.1 at this time.

1.Just install TWRP in boot partition again.

2.Install the boot-image (without Magisk) there, or install the complete LOS (without Magisk-patched boot image) there.

3.Install magisk-18.1.zip after that.

... or restore a previous saved boot image patched with Magisk 18.1.

Until the system patch — published a few pages before in this thread — isn't included in LOS (and I don't expect, that any dev will do that for LOS 15.1 — they're working on 16) a newer magisk of 19.x seems not to be useable.

samhhmobil
[Xperia Z Original Android Development] ISPG:
Ok and thanks [MENTION=8300892]samhhmobil[/MENTION]. I had imagined something similar that you indicate.

I will save your information until the moment of updating the version.

I am also following the threads about Android 9 for this device in case that finally some of

them is stable and with full functionality.
[Xperia Z Original Android Development] 0LDST4R:
[MENTION=5906831]Daedroza[/MENTION]

Could you define which lines in the build.prop are for the Audio config?

I think these are the lines i'm looking for, right?

audio.offload.disable=1

media.aac_51_output_enabled=true

persist.audio.fluence.voicecall=true

persist.audio.fluence.voicerec=false

persist.audio.fluence.speaker=true

qcom.hw.aac.encoder=true

ro.config.media_vol_steps=25

ro.config.vc_call_vol_steps=7

ro.qc.sdk.audio.fluencetype=fluence

Thanks for supporting this old but wonderful device.

:good:
[Xperia Z Original Android Development] Mc_Claude:
Hello,

i have flashed " lineage-15.1-20190716-nightly-yuga-signed " with twrp-3.3.1-0-yuga recovery.

Now lineage OS dont start. Only the Start-Animation apears. ----o / ---o- / --o-- / -o--- / o----

I did it like the wiki at lineageos . org

What I do wrong?
[Xperia Z Original Android Development] 0LDST4R:
Try twrp 3.2.1.0 , i had similar problems too with 3.3.1.0...
[Xperia Z Original Android Development] Mc_Claude:
thx, it works!
[Xperia Z Original Android Development] Admiral AnimE:
Hello. I have the latest official version installed. I updated from unofficial a few weeks a go. No problems at all until suddenly a few hours ago something happened.

- The phone does not ring when receiving calls.

- I also tried to play music, it does not do anything.

- Changing the volume from the keys works, but no sound comes out.

- Changing the volume from inside the settings freezes the settings.

- Opening the stock camera or Opencamera only opens a black screen.

- When trying to play a recorded call, the application freezes.

- I also tried Phone check. First, it did not tell me any information about the phone. Next, when trying the microphone test, it said there is a problem. When trying the speaker test, nothing happened. Then after the screen test the application froze.

I have restarted the phone, but it did not help. How can I confirm what is wrong? Lineage or hardware?

Edit:

I tried to call. When dialing, the digits have sound, so the speaker is working. When in call, I can't hear anything and the other side can't hear anything. The phone does not ring. :/

Well... I uninstalled the call recorder and restarted. Now everything works. Not sure how that happened, because it was working before.
[Xperia Z Original Android Development] TrueFriend-cz:
Autor, do you planing build based you ROM to Android 9 or 10?
[Xperia Z Original Android Development] D34TH4K4:
Hello,

i have same problem.Flashed "lineage-15.1-20191010-nightly-yuga-signed.zip

sha256" with twrp-3.2.1-0-yuga recovery.

"Now lineage OS dont start. Only the Start-Animation apears. ----o / ---o- / --o-- / -o--- / o---- and reboot"

What I do wrong?
[Xperia Z Original Android Development] MAHDI.TX:
Hi, how should I update my device from " lineage-15.1-2018-01-06 " to " lineage-15.1-2019-10-24-nightly " ?

I did flash the new version with recovery but after boot phone just showing "shut down" and rebooting the phone.
[Xperia Z Original Android Development] samhhmobil:
Did you clean Cache and Dalvik in TWRP?

For me, the latest Nightly runs without any issue.

(The one and only important issue is the overheating while running CPU-intensive apps, but this "issue" exists in all builds.)

I'm updating it frequently, week by week, I never have had any trouble while booting.

samhhmobil
[Xperia Z Original Android Development] MAHDI.TX:
Thanks, no I didn't clean Cache and Dalvik

I don't want to lose my apps and settings

Do I need to install G-apps again after update ?
[Xperia Z Original Android Development] samhhmobil:
With cleaning Cache/Dalvik you will NOT loose anything, neither apps nor settings.

You don't need to reinstall Gapps, it should work as it is.

samhhmobil
[Xperia Z Original Android Development] Killer007TV:
Hello man, may I ask you, I have TWRP 2.8.7 flashed into FOTA partition (previously I had had troubles with switching between LOS and RR so this was the solution), is it gonna be ok?
[Xperia Z Original Android Development] Flounderist:
I made an idle test to check system drain.

I charged battery to 100% and I calibrated stats with an app. Then I left it in airplane mode for 12 hours.

Device lost only 2% :cowboy:

I replaced naptime with greenify magisk module to get rid of background running apk notification.

I will test idle drain with network on later on.
[Xperia Z Original Android Development] kebgo23:
more stable

hi guys which is more stable version planning to flash this one to my C6603 LP version from the philippines.

Thanks !
[Xperia Z Original Android Development] Flounderist:
Latest build is OK.

Update your twrp to 3.2.1 before flashing.
[Xperia Z Original Android Development] kebgo23:
how to update do you have the link of it? do you have screenshots of the LOS15?
[Xperia Z Original Android Development] Flounderist:
Just read the first post for ROM download.

For twrp, link is a few post before.

If lazy, just google "twrp 3.2.1 yuga" and you're done. :silly:
[Xperia Z Original Android Development] kebgo23:
how do you change ur twrp ?

---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------

after flashing 3.2.1 im getting bootlop on sony logo

---------- Post added at 05:42 PM ---------- Previous post was at 05:37 PM ----------

bootloop after flashing twrp 3.2.1 from twrp 3.0.2
[Xperia Z Original Android Development] raeed_sal:
Does it work on c6602 xperia z؟؟؟
[Xperia Z Original Android Development] ldx63:
Very happy for LOS 15 development on XZ, thanks [MENTION=5906831]Daedroza[/MENTION]!

For the time being I have no spare devices to replace my XZ to test this build, hopefully in a few days...
[Xperia Z Original Android Development] Flounderist:
When in twrp 3.0.2 go to "install" and flash the zip.

Once flashed go back (don't reboot) to twrp home screen and tap on "reboot"

In reboot menu, tap on reboot recovery.

If in trouble, unpack twrp.img and flash twrp 3.2.1 in FOTAKernel using terminal. you must be rooted.

Rename file as "twrp" only and place in the root of your device storage (not in download or any other folder), then give the command:

su

dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel

reboot recovery
[Xperia Z Original Android Development] ngatia:
yes it does and its stable for daily use.
[Xperia Z Original Android Development] kebgo23:
Thanks sir i will try it
[Xperia Z Original Android Development] kebgo23:
Is it should be in the internal storage or sd card? I try the fota but after it success i boot to recovery still boot loop witj loght blue led light
[Xperia Z Original Android Development] kebgo23:
Itry fota kernel, i put twrp.img to root of my sd card after fota and success. I reboot to recovery usimg app and i cant enter twrp boot loop sony logo with blue led light
[Xperia Z Original Android Development] Flounderist:
I actually don't know how to help further

When flashing 3.2.1 from terminal, do you have any output? If you give command reboot recovery from terminal what happen? Could you try to press volume+ during blue led on?

Last resort, try flashing Oreo ROM using 3.0.2
[Xperia Z Original Android Development] kebgo23:
Nothing happens when itry to reboot to recovry. Is 3.0.2 compatible for oreo roms?
[Xperia Z Original Android Development] Daedroza:
Latest build: 20180106

- Staging Branch (Lineage 15.1) / Android 8.1.0

- Oreo Tiles / Oreo Lock Screen Art / Oreo Visualizer (Under Development, might work incorrectly)

- January 2018 Security Patch (Device specific patches are still remaining as of yet).

- Many other device specific improvements (Brought by Chippa_a / CyberWalkMaN, please look at device trees)

- Removed accidental security patch that brought NULL pointer dereference (surprised no body encountered it yet).

The overall experience is smoother when all the optimizations settles-in.

I won't be building for sometime (until something important drops in like new security patch or something worthwhile to bring in feature).