yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Something is messed up. H+ is definitely indicating that you are getting HSPA, decent speeds but still HSPA. You have network mode set to LTE/GSM/WCDMA?

There was some mention about tweaked apn stuff for Rogers on build 5. I notice that Rogers Tethering apn has changed, for example.

Perhaps something in the new settings is not playing nice with what is required out east. Might have soimething do to with the new "LTE Max" that Rogers is rolling out, but that is a stretch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gauthier81:
Ok. I did my own searching and this is what i did to fix the jumbled name display. I am also on Rogers. You may not like this but.....I flashed a stock image of ICS through ODIN. Rooted phone again, installed TWRP recovery, then flashed Slim again. Now names show correctly. Hope this helps you out. Hit thanks :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
If you could list your baseband version, that would be helpful for others, it only works on 1 or 2 different modems I believe...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TadMorose:
Too long and complicated. Just flash one of the older modems from the link I posted and it's done. My name display is working again. The modem I flashed is I747MUMLJ1: modem_CWM_I747MUMLJ1.zip - 19.48 MB - October 1st, 2012 :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gauthier81:
Haha sorry i guess that would help eh. I747MVLLH1

---------- Post added at 10:37 PM ---------- Previous post was at 10:34 PM ----------

Oh well, sorry. Thought i could help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djmouse:
rom has been great until tonight,havent changed one thing and all of the sudden i was gettin major screen flickering it seemed to start happing when i had my phone plugged in and charging weird? ive never once had a screen flicker problem on any rom either
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
This should not be possible w/ the stock kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] desichiko23:
REally loving this ROM, just wish stock kernel wud let me do some tweaks..

here are some of my screenshots :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djmouse:
yea im running kts newest kernel,just werid it started doing it after 3 days ill flash the slim kernel and see what happens
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
After the flicker was fixed a few weeks ago another commit was added recently that re-introduced it. We reverted it in the kernel that comes w/ build 5, but who knows if others have as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djmouse:
i just flashed the 3.4.41 slim kernel from may 4 is that the stock now on build 5 or was that newer i see it has the faux patch,and one more question i was on build 4 and didnt wipe to build 5 i just saw a gapps build 5 should i flash that,sorry to be a pain,havent been following the thread my wife gave birth to my first son two weeks ago then had a heart attack this past week,not looking for sympathy just feel lost on xda right now havent been able to read she just got home today so i finally had a chance to check up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Its the stock build 5 kernel with faux 2.1 sound patch all the new faux sound patch does is add gain boost to power amp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djmouse:
yea but i thought build 5 was right before faux updated so i wasnt sure if the stock kernel had that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Ya the separate kernel blkjack posted In thread has it for build 5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
Just flashed Slim 5.

Glad to see that capacitive button backlight timeout settings are still avaialble (was removed from other ROM's).

Would be great to see SlimBean add Analog USB Audio. It's now working in some other AOSP ROM's, but not this one yet.

Digital USB Audio still not working also, but it's not working in any AOSP ROM's yet (properly).

I sure do hope you guys add the Bluetooth Shutdown fix that CM is merging tomorrow: :good::good::good:

http://review.cyanogenmod.org/#/c/37077/

Good job, devs. Looks great so far. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djmouse:
now youve confused me,so is the seperate kernel stock in build 5? or is the kernel that is included in the rom different from that seperate kernel, i would think it would be why would there be a seperate kernel if its stock?right? and what about the build 5 slim gapps i posted about?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
The "addon" kernel I posted after build 5 is exactly the same as the kernel included in build 5 with the exception that it has 1 extra commit for the new faux sound changes. Other than that it's identical.

As for the build 5 gapps -- why wouldn't you flash them? It has fixes and updated versions of google apps. You'd upgrade your apps from the play store, right? It's the same thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djmouse:
thanks alot for clearing that up, and i was on build 4 and i read that we didnt need to flash gapps anymore when just flashing without wiping,and i also use google wallet so i have auto update off because i havent found a fix yet for the newest version of wallet but ive updated everything else manualy,i just wasent sure if maybe there were some inverted apps in there or anything else that wasent in the older version of slim gapps. and this rom is the best ive used so far ive got a donation coming your way ass soon as i get squared away here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miluardo:
Will slimbean get the multi-window being developed by PA at some point? I'm thinking about switching when it's released, but don't want to leave slim behind.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
PA's halo feature is only available as an early alpha to certain nexus devices.. Also they haven't opened their source yet. Im sure at some point they will open their source and it will be added to other ROMs.. But that's a ways down the road
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miluardo:
I can't wait for this day. It will be the closest thing to true multi tasking for android... Which is something this OS lacks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Judman:
Is anyone using the ReadItToMe app highlighted in the portal yesterday.

I installed it and it doesn't do crap! I am betting it has something to do with the "slimness" of this rom, but I wanted to see if it just me or not.

Link to apppppppp thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Well not really...

Running in the background is the app developers responsibility. If he wants the app to be able to run when the user navigates away from it, he is completely free to do so.

All halo allows you to do is deal with an app that has a notification by opening that app on top of the active app. I'm not sure if the activities on.pause when halo is used.. haven't looked into it much yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miluardo:
It appears in their video like it still runs.

I understand a dev can allow an app to run in the background, but all other multi tasking operating systems do this themselves for the apps. I don't see the benefit to NOT allowing an app to run until it's closed. BB10, Linux, Unix, mac os and windows seem fine with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Keep in mind this is a phone not a PC.. The benefit is to prevent a laggy experience which is why android stresses to handle app closing properly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miluardo:
Haha it is true. I think if they added the option for higher end phones it would be nice. My girlfriends z10 handles things nicely. But you're right, when it comes down to it is a phone.. Screen realestate is limited and so is ram.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Its all relative... :) [old guy story/rant coming... minus the snow, bare feet, and uphill both ways]

I did development on 6809 processors that could not even mulitply with cassette tape interface, worked on card systems, hand build pcs inthe XT days when 8 MHz cpus with 2 360 K floppies and a 1 M of RAM was the high end... did "high end" cad when running a hardware design group off a 10 G disc array was the be all end all.

Compared to that, a 1.9 GHz quad core processor, with 2 Gb of RAM and 64 GB of storage is insanely high end...

Certainly can do "real" mutlitasking in any current smartphone specs. The question is does it really make sense to allow a multiwindowed UI, with all the headaches that brings on a 5" display. Running stuff in the background allows you to get stuff done, and you can easily flip tasks into the foreground. The other huge issue is battery life. Until that is solved, you are never going to see UIs build around a "real computer" experience running on a smartphone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
I installed it yesterday too, configured it up - which took a few minutes given the zillion settings and detailed walkthrough instructions- and promptly forgot about it. This AM while working out with headphones on, the music stopped and a choppy voice began reading me a fresh email that had arrived. Worked fine for me, either than the bumpy reading voice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LeeC:
Seems there're indeed some GPS issue. Possibly just me but I never had any similar issue before. I did clean install twice but no GPS and went back to 4.2 GPS locked instantly. Seems I'll stay with 4.2 for now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Yeah, I know this has been covered with a few workarounds but it's a new issue for me as well. I don't know enough about Android yet to make any assumptions as to why. Just know the issue is widespread and spotty with all 4.2.2 builds.

Strange though, I've been on EVERY build of Slim and never had the issue till B5.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Judman:
So I had a rom failure yesterday.

I had build 5 dirty flashed over build 4.2 since release day with no issues until yesterday. I was at work and pulled my phone out to text someone and it was at the slimbean glowing startup logo. I set it on my desk thinking it has just restarted for some strange reason. After 10 minutes stuck at that screen I pulled the battery and turned it on again. Still stuck at the glowing slimbean screen. Pulled battery again booted into cwm and whipped dalvik and cache and reflashed the rom and gapps. Still didn't finish the boot.

Finally restored by nandroid to build 4.2 so I could get a few things done then did a full whip and clean install of build 5. It's working now!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
The upstream branches are in a constant, and I mean constant state of development. Massive sweeping changes happen every week as CM (mostly) tries to sync up w/ Qualcomm's code repository. The reason why these new regression issues pop up is because there are large commits that sometimes rebase the entire branch on another, newer set of code.

So as somebody who doesn't usually touch the device/SoC repos (msm8960, etc), I'm left with two options. 1) Don't update those branches and have things break due to incompatibility or 2) Update and risk the chance of things breaking, but at least they break for all ROMs and when a fix comes out it'll fix the issue for all ROMs.

Right now with GPS we're at option 2, where upstream changes have left us with an issue that affects all new 4.2.2 AOSP-based ROMs.

So you either employ the workaround that has been listed in this thread at least half a dozen times, and a few dozen times in the CM threads, or you don't upgrade. It's not that myself or anyone on the Slim teams wants [the d2] to be affected by this issue, but it's mostly out of our (and every other ROM's) control.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LeeC:
It's not and will never be a complain. just simple report the GPS issue:o Thanks a lot for your hard work, blk-jack.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] basily:
So, what's all this about Faux sound - I'm new here, and we didn't have Faux on the Captivate... is it worth it? Will it allow me to raise the volume on the handset speaker and not add too much overhead to the phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] msn.debord:
Yeah its pretty sweet, you need to buy the app though.

Here are the options in the apps presets.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Really appreciate the explanation blk_jack. Hope you don't think I was complaining, I run all your builds cause IMO there always the most solid which I've said more then a few times in this thread and others. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] basily:
Cool. I am not adverse to paying for a good app. So, the speaker sounds can be amplified, right? It's not just for headphones?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] msn.debord:
It is global, so headphones and speaker. I like quality because I can bass boost more without distortion.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] basily:
Sold!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
Slim 5 build.

Clean [total] wipe & install.

Stock Slim 5 kernel & GPU settings.

WidgetLocker.

Opera Mobile Browser.

Got the screen fuzzy/flicker issue.

Was able to reproduce on demand.

Went to a heavy GIF laden webpage in Opera.

Put phone into landscape mode.

Worked fine.

But everytime the screen times out and I unlocked the screen, it would go right to the big fuzzy old-school analog TV signal looking screen, like when there was no station on TV. And would also flicker a bit.

If I scrolled up or down, the issue would go away and be fine until my screen timed out and was re-opened again.

Just FYI'ing in case anyone else has similar issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
Are you able to get a logcat from this? I had this similar issue and was not able to reproduce it so was not able to get a logcat out of it. Getting a logcat would help the team to get this issue resolved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] voidstab:
I seem to be able to reproduce it by unplugging the stereo jack while pandora is running and then waking the screen. I can try and get a logcat later tonight maybe, busy evening.. :(

I didn't think it was ROM related so I never bothered to post.

Almost forgot, I also now have the BMS kernel installed, I did however experience this stock(build5).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
That's a good idea. I should have done that. Logcat Extreme Pro is what I use and I just re-installed it.

Naturally though, now I can't reproduce the problem anymore. :D

Next time though!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jamaiquino:
I call it the "80s time to go to bed" issue. Like when u watched TV past 12 and it just gave you that grey grains, only this has color. I like to think of it as a feature that tells me when to to sleep
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] basily:
search with camera

Hey, I could swear that I used to be able to "search with camera" on google search and scan QR codes. Doesn't seem to work anymore for me. Anyone else have this problem or did I screw something up?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nsmith4:
It works fine for me,I just hit menu then "Search with Camera". You mean through Google Now right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] atrix4nag:
Week signal in my home

I am loving this rom alot, only issue i have with his rom is i have week signal in my home. I dont have this issue, with my earlier roms.

My wife has the same phone, but she is using other ROM, i checked the modem, both the modems are same.

Any idea, what could be the issue.

TIA
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] basily:
Yeah, that's it. OK, I rebooted and it works now...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheIgster:
Loaded the ROM last night. Liking it very much so far. Excellent ROM. I'm on Rogers and I have double checked all the APN settings, but I can't seem to get the LTE icon and or speed. 4G seems to be the fastest. Is there an issue with LTE on the ROM that anyone knows about?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
It's been talked a couple times for Rogers network, I would search the thread for more info...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] basily:
Not ONLY does it work, but unlike my Captivate (which took a lot more work to get it to work on) it doesn't seem to require external power! So far I've used a USB mouse and flash drive with no external power required! Now, to just figure out how to get it to recognize formats other than FAT...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheIgster:
I did a quick search, but it's a big thread...Just was hoping someone would know off the top of their head. :cool:

I did find one user who posted:

Also the rom definitely calls LTE 4G (am staring at the icon right now).

Which doesn't seem right to me, as 4G is NOT the same as LTE as far as I know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
If you flash this zip from Madmack it fixes Bluetooth streaming A2DP audio.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Oleschuldad:
How do I do that? I see Fix Permissions...which I ran but no change. mount cache, sd card and data are all checked, mount system is unchecked...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitarofozz:
If you want to get rid of it you can go in developer settings and change all the animation scales to less than 1x. All your other animations will appear faster but your screen off animation will be gone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

Isn't .5x default? I'll check again, should I restart phone after switching the settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

1x is default. Requires reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

Mine was at .5 from the start I think
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbabiuk:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

Do you need to fix permissions or wipe cache and dalvik?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpride:
Also, this Zip isnt a ROM? Its just a patch to the existing ROM we are running, such as this one?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MedicStuder:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

For some reason since installing this ROM every time a menu opens up the screen flickers. This was a fresh install wiped all caches, internal storage and factory reset. I use TWRP recovery. This occured on kernal that comes with ROM and with KT747 kernal. I have wiped and reinstalled with no change. I have not changed density or frequencies. Any ideas????

SGSlll AT&T
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Yes, its a patch that reverts A2DP to Dec 26th when it worked. I have flashed it on this and 2 others AOKP ROMs and it has fixed Bluetooth music on them all.

It looks like CM is pretty busy working on a permanent solution by the looks of tomorrow's log.

---------- Post added at 02:01 AM ---------- Previous post was at 02:00 AM ----------

There is a silght fliker at times. It should be fixed soon. You can disable HW overlays in Developer Options. That should help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

Doesn't help also can somebody help me when my screen off animation... I did as told put all 3 to .5x and rebooted phone but screen still turns off same way with white line fading out.... I'd really appreciate the help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MedicStuder:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

For the life of me I can not find the developers option in the settings menu. I now it normally is its own group to turn USB debugging on. This is the first time I have not been able to locate it.

SGSlll AT&T
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cytherean:
Magic trick.

Settings-->About Phone-->Build Number (click on it 6 times)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MedicStuder:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

Hey look at that it worked...Lil...thanks....I laughed while doing it...

SGSlll AT&T

---------- Post added at 05:53 AM ---------- Previous post was at 05:51 AM ----------

And my flickering issue has been fixed. Thank you all.

SGSlll AT&T
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cytherean:
Keep in mind that this fix may not stick after a reboot. There is another fix if you play with the prop build; see Task's post #116 in this thread "...screen flickering issues. Try changing your debug.mdpcomp.maxlayer=3. Change it to 2. That should help fix it for now without having to disable HW Overlays in Development Settings. "

I was able to do this on the previous build but can't for the life of me find the debug.mdpcomp.maxlayer in the prop build with this version of slim.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

They removed that line in build.prop in more recent releases. So you dont have to change that line anymore.

ROOTBOX Charged JB 4.2.1 fueled by Ktoonez 747 octaned kernel SGS3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

I did as told put all 3 Animations to .5x and rebooted phone but screen still turns off same way with white line fading out.... I'd really appreciate the help

I wanna make screen shut off w.out the white line in middle
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] prbassplayer:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

The screen off animation is a framework thing. At least afaik. So not a simple thing to change.

Sent from my Slim Bean powered Mako
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Re: [ROM][4.2.1]Slim Bean-d2(att/bell/telus/rogers)

Apparently this doesn't affect the CRT animation in 4.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
I can't help you much, I'm on Bell Mobility and everything works great!

As for 4G not being LTE, I believe 4G is LTE, it's just not written LTE, but maybe someone else can confirm this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheIgster:
Is it displayed as 4G on your phone or LTE?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
It's displayed as 4G on the slimrom, on the touchwiz rom it's displayed as LTE

As far as I know, it's the following:

4G > H+ > 3G

So as far as I know, 4G is LTE
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
AOSP ROM, of which Slim is one, say 4G for LTE.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
Thanks for confirming! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheIgster:
Yup, appreciate the confirmation.