I have a 7-inch Android Tablet, but I can find virtually no information about it. Is there any way to root a device like this? It is running 2.2.2 and has some loaded apps, but no market. The device is:
(triple w).35phone.com/35pad/index.html
You'll have to run the page through a translator (unless you read Chinese). What is possible with a device like this that does not show up on anyone's list of Android devices? I'm trying to put it through its paces, but this is difficult when the device is seemingly unknown. Perhaps there is some way to determine core components and extrapolate to similar devices?
Related
Hi. I'm about to get my first Android phone, and would naturally like to know more about the OS. I would describe myself as intimately familiar with ordinary GNU/Linux systems, but let's face it, Android is hardly your ordinary such creature. Moreover, there seems to be very few technical introductions to Android around; those I've found tend to be idiotic user's guides (not technical at all) or focused on software development (interesting, but not what I'm looking for right now).
Things I wonder about with Android include:
There's an unusual libc, right? Is the GNU userland around, though?
The file system directory structure. It's hardly LSB-compliant, eh?
The package system. Everything I've come across is centered around the SDK, and hides many of the details of what goes on here. Sub-questions: Is it only "apps" (gah, I hate the word, I'm sorry) that use the package manager, or is everything covered by it, as in a normal Linux system?
The boot loader. Experience with other ARM/non-x86-systems indicate this is a world very different from GRUB, and also a highly varied one.
How do shared libraries fit into the Android ecosystem? Some places I get the impression everything is static. Is that really true?
What's this non-X display system? How do you configure it, etc.?
What's the init system like?
As far as I've understood, the actual phone software (is "baseband" the right terminology?) tends to be proprietary and separate from the OS. How does it fit into all of this? Does the OS execute code at some mysterious memory location? Is some special-purpose hardware run? Is it just a standard process? Is it in kernel-space?
I'm not looking to get these questions answered here. Rather, I'm asking: Are there any documents or books around that try to fill the role of bringing an experienced Linux user with decent development background and technical knowledge into Android?
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
Wanted to start a thread on this subject as I have yet to see anything regarding AfW anywhere in these threads.
Does anyone have any information on how the o/s will handle securely wrapping applications and how the o/s creates a second partition/perimeter that is secured from the personal side?
Google Android For Work if you haven't heard about it.
I'm wondering if a rooted device would be able to trick the MDM protected work perimeter to think it has a secure bootrom, recovery partition and valid o/s?
Anyone have a picture of what the filesystem difference looks like?
There's such little information on this, yet it was released with 5.0 lollipop and I'm sure if we reverse engineer the way it functions we could create our own pki enabled MDM open source solution. This would allow end users to freely use there phone without the fear of being snooped on by viruses, corporations for marketing purposes, etc. Overall an open source Mobile Iron solution is what I'm getting to.
Let me know what you guys think.
Does anyone know how to go about casting/mirroring your android device to a TV? While you are hiding information?
For example, say I wanted to cast/mirror a custom app from my phone, but I wanted some stuff to only be visible to me from my phone. How exactly would you go about doing this?
(My thought of approaching this)
Is there a way to configure a custom app so it will zoom-in in a specific area? Which only zooms-in on the app from the TV to hide all of the exterior stuff I ONLY want to see from my android device.
Is there a specific software or device you need to use to accomplish this?
I work with Android Studio just in case this helps. I hope I explained it well enough and provided enough information.
Hi all
We use a few rugged android devices at work as glorified GPS and mapping units. They work great however today I found out that our main data collection service is updating their android application to use TLSv1.2. From my research it looks like all android devices beyond API level 16 (Jellybean) CAN support TLSv1.2, however it is not turned on by default (whatever that means) before API level 20/21 (KitKat wearable/Lollipop). We have devices running 4.1.1, 4.2.1 and 4.4.4.
There is literally zero chance of getting these devices upgraded to Lollipop. They are made by Getac and Aspera - both small companies. Anyone that uses rugged devices knows that you trade in your access to updates and custom roms etc when you opt for one. They are too much of a niche product to attract developers and the manufactures just want a stable device, not the latest and greatest. They also generally run lower end specifications, so updating to newer OS is not always desired. We have a Getac z710 (http://us.getac.com/tablets/Z710/features.html), one Aspera R5 (http://asperamobile.com/products/aspera-r5/) and three Aspera R6s (http://asperamobile.com/products/aspera-r6/). I am not even sure if they have root solutions available for them...
So does anyone out there with a kind heart and some knowledge want to help see if there is anything that can be done on my end to turn on support for TLSv1.2? Here is some stuff I found so far, but most of it seems like it needs to be done on the server side, not client side.
http://stackoverflow.com/questions/24357863/making-sslengine-use-tlsv1-2-on-android-4-4-2
http://www.jordanrejaud.com/android/2015/09/19/android-tls-ssl-engine.html
None of these devices are rooted, so everything needs to be done via adb, or i need a root solution...
bump...
Did you ever find a solution for this? I'm trying looking into this myself but haven't found anything that would modify it for the whole OS, only something that would require modifying the source code for an app.
I have the same problem/question:
GetBackersBH said:
Did you ever find a solution for this? I'm trying looking into this myself but haven't found anything that would modify it for the whole OS, only something that would require modifying the source code for an app.
Click to expand...
Click to collapse
Is there a known solution that would modify the whole OS, not just an app through a code? I would need TLS 1.2 permanently enabled on Android 4.4.2 KitKat. The phone is rooted, BTW.