yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] LeonardoD93:
yep

I have see this app but when i open it it just say the aplication has stopped to work,i have tryed 100x and still nothing,what should i do????
[Galaxy Tab 7.7 Android Development] uli-hh:
Then go to Settings/Performance/Processor and check the Maximum CPU frequency and change it to max!
[Galaxy Tab 7.7 Android Development] LeonardoD93:
.

I go to settings but cann not find Performance :/
[Galaxy Tab 7.7 Android Development] uli-hh:
did you activate developer options?
[Galaxy Tab 7.7 Android Development] LeonardoD93:
yep

Yep i have now activated this option,and i have set it to 1600 max,so is this all or i need more to do????
[Galaxy Tab 7.7 Android Development] uli-hh:
No, nothing more to do. Now you will see that the CPU will get hot quickly and battery is draining faster.
[Galaxy Tab 7.7 Android Development] LeonardoD93:
ok

I tested antutu score and it is 17500 but i have see on the begining of this threat that they mayked 20k 21k :),still need 2-3k more :/,but still on ICS i got 14500 :)
[Galaxy Tab 7.7 Android Development] uli-hh:
Do not look to much to Antutu scores. Check out the performance in daily use and if your apps and other stuff are running smooth it should be ok. Remember you're using a "mature" device not a brand new high end racer.

BTW I'm using a Galacy Tab 7 plus P6200 with the brand-new Carbon-LP rom from daniel_hk. I've Antutu 18900 at 1500MHz. So you should possibly try the Carbon-LP ROM for your device.
[Galaxy Tab 7.7 Android Development] LeonardoD93:
Thanks

I got till 19600 Score :D and the CPU stayed on 1600 i put GPU on 334 maybe will put on 400 but i dont play much games so i dont ned it :),and i adjusted RAM so for now 19600 score :)
[Galaxy Tab 7.7 Android Development] Trung Gs:
Mine was 21k :laugh:
[Galaxy Tab 7.7 Android Development] LeonardoD93:
mine

I got till 19900 but i didnt push the GPU till 400 or more,i stayed on 333MHz :)
[Galaxy Tab 7.7 Android Development] p3dboard:
Galaxy s2 phone just got official cm12.1 nightly builds, not sure if you can cherry pick any committs from the source code to help with our cm 12.1 build for the Galaxy tab 7.7
[Galaxy Tab 7.7 Android Development] LeonardoD93:
Hello i just gonna report my Exp for Lollipop 5.1.1 on my Samsung GT 7.7, i dont know how is with other but with my Tab it is horrible ,the System is so Laggin and you just cann not work with it,i have and OC the CPU to 1600MHz and GPU to 330MHz but still it is incredible LAG,especially whe there are 2 apps open,what would then happen when i opened more :/,sometimes i needed to shot down the Phone so i cann use it again,i dont know how on other tabs but this is what is going on with my,but i have then install the Kitkat 4.4.4 CM11,and the Exp is awesome,there is a little lag but irrelevant,and the system works werry nice,i cann use 2+ apps with no problem,there is just this thing in few apps with distort screen after rotation but like i say nothing big,so with my exp it is better to use Kitkat 4.4.4 then Lollipop 5.1.1,maybe they need still work on lollipop but if this is it then Good Luck :)
[Galaxy Tab 7.7 Android Development] rebski:
I am using 5.1.1_r3 CARBON-LP Unofficial and would agree with your observations. I shall hold on for the next update, my experience with OmniROM was more promising so it remains to be seen what that brings.

It is perfectly possible that our expectation of Lollipop for our device is overly ambitious. But my thanks to daniel_hk for providing us with the opportunity to find out.

The recommendation to 4..4.4 CM11 is appreciated, if 5.1.1 should fall short then at least I know what to revert to.
[Galaxy Tab 7.7 Android Development] p3dboard:
I think it is possible to have a smooth lollipop on our device based on the performance of cm 12.1 on my galaxy-s2 phone, 1gb ram, exynos 4210 processor. It's buttery smooth on the latest nightly builds, and chrome works great, no lags or lockups. I know there's a bit more resources due to the higher screen but I am hopeful of similar performance can be achieved one day

Edit: just a possible cause of the wifi bug where it can't remember passwords. A few in the Galaxy s2 thread have reported this same bug when playing around with the wifi region setting. I haven't tested it myself, but possibly not setting the code or setting it to a specific region may fix the bug
[Galaxy Tab 7.7 Android Development] p3dboard:
Hi Daniel, I noticed on your github page it says there was modifications to the cm12.1 branch two days ago. Is there a new build coming out soon?
[Galaxy Tab 7.7 Android Development] daniel_hk:
My hard drive crash. I was checking the sources in my github...:(

I need to reconfigure the system and sync the sources again. I don't think it would be ready soon... Hoping next weekend.
[Galaxy Tab 7.7 Android Development] philipnzw:
lastest build is quite fast and has little lag

will see if this holds up when i load up all the apps, so far so good
[Galaxy Tab 7.7 Android Development] Mrxyzl:
Just found a way for MDNIE setting

So today I look in to sys/class/mdnie and find out that the setting file is here. Compare with my S3 cm12.1 rom it is the same. So i try copy AdvancedDisplay.apk from my S3 to system/app/AdvancedDisplay. Reboot. Run the Apk by novalauncher/activities/AdvanceDisplay and it work!

So the problem is this rom missing this apk in the attachment .

Cheers!
[Galaxy Tab 7.7 Android Development] mr-bond:
latest build is fast and has a little lag
[Galaxy Tab 7.7 Android Development] p3dboard:
Latest build is working great, after one days testing, i think i can finally move to Android 5.1.1. Real Racing 3, my standard resource hungry app test, works perfectly fine in low detail graphics mode on the largest track,and i have all my apps installed. The last build, it would freeze up in the game menu.

I changed the video player to awesome player in debug, instead of nu player, as awesome seems to provide chrome with hw accelerated video playback, but nu player seems to stutter playing video in chrome.

Thanks for the latest build Daniel ☺
[Galaxy Tab 7.7 Android Development] edwin270:
I moved back to kitkat because I do share wifi with my devices at home. In previous versions turning on portable wifi sharing freezes the tab.

Can anyone, please, confirm if this is fixed in the new build?
[Galaxy Tab 7.7 Android Development] philipnzw:
It's kinda still laggy for me ,like when using browser + music player

I'm constantly going between this rom and 4.2.2 beanstalk

Could that be the problem?
[Galaxy Tab 7.7 Android Development] p3dboard:
Ram usage is higher in 5.1.1, either that or Ram management isn't as good as 4.4.4. I find that stock browser is better behaved than chrome. I am not sure, but possibly a tweaking of ram management values might help. In performance control I am playing around with the values,trying 48mb, 60mb, 72 mb, 84mb,96mb, 120mb. These are the values my cm12.1 galaxy s2 ROM uses (I was playing around with the preset options, but entered these manually - I would have to reboot to see if these are the same as stock values), but chrome seems better behaved with these at the moment.

Edit: You might get some idea's from this guy's post on optimizing the Nexus 7 for Lollipop (https://docs.google.com/document/d/1--5lhynOduiDDB61Zh1hECY6tYzJA852wGFbQa2pK1E/pub) as it also has 1Gb of RAM. He also speaks about Chrome, and suggests with 1Gb of RAM and lollipop, something like Firefox might be better. Because he's on a Nexus however he doesn't have the default CM 12.1 launcher, so I would stick with that launcher as you should have less Ram usage. Also I think the Stock Keyboard uses less ram then say Swift Key keyboard, but you can always play. I like swift key personally more then stock keyboard, but I think it uses a little bit more ram.

Another thing I am just trying is enabling a little bit of Zram (10%) - via Trickster Mod app in the play store, as this uses a little bit of ram as compressed Swap, so possibly gives us a little bit of extra Ram via compression.
[Galaxy Tab 7.7 Android Development] p3dboard:
Bug / Feedback: I just tested Microsoft Word, and on my Galaxy S2 phone with CM 12.1, the initial setup video plays fine, however on the Galaxy Tab 7.7 rom, the video can't playback gets a message - Error Video can't play (I tried both Awesome player and Nuplayer). Also I tested another game - Asphalt 8 - and the game rendering is not working properly, I am just about to test it also on my Galaxy S2 phone to see if it renders fine, possibly it's detecting a wrong OpenGL version (missing features?). Anyway, I'll see if it works fine on my S2 as it's very similar hardware / gpu / cpu. Daniel might be able to pull something from the CM 12.1 commits for the Official CM 12.1 rom for the S2 to fix these bugs.

Edit: Just loaded it on my Galaxy S2 phone with CM 12.1 and Asphalt 8 works fine, all graphics are readable. So its just a bug on the Galaxy Tab 7.7 build of CM12.1.
[Galaxy Tab 7.7 Android Development] Mrxyzl:
Bug report?

Low volume sound cut off when listen to music with ambient/ natural sound by headphone.

Step to reproduce

1. Plugin headphone

2. Set volume to step 1 or 2

3. Play this song: http://m.youtube.com/watch?v=FdD6RMICpfg

4. You will hear the fade out cut off.

I've test with cm12. 1 rom and omni 4.4 rom which is still the same result. So i think it is kernel related problem.

This problem has been reported here https://code.google.com/p/android/issues/detail?id=35861#c77

And here is a kernel that seem to fix this problem on S2

https://github.com/gustavoss/androi...mmit/1509ea20c80859252e533d7eb3522da540364f8c
[Galaxy Tab 7.7 Android Development] p3dboard:
I've just made a modification to the build.prop in /system, based on some settings on my Galaxy s2's build.prop and the tablet seems to be more responsive now.

davilk.vm.heapstartsize=5m

davlik.vm.heapgrowthlimit=48m

davlik.vm.heapsize=48m

davlik.vm.heapsize=128m

davlik.vm.heapmaxfree=2m

All the other davlik values were the same. Now for example. Real Racing 3, going back to the Launcher, would have a fair amount of lag before these values, now it seems to go back fairly quickly, without the lag. Needs a bit more testing, but it looks promising.

Edit : i think that the opengl es version might also be wrong, it's set to 196609 by default, but from what i read opengl es 2.0 is 131072.

#196609 - opengl es 3.0

ro.opengles.version=131072
[Galaxy Tab 7.7 Android Development] TrashX:
Hi, shouldn't these settings be ignored due to CM12+ uses ART by default instead of Dalvik VM?
[Galaxy Tab 7.7 Android Development] p3dboard:
I would have thought so, but maybe ART still uses some of these for some memory values for apps.

I have also found that adding a 300mb zram swap helps in apps using large amounts of ram. I modified the script to drop it to close to 300mb instead of 378mb, put it in a file in /system/etc/init.d and set permission to rwxrwxrwx. I am still playing with zram, as it can slow things down because of the compressing / decompressing, so i am not 100% sure that zram is the best option. I know that my wife's lg g pad 8.3 which has 2gb ram also has a 400mb zram partition in memory for its lollipop rom, so that manufacturer has enabled it.

#!/system/bin/sh

#

######################

# script made by dheeraj (dhlalit11)@xda-developers.com

######################

#

#

# resetting zram

echo 1 > /sys/block/zram0/reset

#

# setting zram size to 378 mb

echo 310286400 > /sys/block/zram0/disksize

#

# making zram swapable

mkswap /dev/block/zram0

#

# starting swap on zram

swapon /dev/block/zram0

#

# setting low memory killer parameters according to total memory

#echo "700,1200,20500,20600,20600,25800" > /sys/module/lowmemorykiller/parameters/minfree

#

# setting swappiness to 100

#echo 100 > /proc/sys/vm/swappiness

#echo 100 > /data/local/devil/swappiness

#

# done

#

######################

# script made by dheeraj (dhlalit11)@xda-developers.com

######################

---------- Post added at 09:59 PM ---------- Previous post was at 09:50 PM ----------

Just looking at this site http://pundiramit.blogspot.com.au/2011/08/android-and-opengl-es-profiles.html there maybe a second location that needs the value fixed

This property can be directly put in /system/build.prop file as it is or can be defined in Vendor specific Board Config files (e.g. device/vendor_name/target/target.mk file) as follows:

PRODUCT_PROPERTY_OVERRIDES+=\

ro.opengles.version = 131072
[Galaxy Tab 7.7 Android Development] p3dboard:
I just checked Daniel's github code, on line 169 of the smdk4210-tab device tree, in device.mk, he has the Opengl Es 3.0 value, instead of Ogengl Es 2.0, so to fix this (which i think will fix Asphalt 8's graphics issue) we will have to wait for Daniel to do a recompile of the code
[Galaxy Tab 7.7 Android Development] p3dboard:
Just trying some different values after checking the Android 4.4.4 slimkat rom settings, i think this makes chrome a bit more responsive, as compared to limiting to 128m. Real Racing 3 performance is still good, the launcher redraws fine without the lag

dalvik.vm.heapstartsize=8m

#80m

dalvik.vm.heapgrowthlimit=64m

#384m

dalvik.vm.heapsize=256m

dalvik.vm.heaptargetutilization=0.75

#512k

dalvik.vm.heapminfree=2m

dalvik.vm.heapmaxfree=8m

Comment

Heapsize of 128,192,256 all seem good so far, 320 might also be ok, i think 384 for lollipop is probably the issue, as it doesn't quite have the same amount of free ram as kitkat had.
[Galaxy Tab 7.7 Android Development] philipnzw:
How do I apply these build prop changes?

And also is poweramp music player working properly on slimkat for you? Songs on sd card seem to stop playing randomly for me
[Galaxy Tab 7.7 Android Development] p3dboard:
I haven't tested poweramp, but i'll test it out. I've gone back to 192m for my Heapsize as it feels the best to me. To modify build.prop, i use Es Explorer, and enable Root Access in the app. After that you need to choose in its root settings to enable read/write for /system. Then you can go to /system and edit build.prop, you can open it as a text file and use its editor to modify the values.

I would probably just drop the max heapsize down from 384m to 192m and leave everything else as default. Then save and reboot for it to take effect. Make sure you have a backup copy of the rom in a zip file incase you do something wrong, you can always flash back to default
[Galaxy Tab 7.7 Android Development] Lt.col.johncross:
undo enable read/write after changes before reboot

in my experience it has caused boot failures on the sch i815 if you don't change the permissions back before reboot.
[Galaxy Tab 7.7 Android Development] p3dboard:
Yes, permission values are important, the build.prop should have rw r r permission, which you can set / check using the properties option in es explorer. But if you just simply edit the file in es explorer it doesn't normally change the permissions. If you copy over a replacement file that is normally when i find permissions change. Thanks for pointing that out John.
[Galaxy Tab 7.7 Android Development] philipnzw:
Just did the build prop changes ,apps seem to install as fast as in KitKat ROMs

Recents panel also seems to be a tad quicker

Interesting
[Galaxy Tab 7.7 Android Development] philipnzw:
60fps YouTube, finally
[Galaxy Tab 7.7 Android Development] p3dboard:
Did you do anything special to enable 720p60 (60fps)? I find that in youtube, mostly it only offers me 480p, sometimes it offers 720p (I am assuming it must be to do with the video format?)
[Galaxy Tab 7.7 Android Development] philipnzw:
No ,don't remember doing anything to get 60fps,it just appeared suddenly

Maybe something in the YouTube settings or perhaps the nu player thingy in developers options

Poweramp works properly on 4.4.4 roms if your sdcard is exfat

Also,could the buildprop settings for note 4 in portal help us with ram management?
[Galaxy Tab 7.7 Android Development] p3dboard:
I found a new bug, when trying to send a file via Es explorer from the galaxy tab to another device running es explorer, the whole os crashes and reboots. Not sure if it's a wifi bug. I might flash the last build to see if it's a bug with the new wifi driver.

Edit: i tested a bit more, receiving files in the app is not an issue, it's only sending files

Edit: just tested Latest carbon rom, same issue. My Galaxy s2 cm 12.1 rom doesn't have the issue, so i don't think its the app, but just our galaxy tab rom builds on lollipop
[Galaxy Tab 7.7 Android Development] p3dboard:
When you say note 4, do you mean the note 4 phone? Or a note somewhere in a comment?

If the note 4, we could look at its settings, but i know that the defaults of the rom are ok on devices with 2gb of ram like my wife's lg g pad 8.3. So we would probably want to look at devices with 1gb of ram to get more optimal settings. The note 4 phone i believe has 3gb of ram
[Galaxy Tab 7.7 Android Development] philipnzw:
The phone

Hrmm yea should use ur s2 then

Hope Android M has better ram management
[Galaxy Tab 7.7 Android Development] p3dboard:
These i feel are the best values so far, basically the s2 values with a slightly larger heapsize

dalvik.vm.heapstartsize=5m

dalvik.vm.heapgrowthlimit=48m

dalvik.vm.heapsize=192m

dalvik.vm.heaptargetutilization=0.75

dalvik.vm.heapminfree=512k

dalvik.vm.heapmaxfree=2m
[Galaxy Tab 7.7 Android Development] Cluey:
That certainly makes a difference [MENTION=5495967]p3dboard[/MENTION] but it's still not exactly snappy.

Any ideas why it is slow [MENTION=4948627]daniel_hk[/MENTION]?

I don't remember it being this slow but I was without it for a while as mine finally died the third time it came off my bicycle mount. :(

I scored a replacement quite cheaply and it came with CM 4.4.2 I think, I put Carbon 5.1 on it as I didn't think much of the CM on it at the time and, of the custom ROM I'd tried before breaking mine, I linked the 4.4.4 Carbon ROM the most.

I might try the original official 4.0.3 again to see how it runs as I don't remember it being terrible.

[MENTION=4948627]daniel_hk[/MENTION] is there a reason we're still on a 3.0 kernel and not a 3.4 one?

I'm guessing it's the driver support missing but was just wondering if there's something else?
[Galaxy Tab 7.7 Android Development] daniel_hk:
May be its time to re-format the internal storage (data, sdcard, etc..)

For the kernel, I've have mentioned a few times. I had tried. The main reason is the blobs provided by the chip manufacturer.

The most lethal one is the Mali-400 blob which can only run on 3.0.x (buffer memory allocation, power management, etc. can only work for 3.0).

The only long shot might be getting one from a newer chip (eg. Mali-450) but I couldn't find one yet. :rolleyes:
[Galaxy Tab 7.7 Android Development] Cluey:
So yes it's a driver thing.

Samsung really dropped the ball on that but I guess they don't care given their market position.

I reformatted everything last time I installed a ROM, I had been wondering if it was a NAND write slow down. I remember when SSD started becoming affordable there was a lot of talk about Windows XP not being able to use them because it didn't have Trim so you needed to run Windows 7.

There were also special tools for SSD drives, secure erase sounds right but I'm going from memory at 3:20am.

Is there such a thing for internal memories on phones/tablets?
[Galaxy Tab 7.7 Android Development] daniel_hk:
There is a tool FSTrim in Linux (and an apk for Android). Starting from Kitkat, fstrim run automatically on every boot.

Our device doesn't have a real internal sdcard, it is part of the huge /data partition. Fragmentation always slow down performance. It would be better reformating the everything after a period of time. Or at least, wipe the Dalvik cache.

Good luck!
[Galaxy Tab 7.7 Android Development] yurius:
Is there any troubles with gps in latest build? Can't find any sat with different software on p6800.
[Galaxy Tab 7.7 Android Development] p3dboard:
I just tested the latest omnirom on my p6810 and also can't get any gps locks. Wifi location is working, but no satellites. So it looks like it's an issue in the latest builds
[Galaxy Tab 7.7 Android Development] uli-hh:
Same issue on my p6200:(
[Galaxy Tab 7.7 Android Development] fastguy:
Hi guys I had a p6800 laying down in my mother in laws home and decided to flash this goodie on it. It went fine, but everything is very laggy compared to my note 3. I know note 3 is a newer device but is it really supposed to be so much laggy? Opening apps and even clicking items on the screen is laggy.

I suspected nand issue did TRIM on it, seems to improve a bit bit still laggy.

For example, opening Firefox takes a few seconds and home button from Firefox also takes a few seconds to show me home screen.

My Androbench4 scores are:

Sq Rd 28.32mb/s

Sq we 13 mb/s

Rnd Rd 1225 iops

Rnd rw 82 iops

Do you see similar values? Or is the nand bady messed up and it's time to say bye bye to the tablet? Any way to bring it back to life?
[Galaxy Tab 7.7 Android Development] p3dboard:
At the moment, Omnirom is the fastest / least amount of Lag of the lollipop Rom's. That said the Android 4.4.4 rom's run fantastic on the device. I know that if you install Omnirom build, set the Animation speed to 1.0 (it's defaulted on 2.0 for my P6810), and I find adjusting the /system/build.prop entry davlik.vm.heapsize=320m (default is 384m) it's not to bad, but I still get lags at times. Android 5.1.1 runs great on my Galaxy s2 of a similar time frame. Not 100% sure what the underlying issues still are (I think its Memory Management / swapping when memory is getting full), but test out Android 4.4.4 (try slimrom or carbon rom) to see how the device can perform. I'm trying to set up my own Build environment at the moment, so I can play with building / modifying some Rom settings.... but Daniel is doing a great job on making builds for us.... it's just trying to figure out what is the issue....

---------- Post added at 05:10 AM ---------- Previous post was at 04:28 AM ----------

I just tested gps on the latest carbon rom build and it's working fine. Give Daniels new build a try.
[Galaxy Tab 7.7 Android Development] fastguy:
Thanks for the advice. I've glanced to many sites and concluded that the issue is because the kernels disable TRIM support on our nand controller. The controller I have on my P6800 is a bad one according to Brick bug testers in play store. The resolution to this problem in recent kernels (as submitted to Google by Samsung) is to disable secure_erase capability of the kernel. This may also explain why I always get 11gb trimmed whenever I run the trim utility.

Of course all of these are assumptions.

So without trim support in the kernel, I decided to give a try to writing zero's with dd in twrp (dd if=/dev/zero of=/dev/block/mmcblk0p10) to data (p10), cache (p7) and system (p9).

Then I setup Slimkat 4.4 as you suggested, and it's now running much better.

I did the same androbench4 on Slimkat but no change in values compared to 5.1.1. Anyway the system feels much better now.