Develop Bugs

E4GT CM9 questions...

Im just wondering.... is there going to be another cm9 release or is the alpha 6 version the last one? I've noticed that cm10 is getting updated, so have they moved on? I also tried checking the cm website and can't find the E4GT section. Ive been holding out on rooting and setting up cm9 for something past alpha stage but im getting tempted too much to load alpha 6 version.
Sent from my SPH-D710 using xda app-developers app

whitelight said:
Im just wondering.... is there going to be another cm9 release or is the alpha 6 version the last one? I've noticed that cm10 is getting updated, so have they moved on? I also tried checking the cm website and can't find the E4GT section. Ive been holding out on rooting and setting up cm9 for something past alpha stage but im getting tempted too much to load alpha 6 version.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
There have been many nightlies that blow alpha 6 away. Go to the CM9 thread in the original development section for details...
Edit. It is very stable now and well worth a daily driver. Hope this helps!
Sent from my SPH-D710 using Tapatalk 2

I'd say its past alpha status. Pretty much an RC release, just haven't been officially merged into CM yet which chris41g has been working on. Like the guy above me said, very stable and a good DD.
Sent from my Nexus 7 using Tapatalk 2

Thats music to my ears. Im going to look for it. Is it still using the, i believe, modified gb kernel or is it using a ics kernel? Being in stock ics (ff18), would it be a problem?
Sent from my SPH-D710 using xda app-developers app

whitelight said:
Thats music to my ears. Im going to look for it. Is it still using the, i believe, modified gb kernel or is it using a ics kernel? Being in stock ics (ff18), would it be a problem?
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
CM9 never used a modified gingerbread kernel, we were flashing it with a gingerbread cwm repack to avoid the eMMC super brick bug.
Nightly 7-31 (which had no data due to a RIL change) was the last FF18 based kernel, initramfs was repacked with the startup scripts for AOSP etc. 7-17 Nightly was my favorite out of those.
Chris41G has had some source kernels out for awhile and starting with the 8/02 nightly they have been included. Early ones and the RC13 and older kernels had some problems with 4G and thanks to a ton of time Chris put into it the current ones shouldnt. Im runnin Chris's builds rather than the nightlies though.

So now there is no worries in the "super brick" thing?
Sent from my SPH-D710 using xda app-developers app

whitelight said:
So now there is no worries in the "super brick" thing?
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The brick is triggered by a function being called with a particular switch but it only happens when the kernel or program has been compiled against a particular library. Thats a basic and slightly outdated view on the problem more info can be found here - http://forum.xda-developers.com/showthread.php?t=1644364
The Galaxy Note actually shipped with ICS and no work around and factory resetting was like playing russian roulette with the phone. The International is supposidly safe but based on the kernel source for FF18, our phone does not have a work around in place on FF18. The bug itself will never be fixed on our end. It requires flashing the eMMC firmware which can generally only be done by an eMMC partner.
Basically any time a partition is formatted without work arounds in place a bug in the eMMC controller could randomly corrupt storage at a very low level. These formats occur during Factory resets and when flashing a rom, etc.
Safe recoveries are worked around so that factory resetting and wiping partitions is safe. The danger still lies in scripts making the call, that as well has been worked around either blocking a certain call or replacing it. The final danger is zips, usually for roms with an unsafe Updater Binary. CM9 Alpha 5 for example does not have a safe updater binary, from what I know the stock roms don't either. There are recoveries setup to swap this element out to make flashing safe altogether. Can't tell you how common that is at this point I do not keep up.
Source kernels have more safeguards than just recovery repacked, but something is better than nothing as well.

RainMotorsports said:
The brick is triggered by a function being called with a particular switch but it only happens when the kernel or program has been compiled against a particular library. Thats a basic and slightly outdated view on the problem more info can be found here - http://forum.xda-developers.com/showthread.php?t=1644364
The Galaxy Note actually shipped with ICS and no work around and factory resetting was like playing russian roulette with the phone. The International is supposidly safe but based on the kernel source for FF18, our phone does not have a work around in place on FF18. The bug itself will never be fixed on our end. It requires flashing the eMMC firmware which can generally only be done by an eMMC partner.
Basically any time a partition is formatted without work arounds in place a bug in the eMMC controller could randomly corrupt storage at a very low level. These formats occur during Factory resets and when flashing a rom, etc.
Safe recoveries are worked around so that factory resetting and wiping partitions is safe. The danger still lies in scripts making the call, that as well has been worked around either blocking a certain call or replacing it. The final danger is zips, usually for roms with an unsafe Updater Binary. CM9 Alpha 5 for example does not have a safe updater binary, from what I know the stock roms don't either. There are recoveries setup to swap this element out to make flashing safe altogether. Can't tell you how common that is at this point I do not keep up.
Source kernels have more safeguards than just recovery repacked, but something is better than nothing as well.
Click to expand...
Click to collapse
Excellently said. Perfect!

Could you link my to Chris's latest/ most stable builds/kernels? Thanks
Sent from my SPH-D710 using Tapatalk 2

timmetal6669 said:
Excellently said. Perfect!
Click to expand...
Click to collapse
Thanks. I am sure anyone on my level with working memory and who has kept up can explain it a little better. Its been awhile for me. I know the mmc cap erase switch on the format call was the suspected culprit but in the end that didnt seem to matter it was then being looked at that the Android 4.0 kernel was compiled against a library for makeext4fs or something.

fabolousrmx said:
Could you link my to Chris's latest/ most stable builds/kernels? Thanks
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
I also tried searching for his rom builds but i get other things. I googled but the closes i got to was a kernel and not sure if it was for E4GT.
Sent from my SPH-D710 using xda app-developers app

whitelight said:
I also tried searching for his rom builds but i get other things. I googled but the closes i got to was a kernel and not sure if it was for E4GT.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
www.chris41g.devphone.org
Sent from my SPH-D710 using Tapatalk 2

Simple port request

Ok guys, before I get flamed for not doing it myself I gotta say that my build system is down ATM. This is a simple thing to do, I just don't have the resources to do it. If anyone would be willing to port this for Toro, that would be AWESOME. It's a new recovery.
http://forum.xda-developers.com/showthread.php?t=2201860
Like I said, I would do it if my computer wasn't down right now. Thanks for anyone willing to do this.
Sent from my Galaxy Nexus using Tapatalk 4 Beta

Why isn't anybody interested? :/
Sent from my Galaxy Nexus using Tapatalk 4 Beta

yepitsme19 said:
Why isn't anybody interested? :/
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well where to start?
Its just another recovery since the unique features of it will not be open sourced by the dev.
What features of it intrigue you the most? I mean I spend all of ten minutes a week in recovery. I have no need for anything else in recovery other than what I currently have.
Sent from my Galaxy Nexus

Pirateghost said:
Well where to start?
Its just another recovery since the unique features of it will not be open sourced by the dev.
What features of it intrigue you the most? I mean I spend all of ten minutes a week in recovery. I have no need for anything else in recovery other than what I currently have.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
For me, CWM is ok, but it lacks the spice of TWRP. On the other hand, TWRP is like a cheap ass Android phone. It works, but completely ruins the experience. This is like CWM on steroids. If you read the OP it says 99% of it is open, just not the touch code like CWM. I feel that this is what I have personally been missing in a recovery.
Sent from my Galaxy Nexus using Tapatalk 4 Beta

yepitsme19 said:
For me, CWM is ok, but it lacks the spice of TWRP. On the other hand, TWRP is like a cheap ass Android phone. It works, but completely ruins the experience. This is like CWM on steroids. If you read the OP it says 99% of it is open, just not the touch code like CWM. I feel that this is what I have personally been missing in a recovery.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
I don't quite understand what the "spice of TWRP" and the "experience" of Android in a recovery are. To me, the two recoveries do the same thing; the only reason I use TWRP is that it is touch, and I have had bad experiences with broken buttons from overuse. So I need to agree with pirateghost; I don't see the appeal.

Pirateghost said:
Well where to start?
Its just another recovery since the unique features of it will not be open sourced by the dev.
What features of it intrigue you the most? I mean I spend all of ten minutes a week in recovery. I have no need for anything else in recovery other than what I currently have.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
All features are open sourced except touch recovery.
Sent from my Galaxy Nexus using xda app-developers app

Grarak said:
All features are open sourced except touch recovery.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Missing Features from github source:
- all gui options, include touch code
- name the backup folder with current ROM name
- custom zip install menu (Free Browse Mode + custom startup folder)
- Create Update.zip from current ROM or from pre-existing backups
- misc nandroid settings menu (but /preload is included by default and I added option to toggle compression under backup format menu)
Please, do not ask for touch source, I will never share it, release it public or make it commercial...
Sent from my Galaxy Nexus

Pirateghost said:
Missing Features from github source:
- all gui options, include touch code
- name the backup folder with current ROM name
- custom zip install menu (Free Browse Mode + custom startup folder)
- Create Update.zip from current ROM or from pre-existing backups
- misc nandroid settings menu (but /preload is included by default and I added option to toggle compression under backup format menu)
Please, do not ask for touch source, I will never share it, release it public or make it commercial...
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I see. Didn't read that.

bananagranola said:
I don't quite understand what the "spice of TWRP" and the "experience" of Android in a recovery are. To me, the two recoveries do the same thing; the only reason I use TWRP is that it is touch, and I have had bad experiences with broken buttons from overuse. So I need to agree with pirateghost; I don't see the appeal.
Click to expand...
Click to collapse
You do know there's a CWM with touch right ? ;]

madd0g said:
You do know there's a CWM with touch right ? ;]
Click to expand...
Click to collapse
Yeah I do, but I never got around to trying it since TWRP works anyway. Like I said, my recovery doesn't really matter to me as long as it works. Does it have any special advantages?

Got my build system up and running finally. Working on syncing some source now then I'll get this going probably tomorrow or so. If anyone is interested just let me know and I'll get it posted in the dev section
Sent from my Galaxy Nexus using Tapatalk 4 Beta

bananagranola said:
Yeah I do, but I never got around to trying it since TWRP works anyway. Like I said, my recovery doesn't really matter to me as long as it works. Does it have any special advantages?
Click to expand...
Click to collapse
Compared to non touch ? Not really, I've started using it because I wanted to save the button wear, but since 4.1.2 I'm not seeing the recovery much anyway (using stock Google image). I tried TWRP, but went back quickly, since I was more familiar with CWM and didn't want to waste time relearning/trying something that I wasn't aware of how it all works when needed.
As for regarding recovery "features" some would probably want working radio in it and use it as a phone ...

Any word on this?
Sent from my Galaxy Nexus using Tapatalk 4 Beta

MisterSprinkles said:
Any word on this?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Any word on what? At this time the only useful aspect of this is the standard recovery features we already have with 2 other recoveries. Since he won't open source the only bits that make it unique it seems like a waste of time.
Sent from my Galaxy Nexus

Pirateghost said:
Any word on what? At this time the only useful aspect of this is the standard recovery features we already have with 2 other recoveries. Since he won't open source the only bits that make it unique it seems like a waste of time.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I think he means from OP:
yepitsme19 said:
Got my build system up and running finally. Working on syncing some source now then I'll get this going probably tomorrow or so. If anyone is interested just let me know and I'll get it posted in the dev section
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse

Looks like Phil just posted it in the Toro section! http://forum.xda-developers.com/showthread.php?t=2281571

TWRP to me is pretty horrible. CWM is simple and it works. Ive used it from the start and never had any problems. also the latest version of CWM supports Toro (obviously) and is also touch. Not sure why the OP wants this one to be honest.

[Q] Which recovery is the best?

I recently used rumrunner to gain s-off and root and I flashed CWM recovery. I have read different posts stating CWM is flaky on the One, and I've also read posts saying TWRP is flaky. Can anyone clear this up?

I've used TWRP on almost every device I've had and have never had an issue with it. I'm currently using TWRP with no issues.
Sent from my HTC One using xda app-developers app

I used TWRP and had no problems. I'm a noob at all this and I couldn't have asked for it to have been easier.
Sent from my One using xda app-developers app

irie27 said:
I recently used rumrunner to gain s-off and root and I flashed CWM recovery. I have read different posts stating CWM is flaky on the One, and I've also read posts saying TWRP is flaky. Can anyone clear this up?
Click to expand...
Click to collapse
Cwm is flaky period not just on the one. Twrp has been the only real choice for years.
Sent from my HTC6500LVW using xda app-developers app

I have had nothing but good luck with CWM myself.
Sent from my HTC6500LVW using XDA Premium 4 mobile app

TWRP and Story time
I'm currently using TWRP with no issues, and never had any, starting way back on the OG Evo.
I do remember installing clockwork on the old school T-Mobile G1 (Dream) and I didn't have any issues. Koush spearheaded the recovery project for us, he will always have that title of being the 'first' with his clockworkmod's. (a tip of the hat to Koush)
Reminds me a little of this story I learned a while back. I heard it was true too...
The importance of a beginning in anything isn't always about that first product or creation in the project. The importance is whether the original design and goal is met at the end and/or in the end product. I.E. Adam.
He was the first to be created of humanity but the original purpose for his creation did not meet all of the requirements of his Creator. Instead of scrapping the original product and starting anew, there was a plan to restore and rectify on the original project, or as i like to call it, the original "storyline".
The similarity of this story to the OP takes a turn here. Where as Koush didn't fully rectify his original product (Clockworkmod) and make a better one, the Creator of humanity did indeed follow up on His promise to begin in the restoration of the original design of His story: the "Second Adam".
One was born from the dust of the earth (ie 'first' Adam; the other birthed from the Spirit of God in Heaven ('Second' Adam).
The first Adam was born perfect but ultimately failed in its original design and purpose. But alas, One had come, the Second Adam, who did not fall or fail, but came, conquered ,and was victorious in all that man was suppose to represent and so so much more...

I use cwm just because I like it better, I've had no issues so far with it. Once 4ext is available I'll be using that, best I've used to date.
Sent from my HTC6500LVW using XDA Premium 4 mobile app

Truthfully I was CWM all day every phone no matter what.
I wouldn't even give TWRP a chance, once I did though, I never looked back, haven't been back on CWM since either.
I do have a gripe with a menu set up. Nothing major and enough for me to change. I highly suggest TWRP.

I like TWRP more. Better UI, navigation and features. That said, I use CWM. After experiencing bugs and instability with TWRP on the S4, I returned to the recovery that has never failed me, CWM.
Sent from my HTC6500LVW using Tapatalk now Free

I use TWRP and have no complaints. Never did with CWM either. The winner for me is TWRP though, because I like being able to add multiple zip files to flash at once instead of flashing them one at-a-time with CWM, not a big deal but saves some time.

I would love to see 4ext make a comeback. Best recovery ever.
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button

tylerlawhon said:
I would love to see 4ext make a comeback. Best recovery ever.
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button
Click to expand...
Click to collapse
I just actually received an email from max about 4ext for the One. In short - the framework of his recovery needs an overhall to work with the larger resolutions, multi-cores, etc. He has a lot of work ahead of him so if he does try to revamp it for the One it will be some time. But I would switch from TWRP to 4ext in a heartbeat...handsdown the best.

brymaster5000 said:
I just actually received an email from max about 4ext for the One. In short - the framework of his recovery needs an overhall to work with the larger resolutions, multi-cores, etc. He has a lot of work ahead of him so if he does try to revamp it for the One it will be some time. But I would switch from TWRP to 4ext in a heartbeat...handsdown the best.
Click to expand...
Click to collapse
Same here. I love twrp, but pales so hard in comparison with 4ext
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button

tylerlawhon said:
Same here. I love twrp, but pales so hard in comparison with 4ext
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button
Click to expand...
Click to collapse
+1.
I actually forgot all about this recovery.
The best.

Anyone who uses CWM is a commie... Lol

cstrife999 said:
Anyone who uses CWM is a commie... Lol
Click to expand...
Click to collapse
I use CWM

Flyhalf205 said:
I use CWM
Click to expand...
Click to collapse
Almost anyone in that case lol

I used cwm with the original droid and it worked fine but when newer phones came out I noticed issues like on my dinc and bolt I had backups that was corrupted and I wasn't happy and moved to twrp and never had an issue since. I did move to 4ext with the bolt and that must say was the best over all. I miss 4ext when I got rid of the bolt but hope it comes to the one soon. It was so user friendly.

I've used CWM on my HP tablet, installed on a few other phones. Honestly, I've never given TWRP a chance. Is there anything I'm missing by not using it. I guess I'm just more used to the look and feel of CWM
Sent from my HTC6500LVW using XDA Premium 4 mobile app

Sprint LG G2 no love?

So Ive never had a device (even on sprint) that has no development to be seen within a weeks period of time. I believe the Root we have is from other devices and the CM 10.2 build that was posted was something that was supposed have never seen the light of day and was broken. I totally love this phone but I was really excited for the development aspects since its basically nexus 5 with a different shell. Anyone else with the sprint variant a little worried by the lack of interest?

I'm on the same boat, many probably are.
This phone is still solid stock.. all I really need is tethering... patiently waiting
Sent from my LG-LS980 using xda app-developers app

Those other carrier variants have been out way longer than ours. We've only had ours for 1 week now. Give it a bit more time?

HaiKaiDo said:
So Ive never had a device (even on sprint) that has no development to be seen within a weeks period of time. I believe the Root we have is from other devices and the CM 10.2 build that was posted was something that was supposed have never seen the light of day and was broken. I totally love this phone but I was really excited for the development aspects since its basically nexus 5 with a different shell. Anyone else with the sprint variant a little worried by the lack of interest?
Click to expand...
Click to collapse
Development is under way. There are 2 devs working on a CM 10.2 ROM right now and another working on a version of CleanROM for us. Its going to take some time and the phone hasn't been out for a week yet.
Also the CM 10.2 ROM was removed because the build was not tested and verified by the dev to be working and they removed the links to it in case it caused a potential brick to the phone. People who downloaded the ROM say it had GPS lock and rotation issues so you don't want to download the ROM anyways. In fact they saved you the hassle of reverting back to stock or a nandroid backup. Read the last few posts in that CM 10.2 thread to get a sense of the situation.
I am not worried at all about the "lack of interest" in this phone. You have to remember that not all the potential devs have received the phone yet such as garwynn who probably just received the phone today. Lets give the potential devs some time to come out with new ROMs and other mods. There are enough ways currently to mod the current stock ROM anyways through Xposed and other mods like (increase volume).

Its only been a week. Our device was rootable even before Sprint released it. I'm not worried. For now I've been using Greenify + Titanium Backup to keep my phone in battery/performance BEAST MODE.
Sent from my LG-LS980 using xda app-developers app

Install G2 xposed and you'll see you can do a lot of the customization yourself. There's also an xposed kitkat theme in the theme's section by ock. The device is already fast and ignoring aosp roms, you can customize the stock rom to your liking.

I ain't skeeerid
Sent from my LG-LS980 using XDA Premium 4 mobile app

I guess I didn't think about the fact that the other variants had been out for a few months already, but I really wasn't trying to comparing them. I was just noticing that compared to devices I've had in the past (even the SGS II which I hated lol) had some things pop up pretty quickly. Also make sure that no one takes this as me complaining, just thinking out loud here.
And as to the xposed stuff, Im atually just interested in some slimed down stock roms and AOSP, but thanks for making sure I knew about it
PS: Ive also had this phone for close to a month so Im probably feeling that rom flash bug harder than most XD

Hey ite only been out 4 a week man
Sent from my LG-LS980 using XDA Premium HD app

HaiKaiDo said:
I guess I didn't think about the fact that the other variants had been out for a few months already, but I really wasn't trying to comparing them. I was just noticing that compared to devices I've had in the past (even the SGS II which I hated lol) had some things pop up pretty quickly. Also make sure that no one takes this as me complaining, just thinking out loud here.
And as to the xposed stuff, Im atually just interested in some slimed down stock roms and AOSP, but thanks for making sure I knew about it
PS: Ive also had this phone for close to a month so Im probably feeling that rom flash bug harder than most XD
Click to expand...
Click to collapse
I'm also getting the flash bug since, like you, I got mine mid Oct.
Great to hear though that there is development support coming. Very excited!!!

WiFi tether is working on aosp goto general section, Sprint testers 4.3 rom and download Carbon ROM and grab 4.3.1 gapps from the Verizon pa ROM it works wonders no rotation issues

chris0160 said:
WiFi tether is working on aosp goto general section, Sprint testers 4.3 rom and download Carbon ROM and grab 4.3.1 gapps from the Verizon pa ROM it works wonders no rotation issues
Click to expand...
Click to collapse
Not worried about development because it's still early. But we do have Garwynn:good:

chris0160 said:
WiFi tether is working on aosp goto general section, Sprint testers 4.3 rom and download Carbon ROM and grab 4.3.1 gapps from the Verizon pa ROM it works wonders no rotation issues
Click to expand...
Click to collapse
Can you provide a direct link somewhere so its easier for folks to find the location? I can't seem to find what you are eluding to.

cdsbj6508 said:
Not worried about development because it's still early. But we do have Garwynn:good:
Click to expand...
Click to collapse
Garwynn!? Hell yeah!! I've worked with some stuff of his before. Awesome work...

chris0160 said:
WiFi tether is working on aosp goto general section, Sprint testers 4.3 rom and download Carbon ROM and grab 4.3.1 gapps from the Verizon pa ROM it works wonders no rotation issues
Click to expand...
Click to collapse
How do you flash this Rom?
I'm rooted, have the Rom downloaded... now what?
Sent from my LG-LS980 using xda app-developers app

centro714 said:
How do you flash this Rom?
I'm rooted, have the Rom downloaded... now what?
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Link please??

chris0160 said:
WiFi tether is working on aosp goto general section, Sprint testers 4.3 rom and download Carbon ROM and grab 4.3.1 gapps from the Verizon pa ROM it works wonders no rotation issues
Click to expand...
Click to collapse
I've searched and cannot find it
Sent from my LG-LS980 using Xparent Red Tapatalk 2

If you think you guys have no development, check out d803! We don't even have our own section
Sent from my LG-D802 using XDA Premium 4 mobile app

BaYRiCaN said:
I've searched and cannot find it
Sent from my LG-LS980 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
How can we help test it if we can't find the darn thing?

Here's where the Rom is located:
http://forum.xda-developers.com/showthread.php?t=2509486
So far I've rooted, download rom, installed twrp, tried flashing it but it booted stuck on carbon logo. It may be because I don't have the gapps file.
Any one with a link to 4.3.1 gapps?
Sent from my LG-LS980 using xda app-developers app

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.