Hello,
So I installed the new CM 11 20.01 build. While it was running flawless before a couple of hours, now I have a strange problem. The defy random tells me that there is a problem with the modem and it the defy should be restarted. What could this be?
Hardware
Sent from my MB526 using Tapatalk
cyrusct82 said:
Hardware
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
Well, I never had that problem before, can't be a faulty hardware.
dampflokfreund said:
Well, I never had that problem before, can't be a faulty hardware.
Click to expand...
Click to collapse
It is a hardware problem, but it appears randomly. It is unpredictable.
hotdog125 said:
It is a hardware problem, but it appears randomly. It is unpredictable.
Click to expand...
Click to collapse
I reinstalled the OS, now everything is working fine.
dampflokfreund said:
I reinstalled the OS, now everything is working fine.
Click to expand...
Click to collapse
Same problem here, modem error after some randomly time did rebooting didnt help.
What did you reinstall ?
Did you wipe data ?
I had no need to make a clean install to have it working, so it could be enough to flash the zip and then wipe dalvik/cache. Randomly I had that modem-error, too (in previous builds, all in all two ot three times), but after a reboot everything worked again.
#SplashmasterBee
Hi,
I have this modem problem as well.
the defy is rebooting up to 5 times a day, sometimes with "modem" message, sometimes without.
I think it's more often if mobile data is enabled.
May be it reboots on incoming calls (every second call?)
I already installed new versions of cm 10 and 11 half a dozen times.
Last time I did a complete factory wipe.
currently I am running: CM 11-20141119-nightly-mb52x (quarx)
model is mb526
I disabled usb debugging which seemed to be enabled by default.
any idea?
thanks
ps. CM11 is great!
Related
Hey friends!
I am using Mb526 for quite a while now.I am having a strange problem of signal freezing within 10-30minutes of booting the phone, cm9 was fine.. but as soon as i switched to cm10 there is a strange problem that the signal bars freeze/there is no outgoing call/the data packet doesnt work and in this case, nothing helps to get it back to working except a complete reboot. this happens suddenly and is self triggered at any point of time because of which i miss important calls and messages. i have tried to do the following
1)set the governor to conservative at default clock settings.(someone suggested this)
2)removed phone.apk and all its associated apk's from HWA's settings
Is there a patch for this? ive tried installing jellybean kernel too(in MIG edition rom but it gives me another problem that the signal is off). please someone help my poor defy :'(
Are you wiping everything (cache, dalvik, data and system) pre flashing?
Try flashing a wipe script.(search for it, it basically wipes everything for you. You have to be careful to use a script that does not wipe your sd card as well)
itsnotmeatall said:
Are you wiping everything (cache, dalvik, data and system) pre flashing?
Try flashing a wipe script.(search for it, it basically wipes everything for you. You have to be careful to use a script that does not wipe your sd card as well)
Click to expand...
Click to collapse
before every possible flash..i do factory reset twice..dalvik and battery once
esidyo said:
before every possible flash..i do factory reset twice..dalvik and battery once
Click to expand...
Click to collapse
Have you tried going back to CM9 to see if everything works as before? That way you can rule out a hardware problem.
itsnotmeatall said:
Have you tried going back to CM9 to see if everything works as before? That way you can rule out a hardware problem.
Click to expand...
Click to collapse
Everything works fine in Ms2ginger
esidyo said:
Everything works fine in Ms2ginger
Click to expand...
Click to collapse
Have you tried with all the different basebands? This was what worked for me when I was having a problem with no incoming calls. There is a baseband changer app in Play.
If that doesn't work - Since flashing a different kernel is getting you a different problem maybe you should try various kernels. One of them might work.
itsnotmeatall said:
Have you tried with all the different basebands? This was what worked for me when I was having a problem with no incoming calls. There is a baseband changer app in Play.
If that doesn't work - Since flashing a different kernel is getting you a different problem maybe you should try various kernels. One of them might work.
Click to expand...
Click to collapse
tried that.. tried jelly x kernel and switching basebands... going back to cm9.. atleast it was stable :\
esidyo said:
tried that.. tried jelly x kernel and switching basebands... going back to cm9.. atleast it was stable :\
Click to expand...
Click to collapse
Now even in cm9 it is unstable... i have seen as soon as i try to underclock it, the problem comes.. phone works fine without underclocking. even when the phone doesnt reboot... it still has that problem of signal freezing...
I have Defy with telephony layer problem. If this problem occurs with stock rom, this layer will be automaticaly restarted and phone remains connected network. I updated to Android 4.4 Kitkat for Defy and Defy+ by Quarx but at this rom, if problem with telephony layer occurs, pop up message comes and asks, if I wan to restrart phone. And since this moment, phone is not connected to network, until I restart completely.
Can you recomend me some alternative ROMs, which restarts telephony layer automaticaly as stock rom does?
Thank you in advance!
But it will automatically restart after 30s as I know if you don't do anything.
Sent from my HTC One using Tapatalk
cyrusct82 said:
But it will automatically restart after 30s as I know if you don't do anything.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I am nearly sure, that the ROM has not restarted. Even after 30seconds.
PeLo02 said:
I am nearly sure, that the ROM has not restarted. Even after 30seconds.
Click to expand...
Click to collapse
it should, on some nightlies phone just stays turned off though. clean install from sbf might help to get rid of those restarts at all.
Wifi stuck on 'turning on'.. My Galaxy S4 won't let me enable Wi-Fi.
i had been using influes v4.0 rom and everything had been working great like a month until a week ago, when suddenly wifi stopped working
What now?
Using official XXUHOD4 framework.
android 5.0.1 lolipop
what Ive tried:
flashing another roms.
flashing paraman.bin- http://forum.xda-developers.com/showpost.php?p=52989594&postcount=4899
Delete wpa_supplicant.bak.conf via root explorer
Might be that the WiFi antenna got disconnected. Or it completely broke.
GDReaper said:
Might be that the WiFi antenna got disconnected. Or it completely broke.
Click to expand...
Click to collapse
bluetooth and hotspot are fully working
not using the same antenna?
darixtorento1 said:
bluetooth and hotspot are fully working
not using the same antenna?
Click to expand...
Click to collapse
I don't know. But when something worked fine before and then, for no reason, stops working, then it might be the result of a hardware problem.
GDReaper said:
I don't know. But when something worked fine before and then, for no reason, stops working, then it might be the result of a hardware problem.
Click to expand...
Click to collapse
sometimes I click on 'hotspot' and it turns off wifi
so I play with this..
turn on hotspot turn it off, then reboot the device and then wifi is working for like 10min and automatically tuns off and it stars again..
its barely working thats why I thought it might be system error.
darixtorento1 said:
bluetooth and hotspot are fully working
not using the same antenna?
Click to expand...
Click to collapse
darixtorento1 said:
sometimes I click on 'hotspot' and it turns off wifi
so I play with this..
turn on hotspot turn it off, then reboot the device and then wifi is working for like 10min and automatically tuns off and it stars again..
its barely working thats why I thought it might be system error.
Click to expand...
Click to collapse
System error should disappear when you flash another ROM.
Did you clean flash or dirty flash?
Also, if the problem persists I suggest flashing a stock ROM (clean flash) and see if it fixes Wi-Fi.
GDReaper said:
System error should disappear when you flash another ROM.
Did you clean flash or dirty flash?
Also, if the problem persists I suggest flashing a stock ROM (clean flash) and see if it fixes Wi-Fi.
Click to expand...
Click to collapse
when it happened in Influes rom, I tried flashing Ale95 Note5 Port Milestone v5.1
of course deleted cache preload and full wipe.
wifi still didnt work so i flashed official android 5.0.1 via odin- didnt help
flashed again and deleted again cache data everything didnt help
now received official update and installed it too- didnt help
Hi guys, I had to give up using CM Roms since the phone reboots every time I try making a call or receive one, I understand there is some king of bug with the dialer framework included in the GAPPS package and that installing the Google Dialer from the play store should solve it but in my case i hasn't. This is what I've tried to no avail:
- Intalled Google DIaler from PlayStore/APK and set it default with all the permissions enabled.
- Installed Google Dialer apk as system app and set it default with all the permissions enabled.
- Installed the full GAPPS package.
- Removed the stock dialer and did all things above.
Hope someone can help me out here,
Thanks.
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Sam Nakamura said:
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Hi Sam, that's what I mean when I've set it as default.
pitrus- said:
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Click to expand...
Click to collapse
Hey pitrus, this issue actually started while only having CM dialer installed since I mainly flash pico gapps.
Will try it again since its been like a month since I gave up on it. Let you know later.
J3RI3L said:
Hi Sam, that's what I mean when I've set it as default.
Click to expand...
Click to collapse
Well, okay.. Thanks for clarification :good:
Maybe you'd like to give Banks a shot, I think it's worth to try...
https://download.dirtyunicorns.com/gapps/Banks/
I never had this specific problem, only when it wasn't set to be default but a also only use one dailer.. The one that is default on cm based roms..
Sent from my OnePlus2 using XDA Labs
Guys I've had no luck, tried with a clean install of CM14 and still facing the same problem. Just today did a CM14.1 install and it is still present for me.
I guess that I could flash just CM and not gapps but I rely on Google services for a lot of stuff. Will keep trying though.
I'm having the exact same problem, random reboots during calls only, sometimes I don't even have time to answer. I'm running CM13 and only have one phone app, also set as default. When running stock and Cyanogen all was fine, this only started after flashing CM13.
Developemt for Cyanogen stopped that's why I switched, maybe coming from another rom is causing this? I did a full wipe when flashing and have updated to several nightlies and the problem remains. Maybe I'll try another rom and test it for a while.
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
It's a problem related to Gapps
rtorresz said:
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
Click to expand...
Click to collapse
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
pitrus- said:
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
Click to expand...
Click to collapse
I've installed them all with the same result, last time I was using Pico Gapps with Seraph's CM14 and it happened eandomly, sometimes I could make and receive calls normally but a most of the time it would reboot as soon as the phone started ringing.
Currently I've tried a lot of solutions so I'm not really sure of what's wrong.
J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
rtorresz said:
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
Click to expand...
Click to collapse
Its happening to me as well just as you describe it. It is very weird. In thinking of flashing the stock OOS 2.2.0 just to check whether it makes any diference.
Yesterday I restored my phone back to stock, but the problen remains.
This definitely has something to do with mobile data. If I disconnect mobile data I can make calls without any problem, when I'm connected to a wifi network too (I'm guessing because the phone has no need to use mobile data).
Some suggest that this might be related to VoLTE and operators not supporting it, but I can't find anyway to see if this is even exists or if its activated in OOS.
Later today I'll try Hydrogen and see what happens.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Kinda solved now
rtorresz said:
Yesterday I restored my phone back to stock, but the problen remains.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Click to expand...
Click to collapse
It seems I have solved my problem with the reboots and I think might help with your droped calls as well.
Firstly I flashed this OOS 3 firmware https://www.androidfilehost.com/?fid=24591020540821656, it comes with a hybrid TWRP, after that flashed the official CM14.1 and pico Open Gapps.
I think the firmware file did the trick or maybe it was the recovery since I haven't had a reboot in the past 2 days when receiving calls or making them.
Hope it helps
It's been a few days since I tried the last solution and so far my problem seems to be solved.
What worked for me was flashing the latest modem from H2OS 2.5 which also is supposed to enable VoLTE, but I can't confirm this since my carrier does not support VoLTE yet. To do this I first flashed CM 14.1 and then the modem, it worked fine since the first boot. Since my battery life wasn't the best in Nougat I went back to CM13 and the phone is still working fine.
Guys I am facing random reboot issue on every cm13 base Roms and even cm14 Roms..
Tried every possibility
1.Changed Roms
2. Cleared internal
OOS works pretty fine. Not even a single random reboot.
I have analysed when I switch off LTE connection phone works fine.
On LTE whenever I try to watch YouTube or any other high speed related stuff signal gets dropped, connects again and phone gives a reboot
Phone is almost unusable as it is giving me reboots multiple times in a day.
I am using Reliance Jio LTE(India)
Any suggestions please?
One guy reported the same issue on cm13 thread but havent got any resolution
I'm sorry bro.. Even I'm using reliance jio and i haven't suffered any such issue.. Try booting into your recovery and doing a fresh install, wipe dalvik and other caches.. Look if the random reboots is happening in a clean rom with no apps installed. You must have messed up with some system/root settings which may be the cause.. Also if u use titanium backup to restore apps after fresh installing a custom rom, try restore only the app and not the data. If then the reboots doesn't happen, it's more likely an app that's causing the reboots..
Also if you're installing additional zip files, verify that they aren't corrupt!
shravansp24 said:
I'm sorry bro.. Even I'm using reliance jio and i haven't suffered any such issue.. Try booting into your recovery and doing a fresh install, wipe dalvik and other caches.. Look if the random reboots is happening in a clean rom with no apps installed. You must have messed up with some system/root settings which may be the cause.. Also if u use titanium backup to restore apps after fresh installing a custom rom, try restore only the app and not the data. If then the reboots doesn't happen, it's more likely an app that's causing the reboots..
Also if you're installing additional zip files, verify that they aren't corrupt!
Click to expand...
Click to collapse
I have tried all the things.. except going full stock..
Tried to go full stock yesterday and now it seems issue is fixed..
Haven't got any random reboot.. will test it more..
ashu01 said:
I have tried all the things.. except going full stock..
Tried to go full stock yesterday and now it seems issue is fixed..
Haven't got any random reboot.. will test it more..
Click to expand...
Click to collapse
Glad you got your issue fixed in stock rom..!
shravansp24 said:
Glad you got your issue fixed in stock rom..!
Click to expand...
Click to collapse
Now even in cm13 I am not facing any issues..
ashu01 said:
Now even in cm13 I am not facing any issues..
Click to expand...
Click to collapse
That's great!