SlimKat is smooth and gave me highest Antutu score of all KK roms on my i9000 (I think about 5030 with Mackay kernel, about 4980 with stock kernel), but its UI doesn't feel so fast. I trust my feeling more than Antutu.
tetakpatalked from P5110
SlimKat is smooth and gave me highest Antutu score of all KK roms on my i9000 (I think about 5030 with Mackay kernel, about 4980 with stock kernel), but its UI doesn't feel so fast. I trust my feeling more than Antutu.
tetakpatalked from P5110
Besides, Phil3759 has just discovered that CWM has a bug since longer time: it prompts by exit / reboot system if the device should be re-rooted (SU installed).
Regardless of your choice, it will not be re-rooted. And nobody else noticed this since about half year, LOL
So TWRP and PhilZ by all means recommended (IDK if stratosk has debugged this in SlimKat stock Semaphore CWM recovery)
tetakpatalked from P5110
My girlfriend got an weird unwanted reboot to recovery an su / reinstall prompt yesterday... Never saw that before... And there is no root problem, I ignore the message and reboot without "fix".
Pretty weird that this kind of behavior appear from nowhere. Easter egg in cwm?
Just found that funny that you mention that bug now
. Never heard of it before lolEnvoyé de mon Nexus 5 en utilisant Tapatalk
Hah, now it works like a charm :3 Just a little bit slower than slimbean, but i assume it'll be improved
One thing i really miss is the "kill all" button in recent apps...
Thanks again tetakpatak, it's been very kind of you to help me so quickly :highfive:
Long press home button and pinch in.
Sent from my GT-I9000 using Tapatalk
That prompt actually isn't so seldom. But if the device is properly rooted (especially if you use SuperSU) the bug has no any influence.
tetakpatalked from the legendary i9000
I've been testing a workaround for incallui delay, seems like if lmk white list included incallui, and once a first call has been received since first boot, the call screen delay isn't so bad after all. I found this app callled autostart - no root on the play store and had the dialer start on boot, assuming this might reduce the time needed to load on first call after boot.
You're welcome mate!
SlimKat is great ROM, but IMHO our phone can't handle KK so good, I doubt it will get as fast as SlimBean was. Pity we have no SlimICS, I really miss Slim's the dark mode now.
Mackay kernel can boost your SlimKat performance a bit (and provide satisfying call volume) and deinstalling some performance-and-battery killing apps like Viber, Whatsapp, Facebook, Hangouts, YouTube and Google location services can also help.
You can enable customizing hardware buttons and for example use long press for back button to kill apps.
tetakpatalked from N7100
@tetakpatak you have been kept busy.
I have the SlimICS downloaded but this might not be the place to talk about it.
Oh, obviously I have totally missed it
I'm gonna browse imediatelly!!!!!!
Thanks a lot, mate!
tetakpatalked from the legendary i9000
GREAT! That's really useful, thank you so much
I don't use Whatsapp\Facebook...should I delete hangouts even if i don't use it? And what about youtube? What's the best way to watch videos without the app? If you have any reference topic about these facts i'd be glad to give it a look
how to fix unknown baseband and IMEI ?
Return to gingenbread with Odin...
Sent from my GT-I9000 using xda app-developers app
how to fix unknown baseband and IMEI ?
Do a search in the i9000 general forum , you will found all kind of guide, tutorial and random thread from person sharing how they fix.
Keywords : imei
Envoyé de mon Nexus 5 en utilisant Tapatalk
yes i am back everything ok now;
but i want Kitkat
Hey man, I just had the same problems two pages ago... check this post that helped me solving my problems
http://xdaforums.com/showpost.php?p=52025160&postcount=851
New phone
Hi all devs and friends... I have gone ahead and purchased a Nexus 5. Its an incredible phone and am enjoying it a lot. Needless to say, I had its bootloader unlocked, rooted, installed custom recovery and custom kernel within the first hour of getting it.
I still have my trusty SGS i9000 which I have filled up with games and given to my little daughter. I will now be sharing time between SGS and N5 forums now. Will never actually leave SGS forums I guess
Nevertheless, I thought this to be as appropriate a time as any to thank all the wonderful devs and friends here who help out each other and keep the SGS relevant even after more than 3 years... kudos to all!!! :good:
PS: you will see this message in different threads... that is because I owe this to many devs and don't want to miss out thanking any of them.
Hi all devs and friends... I have gone ahead and purchased a Nexus 5. Its an incredible phone and am enjoying it a lot. Needless to say, I had its bootloader unlocked, rooted, installed custom recovery and custom kernel within the first hour of getting it.
I still have my trusty SGS i9000 which I have filled up with games and given to my little daughter. I will now be sharing time between SGS and N5 forums now. Will never actually leave SGS forums I guess
Nevertheless, I thought this to be as appropriate a time as any to thank all the wonderful devs and friends here who help out each other and keep the SGS relevant even after more than 3 years... kudos to all!!! :good:
PS: you will see this message in different threads... that is because I owe this to many devs and don't want to miss out thanking any of them.
If one still gets the „google.play.services” error, do the following:
Re-enable Hangouts. Go to Google Play. It will tell you to update Hangouts. Press on update (Hangouts, yes?) - and now it will tell you that you need to update Google Play Services. Do just that following the prompts. When you're done, you may disable Hangouts again.
Thanks, devs!
Re-enable Hangouts. Go to Google Play. It will tell you to update Hangouts. Press on update (Hangouts, yes?) - and now it will tell you that you need to update Google Play Services. Do just that following the prompts. When you're done, you may disable Hangouts again.
Thanks, devs!
Is it Just me or anyone else getting a delayed processing on "Google hangout"? Like, when some one tries to call you on hangout, you get a immediate call on web while a long delay and then on App.
If it's a bug and if you need any specific logs, I'll be very glad to put up the logs.
or Does it help if I over clock my CPU?
Now the Question put, I want to thank all of those involved with Slim ROMs, as this made a great difference to people like me who still use GT-I9000 as a primary phone. You guys have made this device Amazing, It's like using a new device with enhanced function. SLIM ROM is the only reason my phone is alive.
And I am using the latest Stable Release and not the Weekly.
If it's a bug and if you need any specific logs, I'll be very glad to put up the logs.
or Does it help if I over clock my CPU?
Now the Question put, I want to thank all of those involved with Slim ROMs, as this made a great difference to people like me who still use GT-I9000 as a primary phone. You guys have made this device Amazing, It's like using a new device with enhanced function. SLIM ROM is the only reason my phone is alive.
And I am using the latest Stable Release and not the Weekly.
Last edited:
Call Screen Delay, possible workaround 2
a while back I noticed using LMK whitelist to make com.android.incallui bulletproof helped with the screen turn-on delay, then a few pages back someone claimed removing Hangouts apk from system made the problem less pronounced.
Upon a bit of calling myself and looking at Greenify, it appears that Hangouts starts itself using the "apps.babel.phone.PhoneStateReceiver" receiver upon receiving a call, and cutting this off reduces the time needed for the screen to light up!
Moral of the story, if you don't use Hangouts, uninstall it. If you do, cut off that receiver.
a while back I noticed using LMK whitelist to make com.android.incallui bulletproof helped with the screen turn-on delay, then a few pages back someone claimed removing Hangouts apk from system made the problem less pronounced.
Upon a bit of calling myself and looking at Greenify, it appears that Hangouts starts itself using the "apps.babel.phone.PhoneStateReceiver" receiver upon receiving a call, and cutting this off reduces the time needed for the screen to light up!
Moral of the story, if you don't use Hangouts, uninstall it. If you do, cut off that receiver.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
94
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:- The Real Dark Slim
- Full system-wide dark interfaces. - If you like it smooth and classy.
- Custom Shortcuts. Everywhere.
- Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
- System-Wide Keyboard Controls
- Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
- SlimCenter
- Downloads, contact information, system app removal. - More fun than you can shake a stick at.
- Camera Features
- Trueview, Smart Capture. - Capture life moments with ease.
Important links:
SlimRoms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom, gapps and other addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms Team is not responsible for any damages to you or your device.
XDA:DevDB Information
[ROM][4.4.2] SlimKat - I9000 [STABLE!] , ROM for the Samsung Galaxy S I9000
Contributors
mnazim, SlimRoms
Version Information
Status: Testing
Created 2014-05-19
Last Updated 2014-05-1938WARNING!
NOTE:
- Keep in mind that this are early Beta builds!!!!!! Means bugs can happen. So please only use this builds if you want to help us and iron out the bugs with proper bug-reports etc.
- If you get error while flashing, go to advanced->reboot to recovery and flash again.
- If you get SU issues, flash SuperSU v1.80.zip from chainfire's thread.
BUG REPORTING
When you submit a bug-report, you want to make sure that nothing from your side is causing it. Otherwise we might be hunting a bug which doesn't really exist.
The best way to achieve this is by doing the following.
- Make a nandroid backup.
- Perform a full wipe (factory reset + wipe /system) Now we have two different ways depending on what kind of problem you're having.
- When you're having a problem with a ROM function, flash just the ROM without GAPPS, and boot back into the system. You will boot directly onto the home-screen.
- When you're having a problem with a 3rd party app in combination with our ROM then flash the ROM and GAPPS.
- Boot now back into the system. You will boot to the setup wizard. Log in to your Google account but make sure that you untick "Restore from my Google Account to this phone/tablet". Finish the setup and open the playstore and download only the app you're having problems with.
- Start a logcat recording and reproduce the bug (if possible more than once) while taking the logcat. If you don't know how to get a logcat read this tutorial or this.
- Post the logcat in a text file (this is important because you otherwise clog up the threads with your log) in the correct thread. Please also write detailed description how we can reproduce the bug.
- Restore your backup from point 1 and wait for a fix (PLEASE don't ask for ETAs).
25mnazim our device maintainer (DM) isn't active anymore, so our build is still labeled weekly. so we are not at a stable stage as there are issues no one is looking after.
i just hope mnazim can return or some dev can pick up where mnazim left. but that seems unlikely for the old SGS.
Stable is just a tag guys... We will push out weeklies as long as possible for the i9000... This device is just too vintage to let go so easily...19 - The Real Dark Slim
