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?
Just wondering if there is a specific answer as to whether the IR blaster will/can work in custom ROMs.I have read/heard that in some ROMs, like CM 10.1 I believe, that it doesn't work "yet". So should I assume that it's catch-as-catch-can?
For full disclosure, I'm still using my N4 but am strongly considering grabbing an S4, primarily because I can't stand the N4 battery life anymore, want LTE again ( I had an S3 briefly) and a better camera would be nice. But, I will almost certainly root and flash something more stock but definitely want to keep the IR functionality.
Thanks in advance for the help.
It's highly unlikely that custom non-TouchWiz roms like CM10.1 will be able to use the IR blaster. I'm hopeful that the upcoming Google Edition of the GS4 will have functionality so it can be ported to AOSP roms.
snakecharmer23 said:
It's highly unlikely that custom non-TouchWiz roms like CM10.1 will be able to use the IR blaster. I'm hopeful that the upcoming Google Edition of the GS4 will have functionality so it can be ported to AOSP roms.
Click to expand...
Click to collapse
Really? I'm not a developer by any stretch, but does that mean that they have no way of accessing the hardware? What if you were to use a 3rd party remote app, like Peel?
Push the SamsungWatchOn app to your phone and see if it works.
C13v3r0n3 said:
Push the SamsungWatchOn app to your phone and see if it works.
Click to expand...
Click to collapse
It doesn't. I tried it. There are no drivers for the IR Blaster. I would say unless the Google edition has it we are SOL. No apps work it that I tried, and I tried most all of them in the Play Store.
The Google edition of the S4 will not use the Samsung apps or make use of some of the hardware from what I understand. No S-view or gestures or temp sensors or IR or any of that. Which is a huge bummer if you ask me. We don't need T-Wiz but make use of the hardware and capabilities at least.
Just do yourself a favor and download Smart Remote. Problem solved.
Sent from my SAMSUNG-SGH-I337 using xda premium
justlaxin13 said:
Really? I'm not a developer by any stretch, but does that mean that they have no way of accessing the hardware? What if you were to use a 3rd party remote app, like Peel?
Click to expand...
Click to collapse
I'm no dev either.... but I did stay at a Holiday Inn Express last night!
I'll be keeping my fingers crossed that the Google version won't leave half the hardware useless.
my comment is not to bash, it's just my opinion. i get that people want to run stock android because they are used to it from other devices or they may just like the look and feel of it. i like stock android also, just not on my gs4. there is hardware on this phone that stock android can not take advantage of. like all the sensors and aspects of the camera. i just cant bring myself to have stock android knowing that i paid for a phone that can do other things yet i cant use those other things. i dont know what the google edition of gs4 will have, but something tells me it will just be like us putting an aosp rom on our devices right now and not having the drivers to take advantage of the other aspects of the phone hardware. makes me feel like why did i buy this phone with these sensors on it if i cant use them? i should have instead got a different phone that has a 1080p screen with a quad core cpu with ext sdcard, minus the extra gs4 hardware that makes it unique, so that the stock android can take full advantage of.
What about touch squid? Does that work?
Sent from my GT-N7100
@rbiter said:
What about touch squid? Does that work?
Sent from my GT-N7100
Click to expand...
Click to collapse
no ir blaster driver in rom = no app that can run the hardware. needs to be a touchwiz based custom rom. like mdob rom.
I'm 100% positive they will make use of the IR Blaster or atleast include simple drivers for developers to run with.
Let me make this clear, Samsung is NOT going to produce the device with an IR device on the developer edition if they don't plan on giving Google drivers. As if Samsung is gonna waste money on perfectly good IR Blasters to never ever be used....
It's either gonna have the IR Blaster and have simple functionality, or the hardware will be scrapped to save money.
snakecharmer23 said:
I'm no dev either.... but I did stay at a Holiday Inn Express last night!
I'll be keeping my fingers crossed that the Google version won't leave half the hardware useless.
Click to expand...
Click to collapse
WELL you might as well cross your fingers, toes, eyes, and hold your breath.
ZPaul2Fresh8 said:
Just do yourself a favor and download Smart Remote. Problem solved.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Samsung includes an 'irda' driver in their open source, isn't that the driver? If that's the case, couldn't someone compile that driver into a kernel and then we could use apps like Smart Remote?
No rom will work if the Samsung Framework is not installed. If it were as easy as just installing the IR driver in the ROM, i'm pretty sure all roms would be compatible with it by now, or some dev would create a patch for it
Nothing to see here you need Touchwiz to use it. I would not bet on the Google edition having it. Google will not have all the bells and whistles like everybody things.
You need ir blaster stick with stock rom and forget the rest.
The framework is definitely needed for stuff like WatchOn or anything that calls the IR Blaster through the framework, but an app like SmartRemote that calls the hardware directly through the drivers wouldn't need the framework.
I didn't look too much at the irda drivers but I an fairly certain that one could just compile support for that in and if the app is non-samsung that the support should be there the same as any external ir blaster.
Please read forum rules before posting
Questions and help issues go in Q&A and help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Thermalwolf said:
I'm 100% positive they will make use of the IR Blaster or atleast include simple drivers for developers to run with.
Let me make this clear, Samsung is NOT going to produce the device with an IR device on the developer edition if they don't plan on giving Google drivers. As if Samsung is gonna waste money on perfectly good IR Blasters to never ever be used....
It's either gonna have the IR Blaster and have simple functionality, or the hardware will be scrapped to save money.
Click to expand...
Click to collapse
I doubt the actual hardware will be scrapped. This would require a change to their hardware manufacturing process which will be a costly change for them. It seems that the Qualcomm S4s are almost completely identical less firmware and software changes, which would occur after the hardware build.
Because the production volumes of the S4 are so high, the cost of adding these sensors is probably trivial, either cents or fractions of a cent per unit. Changing the production lines to modify the manufacturing, after all of the labor, QC, etc., is likely to cost more per phone than simply including the part, at least at the production volumes we can reasonably expect to see.
Given the volumes on this edition of the S4 will most likely be nowhere near the volumes of the ATT or VZW standard models, the cheapest way for Samsung to create this SKU would be to re-badge the existing hardware with the vanilla software. After all, this is exactly what they did with the i337m.
Of course, this doesn't guarantee drivers will be available for the IR. However, this model is targeted to the enthusiast market, and they would likely see sales of the new SKU cannibalized by other models if they didn't include basic functionality.
After all, why would I buy the Google edition with no IR support when I can go buy the T-Mobile model, with a choice of carrier subsidy, if the end result is essentially the same? I could just buy that one and flash CM10 or equivalent if I don't get IR either way, and I can get that from my friendly neighborhood retail outlet.
Since this model seems to be marketed to enthusiasts, the amount of loss they would sustain by not including an IR driver could be substantial enough that it wouldn't make economic sense to have created the additional SKU in the first place.
Again, this is all speculation, but this is where I'd place my bet. Now watch, since I've stated this, Murphy's Law will kick in and I will be completely wrong...
Sent from my SGH-I337 using XDA Premium HD app
Well if the follow the HTC model the IR blaster will just be disabled
Wayne Tech Nexus
Hello guys
May i ask if OmniROM will ever make it to the Xperia Z2 (Sirius)?
Been missing it for ages now
Keep up the great work
mariotme said:
Hello guys
May i ask if OmniROM will ever make it to the Xperia Z2 (Sirius)?
Been missing it for ages now
Keep up the great work
Click to expand...
Click to collapse
I normally just report device requests, but since I've done a lot of the Sony bringups:
I wanted a Z2. I really, really wanted one.
However I don't buy greymarket imports, and Sony refused to sell the Z2 in North America until after the Z3 was launched. Even now, the purchasing link is nearly impossible to find (it is not listed for sale anywhere on sonymobile.com)
Z3 is a possibility if it goes on sale unlocked in North America in a timely fashion. (Which is unlikely...) Z2 is a possibility if some maintainer picks it up, of course, but considering the device's successor is out now, that's pretty unlikely.
Entropy512 said:
I normally just report device requests, but since I've done a lot of the Sony bringups:
I wanted a Z2. I really, really wanted one.
However I don't buy greymarket imports, and Sony refused to sell the Z2 in North America until after the Z3 was launched. Even now, the purchasing link is nearly impossible to find (it is not listed for sale anywhere on sonymobile.com)
Z3 is a possibility if it goes on sale unlocked in North America in a timely fashion. (Which is unlikely...) Z2 is a possibility if some maintainer picks it up, of course, but considering the device's successor is out now, that's pretty unlikely.
Click to expand...
Click to collapse
I totally understand Entropy512! Thanks for your input buddy. Appreciate all your efforts man. Keep it up :good:
Entropy512 said:
I wanted a Z2. I really, really wanted one.
Click to expand...
Click to collapse
Thanks for your answer, yes that's the best smartphone I've ever got! Why the hell do they think they don't need to sell their devices in america??
As I know you are a major developer of OmniRom, I really hope you will be able to get an Xperia Z4, and hopefully port the ROM on it..
Thanks for your work!:good:
May I Taste said:
Thanks for your answer, yes that's the best smartphone I've ever got! Why the hell do they think they don't need to sell their devices in america??
As I know you are a major developer of OmniRom, I really hope you will be able to get an Xperia Z4, and hopefully port the ROM on it..
Thanks for your work!:good:
Click to expand...
Click to collapse
I'll probably skip the Z4 thanks to Sony's crazy 6-month product cycle.
I have a Z3 but so far it's stock. This device is holding a record for the longest I've gone without root/unlocking the BL.
Sony did an awesome job with the stock firmware on the SIM-unlocked Z3.
Entropy512 said:
I'll probably skip the Z4 thanks to Sony's crazy 6-month product cycle.
I have a Z3 but so far it's stock. This device is holding a record for the longest I've gone without root/unlocking the BL.
Sony did an awesome job with the stock firmware on the SIM-unlocked Z3.
Click to expand...
Click to collapse
Thanks for your kind answer and I can understand you. It seems however that the Z4 will now last for one year as flagship. Anyway I'll make sure to stay tuned if by chance you work on OmniROM for it.
Have a wonderful year, you and your whole family!
There some unofficial builds for the Sony Sirius floating around...
http://infectedbuilds.net/downloads/sirius/omni_lp/
From my very brief play with it, there's no Cam or NFC but everything else seems pretty useable.
A number of Omni team members are working with the Sony AOSP guys. Short-term it means a lot of things are broken that aren't in CM since Sony AOSP is reworking a bunch of stuff onto a newer unified kernel that will support a large variety of devices. Long-term it'll allow us to support more Sony devices with less effort.
I think one of the guys working this has a sirius... I forget who.
I just synced all the Omnirom repos and compiled for the Z2. It works ok, just no Camera, recovery and there seems to be a bug around internal storage, as it thinks there is no space left.
I'd be interested in helping to fix these things, I'm pretty comfortable using git and gerrit and know some Java and C++ but I have no idea where to start.
Code:
adb logcat | grep camera
- waiting for device -
E/CameraService( 373): Could not load camera HAL module
W/ResourcesManager( 1057): Asset path '/system/framework/com.google.android.camera2.jar' does not exist or contains no resources.
I/CameraManagerGlobal( 1057): getCameraService: Reconnecting to camera service
E/CameraService( 373): getCameraVendorTagDescriptor: camera hardware module doesn't exist
W/CameraManagerGlobal( 1057): Failed to set up vendor tags: The camera device is removable and has been disconnected from the Android device, or the camera service has shut down the connection due to a higher-priority access request for the camera device.
So I'd guess I'd have to find out why the camera HAL module can't be loaded?
mikeysteele said:
I just synced all the Omnirom repos and compiled for the Z2. It works ok, just no Camera, recovery and there seems to be a bug around internal storage, as it thinks there is no space left.
I'd be interested in helping to fix these things, I'm pretty comfortable using git and gerrit and know some Java and C++ but I have no idea where to start.
Code:
adb logcat | grep camera
- waiting for device -
E/CameraService( 373): Could not load camera HAL module
W/ResourcesManager( 1057): Asset path '/system/framework/com.google.android.camera2.jar' does not exist or contains no resources.
I/CameraManagerGlobal( 1057): getCameraService: Reconnecting to camera service
E/CameraService( 373): getCameraVendorTagDescriptor: camera hardware module doesn't exist
W/CameraManagerGlobal( 1057): Failed to set up vendor tags: The camera device is removable and has been disconnected from the Android device, or the camera service has shut down the connection due to a higher-priority access request for the camera device.
So I'd guess I'd have to find out why the camera HAL module can't be loaded?
Click to expand...
Click to collapse
Camera is far away from being supported. The blobs are completely missing, because they simply won't work with our kernel.
There's work being done, however a lot of it has to be done by someone within Sony and that results in stuff having to go through a legal approval process.
In theory it might be possible with some work to get 5.0 camera blobs working with a lot of kernel hacking, but most people are focusing on a cleaner approach that will take longer and unfortunately has dependencies on Sony's lawyers.
Entropy512 said:
Camera is far away from being supported. The blobs are completely missing, because they simply won't work with our kernel.
There's work being done, however a lot of it has to be done by someone within Sony and that results in stuff having to go through a legal approval process.
In theory it might be possible with some work to get 5.0 camera blobs working with a lot of kernel hacking, but most people are focusing on a cleaner approach that will take longer and unfortunately has dependencies on Sony's lawyers.
Click to expand...
Click to collapse
Thanks for the update. I noticed there weren't any camera blobs in the source, so I assumed it wasn't as simple as just adding them in. I see on github the CM guys hacked their kernel to be able to use the old Jellybean camera blobs which looks painful. Hopefully Sony's lawyers aren't too obstructionist. Although to their credit the Sony stock rom isn't actually too bad. Nothing compared to Omni Rom though.
mikeysteele said:
Thanks for the update. I noticed there weren't any camera blobs in the source, so I assumed it wasn't as simple as just adding them in. I see on github the CM guys hacked their kernel to be able to use the old Jellybean camera blobs which looks painful. Hopefully Sony's lawyers aren't too obstructionist. Although to their credit the Sony stock rom isn't actually too bad. Nothing compared to Omni Rom though.
Click to expand...
Click to collapse
Yeah. They used a kernel backcompat hack, and are using old 4.3 rhine blobs because those are the last ones that were completely 100% DRM-free.
DRM issues have caused all sorts of problems with rhine/shinano cameras ever since 4.4 - Workarounds for many of these have been found, but not all. But the kernel backcompat hacks would still be needed (potentially multiple hacks for each device supported by the Sony AOSP kernel) and that gets nasty.
So the current plan is to have a unified set of sensor drivers in the kernel, with blobs provided as part of the Sony AOSP project. However I think this is going to be easier said than done - it's not just Sony lawyers, but Qualcomm lawyers. It really sucks that the entirety of Qualcomm's mm-camera subsystem is proprietary and there's no way for an opensource developer to write modules for it, which prevents any of the community side of the Sony AOSP project from working on some things. Otherwise it would probably be not too difficult to replace Sony's noise reduction algorithm (likely with a better one... Sony's NR algorithm got slammed for being too aggressive and killing sharpness over in a dpreview review... All that DRM protection for something some people actually prefer to have gone.)
Edit: And yes, Sony's stock firmwares are amazing. My Z3 holds the record for longest I've ever owned a device without even bothering to root it.
Another thing, my phone is the China Mobile version (L50t) and OmniRom runs perfectly on it, I just have to change the radio and wlan firmware. I can supply the required files and be a tester if you wanted to add official support for this varient.
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.
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.