http://forum.xda-developers.com/showpost.php?p=7401058&postcount=5946
I posted the above in the nightly build thread, but it's moving so fast I'm afraid no one will ever see/respond to such a specialized issue.
I need some help, guys. I've already spoken directly to the developer and they were not able to address the issue. I've been using a program called "Quick Profiles" every since I got my Evo. It's EXACTLY what I need. It worked fine on stock and damage control. But since I've switched to Cyan6, it's not worked. It force closes. The developer seems to think it's a problem with the ROM.
I've attached a logcat, so if anyone can take a look at it and give me some pointers I would appreciate it.
Click to expand...
Click to collapse
I know someone else in that thread (bkfitz) indicated he was having the same issue. I'm attaching a logcat to try to help identify the problem. Please chime in if you have any ideas on how to go forward. Like I alluded to above, I've been in contact with the Dev. We troubleshooted the problem for awhile and he, ultimately, decided it must be an issue with the ROM. He's monitoring the forums, I believe, and mentioned that he would be more than willing to collaborate on a solution if that's possible.
Bump.
10 chars
Same force close problem for me with QP and Cyan 6.0 stable mod. But QP works fine with Simply Stunning 4.7.
Hi,
I've purchased a a Samsung Galaxy 551 (I5510) (Middle east region) about a year ago and i was running android 2.2 fine for a while. When the Gingerbread 2.3 update came out i tried installing a European ROM because the ME ROMs weren't updated, it worked fine but had a weird glitch that if the screen was off (phone still working) for a while it would be very dark when turned on afterwards, it looked like this video:
Youtube > /watch?v=Kwll8ZfgaD0
P.S. I didn't make the video, just linking it because its the same issue
it would randomly work again after a couple of lock-screen off-unlock cycles, then happen again randomly when it's off
I tried a number of GB Roms but to no avail, then finally the latest eu roms (I5510XWKPJ) fixed the problem, nowhere to be seen anymore.
After that i tried installing Cyanogen mod for the phone and the problem came back with different degrees:
1. Cyanogen 7 - normal boot, screen gets dark after being off for a while.
2. Cyanogen 9,10 - show samsung logo at start, screen gets dark as soon as the cyanogen logo appears and continues to be
Any help on what would be causing that especially on the newer CM builds? and why it doesn't happen at all in (I5510XWKPJ)
Thanks in advance,
bump
Bump, any ideas?
I just realized that i should have made this thread in the ""Upgrading, Modifying and Unlocking" thread, i will remake it there so feel free to close this.
Instead you could ask the mod to move it there....
They might consider doin if they feel it's worthy
Sent from my MT11i using xda premium
Ghostfreak NB said:
Instead you could ask the mod to move it there....
They might consider doin if they feel it's worthy
Click to expand...
Click to collapse
Yes, I definitely would have, but since the OP already created a second thread there, this one is closed.
Good ROM, cons, I wanted to know how to:
Add / Remove screen (this was possible with Sense 3.5)
Switch screen in a loop (this was possible from Sense 3.0)
Have shortcuts on the lock screen, the number of SMS / Call are visible although the shortcuts located in the dock, but not when the same shortcuts on the lock screen.
Thank you in advance.
I think you must tell the question in the original Rom Thread.
http://forum.xda-developers.com/showthread.php?t=1839004
FYI...
He Can not post with in the thread as he is not able to do so, because his posts are still under 10... i wasn't too...
Mortal Eternity said:
He Can not post with in the thread as he is not able to do so, because his posts are still under 10... i wasn't too...
Click to expand...
Click to collapse
Exact
About adding/removing homescreen, you can't add or remove homescreens. I think it's a bug of fallout tweaks, or rosie maybe. Maybe you should download launchers, this can fix your adding/removing homescreen problems
Sent from my Desire HD using xda premium
Borrowing topic
Since the topic title was fitting, I take a chance at borrowing this thread and asking my question here. Hope OP don't mind! :highfive:
- I wished to ask in the roms own tread, but I don't have the necessary 10 post yet.
I'm having some issues connecting to my WiFi at home after changing to Sabsa Prime v11.0. With Stock Rom and any of the AOSP/AOKP-Roms I have tried there is no problem. Connecting to my neighbors WiFi works, so WiFi is operational.
Any hint on things I can do to rectify this problem?
I'm thinking about trying another RIL, but I'm uncertain if that will help.
Anyone have any ideas?
It's better since the V13, but we don't have de loop.
What's up guys! I have a question, I rooted my phone, I installed tweaked rom and then I installed a theme. After that I installed Nova launcher, and it works great. BUT, the tethering is not working, it connects but it keeps showing me that I don;t have a plan data when I attempt to load a webpage. The funny thing is that if I install the tweaked rom without the theme it will work, but I like the theme and what I have now. So, is there any way I can use the tethering like this now? How can I fix it?
Here are some pics of how it is right now:
http://img401.imageshack.us/img401/7110/screenshot2013032521054.png
http://img19.imageshack.us/img19/8767/screenshot2013032521053.png
Thanks
Thanks but I fixed it already
I think I like this forum, I'm learning a lot xD
Can you say how you fixed it?
Sent from my SGH-T889 using xda premium
Another one of these, "I have a problem, describes the problem" then answers own problem with "I fixed it" without any explanation of what happened and how it happened. just a waste of forum space. Maybe someone else had the same problem and is looking for a solution or someone might run into this problem in the future and by reading what you did help him/her fix it.
I know I just wasted space stated the obvious but it was needed.
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