Develop Bugs

[Q] Random reboots and frustrating boot loops

Hey all,
I've been having boot-loop problems for almost a month now. The phone just abruptly reboots and goes into a boot loop with just the HTC screen. The problem is fixed temporarily if I remove the battery for a while and then power it back up. If I start having too many things going on, such as several tabs in DolphinHD, downloading several updates, etc. [no gaming at all] it'll do the same thing and just reboot.
I was running Cyanogen 6 [stable] with Kingxkernel #2. I was not overclocked, but did have a few setcpu profiles active. I've tried everything imaginable since they began:
-Tried a different kernel [SNAP], didn't work
-Truned off setcpu, didn't work
Today, I got fed up with everything and then decided to flash a Sense ROM hoping that that would fix everything. I flashed the latest Fresh and after the install, even before I could skip all the set-up stuff, the phone started to reboot again.
As for the Fresh installation, I wiped fully including dalvik and cache all in RA.
I'm about to go crazy. I wan't my fully functioning phone back. Please help
EDIT: Also, I forgot to mention that around the same time the random reboots and bootloops began I got a new battery. It was the one from Best Buy made by Seido. Idk if that would affect anything seeing as I get the same problems with both batteries.

if i was you i would do all the following:
1. titanium backup all your apps...
2. flash clockwork recovery
3. nandroid backup everything
4. wipe /system
5. wipe /data
6. wipe /boot
7. wipe /cache
8. wipe /dalvik
9. install rom of your choice
10. run it for a few hours and push it as hard as you can to cause a reboot
- if it reboots -> plug into computer load up terminal/command prompt do adb logcat (copy and paste where and why it reboots)
- if it doesn't reboot -> start reinstalling your apps one at a time or in batches until you find the culprit (unlikely since most installed apps should only cause a force close rather than a reboot but still worth a shot)
11. post back with your findings... ?
fyi the nightly builds seem more stable than the stable build ever was... at least to me on my evo it was...

Thanks for the reply.
I'm going to try that to see what happens. I'll post asap.

Alright, I flashed Clockwork as you said and wiped/formatted everything you mentioned. After that, I flashed Fresh. Everything went well until it went through it's first routine reboot after flash; I didn't even get to pull down the lockscreen into activation before it randomly rebooted. I did a logcat on the first reboot. This is a little piece of the last part of that:
V/libgps ( 292): DeferredActionThread pthread_cond_wait returned
V/libgps ( 292): PA event: 0x00000040
V/libgps ( 292): PDSM_PA_EVENT_GPS_LOCK 0
D/dalvikvm( 292): GC_FOR_MALLOC freed 618 objects / 115992 bytes in 145ms
I/ActivityThread( 674): Publishing provider com.htc.dcs.provider.utility: com.htc.dcs.service.utility.UtilityProvider
D/dalvikvm( 292): GC_FOR_MALLOC freed 55 objects / 177104 bytes in 74ms
D/dalvikvm( 292): GC_FOR_MALLOC freed 296 objects / 253256 bytes in 86ms
I/ActivityThread( 674): Publishing provider com.htc.sync.provider.weather: com.htc.sync.provider.weather.Provider
D/ConnectivityService( 292): getMobileDataEnabled returning true
I/ActivityThread( 674): Publishing provider com.htc.socialnetwork.snprovider: com.htc.socialnetwork.provider.SocialNetworkProvider
horiveira:tools stgomez91$
Click to expand...
Click to collapse
It rebooted after the second to the last line. This is my first time using logcat, so I don't know too much about what any of that stuff is, except for the last line obviously.
Can anybody tell the reason why I get these problems by looking at that?
Here's a copy of the logcat file: http://www.sendspace.com/file/kt3lj1
I was hoping this would work, but alas...it did not. What do I do now??

Had the same problem.
For me the solution was to reset the GPS and after that all the random reboots stopped.
Dial : ##GPSCLRX#
Enter your MSL Code
let the phone reboot.
I hope this works for you.

How do you get your MSL code?

Gonna try that now, I hope it works...
How did you figure out it was the GPS?
EDIT: Just tried what you suggested. Didn't seem to work: after it rebooted and got past the Fresh screen, it rebooted without me touching it.

jthurs said:
How do you get your MSL code?
Click to expand...
Click to collapse
Use MSL reader, it's in the Market (and free).

Alright, after doing what aj74 mentioned and it not working, I left the battery out for a bit then powered it back on. That was at 3pm. At around 4, it had yet to reboot so I decided to restore all of my apps with Titanium Backup. I have yet to have a random reboot, though I highly doubt it's fixed.
I'm afraid to use my phone :-/

same problem. looks like this is becoming more and more frequent. i have tried unrooted, and a bunch of rooted roms. this is a problem that needs solving fast.

lo' and behold, as I was getting confident and rearranging things on the phone the loops began again.

I guess I feel better
Well, I feel better since it isn't just me. It has been working fine, then I took the phone on my first trip and as soon as I got off the plane on Wednesday, the random restarts started.
I'm guess some type of app update caused it, but god only knows which one. I did a factory reset, the gps reset, restored a nandroid backup from late september, and turned off all synching. Still get the reboot loop.
I seem to be able to make it stop for a little while by putting the phone in the freezer, but I can't believe we would all start having this problem at about the same thing if it was simply a overheating issue.
Update:
I was roaming when all of this happened, and now that I'm home, I haven't been able to get the phone to mess up. This will make it tough to take in for service. It still may be a heating issue, however, since it is not hot where I live, but it was hot where I was visiting.
Update 2:
I have now been able to get the problem to happen in my home area. The battery temp was > 100 F when it happened.

[Q] DSP Manager causing kernel panic?

I use DSP Manager to boost the bass when listening to music through headphones, and I also tend to surf the web while doing so.
Quite frequently, I've been getting reboots while listening to music, and I've pulled the last_kmsg from my last reboot.
My question is: From the attached last_kmsg, can you tell if my reboots are being caused by a generic kernel panic, or is it something I can do about DSP Manager?

Not sure. Does it happen without DSP Manager? I've seen this bug before in a few occurances. It doesn't seem tied into any changes from stock. It may take a while but can you re-create it on the stock GB Sense kernel?
Here's what I can tell from the log:
1. You're using gingertiny-v2
2. The kernel error is related to an audio bug somewhere.
[ 1931.740722] pcm_write: timeout. dsp dead?
[ 1931.740722] kernel BUG at arch/arm/mach-msm/qdsp6/pcm_out.c:180!
[ 1931.740753] Unable to handle kernel NULL pointer dereference at virtual address 00000000
[ 1931.740783] pgd = c77dc000
That's about it. Not sure if it's connected to anything specific in my kernel. I don't think so but I don't know for sure.

Thanks for checking it out.
I'm quite certain it's not just a ROM I'm using as I've had similar if not exact issues with other ROMs while listening to music.
I'll first try debugging this with(out) DSP Manager, then if I really have to I'll use the stock kernel.
I really do enjoy the custom kernel you've made for us Tiny, I'd hate to even go back to stock to test this.

Sound dies after waking

This will be a long post to explain my problem and I hope somebody could enlighten me on what's happening and if it's fixable
Sound Problem
Bought an used T-Mobile S4 (SGH-M919), came with stock 4.3 (MK2), not rooted, not KNOX warranty voided, everything working perfectly including sound, 2 days of constant use, then I wanted to upgrade to 4.4.4 (NK2), I tried through system update on Android and it only said "Failed to register" or something similar, however with Kies3 I was able to upgrade, then the nightmare started.
Being a stock firmware I thought, what could go wrong, update went smoothly, everything was working but after 10 minutes and here comes the important part, the SOUND GETS STUCK/DOESN'T RESUME/DIES AFTER THE SYSTEM GOES TO SLEEP, it always happens when I leave the screen turn off for like 5-10 minutes, the longer it stays off, less chances sound returns, not through ear piece, speaker or headphones, weird part it's that if I turn the phone off and on it works normally again until sleep, everything works normally, except for the part that if the screen goes off, hell begins, the longer it stays off, less chances sound resumes, and I say that because sometimes sound resumes but after like 5-15 seconds of waking, AND IT REPRODUCES EVERY SOUND IT SHOULD HAVE DONE WHEN IT WENT AWAKE (like button presses, volume change, sound systems, etc), like if something was stuck or in large queue, I can almost say it's 100% something related to software and not hardware since it reproduces the animation sound at the boot every time.
After the sound dies, weird stuff happens, Youtube videos get reproduced at like 0.5x speed, trying to play music with the default player says "Not supported" (varying mp3's from 128 to 320kbps), sometimes if I reboot from Android it gets stuck in a restart loop, not always, sound only seems to return again when it's restarted through shutdown/manually (that doesn't seem to happen with custom ROMs), sometimes Android gets weird, like laggy, no background on the home screen, stuck and with only the shutdown menu working, not even volume bar showing up or very laggy (this was something very rare in custom ROMs or it didn't happen at all).
I had to void the KNOX warranty to install a custom recovery (TWRP) and flash custom roms, I already tried stock 4.4.4 roms debloated/deodexed/rooted and even a 5.0.1 rom, tried 2 different kernels + stock, different modems varying from MK2 to NK2 again (flashed like 5 times each one), hell even I tried to flash the LTE modem (NON-HLOS.bin) from MK2, however I didn't get any sound (WiFi was working, weird) since I read that it has to match the bootloader version.
At this moment I'm downloading a 4.3 custom ROM to do another test and probably the last one, I'm running out of options.
Little Facts:
-Already went to complete stock through Kies3 and tried flashing the full firmware with Odin too.
-Volume bar changes normally, I really assured it wasn't muted in any way.
-I f*ckd up IMEI, too much wipes, kernel switches, rom flashing, I did an EFS backup just to find it was at 0 already, however problem started way before that, one problem at the time.
-Light/RGB sensor doesn't work, headphone jack do (I even dissassembled and reassembled without headphone jack to test, didn't work).
-Tried plugin headphones and removing them multiple times.
-Tried with and without a SD card/SIM/WiFi.
-No warranty.
Sorry for the long post, I can create a thread if the mods prefer.

I think I remember seeing something like this and I'm not sure on this but I think it was a third party app causing it. Have you factory reset and installed no apps to see if it still happened, or reboot into safe mode? If you have, can you upload bootloader and modem info using this app https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo when you say you flashed the LTE modem and got no sound, that shouldn't happen if you did indeed flash the matching LTE modem. Could be firmwares never got flashed correctly. Could also be why your imei is 0

I did multiple factory resets, and when I flashed the LTE modem I didn't get sound because the LTE modem was MK2 (just trying stuff) and bootloader NK2, however I reflashed the full stock firmware, I'm currently at NK2 modem, LTE and bootloader.
The only thing I haven't done is reboot in safe mode, will try later and post results.
Edit:
About the IMEI, I'm pretty sure that when I made the EFS backup with TWRP it wasn't 0, since I made it because I was going to try stuff that could go wrong and I wanted a backup, I still have the full system backup with EFS partition included, however, not even restoring the backup bring it back.

New info
-Safe-mode didn't work
-Did multiple full wipes and back to stock through Kies3/Odin, nothing
Trying to find more info found this through ' adb logcat *:E ' (Stock ROM, NK2, 4.4.4)
Code:
E/AudioStreamOutALSA( 300): Invalid argument! It could be standby to recover
E/ACDB-LOADER( 300): Error: ACDB AudProc vol returned = -8
E/alsa_pcm( 300): cannot prepare channel: errno =-22
If the sound was lost, as soon as I click the screen it produces those errors like 100 times, even if it's on vibration only.
Some other errors from *#7353# testing (SPEAKER TEST)
Code:
E/AudioSessionOutALSA( 300): PCM Prepare failed - playback err = 0
E/AudioSessionOutALSA( 300): Failed to open LPA/Tunnel Session
E/AudioTrack( 300): Could not get audio output for stream type 3
E/AudioSink( 300): Unable to create audio track
E/TunnelPlayer( 300): Opening a routing session failed
E/MediaPlayer( 8834): error (1, -19)
E/MediaPlayer( 8834): error (-19, 0)
E/MediaPlayer( 8834): Should have subtitle controller already set
E/MediaPlayer( 8834): Error (1,-19)
E/MediaPlayer( 8834): Error (-19,0)
And from MELODY TEST
Code:
E/MediaPlayer( 8834): stop called in state 0
E/MediaPlayer( 8834): error (-38, 0)
E/MediaPlayerService( 300): WFD client is not created
E/alsa_pcm( 300): cannot prepare channel: errno =-22
E/AudioStreamOutALSA( 300): Invalid argument! It could be standby to recover
E/alsa_pcm( 300): cannot prepare channel: errno =-22
E/AudioStreamOutALSA( 300): Invalid argument! It could be standby to recover
E/alsa_pcm( 300): cannot prepare channel: errno =-22
E/AudioStreamOutALSA( 300): Invalid argument! It could be standby to recover
E/alsa_pcm( 300): cannot prepare channel: errno =-22
And those 2 lines repeats themselves like 100 times
It could be an hardware problem, sadly, I hate that it works, but it stops working for no reason.
And found multiple threads about the same issue across different models:
http://forum.xda-developers.com/showthread.php?t=2333222
http://forum.xda-developers.com/showthread.php?t=2386070
http://forum.xda-developers.com/showthread.php?t=2333222
http://forum.xda-developers.com/showthread.php?t=2718326
http://forum.xda-developers.com/showthread.php?t=2612167&page=6 Post #51

My problem may be similar to yours. I have a completely stock S4. I have done no rooting to it. About a month ago I noticed the same sound problem you have. I noticed my phone would lose sound ability the longer it was on. Similar problems with YouTube playback slow, and I can't play media files like music or video (I get process errors).
I have factory reset a few times and the problems return. I'm getting tired of having to reset my phone every 1/2 hour. I've missed phone calls and alarms I've set.

I had this problem on an ATT S4. It was a hardware issue. Phone was under warranty and fixed by Samsung.
Sent from my SGH-M919 using Tapatalk

I guess I have to do a insurance claim. My current phone is my 1st replacement of my original GS4. The first phone was insurance replaced because it was passed the factory warranty and it stopped charging any battery put into it. Now my current one has started hanging at the T-mobile logo when resetting and just plain random resets.
My GS4 was reliable for a while. Maybe time for a Nexus 6.

I literally did the same thing last week with a refurbished phone from T-Mobile. Buyer be ware
Sent from my SGH-M919 using XDA Free mobile app

Wifi not working after upgrading to 7.0 - ideas?

Hi everyone,
I downloaded and installed the OTA manually using the instructions here. Everything went fine, but after restarting the Wifi does not work. If I go to settings and flip the switch, it flips, but soon moves back into the off position.
Any ideas what I can check, what could be causing this? Thanks!

Just noticed the MAC address for Wifi reads 02:00:00:00:00:00, like the device is not recognised. There's a discussion about this and related problems here: https://productforums.google.com/forum/#!topic/nexus/Qbeb7ZP0wOw
What could be causing this?
strophy said:
Hi everyone,
I downloaded and installed the OTA manually using the instructions here. Everything went fine, but after restarting the Wifi does not work. If I go to settings and flip the switch, it flips, but soon moves back into the off position.
Any ideas what I can check, what could be causing this? Thanks!
Click to expand...
Click to collapse

You could try flashing the vendor.img, system.img, and boot.img from the factory image through fastboot
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
You could try flashing the vendor.img, system.img, and boot.img from the factory image through fastboot
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks SlimSnoopOS, will that preserve all my user data? Isn't that done already during the normal OTA process? Should I get the .img files from the OTA or from the full factory image?
I did a little more research on this by viewing the log over adb. The following status/error messages appear when I try to enable Wifi:
08-31 15:07:29.997 859 7849 D WifiService: setWifiEnabled: true pid=11646, uid=1000
08-31 15:07:35.069 522 857 E WifiHW : Failed to write wlan fw path param (No such device)
08-31 15:07:35.075 859 3272 E WifiStateMachine: Failed to reload STA firmware java.lang.IllegalStateException: command '2325 softap fwreload wlan0 STA' failed with '400 2325 SoftAP command has failed'
08-31 15:07:35.078 859 859 E WifiController: WifiControllerWifi turn on failed
I've been unable to find anything related online, but a lot of other people over at the Nexus product forums have this problem after upgrading. Can someone identify the error from these messages?
Thanks!

strophy said:
Thanks SlimSnoopOS, will that preserve all my user data? Isn't that done already during the normal OTA process? Should I get the .img files from the OTA or from the full factory image?
I did a little more research on this by viewing the log over adb. The following status/error messages appear when I try to enable Wifi:
08-31 15:07:29.997 859 7849 D WifiService: setWifiEnabled: true pid=11646, uid=1000
08-31 15:07:35.069 522 857 E WifiHW : Failed to write wlan fw path param (No such device)
08-31 15:07:35.075 859 3272 E WifiStateMachine: Failed to reload STA firmware java.lang.IllegalStateException: command '2325 softap fwreload wlan0 STA' failed with '400 2325 SoftAP command has failed'
08-31 15:07:35.078 859 859 E WifiController: WifiControllerWifi turn on failed
I've been unable to find anything related online, but a lot of other people over at the Nexus product forums have this problem after upgrading. Can someone identify the error from these messages?
Thanks!
Click to expand...
Click to collapse
Yes to both of your first two questions. When flashing factory image files one by one, only userdata.img affects that. Use the factory image.
Sent from my Nexus 5X using Tapatalk

strophy said:
Just noticed the MAC address for Wifi reads 02:00:00:00:00:00, like the device is not recognised. There's a discussion about this and related problems here: https://productforums.google.com/forum/#!topic/nexus/Qbeb7ZP0wOw
What could be causing this?
Click to expand...
Click to collapse
I am having same problem with MAC address = 02:00:00:00:00:00
---------- Post added at 11:09 AM ---------- Previous post was at 10:21 AM ----------
SlimSnoopOS said:
Yes to both of your first two questions. When flashing factory image files one by one, only userdata.img affects that. Use the factory image.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Flash factory image (boot.img, vendor.img, system.img) does not help my Nexus 5x (WiFi wrong MAC address)

xbing6 said:
I am having same problem with MAC address = 02:00:00:00:00:00
---------- Post added at 11:09 AM ---------- Previous post was at 10:21 AM ----------
Flash factory image (boot.img, vendor.img, system.img) does not help my Nexus 5x (WiFi wrong MAC address)
Click to expand...
Click to collapse
Thanks for trying that xbing6. My phone is still OEM locked so I'd like to try and fix this without removing the lock if possible. Unlikely, I know. I found a post where someone has resolved the problem by gaining root and doing a strange series of flashes and setting modifications:
http://chromloop.com/2016/08/how-to-fix-wifi-problem-updating-android-7-0-nougat/
Does anyone more knowledgeable care to theorize about how this happened and if there is anything we can do, beyond the root method or waiting for Google?

probably a hardware issue...
Hi there!
Does your WiFi keep flashing/blinking and showing "Turning on..."?
For example, like in this video: http://www.dailymotion.com/video/x2cuyjt_nexus-5-turning-wifi-on-frozen-problem_tech
I had a very similar problem on my G2 and I believe that these WiFi/BT problems are common to all LG devices, probably due to poor quality WiFi/BT chips used.
Did you drop your device? Did you leave it charging over a longer period, for example, during the night, and observed it getting very warm, or even hot, during the process?
I believe the root cause of your problem is a hardware issue. Someone in the forums suggested that replacing the battery may solve the problem; I can't confirm nor deny this, you might want to try it out.
Also, you might want to check out a detailed summary I've written about this issue here: http://forum.xda-developers.com/general/help/qa-wifi-stuck-mac-020000000000-g2-g3-g4-t3452133
Let us know if you managed to fix the problem!
Good luck!

NimbleWeasel said:
Hi there!
Does your WiFi keep flashing/blinking and showing "Turning on..."?
For example, like in this video: http://www.dailymotion.com/video/x2cuyjt_nexus-5-turning-wifi-on-frozen-problem_tech
I had a very similar problem on my G2 and I believe that these WiFi/BT problems are common to all LG devices, probably due to poor quality WiFi/BT chips used.
Did you drop your device? Did you leave it charging over a longer period, for example, during the night, and observed it getting very warm, or even hot, during the process?
I believe the root cause of your problem is a hardware issue. Someone in the forums suggested that replacing the battery may solve the problem; I can't confirm nor deny this, you might want to try it out.
Also, you might want to check out a detailed summary I've written about this issue here: http://forum.xda-developers.com/general/help/qa-wifi-stuck-mac-020000000000-g2-g3-g4-t3452133
Let us know if you managed to fix the problem!
Good luck!
Click to expand...
Click to collapse
Thanks for the ideas NimbleWeasel. I doubt it though - the wifi went from functioning perfectly to non-functional immediately after applying the update. Never been dropped, less than 2 months old, and doesn't get excessively hot. Google has now reached out to me for a bug report so I'll hopefully hear more from them soon and update this thread.

keep us posted!
Hi strophy,
What about the link, did you watch the video? Does your phone show the effect as in the video?
After reading through the posts again, I think that you might indeed be experiencing a different problem.
I am curious to see what Google will reply!

NimbleWeasel said:
Hi strophy,
What about the link, did you watch the video? Does your phone show the effect as in the video?
After reading through the posts again, I think that you might indeed be experiencing a different problem.
I am curious to see what Google will reply!
Click to expand...
Click to collapse
Hey mate, no my problem is quite different. Firstly, that video is a Nexus 5 running Android 4.x I think? I'm on Nexus 5X running Android 7.0. The wifi switch slides into the on position, stays there for 5 seconds, then slides back by itself. No hotspots are shown at any time. The MAC address also looks like the photo in this post: http://chromloop.com/2016/08/how-to-fix-wifi-problem-updating-android-7-0-nougat/
I don't think my problem is a hardware problem. Let's see what Google says...

My Wifi drops and reconnects whenever I take the phone out of my pocket and open an app that uses data. My data usage has gone up significantly with the Wifi drops. Appears there's others having problems on google product forums with no workaround at this time.
Any help would be appreciated!
ETA: My MAC address appears normal, not the one posted in other forums.

strophy said:
Just noticed the MAC address for Wifi reads 02:00:00:00:00:00, like the device is not recognised. There's a discussion about this and related problems here: https://productforums.google.com/forum/#!topic/nexus/Qbeb7ZP0wOw
What could be causing this?
Click to expand...
Click to collapse
I am facing the same issue. Hope Google finds a solution for this

Development [ROM][10.0][UNOFFICIAL] LineageOS 17.1

LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS 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. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Known issues:
You tell me
Instructions :
1. Boot into twrp
2. Advanced -> ADB Sideload -> Swipe
3. adb sideload copy-partitions.zip
4. Go back into sideload mode
5. adb sideload lineage.zip
6. Wipe Data
7. Reboot to bootloader
8. fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Downloads :
https://build.lolinet.com/file/lineage/ginna/
Source Code: https://github.com/motoe7
ROM OS Version: LineageOS 17.1
ROM Kernel: Linux 4.9
Version Information
Status: Stable
Credits:
Electimon - The entire device bringup
Rohan Hasabe - TWRP bringup, helped with device bringup
betaxab - Gave devices, helped with TWRP and device bringup
2/6/2021:
Fixed random crashes - https://build.lolinet.com/file/lineage/ginna/lineage-17.1-20210206-UNOFFICIAL-ginna.zip

Thanks to everyone who contributed to these bits, I'm hopeful that by the end of the year I will be using my new moto-e-2020 as my main phone to replace my aging moto-g-2015. I've got a couple first bugs/issues/showstoppers to report, but first I think it's important to note-
Finally I'm able to go to walmart (in the usa) and buy a sub $100 ($70) 'roid (boostmobile) phone (meeting some other criteria as well) which I can immediately install a (mostly?/sdks/tools) non-google-built os on. I erred a bit by doing lots of research (to avoid paying more for a moto g7) and forgetting that the moto-e-2020 is *not* at the moment on motorola's list of models their registered (free) dev program will give bootloader unlock codes for. However after thinking I was going to have to return the phone, I parsed the verbiage on their page and decided to just try 'fastboot oem get_unlock_data'. Then tried going through motorola's unlock code process. To my pleasant surprise, they did give me an unlock code. My next hiccup happened when I was disappointed to discover the 'allow oem unlucking' option was greyed out. I netsearched and found a similar samsung issue that was resolved on phones that hadn't been updated/activated by setting their date back a week. That didn't work here, but what did work was giving my new phone access to wifi and letting it start an update. After a few minutes, while it was still updating, the 'allow oem unlocking' was no longer greyed out, and the rest of the install was straightforward enough (getting used to a and b slots for recovery).
Anyway, as for the first glaring issues-
1) random reboots, seemed at first yesterday it would average less than 10 minutes of uptime and rarely an hour. Seems a bit better right now, I'm seeing if I can get some adb logcat output of interest. Let me know if there are other tests/logs I should do. I haven't yet tried the modded lineageos18. The image I used was lineage-17.1-20210119-UNOFFICIAL-ginna.zip.
2) mobile data won't work. I note that I first activated after installing this rom. I wonder if it would have helped to activate with stock android like I probably did long ago with my moto-g-2015. Note that it shows up as 't-mobile', however given my moto-g with boost showed up as 'sprint' and boost using sprint infra which merged with t-mobile recently...? My aboutphone:simstatus shows 'network:t-mobile', 'mobile network state:disconnected' (but mobile data enabled). If I uncheck automatic network selection, I can click on 'boost' by name on a list (that doesn't include t-mobile) and it will say 'connected' right away, but with no change I see otherwise. There was a weird thing with activation as an additional line, boost first charged me $20, then later charged me $30. And the confirmation sms for the activation happened hours later, but mobile data still isn't working.
3) I'd like to know if twrp is really necessary. I noticed a recovery.img in the download directory, guessing that might be the lineageos17.1 version I was happy to see available for my moto-g-2015. I'm guessing I could try it myself, but I would like to avoid brick-risky things.
4) I wonder if the 'your phone has an unlocked bootloader / can't be trusted' post unlock splash screen can be changed (with the same?) images that are available for the moto-g-2015 (that I read can be used on some other models as well). At least with the moto-e-2020 the splash has a black background.
Feel free to let me know if there are tests I can do or logs I can provide to help. Looks very promising, but not quite usable for me so far.

hi yes please do
adb logcat > logcat.txt
and send me the logcat.txt after around 10 seconds of it running

i've fixed the random crashes.
2/6/2021:
Fixed random crashes - https://build.lolinet.com/file/lineage/ginna/lineage-17.1-20210206-UNOFFICIAL-ginna.zip

Electimon said:
2/6/2021:
Fixed random crashes - https://build.lolinet.com/file/lineage/ginna/lineage-17.1-20210206-UNOFFICIAL-ginna.zip
Click to expand...
Click to collapse
Confirmed (so far, but I'm optimistic). Also I'm quite happy to report that mobile data is now working for me as well (maybe just a reinstall would have fixed?).
The most glaring (new?, not sure) issue/bug now is that speaker output doesn't seem to work except during calls. If I plug in headphones I do get output. Jacksensing failure could be an explanation?
Then after that, I'm getting the sense that the microphone level/gain is not good. Testing by leaving a vmail on my moto-g-2015 the level of the audio on the message seems too low. That is seperate from the longstanding issue I have had with the moto-g-2015/lineage output level. Long ago there was a known issue with a mixer_paths.xml workaround, though I've just lived with seeming lower, but barely tolerable, level since then. I've always planned on going full aosp rebuild with removing whatever softvol max limits are in place whereever. But the mote-e-2020 definitely doesn't have that problem (side by side comparison of same vmailbox checking). But it does seem with this rom the mote-e-2020 has too low mic/gain level. Seems like there could be a standardized testrig used for lineageos qa that could report expected decibel levels/metric on the devices wiki so people know what to expect.
In any event this update will definitely let me get to more serious testing.
Also worth noting, I did the upgrade by repeating the install steps. I noticed that on the copy partitions sideload it ends with an error after doing a lot of partitions fine, then ending with vendor(_b) "dd /dev/block/dm-2: write error: no space left on device". I think that may have happened on my initial install and I just ignored it, and it doesn't seem to matter (yet, afaict).

Ok, can you post a logcat while trying to play audio? Thanks

also, perhaps canceling what I said about in-call output levels, I discovered I'm only getting audio during calls with headphones(jack or usb) or when speakerphone is on. I.e. what I was interpreting as good in-call audio output level in non-speakerphone mode seems to really be a not very loud speakerphone mode output. And interesting to note that the default(?remembered?) setting after installing the rom is speakerphone-on. And to what I mentioned about the mic level, I tried a set of bluetooth earbuds with mic and left equivalent voicemails, and it was clear the bluetooth mic was at standard level, while the phone mic was quite low. That led me to want to try the same test with the default soundrecorder app, but curiously it seems unable to record from (this) bluetooth mic, getting input from the phone mic even when earbuds are connected. I noted the bt/dev settings have on/off for 'phone calls' and 'media audio'. Maybe it's just not supported by these earbuds/headset. I'll check 18.1 when I go back next. Though the mic level on the recorded audio there sounded acceptable compared to the low in-call voicemail test.
Also, is there any difference and a way to install the lineage-17.1-20210207-0753-ginna-25.zip. I'm testing with 0206-UNNOFFICIAL.

Not gonna lie, super excited about this! I never thought that this device would gain traction on XDA due to it being a very low budget device but boy am I glad it's getting some love.

I'm having some trouble here. I can flash Lineage no problem in TWRP the phone just won't boot. So then I try to follow the instructions exactly and get this...
So my moto e booted into Lineage unexpected (I didn't think it would). Nevertheless I'm going to share the command lines I followed since some suggest they failed and I find that strange since Lineage is thus far working.
V:\Everything Android\platform-tools>fastboot devices
ZY227J63CQ fastboot
V:\Everything Android\platform-tools>fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.016s]
Finished. Total time: 0.049s
V:\Everything Android\platform-tools>fastboot devices
ZY227J63CQ fastboot
V:\Everything Android\platform-tools>adb sideload copy-partitions.zip
serving: 'copy-partitions.zip' (~47%) adb: failed to read command: No error
V:\Everything Android\platform-tools>adb sideload lineage-17.1-20210206-UNOFFICIAL-ginna.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
V:\Everything Android\platform-tools>adb sideload lineage-17.1-20210206-UNOFFICIAL-ginna.zip
Total xfer: 1.00x
V:\Everything Android\platform-tools>fastboot devices
ZY227J63CQ fastboot
V:\Everything Android\platform-tools>fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.015s]
Finished. Total time: 0.023s
V:\Everything Android\platform-tools>
Also, about half the internal storage is apparently taken, I must've done something wrong in the flashing process?

Cyb3rSl4v3 said:
also, perhaps canceling what I said about in-call output levels, I discovered I'm only getting audio during calls with headphones(jack or usb) or when speakerphone is on. I.e. what I was interpreting as good in-call audio output level in non-speakerphone mode seems to really be a not very loud speakerphone mode output. And interesting to note that the default(?remembered?) setting after installing the rom is speakerphone-on. And to what I mentioned about the mic level, I tried a set of bluetooth earbuds with mic and left equivalent voicemails, and it was clear the bluetooth mic was at standard level, while the phone mic was quite low. That led me to want to try the same test with the default soundrecorder app, but curiously it seems unable to record from (this) bluetooth mic, getting input from the phone mic even when earbuds are connected. I noted the bt/dev settings have on/off for 'phone calls' and 'media audio'. Maybe it's just not supported by these earbuds/headset. I'll check 18.1 when I go back next. Though the mic level on the recorded audio there sounded acceptable compared to the low in-call voicemail test.
Also, is there any difference and a way to install the lineage-17.1-20210207-0753-ginna-25.zip. I'm testing with 0206-UNNOFFICIAL.
Click to expand...
Click to collapse
Also not getting audio from speakerphone, just headphones. I cannot comment on calls as I'm not using the device as a phone.

Lahpyrcopa said:
Also not getting audio from speakerphone, just headphones. I cannot comment on calls as I'm not using the device as a phone.
Click to expand...
Click to collapse
This morning my first recompile from source finally finished (took a solid couple days and an impressive swap storm on an 8G system (and cough 18G of swap used that I saw. perhaps mka -j 2 will help (default -j left 4 massive java processes running, metalava something or other)). I'll post more as I progress. I had to comment most of device/motorola/ginna/libshims/Android.mk to get it to compile. I was guess/expecting wifi tethering not to work, it seems to say no sim / phone service, though I had let my plan lapse.
But the cool thing is that I do now get speaker out. Another issue is that the recovery.img doesn't want to flash (preboot verification failed, I'll see if I can still reflash twrp next). And now that I've verified I can can compile moto-e-2020/17.1 (after having gotten moto-g-2015/17.1, with CPU_SSE42=false and JAVA_TOOL_OPTIONS=-Xmx6g, kept for e-2020), I'll go try 18.1 again to see if I can get it built without gapps (though I did recently renotice a /d/gapps app on f-droid). I had an issue with libllvm_android/LegalizeIntegerTypes there on my last attempt, but perhaps a fresh start (and reposync) will help me there as it did on 17.1 (which I'm quite optomistic I'll be happy enough with if need be soon enough).

also, I discovered that MotoBootLogoMaker from another xda thread does work (on linux/debian/mono to boot), and while I haven't tried replacing the untrusted/orange unlocked bootloader warning yet, I was able to extract that image with the tool, so I'm hopeful it can be replaced (perhaps excepting the small 'N/A' rendered font text which could perhaps be obscured by some whiter pixels in a custom logo/splash/background, or maybe the font/color is tweakable with that tool too).

Damn, it must take a very beefy machine to operate on android to take days to compile the system.
Well like I said before I only really need the headphone jack working for audio and that creepy message that Moto gives about having an unlocked phone that can't be trusted is absolutely hilarious . Look, I get it Motorola if you read this, you don't want to be liable for jack all nor do any of these even bigger empires. Just tone the scare tactics down a smidge so I can breathe!
To the developer, thanks for your effort. I thought that given the price of the device no one would bother with it.

clarifying a few points above-
- i had forgotten the twrp install step of via .zip (including magiskboot and ramdisk-recovery.cpio stuffs). I.e. I was just able to use the lineage171 recovery to install its build, but just not to install itself as twrp can (perhaps an a/b magisk thing, not sure maybe I saw that was a known thing until lineage adds that functionality? Perhaps I could reuse the twrp zip, or presumably better start building twrp from github now that I'm past the point of having a building lineage tree to use for that purpose)
- indeed MLBM can replace the orange bootloader unlocked splash/logo (which unlike moto-g-2015, is shown after a few milliseconds of the normal seperate logo image). But it doesn't look like there is a way (yet?) with MLBM to effect the 'N/A' text/font/color which remains (again, presumably obscurable if you put an area of white pixels over it on your custom replacement)
- my specific 17.1(and 18.1) build issue with device/motorola/ginna/libshims/Android.mk not-so-much-of-a-workaround-because-simdetection/calling-no-longer-works was a result of this-
"
FAILED: finishing build rules ...
Error: makefile error
Output:
ESC[1mdevice/motorola/ginna/libshims/Android.mk: ESC[31merror:ESC[0mESC[1m "libqsap_shim (SHARED_LIBRARIES android-arm64) missing libqsap_sdk (SHARED_LIBRARIES android-arm64)" ESC[0m
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
ESC[1mdevice/motorola/ginna/libshims/Android.mk: ESC[31merror:ESC[0mESC[1m "libqsap_shim (SHARED_LIBRARIES android-arm) missing libqsap_sdk (SHARED_LIBRARIES android-arm)" ESC[0m
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
ESC[1mbuild/make/core/main.mk:972: ESC[31merror: ESC[0mESC[1mexiting from previous errors.ESC[0m
"
At one point, still even earlier in noob mode, I guessed and tried treating (iirc) /vendor/{lib,lib64}/libqsap_sdk.so as perhaps missing device blobz, and/or went with ALLOW_MISSING_DEPENDENCIES=true. Maybe I'll try again now that I've otherwise got a successful build. I'm doing all this just using the 3 android_ repos from github.com/motoe7. Let me know if I should be using any of the other repos.

Cyb3rSl4v3 said:
I'm doing all this just using the 3 android_ repos from github.com/motoe7. Let me know if I should be using any of the other repos.
Click to expand...
Click to collapse
github.com/LineageOS/android_system_qcom seems to be the answer to my libshims/libqsap_sdk.so issue. I now have a build that at first glance at least is a good reproduction with the addition that speaker out now works for me. Still no in-call volume control. Though as I typed that I see that I seem to be getting crashes similar to what I first reported here but were fixed with the update build. I'll skim my logs a bit...

and seeing the recent git commits and motog7/17.1/nightlies thread (and my log) it seems I can live without MotoActions for the timebeing. I may try toggling some of the recentish audiofx things at some point to see if that gets the in-call volume control working. Also, /d/gapps seems to not apply without root, but I'll try building 18.1 again.

Is this ROM mostly functional? RE: Voice, data, sms? Is it Gapps free?
Just got this phone yesterday & want to start w/ an aged, working build before experimenting further. Open to other suggestions, just want to be free of Goog apps & framework...
Thanks to all who have taken the time to make this affordable phone tweekable.

googleverifysux said:
Is this ROM mostly functional? RE: Voice, data, sms? Is it Gapps free?
Just got this phone yesterday & want to start w/ an aged, working build before experimenting further. Open to other suggestions, just want to be free of Goog apps & framework...
Thanks to all who have taken the time to make this affordable phone tweekable.
Click to expand...
Click to collapse
From my experience it is 80% stable with certain glitches that occur.

I've tried flashing multiple different build of this ROM, and everything is working great, except when I try to flash GAPPS (anything besides pico) and I get an error about having no space on my /system partition.
When flashing PICO gapps, the installation finishes, but the OS fails to boot afterwards.
Any ideas? I've tried Lineage 17 and 18 now and can't get either to work.

googleverifysux said:
Is this ROM mostly functional? RE: Voice, data, sms? Is it Gapps free?
Just got this phone yesterday & want to start w/ an aged, working build before experimenting further. Open to other suggestions, just want to be free of Goog apps & framework...
Thanks to all who have taken the time to make this affordable phone tweekable.
Click to expand...
Click to collapse
It is gapps free, and everything is working on my Moto E. Can't get GAPPS to flash for the life of me though.