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.
Related
With the latest update of googles my tracks now ant+ support was added for external sensors, like footpods, heart rate monitors etc.
Anyone have an idea if the defy has the appropriate chip in it that will enable this in the future? Have read so far in a very early forum statement from motorola that this would not work but then again what customer support tells you is not always the whole truth Both the TI omap 3610 and 3630 does according to their product sheet indicate to support the needed wilink chip. Ericsson have just last week activated ant+ support in all their current android phones so it does seem possible to do things like this, if the manufacturer wants off course
Appreciate any help or info! Thanks
I'm also looking for this, there are some indications that the chipset supports this hardware wise, below is a comment quoted from Jollo at the Motorola developer forum:
"Maybe you know about the first attempts to ANT+ sensor usage in android phones by HTC (ANT+ could be seen as de-facto standard for sports activities sensors like foot- or heart-pace). They used an ordinary Legend which was just flashed to enable the ANT+-capabilities of the TI WiLink radio chipset.
In case the Defy will use such chipset (specs don't name this, but even WiLink Gen. 6 should be adequate), this phone as one of the rare ruggedized ones running Android could become an outstanding sports-device. Even if there is no Software using these capabilities of recording heart-pace or other sensor-data yet, i could imagine that this would be just a question of weeks after the first ANT+-enabled Android phone will reach the market"
http://community.developer.motorola...EFY-development-resources-available/td-p/7794
//Dave
Any information of the possibility of supporting Ant+ by the Defy?
Hi,
this is just an idea. I have to say I do not know to much details about Android driver programming but is there perhaps a chance to port/take the driver from the MOTOACTV device.
www engadget com/2011/12/24/motoactv-torn-down-and-rooted-turned-into-a-tablet-for-ants/[/url]
de engadget com/2011/12/26/motorola-motoactv-wird-kleinstes-tablet-der-welt-video/
(Sorry I am not allowed yet to post direct links)
Perhaps an expert could give a statement here!?
All the best,
Markus
Nobody an idea from this topic ant+ driver for defy?
I was wondering if the 5.0 update will enable SDR104 and accordingly full speed support for UHS-1 to the Note 4 in the future. Its interesting that since the 600 there has been UHS-1 capability at the SoC level but to date zero devices running SDR104 with Qualcomm's chips. Is it because the SD reader physically can't supply enough power or the perception that it is irrelevant due to the limitations imposed by Android before 5.0? Maybe both? I've contacted Samsung and pretty much scoured the web obsessively and there has been no explanation and very few questions ever asked about why, which I find suspicious.
I just heard that Vulkan API is coming to mobile and it is supporting PowerVR chips like the one we have on the phone.
(PowerVR G6430). Some people say on the ZENTALK forum that that's why it takes so much freaking time for Asus to implement Marshmallow as they are busy incorporating the API on the phone.
If this is true just image the gigantic boost it will give to our phones! (just watch on Youtube or search on Google for more information about Vulkan API)
If Vulkan API is implemented at our phone it would be fantastic. Hope Asus will work on the API and make the best for our phone, let's see in a couple of months of so
Too good to be true man, too good to be true.
hi, I'm very interested in everything about vulkan since i could see some videos about it. But my knowledge about api, android and rom's is not that good, so i would thank you if i could get some answers.
1 - Is this implementation of API a work for ASUS or Intel?
2 - Since i saw that PowerVR Rogue has now SDK(i dont know what it is) for Vulkan, Is ANYONE able to make a custom rom that could use Vulkan?
3 - I've heard that Android N will have native support for Vulkan. Does it mean that if i download a custom rom, like a cyanogenmod, for Android N to my Zenfone 2 i will have the benefits of using Vulkan?
4 - Does anyone know if that Galasy S7 that had 135k+ on antutu was using Vulkan? Because my Zenfone 2 is a great phone and only scores 65k, it's scary to thing that a S7 should have more than the double of hardware capacity that my Zenfone has. I thing that should be because of vulkan, but i need to hear it from someone who knows what's talking.
I hope to get answers for this questions. Thank you all.
SSJMatt said:
)Some people say on the ZENTALK forum that that's why it takes so much freaking time for Asus to implement Marshmallow as they are busy incorporating the API on the phone.
Click to expand...
Click to collapse
Sorry, that's not how ASUS usually manages fixes and updates. That would take time and money and we've already spent our money so they have nothing to gain, therefore nothing will happen. Only future customers are a priority for ASUS.
A happy ASUS customer is one with low expectations.
Well, at least It'd give Asus a good excuse for being so late...
Vulkan is something that would need to be implemented at the OS level on Android (mainly the kernel, no idea what other bits Google is including in the rest of the OS). And support for each hardware would need to be provided by the OEM or manufacturers. It MAY be possible for a custom ROM to implement Vulkan support in some fashion in a current version of Android (harder and more "impossible" things have been accomplished) but it's not likely due to too many technical challenges. Besides, it wouldn't happen until after Android N is released and the AOSP code is posted. Only then would someone attempt to backport Vulkan.
I'm not 100% sure, but I do believe that Vulkan support will be a requirement by Google for devices to run Android N. So if Asus does plan on upgrading the phones then they will need to include a kernel for the hardware that supports Vulkan and those drivers would come from Intel. So the chance of the Zenfone supporting Vulkan is 100%, provided Asus upgrades it to N.
SSJMatt said:
I just heard that Vulkan API is coming to mobile and it is supporting PowerVR chips like the one we have on the phone.
(PowerVR G6430). Some people say on the ZENTALK forum that that's why it takes so much freaking time for Asus to implement Marshmallow as they are busy incorporating the API on the phone.
If this is true just image the gigantic boost it will give to our phones! (just watch on Youtube or search on Google for more information about Vulkan API)
Click to expand...
Click to collapse
So is the VULCAN API present in the M update?
Is Vulkan something like the Mantle for Desktops?
EDIT:
Vulkan Drivers for Nexus Player
Google’s Android Image
As part of the Android N Developer Preview 2 release, Google released an Android N image for the Nexus Player that includes Vulkan drivers. You can find out more about the Android N Developer Preview here and can download the image here. As this image is officially supported by Google, we recommend using it for Vulkan Android development.
Click to expand...
Click to collapse
https://community.imgtec.com/developers/powervr/vulkan/
There is two possibilities:
1- Vulkan added in Android N's mainline code, and CM14 (maybe) will do this too.
2- Vulkan driver will be only in manufacters Android N's source. In this case, will be needed to be backported.
In both possibilites, isnt impossible to do it, even without Asus help. But would be awesome if some official MM give it to us (not in the first version, obviously).
Its GPU manufacturer job to implement vulkan, they provide the drivers to OEM manufacturer implement it on their otas. Nvidia already did that on latest MM update to shield TV and shield tablet.
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.
I know this phone runs on a Qualcomm SOC, but every website, including the official Xiaomi site, states that it supports "18W Fast Charging" and not Qualcomm QuickCharge. Is it intentional, as in is it another charging standard that my QC3.0 chargers around the house, in my car, office, won't support or is it just due to some kind of trademark that they can't mention it officially?
Also, is there any particular difference between K20 and 9T given I will be flashing a custom ROM anyway? (I am familiar with Xiaomi products and I know it is baseline the same device, but maybe there is something I should take note of before buying either one)
https://forum.xda-developers.com/mi-9t/accessories/quick-charger-t3964764
Anyway it want work
mvha said:
https://forum.xda-developers.com/mi-9t/accessories/quick-charger-t3964764
Anyway it want work
Click to expand...
Click to collapse
You mean <won't> right?