Develop Bugs

[Q] TOR?

Since I run TOR on my computer I figured I'd check into it for Android and wouldn't you know, it exists. In this age of tracking and privacy going out the door, it's nice to still be able to retain a bit of anonymity.
EDIT: I figured I'd add a small explanation for anyone that's interested in this and doesn't know what TOR is.
Without getting into great detail, some of which I'd have no clue what the hell I'm talking about, it's a way to be anonymous. If you do it correctly no longer will your IP address show up as you current IP which can be used to spy, hack, trace, ad target, and so on. Your IP will show up as something else. e.g. My current location is Overland Park, KS - my IP will reflect this, my ISP also knows my exact address from that IP. With TOR my IP shows up as being located in say, Russia. Problem solved, no more tacking and other bs.
This isn't a pass to do what you want online, you're still a human so act like it. It's just a take back a little bit of privacy and anonymity.
theSpam said:
To simplify things, TOR does onion routing which involves routing your traffic through a number of hosts to final host called the exit node. Exit nodes directly communicate with other hosts on the Internet. The use of exit nodes and encryption throughout this process provides anonymity. See this for more info: http://en.wikipedia.org/wiki/Tor_(anonymity_network)
Click to expand...
Click to collapse
Thanks theSpam
UPDATE: I fixed the issue of Orbot not connecting me to the TOR network. There are more in depth methods but I'll just give the quick and dirty version. After installing Orbot make sure everything is unchecked in setting except: start on boot, transparent proxying, tor everything.
Download ProxyDroid and in setting:
proxy host: 127.0.0.1
Port: 8118
Proxy type: HTTP
Auto connect: check
Global Proxy: check
don't mess with anything else unless you know what you're doing.
Now you can check your IP or use Orbot to check if you're on the TOR network. Enjoy.

Tor? I'm curious
dont send me pm's crying about how i hurt your feelings in a thread

So you know what Tor is then?
Well I installed it and so far it's working aside from not actually connecting me to the network. My IP stays the same so I guess I have to do a few things manually, oh well. When you first boot up and it's starting it eats the processor like a fat lady eats cake but that goes away after 15-20 seconds. On the plus side it doesn't start loading until after the system has finished loading completely so boot times aren't effected.

No sir I'm not sure what TOR is. Was hoping you might shed a lil light on the subject.
dont send me pm's crying about how i hurt your feelings in a thread

OK I updated the OP for you. Hopefully I got it right. I'm not a network genius so I may be a little off.

To simplify things, TOR does onion routing which involves routing your traffic through a number of hosts to final host called the exit node. Exit nodes directly communicate with other hosts on the Internet. The use of exit nodes and encryption throughout this process provides anonymity. See this for more info: http://en.wikipedia.org/wiki/Tor_(anonymity_network)
My main concern with this app is with how TOR works. Does anyone know if Orbot will turn your phone into node used for intermediary routing? (the desktop version does this)

theSpam said:
To simplify things, TOR does onion routing which involves routing your traffic through a number of hosts to final host called the exit node. Exit nodes directly communicate with other hosts on the Internet. The use of exit nodes and encryption throughout this process provides anonymity. See this for more info: http://en.wikipedia.org/wiki/Tor_(anonymity_network)
My main concern with this app is with how TOR works. Does anyone know if Orbot will turn your phone into node used for intermediary routing? (the desktop version does this)
Click to expand...
Click to collapse
There's an option in the settings for it but it's not activated by default. I couldn't imagine switching that option on while using 4G

Google Now over WiFi -- Fails due to MTU size?

Hi guys. I am not sure if this is a common problem, but I was having a difficult time getting Google Now to work whenever I was connected to my home WiFi network. It worked flawlessly however on my 3G data connection. I did a lot of search on this but couldn't find anything, so i figured I'd post it here in case anyone was having the same issue.
I basically took a tcpdump of a few Google Now query tests over WiFi, and noticed that there was a common problem of the google server not receiving the entire query data. Only the first packet was being received, and after that it was all duplicate acknowledgments of the initial packet, until the connection was reset. I decided to fiddle around with the MTU size as I was having similar problems with android devices over my operator's network, where having an MTU of 1500 was creating problems when the packet got larger while traveling through the network, thus exceeding the 1500 limit. Anyway, I set it to 1440 and as I expected, the problem was solved. I can now make normal Google Now queries using my WiFi network.
One thing that is still bothering me though is that the change I made is not permanent. I used the following command:
​ifconfig wlan0 mtu 1440
So I was wondering if there is a way to make this permanent on android. Does anyone know how to do this?
Thanks.

MTU
I also have this problem, mostly using K-9 Mail when sending larger emails (eg. with attachments).
MTU permanent change should solve the problem but I dont know how to do it.
Anybody ... ???

Nice catch...I was concerned a out this too..compliments
Inviato dal mio Galaxy Nexus con Tapatalk 2
---------- Post added at 03:42 PM ---------- Previous post was at 03:34 PM ----------
Modifying internals roms config would be lose the setting every flash or update..one thing come to my mind..if you put the command in the terminal emulator option to exec command at start of the emulator itself ,maybe you just nave to fire up that when needed and you should be done ..
Inviato dal mio Galaxy Nexus con Tapatalk 2

MTU
Great aproach mangusZen
This should be tested, only if I know how
I am just a phone user without much experience in hacking, willing to solve the problem.

bojan_ks said:
Great aproach mangusZen
This should be tested, only if I know how
I am just a phone user without much experience in hacking, willing to solve the problem.
Click to expand...
Click to collapse
Install terminal emulator , in its settings there's ' initial command' .
I added there - 'export PATH=/data/local/bin:$PATH; su - ; ifconfig wlan0 mtu 1440'
Command should be executed when you start terminal application..and yes it's a horrible hack

This is odd...
My phone is rooted, I've instaled terminal emulator and than started this command
ifconfig wlan0 mtu 1440
Click to expand...
Click to collapse
and it responded like this:
error: SIOCSIFMTU (Operation not permitted)
What is this???

When you start terminal you are not root user. You become root with ' su -' command , see my string
Inviato dal mio Galaxy Nexus con Tapatalk 2

Set MTU on your DSL wifi
DSL normally has a max MTU of 1492.
If you change the MTU on the wifi instead, it won't apply to gsm data.
Plus you can fix this problem if your phone isn't rooted

cm11: service at uid 1000 (com.qualcomm.timeservice?) contacts amazon ip??

Hi,
I just flashed cm-11-20150626-SNAPSHOT-XNG3CAO1L8-serranoltexx.zip on my brand new s4 mini. So far, so good.
Using AFWall+ as a firewall in whitelist mode I came accross the following lines in the network log file:
"2015-07-06 06:57:51.901","com.qualcomm.timeservice","com.qualcomm.timeservice","1000","","wlan0","192.168.178.20","54872","54.239.168.154","80","60"
"2015-07-06 06:57:51.908","com.qualcomm.timeservice","com.qualcomm.timeservice","1000","","wlan0","192.168.178.20","45011","54.239.168.100","80","60"
"2015-07-06 06:57:51.910","com.qualcomm.timeservice","com.qualcomm.timeservice","1000","","wlan0","192.168.178.20","33953","54.239.168.231","80","60"
"2015-07-06 06:57:51.912","com.qualcomm.timeservice","com.qualcomm.timeservice","1000","","wlan0","192.168.178.20","43091","54.239.168.99","80","60"
"2015-07-06 06:57:51.915","com.qualcomm.timeservice","com.qualcomm.timeservice","1000","","wlan0","192.168.178.20","59703","54.239.168.88","80","60"
"2015-07-06 06:57:51.916","com.qualcomm.timeservice","com.qualcomm.timeservice","1000","","wlan0","192.168.178.20","58289","54.239.168.95","80","60"
"2015-07-06 06:57:51.917","com.qualcomm.timeservice","com.qualcomm.timeservice","1000","","wlan0","192.168.178.20","58289","54.239.168.95","80","60"
These IP adresses belong to Amazon according to whois. As there is an extra ntp service in android this qualcomm service might be something else ...
I also noticed in AFWall+ that some more services are bounded to the UID 1000, like dev tools, fm radio, android system etc and that mobile network wont work without the services of this UID (wlan does).
I wonder if someone here can explain this and I can learn ...
Thanks and regards,
foxyu

Bypass for T-Mobile Tethering throttle on unlimeted plans?

This is quite easy on android but I honestly cant bring my self to give up on windows phone just yet. On android all I had to do was figure out the default TTL settings and then proceed to change them on all of my devices, 1 over the android factory ttl. For example, android TTL is 64, I set the devices I had to 65. Now comes the issue. I cannot for the life of me through google or system access figure out the factory TTL (Time to Live) on windows 10 mobile. Am I missing something? Also I don't know if the tethering function in the system outputs a different TTL compared to the direct os all together. I have a 950, 950 XL (Favorite), and Idol 4S that just arrived (couldn't pass up the 99$ sale) If someone can point me in the right direction I would be very grateful for their time. Maybe its possible there is a hack through the apn settings. I just know the 3g speed cap, which is actually more like 56kbs cap, not even close to what they state they are throttling it to and I have no problem bypassing that.

corvettezo7sp said:
This is quite easy on android but I honestly cant bring my self to give up on windows phone just yet. On android all I had to do was figure out the default TTL settings and then proceed to change them on all of my devices, 1 over the android factory ttl. For example, android TTL is 64, I set the devices I had to 65. Now comes the issue. I cannot for the life of me through google or system access figure out the factory TTL (Time to Live) on windows 10 mobile. Am I missing something? Also I don't know if the tethering function in the system outputs a different TTL compared to the direct os all together. I have a 950, 950 XL (Favorite), and Idol 4S that just arrived (couldn't pass up the 99$ sale) If someone can point me in the right direction I would be very grateful for their time. Maybe its possible there is a hack through the apn settings. I just know the 3g speed cap, which is actually more like 56kbs cap, not even close to what they state they are throttling it to and I have no problem bypassing that.
Click to expand...
Click to collapse
Someone posted the TTL for Windows phone here as 128. Not sure if it is accurate as it is an old post but his reply is from 2016...

nate0 said:
Someone posted the TTL for Windows phone here as 128. Not sure if it is accurate as it is an old post but his reply is from 2016...
Click to expand...
Click to collapse
Let me give that a try. I will set my computer to 129. Should do it theoretically unless its ported somewhere else.

nate0 said:
Someone posted the TTL for Windows phone here as 128. Not sure if it is accurate as it is an old post but his reply is from 2016...
Click to expand...
Click to collapse
TTL is correct, it is 128 just like windows 10 on the PC. Did not stop the throttled tethering. Windows Mobile must report to the network provider or re route the network through a separate IP or TTL setting. TTL set to 127 on android gave me full speed on the windows phone so definitely correct on the default TTL. Thank you. Now for the task of tearing into the system to see what the tethering setting uses.

https://forum.xda-developers.com/showpost.php?p=59328211&postcount=12
Ok, so it looks like it will rout the tethering service through a separate path if requested by the network. I understand this guy is talking about sprint but reading more in depth revealed to me that if any network requests it the network would be routed through a separate port. Much like androids
Code:
tether_provisioning_required=0
setting Microsoft has implemented
Code:
"EntitlementRequired"=dword:00000000
Sadly, much harder to access that registry value. Then again, i haven't tried to root or mod a windows phone yet so this will be the first time for me. I will try and keep reporting back when i find something new.

So far, nothing, Any ideas? Oddly enough, setting the TTL to 129 on the pc, or android, anything, has the same result. When i ping the default gateway it shows up as TTL 128 instead of 129. Can the TTL not be set above 128?

corvettezo7sp said:
So far, nothing, Any ideas? Oddly enough, setting the TTL to 129 on the pc, or android, anything, has the same result. When i ping the default gateway it shows up as TTL 128 instead of 129. Can the TTL not be set above 128?
Click to expand...
Click to collapse
Maybe set it manually in the registry?
https://technet.microsoft.com/en-us/library/cc957530.aspx

corvettezo7sp said:
So far, nothing, Any ideas? Oddly enough, setting the TTL to 129 on the pc, or android, anything, has the same result. When i ping the default gateway it shows up as TTL 128 instead of 129. Can the TTL not be set above 128?
Click to expand...
Click to collapse
I know this is an old thread, but just in case someone comes alone reading. The results you see are correct you should be pinging the 127.0.0.1( localhost) to see the changes not the gateway. By the way, that alone won't get the job done. They are quite aware of these old tricks.

Wifi and mobile data issue after degoogling

I recently considered completely degoogling lineageos and i succeeded partly.
1. Changed the system webview to bromite webview.
2. Changed the captive portals to
https://e.foundation/net_204/
http://204.ecloud.global
3. And finally changed the timeserver to pool.ntp.org
One of these steps happened to screw up things with the wifi and mobile data.
Wifi works just fine but has a "Limited connection" label on it.
And mobile data doesnt seem to work at all.
Has anyone experienced something similar or knows the solution?
Thanks in advance for your help.

When you are on wifi, are you connecting to a router that has a custom DNS server? I get the same thing, works just fine. Scroll through your router logs and device logs to see what is times out and adjust accordingly.
I lost mobile data on a previous device (LG v20) when I moved over to LOS and was messing around with APN. Given that mobile data runs through provider's server, it might be that the server it being blocked by a content filter or similar. Also, it might be that LOS's list of default APN are not updated with current information required by your provider.

My device uses nextdns through private dns.
I was using vanilla lineageos with microg and mobile data worked fine, after these steps something seemed to have messed up. I have tried resetting APNs too, didnt work.

DNS of wifi doesnt typically affect that of LTE, but might be different in your flavor of LOS.
Look at your logs on router and device.

Private dns is DNS over TLS implementation of android, it works on both wifi and mobile data. I havent changed anything related to dns for a long time. DNS doesnt seem to be the problem.
systool sntpc -sntpRequest
I can see simple ntp client requests like this, should i be looking for something else?

I'm curious as to how many requests you are seeing. I seem to recall android should only check every few days. Hmm.
Checked logs on a rooted v20 stock N7.1 that I keep around for tv and Roku and Plex control. I wasn't able to find a ntp or sntp entry in last 7 days, the length of my log. Firewall did not report any port 123 traffic either.
Incidentally, I am using 3.android.pool.ntp.org to sync with. Not sure where that came from, I don't remember it as being such as I prefer time.nist.gov.
I don't know what could be going sideways with data other than perhaps dns not working ( does ip# work on mobile?) on mobile and degraded showing on wifi.
This may be pointless, but if wifi is turned off, are you able to send/receive a mms? I ask because mms traffic to your phone is based on IP#, but mms traffic from phone has to (typically) resolve name of mms server.
I am just about out of ideas / suggestions.

Thank you for our help mate, i fixed the issue.
Everything is back to normal after changing the captive portal to
http://captiveportal.kuketz.de
https://captiveportal.kuketz.de
The one from e foundation seemed to be the problem. This one is from a security researcher Mike Kuketz.

The captive portal wrecked mobile data too? That is surprising and interesting.
Glad to see you are up and running.
Side note, do you still see same amount of sntp activity now?

deleted