Hey Guys.
I'm using CM 11 as my daily driver for my i9300 with PA GApps from 23-1. Everything was ok till i updated to 20140202 nightly last night.. i got the screen tearing/API 1.1 issue like most people. Also found the Hardware/capacative keys (Menu and Back) not working. long press works as it should but not with one tap. volume rocker is also affected.
I then did some searching over xda and found some possible solutions. I installed newer GApps from 1-2, but nothing happened. Now I'm on the latest CM11nighlty 20140203, it fixed the screen tearing issue but no luck with the hardware buttons still. can anyone help me with this?
Hint: I wipe Cache and Dalvik every time i install a new nightly.
ahmedrehan said:
Hey Guys.
I'm using CM 11 as my daily driver for my i9300 with PA GApps from 23-1. Everything was ok till i updated to 20140202 nightly last night.. i got the screen tearing/API 1.1 issue like most people. Also found the Hardware/capacative keys (Menu and Back) not working. long press works as it should but not with one tap. volume rocker is also affected.
I then did some searching over xda and found some possible solutions. I installed newer GApps from 1-2, but nothing happened. Now I'm on the latest CM11nighlty 20140203, it fixed the screen tearing issue but no luck with the hardware buttons still. can anyone help me with this?
Hint: I wipe Cache and Dalvik every time i install a new nightly.
Click to expand...
Click to collapse
Its a nightly and filled with bugs. Factory reset and flash a stock rom and work your way up from there. And try to use STABLE versions of roms.
~DemonLord~ said:
Its a nightly and filled with bugs. Factory reset and flash a stock rom and work your way up from there. And try to use STABLE versions of roms.
Click to expand...
Click to collapse
Thanks. Already did a factory reset and a clean install. All's good now
Related
I installed Cyanogenmod 7 a week ago, and everything was pretty much working fine.
Randomly today, all 4 of the soft buttons stopped working in the middle of me using my phone. I believe I was checking scores on an NFL app. Regardless, reapplying the CM7 zip didn't fix it. I tried factory reset, wipe cache, wipe dalvik cache. Nothing.
Decided to try to reroot. Reapplied ED05, which is what I did before I installed CM7. Got back to essentially factory... soft buttons still don't work. Reinstalled CM7... took, but soft buttons won't work.
I thought I read somewhere that this is an issue with gapps, but I can't seem to find that page or people discussing it again. Installing gapps again didn't work.
I'm willing to get my phone back to it's most basic level, and even erase the SD card if I need to, but not sure how to clear my phone moreso than my reverting back to ED05.
Thanks for your input guys.
Also, I had reinstalled my apps using Titanium, but not the app data. Again, everything was just fine for a week.
Also, having done a bunch of flashing and what not, I dont' know what happened, but now when I long press the power button, the menu comes up. When I try to use volume up/down to navigate to power off, all I get is volume going up and down
So, i know this thread is sort of dead, but this happened to my fascinate a while back with a version of CM7 mtd (55 maybe?)... I'm fairly convinced that the sensors for the buttons (and the lights for that matter) are completely shot, but I can't really test that. I have flashed back to stock, re-rooted it,and done everything I can think of to fix it.
You probably messed the phone up for good... my advice (if you haven't already done it): get a new phone.
I've noticed that when I revert back to stock ED05, and flash CM7 on top of that, it doesn't work right. minor to major glitches appear...
What i did was flash back to stock ED05, then ran the update to Gingerbread EH03... Then flashed CM7 with Glitch v13 kernel. seemed to fix a lot of my issues.
idk if this helps or it's just a flook, but just sayin...
Will try this out
JJ5150 said:
I've noticed that when I revert back to stock ED05, and flash CM7 on top of that, it doesn't work right. minor to major glitches appear...
What i did was flash back to stock ED05, then ran the update to Gingerbread EH03... Then flashed CM7 with Glitch v13 kernel. seemed to fix a lot of my issues.
idk if this helps or it's just a flook, but just sayin...
Click to expand...
Click to collapse
Thanks for the suggestions. I'm having the same issues as the OP with failing soft keys after flashing through CM7 to an android 4.1 based ROM, Paranoid Android. Is the Glitch kernel built into Cyanogenmod 7 or did you load it separately?
Charcaroth said:
Thanks for the suggestions. I'm having the same issues as the OP with failing soft keys after flashing through CM7 to an android 4.1 based ROM, Paranoid Android. Is the Glitch kernel built into Cyanogenmod 7 or did you load it separately?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1488976
If you are already on ICS just wipe cache and dalvik cache and flash. If not just flash up to ICS and flash kernel with ROM (same cwm session). You may want to do some reading in that thread first to make sure you get right version for your ROM.
Sent from my SCH-I500 using xda premium
I can't seem to find a stable release, yet a lot of youtube videos show people using it?
I've tried the nightly versions and for some reason it just hangs at the samsung load screen.
Anyone know what's happening with it? are we waiting on CM9+ICS instead of CM 7.1 now?
richfreestone said:
I can't seem to find a stable release, yet a lot of youtube videos show people using it?
I've tried the nightly versions and for some reason it just hangs at the samsung load screen.
Anyone know what's happening with it? are we waiting on CM9+ICS instead of CM 7.1 now?
Click to expand...
Click to collapse
I've installed a couple of the nightlies and not had major issues. There were indeed bugs, which made me move on to other ROMs (among other reasons, including the fact that my old HD2 had CM7 and it got a bit old).
As far as my experience goes, the nightlies have been quite stable. As mentioned, there were bugs here and there, and a force close from time to time. But I didn't have the problem you've mentioned with hanging at install.
They did take a while to load the first time, longer than I remember was the case on my HD2. Did you wait long enough? Delvic/cache cleared?
EDIT: I also found a CM9 around New Years, but it wasn't as stable and had charging issues. But I think it's out and the waiting's over, really.
EDIT AGAIN: The other option would be to try out the official ICS release, which can be found at samfirmware.com. That's my plan for the weekend.
like the previous...Sounds like your flashing over existing roms without wiping everything first...From recovery mode after backing up, the best way I find is to wipe data/clear cache and wipe dalvic cache from advanced menu before flashing any roms...that way your starting with a clean slate and will be less conflictions from old to new.
for me CM7.1 not stable
I'm waiting a stable CM9 its promising
If you follow the instructions on how to install it, it's stable for everyone. I'm using it for many many months now, and it's stable.
If you're coming from other ROM's, make sure you do a FULL wipe, and flash the rom TWICE in a row, without rebooting recovery.
And yes, we're waiting for CM9. CM7 is not supported anymore for SGSII.
I cleared the data, the cache, went into advanced and cleared the dalvik cache.
Installed the nightly, which I thought was trange was only 100mb, normally ROM's are like 300mb.
I'll try flashing the ROM twice as TheSaw has said. However, after seeing that CM7 isn't supported, I may think twice, i'm just getting bored of the stock.
Might also be worth noting, i'm using [email protected] #k2-18 kernel.
Also, by the way Sean is here, did you know you've got a USA flag in your mini profile under your username? will the official release be a odin flash? or can I just use a .zip through CWM to flash it? and would I still be able to use the speedmod kernel with ICS?
Always working for me and thousands of others .
Usual story is wrong install .
jje
I managed to get this working, by installing the ROM once, and then installing it again straight after.
I was just wondering, is there a way to move the lock screen lock down to the bottom of the screen, i.e. above the unlock and camera buttons? and is there a way to change the clock?
Hey
I’m am a regular CM9 user on my Galaxy S II. It was running very well till the last month (build 20120330). Since build 20120402 I’ve been getting weird problems. with Gapps. Gmail and News & weather crash as soon as phone starts and Play Store always gives a “Server error” message. I’ve tried build 20120317 and 20120304.
I don’t know where am I going wrong. Here are the steps that I follow while flashing CM9 update:
Flash CM9 update > then Gapps > Wipe Cache > Wipe Dalvik Cache
I’ve even tried side installing market from APK instead of flashing Gapps but that makes even the Store crash everytime I try to open it. Clearing data doesn’t work.
Further, factory resetting the phone and then flashing CM9 disables the home button. It only works for unlocking the display. The power button options get reduced to only Power Off, Restart and Airplane Mode. Screenshot, profile, sound options all disappear.
It’s hard to live with CM9, other ROMs aren’t that good. They lack in either functions or battery life. Can somebody help me please?
why not make a clean install using the resurrection edition and then update to the latest build and see if the problem persists? using the resurrection edition should solve your issues.
Hey bala_gamer, thanks for your quick reply. I'll do that right now and let you know if it solved my issue.
EDIT: Resurrection build (20120330) is too old It hasn't been updated this month. Could you tell me which version of Gapps are you using btw?
Saketme said:
Hey bala_gamer, thanks for your quick reply. I'll do that right now and let you know if it solved my issue.
EDIT: Resurrection build (20120330) is too old It hasn't been updated this month. Could you tell me which version of Gapps are you using btw?
Click to expand...
Click to collapse
its ok with the resurrection build, its just a week old
im using the latest gapps pack 17/3/12
http://goo.im/gapps/gapps-ics-20120317-signed.zip
Hey, I looks like you didn't read my post correctly. CM9 build 20120330 is already working fine for me, the builds released in this month are bugging me. :-(
Hi all
I'm not even sure that's the right section :\
I recently installed the latest MIUI Italian rom (It shall be version 3.7.12) and it worked like a charm (installed with full wipes)... Until today.
I was simply browsing Facebook when the entire phone freezed.
I tried to reboot keeping pushed the Power button, but after Samsung bootscreen (not the one animated, the one before the kernel), black screen.
I tried to:
- Wipe cache & dalvik
- Fix permissions
- Re-flash the rom without any wipe
- Removing the battery and putting it back again inside
But no clue, no one of my solution worked, so I restored a previous AOKP backup.
Since I thought that finally i've found my perfect rom, and i've set all the apps, i'd rather not wipe...
How can I get that device fixed?
And PS: Sorry for my english
bonny1992 said:
Hi all
I'm not even sure that's the right section :\
I recently installed the latest MIUI Italian rom (It shall be version 3.7.12) and it worked like a charm (installed with full wipes)... Until today.
I was simply browsing Facebook when the entire phone freezed.
I tried to reboot keeping pushed the Power button, but after Samsung bootscreen (not the one animated, the one before the kernel), black screen.
I tried to:
- Wipe cache & dalvik
- Fix permissions
- Re-flash the rom without any wipe
- Removing the battery and putting it back again inside
But no clue, no one of my solution worked, so I restored a previous AOKP backup.
Since I thought that finally i've found my perfect rom, and i've set all the apps, i'd rather not wipe...
How can I get that device fixed?
And PS: Sorry for my english
Click to expand...
Click to collapse
miui 3.7.12(180mb) is update from 3.7.5(405mb), i think you need flash 3.7.5 for base rom and after update with 3.7.12
nik60 said:
miui 3.7.12(180mb) is update from 3.7.5(405mb), i think you need flash 3.7.5 for base rom and after update with 3.7.12
Click to expand...
Click to collapse
But until this morning my device was working like a charm, without any problems :\
EDIT: I kept this rom installed from one week ago, and it worked perfectly until this morning...
bonny1992 said:
But until this morning my device was working like a charm, without any problems :\
EDIT: I kept this rom installed from one week ago, and it worked perfectly until this morning...
Click to expand...
Click to collapse
mistery of the rom ?? which kernel you use ?
i have miui in secondrom with dorimanx kernel 8.35 and working fine(for now)
nik60 said:
mistery of the rom ?? which kernel you use ?
i have miui in secondrom with dorimanx kernel 8.35 and working fine(for now)
Click to expand...
Click to collapse
It's because this that I'm asking here
Ok, I got a question what to do now.
The following happened.
I updated the nightly CM10.1 from the settings menu. Normally this works fine. I forgot to make a backup (DUMB). When CM10.1 restarted it never came further than the boot screen (Samsung logo). After waiting for more than 30 minutes I decided to restart the device (get rid of battery). Now CM10.1 won't start again.
Luckily I had a backup, but it was from CM9 (at least I can call). I already tried to install CM10.1 again, but whit no result (bootlooping again).
How to install CM10.1 again? From CM9. What did I forget?
Hope someone can help.
Cm10.1 is no good. Unreliable I think. Try aokp milestone 2 for a solid Rom. If you really want it
Mounts and storage
Format
Data
system
Cache
Wipe dalv cache in advanced
Flash Rom
flash gapps
wipe cache
wipe dalv
Reboot
Enjoy.
or read op first post on first page
I've only just installed CM10.1 on my S2 today. I encountered the same problem with cm-10.1-20130722-NIGHTLY-i9100
However, 0723 worked fine for me. Give that (the latest at time of writing) a go perhaps?
andrewwright said:
Cm10.1 is no good. Unreliable I think. Try aokp milestone 2 for a solid Rom. If you really want it
Click to expand...
Click to collapse
I did, and it works now, luckaly I made a backup on my google account so all apps are downloaded
Thanks for your solution!
ps. Is there an overview what the big differences are between CM10.1 and aokp m2?
baszer said:
I did, and it works now, luckaly I made a backup on my google account so all apps are downloaded
Thanks for your solution!
ps. Is there an overview what the big differences are between CM10.1 and aokp m2?
Click to expand...
Click to collapse
Easy way to put it is cm 10.1 unstable aokp milestone 2 stable. Simple as that. Also more changeable things in aokp. Cm fanboys wont like what I put but they no its the truth :thumbup: glad you sorted your problem :thumbup: