Related
EDIT: We have NAND WRITE ACCESS NOW, NO NEED TO USE THIS ANYMORE! Do the NAND ROOT then Install AdFree from the Market!!!
Sadly we don't have access to write to the NAND on the Evo outside of the recovery console(yet). Some apps such as "AdFree" By BigTinCan do not work for us, as it doesn't have permission for this...
So we must do this manually...
Choose a hosts file!
You need to do is decide where to get your hosts file that will block them. I am attaching the one I am using, but you can find more all over the net
My hosts file (Which is both other options combined)
Another Option
Another option
Once you have one, put it into the tools Android Tools Directory (C:\AndroidSDK\tools for most people).
Copy the Hosts file to the device!
1. ) The phone must be rooted. (Thanks Toast)
2. ) Boot the phone into recovery (Where it says: RECOVERY INSTRUCTIONS).
3. ) Start up ADB Shell
Code:
C:\AndroidSDK\tools>adb shell
4. ) Mount the System Partition
Code:
# mount /dev/block/mtdblock4 /system
5. ) Exit Adb Shell (Press Control+C)
6. ) Push the hosts.txt file to the device.
Code:
C:\AndroidSDK\tools>adb push hosts.txt /system/etc/hosts
7. ) Reboot Device
Code:
C:\AndroidSDK\tools>adb reboot
That's it, not hard at all. Sadly as time goes on, more ads will slip through the cracks, and you have to do this again.
Quick Q&A:
Q: How do I root the phone?
A: Read this thread.
Q: How do I boot into the recovery console?
A: Read this thread.
Q: How do I set up/what is ADB?
A: Read this thread.
Q: Is removing ads wrong?
A: Probably.
Q: What benefits do I get from removing ads?
A: Less distractions, faster load times, more of the actual app/game will be shown.
Q: I still have a question! How do I...?
A: Answer
Credits:
Toast
Joeykrim
BigTinCan
The people that put the list together in this thread.
Thank you so much! I was really pissed that AdFree didn't work!
TheBiles said:
Thank you so much! I was really pissed that AdFree didn't work!
Click to expand...
Click to collapse
pissed really? its day 2 with the evo.. things will happen. I would be pissed bout the oil spill but mildly annoyed that adfree didnt work
joey3002 said:
I would be pissed bout the oil spill but mildly annoyed that adfree didnt work
Click to expand...
Click to collapse
No hate on TheBiles, but this ^. Sometimes we all need to take a step back and see how ****ed up our priorities are. Myself included.
@BPglobalPR....follow it.
currently boycotting all BP products follow @boycottBP
joey3002 said:
pissed really? its day 2 with the evo.. things will happen. I would be pissed bout the oil spill but mildly annoyed that adfree didnt work
Click to expand...
Click to collapse
Well I use "pissed" in a way that is synonymous for "annoyed." My reaction was more like, "Hey, this doesn't work. Damn."
TheBiles said:
Well I use "pissed" in a way that is synonymous for "annoyed." My reaction was more like, "Hey, this doesn't work. Damn."
Click to expand...
Click to collapse
lol, i know.. i was busting balls
odd. this looks a lot like my thread here , posted in a section where it probably belongs
beatcha to it, my man
thanks to the OP.. I just did this last night and it works great.. what free apps can i test just to verify lol...
timothydonohue said:
posted in a section where it probably belongs
Click to expand...
Click to collapse
pheeew i thought the forum police would never show up...
kidding.
Can this be done if I rooted using UnrEVOked?
apristel said:
pheeew i thought the forum police would never show up...
kidding.
Click to expand...
Click to collapse
my point being that
a) i've already posted this up. if tenny had searched, he would have found my thread and would have seen that his was not needed
b) i didn't post it in development, which is designed for kernels, ROMs, radios, etc
honestly, the evo forum is, hands down, the least organized forum that i've seen here at xda. so many people ran out and bought the evo and now come here, just post up without searching, ask the same questions over and over, etc. we end up with 75 threads all saying the same thing. it's ridiculous.
timothydonohue said:
my point being that
a) i've already posted this up. if tenny had searched, he would have found my thread and would have seen that his was not needed
b) i didn't post it in development, which is designed for kernels, ROMs, radios, etc
honestly, the evo forum is, hands down, the least organized forum that i've seen here at xda. so many people ran out and bought the evo and now come here, just post up without searching, ask the same questions over and over, etc. we end up with 75 threads all saying the same thing. it's ridiculous.
Click to expand...
Click to collapse
Well depends on what you consider development, some consider any writing to the system partition to be some form of development...
Still though I apologize for posting this after you, I did search but when I originally made this, just I got distracted and didn't submit the thread until later. Don't worry I never saw your thread and did all the research on my own.
But complaining about this thread in the wrong section TWICE does no good... the mods are moving threads and haven't moved this yet... honestly who cares quit *****ing and let's move on.
WillJitsu said:
Can this be done if I rooted using UnrEVOked?
Click to expand...
Click to collapse
I do not think so. You need to boot into recovery for anything to stick, so if you can't then no.
hmmm...strange that when I push this hosts.txt file over to /system/etc/hosts, my entire device just hung. I have to revert back to original hosts file.
Any ideas?
I noticed it removed the ads from Jewels but it didn't remove them from chompSMS. Since I use text more than play games, I'd appreciate it if someone figures out how to remove the ads from chompSMS to let me know. O btw, I used the original hosts.txt file the OP uses.
i don't know about chompsms, but if you grab the hosts file from my thread, in q and a, it eliminated the ads from handcent (and everything else i run). the hosts file i posted was updated from adfree 3 days ago.
@vboy, do the push while in recovery mode and with /system mounted for write permissions. there shouldn't be any 'hang' because it's not done while the phone is in android.
Sorry I wanted to edit my post and let you know it works with chomp but as a new user I couldn't. The frame is there, but no more ad! Thanks
Sent from my HTC EVO 4G using Tapatalk Pro.
vboyz103 said:
hmmm...strange that when I push this hosts.txt file over to /system/etc/hosts, my entire device just hung. I have to revert back to original hosts file.
Any ideas?
Click to expand...
Click to collapse
Are you pushing it as hosts.txt or just as hosts?
Tenny said:
Are you pushing it as hosts.txt or just as hosts?
Click to expand...
Click to collapse
I'm pushing it in recovery mode and pushed over to evo as /system/etc/hosts. I think it caused some issue with my phone in routing for hosts. Whenever I start using apps with data, then it's start hanging. I removed and revert back to hosts file and all is good.
Since I've gotten my Sidekick, I've noticed on most ROMs a horrible tendency to not register key-presses on the physical keyboard. There was one ROM early on that didn't do this (or very little) and one of the versions of RAGE was very good. I'm running GOV3.2 Bulky right now and it's not horrible, but it's noticeable. Does anyone have an idea of what might cause this? Thanks.
ged92781 said:
Since I've gotten my Sidekick, I've noticed on most ROMs a horrible tendency to not register key-presses on the physical keyboard. There was one ROM early on that didn't do this (or very little) and one of the versions of RAGE was very good. I'm running GOV3.2 Bulky right now and it's not horrible, but it's noticeable. Does anyone have an idea of what might cause this? Thanks.
Click to expand...
Click to collapse
I thought my keyboard was going bad or i just did not press the key all the way, now im on stock and i have not had that issue, hope someone finds the rom
ultraprimeomega said:
I thought my keyboard was going bad or i just did not press the key all the way, now im on stock and i have not had that issue, hope someone finds the rom
Click to expand...
Click to collapse
I wonder what the issue is that's causing it to show up on custom ROMs. Though, I've had it on the stock ROMs as well.
Have you tried this version of the kernel? Along with the removal of the keystroke logger, it also contains a patch that allows you to lower the keystroke timer delays... If you are experiencing dropped keystrokes, this could help, as the patch was designed for tht very issue.
http://forum.xda-developers.com/showthread.php?t=1663622
yogi2010 said:
Have you tried this version of the kernel? Along with the removal of the keystroke logger, it also contains a patch that allows you to lower the keystroke timer delays... If you are experiencing dropped keystrokes, this could help, as the patch was designed for tht very issue.
http://forum.xda-developers.com/showthread.php?t=1663622
Click to expand...
Click to collapse
Thank you!!!!!!!! I went ahead and dug into that thread. I do have that kernel already on my phone. I looked at the thread linked in that thread that gives a patch to adjust the timer delay and column delay in the kernel. HOWEVER, I'm not knowledgeable enough to apply that patch to my phone as it's given. Elsewhere in that thread, someone gave the commands to edit the settings manually through a terminal which I did through Android Commander on my PC and it worked wonders! Being the suspicious type, I guessed that the settings might not keep after a reboot. Unfortunately, that is the case and I had to reapply the settings after my phone finished restarting. So, I'll have to play with this a bit more to get it to keep, but thank you for showing me this!
You're welcome! That patch was made just for this issue. And yeah, it doesn't stick after a reboot, so we could either compile the kernel with chosen settings added in, or make a simple init.d script. I never did either one lol, was too lazy to try editing and building the kernel from source, and was on the stock ROM so I thought maybe it had no init.d support. You could probably create a file with those same commands used in Terminal, and throw it in your init.d folder to change the settings at boot.
yogi2010 said:
You're welcome! That patch was made just for this issue. And yeah, it doesn't stick after a reboot, so we could either compile the kernel with chosen settings added in, or make a simple init.d script. I never did either one lol, was too lazy to try editing and building the kernel from source, and was on the stock ROM so I thought maybe it had no init.d support. You could probably create a file with those same commands used in Terminal, and throw it in your init.d folder to change the settings at boot.
Click to expand...
Click to collapse
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?
ged92781 said:
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?
Click to expand...
Click to collapse
+1
I've noticed this problem and thought it was just me :$
I've had this happen as well as my screen thinking I was pressing it in one location when I wasn't even touching the phone. :s Had me at my wits end.
Sent from my SGH-T839 using xda premium
To those interested in the commands I used to fix the keyboard, see below. If you reboot your phone, these settings will go away and you will need to input these commands again. For a permanent fix, someone will need to add them to a kernel that can be flashed. To use these commands, your phone must be rooted. I've successfully used Android Commander to enter these commands from my PC while my phone is connected via USB.
The current timer delay may be read with:
cat /sys/devices/platform/s3c-keypad/timer_delay
The default is 5 if I remember correctly.
A new timer delay may be set with:
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
The default 300 µs column delay value may be read with:
cat /sys/devices/platform/s3c-keypad/column_delay
A new delay may be set with:
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
In either command, you may experiment with different values by changing the 1 or the 30 in either command to what you want. I believe the lowest is 1 and the max is 256 for the timer delay. If you damage your phone running these commands, that's on you. I'm just telling you what I did and feel worked for me. YMMV. Also, if you don't want to connect your rooted phone to your PC and want to use Terminal Emulator from the Play store, that will work too. You need to enter 'su' prior to running the above commands and grant the terminal super user permissions for the commands to take.
ged92781 said:
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?
Click to expand...
Click to collapse
I'll work on it for the next releases of the Bi-Winning roms and also try to attach flashable zips.
RicAndroid said:
I'll work on it for the next releases of the Bi-Winning roms and also try to attach flashable zips.
Click to expand...
Click to collapse
Thank you!
ged92781 said:
Thank you!
Click to expand...
Click to collapse
You are very welcome! All done, BTW. Posting my updates now.
Permanent Fix(Manual way)
Taking the timer_delay and column_delay tricks shown above...I was able to make an init.d script(pretty easy, tbh) but don't feel it merits an update.zip since it's so easy. What I did was:
1. go to /etc/init.d
2. find the last script(In GOV3.3 it's 18complete) and rename it - adding one to the sequence(In my case I renamed it to 19complete)
3. make a new file name 18keyboardfix(The number depends on your rom, really...like if you renamed the above file to some thing like 33complete, you'd call this 32keyboardfix. Easy? right?)
4. Open the file you just created and put:
Code:
!#/system/bin/sh
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
5. Set the permissions to rwxr-xr-x or whatever the numeric equivalent is. (0755, iirc)
6. Reboot
7. (Optional) Recheck the values with the following commands:
Code:
cat /sys/devices/platform/s3c-keypad/timer_delay
Code:
cat /sys/devices/platform/s3c-keypad/column_delay
I take no credit for this fix. Really, it was all ged92781 for providing the commands. All I did was find a way to make it permanent(Well, it's just reset when the devices is turned off and the init.d scripts set it back to you desired values, but that's debatable on whether it's permanent or not...either way...it works and is a simple fix)
SammaelAkuma said:
Taking the timer_delay and column_delay tricks shown above...I was able to make an init.d script(pretty easy, tbh) but don't feel it merits an update.zip since it's so easy. What I did was:
1. go to /etc/init.d
2. find the last script(In GOV3.3 it's 18complete) and rename it - adding one to the sequence(In my case I renamed it to 19complete)
3. make a new file name 18keyboardfix(The number depends on your rom, really...like if you renamed the above file to some thing like 33complete, you'd call this 32keyboardfix. Easy? right?)
4. Open the file you just created and put:
Code:
!#/system/bin/sh
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
5. Set the permissions to rwxr-xr-x or whatever the numeric equivalent is. (0755, iirc)
6. Reboot
7. (Optional) Recheck the values with the following commands:
Code:
cat /sys/devices/platform/s3c-keypad/timer_delay
Code:
cat /sys/devices/platform/s3c-keypad/column_delay
I take no credit for this fix. Really, it was all ged92781 for providing the commands. All I did was find a way to make it permanent(Well, it's just reset when the devices is turned off and the init.d scripts set it back to you desired values, but that's debatable on whether it's permanent or not...either way...it works and is a simple fix)
Click to expand...
Click to collapse
Uh, oh....I used echo "number" /proc/sys/devices/platform/s3c-keypad in my script. Will I have to change it?
RicAndroid said:
Uh, oh....I used echo "number" /proc/sys/devices/platform/s3c-keypad in my script. Will I have to change it?
Click to expand...
Click to collapse
Idk, honestly. Try and see if your script works first, if not, then use the one I made using the commands ged92781 provided. Now...to find a way to fix the spaztic touch screen...that'll be tricky.
SammaelAkuma said:
Idk, honestly. Try and see if your script works first, if not, then use the one I made using the commands ged92781 provided. Now...to find a way to fix the spaztic touch screen...that'll be tricky.
Click to expand...
Click to collapse
I'm using your commands, dude. I'm very into details....so thanks!
RicAndroid said:
I'm using your commands, dude. I'm very into details....so thanks!
Click to expand...
Click to collapse
Lol. No problem. And good luck with the custom rom cooking.
I have this really odd issue with my Z3 in that I cannot, on any network (wireless or carrier), resolve through DNS forum.xda-developers.com. I first noticed it because my XDA premium HD app couldn't connect to the forums at all. I did a bit of digging and managed to uncover that I can't connect to anything related to the forums. I CAN however connect to the main portal on www.xda-developers.com.
What I have tried:
1. Different wireless networks - no luck.
2. Other devices - all work fine on all the tried networks.
3. Carrier network (Rogers CA) - no luck, but again with other devices no problem
4. Ping and nslookup through Fing network tools - not able to resolve
5. Ping and nslookup through terminal emulator - not able to resolve
6. hosts file just has the standard localhost entry
7. Browse with Chrome just gives the standard error for unresolvable DNS
8. So far I have only seen this happen on the forums.xda-developers.com address.
I am running a Z3 (D6603) with a custom ROM per below.
Pre-rooted ROM from this thread: http://forum.xda-developers.com/z3/general/d6603-5-0-2-flashable-stock-23-1-0-690-t3056361
D6603_23.4.A.0.546_Customized_US_SuperSU_XZDR2.8.2 1 thanx to @julianbl
It's an odd one for sure, so if anyone has any creative ideas for me to test out please let me know. Thanks in advance.
use titanium backup or something similar to disable/uninstall "PrototypeProtection".
It's an app that sony uses to block certain sites when the bootloader is unlocked.
Julián
Go in Root Explorer,
Mount in R/W
Go to: system/etc/hosts
Try to add a xdadevs rule,
examp:
#207.244.72.9 http://forum.xda-developers.com
then reboot your device just normal.
i hope it works,
- bram
julianbl said:
use titanium backup or something similar to disable/uninstall "PrototypeProtection".
It's an app that sony uses to block certain sites when the bootloader is unlocked.
Julián
Click to expand...
Click to collapse
I should note that I have not unlocked my bootloader. I tried this and it has unfortunately had no effect. Open to other suggestions though, thanks for trying.
[EDIT] I may have spoken too soon. I tried connecting after disabling (freezing) that app and didn't have any luck. I rebooted the phone, and things are back online. I will do some further testing to get concrete and repeatable behavior documented. Thanks @julianbl
bramybram said:
If you see a rule wiht xda-developers.com in it
Click to expand...
Click to collapse
Thank for the suggestion. As noted in my OP though, the hosts file is empty except for the default localhost entry.
Swaziboy said:
Thank for the suggestion. As noted in my OP though, the hosts file is empty except for the default localhost entry.
Click to expand...
Click to collapse
Try to add a XDA Rule with a "#" before the rule instead?
bramybram said:
Go in Root Explorer,
Mount in R/W
Go to: system/etc/hosts
Try to add a xdadevs rule,
examp:
#207.244.72.9 http://forum.xda-developers.com
then reboot your device just normal.
i hope it works,
- bram
Click to expand...
Click to collapse
bramybram said:
Try to add a XDA Rule with a "#" before the rule instead?
Click to expand...
Click to collapse
Thanks for your desire to help - given what we've found out so far this isn't a HOSTS file issue. There is no entry in the hosts file, and as such any DNS resolution for the domain should leverage DNS servers based on DHCP settings.
In my mind, adding a rule in the HOSTS file to force resolution of the domain, might work but it's not a real fix as to why this is happening.
Refer to my previous note that the suggestion to block the "PrototypeProtection" app is what has resolved the issue so far.
Thanks again though @bramybram, appreciate your willingness to help.
Hey there, I had the same issue... It is quite frustrating, I guess it's some bug in the firmware you installed (since I used the same to flash my z3)... I resolved it by flashing another firmware, I suggest you the D6603_23.4.A.0.546_Customized_NCB_SuperSU_XDR2.8.2 1 (https://mega.co.nz/#!GJQVBL6K!x8bB2HS-TbpbZTb5IamrJB_xduDMHl9j6jQyAqrJpVQ) one, it worked for me
Hi every one
just need to confirm from professional people here , i need to edit build.prop on my A9 device without rooting so that i could make some connection with my car screen (stupid screen accept only Samsung and LG) , Is that possible?
amro ibrahim said:
Hi every one
just need to confirm from professional people here , i need to edit build.prop on my A9 device without rooting so that i could make some connection with my car screen (stupid screen accept only Samsung and LG) , Is that possible?
Click to expand...
Click to collapse
First, this question gets asked A LOT so a simple search here or google will show numerous others asking this and their findings. It doesn't matter if its not specifically referring to HTC A9 or in this specific forum either.
That being said....to answer your question.....NO! ^_^ You will most likely need root to even access the system root folder where your build prop. You may find it using some app possibly that doesn't require root, open it and change values, HOWEVER, you will never be able to save these changes without root, sorry.
If you are knowledgeable on unpacking system images or have firmware.zip/tar etc that you can dig through and find the build prop, edit it on windows/linux/mac repack or rezip and flash it successfully....thats one way.
Another way would be to use ADB to pull what you want and push it back to system afterwards.....but not to sure as my phone(s) usually are rooted and never tried to use ADB unrooted. Somethings tells me that this too won't work but go for it.
mcbright80 said:
First, this question gets asked A LOT so a simple search here or google will show numerous others asking this and their findings. It doesn't matter if its not specifically referring to HTC A9 or in this specific forum either.
That being said....to answer your question.....NO! ^_^ You will most likely need root to even access the system root folder where your build prop. You may find it using some app possibly that doesn't require root, open it and change values, HOWEVER, you will never be able to save these changes without root, sorry.
If you are knowledgeable on unpacking system images or have firmware.zip/tar etc that you can dig through and find the build prop, edit it on windows/linux/mac repack or rezip and flash it successfully....thats one way.
Another way would be to use ADB to pull what you want and push it back to system afterwards.....but not to sure as my phone(s) usually are rooted and never tried to use ADB unrooted. Somethings tells me that this too won't work but go for it.
Click to expand...
Click to collapse
Actually i searched a LOT but i have found the TWO answers "Yes you can" AND "No you can not" , also people says yes you can giving steps i have no idea about it like this one
1. Make a process which executes "getprop" from the "/system/bin/getprop" directory and initialize the String which we want to get (ro.board.platform in example).
2. Make a BufferedReader which gets the value (String) by retrieving the data from a inputStreamReader().
3.Convert the BufferedReader to String.
. That is why i asked here again to get clear answer which i get it and many thanks for you
amro ibrahim said:
Actually i searched a LOT but i have found the TWO answers "Yes you can" AND "No you can not" , also people says yes you can giving steps i have no idea about it like this one
1. Make a process which executes "getprop" from the "/system/bin/getprop" directory and initialize the String which we want to get (ro.board.platform in example).
2. Make a BufferedReader which gets the value (String) by retrieving the data from a inputStreamReader().
3.Convert the BufferedReader to String.
. That is why i asked here again to get clear answer which i get it and many thanks for you
Click to expand...
Click to collapse
LOL i understand the frustration. I also spend a ridiculous amount of time scouring forums and any other place online for the many questions i need help with only to get fractured/incomplete answers or conflicting ones like you stated where it seems like the answer is both yes and no or whatever....its a real pain. Truthfully, I said you wouldn't be able to do this without root due to the level of difficulty of the other options trying without root. Creating bufferedreader etc is all Java Programming. You will need a decent working knowledge of java programming to be able to do what that guide was talking about.....i figured you might not have that so I said that NO to your question here. I know some of what that guide was explaining enough to create some of that they described but still not enough to feel comfy attempting. Your best option, i think, will be to extract the build prop from a stock.img and repack the system.img after editing the build.prop. Use 7zip to unzip/rezip the system.img and notepad++ to open/edit the build.prop and flash image in your recovery. You could also use Android Kitchen if you can. Plenty of tutorials on this. I linked two below for ya though. '
What were you looking to edit in the Build.prop anyhow? I assume you are disinclined to root/unlock bootloader for warranty issues correct?
BTW, sorry for such a late response...I am not always here for days at a time usually so.....
dsixda's Android Kitchen - http://forum.xda-developers.com/showthread.php?t=633246
Super-Rs - http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296
mcbright80 said:
LOL i understand the frustration. I also spend a ridiculous amount of time scouring forums and any other place online for the many questions i need help with only to get fractured/incomplete answers or conflicting ones like you stated where it seems like the answer is both yes and no or whatever....its a real pain. Truthfully, I said you wouldn't be able to do this without root due to the level of difficulty of the other options trying without root. Creating bufferedreader etc is all Java Programming. You will need a decent working knowledge of java programming to be able to do what that guide was talking about.....i figured you might not have that so I said that NO to your question here. I know some of what that guide was explaining enough to create some of that they described but still not enough to feel comfy attempting. Your best option, i think, will be to extract the build prop from a stock.img and repack the system.img after editing the build.prop. Use 7zip to unzip/rezip the system.img and notepad++ to open/edit the build.prop and flash image in your recovery. You could also use Android Kitchen if you can. Plenty of tutorials on this. I linked two below for ya though. '
What were you looking to edit in the Build.prop anyhow? I assume you are disinclined to root/unlock bootloader for warranty issues correct?
BTW, sorry for such a late response...I am not always here for days at a time usually so.....
dsixda's Android Kitchen - http://forum.xda-developers.com/showthread.php?t=633246
Super-Rs - http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296
Click to expand...
Click to collapse
Thanks again for your replay , actually i still trying to proceed your way .. i think i am too close to do it , but you know after one or two hour of Trying&searching i say to my self let us unlock this phone and finish this matter .. any way i am using the Android Kitchen and i hope i could do it
Hi Again Folks!
This is my first shell script and I didn't think twice before showing it to everyone, look the Github Repo. It is a script that prevents access to the internet until this application is executed when system boots up!
What do you think about it?
Devmobdroid said:
Hi Again Folks!
This is my first shell script and I didn't think twice before showing it to everyone, look the Github Repo. It is a script that prevents access to the internet until this application is executed when system boots up!
I accept criticism hahahaaa
Click to expand...
Click to collapse
How about changing the title of your thread by adding a description of what the script does, otherwise, your thread/script might get overlooked if users can't tell what your script is for by reading the title of the thread, if they don't find it interesting, they probably won't open/read your thread to discover your script.
Droidriven said:
How about changing the title of your thread by adding a description of what the script does, otherwise, your thread/script might get overlooked if users can't tell what your script is for by reading the title of the thread, if they don't find it interesting, they probably won't open/read your thread to discover your scri
Droidriven said:
How about changing the title of your thread by adding a description of what the script does, otherwise, your thread/script might get overlooked if users can't tell what your script is for by reading the title of the thread, if they don't find it interesting, they probably won't open/read your thread to discover your script.
Click to expand...
Click to collapse
Yeah, it's true. I made the changes now...
Click to expand...
Click to collapse