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

[ROM][UNOFFICIAL] Lineage OS 13 For Obake [22/2/17] - Droid Ultra Android Development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lineage OS is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Lineage OS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. Lineage OS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Code:
/*
* 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.
*/
When coming from any other ROM, you must do a factory reset / clean flash.
The first boot can take a very long time. Don't assume that it is a bad flash, boot loop, etc. until it has sat for at least 5 minutes.
Links
ROM: download
GAPPS: opengapps.org
PROTIP: Be sure to flash gapps at the same time you flash the rom. If you boot into los-13.0 without gapps and attempt to flash them later, you're going to have a bad time
Working Stuff
SIM
Phone Calls
Text Messaging
Mobile Data
Sensors
WLAN
Bluetooth
Camera
USB / USB-OTG
Doze mode
NFC
Tethering
Known Issues
2G/3G Switch
Video Recording
Flashlight Turns off after few seconds [WIP]
Crazy/Inverted Colour While Playing Video Through Instagram
XDA:DevDB Information
[ROM][UNOFFICIAL] Lineage OS 13 For Obake [22/2/17], ROM for the Motorola Droid Ultra
Contributors
notz76
Source Code: https://github.com/LineageOS/android_kernel_motorola_ghost
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: Lineage OS
Version Information
Status: Alpha
Created 2016-02-22
Last Updated 2017-02-22

Installing now, will test and report my findings. Thanks for this! Been looking out for a while.
Edit:
So after using this rom for a day, I can say its quite stable for an alpha rom. It's fast, transitions and scrolling are smooth. I had absolutely no freezes, crashes or restarts. With some work, it can be a great rom!

This rom on my maxx is faster than my dt2 on 5.1..1 of course I havent added any apps yet but it is fast as ****

I can't wait to try it out soon. Just waiting to hear more try it out since my phone is a daily driver for work ><

I'm officially using it as my daily. The only thing that doesn't work that bothers me is the flashlight. Video recording actually works fine for me.
Device is a Droid Mini.

bigv5150 said:
This rom on my maxx is faster than my dt2 on 5.1..1 of course I havent added any apps yet but it is fast as ****
Click to expand...
Click to collapse
That is quite an endorsement for the ROM! As soon as the flashlight bug is fixed, I'm flashing!!
Sent from my XT1080 using Tapatalk

No issues so far. Loving it as a daily driver. A third party flashlight app works fine. Stock camera didn't work at first, installed google camera which worked. Then I tried the stock camera again and it works fine, video and all. Weird.
Multi-windows also works fine.
All in all, great job and keep the builds coming.

I couldn't help myself, installing Apps now but yeah, no joke, this thing is smooth... Almost as smooth as my iPhone 6s j/k
Edit: been running for a few hours and it has bogged down a bit with all the Apps I've installed. Still not bad but getting some serious lag with the keyboard as I'm typing this...
Edit2: lag seem to be from BT, I toggled it and everything went back to normal. It was BT'd to my car earlier.
Edit3: loving this ROM! Installed Xposed and Greenify. Battery life so far is pretty good. Will continue to monitor and report back.
Sent from my DROID MAXX using Tapatalk

Bootlooped on a clean flash....just got stuck on the CM logo. Anyone else? DL's are good, TWRP at 2.8.7.0.
Edit: I'm on my third clean flash and it appears to be stuck yet again. I can't get passed the logo. What am I doing wrong? I've re-downloaded, all flashes appear to be successful, I believe my TWRP to be the latest. How long did it sit on the logo? When it's over 10-12 minutes I start over. Should I be changing the system format in TWRP or something? I've flashed all the 5.1.x roms and back to stock a ton, so I must be missing something here that I'm unaware of.

kude87 said:
Bootlooped on a clean flash....just got stuck on the CM logo. Anyone else? DL's are good, TWRP at 2.8.7.0.
Edit: I'm on my third clean flash and it appears to be stuck yet again. I can't get passed the logo. What am I doing wrong? I've re-downloaded, all flashes appear to be successful, I believe my TWRP to be the latest. How long did it sit on the logo? When it's over 10-12 minutes I start over. Should I be changing the system format in TWRP or something? I've flashed all the 5.1.x roms and back to stock a ton, so I must be missing something here that I'm unaware of.
Click to expand...
Click to collapse
All I can think of is your bootloader. What version are you running?
Sent from my iPad using Crapatalk

Johnny Wong said:
All I can think of is your bootloader. What version are you running?
Sent from my iPad using Crapatalk
Click to expand...
Click to collapse
Good call, though I'm not sure what version I need. I'm on 30.BA.

kude87 said:
Good call, though I'm not sure what version I need. I'm on 30.BA.
Click to expand...
Click to collapse
I'm running the bootloader from 4.4.4 SU6-7. Forgot what the bootloader version is exactly. Running battery test right now and don't want to boot into recovery, lol
Sent from my iPad using Crapatalk

Johnny Wong said:
I'm running the bootloader from 4.4.4 SU6-7. Forgot what the bootloader version is exactly. Running battery test right now and don't want to boot into recovery, lol
Sent from my iPad using Crapatalk
Click to expand...
Click to collapse
I'm not sure then. I unlocked way back on 4.4 with sunshine, but I have flashed new versions of 4.4.4 along the way. I know I'm on at least 6-7, and I think I'm on 7-2. I thought if I unlocked ages ago, the bootloader does not update with new flashes? Now I'm just unsure of this all. If someone can chip in with bootloader info for flashing 6.0, that would be great.

kude87 said:
I'm not sure then. I unlocked way back on 4.4 with sunshine, but I have flashed new versions of 4.4.4 along the way. I know I'm on at least 6-7, and I think I'm on 7-2. I thought if I unlocked ages ago, the bootloader does not update with new flashes? Now I'm just unsure of this all. If someone can chip in with bootloader info for flashing 6.0, that would be great.
Click to expand...
Click to collapse
I just checked mine, it is 30.BA. Sorry, back to square one.
Sent from my iPad using Crapatalk

Johnny Wong said:
I just checked mine, it is 30.BA. Sorry, back to square one.
Sent from my iPad using Crapatalk
Click to expand...
Click to collapse
Thanks, I appreciate your help. Gonna be honest, I've never had more issue flashing stuff than I have with my Maxx. Seems there's always an issue, yet I always do it to myself with the want to flash stuff, ha.
Back on stock. If someone has any ideas of why it sticks on the CM logo, I'd be curious to try this again.

Can't thank you enough for this!! Flashing right now and will report back!
---------- Post added at 05:18 PM ---------- Previous post was at 04:51 PM ----------
I am on TWRP 2.8.4.0 and install went super smooth - Droid Mini.
I went ahead and flashed OpenGApss mini package and it was a bad call. Continuous messages popping up on reboot,
Setup Wizard has stopped.
Clock has stopped.
Play services stopped.
lol, read the instructions just now Will re-flash and report back
---------- Post added at 06:11 PM ---------- Previous post was at 05:18 PM ----------
Well, it went fine - had to flash both rom and gapps one after the other without booting (as mentioned in first post). Everything seems to work. I'll report back after trying it out extensively during the next couple of days hopefully. Thank you again

Hey kude, i had the same issue. I know sometimes cm doesn't play well with a clean install. I installed a old snapshot of cm12 from a clean wipe. Then did a factory wipe(data, cache, and dalvik. No system and internal storage wipe) and installed cm13 over that with marshmallow gapps. Booted fine after that.
Its been a few days and I've had no problems. Great rom

appletonpunk said:
Hey kude, i had the same issue. I know sometimes cm doesn't play well with a clean install. I installed a old snapshot of cm12 from a clean wipe. Then did a factory wipe(data, cache, and dalvik. No system and internal storage wipe) and installed cm13 over that with marshmallow gapps. Booted fine after that.
Its been a few days and I've had no problems. Great rom
Click to expand...
Click to collapse
This is good info, thanks! When I have some time to do this, I'll try your method. How's GPS on this new rom? All the 5.1.1 roms had finicky GPS and data hand off quirks for me.

I just wiped everything clean: Dalvik Cache, System, Data, Internal Storage & Cache. Then rebooted in Recovery and plugged in to PC and copied rom and gapps. Flashed both one after the other and rebooted. This went fine!
I'm using Google Maps and GPS seems to be behaving properly. Device is Droid Mini. The Speakerphone during calls and LED issue remains the same as in CM12.1. Speakerphone during the call does not work. It works as a mute button but neither sound goes out nor it gets in. Pressing it back restores the call. Notification LEDs does not work at all.

Yeah notification LED not working in CM 12.1 ..i hope thats working in cm 13. My device droid mini. Thanks Sir...

Related

[ROM] SlimBean 6 Unofficial XT907 [5-31-13]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer: We are not responsible for any damages on your device.
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.
*/
Original Slim Features:
The Real Dark Slim inverted theme
Notification drawer Shortcuts
Customized Pie and NavBar/NavRing
Full hardware key rebinding!
Auto-rotation on keyboard open
SlimCenter, SlimIRC and much more
Check out our full feature list here
Changelog
5-31-13
Initial Release Slim Bean 6
Find our latest Changelog go here
What Does Not Work
Camcorder
You tell us
Chat with the slim team and other slim users
IRC: #slimusers @ freenode
New to IRC? Don't have a native app? Try the Freenode web client [link] or the Firefox extension Chatzilla [link]
Google+ [link]
Twitter [link]
Facebook [Link]
Downloads
XT907
http://downloads.codefi.re/darkspad...07-4.2.2.build.6-UNOFFICIAL-20130530-2235.zip
GAPPS
http://slimroms.net/index.php/downloads/all/viewdownload/383-addons/2822-slim-gapps-4-2-2-build-6
Installation instructions
For Most Users
Please keep in mind if a special instruction is needed it will be noted in the Changelog
Download the latest build]
Addons ( if you don't have it already) from [here]
!Recommended! Full wipe, and manual format /system
Flash ROM and the addons you want, reboot
Screenshots
FAQ
Check out out FAQ before posting! Keeps more common questions answered in one place!
Help us out!
If you want to help us by translating slim to your language check out Crowdin.net and submite your translations.
Or consider a donation.
Thanks!
dhacker
hashcodeof
epinter
slimbean team
cyanogenmod team
motorola
google
You can find the full list of credits here
Source
Please visit here and here for the rom source code.
here for the kernel source code.

reserved

Going to give this a try on my RAZR M. Thanks!
Flashed it over and it went great. Obviously because of the kernel that is used on most 4.2.2 ROMs there are slight issues that just can't be addressed until a new improved kernel hopefully comes out. One is example as programs like Voxer won't be able to properly work with the mic. But, as far as this ROM it's pretty awesome with all the screen space it gives and easy way to adjust options.

is it base on cm10 or cm10.1?
if it cm10.1 based rom, is the laggy problem solved?

goodayoo said:
is it base on cm10 or cm10.1?
if it cm10.1 based rom, is the laggy problem solved?
Click to expand...
Click to collapse
The lag in cm10.1 has been fixed as of 5/24/13. Dhacker released a new build with a new kernel on that day. So the lag is history.
Sent from my XT907 using Tapatalk 2

goodayoo said:
is it base on cm10 or cm10.1?
if it cm10.1 based rom, is the laggy problem solved?
Click to expand...
Click to collapse
I'm guessing this is a CM10.1 (JB 4.2.2) b/c the OP says camcorder is not working - but I have yet to download this ROM.

tolymatev said:
The lag in cm10.1 has been fixed as of 5/24/13. Dhacker released a new build with a new kernel on that day. So the lag is history.
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Apparently, you haven't used any of the recently updated CM10.1 builds. They are as good as CM10.

Been running this for a day or so and it's by far the best 4.2.2 ROM out there right now for the M. Good work!!

I have flashed many before on the unlocked razr m.
I followed the instructions, wiped, wiped, format/wipe system. then installed rom, it reboots and stuck in bootloop on boot animation. i let it sit for 10 minutes and it wont go past. any ideas? am I missing a step here?

CamoCustom said:
I have flashed many before on the unlocked razr m.
I followed the instructions, wiped, wiped, format/wipe system. then installed rom, it reboots and stuck in bootloop on boot animation. i let it sit for 10 minutes and it wont go past. any ideas? am I missing a step here?
Click to expand...
Click to collapse
Wipe, then reboot recovery and mount system. Mine sat for a few minutes on first boot. Did you download and install GAPPS too?
This thing is running smooth. Smoothest 4.2.2 ROM I've run.

RikRong said:
Wipe, then reboot recovery and mount system. Mine sat for a few minutes on first boot. Did you download and install GAPPS too?
This thing is running smooth. Smoothest 4.2.2 ROM I've run.
Click to expand...
Click to collapse
Yes installed gapps too, so after installing- wipe, and reboot recovery then mount system

CamoCustom said:
Yes installed gapps too, so after installing- wipe, and reboot recovery then mount system
Click to expand...
Click to collapse
Wipe cache, dalvik, FDR (wipe system, if you want, but I never do), reboot recovery, and mount system. Then flash away. Just a heads-up, if you flash TWRP 2.5, which Matt just posted, the wipe option will wipe cache/dalvik and FDR all at the same time.

Oh boy another ROM. I just flashed like 5 times this week. Gotta keep it together woooooooosaaaaaaah.

Issues
How is battery life is it simliar to stock or Cm 10.1 and does it have the same problems such as no camcorder and camera preview.

jekovenatinsley said:
How is battery life is it simliar to stock or Cm 10.1 and does it have the same problems such as no camcorder and camera preview.
Click to expand...
Click to collapse
All CM10.1 builds if updated to the latest have the camera preview fixed. The camcorder is still not fixed according to the original post on the first page. I can't speak for the battery life as I have not had a chance to flash this ROM. But the recent CM10.1 built ROMs seem to have decent battery life.

Does rom have the same radio as the one in CM 10.1 (Unofficial). I love 4.2 but without a better radio theres no point in me using it.
Ive got the stock 4.1.2 radio, would i be able to flash that over 10.1 and get it working?

Re-flashed all is good, except bluethooth streaming. Rom is smooth, and lots of cool settings. Thanks to the devs.

Can anyone verify if Bluetooth streaming audio is working with this ROM
Thanks!

dnoren said:
Can anyone verify if Bluetooth streaming audio is working with this ROM
Thanks!
Click to expand...
Click to collapse
No its not working for me, none of the 10.1 Roms I've tried has bluetooth working which is a major bummer for me.
Still playing around with it though and this rom is great, with that one exception.
P.S When I hit play on the music player I just get a low hissing noise.

I noticed that LCD density is set at 184 as default. This makes everything pretty small on the screen. I changed it back to 240 through the Slim settings. Everything looks good now.
jekovenatinsley said:
How is battery life is it simliar to stock or Cm 10.1 and does it have the same problems such as no camcorder and camera preview.
Click to expand...
Click to collapse
I wish people would really stop asking about battery life. You know what the answer will be, so stop asking. If you want battery life, use a stock build. If you want customization, use an AOSP build.
With that being said, I think battery life will be good for a AOSP based ROM. It runs smoothly and has some good tweaks, so I think battery will be decent.
b0uncyfr0 said:
Does rom have the same radio as the one in CM 10.1 (Unofficial). I love 4.2 but without a better radio theres no point in me using it.
Ive got the stock 4.1.2 radio, would i be able to flash that over 10.1 and get it working?
Click to expand...
Click to collapse
Every single 4.2 ROM uses the stock radio, the same exact one that came in the latest update. There's no point in flashing one separately. I don't have reception issues, if you do it's not because of the radio. It's because of the kernel. The kernel and 4.2 ROMs are still works in progress. until the bugs are worked out, radio reception and battery won't be as good as stock.

[ROM] [5.0/5.1] [Official/Official] SlimLP 0.8 beta - Peregrine - 29/09/2015

Official/Newer build 5.1 build by Thecrazyskull(Official device maintainer for moto msm8226 devices)
Older builds below
SlimLP Android 5.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimLP is currently in alpha / beta stage, some custom features are already in place, but much much more is planned for the future.
Download:
Alpha
Google Apps / How to
Follow the work on our custom gapps and find downloads here.
Or Use PA Gapps or any other Lollipop Gapps of your Choice.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download other addons.
Installation instructions Same as CM12
Latest Changelog - Read here if you want information on changes in latest build.
Slim FAQ
Kernel Source - The source of your device's kernel.
My repo
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
Thanks -
- SlimRoms for creating an sharing their vision
- Jubakuba for the OP
- Somcom3X and the CM team for the work on the device/vendor trees
XDA:DevDB Information
SlimRoms, ROM for the Moto G
Contributors
Kayant, Thecrazyskull, prbassplayer
Source Code: https://github.com/SlimRoms
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Alpha
Created 2015-01-11
Last Updated 2015-10-21

Reserved

Amazing rom! There isn't any noticeable bugs that I can see, multitask is a beast, and battery life so far lasts about the whole day using about 2% battery per hour. I used your pink kernel with intelliplug on. The only thing that seems to not work is changing the governor. It always switches back to interactive. Other than that, very impressive for an alpha build! THANK YOU!

Do i need to flash cm11 first? Got a bootloop
Sent from my XT1052 using XDA Free mobile app

whisper13 said:
Do i need to flash cm11 first? Got a bootloop
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
No. But if you're coming from CM a data wipe is needed likely which is why you're probably in a bootloop. CM 11 --> CM12 should be fine with data. CM11 --> other lollipop based roms = most likely a bootloop.

Does it include fm radio?

JimYoung said:
Does it include fm radio?
Click to expand...
Click to collapse
Yes, and it is working very well.
Great work for a alpha version.

The first boot will take quite awhile so just be patient. Also, it seems I can't set my own ringtones and notification sounds.

hotbld5 said:
The first boot will take quite awhile so just be patient. Also, it seems I can't set my own ringtones and notification sounds.
Click to expand...
Click to collapse
Im coming from the original ROM, with root and some mods from Xposed... Did a wipe factory (TWRP), installed ROM and then Gapps, First time took more than 10 minutes to boot and nothing.
Now I did wipe cache, data, dalvik and system, then reinstalled everything... Again it is taking more than 10 minutes to boot.... I will wait more 10... lets see, hope it boots!!!
update: 22 minutes waiting, I guess it will not boot... any ideas?
Thanks guys!

mrps2 said:
Im coming from the original ROM, with root and some mods from Xposed... Did a wipe factory (TWRP), installed ROM and then Gapps, First time took more than 10 minutes to boot and nothing.
Now I did wipe cache, data, dalvik and system, then reinstalled everything... Again it is taking more than 10 minutes to boot.... I will wait more 10... lets see, hope it boots!!!
update: 22 minutes waiting, I guess it will not boot... any ideas?
Thanks guys!
Click to expand...
Click to collapse
Try CWM recovery and see if it'll work.

mrps2 said:
Im coming from the original ROM, with root and some mods from Xposed... Did a wipe factory (TWRP), installed ROM and then Gapps, First time took more than 10 minutes to boot and nothing.
Now I did wipe cache, data, dalvik and system, then reinstalled everything... Again it is taking more than 10 minutes to boot.... I will wait more 10... lets see, hope it boots!!!
update: 22 minutes waiting, I guess it will not boot... any ideas?
Thanks guys!
Click to expand...
Click to collapse
I first flashed an unofficial build of cm12 (before the issue of builds needing to have cm 11 installed first) then let it boot, then after that go back to recovery and install SlimPL
Took 5-10mins to boot
Sent from my XT1045 using XDA Free mobile app

Thanks, its is "upgrading" right now, what I did was get a CM 11 (pacman Rom) installed it , rebooted and flash Slim ans Gapps...
Now I just got a process com.android.phone has stopped...
lets see... Thanks
Edit: Telephone not working... cannot make call or use data and clock not working as well. installed CM 11 and CM12 and them Slim and same problem happened... CM12 working fine

After installing cm12 unofficial, i just did the normal wiping process dalvik data dalvik cache system & factory reset, then it booted
Sent from my XT1045 using XDA Free mobile app

whisper13 said:
After installing cm12 unofficial, i just did the normal wiping process dalvik data dalvik cache system & factory reset, then it booted
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
When I do this my phone just stay on the Slim boot screen...
For now I will try CM12 and when I get some more time I will try to use Slim again, need my phone working to work
Thanks guys! if someone come with some solution I will be glad to try...:good:

I flashed this kernel & it stopped mine sticking on the slim booting logo

Just flashed the Jan 11 build(with basketbuild 5.0 gapps), seems pretty solid.
Noticed a few things, though:
There's no outgoing/incoming indicator for network activity for Wifi and Data(the arrow up/down on their respective icons)
Total display seems zoomed out a bit? In a nice way
Carrier name on lockscreen is a little to the center, shouldn't it be on the left?
Camera's not working for me, even google camera(freezes upon capturing a photo, though can swipe from left to bring up a menu)
AudioFX isn't working for me, tried playing around but couldn't get it to work with Google Play Music, can't really tell if it's the player or AudioFX as there's no stock Music player to try on
Superuser out of the box is not working, though flashing SuperSU 2.40 worked.
Had a random reboot while playing video, probably nothing
Other than what was mentioned, really enjoying this rom and already planning on using it was my daily driver. Cheers!

Great ROM over all. Got a few issues:
1. When you try to import contacts from a backup on the phone it crashes the import (finding file via file manager then opening that way works fine)
2. When I use camera it will take pictures no problem but wont save them. Also when you press the back button when camera is open it won't close. Have press home for it to close. Does this on other camera apps and other lollipop builds so maybe a cm12 issue.
3. When enabling the dark theme in messages it doesn't do anything (cm12 issue would say)
I flashed cleanly per the instructions.
Would be nice to be able to change battery icon and have a clear all under open apps option but these are just extras can love without.
Thanks for your had work so far

Zyquil said:
Just flashed the Jan 11 build(with basketbuild 5.0 gapps), seems pretty solid.
Noticed a few things, though:
[*]Total display seems zoomed out a bit? In a nice way
Click to expand...
Click to collapse
Yeah Slim always changes the dpi. But compared to kitkat it is much more humane now.
Zyquil said:
[*]Carrier name on lockscreen is a little to the center, shouldn't it be on the left?
Click to expand...
Click to collapse
Cm12 error. In cm 12 fixed since a while
[*]Camera's not working for me, even google camera(freezes upon capturing a photo, though can swipe from left to bring up a menu)
Click to expand...
Click to collapse
use google camera
[*]AudioFX isn't working for me, tried playing around but couldn't get it to work with Google Play Music, can't really tell if it's the player or AudioFX as there's no stock Music player to try on
[*]Superuser out of the box is not working, though flashing SuperSU 2.40 worked.
[*]Had a random reboot while playing video, probably nothing
[/list]
Other than what was mentioned, really enjoying this rom and already planning on using it was my daily driver. Cheers!
Click to expand...
Click to collapse
All CM12 bugs. Still this has a lot better multitasking
cobalt01 said:
Great ROM over all. Got a few issues:
2. When I use camera it will take pictures no problem but wont save them. Also when you press the back button when camera is open it won't close. Have press home for it to close. Does this on other camera apps and other lollipop builds so maybe a cm12 issue.
Click to expand...
Click to collapse
Look above. After a reboot it worked for me
Gesendet von meinem XT1039 mit Tapatalk

keenofhiphop said:
Yeah Slim always changes the dpi. But compared to kitkat it is much more humane now.
Cm12 error. In cm 12 fixed since a while
use google camera
All CM12 bugs. Still this has a lot better multitasking
Look above. After a reboot it worked for me
Gesendet von meinem XT1039 mit Tapatalk
Click to expand...
Click to collapse
Camera issues persist to Google Camera too, though haven't tried other cameras if any.

Zyquil said:
Camera issues persist to Google Camera too, though haven't tried other cameras if any.
Click to expand...
Click to collapse
Also worked for me after a reboot.

[Q&A][ROM][6.0.1] CyanogenMod 13.0 for Xperia SP

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#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 this Q&A thread for CyanogenMod 13.0
Use this area to ask anything you want related to CM-13.0,
but try not to spam everyone, always search for an answer before.
General Questions & Answers
Is root access included into CM ?
Yes. Go into Settings, About Phone. Tap "Build number" 7 times.
Go back, open Developer options. Change "Root access" option.
Do not use SuperSU unless you are sure, creates booting issues.
Read more about it : Here.
Is the ROM suited for daily usage ? Google Apps compatible too ?
Yes completely. Nightlies and OpenGApps recommended.
Can I flash CyanogenMod NIGHTLY and UNOFFICIAL without wipes ?
Yes you can.
Should I flash SNAPSHOT builds when I'm on NIGHTLY ?
No, the Nightlies are already more up to date.
You can flash SNAPSHOT builds when you don't want to update often.
Is the device encryption supported ?
Yes it is, but if you're coming from an older ROM
please read the details here : a07afb9660a86f702066003b8e81ab63789d1660
When USB connected to a computer, I can't access the storage ?
The phone is in charge-only mode by default on Marshmallow,
due to a stronger security logic regarding unauthorized data access.
Swipe down the notifications and change the USB mode.
I can't access the ROM's recovery with Volume-
Nightlies before the 4th June 2016 suffered from an incomplete CyanogenRecovery image,
therefore the recovery fails to starts, the display fades out and the device reboots.
You can either flash the boot.img from the newer Releases with "fastboot flash boot boot.img" or FlashTool,
or follow the instructions of the TWRP Recovery installation to update from TWRP.
Against advices, I upgraded without GApps and now it crashes. Any way without factory reset ?
Yes there is, but nothing assures you'll manage to do it fully & preserve all your data...
Once booted, keep saying Ok to all "Unfortunately, ... has stopped",
pull-down the notifications panel, press the Settings icon,
go in Apps, menu, Show System, scroll to Setup Wizard (green Android logo),
Permissions, and activate Contacts + Telephone.
Later, some Play Store apps may need reinstalling.
If not ok, try this : CM Wiki
If still not, then I advise a clean factory-reset reinstallation...

Does anyone know a way (or an App) to get back the quick start function while long pressing the home button? I really miss it.

Hey Adrian, ty for all you hard work on the XSP. I just wanna know if there is a way to fix High Touch Sensitivity. On both cm 12.1 and cm13 it keeps turning off after some time of usage.

Is there a problem if I use nano Gapps instead of Micro or pico?

Hi, I'm using 20160329 build and today my SIM card was not detected, so i rebooted the phone. After reboot, (mostly) all of my app data has gone - the apps installed earlier stayed, but data like login has gone, Play Store acted like it's used first time. If the log is needed, I can get it, but I don't know how. Otherwise, the rom is great.

Everything seems to work fine on build 20162903. The only things that need fixing (so far), for me, are the lackluster gaming performance and the Duolingo app not registering when I talk to it (it worked fine on stock) even if it has the permissions to use the microphone.

Wyjek said:
Hi, I'm using 20160329 build and today my SIM card was not detected, so i rebooted the phone. After reboot, (mostly) all of my app data has gone - the apps installed earlier stayed, but data like login has gone, Play Store acted like it's used first time. If the log is needed, I can get it, but I don't know how. Otherwise, the rom is great.
Click to expand...
Click to collapse
I had a similar problem, maybe you hit the same cm upgrade bug as I did. I solved it without loss of data as described here:
http://forum.xda-developers.com/showpost.php?p=66101184&postcount=5

juliomb179 said:
Is there a problem if I use nano Gapps instead of Micro or pico?
Click to expand...
Click to collapse
should be fine ....but u can try for sure and report back

Ungewiss said:
I had a similar problem, maybe you hit the same cm upgrade bug as I did. I solved it without loss of data as described here:
http://forum.xda-developers.com/showpost.php?p=66101184&postcount=5
Click to expand...
Click to collapse
Maybe, but I did a clean install :I

flash- said:
should be fine ....but u can try for sure and report back
Click to expand...
Click to collapse
I'm on Delta Gapps base (0323) for marshmallow , no problem... :good:

Adrian, ty for all your hard work on the Relaese.
With the last Version cm-13.0-20160329 it works nice (before alot of Loop´s)
1 point of Question.
SP. MHL - HDMI OUT - now its works (perfect) only in 720p.
is there any posibility to get it work on 1080p ?
like here : xxxx//xxx.3g.co.uk/PR/March2014/how-to-connect-sony-xperia-mobile-devices-to-a-tv.html
THX alot
PIT

Krawzer said:
Hey Adrian, ty for all you hard work on the XSP. I just wanna know if there is a way to fix High Touch Sensitivity. On both cm 12.1 and cm13 it keeps turning off after some time of usage.
Click to expand...
Click to collapse
Has been fixed since my Glove Mode service, can't see how you still have the issue,
nobody reported anything related to that since the improvement.
http://review.cyanogenmod.org/#/c/117930/ (November )
Wyjek said:
Hi, I'm using 20160329 build and today my SIM card was not detected, so i rebooted the phone. After reboot, (mostly) all of my app data has gone - the apps installed earlier stayed, but data like login has gone, Play Store acted like it's used first time. If the log is needed, I can get it, but I don't know how. Otherwise, the rom is great.
Click to expand...
Click to collapse
First time reported or heard off, might be something wrong with an app or mod you used, I don't know.
pitps said:
SP. MHL - HDMI OUT - now its works (perfect) only in 720p.
is there any posibility to get it work on 1080p ?
like here : xxxx//xxx.3g.co.uk/PR/March2014/how-to-connect-sony-xperia-mobile-devices-to-a-tv.html
Click to expand...
Click to collapse
1080p should be broken in 12.1 & 13.0, it is known but hasn't been fixed since,
but obviously there are more important things to look at for the moment.

Adrian DC said:
Has been fixed since my Glove Mode service, can't see how you still have the issue,
nobody reported anything related to that since the improvement.
http://review.cyanogenmod.org/#/c/117930/ (November )
Click to expand...
Click to collapse
well this is strange , I have this problem with every recent build of any ROM, cm13 or cm12.1

Can I use open gapps aroma with this version?
Sent from my Xperia SP using Tapatalk

Krawzer said:
well this is strange , I have this problem with every recent build of any ROM, cm13 or cm12.1
Click to expand...
Click to collapse
same here

joaovitorgirotto said:
Can I use open gapps aroma with this version?
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
I think so, I am using them right now and I don't have any bugs.
Adrian DC said:
Wyjek said:
Hi, I'm using 20160329 build and today my SIM card was not detected, so i rebooted the phone. After reboot, (mostly) all of my app data has gone - the apps installed earlier stayed, but data like login has gone, Play Store acted like it's used first time. If the log is needed, I can get it, but I don't know how. Otherwise, the rom is great.
Click to expand...
Click to collapse
First time reported or heard off, might be something wrong with an app or mod you used, I don't know.
Click to expand...
Click to collapse
No way, I wasn't installing any app that requires root, no Xposed or something like that, so it's impossible.

I updated from cm12.1 unofficial build .
Everything is great, but i noticed two issues:
I set priority mode for next 4 hours, but it was active after 4 hour , and i couldn't even deactivate it manually. Restart solved the problem.
It happened one time so i couldn't take log.
Another one is audio glitch when I'm listening music with the cm music player. With musixmach it's OK.
Sent from my Xperia SP using Tapatalk

mrskyou said:
I'm on Delta Gapps base (0323) for marshmallow , no problem... :good:
Click to expand...
Click to collapse
i'm always on delta since cm12.1 ....but i just told him to report back for other users...but thanks for the tip

how's the game performance in this rom?Is the clash of clan running smooth ?

[FunTalks] I don't know about that, but me who really never plays games at all since years,
I have Rayman Adventures & Clash Royale working great . [/FunTalks]

[ROM][VNS-LX1][6.0.1][UNOFFICIAL] AICP for Huawei P9 Lite

Reserved
WORKING/NOT WORKING
-same as CM

Bugs?

How to delete the fingerprint

Does everything work or are there any bugs?

Raymen03 said:
How to delete the fingerprint
Click to expand...
Click to collapse
Settings > Lockscreen > Fingerprint > *Click on your registered fingerprint in the options* > Delete > *click OK*
Thijs van Hal said:
Does everything work or are there any bugs?
Click to expand...
Click to collapse
Simply put,it has the same bugs as CM(the 2.1MP cam limit and that is that?)

The Marionette said:
Simply put,it has the same bugs as CM(the 2.1MP cam limit and that is that?)
Click to expand...
Click to collapse
How about Bluetooth paring?

Care to elaborate on the difference between this and CM?

Hi,
I have a few questions:
1: Does this work on any P9 Lite variant (i have VNS-L21)?
2: Why is archive so big (almost 700mb)?
3: What Open Gapps package do you recommend to flash?
Tnx
tw1st3d ?

tw1st3d83 said:
Hi,
I have a few questions:
1: Does this work on any P9 Lite variant (i have VNS-L21)?
2: Why is archive so big (almost 700mb)?
3: What Open Gapps package do you recommend to flash?
Tnx
tw1st3d ?
Click to expand...
Click to collapse
1. Yeah,I declared the L"X"1 value to say that it is compatible with both L31 and L21.
2. AICP is "fatter" than CM since it has extra features,so no reason to panic. :silly:
3.I personally use the Pico package and then just install other Google apps which I need. That is the beauty of Open Gapps,you have several options.
Sent from my VNS-LX1 using Tapatalk

The Marionette said:
1. Yeah,I declared the L"X"1 value to say that it is compatible with both L31 and L21.
2. AICP is "fatter" than CM since it has extra features,so no reason to panic. :silly:
3.I personally use the Pico package and then just install other Google apps which I need. That is the beauty of Open Gapps,you have several options.
Click to expand...
Click to collapse
Thanks man for fast answer, the flashing will comence in the morning, i need a straight head for this ?
And sa for archive size i did not panic, just been curious because i had AICP on my galaxy s4 and it was half the size...
AICP rom is one of the best out there and it has sooo much customization options that i almost cry with happyness when i saw this post ?
And one more question: do i use ARM or ARM64 version of gapps?

Huawei P9 Lite have to use ARM64

Potato997 said:
Huawei P9 Lite have to use ARM64
Click to expand...
Click to collapse
Yeah,I thought everyone knew that...
Added it as well to the instructions! xD

@The Marionette thanks for this amazing work. There is some possibility that you can support the VNS-L23 variant? It is practically equal to the L31, with the only differences that do not have NFC support, the bands 4G are different and it has 2GB of RAM. Greetings.

Hey @The Marionette,
I flashed the ROM and i got error that data partition could not be mounted and then when i click to boot in to android the phone boots but it ask for password to start android...
What to do?
EDIT: After rebooting recovery the data partition is mounted again and i did a full wipe then flashed rom and gapps again but after boot in to android it ask for password again...

tw1st3d83 said:
Hey @The Marionette,
I flashed the ROM and i got error that data partition could not be mounted and then when i click to boot in to android the phone boots but it ask for password to start android...
What to do?
EDIT: After rebooting recovery the data partition is mounted again and i did a full wipe then flashed rom and gapps again but after boot in to android it ask for password again...
Click to expand...
Click to collapse
Someone on the question and answer thread had the same problem. See if any of his answers helps.
Sent from my Huawei P9 Lite using XDA Labs

oss_mosis said:
@The Marionette thanks for this amazing work. There is some possibility that you can support the VNS-L23 variant? It is practically equal to the L31, with the only differences that do not have NFC support, the bands 4G are different and it has 2GB of RAM. Greetings.
Click to expand...
Click to collapse
I have the L21 variant and it works fine for me. If CM works on your device,AICP will work as well.
tw1st3d83 said:
Hey @The Marionette,
I flashed the ROM and i got error that data partition could not be mounted and then when i click to boot in to android the phone boots but it ask for password to start android...
What to do?
EDIT: After rebooting recovery the data partition is mounted again and i did a full wipe then flashed rom and gapps again but after boot in to android it ask for password again...
Click to expand...
Click to collapse
Did you follow the instructions or did you do it your own way?
Are you coming from stock?
I think everyone needs to be on CM before flashing.
I flashed it exactly like I described and it booted.
The only downside is that the TWRP goes red(thinks the current ROM is stock) and data can't be mounted. I will look into it.
Sent from my VNS-LX1 using Tapatalk

The Marionette said:
I have the L21 variant and it works fine for me. If CM works on your device,AICP will work as well.
Did you follow the instructions or did you do it your own way?
Are you coming from stock?
I think everyone needs to be on CM before flashing.
I flashed it exactly like I described and it booted.
The only downside is that the TWRP goes red(thinks the current ROM is stock) and data can't be mounted. I will look into it.
Sent from my VNS-LX1 using Tapatalk
Click to expand...
Click to collapse
I followed Meticulus instructions first (did all backups and dump) and then i followed your instructions from OP but i come from stock rom, did not try to install Meticulus CM ROM... So now i managed to get past password screen by formating data partition to FAT and then formating it back to ext4 but now when phone boot i get "Decryption unsuccessful" screen and when i click "reset phone" button it reboots in recovery, wipe cache and then boots up back to "Decryption unsuccessful" screen...
I am downloading now Meticulus build to try with that... Will report back soon...
EDIT: I managed to boot AICP!!! By doing this:
First i updated recovery (did not see that Meticulus pushed V2) then i flashed Meticulus CM build but i got "Decryption failed" screen again but this time when i clicked "reset phone" buton the phone just rebooted to TWRP.
Then i did again full harcore wipe and flashed CM with open gapps and the phone booted in to system without problem, from that point i figure that AICP must work now so i rebooted back to TWRP, did another hardcore full wipe, flashed AICP with Open Gapps micro ARM64 version and the phone finaly booted to AICP :happy: :happy: :happy:
Btw i noticed few thing while doing all this... When i first booted CM my SIM card was not recognized but i figured it needs some time to get the signal or wathever but that never hapend and i cheked camera app and in setting of the app i saw that front and back camera was set to full resolution and the photo i took was really in full (13Mpix) resolution... After checking that and few more things i flashed AICP and at first boot my SIM still not working so i figure i will reboot and after second boot the SIM works again but in this ROM front and back camera are set to 2.1mpix (not a problem for me, just saying for ppl to know)...
Now i am going to play with this awesome ROM!
Thanks @The Marionette
EDIT 2: So after few hours of playing with AICP i been forced to go back to stock because my mobile network gone crazy, every 5-10 minutes it disapear and only reboot helps to get connected again and when network disapears the UI get so much lag that is almost unusable...
I can confirm that other things in ROM work as it should, fingerprint, themes, sound bar, navigation bar customization, lcd density, UI animations customizations etc...
Nice work and keep up the good work! ?

So I am running this ROM on my device since yesterday and I really like it. Seems very stable and allows for a lot of modifications.
It drains a lot of battery while listening to music when the device is locked but I also experienced this on the CM ROM.
I am keeping it on my device for now and am looking forward to new updates

Hello @The Marionette,
May I ask you if you plan to update the AICP ROM with the update from CM? Thank you

[OMS7][NOUGAT][7.1.2][obake]XPerience-11.1.2_r29 [NIGHTLY]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XPerience 11.X.X for the Motorola Moto DROID Ultra
Maded by Klozz Jesus AKA TeamMEX
XPerience is a free, community built distribution of Android 7.1.1 (Nougat) which greatly extends the capabilities of your phone.
This project are based on AOSP CAF
Code:
#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.
*/
NOTE: READ this PLS
All required device configs, blobs and kernel source are on my github u know the url
Please don ask for etas
Please don't report same bugs all time
Report with logcat and dmesg
Screenshots representative only
Click to expand...
Click to collapse
Features:
Substratum support
XPerience Updater
NetworkTrafficMetter
Ambient Display with customizations
OMS-N7
Force expanded notifications
Disable inmersive messages
Inmersive recents
Alessa app for kernel tweaking.
XPerience Active Display
Pocket Judge
* Judge if device is in pocket.
* Notify clients callbacks when pocked state changes.
* Start listening when device becomes not interactive.
* Stop listening when device becomes interactive and is NOT in pocket.
policy: introduce pocket lock
fingerprint: disable when device is in pocket
One Hand mode (slide your finger across the navigation bat to switch between the standard and mini screen views(from the center))
App sidebar
WORKING:
Working
Rild
LTE/3G/2G
Bluetooth
MTP
Sensors
Led
Wi-Fi
MUSIC
sounds
Videos
[*] Camera
[*] camcoder
SELinux Enforced
New audio HAL fully working
Mic working.
Not working/ Bugs:
camera
posibility maybe random mic bug like ghost
How to install:
Download zip from Downloads:
Put zip into Internal Storage
Reboot into Recovery like TWRP
Flash zip file XPerience-11.x.x-xxxxxxx-obake.zip
Flash Gaaps
Wipe dalvick-cache and cache
Reboot and config
Reboot Again and enjoy!
Screenshots:
https://lh3.googleusercontent.com/****Wbf15v8tBRMttby0pViCXsGn22HuE5oJ3g9OXbcus2ybc3wnLGVggSXayByZOaShwr9kihLRmpHRvKXsaSwXxACOnkRt=w1366-h768-rw-no
Basketbuild NIGHTLY's
Sourceforge mirror 1
xperience web
MD5:
Google APPS
http://opengapps.org

Changelog in second Post:
Thank you for Donate: (if u want to post ur nick instead of your name send PM)
If you like my work, you can buy me a coffee with your donatives. All donations are appreciated. and this can help me to pay some bills about internet

XDA:DevDB Information
The XPerience Project for Motorola Moto DROID Ultra, ROM for the Motorola Droid Ultra
Contributors
TeamMex
Source Code: https://github.com/XPerience-AOSP-Lollipop/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: unlocked bootloader
Based On: AOSP,CAF
Version Information
Status: Testing
Created 2017-10-01
Last Updated 2017-09-30
Click to expand...
Click to collapse

Reserved

Reserved

Untested some guy asked me if I can port my build N from ghost so here u go
maybe we have the same bugs here like ghost.
please test and report.

What bugs should I expect ? Planning to test it over the weekend.

i wana try it but stuck on kitkat 4.4 su-6-7.7 firmware, any way to root in and unlock its bootloader

First you have to unlock the bootloader, but I think on the latest 4.4.su 6-7.7 isn't possible ...

Still got my droid mini around. Will do some testing for y'all.
Edit: Can't get this to boot. It's stuck on the BL screen and doesn't even reach the rom's boot screen. Using TWRP 2.8.4.0. Is there an updated one for obake?

SnipeR_TT said:
Still got my droid mini around. Will do some testing for y'all.
Edit: Can't get this to boot. It's stuck on the BL screen and doesn't even reach the rom's boot screen. Using TWRP 2.8.4.0. Is there an updated one for obake?
Click to expand...
Click to collapse
Same here with Droid Maxx.

This is awesome.
Do you have chance to fix the non working bits?

s_u_n said:
This is awesome.
Do you have chance to fix the non working bits?
Click to expand...
Click to collapse
Hi, Were you able to get the rom to boot?

s_u_n said:
This is awesome.
Do you have chance to fix the non working bits?
Click to expand...
Click to collapse
it is working for you?
since i dont have the device is hard to me know if it is really working, and yea maybe the camera can't be fixed easy.
cheers.

SnipeR_TT said:
Hi, Were you able to get the rom to boot?
Click to expand...
Click to collapse
I have not tried.
I was hoping I could try once the non working features are working.

Droid mini XT1030, stuck on the bootloader screen.
Can your team fix this?

from following the moto x (ghost) forums (my maxx is currently a ghost in droid clothing running aokp) twrp 3.1.1 is required iirc, due to some new wrinkle that needs support baked in for N. someone would have to port the unofficial one over in the other forum over to us. i can say though, that running ghost firmware, 3.1.1 works great on our devices.
---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------
SnipeR_TT said:
Still got my droid mini around. Will do some testing for y'all.
Edit: Can't get this to boot. It's stuck on the BL screen and doesn't even reach the rom's boot screen. Using TWRP 2.8.4.0. Is there an updated one for obake?
Click to expand...
Click to collapse
westhaking said:
Same here with Droid Maxx.
Click to expand...
Click to collapse
TeamMex said:
it is working for you?
since i dont have the device is hard to me know if it is really working, and yea maybe the camera can't be fixed easy.
cheers.
Click to expand...
Click to collapse
don't we need TWRP >2.8.x to boot N? i ran into this issue a few months ago trying to use the ghost version of this rom. if you can come up with a 3.1.1ish build of twrp for my xt1080m, i'll be happy to test both out.
edit: in fact very interested. i've yet to be able to use my jawbone era earpiece via bluetooth without the connection dropping and phone doing a hard reset. probably highlights one of the few differences in the ultra vs x, if i had to wager a guess. if you have more targeted drivers, in fact i will beg you to let me.
edit 2: i'm good at capturing logcats for devs so they don't have to hear me ramble all the time to figure out wtf i am talking about.

Please don't let this thread die. We have now @tom.etc as a capable tester.

Twrp 3.1.1 for GHOST works on Mini, Maxx, and ULtra
s_u_n said:
Please don't let this thread die. We have now @tom.etc as a capable tester.
Click to expand...
Click to collapse
I got a droid mini for free. It was on an old software version, hadn't been touched in years. I unlocked the bootloader with sunshine and then let it take like 7 system updates until it was up to date, then flashed twrp 2.8.4
I had issues flashing the lineage os 13 unofficial for obake https://forum.xda-developers.com/droid-ultra/development/rom-cyanogenmod-13-obake-t3319958, it was stuck on the lineage boot screen. I was trying to use twrp 2.8.4 because that was the latest version I could find for this device.
As mentioned above, it seems that GHOST (Moto X 2013) software does work on the droid Maxx, Ultra, and Mini Family. I flashed 3.1.1 twrp_ghost from https://forum.xda-developers.com/moto-x/development/twrp-touch-recovery-unofficial-t3309449 on my droid mini and it works.
When I tried to flash Lineage os 13 though, it would fail to flash, saying the firmware file wasn't made for ghost_verizon since I was using the 3.1.1 twrp from ghost, TWRP is under the impression that I am using a different device.
If you open the rom zip using WinRAR, and you can copy the updater-script located at META-INF/com/google/android/updater-script to your desktop, open the file, change 2 instances of "obakem" to "ghost_verizon", save the file, then with WinRAR still open copy the updater-script back into the zip. I flashed the zip in twrp 3.1.1 after doing this and successfully booted into lineage os 13.
I flashed lineage os 14.1 for ghost from here: https://forum.xda-developers.com/moto-x/development/rom-unofficial-lineageos-14-1-t3667515 on my droid mini using the 3.1.1 ghost twrp and lineage os boots! It has on screen buttons for back, home, and recent apps though, the hardware buttons aren't working. Also, as mentioned over there, the camera does not work.
Anyways, sorry for the long explanation. I tried getting this rom to boot in twrp 3.1.1 by updating the updater-script the same way but it didn't work. So there's some other issue causing this rom not to work. If you want nougat just flash twrp 3.1.1 ghost, and lineage os 14.1 for ghost, that worked for me.

smilesinlife said:
i wana try it but stuck on kitkat 4.4 su-6-7.7 firmware, any way to root in and unlock its bootloader
Click to expand...
Click to collapse
try to unlock bootloader in official way https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a if you get bootloader unlock then install custom recovery https://forum.xda-developers.com/droid-ultra/development/twrp-2-8-4-0-droid-mini-ultra-maxx-t3012851 and then flash su zip http://www.supersu.com/download
---------- Post added at 10:53 AM ---------- Previous post was at 10:49 AM ----------
is led notification works on droid mini?

soaking in florida sun for next 2 weeks, but when i get back home to the snow of NJ, i'll give all of this a go and let you know how it all turns out.
---------- Post added at 03:57 PM ---------- Previous post was at 03:50 PM ----------
steven_computer_guy said:
I got a droid mini for free. It was on an old software version, hadn't been touched in years. I unlocked the bootloader with sunshine and then let it take like 7 system updates until it was up to date, then flashed twrp 2.8.4
I had issues flashing the lineage os 13 unofficial for obake https://forum.xda-developers.com/droid-ultra/development/rom-cyanogenmod-13-obake-t3319958, it was stuck on the lineage boot screen. I was trying to use twrp 2.8.4 because that was the latest version I could find for this device.
As mentioned above, it seems that GHOST (Moto X 2013) software does work on the droid Maxx, Ultra, and Mini Family. I flashed 3.1.1 twrp_ghost from https://forum.xda-developers.com/moto-x/development/twrp-touch-recovery-unofficial-t3309449 on my droid mini and it works.
When I tried to flash Lineage os 13 though, it would fail to flash, saying the firmware file wasn't made for ghost_verizon since I was using the 3.1.1 twrp from ghost, TWRP is under the impression that I am using a different device.
If you open the rom zip using WinRAR, and you can copy the updater-script located at META-INF/com/google/android/updater-script to your desktop, open the file, change 2 instances of "obakem" to "ghost_verizon", save the file, then with WinRAR still open copy the updater-script back into the zip. I flashed the zip in twrp 3.1.1 after doing this and successfully booted into lineage os 13.
I flashed lineage os 14.1 for ghost from here: https://forum.xda-developers.com/moto-x/development/rom-unofficial-lineageos-14-1-t3667515 on my droid mini using the 3.1.1 ghost twrp and lineage os boots! It has on screen buttons for back, home, and recent apps though, the hardware buttons aren't working. Also, as mentioned over there, the camera does not work.
Anyways, sorry for the long explanation. I tried getting this rom to boot in twrp 3.1.1 by updating the updater-script the same way but it didn't work. So there's some other issue causing this rom not to work. If you want nougat just flash twrp 3.1.1 ghost, and lineage os 14.1 for ghost, that worked for me.
Click to expand...
Click to collapse
since i have my device already reporting itself as ghost and not obake, i should not have to edit anything then. the recovery and rom should just work, no?
fyi, up through MM, the patch offered in this forum for lollipop has worked swimmingly for activating the capacitve buttons on any ghost rom i've tried. then its usually just a matter of disabling the navbar.

tom.etc said:
soaking in florida sun for next 2 weeks, but when i get back home to the snow of NJ, i'll give all of this a go and let you know how it all turns out.
---------- Post added at 03:57 PM ---------- Previous post was at 03:50 PM ----------
since i have my device already reporting itself as ghost and not obake, i should not have to edit anything then. the recovery and rom should just work, no?
fyi, up through MM, the patch offered in this forum for lollipop has worked swimmingly for activating the capacitve buttons on any ghost rom i've tried. then its usually just a matter of disabling the navbar.
Click to expand...
Click to collapse
Yes. If you have the twrp 3.1.1 for ghost already installed on a Droid Maxx/ultra/mini, you should be able to flash ghost roms without needing to modify them, then flashing the patch you mentioned which does enable the capacitive buttons.

Database Develop

welcome