Related
Hi all. I have a HTC Desire rooted with unrevoked3. Phone runs sweet as except bluetooth. I can enable bluetooth graphically (the checkbox ticks and after some time the bluetooth logo appears on the status bar). However, if I cannot chance the device name, make the device discoverable or scan for devices. Nothing happens.
The kernel gives errors such as:
Code:
<3>[ 71.632263] hci_cmd_task: hci0 command tx timeout
I am currently running CyanogenMod 7.1 RC1, but this problem exists if I run other ROMs too. I've gone back to the HTC RUU to verify it's not hardware and bluetooth works fine there. So I dug about some more.
There are many posts relating to bluetooth problems on rooted Desires, but none appear to be line mine - Still, I tried some recommended solutions anyway. The issue of a 'USB brick' sounded a possible cause, but I followed through the solution (http://forum.xda-developers.com/showthread.php?t=691639) and got no further. I am sceptical as to if I modified the misc.img file correctly, as I don't know how to find my current ROM version (it's not under About The Phone).
I would really appreciate any help. I've been nosing about looking in '/sys/devices/virtual/bluetooth/hci0/' were the bluetooth stuff resides. See here: http://forum.cyanogenmod.com/topic/23500-bluetooth-lack-of-functionality/#entry217041 But this isn't just a Cyanogen problem. The only way I can restore bluetooth functionality is by letting HBOOT re-flash from PB99IMG.
I am not an expert in this, but I have read quite a lot and have a good idea of what's going on, but this has stumped me. I am very fluent in Linux. Any help you can give would be greatly received.
EDIT:
I notice that from the stock HTC ROM, I can root the device with unrevoked3 and Bluetooth still works. Then as soon as I do anything with ClockworkMod (version 2.5.0.7) it appears to break Bluetooth.
I dumped the misc partition from the stock HTC ROM while Bluetooth was working, and tried to reflash that to the misc partition once Bluetooth broke in Cyanogen - It didn't work: using flash_image on the rooted phone, it appears to work... it doesn't actively fail... it doesn't say anything, just returns (exit 0). Using fastboot flash misc mtd0.img results in checksum errors, etc and does actively fail.
Any advice would be greatly received please?!
Kind Regards,
George Smart.
FRX07.1 is here!!
This is a maintenance release - basically taking the newest components to make a completely up-to-date (as of Sept. 1).
Quite a lot has changed since FRX06 - the install process hasn't really, but be sure to read the changelog in the next post and the caveats in post #3!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of FroYo with a stable kernel from GIT (August 19 / 1348), and rootfs from GIT (Sept. 2).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated September 1 2011)
If instead you just want the system.ext2 (zip) (Updated July 15 2011) file by itself... Don't download this if you're not sure! Grab the full bundle!
2. Extract it. You’ll see a folder, FRX07.1, copy its contents to the root of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Screen calibration - you have three choices:
Re-use an old ts-calibration file if you have it and you know it's good.
Download the ts-calibration.zip file and extract it to where you put the rest of the files (root of SD or in a folder - make sure it all stays together!)
Manually calibrate - boot with no ts-calibration file and watch the boot process - you'll be asked to hit 5 points to calibrate the screen. If you have issues calibrating, try an older kernel (1225 works well) Once you have the calibration file hold on to it (make 15 copies if it's a good one ), reboot & go back to the newest kernel!
6. Run haret.exe.. Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins so the media scanner can go thru everything, etc. it will be much more pleasurable experience. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
See Incremental Updates for more information on updating the kernel and other components.
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data (all user data is stored in the data.img!!), Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Even though this build is considered fairly stable, you are more than likely going to run into issues. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
Caveats:
BT - works! But audio doesn't route. See this thread if you're feeling adventurous and want to play with/don't mind using some unstable/incomplete code...
Audio stutters every 10sec. The only fix I've heard is using a kernel from G3rmo (unfortunately it is old), or
Code:
su
kill -9 28
Which kills the [battery] process. I'm sure this will have negative effects on the battery meter/battery life...
SD Card not working...? "Waiting for SD Card" appearing on boot...? Try putting this command in your startup.txt
Code:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
See gummbah30's post reminding us of these commands.
SD Card has partitions? (If you used a non-XDAndroid build the answer is YES) Then you need to add "no_partitions" to your startup.txt. Between the quotes on the set cmdline line. Do not put it on its own line, it goes in between the quotes! Make sure there is one space between each item.
Front buttons messed up/wrong? You can use my rootfs which incorporates g3rm0's layout. This custom rootfs is no longer necessary, I have committed the changes so you can use the autobuild rootfs (in conjunction with physkeyboard=blac in your startup.txt)!
Keyboard tiny/unusable? Either change the IME (long press on the input box) Get rid of it! I've heard "Hackers Keyboard" is a good alternative - many options. There's also "Better Keyboard", Swype, etc... Side load the APK using AndroidApps, adb install, etc.
stinebd's Changelog:
stinebd said:
Here’s a new release for you, folks. This is a major release with a ton of changes, new features, and fixes. Our friend hyc/highlandsun did most of the heavy lifting for this release. Highlights include a rewritten RIL with support for world phones and greatly improved CDMA support; fixes for the media codecs; fixes for MMS on Sprint; increased security with the Superuser app.
A list of changes is included below. The FRX07 system image is available for download now, and will require the use of a new rootfs image, also available now. Additionally, we have a new bundle containing everything needed to enjoy a full FRX07 system.
Note: Due to the incredibly long list of changes, this is a somewhat condensed, terse changelog describing only the overall scope of the changes.
FRX07:
frameworks/base:
Major frameworks changes for CDMA/GSM dual-mode worldphone support. (hyc)
Fixes for data connection handling to improve startup time. (hyc)
Fixes for wifi handling to avoid issues on hanged drivers. (hyc)
Stagefreight (media codecs) fixes. (hyc/viruscrazy)
Fixes for Sprint’s wonky MMS markup structure. (hyc)
Fix MediaScanner not finding audio files (including ringtones) in system.ext2
hardware/libhardware_legacy:
Minor GPS driver fixes. (Alex[sp3dev])
Rename wifi interfaces to wlan0 on all devices (hyc)
hardware/xdandroid-ril: Major RIL refactoring for improved performance on all devices, and added CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Gallery3D: Switched back to Gallery3D as the gallery app (closes bug #111)
packages/apps/Mms: Fixes for Sprint’s wonky MMS markup structure. (hyc)
packages/apps/Phone: Fixes for CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Superuser: Added the Superuser package for authorizing su privileges. This, along with our signed builds, provides greatly increased security for the end user (mostly against malicious apps from the Market).
system/extras/su: Added as a dependency for the Superuser package
vendor/qcom/android-open: Include missing stagefright codec symbols. (hyc/viruscrazy)
To coincide with the FRX07 system image, the following rootfs changes have been made:
init.froyo.rc modifications...
Adjust wpa_supplicant service for the new abstraction provided by libhardware_legacy, as well as interface rename
Abstract the hciattach service to provide bluetooth support on both chipsets
Rename wifi interface to wlan0 on all devices
apns-conf.xml updated
keymaps completely reorganized, and RHOD end-call keya has been remapped to be the Home key in Android.
default.prop: set ro.secure=1 to lock down the adb shell - su can be used with the Superuser app to authorize root access in adb if needed.
Click to expand...
Click to collapse
Layman's Changelog
(As in, the changelog I wrote )
FRX07.1 Changelog:
RHOD - all buttons on the front no longer wake the device. Only the power button wakes the device now.
Updated to the newest RIL
hyc's modified libs for video now baked in - *most* HQ YouTube videos (and other HQ videos) should finally work!
RHOD & TOPA - Userland (Android) now controls the LED by default now. If you need to debug sleep, you will have to change the behavior manually.
Facebook sync should now work, out-of-box.
FRX07 Changelog:
Updated RIL (thanks hyc!) - this covers many different bugs that were in the old RIL - I'm only going to cover the major ones...
CDMA now works correctly (for the most part). force_cdma (and north_am_dialing) is now deprecated (not needed/ignored!)
You can boot with a SIM in on a CDMA device and choose your GSM or CDMA on the fly under Settings.
Location based on towers now works on CDMA.
1xRTT now displays correctly, but I never seem to get EVDO Rev.a... I always get 0. This is represented by a 3g icon, as this is what the Android framework provides.
Full MMS support! Please see this page for configuration instructions. Will need help fleshing out the list of carriers folks!
Spotty service, switching towers, etc should no longer cause the dreaded SoD (Sleep of Death) condition!
(Basic audio) 3.5mm support for RHOD400/500
Droidwall works out of the box now
Keyboard backlight now fades in/out
Gallery3D back in! Picasa Web Sync comes with it
A couple new apps added to AndroidApps folder:
rpierce99's app GetLogs
Titanium Backup
Cool man! Thanks for your work.
Thanks!
Well, in fact WEP works perfectly for me. The only thing that wifi fails is at turning it on after turning it off 2 times...
Also, with latest updates I can pair BT, haven't tried to transfer anything.
Eodun said:
Thanks!
Well, in fact WEP works perfectly for me. The only thing that wifi fails is at turning it on after turning it off 2 times...
Also, with latest updates I can pair BT, haven't tried to transfer anything.
Click to expand...
Click to collapse
Ah, I forget how different the bugs are for the TI chipsets. I'll change it, thanks!
Updated to FRX07! Enjoy!
woo FRX07 - I should really update my blackstone as its running 05 still
It seems that the 20110716 Kernel is giving problem to the Blackstone/Topaz.
you may use the previous kernel, or wait until is fixed.
Brgds
mass storage not connecting......anyone else facing this problem?
welard said:
mass storage not connecting......anyone else facing this problem?
Click to expand...
Click to collapse
USB mass storage has never worked (on looped mounts).
You can kinda fake it with Droid Explorer, it uses ADB to 'fake' USB mass storage.
arrrghhh said:
USB mass storage has never worked (on looped mounts).
You can kinda fake it with Droid Explorer, it uses ADB to 'fake' USB mass storage.
Click to expand...
Click to collapse
ok thanks alot....
Had to use a different kernel as yours wouldnt let it boot up
Working:
installing apps, no fc, its connecting to wifi nicely, only dropped once so far, connected to google account fine, coping nicely with downloading and installing multiple apps!!! i like that the others i have tried freeze up
Defect list:
Power control wigit loads frame but not icons on first load
froze when opening camera the second time had to battery pull! on first load
On restart attempt seemed to load haret ok, boot speed and time impoved compaired to first load, still lightly juddering boot animation
On second boot reloaded power control wigit, now displays correctly
Downloading and installing two apps at once navigating home screens caused 20second freeze up.
As someone said the motions but not the workings for usb connection, i cant get droid explorer to see my device so :-(
BT is reallly messed up using app "bluetooth file transfer", just loops itself to death, killings wi-fi as well, not kwl
Using phones bluetooth in settings, my computer says unable to send blah blah then when i turn off bluetooth the wifi is dropped might be connected
Can i overclock stably with this mod?
How do i get the front facing camera working?
FRX07 with CWM
I just succeeded in starting FRX07 as a CWM build.
But the startup wizard seems to be a little bit crazy. It's my first try to make a CWM build, so no wonder there are problems.
If I really can make a stable build I will post the results here.
alphecca911 said:
Can i overclock stabley with this mod?
How do i get the front facing camera working?
Click to expand...
Click to collapse
I couldn't really follow you post, these were the only questions I could find..
You can overclock - stably, dunno. I don't, so you tell me if you can OC.
Front-facing cam doesn't work, kernel issue not build.
ThaiDai said:
I just succeeded in starting FRX07 as a CWM build.
But the startup wizard seems to be a little bit crazy. It's my first try to make a CWM build, so no wonder there are problems.
If I really can make a stable build I will post the results here.
Click to expand...
Click to collapse
Startup wizard...? There isn't a startup wizard on XDAndroid builds...
yes i am sorry for that, i have just been note taking as i have been instaling and testing in the event that someone came, they could assist. I have it up and running now but it didnt work using ur kernel. (wouldnt boot) i have listed defects so far.
Thankyou for your answers to my questions.
Great rom, best i have tried
alphecca911 said:
yes i am sorry for that, i have just been note taking as i have been instaling and testing in the event that someone came, they could assist. I have it up and running now but it didnt work using ur kernel. (wouldnt boot) i have listed defects so far.
Thankyou for your answers to my questions.
Great rom, best i have tried
Click to expand...
Click to collapse
Hrm. I've heard BLAC doesn't work on the newest kernel... I'll have to ask emwe, he had a list of changes for FRX07 release, but I assumed they were RHOD-only... Perhaps something is effecting BLAC that isn't supposed to be .
I don't have a BLAC, so you'll have to help me - what is the newest kernel that does work? 20110711_082424? Also, how far does it get in the process? If adb is up, logs would be appreciated. Thanks.
Allright I'm running into problems! Haret starts and I get as far as the linux boot animation, but then the phone crashes and reboots... anyone else experiencing this?
bdacier said:
Allright I'm running into problems! Haret starts and I get as far as the linux boot animation, but then the phone crashes and reboots... anyone else experiencing this?
Click to expand...
Click to collapse
Sorry mate, seems the newest kernel isn't BLAC friendly! Please tell me which kernel does work... Use the autobuild service and try older kernels. First post has details on how to change your kernel, plus links to autobuild service...
To alphecca911 - most of your issues seem to be first boot related. Remember, you should let it sit on first boot so all the processes that run on first boot have plenty of time to work! I usually let it sit until it sleeps. I've had a lot of weird issues trying to do too many things on first boot on the device... I am impatient just like you probably . Just fight it .
Startup wizard...? There isn't a startup wizard on XDAndroid builds...
Click to expand...
Click to collapse
That might explain a lot
I just checked the system/app folder in the frx07 package. Of course you're right. I copied apps into this without looking. And there was an old SetupWizard.apk.
But just in the moment I started frx07 without any error.
Now I can start to make a real nice package for CWM. And "most" important: try a different boot animation.
I have to thank all XDAndroid developers for this and arrrghhh here for pointing me to it with his posts.
Really great job you are doing here at XDA developers
Thanks
I hope someone can help me figure out what the problem is with my phone because I am out of ideas. I've been using the peoples ROM with stock kernel and occasionally my phone calls would be very staticy , but toggling speaker phone removed that issue. Now any ROM I use that doesn't use the stock kernel causes that same issue except I can't toggle it off anymore. Also many kernels I use besides stock causes apps to force close and system process to force close, unless the kernel came with the ROM. I've tried wiping my internal storage, formatting everything, installing any kernel I can find, fixing permissions, clear long cache 100's of times, flashing kernelcleaner, and I really don't know what to do next. Any advice? I really don't want to be stuck on 4.1.2.
Can I get any help on this?
Sent from my SPH-L710 using xda app-developers app
dokosatchii said:
Can I get any help on this?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Maybe try a clean install. You could always take a logcat to see if it is phone related. May also be a defective earpiece
lvpre said:
Maybe try a clean install. You could always take a logcat to see if it is phone related. May also be a defective earpiece
Click to expand...
Click to collapse
Do you mean wipe internal/system/factory reset and the install a ROM? I've done that but no improvements. I'll try a logcat but have no idea how to decipher it.
Normally I'd agree with you about it being a faulty earpiece, but the same issue pops up if I connect headphones or bluetooth headset during a phone call, still the same static noise. Could it cause all these issues?
I created a logcat but not sure what I should be looking for. I ran a logcat while making a phone call, does someone have a similar logcat so I can compare against? If it turns out the same I guess its just a hardware problem and that I should replace the earpiece? Any advice would be great.
dokosatchii said:
I created a logcat but not sure what I should be looking for. I ran a logcat while making a phone call, does someone have a similar logcat so I can compare against? If it turns out the same I guess its just a hardware problem and that I should replace the earpiece? Any advice would be great.
Click to expand...
Click to collapse
What rom are you using? Sometimes a logcat with have an /e or /f if a file or service is causing the issue. Start the logcat then try to make a call. If you are still having issues, use odin, unified toolkit, or something similar and make your phone completely stock again. Since you did a full wipe (system, data, caches, factory reset), maybe the rom you flashed has a custom kernel that has voltage settings not compatible with your phone. But try the stock rooted rom and then go back to completely unrooted, out-of-the-box stock if that doesn't work.
lvpre said:
What rom are you using? Sometimes a logcat with have an /e or /f if a file or service is causing the issue. Start the logcat then try to make a call. If you are still having issues, use odin, unified toolkit, or something similar and make your phone completely stock again. Since you did a full wipe (system, data, caches, factory reset), maybe the rom you flashed has a custom kernel that has voltage settings not compatible with your phone. But try the stock rooted rom and then go back to completely unrooted, out-of-the-box stock if that doesn't work.
Click to expand...
Click to collapse
I reset the phone to stock using odin, and I still get the issue(sometimes), but it goes away when I toggle speaker phone once. I am starting to think either the speaker is bad or my phone is just faulty.
I have tried every rom possible, MIUI, Paranoid Android, Slimbean, the only one that works is the rom that uses stock kernel like FreeGS3 and The Peoples Rom and even then I still have to toggle the speaker phone to get it working.(not all the time)
ASIDE: When I flash other kernels to test whether it'll work just as ktoonz, etc. the phone just goes through a bootloop or process start to fail, could be related?
EDIT: I created a logcat while placing a phone call while on stock and while using slimbean and I see the following discrepancies:
Stock: 4.1.2
--------------------------------------------------------------------------------------------
[ 08-21 09:50:38.359 170: 170 D/AudioHardwareALSA ]
setParameters() realcall=on
[ 08-21 09:50:38.359 170: 170 D/AudioHardwareALSA ]
>>>> realcall start!!!!
[ 08-21 09:50:38.369 170:13648 V/AudioPolicyManagerBase ]
setPhoneState() state 2
[ 08-21 09:50:38.369 170:13648 V/AudioPolicyManagerBase ]
Entering call in setPhoneState()
[ 08-21 09:50:38.369 170:13648 E/AudioPolicyManagerBase ]
unknown stream type
[ 08-21 09:50:38.369 170:13648 V/AudioPolicyManagerBase ]
getNewDevice() selected device 1
Slimbean ROM 4.3/4.2.2
--------------------------------------------------------------------------------------------
[ 08-21 10:07:52.803 343: 817 D/AudioHardwareInterface ]
setMode(IN_CALL)
[ 08-21 10:07:52.803 343: 817 E/AudioPolicyManagerALSA ]
unknown stream type
[ 08-21 10:07:52.803 343: 817 E/AudioPolicyManagerALSA ]
unknown stream type
[ 08-21 10:07:52.803 343: 817 E/AudioPolicyManagerALSA ]
unknown stream type
[ 08-21 10:07:52.803 343: 817 E/AudioPolicyManagerALSA ]
unknown stream type
Any idea's on how to get this AudioPolicyManager to run properly?
EDIT: After endless searching, guidance and effort, I am chalking this up to hardware problems. If anyone is experiencing this issue, I recommended returning the phone to sprint and getting it replaced.
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
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.