Database Users

[Q][Dev] Screen Off Programmatically

Hey guys,
Im diving into the android sdk and I've been searching google to find a way to turn the screen off after i click a button in my app. I can not figure out how to get the screen to turn off.. I know you can turn brightness to 0 but i want it off not 0. Does anybody offer guidance, im not looking for a hand out. Is PowerManager really the only thing that can accomplish this? If so I'll go play with that more.
Thanks in Advance!!

You have to use the PowerManager, look here for goToSleep(time) function
http://developer.android.com/reference/android/os/PowerManager.html#goToSleep(long)
To get a PowerManager instance, use a context to get the system service:
Code:
PowerManager pm = (PowerManager) getSystemService(Context.POWER_SERVICE);
pm.goToSleep(System.currentTimeMillis() + 10000); // add 10 seconds to let other apps go sleeping

andy572 said:
You have to use the PowerManager, look here for goToSleep(time) function
http://developer.android.com/reference/android/os/PowerManager.html#goToSleep(long)
To get a PowerManager instance, use a context to get the system service:
Code:
PowerManager pm = (PowerManager) getSystemService(Context.POWER_SERVICE);
pm.goToSleep(System.currentTimeMillis() + 10000); // add 10 seconds to let other apps go sleeping
Click to expand...
Click to collapse
I get a force close everytime I do this. This is the same sample in the reference google offers..

can you post a piece of logcat?

08-09 14:25:57.408: ERROR/AndroidRuntime(3327): FATAL EXCEPTION: main
08-09 14:25:57.408: ERROR/AndroidRuntime(3327): java.lang.SecurityException: Neither user 10182 nor current process has android.permission.DEVICE_POWER.
08-09 14:25:57.408: ERROR/AndroidRuntime(3327): at android.os.Parcel.readException(Parcel.java:1322)
08-09 14:25:57.408: ERROR/AndroidRuntime(3327): at android.os.Parcel.readException(Parcel.java:1276)
08-09 14:25:57.408: ERROR/AndroidRuntime(3327): at android.os.IPowerManager$Stub$Proxy.goToSleep(IPowerManager.java:367)
08-09 14:25:57.408: ERROR/AndroidRuntime(3327): at android.os.PowerManager.goToSleep(PowerManager.java:469)
08-09 14:25:57.408: ERROR/AndroidRuntime(3327): at com.recreation.togglebrightness.AutoBrightness_toggleActivity.onSensorChanged(AutoBrightness_toggleActivity.java:139)
08-09 14:25:57.408: ERROR/AndroidRuntime(3327): at android.hardware.SensorManager$ListenerDelegate$1.handleMessage(SensorManager.java:539)
08-09 14:25:57.408: ERROR/AndroidRuntime(3327): at android.os.Handler.dispatchMessage(Handler.java:99)
08-09 14:25:57.408: ERROR/AndroidRuntime(3327): at android.os.Looper.loop(Looper.java:143)
08-09 14:25:57.408: ERROR/AndroidRuntime(3327): at android.app.ActivityThread.main(ActivityThread.java:4293)
08-09 14:25:57.408: ERROR/AndroidRuntime(3327): at java.lang.reflect.Method.invokeNative(Native Method)
08-09 14:25:57.408: ERROR/AndroidRuntime(3327): at java.lang.reflect.Method.invoke(Method.java:507)
08-09 14:25:57.408: ERROR/AndroidRuntime(3327): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
08-09 14:25:57.408: ERROR/AndroidRuntime(3327): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
08-09 14:25:57.408: ERROR/AndroidRuntime(3327): at dalvik.system.NativeStart.main(Native Method)
HTML:
<permission android:name="android.permission.DEVICE_POWER"/>
^^I do have that in my Manifest file..

see this error:
java.lang.SecurityException: Neither user 10182 nor current process has android.permission.DEVICE_POWER.
has your app compiled/signed with system privileges or is the device rooted?
might be this can help you:
http://stackoverflow.com/questions/...e-android-application-with-system-permissions

I do not have my current device rooted..[Sensation 4G]
I am only running this application straight to my phone from eclipse.
How would i compile with system privileges?? without having to sign my apk everytime?

you have a Android.mk "makefile",
look for the line "LOCAL_CERTIFICATE" - possibly it helps to set the value to "platform"

I noticed in this project of mine i did not have the Android.mk file! However, in other project builds of mine i DO!!
Edit:
HTML:
LOCAL_PATH:= $(call my-dir)
include $(CLEAR_VARS)
# Only build apk if this package is added to CUSTOM_MODLUES in buildspec.mk
LOCAL_MODULE_TAGS := optional
# Only compile source java files in this apk.
LOCAL_SRC_FILES := $(call all-java-files-under, src)
LOCAL_PACKAGE_NAME := toggle
# Make the app build against the current SDK
LOCAL_SDK_VERSION := current
include $(BUILD_PACKAGE)

do you build on windows or linux?
sorry, i only build custom roms under linux env, so i dont have a clue what windows with (possibly) eclipse is doing in build process.

andy572 said:
do you build on windows or linux?
sorry, i only build custom roms under linux env, so i dont have a clue what windows with (possibly) eclipse is doing in build process.
Click to expand...
Click to collapse
im building under windows. But if need be i can copy over to linux ubuntu and finish the app there..

only method to screen off without signing with system key is to use the device administrator (requires 2.2+) and calling the lockNow method.
you can also start a black activity in fullscreen mode and change the displaytimout to a minimum. when you receive the screenOff broadcast then, you can restore the old display timeout & finish your activity

[Q] Can't turn on neither wifi nor bluetooth

I've been reading a lot over the web to find information about this issue I'm having, but by no means I could solve this issue.
I just got my S5. Here's a (very short) excerpt of the
Code:
adb shell dumpstate
command:
Code:
[ril.product_code]: [SM-G900MZWPZTO]
[ro.product.model]: [SM-G900M]
When I got the phone, the first thing I did, as it was used, was to factory-reset it, because I didn't want any data from the previous user. I did this through the phone UI, not from within recovery (wipe cache/wipe data).
Once reset was done, I put in my microSIM and turned it back on. I had no way to test wifi and bluetooth at that point, so I used the mobile network to update my personal info, etc.
By the end of the day, I got home and tried to turn on wireless. The normal behavior of the indicator when turning wifi on is GRAY->DARK GREEN->GREEN, but the phone goes GRAY->DARK GREEN and doesn't go further. It stays in DARK GREEN for a couple minutes, then it goes back to GRAY.
The same happens to bluetooth. The only difference is that bluetooth takes less time to go back to GRAY.
The Android version installed was 4.2.2.
There was an offer to update Android, so I thought that could solve the problem, so I updated Android to 5.0 over mobile network (no wifi, remember?).
After the update, wifi still didn't work. By dialing *#1234#, I noticed this:
Code:
AP: G900MUBU1BOC4
CP: G900MUBU1BOC3
CSC: G900MZTO1BOC4
AP and CP are different. Shouldn't they be equal?
Anyway, after seeing the update didn't solve the problem, I did a downgrade, again with no success. The *#1234# now shows this:
Code:
AP: G900MUBU1ANCE
CP: G900MUBU1ANCE
CSC: G900MZTO1ANCE
Wifi still don't go on.
I also tried to flash two Android 5.0 (Lollipop) versions available to my country (got them from sammobile dot com):
Code:
/firmwares/download/45787/G900MUBU1BOC4_G900MZTO1BOC4_ZTO/
Code:
/firmwares/download/44412/G900MUBU1BOC1_G900MZTO1BOC1_ZTO/
None worked.
I used ODIN for all updates. Some background on how to use ODIN can be found here:
www dot droidforums dot net threads guide-complete-samsung-odin-v3-xx-options-and-reference.278159
While inspecting the phone's dumpstate, I found this:
Code:
01-01 10:56:42.519 732 967 E WifiHW : ##################### set firmware type 0 #####################
01-01 10:56:42.519 252 914 I WifiHW : wifi_change_fw_path(): fwpath = /system/etc/wifi/bcmdhd_sta.bin
01-01 10:56:42.519 252 914 E WifiHW : Cannot open "/data/.cid.info": No such file or directory
01-01 10:56:42.519 252 914 I WifiHW : wifi_change_nvram_path() = /system/etc/wifi/nvram_net.txt
01-01 10:56:42.519 252 914 E WifiHW : TEMP_FAILURE_RETRY complete
.
.
.
01-01 10:56:42.529 732 967 E WifiStateMachine: Unable to change interface settings: java.lang.IllegalStateException: command '16
01-01 10:56:42.529 732 967 E WifiHW : supplicant_name : p2p_supplicant
01-01 10:56:42.529 732 967 D WifiMonitor: startMonitoring(wlan0) with mConnected = false
The following also appears from time to time along the log:
Code:
01-01 10:56:53.549 732 967 E WifiHW : Supplicant not running, cannot connect
I read a lot about wifi connections dropping, but none about not being able to turn on wifi on Samsung Galaxy S5. Got to some similar threads on S4 and previous versions, but none about S5, so I decided to post here.
Some questions arises:
1. Am I the only one having this issue?
2. Can it be hardware-related? And if yes, is there any way to check this?
3. Could the Factory Reset have done something nasty to wifi config files? I read some suggestions to erase wpa_supplicant config files.
4. When flashing a new rom, is any data kept inside the phone or everything is erased?
5. Is there a way to reset the wifi only or updating its firmware?
Thanks for helping!

There could be 3 causes for this...
1. Kernel WIFI modules doesn't match the kernel.
2. Hardware problem
3. Not sure about this since I'm just new to samsung but it could also be from a corrupt EFS partition.
But to further troubleshoot this problem can you do this for me?
1. Install terminal emulator from playstore.
2. execute this command from there
Code:
svc wifi enable
See if it shows some errors, warnings or whatever text it will print.
if not type logcat and paste here the last 100 to 150 lines of the output.
htimsxela said:
I've been reading a lot over the web to find information about this issue I'm having, but by no means I could solve this issue.
I just got my S5. Here's a (very short) excerpt of the
Code:
adb shell dumpstate
command:
Code:
[ril.product_code]: [SM-G900MZWPZTO]
[ro.product.model]: [SM-G900M]
When I got the phone, the first thing I did, as it was used, was to factory-reset it, because I didn't want any data from the previous user. I did this through the phone UI, not from within recovery (wipe cache/wipe data).
Once reset was done, I put in my microSIM and turned it back on. I had no way to test wifi and bluetooth at that point, so I used the mobile network to update my personal info, etc.
By the end of the day, I got home and tried to turn on wireless. The normal behavior of the indicator when turning wifi on is GRAY->DARK GREEN->GREEN, but the phone goes GRAY->DARK GREEN and doesn't go further. It stays in DARK GREEN for a couple minutes, then it goes back to GRAY.
The same happens to bluetooth. The only difference is that bluetooth takes less time to go back to GRAY.
The Android version installed was 4.2.2.
There was an offer to update Android, so I thought that could solve the problem, so I updated Android to 5.0 over mobile network (no wifi, remember?).
After the update, wifi still didn't work. By dialing *#1234#, I noticed this:
Code:
AP: G900MUBU1BOC4
CP: G900MUBU1BOC3
CSC: G900MZTO1BOC4
AP and CP are different. Shouldn't they be equal?
Anyway, after seeing the update didn't solve the problem, I did a downgrade, again with no success. The *#1234# now shows this:
Code:
AP: G900MUBU1ANCE
CP: G900MUBU1ANCE
CSC: G900MZTO1ANCE
Wifi still don't go on.
I also tried to flash two Android 5.0 (Lollipop) versions available to my country (got them from sammobile dot com):
Code:
/firmwares/download/45787/G900MUBU1BOC4_G900MZTO1BOC4_ZTO/
Code:
/firmwares/download/44412/G900MUBU1BOC1_G900MZTO1BOC1_ZTO/
None worked.
I used ODIN for all updates. Some background on how to use ODIN can be found here:
www dot droidforums dot net threads guide-complete-samsung-odin-v3-xx-options-and-reference.278159
While inspecting the phone's dumpstate, I found this:
Code:
01-01 10:56:42.519 732 967 E WifiHW : ##################### set firmware type 0 #####################
01-01 10:56:42.519 252 914 I WifiHW : wifi_change_fw_path(): fwpath = /system/etc/wifi/bcmdhd_sta.bin
01-01 10:56:42.519 252 914 E WifiHW : Cannot open "/data/.cid.info": No such file or directory
01-01 10:56:42.519 252 914 I WifiHW : wifi_change_nvram_path() = /system/etc/wifi/nvram_net.txt
01-01 10:56:42.519 252 914 E WifiHW : TEMP_FAILURE_RETRY complete
.
.
.
01-01 10:56:42.529 732 967 E WifiStateMachine: Unable to change interface settings: java.lang.IllegalStateException: command '16
01-01 10:56:42.529 732 967 E WifiHW : supplicant_name : p2p_supplicant
01-01 10:56:42.529 732 967 D WifiMonitor: startMonitoring(wlan0) with mConnected = false
The following also appears from time to time along the log:
Code:
01-01 10:56:53.549 732 967 E WifiHW : Supplicant not running, cannot connect
I read a lot about wifi connections dropping, but none about not being able to turn on wifi on Samsung Galaxy S5. Got to some similar threads on S4 and previous versions, but none about S5, so I decided to post here.
Some questions arises:
1. Am I the only one having this issue?
2. Can it be hardware-related? And if yes, is there any way to check this?
3. Could the Factory Reset have done something nasty to wifi config files? I read some suggestions to erase wpa_supplicant config files.
4. When flashing a new rom, is any data kept inside the phone or everything is erased?
5. Is there a way to reset the wifi only or updating its firmware?
Thanks for helping!
Click to expand...
Click to collapse

I believe, (Don't quote me on this), if the EFS partition was corrupted or lost, the phone would not have any radio functionality including voice and text etc
Also I 'think' the IMEI is also included on that partition, so *#06# should come up blank if it was the EFS partition causing the problem
But again, this is just what I've also picked up in the short time I've been with my S5 so could be missing something

[Solved], but the hard way
I took the device to Samsung and they said there was a problem on the main board (?), so they replaced it for a new one. I don't think I'm going to complain about it. Although I think that could be fixed somehow, replacing was probably easier. I said "the hard way" on the title, meaning it was a "brute force" fix. It is a pity I wasn't able to keep the old board for experimentation...
Thanks for your replies, guys. I didn't even expect replies and got yours and so complete! Thanks a lot!

Fingerprint Sensor not surviving reboot

All apps I have that use the fingerprint sensor only work until I reboot the phone, any idea why? Here's some logs
Code:
-----
App Version: 1.13.0
App Version Code: 46
OS Version: 3.18.31-perf-g336fddd-00001-g0103837
API Level: 25
Android Version: 7.1.1
Device Manufacturer: motorola
Device Codename: perry_f
Device Model: Moto E (4)
Stacktrace: de.devland.masterpassword.util.FingerprintException: Could not create cipher for encryption. Seems your device is unsupported.
at de.devland.masterpassword.util.FingerprintUtil.getCipher(FingerprintUtil.java:226)
at de.devland.masterpassword.util.FingerprintUtil.initDecryptCipher(FingerprintUtil.java:121)
at de.devland.masterpassword.ui.LoginFragment.onResume(LoginFragment.java:117)
at android.support.v4.app.Fragment.performResume(Fragment.java:2238)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1346)
at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManager.java:1528)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1595)
at android.support.v4.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:2914)
at android.support.v4.app.FragmentController.dispatchResume(FragmentController.java:223)
at android.support.v4.app.FragmentActivity.onResumeFragments(FragmentActivity.java:509)
at android.support.v4.app.FragmentActivity.onPostResume(FragmentActivity.java:498)
at android.support.v7.app.AppCompatActivity.onPostResume(AppCompatActivity.java:172)
at android.app.Activity.performResume(Activity.java:6815)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3427)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3490)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2749)
at android.app.ActivityThread.-wrap12(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1490)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6165)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:888)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:778)
Caused by: android.security.keystore.KeyPermanentlyInvalidatedException: Key permanently invalidated
at android.security.KeyStore.getInvalidKeyException(KeyStore.java:724)
at android.security.KeyStore.getInvalidKeyException(KeyStore.java:748)
at android.security.keystore.KeyStoreCryptoOperationUtils.getInvalidKeyExceptionForInit(KeyStoreCryptoOperationUtils.java:54)
at android.security.keystore.KeyStoreCryptoOperationUtils.getExceptionForCipherInit(KeyStoreCryptoOperationUtils.java:89)
at android.security.keystore.AndroidKeyStoreCipherSpiBase.ensureKeystoreOperationInitialized(AndroidKeyStoreCipherSpiBase.java:265)
at android.security.keystore.AndroidKeyStoreCipherSpiBase.engineInit(AndroidKeyStoreCipherSpiBase.java:148)
at javax.crypto.Cipher.tryTransformWithProvider(Cipher.java:2973)
at javax.crypto.Cipher.tryCombinations(Cipher.java:2884)
at javax.crypto.Cipher$SpiAndProviderUpdater.updateAndGetSpiAndProvider(Cipher.java:2789)
at javax.crypto.Cipher.chooseProvider(Cipher.java:956)
at javax.crypto.Cipher.init(Cipher.java:1329)
at javax.crypto.Cipher.init(Cipher.java:1267)
at de.devland.masterpassword.util.FingerprintUtil.getCipher(FingerprintUtil.java:222)
... 23 more
android.security.keystore.KeyPermanentlyInvalidatedException: Key permanently invalidated
at android.security.KeyStore.getInvalidKeyException(KeyStore.java:724)
at android.security.KeyStore.getInvalidKeyException(KeyStore.java:748)
at android.security.keystore.KeyStoreCryptoOperationUtils.getInvalidKeyExceptionForInit(KeyStoreCryptoOperationUtils.java:54)
at android.security.keystore.KeyStoreCryptoOperationUtils.getExceptionForCipherInit(KeyStoreCryptoOperationUtils.java:89)
at android.security.keystore.AndroidKeyStoreCipherSpiBase.ensureKeystoreOperationInitialized(AndroidKeyStoreCipherSpiBase.java:265)
at android.security.keystore.AndroidKeyStoreCipherSpiBase.engineInit(AndroidKeyStoreCipherSpiBase.java:148)
at javax.crypto.Cipher.tryTransformWithProvider(Cipher.java:2973)
at javax.crypto.Cipher.tryCombinations(Cipher.java:2884)
at javax.crypto.Cipher$SpiAndProviderUpdater.updateAndGetSpiAndProvider(Cipher.java:2789)
at javax.crypto.Cipher.chooseProvider(Cipher.java:956)
at javax.crypto.Cipher.init(Cipher.java:1329)
at javax.crypto.Cipher.init(Cipher.java:1267)
at de.devland.masterpassword.util.FingerprintUtil.getCipher(FingerprintUtil.java:222)
at de.devland.masterpassword.util.FingerprintUtil.initDecryptCipher(FingerprintUtil.java:121)
at de.devland.masterpassword.ui.LoginFragment.onResume(LoginFragment.java:117)
at android.support.v4.app.Fragment.performResume(Fragment.java:2238)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1346)
at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManager.java:1528)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1595)
at android.support.v4.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:2914)
at android.support.v4.app.FragmentController.dispatchResume(FragmentController.java:223)
at android.support.v4.app.FragmentActivity.onResumeFragments(FragmentActivity.java:509)
at android.support.v4.app.FragmentActivity.onPostResume(FragmentActivity.java:498)
at android.support.v7.app.AppCompatActivity.onPostResume(AppCompatActivity.java:172)
at android.app.Activity.performResume(Activity.java:6815)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3427)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3490)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2749)
at android.app.ActivityThread.-wrap12(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1490)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6165)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:888)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:778)

mendelgordon said:
All apps I have that use the fingerprint sensor only work until I reboot the phone, any idea why? Here's some logs
Code:
-----
App Version: 1.13.0
App Version Code: 46
OS Version: 3.18.31-perf-g336fddd-00001-g0103837
API Level: 25
Android Version: 7.1.1
Device Manufacturer: motorola
Device Codename: perry_f
Device Model: Moto E (4)
Stacktrace: de.devland.masterpassword.util.FingerprintException: Could not create cipher for encryption. Seems your device is unsupported.
at de.devland.masterpassword.util.FingerprintUtil.getCipher(FingerprintUtil.java:226)
at de.devland.masterpassword.util.FingerprintUtil.initDecryptCipher(FingerprintUtil.java:121)
at de.devland.masterpassword.ui.LoginFragment.onResume(LoginFragment.java:117)
at android.support.v4.app.Fragment.performResume(Fragment.java:2238)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1346)
at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManager.java:1528)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1595)
at android.support.v4.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:2914)
at android.support.v4.app.FragmentController.dispatchResume(FragmentController.java:223)
at android.support.v4.app.FragmentActivity.onResumeFragments(FragmentActivity.java:509)
at android.support.v4.app.FragmentActivity.onPostResume(FragmentActivity.java:498)
at android.support.v7.app.AppCompatActivity.onPostResume(AppCompatActivity.java:172)
at android.app.Activity.performResume(Activity.java:6815)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3427)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3490)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2749)
at android.app.ActivityThread.-wrap12(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1490)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6165)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:888)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:778)
Caused by: android.security.keystore.KeyPermanentlyInvalidatedException: Key permanently invalidated
at android.security.KeyStore.getInvalidKeyException(KeyStore.java:724)
at android.security.KeyStore.getInvalidKeyException(KeyStore.java:748)
at android.security.keystore.KeyStoreCryptoOperationUtils.getInvalidKeyExceptionForInit(KeyStoreCryptoOperationUtils.java:54)
at android.security.keystore.KeyStoreCryptoOperationUtils.getExceptionForCipherInit(KeyStoreCryptoOperationUtils.java:89)
at android.security.keystore.AndroidKeyStoreCipherSpiBase.ensureKeystoreOperationInitialized(AndroidKeyStoreCipherSpiBase.java:265)
at android.security.keystore.AndroidKeyStoreCipherSpiBase.engineInit(AndroidKeyStoreCipherSpiBase.java:148)
at javax.crypto.Cipher.tryTransformWithProvider(Cipher.java:2973)
at javax.crypto.Cipher.tryCombinations(Cipher.java:2884)
at javax.crypto.Cipher$SpiAndProviderUpdater.updateAndGetSpiAndProvider(Cipher.java:2789)
at javax.crypto.Cipher.chooseProvider(Cipher.java:956)
at javax.crypto.Cipher.init(Cipher.java:1329)
at javax.crypto.Cipher.init(Cipher.java:1267)
at de.devland.masterpassword.util.FingerprintUtil.getCipher(FingerprintUtil.java:222)
... 23 more
android.security.keystore.KeyPermanentlyInvalidatedException: Key permanently invalidated
at android.security.KeyStore.getInvalidKeyException(KeyStore.java:724)
at android.security.KeyStore.getInvalidKeyException(KeyStore.java:748)
at android.security.keystore.KeyStoreCryptoOperationUtils.getInvalidKeyExceptionForInit(KeyStoreCryptoOperationUtils.java:54)
at android.security.keystore.KeyStoreCryptoOperationUtils.getExceptionForCipherInit(KeyStoreCryptoOperationUtils.java:89)
at android.security.keystore.AndroidKeyStoreCipherSpiBase.ensureKeystoreOperationInitialized(AndroidKeyStoreCipherSpiBase.java:265)
at android.security.keystore.AndroidKeyStoreCipherSpiBase.engineInit(AndroidKeyStoreCipherSpiBase.java:148)
at javax.crypto.Cipher.tryTransformWithProvider(Cipher.java:2973)
at javax.crypto.Cipher.tryCombinations(Cipher.java:2884)
at javax.crypto.Cipher$SpiAndProviderUpdater.updateAndGetSpiAndProvider(Cipher.java:2789)
at javax.crypto.Cipher.chooseProvider(Cipher.java:956)
at javax.crypto.Cipher.init(Cipher.java:1329)
at javax.crypto.Cipher.init(Cipher.java:1267)
at de.devland.masterpassword.util.FingerprintUtil.getCipher(FingerprintUtil.java:222)
at de.devland.masterpassword.util.FingerprintUtil.initDecryptCipher(FingerprintUtil.java:121)
at de.devland.masterpassword.ui.LoginFragment.onResume(LoginFragment.java:117)
at android.support.v4.app.Fragment.performResume(Fragment.java:2238)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1346)
at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManager.java:1528)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1595)
at android.support.v4.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:2914)
at android.support.v4.app.FragmentController.dispatchResume(FragmentController.java:223)
at android.support.v4.app.FragmentActivity.onResumeFragments(FragmentActivity.java:509)
at android.support.v4.app.FragmentActivity.onPostResume(FragmentActivity.java:498)
at android.support.v7.app.AppCompatActivity.onPostResume(AppCompatActivity.java:172)
at android.app.Activity.performResume(Activity.java:6815)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3427)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3490)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2749)
at android.app.ActivityThread.-wrap12(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1490)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6165)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:888)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:778)
Click to expand...
Click to collapse
I'm not good with logs, but does it simply not work or force log you out? LastPass often gives me "fingerprint not recognized" and I have to re-log back in and set up my fingerprint to login once more.

AidenSurvival said:
I'm not good with logs, but does it simply not work or force log you out? LastPass often gives me "fingerprint not recognized" and I have to re-log back in and set up my fingerprint to login once more.
Click to expand...
Click to collapse
It Force logs me out and makes me log back in with a password everytime I reboot

HavocOS_2.9 Fastboot ROM

This file is exclusively prepared by BN_P
for
Asus Zenfone Max M2 (X01AD). It is havoc Pie 2.9 on pie vendor, Firmware-JP-16.2018.1910.52.
How to ::
1. Confirm your device model as above.
2. No need to be worried on which build your device is presently. This Rom can be flashed on any build. Also seperate unlock bootloader not required... It will b done by flash process automatically.
3. Only for windows users, flashing can be done in windows only.
Before start flashing,
Unzip the downloaded file. Put it in a folder in desktop.
There is a file named "system+vendor.zip" or something like that, unzip that, refer readme guide for details.
Put those above unzipped .img files in the main folder i.e same location of flash_all.cmd.
4. Put your device in fastboot mode, connect to PC and run the flash_all.cmd, just double click on it.
5. Follow the pop up screen.
6. Data erase will be required after flashing before boot.
Detailed process available in readme file inside.
Best of luck
This ROM is included
TWRP+Magisk
opengapps pico
Gcam
Ampere app
Viper sound mod
Google Phone Dialer
Safetynet Fixed
Bugs::
You tell me.
Thanks to::
@vincent for HavocOS GSI image.
[MENTION=268073]topjhonwu for magisk
Link for file...
https://www.androidfilehost.com/?w=files&flid=293310
NB Drop a line in comment section mentioning your feedback / bugs / experience

Updated version V2
Changelog
Magisk19.3 (magisk20 creating problem)
Updated gapps
Fastboot flashscript errors removed
added viper sound mod
updated twrp3.3.1-0
(NB:: Need to unzip system.zip, vendor.zip,recovery.zip,boot.zip to get corrsponding img files before flash)

what are the differences from havoc 2.9 gsi? (besides TWRP + Magisk20.1 opengapps pico Gcam Ampere app Google Phone Dialer Safetynet Fixed)
Gcam version? all work fine?

KLozhev said:
what are the differences from havoc 2.9 gsi? (besides TWRP + Magisk20.1 opengapps pico Gcam Ampere app Google Phone Dialer Safetynet Fixed)
Gcam version? all work fine?
Click to expand...
Click to collapse
It is a fastboot rom.... Can b flashed thru fastboot mode without twrp/custom recovery. No need to unlock bootloader seperately.
Everything will b done thru flashing script... U can say
Its a one click install rom.

[email protected] said:
It is a fastboot rom.... Can b flashed thru fastboot mode without twrp/custom recovery. No need to unlock bootloader seperately.
Everything will b done thru flashing script... U can say
Its a one click install rom.
Click to expand...
Click to collapse
thx

[email protected] said:
TWRP+Magisk20.1
Gcam
Click to expand...
Click to collapse
Gcam not work
without root
in TWRP 3.2.3(!) not work, mtp, adb, microsb
in archive missing generate_image.exe
Code:
934 I ActivityManager: START u0 {act=android.content.pm.action.REQUEST_PERMISSIONS pkg=com.google.android.packageinstaller cmp=com.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity (has extras)} from uid 10230
10-28 16:42:04.510 1532 3811 D StorageManagerService: UID 10230 is actively using camera; letting them defy reserved cached data
--------- beginning of crash
10-28 16:42:04.570 8619 8665 E AndroidRuntime: FATAL EXCEPTION: GoogleApiHandler
10-28 16:42:04.570 8619 8665 E AndroidRuntime: Process: com.google.android.GoogleCamera, PID: 8619
10-28 16:42:04.570 8619 8665 E AndroidRuntime: java.lang.SecurityException: GoogleCertificatesRslt: not whitelisted: pkg=com.google.android.GoogleCamera, sha1=61ed377e85d386a8dfee6b864bd85b0bfaa5af81, atk=false, ver=14848037.true
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:1950)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1918)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1868)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at ksy.a(Unknown Source:35)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at krq.a(Unknown Source:98)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at lar.run(Unknown Source:54)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:873)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Looper.loop(Looper.java:193)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:65)
10-28 16:42:04.620 1532 8279 W ActivityManager: Force finishing activity com.google.android.GoogleCamera/com.android.camera.CameraLauncher
10-28 16:42:04.639 1532 8279 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1005 com.android.server.am.AppErrors.crashApplicationInner:469 com.android.server.am.AppErrors.crashApplication:392 com.android.server.am.ActivityManagerService.handleApplicationCrashInner:15805 com.android.server.am.ActivityManagerService.handleApplicationCrash:15771
10-28 16:42:04.644 1532 1585 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
10-28 16:42:04.644 1532 1585 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
--------- beginning of main
10-28 16:42:04.693 949 8767 I chatty : uid=1047(cameraserver) /system/bin/cameraserver expire 3 lines
10-28 16:42:04.708 1532 5145 I WindowManager: WIN DEATH: Window{a97e4c3 u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher}
10-28 16:42:04.708 1532 8108 I ActivityManager: Process com.google.android.GoogleCamera (pid 8619) has died: vis +99TOP
10-28 16:42:04.710 1532 1588 I chatty : uid=1000(system) ActivityManager expire 8 lines
10-28 16:42:04.710 795 8752 I chatty : uid=1047(cameraserver) [email protected] expire 4 lines
10-28 16:42:04.713 1532 3227 I WindowManager: WIN DEATH: Window{263b47e u0 Toast}
10-28 16:42:04.713 1532 3227 I chatty : uid=1000(system) Binder:1532_3 expire 1 line
10-28 16:42:04.732 831 1286 W SurfaceFlinger: Attempting to set client state on removed layer: com.google.android.GoogleCamera/com.android.camera.CameraLauncher#0
10-28 16:42:04.732 831 1286 W SurfaceFlinger: Attempting to destroy on removed layer: com.google.android.GoogleCamera/com.android.camera.CameraLauncher#0
10-28 16:42:04.736 795 8785 I chatty : uid=1047(cameraserver) [email protected] expire 2 lines
10-28 16:42:04.739 831 906 E BufferQueueProducer: [SurfaceView - com.google.android.GoogleCamera/com.android.camera.CameraLauncher#0] queueBuffer: BufferQueue has been abandoned
10-28 16:42:04.743 815 840 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-28 16:42:04.743 815 840 E ANDR-PERF-OPTSHANDLER: Perflock resource /sys/devices/system/cpu/cpu0/cpufreq/schedutil/hispeed_load not supported
10-28 16:42:04.743 815 840 E ANDR-PERF-OPTSHANDLER: Perflock resource /sys/devices/system/cpu/cpu0/cpufreq/schedutil/hispeed_freq not supported
10-28 16:42:04.749 1532 1587 W ActivityManager: Slow operation: 142ms so far, now at startProcess: returned from zygote!
10-28 16:42:04.752 746 746 I Zygote : Process 8619 exited due to signal (9)
10-28 16:42:04.763 8821 8821 I chatty : uid=10230(u0_a230) expire 4 lines
10-28 16:42:04.763 1532 1587 W ActivityManager: Slow operation: 156ms so far, now at startProcess: done updating battery stats
10-28 16:42:04.763 1532 1587 W ActivityManager: Slow operation: 156ms so far, now at startProcess: building log message
10-28 16:42:04.763 1532 1587 I ActivityManager: Start proc 8821:com.google.android.GoogleCamera:crash_report/u0a230 for service com.google.android.GoogleCamera/com.google.android.apps.camera.app.silentfeedback.SilentFeedbackService
10-28 16:42:04.763 1532 1587 W ActivityManager: Slow operation: 156ms so far, now at startProcess: starting to update pids map
10-28 16:42:04.763 1532 1587 W ActivityManager: Slow operation: 156ms so far, now at startProcess: done updating pids map
10-28 16:42:04.768 831 1286 E BufferQueueProducer: [SurfaceView - com.google.android.GoogleCamera/com.android.camera.CameraLauncher#0] queueBuffer: BufferQueue has been abandoned
10-28 16:42:04.769 949 1913 I chatty : uid=1047(cameraserver) HwBinder:949_3 expire 12 lines
10-28 16:42:04.771 4271 4271 D Launcher.Utilities: onLauncherStart: 0
10-28 16:42:04.773 1532 3811 W ActivityManager: Unable to start service Intent { act=com.android.launcher3.WINDOW_OVERLAY dat=app://ch.deletescape.lawnchair.ci:10038?v=7&cv=9 pkg=com.google.android.googlequicksearchbox } U=0: not found
10-28 16:42:04.803 831 3852 E BufferQueueProducer: [SurfaceView - com.google.android.GoogleCamera/com.android.camera.CameraLauncher#0] queueBuffer: BufferQueue has been abandoned
10-28 16:42:04.815 795 1794 I chatty : uid=1047(cameraserver) HwBinder:795_1 expire 122 lines
10-28 16:42:04.818 815 840 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-28 16:42:04.853 795 8804 I chatty : uid=1047(cameraserver) [email protected] expire 1 line
10-28 16:42:04.893 795 8841 I chatty : uid=1047(cameraserver) [email protected] expire 2 lines
10-28 16:42:04.894 795 8842 I chatty : uid=1047(cameraserver) [email protected] expire 2 lines
10-28 16:42:04.895 795 8843 I chatty : uid=1047(cameraserver) [email protected] expire 3 lines
10-28 16:42:04.896 795 8844 I chatty : uid=1047(cameraserver) [email protected] expire 2 lines
10-28 16:42:04.903 8821 8821 E AndroidRuntime: FATAL EXCEPTION: main
10-28 16:42:04.903 8821 8821 E AndroidRuntime: Process: com.google.android.GoogleCamera:crash_report, PID: 8821
10-28 16:42:04.903 8821 8821 E AndroidRuntime: java.lang.SecurityException: GoogleCertificatesRslt: not whitelisted: pkg=com.google.android.GoogleCamera, sha1=61ed377e85d386a8dfee6b864bd85b0bfaa5af81, atk=false, ver=14848037.true
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:1950)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1918)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1868)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at ksy.a(Unknown Source:35)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at krq.a(Unknown Source:98)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at kzw.a(Unknown Source:98)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at laa.run(Unknown Source:21)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at kwm.run(Unknown Source:7)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at java.lang.Thread.run(Thread.java:764)
10-28 16:42:04.908 1532 8820 W ActivityManager: Process com.google.android.GoogleCamera has crashed too many times: killing!
10-28 16:42:04.910 1532 8820 I ActivityManager: Killing 8821:com.google.android.GoogleCamera:crash_report/u0a230 (adj 500): crash
10-28 16:42:04.914 795 8846 I chatty : uid=1047(cameraserver) [email protected] expire 5 lines
10-28 16:42:04.918 795 8848 I chatty : uid=1047(cameraserver) [email protected] expire 2 lines
10-28 16:42:04.932 1532 1585 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
10-28 16:42:04.933 1532 1585 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
10-28 16:42:04.937 802 843 I SDM : ResourceImpl::SetMaxBandwidthMode: new bandwidth mode=0
10-28 16:42:04.947 439 439 E SELinux : avc: denied { find } for interface=vendor.lineage.camera.motor::ICameraMotor sid=u:r:cameraserver:s0 pid=949 scontext=u:r:cameraserver:s0 tcontext=u:object_r:default_android_hwservice:s0 tclass=hwservice_manager permissive=0

THANK YOU!!!!!!

[email protected] said:
This file is exclusively prepared by BN_P
for
Asus Zenfone Max M2 (X01AD). It is havoc Pie 2.9 on pie vendor, Firmware-JP-16.2018.1910.52.
How to ::
1. Confirm your device model as above.
2. No need to be worried on which build your device is presently. This Rom can be flashed on any build.
3. Only for windows users, flashing can be done in windows only.
Before start flashing,
There is a file named "system+vendor.zip", unzip that, it will generate two file i.e. system.img and vendor.img
Put the above two .img files in the main folder i.e same location of flash_all.cmd.
4. Put your device in fastboot mode, connect to PC and run the flash_all.cmd, just double click on it.
5. Follow the pop up screen.
6. Data erase will be required after flashing before boot.
Best of luck
This ROM is included
TWRP+Magisk20.1
opengapps pico
Gcam
Ampere app
Google Phone Dialer
Safetynet Fixed
Bugs::
You tell me.
Thanks to::
@vincent for HavocOS GSI image.
[MENTION=268073]topjhonwu for magisk
Link for file
https://www.androidfilehost.com/?fid=4349826312261607460
Click to expand...
Click to collapse
Bootloader unlocking required or not ???

Techgaming432 said:
Bootloader unlocking required or not ???
Click to expand...
Click to collapse
Not required... Unlock will b done automatically by flash script

[email protected] said:
This file is exclusively prepared by BN_P
for
Asus Zenfone Max M2 (X01AD). It is havoc Pie 2.9 on pie vendor, Firmware-JP-16.2018.1910.52.
How to ::
1. Confirm your device model as above.
2. No need to be worried on which build your device is presently. This Rom can be flashed on any build.
3. Only for windows users, flashing can be done in windows only.
Before start flashing,
There is a file named "system+vendor.zip", unzip that, it will generate two file i.e. system.img and vendor.img
Put the above two .img files in the main folder i.e same location of flash_all.cmd.
4. Put your device in fastboot mode, connect to PC and run the flash_all.cmd, just double click on it.
5. Follow the pop up screen.
6. Data erase will be required after flashing before boot.
Best of luck
This ROM is included
TWRP+Magisk20.1
opengapps pico
Gcam
Ampere app
Google Phone Dialer
Safetynet Fixed
Bugs::
You tell me.
Thanks to::
@vincent for HavocOS GSI image.
[MENTION=268073]topjhonwu for magisk
Link for file
https://www.androidfilehost.com/?fid=4349826312261607460
Click to expand...
Click to collapse
Any other ROM like MIUI or Oxygen OS have for X01AD ??

Techgaming432 said:
Any other ROM like MIUI or Oxygen OS have for X01AD ??
Click to expand...
Click to collapse
Search.... I hv not made yet

[email protected] said:
Search.... I hv not made yet
Click to expand...
Click to collapse
Please made a MIUI 10 stable ROM i will give what you want but please made a MIUI 10 stable ROM

Techgaming432 said:
Please made a MIUI 10 stable ROM i will give what you want but please made a MIUI 10 stable ROM
Click to expand...
Click to collapse
May b in future

please tell me full process step by step

nixsting said:
please tell me full process step by step
Click to expand...
Click to collapse
Follow readme file inside

An error occurred when flashing the system image it says invalid sparse system in command prompt window and skips the system image from flashing
Please tell me the solve of the problem

Techgaming432 said:
An error occurred when flashing the system image it says invalid sparse system in command prompt window and skips the system image from flashing
Please tell me the solve of the problem
Click to expand...
Click to collapse
Did u unzipped system.zip and kept the system.img file at flashing folder....?
Plz follow readme file inside.
Before flashing ensure all img files are present
Sydtem.img
Vendor
Boot
Recovery
Other firmwire images

[email protected] said:
Did u unzipped system.zip and kept the system.img file at flashing folder....?
Plz follow readme file inside.
Click to expand...
Click to collapse
Yes i extracted the system+vendor zip file and moved the system.img and vendor.img file into the same location on flashall.cmd and exactly follow the guide but the error occurres

Techgaming432 said:
Yes i extracted the system+vendor zip file and moved the system.img and vendor.img file into the same location on flashall.cmd and exactly follow the guide but the error occurres
Click to expand...
Click to collapse
Post a screenshot

[email protected] said:
Post a screenshot
Click to expand...
Click to collapse
Ok I will try another time to flash if the erro occure then i will take a screenshot of the command prompt window and send it to you by today evening

Android 11 / LineageOS 18.0

When is an unofficial 18.0 build arriving? Unofficial LineageOS 17.1 (afaneh92, Couchy) hasn't had a build in months.
Newer devices than S5 are too limited (bootloaders locked or limited cell coverage with no bootloader locking, fixed battery, sound jack missing/occupies USB charging, $$$$$, curved screen, missing notification LED, obtrusive cameras). No ROM's for bootloader unlocked Galaxy S10 5G Sprint either. So S5 is all there is.

My crystal ball is broken. But probably A11 will arrive when (and if) it is ready...

guest4711 said:
My crystal ball is broken. But probably A11 will arrive when (and if) it is ready...
Click to expand...
Click to collapse
Ok. 6 more months or so. Thanks.

LineageOS 18.0 is already
Khalvat created an alpha version for klte:
lineage-18.0-20200926-UNOFFICIAL-klte.zip
edit.
It does not boot.
edit 2
When you insert the RSA key from your PC after authorization in another ROM,
Code:
adb push adb_keys /data/misc/adb/
then you can watch the logcat.
Code:
adb logcat -b all > klte_logcat.txt
.

ttesty said:
When is an unofficial 18.0 build arriving? Unofficial LineageOS 17.1 (afaneh92, Couchy) hasn't had a build in months.
Newer devices than S5 are too limited (bootloaders locked or limited cell coverage with no bootloader locking, fixed battery, sound jack missing/occupies USB charging, $$$$$, curved screen, missing notification LED, obtrusive cameras). No ROM's for bootloader unlocked Galaxy S10 5G Sprint either. So S5 is all there is.
Click to expand...
Click to collapse
Im going to build some lineage os builds probably starting tonight

¯\_(ツ)_/¯

haggertk said:
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Clean installed ROM only to my g900i device.
Install was smooth, no problems.
There appears to be no mobile data available, otherwise a beautiful build. Testing continues...
Thanks for your work :good:

pmduper said:
Clean installed ROM only to my g900i device.
Install was smooth, no problems.
There appears to be no mobile data available, otherwise a beautiful build. Testing continues...
Thanks for your work :good:
Click to expand...
Click to collapse
Yeah, you should need a dv build for the g900i to have data... I may get to that tomorrow. I did just put a SIM in my g900w8 and have solid mobile data.
Purposely not advertising these since they are permissive, but most people know where to find them.

lineageos 18.0 ready for klte
haggertk said:
Yeah, you should need a dv build for the g900i to have data... I may get to that tomorrow. I did just put a SIM in my g900w8 and have solid mobile data.
Purposely not advertising these since they are permissive, but most people know where to find them.
Click to expand...
Click to collapse
Today I put in my SM-G900F and it works without any noticeable lag.
Thank a lot Mr Haggertk

haggertk said:
Yeah, you should need a dv build for the g900i to have data... I may get to that tomorrow. I did just put a SIM in my g900w8 and have solid mobile data.
Purposely not advertising these since they are permissive, but most people know where to find them.
Click to expand...
Click to collapse
Hi mate,
Thanks for your kltedv build.
Unfortunately I still have no mobile data with LOS18 20201130 build.
Formatted and advanced cleaned, flashed rom only. Setup was smooth. No other fault found after testing the usual.
Appreciate your work

6 months is a good original estimate (in Sept) for a stable 18.1 build for S5, though it may take some more time by the looks of it.
@haggertk posted a few Android 11.0/LineageOS 18.0 builds here (not sure about their state - think it's alpha, but good work!): https://androidfilehost.com/?w=files&flid=320376
OpenGApps only has links to 11.0 test builds for ARM64 (not ARM) - haven't used alternatives yet: https://sourceforge.net/projects/opengapps/files/arm64/test/
So BitGApps:
https://drive.google.com/u/0/uc?id=1w3EK5DpDjJWNN27LFLg-_x41fnT4GopC&export=download
Then there's TWRP 3.4:
https://dl.twrp.me/klte/twrp-3.4.0-0-klte.img.html
Magisk:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
It would help to setup a thread on the S5 Unified Development forum for all the Android 11.0 build/setup items for @haggertk's release. There's also CRDroid 11.0, but no idea about long-term builds.
Might need to move to ARM64 for future Android releases - S5 is about 7 years old, though still better than many newer devices (full root, unlocked bootloader, buttons, headphone jack, no curved screen, notification LED, $80-$100 - like the raw cost to make the new $1000 devices, etc). The S10 5G G977P would be a great ARM64 Snapdragon option (bootloader unlocked), but no ROM's yet, silly cost (about $450). Exynos is cheap, but 4G/5G reception is a guess in the US.
For now, just using latest official 17.1 - it's been pretty rock solid: https://download.lineageos.org/klte
No rush to buy a Galaxy S21 Ultra for $2000 - get more for less

Mobile data internet is not
ttesty said:
6 months is a good original estimate (in Sept) for a stable 18.1 build for S5, though it may take some more time by the looks of it.
@haggertk posted a few Android 11.0/LineageOS 18.0 builds here (not sure about their state - think it's alpha, but good work!): https://androidfilehost.com/?w=files&flid=320376
OpenGApps only has links to 11.0 test builds for ARM64 (not ARM) - haven't used alternatives yet: https://sourceforge.net/projects/opengapps/files/arm64/test/
So BitGApps:
https://drive.google.com/u/0/uc?id=1w3EK5DpDjJWNN27LFLg-_x41fnT4GopC&export=download
Then there's TWRP 3.4:
https://dl.twrp.me/klte/twrp-3.4.0-0-klte.img.html
Magisk:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
It would help to setup a thread on the S5 Unified Development forum for all the Android 11.0 build/setup items for @haggertk's release. There's also CRDroid 11.0, but no idea about long-term builds.
Might need to move to ARM64 for future Android releases - S5 is about 7 years old, though still better than many newer devices (full root, unlocked bootloader, buttons, headphone jack, no curved screen, notification LED, $80-$100 - like the raw cost to make the new $1000 devices, etc). The S10 5G G977P would be a great ARM64 Snapdragon option (bootloader unlocked), but no ROM's yet, silly cost (about $450). Exynos is cheap, but 4G/5G reception is a guess in the US.
For now, just using latest official 17.1 - it's been pretty rock solid: https://download.lineageos.org/klte
No rush to buy a Galaxy S21 Ultra for $2000 - get more for less
Click to expand...
Click to collapse
Mobile data internet is not working (((...it shows "H" and internet is not working (((((

This Android 11 release kind of works on a G900T, but it's unstable. Just change your APN and Network Type and reboot.
You can run "ping -I rmnet1 8.8.8.8" and it will ping. I get a lot of Google Maps crashes, and there's no default network route that works. It lists LTE and allows me to make calls, but there's an X. Some kind of iptables issue with not finding an interface.
For the Network problems:
12-21 16:38:57.059 909 1083 D DataUsageController: setMobileDataEnabled: enabled=true
12-21 16:38:57.059 909 1083 D TelephonyManager: setDataEnabled: enabled=true
12-21 16:38:57.205 479 744 E RIL-QMI : qmuxd: TX message on fd=21, to qmux_client_id=0x1, len=283
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=c1
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=c0
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=bf
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=be
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=bd
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=b0
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=ab
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=aa
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=a9
12-21 16:38:57.205 479 479 E RIL-QMI : qmuxd: RX 52 bytes on fd=21 from qmux_client_id=0x1
12-21 16:38:57.212 479 744 E RIL-QMI : qmuxd: TX message on fd=21, to qmux_client_id=0x1, len=283
12-21 16:38:57.306 765 790 I EthernetTracker: interfaceLinkStateChanged, iface: rmnet1, up: true
12-21 16:38:57.348 765 780 D ConnectivityService: registerNetworkAgent NetworkAgentInfo{ ni{[type: MOBILE[], state: UNKNOWN/IDLE, reason: (unspecified), extra: pta, failover: false, available: true, roaming: false]} network{102} nethandle{441492361229} lp{{InterfaceName: rmnet1 LinkAddresses: [ HIDDEN/32 ] DnsAddresses: [ /PRIVATE ] Domains: null MTU: 1410 TcpBufferSizes: 2097152,4194304,8388608,262144,524288,1048576 Routes: [ 0.0.0.0/0 -> HIDDEN rmnet1 mtu 0,HIDDEN/32 -> 0.0.0.0 rmnet1 mtu 0 ]}} nc{[ Transports: CELLULAR Capabilities: MMS&SUPL&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED LinkUpBandwidth>=15000Kbps LinkDnBandwidth>=30000Kbps Specifier: <TelephonyNetworkSpecifier [mSubId = 1]> AdministratorUids: [] RequestorUid: -1 RequestorPackageName: null]} Score{10} everValidated{false} lastValidated{false} created{false} lingering{false} explicitlySelected{false} acceptUnvalidated{false} everCaptivePortalDetected{false} lastCaptivePortalDetected{false} partialConnectivity{false} acceptPartialConnectivity{false} clat{mBaseIface: null, mIface: null, mState: IDLE} }
12-21 16:38:57.374 765 866 D ConnectivityService: [102 CELLULAR] EVENT_NETWORK_INFO_CHANGED, going from UNKNOWN to UNKNOWN
12-21 16:38:57.375 765 866 D ConnectivityService: [102 CELLULAR] EVENT_NETWORK_INFO_CHANGED, going from UNKNOWN to CONNECTED
12-21 16:38:57.378 765 866 W DnsManager: updatePrivateDns(102, PrivateDnsConfig{false:/[]})
12-21 16:38:57.378 765 866 D ConnectivityService: Setting DNS servers for network 102 to [/HIDDEN]
12-21 16:38:57.378 765 866 D DnsManager: sendDnsConfigurationForNetwork(102, [HIDDEN], [], 1800, 25, 8, 64, 0, 0, , [])
12-21 16:38:57.379 765 866 D ConnectivityService: Adding iface rmnet1 to network 102
12-21 16:38:57.308 765 790 I EthernetTracker: interfaceLinkStateChanged, iface: rmnet1, up: true
12-21 16:38:57.389 765 790 I EthernetTracker: interfaceLinkStateChanged, iface: rmnet1, up: true
12-21 16:38:57.389 435 465 E Netd : Error adding route 0.0.0.0/0 -> HIDDEN rmnet1 to table 1004: Network is unreachable
12-21 16:27:01.131 8034 8198 E AndroidRuntime: FATAL EXCEPTION: grpc-default-executor-0
12-21 16:27:01.131 8034 8198 E AndroidRuntime: Process: com.google.android.apps.maps, PID: 8034
12-21 16:27:01.131 8034 8198 E AndroidRuntime: java.lang.UnsupportedOperationException: The bidirectional stream API is not supported by the Java implementation of Cronet Engine
12-21 16:27:01.148 765 8217 I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
12-21 16:27:01.149 765 1696 W ActivityTaskManager: Force finishing activity com.google.android.apps.maps/com.google.android.maps.MapsActivity
[/data/user_de/0/com.google.android.gms/app_chimera/m/0000000b/CronetDynamite.apk!/lib/armeabi-v7a, /data/user_de/0/com.google.android.gms/app_chimera/m/0000000b/CronetDynamite.apk!/lib/armeabi, /system/lib, /system/system_ext/lib, /system/product/lib, /system/vendor/lib]]
12-21 16:26:56.051 8034 8087 E ChimeraModuleLdr: Failed to load code for module FileApk(/data/user_de/0/com.google.android.gms/app_chimera/m/0000000b/CronetDynamite.apk)
12-21 16:26:56.051 8034 8087 E ChimeraModuleLdr: czi: Can't load code for CronetDynamite.apk
12-21 16:26:59.145 8034 8164 W ChimeraFileApk: Failed to validate PathClassLoader for /data/user_de/0/com.google.android.gms/app_chimera/m/00000011/MeasurementDynamite.apk: java.lang.ClassNotFoundException: Didn't find class "com.google.android.gms.chimera.DynamiteModuleInitializer" on path: DexPathList[[],nativeLibraryDirectories=[/data/user_de/0/com.google.android.gms/app_chimera/m/00000011/MeasurementDynamite.apk!/lib/armeabi-v7a, /data/user_de/0/com.google.android.gms/app_chimera/m/00000011/MeasurementDynamite.apk!/lib/armeabi, /system/lib, /system/system_ext/lib, /system/product/lib, /system/vendor/lib]]
12-21 16:26:59.149 8034 8164 E ChimeraModuleLdr: Failed to load code for module FileApk(/data/user_de/0/com.google.android.gms/app_chimera/m/00000011/MeasurementDynamite.apk)
12-21 16:26:45.752 1979 7875 W aolp : setProperties failed with SecurityException [CONTEXT service_id=204 ]
12-21 16:26:45.752 1979 7875 W aolp : java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_DEVICE_CONFIG
12-21 16:26:45.752 1979 7875 W aolp : at android.os.Parcel.createExceptionOrNull(Parcel.java:2373)
12-21 16:26:45.752 1979 7875 W aolp : at android.os.Parcel.createException(Parcel.java:2357)
12-21 16:26:45.752 1979 7875 W aolp : at android.os.Parcel.readException(Parcel.java:2340)

ttesty said:
This Android 11 release kind of works on a G900T, but it's unstable. Just change your APN and Network Type and reboot.
You can run "ping -I rmnet1 8.8.8.8" and it will ping. I get a lot of Google Maps crashes, and there's no default network route that works. It lists LTE and allows me to make calls, but there's an X. Some kind of iptables issue with not finding an interface.
For the Network problems:
12-21 16:38:57.059 909 1083 D DataUsageController: setMobileDataEnabled: enabled=true
12-21 16:38:57.059 909 1083 D TelephonyManager: setDataEnabled: enabled=true
12-21 16:38:57.205 479 744 E RIL-QMI : qmuxd: TX message on fd=21, to qmux_client_id=0x1, len=283
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=c1
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=c0
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=bf
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=be
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=bd
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=b0
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=ab
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=aa
12-21 16:38:57.205 591 860 E RIL-QMI : qmi_wds_read_cdma_common_profile_tlvs: ignoring unknown TLV type=a9
12-21 16:38:57.205 479 479 E RIL-QMI : qmuxd: RX 52 bytes on fd=21 from qmux_client_id=0x1
12-21 16:38:57.212 479 744 E RIL-QMI : qmuxd: TX message on fd=21, to qmux_client_id=0x1, len=283
12-21 16:38:57.306 765 790 I EthernetTracker: interfaceLinkStateChanged, iface: rmnet1, up: true
12-21 16:38:57.348 765 780 D ConnectivityService: registerNetworkAgent NetworkAgentInfo{ ni{[type: MOBILE[], state: UNKNOWN/IDLE, reason: (unspecified), extra: pta, failover: false, available: true, roaming: false]} network{102} nethandle{441492361229} lp{{InterfaceName: rmnet1 LinkAddresses: [ HIDDEN/32 ] DnsAddresses: [ /PRIVATE ] Domains: null MTU: 1410 TcpBufferSizes: 2097152,4194304,8388608,262144,524288,1048576 Routes: [ 0.0.0.0/0 -> HIDDEN rmnet1 mtu 0,HIDDEN/32 -> 0.0.0.0 rmnet1 mtu 0 ]}} nc{[ Transports: CELLULAR Capabilities: MMS&SUPL&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED LinkUpBandwidth>=15000Kbps LinkDnBandwidth>=30000Kbps Specifier: <TelephonyNetworkSpecifier [mSubId = 1]> AdministratorUids: [] RequestorUid: -1 RequestorPackageName: null]} Score{10} everValidated{false} lastValidated{false} created{false} lingering{false} explicitlySelected{false} acceptUnvalidated{false} everCaptivePortalDetected{false} lastCaptivePortalDetected{false} partialConnectivity{false} acceptPartialConnectivity{false} clat{mBaseIface: null, mIface: null, mState: IDLE} }
12-21 16:38:57.374 765 866 D ConnectivityService: [102 CELLULAR] EVENT_NETWORK_INFO_CHANGED, going from UNKNOWN to UNKNOWN
12-21 16:38:57.375 765 866 D ConnectivityService: [102 CELLULAR] EVENT_NETWORK_INFO_CHANGED, going from UNKNOWN to CONNECTED
12-21 16:38:57.378 765 866 W DnsManager: updatePrivateDns(102, PrivateDnsConfig{false:/[]})
12-21 16:38:57.378 765 866 D ConnectivityService: Setting DNS servers for network 102 to [/HIDDEN]
12-21 16:38:57.378 765 866 D DnsManager: sendDnsConfigurationForNetwork(102, [HIDDEN], [], 1800, 25, 8, 64, 0, 0, , [])
12-21 16:38:57.379 765 866 D ConnectivityService: Adding iface rmnet1 to network 102
12-21 16:38:57.308 765 790 I EthernetTracker: interfaceLinkStateChanged, iface: rmnet1, up: true
12-21 16:38:57.389 765 790 I EthernetTracker: interfaceLinkStateChanged, iface: rmnet1, up: true
12-21 16:38:57.389 435 465 E Netd : Error adding route 0.0.0.0/0 -> HIDDEN rmnet1 to table 1004: Network is unreachable
12-21 16:27:01.131 8034 8198 E AndroidRuntime: FATAL EXCEPTION: grpc-default-executor-0
12-21 16:27:01.131 8034 8198 E AndroidRuntime: Process: com.google.android.apps.maps, PID: 8034
12-21 16:27:01.131 8034 8198 E AndroidRuntime: java.lang.UnsupportedOperationException: The bidirectional stream API is not supported by the Java implementation of Cronet Engine
12-21 16:27:01.148 765 8217 I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
12-21 16:27:01.149 765 1696 W ActivityTaskManager: Force finishing activity com.google.android.apps.maps/com.google.android.maps.MapsActivity
[/data/user_de/0/com.google.android.gms/app_chimera/m/0000000b/CronetDynamite.apk!/lib/armeabi-v7a, /data/user_de/0/com.google.android.gms/app_chimera/m/0000000b/CronetDynamite.apk!/lib/armeabi, /system/lib, /system/system_ext/lib, /system/product/lib, /system/vendor/lib]]
12-21 16:26:56.051 8034 8087 E ChimeraModuleLdr: Failed to load code for module FileApk(/data/user_de/0/com.google.android.gms/app_chimera/m/0000000b/CronetDynamite.apk)
12-21 16:26:56.051 8034 8087 E ChimeraModuleLdr: czi: Can't load code for CronetDynamite.apk
12-21 16:26:59.145 8034 8164 W ChimeraFileApk: Failed to validate PathClassLoader for /data/user_de/0/com.google.android.gms/app_chimera/m/00000011/MeasurementDynamite.apk: java.lang.ClassNotFoundException: Didn't find class "com.google.android.gms.chimera.DynamiteModuleInitializer" on path: DexPathList[[],nativeLibraryDirectories=[/data/user_de/0/com.google.android.gms/app_chimera/m/00000011/MeasurementDynamite.apk!/lib/armeabi-v7a, /data/user_de/0/com.google.android.gms/app_chimera/m/00000011/MeasurementDynamite.apk!/lib/armeabi, /system/lib, /system/system_ext/lib, /system/product/lib, /system/vendor/lib]]
12-21 16:26:59.149 8034 8164 E ChimeraModuleLdr: Failed to load code for module FileApk(/data/user_de/0/com.google.android.gms/app_chimera/m/00000011/MeasurementDynamite.apk)
12-21 16:26:45.752 1979 7875 W aolp : setProperties failed with SecurityException [CONTEXT service_id=204 ]
12-21 16:26:45.752 1979 7875 W aolp : java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_DEVICE_CONFIG
12-21 16:26:45.752 1979 7875 W aolp : at android.os.Parcel.createExceptionOrNull(Parcel.java:2373)
12-21 16:26:45.752 1979 7875 W aolp : at android.os.Parcel.createException(Parcel.java:2357)
12-21 16:26:45.752 1979 7875 W aolp : at android.os.Parcel.readException(Parcel.java:2340)
Click to expand...
Click to collapse
i dont understand anything what you wrote here

Skerleton said:
i dont understand anything what you wrote here
Click to expand...
Click to collapse
Ok.

pmduper said:
Hi mate,
Thanks for your kltedv build.
Unfortunately I still have no mobile data with LOS18 20201130 build.
Formatted and advanced cleaned, flashed rom only. Setup was smooth. No other fault found after testing the usual.
Appreciate your work
Click to expand...
Click to collapse
@haggertk. Merry Christmas to you. Thanks for the 20201225 update.
kltedv build installed works flawlessly!
ROM only, no gapps and no custom kernel.
Mobile data, calls, SMS, Bluetooth, fingerprint, WiFi etc all working smoothly.
Taking it on a road trip tomorrow so I'll have the opportunity to have a good play.

pmduper said:
...Thanks for the 20201225 update.
kltedv build installed works flawlessly!...
Click to expand...
Click to collapse
Thanks for the report.
Could you tell me please if in > Settings > Privacy > Trust > SELinux is set to Permissive or Enforcing?
That's the path in 17.1 & it may have changed in 18.1.
FYI the LineageOS S5 klte family maintainer created a new thread here:
[ROM][UNOFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)
***

curiousrom said:
Thanks for the report.
Could you tell me please if in > Settings > Privacy > Trust > SELinux is set to Permissive or Enforcing?
That's the path in 17.1 & it may have changed in 18.1.
FYI the LineageOS S5 klte family maintainer created a new thread here:
[ROM][UNOFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)
***
Click to expand...
Click to collapse
Hi mate
Its set to Enforcing...

curiousrom said:
Thanks for the report.
Could you tell me please if in > Settings > Privacy > Trust > SELinux is set to Permissive or Enforcing?
That's the path in 17.1 & it may have changed in 18.1.
FYI the LineageOS S5 klte family maintainer created a new thread here:
[ROM][UNOFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)
***
Click to expand...
Click to collapse
Enforcing.. getenforce too.