[ROM][UNOFFICIAL] Lineage OS 13 For Obake [22/2/17]

[Surmoka]

Nandroid backup and restore via TWRP?

Sent from my XT1080 using Tapatalk

Of course I can backup and restore. But this is not always possible, now I'm on 5.1.1 and cannot revert back to my 4.4.2 despite it's backed up. TWRP will just not restore correctly, there is some part of the phone that will not be saved.

 

[MArtyChubbs]

Of course I can backup and restore. But this is not always possible, now I'm on 5.1.1 and cannot revert back to my 4.4.2 despite it's backed up. TWRP will just not restore correctly, there is some part of the phone that will not be saved.

I've had problems downgrading stock roms, but had better success going from CM to stock from Nandroid backups. Good news, I am getting a new phone today (S7E) so I will be the test case for you. I'll keep you posted on the results.

Sent from my XT1080 using Tapatalk

 

[Surmoka]

I've had problems downgrading stock roms, but had better success going from CM to stock from Nandroid backups. Good news, I am getting a new phone today (S7E) so I will be the test case for you. I'll keep you posted on the results.

Sent from my XT1080 using Tapatalk

Thanks. It is also possible that newer TWRP versions now include full-scale backup. (Never had such problems with Clockworkmod)

 

[twidave]

I'm liking this ROM so far with only 2 exceptions:
1. For some reason Bluetooth only half works - I can stream music, but I can't make or answer phone calls unless Bluetooth is off first, and then switched on after the call is connected.
2. I was really hoping for Camera2 API. Honestly, the only reason I went to CM12.1 and now CM13 was for Manual Focus...

The Led/Flashlight issue from the pull down drawer is no biggie. This ROM is like 99% there. Have used it for a couple of days and really like it.
If I may ask a question of those more experienced than I, these CM ROMs are just patches to KitKat 4.4.4 correct? I mean, they aren't full 5.1 or 6.0 OS's right?
If that is true, would I be better off flashing the Moto X 5.1 OEM ROM? (does it even have Camera2 API?)

Thanks for the great work on this by the way!

 

[notz76]

I have created new builds with latest security patches.

Gesendet von meinem DROID Mini mit Tapatalk

 

[monsterlucifer]

Many thanks!!

 

[SnipeR_TT]

Thanks!

 

[Summersett]

I'm using the updated build, stock gapps from opengapps.org, and TWRP 2.8.7.0, but otherwise wiped System+Data/Dalvik/Cache and then followed the instructions to flash CM 12.1 and flash CM 13+Gapps over it, but my flashlight and speaker phone still aren't working. I'll get over it until a patch is made though; not a big deal to me. Thanks for the great ROM @notz76!

 

[monsterlucifer]

I'm using the updated build, stock gapps from opengapps.org, and TWRP 2.8.7.0, but otherwise wiped System+Data/Dalvik/Cache and then followed the instructions to flash CM 12.1 and flash CM 13+Gapps over it, but my flashlight and speaker phone still aren't working. I'll get over it until a patch is made though; not a big deal to me. Thanks for the great ROM @notz76!

Initially, I also did a complete wipe + erase via TWRP then installed this rom and my speakerphone was not working in the first instance. I reverted to stock ROM then. After that, I again did a complete wipe + erase via TWRP. Flashed cm12.1 latest nightly (speakerphone didn't work on cm12.1 either). On this install of cm12.1, I didn't install anything, just booted up clean cm12.1, reboot into TWRP, factory reset and installed this rom followed by OpenGApps. From that day onwards, the speakerphone just worked flawlessly. I again dirty flashed the latest LED rom on my droid mini and so far it works without any issues. May be you should duplicate the steps above and try it out. Flash light issue is still a work in progress as reported by OP and is reportedly resolved using 3rd party app.

 

[Summersett]

Well I found something interesting...

When the screen is on and I get a call, I hit answer from the heads up notification (or drop down notification) and the internal speaker works fine but speakerphone is muted (I can't hear them and they can't hear me).

When the screen is off and I get a call, I hit answer by swiping the button to the right and the internal speaker is muted (I can't hear them and they cant hear me) but speakerphone works fine!

So screen on/off when receiving the call flipflops the behavior. This is with a complete wipe+erase and flashing CM13. Hope this might help @notz76 fix it.

 

[kude87]

Couple observations after a few weeks of use:

1) Audio on video recording doesn't have great quality. Sounds a bit muffled and distorted. Nothing huge, but noticeable.

2) Sometimes the camera button is greyed out, and you can't snap a picture unless you clear the camera app from memory. One time I had to reboot entirely. Seems to happen rarely.

3) Bluetooth is sometimes finicky. Works well with my Sync in my car, but for some reason when I call it goes through the phone and not the car. Will do more checking. Also the battery drain with bluetooth is high for me, but will monitor it.

Still easily my daily driver. Great rom.

 

[s_u_n]

I just installed the latest build from March on my Droid Maxx along with 'nano' OpenGapps.
Coming from TeamEXODUS ROM, the upgrade was very smooth and seamless.\

The speakerphone mode does not work at all during calls. You cannot hear anything nor does the other party hear anything when the Speakerphone is kept on.
I had not wiped Internal Storage but had wiped everything else.

 

[s_u_n]

Tried a few things from the previous page in order to fix the speakerphone problem.
Since speakerphone was not working on CM 13, I downloaded CM 12.1 from 27 January. I did not download corresponding GApps.
Now, I copied over the file to the device and rebooted to recovery.
Then, I wiped everything other than internal data and then flashed CM 12.1
I could not test if speakerphone worked, because after CM 12.1 was booted, the device would reboot after the 'configure WiFi' stage.
Then I flashed CM 13 and OpenGapps after a factory reset. The speakerphone did not work. The torch worked though in my case, unlike someone else's observation above.

Now, I am trying to restore the device to 5.1 (from Team Exodus).

Edit: Restoring to 5.1 (Team Exodus) landed me into trouble. After restoration, the phone got stuck in the animation.
So, I decided to go back to stock 4.4.
I tried to restore my backup from TWRP (to my stock 4.4). I selected only system and data (unselected boot) in the Restore screen inside TWRP.
Now, I am not sure if that was the right thing to do. The phone got stuck on the "Warning bootloader unlocked" screen.


Adding some of my notes here as I progressed....

So, I again went into Recovery and this time I did a format of cache, dalvik and system. Then tried to restore my

stock 4.4

Again back in the "Warning bootloader unlocked" screen. The phone is sitting on that screen since 3 minutes.

So, again rebooted to Recovery and this time I am trying to restore System, Data and Boot partition. Without this,

the phone is not booting into Android it seems.


So, flashing the boot partition above seems to work. Now, I get the familiar "Droid.." sound.

I was back on Stock 4.4.4
Now, inside recovery, I wiped cache, data, dalvik and system (did not touch internal storage)
Installed CM 12.1
This time CM 12.1 did not have any crashes. I made a test call. Speakerphone did not work.

Rebooted to recovery and did a factory reset. Then installed CM 13 followed by GApps. Rebooted.
Speakerphone still does not work.
The only thing I have not done is wipe "Internal Storage". I don't know if that could be affecting somehow.

 

[mushbert]

My device is still running 4.2.2, and if I try a newer version I want to maintain the ability to downgrade to it - which means keeping the bootloader under a specific version.

Is a minimum bootloader version required for this ROM (or any others)?

 

[s_u_n]

My device is still running 4.2.2, and if I try a newer version I want to maintain the ability to downgrade to it - which means keeping the bootloader under a specific version.

Is a minimum bootloader version required for this ROM (or any others)?

The best thing you could do, in my opinion, is to get the bootloader unlocked via Sunshine.
If you have already done so, then you can upgrade to 4.4.4 (stock). This was the last update from Motorola.
You can then install TWRP 2.8.x.x. and then take a backup from the same.
Now, once this backup is in place, you can always try out different ROMS (Android L or Android M). If you don't like them you can simply revert back to stock via the backup taken earlier in TWRP.

 

[mushbert]

you can upgrade to 4.4.4 (stock).

Thank you but I don't believe this answers my question. My understanding is that the bootloader included with 4.4.4 is the element which subsequently prevents downgrades, but that if I were to flash the partitions manually, skipping the bootloader, 4.4.x would still run with the JB bootloader. Unfortunately I don't know if this is the case with Android L or M.

I'm still on JB because there are several aspects of it that I prefer to KK.

 

[s_u_n]

Thank you but I don't believe this answers my question. My understanding is that the bootloader included with 4.4.4 is the element which subsequently prevents downgrades, but that if I were to flash the partitions manually, skipping the bootloader, 4.4.x would still run with the JB bootloader. Unfortunately I don't know if this is the case with Android L or M.

I'm still on JB because there are several aspects of it that I prefer to KK.

Well, I am sorry that I do not have an answer to that.
If you prefer JB, then you might as well stick to it. Remember that your phone is missing several critical security patches and Motorola has no intention to fix the vulnerabilities (even on 4.4.4).

----Meanwhile, on my phone, I can confirm that the speakerphone issue causes a major problem.
If I receive a phone while the phone is at rest, I will have to make the conversation in speakerphone mode ONLY. This makes it impractical to have conversations in office. I suppose, I will have to revert back to Exodus ROM running 5.1.x now unless someone knows how to fix this.

I have already tried the solution on the previous page and that did not seem to help in my case.

Edit:
It seems the speakerphone problem is not unique to Droid Maxx. I can see people complaining about this issue on OnePlusOne threads as well right from CM 12.
I tried some of the suggestions on those threads, but was not successful.

 

[MArtyChubbs]

Anyone else have issues with making a google hangouts video call? I don't see my contacts image. They can see me.

If someone could please test this for me, it would be greatly appreciated.

Running CM13 on XT1080

Thank you!

 

[kude87]

Anyone else have issues with making a google hangouts video call? I don't see my contacts image. They can see me.

If someone could please test this for me, it would be greatly appreciated.

Running CM13 on XT1080

Thank you!

Mine is working just fine, outside of the usual grainy video quality I always seem to have, on any rom.

Also, speakerphone is working fine for me for others asking.

 

[s_u_n]

This ROM has been very smooth. Other than the speakerphone issue and the torch issue (torch goes off after few seconds), I have had a positive experience.
BTW: CVE-2015-1805 has been patched a couple of days ago. So, can the OP please try and get that patch for us?

I am continuing for some more time with this ROM, hoping to find a solution to the speakerphone issue.


Edit: I have a strong feeling that the speakerphone issue is this one: https://jira.cyanogenmod.org/browse/CYAN-5728