[CM11][Official] Cyanogenmod Support Dropped

[Topsnake]

Had an issue sending MMS. Anyone encounter that?

Sent from my XT1080 using Tapatalk

 

[Rottgrub]

Had an issue sending MMS. Anyone encounter that?

May not be apples to apples, but with T-Mobile SIM and config, no problems with MMS at all. Is it throwing an error, or does the MMS just not arrive?

 

[Jaocagomez]

Had an issue sending MMS. Anyone encounter that?

Sent from my XT1080 using Tapatalk

I think you use a non Verizon SIM in i it

May not be apples to apples, but with T-Mobile SIM and config, no problems with MMS at all. Is it throwing an error, or does the MMS just not arrive?

I think it's the lte mms bug, happens to us all


Sent from my XT1080 using XDA Premium 4 mobile app

 

[Topsnake]

I think you use a non Verizon SIM in i it






I think it's the lte mms bug, happens to us all


Sent from my XT1080 using XDA Premium 4 mobile app

No, not that. It was an issue regarding APNs. It would error out. The phone has a VZW sim

Droid Maxx "Developer Edition"

 

[Rottgrub]

Ugh, fairly large bug. Not sure how I didn't notice it before, but there is no external speaker audio at all on the Droid Mini.

In Call audio works, as does all audio to headphones. However the external speaker is completely silent. Time to put in a bug report to CM.

Bleh...

 

[Jaocagomez]

Ugh, fairly large bug. Not sure how I didn't notice it before, but there is no external speaker audio at all on the Droid Mini.

In Call audio works, as does all audio to headphones. However the external speaker is completely silent. Time to put in a bug report to CM.

Bleh...

I recall that the sound name on that device was different than obake and obakem, should be an easy fix, just including the name of your device in the correct path

Sent from my XT1080 using XDA Premium 4 mobile app

 

[mainbord]

Motorola droid mini. Last build. First look.

Speaker phone don,t work.
Russia beeline 2g and 3g works well, but in status panel -120dbm signal strength.
If you want to disable software buttons add line in build.prop
qemu.hw.mainkeys=1

led cgarge and noification don't work.

 

[Rottgrub]

I recall that the sound name on that device was different than obake and obakem, should be an easy fix, just including the name of your device in the correct path

If there is any information, logcats, etc that I can provide to help with supporting the XT1030, just let me know. Thanks!

 

[Jaocagomez]

If there is any information, logcats, etc that I can provide to help with supporting the XT1030, just let me know. Thanks!

i think i found the post related to the sound issues on kitkat on droid devices
http://forum.xda-developers.com/showpost.php?p=48054637&postcount=276
i think you can fix this by yourself by going to root folder system/lib and renaming libacdbdata_obake-maxx.so to libacdbdata_obakem.so
then sound should work

 

[Rottgrub]

i think i found the post related to the sound issues on kitkat on droid devices
http://forum.xda-developers.com/showpost.php?p=48054637&postcount=276
i think you can fix this by yourself by going to root folder system/lib and renaming libacdbdata_obake-maxx.so to libacdbdata_obakem.so
then sound should work

Even better. I'll give it a shot and report back.

 

[Jaocagomez]

About the Moto X compatibility on KitKat, there are further differences between MAXX and Moto X (the audio, (in-call speaker volume), giving me hard time on when nailing CM-10.2 now). Mostly configuration files, just 2 libraries (libaudcal.so and libacdbdata.so, use libacdbdata_obake-maxx.so and rename it - for some reason, audio files are different between Droid Mini (obakem) / Ultra (no suffix) / MAXX (obake-maxx); the version is in stock firmware determined by "ro.audio.init".

I would get why Droid Mini has different files, but not really getting where the difference for Ultra / MAXX comes from.

the one on active development on CM its: @Skrilax_CZ so lets see if he can incorporte droid mini sound working to cm11

 

[Rottgrub]

the one on active development on CM its: @Skrilax_CZ so lets see if he can incorporte droid mini sound working to cm11

Digging through the nightly zip, I am not seeing those files. However, I did find them in the 4.2.2 image on my phone currently. I've also found a directory "/system/xt1080" that contains libacdbdata.so, among other things... and a section in the update script like below:

ifelse(is_substring("obake-maxx", getprop("ro.boot.device")), run_program("/sbin/sh", "-c", "busybox cp -R /system/xt1080/* /system/"));
delete_recursive("/system/xt1080");

Looks like it's checking the model here, and overriding some of the Ultra specific files with Maxx files at install time.

I'm going to play around with this a little, but I'm guessing that specific "obakem" files aren't being built currently. Likely due to there being no way to test them until now.

UPDATE: Tried plugging in the files from the xt1080 directory, but no luck. I'm guessing this will need to be addressed at the source level. I think we are just missing needed support modules and libraries for the xt1030.

 

[nimdae]

The package appears to be built to support all of the lineup that uses this base hardware, but there are minute differences, enough to require their own libraries.

I'm guessing we'll need to get the binaries from the xt1030 stock package, or see if we can get the source from Motorola, or something.

I have CM11 on my Mini now so I'm prefectly willing to provide testing feedback for getting this working.

 

[Rottgrub]

Also probably worth noting, I've had trouble doing restores through TWRP on the Mini. I've since switched to CWM, but have not tried a restore.

Sent from my XT1030 using Tapatalk

 

[nimdae]

Since I'm running a nightly build, I'll go ahead and throw in some observations of issues. Some of these will already be known, and as they get fixed, I'll note that for confirmation.

• LED Indicator doesn't work
• No sound from external speaker (all other sound appears to work)
• Defaults to software nav bar, duplicating hardware nav bar
• Some app stability issues (infrequent crashes)
• Battery stats info doesn't completely work (wakelock detector seems to see app wakelocks, but can't see statistics)
• NFC payment possibly doesn't work (this may or may not be an issue as I had literally just set it up and tried it wtihout verifying my NFC config first, but NFC was on and wallet was enabled, more testing needed)
• USB OTG seems to only be semi-functional. I'm able to mount a device, format it, etc, but I can't seem to copy files to it.

Still testing various things as I can. Performance seems good. Battery life seems good. Overall, I'm happier with this than I was with stock.

 

[Skrilax_CZ]

The unified build doesn't have xt1030 support atm. (model doesn't get detected properly, no sound due to lack of specific files (audcal, abdcdata etc.), probably LCD density). Since there was no dev. edition I didn't bother with it before.

LED indicator right now works only if USB is plugged (dunno atm if that's a HW limitation or due to SW - too lazy). Still some issues with Droid MAXX (video camera resolution, audio issues (voice speaker mute in-call, earpiece works fine) etc.

 

[mainbord]

The unified build doesn't have xt1030 support atm. (model doesn't get detected properly, no sound due to lack of specific files (audcal, abdcdata etc.), probably LCD density). Since there was no dev. edition I didn't bother with it before.

Please add droid mini. Now we can unlock bootloader on all consumor versions on droid maxx mini and ultra.
http://forum.xda-developers.com/showthread.php?t=2679190
And turn off software buttons please.

 

[nimdae]

The unified build doesn't have xt1030 support atm. (model doesn't get detected properly, no sound due to lack of specific files (audcal, abdcdata etc.), probably LCD density). Since there was no dev. edition I didn't bother with it before.

LED indicator right now works only if USB is plugged (dunno atm if that's a HW limitation or due to SW - too lazy). Still some issues with Droid MAXX (video camera resolution, audio issues (voice speaker mute in-call, earpiece works fine) etc.

I definitely understand the lack of resources, etc, to support the Mini/xt1030. I'm pretty technically savvy (systems engineer/architect for some years, recently changed my IT career path for something more specialized) so if there's anything you need from me to help with this, let me know. I mostly don't jump into hacking things because of time constraints.

 

[mainbord]

nimdae
https://github.com
https://source.android.com/
http://sourceforge.net/projects/ultra.motorola/files/XT1080-XT1030/
https://github.com/CyanogenMod/android_device_motorola_moto_msm8960
https://github.com/CyanogenMod/android_device_motorola_moto_msm8960dt
https://github.com/CyanogenMod/android_device_motorola_falcon
You can help at any time

 

[nimdae]

nimdae
...
You can help at any time

... I mostly don't jump into hacking things because of time constraints.

I would love to get my hands dirty with this, but it's really hard for me to add this with all of the things I'm already juggling. The testing and tweaking I'm able to do is pretty much in the little gaps in free time that I get.