Someone please please PLEASE tell me if there is a way to tell the captive touchkeys to stay on when the screen backlight is on. I may be in the minority but I can't stand the lights going out while I'm using the phone. Sounds simple but I REALLY hate them going off. There wasnt an issue with the unofficial CM10 alpha 5(?). At one time I had a rom that allowed me to set a timeout in seconds OR to match the backlight. That would be perfect in my mind. It would be great if the keyboard backlights were on any time the keyboard is open (IMO). If I'm in the minority then someone please tell me where I can set it at the OS level for just me. If I can't find a solution then I will have to go back to alpha 5 and stay there.
I have googled everything I can think of. I keep getting pages about a "great" new beature of CM9 that allows you to disable the backlight altogether. Great for some maybe but not me. I bring that up to say that I have tried to find the answer on my own first.
Is your capacitive lights feature unchecked in the advanced settings? I think the majority of people who have used samsung phones don't need the lights, so that's why this feature has been implemated.
Sent from my SPH-D700 using xda app-developers app
It is unchecked. I have no problem with the ability to disable but would love to have the option to have them stay on (JB Default) when the screen is on. I don't like having to guess where the buttons are when it's dark out. It's petty I know but it really does bother me enough to not use the rom If I can't change it.
Please post questions in Q&A
Thread moved
Thanks
FNM
FWIW - I'd like to see this as an option, too. It's an annoyance, but not a show stopper. I'm actually getting pretty good at guessing where the capacitive keys actually are, but sometimes get ticked at fumbling for them.
Al
Bump (he said sheepishly)
Can any of the kernel or ROM devs provide some words of wisdom here? On Epic TW-based ROMs, there's definitely a setting to have the capacitive key backlighting timeout match either the screen timeout or the keyboard lighting timeout (I don't remember which).
Thanks.
Al
arschend said:
Bump (he said sheepishly)
Can any of the kernel or ROM devs provide some words of wisdom here? On Epic TW-based ROMs, there's definitely a setting to have the capacitive key backlighting timeout match either the screen timeout or the keyboard lighting timeout (I don't remember which).
Thanks.
Al
Click to expand...
Click to collapse
This functionality would have to be added to the CM framework. The framework is what controls the 6 second timeout and a configurable timeout setting has not been coded. Anyone is free to work that out and submit it to the CM gerrit system
Sent from my SPH-D700 using xda app-developers app
I am a programmer but don't have the slightest clue where to even begin. To be honest, it's not worth it if I have to work for months to get up to speed to do it myself. I'll have to look at other roms. Sad because I love this rom except for this one thing.
Sent from my SPH-D700 using Tapatalk 2
reiter01 said:
I am a programmer but don't have the slightest clue where to even begin. To be honest, it's not worth it if I have to work for months to get up to speed to do it myself. I'll have to look at other roms. Sad because I love this rom except for this one thing.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Understandable, because that's no easy task. But another alternative is to build your own kernel, and revert this patch which is how I fixed the capacitive lights in the 3.0 kernel. You could effectively break them again. Don't worry, they will still go off when you turn off the screen, they just won't timeout after 6 seconds.
I finally got brave
bbelos said:
Understandable, because that's no easy task. But another alternative is to build your own kernel, and revert this patch which is how I fixed the capacitive lights in the 3.0 kernel. You could effectively break them again. Don't worry, they will still go off when you turn off the screen, they just won't timeout after 6 seconds.
Click to expand...
Click to collapse
A year has passed. Updates have come and gone. I even switched to another phone and back to the Epic4G. Same thing bugged me as always. I took the leap and set up a virtual machine so I could compile CM 10.1. I did a test compile and came out fine. I then made the changes you mentioned (that made more sense once I got used to the built process) and it WORKED!
I now have CM 10.1 fully working with the button backlight staying on as long as the screen backlight. I LOVE IT.
Thank you so much (a year late).
reiter01 said:
I now have CM 10.1 fully working with the button backlight staying on as long as the screen backlight. I LOVE IT.
Click to expand...
Click to collapse
I've had my Epic for a week, running CM 10.1, and this bugs the snot out of me too. Any chance you could PM me a link to your build? :laugh:
Sure
I'll try to figure out where to upload it. Keep in mind I know nothing about coding for Android. It's simply CM 10.1 (newest) for EpicMTD with 2 numbers changed and then compiled. I do like that the ability to control the brightness of the buttons still works. I don't like them super bright but I do want them always on.
Download
Here is a download of the rom I compiled. Use at your own risk.
http://d-h.st/iuU
reiter01 said:
Here is a download of the rom I compiled. Use at your own risk.
http://d-h.st/iuU
Click to expand...
Click to collapse
Understood, and thank you good sir. :highfive:
UPDATE: Loaded, booted, and is running without a hitch. You have solved my one major gripe with CM on my Epic. Thankyouthankyouthankyouthankyou!
Glad I could help someone else. CM10.1 is so near perfect in every way, it was frustrating to have such an annoying "flaw". In the older version of CM they didn't have the ability to adjust the brightness of the buttons so I can understand some people wanting them off or fast timeout. If I ever have some spare time I will try to add this as a feature to the menu but I doubt it will ever happen.
@bbelos
Any way I can get my hands on your most recent 4.4 build source so I can build it with the bug put back in?
reiter01 said:
@bbelos
Any way I can get my hands on your most recent 4.4 build source so I can build it with the bug put back in?
Click to expand...
Click to collapse
Well,
device: https://github.com/cyanogenmod/android_device_samsung_epicmtd/tree/cm-11.0
kernel: https://github.com/cyanogenmod/android_kernel_samsung_epicmtd/tree/cm-11.0
whatever is in here: http://review.cyanogenmod.org/#/q/epicmtd+status:open+branch:cm-11.0,n,z
Patch
bbelos said:
Well,
device: https://github.com/cyanogenmod/android_device_samsung_epicmtd/tree/cm-11.0
kernel: https://github.com/cyanogenmod/android_kernel_samsung_epicmtd/tree/cm-11.0
whatever is in here: http://review.cyanogenmod.org/#/q/epicmtd+status:open+branch:cm-11.0,n,z
Click to expand...
Click to collapse
Thank you very much. I am running your build now but would love to make my 1 edit. Is it possible, without total rebuild or large headache, to make a patch for the one file?
reiter01 said:
Thank you very much. I am running your build now but would love to make my 1 edit. Is it possible, without total rebuild or large headache, to make a patch for the one file?
Click to expand...
Click to collapse
One other thing that might make things easier, go to Settings->Buttons->Backlight, and set the timeout for "Don't turn off" and see if that behaves to your satisfaction.
Sent from my SPH-D700 using xda app-developers app
Awesome
bbelos said:
One other thing that might make things easier, go to Settings->Buttons->Backlight, and set the timeout for "Don't turn off" and see if that behaves to your satisfaction.
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
I installed your cm11 but havent gone through and tweaked it out. Looks like that might do the trick. I have found a couple bugs (to be expected).
1. If on a call and hit home, there is no way to get back to hang up. Have to power off.
2. While on home screen. Hitting the "menu" button at the bottom and choosing "settings" brings up the launcher3 settings. Used to be the android settings...maybe it's a change. Not a deal breaker but I prefer the old way.
Thank you for all your work. I wish there was some way I could help you out.
Related
Nytefire MIUI Gingerbread 1.4.29
-------------------------------------------------------
Hello all, this is my first attempt at a ROM. I usually downloaded option's work and flashed it, but I didn't feel like waiting this time. :] If anyone wants to give it a shot, I've flashed it now on three separate myTouch 4Gs without any problems. Of course, if you run into any problems, brick your device, or otherwise cause some type of calamity in your mobile world - this is no fault of mine.
For a list of changes from the previous build, check the MIUI website.
This ROM contains the latest Desire Z port of MIUI as well as the Langage Pack.
I've also included Faux123's GB kernel 2.5.2-137 LV kernel. If anyone has trouble with the LV kernel, feel free to flash over the SV version immediately after ROM flash. I'm afraid I can't do much bug fixing if there is any to be done - as this is all taken care of by the MIUI team. I've simply ported over their latest build for everyone to enjoy. If there's anything I need to change for the Glacier, let me know. :]
Edit:
I suggest doing wipes as you had been doing previously with Option's MIUI builds.
Thanks,
Nytefire
[] [] [] Download Link [] [] [] []
http://www.megaupload.com/?d=2D8JWQVO [Fixed from previous version, I somehow had botched su.]
Been waiting for this to drop, thanks
wheeeeee more ROM chefs
Variety is the spice of life! Also my "666" thank you mark
Hm.
Uh oh, due to not testing I've botched (and just now noticed) SU in this ROM. I'll post a fix shortly, as soon as I get home to do the edits. Sorry about this everyone, I'll have it fixed as soon as possible for you all.
Thanks for that catch, just getting it installed. I'll wait for that.
Could you also, in the next update, change the phone model to MT4G?
Home now, made the necessary changes and in the process of uploading.
Wireless tether not working anymore
Sent from my T-Mobile myTouch 4G using XDA Premium App
Not sure if this is a miui problem or a port problem, the buttons at the bottom of the device, e.g. home menu back, do not light up. Also, long pressing the genius button does nothing.
kyuza said:
Not sure if this is a miui problem or a port problem, the buttons at the bottom of the device, e.g. home menu back, do not light up. Also, long pressing the genius button does nothing.
Click to expand...
Click to collapse
does your home button work, and does normal pressing your search button work?
i had this problem before on one of options builds. Just wipe and reflash and you should be set. May take a few tries and retries of wiping and flashing (took me two times) but it fixed the issue
WIFI does not start for me, and third party access for phone calls is not working, even though it is enabled in the Call settings, and Google Voice is set to Always Ask how i want to make a call. Instead of asking if i want to make a call with my Google Voice number, it uses the real cell phone number.
I've tried wipeing and reflashing 4 times. Each time, the translation pack never installed. The buttons still didn't light up, and the genius button did nothing. I flashed on top of a fresh install, and the translation worked. However, the buttons still don't light up, and the genius button doesn't do anything. Also, can't change the brightness in the drop down menu or in settings. The slider/auto brightness does nothing.
To answer VibrantOwnr, the home button does work as it should, just doesn't light up.
kyuza said:
I've tried wipeing and reflashing 4 times. Each time, the translation pack never installed. The buttons still didn't light up, and the genius button did nothing. I flashed on top of a fresh install, and the translation worked. However, the buttons still don't light up, and the genius button doesn't do anything. Also, can't change the brightness in the drop down menu or in settings. The slider/auto brightness does nothing.
To answer VibrantOwnr, the home button does work as it should, just doesn't light up.
Click to expand...
Click to collapse
Um the genius button remap to search is pretty easy you need to go to the system/ usr/ key layout edit the glacier
keys
key 102 HOME
key 139 MENU
key 158 BACK
key 231 CALL
key 211 FOCUS
key 212 CAMERA
key 217 SEARCH
key 183 SEARCH
key 107 ENDCALL WAKE_DROPPED
key 116 POWER WAKE_DROPPED
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
I'm on cm7 but it should be roughly the same
Sent from my HTC Glacier using XDA Premium App
DarkNytefire said:
I've flashed it now on three separate myTouch 4Gs without any problems. Of course, if you run into any problems, brick your device, or otherwise cause some type of calamity in your mobile world - this is no fault of mine.
Click to expand...
Click to collapse
Not for nothing, i'm not sure what kind of testing you did, but this port is incomplete. I understand that this is your frist attempt @ porting a rom, but maybe you should do a little more research before hand.. I'm not trying to be a d*ck here, but this shouldnt of been released to general public. anyone who flashes this rom is essentially flashing a rom for the vision with a modified build.prop.. I would say use this @ your own risk, but dont be surprised when things r broken...
The key lay out is vision you need to add the files from the glacier. I haven't flashed this rom yet but use options rom as a base for your Rom. Since it for the glacier. A lot of the system files are visions.
Sent from my HTC Glacier using XDA Premium App
Killbynature said:
The key lay out is vision you need to add the files from the glacier. I haven't flashed this rom yet but use options rom as a base for your Rom. Since it for the glacier. A lot of the system files are visions.
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
he is missing the correct files from and not limited to:
/system/usr/keychars
/system/usr/keylayout
/system/lib/hw
/system/etc/firmware
not to mention a total unorthodox way to create/flash a rom???
Hey, don't blame him, he's trying. I'm even thinking of creating a crazily modified version of Cyanogenmod 7. He may not be great, but a least he's making an effort.
But as said before... Warning: ROM may have minimal to serious problems.
This is a message to the op next time you decide to make a rom share with friends people that will appreciate your effort not xda this community is very self centered most of time its either there way or no way the devs are great just the public always has something to say
No one is blaming him for anything he made an incomplete port it not that big of a deal but since true s off. We can literally flash any rom. He didn't change any files in this Rom except for a few. All the files are a vision files almost. We don't mean for him to take it. As bad advice. If he would of had a vision radio we would have bricks going back and forth. Then every one would be blaming him.
Sent from my HTC Glacier using XDA Premium App
GazaIan said:
Hey, don't blame him, he's trying. I'm even thinking of creating a crazily modified version of Cyanogenmod 7. He may not be great, but a least he's making an effort.
But as said before... Warning: ROM may have minimal to serious problems.
Click to expand...
Click to collapse
Don't blame him? I don't even understand what that means? There is no blame only telling how it is.. The port is incomplete and i do believe that anyone that is thinking of flashing this ROM would like to know that information, i know i would... I even went a step further and specified folder locations for of the files he need to replace with the correct ones.. So I was helping him out by giving him a little advice since he didnt want to do the research first...
daprince047 said:
This is a message to the op next time you decide to make a rom share with friends people that will appreciate your effort not xda this community is very self centered most of time its either there way or no way the devs are great just the public always has something to say
Click to expand...
Click to collapse
first off punctuation is always nice :] Quite a leap by calling the entire XDA community "self-centered" and i do not believe it was my way or no way, I really think thats an over reaction. Hey i do have to agree with you, the public does always have something to say...
Killbynature said:
No one is blaming him for anything he made an incomplete port it not that big of a deal but since true s off. We can literally flash any rom. He didn't change any files in this Rom except for a few. All the files are a vision files almost. We don't mean for him to take it. As bad advice. If he would of had a vision radio we would have bricks going back and forth. Then every one would be blaming him.
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Thank you! I am glad that someone gets it the main reason the rom boots is thanks to our great friend Faux123
Freedom of speech needs to be revoked, same talk just happened at teampokerface just now, maybe I'm wrong everyone should argue and trash talk and then go out and kill each other this way we can have more English teacher's :-D
Sent from my HTC Glacier using XDA App
Credits goes to st.matt, he gets full credit for the programming. He seemed a little busy, so I thought I'd spread the news so you guys can implement into your builds.
st.matt said:
Also just a run-down of how it works for anyone that is interested:
I use three different elements to get it working. Firstly, I use a small addition to surfaceflinger to set a system property (sys.orientation.landscape) to 1 when it is in landscape mode (either 90 or 270 degrees rotation) and 0 when it is in portrait mode (0 degrees rotation).
When this is set an init service will start depending on the value of sys.orientation.landscape, which in turn starts a script (/system/etc/rotate_lights.sh) which takes the brightness value from the expected led class (ie. if it's changing to landscape it will look at /sys/class/leds/button-backlight-portrait/brightness) and then set this to the new orientation's led class.
The third part is a small modification to the lights lib which also checks that system property when making changes to the button backlight brightness so that it sets it to the correct class.
Click to expand...
Click to collapse
The necessary files/code are on Virtuous' ICS vivo repository: https://github.com/vivo-ICS/android_device_htc_vivo, and you will also need the patched proprietary libsurfaceflinger.so that references to the changes.
Any way to make this backward compatible with cm7.2?
Un1c0de said:
Any way to make this backward compatible with cm7.2?
Click to expand...
Click to collapse
made a CM7.2 kang for you Inc2 users.
All I did was put in the latest commits as of March 03 2012 and added the rotating softkeys. I can't really test it because I don't have an Inc2, so back up your data in case you are not sure if it will work.
You can flash this without wiping if you are on 7.x already.
For the IncS, I know the rotating buttons for them are not perfect. Sometimes you have to toggle the brightness to get it working. Other times it might take a few seconds to rotate instead of immediately. This is because this script was originally written for ICS roms in mind, but it's backwards compatible with GB.
http://www.mediafire.com/?lggqggdx1m4n656
Wow thanks Kaijura. Downloading now, will post back with results
Sent from my Incredible 2 using xda premium
Thanks Kaijura for posting the info, and the CM7 build. Appreciate it a lot
Is this rom dependent? It will only work on cm 7.2? has anyone tried it on miui? Or any other roms?
Sent from my Incredible 2 using xda premium
Ihatepullups said:
Is this rom dependent? It will only work on cm 7.2? has anyone tried it on miui? Or any other roms?
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Will be trying on miui.us shortly.
Never mind its beyond my knowledge and time.
Sent from my Incredible 2 using xda premium
knipp21 said:
Will be trying on miui.us shortly.
Never mind its beyond my knowledge and time.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Ah, that blows would have been cool... Hey if someone points me in the right direction, I'll try: I know how to use adb and the sdk and I'm an experienced ROM'aholic
Sent from my Incredible 2 using xda premium
Awesome. Hopefully I have time tonight to check it out. Thanks
knipp21 said:
Will be trying on miui.us shortly.
Never mind its beyond my knowledge and time.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Ihatepullups said:
Ah, that blows would have been cool... Hey if someone points me in the right direction, I'll try: I know how to use adb and the sdk and I'm an experienced ROM'aholic
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
its different for miui, because we dont build it from source and cant cherry pick commits
miui is more like a sense rom port that uses cm9 or another aosp rom as a "base"
any significant changes have to be done in smali, which is more involved than java source....i k nowwhat has to be changed (or at least part of it) and where for rotating buttons in miui by diffing the builds from aerovan before and after it was implemented but it was a no go on my part...and didnt seem worth the effort to keep pursuing it atm
I tried this yesterday. My phone wouldn't get past the HTC boot screen. I ended up having to pull the battery and reflash my current ROM.
zohner said:
I tried this yesterday. My phone wouldn't get past the HTC boot screen. I ended up having to pull the battery and reflash my current ROM.
Click to expand...
Click to collapse
Hmm, well I guess that didn't work. If you push /system/lib/libsurfaceflinger.so from an earlier working build you should probably be able to boot.
I just copied the file over from the vivo build which seems that it doesn't work with the vivow.
Guess the vivow surfaceflinger is done differently.
kaijura said:
made a CM7.2 kang for you Inc2 users.
All I did was put in the latest commits as of March 03 2012 and added the rotating softkeys. I can't really test it because I don't have an Inc2, so back up your data in case you are not sure if it will work.
You can flash this without wiping if you are on 7.x already.
For the IncS, I know the rotating buttons for them are not perfect. Sometimes you have to toggle the brightness to get it working. Other times it might take a few seconds to rotate instead of immediately. This is because this script was originally written for ICS roms in mind, but it's backwards compatible with GB.
http://www.mediafire.com/?lggqggdx1m4n656
Click to expand...
Click to collapse
Just tried a flash over but didnt work for me. I guess I can always try a wipe and install.
This wouldn't be hard to add to Miui -- as long as they have no weird additions to libsurfaceflinger. You just need the patched liblights, patched libsurfaceflinger (built for CM), script in /system/etc and changes to init.vivo.rc (or init.vivow.rc for Inc2).
Requires no changes to smali or framework.
The other thing is that if someone wants to clean it up and submit it to CM then the MIUI team will pick it up themselves (someone already did this but didn't seem to have to skill / couldn't be bothered to clean it up to their standards and also didn't really submit it correctly).
I would do this but I don't really have the time these days.
Also: I suspect the problem with the lights not working sometimes could be solved just by adding the conditional I have that checks first to see if the brightness is zero to both orientations (in rotate_lights.sh). I will have a quick look at this soon.
just wanted to share a slight modification in the script. When the brightness level is set to the least the leds turn off completely. The attached script makes sure the leds do not turn off completely at this instance. Unzip the file and replace the file in your /etc/ folder. You may want to make a backup of your existing rotate_lights.sh just in case. Ensure the permissions on the file are the same as before after copying.
Just realized that the settings work only the first time when the phone is rotated. I guess I need a better fix. Sorry, remove the attachment as it has undesired issues. Fix No damn good.
Wow. It's been a long time since I made anything useful. Not being able to use NFC with the screen off has always been a pet peeve of mine with my Nexus, so I figured I'd fix it
This is a modified Nfc.apk, which is the system NFC service that runs at boot. It allows you to scan NFC tags either with the screen totally off, or with the screen on but still at the lockscreen. You get to choose which one you want to flash. Just download one of the zips below, and flash it via recovery (tested with ClockworkMod). To restore to stock, just pick the stock version.
The screen off version means you can ALWAYS scan an NFC tag. Don't have to turn the screen on or anything. Just touch the phone to the tag.
The lockscreen version lets you scan a tag whenever the screen is on, but it doesn't have to be unlocked. You can't scan while the screen is off, but you can just touch the power button to get to the lockscreen and then scan. If you have a passcode, no need to unlock your phone to scan a tag.
This has been compiled against CyanogenMod and tested on my own self-built tree based off CyanogenMod source. There is nothing here that should be specific to that ROM.
Devices
Sprint Galaxy Nexus (toroplus)
Fully working on CyanogenMod based ROMs
Fully functional on most AOKP ROMs. Throws random errors on some, but everything still works.
Not functional on some stock ROMs
GSM Galaxy Nexus (maguro)
Fully working on CyanogenMod based ROMs
Fully functional on most AOKP ROMs. Throws random errors on some, but everything still works.
Not functional on some stock ROMs
Verizon Galaxy Nexus (toro)
Untested as far as I know. If you test it let me know
Should be similar to other Galaxy Nexus SKUs
HTC One X
The user StephanSch has created a version for the One X. Get it in this post.
Only screen off seems to work, not lockscreen.
Don't know if this is for the Qualcomm S4 based One X or the Tegra 3 base. Not sure about carrier versions either.
Samsung Galaxy SIII
The user mayhemer has created a version for the SIII. Get it in this post.
I'm not aware of which version of the SIII this is for, now which ROM. As soon as I have info, I'll update it here.
Nexus S
Reported working from at least one user. Don't know GSM or CDMA version, nor which ROM.
Probably working on any CM9 build for either SKU, and possibly stock or AOKP.
It probably will not work on any manufacturer based skins on any other device.
If you try it on any other device, please let me know how it goes! I'll update the OP with your results!
Also of note, I do not know if this will allow you to use Wallet any differently than you can right now. I don't have any way to test it, and don't personally use Wallet. If you do, let me know whether it works or not so I can update this post!
Liability Disclaimer: As always, I hereby absolve myself of responsibility for any damage you cause to your phone by flashing this. There is inherent risk in modding your device, and by flashing anything in this thread you are taking that risk into your own hands. If something goes wrong, I will try and help, but I am not God.
Source Code Disclaimer: The only code modified here was given under the Apache v2 license. That means that I am not required to release source for this. It is an incredibly simple mod at this point, but I plan on taking it into the next level and creating a patch that makes this an option in settings, rather than a zip you have to flash. I will release source with this, but I want to wait until I clean it up and submit it to the CyanogenMod Gerrit as a full feature, rather than a cheap hack! Sorry if that disappoints anyone, I just wanted to get this out ASAP.
In the meantime, I explain what I'm doing in this post. That should be enough info if you're compiling from source, and might be enough if you are using a Smali edit. If you're critically concerned about it, shoot me a PM or an email and I'll try and help more.
How things stand for Jellybean:
I put this on hold for a while. The further I got into making this a toggleable option in settings, the deeper things ran into the system code. With the big change to Jellybean around the corner, I want to wait until Jellybean becomes the main CM branch so I can avoid the breaks that all the code churn will cause. I'm not done with this, but there's no point in putting the work in to make it fully functional when CM10 is around the corner to break it all. I'll get on it as soon as CM10 becomes closer to release. Before the code freeze for CM10.
In the mean time, @PHtQuE got ahold of me on Twitter and I told him what was happening. I gave him a couple pointers and he got it compiling on Jellybean at the same level it is right now on ICS. I may be wrong, but I believe this is his post right here. Regardless, this is a working screenoff version for JB.
Reserved, just in case...
That will definetly come in good use. Thanks
Sent From My Old Epic 4g via XDA Premium
This is nice! Thanks! One thing that I thought would be useful is to have a notification pull down toggle for NFC. so you think that's possible?
Sent from my Galaxy Nexus using XDA
This is handy thanks dog lol.
Sent from my Galaxy Nexus
Hmmm... I've always been able to use Google wallet with the screen off. I'm not sure about any other nfc use though.
Awesome man, thanks. Just bought some NFC stickers to mess around with and this was my biggest problem. Really appreciate it.
Nice!! So the screen of one is only if the screen is off without a lockscreen?
davidrules7778 said:
Nice!! So the screen of one is only if the screen is off without a lockscreen?
Click to expand...
Click to collapse
No. Sorry, I'll update the OP to be a little more clear.
Screen off means you can ALWAYS scan an NFC tag. Don't have to turn the screen on or anything. Just touch the phone to the tag.
The lockscreen version lets you scan a tag whenever the screen is on, but it doesn't have to be unlocked. You can't scan while the screen is off, but you can just touch the power button to get to the lockscreen and then scan. If you have a passcode, no need to unlock your phone to scan a tag.
pastert33 said:
This is nice! Thanks! One thing that I thought would be useful is to have a notification pull down toggle for NFC. so you think that's possible?
Click to expand...
Click to collapse
It's definitely possible. I'm working on getting the option in Settings now, and should have it working by the end of the day. Once there's an option in Settings, it should be super simple to add a notification bar toggle option as well. Haven't messed with that part before, but it's not too dissimilar from WiFi toggling, so I've got code to look at.
I was hoping to get the settings mod done in time to submit it to CM before they started the code freeze for CM9. Well, they went into code freeze this morning so I missed that. I'll still get it submitted ASAP, but don't expect to see it in the initial CM9 official build unless you use the nightlies. I'll of course update everything once I submit the patch and if it gets accepted.
Geniusdog254 said:
No. Sorry, I'll update the OP to be a little more clear.
Screen off means you can ALWAYS scan an NFC tag. Don't have to turn the screen on or anything. Just touch the phone to the tag.
The lockscreen version lets you scan a tag whenever the screen is on, but it doesn't have to be unlocked. You can't scan while the screen is off, but you can just touch the power button to get to the lockscreen and then scan. If you have a passcode, no need to unlock your phone to scan a tag.
It's definitely possible. I'm working on getting the option in Settings now, and should have it working by the end of the day. Once there's an option in Settings, it should be super simple to add a notification bar toggle option as well. Haven't messed with that part before, but it's not too dissimilar from WiFi toggling, so I've got code to look at.
I was hoping to get the settings mod done in time to submit it to CM before they started the code freeze for CM9. Well, they went into code freeze this morning so I missed that. I'll still get it submitted ASAP, but don't expect to see it in the initial CM9 official build unless you use the nightlies. I'll of course update everything once I submit the patch and if it gets accepted.
Click to expand...
Click to collapse
Darn it LOL i would love to have one that works with both
Great work tho, i will probaly get the lockscreen one
Any thoughts as to if this will work on the One X? I'm backing up my stock NFC.apk anyhow and am going to test it, but I thought I'd ask in advance.
agentdr8 said:
Any thoughts as to if this will work on the One X? I'm backing up my stock NFC.apk anyhow and am going to test it, but I thought I'd ask in advance.
Click to expand...
Click to collapse
In theory, it should work on any 4.0.4 base ROM, on any NFC device. No guarantees though
This is just what I've been looking for (FOR AGES) I know that it doesn't come like this from stock, due to the potential security risks, but sod it! Lol, i love it.
Thanks for the fantastic work
Rumble
Sent from my Galaxy Nexus using xda premium
im curious as to the effect on battery life. how noticeable is the difference?
I think that this is a great feature. But I thought that the reason
the NFC only worked with the screen on and phone unlocked was
a security reason. Meaning someone could not just walk up to
you and scan your phone without you knowing. you would have to
have the phone on for anything to work. I think that the settings
idea is great that way if you want to open then you can have it open
if you want it closed then you can keep it like stock. Great work. Worked
good on my GNexus (Sprint).
zcmack said:
im curious as to the effect on battery life. how noticeable is the difference?
Click to expand...
Click to collapse
I can't speak for the battery life, as my phone is plugged in either for tethering or testing code all day. Shouldn't be too noticeable.
Smurph82 said:
I think that this is a great feature. But I thought that the reason
the NFC only worked with the screen on and phone unlocked was
a security reason. Meaning someone could not just walk up to
you and scan your phone without you knowing. you would have to
have the phone on for anything to work. I think that the settings
idea is great that way if you want to open then you can have it open
if you want it closed then you can keep it like stock. Great work. Worked
good on my GNexus (Sprint).
Click to expand...
Click to collapse
Security is exactly the reason it doesn't come like this by default. It's also why I made two versions. If you're worried about security, then flash the lockscreen version and you have to turn the phone on to be able to scan.
Currently, there is no way that I know of to get anything malicious by scanning against someone's will. It doesn't just offer up credit card numbers when you scan it. If you have NFC Task manager on your phone, someone could scan it and make it start an app you have installed or turn off wifi or something mundane like that, but that's about it. Plus they'd have to get within ~5" of your pocket
Geniusdog254 said:
In theory, it should work on any 4.0.4 base ROM, on any NFC device. No guarantees though
Click to expand...
Click to collapse
It would appear that the One X's Nfc.apk has different hardware support. When I flashed your zip, NFC ReTag couldn't detect NFC hardware any more. And the option for NFC disappeared in Settings. Nothing a restore of the original apk couldn't fix, but it's unfortunate it didn't work.
Any chance you'd be willing to share what edits you made? If it's smali, I can probably tweak the One X's apk to be similar.
agentdr8 said:
It would appear that the One X's Nfc.apk has different hardware support. When I flashed your zip, NFC ReTag couldn't detect NFC hardware any more. And the option for NFC disappeared in Settings. Nothing a restore of the original apk couldn't fix, but it's unfortunate it didn't work.
Any chance you'd be willing to share what edits you made? If it's smali, I can probably tweak the One X's apk to be similar.
Click to expand...
Click to collapse
It's actually compiled from source. I've never messed with Smali, so I don't know how useful this will be. The easiest way is to tweak a variable called POLLING_MODE in the NfcService class. There are a couple different settings. 3 is the default, 2 works on lockscreen or unlocked, and 1 works with the screen off, at the lockscreen, or unlocked.
I don't think Smali keeps variable or function names, so that might be of no use at all.. The other method, in a function called applyRouting() there are a couple if/else statements that check if the current state matches POLLING_MODE or not. If you take those out, then it should also work although for some reason that only seems to enable it to the lockscreen level.
You should be able to see a copy of the file here, if that helps.
Geniusdog254 said:
Security is exactly the reason it doesn't come like this by default. It's also why I made two versions. If you're worried about security, then flash the lockscreen version and you have to turn the phone on to be able to scan.
Currently, there is no way that I know of to get anything malicious by scanning against someone's will. It doesn't just offer up credit card numbers when you scan it. If you have NFC Task manager on your phone, someone could scan it and make it start an app you have installed or turn off wifi or something mundane like that, but that's about it. Plus they'd have to get within ~5" of your pocket
Click to expand...
Click to collapse
I did not mean anything by my comment, I think that having to turn the phone
on to use it is a bit much. I like that you have the ability to run it form the lock
screen. I understand that right now you really cannot do much with the NFC,
hacker wise, other than changing settings you are not stealing information by
scanning. But being that NFC is still new(ish) I also feel that all the security
holes have not been discovered. I just wanted people to consider every angle.
I still think that you have created a great feature.
I love what I'm seeing here, well done! Can anyone confirm if this breaks Google Wallet functionality?
So I decided to make the jump from cm10.1 to paranoid android to try out the new pie feature. I finally figure out how to get it enabled and to work, but if I lock the screen and unlock 90% of the time it won't show back up unless I go to settings and then it decides to work again.
I found some info after searching but this does not work either.
HELP! MY PIE WONT SHOW UP AFTER I UNLOCK MY DEVICE, ITS NOT WORKING PROPERLY
Well, i suggest after unlocking the device, give it 2 or 3 seconds then try to use PIE i guarantee 99.9% It will work all the time =)
HELP I CANT USE THE BOTTOM PIE IT NEVER SHOWS UP!!!
Hmmm, as another lad had told me, always swipe up from the notification led place, and give it a good slow (ish) swipe up, and i garuntee 99.8% it will always work.
It doesn't respond to just sliding your finger in one motion. If you make kind of a small L shape where pie should be then it works 100% of the time (at least for me it does) and give it a second to recognize the gesture. Remember your phone is touch screen and you control a lot with just a touch. Make sure you have good performance settings, that will also help load it faster.
Sent from my Galaxy Nexus using xda app-developers app
Try LMT on any ROM till pie matures on paranoid android. It works good.
Sent from my Galaxy Nexus using Tapatalk 2
Literally after I made this thread thought, hmmmm maybe I should try a different kernel then the stocker. Loaded up ak kernel and has not had a issue sense then.
I am trying to figure out how to add 180 degree rotation. I am on the wicked x7.3 Rom. I love the Rom, would like to add this for when I use navigation. I charge the phone when using nav and put the phone in my cup holder. Can't place it the right way due to the charging cord. Anyway, it did work with the xposed firmware,however I was getting SystemUI process. When making and receiving phone calls.
I don't have enough posts to post on the wicked Rom page.
Thanks for your time.
Eric
ejl2002 said:
I am trying to figure out how to add 180 degree rotation. I am on the wicked x7.3 Rom. I love the Rom, would like to add this for when I use navigation. I charge the phone when using nav and put the phone in my cup holder. Can't place it the right way due to the charging cord. Anyway, it did work with the xposed firmware,however I was getting SystemUI process. When making and receiving phone calls.
I don't have enough posts to post on the wicked Rom page.
Thanks for your time.
Eric
Click to expand...
Click to collapse
you can do a bunch of BS posts like saying hi to everyone that's how i got the posts i needed to finally post in the Dev thread and im on 7.2 let me see if i can make this work for you
edit:which Module did you use?
under wanam Xposed, then under system, then under enable all rotation including upside down (about halfway down)
Not sure about wicked, but yea, xposed with wanam does 180. I'm not having any issues though, with running xposed/wanam.
You may want to try Nova launcher? That'll get you a rotating home screen...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Again, it works when I do this, but then the phone calls get messed up. I found some old post with a file to put in the build.prop. it did nothing for me though, nothing changed.
To 180 degree
windowsmgr.support_rotation_180=true;
maybe the code is different with this ROM, I have no idea.
ejl2002 said:
Again, it works when I do this, but then the phone calls get messed up. I found some old post with a file to put in the build.prop. it did nothing for me though, nothing changed.
To 180 degree
windowsmgr.support_rotation_180=true;
maybe the code is different with this ROM, I have no idea.
Click to expand...
Click to collapse
what exactly happens with your phone calls cause i have it working with wanam in xposed and my calling is good
edit: re read your OP does this happen when your phone is upside down? or in every direction?
I am currently using APEX, it also allows home screen rotation, but it only goes to landscape, not 180 degree. I will try to install NOVA later tonight or tomorrow and see. Thanks for the idea!
com.android.systemui or something like that. I can re install and let you know if you need the exact. This is when I hit the dial button or when I receive a call. I can't answer for several seconds until the screen refreshes.
It happens in any direction.
I have to wait 5 min between posts I guess, So my responses are slow, I apologize.
I am leaving work in a few also, so won't be able to respond while driving of course.
I appreciate your time by the way.
Either way, your helping me reach my 10 posts!!! So thank you for that also.
So I went back and unchecked everything I could in Wanan, then checked lock screen rotation and enable rotation, then installed with Xposed. Now all is well. I will do one thing at a time now on and test as I go.
There were several things checked by default I think? So something was corrupting the UI I guess. I will update if something changes, thanks for all the input.
Eric
ejl2002 said:
So I went back and unchecked everything I could in Wanan, then checked lock screen rotation and enable rotation, then installed with Xposed. Now all is well. I will do one thing at a time now on and test as I go.
There were several things checked by default I think? So something was corrupting the UI I guess. I will update if something changes, thanks for all the input.
Eric
Click to expand...
Click to collapse
make sure your module or any other one is up to date this can help
ejl2002 said:
Either way, your helping me reach my 10 posts!!! So thank you for that also.
Click to expand...
Click to collapse
Lol. Then here's another bump. I remember being desperately in need of help and not being able to post. Sucked
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
Lol. Then here's another bump. I remember being desperately in need of help and not being able to post. Sucked
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
so very true sucked so much
I have been bricking and soft bricking for a few years now (only one hard brick thankfully) So this issue is/was very minor. It is nice to have people to help out though, I do really appreciate it! I will keep messing with this and future phones, it is fun to do, and with the community help, I am sure there will always be a fix! Or a new phone!