yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
Thanks for this guys. Just to clarify for everybody, I'm very aware of the video issues and have been able to reliably reproduce them on my own. The build I'm running right now, which will be build 4.2 (out today -- for all devices) contains fixes for it & a few other improvements. I'll have a more elaborate post on it when we release, but I just thought everyone should get a heads up that we're working towards a fix.

Since the switch to the 3.4 kernel, CM has been merging in a ton of CAF commits so you'll see very rapid development likely until Keylime Pie hits. For better or worse, you know the drill... ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I was hoping to try your slim kernel on other ROMs but none of the governors seemed to hotplug. Is this expected using your kernel on other ROMS or is there something else I can look into to try them out?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oriveradel:
A link would be nice?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Just look in the CM thread. Its in one of the last couple pages. Searching is nice. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
What other stuff did it break? I'm just curious. I never got a chance to try it out today. WAYY too busy with classes. We've got a 204 student class this week and next :banghead::banghead:

:thumbup::D:thumbup::beer::beer:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crakerjac:
Is this new? I had Bluetooth issues a while back on most of the SlimBean versions. I would get a lot of static on my Bluetooth headset. I found that if I upped the CPU voltages by 75mV across the board, everything would work fine. No blips, no static, just the audio I expect to hear.

I assume that the Bluetooth radio draws enough current that when we under volt the CPU, there isn't enough current for the radio to work properly. Just my theory.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpride:
Does this ROM support OC and Under(or Over) Volting?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crakerjac:
Should have mentioned that I'm running the ktoonsez kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpride:
How is Battery Life with this ROM and that kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

First wanna give a thanks for this great beta running for couple days its great enjoy the new features.... Just finally found out how to get to developer options lol.... One quick question how do I change the way the screen shuts off when I hit the power button ( get ride of the screen fade white line thing )?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zzmomo73:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

Unless u edit some files in the framework or something, I don't think there is a way.. I know there's an app on the play store which allows you to change that animation but I forgot its name.

Edit: it's called screen off and lock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

Thanks but on my skyrocket if u change the value for one of the scale option in developer tools from like .5x to 1 or I think but I tried all three and no solution, I'm a noon so I won't go change any scripts unless clear directions, not to mess anything up thanks for info
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] testsubject00001:
4.2.1 RC 1 is out!

4.2.1 RC 1 is out for other devices just not ours, so it should be up sometime soon hopefully :) Hitting refresh like i have OCD

Update: Its out downloading now thanks for making my day and all your hard work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrMarkEdward:
downloading RC1 and the inverted addons
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] finneginsfast:
Anyone comment on bluetooth functionality for RC1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crewzta:
Does RC1 have a working camera/photosphere?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

New build is great. Crazy smooth and stable as always. Only strange thing I've noticed is when you open an app, there's no background until the open animation is complete.

I managed to get a screenshot as it might be difficult to describe what I'm talking about lol it wasn't easy

Could be an issue with ktoonsez kernel or the real dark slim gapps but either way still the best 4.2 ROM out there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrMarkEdward:
Dont have this issue and using kt kernal and dark slim apps. I would suggest a full clean install. I never dirty flash and never end up with problems resulting from dirty flashes. And yes SlimRom is very smooth and fast.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] finneginsfast:
First things I've noticed so far are that i/o schedulers are still not sticking and the brightness slider on the status bar isn't working (for me at least) after clean install. Short trial with bluetooth seems to work though...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zild8:
This is my best rom!!!!! MIssing the 8 lockscreen shortcut!

Someting that i found strange is that when you wake up the phone you have to press on the lock and press again for the slider shorcut.

I think before it was not like that and probably better in my opignion

Thank to the slim beam team:laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

Which dark slim gapps did you flash? I flashed the ones from this page http://www.slimroms.net/index.php/downloads/all/viewcategory/204-addons-inverted-full-packages

And it was a clean install
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anilrawal:
USB & NO charhing when powered off

I have tried bot the kernels, the default bundled with 4.1 and KT and the issue is there on both.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] droid_funktionz:
browser force closes on 1st open

I am not sure if its been mentioned but I am getting fairly consistent force closes with the browser the first time I try to open it. It basically just closes out while its opening. It works fine when I go back and try the second time. I am using the latest BMS kernel so I'm not 100% its ROM related just figured I'd mention it. Other than that I am loving the new build and all the new features. Love that blacklist for those pesky collectors!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Vortex1969:
I have seen this to on my sister in law s3 and it is also happening on my wife's N4.

Going to try and get a logcat off her phone tonight.

Still a great rom:thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zzmomo73:
Is fast charge enabled by default? I can't seem to find an option to turn it on
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
The default kernel does not have fast charge (based on CM kernel). Try blk_Jack's add on kernel which does, among other tasty treats.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zzmomo73:
My apologies, I am using blk_Jack's kernel. Was just wondering if blk_Jack's kernel has fast charge enabled or not. Judging by the charging speed I would think it is, but I'm not sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Yes. You wouldn't be able to add the quick setting for it if your kernel didn't support it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brettchuck:
I seem to have an issue connecting to the internet unless I have a wi-fi connection. My phone signal bars are gray with not indication of 3g or 4g. My phone works fine for calls and text messages. As soon as I have a wi-fi connections, it's signal bars and the phone signal bars turn blue. I've tried different modems and still doesn't make a difference. I have reloaded the roms with full wipe two times and even fixed permissions.

Any ideas of what I might have missed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
I guess the issues most r having isnt universal I have no one of these bugs or issues using blkjacks kernel so I'm kinda gunna wait and not update to build 4.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brettchuck:
Always bugs but when they get it figured out like last build..it's the best ROM!! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] droid_funktionz:
Might wanna check and make sure you still have your IMEI number. I lost mine a while back on a random flash(not sure why it happens) and had to go through quite a few steps to restore it. Also check your apn. Mine usually reverts back the old cingular apn after a new flash then i have to change it manually to the LTE apn.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zzmomo73:
Build 4.2 out?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dcoulombe:
Touchkey light timeout ?

Hi,

When I play with System Settings -> Interface -> Display -> Touchkey light timeout, it seems that the 2 seconds and 1 second are not working properly (either one are giving me a 5s delay). Every other options are working properly (Always On, Always Off, 10 seconds and 5 seconds).

I'm running build 4.1 with the add-on kernel from blk_jack (from here : http://xdaforums.com/showpost.php?p=40526077&postcount=1725).

Great job on this wonderful ROM !

EDIT: Same thing with build 4.2, as expected (well, build 4.2 went public while I was typing the original message...)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brettchuck:
My IMEI number is there but where do I check the APN.

---------- Post added at 12:17 AM ---------- Previous post was at 12:11 AM ----------

Never mind...brain fart..I found it and it was set to the normal Cingular setting. Once I get off of a phone call, ill set it to the LTE one and try that.

Thanks for the inside!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Running on 4.0 not a single error literally abs nothing!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
SlimBean 4.2.2 build 4.2

We've added half a dozen new features and fixed quite a few other minor issues, which should hold us over until build 5. There was a major issue with video playback in build 4.1 that we have (hopefully) squashed with build 4.2, and that alone makes the upgrade worthwhile!

You do not need to wipe between minor update releases. buuut if you do have problems full wipe, reproduce & report appropriately ;)

Changes:

Update to JDQ39E

Added Music Playback Control Tile

Added Developer option for MediaScanner Behavior Control on Boot

Added TextArea size to Mms

Enhanced Auto-Brightness UI

Updated PlayStore to v4.0.26

Fixes:

Fixed issue with reboot on video playback

Fixed Translation issues [Spanish/Italian/Polish/Chinese/French]

Fixed SlimSizer FC

Fixed BlackList button behavior

Fixed NavBar menu hidden on softkey devices

Fixed SlimIRC bugs

Fixed DashClock extension icons hidden when minimized

Fixed PIN entry disabled by some apps

- Download build 4.2

Once again here's the build 4.2 addon kernel. It's actually the same as the build 4.1 kernel and since nothing has changed..:

Addon kernel:

Latest CM changes as of 04/22

Minimum 192mhz frequency

Added governors: wheatley, lulzactive, dancedance

USB fastcharge

Vibration control (Settings -> Performance -> Vibration Strength)

Faux sound control

morfic/trinity colors

It's a kernel for people who don't want anything too fancy, just a little something extra.

- Download build 4.2 addon kernel

The source is on my github here. Thanks to ktoonsez and GideonX!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dcoulombe:
I have massive screen flashing/flickering with Swiftkey on the newest 4.2 build. It goes away when enabling this option :

System settings -> Developer options -> Disable HW overlays.

Android Keyboard (AOSP) doesn't seems to have this problem, even with the Disable HW overlays option unchecked.

People over at CM10.1 forum have the same issue : http://xdaforums.com/showpost.php?p=40552492&postcount=13005
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
This is an upstream issue and seems to only (mostly?) affect swiftkey while not typing with it.

A more permanent way to get rid of the flicker is to add:

debug.mdpcomp.maxlayer=2 to your /system/build.prop

Beware, though, it may introduce other issues. YMMV.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dcoulombe:
Correct. I switched to Android Keyboard (AOSP) for now as this one works normally. I'm sure this will be fixed soon.

Great work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
What's a good file manager for slimroms in order to be able to edit system files?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] momyc:
Same issue here. It happened after 4.2 build update. It doesn't do it on build 4. Yes, I have swiftkey .

Should I wait for a fix or move back to build 4 ?

Thanks,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dcoulombe:
I use ES File Explorer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
2 fixes are mentioned on the previous page. 4 has a few other issues and is incompatible with any new kernel, upgrading is highly recommended.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] momyc:
Hi again,

I saw the 2 options and I applied "Disable HW overlays" .So far so good. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
Loving the new releases although my battery life has taken a pretty big hit
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
Battery life has increased a lot since the first 4.2.2 build. No idea what you're doing but I'm getting great battery life with build 4.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Battery life is about as good as I've ever seen at this point.... and seems to be getting better all the time. You should try and find what is hitting that battery... it's not 4.2.

---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------

Check out X-plore. It's free and it's awesome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
I'll give it a couple days being that I'm on a clean install don't really have anything installed except xda
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Make sure u do couple full charges after flashing... I'm on 4.0 battery seems normal
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
GSAM battery monitor can tell you exactly where your battery is being used. It takes away the guessing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Djspinister:
I think it was about 3 or 4 releases ago I did a battery test on this ROM and it was excellent. Since then it has gone a bit downhill (haven't tested this one yet) but they are all still better than any of the other ROMS out there in my opinion. I tried different kernels and that was a joke, not even close. Especially the fact that they say they are based around battery life. Anyways, I would suggest a reflash and make sure you do it clean, then calibrate your battery and you should be good. I have the extended battery 4400 mah, and I have GPS on nearly all day (delivery driver) and I still have about 25-35% when I get home. Good luck!

sent from my Slim'd S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bustedwings:
Build 4.2 openpdroid patches

http://db.tt/NT6ntdMo

Included stock MMS.apk just in case patched one doesn't show up in launcher
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
Am I missing something I have slim pie enabled and have the option to show time check marked but it still does not show even after toggling it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Are you talking about in the status bar? You gotta UN check it

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
I mean when when pie is swiped to show my short cuts it does not show the time any longer with my shortcuts as it did at first
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Software Guy:
The issue with the display time out that I had posted previously is related to my arliberator software not the slim rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] voidstab:
I had to switch keyboards but I'm also getting crazy flicker with exchange email without any keyboard showing. What is better, disable hardware overlays or edit the build.prop, what are the other issues that may introduce?

edit*

Could this be the result of a dirty flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Disabling the overlays you would have to do after every boot. The other option is a more permanent fix that does the same thing.

Exchange is working fine for me and yours is the first report I've read of it, so I think its safe to say the issue is just you.

As general practice, if you have problems, try searching the thread to see if others have already reported an issue. If you don't see anything, you should try a clean flash and run everything stock. If the issue persists, report the issue attaching relevant information like a last_kmsg or logcat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] voidstab:
I quoted the only relevant post I saw. I wanted to know if it was a known issue because I didn't want to reflash if it was.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
No flicker for me on 4.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] momyc:
Just to point out that neither for me on build 4.0 , but yes on 4.2.

I did the Disable HW thing and it's ok , but I understood that I have to do it after each reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
I have not seen any flicker issues on any of the new builds. I don't use exchange, but swiftkey is my default keyboard.

I am using blk_jack's addon kernel with the default settings, other than setting min freq down to 192.

I did a clean install back on build 3, and have been dirty flashing (just clearing cache and dalvik) since then.

If you have not done a full wipe, reinstall from play store (not tb), recently it might be worth the effort to get a clean slate. I have something on the order of 140 apps, and 4.2 is rock solid, with no issues, no force closes, no reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SolidSnake33:
I did a clean install, no more dirty dirty this time, and I'm getting flicker. Mostly using Swype or the aosp keyboard.

Sent From My Slim Galaxy S3

Slim Bean 4.2.2 Build 3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dcoulombe:
Unfortunately, I deinstalled Swiftkey, then I reinstalled from play store. It still flickers. I will do a full wipe, clean flash and report back when I get some time...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Judman:
Flicker Fix

Worked for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
No flicker on my end, swiftkey installed... Perhaps the ones that are getting bad flicker should wipe and start clean fresh install? And install Swiftkey from playstore instead of a TB may also help!

JP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] momyc:
I did the clean install on build 3 , and dirty on the following ones. The swiftkey is an original paid one. For now I'm ok with HW disable thing as I reboot my phone only once a week and only is need it.

I hope that syntax in the file will be ported on the following builds.

Anyway, a very good ROM very stable with my all over 200 apps.

A BIG THANK YOU to the slim team.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
No prob for me with SwiftKey or Exchange using latest build with KT 4-20 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Just reporting same here. Dirty flashed to yesterday's release and no screen flicker. No screen flicker with SwiftKey either. Running KT's 4/20.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Dirty flash as well, Swype keyboard. Kt 4/20. No Flickr.

I don't think dirty flashing is the reason we don't have Flickr, that doesn't make sense

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
Guys, the flicker is a known upstream issue that may or may not affect you. Look back a few pages on ways to fix it if you're affected by it. Doing a clean or dirty flash won't influence if it happens to you or not, it seems to be related to brightness and cpu frequency.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Hey guys... what's Google play services do besides eat my battery? Do I need it? It's always like second on the battery usage list.

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
Correct. I flashed two phones yesterday. One a dirty flash and the other a total/clean wipe. Both had flicker. They were TMO phones that use the same exact ROM file we do.

One with standard kernel at 1.5ghz and the other with BMS kernel at 1.86ghz.

One with Swiftkey and one with Smart Keyboard.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
Hey guys, if you're suffering from flickering here's a flashable zip fix. This zip is supplementary to the 4.2 build and only replaces your build.prop -- it is not a full ROM. It applies exactly what I described a few pages back, so if you've already done that then you don't need this.

SlimBean 4.2.2 build 4.2 flicker fix
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ooklathemok:
My Tracks

Anyone using Google's My Tracks app? Force closes on me after clean install this morning. When I was on 4.1 there was no issue. I use this app every day so if anyone could chime in to let me know if it is working for them, that would be great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
Logcat or bust
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nautiliux:
SlimBean 4.2.2 build 4.2 flicker fix, installed and working to perfection..... Thank you very much!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] momyc:
Thanks for that.

It seems to work well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] munabhai_mbbs_1989:
External_SD card

My External Card is not recognized.

I am using latest TWRP, tried unmounting and mounting using TWRP.

Scanned the whole device using TB as I have my backups in sd card.

exSdCard or not under mnt either...

Any solution/suggestion??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Try putting the SD card in ur computer and see if it shows up sound like ur card is going bad or corrupt
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Move folder/files too phone and scan again should work unless its corrupt....... Like Massachusetts governor

Sent from my
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ooklathemok:
Sorry, false alarm. My Tracks not working has nothing to do with ROM and everything to do with OpenPdroid patches. Restored with bustedwings' restore file and it is working fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slaman:
Two questions:

1. Is there anyway to back up just the Profile settings? That's the most time consuming part of a clean install for me.

2. Had anyone gotten the new ICS theme zip files working? I flashed the 04/22 versions from the website, but all icons are still white.

Sent from my Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nae10135:
Unable to setup AT&T Visual Voicemail app

Hey all,

After searching le googs, and the forums, I have found a common issue with other 4.2.1 ROMs that I am having w/ Slim Bean 4.2.1 stable.

I recently upgraded from Slim 4.1.2, (like I should with full chace & dalvik flashes) and since that time, AT&T's visual voicemail app refuses to setup.

I've tried all types of resets with the voicemail account, and spent about an hour with a great ATT support tech doing everything on the network side of trying to get the app to work, and we stopped short of a full "factory reinstall of the firmware."

The problem is: when trying to setup the app with the voicemail account, after entering the password / PIN, it hangs until the app times out on the packet request.

Is this a problem with 4.2.1 & compatibility with ATT's app, or specifically with 4.2.1 Slim bean?

Thanks in advance,

- nae10135