Develop Bugs

FF18 very .... uhh?

Am I the only one whom finds mostly all FF18 builds unresponsive at times? The touch keys don't work randomly... on the latest ota and the leak? Is this kernel related? I hope so.... I find myself constantly trying to find the right one buy no luck... this is perhaps a useless thread but I feel as if this ICS for phone is not even worth it at times
Sent from my SPH-D710 using Tapatalk 2

I get th. Touch key part as we.
Sent from my SPH-D710 using Tapatalk 2

Then use an aosp build
Sent from my SPH-D710 using xda app-developers app

cp320703 said:
Then use an aosp build
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Or this
http://forum.xda-developers.com/showthread.php?t=1748208
"PROJECT:PLACEBO" - now up to you
Sent from my SPH-D710 using xda premium

pyrostic said:
I get th. Touch key part as we.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Yeah that just makes using any ICS ROM a turn off at the moment... hope source can fix this.
Sent from my SPH-D710 using Tapatalk 2

cp320703 said:
Then use an aosp build
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I love AOSP, I'm just not going that route at the moment till kernel is tweaked and modified now that they have source. Plus not all of us like to run aosp.
Sent from my SPH-D710 using Tapatalk 2

Why is it that all of these types of things are always categorized as ICS issues when the majority of us dont suffer from often if at all...?
Just make a checklist of consistent variables....
You
Your phone
Your settings
An operaring system succesfully applied to most of the world made by top-notch developers then supplemented by equally great devs that just always happens to brake for you =p

PhAkEer said:
Why is it that all of these types of things are always categorized as ICS issues when the majority of us dont suffer from often if at all...?
Just make a checklist of consistent variables....
You
Your phone
Your settings
An operaring system succesfully applied to most of the world made by top-notch developers then supplemented by equally great devs that just always happens to brake for you =p
Click to expand...
Click to collapse
I've had this on both stock and AOSP. I know my way around rooms and completely wipe before every flash even. its been happening to me since the early FF** kernel based builds. Frankly I think Samsung could have worked longer on this but something tells me it was rushed at the end.
Sent from my SPH-D710 using Tapatalk 2

Was mostly just flippin $#!t
Ive just been lucky I guess.. Ive got a big lib folder I carry around with me...
Any little problem Ive gotten has been easily remedied, and Ive never once had the weird problems that some get no matter what.
Maybe because mine was assembled in the states? Idk...
I do know that Placebo, placebo you want.. Worst case the flash doesnt take and you have to flash a backuo...
Most likely youll say, "this is a stock kernel?!"
Lol
Sent from my SPH-D710 using xda premium

PhAkEer said:
Why is it that all of these types of things are always categorized as ICS issues when the majority of us dont suffer from often if at all...?
Just make a checklist of consistent variables....
You
Your phone
Your settings
An operaring system succesfully applied to most of the world made by top-notch developers then supplemented by equally great devs that just always happens to break for you =p
Click to expand...
Click to collapse
Fixed for ya.
Agree 100% though.

Sorry to say this but I'm running my super nova rom and haven't had any problems what so ever. Nothing looked what you're describing at all. Any chance the phone is having a hardware factory issue since so many others have experienced the same thing?

No its definitely an ICS issue on certain devices. As it doesn't happen on Gingerbread roms based at all. Ive noticed certain users complain about the issue, maybe its different hardware models? Ill wait a bit to see what the developers cook up.... I'll give your super Nova ROM a try.. once all that fails I'll go get a device exchange LOL
Sent from my SPH-D710 using Tapatalk 2

Febby said:
No its definitely an ICS issue on certain devices. As it doesn't happen on Gingerbread roms based at all. Ive noticed certain users complain about the issue, maybe its different hardware models? Ill wait a bit to see what the developers cook up.... I'll give your super Nova ROM a try.. once all that fails I'll go get a device exchange LOL
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Lmfao.
When it fails, ill buy your broken phone for like 20 bucks, you say you flushed it so insurance covers it... Ill flash that same rom on your phone and have no issues =) everybody wins!
Sent from my SPH-D710 using xda premium

PhAkEer said:
Lmfao.
When it fails, ill buy your broken phone for like 20 bucks, you say you flushed it so insurance covers it... Ill flash that same rom on your phone and have no issues =) everybody wins!
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Who said anything about insurance? I'm very good friends with the store manager. He always performs a device exchange as long as it hasnt had water damage. And no, I'm pretty sure the issues I'm having are real as pressing the power button and having the unlock screen process done but captive buttons not work for 5 seconds or more, isn't a bad flash. Even on shubs one click to FF18.
Btw check list done.... settings are always left stock. Phone seems okay unless I can surgicly open it to check on internals lol... ! Yes I'm okay myself.other than my messed up fist from a drunk fist fight.

I've had the same issue with most ICS E4GT roms, and doubt it is anything user related. Don't pay attention to the trolls. I've fully wiped my phone and it made no difference. Hopefully someone can figure it out. It's pretty annoying having to turn the screen on a off twice to get the capacitive buttons working.
Febby said:
Who said anything about insurance? I'm very good friends with the store manager. He always performs a device exchange as long as it hasnt had water damage. And no, I'm pretty issue the issues I'm having are real as pressing the power button and having the unlock screen process done but captive buttons not work for 5 seconds or more, isn't a bad flash. Even on shubs one click to FF18.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse

The only thing I notice is a bit of lag. I didn't have this issue before but it isn't so horrendous that I wanna destroy it. Ill be switching to a rom after I find one with absolutely no bugs. Oh an can I flash ICS to ICS now?
Sent from my SPH-D710 using Tapatalk 2

proxy0 said:
The only thing I notice is a bit of lag. I didn't have this issue before but it isn't so horrendous that I wanna destroy it. Ill be switching to a rom after I find one with absolutely no bugs. Oh an can I flash ICS to ICS now?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
No you still can't flash ics to ics the emmc bug is still present
Sent from my Epic Blazer ICS 3G Touch

riggs170 said:
No you still can't flash ics to ics the emmc bug is still present
Sent from my Epic Blazer ICS 3G Touch
Click to expand...
Click to collapse
You think they'll push an update to the phone to fix the issue?
Sent from my SPH-D710 using Tapatalk 2

phelixian said:
I've had the same issue with most ICS E4GT roms, and doubt it is anything user related. Don't pay attention to the trolls. I've fully wiped my phone and it made no difference. Hopefully someone can figure it out. It's pretty annoying having to turn the screen on a off twice to get the capacitive buttons working.
Click to expand...
Click to collapse
Thank you, glad I'm not the only one who has this issue. The screen on and off is so far the only solution to this so far...
proxy0 said:
Oh an can I flash ICS to ICS now?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
You can if you use the latest agat kernel built from source but remember not all developers have built in the new safe kernel! So you would always have to odin the kernel if it isnt baked with the ROM.
For reference, here is the link to source built kernel.
http://forum.xda-developers.com/showthread.php?t=1767421
riggs170 said:
No you still can't flash ics to ics the emmc bug is still present
Sent from my Epic Blazer ICS 3G Touch
Click to expand...
Click to collapse
That's been fixed now that we have source for ICS.
Sent from my SPH-D710 using Tapatalk 2

Ok heres my input. I believe that its a combination of software and hardware. Remember response time of soft buttons depends on how stable the rom is and also whats running at the time they where pressed. Ok say like you have a few apps it the background running and you turn off your screen. Once the screen come on the buttons may take a second to come on because the screen has more of a priorty than the soft button. Its all in how you look at it. And with apps running it slows that process down greatly because a combination of the proccesor and ram being used. Remember not notice but our soft buttons have a back light and they are press sensitive. So with them working together plus all the other stuff i explained timing would be off. But think about it. Lol is it really a depressing ordeal lol. I actually witness it and continue on without even thinking about it. Sorry for rambling lol

New OTA leak T999UVDLI8

Another OTA leak guys only this time we have to install new update coming from T999UVALI5
http://www.hotfile.com/dl/172486377/bfbcb29/SGH-T999_T999UVDLI8-OTA-T999UVALI5_TMB_339817771.zip.html

makavelicruz said:
Another OTA leak guys only this time we have to install new update coming from T999UVALI5
http://www.hotfile.com/dl/172486377/bfbcb29/SGH-T999_T999UVDLI8-OTA-T999UVALI5_TMB_339817771.zip.html
Click to expand...
Click to collapse
Hmm, damn. I just installed frosty JB rom...anyone know advantages/disadvantages between both?

liberalswine said:
Hmm, damn. I just installed frosty JB rom...anyone know advantages/disadvantages between both?
Click to expand...
Click to collapse
well Frosty JB rom, correct me if I'm wrong, it's more of a custom rom which has performance tweaks and whatnot. Is not really stock. Stock is just simply stock no tweaks of any kind.

Good news is as fast as these leaks are coming out means Samsung is working diligently to get the official JB released!

Can't wait that official is right around the corner!
sent from my apple smashing s3

Someone flash & report back!!! lol

Been running it since around midnight here, cst. Pretty stable so far. Camcorder audio still not fixed though.
Released modem a few hours ago in case u didn't see it!
Sent from my SGH-T999 using xda app-developers app

Good thing I didnt install 7 just yet.. hopefully this one will get rid of blue flicker... too bad audio isn't fixed...

I wonder if this means LI5 is a true OTA coming? Why wouldn't it update from LH2?

havent been keeping up with these lately i been to interested in the great news about the note 2 coming to tmo next month
But ill guess ill flash this later when a flashable pack drop.

18
immunityx said:
havent been keeping up with these lately i been to interested in the great news about the note 2 coming to tmo next month
But ill guess ill flash this later when a flashable pack drop.
Click to expand...
Click to collapse
i JUST FLASHED 17 LAST NIGHT...NOW i HAVE TO GO HOME AND FLASH THIS. ANYONE KNOW HOW TO FIX CRAPPY WIFI CALLING?

Is there a flash able zip yet?
Don't feel like going thru flashing lh2 to flash li5 to flash this..
Sent from my SGH-T999 using xda premium

-FuRBz- said:
Is there a flash able zip yet?
Don't feel like going thru flashing lh2 to flash li5 to flash this..
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
here is one by wildshld
http://sourceforge.net/projects/xquizit/files/latest/download

DocHoliday77 said:
Been running it since around midnight here, cst. Pretty stable so far. Camcorder audio still not fixed though.
Released modem a few hours ago in case u didn't see it!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Did you try it from a fresh install? I've noticed progressive differences with all these leaks and starting fresh vs not. (I'm just curious if it changes anything.)
Sent from my SGH-T999 using xda premium

On 7 google voice didnt work, does it on 8?

SebasC said:
Good thing I didnt install 7 just yet.. hopefully this one will get rid of blue flicker... too bad audio isn't fixed...
Click to expand...
Click to collapse
No flickering at all for me! :thumbup:
stevessvt said:
I wonder if this means LI5 is a true OTA coming? Why wouldn't it update from LH2?
Click to expand...
Click to collapse
Thats why there were ics leaks to begin with im sure. Li5 may or may not be the last but it definitely shows progress!
I have been assuming we'd get another official ics update for this reason! Since jb is being deployed as a patch, they both have to play well before, during and after update.
Sent from my SGH-T999 using xda app-developers app

Hey installed the leak and i used superswipe to do this and everything is fine but my notification bar is is shaded and notification NOT completely black. Is this part of the update or i screwd up the flash i am on xquisits l8 rom and before i was on frostys on l7. Thanks!!

hrahman315 said:
Hey installed the leak and i used superswipe to do this and everything is fine but my notification bar is is shaded and notification NOT completely black. Is this part of the update or i screwd up the flash i am on xquisits l8 rom and before i was on frostys on l7. Thanks!!
Click to expand...
Click to collapse
Yup they changed it a few leaks ago lol
Sent from my SGH-T999 using Tapatalk 2

Another leak once again!
There is another leak out T999UVDLI8, yes it is the same name as the last but instead of having to be on T999UVALI5 to update you have to be on T999UVALH2 in order to update. This one is 1.1MB larger than the last LI8.

^ yea i saw that too but didnt think much of it .. wonder if everything is the same as the li8 that was released yesterday

CM10 Developer help

Hello,
I have a big request to ask the developer for the Nightly Official CM10 builds.
I have been running them ever since i got my S3 with only a few known issues. I love love love these builds and greatly appreciate everything that they are doing for us.
I have one small favor to ask them to include in the next nightly or near future build.
Ever since build 9/18, i have been getting a hot reboot. I have narrowed it down to the app, smart status bar. This app has worked perfectly on every other ROM or nightly of CM10. So i KNOW its not the app.
I have a logcat here
and i personally feel its this change that is causing this.. i may be wrong but i dont know since nobody is giving me support or even caring.
On that note, i have mentioned this in the CyanogenMod 10 nightly thread. And all i got was a bunch of people *****ing me out claiming that im the only one who uses this app and experiences this issue. And that the problem lies in the app. But when nightlys are released arent they suppose to fix issues and not cause new ones? and if it were the app causing the problem then the app would have caused a hot reboot on my stock rom, on my galaxy s 2 cm10 nightly, on my HD2 cm9 nightly. And on EVERY other ROM out there. Well it doesnt nor has it caused issues up until the 19th build.
I apologize for any attitude or disgust in my dictation but i was very offended by the rudeness and ignorance of the remarks i was receiving. So i apologize for any hostility in my dictation.
Thank you for your time in reading my thread. I hope something gets done to resolve this issue.

Why not post in the cm10 thread?
Sent from my SGH-T999

lazarat said:
Why not post in the cm10 thread?
Sent from my SGH-T999
Click to expand...
Click to collapse
Lol i did -.- read my post.

I would say send the logcat to the app developer and they should fix compatibility. Link them to the github change as well. Supporting all possible users should be a priority.
Cyanogenmod adds changes that make the most benefit for over all performance. If this broke their code it would be resolved but this breaks the apps code so the dev needs to correct it.
I have sent info like this to devs before and been obliged and had the issue fixed.
Sent from my SGH-T999 using xda premium

imheroldman said:
I would say send the logcat to the app developer and they should fix compatibility. Link them to the github change as well. Supporting all possible users should be a priority.
Cyanogenmod adds changes that make the most benefit for over all performance. If this broke their code it would be resolved but this breaks the apps code so the dev needs to correct it.
I have sent info like this to devs before and been obliged and had the issue fixed.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I've tried that never got a reply from the developer. I just don't see how it works on every other ROM but the 9/18 and up ROMs. So it can't be a app problem
Sent from my SGH-T999 using Tapatalk 2

elesbb said:
I've tried that never got a reply from the developer. I just don't see how it works on every other ROM but the 9/18 and up ROMs. So it can't be a app problem
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
If it isn't working with an AOSP based rom, it is an app problem. Apps are supposed to be built with AOSP in mind..

joshnichols189 said:
If it isn't working with an AOSP based rom, it is an app problem. Apps are supposed to be built with AOSP in mind..
Click to expand...
Click to collapse
Yes i know. But it WAS working before the 9/18 update.. thats why i dont think its an app issue. Now Camera ICS has never worked on CM10 for my S3, it doesnt cause a hot reboot it just freezes then force closes. Thats an app related issue. But smart status bar causes a hot reboot and if you look at the logcat you can notice something is not right with the overlay. Everything runs perfectly on 9/15 build. Smart status bar works and desnt cause a hot reboot. so how could it be the app when it was working before? I just dont understand that part.

elesbb said:
Yes i know. But it WAS working before the 9/18 update.. thats why i dont think its an app issue. Now Camera ICS has never worked on CM10 for my S3, it doesnt cause a hot reboot it just freezes then force closes. Thats an app related issue. But smart status bar causes a hot reboot and if you look at the logcat you can notice something is not right with the overlay. Everything runs perfectly on 9/15 build. Smart status bar works and desnt cause a hot reboot. so how could it be the app when it was working before? I just dont understand that part.
Click to expand...
Click to collapse
The next logical step would be to see if it works on stock 4.1 on a Galaxy Nexus. That was you can see if it was something added that is different than stock Jellybean.
Sent from my SGH-T999

joshnichols189 said:
The next logical step would be to see if it works on stock 4.1 on a Galaxy Nexus. That was you can see if it was something added that is different than stock Jellybean.
Sent from my SGH-T999
Click to expand...
Click to collapse
Thank you... just one problem... don't have a nexus :\ maybe I'll post in the forum over there to see if someone can test it. Thank you for your help!
Sent from my SGH-T999 using Tapatalk 2

elesbb said:
Thank you... just one problem... don't have a nexus :\ maybe I'll post in the forum over there to see if someone can test it. Thank you for your help!
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Yeah that might be your best bet. I was thinking since CM10 is attempting to put stock 4.1 on our phones, you can isolate it to see if it is in fact something extra that CM added or if it is something that would be an issue on stock 4.1 as well.
Sent from my SGH-T999

joshnichols189 said:
Yeah that might be your best bet. I was thinking since CM10 is attempting to put stock 4.1 on our phones, you can isolate it to see if it is in fact something extra that CM added or if it is something that would be an issue on stock 4.1 as well.
Sent from my SGH-T999
Click to expand...
Click to collapse
So i posted this thread over in the nexus forums and someone confirmed it working perfectly on AOKP JB. Dont think its stock but its progress

elesbb said:
So i posted this thread over in the nexus forums and someone confirmed it working perfectly on AOKP JB. Dont think its stock but its progress
Click to expand...
Click to collapse
Very true. Someone will respond eventually I hope. Good luck sir!
Sent from my SGH-T999

joshnichols189 said:
Very true. Someone will respond eventually I hope. Good luck sir!
Sent from my SGH-T999
Click to expand...
Click to collapse
I seriously hope it gets fixed! I love this app
thanks for all your help as well!
Sent from my SGH-T999 using Tapatalk 2

CM10.1 issues?

CM 10.1 has been a not so good experience for me. I solely bought the S3 to root and install CM on it. But bug after bug and gallery not syncing ....its hard to keep it. The TW ROMs eat battery up quicker than anything. What is weird to me though is that I had the S3 on Sprint with CM and all was working even on nightlies. You would think that the T-Mobile version would be as good.NOPE
Sent from my SGH-T999 using Tapatalk 2

So, what's the question?

Have you ever thought that you might be at fault and not installing correctly? Instead of pretty much blaming and insulting the devs?
Sent from my SGH-T999 using xda premium

Aerowinder said:
So, what's the question?
Click to expand...
Click to collapse
My question is or would be does anyone have these issues as well or has anyone figured out a solution to the gallery sync ing
Sent from my SGH-T999 using Tapatalk 2

Ksunnyv1011 said:
Have you ever thought that you might be at fault and not installing correctly? Instead of pretty much blaming and insulting the devs?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Smh.... I have been rooting for years and this is not my first time on this forum so I'm not going to play that card and go down that route with you.
Sent from my SGH-T999 using Tapatalk 2

Jess813 said:
Smh.... I have been rooting for years and this is not my first time on this forum so I'm not going to play that card and go down that route with you.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Sorry dude. Some people tend to give smart answers and make it out to be like you're stupid or purposely disrespecting the devs when those were not your original intentions. You were just looking to get a straight out simple answer.. Everyone's got their reasons for what is said or done though so I can understand both sides but still, a simple answer is a SIMPLE answer.
Sent from my SGH-T999 using xda premium

Jess813 said:
My question is or would be does anyone have these issues as well or has anyone figured out a solution to the gallery sync ing
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
The only issue you name is the gallery sync issue. Is that the Picasa thing? That's never worked on CM 10. Probably still in the OP.
What other issues are your having?

Aerowinder said:
The only issue you name is the gallery sync issue. Is that the Picasa thing? That's never worked on CM 10. Probably still in the OP.
What other issues are your having?
Click to expand...
Click to collapse
Do you mean that it's never worked on the Galaxy S 3 for T Mobile or cm.? Because it has, I've had it on other devices and it runs pretty darn good. besides the gallery issue I have random freezes that to the point I have to reboot my phone or take out the battery
Sent from my SGH-T999 using Tapatalk 2

Use one that isn't a nightly and all US s3 variants will have the same issues except connection/data type issues. I have suggested for you to look up a picasa sync app from the market before, did you not do that? I'm almost positive it never worked for any device, without a mod.

Ok, freezing issues. What nightly are you running?

I was on the 27th but now I'm on stable release to and it still doing it
Sent from my SGH-T999 using Tapatalk 2

Don't use a custom kernel, don't overclock, and don't undervolt. And don't use that ancient CM 10.0 stable build. Use 10.1 with the 20130301 gapps.
The 3.4 kernel builds are still pretty buggy. 3/17 was the last 3.0 kernel build. Try 3/17 (goo.im). If still having issues, please describe exactly what you are doing when the freezes occur.
Using 3/28, I had one hotboot this morning, been fine ever since.

Is hotspot tethering with password supported in the nightlies? I am currently on CM10 stable now. Couple of months ago the nightlies hotspot password was not working.

net.lander said:
Is hotspot tethering with password supported in the nightlies? I am currently on CM10 stable now. Couple of months ago the nightlies hotspot password was not working.
Click to expand...
Click to collapse
It was fixed
T-Mobile SGS III

danke...thanks to all developers from bottom of my heart
Now to find linky for internal external memory swap for CM10.x. I couldn't find it after days googling...maybe I should find better keyword.

Phantom touches. Never had them before

My 16GB flo was working fine from the beginning. Always kept it up to date with android releases. Never had an issue. Just today while swyping noticed some weird behavior.So, I tested with a multi touch tester. There were some fake touches recorded. It didn't even allow me to reboot. Later with some effort I managed though. After reboot, it works fine. I'm scared cause I bought that in US and I doubt the so called international warranty will be honored in India.Has this occurred to anyone else? What shall I do if it happens again? Is there some fix for this?

littleromeo said:
My 16GB flo was working fine from the beginning. Always kept it up to date with android releases. Never had an issue. Just today while swyping noticed some weird behavior.So, I tested with a multi touch tester. There were some fake touches recorded. It didn't even allow me to reboot. Later with some effort I managed though. After reboot, it works fine. I'm scared cause I bought that in US and I doubt the so called international warranty will be honored in India.Has this occurred to anyone else? What shall I do if it happens again? Is there some fix for this?
Click to expand...
Click to collapse
I had the same experience the other day. Currently running
Latest version of Clean Rom with ElementalX kernel. After I was finally able to reboot, all was well.
Sent from my Nexus 7 using Tapatalk

dantegl36 said:
I had the same experience the other day. Currently running
Latest version of Clean Rom with ElementalX kernel. After I was finally able to reboot, all was well.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm running stock+xposed.
Testing with multi touch app seemed to have made it worse for me, even prevented me shutting it down. Hope it doesn't come back.

littleromeo said:
My 16GB flo was working fine from the beginning. Always kept it up to date with android releases. Never had an issue. Just today while swyping noticed some weird behavior.So, I tested with a multi touch tester. There were some fake touches recorded. It didn't even allow me to reboot. Later with some effort I managed though. After reboot, it works fine. I'm scared cause I bought that in US and I doubt the so called international warranty will be honored in India.Has this occurred to anyone else? What shall I do if it happens again? Is there some fix for this?
Click to expand...
Click to collapse
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app

Abel669 said:
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If an RMA is not an option, try Abel's solution. It boils down to bad hardware and no quality control. I had to RMA my first one for the exact same reason. Second one is fine.
If you do some googling, you will see that thousands of people have had this problem. Any definitive word from Google or Asus? You wish. They will never admit they made a mistake.
littleromeo said:
I'm running stock+xposed.
Testing with multi touch app seemed to have made it worse for me, even prevented me shutting it down. Hope it doesn't come back.
Click to expand...
Click to collapse

Abel669 said:
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, will do if it starts again.
Abel669 said:
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Aerowinder said:
If an RMA is not an option, try Abel's solution. It boils down to bad hardware and no quality control. I had to RMA my first one for the exact same reason. Second one is fine.
If you do some googling, you will see that thousands of people have had this problem. Any definitive word from Google or Asus? You wish. They will never admit they made a mistake.
Click to expand...
Click to collapse
Yes I read about them but this is weird cause a reboot solved the problem.

Had this issue start yesterday. Running Sinless 3.2.2 on stock kernel. I've noticed it only start since installing Xposed but that could be coincidence. Reboot fixed it but woke up to it again today...
Sent from my Nexus 7 using xda app-developers app

mister2quick said:
Had this issue start yesterday. Running Sinless 3.2.2 on stock kernel. I've noticed it only start since installing Xposed but that could be coincidence. Reboot fixed it but woke up to it again today...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The one I had (before I sent it back to Google), would only do it after it had been started for a while. Reboot would make it go away for a while, but it always came back.
Not related to Xposed.