Related
Hi all,
I am going through all the threads that have ics based roms for our phone and thought it might be a good idea if we had a communal collation of all ics roms that are active in this forum with provided chainlogs and small reviews of said rom and what issues they have.
Reason for this is simple, to help other users that are not confident in flashing up to 4.0.3 unaware that they may run into something that they did not bargain for.. Hopefully this way we
A) Get a general run down each week as to what rom is working well which are not.
B) Issues/bugs.
C) Reviews of what works and not.
D) Temp fixable issues ie: auto rotation.
E) May help in less clutter in actual development thread.
I thought I would put this out see if anyone agrees here. I am more than welcome that if we use this thread as a starting point.
In no way shape or form that this thread will be used as a means of competitiveness between devs, to start flaming in any sort of fashion, this is purely a thread designed to help everyone with ics progression where its at, what dev's are up too and which would be safe to flash and what is not and is for experimental use.
Hopefully this could be a useful thread, with the dev's permission in doing this of course
Cheers.
I like the idea
+1 to this idea!!
There are already Q&A threads for each of the ROM's. Why make the board more cluttered than it already is by re-posting what is already in those threads?
People need to learn to use the search function and stop being lazy and actually take the time to read a thread every now and then. A thread like this will do nothing but enable the lazy to be even less productive and will not help. You will just see the same questions asked here over and over and over and over and over just like in all the other threads.
Also if people would read a damn OP like they are supposed to before flashing a ROM they would already know what does and doesn't work and if the ROM is a RC or experimental.
+1
Sent from my SAMSUNG-SGH-T989 using XDA
DannyB513 said:
There are already Q&A threads for each of the ROM's. Why make the board more cluttered than it already is by re-posting what is already in those threads?
People need to learn to use the search function and stop being lazy and actually take the time to read a thread every now and then. A thread like this will do nothing but enable the lazy to be even less productive and will not help. You will just see the same questions asked here over and over and over and over and over just like in all the other threads.
Also if people would read a damn OP like they are supposed to before flashing a ROM they would already know what does and doesn't work and if the ROM is a RC or experimental.
Click to expand...
Click to collapse
Valued response, and yes using the search tool does help, but. rather than searching for what is needed why don't we have one thread to sum up on all progression? This thread is not designed to have countless questions all this is to gather weekly updates on ics roms from there respected developer. If someone wanted to ask questions they should be directed to the respected Q&A thread as they have there own. If someone wishes to choose to read up on what is happening in the world of ics t989 development then they come here nothing more nothing less.
As this wouldn't be hard to do at every week commencing someone can be anyone can choose to post up any sort of update to any rom and that is valid for that week only... then make up another thread so for example this one wouldn't spiral out of control and inform a mod to delete or close thread... simple that way it would stay fresh relevant with what we want to know, and of course anyone can participate in this.
Again thanks for your input, I'm not saying this is what we should be doing but a suggestion to everyone and see if this would make life a little easier on some. Alternatively if you don't like it then don't post anything worth mentioning and leave for people who could benefit from it
Cheers.
Issues for all ICS Roms outside xRavers AOSP
Autorotation
Possible Issues:
Echo Call
SMS Fail
Gallery Problems
Shutdown Issues
xRaver AOSP -> see xRaver AOSP thread
Pretty much covers it Can end thread pretty soon.
Is anyone working on a ics kernel for our devices?
Sent from my SGH-T989 using Tapatalk
tdizzle404 said:
Is anyone working on a ics kernel for our devices?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
i am based off the skyrocket sence we dont have **** for our device....
RaverX3X said:
i am based off the skyrocket sence we dont have **** for our device....
Click to expand...
Click to collapse
Cool how's it coming along?
Sent from my SGH-T989 using Tapatalk
RaverX3X said:
i am based off the skyrocket sence we dont have **** for our device....
Click to expand...
Click to collapse
Hi RaverX3X , and would you mind others or yourself would post up on your current progression of your ics roms and their chainlogs and known issues so that way people who this need only to see the basic stats and if it is suitable for daily use?
Cheers.
Sent from my SGH-T989 using XDA
tdizzle404 said:
Cool how's it coming along?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
not as fast as i like but then agian i dont have a whole lot of time to work on it if i could do it 24/7 365 lol prob would have had it done or further then i am now
Agera said:
Hi RaverX3X , and would you mind others or yourself would post up on your current progression of your ics roms and their chainlogs and known issues so that way people who this need only to see the basic stats and if it is suitable for daily use?
Cheers.
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
4th post has the chainlog... or third i dono ll go look lol
Gallery Workaround
jim93 said:
Issues for all ICS Roms outside xRavers AOSP
Autorotation
Possible Issues:
Echo Call
SMS Fail
Gallery Problems
Shutdown Issues
xRaver AOSP -> see xRaver AOSP thread
Pretty much covers it Can end thread pretty soon.
Click to expand...
Click to collapse
To replace my battery and my camera since it force closes, I use QuickPic as my gallery and Camera zoom FX Pro as my camera. They work pretty well with some minor set backs.
Echo?
Are there any ICS ROMs that do not have an echo????
It seems to be an issue with the flashing process as far as echo goes...easy does it, my DD has no echo...actually while many people have reported that among other bugs the only one I have is the reboot hang...which really...tough **** I have to hold the power button down the few times I need to turn it off lol. Oddly though it does not hang if I reboot into recovery from rom manager.
Ics is really weird...everyone is getting different bugs following the same install process. I'm guessing some of our devices are more willing to adapt to the skyrocket kernel than others...
zander21510 said:
It seems to be an issue with the flashing process as far as echo goes...easy does it, my DD has no echo...actually while many people have reported that among other bugs the only one I have is the reboot hang...which really...tough **** I have to hold the power button down the few times I need to turn it off lol. Oddly though it does not hang if I reboot into recovery from rom manager.
Ics is really weird...everyone is getting different bugs following the same install process. I'm guessing some of our devices are more willing to adapt to the skyrocket kernel than others...
Click to expand...
Click to collapse
Guess you got the one with the magic bean.
Well before I went on vacation Tuesday I was playing around with a few of the different ics that are there for tmo gs2 and found that a lot of issues went away when I unmounted the SD card. The camera had no problem and I didn't notice any echoed sound. Kind of strange but one thing I noticed that a lot of native ics devices don't have external SD cards. Might be something for devs to look at.
Sent from my Galaxy Nexus using Tapatalk
retrofred said:
Well before I went on vacation Tuesday I was playing around with a few of the different ics that are there for tmo gs2 and found that a lot of issues went away when I unmounted the SD card. The camera had no problem and I didn't notice any echoed sound. Kind of strange but one thing I noticed that a lot of native ics devices don't have external SD cards. Might be something for devs to look at.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
tried like you said... not true on my phone... either way it does not work.
Rather than start another thread, while perusing the amaze forum I stumbled.upon info on CM9..
According to this https://plus.google.com/106544349933037831956/posts/4Lpyw9bPBCq
Which is the Google+ page of the dev in charge of maintaining CM9 on the amaze, no cyanogen dev is currently.working on our device. Sad to see but figured I'd share for those ccurious
Sent from my Real Gs move in silence like lasagna
FOR AT&T LEAK BASED ROMS ONLY. NOT FOR CM9 or gingerbread!!!
Hi all,
No more call echo
This fix uses the proper T989 audio parameters so noise suppression actually works like it should (car dock should work too in theory). On top of that is Samsung Diamond Voice Engine which really makes calls sound great.
It fixes the issue at the core, within the audio libraries. The audio paramaters and noise cancelling routines now work as they should.
UPDATED
I think I finally fixed this f$cking issue once and for all. For real this time. Try out the newest update I have attached to this post (Diamonds.zip)
This patch is a breed of libraries from the Galaxy Note and the Galaxy Blaze. It took me a very long time to put it together. But with a lot of work and hex digging I found the perfect combination.
I don't even think T-Mobile's ROM is going to sound this good
You might still have to turn down your volume a notch if you have a troublesome case, but I am going to make a bold statement and say that this should fix the problem for a 90% portion of you
Also--by its nature--this newest patch should fix the car dock audio problems. I can't test it to confirm. Please let me know if it does.
Report back with results!
Devs you are free to use. Credit is all I ask I spent lots of time on this and not enough time working on a project due tomorrow >_<
To the kind folks that donated to me in the past few days. thank you and I will thank you personally and address my PMs too. Been on and off the grid because of finals.
Cheers
Yaldak
Sent from my SAMSUNG-SGH-I727-IcyS using xda premium
Dear sweet baby jesus yes!! DLing, gunna see what happens! ur the effin man, seriously.
I've made two phone calls yaldak and asked if they here an echo. They both said no..
1st call was w/ case
2nd call was w/o case
Before it was hit and miss for me some ppl would complain if echoing bothers were not..
So far so good brother
Edit 1 : have not had an oppurtunity to test compass.
Sent from my SAMSUNG-SGH-T989 using xda premium
Good to hear. Compass is still broken in this version
Did 4 test calls myself. All reported no echo.
Sent from my SAMSUNG-SGH-I727-IcyS using xda premium
great work my friend!.. i love your rom. and your fixes.. rotation, facebook font, now echo ! great!
I think TDJ already fixed this issue you should ask him for help if he'd be willing to share.
Sent from my SGH-T989 using xda premium
unlvmike said:
I think TDJ already fixed this issue you should ask him for help if he'd be willing to share.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I know people keep saying he fixed it, but if he did. I would expect he would have released it. Unless he is doing the community a disservice and trying to squander the fix for him self only for glory or what ever other reasoning.
Also to the OP. What do the display firmware in /etc have to do with the audio echo? and i understand you're trying to fix the compass so is that why the sensors lib is in there?
Based on his new ROM being a beta I think TDJ is testing a fix same as Yaldak.
Hopefully they both work.
Sent from my SAMSUNG-SGH-T989 using xda premium
Seems legit, my wife won't hate talking to me! Do you drink? If so, what's your drink of choice? If not, I'll buy you a burger.
Here's something to show my gratitude - 0LC82576P94652635.
unlvmike said:
I think TDJ already fixed this issue you should ask him for help if he'd be willing to share.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
The approach used in the Darkside ROM is different. I did a library comparison to verify it.
While the approach should work because it appears to reverse the noise redcution switch (hence why the TDJ says to keep it on), this approach fixes the problem at its core--audio library side. Noise reduction will work exactly as it did in Gingerbread. Some people in that thread are still reporting the call echo issue because the audio paramters are off in all of the Skyrocket-based roms.
A LOT of work and experimenting was done to narrow it down to this one stupid file.
-Mr. X- said:
I know people keep saying he fixed it, but if he did. I would expect he would have released it. Unless he is doing the community a disservice and trying to squander the fix for him self only for glory or what ever other reasoning.
Also to the OP. What do the display firmware in /etc have to do with the audio echo? and i understand you're trying to fix the compass so is that why the sensors lib is in there?
Click to expand...
Click to collapse
There is no display firmware. That's sensor firmware. This is preliminary work toward fixing the compass, as such it is a work in progress. It's not a beautified patch just yet
Seems legit, my wife won't hate talking to me! Do you drink? If so, what's your drink of choice? If not, I'll buy you a burger.
Click to expand...
Click to collapse
A beer will do my friend
I had echo before and using NexusMod.
Made calls to a POTS, VOIP, and another cell phone.
These people had complained about the echo before and report these calls sounded fine.
Thanks and great work.
Hey Yaldak,
I'll test this out on RomChicago tonight, which is based on your base.
As far as the compass goes, I didn't even realize there was an issue with it until now. I'll check the parts bin to see what works.
This is why I use your bases, because you da man.
Sent from my SGH-T989 Lawyerphone
What ICS ROMs is this patch compatible with?
Thanks for the patch. When I flashed it.in CWM its says auto rotation fix lol. Just forgot to rename it? Did I download the wrong one. Thanks!
deathknellx said:
What ICS ROMs is this patch compatible with?
Click to expand...
Click to collapse
Should work with all of them.
Thanks for the patch. When I flashed it.in CWM its says auto rotation fix lol. Just forgot to rename it? Did I download the wrong one. Thanks!
Click to expand...
Click to collapse
I didn't rename it, this is still "beta"
So would this work on megamix 1.31 ROM?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
HoustonsBirdman said:
So would this work on megamix 1.31 ROM?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I don't see why not.
test it with the new darkside ics rom before and after and people reported to me the they had an echo..
not only that when im back to gingerbread people says that they dont hear an echo but they hear my voice like im coming from out of space
gypsy214 said:
test it with the new darkside ics rom before and after and people reported to me the they had an echo..
not only that when im back to gingerbread people says that they dont hear an echo but they hear my voice like im coming from out of space
Click to expand...
Click to collapse
Darkside's ROM has another approach to this issue....so that is probably why.
It is also likely that--since you had the issue with gingerbread--your phone might be defective. My GB audio was crystal clear.
I'm up to 8 phone calls (2 incoming 6 out) in which the recipients reported no issue.
Is it difficult to apply this? Just asking cuz I never applied a patch. Switching roms, navigating thru root explorer, etc no problem.. but I don't want anyone wasting time explaining it if its something you believe is too complicated to do so. I'd just love to have call echo fixed so people stop telling me about something I already know. Never had call echo on GB. (I have tried the search but with how many posts there are with 'how to' and 'patch' in them its quite difficult and easier to ask)
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
I've noticed a large amount of glitches and bugs in GC01. If you find any please list them here.
some of the bugs ive noticed:
*Volume slider and slider animation
*Random Reboots
*Missing Features
*Unstable in general
eisawi99 said:
I've noticed a large amount of glitches and bugs in GC01. If you find any please list them here.
some of the bugs ive noticed:
*Volume slider and slider animation
*Random Reboots
*Missing Features
*Unstable in general
Click to expand...
Click to collapse
Just a suggestion, but you may want to consider expanding on the issues so those that may feel like investigating have more to go on. For example..:
*Volume slider and slider animation - Can you provide a screenshot for reference of the issue?
*Missing Features - A list of what you find missing would be helpful. For example; Sprint removed Maps and YouTube since they can be downloaded from the Play Store...
*Unstable in general - How so? What are you seeing that makes you say it's unstable..? FC's, freezing, etc?
There again, only a suggestion but you may get more participation or helpful thoughts on remedies..
More Updates?
I was half expecting gb27 to be the end of the line for this phone.
MrLint said:
I was half expecting gb27 to be the end of the line for this phone.
Click to expand...
Click to collapse
GC01 is Boost's Official JB release.
Post removed. Wrong thread.
Now stop the bickering please.
Post edited.
People please... keep this thread on topic. There are a large amount of boost mobile users that are debating on whether to update or not. Thank you.
Wow... A newbie throwing out rules... Granted threads should stay on topic, but you should understand who is posting in your thread, OP. Garwynn is one of the biggest contributors for the E4GT as well as MoHoGalore. I don't think you have any room to make those kinds of demands when a RC has given you advice on this thread and you completely ignore it. So really, this thread has no real topic of discussion because it says absolutely nothing because of the lack of information provided, therefore people can post whatever they want because this thread is just cluttering up the forum.
Sent from my SPH-D710 using xda premium
graydiggy said:
Wow... A newbie throwing out rules... Granted threads should stay on topic, but you should understand who is posting in your thread, OP. Garwynn is one of the biggest contributors for the E4GT as well as MoHoGalore. I don't think you have any room to make those kinds of demands when a RC has given you advice on this thread and you completely ignore it. So really, this thread has no real topic of discussion because it says absolutely nothing because of the lack of information provided, therefore people can post whatever they want because this thread is just cluttering up the forum.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Whether they're senior members or not, they should follow rules. They could be the owners of XDA and I'd still tell them to stay on topic. There are threads for general conversations, this is not one of them. Rules are rules, and they are meant to be followed. Now please stay on topic people, people really need these kinds of things. And also, he gave me a suggestion. I did not follow his advice because I did not feel the need to do so. My thread, my topic, my list. Whoever wants to add to the list can. Bugs need to be reported to samsung so that hopefully we will have a better future release.
eisawi99 said:
Whether they're senior members or not, they should follow rules. They could be the owners of XDA and I'd still tell them to stay on topic. There are threads for general conversations, this is not one of them. Rules are rules, and they are meant to be followed. Now please stay on topic people, people really need these kinds of things. And also, he gave me a suggestion. I did not follow his advice because I did not feel the need to do so. My thread, my topic, my list. Whoever wants to add to the list can. Bugs need to be reported to samsung so that hopefully we will have a better future release.
Click to expand...
Click to collapse
Well if his advice is not important, then I am going to ask a mod to close this thread because it provides nothing. Also, that will be the last update from Samsung, so with that said, this thread is useless. I also am curious about who is reporting said "bugs" to Samsung? Do you think they will come here to find it? Nope. For the record, they nor I are just Senior Members. All of us that have posted and offered advice are Recognized Contributors. One would do well to take the advice of an RC to help better a thread, instead of blatantly ignoring them. We have been around for quite some time and in that time have learned how things work.
Sent from my SPH-D710 using xda premium
as soon as i gather more bugs i will report to samsung over and over until they release another update, and it was never stated that this would be the last update for the boost model. and if this thread does get closed ill start a fresh new thread where theres no un-needed conversation.
Accidental extra post
eisawi99 said:
as soon as i gather more bugs i will report to samsung over and over until they release another update, and it was never stated that this would be the last update for the boost model. and if this thread does get closed ill start a fresh new thread where theres no un-needed conversation.
Click to expand...
Click to collapse
The Boost model is the same as the E4GT. The 4.1.2 JB Update has been reported as the final from the Samsung sources. I highly doubt they will pay attention to one person reporting little bugs, especially when you don't describe them at all. They have more important things to worry about.
i have a question. does it make you feel better to put people down over the internet? does it make you feel as if your in control of everybody? im not going to be the only one reporting. others that want a bug free GC01 will also report. now please stop further cluttering my thread and go troll someone else.
eisawi99 said:
i have a question. does it make you feel better to put people down over the internet? does it make you feel as if your in control of everybody? im not going to be the only one reporting. others that want a bug free GC01 will also report. now please stop further cluttering my thread and go troll someone else.
Click to expand...
Click to collapse
How am I putting you down? I am agreeing with another RC about your thread not having any descriptions to your so called "bugs". I am not trying to control anything. I am offering the same advice. You can do whatever you like, but I can bet that this thread will either die as is, or it will get closed. You can either let one of the 2 happen by not doing anything to fix it, or do something productive and make it a worthwhile thread. Also, take note. I have not seen very many other people complain about it. Seems like you are the only one or one of a very few people.
Protip: Putting full, well thought out descriptions of your issues will help us help you possibly fix them. If you don't think descriptions are important, you will get nothing.
Example: When testing Shadow_God's Jellyverse 2.0 ROM before he posted it. I ran into a few crashes. I didn't just say "Oh, it crashed". I went into details. "Downloaded via Wi-Fi and installed through Agats GB27 RePack. ROM booted fine, but shortly after getting into the setup process the Android.phone process started force closing. My baseband seems to have been wiped and the launcher seems to be nonexistent."
I then took steps to fix it myself. I was able to fix it with little to no effort, and SG was able to post the ROM without any issues.
So with all that said, if you want to ignore very experienced veterans on XDA, that is your choice. You are free to do so. But don't expect me or anyone else to take you seriously when we make an honest effort to gain viable and needed information to potentially resolve the issues, then have you ignore the efforts.
Consider the following, if we don't take you seriously because of your lack of information and willingness to help us help you, do you honestly think Samsung will give even the slightest crap? They won't... Like I said before, they have better and more important things to do.
From the moderator
To all in the thread...........
Post respectfully......... FOLLOW THE RULES OF XDA OR I CLOSE THE THREAD......
......Thx, oka1
oka1 said:
To all in the thread...........
Post respectfully......... FOLLOW THE RULES OF XDA OR I CLOSE THE THREAD......
......Thx, oka1
Click to expand...
Click to collapse
I vote for option two.
The lack of description on these so called bugs is not informative to the readers, it makes me want to try flashing GC01 to my E4GT just so that I can try to experience whatever issues are being mentioned.
Sent from my SPH-D710 using xda premium
Removed my first post on this thread. I was wrong to post here and op was right to call out.
Op... how you updated to gc01 makes a difference. I still recommend a factory reset or full restore one click. This will resolve most issues as noted in past.
As for whether to update or not that's your call. Most around here believe it is FAR better than ICS and even though this is expected to be the final s/w release feel free to complain to Samsung and/or Boost if not happy. That's your right.
But please avoid using generalizations and then assuming the build is bad based on one individual's experience. That too does other folks a disservice. If you can please provide more specific details it helps the community note confirmed issues and possibly address them on our own.
Thanks.
Sent from my SPH-L900 using Tapatalk 2
I never stated that the build was bad, but like every build it has bugs. the reason i didnt further explain is beacause there really is no way for a screenshot... but i believe i found a fix to anyone experiencing these bugs. so heres what i did to fix my problem.
1. download superuser.zip from rwilco's repo
2. download the gb27 repack from rwilco's repo
3. download the stock gc01 stock kernel
4. place superuser.zip on your sd card
5. Odin the GB27 repack
6. enter recovery and flash superuser.zip
7. delete dalvik cache
8. odin stock gc01 kernel
9. reboot twice
Mattix724 said:
I vote for option two.
The lack of description on these so called bugs is not informative to the readers, it makes me want to try flashing GC01 to my E4GT just so that I can try to experience whatever issues are being mentioned.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
go ahead. the more help the better. it is not some bug that will make you loose all your data... it is minor bugs that annoy the (insert profanity here) out of me. keep in mind there are two installation methods to installing GC01 provided by samsung, local and kies. i chose local because kies wouldnt update for somereason and would randomly crash
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
SuperSU on TW ROMs running 4.3 (regardless of version, source of version and how you got it) is frustrating. Apps that need root do sometimes able to get root access, and most often than not wont' be able to.
YES !!! I have done more of my share of reading. And please do NOT treat users with less than 10 posts like idiots.
*** The only solution is to change between Default Access modes. Going from grant, to prompt. Doing so for some strange reasons wakes up SuperSU***
The following solutions DO NOT WORK (meaning the problem resists)
1. Flash Antenna (regardless of which, even with the one provided by OP on their threads)
2. Flash insecure kernel zip
3. Download the version form Play and Update
Hope this help any of you that are experiencing some crazy frustrations like me.
*** Not to offend anyone, but the rule of 10 post or less = No reply/post on dev. forum is beyond me ***
*** I have tried to report my experience with certain ROMs, but Nooooooooooo.... <10 amigo ***
--- One more, since I think I am going be booted because of offending Seniors Party Members. ---
Can anyone tell me the logic of formatting a partition 3 times ??? I found this ridiculously offending being an engineer myself.
I do appreciate every single one of the developers who spends countless hours to make the word "FREE" as free as possible.
@mrbackdoor
Whoa Cool down Bro. Take a deep breath. Now tell me what precise are your problems ? I got the part with SuperSU making you go Ape. But what's with Roms and 10 Wipes ? I have no Idea what you are getting at.
So about SuperSU. If that app is making you go nuts, why don't you try SuperUser by @ChainsDD ? There's also a great Superuser app from CM team. But without knowing your Rom, I won't recommend it.
Do Kindly note, some Root apps are not compatible with 4.3. So you may get weird errors. Others like Nandroid Manager have their own limitations on Root access.
P.S. - Your Current Post Count is 1. I did respond right ?
LOL... thanks man. I am positively NOT HOT
what's with Roms
>>> TW 4.3 ATT leak on Tmobile LTElessS3
>>> I was just venting the fact that a member CAN NOT post on Development Forums because he/she has less than 10 posts.
>>> That's like filling 10 forms before you are able to download a file. Similar to registration process that just drive you nut.
>>> One engineering note is wiping a partition 3 times. The wipe process before installing a new ROM.
>>> I just don't get it... Why 3 ??? "insanity according to Albert Einstein"
Superuser..But without knowing your Rom, I won't recommend it.
>>>Superuser - NOT an option, not even working
Do Kindly note, some Root apps are not compatible with 4.3. So you may get weird errors. Others like Nandroid Manager have their own limitations on Root access.
>>> YES sir. Fully understood
P.S. - Your Current Post Count is 1. I did respond right ?
>>> call me up when you want a beer... or couple shots of the good sh****
@mrbackdoor
I don't have the ATT S3 Let alone the leaked Rom so can't comment. I hate TouchWiz anyway. I don't want to comment on the rules. They are there for a reason. Yes they may be an irritant but they keep Noobs away. You my dear friend is a Newb. There's a difference.
Whoever asked you to wipe the same partition 3 times needs to get their head examined. But then I am jumping ahead without knowing full circumstances. So if you don't mind, show me the thread link.
Are you trying to get the Leaked ATT Rom with a working Root ?
Now you too sir, have been guilty as well. I need to have full problem statement, which I am sorry I have not got as yet. So can you kindly explain what precisely are you trying to do and where does SuperSU come into play ?
Ok, first, please don't assume we are all jerks who are going to belittle you or treat you horribly and then ban you from OUR playground. I personally felt it a little insulting that your first post, coming to us for help, was so defensive and presumptuous.
Yes, we want you to do as much on your own as you can. No, most of us do not consider a low post count an indicator of idiocy. We might, however, judge how much we want to help depending on the quality of your post, or any other OP by anyone. If you do your best to find your own answers, and post clearly and respectfully, it'll show.
And there absolutely are reasons for all the rules here, and no one wants to hear anyone complain about them. (And if you haven't actually read them, please do so). The 10 post rule is to prevent spammers and bots from being able to post in the most important sections. And it's just 10 posts...see you're already on your way!
So if you'd care to try starting over on a better note, here are my points regarding your issues.
There is no real benefit to formatting something more than once. This is something that apparently began with some old device where the recovery wouldn't always format correctly. So people got in the habit of wiping several times rather than the king after each time. They then spread out across xda and push this practice like gospel sometimes, even though it gives no benefit and imo shortens the life of the device. I have tried to point out to folks this is not necessary, but gave up long ago! To each his own.
Enewman found a bit of a workaround for the su issues. It's not perfect but does seem to help a little.
Find these files
/etc/install-recovery.sh
/etc/init.d/dameonsu (or similar named script)
Find this line
/system/xbin/daemonsu --auto-daemon &
Delete --auto
Reboot
Hopefully that helps. And fyi, I'm going by memory, but am pretty sure I've been fairly accurate.
But also keep in mind that it's a combo of things, you do also need the insecure kernel. And Knox is still gonna screw with it if it's not been removed.
Also, try to remember, all of this stuff is brand new to all of us. Do not expect miracles, it takes time to relearn everything for everyone. But if it's really that bad, then consider going back to an older Rom for now.
These are after all leaked builds and should not be expected to be fully functional and bug free.
Sent from my SGH-T999 using Tapatalk
Dr. and Perseus
To you both, thank you, thank you and thank you. It would have been more appropriate on the General thread. Anyhow:
Perseus
If needed, I can point you to the threads. You are kind. I do appreciate that.
Dr.
I think you know exactly what I was talking about. So to you I do apology if my post is offended. In fact, to anyone who do feel the same. My bad.
please don't assume we are all jerks who are going to belittle you or treat you horribly and then ban you from OUR playground. I personally felt it a little insulting that your first post, coming to us for help, was so defensive and presumptuous.
>>>No Sir, no way in any shapes or forms I do assume people are jerks. Like I stated before, I was just venting on the fact that the rule cripples members ability to contribute and alienates them as well.
And there absolutely are reasons for all the rules here, and no one wants to hear anyone complain about them. (And if you haven't actually read them, please do so). The 10 post rule is to prevent spammers and bots from being able to post in the most important sections. And it's just 10 posts...see you're already on your way!
>>> Understood. Complain is absolutely not my thing. If there is a way to monitor users' footprints, you will find out that I have been here for a while, and it just not my style to complain or ask unless I have read just about anything posted.
So if you'd care to try starting over on a better note, here are my points regarding your issues.
>>> Of course.
There is no real benefit to formatting something more than once.
>>> Got it. Now's that is at the core. That's exactly what I was looking for. Instead banging my head trying to understand how partitions are being formatted and the file system that is basically associated to the NIX for a long time . Basically what I posted is the workaround that I use for now.
Hopefully that helps. And fyi, I'm going by memory, but am pretty sure I've been fairly accurate.
>>> Correct.
But also keep in mind that it's a combo of things, you do also need the insecure kernel.
>>> Appreciate your time Dr.
Statement below is my initial love your developers. That has not changed. Just "kang" members that I do find .... well.... you got my drift.
"I do appreciate every single one of the developers who spends countless hours to make the word "FREE" as free as possible."
Whenever you two do find your way to America Finest City... ring me up. A few rounds on me, if not all.
Again, thanks.
mrbackdoor said:
you will find out that I have been here for a while, and it just not my style to complain or ask unless I have read just about anything posted.
Whenever you two do find your way to America Finest City... ring me up. A few rounds on me, if not all.
Click to expand...
Click to collapse
Actually your join date of May '11 is the first thing I noticed. Pretty big time Reading on your part if you didn't ask before.
I am afraid we are still missing the problem you posted for aren't we ? Or what steps Doc suggested about the leak solved your problem ?
I'm on the app most of the time, so I can't readily see post counts, join dates, junior/senior member status, etc. But anyway, thanks for the reply op. I lurked around the forums for about a year before my first post, reading and learning all I could, so I can appreciate that you seem to have done so as well!
I was slightly off earlier, when you find those files, change this:
/system/xbin/daemonsu --auto-daemon &
To this:
/system/xbin/daemonsu --daemon &
Had to go look it up again. Sorry bout that!
@Perseus71
I'm pretty sure his main issue was that root wouldn't always work. After a little while sometimes root apps will lose their root access, which can be annoying, obviously! Some have just resorted to opening and closing the app a bunch of times till it regained root.
If I'm not mistaken it's due to seLinux blocking root. And by removing auto from the script, it forces the daemon to run persistently, as opposed to just when it's called, thereby helping to retain root access.
Another workaround I read somewhere was to tell SuperSU to ignore the apps permissions, or something like that. Not positive on what they meant right now, I'll have to try and find it again to be sure.
The other part of this is the insecure kernel. This will set seLinux status from enforcing to permissive. You may have to reboot or even reflash the kernel if it doesn't change from what I hear. I've not seen this myself though.
And then there's Knox. If it's not removed it can also cause problems with root access.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
@Perseus71
I'm pretty sure his main issue was that root wouldn't always work. After a little while sometimes root apps will lose their root access, which can be annoying, obviously! Some have just resorted to opening and closing the app a bunch of times till it regained root.
If I'm not mistaken it's due to seLinux blocking root. And by removing auto from the script, it forces the daemon to run persistently, as opposed to just when it's called, thereby helping to retain root access.
Another workaround I read somewhere was to tell SuperSU to ignore the apps permissions, or something like that. Not positive on what they meant right now, I'll have to try and find it again to be sure.
The other part of this is the insecure kernel. This will set seLinux status from enforcing to permissive. You may have to reboot or even reflash the kernel if it doesn't change from what I hear. I've not seen this myself though.
And then there's Knox. If it's not removed it can also cause problems with root access.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Oh I see. Honestly on my 4.3.1 rom that I had, I never experienced this problem. Possible its related to the leaked Rom's implementation of SELINUX?
I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers. The developers do they developing, and we do modifications to make things how we want them and hopefully others enjoy it too, that's all.
To OP, we're aware this SuperSU problem was annoying, we were one of the first few dealing with non-stop before bringing the leak from AT&T and debloating it over here.
enewman17 and his infinite knowledge did some poking around in the files and found a way to make root more persistent, albeit this is a leak, and we have Samsung KNOXing at our door. Things are bound to be broken, and especially because myself and others working on the leak are not professional Android developers nor do we ever claim to be, more like hobbyists who try to learn on their own by reading, or their own personal knowledge of NIX' and shell scripting.
Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder.
All
Dr. has it right about the issue (I'm pretty sure his main issue was that root wouldn't always work.). I can work around it. No biggie. Will try the recommended method.
I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers.
>>> Sir, I am not angry. I did explained couple times on previous posts. I just find certain rules and their enforcers hinder members' contributions. Whether that is just saying thanks or report something back. .The process in my opinion alienates the excitement of new members who are willing to do what it takes in hope to return something back. And so I did vent about it, Probably on the wrong forum. And I did apologize. If you want we can table this offline to show you what I meant.
nor do we ever claim to be
>>> Nor did I
Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder
>>> I wouldn't doubt you. I've seen your work.
>>> The point is not about developers, contributors, members. Just rules and the re-reinforcement. I personally believe any voice is constructive and beneficial. I am not a NIX person, but I do find the creation of the linux kernel and its distributions since then fascinating. Awesome technologies have been built due to the collaboration of community sharing and giving back. I am almost certain xda was also created on the same principle.
mrbackdoor said:
All
Dr. has it right about the issue (I'm pretty sure his main issue was that root wouldn't always work.). I can work around it. No biggie. Will try the recommended method.
I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers.
>>> Sir, I am not angry. I did explained couple times on previous posts. I just find certain rules and their enforcers hinder members' contributions. Whether that is just saying thanks or report something back. .The process in my opinion alienates the excitement of new members who are willing to do what it takes in hope to return something back. And so I did vent about it, Probably on the wrong forum. And I did apologize. If you want we can table this offline to show you what I meant.
nor do we ever claim to be
>>> Nor did I
Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder
>>> I wouldn't doubt you. I've seen your work.
>>> The point is not about developers, contributors, members. Just rules and the re-reinforcement. I personally believe any voice is constructive and beneficial. I am not a NIX person, but I do find the creation of the linux kernel and its distributions since then fascinating. Awesome technologies have been built due to the collaboration of community sharing and giving back. I am almost certain xda was also created on the same principle.
Click to expand...
Click to collapse
Glad to know we could be of assistance. Glad to clear that up with you. Feel free to post more, don't be such a lurker!