Hi there. I've been trying to make this module for my personal use all day today.
What I need is for some code to run before the screen turns on, and if I've understood Xposed correctly, it can, among other things, trigger methods/code before or after a native method is called. (might sound weird, apologizing on beforehand)
I have searched like a mad man after the native/stock method that the phone calls when the screen turns on by hitting the home/power button but I just can't find it, and if I'm going to be really honest, I'm not 100% sure on how to go about if I had that information either. I would be eternally grateful for any help I can get.
Thanks!
XDA Visitor said:
Hi there. I've been trying to make this module for my personal use all day today.
What I need is for some code to run before the screen turns on, and if I've understood Xposed correctly, it can, among other things, trigger methods/code before or after a native method is called. (might sound weird, apologizing on beforehand)
I have searched like a mad man after the native/stock method that the phone calls when the screen turns on by hitting the home/power button but I just can't find it, and if I'm going to be really honest, I'm not 100% sure on how to go about if I had that information either. I would be eternally grateful for any help I can get.
Thanks!
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
First, please create an account so you can post in other forums.
Here is the xposed development area:
http://forum.xda-developers.com/xposed
You should find the answers to your question there.
Good luck!
Related
Hey got a weird problem with my Tasker. I had followed the guide posted in the Android forums about creating a text and missed call widget using minimal text as well.
It was all going swell. until seemingly randomly it stopped counting when the phone was locked. I am completely stumped, which is not surprising, as I'm relatively new to this whole thing. As far as I'm aware I haven't changed anything except updating the apps.
Anyway, if anyone has a nice answer I'm happy to let you say it as patronisingly as you want.
Cheers
John
Bump for frustration!
The phones cpu usually gets turned into a low state when it is in standby. Only major events like calls or texts will wake it.
You need a PARTIAL_WAKE_LOCK for your phone to still register widget events or sensors during that time.
It is possible that some one app/widget of yours aquired such a wake lock before, which in return made it possible for your widget to work during that time.
I have made you a small tool that will aquire a wakelock when it is turned on.
Tell me if it helps.
Thanks for your reply. I have tested it with your app and unfortunately it has not worked.
Sent from my Nexus S using Tapatalk
Back up to the top for other suggestions or workarounds.
Use adb logcat from the android sdk to read the log, there might be some hints on whats going on when you lock your phone.
Cheers for your suggestion. I've looked into it, but tbh am struggling a bit. I think I'll leave it, thanks for your ideas though.
hello,
as far i know the battery life on raph is that bad because of the LCD-driver. since nobody knows how to switch the LCD off - and back on again - the LCD is just dimmed - but stays on.
... of course this consumes battery a lot ...
i'd like to help - if i can ?
- i am a developer (but never developed for (xd)android so far)...
- i have a raph
- i have basic (xd)android knowledge
can somebody tell me, where to start ?
what exactly do we need ? the correct hardware registers / arm-code to handle it ?
Wouldn't it make sense to try on WM first - developing arm-code - without win-api of course.
WM has one advantage: i can test faster - since i don't have to reboot to android all the time.
so i need:
- i need to know, what the xdandroid developers already know about this topic - as far i know, they have the code to switch off - but not to switch on.
- i need a quickstart guide how to setup a "xdandroid development environment".
thank you!
Some thoughts
Baal, good look with your try. I'm sure many people will pray for your success -I'm one of them.
I don't have enough time to try to do that, but I spent many hours thinking about the problem. What I'ld do is:
Try to capture all the operations that WM does diring a sleep-on/sleep-off process, specifically registry modifications, internal calls, etc. Also try to save the status before and after, in case they depend on some kind of previous initialization.
I'm not sure if developers didn't get that information or do have it but didn't know how to implement it. Ask in the XDandroid development list.
If you have to do that, maybe you can use some kind of emulator, but probably you'll need to get a system debugger on your phone.
Modify the android module to do the same operations.
Here, both XDandroid Development List or other android developers should help you a lot.
In this part, you'll have to reboot many times...
Good luck! And keep us informed, please.
Well, this is a kernel issue. Unfortunately there's no "how-to" on the kernel sources...
The Getting the Source page is about the system image unfortunately.
Here's the GIT repo for the kernel code.
As for the rest of it, I don't know how to help you. I don't know how they shut the panel down, and as you know, no one actually figured out how to shut the screen back down. Hopefully someone else chimes in about the other information you requested.
Please keep us updated...
Hi, Baal_zebuz
I know it's been a short time since your intentions were declared, but, do you still keep them and you're working on it, or you already abandoned the idea -no matter the reasons, time, difficulty, etc.? Just to keep the hope's flame lighting or switch it off.
Thanks in advance!
Uhm... I use xdandroid in Raph100 and if the chargher is disconnected, the backlight os turning off after few seconds. I've downloaded the last one from xdandroid.com
Maybe I am OT, in this case I apologize
TheXeno said:
Uhm... I use xdandroid in Raph100 and if the chargher is disconnected, the backlight os turning off after few seconds. I've downloaded the last one from xdandroid.com
Maybe I am OT, in this case I apologize
Click to expand...
Click to collapse
Brightness is set to 0 and the backlight is shut off. Unfortunately the panel itself is still drawing power, and sucking battery life. No one has sorted out the proper kernel code to deinit/reinit the panel.
Hey there, new to the forums here. I was wondering if any of you guys new a way to have it so that when I wake the device (note 3 running cyanogenmod 11) , it would be ready to put my pattern In rather then having to hit the lock icon right above the home button every time I unlock my phone. I know its possible, because that's how it was before, but I messed with the keyguard. Apk file it might not be like that anymore (even though I did make a backup and restored it so really it didn't make a difference) is there some kinda check box I need to rick somewhere? Any help would be appreciated.
Hi, thank you for using XDA Assist. That kind of defeats the purpose of having a pin or pattern unlock. But if you're on Android 5.x you can use smart lock, settings, security.
You could also try asking your question here,http://forum.xda-developers.com/showthread.php?t=2595464&page=633
Thread closed.
How to disable the HOME button in the Galaxy S6 ?
Don´want my phone to wake up everytime it is in my trousers.
Is there an apk file for it ?
Thanks !
Umm keep it somewhere else?
Your answer really helped ! [emoji35]
Have you found this to actually be an issue? I can't imagine it'd be so big a deal that you'd want to disable the button altogether.
Japultra said:
Have you found this to actually be an issue? I can't imagine it'd be so big a deal that you'd want to disable the button altogether.
Click to expand...
Click to collapse
Exactly
Both of you off topic ! I just ask for a solution ! Thanks anyway ! [emoji12]
prallo said:
Both of you off topic ! I just ask for a solution ! Thanks anyway ! [emoji12]
Click to expand...
Click to collapse
Not off topic at all, actually. My question is very legitimate and I am actually interested to hear your answer.
Japultra said:
Not off topic at all, actually. My question is very legitimate and I am actually interested to hear your answer.
Click to expand...
Click to collapse
Well, depending on the trousers I wear, I have found this to be annoying as well. Tight pockets often click the home button by accident and wake up my phone, then it sometimes also manages to unlock the screen and start all kinds of apps, call someone or whatever. They could use the proximity sensor to detect phone is in a pocket, but they didn't...
schoolsux said:
Well, depending on the trousers I wear, I have found this to be annoying as well. Tight pockets often click the home button by accident and wake up my phone, then it sometimes also manages to unlock the screen and start all kinds of apps, call someone or whatever. They could use the proximity sensor to detect phone is in a pocket, but they didn't...
Click to expand...
Click to collapse
You don't have the fingerprint security on? Have you tried repositioning the phone? Maybe the home button against your body as opposed to against the pocket? Or phone top down vs bottom up, etc? My pants are usually pretty tight as well but I've never noticed this issue myself (not to say that it doesn't happen, just that I've never noticed it).
Since everyone ignored your question the answer is as follows.
Open generic.kl in root explorer (device/system/usr/keylayout)
Find the line "Key 172 HOME" and commet it out by editing it to "# Key 172 HOME"
If you just want to disable home button wake, i have a workaround here:
http://forum.xda-developers.com/galaxy-s6/help/guide-how-to-disable-home-button-wake-s6-t3128348
To everyone else, whats the point of being a smart ass about his question? if you dont know the fix dont post. Dont pick apart his motives for litterally no reason. Android is about CHOICE.
Thoth33 said:
To everyone else, whats the point of being a smart ass about his question? if you dont know the fix dont post. Dont pick apart his motives for litterally no reason. Android is about CHOICE.
Click to expand...
Click to collapse
I have found that many times people ask for a solution to weird problem X but if you ask a bit more problem X is a workaround for problem Y which they figured they couldn't solve, so it's better to try to solve problem Y. That way you really help them.
Very good for google cardboard!
Thoth33 said:
Since everyone ignored your question the answer is as follows.
Open generic.kl in root explorer (device/system/usr/keylayout)
Find the line "Key 172 HOME" and commet it out by editing it to "# Key 172 HOME"
If you just want to disable home button wake, i have a workaround here:
http://forum.xda-developers.com/galaxy-s6/help/guide-how-to-disable-home-button-wake-s6-t3128348
To everyone else, whats the point of being a smart ass about his question? if you dont know the fix dont post. Dont pick apart his motives for litterally no reason. Android is about CHOICE.
Click to expand...
Click to collapse
this happened to me two months ago, i took my phone from my pocket and found out that i only have 40% battery left, the phone sent many many messages, video calls, calls, whatsapp......since then i use the pattern lock...but it's annoying
Thoth33 said:
Since everyone ignored your question the answer is as follows.
Open generic.kl in root explorer (device/system/usr/keylayout)
Find the line "Key 172 HOME" and commet it out by editing it to "# Key 172 HOME"
If you just want to disable home button wake, i have a workaround here:
http://forum.xda-developers.com/galaxy-s6/help/guide-how-to-disable-home-button-wake-s6-t3128348
To everyone else, whats the point of being a smart ass about his question? if you dont know the fix dont post. Dont pick apart his motives for litterally no reason. Android is about CHOICE.
Click to expand...
Click to collapse
do you need root access on your phone to do that? Because I'm getting "java.io.filenotfoundexception:Read-only file system" error
Hello,
I have a Nexus 5 with Marshmallow.
I don't know what I did but now when I get a call, the lock screen opens but no way of answering the call.
Before a green screen would show up with a button on bottom to swipe up to answer. This screen no longer comes up.
Could someone point me in the direction to fixing this?
Thanks
fhutt said:
Hello,
I have a Nexus 5 with Marshmallow.
I don't know what I did but now when I get a call, the lock screen opens but no way of answering the call.
Before a green screen would show up with a button on bottom to swipe up to answer. This screen no longer comes up.
Could someone point me in the direction to fixing this?
Thanks
Click to expand...
Click to collapse
You could enable "Volume up for answering", most devices have this ability. As for the issue I have no idea, But try what I mentioned as a temporary solution.
Thank you for your reply.
I would like to try "Volume up for answering" but don't recall the location of this setting. I have now looked for it and cannot find it.
Could you please point me in the right direction for finding that setting in Marshmallow?
fhutt said:
Thank you for your reply.
I would like to try "Volume up for answering" but don't recall the location of this setting. I have now looked for it and cannot find it.
Could you please point me in the right direction for finding that setting in Marshmallow?
Click to expand...
Click to collapse
That setting is typically found within phone settings if the device has it, Open the phone app and go to its settings and it should hopefully be there as well.
I couldn't find any setting on the phone app I am using (True Phone) so I looked for the stock Google app and had trouble finding it. I wasn't using it so disabled it a few days ago. I looked on Play Store and found it but wanted to update it. I did that.
From that moment the answer screen returned. Now back to where I was.
Great work for making me look for those settings.
Thank you very much. All done.