Related
i am using a nexus S with whisper systems whisper core
it has real luks based AES full disk encryption and the ability to selectivity revoke application permissions
there seems to be no public info on the encrytion on ice cream sandwich
can anyone comment on it?
Anyone?
Sent from my Nexus S using Tapatalk
thanks for the replys
I got my LTE Galaxy Nexus today by far the best android device ever
I enable encryption
and it works fine
I wonder how long till theres a story about cops unable ( or able ) to get into someones phone because of encryption..
You must use a password/pin to encrypt. Swipe and face unlock are not a option. In cant be more than 16 characters. The same password used to encrypt the device must be used to unlock the screensaver. VERY annoying. You can however change your pass code/pin used to encrypt the device after encrypted nearly instantly. I'm not sure how its able to do this without a complete re-encryption of all encrypted blocks?
Sent from my Galaxy Nexus using Tapatalk
gophet said:
You must use a password/pin to encrypt. Swipe and face unlock are not a option. In cant be more than 16 characters. The same password used to encrypt the device must be used to unlock the screensaver. VERY annoying. You can however change your pass code/pin used to encrypt the device after encrypted nearly instantly. I'm not sure how its able to do this without a complete re-encryption of all encrypted blocks?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
So, if you encrypt you have to enter your PIN to start the phone AND unlock the phone?
The information I read says you only need the PIN when you "turn on" your phone...
That would be okay but not for unlock too...
Yes your pin (or pass code) is used both to turn on the device and unlock the lock screen... I initially created a long random hard to type string of characters for my password but when I figured out I'd have to type it in for my unlock code also I quickly change into a numerical pin the fact I could change it without re encrypting the the tire device leave me to believe encryption keys for the entire disk is stored in small separate encrypted file somewhere.
Still wondering if this is AES or something else? And what partitions exzatly is encrypted.
Sent from my Galaxy Nexus using Tapatalk
gophet said:
Yes your pin (or pass code) is used both to turn on the device and unlock the lock screen... I initially created a long random hard to type string of characters for my password but when I figured out I'd have to type it in for my unlock code also I quickly change into a numerical pin the fact I could change it without re encrypting the the tire device leave me to believe encryption keys for the entire disk is stored in small separate encrypted file somewhere.
Still wondering if this is AES or something else? And what partitions exzatly is encrypted.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Thanks for the clarification... that sucks...
Ive been begging for this option on my Nexus One and now that ive upgraded are there any negatives to doing this? any negative performance hits etc.
What happens when you connect the Nexus to a computer? Can you see the contents of the internal memory via MTP, ei. pictures?
bunklung said:
What happens when you connect the Nexus to a computer? Can you see the contents of the internal memory via MTP, ei. pictures?
Click to expand...
Click to collapse
Yes you can.
gophet said:
You must use a password/pin to encrypt. Swipe and face unlock are not a option. In cant be more than 16 characters. The same password used to encrypt the device must be used to unlock the screensaver. VERY annoying. You can however change your pass code/pin used to encrypt the device after encrypted nearly instantly. I'm not sure how its able to do this without a complete re-encryption of all encrypted blocks?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
you can change the password quickly because it does not reencrypt the whole storage. the actual key used for encryption is static, the password encrypts the key itself, not the storage.
it's a common theme in encryption schemas, truecrypt does the same thing. you generate strong keys once, and protect them with passwords. PGP does the same thing to your private key...
gkaugustine said:
Ive been begging for this option on my Nexus One and now that ive upgraded are there any negatives to doing this? any negative performance hits etc.
Click to expand...
Click to collapse
whisper system whispercord does FDE on nexus one and S
no notable performance issues - have not run any benchmarks
mvorbrodt said:
you can change the password quickly because it does not reencrypt the whole storage. the actual key used for encryption is static, the password encrypts the key itself, not the storage.
it's a common theme in encryption schemas, truecrypt does the same thing. you generate strong keys once, and protect them with passwords. PGP does the same thing to your private key...
Click to expand...
Click to collapse
yeah thats what i kinda figured - now i wonder what file it is that hold the key and how it is encrypted
Petrovski80 said:
Yes you can.
Click to expand...
Click to collapse
Does MTP or Windows prompt you for a password?
Does your phone need to be unlocked for the MTP drive to show? If you lock your phone does a file transfer stop?
Thanks again.
Do you know if the encryption slow down the phone?
It must encrypt every new file. Does this result in slower operations?
sblantipodi said:
Do you know if the encryption slow down the phone?
It must encrypt every new file. Does this result in slower operations?
Click to expand...
Click to collapse
The overhead will be when writing to and reading to the block device. There will be very few scenarios where you are maxing io (aka writing/reading) and the cpu at the same time. And that's the only scenarios where you'd really notice any slowdown.
There will be some increased cpu usage while writing to/reading from file though, so you could take a theoretical battery usage hit. But I doubt you'll notice it.
//edit, I should also point out that even if you find a game that's bothered doing background loading and pushing some cpu task in parallel, the phone has 2 cores.
//edit 2, some more digging:
http://source.android.com/tech/encryption/android_crypto_implementation.html
So we're talking dm-crypt with aes-cbc-essiv 128bit keys and sha256.
thanks! just what i was looking for
I had encryption on for a while. It took 45mins to encrypt my device when first activated. If I rebooted my phone it would take 3mins to boot up during which time I would be asked for my sim pin, encryption pin and finally the SIM pin again. The screen would repeatedly turn off during this time. In the end I removed encryption (factory reset is the only way to do this).
Sent from my Galaxy Nexus using Tapatalk
How does this work for flashing/upgrading the rom? I suppose it would need be be re-encrypted each time, however is the pin entered even before fastboot?
you cant backup a encrypted running system
you can only do a wipe
taking the galaxy nexus back as my nexus S seems to do most everything the galaxy nexus does only slower and smaller
Has any one done any work on getting LUKS working on the Galaxy Nexus yet? I know ICS has encryption but it is not the same (It is file level; dm-crypt encryption and leaves room for data leaks).
For that reason does any know of a WhisperCore alternative?
Thanks!
ICS encryption is dm-crypt based whole partition encryption. See ht tp://source.android.com/tech/encryption/android_crypto_implementation.html for details.
Now it does seem to have lots of drawbacks, but i don't think luks would be much safer. Well, it seems they differ in the used encrypted key headers. Google could have got that insecure.
Just using the lockscreen password strikes me as a bad choice in googles solution.
textshell said:
ICS encryption is dm-crypt based whole partition encryption. See ht tp://source.android.com/tech/encryption/android_crypto_implementation.html for details.
Now it does seem to have lots of drawbacks, but i don't think luks would be much safer. Well, it seems they differ in the used encrypted key headers. Google could have got that insecure.
Just using the lockscreen password strikes me as a bad choice in googles solution.
Click to expand...
Click to collapse
You can tell the whole OS is not encrypted since you can make emergency calls when at the preboot authentication screen.Only /data is encrypted and thus leaves room for data leakage. WhisperCore just managed it perfectly- just like LUKS on a computer. Preboot authentication, ENTIRE disk encrypted (minus /boot), and secondary lock screen (login) password that can be anything include "pattern".
Not to mention ICS is only AES-128 bit, I mean c'mon why not just use 256 bit like everyone else? It's cleared by FIPS for a reason.
x942 said:
You can tell the whole OS is not encrypted since you can make emergency calls when at the preboot authentication screen.Only /data is encrypted and thus leaves room for data leakage. WhisperCore just managed it perfectly- just like LUKS on a computer. Preboot authentication, ENTIRE disk encrypted (minus /boot), and secondary lock screen (login) password that can be anything include "pattern".
Not to mention ICS is only AES-128 bit, I mean c'mon why not just use 256 bit like everyone else? It's cleared by FIPS for a reason.
Click to expand...
Click to collapse
changing the key length for encryption should be an easy thing when compiling from source. Not sure what's the performance impact and security gain.
Having different crypto passphrase and screen unlock code might be a good thing, but if i start caring about encryption of my phone i'd try to push the key into the smartcard inside every phone (SIM card) and just enter the smartcard pin. Depends on amount of paranoia wrt security of these cards though.
But i don't understand why you would like to encrypt /system with a stock ROM. Nothing gained there. /system is read only so it can't really leak data. And as the kernel in the boot partition is unencrypted and unauthenticated anyway the OS code is open for changes anyway.
Without special hardware help or keeping the boot media separate and very safe, encryption will always only work against simple thiefs. If your attacker can get the phone do something to it and return it without you getting suspicious you lost anyway. Assuming he can get it again once you booted and used the phone again.
textshell said:
changing the key length for encryption should be an easy thing when compiling from source. Not sure what's the performance impact and security gain.
Having different crypto passphrase and screen unlock code might be a good thing, but if i start caring about encryption of my phone i'd try to push the key into the smartcard inside every phone (SIM card) and just enter the smartcard pin. Depends on amount of paranoia wrt security of these cards though.
But i don't understand why you would like to encrypt /system with a stock ROM. Nothing gained there. /system is read only so it can't really leak data. And as the kernel in the boot partition is unencrypted and unauthenticated anyway the OS code is open for changes anyway.
Without special hardware help or keeping the boot media separate and very safe, encryption will always only work against simple thiefs. If your attacker can get the phone do something to it and return it without you getting suspicious you lost anyway. Assuming he can get it again once you booted and used the phone again.
Click to expand...
Click to collapse
Not true. You an relock the bootloader on the Nexus phones, this completely prevents evil maid attacks. Secondly if I ever lose my phone and "happen to get it back" the first thing I am doing is wiping it and selling it for another one.
If you have ever use encryption you would know that the less an attacker knows the better. Hence encrypting the entire system is better than only encrypting a partition.
I don't like how Google implements dm-crypt. It would be more secure if the entire device was encrypted as it would completely look like random data to an attacker.
Why would you only encrypt your home folder and not every thing BUT /boot?
I prefer the whispercore way of doing it. I poweroff and you can't access anything except the login screen.
x942 said:
Not true. You an relock the bootloader on the Nexus phones, this completely prevents evil maid attacks. Secondly if I ever lose my phone and "happen to get it back" the first thing I am doing is wiping it and selling it for another one.
Why would you only encrypt your home folder and not every thing BUT /boot?
Click to expand...
Click to collapse
I don't think trusting the locked bootloader is a good idea. Look for e.g. "unbrickable mod" for an example how a lot of samsung phones can be forced to bypass the bootloader on the internal flash and forced to load arbitrary code from outside. So if somebody is willing to do an evil maid attack, they will likely do enough research to know these kinds of backdoors in your hardware platform. JTAG is another usual way. Or whatever the phone manufacturer uses to unbrick phones. I think it prudent to assume any sufficiently founded attacker will have unrestricted read/write access.
And why only encrypt real data? Speed gain for no measurable loss in security. At least from the google perspective. Google will rightfully assume customers are using official ROMs and the exact bit patterns of there are publicly available to everyone. So why waste cpu cycles to encrypt them. What could be useful would be integrity protection.
But while a fully integrity protected boot under the control of the enduser would be very nice (with a bootloader that's unlocked but needs a key or password) if only the manufacturer gets to authorise new software it's evil.
textshell said:
I don't think trusting the locked bootloader is a good idea. Look for e.g. "unbrickable mod" for an example how a lot of samsung phones can be forced to bypass the bootloader on the internal flash and forced to load arbitrary code from outside. So if somebody is willing to do an evil maid attack, they will likely do enough research to know these kinds of backdoors in your hardware platform. JTAG is another usual way. Or whatever the phone manufacturer uses to unbrick phones. I think it prudent to assume any sufficiently founded attacker will have unrestricted read/write access.
And why only encrypt real data? Speed gain for no measurable loss in security. At least from the google perspective. Google will rightfully assume customers are using official ROMs and the exact bit patterns of there are publicly available to everyone. So why waste cpu cycles to encrypt them. What could be useful would be integrity protection.
But while a fully integrity protected boot under the control of the enduser would be very nice (with a bootloader that's unlocked but needs a key or password) if only the manufacturer gets to authorise new software it's evil.
Click to expand...
Click to collapse
Yes but as I said any one that would put that effort in would have to get the phone from me (which I carry 24/7) and once I know I no longer have control of it I would (as I said) reset it and sell it. You are basically saying all Full Disk Encryption (including on computers) is useless because someone can modify the bootloader. I hate to say it (and this is not directed to any one in this thread) but only a true ignorant person would fall victim to a evil maid attack, It is common sense NOT to trust something that you lost control of.
My situation is different: I run a non-profit organization and my employees need to carry sensitive data with them. Why risk security with the built in dm-crypt when something like WhisperCore is much better? I don't won't an attacker knowing ANYTHING about the device.
ICS built in encryption is just as useful as Home folder encryption in Linux. Your data may be safe but an attacker can ascertain how much data is there. And in some case use this information to infer what data may be present on the device. This is why most people using encryption use FDE and not just home folder encryption. When you are done there should be absolutely no way for anyone to tell the encrypted partition from random data (wiped data).
No, i'm just saying the full partition encryption of /data is enough on galaxy nexus and that you can't protect from an evil maid attack except by drastic measures after you lost control of your phone.
Understandable but I respectfully disagree. I want FULL DISK Encryption not Partition encryption. Take a look here: http://en.gentoo-wiki.com/wiki/DM-Crypt_with_LUKS#Security_levels
Either way (even if it is secure enough) It's not going to get approved for me to use in a work environment (FIPS 140-2). This is why I need some like WhisperCore. We handle sensitive data at my company.
Am I alone on this thought? I was really thinking about selling this tablet a month ago and decided to wait for the update, because I knew how terrible Lollipop was/is. I really am glad I waited, this tablet feels like a brand new device! No lag, approximately 650MB being used on average!, battery life is amazing, WiFi connection doesn't drop anymore, so far I can't find a flaw! If I did, there are so many pros to this update it couldn't take away the happiness I feel about what is better!
What do you think? Am I alone on this thought?
Sent from my Nexus 7 using XDA Free mobile app
I share you thoughts but GPU performance is crippled since lollipop :/
Gesendet von meinem Nexus 5 mit Tapatalk
I think it's great too. Much more polished. The only problem is that I can't access my microsd using user apps that don't require root.
Really? I thought that was one of the major changes to 6.0? Very strange... I don't use an external SD though, but still, strange nonetheless. I wonder how the Moto X Pure will do hearing this, considering that's a big selling factor for it.
Sent from my Nexus 7 using XDA Free mobile app
KK for performance, LP or MM for a low gaming performing device and a higher Android number in Abour Tab
Patozan said:
I think it's great too. Much more polished. The only problem is that I can't access my microsd using user apps that don't require root.
Click to expand...
Click to collapse
nikeman513 said:
Really? I thought that was one of the major changes to 6.0? Very strange... I don't use an external SD though, but still, strange nonetheless. I wonder how the Moto X Pure will do hearing this, considering that's a big selling factor for it.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Micro SD is accessible via system app. Once you insert your portable storage, go to Settings/Storage & USB and there you will see your portable storage drive. Click on it and you will be able to access your files. No problem watching movies stored on my micro SD. :good:
Unfortunately wifi option doesn't work properly and you can quickly drain the battery if you don't turn off wifi when you haven't access. Keep wifi on during sleep option is broken.
rsfinsrq said:
Micro SD is accessible via system app. Once you insert your portable storage, go to Settings/Storage & USB and there you will see your portable storage drive. Click on it and you will be able to access your files. No problem watching movies stored on my micro SD. :good:
Click to expand...
Click to collapse
The catch is you can't access your files if you're not using a system app or a user app with root access. Since most multimedia apps don't actively ask root permission, they won't have rights to access the microsd folder created under "/mnt/media_rw". You can't change the permissions to the microsd folder either. Perhaps if you set up your microsd as "internal storage" (see adoptable storage feature) instead of "portable storage" all multimedia apps can access it (since these apps have permission for it, of course), but Android M didn't implement that feature yet, at least as far as Flo is concerned.
Luckly Chainfire's Stickmount app uses its root rights to mount the microsd inside the internal storage (under sdcard), where all apps have access.
I was quite shocked to find out that a feature like adoptable storage, which has been announced by the media as Google finally playing along fairly with external storage, seems to be actually quite the opposite.
in this light YES it feels like a "new" device ... coming directly from a backyard in china with cloned firmware not belonging to this hw ,-)
would be interesting what TO understands as "battery life is amazing" when standby lasts max 2days.
Having to en-/disable WiFi everytime I want to use my tab is anything but amazing.
To add another one to the list: access from PC via USB doesn't work either.
One has to enable developer settings to switch USB to MTM allthough it is allready selected, charge only seems to be default with no possibility to change for standard users.
This seems to be the most untested and buginfested "upgrade" I encountered in my Android history.
I doubt even M$ could do worse ...
magic55 said:
Unfortunately wifi option doesn't work properly and you can quickly drain the battery if you don't turn off wifi when you haven't access. Keep wifi on during sleep option is broken.
Click to expand...
Click to collapse
i see the same problem. My wifi does not turn itself off. Has anyone found a solution for this battery drainer????
does this update bring any changes related to gsm dialing, gsm ussd dialing and sms receiving/sending?
(related dead thread: http://forum.xda-developers.com/show....php?t=2025377)
schufti said:
in this light YES it feels like a "new" device ... coming directly from a backyard in china with cloned firmware not belonging to this hw ,-)
would be interesting what TO understands as "battery life is amazing" when standby lasts max 2days.
Having to en-/disable WiFi everytime I want to use my tab is anything but amazing.
To add another one to the list: access from PC via USB doesn't work either.
One has to enable developer settings to switch USB to MTM allthough it is allready selected, charge only seems to be default with no possibility to change for standard users.
This seems to be the most untested and buginfested "upgrade" I encountered in my Android history.
I doubt even M$ could do worse ...
Click to expand...
Click to collapse
I have that usb problem too thats some bull****.
Battery life is pretty damn good I got over seven hours screen on time over 3 days with not light usage (no games). I don't have any wifi problems but even a bad signal shouldn't drain it since Doze should shut it down so I'm not sure what would be draining your battery. I lose 1-2% overnight.
My biggest problem with 6.0 is Doze. Turns off everything for good standby time, works great for that but now I don't get lots of notifications like email or calendar when it's dozing and excluding them from battery "optimization" does not work. They gotta fix that ****.
looks like I'm not alone with WiFi battery drain.
Maybe it is related to the LTE version?
Today I lost 20% overnight ... on a freshly flashed system w/o any installed apps, not even google account.
Just WiFi credentials and set keep WiFi on to never ...
Good time to test the CM12.1 ....
Edit: somehow 6.0 fails to recognize my 16GB Lexar 3.0 USB-drive. It says it's defective and offers to format but fails with a runtime error. The same USB-drive works w/o problem on my lenovo.
Has anyone have issues downloading files using Chrome? I use CF Lumen, and Chrome prompted me to disable that, which I did. Tapping links for downloads has no effect; I tried multiple sites to be sure. Weird!
[EDIT] Delete please - I posted my question in the Lumen thread.
hmmm, mysterious.
yesterday I left it as is at my office and it lost only 5% in 16 hours ... allthough WiFi was allways on according to batt graph
Is this WiFi behavior normal for marshmallow? I don't think so... Any solution for this?
Unlocked bootloader and rooted
Hi,
at least yours doesn't lie to you. Mine pretends to have not been using wifi ... but if I shut it off, I can see the difference.
It is interesting that the periods where wifi is shown as off were situations where no wifi was available or couldn't connect.
Due to the graph and stats, wifi was on but didn't consume (allmost) any energy. But if I totally disable Wifi I can see the difference (battery life prediction: 15 days)!
If I sum up all consumption infos I get 258mAh used in about 9.5h. 258mAh are approx 5.9% of the battery (not 19%) and recalculated the predicted life should be approx. 16 times 9.5h ... so something is very flawed in this region.
Mine is exceptional, like 1-2% overnight battery usage. My only observation is when I set the tablet down and use it the touchscreen rarely registers a touch. When it is held in my hands and I use my thumbs it works fine.... It has a rubber tpu style case stretched over it, doesn't make a difference. It also has a tempered glass screen protector. Is there a way to turn up touch sensitivity? I know some Samsung builds actually had that option.
Sent from my Nexus 7 using Tapatalk
Hey guys,
Both my wife and me are using a Pixel XL but in different colours. Recently we decided to swap our phones to get a refreshed experience. So I am curious what's the best (lazy) way to achieve this?
We are using the same (Australian) version, same storage size and the same Android version (Pie). Moreover, we are both rooted with Magisk and stock kernel.
I am thinking that I could possibly just back up the boot/system/data partitions and restore them perspectively. However, I don't think the SD storage can be backed up and restored?
What would be your approach?
chinesecooler said:
Hey guys,
Both my wife and me are using a Pixel XL but in different colours. Recently we decided to swap our phones to get a refreshed experience. So I am curious what's the best (lazy) way to achieve this?
We are using the same (Australian) version, same storage size and the same Android version (Pie). Moreover, we are both rooted with Magisk and stock kernel.
I am thinking that I could possibly just back up the boot/system/data partitions and restore them perspectively. However, I don't think the SD storage can be backed up and restored?
What would be your approach?
Click to expand...
Click to collapse
Honestly - buy some thin, different colored cases. Otherwise seems like alot of work to go through just to have a different colored phone. From what you've written that only refreshed part of the experience will be the color of the phone itself.
I had the same idea of transferring data because I got a new Pixel with more storage. I just went ahead and tried it and it works almost fully. The only problem is that some security features don't work anymore: First of all, SafetyNet is tripped now because CTS profile doesn't match. I don't know much about that matter but I'm assuming if it's a properly implemented security feature, it would only be fixable with a vulnerability. Secondly, the fingerprint reader is not usable anymore. I have a feeling that that's also connected to the first problem. When I try to register a fingerprint it works fine until the last part of the analysis process. Then it just says it couldn't be completed. It looks like it has to do with storing the fingerprint, which then again points to it having to do with the security storage (is that the credentials storage? I'm not sure...). Anyway, clearing the credentials also doesn't help. One more weird thing: I tried fixing SELinux contexts in TWRP and it basically went from hitting the button straight to done, but it didn't say anything about it in the log. So I don't know if it actually did it. It also didn't give an error message, though. I actually never used this feature before and don't know what the process is supposed to look like but it did seem a little odd to me.
I think I'll end up just starting fresh and transferring everything Titanium because I think it will be much easier and save me from many other issues down the road.
Artificial_Intelligence said:
I had the same idea of transferring data because I got a new Pixel with more storage. I just went ahead and tried it and it works almost fully. The only problem is that some security features don't work anymore: First of all, SafetyNet is tripped now because CTS profile doesn't match. I don't know much about that matter but I'm assuming if it's a properly implemented security feature, it would only be fixable with a vulnerability. Secondly, the fingerprint reader is not usable anymore. I have a feeling that that's also connected to the first problem. When I try to register a fingerprint it works fine until the last part of the analysis process. Then it just says it couldn't be completed. It looks like it has to do with storing the fingerprint, which then again points to it having to do with the security storage (is that the credentials storage? I'm not sure...). Anyway, clearing the credentials also doesn't help. One more weird thing: I tried fixing SELinux contexts in TWRP and it basically went from hitting the button straight to done, but it didn't say anything about it in the log. So I don't know if it actually did it. It also didn't give an error message, though. I actually never used this feature before and don't know what the process is supposed to look like but it did seem a little odd to me.
I think I'll end up just starting fresh and transferring everything Titanium because I think it will be much easier and save me from many other issues down the road.
Click to expand...
Click to collapse
Thanks for sharing the experience mate. Yeah, like you mentioned it would probably be easier to go titanium instead. :laugh:
chinesecooler said:
Thanks for sharing the experience mate. Yeah, like you mentioned it would probably be easier to go titanium instead. :laugh:
Click to expand...
Click to collapse
Yeah, I did and everything works great now .
Another idea for a refreshed experience could be a skin. I'm thinking about getting one too.
Have the Xiaomi Mi 10T 5G, which comes with Android 10 / MIUI 12 [Sort of combination of them i think], and i wanna install an older version of android only, lower than 10 [Preferably 7.0], is it possible to do at all? If so, then how exactly can i do that? if possible with exact instruction or guide to it..
Thanks ahead..
PEACE AND LOVE!
Not possible. I am really curious why would you even want that.
_mysiak_ said:
Not possible. I am really curious why would you even want that.
Click to expand...
Click to collapse
For many reasons.. They changed it in some very bad way for my opinion.. like the auto turning on WiFi by some apps, like some apps that don't have widgets, the call recording issue and many more very annoying unreasonable changes they did on A10 on.. saw also they only allow FBE encryption instead of FDE which is much better [That i can see for huge 128, 256 or maybe 512 Gigs Storages but still it should be up to the user decision not forcing]
So you say it's completely impossible? even if flash universal / rooted ROM? no way at all?! cause man those are really annoying stuff especially to the tech Pros and/or savvy's like us, and i know that since i saw many threads and posts in other forums about those issues too.. Maybe some giving up or thinking it's advancements, but really, maybe big money involved, espionage, and many more possible reasons they doing it.. It's bad, really bad..
* BTW sorry for the multiplication threads didn't knew it's SPAMing and not very involved it forums world..
Thank ahead.
Jeff1976A1 said:
For many reasons.. They changed it in some very bad way for my opinion.. like the auto turning on WiFi by some apps, like some apps that don't have widgets, the call recording issue and many more very annoying unreasonable changes they did on A10 on.. saw also they only allow FBE encryption instead of FDE which is much better [That i can see for huge 128, 256 or maybe 512 Gigs Storages but still it should be up to the user decision not forcing]
So you say it's completely impossible? even if flash universal / rooted ROM? no way at all?! cause man those are really annoying stuff especially to the tech Pros and/or savvy's like us, and i know that since i saw many threads and posts in other forums about those issues too.. Maybe some giving up or thinking it's advancements, but really, maybe big money involved, espionage, and many more possible reasons they doing it.. It's bad, really bad..
* BTW sorry for the multiplication threads didn't knew it's SPAMing and not very involved it forums world..
Thank ahead.
Click to expand...
Click to collapse
To be honest I don't understand none of your points.
1. Wifi can be still turned on by apps, you just need to enable the permission (allow always vs. allow only when app is running in foreground).
2. Call recording is working in regions where it's not forbidden by privacy laws.
3. FBE is much better because it allows you to start the phone with basic service without using the password. Not sure why do you consider FDE to be superior.
4. Well, you can try to build your own Android 7 ROM from old sources, but you're going to have a fun time adapting to vendor partition/proprietary files created for Android 10 or 11. Also using several years old code which is not supported or patched anymore is quite interesting approach to security.
_mysiak_ said:
To be honest I don't understand none of your points.
1. Wifi can be still turned on by apps, you just need to enable the permission (allow always vs. allow only when app is running in foreground).
2. Call recording is working in regions where it's not forbidden by privacy laws.
3. FBE is much better because it allows you to start the phone with basic service without using the password. Not sure why do you consider FDE to be superior.
4. Well, you can try to build your own Android 7 ROM from old sources, but you're going to have a fun time adapting to vendor partition/proprietary files created for Android 10 or 11. Also using several years old code which is not supported or patched anymore is quite interesting approach to security.
Click to expand...
Click to collapse
Maybe it's regional or SROMs based issue, but the vendor of the app said it's not allowed on Android 10 and on, and i did confirmed the permission to turn on WiFi automatically, but maybe there's some other settings that i missed and that guy was wrong, i'd love if you can show how to enable it globally and/or to just the auto file sync i use, cause i tried many times even with manual syncing [by clicking the Sync button when WiFi is off, it started and turn it off automatically on Android 7.0.. Of course also for time interval based sync]..
Jeff1976A1 said:
Maybe it's regional or SROMs based issue, but the vendor of the app said it's not allowed on Android 10 and on, and i did confirmed the permission to turn on WiFi automatically, but maybe there's some other settings that i missed and that guy was wrong, i'd love if you can show how to enable it globally and/or to just the auto file sync i use, cause i tried many times even with manual syncing [by clicking the Sync button when WiFi is off, it started and turn it off automatically on Android 7.0.. Of course also for time interval based sync]..
Click to expand...
Click to collapse
App info, permissions.
_mysiak_ said:
App info, permissions.
Click to expand...
Click to collapse
Hi.. Thanks for your reply.. i did that already before, but still it doesn't work.. i use FolderSync, that currently in my old Android 7.0 device, does syncing when i click Sync from within the app, while i was totally offline [Data and Wifi] so it turned on the Wifi connection [Specific home network], and also on Scheduled i inserted the Allowed Networks SSID [Which BTW when i turn on WiFi manually and it does sync it with GDrive, it say on top 'Unknown SSID' for case it matters {Had the feeling that it very much does}], I also switced it on in Data and WiFI limit it does on that Security app, which i guess is kind of firewall, and BTW i remember like 5-6 years ago i had the Lenovo A8 "Golden Worrier" has that same kind of Security app built in with firewall and all that, but still manually at least, as i checked, it doesn't turn on the Wifi via FolderSync app.. Got a strong feeling it's due to that Unknown SSID stuff or that Security app.. Could it be?..
Jeff1976A1 said:
Hi.. Thanks for your reply.. i did that already before, but still it doesn't work.. i use FolderSync, that currently in my old Android 7.0 device, does syncing when i click Sync from within the app, while i was totally offline [Data and Wifi] so it turned on the Wifi connection [Specific home network], and also on Scheduled i inserted the Allowed Networks SSID [Which BTW when i turn on WiFi manually and it does sync it with GDrive, it say on top 'Unknown SSID' for case it matters {Had the feeling that it very much does}], I also switced it on in Data and WiFI limit it does on that Security app, which i guess is kind of firewall, and BTW i remember like 5-6 years ago i had the Lenovo A8 "Golden Worrier" has that same kind of Security app built in with firewall and all that, but still manually at least, as i checked, it doesn't turn on the Wifi via FolderSync app.. Got a strong feeling it's due to that Unknown SSID stuff or that Security app.. Could it be?..
Click to expand...
Click to collapse
FolderSync doesn't turn Wifi On automatically, this feature seems to be missing in the app. But I've just tested with Tasker and it is able to turn Wifi On and Off, so it's not a problem of Android version.
For Allowed SSID feature in FolderSync you must enable permanent location access.
Btw. I see no point in turning Wifi Off at any point, it uses so little power that there is next to none benefit in doing it. If you insist on some kind of automation, use Tasker in a fully controlled manner.
_mysiak_ said:
FolderSync doesn't turn Wifi On automatically, this feature seems to be missing in the app. But I've just tested with Tasker and it is able to turn Wifi On and Off, so it's not a problem of Android version.
For Allowed SSID feature in FolderSync you must enable permanent location access.
Btw. I see no point in turning Wifi Off at any point, it uses so little power that there is next to none benefit in doing it. If you insist on some kind of automation, use Tasker in a fully controlled manner.
Click to expand...
Click to collapse
Well your first argument is actually not tru, FolderSync does turns on Wifi automatically as i do for like 4 years with my older Galaxy s6 [Great dev BTW, Samsung's first 64 bit device i thinks] running now Android 7.0, and also the other day and im sure if ill try this right now it will actually turning on WiFi from off mode and also automatically closed it when done syncing, but no matter what i did it doesn't doing it on the XM10T5G, and it both updated to the latest FolderSync version the one with those tiles.. so it must be something with the operation system.. again it's some kind of Andro/MIUI OS so it has to do with one of them..
About the SSID, i did confirmed the location access all the time [not just when it's used] on the Security app, is there any other place that i should enable location or any other settings that may be relating to this?..
And really? you don't see the point in using Wifi? It's much more faster, secure, and reliable than data.. of course i don't care if it'll be 4G or 5G even better to sync, but obviously not any connection, but thanks for the Tasker Tip, i'll try that.. i've heared that somewhere i think from the gut of FolderSync..
And BTW, the call recording is legal in my country, so i did also many years but here only after trying several apps i found Cube ACR working good.. And also, some apps ask you if you confirm that Call recording is legal in your country but of course if you flash custom or different ROM, the system obviously can never tell..
Peace..
Jeff1976A1 said:
Well your first argument is actually not tru, FolderSync does turns on Wifi automatically as i do for like 4 years with my older Galaxy s6 [Great dev BTW, Samsung's first 64 bit device i thinks] running now Android 7.0, and also the other day and im sure if ill try this right now it will actually turning on WiFi from off mode and also automatically closed it when done syncing, but no matter what i did it doesn't doing it on the XM10T5G, and it both updated to the latest FolderSync version the one with those tiles.. so it must be something with the operation system.. again it's some kind of Andro/MIUI OS so it has to do with one of them..
About the SSID, i did confirmed the location access all the time [not just when it's used] on the Security app, is there any other place that i should enable location or any other settings that may be relating to this?..
And really? you don't see the point in using Wifi? It's much more faster, secure, and reliable than data.. of course i don't care if it'll be 4G or 5G even better to sync, but obviously not any connection, but thanks for the Tasker Tip, i'll try that.. i've heared that somewhere i think from the gut of FolderSync..
And BTW, the call recording is legal in my country, so i did also many years but here only after trying several apps i found Cube ACR working good.. And also, some apps ask you if you confirm that Call recording is legal in your country but of course if you flash custom or different ROM, the system obviously can never tell..
Peace..
Click to expand...
Click to collapse
I see no point in turning wifi OFF.
Anyway, good luck finding/building your perfect Andoid 7 ROM.
_mysiak_ said:
I see no point in turning wifi OFF.
Anyway, good luck finding/building your perfect Andoid 7 ROM.
Click to expand...
Click to collapse
Again security and energy reasons.. Think about it..
Anyway i barely know how to flash ROM, so i'm very far from building a custom one.. But at start you said it's impossible to install / flash an older Android ROM to it [XM10T5G], so you say it's possible with custom ROM?
Jeff1976A1 said:
Again security and energy reasons.. Think about it..
Anyway i barely know how to flash ROM, so i'm very far from building a custom one.. But at start you said it's impossible to install / flash an older Android ROM to it [XM10T5G], so you say it's possible with custom ROM?
Click to expand...
Click to collapse
Again - not possible, such ROM doesn't exist.