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

Search This thread
By:
Advanced…
N

__NBH__

Senior Member
May 20, 2011
835
226
Samsung Galaxy S21 Ultra
Google Pixel 7 Pro
I flashed the 4.2.1 beta last night after a full wipe, set up my phone and charged it overnight and have been using it today.

Initial tests seem great, I have managed to get 2 hrs 11 mins screen on time and still have 66% battery left. The jelly bean volume bug seems to have been fixed, it drove me mad that from half way to max the volume didn't change before as I watch videos and listen to music a lot on my phone.

Only issue I have noticed so far is the signal strength, sometimes it says I have full reception then it jumps back down to the normal 1 or 2 bars I usually get at home. Other times when I would get 1/2 bars before it says no signal, I am using the same modem as on Slimbean 3.1 (XXLQ6), is there another modem I should be using with the new version which might be better?

Once the inverted Gapps are back for this version it should be very nice.
 
D

dead0

Senior Member
Sep 6, 2011
941
331
anyone else having gps locking problem? takes ages to search for satellites and when it does find it, cant seem to lock on
 
afaneh92

afaneh92

Account currently disabled
Jul 31, 2012
3,909
5,297
Running great with dual boot patched siyah kernel
But there no lock screen option in settings
 
B

bloodyshyt

Senior Member
Dec 5, 2011
58
5
Just to check with you guys is there the long press volume to skip track function? I am really addicted to that function... Haha
 
sergiu84

sergiu84

Senior Member
Feb 25, 2007
105
4
Excellent! Flashed last night as main ROM, initially with Syiah 5.0.1 and com.android.phone kept crashing. Reflashed on its own, working fine!

Track skipping with volume buttons isn't working quite right with Spotify, maybe there's something I need to tweak? Not showing track controls for Spotify on the lockscreen either.

Also, this might've been the case on SlimICS too but I can't remember - the system RAM is down to 756MB, presumably due to more being allocated to graphics?

Great otherwise so far!
 
sakindia123

sakindia123

Inactive Recognized Developer
May 6, 2011
4,043
9,548
Noida
HardCorePawn,u guys mentioned on the site that u have implemented a gerrit..Is it open to external contributors?(just curious)
 
V

Volpones

Senior Member
Nov 9, 2012
54
17
Hello guys and Happy Christmas to you all ! I just flashed 4.2.1, AIO addons and Dorimanx 7.34 and all working fine. Will see battery drain in the next days.
 
BigE

BigE

Senior Member
Jan 25, 2007
1,553
323
Southern CA
Two questions:

1. I tried to install Google maps and get a message that it isn't compatible with my phone ? How come ?

2. Anyone able to make camera work in sphere mode ?

Sent from my GT-I9100 using xda premium
 
AbyssTrion

AbyssTrion

Senior Member
Apr 13, 2012
205
95
BigE said:
Two questions:

1. I tried to install Google maps and get a message that it isn't compatible with my phone ? How come ?

2. Anyone able to make camera work in sphere mode ?

Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse

Greetings,

Did you change the DPI? If not, maybe clear Play Store Data or try to install the App manually! (It works for me here).
 
nasser4life

nasser4life

Member
Nov 6, 2010
49
13
Roseau
This is how holo launcher HD looks when I change to vertical continuous in app drawer.
uploadfromtaptalk1356533057335.jpg
While changing APN info noticed the heading is for security settings.
uploadfromtaptalk1356533236451.jpg

Also can't find option to close all apps after holding middle button.
ROM looks nice tho. Looking forward to the updates

Sent from my GT-I9100 using Tapatalk 2
 
L

LJ1981

Senior Member
Jun 11, 2010
114
29
Wifi tethering not working for me. Build in tether is not working and also any third party apps not working. Is this known bug or?
 
Last edited:
kontinuity

kontinuity

Senior Member
Dec 3, 2005
150
19
How do I enable developer tools?

Got it! I feel like a true developer now :)

Sent from my GT-I9100 using Tapatalk 2
 
Last edited:
You must log in or register to reply here.

Similar threads

codeworkx
[ROM][GT-I9100][4.0.4] CyanogenMod 9 nightly builds | DEVELOPMENT THREAD
Replies
3K
Views
4M
limitedMUSCL
limitedMUSCL
krarvind
[ROM][4.0.4] Slim ICS (SGS2) - Clean, Simple & Fast (57MB)
Replies
5K
Views
1M
djshotty
djshotty
gokhanmoral
[KERNEL][19FEB] SiyahKernel v6.0b5
Replies
15K
Views
4M
J
jotapdiez
HardCorePawn
[ROM][4.3][03/12]Slim Bean - I9100 [Build 2.2][FINAL]
Replies
1K
Views
350K
B
b13n
Lysergic Acid
[ROM][I9100][5.1.1][OFFICIAL] CyanogenMod 12.1 Nightly Builds
Replies
3K
Views
974K
L
levio

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 269
    HardCorePawn
    HardCorePawn
    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
    View
    60
    HardCorePawn
    HardCorePawn
    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:
    View
    46
    HardCorePawn
    HardCorePawn
    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
    View
    41
    HardCorePawn
    HardCorePawn
    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!
    View
    40
    HardCorePawn
    HardCorePawn
    *cough*

    gtoregop.35g.png
    View

New posts