yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] honhan0904:
My device is P4 and it can get access through pc easy

Have you install driver yet , my windows both 7 and 8.1 work well
[Galaxy Tab 10.1 Android Development] TheOrangeRemix:
Sweet! For once, we get a newer Android version sooner than the XOOM does. Will flash this tonight.
[Galaxy Tab 10.1 Android Development] honhan0904:
Than note 4 too lol
[Galaxy Tab 10.1 Android Development] Lucas Kado:
Precisely. [MENTION=1901608]fixbug[/MENTION] says version 9 runs on his tab :eek:
[Galaxy Tab 10.1 Android Development] fixbug:
Since last map update (9.1), same problem :(

My test with 9.0 was less than 1 minute.
[Galaxy Tab 10.1 Android Development] Dr asphalt:
No bootloop issue at the moment on my p4.

No overclock only governor is set to ondemand...the Tab is fast when battery is charged than reduce the reactivity..For me at the moment Power consuption is a little bit more than ICS 4.0.4 deepsleep modyfied.

Have installed YouTube old ver. 4.0.23 and works well with no lags the settings is naturally set on play in no HD otherways you head but not see. Sometime crasch and say the service is colse etc... but nothing like ver 9.
[Galaxy Tab 10.1 Android Development] honhan0904:
[MENTION=4404851]decatf[/MENTION] more update please
[Galaxy Tab 10.1 Android Development] decatf:
There is a new build up 20141120

Current changelog: -- November 20, 2014

[new] Update to android 5.0.0 r7 (LRX21V)

[new] kernel: arm: tegra: Add an API call to log wakeup reasons

[changed] Enable multi user UI

[changed] Bluetooth audio compatibility backports

[fixed] Browser settings crash

I've added couple of Bluetooth audio backports. I don't know if they did anything so please test it.
[Galaxy Tab 10.1 Android Development] mj-motorsport:
Installed lollipop with no problem whatever, the p4 version. But i cant get play to work, it say no connection try again, gmail, g+ dont work either!? Why?
[Galaxy Tab 10.1 Android Development] gscollier:
GPS and Bluetooth Audio still not working

Installed latest but still neither of these work. Neither worked in first release either. I have a P4, perhaps works on wifi? Full wipe etc, etc.

Still, really great to play with lollipop, thanks and keep the releases coming!
[Galaxy Tab 10.1 Android Development] aduhai:
P4 gps still not working. No sim card detected.
[Galaxy Tab 10.1 Android Development] spamam1:
Root / supersu?

After flashing the Nov 20 ROM and lp GApps, tried stable 2.16 as well as beta 2.25 and 2.27 versions of SuperSU.. No root.

Using TWRP.. 2.8.0.0 I think.

A) just me?

B) Wil try cwm and report

Note: not wiping data from previous ROM.. Will try that

If cwm doesn't work
[Galaxy Tab 10.1 Android Development] iopxiang:
Do I need to reinstall gapps after updating? Cannot root this time
[Galaxy Tab 10.1 Android Development] ep3k20a03:
I also lost root after dirty flashing 11/20/14 Rom with IP GApps. Tried the older root methods in the forum, but it conflicts with SuperSU. Let me know if a full wipe works in restore root for you. Thanks.
[Galaxy Tab 10.1 Android Development] aduhai:
Need to install gapps and superuser after install rom
[Galaxy Tab 10.1 Android Development] gscollier:
Tried that. Still no root after several boot/flash su attempts.
[Galaxy Tab 10.1 Android Development] ThePsychiatrist:
Hi All,

First of all thanks for the rom. It is beautifull. I do have a question wich i hope one of you can answer. When i have installed the new rom i encounter one problem.

When i push te power button shortly to put it into sleeping mode, or when times go by and the tablet puts itself in sleeping mode, my screens turns off, but there is no way to turn it back on, besides hard reset. What have i done wrong and what can i do about this.

At the moment the tablet is not usable.

Thanks for your help,
[Galaxy Tab 10.1 Android Development] DrGirlfriend:
"I can't access this doc - says file does not exist. Can you point me at it?"

Sorry, I'm not allowed to post full links yet - you have to combine the two lines removing the "On " at the bdginning and the "-- file:\n" in the middle to form a full address. Or just google "JimTDI Nexus 7 Tuning Guide.doc". It was originally on xda (11-01-2015, 08:39 AM) but the up to date version now lives on google docs
[Galaxy Tab 10.1 Android Development] DrGirlfriend:
I would start over flashing, carefully following the OP instructions. I've gotten strangeness by not doing Factory Reset (step 2).

Good luck
[Galaxy Tab 10.1 Android Development] rtiangha:
Are you overclocking? There might be issues if you set things too high. Try throttleing down. Conversely, there might be wake up issues if your minimum clock speed is too low. You'll want that set to at least 216 MHz and not lower.
[Galaxy Tab 10.1 Android Development] ThePsychiatrist:
Hey Thanks for your answer. I was overclocking, but when i set it to standard the problem isn't gone. When i unroot my tab to the original rom the problem is gone. When i flash a rom again the problem is present again. So both the solutions didn't work sadly, any other ideas?

update: I have now a working 5.1.1. I used omni 5.1.1. Thank you all for helping.
[Galaxy Tab 10.1 Android Development] Prowler665:
You used DeviceControl for overclocking I guess? The DC-app has a history of messing up this tab pretty bad to a point only a clean install could help.

Regards
[Galaxy Tab 10.1 Android Development] tpsnjs:
Get default browser to show the desktop version of websites

Hi,

This should be asked in Questions area, but this is the goto place for this tablet.

Yesterday I rooted and installed 5.1.1 on a friend's 10.1 (I've done this for three people now - this one was stock and unusably slow).

I find the browser that comes installed with this ROM faster than Chrome.

How can you make this browser get the desktop version of webpages?

For Chrome, you use the steps detailed here http://www.guidingtech.com/16169/desktop-mode-websites-chrome-android-permanently/

Thanks in advance
[Galaxy Tab 10.1 Android Development] doganmanis:
thankyou for this rom

just installed and i love it, very smooth :D

i have a problem with Android System WebView, always force close when i try to open

how to fix this?

can i just install from apk?
[Galaxy Tab 10.1 Android Development] fz798:
First and foremost, many thanks for this ROM.

I've searched and I saw the note in the OP regarding the keyboard dock, but I am hoping maybe somewhere I missed something, is there no way at all to get the keyboard dock working with this ROM/kernel, if even by downgrading or sacrificing some feature/functionality?

Thanks for any help or input on this (pun intended)
[Galaxy Tab 10.1 Android Development] Just_Another_N00b:
Any plans for M? I know it still is in its infant stages, but sounds like a new challenge...
[Galaxy Tab 10.1 Android Development] NeoStormer:
Any chance of a P4VZW flavor? Don't need 4G, just WiFi, would one of the others potentially work? hoping to get out of the 4.1.2 slump.
[Galaxy Tab 10.1 Android Development] dihoc:
Does anyone know how to bring the kill all apps button back ? All of the sudden it disappears on my p4wifi with 0513 rom. It is painful to kill one app at a time. Thanks a lot
[Galaxy Tab 10.1 Android Development] aduhai:
Setting - developer options - kill back button.
[Galaxy Tab 10.1 Android Development] dihoc:
Thank you for your response.
[Galaxy Tab 10.1 Android Development] bl4nk:
Hi,

I've tried installing this rom several times. Everything seems to go through ok, but I am unable to install any new programs.

The "Google" app (36.31 mb) download seems to crawl along and never makes any progress. When I cancel it and go download anything else, google play downloads the program once, then it seems to start up and download the program again and pops up with an error of "Program could not be downloaded due to an error (907)".

After this, I try to reboot into twrp recovery to re-flash, but twrp does not see any of the internal storage or data or system! I have to odin flash cwm touch to factory reset and then flash twrp again.

Does anybody have any idea what's going on or any advice on how to proceed? Are my partitions corrupted somehow?

I wanted to try and flash everything back to stock to start all over, but I can't seem to find any instructions with working download links, if anybody has one please let me know!

EDIT: Forgot to mention that i have the Google I/O edition p4wifi

2nd Edit: Finally fixed it, I think it was because I missed the step about wiping /system for the first install, but I also went ahead and reverted everything to stock via odin and the firmware download at http://www.sammobile.com/firmwares/download/5944/P7510UELPL_P7510XABLPL_XAB/
[Galaxy Tab 10.1 Android Development] mint403:
You're amazing! Thanks!
[Galaxy Tab 10.1 Android Development] doganmanis:
thank you for update :good::good::good:

but how to update?

is it just flashing the new zip?
[Galaxy Tab 10.1 Android Development] dihoc:
i flashed the new rom, gApp and superuser together. It worked
[Galaxy Tab 10.1 Android Development] Grop:
update

Just did a dirty flash, only the zip file, and everything is oké so far.

Thanks for this update
[Galaxy Tab 10.1 Android Development] decatf:
Send me a logcat so I can see the crash log. See post #2 under Problem Reporting Steps on how to do so.

I don't know why the keyboard dock is not working. Someone sent me kernel logs before and all I can see is that the dock is not initializing properly. They told me that it works in the CM 10.1 which my kernel branch is descendant from. There has not been any changes in to the kernel keyboard dock code since then. So there is some other reason why it is not working.

It won't be easy for me to figure this out because the only method at my disposal is having someone with a keyboard dock test through the history of kernel/ROMs until the point where it stopped working is found.

The CM-11.0 ROM is also on the same kernel branch but I don't know if the dock worked on that. It would be useful to test if the dock works on that. If it does then I could try to get a CM-11.0 compatible version of my kernel for you to test so that we can see if it is the kernel or something in Lollipop is the problem.

The p4 tablet can use the p4wifi ROM. I don't know if this is true for the p4vzw though.

The GPU is already overclocked to 400Mhz. It won't go any higher than that. The GPU frequency is set during kernel initialization. There is no way to modify the GPU frequency afterwards.

I won't be reverting the old disable MMC_CAP_ERASE patches anytime soon due to the nature of the bug. A certain percentage of devices could get affected by the brick bug. Even with rigorous testing the bug could not appear at all. Then with a public release and many more devices using the code there could suddenly be a rash of users getting hit with the brick bug. Pretty much what we saw happen back in 2012.

I know that recently there are other devices whose ROM maintainers have applied Samsungs kernel patches and restored the MMC_CAP_ERASE code but keep in mind that there are many different "brickbugs" that affect different devices. Some are less severe than others. The one that affects this device is the "Superbrick" bug which kills the device completely. As in throw it in the garbage once it is bricked. I am not willing to risk this at the moment.

Here is a workaround.

Install Nomone Resolution Changer. Set the resolution to 1280x768 and 160 DPI.
[Galaxy Tab 10.1 Android Development] L3R0N:
Hi [MENTION=4404851]decatf[/MENTION], could you build a kernel for the p5 3g? We are currently using a port of your ROM on the p5 but our kernel is made from a cm11 zimage and a lollipop ramdisk. That's because the full lollipop kernel has some random reboot issues and the screen won't turn on when it goes off unless you reboot. So I'm asking you to build one for us if its not too much of a problem...if it is then don't bother. I'm willing to test whatever you come up with should you attempt to build one. The lollipop kernel works fine on the p5wifi so only the p5 3g is affected by those issues I mentioned. If you won't build one then do you have even the faintest idea what might be the cause of these issues? The p5 and p4 are very similar, in fact we use the same ROM nothing is changed except in build.prop where p4 is changed to p5 etc. The only thing different between them is the kernel and I'm pretty sure they're not different by a long shot.
[Galaxy Tab 10.1 Android Development] decatf:
I don't mind building a kernel but did you run into some problems building it yourself or something? With the same source code and compiler the resulting kernel should be exactly the same no matter who has compiled it.

The source code may be similar but each device has it's own config which means there are some differences between each version of the devices. My advice is to use make sure you've built with CONFIG_MACH_SAMSUNG_P5=y and the rest of the CONFIG_MACH_SAMSUNG_* disabled. And make sure you've packaged it with the AOSP p4 ROM and not the p4wifi ROM.

In the past I have run into similar problems using the p4 kernel on a p4wifi ROM (reboots and shutdowns on screen off). The kernel logs showed some crash but I did not know enough about it to be able to narrow down the issue. It was somewhere in the suspend code. You should get the last kernel log in /proc/last_kmsg. The last kernel log only survives the first boot after the crash. So boot up again and save it before you reboot again. Without kernel logs there's not much to go on.

Second thing is how sure are you that the p4 kernel is exactly the same source code as the p5 kernel. I mean they appear to be the same but has any p4 kernel worked on p5 without these issues in the past? A way to check could be to take the stock kernel source from p4 and diff the entire thing against the stock kernel source from p5.

Third thing is proprietary blobs. Have tried replacing all the proprietary blobs in my AOSP ROM with ones for the p5?
[Galaxy Tab 10.1 Android Development] doganmanis:
sorry, problem fix when i reflash gapps. there is no fc :victory:

i just reflash the new update, wipe cache and dalvic before flashing and everything work fine

the audio apps from http://xdaforums.com/android/software/mod-beatsaudio-e-xloud-installer-t3029951 is gone

but just reinstalled and audio apps back to normal

thank you decatf :good:
[Galaxy Tab 10.1 Android Development] L3R0N:
I've never tried building directly from your source but I've tried building from this and it'd work for some time then freak out after a while. Almost every ROM the p5 has ever had has been a port from the p4 but I'm not certain how similar their sources are. Back in 4.4 days we had no issues with the kernel whatsoever while OmarEinea was doing the porting I'm guessing he didn't add anything special to the mix he just built from source. However when jolinnard took over it started having random reboots, loss of 3g signal and the screen would sometimes refuse to turn on when it went off. Fast forward to 5.0-5.1 and these issues are still there. So I'm thinking maybe he added something that doesn't agree with the p5 but works fine with the p5wifi. The thing is the p5wifi ROM and kernel work fine on the p5...no issues whatsoever but the p5 ROM and kernel has issues. I'm still learning about android and kernels and all that so I don't quite know a whole lot yet but I'd be more than happy to get you any logs you need. I've packaged the kernel with a p4 ROM always and its always been problematic so wrong package is not the cause or at least I'd like to think so.
[Galaxy Tab 10.1 Android Development] twhansen:
I seem tonhave lost root access with the 0620 update (p4). Anyone else with this problem and whst is the easiest way to fix it?

Sendt fra min p4 med Tapatalk
[Galaxy Tab 10.1 Android Development] decatf:
I think there was only one official keyboard dock from Samsung. From the kernel logs I got before the keyboard input driver stops halfway through that's why no buttons work. I don't know why it fails though.

I PMed you some kernel builds to test on cm-11.0.
[Galaxy Tab 10.1 Android Development] fz798:
I'd be stoked to have the keyboard dock working.

Thanks to you both for looking deeper at this!
[Galaxy Tab 10.1 Android Development] rtiangha:
Might this be related to a missing generic USB keyboard driver in the kernel? I recall hooking up a USB keyboard using an OTG cable didn't work either (although it works fine on my stock Note 8).
[Galaxy Tab 10.1 Android Development] FCKöln:
I tried all three kernels on cm11 and the keyboard keys works with all of them. I checked the kernel version on the settings page after flashing each kernel to make sure that it's a different kernel... (different build date for every kernel)
[Galaxy Tab 10.1 Android Development] decatf:
That is an unexpected result. It seemed like it was some change since the CM-11.0 kernel but I guess not. From what I can tell the driver is supposed to initialize the keyboard and Android just detects the keyboard dock when it becomes available. So there is probably something that changed in Lollipop that broke it.

Can you send me a kernel log taken from Lollipop? Put the tablet on the dock first then boot the device and take a kernel log.

The p4wifi-kernel-4.9-4cb02203 is the same as the most recent kernel in the AOSP ROM except it is compiled without SELinux. You could try installing that on AOSP if you're not using SELinux in enforcing mode. I don't think it is SELinux that is the problem though.

Also have you tried the keyboard dock on OmniROM 5?
[Galaxy Tab 10.1 Android Development] FCKöln:
Flashed omni-5.1.1-20150620-p4wifi-HOMEMADE as secondary ROM and it's the same behaviour as with your 5.1 ROM. USB debugging works through the dock but keys are not recognized. Attached is a kernel log from your 5.1 ROM. Will try the other kernel in the next days and report back.
[Galaxy Tab 10.1 Android Development] decatf:
I don't think it is the kernel since it works with the current kernel on CM-11.0 and the keyboard also doesn't work on OmniROM 5.

We can see where it fails in the kernel log. It happens pretty early (29 seconds) in the kernel boot process. It's expecting some hardware to be ready but it's not for some reason.

<6>[ 29.291953] [Keyboard] console uart path is switched to AP.
<6>[ 29.292199] [Keyboard] baud : 9600, quot: 1406
<3>[ 29.321893]
<3>[ 29.321899]
<3>[ 29.321901]
<3>[ 29.321903] [Keyboard] the uart is not ready!!!

When it is working on CM-10.0 it looks like this.

<6>[ 28.492798] [Keyboard] console uart path is switched to AP.
<6>[ 28.493073] [Keyboard] baud : 9600, quot: 1406
<6>[ 28.547319] [Keyboard] Unkown key layout : 0
<6>[ 28.660981] [Keyboard] US keyboard is attacted.

At that point it a lot of the base Android services have not even started yet. So it could possibly be some lower level part of Android that broke it. Since we've ruled out the kernel itself there is possibly something else that is affecting it. I have no idea what could be.
[Galaxy Tab 10.1 Android Development] twhansen:
I still have problems with my root access on this update (P4). It worked great with all previous updates. But this time I lost root, even though the tab seems to go through the same steps as always including the installation of supersu at the end of the ROM flash.

Hopefully someone can guide me in the right direction. It's been ages since I rooted this tab.

Thanks.
[Galaxy Tab 10.1 Android Development] honhan0904:
When you flash this rom on twrp 2.8.x i think it will ask you if you want to install super SU on that rom. Just swipe
[Galaxy Tab 10.1 Android Development] twhansen:
That's exactly what I did and what I have done previously. This time I lost root access.

Sendt fra min HTC One M9 med Tapatalk
[Galaxy Tab 10.1 Android Development] DE52:
Have you tried installing the superSU flashable zip yourself instead of depending on TWRP to root? You can get the flashable zip from here
[Galaxy Tab 10.1 Android Development] twhansen:
Yep, that was the first thing I tried.

Sendt fra min HTC One M9 med Tapatalk
[Galaxy Tab 10.1 Android Development] djokaspotoka:
Nokia Here maps

Hello everybody,

First I want to thank [MENTION=4404851]decatf[/MENTION] for excellent work on our outdated device.

I have one question. Is there any chance to make Nokia Here maps working? Its just closing without any error. I have tried different roms, same thing.

P7500 3g model, full wipe, latest TWRP ,no joy. Is there any other solution?

Thanks in advance.

Log: https://mega.nz/#!WV9xAbJY!-gDDySg5TP-txXDeoEvkQhpCgZX06yGwyXVNeTYEgnY
[Galaxy Tab 10.1 Android Development] Olivier V:
I have had the same problem, no solution yet I'm afraid.
[Galaxy Tab 10.1 Android Development] freakthekid:
twrp issue

hi guys! has anyone experienced any issues with the new twrp? here's mine: ive flashed the new twrp build, suitable for my device and now my pc doesn't recognize it in recovery mode, like with the previous version. can anyone help me with that issue?
[Galaxy Tab 10.1 Android Development] decatf:
It's crashing with SIGILL (invalid instruction) exception. So that app is probably using NEON. The CPU does not have support for the NEON instruction set. If you can find older versions of the app you might be able to find a version that does not use NEON.

That's same issue as with Google+. The current version uses NEON.

Can you be more specific? MTP is not working or what? What was the previous version of recovery you used?

With out any logs it's impossible to know what's going on.
[Galaxy Tab 10.1 Android Development] freakthekid:
cheers

hi, sorry for my panic posting. used p4 version both with twrp and system image as well, everything works like a dream! big ups for your work!
[Galaxy Tab 10.1 Android Development] lalleyne:
I've got a GT 10.1 Verizon model and don't need the LTE, would like to have Lollipop even if only with wifi.

Is there a way to modify the p4wifi image to get it to install on a p4vzw?

Was thinking that maybe repackaging the boot.img to have the CM10.2 p4vzw bootloader but this new Lollipop kernel, and modifying the update-script to ignore the model ID...would that work?

Trying to avoid having to build the whole image.