No, there is no problem with chromium in SlimLP. Yes, there are many games & apps that use the built in browser engine so using these can start building up the memory issues of chromium and start crashing system ui and other apps.
I'm not sure of the best thing to do at the moment. I could revert back to using classic webview but this would negate most of the benefits of building with display-caf in slimkat. Chromium brings much better app compatibility because apps running in kitkat expect the built in web engine to be chromium and crash if it's not. I will make another build with the fixes so far (stagefright, voip) and then continue to look for a fix for chromium.
Ah, yes, I had the browser problem before when working on slimkat caf. It's the black box problem in chromium. In the browser you often see black boxes covering portions of the screen (especially images) and in logcat you see chromium errors (It maybe non-power-of-2 and have incompatible texture filtering or is not 'texture complete') and ion/gralloc out of memory errors. As chromium consumes all of the available memory, it starts crashing parts of system ui too. I forgot about this problem in slimkat as is doesn't happen in slimlp.
No, not yet. I will copy in the latest patches from the frameworks_av github repo for CM11 to fix this. I will wait a few days for people to further test this rom then I will do a new build with the stagefright patches and any changes required for any other reported issues.
@Uliz Baseband 1040 sounds like the G330 rom. Are you installing the correct rom version? @Caras69 Video playback works but it is software decoding only. Hardware decoding does not work with display-caf just as in the SlimLP rom. @sm_94 There are a couple of changes for voip added to this rom made by srfarias. He has added another fix this morning for WhatsApp which will be included in the next build.
I have just uploaded a new test kernel to basketbuild: chil360-kernel-20150824-2112-slimlp.zip I have increased the memory available to surfaceflinger by 5mb. In About Phone you will now see Memory as 399mb instead of 404mb. This might help with the black screen problem - it's worth a try. Let me know if it makes any difference.
I am still here but unfortunately I haven't had much time to work on android recently. So, here's the situation... SlimLP There are a number of problems remaining with this ROM... Black Screen issue when coming out of sleep Hardware video decoding/encoding Unstable Wifi: Frequent connection drops Device reboots when transferring files over wifi Camera Issues: Sometimes get 'Cannot connect to camera' Photos & videos are very dark FM Radio Support - Tunes into channel but audio isn't routed to speaker/headphones The situation is that I just don't know how to fix these problems, I've tried but haven't made any progress on these. In the case of the hardware video encoding/decoding (OMX), I'm not sure if it's even possible to fix. Support for msm7x27a based devices was dropped some time ago which means that there's not much help available to fix these problems and all of the devs have moved on to newer devices. I will continue to build this rom whenever Slim publish new versions but I can't really see much progress being made on hardware support for this device unless other devs get involved to fix these problems. Slimkat (Display CAF) Due to the issues outlined above with SlimLP, I have been thinking that a new build of a display-caf based Slimkat would probably be the best choice ROM for every day use on our device. AOSP Mod is definitely the best choice for gaming but a Slimkat display-caf build (using chromium webview) would give the best application compatibility. So, I am going to start working on a new build of Slimkat 9 final using display-caf. I think the only thing that won't work will be the hardware video encoding/decoding which would mean higher battery use for video playback in software mode. I will publish it when it's done and we can see if any other issues arise.
From the reports of people here, raising the min cpureq to 480MHz and disabling MPDecision fixes the problem. I could add it into the rom and call it 'the fix' but it's not the ideal solution as raising the min cpufreq will drain the battery faster and battery life is already poor. For that reason, I created the flashable zip as an optional workaround.
Unfortunately, this is quite normal on our device. The problem is mainly due the media scanner. When it runs on boot, it take a lot of processor time performing it's initial scan and our phone is just not powerful enough to cope with getting through the setup wizard at the same time. If you boot the phone after install and don't touch it for 10-15mins (depends on how many media files you have on the device/sd card) you will find that the setup wizard is now a lot easier to complete.
I think the most recent build of SlimLP 5.0 I released is ok with Gapps. Slim stopped working on 5.0 when their 'infrastructure issues' started so there won't be any more 5.0 builds. As for SlimLP 5.1, Gapps seems ok in my development builds but I'm rot ready to release them yet.
I updated kgsl, msm_fb and ion to kk_2.7-stable and beyond in order to be able to build the rom with display-caf. The mega CAF update was done to bring the memory management in line with msm_fb and ion. This fixed the 'Error writing to swap device' issue but didn't fix the page alloc errors. The kernel is more stable with the CAF update but we need to find the cause of these black screens.
No, I haven't released any 5.1 builds yet and I'm not going to until Slim have got the rom into a decent state. Slim have not released any official builds for any of the devices that they officially support. That's because it's just not ready. If I released a build now, this forum would be filled up with complaints about things not working and missing features when there's nothing I can do to fix them. For example, at the moment if I receive an incoming call, after about 2 seconds the caller can't hear anything I say but I can hear the caller. I think the fix for this is in gerrit but hasn't been merged yet. This is just one example but there are more making the rom unusable in the current state so please be patient.