Developer Options Marshmallow Vs. Lollipop Mock Location Issues - Samsung Galaxy S7 Questions and Answers

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

[Q] Finding solution for instant switching tool (Root/Unroot) w/o reboot

Hello.
Thank you for your click to read my entire thread.
I prepared two version of my story with different length.
Herer is a longer story
Shorter story is available at the end of this thread.
My family and I have android-based smartphones.
We are Korean and have lived in Korea.
1.
My younger brother chose his first smartphone as Nexus S,
but my father chose his phone as GalaxyS.
My father and younger brother are not familar with electronic gadget,
so I always help them when any change is needed to his smartphone.
2.
Banks in Korea hate rooting action.
In the recent,
they decide to refuse providing smart-banking service
if customer try to use banking service with rooted smartphone.
There are many complains about this decision but no follwing measure was occured.
Bank company's refusing mechanism is following.
When the smart-banking app is excuted, they check some files related rooting.
If the files were found, they stop to work and are automatically closed with warning messege.
3.
I found the 'Tegrak Kernal' and 'Tegrak app' composed by a Korean.
With these kernal and app, user can switch between Rooted and Unrooted by just one tap.
The kernal is neither a rom nor rom-dependant thing. It may stored in recovery reign.
Switching mechanism what I understood is simple.
When menu in the app is tapped, by excuting some script, su related files are completed deleted.
This action does not require any rebooting process.
In one or two seconds, unrooting (by deleting files) is done.
Finally the smart-banking app works again immediately.
Rooting (rerooting) is similar. Tapping another menu button in app, rooting is completed.
Titatanium or Root explorer works again.
This function is fantastic for Koreans.
4.
Tegrak kernal is dedicated to Galaxy serise.
There is no plan to make the kernal available for other devices.
5.
I love HTC's phone and want to keep using the phone with smart-banking feature.
My yonger brother also have to keep using his Nexus S until contract is ended.
I tried some search about rooting/unrooting without reboot in XDA, but I have no results.
In my thought, XDA is the most advanced place for smartphone in the world.
I also think that there are many developers outside Korea than inside Korea.
Idea about swithing without reboot may not unique or special.
I'm sure that a app for "swithing rooting/unrooting without reboot" is alrady exist somewhere.
6.
Can I get any advice or a clue about solution for "swithing rooting/unrooting without reboot" which work for any device (or just not os-dependent)?
The exact name or address is welcomed, but suggesting keywords is also appreciated.
Becasue English is not my native language, I have difficulties in expressing my need or goal in English for a good search result.
Click to expand...
Click to collapse
Shorter story
Tegrak is a kind of recovery and is made by Korean developer.
Tegrak have a function of switching between rooting and unrooting without any reboot.
Tegrak is dedicate to Korea's famous model, Galaxy serise only.
I'm finding such a app or thing for Nexus or DHD.
Any help for finding is appreciated.
Click to expand...
Click to collapse
..
I found this app:
OTA RootKeeper
From the app description:
"A bonus feature is present, allowing you to un-root your device while keeping a su backup.
This way you can naively hide root until you choose to restore it via without further complications.
This nifty feature work on every rooted device.
** Temporary un-root statement **
This feature is designed for dev purposes in order to test their app with or without root.
The goal here is not to encourage stupid and unacceptable behaviors by movie or content sellers trying to prevent you to purchase or watch digital media you purchased if your device is rooted.
Vote with your dollars: Don't accept being a customer of companies restricting your freedom with defective and and inefficient technical measures."
Thank you, Election Day.
Fight against company or government is very painful and scary things for me as a person in Korea. There are many complains but concentrated protest was not found yet in Korea.
Fortunately, a Korean developer opens file/folder list which should be deleted prior to running smartbanking app. That could be helpful later if I find some tunable tools for temp unroot.
Thank you very much el_psycho.
Your found is the exact what I want.
I just tested the app, but it requires some improvements against bank apps in Korea.
Therefore I leaved an appeal to the author of Rootkeeper.
http://forum.xda-developers.com/showthread.php?p=21769752#post21769752
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1241517&page=7
Click to expand...
Click to collapse
Thank you for your advice again, el_psycho.

Android m permission control, is it worth an upgrade?

I've been looking at Android m since it came out.
However my oem will not be supporting the majority of my devices
(That's you Samsung 2 year support has me thinking of never buying your product new again).(Not that many others are much better).
So with the bugs that are ever present in custom Android roms and the developer never ending rush to the next update while the last aosp is not retail stable on most devices(come on Google wait two years and get the base or rock solid already before messing yet again with things).(I understand developers want to play with new features and new devices, but so many people have a 2 y old very capable device that just needs security updates). I have been reluctant to update from 4.4 that most of my devices run solid on.
How much more security has Android m brought to the table?
Is the permission manager worth the update from 4.4 or 5.1 ?
With all the new apps supporting permission denial without crashing going benefit the older os with permission blockers or xprivacy running?
Is the permission paranoid user better off waiting until the last minute to update to miss the worst of the bugs left to squash or just jump in now and live with them?
What is your opinion?
Nope, the permission manager isn't worth the update.
System apps crash when you restrict them too much, even if you restrict permissions they don't need to work properly, which wasn't the case in pre Marsh Mellow ROMs.
Oh well, they crash if you restrict them through the built-in permission management system bla bla, but they probably won't if you restrict them with third part apps...
Plus, at least on the phone I'm currently working on (but I guess it must be the same on all Mesh Mallow phones), the permission system became very dishonest, to say the least.
When you install a new app you don't see all the permissions you are about to grant but only the categories (remember the last changes in the play sore?), which tricks you into wrongly believing that the app doesn't have too many perms. Once installed you can't review neither the permissions nor the categories, pfuut, gone with the wind...
All this "security" hype about Ma Shallow isn't really about security but about making you feel that thanks to google and its well known abnegation you are secure and that you don't need anything more to protect you further.
There's nothing worse than a false sense of security...
What else to say?
The auto start manager, well done, except that third part apps offered it since the days of ICS, if not GB, and that a script can take care of that stuff without even installing anything.
All in all if security is your thing don't bother, moreover than xposed doesn't work on some Mesh Hollow ROM, leaving you without any other alternatives but to secure your ROM on your own.
It's of course doable if you know how, but it'll take time and a lot of decompilation/recompilation/testing.
New features?
Boah, 2-3 gimmicks as usual, fancy colors animations widgets I don't know what bling bling yo yo, not worth the money unless you really need a new phone.
Security patches?
Boah again, they made everybody paranoid with stagefright and the like but hey, do you really think you'll get hit?
What are the chances, unless you download cracked apps or are naive enough to let anyone touch your phone without the screenlock on?
I'd say more or less the same than meeting Santa Claus in person, do you believe in Santa?
I personally don't but still, those vulnerabilities are good for business, it makes the Santa crowd buy newer and more "secure" phones, cool...

Some questions regarding rooting my Samsung S7 G930A

Ok so to start off my ultimate goal is to be able to install chainfires systemless root to be able to install xposed systemless framework to then install the hide mock location program.
All of this is (most probably already know) in an attempt to be able to gps spoof in pokemon go without being banned. The only reason I am doing it is because I live in an extremely rural area with literally no pokemon around. I don't plan on taking over any random stuff gyms or doing anything else to infringe on any other players. Just find some pokemon and collect from some stops.
I have already attempted this only using a gps spoofing app but as expected I have been soft banned many times.
Basically, I'm just trying to find out if it is safe to root my S7 G930A. I have already looked at this thread:
http://forum.xda-developers.com/att-galaxy-s7/how-to/root-s7-att-g930a-g935a-t3410538
Will this method (that seems like the only working method for the AT&T) erase everything on my phone? Is there an increased risk of bricking my phone using this method than anyone using the normal chainfire method?
With all that being said if there was an easier way to not be soft banned or to not have to cheat at all outside of driving a couple of hours to a decent location I would love to hear it. As far as the gps spoofing goes I don't see much of an issue with it as long as I'm not taking over gyms, which I don't plan to. I'm pretty sure that I am being soft banned because they are detecting that my ip address is clearly not an ip address anywhere near where I am changing my gps. I have looked into vpns to attempt to bypass this but I haven't found much luck.
Anyone have any ideas or suggestions. I know I shouldn't cheat but I feel like this is my only option at the moment. Oh and if this is just completely not the place for this kind of question you can tell me that too haha

Security-related arguments for root and custom rom usage...

Exodus, a popular, albeit closed-source, crypto wallet app recently stopped working on my device. After a few days of back-and-forth troubleshooting via support, they somehow realized that my device is both rooted and running a custom, open source, community-supported ROM. They told me this was no longer allowed because it is far less secure than running the proprietary ROM. I countered with both personal testimony (back when I had a Blu phone, and a year later they got kicked off Amazon due to spyware streaming customer data out without consent) and common fact that OEM ROMs are almost always packed full of bloatware and spyware. I countered that installing a reputable open source ROM with only those apps I want and need is better. I argued that root gives me the ability to use AFWall to block outbound access to apps that I don't want having having access to the Internet without my permission. I could have argue that continuing to use a 1-2 year old phone that no longer receives security updates when I could use an open source ROM that does is better. I also provided a few public articles showing how frequently apps from the Play Store and other "OEM" stores are caught abusing their users' trust and performing malicious action. My point was that it's not correct to just automatically assume that having root and using a non-OEM ROM is less secure. That's a falsehood. But that said, I am interested to know what the XDA community thinks about that. And if the XDA community has any facts about custom, open source, community-supported ROMs being more secure than OEM ROMs, I am interested to further arm myself. And of course, I am completely willing to be instructed by the XDA community that indeed Exodus is right and using a custom ROM and having a rooted phone is completely, inherently, automatically more insecure than using an OEM ROM full of bloatware and spyware, not having root so that any rag-tag app can stream data back to home base, and falling behind with security patches because the vendor is either too slow to release or decides my device is no longer worth supporting.
You can't blame them for not troubleshooting unknown firmware. You changed the playing field.
Less mainstream use and support* is one of the disadvantages of custom roms and rooting.
I run stock and use other methods to kill bloatware. Zero brick risk, little down time and they run well.
I'm not saying don't root etc... but you knew the job was dangerous when you took it.
*this can have potentially far reaching and multifaceted implication$
@blackhawk I'm pretty sure it wasn't broken on my phone. One day I opened the app and it said I needed to update to continue using it. So I thought maybe the app just had failed to automatically update from the Play Store. But shortly thereafter I found it wouldn't update. That led to opening support ticket with them which eventually led to them saying it no longer works on rooted devices. Their argument was that they were attempting to protect me. My rebuttal was that I don't want their protection, I want my freedom back. They should focus on making their app as secure as possible and then, if they discover I am running it on a rooted phone, then give me a warning box and force me to accept it but don't just take away my freedom.
The irony of their stance is that they still provide the Linux program. And who doesn't have root access on their Linux computer? Or their Mac or Windows computer, for that matter? I can completely understand if they don't wish to troubleshoot the installation of the Debian package or even the use of the zip on every Linux version out there. I wouldn't either! But that's completely different than saying, "Oh, you have root access to your Linux/Mac/Windows computer? We can't let you use our program anymore." That makes zero sense, and it's the same nonsensical argument they are making for rooted Android phones.
I run stock N10+'s because they're easier to troubleshoot, maintain and it doesn't trip the Knox efuse. I have to add a package disabler and do some optimizing but it's child's play for me to do it at this point.
Unfortunately if you root you're going to have to suck it up and do the work needed to optimize it.
Same thing I do with stock but with more tools at your disposal... after the learning curve.
It's this learning curve, the chance of bricking and the damage that can be inadvertently done to the OS with no access restrictions are some of the downsides. Rooting takes time to learn and perfect. With unlimited power, blah, blah, blah.
I rather just do basic infrequent troubleshooting and have fun... my current load is over 1.5 yo, still fast and stable.
I don't update the firmware because that breaks things. No updates needed once you optimize it and find any needed work arounds... it's good to go. Anything from Pie up is pretty secure; they have some vulnerabilities but in practice this isn't an issue... unless you do something stupid.

Is my Girlfriend is a computer hacker?

Hi, I am not new to computers phones and development but it's been years and a lot has changed. I went to school for software design and I learned on Visual Studio 6.0. So for anyone in there 30's and older you all remember how 6.0 was. Well alot has changed since 6.0 but regardless I know when someone has been messing with my phone a s or computer. I am going to try and post all of my syslog that I have saved and any new that I see. Also ibam going to try and post what open source software that I notice my phone now has licenses for. I am on a Samsung Note 10 plus 5G. And I am almost positive that my girl is responsible for the modifications done to my phone but she screams that she only knows how to play games call and text. I need someone to review my information and any information that anyone needs and tell me if my phone has been modified and if everything could have been done remotely. My ultimate question is could this all have been done remotely or would any of it and I mean even the smallest thing have to be done locally on the phone. If every single modification could all have been done remotely then maybe she's telling the truth but if just one thing had to of been done locally then she's responsible somehow. And then I need to know how to fix all of this and set up secure to prevent it from happening again.
you claim you're developer but provide logs as screenshots... seriously, if you can't trust your girlfriend what you need help is a couble care course or psychotherapist.
I doubt your Samsung Galaxy Note10+ bootloader locked device secured by Knox is tampered in any kind at all
What i'm seeing here is you using your phone with samsung packages working. It's mostly sounds running, you unlocking the device, setting an alarm ect.
Bare in mind google and apps use location alot so the location is i would say the norm. The more apps the more times location is called.
if you are concerned get dmr checker and check security levels, has the device been rooted and displays the true code? Really worried check all your apps then disable location or use odin to fully wipe the device but from what i can tell this is possibly paranoia
Whether your girlfriend can be trusted or not is not the problem. Maybe she is really hacking your phone or maybe you are just paranoid, I can't tell. Either way you two should break up before you break each other.
.. or just a week digital detox

Categories

Resources