[MOD] 2013 Droid Ultra Family Ghost Patch (obsolete)

[rshakin]

Yeah thanks I will try that.

Sent from my XT1080 using XDA Free mobile app

 

[corebore]

New blobs in first post. Should address weird button lights in old package with CM11. GPS seems to work for me with today's nightly, though I only tested it very briefly.

Cheers!

Did you have device only enabled?

 

[Skrilax_CZ]

How many of you are using CM with XT1030 (Droid Mini) and XT1080 (Droid Ultra)? I'm intending to put back official support with CM12, properly supporting all three variants (display + audio differences).

 

[nubia11]

How many of you are using CM with XT1030 (Droid Mini) and XT1080 (Droid Ultra)? I'm intending to put back official support with CM12, properly supporting all three variants (display + audio differences).

Yes please please do! I'm thrilled to hear this,! Thank you very much!

Sent from my XT1080 using Tapatalk

 

[Rottgrub]

How many of you are using CM with XT1030 (Droid Mini) and XT1080 (Droid Ultra)? I'm intending to put back official support with CM12, properly supporting all three variants (display + audio differences).

Official support for xt1030 and xt1080 would be fantastic. There seem to be a few hundred people trying out these patches, which is only a fraction of people who'd use an official version.

Let me know if there is anything you'd need from the xt1030 for development.

Cheers!

 

[nubia11]

I will do anything I can to help out also, please let me know

Sent from my XT1080 using Tapatalk

 

[rob0809]

How many of you are using CM with XT1030 (Droid Mini) and XT1080 (Droid Ultra)? I'm intending to put back official support with CM12, properly supporting all three variants (display + audio differences).

I would be very happy to see the Maxx (XT1080) supported on CM12. I've used your work on my Acer A500, thank you for all you do!

 

[ad fu]

How many of you are using CM with XT1030 (Droid Mini) and XT1080 (Droid Ultra)? I'm intending to put back official support with CM12, properly supporting all three variants (display + audio differences).

That would be awesome!!!!!

 

[nubia11]

Any word?


Sent from my XT1080 using Tapatalk

 

[Rottgrub]

Any word?

Sent from my XT1080 using Tapatalk

It's been less than 24 hours, and you've replied three times. You really need to dial that back.

Also, per XDA rules, don't ask for ETAs or updates.

 

[Skrilax_CZ]

Actually I'd be fine just with build.prop from XT1030 and XT1080 (not Droid MAXX, I have that one) so I don't have to download whole two firmwares

Moto X is getting CM12 nightlies (stuff works), so it shouldn't take long to get Droid Mini / Ultra / MAXX on the line.

 

[nubia11]

I may have the ultra build.prop on my laptop at home if you need. Let me know. Rottrob sorry If I honked you off. I've never been one to ask for eta or updates I know how much work people put into this. I just wanted to help if I could.... Again, I apologize....

Sent from my XT1080 using Tapatalk

 

[Rottgrub]

Actually I'd be fine just with build.prop from XT1030 and XT1080 (not Droid MAXX, I have that one) so I don't have to download whole two firmwares

Moto X is getting CM12 nightlies (stuff works), so it shouldn't take long to get Droid Mini / Ultra / MAXX on the line.

Sounds great to me. =) These patches were a stop-gap measure, and a pain in the butt.

I've attached the XT1030 build.prop from the latest firmware I have. It appears to be correct in the XML:

phone_model model="ULTRAM_CFC_VZW"
software_version version="obakem_verizon-user 4.4.4 SU5-24 24 release-keysMSM8960PRO_BP_23255.127.76.00R"​

But has these entries:

ro.product.model=XT1080
ro.product.name=obake_verizon
ro.product.device=obake​

Checking the phone, getprop reports the correct properties (XT1030, obakem_verizon, and obakem). Not conclusive, but there may only be one build prop for the two devices.
Let me know if you need anything else. I am not using the Droid Mini as my daily driver, so anything you need is fair game.

Cheers!

 

[Rottgrub]

I may have the ultra build.prop on my laptop at home if you need. Let me know. Rottrob sorry If I honked you off. I've never been one to ask for eta or updates I know how much work people put into this. I just wanted to help if I could.... Again, I apologize....

Don't sweat it, man. I'm not mad. Just concerned that lots of posts without real content can quickly hide important posts, like Skrilax_CZ's post about re-adding support for CM. A few pages of "WHEN?!?!" and "Me too!" posts, and suddenly other Droid users, who would love to know about possible CM12 Official support, never see it.

It's also never a good idea to badger Devs. =)

If you really need to express your excitement, start a new post in the General section to speculate about CM12 and squee to your hearts content. =)

Cheers!

 

[Skrilax_CZ]

Sounds great to me. =) These patches were a stop-gap measure, and a pain in the butt.

I've attached the XT1030 build.prop from the latest firmware I have. It appears to be correct in the XML:

phone_model model="ULTRAM_CFC_VZW"
software_version version="obakem_verizon-user 4.4.4 SU5-24 24 release-keysMSM8960PRO_BP_23255.127.76.00R"​

But has these entries:

ro.product.model=XT1080
ro.product.name=obake_verizon
ro.product.device=obake​

Checking the phone, getprop reports the correct properties (XT1030, obakem_verizon, and obakem). Not conclusive, but there may only be one build prop for the two devices.
Let me know if you need anything else. I am not using the Droid Mini as my daily driver, so anything you need is fair game.

Cheers!

Ah I see, they hacked it in the init.rc scripts (init.obakem.rc / init.obake-maxx.rc etc.). So however, if you look on description (getprop ro.build.description), you still should get "obake_verizon-user 4.4.4 SU5-24 24 release-keys" and for fingerprint (getprop ro.build.fingerprint) it is "motorola/obake_verizon/obake:4.4.4/SU5-24/24:user/release-keys".

 

[mattvirus]

I'm running the 1/5 ghost nightly on a droid maxx, unlocked bootloader...latest blob patch from the 1st post in this thread...

phone runs great, boots up with 4G LTE data working but voice is "out of service". If I use Advanced signal status and force it to LTE/CDMA auto PRL, voice goes in service and all is well. Unfortunately, i have to do this on every boot. Anyone else have this problem?

 

[Skrilax_CZ]

I booted up first CM12 obake build, but ended up with crashing gapps and phone causing a soft-reboot for cca. 4 times before stabilizing (not sure if I screwed up or it's in current cm12 itself). Let's see what comes our tomorrow.

 

[Rottgrub]

I booted up first CM12 obake build, but ended up with crashing gapps and phone causing a soft-reboot for cca. 4 times before stabilizing (not sure if I screwed up or it's in current cm12 itself). Let's see what comes our tomorrow.

I've seen some weird behavior with recent CM12 builds caused by certain Gapps packages (PA full, and some CM versions). I've been using Banks 2014/12/14 minimal install for other devices without problem.

Once you get it to the point you are happy with it, let me know. I'll be happy to test functionality on my Mini.

 

[corebore]

I'm running the 1/5 ghost nightly on a droid maxx, unlocked bootloader...latest blob patch from the 1st post in this thread...

phone runs great, boots up with 4G LTE data working but voice is "out of service". If I use Advanced signal status and force it to LTE/CDMA auto PRL, voice goes in service and all is well. Unfortunately, i have to do this on every boot. Anyone else have this problem?

What is your carrier? Because I'm on Verizon with my mini and I have no problems like that. I wonder if there is any build.prop that would make that stick? I think on gravitybox that smart radio has a normal network mode that you can set that might stick.

 

[mattvirus]

What is your carrier? ......

I'm on verizon. I'll have to look into gravitybox. thanks!