Related
Just saw it
"unrevoked: A warning: the SkyRaider for the inc has a higher then average chance of causing "USB bricked" devices, we will try to work on a fix."
--http://www.twitter.com/unrevoked/status/20736784251
Sent from my ADR6300 using Tapatalk
Sheesh man! That is scary! Makes me feel like one of those people who come home and find out that the bank they were at an hour ago got robbed ten minutes later!
The tweet has nothing to do with unrevoked's releases.
The skyraider rom appears to use a slightly broken update-binary. When you flash skyraider rom, it writes stuff to misc that it shouldn't, as far as I can tell. This may cause a USB brick (ie, phone is not accessible via USB)
I didnt know for sure what it meant. Just thought I'd share it. I havnt had problems connecting via usb
Sent from my ADR6300 using Tapatalk
So don't use SkyRaider 2.2 from 8/5? I was literally seconds away from doing this...
Is this "USB Brick" something that can be reversed with a Nandroid restore if I decide to take my chances?
It sounds to me like it's an issue with running Unrevoked after you've already installed SkyRaider. I haven't seen any posts in the 231 page SkyRaider thread that report their phone was USB-bricked.
How would that make sense though, like if you are running a ROM you are already rooted, why run unrevoked again?
Θmega said:
It sounds to me like it's an issue with running Unrevoked after you've already installed SkyRaider. I haven't seen any posts in the 231 page SkyRaider thread that report their phone was USB-bricked.
Click to expand...
Click to collapse
This is the opposite of true.
SoccerCore11 said:
How would that make sense though, like if you are running a ROM you are already rooted, why run unrevoked again?
Click to expand...
Click to collapse
Maybe we're finally getting s-off
Sent from my ADR6300 using Tapatalk
rpearl said:
This is the opposite of true.
Click to expand...
Click to collapse
Any ideas on what the criteria would be for this to happen? Is it the process of flashing, our can this happen through a certain process while running the rom?
Sent from my ADR6300 using Tapatalk
rpearl said:
This is the opposite of true.
Click to expand...
Click to collapse
Then why have so many people not had issues with SkyRaider bricking their phones? So far the only place I've heard this is from the unrevoked team and plenty of people are apparently not having the issue at all.
I'm certainly not saying you're wrong—you're more knowledgable than me—but a lot of us are curious as to why this is suddenly an issue even though unrevoked is the only one who's had it happen. If it's because of unreleased software by unrevoked then what was the point in tweeting, since everyone who has it would be able to be contacted personally?
Θmega;7586637 said:
Then why have so many people not had issues with SkyRaider bricking their phones? So far the only place I've heard this is from the unrevoked team and plenty of people are apparently not having the issue at all.
I'm certainly not saying you're wrong—you're more knowledgable than me—but a lot of us are curious as to why this is suddenly an issue even though unrevoked is the only one who's had it happen. If it's because of unreleased software by unrevoked then what was the point in tweeting, since everyone who has it would be able to be contacted personally?
Click to expand...
Click to collapse
Unrevoked never said that it would definately brick your phone. They said it has a "higher than avarage chance of USB bricking due to a broken update-binary"
I've personally never had problems with sky raider, but then again, I haven't used adb in a while, and I use card reader to mount my sd, so this wouldn't affect me that much
Sent from my ADR6300 using XDA App
Fact:
Without unrevoked we still might not have root.
Fact:
There is no known issue among the general public (us) of SkyRaider bricking the usb. Its possible this has happened to 1 or 2 people sure, but that would be a very isolated incedent and does not mean its a common or uncommon bug - more like so super rare none of us have heard about it.
Now you said in your tweet:
unrevoked: A warning: the SkyRaider for the inc has a higher then average chance of causing "USB bricked" devices, we will try to work on a fix
Click to expand...
Click to collapse
Has a higher than average chance.
this leads me to believe that if the chance is .5 now its .6 - again not making it common.
we will try to work on a fix
Click to expand...
Click to collapse
Now maybe its just me but trying to fix something that you didnt break wouldnt that be considered taking responsibility for whats wrong??
Why would you not contact ihtfp69 about this directly? Sorry to say but your tweet is not very tactful and is now causing panic across multiple boards.
Just a word of advice, before basically saying, hey this ROM could break your ****, maybe in the future talk with the dev of the ROM before causing a panic..
Not trying to bash ya, just dont want unneeded panic especially for someone who has done a great job like ihtfp69 in creating a great ROM for us all to use.
btw thanks for the root!!!!!
jdkoreclipse said:
Unrevoked never said that it would definately brick your phone. They said it has a "higher than avarage chance of USB bricking due to a broken update-binary"
Click to expand...
Click to collapse
I'm sorry if I implied they did, but "higher than average" doesn't explain much.
Again, plenty of people never had this issue. It'd be nice for a bit more clarification instead of worrying a lot of current/future SkyRaider users without further explanations of how it happens…
djkms said:
Now maybe its just me but trying to fix something that you didnt break wouldnt that be considered taking responsibility for whats wrong??
Why would you not contact ihtfp69 about this directly? Sorry to say but your tweet is not very tactful and is now causing panic across multiple boards.
Click to expand...
Click to collapse
This is basically what I'm trying to say, but perhaps it's not coming across that well. If it's a very rare bug then the tweet could have been worded differently, or linked to more information.
Its not about running the rom now, its about how the next unrevoked will brick if you use it with this rom.
"@theozzeh After talking with @koush, we've determined that the "SkyRaider" rom is going to be a major bricking risk with the next unrevoked release."
bhazard451 said:
Its not about running the rom now, its about how the next unrevoked will brick if you use it with this rom.
"@theozzeh After talking with @koush, we've determined that the "SkyRaider" rom is going to be a major bricking risk with the next unrevoked release."
Click to expand...
Click to collapse
Thank you! I hadn't seen that tweet, and which goes back to my (sorta?) original question: if it's not an issue with a current release then why is there a need to panic everyone?
So what is the consensus on this info? Important or not? Does it need to be here in development?
OP can you update the first post with what we've gathered and what this all means?
Thanks
Θmega said:
Thank you! I hadn't seen that tweet, and which goes back to my (sorta?) original question: if it's not an issue with a current release then why is there a need to panic everyone?
Click to expand...
Click to collapse
Im not sure its made to panic everyone .. just informative if we are running skyraider which I am we have to be careful with the new version of unrevoked ... which we must use if we want the new version of cwm
I installed the latest vanilla skyraider, didn't like it so I wiped it and then put on the aiccus ROM. When I attach my phone to my computer it will not bring up the SD card or internal storage in my computer. Instead it brings up a CD drive. In the USB tray icon it still shows two removable disks and the CD drive does skip the letters that were assigned to those two drives. I can still take screenshots of the phone using the SDK.
I think this is the brick, if it's not I'd appreciate someone telling me how I can get my computer to recognize the phone again.
If its an update binary issue, then the author of SKyRaider merely needs to replace it, or remove it, as we don't really need the binary in the first place.
So this is a well-known trick that has worked since the N4 but I wanted to share it anyway. If you go to check for the update and it still says up to date, try this method as it has just worked for my N5 and my N7:
Settings>Apps>All Tab>Google Services Framework>Clear Data>Go back to check update and it should work, if not try the steps again.
Like I said, this has worked for my previous N4, N5, and N7(2013). Each time, I tried the check update button alone at least 5 times in a row with no luck, then trying the trick and checking it worked for each device.
Oh and BTW, this trick if done EXACTLY like this DOES NOT invalidate the tokens like some claim. My play store and GMAIL are completely fine on both devices.
PS: Do this at your own risk/if your new to Android (Butthurt syndrome cured)
A Google employee also explained why you should not do this: http://www.reddit.com/r/Android/com...ear_data_for_google_service_framework/cdiymrp
Oh no you didn't.
myorks1127 said:
So this is a well-known trick that has worked since the N4 but I wanted to share it anyway. If you go to check for the update and it still says up to date, try this method as it has just worked for my N5 and my N7:
Settings>Apps>All Tab>Google Services Framework>Clear Data>Go back to check update and it should work, if not try the steps again.
Like I said, this has worked for my previous N4, N5, and N7(2013). Each time, I tried the check update button alone at least 5 times in a row with no luck, then trying the trick and checking it worked for each device.
Oh and BTW, this trick if done EXACTLY like this DOES NOT invalidate the tokens like some claim. My play store and GMAIL are completely fine on both devices.
Click to expand...
Click to collapse
You're wrong, you shouldn't do that. A quick Google will tell you why
bozzykid said:
A Google employee also explained why you should not do this: http://www.reddit.com/r/Android/com...ear_data_for_google_service_framework/cdiymrp
Click to expand...
Click to collapse
I read that post before and have yet to find a single issue with my devices and never had an issue for my N4 when I did it so I don't see what the big deal is...there is another very similar method that does indeed mess up the tokens but it IS NOT the same by any means.
Please prove me wrong, I will check anything on my phone that you think isn't working now because I did this the quick and easy way instead of wasting my time sideloading...
myorks1127 said:
I read that post before and have yet to find a single issue with my devices and never had an issue for my N4 when I did it so I don't see what the big deal is...there is another very similar method that does indeed mess up the tokens but it IS NOT the same by any means.
Please prove me wrong, I will check anything on my phone that you think isn't working now because I did this the quick and easy way instead of wasting my time sideloading...
Click to expand...
Click to collapse
i'm going to go out on a limb and guess that you don't work for Google, specifically the Android/Mobile division. but since you don't see what the big deal is (going against what a Google engineer says) we should all believe you.
this may not mess up your phone, but it wrecks havoc on the back end of Google's servers... when a Google engineer tells us all not to do something, then thoroughly explains why, it's probably best to heed his advice.
Tried this, took five data clears and it gave me the update. Thanks!
Sent from my Nexus 5 using xda app-developers app
Lucke said:
i'm going to go out on a limb and guess that you don't work for Google, specifically the Android/Mobile division. but since you don't see what the big deal is (going against what a Google engineer says) we should all believe you.
this may not mess up your phone, but it wrecks havoc on the back end of Google's servers... when a Google engineer tells us all not to do something, then thoroughly explains why, it's probably best to heed his advice.
Click to expand...
Click to collapse
It doesn't wreak havok on my end so why would I care?
I'll go out on a limb and say if it caused that much grief for Google the clear data feature would have been gone a long time ago.
Its worked since the nexus s btw
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 06:02 PM ---------- Previous post was at 06:01 PM ----------
I've done it with every update since ICS and never had an issue...and its always worked
Sent from my Nexus 5 using xda app-developers app
Glad I finally have some people backing me up lol, my brother is an engineer for Amazon and he thinks he knows everything too...
And this is how people who don't know better come here to XDA and mess up their devices because they follow bad advice that they read. Don't do this. It can have unintended consequences and according to Google has absolutely no effect on when you will receive an OTA.
muyoso said:
And this is how people who don't know better come here to XDA and mess up their devices because they follow bad advice that they read. Don't do this. It can have unintended consequences and according to Google has absolutely no effect on when you will receive an OTA.
Click to expand...
Click to collapse
People who don't follow the exact directions you mean..and are you saying that this trick worked for 3 Nexus devices I own completely by chance after trying to update over 5 times each before doing the trick and then it working after the trick?
myorks1127 said:
People who don't follow the exact directions you mean..and are you saying that this trick worked for 3 Nexus devices I own completely by chance after trying to update over 5 times each before doing the trick and then it working after the trick?
Click to expand...
Click to collapse
What I am saying is that it doesn't matter how many people like you swear that it works. The people who actually work on Android say it doesn't and that it can have bad consequences. And anyone who actually wants the update can simply sideload it with absolutely no ill effects if they want to force the update onto their devices early. There is absolutely zero reason to do what you swear works.
muyoso said:
What I am saying is that it doesn't matter how many people like you swear that it works. The people who actually work on Android say it doesn't and that it can have bad consequences. And anyone who actually wants the update can simply sideload it with absolutely no ill effects if they want to force the update onto their devices early. There is absolutely zero reason to do what you swear works.
Click to expand...
Click to collapse
The reason to do it is to save time and hassle of doing all the steps needed for side loading, but no worries, I got the update faster and easier than anyone who side loaded with ZERO consequences to me..:good:, your Google knee pads must be pretty worn out by now huh?
Or you can just wait for the update. I'm still on 4.4 and happy about it. 4.4.1 brought radio issues, and 4.4.2 also seems to have a few bugs. Hopefully by the time I get the OTA, the bugs will be fixed.
myorks1127 said:
The reason to do it is to save time and hassle of doing all the steps needed for side loading, but no worries, I got the update faster and easier than anyone who side loaded with ZERO consequences to me..:good:, your Google knee pads must be pretty worn out by now huh?
Click to expand...
Click to collapse
Yes, I am sucking Google's **** because I am telling users who don't know better that Google specifically said not to do this. You got me. My secret is out.
myorks1127 said:
It doesn't wreak havok on my end so why would I care?
Click to expand...
Click to collapse
The problem is you don't know if it does. Because the GCM id changes, things like push messages from different apps will likely stop working (maybe permanently if they don't properly handle a changing id). You might not of noticed this much in the past because not a lot of apps utilized GCM push messages. However, more and more apps are using them today.
It's amazing that people will ignore advice from the people that have written the actual software. Just don't do it. The worst part about doing it is that you may not even know that something has messed up because its not obvious.
Thanks worked for me
Took me straight from 4,4 to 4,4.2 after 4 attempts
So, I made the mistake of uninstalling ItsOn on my Sprint HTC One M8. Now I am unable to use data, sms, make calls, wifi report it's unstable. What the hell is going on? I have attempted to reinstall an RUU and even after that I get the same errors. I am on the verge of going into the Sprint store tomorrow for a replacement. I called HTC and they think the SIM card might be bad. I checked it and it looks fine. Is there something I can reinstall to fix this or is my phone dead just from that one uninstall?
Try flashing a stock 4.4.4 rom it will come stock with itson. Then do a ##72786# reset to attempt to restore your original data settings. Which way did you remove itson?
I used ROM Toolbox to uninstall ItsOn. I have reinstalled a stock rom on my phone in the hopes it would restore, but I still can not use any of the radios. This is crazy.
Just speculating. I almost wonder if this ItsOn also handles the phones antenna encryption. Possible there is some partician this is saved on and by uninstalling it I also wiped the partician. Add in the RUU do not contain it. Either way, guess I have to stop in at the Sprint store today and get a replacement.
ItsOn is in the /carrier partition aswell you cannot simply remove it. To attempt to fix your problem can you go into ##3282# and enter your msl go into data profile and hit restore and reboot. Also to remove itson on a stock rom flash this in recovery https://www.dropbox.com/s/md83hn4um0i5p09/Remove_ItsOn.zip?dl=0
Crud, don't think I have the MSL number.
If you are s-off download msl reader from play store otherwise youll have to get it from sprint
EVOuser94 said:
ItsOn is in the /carrier partition aswell you cannot simply remove it. To attempt to fix your problem can you go into ##3282# and enter your msl go into data profile and hit restore and reboot. Also to remove itson on a stock rom flash this in recovery https://www.dropbox.com/s/md83hn4um0i5p09/Remove_ItsOn.zip?dl=0
Click to expand...
Click to collapse
Now that I think about it. I think Sprint tech support had me do this. I recall a menu where it did this last night.
Most techs will give you the ##786# code to do this. Try a simpler ##72786# that one wont require msl
Ok, got the code and ran what you said. Still dead. HTC just had me do a recovery wipe. I think this is hardware related now. Software would have been restored at some point. I would think it would have restored once I loaded the RUU stock ROM.
Possibly, You could always try to connect to a wifi and do a handsfree activation aswell
All these "fixes" are speculation, I couldnt know your exact problems unless i had the device in hand. Just know Im trying
EVOuser94 said:
Possibly, You could always try to connect to a wifi and do a handsfree activation aswell
All these "fixes" are speculation, I couldnt know your exact problems unless i had the device in hand. Just know Im trying
Click to expand...
Click to collapse
Tried the wifi route, but wifi is also messed up. It will connect to my wifi network, but reports the connection is unstable.
Cataract2 said:
Tried the wifi route, but wifi is also messed up. It will connect to my wifi network, but reports the connection is unstable.
Click to expand...
Click to collapse
Yeah, at this point id also agree its hardware. Getcha a replacement haha
EVOuser94 said:
Yeah, at this point id also agree its hardware. Getcha a replacement haha
Click to expand...
Click to collapse
Lol, I better hope it's hardware. I figured it best to come clean with HTC and let them know it was rooted. So, they will have their diagnosis team look at it and if they determine the root caused it then I might be out some $$$ for the repair of it.
Still don't see how the root could cause this in the end. Unless there is a section that the RUU doesn't get.
Cataract2 said:
Lol, I better hope it's hardware. I figured it best to come clean with HTC and let them know it was rooted. So, they will have their diagnosis team look at it and if they determine the root caused it then I might be out some $$$ for the repair of it.
Still don't see how the root could cause this in the end. Unless there is a section that the RUU doesn't get.
Click to expand...
Click to collapse
Id hold your tongue on that, HTC doesnt really care too much they just see it as a defective device and they RUU themselves and if that doesnt fix it they pretty much use it as spare parts or remelt and rebuild a new one that will work. silence and claiming ignorance is key to winning them over lol
EVOuser94 said:
Id hold your tongue on that, HTC doesnt really care too much they just see it as a defective device and they RUU themselves and if that doesnt fix it they pretty much use it as spare parts or remelt and rebuild a new one that will work. silence and claiming ignorance is key to winning them over lol
Click to expand...
Click to collapse
Bit late on that. I told the care personel over chat that I did. They still offered the swap program that they were offering in the beginning. We'll see what happens. Dunno if they tag my account with regards to it or not. I just was thinking since the bootloader says **relocked** they might notice that and freak.
Cataract2 said:
Bit late on that. I told the care personel over chat that I did. They still offered the swap program that they were offering in the beginning. We'll see what happens. Dunno if they tag my account with regards to it or not. I just was thinking since the bootloader says **relocked** they might notice that and freak.
Click to expand...
Click to collapse
Lol, nah, you got lucky but they hardly ever look at that stuff
EVOuser94 said:
Lol, nah, you got lucky but they hardly ever look at that stuff
Click to expand...
Click to collapse
First time warrantying a phone, let alone a smart phone. Wasn't sure. Will remember that in the future. Guess I should always remember the human condition. Everyone is lazy.
Lesson learned on this though. Do not uninstall ItsOn. Just in case this truly is a software issue. Though I doubt it.
BTW, does that uninstaller you sent me work? Is it based on the Bad Boyz uninstaller? I'm just a bit leary after this experience to attack that again. Though I do not like it using 40% of my battery.
Cataract2 said:
First time warrantying a phone, let alone a smart phone. Wasn't sure. Will remember that in the future. Guess I should always remember the human condition. Everyone is lazy.
Lesson learned on this though. Do not uninstall ItsOn. Just in case this truly is a software issue. Though I doubt it.
BTW, does that uninstaller you sent me work? Is it based on the Bad Boyz uninstaller? I'm just a bit leary after this experience to attack that again. Though I do not like it using 40% of my battery.
Click to expand...
Click to collapse
The one i sent you is for stock, bad boys is for his rom
EVOuser94 said:
The one i sent you is for stock, bad boys is for his rom
Click to expand...
Click to collapse
Just because I want to read up some more. Where did you get yours from? Is there a thread about it or a how to?
So i rooted my new nexus 6 and installed chroma rom. every thing was fine till i noticed a small part of the screen flicker. it was like a black line coming and going as soon as i took it off charging it was fine. this was after i installed the rom there was nothing like this on the stock one. also when i open the camera app i can hear a small click/ crackle sound. this happened in the stock rom too but with the snapchat app. its irritating and i cant find a fix anywhere. and lastly whats with the network issue? it suddenly comes and goes. i checked it and it showe 0dbm and 99 asu?is this common? tried to find a fix but all i got was lots of unanswered threads. as being a student who need to use this phone for a long time can anyone tell me if all this is fixable ? or do i need to get a replacement as im still in my 30 day return period. thanks in advance and sorry if all this issues are already in a post and have fixes just post me the link as i could find it
being a student who needs the use of the phone for long periods of time.. what are you foing moddifying your device. no custom rom will be bug free. even though whtyever bugs dont bother me, they seem to bug you. why dont you just stay stock with root if those issues are bugging you.
simms22 said:
being a student who needs the use of the phone for long periods of time.. what are you foing moddifying your device. no custom rom will be bug free. even though whtyever bugs dont bother me, they seem to bug you. why dont you just stay stock with root if those issues are bugging you.
Click to expand...
Click to collapse
I know no roms are bug free, just wanted to know if these are common software issue and not a bad device that i got. And on the other hand i used my s3 for 2.5-3 yrs with custom roms and stuff simply as i enjoy running them and seeing all the amazing stuff people can do with skill that was the main reason i got a nexus
about_99_ninjas said:
I know no roms are bug free, just wanted to know if these are common software issue and not a bad device that i got. And on the other hand i used my s3 for 2.5-3 yrs with custom roms and stuff simply as i enjoy running them and seeing all the amazing stuff people can do with skill that was the main reason i got a nexus
Click to expand...
Click to collapse
honestly, ive never run into the issues that you decribed.
simms22 said:
honestly, ive never run into the issues that you decribed.
Click to expand...
Click to collapse
So i should request for a replacement ?
about_99_ninjas said:
So i should request for a replacement ?
Click to expand...
Click to collapse
give motorola a call for sure, they themselves might suggest a replacement.
simms22 said:
give motorola a call for sure, they themselves might suggest a replacement.
Click to expand...
Click to collapse
Well i bought online from someother store so I'll get it changed. Need to flash the stock rom first thanks anyways
Ever since I've had this phone I've been experiencing the error in the title above. I've rooted, tried freezing apps I think might be the problem, and just tonight I unlocked the bootloader, which wipes everything, and was hoping the error would go away. It only happens the first time upon boot. I hit either Wait or OK and it goes away until next boot.
Not a big deal, but curious what's causing it. Just wondering if anyone has this issue.
This is the 16gb Prime version, rooted, debloated, unlocked bootloader.
Cheers!
joesee said:
Ever since I've had this phone I've been experiencing the error in the title above. I've rooted, tried freezing apps I think might be the problem, and just tonight I unlocked the bootloader, which wipes everything, and was hoping the error would go away. It only happens the first time upon boot. I hit either Wait or OK and it goes away until next boot.
Not a big deal, but curious what's causing it. Just wondering if anyone has this issue.
This is the 16gb Prime version, rooted, debloated, unlocked bootloader.
Cheers!
Click to expand...
Click to collapse
It's interesting. I just purchased another one for my wife and right out of the box it does the same thing. I guess this is just something that people deal with and don't talk about??
joesee said:
It's interesting. I just purchased another one for my wife and right out of the box it does the same thing. I guess this is just something that people deal with and don't talk about??
Click to expand...
Click to collapse
I have had my phone for almost 3 weeks BLU R1 HD Prime version, I get no error messages, system or otherwise. I Have rooted it, unlocked the bootloader and removed the ads.
joesee said:
It's interesting. I just purchased another one for my wife and right out of the box it does the same thing. I guess this is just something that people deal with and don't talk about??
Click to expand...
Click to collapse
Check your permissions
joesee said:
It's interesting. I just purchased another one for my wife and right out of the box it does the same thing. I guess this is just something that people deal with and don't talk about??
Click to expand...
Click to collapse
Never experienced that issue. That's odd it's occuring on two devices. Who is your carrier, could it possibly be a sim issue??
ariesgodofwar said:
Check your permissions
Click to expand...
Click to collapse
Which permissions would you be referring to? A fresh reboot after a factory reset does it.
kal250 said:
Never experienced that issue. That's odd it's occuring on two devices. Who is your carrier, could it possibly be a sim issue??
Click to expand...
Click to collapse
I thought about that too, but I've tried two different carriers.. T-Mo, and Cricket. Both do it, regardless if one is in one slot or both are in either.
Like I said, it only does it after the first reboot, then I never see it again.
joesee said:
Ever since I've had this phone I've been experiencing the error in the title above. I've rooted, tried freezing apps I think might be the problem, and just tonight I unlocked the bootloader, which wipes everything, and was hoping the error would go away. It only happens the first time upon boot. I hit either Wait or OK and it goes away until next boot.
Not a big deal, but curious what's causing it. Just wondering if anyone has this issue.
This is the 16gb Prime version, rooted, debloated, unlocked bootloader.
Cheers!
Click to expand...
Click to collapse
My LG G4 does this sometimes. Just click wait to avoid dropping a system process. It probably represents a random error during boot, but it never seemed to hurt anything enough to justify a full investigation.
Niki Kidman said:
Go to settings, and choose permission authority!
Click to expand...
Click to collapse
So are you just posting ramblings for the sake of increasing your post counter, or are you serious with these nonsense suggestions?? WTF is permission authority??!!??
Niki Kidman said:
Go to settings, and choose permission authority!
Click to expand...
Click to collapse
haha ... wow....
kal250 said:
So are you just posting ramblings for the sake of increasing your post counter, or are you serious with these nonsense suggestions?? WTF is permission authority??!!??
Click to expand...
Click to collapse
My HTC 10 just gave me this system stopped responding error right after rebooting - Now I'm beginning to think it's just a new "feature" in Marshmallow. When I have some extra time, I'd like to see if I can figure out what does this - more for the sake of learning than anything else.