Simple module to make Android Auto less restrictive. History on this module can be found here and an article about the in-motion tap limits here. This module should remove the "speed bump" notification (Browsing locked for safety) and allow you to scroll through lists (playlists, song lists, etc) without hindrance.
There's also a reddit thread/request which has more specifics about what this module is trying to accomplish.
Features:
Should work for all aftermarket AA-capable headunits (might require a hard-wired bypass module depending on model)
Should also work for most OEM AA headunits that are built into newer vehicles
Should also work for standalone AA running on a phone and not connected to a headunit
Here comes the really large and obnoxious disclaimer.......
This module can alter the built-in safety features that Google has implemented in Android Auto. By downloading and installing, you agree that YOU, and only YOU, are solely responsible for any negative repercussions that may result. This can include injury to yourself and/or others, property damage, or loss of life. Under no circumstances is the author of this module responsible for its use!
...not that a simple disclaimer on a forum post would go far if anything were to happen, but I felt the need to put it out there. Please use YOUR best judgement when it comes to operating a vehicle and futzing with your Android Auto headunit.
Development and testing was done on a Nexus 5x running Android Auto v1.6.240040 (2719917-release) and a Pioneer AVH-4200NEX w/ micro bypass. This should work on any Lollipop and newer rom, assuming Android Auto works on it.
Downloads
See attached files on this post.
You can also grab it from the Xposed Repo
XDA:DevDB Information
Sensible Android Auto:Xposed , Xposed for all devices (see above for details)
Contributors
agentdr8
Source Code: Gitlab
Xposed Package Name: com.dr8.xposed.saax
Version Information
Status: Stable
Current Stable Version: 6.3.611314
Stable Release Date: 2021-04-12
Created 2016-06-04
Last Updated 2021-04-12
Reserved
In case it isn't already clear, this APK is a module designed to be used with the Xposed Framework. It will do absolutely nothing on its own.
Changelog
v6.3.611314 - Updated for Android Auto 6.3.611314
v6.1.610544 - Updated for Android Auto 6.1.610544
v5.8.604354 - Updated for Android Auto 5.8.604354
v5.7.603964 - Updated for Android Auto 5.7.603964
v5.7.603954 - Updated for Android Auto 5.7.603954
v5.6.603444 - Updated for Android Auto 5.6.603444
v5.6.603434 - Updated for Android Auto 5.6.603434
v5.5.602944 - Updated for Android Auto 5.5.602944
v5.5.602934 - Updated for Android Auto 5.5.602934
v5.4.502264 - Updated for Android Auto 5.4.502264
v5.3.501644 - Updated for Android Auto 5.3.501644
v5.3.501634a - Updated for Android Auto 5.3.501634 (fixed negative value)
v5.2.501054 - Updated for Android Auto 5.2.501054
v5.1.500644 - Updated for Android Auto 5.1.500644
v5.0.500214 - Updated for Android Auto 5.0.500214
v4.9.594934 - Updated for Android Auto 4.9.594934
v4.8.594324 - Updated for Android Auto 4.8.594324
v4.7.593824 - Updated for Android Auto 4.7.593824
v4.7.593814 - Updated for Android Auto 4.7.593814
v4.6.593334 - Updated for Android Auto 4.6.593334
v4.6.593324 - Updated for Android Auto 4.6.593324 and 4.6.59xxxx (for 32-bit)
v4.5.592854 - Updated for Android Auto 4.5.592854 and 4.5.592xxx (for 32-bit)
v4.4.592344 - Updated for Android Auto 4.4.592343 and 4.4.592344
v4.3.591854 - Updated for Android Auto 4.3.591843 and 4.3.591854
v4.2.591444 - Updated for Android Auto 4.2.591444 - Versioning has now been changed to mimic the AA versions so that it is clear which version of SAAX works with which version of AA
v1.9.3.2 - Updated for Android Auto 4.2.591xxx
v1.9.2 - Updated for Android Auto 4.2.591xxx
v1.9.1 - Updated for Android Auto 4.1.590xxx
v1.9.0 - Updated for Android Auto 4.0.590xxx
v1.8.9 - Updated for Android Auto 3.9.585xxx
v1.8.8 - Updated for Android Auto 3.8.584xxx
v1.8.7 - Updated for Android Auto 3.7.584xxx
v1.8.6 - Cleaned up debug logging and bumped version
v1.8.5c - With @xs1337's help, added overrides to CarSensorEvent classes which should help those with OEM headunits
v1.8.5a - Fixed typo in method name which was throwing exceptions
v1.8.4 - Updated for Android Auto 3.6.583xxx
v1.8.3 - Updated for Android Auto 3.5.583xxx
v1.8.2 - Added another overridden method to try and bypass warnings, cleaned up comments
v1.8.1 - Added more overridden methods to try and bypass warnings
v1.8.0 - Updated for Android Auto 3.4.582xxx
v1.7.8 - Updated for Android Auto 2.9.574xxx -- missed a method name change
v1.7.7 - Updated for Android Auto 2.9.574xxx
v1.7.6 - Updated for Android Auto 2.8.57451x
v1.7.5a - Missed a method name change
v1.7.5 - Updated for Android Auto 2.7.57395x
v1.7.4 - Updated for Android Auto 2.6.57340x -- added additional options to hopefully override vehicle sensors
v1.7.3 - Updated for Android Auto 2.5.72860x
v1.7.2 - Updated for Android Auto 2.4.72280x
v1.7.1 - Add additional parameter override to get rid of "Paused for your safety" messages
v1.7 - Updated to support the latest Android Auto (2.3.716603-release)
v1.6 - Updated to support the latest Android Auto (2.2.710803-release)
v1.4a - Updated to support latest Android Auto (2.0.642303-release)
v1.3 - Added preference for how many pages are shown in list views
v1.2 - Unreleased, but work done to address built-in vehicle sensors
v1.1 - Updated method hook to include an additional setting, and properly calculate meters/sec from MPH. Also fix initial TypeError crash upon first launch
v1.0 - Initial release
What does this mod do?
"Make Android Auto less restrictive" is very vague, and the history thread is disorganized. Can you add a feature list?
Livingod said:
What does this mod do?
"Make Android Auto less restrictive" is very vague, and the history thread is disorganized. Can you add a feature list?
Click to expand...
Click to collapse
Sorry about that. I've added a few lines about what it does to the OP.
Hi great work so far! Where can I download it?
ahaan said:
Hi great work so far! Where can I download it?
Click to expand...
Click to collapse
In Xposed [emoji12]
☆☆☆ ☆☆☆
amazing, exactly what I have been looking for.
Installed on a Sprint Galaxy S5 with blisspop rom. Will give it a run tomorrow and report back. I just set the number of taps to 999.
ahaan said:
Hi great work so far! Where can I download it?
Click to expand...
Click to collapse
That's odd. When I edit the first post, I can see that the APK is attached. But it isn't showing up. It's probably something to do with the DevDB project.
I've added it to the Downloads tab up top though. And I'll put the xposed repo link on the OP.
Works great! thank you for this. This is highly needed and worked with out a hitch for me on a quick test of spotify (was on a quick drive and was unable to test everything)
agentdr8 said:
That's odd. When I edit the first post, I can see that the APK is attached. But it isn't showing up. It's probably something to do with the DevDB project.
I've added it to the Downloads tab up top though. And I'll put the xposed repo link on the OP.
Click to expand...
Click to collapse
Looks great now, downloaded and tested successfully with the Head unit hack using self mode! Great experience
update on my test, works great on my Sprint Galaxy S5 with blisspop 6.0 rom with the pioneer 4100nex. The first time I tried, AA seemed to have froze when I tapped Spotify, removed the usb and replugged it back in, but the module didnt seem to work, it only allowed 6 taps. On my 2nd drive, it worked great scrolling through my entire playlist when I was in movement
Thank you!! Works great on my Droid Turbo with CM13, Pioneer 4200 NEX.
First time I started AA it froze and crashed with "cannot connect to AA at the moment, when safe please disconnect and check your phone." All I did was disconnect and plug it back in, and it's been great ever since.
ranova said:
The first time I tried, AA seemed to have froze when I tapped Spotify, removed the usb and replugged it back in
Click to expand...
Click to collapse
Jeffy! said:
First time I started AA it froze and crashed with "cannot connect to AA at the moment, when safe please disconnect and check your phone." All I did was disconnect and plug it back in, and it's been great ever since.
Click to expand...
Click to collapse
Interesting. If it continues to happen, please enable debug in the settings and provide the Xposed Installer logs + logcat so I can account for this behavior.
agentdr8 said:
Interesting. If it continues to happen, please enable debug in the settings and provide the Xposed Installer logs + logcat so I can account for this behavior.
Click to expand...
Click to collapse
I've used it about 10 times since then, running errands and whatnot. It's been working perfectly for me, no glitches!
agentdr8 said:
Interesting. If it continues to happen, please enable debug in the settings and provide the Xposed Installer logs + logcat so I can account for this behavior.
Click to expand...
Click to collapse
Jeffy! said:
I've used it about 10 times since then, running errands and whatnot. It's been working perfectly for me, no glitches!
Click to expand...
Click to collapse
yup, only happened to me the first time after installing the module. Its been working ever since. Thanks again!
This is fantastic! Great job. Let's hope you will be able to add more features in the future or that other developers will join you. I love Android Auto but the current restrictions (on which apps can be used for example) are just plain stupid. I understand that there are people who would abuse Android Auto to type entire messages while driving if it was possible but that is not the responsibility of Google. At least, it wouldn't be the responsibility of Google in Europe. It's a totally different story in the US of course
Updated the module today. I figured out that the values for "unlimited browsing speed" and "max speed parking card" were in meters per second (float), so the default of 0.5F is roughly 1.1 MPH. I've made an adjustment so the preference slider accurately represents MPH at which it will no longer allow for unlimited browsing.
Of course if you have the tap limit set to max, then it won't matter. But a sensible tap limit, combined with a sensible max unlimited browsing speed is now achievable.
I also addressed the crash at initial launch.
Hi agentdr8,
Great Module! Congratulations!
One suggestion: Please, can you add the option of "Execute action in the CAR screen"? The idea is: add one entry in this "unused" menu for trigger a Broadcast Intent; this intent then will be captured and processed by another App (like Tasker, AutomateIt, Llama, etc.)
Here some guide about "Broadcast Intent": http://inchoo.net/dev-talk/android-development/broadcast-receiver-from-activity/
For the "Car Screen" see: http://arstechnica.com/cars/2015/07...icle-diagnostic-app-expanded-car-integration/
I hope you agree! :fingers-crossed:
manos78 said:
Hi agentdr8,
Great Module! Congratulations!
One suggestion: Please, can you add the option of "Execute action in the CAR screen"? The idea is: add one entry in this "unused" menu for trigger a Broadcast Intent; this intent then will be captured and processed by another App (like Tasker, AutomateIt, Llama, etc.)
Here some guide about "Broadcast Intent": http://inchoo.net/dev-talk/android-development/broadcast-receiver-from-activity/
For the "Car Screen" see: http://arstechnica.com/cars/2015/07...icle-diagnostic-app-expanded-car-integration/
I hope you agree! :fingers-crossed:
Click to expand...
Click to collapse
I'll see what can be done about adding some things to that screen. I'm not positive, but I believe most apps won't be able to display any activities on that screen unless they have specific Android Auto layouts. But firing off a configurable intent should be possible.
Stay tuned....
EDIT: Upon further investigation, it seems that this isn't doable right now. Those entries under the "Car" screen are services that have to be defined in the manifest. AFAIK, you can't inject service entries (and their associated metadata tags) into an app via Xposed. I think at some point, Google may open up that restriction for OEMs, and allow them to just apply a specific xml description tag to indicate that a particular app can be shown/used in that screen.
I can try and see if I can hook the layout inflation of those entries, and modify their titles there. I can also try and override what they currently launch (right now, just demo screens).
agentdr8 said:
EDIT: Upon further investigation, it seems that this isn't doable right now. Those entries under the "Car" screen are services that have to be defined in the manifest. AFAIK, you can't inject service entries (and their associated metadata tags) into an app via Xposed. I think at some point, Google may open up that restriction for OEMs, and allow them to just apply a specific xml description tag to indicate that a particular app can be shown/used in that screen.
I can try and see if I can hook the layout inflation of those entries, and modify their titles there. I can also try and override what they currently launch (right now, just demo screens).
Click to expand...
Click to collapse
Hi agentdr8,
Thank you for your efforts! Good work! :good:
In reference to the limitations: Then I suggest to just hook the button for selecting the CAR screen. I feel this can be possible, and we use this event to trigger some intent. Please, think that sending one intent is by far more simple that printing on the screen. So, perhaps the first goal can be hook the AA UI for sending events to other Apps. You agree?
Related
WMDreamRemote (WMDR) - with streaming
UPDATE (22/04/2012): No more deadlines. The reason is that I am busy with other projects. I might implement other features in future. You can download from my web-site, http://www.tillekesoft.com. There you can find as usual two versions. One version is for devices using 320x240 but it should work fine also with devices having a resolution of 640x480. For all other resolutions, please use the other one. For existing users, you just need to replace the old executable with the new one.
06/10/2010 - I have attached a "step-by-step"-guide for setting up WMDR - in particular what regards streaming (it is in English but you can use Google Translation-tools to translate it to another language). Hopefully, this will make it easier for new users to get WMDR working.
IMPORTANT (22/06/2010) - I just tested the new version of VLC no. 1.1.0 and it seems like WMDR is not compatibile with the latest version of VLC. So if you want to use WMDR, please ensure to use VLC 1.0.5 or earlier until I have resolved this issue.
Change-log: nothing so I am leaving old change-log here below:
This version is more like a Service-Release fixing some bugs and introducing few new features:
-fixed issue when using WMDR with Enigma2 outside your LocalLAN where WMDR passed on a DynDNS-address to the Dreambox instead of LocalIP-address which is the correct way. Thanks to mkbm for finding this bug.
-fixed streaming-issue in Enigma2 when changing between channels located on different transpoders would cause problems. Thanks to mkbm for explaining this.
-improved error-handling (clearer messages). Still to be improved further.
-possibility to kill stream when exiting WMDR
-other minor bug-fixes
-some optimization
-added a program-icon (it's very basic - if you can come up with a better-looking icon, please do so and post it here in the thread)
-fixed issue with DM8000
To see WMDR in action (using a pre-release of Beta 0.7), watch this video posted by XDA-user ajocius on YouTube:
Background: After on-going discussions in this thread http://forum.xda-developers.com/showthread.php?t=616353 regarding an application to control remotely the Dreambox, I decided to write an application to accomplish this request.
In above thread, a very simple and crude beta-application was posted. Now, the application has evolved further and therefore I reckoned it was more appropriate to open a new thread in this area which is meant for Window Mobile applications.
Extra Information: The Dreambox is a series of Linux-powered DVB satellite, terrestrial and cable digital television receivers (set-top box), produced by German multimedia vendor Dream Multimedia. It's "kind of" of open-source which has led many "teams" to develop so called "images" for this receiver as an alternative to the original one furnished by Dream Multimedia. In addition, many other hardware manufactures have produced their own receivers (some of them are actually clones while others are not) using the same concept of the Dreambox i.e. Linux-powered. The Dreambox has evolved during the years and many models are present on the market. The first ones are/were using a firmware called "Enigma" but, more or less, with the introduction of High Definition TV, a new firmware was released, namely "Enigma2". One of the "revolutionary" features of the Dreambox was that you can connect it to your local network and this opened up a whole new word compared to ordinary satellite-receivers. To get further information, just google for Dreambox or look it up at Wikipedia.
Background for the application: You can read the original thread mentioned above to get an idea why people wanted an application like the one I am releasing. In a few words: since you can access the Dreambox (or any other satellite-receiver based on Enigma or Enigma2) through your local network or through Internet, there are many things you can do remotely (at work for instance) such as handling timer-events, read EPG etc. The ideal way of doing it, especially if you don't have access to a PC, is to use a handheld device. It was brought to our attention, that there are plenty of applications to do what mentioned above already available for download on the Appstore for iPhone.
for instance:
http://appspace.com/apps/view/38502/idreamremote/
http://appspace.com/apps/view/40338/dreamon/
So, it was suggested to write a similar application for Windows Mobile. And here it is, still in beta although with quite a lot of features implemented, even Streaming-support.
Current Features:
-Streaming
-Remote Control
-Bouquets-/Channels-lists from where you can:
1) change channel
2) view EPG
3) set timers
-Controlling the receiver (Shutdown, Reboot etc)
-Supports set-up of multiple profiles (e.g. At work, home, bedroom)
-Supports set-up of multiple streaming-profiles (Local LAN, WLAN, mobile)
Known issues:
-is not compatible yet with old WebIf (1st generation) of Enigma2
-there might be some problems with certain characters not appearing correctly (please report if you have this problem)
-in 320x240 version when setting up Enigma-profiles, you might need to click twice in the various textboxes.
Features to implement in upcoming versions (not necessarily in this order):
- SMS (Send shortmessages to the TV-Screen)
- improve error handling further
- other ideas/stuff
- user-suggestions (your feedback for improvements)
- re-design the remote-control using png-images instead of jpg which should make the application a bit smaller (and require less memory)
- resolving above mentioned issues
- other bug-fixes
- support for other receivers - requests I have received are for D-box2 and IPBox HD (non Enigma)
- cosmetic issues
- Https (SSL) support. (tested and working but needs a specific hotfix-version of CF.NET (published by Microsoft) due to a bug in CF.NET)
Requirements:
-Compact Net Framework (2.0 should be sufficient)
-an Enigma-based receiver such as the Dreambox, IPBox etc..
-for streaming, please see second post below
Installation:
Note: I have not made any CAB-file.
Note2: If you want to keep your old settings and streaming-profiles, you may do so. Just replace the old WMDreamRemote.exe with the new one.
1) download the zip-file attached to this post and extract the files on your computer.
2) Copy the files into a directory of your choice on your device (internal or
storage). The files must be in the same directory.
3) Run WMDreamRemote.exe. The first time, you will get a message
saying "No connection....".
4) Choose Preferences/Profiles from the main-screen and ADD a new
profile inserting your data. Put the flag on default for the profile you use the most.
5) Then click Save Profile.
6) Go ahead if you wish to add other profiles.
7) You may delete my dummy-profile "home" (only after having added your own though) using
the Del-button. NOTE: It's important that there is always one profile present (with Default selected)
otherwise there might be unexpected errors
8) On the main-screen, you can now use the remote-control by selecting its button
9) You may also see a bouquet/channel list by clicking on its button. However, the first time the list will be empty. Therefore,
10). Go back to Preferences/Profiles and select the profile you want to use. Now select the
button named "Create Bouquets for this profile". This will take a minute or two. It will download
your bouquets and channels from your Dreambox. Do the same for each Profile you create.
11) Now you can scroll your bouquets ad channels.
12) Set up streaming-profiles (3 dummy profiles are provided for Local-LAN, WLAN and mobile) - see second post for more information
There might be some unhandled error-messages occasionally. They are mostly due to connection-problems. Just click on continue and retry unless you have indeed a permanent error with your connection.
Please test it and let me have your error-reports, feedback and suggestions for improvements. Please also indicate which device, Dreambox (or similar receiver) you are using and which image.
I must also express my sincerest thanks to XDA-user ajocius for:
-giving me access to Enigma2,
-his superb beta-testing,
-sharing his knowledge about streaming
-and of course for the great video he posted on YouTube (see above).
I have also attached some screenshots.
PS: ANDROID - Just a note to tell you that I posted here on XDA an Android-application for watching your Dreambox in streaming (LocalLAN and 3G). I called the application AndroidDreamer and you can find the thread here: http://forum.xda-developers.com/showthread.php?t=861145
If you want to test and discuss AndroidDreamer, head over to the thread. Please keep this thread for WMDR.
PS2: WINDOWS - I have published a Windows-version (WinDreamRemote or simply WinDR). You can find it on my web-site: http://www.tillekesoft.com
For discussions regarding WinDR, please use the thread mentioned on my web-site. This thread here at XDA is for WMDR - mobile version. Please respect this.
This is it for the time being.
STREAMING
Streaming works great for me, especially at home (in my Local LAN) but also at work (using WIFI) and even at the supermarket using a mobile-connection (3G) although the quality degrades.
For you, I don't know - Streaming may work, may work so and so or may not work at all.
It depends on a lot of factors:
-For Local-LAN: your WIFI set-up at home (11g, 54g etc)
-For WLAN or mobile: upload/download speed of your Broadband (normally upload-speeds are slower than download-speeds (ADSL)
-Your device
-Your computer acting as VLC-server
-not finding the right configuration in stream-profiles settings
-etc
What you need:
1) VLC (Videolan). Just Google for it and install it on your computer which will act as the VLC-server. I have only tested streaming using VLC running on Windows but it should work on VLC-servers using Linux and MAC as well. If it doesn't, please let me know. I have only tested version 1.0.5 of VLC so I am unable to say if previous versions will work.
UPDATE (22/06/2010) - I just tested the new version of VLC no. 1.1.0 and it seems like WinDR is not compatibile with the latest version of VLC. So if you want to use WinDR, please ensure to use VLC 1.0.5 or earlier until I have resolved this issue.
2) TCPMP (free and which you can find here on XDA) or Coreplayer (not free). Make sure that ASX-files are opened by the program you installed (look in the programs' settings for file-association). Some say that TCPMP is faster to load the stream (5-6 seconds in my Local-LAN) than Coreplayer. On the other hand, some say that Coreplayer is more fluid. The choice is yours.
3) A rather modern and fast device. It might work with slower devices as well but you may have to play a lot with your VLC-configuration (bitrate etc) before you get it to work
4) and of course WMDR
How to set up everything:
1) install VLC on your computer which will act as the VLC (streaming) -server. Then under the menu, select "View" in the English version (not sure since I have it in Italian) and then select "Add Interface" and finally you select "Add Telnet-interface". If you haven't changed anything, the default password for Telnet is admin and the port in use is 4212. That's it. VLC must be running to get streaming working. There are options to install VLC as a Windows Service or you can create a bat-file to be executed upon launch of your VLC-server. I guess similar options are availabe on Linux and MAC as well.
2) if you are going to use streaming outside your Local-LAN, you must ensure that you have set up port-forwarding correctly in your router. You must ensure that the WebIf can be accessed. You must ensure also that port 4212 (for Telnet) is opened and forwarded to the VLC-server. The same goes also for the streaming-port on the VLC-server which TCPMP/Coreplayer needs to access to receive the stream. So, basically you need to set up port-forwarding for one port for accessing the WebIf of your Dreambox and two ports for accessing your VLC-server.
3) A typical VLC-command to get streaming going is as follows:
Code:
vlc.exe" -vvv [url]http://192.168.1.130:31339/0,0025,0384,0385,0295[/url] --sout #transcode{vcodec=MP4V,vb=384,scale=0,5,acodec=mp3,ab=64,channels=1,deinterlace}:Duplicate{dst=std{access=HTTP,mux=ASF,dst=192.168.1.12:8085}}
Here are some explanations:
- the part "vlc.exe" is handled by WMDR using Telnet. You don't need to anything except for filling in information regarding the IP-address of your VLC-server, its password and which port to use.
- the part
Code:
"http://192.168.1.130:31339/0,0025,0384,0385,0295"
is your dreambox-ip, the port used for streaming and some channel-parameters. These parameters are handled automatically by WMDR and do not require your attention
- the part
Code:
"#transcode{vcodec=MP4V,vb=384,scale=0,5,acodec=mp3,ab=64,channels=1,deinterlace}:Duplicate{dst=std{access=HTTP,mux=ASF,dst="
is the one you have to insert in WMDR and which you need to experiment with to get the best picture/quality/fluidity according to your connection-speed. WMDR is pre-installed with 3 examples which are working on my HD2, my WIFI (using 54g) and my ADSL with an upload speed of 512kb. You can use those as an example and then modify them according to your needs.
- the part "192.168.1.12:8085" is the IP of your VLC-server and the port which TCPMP/Coreplayer should connect to in order to get the stream. You fill in this information in the stream-profiles.
With this information, you can set up your streaming-profiles in WMDR. In the streaming-profiles, you will find an additional setting called "VLC Sleep Delay". You can leave it at 200ms as its default-value. This parameter is used by WMDR when "talking to" VLC via Telnet. If the connection is very slow, you can increase this value but normally, even on Mobile-connections, the value of 200ms is OK.
Above information should get you going.
If you have problems with streaming, look at the points mentioned above since it is unlikely due to WMDR itself and that I can do anything to resolve your problems.
Good luck!
TIPS AND TRICKS:
-To make TCPMP open up automatically in full screen mode, you can do the following registry-edit:
Code:
HKEY_LOCAL_MACHINE\Software\TCPMP\PLAY
DWORD 123
Change value from 0 to 1
-For associating the file-extension ASX with TCPMP, do as follows: In TCPMP it is under:
Options -> Settings (you need to scroll down to see that option) - > Click button "Select Page" - > File Associacions
Click to expand...
Click to collapse
-As far as I have understood, TCPMP has been discontinued but there are some people updating it from time to time. If you have problems viewing the stream, it may (perhaps) be because you are using an old version of TCPMP. Here are two links to TCPMP which I have found working on my HD2:
http://forum.xda-developers.com/showpost.php?p=5657963&postcount=1
http://forum.xda-developers.com/showpost.php?p=5685536&postcount=1
TROUBLESHOOTING
- If you get errors in TCPMP (unknown file format, crashes) or if you don't see anything at all, you can try the following to trace where the error originates:
Select Stream in WMDR and if you get an error message from TCPMP, just disregard the error and put your device on the table or wherever. Don't click on anything. Don't kill the stream. Now, in the folder of WMDR on the device, you should find a file called WMDR.asx. Copy this file to your desktop (on a PC). Go to your PC and right-click on WMDR.asx and choose "open with" and select VLC (it will open another session of VLC). If you now can see the stream from your Dreambox on your computer-screen, then it means that WMDR comunicates correctly with VLC and most likely there is a problem with TCPMP/Coreplayer or because the file is too large/complex to be seen on the device. If you don't see anything, then probably there is a communication-problem between WMDR and VLC. Check IP-address, Port and Password of VLC.
- Make sure that streaming actually works between your Dreambox and VLC (without using WMDR) and that you can watch the streams on your computer. You can test this by using the web-interface of your Dreambox or you can search internet for instructions. If you have problems (can't see anything at all, bad quality, buffering-problems etc), then the problem itself lies with the source and there is no way streaming will work in a satisfying way. For instance, it has been reported that cheap (clones of) DM500 might have problems with streaming.
is this like a remote control app for any settop boxes and tv's that uses ir port or is it limited to the Dreambox?
Sorry - it's not using an ir port.
The application controls the receiver through the receiver's web-interface or through telnet.
However, the application could probably be used with (and modified to support) other types of receivers as long as there is a way to communicate with the receiver via local network, wifi, data-connections or Internet. If anyone is interested, please let me know.
trickbiker121 said:
is this like a remote control app for any setop boxes and tv's that uses ir port or is it limited to the Dreambox?
Click to expand...
Click to collapse
tilleke said:
Sorry - it's not using an ir port.
The application controls the receiver through the receiver's web-interface or through telnet.
However, the application could probably be used with (and modified to support) other types of receivers as long as there is a way to communicate with the receiver via local network, wifi, data-connections or Internet. If anyone is interested, please let me know.
Click to expand...
Click to collapse
sorry this isnt the app that i thought it was sorry to bother you
Hi Tilleke
Very nice looking release. I'm really happy with it!
i have tested it and here are my results:
Main screen > remote controle > page 2 > the numbers are not working here.
Main screen > preferences > Create bouguets > This option crashed my dreambox with a blue screen like windows always do...
Remember this is NOT a comment, this is only to help you with this great app!
Great Job, keep going... and i will be waiting till next release.
Thanks for testing and posting your results.
Can you please let me know which receiver you have and which image you are running. And on which device did you test it?
Will check this better.
citychannel said:
Main screen > remote controle > page 2 > the numbers are not working here..
Click to expand...
Click to collapse
When creating the bouquets, did you follow the procedure written in the first post? I am saying this since that part is not fool-proof yet. Did you reach the point when a message appears indicating "Update ready" or did it crash before. BTW: I have never seen a crashed dreambox with a blue screen I'd love to able to reproduce that error
citychannel said:
Main screen > preferences > Create bouguets > This option crashed my dreambox with a blue screen like windows always do.....
Click to expand...
Click to collapse
Thanks!!
citychannel said:
Remember this is NOT a comment, this is only to help you with this great app!
Great Job, keep going... and i will be waiting till next release.
Click to expand...
Click to collapse
Hi there
1) I have a dreambox 7025 with enigma on it
2) i didn't saw ' update ready' the DM crashed 4 seonds after i pressed the 'Create Bouquets for this profile'
A new 'bug' i found is the time out bug. This error appears randomly after zapping between channels or using the volume buttons.
Good luck and thanks!
thanks for your report.
1) OK, you've got DM7025 and running Enigma(1). Are you using the original image or have you flashed another image such as Gemini, Nabilo...If yes, which one?
2) Can you access the WebIf of the DM7025 using your local network and using a normal web-browser? In your browser, you should use:
Code:
http://ip-address of DM7025:port
it should then ask you for a user-name and password, normally root and dreambox.
example:
Code:
http://192.168.0.83:8888
If you are using the standard port (80), it could also be:
Code:
http://192.168.0.83
When you are connected to the WebIf and clicking on ZAP, can you see your bouquets and channels?
3) The time-out bug: What message do you get. Can you please transcribe it? Does this happen when you are connected using WIFI or when you are connected using the data-connection of your phone-provider?
4) what device are you using?
Sorry, but I need above information otherwise I really don't see how to track down the errors you mentioned since I can't reproduce them on my system/device.
PS: I confirm that the numbers on the 2nd screen don't work. I forgot to enable a few lines in my code. Will be corrected in next version. Thanks for finding out.
citychannel said:
Hi there
1) I have a dreambox 7025 with enigma on it
2) i didn't saw ' update ready' the DM crashed 4 seonds after i pressed the 'Create Bouquets for this profile'
A new 'bug' i found is the time out bug. This error appears randomly after zapping between channels or using the volume buttons.
Good luck and thanks!
Click to expand...
Click to collapse
Hi, working on my hd2 with dreambox 7000 S (gemini 4.6).
But one issue: The programm can´t display the german letters ä, ö and ü (in programm-list and bouquets)
Glad it works.
Thanks for reporting the problem with the German letters. This probably means it would be a problem with other characters as well. I will check this issue and see if I can correct it in next release.
Bib_x said:
Hi, working on my hd2 with dreambox 7000 S (gemini 4.6).
But one issue: The programm can´t display the german letters ä, ö and ü (in programm-list and bouquets)
Click to expand...
Click to collapse
Can you add support for modacos´s apptodate?
http://www.modaco.com/category/332/apptodate/
http://forum.xda-developers.com/showthread.php?t=327990
Hi Tilleke,
1) Im running Enigma with Gemini on it
2) Yes i’m using Webif and i can zap normally without lag or error (192.168.1.12), so port 80
3) I am using a WIFI connection and after 2 or 3 times pressing downwards in bouquets it comes with this error:
An error occurred on sub_modcommon_executeurl
Response code -1
Timeout
Continue?
4) i am using a HTC TD2 with WM6,1 pro
Thanks in advance
The num pad on second screen isn´t working. Only the buttons on bottom (tv, radio, text, help) are working.
Thx for the suggestion. I'll see what can I do.
Bib_x said:
Can you add support for modacos´s apptodate?
http://www.modaco.com/category/332/apptodate/
http://forum.xda-developers.com/showthread.php?t=327990
Click to expand...
Click to collapse
Yep. Already reported by citychannel. See first post under known issues.
Bib_x said:
The num pad on second screen isn´t working. Only the buttons on bottom (tv, radio, text, help) are working.
Click to expand...
Click to collapse
Thx for the information. This will facilitate tracking down the error and how to resolve it.
citychannel said:
Hi Tilleke,
1) Im running Enigma with Gemini on it
2) Yes i’m using Webif and i can zap normally without lag or error (192.168.1.12), so port 80
3) I am using a WIFI connection and after 2 or 3 times pressing downwards in bouquets it comes with this error:
An error occurred on sub_modcommon_executeurl
Response code -1
Timeout
Continue?
4) i am using a HTC TD2 with WM6,1 pro
Thanks in advance
Click to expand...
Click to collapse
Thanks for your work
im a db fanatic and currently working on e2 image let me know if you need any help.
One small request:
Would be possible in future release to add a DyNdnS address facility ?
It already works...
I have a profile called "away" which I use to set timer-events when I am not at home. Set up a new profile and in the IP-address-field, just write your DynDNS-address and in the Port-field the port you are using.
You might, of course, need to enable portforwarding in your router-settings.
Hope this helps.
^^MeX^^ said:
Thanks for your work
im a db fanatic and currently working on e2 image let me know if you need any help.
One small request:
Would be possible in future release to add a DyNdnS address facility ?
Click to expand...
Click to collapse
A little bit offtopic:
Do you know which ports i have to forward in my router if i want to stream my dreambox-tv-program over internet with vlc?
Streaming in LAN works well, but i want to watch TV outside my home, too.
PREFACE: This ROM is not intended for everyday use and posted mainly for experienced users and streak-oriented developerss to evaluate it and collaborate on bug resolution and further development. If you expect it to fit any particular purpose - answer is: "No, not yet."
People who really helped to make this possible:
985hPaKicK - author of original cm9 overlay files and pricey patches for DSC kernel.
Sergei Lyubshin (n0p) - team lead of DSC Phoenix kernel, which is used (in it's ICS-que incarnation) to power up this ROM.
Marc Alexander (marc1706) - original kgsl3.8 backport is taken from his kernel HD2 ics and used to provide support for ICS adreno drivers. Also, Marc's advices on changes in hw init procedures related to new kgsl were priceless. Marc, you're da man!
TeamICS - for excellent guides on installing android build environment.
Team Evervolv and CyanogenMod teams - for their hardware overlays.
Currently working:
Boot
Adeno drivers used to provide hwaccel (for real now, surfaceflinger no longer eats 100% of cpu all the time)
GSM subsystem - rild is partially working (no sim pin prompt)
Bluetooth - seem to work. Phone is able to pair to BT headset and output sound thru it (OP's Nokia's BH-103 - tested)
Wifi - partially. Signal strenght not being displayed at statusbar
Touchscreen - working.
Charging - works partially. Phone charges, reports battery percentage, but not voltages.
Sound output - works (No headset icon in statusbar is normal for stock sources.)
Data usage collecting.
UMS
Known not to work:
Everything that's not listed as working.
Other bugs observed by OP (to be extended with ROM users' feedback):
No mobile data reported by several users. OP is unable to reproduce it, so it's being investigated in "blind" mode at the moment. Currently known rild refuses to establish datacall because it thinks that user has no data subscription. EDIT: there's report that removing PIN makes things to work. Not perfect, yes, but worth a try. Report your results, please.
Scanning for available cellular networks is broken.
Extremely high load average (sometimes, seem to be caused by installed applications)
Development related links:
Kernel source: https://github.com/kibuuka/dsc-team-kernel-project/tree/ics - fork of DSC Phoenix kernel that's being used in this ROM. ics branch will be pulled back to main DSC kernel project source tree after n0p's return from vacation.
Device overlay based on hPa's code, changed to build against AOSP source tree instead of CM9's.
Download links: ROM itself - Updated Jul. 14th 13:53MST (changes: see post #2)
Alternative build - OBSOLETE Updated Jun. 28th 05:16MST. Temoporary solution for webkit rendering glitches.
gapps: update-Gapps-ICS-20710.zip See TheManii's post for details Mirror
root: Superuser.zip recommended way to gain a root on this ROM (By TheManii) Mirror
Screenshots: posted earlier in General forum *click*
Installation precautions: Usual ones. ROM is pre-alpha, so nandroid backup is your natural choice in this case . Factory reset from recovery menu is suggested (dalvik cache deletion is optional but recommended for first boot - caches will be rebuilt anyway).
Updating from previous builds of this ROM:
Flash new version
Flash gapps
Flash Superuser.zip (if applicable)
Last words: Feel free to provide additional details and feedback as you test it out. This project is amied to provide a stable base for future streak development. Once we have stable AOSP with full hw support - we have nice shortcut for porting anything that's not AOSP.
P.S. OP is not really experienced in ROM hacking and modding - all tips related to optimisation are greatly welcomed - for everyone's benefit
Reseved
Changelog (New records are displayed first):
Jul. 14 (built and uploaded for internal testing Jul. 13)
kernel: hPa's "force speaker on" patch.
system: Multiple internal changes in camera-related stuff (just for ther record. camera is still unfunctional)
build.prop: mobiledata.interfaces=ppp0. ro.telephony.ril.v3=datacall,signalstrength,facilitylock,icccardstatus,skipbrokendatacall
Jul. 11
kernel: reverted io scheduler back to cfq.
kernel: default cpu governor: smartass2.
kernel: screen rotation patch from updated Phoenix branch. Credits to hPa and n0p. hw.sw.rotation=180 is obsolete now.
system: *finally* there's working (for OP, please do extensive testing and report back) usb mass storage. Cm9's vold and LegacyUsbSupport (along with messing with rest of source) did a trick.
system: removed BasicSmsReceiver.apk from being built and installed. Double sms notifications should be gone.
Jul. 02
kernel: enabled iptables support (needed for mobile quota setting).
kernel: new cpu governors added. feel free to play with them and share your experience.
kernel: added new io schedulers. new default is sio (matter of change).
system: mobile quota setup is functional as of now.
system: built with BOARD_AAPT_PREF_CONFIG := hdpi mdpi. 160dpi users - please check if dialer problem is still present.
interface: added two previously unincluded LWPs.
Jun. 30
Resolved FCs in kgsl shown in 0630 posted earlier. Please re-download. Filename should read as dell_streak-ota-eng.den.063012-2.zip
kernel - Added support for quota2. Mobile data limits will work in next release (still need to figure if iptables binary is needed for this to function)
OpenGL-disabled build is put on hold and won't be updated since we have figured most of opengl-related problems now.
Fixed webkit rendering issues. (Gmail renders pages correctly but seem to "hide" message content on scroll. Anyone aware of gmail app bugtracker presence? Share a link, please UPDATE: not present at clean install. Please check if dalvik cache fleanup fixes it for you. If not - try factory reset) Please note browser is built with OpenGL rendering disabled by default for OP's testing purposes. This will be changed in next build.
Multimedia libs being built from sources now.
Working video in YouTube as result
Lots of Qualcomm-related patches in OpenGL-subsystem (selected parts of frameworks/base taken from mikegapinski's PolishBlood repo (Great job, Mike), lots of patches are from CAF, source was additionally patched (proper ro.sf.hwrotation=180 support, gradient fix, some more) to work correctly on DS5)
Removed some unfunctional components from being built. Factory reset recommended for full removal if updating from previous builds of this ROM.
Flipped thumbnails in recent apps issue - fixed. Re-enabling...
kernel: re-enabled per-process pages in kgsl (default setup).
kernel: default io governor set to ondemand.
Jun. 28
0627 rebuilt with new flags. no changes in code. hdpi resources are included and used by default.
added debug.egl.swapinterval=0 to build.prop
Added Superuser.apk (non-functional at the moment. Use Superuser.zip from TheManii's thread for now)
Jun. 27
Partial fix for mobile data. Searching for available networks known to fail. EDIT:SIM PIN request - still no love. Please test everything you can and report back.
Data usage logging is working now. Necessary patches applied to kernel source.
Surfaceflinger has dithering enabled by default. Smooth gradients ftw.
Added missing LWPs (requested by TheManii)
Added alternative build (it's being built with USE_OPENGL_RENDERER set to false). It has no webkit rendering bug at cost of lesser interface attractiveness.
Tethering options re-enabled. Check which are worked for you and report back, please.
Jun. 23
Disabled per-process page tables in KGSL driver (for now, matter of reversal on test results)
Surfaceflinger problem resolved. Interface is pretty smooth now
Enabled PF_KEY support in kernel (in resolution of pkoning's bug report)
Jun. 21
new kernel build - ipv6 is enabled - without this google services fail to operate properly
added missing apps (Messaging, Camera (broken) and several others) to build set
added some findings to build.prop, removed libGLES_android.so - overall interface performance is slightly improved, yet we're sure we're running with hwaccel now
Jun. 19
sound is partially working now (speaker and BT headsets. wired headsets/headphones not working yet)
if i not mistaken... there is ICS apps rip/port for messaging... i think i have seen that on market...
No screenshots?
john9 said:
No screenshots?
Click to expand...
Click to collapse
i believe OP already included it on the first post...
This is the Great Start !!!
john9 said:
No screenshots?
Click to expand...
Click to collapse
I think these are the screenshots
http://forum.xda-developers.com/showpost.php?p=27537842&postcount=46
What a great start!
I just tried it for a while. It feels awesome to have gotten this far. The ROM is quite laggy as the OP has already mentioned but I was able to get around. I was unable to make a call got an error about sim card not being there. I didn't have any 3G connectivity either. And didn't have any Wi-Fi to try since I am office right now. Since I did this in a hurry I forgot to factory reset but didn't get any FCs. I am upgrading from CM 7.2. None of the google apps seem to work besides youtube but all other apps started without any issues. Looks very good though it's almost like I can smell ICS now.
I have a spare Streak so am happy to reserve it for testing. Let me know if I can do anything specific.
I can confirm that wifi works.
I have tried setting up my Google account but get "Unfortunately, Exchange Services has stopped"
Browser works after a fashion but is not usable.
I can dial outgoing call and the receiving phone rings but no sound. Likewise for incoming calls, my Streak rings but I can't hear the caller and the caller can't hear me.
I seem to have trouble setting up an APN.
Sorry if all of this is already known. I still can't believe that I am looking at Android 4.04 on my Streak.
omg!
I am so looking forward to this!
Mega-Kudos to everyone involved!
yes, this is a good start for DS5 android 4.0 .
good start！
waiting for your further work,
thanks a lot.
I use this mms.apk (from Evervolv ICS rom), push it to system app and change permission. Sms can send and receive (but it take about 1 minute to send sms). http://db.tt/DTuQO5sS
Maybe this could help, could you check this build prop patch made by @lithid and @the_plattypus to fix the red box screen.
http://db.tt/zAJ04F8a
The build prop is for evo4g sense 4.0 rom.
The camera libs by @rapmv78
http://db.tt/CiZxdJT2
How I wish I have my streak with me.
Sent from my MT27i using xda premium
nom051205 said:
I use this mms.apk (from Evervolv ICS rom), push it to system app and change permission. Sms can send and receive (but it take about 1 minute to send sms). http://db.tt/DTuQO5sS
Maybe this could help, could you check this build prop patch made by @lithid and @the_plattypus to fix the red box screen.
http://db.tt/zAJ04F8a
The build prop is for evo4g sense 4.0 rom.
The camera libs by @rapmv78
http://db.tt/CiZxdJT2
Click to expand...
Click to collapse
Yep, will look further, thanks a lot. Right now i'm trying to figure what causes gralloc to get this mad (almost sure that buffer status errors are the main reason of phone sluggishness).
Oh and btw, could you please post logcat taken while sending sms?
Oh! Yes, Yes, Yes ... =P
Will flash it wright-a-way and give some feedback
Great news ! "You've made my dreams come true" =D
Hope it'll be great and powerfull change for our DS5's =]
---
Ok, so: - WiFi - worsk
My menu LEDs are always on, even after screen time out.
Camera (from lock screen) makes device reset. [there is no camera app i think]
Can't Add any APNs
Sound want work at all
Can make incoming/outgoing call (but with no sound in my earphone/mic)
Web browser cant display pages correcly
Screen brightness want work
Gallery(phonee) want access my SD
Phone correctly downloaded time data from operator.
I would offer every possible assistance in developing the project =P
Great JOB! ...going back to DSC1.1 - ...till now.
kibuuka said:
Yep, will look further, thanks a lot. Right now i'm trying to figure what causes gralloc to get this mad (almost sure that buffer status errors are the main reason of phone sluggishness).
Oh and btw, could you please post logcat taken while sending sms?
Click to expand...
Click to collapse
Kibuuka would you take a look at CM9 for Acer Liquid?
It is almost same as DS 5.
Maybe you can use the necessary libs from that ROM to solve the issues.
Sms send and received work perfect now (maybe last time hv bad network), opera mobile browser work perfect, superuser not work well, can use root explorer but cannot use other root apps.
This is really a good start, I believe we will hv stable version soon.
Sent from my PC36100 using Tapatalk 2
I am getting some offset errors during install, tried some times downloading but still same
Sent from my Dell Streak using Tapatalk
abauer said:
I am getting some offset errors during install, tried some times downloading but still same
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
These messages are not error ones. Please read this.
Sound output is working now (tested with internal speaker and BT headphones. Wired will be tested tomorrow, don't any of these around at the moment ) EDIT:New download link is live now.
I share links to Pocket a LOT but every time I'm sending link to Pocket, I have to scroll down in the Share dialog to find Pocket. In my case I just use browser, rss reader and email apps more so Pocket app is burried deep down the list. In previous versions of Android it was all about alphabet but now it's about the time spent in apps (read more details about that from actual Pocket lead developer). This module spoofs the usage timer for Pocket so it's always on top of the Share list.
I don't really need any other changes so no custom manager is planned. (But maybe @defim could incorporate something like this in his CustomShare )
This module has been merged into new module http://forum.xda-developers.com/xposed/modules/mod-xposed-tweaks-cm-t3279109. Please check that module for any future updates.
Hi.. thanks for creating this module! I am trying it for the first time on Android 5.1 .. it doesn't seem to work, so I'm guessing it might need to be updated to support 5.1 (or I'm not testing it properly I suppose)
clefster said:
Hi.. thanks for creating this module! I am trying it for the first time on Android 5.1 .. it doesn't seem to work, so I'm guessing it might need to be updated to support 5.1 (or I'm not testing it properly I suppose)
Click to expand...
Click to collapse
Are you sure Xposed works for you - do you use any other module? I only quickly check the source of 5.1 from my phone and I didn't notice any difference.
Thanks, sweet and simple. I share to Pocket a lot, and before I enabled it Pocket was wayyyyyyy down the list when I hit share.
Manta, Purity Rom 5.1
Hi. Is there any way that i could add any app in share menu? For example i use instagram and OGinstagram in same time. In instagram when i want to share a post url, i see many apps but not OGinstagram. I have to choose gnote, then click on link in gnote and then choose OGinstagram... Is there any way/app/module or anything that can do this?
Maybe make it configurable? I would like to be able to choose any app to be first. Thanks!
Introduction
VirtualSensor is a module built on Xposed that creates several sensors on devices which do not have them. It does sensor fusion using the values from the accelerometer and the compass which are the two main requirements for this module.
There are currently 5 sensors emulated :
TYPE_ROTATION_VECTOR
TYPE_GYROSCOPE
TYPE_GEOMAGNETIC_ROTATION_VECTOR
TYPE_GRAVITY
TYPE_LINEAR_ACCELERATION
Being the most useful sensor for many applications, the gyroscope is the main sensor this project is about.
This module is born as an answer to personal frustration from not being able to use some applications after updating from my older Moto G (i.e. Photo Sphere) and later also as an answer to this thread.
Changelog
Code:
v1.5.1 - 02/08/2017:
This minor version fixes the module for Nougat devices.
See the changelog of v1.5.1 for the more information on what has changed for the major version 1.5.
v1.5 - 02/08/2017:
Finally a new release after (quite) a while. This release should fix the majority of bugs encountered on current and previous versions of Android.
With the precious help of people on Github, the cardboard hook has been (hopefully) improved.
The overall stability and reliability should be better now.
This release will stay marked as beta until relevant and good feedback is received, to please head over to Github if you can and report issues if any (or add to the exising issues to check wether they still exist)
v1.41 - 01/08/2016:
* Fixed the module, previous version broke it because of proguard minify, do not use version v1.4
v1.4 - 31/07/2016: /!\ This version is broken, avoid it /!\
* Added a check for already existing native sensors so that they don't get overridden by the module
* Now checks the values of the accelerometer and magnetic sensor against their accuracy. This means that the output values contain less noise without loosing too much precision
* Added a simple GUI to quickly get informations about the module. This part also calculates the values the gyroscope should return and compares them against the one the module actually returns
* Some hooks are now made on higher-level API (public available functions for apps), which means that specific device code should no longer break them
* Fixed a recurrent exception (ConcurrentModificationException)
v1.32 - 29/07/2016:
* Fix the mRequiredPermssion field no available on SDK < 20
Hotfix #2 for v1.3
v1.31 - 29/07/2016:
* Fixes the issue with SDK <= 18 where mStringType doesn't exist in the Sensor class
Hotfix for v1.3
v1.3 - 29/07/2016:
* Sensors are now added in a proper way. They should no longer accidentally override existing sensors / cause compatibility issues
* All gyroscope axes are fully functional !
* If it didn't work before for you on JellyBean-Lollipop, try now, it might (fixed the check for initialisation of SystemSensorManager)
* Started to work on a new filter system for the gyroscope mainly
v1.21 - 25/07/2016:
Hotfix for v1.2 to avoid crashes on JB devices.
v1.2 - 26/07/2016:
* Fixed compatibility with SDK18-22 (Android JellyBean 4.3 - Android Lolipop 5.1)
* Added a little more log
* Calculation for the gyroscope is now based on the calculated gravity sensor data, which (should) makes it work as intended in any orientation
* The virtual sensors now have a little more information in the created Sensor class, just to make sure this isn't an issue
v1.11 - 25/07/2016:
Hotfix for v1.1, fixes an exception raised in some cases when trying to get the accelerometer's min delay.
v1.1 - 25/07/2016:
* Added support for all SDK versions from SDK16 to SDK23+, this means all android versions starting from Jelly Bean should be supported
* Added a lot of new sensors : TYPE_ROTATION_VECTOR, TYPE_GEOMAGNETIC_ROTATION_VECTOR, TYPE_GRAVITY and TYPE_LINEAR_ACCELERATION
* Still no support for Pokémon GO though, working on it
* Some exceptions fixed
* Code refactored a lot
v1.0 - 23/07/2016:
Initial release.
Known issues
Right now, the Z-axis is not emulated as it always returned wrong values (Investigating this right now) Fixed
Some applications use the NDK instead of the SDK to access the sensors, the workaround is to hook them seperately, but that isn't done yet
There is some jitter even though the values are smoothed using a lowpass filter and averaged out
Disclaimer
Code:
Though it is unlikely this could happen given the modifications it does, the responsibility is yours for whatever happens after installing and using this module.
Download
Github : https://github.com/Frazew/VirtualSensor/releases/
Xposed Repository : http://repo.xposed.info/module/fr.frazew.virtualgyroscope
Contributing
There is a Github project for this module so please do not hesitate to contribute to it. I'll be glad to share knowledge and code. Please know that I'm not (yet? ) a professional coder and that errors are quite likely to happen.
XDA:DevDB Information
VirtualSensor, Xposed for all devices (see above for details)
Contributors
Frazew
Source Code: https://github.com/Frazew/VirtualSensor
Xposed Package Name: fr.frazew.virtualgyroscope
Version Information
Status: Testing
Current Stable Version: v1.5.1
Stable Release Date: 2017-08-02
Created 2016-07-23
Last Updated 2017-08-02
Reserved
I supposed you tested this with Pokemon GO, as is the reason of so many requests for a virtual gyroscope so I'll suppose is still nor working due my specific device.
Motorola Moto X Play, running CyanogenMod 13.
Thanks for your work!
Thanks for chance to get normal VR experience
Works great with Lenovo Vibe P1 (this device has a jittering problem with its own pseudo-gyro). Tested with Youtube 360 videos. Works great for watching up/down and rotate. As well as you said z-axis is not working at all, so it's impossible to move point of view to the left/right. Can help you with testing on my device, if you want. I have Lenovo Vibe P1 with Android 6.0, TWRP and Root.
P.S. Is there any way to turn on z-axis for testing, for example by using your project at github. I'm not sure if I will understand there something, I was coding before only at C#, but I can try.
OliverG96 said:
I supposed you tested this with Pokemon GO, as is the reason of so many requests for a virtual gyroscope so I'll suppose is still nor working due my specific device.
Motorola Moto X Play, running CyanogenMod 13.
Thanks for your work!
Click to expand...
Click to collapse
I did not test it with Pokémon GO, however I think the hook will have to be made in the app itself. I'll look into it right now
EDIT: Pokémon GO uses the TYPE_ROTATION_VECTOR sensor. This sensor requires data from the gyroscope. I'm working right now on emulating it.
Saratsin said:
Works great with Lenovo Vibe P1 (this device has a jittering problem with its own pseudo-gyro). Tested with Youtube 360 videos. Works great for watching up/down and rotate. As well as you said z-axis is not working at all, so it's impossible to move point of view to the left/right. Can help you with testing on my device, if you want. I have Lenovo Vibe P1 with Android 6.0, TWRP and Root.
P.S. Is there any way to turn on z-axis for testing, for example by using your project at github. I'm not sure if I will understand there something, I was coding before only at C#, but I can try.
Click to expand...
Click to collapse
Glad to see that it works ! I could make another build with the Z axis activated but I really need to look a bit more into it. The problem with it is that it seemed to return higher values than the other axes. This generally broke the calibration many apps do and though the z-axis worked, they would then ignore the small variations of the other axes.
In case you want to build it yourself, it's quite easy, just remove the multiplication by zero here : https://github.com/Frazew/VirtualSensor/blob/master/app/src/main/java/fr/frazew/virtualgyroscope/XposedMod.java#L156
Can't install it on Jelly bean 4.2.2 :/
first a big THANKS!!!!!
I downloaded sensors tests app.before the module,gyroscope test wasn't there!after the module,voilla!!gyroscope test was there!I openned it and tested side by side with my xperia Z3 tablet.But values was muuuch different...It's ok,we all hope for possible future module updates!again THANK YOU!!!
Dant3s said:
Can't install it on Jelly bean 4.2.2 :/
Click to expand...
Click to collapse
Right now the minimum SDK version is KitKat, that's just because the sensor methods are different on Jelly Bean and I haven't worked on it.
Now that there are people who can actually test it on Jelly Bean I'll make an update to add support for it
Frazew said:
Right now the minimum SDK version is KitKat, that's just because the sensor methods are different on Jelly Bean and I haven't worked on it.
Now that there are people who can actually test it on Jelly Bean I'll make an update to add support for it
Click to expand...
Click to collapse
Glad to hear that, thanks
have see this thread : Help module to simulate Gyroscope with Accelerometer and Compass by nicolobos77
Hey, since we've doubled same purpose module I decided to use yours since its clear that you have much more experience than me and your code is much more elegant. (I never used Xposed before)
I built and ran it on my phone, and noticed exception thrown in logs (made pull request with fix at github), this wasnt big deal, but it seems like even though math is correct, sensor behaves wierd. Output is delayed by ~1 sec. There is also wierd "bounce effect" after rotating at ~20degree/sec and stopping velocity goes to ~-20 degree for a moment and drops back to 0.
Also depending on delay set up by application when registering listener some of apps only seem to get any output other than 0 if I like swing phone very hard. So my guess is that you might have more sensitive sensors in your phone and smoothing methods you applied are overkill for mine. I'll look into it closer later today, or tomorrow and see if changing parameters helps.
Thanks you for your work. One question, my phone has this, link to the image: imgur.com/a/lD7Sg Accelerometer it's fine but compass and orientation sensor are the same thing?. I cant find an app that can show me if I have compass sensor. Thanks you again and sorry for my bad english :/
And can you make a guide like "How to Install or what do you need in order to" or something like that? Please?
Maveroik said:
Thanks you for your work. One question, my phone has this, link to the image: imgur.com/a/lD7Sg Accelerometer it's fine but compass and orientation sensor are the same thing?. I cant find an app that can show me if I have compass sensor. Thanks you again and sorry for my bad english :/
And can you make a guide like "How to Install or what do you need in order to" or something like that? Please?
Click to expand...
Click to collapse
Compass means Magnetic Sensor, so yes, you do have one.
Frazew said:
EDIT: Pokémon GO uses the TYPE_ROTATION_VECTOR sensor. This sensor requires data from the gyroscope. I'm working right now on emulating it.
Click to expand...
Click to collapse
I did some reverse engineering on that matter, Pogo uses whole bunch of sensors: TYPE_GRAVITY, TYPE_GYROSCOPE, TYPE_ACCELEROMETER, TYPE_MAGNETIC_FIELD, TYPE_ROTATION_VECTOR and TYPE_LINEAR_ACCELERATION.
Actually I believe that TYPE_ROTATION_VECTOR can be simulated by copying TYPE_GEOMAGNETIC_ROTATION_VECTOR values.
Mourdraug said:
Hey, since we've doubled same purpose module I decided to use yours since its clear that you have much more experience than me and your code is much more elegant. (I never used Xposed before)
I built and ran it on my phone, and noticed exception thrown in logs (made pull request with fix at github), this wasnt big deal, but it seems like even though math is correct, sensor behaves wierd. Output is delayed by ~1 sec. There is also wierd "bounce effect" after rotating at ~20degree/sec and stopping velocity goes to ~-20 degree for a moment and drops back to 0.
Also depending on delay set up by application when registering listener some of apps only seem to get any output other than 0 if I like swing phone very hard. So my guess is that you might have more sensitive sensors in your phone and smoothing methods you applied are overkill for mine. I'll look into it closer later today, or tomorrow and see if changing parameters helps.
Click to expand...
Click to collapse
Thanks for your, I didn't see this exception when I tested it, but now that you bring it up, it seems obvious.
As for the delay you are talking about, the explanation I have for this is that I filter the output using a mean filter that uses the 10 previous values. This has the advantage of reducing the jitter a lot but it also has the huge disadvantage of adding a lot of delay. I will change this as there are better ways to filter the output than using the mean of the previous values. Like I said, I only tested it with my phone and did not take into account the sensitivity of the sensors. This is actually a good idea and I'll have to change that. Feel free to tweak what you want and make pull requests, that's the best way this module can evolve.
Mourdraug said:
I did some reverse engineering on that matter, Pogo uses whole bunch of sensors: TYPE_GRAVITY, TYPE_GYROSCOPE, TYPE_ACCELEROMETER, TYPE_MAGNETIC_FIELD, TYPE_ROTATION_VECTOR and TYPE_LINEAR_ACCELERATION.
Actually I believe that TYPE_ROTATION_VECTOR can be simulated by copying TYPE_GEOMAGNETIC_ROTATION_VECTOR values.
Click to expand...
Click to collapse
I reverse engineered it too and saw these sensors too. The thing is: TYPE_GRAVITY is a virtual sensor created from the accelerometer so no need to simulate it. TYPE_MAGNETIC_FIELD is the compass and TYPE_LINEAR_ACCELERATION is also a virtual sensor created from the accelerometer so no need to simulate it either. I have right now working code to make the TYPE_ROTATION_VECTOR work. I didn't see the TYPE_GEOMAGNETIC_ROTATION_VECTOR so I did the math directly from the rotation matrix values. I guess I'll change to use its values since it's already there, thanks for your help
EDIT: Actually the TYPE_GRAVITY is not a virtual sensor. My bad, I'll see what I can do to simulate it.
EDIT2: Actually TYPE_LINEAR_ACCELERATION is not always present either, I'll simulate it too. I should verify a bit more before posting stuff.
I would donate some cash if you could get the AR function to work in PoGo! That would be awesome!
wktra said:
I would donate some cash if you could get the AR function to work in PoGo! That would be awesome!
Click to expand...
Click to collapse
No need for cash but I'm currently working on it. I implemented a whole new lot of sensors but sadly PoGo doesn't work with them just yet. I'm investigating this and will make an update once it's ready (I play PoGo too so I'd like to see it work too).
Hi , I just registered to thank you a lot for the effort you're doing.
It doesn's seems to work on my LG G3 S, however thank you a lot and hope someone can help you making it through !
Keep the good work.
Dont work on youtube or pokemon Go in motorola moto g 2015(xt1541). Also i installed Cpu Z and it show the virtual gyro sensor ... I dont know why dont work on 360 video on youtube.(sorry for bad english)
Those who have been lucky to upgrade to Wear 2.0 have probably noticed the removed Do Not Disturb toggle synchronization between wearable and phone. Some like it, some not. I didn't like it, so I made an app that does the sync. Currently it only works one way: wearable -> phone. With some hacking, sync is working both ways.
You can find the application in Play Store.
Source, builds and setup instructions are available in github and licensed under Apache 2.0.
Installation instructions for Watch -> Phone sync:
Install phone application and wearable application from on-watch Play Store
Launch application on Phone
Click "Grant Permission" button
Enable Do Not Disturb access permission for application
Make sure all 3 checks in the application pass
Installation instructions for Phone -> Watch sync:
Setup watch ADB
Execute:
Code:
adb shell settings put secure enabled_notification_listeners com.google.android.wearable.app/com.google.android.clockwork.stream.NotificationCollectorService:rkr.weardndsync/rkr.weardndsync.NotificationService
Enable state broadcast in Watch Setup wizard
Currently synchronization phone -> watch is only possible by assigning permissions in ADB. Wear OS doesn't provide management settings. As this is not officially supported - it may not work for everyone or the next Wear version.
I love that something like this is now made, but I have a question. What is the first screenshot in the Google Play Store link for? I thought this was only for DND?
I'd like to install it and find out myself, but my ZenWatch 2 still hasn't received the update.
If your watch isn't updated, then the sync should work out of the box. As for the screenshot, I tried to show that the toggle in the watch will sync to the toggle in the phone. I'm not a designer.
Wonderful little utility. Thank you very much.
Fingers crossed to get phone > watch allowed.
I have a few apps that toggle DND via Tasker on my phone, and having it trigger the watch too would be sweet.
Good news and bad news.
The bad: notification access and all the management is unavailable in Wear. So there will not be an official way to make this work (source).
The good: you can grant the permission in ADB. I tried it and the app can actually switch DND on and off (source).
Having to run a single ADB command will probably not stop the brave people of XDA! So synchronization should eventually come to the watch, just give me some time to fix the current bugs.
Bonus news: AudioManager can be used in android <6 for sound modes. Haven't looked into that yet.
Thanks for this app, I miss the functionality!
Sync from phone to watch is implemented and functional! v1.5 is being pushed to the Play Store. You just need to enable broadcast from phone in setup wizard and execute this command in the watch:
Code:
adb shell settings put secure enabled_notification_listeners com.google.android.wearable.app/com.google.android.clockwork.stream.NotificationCollectorService:rkr.weardndsync/rkr.weardndsync.HackService
raimondas.rimkus said:
You can find the application in Play Store
Click to expand...
Click to collapse
Hello!
Not work on Huawei Mediapad X2 (android 5.1.1).
I know: "only Android 6+ is supported"... But, maybe, android 5.1 can be added to?..
Thank you!
If it can help, I can access Do Not Disturb on android 5 through Tasker.
But it is called "Interrupt Mode". It can be found here: http://tasker.dinglisch.net/userguide_summary.html search for "Interrupt Mode".
raimondas.rimkus said:
Those who have been lucky to upgrade to Wear 2.0 have probably noticed the removed Do Not Disturb toggle synchronization between wearable and phone. Some like it, some not. I didn't like it, so I made an app that does the sync. Currently it only works one way: wearable -> phone. With some hacking, sync is working both ways.
You can find the application in Play Store.
Source is available in github and licensed under Apache 2.0.
Installation instructions for Watch -> Phone sync:
Install phone application and wearable application from on-watch Play Store
Launch application on Phone
Click "Grant Permission" button
Enable Do Not Disturb access permission for application
Make sure all 3 checks in the application pass
Installation instructions for Phone -> Watch sync:
Setup watch ADB
Execute:
Code:
adb shell settings put secure enabled_notification_listeners com.google.android.wearable.app/com.google.android.clockwork.stream.NotificationCollectorService:rkr.weardndsync/rkr.weardndsync.HackService
Enable state broadcast in Watch Setup wizard
Currently synchronization phone -> watch is only possible by assigning permissions in ADB. Wear OS doesn't provide management settings. As this is not officially supported - it may not work for everyone or the next Wear version.
Click to expand...
Click to collapse
Thank you so much.
Sent from my ONEPLUS A3003 using Tapatalk
Works perfect!! Thanks!
raimondas.rimkus said:
... As for the screenshot, I tried to show that the toggle in the watch will sync to the toggle in the phone. I'm not a designer.
Click to expand...
Click to collapse
me neither, but maybe this could help?
I'm just curious. What's the difference between this version available in the Play Store (source code available here) and your own? It looks to me as though that blunden may have forked your code.
That's how open source works, you are free to fork it or take it as an inspiration. His code isn't a plain copy paste, it looks like he even has sync to older android versions, which I didn't have time to do.
I can no longer sync both ways after the newest update, v1.6. I can only control DND from both devices from my watch. Anyone else having this problem with v1.6?
Sent from my SM-G955U using Tapatalk
thecarp1975 said:
I can no longer sync both ways after the newest update, v1.6. I can only control DND from both devices from my watch. Anyone else having this problem with v1.6?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
The first idea is that app got suspended after the update. Make sure watch app is updated and start the app on phone. I've added a check that will tell you if watch DND permission is granted. If everything passes, then there is probably something weird with the AudioManager. Previous version used the new NotificationManager, but it requires a running service for broadcast events. I've switched to legacy AudioManager that can use a stateless broadcast receiver.
[Edit:] Android 4.3+ support is being pushed. This needed a code refactoring, so bugs are probable.
okk
raimondas.rimkus said:
The first idea is that app got suspended after the update. Make sure watch app is updated and start the app on phone. I've added a check that will tell you if watch DND permission is granted. If everything passes, then there is probably something weird with the AudioManager. Previous version used the new NotificationManager, but it requires a running service for broadcast events. I've switched to legacy AudioManager that can use a stateless broadcast receiver.
[Edit:] Android 4.3+ support is being pushed. This needed a code refactoring, so bugs are probable.
Click to expand...
Click to collapse
Yeah, all three permissions were granted. You wouldn't happen to have the APK for the previous version?
Sent from my SM-G955U using Tapatalk
V1.5 attached.
I would still prefer if you could make a logcat and I could fix the problem for the rest of the people. Just do these steps:
Connect phone to ADB
Enable DND, Disable DND on phone
Enable DND, Disable DND in watch
Run: adb logcat -d > bug_phone.txt
Repeat with watch connected to bug_watch.txt
PM the logs and I may try to fix it. It's not the first time android APIs don't work in specific phones.
Just a quick FYI. Version 1.6 works fine here. Nexus 6 / Pure Nexus 7.1.1 / Magisk root. Huawei watch AW 2.0 7.1.1 stock.
I can start DND from either watch or phone and the other device enables.
It works when I start Sleep as Android; SaS enables phone DND and that enables DND for AW 2.0, then Tasker via AutoWear triggers theater mode on my watch. One step goodness! :victory: