Developer Options Marshmallow Vs. Every Other OS Mock Location Issues - Android Q&A, Help & Troubleshooting

Hello wizards of XDA, I currently face an issue.
As some of you may know, google had the """""brilliant""""" idea to change what used to be called mock locations to mock location app. The problem is, the apps I have are from the before times, While it is confirmed that the mock location app does work, this new sorcery is poorly crafted and chaotic, it does not work with the techno teleportation features of the old apps. Some of these apps are no longer in development so waiting for new releases isn't an option. What I need, is the old option: "mock location." I have no idea how to achieve this, but I do have some theories that will hopefully inspire more knowledgeable users to find a solution. Im running a G930A (at&t s7) with root, though functionality is rather limited as I'm using the root method that was released less than a week ago. Please keep in mind, this is the first time I've ever rooted a device, so i wont understand a 3 word tutorial.
Theory 1: Some Custom Rom: Wondering if a custom rom would have that option, I would want to go with something people who used the same root method as me are having success with. I've heard a number of people had success with Xposed. Also performance is a slight issues, after rooting, myself and several others have had issues with lag and our phones getting abnormally hot.
Theory 2: Do something with custom rom toolkit to make it work
Theory 3: use the terminal in custom rom toolkit perhaps some adb commands to make it work
Theory 4: steal a time machine from the us government, travel back in time and punch the ceo of samsung in the face
Theory 5: mock location is for scrubs, build a teleportation device and make it happen. DONT LET YOUR DREAMS BE DREAMS!
Theory 6: Take a journey with Schrodinger's cat into a dimension where a solution to this problem already exists
Theory 7: Why are you still reading these
Theory 8lease answer my question now

Related

hi

hey i'm new just curious what rooting means? and what it lets you do?
xstreetz said:
hey i'm new just curious what rooting means? and what it lets you do?
Click to expand...
Click to collapse
Google is your friend. But, can can start here.
Root Android the Easy Way
Add advanced features, customize the interface, and boost your handset's performance by rooting your Android phone.
By Robert Strohmeyer
Sep 14, 2010 5:00 PM
Google's Android operating system is riding a wave of popularity that has rapidly eclipsed Apple's iOS, and by the end of 2010 it's expected to overtake RIM's BlackBerry as America's leading smartphone platform. However, despite the relative openness and flexibility of the OS, your Android phone still isn't as powerful and customizable as it could be. To unlock all of your phone's potential, you'll need to root it.
WARNING: Rooting--adding superuser capabilities to your phone by altering its system permissions--is an advanced technique that the inexperienced or faint of heart should NEVER ATTEMPT. It's hacking, folks, and if done improperly it can destroy your phone. Do not follow any of the instructions in this guide or on any of the linked sites unless you are comfortable with the very real risk of turning your phone into an expensive brick. As of this writing, rooting is not supported by any carrier or manufacturer, and will most likely void your phone's warranty. In short: This stuff is for big kids only. No whining if things don't go your way.
Why Root?
With that very real and important caveat out of the way, there are a few really good reasons to root your Android phone. The simplest reason is that rooting your handset allows for some cool features that probably ought to be enabled in Android by default, such as on-the-fly screen capture, tethering capabilities (even on phones whose carriers don't allow it), and advanced firewall apps.
Android Superuser Request
Rooting Android gives you superuser access to your phone's OS, letting you do more than you'd be able to with a stock Android installation.
Rooting also lets you install custom ROMs that eliminate the annoying crapware many manufacturers and carriers include by default. In addition, custom ROMs can give you the latest version of Android weeks--or even months--ahead of the carriers' sluggish update schedules.
Rooted phones can take advantage of some great performance tweaks--such as CPU overclocking and improved cache management--that can dramatically speed up Android. You can take advantage of these options either by installing a ROM that includes them or by downloading apps from the Android Market that will automatically tweak settings on your rooted phone for you.
It would be a stretch to say that rooting Android is a necessary project for most users. In fact, most people should never even try it on their phones, just as most PC users probably shouldn't attempt to overclock their processors. But if you're an advanced user (or an intermediate user with a taste for adventure) and you know the risks, rooting can help you get a lot more fun and function out of your Android device.
Get Root
Until fairly recently, rooting Android was a messy process that required installing the Android Debug Bridge and hacking the phone from a command line. Fortunately, some industrious hackers have produced a few simple apps that can root your device in seconds with the tap of a finger. In this tutorial, I'll discuss two such apps--Easy Root (for the Motorola Droid, Droid X, and Milestone, and the HTC/Google Nexus One) and Unrevoked (which supports a variety of HTC handsets).
It's important to note here that although these one-click root apps are easy to use, they aren't completely trouble-free. For instance, as of this writing the developer of Unrevoked 3 is reviewing it to solve a problem with the HTC EVO 4G (but Unrevoked 2 is still available). And the latest version of Android, 2.2 (aka Froyo), will present new challenges for root users as carriers and phone manufacturers continue to try to block users from hacking their handsets. These obstacles are a basic reality for anyone attempting to root their device, just as Apple iPhone users must constantly adapt to Apple's efforts to block people from jailbreaking the iPhone.
Even though Easy Root and Unrevoked don't work on all Android phones, they do cover a broad swath of the Android universe. If you're interested in rooting a Samsung Galaxy or another device, however, you still have options--they're just not as easy. Because the state of Android hacking is constantly in flux, your best bet for phones not covered in this tutorial is to google "root" and the name of your phone, or to keep an eye on the discussions about your phone on a good Android forum, such as AllDroid.org.
Step 1: Download a Rooting App
To get started rooting your phone, you need the appropriate app for your device. If you're using a Droid, Droid X, Milestone, or Nexus One, you'll want Easy Root. HTC users with an Aria, Desire, Droid Incredible, EVO 4G, Hero, or Wildfire/Buzz will want to use Unrevoked. With either of these apps, your first step is to download the app directly from the developer's Website and put it in the root folder of your phone's SD Card.
Easy Root downloads as an APK file that's ready to run from the phone, so you could just download it straight onto the device and tap it in your file manager app to run it.
Unrevoked downloads as a zipped file with several files inside it. If you have an unzip utility on your phone, you can download and unzip it directly on your device. Otherwise, you'll need to unzip it on a PC and copy the appropriate file to the phone. Because Unrevoked comes in a few phone-specific files, it's generally best just to copy the correct file from your PC in the first place. The documentation on the Unrevoked site clearly explains which file to use for your particular phone.
Step 2: Install the App
Once you've placed the APK file for your rooting app onto your phone's SD Card, locate it with a file-management app such as Astro File Manager and tap it to start the installation. Follow the prompts to allow the installation. Once this finishes, the rooting app will appear in the phone's App Drawer. Launch it.
Step 3: Root It
Easy Root for Android
Easy Root's interface is as simple as it gets. Tap 'ROOT ME!' to root your phone.
This is the moment of truth. With your newly installed rooting app launched, tap the option to root the phone. (You may first have to tap past a warning or disclaimer screen.) Once you tap the button to root your phone, the app will spend a few seconds running a script that alters the system's user permissions to allow superuser access and install a customized recovery image on your phone's System partition. It will then present you with a screen that says you have root.
In some instances, running Easy Root or Unrevoked on a supported device and following all the instructions exactly can still result in an unrooted phone. If this happens to you, don't lose heart. The developers of these apps are highly responsive to user questions and feedback, and if you take care to document everything you did and all of the relevant settings on your device, you stand a good chance of getting the help you need to root your handset. Or, at the very least, you could provide valuable information that the developer can use to update the app and make it work on phones like yours. Just remember: Rooting is a precarious business for everyone involved, and these developers have put a lot of work into their projects with very little promise of reward. So be nice, even if you're frustrated.
Step 4: Reboot
Restart your phone to enable the new root permissions on your device. Congratulations--your handset should now be rooted.
Now What?
Gaining superuser access to your phone is just the first step in a vast new territory of Android exploration. Depending on which rooting app you're using, you may already be enjoying the performance and usability benefits of a host of enhancements included in your root recovery image. But there's plenty more to explore.
Barnacle Wi-Fi Tether
Barnacle makes it one-tap easy to add Wi-Fi tethering to your phone, even if your carrier doesn't support the feature.
If your phone doesn't support Wi-Fi tethering out of the box, you can now add it to your rooted phone. Barnacle is a good, fairly simple app that exploits root for tethering with or without your carrier's support.
Root users also have the option to overclock the phone's CPU to give it a serious performance boost. For this task, it's hard to beat SetCPU, which offers a friendly slider-bar interface for setting your phone's clock speed. But be careful: Setting your clock speed too high can damage your phone permanently.
ROM Manager
ROM Manager includes a variety of features that make replacing your phone's stock OS easy.
The ultimate Android hack is to replace your phone's default operating system with a custom ROM. You have many to choose from, and each has its own pros and cons. Some ROMs are designed for specific phone models, and not all Android phones support the installation of a custom ROM. As of this writing, the Droid X is particularly problematic in this regard, while handsets such as the Nexus One and Droid Incredible support a wide variety of ROMs. The best way to find, install, and manage ROMs is to run ROM Manager, which is available for free from the Android Market. ROM Manager Premium even offers a large list of available ROMs that you can download straight from the app itself.
Have Fun
By now you should have a pretty good handle on working with a rooted Android device. I've attempted to cover all the basics in this guide, but there's no shortage of additional tips, tricks, and advice that can help you improve how Android functions. If you have some tips of your own to share, please chime in with a comment. And if you think my attempt to simplify the process has resulted in a significant error or omission, please let me know by e-mailing [email protected].
Click to expand...
Click to collapse
thanks will do some reading

Root Security

Hi all
I am currently in the planning stages of developing a root security system for Android.
As everyone knows, there are security implications to rooting your phone etc. Untill now, I have used the normal means of controlling this (lock security, disabling ADB, Superuser.apk whitelist), but this is of limitted help if someone physically gets hold of your phone (while unlocked or ADB enabled).
There are a few things I would like to implement, and would like to gather some feedback on whether;
a) It will be of use to anyone but me, and
b) If anyone has any input as to the feasability (or has done any such work in the past)?
There are 3 areas I would like to lock down, somehow. It will not perfect the security, but will go a long way toward improving the overall security on rooted devices. I have not done much reasearch as yet, so some of this may be impossible. These are:
1) CWM recovery: Currently, CWM (and other recovery/pre-android resources) can be used to bypass almost anything you put in place to secure your phone. I would like to implement a password/passcode on CWM to lock out unauthorised changes. My personal preference would be to store this in /data somewhere it would be removed on wipe, and leave the option to wipe without passcode (so you don't end up with a brick if you forget the password), but lock out all security-sensitive operations like flashing. That way, someone could get to recovery, but would have to wipe data to be able to do anything usefull without authorisation.
2) ADB: Currently, even if your phone is locked you can get access to everything through ADB. The only way I currently see to do anything about this is to disable ADB when you are not using it, but this is irritating when you use it as much as I do. What I would like to do instead is either force a popup from Superuser.apk to grant root every time you connect, or implement a password which must be entered on connection. Both could be problematic, but I think forcing a confirmation (or even a check if the dev is unlocked) would be most useable, but my knowledge is limitted here. It may be that neither method is practical and disabling ADB is the only practical solution.
3) Superuser.apk: Everyone knows they should have security set up on their phones and not leave it lying around unlocked, but some don't like the hassle and most will occasionally forget to lock it. I would therefore like to implement securoty on Superuser.apk to stop (at least) new apps from aquiring root. This is the least important IMHO, but would be a further step towards improving security.
So, what does everyone think?
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
lufc said:
Questions or Problems Should Not Be Posted in the Development Forum
Click to expand...
Click to collapse
Sorry. I posted in Dev because this is the beginning stages of some development I plan to do, but fair enough.
I can only really answer the first question... I would be interested in something like this. I've actually taken an interest in mobile security recently, but I've constrained myself to existing products like avast and PDroid to give me some extra protection. When it comes to hardening these other components... I don't know enough about stuff at that level. But I would dig it.
Things like avast handle some things, like disabling debug if you remotely lock it. But it wouldn't solve things like securing CWM if the person simply reboots into recovery.
How do you disable ADB now?
please, do it!
drmouse81
As a poor ex-owner of a lost Samsung Galaxy Ace, I would love to have a password protected CWM recovery ... this would have propably saved my device (an have back my loved photos!)
My device was operator-locked, SIM was pin protected, screen was locked by pattern ... I rang to my lost mobile, taxi driver answered ... spoke with him ... asked him to return my phone I was offering rewarding. He laughted a lot!
Yes, there are apps to locate your terminal, ring loud, etc. But none solves the basic problem of someone that wipes the phone, puts a new bootloader, etc.
Most people do not knkow that IMEI blocking only works in home country of the SIM operator.
On the other hand, there were a lot of past discussions on this topic, but many people seem not to see this as feasible.
If you find a way to solve this, I am sure you will do a lot of money with companies, who are looking for a real solution to information loss on mobile devices.
Requirements: phone should be not functional. thieves would be able to use them only for spares ...
a) require password to make changes to bootloader / wipe (that is, recovery is also blocked)
b) encryption of user data (even in SD)
c) allow to swipe a new SIM, provide pin of the SIM, then block the phone but send SMS with new number and location. Show on screen customizable message (such as -- this phone is property of xxx and has been lost/stolen -- please contact owner at xxx or hand it to police --- )
Is this possible? Why previous discussions shut off this topics?
Best luck - would love to be guinea pig for this ...
CTone.
---------- Post added at 01:00 AM ---------- Previous post was at 12:39 AM ----------
www dot cyanogenmod dot com slash blog slash security-and-you
Hi
I stopped posting here for a couple of reasons, the main one being I have been too busy. I'm still planning to take this on, but it may be a while.
The other problem is that, although it will help, it will not secure the device completely. There will always be ways around it. Manufacturer supplied tools will still bypass it.
As for your phone, did you contact the police? Knowing the taxi driver answered, they should have been able to get it back, or at least prosecute they b#####d!
Sent from my MB860 using xda premium
You actually have a really valid and practical idea...
Have nothing to contribute here, just want to encourage you...
:thumbup:
If personal life does permit you, please do consider working on this
Typed using a small touchscreen

[Q] Set custom DNS (e.g. openNic, OpenDNS, etc.), (post 2015 CE)

I have scoured the interwebs for a solution, yet found only obsolete and empirically ineffectual methods, aka "setprop net.dsn1" etc., none of which persist, neither immediately after the issued command nor, especially, after a reboot.
Please allow me to make it clear, that I find it perverse and loathsome that an "app" would be necessary to accomplish this feat. The indolent '"app" mentality', which is the sadly presumed remedy for nearly every action other than involuntary motion, is a contract with the assassin of freedom – and I abhor it venomously.
I have owned an Android (presently with CM11 ROM installed, with TWRP recovery) device for two weeks. It is the first Android device (or smart, tablet, etc.) I've ever owned or dared t fuss with. I particularly purchased the Samsung Galaxy Tab Pro 8.4 because it was supported by CM. I am normally a Linux user and value my liberties of hack-ability. Oddly, I was able to successfully configure my DNS via a terminal emulator within my Android device, but recent updates seem to have thwarted my efforts. Apparently, resolv.conf no longer exists and some fundamental changes have been implemented, though this is all new to me and I ain't sure.
I believe that a user should be able to configure their own DNS (amongst other things) and therefore request assistance from the wizards of xda. Google is simply unacceptable, and Verizon hijacking plain makes me mad.
Show me the way, to 208.67.222.222!

App not allowing me to sign in due to custom rom

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!

Is there a device and android version that allows complete control of all permissions

Is there a phone/android version that allows someone whos not an Android expert to actually have control over what their phones doing? Or is it just not possible nowadays for a regular person to fully control the info their phone sends?
Sorry if this sounds cynical, it really is a genuine question.
Thank you.
Hi Steve, it sounds like what you need is a rooted phone. Forgive me if you're already familiar with the term, but rooting basically gives you administrator rights over just about everything on your phone, with only a few exceptions depending on which Android version the phone is running. This allows you to do stuff like revoke permissions for apps, block ads, and change how Android looks and behaves.
Do you have a phone in mind already? If not, what's your budget?
questions should be posted in q/a Thread moved please review the rules ( located below)
rhythm_dx said:
Hi Steve, it sounds like what you need is a rooted phone. Forgive me if you're already familiar with the term, but rooting basically gives you administrator rights over just about everything on your phone, with only a few exceptions depending on which Android version the phone is running. This allows you to do stuff like revoke permissions for apps, block ads, and change how Android looks and behaves.
Do you have a phone in mind already? If not, what's your budget?
Click to expand...
Click to collapse
Thank you for your help. I had a rooted phone, but a friend did it for me. Now I have a S8 active on Pie and from my research the bootloader I have (V5) is not rootable. I'm definitely not well versed in Android though and could be wrong. That's why I was wondering if there was a device that offered full control without the need and rick of rooting. If there's not, could you suggest one that is perhaps the simplest and least risky to root? I don't need top of the line, I don't game or anything and would be fine with getting something used. thanks again!
Luckily, there is a way in stock Android to control permissions! I forgot about it when I was typing my previous response. Here's an overview: https://www.howtogeek.com/355257/can-you-control-specific-permissions-on-android/ Hope that does what you're looking for.
If you want to do more with a rooted phone like block ads, there are some that are easily rootable, like the Google Pixel series. Here are a few options: https://www.androidcentral.com/best-phone-rooting-and-modding I liked the Pixel 2XL I used through my previous job, and I've heard good things about the other Pixels, for what that's worth. I haven't tried the other phones in that link, but the OnePlus phones have an excellent reputation.
There are many other phones that have varying degrees of difficulty for rooting, but I'm not aware of any relatively recent ones not on that list that I'd consider easy to root. I've found that the best approach to finding a new phone is going to GSM Arena's Phone Finder to put on my criteria, then coming back to XDA and searching through the forums to find out whether my prospective phone of choice has root yet. As you've discovered with your S8, some phones just never get there, which is pretty frustrating.
I hope that helps! Holler if you have any other questions.
Well, that's my main issue, you can only control certain permissions there. When I click "all permissions" I can see them all, but not turn them off. It's just a bummer that one has to go thru all this rigmarole to control a device they supposedly own. I was hoping maybe someone made a device that you could control stock, but I guess that was wishful thinking. Thanks again.
SteveJustSteve said:
Is there a phone/android version that allows someone whos not an Android expert to actually have control over what their phones doing? Or is it just not possible nowadays for a regular person to fully control the info their phone sends?
Sorry if this sounds cynical, it really is a genuine question.
Thank you.
Click to expand...
Click to collapse
You must distinguish between Android OS itself and the apps that run on it: Android OS has no permissions you can invoke/revoke, only hardware/OS specific settings can be made there, but permissions can be granted/withdrawn from an app - if its developer has allowed the latter. To change the permissions of an app basically no rooted Android is required, this is done either via Android->Settings or via a 3rd-party APK editor.
BTW: It exist 3rd-party apps that can show you what apps are sending/receiving data over Internet.
Hint: Use your Android phone without Google.
Is root required to disable hardware?
SteveJustSteve said:
Is root required to disable hardware?
Click to expand...
Click to collapse
No, only a hammer. :laugh:

Categories

Resources