Related
So I bought the HTC Once E8 from Etotalk, which came with all the Chinese apps removed and the Google Play store added. I went to the ATT store to get a nano sim, and calls and texts work just fine. My issue is with the data connection. I have done a lot of google fu, and have tried the same settings that people are using for UK M8's but am still having issues. From my understanding the bands are supported, so It should just be a configuration issue.
Would anybody be able to shed some light on this for me? This is my first overseas phone, and I have only had experience with vanilla Android installs to date.
Also, the first thing I did was install the software update from HTC, which probably wasn't the smartest move. I don't see how this would affect APN settings though....
Let me know if any other info is needed, thanks in advance for any help!!
ethansc said:
So I bought the HTC Once E8 from Etotalk, which came with all the Chinese apps removed and the Google Play store added. I went to the ATT store to get a nano sim, and calls and texts work just fine. My issue is with the data connection. I have done a lot of google fu, and have tried the same settings that people are using for UK M8's but am still having issues. From my understanding the bands are supported, so It should just be a configuration issue.
Would anybody be able to shed some light on this for me? This is my first overseas phone, and I have only had experience with vanilla Android installs to date.
Also, the first thing I did was install the software update from HTC, which probably wasn't the smartest move. I don't see how this would affect APN settings though....
Let me know if any other info is needed, thanks in advance for any help!!
Click to expand...
Click to collapse
You probably lost the etotalk modrom while updating, but that shouldn't be a big deal. Though it may have overwritten the predefined APN settings?
Did you manualy check your APN settings under settings --> mobile data --> sim1 --> access point names?
matthijsph said:
You probably lost the etotalk modrom while updating, but that shouldn't be a big deal. Though it may have overwritten the predefined APN settings?
Did you manualy check your APN settings under settings --> mobile data --> sim1 --> access point names?
Click to expand...
Click to collapse
Yeah that's what I think happened, is that I lost the modrom. I wouldnt think that would affect the APN though, isn't that supposed to be unique to each country, or something of the sort? I will send Etotalk a message and ask them if there's a chance that could be it anyways.
I have indeed tried keying it in manually, trying every combination from default, to the one I got from the ATT rep, to the ones I have found online from different forums.
Fixed
I tried using the legacy cingular APN. Apparently my grandfathered unlimited data plan was on these old codes, ie. 3G only...
Thanks anyways.
Does anyone knows where to set the default SIM for sending SMS in HTC U11?
I am trying to use Android Messages but I can't until the default SIM is set.
When searching for solutions, it seems the way to set is via SIM Management in Settings, but our HTC U11 doesn't have this menu in Settings.
desean said:
Does anyone knows where to set the default SIM for sending SMS in HTC U11?
I am trying to use Android Messages but I can't until the default SIM is set.
When searching for solutions, it seems the way to set is via SIM Management in Settings, but our HTC U11 doesn't have this menu in Settings.
Click to expand...
Click to collapse
I am having the same issue on a new HTC U11+.
I will ask over in that forum as well.
I get the same problems, all the suggestion said that i need go to sim management, in this case is dual network manager.
But in dual network manager, there are only choose sim 1 or sim 2 and preferred data network, none option for sms
Same thing, looks like I can send sms from main app tho. Google messenger has same problem as stated here.
Just go to settings, search for "SIM" there will be 2 options "SIM cards" or "Preferred SIM for" choose either it will take you to SIM cards menu, underneath it will say preferred SIM for Cellular data, Calls, SMS messages, click on SMS messages and choose a SIM you will send SMS from. That is it, you can now go through Google messages setup and use it.
Sent from my HTC U11 using Tapatalk
Sorry but my sim card menu do not have any option for call and sms. I using android 8 and this issus does not happen with htc mess app
Huntervn said:
Sorry but my sim card menu do not have any option for call and sms. I using android 8 and this issus does not happen with htc mess app
Click to expand...
Click to collapse
Please follow my instructions, look at the attached screenshot to guide you. Let me know.
What you posted is not SIM CARDS option, but Dual Network Manager, different things.
Thanks for your suggestion, however i search sim, only sim tool kit like att photo
Huntervn said:
Thanks for your suggestion, however i search sim, only sim tool kit like att photo
Click to expand...
Click to collapse
I wonder if it is firmware specific, I'm running UAE firmware with CID J15, also running 7.1.1 .
Yes, it seems that in android 8.0, htc chnaged it
Huntervn said:
Thanks for your suggestion, however i search sim, only sim tool kit like att photo
Click to expand...
Click to collapse
Agree. No option for this on U11+ either.
Having the same issue.
Looks like the performance problems for Google messages have been fixed and now we have this
Ok, I have found the setting in U11 Oreo via create widget > Activity > Setting > Sim card (see attached screenshot)
However, it is not possible to select preferred Sim card which suggest to me HTC have deliberately disabled this feature in favour of their in-app solution.
desean said:
Ok, I have found the setting in U11 Oreo via create widget > Activity > Setting > Sim card (see attached screenshot)
However, it is not possible to select preferred Sim card which suggest to me HTC have deliberately disabled this feature in favour of their in-app solution.
Click to expand...
Click to collapse
As far as I know (Android) Google Messages has never been intended for use on dual SIM devices, as Google only produces single SOM devices. This all manufacturers of dual SIM smartphones habe to develop an inbuild solution to go with. No intention by HTC actually.
Sent from my HTC U11 using XDA Labs
5m4r7ph0n36uru said:
As far as I know (Android) Google Messages has never been intended for use on dual SIM devices, as Google only produces single SOM devices. This all manufacturers of dual SIM smartphones habe to develop an inbuild solution to go with. No intention by HTC actually.
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
Dude to android one devices, it looks like Google is adding support for dual SIM, Xiaomi Mi A1 is dual SIM device with android one.
Sent from my HTC U11 using Tapatalk
hmsq said:
Dude to android one devices, it looks like Google is adding support for dual SIM, Xiaomi Mi A1 is dual SIM device with android one.
Click to expand...
Click to collapse
Yes but not to the App as such but a service it seems. Thus it ain't present on any non Google ROM, such as an OEM ROM.
Sent from my HTC U11 using XDA Labs
5m4r7ph0n36uru said:
As far as I know (Android) Google Messages has never been intended for use on dual SIM devices, as Google only produces single SOM devices. This all manufacturers of dual SIM smartphones habe to develop an inbuild solution to go with. No intention by HTC actually.
Click to expand...
Click to collapse
I have a LG G6 Dual sim (Android 7.0) and I have no problem using Google messenger app. I also have the HTC U11+ (Android 8.0) which has the Google messenger dual sim issue.
From adb run the following:
adb shell settings put global multi_sim_sms 1
Source:
https://twitter.com/swashta/status/953226414676901889
Electronic Punk said:
From adb run the following:
adb shell settings put global multi_sim_sms 1
Source:
https://twitter.com/swashta/status/953226414676901889
Click to expand...
Click to collapse
Thanks. I confirm this works.
To get current value: adb shell settings get global multi_sim_sms
Setting SIM 1 as preferred SIM: adb shell settings put global multi_sim_sms 1
Note: default value is "null"
I don't understand , so what should we do?
Thanks
Activate Project Fi account from an unsupported device (Successfully Accomplished)
**Although I accomplished this on a OP5T, there is no reason why the steps below should not work on just about any other Android device that is GSM based and capable accessing T-Mobile towers for cell service. The Fi app controls the whole procedure, it is what activates everything as well as sets the proper settings for MMS and VVM. As long as the Fi app believes the device it's installed on is one of the officially supported Fi devices then it will proceed with the activation of a new sim card**
Project Fi is (in my opinion) the best mobile provider in the US at the moment. It has great service, a radical approach to data costs which no other carrier offers at the moment (you pay exactly for what you use, nothing more nothing less), an unlimited everything plan for $80 but only if you consume 6GB+ of data in a bill cycle. If the next moth you only use 2GB of data then your bill is $40 (so you don't have to pay 80 every month just to have peace of mind. All data is charged at $10 per gig. Anything after 6GB of data in a bill cycle is free. The most you'll ever be charged in a particular month is $80 (20 for unli talk and text, 60 for 6GB of data if youve used that much). You also get access to data only sims which you can use in any other GSM devices and share the data attached to your account. Tethering is free and unlimited as well. I mean you can't beat it. However its only officially supported on 5 devices total and while you can start service and order a sim which can work in other GSM T-Mobile compatible devices, you must first activate the sim card inside an official device in order for your service to begin. Most people don't have one of those devices but they might want to use the service still. Well here's how you can....
I've been experimenting with activating service on a phone that's not officially supported and I am here to tell you that I've successfully managed to do so using a OnePlus 5T which is not an officially supported Fi device. The process was insanely simple and I've actually wondered from day one whether or not the process I accomplished this with would work, but I figured it was too simple for Google to not have considered and so I never attempted it. This was literally the final attempt I was going to make on this and it worked flawlessly.
STEP 1
Root your phone, go /system and edit the build.prop.... (/system means the "system" folder in the root partition, known as "/")
Change the following entries to what I have indicated, (you're only editing the words after the "=" sign)
Each entry below will say something different following the "=" sign depending on which phone you happen to be using... Everything to the left of the "=" sign should be universal across all Android devices...
So if you have a OnePlus 5 for example, then you will initially see "ro.product.model=OnePlus 5" and "ro.product.name=cheeseburger" you'll only change "OnePlus 5" and "cheeseburger" to match what I have written below....
***THESE OPTIONS ARE CASE SENSITIVE!! SO IF YOU WRITE "Taimen" INSTEAD OF "taimen" THEN IT WILL NOT WORK***
ro.product.model=Pixel 2 XL
ro.product.brand=Google
ro.product.name=taimen
ro.product.device=taimen
ro.product.manufacturer=Google
ro.build.product=taimen
ADD THE FOLLOWING ENTRY TO THE BOTTOM OF YOUR BUILD.PROP (the complete line, not just "true")
ro.opa.eligible_device=true
STEP 2
Save the new options added to build.prop and REBOOT YOUR PHONE BEFORE PROCEEDING! If you did everything correctly, then after a reboot when you go to "system" and then "about" you should see the device info reporting that your phone is a "Pixel 2 XL". This is how we are managing the activation, because the Project Fi app will check the device info when you open it the first time and based on the info it sees, it will either treat the phone as an official device, or one that's using a data only sim (which can not activate Project Fi account). Data only devices are restricted in that LTE speeds are reduced substantially, VVM does not work, it's possible to call and text with a few tweaks but MMS will not work outside of the Hangouts app. Official devices have no restrictions. As long as it believes the device is official, it will allow the activation to proceed regardless of the device you're using.
STEP 3
(For the next part:
DO NOT GRANT PERMISSIONS TO PROJECT FI APP UNTIL AFTER YOU'VE OPENED THE APP AND ACTIVATED THE SERVICE!! Upon completing this task you can then grant the necessary permissions to Project Fi app. If you have already granted permissions then clear app data for Project Fi app, uninstall, reinstall and follow my directions)
Download "Project Fi" app and insert the sim you ordered from Google. Open Fi app and choose the correct account (if theres more than one google account signed in on your device) and if you've done everything correctly then the service will activate. I've done this successfully on 3 different devices already.
Once you've completed this you can then revert all changes to the build.prop back to original settings and your account will be activated and the sim can be used in any GSM device compatible with T-Mobile's network from then on.
FYI:
If you want to be able to send mms messages from any text app besides Hangouts and have visual voicemail working as well then you should leave the build.prop the way it is after adding in the Pixel info. All services (except for network transitioning, you'll be limited to T-Mobiles service which is amazing in most areas anyway) will function properly when the device is seen as being a Pixel 2 XL. If you revert the build.prop back to stock following the initial activation of your sim card the you will lose visual vm, mms messaging (except if you don't mind using hangouts for text and mms), you'll have to add the correct apn info, and you'll only get LTE speeds of about 10 Mbps. Leave it the way you changed it to for activation and the phone will function exactly as it does on supported devices with the ability to mms from any text app, working visual vm and the APN will configure itself and your LTE speeds will improve substantially. I hit 60 Mbps consistently. There's an easy way to tell. If your carrier label states "Project Fi" then the build.prop is showing the phone as a device thats not officially supported and you'll have to deal with the extra issues I've stated above. If the carrier label reads "Fi Network" then you phone is seen as a supported device and everything will work perfectly with the exception of seamless network transitioning.
Hope this helps some people out!
not work on op3t. any ideas? i had to add in some of these lines as they didnt exist. project fi app crashes. mms problems
After I completed the above steps, my LG V30 boots to fastboot and won't go any further. Reboot and back to fastboot. Have to restore from backup before I can get back to the OS.
Any ideas why this might be happening?
I called an AT&T store near me (Orange, CA) and I was told they had the new blue sim card pack with the QR code and I could come in today to transfer my number to the esim from the physical...will go tomw morning to see if they know what they're talking about but in the meantime has anyone else tried it on the pixels? If so, how do I open Google's eSim manager app? It says in the play store that I have it installed but I don't see it on the phone..
In "Settings > Network & Internet > Mobile Network > Carrier" there is an "Add Carrier" option which lets you scan the QR code. I think that's what you're looking for.
I visited our local ATT store yesterday afternoon. Needed a new sim so I could get wifi calling to activate (previous sim was at least 2yrs old). I asked about using an eSim and the rep told me they had the "cards" in the back but had received instructions from ATT that they weren't supposed to be using them until further notice..... Not sure if he was just blowing smoke or not. I suppose it's also possible that eSim isn't fully operational up here in Alaska, although I wouldn't know if or why that would be. He said everything was ready, they were just waiting for word from the office to start using them.
On a plus note, wifi calling was working out of the box, once I had a more recent sim.
Hi,
I'm wondering if anyone else has this issue. In my Pixel 3, there are 2 SIMs. The eSIM used for Google Fi and a physical SIM used for RedPocket (on Verizon). The Verizon # is my main # currently, so I normally have Fi disabled (not the service itself but by keeping the Verizon sim as default in my phone). Today, I wanted to check and delete voice messages in my Fi #, so I switched Carrier to Fi in my phone. It seemingly switched just fine, and my About Phone section shows the Fi #. However, if I try to dial my voicemail or any other numbers, it goes straight to Verizon customer support. I'm not sure what's going on. I thought Pixel 3 was supposed to be able to switch between SIMs smoothly.
goldentequila said:
Hi,
I'm wondering if anyone else has this issue. In my Pixel 3, there are 2 SIMs. The eSIM used for Google Fi and a physical SIM used for RedPocket (on Verizon). The Verizon # is my main # currently, so I normally have Fi disabled (not the service itself but by keeping the Verizon sim as default in my phone). Today, I wanted to check and delete voice messages in my Fi #, so I switched Carrier to Fi in my phone. It seemingly switched just fine, and my About Phone section shows the Fi #. However, if I try to dial my voicemail or any other numbers, it goes straight to Verizon customer support. I'm not sure what's going on. I thought Pixel 3 was supposed to be able to switch between SIMs smoothly.
Click to expand...
Click to collapse
I think I know what's going on, I've seen this happening.
This problem seems to arise if you just switch to the Fi eSIM without letting the app know. There's stuff that needs to be updated in Google Fi's backend that goes beyond a SIM switch. What you want to do if you want to switch to Fi from physical SIM is go to the Fi app and tap on activate. This will do a proper switch and calls will go through normally. To go back to physical SIM you can just tap on it.
bartolo5 said:
I think I know what's going on, I've seen this happening.
This problem seems to arise if you just switch to the Fi eSIM without letting the app know. There's stuff that needs to be updated in Google Fi's backend that goes beyond a SIM switch. What you want to do if you want to switch to Fi from physical SIM is go to the Fi app and tap on activate. This will do a proper switch and calls will go through normally. To go back to physical SIM you can just tap on it.
Click to expand...
Click to collapse
You were totally right. I just tested your theory and worked perfectly. It is so dumb for Google to make sim switch so painful. Defeats the purpose of having dual sim capability... Thanks for your help!