I still don't get why people think the memory has anything to do with 64 v 32. I have never heard a person ever say "oh you machine is laggy because you have a 64bit machine and not enough memory." until I found this sub-forum. The iPhone/iPad have had 1-2GB of RAM and not had any huge performance issues while being 64bit.
There are memory issues, that's it, nothing to do with it being 64-bit or not. 3GB MAY "fix" the issue, but that would really just mean the machine would go longer until it started to show symptoms. The nexus 5 and 6 had LOTS of memory issues on Android 5 and no one ever said "it's not enough memory" and not being 64bit hardware they couldn't blame that, because it worked fine on 4.X. We have no 4.X to compare with, so everyone just wants to blame 64 bit when really, it just needs more software fixes that Google isn't spending time on.
If anything having a 64bit CPU just means the CPU can work harder and faster, even if it was running 32bit software. I know that not many developers ahve latched on to the n9, but i would NOT be surprised if a few clever ones could figure out what is actually causing the memory leaks/aggressive paging. For example on my n6 it is using about 4-500MB less ram, just to to Android OS and Google App. There is nothign about being 64-bit that means the Kernel needs over 2x's the memory usage. Something is making it keep memory instead of releasing it. I am not smart enough to know what that "something" is, but I'm sure someone that develops and has an N9 is smart enough and can file a bug report for it that we can all upvote.
If there are any current open bug reports for memory usage on the n9 please link them to me, I will gladly upvote them. Lets just be clear there is no reason to suspect this is anything more than a software issue.
To Update:
Here is a bug report i found of the problem, if more people could Star it then it can get up the priority list.
https://code.google.com/p/android/issues/detail?id=175232
People like to blame the 64bit OS because the switch does make processes consume slightly more memory. If implemented poorly, a 64bit OS can eat up a lot more RAM. Windows XP 64, any Itanium based system and many early x64 Linux distributions come to mind.
Somehow Android OS on my N6 averages 220mb, while it's 800+ on the N9. Because the N9 is 64 bit, that change seems to be the obvious culprit. Clearly, the N9 didn't ship with enough RAM based on the OS memory use as somehow the N6 has 3gb for an 220MB OS footprint and the N9 has only 2mb, despite an OS that eats almost 4x the memory.
Switching to a 64bit OS should make the CPU, RAM, etc. all run 'faster', but if there's not enough RAM to hold running software, the experience will slow down as more processes need to be shuffled in and out of RAM. Look at what happens to a computer when it 'runs out of RAM'. The constant game of musical RAM chairs will more than erase any gains from switching to 64 bit.
In my mind, there is no question that SERIOUS problems exist with this device. The fact that this is one of the first 64bit Android devices is almost definitely a contributing factor, but the slightly reduced efficiency of how 64bit memory is allocated can in no way explain the problems with the devices. Something MUCH deeper is going on. Based on some research, here is what I've learned.
1: Some part of the OS is using an obscene amount of memory. Some of this is probably Google's fault because 64 bit Android just wasn't ready. I'm also pretty sure nVidia and HTC are more to blame for this issue than Google.
2: There's still not enough RAM. If the N6 has 3GB, there is no reason why the N9 shouldn't. Most tablet users run more memory-intensive
3: HTC built a bad device. I've had cellular issues with VZW & ATT which have been discussed in these forums and are obviously HTC's fault. I've also read about there being some hardware issues causing the ram to 'freeze' which required a replacement device.
4: nVidia's hardware sucks. More accurately, their x64 bit implementation of the hardware.
5: Graphics: I BELIEVE THIS IS THE GIANT ELEPHANT IN THE ROOM OF ISSUES. The nVidia Shield has similar hardware with a standard HD screen. The N9 has a different aspect ratio and a lot more pixels. The horrible application switching lag even with relatively low memory use (a process that is still taxing on the GPU) makes me think this is the main flaw of the device. This problem could also make the OS eat more memory to make up for the OS issues. A graphics issue would be everyone's fault. Google is to blame for insisting on this change when the other hardware just couldn't support it properly and choosing partners incapable of delivering the hardware to properly support the screen. nVidia and HTC to blame for not providing sufficient hardware and software support for the screen.
In reality, I think several factors combined to produce this issue. The components of the system were designed primarily for 32-bit implementations of Android. 64-bit support was baked into them, but it wasn't the focus of the components. The device itself was probably designed before 64-bit Android was even available to test properly. Because the pieces looked like they should fit together on paper, everyone just assumed they would. Unfortunately,for some components the fact that they could run in 64-bit mode, didn't mean they would run well.
x64 gets blamed because it is unknown. The average user has no idea what it means to have a 64 bit platform vs 32 bit. IMO x64 is unneeded unless you're mapping 4gb or more RAM and doing a lot of computations with large numbers.
There is most certainly a memory penalty since the os must run 64 bit code and likely have a vm of some sort to run all the existing 32 bit stuff. In windows this is obvious as you have program files and program files (x86) folders as well as windows\system32 and windows\syswow64 humorously the former is the 64 bit subsystem and the latter is the x86 subsystem. This is why you should plan ahead when architecting your applications and not name your folders poorly.
All that said, I have an htc m9 in addition to the nexus. The m9 is also 64 bit and has no issues. Not an apples to apples comparison since it is a Qualcomm processor with 3gb of ram and less pixels but it should indicate that 64 bit android is not the problem in and of itself.
Thanks guys. 64-bit apps should use at most 15-20% more RAM compared to their 32-bt counterparts, simply due to the fast that 64-bit assets are larger. The issue we have is that in cases like Android OS, using over 120% more memory than on a 32bit device. It also for some reason seems at times to feel like the GPU is taxed and it definitely should not be. So either the GPU drivers are buggy or the GPU memory is very limited. Luckily much of this is improved on 6.0, but there are still issues that need to be addressed in the OS itself.
Because saying "I do not know why my Nexus 9 performs poorly" is boring. Jumping to conclusions is much more exciting and dramatic.
knitler said:
Thanks guys. 64-bit apps should use at most 15-20% more RAM compared to their 32-bt counterparts, simply due to the fast that 64-bit assets are larger. The issue we have is that in cases like Android OS, using over 120% more memory than on a 32bit device. It also for some reason seems at times to feel like the GPU is taxed and it definitely should not be. So either the GPU drivers are buggy or the GPU memory is very limited. Luckily much of this is improved on 6.0, but there are still issues that need to be addressed in the OS itself.
Click to expand...
Click to collapse
I suspect you are right that there are driver issues. Sadly our only recourse is to wait on nvidia/htc/google to rectify the issue.
Don't know what it is but 6.0 is not what I expected. Jerky , slow loading and very unpleasant to use. Have never rooted or rommed. Don't think I should have to. Did a FDR, no improvement. Have to constantly clear app cache and system cache to make it tolerable. Hoping for some relief from Google
Android 6 on my stock nexus 9 has brought every task switch of any kind to a near unusable lag. 4 to a full 20 seconds is the norm now. In fact, just about every response to user action in every app has this problem now. I've got almost nothing except Google's apps, many of which I don't use, but still have something running.
The tablet is now a paper weight, almost. The delays make it unusable, as you can't tell whether an interface action didn't "take", or is just laggy.
I did this as an update. Should I just wipe and reinstall clean? If so, where do I get the necessary files and instructions?
Thanks for any insight.
Black Friday buy, feeling I'm going to return it, two days in and I can see the issues already
dislplin01 said:
Black Friday buy, feeling I'm going to return it, two days in and I can see the issues already
Click to expand...
Click to collapse
Welcome to the Lagsus 9 owners club [emoji6] Did it ship with latest android version, or did you ota update?
rolldroids said:
Welcome to the Lagsus 9 owners club [emoji6] Did it ship with latest android version, or did you ota update?
Click to expand...
Click to collapse
It had to update, actually had like 7 different updates, I'm pretty sure I'm returning it I'm really unimpressed and most of it is hardware issues that can't be fixed, lack of ram, light bleed, ****ty power and volume buttons, not exactly the thinnest lightest tablet. Don't get me wrong its a nexus and I do like it, but I don't plan on buying another tablet for at least three years and if I'm already feeling a little unhappy
dislplin01 said:
It had to update, actually had like 7 different updates, I'm pretty sure I'm returning it I'm really unimpressed and most of it is hardware issues that can't be fixed, lack of ram, light bleed, ****ty power and volume buttons, not exactly the thinnest lightest tablet. Don't get me wrong its a nexus and I do like it, but I don't plan on buying another tablet for at least three years and if I'm already feeling a little unhappy
Click to expand...
Click to collapse
I wish I would have returned it, but haven't because I thought they were fixing the memory leak. And after fixed it turned out that all other Nexus devices do well but not the n9.
Feel free to try my ROM if you're unsatisfied with what Google has done with stock.
NYCHitman1 said:
Feel free to try my ROM if you're unsatisfied with what Google has done with stock.
Click to expand...
Click to collapse
Does it have lower system ram usage? There are people (like me) who want just use their device as a normal user and get ota updates and not flash the device manually every few weeks. It's very nice that you are sharing it anyway!
Everyone try first "safe mode" on Nexus 9 for 3-5 days to see if this app or hardware problem!
Press and hold power button
pres and hold "power off" option
then choose OK.
If problems gone (lag, resetting) then do factory reset without backup, install app manually not all at once from backup. It helped mine Nexus 9
Sent from my Nexus 9 using Tapatalk
rolldroids said:
Does it have lower system ram usage? There are people (like me) who want just use their device as a normal user and get ota updates and not flash the device manually every few weeks. It's very nice that you are sharing it anyway!
Click to expand...
Click to collapse
I think you'll be happy. Popular quote that people often use is:
You have breathed new life into my Nexus 9.
Click to expand...
Click to collapse
With that said, it's entirely possible to flash one build and stick with it for however long as you wish. When you do decide to update, you simply create a backup, "wipe", and flash the newer build with some gapps. Something to keep in mind here is that Nexus devices were created to be fiddled with. If you aren't fiddling, you aren't getting the full experience. It is a developer's device, after all. :highfive:
If this is a road you do decide to travel down, just be sure to do a lot of reading and understand what you're doing prior to doing it.
NYCHitman1 said:
I think you'll be happy. Popular quote that people often use is:
With that said, it's entirely possible to flash one build and stick with it for however long as you wish. When you do decide to update, you simply create a backup, "wipe", and flash the newer build with some gapps. Something to keep in mind here is that Nexus devices were created to be fiddled with. If you aren't fiddling, you aren't getting the full experience. It is a developer's device, after all. :highfive:
If this is a road you do decide to travel down, just be sure to do a lot of reading and understand what you're doing prior to doing it.
Click to expand...
Click to collapse
It's a normal end user device, too. And for me the only choice. Don't like apple products at all. Don't want to buy a device and then not get updates. To be exactly, I want to know before I buy and not hope that Samsung, lg or whatever are so friendly to update. And, I don't like the modifications they do to the UI. So for me there is no other than Nexus. But I don't want this special fiddling experience. (For now. I will probably install a ROM on my Nexus 7 2012 some day)
According to this document
https://01.org/android-ia/user-guides/android-memory-tuning-android-5.0-and-5.1
64 bit indeed increases ram usage a lot...
I also have the impression that this is rather an issue with the Nvidia chipset or the general hardware design than with the system being 64bit.
This morning I had a very LOL moment when I read the Google Pixel C review of The Verve:
>>The specs are also huge: 3GB of RAM paired to the latest Nvidia X1 64-bit processor. That all seems good, but something is amiss with performance on the Pixel C. There are inexcusable pauses and latency, especially when launching and switching apps. <<
http://www.theverge.com/2015/12/8/9869980/google-pixel-c-tablet-review-android
So the problem still seems to be out of control. Too bad.
There are many threads about the Nexus 9 and memory issues but I have yet to see any reports of specific analysis of the issue on a problem device. I've had no memory issues with the Nexus 9, 7, 7(2013),5 and Asus tablets. I seen no evidence that there are hardware differences between Nexus 9's (except the pre release version tested for FCC emissions had a Miracast chip) and I believe it is down to the apps that users run. In support of this opinion:
Resets are recommended to clear the issues.
Google state at Investigating Your RAM Usage Although Dalvik and ART perform routine garbage collection (GC), this doesn’t mean you can ignore when and where your app allocates and releases memory. In order to provide a stable user experience that allows the system to quickly switch between apps, it is important that your app does not needlessly consume memory when the user is not interacting with it. Has anyone with memory issues looked at the recommended tests at the link above?
The quality of apps published. Anecdotal evidence (I hope it's wrong) that publishing an app on Google store can be done in 30 minutes but Apple requires "days". I've never owned an Apple product I'm just saying that to me, not a software developer, that the compliance standards imposed on the software tested may allow bad coding to slip through.
Related
With the source code now released how long do you guys think it will be before one of these mad catz works through it and optimizes it for the HTC Titan?
http://source.android.com/projects
I'm guessing we will see something within a month. I'm hoping sooner than that because I can't wait to try this out, I've been messing around with the SDK for a while and I'm looking forward to what is to come!
What do you guys think? Will we see one by Friday? By Nov? In one month?? By Christmas??
I hope something soon. I too want to see all the G1 goddiness on my Titan. Who knows. it might even have a working hardware acceleration driver!
my bet is by Christmas... I am planning on keeping an eye on the Vogue android thread by dzo He is the one that was able to get the SDK releases of android running via Haret... and to my understanding the Vogue and Titan are similar enough that most progress that they can make on the vogue will be relevant to the Titan...
I am not going to be getting a new phone anytime soon, so the idea that I might be able to have a new OS to play with on my phone is very enticing
I am excited about this whole android thing! I am not a devoleper, but I do like to modify, and tinker.... I would love to play with android when it gets close to ready, but I am wondering... is it / would it be possible to dual boot an OS with such limited resources? (i am afraid I don't realy understand how the ROM / OS thing works...) Or would it be more of a second device kinda thing untill all of the kinks are worked out?
I would say a hell of a lot sooner if we all stopped waiting and got to work.
I was surprised to receive a call while running it for the first time today. Need alignment and button mappings for a start.
The Titan doesn't meet the minimum system requirements for Android. Android requires 256MB flash memory and 128MB RAM. The Titan has 256MB of flash memory (which means you wouldn't be able to add anything to the phone), but it only has 64MB RAM (which means you're out of luck).
Don't get your hopes up, people.
dumpydooby said:
The Titan doesn't meet the minimum system requirements for Android. Android requires 256MB flash memory and 128MB RAM. The Titan has 256MB of flash memory (which means you wouldn't be able to add anything to the phone), but it only has 64MB RAM (which means you're out of luck).
Don't get your hopes up, people.
Click to expand...
Click to collapse
my hopes aren't up too high, I don't think we will be dual booting, or completely replacing the WM rom with an android rom really, but I don't see any reason why we wouldn't be able to get android running via haret like we have been doing for the past 3 months...
but I am curious, do you have a link to the minimum android requirements?
From my understanding Android was developed to be able to run on just about any device. In an interview with Googles Director of Mobile Platforms, Andy Rubin
Q: What were the primary development challenges for Android? Did you design it with high-end or mainstream hardware in mind, and what are the system requirements?
Rubin: When we built the system, we wanted it to be as flexible as possible. We did a lot of work to write our own library, and it's 250 kilobytes, not 3.4 megabytes.
We took a lot of those types of considerations when we were developing the platform. The platform is capable of running, as I said, on kind of mid- to lower-end devices as well.
We feel that one of the platform's distinguishing features is how it handles access to data. I talked about the mashups on the Internet and everything else. So, although the platform can run in a stripped-down fashion on mass-market phones, we think that the initial devices will be mid- to higher-end phones just because of the data access capabilities of the platform.
The minimal requirements are 32 megabytes of RAM, 32 megabytes of flash, and a 200-megahertz online processor. There are companies within the alliance working to bring that to even lower-power phones.
Click to expand...
Click to collapse
I am aware that this interview is nearly a year old, so things may have changed, but since I cannot find a recent comment on the minimum requirements I have to assume that they still intend for Android to be able to run on a wide variety of hardware, which would include the Titan
But then again, I could be wrong, I might be missing a very obvious link to the minimum requirements for android.
Thanks in advance for the link
It seems that some people here don't understand that we can already run Android on the Titan. Just go here: http://it029000.massey.ac.nz/vogue/ , get the latest version, extract it to \Storage Card\, and then run the haret.exe.
Of course, we still need a lot of work to be done to make it fully usable. The touchscreen needs a bit of fine-tuning, in my opinion (though it's debatable). Another big issue is the keyboard. I think that some are working on it right now, though.
Hello there.
I'm a new Archos 101 16GB User having a mixed experience.
I feel that what I've got has huge potential, but just isn't being fulfilled - don't know if anyone else feels that.
I've come straight to tablets from netbooks and an iPhone, and have tried not to have any preconceived notions about how iPad sets the bar for these devices, although it does seem to be the case.
I'm finding, knowing very little about Android, that manufacturers have apparently rushed to force-fit a phone OS in a bigger package, which in respect of certain features makes the A101 seem like a giant (largeprint) smartphone. An example of this is the way in which the small, dainty iPhone-worthy icons for Apps can only be laid out on the 'desktop' panes with massive margins of space between them because the Android system seems to rigidly adhere to strict grid patterns for layout when really what users in this day and age want is user-definable pixel-perfect precise placement of elements. Of course, even iPhone is lacking this configurability.
Anyway, I'm currently trying to overcome my disappointment with the UI and the usability and consistency of desktops across horizontal and vertical orientations (Beautiful Widgets look 'OK' in portrait layout, and fugly in horizontal orientation), indeed the feeling that while what I wanted was the unified visual goodness of a WindowsMobile 7 type platform (or indeed the style brought by both HTC and third party developers (SPB?) to WinMo6, or indeed the carefully tuned visual loveliness of some of the HTC Android skins (Sense?) what I've actually got is a pretty clunky and grumpy Linux build that doesn't play well with its own software applications.
This is only a seventy two hour evaluation so far.
I've been looking at benchmarking, and have been led to Quadrant.
So I've got a batch of results, and I'm wondering if anyone cares to compare results and then compare notes.
I've already wiped and reinstalled the fresh FroYo firmware on the device, and am using gApps4 from these forums. I've populated with some apps and such, and had very unsatisfying attempts to switch from the stock Launcher (LauncherPro and ADW) as well as attempting to find usability in QuickDeskPro, mostly to no avail.
So in this 'stock' but loaded with apps state, Quadrant gives me a result of 780.
Then I've rooted with z4root and run SetCPU to give me 1000mhz on demand, and Quadrant gives me a result of 933.
Since then I've used SetCPU to give me 1000mhz on the 'performance' (non-scaled) setting and I get a result of 974.
With people in various forums talking about Archos Internet Tablet devices running Froyo giving them up to 1200 under Quadrant, I'm wondering what I'm doing wrong or lacking?
The 1200 scores you are talking about came from beta software and not the release software. Something was changed in the release version that brought Quadrant scores back down to those of 2.1. Don't read to much in to Quadrant scores though as they don't really affect real world use.
As for apps, the main issue is screen size and resolution. Many apps were not written with a resolution of 1024X600 in mind. So they don't scale very well. Beautiful Widgets is one of those. Once more developers become tablet aware and as Google increases compatibility with tablets this issue will go away.
The Android home screen is what you make it. There are other launcher, as you mentioned, that can be more customized however, there is no real theming that can be done on the 101 until it is rooted. This is the same for all Android devices unless of course you get a phone from HTC or one of the other OEMs that add their own theme to Android.
I think your main issue is that you know very little about Android and you are expecting it to be as evolved as iOS is even though it hasn't been around as long. New version of Android are coming that will be prettier and more tablet friendly but it will take a little time for it to be perfected.
with another beta beta firmware
the score is 1313
cajl said:
with another beta beta firmware
the score is 1313
Click to expand...
Click to collapse
any rumors regarding the release date?
About the same scores here. Topping out around 1000 in quadrant and a bit over 13 in Linpack.
Not sure about your problems installing launcherpro and adw, but I would try one or both again. The stock browser is horrendous in comparison (laggy, takes much longer swipes to see action, etc).
czesiu said:
any rumors regarding the release date?
Click to expand...
Click to collapse
With the A5A last year they gave us one on 14 Dec and another on 24 Dec.
Allen
AllenPapapetrou said:
and another on 24 Dec.
Click to expand...
Click to collapse
crazy Archos devs
no firmware the friday
cajl said:
no firmware the friday
Click to expand...
Click to collapse
?
________________
I get 820 on a temp-rooted archos 101 8GB with 1GHz set by set cpu.
Appearently the H264-coding takes much too long... my htc desire takes a fraction of a second to pass this test while the archos takes several seconds (20+). I read in another thread that the hardware isn't supported yet by Android-API on the Archos, which will be changed in the future, i presume.
Another glitch: The second 3D-test is much slower than on the Desire (7fps compared to 25), with some errors on the moon (black triangles). Perhaps the OpenGLS-driver is faulty in some way. The first 3D-test, however, shows 3-5 frames more per second than the Desire (clocked at 1152 MHz).
Thanks for the input, guys. I'm sure you all know how comforting, and useful it is to be able to geek out on a forum, compare stories and get tips.
BlazingWolf, I'm certain that you're right. Android is entirely new to me other than a quick fiddle (ooh-err) with a Sammy GTab in a branch of PCWorld with a snotty little elf breathing down my neck to see if he could play games on it.
My big mistake in starting to experiment with this device was that I came at it from an iPhone background, expecting to just load up a device with apps from an app store and watch as it sings, dances and performs tricks for me.
I'm back down to earth with a bump (and not in a bad way) because of the greater openness, some would say 'fragmentation' of the Android platform which creates a scenario similar to that in the PC world where we can have any one of a number of preconfigured devices using specific but sometimes unique chipset combinations, with an array of OS's and software that can be installed on them.
I'm sure one day Android will mature to the place where we begin to see such harmony on the software front end in such a way as the hardware backend becomes irrelevant.
My first 72 hours with the device were bitty. I was expecting these instant results and instant satisfaction, and progress didn't really start to be achieved until I'd wiped the A101 and reinstalled 2.2 from scratch. That's a daunting task, especially to a casual user who might buy this off the shelf. Of course, I'm sure Archos are already looking at that and working to fix it so that the product is good to go from the off.
I'm warming very quickly to the A101. I want to like it. I still have an A504wifi which has only ever been used as a much-loved, if clunky looking and with a sucky interface, portable video player, which has had a great deal of use. So I've been excited about the A101 for a while.
And as a device it is an odd one to classify. The inevitable comparison with the iPad is not necessarily as clear cut as it seems. We have to be utilitarian, sometimes, in looking at these things. The iPad fulfils a multiple of tasks, like the Archos, and it does it within a tightly regulated and strictly defined 'controlled' environment which pushes constantly at 'parity' across all contemporary devices (the OS version for example). This gives us an elegant, reliable but inflexible interface, the trade-off for which is the relative safety of the apps in the app store. The Archos, on the other hand, has a less than elegant interface, is suffering from the issues of platform fragmentation and the remote relationship between the OS developer and the hardware manufacturer, has an App Store full of garbage that doesn't work properly but might get fixed one day, and takes a lot of 'taming' as an all-round package in order to get consistent and satisfying results. That said, the nature of the more open platform affords more opportunities, akind to jailbreaking the iDevices, in successfully customising the device to complete satisfaction, and as already said assuming the OS platform is sufficiently developed to catch up with these new 'tablet' formats, especially the larger screen varieties, we could see something really special and really refined happening.
Where the Archos succeeds, however, is that it is clearly a better platform for at least two of the intended functions of the iPad. We've got a better movie player, capable of working with more formats, with instant HDMI output, and with a proper widescreen display instead of the iPad's nearly 4:3 widescreen letterbox squinty vision. We've also got a better e-reader than the Apple ArmBreaker. OK, the bezel on the iPad is easier to grip single-handed than the Archos's much thinner, but much more elegant design, but this is a device I can sit in an armchair with and actually fall asleep while still holding the thing (I know... it happened). With an iPad, I have to keep shuffling position because the thing is so dang heavy.
The Archos seems to be only a few shades shy of perfect, as far as a hardware platform goes.
Granted, Tegra2 might be fun. And definately the low amount of RAM is an inexplicable and bizarre mistake. Plus we could have done with a 32Gb storage option. Oh, and a more easily viewable screen would be nice.
But as I tweek the thing, and accept the failings of OS and softwares, while anticipating future fixes, I'm really getting to like the little fella. I just need a really nice case to cart it around in, and a decent size memory card so I can store more, and I suspect that if someone can make a permanent root happen, that will pave the way to things like 'Startup Managers' so I can stop some of these apps auto loading when I don't need them to.
A question, though... is there any reason why the MicroSD capacity is listed as being limited to 32GB? Is that an actual capacity ceiling, or is it just the number that was most commonly available or tested at the time? Is the hardware limited to 32Gig or is it Android which is limited? Can the Archos 101 'scale' as MicroSD capacities get larger, or are we literally stuck with 32GB?
I've had no issues with build quality, possibly because I don't expect it to be as solid as an iPad, being a cheaper price and different materials. I've never really had much history of busting my devices with rough treatment or accidents, and even my 'expensive' iPhone 3GS has experienced the not-uncommon 'natural' phenomena of cracks appearing in the back casing around the dock port.
One thing I did notice is that when the A101 first arrived fresh from FedEx the box was freezing cold and so was the device, and when I unpackaged it, the top edge of the device (top of the screen when held in landscape) appeared to be quite significantly convex in shape, arced, not separated from the glass in any way, but definitely bulging. I did a lot of pressing back down on the bulge and letting the device get to room temperature before this 'bulge' became minimal. It is there ever so slightly even now, but doesn't appear to be putting any pressure or distortion on the screen.
Oh, and I think it is just the viewing angle issue, but when I hold the device in portrait to browse long pages or long lists, it almost appears as if the screen itself is convex, and I tend to tilt it back and forth to change the viewing angle on each section of the screen. The screen could definately have been executed better, and I don't think it would have raised the price too significantly.
Any other tips for an A101 n00b would be greatly welcomed.
32GB is atm the maximum you can build a sd to.
The std doesn't give more.
There is a new spec by sony that has more, but it seems not compatible.
I'm not sure if you're interested, but my Samsung Galaxy S used to only do about 900 on the Quadrant benchmark with Android 2.1, it was laggy and slow and really seemed a bit disappointing! Then came Froyo! My oh my, what a difference, unbelievable! It's snappy, touch, and it's there, spin, and it spins, breath, and it feels you! And, it also performs excellently in a Quandrant test now, usually in excess of 1700, even out performs most Nexus One phones I think.
It's absolutely blown me away that a simple software upgrade could entirely change a user experience so much! Battery life has also improved dramatically, at times giving me upto 12 hours or more with general use (regular texting plus photos etc). Which is really great for a 1500mAh battery.
So, I wouldn't give up. Froyo is a really smooth incarnation of Android, and future releases will no doubt get even better. It's exciting seeing what having a company as powerful as Google, backing an opensource project like Android can achieve.
While Microsoft and other companies are focusing purely on developing products from a financial profitability standpoint, Google seems to be able to focus more on simply developing a really excellent product.
I think the biggest 'downside' to Android is that numerous companies overload it with bloatware and don't optomise it enough for their hard ware. There is maybe just a general lack of understanding on the importance of making Android work WITH not against the hardware it's on.
Keep the faith though, have a play around with it and I'm sure eventually things will improve for you, otherwise, if you're really disappointed just go and buy a Samsung Galaxy tab or something similar! Samsung does a really good job, even though they take a looooooong time for updates!
Just ran quadrant, score was 1380. Gapps5 launcher pro plus non root.
2500 with urukdroid build
Recently ive been wondering why android is so different compared to windows?
I mean, although android 2.2, 2.3, (2.4) is out and running, only a small percentage of the phones actually got the upgrade, and most of em are still running 2.1 or lower for the time being, so what is the point in having a new firmware available if you cant run it on your phone anyway ?
Android is just a firmware right ? So why cant it be like windows, when there is a new version, no matter what specs or brand of PC, you just install and your up and running... And phones are just like small computers right ?
So why doenst google make android just as compatible as windows, and as soon as a new version comes out, we just install it and were good to go ? I know this is sort or less the whole point of it being open source, but there has to be a solution to this.
This would actually make so much more sense than it is right now! I know all phone-brands want to add there personal touch to there android phones like SE did with timescape and mediascape etc, but its all just based on the same firmware right ? So why cant these things like timescape and mediascape be seen like an update ? rather than fully integrated in the firmware ?
In my opinion, phone brands should go back to what they are actually good at.. manufacturing phones, and google should go back to what they are good at, designing new android versions, this shouldn't be the other way around.
Could one of you pls explain this to me ?
As a master student in economics, IF android could actually be compared like windows as I just explained, this would only have positive effects on the android/phone market, instead of all these angry and disappointed customers...
http://gizmodo.com/5733556/the-complete-state-of-android-froyo-upgrades
this threat is what made me write this, it is clear we are not the only ones stuck with 2.1 (but the gods at XDA are doing their best to fix this!)
I understand your point. My take on it is about the fragmentation. I'm not commenting whether it is good or not, but here's what I think. Windows machine have a much higher memory where they can store drivers, settings, etc. Just Windows XP alone took approx 6GB? I don't think phones can have that much internal memory at the moment. Also, PC's have interfaces where everything comes out to the correct machine language (PCI, SATA, etc) While these lacks on phones. They have different architectures and peripherals that supports only that architecture. Therefore, to keep it lightweight, it is the manufacturer's responsibility that if they are using OS such as Android, that the OS works with their hardware, while on PC, it's more hardware to work with the OS.
I'm sure if there's a universal hardware interface for mobile devices and enough internal memory, your wish will come true
unknown13x said:
I understand your point. My take on it is about the fragmentation. I'm not commenting whether it is good or not, but here's what I think. Windows machine have a much higher memory where they can store drivers, settings, etc. Just Windows XP alone took approx 6GB? I don't think phones can have that much internal memory at the moment. Also, PC's have interfaces where everything comes out to the correct machine language (PCI, SATA, etc) While these lacks on phones. They have different architectures and peripherals that supports only that architecture. Therefore, to keep it lightweight, it is the manufacturer's responsibility that if they are using OS such as Android, that the OS works with their hardware, while on PC, it's more hardware to work with the OS.
I'm sure if there's a universal hardware interface for mobile devices and enough internal memory, your wish will come true
Click to expand...
Click to collapse
I understand what you are saying, but then again, why dont we just manufacture android phones based on the same architecture ? So they will all be compatible with every version of android ?
If this could be accomplished in some way, manufacturers wont have to deal with the lack of compatibility of newer versions anymore, and every phone will run optimal with any given firmware.
Android is at the same development stage as windows when it was win.dos, effectively; the future development was not foreseen. The aggressive marketing by ms changed that, obviously, but pcs from that era are hopelessly outdated. Mobile manufacturers are keeping up with Google rather than being dictated to by them. Eventually, a physical threshold will result in Android updates being software instead of hardware.
I think...
Sent from my X10i using XDA App
android is a fairly new n young operating system... its hardly 2 yrs old....
give it time... the way its goin now it headed in the right direction (same as windows)... compatibility issues will be sorted as time progresses... bare in mind that android devices span vast array of price ranges (and thus diff hardware as suited for that price) so compatibility will be an issue which will be sorted out in time...
clintax said:
I understand what you are saying, but then again, why dont we just manufacture android phones based on the same architecture ? So they will all be compatible with every version of android ?
If this could be accomplished in some way, manufacturers wont have to deal with the lack of compatibility of newer versions anymore, and every phone will run optimal with any given firmware.
Click to expand...
Click to collapse
The problem is there's too many architecture to go for. A universal architecture means we're eliminating many companies. For example, say we choose snapdragon as our universal. That means ARM, NVIDIA, will all be taken out the competition. Of course ARM cannot build a microcontroller based on snapdragon's design either, this is due to licensing and such. I'm sure manufacturer wants something like you said, it will be much easier to manage, but chip makers are doing things their own way. Also, you have to consider how much new technology is being introduced to phones in just one year. It is massive. Even if phones have the same architecture, the problem that comes about is the memory size to store all the drivers. Either way, it will have to go through the manufacturer to strip it out, which would be back to where we start again. So it will not work out anytime soon...However I did heard Google is aiming to make a flexible Android where it can do something like you said, but looking at the hardware change, it's impossible for now
FWIW - I think that it's more to do with USP's - Each manufacturer could, quickly and fairly easily just bung stock android onto their hardware, and therefore make it extremely easy for us all to upgrade to the latest OS.. but they think.. "hang on, if we do that then all the phones will look and work in the same way.. why would anyone want to buy ours, over xxx competitors phone... no that simply won't do.. we must make our phones special, different and more appealing to XYXY subset of the market... that way we'll sell more phones than our competitors and eventually.. if we're lucky, we might just compete with Apple"..
Or something along those lines!
Gawd - I thought for a minute you actually wanted Android to be "like" Windows...
I nearly pooped myself.
k1sr said:
Gawd - I thought for a minute you actually wanted Android to be "like" Windows...
I nearly pooped myself.
Click to expand...
Click to collapse
I was thinking the same way! Windows? Nah! Windows itself is a bloatware OS...
Deleted...
Afternoon folks.
I'm currently on the fence with the N9, and I may have an opportunity to buy a brand new 16GB for only £130-ish.
However, even at that price I'm not willing to forgive the many sins I'm reading about on here, light bleed, getting extremely hot and not being able to have more than 1 Chrome tab open are deal breakers for me.
I know these problems exist but, to my surprise, this doesn't seem to be a very popular forum compared to the N7 (2013) which is my current tablet (was the N9 a bit of a flop or do people just not develop for it on here??) and I wanted to check if there have been any kind of hardware revisions or software improvements that have made the N9 a great device to use, as it should have been from day one.
So yea, even now a year later, are these problems I'm reading about on here widespread?? If not is there a light at the end of the tunnel or should I just avoid?
Thanks
djbenny1 said:
However, even at that price I'm not willing to forgive the many sins I'm reading about on here, light bleed, getting extremely hot and not being able to have more than 1 Chrome tab open are deal breakers for me.
I know these problems exist but, to my surprise, this doesn't seem to be a very popular forum compared to the N7 (2013) which is my current tablet (was the N9 a bit of a flop or do people just not develop for it on here??) and I wanted to check if there have been any kind of hardware revisions or software improvements that have made the N9 a great device to use, as it should have been from day one.
Click to expand...
Click to collapse
I don't believe there have been any hardware improvements.
You might want to check this thread and this thread as well and read about various folks' experiences. You might also wait a few weeks and check back after Android 6 is rolled out (though I think the consensus among folks running the previews is that it is not much different).
I think the bottom line is that some people are very happy with the N9 and others are very unhappy with it. Some issues, the chrome tab one in particular, seem universal unless you modify your device. Others, like overheating and light bleed, appear to be either luck of the draw or situation-dependent. (I have had neither of those problems -- I had overheating due to a misbehaving app but the app was updated and I never had the issue again.)
djbenny1 said:
However, even at that price I'm not willing to forgive the many sins I'm reading about on here, light bleed, getting extremely hot and not being able to have more than 1 Chrome tab open are deal breakers for me.
Click to expand...
Click to collapse
Obviously everyone has a different experience but I would just like to share that my N9 was perfectly fine. No light bleed issues, doesn't get extremely hot (although it does warm a little after heavy usage but I wouldn't call it "hot") and I frequently have multiple Chrome tabs open (in fact I haven't even heard of this issue until now). So I don't doubt some people are having these issues, but I don't think they are as common as you may think because people without problems generally don't say anything.
djbenny1 said:
I know these problems exist but, to my surprise, this doesn't seem to be a very popular forum compared to the N7 (2013) which is my current tablet (was the N9 a bit of a flop or do people just not develop for it on here??) and I wanted to check if there have been any kind of hardware revisions or software improvements that have made the N9 a great device to use, as it should have been from day one.
Click to expand...
Click to collapse
I can't speak about the difference in popularity of the forums but rooting and flashing roms was fun when I got my first Android device but now I'm happy to have something that "just works" so I don't frequent the forums as much. I don't believe there has been any revisions that changed the hardware.
In the end, I like my N9 but it is obsolete now.
woshiweili said:
Obviously everyone has a different experience but I would just like to share that my N9 was perfectly fine. No light bleed issues, doesn't get extremely hot (although it does warm a little after heavy usage but I wouldn't call it "hot") and I frequently have multiple Chrome tabs open (in fact I haven't even heard of this issue until now). So I don't doubt some people are having these issues, but I don't think they are as common as you may think because people without problems generally don't say anything.
I can't speak about the difference in popularity of the forums but rooting and flashing roms was fun when I got my first Android device but now I'm happy to have something that "just works" so I don't frequent the forums as much. I don't believe there has been any revisions that changed the hardware.
In the end, I like my N9 but it is obsolete now.
Click to expand...
Click to collapse
Obsolete?
What would you say is better? When I checked the other day it was 4th in the list of highest benchmarking android devices.
If you can wait one or two more months, and the price of a new tablet is OK for you, then you might want to wait and see how the Pixel C is doing in the tests.
djbenny1 said:
Obsolete?
What would you say is better? When I checked the other day it was 4th in the list of highest benchmarking android devices.
Click to expand...
Click to collapse
Google just announced Pixel C three days ago. While it may not be an obvious successor to Nexus 9 (perhaps the last Nexus tablet?), it is the most current tablet from Google. Nexus 9 has also been out for about a year, the same amount of time the two previous Nexus tablets were released before they were replaced.
djbenny1 said:
Afternoon folks.
I'm currently on the fence with the N9, and I may have an opportunity to buy a brand new 16GB for only £130-ish.
However, even at that price I'm not willing to forgive the many sins I'm reading about on here, light bleed, getting extremely hot and not being able to have more than 1 Chrome tab open are deal breakers for me.
I know these problems exist but, to my surprise, this doesn't seem to be a very popular forum compared to the N7 (2013) which is my current tablet (was the N9 a bit of a flop or do people just not develop for it on here??) and I wanted to check if there have been any kind of hardware revisions or software improvements that have made the N9 a great device to use, as it should have been from day one.
So yea, even now a year later, are these problems I'm reading about on here widespread?? If not is there a light at the end of the tunnel or should I just avoid?
Thanks
Click to expand...
Click to collapse
Hi, djbenny1...
I've generally avoided answering such questions in the past, partially because the answer is going to be hugely subjective, and partially because it also depends on what your expectations of the device are. If you plan on playing lots of graphic, GPU intensive, high octane video games on it, I would be inclined to look elsewhere for another device.
And it also depends on what you're prepared to pay for it...
At £130 this represents a significant reduction in price, from the original £319 (for the 16Gb model) and £399 (for the 32Gb model) price points, when the Nexus 9 was announced in the Autumn of last year (2014). A quick Google search reveals that the 16Gb model currently retails for around £250, give or take a few quid.
Leaving aside the dull, uninspiring appearance of the Nexus 9, and the reported hardware problems - the flexi-back, the lightbleed issues, (I never had those issues with my Nexus 9, and I've no idea if HTC made changes to the production process to remedy these problems.), but I would be surprised if they haven't, given how widespread those reports where.
...but leaving aside those issues, the problem with the Nexus 9, IMHO, is it tried to do too many things, too quickly...
-----
** Implement the new Android RunTime (ART), replacing the old Dalvik runtime, as part of Lollipop. (And compounded further by a memory leak in the initial release version of Lollipop).
** Along with the Nexus 6 smartphone, it was one of the first devices to run Android on a 64bit platform.
** Run Android encrypted (ie, the data partition) by default. Seamless, on-the-fly, encryption, surely has to have some resource penalty (CPU cycles, etc.), resulting in impaired performance - (See my comments later about encryption.)
-----
All of these elements introduce a multiplicity of 'difficult-to-quantify' variables, whose aggregated deficits cannot be easily foreseen. And introduced together, on one device, and at the same time, seems to me to have been not the best idea from Google. There's certainly no doubting Googles audacity with the Nexus 9, introducing these features, but they did too much, too quickly.
I don't pretend to be either a software or a hardware expert, but everything I know about designing new devices and developing software, suggests that a slower process of design, implementation, testing, and feedback is better in the long run. A slower process of iteration...
...rolling out a new feature on a new device - see how it works in the real world. And then later, add-in a second feature, and see how that works out. Maybe wait for the next device release, before adding in a third feature, and so on and so forth. To quote the old aphorism, "Rome wasn't built in a Day", so why did Google attempt to (metaphorically) do so with the Nexus 9 ??
-----
For my own part, I'm pretty happy with my Nexus 9 .
I'm currently running it with the 3rd Android M developer preview installed, it's rooted, and as a requirement of acquiring root, it's also unencrypted.
And running it without encryption, made a **BIG** difference to my Nexus 9. See my post here from June of this year, and the benchmark results I obtained with AnTuTu as a result of decrypting it.
With regard to the oft reported problem of Chrome reloading tabs... yes, it does do this, but I can't say this is a major problem for me.
I've spent the past few hours drafting and submitting posts on XDA, preparing and sending several emails via MailDroid, and all the while, frequently dipping in and out of Chrome to do some fact checking, and with something like around 20 tabs open. Yes, they do reload (but not every time), but it takes no more than a few seconds. Maybe again, this has something to do with my device not being encrypted. I should also add here, I tend to run Greenify rather aggressively (as I do on all my Android devices), hibernating all the apps I have installed that I can realistically get away with. Obviously I don't hibernate things like widgets, or apps which set alarms, or depend on push notifications... but this leaves more RAM for the 3 or 4 apps I do use on a frequent basis.
-----
So... My Nexus 9 does what I need it to do, which is primarily web browsing via Chrome, email via MailDroid, and posting here on XDA, via a combination of the XDA Premium 4 app and Chrome.
I'm not a big video game player, but I've been known to occasionally indulge in a game of chess, with Shredder Chess, or a game of Sudoku with Andoku 2. The most graphics intensive games I play on it are Temple Run: Oz and Subway Surfers. Both games run without problem. And I can't say my Nexus 9 gets particularly hot... A little warm, yes... but hot - no.
-----
So, should you buy one for £130...??
I would say, if you're prepared to tinker with it a little (Unlock the bootloader, flash ElementalX kernel for decryption purposes), then I think there are worse ways of spending £130.
Another way of looking at it is, what alternative devices are available for £130? What specifications do they have? RAM, CPU, version of Android? Likelihood of further updates to Android? If you want to tinker with it, how easy or difficult is to root or unlock the bootloader?
Would I buy one today for £130?
Yes, I would (if I didn't already have one).
The benefit of hindsight is a wonderful thing - a phrase often used with negative connotations, but I use it here positively. Knowing what I know about it now, and having had it for nearly a year, and how to get the best out of it, I would have no hesitation about buying one for that kind of money... .
-----
Right, I can't think of anything else to add. Which is probably a good thing... I've rambled on far too long as it is .
I don't know if I've clarified a few things for you or muddied the waters further. I hope it's the former .
Anyway, good luck, with whatever you decide.
Kind Rgrds,
Ged.
I was sitting on the fence on whether or not to get the N9 what tipped my hand into buying one was Argos dropping the price down to £179 and I'm very please with it so far. I've got slight screen bleed at the top but this is only noticeble on dark screens.
jonchill said:
I was sitting on the fence on whether or not to get the N9 what tipped my hand into buying one was Argos dropping the price down to £179 and I'm very please with it so far. I've got slight screen bleed at the top but this is only noticeble on dark screens.
Click to expand...
Click to collapse
Yes, the Argos price was too tempting for me also.
I also have a touch of lightbleed which I wouldn't put up with if I'd paid £300. Compared to the Nexus 7 (2013) I think the screen isn't quite as good. The black levels aren't as low but the screen can go a touch brighter.
When you get over the screen however, the speed and small things like always on google now, (even when the screen isn't,) make the tablet worth it.
At £179 I'm happy, at £300 I wouldn't be, at £130, I'd deffo take the chance.
i currently own a asus transformer tf700 which has serious i/o memory lag issues that require monthly flashing. i noticed some people seem to have the same problem with n9. whats the general consensus around here?
Get a Surface Pro 4 instead of Nexus 9. N9 let me down. It was laggy when on 5.0, 5.1 solved that. And recently, my N9 shows some signs of screen mess and buzzing when battery is low. Not sure if it's related to software or hardware.
Sent using XDA One
it really depends on what you want to do with it
Watch movies? get a tablet with a 16:9 resolution instead, this one is 4:3
just some reading? this tablet will do fine
Use it for the occasional stuff like word documents, some games etc? it will still do fine
Serious multitasking? dont even bother with this one
hate redraws or application closing due to running low on memory? again dont bother with this one.
All in all i have the device since it came out, android 6 improved battery life some but honestly its just 1 big disappointment device.
As for the post above me, the N9 and Surface Pro 4 aren't even comparable with each other, spec and price wise. (besides the fact its also 2 different OS systems)
All things aside, the biggest downfall for this device is its 2gb of memory and its rather crappy dual core socket. (wich performs exceptionally well in single-thread, just dont expect anything that has to do with multithread and multitasking)
as for the memory, with the amount of pixels this device has you will average 500~600mb ram just to load most assets. they really should have given this device 3gb memory.
GiantAxe said:
it really depends on what you want to do with it
Watch movies? get a tablet with a 16:9 resolution instead, this one is 4:3
just some reading? this tablet will do fine
Use it for the occasional stuff like word documents, some games etc? it will still do fine
Serious multitasking? dont even bother with this one
hate redraws or application closing due to running low on memory? again dont bother with this one.
All in all i have the device since it came out, android 6 improved battery life some but honestly its just 1 big disappointment device.
As for the post above me, the N9 and Surface Pro 4 aren't even comparable with each other, spec and price wise. (besides the fact its also 2 different OS systems)
All things aside, the biggest downfall for this device is its 2gb of memory and its rather crappy dual core socket. (wich performs exceptionally well in single-thread, just dont expect anything that has to do with multithread and multitasking)
as for the memory, with the amount of pixels this device has you will average 500~600mb ram just to load most assets. they really should have given this device 3gb memory.
Click to expand...
Click to collapse
Yea i just bought for the black Friday sale 279$ for 32gig because 16 gig is just to small. But after looking thru a lot of these threads and seeing all the issues people have I'm seriously considering returning it. I have had every nexus device since the Galaxy nexus and im blown away by how many issues this device has and by the lack of development and just lack of general interest on the forums. 100$ more and i can get the Samsung tab S2 8.4, i actually really don't like Samsung design but with the lack of quality android tablets its either this or a ipad.
dislplin01 said:
Yea i just bought for the black Friday sale 279$ for 32gig because 16 gig is just to small. But after looking thru a lot of these threads and seeing all the issues people have I'm seriously considering returning it. I have had every nexus device since the Galaxy nexus and im blown away by how many issues this device has and by the lack of development and just lack of general interest on the forums. 100$ more and i can get the Samsung tab S2 8.4, i actually really don't like Samsung design but with the lack of quality android tablets its either this or a ipad.
Click to expand...
Click to collapse
we also own a Samsung tab here wich has 3gb of memory, but frankly that device performance is even worse then the n9 due to samsungs bloatware. The only reason for a Samsung tab would be to buy it then flash cyanogenmod on it on something.
But yes, I do agree there is rather a lack of quality android tablets. tbh I might consider just buying a Surface tablet next, they start out at 500 bucks i believe, wich is like 50 bucks more then what i paid for the N9.
The reason I went with nexus devices is purely because they are as stock and bloatware free as possible, but the N9 in general is just bad. my 2012 N5 still performs fine.
We just have to hope for a N9 2016 or something with a quad core cpu (and that not being a nvidia tegra) and 3 or 4gb of memory.
GiantAxe said:
we also own a Samsung tab here wich has 3gb of memory, but frankly that device performance is even worse then the n9 due to samsungs bloatware. The only reason for a Samsung tab would be to buy it then flash cyanogenmod on it on something.
But yes, I do agree there is rather a lack of quality android tablets. tbh I might consider just buying a Surface tablet next, they start out at 500 bucks i believe, wich is like 50 bucks more then what i paid for the N9.
The reason I went with nexus devices is purely because they are as stock and bloatware free as possible, but the N9 in general is just bad. my 2012 N5 still performs fine.
We just have to hope for a N9 2016 or something with a quad core cpu (and that not being a nvidia tegra) and 3 or 4gb of memory.
Click to expand...
Click to collapse
Yea thats why i went nexus too i have a lot of device's but nothing beats a stock version of Android with quick updates, i cant stand samsung bloatware, TouchWiz but it's hardware is the best out there. As far as the surface unless it's a work devise i wouldn't recommend it. I actually have a Dell Venue pro with Windows 10, full version has a beautiful screen fast processor actually quite beautiful tablet . But windows ten as a tablet is terrible if you are just using it to read and watch movies and basic stuff, especially if you are tied into the Google ecosystem. The lack of quality apps just makes it worse there are work arounds for most things but they can usually **** up and generally at the most importune times. I really tried to make it work cause i like the tablet but i just cant, that's why i got this but I'm weighing my options now after reading thru these forums.
I'm also looking to get this tablet haven't had a tablet since 2013 how are the tablet apps for Android?
GiantAxe said:
it really depends on what you want to do with it
Watch movies? get a tablet with a 16:9 resolution instead, this one is 4:3
just some reading? this tablet will do fine
Use it for the occasional stuff like word documents, some games etc? it will still do fine
Serious multitasking? dont even bother with this one
hate redraws or application closing due to running low on memory? again dont bother with this one.
All in all i have the device since it came out, android 6 improved battery life some but honestly its just 1 big disappointment device.
As for the post above me, the N9 and Surface Pro 4 aren't even comparable with each other, spec and price wise. (besides the fact its also 2 different OS systems)
All things aside, the biggest downfall for this device is its 2gb of memory and its rather crappy dual core socket. (wich performs exceptionally well in single-thread, just dont expect anything that has to do with multithread and multitasking)
as for the memory, with the amount of pixels this device has you will average 500~600mb ram just to load most assets. they really should have given this device 3gb memory.
Click to expand...
Click to collapse
Dual core and 2GB RAM works very well for iOS. I don't expect that to mean much but there's no excuse for the performance issues really as a Nexus device is already stripped to bare essentials.
Why do I have no issues whatsoever with my n9!
Verstuurd vanaf mijn HIGHWAY SIGNS met Tapatalk