yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] solarpenguin:
I had this happen on previous upgrades but found "restoring to factory" from recovery fixed my issues following the upgrade.

Running 89 for days now and no random reboots.
[Captivate Android Development] br123:
The MAC address of a device never changes. Its the IP address that can change every time you connect, unless you've assigned your device a static IP address.

You can spoof the MAC address, yes, but otherwise it doesn't change.
[Captivate Android Development] zmore:
Your IMEI and h/w MAC don't change when tethered. Everything is the same except the data being 'proxied' through your phone.

The carriers catch "illegal" tethering and/or wifi hotspot usage by inspecting the packets associated with your phone going over their network and looking for suspicious non-encrypted data such as a User-Agent string from a web browser on your PC.

e.g.: my PC browser's user-agent is:

Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0

and my phone is:

Mozilla/5.0 (Linux; U; Android 2.3.5; en-us; SGH-I897 Build/GRJ22) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1

(It'd also be a little suspicious if most of your traffic was tunnelled (over an encrypted VPN), but I doubt they'd call you on that.)
[Captivate Android Development] TheTodFather:
This is exactly why i posted this. I just want to better understand how they are exactly catching this. It's this kinda of info i'mlooking for. So my question again, why is it that that iphones are easier to target?

One more thing to add, I also heard that doing packet inspecting like you mention cost At&t money to do (something at&t doesn't want to do) whereas the iphone they can cross check the mac adresses and not have to go through more evasive ways to track? I'm probably worng but i'm just grabbing at straws here.

Like I said, I work for at&t and in our classes, I've read that cross checking the macs is how they catch tethering.
[Captivate Android Development] ninjuh:
Can I flash any of the gingerbread modems from the sticky thread in cwm for use with cm7? Also is it necessary to wipe cache/dalvik cache afterwords?
[Captivate Android Development] RockRatt:
Yes you can BUT you need to make sure it is in a CM7 packaging. OR you can easily make them yourself from ANY modem.

To make the yourself just download ANY/MULTIPLE modems to your phone. Download one of the CM7 Modems made for CM7. Then use root explorer and extract the modem by long pressing on the modem zip you downloaded. Do the SAME for the CM7 modem zip. Go to the extracted folder. Open up the NEW modem file and then long press on the modem.bin and hit copy. Now back out and the open the CM7 modem zip file and long press on its modem.bin and delete. Then PASTE which will copy the NEW modem inside the CM7 package. Then back out and long press on the one you just pasted the modem.bin file into and RENAME it to match the NEW modem name. Then back out and again long press on the file that you just renamed and hit zip this file. Then go to the zip file folder. Copy the NEW zip file and then go to /sdcard and paste the NEW modem zip inside. Now you can keep doing this to as many modems you want to try. Once you are done then reboot phone into recovery mode, choose zip, choose zip, pick the new modem file and install it. You CAN wipe cache and Dalvich cache if you want to but I almost never do.

This is VERY EASY to do so don't let my instructions seem like a lot. Once you do it you will see what I mean. If by chance you cannot do it shoot me a pm with what/which modems you want and I will try to make them for you.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] nkrick:
Without getting too much into legality of redistributing Google apps, I think that most of the ROMs on xda "get around" this by being in a grey area of tweaking existing manufacturers ROMs that already include gapps. Google's goal was to prevent devices that do not originally include gapps from getting gapps because then Google doesn't get their licensing fees. Mainly, Google wanted to prevent OEM's from releasing official firmware that includes gapps without paying for them. Since most of the devices being developed for on XDA originally came with gapps, Google would create a lot of pissed off developers and power users if they tried to prevent redistribution of gapps on these ROMs.

If Google was smart, they would allow any device to have the Market installed on it, and then do a check on the type of device. If you have a device that was not originally licensed for gapps, then allow use of the Market, but charge a nominal fee for apps like maps, places, navigation, etc, or offer a "bundle" that for the same price as an OEM licensing gapps, you can purchase it for your unlicensed device.
[Captivate Android Development] loserskater:
But what about when you use browsers such as Dolphin where you can change your UA?

I believe how they catch people is by the TTL (Time To Live).

This is from an Iphone forum, but is still pretty much the same with Android. Not sure about the TTL for Android packets though.
[Captivate Android Development] SeriousBizznass:
I'm getting constant force closes, been this way for about 5 updates. Starting to get annoying when you try and make a call and the framework for the phone crashes.
[Captivate Android Development] jacorso:
It looks like the the TTL is set to 64. You can change that yourself though.

/proc/sys/net/ipv4/ip_default_ttl
[Captivate Android Development] raz123:
Bug!

DTMF key presses are not being transmitted when using the SIP protocol!

ie:

>> "Press 1 to reach customer service"

<< "1"...

>> [...] "Press 1 to reach customer service"

<< "111111111111111111111"

>> [...] "Press 1 to reach customer service"

:mad:

Yes, "Audible touch tones" is enabled under the "Sound settings" menu.
[Captivate Android Development] techmik67:
well, gosh, with all the info you provided, logcats and dmesgs and the like, I'm sure we'll have you fixed in an instant......
[Captivate Android Development] zmore:
I don't buy that they're only using TTL, because:

1) if that one-variable "secret" was confirmed, then everyone running a custom android ROM would simply use an app to set their TTL to default+1 when tethered (if the ROM itself didn't have this baked-in, and I bet CM would do it), and for those not running a custom ROM, they'd hack their client device TTL instead (changing it from 64 to 65 on linux and macosx, and from 128 to 65 in the (modern) Windows registry).

2) they would have to be checking the TTL very close to the first hop for this to be accurate, or they'd have to know exactly how many hops away they were when checking. (well, except for tethered Windows devices, which is the vast majority of 'em, since they start at a huge TTL of 128, it'd still be much greater than expected)

3) since they're already doing packet inspection, why not just look at the data anyway to make sure instead of making assumptions?

Then again, maybe they are only using TTL. Nobody said the carriers were smart, especially since they're pulling this greedy **** to begin with. It's like the early days of the internet when ISPs tried (and failed) to charge you for each computer connected to the broadband pipe you were already paying for.
[Captivate Android Development] dave1977nj:
So in short terms get any cm7 modem zip package and you replace the modem.bin with the new one you want to use.. one question when you say "RENAME it to match the NEW modem name" you mean rename the zip package?
[Captivate Android Development] melbourne408:
The renaming doesn't play a role, just ridding the "JL2" for example and putting "KG3" is there mainly for reference so you know what modem your flashing.

Sent From My Swaggin 1.6 Son Of A Glitch
[Captivate Android Development] RockRatt:
As said above me the ONLY REASON to rename it would be so you KNOW what modem is inside. For example the original CM7 modem name you used was radio-cm-7-GalaxyS-JK4-signed.zip you would just rename it to radio-cm-7-GalaxyS-TUBJV6-signed.zip if you had added the TUBJV6 modem inside the file before you zipped it back up.

EDIT2: Here is a post I just made in a modem thread and attached quite a few CM7 modems with links to my dropbox. Here is the link to that post thread: http://xdaforums.com/showthread.php?t=1227717

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] :
The second I am done with my MIUI battery calibration and charge cycles, Nightly 100 will be out, so I told myself I'll switch to it lol.
[Captivate Android Development] Lillian~:
Is there an issue with Skype (video) and CM7 that anyone is aware of?
[Captivate Android Development] sixstringsg:
Well unless you're super creative, no FFC to start out with....
[Captivate Android Development] Haloruler64:
Mirrors and some tape fix that.
[Captivate Android Development] halfsoul:
Only duct tape will work.
[Captivate Android Development] jweitzel24:
datadata folder is probably full to the brim... happens to me every couple months or so unless you stay on it. Moving certain larger apps to the SD card helps, but you're better off doing a full wipe and starting fresh and then moving larger apps to the SD card after the fact.
[Captivate Android Development] jweitzel24:
That last post was for this
[Captivate Android Development] Haloruler64:
Arguable for professionals like me, but generally true.
[Captivate Android Development] Optilicious:
I have been reading though the forum and haven't had any luck finding an answer to my problem. Though I'm still going through the 1048 pages on this forum... lol I was hopeing that someone could help me. I have flashed the latest build and now am unable to see my external SD card. I come from MIUI and if this happens on MIUI you can just create the external_SD card file and reboot to fix. I tried that and didn't work. If someone could help me or direct me to a place I can find the answer it would be much appreciated!
[Captivate Android Development] Johnston212:
Wanted to throw this out, but once again I am having Market FCs all over again. I tried the steps that I used before per another users suggestions. I have re-flashed gapps (latest seems to be out of date), updated to the posted market apk, cleared caches and apparently fixing permissions does not work. So apparently NOTHING is working.

Aside from doing yet another wipe (occurring a LOT lately), are there any other options that I haven't tried yet?
[Captivate Android Development] Bear451:
Had the same problem with the external sd when I can from miui.turns out I was just looking in the wrong place. External folder was still on mine but it was empty. The external sd card is emmc on your root folder.

Sent from my SGH-I897
[Captivate Android Development] nimper:
Clear the Market data in the app manager. It worked for me at least.
[Captivate Android Development] Johnston212:
Tried it, didn't work. I uninstalled updates and I can get in and even get updates going, thank god. Next update, I may just do a wipe along with it. I've just had to do more of those in the last 2 months than since I got on CM7 several months ago.
[Captivate Android Development] forlack:
I used CM7 when it first came out and liked the features, but moved on because of bugs and bad battery life.

Yesterday I loaded the latest Nightly and am loving it! The speed is remarkable and the battery life is equal to or better than Serendipity 7. Great work guys!
[Captivate Android Development] The_Zodiac:
so i just payed for rom manager premium and insalled it when i go to download rom no roms show up under the premium section...

it only shows fasty, miui, gaps and something else
[Captivate Android Development] Johnston212:
Did you setup the CWM part on the home screen?
[Captivate Android Development] The_Zodiac:
what do you man flash cwm recovery? i did that already
[Captivate Android Development] Johnston212:
Ok, so you clicked the Flash Clockwork Mod Recovery , selected Captivate (MTD) and followed the prompts from there?
[Captivate Android Development] mcord11758:
Ok in same screen after you hit option 2 I believe. The top option turns it off, bottom on.

If your signal is an h its on.
[Captivate Android Development] MisterAnthonyxD:
You clearly asked how to disable HSPA but anyway, it's a modem thing. Try flashing JL3 or JK4 and then enable HSPA.

Sent from my Captivate running CyanogenMod 7
[Captivate Android Development] QuarkGluonSoup:
I will try one of those modems. How can I tell whether it is enabled or not?
[Captivate Android Development] :
CM7 is sweeeet! Thanks! Rom Manager is telling me if i buy the full version i can get my cm7 updates.? Is that true/safe?
[Captivate Android Development] PuffinNugz:
It should be automatically enabled after flashing. It was for me with jk4.
[Captivate Android Development] MisterAnthonyxD:
The H symbol will replace your 3G symbol.

Sent from my Captivate running CyanogenMod 7
[Captivate Android Development] MisterAnthonyxD:
Highly doubt that.

Sent from my Captivate running CyanogenMod 7
[Captivate Android Development] QuarkGluonSoup:
Oh you mean, if HSPA is enabled, in the status bar instead of "3g" you will see an "H"? Why then do you need to dial *#301279#?
[Captivate Android Development] E_man5112:
Yeah. Could that be a problem? How else would I get my apps?
[Captivate Android Development] ankitb4u:
So I want to get away from adw launcher and use just the stock launcher. I don't want to download the fake Ginger bread launcher as well. Any way for the same.
[Captivate Android Development] demonte21:
I never seen that H Symbol yet. Using the JK4 modem.

I did a speedtest and it look like HSUPA working. ( i had 6 MBPS download and 3,2 Mbps upload),

I wonder if the 3g / H symbol toggle is bugged ?
[Captivate Android Development] QuarkGluonSoup:
How can you tell from a speed test if you have hspa enabled?
[Captivate Android Development] bay_wolf:
If you restore any system data then you'll most likely have messed stuff up. First try to see if it works without restoring. If that works then just try to restore only the apps + user data and not any of the System data.
[Captivate Android Development] PuffinNugz:
All these questions you have can be found by searching the forums. This is not a thread to answer every question you have about android. Many of your questions are not CM related.
[Captivate Android Development] The_Zodiac:
I know we likely won't gave acwm version soon/ever but how far off are we from a stable version at least?
[Captivate Android Development] mcx6:
I believe that I read earlier in this thread, that this may become an option with the captivate, after things are merged, but it is not an active option at this time.
[Captivate Android Development] techmik67:
umm, if you have High Speed Upload.......... (384 kb/sec is the bottom threshold)...

search is your friend

How can that possibly be known? When it's stable, it's stable and someone will announce it. Until then, it's WORSE than "are we there yet", because you can at least give an estimated answer to that. For CM7, all the problems could magically be fixed in 1 brainstorm weekend by these devs, or might NEVER get "stable".....
[Captivate Android Development] joeshmoe08:
In the op it states under daws that accurate batterymod does not work but that isn't true. I think You were just making a general statement for newcomers but you can always edit the xmls (which I have done and tested) to get the accurate bat mod without the settings.
[Captivate Android Development] Denoh:
RESOLVED. I went back to stock and reflashed the ROM. This time, I manually reinstalled missing Apps rather than use TiBu. Seems that when I used TiBu to reinstall Apps and Data, some Samsung System data was also installed, even though I was only reinstalling user date.
[Captivate Android Development] Dc5e:
I installed this Thursday and so far it has been running very well. I've only ran into one problem (found a fix on some other forums) and I am wondering if other people have ran into it as well.

The problem is, whenever i do "adb install your-apk-here.apk", I get:

/sbin/sh: pm: not found

The fix for this is to add #!/system/bin/sh to the first line in /system/bin/pm.

I just flashed the 0304 update today and this problem came back... so I'm wondering if this is a small bug in CM7 and other people have been running into it or it's just me.
[Captivate Android Development] xFangireKingx:
You need to go into rom manager settings and enable advanced mode, then the CM7 stuff will appear.
[Captivate Android Development] The_Zodiac:
accidentally hit galaxy s captivate instead of captivate mtd working now
[Captivate Android Development] Johnston212:
Good and since you now have the Premium version, you should also go into CM7 Settings and enable the notification so you know when the next nightly comes out.
[Captivate Android Development] The_Zodiac:
yeah i haven't actually run cm7 since it first was released for the captivate (back when you could install apps from the market lol)

do the nightly updates usually improve the rom a good amount?

and im guessing they are no wipe updates?
[Captivate Android Development] The_Zodiac:
another question where did my market go?
[Captivate Android Development] Johnston212:
Um, the nightlies do help. Though I've found the GPS has been worse on some of the more recent nightlies. Haven't tried it much in the 90s yet. And when you flashed CM7 last, did you make sure to flash Google Apps along with it?
[Captivate Android Development] littlewierdo:
Wondering whether nightlies help?

Have a look...

http://cm-nightlies.appspot.com/?device=captivatemtd

Good luck making heads or tails out of it however...

With regards to how phones are being tracked (with regards to tethering), there are a number of ways this can be done, usually it is done with a combination of methods.

But first, time to live is not one of the items being looked at. This is very easily changed and many devices have a TTL of either 64 or 128 (the max is 255). All this byte is/does is decrease by 1 for every 'hop' or router the packet goes thru on its way to the destination router. When/if this byte reaches 0, the packet is dropped (I cant remember if a message is sent back to the originating router or not). Many OS's have a standard TTL of 64 including Windows XP after service pack 2, the iphone, all blackberries, and older versions of Linux. This variable gives NO indication of where a packet originated from.

The user agent is likely not what is being inspected either, as an article from http://at-amp.articles.r-tt.com/ pretty clearly explains...

"In theory, they might be able to spy on the user agent specific data being transmitted to your computer and see that you were viewing non-mobile versions of websites. But the iPhone often views the full versions of websites, so this isn’t necessarily a flag..."

The rest of the paragraph goes on to explain that most of the data is encrypted between your cell phone and the server. This is unlikely. Most websites are not using SSL as a standard connection so the only likely encryption being used would be encryption placed by the carrier (since they are encrypting the data, they obviously can decrypt this data - not to mention, GSM has been cracked already by various hacker groups).

My guess is, cell carriers are looking at data consumption and packet inspection.

For example, AT&T does not have any devices that support Netflix (none that I know of) so if you are receiving Netflix packets, their might be a way to look at the way the packet is put together to determine that you are using Netflix and assume that you are using tethering since your phone "obviously" could not 'possibly' be running the Netflix app. Of course, AT&T would be wrong in this assumption.

And since it would be a complete pain for AT&T to monitor ALL packets, I think they are looking at top data consumers as the primary target. If you are tethering but only using 3-5 GB a month, they most likely aren't concerned. But if you are using 10+ GB (currently, the top 5% of data users use at or over around 12 GB), you are putting a spotlight on yourself.

Think of it like this. If you steal a penny off every $100.00, it is going to be less likely that anyone will see it as more than an accounting error. But if you steal a penny for every dollar, this will be much more suspicious.

So, my suggestion is, tether in emergencies / when you 'need' to but don't rely on it for your main internet needs.
[Captivate Android Development] ninjuh:
Has anyone else noticed cm7 #93 automatically starting a bunch of processes? I'm using advance task manager in market and after my phone being on idle for like 30 mins there's hella apps running and no I don't have auto updates or anything like that going. Could this be the battery drain bug?
[Captivate Android Development] nmoline:
I could use some help:

On every nightly build from 90-94 when I charge my phone at night it shuts off in the middle of the night and does not reboot. When I wake up the display shows a battery with a charge of 100%. I have to turn the phone back on each morning.

Is there an easy fix for this? Or do I need to restore to stock using Odin and then flas CM7 Nightly again?
[Captivate Android Development] littlewierdo:
Nightly 96

This one has a large list of fixes/additions/tweaks...

I installed it thru the GUI in Rom Manager (a bit lazy tonight) with the Google Apps and wipe Davlik cache options ticked (all other options unchecked).

Phone rebooted and installed and then rebooted into the Android OS.

I started playing with my tablet for a few minutes and glanced back over at my phone, there was a message with two boxes, before I could read what was in the boxes or what the message said (it was short), the phone rebooted automatically with no indication what the message was...

Any idea what the message was or could have been?

PS. I really dislike Cyanogen's auto proceeding with its installation process, when CM is done installing, I should have an option of pushing a button to reboot so that I can verify the installation went correctly. The same with this mysterious message I recd, since the phone rebooted, I have no idea what it was or did...