Related
Hi
I am considering the Desire Z and was interested if one will be able to watch DVB-H TV on it. I know that the MSM7230 chipset supports it, but it does not appear anywhere in the DZ specs.
I am assuming that Qualcomm supports it, but HTC have not licensed this module? Could there be any custom ROMs in the future that might add the necessary drivers?
Bump !!!
This would be ******* awesome, in theory, if it's there, you can enable it, but, you will need a hack, and some kind of driver. Just guessing, because till now, nobody have hack nothing more than a FM Radio or a Bluetooth module, but, let the developers own one first, then, when 2 months have pass, we have root, CM 6 or 7, audio hack, OC, and some other super user tricks, then, just then, start thinking seriously about this topic.
Remember, first, we need root.
It is very unlikely anything like this happen. Yes, the chip maybe supports it - but without the supporting equipment on the board, without the antenna, it's useless. So you can stop thinking about it.
MSM7230 supports it and apart the surely missing antenna you don't even know if the required pins are soldered on the board.
IMHO this will never happen and it's obvious that I can be wrong, but I can say that I'm pretty sure of what I'm saying...
faugusztin said:
It is very unlikely anything like this happen. Yes, the chip maybe supports it - but without the supporting equipment on the board, without the antenna, it's useless. So you can stop thinking about it.
Click to expand...
Click to collapse
kholk said:
MSM7230 supports it and apart the surely missing antenna you don't even know if the required pins are soldered on the board.
IMHO this will never happen and it's obvious that I can be wrong, but I can say that I'm pretty sure of what I'm saying...
Click to expand...
Click to collapse
Are you both sure that the antena is missing ? Because till we didn't know that by fact, we can't say that will never happen.
santimaster2000 said:
Are you both sure that the antena is missing ? Because till we didn't know that by fact, we can't say that will never happen.
Click to expand...
Click to collapse
An antenna would cost money to include, why include a part for a feature that isn't available? That would just be wasting money.
santimaster2000 said:
Are you both sure that the antena is missing ? Because till we didn't know that by fact, we can't say that will never happen.
Click to expand...
Click to collapse
If the support was there, why would HTC not advertise it in the product specs ?
steviewevie said:
If the support was there, why would HTC not advertise it in the product specs ?
Click to expand...
Click to collapse
For marketing reasons The next phone will use the same chipset, but will have "more features". As far as I remember P3600 owners one morning woke up with an in-built GPS that they never bought
I realize however that in this case we have likely both hardware & software limitations that might be hard to overcome.
Similar to the Diamond/Touch Pro case where the chipset supports hardware graphic acceleration (Qtv), but it was never licensed for these devices and the available drivers were pretty limited as far as I remember.
This is probably a stupid question, but does anyone know of a custom ROM that does, or possibly will in the future, support NFC?
What so need of that crap?
NFC technology is just like infrared. Beside getting faster connection, it does not have that much advantage.
ashishwebmail said:
NFC technology is just like infrared. Beside getting faster connection, it does not have that much advantage.
Click to expand...
Click to collapse
Android Pay for a start.
I highly doubt that a custom ROM would ever support NFC on the G4 Play - as far as I'm aware of doesn't have the hardware to support it in the first place.
I suppose if someone did a hardware mod like attaching an NFC chip and antenna to the battery cover and hooked it up through the USB port, but that's all I could come up with.
irony_delerium said:
I highly doubt that a custom ROM would ever support NFC on the G4 Play - as far as I'm aware of doesn't have the hardware to support it in the first place.
I suppose if someone did a hardware mod like attaching an NFC chip and antenna to the battery cover and hooked it up through the USB port, but that's all I could come up with.
Click to expand...
Click to collapse
The G4 Play does have NFC... At least, mine does
Right, so I guess not all models have it... I've got an unlocked XT1607 (2GB/16GB, US) and it doesn't have it.
Found a bit more info - I guess some of the non-US versions might have it (the XT1604 comes up), but I haven't seen it at all in the one that I've got here.
That's what I get for assuming they all didn't have one since most of the hardware specs seem to be shared otherwise...
Its a little odd, really, some having it but others not. I had presumed the only differences between them were storage capacity since that's a common theme among manufacturers and their device variants.
MrNudge said:
Its a little odd, really, some having it but others not. I had presumed the only differences between them were storage capacity since that's a common theme among manufacturers and their device variants.
Click to expand...
Click to collapse
from my understanding US doesn't have NFC, all others do. I found out when I bought mine. Sales person assured me it had NFC. Of course I went to set it up in the store and it wasn't there. Wasn't a dealbreaker for me but it would have been nice to have.
Yes, some version of G4 Play has NFC. For example my XT1604 is 16GB storage, 1 GB RAM and NFC inside. It is model for EU region.
I know the Galaxy S8 supports by default Quick Charge 3.0 but does anyone have a thought onto how if the SD devices (like mine) get root, then get unofficial ROM ports to our devices, do you think in the future it would be possible if the ROMs could support Quick Charge 4.0 natively since the SD 835 is compatible with Quick Charge 4.0? I would love to see that soon in the future.
If anyone can answer this question, that would be greatful.
Thanks!
A chipset natively supporting something and a manufacturer implementing it are two very different things. Samsung would have to design the phone to utilize QC 4.0 which then will take advantage of the native chipset support.
Basically, No. The S8 is not even listed as supporting QC 3.0 in qualcoms website. There's been debates and discussions on other forums and the general consensus is. S8/S8+ only support QC 2.0
Samsung didn't bother adding support
It's not that samsung didn't bother but they didn't pay licenses to Qualcomm because they already paid a lot for sd835 licenses itself and a percentage of every phone sold.
Same goes with updates - if Qualcomm is hostile with updates Samsung will not release those.
Hey Guys,
I'm curious whether we can manually add/unlock QC3.0 support to the zuk z2 plus. I have 2 solid sources claiming that the zuk z2 plus has the required hardware to support QC3.0. Although these sources are pretty unknown, they are the only good sources that shine some light on the hardware level support of QC3.0. One source is devicespecifications. com.
[Screenshot attached]. I've verified the hardware mentioned in this site of other phones and they seem to match 100%. The other source is this app called "Device Info HW". Well this app gives more of a concrete base that our device has the hardware chipset (PMIC) to support and manage QC3.0. [Screenshot attached]. The chipset mentioned so in this app is
smb1351 (Check screenshot) which is a QC3.0 chipset (Qualcomm website itself mentions so). But this app when I tried on other devices fails to mention the PMIC present. Now this is where I require some help. I need some of you guys running various roms to install this app and post whether you get the same PMIC (it's mentioned as charger). And also if possible try this app on various other official QC supported phones and post results. I need this info to proceed in porting either a mod (hvdcp file) or request a developer for custom kernel to support QC3.0. I hope we can successfully add QC3.0 support to our phones.
Peace Out
Incrovantilist said:
Hey Guys,
I'm curious whether we can manually add/unlock QC3.0 support to the zuk z2 plus. I have 2 solid sources claiming that the zuk z2 plus has the required hardware to support QC3.0. Although these sources are pretty unknown, they are the only good sources that shine some light on the hardware level support of QC3.0. One source is devicespecifications. com.
[Screenshot attached]. I've verified the hardware mentioned in this site of other phones and they seem to match 100%. The other source is this app called "Device Info HW". Well this app gives more of a concrete base that our device has the hardware chipset (PMIC) to support and manage QC3.0. [Screenshot attached]. The chipset mentioned so in this app is
smb1351 (Check screenshot) which is a QC3.0 chipset (Qualcomm website itself mentions so). But this app when I tried on other devices fails to mention the PMIC present. Now this is where I require some help. I need some of you guys running various roms to install this app and post whether you get the same PMIC (it's mentioned as charger). And also if possible try this app on various other official QC supported phones and post results. I need this info to proceed in porting either a mod (hvdcp file) or request a developer for custom kernel to support QC3.0. I hope we can successfully add QC3.0 support to our phones.
Peace Out
Click to expand...
Click to collapse
Actually you are not the first give to request this
But still we ain't gonna get this quick charge stuff as some diode will overheat and damage it making it unable to charge .
And bro it ain't safe for playing with the charge rate as the manufacturer may put them for a reason .
Go to zukfans.eu and check in details
Incrovantilist said:
Hey Guys,
I'm curious whether we can manually add/unlock QC3.0 support to the zuk z2 plus. I have 2 solid sources claiming that the zuk z2 plus has the required hardware to support QC3.0. Although these sources are pretty unknown, they are the only good sources that shine some light on the hardware level support of QC3.0. One source is devicespecifications. com.
[Screenshot attached]. I've verified the hardware mentioned in this site of other phones and they seem to match 100%. The other source is this app called "Device Info HW". Well this app gives more of a concrete base that our device has the hardware chipset (PMIC) to support and manage QC3.0. [Screenshot attached]. The chipset mentioned so in this app is
smb1351 (Check screenshot) which is a QC3.0 chipset (Qualcomm website itself mentions so). But this app when I tried on other devices fails to mention the PMIC present. Now this is where I require some help. I need some of you guys running various roms to install this app and post whether you get the same PMIC (it's mentioned as charger). And also if possible try this app on various other official QC supported phones and post results. I need this info to proceed in porting either a mod (hvdcp file) or request a developer for custom kernel to support QC3.0. I hope we can successfully add QC3.0 support to our phones.
Peace Out
Click to expand...
Click to collapse
Hey lenovo z2 plus already supports qc3.0 check the specs again
Siddhu1605 said:
Hey lenovo z2 plus already supports qc3.0 check the specs again
Click to expand...
Click to collapse
It doesn't bro... it might have the hardware for it but no support in kernel...
Incrovantilist said:
It doesn't bro... it might have the hardware for it but no support in kernel...
Click to expand...
Click to collapse
Check this it's from android central.
And not only this website.. check any website...it says the same
Siddhu1605 said:
Check this it's from android central.
And not only this website.. check any website...it says the same
Click to expand...
Click to collapse
That article is of thoughts on the phone and not review. Bro we have the phone. I have tested with more than half a dozen QC2.0/QC3.0 chargers and results are always the same. Normal charging speeds if not slower than the charger that came with the phone. Lenovo misquoted this phone's charging capabilities in press release. That's why all websites give the same wrong info. Maybe you can try and post evidence that Z2 Plus supports any form of QC and you'll become famous throughout this forum.
https://forum.xda-developers.com/le...el-z2-plus-t3652855/post73642105#post73642105
Use Lenovo QC 3 charger
https://www.xda-developers.com/charging-comparison-oneplus-huawei/
n00b_dr0id said:
Use Lenovo QC 3 charger
https://www.xda-developers.com/charging-comparison-oneplus-huawei/
Click to expand...
Click to collapse
What charger doesn't matter as long as the phone has/doesn't have the QC3.0 charging chipset.
What's your point anyways?
luws said:
https://forum.xda-developers.com/le...el-z2-plus-t3652855/post73642105#post73642105
Click to expand...
Click to collapse
72%/hr charging or draining?!
Please do elaborate your point.
Incrovantilist said:
What charger doesn't matter as long as the phone has/doesn't have the QC3.0 charging chipset.
What's your point anyways?
Click to expand...
Click to collapse
There is no separate 'chipset' per se for QC. It's SOC. I included the article for further reading. Every manufacturer has his own implementation and/or scripts other brand chargers hence don't work. If any one has a Lenovo QC 3 charger can verify.
n00b_dr0id said:
There is no separate 'chipset' per se for QC. It's SOC. I included the article for further reading. Every manufacturer has his own implementation and/or scripts other brand chargers hence don't work. If any one has a Lenovo QC 3 charger can verify.
Click to expand...
Click to collapse
Bro first please know the basics. Sure you need your SoC to support a particular QC protocol inorder for it to work but that's not it. OEMs need to implement Quick Charge delivering PMIC (Power Management Integrated "Chipset") along side the SoC for the desired QC protocol to work. On paper almost all Qualcomm SoC launched after 2015 support some form of QC (check Qualcomm website). But since Qualcomm demands a Royalty charge for using their QC patent, OEMs implement QC protocols in only certain devices. Though Lenovo should have implemented official QC on our phones (considering that almost all SD820 devices have QC support), due to price factor they didn't. They did implement some form of fast charging protocol developed by themselves, which is nearly equal to QC1.0 or more precisely I'd regard it as QC1.5 (since it's little better than QC1.0). As far as I researched, I came to know that the PMIC in our phone is actually a QC3.0 capable one. That's the reason I started this thread, looking for Unofficial developer support to enable QC3.0 on kernel level.
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