I'm working on an app that shows the user some specs of his device. For example, RAM, disk size etc.
Now I want to show whether the device is rooted or not in case of android device. And whether the device is jailbroken or not in case of devices with iOS.
How to achieve this? Let me tell you that I'm not familiar with native iOS development. So it would be hard for me to write plugin.
EDIT I want the solution in Unity3d. And I want to handle android and iOS devices. That's why it's not a duplicate question as someone mentioned in the comments.
All i can do is to give you a reference.
http://answers.unity3d.com/questions/1012407/detecting-rootedjail-broken-devices.html
Basicaly, the simplest method, would be to pay 5 bucks for a detection script in the asset store.
You can use Application.sandboxType == SandboxBroken // Application is running in broken sandbox.
https://docs.unity3d.com/ScriptReference/Application-sandboxType.html
https://docs.unity3d.com/ScriptReference/ApplicationSandboxType.html
Related
i know it might be the same as this question. i am from the philippines as well but the phone mentioned in that link is a samsung which is an internationally well-known brand and i know that adb supports that brand. what i am planning and really want to buy is this locally known phone. it got a really nice specs but i am worrying that i might not be able to use it on app development. i found adb drivers on the net and installed it but i don't know how to use them with android studio. the reason why i want to use a phone for development is because my laptop slows down with i run android studio and the emulator at the same time. if some co-pinoy already know a phone that they already used for app development within the same price range of flare x, please let me know. please guys i really need help on this matter.
Any phone that allows you to enable USB-Debugging will be suitable for android development. Most developers try to stick to a phone that has a clean Android base like a Nexus or Moto X, as it rules out any interference with vendor specific changes to Android (like Samsungs TouchWiz).
See this page for further information on using a hardware device for development. Google does not recommend any specific device.
Also see this list for device vendors providing ADB drivers. If you want to play it safe, stick to these vendors.
This download page suggests that the Google provided driver is suitable for the Cherry Mobile Flare X too.
Please don't tell me what a bad idea this is. I am not using it as an Android tablet. It is the interface for a propitiatory medical system my company is designing. It's only function ever will be to control the system we are building.
That being said, how can I remove everything from the tablet and only run my app until the tablet dies or the standard firmware is reinstalled?
The tablet is being used exclusively as an interface control panel and CPU to my program which controls the medical equipment externally. I don't want anything else on the tablet. I don't want the users to do anything other than run my program on my equipment.
How can I lock the users into only using my program for the life of the tablet?
(I am building a system that happens to use an Android tablet to control it. Basically, I thought it would be easier to use a tablet, rather than design from scratch a system based on one or more microprocessors and which uses a custom designed and built color interface panel. If the doctors want to use an Android tablet for their offices, they are welcome to buy one.)
Thank you in advance.
Thank you all for your advice.
You will have to build your own version of Android if you wish to do this. For several reasons it is not possible to make an application that will do what you want and have it work on consumer devices.
Exactly how you need to go about customizing the OS build is going to depend on your exact hardware. But the simplest modifications will be removing the unneeded apk files from system/app/ and data/app/
AOSP and XDA-Developers are two great resources for learning the ins and outs of building a custom ROM.
If the device has reasonable power to it, you shouldn't need to worry about background processes.
If this is a consumer product, then it probably has the Google Apps suite and other related items, in which case rooting it and not installing those would be the best route. AOSP only runs processes that it needs to run Android out of the box.
Edit: You might just write the apps a Launcher and not allow opening other apps as the best route to accomplishing your goals.
You might need a custom ROM. It really depends on what version of Android your device supports. Check out the last in the list below.
http://www.redmondpie.com/best-most-popular-custom-roms-for-android-and-why-you-should-try-them-out/
I'm facing similar obstacles utilizing my business tablets. I want to restrict all the pre-loaded applications & only allow the tablet to be utilized for certain applications. White listed websites & such. I wonder if a 3rd party service such as ZENPRISE might offer a mobile management system that would take care of this for me?
zenprise
I just want to know whether it is possible to develop an Android application that will allow remotely controlling an Android phone in the same way that remote desktop, or team viewer allows control over desktop operating systems. Is it possible on an unrooted phone?
The basic functionlit required to acompolish this is would be the ability to capture the frame buffer and programmatically invoke touch on the device.
Any feedback on this matter would be highly appreciated.
No, You would have to modify the OS in order to get that functionality. It is dissallowed for obvious security purposes.
The consensus used to be that it wasn't possible pre-Kit-Kat or without root, but there is a free Android app I came across recently which seems to have figured it out and does exactly what you're asking. It is called Mobizen, and it operates similar to Chromecast or YouTube, pairing the device app with the desktop app (USB) or web-app (Mobile and Wifi).
https://www.mobizen.com/
https://play.google.com/store/apps/details?id=com.rsupport.mvagent&hl=en
How they implemented everything though, I don't know. But it's quite impressive and I would love to get ahold of some source/example code.
I have an android app with more than 500,000 users. I want to try to port it to WinPhone7, but I haven't any smartphone with WinPhone7. Is a real device needed to publish an app on WinPhone? Is there some developper phone?
First of all, I will say that for some scenarios, there is no real substitute for have a physical device to test against. Having said that, I would suggest that 99% of what most apps will do can be developed and test perfectly well on the emulator that comes with the developer tools.
The advantage of the emulator is that you can write and test without shelling out for the hardware and then signing up to create.msdn.com to get it (officially) unlocked, but once you are ready to deploy to the marketplace you will need to sign up anyway.
In your case, I'd say the main word in your question is "try". You don't seem confident in being able to port to the platform so the emulator route seems like the best starting point.
Your will find a Windows Phone 7 emulator in the Windows Phone SDK. You can download it for free on create.msdn.com.
There is an Android to Windows Phone API mapping tool and Windows Phone 7 Guide for Android Application Developers white paper as described on the Windows Phone Developer Blog that you should find very useful.
For getting a development device, you should reach out to Brandon Watson or your local Microsoft WP7 dev rep.
Simple answer - no, you don't. There are plenty of applications out there that were published without being tested on an actual device. Whether it's a good idea or not - that is the main question here. Depending on your application type and its behavior, you might actually need a device.
Also, another problem is the fact that the resources used by the emulator are different from the resources used by the actual device. That being said, if your application runs just fine in the emulator, it will not necessarily run the same way on a device.
You can use the WP7 emulator to test your application. But if you want to deploy it on a real phone, you will have to unlock it though the App Hub portal. That will cost you 100 dollar/year though.
As you and others have rightly pointed out, you can start porting your application using the emulator. There are differences in the emulator and real devices. In particular, to answer your question, emulator does not take pictures.
If your Android app really has half a million users, MS will happily give you a developer device (nearly) for free.
Contact #BrandonWatson or #FrankPR on Twitter.
From my experience I can tell you, that the emulator works very well. But once in a while you will stumble about a problem that you don't understand why it happens. Then you try it on the phone and it works... So... The answer is yes...not!
I am looking for a way (maybe impossible) to test my PhoneGap Android application on different phones / hardware. As I am able to obviously test it only on my phone, but some people are reporting that my app doesn't work / crashes / explodes on their phone. Is there any way how can I test my app on different phones without buying actual device ? Maybe virtually like running Android in an emulator or somehow ?
It is kind of frustrating knowing that the app works perfectly, but some people are not able to even start it...
EDIT: I am certainly testing the app in Android emulator, but that only helps to test on different Android versions. But I am looking for a way how to test in on different phones without actually buying it - if it is possible ?
There is a company called DeviceAnywhere: http://www.deviceanywhere.com/ that seems to be doing that.
But it may cost you. If you don't want to buy all those devices, somebody else will have to. Plus they have to build the infrastructure to support remote access. Does not sound like something you would get for free.
Like DeviceAnywhere, there is another company that will let you test your application on multiple hardware devices. It https://appthwack.com/ . They do have 100 mins of free plan to test out, so go ahead and try this out.
You can run it through the emulator that is provided with the Android development kit through Eclipse. But this will only help test the code on different versions of Android not necessarily on the different hardware so if it is really a hardware problem this will not help but if it is related to the different versions of android this should help you find the problem.
Here is information on the emulator and how to use it: http://developer.android.com/guide/developing/building/building-eclipse.html#RunningOnEmulatorEclipse