If only there were something, perhaps like a sticky at the top of this forum, that could guide you...
Sent via Captivate (powered by CyanogenMOD)
I apologize for not checking there first.
If only there were something, perhaps like a sticky at the top of this forum, that could guide you...
Sent via Captivate (powered by CyanogenMOD)
If you're having these types of issues across all different types of ROMs, including stock ROMs, it may be a hardware related issue. More specifically it sounds like it could be faulty RAM.
Hardware malfunctions generally occur if/when the device gets too hot or wet. Many times people make the mistake of leaving their device sitting in the sun for long periods of time. This can cause damage to the screen as well as internal components. Coupled with even a thin rubber skin/case around the device the damage can occur relatively quick when left sitting in direct sunlight. There are obviously many other ways the device can get too hot and many ways it can get wet. A less obvious way these devices get damaged by moisture that most people may not consider is by bringing it into the bathroom while taking a steaming hot shower. In each case the damage done can/will be slightly different, if at all.
I'm not saying this is most certainly the problem, only that I noticed no matter what version of the ROM you're on, you always seem to have the same issues and that this is usually the case when a hardware defect is the culprit.
I've been wrong before.
Just food for thought...
Thanks for the answer, but I don't understand why on ICSSGS and all builds before the release of the first Nightly (including the first nightly) worked without any reboots??
Perhaps the damage occurred since flashing the first nightly. Try reflashing back to 100% stock and see if the problem persists.
Sent from my SGH-I777 using Tapatalk 2
I haven't. I just flash the nightly then the gapps and reboot.
From #1:
Upgrading from another CM9 (or teamhacksung) Build?
1.Do a Nandroid Backup!
2.Install the ROM from internal sdcard using ClockworkMod Recovery
3.Optionally install the Google Addon
Hi, so I thought I had things figured out, turns out I was wrong. When I try to flash CM via recovery I get the following message
E:failed to verify whole-file signature
E:Signature verification failer.
If anyone can help me out, it would be great appreciated. Thanks in advance.
Loving CM9. Can anyone recommend a good DLNA server since I lost Allshare? Have Samsung TV's through the house and use it quite often to push videos recorded of our daughter to the family. I know there are a few out there but Allshare worked so smooth I wanted to pick your brains.
Thanks in advance!
How come these are called nightlies but not released nightly? I was looking in the vibrant section and they are released much more often.
Sent from my SGH-I897 using XDA
I am coming from Legend 3.0 and followed the instructions:
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
but when I did the "install from zip" after doing the WIPE step, selected cm_captivatemtd_full-181.zip, my phone is now in a boot loop, shows the Cyanogen(mod) screen then clockwork recovery (I see a "no such file or directory") message for a second but thats it then reboots back to the ATT screen.
Nightly builds are automatically generated by the "build bot" when there are new changes that get merged into the code. If there are no new changes, then a nightly build is not generated.
I have been running one of the nightly's for about 4 days now and overall I think its pretty damn good for being a nightly. Here is what I am still having problems with:
1.) Either car mode is not present or it immediately crashes upon plugging it into a car dock.
2.) GPS takes a lot of time to get a lock but I find that when it does get a lock that it is a lot more accurate than the previous GB releases.
3.) Can you make the icon dock at the bottom of the screen any small? That thing is HUGE
4.) LCD Density changer does not work, it screws everything up, any idea on this?
Problem with update-cm-9-20120415-NIGHTLY installation. I'm in another ICS rom, in CWM, wiped all, install zip from sdcard, choice update CM9 zip file, checking and... fail (error 7) then abort installation. I've tried many times and redownloaded the rom many times too but not effect. I've not met this problem with older versions.
I had this problem when I first flashed to CM9, I pulled the battery then went into recovery and re-flashed and it worked fine after that.
At this point it looks as though only the device developers (pawitp in our case) are initiating the "nightly" builds. I believe the newly acquired server is not yet configured to automatically build each device every day.
I'm guessing that when everything is smoothed over with the new server that it will produce nightly builds every day whether or not any new patches have been merged. That is how it was for CM7 at least.
How come these are called nightlies but not released nightly? I was looking in the vibrant section and they are released much more often.
Sent from my SGH-I897 using XDA
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is your--
Phone model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
I understand this is a nightly thread. I was unable to find a stable release anywhere and figured I'd ask here as this is the only CM9 thread that I found for the Captivate.
No wonder people keep telling me XDA is going downhill. Everyone here seems to get all butthurt when someone asks a question.
pawitp,
I understand the importance of following the standard method used on other Cyanogenmod devices, but I am curious how this compares to devices with no external sdcard option (such as the Nexus S and Galaxy Nexus)? Do these devices also have the internal sdcard mounted to /mnt/emmc and nothing mounted to /mnt/sdcard? While I realize that you made the change to follow a standard used by other devices, how does it make any sense to tell people that the internal card is mounted as "external multimedia card" (emmc)?
I think it makes much more sense for the entire CM team to revisit how sdcards (internal and external) are named and mounted to come up with something that makes more sense for every device rather than being arbitrarily based on a standard that was in place since the G1 and other devices that did not have an internal SD card. The Nexus S and Galaxy Nexus should be the references, especially in CM9, not old devices that will never even run CM9.
The download link in the first post is wrong. That link is for the international Galaxy S. Here is the link for the Captivate.
http://get.cm/?device=captivatemtd