yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] superskid:
How do I flash the experimental twrp in Odin? Doesn't look like I can flash a .img file?

Do I use the extra.img or recovery.img?
[Galaxy Tab 10.1 Android Development] Just_Another_N00b:
See post 998 and follow the link supplied. That should give the whole path to getting TWRP on your tab.
[Galaxy Tab 10.1 Android Development] superskid:
Those instruction link to a different version of TWRP, not 2.8.5.0 as suggested for this rom. The one linked to is a file that odin recognizes so that is easy. The one in this thread is a zip with 2 separate image files? I don't know which one to use or how to flash either with odin.
[Galaxy Tab 10.1 Android Development] Olivier V:
Once you flash that twrp in Odin you can flash the new 2.8.5.0 zip file from inside twrp. It's very easy.
[Galaxy Tab 10.1 Android Development] decatf:
No. I just need to see the process of HDMI being set up and running then stopped and removed.
[Galaxy Tab 10.1 Android Development] yitzi:
Lightening Fast - Smooth Ride Where's the Donate Button?

Just dirty flashed 3/20 build over the 5.1.0-p4-20150313 build, also updated SU and TWRP with the latest recommended by the Dev. No problems at all, smooth. This old tab never ran faster since the first day out of the box. I use the tab mainly for news, netflix, watching TV and Movies that were recorded by my server, and email. I also sometimes remote into my machines with the Tab to do admin stuff. I'm a very happy camper.

I don't see a paypal donate button on your page decatf but I would certainty send a small donation your way in appreciation if I could.
[Galaxy Tab 10.1 Android Development] Kaherdin:
It's amazing that my old tab has android 5.1 running! And even more amazing is that it's even before my LG G2 has it!

Amaaaaazing!
[Galaxy Tab 10.1 Android Development] ENRIQUEMM:
Overclock settings unchanged

I used device control to raise the processor speed to 1400 max / ondemmand . And entering the display mode suspension no longer lights up. I kept a few seconds down the On button and lit normally. But had not changed settings . Do not know if there will be collected syslog problem . Notwithstanding attachment

After firing, the parameters of the cpu are as before modifying. But , as seen in the image blocked erroneous values ​​are left alone again restarting previous values. It is perhaps the App .

For the rest goes the rom very well. Maybe a slight lag when changing chart application windows . But otherwise fine , I never thought that the old tab 10.1 was the most updated device

Sorry for my bad English
[Galaxy Tab 10.1 Android Development] decatf:
<- There is a button under my username.

I have seen this problem a couple of times before. One of the CPU cores shuts down for some reason. This causes the system to become very unstable. You have to reboot to fix it.

I haven't been able to figure out what is causing it.
[Galaxy Tab 10.1 Android Development] Prowler665:
Did you at least read the instructions in the guide referred to, especially part II :confused:

Just in case you didn't figure it out by yourself yet - there is no way to flash the TWRP zips via odin!

All files provided by the OP are "flashable zip's" - so you either follow the giude, flash CWM first and TWRP via CWM next, or you try converting the img-files extracted from the TWRP zip-file to tar like described here. The choice is yours.

Reading just a few posts back would have told you that btw...

[MENTION=4523909]Just_Another_N00b[/MENTION] ...it didn't take long for a proof... :D

Regards
[Galaxy Tab 10.1 Android Development] superskid:
I did read a few posts back and I got all of that. But my original question was which img file would I use because there are 2 in the experimental version and only 1 in all the other files. I had already flashed an old version with ODIN before my original post. Nowhere in previous posts that I read did it say that I could flash 2.8.5.0 as a zip file directly from the old version I already have installed, or which of the 2 img files to use if I am to use the script; hence, why I asked the question originally.
[Galaxy Tab 10.1 Android Development] Prowler665:
So it seems you didn't read the guide ;)

Furthermore it seems that you are not familiar with "flashable zip's"... They are not meant to be extracted, but to be flashed 'as is' by a custom recovery.

It might be a good idea to spend some time to get a little more familliar with the basics of custom ROM's before geting disappointed by the pitfalls waiting for you.

Regards
[Galaxy Tab 10.1 Android Development] superskid:
Get off your high horse already. I have rooted and installed roms on numerous android devices. I have never installed TWRP by flashing a zip in TWRP, thats all that someone needed to say. Every other one I have used Odin or flashboot. It was a new scenario so I asked the question which still is not in that guide.

The guide has you flash TWRP via ODIN; however, as stated the TWRP version in this thread is a zip. I have flashed tons of zips in TWRP never a new version of TWRP over the old (not explained in these guides or posts in this thread) I asked the question and it was answered.

Maybe you didn't read my questions thoroughly and linked to answers that aren't relevant. But I read the links to your guides before posting originally and since, and if you can show me where it says to flash the new experimental TWRP from the old TWRP flashed via ODIN then I apologize.
[Galaxy Tab 10.1 Android Development] Prowler665:
The guide is about flashing

CWM

via odin since there has been no TWRP tar-file for ages not to speak of any official one for this tab at all.

You can keep the apology.

<°))))><

Regards
[Galaxy Tab 10.1 Android Development] Just_Another_N00b:
This thread assumes some basic knowledge on flashing as there are numerous other threads on installing a custom recovery and upgrading custom recoveries. We are here to help everybody, but do expect people to do their homework (reading preceding posts and/or other supplementary threads). For that reason we also assume that people know the basics on flashing zips and do not need us to repeat information, other than to clarify and assist.

If you do know a lot about flashing zips we assume that you did know about upgrading custom recoveries as this is a given. Please accept our apologies if we expected too much of your knowledge on the matter and your willingness to read up on the background of flashing before coming to this thread to pose questions...

We also expect some form of courtesy displayed when discussing items or issues, and please keep this thread clean of trolling... [MENTION=3541211]prowler666[/MENTION] is very friendly donating his time and effort to help out everybody, including the OP. Thank you.
[Galaxy Tab 10.1 Android Development] Prowler665:
Using DeviceControl has a, lets say, not so bright history on this tab. I'm not sure about the recent versions but for quite some time using DeviceControl was messing up the system to a degree that only a clean reinstall would help. There are some apps like setcpu or no-frills that are known to work without problems. Most likely switching to one of these will help you get back on track. You should consider a clean re-flash too, just to be on the safe side.

Regards
[Galaxy Tab 10.1 Android Development] ENRIQUEMM:
Hare if his advice , just a doubt, my tab trwp (2.8.5.0) received from stock , and before this rom ( I started with version 5.0 of February) was nameless rom. It would be nice to return to stock and reinstall from there , or as is now making serious wipes enough ... Thanks for your advice .
[Galaxy Tab 10.1 Android Development] jaibar:
I think if you're already on some version cwm, or better, twrp, then just put the twrp zip file in the tablet and simply select and flash it- much much better option than using ODIN. Actually, I'd try to avoid Odin as much as possible, especially if there's no reason to use it at all.
[Galaxy Tab 10.1 Android Development] Prowler665:
I'm not exactly sure if I get your post right so please forgive me if this goes in the wrong direction. There is no need to go back to stock again for a clean installation. Simply wipe system, data, cache and dalvik in "Wipe/Advanced Wipe" before flashing the ROM again to get a clean start. You might want to use TitaniumBackup for a backup of your user-apps so you can restore them afterwards. When restoring, stick to the user-apps and refrain from restoring any other system-data than account-, wifi- and maybe APN-settings since you might mess up your system otherwise.

Your english is way better than my spanish btw, so cheer up and feel free to post any questions that might arise ;)

Regards
[Galaxy Tab 10.1 Android Development] yitzi:
Hey I found it by clicking on your username then a drop down. I was looking for a button and that's why I could not find it before. Just sent a few dollars your way as thanks for your work. I suggest everyone who is enjoying the new life this Lollipop build is bringing to their old Galaxy Tabs do the same! I'm sure every little bit no matter how much is appreciated and it all adds up in the end.
[Galaxy Tab 10.1 Android Development] Prowler665:
Full ack :D

Using the donation-button is rewarding both ways btw. ;)

Regards
[Galaxy Tab 10.1 Android Development] eushaun99:
[MENTION=4404851]decatf[/MENTION] is this fix included in your ROM? Seems like a serious issue here..

http://xdaforums.com/showthread.php?t=3032247
[Galaxy Tab 10.1 Android Development] decatf:
Build 20150328

aosp-5.1.0-p4-20150328.zip

aosp-5.1.0-p4wifi-20150328.zip

Mirror: dev-host

TWRP 2.8.6.0 changelog

twrp2860-20150327-p4.zip

twrp2860-20150327-p4wifi.zip

Changes:

AppOps/Privacy Guard from cm-12.0

f2fs-tools 1.4.1

p4-common: HDMI audio (untested work in progress)

fs_mgr: Skip filesystem check unless fs_type matches

frameworks/base: Clear recents fixes from cm-12.0

kernel:

Revert "disable DEBUG_SEC configs"

radix_tree: clean away saw_unset_tag leftovers

radix_tree: remove radix_tree_indirect_to_ptr()

radix_tree: take radix_tree_path off stack

radix-tree: introduce bit-optimized iterator

radix-tree: rewrite gang lookup using iterator

radix-tree: fix preload vector size

radix-tree: fix contiguous iterator

Update f2fs from Jaegeuk's linux-3.4 branch

f2fs: support for kernel 3.1

mm: shmem: use new radix tree iterator

radix-tree: use iterators in find_get_pages* functions

Additional Notes:

In my last comment about f2fs I said a more recent version appeared to be more error prone but this is because I was not using f2fs-tools 1.4.1 . The latest version of fsck.f2fs does handle more file system errors. The version of f2fs in this build is from the linux-3.4 branch as of March 3. It is newest possible version short using the dev branch. So use f2fs at your own risk!
[Galaxy Tab 10.1 Android Development] decatf:
It is not included in this ROM. The response from Google is that it is working as intended and the patch was not accepted into AOSP. It was not accepted into CyanogenMod either. They don't come to a consensus on the whether or not it's need in their code review comments. I haven't examined the issue closely but it looks like it's the word of at least one engineer at Google + CyanogenMod developers against the one independent developer who submitted the patch.
[Galaxy Tab 10.1 Android Development] jaibar:
Many thanks!

Does the warning in OP still applies for twrp recovery? I mean is it still using the /extra partition and all that?
[Galaxy Tab 10.1 Android Development] decatf:
Yes. It will always be using the extra partition unless someone builds a stripped down version of TWRP again.

The recovery partition is only 5 megabytes. Barely enough space to hold anything and there's no way to repartition this device.
[Galaxy Tab 10.1 Android Development] rtiangha:
Conceptually, if I were to port this to the p4tmo, what would I need to do differently? Is it a matter of swapping in a different kernel for the ROM and TWRP and changing a few entries in BoardConfig.Mk? Or would there be other 'gotchas' involved? I've built custom Roms before, but that was for the Nexus 7 and pretty much all the custom config stuff works out of the box.

If someone can help me figure out how to port this, I'd be happy to do biweekly or monthly builds for the XDA community.
[Galaxy Tab 10.1 Android Development] aga2:
Thanks [MENTION=4404851]decatf[/MENTION] for your work, started the installation of latest version :) (EDIT: works OK as expected :) )

One question, is TWRP 2.8.6.0 supports MTP?
[Galaxy Tab 10.1 Android Development] Olivier V:
Do we still need to do a full wipe coming from the 20/3 build? And flash gapps and supersu every time?

Sent from my p4wifi
[Galaxy Tab 10.1 Android Development] jaibar:
I dirty flashed 28th ROM over 20th , then supersu (although not sure that needed) then reboot- everything seems to work fine.
[Galaxy Tab 10.1 Android Development] Prowler665:
Since the 03-20 build already is a 5.1 ROM a 'dirty' flash should be sufficient. As long as /system is not wiped prior to flashing the ROM both SuperSU as well as the GApps are automatically saved and restored during the installation of the ROM.

On the first installation of SuperSU you are asked if a rescue-script should be installed to survive the flashing of a new ROM. This will be install to "/system/addon.d/99-supersu.sh". If this file exists, automatic backup and restore will be performed if you 'dirty' flash a new ROM.

If this file does not exist take a look at the settings in the SuperSu-app. There is an option to install it.

Regards
[Galaxy Tab 10.1 Android Development] hmarcus56:
i found a problem you maybe aware of

I want to thank you for all the hard work put into this rom but the Camera started a couple of times and now it crashes
[Galaxy Tab 10.1 Android Development] Just_Another_N00b:
I did notice on my p4wifi that the 20150328 release is quite a bit less smooth in the full-screen scrolling inside games. Even starting scrolling has a lag. Tried reset, factory wipe, and reverted back to the 20150320 release to get the smooth scrolling back. Don't know if this is traceable by any tool...
[Galaxy Tab 10.1 Android Development] dimem:
USB connection with Windows 7

Please tell me what drivers I must to have installed on my Windows 7 laptop to see the Samsung GT-P7500 through the USB connection? I don't have any problems before with the Samsung stock ROM but when I installed your ROM Windows and Odin don't see my TAB.

Thank's...
[Galaxy Tab 10.1 Android Development] Olivier V:
I'm suspecting you didn't tick the MTP box or toggle under Storage and then USB-Connection (3 dot menu in the upper right corner).
[Galaxy Tab 10.1 Android Development] dimem:
I'm not shure but I think that I have tick the MTP box. I will check this, Thank's.
[Galaxy Tab 10.1 Android Development] jaibar:
Try also toggle between media and camera, wait a few seconds between and see if windows is recognizing the device.

Did you check in windows device manager if it shows at all? With exclamation or question mark, or simply nothing?

Last but not least- have you got another usb cable to check? A cable that worked before may have stopped doing so...
[Galaxy Tab 10.1 Android Development] spamam1:
TWRP 2.8.6.0 - typo?

Hello,

Thank you for the update.

I dl'ed and installed the P4 TWRP, but the log says 10.1 WiFi..

Is it just a lot/text typo? Or is the P4 recovery actually the P4wifi (and perhaps vice versa)?

Is there a way to check?

Thank you!
[Galaxy Tab 10.1 Android Development] decatf:
Build 20150330

http://d-h.st/users/decatf/20150330

The XDA file host is not cooperating again so the files are only on dev-host for now.

The 20150328 ROM was accidentally built with the userdebug config instead of the user config. It happened when I was trying to find ways to cut down on compile time. It is back to the user config now. You can dirty flash.

The messed up colors in recorded video are fixed in this build.

Changes:

Camera2: Allow setting "profile-video-size" before recording starts

kernel:

memcg: fix/change behavior of shared anon at moving task
mm: don't inline page_mapping()
swap: make each swap partition have one address_space
video: tegra: nvmap: Update to use new total_swapcache_pages function
staging: android, lowmemorykiller: convert to use oom_score_adj
android, lowmemorykiller: remove task handoff notifier
staging: android: lowmemorykiller: Add config option to support oom_adj values
staging: android: lowmemorykiller: Don't count reserved free memory
staging: android: lowmemorykiller: Change default debug_level to 1
lowmemorykiller: make default lowmemorykiller debug message useful
android/lowmemorykiller: Check all tasks for death pending
android/lowmemorykiller: Only consider gfp_mask free pages
android/lowmemorykiller: Wait for memory to be freed
android/lowmemorykiller: Ignore tasks with freed mm
Revert "android/lowmemorykiller: Only consider gfp_mask free pages"
android: lowmemorykiller: add lmk parameters tunning code.
android/lowmemorykiller: Selectively count free CMA pages
android/lowmemorykiller: Account for total_swapcache_pages
lowmemorykiller: Account for highmem during kswapd reclaim
Revert "android/lowmemorykiller: Selectively count free CMA pages"
lowmemorykiller: Don't count reserve page twice
lowmemorykiller: optimize for use with zswap
lowmemorykiller: remove dead code
lowmemorykiller: Fix __module_param_call for 3.1 compatability
introduce for_each_thread() to replace the buggy while_each_thread()
android: lowmemorykiller: squash task adj rbtree optimization from Motorola

The only changes in 20150328 over 20150320 are added AppOps and update f2fs. Plus the previously mentioned userdebug build instead of user. Hopefully it's only due to the userdebug build.

edit: I had also re-enabled Samsungs debugging config in the kernel because otherwise the previous kernel log was not getting saved. I tried disabled it originally because it's very intrusive with a lot of custom changes for debugging output everywhere in the kernel. I could try disabling it again if this build still slower like the 20150328 build.

It's just a typo.
[Galaxy Tab 10.1 Android Development] honhan0904:
[MENTION=4404851]decatf[/MENTION] cant downliad from that host. Pls upload to mega or another host . Thânks
[Galaxy Tab 10.1 Android Development] Technical:
I can't download either. Even entering (login), I can't download.
[Galaxy Tab 10.1 Android Development] dillfever:
nor l
[Galaxy Tab 10.1 Android Development] Prowler665:
Use this link.

Regards
[Galaxy Tab 10.1 Android Development] joegreat:
I am downloading now (painfull slow) as I have to choose "Download Now" button - "Download" made my Kaspersky Internet Security go crazy (malware download via EXE file)! :confused:

Direct Link to the files: aosp-5.1.0-p4wifi-20150330.zip aosp-5.1.0-p4-20150330.zip

With kind regards

Joe :cool:
[Galaxy Tab 10.1 Android Development] Olivier V:
There's a link to all his downloads in the OP. It works, downloading with my tab as I type this.
[Galaxy Tab 10.1 Android Development] Olivier V:
Reverted back to the 20/3 release. It's a lot smoother imo. Only played with the 30/3 build for an hour or so but found no bugs (at least not with the stuff I need). Anyways it's a great ROM but the previous version was slightly greater ;)
[Galaxy Tab 10.1 Android Development] Prowler665:
As stated previously by some of the others the performance of this build dropped noticeably. According to AnTuTu the main issue seems to be the runtime-performance - I don't see any obvious candidate for this in the changelog thou... Could it be related to the memory management? Just a wild guess thou...

Regards
[Galaxy Tab 10.1 Android Development] dihoc:
help!!

[MENTION=4404851]decatf[/MENTION] I dirty flashed my p4wifi with 20150328 build AND twrp 2860 last night. Everything ran smoothly except Google Voice search ("Ok Google" did not work). Since Google Voice search worked fine with previous builds, i returned to 20150320 build. Now I can't reboot my tab into recovery, which is weird. It hangs at welcome screen forever. I can not even power it off. The only option to recover it is flash recover.tar via Odin. My tab is currently running 20150320 build. I cannot flash new builds because I won't be able to reboot my tab into recovery. Do you think twrp 2860 a trouble-maker here? Any suggestions?

Thank you many many times for your wonderful work on our ancient tabs
[Galaxy Tab 10.1 Android Development] decatf:
Is that result repeatable? I am still getting around 17000 score at 1.4Ghz.

Though, there does appear to be a slight performance regression with the Interactive scheduler. I am getting under 17000 and in the 16000 range more often than not. But this issue predates the recent three builds (20150320, 20150328, 20150330).

So flashing any version of the ROM breaks recovery for you?
[Galaxy Tab 10.1 Android Development] Prowler665:
Actually the 14k was one of the better runs it seems... I just did a few more and the performance is degrading :confused:

My first guess was that no-frills might be the culprit, but the statistics indicate that OC is working.

I have dirty flashed the last two updates, only wiping cache and dalvik. CPU is set to 1,4 GHz / 216 MHz, governor is interactive, I/O sheduler is set to bfq. Before testing I reboot the tab, close all recents and let it settle for a few minutes after reboot. Usually I do a minimum of 3 tests since AnTuTu is not that consistent...

I didn't have time to take a look at the logs yet, but I'll try it with a clean install tomorrow.

Regards
[Galaxy Tab 10.1 Android Development] dihoc:
[Right at this moment i am stuck at 20150320 build and not able to get out of it to flash new builds. That is a result of flashing 20150328 plus twrp 2860 then going back to 20150320. The good thing is the tab runs fine at 20150320 build. It just refuses to get into recovery mode for flashing new roms

QUOTE=decatf;59792139]Is that result repeatable? I am still getting around 17000 score at 1.4Ghz.

Though, there does appear to be a slight performance regression with the Interactive scheduler. I am getting under 17000 and in the 16000 range more often than not. But this issue predates the recent three builds (20150320, 20150328, 20150330).

So flashing any version of the ROM breaks recovery for you?[/QUOTE]
[Galaxy Tab 10.1 Android Development] decatf:
Did you actually try restoring recovery with odin or not? If TWRP won't boot then the only option is to flash an old recovery like CWM with odin. Then install TWRP inside CWM.

If you've restored recovery and flashed a ROM again and it still breaks recovery then you need to send me the kernel log from TWRP. How to do that:

Install a ROM and install SuperSU in TWRP.

Boot the ROM and install SysLog.

Reboot into TWRP and wait until the point where it's stuck.

Hold down the power button to reboot into the ROM.

Open Syslog app and save the Last Kernel Log.

Send me the log files stored in /sdcard/Syslog.

Share the files on Dropbox or another similar site. Then PM me a link to the files.
[Galaxy Tab 10.1 Android Development] Prowler665:
I tried again today with a clean installation and this time the performance was way better. Still about 1k below the 03-13 ROM, but with an average of ~16.100 nowhere near the ~11k of the last attempt.

Somewhere on the road 'dirty flashing' from 03-20 to 03-30 the runtime-performance seriously got affected. So for best results I'd recomend a clean installation of the 03-30 ROM if anyone is experiencing performance issues.

I admit that I'm too lazy to track down what actually was causing the problems ;)

Attached are screenshots of 2 sets of tests about 30 minutes apart.

Clean install of aosp-5.1.0-p4-20150330. OC 1.4 / interactive / bfq

Regards
[Galaxy Tab 10.1 Android Development] decatf:
I did some testing today and there is a clear drop in benchmarks from the 20150320 build. Pretty much the same Antutu results as above. The Runtime benchmark was affected the most. I am still narrowing down the problem.