yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] ulbonado:
Two issues

I have two issues, both of which have been present through the last few builds, which I haven't seen anyone else mention.

1) I have "Keep Wi-Fi on during sleep" set to "Only when plugged in". However, the wifi turns off during sleep, even if it is plugged in. The phone knows it is plugged in-- the battery icon turns green, the status on the lockscreen says "charging" etc.

2) Bluetooth occasionally crashes. I've actually never had a problem with it while there was an active connection. But occasionally when Bluetooth is on but idle/unconnected, I see the icon disappear and then re-appear. This always causes the current network connection (whether wifi or 3G) to reset too (icon goes grey/white, and shortly turns blue again as it restarts). This is occasionally accompanied by a dialog saying something about Bluetooth system has unexpectedly stopped or the like (the usual FC dialog), but not always.

Anybody else seen these?
[Captivate Android Development] prbassplayer:
Re: [ROM][4.2.2]SlimBean -I897- [Build 3.0][March 29 2013]

Well 1st I always run mine on, as a matter of fact I use pmfast on semaphore. Second makes me think it's kernel related as its making all 3 network type crash. I don't use by much on my captivate except to test. I'll try it when I'm home, however if you can grab log cats and cat ksmg while error occurs would help greatly. Stupid question have clean flashed?
[Captivate Android Development] RickHenry:
My mistake, I assumed it was included.

Awesome ROM, thanks for all your hard work and great support.
[Captivate Android Development] RashaMatt:
Thank you for the ROM. Looks beautiful, and behaves great - for the first hour. Then it becomes unbeLIEVably laggy until it's rebooted, just like all the other JB ROMs I've tried.

It seems I will have to go all the way back to GB to find a ROM that works well on my Cappy for more than an hour or two :(
[Captivate Android Development] m1batt1:
Have you tried changing kernel settings on this or any other jb you've tried?

In my experience every ROM is a little laggy until I change the governor and I/O settings.
[Captivate Android Development] Kyuta Syuko:
I've had that issue on almost every JB ROM I've tried except this one. I would recommend doing a full wipe install and using Semaphore 2.9.0, getting Semaphore manager, and tweaking the settings.
[Captivate Android Development] grndnl:
What settings are people trying that are working?
[Captivate Android Development] athdaraxen:
For the past few days (and working well) is SmartassV2 and ROW. Its been my favorite combo so far.

Edit: 1024 read ahead and LiveOC at 110%

:3
[Captivate Android Development] prbassplayer:
Smsrtass V2 and row with 1024 read ahead.

Cheers

Also 116% live OC
[Captivate Android Development] RickHenry:
smartassV2 and No-Op has been working well. I will give ROW a try based on the above recommendations.

---------- Post added at 11:54 AM ---------- Previous post was at 11:47 AM ----------

I did have issues with deep idle, however. Cappy would not come back from it, requiring a battery pull.
[Captivate Android Development] athdaraxen:
That happens with me too when I try to play with Deep Idle. It always requires a battery pull, no matter what settings I change or don't change. :3
[Captivate Android Development] m1batt1:
I'm a smartassv2 (with smooth ui enabled) and noop fan.

I don't over clock at all because my phone has never responded well to it. So I'm just running at 100% without lag.
[Captivate Android Development] athdaraxen:
I over clocked mine mostly out of curiosity from the dude who posted earlier with the magical battery life, I wanted to see if overclocking would improve my battery life as it did his, I just changed it this morning so I'm gonna wait before saying anything as to it working or not.
[Captivate Android Development] BWolf56:
OC is usually harder on your battery unless it is mixed with some UV.
[Captivate Android Development] prbassplayer:
I tend to disagree. Voltage doesn't usually affect battery life as much as you think.
[Captivate Android Development] athdaraxen:
I was talking about this guy, he stated all he did was use smartassv2 and OC to 120%. I've never really dabbled with OC but after seeing that I figured it was worth trying. I mean no matter what ROM I use the most I've ever gotten is 7-8 hours and that's with little use.

Its been better with this ROM but I can lose up to 10% within 45 mins. Its crazy so always looking for new ways to save battery.
[Captivate Android Development] prbassplayer:
Chase your kernel wakelocks, freeze apps you don't use (like Maps and DRM) :)
[Captivate Android Development] athdaraxen:
I didn't check the wake lock and I feel kinda dumb for not thinking of freezing apps. I completely forgot I could do that. Derp.

I will say this ROM gives me the best battery life by far. I know Maps is killing me but I actually was using it but I forgot to kill it.

Just to throw this up here...

http://db.tt/piCkHrd9

http://db.tt/eTg2VDLs

Thank you for the advice, I'm sure it'll help!
[Captivate Android Development] Kyuta Syuko:
I've been using SmartAssV2 and SIO, but after doing some research on ROW (I'm guessing it stands for Read Over Write since that's what it does?) I'm going to give that a try myself. Also have SD Read Ahead set to 512, but I don't use it that much anymore since I now keep all my apps on my phone.

On another note my battery life does seem a little shorter on Beta 1 then it did on 3.1, but only by an hour or so.
[Captivate Android Development] grndnl:
Does anyone have any opinion on this: http://xdaforums.com/showthread.php?t=1987032 ?

Tried the apk, and it seems pretty great as of now, i'm not going to lie.
[Captivate Android Development] prbassplayer:
Don't know but will take a look at it later.

Sent from my Slim Bean Beta 2 powered Nexus 4
[Captivate Android Development] athdaraxen:
That seems amazing, I definitely want to give it a shot, eventually.

Also, I figured out it was Google Talk destroying my battery. Uninstalled it and I've seen a 3% decrease in battery over an hour instead of 7-10%. Thanks again for the advice.
[Captivate Android Development] Kyuta Syuko:
I've actually had issue 2 happen to me a few times. Usually it happened after my phone reboots from bad OC Voltages (noticed the stock ones are a bit... messed up...).
[Captivate Android Development] Tsaukpaetra:
I have seen this happen during an OOM condition. I was visiting a CPU-hogging website (Bug in the browser I've been hunting forever, something to do with a render loop on certain CSS-heavy sites), when a monitoring program I use (Usage Timelines) vanished, and shortly after much of the SystemUI had to restart as well.
[Captivate Android Development] ulbonado:
I'll try to get a logcat if I can recreate it. It was a clean flash to 2.5 and then an upgrade to 3.0. But the problem occurred on 2.5 as well.
[Captivate Android Development] bradddo:
Wow, no other posts in a couple days. That's a good sign. Great ROM
[Captivate Android Development] prbassplayer:
psh SlimBean is epic :p. I haven't been able to recreate the bt problem on my end so duno.
[Captivate Android Development] ngochuy:
So happy with this build :)
[Captivate Android Development] whisky23:
Can't speak for issue#2 since I rarely use bluetooth, but I'm definitely experiencing issue#1. Clean installed from 2.5. Once I shut down the screen, it takes a minute or so for the wifi to go to sleep, showing up grey when I turn on the screen again. WIFI is shown as connected though, under settings immediate after switching on the screen. Settings-wise, WIFI is set to always on during sleep, PM Fast off.Even tried to switch off Wifi optimization, but same results. Did not encounter this issue in previous builds.

Update: Problem seems to be intermittent. Now it's acting normally. Not sure what's going on.
[Captivate Android Development] RickHenry:
On issue 1, I keep Wi-Fi on all the time so don't know. Still get phenomenal battery life, so see no need to turn it off.

On issue 2, I have never seen this and use bt extensively with several pairings. I keep a Jambox connected to my Cappy for hours at a time playing music. Likewise connected to Sync in my car for hours at a time. Never had it go away on its own or fail to make the bt connection.

Are you maybe pushing OC or UV? I have sometimes seen where pushing the hardware a little too far causes sporadic issues like this.
[Captivate Android Development] ulbonado:
I may just do the same. Although I wouldn't describe my battery life as phenomenal, my battery is getting old.

My BT doesn't ever seem to crap out when I'm actually using it. I use it for music in the car, and it works fine. It's when I'm doing something else on the phone, mostly web browsing or reading in feedly, that sometimes I just notice the icon disappearing and reappearing, and occasionally the failure dialog. This is accompanied by the other network icons (wifi or 3G) turning grey and then back to blue. If it happens at just the wrong moment, Feedly will crash, probably because it doesn't handle the network disappearing very well.

Also, no, I'm neither OCing or UV at all. Default settings all around.

Sorry that I haven't had a chance to capture a logcat, hopefully I'll get some time to figure that out shortly (I haven't needed to do it before).
[Captivate Android Development] Val D.:
Just to share some experience - I use Nick0703's unofficial kernel (mainly because of In-Call Volume settings) and I have noticed on my phone that Slim runs MUCH faster with zRam disabled (default 18%). All apps open/close instantly, UI is buttery smooth, scrolling contacts/messages is a pleasure. Also, with zRam disabled I can step OC up to 1400 without any stability issues (1350mV, >48h testing). If I restore zRam setting to default 18% the phone gets laggy and often reboots shortly after (in 30min).

:victory:
[Captivate Android Development] bobo122:
i faced a problem for the second time ever last night (the first time was a week / 2 weeks ago i can't remember) , the problem is that the phone shuts down by itself ("complete shut down" , not a reboot) . both times happened while i'm sleeping and the cellphone connected to the charger. when i woke up it was in charging mode (battery on the screen) , when i unplugged it from the charger and turned it on , it worked just fine.

any ideas ? i'm using unofficial semaphore with 120% live oc if that makes any difference but i've been using it that way for quite a while now
[Captivate Android Development] prbassplayer:
I'd be willing to bet oc instability.
[Captivate Android Development] diakonos:
I tried to live OC to 106% and it kept rebooting to Recovery. No OC or UV for me. :-\

Sent from my SGH-I897
[Captivate Android Development] Val D.:
Don't UV when trying to OC, especially close to the limits. Just the opposite, you need to OV to fight stability issues.
[Captivate Android Development] mattytom87:
Hey guys I think I flashed without thinking:/ My girl broke her GS2 so I decided to update her phone. It was on a version of serindipity and I'm not sure which one it was (I know my dumb @$$ fault) I flashed Slimbean and got it up and running but I can't get a signal, there is no APN choices and I have lost my IMEI...I tried restoring the efs folder but could not recover my IMEI still...I also tried restoring a backup I made right before flashing and it keeps failing, now the phone is stuck at the at&t boot screen...Just wondering what my next move should be. Thanks all

Edit: I can't get into recovery but I can get into download mode...should I just odin to get back to stock??
[Captivate Android Development] prbassplayer:
Odin semaphore. Get in recovery and flash a baseband...
[Captivate Android Development] Val D.:
This question is not Slim ROM related, but one way to get what you want is to go back to stock (Odin, to restore IMEI), than flash Corn kernel (Odin, to root and get CWM), than flash CM10 (in CWM, to get right file system), than go to Slim (in CWM, or whatever you want CM10 based). This is a long way but gives constant positive results (to restore IMEI). :)
[Captivate Android Development] yaibakt:
this is the best way (IMO) to "reset" a messy phone after flashing so many roms and finally decide to choose one of them :D

i did the same with my wife's cappy and its been working great now on slim bean. :)
[Captivate Android Development] Val D.:
It is probably, but requires a lot of reading and strong nerves. First two steps often lead to soft bricked phone if not done properly. Been there, done that... :D
[Captivate Android Development] Kyuta Syuko:
Just so you know SlimBean doesn't come with a modem so you'll probably have to flash one if you're coming from stock.
[Captivate Android Development] Val D.:
He has to flash CM10 first to create correct file system, good working I9000UGKG3 modem comes with it.
[Captivate Android Development] prbassplayer:
He can Odin kernel get in recovery and just flash modem. Slim partitions just lacks modem.
[Captivate Android Development] RashaMatt:
ON Slim-4.2.1-stable-OFFICIAL

it's stuck on auto - brightness. I take it off auto, but it's still auto :-\
[Captivate Android Development] prbassplayer:
Well first this thread has moved to 4.2.2. Are you sure you don't have semaphore auto brightness enabled?
[Captivate Android Development] soumian:
Hey, i've been having this issue where some games are playing nice and suddenly it starts to freeze and i even get the non responding pop-up with wait report or close options.sometimes. It's really annoying, i thought it was because i had too much going on and in the background and when a process was restarting itself my phone froze but i'm not really sure. This has been on at least the last 3 or 4 builds. So any insight there will be appreciated.

Also i decided to do a logcat to see if i could get some info from there (BTW i'm not familiar with this things) but the logcat app just sits there and doesn't show anything so now i have another problem, again any ideas here?
[Captivate Android Development] Kyuta Syuko:
Do you have logging turned on in the Semaphore Manager app?
[Captivate Android Development] soumian:
Well I had already tried it but apparently I had to reboot to get it working. Thanks for the suggestion, hope I find what's causing this horrible lag.
[Captivate Android Development] Gatech:
Volume of music, notifications, etc is too LOW on Cappy with this ROM. Do you know how to get higher volumes?.

* Chrome works very bad, it crashes sometimes.

* I created a Swap partition on SD Card, but if it's on the phone during boot, it never boots (keeps on slim loading screen). :S
[Captivate Android Development] Val D.:
For Music/Headphones - adjust Amplifier Level in DSP Manager/WM8994 from default -10db to 2db (or use Voodoo Sound app from the Market)

For Speakerphone/In-Call Volume - use Nick0703's Unofficial Semaphore kernel, Settings>Advanced>In-Call Volume Controls (default settings are good)

For Ringer/Notifications - I don't see any differences compared to other ROMs, same volume levels. Ascending ringtone works as expected too.

Chrome crashes on other ROMs too. I don't think this issue is ROM related. I had similar experience with Chrome and now I'm using default browser. Not a big difference.

Swap partition won't give you any speed gains. SD cards are too slow for this purpose.
[Captivate Android Development] prbassplayer:
Also if memory servers Semaphore doesn't support swap partitions.
[Captivate Android Development] RashaMatt:
Oh crap, that was it. I have so many devices, all with different ROMs, I can't keep track of all these options :-\ Third world problems for sure...
[Captivate Android Development] soumian:
Hello again, i was expecting some answers from the users too. Do you guys notice any lag while playing games? From the logcat i got that a lot of processes close and i mean almost every process or app running in the background. Is this normal? Because i think that when all this processes restart my game lags.

This Logcat scares the crap out of me, theres too much going on and a lot of thing i do not understand obviously so if anyone wants to check it out and tell me if something wrong is going on i'll attach the link to the file. I basically cleared the log, then open Muffin Knight, played for 4 minutes more or less, exit the game, open LogCat and saved the log.

https://www.dropbox.com/s/v74ej7lvvme3364/alogcat.2013-04-11-21-33-53-0300.txt

If this is too off-topic please let me know and i'll delete the post from this thread.

EDIT: almost forgot to ask, whats going on with TapJoy. Does anyone know what app is causing all that fuss in there so i can just uninstall or prevent from doing all that?
[Captivate Android Development] m1batt1:
Ok so first off for anyone reading this out of context... the quoted text above is the commands needs to compile Slim from source after initializing a build environment.

So for PrBassPlayer,,, I've tried a couple different products from compiling and I end up with the same result. The zip appears to build without issue but when I flash I get stuck in a bootloop that doesn't allow me to boot back into recovery.

The first time I Odined the latest Semaphore and it booted without issue, and thought I had synced something wrong so I deleted and reinitialized the repo and rebuilt using the same commands. Unfortunately I've consistently ended up with the same issue. With the build I've compiled it won't boot but when I odin an official copy of Semaphore it boots without problem.

Any ideas?
[Captivate Android Development] prbassplayer:
This was taken while playing a game. Unity is the graphics engine, nothing we can do about it. Tapjoy is probably being used by the app for ads or tracking your infor, again nothing I can do about it. Facebook, obviosuly nothing we can do. Crap about talk and download error out is probably because game is blocking OR game uses up to much resource and doesn't let it work. Dalvik is normal usage, on heavy use dalvik works more. Not much we can do for old devices and games that aren't exactly well made, or just aren't meant to run on older devices.
[Captivate Android Development] RonH54:
Is there an area to change the DPI on ROM? I thought there was an LCD setting somewhere but I am just can't remember where it is.

Thx
[Captivate Android Development] RickHenry:
Settings/interface/General/LCD density
[Captivate Android Development] basily:
Looks like this will be a final build... is that the case?
[Captivate Android Development] prbassplayer:
Lol no. Why?
[Captivate Android Development] prbassplayer:
I missed this. Well what other devices don't work? If just captivate try this

cd kernel/samsung/ics-ramdisk

tar zxvf jb_combo_c.tar.gz

cd ../../../

Follow the build commands again. Could be missing modules from kernel.
[Captivate Android Development] basily:
Because the updates were coming lightening fast, and now we've been on 3 for a while. Or maybe time has just slowed down because I am currently living in hell... (nothing to do with the phone or rom, I continue to love them).
[Captivate Android Development] prbassplayer:
Been on 3 for exactly 2 weeks lol. We wheren't able to keep up with our bi-weekly release this time. All of us had busy weeks and we couldn't merit a release with the little bit done. ;)
[Captivate Android Development] m1batt1:
I don't know if any other devices are working or not I don't have any other devices to test on.

I tried running commands above and recompiling and I'm still stuck on the Semaphore splash screen.
[Captivate Android Development] prbassplayer:
Compare zips? Libs and vendor.
[Captivate Android Development] prbassplayer:
Can you get logcat? Did you make install clean or make clean before make -j4?
[Captivate Android Development] m1batt1:
I did not make clean. However I am running a clean build right now and I'll report back on that in a couple hours.

As far as logcats are concerned I don't think I can get one from the phones current state. As it stands I can't access recovery nor get it to boot. All I can do is get into download mode where I can flash Semaphore via odin. Once I flash that I boot without problem so I would think any logcats at that point wouldn't be of any help.

Edit: OK so I did a clean build and also left out the "export LOCALVERSION="-Semaphore_2.9.21sc" " line. This time it built, installed, and booted without problem.

One thing I did notice comparing the zip that worked to the one that didn't is the working one was about 5mb larger so clearly something was getting left out.
[Captivate Android Development] ctechbob:
Overall the rom is great, just the one little issue that I wanted to bring back up to the front in case someone had the same thing and fixed it or the devs needed to know about it.

After the phone has been up and running for a while (say a day or so) certain programs will close as if they're being killed from memory. The two that do it most for me are Trillian and the music player. Its not a force close and it doesn't appear to be a crash, it looks like it is just the os saying 'I need your memory for something else' and terminating them. You can restart the program and it will continue on fine, but the longer the phone is up, the more often it happens. If you reboot, it will stay up longer than if the phone has been up for a while.

Thanks all for the excellent Rom!
[Captivate Android Development] prbassplayer:
Try sharing 300MB of ram with apps that are being design for 800MB+. Try messing with lmk.
[Captivate Android Development] prbassplayer:
Kernel modules that weren't decompressed in ics-ramdisk. The local version export handles the kernel version seen in about phone, that's it.
[Captivate Android Development] lavero.burgos:
ES File Explorer does that a lot but when I open it again it is right where it was left.

2 other apps have done that too but not often and one of the is the stock browser or dolphin browser I don't remember maybe both Lol. But overall ROM performs well. Thanks to the devS

Enviado desde mi SGH-I897 usando Tapatalk 2
[Captivate Android Development] Tsaukpaetra:
Speaking of browser issues, I often notice this behavior (and the one where bluetooth/data/etc force closes) when I'm viewing certain websites. These websites resize down (they're supposed to be mobile compatible), but I think something weird going on in the CSS parser causes increasing levels of CPU usage as the user scrolls down the page until the browser locks up and things start getting closed.
[Captivate Android Development] Val D.:
Absolutely normal Android OS behavior, not ROM related.

When more RAM is needed, inactive apps are hibernated (not terminated). When you reopen them you'll see the last screen where you left the app.
[Captivate Android Development] lavero.burgos:
I get the wait popup with browsers too
[Captivate Android Development] ctechbob:
I could see that being the case with Trillian since it's not doing much sitting there, but for a media player actively playing music in the background, notsomuch. Unless the memory management has changed in JB. Wasn't an issue on the various GB and ICS roms I've used. I don't remember if it was an issue with Helly, life has been a little overwhelming lately so my memory from back in Jan is foggy.
[Captivate Android Development] Val D.:
OS will never close active application. Playing music on background is still an active application.

I never had issues with Android memory management, on any OS version from Froyo to Jelly Bean.
[Captivate Android Development] prbassplayer:
Are you messing with oc and/or voltage?
[Captivate Android Development] cannondaleV2000:
Delete
[Captivate Android Development] Kyuta Syuko:
I've had that happen to me on other custom ROMs (and I think it might have happened a few times on Slim as well) where I had my music playing but the app was in the background while I was doing something else on my phone and it got terminated. I've also had instances where Play Music would sort of hang at the end of a song sometimes. What I mean by that is Play Music would finish playing the song and there'd be silence, but Play Music would act like it's still playing the song till I hit Pause/Play or Next Track.