Related
***Sticky this please
Check out this application I put together. It is a simple stand alone app for true tethering over wifi, you must have a rooted phone for this app to work....
http://www.androidactivity.com/tetherWifi.html
The main purpose of this thread is to discuss issues with the application. For instructions on how to use it read the webpage from the link above.
Good deal will try it out as soon as i get sp3, is it compatible with new update? thanks for this!
Any chance of making this open source?
If it just uses the same method as http://forum.xda-developers.com/showthread.php?t=474470 then it would be pretty helpful for those of us trying to make a frontend to command line applications.
amgupt01 said:
Any chance of making this open source?
Click to expand...
Click to collapse
Pretty Please... I do appreciate the effort and at that same time, I like to know what I am giving root access to. But, really - I'd like to be able to modify it to my own network environment. I like to customize the dnsmasq.conf a bit for my own peace of mind...
Thanks again, this is the beginning of a great piece of work...
This is really nice!!! The old way with terminal was getting old. Thanks!!!!
Could you have a status icon at the top toolbar to show that the tethering service is active?
Tested, worked flawlessly. Unscecured, of course, but freakin' sweet if you can't get another network. Tried this from my house, worked great on 3g. Work VPN functioned w/o issue.
Nice! Confirmed working with Vista laptop.
I'd like to also voice support for open sourcing this-- or for removing the root requirement if you could get that worked out. I am very appreciative that you've pulled this together but at the same time feel reluctant to install any software that will be running under root that isn't signed or at least has the source code available.
Keep up the great work!
please add an option to change ssid, and settings, and we definately gotta find a way to secure the wifi
I just made a couple bug fixes and put up a new version this morning.
This is still beta and I am looking into making a lot more things configurable.
Right now it is not secure. It only will DHCP out one IP, but it does NAT forward the whole range of 10.0.1.X
I understand everybody's concern about making it open source for root access, at this moment I am not going to make it open source. I would like to figure out a way to make it work without root in the future, but if I cannot I may make it open source.
This may help you out with your concerns, this is what the application does:
-it unpacks files to the /data/data/com.androidactivity.tetherWifi/ directory only on the first run of the application, installing an upgrade of my app will re-unpack the latest files in this directory. a chmod of 744 is done to all of these files.
-manual configuration of dnsmasq.conf, tiwlan.ini, etc.. can be done by modifying these files in this directory. You need to run my application once before modifying, so that these files get unpacked. If you ever upgrade my app, make sure you back up these files before upgrading, because on upgrade my app will overwrite these files.
-when you hit start, i disable wifi if it is on and then run the tether.sh start script.
-when you hit stop, i run the tether.sh stop script, I also enable the wifi back if i had disabled it before running start.
-to see what tether.sh start and stop does, take a look at the /data/data/com.androidactivity.tetherWifi/tether.sh file
stats555 said:
Good deal will try it out as soon as i get sp3, is it compatible with new update? thanks for this!
Click to expand...
Click to collapse
I doubt it needs service pack 3. I just confirmed it working on my machine which has service pack 3.
My bluetooth tethering app, on the other hand, works better with service pack 3, and I do recommend upgrading if you are going to use that app.
moussam said:
***Sticky this please
Check out this application I put together. It is a simple stand alone app for true tethering over wifi, you must have a rooted phone for this app to work....
http://www.androidactivity.com/tetherWifi.html
Update:What this program does..
-it unpacks files to the /data/data/com.androidactivity.tetherWifi/ directory only on the first run of the application, installing an upgrade of my app will re-unpack the latest files in this directory. a chmod of 744 is done to all of these files.
-manual configuration of dnsmasq.conf, tiwlan.ini, etc.. can be done by modifying these files in this directory. You need to run my application once before modifying, so that these files get unpacked. If you ever upgrade my app, make sure you back up these files before upgrading, because on upgrade my app will overwrite these files.
-when you hit start, i disable wifi if it is on and then run the tether.sh start script.
-when you hit stop, i run the tether.sh stop script, I also enable the wifi back if i had disabled it before running start.
-to see what tether.sh start and stop does, take a look at the /data/data/com.androidactivity.tetherWifi/tether.sh file
Click to expand...
Click to collapse
Thanks for this gonna test it out. I was thinking of making something like this you beat me to it.
http://code.google.com/p/gtether/
Similar project, open source.
Do not support closed source projects.
Especially those that require root on your phone!
miseiler said:
http://code.google.com/p/gtether/
Similar project, open source.
Do not support closed source projects.
Especially those that require root on your phone!
Click to expand...
Click to collapse
The gtether application clashes with the ****ty superuser application on the JF releases... it's unusable for me. However, Moussam's works fine.
With GTether, everytime I try and connect my PC - it just goes into an endless loop of approving the super user access, even if you select "Always" it just doesn't work. Which is a shame, because GTether is clearly a better application.
I found the same issue with the endless loop with Super user.
vr24 said:
The gtether application clashes with the ****ty superuser application on the JF releases... it's unusable for me. However, Moussam's works fine.
With GTether, everytime I try and connect my PC - it just goes into an endless loop of approving the super user access, even if you select "Always" it just doesn't work. Which is a shame, because GTether is clearly a better application.
Click to expand...
Click to collapse
Well, the GTether application isn't even Open Source. The SVN for it has no code and the downloadable "source code" is just a gzipped .apk file.
Also, the Super User app is far from ****ty. It is the only thing protecting your phone from people releasing apps on the market targeting rooted users. If someone released an app on the market that ran su without your approval, they could wreak havoc on your phone and potentially brick it.
miseiler said:
http://code.google.com/p/gtether/
Similar project, open source.
Do not support closed source projects.
Especially those that require root on your phone!
Click to expand...
Click to collapse
Everybody, do your homework first before you start making stupid comments. First off gtether is not an open source app. My app is simpler and more stable. Gtether is also a good application, but I wanted to create something that had everything packed up into one install without having to run any shell commands.
I do not have the bells and whistles yet, but I am working on them, this is just a beta release.
amgupt01 said:
Well, the GTether application isn't even Open Source. The SVN for it has no code and the downloadable "source code" is just a gzipped .apk file.
Also, the Super User app is far from ****ty. It is the only thing protecting your phone from people releasing apps on the market targeting rooted users. If someone released an app on the market that ran su without your approval, they could wreak havoc on your phone and potentially brick it.
Click to expand...
Click to collapse
Well, no. The source tgz has all the components of the tether-1.6 app in it, in additional to the apk file (for whatever reason). I suppose you could argue the iptables source isn't present in the file, but that is available elsewhere.
And apps that run su with your approval are just as likely to brick/rootkit.
Well by "source" I am referring to the actual source code used for the .apk file which is run on Android. That's the part which is installed as an application and is actually using the binaries from the tether-1.6 kit as root and running in the background to notify when new users connect.
Also, when I say that SuperUser protects your phone, I'm assuming that people will actually do research before allowing an app to user root privileges and will block an app which has no need to use root whatsoever.
miseiler said:
Well, no. The source tgz has all the components of the tether-1.6 app in it, in additional to the apk file (for whatever reason). I suppose you could argue the iptables source isn't present in the file, but that is available elsewhere.
And apps that run su with your approval are just as likely to brick/rootkit.
Click to expand...
Click to collapse
if it makes everybody more comfortable i can post the script files that are run in my app. su is only needed to run these script files. these files are unpacked into /data/data/com.androidactivity.tetherWifi on the first run of this application and can even be altered to whatever config you want afterwards. su access is not needed until you hit start or stop. if you are concerned install my app and run it and dont grant su access and you will be able to see the unpacked script files in the dir i mentioned, and even alter them if you want.
Hi, I did a simple tracking application to know the phone location if I lose it or it gets stolen.
I'd like to have some thoughts and suggestions, so if someone wants to try it just download it here
Thank you!
post it and let us check it out man, so we can tell you if it is worth anything or not
Any tracking program is going to be easy to bypass...
Alt+W
Turn of GPS
Latitude is the same deal, if you wipe, you lose the log in information on the phone and therefore, it can no longer be tracked.
That being said, the only "true" way to have something like this work (regardless of sim cards/wipes) would be to somehow track the phone by IMEI/SN through a combination of internet usage, cell towers, and GPS. Even though the GPS being turned off is a possible work-around, it renders the phone much less useful. It would also need to be installed with an update so that wipes are useless.
well, personally i have rooted my g1 and installed the app in /system/app, so i think a factory reset shouldn't delete it (am i right?). and gps and network location are automatically enabled for a 60 seconds location scan, then taken back to the previous state.
if you want to check it out, i have put everything here.
all suggestions are welcome!
has anybody tried it? i only received some feedback via email
ajejee said:
has anybody tried it? i only received some feedback via email
Click to expand...
Click to collapse
Says Installation Unsuccessful. Tries to copy over "Android System"
ADP1.1 RC33
interesting. i'll try to do a fresh install on both my g1 and the emulator.
What sort of unique features can the app offer?
Currently I'm using GPS Tracker, which is supplied by instamapper.com, and it allows me to have a website such as this: http://thrash-tracker.co.cc/
If my phone gets lost or stolen, I can just check that website.
I released an application on the Market called Phone Finder. It will email you at a custom frequency (default 1 day) with it's location.
tried it but it didn't work.
ADP1.1h.
I'll give it a try. I'm currently using Where's My Android... but sometimes it says that I don't have a data connection. Not very reliable.
ThrashWolf: about instamapper, a user who's trying my app said: "the thing tht I like the most is that if someone where to steal it they wouldn’t know its tracking, unlike the Gps tracker from Instamapper that lets them know its tracking".
However I'll try their service and see what they offer
Koush: i'm a klaxon user and i love it, will install your app as soon as i find it on the market!
mrjay: could you please be more specific? didn't install? thank you very much
i installed it, run it, got to the username/password creation window and after that nothing is happening. i restarted the phone and still nothing i try to run the application and no result. the screen is flickering for a second trying to load the application and that's all.
that's how it works! i designed it to be just a service that runs in the background, you install and it does its work without user interaction.
have you tried to login to the website to see your location and modify settings?
I added some features like activation via sms. Info&download, as usual, on www.trackdroid.org
now i get it. i logged in and watched last entries. looks promising
thanks! if you have suggestions about features to add, just let me know
i was using on my old WM phones this application and i really miss it. maybe you can inspire from this application.
I had some issues with the ADB commands for preparing my rooted Nook Color for on-device app install (primarily due to microcrap's 64-bit Vista) so I found a very easy method.
In the Market, there's an app called "Sqlite Editor" from the folks who make "Root Explorer" - it's about $3.07 US$ but I bought it anyway.
With this [AFTER A BACKUP!] I was able to directly edit the settings.db (sub category SECURE) and change the following:
'install_non_market_apps' from the default value of 0 to 1 and following a SAVE and REBOOT I can now install directly from my SD Card.
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Dare I do this???
I also posted this in Mobileread's excellent Nook Color Forum and I was thinking that may we should also acknowledge them as a great forum for our beloved Nooks!
docfreed said:
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Dare I do this???
Click to expand...
Click to collapse
LOL...If only it were this easy.
I had no issue with installing apps from the sd card after rooting/installing mkt and gapps.
Depends on How You Rooted..
I'm not certain but some rooting methods have market/gapps built-in, some don't. I used Autonooter (after upgrading to 1.01) and market & Gmail just appeared - I never had to install anything else.
If you used Autonooter then you wouldn't have to do anything to be able to install non market apps. Maybe just toggle the setting in Nook Tools if anything.
docfreed said:
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Click to expand...
Click to collapse
Its NOT that simple, its been turned on in the kernel & custom ones built for it with nothing.
If you see the "salting nook" posts so much as been done trying to get it to work, most expect something ground breaking to come from actually looking at the pins on the chip it self an connection through the MoBo.
Amd sold faulty quad cores as triples so it could be that the chip/Mobo cant do it. Could be a easy hardware mod but TBH so much deep thought an attempts have been seen in IRC i dont see a "virtual fix" anytime soon.
But that said im an idiot so could be 475% wrong
Yeah, I tried toggling Nook Color Tools per the instructions - never seemed to work for me. Anyway, it appears to be just a one-shot adjustment any way it's done (at least till we get FroYo) so I'm happy.
Merry XMAS everyone
docfreed
sqlite not working for me
Purchased Sqlite, when trying to install, exits without loading apps. Any suggestions? Rooted with older booker and then re-rooted with pre 1.01 autonooker. Thanks. -
I have a kernel and u-boot that enables the bluetooth portion of the module and sets up an rfkill device. hciattach will detect it as a TI Bluetooth module and will load one of the TI bluetooth firmware scripts, but then complains about a missing socket or something. It sounds like a software error more than anything that might be wrong with the hardware.
What this means is that the Bluetooth part of the WiFi module isn't just left disconnected and the link to the CPU is working. But we don't know if the antenna is set up to share between wifi and Bluetooth or if the hardware is otherwise missing something that would keep it from working.
If you have experience with getting TI WiLink Bluetooth working in Android or Linux, or know someone who does, PM me or join us on Freenode channel #nookie. We're really close!
Update 09.12.17: The methods below may not fully work on the latest OS versions. There is an ongoing discussion in the last pages so I hope it gets cleared out eventually, sadly I've been busy with my studies and haven't touched my phone since initially making this thread (it's on OOS 4.0.2). I write this just to make sure I don't waste your time accidentally, so please check the latest replies if you're on newer OS versions.
Hello everybody,
*the undermentioned methods and app(s) require root*
I have asked you guys in the AKT thread if you would like to see a small tutorial on how to stop the constant "com.google.android.gms/.measurement.PackageMeasurementService" and "net_scheduler" wakelocks that might or might not be responsible for the device waiting longer than it should before dozing off.
Please keep in mind that this method does work for me, and might or might not work for you, as everybody uses different things/apps so in case you see unwanted behavior, just revert back and sigh that the method has failed you.
I am not responsible for any hardware-/software damage that may occur upon using these settings.
So, now that we've got all the generic stuff out of the way, first few words about why this might bother you:
1) You don't like your device doing stuff you didn't make it do.
2) You want to minimize wakelocks
3) You're here because you just saw the two beforementioned wakelocks and already decided you want to get rid of them.
So, regarding the first one, all I can say is I got the method from this reddit post , which briefly explains which services are doing the waking and what they are. Starting with "At the heart of Firebase is Firebase Analytics, a free and unlimited analytics solution. .." got me raising an eyebrow, as I don't like handling control of my device to other people, without me even knowing.
UPDATE: I have merged the two approaches into just using one app and making the changes on a global level, so you can just do them in like 5 minutes and forget about it, but in case you have problems with disabling package measurement you can also check the hidden text just below for instructions using another app, which was basically "the old way".
So to get rid of the "snooping", as already described in that post, you need to download MyAndroidTools.
Disclaimer: Disabling some services/receivers may "crash" the app. I found it is normal, just go back to where you were and check if you managed to disable the thing you wanted, if yes, then it was successful.
1. Open the app
2. Click on the top left to open the panel, click on Broadcast Receiver.
3. On the menu that opens go to the right column named System. Click search on the top right, type "Play" and choose the Google Play Services option.
4. In the search bar there type at least "ana" and disable the two found results with the names "AnalyticsReceiver" and "AnalyticsSamplerReceiver"
5. Hit x and search again for at least "meas". You will see three results with the names "AppMeasurementInstallReferrerReceiver", "AppMeasurementReceiver" and "PackageMeasurementReceiver*". Disable all three.
****Update 15.02.17*** Apparently this one resets every once in a while, I blame this again on Google's efforts to have their spying on, but anyways. Go to services->system->Google Play Services->search "meas"->disable both "AppMeasurementService" and "MeasurementBrokerService". The third one (PackageMeasurementService) will restart too so don't bother. This should do the trick though.
6. There was discussion about "Campaign Tracking" . I only found it in the same System menu, in Android Pay, by searching at least "cam" you get the result "CampaignTrackingReceiver". Disable it if you feel you want to. I don't use Android Pay and cannot say if it breaks something there, but otherwise have it disabled and haven't noticed any problems so far.
7. Search for Google Play Store in System. In that option, search for at least "app" and disable "AppMeasurementReceiver". Hit x and search for at least "fir", then disable the two results with names "FirebaseInstanceIdInternalReceiver" and "FirebaseInstanceIdReceiver"
8. Done. All the setttings are now global for any sort of app measurements, as far as I know.
This is the "old way" of dealing with app measurement. If you have done the steps above just ignore (hide) this part and continue with disabling net_scheduler below.
So to get rid of the "snooping", as already described in that post, you need to download Root Package Disabler or equivalent alternative.
ATTENTION: As per the last version of the app, I see there might be a bug which reverts some settings when you use the search bar, so please try and find the services by hand in stead of searching, as it is more reliable.
1. Open the app
2. Start with the left-most pane, e.g. "Installed". There you can see all your installed apps
3. Click on the first app on the list, it will display a small menu. Apps that use services will have the bottom-left option named "SERVICES" available, click there. This will take you to the services list that this app uses.
4. Click on the searching icon on the top-right in order to filter the services we need disabling.
5. Write at least "appm" . If the AppMeasurementService is used by this app, it will now be displayed.
6. Tick that off (the switch will turn gray)
7. Hit x, and search again for at least "fireb". This will display all services that use the Firebase SDK. You may also check under the name of the service and see the word is contained in the "executable name", so it might not always have "an official" name that states Firebase, but still use one of their "executables" (sorry for lack of detail)
7.1 Check for any other services that have "analytics" in their description, although I haven't checked if this stops something useful, but I doubt it.
8. When you're done with the current app, it will no longer call these services and cause wakelocks as long as the services remain stopped. To my experience the settings stay after reboot, it's just the above mentioned bug you have to keep in mind since it happened to me now while making the guide, and I know it came with the latest update.
9. Go back to the installed pane and maybe tick on the star next to the app in question. It will be added to the "favourite" list where you can have all those apps and don't bother to search them again if needed.
10. Repeat from step 1 for the next app and go through all your apps. If not you will still get calls to this service from the apps that still have these services on. Also a reminder here, you have to remember and check every new app you install, as most apps do have the service enabled.
11. After you're done with all apps in "Installed", check out bloatware (I think I haven't found anything there, but it's worth checking).
12. "System" apps that I know have some of those services: Calendar, (probably) Chrome (I have that disabled so dunno), Drive, Duo, Gboard, Google Play Services, Google Play Store, Google VR Services.
Here are two pictures how an app's services list looks like, and one with some of the services disabled:
all services on
some services off
After doing these steps, you should charge your battery to 90% to reset the battery statistics and you should see that the "com.google.android.gms/.measurement.PackageMeasurementService" wakelock no longer occurs (or stays really, really low, and not thousands like before). If you still have it after all this, then you probably have an app you haven't disabled the services for.
The second approach will get rid of the "net_scheduler" wakelock. Thanks to @denon480 for the idea, it's post #34 in this thread It involves installing (again) MyAndroidTools or equivalent alternative.
1. Open the app
2. Click on the top left corner to open the menu panel.
3. Click on Broadcast Receiver
4. Navigate to the System pane
5. Click on search on the top right. Search for Google Play Services. Click on them when they show up
6. In the search top right, write at least "sche" and you will see the two receivers responsible for the "net_scheduler" wakelock, "SchedulerInternalReceiver" and "SchedulerReceiver" . Here's a picture how it looks
7. Switch the first one off. The app will quit, don't worry.
8. Go back to where you were (steps 1 to 6) . You will see that you indeed managed to swtich that receiver off.
9. Switch the second one off. The app will quit, again no worries.
10. Check if you managed to switch the second one as well. After that you're done!
I hope I could help you guys out. I know there is nothing fancy in these methods but felt a thread might be useful as I saw a good number of requests when I mentioned it in the AKT thread.
Also sorry for misleading the guys I already told it was going to be a short guide, I honestly thought it would take way less words than it did. But I think it is for the better.
Have fun.
* Reserved *
Going through this guide, I was able to get the services disabled through root package disabler, bit my android tools kept force closing for some reason.
*edit* uninstalled, rebooted, reinstalled, and was able to get the app to stay open, and got them disabled. I'm curious to see what my wake locks are going to look like tomorrow. This is pretty much the nougat answer to amplify, huh? =)
MeggaMortY said:
* Reserved *
Click to expand...
Click to collapse
I think Everything is fine or?
tzbigworm said:
Going through this guide, I was able to get the services disabled through root package disabler, bit my android tools kept force closing for some reason.
*edit* uninstalled, rebooted, reinstalled, and was able to get the app to stay open, and got them disabled. I'm curious to see what my wake locks are going to look like tomorrow. This is pretty much the nougat answer to amplify, huh? =)
Click to expand...
Click to collapse
Hope it gets rid of those for you too. If I remember correctly I noticed the problem since Nougat, but then again I've been on Android since only a few months, coming from a big pause. Last time I was around we were rocking the HTC HD2 and had to deal with very different problems.
1+3_FA said:
I think Everything is fine or?
Click to expand...
Click to collapse
Yup looks great.
MeggaMortY said:
Hope it gets rid of those for you too. If I remember correctly I noticed the problem since Nougat, but then again I've been on Android since only a few months, coming from a big pause. Last time I was around we were rocking the HTC HD2 and had to deal with very different problems.
Click to expand...
Click to collapse
Crazy how much of a beast that phone was. People forget it's actually a windows phone, Android was put on it so much lol!
Thanks for the tips. Works great!
Thank you for your awesome work!
I have two more questions:
1. What about CampaignTrackingService? Could we disable this one as well?
2. In MyAndroidTools under Broadcast Receiver there are lots of receivers like AppMeasurementReceiver or FirebaseInstanceIdReceiver. They also need to be disabled or disabling the corresponding service is sufficient?
Thank you very much
youknownothing said:
Thank you for your awesome work!
I have two more questions:
1. What about CampaignTrackingService? Could we disable this one as well?
2. In MyAndroidTools under Broadcast Receiver there are lots of receivers like AppMeasurementReceiver or FirebaseInstanceIdReceiver. They also need to be disabled or disabling the corresponding service is sufficient?
Thank you very much
Click to expand...
Click to collapse
1. I initally disabled that in a few apps and didn't have problems System-wide or with the apps. So you can give it a go and in case of apps not functioning you can revert those back.
2. No for now it's okay to just use the Package Disabler for that. Like I said both apps have similiar functionality, there's probably a way to find the right service/receiver and disable it globally from MyAndroidTools, then we won't need the Package Disabler. But since it did work for me and I don't install new apps more than like once a week, I just didn't bother figuring it out. I can only say that disabling certain services/activities in MyAndroidTools can brake functionality or even bootloop your device, so be very careful in case you wanna find out if it's possible.
MeggaMortY said:
1. I initally disabled that in a few apps and didn't have problems System-wide or with the apps. So you can give it a go and in case of apps not functioning you can revert those back.
2. No for now it's okay to just use the Package Disabler for that. Like I said both apps have similiar functionality, there's probably a way to find the right service/receiver and disable it globally from MyAndroidTools, then we won't need the Package Disabler. But since it did work for me and I don't install new apps more than like once a week, I just didn't bother figuring it out. I can only say that disabling certain services/activities in MyAndroidTools can brake functionality or even bootloop your device, so be very careful in case you wanna find out if it's possible.
Click to expand...
Click to collapse
Thank you for your quick response. I'll give it a try, if anything goes wrong I'll let you know.
Is there any difference between Package Disabler and Disable Service app? I've tried the former, but it was really buggy. Scrolling was so glitchy and with lots of stutters that I've accidentally disabled few services. So I've used Disable Service with success. Now I only wonder whether both apps have the same functionality. Do you happen to know that?
Thanks in advance
youknownothing said:
Thank you for your quick response. I'll give it a try, if anything goes wrong I'll let you know.
Is there any difference between Package Disabler and Disable Service app? I've tried the former, but it was really buggy. Scrolling was so glitchy and with lots of stutters that I've accidentally disabled few services. So I've used Disable Service with success. Now I only wonder whether both apps have the same functionality. Do you happen to know that?
Thanks in advance
Click to expand...
Click to collapse
Assuming you're disabling services, which we are lol (should've been more obvious for me too I guess), I'd say you should be fine, and even say maybe the same goes for just using MyAndroidTools, just scroll through the Service menu in Table Third-Party and you'll see the same settings you applied with the other app/Package Disabler. I guess I was lazy to realize that since I liked I can favourite the apps I need to keep an eye on in the Package Disabler.
So all in all you should be okay, but even better you may try and just use MyAndroidTools for both. I have some exams coming so I won't be able to test those things but will make sure to update the tutorial if indeed that turns out to be right (for the app you suggested or even just MyAndroidTools).
Give a shout in case you find out something more. And thanks for the info
Followed the guide, thanks for this like said before kind of amplify for nougat. But as I was disabling net.schedule I noticed "my android tool" can do the fire base and app activity. Under service activity and press <...>
I suppose that this two methods doesn't compromise any function of the device right? For example loosing notifications or similar
Sent from my OnePlus 3
Mr.Jay said:
I suppose that this two methods doesn't compromise any function of the device right? For example loosing notifications or similar
Sent from my OnePlus 3
Click to expand...
Click to collapse
Like mentioned, it works fine for me, and probably depends on personal usage. I don't use Google Pay for example, and Chrome, and Google Music.... but besides those I haven't had problems anyway.
Disabled everything that is said to do in this thread and it worked great while I was at home while on wifi. I had drain of .5% an hour at times. However today while at work and on LTE, drain went up to 2.6% an hour, plus wakelocks from play services was waking up the device on average over 3 times a minute. When I looked into it further there was one service under play services where all the alarms were coming from. I do have a screenshot of this. Anyone have any insight to this? For the record, I do keep location off on my device.
Edit: I wonder f it comes from moving around a lot, as I'm always on the move as I manage a restaurant. Its not really a major drain, but still makes me wonder.
NJGSII said:
Disabled everything that is said to do in this thread and it worked great while I was at home while on wifi. I had drain of .5% an hour at times. However today while at work and on LTE, drain went up to 2.6% an hour, plus wakelocks from play services was waking up the device on average over 3 times a minute. When I looked into it further there was one service under play services where all the alarms were coming from. I do have a screenshot of this. Anyone have any insight to this? For the record, I do keep location off on my device.
Edit: I wonder f it comes from moving around a lot, as I'm always on the move as I manage a restaurant. Its not really a major drain, but still makes me wonder.
Click to expand...
Click to collapse
Have you disabled location history in the Google App? The problem is this guide fixes only one concrete aspect of the whole "Google stalking experience" shenanigans. Please check for the thing I mentioned and also in Settings -> Backup & Reset, make sure Back up my data is off if you haven't logged in an account and intend to use that - these two things were also draining battery for me when I was on the go as far as I can remember.
LMcR92 said:
Followed the guide, thanks for this like said before kind of amplify for nougat. But as I was disabling net.schedule I noticed "my android tool" can do the fire base and app activity. Under service activity and press <...>
Click to expand...
Click to collapse
I did some checking on that list and am currently testing a way to only use MyAndroidTools for the whole aproach. If it turns out to be working the whole guide would get reduced to like 10 clicks, since the settings are global. I'll post more info after a day or so to make sure it is working, but as for now I see promising results.
Anyone used Franco's Servicely app to do this?
Up, I have updated the guide to just using MyAndroidTools and disabling the receivers on a global scale. So now you just have to do it once and (hopefully) forget about it.
MeggaMortY said:
Up, I have updated the guide to just using MyAndroidTools and disabling the receivers on a global scale. So now you just have to do it once and (hopefully) forget about it.
Click to expand...
Click to collapse
Will Doing like #1 post notifications from Gmail?
techusthad said:
Will Doing like #1 post notifications from Gmail?
Click to expand...
Click to collapse
Don't know what you mean by #1 - disabling the AppMeasurement stuff, e.g. first set of instructions? I haven't had problems with Gmail and I use it with two accounts on there.
H! So I am actually unsure where to post this..
Here's hoping you can figure something out and not be mad at me if this is the wrong place to post this.
Initially, i was going to post this as a Bug report on Github. However, I figured this was not correct.
Technically speaking this also isn't really an issue with magisk itself, more that adobe might have found a way to circumvent magisk anti detection methods.
In short: The App "Adobe Account Access" (com.adobe.ims.accountaccess on the play store: https://play.google.com/store/apps/details?id=com.adobe.ims.accountaccess) seems to have found a way to detect magisk and/or root, even though root detection is hidden in magisk.
The App just displays a prompt, saying "Device not supported. Sorry, your phone is not supported for Adobe Account Access.", even though the device used should be supported.
I checked with adobe community support on whether my Phone is supported or not and according to them, it should indeed be supported: https://community.adobe.com/t5/acco...-access-app-device-not-supported/m-p/11696613
I suspect they have found a way to get around all magisk anti detection methods and i would be grateful if someone would be kind enough to check if there is a workaround or if magisk's detection prevention needs an update.
Unfortunately, i don't have much more to say other than that..
There aren't any magisk log entries that would indicate something went wrong (only entries mentioning the app are"i" loglevel, one coming from hide_list_add and one coming from proc_monitor).
I could not find anything out of the ordinary in the logcat, although i suppose i could be more thorough with my search.
My technical/general info would be:
Magisk Version used: 22.0 (22000) (18)
SafetyNet integrity: Both basicIntegrity AND ctsProfile = pass; evalType = BASIC
ROM used: OxygenOS 10.0.11.GM21BA
Android version: 10
Device name: OnePlus 7 Pro
"Adobe Account Access" App version: 1.6
+++ Please feel free to ask for any additional info in case I missed it +++
Thanks in advance for any productive suggestion!
When does it display this "device not supported" message? I tested just now and could log in and set everything up without even adding the app to the Hide list, and with the Magisk app unhidden.
Didgeridoohan said:
When does it display this "device not supported" message? I tested just now and could log in and set everything up without even adding the app to the Hide list.
Click to expand...
Click to collapse
Oh? That is peculiar.. Damn, that implies an issue somewhere else i reckon ://
It displays it immediately after launching the app. The very first screen..
What phone and which OS (/ROM) are you using? Might just be that my phone is genuinely not supported and the folks over at the adobe community forum lied when saying my phone should be compatible..
Also, which android version are you on if you don't mind me asking?
You don't have any modules installed? No edxposed or lsposed, or magisk modules?
Have you tried root detection apps like Root Beer Fresh to see if indeed the app is unable to detect root? If you try any such app, remember to add it to the Magisk Hide list beforehand, otherwise the app will clearly detect root.
It's a OnePlus 3T with Android 9 ArrowOS. As stated above, it could very well be a module, like EdXposed. Or a root app, or a file or folder on your device, or something completely different.
It's not detecting Magisk at least, that's for sure...
General root hiding tips:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
@Barrel Titor
Samsung Galaxy S7 Custom 9.0 Pie, Magisk 22 root with random name, application without hiding works fine.
Hi all!
First of all: Apologies! I meant to respond sooner to this, but work has kept me occupied and the one time I actually was available, XDA Forums went down into maintenance mode..
Secondly: Sorry for maybe jumping the gun here a bit!
It does look like I should have tested this issue a bit more! I am definitely going to keep on trying to fix this on my own using the resources and methods you have suggested!
I have tested com.adobe.ims.accountaccess on my sisters unrooted OnePlus Nord.. It works fine there, which is really confusing. None of the other apps I am using show this sort of issue :c Not even my banking app!
@mario0318 Thanks for your suggestion! I know it is good practice to remove/disable all your modules. However, none of the modules I have currently installed are particularly large and they certainly do not modify much compared to what is possible. I am going to attach a list to this response, however I am also going to try disabling them one by one and see if I can find the culprit! Unfortunately, I will not be able to disable the "Google Dialer Framework" module, since it causes the device to bootloop if the google dialer app is still present.
Here is a list of all the modules I have installed and enabled at the moment:
Spoiler
App Systemizer (Terminal Emulator)
Busybox for Android NDK
Google Dialer Framework
Looki75 Product Sans font
Systemless Hosts
ViPER4ANDROID FX
Honourable mentions (these modules are completely DISABLED):
Spoiler
Riru
Riru - EdXposed
However, please note again that SafetyNet seems to be INTACT, with "basicIntegrity" and "ctsProfile" still passing and "evalType" being "BASIC".
In any case. Thanks to everyone for their contribution! I really appreciate any suggestion!
Edit: @mario0318 right after I posted this message, I went ahead and gave "RootbeerFresh" a shot. It does not detect root when it is hidden from it. This makes my leading theory to be that the app truly does not support OnePlus 7 Pro devices. Wouldn't know why it doesn't support this model in particular though. Until I either unroot or find someone with the same device, willing to install Adobe Account Access, i can't say for sure though.
Barrel Titor said:
Hi all!
First of all: Apologies! I meant to respond sooner to this, but work has kept me occupied and the one time I actually was available, XDA Forums went down into maintenance mode..
Secondly: Sorry for maybe jumping the gun here a bit!
It does look like I should have tested this issue a bit more! I am definitely going to keep on trying to fix this on my own using the resources and methods you have suggested!
I have tested com.adobe.ims.accountaccess on my sisters unrooted OnePlus Nord.. It works fine there, which is really confusing. None of the other apps I am using show this sort of issue :c Not even my banking app!
@mario0318 Thanks for your suggestion! I know it is good practice to remove/disable all your modules. However, none of the modules I have currently installed are particularly large and they certainly do not modify much compared to what is possible. I am going to attach a list to this response, however I am also going to try disabling them one by one and see if I can find the culprit! Unfortunately, I will not be able to disable the "Google Dialer Framework" module, since it causes the device to bootloop if the google dialer app is still present.
Here is a list of all the modules I have installed and enabled at the moment:
Spoiler
App Systemizer (Terminal Emulator)
Busybox for Android NDK
Google Dialer Framework
Looki75 Product Sans font
Systemless Hosts
ViPER4ANDROID FX
Honourable mentions (these modules are completely DISABLED):
Spoiler
Riru
Riru - EdXposed
However, please note again that SafetyNet seems to be INTACT, with "basicIntegrity" and "ctsProfile" still passing and "evalType" being "BASIC".
In any case. Thanks to everyone for their contribution! I really appreciate any suggestion!
Edit: @mario0318 right after I posted this message, I went ahead and gave "RootbeerFresh" a shot. It does not detect root when it is hidden from it. This makes my leading theory to be that the app truly does not support OnePlus 7 Pro devices. Wouldn't know why it doesn't support this model in particular though. Until I either unroot or find someone with the same device, willing to install Adobe Account Access, i can't say for sure though.
Click to expand...
Click to collapse
So upon Google searching "oneplus 7 pro adobe account access" it appears to be a common problem.
mario0318 said:
So upon Google searching "oneplus 7 pro adobe account access" it appears to be a common problem.
Click to expand...
Click to collapse
I cannot find any results using this search term on google other than my own post on the adobe community forums.. This one: https://community.adobe.com/t5/acco...access-app-device-not-supported/td-p/11695914
@mario0318 do you happen to know a way to somehow "pretend" to the app that i am in fact using a different phone? Something that would allow me to make the app believe it is running on a different device?
Barrel Titor said:
@mario0318 do you happen to know a way to somehow "pretend" to the app that i am in fact using a different phone? Something that would allow me to make the app believe it is running on a different device?
Click to expand...
Click to collapse
Well, the well known magisk module MHPC or Magisk Hide Props Config comes to mind. You can change device fingerprints and maybe also give the Device Simulation feature a go, or custom edit any range of configurable props.
You could do so without the module editing the build.props yourself. Or if you stick with edxposed and deal with not having magisk manager's hide enabled, perhaps any of the device spoofers on the xposed repo could fool the app. Or Sudohide if you set Adobe app to hide from any and all apps that are root relevant. May also consider removing directories in your internal and removable storage for things like TWRP or PBRP, Titanium Backup, xposes, etc, you know, things that a simple media scan looking for any sign of root apps might pick up.
But for now, I'd give MHPC a try and change device fingerprint and maybe enable device simulation if simple fingerprint change doesn't work.
I'm having the same issue on a rooted OnePlus 8T
Same for me on op7 pro. Hiding with somiko but Adobe still not working. Nor could I bypass square, it notes root when it pairs Bluetooth