yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] servegmo:
I updated my firmware to the latest open Europe one and the problem stop! So the best to solve this problem is to flash a new firmware!

Pure vida guys!
[Galaxy Note GT-N7000 General] ushiuma:
Samsung Galaxy Note or S-Memo or S-Pen bug?

Hi

I have encountered this strange problem with my new galaxy note. Not sure if it is phone hardware, S-Memo or S-pen problem. Nevertheless, after getting the phone replaced, the problem still occurs but less frequently as before. Hope some kind souls could enlighten or share if they've similar encounters.

Problem = there's always this strange spot (right side) that could not be drawn using the S-Pen. Using finger is ok. Sent phone back to Samsung, they've changd the LCD, S-Pen and problem still persisted. Later they changed me a new set, but after a few tries, the same problem comes back but less frequent as before.

I tried resetting the phone, the patch size reduced, and even if it does not occur, drawings on that part of the screen is never smooth. Maybe I am having phobia now.

I can't post the picture here coz I am new... :(
[Desire Q&A, Help & Troubleshooting] Dave759:
Basically we all know that the Desire has a useless ammount of memory. I'm running ICS one of the first beta versions, anyway I've got no memory, I've tried to partition the sd card to ext 4 but it rejects it so I'm looking for someone to point me to the next step with some instructions mainly if I need to revert back to gingerbread, how would I do that?

Thanks Dave

[EDIT] Should also mention I found this thread but doesn't really help me.. http://xdaforums.com/showthread.php?t=1429570&page=2
[Desire Q&A, Help & Troubleshooting] andy3434:
How are you trying to partion SD card? Most reliable methods seem to be with 4ext or Gpart.
[Desire Q&A, Help & Troubleshooting] Dave759:
I've used gparted via ubuntu, but it for some reason doesn't like that, I'm thinking its rom related as it worked on a GB rom but since going over to ICS it doesn't work..
[Desire Q&A, Help & Troubleshooting] snorrip3:
what do you mean 'rejects it'

do you mean that your entire SD card is not being read by the ROM and/or windows ?

You can use one of clockwork recovery's advanced menus to format the drive for you to a size of your choice 512 or 1024 or whatever.. I can't remember if it gave options for ext3 and 4 but you can def. get ext 4 out of it. the rest should be left as fat32.. works like a charm
[Desire Q&A, Help & Troubleshooting] divereigh:
The way I did it was via the CWM.

Before you do this, make sure that there are no apps stored on the sdcard (because your about to wipe it) - i.e. go through each app (unless you have Titanium Backup, which makes this easier).

Boot into recovery, in the advanced section, select partition sdcard, then select a 512Mb partition (wouldn't go higher - you get issues), select 0 for the swap partition.

Then boot up and follow the instructions about a2sd on this page:-

http://xdaforums.com/showthread.php?t=1355660

It all worked fine for me (and I have loads of space now!)
[Desire Q&A, Help & Troubleshooting] jay.t:
What version of CWM did you use?
[Desire Q&A, Help & Troubleshooting] cirapfc:
hmmmm, are you using beta 0.3.6?

I mean, there are some instructions for a2sd:

To activate the built in a2sd:

open terminal and run these commands:

su

a2sd install

To move dalvik cache do:

a2sd cachesd

And try with different sd card....
[Desire Q&A, Help & Troubleshooting] Dave759:
I'm on 0.3.6 i followed the methods of using the CWM to partition it, when i said rejects it i meant that after using gparted android claims it is corrupted and nees to be format. Anyway so after running the terminal commands all fine but i cannot use the phone at all, contacts process crashes and thats followed by "android.process.accore has stopped." Any suggestions? I figured it might be a bad flash so re-flashed it but that doesnt seem to help.
[Desire Q&A, Help & Troubleshooting] jay.t:
I have not yet partitioned my sd card, I am still sorting things out. I also have low mem error. I believe the bulk of the problem, is the sorting of things. Others have had success with certain configurations of CWM, Droid builds, ext3 or ext4, and cell phone carriers.

After reading like you have, I have seen that CWM partitions have been unsuccessful until after version 2. I am currently running a US Cellular Droid 2.2, Rooted, CWM v4.0.0.2. Sorry for the lack of help yet. I will keep updating as I work through this.
[Desire Q&A, Help & Troubleshooting] Dave759:
I think best bet for me is to go back to gingerbread and go back to ICS after that and see where I am.
[Desire Q&A, Help & Troubleshooting] fissikela:
ICS for Desire is too many bug.

Try to erase cash and restart phone
[Desire Q&A, Help & Troubleshooting] djfirefy:
These are the steps you have to do:

1. S-off

2. Get the appropriate partition for the system (see the Alpharev instrutions);you need Bravo Stock or Bravo Data++(I used the last one);

3. with Geparted from Linux(Ubuntu) live cd, partition SD card FAT32 and at least 1,5Gb 4Ext, both as primary partition;

4. power-off your Desire;

5. press Vol. down and Power;

6. go in Recovery;

7. wipe data/factory reset

8. wipe cache partition

9. mounts and storage --> format boot, cache, data, system, sd-ext

10. advanced --> wipe dalvik cache, wipe battery stats

11. install clean rom from http://xdaforums.com/show....php?t=1403113 without trying to get m2sd to work;

12. Setup the Google stuff;

Goodluck!
[Desire Q&A, Help & Troubleshooting] Dark_AJ9:
If you want to have ICS on your Desire, try Chromium v1.5 .

Enviado desde mi HTC Desire
[Galaxy Y GT-S5360 General] mykar3z99:
how to use Ap2sd with creed's v2 rom? would you give me a tutorial please... thx
[Galaxy Y GT-S5360 General] noobwithgalaxyy:
I have no idea if Creed's ROM supports it.. PLEASE CHECK BEFORE PROCEEDING..

http://code.google.com/p/android-roms/wiki/A2SD
[Galaxy Y GT-S5360 General] mykar3z99:
thanks... but i still confused for use it...
[Galaxy Y GT-S5360 General] blackjack1942:
just use link2sd, it's easy to use :D
[Galaxy Y GT-S5360 General] SooNoob:
Just use link2sd, its as easy as nothing. :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] joeyvanhummel:
First off: I am not a programmer. I have only very little experience in C/C++ and that's it. I am here to suggest something, and I am not sure if it would work, but I'd rather have a stupid idea up here than a good idea not up here.

We all know that the developers are having trouble getting hardware drivers for ICS on our HD2s to work since the drivers' sources aren't being released. However, I know that for example Gingerbread ROMs have hardware acceleration just fine.

Android, though, is open source. And so I got an idea: What if we stopped looking at the driver, and focused on Android itself? What if a developer looked at how the driver framework has changed, and wrote some sort of dynamic bridge, so that ICS could use the driver of Gingerbread? Some kind of layer inbetween the driver and the driver framework that would reverse/translate the changes made between Android 2.3 and 4.0?

Again, I'm not a developer or programmer, so I wouldn't know how effective this would be. I'm just throwing this out here; if it's a bad idea you can just ignore this.
[HD2 Android Q&A, Help & Troubleshooting and Genera] sam razzy:
If its a dev question den.. remov suggestion and change it to dev
[HD2 Android Q&A, Help & Troubleshooting and Genera] joeyvanhummel:
I have done so; would this be correct?
[HD2 Android Q&A, Help & Troubleshooting and Genera] czarsuperstar@gmail.com:
That is what ramv87 did I think cause he uses gingerbread files. I dont know where he got the files from but if we knew what device he took the files from and how he modified them. That would be a start.
[HTC Sensation] DrunkenWarrior:
Hi,

I am trying to run revolutionary.io to get root access. But, I am getting an error saying - " failed to get root :( " error. I am currently on stock ROM

2.3.4

Software Number 1.52.720.3

Am I on too new a firmware for revolutionary to work? If so, how do I overcome this problem?

Cheers

JayK
[HTC Sensation] DrunkenWarrior:
Hi,

This is working now. Use tacoroot to gain temp access then when on temporary root - Run Revolutionaryio. This works and I have S-OFF now.

Cheers

Jayk
[HTC Sensation] g15:
I was able to S-OFF by following this. Thank you for the idea!
[HTC Sensation] Forever_n00b:
Thanks, got it working for me too. Have posted a few more details here on the whole process.
[HTC Rezound] carm01:
I was reading about safe mode for android, and found an article on how to do it for HTC devices here:

http://androinica.com/2010/08/how-to-activate-android’s-safe-mode-to-get-out-of-a-force-close-loop/

However i can't seem to get it to work for the rezound

Anyone?

Thanks
[HTC Rezound] WasabiWa83:
Well, not sure if there are any other options for our phone, but issue one would be the fact that we don't have any physical buttons on our phone.
[HTC Rezound] carm01:
It can do it b/c i seen it, it was during a bootloop, and i cant remember how i did it
[HTC Rezound] drynyks:
Turn on your phone, restart, or hot restart > as soon as you see boot animation hold down volume down button. Keep it held until you get a long vibrate. After the vibrate you can let go. You should be in safe mode then.

To get out of it you can hot restart.
[HTC Rezound] Toaplan:
What Rezound are you using? Mine has 3.
[HTC Rezound] SteveG12543:
I think he means on the face of the device. Like, the old HTC Hero has physical buttons for home, menu, etc and a trackball :o.
[HTC Rezound] RuLEoF2:
A WORD OF CAUTION TO ALL ...

I tried this when I was having trouble connecting to my SDcard via USB and it did work, BUT... for some reason, it completely wiped out all of my widgets and home screen shortcuts.

Maybe this is an isolated problem with my phone, but be aware of this possibility before you proceed.
[HTC Rezound] TCM55:
Did you have that issue after you exited safe mode? I remember that after I exited safe mode on my thunderbolt everything returned to normal.
[HTC Rezound] acejavelin:
I booted into safe mode once by accident, same thing, everything on the home screens was almost like a factory default, rebooted and it was fine again, everything came back to normal... Pretty sure Safe Mode on the Rezound is just like in Windows, it essentially just skips a bunch of custom and non-essential startup configuration parameters.
[HTC Rezound] RuLEoF2:
All the widgets and shortcuts were gone after I rebooted into normal mode. The same thing happened once before but I was in the middle of trouble-shooting some issues so I dismissed it as a system glitch.
[Galaxy Tab 7.7 General] sectorlord:
the 77 has same screen as the note... but it's brightness more even across the screen.. the only problem you will have is it's size... since you're coming from Note.. you might find it hard to justified it's size... like bringing it with u anywhere.? when jogging?

I am now using my old trusty ipad2 ... which I can type like a breeze...

like I said 77 has better amoled screen that early Notes...
[Galaxy Tab 7.7 General] Jade Eyed Wolf:
Erm, wrong...

The Note is a PenTile display. The 7.7 is not.

The Note's PenTile arrangement uses 8 subpixels per 1 pixel.

The 7.7's SAMOLED Plus display uses 12 subpixels per 1 pixel.
[Galaxy Tab 7.7 General] EarlZ:
I won't be brining it around for joggin of that sort, its gonna be my primary media device so it needs defect free from those random manufacturing faults.

It might be too early to ask this as probably the user count in xda is pretty small.
[Galaxy Tab 7.7 General] mailings:
I'm returning one of this beacuse when reading in a dark room there are serval visible rings and spots darker than the rest of the screen.

You are only able to see it when you have a grey or black background and your eyes are adapted to the darkness.
[Galaxy Tab 7.7 General] DaveC1964:
This device probably isn't for you, yet.

I just got the 7.7 and have issues. The brightness is a bit brighter along one side, and I have the dark spot issue, this time in the form of dark circles, equally spaced (probably from the glass handling suction cups or something)

On the bright side, at least I don't have any bad pixels ;/

BTW a good app for testing is the simple "Advanced task manager" app, it has a dark screen near black and these blotches are visible with this even in a room with some light.
[Galaxy Tab 7.7 General] randomgent:
I used my galaxy tab 7.7 for almost a month and i must say , the dark circles are truly annoying especially when you watch movies with dark scenes in a dark room with low brightness.You can hide the dark circles by increasing the brightness but it is a simple waste of battery life and its really bright in dark room. I also noticed screen burn in for the wifi and battery icon, i used my 7.7 on zero brightness since day 1 and screen burn-in still persist after 3 weeks. Good way to see the dark circles is by simply turning off the tablet, the tablet will "glow" with the dark circles after the samsung logo is gone.
[Galaxy Tab 7.7 General] reiconol:
My old and new one have these rings. I'm guessing its glue or something bonding the screen to a backplate. Or an imprint of a backplate on the screen.

In any case I think this is not a problem or defect. You really must be in total darkness and viewing a black screen to see it. And even then its very hard to see.
[Galaxy Tab 7.7 General] EarlZ:
Thanks for the heads up, It would seem that the darker spots are quite obvious since the screen is bigger, I also had those spots on some of my Galaxy S2 replacements and I found it very unacceptable and the same with my Note.

When I was testing at the store which had the usual store lighting one unit had several visible lines in greys while the other one only had 3 lines just in the middle.

For the uneven brightness on the screen, Im pretty sensitive to that.. when I saw the HC task bar in landscape mode I immediately noticed a difference in brightness but only 1 of the 2 exhibited the issue.

The screen burn-in is a concern as Im getting the same feedback from friends who bought the unit just last week!

I understand that not all screens have this issue but the chances of getting an out of spec screen might be pretty high, wish they brought back the same quality control when the Galaxy S initially came out, which had none of these issues what so ever.

Do you mean advanced task killer?

It is a defect and a very bad one, also the visibility on this is not the same on all units. I have a suction up ring on my Galaxy Note which is visible at the 'service center lighting conditions' which the tech also saw the rings. Several pictures of this issue also posted on the various Galaxy S2 forums here in XDA under a well lit condition.

Seems like it until screen yields improve or I get a chance to get one w/o any of these out of spec issues.
[Galaxy Tab 7.7 General] f1ux:
No screen is perfect, not even the ipad screen.

Ihave a galaxy s2 and rememeber hearing all the burn in worries last year. Almost a year later now and i dont have any burn in.

The only issue ive noticed is that some pixels on oled can have a slightly differrent brightness than others due to the nature of oled. Yes my s2 has a tiny amount of pixels like that,

But you have to look at it at the wrong angle with the wrong amount of ambient light with the wrong colour on the screen to notice it.

Yes a larger screen is likely to have more issues but if it was an ips screen then we would no doubt all complain about backlight bleed.

My advice is stop looking for problems with it and enjoy your tablet otherwise you will never be happy with it !
[Galaxy Tab 7.7 General] EarlZ:
True no screen is perfect, what I am looking for is a quality screen that is with in specification and Im more than certain there are batches of screens that will meet these requirements.

Like what you said, no perfect screen but there are some screens that are made better, A year of usage with no burn-in is fantastic! Some are getting it as early 30days from purchase.

Yes to certain degree there are but they should not be noticeable to the naked eye, if its noticeable then its purely a quality control issue.

Well that depends on the usage, Im not pushing my own usage to anyone as I believe not everyone watches movies or browses the web on the tab7.7 with close to 0% brightness and in total darkness. My usage revolves on that so there are no special conditions on my end. I hope this is understandable.

Yes backlight bleeding, but thank god both of the ipad2's here dont have any hint of backlight bleeding.

I do not look for these issues intentionally and I see them with my normal usage, thats why I intend to research first before taking the plunge. But I understand I might have a higher standards that others but thats just me, I want to get the most of my purchase or not purchase at all.

Long story short, all the screen issues I've found on my Galaxy S2 was due to normal usage including the yellow tinting and darker spots which annoyed the heck out of me considering the cost of the device. On the Galaxy Note I've read about the all the screen related issues even on the video issue and still said to my self 'these things should not be noticeable in normal usage' but i was wrong. So this time Im taking it slowly but I already know what to expect. But I do understand what you are trying to say.

EDIT:

I dont want anyone to mistake this as a witch hunt, I just want to know what to expect, acceptance is easier when expectations are set.
[Galaxy Tab 7.7 General] reiconol:
Yes, there will never be 100% perfect screens. We'd all be constantly returning devices and not actually using them because of some "defect".

I've had my S2 since it first came out in May 2011. No problems with burn-in or colour shifts. I don't expect my 7.7 to have problems either. I'm not concerned that some "defect" will manifest itself under some extreme "only if I go looking " condition.

I'm enjoying using my S2, 7.7, and Transformer for what they are - mobile devices that provide communications, entertainment, and information.
[Galaxy Tab 7.7 General] EarlZ:
Agreed I can also accept defects as long as I dont see them with my usage. Example between my SGS2 vs Galaxy Note which shared a common issue on the darker spots but it was more obvious on the SGS2 since it was a horrible pattern while on the Galaxy Note its tiny and multiple spots.

Every defect is different and we should not all assume that they are all acceptable to everyone.
[Galaxy Tab 7.7 General] EarlZ:
This is always the case, people who dont have the same usage pattern nor with the same issue will never understand. But its been my understanding that this is already 'common' (but not normal) among amongst the hd samoled and samoled plus.

Yes the other alternatives that I've been looking are also riddled with issues, come to think of it only samsung has the least issues based on my research.
[Galaxy Tab 7.7 General] SonicTab:
I've seen the concerns on other AMOLED devices Earlz mentions as well.

It's not a deal beaker but you may want to keep a LCD device around for reading at night.

No use exchanging numerous times hoping for a perfect screen.

Right now while AMOLED is a very dramatic screen tech

but it's not at its best with low brightness levels,

and certain test patterns / images reveal other side effects .

For reading in the dark a screen like the iPad 2's IPS LCD is probably a better choice.

It offers a very low brightness level with consistent results.

I think the key is to use AMOLED devices where they perform best,

at higher brightness levels during the day.

In that scenario if you hand a iPad 2 and AMOLED device

to the average person they will be floored with the AMOLED screen.
[Galaxy Tab 7.7 General] GOF007:
I don't have any issue on low brightness level.

I always operate my 7.7 at ~0-20% brightness.
[Galaxy Tab 7.7 General] earthman5678:
Did anyone test the screen using the screen test apps? I tested mine and I have yellowish patch at the bottom part of the screen. It's only visible in dim grey. Luckily there is no dead pixel but my screen start to squeak a little when press at the bottom corner. The quality control is really bad. I'm waiting for a engineering revision before going for warranty claim. I must say I'm disappointed.
[Galaxy Tab 7.7 General] EarlZ:
There's been a few reports from here and another forum that the screen seems to squeak or dislodge a bit on the bottom corner.
[Galaxy Tab 7.7 General] mailings:
@SonicTab:

I went for an amoled screen beause it's suposed that when screen is black pixels are off and there should be no light emiting so in my case, when reading in the dark I should only see the text, and not a bluish black background as every other LCD based screen

@GOF007:

You are either lucky or do not use the tablet in the same conditions as I do. Did you test it viewing one of the pictures in the first post in a dark room?

I really hope my case where just bad luck and be given another tablet whitout those screen issues, or at least with something less annoying.
[Galaxy Tab 7.7 General] Richdog:
Well, as of last night I seem to be getting weird colour banding intermittently on my 7.7... but not the "normal" passive kind, it kind of looks like electronic interference of sorts... wavy rainbow-coloured lines going horizontically accross the screen and especially noticeable on Grey and Blue backgrounds.

This was NOT there before, and the only thing I can think of that I did different to "normal" is charge it last night with a universal wall plug USB charger, with a genuine Samsung USB cable inside. Could that have caused some kind of problem? Anyone else experienced this? :confused:

It's not crazy noticeable at all times, but my eyes are sensitive enough that I do notice it with the conditions I described above!
[Galaxy Tab 7.7 General] EarlZ:
It is a common defect but none the less its still a defect but if thats the only part where you notice it I guess it can be acceptable, on my end greys are very important as a good majority of the UI has that shade even ICS theme keyboards are affected.

Right now I have a Galaxy Tab10.1 and Ipad2 in my hands and Im going to use these devices as basis for my next device since Im still in line for a replacement on the Tab7.7 or a refund.
[Galaxy Tab 7.7 General] ph00ny:
I'm still surprised that you still buy them even with numerous complaints about the screens

Captivate, S2, Note, and 7.7 (only had it for few days) have had no visible defects

Nexus on the other hand is grainy and uneven in some colors (very noticeable in xda app brown)
[Galaxy Tab 7.7 General] EarlZ:
Was hoping to get lucky but now I know better :p
[Galaxy Tab 7.7 General] ph00ny:
maybe i'm getting lucky. I usually end up devices with no battery life issues or screen issues.

Nexus color issue does annoy me a bit.
[Galaxy Tab 7.7 General] EarlZ:
Could also be a difference in expectation on what issues and non-issues are.
[Galaxy Tab 7.7 General] moesom:
Okay I tried it and gray 25 reveals everything... there's imperfections everywhere 4 clearly visible rings, 2 feint ones, 2 semi-visible smaller rings (total of 8) and there's blobs/dots EVERYWHERE, also the top right of my screen looks like its darker like its damaged... i've had my 7.7 for 5 days... what can i possibly do? my local good guys have retarded employee's and im not sure how i would get them to identify this, also how can i be sure the replacement will be better? are my symptoms average? or unlucky

thanks..