yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S II SGH-T989] heXacode:
Its very possible that it was partitioned for that case but that is what seems odd to me. It wouldn't make sense to have internal memory, substituted partitioned internal memory acting as a SD card and a SD card slot.

Did you ask if that's just for the display phone or is it the same with for all SGS2s?
[T-Mobile Samsung Galaxy S II SGH-T989] dcam1075:
There is no physical SD card in the phone. This is the same partioning that Samsung used on the first Galaxy S phones. It partitions the internal memory to show an internal SD card.
[T-Mobile Samsung Galaxy S II SGH-T989] NCguy:
So is that internal sd handled like a real sd card? If you install apps to it then it will also install part of the app to the 1.8gb real internal memory until all of the 1.8 is used and then your scre*ed?
[T-Mobile Samsung Galaxy S II SGH-T989] NCguy:
Ok, I may have the answer to my question. I found this post in another forum:

The phone will install the APKs to the internal root memory which is 2GB in size. Then data files and additional app data downloaded goes into the internal SDcard memory which is 11GB in size.

The microSD card is listed as external_sd and you use it to store your photos & video (you can shoot direct to it), your music and movie files. These are files that take up a lot of space but you wouldn't use them all the time"

So I still have this question for anyone familiar:

Do all apps automatically load the apk's to the internal root memory and the data to the internal SD? Or do you have to explicitly tell the installer to install to the SD to prevent everything from installing to internal root memory?
[T-Mobile Samsung Galaxy S II SGH-T989] tenxo:
Mine came partitioned as you wrote but I have not installed anything to it yet so can't answer your last question... what I hope is that it is treated like a total seperate drive I.e. don't erase that partition during flashing or full wipe, but gives you option of what partition to wipe or install to.
[T-Mobile Samsung Galaxy S II SGH-T989] rahlquist:
If the SGSII behaves the same as other Galaxy S phones then when you install an APP you just install it. Nothing special needed to point things around. There is no reason to install all apps to the External_SD or even the regular SD, youre just creating headaches for yourself. I have had over 524 apps installed on my captivate at one point and was still not out of space.
[T-Mobile Samsung Galaxy S II SGH-T989] NCguy:
But just to be clear, it doesn't by default install the app data to the internal sd?
[T-Mobile Samsung Galaxy S II SGH-T989] Jorge18:
Mine has it as USB storage, not SD card.

I'm not sure how to check where the apps were installed.
[T-Mobile Samsung Galaxy S II SGH-T989] rahlquist:
In general it should install the app data where the app tells it to store the data. I know thats not very clear but different devs put data different places. I can remember early on angry birds and sims 2 put their data in a funky location and apps like TIBU wouldn't back them up so on a flash and restore you would loose game data.

I wouldnt worry about the partitioning its likely to work just fine. Install your apps and use the SDCARD for large data like photos and music and external_sd for more big files.

I currently have about 90 apps installed.
[T-Mobile Samsung Galaxy S II SGH-T989] milenko11:
Has anyone noticed the system ram is showing 784 MB?
[Samsung Epic 4G Touch] kanyewest:
I was out on the balcony and noticed these three antennas. Correct me if im wrong but i think one of them is a 4g antenna. Ive had full bars on my OG Evo and now on my SGSIIE4GT. I know a lot of people say wimax sucks but to me 9 Mbps down 1.5 Mbps down is better than alot of dsl connections people have setup in their homes.
[Samsung Epic 4G Touch] dallastx:
I cant see that close enough to tell who's tower that is. But everyone normally has a tower pretty close to them unless you don't live in the city..The issue is not distance, there's not enough 4g antennas and there want be anymore of those type. Most towers get congested and causes slow data and stay full. Your tower probably is not full. Drive 5 miles and try again.
[Samsung Epic 4G Touch] kynetx:
I could run the test with a panel array up my ass and still get less than 1.5 Mbit/sec.
[Samsung Epic 4G Touch] kgbeezr1:
Prove it :D
[Samsung Epic 4G Touch] txmikester:
Sounds painful. I mean, who can live with 1.5 mbps?
[Samsung Epic 4G Touch] Zoidpilot:
I got the same thing... Two towers within a mile from my apt. I got those speeds indoors too.
[Samsung Epic 4G Touch] Docarut:
I have terrible data where I live. Maybe if I wear aluminum foil helmut my coverage will improve?;)

Doc
[Samsung Epic 4G Touch] DoctorComrade:
The correct response is: "pics or it didn't happen"
[Samsung Epic 4G Touch] JohnCorleone:
Well, at least the IPhone can't take away from my 4G which was 4-7Mbps average and the last two months ..wow!
[Samsung Epic 4G Touch] xenokc:
That speedtest app can show a wild range of results depending on server used. My ET shows only 2Mbps on the speedtest app with nearby servers but when using this site, it shows 7Mbps avg and often 10-15Mbps - indoors. I was able to confirm by doing downloads while tethered. Beware the speedtest app, use this site instead...

http://www.speakeasy.net/speedtest/
[Samsung Epic 4G Touch] graffixnyc:
This was in my house with only 1 bar of 4g. :-)

This is right outside my house with 3 bars (I've seen it faster though)

Sent from my Samsung Galaxy S II Epic 4G Touch
[Samsung Epic 4G Touch] dallastx:
My 4g speeds aren't ever worth showing..Everyone would laugh. 3g and you would wonder even if i had internet.
[Samsung Epic 4G Touch] kingsway8605:
Kanye uses xda?
[Samsung Epic 4G Touch] spdwiz18:
Something to laugh at. At my apartment.

Edit: I guess Having the 4g on would help when running a speedtest. Lol.
[Samsung Epic 4G Touch] spdwiz18:
Retest with 4g.
[Samsung Epic 4G Touch] jdverley:
Lte is even better. My aunt had verizon. We live about 10 miles from the tower and she gets over 20 up and down in our house. I can't wait until sprint activates theirs.
[Verizon Droid Incredible 2] JAS_21:
I have seen multiple users here and on Rootzwiki state that they can't run AOSP ROMS. All the users can run a Sense ROM with no problem, but as soon as they load an AOSP ROM they get freezes.

Edit:

In recovery, be sure to do a full wipe of data, cache, and dalvik cache. It is also recommended that you format your system partition as well. Then install ROM.

If you choose to format the SD card, be sure to back up your important files first.

If you still experience problems running AOSP ROMs (CM7, Liquid, OMFGB, Pool Party) share your results.
[Verizon Droid Incredible 2] sjpritch25:
i was tested different rom's and i've never had an issue flashing AOSP roms. I flashed a few ruu and sense rom.
[Verizon Droid Incredible 2] JAS_21:
I haven't had the issue myself, but I've seen a handful that have. No one has figured it out yet.

Edit: if you experienced this it may help to figure it out
[Verizon Droid Incredible 2] xHoLyx:
Its a myth.

I don't see a reason why it wouldn't work.
[Verizon Droid Incredible 2] JAS_21:
I've seen more than one user with the issue. One is a long time forum member.
[Verizon Droid Incredible 2] franklin270h:
Definitely not a myth. I had issues with aosp roms not mounting data or cache properly. However, newest cyanogen fixed it. Were trying to figure out where the problem stemmed from
[Verizon Droid Incredible 2] pudgewack:
I am having this issue. I was actually running CM7 nightly (with Tiamat) when the problem started. I plugged my phone into my stereo before I went to bed and listened to an album. When I woke up, the screen would not turn on. I rebooted and was stuck in boot loop. I tried to wipe the caches, but got stuck in boot loop. I then upgraded to the most current nightly (with a full wipe), but the phone suffered from the sluggish performance and screen issue.

I have flashed just about every ROM listed in the dev section. Prior to having the issue, I was running MIUI. Prior to that, I was running Newts Incredible 2 HD.

I do NOT have this issue with TSM Pool Party or the past week or so of CM7 nightlies.

I do have this issue with the AOSP Liquid Rom, OMGB, OMFGB.

All sense ROMS work.

I was running andrev_oc when this happened. No overclocking, but did have screen on and screen off profiles.

I have attempted to flash with CWM and 4ext recoveries. Even when converted to ext4, I still have the issue.

Sorry for all the info. I just tried to give as much detail as possible.

Hope this helps,

Matt
[Verizon Droid Incredible 2] JAS_21:
Thank you. If anyone else is having, or had this issue let us know what ROM you noticed the issue on, and what you were running prior.

Also, if anyone has a fix it can be posted here.
[Verizon Droid Incredible 2] dch921:
I have seen this as well. It happened to me when I flash 9.30 MIUI because I was bored. The next morning I restored my cm7 backup and it worked just fine until the screen went off and I would have to pull the battery to boot it back up. Did this several times until I remembered seeing this issue. After several wipes and restores the problem stayed. I finially just flashed a nightly #91 believe I was on 87 before and it has worked fine since. Not sure what was the problem or why it worked flashing a different nightly but I was glad it did.
[Verizon Droid Incredible 2] JAS_21:
Were you running a sense ROM before Miui?
[Verizon Droid Incredible 2] devator22:
I switched from newts Inc hd to liquid, and I had all kinds of problems with the SD card not mounting properly. I ran miui a long time ago with no problems.

Sent from my mobile typewriter.
[Verizon Droid Incredible 2] ftmaniac948:
Went from newts hd to liquid as well, tried restoring my cm7 backup and ran into lockups, reboots, and data lose. Any possibility liquid rom is behind this somehow indirectly? No shot at liquid, just maybe some corrupt files?
[Verizon Droid Incredible 2] JAS_21:
No, other AOSP ROMs were having same problem. It seems that data and cache don't mount properly after running certain ROMS.
[Verizon Droid Incredible 2] JAS_21:
It's starting to look like everyone that had problems with AOSP lockups had been running Inc2 HD prior. I'm not saying Newts ROM caused the issue, since I don't know the cause, but hopefully this can help someone to figure out the problem
[Verizon Droid Incredible 2] knucklesmckay:
Is there a fix? I am running liquid now with no problem. If the system doesn't mount properly when I try to switch, can I just wipe or format system and try to restore a backup or load another rom?
[Verizon Droid Incredible 2] JAS_21:
No, you should be fine.

Most people have no problems. This is for people experiencing random lockups and freezes, not just wit Liquid, but other AOSP ROMs also
[Verizon Droid Incredible 2] ftmaniac948:
Iv been using newts hd rom for a long time now, and never experienced problems with it before
[Verizon Droid Incredible 2] franklin270h:
For me it was data and cache that didn't mount properly. But try the newest cyanogen and see, its the only one that worked for me
[Verizon Droid Incredible 2] JAS_21:
I'm not saying that his ROM isn't running right, but it seems that people are having issues going from that ROM to an AOSP ROM.

Edit: There may be nothing wrong with his ROM, but maybe something is being left behind or not formatted after flashing the AOSP ROM.
[Verizon Droid Incredible 2] PacerguyDon:
Could Newts rom being formatted to Ext4 cause issues when flashing back to a Aosp rom? I've ran Newts Inc2HD and flashed back to Omfgb, but I've been using Ext4 for a while now for my system/data/cache file system (since switching to 4ext recovery). After flashing back, my Aosp rom ran fine. But my backup of Omfgb was already formatted to run on Ext4. Now if my backup was formatted to run on Ext3 for the data/cache, I would think this may cause issues if I don't reformat before flashing a new rom... Just a thought anyway.
[Verizon Droid Incredible 2] MJL99:
I suggested it in the liquid thread but for people coming to aosp from a sense rom, when you wipe, go into mounts in cwm and wipe/format those options too. If you choose to format sd make sure you have a backup because you will lose all data on your sd card. Report your success or not after you have done that.
[Verizon Droid Incredible 2] JAS_21:
Updated OP.
[Verizon Droid Incredible 2] devator22:
I would guess it is an ext4 issue. I am using skyraider Zeus without any problems right now, though. Its an ext3 rom.

Sent from my mobile typewriter.
[Verizon Droid Incredible 2] pudgewack:
I attempted to install Liquid. I did a full wipe. Even formatted everything in the mount menu.

Once installed, the I had the same issue. Sluggish performance and tje screen would not turn on after it was turned off.

I even tried to do the same in 4ext recovery on ext4 and ext3 file systems, but had the same issue.

I appreciate the suggestion, but it unfortunately did not work. If you have anymore ideas, let me know and i will give it a shoot.
[Verizon Droid Incredible 2] franklin270h:
Try either the cyanogen 7.1.0.1 or the latest omfgb nightly. Those are the only ones working for me.

I'm not sure that its the fault of a sense Rom. I think its either 2.3.7 related or something that happened after kernel.org got hacked.
[Verizon Droid Incredible 2] pudgewack:
The current cm7 nightlys and TSM Pool party are working for me. I was just trying to install Luquid to satisfy my flashing addiction. I have not tried the most recent OMFGB, but will give it a try.
[Verizon Droid Incredible 2] icon123:
Unfortunatley, it just affected me. I want to start out by saying that I am not a noob and this is a real problem. However, it appears that it doens't affect most people.

I have been running mostly sense lately, but wanted to try some ics. Started with evan's latest, then TP's v1.1. No problems. Flashed back to my MikRunny nandroid. Then I flashed TP's beta 1 and that's when it happened. Screen goes off and doesn't come back on and system runs real sluggish.

Now anyone of those 3 ics roms does this. No problem with sense roms. The problem also happens with an old miui rom I use to run from August. However, the latest miui and CM7.1.0.1 work fine.

I've done all the normaly wipes/formats and combinations of them, switching between ext3 and 4, nothing helps.

Since this problem happens with roms that use to work prior to this problem, I think it must be something that is left somewhere that our wipes/formats must not be getting to.

The other thing is since some AOSP roms work, it would be interesting to know what the differences are between the ones that work (cm7) and the ones that don't (ics).

Sorry for rambling, but it's truely frustrating. Obvious, if this happend to more people, it would get more attention. I wish I knew what triggered it.
[Verizon Droid Incredible 2] RRF12:
Seems to just effect inc 2's that have been runny mik roms, they must leave something behind that wiping doesn't clean.
[Verizon Droid Incredible 2] faehsemc:
No problem on my side and I run mikrom

Sent from my Mikrunny'd Vivo_w
[Verizon Droid Incredible 2] icon123:
It almost seems that way. Don't want to point fingers and I love Newt's roms, but it appears that most people that run into this problem was running one of his roms. Maybe just a coincidence.

BTW - the roms that aren't working for me anymore don't work through BM either.
[Verizon Droid Incredible 2] HypostaticOnion:
If you're doing a complete wipe it'll get it. It helps to use 4ext recovery as it has super wipe, and wipes system, data, cache, and boot.
[Verizon Droid Incredible 2] icon123:
That's what I use. I have even tried Newt's superwipe script.
[Verizon Droid Incredible 2] JAS_21:
Im not sure if anyone ever got to the bottom of this. All I know is the people who were affected had no issue with Sense ROMS. It only happened when they went back to AOSP. Then it seemed to go away after one of the CM7 updates.

It seemed that certain partitions were affected, like system and cache.
[Verizon Droid Incredible 2] faehsemc:
I actually did have this issue going back to miui recently. I checked partition alignment on 4ext and my partitions were incorrect. I realigned and It went smoothly.. I would still be on it, but for some dumb reason I keep upgrading to .30 and get phone fc so I just restored my backup here

Sent from my Mikrunny'd Vivo_w
[Verizon Droid Incredible 2] RegnierD:
I wish I saw this thread sooner. I'm sure everyone following TP's ICS rom has seen my trials and tribulations. EVERY rom except TP's and Aero's ICS builds works just fine. Even the stock Froyo image was smooth. This includes CM7 and GB MIUI.

I will say that I have not run Newt's HD rom in a VERY long time, so I think leftovers from that are definitely out of the question.

However, about a couple of weeks ago, I gave Liquid Smooth a chance (I'd never flashed it and was curious) and while playing music I had some pretty serious lag issues and eventually my entire GUI froze, but I could still control the music app via the lockscreen. That was the only functional part of the rom. After that, I think I went back to the MT4G Slide port because it was my most recent backup.

Around then is when I started having problems. Maybe a little "Hair of the Dog" theory will work. I'm gonna flash Liquid real quick and see if playing around with that will help.
[Verizon Droid Incredible 2] hokieputter:
just found this thread as well...

i've been having the same issues with any of the ICS roms that icon123 and RegnierD are having. and i've been having these problems for quite a while. i had been running CM7 or MIUI, then tried the original ICS roms (protekk's christmas build and aero's first CM9 kang), which all ran smoothly with none of the issues. then after i went back to my MIUI nandroid (because i need bluetooth and like having a camera), i can't get any of the ICS roms to work right. i do all the standard wipes (even have used newt's superwipe script and/or the 4ext superwipe functions). i don't typically play around with sense roms, but recently did install Mikrunny v1.01 to check it out. when trying to install any of the latest ICS roms coming from either Mikrunny v1.01 or MIUI, i have nothing but problems. i have to pull battery when screen turns off, the system is extremely laggy and unresponsive, hangs up when trying to reboot, etc. all of which are really annoying and just make me go right back to my MIUI nandroid. which runs perfectly. as does any other roms i've tried.
[Verizon Droid Incredible 2] RegnierD:
Alrighty, my next step is to do another full unroot and S-On, and then unlock my bootloader via the HTC Dev Site and see if I can make it work like that. God, I really hope this works. :/
[Verizon Droid Incredible 2] JAS_21:
I'm not sure if HTC unlock is really a "fix". I know some users that were effected a while back tried unrooting and running an RUU, but I'm not sure if it helped.

This issue doesn't seem to effect many people, and some may not realize it. I've seen users post that an AOSP ROM is giving them problems, so they flash back to whatever they were using and just blame it on that ROM.

Hopefully someone figures it out at some point. I've never experienced it myself, but it seems the users who have all went from a Sense 3.5 ROM back to AOSP at some point. I never have flashed a Sense 3.5 ROM myself. No matter how "pretty" they are, I like the plain android feel.

I wish I could help figure it out, but my knowledge only goes so far.
[Verizon Droid Incredible 2] beaton3344:
I've done everything too. I'm done spent several days trying to figure it out. Tried both recoveries clockwork and ext4. Messed with partitions. All roms work for me except ICS. Im on liquids 3.2 now working perfect. I wiped SD card with laptop. Deleted all partitions. Formatted and formatted. Its for sire not SD card. Its something else. Only other options I can think of is maybe it is something to do with cloud. Maybe in our Google accounts. Going to try and clear something's off tomorrow.

Also I had touch pros beta 3 running perfect at one point. Then tried areos rom. Then used my backup of touchpros. Got everything back to normal. Plugged my phone in and woke up next morning screen was black and bottom keys where lit. That is when it happened to me...

If that may help anyone...
[Verizon Droid Incredible 2] beaton3344:
Nobody. It has to be a screen on off issue. Happens when you get a phone call and the sensor shuts screen off. Same issue can not turn on screen after that.
[Verizon Droid Incredible 2] beaton3344:
Any luck.
[Verizon Droid Incredible 2] beaton3344:
Just thought of something. This issue seemed to have happened when I started tethering using beta 11 wifitether the yellow one... never used it until recently. Could any of those settings that you guys can think of possibly have done this. Also any of you guys having the issue do the same.
[Verizon Droid Incredible 2] mdspace:
It started on my phone after I flashed the GPS patch.
[Verizon Droid Incredible 2] hokieputter:
hmm.. i also flashed the GPS patch. but i definitely can't pinpoint the problems starting exactly at that time.
[Verizon Droid Incredible 2] beaton3344:
I never flashed the patch. God this is crazy. Has to be something in ICS code.
[Verizon Droid Incredible 2] RegnierD:
If anybody knows anything about logcats:

http://pastebin.com/WBFB19ZD

There's a WHOLE bunch of them there catching errors on a reboot after a battery pull.
[Verizon Droid Incredible 2] beaton3344:
I done. ICS sucks. Have you guys tried Bullet 1.4. Nice rom I'm not going back to ICS even if we do find a fix. Bullet is much better.
[Verizon Droid Incredible 2] hokieputter:
anyone respond on the logcats? wish i knew what i was looking at.

still a no go here. tried every imaginable wipe/format combo, freshly formatted SD cards, etc. just attempted again (for grins) with TP's beta 6. same result. super sluggish and black screen of death the first time the screen turned off.

ANNOYING!!
[Verizon Droid Incredible 2] dirtysox:
If you wanna know about lolcats, you should really post your question on icanhascheezburger.com.

This here is teknikal forrum abowt androyd fonz, nawt pitchurs of kittehs.
[Verizon Droid Incredible 2] beaton3344:
Ok couldn't stand it. Tried beta 6 touchpro. So digging some more into it. Looks like our problem is with the system not mounting properly. Last night none of my data was saved after reboot. I use ext4 tried switching system data and cache to ext3 and ext4. Neither worked... Can someone who has more experience with system data mounting help. I'm sure that at boot something forces our system data or cache to the wrong partition weather it is ext3 or ext4. The partition print out says system ext4 data ext3 cache ext3. Tried to switch system to ext3 sticks until reboot. Hope this all makes sense to someone. Lol.
[Verizon Droid Incredible 2] beaton3344:
Also when I install an ICS Rom the offset at the beginning is different every time. What does that mean? And is everyones the same.
[Verizon Droid Incredible 2] crackedvenom2:
Bump. This is happening with me too. I've tried everything.

I'm in a thunderbolt but I want to come in since I found this via Google. Maybe if you guys figure out out, it'll help me too
[Galaxy S II Q&A, Help & Troubleshooting] cyprusx:
hey guys

Im trying to copy over 6.54GB mkv video file through the USB cable. Every time I start the transfer it, about 10min into it at about 90% i get an error that says "The device has either stopped responding or has been disconnected."

Any ideas guys? thanks
[Galaxy S II Q&A, Help & Troubleshooting] Teio:
You cant transfer files over 4GB to your phone...

You may try splitting it in 2 parts