42 replies to this topic

[PDR447]

Feel free to discuss all things 6.0.0 and use this for small "bugs" and setup issues that don't need a whole new thread.

[laxattack]

i keep getting force close when using the gallery :-D

i keep getting force close when using the gallery :-D

[jbretz]

laxattack, on 01 September 2010 - 04:18 AM, said:

i keep getting force close when using the gallery :-D

i keep getting force close when using the gallery :-D

Obligatory did you wipe before flashing question.

[ZeroBarrier]

jbrtzfldr, on 01 September 2010 - 04:20 AM, said:

Obligatory did you wipe before flashing question.

I swear, I strongly believe if more people would just wipe everything before installing any ROM they wouldn't have the issues they so regularly have. I wipe everything a minimum of 3 times each before I even begin the process of installing any ROM (yes, that's including updates to the same bloody ROM).

Never once have I had any problems other than the normal boot loop when trying out different kernels. No FC's (unless it's from a 3rd party app that has it's own bugs), No problems with settings, widgets, wallpapers, accounts, anything. You name it, it works perfectly (unless I go and fudge it up by modding .apk's and others files).

Almost each and every single one of the "Gapps", "Wallpaper not set", CM Settings", "Launcher Pro", "Market", "GPS"; and so on, problem threads could have so easily be avoided if people would properly wipe before the installation of any ROM, and if they only checked their settings before TiBu'ing the living crap out of anything and everything...

Seriously, think about it. Not all ROMs are created equal; so why do most users think that everything working on one ROM must work on another ROM? I've always thought about it like, "Let's make a mirror image of all this stuff, and dump it straight into my fresh install of another ROM and hope it doesn't break anything; but if and when it does, I'll just post my cry's, moan's and complaints on the forums. If I have to suffer, so should everyone else."

/end rant

laxattack, on 01 September 2010 - 04:18 AM, said:

i keep getting force close when using the gallery :-D

i keep getting force close when using the gallery :-D

I see you type much like you install ROMs. I hope this can be of use to you:

Wipe, wipe, wipe!

Wipe, wipe, wipe!

[hiphopvenom]

Well i have always wiped three times before flashing.. today i noticed my camera takes pics but are not viewable in my gallery.. just shows a black screen

[PDR447]

Clear you gallery cache on the sdcard. Its in /sdcard/android and /sdcard/dcim

[jbretz]

ZeroBarrier, you just described my entire life so perfectly.

[bpyazel]

Can you add a pop-up to the forums that displays "did you wipe first?" before a person can post?  Lol

Sent from my Droid using Tapatalk

[ZeroBarrier]

jbrtzfldr, on 01 September 2010 - 06:50 AM, said:

ZeroBarrier, you just described my entire life so perfectly.

[kevdog]

that eyeball is creepy man

[ZeroBarrier]

kevdog, on 01 September 2010 - 10:10 AM, said:

that eyeball is creepy man

It's the tear that comes out every time I read a thread full of "issues" and "complaints" about certain ROMs.

[pkwjr]

In my power control widget, whenever I hit the sync button, it turns the screenlock on, which is also in the power control widget.

Any solutions?

[defkorn]

When I go to set up the Power Control widget under 'Choose Ring modes' that looks like it address the volume rocker issue of "losing" the ability to go from Sound/Vibrate/Silent.  The setting is 'Sound+Vibrate/Vibrate/Silent' but when I select it I still get the crappy 2.2 volume rocker settings.  Anyone know if this is supposed to fix that?

[cedarrapidsboy]

hiphopvenom, on 01 September 2010 - 05:27 AM, said:

Well i have always wiped three times before flashing.. today i noticed my camera takes pics but are not viewable in my gallery.. just shows a black screen

Not necessary to wipe before flashing...  but mooning is a different story!  

[AbsoluteZero]

bpyazel, on 01 September 2010 - 07:11 AM, said:

Can you add a pop-up to the forums that displays "did you wipe first?" before a person can post?  Lol

Or something requiring them to at least do a simple search for their problem as suggested.

@ZeroBarrier...don't worry, no matter how much you rant, we'll still have tons of people flashing CM over some other Rom and complaining something doesn't work. I've just come to accept it by now and if you stay in the community long, you will as well.

[bigwhite2312]

I am not sure if this is the best place to post this, but I have been having some problems with RC3 and 6.0.  I am looking for any suggestions.  Let me start from the beginning.

I have used cyanogen since rooting my phone back in Dec.  I have had problems over the months but nothing I could not fix with some searching through the forums here. (a big thank you to everyone who contributes and helps noobs like us)  My problems started when updating to RC3.  RC3 was pretty stable and I wanted to overclock beyond the default 800 Mhz.  So I downloaded one of the Chevy kernels, I believe it was the 1.2 Ghz.  Everything was fine for a day or so, then I would get random reboots.  I figured it must be the kernel so I downloaded the 1.1 Ghz and had the same issues.  I then downloaded just about every kernel I could find and the phone would randomly reboot.  

I stuck it out thinking that once 6.0 came out it would fix these issues.  As soon as 6.0 was released, I did a backup and wiped my data and cache to install 6.0.  I did not try to install any kernels, just left it default.  I let google restore all my apps and then I started using the phone.  First thing I noticed is that my cpu was getting very hot.  Not according to SetCPU but just by feeling the back of the phone next to the camera.  First thing I tried was to go into the settings to change a few things because everything was set back to default.  As soon as my setting screen came up, I clicked the about phone option.  The screen froze.  I left it a minute to see if it just needed to catch up.  The screen went off about 30 seconds after the freeze and the power button or sliding out the keyboard did not turn it back on.  I waited about 5 minutes and decided it was time for a battery pull.  The phone booted back up just fine, and as soon as I saw the lock screen, I unlocked it.  It looked like it was going through the normal startup apps and things.  I set the phone down and left it for about a half hour.  I came back and turned the phone on.  I unlocked it and saw my home screen.  I try to swipe back and forth to another screen and it is frozen again.  This time the screen is not turning off.  I look at the clock in the notification bar and it is not working. The phone froze at 3:32 pm and it was now 3:35 and the clock was not updating.  battery pull...

This time I went in and wiped the data and cache again and flashed 6.0 again with the gapps.  when it was done and I logged into my google account, I unchecked the backup my google data option so it would not restore my apps. Looked like everything was stable until I opened the browser.  Google main page came up and then the phone froze again. waiting... battery pull.  I figured it was about time to go back to my RC3 backup.  As soon as it was restored I booted the phone up, and within a few minutes of using it, froze again... battery pull.  I was getting frustrated at this point, I wiped data and cache again and installed RC3 instead of 6.0.  Let it install all my apps and then went to unlock the phone and it froze again.  I wiped data and cache once again, flashed 6.0 back on then did not let it restore my apps.  Finally it seemed like it was working correctly.  I went to bed.  

I set my alarm on my phone and it did go off in the morning.  I clicked the camera button to turn the alarm off and got up.  Came back to the phone in about 15 minutes.  It let me unlock and started to bring up the default home screen, phone froze... battery pull. The only thing I can think of at this point is that maybe my cpu got to hot at some point and whenever it heats up to a certain temperature it starts to error out, causing the freezing.  I decided to use RSD lite and flash the stock 2.1 sbf file back to the phone.  I had plenty of problems with that as well, but I finally got it working. (FYI, never do the sbf flash unless you are at full battery.  my battery died in the middle and gave me a code corrupt error every time I tried to boot the phone.)  I was just about at the point of going back to the VZW store to see if they can do anything to help.  But once I got the stock unrooted 2.1 installed and working, I have been fine.  It has now been 1 day and I have not had any crashes or freezes.  

I think I have narrowed it down to either a ROM issue or a kernel issue.  My only evidence is that when running a stock OS, the phone works fine.  I am wondering if somehow the kernel was stuck in the filesystem somewhere causing issues even after doing a wipe of data and cache.  I ran fix permissions in ROM Manager as well but that did not help.  I want to give the phone another day or so to make sure it is stable, then I might root and flash back to 6.0 to see if it is doing any better.

Any suggestions would be appreciated. I put this comment together on the fly so if you have any questions about what I have done so far, I will answer to the best of my ability.
thanks.

Update: Just went to turn my phone on because I saw the notification light blinking.  I click the power button and the bottom buttons light up but the screen is still dark.  I slide open the keyboard but nothing changes. battery pull. Not sure what to do now...

Edited by bigwhite2312, 01 September 2010 - 03:42 PM.

[laxattack]

ZeroBarrier, on 01 September 2010 - 05:00 AM, said:

I swear, I strongly believe if more people would just wipe everything before installing any ROM they wouldn't have the issues they so regularly have. I wipe everything a minimum of 3 times each before I even begin the process of installing any ROM (yes, that's including updates to the same bloody ROM).

Never once have I had any problems other than the normal boot loop when trying out different kernels. No FC's (unless it's from a 3rd party app that has it's own bugs), No problems with settings, widgets, wallpapers, accounts, anything. You name it, it works perfectly (unless I go and fudge it up by modding .apk's and others files).

Almost each and every single one of the "Gapps", "Wallpaper not set", CM Settings", "Launcher Pro", "Market", "GPS"; and so on, problem threads could have so easily be avoided if people would properly wipe before the installation of any ROM, and if they only checked their settings before TiBu'ing the living crap out of anything and everything...

Seriously, think about it. Not all ROMs are created equal; so why do most users think that everything working on one ROM must work on another ROM? I've always thought about it like, "Let's make a mirror image of all this stuff, and dump it straight into my fresh install of another ROM and hope it doesn't break anything; but if and when it does, I'll just post my cry's, moan's and complaints on the forums. If I have to suffer, so should everyone else."

/end rant



I see you type much like you install ROMs. I hope this can be of use to you:

Wipe, wipe, wipe!

Wipe, wipe, wipe!

Yea sorry bout the double post lol. Yea I wiped 3 times. I think it was the kernel. I changed that and im good now. I do appreciate your rant it is needed sometimes!

[aloha_girl]

hiphopvenom, on 01 September 2010 - 05:27 AM, said:

Well i have always wiped three times before flashing.. today i noticed my camera takes pics but are not viewable in my gallery.. just shows a black screen

Media Scanner found in Dev Tools, pops the "missing" photos back into the gallery.

[Piafinho]

defkorn, on 01 September 2010 - 12:25 PM, said:

When I go to set up the Power Control widget under 'Choose Ring modes' that looks like it address the volume rocker issue of "losing" the ability to go from Sound/Vibrate/Silent.  The setting is 'Sound+Vibrate/Vibrate/Silent' but when I select it I still get the crappy 2.2 volume rocker settings.  Anyone know if this is supposed to fix that?

there is currently a bug with vibrate on the widget. So it doesn't toggle well to vibrate.
It shall be in a nightly soon.

[ZeroBarrier]

Piafinho, on 01 September 2010 - 08:49 PM, said:

there is currently a bug with vibrate on the widget. So it doesn't toggle well to vibrate.
It shall be in a nightly soon.

He's actually asking if the Power Control widget changes the physical volume rocker on the phone. To answer his question; no, it does not.