yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t.square:
Thanks, I'll try that! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bustedwings:
That snow storm you got looked crazy. lol 200 car pile up.

just inverted is broken. can easily be fixed by pushing the mms.apk from the rom file back to system/app set permissions and reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TASL:
Re: [ROM][4.2.2][March 15] Slim Bean-d2(att/bell/telus/rogers) [build 2]

Just wanted to throw a thanks out to SlimRom team, running it on my d2att/crespo4g/grouper and could not be more impressed. Overall usability out the door is fantastic, even better when you spend time going through the included feature set. Mostly I appreciate the time that goes into making each release stable and current. TBH, a yearly fee would not feel unreasonable for the quality delivered.

"For the low, low price of $14.99 a year..." inc your way ( 76J50645315638509 ).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] z34370z:
Re: [ROM][4.2.2][March 15] Slim Bean-d2(att/bell/telus/rogers) [build 2]

Has anyone had any issues with Google maps force closing when using nav? Also my phone froze completely when I was on a call. Just froze once out of ours of conversations. Probably an isolated issue. This is all with a clean wipe. Using optional slim kernel.3-15 build. Everything else is fantastic.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bustedwings:
same issue. i spoke with previous slim d2att maintainer and kinda got nowhere... there is commit changes that where made to samsungservicemode.apk by cyanogen for jellybean but its generating this error

E/SamsungServiceModeActivity( 1158):

E/SamsungServiceModeActivity( 1158): com.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED

E/SamsungServiceModeActivity( 1158): at com.android.internal.telephony.RILRequest.onError(RIL.java)

E/SamsungServiceModeActivity( 1158): at com.android.internal.telephony.QualcommSharedRIL.processSolicited(QualcommShare

E/SamsungServiceModeActivity( 1158): at com.android.internal.telephony.RIL.processResponse(RIL.java)

E/SamsungServiceModeActivity( 1158): at com.android.internal.telephony.RIL$RILReceiver.run(RIL.java)

E/SamsungServiceModeActivity( 1158): at java.lang.Thread.run(Thread.java)

E/Sensors ( 713): accelHandler -0.117356 0.277822 9.450747

E/SamsungServiceModeActivity( 1158):

E/SamsungServiceModeActivity( 1158): com.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED

E/SamsungServiceModeActivity( 1158): at com.android.internal.telephony.RILRequest.onError(RIL.java)

E/SamsungServiceModeActivity( 1158): at com.android.internal.telephony.QualcommSharedRIL.processSolicited(QualcommShare

E/SamsungServiceModeActivity( 1158): at com.android.internal.telephony.RIL.processResponse(RIL.java)

E/SamsungServiceModeActivity( 1158): at com.android.internal.telephony.RIL$RILReceiver.run(RIL.java)

E/SamsungServiceModeActivity( 1158): at java.lang.Thread.run(Thread.java)

but on a side note looks like 2.5 is out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
4.2.2 Build 2.5 is out!!! Is there going to be a new and improved slim kernel as well, based off 3.4?

:good::good: :D:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
No, not yet. 3.4 is too unstable (see CM thread, etc).

Also note that vibration control was removed from this build (sorry, not my doing, if you're interested in a build with it please message me).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpride:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

If we flash a custom kernel with slimrom 2.5, does need to be 3.4 based?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
Slim 2.5 is using 3.0, if you flash a 3.4 kernel you will likely break the ROM.

Guys, please note, we did a lot of extensive testing and I highly recommend against using 3.4 right now. The freezing issues are *completely* random. I had days without a freeze and then had 3 freezes within an hour. Some testers didn't have any freezes in 48 hours of testing and others had a lot. There are truly no qualified gains of having 3.4 over 3.0 at the moment, no matter how much your brain is telling you "newer is better".

No matter what 3.4 kernel you're running you will almost definitely have issues (eventually). Be patient & wait for the kinks to get ironed out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
Vibration control has been removed from the CM kernel used in the stock d2att/d2tmo releases.

If you'd like this, it's included in the addon kernel I've been including the past few releases. The addon kernel has the following additions:

192mhz frequency added as lowest

Vibration control in Performance settings

morfic colors

Faux's Sound Control patch

Download it here

Source is available here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Profile Tab

Quick question... I had some problems after upgrading to 2.5 from the previous release. Once I rebooted I was getting force closes of 'System UI' one after another. I then did a fresh, clean, wipe, and while setting things up, I noticed that the 'Profile' can no longer be added under the 'Quick Settings' tab. I am guessing that is likely why. Not sure if it was omitted by accident or whether there was another reason - I didn't see anything in the changelog about it. But, beware, just in case, if you are upgrading and just wiping cache and dalvik, you may want to remove that tab under quick settings first. Not sure that's what caused it, but it makes sense.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Can I go from 2-2.5 with dirty flash cleaning ROM and caches?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
I did... I wiped /system though... if there's any issues, wipe the whole phone...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Me too. Seems to be fine, through a couple of calls and reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Just finished flashing, apps that didn't work on 2, all seem to be working now!! :cool:

Thanks for quick work on update!!

Fantastic Cheeeers!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jonhy25:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Which version of kernel is the latest update? Is it 3.0.x or 3.4.x?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Awesome update love how the keyboard looks now with trds so quick question I search Google and every where else does anyone have a high res clean copy of the slimrom boot up I wanna use it as a wallpaper but every time I extract it from the boot up file I can't seem to get a clear copy wanted one with the s in full blue if no one has it blkjack I'm sure u know u made it maybe u can snag a clean copy ?

sent from the samsung galaxy airplane (i747)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
It's 3.0... just a couple post back will have your answer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brjig:
Im having issues with the notification light, I have it enabled but it doesnt work whenever I get a msg, or a notification in general. It is on, I know that, Im running Build 2 without anything extra.

I came from liquid smooth, but it was a clean install format system and wipe everything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bustedwings:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Openpdroid patches for 2.5 for those that want.

http://db.tt/TI2b9Dme
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] toyanucci:
Same here! Orange Backup works again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t.square:
Seem's like a good thing Slim hasn't updated to 3.4, just read the CM and KT's thread and there is a metric **** ton of problems...! :p

I'm gonna flash 2.5 this afternoon and get some slim goodness (presented by Linux 3.0) :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

What exactly are these patches for? What do they do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Definitely a good thing. 2.5 is ultimately more of a bugfix & optimization release -- the last thing we want is to have a bunch of issues fixed there and then introduce another set with a new, unstable, barely tested kernel. Especially considering the 3.4 kernel is under heavy development getting commits pushed to it daily.

3.4 will obviously come, but one of slim's primary goals is to provide a stable & reliable rom/experience and that's not something that will change anytime soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

This is why I love Slim team. Releases are always tested, stable, and everything works. Havent jumped on the 3.4 bandwagon cause I just don't see the benefits yet. No knock to any other devs/team cause they are all awesome stuff. But slim stands out. :thumbup:

Suped up S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
^^THIS^^

Flashaholic here and I always come back here for a good stable ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wond3r:
Do those new camera support features also apply to the front camera? Will we be able to get full resolution of the front camera now?

I believe ours is 1.9mp but it would only give us the option for 1.2 in the previous versions
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Try it out deff recommend flashing 2.5 from 2 I notice big difference in stability for most part everything works, everything is flawless!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Blk jack anyway i can have access to the build with vibration control.

Suped up S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cirusnb:
Check this this Thread out.. should explain lots

http://xdaforums.com/showthread.php?t=2098156
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
I think he posted a kernel a few pages back with it.

Edit: here http://xdaforums.com/showpost.php?p=39453372&postcount=1210
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bustedwings:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Thanks was at work. Couldn't respond.

I find it hard to live without this once you actually learn what some apps have access to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Permission please?

I'm currently sporting the 2.5 version and it is near perfect. My only issue being the Google Account Manager continually asking for permission. It cannot/will not be satisfied. I have tried clearing data and force stopping it but it always returns. I tried re-flashing Gapps. Is there an answer for this or do I just put up with it?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zzmomo73:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Did you try removing your account and re adding it? And dirty flash or clean?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cytherean:
Have your tried to log out/remove the account and then log back in? I had similar issue with the play store and that was the "fix".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I think I did, but I'll do it again... It was a clean flash at one point... lol

NOPE, that didn't get it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Is pdroid manager from play store same thing as the openpdroid I read a bit about it thinkin to try iT as well looks cool?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
They are two different apps but the same... openpdroid is the open source version... For JB, you need either pdroid 2.0 or openpdroid...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
Try wiping /system in recovery & reflashing the ROM + full gapps package (latest off the site). The reason it has asked for permissions the past few versions is because we've updated the gapps (calendar/email/youtube/gmail/news widget) and some of those we have to resign or they use different signatures so Android thinks they're different apps and asking for [new] permissions.

That said, the fact that it's not going away is kinda worrisome, makes me think there's something leftover or conflicting..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Yea that's what I meant similar ability and what not... Thanks for quick response quasi

Edit, so do I reflash ROM with the two zip files from 2 pages back dropbox,patch to 2.5 ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
One of those files is the patch, and the other reverts the patch... You don't have to reflash the ROM, but you need to be running the same ROM zip he patched... The patcher takes the ROM zip and creates the patch, and an undo patch... So anytime you flash an update, or a different ROM, you need to load that zip into ApG and it will create those two files for you...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Okay I got it, read it over couple times and made sense finallyi think, the reverting file basically 'uninstalls' patch from rom. And the patch 'installs' pdroid to the rom, every time there's a new update for pdroid or ROM, somebody (I'm noob) has to make new patch for pdroid to work for/new-rom??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lookitfast:
My feelings exactly!! Wasn't impressed with anything the 3.4 offered to me anyway! Tried multitudes of combinations but still had freeze ups like crazy.;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Yea but the patch doesn't install pdroid it just patches the ROM for pdroid to work... The patcher asks for the ROM zip and creates the patch... So you need to make a new patch when a new ROM comes out... Use openpdroid with the patch that was posted... ApG is as easy as giving it the ROM file and choosing openpdroid and aosp and it makes it for you...

Insert sig here...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Professor!!! Thanks a bunch buddy!!

Never checked out the APG software assumed it was some coding require or something more difficult than u said...

Ive setup the pdroid thanks quasi for info and detail. So basically most apps have access to our sim card info IP address etc....?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] otoolerc:
Hey. I finally found a speaker dock for my S3 that I'm considering buying. It's a Philips AS351/37

Its supported Bluetooth profiles are A2DP, AVRCP and SPP.

The 'Bugs' page on the Slim site says "BT handsfree doesn't initialize".

I am just curious if there are any other known bluetooth issues, and/or if anyone knows whether these profiles are supported or not.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbabiuk:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

I seem to be experiencing the exact same thing with the request for permissions. My install was a clean install with a wipe of /system.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Did u try clearing caches and fixing permissions?

Newest gapps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bustedwings:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

In pdriod manager if you click on each option like GPS it will tell you what the app would need that access for. If you really want to be creeped out checkout facebooks access......data mining anyone? Lol

That's why I said earlier. once you start using these options its hard to go back. Some rom Devs will actually include this functionality baked in now.

If slim team was looking for some new features to add, I'm not sure how other users Feel, but its a nice option
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MN_Evolution:
Quick question... Are the "developer options" hidden or just omitted from settings? Looked for it a couple times through all the settings menus but didn't see it. Maybe I'm blind?? Any info would be appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zzmomo73:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

You have to tap build number like 10 times for it to show up. In settings- about phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Tap on the build version 6 times to unlock it...

edit - late with that reply...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MN_Evolution:
Awesome! couple of thanks to go 'round.

Kind of a fun little Easter egg.

Much appreciated guys
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Yea busted ur abs right, I think it would be sick if slim add the feature with some tweaks possibly, luckily I don't have Facebook app, but is there a way to set all/most options with like one click so I wouldnt have to go thru each one and switch settings on/off?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slaman:
My phone is freezing after I hang up a call. I say it's happening about 25% of the time, and it's fairly easy to reproduce. The screen goes black except for the status bar, the backlights stay on, and it's completely non-responsive to all touch and hard-button presses (including the Power button)

Any suggestions? I'm using the kernel that comes with the ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

I too have been getting phone freezes while in the middle of a call as well...both instances were during 40+ minute calls. Doesn't always happen so I almost didn't mention it.

Edits: the system freezes completely and the only way to overcome is via a battery pull or holding the power button.

Sent from my Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

One of guys should grab a log cat it would help fix it big time

sent from the samsung galaxy airplane (i747)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

By any chance those of you having the freezes during a call what kernel are you using?

Suped up S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slaman:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Standard kernel that comes with the ROM.

I'm going to try koonetz's soon though.

Sent from my Samsung Galaxy S III

---------- Post added at 03:25 PM ---------- Previous post was at 03:24 PM ----------

Can't grab logcat because phone freezes and you need a battery pull to recover... the odds of me having the phone connected to eclipse to monitor logcat during a call are very low.

Sent from my Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Yea i was having the same issue with bms kernel. I switched back to kt's and hasnt happened since.

Suped up S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phositadc:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Is it generally true that whatever bugs cyanogenmod has, that slim bean will also have? Or is slim bean more stable than cyanogenmod?

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
That is not necessarily true. I believe Slim to be based on AOSP, which is the same base CM uses. Slim is not based on CM and therefore will not necessarily have the same bugs although they may share features.

For proof - check out the fun in the CM thread since the 3.4 kernel switch in the CM nightlies. Slim is still using the older kernel and is currently much more stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

Yea said it well!!

Nice rolls BTW

Only 'freezing' is a split second delay before my screen actually turns on after clicking power button but its nothing to worry about... If ur phone acting up redownload newest gapps and ROM from slimbean and reflash from scratch...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ovoxo.:
Rom is blazing fast, mostly stable, and battery life seems to be good as well. Anyone who is on another 4.2.2 rom and is hesitant from switching should most definitely give this one a run. Probably my favorite rom I've flashed yet. Thank you for your hard work! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
Yes and no. Slim uses (like most/almost all AOSP based non-nexus device roms) CyanogenMod's device repositories. These repos consist almost entirely of upstream code and in the case of this device specifically, qualcomm and their code aurora forum branches.

So there is and always will be what a lot of people have coined as upstream issues (bluetooth, camera, call hang up freezes, audio glitching, etc). Issues between our hardware and libraries that is in a constant state of development. The difficult thing about these issues is because we're only provided binary blobs instead of actual source, our hands are tied until those binaries are updated for new versions of android or (again in our case) qualcomm updates their chipset branches. As for the device level code that qualcomm provides, I would say that it is beyond 99.99% of XDA's "developers" -- especially considering most devs/ROMs on XDA contain little to no original code or features and that a lot of ROM authors are actually just chefs, cherry picking other people's commits with slight changes here & there to make the code work together. Lately we've been calling them kitchen sink ROMS, since some people are just throwing everything in but the kitchen sink, regardless of how it affects device speed or stability.

Any and every feature you add has the potential to introduce new instabilities and problems. Pick your poison, really. Though I'd like to think we do a pretty damn good job of testing and reviewing all our code before it's merged in github, let alone release to you guys. We have a strict gerrit code review process where in each commit lives for review while we test on all our supported devices. One thing you won't see in our source, which you definitely can't say for most other ROMs, is commits with messages like "Oops!" or "Derp!". That is a very telling sign that the ROM you're going to flash has "developers" who are just pushing broken and buggy code to the github before really testing it themselves and have no actual development experience themselves.

When I put on my typical user hat, that kind of thing is very scary and I stay away from those kinds of ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
Re: [ROM][4.2.2][March 22] Slim Bean-d2(att/bell/telus/rogers) [build 2.5]

I'm using the kernel blk-jack posted 3/22

Edit: My bad. Just realized I'm on the stock slim kernel. I reflashed the ROM and thought I had reflashed the kernel too. Whoops!

Sent from my Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] droid_funktionz:
Random question about the latest 2.5 build. I tried installing one of the alternate weather icon packs for the cLock but I cannot get them to appear. Anyone know how to get these to work in the latest build?