Database Info

[Q] Why STk not working on Galaxy S radio?

Ok. I've seen that it is not possible to have Stk app running under Nexus S under normal circumstances. So I noticed that Galaxy S and Nexus S have the same baseband chip and that Galaxy S comes with Stk.apk and it works fine. So I was able to flash a Galaxy S radio image on my Nexus S, and for my surprise, the Stk didn't work.
Could someone give me a link to a Galaxy S I9000 or I9000B radio image which responds to Stk.apk requests? I've tested some, but I refuse to believe that it is not working cause of black magic... I was sure it would work So this is my last try, if someone have a Galaxy S radio which responds to Stk, I would really appreciate the image name.
Thanks!

HugoS said:
Ok. I've seen that it is not possible to have Stk app running under Nexus S under normal circumstances. So I noticed that Galaxy S and Nexus S have the same baseband chip and that Galaxy S comes with Stk.apk and it works fine. So I was able to flash a Galaxy S radio image on my Nexus S, and for my surprise, the Stk didn't work.
Could someone give me a link to a Galaxy S I9000 or I9000B radio image which responds to Stk.apk requests? I've tested some, but I refuse to believe that it is not working cause of black magic... I was sure it would work So this is my last try, if someone have a Galaxy S radio which responds to Stk, I would really appreciate the image name.
Thanks!
Click to expand...
Click to collapse
If you use CyanogenMod, STK works fine. It even initializes as you boot your phone or turn on then turn off airplane mode (you see the "default message" toast at the bottom of the screen).

polobunny said:
If you use CyanogenMod, STK works fine. It even initializes as you boot your phone or turn on then turn off airplane mode (you see the "default message" toast at the bottom of the screen).
Click to expand...
Click to collapse
I guess there's something else other than the radio image bugging communication of proactive commands. I've downloaded a CyanogenMod 10 build for galaxy s and flashed the modem.bin image on the Nexus. Baseband version is updated (can check trough logs and settings), but still the messages are not supported. I wonder what else could be interfering with proactive commands. Do you have any ideas?

HugoS said:
I guess there's something else other than the radio image bugging communication of proactive commands. I've downloaded a CyanogenMod 10 build for galaxy s and flashed the modem.bin image on the Nexus. Baseband version is updated (can check trough logs and settings), but still the messages are not supported. I wonder what else could be interfering with proactive commands. Do you have any ideas?
Click to expand...
Click to collapse
Sadly, no. I don't need STK here.
But what is your goal? I have the feeling you might be hunting high and low trying to flash a Galaxy S radio, only to get STK working, when if you tell us what is your end goal someone might chime in with better and more precise advice.
As I mentioned, CM10 already has STK.apk working (by the way STK has to be built for the correct OS version and phone, can't just swap it around). Usually you just have to set a SIM pin to "enable" it.

polobunny said:
Sadly, no. I don't need STK here.
But what is your goal? I have the feeling you might be hunting high and low trying to flash a Galaxy S radio, only to get STK working, when if you tell us what is your end goal someone might chime in with better and more precise advice.
As I mentioned, CM10 already has STK.apk working (by the way STK has to be built for the correct OS version and phone, can't just swap it around). Usually you just have to set a SIM pin to "enable" it.
Click to expand...
Click to collapse
My goal is to have the Stk running on Nexus S. For what I've searched the net, I haven't found anyone who was able to do it... You said CM10 already has STK working, but is this for Nexus S?
I didn't get what you said about setting up a SIM pin to enable it... As I see it, if the STK.apk is available in one phone (let's say motorola GB) this means the SIM is already configured to access sim menus and applications. So if I put the same SIM on Nexus S, the natural behavior would be to have Stk.apk pop up in the launcher...
The problem is that Nexus S doesn't show the app in the drawer, and the reason behind that is that the lower levels (proprietary ril) don't send specific messages. To be precise:
Frame work Stk sends a RIL_REQUEST_REPORT_STK_SERVICE_IS_RUNNING message to ril exepecting an ok answer.
What happens is that RIL respondes REQUEST_NOT_SUPPORTED.​
My attempt of flashing a Galaxy S radio on Nexus was based on an idea after seeing this message being answered in a friend's GS.

HugoS said:
My goal is to have the Stk running on Nexus S. For what I've searched the net, I haven't found anyone who was able to do it... You said CM10 already has STK working, but is this for Nexus S?
I didn't get what you said about setting up a SIM pin to enable it... As I see it, if the STK.apk is available in one phone (let's say motorola GB) this means the SIM is already configured to access sim menus and applications. So if I put the same SIM on Nexus S, the natural behavior would be to have Stk.apk pop up in the launcher...
The problem is that Nexus S doesn't show the app in the drawer, and the reason behind that is that the lower levels (proprietary ril) don't send specific messages. To be precise:
Frame work Stk sends a RIL_REQUEST_REPORT_STK_SERVICE_IS_RUNNING message to ril exepecting an ok answer.
What happens is that RIL respondes REQUEST_NOT_SUPPORTED.​
My attempt of flashing a Galaxy S radio on Nexus was based on an idea after seeing this message being answered in a friend's GS.
Click to expand...
Click to collapse
As I said, go to the security option in CM, enable SIM pin. That usually makes STK popup after a reboot in the launcher.

polobunny said:
As I said, go to the security option in CM, enable SIM pin. That usually makes STK popup after a reboot in the launcher.
Click to expand...
Click to collapse
I'll get my hands on a SIM with available pins to test this... I'll post back ASAP.

HugoS said:
I'll get my hands on a SIM with available pins to test this... I'll post back ASAP.
Click to expand...
Click to collapse
You don't have a SIM? You should be able to set a PIN password on any working SIM as far as I know.

[Q] How is the Network Operator determined?

Hi Android-Guru's,
I need some help to research a weird issue that is happening for me on almost ANY custom ROM - mostly CyanogenMOD based, but it is consistent as well throughout all current KitKat builds including AOSP and MOKEE.
What happens is, regardless of which network operator I am connected to, the phone in status-bar and settings menu will always show my SIM card operator (Telekom.de). Even when I go to manual network selection menu and the list of operators is retrieved, I get a list of 6 x Telekom.de
Now the argument is correct, that this is cosmetic, it becomes tricky for me when I go abroad - which I do on a daily basis. So selecting the correct foreign network operator is crucial to save on roaming charges e.g. LUXGSM may be cheaper than TANGO, etc. however, I have no way to properly determine that, since the list will simply show 5 entries with "Telekom.de".
I have a XT925 (RAZR HD) and this works perfectly fine on stock. It works also perfectly fine on the early (10.2) CM releases. At some point starting with 4.3 firmware iterations, I started seeing the "wrong" - I researched google for hours and was directed to compare various eri.xml, spn-conf.xml and decompiled the framework-res.apk to see if maybe the methodology for displaying carrier name had changed between working and non-working builds, but couldn't find any difference.
So, since there are probably enough XT925 users out there, what are you seeing? Could this be related to my sim card which is fairly old (4-5years)? Where do I find the code behind carrier display in android?
appreciate your help,
Stefan

69 views and no one here with a GSM XT925 who is running a recent build of KK and able to perform an operator search to see what he/she gets?

I have a xt925, I don't have that problem but I found this app maybe helps you https://www.google.com/url?sa=t&sou...Wlreb37Zp73w38emuzZ46WA&bvm=bv.60799247,d.aWc
Enviado desde mi HTC Explorer A310e mediante Tapatalk

DorianX said:
I have a xt925, I don't have that problem but I found this app maybe helps you ....
Click to expand...
Click to collapse
thanks for the feedback and the suggestion, Dorian - I tried it, but takes me to the regular network selection screen in the settings that just displays the list of "Telekom.de's" but good thought.
I wonder, what is different with my setup - might this be a baseband or modem issue?
I realized, that my phone number in status screen shows as "unknown" as well - but IMEI shows correctly, not sure if that is related.

still looking actively for an answer.. I tried to go back to stock with RSD Lite to see if any of my baseband or modem files is screwed, but I couldn´t get RSD to recognize my phone.. probably an indication that my device has some kind of issue!?
Anyone any ideas?

Couldn't find Mobile Network Type

Hello, Recently I have bought an Unlocked At&T LG G3 The seller told me that the phone has a bad IMEI But it's unlocked to be used interntionally. When I received it, It's working fine, except the data network speed trough EDGE is too slow. As yo can see on the screenshot below I couldn't find the option to change the network type. and I'm stuck at "E" which mean EDGE.
http://s14.postimg.org/8r7vs0x27/Quick_Memo_2015_09_09_11_41_43_1.png
The phone's model is LG-D850 and it's running android 4.4.2 KitKat. it has no IMEI when I dial *#06# it shows IMEI: 0-05 on Settings/about phone/Status... it says IMEI: 0

Anyone here to help?

First, here are the possible reasons why you don't have an IMEI:
The phone was reported lost or stolen in the past.
The phone is still active on the owner's wireless carrier account.
There is money owed on the wireless carrier account to which the ESN/MEID/IMEI is connected.
For the reasons above, this community does not support such devices and you will probably not get any help.
But, this can also happen during a bad flash, so to fix the issue, you have 3 options:
Reset, unroot, then root and flash again
Try the suggested steps in this video
Find a company that can fix the problem by sending the phone to them

youngunix said:
First, here are the possible reasons why you don't have an IMEI:
The phone was reported lost or stolen in the past.
The phone is still active on the owner's wireless carrier account.
There is money owed on the wireless carrier account to which the ESN/MEID/IMEI is connected.
For the reasons above, this community does not support such devices and you will probably not get any help.
But, this can also happen during a bad flash, so to fix the issue, you have 3 options:
Reset, unroot, then root and flash again
Try the suggested steps in this video
Find a company that can fix the problem by sending the phone to them
Click to expand...
Click to collapse
Thanks for your reply, I'm not seeking to restore the IMEI. I just want to have the option to switch mobile network type. Should I root the phone and install a custom ROM?

AminhoVic said:
Thanks for your reply, I'm not seeking to restore the IMEI. I just want to have the option to switch mobile network type. Should I root the phone and install a custom ROM?
Click to expand...
Click to collapse
My bad, thought you wanted the IMEI back. In that case, the E (edge) is showing up could be due to Maroc Telecom throttling your connection or their towers could be far way (happens when you travel cross country too). Anyway, if you want to fiddle with network settings and try to get it to work BEFORE attempting to flash any ROM, try the following [3845#*855# 3845#*850#] USSD code from your stock dialer. You will get a hidden menu containing a juicy list of options and settings, so what you are probably looking for is the "LTE-Only" option (I am not sure though, but you can look through the settings).
And as always, attempt the suggestions AT YOUR OWN RISK.

youngunix said:
My bad, thought you wanted the IMEI back. In that case, the E (edge) is showing up could be due to Maroc Telecom throttling your connection or their towers could be far way (happens when you travel cross country too). Anyway, if you want to fiddle with network settings and try to get it to work BEFORE attempting to flash any ROM, try the following [3845#*855# 3845#*850#] USSD code from your stock dialer. You will get a hidden menu containing a juicy list of options and settings, so what you are probably looking for is the "LTE-Only" option (I am not sure though, but you can look through the settings).
And as always, attempt the suggestions AT YOUR OWN RISK.
Click to expand...
Click to collapse
I'm living at a major city, here the 4G works great. So yeah I have to change the mobile network type since it is on EDGE by defaut I guess.
I attemted the USSD code however it says "connection problem or invalid mmi code" after I hit dial. I have also tried a bunch of codes before but no luck.
I think I will falsh the phone that's the option left. I just have rooted the phone, then I will install TWRP and I will try to flash a ROM in it. What do youu suggest me to use from those ROMs posted here ?

AminhoVic said:
I'm living at a major city, here the 4G works great. So yeah I have to change the mobile network type since it is on EDGE by defaut I guess.
I attemted the USSD code however it says "connection problem or invalid mmi code" after I hit dial. I have also tried a bunch of codes before but no luck.
Click to expand...
Click to collapse
I get the same error if I use a third party dialer app (i.e., Dialer) until I tried the stock phone app.
I think I will falsh the phone that's the option left. I just have rooted the phone, then I will install TWRP and I will try to flash a ROM in it. What do youu suggest me to use from those ROMs posted here ?
Click to expand...
Click to collapse
I haven't flashed any custom ROMs on my LG, but from experience, each device somehow reacts differently to custom ROMs. For instance, I've flashed my S.G. Note (i717) over 30 times and some ROMs were stable at first then started having issues with them.
The best advice I can give you, is to pick a ROM from the list you posted and check the comments to see if it is stable or too many users have issues with it.

AminhoVic said:
I'm living at a major city, here the 4G works great. So yeah I have to change the mobile network type since it is on EDGE by defaut I guess.
I attemted the USSD code however it says "connection problem or invalid mmi code" after I hit dial. I have also tried a bunch of codes before but no luck.
I think I will falsh the phone that's the option left. I just have rooted the phone, then I will install TWRP and I will try to flash a ROM in it. What do youu suggest me to use from those ROMs posted here ?
Click to expand...
Click to collapse
Ever think that it does not have the correct bands for your carrier?

[Bug] Blank Toast above home button (Solved : I think VoLTE sim related)

(Solution)Update : I did little bit more (well, honestly a lot more digging ) It turns out this wasn't Xposed or Rom or anything related to specific setup related after all !
Many users had same problem ( Random Grey bubble above home button / Black Toast) in past in 5.1 & 6.0 as well & even on Nexus 6
I THINK as described by user on Androidcentral it's related to specific SimCard & my guess is, it happens on VoLTE simcards (Specific Reliance Jio in my case ) because i have other 4G sim (Vodafone) without VoLTE and i'm not getting any "Blank Toast" after inserting it
here are some of links i found while digging and IMO 1st one is somewhat correct about occurrence of issue. ( i'm with him bcz i having same experience till now)
http://forums.androidcentral.com/ask-question/600223-empty-toast-message-wind-mobile.html
https://www.reddit.com/r/nexus6/comments/2zl00j/since_51_getting_strange_periodic_grey_circles/
https://www.reddit.com/r/AndroidQuestions/comments/308xjy/black_dot_appearing_on_android_51/
https://www.reddit.com/r/nexus6/comments/3neppi/i_have_constant_toast_notifications_on_my_screen/
https://code.google.com/p/android/issues/detail?id=196384
as you see in last link someone reported it to google but they didn't take it seriously with not much data.
even though i believe i have enough data, i'm not gonna report it again because i don't have patience to deal with official channel :silly:, that's why i'm writing this long post with almost everything i got, to help someone looking answer related this in future & for any philanthropic who wants to report & deal with it
may be it's due to lack of VoLTE related hardware in N5.
(all above points are just my speculation through data i got, i'm not certain about root cause, but i hope to never see that bug on other Sim Cards :fingers-crossed: )
Problem
As you can see from attached SS , i'm getting this annoying grey bubble randomly (any app/game , any time ! nothing is specific about it's occurrence that i can find ) i got that bubble at-least 5 times while writing this post as well !!
So is it just me or someone other also have same problem ? If someone had similar problem in past and have any solution plz tell )
My setup :
M4B30X Stock (dirty flash over September) + Systemless SuperSu 2.78 + Xposed v86 (official) + gravity Box
(If i'm the only one having this problem, then i'll Clean flash system but if someone ever had similar problem kindly share solution bcz if possible i want to avoid the clean flash )

Seems like an empty toast message.

Running M4B30X since yesterday, and there's no grey bubble on my end.

Sideload OTA now. No issues
Sent from my Nexus 5 using Tapatalk

kicksilver said:
Running M4B30X since yesterday, and there's no grey bubble on my end.
Click to expand...
Click to collapse
lpganesh said:
Sideload OTA now. No issues
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yah i re-flashed it without Xposed and it's working fine now so i guess it was the issue. anyway thanks for confirming
btw today i'm going to flash Pure Nexus bcz i can't live with this un-customizable stock for long and xposed & cataclasm mod giving new & new errors so that's it for me with security updates i'll live happily with older august Pure Nexus as long as i can resist update LOL

download from PC. it'll most likely complete.

OP updated with possible solution

Based on your findings, could you try Deleting sim toolkit APK to test if it goes away?, im assuming its interpreting some kind of mesage as ADs from your carrier, however it fails and throws an empty toast

opssemnik said:
Based on your findings, could you try Deleting sim toolkit APK to test if it goes away?, im assuming its interpreting some kind of mesage as ADs from your carrier, however it fails and throws an empty toast
Click to expand...
Click to collapse
thanks for suggestion but it was debloated before i clean flashed factory image, so i guess it's happening regard-less of STK's presence or not

Question Anyone having issues with VoWiFi NA version?

I just got the NA version of the ROG Phone 5 and sadly I cannot get VoWiFi working on TMobile. Sadly I'm in an area where I don't get the best signal and it's extremely important for this feature to work. Especially considering I spent 1k+ for this phone... Any help/guidance would be appreciated.

Have you enabled it in settings and then tried a reboot?
I've also noticed that it may not work until the SIM is installed BEFORE initial setup (or before a factory reset)

I confirmed with other people too. US version doesnt have Tmobile wifi. If it would, I would have bought one

twistedumbrella said:
Have you enabled it in settings and then tried a reboot?
I've also noticed that it may not work until the SIM is installed BEFORE initial setup (or before a factory reset)
Click to expand...
Click to collapse
Yeah I tried that but didnt work so i manually enabled it using the phone dialer and after i toggle it on or off it will turn on but it turns off after reboot so need to root it so i can make the settings stick.

daviddem said:
I confirmed with other people too. US version doesnt have Tmobile wifi. If it would, I would have bought one
Click to expand...
Click to collapse
It actually does work

My AT&T and T-Mobile SIMs (both Red Pocket MVNO) have VoLTE but not VoWiFi.

kva1992 said:
It actually does work
Click to expand...
Click to collapse
So do you get wifi calling with US ROG phone on Tmobile?

daviddem said:
So do you get wifi calling with US ROG phone on Tmobile?
Click to expand...
Click to collapse
Yup just have to manually enable it Everytime it boots up but if you root it you can set the props and it will be permanent. In the process of doing that atm.

kva1992 said:
Yup just have to manually enable it Everytime it boots up but if you root it you can set the props and it will be permanent. In the process of doing that atm.
Click to expand...
Click to collapse
Thank you. I was debating between ROG or xperia 1iii. but if this works. Ill get ROG.
If you dont mind, can you please post the dialer code

daviddem said:
Thank you. I was debating between ROG or xperia 1iii. but if this works. Ill get ROG.
If you dont mind, can you please post the dialer code
Click to expand...
Click to collapse
Sure here you go *#*#3642623344#*#*
You should be able to copy and paste if that doesn't work try pasting but delete the last * and add it manually. If that still doesn't work just manually type it in. But I tested it out a few times nd it works even turned on airplane mode and it works. Wi-fi calling was a deciding factor for me lol was about to return it until I found out I could get it to work properly.

daviddem said:
Thank you. I was debating between ROG or xperia 1iii. but if this works. Ill get ROG.
If you dont mind, can you please post the dialer code
Click to expand...
Click to collapse
kva1992 said:
Sure here you go *#*#3642623344#*#*
You should be able to copy and paste if that doesn't work try pasting but delete the last * and add it manually. If that still doesn't work just manually type it in. But I tested it out a few times nd it works even turned on airplane mode and it works. Wi-fi calling was a deciding factor for me lol was about to return it until I found out I could get it to work properly.
Click to expand...
Click to collapse
I'd like to add that after running the dialing code you have to enable wifi calling in the settings app.
Aswell as that, at least for me, I need to disable and re-enable it within settings after re-running the dial after reboot, for it to actually reconnect
Just to avoid any confusion.
This does work tho! Kva is right!

Trickster29 said:
I'd like to add that after running the dialing code you have to enable wifi calling in the settings app.
Aswell as that, at least for me, I need to disable and re-enable it within settings after re-running the dial after reboot, for it to actually reconnect
Just to avoid any confusion.
This does work tho! Kva is right!
Click to expand...
Click to collapse
Thank you both. Ill order the phone and try it.

Trickster29 said:
I'd like to add that after running the dialing code you have to enable wifi calling in the settings app.
Aswell as that, at least for me, I need to disable and re-enable it within settings after re-running the dial after reboot, for it to actually reconnect
Just to avoid any confusion.
This does work tho! Kva is right!
Click to expand...
Click to collapse
It's so stupid wish they enabled it by default would make all our lives easier

kva1992 said:
It's so stupid wish they enabled it by default would make all our lives easier
Click to expand...
Click to collapse
I agree, but idk if they need some authorization from T-Mobile to enable it by default and we're just the end user working around that.
Otherwise, I'm not really sure at all why the functionality is developed but not enabled by default.

Trickster29 said:
I agree, but idk if they need some authorization from T-Mobile to enable it by default and we're just the end user working around that.
Otherwise, I'm not really sure at all why the functionality is developed but not enabled by default.
Click to expand...
Click to collapse
Yeah it's stupid I ended up talking to advanced tech support and the guy has never heard of ROG phone 5 and said I should return it cuz it seems like it's a hardware issue.... I'm like dude it's your system not giving me proper access's and authorizing my phone... He's like I guess you know more about phones than I do... The idiot even made me reset my phone to try and fix it even though I told him several times that has nothing to do with it.... I swear I have no idea how some of these morons get jobs as IT... At least have basic IT understanding....

They're not in IT. They're customer service reps. They read from a script.
Check out the movie The Internship. It's just like that.

twistedumbrella said:
They're not in IT. They're customer service reps. They read from a script.
Check out the movie The Internship. It's just like that.
Click to expand...
Click to collapse
Well, when I'm talking to the advanced Technical team I am not talking to customer service reps... I talked to a customer service rep and they forwarded me to the IT team. Considering they are called advanced technical teams I would assume they are in IT. whereas the initial person I talked to was and clearly stated she was a customer service rep.

The only difference between the two people you spoke with is that one had access and authorization to suggest more "advanced" solutions. I'm not saying they shouldn't have better training, but legitimate IT professionals rarely work the call center as more than a summer job.
Anyway, the point was that they're a waste of time unless the issue is the SIM card or your plan. It's unfortunate.
Dial codes typically trigger an intent. If you can track down the intent, you can have it launch automatically on boot. Once that's taken care of, it shouldn't be too hard to automatically enable the setting. That is assuming you called because setting the prop didn't work.
Another alternative if you do have a property and can't write to system is setting it with a magisk module, since the system is read only on a firmware level.

twistedumbrella said:
The only difference between the two people you spoke with is that one had access and authorization to suggest more "advanced" solutions. I'm not saying they shouldn't have better training, but legitimate IT professionals rarely work the call center as more than a summer job.
Anyway, the point was that they're a waste of time unless the issue is the SIM card or your plan. It's unfortunate.
Dial codes typically trigger an intent. If you can track down the intent, you can have it launch automatically on boot. Once that's taken care of, it shouldn't be too hard to automatically enable the setting. That is assuming you called because setting the prop didn't work.
Another alternative if you do have a property and can't write to system is setting it with a magisk module, since the system is read only on a firmware level.
Click to expand...
Click to collapse
How would I set that up using magisk module? One Issue I have noticed is the wifi calling turns itself off after a while. sometimes it works for several hours other times maybe a day but then turns off and I have to restart the phone and run the command again.

Developer Guides
The Magic Mask for Android
topjohnwu.github.io