I just won a free Samsung Galaxy S Vibrant with Bell Mobility, but which one should I keep? I love my Nexus One, and it seems that there is a lot more development for the N1 right now. I am a rom flashing junkie, love to tinker with my phone, and make update.zip files for fun...
That being said, clearly the N1 is better.. but only for right now. Does anyone have any insight on when the Galaxy will get as much attention? It is on 5-6 networks already after all..
Thanks!
Either way, lets get a rom dump and see what we can play with
fiftyclick said:
I just won a free Samsung Galaxy S Vibrant with Bell Mobility, but which one should I keep? I love my Nexus One, and it seems that there is a lot more development for the N1 right now. I am a rom flashing junkie, love to tinker with my phone, and make update.zip files for fun...
That being said, clearly the N1 is better.. but only for right now. Does anyone have any insight on when the Galaxy will get as much attention? It is on 5-6 networks already after all..
Thanks!
Either way, lets get a rom dump and see what we can play with
Click to expand...
Click to collapse
Galaxy S probably has the better hardware.
N1 will continue to get android releases from google first ... once the Galaxy S is out on all networks and widely sold, I would expect custom rom development to explode for it (and be the same if not better than for the n1)
=> I would keep the galaxy (based on better hardware alone)
i would keep both. you have the best of both world. N1 which is will have the most updated android and SGS which has best hardware at this moment. but with some issues on software. but that will be all figured out. play with both and then make your decision.
BTW, hating on you so much. lucky SOB.
Whatever you do, don't get rid of the N1. Either keep both and hope the Galaxy issues get resolved (GPS AND Compass) or sell the Galaxy. The Galaxy has much faster graphics performance and built in HDMI out via USB but, unfortunately, the GPS and Compass issue make it a no go for a day to day user. The thing about the Nexus is that it will continue to get updates first and,likely, there will be much more development on it. Likely, this will result in much better tuned software and possibly even open up even more functionality. With the core hardware issues of the Samsung, you are at the mercy of Samsung and their track record is not so good. I actually bought a Vibrant (Galaxy S) and returned it.
Hey! I'm a new Nexus One user. I've been using the Galaxy S for a long time and in the end chose the N1 over it. Yes, the hardware on the GS is better than the N1, but really, for me it all came down to keeping the phone that made me feel heavenly -- the N1!
You will be better off in the long run with the Nexus One...
I sold my n1 for the sgs and I'm not looking back.. true Multitouch, memory ,gpu and super amoled was enough for me. N1 was great, but the sgs is better IMO... development is starting pretty well. Especially soon....
if gingerbread is the future of android devices, it suppose to support hardware capabilities that may not be on the nexus that has been around for a while.
i really wanted to buy a nexus, but it seems that when android 3.0 is out - it should be followed by high end devices by HTC and others.
i really don't know what to do here...
gingerbread is said to launch mid november - not a long time to hold off.
but hey, what do think? wait or buy nexus now?
That is Exactly what I am doing! The desire HD looks wonderful, but i think There will be a VERY nice phone coming on T mobile with new gingerbread already there around Christmas....Just my guess
It seems T mobile and Google have some sort of special deal when it comes to android, like getting stock android phones.....and there MUST be a stock gingerbread phone coming soon!
oronm said:
if gingerbread is the future of android devices, it suppose to support hardware capabilities that may not be on the nexus that has been around for a while.
i really wanted to buy a nexus, but it seems that when android 3.0 is out - it should be followed by high end devices by HTC and others.
i really don't know what to do here...
gingerbread is said to launch mid november - not a long time to hold off.
but hey, what do think? wait or buy nexus now?
Click to expand...
Click to collapse
First, Gingerbread will run fine on a N1. Second, no matter when you buy a phone in a couple months another one will come out that is even better. The N1 has an awesome modding scene though.
First, Gingerbread will run fine on a N1.
Click to expand...
Click to collapse
nobody know that for sure...the minimal requirements may suit the N1 but it may lack the ability to perform certain tasks. we've seen it happen with other phones.
Second, no matter when you buy a phone in a couple months another one will come out that is even better
Click to expand...
Click to collapse
true for most cases. to me nexus is different from others by design. that phone feels right. i really couldn't care less about all these samsungs or motorolas that are out there. and other htc devices seem too big like the desire HD that was mentioned.
basicly, the world need a NEXUS TWO!
So you think Google will develop an OS using their development phone, but not all features of the OS will work on the phone they developed it on? I highly doubt that. Google debunked the minimum requirements roomer for Gingerbread, that was nothing but a site trying to get traffic. Do a little thinking on the subject.
If I were getting a new phone soon though, I would wait till the next gen ones come out. I do love my Nexus though!
the nexus one was a success in regard of telling the world "this is what android can do right now". others did follow and it is biting the market share making other mobile OS look like code accidents.
none the less, why shouldn't gingerbread allow "facetime like" video service for capable devices? the technology for that is in the wild. that is only one example. i am sure there are more features just like that.
at this point, maybe it would be smarter to wait.
oronm said:
the nexus one was a success in regard of telling the world "this is what android can do right now". others did follow and it is biting the market share making other mobile OS look like code accidents.
none the less, why shouldn't gingerbread allow "facetime like" video service for capable devices? the technology for that is in the wild. that is only one example. i am sure there are more features just like that.
at this point, maybe it would be smarter to wait.
Click to expand...
Click to collapse
Whether or not Gingerbread includes a facetime like option is irrelevant to how it will run on the N1. Obviously any phone without a front-facing camera will not be able to do something like facetime. Gingerbread itself will run just fine on the N1. Without going into any technical reasons, just think of this. Of all the Android phones out there right now, the top ones are all in the general vicinity of the N1 in performance. If Gingerbread wouldn't run on the N1, then you cut out these phones too which means only as-yet-unreleased phones would run Gingerbread. So on what basis are you questioning it?
You should probably wait though since you don't seem sure about the N1. The only guarantee you can have is that in a few months from now an even better phone will be released. And then a few months from that once again, and repeat... Dual core snapdragons will start finding their way into phones at some point soon. If you're not rushed then just wait and see what comes out.
Hi!
I'd like to know if it's reasonable to get a Note as developer phone for the next two years. (I'm noob to android, not to programming in general.)
I will need a more or less up to date android version. My (pessimistic) guess is that Samsung will upgrade the Note to JB and thats about it. There are some good roms out now and i wonder how the situation will be in one or two years. (Ver. 5.0?) Will the development community pick up where Samsung stops and continue to support the Note or will developers move on to newer phones?
Maybe someone can give me any insight on how much work is needed (was needed for ics) to port a new (minor/major) android version to a device or existing rom? (Anything between 1guy/1week and 4guys/4weeks?)
I know the usual answer is "get a Nexus" but I really like the big screen, thats why i have to ask.
Good to hear that one more person is coming into development of the GNote. Most Welcome. We are already hearing about the Chinese Jelly Bean leaks for Galaxy Note,then android keeps updating. But no matter what, we will have the devices and the development will move on. Hoping to see you soon.
I dont expect note to become developer device, better get a nexus for that
the nexus series are the first to be upgraded and build for developers
nothing beats the note in terms of screen thought
Sent from my GT-N7000 using Tapatalk 2
I wouldnt expect this to have long term development either..Its the only negative I have about the phone but Im happy enough..
I'll be honest though I am pretty sure I'll get the next Nexus simply because development cant be beat that route.
as with all android devices the main dev base will always move on to newer devices when they upgrade, however im sure there will be for a good few years people sticking with the note after all main are locked into a contract or simply havnt the funds to buy a new devices when its released.
I for one will have my note for another 18 months or so, and look forward to using it solidly for deving, i have found it a great platform for app work/running linux/ROM development.
Of cause we dont know what the next big update of android will bring, it may mean that the note no longer has the power to run it etc but thats unlikely for some time (after all even the g1 'can' run ICS).
HansDB said:
I'd like to know if it's reasonable to get a Note as developer phone for the next two years. (I'm noob to android, not to programming in general.)
Click to expand...
Click to collapse
If you want a developer phone, you really shouldn't consider anything other than a Nexus.
Whilst the Galaxy Nexus isn't exactly top drawer these days, it's still very good, and both it and the Nexus S will see Jelly Bean. Whilst I expect support for the Nexus S to drop off after Jelly Bean, the Galaxy Nexus should be good for at least the version after JB.
Regards,
Dave
Is it possible to port over Nexus 4 ROMs (including 4.4 KitKat) to HTC First? HTC has released the kernel source code for our phones. I like the Nexus experience, and don't really want CM. If HTC made Nexus handsets for Google I would have bought that instead, but the minimalist nature of the First really appeals to me.
r00tb33r said:
Is it possible to port over Nexus 4 ROMs (including 4.4 KitKat) to HTC First? HTC has released the kernel source code for our phones. I like the Nexus experience, and don't really want CM. If HTC made Nexus handsets for Google I would have bought that instead, but the minimalist nature of the First really appeals to me.
Click to expand...
Click to collapse
um that isnt quite as easy as you think. porting cm is easier cause our phone has hardware relatives like the HTC One mini which use the same drivers and stuff like that. also our screen size matches the One mini so porting it would be as easy as 1-2-3. it does take time but it will be a hell of alot faster than BUILDING an AOSP rom. to make aosp work 1, you would need screensize and other hardware compatibility, then 2, the rom was never made for htc and 3, there is not flashable zip of the stock rom to base the OS off of, so it would requre alot more work. trust me , cm and and aosp arent much different so dont worry.
russian392 said:
um that isnt quite as easy as you think. porting cm is easier cause our phone has hardware relatives like the HTC One mini which use the same drivers and stuff like that. also our screen size matches the One mini so porting it would be as easy as 1-2-3. it does take time but it will be a hell of alot faster than BUILDING an AOSP rom. to make aosp work 1, you would need screensize and other hardware compatibility, then 2, the rom was never made for htc and 3, there is not flashable zip of the stock rom to base the OS off of, so it would requre alot more work. trust me , cm and and aosp arent much different so dont worry.
Click to expand...
Click to collapse
Since I have no experience porting Android I can't say that you are incorrect, but isn't the binary architecture of applications the same (ARMv7-A Krait instruction set?), the screen is reasonably similar (1280x720 vs 1280x768, or Nexus 4 having 48 extra pixels on the width in portrait mode). Basically, it's not possible to just stick our device-specific kernel (and kernel modules, aka drivers) in there and have everything else just work? Before Android, I had no problems compiling a new Linux kernel for my distro with new options and applications worked just fine.
By the way, HTC promised a 4.4 KitKat update for HTC One Mini which AFAIK is 95% same as our First. Would it be possible to port that ROM? I'd still prefer Nexus though.
Yeah it would be possible to port 4.4 from the the One Mini, I'm not to sure how stable it would be though I'd foresee the usual bluetooth,camera,wifi issues.
Kendosis said:
Yeah it would be possible to port 4.4 from the the One Mini, I'm not to sure how stable it would be though I'd foresee the usual bluetooth,camera,wifi issues.
Click to expand...
Click to collapse
Why would there be bluetooth/camera/wifi issues? We would use our own kernel with correctly configured modules. Both First and One Mini kernel source is out, can't we just run a comparison to see what's different? From the look of it they use the same Linux kernel release, so differences should be few (at least no false positives from different module versions). If newer Android builds will use newer Linux kernel, we can add those differences that we will know of after we do the First vs One Mini source comparison.
I think running the patch program would be an easy way to find the affected source files, as files with no differences will generate no patch lines.
Kendosis said:
Yeah it would be possible to port 4.4 from the the One Mini, I'm not to sure how stable it would be though I'd foresee the usual bluetooth,camera,wifi issues.
Click to expand...
Click to collapse
It's a darn LG. It would like either 1. Take for ever or 2. Impossible
We are using an HTC lol
Sent from my HTC first using xda app-developers app
russian392 said:
It's a darn LG. It would like either 1. Take for ever or 2. Impossible
We are using an HTC lol
Sent from my HTC first using xda app-developers app
Click to expand...
Click to collapse
I don't follow what you mean about incompatibility of LG. It's still the same CPU architecture, and neither the Linux kernel nor the Android operating system are the developments of LG. Explain please.
I'm a computer engineer with a bit of custom hardware core development experience for embedded systems running Linux. I just don't see why there's a problem swapping out all the hardware-specific stuff from underneath Android as long as CPU architecture remains the same.
I have years of Linux experience, just not Android-specific.
r00tb33r said:
I don't follow what you mean about incompatibility of LG. It's still the same CPU architecture, and neither the Linux kernel nor the Android operating system are the developments of LG. Explain please.
I'm a computer engineer with a bit of custom hardware core development experience for embedded systems running Linux. I just don't see why there's a problem swapping out all the hardware-specific stuff from underneath Android as long as CPU architecture remains the same.
I have years of Linux experience, just not Android-specific.
Click to expand...
Click to collapse
well.
1. ive seen people try, its not as easy as it seems.
2. think of it as windows. you install it on your pc, it will take another several hours just to download and install various drivers and software for your hardware.
the thing is not just in the android OS. the os should be able to auto adapt itself to any android capable device. BUT we have to consider 1. drivers for the adreno 305 and the snapdragon 400. we also need kernel/baseband capability. the nexus is pretty much a BLANK device with absolutely nothing on it, and they install a stock kernel and stock rom. we would have to go in and make the kernel work, which hopefuly we can just use a ready built one, and then tweak the rom + kernel to fit the harware, whcih will include the capatative side of the screen, and camera, and everything else, and the ram. and that. although technicaly some of it will be there, its not as easy as you might think.
edit
see, ive worked on an ARMv6 device, and its like much harder than an ARMv7 which has alot of similarities. and mind you, im not saying its IMPOSSIBLE, and im not saying its extremely hard. im sure it can be done, but porting cm form a mimic device like the One Mini would be easier than a Nexus 4, or a Nexus 5 at that.
here. maybe this will make my point clear...its not easy eve for big companies, not just for a single person
http://www.androidcentral.com/why-you-ll-never-have-latest-version-android
Wouldn't it be easier and more connivent to port from the HTC one xl? It does have a good amount of great ROMs
abrahammmmmmm_ said:
Wouldn't it be easier and more connivent to port from the HTC one xl? It does have a good amount of great ROMs
Click to expand...
Click to collapse
its not the ROM, gosh. its the HARDWARE. the One mini has pretty much identical hardware, therefore its easier. if we can atleast get ONE rom ported successfully everything else would be much easier cause the that rom could be used as a base for other ports...
the XL, well the major difference is the adreno 225 vs our 305, plus we have more sensors...
so um...posibly? you could give it ago if you want
russian392 said:
its not the ROM, gosh. its the HARDWARE. the One mini has pretty much identical hardware, therefore its easier. if we can atleast get ONE rom ported successfully everything else would be much easier cause the that rom could be used as a base for other ports...
the XL, well the major difference is the adreno 225 vs our 305, plus we have more sensors...
so um...posibly? you could give it ago if you want
Click to expand...
Click to collapse
I see what you mean, but I wasn't really aware of the great difference of the adreno 225 & 305. When checking it out I only heard there was some very minor tweaks done to the 225 to get the 305. And I'd actually give it a go if it wasn't for how easily this phone bricks, I guess I'll just have to be patient and wait to see what our great devs we've got can whip up for now
russian392 said:
its not the ROM, gosh. its the HARDWARE. the One mini has pretty much identical hardware, therefore its easier. if we can atleast get ONE rom ported successfully everything else would be much easier cause the that rom could be used as a base for other ports...
the XL, well the major difference is the adreno 225 vs our 305, plus we have more sensors...
so um...posibly? you could give it ago if you want
Click to expand...
Click to collapse
Modern operating systems are built on the principle of abstraction layers. The *nix kernels place devices as memory pointers on the filesystem tree (they are not files however in the literal sense), so you can swap out hardware and kernel but maintaining the same pointer names and your upper level application won't care at all, as a matter of fact it may not even know it runs on different hardware from before. The "ROM" that you download and flash onto your device is not monolithic, it's made up of components and the Linux kernel and Android OS, and the rest of the applications are separate parts. You should be able swap out the hardware specific layer, otherwise the design of the OS won't be worth a damn.
From user's perspective however "ROM" means something else, it means a specific set of features, be it pre-installed apps, eyecandy (like Sense or Touchwiz), or other miscellaneous bloatware. Basically it's a snapshot of an environment, which defines the user experience. HTC has their own tailored user experience which they ship with their phones like the One mini, with Sense, and probably some carrier restrictions (like custom restricted Wi-Fi tethering on AT&T). HTC first, because it's a product manufactured FOR Facebook, and marketed as A Facebook phone, has a different user experience from typical HTC products. Samsung has their own tailored user experience with their own apps and Touchwiz. Finally LG makes their own phones too, however the Nexus device they make for Google is a Google product, and Google tailors the user experience for their product. I like Google's vision of the smartphone user experience (I had a Nexus One before), and that's what I want to achieve with the current phone. True, that I could have bought a Nexus 4, however HTC's hardware design allows me to do things that are seemingly impossible with LG... Like swapping the IMEI (don't ask).
Not everybody wants their user experience be of HTC or CM flavor. Please be respectful of that. Arguing against wishes of others accomplishes nothing.
I believe it's clear enough that One mini updates can AND WILL be ported to our phone, there is no point to discuss that further in the context of THIS thread.
r00tb33r said:
Modern operating systems are built on the principle of abstraction layers. The *nix kernels place devices as memory pointers on the filesystem tree (they are not files however in the literal sense), so you can swap out hardware and kernel but maintaining the same pointer names and your upper level application won't care at all, as a matter of fact it may not even know it runs on different hardware from before. The "ROM" that you download and flash onto your device is not monolithic, it's made up of components and the Linux kernel and Android OS, and the rest of the applications are separate parts. You should be able swap out the hardware specific layer, otherwise the design of the OS won't be worth a damn.
From user's perspective however "ROM" means something else, it means a specific set of features, be it pre-installed apps, eyecandy (like Sense or Touchwiz), or other miscellaneous bloatware. Basically it's a snapshot of an environment, which defines the user experience. HTC has their own tailored user experience which they ship with their phones like the One mini, with Sense, and probably some carrier restrictions (like custom restricted Wi-Fi tethering on AT&T). HTC first, because it's a product manufactured FOR Facebook, and marketed as A Facebook phone, has a different user experience from typical HTC products. Samsung has their own tailored user experience with their own apps and Touchwiz. Finally LG makes their own phones too, however the Nexus device they make for Google is a Google product, and Google tailors the user experience for their product. I like Google's vision of the smartphone user experience (I had a Nexus One before), and that's what I want to achieve with the current phone. True, that I could have bought a Nexus 4, however HTC's hardware design allows me to do things that are seemingly impossible with LG... Like swapping the IMEI (don't ask).
Not everybody wants their user experience be of HTC or CM flavor. Please be respectful of that. Arguing against wishes of others accomplishes nothing.
I believe it's clear enough that One mini updates can AND WILL be ported to our phone, there is no point to discuss that further in the context of THIS thread.
Click to expand...
Click to collapse
1. SWAPPING IMEI IS ILLEGAL
2. You are correct, htc has some briliant hardware but the nexus 5 is a monster now haha
3. Go get the stock aosp android rom (4.2 or 4.3) then get a kernel for our phones, and flash it....see what you get and PLEASE let me know if it works cause i highly doubt it.
4. The reason why i duscussed the One Mini ports, is because if they are successfull, you can use them as a basis for for other ports like a nexus 4 port. and it doesnt have to be a nexus 4 port, it can be anything else, just at the moment, so far we have ZERO roms that boot, one bricked phone because of a blind build, and what you basicaly want is a blind build of a nexus 4 rom...so if youre willing to put your phone on the line, go right ahead.
russian392 said:
1. SWAPPING IMEI IS ILLEGAL.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2216371
russian392 said:
1. SWAPPING IMEI IS ILLEGAL
2. You are correct, htc has some briliant hardware but the nexus 5 is a monster now haha
3. Go get the stock aosp android rom (4.2 or 4.3) then get a kernel for our phones, and flash it....see what you get and PLEASE let me know if it works cause i highly doubt it.
4. The reason why i duscussed the One Mini ports, is because if they are successfull, you can use them as a basis for for other ports like a nexus 4 port. and it doesnt have to be a nexus 4 port, it can be anything else, just at the moment, so far we have ZERO roms that boot, one bricked phone because of a blind build, and what you basicaly want is a blind build of a nexus 4 rom...so if youre willing to put your phone on the line, go right ahead.
Click to expand...
Click to collapse
1. Depends, still, don't do it. I don't tell others to do it, and won't say how even if asked. But that's a feature I need hence why I choose HTC.
2. More than I need.
3. When I get around it. Fortunately it's possible to unbrick these if something goes terribly wrong (I have the JTAG pinout for this device). I am waiting on a new JTAG box from the team before I release the pinout to public... Unless of course anyone wants to donate a new box or badass logic probe or a very high speed digital oscilloscope.
4. Of course the One mini port will happen before any others because it will take the least time, however not all of us want to use it.
Hey, i was just wondering why hasnt there been any stock android roms for the note 8 yet? I saw the s9 getting a resurrection remix. Is there any technical limitations thats holding back the development or do people just not care?
Because this phone has a pen ana that pen won't work without source code from Samfail
silveraero said:
Because this phone has a pen ana that pen won't work without source code from Samfail
Click to expand...
Click to collapse
Stock Android - and especically things like RR actually have pretty solid stylus support. And there's plenty of apps that add features like pen-gestures and replicate the proprietary Samsung stuff.
The problem is likely more to do with the lack of treble support that the S9 has - which drastically simplifies the issue of dealing with proprietary firmware and API's.
And the fact that a large portion of Note 8 users have models with locked bootloaders, which prevent the usage of non-Samsung ROMS. There have been several threads detailing attempts at making AOSP or similar ROM's, but all have fallen silent without much to show in the way of progress:
https://forum.xda-developers.com/galaxy-note-8/how-to/unofficial-lineageos-t3686026
https://forum.xda-developers.com/galaxy-note-8/how-to/bounty-aosp-roms-note8-t3686083
https://forum.xda-developers.com/galaxy-note-8/how-to/resurrection-remix-official-note-8-t3756351
Decoding and dealing with proprietary API's and firmware takes a lot of time and luck without sources which Samsung refuse to provide. And the pool of developers that seem interested in such a huge effort for the Note 8 seems to be shrinking.
Aaren11 said:
Stock Android - and especically things like RR actually have pretty solid stylus support. And there's plenty of apps that add features like pen-gestures and replicate the proprietary Samsung stuff.
The problem is likely more to do with the lack of treble support that the S9 has - which drastically simplifies the issue of dealing with proprietary firmware and API's.
And the fact that a large portion of Note 8 users have models with locked bootloaders, which prevent the usage of non-Samsung ROMS. There have been several threads detailing attempts at making AOSP or similar ROM's, but all have fallen silent without much to show in the way of progress:
https://forum.xda-developers.com/galaxy-note-8/how-to/unofficial-lineageos-t3686026
https://forum.xda-developers.com/galaxy-note-8/how-to/bounty-aosp-roms-note8-t3686083
https://forum.xda-developers.com/galaxy-note-8/how-to/resurrection-remix-official-note-8-t3756351
Decoding and dealing with proprietary API's and firmware takes a lot of time and luck without sources which Samsung refuse to provide. And the pool of developers that seem interested in such a huge effort for the Note 8 seems to be shrinking.
Click to expand...
Click to collapse
SO basically no hope for the future? this thing wouldve been a beast with an aosp rom. Thats really dissapointing i was looking forward to android p (
2000ftt said:
SO basically no hope for the future? this thing wouldve been a beast with an aosp rom. Thats really dissapointing i was looking forward to android p (
Click to expand...
Click to collapse
I wouldn't say the situation is hopeless. Just pretty silent at the moment. Some of the groundwork seems to have been done particularly by @SaschaNes and the teams they're a part of. But they've been silent on actual progress of bootable builds for several months now. No clue if they're still working at it or not.
I would say AOSP or Lineage for the Note 8 is achievable it would just take reasons for developers to dedicate their time and effort. And currently, there aren't many for most. Few dev's actually have the device, and even fewer are interested in AOSP for it. Perhaps a bounty might lure one or two - but it would have to be sizeable, and considering the amount of people that seem to have bought this device for the Samsung features - that's going to be hard to organize.
considering the amount of people that seem to have bought this device for the Samsung features - that's going to be hard to organize.
Click to expand...
Click to collapse
This, is the reason the note line, for a while now, has not had the development other Samsung phones have. Add to that , snapdragon and its lockdown , makes it difficult to see the note series as a custom powerhouse.
Sent from my Galaxy Note8 using XDA Labs
Which is a shame, considering the legacy of the Note 3,4 and 5 which continue to have AOSP roms built for them to this day - which has drastically extended the lifespan beyond Samsungs woeful EOL. Sadly devs simply don't seem to have the motivation or time to deal with jumping through the increasingly convoluted hoops constantly being errected by google and OEMs.
Because the note 8 is so locked down