yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Sun90:
Find the same att ma8 :)
[Galaxy S II Android Development] anuradha96:
Thank you !! I put this to system-apps and set the permissions..but I can't set the widget in the lockscreen :(
[Galaxy S II Android Development] Phenomzye:
What is happening right now on Recents panel? still using SlimRecents? Did they implement a button instead of a gesture to clear all?
[Galaxy S II Android Development] Harsha Raj:
Still SlimRecent, which IMHO is better than stock recent panel. And AFAIK, button to clear all apps isn't coming to SlimRecent.
[Galaxy S II Android Development] Heraku:
Do a pinch to zoom from top/bottom to the middle :silly:
[Galaxy S II Android Development] Rizsparky:
Although this is an adequate method for clearing apps, its not very responsive. A button would be much better.
[Galaxy S II Android Development] Twiq:
This a method to stop users from clearing apps, that is a bad habit since it also messes up the android memory management and cause problems later

Running 0416 Sabered SlimKat | DorimanX 10.43v108
[Galaxy S II Android Development] velocity90:
Hi,

I'm ready to try this rom. Im coming from neatrom and want to try this one because of an annoying problem. Might be slimrom based so I'll ask here.

When my phone is in sleep for a while i don't receive any messages. When I unlock and look at the tiles, both wifi and phone are orange. If I wait some seconds they turn white and I receive all my messages /whattsapp.

No wifi powersafe is on and connection is always on.

Is this a known issue with this rom?
[Galaxy S II Android Development] Hopper8:
I've never had that issue, but I can't say how you will go obviously. Best thing to do is make a nandroid, flash SlimSaber and see how you go [emoji106]

Sent from a galaxy far, far away
[Galaxy S II Android Development] aca89:
So what happened with the sd card (music) bug? I know there was some sort of workaround but I'm not sure if it's still working. I'd like to try this rom but this is a deal breaker for me.

Thanks
[Galaxy S II Android Development] Adevem:
as far as I know, it's been fixed. media wakelock's pretty much gone too.
[Galaxy S II Android Development] velocity90:
Yes, on slimsaber now and same problem. It wasn't there a view versions back. This is driving me nuts. Fresh install:confused:
[Galaxy S II Android Development] razen_kain:
Hey i had this same problem. I tracked it down to my Wi-Fi router but there is also an app linked there that may help you. It's called push notification fixer.

http://xdaforums.com/showthread.php?p=51941786
[Galaxy S II Android Development] j1gga84:
It is not fixed yet, there is only a workaround out but the problem is still (but less) presence.

For the newest infos, check this out: http://xdaforums.com/showthread.php?t=2612329

Regards
[Galaxy S II Android Development] Computoncio:
So resuming maybe media scanner is ignoring .nomedia file and scanning directories that mess up and stuck media scanner.

If you didn't post it in slimkat thread you should, so dev's can take a look at it.

Great debugging mate, that's what we need.

Slimsaber 0416 running perfect here, no issues at all.

Phone: Samsung Galaxy SII - GT-I9100

Kernel: Dorimanx kernel v10.43v108-mv3

1st ROM : SlimSaber 4.4.2 Maliv3 by fusionjack build of 20140416 (Online)

2nd ROM :

MODEM: UHMS1

MODS: Partition Fix, Hue Blue v4.4 by Kroz :good:
[Galaxy S II Android Development] hawaiisteve:
I haven't but I will now. Always nice to get a compliment!
[Galaxy S II Android Development] Bogeyman13:
For me the bug has gone. After the workaround it didn't happen any more, and I'm listening to music every day.
[Galaxy S II Android Development] 78apb:
Is there something as perfect as SaberMod Slim for Galaxy S4 i9505?

Can anybody recommend by personal experience? I like that it is fast, smooth and slim (no extra ware).

Sorry for offtopic, please, answer in PM.
[Galaxy S II Android Development] fusionjack:
With my limited knowledge, it looks like an app problem:

08-04 21:53:09.404 E/AndroidRuntime(4062): FATAL EXCEPTION: main
08-04 21:53:09.404 E/AndroidRuntime(4062): java.lang.NoClassDefFoundError: robj.floating.notifications.NotificationListener
08-04 21:53:09.404 E/AndroidRuntime(4062):	at robj.floating.notifications.WindowStateChanged.onAccessibilityEvent(WindowStateChanged.java:30)
08-04 21:53:09.404 E/AndroidRuntime(4062):	at android.accessibilityservice.AccessibilityService$1.onAccessibilityEvent(AccessibilityService.java:523)
08-04 21:53:09.404 E/AndroidRuntime(4062):	at android.accessibilityservice.AccessibilityService$IAccessibilityServiceClientWrapper.executeMessage(AccessibilityService.java:589)
08-04 21:53:09.404 E/AndroidRuntime(4062):	at com.android.internal.os.HandlerCaller$MyHandler.handleMessage(HandlerCaller.java:40)
08-04 21:53:09.404 E/AndroidRuntime(4062):	at android.os.Handler.dispatchMessage(Handler.java:99)
08-04 21:53:09.404 E/AndroidRuntime(4062):	at android.os.Looper.loop(Looper.java:137)
08-04 21:53:09.404 E/AndroidRuntime(4062):	at android.app.ActivityThread.main(ActivityThread.java:5232)
08-04 21:53:09.404 E/AndroidRuntime(4062):	at java.lang.reflect.Method.invokeNative(Native Method)
08-04 21:53:09.404 E/AndroidRuntime(4062):	at java.lang.reflect.Method.invoke(Method.java:511)
08-04 21:53:09.404 E/AndroidRuntime(4062):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:794)
08-04 21:53:09.404 E/AndroidRuntime(4062):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:561)
08-04 21:53:09.404 E/AndroidRuntime(4062):	at dalvik.system.NativeStart.main(Native Method)

The app cannot find a file (java class) that should be existed in the app itself.

Did it work on the previous build?
[Galaxy S II Android Development] ercxar:
I'm feel like build 07/28 was battery friendlier than these two latest releases! Not very much difference though.
[Galaxy S II Android Development] Truman82:
What kind of governors so people here go with, that is when using sabermod kernel? Been trying different ones, and can't really see difference in any :-$

Swiftkey'ed from my i9100 using tapatalk 4 beta
[Galaxy S II Android Development] dante_67:
I think it all depends on your environ, like how have you set the phone, what are the always on application, your location, signal strength, even use can be different on day to day basis, for me generally, the battery has been very good so far

---------- Post added at 01:43 PM ---------- Previous post was at 01:35 PM ----------

Generally there are some performance differences, i prefer zzmoove, because on demand gives me a hot phone with minimal use. And i prefer sio as over row in io scheduler, that combination gives me a very smooth performance, I am using Dori's latest Kernel
[Galaxy S II Android Development] deviatesaw:
Anybody else having proximity sensor and gyroscope issues after a few hours of uptime? All of a sudden my proximity sensor doesn't work and auto rotation won't work even when I know its turned on. A reboot solves this. I love this ROM and its perfect apart from this tiny issue.

Stock kernel used also.
[Galaxy S II Android Development] 78apb:
- none of them. I read a lot with Cool Reader. And I use "auto=sensor" orientation option, works perfect for hours of reading.
[Galaxy S II Android Development] GNUDroid:
New Mali blobs flashable zip

There are new mali-blobs implemented in the latest CM10.1 sabermod builds from infected:

“Today, 04:11 AM Infected_

New build 20130805 UPLOADED..

PS: added new leaked MALI 400 blobs r3p1-01rel1 25 Jul 2013”

--> http://xdaforums.com/showthread.php?t=2339377&page=74

Just because of curiosity, I took the old mali-blob-update zip from codeworkx in May this year and put the new lib files from the CM10.1 by infected_ into that zip (do nandroid, flash in recovery).

The new binary leak seems to work fine in slimbean sabermod!

I do not see any outstanding benefit from that until now, but to be honest, I did no benchmark or even started a game…. but since they work, I share for all ‘flash-junkies’. ;). (I’m still on 01082013 build)
[Galaxy S II Android Development] Minfreak:
Floating notification 1.4, 1.3 work very well with Any Slim bean build but v1.5 (last) dont work :(

Enviado desde mi GT-I9100 usando Tapatalk 4
[Galaxy S II Android Development] Nos_20:
I have flashed the new Mali zip. My phone hasn't blown up or melted!

Everything seems to work OK. Although not tried any games or anything yet :D

Sent From My Galaxy S2

Running SlimBean SabreMod 4.9

Powered By DorimanX Kernel v9.35
[Galaxy S II Android Development] djsky2011:
What is the date of this new Mali you are talking about any links?
[Galaxy S II Android Development] Nos_20:
Check the previous page, it was posted there.....

http://xdaforums.com/showthread.php?p=44307765

Sent From My Galaxy S2

Running SlimBean SabreMod 4.9

Powered By DorimanX Kernel v9.35
[Galaxy S II Android Development] wonsky21:
Oh, you got to be kidding...

Sent from SGS2 powered by Dorimanx kernel
[Galaxy S II Android Development] ercxar:
Yeah I know. That was why I mentioned it here. Cause my usage is very similar everyday and I can feel the difference with same usage even same settings.
[Galaxy S II Android Development] djsky2011:
No not kidding I thought there was a newer one to the 25th July Mali which is why I said what's the date ;)
[Galaxy S II Android Development] m1trand1r:
guys...

what do you think?
[Galaxy S II Android Development] ercxar:
Did you use 3G on that entire period?

It's very good indeed. Still with half of your battery juice remaining!

Take a look at my screen time with build 07/28
[Galaxy S II Android Development] m1trand1r:
yep..3g always on....even when screen off:)...
[Galaxy S II Android Development] fusionjack:
07/28 is the last build before i compile with -O3.

let's observe further how the battery consumption goes...i didn't notice anything until now. :D

that should fine as long as from cm. ;)

make sure the file list is the same with the previous one.

i just did a little search on mobile but didn't find any commits regarding new mali.

good...that proves my observation. it is app problem.
[Galaxy S II Android Development] ercxar:
wow I must confess that my jaw dropped on table now. lol:D Cause when I switch to 3G network even when data network is Off. My battery consumption will increase triple times than 2G! I know that 3G uses more battery but I don't think that much! I don't know if I have to blame my operator (I think that's the one) or other roms that I've been using.

IMHO that's a hell of battery usage! :good:

I should mention that before 07/28 release there were builds which not battery friendlier as 07/28 was. So I don't blame it on -O3 thing. :D

Yeah we should wait and see further what will happen. :good::D Anyway battery consumption is way better than any other roms that I flashed except MIUI!!! :D SleamBean SaberMod is the best. WooHoo!:D:p:o
[Galaxy S II Android Development] hawaiisteve:
Im not experiencing the music stopping since the workaround also. The sticking media scanner I'm talking about happens randomly when scanning or sometimes when opening files with es explorer or any file manager. The scanner gets stuck on a file it can't read and just runs forever.
[Galaxy S II Android Development] CounterC:
Music also fine here.

Still having issues with Google Camera. It works on startup but I cannot get into the settings, keeps crashing. On other ROMs settings didnt crash and I could enter the menu (only crashed when trying to change resolutions). Anyone experience same behaviour? It seems ROM related...
[Galaxy S II Android Development] clock51:
I solved with the app "Snap Camera" you can find on the playstore
[Galaxy S II Android Development] CounterC:
Hi, thanks for answering but I already own Snap Camera since a long time.It is one of the best camera apps out there.

Still in the Google Camera I find features that no other camera has. On SlimSaber I have issues with it.

Anyone knows solution?

PS: Already flashed compatibility fix from SlimRoms.
[Galaxy S II Android Development] clock51:
you have locked the camera and the default gallery? I stuck with TitaniumBackup
[Galaxy S II Android Development] CounterC:
I tried that but same result...
[Galaxy S II Android Development] razen_kain:
This ROM is extremely fast. Nice job. Running it on straight talk's i777 aka 959g
[Galaxy S II Android Development] wassk:
whats the point that i cannot find google camera with my phone on google play, but i can find it on computer....??
[Galaxy S II Android Development] changlung:
with 04/16 SlimSaber and Dorimanx kernel, after I disable image show for bowser , I can not enable it on the browser settings menu. I has to clear the app data to enable it.
[Galaxy S II Android Development] velocity90:
Thank you, testing it now:thumbup:
[Galaxy S II Android Development] aca89:
Hi guys, I have annoying problem, here's what's happening. I flashed slimsaber JB edition (for me it's a perfect balance between battery and latest sw) and occasionally I completely lose signal AFTER a reboot. When I enter 'settings - about - status' it states that I have unknown baseband, no imei, I'm out of service. I can fix it if I turn of the phone and take out the battery. I don't understand why this is happening.

Before this I was using neatrom lite. Here's how I installed it (official instructions from slim website).

Flashed cm10.2 compatible recovery (tar version via Odin), booted cm10.2, entered recovery, wiped data, formated system, flashed latest slimsaber jb edition posted in op together with slim gapps, flashed Gustavo's kernel.

Have I done something wrong, maybe it's modem-ril connected? It's xxms3 btw.
[Galaxy S II Android Development] pippone121263:
try to flash the slim kernel and flash again slim rom I had this problem after fleshing apolo kernel with slimsaber 4.4.2, soved it flashing slim kernel and rom

hope it can help
[Galaxy S II Android Development] aca89:
Thanks for responding but I was hoping to use Gustavo's kernel if possible of course.
[Galaxy S II Android Development] fusionjack:
see if you have any apps that could turn off wifi or 3g on screen off. [MENTION=4851213]Hopper8[/MENTION]: yes, there is some conflicts with the last merge. i have resolved it.

@ all: i'm still busy, so can't text much
[Galaxy S II Android Development] Hopper8:
They are doing my head in ;) but if you have resolved them, I will look on your github and see what I can do :)

Sent from a galaxy far, far away
[Galaxy S II Android Development] fusionjack:
unfortunately i forgot to submit the latest upstream sync to my github. [emoji45]

now i don't have time to submit it since i'll be away again from home starting today. i'll update it as soon as i'm available again.
[Galaxy S II Android Development] Hopper8:
No worries. I am still trying to resolve conflicts but it's a steep learning curve for me. [MENTION=4620275]Nico_60[/MENTION] is helping me, so HUGE thanks to him :) No rush at all, enjoy your break! :D once you do manage to push to github I think I can build for everyone. I am hoping to be able to build before you have to push back to github though, by resolving conflicts :)
[Galaxy S II Android Development] Flegias:
Hi all,

Everything goes great with this ROM except for one thing:

Everytime I reboot my devices the screen won't turn off for 5/10 minutes! Even if I push the lateral button.

After some minutes the screen turn off and finally I have the lockscreen to turn on again.

I had this problem even after the flash of the updated version!

Any help would be appreciated

Thanks
[Galaxy S II Android Development] Twiq:
I think you've had a bad flash, try reflashing the rom

Running 0416 Sabered SlimKat | DorimanX 10.43v108
[Galaxy S II Android Development] Flegias:
But I flashed only yesterday the last build!

Inviato dal mio GT-I9100 utilizzando Tapatalk
[Galaxy S II Android Development] LAKAME_MAN:
I personally don't think so. I actually have the same problem (well not 5 or 10 minutes, more like a couple of minutes) on my N7000 on all 4.4 ROMs AFAIK.
[Galaxy S II Android Development] Hopper8:
I quote myself... Something went wrong with my HDD and now my Linux partition won't boot. So I now have to wipe, re-install Linux and build environment, and start over :( unfortunately I don't have the time to do that in the immediate future... there goes my attempt at dev work :( so I guess we wait for fusionjack's break when he will be back here :good:
[Galaxy S II Android Development] Twiq:
It's just weird, while other users flashed and work normally, only two guys complaining about laggy screen off and on.. So the problem might be on your end, check for the downloaded rom integrity, then try flashing with full wipe, then check your problems again, if it still behaving then i suggest sending feedback with logcat..

Coz we can't see what's causing it if you only say so..

Running 0416 Sabered SlimKat | DorimanX 10.43v108
[Galaxy S II Android Development] LAKAME_MAN:
I didn't complain about laggy screen off and on. I didn't complain at all. I just said I have the same issue on my Galaxy Note on all 4.4 ROMs. The screen doesn't turn off exactly after a boot for a couple of minutes. And I remember seeing another using reporting the same issue on a different ROM in N7000's section, so it's not just us. It's a really minor issue, that's why I've never complained. I wipe data, system, cache, dalvik cache and android_secure (basically anything except internal and external storage) before flashing the ROM and Gapps. After that I just reboot system.I'm not really looking for a way to solve this issue, it doesn't really bother me, so I'm just gonna try to end this before it gets out of control.

Have you actually tried this yourself? Booting the phone, and trying the turn off the screen exactly after that?
[Galaxy S II Android Development] hawaiisteve:
I think its normal operation. I notice that the CPU is at max freq for maybe a half minute after boot. I think its still finishing the boot process during that time and the screen cannot be turned off. After a short period, the softkeys light up for a couple of seconds, the CPU drops to normal, and the screen can be turned off.
[Galaxy S II Android Development] Twiq:
Sorry, let me rephrase that..

Two people giving feedback about laggy screen off and screen on right after boot.

And to your question, i don't see that issue on my end, after media scanner notification icon is gone, tried turning off the screen, it went off right away. Tried turning it on again and it gives several seconds to turn on but less than 10s..

Running 0416 Sabered SlimKat | DorimanX 10.43v108
[Galaxy S II Android Development] LAKAME_MAN:
Yeah I didn't say anything about waiting for the media scanner to finish. I meant right after booting. You boot the phone, you see the lockscreen, and you press the power button (or use the go to sleep tile, or double tap the status bar, or use a hardware button remapped for turning off the screen). That doesn't work for me.

I actually read something about what you said. That the screen won't turn off before the media scanner finishes it's thing after boot.

Also, I didn't give feedback about a problem with turning the screen on. The problem is turning it off, and it's not laggy, it just doesn't work for a short time :D

EDIT: I just tried booting again. I was able to turn the screen off about 40 seconds after boot. Doesn't really bother me :D

I agree, that's why I don't care. I was just trying to say that's it probably isn't an isolated issue and that it won't be fixed with reflashing the ROM. I hope I haven't offended anyone.
[Galaxy S II Android Development] damnation333:
Anybody noticed Google maps lagging? Was away this weekend and had about 10 big, draining freezes.

Thanks
[Galaxy S II Android Development] iekansh:
Just a general query, any update about theme chooser? Inquisitive enough because of the build up! :D

Thanks [MENTION=1228651]fusionjack[/MENTION] and slim team for the awesome work!
[Galaxy S II Android Development] Flegias:
Hi!

Due to the very long delay to have the screen off after a boot, I decided to reflash the ROM after full wipe and format system.

It seems that the issue is gone!!!

I'm able to turn off the screen after few (10/15) seconds from the boot!

Don't know why I had that issue because I did full wipe and format system even with the first flash of the ROM

btw I have the device fully working now!

Thank you guys
[Galaxy S II Android Development] Twiq:
Thats what i meant in earlier post, since early slimics releases it is known that some rom flashes didnt completely/correctly get flashed. The developers are suggesting to flash twice or even three times if the flash progress is too quick. Symptoms of bad flashes are not limited to dumb system permission, media scanner issues, undetected system files/media, unstable systems and making some certain features not showing.

Running 0416 Sabered SlimKat | DorimanX 10.43v108
[Galaxy S II Android Development] hawaiisteve:
<br />

<br />

Thats what i meant in earlier post, since early slimics releases it is known that some rom flashes didnt completely/correctly get flashed. The developers are suggesting to flash twice or even three times if the flash progress is too quick. Symptoms of bad flashes are not limited to dumb system permission, media scanner issues, undetected system files/media, unstable systems and making some certain features not showing.<br />

<br />

Running<b> 0416 Sabered SlimKat | DorimanX 10.43v108</b>

[/QUOTE]

That's very interesting. Never read any op that recommended flashing a ROM more than once...I'll give it a try. Thanks for the info!
[Galaxy S II Android Development] wassk:
so any news guyz when fusionjack is coming back?
[Galaxy S II Android Development] Nos_20:
He posted he will be away for three weeks, he pops in now and again. He is on holiday probably another week or two yet before he is back

Sent From My Galaxy S2
[Galaxy S II Android Development] Hopper8:
Errr... Calendar?? Look at when he said he was leaving (can't remember what date it was) and add 3 weeks, I guess give or take a few days :p
[Galaxy S II Android Development] Twiq:
It's quite popular thing to do in SlimICS days, we're recommended ro flash base twice.. Back in the days we called the rom as "base" and gapps as "essential" packages..

Sorry i couldn't find the real instructions since the slimroms.com moved to slimroms.net, but here's a quote from slimrom founder krarvind and retired RC AvRS:

http://xdaforums.com/showthread.php?p=27416756

And

http://xdaforums.com/showpost.php?p=27159470&postcount=3470

Running 0416 Sabered SlimKat | DorimanX 10.43v108
[Galaxy S II Android Development] hawaiisteve:
I'm kinda questioning if flashing more than once is really helpful now, after I thought about it. Doesn't cwm format system automatically before flashing a ROM? If that's true, then the first flash is formatted and gone before the second is done. Please correct me if I'm wrong...
[Galaxy S II Android Development] Twiq:
Not the CWM tho, but you're correct.. The flash script unmounts the system, then it mounts system, format it, then dump zip content to the partitions, then it symlink and sets up permissions.. And later on set metadata in files (in later KK builds)

Not too sure about which steps that are oftenly skipped during flashing therefore causing problems, anyways if you're on stock slimroms and having weird issues while others dont, try reflashing :)

Running 0416 Sabered SlimKat | DorimanX 10.43v108
[Galaxy S II Android Development] clock51:
problem??

hello guys, it's a little bit of time after ending a call (incoming or outgoing), I find myself open some apps usually the calendar or the clock and in addition increases the brightness to maximum, it happens to others? advice? pissed gustavo the kernel and I've done wipe cache and wipe Dalvik, even reflash rom, gapps and kernel with the necessary cleaning wipe and scripts, but the problem remains.