Recent content by xxn0sflam3zxx

+1 However, in my instance my phone was stolen. I had used Lookout to attempt to source it, but it was to no avail. I tested it again on my replacement device, and found that while I had Lookout whitelisted (as I had previously on the old device), it would only function/trigger the locate...

Love this ROM, fast as hell! It's too bad I keep getting SOD's. It appears that I've had this issue with all blasphemy kernels...

You're not going to please everyone. For myself and the few that seem to have this running without issue, I commend your work and encourage you to build upon it. I'd also encourage those others with varied results to follow in your footsteps by quoting your entry post, to hopefully achieve...

I'm surprised I even read that wall of text... But cheap vs. free is a typically a no-brainer. I sent my device in to Samsung and my out of pocket was $0. More so- I'd like to keep my existing warranty active by not ripping into it's insides. Albeit, I suppose that guide would work for anyone...

It's a hardware issue involving the LCD screen - the phone's radio interferes with the screen when it enters a low signal state and triggers the menu/search buttons. The only way to resolve the issue is to have the entire LCD screen replaced. Cliffs: You have a faulty LCD screen, and you're...

That's a hardware issue. There are a few references here and there if you search for "phantom presses", in regards to the menu and search buttons randomly firing. Sent from my SPH-D710 using xda premium

Haven't had this happen in a long time, but has anyone else experienced LOS running 1.3 ?

Icanhazmilestone1.3?

It's a hardware issue. The only fix is to replace the LCD. This happens across a HUGE range of Samsung phones, from what i've seen, the Nexus predominantly. Low signal Tx interferes with the screen and ends up firing the capacitive buttons due to the fault. I just received mine back from...

Sorry bro, didn't mean to be a buzzkill... I typically leave that for some other jerk :)

CM10 Beta 1 - Clean install. I initially just flashed A2, when that didn't work i figured A1 had necessary files that A2 would build on top of, but found out that it wasn't the case.

A2 doesn't seem to like my phone. Gets stuck at the boot screen. A1 will work perfectly, though. Any ideas?

Yes, on my head unit it will indicate that it's paired, however still has audio output through the phone. I typically disconnect and reconnect the phone's Bluetooth during playback of the audio. Once it re-connects, it comes through the car speakers as intended.

Running dd-wrt w/ no issues. Sent from my SPH-D710 using xda premium