Currently running pershoots cm9 ics 03.02.2012 version. There have been plenty of nightlies posted since but is there much to gain? I also see Lang versions but still don't know what that means.
This runs better than anything I've used before,but its the only ics rom I've tried.
There's Romans one which is stable and constantly updated before a fortnight, might want to check it out, his thread has the milestone 4, which is the currently stable version
Sent from my GT - I9003 in the bathroom
Any notable improvements? Netflix and pulse run laggy and the browser needs to be open and closed or stops working at times on pershoots. Those are my main complaints.
Well ICS has been built to support the user's needs, only camera doesn't work since Samsung hasn't given us the driver's for those yet, but everything else has been tailored to performance.
Netflix still lags only because of horribly failed ARM mobile flash port which drains more battery and isn't that optimized for Tegra2 devices. It's a common thing on most, don't worry about it, I assume HTML5 would rectify this.
I'm sorry but what is Pulse? These apps are only for the land of milk and honey
Misledz said:
Well ICS has been built to support the user's needs, only camera doesn't work since Samsung hasn't given us the driver's for those yet, but everything else has been tailored to performance.
Netflix still lags only because of horribly failed ARM mobile flash port which drains more battery and isn't that optimized for Tegra2 devices. It's a common thing on most, don't worry about it, I assume HTML5 would rectify this.
I'm sorry but what is Pulse? These apps are only for the land of milk and honey
Click to expand...
Click to collapse
Pulse is a fairly graphic intensive news reader: https://play.google.com/store/apps/details?id=com.alphonso.pulse&hl=en
The time warner cable app is also very laggy.
It's not that theyre unusable, but when in the hell are apps going to run as smooth on Android as they do on an ipad? I like everything about Android platform over ios, but it never runs apps as well. Use flipboard on an ipad and every app on the tab seems choppy and clumsy. Pulse is an excellent reader, and fine replacement, but I just want a smooth responsive scrolling experience.
Thing is android and IOS packages are built differently, where as apple sdk package already has everything needed to make a stable generic app for all IOS devices, the android version has to balance itself in terms of graphics and performance, what's built on an S2 and tested on one will differ on the 10.1, It's sad really
I have tried 3 or 4 ROMs for this phone including miui7 and in all of them there is a fair bit of chopiness... Does anyone know where this comes from? I would blame the SOC but it seems to be able to handle some pretty heavy duty games, it's just not able to handle Google now launcher?
I am thinking that it is either power management or the limited 2 gig of ram.
Wonder if anyone has tried to tweak kernel source for smoothness.
And what is CAF?
Ty
What in the world is CAF?
Remember CAF? You might have seen that name all over the forums back when kernel developers for Qualcomm Snapdragon devices maintained two separate forks of their work. One for code based on Google’s AOSP, and another based on CAF. Code Aurora Forum is maintained by the Linux Foundation, and is where Qualcomm releases the reference sources for their various platforms. Most OEMs base their kernel source off of what’s provided by Qualcomm. On the other hand AOSP works off of a fork of CAF for each Android software iteration, introducing new features for all Android devices along the way. Over time, CAF then introduces its own optimizations intended specifically for Snapdragon devices.
"CAF stands for the Code Aurora Forum. It's the place where Qualcomm releases source code for their phone processors. It's directly supported by Qualcomm and it's generally a more optimized branch for Snapdragon phones.
Now, there are two mainlines for Qualcomm chipsets. We have CAF, and we have AOSP.
CAF is what Qualcomm provides to all hardware vendors, as references and documentation on the chipset. Because of this, almost all non-Nexus devices are running HALs, kernels, etc from the CAF line.
AOSP is direct from Google. Google will take a fork from the CAF like, and add or retract features that they deem necessary, and then produce that for Nexus phones.
So, what this means is CAF ROMs will likely perform marginally better, but they are lacking features added by Google's AOSP line.
As of 4.3 Jelly Bean, CyanogenMod uses a mixture of both CAF and AOSP base, to try and get the best of both worlds.
I hope that helped. "
I have a nexus 9 wifi 16gb and its terrible. I mean, it can't run more than 1 app at a time! All I use it for is reading documents and browsing and most of the time I don't even do them simultaneously, but have to read multiple documents by switching and even for that it doesn't work! It reloads the other app every single time I switch!
I read a few people asking to try custom ROMs for RAM issues, and right now I'm on official lineage os 14.1. Its quite better than stock, but still terrible.
It takes 1.7gb RAM on average out of available 1.8 (for above mentioned usage).
So after reading all about android Oreo go edition and their stupid idea to bring back cheap phones with 1gb ram or less (seriously? To prove that your OS can run on it?), finally I think go edition can bring dead devices like this back to life. So "is it possible to run go edition on nexus 9 and if so, when?" is what I want to know.
And by the way, don't ask me to stop using chrome and other apps. Chrome hardly even takes 50mb of ram on average I also tried uninstalling it. Not much of a difference. I've already seen many ROM recommendations but still any highly recommended suggestions are entertained.
I would actually be willing to give this a try. May breathe new life into my old Nexus 9.
Until now the source code of Android go hasn't been released yet, so we will need to wait for that. When it's released I'm sure someone will give it a try
Go really isn't the issue. If you want to be faster, either run that ported 32bit kernel or run fire and ice or elemental x and change the settings. And no encryption. And perhaps most important, run pure Nexus as it runs better than anything I've tried.
sprockkets said:
Go really isn't the issue. If you want to be faster, either run that ported 32bit kernel or run fire and ice or elemental x and change the settings. And no encryption. And perhaps most important, run pure Nexus as it runs better than anything I've tried.
Click to expand...
Click to collapse
OK I'll give it a try. By the way, do you know any other devices for which the 32 bit kernel is ported(maybe a thread link)? I need it for my redmi note 3 since I believe 32 bit software requires less resources to run overall, leaving more RAM for user apps. This is probably the reason why my oneplus one still works pretty well in RAM management section.
sprockkets said:
Go really isn't the issue. If you want to be faster, either run that ported 32bit kernel or run fire and ice or elemental x and change the settings. And no encryption. And perhaps most important, run pure Nexus as it runs better than anything I've tried.
Click to expand...
Click to collapse
Why do you say that Go won't help? The whole point of Go is to run on crappy hardware like the Nexus 9.
KevlarTheGreat said:
Why do you say that Go won't help? The whole point of Go is to run on crappy hardware like the Nexus 9.
Click to expand...
Click to collapse
Because the Nexus 9 isn't by definition typical crappy hardware. It has 2GB of RAM and it has a "fast" CPU.
The problem is, is that it has a fundamentally different architecture than normal android. You can watch it update and install apps very quickly then take forever to open up a normal app. That's due to how that ridiculous CPU works.
Heck, since all the apps can be installed without the OS you might as well try that.
KevlarTheGreat said:
Why do you say that Go won't help? The whole point of Go is to run on crappy hardware like the Nexus 9.
Click to expand...
Click to collapse
Since when does n9 have crappy hardware? Lol. We all know what the n9's performance issues stem from, and it's not "crappy" or "cheap" hardware. It's a programming language (or CPU language) issue.
Just like @sprockkets said.
Have you tried the 32bit AOSP build? It really helped with RAM management. I can switch to multiple tabs in chrome now without it having to reload every time. Too bad it hasn't been updated lately
madbat99 said:
Since when does n9 have crappy hardware? Lol. We all know what the n9's performance issues stem from, and it's not "crappy" or "cheap" hardware. It's a programming language (or CPU language) issue.
Just like @sprockkets said.
Click to expand...
Click to collapse
Haha, what are you talking about? The programming language used for Android on the Nexus 9 is the same as the programming language for every other version of Android (mostly C, C++, and Java). It's just Android.
CPU language... do you mean the CPU instruction set? The NVIDIA Tegra K1 is a ARMv8-A CPU. ARMv8-A is a 64-bit architecture. It's true that when the Nexus 9 launched 64-bit devices were uncommon, so there were some compatibility issues. But that's far in the past. Every Android device from 2015 and on has a 64-bit CPU. The Nexus 6P, Nexus 5X, Pixel, and Pixel 2 all have ARMv8-A CPUs.
sprockkets said:
Because the Nexus 9 isn't by definition typical crappy hardware. It has 2GB of RAM and it has a "fast" CPU.
The problem is, is that it has a fundamentally different architecture than normal android. You can watch it update and install apps very quickly then take forever to open up a normal app. That's due to how that ridiculous CPU works.
Heck, since all the apps can be installed without the OS you might as well try that.
Click to expand...
Click to collapse
Android Go is not fundamentally different from Android. It's just a stripped down version of Android intended to run on less powerful hardware. Things like multi-tasking and animations are disabled. Android Go is a variation of Oreo. The official name is Android O (Go edition). There will be an Go edition of Android N as well. Google created it to encourage entry level devices to run Oreo rather than some old version of Android as is common in developing countries.
---------- Post added at 04:03 PM ---------- Previous post was at 04:03 PM ----------
As sprockkets said, you can install the Google's (Gmail, YouTube, Maps, etc.) Android Go applications from the Play Store on non-Go devices. Additionally, you can flash this Low-RAM Property Patcher. It sets the flag that tells apps and the The Play Store that you have low RAM. I don't think many apps use this flag right now. But if Go devices become popular, developers may disable some the more memory intensive features (animations for example). Now if you are running Oreo, this will also cause the Android UI to use less RAM.
Although there is at least one Oreo ROM for the Nexus 9, I don't expect them ever to be stable. There are no Oreo drivers for the NVIDIA Tegra K1. And it's doubtful there ever will be. You could ask that developer to build a Go version of the ROM. It may make a difference.
benpage said:
Haha, what are you talking about? The programming language used for Android on the Nexus 9 is the same as the programming language for every other version of Android (mostly C, C++, and Java). It's just Android.
CPU language... do you mean the CPU instruction set? The NVIDIA Tegra K1 is a ARMv8-A CPU. ARMv8-A is a 64-bit architecture. It's true that when the Nexus 9 launched 64-bit devices were uncommon, so there were some compatibility issues. But that's far in the past. Every Android device from 2015 and on has a 64-bit CPU. The Nexus 6P, Nexus 5X, Pixel, and Pixel 2 all have ARMv8-A CPUs.]
Click to expand...
Click to collapse
That is what I meant, ya got me being in a rush, lol.
I meant the difference in nvidia's. As opposed to Qualcomm.
Not between armv7 and armv8
Trying not to get too long winded but...
Perhaps the critical point in understanding Denver then is that it is non-traditional for a high-performance CPU due to its lack of OoOE hardware, and for that reason it’s a CPU unlike any of its contemporaries. We’ll get back to the software aspects of Denver in a bit, but for now it’s enough to understand why NVIDIA has not pursued an OoOE design and what they have pursued instead.
benpage said:
Haha, what are you talking about? The programming language used for Android on the Nexus 9 is the same as the programming language for every other version of Android (mostly C, C++, and Java). It's just Android.
CPU language... do you mean the CPU instruction set? The NVIDIA Tegra K1 is a ARMv8-A CPU. ARMv8-A is a 64-bit architecture. It's true that when the Nexus 9 launched 64-bit devices were uncommon, so there were some compatibility issues. But that's far in the past. Every Android device from 2015 and on has a 64-bit CPU. The Nexus 6P, Nexus 5X, Pixel, and Pixel 2 all have ARMv8-A CPUs.
Click to expand...
Click to collapse
The K1 runs ARMv8 code but if you look at the history of that CPU, you'd realize it was originally made to run x86.
And I'm not really interested in posting the rest of the details - read it for yourself here.
https://www.anandtech.com/show/8701/the-google-nexus-9-review/4
And read pages 2 and 3 for more info, but page 4 has the biggest reason for its wonky performance.
Google's Tensor inside of Pixel 6, Pixel 6 Pro: A Look into Performance & Efficiency:
Google's Tensor inside of Pixel 6, Pixel 6 Pro: A Look into Performance & Efficiency
www.anandtech.com
Just like I expected, very disappointing, to say the least. And Google's optimization is really average (looking at jitter tests on UI bench and jankbenchX). Hopefully they improve things ASAP and also improve A12. I also have some hope since some talented devs will get their hands on this phone.
I agree. I hoped for more. IMO it's an Exynos chip. Sifted through the source code and although this new GKI kernel is a bit different, there are about 20-30 "Exynos" labeled kernel modules.
Other weird things to, like doing some benchmarks while watching CPU/GPU performance. The cortex x-1's will not go past 2.4ghz. Where'd the other ~400mhz go? And all 4 A55's are mostly static at 1800mhz when not loaded. They won't throttle down? Hopefully they do when screen is off....lol?
Just placed my order and can't wait for all the dev, for this device. Been rocking the P3XL for a few years and when I saw the redesign of the 6 I knew I needed to have it