No service while charging - Moto G5 Plus Questions & Answers

Hi I am using Moto g5 plus from past one year. I have rooted and on custom rom now.
my phone loses the network signal while charging and I have to restart the phone to get back the signal again. It happens every time I charge the battery.
Can anyone help me in solving the issue.
From the daily observations:
I use turbo charger and whenever my phone gets heated up that time I lose the network signal and shows no service at status bar.

have you tried doing a clean flash? are you using any custom kernel?

M1810 said:
have you tried doing a clean flash? are you using any custom kernel?
Click to expand...
Click to collapse
yes, i am using custom rom andriod p dp5 with ace kernal

R3dblue said:
yes, i am using custom rom andriod p dp5 with ace kernal
Click to expand...
Click to collapse
So that's an issue you should bring up in the thread for that rom. It's still new, and it's a treble rom, and treble should probably still be considered beta, with all due respect to the Devs who are working on it.

If you are newbie you should go for Oreo roms now, Best one is Havoc
P's only DP version is out so its underdevelopment till date.

Now it's also happening on the stock ROM too. May be it's an internal hardware issue. It works when I hit the phone on the back near sim tray which is connected to other parts

Sounds like a bad connection, could be a solder joint or a plug together connector, maybe a pin not inserted correctly during manufacture.

Related

Bluetooth borked

I'll try to keep this brief, but backstory is necessary.
Original Nexus 4 came in, bluetooth often would refuse to connect to paired devices without rebooting the phone (or power-cycling the other device oddly). This was on stock. Flashed AOKP milestone 2 at some point and problem persisted.
Original Nexus 4 data port broke, RMAed and got a new one (now with nipples!). Flashed the same AOKP milestone and whoa, bluetooth works wonderfully now. Always connects immediately, amazing!
Fast forward to yesterday, I flash the new AOKP 4.3 build along with a new radio at a knowledgable user's suggestions (filename radio-mako-m9615a-cefwmazm-2.0.1700.84.zip). I'm right back to where I started with bluetooth refusing to connect half the time. Now I KNOW it's not a hardware issue because it worked on this new Nexus until yesterday.
Is this a kernel issue or could it be the radio? Recommendations on what to flash to get my bluetooth working again?
Headcase_Fargone said:
I'll try to keep this brief, but backstory is necessary.
Original Nexus 4 came in, bluetooth often would refuse to connect to paired devices without rebooting the phone (or power-cycling the other device oddly). This was on stock. Flashed AOKP milestone 2 at some point and problem persisted.
Original Nexus 4 data port broke, RMAed and got a new one (now with nipples!). Flashed the same AOKP milestone and whoa, bluetooth works wonderfully now. Always connects immediately, amazing!
Fast forward to yesterday, I flash the new AOKP 4.3 build along with a new radio at a knowledgable user's suggestions (filename radio-mako-m9615a-cefwmazm-2.0.1700.84.zip). I'm right back to where I started with bluetooth refusing to connect half the time. Now I KNOW it's not a hardware issue because it worked on this new Nexus until yesterday.
Is this a kernel issue or could it be the radio? Recommendations on what to flash to get my bluetooth working again?
Click to expand...
Click to collapse
Try reflashing the ROM with a data wipe. If the problem persists, then it's either a ROM issue, or your bluetooth chip is malfunctioning again (Which is improbable).
I was hoping perhaps someone would say "Oh that sounds like a radio issue. Just flash this one and you should be good."
Oh well, I guess I'll put up with it for now and do a factory wipe when AOKP releases a milestone 4.3 or something.
Headcase_Fargone said:
I was hoping perhaps someone would say "Oh that sounds like a radio issue. Just flash this one and you should be good."
Oh well, I guess I'll put up with it for now and do a factory wipe when AOKP releases a milestone 4.3 or something.
Click to expand...
Click to collapse
Bugs in nightly builds are very common. If you want to be sure, flash the stock rooted ROM, and check if the problem is a hardware one.
And yeah, the radio is most probably not causing any problems, since most of us use the latest one with no problems.
abaaaabbbb63 said:
Bugs in nightly builds are very common. If you want to be sure, flash the stock rooted ROM, and check if the problem is a hardware one.
And yeah, the radio is most probably not causing any problems, since most of us use the latest one with no problems.
Click to expand...
Click to collapse
I was actually having this same problem with stock 4.2.2, CM10.1, and AOKP Milestone2 on the first phone. Didn't have the problem with AOKP Milestone2 on the new phone, but am now with the new 4.3 preview build. Really frustrating. Oh well, I'll keep flashing clean until it works. Thanks.

[GUIDE] Install CloudyG2 3.3 on VS980

First of all I'd like to thank the following forum members for their contributions:
@Zackptg5 and @megaghostgamer for their basic steps
@xdabbeb for his bootstack
Major thanks to @Cloudyfa for his amazing ports!
I've compiled their steps into a very user friendly guide with all downloads in one place.
I recommend TWRP for the procedure. Any version 2.7.0.0 or above should do.
First of all, you need these files:
Dorimanx 3.9.2 kernel vs980 (Make sure you download the kernel for the VS980)
Aroma Patch Fix
CloudyG2 3.3
xdabbeb's vs980 39a bootstack
Then, follow the steps carefully. I am not responsible if this didn't work for you as it did for me.
Backing up is recommended, nandroid or data backups.
Boot your phone into TWRP. (Recommended method is going to recovery after turning off the device)
Wipe everything except internal storage.
Flash Xdabebbeb's VS980 39A bootstack.
Reboot the device into recovery (there should be an option for this in the reboot section of TWRP).
Flash CloudyG2 3.3 and make sure you select your variant as VS980. Make sure you uncheck the reboot option at the end of the installation.
Flash the Aroma Patch Fix zip, and select your variant as VS980. Make sure you uncheck the reboot option at the end of the installation.
Flash the VS980 39A bootstack once more.
Flash the Dorimanx 3.9.2 kernel zip.
Wipe cache/dalvik cache.
Reboot the device to system.
Notes:
First boot usually takes awhile. The pulsing LED will show up for a long time with the LG Logo.
Mobile Data does not work unless you enable data roaming.
Please hit that thanks button if this guide helped any of you! Any questions, just post down below.
I have followed everything as it has been mentioned in the guide.
When i rebooted the system in the end, LG logo appeared for a second and then black screen with [880] Fastboot mode started.
now what should i do ? its just stuck here.
Shujja Haider said:
I have followed everything as it has been mentioned in the guide.
When i rebooted the system in the end, LG logo appeared for a second and then black screen with [880] Fastboot mode started.
now what should i do ? its just stuck here.
Click to expand...
Click to collapse
You flashed the kernel for the wrong variant. Flash the one for the vs980, its towards to bottom of the download page. You can still boot into recovery by following this guide: http://forum.xda-developers.com/showthread.php?t=2534981
Zackptg5 said:
You flashed the kernel for the wrong variant. Flash the one for the vs980, its towards to bottom of the download page. You can still boot into recovery by following this guide: http://forum.xda-developers.com/showthread.php?t=2534981
Click to expand...
Click to collapse
oh yes.. my bad.. the kernel was mistakenly downloaded from LS980 instead of VS980. again followed the process and it is starting up.
lets hope reception problem is fixed.
Shujja Haider said:
oh yes.. my bad.. the kernel was mistakenly downloaded from LS980 instead of VS980. again followed the process and it is starting up.
lets hope reception problem is fixed.
Click to expand...
Click to collapse
Easy mistake to make (I did that too once). It'll say you're roaming, but that's just a weird bug. Go into networks setting and enable data while roaming and it'll work fine. You're not actually roaming so you won't get charged for it.
Oh well. Added an extra precaution next to the download link.
Zackptg5 said:
Easy mistake to make (I did that too once). It'll say you're roaming, but that's just a weird bug. Go into networks setting and enable data while roaming and it'll work fine. You're not actually roaming so you won't get charged for it.
Click to expand...
Click to collapse
I did everything correctly now .. even the enable data while roaming is checked.
I am receiving a few bars of reception but neither i am able to receive calls or make calls .. first time there was message emergency calls only but now .. nothing ..
very rarely calls or messages are received while most of the time .. just nothing .. no incoming or outgoing
Shujja Haider said:
I did everything correctly now .. even the enable data while roaming is checked.
I am receiving a few bars of reception but neither i am able to receive calls or make calls .. first time there was message emergency calls only but now .. nothing ..
very rarely calls or messages are received while most of the time .. just nothing .. no incoming or outgoing
Click to expand...
Click to collapse
These things also happened to me
My phone is unusable now
Even after i restored my backup from twrp
Please anyone
How you cell is unusable now?
I am not able to access to network.. No data connection at all.. Other than that.. Charging is seriously slow...
Sent from my VS980 4G using XDA Free mobile app
Shujja Haider said:
How you cell is unusable now?
I am not able to access to network.. No data connection at all.. Other than that.. Charging is seriously slow...
Sent from my VS980 4G using XDA Free mobile app
Click to expand...
Click to collapse
Flash xdabbebs rom: http://forum.xda-developers.com/showthread.php?t=2715408
It is stock with some tweaks, g3 ported apps and such. If you still have these issues, it's likely a hardware issue
You mean I should not use cloudyG2 3.3?
But if it is hardware issue then why I was not facing it other ROMs?
Sent from my VS980 4G using XDA Free mobile app
Shujja Haider said:
You mean I should not use cloudyG2 3.3?
But if it is hardware issue then why I was not facing it other ROMs?
Sent from my VS980 4G using XDA Free mobile app
Click to expand...
Click to collapse
Im saying that the hardware issue could have just developed and an easy way to test that is with flashing a stockish rom. If it's a software issue, than you'll have no problems with it. I've never had signal issues with Cloudys rom on my vs980
Zackptg5 said:
Im saying that the hardware issue could have just developed and an easy way to test that is with flashing a stockish rom. If it's a software issue, than you'll have no problems with it. I've never had signal issues with Cloudys rom on my vs980
Click to expand...
Click to collapse
No i had signals issues before and in this room the issue seemed to have worsen but i think its okay .
but the real issue now is .. extremely extremely slow charging .. even tweaking the kernel with fast charging at 2000mAH.. its such a lazy charging .. you can imagine .. for more than 2.5 hours, the charging has just been moved from 12% to 34%.
not using at all .. only charging .. how to resolve this issue ??
Shujja Haider said:
No i had signals issues before and in this room the issue seemed to have worsen but i think its okay .
but the real issue now is .. extremely extremely slow charging .. even tweaking the kernel with fast charging at 2000mAH.. its such a lazy charging .. you can imagine .. for more than 2.5 hours, the charging has just been moved from 12% to 34%.
not using at all .. only charging .. how to resolve this issue ??
Click to expand...
Click to collapse
Try uninstalling the apps installed with dormant kernel (color changed, synapse, dorimanx kernel settings) forget the names for them but you'll figure it out. Then flash xdabbebs stock kernel (permissive): http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560
If the slow charge is still present, then it's likely a hardware issue. Sounds like you need a new phone with all of the problems you're having. Have you tried cleaning out the charging port with compressed air?
Zackptg5 said:
Im saying that the hardware issue could have just developed and an easy way to test that is with flashing a stockish rom. If it's a software issue, than you'll have no problems with it. I've never had signal issues with Cloudys rom on my vs980
Click to expand...
Click to collapse
Zackptg5 said:
Try uninstalling the apps installed with dormant kernel (color changed, synapse, dorimanx kernel settings) forget the names for them but you'll figure it out. Then flash xdabbebs stock kernel (permissive): http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560
If the slow charge is still present, then it's likely a hardware issue. Sounds like you need a new phone with all of the problems you're having. Have you tried cleaning out the charging port with compressed air?
Click to expand...
Click to collapse
you probably are right that i might need a new phone but i had just got this one and charging was okay with kitkat based ROMS.. like i was using CloudyFlex before and no issue but only with this rom i had this issue. and I had not tried compressed air cleaning at all .. i think i must consider changing the kernel .. it might save the issue..
Zackptg5 said:
You flashed the kernel for the wrong variant. Flash the one for the vs980, its towards to bottom of the download page. You can still boot into recovery by following this guide: http://forum.xda-developers.com/showthread.php?t=2534981
Click to expand...
Click to collapse
Where did you get that version of Dorminax or can you use a later version of that Kernel
Shujja Haider said:
you probably are right that i might need a new phone but i had just got this one and charging was okay with kitkat based ROMS.. like i was using CloudyFlex before and no issue but only with this rom i had this issue. and I had not tried compressed air cleaning at all .. i think i must consider changing the kernel .. it might save the issue..
Click to expand...
Click to collapse
I'm thinking that the first install of the wrong kernel did some stuff.
Try backing up your stuff, using LG Tool to restore back to stock, and retry the procedure. I'm coming straight off of Resurrection Remix 5.1.1 and I've had no issues with this ROM. Data works without enabling Roaming too.
TheSkilledPlaya said:
I'm thinking that the first install of the wrong kernel did some stuff.
Try backing up your stuff, using LG Tool to restore back to stock, and retry the procedure. I'm coming straight off of Resurrection Remix 5.1.1 and I've had no issues with this ROM. Data works without enabling Roaming too.
Click to expand...
Click to collapse
LG Tool doesnt take me back to stock.. i have to manually flash stock ROM for this ..
actually I had mentioned before, i was already facing severe signals issues and not to forget, GPS is also faulty.
so might be hardware issue that is continued in this ROM too.
But what has been added is .. extremely slow charging .. charging is totally dead.
Using Dorimanx Kernel v 4.6.
even enabled fast charging at 1800 but no effect at all ..
Shujja Haider said:
LG Tool doesnt take me back to stock.. i have to manually flash stock ROM for this ..
actually I had mentioned before, i was already facing severe signals issues and not to forget, GPS is also faulty.
so might be hardware issue that is continued in this ROM too.
But what has been added is .. extremely slow charging .. charging is totally dead.
Using Dorimanx Kernel v 4.6.
even enabled fast charging at 1800 but no effect at all ..
Click to expand...
Click to collapse
I thought my guide mentioned version 3.9.2..
Well if this ROM doesn't work out for you, stay on CloudyG2 2.2. It's the most stable ROM we have for our VZW G2 out there.
TheSkilledPlaya said:
I thought my guide mentioned version 3.9.2..
Well if this ROM doesn't work out for you, stay on CloudyG2 2.2. It's the most stable ROM we have for our VZW G2 out there.
Click to expand...
Click to collapse
I think so its not working out well .. though i have loved it .. its interface and everything but i have faced so many issues and now i am observing videos are not being played at all ..even tried installing MX Player but same issue..
tonight i am going to flash debloated Stock lollipop cuz i want to use LP .. if it doesn't work out .. then i will revert back to CloudyFlex cuz that was working fine too ..
CloudyG2 and CloudyFlex.. are they the same or different .. i am sorry for my ignorance but these both roms were downloaded by one of my friend so I didn;t keep a check..

All X820 phone problem caused by flashing/rooting

After using this phone for few months with everything sick and untouched, I can finally say that every single problem ranging from fingerprint, boot loop, etc is caused by flashing/rooting. Discuss...
kkcheong said:
After using this phone for few months with everything sick and untouched, I can finally say that every single problem ranging from fingerprint, boot loop, etc is caused by flashing/rooting. Discuss...
Click to expand...
Click to collapse
There just aren't a lot of super stable ROMs developed for this phone. Every custom Rom has charging issue, camera issue, location issue, Network signal issue. If your boot looping it's because you didn't flash right or changed some system files. After rooting fingerprint broke for me for 3 months than suddenly started working again. Stock rom is still the most stable available. But people are sick of eui the ram management is terrible. That's why they root and flash custom ROMs. If you flash a rom and are having issues move to another custom Rom or wait for an update to fix the problem. I'm rambling.
?
allrockedout said:
There just aren't a lot of super stable ROMs developed for this phone. Every custom Rom has charging issue, camera issue, location issue, Network signal issue. If your boot looping it's because you didn't flash right or changed some system files. After rooting fingerprint broke for me for 3 months than suddenly started working again. Stock rom is still the most stable available. But people are sick of eui the ram management is terrible. That's why they root and flash custom ROMs. If you flash a rom and are having issues move to another custom Rom or wait for an update to fix the problem. I'm rambling.
Click to expand...
Click to collapse
I have a different experience. Custom rom since day one. Phone charges crazy fast, faster than eui, the only camera issue is flash desync on some apps, location and network works great every time. Fingerprint at least on my rom is much faster than eui. Never ever had a problem after rooting or flashing a phone, it's always the user's fault not doing something right like not updating firmware or something
KuranKaname said:
I have a different experience. Custom rom since day one. Phone charges crazy fast, faster than eui, the only camera issue is flash desync on some apps, location and network works great every time. Fingerprint at least on my rom is much faster than eui. Never ever had a problem after rooting or flashing a phone, it's always the user's fault not doing something right like not updating firmware or something
Click to expand...
Click to collapse
Which rom?
popoyaya said:
Which rom?
Click to expand...
Click to collapse
BlackX
KuranKaname said:
I have a different experience. Custom rom since day one. Phone charges crazy fast, faster than eui, the only camera issue is flash desync on some apps, location and network works great every time. Fingerprint at least on my rom is much faster than eui. Never ever had a problem after rooting or flashing a phone, it's always the user's fault not doing something right like not updating firmware or something
Click to expand...
Click to collapse
The flash desync seems to be some trouble with camera 2 API, I remember having it on eui with camera2 api, WhatsApp photos were all white

Wifi is disconnecting on screen off

So I tried 3 differents roms and all of them had the same issue and I can't fix it.
I tested with stock rom, stock kernel or blu spark kernel. I tried bliss rom and now I am using Codename Phoenix rom.
But I always have the same issue after going to Android Pie, my wifi get disconnected after a few minutes of screen off. My global wifi_sleep_policy is to always enabled but it is not working.
Does anyone have a fix for it?
archraziel said:
So I tried 3 differents roms and all of them had the same issue and I can't fix it.
I tested with stock rom, stock kernel or blu spark kernel. I tried bliss rom and now I am using Codename Phoenix rom.
But I always have the same issue after going to Android Pie, my wifi get disconnected after a few minutes of screen off. My global wifi_sleep_policy is to always enabled but it is not working.
Does anyone have a fix for it?
Click to expand...
Click to collapse
For Pie custom roms you need pie firmware too, checked that?
strongst said:
For Pie custom roms you need pie firmware too, checked that?
Click to expand...
Click to collapse
I was using stock 9.0.4 before trying the custom ROMs. Wouldn't the firmware be automatically updated ?
I will have a look into that, maybe reflash the firmware.
archraziel said:
I was using stock 9.0.4 before trying the custom ROMs. Wouldn't the firmware be automatically updated ?
I will have a look into that, maybe reflash the firmware.
Click to expand...
Click to collapse
The you have 9.0.4 firmware, but try to flash again. Also make sure it's not a custom kernel issue.
strongst said:
The you have 9.0.4 firmware, but try to flash again. Also make sure it's not a custom kernel issue.
Click to expand...
Click to collapse
My current rom is Codename Phoenix, I tried about 3 different kernel to make sure is not a kernel related.
My current baseband is mpsss.at.2.0.c4.7-00070-8998_gen_pack-2.132073.1.179387.1
If I flash the firmware/modem from OOS 9.0.5, will it break something?
archraziel said:
My current rom is Codename Phoenix, I tried about 3 different kernel to make sure is not a kernel related.
My current baseband is mpsss.at.2.0.c4.7-00070-8998_gen_pack-2.132073.1.179387.1
If I flash the firmware/modem from OOS 9.0.5, will it break something?
Click to expand...
Click to collapse
No it won't break something, you can try to update it, maybe it's running then for CNP rom
strongst said:
No it won't break something, you can try to update it, maybe it's running then for CNP rom
Click to expand...
Click to collapse
So I reflash the firmware+modem form this page
https://forum.xda-developers.com/showpost.php?p=76943628&postcount=8
I flashed the 9.0.5 version, but the problem persist, after a few minutes of screen off the wifi just disconnect and I have to unlock and enter the app to receive the notifications.
I realized the problem is that for some reason whatsapp is being killed in the background even after I put it to not be battery optimized.
Will try to make it a sysapp to see if works
archraziel said:
I realized the problem is that for some reason whatsapp is being killed in the background even after I put it to not be battery optimized.
Will try to make it a sysapp to see if works
Click to expand...
Click to collapse
Your wifi disconnects cause YouTube gets killed in the background
strongst said:
Your wifi disconnects cause YouTube gets killed in the background
Click to expand...
Click to collapse
I fixed my wifi , it was caused by some new firmware installed in the router that had a bug that caused all my devices to disconnect when idle.
The new problem now is that my apps are being closed/killed after the screen is off for a few minutes I tried to turn off Baterry Optimization but it did not work.
If I put my phone to charge this behavior does not happen my phone does not kill the apps.
archraziel said:
I fixed my wifi , it was caused by some new firmware installed in the router that had a bug that caused all my devices to disconnect when idle.
The new problem now is that my apps are being closed/killed after the screen is off for a few minutes I tried to turn off Baterry Optimization but it did not work.
If I put my phone to charge this behavior does not happen my phone does not kill the apps.
Click to expand...
Click to collapse
Thanks for the information. To help others you can mark the thread as [SOLVED] and add an info to the first post that it was your routers firmware and not the smartphone
After some time and a lot more of test I find out it wasnt my router firmware problem
The only thing that really solved the problem was installing this mod:
https://forum.xda-developers.com/oneplus-5/themes/magisk-pixel-2-wifi-mod-t3752321
Thanks and this thread can be closed now.

no signal

i tried all custom 10 roms but the signal strenght is almost nothing or no signal at all
my IMEI is still good/original, wiped logs in /persist/cache/recovery.
i upgraded to latest firmaware that works and then a full wipe to flash custom roms
am i forgetting something to do
what about stock rom?
mrsiri said:
what about stock rom?
Click to expand...
Click to collapse
stock works fine its just every custom 10 rom the signal is crap
kkdamion said:
stock works fine its just every custom 10 rom the signal is crap
Click to expand...
Click to collapse
This rules out a problem on your phone. Contact the developers of a specific custom rom, they should be the ones to fix this problem. Maybe it's common and unfixable, if every rom has this problem. On my old asus Zenfone, there was no custom rom with radio working, because asus didnt release the source code for it.
See my response to your question on the Evolution X forum. I'm not going to repost because I had attached a file to my response there.

Categories

Resources