Related
http://code.google.com/p/vogue-andr... Priority Component Owner Summary#makechanges
things change fast around here. try reading new threads before post useless request to fix an old problem from march
If your going to daddy me at least leave me a toy.
Wow learn to read. The android n00b thread people are still having these issues. Maybe something has changed but I have seen it. I see two categories of haret users those who work (miracles people who usually are using nand and may have some enviromental difference over us regular sdcard-hare ppl)..
If you can fix my issue fix it, but don't tell me its fixed when nothing says that. Albeit a night of going through all the updates on the different builds may produce results no one has done that in that particular thread (2, or 3, which upon someone coming up and saying this easy has ended up giving up) both threads are a bit different. One was supposed to be look how easy it is , with a few nand resistant fools getting every thing but sound. You sir are a troll... !#@@! @!# @#[email protected][email protected]@!
Seriously if you want new people using android put out a haret build that works... Don't make us n00bs flash our customized **** so we can say oh thats broke, i need that...
sorry if my tone was incorrect. let me try again
The link you posted refers to something that is not a problem any more or was due to old hardware, ie the button physically wasnt working.
k_k successfully used haret to test his build when he was working on the gps. that was the beginning of june
are you trying to say that the link is to YOUR problem? i cannot tell from the post of only a link. it looks like reading through this thread that you got past that problem.
if you need help please list your problem with as much detail as possible so i or someone else can help you.
if you are trying to make a case for haret dev, you should post links or quote more recent attempts and problems
Thanks for the news
Cool. I'll search up on that and post to the threads that I've been going to. It's just email never comes across very personable. People who say to read the entire forum get on my nerves or to search when I have is annoying because sometimes they have read it in an area I haven't landed and it like a race run condition due to bad communication. If you see something try to link it, glad I have a user name to search off, but if you can pt a better thread I'll be happy. Either way when I find it, I'll try to boot again maybe in a week or so. I'll be very happy if it does indeed work now, we'll see.. As far as my posting relating to haret, yet you can regain control of your buttons but if you actually read all of the thread you'll see it doesn't get better than that, it then is a sound issue. Either way haret is broken, and my point is that poor user from march is still suffering now, and this time its sound. I suspected that haret became broken due to the development direction towards nand. I.e. whatif system.file is reffed somehow as (NAND0,0):/initrd.gz. I mean droid when from system.img's to partitions so something very generic could lead to both issues esspecially if a user A who can't hear in haret, can hear in a nand install using the same release? See the modules and stuff are going to be the same. I hope your not wasting my time with the k_k bit...
tyler51773 said:
I hope your not wasting my time with the k_k bit...
Click to expand...
Click to collapse
no. he is one exmple of people who have it working. there are others, i just know him off the top of my head.
People who say to read the entire forum get on my nerves or to search when I have is annoying because sometimes they have read it in an area I haven't landed and it like a race run condition due to bad communication.
Click to expand...
Click to collapse
your first post was just as indirect. from that post i had no way of know you have been working on it. the specific link you post was probably not the best choice. with out direction from you i have no reason to go 2 links deep. not until you gave more description did i go into the xda thread where have been trying things.
it then is a sound issue.
Click to expand...
Click to collapse
yes there is still the sound issue. you could have gotten much better response if you had put something in the first post to indicate you specifically want the sound worked on.
sound it is.
its just more like a watch me thread for people who care about haret. i posted a bug on vogue-android.. but the drift it haret is broken. been broken. its bad right now. can we fix it? or is it fixed already. you mentioned K_K do you mean this thread http://forum.xda-developers.com/showthread.php?p=6852911 or do you mean kalt_kafee kernel are they same guy? where you saying dpad was fixed versus just sound. I guess I'm going to try his latest update kernel, unless you've seen a better thread. I've already got to goto bed. Maybe that's why the guy never came back on my own thread cause i sent him to a new kalt kernel hehehe..
sound working
Going through the list now. Thanks for the pointer. I'll will soon venture forward.
I got sound on an old androidinstall of unknown origin. it was freezing and unstable. I did not get sound ironically on VaniljEclair , the second install from the old android I also installed to system.img vs sdcard partition. trying warm
Aqtrans' CM-5.07 - nice and stable
warm eclair rls 1 - fast, worked great for a day then force closes all over
Incubus26Jc's SuperE beta 3 - still slow on kaiser
VaniljEclair 5.0.8 out! (not tested by me)
trying myn's warm donut then will try aqtrans'
you may have beaten the pepsi challenge.
Hey all!
You sure all know blubber's 3-dot-remover Patch..
I use it to remove this annoying bar on the screen's bottom when using a "old"-non -ICS-app with the menu-long-press-home configuration, because I use multitasking a lot, and just want the home fix for the old apps.
However, in blubber's first Aroma-version of the 1.29.xxx.x patch, it worked wonderful, an the NEW ICS MENU BUTTON in the ACTION BAR, which i love a lot, was still there.
Sadly, in the newer version it is gone
As I didn't know that when updating to the patch's new version, I deleted the "old" version..
So, my question is, does anyone know how to get the ICS-MENU back, or does anyone still has the "old" version of the patch and can upload it for me?
That would be really awesome! Thanks.
Code:
Off-Topic:
Why does my question has a small q in the Title? o__O
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?
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
mkanet said:
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
Click to expand...
Click to collapse
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
dwitherell said:
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Click to expand...
Click to collapse
My annoying fix...
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
I forgot to mention that lock screen prevents this bug from happenening. I'm guessing that's why not everyone has complained about the issue.. and why the bug somehow sneaked passed beta testing of 4.1.2. I would think this changed behavior was a new "feature" as horrible as it is, but it looks like it dad unintentional since its not consistent behavior.
I'm hoping that a kind android developer who also can't stand this problem, Kay offer a small script or app for rooted user to patch this problem.
mrtolles said:
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
Click to expand...
Click to collapse
mkanet said:
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
Click to expand...
Click to collapse
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
You did it! Your fix works perfectly! The bug is gone! ...like the bug was never there. My understanding is the fix prevents the phone from stupidly trying to launch the task manager when the screen wakes by the home button. I also donated for you time and effort. Thanks a million.
dwitherell said:
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
Click to expand...
Click to collapse
No, thank you for making me learn how to put an odexed mod together and testing it for me!
So this fix will work for anyone running a stock odexed version of 4.1.2 UVBMB4 - you just need to be rooted, and having a custom recovery would be nice so you could flash it but you could also just copy the files over. That being said - would this be worthwhile to post?
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
mkanet said:
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
Click to expand...
Click to collapse
The flashable zip is just one method to get the files where they need to go. Literally all it does is overwrite the 2 files in /system/framework by moving the 2 files over from the zip - but there are definitely other ways to do such things. Some are more comfortable with this route, others are more comfortable w/ getting /system to be rw and move the files manually.
I'll likely post this at some point in the next few days
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
Glad to hear
Is it possible that my phone isn't affected? If its a 4.1.2 bug, it should be in all phones with same version right?
This is not happening to my phone. Whether I have lock screen activated or not. I'm rooted but running stock ROM and I have Nova launcher installed if thats even important.
It's not all notes.
Sent from my SGH-T889 using xda premium
kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Yes you'll need to be rooted unfortunately - sorry
wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Absolutely. just PM me. Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
kabuk1 said:
...Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
Click to expand...
Click to collapse
^^^ THIS - a thousand times over
Hello:
I have completed an OTA update of my Moto G 2nd Gen, and everything went smoothly, except for a pop-up after restart, giving me 3 options in some "pirate" lingo...
Fine and dandy, except I chose option 3 - "Take me to the deep", or something similar, - and that took me to the change log and release notes.
OK, but now there is an exclamation mark in the notification area, saying "LineageOS Settings", and a phrase "Ye be on the way to Davy Jones' Locker, me hearties".
It's rather funny, of course, but what exactly is this, and how do I get rid of it?
It's really annoying at this point...
Any help would be appreciated.
F3nn3c said:
Hello, I have completed an OTA update of my Moto G 2nd Gen, and everything went smoothly, except for a pop-up after restart, giving me 3 options in some "pirate" lingo...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3458931
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
You might consider re-flashing the previous zip file. No need to wipe anything first. This has worked on the three devices I've tried it with so far. Good Luck.
April fools joke @Ibuprophen you know better. Why do you always post a link to device forum? Like having a bot running for.
Not necessarily a funny joke
kurtn said:
April fools joke @Ibuprophen you know better. Why do you always post a link to device forum? Like having a not running for.
Click to expand...
Click to collapse
Personally, I wouldn't bundle a joke in with a scheduled update, nor would I expect my entire user community to effortlessly know how to remove it. Some jokes are harmless. Others are not. Perhaps I am just one of those people who wants to be able to TRUST the software I am installing (and no, I am not so blind as to assume I always can). Lord knows there are enough malicious types out there messing with enough things as it is. I am sure that, as a joke, no one at LOS was actively trying to be cruel (at least I hope not) but there are 'inside' jokes you can share with your closest associates, and jokes that are meant for global consumption. Most adults who "know better" know the difference between the two, that's all.
nezlek said:
Personally, I wouldn't bundle a joke in with a scheduled update, nor would I expect my entire user community to effortlessly know how to remove it. Some jokes are harmless. Others are not. Perhaps I am just one of those people who wants to be able to TRUST the software I am installing (and no, I am not so blind as to assume I always can). Lord knows there are enough malicious types out there messing with enough things as it is. I am sure that, as a joke, no one at LOS was actively trying to be cruel (at least I hope not) but there are 'inside' jokes you can share with your closest associates, and jokes that are meant for global consumption. Most adults who "know better" know the difference between the two, that's all.
Click to expand...
Click to collapse
Thank you for the suggestion. Well, if it is an April Fools joke, it might be funny, but not being able to clear it from a notification area is actually a nuisance. I truly hope that Lineage will release another build to clear this up - I rely on my phone a lot, and although I am all for having a bit of fun, I certainly prefer a clean, well polished and smoothly running interface, that does not detract me from whatever I am doing at the moment. As a short time fix, I had to delegate Lineage OS system notifications to the bottom of the stack, just to get rid of an exclamation mark...
You are very welcome. We all are supposed to be here to be mutually supportive, after all ANYWAY - if re-flashing the last update, which in my cases left everything else about my devices unaffected, is an unsavory choice, there were some other suggestions about minor build.prop edits, etc.. which I am confident would also do the trick. Last year's LOS 01 April joke was some passive "mascot" animation and the updates after 08 April removed it. I think it is reasonable to expect the same will happen this year, and it looks as if the relevant postings on lineage.org now reflect that (which I do NOT recall seeing there yesterday, but at this point, who cares ?). As for me - I guess I will just avoid installing future LOS updates plus or minus a week from 01 April. If letting the developers blow off some steam by making these sorts of things keeps things moving forward, so be it. Good Luck.
@F3nn3c and Everyone Else...
Please see the following Post that will clarify this April Fools Joke (in a form of Bad Taste) announced by the Official Lineage Team.
https://forum.xda-developers.com/showpost.php?p=76111211&postcount=18
And please don't kill the Messenger... LMAO!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I ran this command and rebooted my device. Worked for me.
"setprop persist.lineage.nofool true"
Hi,
I got the update today, so for an april fool joke it's late, and kinda bad since we cannot remove the notification easily.
Anyone have a suggestion to remove it without root?
I did not root my phone because some app does not work with it root, and I did not wanted to search for 3 days to make them work on root.
As previously mentioned ......
mael976 said:
Hi,
I got the update today, so for an april fool joke it's late, and kinda bad since we cannot remove the notification easily.
Anyone have a suggestion to remove it without root?
I did not root my phone because some app does not work with it root, and I did not wanted to search for 3 days to make them work on root.
Click to expand...
Click to collapse
Without root, the best approach is probably to dirty flash the previous build - don't clear caches, etc.... At least, it worked for the three devices I used that approach on. OR, wait patiently until 08 April. The next set of updates will remove the nonsense if they are true to their "lineage."
Sadly, on a scale of 1 to 10, not very bright. Good Luck.
mael976 said:
Hi,
I got the update today, so for an april fool joke it's late, and kinda bad since we cannot remove the notification easily.
Anyone have a suggestion to remove it without root?
I did not root my phone because some app does not work with it root, and I did not wanted to search for 3 days to make them work on root.
Click to expand...
Click to collapse
You can apply the command in twrp or adb.
Why developers smoking old tyres ???
This is pure, non serious kiddish ****. 1000%.
Like these guys sitting in front of the TV and burning their farts and making bad jokes in some Trumpish slang people outside Trumpistan not understand...
stagefright1003 said:
I ran this command and rebooted my device. Worked for me.
"setprop persist.lineage.nofool true"
Click to expand...
Click to collapse
Where to put that exactly?
F3nn3c said:
Hello:
I have completed an OTA update of my Moto G 2nd Gen, and everything went smoothly, except for a pop-up after restart, giving me 3 options in some "pirate" lingo...
Fine and dandy, except I chose option 3 - "Take me to the deep", or something similar, - and that took me to the change log and release notes.
OK, but now there is an exclamation mark in the notification area, saying "LineageOS Settings", and a phrase "Ye be on the way to Davy Jones' Locker, me hearties".
It's rather funny, of course, but what exactly is this, and how do I get rid of it?
It's really annoying at this point...
Any help would be appreciated.
Click to expand...
Click to collapse
Same problem here...
i'm really annoyed about this stupid notification i cannot remove and keeps pinging....
whichever dev thought this was a good idea, please give them a slap for me!
As mentioned above...
FIX
Reboot to twrp --> advanced --> terminal
setprop persist.lineage.nofool true
phrag said:
i'm really annoyed about this stupid notification i cannot remove and keeps pinging....
whichever dev thought this was a good idea, please give them a slap for me!
As mentioned above...
FIX
Reboot to twrp --> advanced --> terminal
setprop persist.lineage.nofool true
Click to expand...
Click to collapse
Thanks All OK now.
Was very annoying
Bloody stupid thing to do.