• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[ROM] aospCMod | AOSP 2.3.4 / CM7 (Gingerbread) [05/23/11]

Any idea why my screen wont respond when I touch it? I installed the 2/23(22) Rom and it started doing it. I nandroided back to the 2/18 one and it works.
 
Try clocking it down a little and see if that helps, try 176 to 691 and see what happens, when mine was higher I had the same issue from time to time


kellysa111 said:
Any idea why my screen wont respond when I touch it? I installed the 2/23(22) Rom and it started doing it. I nandroided back to the 2/18 one and it works.
Click to expand...
 
kellysa111 said:
Any idea why my screen wont respond when I touch it? I installed the 2/23(22) Rom and it started doing it. I nandroided back to the 2/18 one and it works.
Click to expand...

Before doing a nandroid restore, if your phone becomes slow and unresponsive, I would suggest booting to recovery and wiping cache and Dalvik cache, then reboot the phone and see if that helps.;)
 
so AOSP links to the 3.0.0.5 CM recovery .img file -- how do I install this? I currently have RA 1.2.7 and Im wanting to install CM recovery so I can flash GB. I downloaded the latest Rom Manager which is 3.0.1.0 -- will this flash the wrong version of the recovery? thanks for curing my confusion
 
That is correct, you boot into recovery, Nandroid your current Rom, then do a full wipe as describe here many times, then you flash GB and then flash the latest Gapps, and then reboot and set your phone up


vng10 said:
so you just wiped everything and flashed GB and gapps?
Click to expand...
 
So the 2/25 update is running smooth as butter, and definitely seems faster. However, and I know this is trivial at best, I miss the 3D gallery. I know it was removed for speed purposes and all, but it always worked wonderfully for me and I really ended up liking it. Now it's gone, and I want it back. Anyway, that's my mini rant. ROM is fantastic and runs great, minus my one complaint. :)
 
hi all, just curious. Have tried to install AOSP's last ROM and the one just released. Did the whole thing as instructed in the wiki - backup, CWM recovery, wiped everything including davlik, then installed 2.3.2 and gapps (gapps wouldn't install unless I toggled so it would accept unsigned, for some reason, tho).
Rebooted, and now it hangs on the black c\screen w/ white HTC logo. After half hour I called it quits. Any reason I should let it go longer? Coming from Cyanogen's 6.1.
 
what do you need to wipe before flashing a kernal if you have problems?(for my general questions thread)
 
You need to make sure you do a proper wipe,

Full Wipe Means

CWM Recovery
Wipe data/Factory Reset
Wipe cache partition
Advance/Wipe Davlik cache
Partitions Menu/Format Boot
Partition Menu/Format System
Partition Menu/Format data
Partition Menu/Format Cache


laithis said:
hi all, just curious. Have tried to install AOSP's last ROM and the one just released. Did the whole thing as instructed in the wiki - backup, CWM recovery, wiped everything including davlik, then installed 2.3.2 and gapps (gapps wouldn't install unless I toggled so it would accept unsigned, for some reason, tho).
Rebooted, and now it hangs on the black c\screen w/ white HTC logo. After half hour I called it quits. Any reason I should let it go longer? Coming from Cyanogen's 6.1.
Click to expand...
 
DonB said:
You need to make sure you do a proper wipe,

Full Wipe Means

CWM Recovery
Wipe data/Factory Reset
Wipe cache partition
Advance/Wipe Davlik cache
Partitions Menu/Format Boot
Partition Menu/Format System
Partition Menu/Format data
Partition Menu/Format Cache
Click to expand...

Yep, that's exactly what I did, in that order. When rebooting, it quickly went thru 5 reboots, then hung on the black screen w/htc logo. Waited 30 mins then gave up & flashed clockworkmod recovery back to Cyanogen's 6.1. Any ideas? Did I just get too impatient and shoulda hung with it for a while longer?

_____
Just tried again, cycled reboot 10 times in succession then hung on htc logo.
 
You can unzip it from the previous version and install it, it is in the app folder, and if you want to uninstall the 2 D one let me know


KitsapAndroid said:
So the 2/25 update is running smooth as butter, and definitely seems faster. However, and I know this is trivial at best, I miss the 3D gallery. I know it was removed for speed purposes and all, but it always worked wonderfully for me and I really ended up liking it. Now it's gone, and I want it back. Anyway, that's my mini rant. ROM is fantastic and runs great, minus my one complaint. :)
Click to expand...
 
laithis said:
Yep, that's exactly what I did, in that order. When rebooting, it quickly went thru 5 reboots, then hung on the black screen w/htc logo. Waited 30 mins then gave up & flashed clockworkmod recovery back to Cyanogen's 6.1. Any ideas? Did I just get too impatient and shoulda hung with it for a while longer?

_____
Just tried again, cycled reboot 10 times in succession then hung on htc logo.
Click to expand...

mine did the same thing today, on the front page of the rom repo wiki it says if it does this you need to install a kernel. going to try the jasonm kernel now
 
laithis said:
hi all, just curious. Have tried to install AOSP's last ROM and the one just released. Did the whole thing as instructed in the wiki - backup, CWM recovery, wiped everything including davlik, then installed 2.3.2 and gapps (gapps wouldn't install unless I toggled so it would accept unsigned, for some reason, tho).
Rebooted, and now it hangs on the black c\screen w/ white HTC logo. After half hour I called it quits. Any reason I should let it go longer? Coming from Cyanogen's 6.1.
Click to expand...

The same thing happens to me, so I just flash Deca's kernel and then it works fine.
 
srkmagnus said:
LMAO. Hey, we all have those days when the small things get to us. Are you buy chance using an overclock manager like setcpu or ocverclock widget? Only reason I ask is because the settings could be causing the phone to be laggy as you described. Just a thought.

Hope the problem is fixed for you so that you can enjoy the full potential of the phone.
Click to expand...

Nope... I figured the ROM had a manager built in. And sad to say, I'm on day 5 I believe... and the phone is very jaggedy, I'm not getting email notifications, I have to manually refresh my emails sometimes to get emails from hours ago, and I've had a few instances where my phone rings and then goes right to voicemail :(
 
Toyzruskid1976 said:
Nope... I figured the ROM had a manager built in. And sad to say, I'm on day 5 I believe... and the phone is very jaggedy, I'm not getting email notifications, I have to manually refresh my emails sometimes to get emails from hours ago, and I've had a few instances where my phone rings and then goes right to voicemail :(
Click to expand...

:( Try flashing another ROM and see if the problem persists. I'd recommend a Froyo based ROM and compare your findings.

The ROMs don't have built in overclock management. The kernals allow you to overclock to a certain speed but don't allow you to control the parameters unless you install an app, widget or battery tweak script.
 
srkmagnus said:
:( Try flashing another ROM and see if the problem persists. I'd recommend a Froyo based ROM and compare your findings.

The ROMs don't have built in overclock management. The kernals allow you to overclock to a certain speed but don't allow you to control the parameters unless you install an app, widget or battery tweak script.
Click to expand...

What kernel should I be rocking? I just realized I didn't put a mod kernel on my phone. I've used CM7 with no issues. I honestly forget why I removed it and went to stock for a few months. I love this new rom, but the jaggedy issue is a concern
 
I believe aosp uses Decad3nce's kernal, which is clocked to 691 max. Decad3nce has another kernal source that you can flash which increases to 768 maximum, but you may expect unstableness.

Also, Decad3nce has a battery tweak that allows you to set the overclock parameters, which you can also grab on XDA. It lets you sets the minimum and max speeds. Very good script that I would recommend using.

Read through the first post to learn more about the different kernals. The tweak is located further down the 1st post:

[Kernel][GPL] DecaFuct [2.6.29.6][12/22/2010] - xda-developers
 
AOSP uses his own kernel for the GB ROM. The about phone option in the settings menu will tell you. The GB kernel can clock up to 768. Aosp GB also has a poor man's setcpu baked into it so that you can adjust the cpu speeds to whatever works for you. The stock kernel is quite functional if you ask me. Deca does make nice kernels as well, but I see no need for the change unless the stock one is causing you problems.
 
Did you read what I mentioned to you about the 3D Gallery ?


KitsapAndroid said:
AOSP uses his own kernel for the GB ROM. The about phone option in the settings menu will tell you. The GB kernel can clock up to 768. Aosp GB also has a poor man's setcpu baked into it so that you can adjust the cpu speeds to whatever works for you. The stock kernel is quite functional if you ask me. Deca does make nice kernels as well, but I see no need for the change unless the stock one is causing you problems.
Click to expand...
 
You must log in or register to reply here.
Back
Top Bottom