News Republic - HTC 10 Questions & Answers

Recently News Republic has started to display notifications. I don't use the app and don't use blinkfeed. Is there any way to stop it displaying them? I can't uninstall the app, I'm also unrooted
Sent from my HTC 10 using XDA-Developers mobile app

You can go into App Settings and Disable the app. That's what I have done.
Sent from my HTC6545LVW using Tapatalk

Configure the app per your preferences. I don't get notifications from it but I don't have it disabled; I did spend time setting all it's options to be quiet. (I only want notifications I specifically set, like reminders, or from other living, breathing people I know and nothing else.)
I prefer to use the minimum amount of force necessary...keeps other issues popping up at a minimum (like removing TouchPal can prevent you from decrypting your device on boot, as one example).

Rolo42 said:
Configure the app per your preferences. I don't get notifications from it but I don't have it disabled; I did spend time setting all it's options to be quiet. (I only want notifications I specifically set, like reminders, or from other living, breathing people I know and nothing else.)
I prefer to use the minimum amount of force necessary...keeps other issues popping up at a minimum (like removing TouchPal can prevent you from decrypting your device on boot, as one example).
Click to expand...
Click to collapse
Not to digress but removing TouchPal itself isn't what causes boot issues, it's not having a system installed keyboard. I uninstalled TouchPal day #1 and run HTC IME installed to system and there are not issues.
News Republic is bloatware, root and use titanium backup to remove it.
Sent from my HTC 10 using telepathy...

datafoo said:
Not to digress but removing TouchPal itself isn't what causes boot issues, it's not having a system installed keyboard. I uninstalled TouchPal day #1 and run HTC IME installed to system and there are not issues.
Click to expand...
Click to collapse
Hello, how did you do that? I am un-rooted and the only reason I do not uninstall (actually, disable) TouchPal is decryption upon boot. I use Google Keyboard.

errikosd said:
Hello, how did you do that? I am un-rooted and the only reason I do not uninstall (actually, disable) TouchPal is decryption upon boot. I use Google Keyboard.
Click to expand...
Click to collapse
You need root. If you search the forum you'll find all instructions you need to root.
Thete is a flashable zip with missing HTC apps and it includes HTC IME keyboard.
Sent from my HTC 10 using telepathy...

datafoo said:
You need root. If you search the forum you'll find all instructions you need to root.
Thete is a flashable zip with missing HTC apps and it includes HTC IME keyboard.
Sent from my HTC 10 using telepathy...
Click to expand...
Click to collapse
Yeah thought about it too. I was looking for a root-less way. I hope the N update brings another default keyboard so that I can at least disable TouchPal, but I highly doubt it. Thanks for the answer anyway.

errikosd said:
Yeah thought about it too. I was looking for a root-less way. I hope the N update brings another default keyboard so that I can at least disable TouchPal, but I highly doubt it. Thanks for the answer anyway.
Click to expand...
Click to collapse
We're way off topic but Nougat itself has nothing to do with what Keyboard is installed, that's an HTC choice. Whatever the HTC Bolt has is what we'll get for a keyboard and that's TouchPal if I'm not mistaken.
There is no harm in rooting unless you need Android Pay. Otherwise it's very easy and harmless.

datafoo said:
Not to digress but removing TouchPal itself isn't what causes boot issues, it's not having a system installed keyboard. I uninstalled TouchPal day #1 and run HTC IME installed to system and there are not issues.
News Republic is bloatware, root and use titanium backup to remove it.
Sent from my HTC 10 using telepathy...
Click to expand...
Click to collapse
I know that and that wasn't my point. My point was that changing things (i.e. removing TouchPal only--which is what I said) can cause problems. To troubleshoot, one must consider this and going back to baseline may be the most efficient route to diagnosis. Basically, asking, "Did I cause this?".
I also said, "can" cause problems, not "will"; I removed TouchPal and didn't install any other keyboard and my device booted just fine (in spite of the Viper installer warning). I got the SmartDial keypad to enter my bootup PIN, which I actually liked better.
Additionally, still removing TouchPal may cause other problems, depending on how much htc expects it to be there (dependencies). Given the potential downside with no potential upside to removing it, I don't; I just don't use it (aside from bootup). SwiftKey works just fine with TouchPal still installed.
So, to clarify, you are correct, not having a system keyboard can cause problems. TouchPal is the only system keyboard; ergo, removing TouchPal removes the only system installed keyboard.

Rolo42 said:
I know that and that wasn't my point. My point was that changing things (i.e. removing TouchPal only--which is what I said) can cause problems. To troubleshoot, one must consider this and going back to baseline may be the most efficient route to diagnosis. Basically, asking, "Did I cause this?".
I also said, "can" cause problems, not "will"; I removed TouchPal and didn't install any other keyboard and my device booted just fine (in spite of the Viper installer warning). I got the SmartDial keypad to enter my bootup PIN, which I actually liked better.
Additionally, still removing TouchPal may cause other problems, depending on how much htc expects it to be there (dependencies). Given the potential downside with no potential upside to removing it, I don't; I just don't use it (aside from bootup). SwiftKey works just fine with TouchPal still installed.
So, to clarify, you are correct, not having a system keyboard can cause problems. TouchPal is the only system keyboard; ergo, removing TouchPal removes the only system installed keyboard.
Click to expand...
Click to collapse
Removing TouchPal causes no known issues other than the needing a pin at boot and not having a system keyboard, unless as we've both agreed an alternate keyboard is installed. I understand you're speaking from speculation about potential issues but I'm speaking from actual experience as I flashed the HTC default keyboard as a system keyboard on both MM and N and have had zero issues directly or indirectly related.
Happy Holidays, hope your 2017 is fantastic.

datafoo said:
Removing TouchPal causes no known issues other than the needing a pin at boot and not having a system keyboard, unless as we've both agreed an alternate keyboard is installed. I understand you're speaking from speculation about potential issues
Click to expand...
Click to collapse
If by "speculation", you mean the users who posted the "potential issues" becoming a reality on their phones on this forum, then yes.
Installing an alternate keyboard isn't enough; it has to be a system keyboard.
My experience is that my phone presented the dial pad to enter my PIN after removing TouchPal but had SwiftKey installed (but not as system app). Had I set a password instead, I would have had to reformat/reflash from scratch.
Additionally, custom ROM installers provide a warning about this.

Related

[Q] HTC_IME_mod not working with Warm 2.2 release 5

I just recently reflashed to Warm 2.2 release 5 and now I can't get the warm themed HTC_IME_Mod to work. I have tried swype and other keyboards, but I still really prefer the customizable HTC_IME_MOD keyboard. All help on this will be much appreciated. I realize this has been brought up before, but no one seems to have addressed it yet.
flyboy780 said:
I just recently reflashed to Warm 2.2 release 5 and now I can't get the warm themed HTC_IME_Mod to work. I have tried swype and other keyboards, but I still really prefer the customizable HTC_IME_MOD keyboard. All help on this will be much appreciated. I realize this has been brought up before, but no one seems to have addressed it yet.
Click to expand...
Click to collapse
This could be a number of things! Beginning with the HTC IME mod.apk that you're trying to install not being signed to the rom itself.........What I would do is this!
Post this question in this thread
http://forum.xda-developers.com/showthread.php?t=793471
Is the thread for the rom you have flashed and you have a 99.9% chance of getting your question answered quickly!
Unfortunately I have not yet reached the "10 post requirement" to post in that forum yet... Also, multiple people asked similar questions on this subject in that particular thread and it was never addressed. I do appreciate your input though.
flyboy780 said:
I just recently reflashed to Warm 2.2 release 5 and now I can't get the warm themed HTC_IME_Mod to work. I have tried swype and other keyboards, but I still really prefer the customizable HTC_IME_MOD keyboard. All help on this will be much appreciated. I realize this has been brought up before, but no one seems to have addressed it yet.
Click to expand...
Click to collapse
What happens when you try to install it? Does it install and then not work or force close,or does it not install at all? You're rather vague, by saying "it doesn't work". Is it the keyboard that is linked in Myns first post? What are the steps you took to try installing it?
Sent from my PC36100 using XDA App
I used the update.zip listed on Myn's thread and installed it like any other flashable app. When I select it as the input source for my keyboard it begins to repeatedly force close without ever even displaying.
flyboy780 said:
I used the update.zip listed on Myn's thread and installed it like any other flashable app. When I select it as the input source for my keyboard it begins to repeatedly force close without ever even displaying.
Click to expand...
Click to collapse
Okay, got ya. Now I know where you stand. If I were presented with that problem, I would first try clearing cache and dalvik from recovery. If that doesn't fix it, I would uninstall the keyboard, reboot, wipe cache and dalvik, then try again. I've never had any issues with the keyboard before, but this is what id try if I did.
Sent from my PC36100 using XDA App
I will definitely give all of that a shot. Though this will come off as amatuerish, I'm going to ask anyways: How do I uninstall the keyboard? I have used Astro to locate the program, then selected it to open the app manager where I am presented with the option to uninstall it. I select unistall and it says that it is unable to uninstall. I can delete the update.zip, but that has no effect either. Also, does clearing the cache and dalvik have any negative impact on the ROM or any data from any of my other programs?
flyboy780 said:
I will definitely give all of that a shot. Though this will come off as amatuerish, I'm going to ask anyways: How do I uninstall the keyboard? I have used Astro to locate the program, then selected it to open the app manager where I am presented with the option to uninstall it. I select unistall and it says that it is unable to uninstall. I can delete the update.zip, but that has no effect either. Also, does clearing the cache and dalvik have any negative impact on the ROM or any data from any of my other programs?
Click to expand...
Click to collapse
To keep it simple, just reflashing the keyboard should over write itself, so no real need to actually uninstall I guess.
However if you did want to uninstall, you'll need a root level file explorer, preferably Root Explorer, but you can use ES file explorer as a free alternative if you don't have root explorer. The keyboard will be in the /system/app folder, as htc ime or something. Now, its possible that there could be some libs associated with the keyboard that need to be removed , but I wouldn't know without looking at the file. Either way, probably just reflash the keyboard after wiping cache and dalvik cache. That will be the easiest to try.
Also, you're sure the keyboard.you're using is for RLS5? I can't recall if there were compatibility issues between rls4 and rls5
Sent from my PC36100 using XDA App
Thanks for the quick responses. I'll just try reflashing after wiping the cache/dalvik as you suggested. I would not say that I am positive about the compatibility, The keyboard I'm attemting to install is listed in the optional add-ons for release 5 though. I know a few others had this problem, but I never saw any kind of response from Myn or anyone else regarding it. I'm trying to adapt to the swype keyboard, as it may be my only choice moving forward (short of reflashing back to release 4), but I find it somewhat awkward. I suppose with enough time I will get over it, but I would sure like to try to get the HTC IME mod back if possible...
flyboy780 said:
Thanks for the quick responses. I'll just try reflashing after wiping the cache/dalvik as you suggested. I would not say that I am positive about the compatibility, The keyboard I'm attemting to install is listed in the optional add-ons for release 5 though. I know a few others had this problem, but I never saw any kind of response from Myn or anyone else regarding it. I'm trying to adapt to the swype keyboard, as it may be my only choice moving forward (short of reflashing back to release 4), but I find it somewhat awkward. I suppose with enough time I will get over it, but I would sure like to try to get the HTC IME mod back if possible...
Click to expand...
Click to collapse
I hate the htc keyboard, lol I can't stand the arrows. I always hit them by accident. Even the one without the arrows sucks for me. Just don't like it. Have you tried any of the gingerbread keyboards? I like them better, and have an easier time typing on it. I suggest trying one out, if you haven't yet. Once im on my computer, I could give you a couple keyboards to try, or at least links to check out.
Sent from my PC36100 using XDA App
It worked! I really appreciate all the help!
flyboy780 said:
It worked! I really appreciate all the help!
Click to expand...
Click to collapse
Any time,
Awesome, glad to help! As a rule of thumb, to be safe, wipe cache and dalvik cache before you flash anything at all. I suggest a full wipe before flashing a rom, always.
Take care.
Sent from my PC36100 using XDA App
This keyboard does not have the dumb arrows either. Instead it lets you use gestures for several things (ie: shifting to/from CAPS, skipping to beginning/end of the word, hiding the keyboard) as well as the volume buttons on the side of the phone to move the cursor left/right. It also has a quick key for emoticons...(lame I know, but I use them often enough that it is very convenient). Again, thanks for the assistance!
flyboy780 said:
This keyboard does not have the dumb arrows either. Instead it lets you use gestures for several things (ie: shifting to/from CAPS, skipping to beginning/end of the word, hiding the keyboard) as well as the volume buttons on the side of the phone to move the cursor left/right. It also has a quick key for emoticons...(lame I know, but I use them often enough that it is very convenient). Again, thanks for the assistance!
Click to expand...
Click to collapse
You're welcome. And yup, I remember using that keyboard on myns, before I converted to the gb keyboard. I did like being able to use the volume rocker to move the cursor, that was convenient. I just love the scrollable toolbar on the gb keyboard, and the layout a bit better too. Thankfully there are tons of options with android, so everyone can use a keyboard that suits their own preference. Love choices.
Sent from my PC36100 using XDA App

[Q] Keyboard Keeps Resetting To Samsung 3

Maybe it's since the JB upgrade, but my keyboard keeps resetting to the Default Samsung 3, from Swiftkey 3. Could also have been from installing the Swiftkey Flow beta.
Anyone else experience this, and what can I do to stop it.
dratsablive said:
Maybe it's since the JB upgrade, but my keyboard keeps resetting to the Default Samsung 3, from Swiftkey 3. Could also have been from installing the Swiftkey Flow beta.
Anyone else experience this, and what can I do to stop it.
Click to expand...
Click to collapse
I think if you go to the buglist at swiftkey.net you'll find you aren't alone. I'm using the Swiftkey Flow beta and this problem hasn't occurred...yet. You can turn of the Flow feature and it becomes a regular Swiftkey keyboard.
I use Smart Keyboard Pro off of the market and the same thing keeps happening to me. By that I mean I don't use swype and my settings keeps rolling back to the regular keyboard.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
dratsablive said:
Maybe it's since the JB upgrade, but my keyboard keeps resetting to the Default Samsung 3, from Swiftkey 3. Could also have been from installing the Swiftkey Flow beta.
Anyone else experience this, and what can I do to stop it.
Click to expand...
Click to collapse
I've found that these problems can sometimes can be fixed by uninstalling and reinstalling the keyboard.
I did a factory reset and it still happened.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jeffdaman said:
I did a factory reset and it still happened.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Could you describe how this is happening? Does it switch keyboards after you use a certain app, or does it just switch at random times? One thing you could try is to disable all other keyboards under applications. This way, the phone has to keep using your keyboard.
Happens for me after a reboot. Always goes back to Samsung keyboard. Once I change to SwiftKey, it stays that way until the next reboot. As others have said, seems like a bug between JB and SwiftKey 3 (without Flow beta)
It happens every time I restart and then it would happen randomly while using the phone. I thing Task Manager by Rythm Soft was killing Smart Keyboard but I got it on the ignore list now; and so far it seems limited to the restart. It's not possible to disable Swype or the Samsung Keyboard. They are greyed out on the list.
To the O.P. you should check any task managers to be sure Swype isn't being killed.
MobileNick said:
Happens for me after a reboot. Always goes back to Samsung keyboard. Once I change to SwiftKey, it stays that way until the next reboot. As others have said, seems like a bug between JB and SwiftKey 3 (without Flow beta)
Click to expand...
Click to collapse
Same thing is happening to me. Always after a restart it falls back to the Samsung Keyboard.
If you guys are rooted make a back up of the Samsung keyboard then delete it. From system/app i know that worked on the early sprint JB leaks
Sent from my SGH-I747 using xda premium
brorex said:
If you guys are rooted make a back up of the Samsung keyboard then delete it. From system/app i know that worked on the early sprint JB leaks
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Anyone try this, and what does it default to if you do remove the Samsung Keyboard? I have several inputs, WiiMote, PS3, etc. If I have to keep changing the default back to Swiftkey, then this option would get annoying.
Known Bug with Work-Around
dratsablive said:
Maybe it's since the JB upgrade, but my keyboard keeps resetting to the Default Samsung 3, from Swiftkey 3. Could also have been from installing the Swiftkey Flow beta.
Anyone else experience this, and what can I do to stop it.
Click to expand...
Click to collapse
This is a known bug with JB 4.1.x.....
Swiftkey has it mentioned in a bug list as well as Google in a bug list...
It has something to do with apps getting installed differently and storing app data differently with JB. When a phone reboots the storage location for that app's data is not mounted or available right away so the app can't load and therefore the phone switches to the default keyboard.
Happens with a few other apps like AT&T Vooicemail Viewer.
The work-around is to root the phone, backup the app with Titanium Backup, uninstall the app, then restore it without data. Then set the keyboard as default and it should stay that way after re-boots.
Good luck!
Boomer6345 said:
This is a known bug with JB 4.1.x.....
Swiftkey has it mentioned in a bug list as well as Google in a bug list...
It has something to do with apps getting installed differently and storing app data differently with JB. When a phone reboots the storage location for that app's data is not mounted or available right away so the app can't load and therefore the phone switches to the default keyboard.
Happens with a few other apps like AT&T Vooicemail Viewer.
The work-around is to root the phone, backup the app with Titanium Backup, uninstall the app, then restore it without data. Then set the keyboard as default and it should stay that way after re-boots.
Good luck!
Click to expand...
Click to collapse
Might wait for Google or Swiftkey to fix the bug. If I restore without the data, then I lose all the words Swiftkey has learned.
This is really odd. A few weeks ago I downloaded the SwiftKey Flow Beta and this problem disappeared. That is, after a reboot my default keyboard would stay on SwiftKey Flow Beta. But yesterday SwiftKey released the official version 4 with Flow integrated. And now the problem is back - reboot makes Samsung Keyboard as default.
So what did the Beta do that was so special that it would stay after a reboot??
MobileNick said:
This is really odd. A few weeks ago I downloaded the SwiftKey Flow Beta and this problem disappeared. That is, after a reboot my default keyboard would stay on SwiftKey Flow Beta. But yesterday SwiftKey released the official version 4 with Flow integrated. And now the problem is back - reboot makes Samsung Keyboard as default.
So what did the Beta do that was so special that it would stay after a reboot??
Click to expand...
Click to collapse
Same. Reboot causes the problem. Not a huge issue, but odd.
cfn87 said:
Same. Reboot causes the problem. Not a huge issue, but odd.
Click to expand...
Click to collapse
It's a change in the way Jellybean handles how Google Play apps are loaded during boot process, since they happen after the keyboard gets loaded, it reverts to default.
Boomer6345 said:
This is a known bug with JB 4.1.x.....
Swiftkey has it mentioned in a bug list as well as Google in a bug list...
It has something to do with apps getting installed differently and storing app data differently with JB. When a phone reboots the storage location for that app's data is not mounted or available right away so the app can't load and therefore the phone switches to the default keyboard.
Happens with a few other apps like AT&T Vooicemail Viewer.
The work-around is to root the phone, backup the app with Titanium Backup, uninstall the app, then restore it without data. Then set the keyboard as default and it should stay that way after re-boots.
Good luck!
Click to expand...
Click to collapse
correct. since the play store installs apps in a location (on your JB device) that is not immediately scanned during the first part of boot up, thats why the stock keyboard is loaded. however, to fix this on my wife's unrooted/stock S3, i found the actual swiftkey apk then downloaded and installed it onto the phone. this placed the apps info in the correct storage location that is seen on boot up. i do not condone downloading apps you have not paid for however i did this for her as she and i have both paid for swiftkey on all our phones/tablets when it initially released on the play store. i dont have this swiftkey issue on my s3 as it is running a custom rom. cheers
xBeerdroiDx said:
correct. since the play store installs apps in a location (on your JB device) that is not immediately scanned during the first part of boot up, thats why the stock keyboard is loaded. however, to fix this on my wife's unrooted/stock S3, i found the actual swiftkey apk then downloaded and installed it onto the phone. this placed the apps info in the correct storage location that is seen on boot up. i do not condone downloading apps you have not paid for however i did this for her as she and i have both paid for swiftkey on all our phones/tablets when it initially released on the play store. i dont have this swiftkey issue on my s3 as it is running a custom rom. cheers
Click to expand...
Click to collapse
Where would this location be?
dratsablive said:
Where would this location be?
Click to expand...
Click to collapse
via a google search
MobileNick said:
This is really odd. A few weeks ago I downloaded the SwiftKey Flow Beta and this problem disappeared. That is, after a reboot my default keyboard would stay on SwiftKey Flow Beta. But yesterday SwiftKey released the official version 4 with Flow integrated. And now the problem is back - reboot makes Samsung Keyboard as default.
So what did the Beta do that was so special that it would stay after a reboot??
Click to expand...
Click to collapse
Sorry if this was already covered...but I read a post at the Swiftkey site that the issue is with Paid apps on JB. Not all paid apps of course...but some paid apps like Swiftkey install to this special storage location that is not available soon enough during the boot process.
The 4.x Swiftkey beta was not a paid app so it worked...now that the beta is released it is a paid app and the Swiftkey 4.x release in Google Play has the issue again on JB just like 3.x did.

Samsung keyboard leaves phones hackable

Anyone read about this yet? I read about it in the guardian. It seems the chances are fairly slim if you watch what networks you connect to, but i would still prefer to have this issue fixed. Since i am running a custom rom without knox, i will not get any fix OTA. Any ideas for custom rom users?
For reference:
http://www.theguardian.com/technology/2015/jun/17/samsung-keyboard-bug-android-hack
http://arstechnica.com/security/201...ng-galaxy-phones-into-remote-bugging-devices/
I'm paranoid; I found /system/app/ SamsungIME and /system/lib/libswiftkeysdk-java.so and moved them permanently to ExtSdCard/downloads just for safekeeping. I looked for other files associated in /data/data and /data/dalvik-cache but found none. Rebooted with no issue; just don't try to select swiftkey as default in Settings/Language and input.
IDK how this swiftkey dictionary update works so I'm thinking there's still some or all security vulnerability. Anyone know? I searched pages of Google Search but currently filled with vulnerability issue and updates.
No Knox here either. I've long used Swype paid customized with top number row. Had no idea the swiftkey dictionary was updating in the background despite not being the default dictionary.
Sent from my SM-N910P using Tapatalk
Since most of us on xda have root, just wipe data and uninstall it with titanium backup. I'm maybe thinking user dictionary should be wiped and uninstalled. I'll back both up and check if everything is ok. It's no skin off my back, I've used Swype since it first appeared on android and that has its own dictionary it backs up.
I also could be wrong and uninstalling these may not prevent anything. But these are still parts of the rom that are not needed for me and hasn't hurt anything yet.
If any devs could chime in if they know that would be great.
Just decided to freeze the dictionary. Wasn't but 52 kB of data, 12kB cache there per application manager.
Sent from my SM-N910P using Tapatalk

TouchPal keyboard

I've got 2 issues, prediction keeps switching itself off all the time, and I just cannot get curve (swype) to work despite trying every combination of TouchPal settings, any ideas?
Sent from my HTC 10 using XDA-Developers mobile app
I couldnt stand touchpal. I use google keyboard and deleted touchpal and all its lanugage packs, skins etc (requires root). Much better now.
Just found solution to Swype, you have to update the language as htc only included basic language.
Sent from my LG-D855 using XDA-Developers mobile app
Holding off on root, but its killing me as no proper app backup solution, need to read up as htc is sooo different to sammy/lg
Sent from my LG-D855 using XDA-Developers mobile app
gsw5700 said:
Holding off on root, but its killing me as no proper app backup solution, need to read up as htc is sooo different to sammy/lg
Sent from my LG-D855 using XDA-Developers mobile app
Click to expand...
Click to collapse
You probably already know about this but to back up my app data I used helium from clockwork mod. It doesn't require root and all you need to do is enable USB debugging. That's what I used to back up my game data and other things when I switched from my one m9 to the 10.
For my call logs and text messages I used SMS backup and restore which worked flawlessly. The only thing left to do after that was to export my contacts to my SD card and I was set to go. It took me about 25 minutes to get everything up and going on the new phone not including system updates and application updates of course which you can't avoid
I hope that helps out some
Thanks, I am aware of helium but thought it may be a bit of a hassle. I'm used to titanium backup, LG has its own awesome backup utility.
Not too sure about flashing twrp/root yet as it stops OTA updates. So left with custom rom and wait for that rom to get OTA included. Looking forward to custom roms, custom kernel, heavy debloating, easy backup and restore. Still not sure how you flash HTC 10 back to stock!
Sent from my HTC 10 using XDA-Developers mobile app
gsw5700 said:
Thanks, I am aware of helium but thought it may be a bit of a hassle. I'm used to titanium backup, LG has its own awesome backup utility.
Not too sure about flashing twrp/root yet as it stops OTA updates. So left with custom rom and wait for that rom to get OTA included. Looking forward to custom roms, custom kernel, heavy debloating, easy backup and restore. Still not sure how you flash HTC 10 back to stock!
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
In my experience helium is not a hassle to use at all. If you've never used it before you basically turn on USB debugging install the app from the play store and install the application from the website on your computer. After you do that plug your phone into your computer and launch the application on your phone. It then comes up with a list of all the applications on your phone, you can either press select all or individually select the applications you would like to back up. Once you do that you push a button and a few moments later everything is done.
One thing to note is that it creates a folder named carbon on the root of the internal storage of the phone, just remember to move that folder over to your SD card before you start experimenting with anything that may require wiping the phone. I have used titanium backup in the past as well and while the helium method may not be just as easy it is the absolute best solution out there for people that don't already have a rooted device
dabbler77 said:
I couldn't stand touchpal. I use google keyboard and deleted touchpal and all its lanugage packs, skins etc (requires root). Much better now.
Click to expand...
Click to collapse
Just a heads up. Do not delete TouchPal like i did. My phone asked for the password for encrypted data at boot - it hadn't loaded the google keyboard, and as I deleted touchpal from system I had no keyboard! Only option was to restore. I've now left touchpal (minus all the language packs) in my rom, for some reason Google keyboard couldn't be moved to system. Oh well.
Hi I'm using Swiftkey but tried many keyboard. All are giving me a problem in the p button and keyboard being too sensitive. It types the same letter three times. Can anyone help
himesh82 said:
Hi I'm using Swiftkey but tried many keyboard. All are giving me a problem in the p button and keyboard being too sensitive. It types the same letter three times. Can anyone help
Click to expand...
Click to collapse
Hello,
I am an official moderator from SwiftKey, can you go to our community to post your issue?
Appreciate!
Alpert
---------- Post added at 09:52 AM ---------- Previous post was at 09:50 AM ----------
dabbler77 said:
Just a heads up. Do not delete TouchPal like i did. My phone asked for the password for encrypted data at boot - it hadn't loaded the google keyboard, and as I deleted touchpal from system I had no keyboard! Only option was to restore. I've now left touchpal (minus all the language packs) in my rom, for some reason Google keyboard couldn't be moved to system. Oh well.
Click to expand...
Click to collapse
Oh buddy, that's sad...
Just do not activate TouchPal in language&keyboard menu?
dabbler77 said:
Just a heads up. Do not delete TouchPal like i did. My phone asked for the password for encrypted data at boot - it hadn't loaded the google keyboard, and as I deleted touchpal from system I had no keyboard! Only option was to restore. I've now left touchpal (minus all the language packs) in my rom, for some reason Google keyboard couldn't be moved to system. Oh well.
Click to expand...
Click to collapse
Yeah. Disable touchpal doesn't stop force install on language packs. I'm disappointed there's no option to remove this on play store.
Sent from my HTC 10 using Tapatalk

Screen Overlay Detected

If this is in the wrong thread then please move to correct one.
Has anyone else had issues with this... I'll call it problem, but by the way it behaves, it seems more like its a bug.
It has only been something I've seen on Marshmallow. Try to install an app, and its 50/50 whether or not you get "screen overlay detected"
Try to give an app permission, "screen overlay detected".
I should also point out that it isnt just restricted to HTC. My partners (now apparently ticking time bomb) s7 has also had the issue
You can disable as many screen overlays as you like, it still doesnt go away.
I've noticed now, too, that anytime a chat head from facebook messenger is on screen when I try to do something like install an app, it will spit out that problem until I close the chat head. Which was never an issue, ever, before.
Where has this thing come from and why is it even a problem for Android?
Those chat heads on the messenger as well as light filters, as e.g. CF.lumen, are always screen overlays. Those overlays could read out the whole screen, and thus as well what you're typing into banking apps or similar. Thus Google updated the privacy policy of their devices in Marshmallow, ending up in this specific error message. Sometimes it's enough to just turn the screen overlay of via settings > apps, regarding Apps like FB Messenger, CF.lumen, and the like, on other times and Apps you got to reboot the device after done so, or disable the overlay within the Apps settings as well, and seldomly you got to uninstall such an App to get the problem sorted for the time being. At least that's what I could find out searching the web.
Sent from my htc_pmeuhl using XDA Labs
silegeek said:
Where has this thing come from and why is it even a problem for Android?
Click to expand...
Click to collapse
It's so malicious apps don't replace the install button with something else (like an install button to install something else).
It's quite clever if you think about it.
Lambo_car16 said:
It's so malicious apps don't replace the install button with something else (like an install button to install something else).
It's quite clever if you think about it.
Click to expand...
Click to collapse
In theory I would say it's clever. In practice, it doesn't distinguish between safe apps that are harmless and those that aren't.
silegeek said:
In theory I would say it's clever. In practice, it doesn't distinguish between safe apps that are harmless and those that aren't.
Click to expand...
Click to collapse
How does the system know if an app is safe or not..?
Sent from my E6653 using Tapatalk
Lambo_car16 said:
How does the system know if an app is safe or not..?
Click to expand...
Click to collapse
Since Facebook messenger (and pretty much all my apps, most of which don't even have screen overlays but are in the list for it) was downloaded from Google play, I would imagine it isn't difficult to implement a system that flags it as safe.
If an app is installed via an apk, even if it is safe, I would understand more the need for concern. You never know, etc.
silegeek said:
Since Facebook messenger (and pretty much all my apps, most of which don't even have screen overlays but are in the list for it) was downloaded from Google play, I would imagine it isn't difficult to implement a system that flags it as safe.
If an app is installed via an apk, even if it is safe, I would understand more the need for concern. You never know, etc.
Click to expand...
Click to collapse
It would be difficult to implement a system like that. You never know which app is fake or real. Maybe it was a modified version of the app, you'll never know.
Either way, the feature is there and if you want to install an app just quickly turn off your overlay. Not exactly a big problem.
Sent from my E6653 using Tapatalk

Categories

Resources