yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] titanic_fanatic:
I don't have time to search for you. If your unable to do your own research and learn, maybe you shouldn't be using a custom Rom. Use of a custom Rom requires that you are willing to learn how it all works and that includes finding leaked apk or other files. It also requires patience. We as developers of open-source software do all of this for free, we make no money doing this and is it's rude to post the same question multiple times and then pm me 3 more times with same question.

Post only 1 time then wait for a response.

If you follow the link above, you would have realized that this was a file from both the s3 and s4 devices. If you download one of their Roms, you could find that apk, but it will not work on any of our Roms. As they were not developed for use with this apk. You would have to learn how to port it to this device and that is a complicating matter which involves reverse engineering and I'm not willing to even look into that. It's more work than its worth. You will have to do without it.
[Galaxy S II General] JimbobDobalina:
Appalling battery life

Hey, I've been following this thread for a while and loaded the CM10.2 a few days ago, thanks a lot for your awesome work titanic. I like it a lot, and it is running really well except for one fairly major problem.

I'm wondering if anyone else is experiencing terrible battery life with this release - before this I was running the stock JB release, and while battery life has never been great, I am lucky if I get 5-6 hours of standby right now.

I just had the phone on a 2 amp charger in my truck, and with maps+navigation+gps running, the battery went dead even on the charger - phone shutdown the instant I unplugged it. This never used to happen, and I frequently used to run all these.

If I take the phone off the charger about 7am, it is flat by noon, even just sitting in my pocket. Looking at the battery stats, nothing appears alarming - screen usage is usually about 40%. Android System is about 15%, and Android OS is about 10% - and a few other apps, all under 5%

If I leave the phone on the desk, and look at the screen every 5 mins or so, the battery % indicator has always dropped by 1 or 2.

How can I go about tracking down the culprit?
[Galaxy S II General] titanic_fanatic:
I would try both gsam battery monitor and better battery stats. These apps will show you what wakelocks are active, how long they've been active for and much more. What you'll be interested in is the partial wakelocks. These are apps or services that keep your phone from reaching deep sleep which leads to battery loss.

One thing to check first is in Settings -> Wireless & Network -> Wi-Fi -> Advanced and make sure that scanning always available is not checked, this stops your phone from getting into deep sleep and killed my battery at about the same rate as you describe. I also have set keep Wi-Fi on during sleep to never so that when my screen is off, Wi-Fi turns off as well and saves battery (I have a 6gig data plan though and don't have to worry about going over my limit).
[Galaxy S II General] JimbobDobalina:
Thanks

I checked the WiFi settings - I usually have wifi off as I have an unlimited data plan, and my office has no WiFi. Scanning always available was off, and I will try turning WiFi off during sleep. Not sure if that will make any difference if wifi is always off anyway

Don't know if it affects anything, but I am using LTE - but I always was on last OS - just wondering if the new kernel or radio has issues with LTE?

I have installed gsam battery monitor from the play store, will see if that shows anything up.

Thanks for the quick reply!
[Galaxy S II General] formercontra:
When a friend of mine had battery drain that drastic, it ended up being a physical problem with the actual battery.
[Galaxy S II General] danrobi:
That'ds right, maybe battery is just dead. And LTE really drains a battery quite fast.
[Galaxy S II General] titanic_fanatic:
Yes, while it's true that batteries die. He did say it wasn't like this until he switched Roms which most likely might be a rogue app. This can sometimes be fixed by deleting and reinstalling them
[Galaxy S II General] :
On my t989 now...battery is draining about a good third faster than normal....no matter what I try to do.....and the funny part, it takes about a third or half the time to charge. LOL. Should see if my i757m has a compatible battery.

Anyway, Christmas ....on to an LG G2. Apparently they're getting up to 7 hours screen time. Yummy! ;)

So yes....batteries die. Lol
[Galaxy S II General] dmeinder:
Maybe list the ROM as beta and you would't get so many questions.... It just makes sense for a known unstable ROM.

Then I agree, but telling those with legitimate concerns they are pushy when the build isn't labeled correctly isn't their fault
[Galaxy S II General] bitwarrior1:
I tried out the podcast manager Doggcatcher today and it worked flawlessly with bluetooth in the car! Prior to this I did have bluetooth crash while recieving a call but didn't get a chance to grab a log. I've made calls since and had no issues. Thanks again for looking at this, T_F.
[Galaxy S II General] :
TF isn't paid for this. He does it I assume cause he enjoys it and wants his own phone to be better.

That said, flashing roms is a "do it at your own risk" adventure. And the devs are kind enough to share with us, who can't do it ourselves. So they can call a rom whatever they want.....and if any of us don't like the name, features, stability, color or anything at all about it......we can not use it. That's our choice. And the devs don't HAVE to help us with issues at all if they don't want. And many don't. I've never seen a more helpful and involved dev ....ever on this site. And he's currently the ONLY one posting anything at all for the i757m.......

So demanding help, answers, and anything else seems to be pretty damn foolish to me. Cause if anyone wants to aggravate TF for fun or by accident even....he can simply go away.

Know what that means ....as it stands today......the i757m is done. Nothing more. Enjoy it how it is now, cause that's all you're getting.

Understand what I'm saying? ;)

---------- Post added at 09:05 PM ---------- Previous post was at 09:02 PM ----------

TF.....please do yourself a favor and ignore the above user. He's only ever trolled the i757m threads and done all he can do to insult, belittle and taunt you guys.

Friend ....until you start putting up roms ....perhaps show a little gratitude ....instead of hostility. ;)
[Galaxy S II General] dmeinder:
Well.... So much for trying to help and offering a suggestion...

Just calling it like I see it.

For those who want to listen, when flashing a ROM, as a general rule, if your new, shy away from those labeled beta, as they are work in progress... And those that are posted as not having any known issues or problems, should be Ok.... With the exception of the last couple for this device.

So just so they know, the last "complete" ROM is the one from strange Peer, and the others are actually beta...
[Galaxy S II General] :
Voice mail notification. ;)

All roms have quirks.

How about letting go of very old grudges and just leaving this thread alone. We both know the word "beta" would change nothing. Every single post in this thread would be the same. Problem is....there's absolutely no other options with this phone, not if you want the latest android versions. So how about forgetting about hurt feelings from many months ago....and lets all move on. If you don't care for the rom, great. Stop trying to make people look bad and just stay away from this thread if you don't like the rom or the people involved with it.

That's all I'll say. The mods are watching, trust me.

Sorry for cluttering the thread. Again. Lol

---------- Post added at 10:27 PM ---------- Previous post was at 10:14 PM ----------

Oh.....one last thing. Being on an S2 primarily that has tonnes of 4.3 roms.....I can say every single one of them has issues.....and guess what. Not one of them is labeled as a beta.
[Galaxy S II General] titanic_fanatic:
Hey guys, it's alright. He is entitled to his opinion.

Dmeinder, thank you for your suggestion ;) I chose not to list as beta since beta implies not usable as a daily driver, and I'm using it as my daily driver. On your suggestion though, I think listing as alpha would not be a bad idea ;)
[Galaxy S II General] :
I'd say yours has fewer issues than most other S2 versions for 4.3. Never seen anyone tell any of those devs their roms should be called beta.

Opinion is great. And I always encourage free speech. But you and I know that his comments are more than that. Its a grudge ....plain and simple. ;)

But your thread....your rules. I'll let it go. :)
[Galaxy S II General] formercontra:
Can I just say everything's been going great on this ROM for me? No random reboots, no consistent fc's, everything works, it's good at all the things I use it for. Plenty of people have had bugs, but there might be lots more who aren't speaking up because it's stable for them too.

I'm messing around with Performance > Memory Management over time to see what does and doesn't help battery, but I'm averaging 12hrs with 2hrs screen time, which is better than it's been over a few different ROMs.
[Galaxy S II General] sadowling:
I'm no brain surgeon (and won't be offended if the moderator removes this)...but I feel like I would be hard pressed to find ANY forum...let alone a volunteer software development forum with one active developer, where posting the same question multiple times and then pm'ing the same question 3 more times (for a new feature no less) isn't considered pushy. Maybe you hang with a different crowd and that's cool...to each their own. For myself and I think pretty much everyone else in this forum but you...thanks TF, keep up the good work and no need to list the ROM as "beta" IMO. It's a custom ROM...they are ALL beta to some degree or another. Read the the thread, install at own risk, test and report...I can't help but think this goes without saying if you've made your way to XDA.
[Galaxy S II General] titanic_fanatic:
Let's not him him feel unwelcome, I simply wanted to point out that it wasn't necessary.
[Galaxy S II General] danrobi:
Same for me. if this rom would be a BETA, would be the best one out there. I'm don't know anything in programing, and from what i have seen from Titanic, he's got my full thrust. If Titanic decides it is best to move on to kitkat, i will be right behind him.
[Galaxy S II General] danrobi:
To those who have installed this rom, how is battery life so far
[Galaxy S II General] formercontra:
Hard to tell thus far, my Saturday night routine is usually very tough on the battery but it seemed to do pretty well.... it jumps to deep sleep a lot more than any other ROM I've used.

Once I've set up the brightness levels and the new expanded governor settings, I'm very optimistic about this phone's charge. Like I said though, it'll be another few days until it settles.
[Galaxy S II General] :
Great work TF!! never thought I'd see 4.3 on this device!!! Awesome job!!! ;)

Battery problems? No matter the rom or android version.... >>>> http://xdaforums.com/showthread.php?t=2461864
[Galaxy S II General] titanic_fanatic:
This is excellent, especially the part about rebooting after unplugging the charger. I can't remember the specifics, but it had to do with the charging cord and the source such as the wall or computer. One of the combinations caused a vbus_present wake lock which never terminated until you reboot. That is what rebooting after charging is supposed to fix. I can see the proof with gsam ;)

Thanks for that!
[Galaxy S II General] :
LOL. That's my signature. Unbelievable how many posts in the t989 section with people just saying their battery dies too fast.....and they have no idea why. I made a thread.....but it disappears down the list. So I linked it in my signature. Its easy to track down battery issues with the right tools.....and fix them, or report to the dev if its rom related. Also, people are always comparing battery life and picking roms there based on others advice. And comparing battery life is practically useless. LOL

Yeah, I charge with about 3 different cables and wall plugs....and I don't think any are my original .....so rebooting is a good idea. Also can stop the dreaded media process draining issue.....sometimes.

And greenify is really cool too! ;)

Battery problems? No matter the rom or android version.... >>>> http://xdaforums.com/showthread.php?t=2461864
[Galaxy S II General] RukusX7:
I have two cameras, two galleries, two calendars.
[Galaxy S II General] titanic_fanatic:
If you look in /system/app, do you see Gallery2.apk and GalleryGoogle.apk?

I have had similar weird things happen where it seems like my wiping/formatting didn't fully complete and left old versions of system apps. I haven't noticed it with calendar though, just the camera and Gallery I suppose because they are one in the same app.
[Galaxy S II General] RukusX7:
I'll look into it when I get home from work in a few days. Otherwise this ROM is super amazing!
[Galaxy S II General] FuryriderX:
I had 2 calendars too. Just uninstalled one with titanium backup haha. Going to try the sensor fix. Thank you!
[Galaxy S II General] formercontra:
The notification drawer has frozen like this twice. Everything still works, but the status bar only unfreezes after reboot. The second time, all the icons were gone and only the frozen bar and the wallpaper were visible.
[Galaxy S II General] RukusX7:
OK. Forget my tip on enabling kernel samepage merging to fix the lock screen.

I am currently testing an old tweak I had for Dadoes ROM. I've forced GPU rendering.

Comment out the first line in /system/lib/egl/egl.cfg using the # symbol

#0 0 android

0 1 adreno200

In same folder rename libGLES_android.so to libGLES_android.so.bak

Now edit build.prop

Change debug.composition.type=dyn to

debug.composition.type=gpu

dev.pm.dyn_samplingrate=1 to

dev.pm.gpu_samplingrate=1

Reboot a couple times.

Report back if it works. This might fix the notifications drawer issue too. I had the freeze up as well. The only reason I could see is back to the glitch Titanic_fanatic mentioned about the phone deciding between using CPU or GPU to draw the screen. So I made the decision for the phone.

Also in developer options change your animations to off or .5 to speed things up some. Seems to help with going from screen off to lock screen.

---------- Post added at 10:05 PM ---------- Previous post was at 09:36 PM ----------

So far its working for me. :)
[Galaxy S II General] titanic_fanatic:
Me too so far. I just sat here for 5 mins turning the screen on and off, and I can't get it to go black... fingers crossed ;)
[Galaxy S II General] RukusX7:
If you let it sleep, it still goes black. But comes on second click. Could try both this and kernel samepage merging together? Do you think its a ram thing?
[Galaxy S II General] FuryriderX:
I had this happen once too. Going to try the fix mentioned. Proximity and rotation work great now after downloading and inserting that .so file!
[Galaxy S II General] RukusX7:
Okay. So i reverted all my changes to stock. Then instead of changing the following line in build.prop to GPU, I used mdp.

debug.composition.type=MDP

Lock screen works a lot better. I also enabled zram for 18%.
[Galaxy S II General] FuryriderX:
So, you uncommented that line in egl.cfg, renamed the .bak file to .so, set dyn.samplingrate.GPU back to dyn.samplingrate.egl (?) and changed only debug.composition.type to MDP?
[Galaxy S II General] RukusX7:
Don't over complicate this. Lol if you made any changes revert to what it was before you changed it.
[Galaxy S II General] RukusX7:
The graphics performance is amazing! I also hit 10916 in antutu! Amazing!

The only annoyance for me is the lock screen still blanks once and a while. Comes back after only one click of button tho! Battery life should be better tho....
[Galaxy S II General] FuryriderX:
Still black screening here too. Same thought though, its rather awesome otherwise!
[Galaxy S II General] titanic_fanatic:
Yeah, and init.d actually works I just discovered. My 91fixoverlays is getting some reworking though since when it runs, SurfaceFinger is not running and consequently it fails. I'm writing a loop to check for the SurfaceFlinger, and when it finds it, it will run the command to disable HW Overlays and exit. The universal init.d app reports our kernel as not supporting it since it cannot write the test file to the sdcard on boot. Alas, we have a working init.d ;)

I'll upload the new 91fixoverlays script after I get it working just right ;)

EDIT:

I should also mention that at the top of my list for fixing is adding bln control from the settings menu, black lockscreen and stuck notification drawer. These are most annoying to me and hope I can fix them soon. Not sure where to look yet though. Will keep digging like I always do.
[Galaxy S II General] Tronith:
This is a bit ridiculous what is going on in this thread. Let's just clear this up.

One user asked multiple times the same question on our thread. Xda States to ask your questions in the appropriate forum. He was asking about stock Rom. Titanic answered without hesitation. That user asked again the question without even looking at the forum. Which again xda rules says read all posts. Then that user spams Titanic about this question in pm and again Starts demanding a solution. Titanic States after that this feature is in the s3 and s4 models and if the user wants it, he will need to reverse engineer the app himself as it isn't part of Titanic development of THiS Rom so he can no longer be bothered. I feel Titanic did more then he should for this user, and is more in the right for calling that particular user pushy.

Next a different user entirely ignores that the first user had posted 3 or four times the same question and takes titanic_fanatic 's comment as a comment to all the users on this forum. When it was actually intended to the one. This same user has also been rude to the developers in the original dadoes Rom fourm as well as the other roms for our device only causing tension on our forums instead of support. So ignore the hater.

Titanic I agree that this IS a beta and you can add that to the description if you want, but it is definitely not an alpha build. Alpha means only a few features work and this Rom couldn't be used as a Daly driver. The github post you shared earlier showed that the kit Kat is currently in alpha as their launcher, phone app, and something else didn't transfer over and needs to be redone. The is alpha as it cannot be used yet. So no more bashing on Titanic. The user who can't speak English got his answer multiple times so no need to respond to that anymore, and ignore the trouble maker.

I enjoy using this forum. I respect Titanic who not only works on this Rom but is actively speaking with us so we know what is happening. He makes this feel like a good community. (minus a few bad eggs :p)

Let's all work together :)
[Galaxy S II General] RukusX7:
I have very little issue with this rom that would suggest I would not recommend it as a daily driver. With a clean flash, properly installed,

I get 12 hours average use.

I cannot remember one force close of ANY app I use.

I have had a reboot when changing governors. Smartassv2 does not work for me (stays at 1512 MHz) So if you were a novice user and didn't mess with any perofrmance settings, youd be fine.

The lock screen is slow from returning from sleep.

Sometimes I can't see the unlock icon, if you swipe anyway, it works.

Sometimes my messaging app gets confused if i turn the phone sideways. I just exit out and back in. no biggy.

The rom is snappy, its fast, and DEFINITELY VERY useful. To suggest alpha would be an understatement. At very least I'd list as beta. It's hard for titanic_fanatic to judge where the rom is going, as he is building from someone elses developed code as they improve on it. As new fixes and features are released, he is much much better off working on what the CM team is working on, as I imagine he isn't able to anticipate their next step.

The goal tf has made obvious whilist building his roms, is for the rom to be a daily driver, He has even held off on releasing rom versions with the fear it could not live up to that goal!

This is great work tf and i appreciate where you ahve taken our phone!
[Galaxy S II General] formercontra:
Is there a way to disable boostpulse in the system? [MENTION=3478918]rukusx7[/MENTION] you asked Strange Peer to disable it a while ago. I tried manually changing it to 0 in /sys/devices/system/cpu/cpufreq/ondemand, but it wouldn't save the change. I end up rebooting so many times, the switching to interactive and back fix wouldn't be much help.
[Galaxy S II General] JimbobDobalina:
Thanks again for your help in suggesting some apps for tracking down the battery fault - it appears that the launcher I am using is causing the issue - I was using the GO launcher EX, which I wasn't using on my previous ROM. In the battery stats it is showing up using 50% of the battery life of all the apps on my phone. It is running a download service that must be waking the phone for some reason, and using LTE it appears to be chewing my battery. I have uninstalled it, and will try the phone with the stock launcher for a bit.

Screen brightness appears to be an issue as well - I run it on auto brightness, but it shows up being on max 90% of the time - I am pretty sure I could cut that back. Is there a way to limit the max brightness that the auto setting will go to?

I also wanted to say that apart from the battery life, the rest of this release is definitely a daily driver for me - I haven't had a crash or force close in the 5 days I've had it running.

Cheers for your effort.
[Galaxy S II General] titanic_fanatic:
I too use go launcher, however, mine is only consuming about 30%. It's high, but I like go launcher. Did you have the 3d engine turned on. That will eat through your battery like there's no tomorrow. I keep that turned off.

For brightness, I have mine always set at about 30% while inside and turn it up to 75% while outside (unless it's dark outside). It's easy to change with the time in the quick settings menu and can be done from mostly any app as long as you have access to your status bar.

I couldn't use the auto brightness because it'a performance is so random to me and didn't seem to make it easier to read my screen rather it made it more difficult since my eyes constantly had to adjust to the changes ;)

EDIT:

When I figure out when and where these values are changed, I'm going to build in some system settings to allow the user to manage them.
[Galaxy S II General] JimbobDobalina:
Ah, I did not know that the 3d setting would kill battery, I had that on.

I found a widget called 2way Brightness that just toggles between custom brightness levels. That should help.
[Galaxy S II General] wmgreig:
Statement of Appreciation

I'd just like to add my $0.02 to the forum in support of the awesome work that Titanic continues to do with our S2. For a noob like myself, this forum has been both a revelation and an education. I've been running the Slimbean ROM for some time now and have been pretty happy with it. I'm stoked about the new ROM and figure it's time to take the plunge. The feedback and support here is outstanding.

Also, I have to say that the respect shown on this thread is commendable. Titanic....you lead the way with your patience and tact. You're not just a talented developer, you're a good human being. Many thanks :highfive:
[Galaxy S II General] bitwarrior1:
I think I spoke to soon on the bluetooth issues being resolved. The bluetooth is still crashing when trying to play audio through the car radio with poweramp and doggcatcher. It doesn't happen every time, but after connecting the app shows as playing but no sound from the radio or the car speaker, then bluetooth fails with an ANR for com.android.bluetooth and won't turn on until reboot. It then works once, and the behaviour repeats when I reconnect my phone. I managed to catch a log, which is attached