Related
I received a new phone today that I got on eBay, a Cobalt SP300. The hardware itself is pretty decent, except for the camera, but I've run into some issues with Android. I think it might be my APN settings, even though I've tried many different variation, but I can't get outbound texting to work. It just says sending for a while and then fails. Inbound texting however works fine.
Another issue is that I am stuck on the Edge network. I took a game since the eBay description said Edge only, but I was hoping it might have been in error since this chipset inherently has 3G built into it. But I think for some reason this company disabled it. Also kind of odd since it says it allows HSDPA right on the box... Anyway,when I go into the info screen (*#*#4636#*#*) I see it says GSM only, but it won't let me change it. I remember seeing on a russian site some sort of debugging screen where you could see all bands the phone allows. Anyone know how to get to that?
Would anyone be able to help with this?
Would knowing the baseband or kernel version help?
Thanks
I have also tried getting into an engineering mode as well using *#*#3646633#*#* and *#*#197328640#*#* to view band modes but neither of those codes work, it just brings me back to the dialer screen.
As far as the no incoming texts go, I figured that out by putting the proper SMSC code for AT&T in the messaging app setting. Hopefully this bit might help anyone else with the same problem.
I don't know if anyone may be able to answer this now but with so many of these selling on eBay someone else is bound to searching for the same fix as I am for the 3G. I made the EDGE bearable by using Opera Mini however.
Also, I found the original Chinese version of this phone, the Morningside A206.
And it turns out I'm not alone in the search for 3G, I found something in Chinese with someone inquiring why their A206 won't connect to 3G.
I would post these links but I don't have enough posts.
3G is looking less likely to be activated.
I found an app called Mobileuncle MTK Tools that gets you into engineer mode. I go down to Band Modes (Screenshot attached) and the GSM modes are all selectable but all of the UMTS modes are grayed out. It just seems so weird I know this is a MT6575 chipset which supports it. Is there anything else that can be done?
I also happened to find out how to root the phone if anyone comes across this and needs to know.
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=2046161
I also had to find the drivers elsewhere, so just google this .rar file: usb_driver_MT65xx_Android_ZTE_v821.rar
The first google result from rghost . net worked fine
I have a Mate7 TL10 that has 7 link +
This is a good feature WiFi enabled and even when a known network is nearby.
It deactivates when leaving the network again.
I have found the x2 how to activate it.
The MP X2 must be rooted.
Install a Build Prop Editor,open it and search the Line
ro.config.hw_wifipro_enable=false
change the false to true
then it must look like
ro.config.hw_wifipro_enable=true
done.
Save the Build Prop file and Reboot.
Then this should be seen in the Settings (See Pics in Attachment)
I have tested it with Android 6 (B205).if it works with 5.1.1 I do not know.
However, it may take longer to be Link + automatically enable / disable it must know the network only learn.
I hope you understand my bad English!
The same works with Roaming+ and Signal+
see the Pic in Attachment,but if it really works, I can not say
Great feature! Thanks!
I recently received the July AQG5 UK update for my Galaxy S8+ G955F (Exynos) and the service mode menu (*#2683662#) now says not supported when in the prior firmware version it worked fine. the service mode menu allows you to lock onto specific LTE bands and enable more advanceed features such as 4x4 MIMO and 256QAM as well as other things, as i mentioned earlier it worked fine in the previous update but now just says not supported.
The service mode code •#0011# still works fine, its just the other one mentioned that no longer works, anyone know why or if can get it back without having to flash back to a previous firmware version?
bump
bump, come on people someone must have some info
have you tried *#2263# ??
It's disabled on my Indian set also.
Maybe the 6gb set suffers with this aspect
esjames said:
have you tried *#2263# ??
Click to expand...
Click to collapse
that is for the snapdragon version, i have the international exynos version and the *#2683662# code used to work but after the update it now says unsupported
bluheart said:
It's disabled on my Indian set also.
Maybe the 6gb set suffers with this aspect
Click to expand...
Click to collapse
possibly yes, im not sure which soc the indian version has whether its snapdragon or exynos but if its exynos then seems samsung have disbaled it after a recent update for whatever reason
After months there is still no information for it on the Internet other than that it's not working, so, let's start.
What's in
Code:
logcat -b all -s RILD -s RILD2 -s RILS -s ServiceModeApp_RIL -s XMLParser
?
Which CSCs have it disabled?
Is it accessible with root?
That menu *#2683662# allowed the selection of antennas on a cell tower; channel selection (12 channels in UMTS band 1 as an example); band selection; CA enable/disable; LTE CAT selection; UMTS/LTE Release selection; viewing of 2G/3G neighbours by arfcn/uarfcn; 256QAM/4x4(but no one got it to rank 4, not working? no antenna for the BTS?); reject codes; displayed supported bands and CA Combinations; etc.
Bryan48765 said:
After months there is still no information for it on the Internet other than that it's not working, so, let's start.
What's in
Code:
logcat -b all -s RILD -s RILD2 -s RILS -s ServiceModeApp_RIL -s XMLParser
?
Which CSCs have it disabled?
Is it accessible with root?
That menu *#2683662# allowed the selection of antennas on a cell tower; channel selection (12 channels in UMTS band 1 as an example); band selection; CA enable/disable; LTE CAT selection; UMTS/LTE Release selection; viewing of 2G/3G neighbours by arfcn/uarfcn; 256QAM/4x4(but no one got it to rank 4, not working? no antenna for the BTS?); reject codes; displayed supported bands and CA Combinations; etc.
Click to expand...
Click to collapse
the logcat command you provided doesn't really give any useful information which can pinpoint any potential solution.
With regards to the CSC's, i can only comment on the XEU CSC which is part of the OXM multi csc and the one my phone is on and on that it says not supported for the code.
I haven't checked on root, don't really want to root my device
hamzahshakeel said:
the logcat command you provided doesn't really give any useful information which can pinpoint any potential solution.
Click to expand...
Click to collapse
But it could be compared with the logs of a working 2683662. How many of those names appear? Maybe Samsung has changed those names. It's the system wide no-root logcat "adb logcat"?(not sure about the /data/log one) It's while the RIL service mode is starting?
Bryan48765 said:
But it could be compared with the logs of a working 2683662. How many of those names appear? Maybe Samsung has changed those names. It's the system wide no-root logcat "adb logcat"?(not sure about the /data/log one) It's while the RIL service mode is starting?
Click to expand...
Click to collapse
i tried the logcat using the filters you provided (i.e. RILS, RILD etc) and yes it does bring back logs relating to those services however its not enough, all it outlines is when i type the code and monitor the logs subsequnt to the typing of the code the log just shows it trying to open the process associated with the menu, it doesnt show what it tries to do in between me sending the code and the response coming back so comparing that with a working code log will bring back nothing of note
however having said that i did try the full system wide log which was a bit teidous given it logs everything so going through it and pinpointing the relevant piece of log was a bit hard, i will attempt to log again using my s8+ and another samsung phone for which the same code works on and then post it here
try install phone info . this programm has all codes inside
Guys, the same in brazil. Since the begining of the year I've tried to activate 256QAM+MIMO 4x4 in my sumsung galaxy s8 using *#2683662# and by now it doen't work as return the message "not supported". Do you guys has reached some progress on it?
Seems they changed something inside the CP (modem.bin) and disabled the code. Flashing back the AQF7 - CP file will get back the code, but don't know the effect.
Yes I also noticed this a couple months back and made my own thread on it. So far there has been no progress except to flash a previous older update
Hi, you can get into advanced service menu with the app called phone info. Look for code 27663368378 and click Launch 0. Tested on rooted android 7, exynos galaxy s7.
no_name_no said:
Hi, you can get into advanced service menu with the app called phone info. Look for code 27663368378 and click Launch 0. Tested on rooted android 7, exynos galaxy s7.
Click to expand...
Click to collapse
Ive tried this but not work
Enviado desde mi SM-G935F mediante Tapatalk
hamzahshakeel said:
I recently received the July AQG5 UK update for my Galaxy S8+ G955F (Exynos) and the service mode menu (*#2683662#) now says not supported when in the prior firmware version it worked fine. the service mode menu allows you to lock onto specific LTE bands and enable more advanceed features such as 4x4 MIMO and 256QAM as well as other things, as i mentioned earlier it worked fine in the previous update but now just says not supported.
The service mode code #0011# still works fine, its just the other one mentioned that no longer works, anyone know why or if can get it back without having to flash back to a previous firmware version?
Click to expand...
Click to collapse
Unfortunately starting with Android v8.x.x (Oreo), test codes sent to the RilServiceModeApp via android_secret_code://<code> even by root are being denied.
If the test menu *#2263# or *#2683662# or *#2766338378# doesn't work with your current sim card, then try the following.
Find a couple of other active or inactive sim cards (can be another local carrier or from abroad), let the phone reboot and reconfigure its CSC while on the blue bootup screen, then try the code again, since test codes are CSC specific. It's a hit and miss affair, so be persistent.
If your phone is rooted, you can try these methods one at a time.
After each step, reboot the phone and try the test codes *#2263# or *#2683662# or *#2766338378#.
1. Using Shortcut Master (free version) from the PlayStore, tap on the menu, Secret Code Explorer, scroll down to 2263 or 2683662 or 2766338378 (or Menu > Search for "band"), tap on Launch0.
2. On combination firmware edit the file /efs/carrier/HiddenMenu and /efs/FactoryApp/keystr to be "ON", which will persists even after flashing back to stock firmware.
3. Copy the <CSC>_keystrings.dat from system/etc to root/etc and set permissions to 0744.
4. Try replacing the /system/priv-app/ModemServiceMode/ModemServiceMode.apk=com.sec.android.RilServiceModeApp from a previous Android version which had the codes working, and set the permissions to 0744.
5. Flash an earlier radio (CP) which had the codes working, if the current bootloader allows it to be downgraded.
This last method works on all Samsung models/firmwares without root, but requires a special test cable, which is only available for micro-USB ports at this time.
If you can find a similar cable with a USB-C connector, then it should work just fine. By the way, using an micro to C adapter does not work.
The following is only for phones with a micro-USB port, nonetheless it makes an interesting way to enable the hidden test menus.
You can actually enable most test codes (including RIL test codes which fail to execute on Oreo of newer even while rooted, such as *#2263# band change, *#2683662 lab test mode, and *#2766338378# engineering test menu, etc) on pretty much any model/firmware/region by simply plugging in a test cable into the phone (the other end doesn't have to be plugged in anywhere, it's just the built in resistor which enables test mode/FactoryMode).
It's important to follow the next steps exactly in this order: Open the dialer, exit the dialer with the Back key (not the Home button!), reopen the dialer and now it should accept most test codes.
These cheap test cables can be found on Ebay or AliExpress, just search for "Samsung 523K uart cable" or "Samsung 619K uart cable". Some come as a combo where you can simply switch the resistor values via a switch, but you must try both values, since only one or the other will work on certain models/firmwares/regions.
I've been using this method successfully for many years (currently on my Samsung S7 with the latest 2019 firmware), unfortunately these test cables are only available for micro-USB connectors, so it won't work on the newer USB-C phones even with an adapter (because it doesn't extend the resistor lines, only the data lines). If anyone finds a solution for USB-C, please post a message here.
https://developer.sony.com/develop/android-q-beta
Someone tried it?
https://youtu.be/W6BzFQqtOKg
I tried, but the problem is that the Xperia Companion gives me an error saying that my device doesn't support Developer Preview.
I will try to flash a non Operator customized firmware.
Vampirelu said:
I tried, but the problem is that the Xperia Companion gives me an error saying that my device doesn't support Developer Preview.
I will try to flash a non Operator customized firmware.
Click to expand...
Click to collapse
That's what you will need to do. Carrier branded firmware not eligible for beta
Anyone try Camera2 probe APP on Android 10 Beta?
Maybe support RAW?lol
Mine had EE UK firmware, I changed to Custom US firmware to try the Q preview mode.
All I can say is that it's not worth to leave 9 behind just yet. It's pretty much stock Android without Sony stuff in it, kinda miss it already, but all in all I only noticed one bug.
Connecting earphones with Jack will still have the speakers playing music, but you're fine with Bluetooth connection.
The gesture thingy is pretty weird by the way, fortunately there's the option to go to the classic three buttons.
Don't know if this answers you question but here's a snapshot of the raw Info
Tried it last night, some of the open issues makes it quite unusable.
Setup wizard can sync down backup data from google account/cloud, but not restore via BT/Wifi from other Xperia device
Delay with black background after the “Android Beta” information is shown before entering home screen
Camera functionality and quality are limited compared to Xperia SW
Camera button press is not starting camera, but double press on power button starts camera
Chromecast does not work for audio/video as cast icon is not shown
Media playback support is not on par with Xperia SW.
External SDcard is not fully supported for media playback and MTP
Audio routing with PHF is not fully working
Adoptable storage is not supported
Sd card is basically useless. So is dual sim.
chadd1039 said:
Don't know if this answers you question but here's a snapshot of the raw Info
Click to expand...
Click to collapse
Thank you bro.
It looks still not support raw
Hope xz3 can use Gcam on Q
This is a copy from the website and seems to not give a full actual experience..... I've been using all day and it runs well .... The Google cam app that's in it is crap bit I've installed open camera and it works great ...... And I can also play videos and use the SD card as normal ... No issues ....... Google camera does not seem to be compatible as of yet .... Until it's developed specifically for Sony I guess
It seems more stable than the Android P Beta that was pushed for Xperia XZ2 Premium. I have it installed and using it without too many issues yet either. SD card is normal but camera is very basic. All apps installed and are running well also which wasn't the case with P Beta.
Out of curiosity, how many versions do Betas usually get?
I rolled back already btw, I was already missing all the quirks that Sony brought to this phone. Also that bug I mentioned earlier - about having headphones connected *physically* and still having sound coming out of the phone speakers - was annoying me.
I installed it right after it was announced and only sort of regret it. It's stable-ish but so many things have been made useless. I just got the xz3 two weeks prior so I'm still in my adjustment phase. I think I'll stick it out until the next beta in June. Lack of SD card slot use, camera that barely works... It's not pretty.
Beta time-line described here:
https://developer.android.com/preview/overview
I rolled back as well. I have been with Sony phones for twelve years and like the skin and apps also. I do enjoy test driving the new Android version as well but only temporarily.
In order to Flash a Customized UK version & update to Q, I unlocked the bootloader . Guys, do you know a way to lock it back, since Flashtool doesn't support it and also when I try from command lines it gives me command not found. Do I have a chance to restore it back to original state ?
Don't think so. No need to unlock bootloader to flash another regional firmware.
The folder 'c:\ProgramData\SonyMobile\Update Engine\[date]\localstorage\' contains the firmware downloaded by the Xperia Companion stored in *.file ~ 2.3 GB. I extracted and seems to be all the files that FlashTool downloads. Did someone tried to flash Android Q like this ?
Does it have Wifi calling for T-Mobile USA?
daviddem said:
Does it have Wifi calling for T-Mobile USA?
Click to expand...
Click to collapse
I don't know if it's network related or not, I'am on US firmware and Wi-Fi calling feature is missing. On Original firmware the feature was present.
In the first week of having my Note 10 Pro, I was using the global ROM that came with it, and after foricng volte and vowifi on with the dialer codes they were both working, I still have call logs in my phone showing it was working.
But, after the week when I was able to unlock, I unlocked the phone and moved to miui 12 on Xaiomi.eu, and both these functions no longer work, IMS status shows unregistered.
Does anyone know if this is a fault of Xaiomi.eu or the Chinese ROM? I haven't had much time to bother with switching around ROMs as I've had to be using my phone, but if someone already knows this will only work on global I'll probably switch back.
Updated to Xiaomi.eu 20.5.14 and the issue persists.
I am using volte and vowifi on Xiaomi.eu 20.5.14 without any problems.
I didn't change any settings, it was just active when I started the phone first time.
Using provider 3.AT
Maybe not all carrier settings implemented in the ROM.
philipp900 said:
I am using volte and vowifi on Xiaomi.eu 20.5.14 without any problems.
I didn't change any settings, it was just active when I started the phone first time.
Using provider 3.AT
Maybe not all provider settings implemented in the ROM.
Click to expand...
Click to collapse
It's definitely to do with carrier, I'm on Tmo in the US. As I said in global it worked with nothing extra, so I think xiaomi.eu or the China beta is missing some configs or something.
Volte is disabled for some countries.
It should be enabled by
*＃*＃86583＃*＃*
sanoayyk said:
Volte is disabled for some countries.
It should be enabled by
*＃*＃86583＃*＃*
Click to expand...
Click to collapse
I've already done the dialer codes, the build prop edits, checked the APN, tried the PDC tool, nothing works.
Issue is still present on 20.5.21, I think the Chinese beta or xioami.eu might be missing the proper modem configs for tmobile US, haven't been able to test on other ROMs (miroom, revtech, masik, etc), but I might have to stay on global on this phone once global miui 12 comes out :/
Rakuu said:
Issue is still present on 20.5.21, I think the Chinese beta or xioami.eu might be missing the proper modem configs for tmobile US, haven't been able to test on other ROMs (miroom, revtech, masik, etc), but I might have to stay on global on this phone once global miui 12 comes out :/
Click to expand...
Click to collapse
I'm on T-Mobile here in US also and it's not working. I also get a few calls that go straight to voicemail since using EU now. I might try miroom haven't heard of revtech.
Cj719 said:
I'm on T-Mobile here in US also and it's not working. I also get a few calls that go straight to voicemail since using EU now. I might try miroom haven't heard of revtech.
Click to expand...
Click to collapse
I made some progress!
After flashing the firmware from here https://forum.xda-developers.com/mi...rmware-xiaomi-mi-note-10-pro-mi-cc-9-t4096347 after a first boot the wifi calling icon appeared for a split second, but VoLTE was enabled! important to note, volte icon will only show in the status bar with the control panel pulled down (right side panel).
After some testing, I was able to get wifi calling working too, but only in airplane mode. With airplane mode enabled and wifi manually turned on, after a few seconds wifi calling appeared and calls connected, but as soon as I turn off airplane mode wifi calling goes away and it switches to just volte, even starting a wifi call and then disabling airplaneode would convert the call to a volte or regular call, very strange!
If you're going to try this yourself, you can flash any firmware from the eea or global rom, but to avoid breaking your fingerprint scanner, after flashing the firmware and rebooting, make a backup of your modem in TWRP, and then flash the 2.5.14 china ROM firmware back, reboot, and then restore the modem backup. You'll probably still have to re-register your fingerprints, but it's better than nothing!
I've attached some screenshots for proof
About to try this
---------- Post added at 05:35 PM ---------- Previous post was at 04:39 PM ----------
So after I flashed global firmware, I got icon for about 10seconds after a reboot in airplane mode but it wouldn't make a call. My Google messages now allows the rcs chat option though
Cj719 said:
About to try this
---------- Post added at 05:35 PM ---------- Previous post was at 04:39 PM ----------
So after I flashed global firmware, I got icon for about 10seconds after a reboot in airplane mode but it wouldn't make a call. My Google messages now allows the rcs chat option though
Click to expand...
Click to collapse
Do you have volte/VOWiFi force enabled? That's the only thing I can think, volte works with no extra steps whereas VOWiFi only works with airplane mode. I'll try sending you my TWRP modem backup maybe that'll help.
Edit: here's my TWRP backup of my modem https://drive.google.com/file/d/1--fGb80OjIdJpUzkgiKlHhlW9oykjyme/view?usp=drivesdk you'll need to unzip it in /sdcard/TWRP/BACKUPS/<random letters and numbers>/
So I just did a reboot again before doing anything else and it works.
Cj719 said:
So I just did a reboot again before doing anything else and it works.
Click to expand...
Click to collapse
Awesome! Now we just gotta figure out how to get wifi calling consistently working.
Mine was on for about an hour today
Cj719 said:
Mine was on for about an hour today
Click to expand...
Click to collapse
I'm going to make an educated guess based on your signal being very poor in that screenshot; It's possible there's a change in MIUI 12 causing wifi calling to only be enabled in poor or no reception areas, which would line up with me only being able to see it on in airplane mode.
I'll have to figure out some testing for this myself, I suppose this change isn't too illogical, you'd probably only really need it in those cases, just kind of off-putting/misleading that the behavior changed between versions in a way that made it seem broken...
Rakuu said:
I'm going to make an educated guess based on your signal being very poor in that screenshot; It's possible there's a change in MIUI 12 causing wifi calling to only be enabled in poor or no reception areas, which would line up with me only being able to see it on in airplane mode.
I'll have to figure out some testing for this myself, I suppose this change isn't too illogical, you'd probably only really need it in those cases, just kind of off-putting/misleading that the behavior changed between versions in a way that made it seem broken...
Click to expand...
Click to collapse
Let me test that theory, I get poor signal in the basement and great upstairs so let me see if this is indeed the case
Just a little update on this, today my phone started getting some spotty cell reception, and wifi calling turned on! There doesn't seem to be any threshold (i.e. past two bars or less, it turns on), just while the signal is poor it will arbitrarily decide to turn it on. Some undocumented miui 12 feature I'm guessing, since it didn't act this way on the stock miui 11 ROM the phone came with.
Also something maybe interesting of note, I was curious and connected the phone to the PDC tool and it said I was on a T-Mobile modem, as would be expected I suppose, it's just strange why the stock xiaomi.eu modem will not show this modem option even when manually imported to PDC.
On a slightly related note, I put my sim back in my Mi Max 3 running miui 11 still, which previously only had volte available, I tried the same process as what I did on my note 10, I flashed the firmware from the global and EU ROM to see if wifi calling would become available but no dice, so it seems this solution isn't fullproof for all devices just ours.
sanoayyk said:
Volte is disabled for some countries.
It should be enabled by
*＃*＃86583＃*＃*
Click to expand...
Click to collapse
I saw only this code
This is for WiFi calling
*#*#869434#*#*
I disabled using *#*#869434#*#*
After that I could go to my sim card and enable it, and choose if I prefer wifi or mobile network.
These options have not been availble if i enable using *#*#869434#*#*
hello guys i put the xiaomi.eu rom on my 10 with the android 11 global rom and MIUI 12.2.0.6 i had the icon voLTE ene call log marked me call HD or want to know if a bug because I don't see plus the voLTE icon in the status bar and neither the HD and voLTE icon on the call log