So, this may be a very newbie question, but I'm sorry.
My phone (SM-A500FU) doesn't have a gyroscope, but I found this page on github, that provides some source in C and an explanation about a Virtual Gyro.
By my previous experience with Linux on a desktop, I know CPU thermal sensor data is stored in a file.
Could it be possible with Xposed or anything to fake a gyroscope? Or override the methods games use somehow just like Lucky Patcher does with Google Play?
I don't really know much about how could this be done, so maybe someone can help.
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!
Hi,
First i'm new and maybe i didnt choose the correct subforum, so if i'm wrong i'm sorry. Second, i entered in 'similar' threads about my questions and nothing similar.
Well, i'm comp. engineer student and i have to make one project about encoding and decoding video using the Device Hardware, so i began to investigate and i could find that Google released one API with some classes that access to low-level codecs (eg. MediaCodec, MediaExtractor or MediaFormat), so that API solve my problem, so i should learn how to develop with it and no more but...
I have readed that before that API, released this year, there was some frameworks named OpenCore and StageFright, and people who wanted to use hw device codecs had to use that frameworks, but i really dont know how people did it, if i can find some examples, and which differences can i get using directly this frameworks instead of the Android 4.1 API.
As last question, does anybody knows if this API access to the stagefright or opencore frameworks when you creates an encoder or decoder?
I know that maybe are totally noob questions, but i have googled for it from time ago and i can't get nothing usefull exception about 4.1 API which i could find Google I/O videos and documentation and now i know a bit better how it works.
Thanks!
Hi Guys
I've been developing a http based Server Software that uses an android device as a single purpose device.. say an input terminal. So I developed a very simple app just for this input purpose (including some data from sensors on the device). It aslo loads a web view for a little html banner.
So it's really simple and the design is to basically turn an android device into a single purpose hardware... and with that said i really dont need 90% of what's installed and running on android, I dont need complicated launchers, and i DO need to kind of "lock the device down" to my app only (i guess kiosk like?)
I basically need the hardware and the OS to run my app.
if possible make everything as lightweight as possible (again as i dont need most of the android features)
and I would love it if my app can run on top of everything and at every start up (it can even pretend to be the SHELL or OS on top of Android OS, or kind of like that approach)..
So yeh, I'm hoping you guys can give me some advise/suggestions as to how best to approach this? (honestly i'm fairly new to android as a whole)
Things off the top of my head are:
1) Custom ROM like really plain/lightweight w/ lock down features <-- is there even any rom like this? or could i ask someone to code this for me?
2) Root, SuperSU, and xPosed Framework plugins and tweaks ? <-- i've not tried xPosed Framework and Im not sure if it's meant to be, or good for, my purpose.
3) Use an APP that can pretty much make a Kiosk out of the phone, w/ my app running permanently? <-- i've seen one kiosk app www.kioware.com but it's crazy expensive and i guess a bit of an overkill to what i need.. Perhaps there's a cheaper more simple kiosk app you can recommend? or perhaps an opensource project i can tinker with?
Would really appreciate your thoughts on this..
Thank you very much!
A common request
Can anyone direct me to a thread where this issue is resolved? It seems more complicated than it seems at first glance.
Hi.
Are there any game hacking tools like gamecih or game guardian( searches ram for values and changes them) that works with android 5.1? I couldn't find anything anywhere.
I need to test how vanurable my game is from these kind of hacks. So I need to find one of these tools for testing.
Thanks
Lucky patcher is banned here. Do not mention it.
Also you won't find any of these types of tools here.
I'll be honest anyone running xposed would be able to bypass any restriction you try.
I'm not a developer but I have knowledge about Linux and how PCs in general work. Is there any book/course that explains how android works on a deeper level? I'm not interested in apps or user UIs, I want to know the deeper levels like how partitioning works, how the OS is loaded, why some bootloaders are locked by default, what a custom recovery is or what is the first thing to load when you power on your phone/tablet (do phones have a BIOS like PCs or anything equivalent?). Thanks in advance.
I'm also interested in this, but I think the answer is it's a bunch of undocumented proprietary baseband processor junk nobody will share for the boot, then the rest is basically a Linux distro made by 1000 monkeys on 1000 typewriters copy/pasting stuff provided by their hardware vendors together, and the components of that also probably have no documentation or incorrect documentation.
Just browsing through directory structures on a rooted phone there's so much unused and inaccessible junk like config files for really old versions of android, random vendor apks that aren't configured, and firmware for other processors strewn all over, sometimes multiple copies of the same structure, that it makes no sense. It looks like a bunch of vendors gave their support libraries to manufacturers with the intent they'd delete the unused parts and copy the used parts in, but the manufacturers don't understand how to do that so they just paste the same full directory structure several different places until it starts working.
If it made any sense, some people would just learn it and rooting new phones wouldn't be hard.
dan2525 said:
I'm not a developer but I have knowledge about Linux and how PCs in general work. Is there any book/course that explains how android works on a deeper level? I'm not interested in apps or user UIs, I want to know the deeper levels like how partitioning works, how the OS is loaded, why some bootloaders are locked by default, what a custom recovery is or what is the first thing to load when you power on your phone/tablet (do phones have a BIOS like PCs or anything equivalent?). Thanks in advance.
Click to expand...
Click to collapse
The rabbit hole goes as deep as you want it to. I have plenty of information to get you started. Happy digging!
*A general overview of the android boot process, thanks to the Lineage OS developers.
*An old, but good read on reverse engineering aboot.
*And a much more recent article on reverse engineering android. It gets very detailed in this one. It also goes into the low level processes of android. Like; What loads the bootloader? That kind of stuff. I think this is what you're after. Hope it helps.
About the bios question. The short answer is, "kind of". They have a very simple and proprietary one that's not easy to access. It also does not function in the same ways that a PC bios does. It's more like a motherboard programmer. It's hard to explain. The last article goes into some of that.
Spaceminer said:
The rabbit hole goes as deep as you want it to. I have plenty of information to get you started. Happy digging!
*A general overview of the android boot process, thanks to the Lineage OS developers.
*An old, but good read on reverse engineering aboot.
*And a much more recent article on reverse engineering android. It gets very detailed in this one. It also goes into the low level processes of android. Like; What loads the bootloader? That kind of stuff. I think this is what you're after. Hope it helps.
About the bios question. The short answer is, "kind of". They have a very simple and proprietary one that's not easy to access. It also does not function in the same ways that a PC bios does. It's more like a motherboard programmer. It's hard to explain. The last article goes into some of that.
Click to expand...
Click to collapse
Do you know if there is any tool that lists all the various initscripts and settings in use on a running system? I'd like to remove Google entirely from my phone, but there are so many firmwares and initscripts all over the place that I can't even figure out which ones are actually used to run the system. Half of the settings files, properties, and commands return 0 results or 3-4 useless results when searching for them on the internet.
ZHNN said:
Do you know if there is any tool that lists all the various initscripts and settings in use on a running system? I'd like to remove Google entirely from my phone, but there are so many firmwares and initscripts all over the place that I can't even figure out which ones are actually used to run the system. Half of the settings files, properties, and commands return 0 results or 3-4 useless results when searching for them on the internet.
Click to expand...
Click to collapse
The best way to remove google entirely is to flash a custom ROM or GSI if your device supports it. You really only need to look in system/app and system/priv-app for google stuff. Some phones use stock Google apps for things like the Calendar or MMS. So, to run google-less you may need to replace some system apps as well. Just a warning, even if you already know this. Removing certain apps, even google apps, may cause problems for normal operation. Definitely make a backup before deleting anything in the system.
ZHNN said:
Do you know if there is any tool that lists all the various initscripts and settings in use on a running system? I'd like to remove Google entirely from my phone, but there are so many firmwares and initscripts all over the place that I can't even figure out which ones are actually used to run the system. Half of the settings files, properties, and commands return 0 results or 3-4 useless results when searching for them on the internet.
Click to expand...
Click to collapse
I'm no expert but have been running lineageos 14.1 for some time now. It is a version of android 7.1 in which everything google has been removed. I use it with microG which replaces google play services.
You may wish to look into it instead of re-inventing the wheel.
I use it with a firewall (AFWall +), and Xprivacylua for additional privacy.