Simply, android.os.Build.MODEL information and others on Chromebook is needed.
I am managing 3rd party library which is used for several published games, with totally not considered run on Chromebook.
Some of my customers asked me to want to know my library's Chromebook compatibility because they are getting some CS from there end-users.
I don't have Chromebook now, but My library reports some data to monitor crash or ANR, etc.
I could not find any device information from which can specify the log came from Chrome OS or Chromebook devices which listed on Google`s Chromebook list. (https://www.chromium.org/chromium-os/chrome-os-systems-supporting-android-apps)
Anyone can share with me what kinds of device model information and OS version is shown when the Android app launched on Chromebook?
Here you go:
How to detect programmatically if "Android App" is running in chrome book or in Android phone
context.getPackageManager().hasSystemFeature("org.chromium.arc.device_management");
Related
I'm creating a flutter app that will be installed on a Samsung Galaxy 7-inch Tablet with Android KitKat (v4.4). It will be the only app on the tablet, and will be implemented such that it loads when the device is powered up, and the user will be unable to exit the application.
I've found this on the Android Developer docs, but it only applies for versions 5.0 and over.
https://developer.android.com/work/dpc/dedicated-devices/lock-task-mode#java
I have not been able to find any documentation/tutorials that could possibly assist with this, without using a 3rd party application such as Surelock and Kioware.
Is there a way to implement the above for older Android version (in my case for version 4.4)? Thank you.
As you are targeting an older Android version you will need to implement some workarounds, but luckily there is a very extensive tutorial on how to do just that for Android 4 which you can find here:
http://web.archive.org/web/20201101145703/https://www.andreasschrade.com/2015/02/16/android-tutorial-how-to-create-a-kiosk-mode-in-android/
As this is very platform specific you will need to develop directly for Android and then connect it to your Dart code with this tutorial.
If you control the devices your software will be installed on, you can also opt for the 'root' way of doing things which is described here:
Enabling KioskMode in Android 4.4.2 with Root
I'm working in a company building Android-based IVI system for Tier1/OEM/aftermarket. Before the release of Android Automotive OS, we ported Android for Phone on IVI hardware and do customizations to bring in vehicle-related features like rear view camera, HVAC control, BT music, navigation, steering wheel control, etc. At that time, our products didn't need to be certified by Google and we could choose whether to test CTS or not. But with Android Automotive OS, I'm not sure if the CTS test should be carried out and the report must be sent to Google for certification, or even integrate GMS?
In the latest Android CDD document: https://source.android.com/compatibility/android-cdd.pdf. I can see that there are some hardware and software requirements for Automotive devices. But I can't find any further information about what exactly should be conformed before shipping a vehicle with Android Automotive OS based IVI in different countries.
Looking forward to any tips & info. Thanks a lot!
BR
It is still the same way you did for your last project.
I would say it up to you.
There is nothing diferences until now for what we called Android Automotive OS..
There is no "Android Automotive OS" actually .. it is simply Android PLUS some added service , Vehicle HAL, CarService
So nothing special... Android still violate many Automotive requirement regrading safety and Performance. That why many OEM like GM have to customize alot of things on top Android
Basically if your IVI contain Android Auto certification then you need to do CTS and other stuff to make Google say YES if not... then Who care...
i know it might be the same as this question. i am from the philippines as well but the phone mentioned in that link is a samsung which is an internationally well-known brand and i know that adb supports that brand. what i am planning and really want to buy is this locally known phone. it got a really nice specs but i am worrying that i might not be able to use it on app development. i found adb drivers on the net and installed it but i don't know how to use them with android studio. the reason why i want to use a phone for development is because my laptop slows down with i run android studio and the emulator at the same time. if some co-pinoy already know a phone that they already used for app development within the same price range of flare x, please let me know. please guys i really need help on this matter.
Any phone that allows you to enable USB-Debugging will be suitable for android development. Most developers try to stick to a phone that has a clean Android base like a Nexus or Moto X, as it rules out any interference with vendor specific changes to Android (like Samsungs TouchWiz).
See this page for further information on using a hardware device for development. Google does not recommend any specific device.
Also see this list for device vendors providing ADB drivers. If you want to play it safe, stick to these vendors.
This download page suggests that the Google provided driver is suitable for the Cherry Mobile Flare X too.
I am new to android development, i created some applications and published in android market place. I am facing issues with some devices like AT&T and Sprint android devices that these devices are unable to find my application in android market.
Can any one tell me why these devices are not able to find my app from the android market?
Any help will be appreciated.
Thanks,
Sathish.
What do your apps do?
You should read and understand Market filtering.
In a nutshell, it seems likely that those devices that cannot see your apps are either unable to run your app (so they never see it), or the carrier has modified the firmware image or market experience to prevent installation of some types of app.
I've recently purchased Samsung Galaxy Android phone after using Openmoko phone for 2 years.
One of the reasons for choosing Android was is that it's open sourced.
I don't want to depend on phone maker to provide updates for my phone. I'd like to do it myself.
Right now I'm in research stage if it's worth the time or not. So here are the questions:
I found some tutorials for building ROM images from source. They tell that Android build script will ask for make of the phone before building kernel. Does it mean that all the phone specific stuff is handled by the script or I will have to do some voodoo before I can flash it onto my phone?
Drivers. How are they handled? Are they included in the source as binaries and added automatically (question 1) or will I have to dissect old firmware to get them and put in my build? I realize that would mean some problems with module/kernel versions compatibility.
Is there is something I'm not aware of that would prevent me from building my custom firmware or make it very time-consuming?
I'm not afraid of installing SDK's and toolchains, after all I'm an Openmoko owner.
It's gonna be a little more complicated than that.
On any consumer Android phones I've seen, the user doesn't have root access to the OS. So step one, would be finding an exploit to get root.
Even after you get root, all consumer Android phones "lock" the bootloader to prevent unauthorized OS images from being booted.
The Android OpenSource project only contains device drivers for a small number of phones (Google dev phones, possibly the Nexus One?). For other phones, the drivers are proprietary binaries that the manufacturer loads on the phone. They generally aren't available separately.
Even with all of those obstacles, some enterprising smart guys have managed to create custom "ROM's" that blend the OpenSource release with drivers ripped OEM install on the phone, etc. CyanogenMod is one of the best known and is available for several different Android devices, but unfortunately the Samsung Galaxy does not currently appear to be one of the device supported by Cyanogen.
I found an old link here to a guide to getting root on the Galaxy and loading a custom ROM on it, but unfortunately the ROM they link to doesn't seem to be actively maintained anymore. It might be worth doing some more exhaustive google searches to see if you can find anyone doing active development on the Galaxy.