I have been on Beans 22 (as well as previous revisions) for quite some time without issue with disabling the home button using the standard gpio-keys.kl edit; completely removing "HOME" & "WAKE" as well as removing "HOME" and changing "WAKE" to "WAKE_DROPPED". I tried this first on Sophisticated v1.5 and found that with this file edited, my wifi would not start. v2.0 came out today so I figured I would do a clean install and try it again. With nothing else on the phone, my wifi works great until I edit this file. Once the file is edited and the phone rebooted, the wifi fails to start. It will show the icon as dimmed and just stick there. If trying to do it through settings, you can move it to 'ON' and it will go right back to 'OFF'.
Could someone else that is using this ROM confirm this or possibly shed some light on what might be going on?
I have been rooting and ROM'ing my phones since my old DroidX and have never had a reason to post before because I have always found help through searching. I have yet to find this specific problem though and do realize that it would be more appropriate to post in the developer thread, but since this is my first post on this forums, I cannot.
Thanks in advance!
Well... I did another fresh install, wiping everything except the external card before installing and wiping cache/davlik a few times after. This time, removing "HOME" & "WAKE" causes the same symptoms, but removing just "HOME" and changing "WAKE" to "WAKE_DROPPED" allows for normal operation. I am still not sure why this change would have anything to do with the WiFi, but it seems to be working properly now.
Updated to SR_KK_v1...
Having been on several different 4.3 based roms for quite a while, the information posted in the post immediately proceeding this worked great.
Last night I created a full backup and flashed SR KitKat v1. I have tried all of the combinations listed above and in other threads on the subject with zero impact on the operation of the home button. The changes had no affect on anything else for that matter (previously I had experienced wifi problems after modification).
I really need the home button disabled as I carry the phone in my pocket and with the home button able to wake the phone, it will do all sorts of weird things in my pocket.
This thread has been just me talking to myself so far, but I would greatly appreciate any help that the kind members of this forum can lend!
I work outside in the heat/humidity/dirt/mud and the safest location for my phone is in my pocket. Without the home wake disabled, the phone will unlock and things will happen. It has been a problem in the past for me. If it isn't for you, good, I'm glad, but stating so does not change my current situation.
Related
ive seen this discussed somewhere else, maybe it was ppcgeeks, but the problem is, i lose text messages when i soft reset.
i dont have much information about it, but if i soft reset soonafter a soft reset, or even an hour or so after a string of text messages, they will sometimes just not be there any more.
anyone have any idea why this is happening, or more importantly how to fix it?
thanks
i would really like some info on this. i cant offer any help other than verifying that it happens to me too. i think it has happened with both sms and mms too actually. i dont like it though
The only way I've been able to save my SMS when I reset is by holding the button to power the phone off rather than using the stylus to reset. Every time I use the reset button I lose info. Power the phone down, then turn it back on. Should help.
Sounds alot like a cache issue.... Sometimes things get put into mem cache and will be saved later when enough has been stored.... I do not know how to adjust it tho.... I'd say that between the 3 of you, there is a common program that you have installed that may be changing the way your messages are stored.... just a theory on my part, cuz I don't have that issue....
Perhaps 1 of you can flash the ROM from the 3.2.0 post and install nothing but your carrier and then send a bunch of SMS messages. Then do a soft reset to see if they stay....!
are you running a cooked rom?
i recall having this on pre 6.1 roms, though you will always risk data loss if you suddenly soft reset your device with the reset button instead of powering it down properly
i have used the same apps on my phone for a while and only started noticing this messaging issue recently. the more i think about it i think it might have started once i started using 6.1 roms. before that i was just on alltels updated stock rom and this didnt happen. but on both no2chems 5069k and now dcd's 3.2 it happens.
so..maybe its a 6.1 issue? maybe a 6.1 cache issue? all of these 6.1 roms we are using are going to have bugs so this is what im guessing.
just read the post directly above mine...... so maybe im wrong.
anyone else offer any suggestions?
This is definitely a cache issue I discovered some time ago, I think even with 6.0. If you use the reset button or pull the battery within an hour or less of doing text messaging you have to shut down Outlook/SMS first so that it will write the cache to the database.
I'm on Verizon.. This has happened to me even with the stock ROM. Not only do new text messages disappear, but if you delete all your text messages.. then reset.. they are all back.
It does appear to be a cache issue. It takes some time before changes are permanent I guess.
This happened to me on Stock with original Arcsoft, Also on DCD ROM 3.1.2, 3.1.6, 3.2.0.. with various Arcsoft versions 5.xx.
I have found no way to change this.. but I haven't checked all the reg keys for a setting that might do this. If I discover one, I'll post back.
Well, today my girlfriend found out that she can play Words with Friends on her Samsung Fascinate. Only, she had AdFree for Android installed, and it was causing numerous errors. So she did what any person of average intelligence would do: She googled an answer.
http://neallambert.com/?p=5
The gist of the issue is, when instructed to make sure her screen matched the screenshot exactly, of course she didn't. She dd'd two extra lines. Since then, she's not been able to search or go home.
When pressing the Search or the Home Softkey, it provides the haptic feedback and blinks the light, but nothing happens.
Also, I installed Galaxy Tuner as a workaround until I discovered a way to fix it (or enlisted the help of those of you here that are far more savvy than myself), and mapping the touch gestures to home and search, the same thing happens. Meaning, when the specified gesture for home is executed, it will provide the haptic feedback, but nothing else happens. So it registers the command, but it is not completed.
If you have any ideas how to fix this, or can just point me in the right direction, it would be greatly appreciated. Thanks in advance for your help!
Flash THIS FILE via CWM and it should reset melfastouchkey settings.
good day.
Hey Chopper, Thanks for the response. I did flash the download, but it was still exhibiting the same symptoms. In the end, I just did a wipe/reinstall.
Hey y'all,
So I have Unnamed installed (currently v2.2.1), and have for a while. Every once and a while, hitting the power button (to wake up or sleep the phone, for example) will also toggle mute/unmute. Unfortunately, I am unable to replicate it consistently. It has persisted through upgrades of Unnamed. I have been using Unnamed since v1.0. Does anyone have any insight? I have searched for an answer but found nothing.
I have tried a few things on my own before posting:
Trying to make sure I'm not hitting another button
Full Wipe and reflash (With and without replacing data)
I have not tried:
Another ROM or back to stock to see if behavior continues
BTW: Long time user of the forum, first time posting. Great community, always helpful! As a fellow developer/techie (not Android) I really appreciate the hard work people put in here!
I hadn't heard of this issue. Perhaps it's a bad download? Or kernel related (if you've done anything with the kernel)?
Simba501 said:
I hadn't heard of this issue. Perhaps it's a bad download? Or kernel related (if you've done anything with the kernel)?
Click to expand...
Click to collapse
Originally. I also messed with the voltages however after experiencing this issue reverted back during reflash.
Just tried to use the camera and it's flashing green and pixilated if that's a word. Tried a reboot and it's still the same. Switching to front camera is fine. Also tried different power modes and doesn't change.
Haven't screwed around with any settings so I don't think that's it. Was working the other day so I guess I'll have to back track to see if there's anything I've done other than the ATP Tweak.
Just thought I'd share this in case it has happened to someone else and can help. Thx
Edit: Now I've lost the app completely. Just won't turn on or do anything. After that happening I tried force close and wipe data and it did nothing to help. This is kinda strange. I've uninstalled recent apps and things and rebooted again and still no go. Any help would be appreciated.
Edit: Sorry for the duplicate thread. Just saw similar thread. Mod's, please remove if you like.
I'm having issues with my calls ever since I changed my S3 configuration (ROM, kernel, apps, framework…).
On most of them, I get a soft reboot at the start or in the middle of the conversation.
I've tried changing the modem but there were no results.
How can I diagnose the problem?
Thanks.
P.D: You can see my config on my signature
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
eXtremeDevil said:
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
Click to expand...
Click to collapse
If you have overclocked then lower the frequency I had the same issue on another device and doing so resolved it
We'll see if that's the issue. Thanks for the tip, I'll keep you guys informed.
Have you tried changing kernels, it happened to me once from a custom kernel
Well, I'm very happy with my kernel, but if the problem persist I will consider it.
Thanks!
The problem persists. May be that I installed BusyBox from Play Store when I had it already from the ROM & Kernel?
Yeah most likely thats the problem, try flashing your rom again
Sent from my SM-G900F using XDA Free mobile app
I have uninstalled BusyBox, reflashed the ROM and changed the kernel. I'll keep you guys informed.
So far so good, the system was even better (a lot more stable) and no call reboots. But just now I've had the first one. I guess the number of call reboots have decreased (I'm not sure because it is a ramdom thing) and that's good but, again, any way of diagnose the problem?
Thanks!
EDIT
I often lose my APN settings and I had to reboot the device (a soft reboot is valid as well), may that problem be linked to the other?
I've performed a full wipe and started all over again. Let's see if this time everything works well...
Unbelievable. I did every single thing from scratch and the phone was perfect. Today I make my first call after all the mess and configuration and AGAIN, a soft reboot.
I'm 100% out of ideas here. Is there something, ANYTHING I can do to confront the problem? Some kind of log or monitoring action so I can know a litte bit more about this??
Please, I'm REALLY desperate right now…
I've installed the app SIM Card Manager and the phone field was unkwown. I rebooted and my phone showed up correctly. Maybe the app's fault or my SIM is half-broken? Or is it the phone lector?
Tomorrow I'm changing my SIM for a new one and let's see what happens, really out of ideas right now...
I think I found the cause of the problem.
This modification along with the Xposed app StatusbarVolume seems to cause the reboot when I try to change the volume when in a call.
I can't be 100% sure this is the faliure scenario because the bug is a little bit random, but I am 99% sure anyway.
EDIT
Not sure if the cause is the volume unlink, or the Statusbarvolume overlay failing to show up in call if it has never been invoked outside of a call before since the phone startup. May be a mix of the two things.