Anyone have a clue as to how to get the processor id or serial number or anything relevant for asset tracking from an XDA via an API. Compaq has an API to get at this stuff. Ideas? Anyone?
Related
Hello,
I would like to develop an application that makes use of the accelerometer sensor on an Android smartphone.
My app needs a measurement range of +-4g. I looked for accelerometer hardware specifications for various models and found that Nexus One mounts BMA150 by Bosch Sensortec, which supports three ranges (+-2g/+-4g/+-8g).
While browsing Android source code from Nexus One, looking for bma150 driver, I read this issue:
code.google.com/p/android/issues/detail?id=8143
I wish to modify the bma150 driver to set a default range of +-4g and then write a Java app to get and use data from the sensor. By the way, as far as I understand, the driver is actually not implemented at all. Or it is just not exported to the Java API? However, if it is not implemented at all, how can the OS change the screen orientation when the user rotates the device? And if it is not exported to the Java API, what would actually happen when an app tries to read data from the sensor?
Thank you for your help,
Nhexus
Using the accelerometer is pretty easy from the SDK, just google for "android accelerometer" you'll get loads of examples, like:
http://stuffthathappens.com/blog/2009/03/15/android-accelerometer/
Note the "onAccuracyChanged" method, I think the ranges/accuracy depend on the magnitude of the forces currently applied.
Hope that helps.
Thanks for the answer. I'd already had a look at the Sensor API in Android.
I was trying to understand a bit more about the driver that actually stands behind the Java API. I thought that the measurement range could be set via software (maybe via i2c communication with the device) and that it is not dynamically adapted.
However, I'm not an expert in the Android Open Source Project, so I don't clearly understand the source code structure and design. Maybe someone with an in-depth knowledge of HAL and drivers could give me some hints.
Thank you again for you help!
When I get handed a new and previously unknown Android device (typically from a minor player), is there a way to figure out which components it is made of, such as the SoC, the flash chip, the RAM type etc. (Assuming noone else has posted the info of cause)?
In other words are there any tools (other than a screwdriver) for finding this out directly from the device, preferably without rooting (as some of this info may be needed to pick a rooting method...)?
It's really hard to find detailed information for the entire hardware of a phone on a single tool..I recommend System Info Droid or Android System Info which work fine for me(you can get them on Google Play for free)..However, a google search on a specific device will cetainly provide you with more elaborate specifications..
Use Z-DeviceTest from Google Play
Sent from my LT28h using xda premium
Hi guys,
My first time here so if this is the wrong place (I have a strong feeling that this might be true) feel free to move/remove it.
I was trying to build a simple app for android. I'm suing Qt5.4 with qtcreator. This app is meant to calculate some properties of steam (engineering stuff). This app links to a library called freesteam, which in terms links to the GNU Scientifc Library I believe. It runs fine when build for desktop but when using the android for armeabi-v7a it fails with an error saying: "#error Bionic header ctype.h does not define either _U nor _CTYPE_U" .
I was told that this problem is not related to Qt so I started digging around the internet and found out that this might have something to do with some ctype_base.h and ctpye.h from NDK not being in sync (?) with the bionic version of ctype.h.
Any ideas of how I might go about solving this issue?
Thank you for your time and/or any replies.
Have you built the GNU SL with NDK for Android?
Good day!
In learning objectives I am developing desktop app that must reproduce the behavior of one of the social network's client app on android.
This android app makes several POST-request to android.clients.google .com/c2dm/register3 to confirm that this is real mobile app and to confirm it's API token, then it uses the response from this /c2dm/register3 request as one of the params for refresh token request.
So there is no problem with reverse-engineering social network's client app and using it's private API, but I stuck with implementing this request.
When trying to reproduce the same request intercepted from my mobile app I obtain response
"Error=|ID|3|HONE_REGISTRATION_ERROR"
Click to expand...
Click to collapse
The request headers and data example here (I replace some data with ?? symbols):
POST htt ps: //android.clients.google. com/c2dm/register3 ← 200 OK text/plain 57b 202ms
Headers:
-----------
Connection: keep-alive
Accept-Encoding: gzip
Accept: */*
User-Agent: Android-GCM/1.5 (m0 JSS15J)
Authorization: AidLogin ???????????????????:???????????????????:
app: ?????????????????????
Gcm-ver: 11975036
Gcm-cert: 48761eef50ee53afc4cc9c5f10e6bde7f8f5b82f
content-type: application/x-www-form-urlencoded
Host: android.clients.google.com
Content-Length: 1180
URLEncoded form:
---------------
X-messenger2: 1
X-scope: GCM
X-osv: 18
X-cliv: iid-9877000
X-X-subtype: ????????????
X-appid: fKIbwEJAPu4
X-kid: |ID|3|
X-X-subscription: ????????????
X-subscription: ????????????
X-gmsv: 11975036
X-subtype: ????????????
X-X-kid: |ID|3|
X-pub2:: <SOME_TOKEN_OR_SIGNED_STR_HERE>
X-app_ver_name: 4.13.1
X-app_ver: 1206
X-sig: <SOME_TOKEN_OR_SIGNED_STR_HERE>
app: ?????????????????????
sender:: ????????????
device:: 3597631400132452708
cert: 48761eef50ee53afc4cc9c5f10e6bde7f8f5b82f
app_ver: 1206
gcm_ver: 11975036
Click to expand...
Click to collapse
I would be grateful if anyone can give me a prompt about this workflow, tell me where i can find some sources or is it possible at all to implement this workflow without real phone?
So thank you in advance and sorry for bad english.
el_zok said:
Good day!
In learning objectives I am developing desktop app that must reproduce the behavior of one of the social network's client app on android.
This android app makes several POST-request to android.clients.google .com/c2dm/register3 to confirm that this is real mobile app and to confirm it's API token, then it uses the response from this /c2dm/register3 request as one of the params for refresh token request.
So there is no problem with reverse-engineering social network's client app and using it's private API, but I stuck with implementing this request.
When trying to reproduce the same request intercepted from my mobile app I obtain response
The request headers and data example here (I replace some data with ?? symbols):
I would be grateful if anyone can give me a prompt about this workflow, tell me where i can find some sources or is it possible at all to implement this workflow without real phone?
So thank you in advance and sorry for bad english.
Click to expand...
Click to collapse
I've been working on this as well. Let me share what I've found out thus far pertaining to the information you're unclear about;
Headers
Authorization: AidLogin ???????????????????:???????????????????:
Click to expand...
Click to collapse
The values provided for the AidLogin are android_id:security_token. These values are sent to us (afaik) somewhere along the line from the Google Play Store API. I have yet to find where this occurs and would def appreciate any information anyone has on the subject. I have read the values are returned in a response to a request to the checkin endpoint, but I haven't seen the required values in any response yet. These values are used for AidLogin instead of emailassword. What I do know is that these 2 values can be used more than once while registering devices so if you're unable to figure it out, you can just log the values from emulators and reuse them.
app: ?????????????????????
Click to expand...
Click to collapse
This is the package name of the apk making the /register3 request.
Form
X-X-subtype: ????????????
X-X-subscription: ????????????
X-subscription: ????????????
X-subtype: ????????????
sender:: ????????????
Click to expand...
Click to collapse
These are all the same value (or atleast they have been in all of the requests I've seen). This value can be pulled directly from the apk.
app: ?????????????????????
Click to expand...
Click to collapse
The value provided for device is the same value used in the app header (package name)
X-pub2:: <SOME_TOKEN_OR_SIGNED_STR_HERE>
Click to expand...
Click to collapse
This value is the base64 encoding of the der encoded public rsa key generated by the application.
X-sig: <SOME_TOKEN_OR_SIGNED_STR_HERE>
Click to expand...
Click to collapse
This value is the base64 encoding of SHA256RSA encoded package name, signed using the private rsa key generated by the application.
Note: The value provided for device is the same value used in the AidLogin header (android_id)
device:: 3597631400132452708
This is all the information I know presently and again, if someone has any information on how to obtain the android_id:security_token values I would greatly appreciate any insight. Thanks in advance to whomever may help, As it turns out the android_id and security_token values come from the protobuf response to the request made to https://android.clients.google.com/checkin. Good luck to OP!
Hey all,
There's an app I need help updating to either api 24/26 . The app which is meant to interface with the Joyetech Ocular/Ocular C, which is on Google Play,
https://play.google.com/store/apps/details?id=com.zijing.joyetech
The problem is, the devs of the app hasn't updated it since api 22, and after sending emails to the devs on multiple channels, there's no response.
Looking at the logcat of an app's activity, the Android app derives keys using the SHA1PRNG algorithm from the Crypto provider, and as of Android N, apps must start using a real key derivation function.
My issue is that:
1: I'm very mediocre at things like this. (Decompile, import into Eclipse, edit as needed, then recompile.)
2: My laptop doesn't have enough space to install Eclipse.
Would anyone with more knowledge on this subject be willing to update this apk for me?