I keep having to replace items and folders on my desktop. I have things set up the way I want them, but if I have to "restart" the phone a bunch of them disappear every time. It's like the desktop state is not properly saved. I'm wondering whether it has to do with the merged CD card? I'm on the unlocked 4GB model XT1710-01. There's no SIM card yet because I have to port from Straight Talk Verizon to Sprint.
Has anyone else seen this behavior? Is there a fix?
Interesting, we noticed a similar symptom on an HTC One M8. Unfortunately our fix was to get a Moto Z2 Play. Which isn't helpful, but could indicate that perhaps it's an android issue and an expanded search may be in order (i.e. not limited to the moto device)
My fix was to install Nova Launcher, but I shouldn't have to do that. I'm guessing that it's an Android Nougat issue related to the merged SD card.
dahlungril said:
Interesting, we noticed a similar symptom on an HTC One M8. Unfortunately our fix was to get a Moto Z2 Play. Which isn't helpful, but could indicate that perhaps it's an android issue and an expanded search may be in order (i.e. not limited to the moto device)
Click to expand...
Click to collapse
Related
Greetings all!
I have searched around a bit but surprisingly I can't find anyone else that has had this problem.
I have two Mark 1 Motorola Droids (aka Milestone) on Verizon Wireless. My phone works okay, but it is the original version. One problem I have with it is that I can't over clock it as high as the other one.
So I want to switch to the other phone as primary. No problem, when I change the MEID on VZW site the new phone works, and my apps (that are still on the market) are downloaded. That is all fine and dandy, but I want all the data IN those apps to come too.
For instance, I have Handcent for text messages, on the new phone all the old texts are gone. I also use an app called Fuel Log to monitor all my fuel consumption on three cars. This data is gone. Also my call history is gone, and this list goes on. I was told by a dev before that they used the default android database but he didn't know how to move it. My thought is if I can find it, I can move it.
The other issue is that my old phone is rooted, with an almost stock ROM. So I can't just "Ghost" it to another phone and upgrade to Froyo. I want to use Froyo on the new phone first, then move the database over.
Anyone have any ideas?
Matt|ttaM
Doesn't anyone have any ideas or suggestions?
Matt|ttaM
I'm wondering if anyone who installed the dev preview of 7.1.1 on the 2015 Nexuses tried setting up their new Pixel by copying data with a cable. I'm doing it with 7.0 on my N6P, but it doesn't appear to be different than the old proximity method that came out with M, that is, it doesn't copy a lot of stuff like downloads and app data. I was hoping that with N and with this new cable method finally one could seamlessly transfer from one phone to another, but it isn't the case here, so wondering if having 7.1.x on the old phone makes any difference.
andy o said:
I'm wondering if anyone who installed the dev preview of 7.1.1 on the 2015 Nexuses tried setting up their new Pixel by copying data with a cable. I'm doing it with 7.0 on my N6P, but it doesn't appear to be different than the old proximity method that came out with M, that is, it doesn't copy a lot of stuff like downloads and app data. I was hoping that with N and with this new cable method finally one could seamlessly transfer from one phone to another, but it isn't the case here, so wondering if having 7.1.x on the old phone makes any difference.
Click to expand...
Click to collapse
I have 7.1.1 on my 5X. Can't get the initial setup/transfer to work whether I try to use the cable or cloud. "Google Play Services has stopped working" comes up just after I hit "copy" on the old phone, or when I select the 5X backup in the WiFi version, and basically brings me back to the beginning of the process. Not sure why it's happening, spent hours on the phone with Google support last night and didn't get anywhere, other than them offering me a replacement phone. That said, the support person couldn't even send me an RMA link that didn't give a "Internal Server Error" no matter what device or network I used... Anyway I doubt my particular issue is a 7.1.1 issue?
Im using a HTC 10 (EU variant). Today i was scrolling through "Netguard" (if you dont know it, its an app to prevent other apps from internet access), since i configured it to show system apps it displays way more apps than the normal app overview in the settings. In there i found an app called "RootPA" and one called "root", which seems strange since i didnt unlock the bootloader or root on my own. The details in the RootPA entry say "com.gd.mobicore.pa", no idea if thats helpfull to determine the origin of this mysterious app.
Can you help me with this?
Did you Google it?
I did, but the results were not realy usefull. I found someone with a modded Galaxy S3 who deleted a RootPA on accident and broke stuff, but that ssems unrelated. Are there any things i could do to find out more about the app installed on my phone without root?
I cant say its something I've ever seen. If this person in the past removed it, and it broke stuff, that would suggest that it may have been a system app and he was rooted. From what I managed to find on google, it is part of a security suite (mobicore) used by networks to monitor what the state of the phone is, presumably incase something happens, and it was the user fault, and they know for a fact because they have logs of what the phone has done.
[ACCESS_NETWORK_STATE] Allows applications to access information about networks
[INTERNET] Allows applications to open network sockets. (i.e send information)
[READ_EXTERNAL_STORAGE] Allows an application to read from external storage.
[READ_PHONE_STATE] Allows read only access to phone state.
A friend of mine got his HTC 10 2 days ago, ill ask him to look for this app. Its unlikely we would have the same virus/whatever installed.
Edit: He just reseted his 10 (due to missing language options, but thats another topic), but still found "root" and "rootPA" on his phone, so its preinstalled (although i still dont understand whats its purpose).
RootPA is provides service for provisioning secure applications that run on ARM trustzone and t-base OS (formerly mobicore). It is preinstalled in some vendors Android devices (search for this string on the internet: htc-devices-to-incorporate-trustonic-t-base-tee), but mostly unused as far as I know. The source code of some versions is available on the Internet (e.g. on github /Faryaab/android_hardware_samsung_slsi_exynos5410/tree/master/mobicore/rootpa).
It has nothing to to with rooting or unrooting the device.
PA route is very dangerous I had some I have somebody who has hacked into my phone through this particular program so to speak I have a lot of issues right now with my phone trying to get them off of my phone and this seems to be the root cause or the start of it have anybody knows how I can clear my phone and my Ram from the Vicious hacker I appreciate it I'm tired of being watched and recorded everything I do
Illfidusoon12 said:
PA route is very dangerous I had some I have somebody who has hacked into my phone through this particular program so to speak I have a lot of issues right now with my phone trying to get them off of my phone and this seems to be the root cause or the start of it have anybody knows how I can clear my phone and my Ram from the Vicious hacker I appreciate it I'm tired of being watched and recorded everything I do
Click to expand...
Click to collapse
PA route..... .rootPA ......2 different things. Hacked ? Unlikely, I think some OCD is kicking in. Want to be clean? RUU the device and do not restore anything
Recently (outside the U.S.) Instagram has release the Live functionality, but so far I've tried to go live with my Moto Z Play, but without luck. Instagram keeps showing a message saying it's not possible to go live because of network problems.
I also have a working HTC One M9, and Instagram Live functionality works perfectly, no error messages.
I've seen some uses experiencing problems (with other phone models, not specifically the Moto Z Play) and some say that logging out and in again on Instagram will do the trick, others say to restore your phone to factory settings and then it'll work. None of these tips got me anywhere near. =(
I'd like to know if it's an issue with Moto Z Play, or if the next minor updates shall fix it, or maybe the big Nougat update may solve that.
Is anyone having the same issues?
Thanks a lot!
I'm curious if anyone has tried the 7t on the visible Network by Verizon. I got my Sim in the mail yesterday and there were some issues with the app. The phone recognized the Sim but I could not activate because the app didn't recognize that the Sim was inserted and therefore could not proceed. I currently have a case being worked by visible. I checked my IMEI before ordering the Sim and visible said it was compatible. I'm curious about others experience with visible using the 7T. If anyone else has had a similar experience and has a workaround it would be greatly appreciated.
7T works fine here. Followed their instrutions for provisioning (reboots etc)and works fine. Default voicemail password is 1234.
(My carrier tag on XDA says "Verizon" because there's no Visible tag)
Skripka said:
7T works fine here. Followed their instrutions for provisioning (reboots etc)and works fine. Default voicemail password is 1234.
(My carrier tag on XDA says "Verizon" because there's no Visible tag)
Click to expand...
Click to collapse
I followed the instructions too, just a different result sadly.
khuttha said:
I followed the instructions too, just a different result sadly.
Click to expand...
Click to collapse
One thing I found, was that the Visible SIM fit very loose in the tray--it kept wanting to push itself out as I was closing the tray and needed held in. Barring that--there have been a few app updates--could try rolling back versions via apkmirror etc.
For people whom it works--it is quite great....but people with issues find Visible support generally useless, unfortunately .
Skripka said:
One thing I found, was that the Visible SIM fit very loose in the tray--it kept wanting to push itself out as I was closing the tray and needed held in. Barring that--there have been a few app updates--could try rolling back versions via apkmirror etc.
For people whom it works--it is quite great....but people with issues find Visible support generally useless, unfortunately .
Click to expand...
Click to collapse
Update....I was able to activate on the OnePlus 6t using the app and swap the SIM back to the 7t and it worked. I would have tried this much earlier but visible said they didn't support the 6t.....go figure.