Remote Wipe Vulnerability - Motorola Droid 3

Hi Guys, the browser hack that wipes Samsung phones is not limited to just those handsets. These guys do a better job of describing the whole thing:
http://www.theverge.com/2012/9/26/3412432/samsung-touchwiz-remote-wipe-vulnerability-android-dialer
Here is a direct link to the exploit test:
http://dylanreeve.com/phone.php
I'm running MavRom4 with the China telco radio image and my device is vulnerable. Just wanted to share the info so people are aware; having two dialers and no default will force the exploit to ask you to actively pick a dialer; this would neutralize most cases but that is a pretty annoying work around.
Maybe people can post D3 Roms that aren't vulnerable.

majatt said:
I'm running MavRom4 with the China telco radio image and my device is vulnerable. Just wanted to share the info so people are aware; having two dialers and no default will force the exploit to ask you to actively pick a dialer; this would neutralize most cases but that is a pretty annoying work around.
Click to expand...
Click to collapse
Also, installing DialerOne and making it the default will protect you as well - you do not have to leave it without a default dialer set. DialerOne is actually a good dialer - I used to use it with my Droid Eris with CyanogenMod ROMs, in order to have the dial by name function that the Sense dialer supported back. And you can still leave the stock dialer set in a home page or on the launcher dock - it will still work if you call it up. It will not be called up if you launch the dialer from another app, though, if you make DialerOne the default.
The stock dialer is vulnerable - a predictable result, based on the vulnerability of MavRom, but I did want to say that I tested it. I haven't tested any other ROM - at this point, I don't have much time to try some out, and I think I recently deleted my most recent Liberty and Bionic Nandroid backups.
Let's see how long before Moto releases a critical patch update for stock.

Thanks, this is good to know. I thought it was only Samsung phones that had the issue, but since I'm still on stock 2.3.4 it appears I'm vulnerable. I have GrooveIP Lite installed on my phone, an app that allows you to make voice calls with using your Google Voice number. With this app installed I get a complete action using Dialer or GrooveIP window so I should be safe if I get a random popup Ill be sure to not select Dialer.

I heard about this "wipe" problem and when I saw it was just passing dialer codes to the fone I knew it would affect more than just Samsung.
Does anyone know if they have a list started of fones that might be vulnerable?

I read somewhere (though haven't tested it...) that the D3 does not have a dialer code that resets the phone, as the Samsung phones do/did. So, the D3 fails the display the IMEI test, but I believe that the reset code does not work with the D3.

FYI: CM10 kexec isn't vulnerable. Probably b/c it's JB (I think they fixed the vulnerability in JB). I go to the site and dialer pops up w/ *#06# No IMEI displayed
Sent from my AOKP JB GT-P3113 using Tapatalk

Related

App Requires Phone Number work around

I tried to install the verizon fios dvr manager/remote control - the application however requires a cell phone number - does any one know a work around to create a "fake number" on the nook to use these apps?
Thank you
xtrezpasor said:
I tried to install the verizon fios dvr manager/remote control - the application however requires a cell phone number - does any one know a work around to create a "fake number" on the nook to use these apps?
Thank you
Click to expand...
Click to collapse
I would also like to get something like this working for Google Voice so that I can use the messaging service.
Any and all help is appreciated.
I signed into my google account and google voice "just worked". Of course i can't make any calls but i can use it to send texts and receive texts sent to my gv number.
Sent from my LogicPD Zoom2 using XDA App
I think if you could lift the data/configuration from your existing phone then you could copy that to the Nook and be working. I could not find where the data was stored though for the app.
GarJones27 said:
I would also like to get something like this working for Google Voice so that I can use the messaging service.
Any and all help is appreciated.
Click to expand...
Click to collapse
I just entered my iPhone's number (which is already registered to Google Voice and has the Google Voice app on it) and I can use it for texting just fine.
KitF said:
I just entered my iPhone's number (which is already registered to Google Voice and has the Google Voice app on it) and I can use it for texting just fine.
Click to expand...
Click to collapse
Can you give a short tutorial on how to get this set up? I too (and im sure others) would like to be able to text from the Nook.
Sent from my HERO200 using XDA App
Setup gvoice on a phone first (you should able to find a tutorial by searching google). Then use the same # when setting up on the nook.
seeddemon said:
Setup gvoice on a phone first (you should able to find a tutorial by searching google). Then use the same # when setting up on the nook.
Click to expand...
Click to collapse
Edit: Okay, set up Google voice and I'm able to send texts using that number however the apps that require a phone number do not see it. Not a huge deal, but there might be more apps out there that require a phone number to work.
I simply set up Google voice via the Google.com/voice website. And then got a Google number to use for texts. In the voice app you can compose a message and my Google contacts are available.
Sent from my Nook Color.
This isnt what what I was looking for - I was looking for a way to use verizon Fios manager...
hijacked
I agree this thread was hijacked. We want a workaround for the Android verizon manager on the kindle fire or nook color where the app was meant for a mobile phone. Would there be a way to give a rooted device a phone number?
3EyedPhish said:
I agree this thread was hijacked. We want a workaround for the Android verizon manager on the kindle fire or nook color where the app was meant for a mobile phone. Would there be a way to give a rooted device a phone number?
Click to expand...
Click to collapse
Depending on the ROM your running, you may be able to enter a phone number in the settings.... otherwise you may be able to edit TelephonyManager.smali and find the section to pull the phone number and hard code a phone number in the same way we do IMEI edits.
DizzyDen said:
Depending on the ROM your running, you may be able to enter a phone number in the settings.... otherwise you may be able to edit TelephonyManager.smali and find the section to pull the phone number and hard code a phone number in the same way we do IMEI edits.
Click to expand...
Click to collapse
I got the FIOS app to run on my Nook by doing the reverse of this. I found the few places in the app where the phone number was looked up and replaced those by calls to get an apps prefs setting "Display Name" which is entered during set up but unused by the app. So I put in the phone number under Display Name during set up.
This was done using apktool to patch the app but I am reluctant to post the modified version as this is explicitly ruled out by license agreement.
I did consider going the TelephonyManager route but as I am using CM9 which is still changing quite a bit then that becomes a moving target. If CM9 puts explicit coded support in for entering a number like CM7 did then that would be the best option. I did find, however, when using the CM7 option that it had a tendency to lose the entered number during reboots.
You can set a phone number, IMEI, location and many other things for each individual app with PDroid without modifying any code on those apps.
All you need is to enable the PDroid framework. There are packages in Botbrew for Nook or you can use the auto-patcher if you have Linux.
The above links are for CM9. If you have cm7 there are auto-patchers for Linux and windows, which can be found at the PDroid thread.
mateorod said:
You can set a phone number, IMEI, location and many other things for each individual app with PDroid without modifying any code on those apps.
All you need is to enable the PDroid framework. There are packages in Botbrew for Nook or you can use the auto-patcher if you have Linux.
The above links are for CM9. If you have cm7 there are auto-patchers for Linux and windows, which can be found at the PDroid thread.
Click to expand...
Click to collapse
That looks like a better more general method. In checking this out I also notice that Verizon did do an update a couple of weeks ago where the FIOS remote app claims it has a new pairing method which works with non-phone tablets so maybe this isn't needed any more for this particular app. I'll try that out.
It is a pretty neat program, with a ton of functions and uses that go pretty unnoticed.
One note, though: due to an update in the CM repo, our auto-patcher ( and even the patches I used to make the auto-patcher) broke.
I have updated everything for CM9, but we are waiting on an aokp build before releasing another version of the auto-patcher.
But the Botbrew packages are up to date and can be used immediately for 5/08 and the patcher will be updated soon.
If you are running an older build, make sure the package you use matches the build date. And the auto-patcher still works to builds from 5/06 and earlier.
bobtidey said:
In checking this out I also notice that Verizon did do an update a couple of weeks ago where the FIOS remote app claims it has a new pairing method which works with non-phone tablets so maybe this isn't needed any more for this particular app. I'll try that out.
Click to expand...
Click to collapse
I tried out the new version of the Verizon app and it now does allow use of a 4 digit PIN as opposed to a phone number for setting up the remote control pairing. It finds the set top box OK but then immediately crashes on the Nook Color CM9.
I'm going to do a bit more investigation and maybe try it from a Touchpad to see if that behaves the same way.

[Q] Change CM10.1 to work in Tablet mode

Just recently pulled my old DS7 out of the corner and after seeing, nvflashed this really great Unofficial CM10.1 for Dell Streak 7 ROM on it. Works great, apart from the one tiny problem - it thinks it's a phone ... I already used Uninstall Master to remove some Phone features, such as: SIM Toolkit(it's called Mobile Data i think?), Messaging and Mobile Network Configurator. Was wondering how or where can I change or modify the settings related to how the Cyanogenmod acts as a Phone or a Tablet so that many apps from Play Store wouldn't default to the portrait mode.
On a sidenote - thanks to giveen and anyone involved in making this really awesome CM port to DS7 :good:
karlis1989 said:
Just recently pulled my old DS7 out of the corner and after seeing, nvflashed this really great Unofficial CM10.1 for Dell Streak 7 ROM on it. Works great, apart from the one tiny problem - it thinks it's a phone ... I already used Uninstall Master to remove some Phone features, such as: SIM Toolkit(it's called Mobile Data i think?), Messaging and Mobile Network Configurator. Was wondering how or where can I change or modify the settings related to how the Cyanogenmod acts as a Phone or a Tablet so that many apps from Play Store wouldn't default to the portrait mode.
On a sidenote - thanks to giveen and anyone involved in making this really awesome CM port to DS7 :good:
Click to expand...
Click to collapse
The reason why it is that way is because there are 4G models of the DS7
giveen said:
The reason why it is that way is because there are 4G models of the DS7
Click to expand...
Click to collapse
Understandable, but since I have a Wi-Fi only version I wanted to know if It's possible to change this in form of a setting or a few lines inside a configuration file without involving compiling. I even faintly remember stumbling upon something like this on a CM9 version I had on my old Xperia MT15i Neo ... if only I could remember or find where or how (currently strolling through the developer and CM10 related menus) - deleted my Xperia related bookmarks when I sold it.
p.s. - people mentioned some problems with the on-screen keyboard disappearing as described in one of the posts on the main CM10.1 thread, I've noticed them myself too and they tend to be application specific ... it feels like the keyboard crashes or force-closes due to not enough memory, like in lighter applications the keyboard works fine, but when trying to use the keyboard for writing for example a post in the comments section in a website will most likely result in keyboard disappearing after first input character.
So I am still trying to figure out why you started a new thread about this and what your question is.
To remove mobile data completely requires a new compile, something that cannot be done right now for a variety of reasons.
I guess I simply went too far off topic while trying to explain why I'm writing here... sorry.
So, to clear things up, the question still remains the same - what can I do to make it act more like a tablet and less like a phone on my Wi-Fi only DS7. So what I'm trying to find in the developer and CM menus is if I can more or less simply switch between some sort of "phone" and "tablet" mode so that some applications from Play store wouldn't default to portrait view mode.
And I noted that I've already uninstalled/disabled (call it how you want - I can restore them from the Unnstallers Recycle Bin if something weird starts to occur) some of the system .apks and as You already pointed out:
To remove mobile data completely requires a new compile, something that cannot be done right now for a variety of reasons.
Click to expand...
Click to collapse
... so thanks for clarifying that and no need to do any special versions - it's just fine how it is now. I didn't come here to request anything to be compiled or modified for me but just to ask for info, heck, I wasn't even expecting You to be answering on this thread.
karlis1989 said:
I guess I simply went too far off topic while trying to explain why I'm writing here... sorry.
So, to clear things up, the question still remains the same - what can I do to make it act more like a tablet and less like a phone on my Wi-Fi only DS7. So what I'm trying to find in the developer and CM menus is if I can more or less simply switch between some sort of "phone" and "tablet" mode so that some applications from Play store wouldn't default to portrait view mode.
And I noted that I've already uninstalled/disabled (call it how you want - I can restore them from the Unnstallers Recycle Bin if something weird starts to occur) some of the system .apks and as You already pointed out: ... so thanks for clarifying that and no need to do any special versions - it's just fine how it is now. I didn't come here to request anything to be compiled or modified for me but just to ask for info, heck, I wasn't even expecting You to be answering on this thread.
Click to expand...
Click to collapse
I make it my special concern to answer questions, even if it with sarcasm
I'm not sure what more you can do besides deleting the phone. Comment out in build.prop the rild stuff
I wonder if he is referring to TabUI? Which I as well am trying to relocate the flash able .zip which enabled this display difference. I have been running cm10.1 2/12 because of the sensors not working on the 2/14 build.
Sorry to piggyback the thread, but is there an answer for where the tab ui .zip is for the 2/12 build?
Sent from my Galaxy Nexus using xda premium

Assist is broken, help?

Soooo...
I was messing around with getting text secure to get working with Motorola Assist. From what I remember, I froze Messaging at one point while simultaneously making text secure a system app. Long story short, I broke the function where it talks to you when a text comes in. It still works with active screen and the Bluetooth in my car. It also still works with incoming calls for some reason. Wiping, reloading both the messaging apk and Motorola assist and its framework did not work. I'm looking at databases right now and I noticed it has a different status number and such compared to the other functions. I'm going to play with it to see what I can do, but is there anyway I can get a copy of the database from someone in the community? The database I was looking for was in data/data/com.motorola.contextualsmartrules2/databases/assist.db.....I want to compare the two to see what's different. I would also be open to someone else's titanium backup of Assist and its framework. I have a Verizon Dev Edition. I don't think the individual carriers matter since the databases don't reference the carrier. Unless someone else has a better idea? Thank you in advance for your comment/support.
P.S. I could technically just install my ROM fresh and restore everything but I got ALOT of customizations as well as Google Authenticator and I'd like to keep the ROM as is if I can't help it. I should've backed up before messing with it I know....
Sent from my BOOSTO! Moto X
ovismos said:
Soooo...
I was messing around with getting text secure to get working with Motorola Assist. From what I remember, I froze Messaging at one point while simultaneously making text secure a system app. Long story short, I broke the function where it talks to you when a text comes in. It still works with active screen and the Bluetooth in my car. It also still works with incoming calls for some reason. Wiping, reloading both the messaging apk and Motorola assist and its framework did not work. I'm looking at databases right now and I noticed it has a different status number and such compared to the other functions. I'm going to play with it to see what I can do, but is there anyway I can get a copy of the database from someone in the community? The database I was looking for was in data/data/com.motorola.contextualsmartrules2/databases/assist.db.....I want to compare the two to see what's different. I would also be open to someone else's titanium backup of Assist and its framework. I have a Verizon Dev Edition. I don't think the individual carriers matter since the databases don't reference the carrier. Unless someone else has a better idea? Thank you in advance for your comment/support.
P.S. I could technically just install my ROM fresh and restore everything but I got ALOT of customizations as well as Google Authenticator and I'd like to keep the ROM as is if I can't help it. I should've backed up before messing with it I know....
Sent from my BOOSTO! Moto X
Click to expand...
Click to collapse
This is the very thing custom recovery is for!!
Making a backup before you mess around. Not a big deal, no ROM flash nor Rsd firmware
aviwdoowks said:
This is the very thing custom recovery is for!!
Making a backup before you mess around. Not a big deal, no ROM flash nor Rsd firmware
Click to expand...
Click to collapse
I just wish I had the foresight to do that before I started messing with the messaging -_-'
I got a copy of the database I'm messing with in another location as well. So I just overwrite if necessary. What I noticed in some of the tables is that the other actions including hanashi, have status values of 1 or 2. The one that does the one for home has a 5. I've tried changing it to 1 or 2 and haven't gotten anywhere. My understanding of SQL or databases in general is spotty at best. But if I had to describe it, Assist isn't "seeing" the notifications from the stock SMS app anymore since it was frosted/defrosted/moved as user app. I'm not sure what kind of things that would break considering from what I've seen, it doesn't really. Also considering that SMS works in all other applications, I'm thinking it has to be Assist.
But I'm just an idiot with Google at this point, so who knows :laugh:
EDIT: Hanashi not Hamachi.
Update:
5 in the table means it's on.
2 means it's on, but not active
1 means it's disabled.
So according to the database, it should be on. Which technically, I suppose that's right since I see the Home icon up top. What's odd is that it's intent actions are different from the others as well. Referencing something with android.media intent. I'm wondering if I'm looking in the wrong spot...
Update 2:
After figuring out that the table I was looking is just for the intent and the activation of Motorola Assist, I decided that I would try Motorola support.
Telling them what I already did, the only other course they mentioned was wiping the cache partition....or resetting the device.
I'll be kicking myself if that's all it is (wiping cache partition). Won't know till I'm home later today.
Update 3:
No....no it does not work still. Ugh. I don't suppose anyone would wanna Titanium backup their Assist and Assist Framework and send me a link? Possibly their Messaging app too? If not I'll probably just have to bite the bullet and re-do everything.
Sent from my BOOSTO! Moto X

Haw can I use Chroma Dialer on Stock 5.1.1?

I have used Chroma in the past with minimal issues, but prefer the pure stock over a rom - so my question is; is there any way to use the Chroma Rom Dialer on the stock 5.1.1? (since I know there's several telephony, dialer, phonesky apps/files) I am not sure how I would go about doing that, or what all I would need to change in order to pull it off - if this is even possible at all?
Reason for my question, I like that it has BUILT IN native call blocking ability that the stock dialer doesn't, other than THAT feature it's identical to the stock dialer. I don't care if it's the Chroma dialer, or another rom dialer, I just want the STOCK dialer (or stock-like) to have this ability.
I know there's 3rd party apps for this type of thing, and I've used many of them, but I very much so prefer NOT to have to use a 3rd party app for something that (IMO) should have been built in to begin with.
If you wish to know why this is important to me, read the spoiler:
So, I get ~3-6 calls every day that's just the same BS; Scam calls saying I can lower my CC interest rates and to press 1 to speak to a representative. They always call from a different number, so blocking them individually doesn't work since it's never the same twice (typically - you'll understand after reading below). If you DO press 1 you get a rude person who will cuss at you, call you names, or laugh at you if you ask to be removed from their calling list. Doing that will only make it worse. I've recorded dozens of calls where they say really effed up things to me. Beyond harassment, it's straight up abuse.
I have been getting them for years, I DO NOT own a credit card, never have owned one, and have never even applied for one - plus there's THOUSANDS of pages on Google about these type of calls being a major problem. Even the FCC has a $50,000 bounty for anyone who can legally or illegally stop them - no questions asked (how badass is that!?) - THAT should tell you how hard they are to catch, find, or stop.
After more than 2 years of filing formal complaints/reports with the FCC, Local PD, FBI (as told to by the FCC), USCC, and have seeked legal advice from my lawyer as to getting this stopped via getting a subpoena so uscc has to release the real call origin trace, I'm on the Do Not Call list... - I've been met with ONE solution that has been common on all counts; change my number. That's not really an option, I've had this number since 1997, I'm not about to change it for obvious reasons.
Now, I've tried many apps to get this stopped, ranging from free to paid, and have not found one that ACTUALLY works toward getting it stopped, many are difficult to use or require WAY too much effort and personal information in order to do anything but ask you to donate.
So far I have logged (through Google Voice VM) a growing total of 566 *different* numbers they have called me from - from all over the US and some that are unused anywhere on earth.
In conclusion, Ive logged 566 different numbers that have called me a total of 11,925 times since 2008.
If that isn't justification for this request, then IDK what is. Shy of ditching my phone altogether, I'm out of ideas.
Bumping - I'd really appreciate any help, gents.
iRub1Out said:
Bumping - I'd really appreciate any help, gents.
Click to expand...
Click to collapse
Have no idea. If dialer would work would need boh contacts and dialer apk. Have no idea where the code for that mod is and if ASOP dialer will even work on stock. Then you have odex vs deodex to work through.
If it CANT work on stock (which, honestly, I didn't expect it to) given, as you said, the differences are small on the surface but in the actual build they're very different. I understand that, and those are things I considered leading me to wonder.
Can anyone MAKE the stock dialer with that mod added in, or a otherwise stock rom with that?
It seems like a lot to request, I know, but I've been looking for this for months, I've even set up a bounty in a thread on TUSCC, its something that I've really hoped would become a mod thru xposed or "Pure Shamu" rom with it. However, it seems that others don't experience this ridiculous problem, leading to it not being as popular as I wish it was.
Trying to stop an ex from calling is one thing, but trying to stop every call that isn't a contact, I realize that's quite another. Thus is my case, its crazy how many spoofed numbers they use. I'm more amazed that the carrier hasn't done something than I am that it's not a mod. There's tens of thousands of people with this problem and the one solution that requires no effort on the end user isn't available to cell phone users.
I don't know - I'm just at my wits end with these calls. I'd be happy to do it myself if a dev is willing to give me some direction, or ideas to try out.
As a side note, I've recorded several where I just screw with them for as long as I can - then put it on YT after they realize they've been trolled and blow up. It's a small, yet, satisfying "middle finger" I can do.
iRub1Out said:
If it CANT work on stock (which, honestly, I didn't expect it to) given, as you said, the differences are small on the surface but in the actual build they're very different. I understand that, and those are things I considered leading me to wonder.
Can anyone MAKE the stock dialer with that mod added in, or a otherwise stock rom with that?
It seems like a lot to request, I know, but I've been looking for this for months, I've even set up a bounty in a thread on TUSCC, its something that I've really hoped would become a mod thru xposed or "Pure Shamu" rom with it. However, it seems that others don't experience this ridiculous problem, leading to it not being as popular as I wish it was.
Trying to stop an ex from calling is one thing, but trying to stop every call that isn't a contact, I realize that's quite another. Thus is my case, its crazy how many spoofed numbers they use. I'm more amazed that the carrier hasn't done something than I am that it's not a mod. There's tens of thousands of people with this problem and the one solution that requires no effort on the end user isn't available to cell phone users.
I don't know - I'm just at my wits end with these calls. I'd be happy to do it myself if a dev is willing to give me some direction, or ideas to try out.
Click to expand...
Click to collapse
If I knew what the mod is it would be possible to port to stock. My guess it is in smali which cannot access on stock odex. Stock Would have to be deodexed to access smali which is also possible in rom form. Nobody I know of is deodexing stock 5.1.1 We have done it and got it working but don't post as we still don't know if everything works. Lollipop is still hard to make fully working rom from stock image. M is even going to be harder. Would still need the code required to enable the mod.
prdog1 said:
If I knew what the mod is it would be possible to port to stock. My guess it is in smali which cannot access on stock odex. Stock Would have to be deodexed to access smali which is also possible in rom form. Nobody I know of is deodexing stock 5.1.1 We have done it and got it working but don't post as we still don't know if everything works. Lollipop is still hard to make fully working rom from stock image. M is even going to be harder. Would still need the code required to enable the mod.
Click to expand...
Click to collapse
I concurr, your talking about taking apk's not meant for a certain rom and adding them in to pray it works. Did you look in the market t.o see if there was a KB you liked there? You can't just switch around apk's like that because you could easily get force closes. If you want to try just copy and paste it into a rom. you wont brick doing that, it may work
I know it isn't as easy as swapping apks - I had *hoped* it would be similarly easy, but figured there was no way.
Idk what the mod is, or how Chroma did it - but the dialer looks stock other than the addition of that option under the advanced menu in the dialer settings.
I've looked in the market, used many of them, Mr. Number was my go to for a long time but it is iffy on 5.1 as *sometimes* a call will get through for a couple rings then gets blocked. It would also block known contacts on a rare occasion, I would go a couple days without knowing I had missed a call from a family member because it didn't show up in Mr. Number or the stock dialer - somehow it blocked it and had no record of the call even coming in.
That's why I was hoping to find a way to get this option in the stock dialer - without porting anything or swapping apks, that way it's a native feature to the dialer and I wouldn't have to depend on 3rd party apps to do it.
I've asked Google, but their solution was to add them to one contact and send the calls to VM - while that essentially works, that means I'd have to add all 500+ numbers to a single contact, and they OFTEN call from spoofed numbers I've never seen before - so that really doesn't solve anything.

Possible alternative to OP7P T-Mobile stock ROM

This is not a tutorial, just a technical note. I have been able to restore my unlocked T-Mobile OnePlus 7 Pro (model GM1915) that was firmware build GM31CB, with the GM21AA for models GM1911 and GM 1917. YMMV.
I have not experienced any issues with LTE or wifi calling, or text messages. I immediately received and successfully installed an OTA. The only difference I've seen so far is the wifi-calling icon now says "V♂WIFI" (still works though) and default ring tone.
Before you ask why didn't I just use the MSMTool to install the international version.... Some may find themselves in my predicament, where they are Linux or Mac users and the MSMTool.exe is for Windows. I tried a Windows VM but was only partially successful. The T-Mobile download links I found were broken and GM21AA is easily found.
Follow up: I've figured out that the male symbol is actually "oiP" to spell VoiP. Another note is that swiping from edge left to center used to bring up curated news, a feature I liked, but now it brings up a tray with widgets like a parking tool. I'm starting to think that the tiny differences I'm noticing are differences in the updates because T-Mob was behind on the releases. Also, I neglected before to mention that the ROM was installed via TWRP.
dgerton said:
Follow up: I've figured out that the male symbol is actually "oiP" to spell VoiP. Another note is that swiping from edge left to center used to bring up curated news, a feature I liked, but now it brings up a tray with widgets like a parking tool. I'm starting to think that the tiny differences I'm noticing are differences in the updates because T-Mob was behind on the releases. Also, I neglected before to mention that the ROM was installed via TWRP.
Click to expand...
Click to collapse
You can get that back by installing Nova launcher and the Google companion app. The international version is leaps and bounds better than the hack job TMo did. For being optimized for Tmos network I have way better performance on the international version. MMS messages wouldn't always download, sms would hang. On the international version everything just works. You think it would be the other way
Sent from my GM1915 using Tapatalk

Categories

Resources