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!

Internal SD Disappears?

My internal SD card keeps disappearing, about once a day on my I9000M. I'm on stock Bell JH2 rooted. No lagfix, although I did use it for a while.
So my phone keeps working fine, I only notice this when I go into the gallery or try to play music stored on the internal SD.
Gallery - says no SD card detected
My Files - says "Your phone does not have a SD card inserted"
Astro - says "error writing internal memory" - but it opens and shows no files in SDCARD
It only takes a power down to get it back. And works fine until the next time.
So I bought this phone through Besy Buy in Canada and unlocked it and I use it on Telus.

Sounds like your SGS is starting to experience signs of a possible internal SD card failure which will require an exchange or service to fix. You say that you did use a lagfix at one time... Is that correct? Seems that the lagfixes speed up devices that already have a possible issue with this SD card problem.
Read around somemore and you will see MANY i9000M devices with this issue and most happen after installing a lagfix or an unofficial firmware.
Sorry to be the bearrer of bad news but I would look into a replacement (if you still qualify) or sending it in for repair.

I get something similar but I never applied any lag fix. In fact it only happens why I plug in my phone to charge via the computer. If I don't plug in for a few days, then I dont get the sd unavailable issue.
Sent from my GT-I9000M using XDA App

asicman said:
I get something similar but I never applied any lag fix. In fact it only happens why I plug in my phone to charge via the computer. If I don't plug in for a few days, then I dont get the sd unavailable issue.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Actually now that you said that I remember lately when I have my phone plugged into the wall charging, when I pick it up it says connected to kies.

DaveJeep said:
Actually now that you said that I remember lately when I have my phone plugged into the wall charging, when I pick it up it says connected to kies.
Click to expand...
Click to collapse
So then I would have to say that there is a different defect with both of your devices that is causing this. There is no other reason that when your phone is plugged into the wall on "power" only that your phone should think its connected to kies.
LOL... Plug in your phone to the wall... Wait for it to say its connected to kies and flick the lights on and off lots and see if it will strt downloading froyo!!! Just Joking here but in all seriousness I would look into fixing or replacing the device...

Random Reboots, unable to complete a boot

OK Guys, here is my issue... I searched the forums and had no luck for what seems to be my problem, nor did a google search return anything.
I got my Nook back in Febraury, and it worked great, right away wound up putting NF 0.6.7 on the eMMC and life was peachy. I hadn't been using it much, had been waiting for CM to get to a stable release so I could put that on there and call it good.
Anyways, I'm using it one night, full battery, I turn the screen off, head to bed. The next day I try turning it on, nothing happens, tried all the key combinations, but wouldn't start. My microSD adapter was broken and was waiting for a new one so couldn't try much.
Just got the adapter yesterday so I went ahead and made a CWR bootable SD card (not ext4) and booted it up, but it was doing the weirdest thing, The whole screen was flashing, like how the screen will turn black if you press the power button while in CWR, it would blank the screen then come back momentarily, and then probably 10 seconds into it it rebooted itself. Thought this was pretty weird so tried booting again with the same results.
My next step was try download the SD image again, reburn it and try the process again. At some point I wound up trying the ext4 image because I wanted to install CM7 anyways. One time I was able to boot to CWR, and it didn't seem like anything was wrong, so I thought life was grand, wiped data/cache and installed the CM7 zip liek the instructions stated. Rebooted, nothing. Rebooted with the SD card in again and it was back to its old antics. Anyways, after many reburns and tries, I was able to get CWR to stay up long enough to flash the repartition boot with stock image. When I rebooted it would get to the N screen, and then bootloop like it's supposed to, did that 8 times, got to where it shoudl Factory reset itself, got the installing screen, and the Nook rebooted right before it was about to finish!
So ever since then it's been a struggle of trying to keep it up long enough to flash a stock zip, but I have had no luck, it literally reboots within 30 seconds of being in CWR. Tonight I'm going to try making a CM7/NF SD card to see if ti will stay booted solely off of the SD card, but not holding my breath since CWR won't stay.
To me it sounds like a hardware problem, all the keys work fine tho, power to boot and turn off, I guess i cant test volume keys but the N works just fine too. Didn't drop a glass of water on it, didn't leave it on top of a furnace or anything, I have no clue.
Crappy part is im outside of BB's return perios, and even if I wasn't, I threw the box away last week So what do you guys think? Am I totally missing something? Is it hardware? Can I send it back to B&N for a warranty claim? Not sure if they'd be able to tell it's been messed with since it appears stock now, and I don't feel like defrauding them, but if it's hardware it would have happend with or without a custom rom on there. Sorry for the long winded post and thanks!

does it behave when hooked up to your computer via usb? is it possible to complete the flashing using adb?

Hi,
It also sounds like the electronics might be intermittent - have you given the
unit a 'thump'?
Cleaned the uSD connections on the card (and maybe on the Nook?)
Probably not it, but in your long description above, you don't mention reformatting
to EXT4 all the correct partitions before installing CM7.
Good luck!
Peter

Animec said:
does it behave when hooked up to your computer via usb? is it possible to complete the flashing using adb?
Click to expand...
Click to collapse
Holy crap, it behaves perfectly when hooked up to the computer, i can mount it and everything, but as soon as i unplug it, it's up to it's old tricks, dimming the screen, going back to the lock screen, acting like the power button was pressed. I don't get it at all.. I'm going to do some research on pushing the partitions via adb...

spoke too soon, back to rebooting every time it gets to the N screen

pmilford said:
Hi,
It also sounds like the electronics might be intermittent - have you given the
unit a 'thump'?
Cleaned the uSD connections on the card (and maybe on the Nook?)
Probably not it, but in your long description above, you don't mention reformatting
to EXT4 all the correct partitions before installing CM7.
Good luck!
Peter
Click to expand...
Click to collapse
What kind of 'thump' do you recommend? lol, i tried cleaning the connectors, no luck, i actually didn't format any partitions to ext4 before i tried flashing the zip, i thought flashing it from an ext4 compatible sd card was the only thing you had to do? please tell me i missed something and we can fix it!

OK one more reply here..it seems to be behaving fine when its plugged into either usb or outlet, its almost like thinks it's dead unless its charging?

HI,
CM7 requires most of the partitions to be formated with ext4.
I found this posting to be the most useful for my install of CM7:
http://forum.xda-developers.com/showthread.php?t=960542&page=16
a little dated, but very detailed!
Looks like /system /data and /cache should be ext4.
I would be surprised if running CWM from external SD, if it is setup correctly
would just crash before you try and access the internal memory though.
-> have you tried a second uSD card?
Could it be a bad card plus badly corrupted mixture of stuff on internal emmc?
You mention in post that device looks ok with USB power adapter connected?
Perhaps intermittent battery connector? (Try holding unit at different angles?)
Thump: whatever you feel comfortable with without doing any damage(?)
Good luck!
Peter
jwood55812 said:
What kind of 'thump' do you recommend? lol, i tried cleaning the connectors, no luck, i actually didn't format any partitions to ext4 before i tried flashing the zip, i thought flashing it from an ext4 compatible sd card was the only thing you had to do? please tell me i missed something and we can fix it!
Click to expand...
Click to collapse

OK, morning report, left it plugged into the Nooks EOM charger cable over night, seems to be working this morning, its almost like the battery was dead...maybe i was using my Captivates charging cable instead of the Nook one? Anyways, everything seems to be better now, thanks for the help!

did i just brick my phone? bsod, connected via usb as mass storage with OR

i had my phone connected via usb like a mass storage device with OpenRecovery when my pc crashed for god only knows what reason... it seems to coincide with the phone simply DYING, meaning that now it doesnt even turn on, no OR no nothing, the only thing that does work is the charging light when i do plug it in... however that is all i can do.
so did i just break it? if yes - someone shoot me... if no - how do i fix it? i dont care for whatever was on the phone since i just had it all backed up and was about to wipe everything and reinstall a new CM6 version since by mistake i've gotten myself a little older one... anyway. help?
EDIT: on second thought disregard my stupid face, something tells me that while doing nandroid backups and other crap i killed the battery and simply have to charge it, i was able to get back into OR however the phone turned off before i could connect it to the pc, i'll probably turn off panic mode and go sleep on it while the phone is plugged NOT into the pc for charging -.- I would still like to know if my theory is right... etc etc...

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