yashsingh1/xdaforums huggingface dataset:
[Droid Ultra Android Development] pbarrette:
Hi Karsto,

I was on the latest SU6-7.7 release before I updated. I don't know if you absolutely need to update to the latest official, but it can't hurt and it won't re-lock your bootloader. For reference, I accepted all the OTA updates after I unlocked via sunshine.

Don't be too nervous. You're going to have to wipe the phone completely anyway, so take a good backup.

I prefer Titanium Backup Pro because I can restore data to dissimilar ROMs/Phones, but whatever works for you.

Hi s_u_n,

Still no luck on the August updates. The patches still haven't been merged into the LineageOS 13.0 source tree. I don't know why it's taking so long this month. We're about to get September security patches released by Google while LineageOS will be a month behind in the 13.0 branch.

When the updates get merged, I'll build a new release and post here.
[Droid Ultra Android Development] pbarrette:
The August updates were finally merged and I built a new release yesterday evening.

The ROM zips are here.

Note that there are some WLAN changes that were merged in late July for our kernel. I haven't noticed any differences in WiFi connectivity, so I assume the updated code is stable:

https://review.lineageos.org/#/q/pr...rola_ghost+branch:cm-13.0+topic:CVE-2015-0571
[Droid Ultra Android Development] s_u_n:
Awesome.

There are two files (one is with 'root' and the other without); which one should I use for my Droid Maxx?
[Droid Ultra Android Development] .: SID :.:
Many thanks for new builds. What's the difference between root and non-root build? Is it possible to use just Magisk with non-root build?
[Droid Ultra Android Development] pbarrette:
LineageOS, by default, does not have root capability baked in, but a developer can include it via a compile time switch.

I prefer to have the LineageOS native root, but I understand that others may not want it included, so I build the image both ways.

The only difference between the two is that the "root" image has the native LineageOS root baked into the ROM and it can be enabled through the developer options in the Settings menu and the permissions are controlled via the native LineageOS user interfaces.

Other people have used Magisk with other LineageOS ROMs, so I assume that it will work with this one, but I haven't tried it personally.

If you are going to use Magisk, I'd start with the non-root version and use the flashable Magisk zip.
[Droid Ultra Android Development] s_u_n:
Which gapps should I use?
[Droid Ultra Android Development] pbarrette:
Hi s_u_n,

That's up to you. Personally, I use the Stock GApps with a "gapps-config.txt" file to exclude the apps I don't want.

Instructions for that can be found here.
[Droid Ultra Android Development] westhaking:
[MENTION=4782500]pbarrette[/MENTION] Thanks for keeping these updated with the latest security patches for those of us still using this phone but I have a small issue that maybe you can help me with. I read in an earlier reply that you are on Verizon. I am too but I can no longer receive text messages after flashing this. I can make and receive calls and send text but I just can't receive them. Mind to share your mobile network settings (with screenshots maybe)? What is your preferred network type in Phone Information after dialing *#*#4636#*#* What about APN settings? Thanks in advance and hoping you can help.
[Droid Ultra Android Development] pbarrette:
Hi westhaking,

1] Which ROM are you coming from?

I flashed LOS from the last Verizon stock ROM.

Did you do a full wipe before you installed the ROM?

2] Can you send MMS, but not SMS?

SMS but not MMS?

Do you have data working?

3] Screenshots of the test menu are attached.

The second screenshot shows the SMSC number which was populated by hitting the "Refresh" button.

I didn't input that anywhere. It was picked up as part of the standard registration.

4] The APN settings are tricky to get to and seem to be mostly disabled for CDMA phones on LineageOS.

I didn't enter APN info, but you could always try:

Name: Verizon

APN: VZWINTERNET

MMSC: http://mms.vtext.com/servlets/mms

MCC: 311

MNC: 480

APN Type: default,dun,supl

5] Is it possible that you configured this phone as a GSM phone previously?

You may need to change the boot-up carrier mode with "fastboot oem config carrier vzw".

Check "adb shell getprop ro.boot.carrier" and see if it returns "vzw". If not, run the fastboot command.

6] Your Verizon SIM should already have all of the settings you need on it. It could be that you need a new SIM.
[Droid Ultra Android Development] westhaking:
1] I came straight from stock 4.4.4

2] I can send both sms and mms but if I receive any back it is only a single reply then no others show up. I only receive the remaining replies back after a reboot of the phone. After I reboot, all the text,mms that were previous sent (minus a single one) suddenly show up. It's seems that somehow after I get the first sms back that something (service?) is being killed and is only restarted after a reboot which then allow all backlogged sms to go through.

3] I flashed back to stock to look and the settings there and they are definitely different between stock and LOS13. The attached photos show comparisons of the #*#*4636*#*# settings (stock of the left/LOS on the right). The Set preferred network type available in stock is different than what shows up in LOS13. In fact, the LTE/CDMA/EvDo/GSM/WCDMA network type doesn't even show up on this page under LOS13. The SMSC was initially blank but I hit refresh and the same number showed up for me.

4] The settings you listed show up under the APN settings page for VZWINTERNET on LOS13 (I was able to get there through an app on the app store), but what shows up on Stock 4.4.4 is:

Name: Verizon

APN: VZWINTERNET

MMSC: http://mms.vtext.com/servlets/mms

MCC: 311

MNC: 480

APN Type: default,dun,stdhipri,supl

The difference is the addition of stdhipri in the APN type on stock.

5] The phone is provisioned for vzw as indicated by 'adb shell getprop ro.boot.carrier'

6] Went to Verizon yesterday and got a new SIM card and still no luck :(

Any ideas? Do you know what would allow only one sms to come through until a reboot is performed?
[Droid Ultra Android Development] pbarrette:
If you send me a logcat showing the behavior, I can try to take a look at it to see if something is getting killed.

The options are the same. They just appear different in LOS. If the SMSC is good, you should be able to send and receive correctly.

This shouldn't cause any problems. The absence of a HIPRI type is basically overridden by the presence of "default".

1] It could be a modem initialization issue.

Do you get proper GPS location data?

I had to erase modemst1 and modemst2 to get GPS working correctly, so there may be a modem cache problem:

fastboot erase modemst1

fastboot erase modemst2

2] Instead of rebooting, have you tried toggling airplane mode?

Also, is WiFi off when you're receiving SMS's?

3] What's your baseband in "About Phone"?

Mine is MSM8960PRO_BP_23255.132.81.03R
[Droid Ultra Android Development] westhaking:
I will see about getting a logcat. Never done it so I will need to read up on it.

I had previously run these commands. GPS seems to be working fine.

Toggling airplane mode makes no difference. Wifi is usually on.

I have MSM8960PRO_BP_23255.132.81.01R. I thought I had the latest with ...81.01R. Where did you get ...81.03R? Are you able to share it by chance?
[Droid Ultra Android Development] dDefy:
No Sound for incoming calls

I'm glad to see that this topic is still alive.

Installed both notz and pbarrette ROM's and they added a new life to my Droid Mini.

The only thing that is not working is that on incoming calls I don't have any sound nor the caller can hear me, the interesting part is that if I call them back all works as it should.

Any fix to this or what possibly could I've done wrong ?

Thanks, David
[Droid Ultra Android Development] pbarrette:
Hi Westhaking,

The .03R baseband came with the last official update: SU6-7.7, while .01R is usually associated with the SU6-7.3 update.

Edit: To get a logcat, do a reboot and reproduce the behavior, then run the command:

adb shell logcat -d -b all > logcat.log

Hi David,

I haven't heard of this problem before. Before you flashed LOS were you on the latest official ROM (SU6-7.7)?
[Droid Ultra Android Development] dDefy:
I've had the 5.1.1 ASOP from notz, now I'm back on that.

Cleaned up all the mess, and pushed them trough TWRP, but still nothing.
[Droid Ultra Android Development] pbarrette:
All,

The September 2017 security patches have been released and I compiled a new ROM.

I am not going to release it at this time because the merged code completely breaks SSL certificate validations.

This means that virtually all applications and services that rely on internet functions are crashing.

I will keep tracking this and post an update when the issue is corrected.
[Droid Ultra Android Development] dDefy:
Still no idea what have could be wrong, I'm open to any ideas.

Thank you
[Droid Ultra Android Development] pbarrette:
Hi David,

1] Which bootloader and baseband are you on?

2] What was the last official firmware version your phone was on?

3] Did you do a clean install of LOS 13 or are you trying to install over CM-12?

By clean install, I mean:

a] Wipe of System, Cache, Dalvik Cache, Data, Internal Storage.

b] adb push of "lineage-13.0-20170901-UNOFFICIAL-obake[-root].zip" to /sdcard

c] Optional adb push of your GApps to /sdcard.

d] Install the ROM

e] Optional install of GApps.

(I use a USB stick instead of "adb push", same thing).

4] Which dialer are you using? The LOS dialer or a Google dialer from your GApps?

If it's the GApps phone, which version of GApps did you install?

5] Does speakerphone work, bluetooth? Does the mic work if you switch between speakerphone or bluetooth? How about a wired headset?

The thing is, you're not really giving us any information to work with, other than "It doesn't work", so we don't really know what to tell you.

I've also got the Droid Mini, so I know that it can work.
[Droid Ultra Android Development] westhaking:
My texting issue are resolved now. I've updated my radio to MSM8960PRO_BP_23255.140.93.00R found in the stock 5.1 Moto X rom. I've been on a journey since my last post that involved lots of reading and running Moto X roms but now I'm back again with a newer and better radio baseband! Looking forward to the newest September patches....
[Droid Ultra Android Development] pbarrette:
Excellent!

Moto X (2013 version) are a good place to look because the obake (Ultra, Mini, Maxx) platform uses the ghost (Moto X) kernel.
[Droid Ultra Android Development] dDefy:
1. I don't know, using TWRP 2.8.4.0, baseband MSM8960PRO_BP_2323.011.75.00R

2. The last one was [ROM][5.1.1_r8][23/7/15] AOSP by notz

3. I've tried wipeing and formating before pushing using adb the lineage and the gapps images.

4. Have tried the LOS and Google's dialer too, using the open_gapps-arm-6.0-pico-20170918.

5. Yes, both the speakerphone and bluetooth works when I'm making the call, but when I get an incomming nothing works. Have to call them back :)

Thank you for your patience and asking the questions I never tought about.
[Droid Ultra Android Development] pbarrette:
This is likely your problem. That modem firmware seems to be associated with the original official 4.2.2 firmware.

Also, AOSP is not an official, Motorola firmware. I was asking which official, from the manufacturer, firmware version you had installed.

You should probably flash the last official firmware version to ensure you're on a current bootloader and baseband.

Instructions to flash stock firmware:

https://xdaforums.com/showthread.php?t=2580060

Stock firmware image:

https://firmware.center/firmware/Motorola/Droid Mini (XT1030)/Stock/

You want: CFC_obakem_verizon-user-4.4.4-SU6-7.7-release-keys.xml.zip

Flash that and boot up at least once to ensure the modem gets initialized.

Then you can go back to fastboot and flash TWRP.

Finally, from TWRP, flash LOS and your GApps.
[Droid Ultra Android Development] dDefy:
Thank you for your answer, will try this.
[Droid Ultra Android Development] otmitia:
Hi pbararette, there was a new build lineage-13.0-20170923-nightly-ghost-signed.zip and in it ASB September 2017, version string to 2017-09-01. Make us a new build?))
[Droid Ultra Android Development] dDefy:
It really works, after I did all the steps.

Thank you pbararette, made my day !
[Droid Ultra Android Development] pbarrette:
Hi otmitia,

As you can see from my post above, I delayed a release because of problems introduced with code changes to SSL found in this merge:

https://review.lineageos.org/#/c/181332/

I was able to build a new version yesterday that reverts the code change and it has been working for me, but there is no official merged fix in the Lineage OS github tree. I have uploaded new images with the September security fixes, but it's not a mainline image because of the code revert that has to be manually applied.

Do you know anyone who is running the 20170923 image for ghost (Moto X)? I suspect they will have the same SSL problems I did. Those problems include all Google apps crashing, to include Chrome, crashes of all email clients, etc.

Working ROMs for obake (lineage-13.0-20170922-UNOFFICIAL), both with and without root, can be found at the usual AndroidFileHost location below:

https://www.androidfilehost.com/?w=files&flid=194742
[Droid Ultra Android Development] dDefy:
Saw that you've made a new build, any new things in ?

[ sorry, way to impatient :), saw your post above ]
[Droid Ultra Android Development] otmitia:
I do not know, at 4pda.ru everything is quiet, well, probably correct, soon)

Thanks for the release, let's hope for a quick fix!)
[Droid Ultra Android Development] smilesinlife:
i wana try it but stuck on kitkat 4.4 su-6-7.7 firmware, any way to root in and unlock its bootloader:confused:
[Droid Ultra Android Development] mushbert:
The short answer is no. Root can be obtained but you cannot write to the system partition without an unlocked bootloader. The only current way to unlock is using Sunshine (available at http://theroot.ninja), which works with phones running 4.2 through early 4.4. You can try it if you want to satisfy your curiosity though.
[Droid Ultra Android Development] pbarrette:
Hi Everyone,

The October security updates have been merged in Lineage and I have compiled a new ROM found here:

https://androidfilehost.com/?w=files&flid=194742

There are a couple items to note:

1] This bumps Android to 6.0.1_r80 which is MOB31Z.

2] The SSL problems are gone after I destroyed and re-created my development VM. So the earlier problem was on me.

3] I changed the start-point of the "obake_thermal" service from "on property:init.svc.bootanim=stopped" to "on post-fs" to get the thermal control in place earlier.

- This should help some with heating after installing a ROM update.

- The github project has also been updated.

4] Immediately after I installed the ROM yesterday, I had to re-select my SIM card and my radio started crashing. A reboot fixed the issue.
[Droid Ultra Android Development] pbarrette:
All,

I have purchased a Sony Xperia XZ1 Compact and moved from Verizon to T-Mobile.

It's barely larger than the Droid Mini, has a modern CPU, launched with Oreo and supports T-Mobile US's VoLTE and WiFi calling, so I couldn't justify using the Droid Mini as my daily phone any more.

As such, I can no longer do any "soak" testing of compiled ROMs and plan on pushing a final ROM update with the December 2017 security updates (whenever those are merged into the LOS-13 code tree). So, basically, two more ROMs that I can't really test before releasing to you guys.

I'm also willing to walk anyone through the procedure of setting up a build environment if they wish to continue supporting the obake line.

My build environment is a Ubuntu virtual machine with 128GB of storage running on Hyper-V on a Windows 10 laptop. Not the fastest build system, but it's fairly simple to set up if you've got a little experience with linux.

You may have noticed that shortly before the last ROM release, I added a "proprietary_vendor_motorola" repo (forked and cleaned up from TheMuppets) to my github that contains the proprietary motorola binaries and firmware. This was in an effort to streamline the build process and make it as simple as possible. Hopefully, if someone decides to continue support, it will make the process easier for them.

I will update my github with my "local_manifests" repo before I stop support. It basically changes the build sources for "obake" from the out-of-date LineageOS official github repo to mine, and downloads the vendor blobs so you don't have to do an initial "adb pull" from a working phone to get them.
[Droid Ultra Android Development] dDefy:
Hi pbarrette,

Good luck with your new phone, it is a decent update from the Droid Mini, altoough I'm missing the wireless charging on.
[Droid Ultra Android Development] SnipeR_TT:
pbarrette,

Thank you for your contribution to our devices! I've moved on to another phone a while now, but it's because of you that I still can use my Mini as a backup.
[Droid Ultra Android Development] otmitia:
Hi pibarrette, I want to express my gratitude in supporting the device, I also went to another motorola, Moto X Force))
[Droid Ultra Android Development] dDefy:
I'm still with my Droid Mini :)
[Droid Ultra Android Development] pbarrette:
One thing you could try is flashing the modem from the latest Moto-X (2013) model, codename "ghost".

Essentially, the phones have the same processor and modem hardware. Also, the LineageOS kernel and support libraries for our phone (obake) are the same as that for the ghost platform. In fact, to support obake originally, it looks like they had to split off a portion of the

android_device_motorola_ghost

repo into the

android_device_motorola_msm8960dt-common

repo and have both ghost and obake point to the common repo. So the whole LOS port started with ghost.

I don't think there's anyone left who really supports obake, but there are a couple who are still working on the Moto-X and sometimes they still contribute upstream to the LOS repositories.

So there's a chance that the modem from "XT1060_GHOST_VERIZON_5.1_LPAS23.12-39.7-1_cid2_CFC" will be more compatible with what LineageOS expects from it.

Essentially, you'd need to flash the

NON-HLOS.bin

file, clear modemst1 & 2 and flash the

fsg.mbn

file from the ghost firmware.

The ghost firmware's

fsg.mbn

file contains modem config binaries for ghost, obake, obakem (the Mini) and obake_maxx (the Maxx). I assume that because it's the same platform, Motorola just compiled it all together and bundled it all together without regard to which phone the stuff was going into. There's also a "sasquatch" modem in there, but I don't know what phone that is.

As far as someone adding nefarious bits to the CFC firmware.. I suppose it's possible, but it would take a lot of work to bypass the Moto signed binaries and tamper checks. If someone could do that, they'd probably be selling a post 4.2 bootloader unlock instead. Or a simple to use root method for locked bootloaders, because these images can be installed on phones that still have the bootloader locked. So you'll just have to take it on faith, basically.

I mean, you installed LineageOS provided by some random idiot on the internet (me) on the faith that I haven't planted anything nefarious in there.

If it is a concern, then you should compile your own LOS build from source. But then you'll need to verify that nobody has planted malicious code in the LOS repos, so it's really just turtles all the way down at some point.

Question to everyone following this thread:

Is anyone else having reboots during calls?
[Droid Ultra Android Development] GeneralSchnook:
Thanks for the reply. Based on what you said, are you sure you didn't add a little extra something to your lineage build ;)? I'm just messing with you :P

Tried completely restoring to stock via the CFC file for my model, so I know I was starting with a clean phone. Still encountered the same problem, even without flashing GAPPS (only lineage).

I also tried it with a different bluetooth handsfree device (my Bose speaker), and the same error was present. Although sometimes it doesn't reboot the phone it seems, but it sure takes a while for the dialer to end the call (and then usually reboots).

Important to note that I don't have any issues if no handsfree/headset/phone bluetooth devices are connected.

I also followed your suggestion and tried with the MOTO X modem and fsg, but it didn't change anything.

Took a closer look at the logcat, (and even compared the output to a normal non-bluetooth call), but it basically just told me that bluetooth messed up and then the phone rebooted. Wasn't very helpful.
[Droid Ultra Android Development] pbarrette:
The reboot reason would probably be caught in the kernel messages.

You could try something like this while starting a call:

adb shell cat /proc/kmesg

That should dump the kernel messages continuously, so you'll catch the problem as it occurs.

Another one is:

adb shell logcat -b all

Logcat only reports the "main", "system" and "crash" buffers by default, but there are also "radio" and "events" buffers that can be reported.
[Droid Ultra Android Development] GeneralSchnook:
logcat -b all is pretty neat, able to see a lot more messages.

In particular, a whole bunch of underflow messages inside a bluetooth module:

10-22 17:11:43.125 13452 13488 E bt_btif : ## Audio Congestion (iterations:4 > max (3))
10-22 17:11:43.135 13452 13488 W bt_btif : ### UNDERFLOW :: ONLY READ 0 BYTES OUT OF 512 ###
10-22 17:11:43.135 13452 13488 W bt_btif : btif_media_aa_prep_sbc_2_send underflow 9, 0
10-22 17:11:43.149 13452 13488 W bt_btif : ### UNDERFLOW :: ONLY READ 0 BYTES OUT OF 512 ###
10-22 17:11:43.149 13452 13488 W bt_btif : btif_media_aa_prep_sbc_2_send underflow 9, 0
10-22 17:11:43.159 13452 13488 W bt_btif : ### UNDERFLOW :: ONLY READ 0 BYTES OUT OF 512 ###
10-22 17:11:43.159 13452 13488 W bt_btif : btif_media_aa_prep_sbc_2_send underflow 9, 0

These messages repeat a fair amount, then it looks like something tries to suspend BT:

10-22 17:11:43.472 13452 13477 D bt_btif : AV Sevent(0x41)=0x1223(STR_SUSPEND_CFM) state=3(OPEN)
10-22 17:11:43.472 13452 13477 E bt_btif : bta_av_suspend_cfm: suspend failed, closing connection
10-22 17:11:43.473 13452 13477 D bt_btif : AV Sevent(0x41)=0x120a(API_CLOSE) state=3(OPEN)
10-22 17:11:43.473 13452 13477 W bt_avp : avdt_scb_snd_stream_close c:0, off:0
10-22 17:11:43.473 13452 13477 W bt_btif : bta_dm_rm_cback:1, status:6
10-22 17:11:43.474 13452 13472 D bt_btif : btif_av_state_started_handler event:BTA_AV_SUSPEND_EVT flags 1 index =0
10-22 17:11:43.474 13452 13472 D bt_btif : ## ON A2DP SUSPENDED ##
10-22 17:11:43.474 13452 13472 D bt_btif : ## a2dp ack : A2DP_CTRL_CMD_SUSPEND, status 1 ##
10-22 17:11:43.474 4134 14349 I bt_a2dp_hw: a2dp_command: A2DP COMMAND A2DP_CTRL_CMD_SUSPEND DONE STATUS 1

After that, looks like something is trying to close bluetooth, followed by a whole bunch of these messages:

10-22 17:11:43.532 13452 13488 E bt_btif : ERROR Media task Scheduled after Suspend

The reboot seems to happen because of something making the watchdog timer angry:

10-22 17:12:47.539 4450 5055 I Watchdog_N: dumpKernelStacks
10-22 17:12:47.652 4450 5055 E Watchdog: Triggering SysRq for system_server watchdog
...
10-22 17:12:47.705 4450 5055 W Watchdog: *** WATCHDOG KILLING SYSTEM PROCESS: Blocked in handler on main thread (main)

---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------

Well, I actually need to use my phone without this nonsense, so I am going back to stock for now...
[Droid Ultra Android Development] pbarrette:
Have you seen otmitia's post here:

https://xdaforums.com/showpost.php?p=72892345&postcount=283

You may have to disable A2DP for your bluetooth device and use the headset profile instead.