Related
So fennec went alpha this week and wanted to know if anyone tried it yet?I've tried to use it but it keeps crashing, has anyone had this issue?
As much as I like firefox, I'll not get this until they trim this chubby app down some. 31mb?
Sent from my CDMA Hero. I got me some hot froyo on hero action here!
couldnt get this app to work either and the size is crazy if u want a different browser try OPERA thats pretty good if ur looking for some fast net or just wait for a better realese
WOW mY English is Atrocious
Yea I like opera but don't like that you can't really download stuff from it. But yea wanted to try out fennec to see how it runs but it's a no go so kinda disappointment.....eh
Actually, Fennec's quite a few good ideas, expecially for Firefox users. I mean, it can syncs your open tabs (the ones you left open at home before leaving!), bookmarks, search history and site access infos (so you won't type those old pass/user you can't even remember).
Moreover, you get plugins... not a big amount of them available, but this could just a matter of time if this catches up; and tab management is on par with Android browser's.
Main downside is related to page render speed and program open, they just fail before Android stock browser (which I think is quite awesome, I have to admit it, in terms of performances and compatibility).
Definitively still a "to keep an eye on" project, though.
just installed the app, but it wont even open
Junk
I find it unbelievable that this has even been considered for a release to anyone!
After several attempts to install, I finally got this bloated mess to work, slowly and with no features that haven't been done better elsewhere.
I was truely expecting more, Firefox and Thunderbird have become bad enough lately, with this rubbish Mozilla have scored 3 out of three.
Haven't tried this alpha yet, but I played around with an older Version. I also tried the WinMo version and I can tell you that Fennec on Android is much better than the WinMo version. On my HD2(running Froyo) it installed without problems and it didn't crash. But because the UI had no priority over the webpage rendering it wasn't really usable. But I think I read somewhere that in this alpha the UI has priority, so when I can I will give it a try again. But the only reason for using Fennec are the sync features.
You people should READ THE SYSTEM REQUIREMENTS before commenting on whether things are good or not. It CLEARLY states that MSM720xA based phones are NOT COMPATIBLE. Regarding the one who managed to partially get it working.... I don't believe you.
Specifically, the program is built for ARMv7 instruction set. YOUR PHONE SUPPORTS UP TO ARMv6 instruction set ONLY.
To put this very simply.... the program is NOT COMPATIBLE [yet].
lbcoder said:
You people should READ THE SYSTEM REQUIREMENTS before commenting on whether things are good or not. It CLEARLY states that MSM720xA based phones are NOT COMPATIBLE. Regarding the one who managed to partially get it working.... I don't believe you.
Specifically, the program is built for ARMv7 instruction set. YOUR PHONE SUPPORTS UP TO ARMv6 instruction set ONLY.
To put this very simply.... the program is NOT COMPATIBLE [yet].
Click to expand...
Click to collapse
There are nightly builds, which work on Armv6.
I have it running, on a HTC Magic.
http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-android-r7-nothumb/
The main deal breakers are that it takes forever to load and that the GUI doesn't scale and all the buttons are too big.
Finally:
Coming from my standpoint, that really didn't call for caps, as what you believed and clearly read into the announcement didn't eventuate anyway.
I am positively glad about that, I hope you are too xD. So far Armv6 isn't going to be left behind (all too far).
20100905 fennec works on hd2- arm 7
Hi,
Fennec seems to work on HD2 (an ARM 7 device).
Not sure I like the rendering of pages like xda-developers.com - but it works.
Seems like it has potential.
newowner
Definitely has a potencial, but it's too slow and so not usable for normal android experience...waiting for beta release
works on the vibrant but very very laggy. UI is ugly but simple to use.
Is there anything I should know about how a rooted Nook Color acts compared to something that's meant to be a tablet (e.g. the Galaxy Tab) that could influence whether I want one? For example,
This thread has workarounds for a bunch of quirks and problems with the NC. Is it common to need to workaround these and other B&N ROM issues?
I've seem mention of 'porting' apps to the Nook Color. Does this mean I have to do more work to get apps from the market than just hitting 'install'? Do some apps not work on the Nook Color?
It looks like B&N pushes over-the-air software updates to the NC that return it to a stock ROM. Is this easy to prevent? When they push their Q1 update, will it (probably) be easy to apply the update and then get all of my data/settings back, or are updates a pain that I have to put off applying until I have time to reconfigure everything?
Is there anything else I should know?
Well I am not hijacking this forum I just ordered a Nook Color I would cetrainly love to see these questions answered but could I also add a few of my own ?
I am in Europe what kind of usability can I expect from the device, will I be able to register it and what about books.
Also I 've heard there are some touch issues, whats up with that ..? is it true .. any solutions..?
I am following the BT thread and all looks great but what about the USB would we be able at some point to connect ext HDDrives or Webcams ..
Lastly I understand it will only play .mp4 movies anyway around that .......?
I will try to give you a couple answers based on my own experiences, though im no expert when it comes to rooting.
Yes there are some quirks with the NC that you wouldn't have to deal with on a regular android tablet. The biggest one is the lack of hardware buttons. There are several software solutions for this, the most effective and stable of which has been "button savior" which you can get in the market.
Some apps font render correctly because of the screen resolution/dpi of the NC. Some of that can be fixed by using an LCD density changing app or altering the setting manually.
You shouldn't have to port apps to run on the NC, but don't be surprised if some apps don't show up in the market. Most stuff works fine though.
As far as i can tell you wont get BN ota updates unless you're on a BN store wifi network. I've been rooted for weeks and i've never seen the 1.01 update pop up. I figure im waiting for the bigger update before i bother reverting to stock and restoring all my apps.
Ill post more stuff as it comes to mind!
posted from my nook color using the official xda app
There are certainly quirks, such as the hardware buttons issue mentioned above. And some apps don't work now, but I imagine other tablets would have similar issues. as android tablets grow in popularity we can expect more compatible apps
spiffytech said:
Is there anything I should know about how a rooted Nook Color acts compared to something that's meant to be a tablet (e.g. the Galaxy Tab) that could influence whether I want one? For example,
This thread has workarounds for a bunch of quirks and problems with the NC. Is it common to need to workaround these and other B&N ROM issues?
Click to expand...
Click to collapse
The B&N ROM does not contain some things that were completely not needed for the device as it was designed, so yes there are workarounds in that thread and on the wiki here: http://nookdevs.com/NookColor_Issues
spiffytech said:
I've seem mention of 'porting' apps to the Nook Color. Does this mean I have to do more work to get apps from the market than just hitting 'install'? Do some apps not work on the Nook Color?
Click to expand...
Click to collapse
Never heard anything of "porting" apps, only reason would be screen resolution of tablets vs phones. Some apps don't behave nicely on the higher res, either they are in the center of the screen, stretched out and ugly, or simply draw really badly. Most fall into the first two categories.
spiffytech said:
It looks like B&N pushes over-the-air software updates to the NC that return it to a stock ROM. Is this easy to prevent? When they push their Q1 update, will it (probably) be easy to apply the update and then get all of my data/settings back, or are updates a pain that I have to put off applying until I have time to reconfigure everything?
Click to expand...
Click to collapse
Yes, your device will query for OTAs and so far nobody has figured out how to safely disable them. Update to 1.0.1 first, then noot it. And when a 1.0.2 or 1.1.0 comes out, expect to do it again. Until someone comes out with a real way to disable the OTAs or a full custom ROM is made.
pavlos46 said:
Also I 've heard there are some touch issues, whats up with that ..? is it true .. any solutions..?
Click to expand...
Click to collapse
It generally happens only when plugged in, and almost always unplugging it and turning off the screen and turning it back on the problem goes away. Some folks say it happens more if the screen is dirty, although in my experience with capacitive screens this is not the case.
pavlos46 said:
I am following the BT thread and all looks great but what about the USB would we be able at some point to connect ext HDDrives or Webcams ..
Click to expand...
Click to collapse
Highly unlikely, but there are ways to do USB Host drivers on Android phones, so it's possible in the future.
pavlos46 said:
Lastly I understand it will only play .mp4 movies anyway around that .......?
[/LIST]
Click to expand...
Click to collapse
Sure, use something like RockPlayer.
Other things to note...
Games run fairly well on Nook Color. I've been using Dungeon Defenders (framerate not the best), Antigen, Angry Birds, Fuzzies and Nesoid. They all work pretty well except for poor framerates with Dungeon Defenders.
You'll definately need Button Savior. The LCDDensity app is also good to have and tinker with. You'll want to get NookColor Tools on there as well to change keyboards. Root Explorer also.
It runs pretty much any app that I can run on my Droid.
Dolphin-Mini works great on the Nook Color.
There are some issues with buttons at the screen edges, like the Android Marketplace search icon or tab switching in Dolphin. Adjusting LCD Density with the LCDDensity app will cure that problem. Otherwise you will have to figure out how to tap on the edges for it to register. Mine only does this at the top edge and not on the sides or bottom.
Overall, a great device. Clockwork is well on it's way to being finished. And there are now a few folks jumping on the bandwagon to create custom roms.
Rockplayer will play other video types, but wont use hw acceleration and will be choppy. Best to convert to mp4 instead.
In the end i think this tablet is for those who actually enjoy tinkering and tweaking.
Sent from my Nookcolor
Seems like I say this constantly, but in my opinion you do not need Button Savior, Softkeys included in the Auto Nooter script for 1.0.0 or 1.0.1 works great.
markiejones said:
In the end i think this tablet is for those who actually enjoy tinkering and tweaking.
Click to expand...
Click to collapse
Exactly. I've enjoyed "fixing" the Nook. But this process could be annoying to many people. Those people would be much happier with an ipad.
khaytsus said:
Seems like I say this constantly, but in my opinion you do not need Button Savior, Softkeys included in the Auto Nooter script for 1.0.0 or 1.0.1 works great.
Click to expand...
Click to collapse
I agree. When you set softkeys "just so", it's a near-ideal key replacement. The default setup is what throws people off, with the little arrow-guy getting in the way and some confusion regarding the "n" key.
Mine is invisible except when I single tap the "n" key -a double tap gets me "home". That's perfect, and not at all in the way.
Can someone with the Nookie Rom download "Multitouch Visual Test" and tell me how many fingers you can get to work? I've seen that the stock-ish nc can only do 2 but I'm curious if Nookie Rom allows for anymore.
Thanks
Just checked with MultiTouch Visualizer 2, and it's a no-go. Still only shows two multitouch points in Froyo.
dang, thanks for checking
In what apps do you use 3 or more touch points?
was hoping to use it as a development platform for a strategy game for one of my classes, was hoping to get 4 touches so two people could use it at the same time
Anyone have any idea if there is a way around this or should I just give it a rest?
I've seen some comparison made in threads, but most are partial, and while I've looked into Froyo quite a bit, and even made a hack at it, I haven't come to fully understand why I should. So I thought it might be helpful to have a Pro/Con differentiation between the two; why did you go through the effort to Froyo? Why didn't you? I know some have gone Froyo and then back to Eclair. I'll try to edit this post into a list once we have some good comparisons thrown out here.
Alright, after playing with the latest Froyo and looking at this thread so far, the tentative list for newbz0rz to consider is here.
The List:
Froyo 6.6
+Flash (!)
+Higher Benchmark scores, possibly faster in certain ways
+Higher compatibility with certain apps
+Potentially more configurable
+Cut and paste
+JIT compiler (potentially increases speed)
+Launchers behave properly (i.e. add shortcuts)
+Text-to-Speech
-Choppy Flash (!)
-More effort and time (lots more) to setup equivalently capable features
-Higher risk of Nook destruction (although still low)
-Higher risk of lots of work rescuing Nook from the grave/brickyard
-No Nook Color features (i.e. B&N apps, in store access, reader, magazines, etc)
-Buggy-ish sometimes (Unstable) :-(
*-Different users seem to report very different experiences; thus, we'll just call Froyo Inconsistent
-Ignores internal 5GB storage
-Ugly notification bar mis-sizing
1.1.0 Rooted
+Stability (Consistency in a stable experience, compared to Froyo)
+Some claim smoother overall
+B&N "experience" (FWIW)
+magazines, built-in reader for those who prefer it (hint: Aldiko is better)
+Status/Notification bar at bottom with back/menu keys
-Ye Olde Android 2.1
*-No JIT
*-No Flash
-Incompatible with shiny new 2.2+ apps (not very many of those, but still)
-Possibly slower, benchmarks lower
-Dialogs don't display correctly due to B&N system configuration
-Many alternative keyboards don't work properly
-No Cut and Paste
*Evernote was a dealbreaker for me, oddly enough. I use it all the time. Also, 6.6 Froyo broke my ADB somehow, and was a huge pain for very little gain. Gotta love Nandroid. 1.1.0 rooted does 95% of what I want, while Froyo does the 5% it can't do and breaks another 10% of what already worked. But that's just me. I can wait for CM7/ a more stable Froyo before I get flash. Honestly, what flash content do I want to watch on my tablet that I cant use my netbook/desktop for? I'll stop asking questions I don't want the answer to.
The biggest plus for froyo for me was flash content. The negative is Thai it is not as smooth as 1.1.
haven't tried 1.1 yet, but froyo+launcherPro+dolphin browser is as smooth as a phone. also, plus flash content
It really comes down to this:
Rooted 1.1.0 is for people who want to have the basic(older, no flash) tablet expirence, on a platorm which runs well and requires little to no cmd-line/linux/etc. knowledge.
Rooted 1.1.0 OC'ed to .950/1.0/1.1ghz only requires a couple hours of development forum reading, a little bravery, and a NC that can handle it.
Nookie Froyo 6.6 OC'ed to 1.0/1.1ghz ON SD CARD again, only forces you to read the respective threads(twice) and have an available micro SD card(at least class-4 4gb). This is a good method to start out with because if you mess it up, just reflash the SD card.
Nookie Froyo 6.6 OC'ed 1.1ghz INSTALLED TO EMMC is not over-the-top hard. It just requires a lot of dedicated hours understanding what exactly the flash images are doing to your device. Being comforable while working in cmd-prompt/linux/android-system is a must. Acceptance of the fact that, doing so *can* break your $250 toy.
knaries2000 said:
The biggest plus for froyo for me was flash content. The negative is Thai it is not as smooth as 1.1.
Click to expand...
Click to collapse
agreed Flash was upsetting otherwise i would of kept it as 1.1 right now i dual boot w/ 66 and 1.1 but using froyo i really only go back to read my magazine subscriptions, and i like the back and menu softkeys setup on the bottom in teh 1.1 not so much in froyo
woot1524 said:
It really comes down to this:
Nookie Froyo 6.6 OC'ed 1.1ghz INSTALLED TO EMMC is not over-the-top hard. It just requires a lot of dedicated hours understanding what exactly the flash images are doing to your device. Being comforable while working in cmd-prompt/linux/android-system is a must. Acceptance of the fact that, doing so *can* break your $250 toy.
Click to expand...
Click to collapse
I've yet to see anyone break their $250 doing so. (In fact I don't see how it could break it). Also it doesn't require being fluent in any of those. Can you copy and paste? Okay well then youre set. Also, with people posting builds coming preinstalled with needed apps makes even using the command prompt almost uneeded (the only thing that needs to be pushed is the market).
The real downside to froyo is the lack of the B&N soft-keys on the bottom, meaning there isn't always a back and menu button on screen.
To Sum:
Froyo = Lack of softkeys permanetly there
Eclair = Slower, Lack of Flash
I tried NF for a little bit. I still have the card sitting somewhere.
For some reason, I don't feel the need to get Froyo on here until I can easily flash it like any other Android device.
I seem to remember there were certain compatibility issues along with slower benchmark results on Froyo. Is this no longer true?
vapor63 said:
I seem to remember there were certain compatibility issues along with slower benchmark results on Froyo. Is this no longer true?
Click to expand...
Click to collapse
Not that I know of. Froyo Quadrant scores are a full 400 or so points above eclair.
I've got rooted/OC'd 1.1Ghz 1.1 on mine.
I don't feel the need to go to Froyo.
Once Honeycomb is perfected, though, I am SOOOOOOOO there.
MattJ951 said:
I've yet to see anyone break their $250 doing so. (In fact I don't see how it could break it). Also it doesn't require being fluent in any of those. Can you copy and paste? Okay well then youre set. Also, with people posting builds coming preinstalled with needed apps makes even using the command prompt almost uneeded (the only thing that needs to be pushed is the market).
The real downside to froyo is the lack of the B&N soft-keys on the bottom, meaning there isn't always a back and menu button on screen.
To Sum:
Froyo = Lack of softkeys permanetly there
Eclair = Slower, Lack of Flash
Click to expand...
Click to collapse
True, the chances of bricking the nook color are remote. But as you can see from the dev threads, even they have warnings. Because the odds dramaticaly increase when one starts messing with system and boot mounts, or over-clocking the hardware.
The reason why I stressed the understanding of what exactly your doing, when you flash the emmc or uImage, is there are many conflicting/confusing instructions involved If you take things verbatum from threads. I just don't think it's something a novice user should try at the moment. Especialy with the loss of the abilty to do a CWM recovery(I know about the sd images and swaping the cards out to do a backup, others don't, nor have more than one sd card)
Froyo does infact have Back and Menu buttons in the status bar.
you just need to push a couple files found in this thread: http://forum.xda-developers.com/showthread.php?t=932631
The real problem with nookie Froyo is that it's still not a daily driver. It's buggy(to an extent), it's always being updated(annoying, but part of the fun), and frankly 1.1.0 just runs better.
I am surprised that nobody bothered to mention that with Froyo, currently, you lose the ability to veiw kids picture books, newspapers, and magazines. If you care about any of that stuff, you have to stay with 1.1.0
waiting for guys at Cyanogen to release the nightlies for NC
i tried froyo last night since you can now flash through recovery.
it was a painless install but then i had to get adb running to install gapps and sdcard fix.
after running it for awhile it isn't bad but still not as smooth as 2.1. not sure why people are posting that its faster as it is not. it's little more choppy overall and has hardware acceleration problems when playing movies. as some have mentioned it is annoying not having the navigation buttons without the nook bottom bar.
i am also just waiting for cm7 and i'll say goodbye to eclair forever. it was a breeze restoring back to stock through recovery and will probably try the next update of froyo now that I know what I'm doing.
jblues1969 said:
I've got rooted/OC'd 1.1Ghz 1.1 on mine.
I don't feel the need to go to Froyo.
Once Honeycomb is perfected, though, I am SOOOOOOOO there.
Click to expand...
Click to collapse
This is my exact standpoint.
If a Honeycomb (That isn't just the SDK preview) is made for the NC, I will be downloading it.
So we've got a working list running for reference; I'm sure some people have more to add? This kind of thing would have saved me a lot of time a few months ago, let alone now with the increase in crazy options.
Thanks for this list, its awesome. It helps address the questions.
I am ofcourse going to try froyo since its so easy to do so but I wanted to help decide what was going to be my daily driver, etc.
CM7 is built on 2.3 AOSP right? I am excited to read above that nightlies are coming soon?!?!?
woot1524 said:
True, the chances of bricking the nook color are remote. But as you can see from the dev threads, even they have warnings.
Click to expand...
Click to collapse
The warning are there as a just in case. These roms won't short out any circuits (short of the Overclocking one) and are just standard warnings. Since the NC boots to the SD card first it shouldn't be bricked. In fact if you wish to claim it can brick it then I can equally make a claim nooter will.
woot1524 said:
(I know about the sd images and swaping the cards out to do a backup, others don't, nor have more than one sd card)
Click to expand...
Click to collapse
You don't need more than one sd card. I only have one and have successfully recovered when I was trying to do some edits myself.
woot1524 said:
Froyo does infact have Back and Menu buttons in the status bar.
you just need to push a couple files found in this thread: http://forum.xda-developers.com/showthread.php?t=932631
Click to expand...
Click to collapse
That is actually glitchy and if you read the developer even stated it himself later on. He said instead of releasing a custom ROM to fix the problems he'll just release the source code in case anyone really wants them
woot1524 said:
The real problem with nookie Froyo is that it's still not a daily driver. It's buggy(to an extent), it's always being updated(annoying, but part of the fun), and frankly 1.1.0 just runs better.
Click to expand...
Click to collapse
Eclair is buggy to an extent as well and on the issue of which runs better we'll have to agree to disagree since we can only have it based on opinion. Froyo has higher quadrant scores, and runs much smoother for me. As for compatability I'll test evernote later, but I dont know of any apps I've tested that don't work in froyo but do in eclair, while theres quite a few 2.2 exclusive apps that obviously won't work in eclair. But for those who can't get apps to work in 2.2 that did in 2.1 might be worth more than those 2.2 exclusives
In the end I would suggest just dual-booting Froyo and Eclair. Theres a simple download over the developers forum's that allows this. You just put it on an sd card, then type one line on your nook and you can test both of them and decide for yourself, while always having one for backup
How is the 1.1 g?
I feel quite the opposite, I think the B&N 2.1 experience is horrible.
B&N 2.1
- Dialogs don't display right due to B&N system configuration
- Keyboards don't work properly and if the keyboard does not have the settings in the UI there is now way to configure it due to B&N config
- No Cut and Paste. The work around are horrible.
- Default B&N Apps are horrible by far the worst apps in every field.
- System settings are non standard and accessing app configurations is very difficult.
- No JIT compiler causes apps to run slower.
- Launchers do not work properly because of missing
- No Text-to-speech.
- Random reboots multiple times a day.
- Games are sluggish, basic games are just fine.
Froyo 2.2 (0.5.8)
+ JIT compiler
+ Can get the nook 4 android app (which I think is better than their stock reader)
+ Cut-n-paste
+ Text-to-speech
+ More Stable( reboots on me twice a week)
+ Default Android back end so configuring keyboard apps and other apps is possible.
+ Launchers behave properly.
+ Access to more Market apps.
+ Game experience is much smoother(thanks to the JIT).
What bugs do you see on the Froyo that you don't see on the Stock nook. If anything I've seen more issues running stock nook than foryo?
What is the advantage of using android 3.0 have over 2.2. and 2.3?
Install all three and really see no difference beside the slight UI changes.
evilPERSOn,
I had not yet loaded HC, so my advice is pure speculation. HC has an entirely different interface which acknowledges the fact that a tablet is in essence a tablet and not an oversized phone. So, as such, it works a bit more like a computer with. The speed and streamlined interface of a tablet. As I write this I really wonder why I have not cobbled it up. Well, it is only a matter of time.
Have fun
~Leko
evilPERSOn2009 said:
What is the advantage of using android 3.0 have over 2.2. and 2.3?
Install all three and really see no difference beside the slight UI changes.
Click to expand...
Click to collapse
well for starters this should be in general not development
second HC isnt just a slight UI change, it was MADE for tablets so if you want your tablet to be a giant itouch running android than install 2.2/2.3 but if you want a tablet you should install 3.0
^My bad. I had two tabs open. General and Development. Must have started thread on the wrong location.
1. HC uses GPU interface rendering.
2. HC is meant for a system like a nook with few buttons (good for us)
3.But HC's source is not in the open (bad for us).
poofyhairguy said:
1. HC uses GPU interface rendering.
2. HC is meant for a system like a nook with few buttons (good for us)
3.But HC's source is not in the open (bad for us).
Click to expand...
Click to collapse
Hopefully the source will be released soon!
For me i thought i would try hc on the sd card and just go back to froyo. I was hooked. I used it for two days on a class 2 card then i flashed, and ive tried to go back to froyo and get flash but i cant. The UI is just perfect, the live app switcher key is wonderful and so great to use, probably my favorite feature. Not to mention i love that the task bar is on the bottom, reminds me of windows and keeps the clock and keys out of my face. Honestly i hate the top notification bar on other versions, ive always hidden it on my droid. Being on the bottom is so nice and out of the way.
Its got its downsides, but give it 2 months.. apps galore, source files..... it will be really good to run.
Edit: not to mention, ive never lost data like on my droid while switching apps. Ive come back to apps ive had open for over 24hrs and its still in the same state
Sent from one of those missing Droids
altimax98 said:
The UI is just perfect, the live app switcher key is wonderful and so great to use, probably my favorite feature.
Click to expand...
Click to collapse
i'm using the samuelhaff's eMMC HC and i noticed that i can't scroll the app switcher, so i don't have access to all my previously run apps. is this normal?
loving HC, so far. the fact that it's designed for no hard buttons is just awesome.
i don't think the app switcher even scrolls on the xoom yet.
I have only played with HC breifly. But from what i know about it these are the following reasons to use it.
1. Market. Honeycomb is the first android os that will support having the google market. This provides a few things. Any of us who have played with Ipods and ipads will know that there are specific apps built for ipad. Now that Android 3.0 is built for tablet form factor, and officially supports the market. We will now see Tablet applicatons that provide higher resolutions, or new features. These apps will be built around the 3.0 os, and may not work on older operating systems.
2. Built for tablets. Everything we have had up untill this has been a phone operating systme built for a 3" screen ported to something with a 7-10" screen. The os is clearly built for phones there are things in there that just dont work right, or should not be there, but are there, on a fundimental level in the operating system. By adding native support for larger screens, and removing the phone items, it provides for a cleaner higher performance interface.
3. Interface enhancements. The UI has been built to support the larger form factor. This will provide easier navigation as well as soft keys as mentioned above, since alot of tablets are just missing physical buttons.
Unfortunatly the OS has not been released to the public. My guess is there is some contract between motorola (xoom) and google for exclusivity on their tablet. but dont quote me on that.
1) The web browser is much improved - even over Dolphin
2) The email client is much improved - even over K9
3) Contacts sync seamlessly with Google contacts
4) The keyboard is much improved - has a TAB key, has a "handle" to move the cursor around in text, has cut and paste features.
All of this is enough to make me swich to HC.
Downsides:
1) Many of my favorite apps cannot be found or downloaded from the Market - even though they worked fine on 2.1.
2) From uSD card, runs a little slower than 2.1, but not enough to bother me.
is the video accelerated? I could not take cm7..so slow.
winkler1b said:
is the video accelerated? I could not take cm7..so slow.
Click to expand...
Click to collapse
No. Same problem effects both I think.
Well, I switched and got my nook to recognize the sd (Class 2) partition. I expanded the image to use the 16 gigs too. I love it. The Live App switching is nice. It actually feels more like true Linux (I am thinking KDE) than any other droid system. I just can't handle the lag when booting apps (probably a combination preview/sd card). I am a teacher and grade on my Nook, so I need speed. But, I am excited about this. Thanks a lot Deeper Blue. This will be stellar.
The true app switching is almost priceless as is the efortless interface.
~Leko