[ROM][5.1.1_r34][p6800/p6810](6April2016-Build1.8)SlimLP 5.1.1-.beta.0.15-UNOFFICIAL

p3dboard · Sep 24, 2015

philipnzw said:
Nice

New build for p6800 is uploading now. Should be there in the next 20 minutes

LeonardoD93 · Sep 24, 2015

Omni

p3dboard said:
I just tested Facebook Messenger with the davlik memory value set at 320m, and it uploaded a photo fine in my test, no crash. So it may be a memory limitation. SlimLP seems to be lighter on Ram, it may even be ok with 384m, but 320m seems to working ok for me. Next build, I'll increase the /system/build.prop Ram value to at least 320m, possibly 384m.

I use for 2 days Omni Rom and i must say i am amazed,how well it go,tested FB+Messenger,and it is like 80% faster then on Cyanogenmod,Carbon and Slim,but 1 thing,i tested today asphalt 8 just to se how it go with stronger games,and i must say there is just no way that i cann play it,it just lag,and dont responde,but that is not mather to me

,i dont play ho demanding games,because i know that my tab is not the best for it

p3dboard · Sep 24, 2015

LeonardoD93 said:
I use for 2 days Omni Rom and i must say i am amazed,how well it go,tested FB+Messenger,and it is like 80% faster then on Cyanogenmod,Carbon and Slim,but 1 thing,i tested today asphalt 8 just to se how it go with stronger games,and i must say there is just no way that i cann play it,it just lag,and dont responde,but that is not mather to me ,i dont play ho demanding games,because i know that my tab is not the best for it

The reason why Asphalt 8 is running so bad, is the default /system/etc/build.prop value for opengles in Daniels builds is set to opengles 3.0, but our tablets gpu only supports 2.0. Not many games use opengles 3, but Asphalt 8 does. So it downloads from the play store the wrong version for our tablet.

The right value for opengles 2 is, ro.opengles.version=131072, after you set that, you will need to reboot, then clear the playstore apps data so it refreshes it's value. Then you can download the right version of Asphalt 8 that will work.

sas_sas · Sep 25, 2015

Thanks for your efforts.

I attemted to test your rom on my P6800 but the last 24/09 release has an essensial problem.. Keyboard not appearing at all... It is obvious w/o keyboard no progress...

SM-T700 cihazımdan XDA Forums kullanılarak gönderildi

philipnzw · Sep 25, 2015

sas_sas said:
Thanks for your efforts.

I attemted to test your rom on my P6800 but the last 24/09 release has an essensial problem.. Keyboard not appearing at all... It is obvious w/o keyboard no progress...

SM-T700 cihazımdan XDA Forums kullanılarak gönderildi

Go settings input and languages
Turn of the physical keyboard input thingy
Its somewhere it there

p3dboard · Sep 25, 2015

sas_sas said:
Thanks for your efforts.

I attemted to test your rom on my P6800 but the last 24/09 release has an essensial problem.. Keyboard not appearing at all... It is obvious w/o keyboard no progress...

SM-T700 cihazımdan XDA Forums kullanılarak gönderildi

Yes, that's the next bug i am working on fixing, but as mentioned in my opening posts, there is a work around. You have to cancel any setup if you have Google play services installed. After go into language and input under settings and flip the hardware switch under current keyboard

I think i might have found some code to fix the problem at https://gerrit.omnirom.org/#/c/903/2

Edit: Looking over Cyanogenmod code, they have already implemented this fix, but SlimLP hasn't added it to their code base, so I have added it to the source code and am doing a compile now. The only thing I think I need to work out is if I need a true / false value, but hopefully this should fix it.

Edit: This is the code and files I am modifying and compiling now (notes added to my change log.txt which I'll upload with a new build if I find it fixes the problem)

Code:

FILE:/frameworks/base/services/core/java/com/android/server/wm/WindowManagerService.java
# add after this line -final DisplayManager mDisplayManager;

    private boolean mForceDisableHardwareKeyboard = false;

# add after mAnimator = new WindowAnimator(this);
        mForceDisableHardwareKeyboard = context.getResources().getBoolean(
                com.android.internal.R.bool.config_forceDisableHardwareKeyboard);

# add/modify - standard line boolean  boolean hardKeyboardAvailable = config.keyboard != Configuration.KEYBOARD_NOKEYS;

            // Determine whether a hard keyboard is available and enabled.
            boolean hardKeyboardAvailable = false;
            if (!mForceDisableHardwareKeyboard) {
                mHardKeyboardAvailable = config.keyboard != Configuration.KEYBOARD_NOKEYS;
            }

FILE:/frameworks/base/core/res/res/values/slim_symbols.xml
# Add this line just above <java-symbol type="bool" name="skip_radio_power_off_on_sim_refresh_reset" /> entry

<java-symbol type="bool" name="config_forceDisableHardwareKeyboard" />

FILE:/frameworks/base/core/res/res/values/config.xml
# Add this line after <integer name="config_toastDefaultGravity">0x00000051</integer>

<!-- Workaround for devices with broken keyboards -->
    <bool name="config_forceDisableHardwareKeyboard">false</bool>

Edit: This bit of code I don't believe fixes the error after my initial test. What it does do is hide the Hardware option from the language and input, which allows us to fix the problem, but it's probably in this same bit of code I need to add the fix / default value.

Edit: My testing has confirmed that this code only removes the hardware option, doesn't set it. But I might be able to use this bit of code to help me start to find the option. I just need to find where the Default Value of this toggle switch is set, and then adjust the default to be turned on, instead of off.

philipnzw · Sep 25, 2015

Does this build have rro layers support?
Installed the rro managers but it says plugin not supported
Feel like messing around with themes but seems like it could be super memory hungry

p3dboard · Sep 25, 2015

philipnzw said:
Does this build have rro layers support?
Installed the rro managers but it says plugin not supported
Feel like messing around with themes but seems like it could be super memory hungry

I haven't specifically added it to the SlimLP build, so it's probably not there. I can probably find out what needs to be included to add RRO layers, but I would say it will add to the memory overhead of the build, but not sure by how much.

p3dboard · Sep 27, 2015

philipnzw said:
Does this build have rro layers support?
Installed the rro managers but it says plugin not supported
Feel like messing around with themes but seems like it could be super memory hungry

I've done a little bit more research, and the current SlimLP rom's that have RRO layers, have cherry-picked extra code from http://xdaforums.com/android/apps-games/official-layers-bitsyko-apps-rro-t3012172

So to add Layers, I'll have to incorporate that. Once I get the keyboard and torch bugs sorted, I'll look at that.

Just found a github source https://github.com/SlimBit that might have all the RRO Layers bits added... anyway I'll look at this later.

curtislin · Sep 28, 2015

Test report 1.4

I flashed the new 1.4 rom.
Performance is excellent. There are 2 problems…
1. When boot new rom after wipe, during account login keyboard did not show up.
2. Wifi ap cannot be turned on due to error.

Thanks for great works!

p3dboard · Sep 28, 2015

curtislin said:
I flashed the new 1.4 rom.
Performance is excellent. There are 2 problems…
1. When boot new rom after wipe, during account login keyboard did not show up.
2. Wifi ap cannot be turned on due to error.

Thanks for great works!

Thanks for the feedback.
1. I am trying to work on fixing the keyboard at initial boot, the Samsung Dock driver is incorrectly reporting a physical keyboard is connected, so it doesn't show the touch keyboard - For the moment the work around is mentioned in my opening post - It's in a Pink colour.
2. I'll have to check to see if I have Daniel's latest code fixes, as he's just fixed the hotspot in his Omnirom build, but I wasn't sure if my last code sync got all his fixes. Thanks for the feedback.

Btw, if you are just upgrading from a previous build, you don't need to do a full wipe (but if you are coming from another rom you do). The System Patching also preserves the existing Google Play services, so you can just flash the main rom if you were on a previous build and then reboot.

curtislin · Sep 28, 2015

Thanks a lot. I am upgrading from slimkat 4.4.4 , if i didn't wipe i got an google play service stopped error. Is there ways to fix that?

p3dboard · Sep 28, 2015

curtislin said:
Thanks a lot. I am upgrading from slimkat 4.4.4 , if i didn't wipe i got an google play service stopped error. Is there ways to fix that?

Possibly a wipe of the Data, but I also had problems going from Slimkat 4.4.4 straight to 5.1.1. I found that in this scenario, it was best to do a full wipe, not just an upgrade.

Cluey · Sep 30, 2015

Looks like I should wait for 1.5 to be uploaded then.

I forgot about the keyboard not working on first boot and wasn't home at the time, I tried forcing a reset from the settings menu and it booted to TWRP but kept fading in and out the splash screen. That had me freaked out for a while, I couldn't work out how to power it off. In the end it just went flat!
Managed to sort out a USB drivers problem and have it working again, just testing some ROM's now to give to a friend to use.

p3dboard · Sep 30, 2015

Cluey said:
Looks like I should wait for 1.5 to be uploaded then.

I forgot about the keyboard not working on first boot and wasn't home at the time, I tried forcing a reset from the settings menu and it booted to TWRP but kept fading in and out the splash screen. That had me freaked out for a while, I couldn't work out how to power it off. In the end it just went flat!
Managed to sort out a USB drivers problem and have it working again, just testing some ROM's now to give to a friend to use.

Build 1.5 is available. I am still playing with optimal Davlik settings for better Ram management under various conditions / apps

Cluey · Sep 30, 2015

p3dboard said:
Build 1.5 is available. I am still playing with optimal Davlik settings for better Ram management under various conditions / apps

Cheers mate, I'll give it a crack.

I had various problems getting different ROMS to install, I kept getting a setup error crash but fully formatting it and starting from scratch seems to have sorted that out.
I've got OMNI on it currently, and as you said in one of your posts it is pretty smooth but it is lacking some features I'd like from Slim so I'll give your build after I've slept.

/me wonders how many non-locals he confused with the first line.

p3dboard · Sep 30, 2015

For those using my Rom, let me know if you think performance is better with the new Dalvik.vm values in build 1.5. I think it still might need some tweaking.

Edit: I think the values are a bit excessive for Davlik. I think increasing to dalvik.vm.heapgrowthlimit=64m, instead of dalvik.vm.heapgrowthlimit=100m, provides better responsiveness, but still enough for background apps like facebook (which uses around 60m of ram). For example, with the 64m value, opening a hyperlink from Gmail in Chrome works nicely, but at 100m, it's very laggy.

I think these values are better - I'll put a build 1.5.1 up soon, for those who want to try the different values (or you can manually set it yourself in Build.prop if your comfortable).
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=320m
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m

philipnzw · Oct 1, 2015

p3dboard said:
For those using my Rom, let me know if you think performance is better with the new Dalvik.vm values in build 1.5. I think it still might need some tweaking.

Edit: I think the values are a bit excessive for Davlik. I think increaseing to dalvik.vm.heapgrowthlimit=64m, instead of dalvik.vm.heapgrowthlimit=100m, provides better responsiveness, but still enough for background apps like facebook (which uses around 60m of ram). For example, with the 64m value, opening a hyperlink from Gmail in Chrome works nicely, but at 100m, it's very laggy.

I think these values are better - I'll put a build 1.5.1 up soon, for those who want to try the different values (or you can manually set it yourself in Build.prop if your comfortable).
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=320m
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m

New values made tablet slightly more responsive
YouTube and browser still crashes if used too much ram tho

Any idea if marshmallow is more ram friendly?

p3dboard · Oct 1, 2015

philipnzw said:
New values made tablet slightly more responsive
YouTube and browser still crashes if used too much ram tho

Any idea if marshmallow is more ram friendly?

Marshmallow is supposed to improve ram management, so we can only hope it will help our tablet. Android 4.4.4 is still the best performing for me, but Android 5.1.1 is becoming more stable with these slight adjustments. I don't think it will match 4.4.4, but Marshmallow could do if Google fixes the memory requirements and memory management.

[ROM][5.1.1_r34][p6800/p6810](6April2016-Build1.8)SlimLP 5.1.1-.beta.0.15-UNOFFICIAL

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts