For general information, I've just clean flashed the nightly from LineageOS site and... working fine till now.
Thanks again to @Daedroza and others who made this happen
Aldo
Thanks again to @Daedroza and others who made this happen
Aldo
[ROM][NIGHTLIES][7.1] LineageOS 14.1 for Xperia Z
- Thread starter Daedroza
- Start date
For general information, I've just clean flashed the nightly from LineageOS site and... working fine till now.
Thanks again to @Daedroza and others who made this happen
Aldo
What do you mean with "clean flashed"?
Having the latest unofficial (2017-08-27), which partition (if any) do I have to format prior to flashing the 2017-09-22 nightly? (ok I found the answer in another post of this thread: system, cache, dalvik cache, data)
Last edited:
Found an other bug
@Daedroza
It's me again... I'm not sure if you noticed but the screen Recorder app has a small bug.
How to reproduce it:
Open up Recorder as if you were trying to create a screencast .As always select "SCREEN" select your audio to be included in the screencast (or not) press the camera icon at the bottom of the app watch the small windows with a camera on the left side and and those up and down arrows on the right side appear.
It's all good until now. The problem appears when you actually CHANGE YOUR MIND and you decide you don't want to take the screencast for whatever reason.
The bug is , there's no way to close that window now...
The only way to make it disappear is to actually click on it take a screen cast and then quickly stop that screen record.
That is awkward, clunky and not elegant at all.
For some reason even turning on "Kill app back button" feature in the Developer options does not allow you to close that window.
Long pressing that button it will get you an "app killed" message but nothing happens.
Are there any other settings i might have missed ?
Anyways, is there anything we can do about it?
Cheers.
@Daedroza
It's me again... I'm not sure if you noticed but the screen Recorder app has a small bug.
How to reproduce it:
Open up Recorder as if you were trying to create a screencast .As always select "SCREEN" select your audio to be included in the screencast (or not) press the camera icon at the bottom of the app watch the small windows with a camera on the left side and and those up and down arrows on the right side appear.
It's all good until now. The problem appears when you actually CHANGE YOUR MIND and you decide you don't want to take the screencast for whatever reason.
The bug is , there's no way to close that window now...
The only way to make it disappear is to actually click on it take a screen cast and then quickly stop that screen record.
That is awkward, clunky and not elegant at all.
For some reason even turning on "Kill app back button" feature in the Developer options does not allow you to close that window.
Long pressing that button it will get you an "app killed" message but nothing happens.
Are there any other settings i might have missed ?
Anyways, is there anything we can do about it?
Cheers.
You are missing the point here.
As I said, the window can be closed once you click on it and start recording. Stop the screencast after one sec and voila, you got rid of that tiny window.
The point is, other than that there's no other way to interact with that window and close it if you feel like.
There should be no need to restart the UI nor to roll the eyes...
We're reporting bugs..
As beta testers that's what we're supposed to do.
Provide feedback in exchange of getting to play with a cutting age ROM.We get support for our old ,decrepit antique devices and the DEV gets his feedback which will enable him to get better and better.
A lot of people seem to forget that.
As I said, the window can be closed once you click on it and start recording. Stop the screencast after one sec and voila, you got rid of that tiny window.
The point is, other than that there's no other way to interact with that window and close it if you feel like.
There should be no need to restart the UI nor to roll the eyes...
We're reporting bugs..
As beta testers that's what we're supposed to do.
Provide feedback in exchange of getting to play with a cutting age ROM.We get support for our old ,decrepit antique devices and the DEV gets his feedback which will enable him to get better and better.
A lot of people seem to forget that.
tried restarting system ui yet???
You could flash the [MOD][4.4+] Sony Apps Enabler.
Or use the Sony Apps Enabler Magisk Modul which is available in the official Magisk Module repo.
Last edited:
Try to flash boot.img of the los zip file with fastboot from your pc. I had the same issue with boot.img from rr.
Some additional info about the fc in setup wizard. After a clean flash on my SGS4, unofficial build from 25/09/2017, the same happens, after the "SIM is missing" message setup wizard crashes. Like in our Z this only happens when the ROM and GApps have been flashed together. Seems to be a general LOS bug.
Thanks for everyone trying to help me with being stuck on LOS without working recovery..
I found out that, after successful flasing LOS (even the latest nightly build worked without trouble after full wipe), trying to install TWRP 3.0.2 via TWRP app or Terminal Emulator ends up with no success whatsoever. However, version 2.8.7 works and is finally flashed to FOTA partition.
Finally, flashing Magisk through this TWRP ends succesfully (and in-built flash management gets disabled in Developer options). Everything would be great, if... Titanium Backup didn't FC immediately after launch. Tried different versions (one from GP/one old apk on my sd card), tried updating busybox, installing/removing Magisk.
So I restored my RR and running fine right now, however if anyone could try to make Titanium work and responded here I'd be really glad. Looking forward to try LOS again
I found out that, after successful flasing LOS (even the latest nightly build worked without trouble after full wipe), trying to install TWRP 3.0.2 via TWRP app or Terminal Emulator ends up with no success whatsoever. However, version 2.8.7 works and is finally flashed to FOTA partition.
Finally, flashing Magisk through this TWRP ends succesfully (and in-built flash management gets disabled in Developer options). Everything would be great, if... Titanium Backup didn't FC immediately after launch. Tried different versions (one from GP/one old apk on my sd card), tried updating busybox, installing/removing Magisk.
So I restored my RR and running fine right now, however if anyone could try to make Titanium work and responded here I'd be really glad. Looking forward to try LOS again
I have the Titanium Backup fc issue on the latest nightly on the Oneplus 2. I cant find any posts about this. Any ideas?if anyone could try to make Titanium work and responded here I'd be really glad. Looking forward to try LOS again
Boy you are in wrong Device Forum. Go and ask this question in oneplus 2 forums at xda, you may get help there
Tested Here Maps right now on my terminal, works well. Can't guess what is going wrong in your case, sorry.
Many thanks to developers and contributors of this Sony yuga LOS project.
As official nightly has now been released, I'm wondering that does Firmware Over-The-Air (FOTA) now work? So far I have not been able to upgrade previous development branch version by using LineageOS own functionality (settings --> about phone --> system updates). Can someone confirm that functionality is now working, even by saying that system updates informs (if you have latest version) that no new updates exists? On previous development versions my phone has constantly been saying that it cannot connect to update server and therefore saying that last check was made in 1.1.1970 (when Unix time started); so FOTA was not working at least in my phone.
As official nightly has now been released, I'm wondering that does Firmware Over-The-Air (FOTA) now work? So far I have not been able to upgrade previous development branch version by using LineageOS own functionality (settings --> about phone --> system updates). Can someone confirm that functionality is now working, even by saying that system updates informs (if you have latest version) that no new updates exists? On previous development versions my phone has constantly been saying that it cannot connect to update server and therefore saying that last check was made in 1.1.1970 (when Unix time started); so FOTA was not working at least in my phone.
I don't think this is a device specific issue.
Here is what worked for me:So I restored my RR and running fine right now, however if anyone could try to make Titanium work and responded here I'd be really glad. Looking forward to try LOS again
-Uninstall titanium backup
-Use any root explorer to go to data>data>com.keramidas.TitaniumBackup and delete the folder.
-Reinstall.
I hope I could help. Let me know.
Last edited:
Extra reason for not posting here ("Xperia Z Original Android Development"): either choose Lineage or App & games section
Last edited:
You are actually right.
I just wanted to pick up on @Killer007TV asking how to get Titanium Backup to work.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
32Code:
#include <std_disclaimer.h> /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
Downloads Links
LineageOS 14.x (Unlocked Bootloader) :
Nightlies : https://download.lineageos.org/yuga
Google Applications (optional) :
OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 7.x, Micro or Pico)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Informations and references :
About LineageOS updates : ChangeLog available on http://www.cmxlog.com/14.1/yuga/
About LineageOS device side : See my GitHub trees linked below
Flashing and updating
LineageOS clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Wipe the data & cache (Backup to make sure not to loose data)
- Flash the LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS update / upgrade :
- (Information) Don't wipe anything unless you want to
- (CM / UNOFFICIAL) Nothing to wipe when switching
- (FUTURE RELEASES) Might need clean, informations will be updated
- Flash the latest LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS addonsu for root access :
- (Information) Read the Root section of the Q&A thread
- (Download) Download the addonsu for arm : LineageOS Downloads / Extras
- (Optional) Flash the zip on a working Lineage installation (once)
- (Information) Upon ROM updates, the addonsu is preserved
- Reboot
About the builds
Device tree : https://github.com/fusion3-common/android_device_sony_Yuga/commits/cm-14.1
Kernel sources : https://github.com/fusion3-common/android_kernel_sony_apq8064/commits/cm-14.1
Vendor blobs : https://github.com/fusion3-common/proprietary_vendor_sony/commits/cm-14.1
Issues and reports
- Report issues only if you are using the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example
About LineageOS Legal : http://lineageos.org/legal/
The LineageOS team would like to thank everyone involved
in helping with testing, coding, debugging & documenting! Enjoy!
[/INDENT]
LineageOS available for Yuga also thanks to :
- The LineageOS Team
- The CyanogenMod Team
- Everyone involved in working and testing
XDA:DevDB Information
[ROM][NIGHTLIES][7.1] LineageOS 14.1 for Xperia Z, ROM for the Sony Xperia Z
Contributors
Daedroza, AdrianDC, Chippa_a, Olivier, Namelos, CyberwalkmaN, sigprof
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2017-07-16
Last Updated 2017-11-1027We've successfully pushed to Nightlies.
Since all the builds are done alphabetically with other phones, the first nightly would be in following sequence:
dogo -> odin -> pollux -> pollux_windy -> yuga
Each of the devices download page should be created and popped with a new build as soon as it's completed and uploaded (till 24th of this month).
Notice: The builds that are provided by me are unsigned debug enabled builds. Meaning the /data stack is incompatible with signed builds (provided by LineageOS build bot). Switching over to nightlies would require full clean flash. Also, since signed builds have no debug facilities ON by default, so there shouldn't be any SU addon pre-installed. You need to manually flash that if you plan to use root for your device.
Also, my Fusion3 device broke a few days ago. It's the power controller that has successfully burned out. I've been trying to repair it since few days, but all my attempts are in vain. Today, I will go to a professional to deal with the hardware issue. If someone has an extra Fusion3 device lying around, please let me know. Thanks, and Cheers.
Special thanks to:
- @Chippa_a
- @CyberWalkMaN (This guy is a genius and deserves a beer and all efforts were taken by him is the reason we are here, thanks a lot.)
- @sigprof (For tedious debugging and fixes that I couldn't figure out)
- @namenlos
- @AdrianDC (Legend)
- @CAHbKA (For pollux / pollux_windy bringup)
- @MardonHH (For all the testing)
- @alex-gibson
- @Røbin (For all the testing)
- @tejas_kesaria (For testing)
- @ldx63 (Helping and testing in-call audio with headphones)
- @C0rn3j (Early testing)
- and those were all involved.
Sorry if I'm forgetting someone. If my device doesn't get fixed, I'm happy to say I had the best time with everybody.22Reserved
FEATURES AND ISSUES
Code:- Boot : Ok - GApps : OpenGApps Micro Ok - FOTA Recovery : Ok (see below) - WiFi : Ok (real SONY MAC address) - Bluetooth : Ok (real SONY MAC address) - WiFi Hotspot : Ok (2.4GHz and 5GHz) - RIL - Phone - Data : Ok - GPS : Ok - Camera : Ok - Camcorder : Ok - Lights : Ok - MicroSD : Ok - Accelerometer : Ok - Compass : Ok - Gyroscope : Ok - AOSP sensors : Ok - FM Radio : Ok - Vibrator : Ok - Microphone : Ok - Audio & external audio : Ok - Bluetooth audio : Ok - NFC : Ok - Kernel : Ok, Updating frequently - Graphics : Ok - 3D Rendering : Ok - Clock : Ok - Offline Charging : Ok - SEPolicies : Fully enforced17New build is up folks.
- Security patches till July 2017.
- Clean build, inclusive of all changes by LineageOS till yesterday.
- Includes DRM libraries, so please test @raShMan777
- All other standard bugfixes from cm-13.0 thread, all of them. YES, all of them.
- Attempt to fix a problem as told here (https://xdaforums.com/showpost.php?p=73250499&postcount=16)
Folks, this has been a year long journey for me, let's face it, I am learner, so I need your feedback here. Even a smallest problem (like force closes) will seen as long as you provide logs. Regarding stability, we're not pushing devices that reboot or mess up after some time. A lot of people are involved in completing this and I would like to thank all of them. And good feedbacks are welcome too, if it works for you14No 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.
If you feel you're capable of testing i.e providing logs and not just waste our time for next ETA for 15.0 then please PM or just wait like other people for a build.
Constructive and useful criticism are much appreciated in DEV threads, as said, "DEV" threads.
Still, if you guys think you want build (personal use and personal sharing, no posting), please build the ROM yourself, all of our sources are public. And please post the proper credits, that includes @Chippa_a and @CyberWalkMaN (they've done the most work for 15.0) and not "YOU" if you ever plan.
Thanks. We still want knowledgeable testers for 14.1, we're polishing it and help is always appreciated.
