yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Accessories] injulia:
Excuse me,

I have bought Sandisk Micro SDHC, 32GB, class 10.

With the adaptor to SD Card (included), the H2test say; Error.

there is file *.h2w , on card, it mean not in writte protected mode.

So, i use Micro card reader, the first test:is:

I format with:

https://www.sdcard.org/downloads/formatter_3/

and tes again, the result is:

What does it means?

***

I Insert to SGSII, with app: SD Tools, it says :

write speed: 9.1 MByte/s

Read speed : 20.7 MByte/s

Please advise me, must I retour this Micro SDHC ?

Thanks
[Galaxy S II Accessories] injulia:
help.....

:)
[Galaxy S II Accessories] lambstone:
That means its ok.

If they say 1000mb tested and 800mb lost, it means that the actual capacity is 200mb. Hence, your micro sd card seems to have the standard 32gb capacity

HOWEVER, you were scammed. Class 10 sd cards should not have "Writing speed: 4.74 MB" It should be around 10MB

So yes, you should 'retour' your sd card. If you used paypal, I think you can get a full refund without having to send back anything as this is obviously a counterfeit item.
[Galaxy S II Accessories] injulia:
I understand, it is 32 GB.

And I have register the serial number to :

http://www.sandisk.com/

and no problem, they said: in warranty.

and test in my Samsung galaxy SII, with "SD Tools",

I think the different speed may be because the Sandisk MIcroSDHC card reader, my Netbook (MSI U230, Windows XP SP2) or some thing else that may be not compatible with SDHC card.

because, in first test, i use the Adaptor to SD, insert to SD card slot in my Netbook: The H2testw said: Error. But with explorer, i can copy file to the card.

Then, i use Sandisk MicroSDHC card reader, insert to USB port in my netbook. And the H2testw said:

So, about the size (32 GB) and speed (9.1MByte/s) it is fine.

What I don't understand is that i bold. :)

Thank you
[Galaxy S II Accessories] injulia:
Is there a related between:

"Protected Area" on the card for the SD standard's security function.

20.4 MByte aliased memory (41956 sectors)

???

PS:

I have tested my 8 GB sandisk MicroSDHC class 4, on the same netbook and micro card reader:

[It is the memory card that i use in my SGSII, has many file, and only have space : 1,8GB ]

it means my netbook, my windows, my Sandisk MicroSDHC card reader is fine.
[Galaxy S II Accessories] KraftwerkElectro:
Tested - ADADTA microsd card

I bought a 32GB ADATA (upgraded) microsd card off Ebay.

It arrived in what looked like it's proper packaging but on the actual microsd card it said 64GB?

I did the test and the results are below - they don't look good.

Is the H2testw always 100% accurate because I don't want to complain to the seller if there is nothing actually wrong.

Thanks
[Galaxy S II Accessories] rani_345:
How to gets off write protected the USB with h2testw and now USB is going write protected and can't working. And it can't formatting any one software and other format tools.
[Galaxy S II Accessories] YourLeastFavoriteMC:
Can anyone tell me what this means? I had bought a 512 sd card and tested it on h2testw but do not understand the results, can any of you help me?
​

Please put this in the simplest terms possible as I'm not very smart lmao

"The media is likely to be defective.

58.5 GByte OK (122699639 sectors)

70.5 GByte DATA LOST (148000905 sectors)

Details:2.2 MByte overwritten (4520 sectors)

0 KByte slightly changed (< 8 bit/sector, 0 sectors)

70.5 GByte corrupted (147996385 sectors)

2.2 MByte aliased memory (4520 sectors)

First error at offset: 0x00000008cd7cb000

Expected: 0x00000008cd7cb000

Found: 0x00000008cd7cb200

H2testw version 1.3"
[AT&T Samsung Galaxy Note I717] NYConex:
I have noticed that the liquid ROM as well as the most recent nightly (2 SEP) have been pretty smooth. Nova launcher works great and I don't really see a lot of lag outside the launchers. One thing that kinda brothers me is the lag that is introduced when you enable the nav bar. I don't know exactly what happens behind the scenes (other than it disable the hw keys and enables the soft keys) but it adds a lot of lag. Is there a way to monitor exactly what happens when doing things to your phone? When I use liquid it changes without a reboot but with cm10 I have to manually disable the hw keys so it requires a reboot. Anyone know what's going on with it?
[AT&T Samsung Galaxy Note I717] thair7391:
Good question. I know there are settings in Developer options that allow you to show GPU status and updates which may provide some insight into GPU/CPU utilization. I don't have an immediate answer for you though. I'll do some research and report back.

With the Liquid ROM, I noticed it to be of the poorest performance as others. Was your experience smooth out of the box or did you have to change the debug.mdcomp.maxlayer from 2 back to 3 first?

**EDIT**

I just tried the Liquid ROM again and realized the debug.mdpcomp.maxlayer setting was set to 2 by default in that ROM and after the changing it, the performance was much better, though about the same as CM10 nightlies.
[AT&T Samsung Galaxy Note I717] NYConex:
The mdcomp.maxlayer is always the first thing I check after flashing a ROM. I always set it to 3. But if you go back to liquid try the navbar and you will see what I mean. In not home right now but when I get back I'll mess with it a little.
[AT&T Samsung Galaxy Note I717] andrawer:
I'm on the Liquid ROM and I don't notice any lag. So i don't think anything needs fixed...since I dont have the problems u describe.

I use almost all aspects of the Note except little music and games.
[AT&T Samsung Galaxy Note I717] Fasty12:
Try pulling down the notification drawer. Now sit there and tell me to my face its 60fps. No its not... its really choppy.
[AT&T Samsung Galaxy Note I717] thair7391:
Lol damn right. I'd say its between 14-21 FPS variably.

Which ROM's have worked the best for you so far?
[AT&T Samsung Galaxy Note I717] SayWhat10:
On mobile, had 2 scroll forever to read topic
[AT&T Samsung Galaxy Note I717] thair7391:
Are you saying that my OP is too long which made you scroll forever or are you saying that the lag in Jelly Bean cause you to scroll forever?
[AT&T Samsung Galaxy Note I717] thair7391:
Do you use Google Chrome? If so, how would you describe its performance in comparison to Ice Cream Sandwich?
[AT&T Samsung Galaxy Note I717] Fasty12:
The CM10 nightly has been the smoothest this far. So going by experience heres the rankings ATM.

1) Nightly... Smooth but constant flicker.

2) Liquid

2) Paranoid

3) Aokp

4) manualscout4life's rom.
[AT&T Samsung Galaxy Note I717] andrawer:
not sure if i understand.

I use my thumb to initiate the notification bar/drawer pulling down and it's immediate and smooth?? Up/down/up/down/up/down...smooth...just tried it. Not even a hint of lag...and that's with 4 notifications waiting for me to do something.
[AT&T Samsung Galaxy Note I717] roloracer:
The mentioned lag on jellybean compared to anything previous doesn't come from anything done by Google or issues with software but comes from the lack of hardware acceleration which we don't get to use with jellybean, so our device is not being used to the fullest, is known like previous versions of android when it comes out and ported , is not going to performed like it's supposed to until HWA becomes available. This is the performance drop in fps compared to ICS. Some think because is a newer version of android is going to be better performing out of the box, but that won't happen unless an official version with HWA becomes available or a developer figures out how to implement it into a ROM.

I think JB is amazing and smooth in the little time it has been out.

RoloRacer Paranoid on JellyBean
[AT&T Samsung Galaxy Note I717] egomezmorales:
I agree about the sluggishness of JB at its current state, its normal since we don't have HW acceleration, I'm on Paranoid and flashed Flaps Hot kernel, OC'ed to 1.7Ghz and its performing really well, you should try it out
[AT&T Samsung Galaxy Note I717] Fasty12:
So when will we get hardware acceleration? When jb officially comes out for the note?
[AT&T Samsung Galaxy Note I717] thair7391:
This has been my thought and awareness all along and what I've wanted to work on repairing. Perhaps it's everyone's use of the term "smooth" that is making everything amiss. When people boast that their JB experiences are "incredibly smooth!" and even more specifically "smoother than ICS!" I think they are making very fallible statements because I don't think that my perception of JB being behind ICS in smoothness can be interpreted as just a "difference in opinion or interpretation". It's definitely factual and quantifiable when testing frame rates and comparing them to ICS. Perhaps it's safe to say that "Jelly Bean is remarkably usable right now considering its alpha state", but to say that it is smooth is quite a fallacy. It's really not much better than Gingerbread and Gingerbread lacked HW acceleration altogether.

But if JB lacks hardware acceleration completely, then how is toggling the maxlayer setting and HW overlay setting in developer options clearly affecting performance if HW acceleration isn't even supported at all in the first place? Some sort of acceleration is clearly being enabled for the evident difference in performance to occur.

I am grateful that you recognize JB's current state to be behind and also attribute it to HW acceleration as I initially did. Now we can hopefully gain some momentum on finding the hindrance of bringing HW acceleration to JB!

If there's anything we've learned thus far, it's not to label a ROM officially "smooth" unless you can prove it greater than or equal to stable ICS builds with quantifiable means!

The word "smooth" is beginning to become a profanity for me, which is rather extreme, as there aren't many words I don't say! Lol...
[AT&T Samsung Galaxy Note I717] yollasho:
Everyone should read this.

http://www.androidpolice.com/2012/0...roject-butter-how-it-works-and-what-it-added/

Jb runs exceptionally well for me with just the 2 buffers. Are all the animations perfect every single time? No, but it's perfectly usable, and slick enough for my dd. I'm sure it will be sorted in time.
[AT&T Samsung Galaxy Note I717] zer0nine:
So far the smoothest jb rom for me has been dagr8's aokp Sept 1 build.

HW overlays are disabled and cpu at stock frequencies. Running Nova 1.2.2 and have fluid home screen transitions and overall smoothness.

If I were to nitpick, the notification bar is the only thing that seems somewhat sluggish but only when I pull it down on the home screen (I am running a live wallpaper.)

No reboots or sleep of deaths so far, loving this rom at the moment.
[AT&T Samsung Galaxy Note I717] egomezmorales:
Really interesting read, thanks for sharing!

---------- Post added at 01:04 PM ---------- Previous post was at 01:04 PM ----------

Yep, or that a developer taps on how to get HW acceleration
[AT&T Samsung Galaxy Note I717] Eric-1987:
We've had hardware acceleration.
[AT&T Samsung Galaxy Note I717] thair7391:
Then what is the culprit that you propose for the decrease in performance?
[AT&T Samsung Galaxy Note I717] thair7391:
Spectacular material. Thanks for sharing this. This article is useful in correcting other's misconceptions that Jelly Bean is "buttery smooth" in its current state on our device. It creates a definition for smoothness which is essential to this thread. Thanks again!

So we know that Jelly Bean has been programmed to process frames correctly to provide us with a smooth experience, but what is causing it to fail in doing so if it's programmed correctly already?? Hmm... Well it must be its interaction with the hardware, as many have already mentioned: HW acceleration! I'm glad we cleared that up for the good fellow who stated that we already have HW acceleration on our devices in the Jelly Bean environment.
[AT&T Samsung Galaxy Note I717] :
We do have hardware acceleration up to 2 overlays is how I'm reading it. But the 2 isn't enough to make it buttery smooth all the time. That's why jb takes it a step further and adds a third buffer for times of need, and they lock the processing for frames more strictly for vsync processes.

Is jb hardware accelerated on our device? Yes, android has had some hw acceleration (and increased usage of hw acceleration with releases) since inception. We just don't have the full jb implementation as Google has designed it just yet. I don't know if it has to do with setting up registers and addressing them correctly or what, but I'm sure they'll figure it out.

Edit-Also, the Qualcomm site lists the JB driver for Adreno 2xx devices was only released August 1st, 2012, and they specifically say it's an early release and will be updated.
[AT&T Samsung Galaxy Note I717] egomezmorales:
Thanks for clarifying, I was wrong about it :o
[AT&T Samsung Galaxy Note I717] jjc5891:
Just curious...do people here have first hand experience about the stuff they talk about? I'm talking about getting into the underlying code...those are the developers who I want to hear from.
[AT&T Samsung Galaxy Note I717] :
You can go here and check out all the source, what they are changing, and read code for yourself. You can check out some of the GPU code in the 8660 repos. And also check out the gerrit review site. Also, I edited my post above with tiny bit more.

No thread in the general section is really going to accomplish anything. I don't think actual dev stuff should be here in general, but if you want dev stuff, go to the above sites, and check out Googles extensive sites on android and developing.
[AT&T Samsung Galaxy Note I717] Eric-1987:
Where is the decrease in performance? Mine is fine.
[AT&T Samsung Galaxy Note I717] tbae2:
Having compared my phone running liquid to my friends Verizon nexus, there I no competition as far as smoothness goes. I think peoples perceptions are different and I doubt it is "fine" if you compare the two. The nexis just flows so smooth with the UI whereas our phones do not. I'm sure this will get solved eventually.
[AT&T Samsung Galaxy Note I717] Eric-1987:
I have a friend who has the nexus and his phone isn't any smoother.
[AT&T Samsung Galaxy Note I717] tbae2:
Well then mind sharing your setup? Because my friends nexus is completely "buttery smooth" no lags on transitions flows seamlessley where my note does not And you can tell . And he's not OC'ing and I prefer not to .
[AT&T Samsung Galaxy Note I717] thair7391:
Your perceptions of smooth must not be the same as the rest of us who have recognized the temporary lack of smoothness if you can't tell a difference between a Galaxy Nexus running Jelly Bean and our device running Jelly Bean in its current state. Smoothness isn't really about speed. It's all about Vsync which you can get a better understanding of through the article that yollasho provided. If you read that article and can still compare the two devices without noticing a difference, then either the occipital lobe of your brain can't process more than 14 FPS, or you have a miracle device. Clearly there are a reasonable amount of people here who recognize the issue so we're not all bull****ting or overly critical.

I'm not saying you're wrong, as the possibility can't be eliminated that you have a miracle device that performs differently than the countless others, but for the rest of us less fortunate users, we've a lag issue to solve!

I just installed a nightly build of CM10 on my friend's Samsung VIBRANT and it ran smoother than our phones!! A VIBRANT!!! Clearly our hardware is more capable than that of the Vibrant's, even the Nexus. There is just an issue with a driver/configuration/module that is improperly rendering hardware acceleration in our current builds of JB that is crippling our performance.
[AT&T Samsung Galaxy Note I717] thair7391:
Hey everyone, I just wanted to let you know that I was tinkering around in build.prop and discovered a fix that MAJORLY improves performance.

Change the debug.composition.type from "dyn" to "GPU" and reboot.

I think the graphics have been loaded on the CPU the whole time and this setting seems to offload it to the GPU which not only makes things MUCH smoother but takes a load of off the CPU which increases speed!!!

Let me know or thank this post if you had as much success as I did.

**EDIT**

I've also noticed that after enabling use of the GPU, you can change debug.mdpcomp.maxlayer back from 3 to 2 again to fix flickering and the performance is still much better! For some reason the home screen seems a little slower on 2 but Chrome runs smoother on two than it does on 3, as well as the Play Store. Kind of inconsistent than what I experienced in the past but hey I can't complain! Things are much better! I really recommend everyone try this! The phone just seems to FLY!!!!
[AT&T Samsung Galaxy Note I717] thair7391:
Sorry to keep posting but I'm just so damn excited. MY PICKLE IS TICKLED!!!!

I think I've actually just attained a sort of "Buttery Smoothness" on my device after all of this time (except for a few apps like Chrome that are slightly choppy)

Let me know your experiences everyone!
[AT&T Samsung Galaxy Note I717] NYConex:
Changed it for a bit but seems about the same as dyn on the current nightly (0904). Maybe a little smoother right at the reboot but after everything settled in for me it was about the same.
[AT&T Samsung Galaxy Note I717] :
I would guess dyn is supposed to be dynamic? Probably offloading to cpu/gpu depending on which one has resources.
[AT&T Samsung Galaxy Note I717] thair7391:
Yeah my thoughts exactly. Only, I don't think Android was doing a very good job at scaling with it on lol. What kind of improvement have you noticed since changing it? Mine has been drastic!! Also, what is your maxlayer set to?
[AT&T Samsung Galaxy Note I717] thair7391:
As weird as this is, I feel like I had to reboot twice to notice the full effect. What is your maxlayer set to? 2 or 3? (Or 4 or 5 if you know something we don't! lol)

If the flicker bothers you immensely, then you can still leave it at 2 and not have as much of a decrease in performance but if the flicker isn't a big deal to you (it isn't to me), then leaving it on 3 is a TREMENDOUS boost.
[AT&T Samsung Galaxy Note I717] Eric-1987:
I think I just know how to use and configure my device properly. I haven't had performance issues since like the 5th build of PA JB. My device is 100% smooth and buttery no lag what so ever. I am a stickler for how my device runs too. I also have a friend who has a vibrant and his isnt smoother than mine. Pretty much the same across all devices. Android doesn't take much to run. What I did notice is my device boots a LOT faster though. I can use my device instantly when it starts up his he needs to wait 30 seconds.
[AT&T Samsung Galaxy Note I717] thair7391:
Well, I certainly can't claim to be an Android guru as I'm new to Android by only about 4 months. I am fairly confident in my overall understanding of all computer models though as well as in my ability to troubleshoot but maybe I'm not good enough to know how to configure my device as well as you.

Do you mind sharing with all of your steps to setting up a buttery smooth, lag-free ROM from start to finish? (You can assume you're already rooted and have a recovery environment)
[AT&T Samsung Galaxy Note I717] Eric-1987:
Dont have clutter pretty much. No tons of widgets or anything like that. I uninstall EVERY app I dont use. And I mean EVERY app. I have about 4 widgets. Everything is as clutter free as possible. I only keep on the device what I'll actually use. NOTHING else.
[AT&T Samsung Galaxy Note I717] robyr:
I don't think you fully understand the issues with JB on our (and any Adreno based) device. This isnt a "clutter" problem, and it is not a config issue. It is squarely a driver issue, and it is well documented on the S2 forums.

Please stop spreading this misinformation. Or, if you feel like keeping this line going, take an HD video of your phone operation. I highly doubt you have some exception to this rule on your device.
[AT&T Samsung Galaxy Note I717] thair7391:
I'm the exact same way. That's why I rarely like any custom ROM's aside from official CM10 or AOKP because there aren't any of the developer's "preferred apps" trashing up the ROM. I like starting BASE only. It's why I reformat my Windows PC at least 3 or 4 times a year lol and as well as why I use Arch Linux. I want to start with nothing and add only what I need. I will say though that in Android on the Galaxy Note, 0 widgets or 6 widgets don't make a noticeable difference in performance for me. And installed but unused applications don't necessarily impact performance if they're not running in RAM. A computer's hard-drive could be filled to the brim with only 1 MB to spare and have minimal services configured to run in RAM and perform much faster than a computer with barely any applications installed but everyone of the few that are installed running at startup. Storage and RAM aren't the same.

Aside from reducing clutter ( a storage matter and nothing more) which really doesn't impact active RAM-based performance, you really haven't said much about how to "configure" your ROM as you mentioned in your previous post. Could you provide a little more information?
[AT&T Samsung Galaxy Note I717] Eric-1987:
I know exactly the issue people are talking about and I just dont have it. I dont have a way of taking HD video of phone operation or I would. Why in the hell would I lie? Dont get mad my phone is perfectly smooth. And for thair7391 you've never used a cluttered android phone have you? Big difference in performance and a hdd with 1gb left will run noticeably slower than 500gb left. I work as a computer tech so trust me. And also I have the latest Nova running beta and all animations are set to either system default or JB default. And widgets do make a big difference in performance. I dont use live wallpapers either. I even uninstall the stock messaging app and apolo too. I even uninstall the stock launcher that comes with PA JB builds.
[AT&T Samsung Galaxy Note I717] thair7391:
THANK YOU. My thughts exactly. I'm just not as good at being as abrasive as you lol :D
[AT&T Samsung Galaxy Note I717] wase4711:
6 months from now, when JB is OFFICIALLY released for our phones, this discussion might have some more relevance; until then, while we are using ALPHA/KANGED versions of JB, this really has no relevance...The Dev's are doing a great job with the limited tools/resources they have, but these roms aren't really indicative of what the REAL JB will be like
[AT&T Samsung Galaxy Note I717] thair7391:
Hmmm... Check this out everyone:

http://review.cyanogenmod.com/#/c/22782/

The latest change on appspot for CM10 shows a fix for : hwc: Enable MDP_BACKEND_COMPOSITION and it's proposed to resolve the flicker that everyone is ill of. I wonder what effect this will have on performance as well. I'm going to look into the code or files he's changed and see if I can understand it a little better then I'll report back here.

If someone else knows more about this change with more experience, feel free to enlighten me! I'm here to learn!:fingers-crossed:
[AT&T Samsung Galaxy Note I717] thair7391:
I'll check it out! Thanks. The name just of repelled me... "Gubment Cheese"?? It sounds like something you'd find in a hobo's groin.

And one more thing baout your wife, I have to know... Does she flash ROM's like you like it??
[AT&T Samsung Galaxy Note I717] robyr:
I am quite interested in how this pans out. This sounds like our ticket, now.

I think I am going to pull the sourcetree and diff it to see whats been changed.

Actually, this is EXACTLY what we needed. The next Nightly will almost certainly be fully accelerated. Good find, dude.
[AT&T Samsung Galaxy Note I717] O_G:
Thread Cleaned​

Stop with the pointless bickering, three pages of the two of you going at it is to much!​
[AT&T Samsung Galaxy Note I717] thair7391:
Thank you for deleting it. I tried to stop but the remains of my mistakes from not doing so soon enough were forever fated to haunt me until your generous removal from my past. Thank you !!
[AT&T Samsung Galaxy Note I717] tbae2:
Changing to "GPU" made a helluva difference for me even with Max layers at 2 , way too much ficker at 3 . Nice tip!