Related
Tested with Skype version 3.2.0.6673 (released 1st July 2013) on various
Android devices (Sony Xperia Z, Samsung Galaxy Note 2, Huawei Premia 4G
The Skype for Android application appears to have a bug which permits the
Android inbuilt lockscreen (ie. pattern, PIN, password) to be bypassed
relatively easily, if the device is logged into Skype, and the "attacker"
is able to call the "victim" on Skype.
This can be reproduced as follows with 2 Skype accounts, and 2 separate
devices to use with Skype. The target phone is presumed to have an Android
lockscreen configured and in use, and to be locked during the test.
1. Initiate a Skype call to the target device, which will cause it to
wake, ring, and display a prompt on the screen to answer or reject the call
2. Accept the call from the target device using the green answer button
on the screen
3. End the call from the initiating device (ie. the device used to call
the target phone)
4. The target device will end the call, and should display the
lockscreen.
5. Turn off the screen of the target device using the power key, and
turn it on again
6. The lockscreen will now be bypassed. It will remain bypassed until
the device is rebooted
Similar to (ironically enough):
http://arstechnica.com/security/201...een-lock-on-up-to-100-million-android-phones/.
Seems that internet based calling apps might well be "unlucky".
I suggest logging out of skype when not using it, until there is a fix.
Thanks to Turl for originally bringing this to my attention.
Greetings pulser_g2,
Thanks for posting this. I found that all these screenlock bypass vulns (including yours) won't work if a enterprise policy is enforced on the target device. I've tested with 2 different smartphones, Note 8.0 and Note 2. Both with the current stock firmware. Can you or anyone else confirm this?
Cheers,
Michael
c0rnholio said:
Greetings pulser_g2,
Thanks for posting this. I found that all these screenlock bypass vulns (including yours) won't work if a enterprise policy is enforced on the target device. I've tested with 2 different smartphones, Note 8.0 and Note 2. Both with the current stock firmware. Can you or anyone else confirm this?
Cheers,
Michael
Click to expand...
Click to collapse
Hi Michael,
Thanks for the tip. However, forcing enterprise policy onto a device that does not need it should not be a solution for a bug like this (not ranting against you, please don't take it that way). Skype was already informed about this a couple of weeks ago and nothing has been done afaik.
I received a Skype update today from the market, so I guess it might be worth checking if the bug can be repeated or if it has been fixed.
Hi egzthunder1,
I don't take your post personal. My post was not made with the intent to be a bugfix. I just want someone else who also has access to provisioned devices to confirm my observation. Additionally if my observation is correct then it should be mentioned in a security advisory that enterprise provisioned devices with an enforced password seem to not be affected by all these lockscreen bypasses. I'm just discussing here
Does andybody know which wrong usage of the Android-API might be used here? I'm developing myself an app which switches the Screen on and shows information without the need to unlock the device. Know I'm concerned that I might use the API wrong, too. There were also such bugs in other apps in the past month, so there must be some wrong usage type. Saidly I didn't find anything about it via googling. If you have links, please share.
SamsungPisser said:
Does andybody know which wrong usage of the Android-API might be used here? I'm developing myself an app which switches the Screen on and shows information without the need to unlock the device. Know I'm concerned that I might use the API wrong, too. There were also such bugs in other apps in the past month, so there must be some wrong usage type. Saidly I didn't find anything about it via googling. If you have links, please share.
Click to expand...
Click to collapse
It seems to be related to the use of the permission to disable the lockscreen.
I.e. http://stackoverflow.com/questions/12021800/disable-delay-android-lock-screen-programmatically
You want to ensure you definitely disable the option once done. I suggest you create a test plan and ensure even if everything goes wrong, the lock will still get enabled again in the end.
c0rnholio said:
Hi egzthunder1,
I don't take your post personal. My post was not made with the intent to be a bugfix. I just want someone else who also has access to provisioned devices to confirm my observation. Additionally if my observation is correct then it should be mentioned in a security advisory that enterprise provisioned devices with an enforced password seem to not be affected by all these lockscreen bypasses. I'm just discussing here
Click to expand...
Click to collapse
Hmmm that is interesting actually.
I need to see if I can replicate this by forcing provisioning manually.
I don't have an exchange server unfortunately (I use my own mail server that uses the protocol but doesn't do the complex provisioning.)
I'll have a look though as I think it supports provisioning in the configuration where it emulates Exchange. I believe this likely is a workaround for enterprise users.
This would be enough motivation actually to look at setting up proper provisioning of my devices.
Thanks for letting me know
Q&A for Lollipop 5.0 runs on our msm8960s on kkbl
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Lollipop 5.0 runs on our msm8960s on kkbl. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Battery Life
derpyherp said:
I think its odd how there is no deep sleep state i put a screen shot of the cpu times at each cpu speed... Its odd but somehow battery life is amazing
Click to expand...
Click to collapse
I switch back to cm11 because i have 6%/hr of battery drain, (7hr/41min Screen on time, 65% left), that is for me horrible battery life.
I did not look the cpu states, but, if there is no deep sleep, it sould explain mi experience about battery.
I have the same mensage when I was in f2fs. I have to go back to ext4 to work.
Does anyone know if the AOSP Camera will be made available? I don't like the Google one since it doesn't allow me to choose the external SD card as a storage option.
The system itself boots, and runs quite smoothly from what I've tried so far. Very exciting!
But I've found that Lastpass crashes immediately when I try to launch it. I did a clean install with CM12 11/17. Has anyone else seen this behaviour with this app? I'm assuming for the moment it just hasn't yet caught up to Android 5, and I'll have to sit patiently on 4.4 until then.
Cubkyle said:
The system itself boots, and runs quite smoothly from what I've tried so far. Very exciting!
But I've found that Lastpass crashes immediately when I try to launch it. I did a clean install with CM12 11/17. Has anyone else seen this behaviour with this app? I'm assuming for the moment it just hasn't yet caught up to Android 5, and I'll have to sit patiently on 4.4 until then.
Click to expand...
Click to collapse
I don't use that app, but it's probably either one of two things (or both):
This ROM was just release back on 11/14, so it's fairly new (the 11/14 was the first release), so there could be some issues that are causing the app to fail.
The app needs to be updated to run correctly under LP. There were some major changes to the API for LP that could cause other apps to fail that are now using these deprecated API calls. The developer needs to take there app and compile it under the latest LP compiler and libs to see if it compiles.
So, you'll probably have to wait and see. So far, I've been lucky. The apps that I need to work (CoPilot USA, etc) all work. Just waiting for dhacker to figure out the correct set of libs for DRM so that Google Play Movies and Netflix start working again. They work fine under my Nexus 7 running LP, but that was an official release by Google.
iBolski said:
I don't use that app, but it's probably either one of two things (or both):
This ROM was just release back on 11/14, so it's fairly new (the 11/14 was the first release), so there could be some issues that are causing the app to fail.
The app needs to be updated to run correctly under LP. There were some major changes to the API for LP that could cause other apps to fail that are now using these deprecated API calls. The developer needs to take there app and compile it under the latest LP compiler and libs to see if it compiles.
So, you'll probably have to wait and see. So far, I've been lucky. The apps that I need to work (CoPilot USA, etc) all work. Just waiting for dhacker to figure out the correct set of libs for DRM so that Google Play Movies and Netflix start working again. They work fine under my Nexus 7 running LP, but that was an official release by Google.
Click to expand...
Click to collapse
It turns out it was simply a matter of PEBCAK. I uninstalled Android System Webview, because it has the same icon as the stock Browser, while I was removing unwanted processes.
The first time , I flashed 11/15 version, everything seems to work fine ,then I flashed gapps, then I got no signal anymore,but everything else seems to work, so I did a factory reset, the gsm signal came back again, today when I trying to flash 11/18 version, the signal gone again, this time I don't want loose my data , what should I do to get a gsm signal? *#*#4636#*#* seems not working on 11/18, sorry for my poor english
Cubkyle said:
It turns out it was simply a matter of PEBCAK. I uninstalled Android System Webview, because it has the same icon as the stock Browser, while I was removing unwanted processes.
Click to expand...
Click to collapse
Ah, I'm familiar with those errors as well as the ID10T error as well.
Works just fine, very smooth. Had no troubles with the signal at all.
However, I can't receive a call, the dialer just stops. It is possible though to make a call. Anyone had this problem?
yes had that error many times "dialer has stopped", this is work in progress man. I hope that dhacker checks this and the other thread and try to remedy some of the prob.
For that dialer has stopped error, a reboot can cure it. But again i cant rely on a phone that is going to quit when you need to make or receive a call.
So the fix for no service is still reboot and hope?
I'm on Verizon CDMA, XT926, 11/23 build, 11/22 gapps, SuperSU 2.27
Thanks.
Doug B.
I had an odd issue on 11/22 build:
When I connect my car via bluetooth, when a call comes in, pressing the answer button does nothing and the call keeps ringing forever.
Also,
Is Anyone having issues with restoring on TWRP 2.8.1.0? I tried restoring a backup I made and my phone won't boot. It just gets stuck at the cyanogen mod screen.
Edit: I restored a previous backup, installed TWRP 2.8.2.0 and then restored the backup I was trying to. It worked.
dvgb173 said:
So the fix for no service is still reboot and hope?
I'm on Verizon CDMA, XT926, 11/23 build, 11/22 gapps, SuperSU 2.27
Thanks.
Doug B.
Click to expand...
Click to collapse
On my 11/25 build data wasn't working at first, I just turned it on and off from settings and it started working.
11/25 build is working for me as far as being able to receive phone calls. I was previously getting FCs on it when an incoming call was coming, but I was also running f2fs. I've gone back to ext4 and things seem to have stabilized at this point.
This build is the dhacker? I found nothing in his link. Many changes over the previous build?
When open 3g ,call comein can not.
How to fix it?
Thank.
soowijux said:
When open 3g ,call comein can not.
How to fix it?
Thank.
Click to expand...
Click to collapse
Now, I install 30/11 it OK.
Thanks.
SMS issue
Is the sms issue (can't receive sms, although the phone I'm sending from receives the delivery report) still present in this new build (12-02)? I've tried the 11-25 build and BlissPop and none of them allowed me to receive sms... It's the one real issue that's keeping me from jumping into Lollipop
Razr HD (XT925, KK bootloader)
My device does not come out of the boot with this version.
At about 5:00am today, I was notified that an Over-The-Air Update is available for my stock Sprint Galaxy S5 hardware number SM-G900P. Googling got me no info on this update, and all the info Samsung pushed on me is typed at the bottom of this post.
Has anyone let it update your phone yet?
Did anything notable change after you ran the update?
Did any settings you loved go away?
Did any new settings turn up?
What Android version number do you have after the update?
Relax, and tell us about your mother.
Anything else you feel is pertinent?
Please post on this thread to let us cautious adopters (a.k.a. chickens) get a picture of how safe (or unsafe) this update may or may not be.
Good luck, everyone!! Thanks!
?*Ã??*â?¢?*Ã??*â?¢?*Ã??*â?¢?*Ã??*â?¢?*Ã??
Info on the update says thus:
Software Update
The latest software update
is ready to be installed. If you
tap INSTALL OVERNIGHT, the
update will be installed between
2:00 AM and 5:00 AM
Version: G900PVPU3CPCA/
G900 PSPT3CPCA/
G900PVPU3 CPCA>
G900PVPU3CPE1/
G900 PSPT3CPE1/
G900PVPU3 CPE1
Size: 187.58 MB
What's new
-The security of your device has been improved
-Wi-Fi connectivity and stability have been improved
A software update can include, but
is not limited to:
-Device stability improvements, bug fixes
-New and / or enhanced features.
-Further improvements to performance.
To get the best from your device, please keep your phone up to date and regularly check for software updates.
Your device will restart after the update is installed. Tap here for more information.
Caution
LATER
INSTALL OVERNIGHT
INSTALL NOW
(Then if you click on the word "Caution"):
You will not be charged for this software installation.
-During installation, you will not be able to use your device at all, even for emergency calls.
Icons on the Home screen may be reset to their defaults and may need to be reconfigured after installation.
-A software update should not affect the files and data on your device.
-To avoid unexpected data loss, we recommend that you back up important data before installation.
i wasnt aware that a PE1 baseband was released. I guess we'll just have to stay tuned to see what info turns up
i just looked on sammobile.com, and the pca baseband was the most recent one showing there. Weirdness :/
It's only 187mb. The only difference at least for me is WiFi not turning on by itself.
Sent from my SM-G900P using Tapatalk
Thanks. WiFi turning itself on is really annoying. I won't miss that!
Edit: I ran the update. WiFi still turns itself on. The second warranty is up this baby is getting rooted.
Also the so-called lag-free camera which always took a long time to focus takes MUCH longer to focus now. Much. Longer.
I received the update notification but I was afraid to accept it for fear of losing root.
1) Does the update remove root?
2) If so, can the update be rooted?
Tried updating but it just boots into custom recovery. You must reinstall stock recovery to utilize update. Not worth it imho
Somebody know how to root on that build CPE1 or CPE2?
Question: Does rooting the device prevent me from receiving OTA updates? Do I have to "re-root" after each OTA update?
Background: I used to be really into custom roms, TWRP recovery, Xposed mods....back in the days up to the LG G2 and Nexus 6. So I am super rusty on Android changes in the last 5 years. I am now coming back from iPhone jailbreak land. I just ordered a 7 Pro directly from Oneplus.com and super am excited. I spent the last 12 hours reading up on Android related info. I plan to unlock the bootloader and root the phone right away so that I can #1 enable native tethering, #2 system-wide adblock, #3 youtube adblock.
I would like to stay close to stock as possible to receive OTA updates. The only thing more important to me than OTA is being able to #1 enable tethering. #2 and #3 are nice to have, not must haves.
I'll be using this device with T-mobile in the USA.
Your help and patience would be much appreciated. Sincerely, thank you.
Either re-root after ota, or just flash the full update in twrp then reflash twrp/magisk for root/recovery. If you want to hide tethering usage on tmo there are a few ways to do it but I use "
VPN Hotspot - tethering/Wi-Fi repeater"
https://play.google.com/store/apps/details?id=be.mygod.vpnhotspot
JedixJarf said:
Either re-root after ota, or just flash the full update in twrp then reflash twrp/magisk for root/recovery. If you want to hide tethering usage on tmo there are a few ways to do it but I use "
VPN Hotspot - tethering/Wi-Fi repeater"
https://play.google.com/store/apps/details?id=be.mygod.vpnhotspot
Click to expand...
Click to collapse
I want to use native tethering (if it works) so that I can enable Tasker automation - turn on wifi hotspot while I am in the car. Although I like this option as well. I could connect to my home OpenVPN server.
Thanks. Sounds like I can just quickly reflash the two files in succession and I am good to go?
5+ years ago, doing this sometime causes problems when the version difference is very significant. For example, going from Android 9 to Android 10 OTA, I would have to wipe user data and start over. Not sure if it's still true today.
I'm rooted on Pie June update (PQ3B.190605.006) and suffering from infamous "CaptivePortalLogin keeps stopping" issue reported on Reddit ( can't post link due to policy, sorry).
As a temporary solution I use CAPTIVE_PORTAL_MODE_IGNORE in Settings.java to prevent Android from detection of captive portals.
To do that in root shell on device run:
settings put global captive_portal_mode 0
The same could be accomplished over ADB.
After updating that setting I don't get notifications until opening page in browser, which redirects me to the login page of the Wi-Fi provider.
I'm looking for ideas how to make CaptivePortalLogin to work on PQ3B.190605.006 version.
Tried to remove Magisk, reflash clean and replace CaptivePortalLogin in /system/apps with different APK provided here on XDA, sideloaded July PQ3B.190705.003 version, but nothing helped.
SOLUTION: Clean flash of July update PQ3B.190705.003 on both A/B and full factory reset.
my workaround for this is basically turning on airplane mode -> turn on wifi and connect to network -> open browser and load a random page to be redirected to the captive portal.
Did it work with the march version? Looks like even stock phones seem to have a problem with it according to reddit. It worked just fine for me on june when it wasnt rooted..
Thank you so much for workaround! It works.
For your question about March version, I don't have an answer if it worked out of the box, as I didn't try it.
It would be nice to fix CaptivePortalLogin, not sure how to attack it though.
While waiting on support to fix CaptivePortalLogin, I came up with a temporary solution, to avoid a brute force "Airplane mode" method. I decided to use CAPTIVE_PORTAL_MODE_IGNORE in Settings.java to prevent Android from detection of captive portals.
Solution:
in root shell on device run:
settings put global captive_portal_mode 0
The same could be accomplished over ADB.
After updating that setting I don't get notifications until opening page in browser, which redirects me to the login page of the Wi-Fi provider.
I hope someone can benefit from this solution until we get a real fix for CaptivePortalLogin.
I have disabled MAC address randomization in the advanced options of the WiFi network and it seems to solve the issue. Many captive portals use the MAC address to identify the device, so this would be a good explanation of the problem.
Thanks for suggestion. That option was off on my device by default and I didn't play with it. And in my case Captive Portal Login crashed on every network implementation from my corporate one to coffee shop.
R0BiN0705 said:
my workaround for this is basically turning on airplane mode -> turn on wifi and connect to network -> open browser and load a random page to be redirected to the captive portal.
Did it work with the march version? Looks like even stock phones seem to have a problem with it according to reddit. It worked just fine for me on june when it wasnt rooted..
Click to expand...
Click to collapse
This did not help
Still keep getting captiveportal crashed.
Any other suggestions?
Look at my original post or post #4 how to use CAPTIVE_PORTAL_MODE_IGNORE to disable Captive Portal login.
Wow! I am glad I am not the only one experiencing this issue!
I have the google pixel 3a with June security patch and rooted with Magisk via patched boot image.
Im wondering, is this due to Magisk or is this an actual issue with the June 2019 Factory Images/OTA?
Thanks!
djjohnnyblaze said:
Wow! I am glad I am not the only one experiencing this issue!
I have the google pixel 3a with June security patch and rooted with Magisk via patched boot image.
Im wondering, is this due to Magisk or is this an actual issue with the June 2019 Factory Images/OTA?
Thanks!
Click to expand...
Click to collapse
I speculate it's a bug in June update, because it did crash for me with or without Magisk. But on another hand I would expect more activity on this thread if it is a widespread issue.
pasha_d said:
I speculate it's a bug in June update, because it did crash for me with or without Magisk. But on another hand I would expect more activity on this thread if it is a widespread issue.
Click to expand...
Click to collapse
Looked at some threads on Reddit and it seems like even new devices are having this issue.
I don't think anyone knows what's causing it but this is a big deal. What scares me is one thread that said a replacement device works now with June security update. How could this be hardware though? Especially if it was working prior to June 2019 security update ...
The July security patch did not resolve this issue. How do we escalate this?
Issue had already been raised... No fix yet.
https://issuetracker.google.com/issues/135711621
karimski75 said:
Issue had already been raised... No fix yet.
https://issuetracker.google.com/issues/135711621
Click to expand...
Click to collapse
Not sure where they're going to fix it though, maybe in Q only. I'm looking for a fix in Pie.
Here is the post from assigned developer from Google:
vi.. @google.com <vi.. @google.com> #83 Jul 9, 2019 02:26AM
Marked as fixed.
The issue has been fixed and it will become available in a future Android release. Please keep an eye on the release notes(https://developer.android.com/preview/release-notes)
It crashes for me too. Bummer!
Stock and non-rooted.
Pasha_d posted a solution that worked for me. You need to be rooted.
https://forum.xda-developers.com/pixel-3a/help/captiveportallogin-apk-t3940042
Pasha, did you ever find a copy of the March version of the captiveportallogin.apk?
No I didn't. The only ones I found on APK mirror were from February. Nobody replied to my original request here on XDA.
I was able to turn off data. Load a web page and sign in over wifi.
pasha_d said:
No I didn't. The only ones I found on APK mirror were from February. Nobody replied to my original request here on XDA.
Click to expand...
Click to collapse
March apk