4.3 update causes strange glitch
Hello,
I'm somewhat new to the rooting world of Android but when I got my Note 2 last year the first thing I did was root it and unlock the bootloader, and kept that through the 4.1.2 (if I recall correctly) update. I knew I wasn't getting 4.2 and jumping straight to 4.3 as was Verizon's plan. I waited patiently and forgot about it entirely, so a couple of days ago I found the stock rooted deodex rom located here. I thought I had made the correct decision, it seemed to be for my phone, it flashed with no issues (both the rom and firmware) and runs fine except for one flaw which has proven to be a pain due to it cancelling my alarm every morning.
Whenever the lock screen comes up, the phone things a touch happens right in the middle of the screen. Nothing's there, but it doesn't matter what happens, I push the power button, plug its charger into it, it will always send out that one little ripple and as a result it cancels my alarm. I looked through the thread, I appear to be the only one with this issue.
Any recommendations?
Related
Hey guys, this is my first post on XDA as I'm usually lurking or keeping up with updates. I've searched many forums for an answer to my problem but it does not seem that anyone has had the same issue.
Anyway, lately I've run into the problem of an unresponsive touchscreen. I can't even unlock my phone! Two nights ago I made three consecutive calls and about ten minutes later I couldn't unlock my phone.
In order to correct this problem, I first took off the screen protector to no avail. I was running CM7, flashed a sense ROM, flashed my backup of the stock ROM, went back to stock with S-ON, pulled the battery a bunch of times, completely wiped, removed the SD card, Soft & hard reset at a VZW store. Nothing.
Took it with me to school today, powered it on and before it completely loaded I was able to unlock it by chance, skipped the setup and it was working fine all day. I was hella overjoyed... until it did it again tonight. D: I so want it to be OS issues rather than hardware because I don't want to wait two days to get a 'reconditioned' TB from VZW.
HALP! Please? Thanks, guys for even looking!
MP
P.S. I do apologize if I did not follow proper procedure to post or posted in the wrong subforum. S:
I'm frustrated and sitting around with an unrooted TB, ohnoes. (Although the screen looks sexy as hell without a screen protector.)
moneecuh said:
Hey guys, this is my first post on XDA as I'm usually lurking or keeping up with updates. I've searched many forums for an answer to my problem but it does not seem that anyone has had the same issue.
Anyway, lately I've run into the problem of an unresponsive touchscreen. I can't even unlock my phone! Two nights ago I made three consecutive calls and about ten minutes later I couldn't unlock my phone.
In order to correct this problem, I first took off the screen protector to no avail. I was running CM7, flashed a sense ROM, flashed my backup of the stock ROM, went back to stock with S-ON, pulled the battery a bunch of times, completely wiped, removed the SD card, Soft & hard reset at a VZW store. Nothing.
Took it with me to school today, powered it on and before it completely loaded I was able to unlock it by chance, skipped the setup and it was working fine all day. I was hella overjoyed... until it did it again tonight. D: I so want it to be OS issues rather than hardware because I don't want to wait two days to get a 'reconditioned' TB from VZW.
HALP! Please? Thanks, guys for even looking!
MP
P.S. I do apologize if I did not follow proper procedure to post or posted in the wrong subforum. S:
I'm frustrated and sitting around with an unrooted TB, ohnoes. (Although the screen looks sexy as hell without a screen protector.)
Click to expand...
Click to collapse
sounds like it could be a digitizer(hardware related) issue. on the plus side, you can pickup a new digitizer pretty cheap... downside though is you'd have to open up the phone to replace it. it's not that hard to do and there's videos online showing you how to.. you'd just have to be comfortable i suppose.
i'd just fix it rather then going the refurbished route considering that god know's what was wrong with it before it became "refurbished" not to mention you have no idea how much use the phone had been put through and how much life it has left.
Hi;
I apologies in advance for the long thread, but I want other users to notice the symptoms I faced maybe someone else will benefit from it.important parts are marked in blue
MY galaxy s3 is only 4 months old....I got tempted by rooting and getting all -other- features such as fast recharging, sound hack, trying new roms before they are officially released...etc
anyhow, my phone's troubles showed strange symptoms quite shortly after the second rom being installed....
at first I was not fully aware of the required rooting steps, until I use the galaxy toolbox that rooted my phone easily for me...
then I started noticing the phone would start and everything but noticed (root user notices) take time to show up after boot, it would take approx. 1min then they will show very fast...after that everything is normal so i figured the processor is a little bit loaded...
few weeks later I started using CWM's backup &restore feature , noticed that when I go back to the official Rom, it lags, a lot! , I have to restart the phone at some points because it will stop responding...I started checking processor load and was surprised to see normal non harmful rates...so I forced apps to be closed once I exit them.
few roms and flashings later, the phone started restarting it self randomly,like an old car heating up, it would restart few times then get back to normal state....this would happen whenever i try to change anything in the rom (CM10+nightlies build)
few days ago, whenever the phone received or made a notification sound, I would pick it up and find it turned off! I turned on again and use it normally , no issues....after this happening for 2 times, the phone just died ...PIT partition is non-readable/writable anymore :crying:
I noticed the night this thing happened that, when I restored the rom, it took a longer time, and something was not found but the rom booted normally....
now my phone is in service and they are overloaded with service-warranty requests, so they haven't checked it yet (it has been there for 3-4 days)..I used traingle away on the current rom, no flash counter appears and the binary is official, but the rom appears as custom
notes:
*from the beginning, every step I made was a trial and error to me, I tried rooting once (manually) and I didn't figure it out,until i saw the toolbox that made it easy,,,the first root was amazing, but I rooted again after rom crashed and seems I used a different root that started all that trouble.
*All the mentioned above I believe were symptoms, that I didn't care about since the phone was acting normally after those occurring..I think I should've spotted them earlier.
*There have been 2 overheating incidents, one happened when I forgot the phone in my pants and by mistake i ticked "load new videos from subscriptions in youtube and the phone sucked up around 3gbs that day...it was really really hot when I got back to it.....the other one was when I went to sleep few days ago, I put it under my pillow, woke up with the phone overheated and restarting continuously "might've been doing this all overnight!"
*I insisted -although it was clearly troublesome to my phone- on installing Siyah kernal on every rom "always the latest one", sometimes the phone would keep restarting and I would have to restore a previous rom, sometimes it would go without issues, this happened more oftentimes during the last few weeks and CM10 nightlies offers dialy updates and I had to flash siyah back after every update...now I'm writing it and feeling stupid!
*Official JB roms caused the phone to hang a lot, so I kept using CM10+siyah kernel till the last moment.
now, what I would like to know is:
1- why does that chip get affected?? I never flashed a 3/4 part rom, just using CWM....
2- I decided (if) the phone gets fixed on warranty, to not to root again, I'm having a million guesses as the reason why this happened, including the fast recharging, the continuous flashings and testing (although all are stable roms, only official and CM10 roms), the overheating incidents....etc....I would like to know what you guys think.
If you had read the faqs and guides first you would not have the trouble .
Like
at first I was not fully aware of the required rooting steps
from the beginning, every step I made was a trial and error to me
I tried rooting once (manually) and I didn't figure it out,
>> basic CF Root is simple as it gets .
jje
So I've had a S3 for about 6 months by now, and at first, it was running pretty smoothly. Few weeks ago (might even be a month by now) the JB update came out for my phone, so I installed that. Over the past two or so weeks, my phone has been laggy as hell, including random resets. I get a few restarts which the phone does itself, without any input from me. I'm also getting a serious lag whenever I'm attempting to type a message. I'll be able to type my whole message out, but it hasn't shown up on the screen (so the phone's manage to register the touch prompts I make, it just shows them on a 5-10 second delay). This occurs even when the only app I'm running is the messaging one. Further lag issues include receiving messages. My phone will vibrate, then some 5 seconds or so later the message will finally be received by the phone and my ringtone goes off.
I've tried doing a hard reset on the phone, and that hasn't changed anything. Could it be hardware related?
And I'm currently running the stock Aus unbranded ROM, unrooted, no mods (XSADLK3 I think)
I had this issue on my sgs2 when upgraded to ics, only fix at the time was to take back to my carrier for a re flash (they told me if I flashed it myself I'd void the warranty). Dunno if that helps at all.
It could be. Try updating to the latest JB firmware first though.
jimbo1531 said:
I had this issue on my sgs2 when upgraded to ics, only fix at the time was to take back to my carrier for a re flash (they told me if I flashed it myself I'd void the warranty). Dunno if that helps at all.
Click to expand...
Click to collapse
Well, I called up Samsung support earlier, and the guy kept suggesting I just restore the phone. Which I had already done at that point. And the carrier I'm on doesn't have a store where I live, I'd have to mail it back to them, have their guys take a look at it and either can my contract or send me a new one
First off, I'd like to say my S2 is the Virgin Mobile version (model i9210) so I'm not sure if it's okay for me to post this in this forum or not. Feel free to move it where it should be, I won't be offended.
Edit: Originally had posted this in the Samsung Galaxy S2 forum, but it was nicely moved to this forum in hopes that it would be seen more~ So to clarify, my phone is the Virgin Mobile Samsung Galaxy S2, running Android 4.1.2, model number SPH-D710.
The ROM I have is BiftorROM-V8-JB-XWLSN-NoWipe.
Onward. This is my first Samsung phone AND my first Galaxy, and when I decided to root my phone, I had no idea how much different it would be from my past phones. How I didn't completely brick this phone, is nothing short of a miracle. I had trouble with some ROMs so someone eventually linked me to a Sprint stock ROM, saying it was compatible with my phone.
Since then I've been using that ROM, despite having a Virgin Mobile phone, with no problem. Recently I noticed an app I use (SD Maid) was listing my phone as unrooted. It was weird but I ignored it, because the app still worked. Even later, I noticed other apps that require root access were not working correctly, so I decided to download a root checker.
Status: Unrooted
Well, then. I'm not sure how this happened, or what's going on, but I figured again, it was no big deal because my ROM was running perfectly and I had no desire to change my ROM or anything else soon. Last night my phone started acting completely different. Lagging like crazy, and when I tried to unlock my phone, it would take a good 15 seconds just for the screen to turn on and my lock screen to start functioning normally. Then another 20 seconds or so for the screen to register my touch and actually unlock my phone. I tried disabling all lockers, but my screen would just turn black and I would still have to wait.
A friend suggested that I simply go through the process of rooting as though my phone really were unrooted and just hope that fixes it, but I'm not sure if that would be a good idea. If my phone wasn't operating so slowly this wouldn't be as big of a problem, but it is, and I'm pretty afraid that I'll mess my phone up somehow.
I once found a forum with the topic the same as mine but I haven't been able to find it since, so I'm hoping someone here could point me in the right direction. Do I go through the root process, maybe try just reflashing my current ROM? I've also thought about just doing a system restore on my phone and see if that helps. Thanks in advance.
Hello:
So, the bottom line up front is I need help solving a problem with my now third, new Verizon Samsung Galaxy S4--it keeps restarting on its own, at random times, but most often after I lock the screen.
To go in more depth, if you think you may know the solution: I purchased the S4 when it first came out, some time in 2013 (not sure specifically, but it was new) and it worked just fine for 13 months (1 month past the warranty of course); this was back in August, when I got the latest Android update pushed to my phone from Verizon (4.4.2). A couple of weeks later, I would occasionally get overheating warnings that would very quickly disappear (like within a few seconds), and then the device started restarting itself... I cannot predict when it will restart, it's random, but like I said above, it usually happens most right after I lock the screen by pressing the right side button once. I started looking around on the internet for a solution then, but only found a couple of videos from earlier in 2013 where people were having battery problems (Google search has been letting me down more and more as the years pass). One day while at work, I was listening to Pandora as I always have with the phone in my front pocket, as I always have. A few hours later when I got home, not having taken the phone out of my front pocket since those last few hours at work, I went to answer a text message I had received; when I unlocked the phone, the screen was black, except for a small bit of white showing through some cracks UNDER the LCD, UNDER the screen protector, INSIDE my Otterbox Defender... the phone appeared to be working still, but the screen and touch screen did not. At that point I was pretty damn irritated and tried to find answers for a week with no luck... I called Verizon, they sent me on a goose chase to Samsung, who sent me back to Verizon, who got me in a conference call with Samsung and then left the call, and then Samsung ultimately said I would need to pay for repairs to the phone... SO... I went back to Verizon who again said I would have to talk to Samsung, but instead I just settled to giving Asurion (my phone insurance through Verizon, whom I pay an extra $9 monthly) $99 as a deductible to get a replacement S4...
Two days later I receive a brand new S4... spend hours setting it up the way I had my prior one... wasting tons of my valueable time to do so and bandwidth from my Concast ISP and the data cap they've decided to give us... one week later, the phone starts restarting itself... and this one did it more often than my prior one... EVERYTHING is up to date, minus a good amount of useless bloatware apps I never use from Samsung, like "Watch On," which I ignore... but everything necessary, I update. So, I go back to Asurion, who quickly ships me a 3rd S4...
Two days later I receive that third, brand new S4... spend hours setting it up the way I had my prior one... and now, this one is also restarting itself randomly. Interestingly, when I visited family for Thanksgiving, it restarted itself over and over and over much more frequently than when I'm at my place... at my family's place, they have very poor reception, and my phone usually has to work more to try to get the signal... IDK what the deal is, but maybe that information can be helpful to y'all.
Other things to note:
1) When I check the "RAM manager" by holding down the home button and then choosing "Task Manager", the phone is always using at least 800MB of 1.77GB of RAM... even when I choose "Clear memory" and it tells me 30 something apps have been closed... it jumps right back up to 800-900MB of usage.
2) I've tried factory resets on all three phones; with the first one where the screen cracked inside, I hooked the phone up via HDMI... within a couple of days, the restarting begins.
3) With the first replacement I received, I could not sent text messages with the default messenger app... and shortly after trying, it would restart.
4) I have used the same SIM card with all three phones since the issue began, when I first got the 4.2.2 update... I do not suspect the SIM card is the problem, but I'm also not savy with the phone... I know my way around it, but I'm not in the know.
5) I thought maybe it started because of some apps I had been trying, so I had deleted them, and the problem still persists.
6) I constantly have a Pebble Bluetooth smart watch connected to the phone... I have since I got it last Spring (2014).
7) I have never rooted the S4, overclocked it, underclocked it, or modded it in anyway because I do not know how, and I was afraid of what could happen in the future with whatever ROM I did flash onto the device if Verizon tried to push an update to it... I just don't know anything about the whole process, and I'm assuming it requires a lot of know how and babysitting of the device... I just want it to work.
8) I've replaced the battery twice; it doesn't seem to be the problem.
9) I've cleared the cache through the boot manager thing gotten to by holding a combo of buttons on the device while it's rebooting... it did not help.
Edit: 10) Today while I was listening to Pandora in the car, the audio began to skip and scratch, and then it paused for a moment, and then the phone restarted itself.
11) I forgot to mention that the reboot process itself is very fast compared to a manual restart performed by me... the phone will go black, the Samsung color rings will show a second after that, the logo appears then, the screen flashes the red Verizon logo, and then the devices is ready to be used... it's less than 10 seconds.
I've been searching around on the internet for about two months now while dealing with the problem and I can't find anything useful. Does anyone here know what my issue is and how I can fix it? Is there a way to pull error logs / information from the S4 somehow to give to someone to diagnose, like DxDiags on PC? I don't know how to read that stuff myself, but I know it can be very useful... I just don't know how to find that info inside of these very locked down ****boxes we call smartphones...
I truly appreciate any help I can get--sorry I can't offer anything in return; if I can't find a solution, I'm just going to go to my backup phone from 2011 (Droid X), and I will definitely never purchase another Samsung device, especially after they blamed me as the cause of the problem without even seeing the phone...
Thanks.
The problem is with the NG6 software build, and "probably" not with your phone. Go to Settings>About Phone> and see what Baseband Version is on your phone. If the last 3 letters are NG6, that's probably the problem. There is a new OTA update (as of 12/1).....Baseband Version ending in NK1, which corrects the rebooting problem. Either install the new update, or go back to the NC5 baseband version and that should solve your problem. Both NK1 and NC5 can be rooted if you desire.