[Galaxy Tab Q&A, Help & Troubleshooting] Suleeto:
Um I only mentioned that out of rhetoric, I am not questioning what I can do to resolve the tablet connection process AT MY HOME, I'm questioning the logic of defining the router as a "problem", which the other gentleman (darkmatter) is discussing with me. Or did you miss the point I was actually making? Jeez :P

I am not really concerned with "great code" vs. "poor code" here, I'm concerned with consumer use. I am more and more convinced this was a decision of the ROM chef and less that it's "Gingerbread" design. I can't imagine Google taking a risk of alienating even a small percentage of consumers who find themselves trying to connect to routers with default infinite leases. You claim that most new routers don't even allow that. This would mean that "infinite lease" is a legacy configuration, but again, every other device seems to have no trouble with that, because companies making these devices and their ROMs understand that the average consumer DOES NOT always know how (or have the option to) go in and change the config of a given router.

And btw... using the term "code" to criticize router design is a bit sloppy. How cleanly it's "coded" isn't at all what you're describing. It's "design philosophy" that is at work here. Not "code". Sometimes amateur programmers haven't spent enough time in the corporate development world and do not understand that the deciding factor in features and function is the COMSUMER end. Code is the guts, not the result. The result is designed based on need.

Also, you have some devices (recent ones, like my HP wireless printer for instance) that do not have an easy way to be assigned a fixed IP, and do not like frequent DHCP reassignment because the driver end on the client PC retains the IP as the pointer for the print queue. An infinite lease allows the initial assignment process to happen, and allows the client PC driver assigned IP to keep consistent with the IP assignment of the printer. This is not the only device that has this issue, but it is an increasingly common problem among a few wireless printer manufacturers in the way they set up client software connections to wireless printers.

So are you saying I should change my router config and cause printing problems in order to satisfy my apparently gutted, less-than-full featured network functionality of my custom flashed Android device?

Does that sound reasonable? Does that even address the concern that I have no control over public and other private wireless networks that I might try to connect to (and have infinite lease enabled)?

Tell you what: I will be going to not one, but three different wireless networks today. One at my local college, one at Starbucks, and believe it or not, the Denny's down the street has a brand new wifi setup installed (only about six months old). I will tell you what happens.

Even still, if I have this situation at home, then inevitably it exists elsewhere. And I would wager it's not a 1% experience, either.

I'm all for streamlining custom ROM's and trimming the fat, but not at the expense of such particularly important functionality. You call it "fringe", but from a product development point of view, we would consider it "comprehensive".

I like my "comprehensive" term a lot better than your "fringe" one. Maybe dropping this kind of functionality will happen eventually in devices, but I feel that doing so now is premature.

And I'm hoping that the chef reads this and at least offers the code in a subsequent version.

---------- Post added at 10:06 AM ---------- Previous post was at 09:50 AM ----------

From the Overcome 4.1.0 thread:

So Google may have indeed been the one to F' things up... Still, my sentiments stay the same, and it means that I might be switching to Overcome 4.0 until the situation is resolved. At least if this is the case, it's not the Chef's fault.