Related
AdFree is a fantastic program created by XDA user delta_foxtrot2 (see this thread in the G1 forum) to facilitate using your hosts file to block ad servers. This makes it extremely easy. Of course you will need root access!
Unfortunately I found some ads still weren't blocked and the last update to the AdFree hosts file happened 2010-02-27. So I decided to update the hosts file myself. I merged the hosts files from adfree/mvps/yoyo and added a bunch of mobile ad providers I've found myself. The list is free of duplicates and comments, so as to keep it as small as possible (it still amounts to about 635 kB).
To install this hosts file, you still need root access obviously:
download the zip
unpack it to the directory where adb.exe is located (if you don't know what adb is or how to get it running, please use the search)
open a command prompt
Code:
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
adb push hosts.for.mobile.txt /etc/hosts
adb shell mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
You might need to restart your phone. Also clearing the Android browser cache will apparently help in getting rid of already cached ads (worked for me, ymmv).
As for ethical discussions on blocking ads for free apps, blah. I don't so much have a problem with ads, as I do with the personal data that gets send to the ad providers. I'm talking about location data and whatever else they might want to know about my device and what I'm running ("analytics" is a fancy name for "we want to find out as much about you as we possibly can get away with").
Anyway.. use it, don't use it, up to you.
Last updated
15-4-2010 23:23 (20808 hosts blocked)
.
Thanks a bunch!
Thanks for the updated hosts. So should we even bother with the program, especially if it doesn't get updated hardly at all?
You're welcome!
If you push my hosts file, you don't need the AdFree app, but I wanted to acknowledge his work and give people a simpler alternative to using adb.
Best choice right now is my hosts file as it's simply more comprehensive.
Sent from my HTC Hero using the XDA mobile application powered by Tapatalk
phaelox said:
You're welcome!
If you push my hosts file, you don't need the AdFree app, but I wanted to acknowledge his work and give people a simpler alternative to using adb.
Best choice right now is my hosts file as it's simply more comprehensive.
Sent from my HTC Hero using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Understood. Yeah, it was a great start/beginning to blocking ads, but no updates. Thanks again.
Thanks! I've been looking for something like this for awhile. Real quick question: is getting "Data connectivity errors" in browser normal with this? It didn't start till I pushed this on my phone.
tmayne said:
Real quick question: is getting "Data connectivity errors" in browser normal with this? It didn't start till I pushed this on my phone.
Click to expand...
Click to collapse
Short answer: Yes.
Long answer:
You may know this, but I'll explain anyway. The way this works is as follows. The loopback address for any network interface is 127.0.0.1 -- this is the address for the device, but only from the device itself, it loops back on itself. We don't want to waste bandwidth with ads, or have ad providers collect all sorts of data on us, so we don't want to connect to them. Any FQDN -Fully Qualified Domain Name- (for example: analytics.admob.com) needs to be converted into an IP address to be able to connect to it. Here's where the 'hosts' file comes in. It's a simple text file with a record on each line that says redirect 'hostname' to 'ip-address'. So we put a line in that reads '127.0.0.1 analytics.admob.com'. This tells our device that any connection made to 'analytics.admob.com' needs to be redirected to '127.0.0.1', which is your device. Basically a dead-end, as you are not running their webserver serving ads on your device, so this results in a data connection error.
Now, usually you will surf to a site that loads images (advertisements) from a server that is listed in this hosts file, and as a result the ads will not load. That shouldn't popup any error windows. But if you try to visit http://analytics.admob.com in your browser, then yes, you will see an error.
If the latter happens with a site you do wish to visit, just open the hosts file in a text editor (one that supports UNIX-style line ends) and remove the line in question, or put a '#' in front of the line to comment it out.
Hope that made it clearer.
Yeah it did. No worries though since it seems that after pressing "Ok" everything works fine! Small trade off for blocked ads! Thanks!
Thanks for this How-TO!
So basicaly that mean we can restrict acces to certain websites from our phone?
eg: adding this line
Code:
127.0.0.1 forum.xda-developers.com
and I'll no longer be able to browse XDA from my phone?
Keep writing such How-To, like this one and the one to sign update.zip, I found this interessant and usefull
tmayne said:
Yeah it did. No worries though since it seems that after pressing "Ok" everything works fine! Small trade off for blocked ads! Thanks!
Click to expand...
Click to collapse
You're welcome, glad I could help.
carbonyle said:
Thanks for this How-TO!
So basicaly that mean we can restrict acces to certain websites from our phone?
eg: adding this line
Code:
127.0.0.1 forum.xda-developers.com
and I'll no longer be able to browse XDA from my phone?
Keep writing such How-To, like this one and the one to sign update.zip, I found this interessant and usefull
Click to expand...
Click to collapse
Cheers. And yes, that's exactly right. Just remember the hosts file takes FQDN's, so you can block a domain (or subdomain) this way, but not a directory or page on a domain. Also, blocking a domain does not also block its subdomains.
PS. this method of using the hosts file is not unique to your android phone, it works on most operating systems on PC as well. See this Wikipedia entry for more info.
what about non rooted phones? I just got myself a htc desire, I'm happy with it but would be happier if I wouldn't be required to see all those ads.
Unfortunately root is required to remount /system as writable to be able to overwrite the hosts file.
Without root you could use another free app found in Market called "AdBlock", which functions as a localhost proxy. Just set localhost as proxy in APN/wifi settings. It doesn't come with a prefilled list of keywords to block though, but it works on a URL level, not FQDN, so you can specify a url or part of it to block.
Just one more quick concern about the Data Connectivity issues: Certain areas of my university require a redirect page login in order to connect to wifi. However, it seems that at certain locations, I get the Data Connectivity error pop up repeatedly and my phone never makes it to the redirect page.
Actually it seems my phone only likes the wifi in my dorm. As stepping outside (to a library or classroom) and attempting to connect to the same wifi produces the error.
Is this an issue with the hosts file or with the phone itself??
Thanks!
If you DO see the wifi redirect page at SOME locations, then the hosts file is not blocking it (wouldn't make sense as it's likely an intranet page anyway). Sounds like wifi reception is unstable on your phone.
This is getting off-topic, but..... Have you already updated your radio? (the part of the ROM that handles everything related to GSM/3G/WiFi/Bluetooth connections). If not, here for the latest radio update.zip - flash through recovery.
phaelox said:
If you DO see the wifi redirect page at SOME locations, then the hosts file is not blocking it (wouldn't make sense as it's likely an intranet page anyway). Sounds like wifi reception is unstable on your phone.
This is getting off-topic, but..... Have you already updated your radio? (the part of the ROM that handles everything related to GSM/3G/WiFi/Bluetooth connections). If not, or the latest radio update.zip - flash through recovery.
Click to expand...
Click to collapse
I should note that I'm using a Motorola Cliq...Handler 1.5 ROM. There is a radio update available for the Motorola Cliq (I'm currently using 1.3.18 and 1.4.8 has been released) but there are some apk incompatibilities with it (particularly Swype which I love...since it's in closed beta right now, there are no accessible updates for it unfortunately).
Since I bought my phone off of ebay, I can't send it back for a new one. The essential things work but it is a bit frustrating that it has some problems.
tmayne said:
I should note that I'm using a Motorola Cliq...Handler 1.5 ROM. There is a radio update available for the Motorola Cliq (I'm currently using 1.3.18 and 1.4.8 has been released) but there are some apk incompatibilities with it (particularly Swype which I love...since it's in closed beta right now, there are no accessible updates for it unfortunately).
Since I bought my phone off of ebay, I can't send it back for a new one. The essential things work but it is a bit frustrating that it has some problems.
Click to expand...
Click to collapse
I'm pretty sure that updating radio won't affect other softwares since "radio" is *just* the piece of code that can handle GSM/Wifi/BT/3G, ... signals
I'll always keep an open mind, but from what I know, I'm with carbonyle on this.
Back on topic:
if you come across an app that still displays ad, regardless of my hosts file, please reply in this topic with the app/version (and a logcat output would be nice if you know how) and I'll see if I can find the ad provider domain and update the hosts file.
I'm confused... This is for blocking apps adds???
:No-Frost: said:
I'm confused... This is for blocking apps adds???
Click to expand...
Click to collapse
Yes it is. See it like a firewall wich blocks mobile ads. Because the app wont recieve any response from the ad url it tries to reach, it'll simply not display the ad (like when you use the app without wifi or data connextion on)
Wooooooo thanks... worked like a charm in glympse shazam and others =D...
PS: Air Control still have adds... Mmm how can we know what's the host for the add in the apps so we can contribute into blocking them???
If you compare the various, Galaxy Tabs currently available (Verizon, AT&T, Sprint & TMobile) it becomes obvious that there are fairly significant differences between the way they are configured. There are differences in memory, accessibility to Bluetooth keyboards and mice, DivX compatibility, etc. Has there been any info available as to how the WiFi-only Tab is going to be configured, when available? I'm waiting for one of these but I'm concerned that it will end up configured in some manner that I won't like and I would have been better to have gotten one of the currently-available models (probably the TMobile version) and not waited so long....I want one bad....
Ken
Ken, I just picked up a Sprint one and though we didn't choose data plans, wifi only, we kept getting this extremely annoying activate now message from sprint. It was easy enough to stop:
1) Download and install an app manager form the market, Astro or App Monster for instance
2) Locate and Download Z4Root
3) Install using the app manager you, then run the app and root the phone
4) Once rooted, reboot if not done already, go to the app market and download terminal emulator
Run the following commands in terminal emulator (no quotes):
“su”
“mount -o remount,rw -t rfs /dev/stl5 /system”
“rm -r /system/app/ sprintadroidextension.apk”
“mount -o remount,ro -t rfs /dev/stl5 /system”
“exit”
Close and reboot. Let me know, I tried to make it simpler for you so you don’t have to download and install all the sdk stuff.
Been looking for this fix... many thanks!
I am looking for one for wifi only. I am fairly familiar with rooting (phones anyway).
Is the Sprint version to best one to shoot for? They appear to run ~ $500 on Ebay but I have hesitated because I was worried about not being able to use it. The fix above looks very simple. Any other worries? Running outta days before Ho-Ho time and I need to get this done.
Thanks.
Got to third command line and my tab bricked. Anyone else have this happen?
YEA ME TO. ANYONE PLEASE HELP. My Galaxy Tab just keeps rebooting, it was RIGHT at the 3rd command line to.
Ouch! Not surprised because you've just removed /system/app in its entirety.
You're going to need to reflash at least the PDA part of your ROM.
This thread needs to be edited/deleted now before it screws up any more devices.
Regards,
Dave
I was just about to do this since I too have the Sprint version of the Tab.....everybody's tab ok? Any fix?
The fix is don't run a "rm -r" command unless you know *exactly* what it is going to do!
If you really want to remove this APK, and you don't know your *nix command line utilities from your elbow I suggest that you:
1. Root using z4root.
2. Buy Root Explorer from the Market
3. In Root Explorer browse to /system/app - press the "Mount r/w" button at the top of the screen.
4. Locate the file sprintadroidextension.apk and delete it (that file, and only that file!)
5. Press the "Mount r/o" button at the top of the screen.
That will remove the single APK referred to by "sirmacbeth" - I've no idea if this is actually stop any Sprint activation messages though, as I really must question "sirmacbeth"'s motives here because what he wrote as a guide ranks amongst the worst things I've seen on XDA.
Regards,
Dave
Guitar4Him said:
If you compare the various, Galaxy Tabs currently available (Verizon, AT&T, Sprint & TMobile) it becomes obvious that there are fairly significant differences between the way they are configured. There are differences in memory, accessibility to Bluetooth keyboards and mice, DivX compatibility, etc. Has there been any info available as to how the WiFi-only Tab is going to be configured, when available? I'm waiting for one of these but I'm concerned that it will end up configured in some manner that I won't like and I would have been better to have gotten one of the currently-available models (probably the TMobile version) and not waited so long....I want one bad....
Ken
Click to expand...
Click to collapse
You may have posted this on android forums as well. I have the same concern. I would ideally like the WiFi version to keep the same screen (rumored to not use samoled but lcd) as well as 16gb (or more) internal storage as well as the sd slot. And divx certified as well.
Also IF anything offering a world galaxy tab with all the above and gsm and cdma ability.
latinmaxima said:
I would ideally like the WiFi version to keep the same screen (rumored to not use samoled but lcd).
Click to expand...
Click to collapse
???
The Tab doesn't have an AMOLED screen - it's an LCD.
Regards,
Dave
foxmeister said:
The fix is don't run a "rm -r" command unless you know *exactly* what it is going to do!
If you really want to remove this APK, and you don't know your *nix command line utilities from your elbow I suggest that you:
1. Root using z4root.
2. Buy Root Explorer from the Market
3. In Root Explorer browse to /system/app - press the "Mount r/w" button at the top of the screen.
4. Locate the file sprintadroidextension.apk and delete it (that file, and only that file!)
5. Press the "Mount r/o" button at the top of the screen.
That will remove the single APK referred to by "sirmacbeth" - I've no idea if this is actually stop any Sprint activation messages though, as I really must question "sirmacbeth"'s motives here because what he wrote as a guide ranks amongst the worst things I've seen on XDA.
Regards,
Dave
Click to expand...
Click to collapse
As far as motives goes I can't say anything about "sirmacbeth" but there is a intentional or unintentional "space" char left in his third step:
“rm -r /system/app/ sprintadroidextension.apk” and the correct command would be
“rm -r /system/app/sprintadroidextension.apk”
if there was no space there, people would have been deleting the app only but with that mistake they ended up deleting to whole app dir..
but, i agree, and the safest way to do this is to delete the file through an explorer app like advised..
noyan said:
“rm -r /system/app/sprintadroidextension.apk”
Click to expand...
Click to collapse
Actually, there's no need for the -r - there would have been no problem if this hadn't been there, and it's completely superfluous for deleting a single file!
Regards,
Dave
This method works, but deletion is rather permanent, why not "freeze" the app using Titanium Backup, or, (if you love the terminal), just rename the apk or move it to your sd card as a backup file. This way you can restore it if you need or want to later.
I also heard that putting it in Airplane mode will stop it and the wifi will still work.
ok, well since i was in the endless boot loop i used ZoinksS2k's ALMOST Stock ODIN ROM.
- Well that causes the GPS to stop working, and uses another phones modem driver.
*I called Samsung, i didn't tell them i was rooted, i just said i recieved this product when i booted it, everythign kept saying FC'd and then when i rebooted it, it went into an endless loop.
*They said I can send it in for a REFLASH.
What do you guys think? Should I do that? its free under warranty, OBVIOUSLY i'd UNROOT it before shipping it in.
Turn around time is about 5-7 days + shipping.
Ikyo said:
I also heard that putting it in Airplane mode will stop it and the wifi will still work.
Click to expand...
Click to collapse
Airplane mode turns off all radios, including wifi. Beyond that, the activation process is governed by an application, not by the presence of networks. Unfortunately airplane mode won't fix it.
rkmj said:
Airplane mode turns off all radios, including wifi. Beyond that, the activation process is governed by an application, not by the presence of networks. Unfortunately airplane mode won't fix it.
Click to expand...
Click to collapse
You can switch WiFi back on even when in Airplane mode. The standard power control widget won't let you do it, but you can do it from the settings menu and there are plenty of WiFi toggle widgets that will allow it too.
Regards,
Dave
foxmeister said:
You can switch WiFi back on even when in Airplane mode. The standard power control widget won't let you do it, but you can do it from the settings menu and there are plenty of WiFi toggle widgets that will allow it too.
Regards,
Dave
Click to expand...
Click to collapse
I had forgotten that, thanks for the reminder. Nevertheless, it won't fix the activation issue. Wifi on or off, unless you do something about the applications that check for and trigger an activation prompt, it's going to bug you for activation.
Hi folks,
I have a Verizon tab and i follow these steps to device stop asking for activation.
When the activation message shows up, i pressed the volume buttom at this order.
1 time vol. Up
2 times vol. Down
3 times vol. Up
4 times vol. Down
Cheers
hello, i am new to the rooting scene and droid. i have the AT&T S4 and i would like to remove all this crap that AT&T loads on the phone. i would also like to know that if i root my S4 can i use my sdcard to install apps to since the default "8gb" might not be enough so i bought a 32gb sdcard. please advise, i don't even know if this is the purpose of rooting a phone or not, sorry it its a dumb question.
Thanks
Well you're not new to xda. This belongs in Q&A, not development.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
how do i move this to the correct area. i am not new to the forum new to droid. i many years ago i had a htc 6800 for verizon i used to "cook" roms for.
plwalsh88 said:
Well you're not new to xda. This belongs in Q&A, not development.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
LilSnoop40 said:
how do i move this to the correct area. i am not new to the forum new to droid. i many years ago i had a htc 6800 for verizon i used to "cook" roms for.
Click to expand...
Click to collapse
You can click on the triangle in the upper right corner of the post, and report to a moderator for moving/maintenance. I already reported it for you.
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Development is only for developers to post work
LilSnoop40 said:
hello, i am new to the rooting scene and droid. i have the AT&T S4 and i would like to remove all this crap that AT&T loads on the phone. i would also like to know that if i root my S4 can i use my sdcard to install apps to since the default "8gb" might not be enough so i bought a 32gb sdcard. please advise, i don't even know if this is the purpose of rooting a phone or not, sorry it its a dumb question.
Thanks
Click to expand...
Click to collapse
It seems nobody has answered this, only moved your thread around. ^_^
In short, rooting just allows you to do things to your phone that normally would be against the manufacturer's/carrier's intent. One such example would be to remove carrier-added bloatware that is otherwise not removable. I personally use root for the following:
Titanium Backup Pro: This would let me backup my apps AND data for each app. Google does a decent job at backing up most my apps, but if I "sideload" an app (install from a different source other than the Play Store), I can back it up also. Plus Google doesn't always backup the DATA part of an app, which can be important for me (e.g. an authenticator, or RSA token for work). In addition, TiBu also allows you to easily "freeze" the bloatware, which prohibits it from running or showing up anywhere. This is usually a better option than completely uninstalling it, because it's usually much easier to recover from de-bloating the wrong bloat.
AdFree: An advertisement blocker. Typically Root is required to do this properly, as it modifies the "hosts" file on your android. In the end, it overrides your phone's DNS such that when an app or webpage requests data from a known advertising website, the phone will redirect the request to "nothing", and the ad will not show. Use with discretion - some people frown upon this because they "lose" revenue from the ads that are not shown. I won't comment further, fearing I'll start a verbal war here.
Greenify: Allows you to put certain apps to sleep while they are not being actively used. I use it for Facebook Messenger, because I've found that if this app is allowed to run in the background, it kills my battery. I leave Facebook running in the background, so that I'll still get notifications of new FB messages. Seems to work out for me well.
"Some Tethering Applications or Methods": Some of the better ways to tether/hotspot from your phone will require root. Again, I'll leave this one lie. Personally, I rarely use it, but I've been in a bind before without internet access, and I've needed to use it. I don't want to lose my unlimited data with AT&T, so I really have no choice to add a tethering plan anymore. Regardless, it's nice to know I have it available as an emergency option.
While I could recommend the root, I also have to warn you that this will effectively void your Warranty. There's ways (read through the forums here) to "hide" the root, by using SuperSU instead. But just be forewarned.
EDIT: Here's the link to the thread with the video - How to Root & Remove Unlock Icon & Unroot
First thing's first; learn correct terminology. The Galaxy S4 is certainly not a Droid phone. "Droid" is a term used by Verizon to attempt to label and unify their line of Android phones. "Android" is the name of Google's open-source mobile OS.
LilSnoop40, I got your private message, but I'm going to post some stuff here on this thread for everyone to see, just in case there are others that need some help with the rooting as well. Here goes:
The actual part of rooting your device is not too difficult using "Motochopper". The hardest part is just getting ADB setup and your phone recognized in ADB. For the Motochopper root and a basic outline of how to do the root, see this thread:
http://forum.xda-developers.com/showthread.php?t=2252248
Some recommendations:
- Be sure the phone is in USB Debugging mode. You'll have to enable the Developer options first. Let me know if you need help with this part. IT involves repeatedly clicking something in Settings to enable Dev options, and then there's just a checkbox to check after that to enable the debugging mode. This is "Step 3" in that thread I linked.
- Be sure you have the latest samsung drivers for your phone. There's a few threads around here that have JUST the drivers, and not the whole Samsung Kies software package (completely unnecessary!). If you can't find them, I'll see if I can search around and provide a link. This is "Step 2" of the thread.
- If you're in Debugging Mode, the drivers should also being installed for the "ADB device" - I forget the actual name of it, but it's a device on your computer that says something about ADB. This will only appear when you have the phone in debugging mode of course.
- super-important: When you run the root/hack/motochopper thing, you'll be prompted on your device to allow the ADB connection. It will say something about accepting a certificate or something like that. If you don't respond in 10 seconds, it will deny it, and the root will fail. This is "step 6" on the thread I linked.
Also, if you manage to do all this successfully, you'll see that the root was successful, and you'll have a new app on your phone: Superuser. This new app is what allows you to approve root access by other applications (more-or-less). A side-effect of having this app installed will be that the system will detect the presence of root, and when you boot your phone, it will show an open padlock and "custom". If you follow my basic instructions in this post, you can get rid of that.
Feel free to ask for any clarifications, etc. I'll try to be as helpful as possible.
First android phone I've owned since coming from years of iPhones, does the recent update that I downloaded affect the ability to root the device? I keep seeing people talking about versions but I don't see the numbers that they are saying so not sure what to look at, or if it matters at all? Will this work on any quadcore S4?
Skattered said:
First android phone I've owned since coming from years of iPhones, does the recent update that I downloaded affect the ability to root the device? I keep seeing people talking about versions but I don't see the numbers that they are saying so not sure what to look at, or if it matters at all? Will this work on any quadcore S4?
Click to expand...
Click to collapse
Short answer: No, the update won't affect your ability to root.
What carrier do you have? For the basic model number, you can read the label that's under your battery. The AT&T version, for example, will read: "SGH-I337". You can also get very specific information about your phone, the model number, build number, etc. bu doing the following: Go to Settings -> More... (The "Build number" is probably the numbers your looking for.)
If I'm not mistaken, the Motochopper root works on all I337 models?
Okay sweet, it is a 1337 (guess the signature tells me that too) and its on at&t
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Many of us don't have root and many of us also uninstalled may system apps, including Fire Launcher. That left us with some annoyances. One major annoyance was being kicked to the lock screen whenever we swiped away apps from the recent apps menu. Some people saw annoying flashes. Well this isn't quite a fix, but it pretty much takes care of the problem. You can now remove your lock screen completely and replace it at will and you do NOT need root access.
***WARNING: Touching any other settings on your tablet during this guide can cause a brick!!!***
1. Download and install Settings Database Editor.
2. Plug your tablet into your PC and open an ADB window. Enter the following:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Step number 2 MUST be done in order for this to work.
3. Open Settings Database Editor and tap on the 'secure' tab at the top.
4. These settings are in alphabetical order. Scroll until you see:
Code:
"lockscreen_disabled" "0"
5. Change the 0 to a 1. DO NOT CHANGE ANYTHING ELSE
6. Close Settings Database Editor
Now turn off your screen. Now turn it back on. You are welcome! I have a few more tricks coming. Watch for some later!
IF THE ABOVE DOESN'T WORK, TO DISABLE LOCK SCREEN:
Code:
adb shell settings put secure lockscreen_disabled 1
ENABLE LOCK SCREEN:
Code:
adb shell settings put secure lockscreen_disabled 0
Both methods don´t work on my Fire HD10 2017.
tommes-d said:
Both methods don´t work on my Fire HD10 2017.
Click to expand...
Click to collapse
It worked almost instantly for me. Maybe wait a bit? Did you reboot? It won't work on every device. Doesn't work on my Galaxy S7.
Not working for me too (Fire HD 8 2016). Also, you've made a mistake: original setting name is "lockscreen.disabled" (dot, not an underscore).
sensboston said:
Not working for me too (Fire HD 8 2016). Also, you've made a mistake: original setting name is "lockscreen.disabled" (dot, not an underscore).
Click to expand...
Click to collapse
Disappointing. Today I got a good one though. I can't wait to get home and post a thread.
I know this isn't the correct forum for this but I tried this on a Fire 7 (2017) and it also does not seem to work.
is there an updated way to do this?
is there an updated way to do this?
edit: kindle fire 8 7th gen, confirmed not working.
Doesn't work on my Fire HD8. But while browsing through Settings Database Editor I have found something useful.
In the "Global Table" tab there's a setting called LOCKSCREEN_AD_ENABLED. Change the value from 1 to 0, save. Turn off screen, turn it on again --> ads are gone!
At least for a while...
Seems to be working on KFAUWI (Fire 7 7th Gen) on 5.4.0.0.
EDIT: Maybe it doesn't work with 5.4.0.1 and later?
It would be useful for those reporting success/failure to include not just device model, but fw version as well.
EDIT1: After some time playing around the system I have found out that by default it actually does not work, but if Global Table->"device_provisioned" = 0 then lock screen gets disabled, but serial number gets greyed out and developer options get disabled, while adb remains functional.
On 5.6.0.0 even change to "device_provisioned" did not disable the lock screen.
gabosius said:
Seems to be working on KFAUWI (Fire 7 7th Gen) on 5.4.0.0.
EDIT: Maybe it doesn't work with 5.4.0.1 and later?
It would be useful for those reporting success/failure to include not just device model, but fw version as well.
Click to expand...
Click to collapse
There are settings in the "private" class that override some of these lower ones, usually in favor their using their own software. I think most device stock settings are hidden for the purpose of favoring their own software. Though with Amazon, I scratch my head. Why spend the large amount of money, to install a high tech, customizable GPS system on devices, only to spend more money carelessly blocking your Access?
Sent from my Samsung Galaxy S4 using XDA Labs
DragonFire1024 said:
There are settings in the "private" class that override some of these lower ones, usually in favor their using their own software. I think most device stock settings are hidden for the purpose of favoring their own software. Though with Amazon, I scratch my head. Why spend the large amount of money, to install a high tech, customizable GPS system on devices, only to spend more money carelessly blocking your Access?
Sent from my Samsung Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
That's fairly simple, the same goes for one of the iPhones (don't recall which gen exactly) which had two different models of radio chips, one of which did support LTE, but Apple decided to disable LTE support for that gen of the phone altogether.
Now more on the topic, checked the specs of all 7th gen tablets, indeed none of them seem to support GPS officially (for some reason I thought that HD8/HD10 might have it), but if they have the hw, it could be for testing purposes to test proprietary GPS related sw on development devices before introducing it in the next gen? Or simply they decided to drop it somewhere along the way but left the hardware (as we still have Serial/UART on some production devices nowadays, which are used only for debugging in the development stage).
On the other hand, where did you get the info that it actually has GPS related hardware? Because while exploring my device settings I only found a hint on A-GPS support (which is not proven).
gabosius said:
That's fairly simple, the same goes for one of the iPhones (don't recall which gen exactly) which had two different models of radio chips, one of which did support LTE, but Apple decided to disable LTE support for that gen of the phone altogether.
Now more on the topic, checked the specs of all 7th gen tablets, indeed none of them seem to support GPS officially (for some reason I thought that HD8/HD10 might have it), but if they have the hw, it could be for testing purposes to test proprietary GPS related sw on development devices before introducing it in the next gen? Or simply they decided to drop it somewhere along the way but left the hardware (as we still have Serial/UART on some production devices nowadays, which are used only for debugging in the development stage).
On the other hand, where did you get the info that it actually has GPS related hardware? Because while exploring my device settings I only found a hint on A-GPS support (which is not proven).
Click to expand...
Click to collapse
Add a few .xml configuration files to start and there is configuration settings in the framework. Look for an app on the tablet with HERE in all caps in the title. That's the APK module making it possible. And yes I figured out a way to modify framework settings
DragonFire1024 said:
Add a few .xml configuration files to start and there is configuration settings in the framework. Look for an app on the tablet with HERE in all caps in the title. That's the APK module making it possible. And yes I figured out a way to modify framework settings
Click to expand...
Click to collapse
I see, just checked MT8127 specs, and indeed there seems to be integrated support for GPS with GLONASS, that may be something interesting to play with.
EDIT: HD8/HD10 even have broader support of GPS related technologies according to their SoC specs.
Yeah, I was following root progress thread, even tried Blueborne exploit (the one published by Armis labs on github) on KFAUWI without much success as there is no access to /proc/<pid>/maps. And framework-res.apk mod looks promising only for devices having root, as getting required permissions outside /system is rather problematic.
Yet I was surprised that WRITE_SECURE_SETTINGS can be assigned outside /system. As I was poking around com.amazon.dcp.permission.DISPLAY_DEBUG_UI for quite some time.
gabosius said:
Yet I was surprised that WRITE_SECURE_SETTINGS can be assigned outside /system. As I was poking around com.amazon.dcp.permission.DISPLAY_DEBUG_UI for quite some time.
Click to expand...
Click to collapse
Do you have any idea if you can grant something like Activity Launcher the DISPLAY_DEBUG_UI permission? Some of the activities gave me errors when I tried to open them, saying they require com.amazon.dcp.permission.DISPLAY_DEBUG_UI.
The thing is, this appears to be a custom permission added by Amazon, not available in the official Android documentation.
Would Activity Launcher even be capable of launching certain "hidden" activities with this permission granted? Presumably you would grant permission over ADB the same way as WRITE_SECURE_SETTINGS?
Any ideas would be great.
lakitu47 said:
Do you have any idea if you can grant something like Activity Launcher the DISPLAY_DEBUG_UI permission? Some of the activities gave me errors when I tried to open them, saying they require com.amazon.dcp.permission.DISPLAY_DEBUG_UI.
The thing is, this appears to be a custom permission added by Amazon, not available in the official Android documentation.
Would Activity Launcher even be capable of launching certain "hidden" activities with this permission granted? Presumably you would grant permission over ADB the same way as WRITE_SECURE_SETTINGS?
Any ideas would be great.
Click to expand...
Click to collapse
Tried granting it to other apps and it resulted in "com.amazon.dcp.permission.DISPLAY_DEBUG_UI is not a changeable type" the command I used was pm grant com.amazon.dcp com.amazon.dcp.permission.DISPLAY_DEBUG_UI so yes, the syntax is the same with custom amazon permissions. Also execution of dumpsys package com.amazon.dcp shows that app already has DISPLAY_DEBUG_UI permission.
My guess is that it requires root, as even when I am launching activity from adb shell (not in context of activity manager) I get the same error that it requires the permission, and the same goes for some other hidden amazon applications.
EDIT: you can get list of device permissions by executing "pm list permissions" without quotes from adb shell, there are at least a few interesting ones.
lakitu47 said:
Do you have any idea if you can grant something like Activity Launcher the DISPLAY_DEBUG_UI permission? Some of the activities gave me errors when I tried to open them, saying they require com.amazon.dcp.permission.DISPLAY_DEBUG_UI.
The thing is, this appears to be a custom permission added by Amazon, not available in the official Android documentation.
Would Activity Launcher even be capable of launching certain "hidden" activities with this permission granted? Presumably you would grant permission over ADB the same way as WRITE_SECURE_SETTINGS?
Any ideas would be great.
Click to expand...
Click to collapse
That's a great question and one that hasn't been asked before. I can tell you I've been able to, in some apps, modify the manifest permissions. For example, I can use an app to edit the manifest of Jack Pals terminal emulator to add the secure settings permission and have it successfully install etc. I never thought of doing the same with activity launcher and if successful, seeing what happens. This could be very interesting. If you give me a few copies of some of the manifests permissions, I can see if a recompile and install will hold.
DragonFire1024 said:
That's a great question and one that hasn't been asked before. I can tell you I've been able to, in some apps, modify the manifest permissions. For example, I can use an app to edit the manifest of Jack Pals terminal emulator to add the secure settings permission and have it successfully install etc. I never thought of doing the same with activity launcher and if successful, seeing what happens. This could be very interesting. If you give me a few copies of some of the manifests permissions, I can see if a recompile and install will hold.
Click to expand...
Click to collapse
I attached a text document with ALL of the permissions listed by "pm list permissions" since it was too long to put here.
lakitu47 said:
I attached a text document with ALL of the permissions listed by "pm list permissions" since it was too long to put here.
Click to expand...
Click to collapse
Give me a few hours to see if I can modify the app. If I can, I'll upload a. APK
Sent from my Samsung Galaxy S4 using XDA Labs
DragonFire1024 said:
Give me a few hours to see if I can modify the app. If I can, I'll upload a. APK
Sent from my Samsung Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
Questionable whether anything would change, as I don't see where activity launcher would need write secure settings permission.
On the other hand I did some digging on the "not a changeable permission type" message, and this provides some answer on what it might be expecting in order to activate?/assign the permission.
gabosius said:
Questionable whether anything would change, as I don't see where activity launcher would need write secure settings permission.
On the other hand I did some digging on the "not a changeable permission type" message, and this provides some answer on what it might be expecting in order to activate?/assign the permission.
Click to expand...
Click to collapse
Interesting. So each permission has a certain "protection" level?
I am thinking of rooting my Oneplus 8 Pro but I would like to know if there is currently a ROM that allows me to:
have automatic call recording (maybe even with google dialer or third-party programs)
have the possibility to exploit the "infrared camera" at 100%
have the latest version of android (11) and related security patches
it's possible?
Thanks.
You can enable Call Recording with ADB you don't need root for that.
Code:
Use this code at your ADB shell:
adb shell settings put global op_voice_recording_supported_by_mcc 1
Using infrared camera is also avaliable with ADB
Code:
I think this is the only solution so far. With root you can just use this FactoryTool without pasting command. There is no a quick solution to use it in normal camera app.
adb shell am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
I already using OnePlus's latest OpenBeta's, they have mostly latest security patches. They are coming like 25th day of that month, you are using security patch a bit old but anyway I think it's fine, thats depends on you what you'll do with phone and considering are you really need that security patch that hard. Most of phones are getting them nearly per quarters of year.
And after unlocking bootloader is damn hard to hide from apps in Android 11. I was rooted like a month ago and I just give up. Thats not worth the effort you give. I used with root like a week than I realized I can do most of stuff I'm doing at phone without root/unlocked bootloader but I cannot do banking with root/unlocked bootloader. I think is the best part of rooting is you can backup your persist and modem partition if something goes wrong with your firmware in future you don't needed to deal with OnePlus's ****ty RMA process, they are this close to screw all persist partition.
If you have further questions I'll gladly answer them And If you want to root be sure to NOT use pre-modded boot images, they can broke all you fingerprint, camera, axonometry, gps sensors. Have a great day...
emirefek said:
You can enable Call Recording with ADB you don't need root for that.
Code:
Use this code at your ADB shell:
adb shell settings put global op_voice_recording_supported_by_mcc 1
Using infrared camera is also avaliable with ADB
Code:
I think this is the only solution so far. With root you can just use this FactoryTool without pasting command. There is no a quick solution to use it in normal camera app.
adb shell am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
I already using OnePlus's latest OpenBeta's, they have mostly latest security patches. They are coming like 25th day of that month, you are using security patch a bit old but anyway I think it's fine, thats depends on you what you'll do with phone and considering are you really need that security patch that hard. Most of phones are getting them nearly per quarters of year.
And after unlocking bootloader is damn hard to hide from apps in Android 11. I was rooted like a month ago and I just give up. Thats not worth the effort you give. I used with root like a week than I realized I can do most of stuff I'm doing at phone without root/unlocked bootloader but I cannot do banking with root/unlocked bootloader. I think is the best part of rooting is you can backup your persist and modem partition if something goes wrong with your firmware in future you don't needed to deal with OnePlus's ****ty RMA process, they are this close to screw all persist partition.
If you have further questions I'll gladly answer them And If you want to root be sure to NOT use pre-modded boot images, they can broke all you fingerprint, camera, axonometry, gps sensors. Have a great day...
Click to expand...
Click to collapse
Thank you very much for the reply.
I have the latest version of android 11 released not even a month ago (updated to the latest security patches).
With this version do you think I can unlock registration via ADB with the command you gave me?
As for the infrared camera, using that ADB command would I be able to use it through the official oneplus "camera" app?
I also wouldn't want to root for any problems with banking apps and the like, so if I could fix that it would be better.
Thank you again.
emirefek said:
You can enable Call Recording with ADB you don't need root for that.
Code:
Use this code at your ADB shell:
adb shell settings put global op_voice_recording_supported_by_mcc 1
Using infrared camera is also avaliable with ADB
Code:
I think this is the only solution so far. With root you can just use this FactoryTool without pasting command. There is no a quick solution to use it in normal camera app.
adb shell am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
I already using OnePlus's latest OpenBeta's, they have mostly latest security patches. They are coming like 25th day of that month, you are using security patch a bit old but anyway I think it's fine, thats depends on you what you'll do with phone and considering are you really need that security patch that hard. Most of phones are getting them nearly per quarters of year.
And after unlocking bootloader is damn hard to hide from apps in Android 11. I was rooted like a month ago and I just give up. Thats not worth the effort you give. I used with root like a week than I realized I can do most of stuff I'm doing at phone without root/unlocked bootloader but I cannot do banking with root/unlocked bootloader. I think is the best part of rooting is you can backup your persist and modem partition if something goes wrong with your firmware in future you don't needed to deal with OnePlus's ****ty RMA process, they are this close to screw all persist partition.
If you have further questions I'll gladly answer them And If you want to root be sure to NOT use pre-modded boot images, they can broke all you fingerprint, camera, axonometry, gps sensors. Have a great day...
Click to expand...
Click to collapse
I tried with the two ADB controls for recording and the camera.
The first one enables me the recording menu in the options, but in fact, despite having enabled the automatic recording, it does not record anything, the option appears on the dialer screen.
I think it is blocked for my country (Italy), is there any way to unblock it?
I was able to record the call. Stupidly I hadn't set the oneplus dialer as the default one. Now I wonder if there is a way to record calls with google too?
As for the room, on the other hand, even when photochromic is selected, it simply tells me that I have to be outdoors and in more illuminated environments.
I managed to enable the camera too: D
My only doubt now is if it is possible to make call recording work with the google dialer or, with the google dialer + external programs (like CubeACR).
ChIP_83 said:
I tried with the two ADB controls for recording and the camera.
The first one enables me the recording menu in the options, but in fact, despite having enabled the automatic recording, it does not record anything, the option appears on the dialer screen.
I think it is blocked for my country (Italy), is there any way to unblock it?
I was able to record the call. Stupidly I hadn't set the oneplus dialer as the default one. Now I wonder if there is a way to record calls with google too?
As for the room, on the other hand, even when photochromic is selected, it simply tells me that I have to be outdoors and in more illuminated environments.
I managed to enable the camera too: D
My only doubt now is if it is possible to make call recording work with the google dialer or, with the google dialer + external programs (like CubeACR).
Click to expand...
Click to collapse
You need to do your research yourself about Recording in Google's dialer. I'm not using it actively. I hope you'll find a way. And quick tip. After opening IR camera with ADB try to lock camera app from recently apps menu. With that you can use after a while without re-running command. And don't forget to share HowYouDid after figuring out recording at Google's Dialer. Have a great day!
You can enable Call Recording with ADB you don't need root for that.
Click to expand...
Click to collapse
You can't use call recorder on Android 11 in certain countries - Poland for example. I will try to go back to Android 10 ( Oxygen ).
Only way to get infrared is to roll back to 10.5.9 I think it is, I'm in the UK so that was the last one to work for me.
In regards to the camera on 11 it's quite simple but not the same..
Just obtain factory mode via the above method or several others, then you have two options.
Either use *#808# then go to the camera test page and use the 4th camera, then take screen recordings or screen shots (that's what I use) as it's the quickest way Vs the command to open it each time
Or
Download the app from the play store for the photchrom camera and use that which gives an interface for the same thing but has more options, simply cycle the camera using the flip button (bottom right)
OnePlus 8 Pro Photochrom[ROOT] - Apps on Google Play
OnePlus 8 Pro Photochrom Camera for ROOTED devices & OxygenOS 10.5.11 or 11
play.google.com
Call recording I have this by default.
If you're in a region like Australia then it may be blocked, AFAIK most places allow it.
emirefek said:
You can enable Call Recording with ADB you don't need root for that.
Code:
Use this code at your ADB shell:
adb shell settings put global op_voice_recording_supported_by_mcc 1
Using infrared camera is also avaliable with ADB
Code:
I think this is the only solution so far. With root you can just use this FactoryTool without pasting command. There is no a quick solution to use it in normal camera app.
adb shell am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
I already using OnePlus's latest OpenBeta's, they have mostly latest security patches. They are coming like 25th day of that month, you are using security patch a bit old but anyway I think it's fine, thats depends on you what you'll do with phone and considering are you really need that security patch that hard. Most of phones are getting them nearly per quarters of year.
And after unlocking bootloader is damn hard to hide from apps in Android 11. I was rooted like a month ago and I just give up. Thats not worth the effort you give. I used with root like a week than I realized I can do most of stuff I'm doing at phone without root/unlocked bootloader but I cannot do banking with root/unlocked bootloader. I think is the best part of rooting is you can backup your persist and modem partition if something goes wrong with your firmware in future you don't needed to deal with OnePlus's ****ty RMA process, they are this close to screw all persist partition.
If you have further questions I'll gladly answer them And If you want to root be sure to NOT use pre-modded boot images, they can broke all you fingerprint, camera, axonometry, gps sensors. Have a great day...
Click to expand...
Click to collapse
VERY USEFUL.
Do you know where we could find more "tricks" like those??? They're great!
Donno if anyone chimed in bit I'm using mobile banking with zero issues rooted. If done right it all works proper. The main reasons for me to root are to force chat heads. (Exposed) change the dpi (much more real state ) gravity box(volume skip screen off with no issues ran through exposed) along with a few other things inside gv.
Button mapper for screen on volume skips (usually cannot get it to work right for screen off long press skipping but this with gravity box is a seamless long press setup) titanium backup to freeze a few things.
There's an app for root that allows you to basically shut all sensors and everything per app. Xprivacy or some thing other)
I can't not lol