yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Makishima:
I don't know if this is helpful at all, but I had a SOD with the 10.43v49 on SlimKat with Awake: Nightmare and Sleep: Ondemand. It happened overnight and in the morning the battery was gone and completely dead so I couldn't get a log or something. Charging it now. Is this Nightmare's fault or something else perhaps?

Also, the phone is completely off while charging but it charges quite slowly, it seems to me. I saw another post saying it charges slowly but I don't know if it's the kernel's fault while it's turned off. Is it?
[Galaxy S II Android Development] gippy2:
First..Hyper is the only governor dori will support for stability... Not to say the others arnt...I use zzmanx but some have problems with it.. Rkoby seems to like nightmare but my phone doesn't... I guess try a few and see which one your phone responds to best...
[Galaxy S II Android Development] Jsilver73:
stuck at 800mhz

First of all - thank you [MENTION=2376110]dorimanx[/MENTION] and d team for bringing us this fantastic kernel.

I have been testing for more than 24h now and have encountered zero SOD or random reboots so from that perspective this seems nice and stable.

Only problem is not getting deep sleep (I have disabled media scanner) - well, when I say that I get some deep sleep - like a couple of minutes but then seem to sick at 800mhz (according to bbs) I have tried fresh install of carbon, and slimsaber with nothing but gapps, tb and bbs installed but still stuck at 800mhz - I have tried changing governors and io's but still the same results. I'm a bit confused now as to what the problem could be?

I have read back and see that others have had issues with deep sleep but see nothing of getting stuck at 800mhz - is anyone else seeing this or have I missed something blindingly obvious?
[Galaxy S II Android Development] m1trand1r:
guys...i'm running latest 10.43v49 and yesterday one weird thing happened which I couldn't log at all....sadly....but...I was outside and I received an sms....then my vibration was stuck....device was vibrating continuously and it didn't stop untill I did a force reboot ....oh and device was in frozen like state ...I couldn't do anything except Mdnie toggle which is set to 4 clicks was working....anyone faced something simmilar ?...

It's running fine since that happened..,0 problems :good:

Beam-ed through your pineal gland via//Android 4.3.1:p//
[Galaxy S II Android Development] Adithya88:
Yep, same thing happened to me also. difference is instead of sms, i received a call, when i tried to answer the call, phone just stuck, force rebooted it:( Another strange thing is, now system ui crashes every time i unlock my phone.:(:( Using hyper as awake, nightmare as sleep governor. Rest all stock settings. I am on v49 with latest slimkat

---------- Post added at 04:58 PM ---------- Previous post was at 04:52 PM ----------

Rebooted into recovery wiped cache, dalvik cache. Replaced nightmare with ondimand as sleep governor. All working fine now. No more system ui crash.
[Galaxy S II Android Development] m1trand1r:
i'm using HYPER/ONDEMAND combo for some time now....as nightmare didn't work as expected ....can you log this vibration stuck ?....It seems like a "bug" to me....maybe something to do with haptic feedback ?....i'll try to reproduce it and see...:fingers-crossed:

Beam-ed through your pineal gland via//Android 4.3.1:p//
[Galaxy S II Android Development] Adithya88:
is there any other way than connecting to PC for logcat?

coz, my PC is at service centre due to board related issues.

that is the reason I couldn't take logcat.

---------- Post added at 05:14 PM ---------- Previous post was at 05:13 PM ----------

I have to wait one more week to get my PC fixed. :(
[Galaxy S II Android Development] d_Schizzo:
Try Catlog app from playstore
[Galaxy S II Android Development] Adithya88:
thanks. will try it.
[Galaxy S II Android Development] Makishima:
I have changed to Hyper just to see if it happens again with this governor. I will post if it does.
[Galaxy S II Android Development] Adithya88:
WTF!!!! that damn thing happened me again. I opened poweramp app, at the same time I got a call and bammmmm phone got stuck. force rebooted it. attached logcat taken using catlog app.

hope it helps [MENTION=3763274]rkoby13[/MENTION]
[Galaxy S II Android Development] m1trand1r:
you took logcat after force reboot right?

That won't help....sadly...and don't curse please ....I still didn't get the issue again....waiting ...

Beam-ed through your pineal gland via//Android 4.3.1:p//
[Galaxy S II Android Development] Adithya88:
yep...I took it after reboot. there is no other way for me.:(

I am missing my PC badly:(
[Galaxy S II Android Development] dorimanx:
I need help from fellow testers!

I am trying to fix the apps 2 sd bug..

so i need someone to install ORIGINAL ROM 4.4.y Kernel and using adb pull the mount screen print...

Install Original kernel on FIRST ROM (4.4.y)

connect via adb

mount

copy paste the output and post here..

I need to see how it's should be mounted.

========

i have 4.3.1 ROM as Main ROM, and 4.4.2 as SEC for testing..

Thanks.
[Galaxy S II Android Development] pSyCh¤_O_O:
No PC :criying:
[Galaxy S II Android Development] Christiaan91:
shell@android:/ $ mount

mount

rootfs / rootfs ro,relatime 0 0

tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0

devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0

proc /proc proc rw,relatime 0 0

sysfs /sys sysfs rw,seclabel,relatime 0 0

selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0

none /acct cgroup rw,relatime,cpuacct 0 0

none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0

tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0

tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0

tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0

none /dev/cpuctl cgroup rw,relatime,cpu 0 0

/dev/block/mmcblk0p9 /system ext4 ro,seclabel,noatime,user_xattr,barrier=1,data=

ordered 0 0

/dev/block/mmcblk0p7 /cache ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,u

ser_xattr,barrier=1,journal_async_commit,data=ordered 0 0

/dev/block/mmcblk0p1 /efs ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,use

r_xattr,barrier=1,journal_async_commit,data=ordered 0 0

/dev/block/mmcblk0p10 /data ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,u

ser_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0

0

/dev/block/mmcblk0p12 /preload ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,

barrier=1,journal_async_commit,data=ordered 0 0

/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0

/dev/block/vold/179:9 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,

relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437

,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1

023,default_permissions,allow_other 0 0

/dev/block/vold/259:3 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,

relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437

,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/vold/259:3 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat

ime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,ioch

arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1

023,default_permissions,allow_other 0 0

/dev/block/dm-0 /mnt/asec/com.xs2theworld.voetballNL-1 ext4 ro,dirsync,seclabel,

nosuid,nodev,noatime,user_xattr,barrier=1 0 0

shell@android:/ $

I hope this is what you're looking for.

rom: slimkat (21 dec build)
[Galaxy S II Android Development] 7HUND3R:
When i open stweaks it goes "unexpected error!" and then it shows me all the tweaks..is it a problem/bug?
[Galaxy S II Android Development] fuchbitch:
Dori why don't you include in the kernel the correct recovery version for flashing kitkat 4.4 and you stick with older versions??
[Galaxy S II Android Development] dorimanx:
it's ROM bug, stweaks works as should any way.

IGNORE it :)
[Galaxy S II Android Development] dorimanx:
for you to ask.

before you READ :confused:
[Galaxy S II Android Development] Crazy-Silver:
Dori I have a strange problem. When I lock my phone I am not able to wake it. But it is not a sod because the screen seems to wake up but it stay black. Touchscreen sometimes works with the black waked screen. I have the some problem while charging so.... no sod but what is that? T.T I'm on latest SlimSaber + 10.43 latest beta.
[Galaxy S II Android Development] fuchbitch:
Dori i am sorry to piss you off , but i just don't see the answer anywhere ! Maybe because it's 2 am in my country ; nevermind. Great job with the kernel !
[Galaxy S II Android Development] nik60:
Hi

I had The same error, some time ago-is busybox

Thank for Kernel - 8.43v49 work fine db 2 Sammy
[Galaxy S II Android Development] fuchbitch:
Stock voltages and no uv/oc ? Crazy-Silver
[Galaxy S II Android Development] Crazy-Silver:
All stock.

EDIT: Disinstalled Greenify and all works now. Thanks for your time and sorry.
[Galaxy S II Android Development] RovG:
[MENTION=2376110]dorimanx[/MENTION], I believe the same or similar issue was fixed by the dev herna in the official Omni build and was submitted via gerrit. I am trying to find the post or patch & will update.
[Galaxy S II Android Development] br3ak:
I am stuck at the dorimanx kernel boot screen logo using the latest version of saberslim. Any suggestions? I am new to the S2 scene.
[Galaxy S II Android Development] m1trand1r:
Q/A thread and happy reading newbie:)

Beam-ed through your pineal gland via//Android 4.3.1:p//
[Galaxy S II Android Development] dorimanx:
that is what i needed! GOOD work!

you just helped to SOLVE the apps2SD bug with my kernel :)

MY output!

rootfs / rootfs rw,noatime,nodiratime,size=406484k,nr_inodes=101621 0 0

proc /proc proc rw,noatime,nodiratime 0 0

sysfs /sys sysfs rw,noatime,nodiratime 0 0

/res/dev/system /system ext4 rw,noatime,nodiratime,journal_checksum,journal_async_commit,noauto_da_alloc 0 0

tmpfs /dev tmpfs rw,nosuid,noatime,nodiratime,mode=755 0 0

devpts /dev/pts devpts rw,noatime,nodiratime,mode=600 0 0

none /acct cgroup rw,noatime,nodiratime,cpuacct 0 0

none /sys/fs/cgroup tmpfs rw,noatime,nodiratime,mode=750,gid=1000 0 0

tmpfs /mnt/asec tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0

tmpfs /mnt/obb tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0

tmpfs /mnt/fuse tmpfs rw,noatime,nodiratime,mode=775,gid=1000 0 0

none /dev/cpuctl cgroup rw,noatime,nodiratime,cpu 0 0

/dev/block/mmcblk0p11 /mnt/.secondrom vfat rw,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mix

ed,utf8,errors=remount-ro 0 0

/dev/block/loop0 /cache ext4 rw,nosuid,nodev,noatime,nodiratime 0 0

/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,nodiratime,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0

/dev/block/loop1 /data ext4 rw,nosuid,nodev,noatime,nodiratime,journal_checksum,journal_async_commit,noauto_da_alloc 0 0

/sys/kernel/debug /sys/kernel/debug debugfs rw,noatime,nodiratime 0 0

/dev/block/mmcblk0p10 /data_pri_rom ext4 rw,noatime,nodiratime 0 0

/dev/block/mmcblk0p9 /system_pri_rom ext4 rw,noatime,nodiratime 0 0

tmpfs /mnt/ntfs tmpfs rw,noatime,nodiratime,mode=777,gid=1000 0 0

/dev/block/vold/259:3 /mnt/secure/asec vfat rw,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mi

xed,utf8,errors=remount-ro 0 0

/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,nodiratime,noauto_da_alloc 0 0

/dev/block/dm-1 /mnt/asec/com.keramidas.TitaniumBackup-1 ext4 ro,dirsync,nosuid,nodev,noatime,nodiratime,noauto_da_alloc 0 0

/dev/block/vold/179:9 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime

=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,noatime,nodiratime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

/dev/block/vold/259:3 /mnt/media_rw/sdcard0 vfat rw,nosuid,nodev,noexec,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iochars

et=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noatime,nodiratime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

root@android:/ #

================

as you can see titanium backup is moved to SD and loaded after boot! :)

i see new file in SDCARD

com.keramidas.TitaniumBackup-1.asec

please check your internal storage:

do you see your app in ROOT of the sdcard?

com.xs2theworld.voetballNL-1.asec

or it's in .android_secure ?

Thanks a lot for HELP :)
[Galaxy S II Android Development] gippy2:
You think dori sticks with an old recovery cos he can't be bothered lol...No there's a reason a big reason and half of xda knows why...See if you can work it out ....And dont post the answer here thanks....
[Galaxy S II Android Development] Christiaan91:
ART takes a lot of time to rebuild :(

to be honest i can't find the app on the sdcard and the .android_secure directory is gone.

I just had the same problem with stock kernel a few times, so i don't think it's a kernel problem. Dirty flashed the 19 build but the problem is still there. Only a full wipe will probably solve this.
[Galaxy S II Android Development] fuchbitch:
Found the answer partially , posted by someone in the Q&A who whas telling another guy(he was having dorimanx 9.43 brach kernel) to, firstly flash a kernel with a newer recovery before flashing slimkat ! But still i don't understand why ... Maybe because i am relatively new here ( 3 weeks since i got my i9100) ! :silly:
[Galaxy S II Android Development] gippy2:
[MENTION=5170800]fuchbitch[/MENTION] pm me if you want to know..whilst you can tell me what the partial answer is lol
[Galaxy S II Android Development] dorimanx:
ART? i didnt tried it, but it's some other dalvik build... so i cant really do any thing...

with default kernel its FAST?

about app not on sdcard and .android_secure folder is gone:

if app not on sdcard root, then its in .android_secure

.android_secure is ROOT access only folder, so you can see if only with mass_storage mode, and using my kernel! (the dual mount is running as ROOT)

so you will see the folder and the app inside it.

i am very close to release BUG fix.

doing last mods and tests...
[Galaxy S II Android Development] Christiaan91:
i didn't use your kernel. I was still on the stock kernel that comes with SlimKat. I can flash your kernel if you want.

I'm going back to dalvik. ART takes up around 20 mins for me and i had to do it 7 times today.(and no big difference on speed)
[Galaxy S II Android Development] Misk77:
10.43v.49

Flashed latest 10.43v.49 with Slimkat 4.2.2.

So really FAST and smooth.

No problem so far.

Default and report if any issues.

THX Dorimanx
[Galaxy S II Android Development] gippy2:
Don't bother with art its pointless at this stage not enough benefit if any and the time loading up all the time is not good if you are a flashaholic.......
[Galaxy S II Android Development] dorimanx:
News Update!

I have finally fixed the apps2sd for KITKAT 4.4.y ROMS support.

Now all works as should.

I have uploaded V50 BETA (3 kernels branches) to my BETA Storage SEE OP for LINK!!!!

Added all new Main Line kernel updates. some are urgent! about RAM stuff...

Kernel is close to Release...

Kernels (last)> https://github.com/dorimanx/Doriman...mmit/83d4c5d4d6ada885fbe4149d6b013bab23ffab80

initramfs > https://github.com/dorimanx/initramfs3/commit/3ac50f8a92ddc8c8d4419dc4105f355eb4445c03

All the SODS using CPU govs OTHER than HYPER/ONDEMAND/Pegasusq/Inteliondemand,

are not interest me, as i posted not once that other govs not supported and not updated!

and considered UNSTABLE for daily usage...

you got stuck, not my problem... i am thinking to disable them for good...

but some will say: NOOOOO! it's working good for me! that is the only reason that i didnt EXTERMINATED them long time ago! :)

Any way all great here with Hyper/ondemand as always...

have fun testing and check the app2sd in/out and apps load after boot :)

it's important.
[Galaxy S II Android Development] fatjoez:
I work in customer service for a living, my advice is disable them.

Deliver a quality stable product with less options, people will eventually like this more

Ask yourself why apple iphone is so popular but is so locked down.

Burn the govs and focus on the ones you use
[Galaxy S II Android Development] stopro:
And am missing all that stuff i feel shame good luck mate
[Galaxy S II Android Development] gippy2:
No blasphemy on here please :D:banghead::banghead:
[Galaxy S II Android Development] Misk77:
10.43V50

Flashed v50.

No problem and app2sd worked..but I could move apps in the previous beta as well. Report if issues.

If you wanna some help or code..tip ..look or talk to Ktoonsez ..KT kernel. He's very helpful but working alone with he's kernel..he is working nearly 24/7 with all he's kernel. A very impressive kernel for all branches and phones. Think you two could get some good things from each other.
[Galaxy S II Android Development] Adithya88:
Flashed latest v50. [MENTION=2376110]dorimanx[/MENTION] But sorry, sorry for disturbing you.

storage issue still causing me a lot like, i can't take screenshot. It says storage may be in use or not available.

I cant take logcat using catlog, it says cant write to storage.

And receiving files via bluetooth also not working.

Can u please look into this matter.

I am on slimkat v1219.
[Galaxy S II Android Development] pSyCh¤_O_O:
App2sd sticking on reboot :D :thumbup:
[Galaxy S II Android Development] Jsilver73:
v50 still stic sticks at 800mhz

Please, I'm really not complaining, just reporting my findings:

See attached screen shots, very little deep sleep and something is keeping CPU at 800mhz - I tried last night with v49 using clean fresh install of slimsaber with nothing but yourz minimal gapps + tb + bbs - running on dalvik, the results were exactly the same, is this issue only happening to me?

I've always used dori kernel and love it, I just can't understand why this is happening.

Same set up zero issues with stock and Gustavo kernels.

I'm going to swap kernels now and post screen shots of CPU usage same set up to show comparison.
[Galaxy S II Android Development] 7HUND3R:
App on the SD survive reboot on v50!

Now testing deep sleep and my settings..I found that kitkat is battery hungrier than jellybean but this may be because it is in an early stage..is very good at daily driver..

I had a couple of language reset after reboot and a soft reboot after changing my wallpaper but I don't really believe it is kernel related..I'll repost that to rom thread :)
[Galaxy S II Android Development] cybernetus:
Try the logcat using adb on your desktop.
[Galaxy S II Android Development] Jsilver73:
800mhz sticking issue

Further to my report here are screen shots of Gustavo for comparison with exact same ROM/apps set up.
[Galaxy S II Android Development] budsixz:
Guys i can't download from computoncio

What do i do
[Galaxy S II Android Development] Adithya88:
I wish i could.... :P... my pc is at service centre... Anyone else having this issue? or only me...?

I want to take logcat but i cant... Feeling sorry for that... :(

One thing i can confirm that i can access internal and extenal storage using file managers.

May be what i am thinking is, android system and other user apps are not having permissions to access storage.

Any idea guys? :confused:
[Galaxy S II Android Development] cybernetus:
Without logs, no ...
[Galaxy S II Android Development] Adithya88:
Its ok... Thanks....

---------- Post added at 05:11 PM ---------- Previous post was at 05:07 PM ----------

Dorimanx.com/beta-test

Do not flash test version unless you know what you are doing.
[Galaxy S II Android Development] eskriminal:
slimsaber faq gogogo
[Galaxy S II Android Development] Jsilver73:
800mhz

Just tried [MENTION=4663860]Computoncio[/MENTION] build v50 but still getting the same limited deep sleep and CPU stuck at 800mhz - is anybody else having this issue or know anything?
[Galaxy S II Android Development] Computoncio:
Why you can't download?

Can you explain....

Phone: Samsung Galaxy SII - GT-I9100

Kernel: Dorimanx kernel v10.43v50-mv3

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

2nd ROM :

MODEM: Modem+RIL - XXLS8

MODS: Partition Fix, Hue Blue v4.4 by Kroz :good:
[Galaxy S II Android Development] Shahan_mik3:
Hmmm try this

Create a folder and name it screen shots inside pictures folder.

It should work.
[Galaxy S II Android Development] :
I've had that too. Its to do with Google accounts. Check your logcat. I deleted Google accounts and re added. All good in the hood now. :thumbup: :)
[Galaxy S II Android Development] sien1996:
hmm yeah or you could do it the caveman way and take another phone or camera and take the photo of your phone then upload it here. :p use that as last resort though haha :silly:
[Galaxy S II Android Development] Jsilver73:
800mhz

Thanks for this although I can now report that after going into recovery then rebooting system from there recruiting seems to be as it should be, lovely deep sleep and no sticking at 800mhz - :)
[Galaxy S II Android Development] budsixz:
Well the download gets stopped anytime n says it was unsuccessful

(i m using my phone to download)

Anyways i have downloaded from dorimanx. Com

Will test now
[Galaxy S II Android Development] Adithya88:
Will do it once i reach home... Thanks
[Galaxy S II Android Development] corsicanu:
10.43v50 with 1st rom cm10.2 19.12 nightly and 2nd CyanFox2.0.1 working like a charm.. tested on both roms and no sods, no wakelocks, apps are where should be, art working on cyanfox and the best from all is that in 3h and 27mins with data/wifi enabled battery drained was at 10% on 4.4... I love this kernel even more!!! Great job dori! Best Christmas present!! :D :beer:
[Galaxy S II Android Development] dorimanx:
reset stweaks profiles using my recovery advanced tab.

gustavo kernel is not my kernel...

but its also use stweaks.

and yes that bug is local to your device.

Sent from my GT-I9100
[Galaxy S II Android Development] nihilista:
Tried to install slimsaber 4.4.2 to 2nd rom, but fails with error.

Warning: No file contexts

set_metadata_recursive: some changes failed

Error ... (status 7)

Did i miss something?
[Galaxy S II Android Development] aceman2013:
Read post #5312.

There you will find the answer.
[Galaxy S II Android Development] nihilista:
Ah thx, was impossible to read he whole thread and search won't give me what i needed ;)
[Galaxy S II Android Development] altojd:
dori your kernel is terrific. any chance to have it with twrp recovery?
[Galaxy S II Android Development] gippy2:
Don't ask stupid questions especially in a beta test thread...
[Galaxy S II Android Development] oL00No:
Out of test thread. Into q/a, where you'll be yelled at for not searching something dori has answered 7 times.
[Galaxy S II Android Development] nuraniharun:
Hi dorimanx.

8.43v50 gives parsing error at installing apk package.

I revert to 8.43v49 for test. V49 is ok. Can you fix this?
[Galaxy S II Android Development] Troubadour666:
Hi.

I replace meta-inf in slimsaber last. Flash and boot it fine with v50 from [MENTION=2376110]dorimanx[/MENTION] on 2nd ROM.

And sorry for the thread i have posted some days ago.

Thanks

Envoyé de mon GT-I9100 en utilisant Tapatalk
[Galaxy S II Android Development] Adithya88:
Nope....method not working. I tried using root explorer...but cant create new folders. It says creation folder failed:(

Anyways thanks for help.:thumbup:
[Galaxy S II Android Development] Adithya88:
Here is the screen shots.

I can send files to another device but cant recieve files to my device. Even i checked errors in sd cards in a laptop,all are fine.

I think the only way left is a clean install of rom and kernel....