Stuff screws up after root/installing BB/overclocking

Discussion in 'Android Hacks and Help' started by brando56894, Mar 14, 2010.

  1. brando56894

    brando56894 Active Member

    Joined:
    Mar 9, 2010
    Messages:
    1,217
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    New Jersey
    Ratings:
    +0
    I followed everything in Matth3w's guide and everything went to hell after I installed ChevyNo1's 5 slot 1.25 kernel. As soon as I installed it and booted into the desktop stuff started to FC and its only gotten wose as time goes on, the audio also screws up when playing stuff.

    How can I fix this?
     
  2. Cornholieo

    Cornholieo Member

    Joined:
    Feb 15, 2010
    Messages:
    46
    Likes Received:
    0
    Trophy Points:
    6
    Ratings:
    +0
    Overclocking

    I read in a few places that going over 1ghz did not turn out well for many people. I chose to only use his 5 up to 1ghz, and have not had any problems. :greendroid: I just did mine last night, and have been soooo happpy :icon_ banana:
     
  3. KZIWarrior

    KZIWarrior Silver Member

    Joined:
    Dec 31, 2009
    Messages:
    2,609
    Likes Received:
    2
    Trophy Points:
    103
    Location:
    Nashville, TN
    Ratings:
    +2
  4. brando56894

    brando56894 Active Member

    Joined:
    Mar 9, 2010
    Messages:
    1,217
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    New Jersey
    Ratings:
    +0
    thanks ill try that out later, i just restored my phone to the backup I made before I installed bugless beast.
     
  5. Dxun

    Dxun Member

    Joined:
    Mar 9, 2010
    Messages:
    257
    Likes Received:
    1
    Trophy Points:
    18
    Ratings:
    +1
    Im using Chevy 5 slot running at 1100 and its running like a champ. I was running 1250 at 1st but the phone was constantly rebooting, and force closing apps.
     
  6. Slider46

    Slider46 Member

    Joined:
    Mar 3, 2010
    Messages:
    175
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    I had to step down to Chevy's 10-slot 1.0Ghz kernel to be stable. 1.25Ghz would run for a short time and then completely crash (hard reboot).
     
  7. brando56894

    brando56894 Active Member

    Joined:
    Mar 9, 2010
    Messages:
    1,217
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    New Jersey
    Ratings:
    +0

    I tried it without wiping (since he says you don't need to if you have 2.1) and it wouldn't boot past the m no matter what kernel or voltage level I tried. Then I completely wiped My Droid and reinstalled it but the same thing still happens. Atleast with Chevy's kernel it would boot, with this it won't even boot.

    Edit: I just installed smoked glass v6 and everything seems fine so far I'm stress testing it now and its been fine for about the last 20 minutes.
     
    #7 brando56894, Mar 15, 2010
    Last edited: Mar 16, 2010
  8. brando56894

    brando56894 Active Member

    Joined:
    Mar 9, 2010
    Messages:
    1,217
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    New Jersey
    Ratings:
    +0
    Stuff still screws up, it works fine for a few days but then it starts to crash/lag/get really hot/ etc... I'm running at 1.1ghz and the phone was charging via USB and I picked it up to take a call and it was physically hot the top temp (cpu?) was 160F!!!

    I just wiped it and I'm gonna move the kernel and keep testing it out.
     
  9. BayouFlyFisher

    BayouFlyFisher Rescue Squad
    Rescue Squad

    Joined:
    Dec 10, 2009
    Messages:
    4,958
    Likes Received:
    17
    Trophy Points:
    168
    Location:
    Baton Rouge, LA
    Ratings:
    +17
    The normal response to boot failure or FC's after installing a new kernel is to simply go down one level on the available kernels. If you installed a 1.2 just go down to the next lowest kernel such as a 1.1 or 1.0.

    Also, prior to installing a new kernel make sure you have Setcpu set to a low speed such as 550 or 600 if you have it set to start on reboot.