[ROM][4.2.2][05/08]Slim Bean - I9100 [Build 8][FINAL]

Search This thread

ShadowSkills

Senior Member
Mar 26, 2012
100
29
Re: [ROM][4.2.1][04/02]Slim Bean - I9100 [RC2]

Or you could just drop your alarm sounds in Notifications or Alarms directory in your sdcard..

Cheers
Sent from my SlimBean-ed I9100
 
Last edited:

HANDSY

Senior Member
Apr 7, 2012
790
293
Re: [ROM][4.2.1][04/02]Slim Bean - I9100 [RC2]

Hey guys, loving rc2 so far! Its really fast and stable.

Just one thing, when I scroll through the home screens, it sometimes flashes the next screen just as i scroll. Is it a launcher glitch?

Im running everything stock with elastic and infinite scrolling enabled.

Sent from my GT-I9100 using Tapatalk 2

Hi, I had this issue with holo launcher hd whilst using card stack transition. It also happens with trebuchet launcher. The only way to resolve this issue, for me, was to change from card stack to tablet transition.

Sent from my GT-I9100 using xda premium
 

pocvitaldo

Member
Jan 19, 2012
41
9
hey guys great rom!!
thank you very much for your time

been using rc2 since this afternoon and i find it perfect but i found some issue not adressed before:

-some random reboot while phone was idle with the screen off
-the battery icon circle+percentage and dotted circle+percentage don't show percentage
-both incoming and outgoing call log always show 0 mins 0 secs

And one question: there is a way to disable the crt-off effect??
 

crocodilechris

Senior Member
Nov 13, 2012
64
25
Berlin
@steveria79:
just tested it:
create alarms directory in /sdcard/media/audio.
put file in /sdcard/media/audio/alarms, then choose it in alarm clock settings. Works for me.
alternatively install ES File Explorer, so you can choose your music file from wherever you put it.

also tested with ringtone:
put file into /sdcard/media/audio/ringtones, so it is listed at sounds as ringtone

to make it work the id3 media tag "title" of the music file have to be set.

@pocvitaldo:
circle+percentage works here... just don't show if battery is at 100% - is it?
call times are mapped wrong here. Shows hours as minutes and minutes as seconds. So if you call less than 1 minute nothing is showed. Every minute will be showed as secs
 

DVDeus

Senior Member
Dec 9, 2011
170
7
Hi,

a bit OT: is there a noise reduction option in this ROM? So when I am outside in traffic, it isolates other sounds but my voice.
I also remember that when a person stopped talking to me, the voice transferring stopped like the line was dropped (like he/she would mute the sound), but then when the person continue talking again, the sound was back again. It was a nice feature, but I cannot remember on which ROM I was, because on 4.1.2 SlimBean 3.1.0 this is not working.

I hope I did not complicate it too much:)

Thanks!
 

DVDeus

Senior Member
Dec 9, 2011
170
7
So I guess that is an option in SlimBean/Android 4.2.x.
What about noise reduction, is there an option when in a call (special icon for enable/disable)?
 

The-Captain

Recognized Themer / Retired Forum Moderator
May 18, 2011
2,802
3,179
Let's keep this thread related and on-topic to this ROM. Thanks.

~ The-Captain
 
  • Like
Reactions: netban

asterius

Senior Member
Dec 13, 2012
87
16
Re: [ROM][4.2.1][04/02]Slim Bean - I9100 [RC2]

Works great @ my device:) thanx to all. Have a question? How it goes with dorimanx7.47? And Any update for iso settings at camera? Thx again.

BTW no performance settings under Ass ??

Sent from my GT-I9100 using xda app-developers app
 
Last edited:

HardCorePawn

Senior Member
Mar 24, 2009
1,072
4,716
Auckland
Thanks for that... Nailed the BT one... It is missing a "VIBRATE" permission apparently, actually a google bug by the looks of it!!?! This will be fixed in next release... as a workaround, make sure phone isn't on vibrate before sending files via BT ;)

Couldn't see anything obvious in logcat for the Play Store thing... can you please get another logcat after Play Store FC's?? You can also try Settings -> Apps -> Play Store and try clearing cache and data... see if that helps... also, try removing and re-adding your Google Account.


Hi, I had this issue with holo launcher hd whilst using card stack transition. It also happens with trebuchet launcher. The only way to resolve this issue, for me, was to change from card stack to tablet transition.
Never noticed this... as my homescreens were on "none" for transition effect. I suspect this will be related to the ongoing HWC issues with Exynos... not much we can do but suggest different launchers and/or not using certain effects... sorry :(


-some random reboot while phone was idle with the screen off
-the battery icon circle+percentage and dotted circle+percentage don't show percentage
-both incoming and outgoing call log always show 0 mins 0 secs

And one question: there is a way to disable the crt-off effect??
- Haven't had one "random" reboot (all have been the direct result of my dev work :silly:) Are you on stock or custom kernel? Did you upgrade to RC2 from RC1 or a completely different ROM? If you upgraded from different ROM, did you do a full wipe?
- Shows percentage fine unless you're at 100%... not enough room for 3 digits ;)
- Had others with call log issues... works fine here... can you try Settings -> Apps -> Phone, and clear cache and data?

As for CRT, we just added a function yesterday to allow disabling of this... will be in next release :)


BTW no performance settings under Ass ??

Did you search/read the thread? This has been asked/answered several times...
 

pocvitaldo

Member
Jan 19, 2012
41
9
thanks for the answers:

@HardCorePawn: yea i did a full wipe and all and the "random" reboot only happened once with full battery (it seems a battery issue on my phone).
Until now never had another random reboot

I realized only later there was no room for 3 digit in the battery circle :silly:

For the call log it seems crocodilechris has addressed the problem:
(i cleared cache and data of phone app)

crocodilechris: call times are mapped wrong here. Shows hours as minutes and minutes as seconds. So if you call less than 1 minute nothing is showed. Every minute will be showed as secs

Thanks again for the greatest rom for the S2 :good:
 

polishpt

Senior Member
May 8, 2010
71
5
thanks for the answers:

@HardCorePawn: yea i did a full wipe and all and the "random" reboot only happened once with full battery (it seems a battery issue on my phone).
Until now never had another random reboot

I had few random reboots and it wasn't related to the battery - once it was around 50%, some other time around 90%.
Once it happened unlocking the phone, other time switching between the apps

I'm on RC2 upgraded from RC1 with stock kernel, stock everything :)
 

Mk.Xal

Senior Member
Aug 24, 2010
280
115
I had few random reboots and it wasn't related to the battery - once it was around 50%, some other time around 90%.
Once it happened unlocking the phone, other time switching between the apps

I'm on RC2 upgraded from RC1 with stock kernel, stock everything :)

Try to do a clean install of RC2.
 

Blaiz0r

Member
Jul 2, 2010
31
1
Thanks for that... Nailed the BT one... It is missing a "VIBRATE" permission apparently, actually a google bug by the looks of it!!?! This will be fixed in next release... as a workaround, make sure phone isn't on vibrate before sending files via BT ;)

Couldn't see anything obvious in logcat for the Play Store thing... can you please get another logcat after Play Store FC's?? You can also try Settings -> Apps -> Play Store and try clearing cache and data... see if that helps... also, try removing and re-adding your Google Account.

Thanks for looking into that, attached is another logcat file, I created this one by clearing the log using catlog, opening my offending app 'Learn Cantonese' choosing the in-app upgrade option as it hadn't noticed that I was a full owner, this took me to the Play store which notified me I already owned the app, the prompt had a details button, when I clicked this, Play crashed.

View attachment logcat_and_device_info.zip

Regarding the BT fix, I also had a pairing issue with my Jawbone Jambox, that may not have been in my previous Logcat, if not I can upload one for you tonight, or would the pairing issue also be fixed with the latest changes you made?

Thanks for all your hard work!
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 269
    SlimBeanOP2.png

    Disclaimer: We are not responsible for any damages on your device.

    Original Slim Features:

    1. The Real Dark Slim
    2. Notification drawer Shortcuts
    3. Full hardware key rebinding!
    4. Keyboard rotation
    5. SlimCenter

    Check out our full feature list here

    Important Notes:

    • Build 8 is the final 4.2.2 build for Slim Bean
    • NO ETA's...
    • Fully compiled from AOSP source ( source.android.com) with our mods.
    • Read the Change-log and installation instructions from the official website carefully.
    • Feature requests will be ignored in general, but we will review ( if a relevant commit or source is provided) and then decide.
    • Please provide a logcat if reporting a bug.
    • Strictly NO ports based on our ROM zip (official or unofficial build) file, manifest.xml will be updated regularly and feel free to compile from source.
    • No discussions/screenshots etc in the thread about battery life, "best settings/gov/scheduler" for "best battery life" etc... see here for the reasons why...

    Changelog
    Find our latest Changelog go here

    Chat with the slim team and other slim users
    • IRC: #slimusers@freenode
    • New to IRC? Don't have a native app? Try the Freenode web client [link] or the Firefox extension Chatzilla [link]
    • Google+ [link]
    • Twitter [link]
    • Facebook [Link]

    Installation instructions
    For Most Users
    Please keep in mind if a special instruction is needed it will be noted in the Changelog
    • Download the latest build from [here]
    • Addons ( if you don't have it already) from [here]
    • !Recommended! Full wipe, and manual format /system
    • Flash ROM and the addons you want, reboot

    FAQ
    Check out out FAQ before posting! Keeps more common questions answered in one place!

    Help us out!
    If you want to help us by translating slim to your language check out Crowdin.net and submite your translations.
    Or consider a donation.

    Thanks!
    You can find the full list of credits here

    Source
    Please visit here for the rom source code.
    Kernel source can be found here
    60
    Known Issues (as of Build 7):

    Device Specific:
    • Wifi Direct is not working
    • BT - A2DP does not transmit Artist/Track info (AOSP BT stack issue :()
    • Zoom on camcorder at 1080p is broken
    • Front camcorder buggy
    • USB Dock audio broken

    General:
    46
    Just to be clear...

    I have tested this extensively... I have other people testing it... This is why we don't do nightlies...

    Yes, we are including CM's open source RIL
    NO, we don't have the RIL issues that Rootbox has (because I figured out what was wrong and fixed it) :fingers-crossed:

    For the record, initially, I did have a broken RIL... Couldn't send touch tones in a call, couldn't hangup etc...

    TLDR; PROTIP: make clobber, tell your friends ;)

    Long Version: Turns out that, for whatever reason, the old (Sammy blob) version of libril.so was being cached and injected into the build, despite the fact that it had been removed from vendor/samsung/proprietary/i9100/lib/ :confused:

    So, you'd end up with new opensource /system/bin/rild, but old /system/lib/libril.so.

    They wouldn't play nicely together and you'd get the messed up phone functionality... :rolleyes:

    Old version of libril.so was, from memory, 49,100 bytes, new compiled one was 35,336 bytes...

    So I did what I always do when things are not being recompiled properly... I did a "make clobber"... Which completely removes the entire build directory AND wipes the compiler cache...

    Et voilà... New libril.so is built and used and everything works as it should... :thumbup: :cool:

    Note: The compiler cache is useful, in that it can cut down compile time dramatically... A full build from scratch after make clobber, using 2 threads (have to play nice with rest of team sharing build box :p) will take about an hour... If the cache is available... It'll take less than 30minutes! Very handy if you're doing a lot of compiling...

    The only issue, is that sometimes, you get situations like this, where, for whatever reason, the system doesn't detect a change and just bundles the old libraries in... :(

    Which brings me to my last point... Why I am (and most of the Slim team are) hesitant to do nightlies... (to be honest, I'm not 100% comfortable with weeklies, but they're a good way to get feedback on new features and real world user testing ;))

    Nightlies are, usually, just automatic builds of whatever is in the repo... About the only checking, is that the compile finished without errors...

    This is why they are always plastered with warnings that they are highly experimental in nature, possibly broken, use at your own risk, read before you flash, make backups etc...

    And yet, people still moan and whinge and complain at the devs and say things like "y u release broken build??!?"...

    I personally, and the Slim team as a whole, take quality seriously... Sure we've made mistakes in the past, and released subpar versions.. . And you know what? We were so concerned about it, that we modified our entire dev and release process to try to make sure it never happens again...

    This is why we:
    - moved away from the "every 2 weeks" release cycle we used to have.
    - implemented gerrit to allow for proper peer code review and testing
    - implemented a release cycle that involves code freeze, dedicated testing and final release

    Will our ROM always be perfect? No... But will we always strive to make it as close to perfect as possible? YES! :D


    Sent from my SlimBean pwned GT-I9100
    41
    Now... for some general discussion on a couple of topics...

    Firstly... Battery Life...

    There shall be no more discussions/screenshots etc about battery life, "best settings/gov/scheduler" for "best battery life" etc...

    battery is, AND ALWAYS WILL BE, very much a "personal" thing... your own particular usage patterns, apps, cell network, signal strength, RF interference, WiFi config, battery condition, brightness levels etc etc, will define what you get out of the phone/battery...

    I've seen folks who consider "normal" usage, to be having no apps installed, running all black themes/apps and sending 2 text messages a day and making or receiving one phone call of 2 minutes in length... with WiFi disabled and no mobile data. I've also seen folks who consider "normal" to be sending about 100 text messages a day... making 2 hours worth of phone calls... and listening to music via BT headphones, watching video or playing 3D games while updating Facebook every 5 minutes...

    There is no magic bullet... there is no magic governor/scheduler combo which is suddenly going to grant you 3 days of constant 3D gaming etc...

    If you suddenly get unusually high battery drain for your situation... there is about a 99% chance that you have a rogue app causing wakelocks... install BetterBatteryStats, find out what is causing all the wakelocks and fix it. If you end up in the 1%, have investigated and sought help in the BBS thread and discovered that it is actually something system related (and have BBS reports to prove it!) then go ahead and post here...

    Smartphone battery life in general is just poor compared to that old Nokia 3310 that you used to own that lasted for 7 days on a charge... get over it.

    Remember, this is, technically, a dev thread... and while I'm happy to have "general discussion" in here, mostly because a 2-thread system doesn't work... posts about battery life, and screen shots of how awesome/poor your setup is, just don't result in anything meaningful... and to be blatantly honest, there isn't anything we can really do about it to make any significant difference. Sure we might be able to get you an extra 15 mins of screen on time by tweaking the CPU and/or GPU voltages by -25mv... and opening you up to freezes, lag and random reboots in the process. :rolleyes:

    If you don't like this... feel free to go open a battery thread in the General and/or Q&A forums... any more posts in this thread regarding battery life will be reported and removed (and yes, the OP will be updated to reflect this)...

    HALO...

    quite a polarising topic this one... some folks think it is the best thing to have happened to Android. Some folks seem to think it was some sort of plague devised by Apple to destroy Android. Others simply don't care, as they realise if it ever gets implemented, it will have an On/Off switch... much like SlimPIE ;)

    As it stands, HALO just isn't ready for Slim. There are some fundamental issues with it that need to be resolved before you'll see it on an "Official" Slim build and we're not sure they can or will be resolved. This isn't just performance related either. We're talking things like:

    • The install button problem, can't press "Install" on the APK installation screen. (possibly already solved)
    • G+, whatsapp and some parts of youtube (lpe videos) are cut off or gave weird results in a floating window just to mention 3 bigger apps
    • if an app call an activity from a floating window and is waiting for activityResult the callback does not work.... Major issue!!
    • memory leaks need to be solved especially for our old devices. There is some code cleanup needed. Just turn it off for this devices do not resolve it
    This doesn't mean it will never be implemented... just that we feel it is detrimental to the overall quality and stability of the ROM as things currently stand. And of course, as with most things like this... if we ever do roll it out, it'll be a feature that you can turn on/off ;)

    On a similar topic... Hybrid mode... probably never going to happen. In our opinion, it just isn't worth the sacrifice that would have to be made to stability and performance to achieve. Consequently, this is not actively being considered, at this point, by the Slim team.


    Finally... a small teeny tiny little request... should you choose to respond to this or any of my long posts... please, for the love of little green robots everywhere... DON'T QUOTE THE WHOLE POST... remove all the bits that are not relevant!