Hi,
I would like to request a feature which I think would be real help either on XDA-developers.com or wiki.xda-developers.com[
There is an excellent matrix of differences between the different HTC models & the names different phone providers give them.
I've tried using searching terms like 'comparison' or 'differences' (between XDA's) to find it, but the search engine does not seem to be speaking my language.
1.
I think having a better main page hotlink to such a comparison Matrix would be REALLy helpful, PARTICULARLY as the matrix is (hopefully) updated regularly and has lots of hotlinks to the various models.
2.
The second request is to somehow display details in a list of phones as they are released so that I can see whether the XDA I'm waiting for (or similar) has been released.
Thanks for an EXCELLENT site
The video is up today if you'd like to follow along, otherwise download the source and learn how to use a JSON API and Bind Controls and use Static Resources, GZip Requests vs WebClient and how to easily make a Panorama App.
Questions? Want to see a certain thing created? Tell me!
Please put a direct link for this in the video, it is not obvious where to search for it, and vice versa.
Also I have some comments for your video:
I really really dislike that you call your variables stuff like TheSource rather than describing the variable with what the actual source is. So if it is a Source with Friends, I would call it FriendSource.
You also have other bad and inconsistent naming conventions throughout your sample.
You also assume a lot of things in your video when explaining things. Such as the viewer knows what the data contract is that you are using and how you generated it, or from where you found out what properties it had to contain. You also didn't really explained what the Data Contract deserialization did, which can be very confusing to people and they would probably think: "What is this black magic?!".
Though I don't necessary think that stuff like this should be a part of the video, otherwise it would be super long, but it would not hurt posting links to where to find more information about these things. These things are not as obvious to new developers as they are to you.
This might seem as a lot of criticism, but you are doing better and better on the videos!
Thanks for this. Im writing a few json apps will no doubt help me with best practice
WP7: JSON & BINDING (Episode 3)
http://www.xda-developers.com/windo...art-3-oauth-tokens-and-json-xda-developer-tv/
Cheesebaron said:
Please put a direct link for this in the video, it is not obvious where to search for it, and vice versa.
Also I have some comments for your video:
I really really dislike that you call your variables stuff like TheSource rather than describing the variable with what the actual source is. So if it is a Source with Friends, I would call it FriendSource.
You also have other bad and inconsistent naming conventions throughout your sample.
You also assume a lot of things in your video when explaining things. Such as the viewer knows what the data contract is that you are using and how you generated it, or from where you found out what properties it had to contain. You also didn't really explained what the Data Contract deserialization did, which can be very confusing to people and they would probably think: "What is this black magic?!".
Though I don't necessary think that stuff like this should be a part of the video, otherwise it would be super long, but it would not hurt posting links to where to find more information about these things. These things are not as obvious to new developers as they are to you.
This might seem as a lot of criticism, but you are doing better and better on the videos!
Click to expand...
Click to collapse
Hello
I would first like to thank you for your feedback and appreciate your suggestions and will definitely take note and ensure I am more specific on strings and item controls. Our next video was actually on how to make Classes for your JSON API (except now it's on Maps/Nokia Drive + New WP Apps/News) but I get maybe 8 Mins for actual video, 30s for Intro and max ideally 10Min for the whole video. So, can't put everything in, I wish but I will surely alert everyone if they don't know how to do it to visit a specific site or wait for the next video. I will definitely keep these items in mind.
As for my videos, that's nice of you to say. We're actually going to be throwing in stuff besides programming & review our forums WP Apps and talk about them as well as any news like the others with Android. If you have any suggestions, happy to hear them and give you credit.
Thank you again for all the feedback!
- Lance
meandu229 said:
Thanks for this. Im writing a few json apps will no doubt help me with best practice
Click to expand...
Click to collapse
I am so happy to hear that! That's great to hear. One more video coming around JSON actually, might be even more helpful to you.
Keep me informed about your App, I would also like to talk about it when you're done.
- Lance
I know this has already been discussed in several threads, but none of them go further than just stating that it doesn't work. I'm talking about external mic support on the OnePlus 3's best video recording apps: OnePlus cam and Gcam. All alternatives are far inferior, but if you know any, please tell me (including voice recording apps that can record while filming).
I'm a total noob at making/modding apps, but I've go so far as to having converted the apks to java source code (or as close as dex2jar can get it. It just seems so simple to change from TYPE_BUILTIN_MIC to TYPE_WIRED_HEADSET with setPreferredDevice() in the interface AudioRouting. But that isn't the case, and I would like to ask if OnePlus cam and Gcam just have different names for these thing and it still would be quite easy to change, or if it's so entangled and proprietary that it's impossible. I have the java code for reference, but not sure if it's against the rules to upload even thought they're free apps.
Does anyone have experience with this and can help me/try and mod the apks?
Here's some files with audio in their names (is this where to look and if so, which?):
OnePlus cam:
AudioAttributesCompatApi21.class
AudioAttributesCompat.class
AudioManagerImpl.class
AudioManager.class
AudioManagerBuilder.class
Gcam:
AudioFrameProvider.class
AudioSample.class
AudioFrameConsumer.class
AudioTrackDecoder.class
In addition to the there are also files with names like: ExternalMediaSource.. MediaDecoderSource.. TrackDecoder..
Thanks in advance - ASH19
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.
Face Designer:
https://developer.huawei.com/consumer/en/doc/30114
Guide:
https://developer.huawei.com/consumer/en/doc/5050304
Thanks,
played a bit, but seems quite buggy (or not the latest beta version?).
I can't open the standard examples provided.
And didn't make work simple infos as steps/heartbeat.
Hello,
which examples are you talking about? I downloaded the watch face designer from here: https://developer.huawei.com/consumer/en/doc/distribution/content/themes-design-tools
No examples contained. But I am having problems finding features. I suppose, they forgot some data types in this version. I cannot add the unread-messages feature into the watch face. It's simply not available. In a previous beta version it was. But the project (designer UI structure) and xml file structure changed.
That's why I'd like to have some working examples, too. Maybe I can learn something from them.
Shaker1978 said:
Hello,
which examples are you talking about? I downloaded the watch face designer from here: https://developer.huawei.com/consumer/en/doc/distribution/content/themes-design-tools
No examples contained. But I am having problems finding features. I suppose, they forgot some data types in this version. I cannot add the unread-messages feature into the watch face. It's simply not available. In a previous beta version it was. But the project (designer UI structure) and xml file structure changed.
That's why I'd like to have some working examples, too. Maybe I can learn something from them.
Click to expand...
Click to collapse
on the official site they give a sample - the one in the attachment - I'm struggling too in order to make it work
Golem_ said:
on the official site they give a sample - the one in the attachment - I'm struggling too in order to make it work
Click to expand...
Click to collapse
Stop struggeling, something in the project files must have changed, so that they became incompatible. Personally I don't need those examples anymore, since the most recent version of the designer now works. I don't need to analyze anything, except for configurable widgets. But I doubt, these are in the examples.
Shaker1978 said:
Stop struggeling, something in the project files must have changed, so that they became incompatible. Personally I don't need those examples anymore, since the most recent version of the designer now works. I don't need to analyze anything, except for configurable widgets. But I doubt, these are in the examples.
Click to expand...
Click to collapse
Yes, you're right, since then already I've created few working projects that are now installed on my watch