yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Neverendingxsin:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

To fix the dark Rootbox issues I had to flash the Rom again. It caused system ui force closures and slow downs
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlpatter:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Flash gapps

---------- Post added at 08:54 AM ---------- Previous post was at 08:53 AM ----------

Flash gapps after
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Neverendingxsin:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Okay maybe my recent post didn't fix it. But I think I did now after a few reboots and wiping cache a few times. If the force closures and slow downs continue then I'll do a clean install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blublazx:
new nightly is no good. Phone wouldnt boot I had to reboot it multiple times something like 10 then once I got it up it freezes when trying to open up anything. Now froze so bad had to reboot and it wont reboot again. Once I get it back up I am going back to the last stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cyberpac9:
Was really interested in trying the new nightly, but sounds like I might hold off - too many issues reported.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Full wipe. No issues at all so far. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blublazx:
I didnt do a full wipe so I may try again with a full wipe this time and see. Loved the dark root feature looked good. Will report back later.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlpatter:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Ditto
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Neverendingxsin:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Oddly enough my force closures and system ui issues were all related to the hue theme. As soon as I changed to system theme my nova launcher sped back up

I am not saying that the theme is bad. I'm just pointing out that on the stock theme things are no longer slow.

Edit: after switching to system theme and then switching back to hue it's perfect. I haven't had a chance to reboot and see if that messes things up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
It's always better to try a full wipe (with formatting system) before reporting issues. If you use TiBu to back up your user apps, when setting up your phone let Google restore the apps and use TiBu to restore user app data only. I can set up a clean wipe in about 30 mins.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djmouse:
the new nightly is fine to install if you do a clean install of it,but changing the kernel is when you hit problems from what ive experienced,tasks newest underwear kernel will work but the only reason to flash that kernel is for the sound patch but it still wont work im not sure why it wont let me install fauxs sound app,but ive reverted back to my back up because ive been spoiled with the sound,just curious why fauxs app wont work with the stock kernel, if anyone knows enlighten us please.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wcoast:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Stock kernel requires FauxSound patch for FauxSound to work

Some people have reported issues with FauxSound 1.0.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kroz:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

sorry to hear that mate, just test further and let me know any findings, ;)

i am still using Hue together with dark rb for better dark experience,

many users in i9100 are having the same setup as mine, Hue + dark rb, and we never encounter any crashes of system ui,

i also make sure that dark rb will not mess with Hue in terms of codes of font vs background issue,

;)

Sent from my Hue themed GT-I9100 using Hue themed Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djmouse:
ok understand that,how bout tasks kernel it has the patch but when i flahsed it, fauxs sound app was gone and it gave me error dling it?something in the build prop maybe?

---------- Post added at 01:07 PM ---------- Previous post was at 12:54 PM ----------

one more thing can anyone confirm the lean kernel is working with the new nightly?and if so a link to where to dl it, thanks

---------- Post added at 01:10 PM ---------- Previous post was at 01:07 PM ----------

i had the hue green 2.5 running with the dark root box it seemed fine only ran it for about an hour,but i love the green hue theme thanks

---------- Post added at 01:46 PM ---------- Previous post was at 01:10 PM ----------

ok i dont know what i did different but from my back up,i flahsed the new nightly with gapps went perfect,then i installed tasks kernel and it went fine and fauxs sound patch is working everything is perfect as of now ill let it run for a few hours report back but i think its fine.thank god
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Neverendingxsin:
Alright i did a full clean install, formatted system, wiped data/cache/dalvik. Then restored my apps and stayed on the system theme for a bit no issues yet.

Then i turned dark rootbox on, still no issues, then put the hue blue 2.5 on and no issues. But as soon as i reboot and it boots back up the system UI force closes, and i can't do anything without having to pull the battery out. (this is with dark rootbox and hue blue 2.5) the other odd thing is that my background gets reset somehow as well during all of that. Sometimes i'm able to get the pulldown to trigger and i see that every icon is still hue blue themed except for the data one (the 4G/LTE icon) that's the only one that shows LTE on it instead of the 4G from hue blue 2.5.

I just now fixed permissions and it booted back up with a system UI force closure but i was able to get past it. What's weird is that in Nova none of my widgets were loading up, i mean they just say at "loading widget" all of my apps are saved on the normal internal memory, nothing is on the external sd card. Ummm then i was able to fix that, except that beautiful widgets would not show ANY of the font/weather icons that i already had installed including the default ones.

I'm basically lost as to what the heck is going on :( I haven't touched the kernel or anything, and its a completely clean install. I didn't have any issues until i tried dark rootbox and hue blue 2.5. This is on D2VZW i535 if that helps.

Note: I have not touched the dpi or xposed settings. I only set up my quick tiles and changed the battery to rootbox speedometer
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shadowleo85:
new build does not work with lean kernal 2.9 either... flashed it and device wouldnt boot at all... i didnt have any issues on the build doing a dirty flash though... ill see what happes when i use dark rootbox aNd report back BUT STAY AWAY FROM LEANKERNAL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

You flashed the wrong kernel. Read a little bit. You now need a new kernel based on 3.4 kernel source. The newest build in his test folder for VZW works perfect. I've been running it for 12 hours now. His 2.9 kernel is based on the old source which isn't compatible. Here's his test folder link. His 3.0rc2 kernel, the 3/18/2013 build is a 3.4 kernel. http://imoseyon.host4droid.com/s3/aosp/test_builds/#!/view=details/lang=en/sort=na and if you don't have a d2vzw, just wait a bit for stuff to be updated. But don't go in a thread saying stay away from something because you flashed the wrong thing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shadowleo85:
if 2.9 caused problems and im telling people to stay away from it thats not a problem... seems more like a solution so people dont make the same mistake i did in flashing the kernal that was available to them... so again i say STAY AWAY
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Neverendingxsin:
Okay so a little update, i froze nova launcher and rebooted and i didn't have a system UI force closure upon boot but i did have a system force close and i noticed that the wallpaper i set was reset to a plain black one on the stock launcher instead of a wallpaper from the "wallpaper" selection, not RB wallpapers just regular wallpaper.

I'm half tempted to format my internal card but i don't see how that would solve anything.

Edit: bumped SD read ahead speed from 128 to 2048 seeing if that helps at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Its not Imoseyons fault you flashed a kernel that wasn't compatible. So don't say stay away from lean kernel, maybe saying make sure you flash a compatible kernel would have been more appropriate.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krntehknik303:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

So a kernel with 3.069 base will not work with the latest nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Correct. Must be the new 3.4.something kernel base.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bakasam:
Dirty flashed from the previous nightly (not 3.91). I was having the system UI crash/reboot when I turned Dark Rootbot. Ended up flashing another kernel (Task's) and phone seems to be running fine now. So for those of you having issues maybe give that a try:highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shadowleo85:
dark rootbox seems to be working out the box over a dirty flash... only issue i ran into was in the gallery it would open photos until i locked and unlocked the device
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djmouse:
i guess im first to dl the new nightly?

---------- Post added at 02:34 AM ---------- Previous post was at 02:26 AM ----------

bootin now

---------- Post added at 02:45 AM ---------- Previous post was at 02:34 AM ----------

i did the incremental dl installed fine,still no support for fauxs sound tho,gonna put on underwear and then donate to these guys for all there work thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

New lean kernel (v5.0rc3) out as well... running good. See Rootz for link.

Will try with new 3/20 nightly in a bit... Downloading now.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HoudiniJr:
Hey bajee, was wondering if it would be ok to put up an Mms apk that I have modified from root box that will help with compression.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxsicknessxx:
so new tasks kernal should be working? I get no boot when I flash kernal but if flash rom im fine.... ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djmouse:
task new underwear kernel works with this rom,the one that says not to use with any other rom that was before this rom was out,tasks kernel not ktoonzs
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlpatter:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Is there a trick to getting incoming calls sound to work when head phones are plugged in? I drive an scion xb and headphones I can hear the caller better....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbrannack:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Is anyone with the Verizon variant able to get either nightly 3/19 or 3/20 to run smooth. They both shut my phone down. I can't even get it to not freeze long enough to get a log. If anyone has any ideas I would really appreciate it. 3.9.1 is running 100% perfect. Love this ROM!!

Edit: I'm using stock kernel.

Sent from my SCH-I535 using Xparent

BlueTapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radioraheem:
Just for the record: I flashed latest nightly over 3.9.1, did not wipe data, wiped cache & dalvik before installing rom, flashed rom and gapps, wiped cache & dalvik again, no issues at all for over 24 hours. Dark Rootbox turned on for me fine. Glad I've stuck with the stock kernel :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbrannack:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Are you on Verizon by chance. If so can you use your gallery?

Sent from my SCH-I535 using Xparent BlueTapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Neverendingxsin:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Gallery works fine here on Verizon but I clean installed the 3-19 nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRJ442:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

My gallery is working just fine too. I think I saw someone else with gallery issues somewhere. Rootz perhaps. Think I'd either try clearing data on the gallery app or do a complete wipe and reflash if you didn't already.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Neverendingxsin:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

On the latest nightly my screen froze when I tried pulling the notification bar down from the lock screen. Oddly enough my music kept playing normally just couldn't skip with volume buttons but I could adjust the sound and just couldn't turn on the screen. Only fix was a battery pull

Trying lean kernel 3.0rc2 to see if that fixes the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Have you tried the newer version of lean kernel; v5.0rc3?

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Neverendingxsin:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

I just saw that a few minutes ago, I plan on flashing it once I leave the gym. Rc2 seems to be doing great so far. Any major changes between the two?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Not sure... Some have been having wake lock issues, but I've been fine.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Demiurge7:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Running 3-20 w/lean 5.0 rc3 so far with no issues today. I dirty flashed over 3.9 (wiped dav/cache before and after), and am super excited for additions. With a power widget toggle for screen timeout, and dark root box; this rom is officially perfect and then some! Totally donating again today... the speed at which you guys release updates and add options - without losing stability is just so impressive. Can't say it enough.

Also, Jase holo mms for 4.2.1 continues to work with all builds for me (can't live w/o popup mms, if this was not inherently added already)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shadowleo85:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

I wish they would update lean for the tmo and att s3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I have been getting msm_otg wakelocks after charging my phone using my pc. After a reboot the phone sleeps fine, but as soon as I plug into my pc and unplug again the msm_otg wakelock keeps the phone awake 100% of the time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

You can run the Verizon AOSP or TW lean kernel builds on AT&T or T-Mobile just fine. Been running the most recent version of lean kernel (v5.0rc3) just fine on AT&T since last night, with no problems, and it's labeled a Verizon build. See Rootz thread for newest links.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bitemeoftn:
If you go to settings/device options then tick use dock audio on USB when you have the phone plugged into the car charger and sound going through the speakers your calls should as well. I do the same thing and it took a second to figure out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlpatter:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Thanks, that worked perfectly... That was my only issue with this ROM and now finding out the issue was me... This is one great rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbrannack:
Re: [ROM][4.2.2] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Could you give me a quick crash course on how to flash a kernel. I'm pretty sure you flash it just like a ROM. I'm just not a 100% sure. I can't seem to get either one of the new nightlies to work with stock kernel. I'm on Verizon and have had no problems until these new builds. Also I've been looking on Rootz and found the thread for lean kernel I just have no idea how/or which one to DL. Super confusing. Any help would be greatly appreciated. Thx

Edit: OK my dumb ass found lk rc5.0. So if you could just tell me how you flash this I'd really appreciate it.

Sent from my SCH-I535 using Xparent BlueTapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
I just download to external...reboot to recovery..clear caches...flash kernel and reboot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
What is the difference between leankernel 5.0 rc3 for Verizon and the ATT 2.9?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
A fix with the new stuff? or a revert? I don't know who BMC is... I'm guessing I should.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spacemonkey333:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Please leave me alone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bajee11:
A fix. And yes, you should know who BMC is ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bikrame:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

You mean on todays build(1/29) ? Or I have to wait till next build? I used it a lot so if its not workin on todays build I will wait.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bajee11:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

This is when changelogs comes in handy. Checkout changelog and you'll find out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Hey i know bluetooth music streaming is borked but bluetooth for calls works. But when I try turning it off it hangs and just sits there saying turning off bluetooth. Phone works fine just this issue. Anyone else? Andbthx bajee for the most amazing rom perfectly suited for my needs. And my wifes, daughters and dads phones. Rb all day babayy!

ROOTBOX Charged JB 4.2.1 fueled by Ktoonez 747 octaned kernel SGS3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

One thing I did to remedy the Bluetooth sticking like that is create an auto off profile in tasker. Mine is set to turn off after five minutes. No hang ups done that way. Hope that helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxsicknessxx:
Before on 4.1 when I flashed something nothing happned (as in it was ok)

Now every time flash something like keyboard (extra not system) it says upgrading apps. Every time. Is this part of 4.2 ? I don't know about

Seems off

As to that coments on inverted apps. I see your point now I never knew that.

Now maybe we can post that at the front of the page (some inverted apps mod system apps and stuff) or something so we all know why.

Thats a great reason to not support inverted apps and I understand in fact I agree im reflashing right now clean install we see how it goes.

Im starting to think its my computer or something giving me stress for one im conected to usb all the time and also I get hardware device id is missing all the time. only way I fix it is to restart or to install other drivers other then the right ones.

Its not a huge problem but makes me wonder. sucks having issues when I didn't on 4.1 builds
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DigitalUnderground:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Every time u wipe cache/dalvik (I assume u do this when flashing extra mods) u will get the updating apps when u boot back up... If I remember right... It was like that on 4.1 as well but I may be wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Force stopping bluetooth share in settings-->apps will usually work as a temporary solution to this. Also, deleting the configuration files in /data/misc/bluedroid sometimes fixes this more permanently, but you may have to re-pair your bluetooth devices afterwards.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxsicknessxx:
nm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxsicknessxx:
getting help else where think problem maybe deeper then just the rom. (which I had hoped) no one wants system errors :(

I still ask if anyone else gets the error I get (posted bellow) thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dunlap92:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

If you have icon markers then you're not doing a full wipe. You have to wipe data, system and cache....after doing it once I never have to full wipe as long as I stay on the same ROM...just davick cache and install update and gapps 12/12/12.

---------- Post added at 11:32 PM ---------- Previous post was at 11:28 PM ----------

If you're using cwm youll have to go to mounts and format from there...internal card. And I don't use inverted apps or custom kernels.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxsicknessxx:
I get a odd error that pops up so fast I cant read it but when I google it rom stuff comes up... so dunno what means maybe dev will

a window pops up when install or uninstall some apps saying "cananot read data Xposted framework whitelist module error

God my spelling sucksc but its something like that a little error.. its from data/data folder somewhere in there I found the folder its looking for its with a bunch of old app historys which I don't get how they all there (if i did clean install) shouldn't all that be wiped? or does data./ daqta folder never get wiped

its weird certain apps don't go where they should Ive never messed around with anything to deep with my phone I just don't get issues.

In end i think might end up being a bad phone sorry to waste all your guys time with my problems Just *shrug* seeking help where it seems I might get it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bajee11:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

a2dp working in latest nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Go into settings-->module management and press install, that should fix it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Re: [ROM][4.2.1] RootBox Non-development | Discussion | Support [d2att/2tmo/d2vzw]

Already downloading. Thanks dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AnarchoXen:
Flashed 3.0.60-KT747 Kernel last night and CAN connect to my network with no issues.

I tried connecting with the stock kernel using no security and wouldn't connect. GF's Note II, bone stock, connects using security encryption.