Just got my handset about a week ago. Got an update to 5.02 and OK Google seemed to be working fine until a couple of days ago whereby I have now noticed that it's not there anymore.
Just me then?
Same here
Verstuurd vanaf mijn SM-G920F met Tapatalk
Replaced by Siri! Huehuehue
Sent from my SAMSUNG-SM-G920AZ
Im amazed more people have not noticed or had anything to say about it. I can recall something about it being removed when the handset was first released because of battery issues I think it was but then I understood it to be real activated.
Now all of a sudden it's gone again.
Might want to uninstall updates and reinstall, it's still there just reset my phone couple days ago ago and set it all up again today.
Sent from my Verizon Galaxy S6
Seems like actually it's still there.
It just does not show on the search widget anymore but if I give the command it works.
Related
Running totally stock on 5.1.1 (N920PVPU2A0I6). Starting about an hour ago I'm getting a pop-up saying "Bootstrap Failed...".
Phone is unresponsive and reboots by itself.
Thoughts?
late,
Coz
*EDIT: Factory reset didn't solve it.....correction, 3rd attempt at factory reset seems to have solved it. But I would love to know what initially caused the situation.
Same
Sent from my SM-N920P using XDA Premium HD app
pbedard said:
Same
Sent from my SM-N920P using XDA Premium HD app
Click to expand...
Click to collapse
The only thing that updated/changed this morning was an update (I believe) for Sprint Zone.
late,
Coz
Well that didn't work....after about an hour of it running without issue, I'm getting the Bootstrap Failed... message again and it's restarting.
late,
Coz
Update....phone has been stable (no re-boots, lock-ups, etc.) for the past few days. I occasionally get the pop-up message stating, "bootstrap failed..." but it doesn't seem to impact the performance of the phone from what I can tell.
late,
Coz
Mine keeps doing it oh well
Sent from my SM-N920P using XDA Premium HD app
My phone just started doing this today. Also a Sprint Note 5. No software updates installed recently... most recent was the Sprint and Samsung updates for Samsung Pay, which I did set up-- but I did that day 1. Right before the problem started happening, the phone rebooted itself, and it hasn't been well since. I checked aLogcat, but nothing gets logged there. After a few of the "Bootstrap failed..." toasts, the phone just becomes unresponsive and I have to hard shutdown. The only thing that I can think of that I've done differently today was plug my phone into my laptop to charge it earlier. I don't think I'd ever plugged it into my laptop before.
Hopefully somebody can pin down the cause of the problem here. I'm surprised that aLogcat doesn't show anything, which makes me wonder if it's some Knox issue...
U have to use root explorer and go to carier/itson delete that folder it will make your phone faster but u need to power it off for like 20 mins afrer u delete it
Sent from my SM-N920P using XDA Premium HD app
pbedard said:
U have to use root explorer and go to carier/itson delete that folder it will make your phone faster but u need to power it off for like 20 mins afrer u delete it
Sent from my SM-N920P using XDA Premium HD app
Click to expand...
Click to collapse
I'm curious as to why you suggest deleting that folder? What exactly will that fix? Details please before you suggest to a member to just delete something.
late,
Coz
The reboots i saw it mentioned.
Sent from my SM-N920P using XDA Premium HD app
Same problem, I have stock Sprint Note 5 with Samsung Pay updated and activated. Worked fine for a few days then all of the sudden I started getting "Bootstrap Failed" and my phone is unresponsive and/or data connection stops functioning forcing me to restart.
Is Sprint/Samsung aware of this issue and working on a fix? Very annoying. I've uninstalled all updates to Sprint Zone, force stopped and cleared data for Sprint Zone which appeared to help for a couple days, but now it's back again.
Has anyone had any luck with hard / factory reset? I don't want to go through the hassle of backing everything up, wiping it clean and reinstalling everything if at the end of the day it doesn't make a difference.
After a few more lock ups and reboots yesterday, my phone started behaving normally again, but just now I saw another "Bootstrap failed..." toast, so clearly the problem has not gone away. It hasn't locked up again on me yet, so maybe I'll be okay for a while. The only references I've seen to this error have all pointed to the Sprint Note 5, and most have mentioned Samsung Pay, so I suspect it's an issue there. Whether or not Samsung/Sprint are aware of it, I don't know.
I've also read it may or may not have something to do with Sprint Zone. I would agree it's purely due to the recent Samsung Pay update as I've had the Note since launch day and only noticed this after activating and updating Samsung Pay late last week. Before that I used the phone for nearly a month with no issues whatsoever.
While my phone hasn't locked up or rebooted by itself, I still get the "bootstrap failed..." occasionally.
I too think it was associated with the Sprint Zone and/or Samsung Pay update.
late,
Coz
I have only seen it once. Im fully stock to latest update. It happened to me after i noticed i had no data connection showed full lte but i had nothing opened up sprint zone and tried to refresh showed error. Then bootsrtap failed, have not seen it since
Sent from my SM-N920P
Bootstrap failed
It started happening to me after my fingerprint recognition failed, and I could not remember my backup password.
Just started happening to me a few days ago. completely stock sprint phone with the latest update (samsung pay). I noticed that right after the message PRL update began. After that and updating the profile, i havent seen the message.
Any updates on this? I went into Best Buy this weekend and had Samsung Experience store re-flash the OS to the phone, uninstalled Sprint Zone, uninstalled Samsung Pay updates, and force stopped Samsung Pay Framework. It worked fine for a few days but it started showing "Bootstrap failed" again. While it doesn't freeze up like it did the first time I received that message, in general the connectivity seems spotty (I'll show I'm connected to Wifi but nothing shows up on web browser or apps).
The problem is when Samsung Pay installed, it also installed an update to Android, and the Samsung Experience store in Best Buy can only flash the latest version of the OS. They can't revert back to the stock version of Android that came with the phone.
That's the biggest problem. Samsung and Google should make it so that they can revert back to a prior version of Android if the latest version has major bugs in it (which has been increasingly the case since Lollipop began rolling out). I had ZERO problems with the stock software/firmware that came with the device out of the box. Lesson learned I guess, don't accept an update if the version you have works well, until at least a couple months of the new update being out in the wild first....
Haven't seen this notice in a few days. It stopped after manual prl and profile update.
On a side note, I disabled the Samsung pay via package disable pro
Anyone figure this out?
Hello everyone,
This is my first post on XDA so please forgive me if I'm doing something wrong (I also posted in the T-Mobile S6 Forum).
So my story, I got a refurbished unit G920T at Swappa, I updated to the newest version directly (G920TUVU3DOI1) and it was working fine for the first week or so. Then the reboots started happening, I didn't give it too much thought but looked into it anyways.
At first I thought it was a problem with the WiFi and I tried to keep it off for a while, and it did work for a day but again the restarts kept happening, and now with the phone turning off during the night (no apparent loss in battery mind you).
Then I went to rooting and custom kernels.
I installed unikernel v8-0002 through Odin3_v3.10.6 and I tried removing some Samsung apps with TitaniumBackup in case there was some conflict happening but the restarts kept happening.
Then I installed a custom ROM, "XtreStoLite_ROM_v2.4_Deo-Mod-Edition_XXU3COI9_G920-5-F-I-T-W8-K-L-S" to be more specific.
And to my surprise it worked great, no restarts or shutdowns for about 2-3 weeks, it was great!
But then out of the blue the restarts started happening, they started slow, about 2-3 a day.
But after a few days they went to 10-20 and after that 100-200 a day.
Something was definitely wrong. So I installed the original firmware again (G920TUVU3DOI1_G920TTMB3DOI1_G920TUVU3DOI1_HOME) and booted to the stock firmware, restarts kept happening of course (didn't expect them to stop).
So I retreaded my steps and installed multiple other kernels (Unikernel V9, Vindicator, multiple different flavors of them). Also I installed multiple ROMs (Arrow_ROM_v6.0.0, and DN5 - S6 FLAT - EDGE v4 OJ5 - deodex) but nothing seems to work;
I did multiple wipes, storage wipes, cache wipes, factory resets (from GUI and twrp-2.8.7.2-zeroflte) but every time the same thing happens.
I did notice that the phone stutters and freezes, a behavior that I have not experienced before.
I installed CatLog and got multiple log files when the phone restarts but all of them are different and there is no "pattern" to be found (at least in first inspection). I want to upload them but my post count prohibits it.
Please let me know what can I do, I will reply to your questions ASAP so at least I can get some light into what is happening.
Thank you!
Well, if this is happening across multiple roms/software it can only really be hardware at fault I would think?
Sent from my SM-G920F using Tapatalk
jr866gooner said:
Well, if this is happening across multiple roms/software it can only really be hardware at fault I would think?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Hello!
After I posted this I ended up talking to T-Mobile and apparently the phone still is under warranty and they sent me a shipping label to return the phone and get another one from them.
Which is good but also I tripped KNOX but I don't know how much they care about that.
Fingers crossed I guess.
Thank you for replying!
Good to hear of a semi positive result! Let us know!
Sent from my SM-G920F using Tapatalk
Can anyone confirm if it works or not on Marshmallow?
It's not working on my S6 anymore and I'm not sure if that was before or after I upgraded and every other device I have that supports it is still on Lollipop and working.
yes, the service is installed.
Sent from my Galaxy S6 using Tapatalk
Works fine for me
jai23 said:
Works fine for me
Click to expand...
Click to collapse
what ROM and kernel?
Sent from my Galaxy S6 using Tapatalk
Phoenix09 said:
what ROM and kernel?
Sent from my Galaxy S6 using Tapatalk
Click to expand...
Click to collapse
Stock.
I'm on AOSP VRToxin 6.0.1 and it doesn't work. It opens but somehow the barcode is not readable from the scanner. Tried on two different supermarkets where beep n go on lollipop would work flawlessly. I'm on S4 GT-I9505 btw.
About 2-3 weeks ago I noticed Beep-n-Go had stopped working on my T-Mobile Galaxy S6. I suspected it was due to the latest Beep-n-Go update and I worked with a tech from Mobeam for about a week via email but to no avail. Today I even uninstalled Beep-n-Go and all Beaming Service updates and downloaded the previous version of Beep-n-Go and installed it. Just tried it out at Kroger and it's still not working!
I'm beginning to believe something went sideways when I got the Marshmallow update a month or two ago... The tech from Mobeam has stopped responding to my emails. I'm inclined to go on a pubic Twitter campaign to get some visibility on my plight and see if Mobeam will respond then.
WayneTho said:
About 2-3 weeks ago I noticed Beep-n-Go had stopped working on my T-Mobile Galaxy S6. I suspected it was due to the latest Beep-n-Go update and I worked with a tech from Mobeam for about a week via email but to no avail. Today I even uninstalled Beep-n-Go and all Beaming Service updates and downloaded the previous version of Beep-n-Go and installed it. Just tried it out at Kroger and it's still not working!
I'm beginning to believe something went sideways when I got the Marshmallow update a month or two ago... The tech from Mobeam has stopped responding to my emails. I'm inclined to go on a pubic Twitter campaign to get some visibility on my plight and see if Mobeam will respond then.
Click to expand...
Click to collapse
if you're rooted, backup /system/app/BeamService, uninstall Beaming Service with Titanium Backup, reboot, copy backup back to /system/app (it won't install if you open the APK, I tried), reboot
I think that's what eventually fixed it for me, I'm not sure though because I'm sure I tried that a few times before contacting support who told me to clear data for the service and reboot, which was the first thing I did when I found out it wasn't working
otherwise, you might have to try a factory reset
I ended up buying a cheap USB barcode scanner so I could test it easily
Sent from my Galaxy S6 using Tapatalk
Phoenix09 said:
if you're rooted, backup /system/app/BeamService, uninstall Beaming Service with Titanium Backup, reboot, copy backup back to /system/app (it won't install if you open the APK, I tried), reboot
I think that's what eventually fixed it for me, I'm not sure though because I'm sure I tried that a few times before contacting support who told me to clear data for the service and reboot, which was the first thing I did when I found out it wasn't working
otherwise, you might have to try a factory reset
I ended up buying a cheap USB barcode scanner so I could test it easily
Click to expand...
Click to collapse
I'm not rooted. Knox is still cherry (it hasn't been tripped). I have rooted other phones in the past, but with the S5 and S6 since Knox was added, tripping Knox affects the resale value and I'd rather not do it.
As to Mobeam's lack of response, I've sent one tweet to @Mobeam so far and of course, I didn't receive a reply!! I then emailed Mobeam again asking if I was deliberately being ignored, also with no reply. I may be sending several tweets in "machine-gun" fashion to Mobeam as my next tactic.
Hey i have my HTC Desire 610 and it has been working fine till now, two weeks my phone has unresponsive touch for example when im typing it wont type an "n" or an "i" but the weird thing is that it sometimes works perfectly and sometimes absolutely not.
I already tried a few things :
A factory reset in the beginning worked fine but now it doesn't. Some calibration apps they dont work either and of course contactig HTC they told me to replace my screen but i dont want this because sometimes my phone works good so its fixable ( i guess).
If you have some tips or questions help me or send them
Verstuurd vanaf mijn HTC Desire 610 met Tapatalk
I sideload a lot of apps, and an annoying kwirk that I've found is that unknown sources does not stay enabled permanently. Everytime I attempt to install an app from unknown sources, I have to hop into settings and recheck unknown sources.
Yes, I do uncheck "this install only"
me too. I've turned it back on about a dozen times. This last time seems to be holding, for a day so far.
yeah, it's been driving me nuts, I kept having to do this with all my Amazon underground apps. I did notice in the settings though in my case, it showed checked, but once amazon tried to install an app, it would magically uncheck.
did the software update this morning and it did not fix this for me still.
A good example why root and tasker is needed; this has been my experiance with touch wiz on S7 as well, simple setti gs dont stick ore reset sometimes. With root andbtasker though you can wright tasks that will auto re-apply seetings when touch wiz drops the ball.
This is different, my unknown source settings stuck on my S7E and Note 7 I had.
Root isn't needed for this. If it only happened after a reset it'd be no big deal. It happens literally every time you try and install and app. Even if its 2 mins apart no reboot.
Have same issue. Never had this issue before with S7 Edge and was not rooted. The permission just doesn't stay like it should.
Man, I thought I was going nuts lol. Same issue, but at least it didn't break the feature.
I thought this was just me.
Sent from my SM-G955U using Tapatalk
Same issue here
Sent from my SM-G955U using Tapatalk
Same here
Sent from my SM-G955U using Tapatalk
Can confirm I'm having the same problem. I'll see if talking to Samsung will get them to patch it soon hopefully.
Ditto
Sent from my SM-G955U using Tapatalk
nosympathy said:
This is different, my unknown source settings stuck on my S7E and Note 7 I had.
Root isn't needed for this. If it only happened after a reset it'd be no big deal. It happens literally every time you try and install and app. Even if its 2 mins apart no reboot.
Click to expand...
Click to collapse
You misunderstand my post, often despite samsung best efforts, touch wiz is buggy, this is a bug!
Options;
1) You live with it
2) wait for samsung to fix, which in my experiance doesnt happen often
3) fix it yourself (but root and tasker required)
Same issue here, kind of a ridiculous bug
Same issue. At first, I thought Verizon struck again. I never know ifnitnis a bug or Verizon intentionally screwing with the OS.
VinylJStar said:
Same issue. At first, I thought Verizon struck again. I never know ifnitnis a bug or Verizon intentionally screwing with the OS.
Click to expand...
Click to collapse
Well I've got AT&T, and it's like this. Not tooooooo bad but still and annoyance, and definitely not intentional because there is a option to uncheck "for this install only". It should get fixed.
lol, i thought i was going crazy.
Same problem here thought it was weird.
I'm having the same issue. At least I know now that I'm not the only one
Mine does. I went into settings and turned it on. I installed 3 apps and it's still on.
Sent from my SM-G955U using Tapatalk