I was just curious and wanted to try something, if anyone here may help me out. I am recieving an LG spectrum (I know this is a Nexus area) and I was doing some reasearch because I'm not a fan of the slide up to unlock and I found some info on how to get the aosp lock screen going and then it got me to thinking if there may be a way to switch the files for the aosp lockscreen with the ones from the nexus and be able to port it to other devices (like the spectrum,or razr). Don't know if it will work but I have an old phone I can try it on, so if anyone can help me out that would awesome. Thanks
It'll be much easier to get a stock 2.3 lockscreen than it will be to get a 4.0 lockscreen to port back to 2.3 phone.
Probably right but still want to tinker with the idea and if it can even be done
You're better off using a recent build of Cyanogenmod 7, where you will have the stock Gingerbread lock screen as well as the ability to add custom shortcuts and unlock actions. The ICS lock screen doesn't add anything that hasn't already been a part of CM7 for quite some time.
Hey guys, I am well aware that their is a thread with a transparent statusbar/navbar here in the VGnex section already, the problem is that the developer has not updated the code since PA 2.12, I have made requests and so have a couple others but he says that it seems to work fine on the new ones. The OP of the thread says the paranoidandroid version of the transparency mod is 2.18 but the download is the 2.12 and has not been updated.
As someone already pointed out, the systemui.apk is not the same in the newer versions of PA and just because it seems to work cosmetically does not mean it isn't breaking some things under the hood. I for one have noticed broken bubble text saying things that make no sense, for instance when I long press the back button to kill and app it says "Launch Browser?" instead of "Application Killed" and when my phone is charging instead of showing the word "Charging" and the percentage in the lockscreen it says "Try Again?".
Anyway, I appreciate the time the developer (aooga) has put in but he seems to completely overlook updating lately and rarely even checks the thread. Anyone willing to help out on getting this mod to work would be greatly appreciated.
The developers for Paranoidandroid have removed the statusbar/navbar transparency settings because they are recoding them and said that the project is "on hold" right now and it might be quite some time before we see it implimented. This is why I am making this request.
*I've noticed that gangsterjoop has just updated the toro paranoidandroid to 2.22.
Thanks in advance to anyone willing to give it a go!
Wow, nobody would like to help with this?
I support you man !!
So, I am running the AOKP ROM v.3.1 but when check for an update, it says that d2att (4.1.2 JZO54K) Build 12.2.2012 is available. I click YES to install it, and it downloads, but it never actually installs... Do I have the right AOKP rom on my S3 (I747) ???
Also, I really miss the phone calling functionality where you swipe your finger to the right to make a call, and swipe to the left to creat a text message. I figure that this is a ICS thing...
I am surrently experiencing some small bugs with my AOKP rom when I make a call, but its difficult to hang up after a call as the call screen has dissapeared.
BTW, I am coming from having a iPhone for 4 years, so this is my first Android phone/expreience...
one last thing, I really liked the AccuWeather widget that came with my phone - it is the widget that you could swipe up and down to get the different cities, but I cant find that same one anywhere in Google Apps...
Any advice is appreciated!!!
Some of the things your looking for I believe are only available on a ROM based on touchwiz and needs the TW framework. Thats the same reason you cant use the camera that cane with stock. Like the phone swiping and the accuweather. The ROM your on is not, its AOKP. Someone else I'm sure will chime in to help as I'm not running the ROM your on.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
maybe i should just go back to the stock ROM ?? I m not even sure that I have the right AOKP rom as I cant update it OTA...
Any suggestions?!
Take a look at this ROM. Not sure what urs looking for but this is a mix. Based on TW. Also look Ariel.
http://forum.xda-developers.com/showthread.php?t=1765130
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Does the ROM you suggest do OTA updates?
For any Touchwiz users: does it provide a OTA update? Does it have the stock AccuWeather Widget? Can I still swipe to the right to make a phone call and swipe to the left to create a text message??
I am sure i know the answer to this, but is there any way of fixing this without flashing a custom rom? Even if i have to root and keep stock, i am ok with that. I just wanna fix this STUPID stupid feature that samsung was obviously drunk and thought it would be a good idea to put in...
I hate that i have to edit my ringtones just to make them sound right for this stupid "feature"...
Like i said, even if I have to root, I am ok with that. I just want to keep my stock rom, UNLESS someone has found a way to make all the features of stock work in a custom rom with some perks (like spen opens snote or evernote, or wificalling is there, etc...good USEFUL features)
Some people modded the secphone.apk and got rid of it for s3...and i think it was for verizon or at&t. Try searching for it and you can try doing it yourself.
http://www.mediafire.com/?56fn99xzjegx547 . flash via CWM
Download "Disable Increasing Ring" app from Google Playstore. Works great, no root needed.
tbvnz said:
Download "Disable Increasing Ring" app from Google Playstore. Works great, no root needed.
Click to expand...
Click to collapse
omg it works....now if only it didnt have a notification....or was an option in the phone from the getgo! Seriously! Im just glad they fixed the stupid "unable to open camera while in call" stupidity...what the hell was that all about.
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