First off, a little background.
The first few days after buying the Moto X I found MotoDisplay a little too sensitive and, to be honest, a little annoying that it would turn on all the time, but after a while I started getting used to it and subconsciously dependent on the way it works.
A few days ago I remembered using an application on my galaxy nexus which kind of did the same thing, and so I tried replacing MotoDisplay with one of the alternatives from the playstore. I chose AcDisplay and I really liked most of it's features (it's animations are beautiful). Except it doesn't use the IR sensors.
AcDisplay being an open source project, I thought to my self "I could probably implement a feature similar to MotoDisplay's extremely sensitive wave to wake up". So I looked for examples on how to use the IR Sensors and found none. I looked for an SDK/API and found nothing. I've looked at motorola's github and none of the repositories seemed to be what I wanted.
So the question is, how can I make a program that makes use of the Moto Xs IR sensors? Are there any resources on how to use them, or is this feature closed source and I'm not supposed to use it?
Apparently, apart from the official MotoDisplay, the only other project making use of these sensors is CM12 (which I haven't tried myself), which leads me to believe that it's not as simple as using the other, more common, sensors.
bump
evilnoxx said:
First off, a little background.
The first few days after buying the Moto X I found MotoDisplay a little too sensitive and, to be honest, a little annoying that it would turn on all the time, but after a while I started getting used to it and subconsciously dependent on the way it works.
A few days ago I remembered using an application on my galaxy nexus which kind of did the same thing, and so I tried replacing MotoDisplay with one of the alternatives from the playstore. I chose AcDisplay and I really liked most of it's features (it's animations are beautiful). Except it doesn't use the IR sensors.
AcDisplay being an open source project, I thought to my self "I could probably implement a feature similar to MotoDisplay's extremely sensitive wave to wake up". So I looked for examples on how to use the IR Sensors and found none. I looked for an SDK/API and found nothing. I've looked at motorola's github and none of the repositories seemed to be what I wanted.
So the question is, how can I make a program that makes use of the Moto Xs IR sensors? Are there any resources on how to use them, or is this feature closed source and I'm not supposed to use it?
Apparently, apart from the official MotoDisplay, the only other project making use of these sensors is CM12 (which I haven't tried myself), which leads me to believe that it's not as simple as using the other, more common, sensors.
Click to expand...
Click to collapse
You can look at the CyanogenMod CMactions source code. However, you are going to have selinux problems as you need to touch the raw driver to enable wakeups.
crpalmer said:
You can look at the CyanogenMod CMactions source code. However, you are going to have selinux problems as you need to touch the raw driver to enable wakeups.
Click to expand...
Click to collapse
That seems way to hard for me. Thank you anyway for the reply
Related
Hello,
As It's difficult to search for "ANT+" in the forums, sorry if this issue has already been addressed
And now some extra keywords to ease the search: ant, ant+, antplus, ant_plus, antwireless, ant_wireless
This is a thread to summarized all the facts about ANT+ and the Nexus 5 I have found so far:
HARDWARE: BCM4339. The Nexus 5 has this chip which provides WiFi, BT and presumably ANT+. It's also present in the Galaxy Note 3 which reportedly has ANT+ capabilities.
DRIVER: The required driver source can be found here: https://github.com/ant-wireless . Once compiled it generates a module (libantradio.so) and two apk (AntHalService.apk, ANTRadioService.apk).
SOFTWARE: There are several apps with ANT+ enabled, but for testing purposes the ANT+ demo can be used.
To be able to test ANT+ I have the Nexus 5 and ANT+ capable hardware (HRM, cadence sensor, etc), the ANT+ Demo in google play but I'm missing the driver.
I know I need a kernel with module loading enabled (for example this modified stock: http://forum.xda-developers.com/showthread.php?t=2514765) but I don't know howto to compile the ANT+ module.
Can someone generate the driver as per the instructions in https://github.com/ant-wireless/ANT_in_Android or explain me how to do it?
I'm on a linux host, I have a rather limited experience in compiling stuff but I'm not afraid of learning something in the process!
Thanks!!
very interested in the results. thank you for your work on this
interested
Subscribed.
I am also interested in this as I have my phone and Garmin Forerunner watch with me when I run so if I can just carry my phone and get the same data that would be awesome!
If no one else takes this on, I'll see about looking into it later. Keep in mind though that I'm not a developer of any sort but am comfortable with compiling kernels. I have an ANT+ HRM from my Motoactv that I'd like to use.
Ok,
So far I haven't able to compile stock kernel. I'm trying with NDK GCC 4.7 without success: http://forum.xda-developers.com/showthread.php?p=47577117
But I've investigated in other fields. I've downloaded S4 and Note3 ROMS with ANT+ support to have a look at the files.
S4 CRASH_ROM_V11: http://forum.xda-developers.com/showthread.php?t=2322619
Note3 BoBCaTROM_V2.0: http://forum.xda-developers.com/showthread.php?t=2498687
This is want I've found so far:
There are three system apps: AntHalService.apk, ANTRadioService.apk and ANTPlusPlugins.apk. These two latter can be found in google play. The first app is the one that "informs" the system that the device is ANT+ capable (as stated in the ant_wireless git). I've tried to install this apk manually but fails due to certificates (samsung).
S4, Note3 and Nexus5 have all different revisions for the bcm433x firmware but they all have an "ANTLockUsed" string in it (hexdump). Is it related to ANT+ or the ANTenna? Incidentally, the wisol firmware revision doesn't have this string.
The rest of the files related to ANT+ are for the com.dsi.ant.antradio_library (etc/permissions and framework files).
I can't find any ANT+ related module (ant*.so, libant*.so). Thus, is it already compiled in the kernel or not needed at all?
I've uploaded all these files in case anyone wants to have at look them.
Subscribed. ANT+ support would be awesome for all the athletes out there.
I'm a big supporter of ANT+. I wish I knew more about Android to help on this side. I have a blog that documents a lot of hacking projects related to ANT+.
If the Nexus 5 could access ANT+ it could be an amazing cycle computer potentially.
I work a bit with a SOC from Nordic. The way it works for BLE is that it compiles and downloads a soft protocol. I'm wondering if this is how the Boardcom chip works too. My reasoning is in the github:
Additionally, in Android 4.2, the Bluetooth stack switched to Bluedroid (from BlueZ) and this existing ANT implementation for chips using Vendor Specific Bluetooth HCI messaging for ANT packets (wl12xx and bcm433x) is currently not compatible, until somebody is able to do the work for the different bluetooth stacks. The chip vendors may provide build support for their own products if you inquire with them.
Click to expand...
Click to collapse
So it sounds like, because ANT+ and BLE are so similar, they upload a new stack to the chip which enables it. However, this stack is not in the wild.
kwakeham said:
So it sounds like, because ANT+ and BLE are so similar, they upload a new stack to the chip which enables it. However, this stack is not in the wild.
Click to expand...
Click to collapse
That makes sense as I wasn't able to find any more files related to ANT+ (directly not by looking into the source code).
However, I'm very stubborn and I want ANT+ in the nexus :silly:
First of all: It still doesn't work, but so far I've learnt a few things.
First I copied the Note3 files (attached) related to ANT+ (root needed, remember to chmod 644):
/system/app/AntHalService.apk (modified to strip samsung certificates)
/system/etc/permissions/com.dsi.ant.antradio_library.xml
/system/framework/com.dsi.ant.antradio_library.jar
/system/vendor/firmware/bcm4335_A0.hcd (renamed to bcm4335c0.hcd to max nexus5 firmware name. Backup old one first!!)
Upon reboot I also installed from google play the rest of ANT+ app required.
ANT radio service: https://play.google.com/store/apps/details?id=com.dsi.ant.service.socket
ANT+ Plugins: https://play.google.com/store/apps/details?id=com.dsi.ant.plugins.antplus
ANT+ Demo: https://play.google.com/store/apps/details?id=com.dsi.ant.antplusdemo
When using the ANT+ Demo App it doesn't warn about anything missing (good!!) but when searching for the HRM I have it just fails (bad!!). It fails with either firmware (nexus or note). In any case dmesg doesn't so any info related to ANT+.
To summarize:
The previous files are needed so that androids "knows" ANT+ hardware is present, but
Something else needs to be modified. As stated by kwakeham probably the bluetooth stack.
I have no android or coding skills (or any skills at all ), but with this information I hope someone can have a look at the modified bluetooth stack of either S4 or Note3 to port those changes to Nexus5 :fingers-crossed:
I'm very confident because XDA is a great place with lots of wonderful people, fully capable of implementing ANT+ in the Nexus5.
They've done much harder things!!
Is it true that Bluetooth 4.0 can only connect to one device at a time? So, if we wanted to monitor heart rate on the phone and listen to music via bluetooth headphones, this would not be possible unless we used an ANT+ heart rate monitor, correct?
Cleanskinned said:
Is it true that Bluetooth 4.0 can only connect to one device at a time? So, if we wanted to monitor heart rate on the phone and listen to music via bluetooth headphones, this would not be possible unless we used an ANT+ heart rate monitor, correct?
Click to expand...
Click to collapse
Close but not quite.
A BT4 HR strap will only allow one device to connect to it at a time but the phone can connect to multiple BT devices at the same time. ANT+ lets an infinite number devices to connect to a single HR strap, so like your phone stashed in your pocket and a running watch on your arm. ANT+ would also allow you to read data from hundreds of sensors, though that would be more useful for a trainer at a spin class or something lol.
Exactly, and to verfy that I just connected two Bluetooth 4.0 devices with my Nexus 5. My Pebble and the fitbit Flex from my girlfriend, both worked fine simultaneously.
Btw, windows has a limit of 7 connected Bluetooth devices at a time, but that's not caused by the Bluetooth specification.
Sent from my Nexus 5 using xda app-developers app
Hello,
Still no success.
I've been looking into the source code of both S4 and Note3 opensource kernels for android version 4.3, but due to lack of coding skills I just have no idea of what to search.
The source code of bluetooth stack from these kernels and the one for nexus5 seem completely different thus it's hard to draw any conclusions. The only thing clear is that running a "grep" search into the code for "ant+", "antplus", "ant_wireless" (or similar) doesn't show any results.
It seems someone is working on having ant+ on the google editon S4: http://forum.xda-developers.com/showthread.php?t=2542922
Let's hope his work can be reused for the nexus5.
PS. I don't have enough posts yet to ping him back to this thread but I will try to use the files he has attached.
usu4rio said:
It seems someone is working on having ant+ on the google editon S4: http://forum.xda-developers.com/showthread.php?t=2542922
Let's hope his work can be reused for the nexus5.
PS. I don't have enough posts yet to ping him back to this thread but I will try to use the files he has attached.
Click to expand...
Click to collapse
That's me. I've found you looking for some info to help me out.
The main issue I'm facing is the AntHalService.apk from the vendors(Samsung,Sony) is the 3.0.0 and there were 2 updates already.
I compiled the 3.1.1 but I can't run it as a system app.
Regarding the Nexus 5, I guess that since S4 got ANT+ activated on 4.3, something in the updated radio probably activated it, and as you mentioned, no .so modules on the system.
Maybe analyzing the ANTHal code deeply might bring up some light on this.
Btw, you're Brazilian or Portuguese or Spanish? (due to your nickname)
If so, we can add each other on G+ and progress on talks to see if we can bring some light to the athlete droiders out there...
Worst case scenario you can use an USB Ant+ Stick with an OTG cable. (what I am going to do while I research for this.... )
Oh, btw, Galaxy S3 also had the hardware but Samsung never activated it...
ADD
AdrienC said:
That's me. I've found you looking for some info to help me out.
The main issue I'm facing is the AntHalService.apk from the vendors(Samsung,Sony) is the 3.0.0 and there were 2 updates already.
I compiled the 3.1.1 but I can't run it as a system app.
Regarding the Nexus 5, I guess that since S4 got ANT+ activated on 4.3, something in the updated radio probably activated it, and as you mentioned, no .so modules on the system.
Maybe analyzing the ANTHal code deeply might bring up some light on this.
Btw, you're Brazilian or Portuguese or Spanish? (due to your nickname)
If so, we can add each other on G+ and progress on talks to see if we can bring some light to the athlete droiders out there...
Worst case scenario you can use an USB Ant+ Stick with an OTG cable. (what I am going to do while I research for this.... )
Oh, btw, Galaxy S3 also had the hardware but Samsung never activated it...
Click to expand...
Click to collapse
i have a Galaxy S4 but i want to change it for Nexus 5
i hope it works
following
HI to all
I'm interesting on this too and I'm waiting how advance this to buy an nexus 5
You will try to ask on thisisant forum. there are developers from ant+ and offer some news about phones sometimes.
Waiting news, best regards to all.
Guys, I've got a message from @fcastillousfq and I think it might be of your interest my response:
fcastillousfq said:
Hey, I saw the post about getting a USB accessory for the Nexus 5 to be able to use ANT+ as a last resource, I've been searching online and can't find any for Android, only for iPhone. The only one I've found was huge and it's not for sale yet.
Could you provide me a link or the name of the accessory so I could buy it?
Thanks!
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Sure, it the Suunto Movestick Mini + OTG Cable
Then you have to install:
https://play.google.com/store/apps/details?id=com.dsi.ant.usbservice
https://play.google.com/store/apps/details?id=com.dsi.ant.service.socket
https://play.google.com/store/apps/details?id=com.dsi.ant.plugins.antplus
https://play.google.com/store/apps/details?id=com.dsi.ant.antplusdemo (for testing)
https://play.google.com/store/apps/details?id=com.dsi.ant.antplus.grapher.heartrate (for testing)
And you're set. It's pretty easy!!
ps: forget to mention that you can use regular size ant+ usb sticks, as the one from Garmin, but I preferred this one as it's smaller.
With a bit of DIY you can make something smaller.
Thanks for the info! I'm going to look into it and probably buy it.
I'm also considering the Viiiiva, which acts as a bridge between all my Ant+ devices and Bluetooth 4. The bad thing is that there's no android app yet, in the mean time, the USB one will suffice.
Sent from my Nexus 5 using xda app-developers app
AdrienC said:
That's me. I've found you looking for some info to help me out.
The main issue I'm facing is the AntHalService.apk from the vendors(Samsung,Sony) is the 3.0.0 and there were 2 updates already.
I compiled the 3.1.1 but I can't run it as a system app.
Regarding the Nexus 5, I guess that since S4 got ANT+ activated on 4.3, something in the updated radio probably activated it, and as you mentioned, no .so modules on the system.
Maybe analyzing the ANTHal code deeply might bring up some light on this.
Btw, you're Brazilian or Portuguese or Spanish? (due to your nickname)
If so, we can add each other on G+ and progress on talks to see if we can bring some light to the athlete droiders out there...
Worst case scenario you can use an USB Ant+ Stick with an OTG cable. (what I am going to do while I research for this.... )
Oh, btw, Galaxy S3 also had the hardware but Samsung never activated it...
Click to expand...
Click to collapse
Sorry for the delay.
Yes! spanish :good:
Unfortunately I don't use G+ (or facebook or in fact any other so-called social network). I will try to be active here so we can achieve the desired ANT+ support.
Tomorrow I will have a look at the ANT+ files you compiled (posted in the other thread) and I will compare the results with the ones provided by samsung (which I somehow managed to installed but don't really know if are working or not). I will add a post with the steps I followed to make it work.
AdrienC said:
Guys, I've got a message from @fcastillousfq and I think it might be of your interest my response:
Sure, it the Suunto Movestick Mini + OTG Cable
Then you have to install:
https://play.google.com/store/apps/details?id=com.dsi.ant.usbservice
https://play.google.com/store/apps/details?id=com.dsi.ant.service.socket
https://play.google.com/store/apps/details?id=com.dsi.ant.plugins.antplus
https://play.google.com/store/apps/details?id=com.dsi.ant.antplusdemo (for testing)
https://play.google.com/store/apps/details?id=com.dsi.ant.antplus.grapher.heartrate (for testing)
And you're set. It's pretty easy!!
ps: forget to mention that you can use regular size ant+ usb sticks, as the one from Garmin, but I preferred this one as it's smaller.
With a bit of DIY you can make something smaller.
Click to expand...
Click to collapse
I also have the LARGE garmin usb stick. I successfully used it with the Razr (910xt), but if only we could make use of the internal ANT+ hardware it would be soooo convinient
usu4rio
PS. As a "last resort" I'm planning to contact Carlo Pescio, the creator of Sportablet (http://www.sportablet.com). If I were able to use the internal ANT+, I would definitively buy his software (https://play.google.com/store/apps/details?id=com.carlopescio.uploader). I hope this doesn't sound as extortion ... too much :angel:
So being very new to Glass (only got it on Wednesday 25/06) it is my understanding that the firmware after 16 disabled the 'normal' control via the touched? So versions after this are only capable of back and scroll?
Is there anyway of configuring a program like Remodriod or Tablet Remote so you can use the controls from your phone on Glass? Might sound silly as you could just say use your phone for what your doing but I was more thinking of using it to control the likes of YouTube so I log in and obtain my play lists, also it would stop the need to plug in for control via ADB, for which as a newbie to ADB I'm struggling with commands.
I was playing around with Remodriod and it asked me to set the input in Language and input, for which it didn't pop up like it did on my phone, I assume it is because there is no native option for this on Glass and therefore couldn't obtain the screen for it? Would I need to install the language and input options? Of so where can I get it from?
Has anyone else tried this idea?
Regards
Giles
GiGoVX said:
So being very new to Glass (only got it on Wednesday 25/06) it is my understanding that the firmware after 16 disabled the 'normal' control via the touched? So versions after this are only capable of back and scroll?
Is there anyway of configuring a program like Remodriod or Tablet Remote so you can use the controls from your phone on Glass? Might sound silly as you could just say use your phone for what your doing but I was more thinking of using it to control the likes of YouTube so I log in and obtain my play lists, also it would stop the need to plug in for control via ADB, for which as a newbie to ADB I'm struggling with commands.
I was playing around with Remodriod and it asked me to set the input in Language and input, for which it didn't pop up like it did on my phone, I assume it is because there is no native option for this on Glass and therefore couldn't obtain the screen for it? Would I need to install the language and input options? Of so where can I get it from?
Has anyone else tried this idea?
Regards
Giles
Click to expand...
Click to collapse
I'm glad you've done your research, it gets old telling people the same things over and over again.
As you mentioned, there was a time where you could easily control most apps with the touchpad, but that functionality has since been removed. Besides, there was no way to enter text without some sort of remote; many people managed to use bluetooth keyboards to achieve this, and the combination worked quite well.
In XE16, Google apparently decided that they wanted to make a clear distinction between Glass and Android controls. Apps that don't implement the Glass-specific gesture listeners can't be controlled at all. Even native Android popup windows don't allow you to choose which button you want to select (even if the Languages and Input popup did show up on Glass, you couldn't select the button).
So here we are today, either using the stripped-down, masked version of Android that Google gives us, or fumbling with ADB commands attempting to get that one video on YouTube to play. But there is hope yet. Google gives us rooted boot images, presumably hoping that we will show them something that they haven't done themselves. This tiny 5.5MB file opens up a ton of possibilities, but someone needs to be the middle man that brings these possibilities to the masses.
Thanks to the beauty of open source, we have a clear model of what needs to be done for Glass to work like so many people wish it would.
Port a working recovery image to flash zips to the Glass system folder (Done)
Modify Superuser to function properly given Glass's limited control set
Modify XposedInstaller in the same manner
I have a proof-of-concept Xposed module for Glass that lets me control the Netflix app with the touchpad. It's dirty, and it takes a lot of work to get working, but the concept is solid. Xposed is an incredibly powerful utility. The end goal is to create a Glass-oriented keyboard (think oldschool arcade video game high score screens - "Enter Your Initials").
While my goal is solid and my intentions are pure, I worry that there is a reason Google didn't do this to begin with.
TLDR; I'm working on it.
Many thanks for the response, so the short answer is no. That's a big shame and I hope I haven't just wasted 1k on a peice of eyewear that needs charging halfway thru the day!
I assume there is no way of going back to version 16?
I think it's strange how little development there is with Glass on XDA (I could be wrong but if you look at the likes of the smart watches there seems to be considerably more development) and how inactive this part of the forum seems? considering the idea and in my eyes (no pun intended) cool Glass is hence why I ordered mine as soon as I could here in the uk, so far I haven't met anyone with one, and I'm still getting some strange looks lol
The things that are possible with Glass are amazing. Really wish they had added a rear facing camera, eyes in the back of my head, no, but I can see behind me lol
I am eager to see your work and I will experiment on trying to build your xposed modules (never tried building an apk before) no harm in learning on what is probably the most expensive peice of tech I own lol
GiGoVX said:
Many thanks for the response, so the short answer is no. That's a big shame and I hope I haven't just wasted 1k on a peice of eyewear that needs charging halfway thru the day!
I assume there is no way of going back to version 16?
I think it's strange how little development there is with Glass on XDA (I could be wrong but if you look at the likes of the smart watches there seems to be considerably more development) and how inactive this part of the forum seems? considering the idea and in my eyes (no pun intended) cool Glass is hence why I ordered mine as soon as I could here in the uk, so far I haven't met anyone with one, and I'm still getting some strange looks lol
The things that are possible with Glass are amazing. Really wish they had added a rear facing camera, eyes in the back of my head, no, but I can see behind me lol
I am eager to see your work and I will experiment on trying to build your xposed modules (never tried building an apk before) no harm in learning on what is probably the most expensive peice of tech I own lol
Click to expand...
Click to collapse
I can't say I'm surprised by the lack of activity. Rooting Glass voids the warranty, and with the high price in addition to so many reported issues, not many people are willing to take that risk at the moment.
If you want to get touch controls back, then you'll need to flash down to XE12. See https://developers.google.com/glass/tools-downloads/system. Please be sure to read any warnings and notices. XE12 still doesn't have many options for keyboard input, but you'll have better luck than using XE16+.
Also, the strange looks won't be going away any time soon
jtxdriggers said:
I can't say I'm surprised by the lack of activity. Rooting Glass voids the warranty, and with the high price in addition to so many reported issues, not many people are willing to take that risk at the moment.
If you want to get touch controls back, then you'll need to flash down to XE12. See https://developers.google.com/glass/tools-downloads/system. Please be sure to read any warnings and notices. XE12 still doesn't have many options for keyboard input, but you'll have better luck than using XE16+.
Also, the strange looks won't be going away any time soon
Click to expand...
Click to collapse
The really frustrating thing with my Glass is that I'm still waiting for Google to get back to me about the 'split framed' version they should of sent me instead of the current standard version I have!
I requested a call from Google shortly after I received them asking the above question but they couldn't find my order, sure enough they have taken my money but can't find my order number, nor my Gmail address or the serial number for my Glass device! A little concerning that Google of all people couldn't find my info! I'm still waiting for an email back 3 days later! Longest Google search in history lol
i would like to write a replacement for active display on my victara handset. i have a fair amount of android development experience but no experience reverse-engineering an application. it seems motorola is not interested in opening up active display to the developer community, so i need some help! if you would like to assist me with the reverse-engineering portion of this project and have the requisite experience, please send me a message.
thanks.
symnem said:
i would like to write a replacement for active display on my victara handset. i have a fair amount of android development experience but no experience reverse-engineering an application. it seems motorola is not interested in opening up active display to the developer community, so i need some help! if you would like to assist me with the reverse-engineering portion of this project and have the requisite experience, please send me a message.
thanks.
Click to expand...
Click to collapse
You're right, they are not interested in opening up the toolbox for their proprietary software. That's why I said to each manufacturer apart from the other one. Android is open source but that's it.
What are you wanting to change?
matt99017d said:
You're right, they are not interested in opening up the toolbox for their proprietary software. That's why I said to each manufacturer apart from the other one. Android is open source but that's it.
What are you wanting to change?
Click to expand...
Click to collapse
99% of it. i don't like the font, i don't like the direction of the swipe to open (i want it to be consistent with lollipop's lock screen, which is swipe from the bottom up) there should be color, not just white (color is more energy efficient, anyway) there is no indication of current battery status, cell status, or wi-fi status. no notification count... so, basically, just about everything. i doubt it would be very difficult, but i would need access to the api for the hardware ir sensors, sleep-active screen renderer, and sleep-active digitizer.
I'd pay for something like that so I could finally root and flash a rom on my moto x2 without missing moto display
Hello XDA!
I was wondering if its possible to install and run the original Moto Display application on my device. My device is a Moto X 2014 (Pure Edition) running Cyanogenmod 14.1. I have tried alternatives such as DynamicNotifications, ACDisplay, and Cyanogenmod's own Ambient display, but none compared to how Moto Display feels. I've tried installing the application from the Play Store but once I open the "Display" portion of the Moto app, the app crashes and goes to the main screen. Any help at all would be appreciated. Thanks again and I look forward to my first XDA Thread.
Hi man!
I get that this is your first thread, but this has been discussed a million times. You'll never get Moto Display or Voice on any ROM that is not stock. They're closed source apps and there's nothing we can do about it, not even workarounds because the lads at Google are greedy bast*rds which have hijacked most of the features in Android, the most notable one being, guess what, voice control.
Flipz77 said:
Hi man!
I get that this is your first thread, but this has been discussed a million times. You'll never get Moto Display or Voice on any ROM that is not stock. They're closed source apps and there's nothing we can do about it, not even workarounds because the lads at Google are greedy bast*rds which have hijacked most of the features in Android, the most notable one being, guess what, voice control.
Click to expand...
Click to collapse
Thanks for your help. I am sad that its a close sourced app but I guess there's nothing I can do about it. Thanks you for assisting me in this matter.:good:
You're welcome I also used CM14 for some time until I realised that workarounds for Display weren't the same thing, that replicating Voice functionality was a lost cause, and that I needed some Xposed-related features for my job (such as disabling the proximity sensor).
I settled on stock 6.0 with N-ify and N Navbar, which do a pretty good job at making this phone feel up-to-date.
It's a setup I would suggest to anyone looking for a feature-minded compromise, even if multiwindow is absent and quick reply only works to a certain extent.
This thread is so more information about our fingerprint issue when building from source code can reach more devs and enable them to start off without having to research any and all the information that we already have.
The main goal is to share what each one of us knows so far and discuss what may work and won't work.
Share our ideas and thoughts on the subject.
First question is
how many of you still have these files in these locations after flashing source built rom?
system/vendor/lib64/hw/goodix.fingerprint.sdm845.so
system/vendor/lib/hw/goodix.fingerprint.sdm845.so
system/vendor/lib64/hw/goodix.fod.sdm845.so
system/vendor/lib/hw/goodix.fod.sdm845.so
system/vendor/lib/libgoodixfingerprintd_binder.so
system/vendor/lib64/libgoodixfingerprintd_binder.so
system/vendor/lib/[email protected]
system/vendor/lib64/[email protected]
lets start here.
Reserved
This one too
Maybe one more
I'm running the latest havoc, and these are the only fingerprint files I have
To understand the problem you have to understand how it works in the first place. The fingerprint sensor is actually working, so its not a blob issue. The issue(from what I am seeing at least) is that stock aosp source cannot differentiate between the fingerprint sensor touch vs the regular display touch. After digging through oneplus systemui you will notice that there is quite a few proprietary things in there pertaining to the touch system for fingerprint. All of which is missing from aosp source.
We currently have 2 options for getting FP working. Either OP releases the fingerprint source or someone reverse engineers the code from oneplus(like what was done with the slider).
EDIT: Since it will be asked anyway how i know its not a blob issue... If the fingerprint sensor was not working correctly Roms would not even have the fingerprint option available or it would crash on load.
me2151 said:
To understand the problem you have to understand how it works in the first place. The fingerprint sensor is actually working, so its not a blob issue. The issue(from what I am seeing at least) is that stock aosp source cannot differentiate between the fingerprint sensor touch vs the regular display touch. After digging through oneplus systemui you will notice that there is quite a few proprietary things in there pertaining to the touch system for fingerprint. All of which is missing from aosp source.
We currently have 2 options for getting FP working. Either OP releases the fingerprint source or someone reverse engineers the code from oneplus(like what was done with the slider).
EDIT: Since it will be asked anyway how i know its not a blob issue... If the fingerprint sensor was not working correctly Roms would not even have the fingerprint option available or it would crash on load.
Click to expand...
Click to collapse
Thanks for the input.
I believe we have a long road ahead but we have to start somewhere.
me2151 said:
To understand the problem you have to understand how it works in the first place. The fingerprint sensor is actually working, so its not a blob issue. The issue(from what I am seeing at least) is that stock aosp source cannot differentiate between the fingerprint sensor touch vs the regular display touch. After digging through oneplus systemui you will notice that there is quite a few proprietary things in there pertaining to the touch system for fingerprint. All of which is missing from aosp source.
We currently have 2 options for getting FP working. Either OP releases the fingerprint source or someone reverse engineers the code from oneplus(like what was done with the slider).
EDIT: Since it will be asked anyway how i know its not a blob issue... If the fingerprint sensor was not working correctly Roms would not even have the fingerprint option available or it would crash on load.
Click to expand...
Click to collapse
I'm in agreement on this. My LG G5 has a fingerprint sensor and when the battery was getting bloated it was actually lifting the power/fingerprint button off the connector. When it got bad enough the phone just stopped showing the option for the sensor because it no longer detected the presence so even if the files are there Android is smart enough to hide the option if it doesn't see a working sensor.
Yep. A lot of times when device bringup is being done if you haven't done fingerprint yet android will just not show the fingerprint options(in setup or in settings). Usually won't until it sees the fingerprint hardware actually working and connected.
me2151 said:
Yep. A lot of times when device bringup is being done if you haven't done fingerprint yet android will just not show the fingerprint options(in setup or in settings). Usually won't until it sees the fingerprint hardware actually working and connected.
Click to expand...
Click to collapse
Since you said something about the system Ui I decompiled it.
It looks like everything is in there even the green light.
twinnfamous said:
Since you said something about the system Ui I decompiled it.
It looks like everything is in there even the green light.
Click to expand...
Click to collapse
Yep. Even the code for the face unlock is in there.
me2151 said:
Yep. Even the code for the face unlock is in there.
Click to expand...
Click to collapse
So in a sense all it takes is someone capable enough to take the decompiled files and modify the system ui apk source code in the rom they are building?
I have the files if anybody needs them there on afh
me2151 said:
Yep. Even the code for the face unlock is in there.
Click to expand...
Click to collapse
So in a sense all it takes is someone capable enough to take the decompiled files and modify the system ui apk source code in the rom they are building?
I have the files if anybody needs them there on afh
twinnfamous said:
So in a sense all it takes is someone capable enough to take the decompiled files and modify the system ui apk source code in the rom they are building?
I have the files if anybody needs them there on afh
Click to expand...
Click to collapse
Yes and no. The main problem is the fact that the code is proprietary. If you release it as is or share it as is you could face legal action from one plus. It has to be completely rewritten. Hence the reverse engineering part. But the yes to it is it just needs someone capable.
few Devs have the code already ..
But unfortunately can't post a rom with fingerprint fix , cause is proprietary or get DMCA'd
So they're working on a fix that's open source to share it...
cultofluna said:
few Devs have the code already ..
But unfortunately can't post a rom with fingerprint fix , cause is proprietary or get DMCA'd
So they're working on a fix that's open source to share it...
Click to expand...
Click to collapse
Did any dev even got the fingerprint to work?
Electric1447 said:
Did any dev even got the fingerprint to work?
Click to expand...
Click to collapse
Not yet
cultofluna said:
few Devs have the code already ..
But unfortunately can't post a rom with fingerprint fix , cause is proprietary or get DMCA'd
So they're working on a fix that's open source to share it...
Click to expand...
Click to collapse
Systemui in source built roms have fingerprint files in them. May be easier if someone running a open-source rom pulls the apk and decompiles it then edit and put back in device to test? Just a thought but I've been going through everything the only thing I seen so far we need to add is the fingerprint location values and add files to show on screen.
We shouldn't have to rewrite completely as most files are all ready open source and in systemui of aosp source code.
I've been caught up in building a source code rom and trying things but there are far more people that have more experience than I do at the .apk part.
Hope any of this helps.
twinnfamous said:
Systemui in source built roms have fingerprint files in them. May be easier if someone running a open-source rom pulls the apk and decompiles it then edit and put back in device to test? Just a thought but I've been going through everything the only thing I seen so far we need to add is the fingerprint location values and add files to show on screen.
We shouldn't have to rewrite completely as most files are all ready open source and in systemui of aosp source code.
I've been caught up in building a source code rom and trying things but there are far more people that have more experience than I do at the .apk part.
Hope any of this helps.
Click to expand...
Click to collapse
This what I thought someone should do. Even if someone uses copyrighted code he could still test and see if it works.
I want to continue research on this topic. I'll take a look at systemui and framework-res and try to just test if I can get OP code working on AOSP. Then I'll go from there.
Edit: From a quick glance, FP code seems to be also present in framework-res, so that likely will also need to be worked on.