Database Develop

STABILITY... Please...?

Ok. So just about every roms that I've tried on my G1.. I get the same issues. Be in a hero rom, 1.5,1.6,2.1... whatever.. there's a couple probs I run into that are starting to become extremely annoying.
FREEZING - all the time. Every day. At least 20 times. Requires battery pull and waiting 5 minutes for reboot. ANNOYING.
Phone randomly shuts off... I bet all can see why this may be annoying.
Battery meter at <70%... phone freezes.. battery pull.. then its at like 1% when I turn it back on
EVERYBODY I talk to says "all they can hear is background noise" and can barely hear me. Tried all 3 G1 radios with NO success. And no.. there has been do damage or water damage to my phone. This started when I put the newest radio on, so I downgraded to the previous one and the issue still stays.
Idk... I know it seems like I'm just complaining.. but I suppose my question is.. WHAT IS THE STABLEST ROM YOU YOURSELF HAVE USED in the aspects of freezing, and random reboots?
Any input will be appreciated. Thanks in advance...

You've got hardware problems. You could flash every ROM out there and it won't help.
The first thing I would try is to eliminate the SD card from the equation - either try a new one or try running without it.

Shrivel said:
You've got hardware problems. You could flash every ROM out there and it won't help.
The first thing I would try is to eliminate the SD card from the equation - either try a new one or try running without it.
Click to expand...
Click to collapse
Could this be why my sd card won't mount either? It won't mount under any cirumstances. The "mount usb" doesn't even come up in my notifications. But these problems have persisted with a few micro's of mine.. but they are all old and have been used in my G1 successfully before. Is it possible that they're fried? Fat32 and ext4 access & write from the phone works. Same thing if I put the micro in an adapter and into card reader in my comp. I've flashed maybe at least 30-40 roms PER sd with partitions, etc.. and they're all no-name brands. All classless too. (Not C6 or class 4, etc).
Any input appreciated. Thx!

[Q] I9000M - Question for people that had their Internal SD fail.

I was just wondering, for those of you people that had the I9000M Internal SD fail can you answer the following (approximately):
how many apps did you have installed?
how much of the internal SD was used?
I'm just trying to figure out why they're dying. I have one myself and I'm not exactly using it to its full capacity. I was wondering if people that used their Internal SD more heavily were the ones that were have problems.

nemethb said:
I was just wondering, for those of you people that had the I9000M Internal SD fail can you answer the following (approximately):
how many apps did you have installed?
how much of the internal SD was used?
I'm just trying to figure out why they're dying. I have one myself and I'm not exactly using it to its full capacity. I was wondering if people that used their Internal SD more heavily were the ones that were have problems.
Click to expand...
Click to collapse
I was using about 4.5 GB on mine with about 110+ apps. I don't think it has anything to do with the amount being used though. More with the flashing of a Froyo firmware, specifically, doing a factory wipe in Recovery Mode of a Froyo ROM. I was able to flash a Froyo ROM successfully and have it boot up properly once before I decided to do a wipe and pretty much screwed up my internal SD.

dawgpound6985 said:
I was using about 4.5 GB on mine with about 110+ apps. I don't think it has anything to do with the amount being used though. More with the flashing of a Froyo firmware, specifically, doing a factory wipe in Recovery Mode of a Froyo ROM. I was able to flash a Froyo ROM successfully and have it boot up properly once before I decided to do a wipe and pretty much screwed up my internal SD.
Click to expand...
Click to collapse
That's the thing though. One person having an issue doesn't which they think resulted from 'this' may not apply to everyone. This is why I'm trying to take a sample and find out what is the biggest culprit (i.e. lag fix, flashing ROMs, amount of storage, etc.).

i believe this is also the cause of my sdcard corruption. ever since i installed froyo, i lost half the sdcard, and now i can't mount it in recovery.

i can't comment yet
still working
have over 400 apps installed
only around 400 MB free in the internal SD everything else consume by Apps and Maps
i keep changing apps frecuently, and installing updates as they appear on Android Market

I was using about 10GB of my internal SD card when I chose to download a Froyo build (JPK). Soon after installing it, I tried plugging it into my computer via Mass Storage mode, and then couldn't get out of it. Eventually the phone went blank, it vibrated a few times, and the only way to get it to do anything was to pull the battery. Once I did that, the internal SD storage was toast.
I was trying quite a few things to get it to recognize the internal storage, but in the end I ended up bricking the phone even more. Now it will bring up the Galaxy S GT-9000 screen, light up the Back/Menu buttons for a few seconds, and then reboot. Download mode and recovery mode are now gone and the only thing I've had it do is go into Forced Upload mode (which as far as I've searched) is pointless for us now.
I have a feeling it's more related to the lagfixes. I had uninstalled the Voodoo one soon after trying it out, but I guess that wasn't enough.

Devhux said:
I was using about 10GB of my internal SD card when I chose to download a Froyo build (JPK). Soon after installing it, I tried plugging it into my computer via Mass Storage mode, and then couldn't get out of it. Eventually the phone went blank, it vibrated a few times, and the only way to get it to do anything was to pull the battery. Once I did that, the internal SD storage was toast.
I was trying quite a few things to get it to recognize the internal storage, but in the end I ended up bricking the phone even more. Now it will bring up the Galaxy S GT-9000 screen, light up the Back/Menu buttons for a few seconds, and then reboot. Download mode and recovery mode are now gone and the only thing I've had it do is go into Forced Upload mode (which as far as I've searched) is pointless for us now.
I have a feeling it's more related to the lagfixes. I had uninstalled the Voodoo one soon after trying it out, but I guess that wasn't enough.
Click to expand...
Click to collapse
Sorry, but what? Let me get this straight, you tried voodoo lag fix, uninstalled immediately, and yet you still believe it is the lagfix that destroyed the SD card? You think that applying the lagfix mod somehow utterly destroys your SD card even though you've used it for an extremely short amount of time? If that's true then most root users would have bricked their vibrants already.
Seriously, that makes no sense. I stand by my theory that there's a bad batch of SD cards that went into the i9000m production. Bad SD batches happen all the time. Not something uncommon. On top of that, all Voodoo lagfix does is change the file system of the SD card. Would your hard drive die if you formatted it from ntfs to fat32? No. This is not mentioning there are quite a few vibrants that have not used lagfix with dead sd cards.

If it was purely a hardware failure of the flash chips, then it would make sense to have the failures occur randomly. As it is right now, most of the failures seem to happen when people flash the newer Froyo builds (or very soon afterwards).
As far as the lagfix is concerned, I'm by no means implying that this is the only cause of the failures, but if something is going wrong in the conversion of file systems (however minute it may be), it is possible for the file system to become corrupted over time.
I don't think we know for sure whether it's a hardware failure or a software one. This is made even more difficult by the fact that we are generally limited in what recovery options are made available (not like a desktop, where I could boot a Linux distro off a USB stick and directly access the file system to troubleshoot). I do realize some have been able to try and get utilities like GParted to run on the phone's internal memory, but it's still not nearly as convenient as running the same utility on a desktop HDD/SSD.
Feel free to disagree with me, but I know once I get my phone back, I won't be installing a lagfix (or a custom build for that matter).

Hmm.. So i9000m's had a bad batch of memory? interesting. I'll remember that when someone comes asking for problems and see if their device is a i9000m , BTW what is the i9000m ? Captivate?

i9000m = Canada Bell Mobility version of Samsung vibrant
i9000 = international version

nemethb said:
That's the thing though. One person having an issue doesn't which they think resulted from 'this' may not apply to everyone. This is why I'm trying to take a sample and find out what is the biggest culprit (i.e. lag fix, flashing ROMs, amount of storage, etc.).
Click to expand...
Click to collapse
I missed this post completely. People are having some MAJOR confirmation bias for WHY the i9000m dying.
Just because you do something, it doesn't always imply causation. There are plenty of vibrants around with dead SDs without ever installing lagfix or froyo. It's purely coincidence, because the SD was going to fail anyway.

Actually, I don't think there is enough evidence to come to any conclusion regardless.. But there is no evidence proving that the lagfix cannot be part of the problem, or no reliable proof. especially since nobody totally understands how the internal hardware works on this phone though. In fact, the "evidence" that wear leveling happens on the hardware controller is based solely on the sentence "computer SSD's do it that way" (ie, no evidence). And a lot of other evidence related to other problems i'm seeing is also based on assumption.
1) First isolate if the problem is faulty hardware or simply a formatting issue..
2) Work out what ROM's and such people were using
3) Work out if they were using a lagfix.
4) CONFIRM that the internal SD is actually dead. Many people here jump to conclusions too quickly.
5) Also, work out if there is an easy way to get "batch numbers".. Maybe it's isolated to a specific hardware batch.

i was on official jh2 rom from bell w/ voodoo lagfix. Never attempted flashing another rom. I noticed one time it crashed so i pulled the battery for an hour and that had fixed the issue (or so i thought). Was working for about a day and it crashed again. Out of desperation i tried flashing other roms like froyo. So the way i see it, its either general faulty hardware or the lagfix...not flashing froyo builds.

My i9000M had never crashed until soon after installing the JPK firmware, and in my case one crash was enough to "break" the SD Card. Again though, the fact it only crashed when I installed Froyo does not mean this was the cause.
Hopefully we can figure it out, because between the 3-button recovery mode issue and this, I'm considering getting another Android device instead.

I have a bell i9000m and I have not had this issue yet. Just curious for people who have. Did your phones have the three button issue as well?
Sent from my GT-I9000M using XDA App

I started thinking the same thing actually. Mine did have the 3 button recovery issue as well, and of course I had patched it (using the official Samsung Canada JH2 re-release).

MaestroSeven said:
I have a bell i9000m and I have not had this issue yet. Just curious for people who have. Did your phones have the three button issue as well?
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
3 button was working on mine. But I have seen reports on here from people with the same issue where 3 button was not working..
Sent from my GT-I9000M using XDA App

3 button was also working on mine. Like the others, JPK booted correctly but I was getting force errors due to me upgrading from Eclair. Then I decided to wipe/factory reset and it was a no go from then on.
I hope we can figure this out. There has to be a way to get to the internal SDCard and repair it properly.

I have the T-Mobile US Vibrant and I noticed some weird problems with my internal storage too. I have only rooted and lagfixed my phone. I noticed it was taking longer and longer to open photos in my gallery and sometimes they don't open at all. Sometimes the phone will not mount as a storage device on my laptop. In the past 4 days, my phone has crashed hard twice. The first time I had to boot into recovery and wipe personal data and download all my apps and set my email accounts again. This morning my phone lost all the contacts from Facebook, Touchdown (Exchange) and Gmail.

This JUST happened to me like, 5 minutes ago. I browse these forums every day and I had never seen any warnings with regards to Froyo screwing up internal sd cards. It seems many of these cases are Froyo related. Now I probably have to take my phone back.

[Q] Reboot Causes All Apps and Settings to be Completely Reset

Problem:
Whenever I reboot the phone Go Launcher and all other installed apps get completely reset to their default settings as if they were just installed, losing all of my settings, stored login creds, etc. Usually I stick to stable builds when flashing mods and have never had an issue, so I'm at a loss as to where the actual problems may be with my current setup. Any help in troubleshooting this matter or suggestions on how to resolve it will be GREATLY appreciated.
Setup:
Evervolv JB p4
AD2SDX - Amarullz Data to SD-EXT
BlackRose HBoot; 260MB / 8MB / 168MB
32GB Class 2 MicroSD; 10GB EXT3 / 22GB FAT32
More Info:
The phone runs relatively good, considering it is JB on a N1. It gets a little choppy at times, but that is to be expected with a pre-alpha mod and a class 2 SD. After I setup my phone for the first time, and got all of my apps installed and setup as well, I ended up rebooting the phone and everything got reset. I was pretty pissed as I had just spent a quite a bit of time configuring everything. I figured it was a fluke and set everything up all over again, only to have it reset on the next reboot. Very frustrating.
I like JB but the choppy performance has me considering going back to CM7.2. Before I even realized I had this problem I ordered a new Class 10 32GB SD to speed things up. I want to see how much of an improvement the SD gives me before I give up on JB. If I do go back to CM7.2 I would like to keep a similar partitioned SD setup to resolve the limited on-board memory issue with the N1. However, if it is in fact the partition setup that is causing this problem then that isn't going to be an option and I'll have to go back to the conventional storage setup until I get around to getting a new phone.
Thanks for taking the time to read this and for any assistance you may provide.

Frequent freezes/reboots after upgrading Spice Dream Uno H to Marshmallow

Hi everyone,
I upgraded my phone to 6.0 this morning, and have been facing issues ever since. The phone keeps freezing or rebooting at will. When I first tried to format my SD card (a class 10 Strontium Nitro 32GB purchased 2 months back) as internal storage for the first time, it got stuck for a long time and I had to do a factory reset and format again. After that, I moved all possible apps to the SD card, but every time I try to access a few of these apps (official Twitter, Truedialer, AdSense, etc) the entire phone will freeze for about a minute and then reboot for a very long time (over 5 minutes). I am terrified of opening any app on the SD card right now because it might trigger the reboot again.
Is anyone else facing similar issues on their Android Ones?
The battery life has also seemingly degraded, and once the phone completely shut down because the battery suddenly went from 40% to 0%.
After last year's Lollipop debacle and now this, I am really disappointed with Google's quality assurance. Marshmallow was supposed to be all about stability.

ashutoshmishra said:
Hi everyone,
I upgraded my phone to 6.0 this morning, and have been facing issues ever since. The phone keeps freezing or rebooting at will. When I first tried to format my SD card (a class 10 Strontium Nitro 32GB purchased 2 months back) as internal storage for the first time, it got stuck for a long time and I had to do a factory reset and format again. After that, I moved all possible apps to the SD card, but every time I try to access a few of these apps (official Twitter, Truedialer, AdSense, etc) the entire phone will freeze for about a minute and then reboot for a very long time (over 5 minutes). I am terrified of opening any app on the SD card right now because it might trigger the reboot again.
Is anyone else facing similar issues on their Android Ones?
The battery life has also seemingly degraded, and once the phone completely shut down because the battery suddenly went from 40% to 0%.
After last year's Lollipop debacle and now this, I am really disappointed with Google's quality assurance. Marshmallow was supposed to be all about stability.
Click to expand...
Click to collapse
My experience is pretty opposite to yours, my canvas is working flawlessly, and battery life has significantly increased. There is no sd card problem for me and app permissions and doze mood is best of the picks...try to reset your device

ashutoshmishra said:
Hi everyone,
I upgraded my phone to 6.0 this morning, and have been facing issues ever since. The phone keeps freezing or rebooting at will. When I first tried to format my SD card (a class 10 Strontium Nitro 32GB purchased 2 months back) as internal storage for the first time, it got stuck for a long time and I had to do a factory reset and format again. After that, I moved all possible apps to the SD card, but every time I try to access a few of these apps (official Twitter, Truedialer, AdSense, etc) the entire phone will freeze for about a minute and then reboot for a very long time (over 5 minutes). I am terrified of opening any app on the SD card right now because it might trigger the reboot again.
Is anyone else facing similar issues on their Android Ones?
The battery life has also seemingly degraded, and once the phone completely shut down because the battery suddenly went from 40% to 0%.
After last year's Lollipop debacle and now this, I am really disappointed with Google's quality assurance. Marshmallow was supposed to be all about stability.
Click to expand...
Click to collapse
Install android m stock rom again and after install format your memory card for internal storage using wait when memory card is formatted don't shutdown your mobile try this it will work

I am also facing random freezes with Spice Dream Uno on MM.

So I factory reset again this morning, formatted the SD card as internal storage one more time, and installed a few apps to the SD card. Things look much better than yesterday, so I am slowly adding apps and checking if any of them misbehaves.
I can't believe there isn't an option to auto-install apps to the SD card for sprout4 models.
Thanks for your replies. :good:

There are a lot Fc's on sprout 8 on root too I guess it has to do something with costom kernel apparently stock rom works perfectly

same problem Here in Spice Dream uno
I am also facing random freezes with Spice Dream Uno on MM

Freezes are back
They are back. At this point, I don't know what else to do except swap my SD card and see if the new one fixes the issues.

I can confirm this on Sparkle V too.
Making ext_SD to be used as internal even on Class 10 makes rebooting to take a hell of time.

I can confirm this with my canvas A1 running stock Marshmallow and Nitro Class 10 memory card.
It works flawlessly as external storage. But often freezes when used as internal.
I experience this on low battery usually.

Use sd card as external no problem but crashes the other way around same here

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