Not a issue but... 14_r51 successfull building!
tydudev opened this issue · comments
Acknowledgements
- I have chosen an appropriate title.
- All requested information has been provided properly.
- This is not a feature request.
- This issue is not a duplicate of an existing issue.
- The issue is solely related to this GSI.
- This issue occurs with the latest available build.
- I am not running a custom vendor on my device.
- This issue is not kernel related.
- This issue is not related to Magisk/KernelSU/APatch.
Info
I have successfully compiled android 14 r_51 based gsi with release_keys to bypass play_integrity!
My ponce's edit fork:
https://github.com/tydudev/treble_aosp
Expected Behavior
....
Current Behavior
....
Possible Solution
No response
Steps to Reproduce
....
Logs
No response
Additional context
No response
I have tried with Android 14 r_50 and it was stuck at the boot. Had to wipe the system in order to revert back to Android 14 r_37. Now trying with Android 14 r_51 to check if this issue is fixed or not.
What is your phone and kernel version?
r51 boot successfully fluid and smootly on samsung s23... r50 not tested!
What is your phone and kernel version?
It is for Surface Duo
The kernel version is 4.14.190 and this particular kernel has device specific mods
I have tried with Android 14 r_50 and it was stuck at the boot. Had to wipe the system in order to revert back to Android 14 r_37. Now trying with Android 14 r_51 to check if this issue is fixed or not.
It is for Surface Duo The kernel version is 4.14.190 and this particular kernel has device specific mods
You are not alone.
My old device with kernel 4.14.186 also won't boot with the latest release of ponces based on android-14.0.0_r51.
For all those complaining, I remind you that without logs there's no issue...
If you have them, add them at #102.