Hi,
I recently installed the Slim CM10 rohan007 build from A_U post
and everything have been working great because of the little ram it consumes,
except for the home key, probably there's something obvious that I've not seen, but I can't get it working, it just does nothing.
I've tested the keys with clockworkMod key test and it's ok, checked the layout files in /system/usr/...
tried with another laucher, tried with another framework-res.apk and tried wiping everything from cwm.
What other things could I try?
Do you have any clue of what the problem could be?
Thanks!
is it working in other roms
Ed_OS said:
Hi,
I recently installed the Slim CM10 rohan007 build from A_U post
and everything have been working great because of the little ram it consumes,
except for the home key, probably there's something obvious that I've not seen, but I can't get it working, it just does nothing.
I've tested the keys with clockworkMod key test and it's ok, checked the layout files in /system/usr/...
tried with another laucher, tried with another framework-res.apk and tried wiping everything from cwm.
What other things could I try?
Do you have any clue of what the problem could be?
Thanks!
Click to expand...
Click to collapse
Hahaha!That happened when I flashed my own ROM
I don't know what I did but it worked again!
Try to reboot it.
Radu M. ^_^
raducu7890 said:
Hahaha!That happened when I flashed my own ROM
I don't know what I did but it worked again!
Try to reboot it.
Radu M. ^_^
Click to expand...
Click to collapse
Thanks!
It's solved now.
Just -> wiped, installed, wiped again, installed gapps and it worked
Related
I've got CM7 running and everything is perfect...But I decided to remove the lockscreen that I had enabled earlier and now the screen is locked and there is seemingly no way to unlock it.
Under the lockscreen settings, I know that I enabled the first and third options thinking that all I would have to do is press the "N" button on the bottom to unlock but nope!
Can anyone help or am I forced to completely reset this.
lol i did the same thing as you to try and see if i could be of any help but i also got stuck at the lockscreen.
the menu button is the two rectangles (to the right of the home softkey) and not the 'n' button. well anyways i tried both the 'n' and the menu soft key and nothing happens. i guess this could be a good excuse to update to the stable cm7 as i dont think this can be undone otherwise
LOL I'm sorry to hear that...I wasn't expecting someone to try the same.
Well, if I have to install a new build, do I simply install over the existing in CWM or do I have to format a section only...I'm happy with the kernel. Do I have to reinstall Gapps?
you can simply reinstall over the existing cm7 build without formatting anything and you dont have to reinstall gapps.
however two things to note:
1. if gapps force close after flashing a newer cm7 build, you will have to reflash the gapps. this has happened very rarely while updating versions of other roms but it has happened.
2. if the lockscreen still stays the same after flashing the new cm7 build, that means that the cm7 settings were not reset. if this is the case, we both will have to do a full system, data and cache format using cwm and then flash cm7. hope it doesnt come to that.
Well you're right...it doesn't reset the system. I'll do the full reinstall tomorrow...thanks though for you help!
3rdman said:
I've got CM7 running and everything is perfect...But I decided to remove the lockscreen that I had enabled earlier and now the screen is locked and there is seemingly no way to unlock it.
Under the lockscreen settings, I know that I enabled the first and third options thinking that all I would have to do is press the "N" button on the bottom to unlock but nope!
Can anyone help or am I forced to completely reset this.
Click to expand...
Click to collapse
Check my posts. Can unlock screen with adb then change settings.
3rdman said:
Well you're right...it doesn't reset the system. I'll do the full reinstall tomorrow...thanks though for you help!
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?p=12542267#post12542267
already know how to use adb, so your instructions were real easy to follow. cheers mate! saved me formatting system and data
Thanks for the adb suggestion but I'm far too impatient to actually wait for help so I reinstalled everything.
Just as well really as I really wanted to jump to the latest version on a clean install. Everything is running beautifully (again). Thanks to all to those that posted here!
So i successfully installed rom manager from market and got 3.0.2.8 recovery. Backup worked like a charm. Then i tested "Fix permissions" and it did bad things to my phone... i lost all text almost everywhere after the recommended reboot... luckily i had a fresh backup and the restore worked just as intended.
So what good things is this "Fix permissions" supposed to do?
stenull said:
So i successfully installed rom manager from market and got 3.0.2.8 recovery. Backup worked like a charm. Then i tested "Fix permissions" and it did bad things to my phone... i lost all text almost everywhere after the recommended reboot... luckily i had a fresh backup and the restore worked just as intended.
So what good things is this "Fix permissions" supposed to do?
Click to expand...
Click to collapse
When u have FC issues (forced closes of apps), Fix Permissions usually will resolve it.
temasek said:
When u have FC issues (forced closes of apps), Fix Permissions usually will resolve it.
Click to expand...
Click to collapse
Yes that's what it says in the app, but the lost of text issue,,, is that supposed to happen? Is it a bug?
stenull said:
Yes that's what it says in the app, but the lost of text issue,,, is that supposed to happen? Is it a bug?
Click to expand...
Click to collapse
Fix permissions will not do what u described. Nothing of that sort.
temasek said:
Fix permissions will not do what u described. Nothing of that sort.
Click to expand...
Click to collapse
Well but it did... i tried to reboot 3x before i did a recovery.
Have u tried it out?
Im on MoDaCo Fr12 - Vanilla Edition and eternity 1.3 kernel.
stenull said:
Well but it did... i tried to reboot 3x before i did a recovery.
Have u tried it out?
Im on MoDaCo Fr12 - Vanilla Edition and eternity 1.3 kernel.
Click to expand...
Click to collapse
I've use ROM Manager and CWM for awhile now. And to answer your question, yes I did a fix permissions thru RM on my O2X. I'm on rooted stock ROM. No issue.
temasek said:
I've use ROM Manager and CWM for awhile now. And to answer your question, yes I did a fix permissions thru RM on my O2X. I'm on rooted stock ROM. No issue.
Click to expand...
Click to collapse
Ok, i will replicate it on my lunch and see if it happens again...
It's like the programmer and his car after he survives downhill with breaks out of order, -lets try that again and see whats happens
stenull said:
Ok, i will replicate it on my lunch and see if it happens again...
It's like the programmer and his car after he survives downhill with breaks out of order, -lets try that again and see whats happens
Click to expand...
Click to collapse
LOL
I'm used to risks of daily flashing ROMs. CM ROM Nightly flasher myself (with my Nexus One).......
Ok so im back and has replicated my experiment with success...
Strange huh?
as said im on MoDaCo Fr12 - Vanilla Edition + eternity 1.3 kernel, could that be the problem? Maybe someone else on same setup could give it a try?
Fonts are gone here as well after selecting "Fix permissions" by accident.
On stock ROM and wasn't even rooted yet (only did a Nandroid backup).
Hello, I'm not particularly new to Android, nor am I new to the prospect of flashing roms. However, I recently flashed an upgrade of cm10.1 to my Nook HD via recovery and I'm now stuck at "Loading (SD)..." in the bootloader. Is there a specific way that CM10.1 has to be upgraded or did something just go wrong during the flash? With my other devices, you can just flash the upgrade zip from the recovery menu. Thanks in advance for the help!
and finglha
bradleyrogers89 said:
Hello, I'm not particularly new to Android, nor am I new to the prospect of flashing roms. However, I recently flashed an upgrade of cm10.1 to my Nook HD via recovery and I'm now stuck at "Loading (SD)..." in the bootloader. Is there a specific way that CM10.1 has to be upgraded or did something just go wrong during the flash? With my other devices, you can just flash the upgrade zip from the recovery menu. Thanks in advance for the help!
Click to expand...
Click to collapse
Up until the most recent .zip, I have done just what you described. Couple times my HD god hung up during that same process... I just powered down and restarted and it booted fine.
lossofsilence said:
Up until the most recent .zip, I have done just what you described. Couple times my HD god hung up during that same process... I just powered down and restarted and it booted fine.
Click to expand...
Click to collapse
Yea it has happened to me too, I just powered off with a long press on the 'N' and power button. Restarted and it worked fine.
Actually i'm on 10.1 too.
This thing happens sometime. This is normal for early alfa soft.
On first clean install test i had 3 or more times stop on Cyanogen logo. But it started work on fourth time. Same happened with second clean install too (messed Adnroid to death with my hard tests and modifications ). Power OFF/On have sometime magical power.
Well, I was able to restart the nook and flashed the zip again. It worked! However, I can't change the brightness. To be honest, I can't remember if I even tried before. So, is this just a bug or is it common? Thanks for the help guys
bradleyrogers89 said:
Well, I was able to restart the nook and flashed the zip again. It worked! However, I can't change the brightness. To be honest, I can't remember if I even tried before. So, is this just a bug or is it common? Thanks for the help guys
Click to expand...
Click to collapse
I have no problem adjusting brightness on 1/28
codya321 said:
I have no problem adjusting brightness on 1/28
Click to expand...
Click to collapse
It's weird. I couldn't get it to work without using the Tablet UI. Once I switched, it started working. Oh well, it's working fine now. Thanks for the help, you guys are the best.
CM 10.1 needs some time for settle. Then it works wthout lag
Sent from my GT-I9100 using Tapatalk 2
Hey Guys!
I recently upgraded from the latest CM9 Nightly to Jscullins 4.1.2 using clockwordmod....i also upgraded my GAPPS....
Whenever i boot up to CM10...it works fine for a minute and then freezes. The only way i can get it out of the freeze is by doing a Hard restart..
When I say "Freeze" i mean the touchscreen stops working...of it just freezes.
How do I fix this??!! Please Help!!
Thanks!
kmanleafs said:
Hey Guys!
I recently upgraded from the latest CM9 Nightly to Jscullins 4.1.2 using clockwordmod....i also upgraded my GAPPS....
Whenever i boot up to CM10...it works fine for a minute and then freezes. The only way i can get it out of the freeze is by doing a Hard restart..
When I say "Freeze" i mean the touchscreen stops working...of it just freezes.
How do I fix this??!! Please Help!!
Thanks!
Click to expand...
Click to collapse
I don't know if it will work or not, but you can give the attached zip file a try.
chicle_11 said:
I don't know if it will work or not, but you can give the attached zip file a try.
Click to expand...
Click to collapse
Thanks but the title says "4.2.2" and i have 4.1.2...and what exactly is it?
kmanleafs said:
Thanks but the title says "4.2.2" and i have 4.1.2...and what exactly is it?
Click to expand...
Click to collapse
Again, I don't know if it will work for not.
It's a fix for touch sensitivity issues.
Make a backup, just in case.
Edit : cm10 needs more room than CM9. Make a backup, then run acmeuninstaller. Use AcmeInstaller 3 to flash the CM10 rom along with the appropriate gapps. You might as well upgrade your moboot to 0.3.8 and and your cwm to 6.xxx. You can find these files in Goo.im, under developers and Jscullins. For cwm use the 12/15 one.
Once installed you can restore your apps using advanced restore in cwm (you want to restore the data only).
Good luck.
Ok...i noticed that it is actually a HEAVY LAG, rather then a freeze. I was able to go into the "Usage" Panel in settings and noticed that i have 148MB in "System" and around 20GB in 'SD Card". When I tried to exit...it froze and the screen turned off and it wouldn't turn back on...I do NOT want to do a complete restore....
kmanleafs said:
Ok...i noticed that it is actually a HEAVY LAG, rather then a freeze. I was able to go into the "Usage" Panel in settings and noticed that i have 148MB in "System" and around 20GB in 'SD Card". When I tried to exit...it froze and the screen turned off and it wouldn't turn back on...I do NOT want to do a complete restore....
Click to expand...
Click to collapse
Well then, I hope you have a backup.
You do need to use AcmeInstaller 3 to flash cm10, or you will keep running into problems.
Edit:make sure that the battery is fully charged before doing anything.
If the tablet remains unresponsive, you might have to use this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you do, you will have to do a complete restore.
How do i fix this? I'm using stock 20c as my primary and have installed all the necessary files as well as a hexec comp. kernel (optimus prime 2.7) . I tried booting up slimbean 4.3 with iodak v8 but the phone shuts down instead of booting. Also tried slimbean 4.22 with no luck using the patched cm kernel in the multirom thread, iodak, and optimus prime 2.7 cm version but the phone still shuts down after hitting the boot option. Have also tried deleting and reinstalling but no luck. YES, I'VE SEARCHED FOR MY PROBLEM AND LOOKED AT EVERY SINGLE POST IN THAT THREAD AT LEAST TWICE and none of the posts help with my issue, I've seen my problem mentioned a couple of times but the authors somehow fix it without posting why or have a completely different issue. Is there anyway to fix my problem?
juanacevedo said:
How do i fix this? I'm using stock 20c as my primary and have installed all the necessary files as well as a hexec comp. kernel (optimus prime 2.7) . I tried booting up slimbean 4.3 with iodak v8 but the phone shuts down instead of booting. Also tried slimbean 4.22 with no luck using the patched cm kernel in the multirom thread, iodak, and optimus prime 2.7 cm version but the phone still shuts down after hitting the boot option. Have also tried deleting and reinstalling but no luck. YES, I'VE SEARCHED FOR MY PROBLEM AND LOOKED AT EVERY SINGLE POST IN THAT THREAD AT LEAST TWICE and none of the posts help with my issue, I've seen my problem mentioned a couple of times but the authors somehow fix it without posting why or have a completely different issue. Is there anyway to fix my problem?
Click to expand...
Click to collapse
Honestly man I do not think that you really search because I answered this question twice ...
Anyway to boot your second 4.3 ROM, you need either to put your phone on charge and then select Slim OR just after having selected Slim, wait one second and then hold the power button as if you wanted to turn on your phone. These two methods will boot your second ROM.
The last method is easier but longer in time : you need to backup your two ROMs and then invert their position ... I don't think I'm really clear ... In your case you need to have Slim as first ROM and Stock as second.
All your ROMs will then boot normally without any trick
Sent from my LG-P880 using xda premium
juanacevedo said:
How do i fix this? I'm using stock 20c as my primary and have installed all the necessary files as well as a hexec comp. kernel (optimus prime 2.7) . I tried booting up slimbean 4.3 with iodak v8 but the phone shuts down instead of booting. Also tried slimbean 4.22 with no luck using the patched cm kernel in the multirom thread, iodak, and optimus prime 2.7 cm version but the phone still shuts down after hitting the boot option. Have also tried deleting and reinstalling but no luck. YES, I'VE SEARCHED FOR MY PROBLEM AND LOOKED AT EVERY SINGLE POST IN THAT THREAD AT LEAST TWICE and none of the posts help with my issue, I've seen my problem mentioned a couple of times but the authors somehow fix it without posting why or have a completely different issue. Is there anyway to fix my problem?
Click to expand...
Click to collapse
I Got same Problem, but With offial stock 4.1.2 AS secundary. When i Boot it it "shuts down", but i can't Start anything after it. I need To remove akku To get it up again...press power button after multrom Boot works for me...is that normal ? :/
Sent from my LG-P880 using xda app-developers app
The "ectoplasma22" solution worked, I thanked him with the button, but I do it publicly, thank you!
This is my first message, I have yet another 9 to be able to write in the multirom development section, to report this bug, the solution is not elegant, and this problem must be seriously considered.
PS. Of course, respecting the times of the developers and their dedications. Thanks everyone!