Database Develop

[Q] Poll On Successful Update to Froyo for I9000(m)

I would like to know how many of you had successfully updated their SGS (Samsung Galaxy S) to Froyo. I think this will help us understand the failure rates so people who do not want to risk bricking their phone.
1) Updated with no problems
2) Updated with problems
3) Tried to update and having problems
4) Did not update at all

If you are talking about roms.. Well most are a 1. I habent heard of an official froyo update. And.if.you by chance do.brick it, there are ways to unbrick it pretty easily.
Sent from my SAMSUNG-SGH-I897 using XDA App

I have the Bell Vibrant which is the I9000M.
I thought that Bell released an official update for their new Froyo. Check it out here
mobilesyrup.com/2010/12/08/bell-samsung-galaxy-s-vibrant-upgrade-to-os-2-2-froyo-coming-december-10th/

Did update my Bell Samsung Galaxy S GT-I9000M with Bell release Froyo available using Kies and all seemed to be running smoothly until I had issues connecting my bluetooth and trying the voicedialing features that did not work in my case and after got Force close on every apps. Did a shutdown and got the device in a loop at boot up.
Will try tonight to reload the device with 2.1 and see from there to retry 2.2.
Finger cross !

I upgraded with no problems but I did do a factory reset as things started to get a bit slow and from what Ive read it is a good idea to do a reset to get rid of any residual 2.1 stuff on the device. Since then the update has been working well for me...
KNOCK ON WOOD!!!

I have 2 SGS phones so you'll just have to add another vote to the "successful upgrade" option in addition to the one I was able to cast
I've flashed the following 2.2's without any problems so far:
- unofficial JK3 (Canada) via ODIN
- official JK4 (Canada) via Kies
- straight JPU via ODIN
- JPU Doc RomMOD v2 via update.zip recovery
No problems with flashing.
And yes, clearing data & cache is helpful (mandatory?). Backups are good!

there is NO problem upgrading.
the Internal SD failure comes AFTER you have SUCCESSFULLY upgraded the phone, a few hours to a few days later
ssj2miguelx said:
I would like to know how many of you had successfully updated their SGS (Samsung Galaxy S) to Froyo. I think this will help us understand the failure rates so people who do not want to risk bricking their phone.
1) Updated with no problems
2) Updated with problems
3) Tried to update and having problems
4) Did not update at all
Click to expand...
Click to collapse

AllGamer said:
there is NO problem upgrading.
the Internal SD failure comes AFTER you have SUCCESSFULLY upgraded the phone, a few hours to a few days later
Click to expand...
Click to collapse
Cool. That makes this type of poll misleading then because someone reporting success today may have issues tomorrow (we can't change our vote correct?).
That's right. I saw your post about your phone going bust. Sorry to hear that.

I just can't get Kies to work -- it just says "connecting to device" and it hangs
Also can't install MPT USB drivers -- always fails. I installed the correct x64 bit Windows 7 drivers and everything.
Ughh

Wow. I didn't think people would have problems after the update. Man, I really should wait until we all know that its okay to update. I am new when it comes to the SGS so if I fail at it, I don't want to start crying. This is such a nice phone....so if it works, why break it?

ssj2miguelx said:
Wow. I didn't think people would have problems after the update. Man, I really should wait until we all know that its okay to update. I am new when it comes to the SGS so if I fail at it, I don't want to start crying. This is such a nice phone....so if it works, why break it?
Click to expand...
Click to collapse
Same - I am hessitant now to upgrade.
I had one of the original phones, it sucked, no GPS, etc. and it died on me.
I got a new phone, for free, my buddy works at bell, GPS works fine, and this one I think had the internal card failure b/c one day it just went black - reboot and the bottom lights light up but it doesn't boot in.
I did a recovery mode -> hard reset seemed to fix it -- tho i lost all my apps and contacts etc.
Now I haven't rooted or lag fixed, but I REALLY want froyo.
But what's the point ? I already had to do a reset b/c of internal card failures in the past, that means im almost guaranteed to lose this one if i upgrade,...

Funkadelick said:
Same - I am hessitant now to upgrade.
I had one of the original phones, it sucked, no GPS, etc. and it died on me.
I got a new phone, for free, my buddy works at bell, GPS works fine, and this one I think had the internal card failure b/c one day it just went black - reboot and the bottom lights light up but it doesn't boot in.
I did a recovery mode -> hard reset seemed to fix it -- tho i lost all my apps and contacts etc.
Now I haven't rooted or lag fixed, but I REALLY want froyo.
But what's the point ? I already had to do a reset b/c of internal card failures in the past, that means im almost guaranteed to lose this one if i upgrade,...
Click to expand...
Click to collapse
If your card is gonna die its gonna die no matter if you upgrade or not....Flashing just seems to speed up the corruption.

Thats a good question. People seem to be having big issues with this new Froyo update here, http://forum.xda-developers.com/showthread.php?t=867157. I really hope Bell gets a fix for this new "firmware Froyo 2.2" that they just released.
If the Nexus S is the so similar to the SGS I9000M why dont we have Gingerbread (2.3) yet?

Again people. It's not the froyo update that's a problem it's bad internal SDcards. These phones were dying before froyo came out and without ever flashing anything.
If they're gunna die, they're gunna die. Flashing just helps to speed up the failures. SO flash away and hope it blows before your warranty is up.

Funkadelick said:
Same - I am hessitant now to upgrade.
I had one of the original phones, it sucked, no GPS, etc. and it died on me.
I got a new phone, for free, my buddy works at bell, GPS works fine, and this one I think had the internal card failure b/c one day it just went black - reboot and the bottom lights light up but it doesn't boot in.
I did a recovery mode -> hard reset seemed to fix it -- tho i lost all my apps and contacts etc.
Now I haven't rooted or lag fixed, but I REALLY want froyo.
But what's the point ? I already had to do a reset b/c of internal card failures in the past, that means im almost guaranteed to lose this one if i upgrade,...
Click to expand...
Click to collapse
If I was you I'd flash the crap outta your phone. If your black screen was due to a weak internal SD then it's gunna go. So flash it and hope it goes so you can get a new(repaired) one. Of course the wait time is a bit long right now for repairs. And there's no guarantee that the newly repaired one won't blow.
Damn this phone....

And yes, clearing data & cache is helpful (mandatory?). Backups are good!
Click to expand...
Click to collapse
How to do it?
It will delete also my files (photos, music....) on the internal memory?
Regards
Sent from my GT-I9000 using Tapatalk

AllGamer said:
there is NO problem upgrading.
the Internal SD failure comes AFTER you have SUCCESSFULLY upgraded the phone, a few hours to a few days later
Click to expand...
Click to collapse
yeah!
my phone upgrade went well..but i have occasional force closure on apps. Then one day it just hang using Msn Talk Pro and I had to pull the battery out to reboot and it never came back on - stuck after the bootup S logo. grrrr..
how long does the warranty repair usually takes?
Anyone in Vancouver Canada that are non Bell subscriber have any problem bringing it in? Which store do you guys go to? I will try the same store for hassle free repair job. Thanks

Videonut said:
Again people. It's not the froyo update that's a problem it's bad internal SDcards. These phones were dying before froyo came out and without ever flashing anything.
If they're gunna die, they're gunna die. Flashing just helps to speed up the failures. SO flash away and hope it blows before your warranty is up.
Click to expand...
Click to collapse
Is there a chance that my phone has a bad internal SDcard?

betaboy00 said:
yeah!
my phone upgrade went well..but i have occasional force closure on apps. Then one day it just hang using Msn Talk Pro and I had to pull the battery out to reboot and it never came back on - stuck after the bootup S logo. grrrr..
how long does the warranty repair usually takes?
Anyone in Vancouver Canada that are non Bell subscriber have any problem bringing it in? Which store do you guys go to? I will try the same store for hassle free repair job. Thanks
Click to expand...
Click to collapse
Took mine into the bell store at guilford mall, originally purchased at wireless wave.Unlocked and being used on the fido network. No issue at all, the guy took down my cell number as a way to track its progress.

ssj2miguelx said:
Is there a chance that my phone has a bad internal SDcard?
Click to expand...
Click to collapse
There's no way to know for sure. Some ppl seem to have a bunch of force closes bfore it dies and others just turn it on and it's dead.

cm7 broke my nook

I put in CM7 two days ago, and every thing was working fine. I restmy nook and it would not power on at all. I tried for 2 hours, and nothing. I was able take it back to the store and get a new one. What could cause that problem? After I installed cm7 it worked fine, I then took my sd card out reformatted it to put files on it. Then when I reset my nook and no power, no nothing.

Same Issue
I had the exact same thing going on. I installed CM7 and it worked great for a cpl days. Last night I plugged it in to charge it (left it on), and when I woke up it was off and unable to turn on. Black screen.
I put in my CWR sd card and held the nook, volume up, and power buttons to turn it on. I figured I just go back to eclair auto-nooter because I know its stable, so I formatted system and data and flashed the stock barnes and noble 1.0.1 rom. However...
I still have the same issue. The device doesn't power on. I'll return it to the store if I have to, but I'd prefer to fix it so that we can raise awareness.
Edit: I figured it out. The flashable repartition-boot-with-stock.zip was corrupted on my CWR sd card. I made a new one and I'm right as rain. Follow the instrustins HERE to fix the black screen issue with CM7. Although it will restore you NC to stock.

More than likely something happened to your boot partition. Please investigate the threads titled "guide to my nook won't boot"

jd95 said:
After I installed cm7 it worked fine, I then took my sd card out reformatted it to put files on it. Then when I reset my nook and no power, no nothing.
Click to expand...
Click to collapse
Thread should be called, I didn't read the directions and broke my nook. cm7, as well as all the other froyo/ginger roms that I've seen run off of the sd card. If you wiped those files off, it shouldn't be expected to still work.

jeremiah_mn said:
Thread should be called, I didn't read the directions and broke my nook. cm7, as well as all the other froyo/ginger roms that I've seen run off of the sd card. If you wiped those files off, it shouldn't be expected to still work.
Click to expand...
Click to collapse
The CM7 nightlies are not meant to be run from the SD card. There is also a build of HC that is not meant for the SD card. In my experience, nookie froyo ran better from the sd card, but it could also be run off internal storage.
So i respectfully disagree with your opinion. Which was actually a statement of incorrect facts.

jeremiah_mn said:
Thread should be called, I didn't read the directions and broke my nook. cm7, as well as all the other froyo/ginger roms that I've seen run off of the sd card. If you wiped those files off, it shouldn't be expected to still work.
Click to expand...
Click to collapse
You're wrong here, I don't believe CM7 even comes available for SD card, it's an internal install..
And there is a very common theme here... Install CM7, works fine, reboot, it's dead.. Have to do XYZ to get it back up running. Something is hosing something, surprised nobody has figured it out yet.
I remain on rooted Stock 1.0.1.

sparhawk36 said:
More than likely something happened to your boot partition. Please investigate the threads titled "guide to my nook won't boot"
Click to expand...
Click to collapse
Not trying to be a ****, but I did exactly what you said, and stated so in my post.
I followed the instructions listed here
I've actually done this many times in the past. Most of the time its because I'm messing around in adb. I even keep a spare sd card with me, ready to do this at all times.
In this instance, however, it is not fixing it.
Fixed it. My sd card went bad. The post in the link still works, although it restores your NC to stock.

khaytsus said:
You're wrong here, I don't believe CM7 even comes available for SD card, it's an internal install..
And there is a very common theme here... Install CM7, works fine, reboot, it's dead.. Have to do XYZ to get it back up running. Something is hosing something, surprised nobody has figured it out yet.
I remain on rooted Stock 1.0.1.
Click to expand...
Click to collapse
Ive done all kinds of stupid things to my nook including an attempted install of Slackware... but I have never bricked it. Ive been running the CM nightly builds without any kind of problems as well. Well, no problems outside what one would expect from development software that is still in a rapidly changing state. If you want stability and reliability, EMMc installs of CM and HC and even Froyo are probably not where you want to look right now.

admiralnorman said:
Not trying to be a ****, but I did exactly what you said, and stated so in my post.
I followed the instructions listed here
I've actually done this many times in the past. Most of the time its because I'm messing around in adb. I even keep a spare sd card with me, ready to do this at all times.
In this instance, however, it is not fixing it.
Fixed it. My sd card went bad. The post in the link still works, although it restores your NC to stock.
Click to expand...
Click to collapse
So to be clear here, your problem with CM7 not booting was related to your SD card "going bad"? Or was your restore process hampered by this?
You had installed CM7 to emmc and such, right? How would the SD card be affected by that?

If you formatted your card in your NC then that's the problem. Don't format your card with CW because it'll wipe the boot sector giving you a black screen. It's fixable, many people have made the same mistake on the #NookColor channel. Go there for help because it's faster than waiting for someone to respond here.

Edited for derp.

combustiblemonkey said:
Ive done all kinds of stupid things to my nook including an attempted install of Slackware... but I have never bricked it. Ive been running the CM nightly builds without any kind of problems as well. Well, no problems outside what one would expect from development software that is still in a rapidly changing state. If you want stability and reliability, EMMc installs of CM and HC and even Froyo are probably not where you want to look right now.
Click to expand...
Click to collapse
I agree with this statement. I'm happily back to Eclair and advanced task killer.
Sent from my PC36100 using XDA App

succulent said:
If you formatted your card in your NC then that's the problem. Don't format your card with CW because it'll wipe the boot sector giving you a black screen. It's fixable, many people have made the same mistake on the #NookColor channel. Go there for help because it's faster than waiting for someone to respond here.
Click to expand...
Click to collapse
Not helpful information contained in this post.
Sent from my PC36100 using XDA App

khaytsus said:
So to be clear here, your problem with CM7 not booting was related to your SD card "going bad"? Or was your restore process hampered by this?
You had installed CM7 to emmc and such, right? How would the SD card be affected by that?
Click to expand...
Click to collapse
The recovery SD card was not in the nook when it went bad. The Nook and the card weren't even in the same building. I would assume that the SD card simply wore out. It was an old card that saw much use. Everything from sitting in a camera to running the R4 in my Nintendo DS. I will give it the burial of a Patriot, Westboro Baptist protest and all.
I still have no idea why CM7 tore up the boot of my Nook. I was reading a book in aldiko before I fell asleep, but I don't rememeber what else I was doing.
Sent from my PC36100 using XDA App

admiralnorman said:
Not helpful information contained in this post.
Click to expand...
Click to collapse
YOUR post was useless. His post was completely accurate. If it wasn't what caused YOUR issue, fine, but what he said was 100% true.
By the way, you realize you didn't start this thread, right?
admiralnorman said:
The recovery SD card was not in the nook when it went bad. The Nook and the card weren't even in the same building. I would assume that the SD card simply wore out. It was an old card that saw much use. Everything from sitting in a camera to running the R4 in my Nintendo DS.
I still have no idea why CM7 tore up the boot of my Nook. I was reading a book in aldiko before I fell asleep, but I don't rememeber what else I was doing.
Click to expand...
Click to collapse
So what does your SD card going bad and your NC not booting have to do with each other????

khaytsus said:
YOUR post was useless. His post was completely accurate. If it wasn't what caused YOUR issue, fine, but what he said was 100% true.
By the way, you realize you didn't start this thread, right?
So what does your SD card going bad and your NC not booting have to do with each other????
Click to expand...
Click to collapse
Right. You asked for clarification on my earlier post. I provided it. It seems you don't like your quesions being answered. Next time use periods instead of question marks. Or properly label them as rehtorical.
- Sent from my HTC Evo 4g using XDA Developer's app.

It's the boot partition. Same exact thing happened to me. The nook seemingly won't power on due to not having anything to boot from. Luckily the uSD has boot priority so if you get one of the CWR IMGs floating around here and follow the guides, you can be up and running relatively quickly.

paranoid__android said:
It's the boot partition. Same exact thing happened to me. The nook seemingly won't power on due to not having anything to boot from. Luckily the uSD has boot priority so if you get one of the CWR IMGs floating around here and follow the guides, you can be up and running relatively quickly.
Click to expand...
Click to collapse
So any idea what's causing it to get wiped/corrupted? Formatting SD from within the booted ROM or unknown?

These types of threads are funny. People are too quick to blame the rom alone (even when clearly marked as dangerous / test / experimental, etc ones) after making the decision to risk the normal operation of the device in the first place. Take some responsibility people

Exactly.. I don't usually post in forums but this kind of stuff bothers me. I wasn't able to boot my Nook Color for a few hours but I never blamed it on anyone but myself. Almost every one of the custom Roms, Mods, etc says something like "Use at your own risk" Nobody is forcing you to try anything. If you think you "bricked" your Nook Color (which is almost impossible) you shouldn't blame it on the Rom or Mod or even expect to take it back to the store.. YOU took the risk. Even if you installed a Rom that slapped you and gave you the middle finger it's your fault in the end because no one forced you to try it (most likely...). I'm sorry if I haven't offered a useful solution to "cm7 broke my nook", but anyway all this is purely my opinion and I apologize if I have offended anyone but people need to take some responsibility for their actions.

[Q] Nook color power off loop for cm7 and froyo sd installs

A couple of days ago my dad got my sister and me nook colors. I installed honeycomb which ran off the sd card on both and rooted both. I was tired of not having YouTube flash and many other apps so I tried out froyo and cm7. After about 50 unsuccessful installs I have decided I must have a hardware problem because they will run on my sisters nook.
The problem is that after the install, it boots off the sd card and loads android completely but when it asks to complete with setup wizard or
Default action it freezes up for a second and shuts off. After I boot again it just says "Powering Down."
I don't know if I should try a native install or go return this one. I already restored it completely to factory conditions so they won't be able to tell. I have searched everywhere and cannot find this anywhere else (problem or solution).
I just find it so strange how it works on the other nook color but not mine. Even setting it up on hers and moving it to mine produces the same issue. I probably will return it unless someone can help me but I'm more curious to what the problem is than how to fix it, since I can simply go get a new one.
Any help is appreciated!

****bump****

Thats certainly a new one. I only have one nook so ive never tried them side by side. Ive never been able too successfully boot off an sd card and have it stable. I eventually just decided to go to cm7 internal and never looked back. I wonder if theres something different in the nook in how it reads from the sd card.
are you overclocking the image? or running it stock?
you said you set it up on your sisters nook then move it to yours and you have problems. did you try taking her good, working build and moving that sd card to your nook and seeing if the problems go away. Ive read alot about sd cards and different quality's of cards. maybe theres something up with the sd card you have.

I have problems no matter what. If i put it on hers to setup, it still has the problem. If i set it up on mine, still has the problem. I just tried phiremod v6.1 and it also had the problem (i expected this because it is still cm7). I probably will return it but i wish they would just update these things to android 2.2/2.3 and maybe even full honeycomb when it comes out and save all of us from these issues.
The image is the normal one. I have tried installing directly to the sd, using the "SD CARD TEMPLATE" files that you install and then boot from to install cm7, etc.
They all work on the other nook but mine is being stubborn for some reason.
I am at the airport getting ready to fly home and i might try installing it internally tomorrow. I just don't want to have this problem again and have to spend a bunch of time reinstalling the stock rom to return it.

I completely understand your frustration, especially since you have 2 and are not seeing the same thing on both. Are you experiencing any other problems with the device. based on what your telling me i would have to assume there is something wrong with the sd card slot.
but if you forget about your sisters nook for a min, what you are describing is exactly what i experienced on my nook. that's why i went for internal. I started with the dual boot, but found that i stopped using the stock rom pretty quickly, and with the slow ports of cm7 to dual boot, i just scrapped dual booting all together, and now im full cm7 and its great.

john10101 said:
I completely understand your frustration, especially since you have 2 and are not seeing the same thing on both. Are you experiencing any other problems with the device. based on what your telling me i would have to assume there is something wrong with the sd card slot.
but if you forget about your sisters nook for a min, what you are describing is exactly what i experienced on my nook. that's why i went for internal. I started with the dual boot, but found that i stopped using the stock rom pretty quickly, and with the slow ports of cm7 to dual boot, i just scrapped dual booting all together, and now im full cm7 and its great.
Click to expand...
Click to collapse
I tried the internal install, but it is doing the same thing. I am recovering the stock image right now. Thanks for the help, but I am just going to take it back and get a new one and not root it or anything and just install it to the sd card.

I have the same problem too.

[Q] Phone freezes randomly / needs hard reboot - 2.3.3 and 2.3.4 custom ROM's

Hi all
Ever since upgrading to 2.3.3 I've been having random freezes that usually end up in needing a battery pull or pressing down on the power button until the phone reboots itself. This is with Darky's 10.1, although I don't think it's related to the "Darky parts" of the ROM itself, but something more to do with the OS.
Also, I've felt that the phone sometimes slows down. It doesn't feel like the original lag on 2.1, but rather feels like something's eating up CPU power. This will happen on ANY application, and even when moving through homescreens on TW Launcher or ADW Launcher.
Another thing of note is that it seems to be the UI or input process that hangs or dies or something. Because whatever's running keeps running I just can't make the phone respond to touch or any of the hard buttons. For example, today I was playing Age of Wind (sweet game, check it out) and after like 10 seconds of the game stuttering, the phone stopped responding, but my ship just kept going forward and the other ships were trying to keep up with me. Sounds and music kept going. And after 30 seconds of "inactivity", the screen went to sleep. As you can see everything's normal except there's no input.
So what I'd like is for ideas on how to fix or figure out what's wrong. I'm somewhat tech-savvy so I wouldn't be scared of using adb or some other debugging tool. So far I've not been able to figure out what's wrong because all the logs start over whenever I reboot the phone.
So, any ideas? Any additional information that would be useful?
Edit and update: I've changed the title because this has already happened on different custom ROM's, including Darky and Criskelo.
I have now tested for 5 days on Criskelo's ROM (based on 2.3.4) and it will happen also. So far what I've noticed both on Darky's and on Criskelo's ROMs:
- The phone will work perfectly for about 4-5 days
- On the 4th day it will start stuttering and lagging. That's when I know it's very close to locking up.
- On the 4th day it will maybe lock up once in a day
- After the 4th day it will start locking up up to three times a day
- The lock-up is at the UI level. Applications will keep running, it will ring if you call it, notification sounds are still alive, the screen will turn off normally after 30 seconds or whatever timeout you set up. But input is totally dead.
- When it locks up, both soft-buttons will light up and stay lit.
Possible causes:
- Something related to USB storage or SD card storage. Someone mentioned that it might be caused by the "fast media scanner". It's possible, because on one of my many tests, instead of reinstalling an OS, I formatted the minisd, the internal sd and phone storage and the phone was fine for 4-5 days and then it started doing screwy stuff again. This reinforces the theory that it's something to do with storage. My guess is the OS itself starts degrading the filesystem or handles or something. And my suspicion is that it's something in the /system/dbdata or /cache partitions, not the sdcard or external sd cards. Impossible to know because I have no idea how to debug using adb and nobody has given any ideas on this.
- I'm starting to suspect the BLN support in the kernel. I have BLN turned off, but I'm not so sure.

Hi,
Sorry don't have any answers, but am having the exact same problems on Darky's 10.1. Except I have a TouchWiz4 Port + Galaxy S II Icons.
Hopefully someone will know of this issue! Its starting to annoy me!!
Cheers,
Sunny

Tell me something, when you installed Darky, did you restore your apps via Titanium Backup? Did you select "Restore apps + data" or just apps?
I'm in the process of reinstalling Darky's from scratch, see if that works. If not I might go back to 9.5 or try Criskelo's ROM.
Thanks

Hi,
Nope I didn't backup or restore any apps. My data is all on my SD card and I just reinstall apps.. I came from DebusROM G1.
Thanks,
Sunny

Maybe a factory reset (do it in recovery) would help?

I actually did a factory reset before installing.
@sundazetoo: Do you have Voodoo lagfix enabled?
Last night, while in the process of reinstalling Darky's ROM, I disabled the lagfix (converting to RSF) and after almost an hour i decided to pull the battery. Then when I rebooted again, it went through the conversion process, finished in 2 minutes (wut!) and an error displayed (it couldn't mount some partition, one that I know is not critical).
So I'm suspecting a filesystem problem.
I already installed and DO NOT have Voodoo's lagfix enabled. I also did a complete wipe and restored my apps without data. So far it seems fine but it's only been a few hours.

@Lunchbox115: I did the factory reset when I installed too.
@ferparedes: Yep voodoo is enabled. I am now running on the stock launcher that came with Darky's 10.1 and it seems to be running a lot smoother. I was running a TW4 port so that may have been my problem!
I will monitor it and let you know how it goes.
Have you tried clearing the data / cache for the launchers you are using? That seems to fix alot of FC issues for apps for me.. I guess no harm in trying anyways?

2 days in after reinstalling.
Voodoo EXT4 lagfix NOT enabled. Phone is pretty snappy and I've haven't had any more freezes. I think it was either a bad EXT4 conversion or the lagfix itself was causing it. Anyways, since the phone is pretty fast I'm leaving it with RFS lagfix only.
One thing of note, though. I'm running stock GB launcher atm, because ADW was giving some problems.
Yesterday ADW Launcher *died* and although the phone was working and responsive, the launcher never came back. The result was that when I pressed the home button nothing happened but a blank screen. The power button worked, though, so I was able to do a clean reboot and switch to Launcher.

Interesting, I dont seem to have the same issues with the voodoo lag fix.
Also I am now using ADW Launcher EX and have not had any issues. I think my problem was the TW4 port.

Same again
I get these issues too. I seem to get them RFS and ext4 (I think - mostly its been ext4 though). Often get a delay on the keyboard. Its driving me a bit nuts but I am reluctant to go back to Froyo just for this (I hate having to restore all my user names and passwords).
Silly thing is I cannot recall if I got in when I tried Gingerreal (on Darky 10.1 now).
Would love to see thoughts and theories too..
G

UPDATE
After almost 2 days of totally flawless operation, I reinserted my 16 GB Micro SD card with all of my stuff in there. Among many things:
- Audible audiobooks, along with bookmark and "furthest listened" data
- Music, playlists. All created by TuneSync (which I use to wireless sync music and playlists from my PC's iTunes)
- Dropbox download folder
- Photos and videos taken with the phone
- Some other files not associated with any app
2 hours after doing this, blam, the phone locked up again requiring a reboot. So I removed the Micro SD and when I got home I backed up my photos and videos on the PC, reinserted it in the phone and formated the card. This was last night.
So far the phone's working fine.
My current theory:
The Micro SD card I originally bought for the phone was an 8gig. When I got the 16 gig one, I just copied everything from the 8gig onto a folder on the PC, then copied everything over to the 16 one. This might've broken something.
After going to Gingerbread, it's possible that the way some applications look for their data (for example, Audible) changed but when encountering the same data (that was copied over from a windows folder on the PC) it might've generated errors which in turn put the interface into a deadlock.
My strongest suspect is Audible. After installing Darky 10.1, the app just chugged away remembering all my farthest listened to data, all my audiobooks were visible, etc. After reinstalling (and removing the Micro SD) I had to redownload some, but it still remembered where I was and didn't have to reactivate the device. Now, after formatting the Micro SD, I've had to redownload everything, it didn't remember where I was on each audiobook and I also had to reactivate the device.
If the phone doesn't lock up during the next 4-5 days then I'll conclude that errors on accessing the Micro SD by some app was the cause.

sundazetoo said:
Interesting, I dont seem to have the same issues with the voodoo lag fix.
Also I am now using ADW Launcher EX and have not had any issues. I think my problem was the TW4 port.
Click to expand...
Click to collapse
Yeah I actually don't think ADW launcher is causing this particular problem. But in a different problem altogether, it did die and in this case required me to do a reboot, albeit a clean one. But if it gave me this one single problem than I'm inclined to stop using it. I don't want the phone disabled for the 3-5 minutes it takes to boot up if I need it in an emergency (it's a phone first and foremost, after all)

tw4 is an EVIL for SGSi9000 imho... because almost everyone have problems with it !!! so just use another Launchers... LauncherPro, Launcher EX (my favourite) but not TW4 )))

I tried to fix with a reinstall of stock jvp and then went to F1 v8 jvp rkm but I also formated ext_sd card as suggested here (and deleted audible application which I was not using.
So far so good but it's only been an hour...
Sent from my GT-I9000 using XDA Premium App

Definitely something related to sd card. Everything is screwy now but less so with the sd card out.
Anyone find any solutions?
I was getting double boot screens and freezes on the dialer. Realized it was the sd when my backup would not load.
Sent from my GT-I9000 using XDA Premium App

Had this happen to me today,
I had the phone boot up and it would get to the lockscreen, then media scan, then it would lock up, only a battery pull would turn it off.
Tried booting without the External SD and it didnt occur, hmmm
Put the microSD card in the card reader on the PC, and performed a scan for errors/fix bad sectors, it didnt find anything but i put it back in and it goes fine now, im sure its the external card.

related info
Found this thread that seems related;
http://forum.xda-developers.com/showthread.php?t=367912&page=3
Trying the chkdisk utility now...

It did it again with the micro sd card out. So today I reformated the internal SD storage (usb storage) and will see how it goes. If this last attempt fails I will either go back to froyo or try another ROM.
But I do think it has something to do with one of the SD card storage.

gfacer said:
Found this thread that seems related;
http://forum.xda-developers.com/showthread.php?t=367912&page=3
Trying the chkdisk utility now...
Click to expand...
Click to collapse
Should be fine

More things to try
Looked at my rom page (F1 JVP) and noticed that V8, which I have now, had the faster media scanner as does Darky's 10.1-which is not getting updates often now it seems. Well the faster media scanner only lasted 2 days until V9 of the F1 rom when the delevoper removed it. My guess it that it was causing issues.
Leads me to wonder if that might be causing the corruption in the first place or at least a contributing factor.
Also read some threads at google about similar issues across a whole wave of devices and one person there mentioned H2testw utility to test the sectors of your SD card. It sounds like cheap ebay sd card and larger SD cards my have more issues (mine is a 32gb). It is best to format and then test with h2testw but I decided to run just on the empty parts of the card and decide from there.
G

TWRP, eMMC errors, and a lot of questions...

So I have one great Note 4 that runs fine. A second Note 4, given to me appearing to be a paper weight, has been with some effort rescusitated. But no, the eMMC errors have not gone totally.
This "bad" phone, however, is allowing me to fully exercise some of my curiosity. And in the process, no matter what happens, I hope I can get a few more answers about things. I know about the little app that keeps the phone from going to sleep and stablizes it... that works on the phone unless it gets turned off. And then the whole cycle of trying to start it again (the freezer trick, the holding of buttons, the pulling of the battery... sigh).
My latest gambit has been to go into TWRP and reformat /system /data and /cache (the only directories where I'm allowed to do so) to f2fs. In fact, just to really wipe this baby as clean as I possibly could, I reformatted them back to ext4, then back again to f2fs. I then installed a custom rom (the official CM 14.1). It appears to have installed over the top of the f2fs without trouble.
But of course I am freewheeling it here. I do not know very much about what is going on down inside there.
My questions:
1. What "hidden" directories are there that TWRP isn't showing me? Is there any possibility that if I could reformat them (and not destroy the phone) it might help with the eMMC errors? How would I do that if I in fact can?
2. When I reformat the directories from one format to another, am I actually wiping them or not? (I've read long pages about people suggesting that Android phones are terribly hard to actually wipe all data off.)
3. Is there any other possible cause for the eMMC errors than bad physical memory? I understand that bad memory chip *is* one obvious cause... but are there other causes that could in fact kick up an eMMC error that isn't really about the memory chip?
I'll post any other questions if and when I think of them. Worst happens, I mess this phone up so bad it won't reboot at all. I'm not too worried about that.
All thoughts welcome. I can experiment without caring too much.

I have read elsewhere that the problem could be caused by having a micro sd inserted in the phone.

Intensivefire said:
I have read elsewhere that the problem could be caused by having a micro sd inserted in the phone.
Click to expand...
Click to collapse
Yes, I've read that also. Tried all sorts of experiments with and without micro-sd card inserted. Using a Wake Lock app from playstore (set on mid-range) allows the phone to do and be nicely. But shut it off and I have to freeze it for 5 min before it will restart. So... hopefully the Chinese mb card I bought today will actually work. Providing I can in fact open the phone without busting it. (There's some good clues on youtube which is nice.)

shonkin said:
Yes, I've read that also. Tried all sorts of experiments with and without micro-sd card inserted. Using a Wake Lock app from playstore (set on mid-range) allows the phone to do and be nicely. But shut it off and I have to freeze it for 5 min before it will restart. So... hopefully the Chinese mb card I bought today will actually work. Providing I can in fact open the phone without busting it. (There's some good clues on youtube which is nice.)
Click to expand...
Click to collapse
emmc errors on note 4 is well known hardware failure , its time for you to replace emmc chip or system board

zfk110 said:
emmc errors on note 4 is well known hardware failure , its time for you to replace emmc chip or system board
Click to expand...
Click to collapse
Yes, I said that in my first post. My point was that it is possible other causes for the error message just might exist. But all that is moot now... I did in fact order a new motherboard. But in the meantime, when I went to dissect the phone according to instructions on youtube, I found out too late that the author of said instructions was fairly clueless as far as a successful end result. The phone is dead, dead, dead. Lucky for me, it wasn't my main Note 4, which is just fine.

Here is a 100% hardware fix for this issue that anyone can do with no tools or specia
Here is a 100% hardware fix for this issue that anyone can do with no tools or special equipment.
It really works. Give it a try. ?
https://youtu.be/jLPHWtb0StI