Flash a different ROM then, I guess?oh, how nice to know that this will only be posted to TG.. Guess we can stop coming to xda then...
i can confirm that. without this issue the rom is my first choice.Weird issue: GCam ports won't record audio, and the stock cam won't record video (only shows first frame of the video).
confirmedWeird issue: GCam ports won't record audio, and the stock cam won't record video (only shows first frame of the video).
yes,now it works!"test build of 19.1 which should fix the video recording issue" (unofficial): https://www.gardiol.org/surya/test/
Also no more commit for 12.5.7 blobs, maybe it will be readded later?I just noticed that official build 0502 (which was the first 19.1 build) was also pulled.
Android 12.1 ist working just fine. Me and many other people are using ROMs based on that version and have no problems or complaints
Some people reported hard bricks after flashing 12.5.7 so maybe that's why.Also no more commit for 12.5.7 blobs, maybe it will be readded later?
I flashed the test version from gardiol trying to fix the audio recording and now I cannot boot =/. Can anyone post the 0502 version that was pulled from the servers, to test if I can flash that again an boot?
Nope, flashing the microG version does not fix it. If these (test/microG) versions don't touch /data when trying to boot I should be able to recover by flashing the previous 0502 /system (I think, I don't understand very well these new dynamic partitions)... but my only chance is someone having the 0502 zip still in their hard disk and uploading it somewhere.I do not have the 0502 version but the LineageOS with MicroG, which is based on the 0502 version can be downloaded here:
I have installed it on two devices as an upgrade to LineageOS 18.1 with MicroG and it works without any bugs.
But I am not sure if you can flash it over LineageOS without MicroG - without bricking it.
So you should only use it if you want to have a flawlessly running LineageOS 19.1 with MicroG.
I agree.Nope, flashing the microG version does not fix it. If these (test/microG) versions don't touch /data when trying to boot I should be able to recover by flashing the previous 0502 /system (I think, I don't understand very well these new dynamic partitions)... but my only chance is someone having the 0502 zip still in their hard disk and uploading it somewhere.
(Rant: this is why I hate when they simply remove things from servers. I understand they do it to keep users safe from a bad/dangerous build, but they could just HIDE it, or keep the zip somewhere else... it may be useful to someone!)
This seems the same issue https://github.com/RikkaW/YASNAC/issues/22Tried NikGapps, everything works as it should: isGooglePlayServicesAvailable returns 0 and my app functions as it should. So MindTheGapps seems crippled.
Thanks. I tried that version (because the addon.d script in NikGApps failed when I tried to update to latest LOS) and now my app works without problems. Calls to GoogleApiAvailability.isGooglePlayServicesAvailable() now return 0 and subsequent calls to Wearable.* work as expected.
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/