Related
Hi buddies, i create a petition to Xiaomi for release the kernel source.
You can sign here, it's free : https://www.change.org/p/xiaomi-inc...source=share_for_starters&utm_medium=copyLink
Signed
I guess its useless since it isnt a responsability of Xiaomi but Mediatek
Signed ?
I really don't think that releasing kernel source is up to mediatek right now. Simple example is the HTC's One E9, same SoC. On HTCdev site the kernel source is available for free and for everyone. How is that possible?
adaltavo said:
I guess its useless since it isnt a responsability of Xiaomi but Mediatek
Click to expand...
Click to collapse
As said @nasko_spasko. How to Xiaomi did can build the kernel without source??
Is responsability of Xiaomi, not Mediatek.
+1 signed
Gesendet von meinem Redmi Note 2 mit Tapatalk
+1 signed
~ Xiaomi Redmi Note 2 Prime ~
Deic said:
As said @nasko_spasko. How to Xiaomi did can build the kernel without source??
Is responsability of Xiaomi, not Mediatek.
Click to expand...
Click to collapse
Of course they have it, but Im pretty sure that its illegal for them to release it, since the owner is Mediatek not Xiaomi. Its like if you buy a software for comercial purpouse, it doesnt mean that youre the owner of it and you cant resell it. Here is the same, Xiaomi bought Helio X10 SoC to include it in their phones, and obviously they have source code and permissions to use it, but that doesnt mean they can resell it, or release it to people, they would get involved in serious legal problems.
adaltavo said:
Of course they have it, but Im pretty sure that its illegal for them to release it, since the owner is Mediatek not Xiaomi. Its like if you buy a software for comercial purpouse, it doesnt mean that youre the owner of it and you cant resell it. Here is the same, Xiaomi bought Helio X10 SoC to include it in their phones, and obviously they have source code and permissions to use it, but that doesnt mean they can resell it, or release it to people, they would get involved in serious legal problems.
Click to expand...
Click to collapse
Linux Kernel is under GNU GPL license so no legal problems... Mediatek are a very stupid people... Too the code is modified by Xiaomi, so isn't the original/genuine code of MTK...
Deic said:
As said @nasko_spasko. How to Xiaomi did can build the kernel without source??
Is responsability of Xiaomi, not Mediatek.
Click to expand...
Click to collapse
Deic said:
Linux Kernel is under GNU GPL license so no legal problems... Mediatek are a very stupid people... Too the code is modified by Xiaomi, so isn't the original/genuine code of MTK...
Click to expand...
Click to collapse
Yep, but Mediatek isnt the only one, Samsung also keeps their Exynos code in secret, Huawei with Kirin SoC too, etc. And yep, Linux is free, but... there so many things included in a kernel, it includes system programs that manage an OS, but also includes drivers to comunicate the OS with the hardware (SoC for example), AND are those drivers wich doesnt belong to Linux kernel nor Android OS, that code depends of the hardware manufacturer and they doesnt have any obligation of borrowing it, so if you dont have code drivers you just have an incomplete kernel, AND thats the problem everyone faces with Mediatek
adaltavo said:
Yep, but Mediatek isnt the only one, Samsung also keeps their Exynos code in secret, Huawei with Kirin SoC too, etc. And yep, Linux is free, but... there so many things included in a kernel, it includes system programs that manage an OS, but also includes drivers to comunicate the OS with the hardware (SoC for example), AND are those drivers wich doesnt belong to Linux kernel nor Android OS, that code depends of the hardware manufacturer and they doesnt have any obligation of borrowing it, so if you dont have code drivers you just have an incomplete kernel, AND thats the problem everyone faces with Mediatek
Click to expand...
Click to collapse
Mediatek release the kernel source for helio x10 buddy.
We need the Xiaomi kernel source because we need their drivers from display, touchscreen, etc...
X-Genji said:
Mediatek release the kernel source for helio x10 buddy.
Xiaomi will release their kernel source because we need the drivers from display, touchscreen,etc...
Click to expand...
Click to collapse
wut?
#tapatalknięte
Someone can share it on 4pda and chinese forums?
signed
Mediatek didn't release nothing, the code was leaked but it wasn't useful because it wasn't customised by Xiaomi with drivers.
So Xiaomi have to pay Mediatek in order to get the permission to publish the code
Mediatek must be doing something illegal, violating Qualcomm or some other patents without paying them. That's why they don't want to share their code.
Signed +1
adaltavo said:
is it necesary to be agresive? or are you just a kid :silly:?... And as I said some post ago... Xiaomi doesnt have any responsability of doing that, and maybe they dont have enough rights to release it, and if what you say is true, then those codes must work on ours RN2 since is exactly the same SoC (System on a Chip), this means they must be using same drivers even if they are different phones, since everything is included in the SoC (modem, wifi, display driver, etc.). Maybe Xiaomi uses its own code for MIUI, but thats not necesary for building an AOSP ROM or a CM ROM.
Im not a developer, and Im sure you neither, Im just saying what is obvious for me but I accept I might be wrong.
Click to expand...
Click to collapse
And screen, buttons, camera, IR blaster? There are other components with others drivers
~ Xiaomi Redmi Note 2 Prime ~
SkiFire13 said:
And screen, buttons, camera, IR blaster? There are other components with others drivers
~ Xiaomi Redmi Note 2 Prime ~
Click to expand...
Click to collapse
as I said, screen is included in a SoC (must be), buttons are all the same in Android, just camera and IR blaster might be a problem, but not big enough to not build a ROM. Anyways, an IR blaster isnt such a big problem to handle with, I have worked with them, you dont need special drivers or something like that . And camera... Xiaomi didnt build it, so I guess its a problem of the SoC... So, the problem is from Mediatek, like everything we are talking about here, and if its true that theres codes already released of Helio X10, then all this shouldn´t be a problem, even this post wouldnt have any sense.
Hi... I've been reading some news about Project Treble, and how it helps with the custom ROM development and software updates. But I want to ask. Is this working on phones like the Galaxy S5? Because it would be helpful considering the potential of this phone and how stable it is running on Nougat, and an Oreo update would be easier to Port.
Unfortunately, it's not. It is only compatible with phones that were initially shipped with Android 8.0.
camellirite said:
Unfortunately, it's not. It is only compatible with phones that were initially shipped with Android 8.0.
Click to expand...
Click to collapse
But Huawei Mate 9 got an AOSP build of Oreo in one day thanks to this. And it has never gotten updated since Nougat. It used Treble as the blog said.
Raynelfss said:
But Huawei Mate 9 got an AOSP build of Oreo in one day thanks to this. And it has never gotten updated since Nougat. It used Treble as the blog said.
Click to expand...
Click to collapse
After reading that article, you're right. I read a news article that said only phones shipped with 8.0 will be compatible with treble, my mistake.
Raynelfss said:
But Huawei Mate 9 got an AOSP build of Oreo in one day thanks to this. And it has never gotten updated since Nougat. It used Treble as the blog said.
Click to expand...
Click to collapse
Mate 9 have 4.4 kernel with android Oreo. S5 have 3.4 kernel always. And treble is compatible by phones with 4.4 kernel and above. So no treble for s5.
djgigi94 said:
Mate 9 have 4.4 kernel with android Oreo. S5 have 3.4 kernel always. And treble is compatible by phones with 4.4 kernel and above. So no treble for s5.
Click to expand...
Click to collapse
Ok... That's sad but ok. At least we are having Oreo anyway! Thanks for clarifying. Close thread please!
djgigi94 said:
Mate 9 have 4.4 kernel with android Oreo. S5 have 3.4 kernel always. And treble is compatible by phones with 4.4 kernel and above. So no treble for s5.
Click to expand...
Click to collapse
I heard something about repartitioning, so it doesn't necessarily has to do with the Kernel, it's more like partitioning the device storage, with A/B partitions and stuff with vendor. I heard about a tool that can do that job called REPIT but I didn't do so much of a research of it.
Mi3 with snapdragon 800 on kernel v 3.10 got android p today so is there any hope for our s5s ,can it be ported to our phones like the redmi devs did
https://www.xda-developers.com/xiaomi-mi-3-xiaomi-mi-4-xiaomi-redmi-4x-android-pie-ports/
I looked into it.
In order to get Project Treble working on our Samsung Galaxy S5, we would have to :
- Repartition device to have 2 partitions, Vendor & AOSP
1. All vendor-specific blobs should be moved to /vendor
2. Some blobs load config files from /system/etc. Just hex-edit them to load from /vendor/etc instead
3. Label and format that unused new partition as /vendor - this should be automatically done with an OTA script
4. The kernel should mount the new partition as /vendor as well
OR
https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
Without repartitioning?
- Have a 'Treblified' ROM already installed. (I believe we have Oreo ported..)
- Have 8.1 Vendor Blobs? I don't know much about this.
Any dev willing to make this dream a reality, please, step forward!
Rhioun said:
I looked into it.
In order to get Project Treble working on our Samsung Galaxy S5, we would have to :
- Repartition device to have 2 partitions, Vendor & AOSP
1. All vendor-specific blobs should be moved to /vendor
2. Some blobs load config files from /system/etc. Just hex-edit them to load from /vendor/etc instead
3. Label and format that unused new partition as /vendor - this should be automatically done with an OTA script
4. The kernel should mount the new partition as /vendor as well
OR
https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
Without repartitioning?
- Have a 'Treblified' ROM already installed. (I believe we have Oreo ported..)
- Have 8.1 Vendor Blobs? I don't know much about this.
Any dev willing to make this dream a reality, please, step forward!
Click to expand...
Click to collapse
Looks nice. It would be great to try. If someone does try please post your experience here!
clockstoper said:
Mi3 with snapdragon 800 on kernel v 3.10 got android p today so is there any hope for our s5s ,can it be ported to our phones like the redmi devs did
https://www.xda-developers.com/xiaomi-mi-3-xiaomi-mi-4-xiaomi-redmi-4x-android-pie-ports/
Click to expand...
Click to collapse
Xiaomi have a terribke habbit of skipping android versions
Take the MiBox for example, from what i hear it never got an official 7.1.2 only leaked builds, they went from 6.0 to 8.0 and still face quite alot of bugs.
don't know if this is the right place for this but my old moto g 2014 with 3.4 kernel version just got android pi port its very smooth as per the reports, i have not installed it yet as i gave that phone to my mom. the phone runs on with a lowly snapdragon 400 chip and 1gb ram also its kernel version is 3.4 which is the same as our s5s so there might be a good chance android pie can be ported to our device
LINK
https://forum.xda-developers.com/moto-g-2014/development/titan-xperience-13-0-t3830834
did some further searching and found that lenovo zuk z1 also got Pie and it has SD 801 chip like our S5 so things looking quite promising tbh.....
LINK
https://forum.xda-developers.com/zuk-z1/orig-development/rom-pixel-experience-t3830494
clockstoper said:
don't know if this is the right place for this but my old moto g 2014 with 3.4 kernel version just got android pi port its very smooth as per the reports, i have not installed it yet as i gave that phone to my mom. the phone runs on with a lowly snapdragon 400 chip and 1gb ram also its kernel version is 3.4 which is the same as our s5s so there might be a good chance android pie can be ported to our device
LINK
https://forum.xda-developers.com/moto-g-2014/development/titan-xperience-13-0-t3830834
did some further searching and found that lenovo zuk z1 also got Pie and it has SD 801 chip like our S5 so things looking quite promising tbh.....
LINK
https://forum.xda-developers.com/zuk-z1/orig-development/rom-pixel-experience-t3830494
Click to expand...
Click to collapse
Anyone working on 9.0 for S5?
Official Aex devices will get 9.0 soon so yes I presume
The Galaxy S5 (klte) Kernel source on LOS has reportedly submitted comments about LineageOS 16. So we're having our pie soon.
LineageOS 16.0 teaser trailer by haggertk.
Rhioun said:
I looked into it.
In order to get Project Treble working on our Samsung Galaxy S5, we would have to :
- Repartition device to have 2 partitions, Vendor & AOSP
1. All vendor-specific blobs should be moved to /vendor
2. Some blobs load config files from /system/etc. Just hex-edit them to load from /vendor/etc instead
3. Label and format that unused new partition as /vendor - this should be automatically done with an OTA script
4. The kernel should mount the new partition as /vendor as well
OR
https://forum.xda-developers.com/pr.../tool-capire-le-treble-terble-vendor-t3774629
Without repartitioning?
- Have a 'Treblified' ROM already installed. (I believe we have Oreo ported..)
- Have 8.1 Vendor Blobs? I don't know much about this.
Any dev willing to make this dream a reality, please, step forward!
Click to expand...
Click to collapse
I've heard from the official website of lineage os that they can turn a device into an A/B device, but I am not sure that whether the A/B device is the one that have 2 partitions, here it is (https://lineageos.org/Changelog-19/)
Frank Telescope said:
I've heard from the official website of lineage os that they can turn a device into an A/B device, but I am not sure that whether the A/B device is the one that have 2 partitions, here it is (https://lineageos.org/Changelog-19/)
Click to expand...
Click to collapse
Its not as simple as having a/b partitions , there is a kernel issue. a simple google search wich show you guys that there is a minimum kernel version required for treble which the s5 is far and i mean far behind that minimum requirement for treble.
I know this is like off-topic but there is now a project WIP going on for Samsung Galaxy S3 Neo, since it's using 3.4 kernel, we using S5 have luck to support treble. At least if someone willing to do it.
For the AB partition it might be impossible to do so.
Now with pascua28's Intelli-Kernel we're even closer to the dream. This guy has managed to do wonders with this device... The last thing that may happen is him being able to update our Kernel version. I don't know how the A/B partition things work, but from what I've heard it requires a higher Kernel version. The S5 runs 3.4 right now, but with @pascua28 work it may get a higher version soon.
Hi all,
I am searching and wondering for any guides/ experience/ instructions about:
Can Project Treble be ported to a device where the support is not introduced by the official vendor?
What would be required to do so? I wonder if it would be possible to use the information provided from a released kernel source in combination with some re-partitioning (?), but these are just guesstimates.
So can anyone share some insight please? I think the possibilities such a project could introduce for custom rom developments would be even much more noticeable than right now. But that's just my 2 cents.
Looking forward to hear your thoughts and productive input.
P.S.: Please keep it friendly and productive as I know this is a topic with high chances for very different point of views and that is a good thing as long as everyone is not judging, polite and fine with co-existing opinions.
---
Update: 9th May 2018
I found an interesting lead for enabling treble on devices which current partition layout would not allow it otherwise:
https://github.com/Lanchon/REPIT
Given my understanding of project treble, I would say no. This is due to the fact that you would have to have the individual drivers and their own partitions. So I believe you would have to have those drivers and the partitioning set up from the vendor in order to do it. Then again, this is xda...someone may figure out a way to do all this and make some magic!
@BakedTator Do you reckon an open-source Treble-compatible alternative could be made?
We could call it "Bass".
majamee said:
Hi all,
I am searching and wondering for any guides/ experience/ instructions about:
Can Project Treble be ported to a device where the support is not introduced by the official vendor?
What would be required to do so? I wonder if it would be possible to use the information provided from a released kernel source in combination with some re-partitioning (?), but these are just guesstimates.
So can anyone share some insight please? I think the possibilities such a project could introduce for custom rom developments would be even much more noticeable than right now. But that's just my 2 cents.
Looking forward to hear your thoughts and productive input.
P.S.: Please keep it friendly and productive as I know this is a topic with high chances for very different point of views and that is a good thing as long as everyone is not judging, polite and fine with co-existing opinions.
Click to expand...
Click to collapse
I'd say it's possible.
There are some good tentatives on the way on some devices, and it seem to have nicely progressed.
It is still not able to boot GSI, but I'm quite confident.
FWIW, this has basically nothing to do with kernel sources, and not with partitioning either.
phhusson said:
I'd say it's possible.
There are some good tentatives on the way on some devices, and it seem to have nicely progressed.
It is still not able to boot GSI, but I'm quite confident.
FWIW, this has basically nothing to do with kernel sources, and not with partitioning either.
Click to expand...
Click to collapse
Thank you for the info, especially for the FWIW part. Nevertheless, could you please be so nice to share what you know what is neccessary instead? I'm not finding any good leads/ information sources about this topic so far. Would be appreciated
zoomer296 said:
@BakedTator Do you reckon an open-source Treble-compatible alternative could be made?
We could call it "Bass".
Click to expand...
Click to collapse
You heard the man...he says it's possible...I would listen to him over me any day! Lol. Would be nice to see it happen...make more rooms reach more devices
mi5devs are porting Treble to Xiaomi MSM8996 devices (Mi5, Mi5S, mi5S plus, Mi Mix, Mi Note 2)
https://review.lineageos.org/#/q/topic:xiaomi8996-treblize-all-the-things
Nice... the avalanche is starting
Codeworkx is working on bringing treble to Oneplus 5/5T.
https://review.lineageos.org/#/c/205186/
Yes: https://forum.xda-developers.com/re...other-development/rom-lineageos-15-0-t3690465
Another device with Treble ported, Redmi 3S (Land)... @TeamMex has brought in initial Treble support to Redmi 3S just like it was done on Redmi Note 4, using Cust as the Vendor partition... Hope He has great success in it...
Source: https://plus.google.com/u/0/+klozzjesus/posts/5REcrMxfq67
Correct me if I'm wrong. To use Treble device must have /vendor partition right? So if device have this partition by default it will be easier to implement it?
Sent from my Nexus 5X using XDA Labs
Banan PL said:
Correct me if I'm wrong. To use Treble device must have /vendor partition right? So if device have this partition by default it will be easier to implement it?
Click to expand...
Click to collapse
Yes, but devices that have extra AOSP unused partitions, such as the Xiaomi /cust and Motorola /oem can have those partitions mounted as /vendor for treble ports. I'm guessing what's most important is that the partition has enough space for all the vendor blobs
I'm wondering about why they can make their devices (like xiaomi redmi 4 .Etc) adapt to treble.
The vendor code is close-source isn't it? So they write the code completely by them selves????
KuwaLee said:
I'm wondering about why they can make their devices (like xiaomi redmi 4 .Etc) adapt to treble.
The vendor code is close-source isn't it? So they write the code completely by them selves????
Click to expand...
Click to collapse
No. There were HALs before Treble, they just connect the old HALs to binderized HALs, Google even wrote several such converters.
(That's a big simplification, they still had to do a lot of work for that, that's not easy)
phhusson said:
No. There were HALs before Treble, they just connect the old HALs to binderized HALs, Google even wrote several such converters.
(That's a big simplification, they still had to do a lot of work for that, that's not easy)
Click to expand...
Click to collapse
I didn't thought it was possible without rewriting the blobs...are you willing to share some more details/resources to help other people do the same with other terminals?
For example, the whole Xperia X line has an oem partition which can be used as vendor (in the aosp version is used to store the blobs, and they also have some HALs binderized https://github.com/sonyxperiadev/device-sony-common/blob/master/manifest.xml)...but there is still something missing for full treble support.
Thank you
@phhusson when we get Android P dev preview images can we extract/make something to get them work on every treble device or do devs need sources released?
stunned said:
@phhusson when we get Android P dev preview images can we extract/make something to get them work on every treble device or do devs need sources released?
Click to expand...
Click to collapse
Hard to say. I'd say we'll need the sources.
That means that unsupported MTK devices that are still stuck on 6.0 would be able to use treble?
Then if kernel source are necessary for treble would it be possible for devices using MTK Helio Cpus to be finally updated to 8.1 as Kernel Sources are only available for a couple devices using Helio X SOCs?
For instance Helio X20 source are available from Vernee that helped developers building a semi-stable 7.1 ROM for LeEco X62x devices while the Redmi Note 4 MTK is stuck on AOSP 6.0
I think there is a way. We need to explain how Treble Works (I think anybody know's but casual users)
Devices with Treble Support had a /vendor partition with vendor, kernel and all things needed to boot, Before treble all these things will be on /system partition. Now what we can do ?
We can:
- add /vendor partition by adb
What developers need to know to port Treble sucessfully
- Developers need to know how to mount all drivers to be visible for android in /vendor partition
Hello everyone, has someone already tried to flash a GSI ROM on the k20/mi9t?
Yes, I'm running PHH's AOSP 9.0.
Two big issues:
• Popup camera pops at every reboot
- It only popup and retract with commands
- Doesn' work when you use any camera app
• You have to wake up the screen to use the fingerprint
Popup camera is almost fixed, someone with a Redmi K20 Pro is working on it and Phhusson is cleaning the code.
Schnedi said:
Yes, I'm running PHH's AOSP 9.0.
Two big issues:
• Popup camera pops at every reboot
- It only popup and retract with commands
- Doesn' work when you use any camera app
• You have to wake up the screen to use the fingerprint
Popup camera is almost fixed, someone with a Redmi K20 Pro is working on it and Phhusson is cleaning the code.
Click to expand...
Click to collapse
So you can use the guide from phhusson on github for the k20 pro for the k20/mi9T?
hmuny99 said:
So you can use the guide from phhusson on github for the k20 pro for the k20/mi9T?
Click to expand...
Click to collapse
Yes, unless it's something specific for the Snapdragon 855, most of modifications should work in both devices.
I just tried flashing havoc OS GSI and it results in a boot loop at the Mi Logo
hmuny99 said:
Hello everyone, has someone already tried to flash a GSI ROM on the k20/mi9t?
Click to expand...
Click to collapse
I try to find useful Information about GSI images but at the end I do not understand what diff's this from a crom like LineageOS.
Can Somebody explain what GSI is useful for.
I_did_it_just_tmrrow said:
I try to find useful Information about GSI images but at the end I do not understand what diff's this from a crom like LineageOS.
Can Somebody explain what GSI is useful for.
Click to expand...
Click to collapse
A GSI rom Is a Generic System Image, in other words Is Simply an "Universal rom", you can literally flash It on every device compatible with project treble.
Standard Roms on the other side (like LOS) are made specifically for a single device
I dont know why peoples wants to install GSI ROM, ? half things doesnt work, better to wait for real ROMs for this device, if it will be once.
slavke1976 said:
I dont know why peoples wants to install GSI ROM, ? half things doesnt work, better to wait for real ROMs for this device, if it will be once.
Click to expand...
Click to collapse
Speak for yourself, on my current device, that didn't even had treble at first (ZTE Axon 7) I'm running the same GSI image for 2 months now without a single issue!
FunkyRasta said:
Speak for yourself, on my current device, that didn't even had treble at first (ZTE Axon 7) I'm running the same GSI image for 2 months now without a single issue!
Click to expand...
Click to collapse
But axon 7 is not xiaomi, and dont have miui. dont know what firmware your axon come with. But if you use mi9t/k20 to use gsi for now i dont see reason. if on your k20 is chines firmware, unlock bootloader and flash global, or XEU rom. and if your mi9t is with global, unlock bootloader install chines or xeu, or any other miui rom. and wait for other normal custom roms, this gsi have non senses for this kind of phones. there is sense for gsi for devices as huawei as you cant unlock bootloader, so no aosp custom roms, just treble or gsi.
slavke1976 said:
I dont know why peoples wants to install GSI ROM, ? half things doesnt work, better to wait for real ROMs for this device, if it will be once.
Click to expand...
Click to collapse
We flash GSI because the really stable custom ROMS will come out at least 2-3 months from now, so unless you can tolerate the MIUI it is the only way to flash and use a quite stable custom ROM since patches for GSIs will arrive very soon for our device
Schnedi said:
Yes, I'm running PHH's AOSP 9.0.
Two big issues:
• Popup camera pops at every reboot
- It only popup and retract with commands
- Doesn' work when you use any camera app
• You have to wake up the screen to use the fingerprint
Popup camera is almost fixed, someone with a Redmi K20 Pro is working on it and Phhusson is cleaning the code.
Click to expand...
Click to collapse
Can you tell more about whats work or not?Im thinking about buying Mi 9t or OP6t.Is everything else working fine?Like Bluetooth calling,Lte connection...Is gsi good as daily?Did you check others gsi?
sebcio2804 said:
Can you tell more about whats work or not?Im thinking about buying Mi 9t or OP6t.Is everything else working fine?Like Bluetooth calling,Lte connection...Is gsi good as daily?Did you check others gsi?
Click to expand...
Click to collapse
For OP6T you dont need gsi roms, you have real aosp roms for that phone,
slavke1976 said:
For OP6T you dont need gsi roms, you have real aosp roms for that phone,
Click to expand...
Click to collapse
I thinking about buying these devices and want to now how it is on Mi 9t and gsi.
sebcio2804 said:
I thinking about buying these devices and want to now how it is on Mi 9t and gsi.
Click to expand...
Click to collapse
i dont know on mi9t as i dont use gsi, i just imagine you want to use gsi on op6t too
Havoc OS has the same issues AOSP has.
Now I'm trying LineageOS 16 and camera is partially fixed.
• It works with GCam and default camera
• Still pops up every reboot
Schnedi said:
Now I'm trying LineageOS 16 and camera is partially fixed.
Click to expand...
Click to collapse
Can you share a link for people who want to try as well? I googled around a bit but couldn't find anything
olihey said:
Can you share a link for people who want to try as well? I googled around a bit but couldn't find anything
Click to expand...
Click to collapse
here: https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029
HEY everyone sorry for interrupting but can we expect some roms for the k20 variant? Is there a developer ready to take on these
I hope it will be some
Sent from my Redmi K20 using Tapatalk
I'm currently using LOS 15.1 for my axon 7 but since it's not maintained anymore, I was wondering if there were any other ROMs that were being made or maintained for this device. Thanks in advance!
Im currently using stock A2017G B03 and move on with Huawei Mate 20x, i have been there done that with all known working GSI Roms and to be honest nothing feels as stable as stock especially when you need dolby atmos and banking apps, but if your device is not your primary device then you can try GSI Roms from Erfan or nFound.
Blankisblank said:
I'm currently using LOS 15.1 for my axon 7 but since it's not maintained anymore, I was wondering if there were any other ROMs that were being made or maintained for this device. Thanks in advance!
Click to expand...
Click to collapse
A lot of people have Treble'd their device and went with GSIs
I'm on LiquidRemix which seems to work nice with Speedy Vendor and Baddar Kernel
ibphantom said:
A lot of people have Treble'd their device and went with GSIs
I'm on LiquidRemix which seems to work nice with Speedy Vendor and Baddar Kernel
Click to expand...
Click to collapse
So I'm a bit confused, is LOS not made from a GSI? Or what's the difference between GSI's like LiquidRemix versus LOS?
Blankisblank said:
So I'm a bit confused, is LOS not made from a GSI? Or what's the difference between GSI's like LiquidRemix versus LOS?
Click to expand...
Click to collapse
When you Treble your device you split some partitions of your phone, particularly the vendor partition which opens the possibility of using ROMs from other phones. LOS offers a ROM version and GSI. The ROM versions are usually made just within the threads of the particular device. Some GSIs are broken, but that's because of a hardware mismatch but an updated vendor usually takes care of any mismatches. Each GSI/ROM has it's own custom set of features.
If you like LOS, you could try out the latest LOS16
But check out Havoc or LiquidRemix if you want to test GSIs
Keep in mind that we *may* have one official ROM supported for our phone. But GSIs are usually built monthly by a group of devs and they keep the security features up to date and make small changes like the AOSP public chain from Google.
ibphantom said:
When you Treble your device you split some partitions of your phone, particularly the vendor partition which opens the possibility of using ROMs from other phones. LOS offers a ROM version and GSI. The ROM versions are usually made just within the threads of the particular device. Some GSIs are broken, but that's because of a hardware mismatch but an updated vendor usually takes care of any mismatches. Each GSI/ROM has it's own custom set of features.
If you like LOS, you could try out the latest LOS16
But check out Havoc or LiquidRemix if you want to test GSIs
Keep in mind that we *may* have one official ROM supported for our phone. But GSIs are usually built monthly by a group of devs and they keep the security features up to date and make small changes like the AOSP public chain from Google.
Click to expand...
Click to collapse
So GSI's like LiquidRemix or Havoc are supported across multiple devices while ROM's are built more to match that specific device? Would that be correct? And we have a supported ROM still?
Blankisblank said:
So GSI's like LiquidRemix or Havoc are supported across multiple devices while ROM's are built more to match that specific device? Would that be correct? And we have a supported ROM still?
Click to expand...
Click to collapse
Yeah. GSIs are meant to be shared across devices with similar hardware and issues with a broken GSI are tweaked by having an updated Vendor file. ROMs are specifically made to match all the hardware in a particular model of phone. I think all the ROMs for the Axon 7 are unofficially supported at this point, which means a 3rd party dev decided to pull the source code of a popular ROM like Lineage and build it for our particular model just because they were feeling nice and appreciated by the people who use it.
ibphantom said:
When you Treble your device you split some partitions of your phone, particularly the vendor partition which opens the possibility of using ROMs from other phones. LOS offers a ROM version and GSI. The ROM versions are usually made just within the threads of the particular device. Some GSIs are broken, but that's because of a hardware mismatch but an updated vendor usually takes care of any mismatches. Each GSI/ROM has it's own custom set of features.
If you like LOS, you could try out the latest LOS16
But check out Havoc or LiquidRemix if you want to test GSIs
Keep in mind that we *may* have one official ROM supported for our phone. But GSIs are usually built monthly by a group of devs and they keep the security features up to date and make small changes like the AOSP public chain from Google.
Click to expand...
Click to collapse
ibphantom said:
Yeah. GSIs are meant to be shared across devices with similar hardware and issues with a broken GSI are tweaked by having an updated Vendor file. ROMs are specifically made to match all the hardware in a particular model of phone. I think all the ROMs for the Axon 7 are unofficially supported at this point, which means a 3rd party dev decided to pull the source code of a popular ROM like Lineage and build it for our particular model just because they were feeling nice and appreciated by the people who use it.
Click to expand...
Click to collapse
Okay so one last question, is there anything that you lose from moving to a GSI compared to a ROM? Like for example, would I still be able to use the superior audio DAC of the axon 7 or would that not be possible since that's too device specific? Thanks in advance!
Blankisblank said:
Okay so one last question, is there anything that you lose from moving to a GSI compared to a ROM? Like for example, would I still be able to use the superior audio DAC of the axon 7 or would that not be possible since that's too device specific? Thanks in advance!
Click to expand...
Click to collapse
Not that I know of. I'm able to use VoLTE and Viper4Android for the HD DAC and I'm on GSI.
Edit: And now that I remember, you should check out raystef66 ROMs. Those are still active for our phone and from an awesome dev.