Related
I'm just wondering as this does not seem to be a topic written about much.
For example, this thread details how to do it based on another rom, http://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
But, this would be doable on a rom such as Cyanogenmod 6.1.1 I presume?
One obvious benefit would be to have more internal memory to be used for apps or whatnot, but does it benefit with making the system feel a bit faster or speedier, or anything of the sort?
Thanks for any info you provide.
Android 17 said:
I'm just wondering as this does not seem to be a topic written about much.
For example, this thread details how to do it based on another rom, http://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
But, this would be doable on a rom such as Cyanogenmod 6.1.1 I presume?
One obvious benefit would be to have more internal memory to be used for apps or whatnot, but does it benefit with making the system feel a bit faster or speedier, or anything of the sort?
Thanks for any info you provide.
Click to expand...
Click to collapse
The problem with doing that is it usually causes a performance loss.
Unless you have a high class card.
I have a class 6 SD card, I read that using a 4 or higher is recommended, so perhaps it would be fine in my case? I certainly wouldn't try it with the included card, that's only a class 2.
Android 17 said:
I have a class 6 SD card, I read that using a 4 or higher is recommended, so perhaps it would be fine in my case? I certainly wouldn't try it with the included card, that's only a class 2.
Click to expand...
Click to collapse
Class 6 may be fast enough to do it.
You're welcome to try it and see what the result is.
I certainly wouldn't try it with any slower of a card though.
Anyone have any experience doing so, or encountered any positives or negatives of attempting to do so?
Android 17 said:
Anyone have any experience doing so, or encountered any positives or negatives of attempting to do so?
Click to expand...
Click to collapse
I've done it to free up space. I've got about 230 apps/installed widgets and moving the davlik was the only way to reclaim my space. Works fine. Has slowed my phone but is acceptable (Class 2 32g card). I do have to say though that at this moment I'm in the process of replacing my microsd with a 32g class 10 card to speed things up a bit.
[POLL] Which gsm hero rom is CURRENTLY running on your phone?
Choose one and we'll see what's going on in the world of our little gsm heros.
I don't see a poll like this for gsm hero - certainly nothing with current roms.
Good idea for a poll! I too would like to know what is happening with our little Hero(s).
thanks
I decided to limit to only one answer, what's running right now, since many of us nandroid and flash regularly we could end up with the 5 or 6 most obvious answers all being voted for by everyone. to me that's just silly.
at least this is scientific: if not absolutely indicative of everyone's favorite rom, at least it's indicative of the current choice.
Could be used for a trend chart if in the future we do the same poll again and compare results.
a.t.m. running:
- 2.3 gingerbread - cronos
Working good, happy Gingerbread user
DjoeN said:
a.t.m. running:
- 2.3 gingerbread - cronos
Working good, happy Gingerbread user
Click to expand...
Click to collapse
Dito, and voted as such
note: I kept results anonymous (hopefully) so if you wish to keep your status private you can still vote.
happy to see people posting openly though of course
wow hahaha reload first page of gsm hero development forum and every rom thread's most recent post is my link to this poll.
I wanted to be fair so tried to post the link for every rom that is getting current thread discussion.
but no posts there after my posts, even after 15 minutes or so - I suppose everyone's here voting.
pretty much the results I expected aside from the mass of gb users!
surprising about rcmix and tegro - I know of some users of those roms currently.
wow - you VR12 guys - you could consider backing up (using nandroid) and trying out RCmix or tegro. they're both much newer versions of sense roms that are quicker in some ways and also offer newer nicer features (newer widgets and other good things). but good that you're happy with vr12 still
Cheers
dkelley said:
wow - you VR12 guys - you could consider backing up (using nandroid) and trying out RCmix or tegro. they're both much newer versions of sense roms that are quicker in some ways and also offer newer nicer features (newer widgets and other good things). but good that you're happy with vr12 still
Cheers
Click to expand...
Click to collapse
Hey dkelley, long time no speak (again)
Interesting you mentioned VR12... I have been looking into security of the Android platform, and I would strongly recommend people move off Sense-based ROMs, and onto a Froyo custom ROM for now...
I am not at liberty to give details of the exploit (and I don't have full details), given most non-custom ROM devices will sit for the rest of their lives, vulnerable to this, but I understand that the 2.1 ROMs have some pretty serious security holes in the browser system, which appear to be better in the last set of sources I pulled from CM on the froyo tree (for FroydVillain 1.7.x)
So while it's interesting to see people still using VR12, I would suggest everyone on a Sense-based ROM moves to a "proper" 2.2 vanilla ROM. I don't think a Sense UI 2.2 ROM would be safe, so I'd discourage those too. It appears you need something CM based, and pretty recent.
As such, I would urge anyone using older CM-based ROMs (say from before November or October) to upgrade if they are concerned about security while surfing the internet. HTC don't seem to be interested in fixing the vulnerability, but I checked FV 1.7 and it is not vulnerable to this one attack.
If you support the idea of HTC being pressed into updating their phones (remember that EVERY user of the Hero, who isn't on a custom ROM, is vulnerable to any security exploits, which will not be fixed unless they do an update), then check out http://bit.ly/fDGHPV, where I am trying to get some support together before I contact HTC and mobile carriers.
PS Don, I seem to have derailed this a bit... Figured it was perhaps best to post this in here, since there's no point in making a new thread that we want to get many people to do, and you already did the "donkey work" so to speak. If this derails the thread, I'll sweep it out into another thread if you want
pulser_g2 said:
If you support the idea of HTC being pressed into updating their phones (remember that EVERY user of the Hero, who isn't on a custom ROM, is vulnerable to any security exploits, which will not be fixed unless they do an update), then check out http://bit.ly/fDGHPV, where I am trying to get some support together before I contact HTC and mobile carriers.
Click to expand...
Click to collapse
Hi....
Do you have any CVE references ?
http://cve.mitre.org/
This is just a blog with without any CVE-refs as I can see.....
http://thomascannon.net/blog/2010/11/android-data-stealing-vulnerability/
Hey Pulser
surprised you didn't send me a warning for spamming the same post linking to this thread in like a dozen gsm hero threads within 5 minutes yesterday LoL
Interesting, and a little scary, what you're saying.
But being the scientific (and slightly cynical) type I tend not to believe anything without either proof or at least further information.
I'll read up on it some - but can you summarize the possible type of damage? such as gathering of private data by parties who know about the exploit? or damage to the phone via intentional cause (again by parties in the know)? or what
dkelley said:
Hey Pulser
surprised you didn't send me a warning for spamming the same post linking to this thread in like a dozen gsm hero threads within 5 minutes yesterday LoL
Interesting, and a little scary, what you're saying.
But being the scientific (and slightly cynical) type I tend not to believe anything without either proof or at least further information.
I'll read up on it some - but can you summarize the possible type of damage? such as gathering of private data by parties who know about the exploit? or damage to the phone via intentional cause (again by parties in the know)? or what
Click to expand...
Click to collapse
I went back to Cronosproject 1.7.2 from gb beta 6. Even the massive headway they made thus far has been awesome with Fee and Ele together I can't see how it can be made as good as 1.7.2. Its way behind on performance and hogs memory with the minimum system and regular apps installed. The battery seems awesome but not much in there to use it. I'll wait till full release or stick with this rom. I can have a desire on wife's upgrade but I fancy something more now.desire is very quick.
V1.7.2 Cronos® Speed Machine
spikey68 said:
I went back to Cronosproject 1.7.2 from gb beta 6. Even the massive headway they made thus far has been awesome with Fee and Ele together I can't see how it can be made as good as 1.7.2. Its way behind on performance and hogs memory with the minimum system and regular apps installed. The battery seems awesome but not much in there to use it. I'll wait till full release or stick with this rom. I can have a desire on wife's upgrade but I fancy something more now.desire is very quick.
V1.7.2 Cronos® Speed Machine
Click to expand...
Click to collapse
agreed but give it time, and disagreed about "hogs memory": using the available memory like crazy is done to speed up performance, it's not hogging anything in a bad way. when something else requests memory that memory is freed up.
gb's memory manager is years ahead of it's predecessors
but yea, it will take a while.
Note - it's at 0.0.7 now and has everything working except camera which they're working on. performance is always improving, all sensors work now, and it's pretty amazing.
I just need a more stable build for now dude. Grafix and app issues made me revert. I'm sure with input on Cronus now they will make it much better. They need to get used to each others methods of building. I love it on there and not many will give it the dedication that Feeyo puts in. Ele is not dissimilar so expect great things. The futures bright
V1.7.2 Cronos® Speed Machine
spikey68 said:
I just need a more stable build for now dude. Grafix and app issues made me revert. I'm sure with input on Cronus now they will make it much better. They need to get used to each others methods of building. I love it on there and not many will give it the dedication that Feeyo puts in. Ele is not dissimilar so expect great things. The futures bright
V1.7.2 Cronos® Speed Machine
Click to expand...
Click to collapse
agreed. was just correcting you about the memory hogging thing since it's a good thing not a bad thing.
edit: well, not agreed about stability LoL. sorry I keep doing that . I'm running it and have for days and it's super stable. gui speed has improved a ton now too. you wouldn't know you were in such a new rom if you tried it on my phone cuz I disabled the animatinos etc very carefully in various settings places and use LP and so on.
BUT for me the fastest rom is still cronos eclair lite - it's gui, with LP, is noticeably faster than with other roms. If only it wasn't 2.1 based (with it's EXCEPTIONALLY slow and crappy applications manager and so on).
dkelley said:
agreed. was just correcting you about the memory hogging thing since it's a good thing not a bad thing.
edit: well, not agreed about stability LoL. sorry I keep doing that . I'm running it and have for days and it's super stable. gui speed has improved a ton now too. you wouldn't know you were in such a new rom if you tried it on my phone cuz I disabled the animatinos etc very carefully in various settings places and use LP and so on.
BUT for me the fastest rom is still cronos eclair lite - it's gui, with LP, is noticeably faster than with other roms. If only it wasn't 2.1 based (with it's EXCEPTIONALLY slow and crappy applications manager and so on).
Click to expand...
Click to collapse
I just had fc's with too many things. Neo, quad, then regular apps and no market. With minimal apps it was slowing right down. I figured that no matter how good the memory allocation manager if you don't have the physical memory the manager can't work right. I'll wait. Do you have basics like market working?
I never had any kind of lag with 1.7.2. The GUI is awesome. It benches close to the desire.
V1.7.2 Cronos® Speed Machine
spikey68 said:
I just had fc's with too many things. Neo, quad, then regular apps and no market. With minimal apps it was slowing right down. I figured that no matter how good the memory allocation manager if you don't have the physical memory the manager can't work right. I'll wait. Do you have basics like market working?
V1.7.2 Cronos® Speed Machine
Click to expand...
Click to collapse
everything's workign perfectly, no FCs, market's been fine for several versions now for most of us. everything except camera apps and certain specific graphics apps work great now.
neocore's broken, doesn't matter of course, same with quad, it's not relevant to anything. They're apps designed for certain operating system versions and hardware and the hero running gb doesn't fit the bill. those are are irrelevant apps that can be dismissed.
I play lots of games and they're working just great. all productivity and utility apps are great.
audio and multimedia stuff are fine too. not really sure where you were getting FCs but it sounds like it needed a new wipe and reflash possibly.
but then there's that strange thing were not every rom works on everyone's hero - I'll never know why, but I swear it's true
apps2sd and so on are working now (with a patch from elelinux). there's something that's slowing down the gui and animations still, and I accidentally had my gb phone running super fast in those areas when my app2sd flash borked. So I know a solution is possible to that last little bit of performance...
dkelley said:
everything's workign perfectly, no FCs, market's been fine for several versions now for most of us. everything except camera apps and certain specific graphics apps work great now.
neocore's broken, doesn't matter of course, same with quad, it's not relevant to anything. They're apps designed for certain operating system versions and hardware and the hero running gb doesn't fit the bill. those are are irrelevant apps that can be dismissed.
I play lots of games and they're working just great. all productivity and utility apps are great.
audio and multimedia stuff are fine too. not really sure where you were getting FCs but it sounds like it needed a new wipe and reflash possibly.
but then there's that strange thing were not every rom works on everyone's hero - I'll never know why, but I swear it's true
apps2sd and so on are working now (with a patch from elelinux). there's something that's slowing down the gui and animations still, and I accidentally had my gb phone running super fast in those areas when my app2sd flash borked. So I know a solution is possible to that last little bit of performance...
Click to expand...
Click to collapse
Weird dude. I haven't had time to go through the thread but I will now and go again. I could swear I full factory reset and wiped everything.
I had a long week with kids but thanks, I wondered why it was so bad.... but it wasn't! And no mention of my probs!
Taxi for spike...
V1.7.2 Cronos® Speed Machine
spikey68 said:
Weird dude. I haven't had time to go through the thread but I will now and go again. I could swear I full factory reset and wiped everything.
I had a long week with kids but thanks, I wondered why it was so bad.... but it wasn't! And no mention of my probs!
Taxi for spike...
V1.7.2 Cronos® Speed Machine
Click to expand...
Click to collapse
haha - well hopefully it'll work better for you now than it did before. you will find slow gui screen animations at times though so it's worth disabling all of that and using launcherpro (if you can find launcherpro anywhere considering fede's rather frustrating emergency issue at the moment).
My launcher pro plus backup will work wont it?
V1.7.2 Cronos® Speed Machine
So I have been searching the forum for a while but haven't been able to piece together a good answer from what I have been reading, so I decided to go ahead and ask. I know that these questions have been asked before, more or less, but at the rate development is going, and with the updated Android builds, I would guess things have changed even from 2-3 weeks ago, let alone 2-3 months.
What are the advantages of a NAND build (nowadays anyhow) over SD? Is it the speed?
Is battery life better on NAND or SD or it is really up to the kernel?
Are RAM editions somewhat speedier than their counterparts? if so, are they less stable or something than a regular NAND or SD version? I mean, if they are equally as stable, why isn't every developer doing RAM versions to get the most possible speed?
I know the speed of the SD card helps with SD versions to some extent. I bought a 16GB class 10 Wintec for that purpose, and it seems to do well. At that point, battery nonwithstanding, would be it worth it to go to a NAND build or would the speedy MicroSD make up most (if not all) the difference?
Thanks for the answers in advance. I just wanted to get a little bit of updated info from those in the know
While I am at it, another question to add to the list.
Does the underlying OS make a difference with the SD build? I know that Android should shut down and supersede the WM drivers, but would having WM7 over WM6.5 as the underlying build make any difference whatsoever to anything when booted into Android from SD?
thanks!
Main advantate of NAND is that you can replace SD card without turning off phone. And your build don't rely on speed of SD card. But due to small storage space, many builds still use SD which kinda defeats it's purpose.
Sent from my DL DesireZ 3.3 final using XDA App
No one has any idea on the other questions? Thanks for your input matejdo.
Again, some info is appreciated.
SD/RAM/NAND?????????????????????????/
I would really like these questions answered too.
I know that so far NAND is more complicated ....
with 2 or even 3 partitions, from EXT2/3/4, < who knows which is best.
And NAND is not as fast as RAM obv but is much safer in regards to corruption.
I have found SD builds to score higher in flops and quadrant than NAND however which is strange. SD is easier to copy to device, other than that im sure all custom roms have their issues. including screen light on lag.
i have tried and loved darkstone ram edition which was rapid but just not all there is you know what i mean, and now after giving up on dandiests desirez3.4/5 in nand and sd after too many lags, crashes and data drops etc im looking at MCCM HD V4 or MCCM GB1.8 SENSE GINGERBREAD as these seem to be the most stable build with all functioning functions but i shall soon see how they fair.........
.............................greatest respect goes to all devs for you efforts
we're nearly there!
but please any input regarding these questions would personally b appreciated!
Ok, here's my 10 cents. Some of this is debatable but these are pretty standard answers.
jotekman said:
What are the advantages of a NAND build (nowadays anyhow) over SD? Is it the speed?
Click to expand...
Click to collapse
Yes, speed, responsiveness, battery life, etc.
jotekman said:
Is battery life better on NAND or SD or it is really up to the kernel?
Click to expand...
Click to collapse
Battery life is typically better on NAND. Kernels can also make a difference.
jotekman said:
Are RAM editions somewhat speedier than their counterparts? if so, are they less stable or something than a regular NAND or SD version?
Click to expand...
Click to collapse
Technically, RAM editions are faster but they are worse on battery life. Data stored in RAM requires constant power and does not survive a power cycle of the phone, therefore the data is stored typically to SD card, which also consumes more power.
jotekman said:
I mean, if they are equally as stable, why isn't every developer doing RAM versions to get the most possible speed?
Click to expand...
Click to collapse
Previous answer is why, more power consumption, data stored on SD.
jotekman said:
I know the speed of the SD card helps with SD versions to some extent. I bought a 16GB class 10 Wintec for that purpose, and it seems to do well. At that point, battery nonwithstanding, would be it worth it to go to a NAND build or would the speedy MicroSD make up most (if not all) the difference?
Click to expand...
Click to collapse
They say NAND write operations take longer than an SD card but for the life of me I still find it faster when a ROM is running completely off NAND than off NAND and an SD-EXT partition. Or, NAND versus full-SD- there is a huge difference in responsiveness between read speeds. They are much faster on NAND than even a fast SD card.
Hope that helps...
benc88 said:
I know that so far NAND is more complicated ....
with 2 or even 3 partitions, from EXT2/3/4, < who knows which is best.
Click to expand...
Click to collapse
It can be more complicated... until you do it once or twice and fully understand how it works. Now that this has all been out a while everything is starting to standardize and more and more ROM's are using the same partition layouts. From a performance perspective there really isn't anything noticeable between EXT 2/3/4.
Oh, most ROM's now also use CWM, which along with an SD-EXT partition can leave you with up to 7 different partitions on your device. Fortunately, you don't really have to manage any of them as the ROM's do all the work once you've set it up once.
benc88 said:
I have found SD builds to score higher in flops and quadrant than NAND however which is strange. SD is easier to copy to device, other than that im sure all custom roms have their issues. including screen light on lag.
Click to expand...
Click to collapse
This is due to a slower write speed of NAND storage versus SD storage. But, because the read speed of NAND storage is higher you still get an overall feel of greater responsiveness and speed even though the scores are lower. NAND ROM's are easier to backup and manage via the CWM aspect.
I mean, if they are equally as stable, why isn't every developer doing RAM versions to get the most possible speed?
Click to expand...
Click to collapse
Possible problem may be higher amount of RAM needed. Especially sense builds would need a lot of RAM.
I have to disagree with a lot of what the post above mine said... The main difference between NAND and SD builds is with NAND builds you can use clockwork recovery, remove and replace your SD card while booted in android, and maybe a few other small improvement in stability and performance, but nothing too noticeable. Speed and battery life are about the same. You might get a little better battery life on standby with NAND. I generally got 3-5ma drain on standby with NAND, while I get 4-6ma on standby with SD. Speed and performance are pretty much the same because when you're running something with either type of build, it does it from RAM with either type of build. When an app or a process is running, it goes into ram, regardless of where the info was stored. NAND and SD are just the 2 options of where the data is stored when it's not being used by ram. Actually, the NAND in the HD2 can be slower than the NAND in good quality SD cards... but the random access speed is good in the HD2 NAND. But with a high quality SD card, you can get just as good random access speed with SD. That is what makes the performance difference with different SD cards... when the OS is trying to access small amounts of data or write small amounts of data, different SD cards will take different amounts of time to access... and the class rating of the card has nothing to do with that... in fact, class 2 cards tend to have better random access times than class 6 or 10.
But anyways, if you have a good SD card, performance and battery life are about the same... depending on the build of course. Desire HD builds tend to run a little better on NAND... but some recent SD DesireHD builds are good, too. AOSP and CM builds run pretty much the same off of SD and NAND as far as I can tell.
RAM builds work by loading more of the OS files into RAM at startup so that the random access speed of them is improved greatly, since RAM is the fastest memory and where any data is loaded to run anyways... it cuts down on the need to access the SD card for as many small system files, which improves performance and battery life in theory. The RAM is used anyways, so it doesn't use any more power keeping extra data in RAM, and since the SD card isn't accessed as much, it saves power there. But SD doesn't use much power anyways, so it's not really a noticeable power reduction. Also, RAM builds are still pretty experimental, and can have problems with data corruption... if any changes made to the os are not recorded to the SD, then if you lose power suddenly, there can be problems. Also, keeping all those system files in RAM causes you tohave less RAM available to run other apps and such... thats why there's no RAM builds for DesireHD builds, because there's not enough RAM. Personally, I never noticed too much of an increase in RAM builds performance compared to other AOSP SD builds like JDMS. Also, I'm not sure why, but I don't think RAM builds worked very good with NAND. But in theory, the system files in RAM is a good idea, especially for SD cards so it takes some stress off the SD cards. When running a build off SD, your accessing the SD to read and write system files while also accessing it as normal to run your apps or play your music or other data you have on SD. Keeping system files in RAM cuts down on the work the SD needs to do in the same way installing android to NAND does... then the SD is just used to access your media files or apps or data.
So in the end, it all depends on what you want from your phone... if you are not going to use winmo or wp7, and only use android, you might as well put android on nand, even if the improvement isn't that noticeable, because you can then use clockwork for easy updating or flashing roms, and you can change out your sd card, and there may be other small improvements. But if you still use winmo or wp7, then you have to decide if it's worth losing the ability to run more than one OS to give your android the added functionality of clockwork and other improvements. I use android on NAND for a month or so, but I didn't like how it turned my phone into just another android phone... it couldn't do anything that you couldn't do with a desire or evo or other android phone. But with the ability to run winmo or wp7 also, it's the only phone that can do it this well. When wp7 was released for the HD2, it was perfect for me because I wanted to try that OS out, and now I love that OS almost as much as android... I would have a hard time picking between the 2... luckily I don't have to. No other phone can run both of those OS's, either... I feel like I'm really making use of my HD2. If I just wanted android, I would've bought a native android phone from the beginning. But the great thing about the HD2 is no matter what OS you want, the HD2 can do it. People who want just android can make their HD2s almost like a native android phone now that it has clockwork recovery support. People who want 2 OS's can do that too. Android runs great from both SD and NAND... so use what works for you.
the battery life in android roms, is better than original windows mobile?
speed battery and efficiency are the main reasons
Yes it has a beter battery life (imo)
Ram is faster memory wich will make everything very fast, but you have to fuzz with Windows Mobile (?) to get there and that is what people dont like, the I/O on RAM is very fast, thats nice and makes quadrant scores very high
Class 10 card is good for SD versions, but imo that is very outdated, NAND is the way to go, like real Android devices loaded from the phone memory, not ram or sd, wich gives a beter battery life and fast speed (almost like stock) .. and also important , no fuzz with Windows Mobile.
And rest of the data wich isnt on your phone mem can be get of your SD card with a NAND version, cause the phone mem doesnt have rly that much space left after u installed Android on it (enough for enough apps though), class 10 mostly means a faster speed, so it will benefit you in some way
zarathustrax said:
I have to disagree with a lot of what the post above mine said...
Click to expand...
Click to collapse
No offense at all, but I really tried to read your massive wall of text but I got lost after the first sentence.
I beleive that the custom android roms do last longer than original winmo. I love this 2.3.2 rom on my HD2. 2.3.2 on my gf's mytouch 4g last about 18 hours on moderate call/text/ use with overclocked on 1.3
Azerox said:
speed battery and efficiency are the main reasons
Yes it has a beter battery life (imo)
Ram is faster memory wich will make everything very fast, but you have to fuzz with Windows Mobile (?) to get there and that is what people dont like, the I/O on RAM is very fast, thats nice and makes quadrant scores very high
Class 10 card is good for SD versions, but imo that is very outdated, NAND is the way to go, like real Android devices loaded from the phone memory, not ram or sd, wich gives a beter battery life and fast speed (almost like stock) .. and also important , no fuzz with Windows Mobile.
And rest of the data wich isnt on your phone mem can be get of your SD card with a NAND version, cause the phone mem doesnt have rly that much space left after u installed Android on it (enough for enough apps though), class 10 mostly means a faster speed, so it will benefit you in some way
Click to expand...
Click to collapse
for ex in win mobile, using the hd2 moderatly, how long the battery survive? and in android?
Wow! Lots of great info here!
I have been playing back and forth with different OS's and builds and SD builds and NAND builds etc. My phone is probably screaming at me to give it a break
As per responsiveness, the NAND builds (non-sense) seem to be a little snappier than the SD ones for me. The battery life seems about the same. Haven't had a problem with NAND space as I bought a US HD2 with 1 gig of ROM space, which is plenty for me. I haven't actually delved into the WM7 yet, but after reading this, I think I might give it a whirl and see what happens.
The biggest difference for me between the Android Nand/SD builds was the initial loading times. Which makes not that much of a difference because I tend not to turn off my phone anyhow.
The 2nd biggest difference is the wake from standby. On almost all the SD builds I tried, I would hit the hangup button, and the screen would come on in like 1/3-1/2 a second. If I accidentally hit it twice, I would have to wait 3-4 seconds for it to work properly again.... more presses seemed to do nothing. On a NAND build, it seems like the screen comes on instantly, and does not have the repress issue. But, then again, this is not a big issue for me at all.
The fastest build, by far, that I have tried so far is the Hyperdroid v5 build. It really does respond faster than almost anything I have put on the phone.
Thanks for all the answers people! It really helped to fill in the gaps in my admittedly shaky knowledge!
Digital Outcast said:
No offense at all, but I really tried to read your massive wall of text but I got lost after the first sentence.
Click to expand...
Click to collapse
Yeah, sorry about that... I tend to try to fit too much info into a post all at once and I sometimes don't organize it well. I'll also ramble on sometimes to get everything out I'm trying to say and it ends up making the reader miss a lot of the important parts.
zarathustrax said:
Yeah, sorry about that... I tend to try to fit too much info into a post all at once and I sometimes don't organize it well. I'll also ramble on sometimes to get everything out I'm trying to say and it ends up making the reader miss a lot of the important parts.
Click to expand...
Click to collapse
i understood it quite well..i think u have alot of valid points.. There arent big differences between sd/ram/nand...its a matter of choice imo..
11111
11111lllllllllllllllllllllllll
if its on sd card it will still load into android after turning off everytime right? i dont want to see windows anymore at all
zarathustrax said:
I have to disagree with a lot of what the post above mine said... The main difference between NAND and SD builds is with NAND builds you can use clockwork recovery, remove and replace your SD card while booted in android, and maybe a few other small improvement in stability and performance, but nothing too noticeable. Speed and battery life are about the same.....
Click to expand...
Click to collapse
Thank you for your post it has the best thought out points for and against, and greatly helped me in deciding which build to go for.
Hi All
I've been using ICS since pretty much day one when i bought the phone.
I realized the USB transfer speed when I copy files is very low.
in my phone around 1.3MB/s and on another 1.9MB/s
both are incredibly slow.
Could you guys help me determine whether this is a problem only affecting my phones, or is something ICS related?
Seems to be ICS related, many threads saying the same problem. I'm getting a middle-ground speed personally on ICS.
If you want to transfer large files, you might prefer doing it via mounting the sdcard through recovery (assuming you have a custom one, don't think stock can do this).
It is Google who may completely solve this problem...
Harbb said:
Seems to be ICS related, many threads saying the same problem. I'm getting a middle-ground speed personally on ICS.
If you want to transfer large files, you might prefer doing it via mounting the sdcard through recovery (assuming you have a custom one, don't think stock can do this).
Click to expand...
Click to collapse
nope, GB has this problem too.
i opened a thread about this on the google support forums, but didnt get any helpful answers. nobody know how to solve this.
the transfer-rate just stays around 1.3 mb/s, tops (for me at least). this is painfully slow. i'm pretty sure google locks the speed somehow, for whatever reason.
on my n900 i get my usual 10-12 mb/s write speed, no matter if internal storage or microsd. why cant the nexus do this?
I wonder whether thee from devs are aware of this. Should be able to fix it.. how can we let them know?
I'm fairly certain the devs are aware of this. Maybe the CM team has something in mind here, i havn't tested sd speed on any CM9 ROM - or maybe they need some notification. It may not be a "bug" in the common sense, but possibly a series of underlying issues which increase the transfer rate. Maybe I'll test some things later to see if i can get a better idea on what is the cause.
For the record, I could get around 3-4MB/s on GB, i get around 2.5 - 3MB/s on ICS. In recovery i get closer to 4 - 4.5MB/s. The flash memory inside the Nexus S is quite slow write-wise, sadly. External SDCards rely entirely on the Class it is in, C2 will be very slow, C4 faster, up to C12 or whatever they have now which are happy to write Full HD video in real time.
got the same prob since beginning of the ics era ...
All right so this may be strange but...
I had no problem creating a bootable SD card for the Nook Color. Wanting the latest and greatest, I went for CM9.
I got Samian's larger CM9 image file so I could use the cm9 nightlies, which are too big for the boot partition of CM7 build.
Anyway, it all went great. Smooth as butter, no crashes, no fuss. So far everything works....EXCEPT, I don't know exactly how it IS supposed to work, since this is the first and only android device I've owned.
So I am in the strange position of having no real technical issue -- but I do have significant "user" questions.
Here are a few. 1. Android Marketplace seemed to install fine. But I end up going to google play when I hit the "shop" button. Is that right? Or is marketplace some kind of integrated app I should be able to use without google play coming up?
2. Can I access the files on my internal Nook Color memory -- i.e. can I read my books, or do I have to put them on the SD card?
3. Are all my apps always on? Is there a way to "shut them down"? Do I need to? Coming from a PC environment, I like to shut down a program when I'm not running it.
4. My "system" information shows (when look at running programs) that I have only about 500MB of RAM. Is there a way to use some of my SD card for more RAM -- or any other way to increase it?
5. Any kind of general user guide for CM9 out there? I realize there probably wouldn't be one specific to Nook Color, since in a sense this is very elaborate hack, but I am starting from scratch.
thanks so much. I've enjoyed the messing around, and I'm thrilled at how well it's gone so far. I got a lot of info from xda.
RevTom said:
All right so this may be strange but...
I had no problem creating a bootable SD card for the Nook Color. Wanting the latest and greatest, I went for CM9.
I got Samian's larger CM9 image file so I could use the cm9 nightlies, which are too big for the boot partition of CM7 build.
Anyway, it all went great. Smooth as butter, no crashes, no fuss. So far everything works....EXCEPT, I don't know exactly how it IS supposed to work, since this is the first and only android device I've owned.
So I am in the strange position of having no real technical issue -- but I do have significant "user" questions.
Here are a few. 1. Android Marketplace seemed to install fine. But I end up going to google play when I hit the "shop" button. Is that right? Or is marketplace some kind of integrated app I should be able to use without google play coming up?
2. Can I access the files on my internal Nook Color memory -- i.e. can I read my books, or do I have to put them on the SD card?
3. Are all my apps always on? Is there a way to "shut them down"? Do I need to? Coming from a PC environment, I like to shut down a program when I'm not running it.
4. My "system" information shows (when look at running programs) that I have only about 500MB of RAM. Is there a way to use some of my SD card for more RAM -- or any other way to increase it?
5. Any kind of general user guide for CM9 out there? I realize there probably wouldn't be one specific to Nook Color, since in a sense this is very elaborate hack, but I am starting from scratch.
thanks so much. I've enjoyed the messing around, and I'm thrilled at how well it's gone so far. I got a lot of info from xda.
Click to expand...
Click to collapse
1. Market just was upgraded by google to Play Store. So it is operating properly.
2. You can access files from internal media memory (emmc). But you may have difficulty reading the nook books stored there. They are encrypted for your nook account (DRM). But you can install the android version of the Nook reader and log into your account and redownload them to your SD.
3. Don't worry about always on apps. Android was built for multitasking and has a very efficient memory management system. It does everything for you. It puts apps in memory for you so that when you go to them they are ready to start. Just being in memory is not using processor time so it is not a drain. Also Android will automatically remove apps from memory if it needs to.
4. Because of 3 above 512MB is a lot ram. There is really no need to expand it.
5. Off the top of my head I don't know of a manual, but I'm sure there are some out there. Just google search.
Most of the questions are Android related matters, so any google search about general Android, would do the job.
Unleashed from my Revolutionized Desire HD
Thanks Guys, I appreciate it.
Two follow up questions:
I am running ICS/CM9. Only been at it a day or so, but so far, no real problems. The screen might be *slightly* less responsive than the NC system, but it's not clunky -- maybe just a little slower, a little more prone to having to tap some things more than once.
1. I've seen many other posts of people raving about CM7 and how stable and zippy it is. Would I benefit from switching to CM7? Is it faster/more responsive than CM9 currently?
2. I was thinking of just finding another cheap micro SD and installing CM7 on it (rather than the dual boot thing, which would require me to wipe my current SD and start over). Any reason it wouldn't work to run CM7 off a different card?
thanks again!
It would be worth it for you to get another SD card and load CM7 on it to see the difference. I have used both CM7 and CM9 and love the interface of CM9 but do prefer the stability of CM7.
Learning your way around the systems can.be daunting, but stick with it - Google your questions, read the forums here. You will learn loads just using your nook.
Sent from my NookColor using xda premium
RevTom,
Only use a Sandisk Cl 2 or 4 microSD card for an SD install. Others don't work as well. This has been well documented here on XDA many times.
There is a high likelihood you will have a bad experience if you don't follow this advice.. (force closes.. slow response, ramdom re-boots, etc)
Search the web.. they are about as inexpensive as the rest. Sometimes Radio Shack has a decent price on them.. sometimes not..
RevTom said:
Thanks Guys, I appreciate it.
Two follow up questions:
I am running ICS/CM9. Only been at it a day or so, but so far, no real problems. The screen might be *slightly* less responsive than the NC system, but it's not clunky -- maybe just a little slower, a little more prone to having to tap some things more than once.
1. I've seen many other posts of people raving about CM7 and how stable and zippy it is. Would I benefit from switching to CM7? Is it faster/more responsive than CM9 currently?
2. I was thinking of just finding another cheap micro SD and installing CM7 on it (rather than the dual boot thing, which would require me to wipe my current SD and start over). Any reason it wouldn't work to run CM7 off a different card?
thanks again!
Click to expand...
Click to collapse
1. Just a little faster, more stable. But you give up the tablet interface.
2. Only reason not to is inconvenience of manually switching the cards and of course your media files go with each card. But it will give you a chance to look at it and decide which you want.
Sent from my Nook Color running ICS and Tapatalk
davidr415 said:
RevTom,
Only use a Sandisk Cl 2 or 4 microSD card for an SD install. Others don't work as well. This has been well documented here on XDA many times.
There is a high likelihood you will have a bad experience if you don't follow this advice.. (force closes.. slow response, ramdom re-boots, etc)
Search the web.. they are about as inexpensive as the rest. Sometimes Radio Shack has a decent price on them.. sometimes not..
Click to expand...
Click to collapse
Yes, I've seen those threads -- maybe I can add some new info. I went with a SanDisk class 6 16GB. I didn't see the class-rating discussions until too late. There are some who also recommend staying 8GB.
However, with CM9, I've had no trouble using the class 6, 16GB. Maybe I just got lucky, or perhaps CM9 can handle the 6.
I'm glad your class 6 is working for you. Have you seen Racks thread in the development section for a dual boot SD card with both Cm7 and Cm9 on it? I did that for awhile. His instructions are pretty straight forward. You can have your books, pictures, music, etc. on the.SD card and use them with both systems.
Sent from my NookColor using xda premium
k8108 said:
I'm glad your class 6 is working for you. Have you seen Racks thread in the development section for a dual boot SD card with both Cm7 and Cm9 on it? I did that for awhile. His instructions are pretty straight forward. You can have your books, pictures, music, etc. on the.SD card and use them with both systems.
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
Yes, I've seen the the thread. I would still have to wipe what I have so far, and I like the version of CM9 I've already got -- believe it came from someone called "Samian" or something like that.
One final question. For a single-boot SD OS, anyone have thoughts on the best CM7 to run with?
RevTom said:
Yes, I've seen the the thread. I would still have to wipe what I have so far, and I like the version of CM9 I've already got -- believe it came from someone called "Samian" or something like that.
One final question. For a single-boot SD OS, anyone have thoughts on the best CM7 to run with?
Click to expand...
Click to collapse
Some swear by Mirage by mr666. It has been customized heavily so I personally like stock CM 7.2 RC3 from the Cyanogenmod site.
Sent from my Nook Color running ICS and Tapatalk
Mirage-Kang no question.
---------------------------------------------------
Sent from the Center of My Mind
RevTom said:
Yes, I've seen the the thread. I would still have to wipe what I have so far, and I like the version of CM9 I've already got -- believe it came from someone called "Samian" or something like that.
One final question. For a single-boot SD OS, anyone have thoughts on the best CM7 to run with?
Click to expand...
Click to collapse
My own setup involves Cm7 at main memory with 233 nightly and sdcard with Racks dualboot (kang Cm7 and ICS).
You should consider the fact that its easy to try other systems by just swapping Sd cards. Then you will find what you really like.
Unleashed from my Nook Color at 1.2G
Here's where I got my original CM9
android.sphsolutions.net/Encore/Nightlies/Misc/
The "generic 1.3" creates a larger boot sector to accommodate the larger cm9 nightlies.
Since the first post, I left that one on my larger, faster card (class 6, 16GB), and tried Racks' Dual boot. Cm9 seems to run a little zippy-er there, but I can't tell if that is the build or it is the fact that I'm running that one from an 8gb class 4 card (which is said to be better than a class 6).
Still favoring ICS/CM9 over CM7.
Any thoughts on file management for the free SD space? I am having mixed results with plugging the Nook into the PC. Sometimes I have full access to the free space/storage on the SD, and sometimes it shows up without any folders or files at all. (this is in Racks Dual boot, CM9)
Also, anyone remember off-hand where I can find the thread that tells me how to make CM9 the first (primary) boot instead of the secondary? I've traveled so much ground in these forums lately...