I read that the Pixel 4 and 4 XL have DisplayPort Alt Mode disabled on the Kernel and was wondering if anyone has made or started working on a custom Kernel that enables this feature? Is it even possible? Yeah I know I can use Chromecast or cast via WiFi but nothing beats a direct HDMI connection due to virtually no input lag etc.
Thanks.
marsfan89 said:
I read that the Pixel 4 and 4 XL have DisplayPort Alt Mode disabled on the Kernel and was wondering if anyone has made or started working on a custom Kernel that enables this feature? Is it even possible? Yeah I know I can use Chromecast or cast via WiFi but nothing beats a direct HDMI connection due to virtually no input lag etc. Thanks.
Click to expand...
Click to collapse
Based on no replies in over 65 views I would say no, but you may have better luck posting this over in the Kernels section. That, and maybe linking to the piece you found on this disabled feature waiting to be unlocked.
Still no progress on this? This would be the only reason for me to root.
shagggggggy said:
Still no progress on this? This would be the only reason for me to root.
Click to expand...
Click to collapse
No, unfortunately its still not possible. It is 100% hardware capable and only blocked at the Kernel level unlike Pixel 1-3. It's entirely possible to one day have it enabled but right now it doesn't seem to be a priority for any of the great Kernel devs we have here which is completely understandable. Although there are a bunch of us that would love to have this feature, its still a niche feature and so devs priorities are focused on the broader features for us. I read that Google MAY activate the display out over usb when stadia launched as that would make a lot of sense to tout as a feature but that hasn't happened yet and I'm not holding my breath.
Honestly, I'd be ecstatic just to have display out over WiFi (Miracast) enabled and there is a magisk module that enabled it on Pie for the Pixel 2-3, I loved having that when I was still on my Pixel 2 XL.
1dopewrx05 said:
No, unfortunately its still not possible. It is 100% hardware capable and only blocked at the Kernel level unlike Pixel 1-3. It's entirely possible to one day have it enabled but right now it doesn't seem to be a priority for any of the great Kernel devs we have here which is completely understandable. Although there are a bunch of us that would love to have this feature, its still a niche feature and so devs priorities are focused on the broader features for us. I read that Google MAY activate the display out over usb when stadia launched as that would make a lot of sense to tout as a feature but that hasn't happened yet and I'm not holding my breath.
Honestly, I'd be ecstatic just to have display out over WiFi (Miracast) enabled and there is a magisk module that enabled it on Pie for the Pixel 2-3, I loved having that when I was still on my Pixel 2 XL.
Click to expand...
Click to collapse
Where did you get the information that the pixel 4 xl (I have only tried it on the XL model since I don’t own the regular one) is actually capable of this?
I have seen none other source of information than the google commits disabling it in the kernel.
I enabled it at kernel level and all I got was a freeze when the phone booted.
Freak07 said:
Where did you get the information that the pixel 4 xl (I have only tried it on the XL model since I don’t own the regular one) is actually capable of this?
I have seen none other source of information than the google commits disabling it in the kernel.
I enabled it at kernel level and all I got was a freeze when the phone booted.
Click to expand...
Click to collapse
I've read it from multiple sources. I was seeing it quite a bit shortly after the phone was released and haven't seen anything about it recently but I've found an article for you showing the information I was talking about:
Via AndroidPolice:
"A commit has been found in the Android source code that disables DisplayPort over the USB Type-C port in the Pixel 4. The commit message simply reads, "Disable DP function."
The link to the whole article is:
"Pixel 4 has USB video output disabled in software" https://www.androidpolice.com/2019/11/03/pixel-4-has-usb-video-output-disabled-in-software/?amp
It's possible Google never finished it implementing the feature or maybe it didn't work fully before they had to release the phone. Is there any chance you want to PM me a copy of your kernel with it enabled? I have a couple of ideas on trying to get it fully enabled and working semi-reliably.
1dopewrx05 said:
I've read it from multiple sources. I was seeing it quite a bit shortly after the phone was released and haven't seen anything about it recently but I've found an article for you showing the information I was talking about:
Via AndroidPolice:
"A commit has been found in the Android source code that disables DisplayPort over the USB Type-C port in the Pixel 4. The commit message simply reads, "Disable DP function."
The link to the whole article is:
"Pixel 4 has USB video output disabled in software" https://www.androidpolice.com/2019/11/03/pixel-4-has-usb-video-output-disabled-in-software/?amp
It's possible Google never finished it implementing the feature or maybe it didn't work fully before they had to release the phone. Is there any chance you want to PM me a copy of your kernel with it enabled? I have a couple of ideas on trying to get it fully enabled and working semi-reliably.
Click to expand...
Click to collapse
Yes all these articles base back to the commit that actually disables the function in the display driver. There´s no source of information that the Pixel 4 XL is actually capable of doing it. I think that´s why they disabled it.
So I don´t understand why you think the phone is 100% hardware capable of doing this, if you have no other information.
The phone freezes before the bootanimation comes up when the commit is reverted. So I´m not sure what you want to do that doesn´t involve recompiling the kernel with additional changes of your own.
I´d need to recompile the kernel as I did this already last year and the kernel is by now incompatible with the current firmware.
Freak07 said:
Yes all these articles base back to the commit that actually disables the function in the display driver. There´s no source of information that the Pixel 4 XL is actually capable of doing it. I think that´s why they disabled it.
So I don´t understand why you think the phone is 100% hardware capable of doing this, if you have no other information.
The phone freezes before the bootanimation comes up when the commit is reverted. So I´m not sure what you want to do that doesn´t involve recompiling the kernel with additional changes of your own.
I´d need to recompile the kernel as I did this already last year and the kernel is by now incompatible with the current firmware.
Click to expand...
Click to collapse
Yeah that wasn't the actual source I heard that from, like I said this was coming up on a year ago so I'll likely never find the sources.
Look, I mean you're most likely right about it not being a possibility, I know you have more knowledge of this stuff than I do so I'll take your word. I gave up on this a long time ago I was just replying to the OP with what I remembered. I have Chromecasts on my house TV's so it's not even relevant to me anymore.
What's your view on enabling display-out over WiFi? Outside of a Chromecast I mean. There was a magisk module for the Pixel 2 on Pie that re-enabled the Miracast support that Google disabled.
Related
Im looking for a way to run a camera control software for nikon DSLRs on my note. However theese apps all are tablet software for android 3+. They run just fine on the cyanogen alpha, but that rom is too far from daily use even for bleeding edge enthusiasts, like most of us here. Thus, until now I have been forced to reflash everytime i need to control the camera with the phone.
Now several ICS ROMs have emerged, but those I have tested, though stable enough, refuse to work with USB on the go devices. The notice about the OTG cable show up all right ob them all, but they do not detect anything attached to the other end of it like in gingerbread and cyanogen alpha.
Is there a way i could fix this by copying some files from the cyanogen ROM over to one of the other ROMs? If so, which files would that be?
It's a kernel related issue. This means that we have to wait for Chainfire to get back from his vacation and tackle this problem. Or some other kernel dev.
Nothing we can do about it right now.
Ok, though i am a novice in the world of android hacking, that is not the case, at all, regarding linux kernel hacking. Setting up a cross compiling dev environment and moving a driver from one kernel source to another or compiling a module is actually less unfamiliar to me than trixing around with binaries from different beta releases. If that is the case i might be up to it. But that would only work if the source code, or at very least the kernel headers are available for the kernels used in the betas.
Sent from my GT-N7000 using XDA App
I'm currently in search of a ROM with most of functionality Sony claimed to be. So far i've discovered, that Wireless Mirroring works well on CM-based ROM (ParanoidAndroid, for sure) and do not work on stock-based. But i'm happy to be wrong. So, here's my question: does work Wireless Mirroring in this ROM and AR-Effects by Sony ?
Blue2s said:
I'm currently in search of a ROM with most of functionality Sony claimed to be. So far i've discovered, that Wireless Mirroring works well on CM-based ROM (ParanoidAndroid, for sure) and do not work on stock-based. But i'm happy to be wrong. So, here's my question: does work Wireless Mirroring in this ROM and AR-Effects by Sony ?
Click to expand...
Click to collapse
I can confirm once you're rooted wireless mirroring doesn't work on stock roms (I can't talk about ore rooting, since I never got to try before I rooted) I'm not entirely sure if it's fully functional on AOSP ROMs, but give it a try, no harm in trying
AnrgKrshn said:
I can confirm once you're rooted wireless mirroring doesn't work on stock roms (I can't talk about ore rooting, since I never got to try before I rooted) I'm not entirely sure if it's fully functional on AOSP ROMs, but give it a try, no harm in trying
Click to expand...
Click to collapse
If it was so simple... WifiMirroring stops working after one of OTA official updates.After that, app demands some sort of HDCP, which most of TV's do not provide, without option to turn HDCP off. "Most of TV's" - because on one os Samsung's TVs i've got mirroring running, and that was on rooted official ROM. On AOSP ROM this function surely runs well on ParanoidAndroid CM11, but i presume success is in fact, that AOSP ROMs use self-made Wireless Mirroring. And in the same time function don't work on modified KK rom with HDCP=OFF setting. That's unAlgebraic, if you ask me.
Blue2s said:
If it was so simple... WifiMirroring stops working after one of OTA official updates.After that, app demands some sort of HDCP, which most of TV's do not provide, without option to turn HDCP off. "Most of TV's" - because on one os Samsung's TVs i've got mirroring running, and that was on rooted official ROM. On AOSP ROM this function surely runs well on ParanoidAndroid CM11, but i presume success is in fact, that AOSP ROMs use self-made Wireless Mirroring. And in the same time function don't work on modified KK rom with HDCP=OFF setting. That's unAlgebraic, if you ask me.
Click to expand...
Click to collapse
I've tried multiple times on smart TVs with a rooted ROM and have ALWAYS got a HDCP error. Samsung and Sony TVs. However, the store representative used his Note 3 to mirror and it worked instantly. Till date, I haven't been able to get screen mirroring to work on my phone. Haven't tried AOSP though.
I also haven't found a way to bypass HDCP (turn it off) Maybe it works on AOSP because they don't use HDCP as you said, or we have broken HDCP certificates on modified stock ROMs, I'm not entirely sure which.
Many people across many devices have had issues with HDCP on rooted devices. There was a a workaround, but it involves manual modification of files, and I'm not really one to try mass code changing. A quick Google shows many people reporting loss of mirroring with the same error, on rooted devices.
The explanation as to why it's happening, could be any of the things above. I think the workaround is disabling the HDCP check. So that may be the fix.
AnrgKrshn said:
I've tried multiple times on smart TVs with a rooted ROM and have ALWAYS got a HDCP error. Samsung and Sony TVs. However, the store representative used his Note 3 to mirror and it worked instantly. Till date, I haven't been able to get screen mirroring to work on my phone. Haven't tried AOSP though.
I also haven't found a way to bypass HDCP (turn it off) Maybe it works on AOSP because they don't use HDCP as you said, or we have broken HDCP certificates on modified stock ROMs, I'm not entirely sure which.
Many people across many devices have had issues with HDCP on rooted devices. There was a a workaround, but it involves manual modification of files, and I'm not really one to try mass code changing. A quick Google shows many people reporting loss of mirroring with the same error, on rooted devices.
The explanation as to why it's happening, could be any of the things above. I think the workaround is disabling the HDCP check. So that may be the fix.
Click to expand...
Click to collapse
As i wrote before, i've got Mirroring running on official rooted ROM with Samsung TV, so far only one model, but still- it shows that root is not an issue. But support of many TV's void after OTA update for sure.
Blue2s said:
As i wrote before, i've got Mirroring running on official rooted ROM with Samsung TV, so far only one model, but still- it shows that root is not an issue. But support of many TV's void after OTA update for sure.
Click to expand...
Click to collapse
Which ota are you talking about?
OTA- OverTheAir - is update system, which updates firmware and even kernel in some cases, via WiFi or mobile internet, without use of PC. In my case, i'm talking about official ota update, after which WifiMirroring stops working.
Blue2s said:
OTA- OverTheAir - is update system, which updates firmware and even kernel in some cases, via WiFi or mobile internet, without use of PC. In my case, i'm talking about official ota update, after which WifiMirroring stops working.
Click to expand...
Click to collapse
I know what OTA is, mate, I meant, the update to which firmware version?
I don't know. All that I remember, it's that I was on 4.3, and that bug is applied on multiple devices, not only for Z1
Q&A for CyanogenMod 12 - Lollipop - Pre-Nightly Shakeout
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 CyanogenMod 12 - Lollipop - Pre-Nightly Shakeout. 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!
CM12 dead space on launcher screen
Installed this shakeout looks great!
I have unusable screen real estate on the left and right sidesnof the launcher is this normal?
Resolution and DPI changes in lollipop
With root enabled you can use ResUI from the themes and apps section and DPI changer from the play store. You have to have root enabled for the changes to take effect I believe.
If u make ur grid size custom and scroll down so its the largest, a 9x8 I believe, it uses most of it
ROM Pershoot TF701T 20150227 testing results
so, since I have less than 10 posts, this will automatically be put in the wrong Q&A section. Anyway, I'm running Pershoot's new TF701T Rom 20150227 and want to give some feedback since I also ran the prior version. If an OP would kindly take this restriction off so I can actually post in the correct thread...
This version is much more responsive than the 20150205 Rom. I am using this Rom with Google Keyboard to type this voice message! Everything seems to run very smooth YouTube is good. WiFi is quick, internet and embedded videos are great! Google Apps work fine. Almost 24 hours now and no slow down, battery use is normal and it barely uses any power during sleep.
The only thing I see missing is screen mirroring. Until that is implemented, it can't be a daily user for me. I have not tested GPS yet, & I wonder about the Nvidia specific drivers for the Tegra 4. I do not play games much and have not had a chance to test that either. All in all, it seems like a very stable base!
Miracast & Screen casting
Any idea when screen casting will be implemented? I have been playing with the latest build and all seems great! The settings menu is quite confusing and took forever to find the keyboard settings... I also find it difficult to find other settings that are common in prior Android versions. Is there anyway to keep the KitKat version of settings? ?
getting there... CM 12 testing
okay, so I'm using the current cm 12 20150309. I actually get to enable miracast and see receiving devices but I cannot connect to them. I have tried with a LC Smart TV and a Roku streaming stick which neither will connect. Also, the stock 442 version will only connect to the lc tv and not the streaming stick... the Roku is still in beta just to let you know.
this is also getting posted in the wrong thread again! hopefully the OP will recognize this and I don't think that is even recognizing that this is the third posting of mine! My posts are not getting counted...
i've enabled wifi display and protected buffers support for it (also enabled in the CM11 build); ensure its checked (in casting; wireless display). i have no way to test. you'd need to post logs and i'll see what i can do, or submit a patch which sorts it out to gerrit, against the known working device.
more testing... 20150311
Once again I am using the latest cm build with Google keyboard to voice type this message. this build is definitely quick and responsive and miracast or screencasting is almost functional. I have tried about a hundred combinations of settings on both receiving devices and this tablet without success. Also I noticed that I cannot connect to an external Bluetooth speaker without the launcher crashing when trying to use the volume keys. The Bluetooth speaker will connect but there is no sound and it crashes the launcher. Seems to me as a buffering or memory allocation issue since both devices want to connect but cannot finalize the handshake.
Let me know what the easiest way to pull log files off of this tablet is and I will see what I can help with... ???
Take note of the 'Known Issues' (on DB), and you will see the workaround for the Bluetooth issue (un-select Phone Audio on the device's BT settings).
Pull a logcat while trying to connect to a known working Miracast device and post it.
Thx.
10-4...
pershoot said:
Take note of the 'Known Issues' (on DB), and you will see the workaround for the Bluetooth issue (un-select Phone Audio on the device's BT settings).
Pull a logcat while trying to connect to a known working Miracast device and post it.
Thx.
Click to expand...
Click to collapse
will do, I'll see what I can get you tomorrow for some fresh logs... ?
Howdy strangers...!
So, I am just playing around with Pershoot's new cm 12 OS and I am wondering why hundreds of people view this thread and nobody contributes! There must be many more people out there that can provide debugging and log information than just me! Let's all work together and get this done ASAP! Don't be intimidated to contribute to this thread! We need all the input everybody has on everything!?
K94U said:
So, I am just playing around with Pershoot's new cm 12 OS and I am wondering why hundreds of people view this thread and nobody contributes! There must be many more people out there that can provide debugging and log information than just me! Let's all work together and get this done ASAP! Don't be intimidated to contribute to this thread! We need all the input everybody has on everything!?
Click to expand...
Click to collapse
Havent miracast or something like this. BT speaker is working here. Atm i havent any problem with this build (except ui battery symbol of dock isnt visible)
Gesendet von meinem LG-D855 mit Tapatalk
20150313 miracast log
Here is the log file... Tried to connect miracast to the LG TV 3 times in different ways. Also, the stock browser has no upload options for attaching documents to XDA posts. I got my Bluetooth speaker working... Thanks!!!
I do not know why this log file ended up having such a long name but it is the original file.
20150313 miracast log for Roku
Here is the log file for trying to connect miracast to the Roku streaming stick. I tried 3 times and it tries to connect then the roku immediately goes back to the home screen. Thanks!
more casting info
I have a verizon wireless galaxy s4 that connects to both the LG TV and the Roku streaming stick just fine running the latest stock 442. The latest stock version 11. 4.1. 29 for this tablet will only connect to the LG TV after numerous tries but not the Roku. ?
I haven't looked at your log as of yet. but please only post the one from the device that is known working against stock.
Please also post a log from stock of it working.
Thx.
Just noticed this week while I was away that when a USB is plugged into the dock everything works however there is no notification that it is plugged in and there is no way to eject it. Also if you close the dock while it is plugged in and then open it it tells you that it was not safely removed. I am not sure if that is stock behavior or not and it is not really an issue if I could eject it properly.
Turn off MTP and you should get eject options in storage.
pershoot said:
Turn off MTP and you should get eject options in storage.
Click to expand...
Click to collapse
pick up 3/15 and you'll get the extended options for USB in storage.
I've managed to enable WiFi on lenok by coping several files from bass and kernel with the wlan driver enabled, courtesy of intersectRaven. It seems to be working without any issues, so here's a flashable ZIP.
Requirements:
LG G watch R running the 5.1.1 update (LDZ22D). This wasn't tested on anything else.
TWRP installed as custom recovery
unlocked bootloader
Instructions:
(optional) make backup of system and boot in TWRP, so you can revert changes my ZIP makes
install intersectRaven kernel 20150530_08XX or newer. Doesn't matter if you choose single or dual core. I recommend reading through his thread first. kernel thread | link to folder with his lenok kernels
reboot into TWRP
flash lenok_wifi_zip-XX.zip (you can get it to the device with adb push lenok_wifi_zip-XX.zip /sdcard/)
reboot the device
Whenever you flash anything that modifies boot.img (say, a kernel), you have to re-flash lenok_wifi_zip-XX.zip file.
Needless to say, this breaks OTAs - when next Android update hits, you'll have to restore from backup or flash whole images.
Downloads:
0c8d3fa95380e7ac75201bed0cab85fb lenok_wifi_zip-02.zip
AndroidFileHost: https://www.androidfilehost.com/?fid=23991606952612046
Basketbuild: https://basketbuild.com/filedl/devs?dev=Tassadar&dl=Tassadar/lenok/lenok_wifi_zip-02.zip
dev-host: http://d-h.st/FLCk
Notes, warnings...
You're flashing this from your own will. This file brings over bunch of files & bits of firmware from Urbane, something might break. There's also a chance LG didn't just do this because "hey, buy urbane, it has WiFi!" and there is some actual reason why WiFi was not enabled on lenok - including some HW difficulties. Using this method to enable WiFi has the potential to cause permanent HW damage. Also keep in mind that WiFi on G Watch R might not have been certified for use.
It's working just fine for me so far, but I haven't been using it for very long. The voice recognition is slower than on BT and less reliable (sometimes even claiming "offline"), not sure if that's "how's it's supposed to be" or if it is bug specific to this mod. Some guessing about what might be causing it in this post.
One last thing - please, don't discuss common "halp I don't know how to install recovery/flash kernel/flash a ZIP" problems in this thread and focus only on issues related to the mod itself. Thanks.
Lets start the party, flashing right now
Flashed everything. Now the G Watch R reboots into TWRP or maybe Bootloader. But no normal reboot into android?
Glad to see that someone mirrored what Paul O'Brien did for me back in the N1 days. He gave me the ROM and I gave the kernel to enable FM radio.
Flashed stock boot.img, recovery.img and system.img to get the G Watch R back to work. Now I'm waiting for comments with working hack until I'm gonna try it again..
tried,everything seems good,got the wifi
Why the kernel requirement?
SferaDev said:
Why the kernel requirement?
Click to expand...
Click to collapse
The stock kernel doesn't have wifi drivers enabled. That release of intersectRaven's kernel is based on urbane's sources, and has all the drivers enabled.
Tasssadar said:
The stock kernel doesn't have wifi drivers enabled. That release of intersectRaven's kernel is based on urbane's sources, and has all the drivers enabled.
Click to expand...
Click to collapse
Alright seems logical, G Watch R had the hardware inside but no certification in the device specs. I'll give it a try later. Thanks, if you need anything don't hesitate to ping me.
SferaDev
Hi firstly thank you for this mod!
I have a simple and noob question is it normal that with wifi turned on i can receive notifications but i can't answer them?
fabioio said:
Hi firstly thank you for this mod!
I have a simple and noob question is it normal that with wifi turned on i can receive notifications but i can't answer them?
Click to expand...
Click to collapse
What do you mean "answer"? Voice recognition? I've noticed that it is much slower and less reliable (sometimes even claiming "offline"), not sure if that's the same on Urbane or not. Urbane has different mic configuration and different sound firmware files, which don't work on lenok - so lenok might be missing some optimizations that make voice recognition over wifi faster (BT and WiFi use different "formats" of data sent into the cloud, that's why it might matter how they are "prepared" on the device by the FW).
Or maybe it is the same on Urbane? I really dunno, get some users with watches that have wifi by default and make them tell us
Tasssadar said:
What do you mean "answer"? Voice recognition? I've noticed that it is much slower and less reliable (sometimes even claiming "offline"), not sure if that's the same on Urbane or not. Urbane has different mic configuration and different sound firmware files, which don't work on lenok - so lenok might be missing some optimizations that make voice recognition over wifi faster (BT and WiFi use different "formats" of data sent into the cloud, that's why it might matter how they are "prepared" on the device by the FW).
Or maybe it is the same on Urbane? I really dunno, get some users with watches that have wifi by default and make them tell us
Click to expand...
Click to collapse
yeah i meant that! i actually can't use voice recognition i always get some connection problem!
Why would they disable it when it clearly works?
Works great
123421342 said:
Why would they disable it when it clearly works?
Click to expand...
Click to collapse
Clearly for market reason. LG want everybody buy urbane.They are sucks.
akaHardison said:
Clearly for market reason. LG want everybody buy urbane.They are sucks.
Click to expand...
Click to collapse
wifi certifications take time and cost money, that is probably why
suljo94 said:
wifi certifications take time and cost money, that is probably why
Click to expand...
Click to collapse
You should know that this watch has already have certification it needed.FCC has already approved this watch using WiFi.
No LG bashing guys, keep in clean in here. This is about the mod, nothing else.
What could actually be permanently damaged by this? I want WiFi, but not bad enough to risk damage to the radio chip. In other words is it a generic warning, or is there actually an above-typical risk of damage?
Koopa777 said:
No LG bashing guys, keep in clean in here. This is about the mod, nothing else.
What could actually be permanently damaged by this? I want WiFi, but not bad enough to risk damage to the radio chip. In other words is it a generic warning, or is there actually an above-typical risk of damage?
Click to expand...
Click to collapse
It's just that we have no idea. While I'm inclined to believe lenok doesn't have wifi just due to marketing reasons, there might be some key differences between bass and lenok that I don't know about, and that _might_ cause some problems later.
Great work Tasssadar!
Regarding the voice recognition "issue" I've noticed it works pretty decently if I'm close to the WiFi AP but gets worse and worse as I move away, so it might have something to do with WiFi signal quality.
Shame on you, LG.
I'm considering to enable the encryption on my device (currently running LOS 14.1) but I'd like to know more about the impact on performance and battery life beforehand. As far as I know the S5 mini doesn't has hardware support for AES therefore encryption/decryption has to be done by the CPU.
It would be nice if you could share your experiences.
The normal s5 and every other Smartphone with no armv8 support is with android 5 and above extremly slow. Is on this rom you use (android 7.1) no aes encryption activated? How is it possible to deactivate it on any phone? I thought, that only Google maybe deactivated it in Android 8.1 and 9, when they activate automatically the GO version for a phone.
Then you can instal every new android Version with the most old Smartphones, when you can disable aes without this extremly performance loosing!?
rainbowxxl said:
The normal s5 and every other Smartphone with no armv8 support is with android 5 and above extremly slow. Is on this rom you use (android 7.1) no aes encryption activated? How is it possible to deactivate it on any phone? I thought, that only Google maybe deactivated it in Android 8.1 and 9, when they activate automatically the GO version for a phone.
Then you can instal every new android Version with the most old Smartphones, when you can disable aes without this extremly performance loosing!?
Click to expand...
Click to collapse
Sorry to be so harsh, but could you please try to express yourself a little better? Just a request tho. Answering your question (partly, if I got the question right): I think armv8 isn't the most important factor for AES en-/decryption. As far as I know AES is hardware accelerated, a little how Graphics are accelerated by the GPU. I'm not completely sure, but I think AES acceleration should be available on the Exynos 3470, at least to some extent.
EDIT: Ok, AIDA64 tells me that AES is actually not supported, so yes, encrypted storage would probably slow the phone down quite a bit.
EDIT2: Ok, I'm officially dumb
I didn't even read the OP properly, the creator already mentioned there is no hardware AES! Don't post late in the evening I guess (around midnight here)...:victory:
Pokemetti2 said:
Sorry to be so harsh, but could you please try to express yourself a little better? Just a request tho. Answering your question (partly, if I got the question right): I think armv8 isn't the most important factor for AES en-/decryption. As far as I know AES is hardware accelerated, a little how Graphics are accelerated by the GPU. I'm not completely sure, but I think AES acceleration should be available on the Exynos 3470, at least to some extent.
EDIT: Ok, AIDA64 tells me that AES is actually not supported, so yes, encrypted storage would probably slow the phone down quite a bit.
EDIT2: Ok, I'm officially dumb
I didn't even read the OP properly, the creator already mentioned there is no hardware AES! Don't post late in the evening I guess (around midnight here)...:victory:
Click to expand...
Click to collapse
But whats the way to delete it from every smartphone and rom? Maybe always the same way like with the nexus 6 (custom kernel) or tools like this FDE.AI or one of these kernel manager apps in the store i think. here A few articles and solutions for this big and for the most people unknown problem:
XDA Disk Encryption: The Good and The Slow: https://www.xda-developers.com/disk-encryption-the-good-and-the-slow/
A way for nexus 6 phones, benchmarks and rare good infos: https://www.androidauthority.com/nexus-6-device-encryption-performance-568629/
Android 5.0 Lollipop encryption severely impacts performance: https://betanews.com/2014/11/21/android-5-0-lollipop-encryption-severely-impacts-performance/
A way from google itself, but YEARS to late (search for Google Adiantum, this news article is in german): https://www.heise.de/security/meldu...elung-fuer-schwache-Hardware-vor-4304013.html
A list of the ARM Architectures and the features (in wikipedia you see it too, that the Cortex A-7 and A-15 has no hardware encryption): https://developer.arm.com/ip-products/processors/cortex-a
I think there isn't a universal removal script or anything comparable, why do you want to delete it so badly? As far as I understand the kernel and sometimes the ROM are reaponsible for encryption, and I don't know any patcher which universally removes/disables it, sorry.
Pokemetti2 said:
why do you want to delete it so badly?
Click to expand...
Click to collapse
in every smartphone i had, yes. a galaxy s5 was slower than a s4.
rainbowxxl said:
in every smartphone i had, yes. a galaxy s5 was slower than a s4.
Click to expand...
Click to collapse
You don't have to delete it for that, just disable it. And no ROM on the S5 mini has encryption enabled by default, so you would have to go to the settings and enable it manually to encrypt the device. On some other phones it is enabled by default, but mostly on newer devices on which it doesn't really matter, where performance is unaffected. There is no need to delete anything on an S5 mini, and probably not on the S5 either. Decryption is ok to have on those phones, as long as it is not activated.