Related
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?
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.
Hello people!
I have not long been using AOKP for very long, but i can say overall i love it, i have a few issues though.
I am aware of course it is a unofficial ROM and to expect it to run perfectly would be ridiculous and i was hoping if anybody had experienced anything similar and had any solutions?...
- My headphone jack has 100% stopped working since installing is ROM, i even reinstalled an old backup of MIUIv4 and it was working fine so it defiantly isn't the hardware.
- Black screen notifications, if i received an IM like whatsapp or even a SMS my led would light up and the screen backlight will turn on but its just a black screen?
- Fail to unlock screen first time around, now this doesn't happen all the time, maybe 30-40% of the time, but ill press the unlock button... the backlight will turn on but again its just a black screen, so i have to re-lock and unlock again and it will 100% work the second time... its kind of annoying.
Other than that the ROM works fine for me, i really don't want to lose the JB OS... is there a stable alternative maybe? or hopefully a simple fix.
By the way is based on their latest build.
Thanks!
Moved to Q&A
Please post in the correct section next time
Sent from my Nocturnalized One XL using Forum Runner
the best for me
http://forum.xda-developers.com/showthread.php?t=1982411
the best ROM for me work perfect!!
xmixmaster said:
http://forum.xda-developers.com/showthread.php?t=1982411
the best ROM for me work perfect!!
Click to expand...
Click to collapse
thanks for that man... im gonna read a little more into but it seems like the best choice... will defiantly check it out!
UPDATE: ive given the ROM a go and i must say its a lot more stable than i thought it would be when its a "mishmash" of different ROMs put together.
i still have the headphone jack issue thought, i read a few other forums that people are experiencing using ROMs based on CM10... have you not had this issue?
CSROM & Graviton Support and Discussion Thread
This thread was created in response to a new xda initiative to reduce non-development related posts on development threads.
An added benefit of a thread here is that users with under 10 posts can get some help (and won't have to PM me).
I will maintain just one thread (hopefully this works) for both ROMs and all carriers to help preserve my sanity.
Please be sure to specify which ROM you are using and the carrier.
Below are some examples of common types of posts and where they belong
Q&A and FAQ Thread:
"What kernel gives the best battery life with this ROM?"
"Is Nova launcher compatible with this ROM?"
"The battery life for this ROM is off the chizarts!"
"The battery life for this ROM is total crap!"
"I just flashed this ROM and my GPS doesn't work. :crying:"
Development Thread:
"The new cellular data toggle isn't working (confirmed by another user)?"
"I keep getting FC's from SystemUI. Any thoughts?"
"I selected the green battery icons in Aroma but it installed the blues ones (I checked twice)."
"I just flashed this ROM and it bricked my device! "
"The battery life for this ROM is off the chizarts!
(see attached screenshots from Better Battery Stats)."
"The battery life for this ROM is total crap!
(see attached screenshots from Better Battery Stats)."
**********************************************
There are exceptions to the examples above. If you are using a port and your GPS doesn't work I need to know that.
It will probably take some time for threads like this to evolve, so I am definitely open to feedback.
**********************************************
Frequently Asked Questions
Q: How can I change the lockscreen wallpaper to a pic in my gallery?
A: You must use the Samsung gallery.
Q: Why won't the circle widget work with the TW launcher?
A: The circle widget currently only works with the RAZR M launcher.
Q: The AOSP lockscreen keeps freezing. What's up with that?
A: All lockscreen options must be unchecked when using the AOSP lockscreen.
Q: Why does my phone keep freezing up when I use Light Flow?
A: Light Flow seems to be incompatible with the AOSP lockscreen. I don't recommend using the two together.
Q: Why doesn't Wifi Direct work?
A: I don't know.
Q: Where can I find all the stock apps you removed?
A: The DR App Machine.
Q: My GPS isn't working. Any suggestions?
A: Link1, Link2, Link3, Link4, Link5, Link6.
*****
OK...one more....
2char
Re: [Q&A][FAQ] CSROM and Graviton
Im sure it must suck trying to keep up with 20 different threads.
Sent from my SCH-I535 using Tapatalk 2
Hey guys,
ATT CSROM v1.4 GS3 - Love the ROM so far, once I got a lot of my apps and data restored and a few issues with that worked out.
Kind of a newb to customs roms. This is the first one I have put on my GS3.
As far as I can tell I am using the CS launcher and would like to the change the wallpaper on my lock screen. However when I bring up the selection screen it only give me the option to use the stock wallpapers.
Can I just move an image to the stock location and have it appear? Or is there another option?
gcarterny said:
Im sure it must suck trying to keep up with 20 different threads.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, it get's tough sometimes. That is why guys like you and the other people that test for me are a huge help. You guys make my life a lot easier by helping out on the threads.
It won't be long before I stop supporting the Atrix. I just don't have the time and I don't use the device anymore.
There is also a pretty good chance I will close up shop for my Sprint and T-Mobile ports for this device. There is not much interest for my ROMs in either forum. Probably not a bad thing since that will lighten my workload.
_____________________
I am wondering if this thread would be better in the general section. That way it can be Q&A, FAQ, and general discussion. But, like I said in the OP, this is a new concept to we will have to see how it evolves.
Judman said:
Hey guys,
ATT CSROM v1.4 GS3
Kind of a newb to customs roms. This is the first one I have put on my GS3.
As far as I can tell I am using the CS launcher and would like to the change the wallpaper on my lock screen. However when I bring up the selection screen it only give me the option to use the stock wallpapers.
Can I just move an image to the stock location and have it appear? Or is there another option?
Click to expand...
Click to collapse
If you want to use anything other than a stock wallpaper for the lockscreen you need to have the Samsung gallery installed. The AOSP gallery is not compatible with the lockscreen for pics, or other images on your device.
upndwn4par said:
If you want to use anything other than a stock wallpaper for the lockscreen you need to have the Samsung gallery installed. The AOSP gallery is not compatible with the lockscreen for pics, or other images on your device.
Click to expand...
Click to collapse
Thanks for the answer!
Can more than one galleries coexists? If so, do I just select another one gallery in the Aroma installer and deselect all other options?
Im still kinda fuzzy on the modify/upgrade process within the installer.
Re: [Q&A][FAQ] CSROM and Graviton
Yes they can Co exist. I can't remember how many there are in aroma but you can download as many as you want. I have three not including quickpic
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Just flashed and very much enjoy it. It has the best of both extremes. Thanks for the hard work. Will report after a few battery cycles.
Sent from my SGH-T999 using Tapatalk 2
rawdaddymagraden said:
Just flashed and very much enjoy it. It has the best of both extremes. Thanks for the hard work. Will report after a few battery cycles.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Welcome aboard!
Which Rom did you flash?
upndwn4par said:
Welcome aboard!
Which Rom did you flash?
Click to expand...
Click to collapse
I flashed cs rom and am loving it still battery is doing well.... no hiccups thus far
Sent from my SGH-T999 using Tapatalk 2
It's a great ROM and I used it as a base to mess with flashing different things and learning stuff. Dev and testers always help.
No matter how many others I try I come back haha
hednik said:
It's a great ROM and I used it as a base to mess with flashing different things and learning stuff. Dev and testers always help.
No matter how many others I try I come back haha
Click to expand...
Click to collapse
Yeah I'm learning to port and build from source at the moment so this will stay as my daily driver for sure.
Sent from my SGH-T999 using Tapatalk 2
Just a mention,
I installed Light Flow Lite yesterday and toyed around with it. Long story short it broke the AOSP lock screen. By broke I mean any time I would put my phone into sleep then wake it up and interact with any function of the lock screen it would become unresponsive and reboot (fast reboot I think).
I was finally able to get out of it by bringing the notification window down and getting into settings. Disabled the lock screen and the device was fine. Uninstalled Light Flow and wiped the data with TB, but the lock screen is still broken. Haven't tried the touchwiz lock screen for fear of it being broken too.
Aside from that the batt life is amazing and everything works wonderfully. Even got another gallery installed via Aroma and can change the lock screen wallpaper (not that im using a lock screen right now).
Judman
Based on what I have read on this apps web site it wasn't meant for an aosp rom. That sounds like a matter of app not being compatible with the rom so I would say not the roms fault.
Glad you were able to get things back to normal.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Judman said:
Just a mention,
I installed Light Flow Lite yesterday and toyed around with it. Long story short it broke the AOSP lock screen. By broke I mean any time I would put my phone into sleep then wake it up and interact with any function of the lock screen it would become unresponsive and reboot (fast reboot I think).
I was finally able to get out of it by bringing the notification window down and getting into settings. Disabled the lock screen and the device was fine. Uninstalled Light Flow and wiped the data with TB, but the lock screen is still broken. Haven't tried the touchwiz lock screen for fear of it being broken too.
Aside from that the batt life is amazing and everything works wonderfully. Even got another gallery installed via Aroma and can change the lock screen wallpaper (not that im using a lock screen right now).
Click to expand...
Click to collapse
You are the second or third user that had this happen. I will add a warning to the OP.
If I remember correctly, Light Flow works fine with the stock lockscreen. But you might want to wait until someone that actually uses it chimes in.
oldbbman said:
Judman
Based on what I have read on this apps web site it wasn't meant for an aosp rom. That sounds like a matter of app not being compatible with the rom so I would say not the roms fault.
Glad you were able to get things back to normal.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
upndwn4par said:
You are the second or third user that had this happen. I will add a warning to the OP.
If I remember correctly, Light Flow works fine with the stock lockscreen. But you might want to wait until someone that actually uses it chimes in.
Click to expand...
Click to collapse
Thanks, I couldnt really find anything else that mentioned having that kind of trouble, but it definitely makes sense. And I wasnt blaming it on the ROM, just saying it was a side effect.
Maybe the mention will keep someone else from breaking their lock screen.
Again, thanks for the great rom!!
Judman said:
Thanks, I couldnt really find anything else that mentioned having that kind of trouble, but it definitely makes sense. And I wasnt blaming it on the ROM, just saying it was a side effect.
Maybe the mention will keep someone else from breaking their lock screen.
Again, thanks for the great rom!!
Click to expand...
Click to collapse
Try light manager app in my experience it is more aosp friendly
Sent from my SGH-T999 using Tapatalk 2
With some roms, I have this issue where when I click the recent apps, theres an animation flicker/lag when there shouldn't be one. After a very, very brief moment, it disappears though.
I don't know what could be causing this in one version of the rom, the issue is not there and then in another version, it is present.
I thought this might have been something on my phone that was cleared properly so today I did a clean instal of the rom (after I went back to stock for a few minutes), but it is still there.
Does anyone have insight to how to get rid of this? I *think* that some people have it and others dont
I had this for the longest time, and I'm pretty sure I've tried every fix imaginable. The only thing that works for me is pressing home before pressing recents. If you always press recents from your home screen, and not from within an app, the animation bug never seems to occur.
Sent from my Mahjong Nexus
tritonesub said:
I had this for the longest time, and I'm pretty sure I've tried every fix imaginable. The only thing that works for me is pressing home before pressing recents. If you always press recents from your home screen, and not from within an app, the animation bug never seems to occur.
Sent from my Mahjong Nexus
Click to expand...
Click to collapse
Before, I was able to do a reboot and it would be fixed for a while but now it doesnt go away. And thank you, I'll try pressing home first!
I thought it was my rom so I did a clean flash 3x. It was so tedious
moomingstarz said:
Before, I was able to do a reboot and it would be fixed for a while but now it doesnt go away. And thank you, I'll try pressing home first!
I thought it was my rom so I did a clean flash 3x. It was so tedious
Click to expand...
Click to collapse
Are you on toroplus? It seems most people that get this are toroplus.
Sent from my Mahjong Nexus
tritonesub said:
Are you on toroplus? It seems most people that get this are toroplus.
Sent from my Mahjong Nexus
Click to expand...
Click to collapse
No, I'm on maguro.
Its weird because I used to be able to reboot and it'd get rid of the problem but now I cant.
I actually rooted my brothers phone yesterday and put on the same rom (but he has the nexus 4-mako) and the issue is there as well! I originally thought it was my phone only.
I was on liquid 2.1 stable (and the issue wasn't there) but on 2.1 official it is, and it is on 2.2 official as well.
When I was on xylon, there were versions where it wasnt there and then versions where it is there
I think it might be a feature that all of these roms added (perhaps from one source) but I'm not a developer so this is probably just gibberish!
The roms that I've tried and seen it on is Xylon, Xenon HD and AOKP. The only rom where I consistently never had this issue is CM (M2) but the CM series don't have enough customizations for my taste, unfortunately.
Which rom(s) do you have this issue with?
Carbon,Xylon and Paranoid are ROMs that I know that doesnt have any lag in recents
Godra said:
Carbon,Xylon and Paranoid are ROMs that I know that doesnt have any lag in recents
Click to expand...
Click to collapse
What version on Xylon? I switched roms because xylon (for me) was acting up and I had that issue on the last update I tried (which is 2.3).
I might give carbon or Paranoid a try though! Thanks for the recommendations!!
Also! Does paranoid have 4-row toggles? I have quite a bit of toggles so its much more convenient to have 4 per row then 3 per row!