Related
I'm looking to get my first Android tablet. I've always rooted and run custom firmware on my Android phones, so I need a "cheap" Android tablet with a healthy developer community and a lot of support.
My first thought was to go for the $250 Nook Tablet, spec for spec it's better than the Kindle Fire; but didn't an update come out for it recently that made rooting it near impossible or so highly difficult that it hasn't been done yet?
Then the $200 Kindle Fire came to mind, very popular tablet must mean a very healthy/active hacking/dev community right? But isn't it also locked down in such a way it can't be rooted or modified anymore?
Then I see a $189 Lenovo A1 Tablet at Best Buy with decent specs. It's running Android 2.3 which I'd normally prefer over Android 3.0/Honeycomb but now that ICS/Android 4.0 is out, I'd definately want to run that on my tablet. So is ICS running very good/stable on any sub $300 Android tablet?
I wonder when the $250 Tegra3 based tablet from Asus (or is it Acer...) comes out. Suggestions on which route to go?
My friend has a Kindle Fire, and it's too slow to be called a tablet. It's an E-Reader that can run Apps.
Even the web browser - scrolling and loading pages - is laggy.
Colton127 said:
My friend has a Kindle Fire, and it's too slow to be called a tablet. It's an E-Reader that can run Apps.
Even the web browser - scrolling and loading pages - is laggy.
Click to expand...
Click to collapse
Does it run any custom firmware? Or is it 100% stock? The first thing I plan to do is run a custom ROM on it. Even if it's to remove the bloatware and put in a few tweaks, at least it'd be better than stock. My Galaxy S II right now runs a custom ROM based on the factory ROM, so it has full hardware support and such but it's got a lot of tweaks put into it and bloatware removed, etc. the end result is it's got better battery life and runs faster/smoother than any stock Galaxy S II ROM. I'm hoping to get ICS/Android 4.0 onto a tablet, as that's the way to go, but if the dev community isn't quite there yet, then I'm hoping for a custom/tweaked out ROM as a tide-me-over.
glitchsys said:
Does it run any custom firmware? Or is it 100% stock? The first thing I plan to do is run a custom ROM on it. Even if it's to remove the bloatware and put in a few tweaks, at least it'd be better than stock. My Galaxy S II right now runs a custom ROM based on the factory ROM, so it has full hardware support and such but it's got a lot of tweaks put into it and bloatware removed, etc. the end result is it's got better battery life and runs faster/smoother than any stock Galaxy S II ROM. I'm hoping to get ICS/Android 4.0 onto a tablet, as that's the way to go, but if the dev community isn't quite there yet, then I'm hoping for a custom/tweaked out ROM as a tide-me-over.
Click to expand...
Click to collapse
He runs stock rooted with Android Market and a custom launcher.
I tested Opera Mobile on it - which uses full hardware acceleration. It was the smoothest browser I tested on the device, but it was still jittery and lagged while scrolling. The GPU and CPU are obviously not that great.
Colton127 said:
He runs stock rooted with Android Market and a custom launcher.
I tested Opera Mobile on it - which uses full hardware acceleration. It was the smoothest browser I tested on the device, but it was still jittery and lagged while scrolling. The GPU and CPU are obviously not that great.
Click to expand...
Click to collapse
Well it is a cheap tablet new, but I thought it was dual core. Kind of disappointing it's sluggish even with HW acceleration. I just checked the Kindle Fire Android Development forum and it looks like they have ICS/Android 4.0 ROM's for it but the 3 main issues are no HW UI Acceleration; 720p and HD video in general; No bluetooth. I don't care too much for Bluetooth and the 720p video thing isn't that important at the moment (I think), but the no HW UI Acceleration could pose a problem, especially if the CPU is as sluggish as you say.
glitchsys said:
Well it is a cheap tablet new, but I thought it was dual core. Kind of disappointing it's sluggish even with HW acceleration. I just checked the Kindle Fire Android Development forum and it looks like they have ICS/Android 4.0 ROM's for it but the 3 main issues are no HW UI Acceleration; 720p and HD video in general; No bluetooth. I don't care too much for Bluetooth and the 720p video thing isn't that important at the moment (I think), but the no HW UI Acceleration could pose a problem, especially if the CPU is as sluggish as you say.
Click to expand...
Click to collapse
It is Dual-Core, but it was still laggy when I had tested it. I guess it really bothered me because I was so use to the extremely smooth and fluid iPad 2 & Galaxy S II I own and use day-to-day.
I never tested any custom ROMs, but wish I was able to. It seems to have a lot of popular ROMs and a good developer community.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Sorry about that. Thanks for moving this thread/keeping things organized, I really appreciate what you guys do.
Right now I'm leaning toward the HP Touchpad or the Kindle Fire. Seems CM7 is the better option for both devices and good enough as a daily driver; but CM9 is further along on the Fire than it is on the Touchpad.
I'm in about the same situation.
I vastly prefer the 7" form factor, although I could probably be persuaded to a 10" for the same price range...
Currently, I'm leaning towards the 16G Nook Tablet, mostly because of the RAM advantage it has vs the Kindle Fire.
The fire seems to have a more active dev community, but, once it is rooted & has a working ROM (ICS preferred), isn't that the main thing to be looking for?
However, I am not set on any specific tablet, and am very open to suggestions...
I'm still rocking the original Nook Color. Runs CM7 like a champ, and CM9 builds are showing great progress.
For a thread revival, I figured I would state my final decision & reasons for it, just in case anyone else is looking for similar information...
I ended up going with a Nook Tablet...
I considered the Kindle Fire, but it has 512MB vs the 1G of RAM that the Nook has.
Checking the dev status for the Nook, there is a CM7 running (fairly well, now that I've given it a shot). Once that is 100% (and, in my opinion, it is very nearly there), there really isn't much of a reason to avoid it.
In the day I've had it, I have to say that it has ended up being much better than I was expecting.
check out this tablet
/watch?v=JUhiQZE4_VE&feature=g-u-u&context=G2a75f87FUAAAAAAAHAA
it's a youtube link to a NCIX review on a new tablet seems nice for the price I can't post full link cause I don't have enough posts maybe someone can help me out and post it for me? thanks
EDITED as more information about other platforms were found.
Based on my reading here, it sounds like there are two theories exist currently.
1, ASUS using old kernel
2. Tegra chip issue
However, following information seems to challenge these hypothesis..
According to this http://forum.xda-developers.com/show....php?t=1722799, Iconia A700 has very similar result and also Kernel info shows 2.6.39.4+.
So based on this, I think we can hypothesize couple things:
Hypothesis 1: Kernel is the issue
One flag goes against this is that Nexus 7, which uses the latest kernel did not outperform transformer line by much. So it may boost some, but unlikely to be the sole cause of the problem.
Hypothesis 2: Tegra chipset is the issue
On the andropolice benchmark page, they included HTC One X with Tegra 3 version. It actually outperformed it counterpart and in fact was one of the best I/O benchmark result producing unit excluding Nexus Phone. So it is hard to believe Tegra 3 is the issue.
Hypothesis 3: ASUS is the issue
This well may be true, but when you look at Acer Iconia 700 Tegra 3 HD Screen model, it is as bad or perhaps slightly worse than the Transformer Infinity. So perhaps there is a part of kernel that they share or provided by someone?
Hypothesis 4: Tablet SSD/Flash or other common denominator hardware is the issue
Again this is something based on the Iconia vs. Infinity. Infinity has superior CPU and RAM yet the difference in IO is so subtle. This to me suggest bottleneck lies somewhere else. Such as SSD/Flash drive itself? Though I am not sure if that is major advantage of HTC One over Tablet as you would think smaller drives are tends to be slower and more expensive...
I know we still have not answered anything here, but at least, this result make a step further to suggest underlying issue is NOT unique to infinity but perhaps wider problem across the android tablet. If so, the chance of it getting fixed would either depend on the Google or individual manufactures to put unexpected amount of resource into this...
What do you all think?
HoushaSen said:
Based on my reading here, it sounds like there are two theories exist currently.
1, ASUS using old kernel
2. Tegra chip issue
However, following information seems to challenge these hypothesis..
According to this http://forum.xda-developers.com/show....php?t=1722799, Iconia A700 has very similar result and also Kernel info shows 2.6.39.4+.
So based on this, I think we can hypothesize couple things:
Hypothesis 1: Kernel is the issue
If so, who is actually making this kernel? Is it vendors of tablet or Google? i.e. Samsung doing its own customization which includes the newer Kernel? One thing that does not make sense here (at least to me) is that if you look at http://en.wikipedia.org/wiki/Android_version_history, the Kernel is based on the version of Android i.e. sounds like NOT dependent on the manufacture. However, clearly the picture above shows Iconia A700, which runs Ice Cream Sandwitch is not running on newer kernel as stated by the Wiki... So I am a bit confused here...
Hypothesis 2: Tablet SSD or other common denominator hardware is the issue
Considering the faster Tegra 3 (not by much but some), and better RAM (DDR3 vs. DDR2) and minimal differece between the two systems, my guess is Tegra 3 chip or memory is not the bottle neck, but rather SSD or other common component is the issue.
I know we still have not answered anything here, but at least, this result make a step further to suggest underlying issue is NOT unique to infinity but perhaps wider problem across the android tablet. If so, the chance of it getting fixed would either depend on the Google or individual manufactures to put unexpected amount of resource into this...
What do you all think?
Click to expand...
Click to collapse
Kernels are created by the manufacturer, they're what tell the OS about the hardware and how to use it. Google makes the Operating system, not the kernel. Each kernel is different on each device because each device has different hardware.
So I'm thinking it's just a software issue. I haven't really looked into it, but I haven't heard a ton of complaints about I/O issues from One X users. I think this whole issue is just normal Android stuff that people are blowing out of proportions because it may be a little worse on this right now. I know on my Bionic when a lot of I/O operations are happening, it slows down a bit. Especially with restoring Titanium Backup files and moving big files around. I'm thinking with a little help from Asus and/or indy devs this won't be a big issue.
If you use old software, you always miss out on some features. (Office 95 won't open OpenDocument-formatted documents, AFAIK. ) That being said, it is quite common for SSDs to use a number of controllers that is suboptimal for the number of memory units. That might be a problem.
Given that I perceive the TF700 to be quite a bit snappier with the SuperCharger, I think it's quite possible the issue is in fact caused by an interaction of multiple factors: standard Android policies (not being able to clear out finished-and-not-to-be-used-anytime-soon apps, filling RAM to the brim py preference), suboptimal hardware (crippled I/O controller(s)?) and software (kernel issues).
The second component obviously is out of reach in terms of solutions.The first component could be alleviated partly -- this going head-on with the considerations for earlier and less capable Android systems -- by using a task killer, or optimizing the system (SuperCharger), and the third component could be solved by some of the unbelievably able kernel enthusiasts we have in the XDA ecosystem.
I think we might have a case on hand here for arguing that the current versions of Android are not really optimal for these high-end devices. Scaling issues are not that rare: Windows scales like crap to less capable devices, whereas all *nix systems I've worked with ran beautifully on pretty much archaic systems, and the latter don't gain as much when upgrading hardware, in my experience. From a cynical point of view, you might argue that that's because they ran REALLY well initially anyway.
The policies in force for both scenarios are necessarily different. It might be beneficial to change some of them a little bit. If Google does not institute that by its mighty self, we can at the least take matters in our own hands.
KilerG said:
Kernels are created by the manufacturer, they're what tell the OS about the hardware and how to use it. Google makes the Operating system, not the kernel. Each kernel is different on each device because each device has different hardware.
Click to expand...
Click to collapse
So I guess Wiki is not correct... They often amazes me how much detail there are and quite frequently right. But I guess not this time as Wiki clearly assigns each Android OS version as based on XXX Linux Kernel. But what you say actual make sense as Kernel is like interface between the OS and underlying hardware so my understanding is Kernel just simply provides set of API that meets the OS demand.
But if this is indeed the case and Kernel is the real conundrum then the chance of it being fixed may be much lower, isn't it? Because fixing kernel or upgrading kernel to newer version probably requires extensive amount of work, which I am not sure any company is willing to do when the machines are already sold.
If it was Google, perhaps they could have indeed updated kernel along with Jellybean, but that's out of picture now except of XDA members.
MartyHulskemper said:
I think we might have a case on hand here for arguing that the current versions of Android are not really optimal for these high-end devices. Scaling issues are not that rare: Windows scales like crap to less capable devices, whereas all *nix systems I've worked with ran beautifully on pretty much archaic systems, and the latter don't gain as much when upgrading hardware, in my experience. From a cynical point of view, you might argue that that's because they ran REALLY well initially anyway.
Click to expand...
Click to collapse
Interesting argument there. One hope I have here is that if Nexus 7 succeeds, developers are more willing to put apps specific for tablets. yes. they may be 7 inch... but better than 4 or 5 inch scaling to 10.1 inch. Plus Nexus 7 has very similar spec as Transformer Prime, so supporting of such device seem to make ASUS ahead of packs and in fact, (if they decide to do so) they can easily port those knowledge and resources into Transformer line.
But this IO issue may be one reason why iOS avoids true multitasking. I can never download files or load files in a application in background on my iPAD2. It basically freezes the application where left off i.e. not really multitasking. But because of it, most application won't see any issue what other application is running in background (well actually nothing is running in background..but you know what I mean).
So I am not saying, Android should take this approach but perhaps we may have to take that into consideration and appreciate true multitasking in Android. and when the task becomes large (such as IO issue here), we may simply have to understand some tasks are not for multitask friendly...
Mostly interesting questions but when it comes to nvidia and i/o problems lets blame it on the kernel drivers.
Look at around 48 min mark.
www . youtube . com/watch?feature=player_embedded&v=MShbP3OpASA
Do you think Asus seriously cares about its customers??
HoushaSen said:
So I guess Wiki is not correct... They often amazes me how much detail there are and quite frequently right. But I guess not this time as Wiki clearly assigns each Android OS version as based on XXX Linux Kernel. But what you say actual make sense as Kernel is like interface between the OS and underlying hardware so my understanding is Kernel just simply provides set of API that meets the OS demand.
But if this is indeed the case and Kernel is the real conundrum then the chance of it being fixed may be much lower, isn't it? Because fixing kernel or upgrading kernel to newer version probably requires extensive amount of work, which I am not sure any company is willing to do when the machines are already sold.
If it was Google, perhaps they could have indeed updated kernel along with Jellybean, but that's out of picture now except of XDA members.
Interesting argument there. One hope I have here is that if Nexus 7 succeeds, developers are more willing to put apps specific for tablets. yes. they may be 7 inch... but better than 4 or 5 inch scaling to 10.1 inch. Plus Nexus 7 has very similar spec as Transformer Prime, so supporting of such device seem to make ASUS ahead of packs and in fact, (if they decide to do so) they can easily port those knowledge and resources into Transformer line.
But this IO issue may be one reason why iOS avoids true multitasking. I can never download files or load files in a application in background on my iPAD2. It basically freezes the application where left off i.e. not really multitasking. But because of it, most application won't see any issue what other application is running in background (well actually nothing is running in background..but you know what I mean).
So I am not saying, Android should take this approach but perhaps we may have to take that into consideration and appreciate true multitasking in Android. and when the task becomes large (such as IO issue here), we may simply have to understand some tasks are not for multitask friendly...
Click to expand...
Click to collapse
I hope (and actually expect) that JB will fix a lot of these issues, as it seems to tweak lot of elements that might be in the way of Android really deploying on capable hardware. As far as the Nexus 7 goes, it probably is a really nice device, but I am too much infatuated with the HD screen and the battery/keyboard/dock I currently have to even consider going over.
And yes, maybe we just have to accept that, for the time being, real mobile multitasking (i.e., relatively limitless) may be out of reach. According to your experience with the iPad2, it may show that Apple actually did some real-life testing and came to the same conclusion. That may have been the reason for the much criticised decision to not support multitasking.
Someone mentioned on our Infinity fora here that all the flash memory used in today's tablet is the same chip, so it's not somebody in ASUS or Acer didn't want to spend an extra 10$ per device, it must be something else.
I'm still wondering why I get ca. 10MB/s write and ca. 20MB/s read on internal storage and the other way around with (micro)SD or USB storage.
I think all of us are waiting for JB right now.
Its definitely a kernel issue. If you look in the Prime forum, there's a lot of people raving about the IO performance of Motley's kernel. In the TF300 forum, there's been some mention that CM9 improves the browser performance Once we get a bootloader unlock I'd be shocked if we didnt get a better kernel, if Asus hasn't fixed it already by then.
The old kernel is caused by NVidia because in every Tegra 3 device the kernel is the same: 2.6.... Nexus 7 seems to have 3.1 kernel and hopefully all Tegra 3 devices which get JB will get updated kernel. Old kernel isn't Asus' fault. It is NVidia's fault. Google built ICS with 3.0 kernel and that is why almost all other devices except Tegra 3 devices have Linux kernel version 3.0.
attelaut said:
The old kernel is caused by NVidia because in every Tegra 3 device the kernel is the same: 2.6.... Nexus 7 seems to have 3.1 kernel and hopefully all Tegra 3 devices which get JB will get updated kernel. Old kernel isn't Asus' fault. It is NVidia's fault. Google built ICS with 3.0 kernel and that is why almost all other devices except Tegra 3 devices have Linux kernel version 3.0.
Click to expand...
Click to collapse
Wait correct me if I am wrong. So you are saying, as stated in the Wiki when original Android OS is developed e.g. ICS it used Linux kernel version 3.0.x but then when ASUS or other manufactors using Tegra 3 chip only got access to Kernel 2.6 because it is what Nvida provided? So blame is actually on the Nvidia?
So how did Nexus 7 got new kernel? It uses Tegra 3, ASUS is involved... Is it google that forced NVida to upgrade to newer kernel? In any event, do Kernel usually get updated along with OS update?
One pessimistic comment though.. If we look at Andropolice benchmark Nexus 7 was included there, and their IO result was not much better than Transformer line.
HoushaSen said:
Wait correct me if I am wrong. So you are saying, as stated in the Wiki when original Android OS is developed e.g. ICS it used Linux kernel version 3.0.x but then when ASUS or other manufactors using Tegra 3 chip only got access to Kernel 2.6 because it is what Nvida provided? So blame is actually on the Nvidia?
So how did Nexus 7 got new kernel? It uses Tegra 3, ASUS is involved... Is it google that forced NVida to upgrade to newer kernel? In any event, do Kernel usually get updated along with OS update?
One pessimistic comment though.. If we look at Andropolice benchmark Nexus 7 was included there, and their IO result was not much better than Transformer line.
Click to expand...
Click to collapse
Its entirely possible that Asus decided backporting 3.X's features to a 2.6 kernel would be easier than to do a 3.X kernel from the ground up. Its the route many devices without official ICS have taken to get their community builds and for most of those devices it works just fine.
The Nexus 7 had the advantage of being being handled by Google for software, and as such had no legacy code to be based on. The 700, on the other hand, was close enough to the Prime that Asus probably decided to use the kernel of the later as a base.
This is just speculation though.
jdefi3ebuggdsf32 said:
Mostly interesting questions but when it comes to nvidia and i/o problems lets blame it on the kernel drivers.
Look at around 48 min mark.
www . youtube . com/watch?feature=player_embedded&v=MShbP3OpASA
Do you think Asus seriously cares about its customers??
Click to expand...
Click to collapse
So NVIDIA is the issue then? I like his comment, at the end. "So NVIDIA, F*CK YOU."
Jotokun said:
Its entirely possible that Asus decided backporting 3.X's features to a 2.6 kernel would be easier than to do a 3.X kernel from the ground up. Its the route many devices without official ICS have taken to get their community builds and for most of those devices it works just fine.
The Nexus 7 had the advantage of being being handled by Google for software, and as such had no legacy code to be based on. The 700, on the other hand, was close enough to the Prime that Asus probably decided to use the kernel of the later as a base.
This is just speculation though.
Click to expand...
Click to collapse
But reasonable speculation. I don't think you're far off with these assumptions.
Here's hoping that JB and maybe even some kernel updates and tweaks can at least alleviate the IO issues.
The kernel is a part of OS and can be updated when the OS is updated. I think the kernel is old because Nvidia hadn't lot of time to prepare the kernel to be compatible with new android. Now when nvidia have bee working with google and asus so maybe google have helped nvidia to make new kernel to work with tegra 3. If you want new kernel, find a working custom rom with new kernel and use it.
attelaut said:
The kernel is a part of OS and can be updated when the OS is updated. I think the kernel is old because Nvidia hadn't lot of time to prepare the kernel to be compatible with new android. Now when nvidia have bee working with google and asus so maybe google have helped nvidia to make new kernel to work with tegra 3. If you want new kernel, find a working custom rom with new kernel and use it.
Click to expand...
Click to collapse
Well at this point, we should be waiting for the bootloader to be unlockable. Once we can load custom kernels, the tablet will zooooooooooom.
KilerG said:
Well at this point, we should be waiting for the bootloader to be unlockable. Once we can load custom kernels, the tablet will zooooooooooom.
Click to expand...
Click to collapse
Did custom ROMs solve the I/O problems with the Prime entirely? (never owned one)
d14b0ll0s said:
Did custom ROMs solve the I/O problems with the Prime entirely? (never owned one)
Click to expand...
Click to collapse
According to this thread, it does.
http://forum.xda-developers.com/showthread.php?t=1768406
Jotokun said:
According to this thread, it does.
http://forum.xda-developers.com/showthread.php?t=1768406
Click to expand...
Click to collapse
no it doesnt help entirely. it helps a bit but it does not solve the problems.
for instance the browser still locks up a lot, some ANR messages every now now and then.
only way to get the browser stable is by using browser2ram.
Seems it can be a hard way out of the T3 path.
Have you tried Dolphin browser on your Prime btw? (if I assume correctly that you own one) It helps a lot on the Infinity (Chrome is slightly faster than the stock browser, but is said not to support H/W acceleration, which makes it slower on content-loaded pages)
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
I am sure someone else has already noticed, but HTC One X which had one of top I/O result on Andropolice benchmark has a version with Tegra 3, which still performed well in fact often outperformed its counter part. I could not find which Kernel it uses though. But this may perhaps be one evidence goes against Tegra 3 is the actual issue, but rather something else. And also noting Nexus 7, which used Kernel 3.1 not doing that much better than transformer line also put a flag against Kernel being underlying issue. Could it really be the flash drive itself?
Now to put these in summary, I edited my opening post.
I'm juggling with this idea for a little down the road but when I sit back and think about it, I have a hard time thinking of the benefits other than just for fun. What would be beneficial to you if you're considering dual boot for the tf700. This question is directed at android/ubuntu or android/win8 (if possible) users.
Sent from my ASUS Transformer Pad TF700T using Xparent SkyBlue Tapatalk 2
The main benefit I see is the ability to run Linux applications that are designed for laptops/desktops. Things like full office suites, more robust browsers, photo editors etc. Would add a lot more functionality to the tablet, and also get you all the advantages that a windowed environment would provide for multitasking. You can do all that without dual boot through a chroot, but since you're sharing ram and cpu time with Android its a bit slow and tight.
Would also give you the option to try Win8 if we ever get a port, if it actually delivers on its promises (I highly doubt it) it could save some money initially over buying a tablet actually designed for the OS.
I actually don't see a point in dual booting. There are not much other applications you would be able to run on Linux or win 8 other than stock apps. This is an ARM device which is not compatible with x86/x64 apps.
monkey10120 said:
I actually don't see a point in dual booting. There are not much other applications you would be able to run on Linux or win 8 other than stock apps. This is an ARM device which is not compatible with x86/x64 apps.
Click to expand...
Click to collapse
That really only applies to Win8. Since Linux and most of its software is open source, applications can generally be compiled to run on (or existing packages found for) any CPU type so long as its physically fast enough to handle it. The only catagroy I can see lacking on the Linux side would be heavily optimimized or 3D accelerated games, which there arent very many of in the first place.
Is it theoretically possible for me to install gentoo on my tablet?
Jotokun said:
That really only applies to Win8. Since Linux and most of its software is open source, applications can generally be compiled to run on (or existing packages found for) any CPU type so long as its physically fast enough to handle it. The only catagroy I can see lacking on the Linux side would be heavily optimimized or 3D accelerated games, which there arent very many of in the first place.
Click to expand...
Click to collapse
I thought some Windows 8 devices were to work on Tegra 3 devices? That could mean that over time, Windows 8 could get ported, right?
Not that I care, I -myself- prefer a touch-based OS for a touch-based device.
However, I still believe the are huge possibilities to improve browsing performances on Android.
Actually, being able to dual boot is very nice if you're into flashing different roms (flashaholic). It lets you have a stable go to rom. Then you can have that experimental rom to try out that may not all things thing functional or so forth.
I use Boot Manager on my HTC Evo 4G, which lets you have multiple roms on your phone; it runs them off your SDHC card. I have a stable Sense rom on the phone. Then I have, usually two, other roms on the SDHC card, such as CM7 and CM9.
jdeoxys said:
Is it theoretically possible for me to install gentoo on my tablet?
Click to expand...
Click to collapse
Theoretically, it would be possible. They got Ubuntu on the Prime, so I dont see why other variants of Linux couldn't be made to work.
adelancker said:
I thought some Windows 8 devices were to work on Tegra 3 devices? That could mean that over time, Windows 8 could get ported, right?
Not that I care, I -myself- prefer a touch-based OS for a touch-based device.
However, I still believe the are huge possibilities to improve browsing performances on Android.
Click to expand...
Click to collapse
Not quite... Win8 is only for x86 CPUs. WinRT will be made to run on Tegra 3 and has a chance of getting ported, but it wont run any Win8 desktop software, and is completely locked down iOS style so if you wanted to add any additional software without going through an app store (or period for the Desktop) you'll have to root/jailbreak.
lovekeiiy said:
Actually, being able to dual boot is very nice if you're into flashing different roms (flashaholic). It lets you have a stable go to rom. Then you can have that experimental rom to try out that may not all things thing functional or so forth.
I use Boot Manager on my HTC Evo 4G, which lets you have multiple roms on your phone; it runs them off your SDHC card. I have a stable Sense rom on the phone. Then I have, usually two, other roms on the SDHC card, such as CM7 and CM9.
Click to expand...
Click to collapse
This right here is the only reason I would ever dual boot. I love having a unstable cool new JB ROM but hate losing my daily driver ROM.
I'd love to dual boot (or emulate). Using Ubuntu/Win8 would massively enhance my productivity.
I've got a rooted P5110 running the latest Clockwork Recovery and Cyanogen Mod 10.1 and by few apps. I'm running this rom in an attempt to get the Tab2 to be smooth and glitch free. No matter what rom I try I get some level of stuttering and glitchyness even on very mild use such as simple browsing with a couple of tabs open. I've grown tired of trying every possible rom to solve this so I've come to thinking that it is just not possible, no matter what Rom is used, to get the Tab 2 buttery smooth (like an iPad).
My question is to those really up to speed on Roms/Kernels/Modding and it is whether it is genuinely possible (Android/Apple rivalry aside) to make the Tab 2 super-glitch-free like an iPad? I.e. is the Tab2 stuttering a hardware/spec issue that simply can't be overcome by ultra-clever programming or modding?
I'd appreciate honesty on this because I can still (reluctantly) send the Tab 2 back and get an iPad in its place. I don't want to do this but I cannot live with its stuttering anymore but will stick with it if it's easily and genuinely fixable.
Android is a different beast, the software is written for a few hundred devices, where as ipad apps are written for three devices...you well never get that with android, that said I guess I'm not as picky as you because I feel that cm10.1 is smooth with stock or black hawk kernel..
Sent from my GT-P3110 using xda app-developers app
mrkhigh said:
Android is a different beast, the software is written for a few hundred devices, where as ipad apps are written for three devices...
Click to expand...
Click to collapse
Totally get this but my Android phone (Motorola RAZR I) doesn't stutter at all, no matter what I throw at it. It's got a faster processor (Intel chip) but still it shows that Android doesn't need to stutter. As I understand it the Asus Transformer Prime tablet doesn't stutter at all (but does have other issues) so this brings me back to thinking that the Tab 2 is simply well and unforgivably under spec'ed.
If you want a solid functioning tablet for basic usage without the need for modifications, the ipad is probably best to meet your requirements.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
If you really hate lag, there are a few things you can do.
1. If you use SwiftKey, don't. It produces a fair bit of lag when typing.
2. Don't use a live wallpaper.
3. Use a custom homescreen like Nova Launcher.
4. Use Chrome.
GrandMasterPlank said:
I've got a rooted P5110 running the latest Clockwork Recovery and Cyanogen Mod 10.1 and by few apps. I'm running this rom in an attempt to get the Tab2 to be smooth and glitch free. No matter what rom I try I get some level of stuttering and glitchyness even on very mild use such as simple browsing with a couple of tabs open. I've grown tired of trying every possible rom to solve this so I've come to thinking that it is just not possible, no matter what Rom is used, to get the Tab 2 buttery smooth (like an iPad).
My question is to those really up to speed on Roms/Kernels/Modding and it is whether it is genuinely possible (Android/Apple rivalry aside) to make the Tab 2 super-glitch-free like an iPad? I.e. is the Tab2 stuttering a hardware/spec issue that simply can't be overcome by ultra-clever programming or modding?
I'd appreciate honesty on this because I can still (reluctantly) send the Tab 2 back and get an iPad in its place. I don't want to do this but I cannot live with its stuttering anymore but will stick with it if it's easily and genuinely fixable.
Click to expand...
Click to collapse
The main reason is because apple has loads more years of experience when it comes to software! But also the bloatware that samsung installed doesnt help, ios hibernates the operating sistem when u play a game for example! So all of the ram and cpu power goes towards the game! Where as android the game runs on the top of android. Also there are no home screen of widgets less animations! Should I go on? Honestly android will never run like ios!! Android may get better but so will apple so android will always be behind! Thats why the iphone can run games lag free etc and also why the iphone 5 has less cores and that then the s3 or s4! Everyone says wow look at my s3 4 cores your iphoen 5 only has 2 mine is better! That is wrong! Iphone 5 doesnt need 4 cores! Or 2 gb of ram... etc. So yeah If you don't like lag buy a really expensive device like the note 2 or just buy an ipad!
I hope there were no errors it that!
Press thanks if I helped!
Sent from my galaxy tab 2 jelly bean using Xda Premium
You know, i'm supposed to love all android things, i love my smartphone, but with tablets, i have an xoom that traumatized me because issues, i don't buy any other tablet because that, i don't know if it's only with me or i'm doing something wrong.
The true is that the xoom have a problem, a problem specially with the screen, i don't know, it's not lag, looks like it is but i think is not, for my knowledge on the subject it's with screen refresh frequency that it's not high, is that why you see pixelated movement of screen objects when you do a slowly fast swipe.
It's like the image of icons don't move in the same time and broke the transition, i want to know if that is a hardware issue, is that why xoom have that problem, or it's because Tegra 2 can't handle xoom? I don't want flame, i love my xoom, really but i want to resolve that problem, it's annoying me, i have an iPad 1 with single core 1ghz, xoom is dual core 1ghz with 1 gb, my iPad have 256 and you don't have that problem. Can someone help or explain that for me?
Sorry, my English, i'm Japanese.
I don't have this problem with mine, maybe your ROM is too cluttered. The info you passed is not enough to specify your problem, can you provide some more system info ?
XxLordxX said:
I don't have this problem with mine, maybe your ROM is too cluttered. The info you passed is not enough to specify your problem, can you provide some more system info ?
Click to expand...
Click to collapse
I'm Running Stock 4.0.4 Icecream Sandwich, all stock, i already use CM10.1 and EOS 4.2.2. What i want to say is that my xoom is not fancy on transition and all xoom that i saw is that way too, i have a Galaxy SIII, i know it's a quad-core actually processor but i'm still compare, i haven't lag, it's like the transition it's not fancy, it's smooth but not fancy, it's like play video game on LCD/LED TV, LED have problems with refresh response that make HDMI Video Games not smooth, that's why i said about screen refreshs.
Also i got an Galaxy Tab 2 10.1 in my hands on Store and compared with my xoom display, i will say again, it's not lag or slight lag, it's about the things moving on the screen, you see the trail if i can call it in that way.
I will make a video to show you what i'm talking about.
iSaoHatake said:
I'm Running Stock 4.0.4 Icecream Sandwich, all stock, i already use CM10.1 and EOS 4.2.2. What i want to say is that my xoom is not fancy on transition and all xoom that i saw is that way too, i have a Galaxy SIII, i know it's a quad-core actually processor but i'm still compare, i haven't lag, it's like the transition it's not fancy, it's smooth but not fancy, it's like play video game on LCD/LED TV, LED have problems with refresh response that make HDMI Video Games not smooth, that's why i said about screen refreshs.
Also i got an Galaxy Tab 2 10.1 in my hands on Store and compared with my xoom display, i will say again, it's not lag or slight lag, it's about the things moving on the screen, you se the trail if i can call it in that way.
Click to expand...
Click to collapse
Hum... But you mean only in the launcher you find the "lag"? The stock launcher has some problems, I'm running EOS 4, with Nova launcher (one screen) and my Xoom is blazing fast, it's not a Galaxy Tab 2 10.1 neither a S3, but it's working well. Try changing the launcher, installing the ROM again and changing the launcher. Mine is quite fast, however I have a friend whose isn't as fast as mine because of the settings
"This Story Ends Where It Began" - Octavarium (Dream Theater)
XxLordxX said:
Hum... But you mean only in the launcher you find the "lag"? The stock launcher has some problems, I'm running EOS 4, with Nova launcher (one screen) and my Xoom is blazing fast, it's not a Galaxy Tab 2 10.1 neither a S3, but it's working well. Try changing the launcher, installing the ROM again and changing the launcher. Mine is quite fast, however I have a friend whose isn't as fast as mine because of the settings
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Click to expand...
Click to collapse
As i said, yeah i know, stock launcher have some lag, but it's not about lag, as an example, what a video with a lot of fast footage, if you see on xoom, on PC and on a OLED TV like i have here, TV is the best way followed by PC, but on xoom i have headache seeing fast movements, you see the trace you know, it's not like instant, as i said i will make a video.
What's your ROM?
Okay, I will wait for your video to help I understand more your problem . I'm using EOS 4 on my Xoom (MZ601)
Sent from my MZ608 using xda app-developers app
XxLordxX said:
Okay, I will wait for your video to help I understand more your problem . I'm using EOS 4 on my Xoom (MZ601)
Sent from my MZ608 using xda app-developers app
Click to expand...
Click to collapse
So a long time ago, i just got my camera today! AAAAAAAAAnnnnnndddd.... here is the vídeo :silly::silly::silly::silly::silly:
It's not a review and not so long, it just show the xoom screen besides others. I advise you to watch on youtube in 720p!
You have a good pronunciation ^^.
I have an idea of how to test if it's a hardware problem. Do you have a HDMI cable? If so, try plugging on your TV and see if the trail is still there, then we can have an idea .
XxLordxX said:
You have a good pronunciation ^^.
I have an idea of how to test if it's a hardware problem. Do you have a HDMI cable? If so, try plugging on your TV and see if the trail is still there, then we can have an idea .
Click to expand...
Click to collapse
Oh really, really thanks, when i'm nervous i say a few words wrong (exchanging letters for anothers just like all people do when nervous) XD due to my shy profile, but really thanks, i'm doing videos in english and writing in english just to learn more and more. :victory:
So, about HDMI, yes i have it, but i need to search it, i will try to find and get that working to see, really thanks for support and your attention.
The bad news, if it is hardware, i'm lost due to the warranty period which is over hehe, but thanks again pal! :highfive:
I have 601 32GB 3G and I am very satisfied himself with the new rom 4.2.2
rep
i don't have the same problem like yours. maybe because of your hardware
Spirit_Guru said:
I have 601 32GB 3G and I am very satisfied himself with the new rom 4.2.2
Click to expand...
Click to collapse
You are using 4.2.2 from CM?
The real problem with the Xoom is that tegra 2 is one of the worst Soc's ever made ..
In Benchmarks tegra 2 is close to OMAP4430 , but in real world most of OMAP4430 run perfectly smooth while TEGRA 2 devices can't even run the launcher smooth .
Sent from my ME865 using xda app-developers app
I have had a combination of Custom Roms and Software that brought the Xoom to a crawl. Currently using latest CM10.1 Nightly, Overclocked with Unified Gapps. A lean amount of Software. I have to say it runs well right now. I do wipe the system fairly often. I try not to dirty flash very often.
Sent from my Nexus 4 using XDA Premium HD app
logitechor said:
I have had a combination of Custom Roms and Software that brought the Xoom to a crawl. Currently using latest CM10.1 Nightly, Overclocked with Unified Gapps. A lean amount of Software. I have to say it runs well right now. I do wipe the system fairly often. I try not to dirty flash very often.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
How that you cleaned everything? I hate the /0 partition that transform my SD card into internal memory.
You said your warranty was over, did you buy it new? and experiecning this lattely only? If so, its probably not the hardware, just try out different rom, plus maybe overclock it (as warranty is over anyway)
Hardware issue in my xoom was constant reboots and hangs, so after couple of weeks (yee weeks, I thought it was due to honeycomb) I sent coom to motorola and they fixed it on warranty...
Any way - good luck!