[ROM][7.X.X]LineageOS [Suzuran]

Status
Not open for further replies.
Search This thread
Oct 13, 2015
16
1
I had exactly the same problem. With the installation of Los I started to have the first camera issues. Firstly, it was just bad quality, then green stripes, then drop outs, now nothing at all.
In the process, i had done a complete revert to stock just for clarity. Nothing changed. The camera was gone for good...
I did some reading and it appears the back cameras of the earlier days have issues and are to be exchanged in case of any problems, no questions asked.
However, it also occurred to me that the constant flashing of different (beta) ROMs had its role in this play. Maybe some bad driver was just giving the camera too much juice for a while?

Anyway, once i return from my travels, i will have to get a replacement camera. Good thing is, they're pretty cheap and tutorials how to do it are easy enough to follow.

Gah, okay...I don't want to have to open it up because I'm sure it won't be waterproof after that, but if that's the only fix then I will
 

torben5247

Senior Member
Apr 13, 2013
366
64
I have been running los on z5 compact earlier.
I am currently on stock, but i would like to try the new versions.
But after initial boot up the lineage os freezes.
This is what i have done:
flashing stock .154 using flashtool.
Installed twrp using adb fastboot commands.
Boot into twrp, wiped data,system, dalvik/cahce, cache.
Installed 20180304 and open gapps pico.
The phone boots fine, but freezes after 30 second.
Any help would be much appreciated

edit: i just tried without flashing gapps, phone freezes and the screen goes black, only the status bar is visible.

Edit: problem is gone when i remove my sd card. somehow my sd card is corrupt...
 
Last edited:
Oct 13, 2015
16
1
Calling troubles with LineageOS

Hello,

Running the LineageOS with MicroG build.

Aside from rear camera death, I've noticed a few problems:

  • Calls take 2-3 tries to actually go through
  • I can't receive calls at all--they all go to voicemail
  • The phone doesn't seem to be provisioned for VoLTE even though it has the capability; nothing in the settings menu, *#*#4636#*#* shows not provisioned / greyed out, reprovisioning does nothing

Any of you smart people out there have a thought as to what could be causing this?
 

trax7

Senior Member
May 15, 2012
944
345
Hello,

Running the LineageOS with MicroG build.

Aside from rear camera death, I've noticed a few problems:

Calls take 2-3 tries to actually go through
I can't receive calls at all--they all go to voicemail
The phone doesn't seem to be provisioned for VoLTE even though it has the capability; nothing in the settings menu, *#*#4636#*#* shows not provisioned / greyed out, reprovisioning does nothing


Any of you smart people out there have a thought as to what could be causing this?
MicroG is hackery in and of itself so I'd suggest a full wipe and testing without MicroG and with(out) GApps. If the issue persists it's a LOS issue (very unlikely), if not then it's almost sure to be from MicroG. In that case you can also write in the MicroG thread for double chance of answers.

I've had some experience with it and from what I can see - it works - but only sometimes... It can break for no reason. Hence why I just use the pico package GApps. It's very difficult to have a full-featured Google-less device.

Of course, you could always take logs and try to see what happens there and prob post them here.
 
Oct 13, 2015
16
1
MicroG is hackery in and of itself so I'd suggest a full wipe and testing without MicroG and with(out) GApps. If the issue persists it's a LOS issue (very unlikely), if not then it's almost sure to be from MicroG. In that case you can also write in the MicroG thread for double chance of answers.

I've had some experience with it and from what I can see - it works - but only sometimes... It can break for no reason. Hence why I just use the pico package GApps. It's very difficult to have a full-featured Google-less device.

Of course, you could always take logs and try to see what happens there and prob post them here.

Thanks! Yeah, it's all hackery at some level---not like we're getting thorough code reviews. I'm not sure how MicroG would be breaking something that doesn't have to do with google services, but I guess it's possible. I will post in the MicroG thread.

My own version has VoLTE...
Thanks for letting me know @Berni-0815 !

My phone is currently encrypted, and TWRP on Suzuran doesn't (yet) support encryption so I can't wipe the relevant caches and stuff. I've been dirty-flashing (without dalvik or cache wipes too!) new builds of LineageOS w/ MicroG and that has been (seemingly) working fine. Berni--what do you think my chances are making a move to your build w/Pico or similar? Must do a full wipe?

Thanks again!
 

Berni-0815

Senior Member
Sep 22, 2016
2,517
2,212
Germany
Sony Xperia Z5 Compact
Berni--what do you think my chances are making a move to your build w/Pico or similar? Must do a full wipe?
There is no "must". Sometimes it works, sometimes not. Even when dirty updating my version sometimes a clean install is the only way that works... (Happens to me twice)
I don't know what will happen if you dirty flash my version over your existing and encrypted system.
 

trax7

Senior Member
May 15, 2012
944
345
.
My phone is currently encrypted, and TWRP on Suzuran doesn't (yet) support encryption so I can't wipe the relevant caches and stuff. I've been dirty-flashing (without dalvik or cache wipes too!) new builds of LineageOS w/ MicroG and that has been (seemingly) working fine.

There is no "must". Sometimes it works, sometimes not. Even when dirty updating my version sometimes a clean install is the only way that works... (Happens to me twice)
I don't know what will happen if you dirty flash my version over your existing and encrypted system.

There's two things here - the dirty flashing and encryption. Berni is right, clean flash is the surest way to have a (mostly) bugless installation. If you dirty flash you accept that some issues may/will arise that can't be "repaired" per se without a clean install.

There other thing is, well, encryption support has been a b****h for this device until now. It forces you into dirty flashing and is generally a thing that sits between you and your files, so that's another thing that can possibly go wrong... I am looking into it but it will take time with how things are going rn :)

In a nutshell, even stock(-based) roms sometimes need a good clean flashing, it's just how things are with big OS-es. PCs are the same with Linux and Windows, sometimes a reinstall is all you need.
 
  • Like
Reactions: Berni-0815

torben5247

Senior Member
Apr 13, 2013
366
64
Does the Delta update work in the lineage update app?
After applying the update, the phone boots up in twrp to install the upgrade nothing happens.....
i am using twrp 3.1.1-0
am i the only one having this issue??
It works perfectly on my z4 tablet.
 

Cerhio

Senior Member
Feb 25, 2013
225
30
Anyone getting super slow battery charging? I'm at 11% and its telling me 2 hours before its charged. Seems unusual.
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 74
    LineageOS 14.1 for the Sony Xperia Z5 Compact

    Code:
    #include 
    /*
    * 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.
    */

    Known Bugs: Video Record may be broken

    Download: Get LineageOS
    Kernel sources: https://github.com/nzzane/android_kernel_sony_msm8994
    Tree sources: https://github.com/nzzane/device_sony_suzuran
    Unofficial OTA: https://github.com/nzzane/LineageOTA
    If you enjoy this rom why not Donate to support future releases and hosting ;)


    Additional Information: This is the FIRST ever released Z5 Compact custom AOSP ROM that is using the Stock kernel and blobs. What this means? Not much, exept for the stock like camera of cause, if that is something you care about ;)


    Now stop reading this post. Seriously. You are wasting your time. FLASH THIS AND TAKE PICTURES!

    HUGE THANKS; to all the lineage and kitakami devs who have been working on this, and continue to work hard on this to get you (and me) the best rom that they can! :)
    NOTE:This uses stock kernel and blobs - meaning NO RECOVERY. Please know how to use "fastboot boot boot.img" if you get stuck anywhere

    NOTICE:
    It has been really fun porting and Lineage and Carbonrom top the Z5C, and it has been amazing to see you guys (The community) try it out for yourselves and make your own builds. Due to my Z5C being broke I have passed it on to a recycling company - meaning I can no longer test or update builds. Please do feel free to link your own builds in the comments (As long as they do not breach the rules of course ;) )
    Thanks for the support this year - and I want to thank those who are keeping their own builds up to date! :)


    XDA:DevDB Information
    [ROM][7.X.X]LineageOS [Suzuran], ROM for the Sony Xperia Z5 Compact

    Contributors
    nzzane, myself5
    Source Code: https://github.com/LineageOS

    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.10.x
    ROM Firmware Required: TWRP 3.0.2
    Based On: AOSP, Cyanogenmod

    Version Information
    Status: Beta
    Current Stable Version: 20170827
    Stable Release Date: 2017-08-27
    Current Beta Version: 20170219
    Beta Release Date: 2017-02-19

    Created 2017-02-07
    Last Updated 2017-12-20
    27
    I love how https://github.com/olefb/android_kernel_sony_msm8994/commit/39fe2aaf4701a1ea81812aeaa524d2271b6d33ef

    Is literally doing nothing, because all the makefile code to actually compile the driver is commented out ;P

    So I think all that was needed was the proper bcmdhd config.

    Nice job though :)

    Hah, yeah, I haven't had time to test if it works without that whole commit. Check @zacharias.maladroit's comment here, though: https://github.com/zachariasmaladro...mmit/4ae82dfd11047aeab84dffea3deb80a4b3b0cba1

    Hoping it's fine to post a build here: https://drive.google.com/open?id=0B629ORx1POtQRVZXRHVYMVB0RlU

    Also included the latest changes from Gerrit that fix fingerprint and should fix Bluetooth calling. Be grateful to the people who have been maintaining these LineageOS device trees (just mentioning a few here: Olivier K., Nickolay S., Giulio C., Balázs T., Vladimir M., Evgeny P., Chirayu D., Christian O. (Myself5 here), Rohit G.). They don't get enough credit from us users!
    22
    Work Status

    STATUS: UP TO DATE
    Thanks to all the supporters of this project, and a special mention to the following
    @CubeDev [Build Server - While mine was being repaired]
    @Myself5 [Sumire development - LineageOS development]
    @Triflot [Keeping things alive and fixing some bugs relating to wifi and wakelocks]
    @Berni-0815 [Keeping things alive and fixing bugs + Substratum]

    And to all the donors who support the time that has gone into this project
    17
    Updates on the way
    Going to be a lot more up to date and closer to where CarbonROM is at (good battery and stability etc)
    As well, I will be trying to get back into weekly builds so keep an eye out ?
    17
    Camera ;)

    So we now have a really awesome, working camera ;) Way better than stock in low light
    Nearly got SIM and wifi working, logs are so clean now, its almost unreal