yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] SWTR:
I have uploaded it for you.

NewCameraApp-2-.apk

Just delet the Gallery2.apk in system/app and install the new camera as normal app.

Gesendet von meinem Galaxy S2 mit CM10.1
[Galaxy S II Original Android Development] lickwidice:
Hi HCP and the SlimRom team

I've been using SB for a long time and I really enjoy this ROM. I'm currently on build 4.2.2 build 8. I just wanted to know what has been the mose stable JB Build so far? 4.2.2 Build 8 or 4.1.2 Final?

Logic tells me that 4.2.2 would be more stable because its newer and has more bug fixes.

Also when you flash this ROM. What modem does it come with? Or does it just use the modem that we had before we flashed it.

Sent from my GT-I9100
[Galaxy S II Original Android Development] HardCorePawn:
"Most stable?" is a loaded question... and probably not something that can be definitively answered...

4.2.2 Build 8 is certainly newer... but newer doesn't necessarily guarantee more stable... eg. 4.3 is newer than 4.2.2, but not necessarily more stable :p

If you are already on 4.2.2 build 8, why would you want to flash back to 4.1.2? :confused:

This ROM does not include a modem on i9100 (or any device as far as I'm aware)... modem will only be modified if you're flashing a full (stock) ROM using ODIN/Heimdall... or if you flash a modem via recovery.
[Galaxy S II Original Android Development] mirhl:
I have a problem with track id

The blue circle is actually deformed and looks ugly

Logcat in the second image
[Galaxy S II Original Android Development] HardCorePawn:
App issue? Try resetting to "normal" hdpi DPI (ie. 240) and see if it is still messed up...

In any case, there won't be anything we can do about it... We dont fix ugly apps... :p

You'll need to contact app developer, tell them your device, ROM and DPI (standard slim dpi on i9100 is 182) and see if they can fix it...

ps. Nice effort on the logcat, but for future reference, save the logcat as a text file and upload that... More useful than a screenshot of a very tiny segment of the logcat ;)

Sent from my SlimBean pwned GT-i9100
[Galaxy S II Original Android Development] SPBoss:
guys I have tried every method on xda and in slim beam FAQ to fix Google play store as I can't purchase anything. I'm stuck for the first time! :(:(

Need help please
[Galaxy S II Original Android Development] lickwidice:
I'm just quoting for now so that you have some context. I am using 4.2.2 Build 8. The reason why I considered going to 4.1.2 is that if it is a "more stable" release then I won't mind downgrading as I don't need any of the new features in 4.2.2.

I've had a couple of issues on 4.2.2 that I didn't have in 4.1.2 but It could be me and I didn't get a logcat yet. Basically here is what i've experienced in 4.2.2:

1) Gallery FC's when saving a picture that you editing (manage to fix this by force stopping Gallery and clearing the cache)

2) I'm having an issue with the "stock" slim keyboard and swiftkey. They both seem to lag very badly sometimes. I thought it was only in WhatsApp but this also happens when using the browser. Restarting the phone didn't do anything. some days it works fine though.

3) GPS was taking a long time to lock, got this fixed by replacing some file (found it in this thread somewhere)

HCP can you perhaps answer the following questions for us, I know it doesn't matter but it will give me and maybe others a little peace of mind.

1) What keyboard do you use? the one that comes with SlimRom?

2) Is the keyboard that comes with SlimRom also known as AOSP keyboard?

3) What was the reason for the QSP (Quick settings panel). The power widget worked fine for me so I just disable the QSP. Do you use QSP or the power widget? Is there any performance gain in using 1 over the other (since I don't mind using either.)

4) I find that there is some degradation of picture quality on the camera on non samsung roms. I can think of the following reasons:

4.1) I'm insane / imagining

4.2) Camera lense is probably damaged or scratched since I flashed this rom

4.3) There is really a difference in quality.

5) Not a question... Just wanted to say thank you for all the time and effort that you've put into this ROM, I refuse to use any other ROM because I love the look and feel as well as the minimalism of this ROM.
[Galaxy S II Original Android Development] Shivver:
Everything is fine, except that I don't have any notifications from any app like whatsapp or messenger. Any solution? Thanks in advance.
[Galaxy S II Original Android Development] mirhl:
You were right

240dpi fixed it :thumbup:
[Galaxy S II Original Android Development] HardCorePawn:
I assume you are using Build 8. What Gapps did you install? What is the exact error you are getting from Play Store?

1. Default

2. Yes

3. I have no idea, someone, somewhere thought it would be awesome... it DOES actually provide MORE functionality than PowerWidget... and I believe it is more easily extensible... heh... you should see the fuss created now that CM have removed the PowerWidget in favour of their "QuickRibbon"...

4. Drivers/Hardware Sources (or more correctly, lack thereof... #blamesamsung etc)

App issue then... they're obviously rendering using some fixed/absolute values... rather than using relative ones that would work with all DPIs...
[Galaxy S II Original Android Development] ssuukk:
Hello,

I have a problem using Equalizer programmatically:

09-12 08:12:30.620: E/AudioEffect(7657): set(): AudioFlinger could not create effect, status: -22

09-12 08:12:30.620: E/AudioEffects-JNI(7657): AudioEffect initCheck failed -4

09-12 08:12:30.620: E/AudioEffect-JAVA(7657): Error code -4 when initializing AudioEffect.

09-12 08:12:30.620: D/XenoAmp(7657): java.lang.IllegalArgumentException: Effect type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b not supported.

09-12 08:12:30.620: D/XenoAmp(7657):	at android.media.audiofx.AudioEffect.<init>(AudioEffect.java:381)

09-12 08:12:30.620: D/XenoAmp(7657):	at android.media.audiofx.Equalizer.<init>(Equalizer.java:146)

09-12 08:12:30.620: D/XenoAmp(7657):	at pl.qus.xenoamp.helper.XenoApiTesters.canUseEqualizerTest(XenoApiTesters.java:245)

Did I miss something while installing the rom? Or maybe I uninstalled too much?
[Galaxy S II Original Android Development] m1trand1r:
do you have MusicFX.apk in system up n' running ? And did you set in settings/sound/music effects to Xeno amp if that's a separate app with EQ?

Sent from /SlimBean//Android 4.3:p//
[Galaxy S II Original Android Development] ssuukk:
Nope. Nope.

Do you mean MusicFX that is available in Play?
[Galaxy S II Original Android Development] m1trand1r:
nope...I mean MUSICFX.apk which comes packed in rom...on 4.2.2 there must be this app in system/app for music effects to work properly.....otherwise re-flash rom....dirty flash rom without deleting anything from it and then check in settings/sound/music effects....

p.s. don't delete something out of rom if you don't know what it is....system might not work properly <--- this is written in SlimSizer if you look closer:D:p

Sent from /SlimBean//Android 4.3:p//
[Galaxy S II Original Android Development] ssuukk:
Aaawwwright... It sits there. I've changed sound settings to MusicFX, but where exactly do I add XenoAmp? EDIT - choosing MusicFX (instead of DSPManager) didn't change anything.
[Galaxy S II Original Android Development] spud_work:
Is there any way to tun off the notifications of new updates to the rom? I've got 'automatic update check interval' in slimota settings to disable - but am still getting notifications of new builds (e.g. 4.3 build 1)?
[Galaxy S II Original Android Development] fusionjack:
i'm also have this problem in my galaxy note. i think slimbean team or [MENTION=1663702]HardCorePawn[/MENTION] should take a look. :)
[Galaxy S II Original Android Development] beN..:
Delete the SlimOTA and SlimCenter apk's with some root program and reboot.
[Galaxy S II Original Android Development] m1trand1r:
Or freeze them....or remove them with SlimSizer:D

Sent from /SlimBean//Android 4.3:p//
[Galaxy S II Original Android Development] dredremon:
i have a problem my sensor doesnt work on any games like temple run
[Galaxy S II Original Android Development] HardCorePawn:
Go into Settings -> Advanced Options -> Device -> Sensor...

and do the calibrate thing... don't forget the lay on a flat surface thing...

If that doesn't help, try getting "Sensor Kinetics" from play store and see if that helps reset things... or "GPS Status & Toolbox"... that has a feature to help recalibrate things (Menu - Tools)
[Galaxy S II Original Android Development] Morphy99:
I have a weird problem on this ROM that the calendar widget doesn't get updated. It stays on a previous date till I reboot. Have tried clearing calendar storage and deleting and re-adding it. I'm using nova launcher. Any ideas appreciated :)
[Galaxy S II Original Android Development] rockrl:
Stable not kinda or only stable if everything untouched :/

Hay! i have a problem after using sb rom for a 2 weeks (build8 4.2.2) my phone froze in adobe reader and after i tried to restart it it was stuck on sb logo for ~20min and then i restart again and it boot to lockscreen but when i treid to move the circle to unlock it took like 5 sec to update 1 frame and then it froze no response again and after that i only got stuck on sb logo i tried wiping caches and reinstaling rom (no wipe) and switchiong kernels and same problem if i do full wipe and reset and instal it works again but i spent like 40h costumizing and tweaking rom and dont want to do it again i did backuip be4 flashing and things so if i resotre it am stuck at sb logo (bootscreen) again and this is so far only rom that has features i need but if things like that are gonna happen again i would go back to cm9 (wich lacks few things and has some more glitches but doesnt have souch a fatal glitch) i saw up there someone had same problem and also it happend once my phone was turned on and i could call other and it was just beep beep beep and the phone i called didnt ring and same for them when someone called me was same my phone didnt respond and after restart was working fine and also the photosphere works just fine with ggl camera from 4.3 and everything but only thing is lack of some settings and when recording video preview is broken and is there anyway to add some code in camera app or something to lock video to 30(or whatever framrate it has) just like in cm9 instead of dropping to ~15's in darkspacce + would love to have app or setting for gpu in performance settings (just liek cf3d was for ics and older roms) also the force 4x msaa unticks itself by itself can that be fixed also does this rom have problems with dorimanx kernel is maybe that the cause of everything.?

cheers!
[Galaxy S II Original Android Development] crocodilechris:
TL;DR
[Galaxy S II Original Android Development] malej robin:
hi, can anybody confirm strange bug on all slimbeans (4.2.2): after few days of running SlimBean (currently v8, default kernel, clean install - wipe data, format system, etc) all the sensors stop working, that means screen don't rotate, screen don't go off when calling, ... After restart, all sensors are working great, till next collapse after few days or hours. I don't want to go to another rom, this is only issue i've got with SlimBean, but it's really annoying..
[Galaxy S II Original Android Development] Vink67:
I have same problem with calendar widget, the date is not the right one.

Like you don't find a solution.

Maybe someone ? Thx :)
[Galaxy S II Original Android Development] tazsob:
For those not wanting notifications for new build 4.3 use TB to covert slim centre to a user app and greenify....you can still use the app and notifications won't show up...
[Galaxy S II Original Android Development] HardCorePawn:
Best option is to go into Settings -> Apps... find SlimCentre... and uncheck "show notifications" ;)
[Galaxy S II Original Android Development] tazsob:
Thanks HCP, that did the trick...knew there had to be a easier way...
[Galaxy S II Original Android Development] malej robin:
[MENTION=446203]hcp[/MENTION]: could you please answer my question with sensor problem? thx
[Galaxy S II Original Android Development] HardCorePawn:
Not many reports... and to be honest, I'm using the Mako more than i9100... and I'm on 4.3...

Try installing "Sensor Kinetics" from the play store... see if that "restarts" the sensors when it happens next time
[Galaxy S II Original Android Development] malej robin:
[MENTION=1663702]HardCorePawn[/MENTION]: thx for reply. well, there were about 5 people with same issue at Czech forum, so i'm asking for bigger group, than just me. Will try android 4.3 build and Sensor Kinetic, hope, it will help.
[Galaxy S II Original Android Development] Maniac9331:
Some gapps for 4.2.2 i cant find any.... Pls, thanks
[Galaxy S II Original Android Development] HardCorePawn:
Try Old Releases... http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/440-oldreleases/downloads
[Galaxy S II Original Android Development] infatality:
Just had a radio disconnected issues.. Don't know if it's is ROM or kernel issue.. Had posted at the relevant thread.. Here's the log..

https://copy.com/bwznL
[Galaxy S II Original Android Development] m1trand1r:
Was it RIL Chrash ?...i'll look at log...

Sent from /SlimBean//Android 4.3:p//
[Galaxy S II Original Android Development] nirav173:
I cant see zimage in the zip file of build 8. I'm on chameleon 3.0.2. Is it a safe flash?

___________________________________

Don't feel shy to hit thanks :)
[Galaxy S II Original Android Development] m1trand1r:
it's boot.img...

else re-download and flash...maybe it's a bad d/l:eek:...and you'll get error when flashing without boot.img;p

Sent from /SlimBean//Android 4.3:p//
[Galaxy S II Original Android Development] nirav173:
Is it safe to flash modem from stock sammy rom?

___________________________________

Don't feel shy to hit thanks :)
[Galaxy S II Original Android Development] eskriminal:
yes, no problems, just don't flash anything about ril
[Galaxy S II Original Android Development] HardCorePawn:
Flashing Slim doesn't touch the modem at all... so whatever was on the phone before you flashed Slim, will be on the phone after you flash Slim...

As mentioned... you can use whatever modem you like... just DO NOT flash anything that includes RIL libs... if you look in the zip file and see something other than just flash script/exe and modem.bin, I would recommend not to flash it... if you see anything like libril.so or libsecril.so etc...

That WILL break stuff!
[Galaxy S II Original Android Development] Morphy99:
Guys any idea why my calendar widget doesn't update?

Also getting freezing when taking video in snap chat which then FCs it. Then camera becomes unavailable.

Can anyone test this in 4.3 as reluctant to flash when this works so well...
[Galaxy S II Original Android Development] qqqqqq0:
where is 4.2.2 gapps? i can't find.
[Galaxy S II Original Android Development] fusionjack:
http://slimroms.net/index.php/downl...load/916-addons/5416-slim-gapps-4-2-2-build-8
[Galaxy S II Original Android Development] HardCorePawn:
www.slimroms.net

Downloads -> Old Releases
[Galaxy S II Original Android Development] hispanico957:
I use dual boot... :)) with kernel Dorimx 8.41

1° Rom Slim Bean

2° NeatRom for dualboot (http://xdaforums.com/showthread.php?t=2399193)

So...at this moment all is good... but there is a problem of root and supersu on Slim Bean, because i use Dorimax 8.41 like a kernel.

So if i want use 1° and 2° Dorimax 8.41 is ok, until on 1° rom i must use Titanium Backup or others apps that want smarphoen rooted.

I must come back to recovery, reflash rom Slim Bean and i return to rooted. I cannot reflash only the kernel of Slim Beam because i don''t know where download it, but i try to use kernel of SaberMod Slim Bean (Slim-4.3-SaberMod-Kernel-1012.zip), but Dorimax cannot permitted flash (..firmware bad).

I try this suggestions but the problem remain.

Solutions ?

Thank

Hispa

P.S.

I don't think that this can help me.. http://xdaforums.com/showpost.php?p=45358720&postcount=2264
[Galaxy S II Original Android Development] SPBoss:
Guys I have looked all over xda using search option. I cannot find the forum for slimbean weekly builds for the gti9100! Sorry for OT but if anyone could reply with the link that would be great! Listview animation is epic BTW!
[Galaxy S II Original Android Development] Twiq:
the slimbean 4.3 build is over here
[Galaxy S II Original Android Development] m1trand1r:
um....buddy....which is your primary-1st rom? and which one is your 2nd rom?

My suggestion is use Slim as primary rom and Neat as 2nd rom....but if for some reason you use Slim as 2nd rom....than you NEED to flash that zip you linked too to your 2nd rom slot from cwm menu and you should be good to go with no root issues in future;)

Beam-ed through your brain via//Android 4.3.1:p//
[Galaxy S II Original Android Development] mefistofelis:
i accidentaly uninstalled root through stweaks . How can i get it back? My rom is slimbean version 8
[Galaxy S II Original Android Development] Viper The Ripper:
You can choose one of this options:

1. Downlodd from play store

2. Reflash the rom

3. Extract it form rom .zip and copy it in /system/app or wherever it was and set the correct permissions rw-r--r--

It should work ;)
[Galaxy S II Original Android Development] spud_work:
Wrong thread, sorry!
[Galaxy S II Original Android Development] HardCorePawn:
Easiest solution is to just:

- reboot recovery

- reflash the ROM zip

- Wipe cache/dalvik

- reboot

This should give you root back... although it will wipe any custom kernel that you've installed (which I suspect you have, because you are using stweaks :p)... but that is easy enough to flash back
[Galaxy S II Original Android Development] Prashanthme:
One request from me.. Thr r ppl who r using 4.2.2 though 4.3 has come. So we r not asking fr ROM update. Atleast can we get a GAPPS update of 4.2.2 as play store, music and hangouts are constantly updated/... We love TRDS... Just a suggestion..
[Galaxy S II Original Android Development] WhiT3Kr0w:
Many thanks for all hard work. And these Slim Bean Roms are the best. But yes, that notification to get 4.3 is starting to be really annoying.
[Galaxy S II Original Android Development] HardCorePawn:
A workaround was already posted a while back...

System Settings -> Apps -> All -> SlimCenter... and make sure "Show notifications" is UNCHECKED

:victory:
[Galaxy S II Original Android Development] heywheelie:
Am I correct in saying that build 8 is now stable and bug free? I love slimbean roms.

cheers
[Galaxy S II Original Android Development] Twiq:
[MENTION=446203]hcp[/MENTION] since you're here i want to ask a question ( slim build 8 ).

When we press the toggle for "Network Mode" was it supposed to automatically change when the "Mobile Data" is turned on? or do we have to turn off the mobile data first then toggling it?

can't remember which build that allows us to toggle network mode without turning off the mobile data toggle first.

Thanks..
[Galaxy S II Original Android Development] WhiT3Kr0w:
Thanks, but I've tried that and it keeps popping up the notification.
[Galaxy S II Original Android Development] Twiq:
freeze the app or uninstall it :)
[Galaxy S II Original Android Development] paludi06:
You have to disable the notification of the app 'SlimCenter' and not the notification in the SlimCenter. That's what he meant.
[Galaxy S II Original Android Development] WhiT3Kr0w:
Man... you rock. Such an easy workaround. Didn't get it the first time. Thanks :)
[Galaxy S II Original Android Development] HardCorePawn:
I think this is a "feature" ;)

It is supposed to change regardless of whether or not mobile data is on... unfortunately, due to the ongoing issues with lack of drivers and move to OpenRIL etc... some of the network related stuff can be a bit problematic... I have just checked, and it is still doing it on the latest build of 4.3 for i9100...

It seems that having mobile data on, is blocking the RIL from modifying the preferred networks mode...

Quite a handy error message :rolleyes:

Currently, the only known workaround is to disable mobile data first... and then change modes, and re-enable data...

I also found this comment in an old version of the SamsungExynos4RIL.java file...

And code which sets up a disconnect/reconnect scenario, which would indicate that data needs to be disconnected, then the networkType changed, then data reconnected for things to be working correctly anyway... I suspect that maybe in the move to OpenRIL, this requirement for Exynos4 might have been overlooked? :confused:

You might also like to check a recent CM-10.2 ROM... and see if it has the same problem... if it does, you might like to make a note of it in their thread, and maybe one of their i9100 devs might look into it... unfortunately, the whole RIL stuff isn't really my strong suit... :(

If CM-10.2 doesn't have this issue... let me know, and I'll troll through their telephony code for something else I may have missed.
[Galaxy S II Original Android Development] Twiq:
[MENTION=1663702]HardCorePawn[/MENTION]

i couldn't find a relevant commits from cm10.2, however the problem also posted on https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/CYAN-2098 and still unresolved.

but the closest and relevant commits are from the i9300 10.1 development over here https://bitbucket.org/cyanogenmod/a...a7233f4bcd822ca00ed867c2348de01e75?at=cm-10.1 by codeworx

and it also change 2 more files.

hope it could be any use for later slim builds.
[Galaxy S II Original Android Development] Visual Focus:
Hey guys,I did a dirty flash on stable version 4.2.1 because there was a mess made with the notification sounds.After that the signal and WiFi icons turned into white colour instead of being blue.Any ideas?Tried to fix permissions,clean dalvin cache etc,even dirty reflash the ROM on top but they remain like that
[Galaxy S II Original Android Development] Twiq:
did you flash gapps? or have you add a google account on your device? coz signal indicator only turn to blue if you're successfully logged into google services.

regarding notification sound, what do you mean by "mess"? did it cause a crash? cause app to fc? further info needed to know whats going on on your device.

logcats will help also
[Galaxy S II Original Android Development] Visual Focus:
Thanks for your help,

I reflashed gapps and the icons turned into blue again. Apparently it was caused from Google play services not running properly but now the service is running in the background all the time.Isn't that a battery drainer?

I think the problem occurred when I tried to change the autorun settings through Gemini app manager.

Regarding the mess with the notification sounds I cleared media storage cache and all the sounds disappeared
[Galaxy S II Original Android Development] eskriminal:
you probably disabled the gcm receivers, it saves battery by stopping that sync behaviour
[Galaxy S II Original Android Development] Twiq:
Google services surely use some resources but personally i dont think that it'll "drain" battery that much.

That also depends on how you define battery drain,

well logically all running apps will need some juice. but if it drains noticable amount of battery in short period (on screen off) then something must be causing wakelocks, where you could track them down using betterbatterystats or similar apps. but if its behaving normally then i think you should stop looking at the battery percentage :)

or if you dont use google services at all then you could uninstall anything flashed from gapps. Or alternatively you could use NOGAPPS project, you could find it somewhere on xda.

disabling some google services/receivers could cause much worse wakelocks than it normally would, so i wouldn't suggest tampering them unless you know what you're doing. best way to "calm" google services atm (imho) is by hibernating them with greenify.

regarding media disappearance, try force running media scanner service from developer tools then reboot, if they're still missing then i think it must be permission problem (except for medias located in internal/external sdcard)