I posted this in fascinate forums and haven't been able to get any help, so I figured I would post here as well. I have been running cm7 and installing the nightlies as they come out. When I flashed nightly #9, I lost complete use of my soft keys. Imagine how annoying it is to have to reboot to change screens. I installed a catlog to see if I could figure out what was going on, but I know absolutely nothing about programming. So, this is what I think I figured out. In the bootup, there's no device for "mice", says something about device not found, and then there's another error in system bootup about the"face" error. So I think I have lost something in the system bootup that runs my soft keys.
Does anyone else have issues with their soft keys? Before I lost them totally, my back button would activate all by itself until everything and I mean everything was closed.
I haven't been able to go back to stock to see if that works because I haven't had any computer access since this happened. I will be home tomorrow, so I can see if that helps.
If anyone has any other insight, I'd be really glad to know.
Thanks,
Mona
any solution yet to this my 4 soft keys wont work i dont know wat to do
No resolution for soft key fail
monac66 said:
I posted this in fascinate forums and haven't been able to get any help, so I figured I would post here as well. I have been running cm7 and installing the nightlies as they come out. When I flashed nightly #9, I lost complete use of my soft keys. Imagine how annoying it is to have to reboot to change screens. I installed a catlog to see if I could figure out what was going on, but I know absolutely nothing about programming. So, this is what I think I figured out. In the bootup, there's no device for "mice", says something about device not found, and then there's another error in system bootup about the"face" error. So I think I have lost something in the system bootup that runs my soft keys.
Does anyone else have issues with their soft keys? Before I lost them totally, my back button would activate all by itself until everything and I mean everything was closed.
I haven't been able to go back to stock to see if that works because I haven't had any computer access since this happened. I will be home tomorrow, so I can see if that helps.
If anyone has any other insight, I'd be really glad to know.
Thanks,
Mona
Click to expand...
Click to collapse
I had the same issue when I flashed to Paranoid Android, a jellybean based ROM. Everything worked fine for me with Cyanogenmod 7.2, then I flashed to Android 4.1 and lost the use of the soft keys. I still haven't resolved the issue.
For the record
Charcaroth said:
I had the same issue when I flashed to Paranoid Android, a jellybean based ROM. Everything worked fine for me with Cyanogenmod 7.2, then I flashed to Android 4.1 and lost the use of the soft keys. I still haven't resolved the issue.
Click to expand...
Click to collapse
In case anyone else has this issue, I tried flashing a stock Froyo ROM, a stock Gingerbread ROM, CM 7.2 again, and even stock GB with the latest Verizon Wireless update for GB and the softkey functions never returned. I've managed to put Paranoid Android 2+ back on the Fascinate, a Jellybean ROM, so I can mimic the buttons with onscreen controls, but it eats up a lot of screen real estate. It's a workaround, not a solution by a long shot.
Flashed the Rom, I searched the thread and found nothing, but after flashing and restoring my apps+data my home button stopped working. Not the feedback, just the entire button itself, gone.
Anyone have an idea of how to fix this?
Edit:: Reflashed ROM and it's working now, forgot to do the ATT fix before I rebooted, hopefully I can just reapply it now and it'll be fine >_<
Hey guys,
Been lurking on the site for a while, I've searched all morning for what i need but with no success.
Setup: Att sgh-i777 rooted etc. running JellyBam 5.1
Problem: Power button stopped working, cannot use recovery to backup/flash new software.
Plenty of threads on the button issue, that's not the main question (suggestions welcome though) I just really want to backup before I send it off for repair.
Seems my best course of action is to get a kernel with touch based recovery. I tried downloading mobile Odin to flash a new kernel but it's telling me my phone isn't supported for some reason? I ran the dump file Odin suggested but not sure what to do with that info now. Next best option appears to be to get a .tar of the siyah kernel and flash it with Odin via PC. I just can't find a .tar for that kernel anywhere and I don't have enough posts to ask in the siyah thread.
So, can anyone give me a hand- either with trouble shooting mobile odin, or tracking down a .TAR of the siyah kernel or...any other suggestions?
Edit: Just found this- http://forum.xda-developers.com/showthread.php?t=1644240
I realize this is in the 9100 forum but looks like it simply converts a zip to an odin flashable tar which is what i'm looking for. Anyone have any experience with it?
Thanks in advance for any insight!
You want to do a nandroid backup? Yes just flash the siyah kernel in the development forum with mobile Odin. It does work with our phones.
Phalanx7621 said:
You want to do a nandroid backup? Yes just flash the siyah kernel in the development forum with mobile Odin. It does work with our phones.
Click to expand...
Click to collapse
Odin says "Device not supported, or not detected (check root)" see attached screen. I'm definitely rooted, have superSU1.04, use TI backup frequently etc.
It actually magically started working again last night though. I immediately did a backup but at the end it said "md5 checksum failed". I then ran kernel cleaner, wiped cache, wiped delvik and flashed the newest siyah and tried again and backup was successful and now i'm on touch recovery. Mobile odin still tells me not supported/not detected though- any idea what might cause that? could it be ROM related ?
I'm going to flash back to jellybam 4.1 today and see if that does it.
flet2 said:
Odin says "Device not supported, or not detected (check root)" see attached screen. I'm definitely rooted, have superSU1.04, use TI backup frequently etc.
It actually magically started working again last night though. I immediately did a backup but at the end it said "md5 checksum failed". I then ran kernel cleaner, wiped cache, wiped delvik and flashed the newest siyah and tried again and backup was successful and now i'm on touch recovery. Mobile odin still tells me not supported/not detected though- any idea what might cause that? could it be ROM related ?
I'm going to flash back to jellybam 4.1 today and see if that does it.
Click to expand...
Click to collapse
It possibly can be ROM related (but I am not certain). User AJ's Siyah kernel 7.6.8, it's works well with all the ROMs.
BeenAndroidized said:
It possibly can be ROM related (but I am not certain). User AJ's Siyah kernel 7.6.8, it's works well with all the ROMs.
Click to expand...
Click to collapse
Yup, running 7.6.7 now and enjoying it.. My power button is currently working again but i turned on 'swipe to wake' in Stweaks so when it fails again, at least i'll still have a working phone. the volume wake from AOKP settings doesn't work when the phone is in deep sleep so pretty useless. As long as i stay on Siyah kernel i guess i'll be able to limp along until i get the button fixed.
The Odin thing is still strange though, will have to try another ROM and see if it recognizes my phone then. Tried Jellybam 4.1 but kept getting reboots even with full wipe- tried flashing it twice. Maybe i got a bad download, i'll try again tonight.
flet2 said:
Yup, running 7.6.7 now and enjoying it.. My power button is currently working again but i turned on 'swipe to wake' in Stweaks so when it fails again, at least i'll still have a working phone. the volume wake from AOKP settings doesn't work when the phone is in deep sleep so pretty useless. As long as i stay on Siyah kernel i guess i'll be able to limp along until i get the button fixed.
The Odin thing is still strange though, will have to try another ROM and see if it recognizes my phone then. Tried Jellybam 4.1 but kept getting reboots even with full wipe- tried flashing it twice. Maybe i got a bad download, i'll try again tonight.
Click to expand...
Click to collapse
Try 7.6.8, I'm using 7.6.8-S and swipe works perfectly fine on my end.
BeenAndroidized said:
Try 7.6.8, I'm using 7.6.8-S and swipe works perfectly fine on my end.
Click to expand...
Click to collapse
Oh yea the swipe to unlock for siyah works great. I was referring to JellyBam's AOKP settings which offers a volume to wake. Volume wake works when on charger, but won't wake it from deep sleep. Siyah's Swipe wake does both :good:
I would still love to have an odin flashable .tar of siyah though- If anyone has any insight on how to get that (or make it from the .zip) that would be awesome. I used the tool from the thread linked in the OP and it did turn the kernal zip into a .tar but i don't dare flash it to test...
flet2 said:
Odin says "Device not supported, or not detected (check root)" see attached screen. I'm definitely rooted, have superSU1.04, use TI backup frequently etc.
It actually magically started working again last night though. I immediately did a backup but at the end it said "md5 checksum failed". I then ran kernel cleaner, wiped cache, wiped delvik and flashed the newest siyah and tried again and backup was successful and now i'm on touch recovery. Mobile odin still tells me not supported/not detected though- any idea what might cause that? could it be ROM related ?
I'm going to flash back to jellybam 4.1 today and see if that does it.
Click to expand...
Click to collapse
Read somewhere that jellybam 5.1.0 places the wrong phone info in the rom. It show up as i777 instead of sgh-i777 and this might be causing Mobile odin to fail on the compatibility test.
To turn your volume up button into a power button edit the /system/usr/keylayout/gpio-keys.kl file to read:
key 115 POWER WAKE
key 114 VOLUME_DOWNWAKE
key 102 HOME WAKE
key 107 ENDCALL
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 103 DPAD_UP
key 108 DPAD_DOWN
key 232 DPAD_CENTER
key 116 POWER WAKE
key 212 CAMERA WAKE
key 115 is the volume up button. This only works in the fully booted os. Doesn't work in recovery.
Sent from my Apple IIe
Quicksilver13 said:
Read somewhere that jellybam 5.1.0 places the wrong phone info in the rom. It show up as i777 instead of sgh-i777 and this might be causing Mobile odin to fail on the compatibility test.
Click to expand...
Click to collapse
Yup that was exactly it. I notice it when i went back to Jellybam 4.1 and saw the full device name in the 'about'. Hopefully 5.2 drops soon with all the necessary fixes!
billyjed said:
To turn your volume up button into a power button edit the /system/usr/keylayout/gpio-keys.kl file to read:
key 115 POWER WAKE
key 114 VOLUME_DOWNWAKE
key 102 HOME WAKE
key 107 ENDCALL
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 103 DPAD_UP
key 108 DPAD_DOWN
key 232 DPAD_CENTER
key 116 POWER WAKE
key 212 CAMERA WAKE
key 115 is the volume up button. This only works in the fully booted os. Doesn't work in recovery.
Sent from my Apple IIe
Click to expand...
Click to collapse
Thanks for this info. Is there a thread or tutorial somewhere that will explain how to access and edit this file? I assume it's not as simple as just navigating to it and making the changes?
Also, how do i get volume to go up if i turn it into a power button? wouldn't that make my phone lock every time i tried to turn up the volume then?
flet2 said:
Yup that was exactly it. I notice it when i went back to Jellybam 4.1 and saw the full device name in the 'about'. Hopefully 5.2 drops soon with all the necessary fixes!
Thanks for this info. Is there a thread or tutorial somewhere that will explain how to access and edit this file? I assume it's not as simple as just navigating to it and making the changes?
Also, how do i get volume to go up if i turn it into a power button? wouldn't that make my phone lock every time i tried to turn up the volume then?
Click to expand...
Click to collapse
It actually is just as simple as finding the file, mounting the directory as r/w and then editing the file. As far as turning up volume, you would have to turn down volume and then use the on screen volume panel to adjust.
Sent from my Apple IIe
Great thanks. So to mount the directory it appears i need to use ADB, or could i use an app such as Root explorer or something like this? https://play.google.com/store/apps/details?id=com.beansoft.mount_system&hl=en
Can i access the file right from my phone to make the changes once i have the directory mounted correctly?
flet2 said:
Great thanks. So to mount the directory it appears i need to use ADB, or could i use an app such as Root explorer or something like this? https://play.google.com/store/apps/details?id=com.beansoft.mount_system&hl=en
Can i access the file right from my phone to make the changes once i have the directory mounted correctly?
Click to expand...
Click to collapse
I use root explorer on the phone. If you use a rom that has support, you can add a line into your addon.d files to keep from having to manually change it everytime you update your firmware.
Sent from my Apple IIe
Thx for the info, i'll have to test this out. I'll nandroid and back up the original file too just incase!
Let me know how it works out for you.
Sent from my Apple IIe
Hi,
My wife's power button went out on her i777. Backed up the file and changed key 115 to power wake. Rebooted. This made volume up and down both stop working. Changed it back, they both work. Any ideas?
I have it running AOKP with AJK kernel.
Help!
I have a unlocked AT&T Motorola Backflip (I know its old) and have been trying to install Android 2.3.7 CyanogenMod7. I go through making a recovery image and use Superuser to do a Wipe All. I then flash from the SDcard the zipped file. Everything appears to work fine. After the reboot the phone comes up in the Home page where I can see the apps ect. The issue is that when the phone goes to sleep or restarts I am at the initial power up screen ( where you would select phone, home or return). It is at this point that the home button fails to do anything. I get a short vibration indicating that the phone recognizes I have pushed the button but nothing else happens. When I restore the recovery image everything works fine.
It appears that the link between the home button and the location of the home page is missing.
I would really appreciate expert advice on how to proceed.
Thanks
Ram
CyanogenMod 7.1 mapping
Thanks for the information. If I may pose a follow-up. Based on my description, do you think there is different mapping with Android 2.1.1 and Andriod 2.3.7?
Also, is there a way to tell what mapping is being used in Android 2.3.7 or CyanogenMod7?
I appreciate you help.
There are many people here asking on how to fix the low in-call volume bug present in our cyanogenmod and cyanogenmod based roms.
They have been posting everywhere creating useless threads asking for fix or posting in original development threads of the respective roms on how to fix it.
So, here it is:
There are TWO methods to fix it:
1. Press Vol - and then Vol + after picking up the call EVERYTIME.
2. Or, you can simply install the attached file and run it ONCE, it will be activated and everytime you accept a call, it will automatically do the work
PS: I did not create this tweak, somebody else did, I'm just sharing it with you
szzlgupta said:
PS: I did not create this tweak, somebody else did, I'm just sharing it with you
Click to expand...
Click to collapse
I have created this app.
Anyone can take it from here: http://forum.xda-developers.com/showthread.php?p=50965848 where I'll post updates.
P.S. Sajal, manny thanks for sharing this to anothers!
szzlgupta said:
There are many people here asking on how to fix the low in-call volume bug present in our cyanogenmod and cyanogenmod based roms.
They have been posting everywhere creating useless threads asking for fix or posting in original development threads of the respective roms on how to fix it.
So, here it is:
There are TWO methods to fix it:
1. Press Vol - and then Vol + after picking up the call EVERYTIME.
2. Or, you can simply install the attached file and run it ONCE, it will be activated and everytime you accept a call, it will automatically do the work
PS: I did not create this tweak, somebody else did, I'm just sharing it with you
Click to expand...
Click to collapse
That is not the problem,Even at full volume I get half the volume I used to get on my stock rom (sense) (I am using the HTC one m7 running Cyanogenmod)
Does this work on any ROM?
darkandroid13 said:
That is not the problem,Even at full volume I get half the volume I used to get on my stock rom (sense) (I am using the HTC one m7 running Cyanogenmod)
Click to expand...
Click to collapse
I agree