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

Search This thread

thompson2009

Senior Member
Mar 2, 2011
229
17
Chesterfield
Re: [ROM][4.2.1][16/02]Slim Bean - I9100 [Stable v1.0]

Hi dev

This ROM is wicked fast and brilliant and it's free eeeeeeeee

Nuf said

Will donate now got a job

Sent from my GT-I9100 using xda app-developers app
 
  • Like
Reactions: HardCorePawn

Didgesteve

Senior Member
Nov 24, 2011
1,698
1,029
Truro
5. USB Mass Storage/UMS : There is a strange behaviour that seems to be related to the computers' USB chipset.
Depending on the PC I have tested it with (and even depending on the USB 2.0 or USB 3.0 port on a same laptop) once you have turned it off, you will have to unplug and plug the USB cable before turning it on again, otherwise partitions will not be mounted on the computer. Most of the time it does not show the second confirmation popup (which is not useful anyway, I think).
Finally, why does it say "Connected as an installer" in the notification area?

6. MTP file transfer fails with error message on Windows when transferring certain files (seems to be related to capital letters and/or unsupported file extensions). Still investigating...

7. Transfer all files through BT [including APK] does not work, neither in Explorer+ nor in CM FileManager. Explorer+ app developer claims that the issue is system related as his app simply calls available share options from the system.

Missing stuff that used to be there in previous releases

8. "Performance" is missing some options like "CPU voltage" and "Startup tweaks", Init.d, zipalign

9. BLN support missing (was already gone in 3.x)

10. FastCharge feature missing

11. Option to disable SlimBean boot animation

12. Battery icon styles "icon with text" and "icon with centered text" missing (they used to be available and still are in AOKP 4.2.1)

13. No navigation bar and nice background in CWM (like in some earlier releases

14. USB Mass Storage in CWM does not work

I hope these features will be back soon.... ;)

Missing stuff that would be nice

15. Add EAP-SIM WiFi authentification method (necessary for hotspots like "FreeWiFi_secure" or "SFR WiFi Mobile" in France)
This used to work in SlimBean 3.1 by replacing the wpa_supplicant file in \system\bin with a version taken from a 4.0.x Samsung ROM.
However, in SlimBean 4.2.1 that procedure partly breaks WiFi support.
There are multiple references to EAP-SIM in "\system\bin\wpa_supplicant"
You might also want to have a look at here

Regarding AIO Dark Gapps

19. Default app selection window is still white. Is that the intended behaviour?

20. Could you replace SMS icon with a Holo Blue couloured one?



USB transfers work fine here. Looking at your 'depends which computer I use' comment, I'd say it might be an issue with your PC setup. Do you have the latest Samsung USB driver? available on ApriliaM3's dev site, here

I've had Bluetooth problems with Slim 4, last seen working in Slim 3.1, hopefully 4.2.2 will bring some results.

If you want to play with 'performance' on your kernel, then get over to Siyah or Dorimanx. The build has a stock kernel, and it works fine.
BNL - works in Dorimanx
Fastcharge - Works in Dorimanx



and I'd like mine in pink.
 
Last edited:

ulysse34

Senior Member
Aug 21, 2010
167
41
Thank for your reply, but I don't think that it is an issue with my PC setup. There's something weird on both computers and on the second one it still differs depending on the USB port I use.

The kernel related features that have been removed from Slim Bean used to be present in previous releases, so I hope they will be back officially soon.
Imho tinkering with experimental kernels that often just lead to new issues is not the way to go
 

Didgesteve

Senior Member
Nov 24, 2011
1,698
1,029
Truro
Thank for your reply, but I don't think that it is an issue with my PC setup. There's something weird on both computers and on the second one it still differs depending on the USB port I use.

The kernel related features that have been removed from Slim Bean used to be present in previous releases, so I hope they will be back officially soon.
Imho tinkering with experimental kernels that often just lead to new issues is not the way to go

Looking through the thread, I don't see anyone else with USB problems.
Try the Samsung drivers.
 

k4bbe

Senior Member
Aug 1, 2011
545
429
London
Re: [ROM][4.2.1][16/02]Slim Bean - I9100 [Stable v1.0]

Yes, I m already on siyah kernel n activated BLN but does not work

Sent from my GT-I9100 using xda app-developers app

Must be an issue with your settings then dude as im running Siyah and its working fine. Perhaps now best to take the "issue" to the Siyah discussion thread.

Sent from my Nexus 7 using Tapatalk HD
 

sam5154

Senior Member
Feb 16, 2011
499
129
Does any one have issues with Siyah/Dorimanx "slide2wakr" option?
when this option is activated, digitizer register touches during phone calls, even when the screen is turned off by proximity sensor, it easily leads to mute a call, end a call or opening notification drawer and going to various parts of OS. I have the issue only in 4.2 versions, older versions were fine.
 

Didgesteve

Senior Member
Nov 24, 2011
1,698
1,029
Truro
Does any one have issues with Siyah/Dorimanx "slide2wakr" option?
when this option is activated, digitizer register touches during phone calls, even when the screen is turned off by proximity sensor, it easily leads to mute a call, end a call or opening notification drawer and going to various parts of OS. I have the issue only in 4.2 versions, older versions were fine.

I have seen that issue raised on the Dorimanx thread before, but you would have to search to find what the solution is, I don't use it as I find it eats batterys.
Not really a rom problem.
 

ko_is

Senior Member
May 29, 2012
75
12
Kistarcsa
Hi,
Sometimes I unable to unlock the screen. There is no response after I press home or turn on/off switch. The back of the phone is heater and heater. The only way to start again is pick up the battery or long press the turn on/off switch.
Any suggestion?

Thanks!
 

mcpdigital

Senior Member
Aug 13, 2012
420
122
Hi, here are my impressions about Slimbean RC1.

Smooth easy-rider ROM, I´m using it as primary and I feel is better than my other Samsung LS8 based ROM.
It runs everything without problems and always with good performance (no-OC here), no disappointment. Other benefit is that I have 225MB free system ROM while with the LS8 based one I have only 30MB free or less (same user apps on both). Amazing !

My GS2 is packed with applications, 350+ that range from root tools to Games, with 3 office suites bought at bargain prices. Lots of navigation stuff, Google Now active cards, Acid Audio Engine, Noozxoide DSP, Flipboard, Currents, Pulse, Feedfly, Zinio, Gplus, FB, Pinterest and all the other Google apps. Just naming some so one can figure out the type of use I have.
My phone is always connected and syncing stuff (Wifi or HSDPA), I do not have any special Kernel Wakelock that consumes too much battery. I have some entries in Kernel Wakelock but none of them uses more than 15 mins total time. Deepsleep is compatible with my type of use and is around 50% of the Powered on time.
Everything said, battery last only 12 hours with 1 hour display. I always change Kernels to try features or to upgrade but is always the same, around 12 hours. Note that I don´t blame the ROM, I blame all the components: myself, ROM and Kernel.


Some small problems that are always present since first install quite a while ago.

1-Booting: first the "Android is upgrading" message that appears. Then after unlock a system not responding message and then a Youtube not responding message. After that everything works as it should, no more FCs or strange error messages.

2-Some notification messages never appear, only after reboot. Like Google Play updates and GPlus. All notifications are set to on, but they only show after a reboot. Kind of annoying problem.

3-Sometimes, rare, the phone stalls. It got stuck in the same screen, navigation buttons emit the noise but nothing really happens. After some seconds phone is back to live and execute all the presses I did. Like pressed back two times or touched the screen.

4-After the last 2 upgrades, the notification bar option to slide the settings panel is using 50% of the not. bar size and before it was just on the extreme right of the bar. Turned it off for now.

5-HDMI doesn´t work. This is the reason is use the other LS8 ROM.

6-USB OTG connection mode doesn't seem to work either.

Final verdict. THIS IS THE ROM.

MCP
 
Last edited:
  • Like
Reactions: esperang

donny02

Senior Member
Mar 19, 2011
100
33
AW: [ROM][4.2.1][16/02]Slim Bean - I9100 [Stable v1.0]

Yes, I m already on siyah kernel n activated BLN but does not work.

I'm on siyah too and bln works fine. Found an option “backlight“ or so in “settings - display“ that has to be ticked too! If you dont find it I will have a closer look at it tomorrow.
IMO bln only works, when an app throws a message to status bar. I use the app light flow to get notifications from several apps.


Sent from my A700 using xda app-developers app
 

sam5154

Senior Member
Feb 16, 2011
499
129
Hi,
Sometimes I unable to unlock the screen. There is no response after I press home or turn on/off switch. The back of the phone is heater and heater. The only way to start again is pick up the battery or long press the turn on/off switch.
Any suggestion?

Thanks!

same here.
I can't find any special situation where this happen. seems completely random to me.
 

HardCorePawn

Senior Member
Mar 24, 2009
1,072
4,716
Auckland
Hi there,

first of all, a huge thanks to the whole dev team. This is one awesome new release.

However there is a couple of things I would love to see getting addressed :

Buggy stuff

1. The lower part of cLock widget is truncated on SGS2 at 210dpi (and even more at native 240 dpi). I know that it is possible to maximize the widget, but that's not really a solution.
Did you consider using DashClock instead?

2. "Voice input key" is not shown on main keyboard although the option is ticked. Showing it on symbols keyboard does work correctly though.

3. “Voice Dialer” keeps telling "Starting up..." when launched, but never gets ready in order to actually accept a voice command (not sure if this is app or ROM related)

4. Duration still isn't displayed correctly in call logs

5. USB Mass Storage/UMS : There is a strange behaviour that seems to be related to the computers' USB chipset.
Depending on the PC I have tested it with (and even depending on the USB 2.0 or USB 3.0 port on a same laptop) once you have turned it off, you will have to unplug and plug the USB cable before turning it on again, otherwise partitions will not be mounted on the computer. Most of the time it does not show the second confirmation popup (which is not useful anyway, I think).
Finally, why does it say "Connected as an installer" in the notification area?

6. MTP file transfer fails with error message on Windows when transferring certain files (seems to be related to capital letters and/or unsupported file extensions). Still investigating...

7. Transfer all files through BT [including APK] does not work, neither in Explorer+ nor in CM FileManager. Explorer+ app developer claims that the issue is system related as his app simply calls available share options from the system.

Missing stuff that used to be there in previous releases

8. "Performance" is missing some options like "CPU voltage" and "Startup tweaks", Init.d, zipalign

9. BLN support missing (was already gone in 3.x)

10. FastCharge feature missing

11. Option to disable SlimBean boot animation

12. Battery icon styles "icon with text" and "icon with centered text" missing (they used to be available and still are in AOKP 4.2.1)

13. No navigation bar and nice background in CWM (like in some earlier releases

14. USB Mass Storage in CWM does not work

I hope these features will be back soon.... ;)

Missing stuff that would be nice

15. Add EAP-SIM WiFi authentification method (necessary for hotspots like "FreeWiFi_secure" or "SFR WiFi Mobile" in France)
This used to work in SlimBean 3.1 by replacing the wpa_supplicant file in \system\bin with a version taken from a 4.0.x Samsung ROM.
However, in SlimBean 4.2.1 that procedure partly breaks WiFi support.
There are multiple references to EAP-SIM in "\system\bin\wpa_supplicant"
You might also want to have a look at here

Things I am wondering what exactly they are supposed to do

16. Is "Increasing volume alarm" that the same as "Added ascending volume option to Deskclock" (mentioned twice in change log) I cannot see any settings for these.

17. Whats is 5/8 targets selection?

18. What has been enhanced regarding GPS?

Regarding AIO Dark Gapps

19. Default app selection window is still white. Is that the intended behaviour?

20. Could you replace SMS icon with a Holo Blue couloured one?

21. Google calendar is old (non Play Store) version while in regular AIO the new version is included

22. Wouldn't it be nice to make stock Sound Recorder accessible from the app drawer (like in CM10 nightly) instead of that awkward Speech Recorder

23. Google Ears/Sound Search widget is outdated (it has to be unfreezed for users outside the US by using Market Enabler, then enabled and updated from Play Store)

24. Did you forget to update Play Store to 3.10.10 ?


Thank you,

ulysse

A "couple of things"? :p

1. Did YOU consider using DashClock instead? It is easy enough to install and replace the cLock widget with DashClock (I have done exactly this)... we are also in the process of determining whether we want to use DashClock or cLock...

2. I just installed the SREC_gnow addon... went into settings -> "language & input" and selected google voice typing... ticked mic on main keyboard, and it shows up... ticked mic on symbols and it shows up there???

3. Yeah... voice dialer seems bugged... it seems to generate an exception in logcat relating to BT headset service when you close it??!?... have you tried this on CM??

4. I honestly have no idea why this isn't working for some people? It works perfectly here... have you tried clearing phone and/or contacts app data and cache? Also, what language are you using? And I assume from your mention of issues with AIO Dark Gapps that you're using Dark Gapps... if so, does it do this on normal ROM + normal Gapps? ie. no dark framework or apps...

5. I believe it is triggered by a change in state of USB cable connected... so yes, you have to unplug and replug if you turn it off... otherwise the system can't detect the cable being connected. As for the "Installer" message, this is how it was implemented by CM ;) I'll add it to the ToDo list...

6. Can't say I've had too many issues transferring things with MTP... it just seems to work? But if you can find a method to replicate this error reliably, please let us know.

7. I just paired with my GF's i9000... and sent files via BT from various apps like QuickPic, default Gallery etc... and even downloaded and installed Explorer+... and yep... that works fine as well... you will need to check logcat for errors.

8., 9. & 10. Fairly sure these are all kernel issues... for technical reasons (ie. I have no idea about kernels :p) we are using the CM kernel... if you want these features, you'll either need to install a custom kernel, or ask the CM guys nicely if they plan on (re)implementing these features ;)

11. if you don't like it... just install a different boot animation... /system/media/bootanimation.zip... just make sure it is i9100 compatible...

12. we have icon with percentage... which I think is the same as icon with text... icon with centered text just looked horrible, which is why we removed it... also, this ROM isn't AOKP ;)

13. Yeah... touch recovery is a work in progess... be thankful, the default CM one has no touch... and is all volume, home and power buttons!! :p

14. Yeah... not sure why that UMS stuff isn't working in recovery... I suspect it might have something to do with the UMS being removed from the kernel and then re-added... don't count on this being added back in a hurry... as my knowledge of kernels/recoverys is pretty small (like non-existent small :p) But it annoys me as well... so is on the list of things to look at :)

15. Thanks for the link... but that is from Froyo??!?... Things have changed a fair bit from froyo to JB... and the WiFi drivers have issues as it is... again, due to the use of CM kernel, you might be better off seeing if they can implement it... I assume it doesn't work on CM either?

16. Yeah... volume starts low and slowly gets louder... you'll see the little checkbox when setting the alarm that says "INCREASING VOLUME"... as far as I know, there are no settings that you can mess with... I believe it starts at silent, and slowly increases to whatever your "Alarm Volume" is set to...

17. On lockscreen "Slide"... you can set targets on the lockring... you can either have 5 or 8... If you use 8, you might find the bottom 3 are sliced off, depending on screen size and/or dpi settings... not much we can do about it on i9100 due to changes in lockscreen design by AOSP... if you don't like the targets being cut off... use 5.

18. I think this was actually for other devices... and might actually have been reverted... for i9100, nothing should really have changed.

19. Will pass that on to Kufi...

20. You can do this yourself, most launchers will let you customise icons... I will pass on to Kufi tho...

21. I believe there was some issues preventing him from theming the latest one... google changed a whole bunch of stuff... and it was either not have dark calendar or have old dark calender...

22. never really used either tbh... I will look into the sound recorder...

23. & 24. I suspect that making these dark was the reasons for the issues and/or old versions... it isn't a simple task of "<color=dark>" in an xml file somewhere ;)


Hi,
Sometimes I unable to unlock the screen. There is no response after I press home or turn on/off switch. The back of the phone is heater and heater. The only way to start again is pick up the battery or long press the turn on/off switch.
Any suggestion?
Thanks, anyway I have already flashed Dorimanx v7.47. Is there any advantage of using Siyah kernel?
If this is happening with custom kernel... you'll need to take it up with them in their discussion thread... http://xdaforums.com/showpost.php?p=38312168&postcount=1177

If this is happening on stock ROM, I'll need logcat and last_kmesg etc...


Hi, here are my impressions about Slimbean RC1.
...<snip>...

Some small problems that are always present since first install quite a while ago.

1-Booting: first the "Android is upgrading" message that appears. Then after unlock a system not responding message and then a Youtube not responding message. After that everything works as it should, no more FCs or strange error messages.

2-Some notification messages never appear, only after reboot. Like Google Play updates and GPlus. All notifications are set to on, but they only show after a reboot. Kind of annoying problem.

3-Sometimes, rare, the phone stalls. It got stuck in the same screen, navigation buttons emit the noise but nothing really happens. After some seconds phone is back to live and execute all the presses I did. Like pressed back two times or touched the screen.

4-After the last 2 upgrades, the notification bar option to slide the settings panel is using 50% of the not. bar size and before it was just on the extreme right of the bar. Turned it off for now.

5-HDMI doesn´t work. This is the reason is use the other LS8 ROM.

6-USB OTG connection mode doesn't seem to work either.

Final verdict. THIS IS THE ROM.

MCP

Thanks for the vote of confidence... Also.. I assume you mean Stable v1.0??? not RC1???

1. We've had a few reports of YouTube FC on startup on various devices... can you provide a logcat next time you get it?
2. Can't say I've had this problem... is your data/wifi icon blue? If not, then that might explain the lack of notifications from play store and/or gplus, as you're not sync'd with google... perhaps you have data/wifi set to turn off during sleep??
3. Stock kernel? or custom?
4. People complain that it wasn't big enough area, now people complain it is too big... not much we can do... :rolleyes:
5. HDMI won't work on any "true" custom ROM... only Stock Sammy Based... blame samsung for lack of drivers...
6. Not sure about OTG... I don't have a cable to test... but as far as I was aware, you connect USB device and then went into Settings -> Storage and clicked the "mount" button at the bottom? What exactly is happening if you plug something in? I suspect this might be a kernel issue... Have you tried other kernels like DorimanX or tried on CM ROM?
 
Last edited:

djshotty

Senior Member
Oct 7, 2008
1,079
531
East Maitland, NSW, Australia
Bluetooth Phone Audio Failures

Switch to Siyah Kernel...
As a help to others, here are links to the kernels other posts in this thread have been making reference to...

Siyah kernel...
http://xdaforums.com/showpost.php?p=23810024&postcount=1

Dorimanx kernel...
http://xdaforums.com/showpost.php?p=25262098&postcount=1

Now, I myself am using the latest Dorimanx (V7.48), have tried the latest Siyah (V6.0b5) and also the Stock kernel (the one HardCorePawn has got in this latest ROM) only to experience the same issue -
NO BLUETOOTH PHONE HEADSET SUPPORT!!!
Every other ROM I have flashed on my i9100 hooks up to my Eclipse brand car CD player without any issue at all, then I can make calls with sound coming through the front speakers of the car. With an extension microphone right next to me, making phone calls while driving has never been so easy - until now. From the moment I flashed the latest release of SlimBean I have not been able to make calls whilst in the car through Bluetooth. The media audio is still fully operational, and I can play songs direct through the head unit via Bluetooth from the phone - even having the ability to skip tracks using the <<- and ->> buttons on the head unit.
After testing using a couple of other JB 4.2.1 ROMs (the latest AllianceROM + its Stock kernel, X-TremE JB ROM V.5 beta 1 with it's Stock kernel and CarbonRom 1.π » Feb 21 + Stock kernel) I have found the issue is definitely within SlimBean. Each time I flash I run hawkerpaul's ROMWipe script through Recovery, to ensure a clean install. Now, I'm not sure if it's the way the Phone Audio works with the Bluetooth drivers included in SlimBean, or whatever, so I'm hoping HardCorePawn can get a few minutes spare and check out what might be going wrong...
 

ulysse34

Senior Member
Aug 21, 2010
167
41
A "couple of things"? :p

1. Did YOU consider using DashClock instead? It is easy enough to install and replace the cLock widget with DashClock (I have done exactly this)... we are also in the process of determining whether we want to use DashClock or cLock...

2. I just installed the SREC_gnow addon... went into settings -> "language & input" and selected google voice typing... ticked mic on main keyboard, and it shows up... ticked mic on symbols and it shows up there???

3. Yeah... voice dialer seems bugged... it seems to generate an exception in logcat relating to BT headset service when you close it??!?... have you tried this on CM??

4. I honestly have no idea why this isn't working for some people? It works perfectly here... have you tried clearing phone and/or contacts app data and cache? Also, what language are you using? And I assume from your mention of issues with AIO Dark Gapps that you're using Dark Gapps... if so, does it do this on normal ROM + normal Gapps? ie. no dark framework or apps...

5. I believe it is triggered by a change in state of USB cable connected... so yes, you have to unplug and replug if you turn it off... otherwise the system can't detect the cable being connected. As for the "Installer" message, this is how it was implemented by CM ;) I'll add it to the ToDo list...

6. Can't say I've had too many issues transferring things with MTP... it just seems to work? But if you can find a method to replicate this error reliably, please let us know.

7. I just paired with my GF's i9000... and sent files via BT from various apps like QuickPic, default Gallery etc... and even downloaded and installed Explorer+... and yep... that works fine as well... you will need to check logcat for errors.

8., 9. & 10. Fairly sure these are all kernel issues... for technical reasons (ie. I have no idea about kernels :p) we are using the CM kernel... if you want these features, you'll either need to install a custom kernel, or ask the CM guys nicely if they plan on (re)implementing these features ;)

11. if you don't like it... just install a different boot animation... /system/media/bootanimation.zip... just make sure it is i9100 compatible...

12. we have icon with percentage... which I think is the same as icon with text... icon with centered text just looked horrible, which is why we removed it... also, this ROM isn't AOKP ;)

13. Yeah... touch recovery is a work in progess... be thankful, the default CM one has no touch... and is all volume, home and power buttons!! :p

14. Yeah... not sure why that UMS stuff isn't working in recovery... I suspect it might have something to do with the UMS being removed from the kernel and then re-added... don't count on this being added back in a hurry... as my knowledge of kernels/recoverys is pretty small (like non-existent small :p) But it annoys me as well... so is on the list of things to look at :)

15. Thanks for the link... but that is from Froyo??!?... Things have changed a fair bit from froyo to JB... and the WiFi drivers have issues as it is... again, due to the use of CM kernel, you might be better off seeing if they can implement it... I assume it doesn't work on CM either?

16. Yeah... volume starts low and slowly gets louder... you'll see the little checkbox when setting the alarm that says "INCREASING VOLUME"... as far as I know, there are no settings that you can mess with... I believe it starts at silent, and slowly increases to whatever your "Alarm Volume" is set to...

17. On lockscreen "Slide"... you can set targets on the lockring... you can either have 5 or 8... If you use 8, you might find the bottom 3 are sliced off, depending on screen size and/or dpi settings... not much we can do about it on i9100 due to changes in lockscreen design by AOSP... if you don't like the targets being cut off... use 5.

18. I think this was actually for other devices... and might actually have been reverted... for i9100, nothing should really have changed.

19. Will pass that on to Kufi...

20. You can do this yourself, most launchers will let you customise icons... I will pass on to Kufi tho...

21. I believe there was some issues preventing him from theming the latest one... google changed a whole bunch of stuff... and it was either not have dark calendar or have old dark calender...

22. never really used either tbh... I will look into the sound recorder...

23. & 24. I suspect that making these dark was the reasons for the issues and/or old versions... it isn't a simple task of "<color=dark>" in an xml file somewhere ;)

Thanks for your answers :)
I am starting over with a clean install now, even used GS2ROMWipe just like I always use to and Slim Gapps and SREC_gnow addon

1. I know that I can do that. I just thought that it would be in the interest of the average user ;)

2. No matter what I do, the voice input key isn't shown at all now. However, the option to enable this in under AOSP keyboard, not Google voice typing...

3. I have tested CM and AOKP. On AOKP i worked for sure, as for CM I don't remember very well but I think it worked.

4. It does work right now. I am using English most of the time and sometimes switch to French for testing purposes.

5. OK ;)

6. An example: I cannotcopy Slim_Gapps.zip but after renaming to SlimGapps.zip it's ok. I will let you know if I can figure out what exactly this is related to.

7. Did you try to share files other than pictures? Try to transfer an .apk or .xml file

8., 9. & 10. OK, I thought you were the kernel guy for Slim. Even when using a custom kernel these option are no longer available in Slim GUI (only via apps like STweaks). Never mind...

11. Just asking because there used to be a button for it.

12. The old "icon with text" in Slim Beam 3.0 looked much better than the new "icon with percentage"

13. OK just asking again as the feature suddenly disappeared some time ago ;)

14. Good

15. No no, it worked on Slim Bean 3.0 using the file from the first link, only the GitHub link is about Froyo

19.-24. OK thanks, I am wondering whether kufi themes all the dark apps himself or simply puts them together in a package.
For some or them you will be able to find "darker" versions on xda (more sub menus darked out)
 

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!