anyone else having issues with knock on not working? knock off works perfect everytime, but knock on is not working at all.i am now stock zvc unrooted after .toting to test if i maybe deleted something i shouldn't have, however after .toting it is still not functioning?
Robisgnarly said:
anyone else having issues with knock on not working? knock off works perfect everytime, but knock on is not working at all.i am now stock zvc unrooted after .toting to test if i maybe deleted something i shouldn't have, however after .toting it is still not functioning?
Click to expand...
Click to collapse
Just noticed that yesterday. I have stock zvc rooted. It did work shortly after i ran .tot. I just dont know why or when it stopped working. Knock off works just fine.
sclarktay4 said:
Just noticed that yesterday. I have stock zvc rooted. It did work shortly after i ran .tot. I just dont know why or when it stopped working. Knock off works just fine.
Click to expand...
Click to collapse
Apparently toggling it on and off, and recalibrating the screen in settings fixes the issue for many.
No Knock on
I am Optimus DE 2.2 ZVA radio, been on it since feb and has no issues. But Sunday, no more knock on. Knock off works great. I tried to re flash rom, tried a factory wipe and re calibrate screen. If, no one has a better idea I may just tot back to factory. Thank you in advance for any help.
abhinav.tella said:
Apparently toggling it on and off, and recalibrating the screen in settings fixes the issue for many.
Click to expand...
Click to collapse
Toggle on and off and calibrating did not resolve. What i did notice is that is will work eventually if you just keep tapping and timing yourself. I have tried lots of suggestions from other sources and nothing has worked consistently for me. The frustrating part is that it was working flawlessly not too long ago. I have not installed any new apps but some apps have updated. After about 50 tries, knockon did work but out of about 120 tries, i have only successfully got the phone to turn on twice by using knockon. Has anyone else had better luck?
sclarktay4 said:
Toggle on and off and calibrating did not resolve. What i did notice is that is will work eventually if you just keep tapping and timing yourself. I have tried lots of suggestions from other sources and nothing has worked consistently for me. The frustrating part is that it was working flawlessly not too long ago. I have not installed any new apps but some apps have updated. After about 50 tries, knockon did work but out of about 120 tries, i have only successfully got the phone to turn on twice by using knockon. Has anyone else had better luck?
Click to expand...
Click to collapse
I'm on ZVA rooted and I lost knock on a couple of weeks ago. I tried the usual culprits, turning on and off, calibrating, fix permissions, etc. It's still not back on. I'm not expert on these things, but could it be an app issue? Knock off works fine. I'm in the process of thinking about tot'ing to ZVC, but have to find 1/2 day to do it. Maybe when I do, I will load apps in sequence and reboot to see if an app could cause this problem. Again, I'm doubtful, but who knows.
esoh said:
I'm on ZVA rooted and I lost knock on a couple of weeks ago. I tried the usual culprits, turning on and off, calibrating, fix permissions, etc. It's still not back on. I'm not expert on these things, but could it be an app issue? Knock off works fine. I'm in the process of thinking about tot'ing to ZVC, but have to find 1/2 day to do it. Maybe when I do, I will load apps in sequence and reboot to see if an app could cause this problem. Again, I'm doubtful, but who knows.
Click to expand...
Click to collapse
have tried all this, and it will start to work again like mine has however it is hit or miss the problem is not consistent.
Its a hardware defect, go to developer options, turn on show screen touch data and find the dead area
Sent from my LG-LS980 using xda app-developers app
---------- Post added at 10:52 PM ---------- Previous post was at 10:49 PM ----------
My brothers didit and im about to get another replacement for the issue
Sent from my LG-LS980 using xda app-developers app
darkpoe said:
Its a hardware defect, go to developer options, turn on show screen touch data and find the dead area
Sent from my LG-LS980 using xda app-developers app
---------- Post added at 10:52 PM ---------- Previous post was at 10:49 PM ----------
My brothers didit and im about to get another replacement for the issue
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Did that. No dead area. I have been testing this for days now and for some reason knock on only works intermittently for me. Might be calling sprint soon if i cant figure this out
Edit:
Must be an app because my wife has g2 rooted by the same process mine is. Her knock on and knock off work perfectly. She does not install many apps, that is the only difference between our devices.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Has anyone tried to .tot back to pure stock to see if knock features work then?
Edit:
Can confirm, .tot back to stock zvc does not fix knock on. At least for me it did not. No apps installed and enabled knock features. Knock off still works perfect.
Sent from my LG-LS980 using XDA Premium 4 mobile app
esoh said:
I'm on ZVA rooted and I lost knock on a couple of weeks ago. I tried the usual culprits, turning on and off, calibrating, fix permissions, etc. It's still not back on. I'm not expert on these things, but could it be an app issue? Knock off works fine. I'm in the process of thinking about tot'ing to ZVC, but have to find 1/2 day to do it. Maybe when I do, I will load apps in sequence and reboot to see if an app could cause this problem. Again, I'm doubtful, but who knows.
Click to expand...
Click to collapse
Tried that. I .tot back to zvc today and i still do not have knock on, only knock off
I am having the exact same issue and have tried the exact same solutions to no avail..... Seems to be I guess a hardware issue. So now my ? is what will sprint do if I return the g2 rooted? It's just stock rooted with no recoveries or nothing special. Can I just Remove Greenify, G2Xposed, and Titanium Backup and give it to them to exchange? Can they really not except it? I love this feature and it annoys me to no end that it doesn't work but maybe 20% of the time.
coolblood2 said:
I am having the exact same issue and have tried the exact same solutions to no avail..... Seems to be I guess a hardware issue. So now my ? is what will sprint do if I return the g2 rooted? It's just stock rooted with no recoveries or nothing special. Can I just Remove Greenify, G2Xposed, and Titanium Backup and give it to them to exchange? Can they really not except it? I love this feature and it annoys me to no end that it doesn't work but maybe 20% of the time.
Click to expand...
Click to collapse
.tot back to zvc and return phone. Thats my plan and it unroots phone so no worries.
Sent from my LG-LS980 using XDA Premium 4 mobile app
I posted in several different areas of the forum and no success. Flashed back to stock with ODIN and still had no success so I just took it to the Sprint store and they're ordering me a replacement ???????
Having same issue with the knock on feature working, knock off works fine. I am also on OpTimuS DE 2.3ZVC. It worked, then suddenly stopped working. I even made a nandroid backup, then tried the Dorimanx kernel and the knock on & knock off worked perfectly. Myself i think it an issue with the Furnace kernel, hopefully Savoca will help us out.....
http://forum.xda-developers.com/showthread.php?t=2467302
[VZW] HiddenMenu
Read the entire 7 page thread, and follow directions.
System app this should be with terminal instructions.
This did fix my knock on problem.
Sent from my LG-LS980 using Tapatalk
Sent from my LG-LS980 using Tapatalk
how to fix Knock on
First copy the apk to System/apps fix permission to rw- r- r-
Them reboot
Open dailer and put this. 5689#*980#
Them go to
hw device test/ Touch test/ touch firmware update.
Exit out and done knock on is working
Go back to ZV7
Nothing worked for me and I could't get the option on the menu. I've just went back to ZV7, the menu appeared and Knock On is working again.
secret.animal said:
http://forum.xda-developers.com/showthread.php?t=2467302
[VZW] HiddenMenu
Read the entire 7 page thread, and follow directions.
System app this should be with terminal instructions.
This did fix my knock on problem.
Sent from my LG-LS980 using Tapatalk
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Demo3827 said:
First copy the apk to System/apps fix permission to rw- r- r-
Them reboot
Open dailer and put this. 5689#*980#
Them go to
hw device test/ Touch test/ touch firmware update.
Exit out and done knock on is working
Click to expand...
Click to collapse
This doesn't work for me. I've replaced the HiddenMenu.apk properly, changed permissions, and rebooted. Once into the menu either by terminal or dialer code, there is no HW Device Test option to choose. It's giving me the same hidden menu that Sprint already has. Again, yes, I replaced the apk properly.
Stock rooted ZVC
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wait a second... I'll double check, but I messed up mine one time and got the same menu. Trying to remember what I did to get it fixed.
Sent from my Nexus 7 using Tapatalk
Related
in the past two days my phone has failed to start my camera twice. I opened instagram first and when I tried to take a photo it said "unable to start camera" in tried it again and it said the same thing. So I opened the actual camera and it just opened a black screen with the camera controls (shutter buttons, settings, etc)
No matter how many times I opened the camera or cleared the tasks using the camera it still refused to start. only after restarting the phone did the camera start again.
has anyone else experienced this or know any possible reasons as to why this could be happening???
Sent from my SGH-T999 using Tapatalk 2
Try deleting the data of the camera app, if that doesn't work, try a different ROM, if it still happens, it's a hardware problem.
theexel said:
Try deleting the data of the camera app, if that doesn't work, try a different ROM, if it still happens, it's a hardware problem.
Click to expand...
Click to collapse
ill try that the next time it happens but at the moment I'm completely stock and just rooted.
Sent from my SGH-T999 using Tapatalk 2
I actually had this happen a few times before I rooted or ROM'd. I have yet to have it happen on JellyBean and, if I did, I could just hot boot. The only thing that ever fixed the issue on stock was a restart.
Is it possible this is an issue similar to webcams and PC's where the permissions get messed up? Can you recreate it? Open app x then try to use the camera in app y and see if it's bonkers.
I have been trying everything in order to reproduce the problem, no luck as of yet unfortunately.
Sent from my SGH-T999 using Tapatalk 2
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
I works on the 2/26/13 Nightly of CM10.1. You wanna try and clean flash it? If it doesn't work then it's just a problem with your phone hardware instead of the software. Might be a buddy bluetooth adapter or such.
zxstyle07 said:
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
Click to expand...
Click to collapse
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yup, this helped for my JB-MR build 4!
no more having to reboot to enable bluetooth
wbexpress said:
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Click to expand...
Click to collapse
http:// http://forum.xda-developers.com/showthread.php?t=2158329
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Well, what seems to happen is it is fine for 15-30 minutes after I've freshly installed the ROM, then it just turns off. When I then try to turn it back on it hangs at "turning on" and then goes back to off. At that point when I click "turn on", it doesn't even move. I'm a gonna try the fix, nothing to lose at this point...
Nuts. It fast moves to on and immediately goes back to off. White flag, thanks to all.
Apply the fix and delete all you devices then try turning it on and off with nothing on it...if it works then add devices one by one...if you have devices married to it the patch might not work also I think my computer dongle was the culprit
Sent from my SAMSUNG-SGH-T989 using xda premium
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
wbexpress said:
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
Click to expand...
Click to collapse
Your exactly right...
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
wbexpress said:
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
Click to expand...
Click to collapse
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
bluetooth issues
djtheraven said:
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Not a perfect answer...
RandyToe said:
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Click to expand...
Click to collapse
I found one thing that at least gets it working again without rebooting is to activate airplane mode. Its faster than rebooting. Wish I had a better answer...
Ive searched everywhere and can't seem to find anyone with a solution. Ive found a post with the same problem but no solution.
So yesterday my s3 started having problems waking up. Meaning when I lock it usually you bring up the lock screen by pressing the power button or home button. Problem is when I press either one, screen doesnt come on. The buttons do. If I tap the screen I can hear the ripple effect but the screen doesnt light up. I have to keep locking and unlocking till it finally works. Averege of about 6 tries. When I get a call most of the time the screen doesnt come on either. I can still answer since I know where the slider is. When I do turn it on everything works perfect. No flickering or any other issues. When it boots it works perfect...never fails. Just when I lock it.
I tried restoring already, thinking its a software issue...still does it. What piece of hardware could cause this? I'm stumped. Please any advice would be great.
I'm not rooted and running 4.1.1 oem rogers software.
Sent from my SGH-I747M using xda app-developers app
felcom said:
Ive searched everywhere and can't seem to find anyone with a solution. Ive found a post with the same problem but no solution.
So yesterday my s3 started having problems waking up. Meaning when I lock it usually you bring up the lock screen by pressing the power button or home button. Problem is when I press either one, screen doesnt come on. The buttons do. If I tap the screen I can hear the ripple effect but the screen doesnt light up. I have to keep locking and unlocking till it finally works. Averege of about 6 tries. When I get a call most of the time the screen doesnt come on either. I can still answer since I know where the slider is. When I do turn it on everything works perfect. No flickering or any other issues. When it boots it works perfect...never fails. Just when I lock it.
I tried restoring already, thinking its a software issue...still does it. What piece of hardware could cause this? I'm stumped. Please any advice would be great.
I'm not rooted and running 4.1.1 oem rogers software.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
My guess is that you have something draining all your RAM or being hard on your CPU. When you restored, did you factory reset?
You might have to backup your stuff, factory reset. Test it, if it still does it, bring it up with Rogers for a replacement. If it doesn't, reinstall your stuff until you find the culprit.
You could troubleshoot it also by uninstalling the latest apps you installed.
BWolf56 said:
My guess is that you have something draining all your RAM or being hard on your CPU. When you restored, did you factory reset?
You might have to backup your stuff, factory reset. Test it, if it still does it, bring it up with Rogers for a replacement. If it doesn't, reinstall your stuff until you find the culprit.
You could troubleshoot it also by uninstalling the latest apps you installed.
Click to expand...
Click to collapse
Like I said...Already did a factory reset. Meaning All apps were gone. Started fresh. Even without going through the first setup (setting up google account etc etc) if I lock the phone its hard to wakeup.
Phone is out of warranty so no go there....
I'm just not understanding what is causing it. I know the screen is fine...buttons are fine...everything points at a software problem. I found a post from a while back where someone was having the same problem....no solution was posted though. I even took the phone apart last night thinking a bad connection or something...disconnected the screen and reconnected it...didn't do anything.
If the screen was going bad wouldn't I have issues all the time? Once I wakeup the phone it works perfect...no flickering or anything. When it boots (which I've done like 30 times between today and yesterday) the screen has come on every single time perfectly fine. Everything tells me it's software related...but after doing a factory reset and running original firmware it seems as though it must be a hardware issue...but which component.
I know the phone wakes up when I press the buttons...I can see the menu and back buttons light up...and if I tap the screen the ripple sound is there...just the screen doesn't wake up....till I try a few more times....very frustrating.
Thanks Again for trying...if anyone has any ideas....greatly appreciated. I'll try and find original Rogers firmware and install with odin...see if that works....
felcom said:
Like I said...Already did a factory reset. Meaning All apps were gone. Started fresh. Even without going through the first setup (setting up google account etc etc) if I lock the phone its hard to wakeup.
Phone is out of warranty so no go there....
I'm just not understanding what is causing it. I know the screen is fine...buttons are fine...everything points at a software problem. I found a post from a while back where someone was having the same problem....no solution was posted though. I even took the phone apart last night thinking a bad connection or something...disconnected the screen and reconnected it...didn't do anything.
If the screen was going bad wouldn't I have issues all the time? Once I wakeup the phone it works perfect...no flickering or anything. When it boots (which I've done like 30 times between today and yesterday) the screen has come on every single time perfectly fine. Everything tells me it's software related...but after doing a factory reset and running original firmware it seems as though it must be a hardware issue...but which component.
I know the phone wakes up when I press the buttons...I can see the menu and back buttons light up...and if I tap the screen the ripple sound is there...just the screen doesn't wake up....till I try a few more times....very frustrating.
Thanks Again for trying...if anyone has any ideas....greatly appreciated. I'll try and find original Rogers firmware and install with odin...see if that works....
Click to expand...
Click to collapse
Sounds indeed like software issue. I'm not so sure what would cause it on stock rogers though.
Either way, you can find the stock ROM on sammobile.com or on this thread: http://forum.xda-developers.com/showthread.php?t=1822308
You'll need Odin to flash it. (It doesn't trigger the flash counter)
felcom said:
Phone is out of warranty so no go there....
Click to expand...
Click to collapse
Did you buy your phone with a credit card? Some cc's have warranty built in. Mine doubles what the manufacturer offers.
Thanks for the link. I will try it tonight and post the results. Really hoping it works.
Sent from my SGH-I747M using xda app-developers app
I downloaded the newest firmware. 4.1.2 official rogers. Problem persists. Must be a hardware issue. Thing is what could cause this? Is it the screen...is it the gpu? I imagine if its gpu the phone is only good for parts as I imagine its part of the motherboard. Oh well...might be getting the s4 sooner then planned.
Sent from my SGH-I747M using xda app-developers app
felcom said:
I downloaded the newest firmware. 4.1.2 official rogers. Problem persists. Must be a hardware issue. Thing is what could cause this? Is it the screen...is it the gpu? I imagine if its gpu the phone is only good for parts as I imagine its part of the motherboard. Oh well...might be getting the s4 sooner then planned.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
If you're down for a little test, you could try with a custom ROM.
Use the link I gave you and flash pre-rooted Rogers' ROM. From there, install TWRP (or cwm) using goomanager (from the Play Store) and flash a custom ROM as per their instructions (Don't forget the Gapps).
Before anything though, make a backup
Never know, might save you some time on that S4.
BWolf56 said:
If you're down for a little test, you could try with a custom ROM.
Use the link I gave you and flash pre-rooted Rogers' ROM. From there, install TWRP (or cwm) using goomanager (from the Play Store) and flash a custom ROM as per their instructions (Don't forget the Gapps).
Before anything though, make a backup
Never know, might save you some time on that S4.
Click to expand...
Click to collapse
Thanks. I might try it. Dont think I have too much to lose at this point. I always try and keep my phones nice so that when I get a new one I can sell the old one for good money to help offset the cost. This really messes with that system as the phone isn't worth much now...just bought an extended battery too...was planning to keep it for at least another 6 months.
Sent from my SGH-I747M using xda app-developers app
So just a quick update. For no apparent reason the phone started working fine again. It now turns on and off just fine. I'm not going to mess around with it anymore. That's really bizzare. I'll give it a couple days and will report back if it continuous to work fine or if the problem comes back. Thanks for the input.
Sent from my SGH-I747M using xda app-developers app
Since I soft bricked and then restored my phone I have been having a couple issues. The first is that my service just drops for no reason, and I only get it back from restarting the device. The second is whenever I turn my phone on, it tells me that gapps has stopped working. Should I be concerned /is there fix?
Sent from my LG-LS980 using xda app-developers app
eddytheyeti2 said:
Since I soft bricked and then restored my phone I have been having a couple issues. The first is that my service just drops for no reason, and I only get it back from restarting the device. The second is whenever I turn my phone on, it tells me that gapps has stopped working. Should I be concerned /is there fix?
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Flash the ZVC.tot, maybe something got corrupted. Did you edit the build.prop? The G2 build.prop is too big for some apps and when you edit they truncate it, giving the effects you have. I use RootExplorer and at least it gives me a warning that it will truncate the build.prop as its too big. If thats the case, next time use a build.prop editor or edit on desktop and replace original setting permissions back to rw-r-r.
I've had my G3 for over a month now without many issues, however yesterday evening my phone randomly rebooted itself, and ever since reboots every few minutes, often when I unlock my phone or shortly after. I have booted in to safe mode, and reflashed both the latest i and j firmware updates but no success.
Any ideas or anything I can try to dig in to the issue further?
By any chance did you enable ART runtime in settings? Otherwise maybe you have a corrupt sdcard.
Did you try booting into recovery to delete the cache? All else fails, you might need to factory reset.
alondero said:
I've had my G3 for over a month now without many issues, however yesterday evening my phone randomly rebooted itself, and ever since reboots every few minutes, often when I unlock my phone or shortly after. I have booted in to safe mode, and reflashed both the latest i and j firmware updates but no success.
Any ideas or anything I can try to dig in to the issue further?
Click to expand...
Click to collapse
Its probably due to either overheating or you messed with something in the build.prop.
First is your phone rooted? If it is then did you do anything system-wise? (Xposed framework or edit the build.prop or attempt to "flash" something)?
Sent from my LG-D852 using Tapatalk
Colchiro said:
By any chance did you enable ART runtime in settings? Otherwise maybe you have a corrupt sdcard.
Did you try booting into recovery to delete the cache? All else fails, you might need to factory reset.
Click to expand...
Click to collapse
Thanks, unfortunately I'm still on Dalvik, and have removed my sdcard to try and remove another piece from the puzzle. I've factory reset and also flashed both an i and a j kdz using LGFlashTool2014.
Is it worth me following the guide here http://forum.xda-developers.com/showthread.php?t=2475045 or is the LGFlashTool2014 the same thing?
Helloworld294 said:
Its probably due to either overheating or you messed with something in the build.prop.
First is your phone rooted? If it is then did you do anything system-wise? (Xposed framework or edit the build.prop or attempt to "flash" something)?
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
I've had Xposed installed with a few modules since I first had the phone, and hadn't added any new modules recently, although I guess possibly one of them may have updated. I've since done a factory reset and flashed however so can no longer check. Would I be right to assume the re-flash would have put everything back in a stock state?
alondero said:
I've had Xposed installed with a few modules since I first had the phone, and hadn't added any new modules recently, although I guess possibly one of them may have updated. I've since done a factory reset and flashed however so can no longer check. Would I be right to assume the re-flash would have put everything back in a stock state?
Click to expand...
Click to collapse
Reflash puts everything the way it was when you first took the phone off the box with the excitement and love.
Sent from my LG-D852 using Tapatalk
Xposed causes my LG to reboot every few minutes, so it could be that.
Just for extra info...I had an optimus g pro and the same thing was happening...I sent it in for repair...but that didn't fix the problem...here is what fixed it from rebooting...I replaced the battery...yep it was the battery causing it...put the old one in and it started rebooting again...put the new one in again and no reboots...don't know if this will help you but it's what happened to me
Sent from my LG-D850 using XDA Free mobile app
MythicBlue said:
Just for extra info...I had an optimus g pro and the same thing was happening...I sent it in for repair...but that didn't fix the problem...here is what fixed it from rebooting...I replaced the battery...yep it was the battery causing it...put the old one in and it started rebooting again...put the new one in again and no reboots...don't know if this will help you but it's what happened to me
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Na man its all about the lightbulb in your room, replace that and the reboots will stop.
Sent from my LG-D852 using Tapatalk
MythicBlue said:
Just for extra info...I had an optimus g pro and the same thing was happening...I sent it in for repair...but that didn't fix the problem...here is what fixed it from rebooting...I replaced the battery...yep it was the battery causing it...put the old one in and it started rebooting again...put the new one in again and no reboots...don't know if this will help you but it's what happened to me
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Really? Seems far fetched, but I'm willing to try anything now! I'll test with a colleagues battery tomorrow and let you know how I get on!
alondero said:
Really? Seems far fetched, but I'm willing to try anything now! I'll test with a colleagues battery tomorrow and let you know how I get on!
Click to expand...
Click to collapse
Unfortunately that didn't work either. Looks like it'll have to go back for repair.
As a last gasp attempt to see if anyone else has any thoughts, I've noticed the following message in the logcat near when the phone restarts itselfL
[ 09-24 20:49:38.359 331: 331 E/ThermalEngine ]
out low battery limit.
Click to expand...
Click to collapse
I can't find anything online but I wonder if the phone is thinking it is overheating and therefore restarting? The device feels cold to the touch so I don't think it is actually overheating
Sounds like one of the chips is overheating. Maybe not be seating with the heatsink or whatever is supposed to help it keep cool. Ide take it back and get a replacement.
Helloworld294 said:
Na man its all about the lightbulb in your room, replace that and the reboots will stop.
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
Man the guy is having issues with his phone and ur making fun of it?? Dont you have anything better to do?? Put yourself in his position before u say anything idiot !!
mustang2012 said:
Man the guy is having issues with his phone and ur making fun of it?? Dont you have anything better to do?? Put yourself in his position before u say anything idiot !!
Click to expand...
Click to collapse
Wow I guess its someone's time of the month.
Sent from my LG-D852 using Tapatalk
Interesting development, I flashed the Deviant CM11 AOSP rom on to it (using Tethered TWRP) and whilst it couldn't do much it lasted a whole day without rebooting. Unfortunately flashing the stock firmware or any other kdz back to the device causes the rebooting again. I'm still suspecting it could be a thermal issue, the phone wasn't exactly being stressed on Deviant.