Is there a solution for the problem of music stuttering?
Don't just blame me for creating this thread.
I have asked this question for a solution in many threads.
Some said that it was a SD card problem with incorrect allocation size or cluster size.
I tried formatting my memory card from the cmd prompt with the following command-
format f: /fs:FAT32 /a:32K
But even after doing this I found no change in the issue.
I even did this with my other 2 SD cards, But the result is same.
I am using the stock 8gb Transcend microsd card got it with my HTC HD2.
I don't know its class details.
While, with the same evo builds, I have tried using the Nexus based Kernel, which resolves this issue but with sound very low.
Can some one help me to get out of my problem!
Thank you.
I think no one wants make a reply in this thread
shree.cse said:
Is there a solution for the problem of music stuttering?
Don't just blame me for creating this thread.
I have asked this question for a solution in many threads.
Some said that it was a SD card problem with incorrect allocation size or cluster size.
I tried formatting my memory card from the cmd prompt with the following command-
format f: /fs:FAT32 /a:32K
But even after doing this I found no change in the issue.
I even did this with my other 2 SD cards, But the result is same.
I am using the stock 8gb Transcend microsd card got it with my HTC HD2.
I don't know its class details.
While, with the same evo builds, I have tried using the Nexus based Kernel, which resolves this issue but with sound very low.
Can some one help me to get out of my problem!
Thank you.
Click to expand...
Click to collapse
Hi...I experienced that situation before. What I do is revert back to nexus kernel...
I think there is nothing to do with SD card, it is the stability problem of evo kernel since it is still in its premature stage.
Hope this help...cheers...
sylau90 said:
Hi...I experienced that situation before. What I do is revert back to nexus kernel...
I think there is nothing to do with SD card, it is the stability problem of evo kernel since it is still in its premature stage.
Hope this help...cheers...
Click to expand...
Click to collapse
Thank you, But a day back I too just thought as you.
Here is the response I got for asking this question in mdeejay desire Hd 3.3a thread.
Originally Posted by shree.cse
SIMPLY DON'T REPLY AS THE PROBLEM WITH SD FORMATTING.
I tried it but it wasn't resolved.
Actually the problem is with kernel under Evo tree only.
Why because I came with a solution now,
I am now using stock nexus one based kernel out on 13th sep with this desire hd 3.3a. Now I don't have any kind of music stuttering.
Try once.
Correct me if I was wrong.
Sent from my Desire HD
Originally Posted by krat0s123
well i'm sorry but you are very wrong.. believe me.. i've had this same discussion with one of the members here on hastarin's kernel thread.. i told him that the problem is with the microSD card in general.. meaning it could be the way the card is formatted (wrong cluster size or allocation unit size) or just the microSD card itself is having problem.. he had the same reasoning as you, where he said that it only happens on one kernel and fine with the others.. so i pointed out to him that if the problem was indeed with the kernel, you will see a lot of people complaining about the same thing and not just a few which would be addressed by the dev (hence the reason for changelogs).. so what he did is he tried 6 different microSD cards (yes six) and found that one of the microSD card is working perfectly while the others are having stuttering issues.. so what he did is he tried playing with different cluster sizes when formatting the other cards and have had success with them.. another thing is, if you look around on every builds that came out right now, a lot of people are starting to complain about stuttering.. not with the kernel but even on different builds (CM, froyosense, Evo and desire).. so i advice you try the same thing.. try to find a card lying around and install the same build/kernel with them.. and come back with the result..
Finally, I came to a conclusion.
That this problem is really not with SD cards or builds, this is truly the problem of the latest EVO based kernels.
Why I came to this conclusion, I have tried each and every kernel released from 13th sep to till date. I found the problem is gone with all the nexus based kernels.
shree.cse said:
Finally, I came to a conclusion.
That this problem is really not with SD cards or builds, this is truly the problem of the latest EVO based kernels.
Why I came to this conclusion, I have tried each and every kernel released from 13th sep to till date. I found the problem is gone with all the nexus based kernels.
Click to expand...
Click to collapse
idd I also have this problem.
HectiQ said:
idd I also have this problem.
Click to expand...
Click to collapse
Have you Formatted your SD card and tested after doing that?
I'm getting this too, i have tried different cluster sizes and they have offered some improvement however there is the occasional stutter. Some people's logic that as it only happens on certain cards, the card must be the problem is clearly wrong. Surely if that card worked fine with the nexus kernel then it is infact the evo kernel tree causing this issue.
Dude,i tested like 10 different cards,and believe me,brand is the magic word,not class.....take a sandisk ultra 8 gb class 6 with 64 clustersize....no lag or stuttering,my adata,kingston class 6 stutters,how do you explain that? Well i can,my sandisk does 18-20mb/s and the other 2 10-12 mb/s......you do the matt....
Jack E said:
I'm getting this too, i have tried different cluster sizes and they have offered some improvement however there is the occasional stutter. Some people's logic that as it only happens on certain cards, the card must be the problem is clearly wrong. Surely if that card worked fine with the nexus kernel then it is infact the evo kernel tree causing this issue.
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
It may be due to brand, however I also have a class 6 sandisk card, but surely that is irrelevant as the problem is kernel specific. Why would a card that works perfectly fine with the nexus kernels have problems with kernels based off the evo tree, would seem that the kernel is at fault. Also why would music stutter when you would need a read speed of less than 1MB/second to play a track with a bitrate of 320Kb/second... you do the math and don't insult my intelligence.
edit: I'm also using the 64KB cluster size.
Surely then in this case the EVO kernels have a severe problem with reading SD cards. It's not normal having to format the cards like that to be able to listen to music.
Jack E said:
It may be due to brand, however I also have a class 6 sandisk card, but surely that is irrelevant as the problem is kernel specific. Why would a card that works perfectly fine with the nexus kernels have problems with kernels based off the evo tree, would seem that the kernel is at fault. Also why would music stutter when you would need a read speed of less than 1MB/second to play a track with a bitrate of 320Kb/second... you do the math and don't insult my intelligence.
edit: I'm also using the 64KB cluster size.
Click to expand...
Click to collapse
Hey dude! You are 100% correct.
I tried with different cluster sizes but my system doesn't supports to format my SD card with 64k cluster size.
It's the time for the developers to concentrate on the EVO KERNELS other than blaming the user's SD card.
Sent from my Desire HD
I use an evo kernal and i get slight and minor skips when using the stock music app.
I dont get skips ands stutters when I use a different music app like rockbox.
I am not saying this will work for everyone. Its just what I do and It works fine for me
There must be something wrong, but I think it's more ROM specific than just the kernal. I had lots of problems with stuttering when using the Desire HD build. I've now changed to FroyoStone 3.1 which uses the EVO kernal tree and never had a problem. BTW I haven't formatted my SD card in about 6 months so I can't see how the problem can come and go if it was caused by that.
crazyman1 said:
There must be something wrong, but I think it's more ROM specific than just the kernal. I had lots of problems with stuttering when using the Desire HD build. I've now changed to FroyoStone 3.1 which uses the EVO kernal tree and never had a problem. BTW I haven't formatted my SD card in about 6 months so I can't see how the problem can come and go if it was caused by that.
Click to expand...
Click to collapse
May be, but I haven't tried the froyostone sense 3.1 build. So, that I can't say anymore.
But I tried all the rest of the Evo builds and sense builds and Desire HD builds of Mdeejay, Sergio and Darkstone.
I am having this problem more or less.
But while changing to the nexus based kernel the problem completely went off. that's why I made this conclusion.
I'll try froyostone 3.1 and report you back.
Thank you
Sent from my Desire HD
hazard99 said:
I use an evo kernal and i get slight and minor skips when using the stock music app.
I dont get skips ands stutters when I use a different music app like rockbox.
I am not saying this will work for everyone. Its just what I do and It works fine for me
Click to expand...
Click to collapse
Where can I get this app, I searched with the keyword on market. No result found.
Can you please send me the link.
Sent from my Desire HD
The link I found is now dead as confirmed by another user. I would suggest Google search
Sent from my HTC HD2 Decepticon using XDA App
i don't have this issue. using a samsung class 6 8gb card if it matters
shree.cse said:
Is there a solution for the problem of music stuttering?
Don't just blame me for creating this thread.
I have asked this question for a solution in many threads.
Some said that it was a SD card problem with incorrect allocation size or cluster size.
I tried formatting my memory card from the cmd prompt with the following command-
format f: /fs:FAT32 /a:32K
But even after doing this I found no change in the issue.
I even did this with my other 2 SD cards, But the result is same.
I am using the stock 8gb Transcend microsd card got it with my HTC HD2.
I don't know its class details.
While, with the same evo builds, I have tried using the Nexus based Kernel, which resolves this issue but with sound very low.
Can some one help me to get out of my problem!
Thank you.
Click to expand...
Click to collapse
I have to agree that the card can be the most likely cause for the stuttering. That isn't to say it is in your case, though. But, from my own recent experience, the card was the culprit of stuttering in one of my eVo-based builds. I was using the 16GB Sandisk Class 2 card that came with my HD2 and had serious stuttering. I switched over to an 8GB Sandisk class 4 card and the stuttering vanished. The build worked smoothly and the music played smoothly.
I don't think we are denying that it is occurring with certain cards, more stating that this issue shouldn't be happening and needs to be fixed rather than ignored by kernel devs.
Related
I noticed that a LOT of people on these Android Development threads are complaining of a "black SOD" they receive even AFTER reformatting their SD cards and reinstalling everything properly. Basically this is an SOD except the screen backlight is on but there aren't any icons.. Similar to the back-lit screen you see before the unlock screen appears, except the phone isn't locked (sometimes, it is).
I noticed this problem when I first started using Android, and let me tell you, it was quite frustrating!! I tried everything. All different WinMo ROMS, multiple Android ROMs, radios; you name it, and I probably tried it. Until one day...
... I finally came upon the solution: the SD card!! For some reason, I wanted to try out a different SD card other than the stock 16GB one. I don't exactly remember the thread or the URL, but I do recall reading a bit of info that helped lead to this conclusion. For me, I switched to the 2GB from my BlackBerry and haven't had one single "black SOD" since that change.
I am posting this thread in the development forum because I constantly see people with the same frustration.. Which in turn leads to them blaming the build itself. I urge the dev's to post a note in their threads with this solution, as it will help diminish unnecessary bickering/bashing/posting that these dev's must deal with regarding this issue. Also, I am posting it here because I tried MULTIPLE 'Droid builds and this was the only solution that worked for me.
Let me know if this helps anybody with their dreaded black SOD!! And a big thank you to all the dev's for their extraordinary hard work and dedication in bringing the amazing Android OS to our beloved HD2's.
maff1989 said:
I noticed that a LOT of people on these Android Development threads are complaining of a "black SOD" they receive even AFTER reformatting their SD cards and reinstalling everything properly. Basically this is an SOD except the screen backlight is on but there aren't any icons.. Similar to the back-lit screen you see before the unlock screen appears, except the phone isn't locked (sometimes, it is).
I noticed this problem when I first started using Android, and let me tell you, it was quite frustrating!! I tried everything. All different WinMo ROMS, multiple Android ROMs, radios; you name it, and I probably tried it. Until one day...
... I finally came upon the solution: the SD card!! For some reason, I wanted to try out a different SD card other than the stock 16GB one. I don't exactly remember the thread or the URL, but I do recall reading a bit of info that helped lead to this conclusion. For me, I switched to the 2GB from my BlackBerry and haven't had one single "black SOD" since that change.
I am posting this thread in the development forum because I constantly see people with the same frustration.. Which in turn leads to them blaming the build itself. I urge the dev's to post a note in their threads with this solution, as it will help diminish unnecessary bickering/bashing/posting that these dev's must deal with regarding this issue. Also, I am posting it here because I tried MULTIPLE 'Droid builds and this was the only solution that worked for me.
Let me know if this helps anybody with their dreaded black SOD!! And a big thank you to all the dev's for their extraordinary hard work and dedication in bringing the amazing Android OS to our beloved HD2's.
Click to expand...
Click to collapse
+1... and i believe it's not just the SOD that our SD card is causing.. even the music stuttering, which some people are blaming the problem with the build, kernel and now the enabling of stagefright.. it's not consistent as only some people would have certain issues while most others don't.. i myself have fixed the SOD and music stuttering by replacing the sd card or just by simply fomatting the card.. so i think until we run the full Android on NAND, we would see a lot of incosistencies on the issue of the builds.. unless of course if the problem was something like "camera" for the desire HD build doesn't work.. that you can blame on the kernel as everyone has the same problem therefore consistency on the issue..
I already knew that it was the sd card. Since I never had any sod since august 1. (Started android using there)
I have been getting these alot recently. But it doesnt seem to be the SDcard for me. I can play music just fine without any stuttering. Im also been sufferring alot from touch screen freezes which is at its worst when walking on foot, yet its not so bad when on the move in a vehicle. strange.
+1 for me too.
Had exactly the same with an 8gb SD card but, since switching to a 4gb SD card, I've had no issues whatsoever. All my WINMO and Android installs work straight away with the new card but the Android especially would, 90% of the time, fail to load up on the larger card!
I currently have a temporary black and white sod, but it boots through.
I've got this Black-SOD only in Mdeejay Froyo NextSense 2.5. (No Wake up from Stand-By).
In Versions 2.1 to 2.4.2 are no BlackSod's for me.
I'm using a Kingston 16gbc10.
hey i too had the problem with SOD. i got it all fixed by changing the radio version to 12.50 it works fine i wouldnt blame the poor SD card btw what can u do wit a 2gb sd card... useless
i just replaced my stock TMOUS sd card and put in a 4gb card and loaded the Core Droid 0.5 and it seems to be working fine ( fingers crossed ), no SODs. And i'm also looking at low power consumption as well. Thank God.
pillai.raul said:
hey i too had the problem with SOD. i got it all fixed by changing the radio version to 12.50 it works fine i wouldnt blame the poor SD card btw what can u do wit a 2gb sd card... useless
Click to expand...
Click to collapse
The 2GB I'm using was mainly for testing purposes.. but I'm still using it until I can buy a larger one. Better to have little space with a working build, eh?
Well I'm not sure one way or another about the black screen SOD, but I am sure that the "skipping" is not related to the sdcard. Some cards, faster ones, seem to do it a lot less (I currently have 7 sd cards, different sizes, speeds, and makes, and have had some downtime at work so I did a bit of testing), but they do it on the evo kernels. Disabling stagefright does work, but it causes other issues with video, so i wouldn't suggest it.
Turn off auto-brightness it will disappear
Sent from my HTC HD2 using XDA App
I just performed a little experiment.
Bangsters 1.5, fresh install on my 16gb class 4... SOD present, hard.
Copied the contents of the card to my 2gb card... no SOD. can rapidly sleep\wake phone with no issues at all.
*sigh*
I have narrowed down Wake-up death screens to two Apps actually since I had no other MicroSD cards to test out...
AutoKiller - any preset you choose you will get SOD (wake-up SOD) - I don't use it anymore and no SODs (this may be actually MicroSD card as all those apps are on it lol);
Ummmm forgot the other one - URGH ... wait ... can't remember now ... once I do I will update my post...
I fixed my SOD problem by updating kernels. The one working for me now is the netripper nexus oct 8 one. I'm on TMO stock and Shubcraft 1.5
fflakes said:
I fixed my SOD problem by updating kernels. The one working for me now is the netripper nexus oct 8 one. I'm on TMO stock and Shubcraft 1.5
Click to expand...
Click to collapse
can you describe where to get, and\or how to upgrade to this?
Here is my solve
I have been experimenting with these Android builds sine day one. I saw many SOD's for the first few months though haven't seen one yet since I replaced my SD. Went from stock TMOUS 16GB Class ? to a Adata 4GB Class 4. I try a new build almost 3 times a week and since seen no SOD's. Now, my SOD's previously would appear normally under heavy loads or wake/sleep. I have had different WM ROM's and Radio's during this process so I dont think its due to the WM build present in the phone.
Im now running the latest eleg WM build and the HyperDroid latest Android build. Great simple non-sense Shub/CM based ROM with no issues. Definitely a daily user. Oh, and i keep my auto brightness on.
I will say i did see one SOD during trying a new EVO based ROM. But, i tried the "hold phone up to light bulb" and the display came right back. I dont know this is the ABSOLUTE remedy to this issue, but worth a try. I changed to a different ROM immediately though because that one had some data issues...But other than that I can say im completely satisfied with using android as a daily and not returning back to WinMo anytime soon.
...Thanks Dev's
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
Hi!
I know i'm not alone having this reboots, maybe we can help the developers by ruling out the SD card... or some SD cards...
Would be interesting to know who have had no reboots at all and what SD card brand they have.
Can as many as possible post their SD card:
Brand
Class
Size
I use a Kingston 8 GB class 6 and are having the reboots on every build i have ever tried. It does not matter who has made it.
Sandisk 4GB class 2. No reeboots. Works great for everyday use.
I have freeze and have to do hard restart only when i play games for 30 minutes (overheat).
Kingston 4GB class 4. I never had reeboots. I use Mdeejay builds and works just great!
denyboy said:
Sandisk 4GB class 2. No reeboots. Works great for everyday use.
I have freeze and have to do hard restart only when i play games for 30 minutes (overheat).
Click to expand...
Click to collapse
im exchanging my hd2 for a new one due to this issu
Transcend 8GB class 6. No reeboots. Works great for everyday use
16gb sandisc class 2
i have rare random reboots; mostly at nights while charging
1 x 8gb Transcend Class 6
1 x 8gb Sandisk Class 2
Using JDMS 1.6 ~ no freeze no reboot, loving it
16gb sandisc class 2
no reboots
Sandisk 8gb class 2.. no reboots whatsoever..
However i dont think these reboot issues are related to sd cards (unless maybe the cards themselves have a problem due to prolonged use or other factors)
I would advise to try formatting ur card on a pc (using a card reader if possible) and then formatting it while in winmo 6.5 (using the htc formatting application found in a stock htc hd2 rom)..
then try out any new build, without changing the kernel, and without overclocking (this can cause issues)
after this procedure, if all doesnt go well, then we can rule out that hardware is the prob (either card or phone)
oh n by the way, during this testing procedure, if possible, flash a t-mo US 3.14 rom (together with radio) using pc of course to keep ur hardspl from being overwritten..
@denyboy
try underclocking ur cpu, less or equal to 768mhz (some desirehd builds apart from mdj's revolution hd build become very slow when below 768)
this should keep the temp less than or equal to approx 40 degrees Celcius (that is if your not plugged in to charger and not in direct sunlight )
i have just changed from a sandisk 2gb to a kingston 8gb class 4. i was happily using a desire hd build and it was running brilliantly. the build doesnt like the kingston card though. i lags terribly so ive gone back to the 2gb for now.
jjblaster3 said:
Sandisk 8gb class 2.. no reboots whatsoever..
However i dont think these reboot issues are related to sd cards (unless maybe the cards themselves have a problem due to prolonged use or other factors)
I would advise to try formatting ur card on a pc (using a card reader if possible) and then formatting it while in winmo 6.5 (using the htc formatting application found in a stock htc hd2 rom)..
then try out any new build, without changing the kernel, and without overclocking (this can cause issues)
after this procedure, if all doesnt go well, then we can rule out that hardware is the prob (either card or phone)
oh n by the way, during this testing procedure, if possible, flash a t-mo US 3.14 rom (together with radio) using pc of course to keep ur hardspl from being overwritten..
@denyboy
try underclocking ur cpu, less or equal to 768mhz (some desirehd builds apart from mdj's revolution hd build become very slow when below 768)
this should keep the temp less than or equal to approx 40 degrees Celcius (that is if your not plugged in to charger and not in direct sunlight )
Click to expand...
Click to collapse
Hi!
I'm doing a PC format and then a WinMo formating tool everytime i try a new rom. And i have no plans on overclocking at all I would like a kernal that's not over/under-clocked. But i have not found any.
SO, maybe it's my card or my phone. Will try the latest Artemis that is now Android supported (what ever that is) And then maybe i can use Android without any reboots as well...
I can stress my device with gaming and the temp is about 40-41 degrees without any reboots. Then the device can lay on my table without any use at all and suddenly reboots itself... very strange i think. I can buy the reboots when stressing the device (since this Android stuff is not for our HD2's) but when not using them.... nah...
Thank you for your reply!
I had random reboots on the 16gb class 2 that comes with the TMOUS phone and with a Kingston Class 4 8gb.
I don't think it is the card, it seems to have to do with the build/kernel. I never get reboots when running either shubcraft or michyprima's CM6 builds. I always get them when I run M-deejays and the topia series builds.
Stock TMOUS 16gb Sandisk Class 2 card. No crash or reboots. Many builds, many kernels.
Try
Darkstone's SuperRAM FroYo build as it puts system in ram, less stress on memory card.
anap40 said:
I had random reboots on the 16gb class 2 that comes with the TMOUS phone and with a Kingston Class 4 8gb.
I don't think it is the card, it seems to have to do with the build/kernel. I never get reboots when running either shubcraft or michyprima's CM6 builds. I always get them when I run M-deejays and the topia series builds.
Click to expand...
Click to collapse
Can't find "michyprima's CM6"? Is that a kernal or a rom build?
Karcus said:
Stock TMOUS 16gb Sandisk Class 2 card. No crash or reboots. Many builds, many kernels.
Try
Darkstone's SuperRAM FroYo build as it puts system in ram, less stress on memory card.
Click to expand...
Click to collapse
I must have the sense version thanks though!
Don't worry Darkstone is working on Sense version so it will be fine later on.
Karcus said:
Don't worry Darkstone is working on Sense version so it will be fine later on.
Click to expand...
Click to collapse
WHAT? are you saying Is he? Thought he left the scene....???!!!
Good news VERY good news, i have found his rom's very stable and good to me.
I'm just putting on mdeejays latest Desire HD version!
I have reboots only when using Sense/Sense HD builds (every few hours). It reboots automatically while the phone is IDLE regardless of the kernel. I don't overclock and the phone cannot be overheating since it reboots when it's idle.
I am now using tytung's NexusHD2 and I haven't a reboot in an entire week. Using a Sandisk 16Gb Class 2. I've been looking around for ages but haven't been able to figure out what could be causing this since it seems to a unique issue. Any ideas?
ToddeSwe said:
Can't find "michyprima's CM6"? Is that a kernal or a rom build?
Click to expand...
Click to collapse
It hasn't been updated in a little while, but this is still my everyday build that I use
http://forum.xda-developers.com/showthread.php?t=824601
PNY 16 GB no re-boots
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.
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...