Fixes/Enhancements:
Voice – HD Voice enhancements.
Audio – Audio clipping when using headphones at higher levels has been addressed.
Application Storage – Enables market application installation onto the SD card.
Wallpaper modifications – One wallpaper was removed and 2 new wallpapers were added..
Messaging Known Issue – Unfortunately Messaging has Stopped error has been resolved.
All I needed to see.
The update is ok, but one thing I notice after rooting and putting on TWRP then installing Hotspot mod it throws my phone into bootloops on the Sprint splash screen. I had to reflash my phone back to MDL for now.
The update is ok, but one thing I notice after rooting and putting on TWRP then installing Hotspot mod it throws my phone into bootloops on the Sprint splash screen. I had to reflash my phone back to MDL for now.
The issue is NOT fixed all hey did was make the settings panel dark Grey now. Still smears. Won't ever change unless Samsung adjusts the black level to not be pixels turned off.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
---------- Post added at 03:08 AM ---------- Previous post was at 03:01 AM ----------
Seems that this is no different than what the international s4 has had for a couple weeks.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
So if you trip the secure boot piece you are stuck on whatever modem you were on? No way to change it from there on? Or is there some way to unlock the nand to allow you to still flash a new modem?It means that if you install something that trips the "Secure Boot Status" then the device will in turn lock the boot loader and modem firmware into place which will not allow us to update the modem or boot loader which isn't a big deal because that means less hard bricks due to bootloaders and modems being borked.
Sent from my SPH-L720 using Tapatalk 4 Beta
Well the good thing on this update we can move apps to sd and they added a new smart pause toggle,
Sent from my SPH-L720 using Tapatalk 2
Hello all, i'd like to answer some of your questions if possible. I've been working with Knox as a QA resource with a 3rd party testing a implementation of Knox and i'd like to answer a few points that have been brought up.
- Activating Knox (knoxifying) a device locks the bootloader and activates the Knox Agent. The Knox agent will consistently force close and attempt to unsinstall any SU style application. The bootloader in Odin mode scans bootloader, PDA, Modem, CSC files for a unique Knox Samsung certificate.
- After activating Knox you will see that the Secure Boot Mode changes to 'Enforcing'
- There is no known way to reverse it back into a Permissive state and remove the Knox agent. Conversations with Samsung have proved less then useful on this subject however i've heard rumor they are coming up with a way to reverse it.
- Knox cannot be activated soley on its own.
- MDM vendors will still have full control of device even when Knox is activated. Knox is not meant to Sandbox a devices MDM vendor. It is meant to sandbox secure corp data, MDM vendors will more then likely still have samples and controls of device.
I had previously made a thread on reddit.com/r/android which I answered a lot of questions there as well however I cannot link to it due to using a throwaway account.
Hello all, i'd like to answer some of your questions if possible. I've been working with Knox as a QA resource with a 3rd party testing a implementation of Knox and i'd like to answer a few points that have been brought up.
- Activating Knox (knoxifying) a device locks the bootloader and activates the Knox Agent. The Knox agent will consistently force close and attempt to unsinstall any SU style application. The bootloader in Odin mode scans bootloader, PDA, Modem, CSC files for a unique Knox Samsung certificate.
- After activating Knox you will see that the Secure Boot Mode changes to 'Enforcing'
- There is no known way to reverse it back into a Permissive state and remove the Knox agent. Conversations with Samsung have proved less then useful on this subject however i've heard rumor they are coming up with a way to reverse it.
- Knox cannot be activated soley on its own.
- MDM vendors will still have full control of device even when Knox is activated. Knox is not meant to Sandbox a devices MDM vendor. It is meant to sandbox secure corp data, MDM vendors will more then likely still have samples and controls of device.
I had previously made a thread on reddit.com/r/android which I answered a lot of questions there as well however I cannot link to it due to using a throwaway account.