Related
BT Tag Writer is application that offers you way to add NFC pairing to your old Bluetooth speakers. NFC pairing allows you to pair, connect and disconnect the device just by tapping the NFC tag with your phone. This application is still under development and this thread can be used to request changes and new features for this application.
Market: https://market.android.com/details?id=fi.siika.bttagwriter
Video: http://www.youtube.com/watch?v=IbuLGsXIvKI
--- original first post ---
Hello everybody.
I have been now writing application for Android devices with NFC capabilities. It basically offers wizard interface for writing new NFC connectivity tags for your Bluetooth speaker(s)/headset(s)/etc. And software that will take care of the actual pairing/connecting, when you tap the tag with your phone. NFC pairing is something Nokia does with N9 and it's Bluetooth speakers, but it looks like Android still doesn't handle this well out-of-the-box. Also I still haven't found easy to use connectivity tag writers for any devices.
Sort demo of application in it's current state: Check youtube video kzoG5VM6VcU (can't have this as a proper link, as I only have less than 8 posts to this forum, sorry)
Before I release this software to market, I would like have some people testing it with their speakers and devices. I really hate alpha level software in market. If you have Galaxy Nexus, some sort of Bluetooth speaker(s)/headset(s) and hopefully some writable NFC tags, and you would like to help me to get this software tested: Please tell it here. I still have some small things to resolve before this is ready for closed testing. If you like to help me to get this tested please also tell what sort of Bluetooth device you have and what NFC tags you have available.
I will most likely release this software as free (gratis) and probably in open source (don't know the license yet). So I am not planning stealing your time and then making money out of it. Only thing I can offer to you is to add your name to application's thanks list.
Also if you know software that already does all this, please tell. If my software does not bring anything new, I have to redesign it little bit.
Thanks.
I'd like to test your app.
Got the same NFC-Chip like you (mi(d)fire or something like that I've bought for my old Nexus S) and a Nokia BH-504 Bluetooth Headset and for sure a Galaxy Nexus and a Galaxy S, too
Just tell me how I can help testing...
i would test as well buddy!
s60mike said:
I'd like to test your app.
Got the same NFC-Chip like you (mi(d)fire or something like that I've bought for my old Nexus S) and a Nokia BH-504 Bluetooth Headset and for sure a Galaxy Nexus and a Galaxy S, too
Just tell me how I can help testing...
Click to expand...
Click to collapse
For now this is ICS software, do you happen to have some unofficial 4.0 image in those? I kinda would like to make this 4.0 only software, as all NFC devices most likely will get that update.
S suxeN said:
i would test as well buddy!
Click to expand...
Click to collapse
Your phone is Nexus S? What sort of Bluetooth devices you have, and NFC tags...
I'd love to test this. I've been using NFC Task Launcher to do something similar but it doesn't currently support connecting to a specific device. I'm running ICS on a GSM Galaxy Nexus and have several A2DP speakers I could test with.
Northernmost said:
I'd love to test this. I've been using NFC Task Launcher to do something similar but it doesn't currently support connecting to a specific device. I'm running ICS on a GSM Galaxy Nexus and have several A2DP speakers I could test with.
Click to expand...
Click to collapse
I will fix few annoying things and then will put link to debug apk-file here (maybe Wednesday). I will try to see if I can make it run in 2.3.5+ too. Anyhow software will be limited to Mifare Ultralight tags (original and C versions). I have to buy other type tags to see what I can do with those, but that's later. Common Ndef writer classes does not work at all with Android or then I'm doing something wrong.
Android also really limits clean ways to do intents for more complex tags. So these tags software now writes are not proper connectivity handover tags. Just the core part of those is used and stored as single NDEF mime item and then this app is marked to handle those NDEF messages/records. Positive side with that is of course that information fits to smaller tags. Also PIN code storing will be probably done little hacky way to the first version.
alump said:
For now this is ICS software, do you happen to have some unofficial 4.0 image in those? I kinda would like to make this 4.0 only software, as all NFC devices most likely will get that update.
Your phone is Nexus S? What sort of Bluetooth devices you have, and NFC tags...
Click to expand...
Click to collapse
Like said above. Both devices got ICS and NFC and I've got Midfire NFC Tags...
s60mike said:
Like said above. Both devices got ICS and NFC and I've got Midfire NFC Tags...
Click to expand...
Click to collapse
So many different Mifare tags out there. Mifare Classics will not work (for now).
Anyway, pushed software to market after all. In few hours you should be able to find it from there. Offer still stays, if you can try it out and report issues here it would help. I had to drop headset support for now as it didn't work as well as I hoped.
Great! Will try it out today. Here's the market link https://market.android.com/details?id=fi.siika.bttagwriter
Sent from my Galaxy Nexus using Tapatalk
alump said:
Mifare Classics will not work (for now).
Click to expand...
Click to collapse
Missed that bit. I really must learn to read All the Mifare tags I have are Classic ones.
A couple of initial thoughts after myfirst use of the app...
1) Back when I was on 2.3.7 there was a Bluetooth A2DP widget I used (can't remember the exact name now) that, when you created the widget, would display a list of already paired devices that supported the A2DP profile. Once you'd picked one the widget would attempt to connect to it automatically.
I'd like to see your app do something similar rather than having to go through a pairing process with a device I've already paired with. It's a small thing to do I know, but I'd imagine most users will have already paired with their speakers before ever finding your app. I don't know if you can enumerate paired devices supporting the A2DP profile in ICS though.
2) When your app was scanning for BT devices it would find my speakers but would only display the BT address. It didn't display the BT device name after waiting for several seconds. This may be a BT stack problem though.
3) It looks very nice!
Northernmost said:
Missed that bit. I really must learn to read All the Mifare tags I have are Classic ones.
A couple of initial thoughts after myfirst use of the app...
1) ....I'd like to see your app do something similar rather than having to go through a pairing process with a device I've already paired with...
2) When your app was scanning for BT devices it would find my speakers but would only display the BT address. It didn't display the BT device name after waiting for several seconds. This may be a BT stack problem though.
Click to expand...
Click to collapse
1. Yes my app does not trust the already known devices list. Have to see if I can get that too. Anyway my application does not pair devices that have been paired already. It simply is stupid to not offer those. I have to check if I can used paired devices list too. I have to add some indicator to list what devices are then old known and what are just found with discovery.
2. I have seen "no name" issue only once. But yes, that's "stack problem"... I hope
Anyway I think I have to try to add Mifare Classic support first.
alump said:
1. Yes my app does not trust the already known devices list. Have to see if I can get that too. Anyway my application does not pair devices that have been paired already. It simply is stupid to not offer those. I have to check if I can used paired devices list too. I have to add some indicator to list what devices are then old known and what are just found with discovery.
Click to expand...
Click to collapse
Sorry for spam, but finally this will be mine 8th post
Request to list already paired devices is now added to Market version (0.3). So no need to turn already paired devices to pairing mode when writing tags.
Support for other than ultralight Mifare tags might take some time. Thanks to keys etc those tags are not ideal for this use. I think I will try to add headset support first.
Just to confirm that 0.3 is listing my paired A2DP devices
alump said:
Your phone is Nexus S? What sort of Bluetooth devices you have, and NFC tags...
Click to expand...
Click to collapse
Nexus S, running Brainmasters ICS 4.0.3
Bluetooth devices:
2 headsets
another Xperia ArcS
NFC Tag:
dont have a tag yet, but could get some. Dunno what kind they are!
S suxeN said:
NFC Tag:
dont have a tag yet, but could get some. Dunno what kind they are!
Click to expand...
Click to collapse
My unofficial NFC tag type list (from memory, might have mistakes)
Mifare Ultralight C is my recommendation. If you plan to use this for this, or for example: storing your contact information, storing some url, storing application starter information etc.... Simple, cheap and easy to use alternative.
Mifare Ultralight (non C) is too small for almost anything. You can use it anyhow with my software (limited features) and you can fit sort URL to it.
Mifare 1K, Classic, etc... these are for more secure needs. Or if you really want to store a lot more information to the tag. For non secure usage (e.g. my app) the secure features are just annoying extra that makes things more complex. Key based security so if you mess up with key, then you can't read or replace that data anymore. Also kinda "proprietary alternative".
Felicas are Sony's alternative for all these. Probably not easy to find outside Japan. Topaz is good alternative for Ultralights, but I don't know how well Android supports those currently (haven't tested). And if Broascom/Innovision still makes these? Not too easy to find anyway. And then there are many more... it's a total mess and maybe the main reason why it's so hard for NFC to break big time.
But for the most of use cases: I assume Mifare Ultralight C is the best alternative.
NFC Tag store examples:
TagAge - I'm using this, but mainly because I live in Finland.
NFCDog - is one UK alternative.
And many more, Google search is your friend. And this message has't been paid by either of these stores
alump said:
My unofficial NFC tag type list (from memory, might have mistakes)
Mifare Ultralight C is my recommendation. If you plan to use this for this, or for example: storing your contact information, storing some url, storing application starter information etc.... Simple, cheap and easy to use alternative.
Mifare Ultralight (non C) is too small for almost anything. You can use it anyhow with my software (limited features) and you can fit sort URL to it.
Mifare 1K, Classic, etc... these are for more secure needs. Or if you really want to store a lot more information to the tag. For non secure usage (e.g. my app) the secure features are just annoying extra that makes things more complex. Key based security so if you mess up with key, then you can't read or replace that data anymore. Also kinda "proprietary alternative".
Felicas are Sony's alternative for all these. Probably not easy to find outside Japan. Topaz is good alternative for Ultralights, but I don't know how well Android supports those currently (haven't tested). And if Broascom/Innovision still makes these? Not too easy to find anyway. And then there are many more... it's a total mess and maybe the main reason why it's so hard for NFC to break big time.
But for the most of use cases: I assume Mifare Ultralight C is the best alternative.
NFC Tag store examples:
TagAge - I'm using this, but mainly because I live in Finland.
NFCDog - is one UK alternative.
And many more, Google search is your friend. And this message has't been paid by either of these stores
Click to expand...
Click to collapse
Okay, ima gonna order some and report back to u
music auto start
is there a way to make it so that my music app doesn't auto play my most recently played track when the BT connection is made ... id like for it to simply open the app
Hello,
Currently i'm working on a personal project to integrate my GS3 into my car display and audio. Well this was easy with the help of a MHL or Allshare Cast Dongle.
My next goal was to install a 4 wire resistive touchscreen on my car display and use it as an external touchscreen control. I bought a 7" 4 wire resistive touchscreen with a USB module build around the CYPRESS CY7C63723C chip. I hooked up the touchscreen with OTG to test if there any initial reactions from my GS3, needless to say there wasn't any (no surprise there).
After a little digging around I came up with the conclusion that I need to create a custom "Input Device Configuration Files" for my touchscreen based on the following links
http://source.android.com/tech/input/touch-devices.html
http://source.android.com/tech/input/input-device-configuration-files.html
My initial question before I start plugging away with some codes is how would I name the files, the documents states "Input device configuration files are located by USB vendor, product (and optionally version) id or by input device name." How would I find the product ID or the input device name for the touchscreen? I'm sure this can be done thru terminal or something but I am new to android development so cut me a little slack here
Also if you know of any Input device configuration files dealing with touchscreen please post it.
Anyone?
hechen said:
Anyone?
Click to expand...
Click to collapse
You would probably be better served asking this on one of the more general hacking sub forums. Here, you're just going to get people who are familiar with the S3. There, you may find someone who has done something similar on another phone.
hechen said:
Anyone?
Click to expand...
Click to collapse
Any resolution with this?
I have been pondering the idea as well, but have no coding or hacking experience to go off of.
Would love to hear about the progress for this project and maybe a writeup of parts and procedures so far.
In short:
- It looks amazing on the wrist and it's worth the price and desire only for this "feature" (I have the silver version).
- It's so confortable you forget you wear it.
- As of now you can't do any useful things with it. The heart rate monitor barely works when you stand still, let alone when you move. It's just for fun and conversation. My LG G2 notification LED is so powerful that it can communicate more things than the watch can.
- It's just a lame remote for the phone right now.
What is needed (mostly from Androir Wear):
- Canned responses, easily accessible and sortable.
- Different vibration patterns depending on notification type (API ?)
- Standalone Wi-Fi functioning (as I understand, the Moto 360 has the Wi-Fi hardware)
- More open API to enable more powerful applications
- I think it's possible to type on the watch, but Google just needs to let developers try it in an official way
Hopefully the Apple Watch approach with powerful applications residing on the watch will "inspire" the Android Wear team to enable more stand-alone functionality.
That's about it. I like the hardware a lot, but the software is in its infancy. I think Samsung's Tizen approach is appropriate at this time, given how limited the Android Wear is.
kevinlevrone said:
In short:
- It looks amazing on the wrist and it's worth the price and desire only for this "feature" (I have the silver version).
- It's so confortable you forget you wear it.
- As of now you can't do any useful things with it. It's just for fun and conversation. My LG G2 notification LED is so powerful that it can communicate more things that the watch can.
- It's just a lame remote for the phone right now.
What is needed (mostly from Androir Wear):
- Canned responses, easily accessible and sortable.
- Different vibration patterns depending on notification type (API ?)
- Standalone Wi-Fi functioning (as I understand, the Moto 360 has the Wi-Fi hardware)
- More open API to enable more powerful applications
- I think it's possible to type on the watch, but Google just needs to let developers try it in an official way
Hopefully the Apple Watch approach with powerful applications residing on the watch will "inspire" the Android Wear team to enable more stand-alone functionality.
That's about it. I like the hardware a lot, but the software is in its infancy. I think Samsung's Tizen approach is appropriate at this time, given how limited the Android Wear is.
Click to expand...
Click to collapse
disagree with the "can't do anything useful" comment...
use autovoice, tasker and google search api and the possibilities are limited to what tasker can do (almost limitless). requires root and a little work, but i now have my watch running tasker tasks including controlling my home automation system... i feel like james bond. "ok, google. flush toilet!"
can't wait for android L
Nub question. What's API ?
Will we see upgrades with Wear 2.0/ Android L?
I'm expecting my watch by the 15th...the wait is killing me.
gerg004 said:
Nub question. What's API ?
Click to expand...
Click to collapse
http://lmgtfy.com/?q=API
Wiley_11 said:
http://lmgtfy.com/?q=API
Click to expand...
Click to collapse
Thank you, sir.
I mean, Troll*.
kevinlevrone said:
In short:
- Canned responses, easily accessible and sortable.
Click to expand...
Click to collapse
I agree that they should be sortable, but it has canned responses.
Tap reply to a text or email, instead of speaking, swipe up.
Yes
No
OK
Hehe
Thanks
I Agree
Nice
On my Way
OK, Let me get back to you later
vansmack said:
Tap reply to a text or email, instead of speaking, swipe up.
Yes
No
OK
Hehe
Thanks
I Agree
Nice
On my Way
OK, Let me get back to you later
Click to expand...
Click to collapse
Thanks ! I just didn't realize that this feature was already available. I withdraw 50% of the criticisms Now I just need to find a way to add my own responses (edit: I think I just read that this feature will be available in the upcoming Android L).
Hi,
Sorry, I had already posted this on another section but I think this one is more appropriate and can't delete other post.
I have a Joying JY-NL124 android car radio, which does not have an accelerometer. I bought the Yocto 3d V2 http://www.yoctopuce.com/EN/products/usb-position-sensors/yocto-3d-v2 to see if I could get it to work with torque and other android apps for the track but although android sees the device the apps do not. I am not a programmer, but is there a way to get the apps to recognize an external accelerometer like some do for an external GPS?
Very interesting. I would like to know as well. It might also be usefull in navigation to get a faster direction orientation.
I was reading up on this again and this bit means someone with the know how would probably need to code something
The main advantage of this solution is that you don't need to install a driver to communicate with a Yoctopuce module, as the HID layer is always present. You only need to add our library, that we provide in source form, to your driving software for it to be able to directly talk to Yoctopuce modules.
Click to expand...
Click to collapse
Have you tried contacting them directly and asking if they can do this for you?
sinnedone said:
I was reading up on this again and this bit means someone with the know how would probably need to code something
Have you tried contacting them directly and asking if they can do this for you?
Click to expand...
Click to collapse
Uff, sorry for the late reply. Life has a way of getting in the way of interesting projects. I'm about to restart this project since I'm using the car a lot on the track. It's weird that the units don't come witha compass, gyroscope, accelerometer, etc, considering they are meant to be used in moving vehicles.
Definitely post up if you figure it out.
It would be nice to get it to work with Android as a whole. If that's the case you might need to talk to one of the ROM developers to see if it's something they can do ROM wise or even a custom kernel.(the kernel bit might be a little harder)
Did anybody get this right. It would be cool if these usb accelerometer could work in the apps
flash_xx said:
Hi,
Sorry, I had already posted this on another section but I think this one is more appropriate and can't delete other post.
I have a Joying JY-NL124 android car radio, which does not have an accelerometer. I bought the Yocto 3d V2 http://www.yoctopuce.com/EN/products/usb-position-sensors/yocto-3d-v2 to see if I could get it to work with torque and other android apps for the track but although android sees the device the apps do not. I am not a programmer, but is there a way to get the apps to recognize an external accelerometer like some do for an external GPS?
Click to expand...
Click to collapse
I'm very interested to understand whether this is possible as I am thinking about a similar setup. You tried the three Bluetooth tips in the roll up thread?
https://forum.xda-developers.com/an...roll-joying-2gb-sofia-mtcb-mtcd-tips-t3555249
"Bluetooth Tethering & BT Settings", "Difficult to pair BT devices" and "Modified stock bluetooth app to allow connection to all devices"
Have you tried external GPS for higher refresh rates or is the Head Unit gps refresh good enough for the track?
Bob
MX5DrIver said:
I'm very interested to understand whether this is possible as I am thinking about a similar setup. You tried the three Bluetooth tips in the roll up thread?
https://forum.xda-developers.com/an...roll-joying-2gb-sofia-mtcb-mtcd-tips-t3555249
"Bluetooth Tethering & BT Settings", "Difficult to pair BT devices" and "Modified stock bluetooth app to allow connection to all devices"
Have you tried external GPS for higher refresh rates or is the Head Unit gps refresh good enough for the track?
Bob
Click to expand...
Click to collapse
Sorry....USB not Bluetooth... Also discouraging. I was hoping USB would be an alternative to BT for track add-ons...
I too have an Android head unit and do track days, and have the exact same interest as you. I use Harry's Lap Timer. I have the Pumpkin AE0273B head unit. It too lacks the compass and accelerometer. I too found this to be a very unfortunate omission.
I have developed apps actually so I do know Android program to some degree (although I am sortof a hack, not a pro). I have apps on the Play Store (since I can't post links just search Play Store for developer JimRoal). I saw the Yocto stuff. When I get some time I will look into this some more.
Any update on this? Would also like to add a compass / accelerometer to my joying.
Also interested. But on a newer 10.0 unit. Something I am going to look into.
nFiniti said:
Also interested. But on a newer 10.0 unit. Something I am going to look into.
Click to expand...
Click to collapse
Sad that over 4 years after I first posted this we still don't have a unit with these features. I finally gave up and bought an AIM Solo 2 DL.
I'm looking for a newer radio though, since mine is older than this thread
Still waiting as well.
Looking forward for solution, we have also WIMOTION sensors in the market with sample android apk but I'm not a developser so, put things together is hard for me !
I think the hard job is try to mock the sensors in Android AS IF external accelerometer was factory embeeded (allowing apps to recognize it)
Nothing new about this project / idea ???
?? dead ???
mariodantas said:
?? dead ???
Click to expand...
Click to collapse
Once you've figured out how to modify the kernel, you should be good to go!
Another option could be sensor to serial over USB, via a compatible adapter, write an app and there you go. Of course it won't be standard Android though.
Drivers are here
https://elixir.bootlin.com/linux/v4.14.133/source/drivers/iio/imu/st_lsm6dsx
The problem is adding them to kernel !
You dont need to add them to the kernel. You will need to implement an Android HAL that can read the values of these sensors. Its not a trivial task but also not very hard if you have access to the source code
I'm currently owning a MTCE device. I'm a software developer (.NET). I'm a design and UX fetishist.
I see many folks of you have posted different apps, skins, mods, a.s.o. to get the best out of the headunit that is possible.
One problem I have seen is, that if I want to have a full working headunit, I will have to read thousand of forum-posts, try hundreds of software and then get stuck by a few apps that design is not fitting together.
Why isn't it possible, to join the forces to make a fully working ROM with preinstalled software that looks as if it was designed and made by the manufacturer? One design (maybe skinnable), one UX, selectable apps. So a newbie (like me) will get a fully functional headunit (including the basics like radio, DAB, mediaplayer, navigation, ...) that looks like factory-made with installing only the ROM.
Modern cars already have a well working headunit that has a seamless UI and UX between the different functions. Why shouldn't this be possible on our headunits?
I would suggest, that all of you developers, skinners, modders, should join your forces and create an experience for our headunits that will outreach the currently built-in headunits of modern cars.
What's wrong with hal9k or malaysk mod? They are fully working and in my opinion are better than original head unit from my car. You can even use google assistant, so you can control everything by your voice.
Maybe my mods will suit your needs?
Have a look at my channel:
https://www.youtube.com/user/KoTiX71
RolandE1204 said:
I'm currently owning a MTCE device. I'm a software developer (.NET). I'm a design and UX fetishist.
I see many folks of you have posted different apps, skins, mods, a.s.o. to get the best out of the headunit that is possible.
One problem I have seen is, that if I want to have a full working headunit, I will have to read thousand of forum-posts, try hundreds of software and then get stuck by a few apps that design is not fitting together.
Why isn't it possible, to join the forces to make a fully working ROM with preinstalled software that looks as if it was designed and made by the manufacturer? One design (maybe skinnable), one UX, selectable apps. So a newbie (like me) will get a fully functional headunit (including the basics like radio, DAB, mediaplayer, navigation, ...) that looks like factory-made with installing only the ROM.
Modern cars already have a well working headunit that has a seamless UI and UX between the different functions. Why shouldn't this be possible on our headunits?
I would suggest, that all of you developers, skinners, modders, should join your forces and create an experience for our headunits that will outreach the currently built-in headunits of modern cars.
Click to expand...
Click to collapse
I exactly know what you are talking about.
Whether malaysk nor Hal9k are the greatest thing since sliced bread and do not fulfill what I and you @RolandE1204 are expecting.
A common UI with same buttons and same background, coordinated in function and visibility would be awsome.
...but..... and now we have the main issue:
All firmware are made of apps from different developers and are just bundled in the firmware. This leads automatically to different UI for each single app.
You won´t get a navigation app which fits any other UI. You won´t get a player app fitting the UI of your launcher. If you would want this, each single app needs to get developed or at least adapted to a UI.... None will do that and as far as I know there is no possibility to create a common UI which adapts 3rd party applications. Each app has it´s own one.
This is one of the benefits of an OEM unit. There you have to pay a lot more and it is not configurable at all, because it is completely closed.... but with a common interface...
That's right ... but does it have to be like that?
@rigattoni You're absolutely correct. But does it have to be this way? Here at xda-developers are all the guys (and girls) that do the best work like malaysk, hal and many others that do very great work.
With a little more work together, there could be a complete solution that would not also work but also look great.
I may think too simple but there has to be a design and UX guideline, that has to be created and every application that will be developed using this guideline, will fit nearly seamless into the bundle of all other apps.
Also I'm sure that there are also som people like me, owning a slightly older car that hasn't built in a headunit with such functions. I like my car (Peugeot 308CC) and would buy it again but I wanted to add functionality that hasn't been in (rear drive camera, good working navigation, ...).
Just to clarify: I'm not searching for a free solution and I understand that this means a lot of work that can mainly be done by enthusiasts, but I'm also willing to pay for a solution that works and looks like a charm. So I think that even if we are talking about different applications that work together seamless, I am sure that there are people like me, who are willing to pay money for this.
I'm currently living with a mediaplayer (poweramp [blue]) that has a different behaviour and look like the radio (stock [black/white]) and a navigation app (magic earth [orange]) that also doesn't fit in. Other applications (TPMS, Bluetooth-Calling, Car-Status) are also looking very different.
I know that there are persons doing great work in modifying roms and apps but they all have their different design-language. So why not using a centralized design and UX language and creating a bundle of software that makes every owner of an android headunit as proud as he can be?
Do we get these devs together to work on one version with a common UI?
I would love everything to look similar, but I would settle for great looking apps that look different. Like that guy who posted the youtube link - nice radio app, but would look for a different music app
kmlnvm said:
What's wrong with hal9k or malaysk mod? They are fully working and in my opinion are better than original head unit from my car. You can even use google assistant, so you can control everything by your voice.
Click to expand...
Click to collapse
Yes, confused, malysk and hal9k are already this way. Perhaps OP wants to define look and feel.
Perhaps too, OP might not understand that source code to the MTCD units has not been released and that to a large extent work is by reverse engineering?
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
rigattoni said:
Do we get these devs together to work on one version with a common UI?
Click to expand...
Click to collapse
Sure, how would you do that?
@marchnz: It was just a question. Nothing else to be interpreted into this question...
I'm aware
@marchnz: I'm aware that reverse engineering is hard work. I've already done this by myself (as I said, I'm a .NET developer).
I'm not into developing android software but I'm sure it is a lot of work too.
As long as I do have the commitment of some developers that they want to follow design guidelines, I'm able to create some. What I don't want to do is, to create guidelines that nobody is considering. Also I do not want to patronize someone. So if someone commits that he wants to use guidelines and has a definitive app in mind he wants to work on, we can work out guidelines.
Maybe first of all invite some developers:
@jamal2367
@Malaysk
@Hal9k_
@mike.b
@f1x
im sorry I didnt get your meaning
whats the plan?
i'm a developer I mean what are we going to do?
can you explain more clear?
What has to be done is to unify the UI and UX of all the major apps that are needed.
The best would even be to make them skinnable.
So there is a need to create a common UI for
- Radio
- Media-Player
- Bluetooth (Calling)
- Vehicle (Doors, Trunk, ...)
What I already can say is, that there will be a skinnable version of magic earth (navigation) in the near future.
Also it would be nice if during this process, some smaller issues of a software can be fixed. (ie. Radio looses the station-names on reboot and only shows frequencies)
Anyone who will contribute on this project, please leave a message or send me a PM.
RolandE1204 said:
What has to be done is to unify the UI and UX of all the major apps that are needed.
The best would even be to make them skinnable.
So there is a need to create a common UI for
- Radio
- Media-Player
- Bluetooth (Calling)
- Vehicle (Doors, Trunk, ...)
What I already can say is, that there will be a skinnable version of magic earth (navigation) in the near future.
Also it would be nice if during this process, some smaller issues of a software can be fixed. (ie. Radio looses the station-names on reboot and only shows frequencies)
Anyone who will contribute on this project, please leave a message or send me a PM.
Click to expand...
Click to collapse
Hey
If you are interested in a radio player that runs over the internet then have a look here!
GitHub: https://github.com/jamal2362/URL-Radio
Download: https://jamal2367.org/downloads/?dir=Apps/URL Radio
You could install it on your mobile phone and use the app in landscape format and see what it looks like on the MTCE.
jamal2367 said:
Hey
If you are interested in a radio player that runs over the internet then have a look here!
GitHub: https://github.com/jamal2362/URL-Radio
Download: https://jamal2367.org/downloads/?dir=Apps/URL Radio
You could install it on your mobile phone and use the app in landscape format and see what it looks like on the MTCE.
Click to expand...
Click to collapse
I've never written about a radio that works over the internet.