Airwatch Error after installing Xposed Framework - Xperia Z5 Premium Q&A, Help & Troubleshooting

First off, sorry if I'm not in the right place - Let me know or move me, its fine by me. This is my first post here...
Backstory: Our company is trying to become more secure(They just blew 30k on Airwatch(MDM Software) and have a full time employee on the phone with him just about every day...) and I'm one of the lower guys on the IT Totem poll but I'm not really worried about them yelling at me for having root, and I can get my E-mails right now but I do know eventually they are going to bring it up and probably make me get rid of it. Xposed has a work around for this, but when I flash Xposed - The app crashes upon opening every time "Inbox" or "Airwatch" Has closed unexpectedly.
At first I thought it was the RomAur I installed because I went that route as it packaged Xposed and saved me a minute and I wanted to try it anyways - So I went back to stock with Root, Airwatch opened fine. So then I just tried to install Xposed and when I booted up it "optimized" all of my Apps, including Airwatch and Inbox(Which is Airwatch's Mail thingy) .
So, I undoubtedly believe its something in Xposed that's causing a corruption in Airwatch so I cannot even open it. I feel pretty good that if I could get it to run with Xposed that either Rootcloak or the Hidewatch Xposed mod's can fix it, but I can't get it to open to even test my theory.
As I said, I'm in IT and I've been flashing phones/rooting/etc for about 6 years but generally never posted because I didn't feel nearly as smart as everyone else here seems on the forums but I am capable and can give logs if you tell me how to - but now I have a problem and I believe with the increase of MDM software out here that I'm not the only one, or there is about to be a lot more like me that have this problem.
So.
1.) Does anyone have an idea how to stop the optimization of an APP through upgrading to the Xposed installer?
2.) An Idea to get Airwatch to a point that it can open?
3.) Something totally ingenious I'm not capable of thinking of?

Related

[Q] Experiencing major issues with any custom rom. Please help!

((if this is in the wrong place or has been covered before, I apologize...))
Hello all.
I just became the new owner of a family member's Samsung Galaxy S3 (AT&T). Already owning and tinkering with two xperia Ion's I wanted to have a little more freedom and experience Kitkat on the GS3.
I had no experience in unlocked bootloaders and all that, so I figured that I would let the Cyanogenmod Auto-Installer do the work for me and install CM11 on my device.
It worked great initially! No problems whatsoever aside from minor glitches here and there. As soon as I started installing some more apps and Xposed modules, I noticed that things were getting odd.
Eventually, my phone wouldn't connect to google's play services whatsoever. Despite countless resets of the phone itself and my modem/router, nothing seemed to help. Flushing the cache and dalvik didn't help either, nor did a factory reset. The issue kept coming back.
Thinking that perhaps another rom wouldn't have the problem, I installed C-Rom (which was based on 4.4.4 KK). It ran BEAUTIFULLY! It is sure one hell of a rom. But then, not too long after I had everything installed and running the way I wanted it to, it had the same errors as before.
I don't know how to explain the error other than the phone just generally messing up. I don't recall it ever having those issues on stock, but then again, it wasn't my phone on stock, and the first thing I did upon receiving it was put a custom rom on it.
But the error can only be explained as a general f***-up of the entire OS. Commands run brutally slow (I will launch the flashlight and it wont turn on until seconds, even minutes later. Alternatively, text messages take eons to send and receive, which I am positive is not an error on the AT&T side of things). Then, whenever I try to download or install an app from the play store, the application will download partially and then stall for what feels like eons. Some of the applications just stop there, and some I will find installed on the device some 30 minutes later. Not to mention that the signal icons on the quick setting tiles are all turned orange for some bizarre reason. Another bizarre issue is that no matter what, I can never launch the terminal to execute an htop, logcat, or anything! The terminal just stalls and eventually crashes, while it worked fine before.
I've checked online for errors similar to this, but haven't found anything that has helped the phone. Anyone out there who is willing to give this a crack or just point me in the right direction?
Thanks in advance.
benhofb said:
((if this is in the wrong place or has been covered before, I apologize...))
Hello all.
I just became the new owner of a family member's Samsung Galaxy S3 (AT&T). Already owning and tinkering with two xperia Ion's I wanted to have a little more freedom and experience Kitkat on the GS3.
I had no experience in unlocked bootloaders and all that, so I figured that I would let the Cyanogenmod Auto-Installer do the work for me and install CM11 on my device.
It worked great initially! No problems whatsoever aside from minor glitches here and there. As soon as I started installing some more apps and Xposed modules, I noticed that things were getting odd.
Eventually, my phone wouldn't connect to google's play services whatsoever. Despite countless resets of the phone itself and my modem/router, nothing seemed to help. Flushing the cache and dalvik didn't help either, nor did a factory reset. The issue kept coming back.
Thinking that perhaps another rom wouldn't have the problem, I installed C-Rom (which was based on 4.4.4 KK). It ran BEAUTIFULLY! It is sure one hell of a rom. But then, not too long after I had everything installed and running the way I wanted it to, it had the same errors as before.
I don't know how to explain the error other than the phone just generally messing up. I don't recall it ever having those issues on stock, but then again, it wasn't my phone on stock, and the first thing I did upon receiving it was put a custom rom on it.
But the error can only be explained as a general f***-up of the entire OS. Commands run brutally slow (I will launch the flashlight and it wont turn on until seconds, even minutes later. Alternatively, text messages take eons to send and receive, which I am positive is not an error on the AT&T side of things). Then, whenever I try to download or install an app from the play store, the application will download partially and then stall for what feels like eons. Some of the applications just stop there, and some I will find installed on the device some 30 minutes later. Not to mention that the signal icons on the quick setting tiles are all turned orange for some bizarre reason. Another bizarre issue is that no matter what, I can never launch the terminal to execute an htop, logcat, or anything! The terminal just stalls and eventually crashes, while it worked fine before.
I've checked online for errors similar to this, but haven't found anything that has helped the phone. Anyone out there who is willing to give this a crack or just point me in the right direction?
Thanks in advance.
Click to expand...
Click to collapse
It sounds like you're the modules you're installing are crashing your system. I'd suggest you do a clean flash of w/e rom you wanna rush (you seem to like C-rom) and run it clean for a few days. You can install apps and such but don't restore system apps and don't install modules.
If it runs fine after a few days, you can cherry-pick the modules you wanna use (make sure they're made for the sammy phones). Install one or two, test for a couple days and so on. You'll eventually find which one is messing with your system (if that's actually what's causing the problems).
All seems to be well now. I've isolated the problematic app after slowly restoring all my app data one at a time. I have since moved to a different rom (SOKP) and everything is going running smoothly! Surprisingly, it wasn't Xposed causing the issue, but a market app that displays system info similar to conky on Linux computers. Once I installed it, the system just crapped out. Signals dropped, the terminal froze, and none of my apps seemed to work properly. But once I uninstalled the app and reset my phone, all was well.
Thanks for pointing me in the right direction!

SDCard bug? or something else

Well, the story goes:
My wife´s SGH-i474 (AT&T) had 4.1.2 installed, crappy reception, launcher buggy (it created more desktops everytime she wanted to delete one), and overall the phone felt laggy. She plays just 3 games, Farmville 2 CS, Candy Crush and Clash of Clans (she´s actually pretty good this one). Not too long ago, since the phone was only rooted to install greenify and link2sd to freeze the bloatware, she found out that it was possible to update the phone to a newer release; and I saw that there was an official OTA to 4.4.2, but since we are overseas, the stock update won´t go (it said that the phone was updated).
I dived into google and I saw that here on xda there was a method to get it into 4.4.2. And me, being the android guy and wanted to get lucky I tried it and succedded, but with one detail...
You see, I mentioned the games for a particular reason, 2 ouf of 3 work, Farmville for some reason doesn´t load (it gets to the loading screen and stays there at 0%). I left it overnight, with the option of leaving the screen on while charging, so that the phone won´t "sleep" to see if the game need to download a file and it was taking a long time, but no, 10 hours later it was still at 0%.
After that, I decided to install Logcat to see what was going on while the game at launch time. Surpringsinly, logcat was unable to save the log to the "sdcard". , another dive into google revealed that there was indeed a bug on the sdcard permissions (never knew that this kind of thing would happen to the gigantic Google, OMG ), and there were several fixes available, which I tried, even manually (just to see that the apps did indeed what they advertised, but to be true, the stock rom that I used had this fix already installed, thank you Mr even... or who ever went into the trouble of making all those files and instructions that helped me get into 4.4.2, I just don´t recall the nickname, but I do remember he has a beard )
Back to the point, I find it odd, that logcat was unable to write to the sdcard, and more odd that just a game was unable to work, because it worked before the update, but logcat doesn´t show anything related to "permission denied" to the Zynga app, nor to logcat itself when it wanted to write to the sdcard.
Since I am just a poweruser, I already wiped to stock and nothing changed, I tried another logcat application with the same result, so what I believe is that maybe the apps have something wrong, because I didn´t find anyone complaining about the stock rooted rom that I used. Besides that it was stock, and just rooted, I just wanted to know if anyone happened to have this problem and if they were able to fix it or have a workaround it.
Just to clarify, the phone works perfectly, and all the 51 apps that has installed (yep, she´s kinda a tech girl herself) work, except FV (which won´t go past 0% at the loading screen) and those to logcat applications that I used. (Catlog and Logviewer Lite, which can´t save logs to the sdcard), even the camera works and saved pics to the sdcard withouth problem (one of the things I saw reading is that maybe the camera would stop working but nope, just fine).
If you have any ideas, please, express yourself.
The kitkat update for google did in fact make it to where nothing could be written to sd. Google trying to get rid of sd cards for some stupid reason. Anyway, if the phone is rooted, try the xposed app with the external sd modules. Took care of my problems with that, not on my S3 because enewman17 is so damn awesome with his S3Rx rom that he took care of that, but on my Note 10.1 and Tab 4 fixed it right up
I see, could you be more specific about the xposed app, the name in fact, a search rendered quite a few, an I am not native english speaker.
I mustbe cursed hehe, I found the "app", is a framework, but guess what? I am unable to install because it is unable to write to the sdcard hehehe, I will give a try to the custom rom.
To mr Enewman, you sir, you deserve a cold beer, my wife is now happy, just a little glitch with the google keyboard at the first boot but after that excellent.
XDADoog said:
To mr Enewman, you sir, you deserve a cold beer, my wife is now happy, just a little glitch with the google keyboard at the first boot but after that excellent.
Click to expand...
Click to collapse
It is an outstanding ROM for sure. Glad it's working.

Learning My T-Mo D851 on ATT. Musings of a stranger in a strange land...

Hi everyone,
I'm the new owner of an unlocked T-Mo D851, and will be using it on AT&T. I bought the T-Mo version instead of the ATT version due to the unlocked bootloader and better Dev support. Love those Devs!
I figured I'd post a thread with the things I learn along the way, to help others that might benefit, particularly since I'm joining the G3 community long after the novelty has worn off. Folks like me that join have a lot of past experience to review here, and so much is out of date it can be intimidating, particularly when our new device acts a lot different from our old one. I hope this thread helps someone, but at minimum it will serve as documentation for me to refer back to, should I need that. I'll include links where appropriate.
I'm an intermediate level flasher, having worked with maybe 6-8 other phones/tablets. So, I know enough to be dangerous, but not enough to have an ego to bruise. My most recent phone was a T-Mo Galaxy S4. But I dropped it, and cracked the screen, just a few weeks after getting it all settled in with a nice 5.1.1 GPE ROM. Sigh.
I got the phone a few days ago but have just gotten around to working on it.
On day 1 I charged it up, skipped setup (touch corners, upper left, upper right, lower right above the softkeys, lower left above the softkeys... took 10 tries or so!), and connected the wifi (no sim card inserted yet). It immediately found update 20E (it shipped with kitkat). I let that update, but was surprised it didn't find the current 20G update. I want to make sure I start with the latest firmware/modems etc. installed.
In this thread, helpful user @mitbit2k3 pointed me to the online LG site that lets you download the LG Mobile Support Tool. It also gives instructions for installing the PROPER PC connection driver for the phone which works, versus the default Win7 driver that doesn't work for the purposes of the update. With proper driver installed, and with USB connection in the right mode (follow instructions to set the phone USB settings), I got up to 20G stock.
I exercised the phone a bit (still without SIM card) and made sure everything worked... cameras, GPS, wifi, etc.
Then I figured it would be time to install TWRP and take it from there. Much to my surprise, you need to root this thing FIRST. Even with an unlocked bootloader, you can't just fire up ODIN and flash TWRP.
I did my research on the forum and through Google... with all the versions of software since release there were numerous descriptions of how to root the thing, some of which were outdated. For me, on 20G software (5.01 Android), this worked fine:
https://www.reddit.com/r/LGG3/comments/3n0nk1/new_super_easy_oneclick_way_to_root_g3/
it references back to XDA of course:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
From this I learned to review the top level LG G3 subforums, not just the T-Mobile XDA subforums!!
OK, that rooted me just fine and installed SuperSU. I was able to use the "first way" which is super simple.
With that done, I was able to install TWRP. I went straight to the source for it:
https://twrp.me/devices/lgg3tmo.html
I used the "dd" method which involves running ADB on the PC. I use a version that is a "Minimal ADB and Fastboot" that works fine... I used it to mess around with my Shield tablet previously, so I was familiar with it. Basically you run the minimal ADB through a desktop icon, and it loads a command line interface. You type ADB Shell after plugging in the phone to the USB cable (it has to be on, developer options enabled, debugging enabled). Then you type the commands listed on the TWRP site. Pretty soon TWRP is installed.
Next I had to figure out how to get into download mode. Yeah, yeah... power plus volume down... been there done that, but on the LG you have to boot with power/down, then when the LG icon comes up you release for a second, then press the two keys again, then at the next screen tell it you want to wipe the phone, and confirm this again on the next screen. THEN it finally boots into TWRP. Kinda scary. And getting the keys right takes some practice.
Once in TWRP, I backed everything up (including EFS partition) to an external SD card, just in case I messed something up. I had previously erased the SD card from within the phone's SEttings/Storage mode, to make sure it would be able to be accessed. No problem.
So now I've got a rooted phone, with TWRP installed, and the next step is to figure out what I want to do ROM wise. I wish there were a 5.1.1 GPE stock + LG Camera ROM. But I haven't found one. I like plain ROMs. The default stock ROM, even if it were debloated, its a bit annoying to me (and just 5.0.1) so I'll probably move to BlissPop or Slim something, but I will research around.
It's time to stick my SIM in and see how the phone does on AT&T. I'd like to get a baseline before I go ROM-hopping.
I will say that on stock ROM, with no SIM but WIFI on, the standby power drain on this thing is incredible. It went overnight (7 hours) and was still reading 100%. A whole 24 hours in, it was only a few percent lower. Of course, I hadn't attached any Google accounts, so the phone was truly idle, but it's very impressive nonetheless.
Stay tuned. I'll be updating this as I go along.
OK, I'm a few hours in.
No problem with my ATT SIM card in the phone; the phone was purchased unlocked and everything hooked up fine as soon as I entered in the APN information for ATT (which you can get from here).
The phone gave me a warning about WIFI Calling invalid SIM; I went into the settings and turned off WIFI calling, since I'm on ATT and only T-Mo offers it.
One other problem I haven't sorted out yet is that I get a text each time I reboot the phone, apparently my phone is sending a text to a very long address 060504071000004163.... and the text I get back is an error message that this isn't a valid number. Not sure how to turn this off. Annoying, but once per boot won't kill me until I figure it out. Google will likely be my friend. EDIT: I think this relates to T-mo visual voicemail. I went into the T-Mo Visual Voicemail app and I immediately got another one of these texts. Time to remove this app...
Meanwhile I notice the WIFI reception of this phone is much stronger than the S4. On the other hand, it seems less likely to drop a weak WIFI in favor of a stronger one... I have several access points around my house, and I've found I've needed to switch them manually now and then. Haven't had to do this on the S4.
I'm also struggling to get restores to work from my Backup Your Mobile app. I moved the backup onto an SD card in the G3, but the app isn't recognizing it. Uh oh. That's got my MMS/SMS/Call log backups. So, I've still got things to work on.
I gradually entered my various Google accounts, and let Play Store download the updates needed for all the apps. I've got about 75% of the apps I use re-downloaded.
I've got one "serious" problem in that the Play Store says the ATT Visual Voicemail app, which is a cornerstone of how I use the phone (because it transcribes voicemails into readable text), isn't compatible with my phone. That's crap. It worked fine on my T-Mo S4 (running a generic GPE edition). I'll probably have to sideload the app, but it's annoying that it's locked out.
Making progress.
I still couldn't download the ATT Visual Voicemail app from the Play Store, and went stir crazy trying to find it on my S4 (which is rooted, so I should be able to find it, but...). I went haring off in lots of directions, including making a full apps backup with Helium, but then the G3 won't restore without using the PC app due to changes in 5.0... which is weird because my S4 (which is running a 5.1.1 GPE ROM) restores fine. I don't have the PC app installed so I tried using Backup My Mobile... but then eventually figured out that on the S4, with ES File Explorer, I not only had Root Explorer OFF (didn't know I had to turn it on), but it's easy to find apps with the APP Library. Once I found the app there, I uploaded it to my Google Drive, then downloaded it from there onto the G3. It installed fine.
I used System App Remover (which requires root) to get rid of all the T-Mobile specific apps and that annoying Lookout security program. Bah! This cured that spurious text message I get with each boot. It was definitely due to the T-mo visual voice mail. Problem solved!
In using the phone, I'm a bit bummed because it didn't occur to me that a big part of my bigger screen as compared to the GS4 would be taken up by the softkeys on screen. The S4 has a physical home button and capacitive keys to either side. So, my screen isn't effectively much bigger, when I account for dedicating some of it to the buttons. You can make the buttons autohide, apparently. One issue is I use my phone in landscape much of the time, and the buttons don't rotate to the new "bottom" of the screen when I rotate. Gotta figure that out.
This morning I installed the PC Helium App so I could enable backup/restore access on the G3. That worked fine, but Helium on the G3 still doesn't detect my external SD card, in order to restore from it. I could manually copy files over to the internal Carbon folder, and restores from there worked fine. Still, I'm not sure why I'm having so much SD Card angst. I know things change each version of Android wrt SD cards... maybe something is fixed in 5.1.1 (as I had on my S4) that is broken in 5.01 on the G3.
So, I've got some tweaking to do from here. The phone is basically set up and working fine except for some straggler apps that I won't bother with until I need them, with one major exception: I need to go in and set up Light Flow. That app is a big part of how I manage notifications on any phone...
If you rooted your phone, then download and run the SDFix app from the Play Store. Apps will then have the ability to write to the external SD card...
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en&referrer=utm_source%3Dgoogle%26utm_medium%3Dorganic%26utm_term%3Dsd+card+fix+kitkat&pcampaignid=APPU_1_bJMtVsTJBoKajwP4noeABw
... and yes, it also works w/ Lollipop.
redduc900 said:
If you rooted your phone, then download and run the SDFix app from the Play Store. Apps will then have the ability to write to the external SD card...
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en&referrer=utm_source%3Dgoogle%26utm_medium%3Dorganic%26utm_term%3Dsd+card+fix+kitkat&pcampaignid=APPU_1_bJMtVsTJBoKajwP4noeABw
... and yes, it also works w/ Lollipop.
Click to expand...
Click to collapse
Thanks. I'll give this a whirl!
EDIT: WORKED LIKE A CHARM. Thanks again! And thanks for the link, because there were several SDFix apps. The link made sure I got the one you intended.:good:
OK, I'm in a pretty good place after making some changes. Still plenty to tweak though.
First, I decided to abandon the stock Home launcher. It was a bit annoying with little UI tweaks LG made that make it just not how I expect it to look, but the kicker was that in landscape mode, the titles of the icons were not readable... they were mostly cut off. I use Rotate (Ultimate Rotation) so pretty much every screen including home is rotatable. But LG Home maintains in landscape mode the little dots representing the various home screen pages... these take up just enough room so that things get squished a bit and the titles cut off. Couldn't figure out how to disable that, so just bailed and installed Google Now Launcher which fixed me right up. That fixed the look and feel of the home screen, the apps drawer, and even reverted settings to the normal views I'm used to.
The only problem is that it kills double tap to sleep... or at least reduces the footprint of the double-tappable area to the notification strip at the top. Sigh. In another thread someone mentioned using Greenify to fix it. I'll try that when I get a chance.
Another weird thing I've got going on is that when I connect via Bluetooth to my car, it starts playing music. See this thread. That's pretty annoying... for now I deleted the default music that was playing, and with an empty directory nothing plays.
I put on a screen protector last night. I got the 0.2mm iCarez one. I performed the application in a steamy bathroom after running the hot shower for a bit, per some tips over in the Accessories thread. I left the backing on, positioned the glass on the screen, taped one side for the "hinge method" after getting it perfectly aligned and accounting for the eventual loss of thickness of the plastic underbacking, cleaned everything one last time with the alcohol wipe, peeled the backing, and plopped it on starting in the center. Got it perfectly positioned and no major bubbles. There were a couple of "spec sized" non-uniformities but they were gone by morning.
I'm gradually setting in... Still lots to play with.
I've noticed the WIFI, while it gets good reception, is a bit sluggish to drop a weak connection in favor of a strong one. Anybody got a tweak for that?
Frankenscript said:
I've noticed the WIFI, while it gets good reception, is a bit sluggish to drop a weak connection in favor of a strong one. Anybody got a tweak for that?
Click to expand...
Click to collapse
Try this app for WIFI management. I have tried several and this is the best I have found. https://play.google.com/store/apps/details?id=org.kman.WifiManager I agree completely that the wifi in the phone is very slow to drop a weak signal and grab a stronger one. But with wifi manager you can play with the sensitivity. Good luck.
Will do. Thanks for confirming it's not just me. Also on another note I just found the LG keyboard has lots of settings for customization. Not bad. May keep it!
Sent from my LG-D851 using Tapatalk

Fake YouTube app with adware pre-installed on stock US 11S

Hi,
I got this phone recently, and noticed that my chrome browser kept opening up a pop up every time I opened it, often managing to install battery pro app or something similar.
I tried almost all anti malware apps to no avail, and after searching vigorously, I found the source.
It seems the phone came pre installed stock with a rogue YouTube app, which appears as an old version, and which you can't update from the playstore.
Check out the thread below, thats how I good to the bottom of it. You need to root your phone to remove it. I was actually being taken to the same website as the author of the blog, and for him it was YouTube as well, so seems this is common practice among foreign cheap phones.
http://blog.teamleadnet.com/2015/06/how-to-remove-adware-browser-hijack-or.html?m=1
deniso177 said:
Hi,
I got this phone recently, and noticed that my chrome browser kept opening up a pop up every time I opened it, often managing to install battery pro app or something similar.
I tried almost all anti malware apps to no avail, and after searching vigorously, I found the source.
It seems the phone came pre installed stock with a rogue YouTube app, which appears as an old version, and which you can't update from the playstore.
Check out the thread below, thats how I good to the bottom of it. You need to root your phone to remove it. I was actually being taken to the same website as the author of the blog, and for him it was YouTube as well, so seems this is common practice among foreign cheap phones.
http://blog.teamleadnet.com/2015/06/how-to-remove-adware-browser-hijack-or.html?m=1
Click to expand...
Click to collapse
I had the same problem, and solved it by finding the same site you linked. However I had further problems later, apps installing themselves without asking permission. The trojan also changed the install apps from unknown sources setting. Christ only knows what else it was doing.
The apps that installed were SuperB Cleaner, Super File Manager, Browser, Facebook Updater and others installed automatically.
After running all anti virus to no avail I found this
https://play.google.com/store/apps/details?id=com.cleanmaster.security.stubborntrjkiller&hl=en
Which seems to work eventually. However that app interacts strangle with SuperSU, killing it, requiring and update to the binary.
This seems to have found something as well
https://www.avira.com/en/free-antivirus-android
It's also being discussed here
http://forum.xda-developers.com/lee...version-youtube-problem-t3408009#post67587785
http://forum.le.com/us/index.php?threads/letv-x800-1pro-how-to-update-eu-rom.455/page-2
http://forum.le.com/us/index.php?threads/open-support-for-model-letv-le1-x800-pro_us.1614/page-5
I'm worried now the phone is permanently compromised without flashing a new rom. And all the US versions seem to have issues.
cormacfitz said:
I had the same problem, and solved it by finding the same site you linked. However I had further problems later, apps installing themselves without asking permission. The trojan also changed the install apps from unknown sources setting. Christ only knows what else it was doing.
The apps that installed were SuperB Cleaner, Super File Manager, Browser, Facebook Updater and others installed automatically.
After running all anti virus to no avail I found this
https://play.google.com/store/apps/details?id=com.cleanmaster.security.stubborntrjkiller&hl=en
Which seems to work eventually. However that app interacts strangle with SuperSU, killing it, requiring and update to the binary.
This seems to have found something as well
https://www.avira.com/en/free-antivirus-android
It's also being discussed here
http://forum.xda-developers.com/lee...version-youtube-problem-t3408009#post67587785
http://forum.le.com/us/index.php?threads/letv-x800-1pro-how-to-update-eu-rom.455/page-2
http://forum.le.com/us/index.php?threads/open-support-for-model-letv-le1-x800-pro_us.1614/page-5
I'm worried now the phone is permanently compromised without flashing a new rom. And all the US versions seem to have issues.
Click to expand...
Click to collapse
I had the same problem with foreign apps being installed, but removing the rogue YouTube solved it.
Had no issues for 2 months now
cormacfitz said:
I had the same problem, and solved it by finding the same site you linked. However I had further problems later, apps installing themselves without asking permission. The trojan also changed the install apps from unknown sources setting. Christ only knows what else it was doing.
The apps that installed were SuperB Cleaner, Super File Manager, Browser, Facebook Updater and others installed automatically.
After running all anti virus to no avail I found this
https://play.google.com/store/apps/details?id=com.cleanmaster.security.stubborntrjkiller&hl=en
Which seems to work eventually. However that app interacts strangle with SuperSU, killing it, requiring and update to the binary.
This seems to have found something as well
https://www.avira.com/en/free-antivirus-android
It's also being discussed here
http://forum.xda-developers.com/lee...version-youtube-problem-t3408009#post67587785
http://forum.le.com/us/index.php?threads/letv-x800-1pro-how-to-update-eu-rom.455/page-2
http://forum.le.com/us/index.php?threads/open-support-for-model-letv-le1-x800-pro_us.1614/page-5
I'm worried now the phone is permanently compromised without flashing a new rom. And all the US versions seem to have issues.
Click to expand...
Click to collapse
I had the same problem with foreign apps being installed, but removing the rogue YouTube solved it.
Had no issues for 2 months now

Question Help Desperately Needed - Random Reboots

So I posted about this previously but here's more info and a clearer summary
The Issue:
Phone randomly reboots about an average of once per day. Screen freezes, goes black, comes back on for 3 seconds still frozen, then proceeds to reboot. I've kept track and 100% of of the time this seems to happen when I'm typing. Initially I thought it was Textra, but it has happened in Snapchat, and Twitch whenever the google keyboard is up. Google sent a replacement phone and the issues persists, and I find it hard to believe that both phone would have the exact same hardware issue. Furthermore it very much seems like a software issue considering it ONLY happens when the google keyboard is up.
My hope is that someone might have encountered this and has a simple solution although I doubt it. Unfortunately since I don't have another phone, I have to wait to obtain one before I do a safe mode test. And even if I do it's not realistic for me to test it that way because I'd have to spend hours typing away just to try to get the issue to occur (since it's not frequent like every 5 minutes).
I'm suspecting some data or a setting is getting transferred over from my previous backup that's affecting google keyboard or something of the sort. My next step will be a factory reset, and then reinstalling everything bit by bit manually. Of course I have to link my google account, but I won't have it automatically restore the backup. If that doesn't help then I'm at a loss. At that point I'd probably pick up a cheap Pixel 2XL as my daily, and use my P6Pro in safe mode as much as I can to try to trigger the issue I guess?
The Phone:
Pixel 6 Pro
Not Rooted
November 5 Update
Set up done using my google account to restore all apps and settings, not cable
Remind me since I don't recall if it was brought up in your other thread about the issue, did you try Official Google Android Flash Tool yet?
Agree with edor, Android flash tool, flash both slots, start all over
roirraW edor ehT said:
Remind me since I don't recall if it was brought up in your other thread about the issue, did you try Official Google Android Flash Tool yet?
Click to expand...
Click to collapse
I have not tried this. What would this be used for?
ne0ns4l4m4nder said:
Agree with edor, Android flash tool, flash both slots, start all over
Click to expand...
Click to collapse
Not sure what that means sorry, can you elaborate?
MarkAnthony121 said:
I have not tried this. What would this be used for?
Click to expand...
Click to collapse
To wipe the phone and start back fresh.
MarkAnthony121 said:
Not sure what that means sorry, can you elaborate?
Click to expand...
Click to collapse
Just that. To start back fully fresh. Then if you do that take my advice from the other thread, don't restore backups from Google or anywhere, and initially only install your most critical apps. Once you determine you're not having the problem, install some more. Verify, repeat.
ne0ns4l4m4nder said:
Agree with edor, Android flash tool, flash both slots, start all over
Click to expand...
Click to collapse
Not sure what that means sorry, can you elaborate?
roirraW edor ehT said:
To wipe the phone and start back fresh.
Just that. To start back fully fresh. Then if you do that take my advice from the other thread, don't restore backups from Google or anywhere, and initially only install your most critical apps. Once you determine you're not having the problem, install some more. Verify, repeat.
Click to expand...
Click to collapse
Yes but I don't understand what "flash both slots" means. And wouldn't I get the same result by simply doing a factory reset and then proceeding with the method of installing everything manually and not from a backup? Why use the google flash tool vs factory reset?
MarkAnthony121 said:
Not sure what that means sorry, can you elaborate?
Yes but I don't understand what "flash both slots" means. And wouldn't I get the same result by simply doing a factory reset and then proceeding with the method of installing everything manually and not from a backup? Why use the google flash tool vs factory reset?
Click to expand...
Click to collapse
At this point, that's more information than you really need to know to try to fix your phone. I don't want to overcomplicate things. You can look at Google search results for "Pixel flash both slots" if you really want to go down that road right now.
Spoiler: Some of the details you're asking for, but you don't need right now
In short, starting with the Pixel 1 in 2016, they have two copies of almost everything (except only one copy of user data). On a Pixel, and another phone that employs dual slots, when you receive an OTA update, it updates the copy of Android that you're not currently running, then reboots into the one it just updated, and once rebooted it goes ahead and updates the copy that you're no longer running, so they're both now updated.
Not all OEMs use the dual partition strategy, which is frustrating. When I briefly had the Note 10+ before the P6P came out, I was amazed that Samsung still hasn't adopted the method. It beats the old style OTA method that Samsung still uses to this day as far as I know where it takes 15-20 minutes or more to run the update while your phone is unable to be used at all, and then even when it boots up the next time Android has to finish the job "optimizing" your apps for the new update. Dual partitions for Android save a lot of time when updating the phone.
In some manual flashing processes, you end up with one slot with a different copy of what you have in the other slot - and you don't want that. The slots are referred to as Slot A and Slot B.
I can go further into detail but you don't really need that to fix your phone.
All you need to know right now is Official Google Android Flash Tool.
If you haven't already tried the factory reset, et cetera, which we had recommended to you at least once in the other thread, then by all means, you can try that. But if you're going to try that, you might as well just use the Official Google Android Flash Tool and ensure you are 100% stock. Official Google Android Flash Tool has fixed a good dozen or two folks' issues (I haven't been keeping count) in these forums in the past 2+ months.
So if the factory resetting doesn't solve things then you'll still have to try Official Google Android Flash Tool to be closer to sure that you tried everything that you could. We had already suggested the Factory Reset to you in the other thread. Since you created a new thread, I figured you might be looking for information you hadn't been given yet.
So the short answer is because Official Google Android Flash Tool will do an even more complete job of putting your phone back to 100% stock, with a lot less doubt than a simple factory reset. Sure, a factory reset, in theory, should get you the same thing, but there are all sorts of circumstances where a factory reset won't. Something is wrong with your phone and we don't know what it is.
There's the Factory Reset idea and then there's the Official Google Android Flash Tool idea - either coupled with the staggered manual installation of apps until you narrow down if it was a particular app causing the issue. It doesn't matter which one you choose to try first. If you try just a Factory Reset, and things still go haywire, then you'll still have to try Official Google Android Flash Tool after that. It's your choice, now pick one and go forth and hopefully reboot no more.
Also, I wasn't going to mention this but I will now. Forums generally discourage users from creating multiple threads about the same issue or posting about the same issue in multiple threads. You can always update the OP (opening/first post) if you need to, and give an update as a reply to your existing thread.
MarkAnthony121 said:
So I posted about this previously but here's more info and a clearer summary
The Issue:
Phone randomly reboots about an average of once per day. Screen freezes, goes black, comes back on for 3 seconds still frozen, then proceeds to reboot. I've kept track and 100% of of the time this seems to happen when I'm typing. Initially I thought it was Textra, but it has happened in Snapchat, and Twitch whenever the google keyboard is up. Google sent a replacement phone and the issues persists, and I find it hard to believe that both phone would have the exact same hardware issue. Furthermore it very much seems like a software issue considering it ONLY happens when the google keyboard is up.
My hope is that someone might have encountered this and has a simple solution although I doubt it. Unfortunately since I don't have another phone, I have to wait to obtain one before I do a safe mode test. And even if I do it's not realistic for me to test it that way because I'd have to spend hours typing away just to try to get the issue to occur (since it's not frequent like every 5 minutes).
I'm suspecting some data or a setting is getting transferred over from my previous backup that's affecting google keyboard or something of the sort. My next step will be a factory reset, and then reinstalling everything bit by bit manually. Of course I have to link my google account, but I won't have it automatically restore the backup. If that doesn't help then I'm at a loss. At that point I'd probably pick up a cheap Pixel 2XL as my daily, and use my P6Pro in safe mode as much as I can to try to trigger the issue I guess?
The Phone:
Pixel 6 Pro
Not Rooted
November 5 Update
Set up done using my google account to restore all apps and settings, not cable
Click to expand...
Click to collapse
I've heard of freezing problems from others related to gboard. This would indeed appear to be a software flaw. I've never really used gboard since the first step for me was google-free AOSP, then put in my sim card and start using it (I don't like spyware).
Simplest solution for you would likely be to try a different soft keyboard. Personally, I would suggest finding one on f-droid rather than play store because open source.
For what it's worth, I've been using GBoard for 5+ years and have never had a problem.
96carboard said:
I've heard of freezing problems from others related to gboard. This would indeed appear to be a software flaw. I've never really used gboard since the first step for me was google-free AOSP, then put in my sim card and start using it (I don't like spyware).
Simplest solution for you would likely be to try a different soft keyboard. Personally, I would suggest finding one on f-droid rather than play store because open source.
Click to expand...
Click to collapse
I used to root back in the day and use a custom ROM. If I do that there's no automatic updates right? Have to reload a new ROM for updates?
MarkAnthony121 said:
I used to root back in the day and use a custom ROM. If I do that there's no automatic updates right? Have to reload a new ROM for updates?
Click to expand...
Click to collapse
Depends on the ROM. I believe GrapheneOS has OTA updates. I know some others over the years have had that, too. Certainly not most custom ROMs but some.
roirraW edor ehT said:
Depends on the ROM. I believe GrapheneOS has OTA updates. I know some others over the years have had that, too. Certainly not most custom ROMs but some.
Click to expand...
Click to collapse
Thanks for all the help. (sorry for posting twice, I tried to delete the other) And I did appreciate the extra info so that I understood WHY I needed to do it this way and how it all functions. Two final questions. On modern phones like this one, does running a custom rom really improve battery/performance much? It's already pretty snappy for me, so I feel if I don't care about customizability it's probably not worth the effort for minimal reward. And second question, will the flash tool give me the option to clear both slots ?
Oh and third, is it ok to link my google account, (to get my contacts and such) as long as I'm not restoring any backups from it?
MarkAnthony121 said:
Thanks for all the help. (sorry for posting twice, I tried to delete the other) And I did appreciate the extra info so that I understood WHY I needed to do it this way and how it all functions.
Click to expand...
Click to collapse
You're very welcome!
MarkAnthony121 said:
Two final questions. On modern phones like this one, does running a custom rom really improve battery/performance much?
Click to expand...
Click to collapse
In my opinion, no, but the object of some ROMs (like GrapheneOS) are more geared towards very much increased security and avoidance of all the Google data-collecting that goes on with everything Google, although you can use some or most Google apps with GrapheneOS if you choose.
I've never actually tried GrapheneOS, though - I've only kept up with the two threads about them because I was curious about it. To me, starting with my first Pixel (I never owned a Nexus device), I liked stock Android way better for my purposes.
But just as for a lot of phone-related subjects, the answer to this question is very subjective. What's right for me isn't right for everyone. Everyone's needs are different. The only way of knowing for sure is to try it. You might try something and very quickly say "to heck with that, I'm going back", or you might say "oh, I like this loads better". I'm not a betting man unless something is a near 100% chance, so it's really a toss-up whether you would like a different ROM or not.
Also, how I handle my battery works great for me - but it wouldn't for everyone. I don't charge the phone until it gets down to 25%, and I try not to let it get any lower than 25%. I only charge the phone up to 75% when I can. I never charge overnight, and I never quick charge. That 50% range of battery still lasts me about 24 hours. My Pixel 1 battery is in great shape because of this habit. My wife's, on the other hand, since she didn't do this - her battery on her old Pixel 1 is relatively shot.
MarkAnthony121 said:
It's already pretty snappy for me, so I feel if I don't care about customizability it's probably not worth the effort for minimal reward.
Click to expand...
Click to collapse
Sounds as if you already have made up your mind to me. I mean, that's how I feel, and I like using Google's services for the most part. I'm more a function over form person. While I don't want something downright fugly, I really don't care what things look like - only how they do what I want them to do. Yet again, "how they do what I want them to do" is very subjective. The Samsung Galaxy Note 10+ didn't do what my wife and I wanted it to do, but we were both spoiled on the Pixel 1 before that. We don't regret our choice to go back to Pixel via the 6 Pro. For others, the Samsung phones are what they need.
MarkAnthony121 said:
And second question, will the flash tool give me the option to clear both slots ?
Click to expand...
Click to collapse
You don't want to "clear" both slots, you want to flash both slots. In answer to your question, I don't think you'll have a choice via the site (or offline flashing the full factory image). In other words, both slots are going to get flashed whether you like it or not. You would have to go to extra efforts to *not* flash both slots. Hence yet another reason why you don't have to worry about that aspect.
Google's official methods would never flash only one slot by default. That would be just plain idiotic of them.
Before you ask, the reason I recommend the site rather than offline flashing of the full factory image is:
It's more user-friendly.
It has solved problems when manually flashing the full factory image has not for some others with particular problems.
MarkAnthony121 said:
Oh and third, is it ok to link my google account, (to get my contacts and such) as long as I'm not restoring any backups from it?
Click to expand...
Click to collapse
Yes, absolutely, although in some cases I've recommended going completely fresh and not even doing that, at least before testing long enough to see if you have the issue. You certainly could go without putting your Google account in, etc, but I don't feel that's warranted at this point. The only time I think you should do that, in this case, is if you do it the other way (with your Google account), and you still have the same problem right away (without installing any additional apps).
Just remember don't install any additional apps to start with, long enough to be sure that the problem isn't happening. I know it's a painful process - I've done this before on several devices for different reasons. Usually, the cause of issues becomes evident but it's possible it won't be completely obvious.
FYI, just putting your Google account in will, I believe, possibly still automatically restore your phone's most basic settings but I could be wrong about that. You could always try it without your account at first, use the phone in it's limited state for long enough to know there's no problem, and only then put your Google account in.

Categories

Resources