Related
Sure the phone has a big screen. Yes it's easier to see things than my Wifes Dinc. No I dont think it is worth it, lets review.
All these issues/problems? happen rooted or not, or rooted without removing Bloat.
Rooted with Following Bloatware removed,
Blockbuster
City ID
Amazon
Youtube
3G hotspot
NFS
Issues........
Keyboard puts period in instead of space when typing, especially when typing fast. Had all features turned off like spell check, etc. Got so bad it would put a period in when I hit the H key or something, and I had to type real slow. Then there would be a delay in typing. I would start typing away and there would be no animation or...typing in the text box, then it would seem like the phone woke up and all of a sudden an entire sentence shows up.
Screen would not recognize touch. Could not unlock phone, could not scroll, if my finger got close to the screen it would select something and open it, but not scroll. Even though I was not touching screen. At times No response. Cleaned screen, cleaned hands. Tried clean hands, dirty hands, sweaty , etc. all same results.
Extreme slow response time. I would unlock phone, select app drawer, it would take 20 seconds before the app drawer would open, or if an app would open, or if the cursor would let me start typing, I had gone through 2 days of dealing with that BS.
Speaker. Oh this one is good...
So one day I notice the phone vibrates, yet no audio. So I check the volume, yup its up, check settings, ok all good. So I decide to play a song, its playing but just next to nothing for volume. I fiddle a bit and said Eff it, I reboot the phone. Audio is back to normal. Seems every 2 days or so I need to reboot the phone so I can hear any audio from speaker.
Random Lock ups.....
BT drops and then phone shows speakerphone button highlighted and BT button highlighted yet no audio from phone call from either BT or Speakerphone.
Unrooted bone stock with only a few apps on phone,
Same **** mentioned above.
Im tired of this. Can someone tell me what I need to do to have a stable Dx?.
Currently the phone is not rooted, and I am still experiencing issues.
I have documented these issues with the Big V as they happen, but have not done anything but order one for my wife gee looking forward to that mess, she loves to load up the apps.......
Try wiping your cache partition from recovery mode. If that doesn't work you can use the now available sbf to get your X back to factory. Now leave the bloatware alone and root again.
I agree with TF. try wiping the phone (I would suggest complete flash if possible) and see if same stuff happens.
I think you may have a bad phone. If the software reset doesn't fix it, See if VZW will exchange it. I've not had any of the problems you describe. And the fact that you are having screen/touch issues, and there was a small batch of phones with screen problems, tells me you may be one of the "lucky:
Don't have much to say, i've only had one reboot and that was bc of rogue app and i had on complete freeze but my battery was less than 10% while actually on this forum, other than that it has been smooth as butter for the most part. I came from the DInc and wouldn't switch back for anything
sent from Shawn Micheals...The heartbreak Kid
I forogt to mention I did unroot, then wipe, then left it stock, still have same issues.
oldmacnut said:
I forogt to mention I did unroot, then wipe, then left it stock, still have same issues.
Click to expand...
Click to collapse
Unfortunately, wiping (factory Reset) doesn't completely restore all of the files. As evidenced by other threads where people changed/removed some APK's and were left in a boot loop when they did a reset.
I'm still leaning towards you having a bad piece of hardware, but it would be better to rule out the software environment first. Thus, it may be worth learning how to flash the new SBF file. That should truly put your phone back in 'out of the box' condition.
To get outta the box you need to use the .sbf file then factory reset. Just using the.sbf leaves all apps and data. Have done .sbf from linux and windows with no problems.remember to *228 option 1 after to reactivate. Would give this a try then bring in for warranty if it doesn't solve it
Sent from my DROIDX using XDA App
you def have a bad phone...exchange it.
I've never had any of these problems, except for the ****ty speaker.
There is as 17+ page thread on Motos forum about the rebooting issue. I just jumped ship from Verizon and went with Sprint.
I could of handled the phone issues and waited for the 2.2 update, however working for Verizon I was in awe of the ****ty service by one particular Verizon store. On a Evo now with 2.2
Yes my phone is a beast. Much more so than the evo. I owned the DInc so yes i know EXACTLY how the evo runs. I definitely think there was an initial bad batch that went out, just like every other phone, evo and dinc, and iphone, and all the galaxy phones that went out. Im in love with this phone
sent from Shawn Micheals...The heartbreak Kid
mine works fine
Mine runs like a champ, get yours exchanged before the 30 days runs out. Simple and easy fix.
Mine is rock solid... works great... this should be a comfort to you... since all you have to do is exchange it for another one.. then you should be good!
Loving mine, glad I waited several weeks to jump on it, after the screen issues, speaker issues, I ended up getting a flawless device, speaker isnt like my tp2, but I havent missed any calls or had any issues hearing it like many others. After being burned time after time, think im gonna wait on pulling the trigger on every phone I get from now on!
this phone is definitely a beast, love it, coming from a Dinc, i have to say the X blows it out the water...
you may have a bad phone...
did u experience the issues you listed prior to rooting? if no, then theres your answer and follow the advice listed earlier about flashing the phone back
You're not by chance running a task killer set to kill everything are you?
First let me say thank you to everyone who makes this place such an awesome resource. I'm sure I'm not the only lurker who feels a ton of gratitude and appreciation for all the time and effort shared here!
Because of that gratitude I just wanted to register and post this in the hope that it'd help someone else in the same position.
I was hesitant to root my vibrant because I'm really not in a position to replace it if I managed to destroy it in the process, but finally 2 days ago I gave in and did the one click root plus clockwork recovery process so that I could use barnacle wifi tether. Of course 2 days later this official over the air update gets pushed through, immediately filling me with dread.
I assumed it was froyo finally but did some reading first, mostly here; and while it was not the much anticipated 2.2 it still sounded like something I'd want to have. Plus there seems to be no simple way to get rid of the update nag in the notification bar unless you update.
So I went ahead and risked it. And I'm happy to say that despite a horrifyingly long pause at the galaxy s screen, the update went thru perfectly using just the official push delivery method, not Odin or anything but the stock delivery method.
Now I have media hub, the gps fix, my signal bars seem to finally be working right and maybe I'm fantasizing but the whole phone feels faster; and I didn't even lose root.
Anyway, I hope this helps someone who like me only rooted and clockworked for wifi tether.
I wasn't so luckly. I undid my lag fix and un rooted and still soft bricked mine and had to use odin to get it back
how long
HumanTarget said:
First let me say thank you to everyone who makes this place such an awesome resource. I'm sure I'm not the only lurker who feels a ton of gratitude and appreciation for all the time and effort shared here!
Because of that gratitude I just wanted to register and post this in the hope that it'd help someone else in the same position.
I was hesitant to root my vibrant because I'm really not in a position to replace it if I managed to destroy it in the process, but finally 2 days ago I gave in and did the one click root plus clockwork recovery process so that I could use barnacle wifi tether. Of course 2 days later this official over the air update gets pushed through, immediately filling me with dread.
I assumed it was froyo finally but did some reading first, mostly here; and while it was not the much anticipated 2.2 it still sounded like something I'd want to have. Plus there seems to be no simple way to get rid of the update nag in the notification bar unless you update.
So I went ahead and risked it. And I'm happy to say that despite a horrifyingly long pause at the galaxy s screen, the update went thru perfectly using just the official push delivery method, not Odin or anything but the stock delivery method.
Now I have media hub, the gps fix, my signal bars seem to finally be working right and maybe I'm fantasizing but the whole phone feels faster; and I didn't even lose root.
Anyway, I hope this helps someone who like me only rooted and clockworked for wifi tether.
Click to expand...
Click to collapse
thats great to hear since I'm rooted and i just installed ROM Manager/Clockwork in order to make a nandroid backup. Now Im wondering whether i should wait for the OTA to hit my phone or if I should use Kies Mini to do it manually over USB. In either case, could you please answer one question...how long did it stay at the galaxy s screen?
Becuase some people are saying it stayed on it for an hour and assuming they're soft bricked but if it really takes 1 hour and 2 minutes than that extra bit of patience is needed...
jblade1000 said:
thats great to hear since I'm rooted and i just installed ROM Manager/Clockwork in order to make a nandroid backup. Now Im wondering whether i should wait for the OTA to hit my phone or if I should use Kies Mini to do it manually over USB. In either case, could you please answer one question...how long did it stay at the galaxy s screen?
Becuase some people are saying it stayed on it for an hour and assuming they're soft bricked but if it really takes 1 hour and 2 minutes than that extra bit of patience is needed...
Click to expand...
Click to collapse
took about 3-6 minutes for me.
I got very worried... but was patient.
Stock ROM
Rooted
All bloatware removed.
wasted mine with no lag fix rooted on stock kernel, stock build..had to odin back and update via odin...****ty
well damn, im kinda at a loss then about whether to go through with this. I want the update but I dont have the time to be messing with flashing and odin right now...
Weirdddddddd
I to bricked my phone with the ota. I was rooted, stock rom, lagfix with clockwork. I undid the lagfix but still bricked. My boy's running the same without clockwork (never had time to put it on). Unrooted, delaged and removed the update.zip that was on the phone from root and cleared the cache. Ota worked without a problem. Some believe it is the result of an update.zip left on the sd which causes the problem.
Hi there,
I bought my Galaxy Note one month ago and in the first weeks I never had any problems with it, but recently it crashes more and more often. A week ago, while I was still on stock rom (unrooted), it crashed 5 times at one day. I did nothing that could be a problem for it, I was sketching (Autodesk SketchbookMobile), browsing, playing games etc.
I thought it may be the best to try a custom Rom, so I rooted my Note and flashed RocketRom v20. But soon after that the same problem appeared, and besides that, I needed after every crash more than 10 trys to successfully start the phone, somestimes it stuck at the "Samsung Galaxy Note" logo, sometimes it even accomplished it to get to the PIN-input, but crashed at it.
Yesterday I flashed RocketRom v21, but nothing changed.
The only thread about crashes I found in this forum says it may be because of S-Memo, but I barely use it, and never had problems while using it.
Right now I'm holding my Note in my Hand and try to start it, it's attempt 30 or so. I really love the Galaxy Note, but this makes it hard to use for me.
I appreciate every attempt to help me.
seems like manufacturing defect. If you are able to enter download mode, then flash Stock ROM which is latest for your region. then go for a replacement.
A few minutes ago I wasn't even able to get to downloadmode or to charge the phone, but after I plugged it in and out a few times I somehow managed it to get to download mode. I flashed the stock Rom, but the phone again stucked at the "Galaxy Note"-Logo the first two attempts to start it, now, again, it shows no reaction.
It seems like I have no other choice then to send it back
Sounds like a hardware defect with the internal NAND that might be accounting for the random freeze/reboots. Bad RAM can also do this.
Bad/ Corrupted sectors can do that. Lawl.
Also, list all apps that you've installde from the market. There might be some conflicting processes that's causing the phone to hang.
And first to be sur take your sdcard out, and test sometime bad/defective sdcard can also have dramatic effect.
It's already on it's way to Amazon.
I tried starting it without the sd-card, but that didn't help.
I hope it doesn't take too long, because i can't handle the tiny screen of my Samsung Wave anymore.
You are not the only one with this problem. Mine also started crashing/turning off randomly after approx 1 month of buying. Again on stock rom unrooted and very few apps installed.
Starting to think that just maybe samsung have tried to push the boat out too far by releasing this device. Don't get me wrong I love it (when it works) but it just seems too buggy atm. And I don't think ICS will cure all these problems we are all having. I know every device has a small percentage of faulty products but it seems that the note has a high percentage of those.
Sorry to be so negative but when you spend 600 euros on a phone you expect it to work for more than a month.
My friend has an S4 that is about 7 months old. It was running stock 4.3 and he was having trouble with the person receiving his call would get a loud growl type sound (he hears nothing on his end), about 50% of the time (though not too good for a business phone). The phone works fine on Bluetooth without any offensive sounds going through. He said if he takes his sim out and puts it in hos sons S4, makes a few calls and then puts it back in his phone, the problem goes away for a few hours to a day.
He got a new sim and he had the same problems. He took the phone to the Samsung repair center here and they said the phone was not under warranty anymore as he had the glass replaced when it cracked (2 weeks after he got the phone).
I took the phone from him to see if I could figure it out and as soon as I booted it up, it started to update to 4.4.2. When it finished, the phone was barely useable, lagging so bad the phone would not respond for 5 to 10 seconds and the screen would jitter up and down. I reset the phone twice and though it is better, the phone is still laggy (not as bad) and when I try to make a call, the call goes through, but I hear nothing.
I want to downgrade to 4.3 and hope the phone is better as I have read a lot of people are having trouble on 4.4.2, but with the new 4.4.2 bootloader, I can't downgrade. Is there a way to downgrade that will not trip the Knox counter? Also, has anyone ever heard of people receiving a call getting a loud sound on their end with the S4?
Many thanks,
Ian
It isnt possible downgrade without trip KNOX :highfive:
Joku1981 said:
It isnt possible downgrade without trip KNOX :highfive:
Click to expand...
Click to collapse
What about flashing a stock ROM from another region, but using the modem from Rogers (My friends telco)?
How can Samsung/Rogers put out software than makes the phone inoperable?
Ian
It isn't possible.
Your only option is to use a custom recovery and flash a custom rom.
Why are you worried about knox when you don't even have warranty anymore? If I had the issues that you descripe I would try to fix them asap and not worrie about knox.
Lennyz1988 said:
It isn't possible.
Your only option is to use a custom recovery and flash a custom rom.
Why are you worried about knox when you don't even have warranty anymore? If I had the issues that you descripe I would try to fix them asap and not worrie about knox.
Click to expand...
Click to collapse
The phone works properly now. I reset the phone again, but this time, I did not allow Google to restore my apps. I installed them manually and the phone works fine. It must have been something Google was restoring from 4.3
Is Samsung the only manufacturer that does not allow downgrading? This was one of the reasons I moved away from Apple. It's my phone, let me do to it what I want.
Ian
Just got this today and it's great besides being a bit smaller than my g6 and because of front camera design only being technically 5.5in screen for most apps especially games.
However since I have had it, it has randomly rebooted itself twice for no real apparent reason. Is this a known issue or something anyone else has experienced? I want to try to get a bit more information on it before contacting the eBay seller. It is a refurbished.
I have never experienced a random reboot. You might want to try factory resetting your phone and then setting it up with the fresh start option instead of restoring from a Google cloud backup. Was your phone on Nougat or Oreo when you received it? Were there any major software updates?
It was fully updated to 8.1.0 when I received it. April 5th security patch. It was factory reset and I started fresh. No backup other than logging into my Google account for contacts, passwords and logins and such. I never do backups and restores always start fresh other than Google account.
Nickvanexel said:
It was fully updated to 8.1.0 when I received it. April 5th security patch. It was factory reset and I started fresh. No backup other than logging into my Google account for contacts, passwords and logins and such. I never do backups and restores always start fresh other than Google account.
Click to expand...
Click to collapse
Must be rogue app, had mine 3 months and never had a glitch or reboot.
Sent from my PH-1 using Tapatalk
If you are still having the random reboots you might want to boot your phone into safe mode to verify that a third party app isn't causing the problem. Since your phone was refurbished it's also possible that it was damaged by the previous owner or returned for the same issue you are experiencing. I did read that some early PH-1 buyers had to return their phones because of hardware issues like overheating.
Just did it again while using chrome. Just froze up for a few seconds and restarted. Doesn't seem to be overheating and the first time it happened before I installed anything I think. Guess I'll try a reset and go from there.
Factory reset twice now. No 3rd party apps installed. Updated all apps on Google play. The default phone apps.
Now the phone is freezing and rebooting itself constantly. Out of control. I am in safe mode right now and hasn't frozen yet. I don't know what the hell is going on.
Would love to be able to fix this issue myself without having to do return shipping. I have contacted the seller already though.
If it doesn't freeze or reboot at all in safe mode that usually means an app that you downloaded is causing the problem. The normal thing to try would be to factory reset the phone, download one app and see if there are problems. If the phone seems to be fine download a second app and use the phone long enough to see if the phone is stable. If it seems fine download a third app and do the same.
That's obviously very time consuming and if you were running a phone with heavily modded code like OnePlus with Oxygen it would probably be worth the investment of time. But this phone runs stock Android. Unless you are installing something unusual that might cause stability issues what you are describing sounds like a hardware problem. You might have bad memory for example and not enough is going on when the phone is in safe mode to trigger the unstable behavior.
I think returning or exchanging the phone you bought is definitely your best course of action. I really like this phone but it sounds like yours is defective or damaged.
The only other thing that comes to mind is that sometimes if you own more than one phone the Play Store will show apps that aren't compatible with the phone you are actually using. Dialers, messaging apps, camera apps and music players made for a specific phone brand aren't usually compatible with other brands because they need modded framework to function properly. Some apps that definitely are not compatible with this phone do show up in my Play Store Library available for download. Is it possible you are downloading an incompatible app?
I factory reset and haven't installed a single app. Just updated everything that was stock with the phone after reset. I was thinking faulty ram too, seems like it is.
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Nickvanexel said:
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Click to expand...
Click to collapse
Grab a BTS zip from the back to stock thread... And flash that...
I'll bet however it was updated had some yuck in it...
Nickvanexel said:
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Click to expand...
Click to collapse
Someone in the Essential stock ROM dump thread just described the exact same behavior that you are experiencing. He hopes reflashing stock will fix it but since it's identical to what's happening with your phone I think he's going to end up disappointed. You might want to check out his post and see if he has any luck. It was the latest post in the thread so it should be easy to find.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page41
Yeah that was me. Trying to get information on the procedure to manually reflash this phone with stock firmware. I shouldn't need to unlock bootloader to do it? Just trying to flash stock over stock to hopefully correct any os corruption. Also mine is apparently a unlocked Sprint variant even though it was advertised as being a normal unlocked variant. Not sure if the firmware from that thread will work for me.
Nickvanexel said:
Yeah that was me. Trying to get information on the procedure to manually reflash this phone with stock firmware. I shouldn't need to unlock bootloader to do it? Just trying to flash stock over stock to hopefully correct any os corruption. Also mine is apparently a unlocked Sprint variant even though it was advertised as being a normal unlocked variant. Not sure if the firmware from that thread will work for me.
Click to expand...
Click to collapse
Sorry I didn't notice that. I haven't done any flashing on this phone but I know I read that people with the Sprint phones were flashing the regular stock image to get rid of the Sprint apps and get updates from Essential rather than Sprint. But if you don't want to unlock your bootloader you can download official factory images from the Essential website and sideload using a computer. Flashing instructions are on the download site.
https://www.essential.com/developer/current-builds
Alright I reflashed the latest firmware from essential page via adb sideload. I highly dout it worked but I'll see.
What would I need to do from here to do a complete fresh reflash completely overrighting any trace of the old os? I still want to keep it stock but doesn't matter if I need to unlock the bootloader. Just want a complete wipe of the old os and fresh reflash to be sure any traces of corruption are removed to be sure if it's a hardware issue.
That's easy on single partition phones but much more difficult on phones with an A & B partition like the PH-1. You definitely need to unlock the bootloader. On my Pixel XL you needed to flash the factory image separately to partitions A & B to ensure there was nothing left from before but the procedure might be different on this phone. I went through the flashing instructions when I got this phone and think if you flash the full restore stock image it supposedly returns both partitions to stock automatically but that definitely didn't happen on the Pixel. Considering that this phone is supposed to be easy to hard brick (which was virtually impossible on the Pixel) I wouldn't chance it unless you can't return or exchange the phone from the seller.
Well side loading the ota from essential website didn't work. I'd say it's already hard bricked. Still crashing after a while of using it. Last night I loaded as many apps at one time as I could. Got maybe 10 opened at once before it crashed. Seems like faulty ram to me.
Wife just had it happen on her new White one twice today while playing Pokemon GO.
She says she also had her podcast app and hangouts open but minimized and not being actively used in the background.
She's on a fresh install of Oreo 8.1 with the Gcam mod by MGC_5.1.018_Urikill_vXXII.apk using the settings suggested by aer0zer0
Anyhow I hope its just a completely random fluke and not a serious issue as I have a new black one from Amazon in the mail and would really hate to have to return these otherwise wonderful devices.
Mine ain't no fluke. After it crashes if I immediately reboot it instantly crashes again. I have to let it sit a while turned off and reboot again to any significant time before crashing. Longest time it's ran before crashing since having it it's maybe an hour. Didn't notice it much at first because I didn't use it more than a few minutes at a time. So it was in sleep mode constantly crashing and rebooting. Now that I have been watching it more it just constantly keeps rebooting even while sitting idle. I'll glance over at my phone and low and behold it's rebooting again.
Nickvanexel said:
Mine ain't no fluke. After it crashes if I immediately reboot it instantly crashes again. I have to let it sit a while turned off and reboot again to any significant time before crashing. Longest time it's ran before crashing since having it it's maybe an hour. Didn't notice it much at first because I didn't use it more than a few minutes at a time. So it was in sleep mode constantly crashing and rebooting. Now that I have been watching it more it just constantly keeps rebooting even while sitting idle. I'll glance over at my phone and low and behold it's rebooting again.
Click to expand...
Click to collapse
Ouch okay that most certainly sounds like a bad hardware issue as you suspected earlier.
Thankfully in her case the reboots were well apart from one another and the phone was fine after the reboot. Even let her play PKGO.
I mostly came in to comment to hopefully help by voicing that it had happened and the circumstances in which it did for her with the idea it might pinpoint some flaw in the overall system if there was one.