yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] damnation333:
Yes, I reflashed the AIO gapps and then the minimal gapps on top. (might be weired, but that's how I got it running the last time.)
[Galaxy S II Original Android Development] HardCorePawn:
Odd.... seems to be working fine here... :confused:

I assume you did all the dalvik and cache clearing stuff as well...
[Galaxy S II Original Android Development] damnation333:
Yes, format system, format cache and clear dalvik.

will wipe and retry again.

edit: just retried. Just wiped everything again and flashed everything and now it is working. Is there a difference between wipe cache and format cache?!?

edit2: Awesome, the calendar and Email is working, too! :) thanks
[Galaxy S II Original Android Development] jeancca:
Google search

Hi,

I did all reflashing and wiping/formatting to get everything fine. All is well except google search, which was not installed properly and could not be updated through google play. Any hints? Or better wait for next weekly?

Thanks,

Jean
[Galaxy S II Original Android Development] SimboXXX:
Yeah, Google search is a problem. I installed from other package but not working. Haven't had time yet to look into it.
[Galaxy S II Original Android Development] SimboXXX:
I was wrong. Just wasn't installed properly.
[Galaxy S II Original Android Development] jeancca:
Ok, how do I install it?
[Galaxy S II Original Android Development] SimboXXX:
I restored it from a saved version in titanium, but the easiest way would just be install from play store.
[Galaxy S II Original Android Development] leechseed:
Beta4 changelog: http://slimroms.net/index.php/changelog/371-slimbean-4-3-build-beta-4

New devices (4.3)

n7000

i9100

hercules

skyrocket

First official weekly for our device is rolling out:D

Slim-4.3|Dori-test|i9100¬Tapa2
[Galaxy S II Original Android Development] bodzik155:
Can I have 4.2.2 and 4.3 Slimbean in dual boot configuration?
[Galaxy S II Original Android Development] thout:
i think yes, you can... with dual boot kernel
[Galaxy S II Original Android Development] HardCorePawn:
Yeah... looks like we're just going to go back to the AOSP way of doing things... which is dalvik-cache on /data... and remove the option for /cache/dalvik-cache completely as it looks like it might be breaking other devices as well (possibly related to Grouper bootloop)

We have commits in gerrit to revert it all... and I'm compiling and testing now... for anyone who wants a quick fix to FCs when using AIO Gapps:

Edit /system/build.prop add in: dalvik.vm.dexopt-data-only=1

reboot recovery

wipe cache, wipe dalvik

reboot

This really seems to be some sort of conflict between BT devices and phones... it seems some work OK, and others don't... it doesn't surprise me that a Sammy based ROM works... as the BT stack was changed by Google in JB 4.2.2 to bluedroid... previous versions (4.1.2 and earlier) used the bluez stack... This change broke a few things (like artist/track title display), as bluedroid was not as advanced...

I have NO idea why Google did this... but they did... and now we all suffer... :rolleyes:

EAP has always been problematic... Not sure why it isn't included in AOSP tho... I suspect it may have something to do with proprietary drivers/blobs for WiFi or something... is it in CM or other AOSP based ROMs?
[Galaxy S II Original Android Development] fusionjack:
[MENTION=1663702]HardCorePawn[/MENTION]: is slim gerrit already public? :)
[Galaxy S II Original Android Development] lickwidice:
Yea I see...no it isn't in any CM or AOSP Roms that I have tried. But I'm convinced I can somehow getting work using the following http://code.google.com/p/seek-for-android/wiki/EapSimAka

I think if I can just find the supplicant file I can play around with some settings and see...unless this whole module is left out. Someone said they got it working on CM 10.1

Sent from my GT-I9100
[Galaxy S II Original Android Development] HardCorePawn:
Not to my knowledge... but it is being worked on...

First tests of the revert of /cache/dalvik-cache are positive... in that, I just flashed my build + AIO... and booted up with any FCs... and all the dex's were created in /data/dalvik-cache :)

You can't just hack the supplicant... it isn't a .config file etc... that linked stuff is for patches to various parts of the source code... so you'd need to get the sources from Slim github... make those changes to supplicant and Settings app (complicated by the fact that we're on wpa_supplicant_8 now, and the patches are for wpa_supplicant_6 ie. OLD)... then compile...
[Galaxy S II Original Android Development] kanchanray:
4.3 build 1.9

After installing 1.9 - I'm getting regular (2-3 times a day) random phone freezes and shutdowns. If the phone is idle for a few hours - somehow it goes to a coma and the battery drains like crazy (even if it's on charging) - the phone becomes super-hot and finally it just dies. Have to take out the battery and restart...

Has anyone seen this? Reverted back to 1.8 now... seems OK with that.
[Galaxy S II Original Android Development] SimboXXX:
Sleep of death - are you doing any undervolting or messing with cpu?
[Galaxy S II Original Android Development] 1username4thisforum:
vibrate notification

Can someone using this ROM and viber kindly explain how to stop viber from vibrating when I receive a message.

I can't find the setting inside viber or sound settings

:(

Thanks in advance
[Galaxy S II Original Android Development] kanchanray:
Not really - I now installed Dori 8.39 kernel - that seemed to have stabilized it...
[Galaxy S II Original Android Development] Upquark:
You could set the Vibration strength @ Settings / Advanced options / Device / Haptic, but this being a global setting, it's perhaps not what you'd want.
[Galaxy S II Original Android Development] dimspace:
is there any simple trick for hiding the status bar entirely with slimbean.

Settings options for hiding it are

disabled - so always shows

non permenant - so it shows when there are non permenant notifications

and all, so it shows when there are any notifications.

I really want it zapped completely. I use aviate with dashclock and floating notifications, so i really dont want a status bar at all.
[Galaxy S II Original Android Development] 1username4thisforum:
I think the setting is listed as vibrate while CALLING in Viber.

Frustrated was i
[Galaxy S II Original Android Development] SimboXXX:
I think there's an option for expanded desktop, that will hide status bar.
[Galaxy S II Original Android Development] HardCorePawn:
^^---- THIS!
[Galaxy S II Original Android Development] MystaMagoo:
Bug

Click the phone.

Swipe to choose the 'contacts' option.

Click any picture in the '

Frequently Called

' list.

'The contact doesn't exist'

BUT

if you actually click the name/number it does dial said name/number.

This is with 1.7 though.

Is it still present with 1.9 anyone?
[Galaxy S II Original Android Development] m1trand1r:
just tried....it works fine here....on latest:)

Beam-ed through your brain via//Android 4.3.1:p//
[Galaxy S II Original Android Development] socekin:
hi,guys. where is the T9 setting ? thanks
[Galaxy S II Original Android Development] guido_glx:
Settings, language and input

Enviado desde mi GT-I9100 mediante Tapatalk
[Galaxy S II Original Android Development] socekin:
I can not find T9 in language and input
[Galaxy S II Original Android Development] badblood_antony:
hi

m from th sgh-i777 forum...i tried this stable build 1 on our device...all features working except for root...

if i stay on stock slimbean kernel the root works...but i loose the key layout of our device...

if i install ajk kernel then i loose root every time i reboot the device...

i tried the solution provided in the op of this thread...still the same issue...

any way this can be solved...cuz slimbean seem to be not developing this os for i777 anymore after 4.2.2
[Galaxy S II Original Android Development] Didgesteve:
Have you tried installing Chainfires SuperuserSU from the market?
[Galaxy S II Original Android Development] HardCorePawn:
Wait... what??!? :confused: You installed the i9100 ROM on your i777?

It doesn't surprise me that the key layout gets lost using i9100... it only has Menu, Home and Back... not the 4 soft keys of the i777...

You could try grabbing the kernel from CM-10.2 for i777 (download ROM zip, extract boot.img and use a kernel flasher zip)... and see if that works (the standard Slim kernel for galaxys2 devices is more or less the same as CM kernel anyway)...

Other than that, you'll need to wait until [MENTION=4568724]fronti90[/MENTION] finds some time to bring up the i777...
[Galaxy S II Original Android Development] damnation333:
Just flashed. Everything working good so far. Thanks for your work!
[Galaxy S II Original Android Development] kanchanray:
BBM Issue

Has anyone tried BBM on this ROM? Everything works - except the notification sound. When I get a BBM message - the notification icon thing pops up at the top - but - I get NO sound notification. Any help?

Cheers!
[Galaxy S II Original Android Development] themike10452:
I want to install this ROM on my friend's phone, is it stable enough for a daily driver? and what are the problems in Build2, any bugs at all? camera BT wifi anything? I read here someone had a problem with SOD, is it common here? On stock 4.1.2 ROM from Samsung we have a problem with SoD even with custom kernels.

Sent from a nexus⁴ Running crDroid Powered by AK xCrossed kernel
[Galaxy S II Original Android Development] HardCorePawn:
Seems to be working fine here... I just installed and created a couple of BBM accounts on my i9100 and my Nexus 4... sent message from N4 to SGS2 and I got the "ding dong" and notification icon...

Are you getting other notification sounds?? If so, try checking BBM Settings... make sure the Tone is setup correctly. If you are not getting any notification sounds, check Quiet Hours... make sure this isn't on when you want notification tones.

Also, less likely, check Profiles (if switched ON)... make sure notification sounds are enabled etc... and lastly, just double check the notification volume isn't muted...

Did you read the OPs?? The most common "known issues" are there (specifically post 3)...

fyi, SoD is generally caused by custom kernels... not a common issue AFAIK on Standard Slim Kernel...
[Galaxy S II Original Android Development] 1username4thisforum:
Just googled android sod.

100% stock completely cleaned install, I got a message of the new stable update. Started downloading that and the new gapps.

Got a screen of death(screen was black and would not turn on no matter what.

Held the power button to reboot the phone.
[Galaxy S II Original Android Development] kanchanray:
I am getting all other (SMS/mail) notifications properly - And I get the notification icon when a BBM text comes - it just does not play the sound... Now, after playing with the 'Tone' - it seems that - if i set the 'Tone' to BBM - it plays the default ding sound. But - if I choose any other sound in the Tone - it does not play that... Will work for the time being :)
[Galaxy S II Original Android Development] Didgesteve:
BBM works fine here, I just installed it, default sound works fine.

I haven't tried changing the sound.
[Galaxy S II Original Android Development] HardCorePawn:
"Sounds" like an app issue :p

Or possibly it doesn't like the format of the audio file you're trying to use... Suggest you contact BBM support
[Galaxy S II Original Android Development] Andromepat:
I flashed Build 2 yesterday in the morning. IMHO, battery drain is much worse than with 1.8 I used before. My phone does just not get through the day and it did before.

As this is very subjective and I did not scientifically verify, see my post more as a hint than a complaint. :angel:
[Galaxy S II Original Android Development] HardCorePawn:
Hence the reason why I put the notice in the OP "banning" all talk about battery life etc, with a link explaining why... :rolleyes:

Be thankful I'm on Tapatalk (due to travelling) at the moment... It is the only reason I am not reporting your post! Grrrr :mad:
[Galaxy S II Original Android Development] m1trand1r:
web view....--> report button....LOL...:p...you can report if you really want to do so:D

Beam-ed through your brain via//Android 4.3.1:p//
[Galaxy S II Original Android Development] iekansh:
I can't see my apps option in play store .. Any solution?
[Galaxy S II Original Android Development] damnation333:
The layout has changed in the play store. Your apps can be found under the options on the left top corner.
[Galaxy S II Original Android Development] m1trand1r:
swipe from left to right like in gmail:good:

Beam-ed through your brain via//Android 4.3.1:p//
[Galaxy S II Original Android Development] spud_work:
Apologies for having to ask, but I am having problems getting build 2 working after coming from the last of the 4.2.2 slim builds.

Before installing I do a full wipe, wipe the cache, dalvik cache, mount and format system. The ROM then installs and works fine using the minimum apps package. I don't restore anything other than a google sync, but on any subsequent boot it gets stuck at the white Samsung logo and won't progress any further.

Am I missing anything obvious?
[Galaxy S II Original Android Development] thiagobraga:
Some random reboots

Did a clean install, manually format system and all this stuff.

Experiencing some reboots, don't know what is causing that, but last time i was listening some music in poweramp.

Keep up the good work.

:good:
[Galaxy S II Original Android Development] Fernandz:
I have the exact same issue. full wipe and manual reformat of all partitions, the rom install and works ok, but after first reboot: bootloop. :eek: tried many times with same result.
[Galaxy S II Original Android Development] HardCorePawn:
Sorry to hear you guys are having issues with this... I honestly have no idea what may be causing this. I certainly haven't had these issues, and there seem to be plenty of users operating without problems. :confused:

If the ROM isn't making it past the Samsung logo, that is generally indicative of the kernel not booting properly or having other issues, as it isn't even showing the Slim splash/boot animation!

Things that might help:

- Try another 4.3 ROM like CM-10.2 and see if you can get that running OK.

- Install... boot into OS, then reboot into recovery... dirty flash ROM+Gapps again, then wipe /cache and dalvik and reboot... if that works, just try rebooting again to make sure :fingers-crossed:

Other than that, about all I can suggest trying, is to flash back to a stock Samsung ROM to really put the phone back to a default state and then try to put Slim back on.

As you can see... I am kinda clutching at straws trying to figure this out... :silly: :fingers-crossed:
[Galaxy S II Original Android Development] 1username4thisforum:
I'm not sure how banning battery talk can help the users or dev of this ROM.

I upgraded from the old stable version to the new 4.3.1 a while after it released.

Battery life is just over half compared to the old version. Used to average 22 hours, now it is 13 hours.

If you want to ban me and that other dude for providing feedback to other users and so the issue can be looked at, so be it. See how many people will continue to use your ROM.
[Galaxy S II Original Android Development] HardCorePawn:
Did you read my comments on why it isn't useful? The short version is: All users are different... all devices are different... all environments are different... all networks are different...

So... all different users use their different devices in different environments on different networks, differently... starting to understand the issue?

Hell... my battery life on i9100 has gone from around 12 hours to around 5 days... simply because my i9100 is now a WiFi only test device... it has no sim in, so I set it on airplane mode and turned WiFi on... This thing lasts forever! :p But that massive increase was all due to the way I was using and had configured the device.

And to be completely honest, from a ROM dev point of view... there really isn't anything we can do about it. Most "high battery drain" issues are caused by rogue service wakelocks (things like leaving the WiFi scanning on even when wifi is off type stuff) or user apps causing wakelocks...

Pretty much NOTHING I can do as a ROM dev, will make any difference to your battery life... I could probable tweak the kernel and try UVing by default, but then the users with less table CPUs will complain of lags, freezes and SoDs... I could set default screen settings to dimmer values... and then everyone would complain their screen wasn't bright enough in sunlight etc etc.

Our focus, is to provide a good solid ROM, that is stable and can be used as a Daily Driver without too many issues...

The onus is on the user to experiment with various things to get the best battery life for them... that isn't something we have control over... turn your WiFi off, turn your BT off, use 2G networks, mess with auto brightness settings, experiment with other kernels and UVing etc etc... check your wakelocks... find what is killing your battery and fix it...

As I mentioned in the rant about battery, In the (highly unlikely) event that part of the system is actually responsible... feel free to provide some solid evidence/logs/proof etc that it IS the system and we'll look into it...
[Galaxy S II Original Android Development] m1trand1r:
I like rants like this^^^ :good:

Beam-ed through your brain via//Android 4.3.1:p//
[Galaxy S II Original Android Development] 1username4thisforum:
This is my daily driver currently, I don't have time to mess around like that with the phone.

I completely understand what your saying.

But I've uses many ROMs over the years, and upgraded through the new releases of those ROMs. Including this ROM. It is not common that an updates version of a ROM makes your battery life just better than half. And when that happens, tons of people post about it in the threads, people using it as a daily driver rollback and wait for the next update.

I really appreciate the work of anyone involved with this ROM, it really is great. :thumbup::beer::)

But, I use my phone the exact same way with this version, compared to the last stable version. The battery is not lasting as long.

Im sorry the only this I can help with is saying I use the phone the same, and am rolling back for better battery life.

It might just be something in 4.3.1,

Or my device in particular.

My post comes from a place of love <3

Sorry its not what you want to hear
[Galaxy S II Original Android Development] SimboXXX:
When can we haz kat-kit?
[Galaxy S II Original Android Development] Mr.NeoTrinity:
Hello slimrom user :)

I use the actual stable 2 4.3 Android.

I recognized when i turn off the device, and on ( no reboot ) the language is changing back to english.

If I choose the reboot function from the power button,everything is ok .

Can anyone confirm this behavior?!

sincerealy :)
[Galaxy S II Original Android Development] jimger:
Guys cause I moved from rootbox 4.2 about 2 days ago does this rom have swype ribbon? or is it just aokp stuff? If it doesn't is it a feature that is going to be added?

Btw to the developers.... Very cool he real dark slim combinated with dark google apps and the ability to not install voice and other things I don't use... Is there any chance to upload somewhere apks of google + or sth in dark style also?
[Galaxy S II Original Android Development] kroz:
no swype ribbon

google + are also supported by trds but it was updated after the release of build2 slim gapps so updated google + will be available on next release or slim gapps

Sent from my Hue themed GT-I9100 using Hue themed Tapatalk 4
[Galaxy S II Original Android Development] jimger:
ok thanks.... But I was talking about also for example maps or sth.... I don't want the full gapps I found the slimmed version more than extremely useful but I would like to have maps and + in apks (or zip) ANyway many many thanks rom seems pretty nice... Let's hope it will be stable too
[Galaxy S II Original Android Development] leechseed:
" Can i haz SlimKat? "

The proper way to beg. (except of missing cat) :D

Omni+Slim-4.3.1Dorimanx|i9100¬Tapa2
[Galaxy S II Original Android Development] rebecker:
Issues With Widgets

I'm currently running build 2 official. With the last 3 builds (2 weeklies and this version) I've started having real issues with widgets. In the past I've run 8 different widgets, some repeated on different screens, using 7 different screens. I've reduced the incidences of widgets (although still using all 8) and removed 3 of the 7 screens. I'm still getting lots of "failure to load" errors and widgets not updating. Before I start re-installing the weeklies in reverse order to try to find a build that doesn't have these issues, can any of you make suggestions of things I might look at (short of removing the widgets, which I use a lot ;) )? I switched from the CM official builds because of this same issue. Initially, I didn't see this issue in Slim Bean.

ALL suggestions will be greatly appreciated!

-Bob-
[Galaxy S II Original Android Development] 1username4thisforum:
I honestly think you are using too many homescreens and too many widgets.

I used to use 3 home screens.

Media, with 6-8 shortcuts, main with weather widget, and settings with power control/audio manager, and some shortcuts.

Dropping down to 1 homescreen with 1 wiget on it improved the response of the phone enough to notice.

I know its a huge change, but I'm just using this for the time being until I figure out what handset to buy(prolly n5 when I can walk into a store and get it locally).
[Galaxy S II Original Android Development] rebecker:
I was afraid you'd say that. :) The interesting thing is that this wasn't an issue some time back in the weeklies. So...I'm going to try reverting back starting with 1.6 and see what happens. I DO have one additional question: Should I install the build 1 gapps, or will the current build 2 gapps work with the earlier nightlies?

Thanks for your reply.

-Bob-
[Galaxy S II Original Android Development] HardCorePawn:
If it is happening at boot it is most probably a timing issue with the mounting/scanning of SDCards... If it is just happening while returning to launcher etc... then it is quite possibly just a lack of memory issue... so tasks/services etc are being killed off by the memory management to ensure the system as a whole remains stable.

Are you running a custom kernel at all? I vaguely remember seeing something about Dori tweaking memory management stuff...

Personally, I have DashClock widget... and that is about it... so I can't be of more help with tips/tricks to try getting this to work... :p
[Galaxy S II Original Android Development] 4igi4:
FP

HI

flash player work on the slim bean "[4.3][28/10]Slim Bean - I9100 Build 2 "?

thanks !
[Galaxy S II Original Android Development] spud_work:
Thanks for your help HCP, I was running a 3rd party kernel on 4.2.2 (Dorimanx) as USB transfers don't work for me with the stock kernel (see my posts about that in the 4.2.2. thread some months back) so your suggestion that this might be a kernel issue was a big help :)

I did a dirty flash of 4.2.2 build 8 over my existing installation to put the original kernel back in place and then flashed 4.3 following the installation instructions and this time everything has worked exactly as it should.

It might, therefore, be worth putting a note on the opening page that there could be an issue for people flashing this 4.3 rom if they are coming from a non-slim kernel.

All I can assume from this is that something in the recovery that comes with Dorimanx kernel that I was using that was failing to wipe or mount/format the system correctly in order to prepare it for 4.3 as I must have tried it 10 or more times and got a boot loop each time, 1st go using the stock slim kernel and everything was good :)

Thanks again HCP and I look forward to seeing what 4.3 has to offer
[Galaxy S II Original Android Development] LikkiHalili:
why when i call somebody the screnn get blank and he cant hear me and i cant her them pls help