yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] kostelo:
I just installed -070 over the previous version that was FCing on me and, after clearing play services data, everything is fine and no random FC (high accuracy location etc). At last. :)
[Galaxy S II Android Development] easyyu:
I try install latest google play service v7.5.73 (1976294-470) but it still gave me force close message..

It is very annoying. I try to wipe data of gplay service try clear cache.

Then clear all cache dalvik with TWRP but it didn't help.

Someone mentioned to disable location service, but I only found Fused Location in Titanium, and I disabled it. Gplay service still FC.

Some idea?
[Galaxy S II Android Development] Nightshadow931:
Turn off location services in settings.
[Galaxy S II Android Development] j1gga84:
Here is a patch that should be implemented in all kitkat builds as I read in Slim Gapps thread:

https://android.googlesource.com/platform/libcore/+/08d97aee56db51f718544562f5b74671be34dfaf

But I doubt development still goes on.. Most developers lay their focus on LP now..

I think only [MENTION=1228651]fusionjack[/MENTION] could help or say something concerning that patch. Because I don't know what it will do and if it is still necessary after Google play services update

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy S II Android Development] governmentissuejoe:
delete
[Galaxy S II Android Development] fusionjack:
yes, this is the fix for google plays service fc. this fc only happens when the rom is compiled with gcc 4.9...i'll try to find time to compile a new build tomorrow. otherwise, i hope thunder can compile it for you all.
[Galaxy S II Android Development] easyyu:
Any news about fc with gplay service?

Did anyone compiled?
[Galaxy S II Android Development] Chillmann:
Patience my friend, he said, he will try to compile tomorrow. That tomorrow is only 3 hours old, at least in my time zone ;)
[Galaxy S II Android Development] m1trand1r:
just wait .. [MENTION=1228651]fusionjack[/MENTION] is a busy man with real life and stuff:) It will come when it's done...:)

/LG-G3/d-855/16Gb/Titanium Black/
[Galaxy S II Android Development] m1trand1r:
guys....with gapps fc's issues ...try this:

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

hit [MENTION=5180758]Natakranta[/MENTION]'s thanks button :)
[Galaxy S II Android Development] Nightshadow931:
It doesn't work. As soon as I turn off location services, I get fcs.

As [MENTION=1228651]fusionjack[/MENTION] said, it's ROM's problem.

We just need to wait for a new version. :)

Sent from my GT-I9100
[Galaxy S II Android Development] easyyu:
I have very interesting problem on this ROM with whatsapp..

When I close app, after some time if someone write to me I do not receive it...

On other side it show in whatsapp as I'm offline but I'm not. Viber working OK as all other chat apps..

If I start whatsapp then I receive all message.

To mention, I do not kill whatsapp and there is no app for killing other app.

It is not always the case..sometimes I receive message normally but most the time I faced with this problem.

I try to uninstall, wipe cache, data...dalvik for all apps from TWRP..

Also try to reinstall ROM, before wipe system, data, cache, dalvik, and install whatsapp on clean ROM, but it is same.

Anyone have some solution for this?
[Galaxy S II Android Development] kalivos:
for fc gplay service..

i had it once

this is how i fix it..

disable gplay service in app option - reboot - enable it - reboot to recovery - flash the gapps again - no fc
[Galaxy S II Android Development] lations:
It's screwed. All you can do is clear cache for Google Play Services, but it comes back eventually after a 12-14 hours.

Really frustrating.
[Galaxy S II Android Development] darkpollo:
Did you try to turn off location?

It worked for me.
[Galaxy S II Android Development] fusionjack:
Markox89 just contacted me, he has compiled a rom with the commit that should fix the play service fc, but he still gets the fc.

this fc on kitkat is actually kind of surprise me since this fc should only related to ART and gcc 4.9, but Markox89 is still using gcc 4.8.

could someone grab a logcat with fc error? you might need to grab the logcat from pc with "adb logcat > logcat.txt"

edit: speaking of which...we are also using gcc 4.8. this makes me more doubt whether this is the same issue with the lollipop one or not.
[Galaxy S II Android Development] m1trand1r:
well...I dunno if this may be related in any way...but...i'm using last SlimLP 5.1 minimal package gapps by [MENTION=1277872]dankoman[/MENTION] and I did wipe system/data/ and caches prior flashing anything than I flashed rom & gapps and some goodies on top...did a reboot and everything is fine since then....now rom & kernel are compiled with below:

if that means anything to you for KK builds...:)

Cheers mate:)
[Galaxy S II Android Development] Chillmann:
Just wiped play service app data, so I have a few hours peace from fc. As soon as they come back I'll grab a log if no one else did it by then.

Best regards, Chillmann
[Galaxy S II Android Development] fusionjack:
unfortunately no, the fc is fixed in 5.1.1.
[Galaxy S II Android Development] akhil17kr:
How much battery life you guys are having on Latest 4.4.4: 20150406 ?

Can we get screen on time more than 2.5 hours ?

How's standby time ?

Which kernel and custom settings you are using to get good battery life ?

Can i opt for this ROM if want good battery life and good balance b/w battery , performance and stability ?
[Galaxy S II Android Development] j1gga84:
[MENTION=1228651]fusionjack[/MENTION]

does this help:

http://xdaforums.com/showpost.php?p=61268342&postcount=994

Do you also know why latest build of skype ( (Video)Calls) does not work with SlimSaber 4.4.4 ? Only chat..

regards
[Galaxy S II Android Development] pedrocrv:
Hey people!

I have installed this latest version and yesterday, when i try to connect te phone to the computer with Kies, it doesn't recognise my phone, and if i do the things directly on windows explorer (like a normal USB device), transfer data is too slow or a lot of errors occurs...

What can solve this?

Thanks
[Galaxy S II Android Development] Saber:
I thought this was already confirmed to be a sabermod problem.
[Galaxy S II Android Development] easyyu:
Try install Wifi ADB on mobile and use it with Total commander ADB plugin.

Connect with USB and it will fly!
[Galaxy S II Android Development] pedrocrv:
Is not possible with kies? Or any other away?
[Galaxy S II Android Development] kostelo:
Forget KIES with custom roms based on AOSP.
[Galaxy S II Android Development] thunder45:
Please find my logcat attached. There are lot's of crashes in there.

I just followed the procedure from here now https://jira.cyanogenmod.org/browse/BACON-3810?focusedCommentId=67877&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-67877

so its looking good now. But as people said, it will probably come back in a couple of ours.

By the way, the fix for lollipop is this one? https://android-review.googlesource.com/#/c/143200/

Thanks
[Galaxy S II Android Development] fusionjack:
lollipop error might be different with kitkat one.

skype call error is a toolchain optimization issue. it might have something to do with O3 optimization, no matter which toolchain is used.

i think i'll compile the next build without any toolchain and art optimization.
[Galaxy S II Android Development] fusionjack:
use the patch from my github lp5.1 branch because the one from aosp cannot be applied because of the benchmark thing.

the kitkat issue probably is different with the lollipop one. that patch fixed play service fc for 5.0.x
[Galaxy S II Android Development] fusionjack:
this should be the error of play service fc:

06-11 23:01:25.427 I/DEBUG (1853): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-11 23:01:25.427 I/DEBUG (1853): Build fingerprint: 'samsung/GT-I9100/GT-I9100:4.1.2/JZO54K:user/release-keys'
06-11 23:01:25.427 I/DEBUG (1853): Revision: '14'
06-11 23:01:25.427 I/DEBUG (1853): pid: 3861, tid: 3888, name: nlp-async-worke >>> com.google.android.gms.persistent <<<
06-11 23:01:25.427 I/DEBUG (1853): signal 7 (SIGBUS), code 128 (SI_KERNEL), fault addr 00000000

i need to research what the code 128 (SI_KERNEL) means.

does this fc happen only in custom toolchain? which rom has this issue?
[Galaxy S II Android Development] thunder45:
This is your 20150406 build.

Thanks
[Galaxy S II Android Development] officiallyme:
Hi together

I wanted to repartition my SII because I am having problems updating Google Services etc. sometimes and then have to uninstall apps first. Very annoying.

So when I do my clean install afterwards, I wanted to clean everything. Is the "Radio Cleaner" in the 3rd post still current/working and is the included LS8 modem still the best choice for our device?
[Galaxy S II Android Development] Twiq:
I don't think you need to flash that radio cleaner, i mean you clean installed the rom, and your ROM still has the openril libs clean (untampered).. Unless you wanted to change modems then that's a different story, try xxms4 if you haven't :)
[Galaxy S II Android Development] AA666:
For me it was repartition after stock and clean install with Slim-Addons-mini_gapps.4.4.4.build.9-20150107 .

Perhaps we can try some other kernel? I can't test it with Doriman because it can't mount my ext4 SD card correctly.
[Galaxy S II Android Development] ssanyi:
Post 13092 in this link http://xdaforums.com/oneplus-one/development/rom-cm11-temasek-build-t2870743/page1310

You probably googled it out, but it worth a share...
[Galaxy S II Android Development] thunder45:
So you mean that we need to :

use a 4.8 Toolchain

+

remove O3 optmization

+

apply libcore fix

So that the FCs are fixed?

Regards
[Galaxy S II Android Development] j1gga84:
[MENTION=1597520]Markox89[/MENTION] will switch to sabermod 4.9 toolchain in his next build, no idea if this will solve the FC's..

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy S II Android Development] ssanyi:
I'm not saying 'we need to', I only shared some thoughts (from oneplus-one 5.1.1 development forum).

At least it worth a try if anybody has resources (machine & time) to make a build with that settings...
[Galaxy S II Android Development] Saber:
You see, it might not do anything. We're using sabermod 4.8 in this ROM, while temasek uses linaro GCC 4.8 (which he eventually got it not to FC). Not sure if switching between sabermod and linaro GCC would make much of a difference too.
[Galaxy S II Android Development] thunder45:
Sorry if I sounded rude, that wasn't my intention. That was exactly what I was looking for: some thoughts so we can try.

I'm freeing up some space on my VM to build.

Could someone point me to the libcore fix? [MENTION=1228651]fusionjack[/MENTION] told us to look at his lp5.1 so I came here , I could not identify the fix.

Thank you in advance
[Galaxy S II Android Development] officiallyme:
hmmm, i wanted to reflash because I was having problems receiving calls. Flashed the cleaner and now I can take calls again. Buuuuut now the signal is weaker and keeps dropping out altogether. So LS8 is not really ideal.

I couldn't find your MS4 anywhere. Do you have a flashable version by any chance?
[Galaxy S II Android Development] Sun90:
check the link below u might find one there :)

http://xdaforums.com/galaxy-s2/general/ref-samsung-modem-ril-cwm-installers-t1881304
[Galaxy S II Android Development] thunder45:
I got it. I undertstood what [MENTION=1228651]fusionjack[/MENTION] mean now. I'm cherry-picking the fix now and will build.

Meanwhile I have an unoptimized build compiled with UberTC 4.8 (both kernel and rom). Maybe that shall fix at least [MENTION=4699854]j1gga84[/MENTION] problem with skype.

For those who want to give a try, it is SlimSaber_UBERTC4.8_unoptimized

Regards
[Galaxy S II Android Development] AA666:
No doubts from my side, it is here

https://github.com\SlimRoms\android_libcore\commit\faeae8da0755f981612289c4eb5b0d12803c44a9

and here are two useful comments by Ray W about this fc for CM12 one+

https://jira.cyanogenmod.org\browse\BACON-3810

from my understanding we need to partially revert this commit for 4.8 chain

Hope this helps
[Galaxy S II Android Development] thunder45:
Yes, you are right. I have asked fusionjack if the libcore fix you mentioned (from AOSP) could be applied, and he said no. At the time, I didn't understand why, but when I took the time to check libcore at Slim codebase I realized there was no "benchmark" or "test" directories at Slim (so that is what fusionjack meant). So, from the three files fixed at AOSP, only one was required to be merged.

I have cherry-picked that already, and build is on the way (unoptimized and using UberTC 4.8).

Nevertheless, fusionjack is not sure the problem on lp5.1 is the same we have here at kk4.4. Also, some people think that the problem at libcore is for 4.9+ toolchains only. And we are using 4.8 in kk4.4.

Anyway, it doesn't hurt trying, and the build unoptimized + UberTC 4.8 + libcore fix should be ready by the end of the day.

Thanks
[Galaxy S II Android Development] fusionjack:
thanks for building...

i'm curious if this build could solve the play service fc, so let the user test. it should however solve the skype call issue.
[Galaxy S II Android Development] j1gga84:
Will I have any disadvantages if I flash/use this build?

Less snappyness for example? ;)

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy S II Android Development] thunder45:
Thank you [MENTION=1228651]fusionjack[/MENTION] , I'm just trying to help you with the minimum knowledge I got so far. I know you have been very busy.

By the way, did anybody else tested the load I built yesterday? I have dirty flashed it over 20150406 load, and so far I could NOT reproduce play service fc's anymore!! I have High Accuracy mode on, and opened the usual suspects:

- Yahoo Mail

- Waze

- Google Maps

- Instagram

- GPS status

So far, so good! And remember, that build does not have libcore fix yet, I have just disabled O3 and memory optimizations (and built the Kernel with 4.8 as well).

Anything else I could try to reproduce the problem?

Thanks
[Galaxy S II Android Development] thunder45:
I didn't notice any snappyness loss. But I haven't yet installed all my 50 usual applications. There is a chance we lose a bit of it at the end, but so far the trade off is minimal in my point of view.

Regards
[Galaxy S II Android Development] AA666:
Thanks for building, just got headset from my spouse and did dirty flashing and no more google location fc. Good job!
[Galaxy S II Android Development] Saber:
[MENTION=5103629]thunder45[/MENTION] [MENTION=1228651]fusionjack[/MENTION] Unfortunately, the build without optimizations doesn't solve the Skype issue here. Other than that, everything else is working fine with my kernel.
[Galaxy S II Android Development] thunder45:
Would you have a logcat?

I'll install skype as well and give a try myself.

Thanks
[Galaxy S II Android Development] thunder45:
At least for me, skype problem is the same we have seen a couple weeks ago with that skype beta:

1) it misses libstlport_shared.so

2) if we soft link libstlport_shared.so to libstlport.so, then we get an error trying to open the CameraProxy:

06-17 19:58:24.210 E/dalvikvm(16913): dlopen("/data/app-lib/com.skype.raider-1/libcodecs.so") failed: dlopen failed: cannot locate symbol "_ZN7android12CameraSource16CreateFromCameraERKNS_2spINS_7ICameraEEERKNS1_INS_21ICameraRecordingProxyEEEiNS_4SizeEiRKNS1_INS_7SurfaceEEEb" referenced by "libcodecs.so"...

Has anyone seen any discussion around this issue?

Regards
[Galaxy S II Android Development] rubentkato77:
What kernel? 15-06?
[Galaxy S II Android Development] Saber:
What I mean is my personal builds of Dorimanx kernel.
[Galaxy S II Android Development] Twiq:
here you go bro, note that it's just the modem without RIL libs
[Galaxy S II Android Development] thunder45:
I just gave a try in a CyanogemMod load I just built with UberTC 4.8. It has no Play Services FC's and Skype works fine. Also. [MENTION=4699854]j1gga84[/MENTION] mentioned it works on stock ROMs.

[NOOB MOMENT]

Would it be possible that there are changes to AOSP kk4.4 that have been ported to CyanogemMod but not to Slim?
[MENTION=1228651]fusionjack[/MENTION], are SlimSaber forks up to date with the latest Slim in kk4.4?

[/NOOB MOMENT]

Regards
[Galaxy S II Android Development] rubentkato77:
Any chance to get this build mate? :good:
[Galaxy S II Android Development] fusionjack:
i believe mine is more uptodate than slim one since slim didn't update kk4.4 anymore.

btw, how did you disable the toolchain optimization? did you disable the flags in the galaxys2-common or i9100 repo? can't remember where i did it.

edit: https://github.com/SlimSaber/device_samsung_galaxys2-common/blob/kk4.4/BoardCommonConfig.mk

you need to disable o3, strict-aliasing and opt_memory. one of them is causing skype call issue.
[Galaxy S II Android Development] thunder45:
You are right [MENTION=1228651]fusionjack[/MENTION], all I did was to comment out the following at device/samsung/galaxys2-common/BoardCommonConfig.mk

#TARGET_USE_O3 := true
#OPT_MEMORY := true

While building cm11, I had also to disable strict-aliasing, since cm11 does not have your fixes for that.

So, yes, its worth trying anothe build with strict-aliasing also disabled:

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.4
SLIM_VERSION=Slim-4.4.4.build.9.0-UNOFFICIAL
TARGET_PRODUCT=slim_i9100
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a9
TARGET_GCC_VERSION=4.8
TARGET_GCC_VERSION_EXP=4.8
TARGET_USE_O3=
SUPPRES_UNUSED_WARNING=true
STRICT_ALIASING=
OPT_MEMORY=
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.16.0-39-generic-x86_64-with-Ubuntu-14.10-utopic
HOST_BUILD_TYPE=release
BUILD_ID=KTU84Q
OUT_DIR=/home/thunder45/i9100/slimsaber/out
TARGET_TOOLS_PREFIX=prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/arm-linux-androideabi-
============================================

Let's see how it goes.

Thanks
[Galaxy S II Android Development] thunder45:
Sure! The ROM is good, but the boot/recovery doesn't seem be working. I have had a couple of building issues; apparently cm11 for i9100 doesn't build out of the box anymore. I have quickly fixed them so the ROM builds, but the boot and recovery didn't work right. So what did was the following:

1) Boot to recovery (TWRP in my case)

2) Backup (boot, data and system) current slimsaber rom

3) Wiped cache, dalvik, data and system (yes, system as well)

4) Flashed my cm11 build and a GAPPs (DO NOT REBOOT after flashing)

5) Open ODIN in my PC and connected the usb cable

6) Got back to HOME menu in TWRP

7) Rebooted to BOOTLOADER (yes, to LOADER)

8) Waited for ODIN to detect my phone

9) Select PDA check box with TWRP Kernel in tar format (kk-kernel-04-02-TWRP-TRIM-for ODIN.tar)

10) Hit start button in ODIN and waited it to reboot my device.

If I had the flashable ZIP of TWRP (does anybody has it?), I could probably just replace step 5 to 10 above for:

5) flash TWRP

6) Reboot

If you follow instructions up to 4, and then reboot you phone, you have two options:

1) Do the magic key combination (power+volume_down+home) to enter LOADER and the follow steps 8 onwards.

2) Simply let your phone to bootloop for a couple of minutes, and it will eventually boot to rom properly. Honestly, I don't know why, but it simply stops bootlooping on its own.

If you still didn't gave up on trying that highly experimental build, you can find all the files you need (including Odin, TWRP.tar and Samsung Drives, and of course the ROM) here CM11_UberTC4.8

Good luck

Make sure you back up your current SlimSaber!!
[Galaxy S II Android Development] j1gga84:
[MENTION=1228651]fusionjack[/MENTION] [MENTION=5103629]thunder45[/MENTION]

What about the flashable patch by [MENTION=1597520]Markox89[/MENTION] concerning the play services FCs?

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

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy S II Android Development] fusionjack:
i thought the build from thunder is solving play service fc, but the Skype issue still remains? i'm not sure what markox did with those libs, recompiling with other toolchain?
[Galaxy S II Android Development] officiallyme:
not sure, but the radio cleaner might be incompatible now. since i used it i cannot get my network to work properly anymore. signal keeps dropping. networks are not being found or cannot be registered. flashed ls8 and ms4. re-flashed radio cleaner a few times.

something got messed up
[Galaxy S II Android Development] kostelo:
Try flashing the stock rom through odin and start all over.

Sent from my GT-I9100
[Galaxy S II Android Development] j1gga84:
No, Skype still does not work, when I click on the camera or phone button screen gets blue and after that skype restarts so video/audio call is not possible.

[MENTION=5103629]thunder45[/MENTION]

What do you think, will it be possible to re-add optimisations with the play services fix or is the fix only possible without these optimisations?

regards
[Galaxy S II Android Development] thunder45:
All I did to "fix" play services FC`s was to disable some of the optmizations (mainly O3) and some memory optmizations. As a matter of fact, the changes I made to libcore (the Lolipop fix for play service FC), actually caused bootloops. I think I know what I did wrong, but I gave up on that and started investigating the skype issue.

In order to re-add the optmization, we should find the exact code that was causing the failure and then re-write it in a way that we could force GCC to compile it differently and generate a healthy assembly code. I`m a begginer in Android development, and at least for me it doesn`t sound like a simple task.

Also, after long hours I spent this weekend trying to fix and/or isolate the skype problem, I have started to think that we might have a major problem that maybe is not worth to fight against:

Over the weekend, I tried lots of possible solutions for the Skype issue:

- Build with no O3, no memory and no strict-aliasing optmization to TARGET-ARM

- Build with no O3, no memory and no strict-aliasing optmization to TARGET-Thumb

- Build with no O3, no memory and no strict-aliasing optmization to both TARGET-ARM and TARGET-Thumb

None of them caused skype to work. The problem is exactly how you described, and logcat is always the same (see details here).

As my previous investigation showed me, there is a mismatch between what Skype expects and what we have at libstagefright.so from SlimRom.

So I started to try to create some "Frankenstein" builds, combining Slim and CM:

- Re-packed my latest SlimSaber build, by replacing its libstagefright.so with the one from my CM11 build (where Skype works fine)

->RESULT: No boot

- Re-packed my latest SlimSaber build, by replacing all libstagefright_*.so with the ones from my CM11 build

->RESULT: No boot

- Tried to build slimsaber again from scratch, but replacing SlimSaber framework_av repository (which is from where libstagefright.so mainly comes from) with CyanogemMod's framework_av repository

->RESULT: Build fails. It depends on some framework_base repository changes that are not present in Slim

- Tried to build slimsaber again from scratch, but replacing both SlimSaber framework_av and _base repositories with CyanogemMod's repository

->RESULT: Build fails. It depends on libcore repository changes that are not present in Slim.

- Figured out that I would eventually bring the whole CM11 source

-> RESULT: Stop!

I did a quick compare between Slim and CM framework_av repository and there are about 10 thousand lines of difference.

We could potentially find what is different on the CameraProxy classes between CM and Slim, but that is probably also a very complex and long task, with a great chance to fall in some sort of "Dependency Hell", and would eventually need to bring tons of code from CM11.

Maybe it would be a goot time to follow SlimRom and join the forces on Lolipop.

Sorry if I sound frustating, but I have spend lot of hours on this skype issue already with no luck.

Regards