no i didn't flash a new kernel. it's still the original one. any ideas to get the camera back?
Ha ha ha ha...that's awesomeClassic.
P.S. - Not raggin' on ya, Khizzer. Phateless just said what I was thinking when I read the post is all. 3D Gallery will run, but it will never run as fast as you want it without a faster processor, unfortunately. If you can do without the fancy 3D part, but still want a nice snappy gallery, check out "QuickPic" in the Market. It's free, no ads and one heck of a Gallery app. My wife really likes it (on her G1).
lol, thanks.
To elaborate, I wasn't trying to be a ****, I promise. I rocked a 32b for almost a year and the reason I got into rooting originally was so I could overclock and try to run Navi and Pandora simultaneously. Never got it to run smoothly.
The closest I came was oem donut rom, new radio/spl for extra ram and ezterry's 614 kernel with settings 528 min/614 max.
That the was the fastest I ever saw that phone run and it still wasn't enough.
The 3d gallery is a memory hog and the sapphire just doesn't have the power to run it smoothly. That's why I upgraded to the glacier (mt4g) with 1ghz processor and 768mb ram. This ****er can run anything, lol.
Just do a wipe data/factory reset and let it sit for 15 mins on first boot before setting up.
Sent from my HTC Glacier using XDA Premium App
CZECHer - I don't see where you posted information regarding your setup. That would help others to help you. (Suggest updating your signature with the info for the future.)
What phone? Dream, G1 or MT3G? (32A or 32B?)
What radio do you have?
What SPL?
How is your SD card partitioned?
How did you wipe your phone before installing?
What kernel are you using?
Are you using a custom MTD setup?
How much room do you have left on system? (In terminal console, type "SU", press enter and allow super user, then type df -h.)
Camera not working isn't typical, so my guess is either 1) something is messy in your setup, leaving too little room in system or not enough RAM 2) improper/incomplete wipe before install, 3) Corrupt download or 4) your camera is broken.
If I had tried all the quick fixes and something is still now working, below is what I would do personally. This assumes that you are using a 32B G1 or MT3G and have a radio/SPL that is compatible with the CM6.1 stock kernel. This also assumes you are not using a Custom MTD partition layout.
1) Redownload the ROM and Gapps to rule out possibility of corruption. (leave on PC for now)
2) Download Ohsaka Super Wipe 2: http://forum.xda-developers.com/showthread.php?t=834812 (leave on PC for now)
3) Remove SD card and using a card reader, backup all data to PC and reformat the card
4) Copy back data to card, along with new ROM, Gapps and Superwipe. Delete .AndroidSecure folder from card.
5) Boot into recovery and wipe with SuperWipe. Shut down and restart into recovery.
6) Flash ROM and Gapps, restart. (If you are using a 2708 radio/SPL combo or have a 32A, flash appropriate kernel.)
If camera is still not functional at this point, I'd be worried about a hardware problem.
Good luck!
What phone? Dream, G1 or MT3G? (32A or 32B?)
What radio do you have?
What SPL?
How is your SD card partitioned?
How did you wipe your phone before installing?
What kernel are you using?
Are you using a custom MTD setup?
How much room do you have left on system? (In terminal console, type "SU", press enter and allow super user, then type df -h.)
Camera not working isn't typical, so my guess is either 1) something is messy in your setup, leaving too little room in system or not enough RAM 2) improper/incomplete wipe before install, 3) Corrupt download or 4) your camera is broken.
If I had tried all the quick fixes and something is still now working, below is what I would do personally. This assumes that you are using a 32B G1 or MT3G and have a radio/SPL that is compatible with the CM6.1 stock kernel. This also assumes you are not using a Custom MTD partition layout.
1) Redownload the ROM and Gapps to rule out possibility of corruption. (leave on PC for now)
2) Download Ohsaka Super Wipe 2: http://forum.xda-developers.com/showthread.php?t=834812 (leave on PC for now)
3) Remove SD card and using a card reader, backup all data to PC and reformat the card
4) Copy back data to card, along with new ROM, Gapps and Superwipe. Delete .AndroidSecure folder from card.
5) Boot into recovery and wipe with SuperWipe. Shut down and restart into recovery.
6) Flash ROM and Gapps, restart. (If you are using a 2708 radio/SPL combo or have a 32A, flash appropriate kernel.)
If camera is still not functional at this point, I'd be worried about a hardware problem.
Good luck!
Last edited:
ty for your awesome help!
here is the missing information:
- phone: HTC Dream
- kernel: 2.6.35.8-cyanogenmod (shade@toxygene #2)
- radio: 62.50S.20.17U_2.22.19.26I
- partion of external SD: FAT32 (dont
- usage: /system 11,2 m available, /system/xbin 0 m available!, rest ist ok
- wipe procedure: i did a factory reset and wiped dalvin-cache and date
- spl: HBOOT-1.33.2005 (DREA11000)
i still have some questions: how can i find out the partition of the internet sd? and what is a custom MTD setup? - i don't even know what it is, i guess i don't have it^^
is the procedure you describe save for me?
ty in advice!!!!!
here is the missing information:
- phone: HTC Dream
- kernel: 2.6.35.8-cyanogenmod (shade@toxygene #2)
- radio: 62.50S.20.17U_2.22.19.26I
- partion of external SD: FAT32 (dont
- usage: /system 11,2 m available, /system/xbin 0 m available!, rest ist ok
- wipe procedure: i did a factory reset and wiped dalvin-cache and date
- spl: HBOOT-1.33.2005 (DREA11000)
i still have some questions: how can i find out the partition of the internet sd? and what is a custom MTD setup? - i don't even know what it is, i guess i don't have it^^
is the procedure you describe save for me?
ty in advice!!!!!
just opened my phone and checked the hardware --> cables and connections seem ok.
the problem with my camera appeared when i installed this rom here with the procedure described in the first post - befor it worked.
could it be that my problem has something to do with the HBOOT i installed with this: http://wiki.cyanogenmod.com/index.php?title=DangerSPL_and_CM_5_for_Dream
ty for your help
the problem with my camera appeared when i installed this rom here with the procedure described in the first post - befor it worked.
could it be that my problem has something to do with the HBOOT i installed with this: http://wiki.cyanogenmod.com/index.php?title=DangerSPL_and_CM_5_for_Dream
ty for your help
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
29CyanogenMod is a free, community built distribution of Android 2.2 (Froyo) which greatly extends the capabilities of your phone.
This version is for the old radio on both Dream and Magic. I plan to support the new radio soon.
Code:#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. */
This is an AOSP-based build with extra contributions from many people which you can use without any type of Google applications. I found a link from some other project that can be used to restore the Google parts, which can be found below or elsewhere in the thread. I've still included the various hardware-specific code, which seems to be slowly being open-sourced anyway.
Visit the CHANGELOG for a full list of changes and features!
If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance.
It's important to know that the "DangerSPL" (or DeathSPL or Haykuro's SPL or whatever you prefer) is a prerequisite for Dream/G1 users. Magic (MT3G etc) users do *not* need to do this. Ciwrl has written a guide to installing this bootloader. Flashing this bootloader under the wrong conditions can actually brick your device, so pay attention to the guide. CM releases have always avoided this requirement, but the new bootloader frees up enough space so that no crazy hacks are required for a fully functional system, and it's easier to keep in sync with the N1/Droid releases.
INSTRUCTIONS:
- First time flashing CM 6 to your Dream/Sapphire (or coming from another ROM)?
1. Unlock/root your device and install Clockwork Recovery via ROM Manager or Amon_RA's recovery image
2. Do a Nandroid backup!
3. Update your radio if necessary
4. WIPE
5. Install the ROM
5. Optionally install the Google Addon
- Upgrading from earlier CM6?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
HOW TO REPORT BUGS OR PROBLEMS?
- Was it a hard reboot? Get me the file "/proc/last_kmsg".
- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get me the full output.
- Pastebin links preferred
- Please use the issue tracker whenever possible!
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
The preferred method of installation is via ROM Manager, or you can head over to the CM Forums for manual downloads.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!3
Ezterry has started something great on xda
a source repo for gingerbread dream/sapphire
its very much a 'support yourself' affair
but if you are smart and post logcats, then some attention may be paid to it
within that thread are my Magpie builds, basically they are Ezterry's builds with CM5 like a2sdext ( Magpie ) added in.
some very kewl features with these builds
Ezterry has recently added AutoKernel to the build system ( far superior to the script based AutoKernel I cobbled together )
this means that one zip supports three different kernel types
- ebi0 ( standard 32b )
- ebi1 ( 32a and Rogers )
- 2708 ( 32b with the extra 15mb ram )
- GPS is working
- gapps and su working ( see bypass's posts in the thread )
- internet calling ( see call settings in settings )
- gmail has a bug, where you can't read 'long' emails , but the basic email app works fine
- other stuff I can't remember
in general the ROM works very well,
it doesn't have all the extra features people have come to expect from a CM, the main reason ( and I have to agree here ) is that ezterry wants a clean base, and some of the extras impinge on performance without any real gain.
if you look at ezterry's issues list on github you will see that he has indicated that he wants to shift the current build system towards one more akin to CM's , so that it can at some point be integrated with CM7
Find
ezterry's builds in post 2
http://forum.xda-developers.com/showthread.php?t=882356
The current Magpie can be found here
http://forum.xda-developers.com/showthread.php?p=10678784#post10678784
it is based on Ezterry's 2011-01-17 code
Magpie zips can be found here
http://www.mediafire.com/?0uefg5g8kyeja
regards gapps, look in that thread
I'll look at putting up some gapps zips
personally I like the minimum on system, getting most from Market
so I'll do SuperTiny, Tiny and Full Fat ( might skip the full fat , and just package extra bloat to flash over a SuperTiny )
some of the gapps that are being linked in that thread are not great, they include hdmi which is just a waste of space for us
so what are you waiting for?
nand backup and get flashing
and if you have 15-20 gb free on a Linux box, repo sync , and push some kewl changes to github2
You could have got all the files you needed in one zip file from my sig. If CM6.1 is too slow for you, there's also a tweak guide in my sig, as well.2Tutorial Update!
To everyone who used it or linked to it, my old tutorial has been updated for CM6.1.0. I also replaced the post with a link to a PDF of instructions. The PDF also contains a clickable link to download an archive of all the files needed for my setup. It's easier for me to update and also prevents my original tutorial post from ever disappearing, for whatever reason. REALLY wouldn't want to have to write that over again
Anyways, the link to the PDF guide is now in my sig, too. The link to the archived files is on the first page of the PDF. And If I ever have to update it, I'll make a post that there's an update. Hope it helps as much as it has in the past!2
mediafire lets you maintain one folder 'shortcut'
so link the folder and have as many revisions as you like
also
tinyurl has a handy feature, link a mediafire folder with a memorable name
