Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added posibility to include device info to simulate real device #208

Merged
merged 2 commits into from
Aug 7, 2016

Conversation

segura2010
Copy link
Contributor

No description provided.

@SpencerSharkey
Copy link
Contributor

awesome 💃

@billyriantono billyriantono merged commit 04eb37b into Armax:master Aug 7, 2016
@billyriantono billyriantono mentioned this pull request Aug 7, 2016
@williamokano
Copy link

williamokano commented Aug 8, 2016

Not sure how to extract these data.

@Josebaseba
Copy link
Contributor

How important is this to don't be detected? Do you notice the difference in your app?

Can you give us an example of valid data, I don't know how to fill it properly.

@williamokano
Copy link

Just call Pokeio.SerDeviceInfo({device_id: "SomeId"}); before Pomeio.init.

You can find your id using some app for this, like Android Id (on play
store).

Em seg, 8 de ago de 2016 07:14, Joseba Legarreta notifications@github.com
escreveu:

How important is this to don't be detected? Do you notice the difference
in your app?

Can you give us an example of valid data, I don't know how to fill it
properly.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#208 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AForwjTpP_oxLUCB2lC2NXmb_yiVh0Deks5qdwGOgaJpZM4JeiY-
.

@segura2010
Copy link
Contributor Author

segura2010 commented Aug 8, 2016

@Josebaseba you can find these values with adb

"DeviceId": "", // adb.exe shell settings get secure android_id
"AndroidBoardName": "", // adb.exe shell getprop ro.product.board
"AndroidBootloader": "", // adb.exe shell getprop ro.boot.bootloader
"DeviceBrand": "", // adb.exe shell getprop ro.product.brand
"DeviceModel": "", // adb.exe shell getprop ro.product.model
"DeviceModelIdentifier": "", // adb.exe shell getprop ro.product.name
"DeviceModelBoot": "qcom",
"HardwareManufacturer": "", // adb.exe shell getprop ro.product.manufacturer
"HardwareModel": "", // adb.exe shell getprop ro.product.model
"FirmwareBrand": "", // adb.exe shell getprop ro.product.name
"FirmwareTags": "", // adb.exe shell getprop ro.build.tags
"FirmwareType": "", // adb.exe shell getprop ro.build.type
"FirmwareFingerprint": "" // adb.exe shell getprop ro.build.fingerprint

(Copied from NecroBot readme)

I dont know if there is any app which gives you these values..

I think is important to use device_info data, because official app always sends this data, if you dont send it you are not using the official app.

Also it's important to use altitude values, i thing most of bots use altitude = 0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants