Database Users

[Q] Music stuttering with EVO based kernel builds.

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.

[ALL BUILDS] Having problems with a "black SOD"?

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

Desire HD roms are slow on my HD2

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

CM7 woes

Long story, short (can be made longer as needed), CM7 snowballs into a bunch of force closes. I have a 16 GB PNY and the write, read speed is fine and quadrant scores are above a Nexus S. I used the verygreen method of rooting and have tried the latest nightly then went back with the latest stable but it makes no difference. It all starts with a force close on android.media.process force close and then I get random force closes on things I am not using and on market and kindle till its nearly unuseable. Perhaps it is how I am wiping the micro sd to start over? I use Minitool partition manager and delete all the partitions then create a fat 32 partition then I use windows 7 to quick format to defaults. Suggestions please. I don't sync it to my phone profile and all the apps.

dejavecu said:
Long story, short (can be made longer as needed), CM7 snowballs into a bunch of force closes. I have a 16 GB PNY and the write, read speed is fine and quadrant scores are above a Nexus S. I used the verygreen method of rooting and have tried the latest nightly then went back with the latest stable but it makes no difference. It all starts with a force close on android.media.process force close and then I get random force closes on things I am not using and on market and kindle till its nearly unuseable. Perhaps it is how I am wiping the micro sd to start over? I use Minitool partition manager and delete all the partitions then create a fat 32 partition then I use windows 7 to quick format to defaults. Suggestions please. I don't sync it to my phone profile and all the apps.
Click to expand...
Click to collapse
Dammit, hit thanks instead of quote by accident.
Anyway, the read speed is not the critical benchmark for uSD cards if running CM7 off it. There's a thread in general regarding this, but it's the small writes that matter most. The general consensus seems to be that Sandisk class 4 or 2 cards perform the best (on average, quality can vary between cards of the same brand/model) out of those out there.
Try using Easus Partition Manager to repartition and format fat32, 8k clusters (for a 16GB card) -- also if you're using a built-in card reader or connecting an external one to a front port on your PC it can cause some weird issues.
You can also try, if you have a second uSD, creating a bootable CWR card, boot into it, swap uSD out for your system card, run fix permissions and reboot (someone correct me if this won't work, afaik it does).

I'm still getting a lot of force closes but with some I chose to click wait instead of force close and then it will work. I'm going to.be aggravated if after all this time it s the sd card. Any cm7 tweaks to.make it more stable?
Sent from my SGH-T959 using XDA App

The best bet for you at this point is to get a Sandisk 8GB class 2/4 microSD from Amazon for around $11.00 including shipping.
(Please note that we are not associated with Amazon in any way.)
We can not emphasize how important it is to have a good disk.
A lot of FC can be avoided at least from my point of view.
Good luck.

If you dont want to wait for shipping, i think staples is have a fathers day sale for 15 dollars of something for a sandisk 8GB class 4

What about a 16 gb?
Sent from my SGH-T959 using XDA App

Also it never will boot in recovery mode. it simply installs the gasps then I power it on again
Sent from my SGH-T959 using XDA App

With verygreen's size-agnostic thing, I've yet to see any bootloader per se. It's this magical thing that when you say "boot to recovery", all it does is run any ZIP that's named "cm-" something, or "update-" something. (Also gapps).
I don't see any menuing like AMONRA or CWM.
I'm using a 8GB class 6 that performs just fine, without any issues (as a point of reference). I also have a 4GB class 4 that ran well, too - albeit a bit slower.
I think when you get above class 6 is when it gets more flakey on the small read/writes.
I used verygreen's size-agnostic installer, coupled with the Win32 imager. Essentially followed Quinxy's easy-to-understand steps here (ignoring him telling you to grab cm7-0-0.zip, the write-up is old - get either the latest nightly or the latest stable -- the 107 nightly worked great for me, 106 didn't have root, so don't ever get that one).
http://quinxy.com/2011/04/01/comple...on-the-nook-color/comment-page-3/#comment-944

I'm running CM7 nightly 107 with Dalingrin's 6-18 kernel on a 16 GB Sandisk class 4 I got from Radio Shack last weekend for $25 (it was on sale). It is rock solid.
Also was running cm7 7.0.3 stable on a Sandisk class 4 8GB stick and that ran rock solid also. I've been using Sandisk mini and micro SD chips in my phones for years and never had a bad experience yet. If it ain't broke, don't fix it...

laggy, choppy, slow response?

Hey guys,
I just dual booted my hd2, super fruit 7.5 and cm9 ics nexus SD build, and I don't know if its just me, or if I was expecting too much, but the android portion is very laggy and slow to respond. Even typing is slow and laggy. Is this just me expecting too much from an Sd build? Or is there maybe something I did wrong?
Spl 2.08
Radio 2.15.50.14
Maglrd 1.13
SD card 32 gb sandisk mobile ultra class i

And Also when in windows, the earpice and speakerphone volumes are extremely low even when turned up to max.

TripleP46 said:
Hey guys,
I just dual booted my hd2, super fruit 7.5 and cm9 ics nexus SD build, and I don't know if its just me, or if I was expecting too much, but the android portion is very laggy and slow to respond. Even typing is slow and laggy. Is this just me expecting too much from an Sd build? Or is there maybe something I did wrong?
Spl 2.08
Radio 2.15.50.14
Maglrd 1.13
SD card 32 gb sandisk mobile ultra class i
Click to expand...
Click to collapse
12.Aug.2012 MAGLDR/SD NexusHD2-ICS-4.0.4-CM9-HWA-SD V2.6 is the ROM you've installed, isn't it.
I would at first try all recommendation of members in that thread which reported same or at least similary issue before starting a new one.
Short wrap up what you can do, update initrd.gz, increase sd speed, limit background process, increase cpu, format your sd card and so on.......you have to play with all of these parameters.
For most of all these actions you can use RomToolbox pro.
If you're still suffering maybe you try another build, again some people get the build running smooth some not, even the set up looks same on the first view.
I have alway's 2 or 3 builds on my sd and try them under normal conditiion, which means for my daily work, which includes phone calls,SMS, data/WiFi usage to justify which build to use at the end.
Good luck :good:!!
Cheers.....LinChina

I believe we entered the era of laggy semi-functional ROMs post-Gingerbread. The last time I had no problems, lags of FC and the ROM felt stable and reliable was over 6 months ago. Can't honestly say which ROM worked as expected, no matter the title or description promises, so if you want to go with ICS or JB (even less functional), find the ROM you can live with without expectations of full functionality or lag.

enigma1nz said:
I believe we entered the era of laggy semi-functional ROMs post-Gingerbread. The last time I had no problems, lags of FC and the ROM felt stable and reliable was over 6 months ago. Can't honestly say which ROM worked as expected, no matter the title or description promises, so if you want to go with ICS or JB (even less functional), find the ROM you can live with without expectations of full functionality or lag.
Click to expand...
Click to collapse
Quite funny your comment ........because yesterday you stated this :good: and it would be the one you will keep.....??!!
Ok......another day
Some moderator might close this thread sooner than later.
Cheers.....LinChina

wrong Thread :silly: