Related
Please suggest a way to make our device get the Project Treble officially.
More details on Google Project Treble,
Thanks.
This can only be accomplished by the manufacturer of the phone (Oneplus) in corporation with the SoC manufacturer (Qualcomm). But we can always say pleeease with a big nice smile in the Oneplus forum and hope for the best. ?
pitrus- said:
This can only be accomplished by the manufacturer of the phone (Oneplus) in corporation with the SoC manufacturer (Qualcomm). But we can always say pleeease with a big nice smile in the Oneplus forum and hope for the best.
Click to expand...
Click to collapse
As per the official OnePlus forums from I visited, I have read them saying "Treble is interesting, we will keep close an eye on it.."
Which is like killing me all the time...
Could someone from XDA OnePlus team reach out to OnePlus official and represent our request???
Project Treble would be expensive and difficult to implement. Given what OnePlus did with the OP2, it's clear where this is going.
The OP3/3T hardware will be likely be completely abandoned by next Summer. One year, folks.
Of course, Google poorly designed Android from the start and created this problem. Hardware abstraction and support for official AOSP should have been baked in from the start--or (at least) implemented before Gingerbread.
I don't use the physical buttons on this device. There's not much to wear out. This next upgrade will be forced by software. I don't give a darn about benchmarks, games, or huge pdf's; hardware isn't compelling anymore. I am going to wait and see about x86 on ARM. Even with limited performance, it would be nice to carry one device and just plug into the hotel television hdmi. Also, the updates would flow for a solid five years--longer than I would use a new device (as it should be).
There will be some broken buggy ROMS floating around for a while after next summer, but those are for kids.
orange808 said:
Project Treble would be expensive and difficult to implement. Given what OnePlus did with the OP2, it's clear where this is going.
The OP3/3T hardware will be likely be completely abandoned by next Summer. One year, folks.
Of course, Google poorly designed Android from the start and created this problem. Hardware abstraction and support for official AOSP should have been baked in from the start--or (at least) implemented before Gingerbread.
I don't use the physical buttons on this device. There's not much to wear out. This next upgrade will be forced by software. I don't give a darn about benchmarks, games, or huge pdf's; hardware isn't compelling anymore. I am going to wait and see about x86 on ARM. Even with limited performance, it would be nice to carry one device and just plug into the hotel television hdmi. Also, the updates would flow for a solid five years--longer than I would use a new device (as it should be).
There will be some broken buggy ROMS floating around for a while after next summer, but those are for kids.
Click to expand...
Click to collapse
Dint quiet get you there mate...
you mean Treble is not a good move?
orange808 said:
Project Treble would be expensive and difficult to implement. Given what OnePlus did with the OP2, it's clear where this is going.
The OP3/3T hardware will be likely be completely abandoned by next Summer. One year, folks.
Of course, Google poorly designed Android from the start and created this problem. Hardware abstraction and support for official AOSP should have been baked in from the start--or (at least) implemented before Gingerbread.
I don't use the physical buttons on this device. There's not much to wear out. This next upgrade will be forced by software. I don't give a darn about benchmarks, games, or huge pdf's; hardware isn't compelling anymore. I am going to wait and see about x86 on ARM. Even with limited performance, it would be nice to carry one device and just plug into the hotel television hdmi. Also, the updates would flow for a solid five years--longer than I would use a new device (as it should be).
There will be some broken buggy ROMS floating around for a while after next summer, but those are for kids.
Click to expand...
Click to collapse
Incoherent, confused, and totally off the point, what after next year there is no Android update, would that kill the phone, I still have wildfire s, it's on ginger bread, it runs youtube, Facebook and what's app, this phone will be usable till it is not broken
Sent from my ONEPLUS A3010 using Tapatalk
dante_67 said:
Incoherent, confused, and totally off the point, what after next year there is no Android update, would that kill the phone, I still have wildfire s, it's on ginger bread, it runs youtube, Facebook and what's app, this phone will be usable till it is not broken
Sent from my ONEPLUS A3010 using Tapatalk
Click to expand...
Click to collapse
I like turtles.
Is it possible for devs to port the kernel to 4.4+ once OP release sources for Oreo?
Well, given that OEM support for our device will end by mid next year, Project Treble implementation is not really worthwhile for our devices. It won't be useful to OnePlus for long (for the 3/T), and also it'll be quite expensive to be worked on.
But if OnePlus decides to pull an OPO, and grant us our wishes, we'd all be happy.
It has almost nothing to do with Oneplus, if Qualcomm update the reference msm8996 kernel to linux 4.4 then its trivial to port oneplus modifications over.
Qualcomm has practically zero motivation to do this, infact it works against their interests.
orange808 said:
Project Treble would be expensive and difficult to implement. Given what OnePlus did with the OP2, it's clear where this is going.
The OP3/3T hardware will be likely be completely abandoned by next Summer. One year, folks.
Of course, Google poorly designed Android from the start and created this problem. Hardware abstraction and support for official AOSP should have been baked in from the start--or (at least) implemented before Gingerbread.
I don't use the physical buttons on this device. There's not much to wear out. This next upgrade will be forced by software. I don't give a darn about benchmarks, games, or huge pdf's; hardware isn't compelling anymore. I am going to wait and see about x86 on ARM. Even with limited performance, it would be nice to carry one device and just plug into the hotel television hdmi. Also, the updates would flow for a solid five years--longer than I would use a new device (as it should be).
There will be some broken buggy ROMS floating around for a while after next summer, but those are for kids.
Click to expand...
Click to collapse
x86 or ARM? Jesus, that's some pretty old CPU architecture right there. Care to elaborate as to why you want it to go further?
thes3usa said:
x86 or ARM? Jesus, that's some pretty old CPU architecture right there. Care to elaborate as to why you want it to go further?
Click to expand...
Click to collapse
I like turtles.
orange808 said:
I like turtles.
Click to expand...
Click to collapse
Makes sense. Thanks for your informative explanation xD
OnePlus 3, 3T, 5, and 5T are all missing out on Project Treble, but will be updated to Android 8.1.
I'd rather have Treble.
Sent from my ONEPLUS A3000 using Tapatalk
HampTheToker said:
OnePlus 3, 3T, 5, and 5T are all missing out on Project Treble, but will be updated to Android 8.1.
I'd rather have Treble.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
And if OnePlus had release Project Treble but not Android 8.1, you would have also complained.
Stop complain about everything you don't have, and enjoy what you have: should I remind you that Android 8.0 should have been the last update for the OnePlus 3(T)? Plus, Project Treble targets all devices launched with Android 8.x, which is not the case for actual OnePlus phones.
Not only "OnePlus" doesn't give project treble,
Stop complaint about "Project Treble"
there is a petition going to support Project Treble for OnePlus devices
feel free to sign the petition and make a difference
We (the community) would like to ask Oneplus to support Project Treble in OOS
casual_kikoo said:
And if OnePlus had release Project Treble but not Android 8.1, you would have also complained.
Stop complain about everything you don't have, and enjoy what you have: should I remind you that Android 8.0 should have been the last update for the OnePlus 3(T)? Plus, Project Treble targets all devices launched with Android 8.x, which is not the case for actual OnePlus phones.
Click to expand...
Click to collapse
Project Treble is compulsory for devices launching with Oreo, but can be enabled when a device is updated (see OG Pixel/XL and Essential Phone), so OnePlus can do it if they want to.
JoinTheRealms said:
It has almost nothing to do with Oneplus, if Qualcomm update the reference msm8996 kernel to linux 4.4 then its trivial to port oneplus modifications over.
Qualcomm has practically zero motivation to do this, infact it works against their interests.
Click to expand...
Click to collapse
Correct me if I'm wrong, just guessing here, but isn't the Google Pixel 1 getting treble? It has the same SOC, so getting the required kernel references shouldn't be a problem right?
EDIT: This is ofcourse only applicable to the 3T, so they'd have to split the OTA's from the OP3. Highly doubt that they'd do that though.
To all those who want to know more about Project Treble please use this thread to discuss about it.
What is Project Treble?
Ans. Treble is the most significant low-level change to the Android platform to date. To simplify heavily, it separates the vendor implementation from the Android framework in an effort to avoid lengthy waits for updates. . Let’s break things down a bit more:
The full update process to bring a new Android version to devices is a long and complex topic.
The “vendor” usually refers to silicon-manufacturers such as Qualcomm, but can also refer to the maker of any other proprietary hardware found in a device. The “device maker” or “OEM” usually needs to wait for the vendor to update their code so the proprietary hardware works with the Android OS framework in a newer version of Android.
However, what is happening with Project Treble is that Google is requiring that any vendor-specific code be separated from the Android OS framework and instead live in its own vendor implementation. Usually this means that there is now a separate /vendor partition on Treble-enabled smartphones that contains a bunch of HALs (Hardware Abstraction Layers).
Furthermore, vendors must implement code that lets the Android OS framework communicate with HALs in a standardized way. This is done via HIDL (HAL Interface Definition Language). With this in place, an OEM can work on an Android update without having to wait on vendors to update their HALs. Theoretically, this should speed up the entire Android update process as vendors can update their code at any time through the Play Store.
For indepth information check out this pagehttps://www.androidauthority.com/project-treble-818225/
Devices with Treble support:
- Essential PH-1
- Google Pixel
- Google Pixel XL
- HTC U11 Plus
- Huawei Honor 8 Pro
- Huawei Mate 9
- Huawei Mate 10 Pro
- Sony Xperia XZ1
- Sony Xperia XZ1 Compact
- Asus Zenfone 4 (ZE554KL)
- Honor V10
- Huawei P10/ P10 Plus
Devices which will ship with Android 8.0 Oreo will be Treble compatible by default.
Older devices will become treble compatible if the OEM creates a vendor partition via OTA update, like the Honor 8 Pro.
Custom Roms:
As of now @phhusson is working hard to make his AOSP rom boot as a fully functional rom on all the Treble supported devices, go check out the rom thread here https://forum.xda-developers.com/pr...evelopment/experimental-phh-treble-t3709659"]
Check Treble Compability
Open a terminal app on your device and simply type the following command:
getprop ro.treble.enabled
Click to expand...
Click to collapse
If it returns a boolean value true, your device supports Treble and if false it doesn’t.
[NOTE: New devices with Treble support are launching so its not possible for me to update the supported device list, so they'll not make their name on my list, but you can surely ask about your device on the discussion thread]
My understanding of Treble is, from the *big picture* anyway, that the responsibility for hardware access shifts from Google to the individual device mfgs.
The hope for us is that new versions of Android can be distributed much more rapidly, because testing of new hardware (or changes to existing hdw) won't have to wait for the new OS to be done, and that the interface to the hdw will be separate from the OS.
Another hope would be that a devices 'life span' would increase? (or at least stay current longer).
AsItLies said:
My understanding of Treble is, from the *big picture* anyway, that the responsibility for hardware access shifts from Google to the individual device mfgs.
The hope for us is that new versions of Android can be distributed much more rapidly, because testing of new hardware (or changes to existing hdw) won't have to wait for the new OS to be done, and that the interface to the hdw will be separate from the OS.
Another hope would be that a devices 'life span' would increase? (or at least stay current longer).
Click to expand...
Click to collapse
Treble means separating the vendor source from the software source, the treble devices will have a separate vendor partition, in which the vendor source will be. Now the manufacturers will only require to make the Software bug free so that the user dosent face any problems in day to day usage. From @phhussons AOSP treble rom we can get a clear picture that by separating the vendor source, the Treble based AOSP roms will run on any Treble compatible device regardless of the SOC/hardware configuration.
venom928 said:
Treble means separating the vendor source from the software source, the treble devices will have a separate vendor partition, in which the vendor source will be. <snip>
Click to expand...
Click to collapse
Ah yes that makes sense, it's not only the hardware source (vendor specific), it's also the vendors software (their mods and bloatware) that will be in the separate partition.
It really does sound as though this should speed up the time it takes for users to get updates of all kinds. It also seems pretty certain, non-Treble enabled devices will fall by the wayside. Doesn't seem there's any way around that?
AsItLies said:
Ah yes that makes sense, it's not only the hardware source (vendor specific), it's also the vendors software (their mods and bloatware) that will be in the separate partition.
It really does sound as though this should speed up the time it takes for users to get updates of all kinds. It also seems pretty certain, non-Treble enabled devices will fall by the wayside. Doesn't seem there's any way around that?
Click to expand...
Click to collapse
For non-treble devices the only way is that the OEMs must release an OTA update which will create a separate Vendor partition, but OEMs won't do(except some recent flagships) that bcz they want sales of newer devices with Treble support. As far as time is concerned, suppose it takes 2-3months for an OEM to build a fully bug free update, but it will require 3-4weeks for the OEM to build that same update
venom928 said:
For non-treble devices the only way is that the OEMs must release an OTA update which will create a separate Vendor partition
Click to expand...
Click to collapse
Yes, it seems the consensus is that mfg's won't risk bricking the phones by doing that kind of an OTA update? We'll see fairly soon what they'll do with the older devices.
It's good that google is calling the shots with this and is insisting new Oreo devices have it. It's bad though that devices just a few months old that cost mucho bucks may go without it.
AsItLies said:
Yes, it seems the consensus is that mfg's won't risk bricking the phones by doing that kind of an OTA update? We'll see fairly soon what they'll do with the older devices.
It's good that google is calling the shots with this and is insisting new Oreo devices have it. It's bad though that devices just a few months old that cost mucho bucks may go without it.
Click to expand...
Click to collapse
The honor 8 pro got Treble via OTA because it was one of the best selling device, but some OEMs will prefer not to do that so that customers will shift to newer devices. Like OnePlus could have easily added Treble to atleast 5/5T but they thought of not doing it, just depends upon the OEM
venom928 said:
The honor 8 pro got Treble via OTA because it was one of the best selling device
Click to expand...
Click to collapse
Wow, I did not know that, thanks. I better read more of the Treble threads to keep up to date
AsItLies said:
Wow, I did not know that, thanks. I better read more of the Treble threads to keep up to date
Click to expand...
Click to collapse
yep surely
Mate 9 as well
AsItLies said:
Wow, I did not know that, thanks. I better read more of the Treble threads to keep up to date
Click to expand...
Click to collapse
Mate 9 got treble as well with the Oreo update, major repartitioning as well.
revjamescarver said:
Mate 9 got treble as well with the Oreo update, major repartitioning as well.
Click to expand...
Click to collapse
Mate 9 is in the list bro, check OP
revjamescarver said:
Mate 9 got treble as well with the Oreo update, major repartitioning as well.
Click to expand...
Click to collapse
Thanks Neighbor. Huawei is rapidly moving to the top of my list of phone mfg to buy. It doesn't look like the kirin processors have much los support, but with treble... well, it seems previous prerequisites are being turned upside down.
For sure, when one evaluates (buying) a phone, many factors are relevant. But for most (if not all) of us, how long the phone will stay up to date is probably at the top of that list.
Hope the other mfg's follow Huawei's lead here, else we'll have a lot of recently mfg phones with outdated sftwr soon.
AsItLies said:
Thanks Neighbor. Huawei is rapidly moving to the top of my list of phone mfg to buy. It doesn't look like the kirin processors have much los support, but with treble... well, it seems previous prerequisites are being turned upside down.
For sure, when one evaluates (buying) a phone, many factors are relevant. But for most (if not all) of us, how long the phone will stay up to date is probably at the top of that list.
Hope the other mfg's follow Huawei's lead here, else we'll have a lot of recently mfg phones with outdated sftwr soon.
Click to expand...
Click to collapse
Huawei is the 3rd most fastest growing OEM after Apple and Samsung. What stops me from buying a Honor Device is the Kirin SOC and apps like Google Camera port dosent work on the devices except devices with Snapdragon SOC, so will wait for a device with the specs like the Mi A1 and a 18:9 display
venom928 said:
Huawei is the 3rd most fastest growing OEM after Apple and Samsung. What stops me from buying a Honor Device is the Kirin SOC and apps like Google Camera port dosent work on the devices except devices with Snapdragon SOC, so will wait for a device with the specs like the Mi A1 and a 18:9 display
Click to expand...
Click to collapse
Very good point. So even with Treble, which SOC (the phone has) will still be relevant in some respects. I have a G6 and think a wide angle lens is da bomb, but could easily do without all the glass 'bling'.
Kirin SoC
venom928 said:
Huawei is the 3rd most fastest growing OEM after Apple and Samsung. What stops me from buying a Honor Device is the Kirin SOC and apps like Google Camera port dosent work on the devices except devices with Snapdragon SOC, so will wait for a device with the specs like the Mi A1 and a 18:9 display
Click to expand...
Click to collapse
Nothing at all wrong with the Kirin SoC, performance is on par with the Qualcomm SoC, only real downfall is that Huawei doesn't sell the Kirin to other oems, otherwise it would be more widespread. The Kirin 970 with its built in NPU and and gigabit LTE modem is going to give the Qualcomm 835/845 a run for their money. Of course the port of the new Google camera app is not going to give you more than the basic functionality as it was written specifically for Google pixel devices (it doesn't give you all the features on older Google or snapdragon devices either), I installed the port on my mate 9 and it was acceptable for basic camera functions but no matter what you do you're never going to get a port of something written for another device to have the same features or performance as the stock app written for your device.
revjamescarver said:
Nothing at all wrong with the Kirin SoC, performance is on par with the Qualcomm SoC, only real downfall is that Huawei doesn't sell the Kirin to other oems, otherwise it would be more widespread. The Kirin 970 with its built in NPU and and gigabit LTE modem is going to give the Qualcomm 835/845 a run for their money. Of course the port of the new Google camera app is not going to give you more than the basic functionality as it was written specifically for Google pixel devices (it doesn't give you all the features on older Google or snapdragon devices either), I installed the port on my mate 9 and it was acceptable for basic camera functions but no matter what you do you're never going to get a port of something written for another device to have the same features or performance as the stock app written for your device.
Click to expand...
Click to collapse
I agree that the Kirin Processors are good, and the reason is Kirin is Huawei's home made processor so the pairing between Hardware and Software is perfectly optimisez for better performance and as far as Better Processing is concerned, after Apple Qualcomm holds the 2nd position no doubt, yeah in near future Kirin might surpass Qualcomm interms of performance no idea.
As far as the ported app is concerned I prefer stock android/custom roms over stock roms(MIUI/EMUI) and if someone ports the stock huawei camera for Los/RR running on Huawei devices itself, I'll surely go with a Kirin device but right now thats not available so after installing a custom rom I'll prefer Google camera app, if not the ported one, I'll go with the one available in Apkmirror, though this is my own preference as I'm addicted to using stock android and google apps suite, lets see how much development the Honor 7X gets, if it gets Treble support via OTA I'll go with it else the Mi A1 as of now is my 1st choice
I'm wondering, and the answer may be 'We don't know yet', but...
Many of us have used custom ROM's to avoid using an OEM's UI, bloatware, etc. Because Treble enabled phones will have a 'Vendor' partition (which will include these UI's etc), will that then mean the mfg's specific stuff can't really be (completely) removed the way an after market ROM does?
Of course, there's always ways of disabling mfg stuff, but Roms like Los just do it all in one fell swoop (much easier).
Do we know at this point how this will work with Treble?
Cheers and Happy New Year
AsItLies said:
I'm wondering, and the answer may be 'We don't know yet', but...
Many of us have used custom ROM's to avoid using an OEM's UI, bloatware, etc. Because Treble enabled phones will have a 'Vendor' partition (which will include these UI's etc), will that then mean the mfg's specific stuff can't really be (completely) removed the way an after market ROM does?
Of course, there's always ways of disabling mfg stuff, but Roms like Los just do it all in one fell swoop (much easier).
Do we know at this point how this will work with Treble?
Cheers and Happy New Year
Click to expand...
Click to collapse
The SOC source code will reside in the vendor partition, for example The Pixel XL has SD835 so the source code of the SOC will be there in itz Vendor partition. So if you are using a Treble enabled device such as the Huawei Mate 9 which has its own custom UI, if u flash a custom rom on it, the stock OS will get completely removed and the run ROM will run on it.
The Mgf's UI is a part of the system nd not of the vendor partition.
I am planning to buy Honor 7x, I found a thread on 7X forum which has Mount points and partition layout details for 7x. In the details, i can see below line, does this mean that phone supports Treble once updated to Oreo?
lrwxrwxrwx 1 root root 21 Dec 24 10:46 vendor -> /dev/block/mmcblk0p47
Orignal thread link
https://forum.xda-developers.com/honor-7x/development/mount-partition-layout-profile-xml-t3727990
Thanks:good: in advance!!
indigo110 said:
I am planning to buy Honor 7x, I found a thread on 7X forum which has Mount points and partition layout details for 7x. In the details, i can see below line, does this mean that phone supports Treble once updated to Oreo?
lrwxrwxrwx 1 root root 21 Dec 24 10:46 vendor -> /dev/block/mmcblk0p47
Orignal thread link
https://forum.xda-developers.com/honor-7x/development/mount-partition-layout-profile-xml-t3727990
Thanks:good: in advance!!
Click to expand...
Click to collapse
It is evident from past experiences that the Honor 7X might get Treble via OTA update as the case was with Honor 8 Pro. The Honor 7X's source code got released a few weeks ago and I got some info that the Open Kirin team will also support the 7X so I guess the Open Kirin team will also release a Treble supported rom
So I'm watching the treble news for the galaxy 9 and it's like a knife is turning in my back. I love the s8 hardware but the software, not so much. I have always preferred aosp but I don't like the pixel 2 xl's screen and I want a 2k display so no OnePlus. I hoped that the Oreo update for the s8 will bring project treble support like other OEM's did, but ofc Samsung screwed us one more time before the s9 launch. My question is: do you think that treble will ever come to the s8? Via official update from Samsung? or an xda developer port? :crying:
Because of how the system needs to be repartitioned, the only way to have treble is for the phone to come from the factory with treble set up.
eregev said:
Because of how the system needs to be repartitioned, the only way to have treble is for the phone to come from the factory with treble set up.
Click to expand...
Click to collapse
But phones that launched with nougat and got updated to Oreo support treble. Some Huawei and Sony devices. The essential phone too
vladtdr said:
So I'm watching the treble news for the galaxy 9 and it's like a knife is turning in my back. I love the s8 hardware but the software, not so much. I have always preferred aosp but I don't like the pixel 2 xl's screen and I want a 2k display so no OnePlus. I hoped that the Oreo update for the s8 will bring project treble support like other OEM's did, but ofc Samsung screwed us one more time before the s9 launch. My question is: do you think that treble will ever come to the s8? Via official update from Samsung? or an xda developer port? :crying:
Click to expand...
Click to collapse
I'm very pessimistic when it comes to Samsung and upgrades. There is no money in putting the extra work to bring Project Treble on another "old" phone.
So bad is Samsung software update strategy that I'm on October 2017 Security patch while March 2018 is already out!
(Australian non-branded XSA S8+ here). They haven't even released Oreo update for non-branded phones! These phones are meant to get updates first as they don't require telco "certification".
Having said that all that, I'm sticking to with Samsung as their hardware "just works". If Google released a phone of Samsung quality and with a Samsung AMOLED screen I'd switch in a heartbeat.
samsung probably won't add treble support because there is nothing to gain for them. they'd rather you buy a s9. there's a lot of software-only feature in these phones where they want you to buy new hardware, even thus they could easily do it on the old hardware. but it cost money (effort) and they don't get revenue for it (sales), and they're already one of the leading android phone maker, so they don't have to care. All this make it very unlikely.
community might add it somehow, eventually, who knows. I guess you could interface oreo drivers to wrappers or something like that...
vladtdr said:
But phones that launched with nougat and got updated to Oreo support treble. Some Huawei and Sony devices. The essential phone too
Click to expand...
Click to collapse
Those companies care about its user, samsung on the other hand doesn't.
I saw that some Xiaomi phones got treble support un oficial( from Devs here on xda) maybe they can do the same for s8? I think the phone has to have a vendor partition tho
I think yes, because google demands companies to do so, and that means if they are going to use google's software, they have to respect their rules. But it probably will be supported after android pie update. At least s9 does support project t.
---------- Post added at 06:32 PM ---------- Previous post was at 06:29 PM ----------
vladtdr said:
I saw that some Xiaomi phones got treble support un oficial( from Devs here on xda) maybe they can do the same for s8? I think the phone has to have a vendor partition tho
Click to expand...
Click to collapse
I think it is only possible for some devices with non-necesarry but existing special partitions. Redmi note 4 had a special partition for miui to store some specific data. And dev used that partition to bring project treble support. As i know sammy devices don't have any other partition except ordinary ones.
Nope. Not going to happen. It wouldn't help USA Snapdragon devices anyway, as Samsung isn't signing non stock images. For 95XF/FD & 95X0 you can probably fake it, which I'll explain below.
vladtdr said:
I saw that some Xiaomi phones got treble support un oficial( from Devs here on xda) maybe they can do the same for s8? I think the phone has to have a vendor partition tho
Click to expand...
Click to collapse
For exynos and non usa/canada phones only this is possible now, if someone reverse engineers the pit file format, or if the one someone came out with years ago still works.
An easier solution though is to just make hybrid images from existing gsi ROMs. Just open up a gsi image, paste in the vendor from a rom and voila! Samsung already moved all the config files around and simplified /vendor to /system/vendor so this should work just fine. I've been meaning to try but haven't gotten around to it yet
Im willing to try
partcyborg said:
Nope. Not going to happen. It wouldn't help USA Snapdragon devices anyway, as Samsung isn't signing non stock images. For 95XF/FD & 95X0 you can probably fake it, which I'll explain below.
For exynos and non usa/canada phones only this is possible now, if someone reverse engineers the pit file format, or if the one someone came out with years ago still works.
An easier solution though is to just make hybrid images from existing gsi ROMs. Just open up a gsi image, paste in the vendor from a rom and voila! Samsung already moved all the config files around and simplified /vendor to /system/vendor so this should work just fine. I've been meaning to try but haven't gotten around to it yet
Click to expand...
Click to collapse
Im willing to try this out, any chances of bricking my g955f. could you give me a step by step instruction on how to accomplish this seeing as no one seems to want to do this
DalmAsian said:
Im willing to try this out, any chances of bricking my g955f. could you give me a step by step instruction on how to accomplish this seeing as no one seems to want to do this
Click to expand...
Click to collapse
I gave this a shot on a bl unlocked snapdragon a bit ago and had no luck. At least with snapdragon, there is more to it than that.
So no, this isn't something that I or anyone else can give you a set of exact steps to accomplish. There is way too many unknowns to possibly predict them all, as this would up being much more a development/porting project than I suspected.
I still think it's doable for my device, especially after learning a few things through running gsis on a device with full treble support, but it will still take understanding what is happening and being able to make decisions based upon logs and other development practices.
Hello!
I am again, after just 2 years, in a phase of searching for a new mobile device with a good official LineageOS support. And hopefully long support. But somehow I do not know on what my decision should be based. Maintainers are picking up support and dropping it by their own choice and for users there is no predictability.
I find this very problematic, specially if you are determined to use only official LineageOS and you base you purchase merely on that.
Official LineageOS wants to be a trusted, long-lasting system and also available on many devices. But this picking up and dropping of support for an individual phone models is sadly making LineageOS just one of many costum ROMs.
In my opinion, they (stuff, leadership,..) should (maybe even with contributions to few specific developers) "commit" to support FEW devices for a LONG PERIOD. Maybe even just for 1 device in a budget range, 1 in a middle class and 1 a in high class. I would be even prepared to pay for such support. On the other hand, other devices could be further supported in a way that are now - someone picks it up and supports it until the support is dropped. Developer's choice, their kindness, their time, their device choice. But for few devices, more predictable support would be very welcome.
This right there, an insurance of a long-time support (maybe at least 3 or 4 years (?)) for just few devices, would in my opinion rise LineageOS above all other costum ROMs.
In my case, 2 years ago I picked myself a device based merely on a LineageOS statistics website. I wanted to degoogle myself, so official LineageOS (more specifically, LineageOS for microg, which is dependent on official LineageOS, because I needed push messages for 1 specific app) was the best or even only choice. But how to select a device. On a FIRST place on a website stats.lineageos.org has been Mido (Xiaomi Redmi Note 4), so I selected it, of course, in a hope for a good, long term support. It was the device with most official LineageOS installs, good specifications and good P/P value. Even now, it is still very high at 14th place, but support has been dropped 2 times until now. But sure, I cannot complain about developers, they are doing it for free. I am truly grateful for their time, I have even donated to Lineage few times.
I hope the leadership of LineageOS will read this. In my opinion, they will be only able to expand and to exist for a long time, if they provided "guaranteed" long time support for few selected devices. Right now, I am searching for such device, but do not know, which one to pick. Because now, it is just a question "Which device do you think has good and long support?".
Now most of users say Pocophone F1 (or Xiaomi Mi A1) is best budget choice for great support, but hey, this model is from 2018 and in 1 year support could be questionable, just like it was with Mido, even thou it was on the first place as the most used device. I do not want to look again for a new device in 1 year. I could, but would rather have one for as many years, until it breaks. I have small needs, I do not care, how device looks, I do not need new flagship every 2 years (it is a consumerist idiocy), I just need a working, safe, updated, private, deegoogled phone, few specific trusted apps and a case. And a long, official Lineage support, because I trust you guys.
Please consider my suggestion, I am sure it is not a new one. I am sure it would be good for everyone.
Thank you for all good work and greetings!
Full ACK! I have the same problem.
Maybe, the "e Foundation" is a solution? (Google after "e Foundation")
I think exactly the same. Something like 3 phones in 3 three different price ranges but with long LineageOS support. Possible payed version of LOS.
Hi friends,
Background: I have DirecTV Streaming Service for my home because it offers 5.1 surround.
I HAD their mobile app on my Sprint Note 4 but before Sprint was purchased by T-Mo I was prompted to update the app in the Play Store.
When I tried a dialog popped up saying that my Android 6 Marshmallow phone was no longer compatible and that DirecTV Stream now required Android 7, Android 8 recommended.
If I successfully flash an OREO 8.1 ROM will the Play Store permit me to update my app or will they see that I am a Note 4 and deny me ?
And although YTTV/Hulu etc apps still work on Marshmallow they have poor audio for my home surround system .
No, it will only see the actual version of Android.
I actually flashed CRDROID Oreo 8.1 and was then able to download the latest apk from the playstore.
Installed and ran perfectly...
BUT, my WIFI connection repeatedly disconnected.
So did my bluetooth.
And my S-Pen was neutered.
Battery life abysmal.
Also, OREO was simply baffling to me.
Nothing like the Marshmallow that I am used to.
I wish that there was a way to "spoof" my android version and APPEAR as Nougat 7.
The Note 4 itself proved that it can run the app A-OK.
When Sprint died I just assumed that the latest Samsung offering would be better than my 7 year old phone.
So I bought a brand new A52 in August 21.
$450.00 wasted.
I hate it.
Stupid aspect-ratio results in black bands while streaming.
The display IS an inch wider (in landscape mode), 6.7 inches vs 5.7 inches.
BUT, considerably shorter (in landscape mode) which translates to LESS screen area.
As a result, typing is nearly impossible on the diminished keyboard.
No replaceable battery.
No S-Pen.
Overall, a big step BACKWARD !
<rant off>
Maybe try https://forum.xda-developers.com/t/...experience-pie-trlte-tblte-trlteduos.3925885/ (PixelExperience 9)?
There are tons of roms and at least 1 will suit your needs
traman124 said:
Maybe try https://forum.xda-developers.com/t/...experience-pie-trlte-tblte-trlteduos.3925885/ (PixelExperience 9)?
There are tons of roms and at least 1 will suit your needs
Click to expand...
Click to collapse
Thanks pal...I have only flashed the OREO I mentioned so I am a very green newbie.
I have seen positive comments about Pixel so I will give it a shot.
Android 9 > 8. Any apps for 8 will work on 9 (or 10 and 11 and so on)
Hi Gang,
I thought that I'd update my results for those who are interested.
I eventually got comfortable flashing the Custom ROMs/GApps and tried many variants from 7(Nougat) up to Lineage 18.1(Android 11).
I tried a Pixel Experience package with included GApps that was very nice but on THIS particular ROM the DTVS(DirecTV Stream) APK would not install.
I suspect that the very comprehensive included GApps somehow betrayed my device's true identity.
All the other ROMs that I successfully flashed permitted the installation of the DTVS APK and it streamed flawlessy on each of them.
I do not understand why Marshmallow 6.0.1 is no longer considered sufficient.
Anyway, in the end I was really enjoying CRDroid 10 but something I had not considered made this entire exercise moot.
My home has terrible cellular reception and WIFI-Calling is indispensible for phone connnections.
What I had not realized was that WIFI-Calling is associated with each carrier's customization and cannot be incorporated into Custom ROMs as it is closely held proprietary information.
And so I have returned to the stock T-MO ROM I started out with.
Like anyone else I must be able to reliably contact emergency services for police, fire, medical, etc.
So my current solution is to leave my Mint Mobile SIM Card installed in the Note 4 while I am at home.
And if I wish to stream DTVS(via cellular) while I am out and about I must transfer the SIM to my Huawei Mate 10 which runs EMUI 12 (Android10).
It lacks WIFI Calling so it cannot be my home phone, BUT, it streams DTVS perfectly on a nice 16:9 display (no black bands on each side).
Swapping the card is a hassle but it's the best option I could think of.
I hope other users can somehow profit from my experience.
Weird. The app is not looking for the phone model; it's looking for the Android version.
Correct !
I can only assume that the model and droid version are conflated since the Note 4 was last updated in 2015 (marshmallow 6.0.1) and no further updates were/are authorized.
And so if the app sees Note 4 it can only be 6.0.1 max.
Just guessing here.
I spent alot of time studying build.prop mods to spoof my version but that never panned out.
I feel like I need to restate this: it doesn’t care if you have a note4 and limit based on that. It only limits based on version of Android.
Weird that PixelExperience didn’t work….
Lord_Ligonier said:
Correct !
I can only assume that the model and droid version are conflated since the Note 4 was last updated in 2015 (marshmallow 6.0.1) and no further updates were/are authorized.
And so if the app sees Note 4 it can only be 6.0.1 max.
Just guessing here.
I spent alot of time studying build.prop mods to spoof my version but that never panned out.
Click to expand...
Click to collapse
2016. That's when Marshmallow was released. 2015 was Lollipop
I Recently learned of a Magisk Module called "Hide Props Config"
that promises to fake my version...
How To Spoof/Fake The Android Version On Your Device
How to Spoof/Fake the Android Version on your device
In this comprehensive guide, we will show you the steps to spoof/fake the current Android version on your device to an older one.
droidwin.com
Trying to understand how this might work to make MY android version masquerede as a newer version that would permit the installation of the DTVS APK.
It appears that having rooted via Chainfire that I would need to unroot and then start over with Magisk.
Something about the stock boot.img being patched creating an obstacle to the installation.
Has anyone successfully installed Magisk while previously rooted ?
I tried and the app installs but two critical buttons are grayed out at the bottom of the app.
SU and Modules.
Anyone ???