yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] AvRS:
If you just installed a kernel it re-builds the dalvik hence the "Android is upgrading". Try again if it's still doing it without wiping dalvik or installing anything, just a normal reboot, then you've got something weird going on.
[Galaxy S II Original Android Development] quijote1:
Yes, definitely weird! I've tried every imaginable combination of adjustments and every reboot gives the same result - but only when I boot into Slim. Weird!

Primary ROM : NeatRomLite XWLPY 4.0.4. 3.5

Secondary ROM : Slim Bean 4.1.2 v. 2.9

Kernel: Dorimanx 7.10 Mali

Modem NELP4

Apex Launcher
[Galaxy S II Original Android Development] AbyssTrion:
One more happy Member of Slim Bean. Tried many ROMs but after Week's of ParanoidAndroid I got back to Slim Bean.

Thanks for 2.9 :D
[Galaxy S II Original Android Development] ahm_salloum:
+1

I started using slim ROM a week ago ... and I will be really stupid if I think to go back to any other ROM :p
[Galaxy S II Original Android Development] HardCorePawn:
A quick Google search for "android is upgrading every reboot" shows lots of threads on various forums for a variety of devices and ROMs...

A quick read of a couple seems to point to a corrupted Titanium Backup as the culprit...

Try uninstalling/reinstalling TB...

If that doesn't work... Uninstall TB, reboot (twice, if it "upgrades" the first time)... Once it has stopped the upgrading on reboot... Try reinstalling TB...

Good luck...

Sent from my pwned SlimBean GT-i9100
[Galaxy S II Original Android Development] quijote1:
After 3 reboots it is still updating and I haven't put TB back yet. But thanks...

Primary ROM : NeatRomLite XWLPY 4.0.4. 3.5

Secondary ROM : Slim Bean 4.1.2 v. 2.9

Kernel: Dorimanx 7.11 Mali

Modem NELP4

Apex Launcher
[Galaxy S II Original Android Development] krarvind:
Alright everyone. This is now officially hardcorepawn's thread. He is the dm for i9100.

Cheers

sent from one of the slimmed device
[Galaxy S II Original Android Development] turner2914:
Hey I love the ROM except I keep getting music has stopped working whenever I try to open the app. Any suggestions on what may be causing this and how I can fix it?

Thanks for all the work too dev.
[Galaxy S II Original Android Development] HardCorePawn:
Without a logcat of the error... The only suggestion I have on what may be causing it is "solar flares" :P

Sent from my pwned SlimBean GT-i9100
[Galaxy S II Original Android Development] HardCorePawn:
Bugger... :(

Try going into DorimanX recovery -> kernel options and delete init.d and reset ExTweaks profiles, then select Default and reboot...

Maybe one of the kernel options got messed up...

And just as a tangent on this... I assume you've run "fix permissions"?

Sent from my pwned SlimBean GT-i9100
[Galaxy S II Original Android Development] quijote1:
Thanks, I'll try those things right now. But Slim is my secondary ROM and I'm not sure there is an option to remove init. d. But I can make Slim the primary and then I'll have all the options. Back in a while...
[Galaxy S II Original Android Development] HardCorePawn:
Yeah... actually meant to suggest that too... I noted from your sig it was secondary... was going to say try switching it to primary just to rule that out as a cause (some weird dual boot issue perhaps? :confused:)

Keep us updated :good:
[Galaxy S II Original Android Development] quijote1:
I tried all the above recommendations without swapping 1st and 2nd. Now my battery is low so I'll plug in and then make the swap. So far still updating!

Primary ROM : NeatRomLite XWLPY 4.0.4. 3.5

Secondary ROM : Slim Bean 4.1.2 v. 2.9

Kernel: Dorimanx 7.11 Mali

Modem NELP4

Apex Launcher

---------- Post added at 01:41 AM ---------- Previous post was at 01:17 AM ----------

I'm sorry to bother with this. Swapping the ROMs didn't work either. I'll keep trying things but with this exception everything works great. I'll just put up with it. Thanks.

Primary ROM : NeatRomLite XWLPY 4.0.4. 3.5

Secondary ROM : Slim Bean 4.1.2 v. 2.9

Kernel: Dorimanx 7.11 Mali

Modem NELP4

Apex Launcher
[Galaxy S II Original Android Development] HardCorePawn:
And I assume you have actually tried wiping cache and dalvik cache yourself from recovery?
[Galaxy S II Original Android Development] djshotty:
Much obliged...
[Galaxy S II Original Android Development] quijote1:
I did that when I flashed the rom. Should I do it again? Well I'll try anything! I'll let you know.

Primary ROM : NeatRomLite XWLPY 4.0.4. 3.5

Secondary ROM : Slim Bean 4.1.2 v. 2.9

Kernel: Dorimanx 7.11 Mali

Modem NELP4

Apex Launcher
[Galaxy S II Original Android Development] Mr.Greg:
Sir, I see somebody took your thread, but are you still development for s2? I mean will be more updates for s2?
[Galaxy S II Original Android Development] quijote1:
THAT DID IT! After the 2nd boot it booted correctly. Thanks.

Primary ROM : NeatRomLite XWLPY 4.0.4. 3.5

Secondary ROM : Slim Bean 4.1.2 v. 2.9

Kernel: Dorimanx 7.11 Mali

Modem NELP4

Apex Launcher
[Galaxy S II Original Android Development] CanadaJim:
Maybe hit the Thanks button as well...? I think he deserves it. ;)
[Galaxy S II Original Android Development] krarvind:
Not somebody :p. HCP is part of my team and slim is very much active for sgs2 as long as cm team continues to support (device and vendor files) when 4.2 rolls around.

sent from one of the slimmed device
[Galaxy S II Original Android Development] Mr.Greg:
Thanks Sir for answer.
[Galaxy S II Original Android Development] YaPaY:
I have a sync problem with this 2.9 Rom.

Exchange and gmail push alerts are open but sometimes these emails doesn't come. I'm checking the setting everything looks like ok.
[Galaxy S II Original Android Development] sepu79:
hi.

im thinking of install this rom

so i downloaded slim rom 2.9 and slim gapps.

what is aio addons,do i need install these too:confused:

thanks.

okey,did read little bit more. AIO addons includes allkind of stuff
[Galaxy S II Original Android Development] netban:
AIO = All In One

SGSII - Dorimanx - Slim Bean - AOKP
[Galaxy S II Original Android Development] HardCorePawn:
Glad you got it sorted :)

Hmm... Must have been a corrupted cache, so the system decided it needed to fixit... But wasn't able to, thus the repeated cycle...

Will note that down for future reference

Sent from my pwned SlimBean GT-i9100
[Galaxy S II Original Android Development] HardCorePawn:
Connecting via WiFi, mobile data or both?

If wifi, check to make sure that wifi is set to remain on during sleep... (wifi settings, "menu", advanced, keep wifi on during sleep)

If on data, goto settings, mobile data, "menu" and make sure the options around background data and autosync are set appropriately...

Also, are you running the default kernel or a custom one?

Sent from my pwned SlimBean GT-i9100
[Galaxy S II Original Android Development] turner2914:
I have problems with the music application force closing so I have attached a logcat so that someone may be able to help me fix it :)
[Galaxy S II Original Android Development] HardCorePawn:
Thanks for the Logcat :thumbup: :thumbup:

I'm away from my PC, so will investigate more thoroughly when I get a chance.

It looks like the app is attempting to load something at startup... And failing. Maybe last played song or playlist that has been moved/removed?

In the meantime... Have you tried clearing the app cache and app data for Music in System Settings -> Apps?

Sent from my pwned SlimBean GT-i9100
[Galaxy S II Original Android Development] turner2914:
I can try that right now

*Edit* I tried it and I cleared the data and rebooted and it is now working fine thank you for your help and keep up the good work! :)
[Galaxy S II Original Android Development] YaPaY:
Sleep policy off for wifi. I'm connecting with wifi.

auto sync data enabled

all others are disabled (not checked)

Kernel: dorimanxx 7.3 Mali
[Galaxy S II Original Android Development] wonsky21:
I'm checking SlimRoms website every day, but still no "3.0 WIP" :D
[Galaxy S II Original Android Development] krarvind:
Check github for progress

sent from one of the slimmed device
[Galaxy S II Original Android Development] marbutina:
Is possible to set a lockring with the profiles selector?

Thanks in advance.
[Galaxy S II Original Android Development] ophirb:
Good ROM as always.

All things, as far as I checked, works, the only thing that is a little uncomfortable is the over transparent notifications area that's make them difficult to read.

Maybe on next version you can make it selectable via settings.

Thanks

BTW using dori 7.13 kernel and Mixer theme, if anyone is interested knowing.
[Galaxy S II Original Android Development] ahm_salloum:
Hi m8 ... when I installed mixer theme ... notification becomes the way u says.

I used to use default system theme and set the trasperency to.0% and there was no transperency at all ... but with mixer theme it won't work seems to be
[Galaxy S II Original Android Development] kapica:
Hi, im new to Slim, 2.9 with latest siyah 5.0i..

I found one bug so far.. when using default browser embedded youtube clip on site crashes the browser...

/* One other thing, why arent there in settings in browser for Call options, as to set call waiting, forwarding and similar..? */ - ok, found it in phone -> settings.. kinda weird u cant find that option directly in settings

And sorry if that was already addressed..
[Galaxy S II Original Android Development] digitalH:
Hello im thinking about flashing slimbean for first time, but Im not sure what means "Gallerygoogle.apk which gives 3MP but allows for Picasa sync has now been moved to the OTA app"

Does it means the camera only take to 3MP pictures, not 8 ?

Sorry for the very stupid question ~
[Galaxy S II Original Android Development] Weeboab:
Not that I know of mine still takes 8mp pictures
[Galaxy S II Original Android Development] stebu79:
I'm facing a strange upgrade issue with slimbean 2.9. I'm with slimbean since 2.1 and it's the best ROM for me, currently I have 2.8 and dorimanx 7.14 (no second ROM) and I tried everything but I simply don't manage to upgrade, for sure I'm a noop... , as everybody else is on 2.9 without problems.

I tried to read through different forums and posts and I tried several times since 2.9 is out. I did a full wipe as recommended, I even flashed last cm10 nightly as recommended on another side before, still didn't work. After flashing 2.9 booting always stops at Samsung logo screen... any hint?

I feel ashamed to bother people in this forum, as I really appreciate all the work people invest in this ROM and I follow the thread as a regular reader. Or is there a better place to ask questions like that?
[Galaxy S II Original Android Development] Weeboab:
Are you trying to restore your data as well I had problems doing that had to redownload all my apps
[Galaxy S II Original Android Development] stebu79:
Well after flashing 2.9 and being stuck with Samsung boot logo I always have to flash with Odin to get to recovery and then I restore a nandroid backup to get back to 2.8
[Galaxy S II Original Android Development] HANDSY:
Tell us exactly what you are doing when you upgrade please.
[Galaxy S II Original Android Development] ophirb:
There is no transparency settings for the notifications area, you probably mean the status bar. It works also with mixer theme.

Cheers
[Galaxy S II Original Android Development] ahm_salloum:
Isn't this what u want ?
[Galaxy S II Original Android Development] ahm_salloum:
Double post
[Galaxy S II Original Android Development] CanadaJim:
I had the same problem with the upgrade. I had to do a full wipe (ie. Brand new phone), restore apps with settings, but not system data. Something in the system data from some configurations doesn’t upgrade well.

Running sweet now!
[Galaxy S II Original Android Development] quijote1:
I also had that problem with the upgrade. Did a full wipe and still got stuck at the Slim bootscreen. What worked for me is, when I was looking at the flashing Slim logo, I powered off with the power button. Then I powered on again after waiting 30 seconds. As I remember, the boot started over but this time it finished. I've had no problem ever since.
[Galaxy S II Original Android Development] stebu79:
A full wipe (formating data, dalvick,cache,system and internal SD card) didn't help either. I hope with slim bean 3.0 I can follow again.
[Galaxy S II Original Android Development] HardCorePawn:
Sleep policy off? I'm not sure what you mean?

Which one of the three options is selected?

-Always

-only when plugged in

-never (increases data usage)

Also, you might like to upgrade to latest DorimanX. Not sure exactly which versions it was, but some of the earlier 7.x versions had some WiFi issues. I believe 7.13 is the latest.

Sent from my pwned SlimBean GT-i9100
[Galaxy S II Original Android Development] HardCorePawn:
Do you mean the statusbar or the notification drawer? They are different... And at present, only the statusbar has transparency... Goto Settings, interface, statusbar and scroll to the bottom. Set transparency to 0% (or as you prefer)

No issues with embedded youtube in default browser here? :confused:

Try going to Settings, Apps... And clearing app cache and app data for the browser.

If that doesn't work... Please provide a logcat and some example webpage links that cause the crash.

And just as an FYI, the "phone" (aka Dialer) is technically an application... Can be replaced completely! So it's settings are part of the app, not the system... Same way SMS settings like ringtones, send/delivery reports are part of messaging "app" :)

It just means that there are a few camera/gallery versions... The one that supports syncing with Picasa, only takes 3mp pics, however this is not the default install. It is in the OTA (over the air) app (aka Settings, OTA, Apps) as an optional install for those that want Picasa sync.

The default camera has full resolution, but does not support syncing with Picasa.

Hope that helps to explain it for you :)

Sent from my pwned SlimBean GT-i9100
[Galaxy S II Original Android Development] HardCorePawn:
Have you checked the md5 checksum of the downloaded ROM zip on the phone? It sounds like it might be a corrupted file if it isn't getting past the samsung logo! :confused:

Just to confirm, you don't get the flashing SlimBean logo? Only Samsung one?

Sent from my pwned SlimBean GT-i9100
[Galaxy S II Original Android Development] ophirb:
Yes and you are right it is mixer theme problem. Switched to Cobalt and it is fine now.

Thanks
[Galaxy S II Original Android Development] stebu79:
Yes only Samsung... I'll try and download new and then flash again, tonight.
[Galaxy S II Original Android Development] Zetup-EXE:
Hi everbody,

tried to install slim bean as second rom. i installed the zip file(s) as second rom (slim-rom and gapps), and then the siyah v4.1.4 into the second rom (which is required to keep dualboot as far as i know. after reboot, i choose the 2nd rom for boot, black screen and ...nothin.

first rom still booting fine. :)

first rom is cyanogenmod 9.1 stable.

isn't it possible to mix this ?

any tip would be nice.

cu...

...and by the way, good work 2 all devs :good:

Zetup-EXE
[Galaxy S II Original Android Development] ophirb:
One thing to report is that camera fc when changing orientation. As far as I could see it does not fc if orientation does not change.

Regards
[Galaxy S II Original Android Development] GaboWinter:
Beautiful ROM! :eek: thanks and congratulations @krarvind and @HardCorePawn you have here an awesome work. Now this will be a must to my phone and my dad SGS.

Installed yesterday by night without any issue.

Minimalism FTW!
[Galaxy S II Original Android Development] AvRS:
Siyah 4.1.4? You need Siyah v5 whatever is the latest to use CM9 and JB ROM's together. I'm guessing that's your issue.

Took you long enough to find it :-p I've not gone back since the first ICS release all those months ago :cool:
[Galaxy S II Original Android Development] GaboWinter:
Hahaha I know it, honestly, I don't know why I've never tried it before, now I see that was a big mistake ;)
[Galaxy S II Original Android Development] ophirb:
I now can add that even without changing orientation every second photo it fc.

Just to make more clear.
[Galaxy S II Original Android Development] GaboWinter:
I've just test it right now and it's working fine, did you install some extra? Also, did you perform a full wipe?

Sent from Nyarlathothep's SGSII..."Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn"
[Galaxy S II Original Android Development] ophirb:
I did a full wipe but now come yo think of it I am using Dorimanx kernel so maybe the problem is there.

Is there a flashable stock kernel?
[Galaxy S II Original Android Development] AvRS:
Check this post of mine as has everything you need to get the stock kernel from the original zip file flashed.
[Galaxy S II Original Android Development] ophirb:
I was on 220dpi changed to 240 and it seems to work now.

Thanks
[Galaxy S II Original Android Development] ahm_salloum:
Nice to see u hear gabo ... in serious I dunno why this ROM is not soooo popular ... maybe "original development " forum is not popular as the normal development

Even my self ... only 3 weeks since I found this ROM ... and I still never even think to go back to any other ROM .... and now it is flashed into 4 of my friends mobiles (1 of them got S3 and 2 galaxy i9100G and the last normal 9100 ) all of them are very happy

Looking forward for new versions ....
[Galaxy S II Original Android Development] stebu79:
So I tried again with a new downloaded slim bean 2.9 from the slim-website and again no success, stuck at Samsung logo...
[Galaxy S II Original Android Development] xflowy:
hey. nice rom! about to donate!

just one question: why does my notification bar changes to an ugly grey when starting most of applications?

btw. u should move to non-original section.
[Galaxy S II Original Android Development] HANDSY:
It's to do with the transparency settings, experiment with the settings until you have what you want
[Galaxy S II Original Android Development] xflowy:
you mean the transparency scale in settings, which is 30 on standard? if i chane it, nothing changes.
[Galaxy S II Original Android Development] GaboWinter:
Change it to 0, then back to the previous menu and back again to the statusbar settings, check if the percentage it's not reverted, the first time that I set it to 0 revert it alone so, I put it again to 0 and now works fine, status bar in black.
[Galaxy S II Original Android Development] CanadaJim:
Status bar transparency in interface settings.
[Galaxy S II Original Android Development] HardCorePawn:
As the others mentioned, it is a transparency setting...

it lives in: System Systems -> Interface -> Statusbar.

There is a slider at the bottom labelled "Status Bar Transparency". If you set this to 0%, it should stop the "grey" effect.
[Galaxy S II Original Android Development] HardCorePawn:
Bizarre that it isn't making it past the Samsung logo??? :confused: It would seem to indicate that either the Kernel is not loading correctly... or the Kernel is unable to start the ROM.

Are you able to connect the phone via USB and get logs of the boot process?

Assuming you have ADB setup, you can do an "adb logcat" (no quotes) and it should sit at "waiting for device"... you can reboot the phone and plug it in. Hopefully it will then start spitting out all sorts of startup logs.

Also, hopefully you could "adb shell"... then "dmesg > /sdcard/kernel_boot_log.txt"

Then copy the kernel_boot_log.txt from the sdcard to your computer (ie. adb pull /sdcard/kernel_boot_log.txt /path/on/local/PC/kernel_boot_log.txt)
[Galaxy S II Original Android Development] eths83600:
I'm still having random freezes and sods.

I'm using the kernel that comes along, without modifying anything.

I did fully wiped and formatted everything
[Galaxy S II Original Android Development] 0blivious:
Great ROM! This is the first one I have installed (using philZ safe kernel v4.0.3) after being 1,5 year on stock everything (and putting up with it!).

So thanks, I feel that my s2 is finally what it should have been (speed/features/look)..

Ok, so here I am submitting what I found were problems/bugs after using this rom (v2.9.0) from almost 2 days constant using/testing (hey it's like a new phone so I'm working the **** out of it :) ).

Don't know if these are known problems/bugs;

Touchkeys: Backlights don't stay lit.

I personally like my touchkeys backlight always on, so I set the setting in device options>screen>touchkeys>backlight timeout to never.

How to replicate:

But once the device goes on standby (or I press the standby button), the touchkeys don't light up. They stay unlit as if the backlight was disabled. I have to go back to device options, disable & enable backlight.

Now I just set it to 6 seconds.

Standby: Lock Screen bypassed.

I don't know if this is a bug or a feature, but if it is a feature: pretty cool.

How to replicate:

When the device goes on standby after the timeout (only tested this with 15seconds timeout) if you press the home hardware key within 5 seconds, the software never shows the lock screen and just wakes the screen (and you return to where you were). If you press it after 5 seconds it will show you the lock screen.

So personally I just think this is a cool feature (which maybe could have an option somewhere "bypass lock screen after timeout within [...list] seconds", but I'm just mentioning it because it seems inconsistent.

Either way, there are a few other things that go wrong like the launcher that hanged/crashed, as does the Statusbar; but those happened once and I'll report back when I run into it again and found a sure way to replicate it.

I do have a question about something;

I regularly got the message that my google play service (or something of the like, I should've written it down!) is not up to date or something is wrong with it, so removed it with Titanium, but after a while the message returned. I don't think I need this app/service, Google Play works as it should without it, it seems.

Anyway, thanks again for this cool ROM! (I have installed the AIO pack and removed google music with Titanium) Keep up the good work!
[Galaxy S II Original Android Development] Zetup-EXE:
That does the trick ;) - Thx.
[Galaxy S II Original Android Development] AvRS:
You should look at the differences in this ROM and the copies of ROM's in that section and you'd know this doesn't belong in the other section. This has been discussed numerous times and doesn't really matter on opinion as it's here for a reason. Personally I've never flashed a ROM from the other section and never will, they're all too similar and seems any man and his dog now winzips a ROM together with a theme/a few mods and calls it a ROM.Oh well....
[Galaxy S II Original Android Development] HardCorePawn:
Without logcats or kernel logs... I can only deduce that your problems are caused by:

"overflow error in /dev/null"

:rolleyes:
[Galaxy S II Original Android Development] kapica:
..so.. i did a clean slim 2.9 install.. using dorimanx 7.15 ...

And everything works fine...

Except autofocus on camera is terrible, instagram camera is better, so this is a little dissapointing...

What i think is a bug happened yo me last night.. i left mh phone on charger, and when i woke up, i noticed my weatherpro widget frozen.. and i got FC on com.mg.android something...

Ok, i go restart, and after it i lost some apps...

BBS, news&weather, skin for gosms.. how can this happen?