A couple days ago I noticed the slide to unlock function stopped working. Sometimes after a rebot it work again. Sometimes opening the gamepad the screen goes to landscape display and it can be unlocked. But today it has gone completely frozen, none of these workarounds seems to work. The phone seems fine, it turns on and off correctly, but since it is locked by default I can't do a thing. Also, I had it to request the SIM pin code at start up, but since it locked it doesn't connect to the network. The only thing that works is holding On/Off button, and selecting shut work with the gamepad.
When it does unlock it only work in landscape mode, when the screen is vertical nothing works!
In other forums this problems seems to be related to HTC phones (mine is Xperia Play, 8 months old, not rooted, v. it ends with 69 I don't know the exact number) or a low battery problem (is fully charged). My guess is that opening and closing the phone to use the gamepad might have damaged some bus cable in the screen. Does anyone ever had a problem like this and know how to fix it, if it software related?
All technology seems to be against me: Windows Phone discontinued support for 6.5 after I got one and now this with Android. iPhone seems the only thing that works "kinda" well and I've never had one
alextrevelian said:
A couple days ago I noticed the slide to unlock function stopped working. Sometimes after a rebot it work again. Sometimes opening the gamepad the screen goes to landscape display and it can be unlocked. But today it has gone completely frozen, none of these workarounds seems to work. The phone seems fine, it turns on and off correctly, but since it is locked by default I can't do a thing. Also, I had it to request the SIM pin code at start up, but since it locked it doesn't connect to the network. The only thing that works is holding On/Off button, and selecting shut work with the gamepad.
When it does unlock it only work in landscape mode, when the screen is vertical nothing works!
In other forums this problems seems to be related to HTC phones (mine is Xperia Play, 8 months old, not rooted, v. it ends with 69 I don't know the exact number) or a low battery problem (is fully charged). My guess is that opening and closing the phone to use the gamepad might have damaged some bus cable in the screen. Does anyone ever had a problem like this and know how to fix it, if it software related?
All technology seems to be against me: Windows Phone discontinued support for 6.5 after I got one and now this with Android. iPhone seems the only thing that works "kinda" well and I've never had one
Click to expand...
Click to collapse
what u can do is update phone using seus [sony ericcson update service] (its easy) or flash stock rom using flashtool
if its a software prob. it will be gone (i had a similar issue on my lg p500 got solved with reflashing rom. by the way i was on custom rom)
I had recently unlocked my phone because i've been trying to root it to remove the bloatware that comes on the system. The phone was working fine (for about a couple of days) and suddenly the lock screen shows up static-y looking. Everything still works (kind of). If you know where the slide is to unlock it, you can, and after awhile it goes to normal looks. Also, the device is running semi-buggy and slow. Any ideas / help?
Thanks
MY v500 G Pad is experiencing a weird issue where immediately after waking the device (via knock-on or power button), my lock screen will appear as expected, but then almost immediately the screen will become unresponsive (I'm unable to swipe my pattern to unlock) and the display will dim in increments until black. Once the screen is off, I have to hold down the power button to get the device to reboot.
The changes I have made that seems to coincide with this issue are:
1. rooted the device using the .bat script method
2. installed TWRP recovery
3. switched to Nova Launcher
It's important to note, I have not rom'd my device, and am still running the stock rom.
This is happening one out of every 15 or so times I unlock my device. I have switched from pattern to password unlock to see if it's an issue related specifically to the pattern lock screen (although I have used pattern unlock since the day I got the device).
Any ideas would be greatly appreciated!
Thanks
longboarder543 said:
MY v500 G Pad is experiencing a weird issue where immediately after waking the device (via knock-on or power button), my lock screen will appear as expected, but then almost immediately the screen will become unresponsive (I'm unable to swipe my pattern to unlock) and the display will dim in increments until black. Once the screen is off, I have to hold down the power button to get the device to reboot.
The changes I have made that seems to coincide with this issue are:
1. rooted the device using the .bat script method
2. installed TWRP recovery
3. switched to Nova Launcher
It's important to note, I have not rom'd my device, and am still running the stock rom.
This is happening one out of every 15 or so times I unlock my device. I have switched from pattern to password unlock to see if it's an issue related specifically to the pattern lock screen (although I have used pattern unlock since the day I got the device).
Any ideas would be greatly appreciated!
Thanks
Click to expand...
Click to collapse
I don't have that issue and I'm stock , rooted and with twrp you should probably check it's either some settings causing this or more likely an app you installed.
Sent from my SGH-T889 using Tapatalk 2
Thanks for the info Naruto. I think I'm going to remove Nova launcher and see if the problem goes away.
Meanwhile, the problem just happened again, but manifested itself slightly differently. Basically, just a few minutes ago when I pushed the power button to wake the device, nothing happend for ~ 10 seconds. Finally, the lock screen came up, but I got an error message "Sorry! Process system isn't responding. Do you want to close it?" Options were "Wait" and "OK". I selected OK and was taken to the lock screen like normal.
What do you guys think?
I had root from dalingrin and twrp on stock rom for about 2 months and i never experienced this issue you report. The lock screen is related to the launcher and as you use nova launcher i d say that it is most probably caused by it.
Thanks for all the help guys. I'm not ready to say that the problem is fixed quite yet, but after switching back to the stock launcher and rebooting, I have locked and unlocked the tablet about 50 times without issue. Looks like the problem was indeed Nova Launcher. That's kind of a bummer because I love Nova, and I have it setup exactly like my phone and it works great for me.
Maybe you could try to re download nova again that's what I'm using and I have no issues. Maybe it was a setting you had checked inside of its settings ?
Sent from my SGH-T889 using Tapatalk 2
longboarder543 said:
MY v500 G Pad is experiencing a weird issue where immediately after waking the device (via knock-on or power button), my lock screen will appear as expected, but then almost immediately the screen will become unresponsive (I'm unable to swipe my pattern to unlock) and the display will dim in increments until black. Once the screen is off, I have to hold down the power button to get the device to reboot.
Click to expand...
Click to collapse
I got the same thing on a completely unmodified G Pad last weekend. It happened once, worked ok for a few unlocks, then happened a second time. Each time I had to hold the power button down to force a reboot. It's hasn't happened before or since, so I've no idea what caused it, but I did notice something that might or might not be relevant - I happened to be looking at the battery graph later that day, and noticed that at the time of the forced reboots, the battery appeared to drop instantly by about 10%. There was a break in the graph - no vertical line showing the drop, the line just ended, then started off again immediately 10% lower down. If you get the same issue again, it would be interesting to see if your battery graph behaved in the same way.
I had this problem with stock rom changed to Mahdi
No reboots yet.
By the way, I saw a review video on YouTube and the guy was showing knock knock (spell?) and the g pad just crashed and rebooted.
Edit:
I have an LG G2, best phone ever never crashed no lag and a fast phone with great LCD maybe the best mobile screen I have ever seen.
Sent from my LG-V500 using xda app-developers app
Ok, so I don't think the problem was nova launcher after all. After switching back to the stock launcher, the tablet worked great for several hours, but eventually the problem started happening again. At that point, I rebooted into recovery, cleared cache and dalvik, then fixed permissions, and rebooted. Fingers crossed, but the issue hasn't returned once since, and we're going on 18 hours. I've even been using nova launcher without issue. Still not sure what the issue is, but at least for me, clearing cache and fixing permissions has worked so far.
Sent from my LG-V500 using Tapatalk
There is a known issue with 4.2+ of rebooting if you have third party widgets (Not sure which) on the lock screen. Do you have any on there?
http://blogs.computerworld.com/android/21427/android-42-random-reboots
stevessvt said:
There is a known issue with 4.2+ of rebooting if you have third party widgets (Not sure which) on the lock screen. Do you have any on there?
http://blogs.computerworld.com/android/21427/android-42-random-reboots
Click to expand...
Click to collapse
Thanks for that -- unfortunately I don't have any third-party widgets on the lock screen.
Victoria75001 said:
I got the same thing on a completely unmodified G Pad last weekend. It happened once, worked ok for a few unlocks, then happened a second time. Each time I had to hold the power button down to force a reboot. It's hasn't happened before or since, so I've no idea what caused it, but I did notice something that might or might not be relevant - I happened to be looking at the battery graph later that day, and noticed that at the time of the forced reboots, the battery appeared to drop instantly by about 10%. There was a break in the graph - no vertical line showing the drop, the line just ended, then started off again immediately 10% lower down. If you get the same issue again, it would be interesting to see if your battery graph behaved in the same way.
Click to expand...
Click to collapse
When I get home I'll check my battery stats to see if similar happened on mine
I bought and second hand Verizon LG 8.3 a few weeks ago for my wife. She used it trouble free for about 2-3 weeks, but just last week, it has started acting weird. I began with random crashes to desktop during some of the games she plays (Soduku, Wheel of Fortune, etc.) After reset, it wasn't crashing to desktop, but the screen goes blank temporarily then returns to normal. When reading a Nook book, the screen will go blank (not black, just words disappear) and the loading wheel appears. After 1-2 seconds, it returns to the normal page. Additionally, occasionally, the Nook settings bar appears randomly, as well. It has a Otter case, which I removed to test, but the issues persist. I has the stock 4.2.2, and I have not tried rooting or any major changes as of yet. I have tried factory reset 3 times now.
I contacted LG, but they just want it shipped back with receipt (which I don't have), or else they can't do anything. Any ideas here? Can this be hardware related? Should I try rooting first? Wait for the Kitkat update to see if that fixes it, etc?
Update
I just thought I would update, in case anyone else runs into this issue with the G Pad 8.3.
Turns out, it was the SIM card. After purchasing it, the 4G service was still active for a couple of weeks (Verizon's 4G is fast, btw...) so it remained in the tablet. It took a several days after the service ended for the issue to appear, and then it dawned on me; even though the 4G service was turned off, that the SIM may affecting the system. Sure enough, after removing the SIM card all is well. Wish I would have thought of it before resetting the thing like 10 times, but better late than never... :cyclops:
Maybe this would be obvious to others, but having never used a SIM card, it never even occurred to me. So just a heads up to anyone buying a Verizon LG 8.3; make sure the SIM card is removed, if you plan on not using the cellular service...
Hi there,
i couldn't find my problem already discussed via the board search, so i'm posting it here. i hope this is the right board, if not please relocate.
i'm using the find7a since about 1 year now. the only updates i did for colorOS were the ones that have been proposed automatically via the popups. but these i did every time.
i have alwas had several issues with the phone/os, mostly random shutdowns without any reason. but at some point, these shutdowns suddenly declined and i got used to live with the few that still occur from time to time. but now i have a much bigger problem and i don't know where it came from:
few days ago, i got the popup that a new os-update was available. i had a little time so i did it instantly. without any problems the update was installed and after that the phone booted as always and nothing strange happened. 1 day later i recognized that something had changed. i wasn't able to turn on the wifi anymore! same goes for the bluetooth. also the automatic screen rotation (when you turn the phone in a right angle) didn't work anymore! but all of them DID work for the 1 day since i made the last update. so i assumed it has nothing to do with the new os-version (which is 1.2.9 btw). i didn't change anything in the phones settings, everything was the same. but from one moment to the other these three problems suddenly came up. maybe even more that i didn't recognize yet.
although everything worked fine for 1 day since the update, i thought maybe the update could be the problem after all. so i wanted to flash another version of colorOS. i tried the 2.0.8i which was considered stable by the official oppo board admins on friday. the flashing worked fine, colorOS 2.0.8i booted, but the problems remained! still no wifi, no bluetooth, no screen rotation.
next thing i thought: maybe it's a hardware problem. so i flashed another ROM (always making a factory reset + wiping all cashes and data from the internal storage first), i tried a few. they were all flashed successfull but most of them hung up during the first boot sequence (cyanogenmod, paranoid, nameless), i always got stuck in the loading screen. last one i tried was OMNI ROM, and this one finally worked, meaning i got it started. first thing i did was checking the wifi connection and what do you know? the wifi worked just fine, my home network was found immediately und the connection went all good! which means a hardware defect should be out of the question.
this brings me back to thinking the problem lies within colorOS. which would be very sad becaue i really like colorOS and i would like to keep using it!
reproduction of the issues:
to reproduce the problems, when you are on the home screen you simply have to drag down the shortcut-menu. then tap on "wifi" and watch the symbol turn into the one for "loading" (the circling line). and then: nothing happens. the loading symbol just keeps on circling on and on. when you slide the menu up and down again, the normal "wifi-off" symbol shows and wifi is not turned on.
almost the same goes for the bluetooth. only when you tap this icon, the loading animation stops after a few seconds und the "bluetooth-off" icon appers again, this time without sliding the menu up and down. bluetooth stays turned off anyway.
for the rotation problem you just need to got to an app, where you can type in some text, f.e. whatsapp or gmail. tap the message area to make the keyboard and the cursor appear and then turn the phone from vertical to horizontal. normally the display should rotate automatically, but it doesn't it just stays in the vertical view mode. of course the rotation ist activated all the time, so no need to advice that
the rotation problem does not only occur when trying to type sth. in but also when i want to watch videos (f.e. with the vlc player app). the video stays locked in the vertical mode, making the image very small of course. this is also very annoying!
so, what do you think could be the reason for my problems? and what could i do to solve them? i hope you can help me.
i attached a log-file which hopefully shows the bugs.
my current specs are:
find 7a
colorOS 1.2.9
TWRP 2.8.6.0
greetings
tim