Database Info

[Q] Reboot Bug - Is it really so prominent?

I keep hearing about this unfixed Nexus S reboot bug. I'm curious... is it really so widespread? Or is it only something a few people experience, like the luck of the draw?
I apologize if this question has been asked before. I'm considering buying the phone but can't decide if I should wait.

It always seems to pop up in the forums but it has never happened to me. I've had mine for almost a month now and it all seems to be perfect. No defects with screens or buttons or reboots. Maybe im just lucky...or people with complaints are just louder than ones who are satisfied.

The issue is real and Google have confirmed it. They've been working on a fix and the official word was an OTA update was going to be released this week:
Just a heads up that our initial tests look good and that we are expecting to send out an OTA within one to two weeks that will resolve the issue. Thanks for your continued patience!
Click to expand...
Click to collapse
code.google.com/p/android/issues/detail?id=13674

silfer said:
It always seems to pop up in the forums but it has never happened to me. I've had mine for almost a month now and it all seems to be perfect. No defects with screens or buttons or reboots. Maybe im just lucky...or people with complaints are just louder than ones who are satisfied.
Click to expand...
Click to collapse
Argh. I did not have this problem until yesterday (had the phone since January). Now my phone will reboot right after a call.

apreichner said:
I keep hearing about this unfixed Nexus S reboot bug. I'm curious... is it really so widespread? Or is it only something a few people experience, like the luck of the draw?
I apologize if this question has been asked before. I'm considering buying the phone but can't decide if I should wait.
Click to expand...
Click to collapse
I've had three Nexus S so far. The first one I picked up on dec 16th and didn't get a single reboot on - but the oleophobic coating on the screen was coming off in spots so I swapped it for another unit.
The second unit had issues rebooting. I saw it immediately - it rebooted while sitting on my desk. I could constantly recreate this by streaming audio over BT in my car - every 10-15 minutes it would reboot.
I picked up a mt4g for a few weeks to see if they could sort whether this was a hardware of sw issue (that thing is a brick to hold) and eventually picked up a third Nexus S once they identified it as a SW issue. This device has not rebooted a single time in the 27 days I've had it. I can stream audio and make long calls without an issue.
All three devices have operated with identical configurations. Based on this I'd say that some units are worse than others.
Maybe it's issue with the hardware tolerances and some hardware that falls within the accepted tolerance is not operating as expected and causing kernel panics as a result. This would explain why some have this issue constantly and others rarely or never see it. Perhaps it's something seemingly unrelated that everyone experiencing the reboots has in common. It would be nice if Google weren't so tight lipped about this. Supposedly the OTA will address these issues and moving forward it should be irrelevant.

I get this issue at least 60% of my calls (not that i call much). i have made 4 calls today, and 3 of them my phone rebooted during the proccess.
I am returning this to CW tommorrow for a replacment unit, i love the phone dearly but do not want to be robbed for £429 but not being able to take it back if they do not resolve.
It could be a batch issue, or something i guess, but that's not my job to find that out, that's for the people i paid for the hardware/software
I hope i get another unit, and if not problem free at least i can rely on a warranty, hopefully making sure if google slack on fixing this i can get my money back.
If it fixes soon or the new handsets ok, i can keep this lil beauty of a phone

I've had my SNS since launch. My phones has rebooted on me twice. It was right after playing a 3D game. Right after i exited the game the phone rebooted. Funny though, it hasn't happened again.

I've gone back to using my Desire until Google sort this out. For me, any call above 5 minutes has a 50% chance of rebooting the handset.
The handset (running stock 2.3.2 and un-rooted) will on occasion spontaneously reboot as well. Not good.

It is a bug that seems to be very limited in scope but is very serious for those affected. Personally, I've never had it happen to me or my wife.

Thank you for your replies, they were very helpful. I was keeping up with the OTA Bugfix promised by Google for the Nexus S. Although, that was promised almost 3 weeks ago and still no word from Google since. That's one of the reasons why I came here to ask for advice before I bought the phone. Although I'm curious to see if 2.3.3 resolved the issue. I know the 2.3.3 just lists API changed, but I wouldn't expect them to list bugfixes on a list of API changes.
I think I'm ready to buy the phone and hope for the best. I'll probably just get Best Buy insurance just to be safe.

apreichner said:
Thank you for your replies, they were very helpful. I was keeping up with the OTA Bugfix promised by Google for the Nexus S. Although, that was promised almost 3 weeks ago and still no word from Google since. That's one of the reasons why I came here to ask for advice before I bought the phone. Although I'm curious to see if 2.3.3 resolved the issue. I know the 2.3.3 just lists API changed, but I wouldn't expect them to list bugfixes on a list of API changes.
I think I'm ready to buy the phone and hope for the best. I'll probably just get Best Buy insurance just to be safe.
Click to expand...
Click to collapse
Getting the insurance is definitely the right choice. I hope you enjoy your phone and your stay here!

I get periodic reboots on both my phones.
It is not that noticeable, since it often happens when I am not using the phone and unless I glance at it and see the start animation, I may be unaware of it.
But it has happened during a call as well (couple of times on each phone) and then it is definitely noticeable.

I have this bug... not during phone calls but random reboots. 2-3 a day. I hate it but its tolerable.

Weird, I don't have this bug

If flashing a custom rom, the problem will be solved? Since i am considering if i should get Nexus s later on.
Thanks

android on HT-01a

Just over a week ago I saw three used Docomo HTC HT-01a phones (Raphael 100) for sale in a used electronics shop for 2000 yen. That's about $20. I've been successful in getting Linux and Android to run on all sorts of things so I thought I would see what I could do with one.
Luckily for me there was already a rom in development.
The first thing I had to do was flash the bootloader. That was pretty easy using the ActiveSync software. Then I downloaded the Windows Mobile 6.1 English Rom from HTC. I tried out a few other custom roms but really the one from HTC was the best I just needed English instead of Japanese.
The new Rom was able to connect to Docomo and everything set up nicely.
Then I came back to XDA to get Android roms.
I tried 2.1 first and it didn't work so well. If the phone fell asleep it would not wake back up. If I tried to make a call the call would only last for about 30 seconds until the phone would quit on me. On top of that I would actually have to take the battery out to reboot the phone. Also, if I plugged in the charger the phone would be fine, but if I unplugged the charger it would crash.
Then I tried the FRX06 and it was much better but not that much. The phone could do some things and I could actually make a call. I set up Skype and Sipdroid to turn the phone into a wifi house phone for my son and things seemed ok. But it required care, a lot of care. I basically had to look after the phone. If I didn't use App Killer and do something with the phone about every 20 minutes then it would crash.
A couple of days ago I put in the FRX07 and this is a huge improvement. The phone can now basically last all day and won't crash. It still needs to be plugged in frequently but I guess thems the breaks. Skype and Sipdroid both work well but they seem to work best if only one is running at the same time. Also the official Skype from the market is broken so I went to Freewarelovers to get the old skype and it works fine. Don't use anything after 1.0.0.84. All the 2.0's are broken.
Anyway, FRX07 really seems to be a winner. I went one whole day using only this as my main phone and it gave me no problems besides wanting lots of energy. I didn't have to reboot or fall back to WM 6.1 for anything. I did have to be patient when looking up a few things on the internet or using the new app but it was still faster then WM would have been. I did find that it functioned better if I turned off animations and streamlined the homescreen.
Now I just wish that I could replace WM completely with Android or at least install android onto the internal memory and have the full use of the SD card. I seems like there is enough memory for that but I may be wrong.
Also, it looks like the screen turns off when I hit the power button, but I think the OS still thinks its on. It still gets hot and uses more power than it should. I don't know exactly what's going on there. I'm more of a hardware guy than a software guy so I noticed. It isn't a big deal but that might be where the battery is going.
Anyway, thanks to the new rom I now have a $20 wifi phone for my house and a second phone in case my Xperia X10 ever dies on me.
Thanks a bunch to the developers.

Have you tried Gingerbread alpha yet? The panel collapse code is still being worked on; the system just turn the display to "0" instead of "off". Will require a devs expertise to get this working. At any rate, there is more in the TP android threads and it seems arrrghhh is quite the tester and occasional team player from time to time. Can't blame him for being upset at the noobs as well as me sometimes. There are still some issues for our device that are still being worked out and others that are being looked over. Glad you got around to checking FRX07 out and that it works for you. Some haven't had that luxury yet and others are still lost in the abyss. Give it a once over if you'd like to get a preview of gingerbread on your device! It would be recommended to make a backup of your microSD IF you have a good configuration.

Thanks. I'll check out the 2.3 when I get a chance. So far the most use the phone gets is when my son watches Thomas the Tank Engine videos or plays a Thomas game. He's almost four but has already figured out how to do that!

[Q] Frustrating One S sensors locked?

Greetings all. I'm not convinced my problem is specifically related to the One S, and I certainly haven't got anywhere near rooting yet, but you Guys are expert at nosing round in the bowels of this phone & the OS, and I'm getting totally flummoxed as to where I've gone wrong.
I've owned this phone since June and it was originally locked to O2, was unlocked and used on Giffgaff, an O2 offshoot - probably irrelevant. One of the apps I particularly wanted to use was Google Sky Map, duly installed and run successfully for a day or so. Other apps installed, as one does, but when I came back to Sky Map, the app was frozen, as were seemingly all compass function apps.
Various uninstalls & reinstalls later, a system reset and a factory reset and this function still was inactive. Returned to HTC for fixing. No better - all worked OK for a short while then stopped. Returned again and this time internals were swapped ,but now the microphone wouldn't work. Third return and an unlocked sim-free handset was returned.
As soon as I loaded my profile from Google, initially it worked, but later most of the sensors again seemed to fail. I've tried the full factory reboot then logged in with a totally new Gmail account, but no change. Phone Tester app shows only readings from proximity and light sensors - no gyroscope,compass, mag. field or accelerometer. Accelerometer did show one set of readings this morning, but nothing since. Lookout AV has always been installed. Incidentally, almost exactly the same profile worked perfectly well on my previous phone, a Wildfire S.
Should I shoot myself or the phone? I admit I'm not any sort of phone expert, but I don't think I'm that dense as to so consistently screw this thing up.
Any ideas people please, in (moderately) simple terminology?

Ok maybe you could shoot google, maybe its a fault by them.
If I helped in anyway please hit thanks

Thank you for the oh-so-helpful response.
Just in case one of the myriad readers of this thread should have just a quiver of interest ................. I believe I've found the answer.
It's always been difficult to pinpoint the problem, and certainly HTC haven't twigged what's happening, as before I sent the phone back to them I TOOK THE FLIP CASE OFF!
That's why it would work for a short while after return, until I replaced the case. I can only guess there's something like Carbon Black in the plastic back shell, and that's what's been interfering with the sensors.
It may also be relevant to the big Home Button problem, with the screen flipping between Home & Helicopter views. Has anyone investigated whether there could be sufficient signal degradation to trigger this problem caused by the use of a case?
Sweetness and light to all.

I spoke to an HTC rep, and he said they would not give an unbranded handset back. If that's the case, I want my phone unbranded. I'll take it to them and hopefully get an unbranded one.

Well good for your HTC rep. They can't go giving out unbranded sets like that. What is the World coming to?
Notwithstanding - the previous clutter of O2 apps was pleasantly noticeable by its absence as was the O2 splash screen.
What a lucky little customer I am and it's only taken 4 months to sort out.

[Q] "Retroactive Bricking" or "spontaneous" hardware fault?

PSA: *This will be crossposted in xda HTC One X and HTC One X+ forums, I hope cross posting is allowed, haven't seen it mentioned in rules.*
Hi all,
Quick disclaimer: I've been lurking parts of xda now and again for a couple years now, have flashed a couple of phones and tablets now and again for mainly practical reasons, recently getting more interested in it as a ""fun" interest or "hobby".
SO: I am very aware that this is my first post, the rules, search function, etc. ..
BUT: After extensively searching both google and specifically xda to help me resolve this issue *myself*, I decided to create an account and post. I'm sorry if this Q should have been put in the newbie thread, my assessment was that it probably has no place there.
ALSO PLZ NOTE: What was meant to be a succinct summary and question somehow turned into a condensed but complete rundown of events, so here is a...
TL;DR:
- Replaced HTC One X+ display/digitizer unit myself, ran fine for 5 weeks.
- Then: flashed twrp 2.7x or 2.8, not sure anymore, before installing Android HD Revolution 33.1 by mike1986, and following the official instructions, which ran great for about week until my phone spontaneously BRICKED THE F*CK OUT COMPLETELY.
(yes, true brick, paperweight, robot-corpse, whatever)
=> Question: IS "RETROACTIVE/RETROGRADE BRICKING POSSIBLE/A "THING"??
If so, what could I have done wrong? (POSSIBLY something to do with a bootimage of firmware that I was sure I had the up to date version of... dunno though).
=========================================================================
About 6 weeks ago:
- Cracked the display of my HTC One X+ badly by dropping it onto concrete-type floor at a rave/party
=> Decided to try and replace it myself, researched for a good while (talking several days here, 90s/00s kids),
=> Decided to replace the display/digitizer unit myself to save money and gain knowledge.
Repair process was challenging and nearly as nerve wracking as playing the WSOP (not kidding, have played it three times), had an issue immediately after putting it back together where it suddenly wouldn't charge AT ALL anymore (NO LED), and overheated, and had unusually fast battery drain of its remaining charge (which never ran out completely before resolving that issue, since I kept turning it off whenever possible).
=> Took it apart and put it together again XX times until realizing the power switch flex cable kept slipping out of its two (jawbone?) connectors during putting it back together (I was doing something wrong with the flex positioning).
=> This resolved the issue.
=> Felt like a hero and that I win at life (since this phone has a rep as being hard to meddle with, and this was my first time even opening, let alone taking apart a smartphone).
=> Continued joyful phone shenanigans for over one month.
=> THEN: Decided to root it, mainly because there was a particular app I wanted that required root ("Quick reply for Whatsapp/Pushbullet", for the curious).
My previous, very limited rooting/flashing experiences =
- Google Nexus One (CWM/Cyanogen) a few times, years ago
- Galaxy Tab 10.1 (CWM/Cyanogen 10.1 ages ago, TWRP/Omnirom Kitkat 4.4.4 recently) a couple times.
So, did my research (or so I thought..?) for this particular custom ROM, decided to go for Android Revolution HD for HTC One X/+ 33.1 by mike 1986 (because it looked fckin awesome, and it was, while it ran) and loved the sh*t out of my "new" phone for about a week. Especially the vastly improved battery life seemed almost surreal, a big deal for a fixed-battery phone.
Then, ONE FATFUL EVENING in a bar, I remember looking at my phone and seeing 35% left, (days before it would've been an amazing 70-80% on an avg. day), which may not be relevant as it was my birthday, so had been using it a lot that day => may be a moot point
- Next time I looked at the phone ( < 1 hour without active use for sure) it was dead.
"Hmmmm," thought slightly drunk me. Whatever, charge it later, weird sh*t happens.
- Got home later, charged it over night after booting it with usb cord attached (mains).
Seemed normal, I even set an alarm.
=> Alarm never rang because it was in a powered-off state again come morning, despite all-night charging.
=> It booted to HTC logo. Seconds later, it turned off again. Held down power again, all I saw was the soft touch buttons flashing red a few times. After this it unexpectedly became (or was secretly crowned):
!! COMPLETE AND UTTER FCKNG KING BRICK OF BRICK COUNTRY AND ATTACHED TERRITORIES !!
No power on with or without volume up/down held for whatever amount of time;
No charging, no heating up when "charging";
No LED in any colour or flashing frequency, ever;
No response after hours and days of charging on different USB cables on PC/wall socket;
PCs and laptops don't register a sign of anything when it penetrates their port parts, etc etc...
...
.Even that semi-mystical bright-light-exposure-while-charging "light sensor manipulation" thing (which apparently worked for a lo of people with similar issues) did nothing for the cause.
Promotion: *Paperweight status successfully acquired.* Yay.
=====================================================
Now, obviously my first thought was that the power flex that gave me trouble during display replacement probably slipped again., somehow (I had taped it down solidly I thought).
=> SO I opened it once again, flex position seemed ok, but I wasn't sure of its functionality as it did look kind of battered from the somewhat unprofessional repair I had conducted on it (which I openly admit to, though I really did try my absolute best).
- Spontaneously took mainboard/battery combo to a local independent phone/accessory shop after being told they'd take a look for free
(I was in there was in there buying a microsim adapter so I could use my ancient Nexus One, since my GF has my old S2 now, which she kindly offered back, but its hers now, so nah. Great phone though.)
=>Shop's advice echoed my thoughts: Flex cable may be screwed, I may have damaged it by bending in the wrong direction/too often, and that damage somehow didn't manifest until much later. I didn't mention the recent rooting + flashing as I deemed it irrelevant at the time.
Their secondary thoughts: Battery or mini-usb port fukt, (which would require soldering, which they don't even offer).
=> SO, feeling confirmed in my layman's assessment, I cheaply got a pristine new replacement flex on ebay, double checked all videos/tutorials, implemented the damn thing with considerably more skill/experience and even higher anticipation. What happened next was shocking:
Absolutely nothing, obv.
=> Did an additional epic f*ckton of internet/forum research, found similar problems and some resolutions, but no real answers, probably because my main problem translates to a kind of hybrid question.
So here I am now am with my core question:
Is it possible to FULLY brick an HTC/any smartphone but not become aware of this until one week later, when the device dies OVER ONE WEEK of reliable and amazing performance?
(and if yes, what aspect/stage of the flashing process is this likely related to?)
If the answer is NO, it must be a hardware fault with probability rank (I think)
:
1.) Battery dead for whatever reason
2.) Mini USB OR mainboard/integral component (equal rank as not sure), possibly caused by incompetent repair, but why or how would this express itself over a month later??
3.) Other, which I'm not aware of.
While researching new ROMS for the N1, I realized that I may have messed up on the "bootimg part" of the flashing process of the Revolution ROM, a part I found v. confusing in the instructions, even after rereading them many, many times. It was about the most recent firmware, which I was pretty sure I had anyway, since it was unrooted before and I do remember installing some firmware updates over the air.
I still did my best to follow the instructions though.
=> Maybe this has something to do with it, i.e. the hardware can't accept a charge because the software allowed it to become too uncharged (a fairly paradox concept to me, but apparently it can happen. Guess it's like a BIOS-type thing).
Thank you for anyone who read this far!
As it stands, I refuse to give up hope so soon after experiencing that rush of having fixed it myself.
Any specific or general help, tips, hints, pointers, replacement phones (One M8 or S5 plz., Iphones will go straight on ebay) would and will be greatly appreciated!!
The obvious choice is to get a new battery and see what happens, but I'm not sure if I wanna sink any more money into this phone, only to later find out the mainboard is at fault (not worth the money replacing), AKA "get a new phone without a contract", which would more than suck for me financially atm (Im ignoring my N1 here, which I love, but don't wanna be stuck with, esp. as it has the standard-issue broken power button (which I actually had repaired once under warranty, back in the ol' days of yore some prefer to refer to as 2009.
So guys: What's my move, if there is one, besides going to a local/online service centre (I live in Germany btw.) and probably paying unproportionate cash money to even have it looked at?
Cheers, thanks, merci, danke
PS: Just saw the polling function, so I attached one just for the hell of it, to see what happens (never used one before).
If you feel both qualified AND so inclined as to pass judgement on this here serious business, please indicate what you think may be the cause of my issue.

*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!

Keyboard issue on brand new and warranty replacement - long time returning user

Hi. I'm not your typical noob person, I simply haven't had an issue I couldn't find a solution for that required me to come to XDA in a very very long time.
Long story short, I got the Galaxy S8+ 5G tablet brand new from T-Mobile in less than a week.. immediately noticed issues with swiping/glide on both Samsung and Gboard keyboards(Gboard is my STRONG preference for a long time now)
This is brand new out of the box, before a screen protector was added or any apps installed. Still did all the standard trouble shooting - installed update, no dice. Force closed each keyboard, wiped cache and data on each keyboard, tried turning sensitivity off and on and.. no dice. Restarted into boot mode and wiped cache.. most of these things not really something that should apply to a brand new out of the box tablet except update and factory reset - both of which I did, neither of which, nor anything else has helped.
I even added a tempered glass screen protector thinking it's TOO sensitive, and even after that, and again trying to toggle sensitivity setting in the settings.. still just will not swipe.
I type this currently on my Samsung Galaxy S20 FE5G absolutely flawlessly. I can type without looking at the phone at all and type near perfect accuracy with just the occasional need to choose a different word in the suggestion bar.. that is using Gboard "glide". The tablet using Gboard bloating mode is almost an identical match to the size of this keyboard and would make it a nearly *perfect* way of typing just as quickly and accurately on the new tablet.. I understand that some of the accuracy comes from use of the keyboard and locally stored into but.. the tablet types gibberish half the time. If I push FAR harder than I should have to while gliding, a few words may work.
Called T-Mobile Saturday, had a warranty replacement sent(God I didn't want a refurbished device) because the only natural conclusion I could come up with is the digitizer has an issue, maybe during shipping.. etc. I don't know..
Got it last night, booted it up, this time I made them include a "invisible shield glass fusion+" screen protector which went on flawlessly and should have no effect on typing at all.. and it's got the same EXACT issue. Maybe a HAIR better, but still completely unusable in my opinion.
I want this for work, the tablet and this phone and a 4k Chromecast, with features like dex, second screen, etc.. there's just about no scenario I can think of where this WON'T be beneficial in any support scenario..
T-Mobile already wants to give me the tablet for free, I've had so many issues with them for so long they switched me to a "business select" package only certain managers can apply, and I get unlimited everything for each device at $25 per device.. forever. No matter how many.
No discounts for auto pay or mass numbers or.. just a flat number that beats the company I was going to switch to when I unlocked my phone 12 days ago.
But I've been a customer customer for 8 years and a T-MOBILE customer since before the first iPhone smartphone was released.. even a few years before that when the best phone you could get had a slide out keyboard and basic touch functions..
So they are supposed to be calling me within the hour, I expected to see numerous threads or posts about this issue, because clearly it isn't ME..
I find some other links I've tried fixes from like:
Strange Gboard bug temporarily breaks glide typing, here's how to fix it [Update]
Over the past 24 hours or so, users have started noting a strange issue with Google’s Gboard keyboard on Android,...
9to5google.com
And see this post of Galaxy phones describing exactly the same issue
https://www.reddit.com/r/GalaxyS22/comments/u8y4cz
and describing it happening with a specific update..
I've got 2 devices, the first is brand new and factory reset as of last night, has a glass screen protector, and the refurbished one in front of me with the same issue.. I've restored data so I can continue using it, but tried all the SAME fixes and nothing.. and T-Mobile is calling in 45 minutes or so.
Obviously I'd like to keep the brand new device rather than the refurbished one- but IS THERE A FIX, or anything I can do with them on the phone.. I got a Bluetooth keyboard and mouse and aftermarket case.. I can type using the keyboard obviously, but I typically can type WAY faster with Gboard the way I am on my phone right now..
I tried doing searches on XDA but it seems like their search functionality has changed for the worse in the years I haven't been here.. that or I can't find the advanced search and forum search I KNOW I used to use daily.. not in the app, the mobile page, or desktop version.
And because it isn't worth it's own post I'll ask one more question -originally I had them send me a Galaxy tab 7 FE 5G becauseb the S20 I'm using still works so well and it was only $100 if I added the line.. and it's just an oversized worse version of my phone.(but don't recall it having this issue now that I think about it) Which is why I'm here now with this tablet..
The problem created by that is I can't tell the pen for that tablet and the new one apart, and here https://m.gsmarena.com/compare.php3?idPhone1=11342&idPhone2=10922# it is showing the new one has less latency, Bluetooth, etc..
Part of the reason they are calling this morning is they were like "oh, just keep the Galaxy tab 7 for free, on us"
Me: "I don't want that oversized garbage, that's why I'm ordering the 8+!"
T-Mobile guy: "Oh, well then return the 7 and you can have the 8+ on us!"
Then I've been trying to get a shipping label for 11 days now, only to find out that he never put in the system that I wanted to return the device and he already voided out the equipment plan for it.. meaning I'm stuck with a tablet I don't even want- and can't tell which s-pen is supposed to be the better pen!
I mean, the chance I'll lose one is so high I won't return the pen and keep it as a backup.. but.. I'd still like to know how to tell the difference, when I attach either one it connects with no issue and I can't find anywhere that shows the pen type connected!
I'm so sorry this is so long, but like I said.. I normally do not need to come here and get my issues resolved myself, it's what I do for work.. and I haven't needed to root/rom a device in so long that I just kinda.. stopped.
(But I'm not going to lie, I got super excited when I came here and there seems to be the option to root/ROM and that it seems like a well supported device in that way! I've kind of dreaded KNOX because previously I never could.. but I'll look into that later once I fix my CURRENT issues..!)
Best I can do as far as pic of S-Pens https://photos.app.goo.gl/pfqKMiiG49L21gx7A