[ROM][4.2.2][05/08]Slim Bean - I9100 [Build 8][FINAL]
- Thread starter HardCorePawn
- Start date
AW: [ROM][4.2.1][16/02]Slim Bean - I9100 [Stable v1.0]
google play make not fast automatic update with titanium update help!
SliM BEAN v1.0- REVOLT 3.2
DORIMANX
google play make not fast automatic update with titanium update help!
SliM BEAN v1.0- REVOLT 3.2
DORIMANX
I don't know if it's my device, but I experience a BLUETOOTH bug with this rom as well as Cyanogen roms ... rendering my phone useless as I use it through out the day as a PHONE. Basically the phone stops responding while engaged. It's not all the time, but its shortly after its connected. Phone lags, and locks. Dialer doesn't work.
I haven't had this with any other rom (except the aforementioned), and unfortunately SLIM has always been my favorite.
Thanks
I haven't had this with any other rom (except the aforementioned), and unfortunately SLIM has always been my favorite.
Thanks
Hi all, I am interested in trying this ROM - just wanted to know of their is a list of compatible kernels anywhere?
I did try quickly last night but it failed to boot after i switched to speedmod kernel. I have read a few people mention siyah and dorimanx but what about jeboo or speedmod ot others.
Thanks
I did try quickly last night but it failed to boot after i switched to speedmod kernel. I have read a few people mention siyah and dorimanx but what about jeboo or speedmod ot others.
Thanks
Given that one of the first things mentioned in the OP for Speedmod is:
I highly doubt it will work with Slim
Likewise with Jeboo:
Did you actually bother to read the kernel threads before posting?? Or did you just flash from a Stock ROM and hope that the kernels that you use on Stock ROMs would magically work with AOSP and/or CM-based ROMs?
You might want to try looking up the index of kernels that GaboWinter has put together and checking out the Jellybean kernels... and looking in the individual threads for information as to what ROMs they support...
Hint: If they mention support for CM or AOSP there is a 99.9% chance it will work OK with Slim... However, if they only mention Stock or Samsung JB... there is 0.01% chance it will work with Slim...
FYI, the only kernels I know that works OK, is the default one that comes with Slim... (which is actually CM kernel 10.1)
The only other reported kernels that work OK are DorimanX and Siyah...
Code:
I/GsmServiceStateTracker( 4851): Auto time zone state changed
W/Settings( 4851): Setting auto_time_zone has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
D/AlarmManagerService( 2336): Kernel timezone updated to -420 minutes west of GMT
V/AlarmClock( 7594): AlarmInitReceiver finished
I/GsmServiceStateTracker( 4851): Auto time state changed
W/Settings( 4851): Setting auto_time has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value.
V/AlarmClock( 7594): AlarmInitReceiver finished
D/dalvikvm( 7594): GC_CONCURRENT freed 256K, 16% free 2448K/2884K, paused 1ms+10ms, total 44ms
D/SystemClock( 4851): Setting time of day to sec=1361306154
D/lights ( 2336): set_light_button on=0
D/lights ( 2336): set_light_button on=1at 1st reboot it didn't pick the correct timezone, but on 2nd it picked the right timezone and time.
Instead of "Western Indochina Time" now it received "Western Indonesia Time".
Thanks for the tip dude. You've really saved my day
still curious tho, how come we couldn't manually specify our timezone? And "Western Indonesia Time" is isn't on the list?
I know that my time zone is somewhere near "Bangkok, Hanoi, Jakarta", but where the hell they got the "Western Indonesia Time" string?
Yes, there is lag.. app drawer, launcher, lock screen all lags for me.. also the VoIP data has some fault.. I'm unable to use GrooveIP successfully although they have released a JB compatible version... something just does not add up on this ROM.. I reverted back to 3.1
Additionally, the lock screen widgets keep jumping about ...
The only thing I dint like about 3.1 is that the screen can not be unlocked when in landscape mode.. everything else was perfect...
yeah but when i was using rootbox its available in there and use it once..then after i restart my phone due to freeze, its gone lol :laugh:
Thanks for the developer option path :good:
Last edited:
May have something to do with the CSC (country code) not being correctly set for your country. You'd have to ask HardCorePawn what CSC's are supported for this ROM. Stick with it, though, it's by far the most stable JellyBean 4.2.1 ROM out there, and certainly the best looking...Thanks for the tip dude. You've really saved my day
still curious tho, how come we couldn't manually specify our timezone? And "Western Indonesia Time" is isn't on the list?
I know that my time zone is somewhere near "Bangkok, Hanoi, Jakarta", but where the hell they got the "Western Indonesia Time" string?
Well mate, I've just done a full wipe reinstall of HardCorePawn's latest masterpiece, including kernel wipe, full factory data reset, cache and Dalvik wipe, then reflashed the ROM and Dark Themed Gapps. The moment I got up to Launcher screen I went straight into the App drawer, and the Camera is definitely there...
Re: [ROM][4.2.1][16/02]Slim Bean - I9100 [Stable v1.0]
I have been taking 1080p vids of my son this morning. Its definitely there
Sent via HSPA±
I have been taking 1080p vids of my son this morning. Its definitely there
Sent via HSPA±
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
269
Disclaimer: We are not responsible for any damages on your device.
Original Slim Features:
- The Real Dark Slim
- Notification drawer Shortcuts
- Full hardware key rebinding!
- Keyboard rotation
- 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 here60Known 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:
- see changelog
46Just 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/
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...
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:
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) 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!
Sent from my SlimBean pwned GT-I910041Now... 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.
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
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!40
