Hello guys,
this modded radio app is widespread on Xda these days, and lots of users are loving it;
so I thought it would be cool if we have it on our beloved Z1C too.
This mod allows you to launch the Radio without headphone (or earphone),
it was tested by me on both KK .681 and .757 {odexed and deodexed}.
it was tested by BarbasanAB on JB 4.3
The benefits of this mod are:
You won't face the silly message "insert headset" or being forced to close the app
You don't have any headset near you but you wonna play radio
It is a cool feature to have (or I think so)
As I did, you can check any material you wan't if it is metal or not:silly:
Instructions:
Just flash This Flashable Zip,,, [Mirror for the same file] and enjoy:fingers-crossed:
Also you can change it manually and set permission for it (664)
Notes:
If you insert your head set then remove them; the radio will turn off, you need then to press the turn on button
Since the headset is actually the antenna, playing radio without antenna wouldn't be as clear as when you have one
So for better reception, place metal object near the phone {no need to touch}, or you have to be in a high place and without roof above you
RDS working, but need a very good signal
To restore the original radio; Flash This,,, [Mirror for the same file]
Reserved for the future
Is this not a pointless mod if the radio uses the headset as an antenna as stated by other users.
XperienceD said:
Is this not a pointless mod if the radio uses the headset as an antenna as stated by other users.
Click to expand...
Click to collapse
Well I mentioned the benefits of this mod, so if you're not interested of any of them; don't use it;
no need to destroy the thread with such comment, other users maybe interested in it (it's been downloaded 21 times for now)
XperienceD said:
Is this not a pointless mod if the radio uses the headset as an antenna as stated by other users.
Click to expand...
Click to collapse
omarainea said:
Well I mentioned the benefits of this mod, so if you're not interested of any of them; don't use it;
no need to destroy the thread with such comment, other users maybe interested in it (it's been downloaded 13 times for now)
Click to expand...
Click to collapse
I for one appreciate it. Not pointless, quite the opposite actually.
Sent from my D5503 using Tapatalk
This is great. I loved this on my Xperia TL (shout out to @peetr_ !)
I should have just tried it. Works nicely on JB! Thank you.
Any chance you can do this for the 4.3 version? (I'm assuming this KK apk won't run on JB)
working with 4.3
Do you need root for this?
New Folder said:
Do you need root for this?
Click to expand...
Click to collapse
no, if you have recovery, then just flash the zip;
but if you don't have recovery or root, then you can't use it
I assume this should work on the new 4.4.4 firmware too right?!!
Works in 4.4.4 as well....
OmarEinea said:
Hello guys,
this modded radio app is widespread on Xda these days, and lots of users are loving it;
so I thought it would be cool if we have it on our beloved Z1C too.
This mod allows you to launch the Radio without headphone (or earphone),
it was tested by me on both KK .681 and .757 {odexed and deodexed}.
it was tested by BarbasanAB on JB 4.3
The benefits of this mod are:
You won't face the silly message "insert headset" or being forced to close the app
You don't have any headset near you but you wonna play radio
It is a cool feature to have (or I think so)
As I did, you can check any material you wan't if it is metal or not:silly:
Instructions:
Just flash This Flashable Zip and enjoy:fingers-crossed:
Also you can change it manually and set permission for it (664)
Notes:
If you insert your head set then remove them; the radio will turn off, you need then to press the turn on button
Since the headset is actually the antenna, playing radio without antenna wouldn't be as clear as when you have one
So for better reception, place metal object near the phone {no need to touch}, or you have to be in a high place and without roof above you
RDS working, but need a very good signal
To restore the original radio; Flash This
Click to expand...
Click to collapse
Did not work without Headset.
djsnoopyxxl said:
Did not work without Headset.
Click to expand...
Click to collapse
How did you replace it?
this usually means it wasn't really been replaced!!
OmarEinea said:
How did you replace it?
this usually means it wasn't really been replaced!!
Click to expand...
Click to collapse
I have made a flash and i have replace it with Root Explorer.
The Radio works without the Headset, thats real.
But you dont have a Signal.
You can only hear a noise and nothing else.
And that is the reason why you dont have a Antenna.
djsnoopyxxl said:
I have made a flash and i have replace it with Root Explorer.
The Radio works without the Headset, thats real.
But you dont have a Signal.
You can only hear a noise and nothing else.
And that is the reason why you dont have a Antenna.
Click to expand...
Click to collapse
Yeah that is mentioned in OP, read it and see the possible benefits of this mod,
Dont works on .108, the radio turns on, but i only can hear noises
xCoNDex said:
Dont works on .108, the radio turns on, but i only can hear noises
Click to expand...
Click to collapse
please read full OP before posting, as the head/earphones work as an antenna, you won't hear anything unless you are in an uncovered place,
or a high place would be better.
Tried on open places and dont work, no signal
UPDATE: I should have just flashed the zip. Sorry about the stuff below. I reverted everything that I did below and just flashed the zip with TWRP. It is working fine for me now. Thanks!
With the understanding that location is key here in order to get this working properly without headphones/antenna, I think I'm having a bit of a different issue on 4.4.4 (14.4.A.0.108). I believe that I am getting signal, but no audio output. I started outside with no headphone, and did the scan. It found a station (and I could tell it was getting signal because it read the name of the radio station), but no audio output (whether I chose speaker output or not). Later on, I tried again by plugging my headphones in. Same result - the scan found a station, displayed the info, but no sound coming through, whether I chose speaker or headphone. Screenshot attached.
Now I didn't flash - I grabbed the APK and did the following:
1) Renamed my /system/app/radio3.apk to radio3.apkbak
2) Renamed my /system/app/radio3.odex to radio3.odexbak
3) Copied the radio3 apk from this thread and dropped it in, and set permission (644).
4) Powered off phone, and back on, then tried the app.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas?
OmarEinea said:
please read full OP before posting, as the head/earphones work as an antenna, you won't hear anything unless you are in an uncovered place,
or a high place would be better.
Click to expand...
Click to collapse
Please,what is better with your app as the stock one.
When i need a Headphone for your Mod, is that the same like the stock one.
So, nobody need this.
For me , only the differents to the stock is, you can start without the Headphone but for a working app you need the Headphone.
Tell me...what is in your Mod better as in the stock one.
Thanks
Related
The app is now live on Google Play.
Thanks to all my beta testers for helping me iron out the wrinkles. I will still post beta versions here when I have new features that need testing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tired of entering your password all the time? SkipLock lets you skip past the lock screen when you're connected to a designated wifi or bluetooth device. When you're at home or in your car, your phone is safe and you don't need to be typing in that damn password all the time. When you're connected to your wifi network, or any bluetooth device, you can go straight to the home screen when you press the power button. You can even have it keep the phone unlocked while you're connected to a bluetooth keychain or headset. As soon as the phone gets out of range, it locks.
This is a public beta. SkipLock is a complete rewrite of Unlock With WiFi. Why rewrite it? This blog post explains the reasoning behind it.
Here are the new features in SkipLock:
Pattern and face unlock supported on rooted devices
Completely redesigned Android 4+ user interface
No background service = less memory usage and more reliable
No status bar icon required (but it’s still an option). Tray-only notifications also an option.
If you have notifications enabled, you can now tap the notification to instantly lock the device
Even more cool stuff coming later
Many of the existing features from Unlock With WiFi will also be in the new app. Some of them are:
Automatically turn off wifi when leaving home
Automatically turn on/off bluetooth
Automatically turn on/off sync
WidgetLocker integration
Lock delay has been removed because Android 4+ supports it natively now
If you have a bug to report, press Bug Report in the app's menu. This will send me some diagnostic information that will help me figure out what's wrong. This is the quickest way to get a response. You may post more general questions in this thread, and I will try to answer them, but bug reports sent directly to me take precedence.
SkipLock requires Android 4.0 or above. Root is required for patterns and face unlock. Only PINs and passwords are supported without root.
SkipLock FAQ
The FAQ is now being maintained on my website.
Crashes on startup on CM 10.2 M1 on HTC One
MajorGaz said:
Crashes on startup on CM 10.2 M1 on HTC One
Click to expand...
Click to collapse
sorry about that! it is the first release of the beta, so please bear with me. can you email me the log file? it's at /sdcard/SkipLock.log. send it to support at benhirashima dot you know what.
Crashes
This seems like a really great and useful app. However I can't seem to access it. Every time I click on the app it just crashes.
Running Droid Bionic with Jelly Bean [4.1.2]
Bionic22 said:
This seems like a really great and useful app. However I can't seem to access it. Every time I click on the app it just crashes.
Running Droid Bionic with Jelly Bean [4.1.2]
Click to expand...
Click to collapse
sorry, corrupted apk file! i just uploaded a new one that works.
Ben74 said:
sorry, corrupted apk file! i just uploaded a new one that works.
Click to expand...
Click to collapse
Seems to work fine on my Nexus 5.
Only tested the WiFi setting though, not bluetooth.
Are there any plans to unlock with NFC too? I should be getting an NFC ring soon and I'd love for it to work with that, so when I grab my phone there's no PIN/password but when others get hold of it it requires a PIN/password.
D3_ said:
Seems to work fine on my Nexus 5.
Only tested the WiFi setting though, not bluetooth.
Are there any plans to unlock with NFC too? I should be getting an NFC ring soon and I'd love for it to work with that, so when I grab my phone there's no PIN/password but when others get hold of it it requires a PIN/password.
Click to expand...
Click to collapse
i would love to do that too, but unfortunately, the NFC reader is not active unless the phone is already awake and unlocked. that goes for most phones anyway. obviously, there are some exceptions, like the moto x.
Ben74 said:
i would love to do that too, but unfortunately, the NFC reader is not active unless the phone is already awake and unlocked. that goes for most phones anyway. obviously, there are some exceptions, like the moto x.
Click to expand...
Click to collapse
True, but there are plenty of custom ROMs and even xposed modules which allow you to enable NFC with the screen off or with the screen on and the phone locked.
Still, if it's not something you're willing to add, there's nothing I can do to change that. The app works great as it is.
D3_ said:
True, but there are plenty of custom ROMs and even xposed modules which allow you to enable NFC with the screen off or with the screen on and the phone locked.
Still, if it's not something you're willing to add, there's nothing I can do to change that. The app works great as it is.
Click to expand...
Click to collapse
hmm, that's interesting. maybe i'll look into it when i get a chance.
Installs now.
Will give it a whack when i get home
It works!
My phone was locked and by adding my WiFi network as an exception, the phone was automatically unlocked.
I'll test it out tomorrow when I leave my house and when I get back to see if it re-locks when i leave my wifi network/unlocks itself upon reaching my wifi network.
Bionic22 said:
My phone was locked and by adding my WiFi network as an exception, the phone was automatically unlocked.
I'll test it out tomorrow when I leave my house and when I get back to see if it re-locks when i leave my wifi network/unlocks itself upon reaching my wifi network.
Click to expand...
Click to collapse
great! thanks for the feedback. try to test it with bluetooth too, if you can.
Also work on my SGS3 Omega v51 4.3
sent from my amazing SGS3 via Tapatalk
Is this time limited?
I don't know how you did it, but this works on stock rooted HTC One with pattern lock! Your previous app and some other apps do not, but this one works perfectly! When does this beta expire?
Take my money!
Side note: does not work on nexus7 with CM 10.2 (4.3) pattern always shows even when skiplock notification says its unlocked. Going to submit report from app
Thanks for this! I have missed this function since using HTC One. And will use this on my Nexus 5 when it arrives too
D3_ said:
True, but there are plenty of custom ROMs and even xposed modules which allow you to enable NFC with the screen off or with the screen on and the phone locked.
Still, if it's not something you're willing to add, there's nothing I can do to change that. The app works great as it is.
Click to expand...
Click to collapse
Yes, the S3 supports nfc from the lockscreen on some ROMs
My Feedback
Thank you for this great little software. You can also achieve this with software like lama or tasker. But I dont need such big toolkits. So your app fits perfectly on my device.
Here are my thoughts:
* starting an app when a network is in reach - great for car-users to start their favorite mp3-player etc.
* simple geofencing to re enable wifi/bluetooth
* turning on/off different system profiles (so you dont have to take care of all settings...it´s all build into the os)
Keep on coding!
working great on note 2 4.3 keep it up bro!
thanks for the feedback, guys. good to hear it's working! for those who asked, yes it's time limited. the current version will expire at the end of november, but if i feel that more testing is necessary, i will update the app and extend the time limit.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your warranty is now void.
I am neither responsible for bricked devices, dead SD cards,
thermonuclear war, nor you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! You alone are choosing to make these modifications.
If you point the finger at me for messing up your device, I won't laugh at you, but I'll try to work with you to fix it.
Thank you Rashed97 for your RS988 device tree!
This is an unofficial LineageOS 14.1 ROM for the LG G5 RS988 . This is my first ROM, so things may go awry, but I haven't seen much evidence for that yet.
Working:
Brightness
Cameras
Fingerprint reader
Flashlight
Microphone (calling w/ Google Voice/Hangouts seems to work--that's what I use)
LED
Wi-Fi
Wi-Fi Hotspot
Quick Charge (users are reporting faster-than-stock speeds. I have experienced this as well)
Video recording (thanks @T3MPEST)
Not Working:
NFC, which includes Google Pay, etc. (thanks @-lukin-)
Loud static noise when using BT devices in calls (thanks @goast)
GPS — issues locking location while using Google Maps, etc.
Buggy media codecs preventing proper music playback; use third-party music players instead (thanks @LucklessCebu)
Audio recording (both pre-installed and third-party app) Working as of 3/10
Battery charging animation missing; "loops" LG logo (thanks @mattintoronto) Working as of 3/10
In The Works:
FM Radio Radio is apparently not included in any of the U.S. variants
Magisk Working w/ flashable .zip
Substratum Theme Engine Development on LineageOMS is currently inactive
Downloads:
I make direct links whenever possible for those of you with download managers.
20180615: MD5: db6f5cae64311f74425de7dff4f13dda
Updates: 5 June security patch, upstream Lineage updates
Android File Host
20180415: MD5: 1315911cb5c4bb875c2d1ab1b9eaa8ac
Updates: Security patch updates, upstream Lineage updates
Android File Host
20180327: MD5: e492de44bb789121916b22353a436dcc
Updated Lineage sources. Fixes double-tap to wake, screen tearing, etc.
Android File Host
20180310: MD5: 10b5c19def693e83203d5d8e07358ba6
Updates: Switched to current Lineage sources, which should fix a lot of things. Clean install will be necessary.
Android File Host
20180204: MD5: da2b6a9cd9265177566470aab2bc3aa0
I have been developer-approved! I have removed the Google Drive links in favor of Android File Host.
Android File Host
XDA:DevDB Information
[RS988][ROM][UNOFFICIAL] LineageOS 14.1, ROM for the LG G5
Contributors
NextDroid, Rashed97
Source Code: https://github.com/imasaru/android_device_lge_rs988
ROM OS Version: 7.x Nougat
ROM Firmware Required: Bootloader Unlocked, Latest TWRP installed
Based On: LineageOS
Version Information
Status: Nightly
Created 2018-02-04
Last Updated 2018-06-18
Reserved.
NextDroid said:
Reserved.
Click to expand...
Click to collapse
Do you own Bluetooth devices? Specifically Android Wear and headphones? Just wanted to see if the Android Wear connected and worked and to see what Bluetooth calls were like. I'll back up and flash
Darn it @goast! I was just about to make another "reserved" post! Haha, just kidding. It's fine
I'll test my headphones right now and report back.
EDIT: It seems to work. Playback and the microphone on my BT headphones work.
NextDroid said:
Darn it @goast! I was just about to make another "reserved" post! Haha.
I'll test my headphones right now and report back.
EDIT: It seems to work. Playback and the microphone on my BT headphones work.
Click to expand...
Click to collapse
I'm sorry bro so everything I tested works. Bluetooth during call didn't. I have to use for work. So I restored my stock backup. I know this is a long standing upstream issue. Caller complained of loud scratching sounds during call.
If you need anymore info or anything for testing pm me and I'll respond
goast said:
I'm sorry bro so everything I tested works. Bluetooth during call didn't. I have to use for work. So I restored my stock backup. I know this is a long standing upstream issue. Caller complained of loud scratching sounds during call.
If you need anymore info or anything for testing pm me and I'll respond
Click to expand...
Click to collapse
Alright! Thanks.
Wy Wi-Fi is not woking
After flashing this Rom, my wi-fi is not working any longer. It turns on, but it won't connect.
Any Ideas?
edit: I am in Europe so I guess that's the deal... I'll flash another one
SuperQvas said:
After flashing this Rom, my wi-fi is not working any longer. It turns on, but it won't connect.
Any Ideas?
edit: I am in Europe so I guess that's the deal... I'll flash another one
Click to expand...
Click to collapse
Hm. I assume they use different frequencies 2.4/5GHz band for their wireless networks along? I'm not too sure.
Here in the U.S., WiFi works for me on the 5GHz band.
goast said:
I'm sorry bro so everything I tested works. Bluetooth during call didn't. I have to use for work. So I restored my stock backup. I know this is a long standing upstream issue. Caller complained of loud scratching sounds during call.
Click to expand...
Click to collapse
Adding to main post.
NextDroid said:
Hm. I assume they use different frequencies 2.4/5GHz band for their wireless networks along? I'm not too sure.
Here in the U.S., WiFi works for me on the 5GHz band.
Adding to main post.
Click to expand...
Click to collapse
I say I know I didn't look but all the other cm or aosp rooms had it too
Probably could be fixed but I know nothing about how to do it.
Edit: pmed u
Finally some light for RS988
NextDroid said:
Darn it @goast! I was just about to make another "reserved" post! Haha, just kidding. It's fine
I'll test my headphones right now and report back.
EDIT: It seems to work. Playback and the microphone on my BT headphones work.
Click to expand...
Click to collapse
Finally, someone is taking efforts to port ROM to this device.
Thanks @NextDroid
Will try out this rom coming weekend.
More keen on the battery performance.
rahuldg said:
Finally, someone is taking efforts to port ROM to this device.
Thanks @NextDroid
Will try out this rom coming weekend.
More keen on the battery performance.
Click to expand...
Click to collapse
Thank you!
Speaking of battery performance, I made this observation about an hour ago and was just about to post on it.
So I tried @waau 's Typhon kernel (M5 RC1) for RS988 earlier today to see whether it would work with this build of LOS. I found that Bluetooth would not work properly (as I wrote in the main post).
Thus I decided to return back to the 3.18 kernel that was built with LOS. I didn't have a .zip or an .img handy, so I reflashed the ROM to get the kernel and my Bluetooth back.
My phone was on low battery a while ago at 13%, and so I connected the charger and did something else for five minutes or so. When I got back, it was at 22%! I opened up Ampere to find something interesting... (attached photo)
Is this a feature of the stock kernel or did my reflashing "overlay" Typhon and keep Quick Charge from it? It would be nice to retest pure stock and see what happens (@goast?)
Either way, this is definitely a win-win.
Also, there weren't any camera issues on the stock kernel (before I flashed Typhon). Zoom worked and everything.
NextDroid said:
Thank you!
Speaking of battery performance, I made this observation about an hour ago and was just about to post on it.
So I tried @waau 's Typhon kernel (M5 RC1) for RS988 earlier today to see whether it would work with this build of LOS. I found that Bluetooth would not work properly (as I wrote in the main post).
Thus I decided to return back to the 3.18 kernel that was built with LOS. I didn't have a .zip or an .img handy, so I reflashed the ROM to get the kernel and my Bluetooth back.
My phone was on low battery a while ago at 13%, and so I connected the charger and did something else for five minutes or so. When I got back, it was at 22%! I opened up Ampere to find something interesting... (attached photo)
Is this a feature of the stock kernel or did my reflashing "overlay" Typhon and keep Quick Charge from it? It would be nice to retest pure stock and see what happens (@goast?)
Either way, this is definitely a win-win.
Click to expand...
Click to collapse
Those two things were broken on other devices before Typhon was made. I'd be willing to guess it some artifacts left over from Typhon. Maybe someone else can elaborate
I had no camera focus issue with stock kernel on this rom. I'm not sure about the quick charge though. I have 5 batteries so I rarely plug it in.
first custom rom i've tried on my RS988 that has worked so far. i am very impressed at the results. it just feels a lot quicker than stock nougat. sure as hell helps to not have 345830 pre-installed bloatware garbage apps.
also, my charging speed is a lot faster than stock nougat as well! normally accubattery shows my charge speed capping out at 2,480mA and right now on LineageOS i am capping out at 3,010 mA ! at that speed I could go from a dead battery to 100 percent in one hour. incredibly impressive. i don't use NFC at all and barely use bluetooth so i haven't bothered to test those things yet. so far everything else works for me. FANTASTIC WORK!
jungle35 said:
first custom rom i've tried on my RS988 that has worked so far. i am very impressed at the results. it just feels a lot quicker than stock nougat. sure as hell helps to not have 345830 pre-installed bloatware garbage apps.
also, my charging speed is a lot faster than stock nougat as well! normally accubattery shows my charge speed capping out at 2,480mA and right now on LineageOS i am capping out at 3,010 mA ! at that speed I could go from a dead battery to 100 percent in one hour. incredibly impressive. i don't use NFC at all and barely use bluetooth so i haven't bothered to test those things yet. so far everything else works for me. FANTASTIC WORK!
Click to expand...
Click to collapse
Well this is great news! Thank you for trying this out I'm glad it's working out!
@goast Maybe this is an indication that this is the Lineage kernel and not Typhon. Now that I think about it, the kernel is compiled at buildtime into a single file, which is stored in the boot partition. I doubt that it is a system of directories that could have some files overwritten.
Also, I think I see the BT calling problem you were talking about. I attempted to make a recording with both the preinstalled Recorder and a third-party app and I got static. When I made a call over Wi-Fi using Hangouts, though, I had no issues.
Also, final thing: have any of you tried to flash a Magisk .zip or SuperSU? I have tried countless times but have not had any success :/
NextDroid said:
Well this is great news! Thank you for trying this out I'm glad it's working out!
@goast Maybe this is an indication that this is the Lineage kernel and not Typhon. Now that I think about it, the kernel is compiled at buildtime into a single file, which is stored in the boot partition. I doubt that it is a system of directories that could have some files overwritten.
Also, I think I see the BT calling problem you were talking about. I attempted to make a recording with both the preinstalled Recorder and a third-party app and I got static. When I made a call over Wi-Fi using Hangouts, though, I had no issues.
Also, final thing: have any of you tried to flash a Magisk .zip or SuperSU? I have tried countless times but have not had any success :/
Click to expand...
Click to collapse
I think it is LineageOS itself in regards to the quick charge. I went from stock Nougat -> flashed the stock Nougat 21c build for RS988's via TWRP -> flashed LineageOS and from the first time booting up into LineageOS the quick charge was working already. It won't tell you it's quick charging in the notifications the same way stock Android does, but if you monitor it with Accubattery or a similar app you will see the charge rate is definitely quick charge.
In regards to Magisk, that is how I am rooted right now. Using the patched bootloader method caused me to boot loop so I just flashed Magisk 15.3 via TWRP then installed Magisk Manager and it worked perfectly. No problems with root at all and all the apps I've tried so far that required root access have worked. I am really really liking this setup a lot. Overall this is much faster for me than stock Android was due to how many bloatware apps LG included by default.
Will continue to test it out during my day to day use and see if I come across any problems. Once again, great work @NextDroid !!
NextDroid said:
Well this is great news! Thank you for trying this out I'm glad it's working out!
@goast Maybe this is an indication that this is the Lineage kernel and not Typhon. Now that I think about it, the kernel is compiled at buildtime into a single file, which is stored in the boot partition. I doubt that it is a system of directories that could have some files overwritten.
Also, I think I see the BT calling problem you were talking about. I attempted to make a recording with both the preinstalled Recorder and a third-party app and I got static. When I made a call over Wi-Fi using Hangouts, though, I had no issues.
Also, final thing: have any of you tried to flash a Magisk .zip or SuperSU? I have tried countless times but have not had any success :/
Click to expand...
Click to collapse
Cool. If you can get me a log of the issue I can pass it along if you can't figure out a solution
If you think you have one and run a test build let me know too lol
First off all, thanks for your work, this is a big step in having more roms developed since a couple of them follow the lineage branch.
I'm not a dev so probably this is just a stupid idea, but seeing that the main problems for the bugs appears to be the base kernel, maybe something can be ported from the LG V20 kernel in order to fix those problems since both phones share mainly the same specifications and the V20 has official lineage branch.
Also maybe check the wifi/bluetooh drivers in custom V20 kernels for lineage.
My previous phone was a motorola verizon droid turbo, and a lot of its development was thanks to the nexus 6, and moto x repository.
Just a thought.
SuperQvas said:
After flashing this Rom, my wi-fi is not working any longer. It turns on, but it won't connect.
Any Ideas?
edit: I am in Europe so I guess that's the deal... I'll flash another one
Click to expand...
Click to collapse
I know i had trouble connecting to my 5GHz wifi at home until I set my router to only use one channel. Currently its using channel 36, and its been working just fine ever since i changed that.
DEPRECATED, PLEASE DOWNLOAD FORM OFFICIAL PIXEL EXPERIENCE WEBSITE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Moto G6 Plus
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 10.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
You tell me!
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from Android File Host Folder
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Our device Telegram group
Our device Telegram channel
Android OS version: 10.0.0_r40
Security patch level: July 2020
Build author/Device Maintainer: @juampapo546
Special thanks to: @Jleeblanch
Device Source code: https://github.com/juampapo546
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Changelog 16/07
Fixed bluetooth and wired headsets calls
Update kernel and some device stuff
5th July security patch
Thanks!!!
It's a very good and stable Rom
After two days of using I found no issue and the battery was at the second cycle 7 hours of screen on time and everything worksfine
You can use it as daily driver
hey there, just curious if this has the same issue with bluetooth headphone calling as some other roms for this phone?
Reece's Puffs said:
hey there, just curious if this has the same issue with bluetooth headphone calling as some other roms for this phone?
Click to expand...
Click to collapse
For the moment yes, we all use same dt so bugs are shared, we are working on it
juampapo546 said:
For the moment yes, we all use same dt so bugs are shared, we are working on it
Click to expand...
Click to collapse
dt?
but thank you for letting me know, thats very helpful
Reece's Puffs said:
dt?
but thank you for letting me know, thats very helpful
Click to expand...
Click to collapse
Device tree, it would be like the specific device Configuration, that's the difference between an evert and an ali rom (Plus vendor and kenel)
Am using this rom from a month ago, and honestly everything is so perfect. And I couldn't find any bugs in daily routine usage.
Untill I travelled from one city to other and when signals started gain/drop scene, my phone automatically was restarting after every few minutes.
And another thing it makes my game crash while playing ?
Okay am reediting to add another bug.
Whatsapp calls are perfectly working on speaker and wired handsfree. But cellular calls are only working on phone speaker but not on wired handsfree. And in case my handsfree is plugged in and I got a call, no audio will progress on both sides even if I unplug handsfree at that time.
Sometime "Settings" gets crash too.
haris.sdq said:
Am using this rom from a month ago, and honestly everything is so perfect. And I couldn't find any bugs in daily routine usage.
Untill I travelled from one city to other and when signals started gain/drop scene, my phone automatically was restarting after every few minutes.
And another thing it makes my game crash while playing
Okay am reediting to add another bug.
Whatsapp calls are perfectly working on speaker and wired handsfree. But cellular calls are only working on phone speaker but not on wired handsfree. And in case my handsfree is plugged in and I got a call, no audio will progress on both sides even if I unplug handsfree at that time.
Sometime "Settings" gets crash too.
Click to expand...
Click to collapse
I'm aware of the incoming call on headset/bt bug. However i never experienced the signal drop of this rom, maybe check on the guide i've made for a similar issue (It's on the Moto g6 plus guides section)
If you discover any other bug please share me a log
Thank you for responding.
Actually its not a signal problem with this ROM, but where i live in Pakistan so on highways we experience signal drops from cellular towers.
And problem with this ROM is when signals get up and down phone gets restart repeatedly.
Or in simple words when signals are auto switching between 2G, 3G and 4G it gets restart.
And also please guide me how to share logs ?
Microphone is working?
Jonathas S said:
Microphone is working?
Click to expand...
Click to collapse
Yes its working after you switch off Voice Match "Hey Google" in your Assistant setting.
A noob question! Since you don't have VoLTE line it may never be incuded in the ROM. Correct? That being the case, is it possible for you to take the module from other moto devices or say if i could send you my phone's image, could you add the module to rom? It would be really helpful. Eversince I uncloed my device, every update makes me reset the phone and gets stuck on bootloop. It's very time consuming and beats the hell out of me
Hi, sorry for cross posting. Just installed LineageOS and noticed the problem about the Bluetooth calling issue. Thought I'd install this one, but read that it has the same problems. Does anyone here have an update on that? Anything I can do to help?
CAST to SmartTV
Hello, very nice job! CAST work? Mirroring?
haris.sdq said:
Thank you for responding.
Actually its not a signal problem with this ROM, but where i live in Pakistan so on highways we experience signal drops from cellular towers.
And problem with this ROM is when signals get up and down phone gets restart repeatedly.
Or in simple words when signals are auto switching between 2G, 3G and 4G it gets restart.
And also please guide me how to share logs ?
Click to expand...
Click to collapse
Connect your phone yo pc, give adb acces to it and on the power shell (in adb folder) run
adb logcat -d > log.txt
and share me the log.txt file that will appear in your adb folder, it's important to take the log while the error is happening
sani23 said:
A noob question! Since you don't have VoLTE line it may never be incuded in the ROM. Correct? That being the case, is it possible for you to take the module from other moto devices or say if i could send you my phone's image, could you add the module to rom? It would be really helpful. Eversince I uncloed my device, every update makes me reset the phone and gets stuck on bootloop. It's very time consuming and beats the hell out of me
Click to expand...
Click to collapse
Atm we haven't found a workaround for volte, maybe I'll look into it once other bugs are solved
WhistlerNL said:
Hi, sorry for cross posting. Just installed LineageOS and noticed the problem about the Bluetooth calling issue. Thought I'd install this one, but read that it has the same problems. Does anyone here have an update on that? Anything I can do to help?
Click to expand...
Click to collapse
Most bugs are shared because we use the same device source (I base on joshua's work, lineage maintainer). As soon as this issue is solved I'll upload the build and add it to the changelog
Hello together,
I flashed the ROM yesterday and everything is working extremly good except one thing. Normal phone calls are not working. Everytime I do a call it says that the phone call is initializing but it hangs up at that point. If I try to close the call it just says that the call is closed but nothing happens. I have to restart the phone completely. I come from Lineage OS 17.1 and I the phone call issue was there too. Any idea how I can get it back to working? Things I tried:
- Other Dialer apps with setting them to standard with every right they need
- Deactivate auto search network and set the correct provider
- Setting LTE to default
I added two logfiles but i had to shorten it a little bit because of the size for free users. I hope it's enough.
Outgoing Call:
https:// pastebin.com / aGM9WV5S
Canceling Call:
https:// pastebin.com / wc54K0A7
Edit: Sry for insert spaces in the links but under 10 posts you can't post links.
ceroc said:
Hello together,
I flashed the ROM yesterday and everything is working extremly good except one thing. Normal phone calls are not working. Everytime I do a call it says that the phone call is initializing but it hangs up at that point. If I try to close the call it just says that the call is closed but nothing happens. I have to restart the phone completely. I come from Lineage OS 17.1 and I the phone call issue was there too. Any idea how I can get it back to working? Things I tried:
- Other Dialer apps with setting them to standard with every right they need
- Deactivate auto search network and set the correct provider
- Setting LTE to default
I added two logfiles but i had to shorten it a little bit because of the size for free users. I hope it's enough.
Outgoing Call:
https:// pastebin.com / aGM9WV5S
Canceling Call:
https:// pastebin.com / wc54K0A7
Edit: Sry for insert spaces in the links but under 10 posts you can't post links.
Click to expand...
Click to collapse
First of all, please install the official version found at pixelexperience.org/evert
Secondary, to make calls disable VoLTE for now
juampapo546 said:
First of all, please install the official version found at pixelexperience.org/evert
Secondary, to make calls disable VoLTE for now
Click to expand...
Click to collapse
Thanks for the quick answer! I used the official plus edition from your site for flashing. Disabling VoLTE worked. I totally forgot what VoLTE means pronounced... It makes now sense why everybody is asking about it. Sorry for bothering you and keep on the good work. Never had less problems with Pixel Experience than with other roms.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
Gapps (Download from here)
Magisk for root - (Download from here)
First time installation:
Download Rom, Gapps & Magisk (If you want ROOT)
Reboot to recovery
Format data
Flash Rom, optional Gapps & Magisk
reboot and enjoy
Sources: https://gitlab.com/samsung_s5neolte
Known issues:
you tell me
Credits goes to:
LineageOS
Community
Download
july 2022
dummy2
Wow thanks
after flash im missing keyboard and messaging apps, flashed with and without gapps, same result, even after manual install of any keyboard app, system does not recognize them.
sanczooo said:
after flash im missing keyboard and messaging apps, flashed with and without gapps, same result, even after manual install of any keyboard app, system does not recognize them.
Click to expand...
Click to collapse
strange, here is all working, screenshot is seconds ago taken
Hello, great rom, congratulations on work, I have a problem with bluetooth, after pairing the device, after 1-2 seconds it disconnects the device.
jreneusz said:
Hello, great rom, congratulations on work, I have a problem with bluetooth, after pairing the device, after 1-2 seconds it disconnects the device.
Click to expand...
Click to collapse
confirmed, will take a look.
no bug, more a special thing with android 11, when you connect two phones enable "Settings > Network and Internet > Hotspot and tethering > Bluetooth tethering" on both phones.
my jabra speak 510 works instantly without anything special. see pictures.
dont know what you are do with bluetooth, but if you have wifi in your location its way faster to share files with kdeconnect(is in playstore/fdroid), directly from device to device or pc ;-)
I have no idea on where to start. You were the first who actually did an >android9 rom (all android 10 and 11 ones i've tried failed) to SM-G903M. But it doesn't stops right there.
-Performance is amazing. It feels even faster than CrDroid in galaxy S7 (my older, now screen-damaged, phone).
-Battery control levels (battery economy/balanced/performance) in battery settings keep true to what they promise. Battery economy keeps only 4 of the 8 cortex-a53 small cores on, to a 1ghz maximum, balanced delivers excellent performance and battery life, performance is excellent for compression and other tasks but with a higher power draw
-Memory management is excellent, something vital in a 2gb ram phone.
-Noop as default I/O
-ROM is so slim, even after gapps, trashing with all possible apps, custom whatsapp, and all kinds of addons, i still have 2GB of my 16GB space left, something IMPOSSIBLE on stock ROMs.
-Face unlock is smooth, fast, precise.
-No bugs as of now
I'm really asking myself if you don't actually use this phone daily, because the level of attention to details (geekbench even shows the phone in this ROM performance rivaling the j7 and exynos 7870 which is a faster chip) is amazing. Even the onscreen button toggle works (not using them btw), something which failed miserably for me in crdroid and dotOS from galaxy s7. I can't stress out how grateful i am, i thought i would never leave android 6 because my model (sm-g903m) was not compatible with other ROMs. I will update to android 12 if you make it happen for us again, sm-g903m, sm-g903f, sm-g903w, all included, as some developers (you an exception) seem to forget there are users worldwide who do not own american models
Thank you so much. If you need any actual help with anything, spreading the news about your ROM with a youtube video review in my native language and in clear english, i can do it. Just PM me.
Everything working great
Does this ROM have FM-radio?
evil-god said:
confirmed, will take a look.
no bug, more a special thing with android 11, when you connect two phones enable "Settings > Network and Internet > Hotspot and tethering > Bluetooth tethering" on both phones.
my jabra speak 510 works instantly without anything special. see pictures.
dont know what you are do with bluetooth, but if you have wifi in your location its way faster to share files with kdeconnect(is in playstore/fdroid), directly from device to device or pc ;-)
View attachment 5450975View attachment 5450977
Click to expand...
Click to collapse
Thanks for the answer, will try kdeconnect.
bluetooth works.
How's the mic working on this ROM, is it also very low in calls?
I might test after I play around with the LOS a bit more, see if I can get it to work there.
wvanstraalen said:
How's the mic working on this ROM, is it also very low in calls?
I might test after I play around with the LOS a bit more, see if I can get it to work there.
Click to expand...
Click to collapse
I just tested this ROM yesterday and unfortunately mic works in the same manner as in LOS 17.1 and LOS 18.1
I just don't get - how it is that some people here report that everything works perfectly and some can't have regular phone calls. MICGAIN patches do not work. S5 Neo lifevibes by danwood76 work only in v2 (still not close to stock quality). Speakerphone completely dead.
My device is SM-G903F (European distribution), maybe there is some difference in microphone hardware values between different devices distributions? It seems as if those custom ROMs mic programming has way too low values for mic input compared to mic hardware.
Hey devs, is there any chance to fix this problem? I volunteer to test any solutions and report them back here for future reference.
Thanks
Mike-san said:
I just tested this ROM yesterday and unfortunately mic works in the same manner as in LOS 17.1 and LOS 18.1
I just don't get - how it is that some people here report that everything works perfectly and some can't have regular phone calls. MICGAIN patches do not work. S5 Neo lifevibes by danwood76 work only in v2 (still not close to stock quality). Speakerphone completely dead.
My device is SM-G903F (European distribution), maybe there is some difference in microphone hardware values between different devices distributions? It seems as if those custom ROMs mic programming has way too low values for mic input compared to mic hardware.
Hey devs, is there any chance to fix this problem? I volunteer to test any solutions and report them back here for future reference.
Thanks
Click to expand...
Click to collapse
thx for reporting, i will take a look
edit: my device is a SM-G903F too, today my GF and me switch the phone, make several calls, then switch back, do some test calls, everything work for both sides normal, cant reproduce any issue.
anyone else with this problem?
evil-god said:
thx for reporting, i will take a look
edit: my device is a SM-G903F too, today my GF and me switch the phone, make several calls, then switch back, do some test calls, everything work for both sides normal, cant reproduce any issue.
anyone else with this problem?
Click to expand...
Click to collapse
Hi,
Didn't know you replied by editing. Been too busy during whole week to take a closer look on this thread.
Thanks a lot for trying to figure out what's going on. This is really strange that you did not experience any issues during phone calls - what distribution your phone is? I've read that there may be some differences between different distributions around the world in hardware configuration. I discarded version of mic malfunction - before swithing to LOS 17.1 and 18.1 and CrDroid there were not problems with phone calls, audio recording and camera recording with stock ROM.
I am not exaggerating about this issue - wvanstraalen also reported this problem and there had been numerous reports in this thread https://forum.xda-developers.com/t/...c-gain-and-a-little-speaker-gain-too.3491483/ but they do not apply to Android 11.
Is there any way to compile a file/files which would contain insight info about how mic behaves in different circumstances and how mic values in mixer paths are fixed? I don't know if I am precise at the moment - I just write what my guts tell me what may be wrong with my and some people's devices. There must be some way to fix this. Or maybe there are people who have some practical knowledge about this issue. I do not expect miracles, but if you could point what could possibly done I'd be very grateful. If not - maybe there are some devs here who have dealt with this issue with different Samsung devices?
Kind regards,
Mike
evil-god said:
Download
december 2021
Click to expand...
Click to collapse
Thanks.
Some very significant performance improvements seem to have been achieved from the first version to the january 2022 update. Cores now seem to be able to turn off in heavy multitasking, such as with YouTube music, browser alongside facebook app as the first open app. This was impossible in the old ROM version. It may help with temperatures and prolong new third party batteries lifespan (not speaking about the more expensive ones but the ones below 10usd sold for the original galaxy s5 but compatible with the s5 neo, for those who ask themselves which ones i'm talking about. I highly distrust new batteries claiming higher capacity than the original as well)
After flash im missing data network, I have a G903M, anyone else with this problem?
I'm at the end of my rope here and I'm loosing patience with this very strange problem:
Some time ago, I received a HTC U11 from a friend. Since I came from a impenetrable (AT&T locked) Samsung Galaxy S7, I didn't bother testing the U11 before tinkering with it. I missed the freedom of a custom OS so much, that I just wanted that back again. So I don't know if the phone had worked with the originial software on it.
Naturally and right away, I unlocked it, flashed TWRP (3.6.1_9_0) , LineageOS 18.1 (2022-02-19), as well as Magisk (v24.3) and a core version of the GApps (NikGapps Core ARM64 2021-05-01) as to bloat my system as little as possible.
Now, everything seemed to be in working order. I can install and use any app like I would normally. Strangly enough, I can even send and receive speech messages in WhatsApp (haven't tried any other messenger app though).
However, if I try to make a phone call (through 3rd party apps like WhatsApp as well as "classical" phone calls alike) there won't be any audio, in neither directions from either source. Can somebody just...... I'm not that much of a noob, usually, so, HOW?
Starting out, I had another issue that a call (incoming or outgoing) would not be visible even in the task manager. I could solve the issue by reapplying a "special permission" to the phone app so it was allwed to pose itself on top of the other layers. Still, there was no audio - so could it have something to do with permissions?
Or am I missing an important (background) up with the core version of the GApps?
What I've tried so far:
- All the wipes up to and including a complete factory reset.
- Superficially checking, if I missed something during installation (nothing immediate springs to mind).
- Trying a different phone app (contacts+).
- Checking permissions of phone app.
- Trying loudspeaker and normal speaker settings.
- Using a land line to connect to my phone to check if there's any audio in either direction.
- Banging my head against the wall...!
Please help me find the reason behind this issue. It's just completely non-sensical to me that I can send and receive audio messages but my audio doesn't work during calls in both ways.
I have that same problem.
I tried 5 different custom roms, I tried the kernel, it didn't work.
everything is working, only the sound on the phone call is neither going nor coming. same as normal earphone with bluetooth earphone.
audio recording in video recording, music working, microphone recording sound, but no sound in calls. There is an imei signal, but there is no solution.
Even emergency calls have the same problem.
why could it be?
Thank You for replying, OnlineBeyin!
And here I thought, I was completely alone in this. At least there's someone out there sharing the pain!
Well, here's to a strage new Problem.
In a funny way, I love this about digital technology; it never gets boring - as soon as you'd think you've got your stuff figured out, along comes a curious problem you've never heard of or even expected to be possible.
I havent found a solution yet but having someone with the same problem gives me hope, maybe together we can work it out.
I don't think it's about the custom ROMs since You tried five of them to no avail. What do You mean by "trying a kernel"?
I've come to terms with it since I kind of enjoy the silence that not being able to answer calls has provided, but there is some other strange behaviour that might hint at a possible solution I have not yet explored:
I've taken a look at the NikGApps package I was using (core) and I've realised that
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I might need the basic version, since the core version does not provide an obvious dialer (What does "AOSP" stand for?) nor "Google Carrier Services", both of which seem quite important for phone calls.
Now me being a rather lazy fellow by nature, I thought I could just install the basic version over the the core version. In doing that, the clock app stopped working. I don't know why but opening it leads to the app crashing.
I've just seen Your post so I wanted to reply first rather then try a bunch of stuff and keep you waiting for an answer, but that's where I'm at.
So this strange behaviour (not being able to open the clock app) leads me to belive that...
<TL;DR>
Could there be an issue with different versions of programs running in the background?
(My point being Android is basically a customized version UNIX which has some similarities with Linux with which I have some modest experience with.
There I've experienced such issues around the OS telling me (paraphrasing) "the thing You want won't work like that because it is dependent on something that cannot be resolved automatically. You gotta have this version of that other thing to talk to that version of yet another thing and you have to solve that first. Then it'll work.")
So, long story short,
just to rule out this source of error, the next thing I'm going to try is to make a clean install with the full and original Version of GApps just to see if it'll work and go from there. If that won't help, I'll find out if there is something like the bash terminal from Linux just so I can see what the phone is doing exactly.
I hope this helps, if at least to spark an idea from somebody, anybody else!
I really want to get this phone working at some point, if only for sustainability's sake!
hi mate, still having the same problem...
Here's what I've tried and what I'm sure of
I tried turning off features such as google assistant voice listening and it didn't work.
I tested multiple microphones in the device with hardware test programs and the speaker that acts as a handset and it works fine.
The device is calling the other party, sending sms, just because there is a voice exchange problem, I have no doubts about imei etc.
It's purely a software issue. it's so clear
The first thing I would try would be to go back to the original rom. I haven't tested this before.
I also think that the device may have different criteria according to different countries, so there may be a conflict. But I don't think I made a lot of mistakes, to be honest.
It's very important to me that you share your every attempt.
I really want to operate this device. It's my favorite device.
In the meantime, I opened the device and tried to change the transmission films. I tried changing the bottom charging port. These are not solutions.
Hi
Cyberfreak1992 said:
I'm at the end of my rope here and I'm loosing patience with this very strange problem:
Some time ago, I received a HTC U11 from a friend. Since I came from a impenetrable (AT&T locked) Samsung Galaxy S7, I didn't bother testing the U11 before tinkering with it. I missed the freedom of a custom OS so much, that I just wanted that back again. So I don't know if the phone had worked with the originial software on it.
Naturally and right away, I unlocked it, flashed TWRP (3.6.1_9_0) , LineageOS 18.1 (2022-02-19), as well as Magisk (v24.3) and a core version of the GApps (NikGapps Core ARM64 2021-05-01) as to bloat my system as little as possible.
Now, everything seemed to be in working order. I can install and use any app like I would normally. Strangly enough, I can even send and receive speech messages in WhatsApp (haven't tried any other messenger app though).
However, if I try to make a phone call (through 3rd party apps like WhatsApp as well as "classical" phone calls alike) there won't be any audio, in neither directions from either source. Can somebody just...... I'm not that much of a noob, usually, so, HOW?
Starting out, I had another issue that a call (incoming or outgoing) would not be visible even in the task manager. I could solve the issue by reapplying a "special permission" to the phone app so it was allwed to pose itself on top of the other layers. Still, there was no audio - so could it have something to do with permissions?
Or am I missing an important (background) up with the core version of the GApps?
What I've tried so far:
- All the wipes up to and including a complete factory reset.
- Superficially checking, if I missed something during installation (nothing immediate springs to mind).
- Trying a different phone app (contacts+).
- Checking permissions of phone app.
- Trying loudspeaker and normal speaker settings.
- Using a land line to connect to my phone to check if there's any audio in either direction.
- Banging my head against the wall...!
Please help me find the reason behind this issue. It's just completely non-sensical to me that I can send and receive audio messages but my audio doesn't work during calls in both ways.
Click to expand...
Click to collapse
I had the same Issue with the sound in Calling etc... , this is a Problem with the DSP and when you use a CustomROM than use LineageOS_18.1-for_OREr_PIE_firm_with_DSP_patch-monthly_builds and after install ROM you must Flash this HTC_U11_DSP_TWRP_Flashable_OREO_2.33.401.19_install.zip that Fixes my Audio Problem and its work fine.
when you would more you find it here, HTC U11 - CustomROMs all with DSP Patch
Happy new year, everyone!
System23 said:
Hi
I had the same Issue with the sound in Calling etc... , this is a Problem with the DSP and when you use a CustomROM than use LineageOS_18.1-for_OREr_PIE_firm_with_DSP_patch-monthly_builds and after install ROM you must Flash this HTC_U11_DSP_TWRP_Flashable_OREO_2.33.401.19_install.zip that Fixes my Audio Problem and its work fine.
when you would more you find it here, HTC U11 - CustomROMs all with DSP Patch
Click to expand...
Click to collapse
With great pleasure I'm here to announce:
Can confirm this works! Just tried it today, the patch straightforwadly fixes this issue.
I had to skip the integrity check in TWRP to be able install it, but that should be obvious.
I already lost hope.
All the thanks and all the glory definately go to System23!