I have a S3 Mini I8190N, Baseband I8190NXXALL6, on Three Ireland.
I've tried all of Maclaw's CM10.2 roms for the last month, along with some of OliverG96's releases, and none of them show up any network signal for me, and won't let me search for networks, almost as if the rom can't use the hardware radio.
The stock 4.1.2 rom works perfect.
I've tried changing my baseband from I8190NXXALL6 to I8190NXXAMG1, and that made no difference.
(Stock still has perfect signal, Maclaws CM10.2 has no signal at all)
I've also looked through the build.prop files and compared them to the working stock build.prop, but I don't really think tweaks in there will fix this.
Seeing as this possibly could be a hardware issue, is there a file defining what radio hardware my phone has, like /proc/cpuinfo does for the cpu?
Anyone have suggestions on how i could fix (or help fix) this issue?
I can test suggestions and provide logcats if anyone requires?
EDIT:
Problem solved! seems there were some issues with my modemfs, and golden-guy's suggested fix here worked.
did you make a clean or dirty install?
if dirty try a clean install.
Same bug here and also Oliver96 has the same problem s.s
Sent from my GT-P3100 using xda app-developers app
JackoMJ said:
did you make a clean or dirty install?
if dirty try a clean install.
Click to expand...
Click to collapse
I've tried a dirty install, a clean (factory reset) install, and I've even went into ODIN, flashed a complete stock rom, TWRP, and then put CM10.2 on after that with a factory reset.
alexmarra3000 said:
Same bug here and also Oliver96 has the same problem s.s
Click to expand...
Click to collapse
Do you also have an I8190N? I'm trying to work out if its a hardware thing (like maybe we have a different hardware revision) or if its something we can actually fix. Is OliverG96 trying to solve this or is he just working on having a working rom for the majority?
same problem
i have got the same problem too.
got back to original samsung firmware und stock recovery... nothing
i am from germany und tried out any available basebands... nothing
on any stock, theres no problem, but if i want to get some roms e.g. from maclaw.pl i cant get signal at all
greez
EccTM said:
Do you also have an I8190N? I'm trying to work out if its a hardware thing (like maybe we have a different hardware revision) or if its something we can actually fix. Is OliverG96 trying to solve this or is he just working on having a working rom for the majority?
Click to expand...
Click to collapse
No, I have the I8190 normal version like OliverG96, and I don't know if he is working on a fix.
The strange thing is some users have the bug and some users not.
Also I have this bug with paranoid rom, pac rom and aokp.
On the contrary with Dmod v6 I don't have any issue, probably because it is based on official firmware, I don't know sincerly.
Sent from my GT-P3100 using xda app-developers app
i also think that the problem doesnt come up when u are using any rom which is based on stock firmware.
any custom rom which is using its own firmware doesnt get any signal
btw.: i am in the net of telco (o2)
Sent from my GT-I8190 using xda app-developers app
mausdefekt said:
i also think that the problem doesnt come up when u are using any rom which is based on stock firmware.
any custom rom which is using its own firmware doesnt get any signal
btw.: i am in the net of telco (o2)
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Hi, i also use O2 (directly) and had never problems with any CM-ROM of Maclaw.
You checked the APN??? Maybe you have to use a different one.
build.prop tweaks
Did some of you already try adding/tweaking some attributes in /system/build.prop?
There are quite some available to get better signal:
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
I did not try these myself, as I don't have any RIL issues, so use them at your own risk. Reboot afterwards for the changes to apply.
Source: http://geekyogi.tumblr.com/post/24692879082/android-build-prop-tweaks-root-only
Hi
There was similar problem with SGS1 long ago, it was caused by wrong IMEI. Check your IMEI with stock ROM and then with CM rom.
hey there, i looked up my imei with *#06# and got two different results.
the aokp custom rom shows me the same imei as the stock. but at stock, i get additionally "/ 01" at the end of the imei. the custom rom doesnt show this
Sent from my GT-I8190 using xda app-developers app
golden-guy said:
Did some of you already try adding/tweaking some attributes in /system/build.prop?
There are quite some available to get better signal:
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
Click to expand...
Click to collapse
I compared the maclaw 10.2 build.prop with my own functioning stock build.prop and changed most of the attributes about with no luck. I've also tried both those suggested options, but they seem to be more for improving signal strength rather than actually getting a signal, I didn't see any changes using them.
stenc55 said:
There was similar problem with SGS1 long ago, it was caused by wrong IMEI. Check your IMEI with stock ROM and then with CM rom.
Click to expand...
Click to collapse
Like mausdefekt, I get two slightly different results from *#06#.
My IMEI matches up, but when i'm running a non-stock based rom, my IMEI SV is 00 for some reason.
Guys, just back up your EFS partition and restore after you flash CM roms. You wouldn't have this kind of problems if you were using TWRP you know.
joelalmeidaptg said:
Guys, just back up your EFS partition and restore after you flash CM roms. You wouldn't have this kind of problems if you were using TWRP you know.
Click to expand...
Click to collapse
Ive tried that too, no difference. Also tried it with factorymode set both on and off.
I'm using Maclaw's TWRP 2.6.3.0 with kitkat support atm, I've never used any non-TWRP recovery.
mausdefekt said:
hey there, i looked up my imei with *#06# and got two different results.
the aokp custom rom shows me the same imei as the stock. but at stock, i get additionally "/ 01" at the end of the imei. the custom rom doesnt show this
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Hey,
I am running CM-10.2 on my S3 Mini (Oliver's cm-10.2-20131116-UNOFFICIAL-golden) and RIL is working just fine. So I would not think that there is a general issue with RIL on custom ROMs. Rather, the way how you switch from stock to custom might have an impact on RIL...
You could try going back to stock, verify RIL is working again as expected and then start flashing anew following my approach using heimdall: http://forum.xda-developers.com/showthread.php?t=2537520
Since when I switched from stock to custom, I exactly did that. And I never had any issue with RIL on any custom ROM I have installed since then - which was basically all versions since the 20130928 release.
Cannot tell if that works out for you, but it's definitely worth a try
Btw, I did not check the additional "/01" in the IMEI output when I was still on stock. Running custom I get the very same output - just the IMEI, without this suffix. In the "about phone" section, the relevant IMEI SV entry does read "01" for me.
I wonder if your cellphone is SIM-locked...
hi
i've a similar issue:
tried all maclow roms (4.1 and 4.2), in standby no network signal.
When I plug the phone to AC all works fine, in standby without AC no network signal.
I've tried setcpu to raise min. cpu to 1ghz, nothing.
What's wrong? On AC all works fine!
golden-guy said:
You could try going back to stock, verify RIL is working again as expected and then start flashing anew following my approach using heimdall: http://forum.xda-developers.com/showthread.php?t=2537520
Click to expand...
Click to collapse
I factory reset, flashed back to complete stock I8190NXXALL6 (it's 4.1.2) using ODIN, and everything worked perfect. From there I followed your guide to flash CWM recovery, then flashed maclaw's cm 10.2 (20131123) but I still had the same RIL issue.
Then I tried flash the stock rom with heimdall instead of ODIN initially and then follow your guide, same result.
Then I downloaded the odin version of maclaw's CM 10.2 (20131122) and flashed it directly with heimdall. same result.
After that, I took apart both the stock and odin cm 10.2 versions, and tried use heimdall to flash a hybrid version of the two:
Stock: STEboot1.img, STEboot2.img, Modem.bin
CM10.2: boot.img, system.img, recovery.img
Still had no signal at all, so I flashed TWRP 2.6.3.0 recovery and restored back to my usual stock-based backup.
joelalmeidaptg said:
I wonder if your cellphone is SIM-locked...
Click to expand...
Click to collapse
I checked (borrowed an o2.ie sim from a roommate) and it is network-locked to Three Ireland, but with my last phone (Samsung Galaxy Spica - I5700) it didn't affect using custom roms so I honestly didn't consider that... Do you think my problem could be that my device is network locked? Would that really cause this?
Timewolf said:
i've a similar issue:
tried all maclow roms (4.1 and 4.2), in standby no network signal.
When I plug the phone to AC all works fine, in standby without AC no network signal.
Click to expand...
Click to collapse
I just tried to see if i'd get any sort of signal on maclaw roms by plugging my phone into AC... no joy for me there either
Does it have signal if its plugged in then the phone is turned on, or can you get signal at any time just by plugging into AC? like:
*Turn on phone* > standby (on battery) - no signal > *plug into AC* > standby (on AC) - signal > *unplug AC* > standby (on battery) - no signal
Sounds like your problem could be more hardware based than mine? something to do with voltages possibly? I'm really not sure what to suggest.
EccTM said:
I checked (borrowed an o2.ie sim from a roommate) and it is network-locked to Three Ireland, but with my last phone (Samsung Galaxy Spica - I5700) it didn't affect using custom roms so I honestly didn't consider that... Do you think my problem could be that my device is network locked? Would that really cause this?
Click to expand...
Click to collapse
The thing is, that operators and brands, on earlier devices, put some limitations on the devices. For example, if you buy a Sony smartphone from 2011 and forward that is SIM-locked, you won't be able to flash any custom kernel at all. Can someone with the same problem confirm that their phones are SIM-locked?
joelalmeidaptg said:
The thing is, that operators and brands, on earlier devices, put some limitations on the devices. For example, if you buy a Sony smartphone from 2011 and forward that is SIM-locked, you won't be able to flash any custom kernel at all. Can someone with the same problem confirm that their phones are SIM-locked?
Click to expand...
Click to collapse
So assuming thats the issue, would getting a network unlock code allow me to use custom kernels and roms?
Related
Whenever I flash custom ROMs I have several problems. One of them is random rebooting. This isn't the problem with the stock ROM. Another problem I have is not receiving messages. If I flash back to a stock ROM I receive tons of messages that I didn't get while I had the custom ROM installed. I have tried re flashing the custom ROMs several times. The question is has anyone had this problem, and how can I fix this?
my question to you is what custome roms are you flashing that is a start and then i can help
i will check when i wake up there had better be a list
lol.....nice shadow...hope they don't have to work today, or you sleep for quite a while!
gordon154 said:
Whenever I flash custom ROMs I have several problems. One of them is random rebooting. This isn't the problem with the stock ROM. Another problem I have is not receiving messages. If I flash back to a stock ROM I receive tons of messages that I didn't get while I had the custom ROM installed. I have tried re flashing the custom ROMs several times. The question is has anyone had this problem, and how can I fix this?
Click to expand...
Click to collapse
Need to know what ROM's you are attempting to flash.
What version of phone do you have? Pull the battery and look at the white
label and tell me the build # of that phone. It's a 4 digit number (I.E. mine is 1008) If it is a 1008 - this is a known issue - and you'll need to test by going back to STOCK and seeing if the issue continues. If it does - you will need to warranty replace it.
The "tons of missing messages" means that the flash of the custom ROM didn't work right.
Best thing you can do to fix these issues - make sure you are installing the custom ROM correctly - make sure to follow the "chef/dev's" instructions before flashing the ROM.
Also.. if you go to the Q&A sticky it will point you to all sorts of different information - I would look at the "How to install a custom ROM" sticky in the dev section.
avgjoegeek said:
Need to know what ROM's you are attempting to flash.
What version of phone do you have? Pull the battery and look at the white
label and tell me the build # of that phone. It's a 4 digit number (I.E. mine is 1008) If it is a 1008 - this is a known issue - and you'll need to test by going back to STOCK and seeing if the issue continues. If it does - you will need to warranty replace it.
The "tons of missing messages" means that the flash of the custom ROM didn't work right.
Best thing you can do to fix these issues - make sure you are installing the custom ROM correctly - make sure to follow the "chef/dev's" instructions before flashing the ROM.
Also.. if you go to the Q&A sticky it will point you to all sorts of different information - I would look at the "How to install a custom ROM" sticky in the dev section.
Click to expand...
Click to collapse
My last IMEI numbers are 4486, and my build number is 1008.
I have been flashing Darky 7.01 up to 7.7 and perception. Before installing the ROMs I flash back to stock firmware and I do a master clear.
I have a hard time believing that the ROM is just flashing wrong because I have tried this around 10 different times. Each time I get a removed SIM error,
Which perception?
Sent from my SGH-I897 using XDA App
goob1284 said:
Which perception?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
10,9.9, and 9.5.
Try running Assonance and see if you get the same issue.
And.. Build 1008's (my build btw) is known to have random shutdown issues.
Mine is very specific - when I fully charge my phone to 100% it won't stay up until the battery drains back down to around 85% then no more shutdowns.
Will need to warranty your phone for replacement if it is still doing this while stock. I'd recommend flash back to stock - DO NOT ROOT - just run the phone for a day or so with a full charge and see if it is still shutting down. If it is.. then you will need to have it replaced.
And I randomly get "no sim card found" errors with i9000 roms after a reboot. I just turn airplane mode on/off and all is good afterwards.
I don't seem to have any problems with stock firmware
Sent from my SAMSUNG-SGH-I897 using XDA App
i search whole vivid forum about this problem
some guys (like me ) have problem with wifi on custom Roms
in some kernel wifi stuck on "wifi is turning on ..." and some kernel wifi could be on but it's crazy (like couldn't off) and couldn't find any wifi signal.
phone go to s-off but problem not solved
phone like Velocity 4G x710s
any body have a suggestion or help
when you flash any kernel, after that you have to push these file (bcmdhd.ko) which is in the kernel you download - to system/lib/module
and you will have wifi working with every kernel
mohamed_moscow said:
when you flash any kernel, after that you have to push these file (bcmdhd.ko) which is in the kernel you download - to system/lib/module
and you will have wifi working with every kernel
Click to expand...
Click to collapse
i found some "bcmdhd.ko" in some kernel
which is best for me
Cant wait for release!!
Can you upload that file for us?
Sent from my HTC Raider 4G LTE running ICS.
ideaLduK said:
Can you upload that file for us?
Sent from my HTC Raider 4G LTE running ICS.
Click to expand...
Click to collapse
yes, upload that for us
Every kernel has it's own specific modules.
Thats why if you're S-ON you have to flash a CWM Zip and fastboot the img.
If you're S-OFF both are done in CWM.
This thread should be moved.
ok i find working file
tested with kozmik RC1 kernel and work well
Nottach said:
Cant wait for release!!
Click to expand...
Click to collapse
Hehe awesome.
I experienced the issue you described as a separate error from the common issue solved by a manual adb push for the wireless module.
Even though my phone is S-Off, I'd receive the error consistently when installing certain ROMs (but not all ROMs).
After multiple wipes (including formatting all SD drives, data and system partitions), I finally fixed the issue on my phone by fastboot flashing the kernel for the specific ROM I'm installing after doing a re-format/wipe and before starting the ROM installer through CWM.
It's a strange error, especially because everything seemed to be installed properly (including proper kernel info in the system) and my phone is S-Off, but this is the method I've found that works.
If anyone experiences the issue, I'd recommend doing a back-up, full wipe and re-format (including internal and external SD, basically everything you can wipe); and then fastboot flash the boot.img pulled from your ROM zip before going into CWM and installing (always be careful when fastboot flashing; if you're new to it, you definitely need to familiarize yourself and read a tutorial or two; don't blame me if you're new to flashing, don't read tutorials and end up accidentally flashing a kernel to the wrong partition or some other problem).
Hope this helps out some of the people experiencing this issue.
I can relate
First let me say that kernels and ROMs are two different things.
Kernels are the base on which the ROM operates, they do include important information that can impact phone interoperability. They are required for a ROM to function. And they and ROMs do inter operate extensively.
ROMS are the added features and functionality that make our phones work as an actual appliance. They include software applications and compatibility feature that enable us to make and receive calls, and do all the other crazy things that we want in our phone, work.
I was experiencing similar issues recently. It turned out for me that if I didn't reflash the correct kernel after updating to a ROM that my MAC address would be missing. When that happened you will get the "turning on wireless" message that never completes, or your Wireless Networking switch in extended menu will be "ghosted" out.
Thanks to some great guys in TWRP, I got enough help to figure out what the right combination of "this and that" was. Now I am able to try and troubleshot mine effectively if I do it again.
Just my 3 cents guys, your mileage may vary!
daspazz said:
First let me say that kernels and ROMs are two different things.
Kernels are the base on which the ROM operates, they do include important information that can impact phone interoperability. They are required for a ROM to function. And they and ROMs do inter operate extensively.
ROMS are the added features and functionality that make our phones work as an actual appliance. They include software applications and compatibility feature that enable us to make and receive calls, and do all the other crazy things that we want in our phone, work.
I was experiencing similar issues recently. It turned out for me that if I didn't reflash the correct kernel after updating to a ROM that my MAC address would be missing. When that happened you will get the "turning on wireless" message that never completes, or your Wireless Networking switch in extended menu will be "ghosted" out.
Thanks to some great guys in TWRP, I got enough help to figure out what the right combination of "this and that" was. Now I am able to try and troubleshot mine effectively if I do it again.
Just my 3 cents guys, your mileage may vary!
Click to expand...
Click to collapse
How did you get it working
Sent from my ADR6410LVW using xda premium
Hello everyone,
Yesterday I decided to flash an updated ROM of 4.3 to my One. After flashing it (happens with new ROM, or after flashing a new custom kernel... logo2menu, you know), a message appears ALWAYS on-screen:
com.phone.android has stopped working​
This message repeats a hundred times. I can't type anything without the message popping up. I reached the launcher, but I have no Phone signal and the WiFi is not working. It's like the phone wants to wake up the Phone Antenna but it crashes to do it.
I've read that I had to flash the boot.img from the ROM I wish to flash, and I don't know if that causes the problem...
Any help would be perfect.
Thank you in advance.
=====================================================================================
SOLVED!
Well, after my vacation, took my One and did a bit of research. I know everything about this problem now.
The problem is only in GE ROMS. Why? 4.3 GE hasn't listed my MVNO yet (known error by Android and by 'Pepephone'). So, as soon the mobile goes on, Android tries to connect to the SIM, but as it's not listed amongst the companies, the phone crashes. I had to flash a file with the APN, then add it manually. Ta-Da! It works.
Attached the ZIP file to flash in Recovery.
- Install 4.3 GE Rom.
- Flash the Fix.
- Start and complete the Install Wizard.
- Inside the APN config, manually introduce Pepephone's APN
o NAME: Pepephone
o APN: gprsmov.pepephone.com
o MCC: 214
o MNC: 06
Sorry to bump the thread, but currently I have a HTC One with no phone and it's really important for me to solve this asap. I'm going on vacation tomorrow and I need my phone
raulongo said:
Sorry to bump the thread, but currently I have a HTC One with no phone and it's really important for me to solve this asap. I'm going on vacation tomorrow and I need my phone
Click to expand...
Click to collapse
Are you using a custom kernel that matches, exactly, the 4.3 custom rom you are using? If it is a GE 4.3 based rom, you need a GE 4.3 custom kernel (check out ElementalX). If it is a Sense 4.3 base rom, well that update just came out yesterday and there are no custom kernels for it yet.
dgtiii said:
Are you using a custom kernel that matches, exactly, the 4.3 custom rom you are using? If it is a GE 4.3 based rom, you need a GE 4.3 custom kernel (check out ElementalX). If it is a Sense 4.3 base rom, well that update just came out yesterday and there are no custom kernels for it yet.
Click to expand...
Click to collapse
It happens with EVERY 4.3 GE Rom, stock kernel. I was in 4.2.2 GE (Android Revolution) and Installed 4.3 and gave me that error all the time without upgrading the Kernel... I'm pretty lost.
raulongo said:
It happens with EVERY 4.3 GE Rom, stock kernel. I was in 4.2.2 GE (Android Revolution) and Installed 4.3 and gave me that error all the time without upgrading the Kernel... I'm pretty lost.
Click to expand...
Click to collapse
It sounds like there is an incompatibility with the new base. I would reflash the rom, doing a full wipe in the process
dgtiii said:
It sounds like there is an incompatibility with the new base. I would reflash the rom, doing a full wipe in the process
Click to expand...
Click to collapse
Full wipe means to wipe/factory reset in ClockWork Recovery before flashing? I already did that like dozen times, but still, same error I don't know why I'm the only one with this problem...
raulongo said:
Full wipe means to wipe/factory reset in ClockWork Recovery before flashing? I already did that like dozen times, but still, same error I don't know why I'm the only one with this problem...
Click to expand...
Click to collapse
The Roms I've used have an option for full wipe during the install in Aroma, but I guess doing it in CWM does the same thing. Are you theming the phone app by any chance? Something isn't playing nice with the 4.3 base, that's what you have to track down. Maybe go back to 4.2 while you sort it out
dgtiii said:
The Roms I've used have an option for full wipe during the install in Aroma, but I guess doing it in CWM does the same thing. Are you theming the phone app by any chance? Something isn't playing nice with the 4.3 base, that's what you have to track down. Maybe go back to 4.2 while you sort it out
Click to expand...
Click to collapse
Yup, did it inside the installer and outside it, but always same result. I'm back now into 4.2.2 Sense AR Rom and the phone works great, but I hate Sense.
Could it be the baseband firmware?
raulongo said:
Yup, did it inside the installer and outside it, but always same result. I'm back now into 4.2.2 Sense AR Rom and the phone works great, but I hate Sense.
Could it be the baseband firmware?
Click to expand...
Click to collapse
Firmware could be the case, was just thinking that.
My advice tho, you have a working phone, and with your vacation tomorrow, I would leave it as is for now
dgtiii said:
Firmware could be the case, was just thinking that.
My advice tho, you have a working phone, and with your vacation tomorrow, I would leave it as is for now
Click to expand...
Click to collapse
Thank you for your help. I will investigate a bit more as soon as I'm back.
raulongo said:
Thank you for your help. I will investigate a bit more as soon as I'm back.
Click to expand...
Click to collapse
Sounds good, you're welcome. Enjoy your vacation!
I have the exact same problem. I've literally tried everything. I have S-Off-ed my phone and installed a custom kernel but even that does not fix the problem. All custom 4.3 Google Edition Roms crash after I install them. It works fine if I use the Stock 4.3 ROM.
Kernel
Sent from my HTC One using XDA Premium HD app
dgtiii said:
Sounds good, you're welcome. Enjoy your vacation!
Click to expand...
Click to collapse
A little update. I've got Cyanogen 10.2 working perfectly in my phone. It's running 4.3, so now, I understand even less. Why CM works and the other ROMs doesn't?
The night is long... Hahah.
CM 10.2 works flawlessly "without" bugs. I don't understand why CM 10.2 (JB 4.3) works and the other 4.3 GE does not. Something is not right, or maybe I'm missing some step, but it's really strange...
raulongo said:
Hello everyone,
Yesterday I decided to flash an updated ROM of 4.3 to my One. After flashing it (happens with new ROM, or after flashing a new custom kernel... logo2menu, you know), a message appears ALWAYS on-screen:
com.phone.android has stopped working​
This message repeats a hundred times. I can't type anything without the message popping up. I reached the launcher, but I have no Phone signal and the WiFi is not working. It's like the phone wants to wake up the Phone Antenna but it crashes to do it.
I've read that I had to flash the boot.img from the ROM I wish to flash, and I don't know if that causes the problem...
Any help would be perfect.
Thank you in advance.
Click to expand...
Click to collapse
If you simply need a working phone, return to stock for your vacation, and then start from scratch re-flashing the GE firmware, kernels and rom. If anything is sense on the phone, incompatibility issues will happen.
kibmikey1 said:
If you simply need a working phone, return to stock for your vacation, and then start from scratch re-flashing the GE firmware, kernels and rom. If anything is sense on the phone, incompatibility issues will happen.
Click to expand...
Click to collapse
Finally found a solution to the crash. It was related to a weird combination between GE 4.3 and my mobile network operator, Pepephone. Known bug by Android and Pepephone.
Solution at the first post.
Hey there!
I have a strang problem with my Note, that being that I loose any signal utterly and completely after using the mobile data to some extend. Context: I live in finland right now and here they have unlimited mobile data, so I'm streaming netflix and stuff like that via my mobile connection.
After using roughly 600MB, my radio seems to completely shutdown. This can only be fixed by rebooting the device, I tried many different apps that have to do something with the device's radio, but to no use.
I'm using the latest radio modem software from this thread http://forum.xda-developers.com/showthread.php?t=1645202 (for jelly bean) and I also tried downgrading my radio (tried 4 older versions), but that only seemed to make the connection slower, but ultimately not fixing my problem.
I'm using the latest stable cyanogen mod (cm-10.1.3-n7000.zip from https://download.cyanogenmod.org/?device=n7000).
A friend of mine also has the same mobile data thingy, and he streamed and downloaded roughly 100GB in the last 6 weeks without any outages, so it's definitely my device, not the mobile carrier.
Has anyone any ideas on how to fix this?
If I forgot any important details or did something wrong, please let me know, this is my first time posting here!
Deathsservant said:
Hey there!
I have a strang problem with my Note, that being that I loose any signal utterly and completely after using the mobile data to some extend. Context: I live in finland right now and here they have unlimited mobile data, so I'm streaming netflix and stuff like that via my mobile connection.
After using roughly 600MB, my radio seems to completely shutdown. This can only be fixed by rebooting the device, I tried many different apps that have to do something with the device's radio, but to no use.
I'm using the latest radio modem software from this thread http://forum.xda-developers.com/showthread.php?t=1645202 (for jelly bean) and I also tried downgrading my radio (tried 4 older versions), but that only seemed to make the connection slower, but ultimately not fixing my problem.
I'm using the latest stable cyanogen mod (cm-10.1.3-n7000.zip from https://download.cyanogenmod.org/?device=n7000).
A friend of mine also has the same mobile data thingy, and he streamed and downloaded roughly 100GB in the last 6 weeks without any outages, so it's definitely my device, not the mobile carrier.
Has anyone any ideas on how to fix this?
If I forgot any important details or did something wrong, please let me know, this is my first time posting here!
Click to expand...
Click to collapse
Well, try a more recent copy of cyanogenmod. 10.1.3 is over a year old.
You might also want to try a different baseband
Azeazezar said:
Well, try a more recent copy of cyanogenmod. 10.1.3 is over a year old.
You might also want to try a different baseband
Click to expand...
Click to collapse
Okay thanks, I will try using the latest nightly build. What's a baseband in this case? Google can't help, so I must be googling wrong. I tried many different radio versions, but that's not what you mean I guess?
edit: Ah, yeah we mean the same things. I already said I tried using older radios, but no use. Every link i find for the newer XXLT5 is down, so I can't try that one.
LT4 is recent enough. Its what i use. If you really need LT5 or bolt, make a backup of your rom, flash a stock rom that includes it with odin and restore the backup.
Azeazezar said:
LT4 is recent enough. Its what i use. If you really need LT5 or bolt, make a backup of your rom, flash a stock rom that includes it with odin and restore the backup.
Click to expand...
Click to collapse
I just now found an LT4 zip file, so I'll try that. Now that I upgraded to the newest nightly build (there's a new version everyday ) I only loose the connection for some seconds. Maybe LT4 will fix that.
edit: Okay false alarm, I only find complete ROMs with LT4 integrated. Isn't there a standalone .zip file? I can't flash new ROMs every 12 hours, I already lost all my photos because the SD card was formatted by accident
edit2: okay, when I loose connection, it is automatically reestablished in the next 10 seconds, so for streaming or downloading (most) stuff, that works okay. Still, is there a way to get rid of this? My friend is downloading with 3 MB/s all the time via mobile data, and I'm sitting here stuck with 500 kbit/s and connection losses every ~45 minutes
push
I have an unlocked bootloader and rooted Nexus 6. I usually run custom ROMs but I have had some issues when I install them for about the past week or so. I use Straight Talk CDMA which uses the Verizon towers. If I flash an official firmware such as LMY47I (5.1) or LMY47Z (5.1.1) then I have no issues with LTE connecting from the very beginning of the setup screen. Everything works fine including voice, data, and texting. When I install a custom ROM the signal will not connect and there is an exclamation point (!) next to the signal icon. I did have to exchange my phone and Motorola sent me a new one but I was able to use custom ROMs without issues on this phone until sometime earlier this week.
I know that people have been having some issues recently with connection problems and there are various threads on them. I have tried several of these workarounds but it just seems odd that I never had these issues before.
Any help or suggestions would be great. Don't mind running stock firmware but would prefer to be able to use custom ROMs again.
Thanks in advance.
emmittobie said:
I have an unlocked bootloader and rooted Nexus 6. I usually run custom ROMs but I have had some issues when I install them for about the past week or so. I use Straight Talk CDMA which uses the Verizon towers. If I flash an official firmware such as LMY47I (5.1) or LMY47Z (5.1.1) then I have no issues with LTE connecting from the very beginning of the setup screen. Everything works fine including voice, data, and texting. When I install a custom ROM the signal will not connect and there is an exclamation point (!) next to the signal icon. I did have to exchange my phone and Motorola sent me a new one but I was able to use custom ROMs without issues on this phone until sometime earlier this week.
I know that people have been having some issues recently with connection problems and there are various threads on them. I have tried several of these workarounds but it just seems odd that I never had these issues before.
Any help or suggestions would be great. Don't mind running stock firmware but would prefer to be able to use custom ROMs again.
Thanks in advance.
Click to expand...
Click to collapse
Try a different radio. I've read that the radio from the M test build is fixing some issues.
I've tried flashing a few of the newest radios but not the Android M version. Will give it a try.
Thanks for the reply.
Sent from my Nexus 6 using XDA Free mobile app
emmittobie said:
I've tried flashing a few of the newest radios but not the Android M version. Will give it a try.
Thanks for the reply.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
You can even flash an older radio if need be.
So I tried installing two different custom ROMs and both times I got the same signal icon with an (!) next to it. There is no working connection. I tried flashing the radio from the Android M preview and also installed the radio from LMY47D (Verizon 5.1.0) since I am on Straight Talk CDMA. Neither one seemed to help. After flashing these radios I went back to restoring a TWRP backup based on just a stock firmware. From what I understand the radio is separate from any particular ROM you flash and thus independent of each other. I am able to get an LTE signal when I revert back to the backup.
So now I'm stumped. It doesn't seem to be based on the radio. None of the custom ROMs that I was able to use less than a week ago are able to find an LTE signal after a clean install. I can only seem to use official firmware versions.
Any other possible ideas? Could the phone be defective? It was an RMA replacement and I think it was new and not refurbished.
Thanks in advance.
emmittobie said:
So I tried installing two different custom ROMs and both times I got the same signal icon with an (!) next to it. There is no working connection. I tried flashing the radio from the Android M preview and also installed the radio from LMY47D (Verizon 5.1.0) since I am on Straight Talk CDMA. Neither one seemed to help. After flashing these radios I went back to restoring a TWRP backup based on just a stock firmware. From what I understand the radio is separate from any particular ROM you flash and thus independent of each other. I am able to get an LTE signal when I revert back to the backup.
So now I'm stumped. It doesn't seem to be based on the radio. None of the custom ROMs that I was able to use less than a week ago are able to find an LTE signal after a clean install. I can only seem to use official firmware versions.
Any other possible ideas? Could the phone be defective? It was an RMA replacement and I think it was new and not refurbished.
Thanks in advance.
Click to expand...
Click to collapse
Really sounds like an APN issue. I have flashed a few ROMs and have had that problem. Most recently Exodus ROM. I changed the APN and all is well.
Evolution_Tech said:
Really sounds like an APN issue. I have flashed a few ROMs and have had that problem. Most recently Exodus ROM. I changed the APN and all is well.
Click to expand...
Click to collapse
Let me take a look at the APN settings on the stock firmware and then see how they compare when I use a custom ROM. In the past, I never had to set the APN settings as I thought they were set automatically on CDMA sim cards. I'll take a look.
Thanks.
emmittobie said:
Let me take a look at the APN settings on the stock firmware and then see how they compare when I use a custom ROM. In the past, I never had to set the APN settings as I thought they were set automatically on CDMA sim cards. I'll take a look.
Thanks.
Click to expand...
Click to collapse
Even if there's another APN with the same name as the one set by default, try switching to the other. That's what worked for me on Exodus.
Evolution_Tech said:
Even if there's another APN with the same name as the one set by default, try switching to the other. That's what worked for me on Exodus.
Click to expand...
Click to collapse
Thanks for the advice. I was able to compare the APN settings on a stock firmware and enter these settings into the APN settings of a custom ROM and able to get it to work. Just strange that I have to enter these settings manually when I never had to do it before. Thanks for all your help. Much appreciation.
emmittobie said:
Thanks for the advice. I was able to compare the APN settings on a stock firmware and enter these settings into the APN settings of a custom ROM and able to get it to work. Just strange that I have to enter these settings manually when I never had to do it before. Thanks for all your help. Much appreciation.
Click to expand...
Click to collapse
No problem, glad you got it straight. :good: