Related
CottonmouthOS
A security and privacy focused mobile operating system based on CopperheadOS that is MicroG friendly.
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
This ROM is based on the great CopperheadOS ROM with signature spoofing enabled to allow MicroG framework. There will be changes to make the signature spoofing spoof ONLY the Google service signatures and ONLY usable/allowable by MicroG services ONLY. The new name CottonmouthOS is a way to distinguish from CopperheadOS builds, because of the signature spoofing patches.
Prerequisites coming from other ROMs :-
Have latest March factory image installed.
Instructions :-
Download the CottonmouthOS ROM
Follow the install guide
Have a more private and secure phone
Features :-
Features of CopperheadOS ROM
Note :-
CottonmouthOS is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team
Mar-V-in for MicroG
razorloves for inspiration
References :-
Copperhead homepage
Documentation
Instructions used to build
Sources
MicroG patch
If anyone wants to reupload to a better file hosting site please do.
OLD OP
CopperheadOS
A security and privacy focused mobile operating system compatible with Android apps
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
CopperheadOS - a hardened FOSS operating system based on the Android mobile platform. Its based on Android Open Source Project with added privacy and security features.
Prerequisites :-
Have latest factory image installed
Instructions :-
Download the UNOFFICIAL CopperheadOS ROM
- Mirror 1
- Mirror 2
- Mirror 3
Follow the install guide
Have a more private and secure phone
Features :-
Protection from zero-days
Prevents many vulnerabilities and makes exploits harder
Hardened C standard library and compiler toolchain
Catches memory corruption and integer overflows
Hardened kernel
Kernel self-protection and high quality ASLR
Stronger sandboxing and isolation for apps & services
Stricter SELinux policies, seccomp-bpf and more
Backported security features and quicker patching
Benefiting from upstream changes long before stock
Firewall & network hardening
Along with improvements like MAC randomization
Open-source and free of proprietary services
Uses alternatives to Google apps/services like F-Droid
Security-centric user experience changes
Better defaults, finer-grained permission control
Note :-
Copperhead is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team and razorloves for inspiration.
References :-
Copperhead homepage
Documentation
Instructions used to build
Last Updated 2018-02-28
Does copperhead have the pixel navbar animation?
File not yet uploaded
ChongoDroid said:
File not yet uploaded
Click to expand...
Click to collapse
+1
ChongoDroid said:
File not yet uploaded
Click to expand...
Click to collapse
That is strange. Will reupload.
EDIT: Done see OP
I've always wondered something, since COS charges money for phone flashing and the only way to get it yourself is to compile it yourself and flash. Once you flash your self compiled build, do you have to build the updates or does the built in updater work?
ChongoDroid said:
I've always wondered something, since COS charges money for phone flashing and the only way to get it yourself is to compile it yourself and flash. Once you flash your self compiled build, do you have to build the updates or does the built in updater work?
Click to expand...
Click to collapse
I didn't see the updater, and even if it was there the keys would not match so you would not be able to update.
Ideally, we would put this on a build server and release the full install and OTA every time there was an update so we would get the updates within a few hours of official. A few changes could be made to either change the updater (if it is there, which I did not see it) or use lineageOS one and modify it to point to the release server.
jahrule said:
I didn't see the updater, and even if it was there the keys would not match so you would not be able to update.
Ideally, we would put this on a build server and release the full install and OTA every time there was an update so we would get the updates within a few hours of official. A few changes could be made to either change the updater (if it is there, which I did not see it) or use lineageOS one and modify it to point to the release server.
Click to expand...
Click to collapse
Yeah CopperheadOS uses the stock recovery iirc. They do it like this to use verified boot iirc. I personally loved COS on my Nexus 5 and missed it on my pixel.
how likely are weekly builds for this rom? also did you find a workaround for the F-Droid extension? I tried manually removing it and disabling it via twrp, but it seems to restore itself or simply refuse to delete, showing as deleted from within twrp
Thank you for building this, I tried and failed miserably. Will flash it today :good:
Fdroid Keys and BuildSystem
Thanks for building.
Please add your keys to the fdroid whitelist.
Could you write/post about your build system?(Like a Howto)?
KShion619 said:
how likely are weekly builds for this rom? also did you find a workaround for the F-Droid extension? I tried manually removing it and disabling it via twrp, but it seems to restore itself or simply refuse to delete, showing as deleted from within twrp
Click to expand...
Click to collapse
The fdroid extension needs the keys as I pointed out in the 2nd or 3rd post notes. Regular builds would require a build server but a build server costs money. So, will try to update when I can.
smilingtux said:
Thanks for building.
Please add your keys to the fdroid whitelist.
Could you write/post about your build system?(Like a Howto)?
Click to expand...
Click to collapse
Please see the build instructions in the op that I posted.
Ideally, I would like to make another rom that has the restricted sigspoof added so we could have an option for microg
jahrule said:
The fdroid extension needs the keys as I pointed out in the 2nd or 3rd post notes. Regular builds would require a build server but a build server costs money. So, will try to update when I can.
Click to expand...
Click to collapse
Meant like a user-doable way until the keys updated, I'm fine with the full screen dialog for now
KShion619 said:
Meant like a user-doable way until the keys updated, I'm fine with the full screen dialog for now
Click to expand...
Click to collapse
The keys are compiled in so, no.
jahrule said:
Please see the build instructions in the op that I posted.
Click to expand...
Click to collapse
I have seen and read it before
I setup an build host based on copperheads documentation, I read about the java whitelisting of my keys for fdroid, but the build process itself fails from time to time.
So my question was more about, how did you manage to setup a reliable environment for building. What OS did you use, installed dependencies etc.
smilingtux said:
I have seen and read it before
I setup an build host based on copperheads documentation, I read about the java whitelisting of my keys for fdroid, but the build process itself fails from time to time.
So my question was more about, how did you manage to setup a reliable environment for building. What OS did you use, installed dependencies etc.
Click to expand...
Click to collapse
You seem to ask for a docker.
New build up at sx.ix5.org, use version 2018-10-30.
Changelog here: https://sx.ix5.org/changelog.html
Install guide: Flashing AOSP on Xperia XZ
XDA:DevDB Information
AOSP Pie based on Sony Open Devices Project, ROM for the Sony Xperia XZ
Contributors
local__hero, fastbooking, oshmoun
Source Code: https://git.ix5.org/felix/local-manifests-ix5/src/branch/ix5-customizations
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: .184 / .192
Based On: AOSP
Version Information
Status: Nightly
Created 2018-11-09
Last Updated 2019-05-17
Reporting bugs
Important: Read the bug list before posting. Anyone can add bugs to the list, just follow the rules.
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread
Don't make me ask you for logs every time!
I will repeat the rules again here:
Rules:
New bugs must include version where error popped up and which oem version you are using
Only reproducible errors
Should include adb logcat (linked in a pastebin service like https://del.dog)
Must include clear description what is wrong
If it is a visual/SystemUI bug, only report it here
If it is an internal bug(e.g. fingerprint crashes device), report it to the Sony bugtracker as well!
Always try to fix the bug yourself first! Then submit a pull request to Sony
Must search if error has already been reported (bug tracker, this document, dev buglist)
If you've reported the issue somewhere else already and just want to track it here as well, add a link
Before reporting a bug, always make sure to isolate it. That means, wipe everything, install only the ROM without GApps and Magisk and see if the problem still exists. Only then report the bug!
---
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread
---
In 9.11
1. Everything still works
2. Charging with plugged at screen off works
3. On gcam portrait mode and night photo gives purple glitched image
And phone seems to be faster.
Bug: 9.11 with oem v2- Clean install
- Hotspot not working
- Phone call issue - Mic and speaker not working, cannot hear anything or say anything << Listed in the bug
- Top speaker not working
Still testing.
An update
Yes, we know calling is kinda broken right now on both oem versions. Yes, we know you have problems with dualsim devices because you didn't flash the dualsim patcher. Yes, battery life isn't very good because we are testing out some increased CPU frequencies so video doesn't stutter. (you can go back to the 11-05 build which has the old CPU freqs and compare).
We're aware of a lot of these issues, and they are all tracked in the current buglist (see post #2).
Development happens mostly in the Sony open devices program, with a few heroic volunteers contributing. Right now, a lot of work is being done to get the current flagships(think XZ2, XZ3) to a semi-stable state, but work for our device is done as well.
You can check progress in the sonyxperiadev repos. E.g. recently, some changes to the telephony HAL integration have been made, see the common device repo.
Why is it taking so long to fix all this?
Sony buys many of their processors from Qualcomm. Lots of stuff in phones is proprietary and covered in patents, and you can only get the source code if you sign an NDA. So even if Sony wanted to, they could not release the source for a lot of things.
See all the files with the name "qti" in them? That's Qualcomm Technologies, Inc. See all the repos named something like "qcom-something-something"? That's Qualcomm.
When there's a problem, we have to report it to Sony, who report it to Qualcomm. This takes time already. And don't forget Qualcomm has suppliers as well, and so on and so on. The same is true for other parts, e.g. the Wi-Fi chips are from Broadcom.
Then, support for hardware stuff is on many levels. A lot of low-level drivers that are driving the hardware are on the /odm partition(the one that the oemv1/v2 blobs get flashed to). Then there is work to be done tweaking the actual hardware abstraction layer(HAL) interfaces that work with these driver blobs. Then there are kernel drivers that can go wrong and mess up. Then it can be a problem somewhere higher up in the Android frameworks. Lots of detective work.
If new blobs from Qualcomm come out, Sony itself needs to do some testing, and then releases a new oem version. It won't just magically work, we need to tweak the SODP vendor side as well. It could be as easy as changing a version to a newer one, but it could also be a lot harder. The sonyxperiadev crew knows what's needed to integrate these new blobs, but it still takes time and testing.
Qualcomm provide the a lot of the source code to work with their hardware and blobs from the higher-level Android side in their CodeAurora forum (CAF) repositories. The relevant changes then get merged into the sonyxperiadev repos and we can test if it works(or if something new is broken...).
For more info, read the Android documentation on hardware etc.
The chip in our phone, the MSM8996, is quite old already(even the SDM845 in the XZ2/3 is already quite old in processor standards). We can be luck that Qualcomm still provides support. But it's not a priority to them, they want to sell new
ones of course. That is also a reason updates can take longer.
Regarding full forced-reboot crashes:
Sadly, as of now, for some people the "/sys/fs/pstore" folder does not get populated after a crash. This is important to diagnose what happened.
You can apply this patch to force a kernel panic on every reboot, but I would recommend that you do
so only if you know what you are doing.
Regarding battery life:
Please install BetterBatteryStats
and find out what is draining the battery.
This could really help us out! But first, make sure you are not running any GApps, because the Google Mobile Services are a massive pile of battery drain.
If you absolutely have to use GApps, please run only the "pico" GApps version!
---
About the posts here:
Like 90% of posts here and in the old thread are full of people who just plain refuse to read, asking how to install or demanding someone help them out with something that has already been answered time and time again. This makes it extremely annoying for the us who have to scroll through pages of useless stuff to find the genuine bug reports. You do realize this site is literally named "xda-developers", right? If you're unclear on the concept, please read this: https://forum.xda-developers.com/showpost.php?p=16682226&postcount=2441
"This doesn't work!" - "This thing crashes!" - That gives us almost no clue what is happening. We need logs, or we can't do anything about it. I have only one phone, and I only use the stock ROM. There are a lot of nice testers who send others and me helpful bug reports, with detailed explanations in what circumstances it occured, with proper logs.
With that info, the Sony open devices team and us can actually look into issues.
So please, if something doesn't work AND we are not aware of it yet, post it to the bug list (not here!) and attach a link to a log that you uploaded, e.g. to a service like hastebin.com.
nhicko95 said:
how is battery life?
Click to expand...
Click to collapse
Test it out, please. And don't forget to report the diagnosed battery stats.
DarkPrinciple said:
I should be able to get to 12 lunch with my battery being more than 50%
Click to expand...
Click to collapse
I've tweaked for more performance right now, but you can use 11-05 to get old CPU freqs. Also, please help hunt down what is draining the battery, it's most likely too many held wakelocks, but it could be any number of things.
bihslk said:
So what is the latest and best working version of this rom?
Click to expand...
Click to collapse
It's literally in the first post.
bihslk said:
Rom is pretty OK but really annoying top speaker bug. Only lower one works.
Click to expand...
Click to collapse
That is already in the bug list. Please read the bug list before posting.
Update 2018-11-16
Some new developments are happening.
Oem binaries version 3 are out. This should give improved power management. The SODP team has also worked on getting audio handling during calls to work. A big thanks to oshmoun for his work on the audio manager. This change was introduced on the 11-15 build. The issue of no call audio when a bluetooth headset is connected is still present as of now.
Changed IRQ handling (PR by Angelo/"kholk"). This should give better battery life and maybe faster wakeup from deep sleep. But could also lead to instabilities and crashes. Send logs & pstore, see post #2. This change was introduced on the 11-15 build.
Testing kernel 4.9.137 i in progress (we are currently on .103). This means stability and security enhancements from upstream linux. Thanks to Nathan Chance who opened this pull request..
But some of those upstream changes might be incompatible with our Sony kernel, so we have to test that. Send logs & pstore, see post #2. This change was introduced in the 11-16 build. If the 11-15 and 11-16 builds are unstable, revert to an older one. But please be brave and run them for at least a day to get us logs of potential crashes.
---
optixperiaa said:
I am always confused about "flash latest stock ftf" part about roms as a newbie.. if we flash sony's ftf how can we flash rom ? isnt it overwrite ?
Click to expand...
Click to collapse
Your phone software is made up of many layers. The ROMs like omni or this AOSP-based one only modify your /system and /boot partitions.
But when you update your stock firmware via flashtool, you also update your phone modem firmware, your qnovo charging controller firmware, your lower-level bootloaders etc. That is why we instruct you to update to the latest stock firmware. You could theoretically skip flashing /system in flashtool(because it will get overwritten anyway, as you've already discovered) and directly flash a custom ROM afterwards.
When you're coming from omni, there is no need to flash stock firmware again in between, because your other partitions stay the same. Just a new /oem is needed.
viori said:
flash omni_kagura-2018-11-20_UNOFFICIAL_TESTBUILD-2
Click to expand...
Click to collapse
Again, please keep this thread about development for AOSP. The omni builds are not meant for you.
If you have trouble installing then simply don't use it.
DO NOT POST HERE FOR HELP OR YOU WILL BE REPORTED. Read everything before posting.
If you have questions, ask them in this thread: AOSP 9.0 Pie builds for F8331/F8332
The OP has requested that you do not post questions in this thread, please use the thread he states in the OP to do that.
If you have questions, ask them in this thread: AOSP 9.0 Pie builds for F8331/F8332
Click to expand...
Click to collapse
Thanks
Thread cleaned
General update
Newer builds will have selinux set to "enforcing". Most denials should have been fixed or are irrelevant. If you encounter any problems, selinux-related or anything else, please report them to the Sony bugtracker or - even better - submit a pull request to the selinux-policy repo.
Update 1: vendor blobs aren't binderized correctly atm, so no network. You can set selinux back to permissive to fix most issues atm.
The Wi-Fi hotspot has been fixed thanks to oshmoun. In newer builds, it should be using less battery.
Next thing we're going to tackle is deep sleep and battery drain. Big pain point and one of the last blockers, apart from the camera and bluetooth in-call audio.
You might have noticed that the omnirom device trees have been updated to 9.0. Nightly testing builds work fine, but they have the same issues as the AOSP-based ones.
Work is also under way to get a Pie-based TWRP recovery stable, with support for FDE encryption(this means that you will be able to back up your encrypted installations). Mounting /userdata works, but the builds are not ready for public release yet.
Update
New build up (2018-12-08)
Camera key works
Update to December security patch(12-05, r21)
Fingerprint should not crash device on enrollment any more
Allow setting lower minimum brightness
Double-tap-to-wake off by default(but can be enabled)
Plugging in charger with screen off should be fixed
Once again, I invite anyone who would like to help out or just learn a bit about building and tweaking to take a look at the sources posted here.
There will be a guide on how to build only the kernel and experiment with a custom boot.img shortly.
The build guide on sx.ix5.org for reproducing these AOSP builds should bring you up to speed, and if you need help building or just want to chat, the telegram group in post #1 is open to you.
local__hero said:
New build up (2018-12-08)
Camera key works
Update to December security patch(12-05, r21)
Fingerprint should not crash device on enrollment any more
Allow setting lower minimum brightness
Double-tap-to-wake off by default(but can be enabled)
Plugging in charger with screen off should be fixed
Once again, I invite anyone who would like to help out or just learn a bit about building and tweaking to take a look at the sources posted here.
There will be a guide on how to build only the kernel and experiment with a custom boot.img shortly.
The build guide on sx.ix5.org for reproducing these AOSP builds should bring you up to speed, and if you need help building or just want to chat, the telegram group in post #1 is open to you.
Click to expand...
Click to collapse
Great job.
I already built a custom Pie kernel about a week ago to gain better performance but the charging bug was driving me insane :crying:
I guess now's the time to go back to the mighty Pie and try building a nice and hopefully stable Marrow Kernel.
Cheers
Finally a new build is out!
I can't pass safety net on latest build.
Any ideas what should I use ?
Since modules for spoofing fingerprint simply don't work.
I tried universal safety net fix but with no avail.
V 12.15
Charging working fine. But i have problem with camera, photos are very dark.
Sometimes touch screen not working and i need to switch the screen and on again.
ov2rey said:
Sometimes touch screen not working and i need to switch the screen and on again.
Click to expand...
Click to collapse
Disable Dt2w
oem v4 is out
DahakePL said:
Disable Dt2w
Click to expand...
Click to collapse
Thank you It's work!
Layns said:
oem v4 is out
Click to expand...
Click to collapse
i am testing v4 on latest build aosp_f8331_2018-12-21-NIGHTLY-permissive.
Screen unable to display after update to oem v4
https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-tone/
ov2rey said:
Thank you It's work!
i am testing v4 on latest build aosp_f8331_2018-12-21-NIGHTLY-permissive.
Screen unable to display after update to oem v4
https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-tone/
Click to expand...
Click to collapse
I tried it works fine but the camera sucks and the sound is bad, the screen opening with double tap is running slow, the charge is a little quick
If not, anyone can make a bount?
matheus_sc said:
If not, anyone can make a bount?
Click to expand...
Click to collapse
Surely they are already working on it. But it just takes some time. At the moment everything is working optimally despite fastboot. Even root is possible.
pittrich said:
Surely they are already working on it. But it just takes some time. At the moment everything is working optimally despite fastboot. Even root is possible.
Click to expand...
Click to collapse
I know i use xiaomi eu already. Only update is pain to ass
wait for it
Rumour has it some chinese dev is working on it
Any news?
matheus_sc said:
Any news?
Click to expand...
Click to collapse
Still no sign.... Orangefox also quiet...
The guy who made lots of xiaomi TWRP recoveries stopped developing.
... are kernel (or device/vendor) repos released for it?
This would help.
Do we have TWRP and/or released kernel sources from other Qualcom 888 based devices out there?
raupe said:
... are kernel (or device/vendor) repos released for it?
This would help.
Do we have TWRP and/or released kernel sources from other Qualcom 888 based devices out there?
Click to expand...
Click to collapse
This?
Xiaomi Mi 11 kernel source code is out, the device is codenamed "venus" - Gizmochina
Yesterday, Xiaomi announced Mi 11 as the world’s first smartphone powered by Qualcomm Snapdragon 888. The handset already went for pre-order soon after the launch and is set to go on sale for the first time on January 1. Ahead of its sale, the company has even released this device’s kernel...
www.gizmochina.com
I read on Xiaomi.eu somewhere that there are issues with how the partitions are made and TWRP is very difficult to make for this. They said it's gonna take either a very long time before a recovery is made, or maybe not even at all.
Danacy said:
I read on Xiaomi.eu somewhere that there are issues with how the partitions are made and TWRP is very difficult to make for this. They said it's gonna take either a very long time before a recovery is made, or maybe not even at all.
Click to expand...
Click to collapse
Yeah they changed everything over to GKI 1.0 and no one seems to be supporting it, although they found somewhere on a Chinese site a recovery that works (TWRP) if you boot it (don't flash it) and unencrypts the data. It's in the XDA forums now.
[TWRP] [venus] TWRP Recovery for Mi 11
REMOVED! Use this instead : https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374109/
forum.xda-developers.com
mslezak said:
[TWRP] [venus] TWRP Recovery for Mi 11
REMOVED! Use this instead : https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374109/
forum.xda-developers.com
Click to expand...
Click to collapse
*justintime* said:
Still no sign.... Orangefox also quiet...
The guy who made lots of xiaomi TWRP recoveries stopped developing.
Click to expand...
Click to collapse
Yeah Mauronofrio is out, too much work for no return. He was pretty much the last standing open-source TWRP dev out there for tons of devices. The ones from China never get source released... Which would mean that someone would have to pickup the TWRP project and re-engineer it to fit the new GKI 1.0 then 2.0 platforms that run off that ACK. That's a lot of work. I'm talking about keeping the TWRP project open-source. It would very nice if Google stepped in since they are experts on the new format, but no such luck.
mslezak said:
Yeah they changed everything over to GKI 1.0 and no one seems to be supporting it, although they found somewhere on a Chinese site a recovery that works (TWRP) if you boot it (don't flash it) and unencrypts the data. It's in the XDA forums now.
Click to expand...
Click to collapse
Interesting, that would explain also the lack of custom ROMs? But I read that the source code is released, even before the device was launched. Isn't there GKI-support to be found in there?
Danacy said:
Interesting, that would explain also the lack of custom ROMs? But I read that the source code is released, even before the device was launched. Isn't there GKI-support to be found in there?
Click to expand...
Click to collapse
Yes they released source there are just no instructions anywhere on how to build the kernel #1 and the GKI modules #2 and combine into a build.
The new Xiaomi.eu weekly includes TWRP for Venus (Mi11) as well as Star (Mi 11 Lite 5G, Mi 11 Pro, Mi 11 Ultra, MIX FOLD) (it's a bootable TWRP, but persists after installation). Seems last week's has added Alioth (Mi 10S, Redmi K40). So I would expect a TWRP for Haydn to show up soon in the weekly Xiaomi.eu releases. Seems they forgot the haydn doesn't have TWRP yet so you can't actually install it! Tried the updater app no go, it can't boot to recovery because they don't have one yet, even though on Xiaomi.eu they say it's available, can't find it anywhere.
BTW the only TWRPs I can actually find are for Venus and Star.
haydn TWRP is not working: https://androidfilehost.com/?fid=14943124697586336730 remember: fastboot boot twrp-3.5.1-haydn.img ... although I tried everything, this TWRP just doesn't work - you boot right into the system after the fastboot boot step. Tried everything I can think of, always boots to system. Guess it's still a waiting game...
mslezak said:
Yes they released source there are just no instructions anywhere on how to build the kernel #1 and the GKI modules #2 and combine into a build.
Click to expand...
Click to collapse
Just one more question since this has been bothering me; what would be needed from Xiaomi? Instructions on how to build the kernel? Have they ever done this before about something like this? Like, is it a reasonable thing to ask them to release instructions? I know some people working there, I could forward the request.
Well I've run this by many many devs.
The issue with the GKI 1.0 and ACK is that you must download the entire AOSP build environment and make sure it works with the separate ACK (Android Common Kernel) and then properly loads the GKI modules from a separate build step. Together they make 1 kernel. This ACK per Linux Version and across vendors should be AOSP and identical. Therefore, a single build should work across all Linux 5.4 based kernels.
But... most devs are just skipping AOSP and inlining the GKI modules so they can have 1 build step. Not exactly what Google intended, but way less storage, and you can use Clang or GCC or whatever you want.
I think what OEMs are posting is merely the entire combined source code, no 2 step build process. Only a single file for the QGKI config portion. Which won't build your GKI modules as it comes. A build script for this (Q)GKI portion would be extremely beneficial.
If any OEM walks through the build steps 1) how to create only the QGKI modules and 2) how to assemble them into 1 kernel with the ACK, that would be great for devs. It just hasn't happened. So we get hacked kernels for the 888 running Linux 5.4.
The Generic Kernel Image (GKI) project | Android Open Source Project
source.android.com
mslezak said:
Well I've run this by many many devs.
The issue with the GKI 1.0 and ACK is that you must download the entire AOSP build environment and make sure it works with the separate ACK (Android Common Kernel) and then properly loads the GKI modules from a separate build step. Together they make 1 kernel. This ACK per Linux Version and across vendors should be AOSP and identical. Therefore, a single build should work across all Linux 5.4 based kernels.
But... most devs are just skipping AOSP and inlining the GKI modules so they can have 1 build step. Not exactly what Google intended, but way less storage, and you can use Clang or GCC or whatever you want.
I think what OEMs are posting is merely the entire combined source code, no 2 step build process. Only a single file for the QGKI config portion. Which won't build your GKI modules as it comes. A build script for this (Q)GKI portion would be extremely beneficial.
If any OEM walks through the build steps 1) how to create only the QGKI modules and 2) how to assemble them into 1 kernel with the ACK, that would be great for devs. It just hasn't happened. So we get hacked kernels for the 888 running Linux 5.4.
The Generic Kernel Image (GKI) project | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
OK, I see. Thank you for your reply. I am going to see how far I can get this. Tnx again!
Has anyone created a lineage rom for the A33? Can't find it.
To be clear, for me this forum is like a maze, i was previously searching for a rom for the galaxy S7 and could not find it anywhere but then a forum member sent me a link to an unofficial build which i installed and it works perfectly, so i really dont care about unofficial builds, i will take anything over the preinstalled google spyware, if you know where to find a lineageos build for the A33 please share it!!
I'm not even sure if there's a custom recovery for A33 yet, let alone a Lineage build. You could maybe attempt to patch stock recovery to allow fastbootd and use to to try and flash Lineage GSI as system.img
It's the only way I see it may work
ShaDisNX255 said:
I'm not even sure if there's a custom recovery for A33 yet, let alone a Lineage build. You could maybe attempt to patch stock recovery to allow fastbootd and use to to try and flash Lineage GSI as system.img
It's the only way I see it may work
Click to expand...
Click to collapse
I did not expect lineageos to be available for a very new phone, this is the only phone i can get for free from my provider that's why i asked.
As recovery i could use TWRP, or not?
Sorry i don't know what you mean by lineage GSI, could you please explain? What does GSI stand for and where can i get it?
Edit: just noticed you made a rom (RayOS) or atleast ported it for the A52, that's interesting!
I never heared about RayOS, is it similar to lineageos? Is there a official website?
For starters, let me know if you have a U.S. phone because if you do this whole conversation is moot.
Librem5OS said:
As recovery i could use TWRP, or not?
Click to expand...
Click to collapse
Well I don't see TWRP in this forum so, I'm guessing it's still not available. I've seen a few people patch their stock recovery to allow fastboot commands so, maybe that'll work.
Librem5OS said:
Sorry i don't know what you mean by lineage GSI, could you please explain? What does GSI stand for and where can i get it?
Click to expand...
Click to collapse
GSI is a Generic System Image. It can count as a "ROM" but it's not for a specific device. Without going too much into detail, ever since Google released Oreo they changed the way of how it works. Project Treble (you can look it up for more details) now separates the system and where the system takes its hw libs (called vendor). Because of this, it has opened the gate for GSI to act as ROMs. Developers can build a generic Lineage (or Lineage-like) system and it can pretty much work on most devices that have Project Treble (this is mandatory for devices released with Oreo and onwards). So, you can look up Lineage GSI on google and you'll be able to find it. The only downside to this as opposed to actual ROMs for devices is that since it's generic, some features may work for some brands and some features are broken on other brands. Unfortunately, every OEM has taken it upon themselves to implement Project Treble as they please and there are a few differences here and there, therefore GSI won't work the same for all brands.
Sorry to dump all this information to you, I hope you're still with me here lol. From what I've seen, GSI that are based on phhusson (a developer who is also known as phh) work pretty well on Samsung devices, so if you're interested you can look for GSI that say that they're based on his work.
Librem5OS said:
Edit: just noticed you made a rom (RayOS) or atleast ported it for the A52, that's interesting!
I never heared about RayOS, is it similar to lineageos? Is there a official website?
Click to expand...
Click to collapse
RayOS is OneUI based. I just took S21FE system (which has built in flagship features) and flashed them over to A-series phones which don't have most of those flagship features. Because this is Samsung to Samsung and they implement Project Treble pretty much the same across all their devices, be it mid-end or high-end, this was real easy to achieve and implement with a few fixes here and there. It's just my little personal project, I don't have a website for it.
ShaDisNX255 said:
For starters, let me know if you have a U.S. phone because if you do this whole conversation is moot.
Well I don't see TWRP in this forum so, I'm guessing it's still not available. I've seen a few people patch their stock recovery to allow fastboot commands so, maybe that'll work.
GSI is a Generic System Image. It can count as a "ROM" but it's not for a specific device. Without going too much into detail, ever since Google released Oreo they changed the way of how it works. Project Treble (you can look it up for more details) now separates the system and where the system takes its hw libs (called vendor). Because of this, it has opened the gate for GSI to act as ROMs. Developers can build a generic Lineage (or Lineage-like) system and it can pretty much work on most devices that have Project Treble (this is mandatory for devices released with Oreo and onwards). So, you can look up Lineage GSI on google and you'll be able to find it. The only downside to this as opposed to actual ROMs for devices is that since it's generic, some features may work for some brands and some features are broken on other brands. Unfortunately, every OEM has taken it upon themselves to implement Project Treble as they please and there are a few differences here and there, therefore GSI won't work the same for all brands.
Sorry to dump all this information to you, I hope you're still with me here lol. From what I've seen, GSI that are based on phhusson (a developer who is also known as phh) work pretty well on Samsung devices, so if you're interested you can look for GSI that say that they're based on his work.
RayOS is OneUI based. I just took S21FE system (which has built in flagship features) and flashed them over to A-series phones which don't have most of those flagship features. Because this is Samsung to Samsung and they implement Project Treble pretty much the same across all their devices, be it mid-end or high-end, this was real easy to achieve and implement with a few fixes here and there. It's just my little personal project, I don't have a website for it.
Click to expand...
Click to collapse
I am from the EU so i dont have a US phone.
Im not an expert so this whole information is a little more detailed than what i usualy deal with, had to read it twice lol. How is GSI different from the default google OS? Does it have google services injected or not?
From your description it sounds like the general stock rom for android.
I will check phhusson, however if GSI has google in it im not interested, i want privacy so no google.
I also never heared about OneUI, does it or does RayOS (your work) have google services in it or is it google free? I don't necessarly need lineage as my os, anything without google spyware will do the job.
-Thank you for the reply.
Librem5OS said:
How is GSI different from the default google OS? Does it have google services injected or not?
From your description it sounds like the general stock rom for android.
I will check phhusson, however if GSI has google in it im not interested, i want privacy so no google.
Click to expand...
Click to collapse
I think the best way to answer this question is by stating that most GSI's offer both a vanilla and gapps version. Vanilla meaning no Google services on them.
Librem5OS said:
I also never heared about OneUI
Click to expand...
Click to collapse
OneUI is the current OS name for all Samsung phones... That's what they name their version of Android
Librem5OS said:
does RayOS (your work) have google services in it or is it google free?
Click to expand...
Click to collapse
I leave the Google apps on, I use them so I don't remove them.
Librem5OS said:
I don't necessarly need lineage as my os, anything without google spyware will do the job.
Click to expand...
Click to collapse
Well then when you look for GSI, search for the term vanilla.
ShaDisNX255 said:
I think the best way to answer this question is by stating that most GSI's offer both a vanilla and gapps version. Vanilla meaning no Google services on them.
OneUI is the current OS name for all Samsung phones... That's what they name their version of Android
I leave the Google apps on, I use them so I don't remove them.
Well then when you look for GSI, search for the term vanilla.
Click to expand...
Click to collapse
Thank you now i know what ill have to look for!
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
This seems to be the generic build you where talking about?
I was just a little confused if i should visit phhs github or xda.
After all his XDA thread says: You are STRONGLY ADVISED to try PHH's AOSP of equivalent version FIRST
So i did that and this is where it takes me https://github.com/phhusson/treble_experimentations/releases/tag/v414
However all the files extensions are .xz i have no idea what that means.
When i flashed lineage it said img.tar if i remember correctly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Whats the difference between the two red marked? one says secure img the other only img?
As they say vanilla these must be the ones without google?
Or should i download these instead? If yes which one? I have no clue what the names stand for. Noticed one says ARM and the other doesnt. However what is the difference between those and what is the difference between all arm versions and all non arm versions?
Librem5OS said:
However all the files extensions are .xz i have no idea what that means.
Click to expand...
Click to collapse
The .xz extension is just an .img file compressed. You need to use something like 7zip to unzip the .img file inside.
Librem5OS said:
I was just a little confused if i should visit phhs github or xda.
Click to expand...
Click to collapse
Well as I mentioned before, many people base their work of phh. I guess this developer wants you to check phh's work first so that if it doesn't boot, you won't bother installing his work at all.
Librem5OS said:
When i flashed lineage it said img.tar if i remember correctly.
Click to expand...
Click to collapse
Tar is usually made for flashing with Odin. Looks like someone did the work of packing everything to make it easier for Samsung users to flash to their phones.
ShaDisNX255 said:
The .xz extension is just an .img file compressed. You need to use something like 7zip to unzip the .img file inside.
Well as I mentioned before, many people base their work of phh. I guess this developer wants you to check phh's work first so that if it doesn't boot, you won't bother installing his work at all.
Tar is usually made for flashing with Odin. Looks like someone did the work of packing everything to make it easier for Samsung users to flash to their phones.
Click to expand...
Click to collapse
Thanks for the help.
So as the title of his post says:
[GSI][12] LineageOS 19.x GSI (A64B/64B)That does not mention any specific device, so i asume it should be compatible with any android device.
So if i have a huawai phone with android on it, i should be able to flash this GSI on it, correct?
If yes excuse me if that sounds stupid but huawai is known to be chinese spyware, what do you think about privacy on a huawai with lineage on it? Could it be that the chinese has some shady things so deep in the phone perhaps even hardware so that even flashing a custom rom wont guarantee privacy?
Also i checked on youtube how to install GSI and the person said, flashing GSI system img only installs the system but not a boot img so i wont be able to boot, im not sure what im supposed to think about this?
For beginngers what do i need? a recovery like twrp?
A boot img?
A system img?
Is the GSI all in one or are further steps required?
Also im not sure if sourceforge is a trustworthy download option.
Librem5OS said:
[GSI][12] LineageOS 19.x GSI (A64B/64B)That does not mention any specific device, so i asume it should be compatible with any android device.
Click to expand...
Click to collapse
Well, also have to make sure you're using the correct system. As far as I know, there are arm builds, a64 builds and arm64 builds. That A64B/64B in the title makes me thin they're only offering a64 and arm64 builds, download the one according to your device. I don't know in which category A33 falls so I can't help you there. My first guess is always arm64.
Librem5OS said:
So if i have a huawai phone with android on it, i should be able to flash this GSI on it, correct?
If yes excuse me if that sounds stupid but huawai is known to be chinese spyware, what do you think about privacy on a huawai with lineage on it? Could it be that the chinese has some shady things so deep in the phone perhaps even hardware so that even flashing a custom rom wont guarantee privacy?
Click to expand...
Click to collapse
I've never owned a Huawei phone so I can't really comment if they can flash GSI flawlessly and/or if that helps with any privacy issues they may or may not have.
Librem5OS said:
Also i checked on youtube how to install GSI and the person said, flashing GSI system img only installs the system but not a boot img so i wont be able to boot, im not sure what im supposed to think about this?
Click to expand...
Click to collapse
The boot.img is the kernel, your phone already has a stock boot.img in it, no need to worry about it for now. If you dedice to use a GSI, a common bug in Samsung phones is that you won't be able to use MTP when connecting to a PC. This is usually fixed in custom kernels specifically made for AOSP ROMs and GSIs. It's a result of Samsung like doing things their own way.
Librem5OS said:
For beginngers what do i need? a recovery like twrp?
A boot img?
A system img?
Click to expand...
Click to collapse
Yes, you need a recovery capable of flashing custom system.img. It can be TWRP, OrangeFox or maybe just patching your stock recovery to be able to use fastboot commands.
Boot img is optional, as I mentioned above your phone already has one so no need to worry about it
System img is obvious, yes it's the GSI itself.
Librem5OS said:
Is the GSI all in one or are further steps required?
Click to expand...
Click to collapse
Usually GSI have all the same steps. Flashing the system and wiping data
ShaDisNX255 said:
Well, also have to make sure you're using the correct system. As far as I know, there are arm builds, a64 builds and arm64 builds. That A64B/64B in the title makes me thin they're only offering a64 and arm64 builds, download the one according to your device. I don't know in which category A33 falls so I can't help you there. My first guess is always arm64.
I've never owned a Huawei phone so I can't really comment if they can flash GSI flawlessly and/or if that helps with any privacy issues they may or may not have.
The boot.img is the kernel, your phone already has a stock boot.img in it, no need to worry about it for now. If you dedice to use a GSI, a common bug in Samsung phones is that you won't be able to use MTP when connecting to a PC. This is usually fixed in custom kernels specifically made for AOSP ROMs and GSIs. It's a result of Samsung like doing things their own way.
Yes, you need a recovery capable of flashing custom system.img. It can be TWRP, OrangeFox or maybe just patching your stock recovery to be able to use fastboot commands.
Boot img is optional, as I mentioned above your phone already has one so no need to worry about it
System img is obvious, yes it's the GSI itself.
Usually GSI have all the same steps. Flashing the system and wiping data
Click to expand...
Click to collapse
My bet was also arm64, i tend to just try it. If i want to be 100% sure propably wikipedia or the manufactuers tech specs should have info on that? a64b and 64b are entirely new to me.
TWRP is capable of flashing custom roms so if twrp is released for a33 nothing stops me from downloading and flashing the arm64 gsi onto the a33 right? I think twrp has been released for the a33 after looking here https://twrp.me/Devices/Samsung/
Just a question, if it wasn't released are there people on xda pushing their own version of twrp or similar recoverys in order to allow people to flash gsi or custom lineageos builds?
Librem5OS said:
My bet was also arm64, i tend to just try it. If i want to be 100% sure propably wikipedia or the manufactuers tech specs should have info on that? a64b and 64b are entirely new to me.
Click to expand...
Click to collapse
This is something I can't comment on. I know there are some apps on Playstore that tell you what type of system you can run but I don't know which can tell you accurate information (I personally don't use GSI). I wouldn't use any outside sources like Wikipedia or Google for that matter because of one small detail: Samsung's been known to put 64bit chips on their phones but force them to run in 32bits, even more on their lower end phones. A page may tell you that you have a 64bit chip but I don't think they know if it's even running in 64bits or not. Sorry, I can't be much help here.
Librem5OS said:
TWRP is capable of flashing custom roms so if twrp is released for a33 nothing stops me from downloading and flashing the arm64 gsi onto the a33 right?
Click to expand...
Click to collapse
This is correct
Librem5OS said:
I think twrp has been released for the a33 after looking here https://twrp.me/Devices/Samsung/
Click to expand...
Click to collapse
I think the TWRP available in the page you provided is not for the Galaxy A33 5G. It's actually for the Galaxy A3 (2015) whose model is A300H and for some weird reason Samsung gave it the device code-name 'a33g'. Yeah Samsung's very weird when it comes to their naming.
Librem5OS said:
Just a question, if it wasn't released are there people on xda pushing their own version of twrp or similar recoverys in order to allow people to flash gsi or custom lineageos builds?
Click to expand...
Click to collapse
Well, XDA usually has a set of requirements if you want to post something like a custom recovery. A custom recovery may already exist but it may not comply with XDA's requirements and could be a reason why it may not be posted yet. In my personal opinion, I'd download Telegram and search in public A33 Telegram groups any to see if maybe there's something in the works and/or something that could at least let you flash GSI.
ShaDisNX255 said:
This is something I can't comment on. I know there are some apps on Playstore that tell you what type of system you can run but I don't know which can tell you accurate information (I personally don't use GSI). I wouldn't use any outside sources like Wikipedia or Google for that matter because of one small detail: Samsung's been known to put 64bit chips on their phones but force them to run in 32bits, even more on their lower end phones. A page may tell you that you have a 64bit chip but I don't think they know if it's even running in 64bits or not. Sorry, I can't be much help here.
This is correct
I think the TWRP available in the page you provided is not for the Galaxy A33 5G. It's actually for the Galaxy A3 (2015) whose model is A300H and for some weird reason Samsung gave it the device code-name 'a33g'. Yeah Samsung's very weird when it comes to their naming.
Well, XDA usually has a set of requirements if you want to post something like a custom recovery. A custom recovery may already exist but it may not comply with XDA's requirements and could be a reason why it may not be posted yet. In my personal opinion, I'd download Telegram and search in public A33 Telegram groups any to see if maybe there's something in the works and/or something that could at least let you flash GSI.
Click to expand...
Click to collapse
My bad you are right the twrp for the "arr" shows the first release back in 2017 so that cant be the new 5g version...
If you say samsung uses 64 chipset but forces their phones to run on 32bit (idk how that makes sense) why cant i find a arm32 anywhere? I mean could be this question is out of topic too..
I just woonder if there is even a single person who currently owns the A33 and managed to flash lineageos / gsi onto the device and if so how did they do it, either everyone with that phone is using the stock rom unless they are an expert, or there are already custom recoverys and roms available for the public.
Either way in theory the GSI for android version 12 should/could be compatible with the A33 since it is as you said a generic build, but even if that would work i obviously need a custom recovery in order to flash the system on the device, kinda surprised me you mentioned telegram, i never used it as im not really into social media. I tought if there is a custom recovery my best bet would be XDA forums.
If there is no custom recovery i guess ill have to wait for a official twrp release, or an unofficial one on XDA.
Librem5OS said:
If you say samsung uses 64 chipset but forces their phones to run on 32bit (idk how that makes sense) why cant i find a arm32 anywhere? I mean could be this question is out of topic too..
Click to expand...
Click to collapse
I only said they've been known to on some lower end phones, not all. That's why I don't trust any website with that specific information. The reason why you aren't finding arm32 anywhere is because it's usually just referred to as arm in GSI builds.
Librem5OS said:
I just woonder if there is even a single person who currently owns the A33 and managed to flash lineageos / gsi onto the device and if so how did they do it, either everyone with that phone is using the stock rom unless they are an expert, or there are already custom recoverys and roms available for the public.
Click to expand...
Click to collapse
Well, can't really answer that. Maybe someone will post a way on XDA soon or maybe not.
Librem5OS said:
i obviously need a custom recovery in order to flash the system on the device
Click to expand...
Click to collapse
Correct
Librem5OS said:
kinda surprised me you mentioned telegram, i never used it as im not really into social media.
Click to expand...
Click to collapse
Personally I've seen a lot of developers share their work on Telegram first before publishing in XDA. As I mentioned before XDA has a set of requirements before being able to post something like a custom recovery . I also share my work there first so I can get people to test and report any bugs they may find before publishing a final build on XDA. Telegram is great because you don't need your phone to be on (you can use the PC client) as opposed to something like WhatsApp that is mandatory your phone be on.
Librem5OS said:
I tought if there is a custom recovery my best bet would be XDA forums.
Click to expand...
Click to collapse
That's what we all say of course lol
ShaDisNX255 said:
I only said they've been known to on some lower end phones, not all. That's why I don't trust any website with that specific information. The reason why you aren't finding arm32 anywhere is because it's usually just referred to as arm in GSI builds.
Well, can't really answer that. Maybe someone will post a way on XDA soon or maybe not.
Correct
Personally I've seen a lot of developers share their work on Telegram first before publishing in XDA. As I mentioned before XDA has a set of requirements before being able to post something like a custom recovery . I also share my work there first so I can get people to test and report any bugs they may find before publishing a final build on XDA. Telegram is great because you don't need your phone to be on (you can use the PC client) as opposed to something like WhatsApp that is mandatory your phone be on.
That's what we all say of course lol
Click to expand...
Click to collapse
Im having a problem with my old Huawai SCL-L01, this phone is slow and bad (only 1gb ram).
Atleast even when the devices is trash i wanted to install linage on it to atleast have privacy, as long as it's still working why not use it?
So the problem is i have usb debugging and oem unlock both activated, i installed adb fastboot / platformtools on my pc (which i downloaded here https://developer.android.com/studio/releases/platform-tools), i connected the phone to the pc and allowed data transfer over usb debugging by confirming the request which appears on the phone, i entered adb reboot bootloader into cmd.exe on the pc and the phone rebooted into bootloader, i then typed adb flash lineageos_rom.img
As a result instead of flashing the img, the cmd output "waiting for any device".
I dont know what is going wrong, what am i doing false in the process?
I was following the instructions here https://forum.xda-developers.com/t/index-list-of-roms-for-y6-2018.3854167/
Librem5OS said:
then typed adb flash lineageos_rom.img
Click to expand...
Click to collapse
Because you're using a adb instead of fastboot command. They're 2 different things
It's fastboot flash, not adb flash
ShaDisNX255 said:
Because you're using a adb instead of fastboot command. They're 2 different things
It's fastboot flash, not adb flash
Click to expand...
Click to collapse
I used: fastboot flash system recovery.img
Librem5OS said:
Thanks for the help.
So as the title of his post says:
[GSI][12] LineageOS 19.x GSI (A64B/64B)That does not mention any specific device, so i asume it should be compatible with any android device.
So if i have a huawai phone with android on it, i should be able to flash this GSI on it, correct?
If yes excuse me if that sounds stupid but huawai is known to be chinese spyware, what do you think about privacy on a huawai with lineage on it? Could it be that the chinese has some shady things so deep in the phone perhaps even hardware so that even flashing a custom rom wont guarantee privacy?
Also i checked on youtube how to install GSI and the person said, flashing GSI system img only installs the system but not a boot img so i wont be able to boot, im not sure what im supposed to think about this?
For beginngers what do i need? a recovery like twrp?
A boot img?
A system img?
Is the GSI all in one or are further steps required?
Also im not sure if sourceforge is a trustworthy download option.
View attachment 5678691
Click to expand...
Click to collapse
Great to meet someone who also uses pagexray.fouanalytics.com
Yeah sourceforge is not trustworthy at all...
I always get confused by sourceforge.net and curseforge.com
One of them is owned by twitch or overwolf which are owned by amazon = bigtech.
Anyways, looking at forum.xda-developers.com makes me worry...
I believe you can use any LineageOS GSI, but you'd need to flash it in a custom recovery such as TWRP while retaining the stock kernel in /boot.
Opening up this thread in hopes some interest can be made.
Since the beta version of Android 13 dropped, I decided to boot into GSI roms to achieve root. To my surprise, not only did the GSI rom boot, but I was able to go through the google setup like a champ. Every now and again, I load different GSI roms to test and I am currently using Google QPR2. As it stands the following works:
What Works
Opening and closing the device actually works and renders content in open and closed state
Cellular/wifi radio works
Touchscreen works but there's issues (see below)
Camera works (albeit not as well as the pixel camera ports)
Notifications fully work
Android Auto works
SMS works
There is a very big problem with using the GSI - the device detects inputs from both screens whether opened or closed. So here's a list of what doesn't work:
Not working
Touch input (as previously described)
Phone features (phone vibrates but dialer never displays)
Battery isn't optimized (given)
If you want to test it and provide some feedback, I am using this GSI rom:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
As always to install GSI roms, bootloader must be unlocked. To install, use DSU Loader. It's a rather painless process
domineus said:
Opening up this thread in hopes some interest can be made.
Since the beta version of Android 13 dropped, I decided to boot into GSI roms to achieve root. To my surprise, not only did the GSI rom boot, but I was able to go through the google setup like a champ. Every now and again, I load different GSI roms to test and I am currently using Google QPR2. As it stands the following works:
What Works
Opening and closing the device actually works and renders content in open and closed state
Cellular/wifi radio works
Touchscreen works but there's issues (see below)
Camera works (albeit not as well as the pixel camera ports)
Notifications fully work
Android Auto works
SMS works
There is a very big problem with using the GSI - the device detects inputs from both screens whether opened or closed. So here's a list of what doesn't work:
Not working
Touch input (as previously described)
Phone features (phone vibrates but dialer never displays)
Battery isn't optimized (given)
If you want to test it and provide some feedback, I am using this GSI rom:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
As always to install GSI roms, bootloader must be unlocked. To install, use DSU Loader. It's a rather painless process
Click to expand...
Click to collapse
hello and thank you very much for this feedback. after having watched this forum for a very long time, it is time for me to buy this magnificent smartphone because I have always used gsi pixel experience roms. but I would still like to have your opinion on the sound quality of this beast because on no comment and test nobody talks about it
Bwhite... said:
hello and thank you very much for this feedback. after having watched this forum for a very long time, it is time for me to buy this magnificent smartphone because I have always used gsi pixel experience roms. but I would still like to have your opinion on the sound quality of this beast because on no comment and test nobody talks about it
Click to expand...
Click to collapse
GSI depends solely on a bootloader unlock. Unless you get an older device that hasn't been updated, I wouldn't purchase the device with the assumption that root is easy...
domineus said:
GSI depends solely on a bootloader unlock. Unless you get an older device that hasn't been updated, I wouldn't purchase the device with the assumption that root is easy...
Click to expand...
Click to collapse
Yes indeed I understand that. but I read on the forum that unlocking the bootloader was back on a september update. but the question I ask myself more is the sound quality of the dual speakers. anyway thank you very much for your answer.
Bwhite... said:
Yes indeed I understand that. but I read on the forum that unlocking the bootloader was back on a september update. but the question I ask myself more is the sound quality of the dual speakers. anyway thank you very much for your answer.
Click to expand...
Click to collapse
I'm not sure. THere are some who tried who weren't able to bootloader unlock for the September update or afterward.
Sound quality is subjective but I had zero complaints from the speakers
domineus said:
I'm not sure. THere are some who tried who weren't able to bootloader unlock for the September update or afterward.
Sound quality is subjective but I had zero complaints from the speakers
Click to expand...
Click to collapse
ok thank you for all this useful information.
Sorry for the stupid question, but what is GSI? is this a custom rom?
NeoGoku123 said:
Sorry for the stupid question, but what is GSI? is this a custom rom?
Click to expand...
Click to collapse
Generic System Images (GSIs) | Platform | Android Developers
developer.android.com
domineus said:
Opening up this thread in hopes some interest can be made.
Since the beta version of Android 13 dropped, I decided to boot into GSI roms to achieve root. To my surprise, not only did the GSI rom boot, but I was able to go through the google setup like a champ. Every now and again, I load different GSI roms to test and I am currently using Google QPR2. As it stands the following works:
What Works
Opening and closing the device actually works and renders content in open and closed state
Cellular/wifi radio works
Touchscreen works but there's issues (see below)
Camera works (albeit not as well as the pixel camera ports)
Notifications fully work
Android Auto works
SMS works
There is a very big problem with using the GSI - the device detects inputs from both screens whether opened or closed. So here's a list of what doesn't work:
Not working
Touch input (as previously described)
Phone features (phone vibrates but dialer never displays)
Battery isn't optimized (given)
If you want to test it and provide some feedback, I am using this GSI rom:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
As always to install GSI roms, bootloader must be unlocked. To install, use DSU Loader. It's a rather painless process
Click to expand...
Click to collapse
Considering this for a x fold plus.
Were you able to fix the issues and if not, to what to extent are the effects. For example, with the battery not optimized how does it last and with the dialer not displaying are you able to answer the call? Touch input I assume is mostly an issue when using the larger screen (i.e. you accidentally input from the front screen).
NikG25 said:
Considering this for a x fold plus.
Were you able to fix the issues and if not, to what to extent are the effects. For example, with the battery not optimized how does it last and with the dialer not displaying are you able to answer the call? Touch input I assume is mostly an issue when using the larger screen (i.e. you accidentally input from the front screen).
Click to expand...
Click to collapse
I wasn't able to fix them but I didn't try. I don't have the dev machine to try and fix the issues and rebuild a LoS GSI to get it working. Which is a shame :/
But given that I have had a really good time with it otherwise because I like the potential of it