Hi everyone,
I'm wondering if there is a way to quickly control my google home devices from my lock screen without having to enter my phone passcode. My pixel phone is rooted and running Android 11 by the way. If there isn't, could anyone guide me to some good tutorials on how to write a tweak for rooted Android. Sorry if this is not the right place to post.
Thanks in advance.
Related
Hello,
After installing CyanogenMod7 on my Incredible S, I found that the 4 android buttons below the screen no longer rotate when I turn the device sideways. It doesn't worry me because I understand that I put a custom rom on the phone and all.
Although I did find that feature pretty cool and I was wondering if there was a way to get it back, all while keeping the rom?
Thanks!
System92 said:
Hello,
After installing CyanogenMod7 on my Incredible S, I found that the 4 android buttons below the screen no longer rotate when I turn the device sideways. It doesn't worry me because I understand that I put a custom rom on the phone and all.
Although I did find that feature pretty cool and I was wondering if there was a way to get it back, all while keeping the rom?
Thanks!
Click to expand...
Click to collapse
This has been previously asked and the response was that this is a HTC Sense feature and CM7 is not HTC Sense.
Alright, thanks!
Hi is it somehow possible to port those modded Nfc.apks to our stock 4x HD phones?
I tried some of the modded Nfc.apk, but none of them seem to work
NFC is pretty useless when you can't use it while screen is off.
Can anyone help to get nfc working while screen is off?
Evilandi666 said:
Hi is it somehow possible to port those modded Nfc.apks to our stock 4x HD phones?
I tried some of the modded Nfc.apk, but none of them seem to work
NFC is pretty useless when you can't use it while screen is off.
Can anyone help to get nfc working while screen is off?
Click to expand...
Click to collapse
tbh i would prefer NFC not detecting when the screen is off. imagine it going off accidentally in your pocket if so ever happens that your credit card or some other NFC 'device' activates it. the small trouble of unlocking the screen and tapping is worth the other troubles to me.
Not able to use it while screen off - we're not using the phone - is a good way to prevent negligence discharge =D army term =X
L2Deliver said:
tbh i would prefer NFC not detecting when the screen is off. imagine it going off accidentally in your pocket if so ever happens that your credit card or some other NFC 'device' activates it. the small trouble of unlocking the screen and tapping is worth the other troubles to me.
Not able to use it while screen off - we're not using the phone - is a good way to prevent negligence discharge =D army term =X
Click to expand...
Click to collapse
NFC is pretty useless without the option to have it always on. Google had this integrated, but changed some time ago. Most users try to get back to this state (AOSP, Cyanogen, etc.) or to let the user decide what he wants (off, activated when unlocked, activated when display on (and locked), activated when display off).
Why always on: It would be very nice to activate/deactivate things when you put your phone on your table etc without the need to unlock the phone first (then you can also push a button, so no need for nfc).
Although we have no useful NFC applications here (no payment for example), I don't think that always on is a security problem. You need to get really close to transfer something, so this shouldn't be a real security problem.
hi I have the same issue. NFC makes no sense when you have to unlock the screen first.
I have found this for the HTC One X.
http://forum.xda-developers.com/showthread.php?t=1713354
Could this work on the 4X ?
I had a shot
This issue really irritates me, so yesterday afternoon I decided to run head on at a big learning curve and have a shot at decompiling/editing/recompiling the nfc apk myself.. I flashed my edited apk, turned of the screen scanned a tag and it worked! ..Assuming it worked I left it alone..
This morning I realised that my edit only work for 15 seconds after turning on the screen :/ LG have added their own edits on top of the android source, and honestly Im not even sure what for.. Something in that code is contradicting with the android code and I can't really afford to waste more time on it atm!!
I'm attaching my half working APK file if anyone fancies playing with it.. The key value to play with is POLLING_MODE: a value of 0x1 means NFC should work with the screen off and locked; a value of 0x2 means the screen must be on but can be locked; and 0x3 means NFC will only work with the screen on and unlocked. I also made some minor edits elsewhere.
Anyways, sorry about the long post! Just trying to give people hope, as this is most definitely do-able, and probably not too difficult either.. But not by me as I really can't be doing with getting my head around smali when I am supposed to be doing other things
Note:-
Attached file is intended for firmware v10f, just push the file to /system/app/Nfc.apk using abd.
If you can work out what changes about 15 seconds after the screen is turned off, I would love to hear it.
MAKE SURE YOU BACKUP YOUR ORIGINAL Nfc.apk BEFORE PUSHING THIS
G405T said:
This issue really irritates me, so yesterday afternoon I decided to run head on at a big learning curve and have a shot at decompiling/editing/recompiling the nfc apk myself.. I flashed my edited apk, turned of the screen scanned a tag and it worked! ..Assuming it worked I left it alone..
This morning I realised that my edit only work for 15 seconds after turning on the screen :/ LG have added their own edits on top of the android source, and honestly Im not even sure what for.. Something in that code is contradicting with the android code and I can't really afford to waste more time on it atm!!
I'm attaching my half working APK file if anyone fancies playing with it.. The key value to play with is POLLING_MODE: a value of 0x1 means NFC should work with the screen off and locked; a value of 0x2 means the screen must be on but can be locked; and 0x3 means NFC will only work with the screen on and unlocked. I also made some minor edits elsewhere.
Anyways, sorry about the long post! Just trying to give people hope, as this is most definitely do-able, and probably not too difficult either.. But not by me as I really can't be doing with getting my head around smali when I am supposed to be doing other things
Note:-
Attached file is intended for firmware v10f, just push the file to /system/app/Nfc.apk using abd.
If you can work out what changes about 15 seconds after the screen is turned off, I would love to hear it.
MAKE SURE YOU BACKUP YOUR ORIGINAL Nfc.apk BEFORE PUSHING THIS
Click to expand...
Click to collapse
You have to rename nfc.odex (nfc.odex.org or what you want), if you don't do this the code will be replaced with the one in the odex file after reboot.
There also an other thing with the deep sleep mode which starts after a few seconds (15-30s) . In deep sleep mode nfc is not working until the phone is waked up.
But except that your modification ist quite useful. Nfc is starting immediately after the screen is turned on and this is much better than the default behavior.
NFCMod
So. Which ROMs are you using??? Isn't anybody using a signature here?
If I get a fast answer I would try to make it with my usual method but you have to test then.
StephanSch said:
So. Which ROMs are you using??? Isn't anybody using a signature here?
If I get a fast answer I would try to make it with my usual method but you have to test then.
Click to expand...
Click to collapse
At the time of the last post on this thread we had no custom ROMs as there was no way to unlock the bootloader.
SimonTS said:
At the time of the last post on this thread we had no custom ROMs as there was no way to unlock the bootloader.
Click to expand...
Click to collapse
and now?
StephanSch said:
and now?
Click to expand...
Click to collapse
We have an unlockable bootloader. We have various ROMs based around Cyanogen 10.1 but with a couple of AOSP variants appearing over the last few days as well.
With the slim bean ROM it work.
LG 4X HD - Better than a Smartphone
Ok. Then I've nothing to do.
Sent from my HTC One using xda premium
hi.
My Galaxy S1 screen just broke completely today, both LCD and digitizer, so I don't see anything and the phone doesn't respond to touch.
I'm actually using the phone as a security camera, and since it is configured to auto start on boot, I am fine. But I still would like a way to control the phone, maybe something like teamviewer... The problem is, I cannot install anything since I can't control the phone right now. Is there a way to do that? Maybe using some ADB commands? The phone is rooted and running CM 11.
Thanks.
yes you can
romitkin said:
hi.
My Galaxy S1 screen just broke completely today, both LCD and digitizer, so I don't see anything and the phone doesn't respond to touch.
I'm actually using the phone as a security camera, and since it is configured to auto start on boot, I am fine. But I still would like a way to control the phone, maybe something like teamviewer... The problem is, I cannot install anything since I can't control the phone right now. Is there a way to do that? Maybe using some ADB commands? The phone is rooted and running CM 11.
Thanks.
Click to expand...
Click to collapse
https://github.com/yangh/sevensquare i use this
you can also install debian in chroot
debiankit -- google it
midhato said:
https://github.com/yangh/sevensquare i use this
you can also install debian in chroot
debiankit -- google it
Click to expand...
Click to collapse
You can install a kernel which supports USB Host functionality.
Hi,
I wanted to ask if any of you are using android encryption ?
I was curious so I enabled it but I was super disappointed. I had to use the same password for turning ON my device and to UNLOCK THE SCREEN ! This is ridiculous !
Firstly, anyone can see what I'm typing. Secondly if I use strong complicated password then unlocking my device takes forever.
Using Play Services smart something (don't remember how it was named) helps some but still is crappy job.
Truth is you can either be safe and use encryption while the same time wanted to destroy your phone or you can just have it working faster, be more friendly, use whatever lockscreen method you want.
It's unfriendly, inconvenient, slow, problematic and frustrating.
Hello, I'm a newbie. I've browsed the ROMs topic but since I don't understand nothing I was lost. I would like to put stock android on my Galaxy s10, will someone please link to me a guide + stock android ROM? (If what I said made any sense) trying to flee programmed obsolescence. Thank you!
I'm confused - your title says you want to root, but then your post says you want stock. And then you say you're trying to "flee programmed obsolescence:". Can you be more specific about what you are trying to do?
For stock ROM, you can easily use ODIN to do that. This has nothing to do with rooting.
Rooting can be done on some devices, not others. We'd need to know which exact model you have (eg my S10+ is an SM-G975U1)...
schwinn8 said:
I'm confused (...)
Click to expand...
Click to collapse
I meant I wanted to use pure Android, no UI on top of it. I want to root because I've heard it can improve battery life and camera quality. I noticed my phone's screen wakes up randomly no notifications since I bought it, I'm suspicious this is an artifact to decrease the life span of the device. Also there is a carrier app I can't delete which sends notifications that wake up my phone and don't turn the screen off after, no matter my settings, this app I can't delete nor customize notification settings on. This also degrades battery life a lot as it not only wakes up the screen, but puts the whole phone to function and can be there woken for hours if I don't see it, it's really annoying. So I'd like to get rid of that and run pure Android. Galaxy S10 SM-G973F. Thank you for reaching.
Since you're on Exynos, I am not directly familiar with the process (I am in the USA and have a Snapdragon phone, which means we can't root as easily).
This thread seem to have info, and the second post seems quite detailed and clear: https://forum.xda-developers.com/t/...device-and-get-it-right-tipps-tricks.4015813/
If you have further questions about the process, you may want to ask on that thread.