Related
Hey all
Does anyone know if MIUI is going to release a version for the GS4?
CM already told they will NOT be adding any roms for the GS4, so MIUI is my last hope..
Maybe someone made an unofficial release of MIUI-Like rom?
Thanks
This is where owning the I9505 instead of the I9500 becomes a big advantage for people who like non-stock bulds like MIUI, CM and AOKP. Because, unlike Exynos, it's based upon an open-source architecture, it doesn't take much to convert builds to it from other devices. This is shown by the fact there is already a working CM10.1 build for it, created by someone who doesn't even own the phone.
As for the I9500, I'm sure someone will take the challenge up that the official CM team are passing up on. It will just take longer to appear and won't run as well. I don't know the score with MIUI and whether they will bother, time will tell.
But didn't I hear that the official CM team might be having a change of heart? It was back in March when they first said they would pass up on the GS4.
EDIT -- https://www.facebook.com/miuiromchina saying they won't support it for now. Not sure if that will change or if someone else will take it upon themselves to overcome the challenge of developing it for a closed source chipset.
Pagnell said:
This is where owning the I9505 instead of the I9500 becomes a big advantage for people who like non-stock bulds like MIUI, CM and AOKP. Because, unlike Exynos, it's based upon an open-source architecture, it doesn't take much to convert builds to it from other devices. This is shown by the fact there is already a working CM10.1 build for it, created by someone who doesn't even own the phone.
As for the I9500, I'm sure someone will take the challenge up that the official CM team are passing up on. It will just take longer to appear and won't run as well. I don't know the score with MIUI and whether they will bother, time will tell.
But didn't I hear that the official CM team might be having a change of heart? It was back in March when they first said they would pass up on the GS4.
EDIT -- https://www.facebook.com/miuiromchina saying they won't support it for now. Not sure if that will change or if someone else will take it upon themselves to overcome the challenge of developing it for a closed source chipset.
Click to expand...
Click to collapse
Codeworkx and Faryaab are working on the i9500.
I thought I read about a change of heart, like I said. Surprised about Coderworkx though, all the signs were that he had given up on Samsung for good. Have you got a link with confirmation that he is working on the S4? And with the I9505 being the official North American device I'm sure an official build of that will arrive soon enough.
The Samsung devices I currently own (i9100, i9100g, i9300, i9305, t0lte, p5100) are the last ones i will officially support. Some of them might be dropped with the next big android release. Yes, i’ll NOT touch the Galaxy S 4 and whatever comes after it.
Click to expand...
Click to collapse
http://codeworkx.de/wordpress/category/cyanogenmod/
Strong words to go back on but good news nonetheless.
Yes, things doesn't look too good for the i9500
Will Faryaab save my day? who is he?
Pagnell said:
I thought I read about a change of heart, like I said. Surprised about Coderworkx though, all the signs were that he had given up on Samsung for good. Have you got a link with confirmation that he is working on the S4? And with the I9505 being the official North American device I'm sure an official build of that will arrive soon enough.
http://codeworkx.de/wordpress/category/cyanogenmod/
Strong words to go back on but good news nonetheless.
Click to expand...
Click to collapse
https://github.com/CyanogenMod/android_device_samsung_i9500
So there's a chance after all :angel:
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
evodev said:
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
Click to expand...
Click to collapse
It is
XpLoDWilD said:
It is
Click to expand...
Click to collapse
Just a quick question,will it support mediatek devices?
s.sawrav said:
Just a quick question,will it support mediatek devices?
Click to expand...
Click to collapse
Yes.
We have early support for the r819.
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Mayank7795 said:
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Click to expand...
Click to collapse
If you have a working AOSP, it should be available without problems.
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
What about devices that have CM10 only?
lozohcum said:
What about devices that have CM10 only?
Click to expand...
Click to collapse
You need at least an unofficial CM 10.2 / AOSP 4.3.
JoinTheRealms said:
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
Click to expand...
Click to collapse
Building is always worth an attempt...
I used to build my own CM, i'm gonna try to build my own omni too but i'm struggling. I must be doing something wrong with the repo init but I can't seem to find what... I'm gonna update my buildbot first because it's been awhile, and maybe try again tomorrow.
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
That's why its worth scrawling through XDA, going through guides and learning to dev. Nothing wrong with a dev who decides to leave an older version for a newer version. They're doing it for fun and free.
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
As long as there is no hard reason to stop supporting a device and we have someone who is taking care of that device we will try
On the other side - there is constant evolution which sometimes will make it necessary to leave a device "behind" if the effort will become too large
Sent from my Find 5 using xda app-developers app
XpLoDWilD said:
It is
Click to expand...
Click to collapse
Not quite yet... Not until we have roomservice up and running.
(For those that didn't understand what I said - roomservice is the part of CM's repo management system that will automatically sync a device tree and all dependencies. roomservice is HEAVILY dependent on github's APIs, so we couldn't even start work on that particular piece of infrastructure until the project went public.)
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
mattman83 said:
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
Click to expand...
Click to collapse
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
I hope the Acer IconiaTAB A5000 will get supported.
Please, support for RAZR i (x86)
lozohcum said:
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
Click to expand...
Click to collapse
Problem is, every device has its own pitfalls. Some are harder to overcome than others.
For example, the lack of NEON in tegra2 combined with the dependency of newer gapps on NEON really screws tegra2 devices, and there isn't much that can be done about it.
Also, in some cases, the things needed to get a device working aren't in the tree, but are in the frameworks to handle OEM-specific oddities (RIL hacking in opt/telephony, which I admit I'm not too familiar with...) or platform support. Sometimes, old devices get left behind simply because their platform overall is a ***** to support beyond a certain point. (See how MSM8660 devices have been lagging lately, due to Qualcomm pretty much sunsetting that chipset.)
Hi to everyone, got my phone yesterday, rooted unlocked and started off.
I come from some experience in the field (my first phone was an xperia)
and my stats show that I put effort and time into this community and am looking forward to start working on some projects.
(i am merely a builder not a developer)
Would anyone be so kind and nice to give me a picture of current development status?
Are there major bugs being worked on from cm incompatibility?
How come there is only one cm based kernel?
What are the most common problems that have been mostly encountered?
Thanks for your replies, happy to be here, take care
Rudjgaard said:
Hi to everyone, got my phone yesterday, rooted unlocked and started off.
I come from some experience in the field (my first phone was an xperia)
and my stats show that I put effort and time into this community and am looking forward to start working on some projects.
(i am merely a builder not a developer)
Click to expand...
Click to collapse
Welcome to this forum and I hope you'll enjoy working with the community here
Would anyone be so kind and nice to give me a picture of current development status?
Are there major bugs being worked on from cm incompatibility?
Click to expand...
Click to collapse
AFAIK, there aren't any CM bug now, there was a camera lag at start up weeks ago, but now it's solved,
the only thing left is that camera quality on AOSP-Based ROM is not as good as it is on stock Sony FW,
The great thing going on now is that we're gonna have official AOSP support from Sony soon (all thanks to @jerpelea)
check these:
Unified kernel for msm8974 devices
Xperia AOSP Project
these are still new and their early stages, and hopefully we'll start using them soon:good:
How come there is only one cm based kernel?
Click to expand...
Click to collapse
To be honest, there aren't many devs how own or work for this device, even the cm-based kernel we have is ported from Z1 !
also I'm working on a brand new one with the latest features, but I think it'll take some time
What are the most common problems that have been mostly encountered?
Thanks for your replies, happy to be here, take care
Click to expand...
Click to collapse
Well as I mentioned, we don't have any major problems, as this device can get whatever Z1 can get, and Z1 is popular
except for one thing! the double tap to wake feature can't be ported from Z1 to our device as the two devices don't share the same touchscreen!
That's all I can remember right now
if you need any help, I'm always available,
and I'm looking forward to seeing your work
Best Regards,
Omar.
Thank you very much for your long and exhaustive answer.
I did see a camera workaround in the cm system.
Has anyone tried porting stock camera to cm? (Is it the actual camera hal responsible for qualiy or Sony proprietary rendering sw on album(are pics better/worse in fact when viewed on PC or from the phone's album? We did that on the lg with great results..
What about device blobs for the kernel are they closed source or do we have support from Sony?
Thanks again for all the info
Cheers
Hello Guys,
welcome to the world of Team-Exodus.
What is Team-Exodus ?
We are a small group of entusiasts that like to learn more about Android and the Android-ROM developement.
We aren't exactly beginners But there is still room to learn more (you never end learning).
What is Exodus-Rom ?
Maybe, we better should start, what Exodus-Rom isn't: It isn't a (semi)professional mainstream ROM like CyanogenMod,AOKP or similar Roms. We don't focus on buzzword features, nor are we into "bling bling" options. We don't need a "change clock color" option, just because we can do it. These are "low hanging fruits", something nearly everybody can do, who has a computer to compile Android.
So what is Exodus-Rom, what is our focus on ?
We mainly focus on learning how things can be done. We are more into "quality over quantity". We prefer to have 4 or 5 real good and stable working features and not 20-30 features that work... somehow... sometimes...
We want performance, a fast, smooth fluid UI, a real good user experience, not a overbloated kang rom.
For instant that's the main reason why we currently don't have a Marshmallow Rom online, but I will give you a little more information regarding Exodus-6.0 (marshmallow) later.
But before that, who are we, who is "Team-Exodus" ?
The core team of "Team-Exodus" consists of the following guys:
@PrimeDirective - Dave, a very talented developer from the US, founder and Team Leader of Team-Exodus, specialist in App developement (for instant our Exodus Updater or the Drop Wallpaper App) and also our specialist for in deep functionalities of the Android Rom (like a complete rewritten Navbar customization). He currently uses bacon (Oneplus One) and Flounder (Nexus 9) for developenemt
@Raja.M - Raja, a real nice guy from India, he is our java specialist, he started Android developement something link 6 month ago but his knowledge is fast growing. He developes on the bacon (Oneplus One)
@TheCrazyLex - Alex, a kernel specialist from germany, he joined Team-Exodus like 3 month ago, mainly responsible to optimize and unify our kernels where possible. He also uses the Bacon (Oneplus One) as developement device.
@usmcamgrimm - Adrian, our graphics and theme specialist. Beside his amazing wallpapers, he is also responsible for all our LGE G3 devices. He mainly developes on the VS985.
@Martin_Ro - myself, Martin, also from germany, mostly responsible for the server with the build system, gerrit and download page. I'm also developing here and there if I find some time as I'm a married guy with to young boys. I'm developing on shamu (Nexus 6).
But beside this core team, there are a lot more ppl that help us making the Exodus Rom as amazing as possible, I will add some more of them step by step
So, now, back to Marshmallow and why it takes so much more time to bring an Exodus-6.0 to you guys:
For this to understand, you need to know more about where we come from.
On late 2014 we (Dave and Me) parted from VanirAOSP (that wasn't really AOSP but also used CM as base at that time btw) because we feeled like it started to get more and more into that mainstream "feature count is everything".
With 5.1 we started to directly use CyanogenMod (cm-12.1) as base, but was somewhat annoyed by upcomming issues because they used their open source branch as testfield for unfinished stuff, so for 6.0 we decided to go as near as possible back to strict AOSP.
But a matter of fact is: With strict AOSP you aren't able to support every device, and not as many devices as we want to support. So we have had to make some decisions and try some stuff. In the end we started developing Exodus-6.0 with a Mixture of strict AOSP and CAF as base, with the really amazing wide support of CyanogenMod regarding devices.
But with this, we got back to one of our main concerns: CyanogenMod is doing a fantastic job regarding device support (nobody can beat them in that department) but they are cluttering their stuff more and more. In the past few month, they started to create their own SDK, their own framework. And their SDK started to grow like a octupus, sticking his arms into every aspect of android. But we don't want to use their sdk, so we needed to remove it from everywhere.
And that was, what took so long. We wanted the device-tree and their hardware layer, but not their feature, and for sure not their SDK. And removing that stuff from everywhere inside the device-trees and Hardware layer.
Also we needed to use some of their code stuff in various places to make the connection between our AOSP/CAF based ROM and their hardware/device stuff.
So that took us nearly a month to finish up, but now we have first working experimental builds for bacon, shamu and VS985 so we can go into the real developing stuff.
There is still a lot to do (bring back all the features we want to, make the rom that fluid that you might be used to from EXODUS-5.1 etc.) But the real hard part is done now and we are way neared to a first public beta. Depending on the time Dave can find for Exodus (he is really really busy currently because of a new job), we expect to have a public beta by the end of the month...
So stay tuned and be patient
Made sticky
Hello! I enjoyed the 1/2 of the core team's and the new teams work since JB VanirAOSP to Exodus .
Just wondering, it would be cool to say what you do to seperate you guys from the rest. I know you guys build with jdk8 instead of jdk7 for the lollipop builds and use Linaro with some optimization flags.
I'd like to know if you do more than that and also I am wondering how JDK8 especially helps with optimization.
If you need a tester for bacon. I'm here very big fan of 5.1.
Nice to hear the updates... waiting patiently...
Sounds like the beta will become a christmas present.
Gesendet von meinem Nexus 5 mit Tapatalk
big fan/user of Exodus 5.1 on falcon. out of all the LP ROMs i've tried this has to be one of the most stable and lean ROMs out there. love the amount of essential customization catered here and skipping of cliche features that no one bothers to use (atleast me).
big thanks to @sachoosaini for introducing me to the ROM.
Well here it goes on
@PrimeDirective always a great human and great developer who supported Falcon despite the fact that i can never able to contribute the device to you. I find a best buddy out there who will always be my friend... Now @koshikas thanks Dave for supporting this phone, i never did anything for exodus.. But i am committed for future. If Dave continues the journey for exodus i will be with him in all way... Well what he told me around 6-7 months back is now coming to the real world. Now they support falcon or not. But I am honored by Dave for being there with all the silly questions people ask in community, falcon has great life indeed now its upto the team they develope for it not. I will donating device as soon as I am getting my salary which i am for sure going to get soon..... Wish Luck to exodus....6.0 is on the horizon
If you need a tester...
Hey, if you guys need an experienced tester for bacon, look no further. :good:
AndroidPr0 said:
Hey, if you guys need an experienced tester for bacon, look no further. :good:
Click to expand...
Click to collapse
I'm with this guy
Where do I go to look at the rims ?....dir a HTC m8 Sprint
With S-on
Coolkid90 said:
Where do I go to look at the rims ?....dir a HTC m8 Sprint
With S-on
Click to expand...
Click to collapse
Hm, ok, might be, because english is not my mother language, but for me this sound like "too much drugs and not enough sleep"....
Oh, and by the way:
we just prepared the open source manifest so you can start contribute
I will write a short Facts thread for Exodus-6.0 so you know how to build, and what we changed regarding device-support...
Excelente
Looking real forward to Exodus MM!
sir I am with you here.
AndroidPr0 said:
Hey, if you guys need an experienced tester for bacon, look no further. :good:
Click to expand...
Click to collapse
I m new here and wish to get some knowledge from senior member.
Thanks for this great rom
Exodus seems cool... hyped for MM release!
delete : found it
"err on the side of kindness"
Hi guys
Only to keep you informed: We started publishing official release builds for Exodus-6.0.
Look into your devide Android Developement sections for more information or on our g+ community: https://plus.google.com/communities/106801227383087889476
HI everyone
I'm currently running LineageOS17 in my Shamu, but i'm wondering if there is a faster or smother room for the device
I'm really happy with LineageOS actually, it's just curiosity, I read that it's HavocOS, somebody can confirm?
Many thanks!
Pilsener said:
HI everyone
I'm currently running LineageOS17 in my Shamu, but i'm wondering if there is a faster or smother room for the device
I'm really happy with LineageOS actually, it's just curiosity, I read that it's HavocOS, somebody can confirm?
Many thanks!
Click to expand...
Click to collapse
All ROMs use LineageOS's shamu kernel and device code, so you won't see much of a difference.
I've used several Android 10 ROMs, including LOS, and have settled on crDroid because it has a lot of customisation (though in itself that's normal) but also Face Unlock, which I really like. Other ROMs may also have it - I haven't checked. Overall I agree with Elektroschmock - since they use the same code base you'll find it difficult to find huge differences. They have all been stable for me - just Face Unlock made the difference for me, but I reckon you'll be happy with pretty much any one of them.
Edit after three days. Right, that's it for me. I'm taking my own advice. This is definitely the last time I'll offer any help or support to a junior member. I'm done with their lack of interest in answers.
dahawthorne said:
I've used several Android 10 ROMs, including LOS, and have settled on crDroid because it has a lot of customisation (though in itself that's normal) but also Face Unlock, which I really like. Other ROMs may also have it - I haven't checked. Overall I agree with Elektroschmock - since they use the same code base you'll find it difficult to find huge differences. They have all been stable for me - just Face Unlock made the difference for me, but I reckon you'll be happy with pretty much any one of them.
Edit after three days. Right, that's it for me. I'm taking my own advice. This is definitely the last time I'll offer any help or support to a junior member. I'm done with their lack of interest in answers.
Click to expand...
Click to collapse
Because someone doesn't reply doesn't mean they have no interest .
I feel like XDA would be more active if there is a Discord. Reddit is also a good resource that has taken over the popularity of sites
dahawthorne said:
I've used several Android 10 ROMs, including LOS, and have settled on crDroid because it has a lot of customisation (though in itself that's normal) but also Face Unlock, which I really like. Other ROMs may also have it - I haven't checked. Overall I agree with Elektroschmock - since they use the same code base you'll find it difficult to find huge differences. They have all been stable for me - just Face Unlock made the difference for me, but I reckon you'll be happy with pretty much any one of them.
Edit after three days. Right, that's it for me. I'm taking my own advice. This is definitely the last time I'll offer any help or support to a junior member. I'm done with their lack of interest in answers.
Click to expand...
Click to collapse
Oh no! Sorry, It really does interest me! I'm still using LOS17, I just wanted to read another user experiences with different roms! That's all. Thanks for your answer, und danke to Elektroschmock for keeping Shamu alive! :fingers-crossed:
I'm just wondering how ROMs are classified into 2 subforums NEXUS 6 ORIGINAL ANDROID DEVELOPMENT and NEXUS 6 ANDROID DEVELOPMENT
for me, I tend to like ROMs in 1st sub cause it is original. but havocs is also very good though lol
ponichia said:
I'm just wondering how ROMs are classified into 2 subforums NEXUS 6 ORIGINAL ANDROID DEVELOPMENT and NEXUS 6 ANDROID DEVELOPMENT
for me, I tend to like ROMs in 1st sub cause it is original. but havocs is also very good though lol
Click to expand...
Click to collapse
if i want to put my build in original android development forum i can but i like android development forum
ponichia said:
I'm just wondering how ROMs are classified into 2 subforums NEXUS 6 ORIGINAL ANDROID DEVELOPMENT and NEXUS 6 ANDROID DEVELOPMENT
for me, I tend to like ROMs in 1st sub cause it is original. but havocs is also very good though lol
Click to expand...
Click to collapse
AmirHRC said:
if i want to put my build in original android development forum i can but i like android development forum
Click to expand...
Click to collapse
For clarification why there are two different forums:
https://forum.xda-developers.com/showthread.php?t=2112240
So "Android Development" is the right place for most ROMs as the only thing they do is rename some LineageOS stuff.
Elektroschmock said:
For clarification why there are two different forums:
https://forum.xda-developers.com/showthread.php?t=2112240
So "Android Development" is the right place for most ROMs as the only thing they do is rename some LineageOS stuff.
Click to expand...
Click to collapse
lol Why are you so excited? and yes ican post my android 11 build and you can take device tree and rename some stuff ?
AmirHRC said:
lol Why are you so excited? and yes ican post my android 11 build and you can take device tree and rename some stuff
Click to expand...
Click to collapse
I was just answering his question.
I was answering with Android 10 ROMs in my mind.
If you do a proper Android 11 bringup for shamu, it would be justified to post it in original development.
And Yes I would use your repositories - thats the spirit oft open source. But I suspect they are in a state where it's better to keep them closed as I do with mine.
I love full gestures in Android 10, so I tried several roms to find the smoothest one with full gestures on: Lineage, crDroid, Pure Pixel, Carbon. All with original kernels, nanoGapps and some 20 apps of mine installed.
The smoothest performance over time I found with Pixel Experience, using Lawnchair2 as a home launcher.
Cheers
PS: all of them roms run super smooth if you do not use full gestures, and each has its super nice tweaks
alvi.bagolini said:
I love full gestures in Android 10, so I tried several roms to find the smoothest one with full gestures on: Lineage, crDroid, Pure Pixel, Carbon. All with original kernels, nanoGapps and some 20 apps of mine installed.
The smoothest performance over time I found with Pixel Experience, using Lawnchair2 as a home launcher.
Cheers
PS: all of them roms run super smooth if you do not use full gestures, and each has its super nice tweaks
Click to expand...
Click to collapse
update:
moved to Arrow os androdid11 (by amazing AmirHRC, thanks!), same quick response with gesture navigation, plus no glitches, super. Beware you will loose the google camera with its nice HDR. Up to you..