[HTC Sensation] Skipjacks:
Re: [ROM][PRE-ALPHA] Jelly Bean 4.2.1 Pre-Alpha 1 [17.01.13]

Dude, there have been a thousand log cats of this exact problem (many of which were posted by me) for every ICS and jelly bean build for the sensation. Not one has ever shown anything more than a non descriptive message that data connects then disconnects. There have been countless discussions on this problem in numerous threads. Everything that there is to know about this problem is well documented. It doesn't show up in the logs because nothing is wrong with the ROM. Its doing exactly what its supposed to do which is disconnect data when the signal is lost. So to be fair the bug is really either on t mobiles end or on the device hardware level. And the 'fix' for it in the ROM is a patch that compensates for either crappy hardware or a crappy network (or a combination of both)

But the problem is not non existing just because you haven't experienced it. It existed on gingerbread stock sense the year the Sensation came out. HTC and t mobile did an outstanding job of patching the glitch without ever acknowledging its existence or telling anyone else how to fix it.

But when Aosp ICS and job came out without this proprietary patch...boom. Back to square one.

Now I will agree that there could be different hardware in different HTC phones that is causing this not to be a problem on all sensations. Its well documented that HTC often uses different parts to build the same phone. Just about all HTC phones are made with 2 different screens. The my touch 4g had 2 different emmc chips, one of which was faulty and prone to permanent failure during flashing. So yeah, I can believe its a hardware inconsistency. I've also been holding 2 sensations on my hands, both on the t mobile network, both running the same build of jelly bean. One had the problem. The other didn't. Normally I'd say my phone was broke, but since a thousand other people also get the problem randomly I know its a real thing and not just me with a crappy device.

Whatever the fix is, Bruce's builds already have it. I don't understand what he did to fix it. But I know its dramatically reduced on Bruce's builds since late October. (In fact I haven't gotten it once. And I've only seen a handful of people saying they still get it since then) I just tested it today and confirmed that I was getting the bug on Nike's ROM, so I installed an early cm10 from before the fix and still had the problem, installed aokp from before the fix and still had it, and then went to my nandroid of Bruce's cm10 from 3 days ago and it was gone. Went back to this ROM and it was back. So Bruce has it fixed. I just put it out there so Nike would know about it and could get the fix from Bruce. I'd share it, but I don't understand it enough to discuss what was patched.

But don't play that "I've never had the problem so it doesn't exist" nonsense. That's as annoying as someone posting about a bug without including a logcat:p

Nike, I'm happy to help diagnose and collect any information you think would be unhelpful to fix this. Just let me know what you need. I can tell you a log cat won't have the answer, and the easiest thing is probably an introduction to Bruce and I know he has already solved this.

---------- Post added at 01:59 PM ---------- Previous post was at 01:57 PM ----------

Google translate must do dialects now. Hahaha

At least I reckon that's the explanation :D (I live in a place where people actually use reckon on a daily basis. Its a great word!)