yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Q&A, Help & Troubleshooting] Twolazyg:
1. What ROM are you running?

2. Did you do a nandroid?

3. Nand restore...

Let me know how that works for you
[Hero CDMA Q&A, Help & Troubleshooting] PMGRANDS:
The Rom I'm Using Is "FroyoSense- V8.1" (*Only Cause V8.5 Wouldn't Boot*)

Also I Did Make A Backup, But For Some Reason It Still Happened! I Ended Up Doing A "Full-Wipe" & Re-Installing The Rom Again!! Which I Thought Was Straight, Until Today.... When That Damn Issue ReOccurred!!
[Hero CDMA Q&A, Help & Troubleshooting] Twolazyg:
So try doing a nand restore from a time when this didn't happen.. Or try a different ROM.
[Hero CDMA Q&A, Help & Troubleshooting] PMGRANDS:
OK, I Guess Could... Only Thing Is, I Don't Think Theres That Many ROMS Out There With Both Froyo & Sense On Them!
[Hero CDMA Q&A, Help & Troubleshooting] Twolazyg:
No, there isn't. Maybe the Rom file you downloaded was corrupt. Try re-downloading it and flashing, and if you still have problems do a logcat and send it to the dev who made it.
[Hero CDMA Q&A, Help & Troubleshooting] Twolazyg:
You really ought to search for some. After 1 min, I found a stable CM6 sense ROM and a stable AOSP sense 2.2 ROM. Try searching and see what you come up with. Good luck

Sorry for the double post :D
[Hero CDMA Q&A, Help & Troubleshooting] PMGRANDS:
Have You Tried To Install Either Of The Sense Roms? Cyanogen or Aosp? I Believe I Installed The Cyanogen Rom & When I Flashed It It Was Just The Regular Cyanogen, With The ADW Launcher! Though It Said CyanogenSense!
[Hero CDMA Q&A, Help & Troubleshooting] Twolazyg:
No, I haven't and won't. I don't like sense at all. Plus, it's a sense THEME, not a sense ROM. Sense is tied in with the framework so much you can't just pick and choose what you want from it.
[Hero CDMA Q&A, Help & Troubleshooting] PMGRANDS:
If You Don't Mind Me Asking, What ROM/Launcher Do You Prefer? I Choose Sense More or Less Because: I Haven't Found A Widget For The Music Player or The Bookmarks That Compares!! Know Of Any?
[Hero CDMA Q&A, Help & Troubleshooting] Twolazyg:
Right now I'm using Blackmod for CM6.2 with adw.launcher
[Hero CDMA Q&A, Help & Troubleshooting] PMGRANDS:
Is Everything Stable On It? I Was Using BlackMod A Few Months Back & I Was Having A Issue With My Em@il, & My Text Messages, I,Was Receiving "Both" Whenever They Felt Like it! Lol! But Like I Said A Few Months Ago, These Developers Are So Sick With It, They

Can Fix Almost Anything!!
[HD2 Android Q&A, Help & Troubleshooting and Genera] AngelDeath:
Okay before anyone starts to flame or start saying "Oh God" to the screen, this isnt the typical "When are we going to get Android to boot from HD2" question.

I know we all boot Android from our SDCard, but I went looking to see if there was any google pages on why the sd card? Being that we have an HD2 and it has alot of space (My phone says 768mb free internal storage), would it slow Android and the experience down if we had the "Android" folder copied to our phone instead? I know currently it probably wouldnt work, but being that the avg Android folder is 230mb to 260mb thats more then enough space to put the folder in, and possibly change maybe the daily useage or app installations onto the sdcard. If this was just a general rule of thumb that it was decided to be put on an sdcard across the board because not all phone had the room then is there no way to change that now since most phones are coming out to have larger internal space opposed to older ones?

And again, would it be slower to run this way or not?
[HD2 Android Q&A, Help & Troubleshooting and Genera] mally2:
hi

Haret cannot currently read from NAND, its code reads and searches for Data IMG and Rootfs and kernal in SD ONLY .....

hence NAND is so very different from HARET.

well Magldr is what would do the trick
[HD2 Android Q&A, Help & Troubleshooting and Genera] AngelDeath:
I'm assuming your talking about nand as to boot from the phone like as if you are powering it up and windows loads, Im not actually talking about that. I'm actually talking about how it currently loads, except, instead of placing the Android folder on the SDCard and running clrcad and haret, instead placing the folder into the root directory of the phone and running clrcad and haret from there, same exact way we are running it now, except changing the location of the folder from card to phone.
[HD2 Android Q&A, Help & Troubleshooting and Genera] mally2:
hi

Well firstly NAND does not necessarly mean booting from start, NAND= Internal memory, in fact cotulla's MAGLDR can boot android of the SD straight from power up whilst having WIN MO on NAND.

So to answer your question again,

HARET CANNOT READ NAND (INTERNAL MEMORY), it always looks for SD for everything , in some cases RAM, as in the new RAM builds that are popping up by devs.

the code for HARET cannot handle NAND at the moment and i dont thing it will ever be implemented.

I'm neither a dev or a hacker, this is just what i ahve understood from reading, i'm open to corrections, :)

best regds
[HD2 Android Q&A, Help & Troubleshooting and Genera] greg17477:
I have to admit, this idea is very cool.. If haret could "see" the nand memory after WinMo is loaded, then all you need is a WinMo rom stripped down to the maximum and Android folder burned in it (at least the system part). if if if :D i am not sure, if its technicaly impossible for haret to see the nand memory after booting WinMo or if its impossible at all..
[HD2 Android Q&A, Help & Troubleshooting and Genera] mally2:
guys remeber HARET is a bootloader for LINUX, its crazy enough its helping us boot android from SD, I think the possible reason HARET is not designed for reading NAND is the potential damage it could do to SPL leading to a BRICK, now we dont want a brick do we ? :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] greg17477:
never say never and expect the unexpected, thats what life teached me :D

phone wouldnt get bricked if you just read nand, but writing into it could do damage, i agree on this.
[HD2 Android Q&A, Help & Troubleshooting and Genera] huggs:
OK, so when I first read the OP, I thought he meant booting Haret from the phone's internal storage memory, not NAND.

Though the NAND Haret idea is really not bad, I couldn't see it corrupting the bootloader as long as it behaves the same way as it does from the sd. I mean, the phone is already booted WinMo, so HaRet and Android have no need to touch the bootloader, just as when running from sd. It would be more or less a startup.txt change/ rel_path = NAND/Android (not exact, but general idea). Seems alot different to me from MAGLDR, maybe there is just confusion about this

But if the NAND idea is not workable, wouldn't it be possible to run HaRet Android from the phone's internal storage memory, yielding a performance speed increase and less wear on the sd?

Clearly we couldn't do like I have now, a ton of builds with exceller, all running from internal storage, obviously we don't have 16gb internal. But what about just loading our daily driver from internal, and testing/less commonly builds from sd?

I like the idea because it could mean less wear on the sd, and possibly performance increase

:DBTW 300th post:D
[HD2 Android Q&A, Help & Troubleshooting and Genera] AngelDeath:
Thats exactly what I meant, once WinMo is loaded, we normally go into the sd card thru file explorer and then go to android and then run clrcad and haret, winMo is already loaded and doesnt corrupt winmo, but if we could run the core system from the phones storage space, (Putting the android folder into the main directory, and then running clrcad and haret, this way the core system would load and any user installable files would just end up on the storage card, cause obviously we wouldnt be able to load all our apks into the phone (Some might, others like us go nuts).

But the concept is not a bad one, especially if there was a way when installing the apk's it asked for the location to add.
[HD2 Android Q&A, Help & Troubleshooting and Genera] huggs:
I would say that if HaRet was pointed to the correct place correspondingly, either NAND or storage would work as I previously mentioned. I am unsure about any performance gains to be had, but it would surely save on sd card wear.

People say that going from NAND would corrupt bootloader, but since WM is already booted using HaRet, there is no reason that the bootloader is touched, even if it is all stored to NAND. MagLDR is different, that is going for a cold-boot of Android, no WM involved at all. HaRet and MAGLDR work different and I think that if Haret was made to look for /Android in NAND, it could work just the same as if off of sdcard.

And booting from the phone's storage memory would be even safer, as no far-fetched idea of HaRet corrupting the bootloader is even conceivable, as NAND would never even be touched at all.

I honestly believe though that if a version of Haret was released that looked to NAND memory for /Android, that WM chefs could bake lite version WM ROMs with popular Android builds already built into NAND, maybe in the \Windows directory. The chef could even cook in a modified version of Exceller's Android loader which would look to \Windows for the Android folder.

Since Android development is so far along, and there are so many builds that are 100% or near 100% stable, I do think that going this route is a viable option, I mean there are already WM builds that will install an Android build to the sd card all by themselves after you boot them up the first time. This seems a natural progression of that concept to me.

Maybe somebody could contact Netripper, and ask him more about this idea, and see if he would be kind enough to build a HaRet version to look to NaND memory, and another to look to internal storage space, the rest could be done by the end user, as there are WM kitchens available, and most ppl here could make a .cab to install \Android to internal.

That's my $0.02 :p
[HD2 Android Q&A, Help & Troubleshooting and Genera] mally2:
Very possible,

Haret needs to be modified for that,

not sure who can do it.
[HD2 Android Q&A, Help & Troubleshooting and Genera] greg17477:
Guys as far as i know, on hd2 is nand memory the same as internal phone memory.There is no built in sd card. I am not 100% sure, but there is 512mb nand memory (internal memory). I mean, we install winmo roms into the nand. So if your winmo rom is about 200mb, you will be left with soemthing like 300mb internal phone memory. Correct me, if i am wrong..

cheers
[HD2 Android Q&A, Help & Troubleshooting and Genera] mally2:
spot on

NAND = Internal memory
[HD2 Android Q&A, Help & Troubleshooting and Genera] huggs:
Well true except the TMOUS, which is 1024 mb, so it should be plenty then to run Android this way right?

Even with just 300 left after WM ROM, Android could still be done conservatively, without much apps installed, or with some kind of a2sd functionality, Froyo has inbuilt app to sd functionality, albeit not as good as a2sd ext2 or ext3 setup.
[HD2 Android Q&A, Help & Troubleshooting and Genera] TheATHEiST:
Guys I think you are missing the point, If this was possible, viable or worth it, it would have probably already been tried and tested and released along time ago.

The fact that this hasnt been done already tells me that its been thought about and rejected for good reason.

PS. NAND ..IS.. Internal memory guys so the running loading of kernel and files from internel memory instead of nand is a moot point.
[HD2 Android Q&A, Help & Troubleshooting and Genera] dharvey4651:
Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...

What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.

To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?

To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.
[HD2 Android Q&A, Help & Troubleshooting and Genera] mally2:
hmmm,

well in that case, kernel could be programed to create Data IMG on SD, if you have been following the Rhodium Nand Project , you will see what i mean, a few components are on NAND and a few on SD
[HD2 Android Q&A, Help & Troubleshooting and Genera] greg17477:
Its not about putting the whole Android folder into nand, but for example only the system partition, just like in the RAM builds. All data and user stuff goes to sd.

Btw what do you mean by "...*could* be possible to put Android on internal storage(NOT NAND)." ? nand is the internal storage (memory). Or you guys are using different terms ;) do you mean by "nand" the reseverd space where roms are stored and by "internal storage" the free space left (still in nand)?
[HD2 Android Q&A, Help & Troubleshooting and Genera] AngelDeath:
Actually your part right, it was tested and released in the initial phases of the Rapheal (aka Fuze) and ran smoothly from what I read, yes there were hiccups, but that was due to the build being still in the alpha stages.

This is where your part wrong as well. if you use a pre-set data.img file, yes for the most part you cant use anything larger then possibly 512mb on a TMous, 256 on others, definitely could not use the 1gb img file thats for sure, but the other part of this your missing is that if you dont put a pre-set data.img file, during the initial loading of android, android will create the file itself, and IF I am right the file will be sort of dynamic, dynamic in the sense it will expand as needed, I seriously doubt it shrinks. And on top of this you would then use the function a2sd, which in then would install your apk's to sd card. As of right now how much bigger is your 1gb data.img file that everyone added to their SDCards? Bet still the same size.

Actually after doing some reading, neither the kernel (if I read correctly) nor is haret.exe the cause of pointing the boot location. I did some searching (Mind you I am NOT a LINUX person), but reading some of the files, I am guessing that the key file which controls the loading of Android, is located in the "init" file in the rootfs.img file. I mounted this file in windows to look thru it and view files, and that file seems to have a major role in it, how it works I dont know yet.

To All, please I am not trying to cause a stir here, I am merely looking at possibilities, and unfortunately I cant test them out since I dont have a spare SDCard as of yet (Will ina couple of days, 32GB SDCard for $40, woohoo), and then I have nothing to loose to try, cant brick the phone, since winmo is the default loading OS anyway. One of the reason it might not have been put on the phone as I said, could be speed, I dont know how much faster internal phone storage would be opposed to sd, but another reason why could be cause then the installation would put folders on the root file system of the stroage card and make it messy. Also alot of people constantly flash new builds, this would also hamper your android install being on the phones storage. And remember our normal HD2 roms are between 225 and 250mb stock or custom, where lite versions or stripped down version would be considered better for taking up less space.

One thing to keep note, during all this, I have an HTC Aria (Liberty) as well that I just recently got as an upgrade to one of my ATT lines, and I checked the internal storage of that phone, its stock with ATT's build of Android, and it has ONLY 168mb of storage available, and it came with a 2gb sd card. Now think about that when saying that the files would get to big, obviously the HTC Aria doesnt have anywhere near the capacity of the HD2.

And again to anyone else, let's be clear, yes the phones storage is a NAND, but just to make clear, we aren't talking about doing a cold boot of android, I know how sometimes that can get confusing.
[HD2 Android Q&A, Help & Troubleshooting and Genera] huggs:
Sorry guys, yes internal storage is NAND memory, the reason I drew a distinction was to make a distinction between loading from internal storage and ROM space. I only meant to illustrate the difference between the two and demonstrate my opinion that both are possible. I think with further investigation and testing, advantages of booting this way will begin to emerge. For example we will be able to remove the sd card while Android runs, not a great benifit, but you get the idea. But yeah, I should have used the term 'ROM Space' instead of NAND, I only meant to show difference between the 2 places to boot from.

Sorry if i caused any confusion.

Sent from my... whatever
[Fascinate General] wphilly:
Hi there, Fascinate people!

I have a Captivate on AT&T (a.k.a. the my-signal-runs-away-from-buildings carrier). One of my absolute favorite features of my phone--a feature I had believed was common to all Galaxy S models--is the seemingly indestructible Gorilla Glass screen. I've carried this phone naked in my pocket for months now and the screen is still perfect!

A friend of mine liked my Captivate so much that she purchased a Fascinate as her very first smartphone. She put a screen protector and a case on it (two safety mechanisms I've blatantly rejected in favor of the uberslim Captivate), but not two days after purchasing the phone, she had scratch marks in the glass, below the screen protector in the soft button area. Granted, she has probably been carrying the device in her purse, but nonetheless I was blown away by this! I inspected it further today, and it actually looks like the scratching may be below the surface of the glass.

So my question is this: wtf? Is the Fascinate screen wimpier than the rest of the Galaxy S line? Is it possible that dust entered the phone and scratched the surface below the glass surface? Is this the sort of thing she might get an exchange for? Has anybody else experienced this, especially so quickly after purchasing?

Thanks for all of your help!
[Fascinate General] RacerXFD:
Ask the someone who knows... Ask samsung... I have no idea.

This just sounds like you are blaming us for your friend's woes. I feel like giving you the benefit of the doubt for now.

Anyways, ask them or VZW.

I haven't had any issues that you mention.
[Fascinate General] mikey6p:
I've dropped my phone and had it unprotected since I bought it and it still looks brand new. No idea what's up with your friends phone.
[Fascinate General] soba49:
The fascinate does have gorilla glass. It holds up to a lot of abuse: you can't scratch out with keys, etc.

I can't speak to scratches below the screen, never seen anything like that.

Gorilla glass can be scratched (especially by any form of sand, which is more common than you might expect), and it can shatter. This is discussed in the accessories thread.

You also have a few options if you want to keep your phone thin. Look into steinheil, real look etc.screen protectors, also discussed in accessories.

Sorry to hear about your friend's screen. Tender care and a soft clean pocket will get you pretty far, but the back cover especially will scratch up on you no matter how careful you are. Fortunately the back is cheap to replace.

Swyped w/ XDA App. When in doubt, mumble.
[Fascinate General] wphilly:
I'm not sure how that would sound like blame, but I was really just asking if anybody had any similar experiences :)

Likewise - that's what made me question it.

Right! This was the video demonstration I'd seen, so I was very confused! Sand makes perfect sense! She was near a beach for a few days immediately after getting the phone. Thanks!!
[Fascinate General] J Shed:
Jewelry is a common scratcher too.

I have a screen protector on my phone, just in case... its an invisible shield, so it covers the whole screen. I passed on the VZW ones because I figured it just covered only the screen, but the invisible shields do have an orange peel kinda look to them.
[Fascinate General] Jrex:
I have been carrying my fascinate since launch unprotected in my pocket, and my screen is still flawless! I just bought a protector from a local uscc store for the mesmerize that covers the whole screen yesterday! 3 in a pack for $14.95, they fit well (except for maybe 16th of an in. at the edges) and they cover the whole screen!
[Fascinate General] Mylt1:
2 small scratches and 1 small scuff mark on my screen and i have been VERY careful with this phone. not that impressed with the glass. took me weeks to scratch the screen on my TP carrying it the same way i carry the SF. i need to pick up a protector just to prevent any more marks.
[Captivate Q&A, Help & Troubleshooting] EpicYuzer:
I bought a Captivate with rogers on 2.1 update 1 today and when I connected it to my PC it wasn't recognized, installed the drivers and it's still stubborn. I booted into Ubuntu 10.10 and still same problem! I can't stand it it's driving me crazy! there's no reason why it should be doing this but I can't make it work!!! Please someone help I am really desperate :(
[Captivate Q&A, Help & Troubleshooting] axis01:
There are several reasons this could be happening. A search will come up with all of them. For me, it was the USB port on the computer. It didn't like the remote ports. Once I plugged into one of the ports directly off the MB, works everytime.
[Captivate Q&A, Help & Troubleshooting] CatFan:
You might never get it to work

I've been reading these posts and trying suggestions since I got my Captivate back in August. I still have not been successful in getting any kind of reliable connection between a computer and my phone. This is my second phone and I have tried 5 different computers. One of the computers was tried with Win XP, Windows Vista and Windows 7. Nothing seems to get me a reliable connection. I hope you have better luck. I get a wild hair every now and then and spend a few more pointless hours trying to make it work but to this point nothing is working. I've tried Kies, Kies mini, old drivers, new drivers, 32 bit drivers, 64 bit drivers, etc. NOTHING HAS WORKED. I've managed to be able to mount my drives and copy files occasionally but no kind of sync where anything is automated. Also I have found nothing that can get me any sort of contact or calendar sync with Outlook. My work prevents me from putting everything into Google mail and syncing that way so I'm just out of luck with a phone that ATT told me I could sync with Outlook. Maybe Froyo will fix this or else I have to wait my year until I'm eligible for an upgrade to get a phone that actually works properly (ie, non Samsung), although I have to wait for OTA Froyo since Kies won't be of any help in upgrading anything!
[Captivate Q&A, Help & Troubleshooting] silvertag:
This is the best drivers i found to make it work on my Vista box.

http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
[Captivate Q&A, Help & Troubleshooting] avgjoegeek:
The USB drivers from Samsung's website seem to be pretty bogus.

If the ones from the link above don't work you can go here - and download the USB drivers for your OS there. I have tested both and they work great on my computers.

And... if your running Vista - IMO That is Issue #1 :D
[Captivate Q&A, Help & Troubleshooting] silvertag:
:p ... That OS was never a issue for me.. i found the user using it is often the #1 issue :D
[Captivate Q&A, Help & Troubleshooting] avgjoegeek:
LOL I refused to run it. For some reason my systems refused to run it and I always ended up going back to XP.

Now with Windows 7 - I think Microshaft got it right (as close as they can) and its what Vista should have been to begin with :D
[Captivate Q&A, Help & Troubleshooting] jatkins09:
This may seem obvious, but I didn't see it mentioned here. Do you have USB debugging checked? I remember having that issue back in July, when I was just a little noob :)