Related
Hey guys!
I'm developing an android app. I want to use the sip api that android sdk provides to you. But after try with some examples I finally so that SIP api is not working in my mobile, so I google it and I found that samsung remove the SIP api on his devices.
So my question is, if anybody knows if it's possible to put the android sip api on my device?
If not I will use others open source midlewares. but I prefer to continue with android sip api.
Thanks.
Google Pushes Android Wear 2.0 Back To 2017, Issues Third Developer Beta
Google announced Android Wear 2.0 alongside what later became Android Nougat at Google I/O a few months ago, but aside from a second Wear 2.0 developer preview build in July, we haven't heard much since. There's good and bad news on that front: the good news is that Google is releasing a third Wear 2.0 developer preview today with some new features and tweaks. The bad news is that the final release of the software is being delayed.
Wear 2.0's release date has been pushed back from a vague "this fall" window to an equally vague "early 2017" window, presumably so Google can keep testing and tweaking. To that end, Google will release a fourth developer preview build, and the 2.0 update will begin trickling out to supported watches after that.
The biggest addition to the Android Wear Developer Preview 4 is a watch version of the Google Play store that can browse and download watch apps and watch faces without your phone—developers told Google that they wanted watch apps to be easier to find, and this is Google's answer. Text entry still looks painful, and relatively wimpy watch hardware may slow things down, but if the eventual goal is to make watches that can operate independently of phones, this is an important step.
The watch-exclusive store also means that developers can release watch apps that are totally independent of phone apps. Historically, Wear apps have been bundled in standard phone apps—download a phone app, and then the wearable app would be downloaded to the watch from the phone. Apps can still be downloaded and installed this way, but as of Wear 2.0 it will no longer be strictly necessary.
Other tweaks in the new preview build include permission requests for watch complications, a "recycler view" that lets developers display vertical lists of items in a way that will look good on square and round watch faces (the Wear 2.0 app picker uses the same view), and inline actions for new notifications (you would previously need to swipe down on a notification to expose a quick action menu).
Whether your new watch will receive Wear 2.0 is going to be up to its manufacturer, at least in part. The LGE Watch Urbane 2nd Edition and Huawei Watch are safe bets since they're still the only devices you can use to test these preview builds, but we already know that early Wear watches like the LG G Watch and first-generation Moto 360 will be missing out.
There's a toggle in Settings for NFC on LG Urbane 2nd LTE on Preview 3.
kalinskym said:
There's a toggle in Settings for NFC on LG Urbane 2nd LTE on Preview 3.
Click to expand...
Click to collapse
What does that really have to do with this article?
Just for the note: The setup wizard only finishes in the third developer preview if the system language of BOTH watch and phone are English (US). Did not test other english variants. It hangs at the setup screen if I select German for any of the devices.
Of course, you also need to join the beta group of the android wear compagnion app as stated in the install doc (Same symptom if not done).
Installing wear apps from normal android apps with embedded wear apps:
For windows users: see the post below (Thanks for the tool!).
Otherwise:
1. Enable developer options on wear device & adb access.
2. Download the normal android apk.
3. Open the apk with a zip tool.
4. Extract the wear apk from the folder that is referenced in "META-INF/MANIFEST.MF" (search for the string 'apk') in the apk file.
5. Connect the watch to your pc & grant adb access (if not done already).
6. In a shell / command promt type : "adb install <name-of-the-wear-apk>.apk" (Adb drivers & adb tools must be installed therefore).
Diewi said:
Just for the note: The setup wizard only finishes in the third developer preview if the system language of BOTH watch and phone are English (US). Did not test other english variants. It hangs at the setup screen if I select German for any of the devices.
Of course, you also need to join the beta group of the android wear compagnion app as stated in the install doc (Same symptom if not done).
Installing wear apps from normal android apps with embedded wear apps:
1. Enable developer options on wear device & adb access.
2. Download the normal android apk.
3. Open the apk with a zip tool.
4. Extract the wear apk from the folder "res/raw" in the apk file.
5. Connect the watch to your pc & grant adb access (if not done already).
6. In a shell / command promt type : "adb install <name-of-the-wear-apk>.apk" (Adb drivers & adb tools must be installed therefore).
Click to expand...
Click to collapse
for installing apps, you can use this
http://forum.xda-developers.com/huawei-watch/general/android-wear-2-0-apk-installer-t3472766
Hi,
I'm working for one company that makes eletric bikes. Currently we have an app which is used as extended dashboard for the bike and to control your bike when you are not using it. Now we are thinking of extending some of our functionality and one of our feature request would be to use Android Auto within our bike infotainment. My question is whether something like this is 'legit' (Can such an application be approved by Google) ?
Or to be more precise, here is user story request: "As a company that manufacturers e-bike solutions, we want to build bike infotainment that supports Android Auto, so that riders can run all apps that have Android Auto support on e-bike infotainment."
Thank you
If your e-bike application does not have a hidden collection of user information and sending packages to third parties, then you will be moderated by Google in the Play Market. Read about such applications on the thematic sites that are dedicated to e-bikes.
Recently I installed a double DIN Android 11 unit I picked up off Amazon. However, after a few days trying to get a feel for it, I’ll be returning it due to a laundry-list of reasons. Before attempting another model, I’d like to ask this community for their suggestions for a double DIN Android Auto Stereo.
Must-Have Features:
Physical volume knob. Physical "home" & "back" buttons are preferred, but not a deal-breaker.
Automatic screen dimming/brightening for ambient light levels.
Android Auto
Steering wheel control support
Backup Camera support
Budget: Up to $350 USD.
Android Auto Compatibility | Android
Android Auto works with hundreds of vehicles and aftermarket stereos. Check your compatibility here.
www.android.com
From the list of Google sanctioned stereos, what are you considering?
Or were you meaning generic chinese origin kanged android with unreliable pseudo/android auto.
marchnz said:
Android Auto Compatibility | Android
Android Auto works with hundreds of vehicles and aftermarket stereos. Check your compatibility here.
www.android.com
From the list of Google sanctioned stereos, what are you considering?
Or were you meaning generic chinese origin kanged android with unreliable pseudo/android auto.
Click to expand...
Click to collapse
Great list! I had no idea there was an official sanctioned list. Thanks for this. I had been swimming through all sorts of Chinese "android auto" clones, and getting frustrated with claimed compatibility which was totally bogus. I'll look into this list and see if I can isolate my selection a bit more.
Hi all,
I am a newbee, I am looking to develop firmware for Android Car Box, however I have no knowledge about this. I have experience developing fw for Android TV, but not with Android Car Box. I have tried to find out but there is not much information about it yet. I have a few questions that I hope someone can help answer with:
- Is the Android used for Android Car Box products a specific type of Android (such as Android TV, Android Mobile, Android Tablet,...). Or is it simply Android + Android Auto (service or app).
- Is there any difference between using Android Car Box and Android mobile (both use Android Auto to connect to DHU in the car)? If not different then Android Car Box is also using fw which is Android mobile right?
- About hardware, is there anything to pay attention to to build Android Car Box? (like CPU, RAM, ROM, ....)
Thanks everyone!