Error: I was restarted when I tried to resize a window in freeform mode
Unofficial CrDroid-OSv6 Android 10
- Thread starter khalvat
- Start date
Buttons customisations
Hi.It's possible to customise home ,recent,back button for lock screen (Double click like havoc os 9) ?
because my power button is off completely.
Hi.It's possible to customise home ,recent,back button for lock screen (Double click like havoc os 9) ?
because my power button is off completely.
FYI: I have found numerous issues with the ROM that would stop me using it as a daily. Since it is based on LOS I looked for an official build of LOS to check if they were also having the same issue; I think the errors are LOS and not specific to our device.
When doing a search, I found that there are no official builds of LOS 17.1! as of now.
https://ww.9to5google.com/2020/03/27/lineageos-android-10/#
and even the very first test builds were pulled from the server.
https://www.androidpolice.com/2020/...-android-10-builds-will-probably-launch-soon/
If there are no official builds of the base ROM (ie LOS), I think we should expect many bugs in the core of the system.
Just so people have some understanding of what I am talking about, for me, I use my phone as my media player in my car. As such, album art and the media DB is very important and a bit of an obsession. Album art is not working in this or the pure (unofficial) LOS build by @kyasu
Now, it may appear that it is working, but what is shown is NOT the album art, but artwork that is specific to the single MP3 file. Which is incorrect and becomes an issue when you have a 32GB sd card with over 3K MP3's.
eg: copy some MP3's to your device, and allow the media scanner catch up. (the following must be run under su)
As you will find, if you have any music on your device, the first query will return one or more albums. However, the second query will return NO results, indicating that album art is not being created. From what I have seen, the ROM is "falling:" back onto a file based file association for the artwork being displayed. Furthermore, if the artwork (ie a PNG file) is not "OK" (but still a perfectly valid PNG file) an error will be raised in the music player, bringing it down.
When doing a search, I found that there are no official builds of LOS 17.1! as of now.
https://ww.9to5google.com/2020/03/27/lineageos-android-10/#
and even the very first test builds were pulled from the server.
https://www.androidpolice.com/2020/...-android-10-builds-will-probably-launch-soon/
If there are no official builds of the base ROM (ie LOS), I think we should expect many bugs in the core of the system.
Just so people have some understanding of what I am talking about, for me, I use my phone as my media player in my car. As such, album art and the media DB is very important and a bit of an obsession. Album art is not working in this or the pure (unofficial) LOS build by @kyasu
Now, it may appear that it is working, but what is shown is NOT the album art, but artwork that is specific to the single MP3 file. Which is incorrect and becomes an issue when you have a 32GB sd card with over 3K MP3's.
eg: copy some MP3's to your device, and allow the media scanner catch up. (the following must be run under su)
Code:
sDB="/data/data/com.android.providers.media/databases/external.db";
echo "*** List of albums";
sqlite3 --header --column $sDB "SELECT * FROM albums;";
echo "*** One or more albums found";
echo "*** List of album art";
sqlite3 --header --column $sDB "SELECT * FROM album_art;";
echo "*** NONE!";Is this rom dead now after this discovery? The latest version is superlaggy and freezes & crashes now and again.
Thinking of reverting to an older version IF no update is showing any time soon?
Thinking of reverting to an older version IF no update is showing any time soon?
Thr source is your best bet to see what changes are occurring of recent.
5th of apr
https://github.com/Khalvat-M/android_device_samsung_klte-common/commits/10.0
5th of apr
https://github.com/Khalvat-M/android_device_samsung_ks01ltexx/commits/10.0
2nd of apr
https://github.com/Khalvat-M/kernel_samsung_msm8974/commits/10.0
And that is on top of the ROM specific changes.
https://github.com/crdroidandroid
My guess, would be No, the ROM is being modified, but for one reason or an other, its not at a stage ready for a new build and release
Thanks a lot. That Github stuff makes zero sense to me. Still keep it as my daily - despite the freezing issues. But i know the 2nd to last version worked better. @DiamondJohn - are you experiencing similar crashes and issues?
The details are not important, its simply the fact that changes have been made recently. And what point would there be in making changes to the code, unless you plan on doing another build. Which thereby answers your question if the ROM is dead. ie no.
I am not running it as a daily, but as a spare phone to test builds of other android components, and to see how crDroid is coming along. For me its not ready for a daily due to the error I posted above, and I am also hoping that crDroid will add middle shortcuts to the lock-screen.
As for if i am experiencing "similar" crashes, what crashes are you talking about? I have only experienced the ones I have posted in this thread.
New build 2020-04-11 is Available
Included April security patch
Added flip flap
Added advanced display
Fixed UI crashes sometimes
Improved GPS connect
Included April security patch
Added flip flap
Added advanced display
Fixed UI crashes sometimes
Improved GPS connect
New build 2020-04-25 is Available
Optimized device
Optimized device
[/COLOR]time: 1587881731044 msg: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/priv-app/FaceUnlockService/FaceUnlockService.apk"],nativeLibraryDirectories=[/system/priv-app/FaceUnlockService/lib/arm, /system/lib, /system/product/lib, /system/vendor/lib, /system/lib, /system/product/lib, /system/vendor/lib]]] couldn't find "libMegviiUnlock-jni-1.2.so"
stacktrace: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/priv-app/FaceUnlockService/FaceUnlockService.apk"],nativeLibraryDirectories=[/system/priv-app/FaceUnlockService/lib/arm, /system/lib, /system/product/lib, /system/vendor/lib, /system/lib, /system/product/lib, /system/vendor/lib]]] couldn't find "libMegviiUnlock-jni-1.2.so"
at java.lang.Runtime.loadLibrary0(Runtime.java:1067)
at java.lang.Runtime.loadLibrary0(Runtime.java:1007)
at java.lang.System.loadLibrary(System.java:1667)
at com.megvii.facepp.sdk.jni.LiteApi.<clinit>(LiteApi.java:345)
at com.megvii.facepp.sdk.jni.LiteApi.nativeInitHandle(Native Method)
at com.megvii.facepp.sdk.Lite.initHandle(Lite.java:414)
at com.megvii.facepp.sdk.Lite.initHandle(Lite.java:402)
at com.motorola.faceunlock.vendor.FacePPImpl.init(FacePPImpl.java:65)
at com.motorola.faceunlock.vendor.FacePPImpl.saveFeatureStart(FacePPImpl.java:149)
at com.motorola.faceunlock.service.FaceAuthService$FaceAuthServiceWrapper$1.run(FaceAuthService.java:250)
at android.os.Handler.handleCallback(Handler.java:883)
at android.os.Handler.dispatchMessage(Handler.java:100) at android.os.Looper.loop(Looper.java:214)
at android.os.HandlerThread.run(HandlerThread.java:67)
Last edited:
Face unlock not working im 32bit arm devices (may for now)
To anyone trying this ROM, I have flashed this ROM, twice
The same thing happend as last time. I used the latest OpenGApps, and when it tried to initialise GApps. it forced me into face unlock which crashed and sent me back, and then into an endless loop. I have read somewhere this is a problem with GApps; at least with OpenGApps.On my second attempt, after wiping all, I flashed the ROM, booted, then went back to recovery, flashed opengapps, then booted into system and opened the PlayStore to inialise my account. Then my battery died..
Last edited:
I upgraded from Rom 9.0 I am using already has a Google account, so it does not crash like you, everything works except: Faceunlock, Resize Freeform Mode, Wifi DirectTo anyone trying this ROM, I have flashed this ROM, twice
On my second attempt, after wiping all, I flashed the ROM, booted, then went back to recovery, flashed opengapps, then booted into system and opened the PlayStore to inialise my account. Then my battery died..
Some info on Open GApps and Android 10 https://github.com/opengapps/opengapps/wiki/Notes-for-Android-10.x
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone