Related
Process
From Wikipedia, the free encyclopedia
Process or processing typically describes the act of taking something through an established and usually routine set of procedures to convert it from one form to another, as a manufacturing or administrative procedure, such as processing milk into cheese, or processing paperwork to grant a mortgage loan, or converting computer data from one form to another.
Ok first off I'm the biggest noob at all things root as could be. I have managed to make some custom clocks for my old LG voyager way back in the day and have even jailbroke some Ipod touch's so I was able to load bootleg games and apps.
But this root thing has got my brain traped in a vortex and I really want to not just know how to root my droid (That info is everywhere) but I want to know how it all works. What terms like kernel mean and how they relate to clock speed. What is the difference between all the custom rom's? What happens when I root my phone and can't figure out what rom I should use? Do I have to reset all my apps and preferences every time i want to try a new rom?
I understand the how-to's I'm sure when I try to root my phone that I will not have much trouble doing so. But there are so many things I want to learn and know before I do anything.
I would like to say I'm not looking for links to tech reports on rom's that I will not understand I'm looking for alink (or someone who knows the things I wish to learn,) something that will explain the terms what they mean, how they relate to my phone and what outcome I should expect from loading custom rom's.
I understand that most users of this forum fall into one of two category's ONE ether super wonder techs that know exactly what they are doing and know how things work, TWO people who can read follow directions and root there phones while trying NOT to sound like noob's when they ask for help.
And then there's me I'm a number two, now I know that kinda makes me sound like **** but I really want to be a number ONE
So who want's to teach me ? Who's got some time to kill or link's to post? I'm even willing to go buy a android programmers book if there's one that would be recommended reading to help me understand the OS better.
I want to learn from the masters and this is where they all live. So will someone apprentice me ?
To close my rant out I would like to say I'm a 37 year old man with a masters in chemistry 119 IQ and ex-stream case of OCD that drive's my compulsive need to learn how things work, So I make for a good student
Thanx
ö
Thank you so much, I was hoping to be able to reply first, (this sh*t is my crack)
Ok, First off, the kernel is the basic system that controls how the cpu reacts, as well as how programs interact with the hardware on your phone, such as the screen, wifi and bluetooth modules, accelerometer, gps, ambient light and the battery. When a dev wants to overclock their android, add a module for EXT, or TUN, or add wifi support, this is where the magic happens. this is probably the most important part of the firmware. It also controls battery life via voltage, as well as cpu speed.( the average droid can be overclocked to 1200-ish, depending on the randomness of processors, though I've heard of a ridiculous version called OMAP Ti39 or something that could be stable at 2ghz, even 2.3. As I think you may know, Fat32 doesn't support file transfers of more than about 4 gigs at a time, which is why add in ext support is so important, especially since someone made a video player that reads matroska video files (blu-ray) Ive tried it, its beautiful, (V player - on the market) after kernels is framework, the framework is what renders the gui, basically everything that you see on the screen is thanks to the framework-res. We edit it either manually, or through the use of an app called metamorph, which swaps the xml files the framework uses with edited ones, such as one I recently used to give my droid a circular battery, however these xml files can change anything you could need them to visually about your droid, you just have to find what you need. Now on to shell. shell is the engine that is accesible through command prompt and terminal using the android sdk and adb, more on that can be found easily on the google android homepage. however, much use is made through devs and an app called terminal emulator that is basically a straight to shell terminal screen app. Uses for shell may include but are basically limitless, include moving any app to your sd-card to conserve rom (rom is the phones total system memory, apps usually go in there, but before froyo, and ext partition could be used, and with froyo stock support for most apps was allotted, and without the need of an ext partition.) Ram is basically ram, if you use a rom that originally came with a larger ram supported device, something called a swap partition must be implemented, otherwise it won't boot, there is an app or two that will do that for you, manual swap creation is also possible. Swap basically creates virtual ram on the sd-card. Root access, which can be acheived manually through the recovery flashing of specific zip files, or via free apps that do it with one click, basically allows you to flash kernels, change the framework, or allow tethering which I will cover next, is possible because the kernel the phone uses is linux, the unlocking of which is called granting super user access, in ubuntu a linux distribution, typing su, and your admin password will give you access to your computers system files, much in the same way we apply it to android. (However, it is unlikely you would try to flash an alternate kernel to your desktop, as it runs on either ie36 or x64 architecture, whereas phones run altogether seperate architectures , for instance android runs on ARM, and that is the base and primary reason your phone won't run windows.) Since android is free (open-source) there is an x86 version of android, including a froyo port that you can use on laptops and desktops. (Really quickly I would like to interject that recovery is an option on all phones android based that is usually accessible by holding volume up while booting, however the droid requires you press x while booting to get to recovery, which btw is what you flash a custom version of after rooting that allows you to flash roms and kernels. It also allows for backing up all of your phones firmware and data in the event of a problem. Basically its your new best friend, get familiar.) Also there is another form of booting called bootloader, it allows you to flash specific system files that are normally untouched, a guide to using that and a program called rsd lite will help you if you've bricked your phone ( Bricked- term used to describe the state of a phone that is unable to be recovered to an earlier condition and is essentially a brick or "expensive paperweight".) by allowing you to flash a completely untouched sbf (firmware) file. note that you can also use it to change your boring m boot logo with any image that fits 480x182 bytes through a slightly difficult, but fun proccess, a guide to which ,can be found here at xda, including a file that allows for the flashing of just the logo, whereas previously you had to reactivate your phone (you just have to follow the instructions on the phone) reroot, and restore the rom you previously backed up. Now on to tethering, the most important feature available to root users, which, if carriers have anything to do with it, would normally cost an extra 10 dollars a month. (Tethering- using shell or an app with the proper kernel to allow the use of your phones mobile network via usb connection, or the creation of a wifi hotspot with your desktop or laptop.) However thanks to devs who believe that what you pay for should be used how you want, most roms will tether, even in the settings, without carriers any the wiser. Windows 7 and almost all linux will automatically tether, vista is the most difficult, and xp has a quick install init file that works like a charm. The only reason we root is because we believe in the freedom to change our phones to fit us personally, and lets face it, because we can, because its fun, because its not illegal, and it brings a sense of satisfaction and pride in pushing the limits of technology. (P.S. I tried not to take to long so I couldn't really look it over, so sorry for grammatical or vocabulary based errors.)
(P.P.S. I recommend any book to do with android programming, but you'll need programming experience in linux, especially eclipse.)
Oh, and I'm a 17 year old junior with a vocabulary skill level of 139, just in case you wondered.
There are plenty of applications on the market where you can backup apps and data once you root, I personally use titanium, but I never restore system data if I'm flashing roms, only apps n data that comes with apps. Youre gonna have to search around other forums and whatnot to find the right roms.
Sent from my ADR6300 using XDA App
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.
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
Forgive me for the intrusion, but I have a question for you all. Looking at the various threads and screen shots, it appears that most are using a rooted nook rather than honeycomb or froyo; is this accurate?
My story:
I was in Best-buy the other day shopping tablets (Xoom, Galaxy, iPad, etc) and someone was walking by and said "Hey, save money, get a NC." Of course I was like, what? I'm no stranger to Linux, servers, and basic programming but tablets and android is uncharted territory for me. So, after this guy did some basic explaining I was like "half price, and near limitless customization? Yeah thats for me!"
So here I am, been browsing this website for a few days trying to decide how I should go about 'unlocking' my NC. Do I use some sort of root kit to just unlock the 'stock' system? Do I use 'Froyo' on a SD card? What about this honeycomb thing, should I use that?
Like I said, it appears from screenshots most people are still using the basic NC system, that has maybe just been rooted to run apps and such from the market? I'm sorry for sounding dumb, I'm really not, just not sure what route is best for me, or the best choice. I am a fast learner, I just don't want to spend weeks learning something only to realize I was learning the wrong thing for what I need.
What I've gathered so far:
Stock rooted NC - will do fine for most users. Launcher Pro, Pandora, YouTube, browsing, games, gmail, etc. What about GPS? Google Maps?
Froyo - Same as above, some cosmetic differences, bells and whistles only advantage?
Honeycomb - Culmination of the previous two lists?
Insight welcome please?
Signed,
Work in progress.
It may be a little over half the price... But the Nook color is half the speed of the Motorola Xoom. So if you really have the money, I would return the nook color and just get a xoom, you'll be happier with it. If you're looking for just something to surf the net, and play a few games or programs, then the NC is a decent choice.
I use CM7 nightlys. CM7 is in my opinion the best rom, it allows bluetooth support and flash. It can be overclocked to 1190mhz. And has a lot of options for customizations.
HC is limited to a preview sdk build until google decides to let others have the final source, which could be a while... (Motorola Xoom comes with it installed)
Froyo is limited in a lot of regards, and CM7 is far better and offers a lot more support for programs and hardware. That said... Some people feel Froyo is better than CM7, but they're essentially the same underlining OS.
Individuals requirements vary, but since you asked I will give my two cents:
CyanogenMod 7
While it is currently not released as "stable" but only nightly builds, the nightlies are extremely good. Phiremod is based on the nightlies and adds some nice stuff, but is also slightly behind since the nightly has to be released before it can be customized.
The latest is CM7 nightly 32 right now (http://download.cyanogenmod.com/?type=nightly&device=encore) but it changes almost every day.
A Video Test build was just released that has YouTube working in all its glory (? Did I really type that?) so the video issues should be a thing of the past in a few days. http://forum.xda-developers.com/showthread.php?t=960537
The same dev has an overclock kernel which gets the cpu up to 1100mhz and adds the interactive governor- http://forum.xda-developers.com/showthread.php?t=925451
And another guy took a great idea and ran with it: adding Tablet Tweaks to CM
http://forum.xda-developers.com/showthread.php?t=1002000
I generally run the latest nightly with an oc kernel but now that the Tablet Tweaks has made so much progress, my routine is like this:
Flash latest nightly
Flash Tablet Tweaks
Flash OC kernel
Don't let the "nightly" status of CM7 put you off too much- the CyanogenMod team are perfectionists and won't call a rom Stable until it is PERFECT.
Right now the nightlies are better than any fresh install of Windows I have ever seen, for example....
I wouldn't go to honeycomb as a permanent solution now - it is reasonably good but still experimental with problems running full tablet applications.
I'm using Froyo but will switch over to CM7 shortly. At one point, froyo was more stable (two weeks back - things change fast) with working video and flash. CM7 has come along quickly and its time to move on. Having said that - both of these require some fiddling to get working properly. This is not a no-frustration experience - if you are comfortable with sorting out linux-like issues it won't be too bad. Fun if you like tinkering with gadgets.
Rooted stock is stable, adds the open android market to the the stock B&N experience which includes a very nice reader. If you upgrade beyond stock you will lose the reader which has some desireable features like "borrowing a book" in the store, magazines and newspapers. Not working on froyo, cm7, or hc.
I'd agree that cm7 is probably the best compromise at this point - at least for me. You will still be flashing gapps and wondering where certain apps or wallpapers are in the market.
Xoom or galaxy tab actually work (largely) without customization today. Closer to an ipad experience in that it works out of the box. Nook color can largely replicate those functions but you'll do a little work setting it up.
Peter
I would not trade the NC for the Xoom just because the Xoom is so ridiculously overpriced IMO. Personally, I would go with stock rooted. If you find that you are wanting to do something with it that you cannot do on stock rooted, then look for something else like Nookie Froyo or Honeycomb (which is still a little half baked on the NC IMO).
Wonderful advice and well said. Thank you much for everyone's time, I above anyone else know how precious every second is.
'Sorting out linux and tinkering' is exactly on point, I've been doing that very thing for about 12 years now. I like to consider myself an avid enthusiast rather than full throttle geek. Anyway, I think I'll study the route of stock rooted and further my knowledge on full flash before taking that plunge.
That being said, one more question and I'll let you all get back to more important things. I should be right in assuming just follow the steps in this thread http://forum.xda-developers.com/showthread.php?t=872490 or the v3.* thread to fully root the stock NC and have google apps, market, etc up and running? From what I've read, this auto-nooter has pretty much all of it built in already; Gmail, Market, root-kit etc.
PS: Wonderful site, very informative.
Signed,
Work in Progress.
LarcenQ said:
Stock rooted NC - will do fine for most users. Launcher Pro, Pandora, YouTube, browsing, games, gmail, etc. What about GPS? Google Maps?
Froyo - Same as above, some cosmetic differences, bells and whistles only advantage?
Honeycomb - Culmination of the previous two lists?
Click to expand...
Click to collapse
I'm in your same boat (I recently started with Nookie Froyo on SD so I can leave the Nook alone, but am just learning what else needs to be done to fix some buggy behavior.)
One thing to understand is that there are multiple versions of Android. The Nook Color still ships with Android 2.1 (Eclair). They are supposed to be pushing out 2.2 (Froyo) in a few days. The Cyanogenmod (CM7) people are using 2.3 (Gingerbread). And the NookieFroyo folks are of course using 2.2. I have no idea what Phiremod is. As expected, the later versions of Android tend to have more features/work better.
The 3.0 version of Android, Honeycomb, is still the most experimental and apparently doesn't work that well with the Nook Color yet. Worse, Google has decided to hold back the latest source code of this "open source" project for now, meaning that only the Xoom can run the thing. But it's the only Android version with true tablet support.
As to GPS,the Nook Color does NOT have a GPS chip, so regardless of Android version you can get GPS coordinates only by rough calculation based on a WiFi database or by tethering to a GPS device or GPS-equipped cell phone.
xdabr said:
I have no idea what Phiremod is.
Click to expand...
Click to collapse
Phiremod is based on CM7 nightlies with some very nice customizations.
Yup -- Xoom overpriced. Unless you've a burning desire to be on the cutting edge, I'd go with the Nook Color and wait out the pricing on Android tablets. They are bound to come down.
Also, a couple of key points:
Barnes & Noble is theoretically going to push an upgrade sometime in April that will include Flash capability and some sort of Market. No details on the market. However if they're smart there will be a host of apps available that we all know will run on the Nook (because we've rooted and downloaded them). This new stock configuration may be all that a lot of people want or need.
If you are determined, however, remember that this forum is like a big toy store and can be confusing. You can run stock internally and dual boot into a fast SD card to run virtually any other configuration. Or, you can flash the internal rom and run most of these variation on the OS internally.
Here's the relevant point: When booting, the Nook Color looks first at the SD drive. That's very cool, because it allows us to do a whole bunch of fun stuff.
I'm currently running rooted stock internally and CM7 (the version with working Bluetooth) off a SD card. Truth be told I typically boot into CM7 because it works so well -- even for reading B&N Nook books. I use a little variation that allows hard key dual booting. There is a brandy new release of CM7 that resolves some video issues and I'll update to that.
However, the CM7 releases do not include the Google stuff, including the Market, so you have to load those via ADB (Android Development Bridge) which means setting up your computer with an Android development environment -- something very doable and free, but it takes some time to get it all working right.
The holy grail is probably Honeycomb, the Android version specifically designed with tablets in mind. There is a development version of Honeycomb that actually works pretty well, but it's not fully fleshed out just yet. I've got it running on a separate SD and it's very cool, but lacks some functionality. Once it's fully developed that will be my daily OS for sure.
One of my wants and needs is to be able to use an external folding keyboard. The only version floating around right now that supports the Nook's built-in Bluetooth (unused by B&N) is a release of CM7 -- and it works. I can use the nifty Freedom Pro keyboard and it's really pretty good -- no excessive lag.
Hopefully that's enough to get you going. I'd say -- given the overwhelming wealth of information on this forum -- keep your Nook stock until after B&N pushes the update. In the meantime, get a good fast SD card and use that to mess with your pick of Android versions offered here. Pick just one and than tunnel down into the forum to work with it at first.
Happy Nooking!
robedney said:
I'm currently running rooted stock internally and CM7 (the version with working Bluetooth) off a SD card.
Click to expand...
Click to collapse
Thank you! I wanted to try this CM7 tonight when I got home, however, I do not want to wipe/tamper with my onboard nook, and everything I've read about CM7 you have to install on internal memory. Is there a link to the instructions on booting CM7 from the sd card?
Thanks in advance!
Signed,
Getting somewhere.
Yup -- I'll track it down. Stay tuned.
Here's a thread that sets up a SD card to run CM7 with working Bluetooth. Read the whole thread before you start (some good simple instructions are in there):
http://forum.xda-developers.com/showthread.php?t=989637
Be aware that Google stuff and the Market are not included -- you'll have to install those via ADB (and there are full instructions on how to set up and do that on this forum.
Or -- a newer option that looks pretty cool (and avoids having to use ADB to get the Market):
http://forum.xda-developers.com/showthread.php?t=1000957
I think I'll try this on a spare SD card and see how it all works out.
There are hardware differences to consider too.
NC is 7 inch screen, vs 10 inch for XOOM and some other tablet.
Then size and weight.
Also NC doesn't have cameras, the others may have one or two...
And NC doesn't have mic, although bluetooth headset may work.
I am happy with my NC for its price and what I need.
robedney said:
Here's a thread that sets up a SD card to run CM7 with working Bluetooth. Read the whole thread before you start (some good simple instructions are in there):
http://forum.xda-developers.com/showthread.php?t=989637
Be aware that Google stuff and the Market are not included -- you'll have to install those via ADB (and there are full instructions on how to set up and do that on this forum.
Or -- a newer option that looks pretty cool (and avoids having to use ADB to get the Market):
http://forum.xda-developers.com/show....php?t=1000957
I think I'll try this on a spare SD card and see how it all works out.
Click to expand...
Click to collapse
Much obliged! I'll give this a try tonight once I get home from work. God I love mature people instead of 'scr3w yu n00b!'.
Signed,
Getting there.
Just make your of which Stock ROM you have (1.0.0, 1.0.1, 1.1.0). Each Nooter is made specifically for each ROM.
Also, as far as Gapps is concerned, there is no need to use ADB. All of it can be installed easily via ClockworkRecovery. ADB stuff is fun, but not needed to get full blown CM7 w/gapps and everything else.
http://forum.xda-developers.com/archive/index.php/t-1000957.html
just used this for a SD bootable CM7. I'm running rooted 2.1 for daily use and testing out the different options via SD bootable builds. fyi, this also allows the install of google apps without ADB.
HI,
One question for you:
What do you want to use the Nook for mainly?
Toy/Playing/learning/Android Apps/Web/eBooks... CM7 (Nightlies)
eBook reader mainly... Perhaps stock rooted.
Lots of video/Flash? Not sure which, perhaps Froyo. CM7 soon.
Require bluetooth? CM7
One immediate advantage for rooting is access to other eBook reader
applications, such as Kindle.
Don't forget to look at/select a soft button approach that you like,
Android is expecting more than the one button at the bottom. I like
Button Savior from the market, but there are a variety of other solutions.
It is handy to have a bunch of SDcards on hand too, I never seem to have
enough of them. Don't forget that when you move to an internal memory
version of, say, Cyanogenmod7, that you need a SD card for data too.
Good luck, the NC is a fun toy!
Peter
envygreen said:
http://forum.xda-developers.com/archive/index.php/t-1000957.html
just used this for a SD bootable CM7. I'm running rooted 2.1 for daily use and testing out the different options via SD bootable builds. fyi, this also allows the install of google apps without ADB.
Click to expand...
Click to collapse
We're in dire need of a single (maintained) collection of all these pre-built SD card images -- is there such a posting?
Hunting through the forum is not as much fun as it seems.
EDIT: Looks like there's a list of ROMs at http://forum.xda-developers.com/showthread.php?t=872003
DOH!
Read post carefully BEFORE replying!
lol
Delete due to lack of use
Delete please
[font=georgia,serif] You just wiped Dalvik/ Turned on Debugging or did something else that you were told to do... Take the time to LEARN about what the hell you are doing
****A-Z Android Dictionary, know what the abbreviations mean****
http://www.androidce....com/dictionary
****AOSP**** Android Open Source Project's Website with lots of info
http://source.android.com/index.html
***Wiping Data/Factory Reset***
[background=rgb(250, 250, 250)]Wipe data/factory reset does what the name says, it resets the current rom you are using back to its original state it was when you installed it, without the data you added, like your apps and personal data, contacts APN settings, bookmarks etc, thats what it does nothing else, thats what the setting is for in clockwork mode recovery[/background]
[background=rgb(250, 250, 250)]***Wiping***... What you should be wiping[/background]
Go to mounts and storage and select it.
Go to format / system and select it.
Scroll down to format system and select yes.
Go to format / data and select it
Scroll down to format data and select yes.
Go to format / cache and select it.
Scroll down to format cache and select yes
Not Needed but I know I will never hear the end of it if I don't include Wiping Dalvik
Go to Advanced and select it
Go to Dalvik Cache and select it
Select yes
Your personal files are 100% safe, this full wipe will not wipe the internal sd card and will not wipe the external sd card, all your pictures, mp3s, videos and anything you have downloaded will still be there when you install your custom rom.
However what it will wipe is the first 2gb partition which holds the operating system and all personal user data like your contacts, bookmarks, APN settings for Internet access, accounts etc...
****Dalvik****
Dalvik is the managed runtime used by applications and some system services on Android. Dalvik was originally created specifically for the Android project. Dalvik is the process vitual machine (VM) in Google's Android OS. It is the software that runs the apps on Android devices.
***De-Odex*** (I.E. A deodexed Rom)
Android uses a a java based virtual machine as the bases for running programs. This virtual machine is called Dalvik. A .dex file contains the cache used by the Dalvik VM (called Dalvik-cache) for a program and is stored inside the .apk. A .odex file is an optimized version of the .dex file which gets stored next to the .apk as opposed to inside the .apk. This process is done by default to system apps. Deodexing is the process of converting the .odex files back into .dex to be stored inside the .apk so that things can be more easily modified. So a deodexed rom is one that has been through the deodexing process. Deodex can just as easily be called Unodex or any other pre-fix you wish to use.
***RADIO***
The radio stack is responsible for the phone functionality of the device. This includes
1)***GPRS*** is a radio technology for GSM networks that adds packet-switching protocols. As a 2.5G technology, GPRS enables high-speed wireless Internet and other data communications. GPRS networks can deliver SMS, MMS, email, games and WAP applications.***
2)***GSM***, a 2G technology, is the de facto European standard for digital cellular telephone service, and it is also available in the Americas. GSM is the most widely used of the three digital wireless telephone technologies (TDMA, GSM and CDMA), and it supports voice, data, text messaging and cross-border roaming. The SIM (Subscriber Identification Module), a removable plastic card that contains a users data, is an essential element in a GSM network.
GSM operates in multiple frequency bands, GSM 900, GSM 1800, GSM 1900. When GSM is working on a radio frequency of 1800 MHz, it is sometimes referred to as DCS 1800, GSM1800 or PCN.****
3)***UMTS***The 3G mobile telephone standard in Europe, standardized by ETSI. It supports a theoretical data throughput of up to 2 Mbps. Initial trials began in 2001, and it should be rolled out in most of the world by 2005.***
4)***GPS operations as well as camera functionality. The version you use depends on who your carrier is as users have reported versions working better on one carrier than the other. The wiki pages contain the latest versions available to download and install.
***Bootloader***
The bootloader is the first thing to load once you turn on the device, this does the job of booting up the device hardware and loading various items into memory before the ROM starts in the device. The bootloader is also responsible for enabling the flashing of new ROMs and other components such as the Radio and the Ext_ROM.
***Kernel***
Short Answer
The central or core software component of most operating systems. Its responsibilities include managing the system's resources (the communication between hardware and software components) and can provide the lowest-level abstraction layer for resources (especially memory, processors, and I/O devices).
Complete Answer
Android (like many other Smartphone operating systems) runs on the Linux kernel. The Linux kernel was created in the early 1990’s by a gentleman named Linus Torvalds in Helsinki Finland. It’s incredibly stable, incredibly friendly, and incredibly difficult for the layman to understand and modify. Thankfully it’s also very popular so it has been ported on to a multitude of hardware, including our Android devices.
Think of the kernel as an interface layer between the hardware and software on your device. The kernel decides when things happen, such as the LED indicator gets lit. An application sends a request to the operating system to blink the LED. The operating system then sends the request to the kernel, which makes the light flash for the amount of time requested by the OS.
What sounds like a round-about way to get things done is also what makes the system so scalable and robust. Application developers only have to code in a way the operating system understands and the kernel makes it work on the hardware. This also keeps the application running in it’s own user-space and separate from the kernel. That means when you run the latest uber-cool app that wasn’t designed for your particular OS version, or is still very beta and it crashes, the kernel gives you the option to Force Close the application and the kernel can run untouched.
In a standard Android ROM (we will leave developer images and the like for another discussion) the kernel is bundled along with a set of instructions that tell the device how to load the kernel and the OS during boot. This is the boot.img that you see inside a zipped ROM that your not able to easily open. The device knows to extract this image to internal memory (the ramdisk) and follow a series of scripts (init scripts) to load the kernel and then the other portions of the OS. That’s what’s happening while you’re watching the boot animation. Interestingly enough this is done the same way for a PC, your smartphone, an Android tablet, or even a smart Linux powered toaster. If you’re feeling exceptionally geeky, plug your Android phone into the USB port on your PC and let the PC boot from the USB device. No, it doesn’t actually load, but you can watch the animation while it tries to match up the hardware support with what’s inside your PC. As I said, Linux is amazingly scalable and as a result so is Android.
***OS***... Operating System of course but what does it actually do????
Once the kernel is loaded, the init scripts tell the Operating System to load. Android is the user interface for a custom built Java virtual machine called Dalvik. Dalvik was written by Dan Bornstein, who named it after the fishing village of Dalvik in Iceland, where his family originated from. The debate of which Java VM is superior is best left for another discussion, so I’ll simply say that DalvikVM is a register-based machine versus true JavaVMs which are stack based.
The Dalvik machine creates executable files (.dex files) which can be interpreted by the OS and run by the end user. These .dex files are OS version dependant. That simply means that applications and core functions built to work with one version of Android may or may not work well with other versions. Google provides the tools through it’s Software Development Kit (SDK) for applications to communicate with the OS.
***Core Functions***
No smartphone would be complete without a set of functions that allow the device to be used as intended. Things like the phone and dialer interface, the calendar, the messaging system are core functions of the Operating System. In Android, these are run on top of the kernel as separate applications. The merits (or lack of) of providing these needed functions as separate applications is once again best left for another discussion, but this is what allows developers like HTC or Motorola to replace the standard functions with alternatives that provide a different look and feel from stock. HTC’s onscreen keyboard or Motorola’s MotoBlur contact list are great examples of this. The “little guy” isn’t left out of the mix either. Handcent SMS or Chomp SMS can integrate into the OS very well, as most of us already know.
An additional set of Core Functions are provided by Google. Popularly called GoogleBits, things like Gmail, sync, Gtalk and the Android Market are applications written by Google that give an extra set of useful functions to the OS. You’ll find these on all smartphones, as well as many other Android devices
***Gtalk @ [email protected]***
***Twitter @Obsidian_22***[/font]
Future
Sent from my Nexus 7 using Xparent ICS Tapatalk 2
I don't know why the thread looks weird in Tapatalk but it looks fine in Web view
Sent from my Nexus 7 using Xparent ICS Tapatalk 2
Sorry guys but due to lack of use over here I'm pulling it down.... It is still up and running @ other forums but I can't say where on here
Sent from my Nexus 7 using Xparent ICS Tapatalk 2