Related
I have an HD2 with SPL 2.08 and radio 2.15 , WinMo rom - Dexter .sencity 21.11 .
I have tried with other combinations too. My SD card is the original class 2 2gb micro SD. When I install Desire rom it works fast and everything is fine. When I put a Desire HD rom however it is slow - i takes 1-2 secs for it to open keyboard or the menus and so on. I dont know what the problem is or how can I see exactly how slow it is. Any help would be much appreciated! It is odd that people report that the Desire HD roms are really fast when they are slow on my HD2. Probably I messed up something but I dont know what so please HELP! I have tried different roms from m-deejay and Sergio76 and so on. The Froyo stock roms also work fast and flawless. I know there is another thread but it is in another section and there are no responses because this sections has 100x more activity. THank you!
Man honestly to rule out any possibilities of the ROM being the factor you have to use a class 6 or above sd card, otherwise you have no way of really troubleshooting what your problem is. Also, Devs mention in the releases all the time the Radio and WinMo ROM they use so to insure the same performance they can only give you what they are running as well.
SkyWalka said:
Man honestly to rule out any possibilities of the ROM being the factor you have to use a class 6 or above sd card, otherwise you have no way of really troubleshooting what your problem is. Also, Devs mention in the releases all the time the Radio and WinMo ROM they use so to insure the same performance they can only give you what they are running as well.
Click to expand...
Click to collapse
The class of the SD card has nothing to do with it. The majority or people that have tried a class 4 and above say it is a lot worse than the stock SD card. I have tried and it was a lot worse for me also.
The Windows ROM and radio can have a LOT to do with it though.
m2]iceman said:
I have an HD2 with SPL 2.08 and radio 2.15 , WinMo rom - Dexter .sencity 21.11 .
I have tried with other combinations too. My SD card is the original class 2 2gb micro SD. When I install Desire rom it works fast and everything is fine. When I put a Desire HD rom however it is slow - i takes 1-2 secs for it to open keyboard or the menus and so on. I dont know what the problem is or how can I see exactly how slow it is. Any help would be much appreciated! It is odd that people report that the Desire HD roms are really fast when they are slow on my HD2. Probably I messed up something but I dont know what so please HELP! I have tried different roms from m-deejay and Sergio76 and so on. The Froyo stock roms also work fast and flawless. I know there is another thread but it is in another section and there are no responses because this sections has 100x more activity. THank you!
Click to expand...
Click to collapse
By the way, how long exactly did you give it? These HD Roms can literally take hours to settle in and they won't be real speedy until they are completely done syncing everything. I have noticed that sometimes you won't see the sync icon but things will still be syncing in the background, inlcuding the Android market because these new Roms backup all your apps and data with the market and HTC sense. I am using Sergio76's and it is flying so I would try again but give it a lot of time to settle. Hope it works out for you, good luck!
As Motoman said, it will take time for everything to sync, but many reboots is very important. I have been using Mdeejay's Desire HD 4.1 for three days now, and don't have any problems. I must have rebooted 8-10 times the original day and that helped extremely well with speed.
motoman234 said:
The class of the SD card has nothing to do with it. The majority or people that have tried a class 4 and above say it is a lot worse than the stock SD card. I have tried and it was a lot worse for me also.
The Windows ROM and radio can have a LOT to do with it though.
Click to expand...
Click to collapse
At worst a class 6 card (for example) might not provide much in the way of an improvement over a stock class 2 but there is no way it would be 'a lot worse'.
Personally, I noticed a speed increase on identical builds when I swapped from my class 2 to a class 6 but nothing too drastic.
motoman234 said:
By the way, how long exactly did you give it? These HD Roms can literally take hours to settle in and they won't be real speedy until they are completely done syncing everything. I have noticed that sometimes you won't see the sync icon but things will still be syncing in the background, inlcuding the Android market because these new Roms backup all your apps and data with the market and HTC sense. I am using Sergio76's and it is flying so I would try again but give it a lot of time to settle. Hope it works out for you, good luck!
Click to expand...
Click to collapse
I agree with motoman that sdcards have nothing to do with the speed they might make a very little difference which can be negligible, I am suffering from a lot of lag in desire HD builds............
@motoman234, so can you tell us how exactly we should install these desire hd roms ?,
i was having the same issue with the hd roms. i thought they were terrible. i now have MDJ FroYo HD v.4.3=-[kernel:MDJ S7.5HD] running very well. i had to change my rom to achieve this. the wmrom is useless IMO but it lets me run android hd now. i am using this rom
ChuckyDroidROM-HTCFrameworkEdition.Nov.05.7z
and this radio
Radio_Leo_2.15.50.14
i also install bsb tweaks in winmo and set to power save mode. turn off everything in winmo and auto boot to android with hard keys lit up.
it works for me
Same issue as OP here. All non-HD ROMs run really fast. But other Desire HD ROMs are plain terrible speed-wise. I have a good Class 6 card.
It's a kernel issue. There is nothing you can do.
Pagnell said:
At worst a class 6 card (for example) might not provide much in the way of an improvement over a stock class 2 but there is no way it would be 'a lot worse'.
Personally, I noticed a speed increase on identical builds when I swapped from my class 2 to a class 6 but nothing too drastic.
Click to expand...
Click to collapse
To each is own I suppose. I can only speak for myself when I say that a class 6 card made me have SOD every time when waking the phone from sleep, not to mention overall less performance. Not sure what it is about them but it was bad in my case but I doubt every single person will experience this.
vtec303 said:
I agree with motoman that sdcards have nothing to do with the speed they might make a very little difference which can be negligible, I am suffering from a lot of lag in desire HD builds............
@motoman234, so can you tell us how exactly we should install these desire hd roms ?,
Click to expand...
Click to collapse
It is a bit time consuming to get them rolling smooth for the first time but these are the steps I usually use when installing them for those of you that can not get them running like they should.
1) Boot up the build (fresh start)
2) Wait a couple minutes before unlocking the screen for the first time.
3) Setup everything in the SetupWizard.
4) From the moment you hit the "Finish" button on the SetupWizard, set your phone down for about 30-45 minutes before touching anything (OFF the charger if possible since it can get really hot when it is syncing everything for the first time. Charging can just add to that heat)
5) After you notice things to get a little faster, reboot the phone and then boot back into Android.
6) Wait another 5 minutes before unlocking the phone.
7) You should be good to go, if things still seem a little laggy try to reboot one more time.
I know this seems overboard but these HD builds have a lot to them. After you get the process over with you should be happy you did it. Once again **This is just what works for me** I am using Core Droid V0.2 by the way.
@Motoman234,
Not overboard...it's good advice. Thank you for the steps! P.S. Good to see a chef from my neck of the woods! Thank you sir!!
motoman234 said:
The class of the SD card has nothing to do with it. The majority or people that have tried a class 4 and above say it is a lot worse than the stock SD card. I have tried and it was a lot worse for me also.
The Windows ROM and radio can have a LOT to do with it though.
Click to expand...
Click to collapse
Pagnell said:
At worst a class 6 card (for example) might not provide much in the way of an improvement over a stock class 2 but there is no way it would be 'a lot worse'.
Personally, I noticed a speed increase on identical builds when I swapped from my class 2 to a class 6 but nothing too drastic.
Click to expand...
Click to collapse
The Speed of the SD card has nothing to do with the roms performance.
The only difference that we will feel between a 'Class 2' and a 'Class 6' is when copying files to or from the SD card.
I noticed that on my 16GB Class 2, I have a transfer rate up to 4 MB/s when copying the Android folder and this card is supposed to have a maximum of 2mb writing while on my 8GB Class 6 I can copy up to 10 Mb/s the same Android folder (twice as fast).
But when Android runs I don't feel any difference at all.
The reason why the Desire HD roms are slow on the HD2 is because these roms were optimized to work under 768 MB RAM while our HD2 has only 576 MB RAM.
We barely have 100MB of free RAM with a Desire HD rom but with a stock rom we can have 300MB and more free.
ForceField said:
The Speed of the SD card has nothing to do with the roms performance.
The only difference that we will feel between a 'Class 2' and a 'Class 6' is when copying files to or from the SD card.
I noticed that on my 16GB Class 2, I have a transfer rate up to 4 MB/s when copying the Android folder and this card is supposed to have a maximum of 2mb writing while on my 8GB Class 6 I can copy up to 10 Mb/s the same Android folder (twice as fast).
But when Android runs I don't feel any difference at all.
The reason why the Desire HD roms are slow on the HD2 is because these roms were optimized to work under 768 MB RAM while our HD2 has only 576 MB RAM.
We barely have 100MB of free RAM with a Desire HD rom but with a stock rom we can have 300MB and more free.
Click to expand...
Click to collapse
I think what makes it worse is that we dont get 576mb ram in android, as this has not been built into kernels, we are only getting about 350mb of ram. If I check my available ram it is around the 300mb mark and has never been above 350mb.
u must just reboot you device after 1-st boot
hookguy said:
I think what makes it worse is that we dont get 576mb ram in android, as this has not been built into kernels, we are only getting about 350mb of ram. If I check my available ram it is around the 300mb mark and has never been above 350mb.
Click to expand...
Click to collapse
Yes,the secret of having a good performance on any device is to have 1/3 of the amount of RAM always free.
For ex if you have 3GB of ram,you can use till 2GB and you will be very good.
But if you use 2.1 GB of the 3GB then don't think twice and upgrade immediately.
We are using this equation on our servers and t works pretty well,at least for our company.
I've only tested desire_hd beta and Core Droid HD v0.2 so far. Nonetheless, both have been quick and solid here. Like mentioned by motoman234, give these builds time to sync your market apps and settle down, then reboot a couple times, and you should be good to go. If the build has heavy lag, it's most likely still trying to download your market apps and install them as well as sync your personal data. Patience is key here.
Also, this goes for every build, but make sure that your keypad lights are on when booting into android. Doing this has normally solved any high standby battery drain that I've run into to date.
As far as MircoSDHC cards go, I have tested a handful of different class and size cards with the HD2, and found that once the system is booted up, there's no difference, or the higher class cards have more SOD or freeze issues for some reason. The HD2 can only handle so much, and random read speed appears to be the most important factor. In turn, a good quality class 2 card should be all you need. That said, I've been running a Sandisk 32GB class 2 card for months now, without a single problem to date. Regardless of what card you use, I highly recommend using SD Formatter in quick format mode.
Another thought... it may help a little to use a standard wallpaper at first, instead of the live wallpaper, just until the system has settled down.
All that said, I'm a huge fan of Core Droid HD, due to the animations and polished theme work done by Sergio76. It's an excellent build, and you can easily get the camcorder working with the system files fix included in the thread.
On a kind of related note, motoman234 has an excellent EVO Sense Black & Blue Remix build available, if the Desire HD Sense builds are too heavy for your needs.
Best to all,
R
Well said, thanks man.
motoman234 said:
Well said, thanks man.
Click to expand...
Click to collapse
Cheers motoman234! And... thank you so much for your excellent build work and help. To say the least, your EVO remix has been extra solid here.
Best to all,
R
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 guys,
I'm using this bulid for a while now, [25.FEB.11][CWM] RAFDROID HD 3.2|Fastest Full DesHD|DATA2EXT|[Rafpigna 1.7 OC] ,
and I'm sure most of y'all heard about it and maybe you are using it right now!
it is THE best DesireHD build out there,
...
well as it is clear from the title
my question is:
What would happen if I increased the data2ext3 partition to more than 1Gb?
because I love treating my HD2 like an iPhone and installing a lot of apps and I love games too
I have a 16gb class4 sandisk microsd card which turned out to be the most compatible sd with nandroid builds (bought based on your professional recommendations)
it has already a 1gb ext3 partion with 4b cluster size
can I make it more??
and whats the limit and why is there a limit?
THANKS
Grow a pair and just try it. Either it works or it doesn't.
well it kinda works but gives sometimes fc's on sense and phone apps
but I am afraid of any bugs that I as a new user wouldnt notice
and all the developers usually warn us about that
ok so my girlfriend got a nook color for christmas this year and heard you can put honeycomb on it. i did it and all went well BUT she has no market and i have no idea how to use adb and her nook isnt even recognized. i tried the easy adb usb nook installer thing and it wont work. now i tried to format my sd card to use as a regular 4gb card and i only have 117 mb left!!!! i have no way to fix it and i just bought it today from walmart. it was only 10 bucks so no big loss but still its 4gb i couldve used. is there any home to reformat correctly to get it back or any way to completely uninstall android sdk and adb and the drivers and redo it over and can anyone help me as to making the market work if possible? i installed the honeycomb image to the sd card so i dont ruin her nook and i dont plan on flashing honeycomb to the actual nook. i need help asap so please anyone on the website help me!!!!!!
sneakysnake16 said:
ok so my girlfriend got a nook color for christmas this year and heard you can put honeycomb on it. i did it and all went well BUT she has no market and i have no idea how to use adb and her nook isnt even recognized. i tried the easy adb usb nook installer thing and it wont work. now i tried to format my sd card to use as a regular 4gb card and i only have 117 mb left!!!! i have no way to fix it and i just bought it today from walmart. it was only 10 bucks so no big loss but still its 4gb i couldve used. is there any home to reformat correctly to get it back or any way to completely uninstall android sdk and adb and the drivers and redo it over and can anyone help me as to making the market work if possible? i installed the honeycomb image to the sd card so i dont ruin her nook and i dont plan on flashing honeycomb to the actual nook. i need help asap so please anyone on the website help me!!!!!!
Click to expand...
Click to collapse
You should do some more research. Honeycomb on the nook is no bueno. You can use gingerbread with no problems. ICS is being updated daily, still some things not working. To format your micro sd card you can use SD Formatter from Sandisk. Try cm7 on your sd card. Works great. My girlfriend has very few problems, she is very happy.
Sent from my Xoom using Tapatalk
Oh ok thanks for the info I fixed the sd card.she will be happy to hear it might work cause I explained to her how annoying it was... Now do I have to flash anything to the nook itself? And is there any way to restore it in case it messes up? If possible id like it all done on the sd card and I could get an 8gb easy, and I could try for a 16 if necessary. Thank you for the quick reply too really helped
Sent from my SGH-T959 using XDA Premium App
Honeycomb in general is a no-no. The Honeycomb ROM you got was based off of SDK. Google never officially released the Honeycomb source code. As for your problem, I'd need more info. You could always wipe your SD and go to Wal-Mart, asking for a trade-in. If they plug it in, act dumb and say it came that way. Go with the latest CM7 nightly. CM9 is in a rapid change state at the moment, so unless you can build a ROM based off of source, I'd wait until CM9 becomes stable. For now, look into the ROM that would suit her. MIUI is well-supported and sort of resembles iOS. CM7 is strictly Android. Phiremod is nice but is officially unsupported because its developer decided to leave his Android life. Hopefully, someone else takes the reigns from him. My suggestion for you for now is either CM7 or MIUI.
I used to have a forum signature... then I took an arrow to the knee.
sneakysnake16 said:
Oh ok thanks for the info I fixed the sd card.she will be happy to hear it might work cause I explained to her how annoying it was... Now do I have to flash anything to the nook itself? And is there any way to restore it in case it messes up? If possible id like it all done on the sd card and I could get an 8gb easy, and I could try for a 16 if necessary. Thank you for the quick reply too really helped
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
Personally I'd flash a ROM to the Nook. If you want to run CM7 completely off of SD, things get more complicated. For now, give her a ROM. If she likes the look of an iPod, go with MIUI. Otherwise, flash CM7 (the latest stable should do). Make a recovery after you flash and about once every week or so. I suggest getting an SD card for just recoveries. 2GB should do and when you need to delete old recoveries, just hook up to your computer, find the directory in your SD labeled "clockworkmod", open it, and delete the folders that hold the old recoveries. Most are named based on the date and time they were created.
I used to have a forum signature... then I took an arrow to the knee.
First, there is probably nothing wrong with your SD card as I think you have now found. When you make an install that is designed to run off the SD card the process partitions the card into various areas. Windows can only see the first partition which is the boot partition of 117 MB. Other partitions hold the system, data and "SD" areas and the Nook will see all of these and can mount the "SD" area as visible to the PC when connected by USB.
Various utilities are available to put the card back to a single full capacity partition. E.g. the HP utility or the Sandisk utility as mentioned.
I'd certainly follow the advice given on ROM selection. If you choose to use the CM7 type then the ROM build under the KANG MiRaGE thread is the best choice at the moment.
Although installing to emmc internal is nicer in many respects there are also lots of people here who have chosen to run on SD because they wanted to leave the Nook stock software unaltered. Providing you use a SanDisk card this will give good results, running fast and stable and does not alter the internal Nook software so you can just remove the card to get back to the standard Nook.
I started like this but then decided that I was never going to use the stock and eventually flashed into internal. For non-technical friends who want the CM7 experience on their Nook I normally use the SD card method as it then means they have an easy path back to a standard Nook.
If you want to run from the SD card then reformat your card back to full capacity, choose which ROM you want to use then follow the SD card install guide.
http://forum.xda-developers.com/showthread.php?t=1000957
Yea I used a sandisk card and I fixed mine thanks as for installing cm7 I would like it on the sd card becauae if she doesnt like it then idk how to return it to normal...
Sent from my SGH-T959 using XDA Premium App
bobtidey said:
http://forum.xda-developers.com/showthread.php?t=1000957
Click to expand...
Click to collapse
This ^^^. I have flashed cm7 to my gf's emmc, somehow, by accident in the past. I took it back to stock with the help of a thread in the dev section. Not a problem. It seems pretty hard to screw up her nook. She loves cm7 over stock. Actually, I used the cm7.2 kang. Runs really well on the sd card. If there is ever a problem, pull the sd card and start over. Always have current backups of apps/data. Good luck.
Sent from my Xoom using Tapatalk
ugh, I feel stupid, having the same issue with the sd card. Can someone gimme the link for the sd formatter? I tried the hp utility and it didnt change any thing. Thanx guys.
Actually, the stock B&N operating system has a nice SD card formatter. You just put in the SD card after turning on the Nook, go to Device Options from Settings, click on the SD card option, and you can format/wipe it from there.
Under Ubuntu, I use gparted.
For Windows, I don't know which one is the best, but when I had the same problem, I used MiniTool Partition Wizard
std5501 said:
ugh, I feel stupid, having the same issue with the sd card. Can someone gimme the link for the sd formatter? I tried the hp utility and it didnt change any thing. Thanx guys.
Click to expand...
Click to collapse
std5501 said:
ugh, I feel stupid, having the same issue with the sd card. Can someone gimme the link for the sd formatter? I tried the hp utility and it didnt change any thing. Thanx guys.
Click to expand...
Click to collapse
Use MiniTools Wizard
votinh said:
CM7 - nb230 on eMMC - Dalingrin's OC kernel 2.6.32.9 @ 1200MHz NOOKcolor
Click to expand...
Click to collapse
I can't help but notice you have it clocked to 1200MHz. No criticism, and it's purely your choice, but clocking to 1200MHz isn't actually... well, I guess the word is, "beneficial". Personally, I'm clocked to 1100MHz, and I'll tell you why. Clocking the Nook at 1200MHz makes it: 1) Overheat very easily, 2) Drain through battery like a b***ch, and 3) It has no noticeable increase in performance. I'm not the only one out there who has noticed this either. But I can't dictate you and make you change it. Just informing you that Dragons may be ahead of you. If you don't have any of those problems, then so be it. If I were to recommend my opinion for overclocking settings, I'd say 1100/1100 min/max set to interactive or interactiveX. It seems counter-intuitive, but I know of an article (for the life of me can't find the link, LeslieAnn posted the link in one of her replies to an LG Optimus V thread) where a developer did tests at different clocking settings. From his findings; overclocking is better than underclocking, minimum clock setting has a really miniscule effect on the idle power consumption, and setting min & max settings at the same step provides the most balanced power-performance ratio. Anyways, I'll look for the link and see if I can find it.
worldindo1 said:
I can't help but notice you have it clocked to 1200MHz. No criticism, and it's purely your choice, but clocking to 1200MHz isn't actually... well, I guess the word is, "beneficial". Personally, I'm clocked to 1100MHz, and I'll tell you why. Clocking the Nook at 1200MHz makes it: 1) Overheat very easily, 2) Drain through battery like a b***ch, and 3) It has no noticeable increase in performance. I'm not the only one out there who has noticed this either. But I can't dictate you and make you change it. Just informing you that Dragons may be ahead of you. If you don't have any of those problems, then so be it. If I were to recommend my opinion for overclocking settings, I'd say 1100/1100 min/max set to interactive or interactiveX. It seems counter-intuitive, but I know of an article (for the life of me can't find the link, LeslieAnn posted the link in one of her replies to an LG Optimus V thread) where a developer did tests at different clocking settings. From his findings; overclocking is better than underclocking, minimum clock setting has a really miniscule effect on the idle power consumption, and setting min & max settings at the same step provides the most balanced power-performance ratio. Anyways, I'll look for the link and see if I can find it.
Click to expand...
Click to collapse
You know what? I'm here to learn too so any new idea, new knowledge, ..... all are welcomed. Once again, thanks.
Just I thought that at one point, we, dev. concluded that 1200 is best, not 1100, not 1300. That's the reason why I set 1200. Personally I haven't set to anything else beside stock 800 and OC 1200.
Since you said so, I will set it to 1100 and see if any better.
Thanks again, m8
Just get a new sd card here for 8 bucks: http://www.dailysteals.com/
16 gb class 4.
Only good for today.
Go download EaseUS, the free trial. It helped me expand my 16gb sandisk to full capacity after I imaged the files I wanted. EaseUS got a great rating on CNET. I figured out what I needed to do without watching the tutorial video.
If only I could get my nook to actually boot now :/
The EaseUS tool works like a charm. Thanks for the info. I got my 16GB back now...
I messed up my 32GB Sandisk (4) sd card too. It crashed running CM7 (no idea why) and I tried to reformat it using mini as suggested and then reinstall CM7 on it. It would not reformat to FAT32! So, then I wiped it, which maybe was my mistake. Anyway, now I can see the card in mini but checking the properties I see that it's all f'd up. Basically I can't format it as anything, number of cylinders appears to have changed, etc, etc. I have no idea what I did to it! Obviously, my knowledge on this subject is limited. I've learned how to create partitions, define or extend them and so on but know very little about how these little buggers work.
Since it cost about $25 on sale I'd like to fix it, if possible. Anybody have any ideas about how to fix or where I can go to learn? Does this problem have to do with the master build? I see that option in mini but don't understand what it is!
Sorry for being so stupid. I bought a new 16GB card and successfully made a new CM7 sd and restored apps using TB and content from my PC (thank god I had the presence of mind to back that stuff up)! I sure would like the extra 16GB back though....no $$ in the budget for anything more than the 16GB I bought.
I know this is sort of wandering from the OP but since others were discussing f'd up cards (albeit more easily repaired) I thought it would be ok. Feel free administrator, to redirect me if I should start new thread in Q&A. I did surf there and ran a global search of the NT threads and this was the best of four pertinent threads I found.
Snooch
Sent from my Nook Tablet using xda app-developers app
But this is a nook color thread.
Everyone here uses burning software to put bootable NC images on the device and it fixes it. Not sure if such things exist on the NT. Best to search there.
I'ver got EU HTC HD2 and want to install Paranoid-AOKP-JellyBean. As you can see there are 2 versions of this interesting ROM:
NAND: http://forum.xda-developers.com/showthread.php?t=1817793
and
SD: http://forum.xda-developers.com/showthread.php?t=1793180
It's written elsewhere SD Androids can be used as dual-boot together with WindowsMobile (or with WP). It sounds perfect but there should be a price for this. That's why please explain me what is the superiority of NAND version of this Paranoid (and of all NANDs in general)? Thank you!
NAND = faster than SD but limited space fo apps, use link2sd/ap2sd or the like
SD = almost on par with nand but sometimes can slow down, Big storage for apps
i use both NAND & SD to boot Andy
Thanks for clarifying this. I always wondered the difference as well.
And to make sure
NAND is limited built in memory but stable
Sd is greater space but isn't always as stable because of class? Or is there another reason for that?
Sent from my SGH-T999 using Tapatalk 2
I "guess" the class doesn't have much impact since that speed is mostly for READ/ Wite/ Copy, I used both class 4 & class 10 & sometime I find that the class 4 is even more stable.
SD could be slower/ unstable might be because it needs to access some data/ memory & fetching could cause some mishaps - i guess :silly:
I use SD Android for over a year and truth is, since few months I didn't found any fast and stable build like those on NAND. Well, maybe on Gingerbread there were few ones that worked well, but since ICS was announced there always been some problems.
rexx87 said:
I use SD Android for over a year and truth is, since few months I didn't found any fast and stable build like those on NAND. Well, maybe on Gingerbread there were few ones that worked well, but since ICS was announced there always been some problems.
Click to expand...
Click to collapse
thats true but there is a few roms works fine.
rexx87 said:
I use SD Android for over a year and truth is, since few months I didn't found any fast and stable build like those on NAND. Well, maybe on Gingerbread there were few ones that worked well, but since ICS was announced there always been some problems.
Click to expand...
Click to collapse
i have only experience of darkstone superram froyo on SD, never tried NAND, but i've been amazed with how fast and stable that is.
i only installed it recently to get wifi tethering with my blackberry playbook but if i'd known how good it was going to be and how easy to set up i would have installed it ages ago.
the fact that i can revert to winMo at any time by rebooting makes it a no-brainer.
SD Android might be unstable because most SD cards aren't used to have such a high load all the time and often they end up with data corruption, so chkdsk every week gets into your routine. That makes NAND ROMs superior to SD ones.
prosecutor55555 said:
thats true but there is a few roms works fine.
Click to expand...
Click to collapse
Maybe, but it doesn’t change the fact that NAND is still better choice than SD.
mengfei said:
SD could be slower/ unstable might be because it needs to access some data/ memory & fetching could cause some mishaps - i guess :silly:
Click to expand...
Click to collapse
However the main concern reported elsewhere was these SD Androids consumed much more energy so this resulted in quick battery drain. Would you confirm those reports?
Spaqin said:
SD Android might be unstable because most SD cards aren't used to have such a high load all the time and often they end up with data corruption, so chkdsk every week gets into your routine. That makes NAND ROMs superior to SD ones.
Click to expand...
Click to collapse
So then what about NAND ROMs with scripts like Apps2SD? If you move most your apps into SD card then won't they exert too much load on SD card too?
prosecutor55555 said:
thats true but there is a few roms works fine.
Click to expand...
Click to collapse
Is Paranoid-jellybean also among them?
Other question: it seems SD ROMs save NAND memory since elsewhere it's reported NAND memory wore too, especially under intensive writes, so maybe would the SD ROMs be the remedy? How do you think?
Please use the multi-quote feature rather than triple posting.
ioy said:
However the main concern reported elsewhere was these SD Androids consumed much more energy so this resulted in quick battery drain. Would you confirm those reports?
Click to expand...
Click to collapse
SD Android drains battery faster than NAND Android, yes.
ioy said:
So then what about NAND ROMs with scripts like Apps2SD? If you move most your apps into SD card then won't they exert too much load on SD card too?
Click to expand...
Click to collapse
TBH I've used both forms of Android and neither seems to have exerted strain on my SD card very much. At the very least, my SD still appears with the same amount of storage it originally came with.
ioy said:
Is Paranoid-jellybean also among them?
Other question: it seems SD ROMs save NAND memory since elsewhere it's reported NAND memory wore too, especially under intensive writes, so maybe would the SD ROMs be the remedy? How do you think?
Click to expand...
Click to collapse
Correct, repeated writing of the NAND (especially for those people who think Task29 helps when it doesn't) can cause bad blocks which cannot be written to and eventually may make the phone unusable. However, having done a fair amount of flashing my phone I don't think I have many bad blocks. If I do, then they haven't actually affected me yet (i.e. I can use the recommended /system partition without having to account for extra space from the bad blocks).
Nigeldg said:
Please use the multi-quote feature rather than triple posting.
SD Android drains battery faster than NAND Android, yes.
TBH I've used both forms of Android and neither seems to have exerted strain on my SD card very much. At the very least, my SD still appears with the same amount of storage it originally came with.
Correct, repeated writing of the NAND (especially for those people who think Task29 helps when it doesn't) can cause bad blocks which cannot be written to and eventually may make the phone unusable. However, having done a fair amount of flashing my phone I don't think I have many bad blocks. If I do, then they haven't actually affected me yet (i.e. I can use the recommended /system partition without having to account for extra space from the bad blocks).
Click to expand...
Click to collapse
Hi.
So that means flashing to NAND is limited? And it's better to use SD ROM's. How do I find out if and when the NAND becomes bad blocks.
Thank you.
Sent from my NexusHD2 using xda premium
halninekay said:
Hi.
So that means flashing to NAND is limited? And it's better to use SD ROM's. How do I find out if and when the NAND becomes bad blocks.
Thank you.
Sent from my NexusHD2 using xda premium
Click to expand...
Click to collapse
Why not Google/forum search that? And when you say limited, you mean that there's a limit to the number of times you can flash, right? Well if there is one it's incredibly high, and it certainly isn't better to use SD ROMs as they're much slower and consume more battery.
Nigeldg said:
Why not Google/forum search that? And when you say limited, you mean that there's a limit to the number of times you can flash, right? Well if there is one it's incredibly high, and it certainly isn't better to use SD ROMs as they're much slower and consume more battery.
Click to expand...
Click to collapse
Okay,
Thank you very much.
Sent from my NexusHD2 using xda premium
Thanx!!
Nand is much faster as it uses the ram rather than having to read the SD card and then put it into the ram so speed is visibly slower. I use a nand ROM but with a2sd support. That wat you get the speed of a nand ROM but the app space of an SD ROM.. best of both
Sent from my HTC HD2 using xda app-developers app