Disable \ Enable allow peeking\ head up notification for incoming calls


Fuck off , i just hate this shit :

How to disable ? just use adb . Simple neat and you have just to do this :

sudo apt-get install adb 

connect to your linux box , please enable the developer settings on android

  1. If using stock Android, go to Settings > About phone > Build number. On a Samsung Galaxy device, go to Settings > About device > Build number. On an HTC device, go to Settings > About > Software information > More > Build number. On an LG device, go to Settings > About phone > Software info > Build number.
  2. Tap Build number seven times. After the first few taps, you should see the steps counting down until you unlock the developer options. Once activated, you will see a message that reads, “You are now a developer!”
  3. Go back to Settings, whereyou’ll find a Developer options entry in the menu.

Now enable the Usb Debugging on developer mode and Usb debugging (Security Settings)

now to DISABLE FUCKING : HEAD UP OR PEEKING SHIT JUST DO :

adb shell settings put global heads_up_notifications_enabled 0

HOW TO RESTORE the settings you just modified? replace 0 with 1 and you have that shit back.

adb shell settings put global heads_up_notifications_enabled 1

download recursively a folder from apache server


https://stackoverflow.com/questions/23446635/how-to-download-http-directory-with-all-files-and-sub-directories-as-they-appear

kubuntu Network issue www.google.com: Temporary failure in name resolution but ping 8.8.8.8 works.


FAST SOLUTION IF YOU CAN CONNECT TO YOUR FUCKIN ROUTER BUT NOT INTERNET MOST LUCKY YOU HAVE A PROBLEM WITH DNS check this file

 cat /etc/resolv.conf  

if you have something strange like this that should be the local dns but you should have the same problem of mine


nameserver ::1
nameserver 127.0.0.1

infact changin the file with this IT WORKS! (THESE ARE GOOGLE DNS …)

# Generated by Connection Manager 
nameserver 8.8.8.8
nameserver 8.8.4.4

SO EDIT THE FILE AND TRY RE-CONNECT and check if you are using DNS WITH :

nmcli dev show | grep DNS

GENERAL.CONNECTION:       DNS ON
IP4.DNS[1]:               192.168.0.1 # YOUR ROUTER
IP4.DNS[2]:               8.8.8.8
IP4.DNS[3]:               8.8.4.4

You should now be able to get internert back again … but this file resolv.conf will be overwritten by network manager or other software again after the reboot for example rebooting i got this

# Generated by NetworkManager

search fritz.box
nameserver 127.0.0.53

now to determine which software is editing the resolv.conf you can just do

head /etc/resolv.conf

Some utilities don’t include a comment in the resolv.conf file, but you can identify these programs by checking for symbolic links with the following command:

ls -l /etc/resolv.conf

in my case was connman that was messing the things , so i removed it with 

sudo apt-get remove connman 

i have copied the above stuff from this well written article  and please read it for a more complete view about resolv.conf and dns 

MY SILLY STORY

Well well , FUCK OFF , here again with a network issue i was in panic cuz i was not able to get a connection even after a fuckin reboot , yes i did like the window guy that reboot trying hoping it will fix every thing …. instead… FUCK OFF it doesn’t work i was working in a mirror fuckin shit for android and i just messed with wpa_supplicant thanks to this shit https://github.com/intel/wds and in particular for this command :

 sudo hostap/wpa_supplicant/wpa_supplicant -ddt -u

now this shit has messed up i guess something and i tried everything i had in mind expecially

sudo pkill  wpa_supplicant ; sudo systemctl stop NetworkManager.service ; sudo systemctl start NetworkManager.service 

and the silly system worked i was connected with my fuckin router but i got no-INTERNET

now i tried to get rid of my atheros wifi driver with

sudo rmmod atkh9k  && sudo modprobe ath9k 

If you don’t know which module you have to remove just do :

lspci | grep -i wireless 
07:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)

#or with a filter like awk you can get the first numbers with


sem@semvaio18:~$ lspci | grep -i wireless | awk '{print $1}'
#output example 07:00.0

Now you got the first numbers you can do :

 lspci -vv -s 07:00.0 | grep -i driver 

#that will give you the answer :

Kernel driver in use: ath9k

but nothing changed … so i tried

ping -c3 www.google.com 
#but fuckin got this shit
ping: www.google.com: Temporary failure in name resolution
#instead with
ping -c3 8.8.8.8
#IT WORKED 3 packets transmitted, 3 received, 0% packet loss, time 2003ms

so it was the software problem and it turned out that was connman which i have installed to test screen mirroring thing with android and not the networkmanager.