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
Related
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?
Hello,
I have a question not really related to rom development but I hope it is okay if I still ask it here.
My question is: "How deep can I go with an App inside the Android System".
Let me explain. For my thesis in university I need to develop a possibility on how to monitore the behavior of apps. Achieving this by altering the Android System itself is a bunch of work but not very complicated or new. So my Prof asked me if I could do this with just an App - my first thought was NO, but before telling him I thought that I could ask you guys/girls
Topic is on: Monitoring Apps with focus on
- Contacts access (does App xyz actually reads the telephone book and which data is read).
- Calendar (does App xyz reads the calendar)
- Internet Access (does App xyz sends data to a server - to which server - or does this app retrieves information from the internet).
... (... means -> the more ideas the better )
So what I'd like to know is: Does anyone of you has an idea how I could achieve such thing and/or can you tell me how deep I can go into the system with a simple app (doesn't matter if via API or direct IPC or ...)
Thank you very much
Would it matter if the app required root access? I'm sure with root access you could achieve your goal. Not sure if you could without root.
Sent from my ADR6400L using xda premium
Hi a rooted phone is the second possibility - rooting and installing an app is still better then the need to setup with a complete new rom.
Do you have any ideas how I could do this with a rooted phone - i thought about writing some kind of a rootkit but somehow this don't seems to delight my Prof
There seems to be a whole class of software that already does exactly that for not rooted and rooted variations. Check market for any backup software, backup contacts/logs/SMS/apps with data external SD or send to cloud. Pretty much every option seems to be covered under that heading.
Something for you to check out anyway
Sent from my GT-P7300 using Tapatalk
IF you have an idea how you can achieve the above mentioned using a custom rom then you already know which features you will be overridding, in that case create an app that does all that and show's some graphs and features on screen. Just like busybox installer stuff.
just had to say this cause of the threads title...thats what she said!
Sent from my SAMSUNG-SGH-I717 using XDA
Please mind the "with an App" supplement
Hi everyone,
So the company that provides the TV channels in my country (like the cable companies in the US) has a streaming service that streams most of these channels online to phones, tablets, computers.
The problem is that their app is, according to them "not supported on hacked devices". Just so we're clear, we're talking about Android here, and hacked = root/custom rom, which this stupid company considers illegal. In some devices, they check both root and custom rom, in some only one of them, and in some the app will work even if you have both. For example, on my Nexus 4 the app worked with stock rom that was rooted. Now that I am running a custom rom, trying to hide root using various apps does not work. So obviously the problem, with my device at least, is running the custom rom.
I'm currently learning Java & Android development and have decided to use the little knowledge that I have to try to find the lines of code responsible for this idiotic check.
I looked up many tools for decompiling apps and have finally found a good one, called JadX.
http://androidcracking.blogspot.co.il/2014/03/jadx-dex-to-java-decompiler.html#links
This decompiler is excellent, but gives me a scary amount of code files to look. Even so, trying to search all of them (JadX has that functionality) for the code that checks for root/custom rom has turned up nothing. I have also tried to search for the message they give me when I open the app (about hacked devices not working) but I found nothing, again.
One more thing - a developer that also tried to solve this problem said he traced the problem back to DxDrmDlcCore. I searched it, found it a some class, but not sure what to do now (delete the entire class and recompile?)
Can someone here direct me towards what I need to be looking for?
OR
Is the solution really simple, such as editing my build.prop? Someone suggested it once, but did not know what lines to edit.
If someone is ready to step up to the challenge, I can upload the apk.
Thank you!
Hello everyone
I'm switching from an Android emulator to another and want Google to recognizes my new emulator as the same device, and I was wondering which value(s) do I have to copy from my current emulator to the new one in order to accomplish that.
I looked into it and found that there are a lot of values that differs devices from each other like Android ID, GUID, UUID, fingerprint, etc, and of course brand and model. But I'm not sure which value that makes Google see a device as a specific one.
And help is appreciated.
Sent from my LG-D838 using XDA Free mobile app
Aserar said:
Hello everyone
I'm switching from an Android emulator to another and want Google to recognizes my new emulator as the same device, and I was wondering which value(s) do I have to copy from my current emulator to the new one in order to accomplish that.
I looked into it and found that there are a lot of values that differs devices from each other like Android ID, GUID, UUID, fingerprint, etc, and of course brand and model. But I'm not sure which value that makes Google see a device as a specific one.
And help is appreciated.
Click to expand...
Click to collapse
Maybe fingerprint? Like the Android certification check with Android ID, which takes access from playstore, if you are on custom rom without registration.
I'm a long time developer but brand new to Android, with my having past experience developing in Unix systems as well as a lot using Cygwin in Windows. I have a newly-installed App that seems popular called 'C Locker'. So far, I've just got the Free version because I'm trying it out to see if it does what I need. Unfortunately, it's now crashing with the Settings that I've enabled, and as a general developer, I'm interested in seeing if I can glean information from the Bugreport (or whatever else I can use...perhaps even gdb on the device itself?) to help me know what specific Settings might be the problem being that there are so many of them and I would prefer to gain some type of help from my phone in figuring out what the bad settings might be that I've enabled that are causing the problem rather than to spend all day flipping them around. I've already scanned through the Bugreport after uploading it to my computer, examining all of the references it makes in there to "com.ccs.lockscreen" with this apparently being the process name for the C-Locker program. I've seen indications in there where it indeed shows that it has crashed, but I couldn't yet discern if it is able to give me pointers as to what the cause of the crashes might have been. Is that possible to gain such information out of these Bugreport files? Or is there a way to run it directly in gdb on my device to perhaps see the stack at the time that it crashes, for which the names provided might help to discern what specifically it was trying but failing to do at the time? If it helps, as an intended future Android developer, I've already gotten Android SDK set up on my computer, although I haven't yet really used it much to speak of for anything. I also have adb working from my computer to the smartphone and even have rooted it using a rare method being that I have an older phone purchased years ago via Amazon that I didn't activate until about a month ago. (It's an LG G4 VS986 version 13B so I couldn't use the popular rooting method for version 11A but instead had to use the "Injection" method which took me FOREVER although I finally got it to work!) And just in case it helps perhaps even to bypass a direct answer to this question (although it will still of course be appreciated), my Settings within C Locker involve having set it to be a Device Admin and to bring it up as the first App upon Reboot as well as I've selected within the Root category to make it a System App as well as my then having Disabled ALL things that typically show on the screen (such as 9-1-1, camera, Etc). I had left it set to the default "Gesture" Unlock method, but whenever I bring up the App again and go into "Unlock Methods", it now immediately crashes each time (as well as upon Restarting the phone!). So this covers the majority of the most significant of the Settings that I've made on it so far to the best of my recollection. And I feel that if I could get some indications from the system as to what the specific errors may be when its crashing (or from a stack trace or whatever else), then it might help me to discern what specific Settings are creating the problem being that perhaps I just have an odd (rare) combination of Settings on it that I can tweak to get it working. My goal is to ultimately get a lockscreen App that I can use a Pattern type Unlock with that allows an UNLIMITED number of Failed Attempts (so that it won't ever Factory Reset my phone after the 10th or ANY number of failures!!!). I also--as mentioned above--don't want ANY shortcuts whatsoever being accessible BEFORE the phone is unlocked...not even 9-1-1. Anyway, so if there's a way to glean information from the Bugreport (or from whatever other methods available) to find the specific cause (involved errors) of this or any other App that's crashing that I do NOT have the source code for (being that I of course am not its developer) then it will be greatly appreciated to know how to best find this information. (And I promise that I've already searched extensively on Google but couldn't filter out its replies all being based on the idea that I'm the developer of the App that's crashing, with my even trying adding phrases such as "not my app" and "not the developer of" Etc to no avail...lol). Thanks.
By the way, if I shouldn't have combined the 'C Locker' Settings details into this post, then please just let me know because I'm new to posting here. Also, unfortunately, if I don't receive any help with this right away, then I'll be forced to start testing different Setting combinations anyway, which would then of course solve this problem but without knowing truly what exactly was causing the issue. Even if so, it will still be helpful in the long run with other potential App crashes to get the answer to this general question.
Unless not disabled by user, all runtime activities in Android are logged, so app crashes and their reason also. You can view this log by means of Android's logcat command-line tool or by means of a LogCat Viewer app. My POV: logcat is essential for determining what an app and the Android OS are doing while the app is running on a device.
BTW: Android's log can be filtered per package, too.
Thanks!
jwoegerbauer said:
Unless not disabled by user, all runtime activities in Android are logged, so app crashes and their reason also. You can view this log by means of Android's logcat command-line tool or by means of a LogCat Viewer app. My POV: logcat is essential for determining what an app and the Android OS are doing while the app is running on a device.
BTW: Android's log can be filtered per package, too.
Click to expand...
Click to collapse
Thank you, and since posting this, I've been learning more about Android Studio and have used it to actually see the stack trace within the "Android Monitor" pane there in order to find the instant reason why the/ANY (meaning 3rd party as well) App is crashing at the time! Thanks again for the help!