Hey guys! I was paging through the forums and had what could be an awesome idea. I'm by no means a aerospace engineer nor a computer scientist, but I was trying to figure out how hard it would be to take a standalone Attitude and Heading Reference System (AHRS) system like the iLevil 3 Sport, and display it on something like the EPSON BT-300. Im sure it would have to be a simplified display, but in theory couldn't we get something like a fighter jet HUD directly in front of your face?!
The reason I have chosen these two pieces of hardware (iLevil 3 Sport and EPSON BT-300) is to try and simplify the problem at hand. Through programs like ixGyro, AHRS Utility by iLevil, and Xavion, to name a few (all of which are compatible with the iLevel, and available to download directly to any Android system), you already have all of the information in tablet form.
The AHRS device has all of the hardware required and outputs the information via WiFi. These programs have already proven that this information can be successfully displayed. It seems as through that the only problem now is the GUI. I don't have either of these two products so I can't say for certain, but I'm willing to bet that the BT-300, running Android 5.1, can display this information almost the exact same as on your phone or tablet! I propose that we simply delete the background so you have a true augmented reality while you fly!
Related
Hi, my name is Eric. I've been working with WinCE for a long time (since WinCE 2.0 haha) and I've regained interest in PPC programming. Working with few things here and there, mostly experimenting.
In anycase, I've got an idea to record g forces on a vehicle while it's being tested to its limits (AutoX, drag race).
Now, I know there's already a piece of software out there, gPC, but it isn't completely refined (indepth calibration, angle corrections) or completely free (by donation).
The goal of the project is to create something similar to a device called gTech which goes upwards of $300 for the basic model.
Key features will include:
- a reset function + algorithms to compensate for device orientation
- graphs of resulting logged data
- logging of calibrated data and raw data
- Driving aids
- Flashing screen to indicate reaching of new peak G (separate indicators for forward and lateral)
- a screen showing realtime overlapping graphed data for all axis
- a 2d grid with a cursor indicating current forward and lateral g
- on the same 2d graph, a drawn boundary indicating limits of g achieved (this will eventually look like an egg after working the car hard)
- and finally, real time telemetry transmission via edge/3g to a receiving computer
The ultimate goal of this project is to provide reliable data for motor enthusiasts whether they would like to see if their shifting is smooth, or if they're braking, or powering on in the right places or if their car mods have had any effect (this last one is pretty useful to quantify). In addition, provide some rudimentary tools to assist in competitions and spirited driving in the form of g limit warnings (flashing screen, large indicators of current g). In the case of spirited driving on a mountain road, the device can warn when approaching loss of traction (after collecting limit data) to prevent going off a cliff.
Venues of use:
Auto Cross
Track Days
Drag Strip
Skidpad
Of course, I have to insert here, that this device can't save your bacon if you do something idiotic and by no means do I condone dangerous driving.
With that said, all the above is what I hope to achieve and any of your comments is well appreciated.
Current Release:
v0.1
Alpha stage, rudimentary raw data output via numbers and a line (indicating X and Y recorded g) and a circle (indicating Z g). The numbers shown are the raw numbers recorded from the accelerometer and not converted to m/s^2. Although, you can probably do that math on your own if you're smart enough (simple scaling). What I've discovered is that each accelerometer is different, and even going from a negative axis (eg, device upside down) to positive axis (device right side up) will give different numbers. In addition, if you run the program, you'll notice a lot of jitteriness. I hope it doesn't affect the accuracy once I smooth them out with a segmented average.
Executable is packaged in a zip. It contains an EXE which can be straight run with Dot NET CF v2.0 (basically, all WM 6.1 devices)
Hi Canagan,
Great idea, I will certainly be testing this out.
I would like to ask, would it be possible to be able to include 1/4 mile time, and 0-60 etc so we can work out HP of the car. There is a similar app for the Iphone called Dynolicious http://gizmodo.com/5030749/iphone-apps-we-like-dynolicious-car-performance-meter
Thanks.
Whoooaaa sound a really good app ! Will test it this weekend ! Thanks
PooleyUK said:
I would like to ask, would it be possible to be able to include 1/4 mile time, and 0-60 etc so we can work out HP of the car. There is a similar app for the Iphone called Dynolicious http://gizmodo.com/5030749/iphone-apps-we-like-dynolicious-car-performance-meter
Click to expand...
Click to collapse
Yes, I can do that if there's more of a demand for it. Calculating horsepower is fairly simple, however, I may put 1/4 mile times and 0-60 towards the end of development as they require tieing into the GPS.
Great idea.. I will test it also
It seemt to be working on my Touch HD. But are the meaning of all these numbers??
CanaganD said:
Yes, I can do that if there's more of a demand for it. Calculating horsepower is fairly simple, however, I may put 1/4 mile times and 0-60 towards the end of development as they require tieing into the GPS.
Click to expand...
Click to collapse
Cool, looking forward to seeing this develop.
So far the accelerator test seems to be working fine.
would be need ive i could see how many hp mycar has
I am aware that this has been asked many many times, but i don't see a thread for this issue. I would like to know what attemps have been made to get some sort of support. I am by no means a developer, but i will try my best to get things running. Would it be something as simple as taking a a file out of a current android phone with the same specs and modding for use with a touch pro.
I'm simply curious if there is a thread or website around that discusses this and other issues in more detail.
I'm no kernel hacker, but I am...curious.
That's what i would like to know. facts about how far the development is. Maybe we could start a thread that has such progress stated. Where only the devs would be able to post, so we can have us a look.
The best you can do is read the IRC logs from #htc-linux. I think I recall reading in the logs that klinux had gotten OpenGL working on the Pro2, even with applications like Neocore (thought they're apparently slow).
You have to be a little bit more clear on what you mean by "open gl working".
I'm the developer who was working on the open gl for the klinux build. Bottom line is that open gl is working, but not with hardware acceleration. We used then nexus one drivers (adreno200) to enable things a live wallpapers. But it's so slow its not even worth it.
Now to get hardware 3d working 100%? a lot more work and testing. lol.
Well is hardware 3d working for any of the current android ports in any capacity?
Also, I'm so used to reading hardware specs in Desktop computer form. But with these phones, the only thing I know about them is the CPU manufacturer, model number, and speed.
Is there a separate chipset that handles audio graphics etc, or is it completely SoC.
I read about recent Android ports on the iPhone, and it seems they already have things like external audio working. Is this because the hardware on the iPhone similar to another HTC Android phone, more so than the hardware in the Rhodium?
awesome thread... actually informative and supportive.
i think what the OP is saying is how can us lowerscale highend users be more involved, perhaps in the debugging, data gathering... we could start a -sub group dedicated to each corresponding issues... bill gates didnt invent windows, him and his crew did. the more the merrier eh?
I have a long running reverse engineering thing going on. I have been looking for more info other than IRC. I would like to put my good skills to work w/out starting from scratch. Any info?
EDIT: I did find this, It has some helpful starting info: http://www.androidonhtc.com/wiki/Get_Involved
This is a great thread! I've been wanting to get in on some of this action. Hopefully this will reduce some of the clutter in Reefer's thread.
I meant to get hardware acceleration working. How far has this come along since i posted this??
Only Diamond / Raphael has hardware 3D enabled so far.
Very limited 3D for "low resolution" could be enabled in blackstone or other devices with workaround but that is somehow meaningless.
phh has tried different combinations of memory allocation but in vain.
so am I... given up at the moment.
mcdull said:
Only Diamond / Raphael has hardware 3D enabled so far.
Very limited 3D for "low resolution" could be enabled in blackstone or other devices with workaround but that is somehow meaningless.
phh has tried different combinations of memory allocation but in vain.
so am I... given up at the moment.
Click to expand...
Click to collapse
Phh recommended to trace down mem locations used by wince and that has been done but it still refuses to fire up once pmem.c is modified.
Recently i got the wince dmesg from my rhod in hopes that a cold boot would show as to how the 3d is being activated but that also showed no results. I get this crap when Manila is launched.
[ManilaToday](34156): ### Launching manila ###
23:20:09 [DISP] DrvEscape::HTC_SET_3D_LAUNCHING_FLAG.
I'm not sure what HTC_SET_3D_LAUNCHING_FLAG is.
The next step would be to make an android app and trace down what the hell the libgles_qcom driver is actually doing to see if it is working properly. If you load up ahi2dati.dll on winmo you can actually use the functions to show crap on the screen so i'm hoping the same can be done on android.
Not sure what else can be done at this stage.
[ACL] said:
Phh recommended to trace down mem locations used by wince and that has been done but it still refuses to fire up once pmem.c is modified.
Recently i got the wince dmesg from my rhod in hopes that a cold boot would show as to how the 3d is being activated but that also showed no results. I get this crap when Manila is launched.
[ManilaToday](34156): ### Launching manila ###
23:20:09 [DISP] DrvEscape::HTC_SET_3D_LAUNCHING_FLAG.
I'm not sure what HTC_SET_3D_LAUNCHING_FLAG is.
The next step would be to make an android app and trace down what the hell the libgles_qcom driver is actually doing to see if it is working properly. If you load up ahi2dati.dll on winmo you can actually use the functions to show crap on the screen so i'm hoping the same can be done on android.
Not sure what else can be done at this stage.
Click to expand...
Click to collapse
Ok, i would love to help out as i have never rly done anything like this b4. What exactly are you doing. How do you get HTC_SET_3D_LAUNCHING_FLAG?
How would i open a .dll, i dont think these can just be opened up to see what they are doing. I am on the dark side of the moon here. I know whats going on, but have no clue what to do to help.
garage_man said:
Ok, i would love to help out as i have never rly done anything like this b4. What exactly are you doing. How do you get HTC_SET_3D_LAUNCHING_FLAG?
How would i open a .dll, i dont think these can just be opened up to see what they are doing. I am on the dark side of the moon here. I know whats going on, but have no clue what to do to help.
Click to expand...
Click to collapse
I actually found HTC_SET_3D_LAUNCHING_FLAG on the wince dmesg. You can do this by doing a pwf dump.txt 0x16a00000 0xFFFF0 in haret. I did it after a cold boot to see if anything is done to the gpu once wince boots.
Loading the dll is easy. just make a simple win32 app and do a loadlibrary. This part works but it's not helping on android. I'm interested to see what mcdull thinks since i think he has ventured a lot into this as well. Right now if we can make a simple app in android to load the libgles_qcom.so directly and trace every step, i think that would be helpful to see where we are failing. I'm close to giving up..lol i already took 2 sick days from work to get to where i am now so i could use some help.
Here is what i got out of the chip in wince.
name: ATI HandHeld Interface
versions: 2.07.05110.34681
Revision: 0
ChipID: 1362104322
revisionid: 0
TotalMemory: 15990784
BusInterfacemode: 2
InternalmemSize: 262144
ExternalMemSize: 0
Surface info: 800x480
surface total bytes 768000
dwFrameBufferPhysical=0x14c00780 m_dwFrameBufferVirtual=0x57e00000 dwFrameBufSize=0xbb800
Most people here could probably not help with the hardcore kernel dev stuff, but I guess if you need memory locations or so (be it for opengl/sound etc) I think there a a LOT of people that are willing to run some apps that dump a txt file with debugging info & mem locations to their SD-card and send you that
I would love to help with developing, even if it means that I have to boot into winmo and android all night long and gather certain information, memory-adresses, try different versions of programs with all kinds of parameters etc.
Star-Lite said:
Most people here could probably not help with the hardcore kernel dev stuff, but I guess if you need memory locations or so (be it for opengl/sound etc) I think there a a LOT of people that are willing to run some apps that dump a txt file with debugging info & mem locations to their SD-card and send you that
I would love to help with developing, even if it means that I have to boot into winmo and android all night long and gather certain information, memory-adresses, try different versions of programs with all kinds of parameters etc.
Click to expand...
Click to collapse
We need more devs in general. I ran a trace on a basic app that runs 3d. So there is still a lot of crap to examine.
I'm willing to kill my touch pro 2 and remove the CPU to trace the JTAG locations but I only have the datasheet from the MSM7200/7500, not sure if it will be the same locations. I bet if I hooked up my Segger I could see exactly what is failing on the OpenGL and sound side since alot of hardware debugging is done this way...just sucks I dont know for sure if the pinouts are the same. I'm done it on quite a few different phones and boards over the years so its not a big deal. Omap3430 was simple to trace and the OMAP3530 had the exact pinouts.
BinaryDroid said:
I'm willing to kill my touch pro 2 and remove the CPU to trace the JTAG locations but I only have the datasheet from the MSM7200/7500, not sure if it will be the same locations. I bet if I hooked up my Segger I could see exactly what is failing on the OpenGL and sound side since alot of hardware debugging is done this way...just sucks I dont know for sure if the pinouts are the same. I'm done it on quite a few different phones and boards over the years so its not a big deal. Omap3430 was simple to trace and the OMAP3530 had the exact pinouts.
Click to expand...
Click to collapse
Sounds crazy.. i love it.
I was messing around today and made a small app to load the libgles_qcom.so directly to see if i can replicate my winmo success. Most of the ahi functions are included in the android driver as well except for AhiDispSurfGet which made it impossible for me to draw anything on screen.
The chip did pump out the same info as i posted before and it matches so thats a step in the right direction. Means we can recognize the chip with no problems and all 15.25 memory is reporting as well. If i had more documentation on those functions exported im sure i can get the chip to try to display something directly.
Interesting bit of info I read and perhaps someone can clarify this here. The Sprint Touch Pro 2 uses the Qualcomm MSM7600 processor. The AT&T Tilt2 (GSM phone) uses the MSM7201A processor. The "A" refers to the smaller 65nm die size (I believe).
From what I've read, some changes occurred on the MSM7200 -> MSM7201 due to patent infringements. The next question is, is the MSM7201A and MSM7600 essentially the same chip, just different hardware for CDMA/GSM?
I guess the "libgles_qcom.so" library is used in many other HTC Android phones, but for some reason it's failing on the touchpro2/tilt2, and we're not sure why (although logically it sounds like the library should work as it's used by other android phones with the same chipset)? I'm no kernel dev (I write .NET/c# apps which are much easier than kernel stuff), but am somewhat familiar w/ linux and perhaps can assist in development..
NewbTrader said:
Interesting bit of info I read and perhaps someone can clarify this here. The Sprint Touch Pro 2 uses the Qualcomm MSM7600 processor. The AT&T Tilt2 (GSM phone) uses the MSM7201A processor. The "A" refers to the smaller 65nm die size (I believe).
From what I've read, some changes occurred on the MSM7200 -> MSM7201 due to patent infringements. The next question is, is the MSM7201A and MSM7600 essentially the same chip, just different hardware for CDMA/GSM?
I guess the "libgles_qcom.so" library is used in many other HTC Android phones, but for some reason it's failing on the touchpro2/tilt2, and we're not sure why (although logically it sounds like the library should work as it's used by other android phones with the same chipset)? I'm no kernel dev (I write .NET/c# apps which are much easier than kernel stuff), but am somewhat familiar w/ linux and perhaps can assist in development..
Click to expand...
Click to collapse
learn haret/haretconsole and take a look a the kernel. good place to start. Feel free to come into the irc board if you have any questions
I have long since dreamed of a car-puter or workstation that simply my phone expanded. All apps and files would automatically travel with you and the whole system would automatically get upgraded, for free, every time you upgraded your phone.
Mirroring images and sound can be done many ways, but the problem has always been inputs from the larger screen making their way to your phone. There are a few work-arounds with resistive screens, but they look junky, have low sensitivity and don't allow multitouch.
The holy grail has always been full 2-way comm with an external capacitive screen. This is the first time I have ever seen a capacitive screen that lists 10-point capacitive touch as a feature for Android and that has Android drivers downloadable in the 'documents' tab of their product page.
http://lilliputweb.net/capacitive-touch-screen-monitors/7-inch-multi-touch/779gl-70np-c-t.html
Does this really mean what I think it does?!? I know that drivers in android are far from as simple as an executable file in windows. But does this mean that with a little work any of us could make this monitor play nicely with our own devices? Or ideally could a person or two (with more skill than I have) make this monitor plug and play with a common distro like cyanogenmod or the like?
Any thoughts from any of the more experienced minds in these forums would be VERY appreciated. PS. I love this forum and wish I had the time and the chops to add more to it myself, but in the meantime thank you to all contributes. Cheers.
I’d like to start off by saying some of these views are totally personal to me, and how I use these kind of boxes day to day. I have been looking at the NVIDIA Shield TV 16gb model, with the controller and remote.
The Shield TV is right at the top of list of Android TV boxes, it has the spec and the features to make it a future proof Android TV box. The Tegra X1 makes it incredibly fast and snappy. I found myself clicking around with ease, without a single stutter.
The initial setup was easy, once turned on, I did a couple of updates and was logged straight into the Shield TV home screen. This leanback launcher can only be controlled with the “dpad” on either the controller or the remote. There are various rows, including suggestions, Nvidia apps and your own downloaded apps. The suggestion row is bizarre, as I have no idea what the recommendations are based on. I can alter what sources are used (Youtube, Google TV/Movies etc), but the recommendation engine isn’t very good.
Installing apps is easy, but this may be due to the lack of apps you can download. I found very little of my daily driver apps to download, and had to resort to second or even third rate alternatives. This isn’t really NVIDIA’s fault, as this is more an issue with Android TV. Apps have to be compatible and made for the “leanback” generation. Apps like Solid Explorer, TTorrent, and Transdroid are always installed on any Android box, but I was unable to here.
There are ways around these app limitations, involving sideloading, and alternative launchers. But I just want to install an app and use it, I don’t want to have to turn around the box so it’s facing east, wait till the time includes a 9 and then chant whilst installing an APK file! This may be a slight exaggeration though.
Though I was happy to see Kodi and SPMC were compatible. Though SPMC is the only one which utilising the passthrough audio correctly. So I installed SPMC, and plugged in my external HDD and started updating. Now came another issue, I always delete the files via SPMC after watching, and set it to physically delete the file. This has worked on even the worst Android boxes, but on the Shield TV it didn’t. The app would “delete”, yet when I went back and updated, the show/movie came back. After some Googling I found this was a common problem for a lot of people.
I ended up installing one of the two FTP servers on the TV app store, and connected via FTP. Selected the file, delete, but just got back an error! This again was a widely reported issue, and I ended up having to install ES File Explorer (Ugh!) and delete the file that way. Finally I was able to do it. But this was after a couple of hours of research. That was one of the big nails in the coffin for me.
I even reported this to the NVIDIA support team, and they weren’t very helpful. I was passed around a lot, and was sent to level 2 support about 3 times, only to be told to do something I had initially told support I had done!
I am so glad I got the box with the remote, as I was getting annoying navigating around with the bulky controller. I would of liked the remote to be included, and the controller to be sold separately, though I can see why as there is the gaming element.
Now speaking of games, I was massively impressed with the SHIELD games app. There is a long list of games you can play, some for free and some have to be purchases, you check them all out here shield.nvidia.com/games/android
Playing Batman Arkham City, I didn’t notice a single bit of lag in the controls. They were quick and easy to pick up, and felt just like a console game. This alone is a great feature, and I would totally buy a lower priced box, if it just offered this feature and nothing else.
I was happy to see that the thumb sticks on the controller could act like a mouse, but only on some apps. This was my next issue, I use an app called TTorrent, as it does exactly what I want, but this cannot be navigated with the remote or the controller. So now I had to get a bluetooth mouse, which works, but I am now using 3 bloody controllers to navigate one box. Why not give the remote air mouse properties, and then everything would be great.
If they released just a console version of this, for £129 then I would probably buy it. But for what I used my Android boxes for, and how I use them, this box is just too restricted to work into my life. That’s not to say it won’t be awesome for the other 99% of the people out there, this is just my opinion.
http://droidhorizon.com/nvidia-shield-android-tv-box-review/
I cant tell you how many cuss word filled rants I've started typing in the google and nvidia feedback activities expressing many of these same feelings. Sometimes I even avoid messing with it altogether just to prevent the rage I feel about some of the implementations (or deliberate omittance of) by google who for whatever reason decided to cripple these devices with whatever nonsense ideas they have in their heads when they are making their decisions about what the "leanback" experience should be like. Maybe it makes a little sense to limit some parts of Android Auto but I cant believe what I'm seeing in my living room. Its absurd. Then I just delete it like a good end user and try to focus on the things that it does do really well. The device itself is awesome but being a tinkerer makes for a lot of frustration and it totally blows my mind seeing what I think is a perfect example of the direction I think google intends to take with the Android OS
Hi Guys,
This was previously posted in the assist forum but was recommended I try here.. I build custom automotive interiors and have in the past 5 years integrated dozens of android and ios systems into cars. I'm trying to figure out a way to skip all the fabrication of dash bezels by directly integrating into the existing factory lcd touch screens.
I would like to use the existing touch screen in my Ford Edge to interface with an android tablet.
Ideally I'd like to take an existing tablet or phone that I own (Galaxy tab 2 10.1 or Galaxy s4 phone) and send the touch and video information to my stock Ford Screen
CarPerformance .se has a kit that includes an android system with a board that switches the source being sent to the screen with the push of a button allowing you to switch between the Ford information screen, android computer with touchsceen interfacing and video inputs
below is a link to the install instructions and a video of its operation
carperformance.se/wp-content/uploads/2016/05/My-ford-touch-Android-install-manual.pdf
carperformance.se/?product=2001-2014-ford-edge-android-system
(links are broken because I'm too new to post links)
I would like to know if there is a prebuilt video switcher similar to the one above that would allow me to switch between sources and woulld allow me to connect one of my android devices
The reason I want to do this on my own instead of ordering the above product is that it runs older android software and does not have cellular capability.
if someone could point me to the right information I would greatly appreciate it as I'm sure these screens are fairly universal however I don't know what exactly to search.
Hello, I am looking for the same!
Have you been successful in your search of integrating Android into Ford? I have Lincoln MKX with older Sync 2 unit and really disappointed when found out that I won't be able to update to Sync 3 with Android Auto. Please let me know if you found anything good in this matter.
Thanks brother