Database Info

[Q] Screen turning off when docking

Hi all,
I have flashed a CM10 (obviously unofficial) build to see what JB would bring to the TF700. Well, I'm impressed and very much looking forward to it.
However..........
The portrait-orientation bug (currently, portrait apps do not resize correctly) precludes me from reading on the 700 (since it clips the screen in 1/3 / 2/3 parts and repeats content -- absolutely horrible), and that's one of the main things I use it for at the moment.So, I decided to get back to Zeus34's ICS (and otherwise excellent ) ROM. I wiped data / cache / Dalvik cache / system in between installs, mostly multiple times (and obviously system only before an install, thank you ).
I can install Zeus ROM v4.0 from recovery -- Google setup plays nicely for the most part (had one crash in several installs), but whenever I have the keyboard dock connected (whether I boot it without and then connect it, or boot it with it connected from the start) my screen goes black and won't react to the power button anymore. If I then disconnect the dock, I can turn the screen of the tablet on again with the power button.
:silly:
It does the same thing after restoring my backup of the stock .26 ROM, by the way, with the added problem of the keyboard not reacting anymore several times. I then installed CM10 again, and the keyboard dock was functional again. <?>
One admission up-front: I have a depleted keyboard dock, and I forgot the charger at home (I am now at work, approx. 100 kilometers from base).
Ok, question time: could the keyboard dock's depletion play a role in this? Why doesn't it do that under stock ROM? Any suggestions? Have I done something stupid? Could my keyboard be dying on me (although it works now again under Cm10)?
I loved CM10 (and I tried Black Bean as well -- did the same thing with the orientation, so had to go for now as well) -- boy, are we in for a treat when they start supporting the TF700 more fully....

For what it's worth, I basically did the exact same thing - tried CM10 and didn't feel like dealing with the issues (and also really missed the Asus-specific customizations), so I then restored back to my Zeus 4.0 setup (using a full TWRP backup, including the boot partition).
Anyway, everything is 100% back to "normal" for me now. So, if you backed up the boot partition with TWRP before installing CM10, it's probably something to do with the fact that the keyboard dock is out of juice...
Did you backup the boot partition in TWRP before installing CM10?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Technically he installed the Zeus ROM which should have formatted the boot partition with the respective boot image. I know zeus ROM has it. So I am guessing its the dock being depleted.
Sent from my Galaxy Nexus using xda app-developers app

Thanks for the replies! I came home tonight after work and didn't have the energy left to tackle the problem then and there, and figured out charging the dock would at least eliminate that factor from troubleshooting this. This morning, however, I booted up the now fully charged combo, and under yesterday's fresh Zeus install... same thing happens -- to my joy, it booted normally, but about thirty seconds in, it lowered brightness drastically, and a few seconds later, it completely borked out on me again. In frustration, knowing what that would mean, I did a clean install of the .26 update with TWRP -- obviously, I lost everything root and such, and I too do now experience even more extreme lag and choppiness than the "stock stock experience" showed me.
So, in the end, I do not think the depleted dock was the problem, and I thought that before because stock ROM doesn't give a damn if it has juice or not (it is powered by the main if depleted, so it runs down the battery that much faster, maybe, but it will function). Explicitly: this is NOT meant as an ITYS (I Told You So), but I'm trying to figure out what is wrong here, because the current situation is.... slightly undesirable.

MartyHulskemper said:
Thanks for the replies! I came home tonight after work and didn't have the energy left to tackle the problem then and there, and figured out charging the dock would at least eliminate that factor from troubleshooting this. This morning, however, I booted up the now fully charged combo, and under yesterday's fresh Zeus install... same thing happens -- to my joy, it booted normally, but about thirty seconds in, it lowered brightness drastically, and a few seconds later, it completely borked out on me again. In frustration, knowing what that would mean, I did a clean install of the .26 update with TWRP -- obviously, I lost everything root and such, and I too do now experience even more extreme lag and choppiness than the "stock stock experience" showed me.
So, in the end, I do not think the depleted dock was the problem, and I thought that before because stock ROM doesn't give a damn if it has juice or not (it is powered by the main if depleted, so it runs down the battery that much faster, maybe, but it will function). Explicitly: this is NOT meant as an ITYS (I Told You So), but I'm trying to figure out what is wrong here, because the current situation is.... slightly undesirable.
Click to expand...
Click to collapse
Interesting - so before you loaded CM10, you did a full TWRP backup of your Zeus 4 install, correct (including Boot)? I'm just trying to determine why you are seeing different results than myself being that it sounds like we did the exact same process (TWRP backup, CM10 install, TWRP restore) but yet we are seeing different results. I did make sure that Boot was selected in TWRP before doing my backup - I'm wondering if that is possibly the difference?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

jtrosky said:
Interesting - so before you loaded CM10, you did a full TWRP backup of your Zeus 4 install, correct (including Boot)? I'm just trying to determine why you are seeing different results than myself being that it sounds like we did the exact same process (TWRP backup, CM10 install, TWRP restore) but yet we are seeing different results. I did make sure that Boot was selected in TWRP before doing my backup - I'm wondering if that is possibly the difference?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Yes, I believe boot was included, but I am not sure, since it may have been before we were actually able to include the boot partition when backing up with TWRP. I'll take a look.
I am back to .26 stock, rooted and with TWRP. I am going to dip my toes in Zeus ROM again and see if I bump my head again. I'll be holding off on the otherwise absolutely great AOSP/CM10 builds for now, as the portrait bug is really killing those for me. I have found a reference to a TF(101?) AOSP-based ROM of which the dev states (s)he fixed the screen tearing and portrait bug, and I spammed the threads with the link. If it's of use to even one of those ROMs, I'll take the penalty of an infraction if need be. I hope it results in something, since I do notice a tremendous difference in smoothness and responsiveness between my current .26 and the AOSP/CM10 builds
M'kay, here goes. Wish me luck....
EDIT: So far, everything seems back to normal now (every time the time-out kicks in and the screen goes off, I'm having palpitations. Hahahaha! So far, I've been able to revive both tablet and myself by hitting the power button and seeing the screen turn on again. ). I guess flashing the stock .26 and then Zeus fixed it. I still do not know what the issue was though,'so it isnt very helpful. :S

Touch Screen Issue tf101

I have touch screen issues and I'm not sure if it is Hardware related or software.
I will be using my tablet and all of a sudden I lose 90% of control. Basically, I can't touch anything. I know most would say that hardware but, I cycle the power button (Not turning tablet off just screen off screen on) and touch comes back.
I noticed this issues when ICS just came out for our tablets and we were getting major RR and SOD.
Any one else experienced this or am I the only crazy person that this happen to.
Thanks in advance.
Ps. If you have experienced this please post solution.
Video - http://www.youtube.com/watch?v=oO9-D2QJks0&feature=youtu.be
Simular to this issue
http://forum.xda-developers.com/showthread.php?t=1826676

legauxg said:
I have touch screen issues and I'm not sure if it is Hardware related or software.
I will be using my tablet and all of a sudden I lose 90% of control. Basically, I can't touch anything. I know most would say that hardware but, I cycle the power button (Not turning tablet off just screen off screen on) and touch comes back.
I noticed this issues when ICS just came out for our tablets and we were getting major RR and SOD.
Any one else experienced this or am I the only crazy person that this happen to.
Thanks in advance.
Ps. If you have experienced this please post solution.
Click to expand...
Click to collapse
It sounds like you may be on a different ROM then stock. I would recommend a couple of things. First back your system up, and do a clean install. Clear all cache and go. If your on a non stock ROM, then It would probably be a good idea to visit the thread of that ROM and see what they have had come up about the issue.

MasterDecker said:
It sounds like you may be on a different ROM then stock. I would recommend a couple of things. First back your system up, and do a clean install. Clear all cache and go. If your on a non stock ROM, then It would probably be a good idea to visit the thread of that ROM and see what they have had come up about the issue.
Click to expand...
Click to collapse
That is correct I am on Non- stock rom. Guess I should have said that. Should i go all the way back to original rom (HC) then up grade to ICS(stock)?
I have tried multiple custom roms but they all seem to do the same thing. Me being a comp. tech. the way I can restore touch by power cycling makes me think it is software.

legauxg said:
That is correct I am on Non- stock rom. Guess I should have said that. Should i go all the way back to original rom (HC) then up grade to ICS(stock)?
I have tried multiple custom roms but they all seem to do the same thing. Me being a comp. tech. the way I can restore touch by power cycling makes me think it is software.
Click to expand...
Click to collapse
I have had it before but very rare, power tap the power to turn off the screen then tap it again and it all comes back?
It is so rare I just live with it.
Probably been the most stable on eos3 81 with kat 69 kernel

pops106 said:
I have had it before but very rare, power tap the power to turn off the screen then tap it again and it all comes back?
It is so rare I just live with it.
Probably been the most stable on eos3 81 with kat 69 kernel
Click to expand...
Click to collapse
From you response, this is why I am thinking this is related to software. I do not have the proper knowledge to research but I am asking help from a knowledgeable person.
I screen losses touch regularly now. it is taking away from my experience. Are there any drivers particularly for the screen input that can be updated or downgraded to a known working version.
Thanks for not making me fell like I am the only crazy person!

Video to show what Im talking about
http://www.youtube.com/watch?v=oO9-D2QJks0&feature=youtu.be

Touchscreen unresponsive when dock is connected

After updating OTA the other day (I've always been on stock firmware), my tablet seemed to be working fine. However, once I connect the dock sections of my touchscreen become unresponsive. I can still scroll and click with the touchpad on my dock and parts of the touchscreen still work. This only started happening after the update - without the dock my touchscreen works perfectly (unless I connect the dock first, in which case I need to restart my tablet before the screen works again).
I'm not sure if this is an issue with the update or if anyone else has experienced the same problems. Hopefully someone will know what's up.
Any help is appreciated!
Edit: Was playing around a bit and realized I could "fix" it by locking/unlocking the tablet with the dock connected...so I suppose it's not a hardware issue but rather a problem with the new update.

bamtori said:
After updating OTA the other day (I've always been on stock firmware), my tablet seemed to be working fine. However, once I connect the dock sections of my touchscreen become unresponsive. I can still scroll and click with the touchpad on my dock and parts of the touchscreen still work. This only started happening after the update - without the dock my touchscreen works perfectly (unless I connect the dock first, in which case I need to restart my tablet before the screen works again).
I'm not sure if this is an issue with the update or if anyone else has experienced the same problems. Hopefully someone will know what's up.
Any help is appreciated!
Edit: Was playing around a bit and realized I could "fix" it by locking/unlocking the tablet with the dock connected...so I suppose it's not a hardware issue but rather a problem with the new update.
Click to expand...
Click to collapse
After the 4.2 update, my tablet has also become totally incapable of working with the dock connected.
Everything stops working as soon as I connect it; Seems even worse than what you're experiencing.
I hope Asus knows this, because I am sure it has to do with their update, not my tablet

Mmmmhh... So far for quality control? I really do feel f r you guys, asn many of you will not have been able to unlock, and therefore cannot go the custom route. (Especially sad for you, adelancker, since your tablet was unlocked originally!)

You tried a complete system reformat. Restore to Factory?

KinetiClutch said:
You tried a complete system reformat. Restore to Factory?
Click to expand...
Click to collapse
with the dock connected? You can't
Without the dock connected, yes, and got no results
Hahaha, Asus really messed up good.
@MartyHulskemper I have been able to unlock after a lot of whining!
But still, the problem originated from before the unlocking itself...
But you might have given me an idea!!!!
I can try and:
1) make a nandroid
2) go back to 4.1 Cromi
3) connect the dock: see if that works
and then try to
4) flash 4.2 Cromi-X on it with the dock connected.
Maybe that'd help?

adelancker said:
After the 4.2 update, my tablet has also become totally incapable of working with the dock connected.
Everything stops working as soon as I connect it; Seems even worse than what you're experiencing.
I hope Asus knows this, because I am sure it has to do with their update, not my tablet
Click to expand...
Click to collapse
bamtori said:
After updating OTA the other day (I've always been on stock firmware), my tablet seemed to be working fine. However, once I connect the dock sections of my touchscreen become unresponsive. I can still scroll and click with the touchpad on my dock and parts of the touchscreen still work. This only started happening after the update - without the dock my touchscreen works perfectly (unless I connect the dock first, in which case I need to restart my tablet before the screen works again).
I'm not sure if this is an issue with the update or if anyone else has experienced the same problems. Hopefully someone will know what's up.
Any help is appreciated!
Edit: Was playing around a bit and realized I could "fix" it by locking/unlocking the tablet with the dock connected...so I suppose it's not a hardware issue but rather a problem with the new update.
Click to expand...
Click to collapse
Did you apply the update with the dock detached?
Have you tried rebooting with the dock attached? If that does not solve it, I would reflash the last update with the tablet docked.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

berndblb said:
Did you apply the update with the dock detached?
Have you tried rebooting with the dock attached? If that does not solve it, I would reflash the last update with the tablet docked.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
The update was applied without the dock. I tried a factory reset to no avail - although, cold-booting a few times seemed to make the problem less frequent. Restarting with the dock connected had no effect.
Strangely enough, I noticed the system bar lock was enabled by default (it was disabled before the update), once I disabled it again I noticed an immediate difference in the performance of my tablet. Much less frequent lag/unresponsiveness with the dock connected - No idea why this would make a difference though

berndblb said:
Did you apply the update with the dock detached?
Have you tried rebooting with the dock attached? If that does not solve it, I would reflash the last update with the tablet docked.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
I can say that I did that update to 4.2 without dock, I am afraid.
I have tried rebooting, but it just won't boot as long as the dock's connected...

I have the same thing* . Tried many things hard reset, cold boot, downgrade..but unfortunately nothing helps :/
Now I want to drain completely battery-especially in mobile dock
*The same thing means tablet is unresponsive when dock connected(I can't: boot with it, lock scren, neither make factory reset)
Fortunetly I still have warranty, but can't give it now, because I need it for holidays. So did you find something that could help me?
Temporary solution is downgrade to 4.1(10.4.2.20), then it doesn't lag and I can use USB port so I can have keyboard and mouse, but this isn't mobile solution.. (sometimes it also charges from dock-I think when tablet battery is below 90% , but when dock is connected to charger, then it charges whole time)
I don't remember if I made update with or without dock connected.

TWRP and CWM Unstable

Hey guys,
I need help. Badly. My trusty SCH-I535 has pretty much gone to pot over the last three days. It started with the lockscreen/power button becoming so loose and sensitive, that the screen was perpetually turning on and off. However, my warranty expired last Thursday. Aside from that, the software was functioning beautiful (Carbon ROM, unknown August 4.3 nightly). Today however, the phone decided to freak out. Suddenly, it began displaying the incorrect time, wouldn't show me new messages, and applications were incredibly unstable. In an attempt to fix the issue, I decided to re-flash the ROM. This however, made no change. Therefore, I made the decision to finally update to the most recent stable version. After doing this, the phone wouldn't boot past the carbon boot animation. I rolled back to an older build, and had the same issue.
Here's where it gets sucky. After rolling back didn't do anything, I was in the process of re-flashing 1.8. During install process, TWRP crashed. This left me without a bootable system partition. As the night has worn on, it's become worse and worse. Now, TWRP is crashing often before the splash screen, at the "Samsung Galaxy SIII" screen. Occasionally it will load, but always locks up and crashes before finishing the install process. Same deal with CWM. I have tried several versions of both recoveries and none have made a single bit of difference. I've scoured the forums, and can't seem to find an identical problem/working fix. I've tried everything I can find, and so far, nothing productive has happened. It's 3:25AM over here, and I'm exhausted. I'm at my wits end. Any input would be fantastic.
Thanks so much,
The_Unofficial

Did you try to flash via ODIN? Maybe it will help you to boot it to normal.

The_Unofficial said:
Hey guys,
I need help. Badly. My trusty SCH-I535 has pretty much gone to pot over the last three days. It started with the lockscreen/power button becoming so loose and sensitive, that the screen was perpetually turning on and off. However, my warranty expired last Thursday. Aside from that, the software was functioning beautiful (Carbon ROM, unknown August 4.3 nightly). Today however, the phone decided to freak out. Suddenly, it began displaying the incorrect time, wouldn't show me new messages, and applications were incredibly unstable. In an attempt to fix the issue, I decided to re-flash the ROM. This however, made no change. Therefore, I made the decision to finally update to the most recent stable version. After doing this, the phone wouldn't boot past the carbon boot animation. I rolled back to an older build, and had the same issue.
Here's where it gets sucky. After rolling back didn't do anything, I was in the process of re-flashing 1.8. During install process, TWRP crashed. This left me without a bootable system partition. As the night has worn on, it's become worse and worse. Now, TWRP is crashing often before the splash screen, at the "Samsung Galaxy SIII" screen. Occasionally it will load, but always locks up and crashes before finishing the install process. Same deal with CWM. I have tried several versions of both recoveries and none have made a single bit of difference. I've scoured the forums, and can't seem to find an identical problem/working fix. I've tried everything I can find, and so far, nothing productive has happened. It's 3:25AM over here, and I'm exhausted. I'm at my wits end. Any input would be fantastic.
Thanks so much,
The_Unofficial
Click to expand...
Click to collapse
Your broken power button is probably the issue. The reason your recoveries are crashing is likely because the power button is triggered and it's making the phone turn off in the middle of the process.
It's unfortunate your warranty just expired, but you can get it fixed through a website, then you should be good from there. Also I would try to call up Samsung and tell them what you think the problem is, they might give you a break and fix your phone anyway since it's only a week after warranty.
Sent from my SCH-I535 using Tapatalk 2

Details...
Alright guys. More details. Sorry it took so long to reply. Apparently I had Gmail set to send XDA emails to spam. Silly me.
The more times I attempt to boot to recovery, the earlier TWRP will freeze.
TWRP rarely makes it beyond the "Installing System" process
TWRP NEVER makes it beyond the "Creating Symlinks" phase
I'm using TWRP 2.6.3.0
If I let the phone sit, it gets farther in the installation process before hanging
Bad Username, I tried contacting Samsung and Verizon. Neither one of them would replace , or fix it for me. Have any specific resources for repairing the button? That would be excellent. I just ordered a cheap $3 case on Amazon to see if that would help fix the problem. I don't, however believe this is causing the problem. TWRP has a lockscreen. It never goes to the lockscreen, it just hangs, then eventually force reboots. Almost as if some temporary RAM storage is being filled up. It's quite strange.
skyss07 I would REALLY prefer not to flash to stalk. Like, REALLY. This would mean losing all my files and pictures. I'm not too keen on that. I'm saving that as a final resort only.

The_Unofficial said:
Alright guys. More details. Sorry it took so long to reply. Apparently I had Gmail set to send XDA emails to spam. Silly me.
The more times I attempt to boot to recovery, the earlier TWRP will freeze.
TWRP rarely makes it beyond the "Installing System" process
TWRP NEVER makes it beyond the "Creating Symlinks" phase
I'm using TWRP 2.6.3.0
If I let the phone sit, it gets farther in the installation process before hanging
Bad Username, I tried contacting Samsung and Verizon. Neither one of them would replace , or fix it for me. Have any specific resources for repairing the button? That would be excellent. I just ordered a cheap $3 case on Amazon to see if that would help fix the problem. I don't, however believe this is causing the problem. TWRP has a lockscreen. It never goes to the lockscreen, it just hangs, then eventually force reboots. Almost as if some temporary RAM storage is being filled up. It's quite strange.
skyss07 I would REALLY prefer not to flash to stalk. Like, REALLY. This would mean losing all my files and pictures. I'm not too keen on that. I'm saving that as a final resort only.
Click to expand...
Click to collapse
Mobile tech videos would do it, not sure what the cost would be, I'd try contacting them.
Sent from my SCH-I535 using Tapatalk 2

Bootloops

My Pixel 3 randomly restarts and gets stuck in long bootloops. The frequency is completely random, ranging from three times a day (rarely) to once a week or two (more common). There is no trigger, sometimes I have it in my hand, doing stuff, and it does that, sometimes it does it when it's sleeping.
The bootloop is always the same.
I see the bootloader message, then th Google logo, and the phone restars after about one second. I never counted to loops but sometimes it must be tens of them. There doesn't seem to be a way to stop them, or at least I am not awaer of any key combinations.
I presume the phone eventually boots into safe mode or something.
I've had it for several months, bought it used in good condition off Ebay, and other than this I never noticed anything off.
This is extremely frustrating and I have no idea what to do.
Does anyone have any idea?

I really hope it never been inside water. Try updating your OS, or change to Custom ROM. If it still occurs, then that's a big problem.

It's most probably an app that's causing this, try disabling/uninstalling some apps that you don't need.
Booting into safe mode is also an option, that way you can make sure if an app is actually causing this.

I factory reset and later on completely reflashed the phone at one point in not too distant past and it didn't help one bit.
It's also completely untroubleshootable given how randomly the problem occurs, which also makes me sceptical about an app doing this
I'm inclined to think it could be a hardware problem.

WalrusInAnus said:
I factory reset and later on completely reflashed the phone at one point in not too distant past and it didn't help one bit.
It's also completely untroubleshootable given how randomly the problem occurs, which also makes me sceptical about an app doing this
I'm inclined to think it could be a hardware problem.
Click to expand...
Click to collapse
It's highly unlikely for it to be hardware problem, unless you have water/dust/humid damage.
Or maybe your phone heats really fast and therefore some pin inside the motherboard gets shortened due to the heat. But what are the chances of this happening?
But just to be sure, what happens when you connect your device to a charger with output more than 2 amp?
Did you modify your device in anyway whatsoever? Anything the previous owner noted about the device?

I didn't nodify it at all.
This is the charger I use https://www.alzashop.com/vention-dual-quick-30-usb-a-wall-charger-18w-18w-white-d6323711.htm

WalrusInAnus said:
I didn't nodify it at all.
This is the charger I use https://www.alzashop.com/vention-dual-quick-30-usb-a-wall-charger-18w-18w-white-d6323711.htm
Click to expand...
Click to collapse
Yeah, just flash some different ROM on your device and we're good.
Make sure you backup everything through TWRP and that you're flashing your device specific ROM.

As a test you mean? I am used to the stock ROM and last time I checked, there was no stable Android 11 (I think) ROM I would use.

WalrusInAnus said:
As a test you mean? I am used to the stock ROM and last time I checked, there was no stable Android 11 (I think) ROM I would use.
Click to expand...
Click to collapse
Was the last time you checked a year ago?? A11 has been out for a good while now. Here: Stock A11 ROM (Blueline).
And not as a test, no, flash it and keep using it. You can also flash custom ROM if that's your thing.

XDHx86 said:
Was the last time you checked a year ago?? A11 has been out for a good while now. Here: Stock A11 ROM (Blueline).
And not as a test, no, flash it and keep using it. You can also flash custom ROM if that's your thing.
Click to expand...
Click to collapse
But I said I flashed the stock ROM before with no luck. You're suggesting I do the same again. That makes very little sense.

What about the Google camera and LOS btw?