yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] joegreat:
Hi,

Same result: Overclocking simple does not work with the latest ROM version. :(

You can set the higher frequency, but the CPU never goes above 1 GHz!

I check overclocking with Omni ROM 5.1: And? Works out of the box...

So, my device is OK, but no overclocking with this ROM.

By the way: I like Kernel Adiutor (check spelling!) a lot - will keep it!

With kind regards

Joe :cool:
[Galaxy Tab 10.1 Android Development] Prowler665:
Overclocking definitely works...

The screenshots are for aosp-5.1.0-p4-20150403 / OC 1,4 GHz / interactive / bfq

Did you try a clean install after removing DeviceControl? This little piece of code was causing a lot of grief on this tab in the past...

Regards
[Galaxy Tab 10.1 Android Development] decatf:
Please send me kernel logs from your device. See post #2 under Problem Reporting Steps on how to do so.
[Galaxy Tab 10.1 Android Development] Dannyboy_01:
overclock

Like Prowler665, I can also confirm over clock working on latest aosp-5.1.0-p4wifi-20150403 rom, I have mine over clocked with no frills CPU control app to run at 1.4Ghz all the time, confirmed this with CPUZ app.

Device control app defo FUBAR's this ROM, again as Prowler665 suggests clean install a MUST if you have installed it, uninstalling it is not enough in this case, try that and see how you go.:good:
[Galaxy Tab 10.1 Android Development] Finefeather:
I have the 3G tab.

I installed the latest ROM 20150403 with the recommended recovery, gapps and latest SuperSU.

When the setup starts and you need to connect to a wifi it says checking connection, and never comes out of this process. So I re-installed all and tried again, still the same. I then re-installed and skipped the entire setup and connected later which worked fine.

The keyboard keeps stopping so I installed Swiftkey Keyboard and all is great, no stopping...nice keyboard.

I also had stops in Gallery but it just carries on and has not happened again.

Otherwise this ROM combo is working nicely for me.

I put a game on it which was really slow and jerky in the stock rom as well as the CM10.2 rom, an obvious RAM problem, but with this rom it is very smooth. This could be either better RAM usage or less junk from gapps.

I then changed the lcd density from 160 to 180 in build.prop and boy it looks great for me.

The only thing that happens is the home screen buttons move to down the right hand edge and you can move the launcher icons BUT you cant move the app drawer 6 dot dice icon...it stays in the middle right side of the screen.

This does not look too bad. I have not tried to go bigger than 180 but will try 200 some time.

So thanks for a great job so far. Will keep this running for a while and report any other problems I encounter.

Will install new roms as they come available.
[Galaxy Tab 10.1 Android Development] joegreat:
Hi,

As you can see from my posting above, I have switched ROM (with clean install) and witched back (with clean install - even formatted the SD-card partition).

And on Omni ROM 5.1 it works like a charm, but not on this ROM - which is on all other means by far better... :good:

As outlined in one of my previous postings, it looks like there are not voltage information for the higher frequencies... :confused:

With kind regards

Joe :cool:
[Galaxy Tab 10.1 Android Development] Finefeather:
Yes I have the same problem. When you press the 'mount USB storage' option in settings>storage a tiny usb icon appears in the top left hand corner, but then disappears...so it tries but it does not complete the process.
[Galaxy Tab 10.1 Android Development] fabduhameau:
Video are working well with kitkat. Does kitkat use old drivers that cannot be used in lollipop?

I've done a bench from kitkat and lollipop ROM here : http://xdaforums.com/galaxy-tab-8-9/general/best-rom-kernel-casual-net-video-small-t3076901

it's a bench on p7310 but the jolinnard's ROM come mainly from decatf's ROM

last 5.1 ROM is amazing in bench, except for videos of course
[Galaxy Tab 10.1 Android Development] Lucas Kado:
I had the same issue. Something in the automount code seems to be wrong.

I installed chainfire's StickMount and problem solved, but a system notification icon remains when you remove the USB (have to reboot the tablet yet, maybe that fixes it).

Anyway, nothing you can't deal with.... ;)
[Galaxy Tab 10.1 Android Development] Prowler665:
Since development for the tegra2 ended a long time ago, AFAIK the driver-blobs are literally the same since ICS (?). Apart from the fact that the OP switched to video codecs from Toradex since these seem to be the most "recent" ones. The "problem" is that android development moved on and since the blobs are closed source there is no way but reverse engineering to get the drivers on par with the evolution of android. There have been lots of changes under the hood inbetween KK and LP and since there is no way to change the blobs, it's getting harder and harder to keep our beloved tab alive at all - not to speak of any improvement.

This is usually done by patching the new code to use the old drivers directly or via wrappers. It's only due to the enormous effort the OP is putting into this ancient device that we can enjoy this amazing ROM ;)

Regards
[Galaxy Tab 10.1 Android Development] SearchEngine:
Hands-on?

Hi guys,can someone post a small hands-on video to see how fast it goes with lollipop??

I installed a couple of days ago but it's not smooth at all,so i reverted back
[Galaxy Tab 10.1 Android Development] Olivier V:
Try the 3/20 release and overclock it to 1400 mhz. Runs very smooth on mine..
[Galaxy Tab 10.1 Android Development] ENRIQUEMM:
reset?

Running rec Screenrecorder first made me a quick restart slow as 1 minute android logo . Turned to run and this time reset more than 10 minutes STAYING hung logo android, hard reset by pressing on several seconds , starts launching applications are installed apps though he had. Deputy syslog although this latter taken after startup. Everything has happened to 1.4 CFQ . When starting asking me superuser permission for all apps. No happened ?! Sorry for my bad english google traductor...
[Galaxy Tab 10.1 Android Development] bradley_099:
ROM HELP

I installed the aosp 5.1 ROM and forgot to install the gapps, and theres no "Google Play Service" which means I can't use any google application, I also tried to install an apk version of google play service for multiple times and different versions but a pop up keeps on showing "unfortunately google play services hast stopped" so I uninstall it, I can't even root my tab it freezes every time I connect it into a rooting software I also tried variety of rooting software (Kingo root & mobogenie root) still doesn't work means I can't also do clockworkmod recovery on ROM manager even the pre installed android recovery doesn't see to be working anymore, I'm using gt7500 (p4) still unroofed and still on the unofficial aosp ROM (5.1), please help I love the ROM, oh yeah I also have some problems with the ROM *Bluetooth seems like not working and camera is slower and panorama don't work but I still like how the is work
[Galaxy Tab 10.1 Android Development] jdogzilla:
Do CM12 themes work with this ROM? If yes how do I enable them?
[Galaxy Tab 10.1 Android Development] fabduhameau:
Thanks for your answer

I have 2 (noob) questions more:

1) 3D and 2D are working quite well. So i suppose that lollipop is quite optimized for tegra 2. So why should a system that has worked well on 2D/3D no longer work on video. Is there a specific issue on video

2)Does this kind of kernel android-tegra-flounder-3.10-lollipop-release be compatible with tegra t20 or works only with latest tegra gpu?
[Galaxy Tab 10.1 Android Development] Finefeather:
Right you are! ....just imagine what he would have had to do to get this working ;)

[IMG="old phone"]http://freepages.rootsweb.ancestry.com/~bradytrilogy/memories/images/bibliography/antique-telephone.jpg[/IMG]
[Galaxy Tab 10.1 Android Development] Prowler665:
Well, if you refere to issues with video I guess you actually refere to youtube since playing videos, either locally or over the network, using MX-player for instance works quite well - althou in 720p it highly depends on the footage (codecs, bitrate etc.). Bear in mind that the youtube-app evolved quite a bit and may behave differently on KK and LP due to different resources provided. For quite some time disabeling NuPlayer in the developers-options fixed some of the bugs, but I didn't try it lately.

Using different cpu covernors and/or I/O-shedulers also influences the video performance. You're free to start an empiric test ;)

When refering to a "driver" on a Linux OS you usually talk about a kernel-module. The official kernel-tree only provides modules that a) provide the source-code under an open-source-license and are b) approved by the (kernel)-developers. The same goes (mostly) for the android kernel-tree you refered to.

The tegra2 is a Cortex A9 SoC (System on Chip) and while a lot of code is part of the kernel-tree, AFAIK the relevant modules we need still are only provided as binary-blobs by the manufacturer.

Regards
[Galaxy Tab 10.1 Android Development] fabduhameau:
Thank you for your try to make me less noob ;). You're answer is very clear.

I had the same problems when i was building linux kernels (1.3) with nvidia hardware 20 years ago! Nothing changes!

best regards
[Galaxy Tab 10.1 Android Development] hondong:
I use Stickmount from Chainfire. (https://play.google.com/store/apps/details?id=eu.chainfire.stickmount)

This works fine.
[Galaxy Tab 10.1 Android Development] decatf:
No.

There is no newer kernel version that will work for this device. Samsung made a lot of custom modifications that make it impossible* for us to use any other kernel. Most Android device kernels are tailor made for a specific device. You cannot take a kernel from another Tegra2 device and use it on this one.

*Not impossible but very hard. Like pay people a regular salary to work on it full time kind of hard. Might as well buy a new device for everyone with that kind of cash.

A new kernel won't solve laggy video playback anyways. The problem is the parts of the drivers outside of the kernel and the video codecs. Other things are just trying to dance around the issue without fixing it where the problem is. Only Nvidia can fix the real problem. They won't because this device is no longer supported.

I have tried backporting the kernel video drivers before. There is very little new work for the Tegra2 kernel drivers beyond what we already have. It's buggy and there's no performance improvement. If I post it people will just complain even more.

Install the gapps package in the first post. It can be installed after the ROM has been installed. Use TWRP 2.8.6.0.

Use Chainfires SuperSU. for root.
[Galaxy Tab 10.1 Android Development] decatf:
Build 20150414

aosp-5.1.0-p4wifi-20150414.zip

aosp-5.1.0-p4-20150414.zip

]aosp-5.1.0-p4tmo-20150414.zip

For testing: ICS AudioWrapper

This code wraps around the ICS audio HAL so that it is compatible with Lollipop. The wrapper was written by Thomas Wendt https://github.com/thoemy/android-audio-wrapper

What is an audio HAL. The hardware abstraction layer (HAL) is the glue code between the audio driver and the operating system.

The ICS audio HAL was previously used directly on Lollipop frameworks requiring a lot of hacks for Lollipop to support the old audio HAL. By using a wrapper the hacks are not needed. The wrapper provides a compatibility layer between the ICS binary and Lollipop frameworks.

The Lollipop audio HAL was an attempt to create an open source version of the audio HAL. It is not a 100% complete replication of all the original audio functionality. By using the wrapper we don't have to try to replicate the audio functionality of the ICS audio HAL. We also don't have to use so many hacks in the frameworks.

Bluetooth audio should work. HDMI and dock audio need to be tested.

p75xx-ICS_AudioWrapper-20150414.zip​

Changes:

Update CMFileManager
Update telephony frameworks
Switch to CyanogenMod 12.1 audio/video frameworks

7eab128 libc: Restore cortex-a9 to aosp
6a71b00 libc: tegra2: A9 optimized memcmp and memcpy
188a198 Fix memchr overflow.
6b49e30 Make libaudio optional
4c1cf12 Add AudioWrappers by Thomas Wendt
ea20ddc Revert "PowerHAL: Set interactive go_hispeed_load to 95"

kernel:

37a1489 defconfig: bring up p4tmo and p4lte
23538be ARM: 7467/1: mutex: use generic xchg-based implementation for ARMv6+
1e8b290 ARM: mutex: use generic atomic_dec-based implementation for ARMv6+
27c2485 ARM: 7587/1: implement optimized percpu variable access
eed8b4d Revert "cpufreq: interactive: Add get_cpu_idle_time() to for 3.1 compatibility"
450ce14 Revert "cpufreq: interactive: Update from hammerhead kernel"
062577f Revert "android: lowmemorykiller: squash task adj rbtree optimization from Motorola"
c6c5386 Revert "introduce for_each_thread() to replace the buggy while_each_thread()"
c77524c cpufreq: tegra2 voltage control: Improve undervolt table
a1c95e6 arm: tegra: p75xx: Apply OC voltages only to speedo 1 process 0 and 1 chips

Additional Notes:

Some users have a different revision of the Tegra2 chip. This is why overclocking was not working. It should be fixed for those users.

I've gone back to using CM-12 audio/video frameworks because it has moved out of staging repos.

FFMPEG codecs are included. These are software codecs. They are not hardware accelerated. They are slow and not a replacement for the Nvidia codecs. It is meant to supplement the available codecs.
[Galaxy Tab 10.1 Android Development] Olivier V:
Initial impressions after dirty flashing it... Awesome! Very smooth (did oc it to 1500) and you finally did it. I played my reference 720p YouTube video and it never stuttered. Smooth all the way. Will try how it behaves on 1400mhz next. Thanks a million for providing us with your ROM!

Sent from my p4wifi
[Galaxy Tab 10.1 Android Development] sflesch:
Is there an easy way to tell which chip we have?
[Galaxy Tab 10.1 Android Development] decatf:
Look for these lines in the kernel log.

<6>[ 0.000000] Tegra SKU: 8 Rev: A04[COLOR="Red"] CPU Process: 1[/COLOR] Core Process: 2 [COLOR="Red"]Speedo ID: 1[/COLOR]
<6>[ 0.000000] Tegra Revision: A04 prime SKU: 0x8 CPU Process: 1 Core Process: 2

The parts in red are the relevant identifiers. Most people seem to have the above (CPU Process: 1 and Speedo ID: 1)

Basically if you have been able to OC in the last few builds then there is no problem for you. Only one user has reported problems due to having a different CPU revision.

The difference in chips is the voltage that they run at. When I re-refactored some of the overclocks a few builds ago I did not take into consideration the other revisions properly. The CPU Process 0 runs at higher voltages. The consecutive process number run at lower voltages. For example the CPU Process 0 chip runs at 1025millivolts at 1Ghz. The CPU Process 1 chip runs at 1000millivolts at 1GHz.

If you have a CPU Process 3 chip consider yourself lucky! I've searched all the system logs I've received in the past and none of those has CPU Process 2 or 3.
[Galaxy Tab 10.1 Android Development] Pepe.II:
AOSP is updated to LMY47O. Please, can you make new build?
[Galaxy Tab 10.1 Android Development] Lucas Kado:
Two issues (maybe just one)

I've a p4 running a fresh install of version 20150320 (full wipe) and p75xx-gapps-L-3-17-15.zip gapps.

When the tablet is idle and it losts WiFi connection, it doesn't reconnect again. I've a SIM inserted but 3g data is not enabled. I'm at home, connected to my WiFi, and everything is ok. Then I go to work and it doesn't connect to the WiFi there until I turn the screen on. At that moment it connects and receives all the push notifications. It's the same if I disable the WiFi of my router for a moment and then turn it on: the tablet remains unconnected until I turn the screen on. Feature or bug?

I can't get swipe gesture to work on the stock AOSP keyboard. Could it be related to this?
[Galaxy Tab 10.1 Android Development] honhan0904:
Download the newest build

And i think that a bug

I never get that problem
[Galaxy Tab 10.1 Android Development] twa_priv:
Hello decatf,

I finally took my p4wifi out of the drawer it was hiding the last few months and installed your AOSP Lollipop ROM. Great work! Thanks and congrats.
[Galaxy Tab 10.1 Android Development] jeepnutz:
Dirty flashed latest build with ICS audio HAL . Netflix wasn't working on previous build. But it is now
[Galaxy Tab 10.1 Android Development] honhan0904:
Wow long time no see

Could u bring cm12 theme to this aosp rom?
[Galaxy Tab 10.1 Android Development] dihoc:
Mine got stuck at Android logo forever after rebooting from 04142015 rom. I did a dirty flash. Will try a clean install to see.
[Galaxy Tab 10.1 Android Development] decatf:
There is another way to watch 720p Youtube video. You can share videos in the Youtube app. One option is to send it to the BSPlayer app.

This app appears to be capable of playing the videos in HD. You must first configure BSPlayer. Set the default Youtube resolution to 720p. Set the decoding options to drop frames to keep audio and video synchronized. Both of these options are available in the free version of the app.

- Preferences > Network/Streaming > Preferred YouTube quality > 720p

- Preferences > Playback Preferences > Video decoding options (HW mode) > Drop frames if decoder can't keep up

Credits to [MENTION=3271153]Network_Pro[/MENTION] for telling me that you can share Youtube videos to BSPlayer.

So it seems the problem might be in the video player implementations and not the codecs. I have a suspicion that it's due to dynamic streaming implementations. This was not as common back in the ICS days. So all the new dynamic streaming methods that apps are starting to use are not working well with the old ICS video blobs that we are stuck with.

There's not much that can be done for apps that use their own video player modules. In Lollipop the default built video player was switched from AwesomePlayer to Nuplayer. I will switch the default back to AwesomePlayer in the next build. I know this fixes the video benchmark in PCMark since it uses the built in video player. You can set AwesomePlayer as the default in Development Settings.

It's crashing the in proprietary graphics libraries. It's not likely to be fixed.

Swipe gestures won't work with stock keyboard. The gesture detection code is proprietary Google code. It's not working with this tablet.

Thanks! Most of the device repos were forked from yours. :)
[Galaxy Tab 10.1 Android Development] dihoc:
After a clean flash, my p4wifi has run very smoothly with 04142015 rom. Thanks, [MENTION=4404851]decatf[/MENTION]
[Galaxy Tab 10.1 Android Development] enriquevagu:
Thank you so much for the image. I flashed the most recent version aosp-5.1.0-p4wifi-20150403.zip and is running smooth. However, I believe that a couple of details in the first post of the thread are some confusing, and clarifying them could help others:

There are references to AOSP 5.0.x and 5.1.0, but at the moment there are only images of 5.1.0 (the previous 5.0.x images have been removed). The explanations on how to update from 5.0 and the google apps for 5.0 could be removed now (or, at lest, indicate that they are left there for a former ROM version), since they can be confusing ("do I need to install a 5.0.x version first?").

TWRP 2.8.5 or newer is recommended to install the image, but this recovery image cannot be installed from Odin (it doesn't work, the screen remains black) and there are no further instructions on how to do that. I initially installed the ROM from ClockWorkMod but for some reason it gave multiple errors (it was an older ROM, though). After some search I found that TWRP needed to be installed from within CWM, not directly from Odin. A link to these instructions might be very helpful.

Thanks again!
[Galaxy Tab 10.1 Android Development] ENRIQUEMM:
It has fallen further performance. Indicates Antutu 11421

OC 1400 nfq interactive, no frills cpu app

Something I remain poorly to restart after failure when trying to run the recording of the screen. I have returned to perform clean install and AnTuTu back up to more than 16,000 .
[Galaxy Tab 10.1 Android Development] Olivier V:
Mine is reporting around 12500 on 1000mhz and around 18000 when I crank it up and lock it to 1500mhz. Didn't try 1600 yet..

Sent from my Z1 Compact
[Galaxy Tab 10.1 Android Development] decatf:
Antutu is not consistent. Run it 10 times and notice how much variation there is.

It's annoying because I don't have a reliable way to test what changes are good or bad for performance.
[Galaxy Tab 10.1 Android Development] rollrit7:
Hey, I've noticed that mobile data doesn't work with your rom. Any fixes?
[Galaxy Tab 10.1 Android Development] Prowler665:
3G is working just fine. Simply setup an APN manually and you're done. Have a look here for some hints.

Regards
[Galaxy Tab 10.1 Android Development] Prowler665:
FC and lost (User-)App settings

I was away for a few days and left the tab connected to mains using the factory supplied charger. When I returned for some more test of the 20150414 ROM the tab was stuck in the bootanimation. After forcing the tab off and restarting most (?) of the app-settings were gone. The logs show matching entries for the PackageManager complaining about changed uid's resulting in erasing of the 'old' app-data. It seems like system-settings were not affected as far I noticed. There are quite some entries for PackageParser and PackageSettings in the logs too.

There are some new avc-denials and refused connections for Crashlytics which might be ok, but for some reason google gms seems to keep crashing...

This might match this post by [MENTION=5678362]ENRIQUEMM[/MENTION], at least for the crash resulting in lost settings. Thou it seems in his case system settings were affected too.

On a first test the audio-wrapper seems to work quite well with good audio-quality as expected. The dock seems not to work but I didn't have time to get any deeper into this. gonna check it and provide logs later. I couldn't check bluetooth or hdmi since I don't have any matching devices.

Clean install of aosp-5.1.0-p4-20150414 / p75xx-gapps-L-3-28-15 / twrp2860-20150327-p4.

OC 1.4 GHz / interactive / bfq / enforcing.

Regards
[Galaxy Tab 10.1 Android Development] decatf:
Has anyone still been using SELinux in enforcing mode?

I just noticed that the Set_SELinux mode installer breaks things so that it needs to be flashed back to stock with Odin. It this was reported earlier by a p4tmo user but it looks like it's problematic for all the devices. I'm thinking of maybe just removing SELinux all together since it appears not many people care about it.

I haven't been using the Set_SELinux mode installer for the last couple of builds since I flash a build every few days. So I haven't bothered to use it myself lately.

Edit: It's actually recent builds of recovery that are the problem. From 20150407 onwards are problematic. There was a recovery build for p4tmo on 20150407. Anyone who downloaded the TWRP 20150418 builds should revert back to the previous version.
[Galaxy Tab 10.1 Android Development] aamadorj:
Thanks for the information. I've been using the enforcing flashable installer with recovery dated 20150327 at my P4 without issues. I'll be agree with any decision you make about keeping or not SELinux.
[Galaxy Tab 10.1 Android Development] burrni:
Notification problem

I have problem winth notifications: when I pull down the notification shade, I can't pull down anymore to find quick setting. I see no apps notifications in status bar and after pull down notification shade there is neither notifications nor quick icons/quick settings - only message "no notifications".

In settings I also see no way to set notification shade.

I install previous build (20150403) - clean installation from stock with wipes, gapps ( p75xx-gapps-L-3-28-15.zip ) and superSU from the first message. After update on last build (aosp-5.1.0-p4-20150414.zip) nothing changes.

How I can fix it?