I have been searching for a solution to this forever, but cannot find one. I want to completely and utterly remove the Touchwiz lockscreen and replace it with the stock one. I know it is doable as I found instructions for how to do it, but they were unfortunately rather over my head. Is there an easy way to do this?
Please note, I am not talking about simply disabling it and replacing it with some third-party unit from the play store. I'm talking mucking around in the /system folder and deleting it entirely.
Thanks.
Could you link the information ???
That would help the group understand what you are looking at. ..
And allow us to help you more. ..
These guys are sharp...and may recognize the procedure by sight. ..g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
captainradish said:
I have been searching for a solution to this forever, but cannot find one. I want to completely and utterly remove the Touchwiz lockscreen and replace it with the stock one. I know it is doable as I found instructions for how to do it, but they were unfortunately rather over my head. Is there an easy way to do this?
Please note, I am not talking about simply disabling it and replacing it with some third-party unit from the play store. I'm talking mucking around in the /system folder and deleting it entirely.
Thanks.
Click to expand...
Click to collapse
That IS the stock lock screen....do you mean you want aosp lock screen?
Sent from my iPad using Tapatalk
captainradish said:
I have been searching for a solution to this forever, but cannot find one. I want to completely and utterly remove the Touchwiz lockscreen and replace it with the stock one. I know it is doable as I found instructions for how to do it, but they were unfortunately rather over my head. Is there an easy way to do this?
Please note, I am not talking about simply disabling it and replacing it with some third-party unit from the play store. I'm talking mucking around in the /system folder and deleting it entirely.
Thanks.
Click to expand...
Click to collapse
To answer your question, no, it's not this easy. Lockscreen simply does not fall into a certain file or folder. It is tied into framework-res, SystemUI, and Settings.apk. Removing as much as you can will likely break Android OS as this is a system level thing and is tightly integrated. Your only option is disabling. If you can't disable it thru settings, where you set it to none but it's still slide to unlock, you can use Tasker and an on-boot profile to disable keyguard action. That will cause your device to show launcher when you click power button.
Hope this helps,
Sent from my HTCONE using XDA Free mobile app
Related
I just want the old way of swiping into camera, unlock and google now.
the new swipe into camera is noticeably slower than the old method.
found a mod for GSM nexus but not for LTE nexus
poena said:
I just want the old way of swiping into camera, unlock and google now.
the new swipe into camera is noticeably slower than the old method.
found a mod for GSM nexus but not for LTE nexus
Click to expand...
Click to collapse
Yes...I honestly dont like 4.2 at all. Kinda sux really. I dont like the quicksettings and I think the lockscreen is a step backwards...if I wanted lockscreen widgets Id buy widgetlocker.
Im still using 4.1.2 because of the sdcard crap that is going on with 4.2. I have no idea why google named the sdcard 0. Thats pretty stupid when it comes to compatibility and upgrading software. Something so simple causes so much probs. Ive had all my current sdcard stuff moved to /data/media...which it cannot be read from there (ie like gallery, etc). So...I manually move it back to sdcard...and it ruins all my pictures..0 byte jpgs...gray images...thanks google.
That and I couldnt tell you how many duplicate places there is for the sdcard. /storage/emulated0..../storage/legacy.../sdcard/0.../data/media...and having duplicate gobledy gook everywhere.
So...Im with you on the lockscreen...but not just that...its much worse.
edit: while Im at it I may as well just gripe about the kernels lately. All of them have jacked up wifi for me. I have no idea why...my wifi stalls all the time since the 3.0.49 branch. No dev has worked them out yet. I get dropped connections all the time....I get stalls (which I have blue connectivity (full bars)...and pages wont load...its just kinda stuck there in lingo with the incoming/outgoing arrows toggling back and forth....then sometimes it will load after 30 seconds...sometimes a minute or more. Ive had to disconnect wifi...turn it back on. Ive tried every kernel...every new release...everything from tons of different devs...they all do it. The only one that doesnt do it is tiny's. But...tiny kernel doesnt multitask for me well. I get major lag backing out of apps...if I have mulitiple processes going on...its stalling too (UI at least). Honestly its gotten so annoying that It makes me want to throw my phone against the wall.
yakitori2 said:
I dont like the quicksettings and I think the lockscreen is a step backwards...if I wanted lockscreen widgets Id buy widgetlocker.
Click to expand...
Click to collapse
Yeah, they just didn't speed anything up for me. It was like when Microsoft puts yet another meaningless dialog between you and the setting you want to change.
The lock screen is baffling. The whole point of a lock screen is to lock the phone. Not provide another launcher. That, and it just behaves strangely.
About the lock screen rant: disable it with lock screen policy app from play store.
About the SD card rant: done for multi user compatibility and you wont have an issue if you didn't wipe out the special file with your old recovery
Sent from my Google Nexus
MordyT said:
About the lock screen rant: disable it with lock screen policy app from play store.
About the SD card rant: done for multi user compatibility and you wont have an issue if you didn't wipe out the special file with your old recovery
Sent from my Google Nexus
Click to expand...
Click to collapse
actually i DID have an issue. I didnt wipe specific files with my old recovery. I did like I always do...wiped cache...factory reset..format system...flash new rom. 4.2 MOVES your current sdcard contents to /data/media on the rom I flashed....and not only did it move them there...it "blanked" them. All of my apks were not parsed properly...and all my jpgs were 0 byte files that were empty. Nandroid restore did not restore my pictures because it doesnt effect /data/media.....which is where the 4.2 flash moved my stuff in the first place. It turned my pics in to 0 byte files which were all still present...only they were empty files. Restore didnt fix it...twrp latest. Moving them back to /sdcard didnt fix it either.
yakitori2 said:
actually i DID have an issue. I didnt wipe specific files with my old recovery. I did like I always do...wiped cache...factory reset..format system...flash new rom. 4.2 MOVES your current sdcard contents to /data/media on the rom I flashed....and not only did it move them there...it "blanked" them. All of my apks were not parsed properly...and all my jpgs were 0 byte files that were empty. Nandroid restore did not restore my pictures because it doesnt effect /data/media.....which is where the 4.2 flash moved my stuff in the first place. It turned my pics in to 0 byte files which were all still present...only they were empty files. Restore didnt fix it...twrp latest. Moving them back to /sdcard didnt fix it either.
Click to expand...
Click to collapse
That's something different. Moving files won't corrupt them. This is not recovery related.
I am using lockscreen policy to disable widgets but I need to be able to swipe into camera. so I had to leave that.
poena said:
I just want the old way of swiping into camera, unlock and google now.
the new swipe into camera is noticeably slower than the old method.
found a mod for GSM nexus but not for LTE nexus
Click to expand...
Click to collapse
I like it but opening the camera is kinda laggy and too slow for me. And also the messaging widget should be able to send the texts straight from the lockscreen instead of going into the messaging app first! But the idea of widgets on lock screen is pretty cool!
yakitori2 said:
actually i DID have an issue. I didnt wipe specific files with my old recovery. I did like I always do...wiped cache...factory reset..format system...flash new rom. 4.2 MOVES your current sdcard contents to /data/media on the rom I flashed....and not only did it move them there...it "blanked" them. All of my apks were not parsed properly...and all my jpgs were 0 byte files that were empty. Nandroid restore did not restore my pictures because it doesnt effect /data/media.....which is where the 4.2 flash moved my stuff in the first place. It turned my pics in to 0 byte files which were all still present...only they were empty files. Restore didnt fix it...twrp latest. Moving them back to /sdcard didnt fix it either.
Click to expand...
Click to collapse
Is this not caused by using a recovery not designed for 4.2? I thought the new recovery's fixed the issues.
poena said:
I am using lockscreen policy to disable widgets but I need to be able to swipe into camera. so I had to leave that.
Click to expand...
Click to collapse
You've hit on the exact reason why the new lock screen is an improvement. Apparently you don't use any security on your lockscreen, but for those who do there was no way to get to your camera before. The new lockscreen may not be perfect, but it's a huge improvement.
Yep and I made a poll about this. Most people want to be able to disable it natively.
http://forum.xda-developers.com/showthread.php?t=2023434
pfmiller said:
You've hit on the exact reason why the new lock screen is an improvement. Apparently you don't use any security on your lockscreen, but for those who do there was no way to get to your camera before. The new lockscreen may not be perfect, but it's a huge improvement.
Click to expand...
Click to collapse
yup
currently not using any security measures.
Sdobron said:
That's something different. Moving files won't corrupt them. This is not recovery related.
Click to expand...
Click to collapse
I never said it was recovery related. I'm stating what happened when I went to 4.2. How could you prove anything or what caused it. You weren't there. You haven't seen any data or logs. Yet you state your opinion as fact.
I'm stating my opinion of 4.2.+ is don't like the new features... at least not all. Multiple users is cool. Lock screen and quick settings sucks. I'm entitled to my opinion just as others who like it.
Anyone remember one of the original reasons for "locking" phones? To prevent accidental activation. This new lock screen bypass really opens up a hole there. It's not improbable that someone can start the camera and burn down their battery really fast.
haydonxda said:
Anyone remember one of the original reasons for "locking" phones? To prevent accidental activation. This new lock screen bypass really opens up a hole there. It's not improbable that someone can start the camera and burn down their battery really fast.
Click to expand...
Click to collapse
I suppose that pockets conduct electricity now?
haydonxda said:
Anyone remember one of the original reasons for "locking" phones? To prevent accidental activation. This new lock screen bypass really opens up a hole there. It's not improbable that someone can start the camera and burn down their battery really fast.
Click to expand...
Click to collapse
I think the original reason was to prevent butt dialing. Nowadays with so much personal information on phones security is a major reason too. Accidentally running down the battery in the rare situation where your junk accidentally slides open the camera is not a serious concern in my book.
haydonxda said:
Anyone remember one of the original reasons for "locking" phones? To prevent accidental activation. This new lock screen bypass really opens up a hole there. It's not improbable that someone can start the camera and burn down their battery really fast.
Click to expand...
Click to collapse
That's why there's new forms to lock your phone(pin, passwords, etc). You still can't get into the phone if you have it pin/password protected.
For the haters of the new lockscreen-
To clarify a bit with an example: I have my phone pin protected with the messaging widget. I can still see the texts I have in the messaging widget, but when I click to view one, it asks for my pin. Now, if I go to the camera app, if I swipe towards the right, I get a lock icon. If I click on Home, I get asked for my pin.
Now, what's the issue? Aside from just not liking a different implementation.
As for swiping up to get to Now, you still do that. The anchor is just a bit lower now.
Sent from my Galaxy Nexus using xda premium
DirgeExtinction said:
That's why there's new forms to lock your phone(pin, passwords, etc). You still can't get into the phone if you have it pin/password protected.
Click to expand...
Click to collapse
But you can activate the phone. And you can bypass security.
Okay, there are two reasons to have a locking mechanism:
1) accidental activation
2) security
The rationale for #1 was largely "butt dialing". Today, instead of burning cell minutes and battery now you can just find yourself with a flat battery. You can now activate the phone without entering in a proper lock code. You can't bypass the security aspect of it but you can now burn down your battery rapidly by accidentally turning on the camera.
The rationale for #2 is to keep prying eyes away from your device and/or attempt to stop someone else from putting cell charges on your bill. But you can put widgets on the screen that display MMS and email.
It's like having two layers of locking. That in itself isn't terrible but what kills the idea is #1 above.
DirgeExtinction said:
That's why there's new forms to lock your phone(pin, passwords, etc). You still can't get into the phone if you have it pin/password protected.
For the haters of the new lockscreen-
To clarify a bit with an example: I have my phone pin protected with the messaging widget. I can still see the texts I have in the messaging widget, but when I click to view one, it asks for my pin. Now, if I go to the camera app, if I swipe towards the right, I get a lock icon. If I click on Home, I get asked for my pin.
Now, what's the issue? Aside from just not liking a different implementation.
As for swiping up to get to Now, you still do that. The anchor is just a bit lower now.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That you have no control about what information is exposed if you put the widgets on the lockscreen. What if someone emails/messages you a password of a kind or something and its visible in the list ? Lets hope Google polishes it for next major release.
Running 4.1.2 now.
4.2 sucks.
Ugly lock screen
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
madd0g said:
That you have no control about what information is exposed if you put the widgets on the lockscreen. What if someone emails/messages you a password of a kind or something and its visible in the list ? Lets hope Google polishes it for next major release.
Click to expand...
Click to collapse
+1
I hate to bring this up, but no one ever figured anytging about it. Anyways, the stock Samsung keyboard pretty much stopped auto correcting and having issues with a quarter of us who did the ota update to the version previous to lj7, before rooting that is. Now that I'm rooted, after several different ROMs, I can confirm that it's something deeper than what ROMs change.
As in something deeper I mean it's something that doesn't change from ROM to ROM and it remains there no matter what and is completely untouched by common updates. Only 1 happened to corrupt or break it in some way.
Does anyone have a clue of what could be causing this?
Please don't throw the standard nooby trouble shooting questions like factory reset, memory format, flash a different ROM, try to uninstall Samsung keyboard and reinstall a different version of it, just get a 3rd party app, etc. Done it all.
To be clear the issue is only on Samsung keyboards, I just want to find the underlying issue. If I was to go digging around blind in very base system files, I would probably brick my phone. Does any ideas cross anyone's mind besides giving up
Samsung's keyboard has autocorrect disabled it only does suggestions. You need to mod the app to actually get it to insert the words for you.
I like to break stuff!
-EViL-KoNCEPTz- said:
Samsung's keyboard has autocorrect disabled it only does suggestions. You need to mod the app to actually get it to insert the words for you.
I like to break stuff!
Click to expand...
Click to collapse
No its not lol. stock when i got it, for months it had auto correct, then i got an ota, and updated, and it broke. samsung didnt do it on purpose. I emailed them awhile back. Only said it would be fixed in the next update.. 3 later, NOPE..
ReapersDeath said:
No its not lol. stock when i got it, for months it had auto correct, then i got an ota, and updated, and it broke. samsung didnt do it on purpose. I emailed them awhile back. Only said it would be fixed in the next update.. 3 later, NOPE..
Click to expand...
Click to collapse
Yeah actually it is and has been since JB. You can decompile the keyboard apk and change the false value to true and activate autocorrect then recompile it. We've been doing it on the note 2 for a while now since by default the option is disabled at the code level.
Edit: here's the instructions to enable autocorrect and shorten the longpress delay http://forum.xda-developers.com/showthread.php?t=2093588
I like to break stuff!
-EViL-KoNCEPTz- said:
Yeah actually it is and has been since JB. You can decompile the keyboard apk and change the false value to true and activate autocorrect then recompile it. We've been doing it on the note 2 for a while now since by default the option is disabled at the code level.
Edit: here's the instructions to enable autocorrect and shorten the longpress delay http://forum.xda-developers.com/showthread.php?t=2093588
I like to break stuff!
Click to expand...
Click to collapse
Jb is a **** for that >=( Was all fine until pre jb
Edit: Odd. under system/csc Features.XML, at the very bottom is the option to enable auto correct ( AutoCorrectionDisabled>true< ) i changed that to false and restarted but sadly no change.. =( i searched through the samsungIME.apk and i couldnt really find anything to disable or re-enable =/ Only a bunch of code id have to put in or just replace my apk with the attached which just rapidly force closes on me.
ReapersDeath said:
Jb is a **** for that >=( Was all fine until pre jb
Click to expand...
Click to collapse
I'm pretty sure it has to do with Samsung's licensing from swiftkey, basically swiftkey wants you to buy the extra features on their keyboard, and only licensed samsung to use basic features such as slide to type and predictions, but not theming and extra features like autocorrect and delay time adjustment etc. Actually the newest swiftkey is identical to Samsung's keyboard only has more features and Samsung has all the code in the keyboard most of it is just disabled by default in the code, bunch of false statements added in to null them out in the settings
I like to break stuff!
Re read, made a big edit and didn't see you replied when I was editing XD
Sent from my SPH-L710 using xda app-developers app
ReapersDeath said:
Re read, made a big edit and didn't see you replied when I was editing XD
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Look thru the thread I linked ^^ there and you'll find the code that need to be replaced or edited to get it all working. It's a little bit of a pain(or was) cuz the directions weren't entirely specific about which lines some of the edits were on. I ended up using the search feature in notepad++ to hunt out the lines to change or add. You could try pushing a note 2 keyboard into /system and set permissions on it, but back up your keyboard first incase the notes doesn't work. There's a bunch of themed ones with the AC and longpress mods over in the themes and apps section for sprints note 2. I think your rom needs to be deodexed for them to work. Just don't flash them cuz the updater script is for the note, extract the KB from the zip with something like ES file explorer and then copy it into system and set permissions to rw-r-r and rename your KB to samsungime.bak then reboot. If the note KB does the FC dance just rename your keyboard back to SamsungIME.apk and delete the note KB and reboot, or makesure you have a 3rd party KB installed for emergency use.
I like to break stuff!
-EViL-KoNCEPTz- said:
Look thru the thread I linked ^^ there and you'll find the code that need to be replaced or edited to get it all working. It's a little bit of a pain(or was) cuz the directions weren't entirely specific about which lines some of the edits were on. I ended up using the search feature in notepad++ to hunt out the lines to change or add. You could try pushing a note 2 keyboard into /system and set permissions on it, but back up your keyboard first incase the notes doesn't work. There's a bunch of themed ones with the AC and longpress mods over in the themes and apps section for sprints note 2. I think your rom needs to be deodexed for them to work. Just don't flash them cuz the updater script is for the note, extract the KB from the zip with something like ES file explorer and then copy it into system and set permissions to rw-r-r and rename your KB to samsungime.bak then reboot. If the note KB does the FC dance just rename your keyboard back to SamsungIME.apk and delete the note KB and reboot, or makesure you have a 3rd party KB installed for emergency use.
I like to break stuff!
Click to expand...
Click to collapse
I'm not a noob XD I know what to do. What I said is I already did try to use the modified apk provided. It just force closed. So I used the old one. And ya the instructions are pretty crappy lol. Just like xxx pretty much
Sent from my SPH-L710 using xda app-developers app
Again bro?
Since LJ7 asking for stock kb autocorrect. Beyond.
Just let it go and move to another kb.
Sent from my O=O
Hi Guys,
I use this function to prevent being disturbed at night.
However I hate the Icon associated with this feature. Is there a way to hide this (phone is rooted) without using Exposed framework etc?
Thanks,
I assume that you are talking about the notification icon. The notification icon is a feature implemented to let the user know that the phone is in Blocking mode, which is pretty important considering that one might miss phone calls and alarms if using the phone in this mod without knowing. So the icon is a pretty important indicator that cannot be removed only by messing with the framework. I am sorry to be disappointing you, but there's no other way.
Ruwin said:
I assume that you are talking about the notification icon. The notification icon is a feature implemented to let the user know that the phone is in Blocking mode, which is pretty important considering that one might miss phone calls and alarms if using the phone in this mod without knowing. So the icon is a pretty important indicator that cannot be removed only by messing with the framework. I am sorry to be disappointing you, but there's no other way.
Click to expand...
Click to collapse
I'm not sure I agree. The blocking is only setup for early hours of the morning. Why do I need to know Blocking is enabled for the rest of the time. Also it is set to allow those I consider important to call. As such I don't need or want it.
I also think your wrong that this can't be done as a Google search shows a mod to do just this is available for the s3 however I'm not going to flash that.
I could just install exposed but I find it has negative effects with my rom.
Sent from my GT-N7100 using Tapatalk
ninjabadger said:
I'm not sure I agree. The blocking is only setup for early hours of the morning. Why do I need to know Blocking is enabled for the rest of the time. Also it is set to allow those I consider important to call. As such I don't need or want it.
I also think your wrong that this can't be done as a Google search shows a mod to do just this is available for the s3 however I'm not going to flash that.
I could just install exposed but I find it has negative effects with my rom.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Edit. Balls to it I'll reinstall exposed.
Sent from my GT-N7100 using Tapatalk
It is possible by editing the framework, for sure. Go ahead and try the app. You can also edit the framework manually in order block any icon in the notification bar. That would clear any other secondary effects of that app, but also would involve messing with the rom files
Sent from my GT-N7100 using xda app-developers app
I'm trying to figure out where I can remove the Jay Z clips from my phone so it doesn't keep starting up on BT when it syncs to my Alpine deck. I only have the samples not the album. Does anyone know where? how? Can't seem to find it. So annoying.
Uninstall the magna carta app?
Sent from my GT-I9505 using xda app-developers app
tylerholbrook said:
Uninstall the magna carta app?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
I don't have that app, that is the problem. I just have some clips of the songs somewhere and I can't seem to find them. Every time I BT sync with my deck, they start playing the clips. I just don't see where they are located on the phone to rid myself of them.
benjammn said:
I don't have that app, that is the problem. I just have some clips of the songs somewhere and I can't seem to find them. Every time I BT sync with my deck, they start playing the clips. I just don't see where they are located on the phone to rid myself of them.
Click to expand...
Click to collapse
Are you rooted?
If so you can use a root file explorer to look for hidden files.
You can also switch to a custom rom and those media files will be very gone after a full wipe and clean install of another ROM.
Don't know if you want to use the rooting options, but they are guarenteed to work.
Skipjacks said:
Are you rooted?
If so you can use a root file explorer to look for hidden files.
You can also switch to a custom rom and those media files will be very gone after a full wipe and clean install of another ROM.
Don't know if you want to use the rooting options, but they are guarenteed to work.
Click to expand...
Click to collapse
yeah not really wanting to root right now, on Tmobile leap program, don't want any troubles with them....I will keep looking, hopefully someone out there has done this before.
benjammn said:
yeah not really wanting to root right now, on Tmobile leap program, don't want any troubles with them....I will keep looking, hopefully someone out there has done this before.
Click to expand...
Click to collapse
its in Samsung Hub...so now I just have to figure out how to get rid of that Magna Carta Demo from playing everytime
benjammn said:
its in Samsung Hub...so now I just have to figure out how to get rid of that Magna Carta Demo from playing everytime
Click to expand...
Click to collapse
found a link on droidforums that talks about the Hub and disabling it, hope this works...will report back
benjammn said:
found a link on droidforums that talks about the Hub and disabling it, hope this works...will report back
Click to expand...
Click to collapse
can't you just clear the cache on the hub app in settings > app management? I'd think it would clear all of that out.
Ive been wondering the same thing
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