yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] tazsob:
Hi mate, tried flashing 250ms package through CWM but get "status 7" error... Downloaded and flashed twice and both times same issue...
[Galaxy S II Original Android Development] Shinfei:
Sorry, just try on mine and my wife's one, no error :/

Surely a bad download ?
[Galaxy S II Original Android Development] zarl0ck:
Can I use a custom kernel with this version, like DorimanX/Siyah ?
[Galaxy S II Original Android Development] Shinfei:
Yes why not ?
[Galaxy S II Original Android Development] zarl0ck:
Thanks for the reply. How about Ac!d audio? Has anyone every tried flashing Ac!d audio on SlimBean 3.1 + Walkman addon?
[Galaxy S II Original Android Development] F670ES:
Hi. Can I do wipes safely in recovery on the kernel included in the rom ? Where can I get inverted gapps ?

Btw. This rom is the fastest from the custom roms in my opinion. Great work !
[Galaxy S II Original Android Development] distilicious:
I don't think anyone would ever intentionally include kernels capable of bricking your phone. Leaks on the other hand......
[Galaxy S II Original Android Development] tazsob:
For inverted gapps so a search for justun bean gapps.... they work with this rom
[Galaxy S II Original Android Development] tazsob:
I'm not an 100% but it looks like some file is missing from your directory (E) have u tried pairing your Bluetooth with another device and see if the problems still there? Here's a backup of my Bluetooth from Titanium backup, just add them to SD and restore using TB... Remember to back yours up first before you do anything.......

http://db.tt/bM5MBjYU
[Galaxy S II Original Android Development] HardCorePawn:
First of, nice work on the logcat! :thumbup: :good:

Would appear that there is an issue here...

02:35:04.640 E/AndroidRuntime(9905): FATAL EXCEPTION: HeadsetBase Event Thread
12-09 02:35:04.640 E/AndroidRuntime(9905): java.lang.NullPointerException
12-09 02:35:04.640 E/AndroidRuntime(9905): at android.telephony.PhoneNumberUtils.numberToCalledPartyBCDHelper(PhoneNumberUtils.java:1064)
12-09 02:35:04.640 E/AndroidRuntime(9905): at android.telephony.PhoneNumberUtils.networkPortionToCalledPartyBCD(PhoneNumberUtils.java:1033)
12-09 02:35:04.640 E/AndroidRuntime(9905): at com.android.phone.BluetoothSMSAccess.CreatePDUResponse(BluetoothSMSAccess.java:598)
12-09 02:35:04.640 E/AndroidRuntime(9905): at com.android.phone.BluetoothSMSAccess.access$1300(BluetoothSMSAccess.java:41)
12-09 02:35:04.640 E/AndroidRuntime(9905): at com.android.phone.BluetoothSMSAccess$7.handleSetCommand(BluetoothSMSAccess.java:354)
12-09 02:35:04.640 E/AndroidRuntime(9905): at android.bluetooth.AtParser.process(AtParser.java:350)
12-09 02:35:04.640 E/AndroidRuntime(9905): at android.bluetooth.HeadsetBase.handleInput(HeadsetBase.java:133)
12-09 02:35:04.640 E/AndroidRuntime(9905): at android.bluetooth.HeadsetBase$1.run(HeadsetBase.java:172)

Possibly seems to be related to SMS and reading contacts? As there is a lot of vcard activity prior to the exception...

Unfortunately, it is a bit hard to check the code as my Dev environment and I are not on speaking terms at the moment, due to 1. Me not actually being at home this weekend :p and 2. It being a little broken :(

Had you by any chance created a new contact around the time this stopped working? It looks like it is failing to find a number... As the code is:

int numberLenReal = number.length();

So I suspect the number being passed to the method is null...

Or possibly it is a corrupted SMS message? If possible, you can test this by backing up your SMS messages using your preferred method (if you don't have one, I recommend SMS Backup+, backs up and restores to/from your gmail account :)) then delete all your SMS messages... then see if it still crashes when connected to BT...

If it does, then restore your messages, then try deleting the threads one by one until you figure out which one is broken... then see if you can identify either the specific message or contact that is causing the issue...
[Galaxy S II Original Android Development] HardCorePawn:
No logcat = no chance of getting any help... are you running a custom kernel and/or any sort of usb mounting apps like multi-mount/dual mount etc?

inverted gapps on SlimRoms website...
[Galaxy S II Original Android Development] lickwidice:
Which features in slim Bean are taken from aokp?

Can I use setCPU with slim Bean? Does it have any internal cpu tweaks that might conflict with setCPU?
[Galaxy S II Original Android Development] imranrajah:
I have already selected usb connection mode in settings. But wen i connect my fone to my pc and select TURN ON USB STORAGE, my fone crashes and restarts

Please help
[Galaxy S II Original Android Development] F670ES:
Yes You can but for OC You must flash different kernell. As for features it has pretty much everything needed. I was testing Ressurection rom and I like Slim Bean better.

Btw. There are some hangs on Dorinmax v7.29 and only hard reset helps. Most hangs are when I try to wake up and unlock the phone. Have anyone tried this kernel and expierienced the same ?
[Galaxy S II Original Android Development] lickwidice:
I'm using the cm kernel that comes with it and everything is fine not one hang
[Galaxy S II Original Android Development] imranrajah:
Hi,

im not running any custom kernal nor any usb mounting apps.

im a noob with ADB and stuff, so i somehow managed to run the app CATLOG and retrieved the logcat.txt

hope i can get help now :confused:
[Galaxy S II Original Android Development] F670ES:
Yes I must say the original kernel may be the best. It runs smoothly but I didn't test battery life on it yet. One thing bothers me : I have wake up lags and can't get rid of them. I tested Siyah, Dorinmax and the original kernel. Is there any way to fix this ?
[Galaxy S II Original Android Development] imranrajah:
My bad, didnt notice the file didnt get attached.

i have attached it now.:silly:
[Galaxy S II Original Android Development] janeka_pt:
delete this post.. Wrong Section
[Galaxy S II Original Android Development] :
Cm 10 4.2.1 builds are out, lets hope for a fast slimbean 4.2.1 :)
[Galaxy S II Original Android Development] eths83600:
In the settings we can only choose off 214 240 and an other once for changing the LCD density.

But I want 180, so I've downloaded an app that allows to change it to 180, but after a reboot it goes back to 213.

Any solution?
[Galaxy S II Original Android Development] imranrajah:
Hi,

I guess the LOGCAT file i posted here previously is not clear cuz i generated it using Catlog app. I have gone through

FuzzyMeep Two'

s link on how to get LOGCAT using ADB and used his tool to get the LOGCAT.txt file and i have attached the same here.

I have attached another logcat file with only errors.

The problem i'm facing is my phone crashes and restarts when i connect it to my pc and TURN ON USB STORAGE.

i hope i'll get help now....

Thanks in advance.
[Galaxy S II Original Android Development] DerBobo:
You can type in own dpi Values in last menue (5th or 6th) entry on the bottom.

sentbfrom my i9100 with latest SlimBean and latest Siyah Kernel
[Galaxy S II Original Android Development] aktorsyl:
(Posted this in the wrong location before, reposting here)

Hi guys,

I have a Galaxy S2 I9100. It was on stock ROM (ICS 4.0.3) until yesterday, then I flashed Slim Bean 3.1. So far everything works mostly as expected on Slim Bean, but there is one major annoyance:

After every reboot (or when I just toggle between Silent and Normal), the volume is maxed on everything (system, ringer, notifications, etc). The volume sliders are all still where they're supposed to be, but the actual volume is loud as hell. The only way to fix it is to drag each volume slider down one notch and then back up one notch - then the volumes are at the proper levels again. I don't mind doing this after every reboot, but after switching the phone from Silent back to Normal? I do that ALOT :-/

Any ideas? I've googled extensively to find the issue, but no luck.

EDIT: I've also since tried to install the latest Siyah kernel to see if it will fix the issue. It doesn't however. I've also noticed that when the screen fades (before it sleeps), it fades in "steps" or "stutters" if you will, instead of a smooth fade to black.
[Galaxy S II Original Android Development] HardCorePawn:
Did you follow ALL the steps in "System Settings -> Interface -> General UI -> LCD Density" ??

Initially, step 1 gets you to set to a default (I suggest 240)... then you goto step 2. reboot, then 3. clear play store data, then 4. open play store...

finally step 5 should allow you to select from:

160, 182, 200, 220, 240, 241, 268, 280, 300, 320, 340 or custom?? :confused:

TBH, your logcat looks very bad... so many errors (lots of permission errors etc)... I would suggest you do a nandroid backup, then do a full wipe and re-install. It looks like there are some serious errors in your phone! :(

I had a good hunt through the full log... and it looks like a whole lot of apps die when you turn on USB... so I suspect you have moved a lot of apps to sdcard?? :confused:

If this is the case, then when you turn on USB storage, then I'm guessing all the apps suddenly die, and the system freaks out and restarts...
[Galaxy S II Original Android Development] imranrajah:
hi, thanks for the reply.

you mean i should do backup and a full wipe and reinstall the ROM?

You r right, i did move every single app to the internal SD card.

What i'm gonna do next:

1. I'll move some system apps back from SD card to phone memory and test the result. if the issue is resolved, fine.

or else

2. I'll do a full wipe and reinstall the ROM.

Will keep you posted of the developments.

Your advice is highly appreciated.
[Galaxy S II Original Android Development] tazsob:
That is a kernel problem that has since been sorted from what I know.. I'm using dorimanx 7.29, I suggest you try that and see if the problem persists. Don't change any settings in stweaks as its likely to cause the stutter you mentioned.. This ROM and dorimanx kernel as smooth as anything and you shouldn't have any issues at all with the combo
[Galaxy S II Original Android Development] aktorsyl:
Thanks a ton for your reply, tazsob :) I've since given NeatRom 4.0 (containing the leaked 4.1.2) a go and I absolutely love it. Minor issues here and there (battery drains a bit faster etc) as can be expected from a leak. Will see what the ROM devs come up with once the official firmware is released. Personally I'm hoping the NeatRom devs release an update containing the official firmware - their Lite package is amazing.

Thanks again for the advice!
[Galaxy S II Original Android Development] HardCorePawn:
That is your problem... Unless you have dual mount, when you mount your USB storage, the phone loses all access to the sdcard... So if you put all the apps on there, they all "disappear"...

No wonder your phone crashes if you moved all the system apps! :rolleyes:

I am fairly sure there is even a warning that "some apps might stop working" when you go to mount USB storage :p
[Galaxy S II Original Android Development] imranrajah:
Hi, sorry for this noob question.what do u mean by dual mount?
[Galaxy S II Original Android Development] mobix:
Dual booting is the ability to boot into two different Ice Cream Sandwich-based ROMs, more details can be found HERE.
[Galaxy S II Original Android Development] nk7:
Using that same kernel with Slim 3.1 with Slim Gapps. No hangs or locks. Everything smooth. Using default cpu governor and i/o scheduler.

I test with default config for a few days then start making changes like OCing and still no issues...some schedulers can be aggressive and I/O as well...

First of, did you check md5 sums for ROM and Kernel to make sure nothing corrupted was flashed (I doubt this but good to be sure). And you did the whole format system and wipe data prior as well?

imranrajah was asking about dual 'mount' not dual 'boot' and you can dual boot ICS and JB now or any combination thereof...

Dual mount is mounting your sdcard (internal and/or external) to your PC (or similar) and to the phone at the same time. Someone else can chip in here for a better explanation. I think there is a small explanation in stweaks if dori or siyah kernel is being used (under 'Misc' tab).
[Galaxy S II Original Android Development] mobix:
My bad, thanks for correcting. High time to get eye-test done :silly:
[Galaxy S II Original Android Development] nk7:
No worries it is good to see that XDA still has helpful people around.
[Galaxy S II Original Android Development] randy.turker:
Guys is there anyway that i can get stock messaging apk not the black themed
[Galaxy S II Original Android Development] HardCorePawn:
you should be able to extract the messaging apk (Mms.apk) from the original ROM .zip file... (look in /system/app folder in the zip file)...

Then on your phone, you will need root access (use a root explorer, adb shell or terminal emulator) to remove the one that is currently there (/system/app)... and then copy the new one in and make sure to set permissions as 644...
[Galaxy S II Original Android Development] randy.turker:
Wow thats fast

Thx dude
[Galaxy S II Original Android Development] imranrajah:
Hi, thanks for your info.

I have moved all my apps to phone memory, now no crashes when i TURN ON USB STORAGE. :good:

Thanks a million.

Can you please explain to me what is DUAL MOUNT.

Thanks in advance.
[Galaxy S II Original Android Development] HardCorePawn:
That is a good start ;)

Suggest you try googling "android dual mount" or "android multi mount"... basically just allows you to mount SD Cards as usb storage and remain mounted on phone as well... DorimanX (and possibly Siyah?) kernels offer this... or you can use apps like:

Multi Mount...
[Galaxy S II Original Android Development] imranrajah:
I was asking about DUAL MOUNT. ;)

BTW thanks to you, i got to learn a new info called 'DUAL BOOTING'. :good:

I read the link you posted on dual booting. I guess dual booting is also available for JB roms? :D

---------- Post added at 12:15 PM ---------- Previous post was at 12:06 PM ----------

Wow, got it.

Thanks:D
[Galaxy S II Original Android Development] hello2ew:
Hello guys anyone else facing camera FC on SlimBean 3.1? I cleared data of the default camera app, used Camera JB+, and both apps are giving me FC's. I was on CM9 before I went to SlimBean. Followed the steps on Slimrom website. Any help?
[Galaxy S II Original Android Development] GaboWinter:
Here I don't have issues, I'm using the stock and Camera 360, both works fine, which steps did you follow? Did you perform a full wipe? Also, please attach a log to help to identify the issue.

EDIT: Follow the below advice of HCP, I must be more clear in my post to separate the issues on the Front and Read camera. :p
[Galaxy S II Original Android Development] HardCorePawn:
*sigh* Does anyone bother to use the search function these days? :rolleyes:

A quick search for "Camera" in this thread reveals some likely candidates... like this post...

But just to re-iterate... this is a known issue for the i9100... the FFC (aka front facing camera) is buggy on our devices... I believe it is something in the samsung binaries not liking what the CM guys have done to try to remove the shutter lag... I've tested CM10... and it does the same thing...

The rear camera seems to work fine... only workaround we can offer is use a third party camera for FFC... Camera Zoom FX works OK... as do a few others... NOTE: CameraJB+ doesn't because it is effectively using the same camera code as CM... so has the same issues...

Good luck... and if you find a decent camera... feel free to report it here so others may benefit :good:

ps. if you are getting FC's with the back cam... no logcat = no way to help...
[Galaxy S II Original Android Development] gGabi:
Is this ROM stable for daily use? I mean... at least as stable as cm9?

I know JB is not working so good with our phone, for the moment, and I don't want to upgrade blindly. I'll be happy to come back to slim :) Thank's
[Galaxy S II Original Android Development] GaboWinter:
IMO, it's definitely a daily driver and more than that, works really well.
[Galaxy S II Original Android Development] dexvholt:
Can you add ParanoidAndroid to this that would be awesome! I know there is tablet UI etc.. but it's just not the same! So please add it O:)
[Galaxy S II Original Android Development] trveller72:
Working better I will say.
[Galaxy S II Original Android Development] Cryptostasis:
Can I flash Siyah 5.0.1 on the 3.1 version of this Rom? Are there any issues if I will do that?
[Galaxy S II Original Android Development] HardCorePawn:
At the moment... SlimBean 3.1 is based on CM10... which is JB 4.1.2... Perfectly stable, just a few minor issues (like the front cam being a little buggy)... which are easy enough to work around :good:

The JB that isn't working that well on our phone is 4.2... the CM guys (who do some totally fantastic work btw!) are having to do some MAJOR hAxX0rZ to make it all work on the i9100 due to Samsung still being all sekrit squirrels with their source code etc :rolleyes:

Having said that... the Alpha1 build of the next Slim version that we have seems to be pretty decent for daily use... granted it is currently missing a lot of the features of Slim3.1 (they just haven't been ported over yet ;)) and a few things just don't work, like the camera (again, some fixes from need to be ported in)... but we're getting there slowly :)
[Galaxy S II Original Android Development] nk7:
+1 to this comment. Definitely a stable and smooth ROM - so no need to worry about bricking your phone or having random reboots or FCs etc. Well none that I noticed anyway.
[Galaxy S II Original Android Development] hello2ew:
Here is my logcat
[Galaxy S II Original Android Development] HardCorePawn:
Like I said... it is a known bug... there is very little we can do about it until Samsung get their **** together and release some proper sources that the dev community can use...

I suggest finding a 3rd party camera if you need to use the frontcam... you'll just have to put up with the shutter lag...
[Galaxy S II Original Android Development] hello2ew:
No sir it's not about the FFC I knew about it for a long time it's the rear camera which also FC's
[Galaxy S II Original Android Development] HardCorePawn:
That is strange then... all I can suggest is take a nandroid backup...

Then full wipe, then mount /system, format /system (yes I know that the install says it does this, but some stuff is going on in the background to backup some things, so I suggest doing it manually!), then install 3.1 and then Gapps as req'd...

see if the camera is still FCing...
[Galaxy S II Original Android Development] hello2ew:
I did all those except for mount system... Will it help? Maybe I'll try tonight. Heres another logcat. Hopefully its clearer. This one FCed on first touch of the shutter button.
[Galaxy S II Original Android Development] hello2ew:
It still FCs. I did exactly what you said, and the rear camera still FCs. I'm using Dorimanx Kernel, but I dont believe its the kernel problem since Gabo uses it too with SlimBean 3.1. My addons are the inverted framework(FCs occcured without it too), Google Now addon, and thats it. Anyway to diagnose this problem? Or at best fix it?
[Galaxy S II Original Android Development] HardCorePawn:
That is very odd... it honestly looks like the FC most people get with the front cam... Did you move this app to SD? or change the default save directory etc?

and have you tried any 3rd party camera's other than JB+??

Try:

Zoom Camera and/or UCam and see if they do the same thing...

And lastly, just to be completely sure (I'm 99.99% sure it won't make a difference)... can you try running the default kernel and seeing if the cam still FC's...
[Galaxy S II Original Android Development] hello2ew:
Nope the camera app is the standard camera app which comes with the ROM and its a system app. No moving around no changes made. I just tried UCam as you requested, and it seems to be working pretty fine here. Spamming it quite a few times and it takes all the pictures successfully. Do you have flashable zip for the default kernel?
[Galaxy S II Original Android Development] HardCorePawn:
Try the attached...
[Galaxy S II Original Android Development] hello2ew:
Tried it, but still FCs
[Galaxy S II Original Android Development] HardCorePawn:
Honestly don't know what else to try my friend... have you checked the SHA1 and/or MD5 checksums for your download? maybe the zip is corrupted?

SHA1: 14120ec0323031977cad14a2ad5782957a2202b9

MD5: 62f65cf666d40cc8bfb845e89cfc16ad
[Galaxy S II Original Android Development] bachot:
Sleeping Problem

Hey there,

im having a problem with my phone sleeping.

Sometimes when i lock my screen i can't get my phone out of it my screen just stays black and it never gets back on except if i do a reboot. this is kind of a Big issue cause im missing messages and calls.

Would this be the problem of the ROM or the KERNEL?

I hope someone can figure this out!!

Cheers.
[Galaxy S II Original Android Development] HardCorePawn:
Stock kernel? Custom Kernel?

also... I don't see a logcat attached to your post?? :confused:
[Galaxy S II Original Android Development] bachot:
Im using using dorimanx 7.26

What don't you understand about my post?

I'll explain it again: " Sometimes when i lock my phone with the right button on the phone my phone gets locked but im unable to unlock it again and my phone looks like its turned off so i can't do anything but its not really of i think cause sometimes it gets hotter then it should get when its off. so when that happens i need a reboot. im not sure if this is a ROM or a KERNEL problem"

Thanks
[Galaxy S II Original Android Development] biker14:
SiyahKernel v5.0.1

I am using the SiyahKernel S2-v5.0.1 without any issues since I installed this ROM.
[Galaxy S II Original Android Development] HardCorePawn:
I'm going to give you the benefit of the doubt here... and assume that you've already tried some basic troubleshooting... for instance:

You've tried running DorimanX on pure default settings (reset profile in STweaks, no UV, no OC, no messing with settings in STweaks) and you still get Sleep of Death (aka SoD)

You've tried the latest and/or previous version of DorimanX and you're still getting SoD

You've checked in DorimanX kernel thread for possible issues relating to your kernel

Asked for help in DorimanX kernel thread (at which point they'll also ask for logcat and other debug info)

You've tried using the stock Slim Kernel, and you still get SoD

If you manage to get all the way to point 5 on that list and you're still getting SoD, then you NEED to post some logcats and/or debug for us... I can't read your phone's debug logs just using the combined power of my mind and TCP/IP you know... :rolleyes:
[Galaxy S II Original Android Development] Didgesteve:
Did you wipe cache/davik cache before installing the kernel?

Try 7.29. It's solid, no SoDs or freezes.

It is important not to fiddle too much with the settings in STweaks. I know it's tempting, but Dorimanx is a top developer, and the way it comes 'out the box' is best.

But I don't think this is ROM related, there is a non dev discussion thead for Dorimanx here
[Galaxy S II Original Android Development] bachot:
i tried flashing the kernel again and honeslty i forgot wiping dalvik, ill give it some time now. mate.
[Galaxy S II Original Android Development] gGabi:
Thank's for your replies! I'm glad to be back to slim! 3 days now and not a single problem, except mdpi market, it doesen't work... but i did a dirty flash so that might be the cause ... except that, smooth and elegant.
[Galaxy S II Original Android Development] nrbrt:
wifi direct

Has anyone have wifi direct working? My phone has this option, but everything's disabled.
[Galaxy S II Original Android Development] angus1225:
Same here, instead I use Fast File Transfer, is a good application to send files via wifi

Enviado desde mi GT-I9100 usando Tapatalk 2