I have tried for days to get ICS working on my phone. I am using the Chinese radio and everything is working fine on GB.
When I update to ICS it says baseband unknown
Updating the Build prop from default 4 to 3 does nothing.
On Gummy it just stalls and won't boot up.
Using the zips for GSM fix and RWAILY's Modified build in safestrap aborts the Installation. Updating the xt883 radio aborts installation
Why is my phone being such a douchebag.
Try using rick#2's xt860 patch
Sent from my XT860 running ICS using xda premium
http://forum.xda-developers.com/showthread.php?t=1560519 here you can find the build prop for ICS just replace it with root explorer and you should be good.
Sent from my XT862 using XDA
Thanks but they still don't work.
The GSM fix will not flash in safestrap. When I take the build prop and replace it manually, the splash screen hangs
Anytime the build prop is tweaked, I run into problems in ICS. GB is fine though.
phonephoenix said:
Thanks but they still don't work.
The GSM fix will not flash in safestrap. When I take the build prop and replace it manually, the splash screen hangs
Anytime the build prop is tweaked, I run into problems in ICS. GB is fine though.
Click to expand...
Click to collapse
hi
try to make a comparison between a stock GB build.prop vs the modified one for chinesse.
with that info update manually the build prop in ics.
because if you simply put the GB buildprop on ICS ICS will die
if that works can you post which changes you noted
I'm experiencing the same thing. But in my case I also get baseband unknown is GB (verizon gb without radio). Still looking for solution
Sent from my SGH-T839 using XDA
This should work for AOKP at least. It did for me.
nikeusfr said:
For gsm user, this is solution and all works well :
install safestrap
format data, cache and system
install aokp and gapps
reboot without sim card in the phone
edit build.prop with rootexplorer or other :
# Default network type.
# 7 => Global Phone (4 => CDMA).
ro.telephony.default_network=3 (instead of 7 or 4)
# BEGIN Moto,IKDROIDPRO-430, a17673
# Feature33857 on DroidWE, support DualMode switch, UMTS/CDMA
ro.mot.FTR.33857=false (instead of true)
# END IKDROIDPRO-430
# BEGIN Moto, IKSTABLETWO-1284, nfjb73
# without this property, the lock screen would take global phone as UMTS
# block user to operate before setup
keyguard.no_require_sim =false (instead of true)
# End Moto
save build.prop after this change
new step, enter *#*#4636#*#* into the dialer. Then goto "Phone Information". Near the bottom of that screen there's a drop down of network preference. For GSM-ONLY use GSM (PRL). Exit that screen and reboot the phone.
shut off phone, insert your sim card and boot the phone.....
thanks to hashcode and all over.
Click to expand...
Click to collapse
I've done everything. I still get the same results.
When i enter *#*#4636#*#*
I go into phone information
I try to change it from unknown to GSM and it won't do it.
Phone is a big D Bag.
EDIT: Thank you for trying though.
Can you recommend any GB roms? I had Mav and it was pretty good
I use this exact build.prop with my droid 3 on tmobile and ics
http://forum.xda-developers.com/showpost.php?p=23884104&postcount=1368
Hope it helps
SithDagger said:
I use this exact build.prop with my droid 3 on tmobile and ics
http://forum.xda-developers.com/showpost.php?p=23884104&postcount=1368
Hope it helps
Click to expand...
Click to collapse
But can you tell me if you have data connection with T-Mobile?
I am using Mavrom 3.5 and my provider is AT&T. 3G DATA is working so nice and i like this rom but i am thinking to move to ICS.
But if DATA connection is not working with GSM providers, i will stick with Maverick rom.
koukobin said:
But can you tell me if you have data connection with T-Mobile?
I am using Mavrom 3.5 and my provider is AT&T. 3G DATA is working so nice and i like this rom but i am thinking to move to ICS.
But if DATA connection is not working with GSM providers, i will stick with Maverick rom.
Click to expand...
Click to collapse
Yes, fully working 2g data connection with tmobile, wouldnt have ics on my phone without it. 3g would only work with at&t though, since the droid3's hardware doesnt support tmobiles 3g band.
Also, dunno if this helps, but i dont use *#*#4636#*#* to setup, i go into the mobile network settings, and scan for a network operator, connects just fine.
SithDagger said:
Yes, fully working 2g data connection with tmobile, wouldnt have ics on my phone without it. 3g would only work with at&t though, since the droid3's hardware doesnt support tmobiles 3g band.
Also, dunno if this helps, but i dont use *#*#4636#*#* to setup, i go into the mobile network settings, and scan for a network operator, connects just fine.
Click to expand...
Click to collapse
Thanks sounds very nice. Can you also please tell me if you are using CM9 ICS or AOKP ICS?
koukobin said:
Thanks sounds very nice. Can you also please tell me if you are using CM9 ICS or AOKP ICS?
Click to expand...
Click to collapse
CM9, havent tried AOKP yet, need to try it sometime.
SithDagger said:
I use this exact build.prop with my droid 3 on tmobile and ics
http://forum.xda-developers.com/showpost.php?p=23884104&postcount=1368
Hope it helps
Click to expand...
Click to collapse
Hash should add that **** onto his post. I'm seeing a ton of requests for this very thing.
I think your problem is not with the build.prop. Its with the radio that you have before flashing. In my case i have the stock verizon rom with the chinese radio and when i flash to ICS i have the same problem. No signal, unkown imei, etc.
You have to flash the original verizon radio(XT862) and then flash to ICS.
Look at this post:
http://forum.xda-developers.com/showthread.php?t=1544125
Tell me if you fix your problem
chemicalboyxda said:
I think your problem is not with the build.prop. Its with the radio that you have before flashing. In my case i have the stock verizon rom with the chinese radio and when i flash to ICS i have the same problem. No signal, unkown imei, etc.
You have to flash the original verizon radio(XT862) and then flash to ICS.
Look at this post:
http://forum.xda-developers.com/showthread.php?t=1544125
Tell me if you fix your problem
Click to expand...
Click to collapse
But cm9 doesn't touch the radio... I flashed cm9 from stock when I had the chinese radio installed on stock, so I dunno, no problems here.
Of course after I flashed I went to settings, wireless and networks, more, mobile networks, and then network operators, then I selected tmobile, problem solved. This was after modifying the build.prop, and flashing cm9.
I see no reason to flash the stock radio when the chinese is needed for tmobile/at&t, and cm9 doesn't touch it.
sent from Sheogorath with cheese!
SithDagger said:
But cm9 doesn't touch the radio... I flashed cm9 from stock when I had the chinese radio installed on stock, so I dunno, no problems here.
Of course after I flashed I went to settings, wireless and networks, more, mobile networks, and then network operators, then I selected tmobile, problem solved. This was after modifying the build.prop, and flashing cm9.
I see no reason to flash the stock radio when the chinese is needed for tmobile/at&t, and cm9 doesn't touch it.
sent from Sheogorath with cheese!
Click to expand...
Click to collapse
In my case if i flash to CM9 from stock+chinese radio i have the problems that i mention(unkown imei, baseband, no signal, etc). If i flash to CM9 from stock+stock radio that problems dissapear.
I bought a used Droid 3 XT862 which was running 5.7.905 firmware and i went back to 5.6.890 (Kernel and bootloader remained intact as expected). Then i rooted the phone and flashed the chinese radio. I installed CM9 and then i used the buid.prop from this link:
http://forum.xda-developers.com/showpost.php?p=23884104&postcount=1368
I couldn't flash this zip file through safestrap (at least no go for my occasion) so pushed it to /system by using root explorer.
I rebooted the phone and i had 3G data connection working just fine. My provider is AT&T.
Related
I'm having an issue that hasn't happened before. My data used to be working fine on Serendipity but now, even after flashing to the new 5.3, my 3G network isn't working at all for data. I can't browse the web, get e-mail, etc.
When I flashed back to stock rom, the data worked fine, as soon as I flashed to 5.3 the data was inoperable again - and this was a fresh install meaning I did a MASTER CLEAR and did NOT restore my backup from Titanium yet.
I figured that it might just be the ROM so I flashed back to stock, checked that data worked (it did) and flashed Phoenix 4.5. Same problem. Fresh install, data isn't working.
I checked the APN and all the APN settings are the exact same from stock (I wrote them down). I tried disabling 3G and using GSM (Edge) and data worked fine, but when I placed it in automatic again, data stopped working.
I tried switching bands from 850 and 1900. I don't have 850 here but that never been an issue as I have always used 1900. I tried installing the JL3 modem, still data isn't working.
Now, I'm totally lost. Please, does anyone have ANY suggestions?
Did you check your bill to see if you still have the plan?
carboncopy01 said:
Did you check your bill to see if you still have the plan?
Click to expand...
Click to collapse
Yes, of course I still have the plan. If data worked fine in stock ROM why wouldn't I have the plan?
This is the wrong place for this post, mods please move!!!
Most likely you need to check your APN settings.
bbtheory said:
This is the wrong place for this post, mods please move!!!
Most likely you need to check your APN settings.
Click to expand...
Click to collapse
I double checked my APN settings and they are correct, they're the exact same from stock.
charmartist said:
I double checked my APN settings and they are correct, they're the exact same from stock.
Click to expand...
Click to collapse
Get a new sim card. Its free
Sent from recent
ninjuh said:
Get a new sim card. Its free
Sent from recent
Click to expand...
Click to collapse
I don't think that's the problem though. If data worked fine in stock but not in a custom ROM then it can't be the SIM card.
hmm
Try a few modems as well
did you try other roms?
ronii1123 said:
Try a few modems as well
Click to expand...
Click to collapse
I tried the JL3, which other modems are compatible with Phoenix 4.5?
shawn122 said:
did you try other roms?
Click to expand...
Click to collapse
I only tried Serendipity 5.3 and Phoenix 4.5. I'm thinking of trying Perception or Cognition next to see if the problem still persists.
I had/have a similar issue and think it is a modem issue. Using Perception I had no 3g issues. But when I tried Darky's rom it would stay um EDGE. If I forced WCDMA only it would work (or have no service). I can't be certain but the best modem for you depends on region.
Sent from my GT-I9000 using XDA App
charmartist said:
I tried the JL3, which other modems are compatible with Phoenix 4.5?
I only tried Serendipity 5.3 and Phoenix 4.5. I'm thinking of trying Perception or Cognition next to see if the problem still persists.
Click to expand...
Click to collapse
This sounds like an APN/modem issue. Why dont you ask in the Serendipity thread? Im sure people which are using it and Mike will be able to help you
I solved my problem when I installed Cognition 3.04. I'm not sure but isn't Cognition based on a Captivate Rom and uses a Captivate modem?
It might not have been ROM specific but kernel specific. You can load custom ones or use the one each rom is built with. Though I might be way off here.
Sent from my SAMSUNG-SGH-I897 using XDA App
charmartist said:
I solved my problem when I installed Cognition 3.04. I'm not sure but isn't Cognition based on a Captivate Rom and uses a Captivate modem?
Click to expand...
Click to collapse
Try some other i9000 roms like Andromeda, Continuum and di11is5.3 roms.
Here is a list of i9000 and i897 modems http://forum.xda-developers.com/showthread.php?t=876391
(EDIT = they are all i9000 modems actually with one i9088 modem from Chinese Captivate)
The most puzzling thing is that I never had a problem like this before. It just kind of happened, as if AT&T changed something over at the region where I live. Because if it worked with the stock rom and after a master clear still doesn't work with the customs roms... it just seems a bit odd; especially since it worked before.
Did you ever check to see what it says in Settings => About Phone => Status for Mobile Network Type?
well here is my problem i am only getting a edge data connection where i should b getting 3g at least 4 sure. anyone have a fix
We're going to need a little more info my friend. What ROM did you flash from? What kernel were you running? Have you tried going into the "secret code" part of SGS tools and using the 3G/HSUPA option? Have you tried flashing a different radio? Maybe you're using one that isn't compatible with your kernel or the ROM?
i flashed from stock used odin3 thin 1 click root got rom manager installed cw flashed to cog 4.1.1 now i know i have a 3g signal where i am but i am only using edge
i went to the secret code thing and clicked switch 3g/huspa but idk how to do it
if u could explain
i would like the fastest modem i can get i have a unlimited data and battery life don't bother me
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
dinosaur swagg said:
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
Click to expand...
Click to collapse
It may have been flashed to the 883 radio. I would do a complete SBF.
dinosaur swagg said:
All information, such as the Baseband version, IMEI, MEID is "unknown". I've researched heaps and stumbled across a few other posts where people have similar problems although I haven't really seen a definite answer to the problem. I'm running stock ROM, rooted, safestrap 3.05. I've tried a few things, hard rest, flashed CM 10.1, flashed new radio. Although I'm an XDA-noob I'm guessing it's a radio problem? Can someone please help me out here.
Click to expand...
Click to collapse
Your build.prop has to match the radio. If you've flashed the XT883 radio, you must use a modified build.prop.
Here is a post I made for someone with a similar issue. It has necessary files and instructions on flashing the stock and XT883 radio. Flash the stock XT862 radio and see if that helps.
I have sbf'ed the phone, but it hasn't fixed the problem. I have installed the 833 radio previously and made sure I have pushed the build.prop into the system folder still without luck of fixing the problem. After a little more research, could the EFS folder be corrupt/deleted causing the problem?
Skreelink said:
Your build.prop has to match the radio. If you've flashed the XT883 radio, you must use a modified build.prop.
Here is a post I made for someone with a similar issue. It has necessary files and instructions on flashing the stock and XT883 radio. Flash the stock XT862 radio and see if that helps.
Click to expand...
Click to collapse
I do remember using your method although I didn't transfer the build.prop in that case. Does the build.prop in the flash kit match the XT862-890.img radio?
dinosaur swagg said:
I do remember using your method although I didn't transfer the build.prop in that case. Does the build.prop in the flash kit match the XT862-890.img radio?
Click to expand...
Click to collapse
Just use the stock build.prop with the xt862 890 radio. It is the stock radio, works on systems 890 and 906, tested personally. It will work with verizon and non-us gsm. If you require us-gsm such as att, lemme know and I can upload my current build.prop for gb roms.
htsebar meafure
Skreelink said:
Just use the stock build.prop with the xt862 890 radio. It is the stock radio, works on systems 890 and 906, tested personally. It will work with verizon and non-us gsm. If you require us-gsm such as att, lemme know and I can upload my current build.prop for gb roms.
Click to expand...
Click to collapse
I am currently outside of the US and would require a GSM radio. Does this mean that I would flash the XT862-890.img radio in your flash tools? Along with that I would need the stock build.prop I take? Yet I believe I overwrite this when I flashed the 886 radio and pushed the modified build.prop into the system folder. Where can I get the stock build.prop? Thanks very much for the help too
dinosaur swagg said:
I am currently outside of the US and would require a GSM radio. Does this mean that I would flash the XT862-890.img radio in your flash tools? Along with that I would need the stock build.prop I take? Yet I believe I overwrite this when I flashed the 886 radio and pushed the modified build.prop into the system folder. Where can I get the stock build.prop? Thanks very much for the help too
Click to expand...
Click to collapse
Both radios support gsm. The ONLY reason users flash the xt883 radio is because of the mnc block on 310 built into the xt862 radio. This does not affect foreign non-us gsm networks. If you flash any roms, do not modify the build.prop and it should work with the xt862-890 radio. It seems users always rush into either suggesting flash the xt883 radio or lib files, which either one just confuses more than helps an average user... it is better to troubleshoot first..
Anyway, my suggestion (since you seem to have a grasp on flashing radios) is use the kit I gave you, flash the xt862-890.img radio, then flash any rom, such as maverick (I use version 4.0 of this), minimoto, etc. Gb roms will be your most stable and have everything working, such as camera. Do not modify the build.prop, check under wireless settings to change network type to gsm/umts and apns.
The ONLY modification to the build.prop will be after you get it working, changing one line to fix the signal bars display. (Verizon has these nerfed to make gsm look bad) although not a true indication of signal, always check status.
Skreelink said:
Both radios support gsm. The ONLY reason users flash the xt883 radio is because of the mnc block on 310 built into the xt862 radio. This does not affect foreign non-us gsm networks. If you flash any roms, do not modify the build.prop and it should work with the xt862-890 radio. It seems users always rush into either suggesting flash the xt883 radio or lib files, which either one just confuses more than helps an average user... it is better to troubleshoot first..
Anyway, my suggestion (since you seem to have a grasp on flashing radios) is use the kit I gave you, flash the xt862-890.img radio, then flash any rom, such as maverick (I use version 4.0 of this), minimoto, etc. Gb roms will be your most stable and have everything working, such as camera. Do not modify the build.prop, check under wireless settings to change network type to gsm/umts and apns.
The ONLY modification to the build.prop will be after you get it working, changing one line to fix the signal bars display. (Verizon has these nerfed to make gsm look bad) although not a true indication of signal, always check status.
Click to expand...
Click to collapse
Okay so I have just re-flashed the XT862-890 radio then flashed CM10 (a ROM I had sitting on my SD) but I did so without rebooting after the radio flash as I wasn't sure if it were necessary. This still hasn't solved the problem. You did mention not to edit the build.prop wich I wish I had known earlier. I'm not sure whether the build.prop I had in the system file was modified or not so I did a quick google search and found what seemed to be the stock build.prop text (http://www.droidforums.net/forum/droid-3-hacks/159002-build-prop-those-wanting-look.html). I then copied the text to notepad and saved as build.prop prior to pushing to the system folder. Could this have been a bad mistake?
dinosaur swagg said:
Okay so I have just re-flashed the XT862-890 radio then flashed CM10 (a ROM I had sitting on my SD) but I did so without rebooting after the radio flash as I wasn't sure if it were necessary. This still hasn't solved the problem. You did mention not to edit the build.prop wich I wish I had known earlier. I'm not sure whether the build.prop I had in the system file was modified or not so I did a quick google search and found what seemed to be the stock build.prop text (http://www.droidforums.net/forum/droid-3-hacks/159002-build-prop-those-wanting-look.html). I then copied the text to notepad and saved as build.prop prior to pushing to the system folder. Could this have been a bad mistake?
Click to expand...
Click to collapse
Uh, yeah... that build.prop will not work on cm10, also all kexec roms (cm10/aokp/cm10.1) have issues with gsm anyway. Just try to sbf back to stock. If you still get unknown for baseband, etc. Then you may have a hardware problem. After flashing the radio and rebooting, it should show an android with an open box with a meter, then reboot itself. If your build.prop is correct for the radio, your baseband, prl, etc will show. You *may* have to toggle global/gsm/cdma a few times to get signal. Flash a stock based rom (maverick or minimoto) and see if that shows baseband.
Skreelink said:
Uh, yeah... that build.prop will not work on cm10, also all kexec roms (cm10/aokp/cm10.1) have issues with gsm anyway. Just try to sbf back to stock. If you still get unknown for baseband, etc. Then you may have a hardware problem. After flashing the radio and rebooting, it should show an android with an open box with a meter, then reboot itself. If your build.prop is correct for the radio, your baseband, prl, etc will show. You *may* have to toggle global/gsm/cdma a few times to get signal. Flash a stock based rom (maverick or minimoto) and see if that shows baseband.
Click to expand...
Click to collapse
I'm really hoping that this is not a hardware problem and that there is a solution. I'm going to SBF back to stock using this method (http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/) as the method via RSDlite never seems to work for me (failed at flashing process). I believe the last attempt failed to flash the radio as that screen with the android never did show up. I will SBF, reflash radio, and if that doesn't work I will flash minimoto. Do you think that the method I used copying the build.prop off the post will work or even is the correct build.prop? Thanks very much for the help by the way, much appreciated.
dinosaur swagg said:
I'm really hoping that this is not a hardware problem and that there is a solution. I'm going to SBF back to stock using this method (http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/) as the method via RSDlite never seems to work for me (failed at flashing process). I believe the last attempt failed to flash the radio as that screen with the android never did show up. I will SBF, reflash radio, and if that doesn't work I will flash minimoto. Do you think that the method I used copying the build.prop off the post will work or even is the correct build.prop? Thanks very much for the help by the way, much appreciated.
Click to expand...
Click to collapse
The build.prop was wrong for the system. If using the stock radio, do not touch the build.prop on any rom you flash. Roms generally have verizon cdma in mind, but foreign gsm works as well. The build.prop should only be swapped to use at&t/tmobile in the US.
Skreelink said:
The build.prop was wrong for the system. If using the stock radio, do not touch the build.prop on any rom you flash. Roms generally have verizon cdma in mind, but foreign gsm works as well. The build.prop should only be swapped to use at&t/tmobile in the US.
Click to expand...
Click to collapse
Okay so I have the 883 modified build.prop. Do you happen to have or know where/how I can get the stock build.prop?
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?
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: