APERTURE SCIENCE proudly presents eXperience Pro.
The eXperience Pro application implements an innovative cross-device and cross-kernel tweak framework which offers a convenient modular approach for Android customizations and tweaks.
With this powerful and exciting new tool users will be able to apply various tweaks on-the-fly and independent of the running kernel. This application will put users in the position to run their favorite tweaks on whichever kernel they prefer without having to convince the corresponding kernel devs to include it. Thus by cutting out the middleman, this app will empower the users and give them a greater control about customization of their devices. Also this software will open up the world of Android tweaking for users that prefer to run the stock kernel.
Try my free eXperience Test app (https://play.google.com/store/apps/details?id=aperture.ezekeel.experiencetest) first to check whether the device and currently running kernel is compatible with the tweak framework employed in eXperience Pro.
Currently supported devices:
Currently supported devices:
* Nexus 4 (mako)[1][2]
* Galaxy Nexus GSM (maguro), Verizon (toro) and Sprint (toroplus)
* Galaxy SII (GT-I9100), Galaxy SII Skyrocket (SGH-I727) and Galaxy SII (galaxys2)
* Galaxy SIII international (GT-I9300, m0), T-Mobile (SGH-T999, d2tmo), Verizon (qcom, d2vzw), Sprint (SPH-L710, d2spr), US Cellular (qcom, d2usc), AT&T (qcom, s2att) and LTE (GT-I9305)
* Galaxy Note GT-N7000 and Galaxy Note SGH-I717
* Nexus 7 WiFi (grouper) and 3G (tilapia)
* Transformer Pad (TF700T) and Transformer Prime (TF201)
* Galaxy Tab 8.9 (p5wifi)
* One XL (Evita), One X AT&T, One X endeavoru
* One S (Ville)[2]
* Galaxy Note 2 GT-N7100 (t03g), SCH-I605 (t0ltevzw), SGH-T889 (t0ltetmo), GT-N7105 (t0lte), SPH-L900 (t0ltecdma) and Sprint (t0ltespr)
* Optimus G Sprint (geehrc4g_spr_us)[1][2], Optimus G LS970 (geehrc4g)[1][2], Optimus G 4X HD LG-P880, Optimus G LG-E970[1][2]
* Iconia A511
* Droid Razr (XT910)
* Galaxy Note 10.1
* Vivid 4G
* Raider (X710e)
* Rezound (ADR6425LVW)
* Galaxy Tab 7.7 (P6800) and Galaxy Tab 7.7 (GT-P6800)
* Evo 4G Jewel[2], Evo 4G PC36100 and HTC6435LVW[2]
* Galaxy Tab 2 10.1 (GT-P5100)
* Xperia Z (C6603)[1][2]
* Prada LG-P940
If your device is not on the list download my free eXperience Test app which can collect the necessary device-dependent data (no personal information) and send it to the author via email conveniently in one button press.
Currently implemented tweak modules:
* Touchwake (all devices): When the screen times out one can simply touch the screen to activate it which is much more convenient than pressing the power button - especially great for tablets.
* Music Control (all devices): Control the music playback with the volume buttons. Long press of the volume up button skips to the next song, long press of the volume down button skips back to the previous song (or rewinds the currently playing song). Simultaneous long press of both volume buttons pauses the song or continues playback when paused.
* CPU Control (only devices marked with [1]): Adjust the voltages for the different CPU frequency steps.
* Volume Control (only devices marked with [2]): Adjust the output volume of the headphones and device internal speaker and the input volume of the camcorder and handset microphones.
**** IMPORTANT ****
Some custom ROMs come with a broken version of su and/or busybox. If you experience any problems with the app, before reporting the issue first try to fix it by installing Stericson's busybox (https://play.google.com/store/apps/details?id=stericson.busybox) and SuperSU (https://play.google.com/store/apps/details?id=eu.chainfire.supersu) and then updating the su binary in the SuperSU app.
Google Play: https://play.google.com/store/apps/details?id=aperture.ezekeel.experiencepro
Android Pit: http://www.androidpit.com/en/android/market/apps/app/aperture.ezekeel.experience/eXperiencepro
*********************************************************************************************************************************
*********************************************************************************************************************************
Some technical info on how all of this works:
On app start as the first action the program checks whether the eXperience tweak framework is running or not. If the framework is not already running it is initialized in memory.
The eXperience framework interacts with the underlying system and acts as a device-independent layer which both handles the loading and unloading of individual tweak modules and also communication with these modules. Since this framework does not rely on any persistent daemons or other background processes there is no effect on performance of the device or battery drain. Also the persistent memory footprint of the eXperience framework in only around 4kB which is negligible on todays hardware.
Using the platform of the eXperience framework different tweak modules can be implemented in a straightforward manner since one does not have to account for hardware fragmentation (except for some parametric dependencies). This leads to very compact and efficient tweak modules with persistent memory footprints of around 3-5kB.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since the eXperience framework has to absorb all the device dependencies and account for different hardware and kernels, the initialization of the tweak framework is the most critical step of the entire program flow and if complications due to incompatibilities arise they are most likely to surface during this step.
The initialization of the tweak framework as well as the loading/unloading of modules are all performed in memory and the eXperience app does perform any write operations outside of its designated storage space on the data partition - so especially the system partition and other critical partitions remain untouched. Therefore it is not possible to cause any damage to the device resulting in it becoming unbootable or unoperational. In the worst case scenario the app can cause a reboot or freeze of the system.
Ezekeel said:
stub
Click to expand...
Click to collapse
I dont understood the thread
I don't understand either.
Sent from my cm_tenderloin using xda premium
hmmmm I think it'll be good once he tells what it is logo me and glados controlled are both good apps so hopefully this will be also
Sent from my SPH-D710 using xda premium
The suspense
Sent from my SGH-T989 with Cyanogenmod 9 Nightly Power.
His tweaks don't have to be built into a kernel for you to be able to use anything his new app offers.
Sent from my Google Nexus 7 using Tapatalk 2
Touchwake works on Franco And trinity kernels using this app . Great idea !!! specially for us " crackflashers" thanks for your time !
Great idea.
Sent from my GT-I9003 using xda premium
Lovin this EZ
Sent from my Galaxy Nexus using Tapatalk 2
Just wanna put in a plug for d2tmo. I used this on my. Galaxy nexus. I noticed support for att galaxys3 hoping for some t-mobile love. Thnx!
DARKSIDE
I love the touchwake, but it kinda sucks to have to manually reload the modules after each reboot. Any way around this?
Sent from my Galaxy Nexus using Tapatalk 2
farfromovin said:
I love the touchwake, but it kinda sucks to have to manually reload the modules after each reboot. Any way around this?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Wondering the same thing.
Sent from my Galaxy Nexus using Tapatalk 2
DarkSorcerer said:
Wondering the same thing.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi,
Boy, do I feel stupid now. Just long press in module and tick "enable on boot". Found the solution in other forum.
Regards,
Hi,
The app needs update to Android 4.1.2, as modules don't work in the new version. Thank you!
Regards,
Sent from my GT-P5100 using Tapatalk 2
Ezekeel has published in G+ that he has been absent because he had an accident. He's now at home, recovering, and will be back after reading all the emails and catch up with the news.
Sent from my GT-P5100 using Tapatalk 2
I find it unfair that one device gets it free, but the rest of us have to pay. Personally don't think that's a good idea. I do love the concept of the app an tweaks though, hopefully I'll get a chance to test it.
I'm on euroskank 2012.12.11 (cm10.1 kang) using Franco nightly build #344. I load the app and it starts up fine, but all options are greyed out and when I try to use the load modules my device reboots... Is that to apply the modules or does this mean that non of those modules are supported... I'm confused as its supposed to work on Franco...correct? I'm very new to kernel tweaking, so any help would be appreciated here .thanks
I have added some technical information on how this app works to the first post.
If you had problems before, try the latest version. Also try my free eXperience Test app to determine if your not yet supported device is compatible with eXperience and if this test is successful to collect the necessary device dependent data.
Good news everyone!
I have released eXperience Pro V1.8 adding the new Music Control tweak module for all supported devices: Control the music playback with the volume buttons. Long press of the volume up button skips to the next song, long press of the volume down button skips back to the previous song (or rewinds the currently playing song). Simultaneous long press of both volume buttons pauses the song or continues playback when paused.
Additionally I have released eXperience Test V1.1. If the device and kernel are compatible an additional check is performed whether support for this device is already implemented in the eXperience Pro app. If support for this device in not implemented yet, the user has the option to collect the necessary device-dependent data (no personal information) and send it to the author via email conveniently in one button press.
I have released eXperience Pro V1.9 adding support for Galaxy SIII LTE (GT-I9305), Galaxy Note 2 GT-N7100 (t03g), Galaxy Note 2 SCH-I605 (t0ltevzw), Galaxy SII GT-I9100 and One X endeavoru.
I also have released eXperience Test V1.2 adding these five models to the list of supported devices.
A big thanks to all users that have collected the data and send it to me!
Currently the eXperience Pro app supports 26 different hardware models and devices. I wonder how much more devices I can support simultaneously with that one app. Gotta catch them all!
If you have an Android device released last year or this year which is not yet supported by eXperience Pro, please download my free eXperience Test app and help by collecting the device-dependent data (no personal information).
Related
Hello everyone,
Over the last three or so years I have made my way through a lot of phones, always in-search of the 'perfect' one.
I've settled on the Nexus range because I love stock Android and have found the hardware to be acceptable.
For my next foray into a 2013 phone I'm thinking of getting the HTC One and pairing this with Cyanogenmod, when it becomes available.
This to me would be the best physical hardware, in both appearance and materials of any Android device, and software.
Something akin to this!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So the reason for this thread is to gain input from those who have used both Stock and Cyanogenmod.
Am I going to be satisfied with the move?
Visually things are the same? The use the same assets?
What problems could arise? What should I be aware of when compared with Stock?
Any other thoughts or opinions you may have. Please keep it in-line with the HTC One and Cyanogenmod.
Many thanks.
Off-topic but when I look at that Black picture I find it sooo cool.
CyanogenMod will most likely come to the device. I don't see why it wouldn't. It'll also look just like CyanogenMod on your Nexus devices. But you can be assured that it won't come easily. It'll be harder to build than a nexus device, and early builds are likely to have bugs that will need to be worked out
notsointeresting said:
CyanogenMod will most likely come to the device. I don't see why it wouldn't. It'll also look just like CyanogenMod on your Nexus devices. But you can be assured that it won't come easily. It'll be harder to build than a nexus device, and early builds are likely to have bugs that will need to be worked out
Click to expand...
Click to collapse
I've never rooted a device to put any ROM other than an update to Stock. I guess what I'd like to know is what the differences are between stock and Cyanogenmod. If the experience of using them is nearly 90% the same, then I'll be happy. If it's further away than that, I'll have to force myself to wait for the Nexus 5 and hope it brings some premium materials.
Re: blingfeed annoying
Is it worth it. I love it but even on the one x was frustrating due to not being able to use the camera to it's full potential.it would fly on here but you'd lose a lot on this device. Which would be a shame
(No doubt if be trying it still if it was here though and get frustrated again lol)
Sent from my HTC One using xda app-developers app
mr.suff said:
Over the last three or so years I have made my way through a lot of phones, always in-search of the 'perfect' one
Click to expand...
Click to collapse
I had the last 'perfect one' - the legendary HTC HD2 - since it came out.
I dropped the first one I owned and almost sold the insurance replacement to buy a different phone.
I was tempted many times by the hypegasm of new fangled phones but, really, what were they adding that the venerable HD2 couldn't already do? Nothing really.
Glad I made the choices I did.
Wait and see, all these answers can be answered by yourself ...
Sent from my One X using Tapatalk 2
mr.suff said:
I've never rooted a device to put any ROM other than an update to Stock. I guess what I'd like to know is what the differences are between stock and Cyanogenmod. If the experience of using them is nearly 90% the same, then I'll be happy. If it's further away than that, I'll have to force myself to wait for the Nexus 5 and hope it brings some premium materials.
Click to expand...
Click to collapse
By default, it is basically identical, with a few improvements (T9 dialing).
However, there are many options to customise it - adding different shortcuts to the lockscreen ring (up to five, I think), quick-toggles in the notification shade, "quiet hours" (a setting which silences your phone during certain times of the week)..
The list is exhaustive.
CyanogenMod is much better than stock, imo, notification toggles are much better (and less complicated) than the quick-settings panel.
i wouldn't buy this device based on getting CM10. i think it's going to be quite awhile for both this phone and the s4. if you want a pure Google experience id look into the n4 or wait and see if the n5 is going to be announced at google io in may.
fix-this! said:
i wouldn't buy this device based on getting CM10. i think it's going to be quite awhile for both this phone and the s4. if you want a pure Google experience id look into the n4 or wait and see if the n5 is going to be announced at google io in may.
Click to expand...
Click to collapse
Already have the Nexus 4. Mainly interested in the external hardware look and feel of the One, it's the Android equivalent of the iPhone 5 . I doubt Google will announce a new Nexus device at I/O, but I could be wrong.
I'm looking for opinions of those who've used both Stock and Cyanogenmod extensively. What they like and don't like.
mr.suff said:
Already have the Nexus 4. Mainly interested in the external hardware look and feel of the One, it's the Android equivalent of the iPhone 5 . I doubt Google will announce a new Nexus device at I/O, but I could be wrong.
I'm looking for opinions of those who've used both Stock and Cyanogenmod extensively. What they like and don't like.
Click to expand...
Click to collapse
im hearing the n5 will be announced at google io.
What is this cyanidemod? Please be happy to tell me.
Suqmadiq said:
What is this cyanidemod? Please be happy to tell me.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Stock Android without custom skins like Sense and TouchWiz: Wiki
Edit, Its not cyanidemod, its cyanogenmod
AW: HTC One and Cyanogenmod
NiCk.JaY said:
Stock Android without custom skins like Sense and TouchWiz: Wiki
Edit, Its not cyanidemod, its cyanogenmod
Click to expand...
Click to collapse
It's not Stock Android. There are a few modifications! For example the quick toggles.
Gesendet von meinem Transformer TF101 mit Tapatalk 2
I didn't read the question properly lol. Mate if your a fan of pure android stick with the nexus.I love both so I'm okay. But pure...there's a lot to be said for how quick everything runs. Though I wouldn't pass on the one.
Sent from my Galaxy Nexus using xda app-developers app
Thing is, stock rom (Sense) tend to have better battery life than CM10. Stock roms (Sense) are more optimised for the system. I've noticed this since my battery was a lot less when I had the S2, S3, HTC One X etc using CM10.
I also feel this may get a quicker/less buggy release than the S4 with exynos 5. I imagine samsung wont release any info for the exynos 5 like they havent for the exynos 4. The S600 variants will probably be fine but that may give the One an advantage.
it makes no sense to buy a HTC One or any phone for that matter to just put stock android on it.. you lose half the features the phone came with (even if their are gimmick or not)
You should just buy a Nexus device.. because in the end thats all you trying to get..
You are buying the HTC One for design.. not for its features..
The processors wouldn't be any difference in notice.. unless you plan on running HD 1080P videos every second of the day and playing games like "Dead trigger, Real Racing etc every day"
May-C said:
It's not Stock Android. There are a few modifications! For example the quick toggles.
Gesendet von meinem Transformer TF101 mit Tapatalk 2
Click to expand...
Click to collapse
That was just to explain the basics of cm to him
Sent from my Desire HD using Tapatalk 2
The main difference between stock android and cyanogenmod are featured n options. There are a lot more settings, n tweaks and ways to persoalize it the way you want. There are also variations of CM like aokp, paranoidandroid,etc which add even more options and customizations. Also there will be sense roms with things added/removed l, etc that you may like. The great thing about Roms is that you can change the whole look ans feel of your phone within minutes. Best thing for you to do is go over to like the HTC EVO 4g LTE forum or the HTC ONE X forum and look thru the android and original android development sections at all the toms and get an idea what is out there. Any aosp rom would be cm like stock android and any sense is just that tweaked stock sense.
By Stephen Yuen
AndroidSPIN | Jun 19th
New versions of Android 4.3 have been spotted running on Nexus 4 and Nexus 7. Previously we have seen rumours and unconfirmed benchmarks running the newest version of Jelly Bean, but thanks to DoMiN8ToR at myce.com, the JWR66D (Nexus 7) and JWR53F (Nexus 4) builds of Android 4.3 have been seen in the wild.
According to DoMiN8ToR, the “J” at the beginning of the build code designates that the build is of Jelly Bean origins and that the “R” specifies that the build is from the second quarter. Furthermore, the number in the build code is the n-th day of the quarter, placing these builds sometime between at the end of May and the beginning of June. Finally, the last letter of the code defines what build of the day it is i.e. D is the fourth, and F would be the sixth build of the day.
I’m sure we’re all wondering when Android 4.3 is going to drop, but news like this further suggests that it will hopefully be very soon.
OP here http://drippler.com/updates/share/android-43-spotted-nexus-4-and-nexus-7
Sent from my Nexus 4 using Tapatalk 4 Beta
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 4 using Tapatalk 4 Beta
OMG 4.3 SPOTTED ON N4 & N7 ARTICLE..... shows picture of Samsung device
Original rumor from here http://www.myce.com/news/exclusive-new-android-4-3-versions-spotted-on-nexus-devices-67544/ but i think it's still a rumor )
it will e not released today
Are.Two said:
OMG 4.3 SPOTTED ON N4 & N7 ARTICLE..... shows picture of Samsung device
Click to expand...
Click to collapse
New feature: 4.3 will turn your device into a galaxy S4
JWR66D and JWR53F are already rather old (in the context of bleeding edge/not for public roms).
JWR66N is the newest confirmed rom, and JWR66O is the newest unconfirmed rom>
JSR72 might be newer then JWR66O, R66O gives no indication on it's age.
R72 was June 11th 2013, while R66O could be from any time within the last 2 weeks.
(Before the thread gets locked again due to lack of N4 specific stuff)
Issue 250805 - chromium - Repeatable failed check (crash) on tumblr.com/login - An open-source project to help move the web forward. - Google Project Hosting:
Code:
google/occam/mako:4.3/JWR66N/711294:userdebug/dev-keys
We expect a new radio as it was previously already reported that JWR45B already had a new radio for the N4.
Presumably there will also be a new bootloader, but there's currently no proof that it will/wont
They've changed it from reporting JellyBeanMR2 to 4.3 in the fingerprints a bit back, when hints that they have 4.3_r1 in sight.
JellyBeanMR2 represents a master branch and 4.3 represents a branch cut for a release target.
Don't see why this thread would get closed. It is n4 related. Its an article that that's about 4.3 on the nexus 4!!!.
Sent from my Nexus 4 using xda app-developers app
One question is if 4.3 comes with a new kernel version, goog has been working with linux 3.8/3.9/3.10
Refs - kernel/common - Git at Google:
Excluding the NS getting updated to 3.0 (from 2.6.35), nexus devices generally end their lifetimes with the same major kernel version they started with (and extended nexus-like devices such as the xoom and OG droid)
The N7 sucessor will likely launch with a newer kernel version if there is one at all, and there's the question of if the N4/10 will be updated or simply stay on 3.4.
The N7 has already past this point by staying on linux 3.1 for android 4.2.
5.0 is almost guaranteed to come with something newer then 3.4 as even 3.8 is already EOL (end of lifed), 3.4 just happens to be a long term kernel version (ie it will get patches for much longer then non long term ones)
TheManii said:
New feature: 4.3 will turn your device into a galaxy S4
Click to expand...
Click to collapse
LOL:laugh:
TheManii said:
New feature: 4.3 will turn your device into a galaxy S4
Click to expand...
Click to collapse
Ewww.
Gonna stick to 4.2.2 then
Wait! So 4.3 will be touchwiz? I must spread this news to the verge and they will make it front story
Skickat från min Nexus 4 med Tapatalk 4 Beta
norpan111 said:
Wait! So 4.3 will be touchwiz? I must spread this news to the verge and they will make it front story
Skickat från min Nexus 4 med Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes 4.3 is touchwiz yes:silly:
Aerys said:
Yes 4.3 is touchwiz yes:silly:
Click to expand...
Click to collapse
Vanilla is the new OEM skin and touchwiz is the new vanilla
Skickat från min Nexus 4 med Tapatalk 4 Beta
norpan111 said:
Vanilla is the new OEM skin and touchwiz is the new vanilla
Skickat från min Nexus 4 med Tapatalk 4 Beta
Click to expand...
Click to collapse
I want key lime Pie, I mean seriously why is google isurprised of the fragmantation of android? It is their fault instead of bringing a big update they bring small ones..
Google thumbs down , someone of the android department must be fired
hamad138 said:
I want key lime Pie, I mean seriously why is google isurprised of the fragmantation of android? It is their fault instead of bringing a big update they bring small ones..
Google thumbs down , someone of the android department must be fired
Click to expand...
Click to collapse
Why would fragmentation be less if they release yet another big update so phones with OEM skins will have long time to optimize ? If you do little at a time and put core-apps on play (like keyboard now) in my logic that will lead to less fragmentation actually.. You disagree?
Skickat från min Nexus 4 med Tapatalk 4 Beta
The way i see it there is no fragmentation in android (feel free to agree or not). OEM's skins are not really skins anymore, they are standalone versions of android.
Look at the feature-list of touchwiz for example, it offers a lot more than stock android, it's not only a simple framework modification, or a change for something that already exists on stock android, no, we're talking about new features (gimmicky or not), multiwindow, all those air gestures, hovering over text and photos, smart scroll, pause..., 4 or 5 presets for tuning screen colors, totally different camera app with plethora of options not found on stock (HDR recording etc..) . Furthermore, there is support for microSD which google removed from aosp.
My point is, people who buy samsung devices, must know that they are buying samsung's version of android, and have no right to blame google for any update system (frequent lil ones or one big update/year) , or any delays in updating their samsungs. It's not only related to updates, but in general when you buy a device that is not rocking official fully stock android (like nexus or google edition phones) , your relation is not with google, but with your OEM, and any complaints/praises/suggestions/ideas/bug report should be addressed to them. Google's stock android serves only as a reference for OEM's versions.
=> when you're buying a galaxy S or Note, you're not buying android, you're buying a samsung.
=> No fragmentation in android
Same applies to other OEMs.
Good point!
Skickat från min Nexus 4 med Tapatalk 4 Beta
To be clear I read somewhere on Google+, google mentioned Galaxy S3 as Android-based phone and N4 as Android.
So, OEM skin is actually Android-based OS and Vanilla Android is Android OS.
Sent from my Nexus 4 using Tapatalk 2
Who cares about fragmentation. Most android users have never even heard of key lime pie. Most users are not even on 4.2.2. Bring on new versions. The only people that care are nexus users
Sent from my Nexus 4 using xda premium
Smallsmx3 said:
Who cares about fragmentation. Most android users have never even heard of key lime pie. Most users are not even on 4.2.2. Bring on new versions. The only people that care are nexus users
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Don't forget xda users and geeks.
Sent from my Nexus 4 using Tapatalk 2
Smallsmx3 said:
Who cares about fragmentation. Most android users have never even heard of key lime pie. Most users are not even on 4.2.2. Bring on new versions. The only people that care are nexus users
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I agree,many android users I know use anything between froyo and ICS, they have no idea about newer versions or even what the deserts mean, so fragmentation is irrelevant to them.
Sent from my Nexus 4 using xda app-developers app
Hey there,
xplodwild here, I did the announcement session at BABBQ, it was awesome. Thanks for everyone who were there.
So yeah, we didn't prepare a lot of YouTube demo videos yet, but all the information about the philosophy of Omni are available on Omni website: http://omnirom.org/why-omni/.
We are a ROM different than others: we are focused on performance, cohesion, stability, innovation, code quality, community and open source. And the community more than anything else. You are using the ROM, you should be choosing what you want to have.
When we're taking a patch from another ROM, we're trying as much as possible to enhance it before merging it. When we're getting new features, we give you a way to give early feedback, early access to prototypes, early access to mockups, etc, so that we know immediately early on if we're doing it right.
All the contributions will be GPL licensed (at least we'll be pushing for it). People will be able to vote up and down on patches,
Some of the key features of Omni:
Flippable Quick Settings
Roadrunner mode
Multi-window(!)
Daydream enhancements
Integrated Performance Control
Multi-workspace
Color-changeable, 3D depth Phase Beam
And a bunch more
We're also pushing non-Android stuff, such as OmniInstaller (an all-in-one, multi-platform, open source, installer that anyone can plug in), as well as a Qt library to give Qt Android apps a native Android look, and have gorgeous and super-fast Android apps. We're helping users, and helping developers.
Everything is free, free as in money, and free as in liberty. And transparent.
Edit #1: Regarding device support, we currently support all the Nexus devices, as well as the Oppo Find 5, Xperia Z, Xperia Tablet Z. We have preliminary support for the i9300 as well as the Oppo R819.
Edit #2: We'll have a bunch of developer resouces up soon, giving a head start to newcomers in the Android development world.
I probably didn't cover much things but I'll add more things as they come to my mind. We're having beers here and I'm probably not fully able to do a comprehensive post right now.
Have some screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NIce! Does that "multiwindow" works flawlessly?without breaking apps?
I'm overjoyed to see you guys bounce back after the Inc debacle.
Looking forward to compiling, testing and enjoying Omni.
Are you guys going to kang features from other ROMs (Halo and Pie from PA for example) or will all features be developed in-house?
Also, on which Android-version are the first builds based? I guess 4.3.1?
Since the annoucement of Cyanogen to be a corporation, I was searching for a new AOSP-based ROM for my daily needs, and I think I found it. Good luck guys!
I m dying to try this rom.
Would it be possible to port it using cyanogenmod or aosp as base?
chasmodo said:
I'm overjoyed to see you guys bounce back after the Inc debacle.
Looking forward to compiling, testing and enjoying Omni.
Click to expand...
Click to collapse
Me, two©. Joli coup @XpLoDWilD @Entropy512 and everyone else involved, wishing you all the best with Omni. Nice to see espenfjo back on track as well.
#free^3
They say all nexuses are supported , then where is galaxy nexus support huh ? If there will be not official support , how can I develop a unofficial version of OMNIr for gnex ?
sakindia123 said:
NIce! Does that "multiwindow" works flawlessly?without breaking apps?
Click to expand...
Click to collapse
It will do pretty much. We'll get sources up very very soon (ie. minutes), and gerrit is already live where you can see the MultiWindow patch being reviewed and improved.
SGWUser said:
Are you guys going to kang features from other ROMs (Halo and Pie from PA for example) or will all features be developed in-house?
Also, on which Android-version are the first builds based? I guess 4.3.1?
Since the annoucement of Cyanogen to be a corporation, I was searching for a new AOSP-based ROM for my daily needs, and I think I found it. Good luck guys!
Click to expand...
Click to collapse
In the spirit of open source, if there's something that gives positive improvement on the user experience, and it can be introduced, and people want it, it will be included. There's a balance between "settings inception" (ie. a toggle for your toggle, to toggle text alignment of the clock) and something that isn't customisable, but that will be open to much wider discussion and consultation.
4.3.1 is the current version in use, yes.
Halo and Pie are 2 specific examples, but this is where the community comes in - porting these features should be fairly straightforward. We like to try improve things too where possible
AndroidAddiction said:
I m dying to try this rom.
Would it be possible to port it using cyanogenmod or aosp as base?
Click to expand...
Click to collapse
The ROM is based on AOSP, and full sources will be posted today, meaning you can try to build it for yourself. Be aware though, not all chipsets are currently supported - nexus devices will have more luck than other devices for now, but that will obviously change in the coming days and weeks.
Ashutos1997 said:
They say all nexuses are supported , then where is galaxy nexus support huh ?
Click to expand...
Click to collapse
I don't believe anyone has one here for testing, hence it has not been listed yet. it WILL be supported, but until it's been tested, it won't go onto the list
Have the additional selinux commits CM started picking a few months ago been picked here also? If so, would make getting a build up for the Sprint and Verizon GNote 2 much easier Now it's just a waiting game for source to drop.
Sent from my Nexus 7 using Tapatalk 4
slick_rick said:
Have the additional selinux commits CM picked a few months ago been picked here also? By that I mean the 2nd commit from the top to the next page https://github.com/CyanogenMod/android_frameworks_base/commits/cm-10.2?page=15 If so, would make getting a build up for the Sprint and Verizon GNote 2 much easier Now it's a waiting game for source to drop.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
We've not focused yet that much on SELinux, as generally we believe that features like this should be introduced once the tree is stable enough.
There's still work needing done for SoCs (like Exynos!), but once we have the ground work covered, make no mistake, SELinux will be in and securing. Until then though, it will not be a number 1 priority (not to say nobody can go fix it!) - that's the glory of open source
Hurray!
a small query,do you plan to include support for legacy devices?(for example, the video encoding/decoding patches for msm7x27/7x27a)?
Currently,no roms support this by default.
Great News.
pulser_g2 said:
We've not focused yet that much on SELinux, as generally we believe that features like this should be introduced once the tree is stable enough.
There's still work needing done for SoCs (like Exynos!), but once we have the ground work covered, make no mistake, SELinux will be in and securing. Until then though, it will not be a number 1 priority (not to say nobody can go fix it!) - that's the glory of open source
Click to expand...
Click to collapse
Makes sense. I use modified CM trees to build for PA which doesnt have that extra selinux stuff so building should still be pretty painless I hope. Last question, let's say I wanted to add PA Pie support in an aio patch or so, would I just push to gerrit and from there the core team and users vote on it? Considering its stable and working fine. How will that work? Thanks!
Sent from my Nexus 7 using Tapatalk 4
sakindia123 said:
NIce! Does that "multiwindow" works flawlessly?without breaking apps?
Click to expand...
Click to collapse
Still work to be done. I just barely got it working on flo and pollux_windy before flying out to BABBQ.
What's the Roadrunner feature?
sakindia123 said:
a small query,do you plan to include support for legacy devices?(for example, the video encoding/decoding patches for msm7x27/7x27a)?
Currently,no roms support this by default.
Click to expand...
Click to collapse
Yes, we intend to include legacy device support as a key feature. I'll go into this in more detail later, but this was one of our founding "aims".
Provided compatibility for legacy devices can be implemented "neatly" without impacting other devices, it's actively encouraged
Custom ROMs were meant to extend the useful lives of phones, not leave phones dangling without support
hikarugo said:
What's the Roadrunner feature?
Click to expand...
Click to collapse
Roadrunner was the "speculated" feature name for a previous version of Android where some people suggested that it would improve battery life, and add better power profiles and management.
Roadrunner was something Xplod is working on, but it aims to make it possible to easily and quickly bias your device's configuration for performance, or battery, or a balance between the two.
On a modern device with 4 cores, and 2.2 GHz CPU (or whatever), this is frankly excessive for simple tasks. OEMs usually excessively prioritise performance so their device feels "snappy", leaving battery performance poor.
Roadrunner lets you reduce "raw" speed, but gain better battery life.
pulser_g2 said:
Yes, we intend to include legacy device support as a key feature. I'll go into this in more detail later, but this was one of our founding "aims".
Provided compatibility for legacy devices can be implemented "neatly" without impacting other devices, it's actively encouraged
Custom ROMs were meant to extend the useful lives of phones, not leave phones dangling without support
Click to expand...
Click to collapse
I will try to get @PecanCM involved, as well as the members from androidarmv6. They'll have a few patches to push up
Because we use different sets of qcom hardware sources, can I ask for them to be able to be fetched from different github users/organisations, just to keep the source code tidier?
Sent from my Nexus 7 using Tapatalk now Free
LG italy confirmed that O4X won't receive kitkat
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No news...
Did you really thought we would get an official update ?!
LG can not even support their current flagships , so why update an old device ?
Gesendet von meinem A210
hallodrix said:
No news...
Did you really thought we would get an official update ?!
LG can not even support their current flagships , so why update an old device ?
Gesendet von meinem A210
Click to expand...
Click to collapse
There was a little chance half a year ago when Hungarian LG support told me they will make KK for our device... And Yes its another thread about android 4.4 :banghead::banghead::banghead:
Sent from my LG-P880 using xda app-developers app
PenguinStyle said:
There was a little chance half a year ago when Hungarian LG support told me they will make KK for our device... And Yes its another thread about android 4.4 :banghead::banghead::banghead:
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
When you know that the Samsung S3 is getting kitkat and the main features of the current flagships, you just lose faith in LG, I dropped that phone 5 months ago because it was making me sick, and went for the original HTC One, and the support is still going on year after the release, not a very good strategy to keep consummers ...
Achraf4X said:
When you know that the Samsung S3 is getting kitkat and the main features of the current flagships, you just lose faith in LG, I dropped that phone 5 months ago because it was making me sick, and went for the original HTC One, and the support is still going on year after the release, not a very good strategy to keep consummers ...
Click to expand...
Click to collapse
Flash a custom rom and BAM you have the latest 4.4 or enox and you have a G2 and G Pro in one phone
Sent from my LG-P880 using xda app-developers app
Solution is cm 11 flash and relax
LG-P880 cihazımdan gönderildi
PenguinStyle said:
Flash a custom rom and BAM you have the latest 4.4 or enox and you have a G2 and G Pro in one phone
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
I did, I was on CM, on Vanir, and back to 4.1.2 on Enox and then on Zaiben, using iodak kernel... but I had some bootloops, and since I was too excited whenever I tried a new ROM, I didn't backup, I lost everything and it did kinda piss me off, what I mean is that the average consummer doesn't have to go through all this, we were proud when we bought the phone to say it's a Samsung S3-killer, but how about now?
This is why my next phone will be a nexus. No problems with updates. I should had bought the nexus 4...
Sent from my LG-P880 using XDA Premium 4 mobile app
I just want to make it clear, that flashing the latest 4.4 custom rom is not equivalent to an update from LG. Even if LG gave us 4.2, we would get new blobs (these contain proprietary drivers, this costs LG to distribute) The blobs LG have left us with are a mess, Lots of incompatibilities with Android 4.4, this will only increase with each android update.
This would normally spell the end of third party support (custom roms etc), but the awesome work of the p880-dev team, allowed us to use Nexus7 blobs which are compatible with Android 4.4 and beyond, the issue here is, while the nexus7 has similar hardware, its not identical and those blobs are 100% compatible with our device.
We have been let down by LG quite badly, hopefully the next device you buy (be it a smartphone or tablet) is influenced by its manufacturers history if releasing appropriate updates to it devices, low to high end.
JoinTheRealms said:
I just want to make it clear, that flashing the latest 4.4 custom rom is not equivalent to an update from LG. Even if LG gave us 4.2, we would get new blobs (these contain proprietary drivers, this costs LG to distribute) The blobs LG have left us with are a mess, Lots of incompatibilities with Android 4.4, this will only increase with each android update.
This would normally spell the end of third party support (custom roms etc), but the awesome work of the p880-dev team, allowed us to use Nexus7 blobs which are compatible with Android 4.4 and beyond, the issue here is, while the nexus7 has similar hardware, its not identical and those blobs are 100% compatible with our device.
We have been let down by LG quite badly, hopefully the next device you buy (be it a smartphone or tablet) is influenced by its manufacturers history if releasing appropriate updates to it devices, low to high end.
Click to expand...
Click to collapse
Question: considering the point you have superbly explained; considering that we need updated drivers and updated blobs, to make everything working with Android 4.4.x and superiors; has Nvidia released some new code (or may release it, if someone pay for it), fully compatible with our device, which is possible to work on, or is our chipset and other hardware stuff limited by outdated code, to be compatible with newer Android versions, and the only way to achieve a full compatibility would be receiving LG (impossible) updates?
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
peppethustra said:
Question: considering the point you have superbly explained; considering that we need updated drivers and updated blobs, to make everything working with Android 4.4.x and superiors; has Nvidia released some new code (or may release it, if someone pay for it), fully compatible with our device, which is possible to work on, or is our chipset and other hardware stuff limited by outdated code, to be compatible with newer Android versions, and the only way to achieve a full compatibility would be receiving LG (impossible) updates?
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I dont want to go to deep, as im no expert. my assumption is (and if im wrong, i hope to be corrected) Nvidia modify their reference drivers to LGs specifications, this presumably costs LG a lot of money to have done. From any means though, we are not gonna receive specific blob updates, The problem for us is LG only have a single tegra 3 device, it doesn't make a great business case to pay for an update that only one phone or device can benefit from, comparatively Asus could essentially update 5 devices for the same price.
Grouper blobs should ensure us the Android updates the nexus 7 receives, but its likely gonna be a rocky road with future updates, like 4.3 to 4.4. No one really know for sure though
JoinTheRealms said:
I dont want to go to deep, as im no expert. my assumption is (and if im wrong, i hope to be corrected) Nvidia modify their reference drivers to LGs specifications, this presumably costs LG a lot of money to have done. From any means though, we are not gonna receive specific blob updates, The problem for us is LG only have a single tegra 3 device, it doesn't make a great business case to pay for an update that only one phone or device can benefit from, comparatively Asus could essentially update 5 devices for the same price.
Grouper blobs should ensure us the Android updates the nexus 7 receives, but its likely gonna be a rocky road with future updates, like 4.3 to 4.4. No one really know for sure though
Click to expand...
Click to collapse
Yep, I only hope we'll not see our device losing some functions, everytime a new android release will come (like viderecording on kitkat)..I know, a phone is not eternal, but I'd like to see it supported until it has the necessary specs to be supported, at least by a great dev community as our is..and our devs are really working hard! But it would be great, having something to do with Nvidia to release new code
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Can some MOD close this thread please its USELESS.
Sent from my LG-P880 using XDA Premium 4 mobile app
sPEADy said:
Can some MOD close this thread please its USELESS.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I take it there isn't official word or press release yet then?
The problem isn't the phone(s), its the carriers and manufacturers, they kill it. With exception of a few, Samsung, HTC, LG surely sucks more, but I've seen complains from every manufacturer.
Sent from my LG-P880 using xda app-developers app
It's been discarded and forgotten by LG and nVidia so fast, I'm still amazed we even got a 4.1 update. A former top-of-the-line device that's not even 2 full years old! Imagine you got it on 24-month contract last year, as some did.
We should flood their twitter and facebook and whatnot.
MidnightDevil said:
We should flood their twitter and facebook and whatnot.
Click to expand...
Click to collapse
I wouldn't flood social media but I am going to write to LG and ask what is going on as the Apple buisiness model doesn't work with Android.
If KitKat goes to the HTC One X and not the Optimus 4x then LG have screwed up yet again.
The Galaxy S2 Went from Android 2.2, to 2.3 Gingerbread, 4 ICS and then 4.2 Jelly Bean which I assume it will not be upgraded to Kitkat unless you want a Custom ROM
In comparison - The Optimus 2x - Android 2.2, 2.3 then stopped at ICS
Was it because the 2x wasn't seen as successful or as best selling as Samsung is that why they stopped support as it wasn't commercially viable to support a rare device?
Or because they are trying to keep each individual device unique in some way? QSlide went to the Optimus G but not the 4x
Apple support model is very different from Android.
First, because Apple has a very specific range of hardware to support. One update works for every version of their phones (3G, 4S, 5, etc..). Since the hardware between versions is the same or with very little differences.
In this scenario, I'm led to believe our 4X was surpassed quickly since LG release the 4X, and soon after G and G2, so 4X was "forgotten" in the middle. Too bad, since was a flagship phone, didn't got the attention it should.
If the sales weren't what they were expecting, (but they were still sales nonetheless), I guess investing in time and money for a software update which very few people use, isn't exactly a good step, however, there's a good ton of people which use the 4X. It has a good hardware, would support KitKat easily, but I guess it's easier and more profitable to release another high end device and support that one instead, even if equally for a short time.
When I bought my 4X, around 6 months ago, there were posts already mentioning no update for 4.3, i doubt LG would be kindhearted enough to release a KitKat update. But they could at least release the binaries for devs to develop custom roms easier. Oh, but they don't want that either.
Last phone from LG, for sure.
Captain Sisko said:
I wouldn't flood social media but I am going to write to LG and ask what is going on as the Apple buisiness model doesn't work with Android.
If KitKat goes to the HTC One X and not the Optimus 4x then LG have screwed up yet again.
The Galaxy S2 Went from Android 2.2, to 2.3 Gingerbread, 4 ICS and then 4.2 Jelly Bean which I assume it will not be upgraded to Kitkat unless you want a Custom ROM
In comparison - The Optimus 2x - Android 2.2, 2.3 then stopped at ICS
Was it because the 2x wasn't seen as successful or as best selling as Samsung is that why they stopped support as it wasn't commercially viable to support a rare device?
Or because they are trying to keep each individual device unique in some way? QSlide went to the Optimus G but not the 4x
Click to expand...
Click to collapse
You raise some good points Midnight I emailed LG and this was their reply.......
I have had a look into this for you and due to the age of the handset and reaching the end of it's update cycle, KitKat will not unfortunately be coming to the P880. I do apologise I couldn't be of anymore help but if you have anymore questions please don't hesitate to email back in. Have a great evening!
Kind regards
Rob
LG Electronics UK Help desk
----------------------------------
LG Customer Services
UK: 0844 847 5454 Ireland: 0818 27 6954
Mon-Fri 9am to 7:30pm Sat 9am to 6pm Sunday 10am to 4pm
Closed bank holidays
www.lg.com/uk <http://www.lg.com/uk>
You can even reach us via our Web Chat facility through the LG UK website
<http://www.lg.com/uk/support/contact-customer-support>
They can't be serious!
My first android device was Samsung Galaxy Ace. Which was quite nice until I got to know that it won’t receive upgrades past Gingerbread. So, I bought a Galaxy SII. SII was an amazing phone. A great bump in performance and screen size for me after Galaxy Ace. Also SII had the sweet Ice Cream Sandwich. It also got updated to Jelly Bean (4.1.2). Then I made the switch to Galaxy SIII. Which at the time of my purchase still had the same software 4.1.2. Now, it didn’t feel like a huge upgrade in terms of how my phone looked. Except a couple of add-ons the software was similar. Then a 4.2.2 was leaked around the same time when Google released 4.3 and I updated to it, hoping it would bring some fresh change but it wasn’t much. And it had bugs too. I waited for the bugs to be fixed but then Samsung announced that they are skipping 4.2.2 for SIII and will directly update it to 4.3. I was kind of sad but it was good to know that it was getting updated to 4.3. Though when the actual update came out, this was around the time Google announced KitKat, it was again filled with bugs. Now, that wasn’t a leak that was the official update from Samsung and then they stopped the update temporarily to fix the bugs. They released one more 4.3 update after addressing those bugs from previous one but this one had more. And those never got addressed. Then Samsung announced that the international version of SIII, the one I had, will not receive upgrade to Android 4.4 as 1 GB RAM is not enough to run Samsung customizations smoothly. But the versions with 2GB RAM will receive the updates. Some people appreciated Samsung for actually working on to release an upgrade for a device that was out of the conventional upgrade period. But those people need to evaluate the facts that SIII was the company’s most successful phone. Also when you see the timeline of when the updates were released you realise that every update was released almost around 6 months of announcement from Google.
After being fed up with their update system I made the switch to Nexus 5. Even though I haven’t received any major updates, the vanilla android experience itself has been pretty great. And when I compared it to a GS5 running 4.4, I was even more happy. The time to time lag on S5 when switching between apps or the app opening speed or the lag when opening the recent app menu, they all just make me a little bit happier that I am not a Samsung customer anymore.
I just switched from the Samsung S4 to the N% a few weeks ago.
Even though the screen sizes are the "Same" the N5 has a little less usable space because of the soft keys. The S4 has keys below the screen.
No big deal for me though.
The N5 test slower on AnTuTu and Quadrant than the S4, however the N5 is a ton faster than the S4 on everything that I do, for screen scrooling, to app launching, to web sites loading, everything.
The N5 simply leaves the S4 in the dust.
I'm very impressed so far, and happy about the switch.
I still have the S4 as a backup if needed.
Fred
Fred98TJ said:
I just switched from the Samsung S4 to the N% a few weeks ago.
Even though the screen sizes are the "Same" the N5 has a little less usable space because of the soft keys. The S4 has keys below the screen.
No big deal for me though.
Fred
Click to expand...
Click to collapse
Benchmarks don't come into play. they sure as hell don't prove the speed and performance we get on nexus.
about those soft-keys. this what I recently did.
installed LMT
disabled navigation bar
I am running stock on ART. so no xposed module for me
WeandDroid said:
Benchmarks don't come into play. they sure as hell don't prove the speed and performance we get on nexus.
about those soft-keys. this what I recently did.
installed LMT
disabled navigation bar
I am running stock on ART. so no xposed module for me
Click to expand...
Click to collapse
What's LMT?
Gesendet von meinem Nexus 5 mit Tapatalk
Flooney said:
What's LMT?
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1330150
Sent from my PARANOID HAMMERHEAD
Fred98TJ said:
I just switched from the Samsung S4 to the N% a few weeks ago.
Even though the screen sizes are the "Same" the N5 has a little less usable space because of the soft keys. The S4 has keys below the screen.
No big deal for me though.
The N5 test slower on AnTuTu and Quadrant than the S4, however the N5 is a ton faster than the S4 on everything that I do, for screen scrooling, to app launching, to web sites loading, everything.
The N5 simply leaves the S4 in the dust.
I'm very impressed so far, and happy about the switch.
I still have the S4 as a backup if needed.
Fred
Click to expand...
Click to collapse
there is no way a snapdragon 600 can beat a snapdragon 800 in any benchmark
Kippui said:
there is no way a snapdragon 600 can beat a snapdragon 800 in any benchmark
Click to expand...
Click to collapse
samsung devices come with custom dalvik/bionic by default, the nexus does not. becuse it includes a custom dalvik/bionic it scores better. thats why many rooted nexus 5 users flash different dalviks/bionics. the sgs4 can not beat a nexus running custom dalvik/bionic as well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what if you wanted to switch two years ago? you'd still be with Samsung
Kippui said:
there is no way a snapdragon 600 can beat a snapdragon 800 in any benchmark
Click to expand...
Click to collapse
The S4 does score better than a non-rooted N5.
"samsung devices come with custom dalvik/bionic by default, the nexus does not. becuse it includes a custom dalvik/bionic it scores better."
HOWEVER, in real world use my N5 runs circles around my S4.
Fred
Fred98TJ said:
The S4 does score better than a non-rooted N5.
"samsung devices come with custom dalvik/bionic by default, the nexus does not. becuse it includes a custom dalvik/bionic it scores better."
HOWEVER, in real world use my N5 runs circles around my S4.
Fred
Click to expand...
Click to collapse
circles isnt even the right word. my n5 plays in a professional league while my s4 is still TRYING to get onto a minor league team.
WeandDroid said:
Hello everyone
I have written a new blog post about my experience with samsung and why I switched from it. Have a look and feel free to comment and share your experience
POST
Click to expand...
Click to collapse
Why couldn't you post your thoughts here? You make people click your link instead.
Another useless post.
Sent from my Nexus 5 using Tapatalk
TheCybertronian said:
Another useless post.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ironic because you made a useless comment.
On topic: Yeah, I switched from an S3 and was extremely happy. I used to really enjoy touch wiz because of a couple of features but the sluggishness of the phone was getting on my nervous. I flashed a stable built of CM, which wasn't great because that had some pretty serious bugs which annoyed me also. Then the N5 came out and I decided to buy and I am very happy with the experience.
I like nexus 5 but I'm dying to go back to Samsung but i know if i get the galaxy s5 I'll be dying to get back my nexus 5
Sent from my Nexus 5 using Tapatalk
My fiance and I also just ditched Verizon and switched to n5's from s4's. Couldn't be happier. I love Verizon's network but they are overpriced and lock everything down. We are in stl so T-Mobile works just as well.
Sent from my Nexus 5 using Tapatalk
WeandDroid said:
Hello everyone
I have written a new blog post about my experience with samsung and why I switched from it. Have a look and feel free to comment and share your experience
POST
Click to expand...
Click to collapse
Nice post, I think it sums up a lot of users' feelings too. I've never owned a Samsung phone - I started with nexus and have only used nexus since and i couldn't be happier. Between getting major updates first and the rich development community, you have very little limitations with these phones. I just hope that if Google kills the nexus line like they're rumored to, that they still deliver the same experience with future GPE devices (currently, GPE devices are not on par with the nexus line in my opinion).
Sent from my Nexus 4 using Tapatalk
Speaking as a former Galaxy S3 T-Mobile owner, I had to stay that Knox software and bootloader locking is what finally made me give up on the Galaxy series. The Nexus 5 on my opinion is a developer phone and a guideline of what other companies should follow. I'd rather not pay to own hardware that doesn't let me use it in the way I want. Plus no matter how you looked at it TouchWiz was insanely slow because of all the extra features, some of which most people would never use.
Sent from my Nexus 5 using Tapatalk
bblzd said:
Why couldn't you post your thoughts here? You make people click your link instead.
Click to expand...
Click to collapse
Changed that now.
ARTvsDalvik
Next post, both here and on my blog will be ARTvsDalvik. And not just in terms of speed.
I appreciate your positive feedback for this device but there is no necessity for a user review of a device which is almost 6 months old. Thread closed