Hi fellas
I might found something interesting, there is an app in google play called GetRIL by sibbor. According to this app my RIL and BASEBAND wasn't matching (unknown), you can choose another RIL or make it match, so now I'm testing to see any changes. Give it a shot, it may solve lot off problems ;D
On the first start this app showed that my RIL is unknown, then it matched RIL with BASEBAND but lost pin and signal problem still persisted, then I disabled this line in build.prop (ro.telephony.ril_class=X3RIL) and for now it works like a charm
This is my current result (it doesn't match because BASEBAND has another display name but its same as RIL for 100%):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
P. S. I'm on official CM11
I personally wasn't aware taht these RIL problems still exist for some users. For me they were fixed by installing the latest firmware update which came out only to solve these problems, that many german users had caused by changes in the O2/Eplus network, if I remember that correctly.
Tried the app too when I had these poblems, but I couldn't solve them, but I haven't used the same steps you used. Anyway, good if this can solve remaining problems
Androidmarketuser said:
I personally wasn't aware taht these RIL problems still exist for some users. For me they were fixed by installing the latest firmware update which came out only to solve these problems, that many german users had caused by changes in the O2/Eplus network, if I remember that correctly.
Tried the app too when I had these poblems, but I couldn't solve them, but I haven't used the same steps you used. Anyway, good if this can solve remaining problems
Click to expand...
Click to collapse
What do you mean by "For me they were fixed by installing the latest firmware update which came out only to solve these problems"?
Didn't get much attendance (no own forum thread) because it didn't affect the majority, but the complaints in KK and other threads were numerous. if you google for v20c-eur you'll find mostly german forums, but here there are some mentions about it (look at the bottom):
http://forum.xda-developers.com/showthread.php?t=2496075&page=14
The update should brings some fixes, some performance and best thing it has fixed most users problems!
Edit: @Siauka
Androidmarketuser said:
Didn't get much attendance (no own forum thread) because it didn't affect the majority, but the complaints in KK and other threads were numerous. if you google for v20c-eur you'll find mostly german forums, but here there are some mentions about it (look at the bottom):
http://forum.xda-developers.com/showthread.php?t=2496075&page=14
The update should brings some fixes, some performance and best thing it has fixed most users problems!
Edit: @Siauka
Click to expand...
Click to collapse
I know this method for a long time and it never worked for me
Related
Hey,
currently, I have got CM10 latest nightly. I can write SMS but have bad audio quality in calls. This is nothing special and has been discussed in other threads. But there is one question, which is not answered in these threads:
Do I need to flash a new baseband? or will a future CM10 nightly fix this issue by its own?
Thanks for any help!
P.S.: Here is my current configuration:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Better you flash new baseband..
20L n 20s are woking for me.
Also 20L will match with cm10 RIL.
Well, this is kinda ambiguous. On one hand, you've probably had zero issues on CM7 ROMs using the exact same baseband just with a different RIL. Thus, it's possible that a new nightly could resolve this issue.
But on the other hand, some people have reported improved quality when using a new baseband so it's possible that flashing a new baseband may solve your problems.
I recommend you try out new basebands if it's urgent that you get calls working properly again.
Kinimod01 said:
Hey,
currently, I have got CM10 latest nightly. I can write SMS but have bad audio quality in calls. This is nothing special and has been discussed in other threads. But there is one question, which is not answered in these threads:
Do I need to flash a new baseband? or will a future CM10 nightly fix this issue by its own?
Thanks for any help!
P.S.: Here is my current configuration:
Click to expand...
Click to collapse
yeah theres a hole thread about this questions...
A lot of people, including me, tonyp and RC are using v10b 218 and its working pretty fine!
http://forum.xda-developers.com/showthread.php?t=1658047
You need to try out some BBs... theres difference for everyone here... One example, my friend has the same phone and his living in an other city near me, so the same COUNTRY, but my o2x is working perfect ond v10b... but his one got problems with SOUND, GPS... and and and.
So download few of them and just try it...
p.s. BB RIL Thread: http://forum.xda-developers.com/showthread.php?t=1966078
I'm using 420 not 218.
Didn't try any other.
Sent from my Nexus 7 using xda app-developers app
I flashed 521(20s) yesterday, yet it didnt bring much.
since i need the voice call, i have to revert back to CM7...then the nightmare starts...
sometimes it works, sometimes (after reboot) it says "unknown" bb...also getRil can not help...
So i have to flash back to 725 and hope RC could fix it without having to flash the stupid BB...
So my suggestion is: do Not flash any BB, except that u got a backup phone, otherwise when u need a working phone on the way... u might have big trouble to restore back to CM7
Hey everybody !
First of all I want to say hello, as although I've been watching the forums for a while now, I have just registered today
The small issue that I have is that the network icon is stuck in R - roaming - all of the time.
I have tried copying various spn-conf.xml files, setting permissions, even tried flashing a new modem.
When I flashed CM11 the icon seems to work (it shows H, H+, EDGE, etc.), I have also tried copying various files
from that rom with no luck. And automatic/manual/data off/on combination as well.
It seems to be the rom issue (Team Asylum Omni 4.4.2 Naughties - every version that I have tried), but I do not have 10 posts yet so I cannot ask my question in the rom development thread.
It would be great if anyone could help me with it.
Thank you
1. Welcome to the forum
2. Be active. 10 posts is not a hurdle.
3. Settings > wireless & networks > more > mobile network settings
Untick national/data roaming?!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not a ROMs fault. Play around with the ROM instead of playing with other files...
Explore your ROM...
I have tried that, still on R.
The thing is that my network operator (Tesco) is using other operator antennas,
so I need roaming data enabled in order to have internet.
Thanks for answer and I will be active
Okay. Did you check the APN settings for Tesco? Are they similar (i.e. the same) as on CM?
Otherwise you could use the g+ omni community. Maybe you'll find other Tesco users who could help you out.
I tried and they are the same, I also tried restoring default ones from apns-conf.xml in both Asylum and CM11 files.
I will try asking there, thanks for your help again.
I've managed to fix it by adding "values-mcc272-mnc11" folder (from CM11 framework-res.apk) to Omni framework-res.apk, so if you run into similar problem, post it here and I can explain what I did step by step
Facing Roaming "R" symbol Issue on CM12
@arasgym
I am also facing the same problem but on cm12,
Even though I am not roaming it is showing R symbol.
Can you pls help me out to resolve the same?
Was it shown properly in the previous version ?
So i've been facing this issue on the Nexus 6 for a long time now. It was there even when i was running stock.
Current state : Rooted, Chroma ROM 5.0.2
Issue count (daily) : 4-5 times
The problem : Random crashes. There is nothing specific that seems to trigger it. Dont know whether this is a memory leak issue or not.
When the devices crashes / freezes, a glitch distortion appears on screen, rendering all keys except power useless. A forced restart is the only way to get back.
Please follow the images for better understanding :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Questions :
1) Is this a common issue?
2) Should i relock the device and get it exchanged?
3) If i cant exchange it, what should i do?
Thanks.
Thats never happened to me on stock or CM12....
I would contact who ever you bought it from motorola, google , or a carrier and get it replaces you have the year warranty and the pictures you took can be your proof? ...
same issue
I have same issues friend, from the first day. Now i flash latest 5.1 and testing. if i have it again i'll return my device
After testing lollipop 5.1 muy phone freeze again with same distorsión on screen. Its a fresh flash from factory images. I think i RMA because i dont know what cause this
I had the same issues, it happened randomly usually while using the camera or texting with Textra. I was using Liquid Smooth.
I flashed the latest Rebased version of Liquid Smooth and havent had a crash in over a week now. Hope this helps.
Thanks friend, im going to try líquid smooth
mistermoha said:
Thanks friend, im going to try líquid smooth
Click to expand...
Click to collapse
Did it work for you? Crashes have lessened on my chroma 5.0.1 flash but still not sure about whether the issue is fixed or not. Hell, i dont even know what this is :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's still 5.02. Build is LRX22G.T800XXU1BOE2 dated 12May.
The kernel and SE for Android was updated. Looks like they fixed a few Bugs.
Downloading now
Just snagged it myself in Canada. Confirming LRX22G.T800XXU1BOE2 build number.
Otherwise not seeing anything different. Any major bugs that other people were running into that are now squashed?
--Databoy2k
How about a memory leak fix?, or do we have to wait for v5.1 for that.
John.
From what I can see they have fixed the Samsung Lollipop Netflix bug where the video freezes after about 30 seconds. I just tried Netflix for a while and no video freeze! Yay!
databoy2k said:
Just snagged it myself in Canada. Confirming LRX22G.T800XXU1BOE2 build number.
Otherwise not seeing anything different. Any major bugs that other people were running into that are now squashed?
--Databoy2k
Click to expand...
Click to collapse
I think I will try this on my UK Tab S tomorrow.
More bloat and less fixes in this OTA.
ItsLasher said:
More bloat and less fixes in this OTA.
Click to expand...
Click to collapse
What bloat? Where do you find that evident?
Damn, why did this come out a day after I rooted my Lollipop Tab S?
I am making the assumption that I will be notified when this is available as I have checked and nothing. I hope this is not a Samsung gradual update that takes 6 months to get around the world! Does anyone have a download for it to stop the 3 month wait?
Yeah, I wonder if this affects my stock SM-T800 with root. Hmmmm....
Deleted.
anymore info on potential improvements in this update?
Dunno about the improvements. I installed the update, then rooted it again, and installed TWRP recovery back.
I can say I haven't noticed any issues, so at least it is safe to install this, and it did fix the Netflix playback issue I mentioned earlier.
I also think it seems to match my fingerprint better too, but it may just be a placebo effect.
SayWhat10 said:
anymore info on potential improvements in this update?
Click to expand...
Click to collapse
I've just flashed my XZ1C to the newest Customized UK firmware with US OEM.sin (for fingerprint sensor) without flashing /data.
Everything is OK until I go to the settings APP...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know it's caused by the newest firmware it self or it's because I didn't flash /data ?.
Any ideas about it?
KayMW said:
I've just flashed my XZ1C to the newest Customized UK firmware with US OEM.sin (for fingerprint sensor) without flashing /data.
Everything is OK until I go to the settings APP...
I don't know it's caused by the newest firmware it self or it's because I didn't flash /data .
Any ideas about it?
Click to expand...
Click to collapse
Factory reset might fix it, but most likely a complete reflash, wiping data. This has been reported before on the thread, happens when you try to mix-and-match firmwares.
The following won't be news to people more experienced than I, but I managed at one point to get my phone into what I presume is a bootloop. Waiting for the right moment, and then connecting it in flash mode to the computer allowed me to use Xperia Companion to reinstall the current firmware correctly. I'm glad that Sony provides this functionality in its PC/Mac software. Perhaps in first backing up just what you need through Xperia Companion, then doing a software repair (reset/flash), and then restoring your (minimal) data would do the trick. I know how annoying these little anomalies can be, I had the weird experience of having GBoard reinstall itself on every reboot until I "fixed" the installation as I outlined above. Good luck!
Didgesteve said:
Factory reset might fix it, but most likely a complete reflash, wiping data. This has been reported before on the thread, happens when you try to mix-and-match firmwares.
Click to expand...
Click to collapse
Thanks for reply!
I'll try to do factory reset the phone. But I'm still wondering why this will cause the Settings APP to work like this ?
I had the problem when i first flashed the german 8.49. I had the same weird menus and txt because i had the origianl us oem. i reflashed w/ complete custom de (I don't have tmobile) and everything is back to normal. Also, I got the ota update to the current version. I assumed the problems were because the us oem was outdated, but maybe not.