yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] decatf:
I posted a build for p4 and p4tmo that includes a missing init script for 3G.

I don't know why p4tmo is being weird. It's the same as the p4 ROM with the ramdisk replaced with the p4tmo ramdisk. So the only real difference is the kernel.

Can you get a kernel log when it doesn't wake from sleep? Reboot the system after it doesn't wake and save the last_kmsg using Syslog as described in the second post.

Edit: Also I'll try building the p4tmo TWRP again some time soon. It would help if someone could post the kernel log from that too. The steps to do so are as follows:

1. Flash the non-working p4tmo TWRP

2. Reboot into recovery and let it sit at least 3-4 minutes regardless of whether it boots or not.

3. Hold down power + vol down.

4. Odin flash a working TWRP build

5. Reboot directly into TWRP

6. Use the file manager in TWRP to copy /proc/last_kmsg to /sdcard/

7. Post the last_kmsg file here
[Galaxy Tab 10.1 Android Development] mistersixt:
I have a similar issue with waking up my device (p4 this is): with the build 20160128 it happened 3 times now that the power button does not wake up the system. Only a hard reset helped bringing the system up again. This was working fine with the previous build. I will try to generate a logcat next time.

Regards, mistersixt.

---------- Post added at 11:44 AM ---------- Previous post was at 11:28 AM ----------

Now I even have constant resets, please find a kernel logcat here:

http://144.76.203.117/tmp/2016-02-02_11.43.zip

Hope this helps,

regards, mistrsixt.
[Galaxy Tab 10.1 Android Development] spamam1:
Hi,

I checked the 1st post, but still seeing the Jan 28 build.

I found the updated, Feb 01 build via the "Download" tab

at the top.. yes!! =D

Please update the post, or remind people to -also- check

the Download tab. Thanks as always!
[Galaxy Tab 10.1 Android Development] rtiangha:
Alright, just saw the message about the new rom; am currently downloading it and will try it again.

As for the p4tmo TWRP, I flashed the one in the OP again through Odin and can't get it to freeze again. Regardless, I can't boot into recovery using it and it goes straight to the Multirom menu every time. Below is the kernel log as per your instructions.

https://app.box.com/s/lo11hgbz7kyghdgb4nvfg8eyk21uyb2h

The only other thing I can think of is that the first time I tried things when it started to freeze, I didn't flash this version of TWRP through Odin; I used the flashable zip instead. Would it be worthwhile for me to try the flashable zip method again?
[Galaxy Tab 10.1 Android Development] decatf:
There is another build of TWRP for p4tmo. I've tested it on my p4wifi by swapping the proper kernel for my tablet. The only change from the previous recovery kernel was F2FS which should have caused boot failure so hopefully it is working now.

Which builds exactly do these wake up and reboot problems occur?

Does it occur with the 20151211 build too?
[Galaxy Tab 10.1 Android Development] rtiangha:
OK, I flashed the Feb 01 p4tmo rom and have been running it for most of the day; it seems fine. Before, like mistersixt, it would just randomly turn off or reboot, and I couldn't wake it from sleep. I don't get these issues anymore. So maybe problem solved?

The only issue I have is with the camera; the app says the camera is in use, although I'm using Open Camera (which works fine on the Lollipop rom). Is there a preferred camera app to use just for photos?

Going to download and try that new TWRP right now.
[Galaxy Tab 10.1 Android Development] L3R0N:
[MENTION=4404851]decatf[/MENTION], if its not too much of a huge issue can you add in the rotation fixes to make this rom work on the Tab 8.9? We've already done the hard work of getting the tab to boot your M build and now all thats left is to fix rotation. The patches are the same ones from Lollipop and can be found here. I hope its possible.
[Galaxy Tab 10.1 Android Development] decatf:
It's in the 20160131 build.
[Galaxy Tab 10.1 Android Development] rtiangha:
OK, I flashed the new p4tmo both via Odin and flashable zip from using the Multirom TWRP, but I get a bootloop as soon as I try to access recovery either through the power menu or from cold boot using the hardware buttons. I can still boot my rom, though. Am I encountering this because I'm trying to switch from the Multirom TWRP to this version or because my roms have Multiboot injected? Should I try Odin'ing the stock Samsung ICS rom and start from that?

Here are the logs; hopefully it captured the bootloop craziness.

https://app.box.com/s/546thhvmesmnflfnnjfsbfg6dn6natqn

EDIT: If it matters, right now, my primary rom is Lollipop and secondary is Android 6.0.
[Galaxy Tab 10.1 Android Development] L3R0N:
Thank you, I just noticed the changelog however, I cannot see an 0131 build for the p4WiFi or a build more recent than the 0128 build.
[Galaxy Tab 10.1 Android Development] rtiangha:
It's not in the OP links (yet), but check the Downloads tab at the top of the page and you should be able to find the absolute latest versions.
[Galaxy Tab 10.1 Android Development] decatf:
I uploaded another build. If this doesn't work thing I'm out of ideas for now.

The 20160201 ROM is the same as 0128. The only difference is the ramdisk. Only the 0131 build has the hwrotation patches.
[Galaxy Tab 10.1 Android Development] rtiangha:
Well, good news/bad news.

Good News: I was able to use the flashable zip to flash this version of TWRP. Love the new menus!

Bad News: The Odin version gives me a "MD5 hash value is invalid" error when I try to flash the tar.md5 version using Odin. I downloaded it twice to be sure. I've been using Odin3 v.1.85 if it matters.

So almost there! Once all this is ironed out, would it be worthwhile refreshing the Multirom TWRPs as well?
[Galaxy Tab 10.1 Android Development] L3R0N:
Thank you very much for your effort decatf. Made a quick port and the bootanimation is rotated the right way so you've done your part. Thanks for continuing to look out for us the 8.9 users. :good:
[Galaxy Tab 10.1 Android Development] mistersixt:
With version 20160201 the reboots are gone!

Regards, mistersixt
[Galaxy Tab 10.1 Android Development] donjuan10:
The reboot is gone but the 3G is not working and the camera had an error sign.

Here is the log for the camera error:

https://www.dropbox.com/s/qzng9di9w55mcex/2016-02-03_11.27.zip?dl=0

Thanks for the update decatf :)
[Galaxy Tab 10.1 Android Development] daneal2u:
could someone post a mirror link to the latest p4 rom and twrp?

I'm only getting speeds of ~10Kb/s due to heavy traffic on xda servers
[Galaxy Tab 10.1 Android Development] Vitlll:
My device P4 3G

about 3G:

1. aosp-6.0-p4-20151211.zip - 3G works good!!! :)

2. aosp-6.0-p4-20160128.zip - 3g is not working (no sim )

3. aosp-6.0-p4-20160131.zip - 3g is not working (no sim )

4. aosp-6.0-p4-20160201.zip -3g is not working (no sim )

Can be corrected? Thank you!
[Galaxy Tab 10.1 Android Development] rtiangha:
I no longer have a data sim to stick into this, but yeah, I just noticed that Baseband under Settings->About reads as "Unknown." Over on the Lollipop rom, it was the exact same thing for people who had sim issues over there. The working 3G roms correctly listed the baseband in that section.
[Galaxy Tab 10.1 Android Development] Vitlll:
Sorry for my English. I use a translator.

In Lollipop rom 3g worked only in early versions.

If I am not mistaken, last working ROM with 3g there was aosp - 5.1.1 - p4 - 20150628.zip

In all subsequent ROM - 3g did not work! (SIM card Unknown)
[Galaxy Tab 10.1 Android Development] rmvw:
I have a problem with this rom on my p7500, when i try to download something the standard browser stopt and i am back on the homescreen,

When i use dolphin browser it does not complete the download, this happened with all the 6.0 versions even the latest.

Nothing else installed just flash the rom gapps and su
[Galaxy Tab 10.1 Android Development] decatf:
Weird stuff happened with the recent p4 builds which I can't explain. Some binaries are not running and not throwing any error message either. That is why 3g is not working. It's also probably why some people have crashes and reboots.

I will have to do a complete recompile.
[Galaxy Tab 10.1 Android Development] baahst:
I used twrp2870-20160202b-p4tmo.zip to flash aosp-6.0-p4tmo-20160201.zip

1. 3g is not working (no sim ), says "unknown" under Baseband

2. Can't get into recovery even with hardware keys.

3. Browser stops and returns to homescreen when i attempt to download anything.

4. Which of the GApps is suitable for the p4tmo? Platform and Variant, please?
[Galaxy Tab 10.1 Android Development] Vitlll:
For me 3G is very necessary. That is why I use aosp-6.0-p4-20151211.zip but I want to get all of the latest fixes. I wait and hope! Thanks to all, especially to dear decatf.
[Galaxy Tab 10.1 Android Development] rtiangha:
I was in the same boat regarding the recovery, but I have no idea how I got out of it (probably black magic). Try flashing the b version of this TWRP using Odin and see if that works. If not, you could try replicating my path: I had the Multirom TWRP installed and used that to flash the zip version of the b version of this TWRP. That was what worked for me.

EDIT: Actually, I just noticed that this TWRP has slightly different settings than the older TWRP. Maybe try deleting the TWRP directory in /sdcard and then see if you can access recovery then. No idea if that will work, but if we're talking black magic here, who knows. Maybe it's worth trying.
[Galaxy Tab 10.1 Android Development] rtiangha:
dcatf, just curious, but when you said that you had to replace symbols to get the blobs to work, was it similar to this method:

http://dmitry.gr/index.php?proj=04. Android M on Grouper&r=06. Thoughts#cool_hacks
[Galaxy Tab 10.1 Android Development] decatf:
Yes, that is more or less the preferred method in Marshmallow.
[Galaxy Tab 10.1 Android Development] baahst:
As suggested, I "odined" the tar image and was able to access recovery again but 3g wasnt working.

I have returned to Decatf's Lp because for me 3g is vital. I hope I will have the opportunity to use M with all its functionalities in the very near future.

decatf, thanks for all your work to make our tab still useful.

Strangely, I could not access my storage via PC when I flashed M. But able to do so again since I returned to lp.
[Galaxy Tab 10.1 Android Development] mst_mugen:
Many thanks for the ROM! It appears to work smoothly!! Only problem is that I can't seem to install SuperSU from the link you provided.

I tried to flash it with TWRP and once the installation process reaches the "boot image patcher" section, it says "Boot image: not found, aborting". Where have I gone wrong?

Any help would be much appreciated! :)

EDIT: Sorry, forgot to mention that I have the P4 (3G + WIFI) version. I have also installed "Nano Gapps" and the TWRP is also from the link provided in the first post. Hope I have given enough information.
[Galaxy Tab 10.1 Android Development] rtiangha:
You probably downloaded the newer systemless root version that was recently released. Those ones don't seem to work with this rom. Try to track down a copy of version 2.52.
[Galaxy Tab 10.1 Android Development] mst_mugen:
Ok thanks heaps for your reply, I will try to look for it right now :good::good::good:

---------- Post added at 11:34 PM ---------- Previous post was at 11:24 PM ----------

Ok, I have managed to track down and install SuperSU 2.52 and unfortunately when I go to open the app, I get the error message "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"

I installed SuperSU via an .apk file.

Any suggestions?
[Galaxy Tab 10.1 Android Development] rtiangha:
Sorry; find a *flashable zip* of 2.52.
[Galaxy Tab 10.1 Android Development] UncleDick:
Any suggestions on where to look for a 2.52 zip file? I have the same issue that the latest 2.67 SuperSU doesn't install with TWRP.

Thanks
[Galaxy Tab 10.1 Android Development] spamam1:
SuperSU 2.52; and PC-to-Marshmallow

from chainfire site

https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip

===

in MM, by default when you connect,

even if you 'see' the device, cannot see internal memory

by default'; "charge only"

user must unlock screen (if needed), pull down the USB connection,

and select (paraphrase) "File access"; until then, no access to memory;

and also, can NOT change the default (for security, i guess).

if there's a way to change the default, hopefully someone will post;

I didn't try for too long.. just assumed that it's "by design" for security

cheers

and change
[Galaxy Tab 10.1 Android Development] UncleDick:
Thanks, spamam1. Works perfectly. Embarrassed that I did not find it myself.

Noticed that TWRP 3.0 is about to release. One of the changes is that with Marshmallow, TWRP will no longer offer to install SuperSU. That was my experience with 2.65 and 2.67 as well.
[Galaxy Tab 10.1 Android Development] mst_mugen:
Worked at treat, thanks heaps guys! :)

---------- Post added at 11:55 AM ---------- Previous post was at 11:54 AM ----------

Worked a treat, thanks heaps guys! :)
[Galaxy Tab 10.1 Android Development] suprimos:
hey guys...

i cant root

i did all the steps:

Backup all data

Install TWRP 2.8.7.0

Wipe cache, dalvik cache, system, data

Install the ROM

Install gapps

Install SuperSU

Boot the ROM

Enable on screen keyboard by toggling "Show input method"

But i always get an error while trying to install supersu: no rom found ?

i read something about a boot.img ?

______________________

ok it worked with old supersu ...thx
[Galaxy Tab 10.1 Android Development] jaibar:
twrp 2.8.7.0 from op looks pretty much like twrp 3.0, and I don't recall it asking whether to flash SuperSU, but maybe I wasn't paying attention as I got used to automatically ignore it...
[Galaxy Tab 10.1 Android Development] grej:
Why after clean install of this ROM on P4 build-in keyboard doesn't work? Taping on input field should bring AOSP keyboard, but all I get is just small bar with two labels on right (CAPS and ALT).
[Galaxy Tab 10.1 Android Development] rtiangha:
Try number 7 in the installation instructions in the OP.
[Galaxy Tab 10.1 Android Development] decatf:
Build 20160207

Contains the February security patches.

I haven't come across any weird crashes. The RIL services are running. So maybe 3G is working now...

TWRP-3.0.0-0 is also posted. The previous build of 2.8.7.0 was only a few commits away from the 3.0.0.0 release anyways.
[Galaxy Tab 10.1 Android Development] mistersixt:
Thanks so much decatf, I've flashed TWRP 3.0 via TWRP 2.7.1.0, rebooted into recovery once more, installed latest version 20160207, bootet, and did not find any issues after 2 hours usage (don't have a SIM card available, so cannot check the mobile data thing right now on my p4).

Kind regards, mistersixt.
[Galaxy Tab 10.1 Android Development] grej:
I did enable keyboard in input method dialog, but it doesn't work. I'll try new version of ROM and get back to forum to report if this problem remains in new build.
[Galaxy Tab 10.1 Android Development] donjuan10:
The 3G is working, thanks Decatf :)
[Galaxy Tab 10.1 Android Development] MSTRoyal:
Problems with xposed

Hi everyone,

I can't get xposed to work...

i've tried v79 api 23 but it says not enough free space

And with v80 twrp says gzip:short

Anyone who has an idea whats wrong?

Btw tried with multirom twrp 2.8.x and twrp 3.0 both gave the same errors
[Galaxy Tab 10.1 Android Development] jaibar:
It tells you that the problem is not enough space. So why don't you try to free some space?

There are dozens of ways to free space in system partition. Just use titanium backup to uninstall some system apps that you can install from post store anyway.

After you have some 25MB free, try again v80 works fine.
[Galaxy Tab 10.1 Android Development] rmvw:
Still can not download anything with the new version and clean installinstall (P4)

Browser stopt and return to the homepage
[Galaxy Tab 10.1 Android Development] MSTRoyal:
Sounds logik /facepalm/:silly:
[Galaxy Tab 10.1 Android Development] rtiangha:
Yeah, I get the same thing on the p4tmo rom. I started fresh and wanted to download f-droid, but the stock browser would crash as soon as any download started. I used ADB to copy over the installer instead. I tried side loading a few other browsers too; Inbrowser *sometimes* complains about not being able to access internal storage when starting a download, but Firefox seems fine. I think it might have to do with how /sdcard is mounted now. I've noticed when using the Amaze file browser that going to /sdcard using the shortcut menu on the left goes to a directory with a file that just has a file named 'sdcard,' using the Download shortcut goes to /storage/emulated/0/Download, and navigating to / and then to /sdcard sends me to /storage/safe/primary. I can't even use Syslog to grab log files since it throws an error when it tries to save the logs and after playing around with a few apps, I also get some random errors about not being able to access internal storage (sometimes it works trying a second time, but most times it doesn't). It doesn't happen with every app, though. It's either that or it could be a problem with F2FS??

I'm going to try a different logger from f-droid to see if I can at least pull something.

EDIT: Here what I was able to get using Catlog. I tried downloading a file using the stock browser three times. I also get a crash when accessing Settings->About->Status (and I tried doing it without Xposed and got the same thing), so that's probably in the log as well.

https://app.box.com/s/ml8iif3okkw3vclqcagcffcfm1lx0erk
[Galaxy Tab 10.1 Android Development] decatf:
Enable storage permissions for the Browser app in Settings. App Ops is enabled and part of stock Android in Marshmallow. I don't know why Browser has those permissions disabled by default. You might need to check that for other misbehaving apps to.

Google changed the way the storage system works in Marshmallow. For other problems with storage, it might be that the device is not configured right. I have used the Nexus devices as a reference. It might be that some apps need to be updated for Marshmallow.

The crash in Settings>About>Status is related to SELinux. The proprietary graphics blobs were compiled in a way that has some security issues. There is some part of the cellular subsystem that wants to access a graphics blob when viewing the status page. This is restricted by the SELinux rules.

So to get around that we'd have to poke holes in the SELinux rules to allow it. I don't think it's worth it to do so since it's only to look at that Status page. You can set SELinux to permissive temporarily to view the Status page.
[Galaxy Tab 10.1 Android Development] rtiangha:
That would explain a few things. OK, no worries about the SELiniux part; I wanted to get the device IP so I could FTP the log over to my PC before I remembered that Primitive FTPD posts the IP when you run it.

I guess I'll comb through various apps in App Ops and double check that storage setting for the apps I noticed issues with. Thanks for the hints.
[Galaxy Tab 10.1 Android Development] rmvw:
I now have enable the storage permission in the browser app, download works.

Thank you
[Galaxy Tab 10.1 Android Development] DanielWEWO:
Does anybody know if this ROM will run on SCH-I905? If not, does anybody know of any ROMs still working for that device?
[Galaxy Tab 10.1 Android Development] decatf:
It does not work with the Verizon tablet. This one is quite different than the other tablets so there is no way for me to test it.
[Galaxy Tab 10.1 Android Development] UncleDick:
Google App Force Close?

I saw one comment earlier about the Google App "closing sometimes." In my case, the Google App closes in about four seconds EVERY time it is opened.

I turned on ALL permissions, both for the Google App and for Browser (although I personally use Chrome).

No change. Google App still closes within seconds after being opened.

In addition, several times I have had Feedly open for a while and suddenly a box pops up saying, "Unfortunately, Google App has closed." WTF? I didn't open it, why would it have to close?

Does this happen to anyone besides me?

Any thoughts on a cure?
[T-Mobile Samsung Galaxy Note 3] pogotv:
Brain Truss..

I have looked at all the offerings in the development section, and I am wondering is there any development based on a port of an actual Tmobil Note 5 and not one of the international NOTE 5's ...

Many Thanks As Always

:cyclops:
[T-Mobile Samsung Galaxy Note 3] tazfye:
I haven't been able to find any. I'm anxious to see if anyone is taking on the task of porting the mm 6.0 that was uploaded recently from a t-mobile note 5
[Android Auto General] dcdttu:
I ordered a DDX9702S and installed it in my '09 Civic Si. I've got a Nexus 6P and have been experiencing odd audio glitches.

When I play music, everything is fine until I get an audible notification or use the Voice Search. After that there is an audible buzzing/frying noise in the tweeters of my stereo when a bassy note hits. Once the noise starts, it doesn't stop until I reboot my head unit. Could you see if you have the same problem? I don't know whether it's Android Auto in general, my Kenwood stereo, or what. I've also reproduced the issue with 2 other Nexus 6P's and a Nexus 5, so I know it's not just my phone or model. Can anyone with the same head unit with me test out the scenario below and let me know if they've also got static? (I'm on the latest firmware, btw, from Kenwood's site)

Steps to reproduce:

App to use:

Either Google Play Music All Access or Spotify

Song to use:

Rearrange by Vérité - the beginning of the song is quiet with a bassy beat, making it easy to spot the distortion / static.

Steps:

Turn on the head unit and plug in your phone (I used a Nexus 6P and a Nexus 5)

Once Android Auto is running, go to your music app and play Rearrange by Vérité. I find its easier to play the song if you add it to a playlist titled "1" (without the quotes) first, so it's at the top of your playlists.

You'll notice that the beginning of the song is quiet with a bassy beat. After about 10 seconds, hit the microphone in the top right of the screen to activate the Google Now Voice feature. Once it gives an audible beep, hit the microphone button again to cancel.

Hit back on the screen to start the song over. At this point, on my stereo, every bassy beat is accompanied by a static in the tweeters of my stereo. This happens on every song I play, even the radio, but it's much easier to hear on quiet songs like the one I gave as a suggestion to test with.

The static continues even if you disconnect/reconnect the phone. The only think that stops it is restarting the head unit by turning it off and back on. If you use Google Now again or a notification comes in and makes an audible sound, the static will come back. It seems, to me, that any notifications or audio playback from an Android device will cause the head unit to distort the sound until the head unit is rebooted. If nothing happens to cause the distortion, sound quality is stellar.
[Android Auto General] Porntep02:
Either Google Play Music All Access or Spotify
[Android Auto General] dcdttu:
Not sure what you mean, but I can reproduce the problem in Google Play Music or Spotify. Actually, the FM radio too, but it's hard to hear unless you know what you're listening for - then you can't unhear it.
[YU Yuphoria] hariraj96:
hi guys,

can someone upload the eleven music apk from cm 12.1 zip ? the apk size differs for diff phones..... plz upload it:cowboy:
[YU Yuphoria] Irfan.K:
http://xdaforums.com/attachment.php?attachmentid=3438618&d=1439536945

Use this link to download tha music app of cm 12.1[emoji1]
[YU Yuphoria] Chintu57:
Is it compatable for CM13.0 ???
[YU Yuphoria] anil18:
It shows flashing successful but not showing after reboot

I have tried to flash it says flashing successful, bht after reboot the application is not showing in the menu nothing flashed..

Can anyone please help me in this.. :)
[YU Yuphoria] itsallaboutu007:
anybody got the cm13 version ?