yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] Wachicamo:
P6210 report.

Apps keep crashing after 10 mins of usage.

Random ROM freeze.

Screen flickering (known issue).

Videos that are shown in Feedly, says that " videos are unable to watch or unknown error ". If you try to open the video directly to the browser, it crashes.

Random Reboots. It could take minutes or hours to reboot automatically.

It feels a bit faster than Omni, but it crashes more often.

You are almost there, Daniel.

Keep it up the good work.

Regards.
[Galaxy Tab 7.7 Android Development] F R Harris:
Using OMNI lateat build for P6200 clean install,

DT2W working, when accessing the advanced sub menu it FC twice before able to tick the DT2W box. System are smoother than the previous build, and haven't got any random boot yet (i've just booted up, install several apps, then write this) which happens on older OMNI builds after boot and installing apps. Data ok, phone ok. Thanks Daniel

PS: 3minit battery work, omni seems stable, no random reboot until now, wonderful rom, thank you
[Galaxy Tab 7.7 Android Development] daniel_hk:
Still struggling in a job therefore I can't sleep at 2:30 :(

Your message reminds me a break. Glad to know that DT2W works for Tab-plus. It's a good news for my misery week. :D

I don't know why there were FC if you have clean flash (factory reset or wipe data)? I'll test it later.

I don't have problem with battery icon.

Anyway, you may try the 3Minit battery icon mentioned in Q&A of post#2 for the time being.

I need to return to my work now.

Good luck!
[Galaxy Tab 7.7 Android Development] Abort Retry Fail?:
File Transfer Woes

The good news is that you've done your usual great job in keeping our tabs alive and well. I've got 20160115-i815 Omni flashed and working well with the kernel that was posted with the F2FS patch. (F2FS working great with /data and /cache.) All is wonderful except for a peculiar, intermittent problem with the MTP setting in USB configuration. I'm running Windows 10, and Explorer will recognize the tab after toggling MTP in Developer's Options. I have no problem transferring file from my Windows machine to the tab, but transfers the other way sometimes hang for no reason I can determine. Device Manager says the SCH-I815 is working properly, and I have the latest Samsung driver installed for it - 2.9.317.215, dated 2/16/2012. Not all transfers from the tab to the Windows machine fail; what seems to cause the most problems is trying to send my TWRP backups. As you might expect, they tend to be large (about 1.8 GB for my Omni configuration) and most of the transfers get stuck about halfway through when Explorer freezes. Any suggestions or advice would be gratefully appreciated; transferring files that size via Google Drive is a very cumbersome alternative.
[Galaxy Tab 7.7 Android Development] daniel_hk:
I have only tried sending to Windows 7 and 8 briefly not 10. I don't recall any problem. Recently I have backup the whole content of the sdcard (~8G) to my Linux PC. It took hours and 3 retries but didn't hang. I'm.mostly on Linux now so I can't tell you much.

I can only assume it is the Win10 side.

Anyway, the latest Omni (0204) was released yesterday. You may give another shot with the new one.

By the way, have you tried the data connection in your i815? We don't have Verizon locally, no way to test.

Good luck.
[Galaxy Tab 7.7 Android Development] Abort Retry Fail?:
Many thanks for the speedy reply. I tried removing the i815 via the Win 10 Device Manager and reinstalling it, but I got the same result. Curiously, upon re-installation Device Manager showed a Microsoft driver for the i815. After the large file transfers continued to hang with that driver (small files move perfectly) I told Device Manager to update the driver and lo and behold it reinstalled the Samsung driver. Same result. I agree with your suspicion about Win 10. I'll try your suggestion with the latest Omni build and see what happens. FYI, I had data and cache both formatted F2FS before flashing the 20160115 build of Omni and found to me surprise that the format of cache had been changed to ext4. No problem; I just reformatted it to F2FS.

I wish I could tell you about the data connection but I dropped my Verizon contract some time ago. My i815 is now a fine tablet without any data connection or SIM card.
[Galaxy Tab 7.7 Android Development] Abort Retry Fail?:
Success!

Daniel,

You are, as always, sir, a genius. Just flashed the 20160204 Omni on my i815 and my file transfer problem has been solved. I just copied a 1.8 GB TWRP backup of the 20160115 Omni build to my Windows 10 machine. If anyone else has similar problems with transferring large files via MTP I'd urge them to try the 0204 build.

Thank you again for your great work. FYI, in flashing the 0204 build I discovered how my cache partition came to lose its F2FS format. In performing the factory reset in TWRP before flashing the ROM I noticed that TWRP formatted the cache partition as ext4. So that mystery was also solved.
[Galaxy Tab 7.7 Android Development] daniel_hk:
Normally it won't happen. You may try again. Wipe the cache will keep the existing format.

The kernel in 0115 build didn't have F2FS support. Upon start, the system would prompt you to do a factory reset when the /cache and/or /data can't be mounted. If you reply yes, it would reboot to recovery and format your cache to the default Ext4 format. The internal sdcard is inside /data. Wipe data won't format the partition, only delete the files in /data. That's why /data partition is preserved. Reboot would repeat the above procedure until /data is formated to the format which the kernel support. Or when you replaced the kernel.
[Galaxy Tab 7.7 Android Development] philipnzw:
Friend and I were literally just talking about how both our devices dont have double tap to wake, his is a redmi note I think

Well, now we have it muahaha

Tested and working perfectly on p6800

Thx Daniel and happy Chinese new year to all celebrating
[Galaxy Tab 7.7 Android Development] Wachicamo:
P6210 with latest Omni:

This is, by far, the most stable rom.

Downsides:

Double Tap To Wake: Works randomly and it will freeze the Tab.

Screenlock: Sometimes, the screen has a glitch that show half of the screen black. To fix it, you have to turn off and rotate the Tab to another direction.

I don't have any freeze so far. Those who have this Tab, should install it.

Thank you, Daniel! Keep it up the good work!

Regards.
[Galaxy Tab 7.7 Android Development] Abort Retry Fail?:
Thank you helping me understand what was going on behind the curtain. Now I could certainly use some advice on user control with Omni. For some reason Omni has no "Users" setting unlike other MM ROMs. And I have somehow lost Developers Options, which became "not available for this user" since I posted the message above. (This loss of access extends to all the TWRP backups I've restored.) Other MM ROMs give you access to user profiles from the Quick Settings on the status bar, but the Profile/User button on Omni's status bar is dead. What have I done, and can I fix it without reflashing 0204?
[Galaxy Tab 7.7 Android Development] Abort Retry Fail?:
Mea Culpa

Thank you for your kind patience in helping someone who apparently screwed something up to undo the mischief I created. I had tried your suggestions before you were kind enough to post them, but hitting "Build" in About Tablet did nothing. The Developers Options setting appears, but when I tap it the screen simply says "Developers Options not available for this user." (They were certainly available yesterday when I toggled USB configuration so I could successfully test the MTP transfer effectiveness of the 0204 build.) Regarding the User button in Quick Settings, when I tap it I expect to get a dialogue box with options to select a user, add a guest, or add another user. (There are the options I get from MM on my smart phone, which is a rooted LG G3.) "Dead" was probably not the best word to use to describe the absence of these expected options. Tapping that button in Omni only brings up me as the user with no option to change users or add new ones. I Googled the problem of the unavailability of Developers Options and all the solutions I found involved changing the tablet's user, which I for some reason seem to be unable to do in the 0204 build.

At the end of the day it is not a great problem. If nothing works, I'll just flash the 0204 build again and invest an hour or two in installing the system. FYI, I have flashed xposed-v80-sdk23-arm.zip and installed XposedInstaller_3.0_alpha4.apk plus a few modules, but I don't think these could have wiped out my Developers Options.
[Galaxy Tab 7.7 Android Development] Mrxyzl:
Tab stay awake

When enable dt2w on. P6810, tab staying awake? Here is the screen shot
[Galaxy Tab 7.7 Android Development] daniel_hk:
What figure in your screen shot make you think that?

I didn't put any wake lock to the touch screen driver.

Obviously, the power of the touch screen can't be cut to accept actions. I started an interrupt watch when receiving a suspend from the system. Whenever the screen is touched, it would track the action. If the touch screen is continuously activated (eg. put in the bag while we are walking), it would look that way but for the touch screen only. Other drivers would behave as before.

The touch screen with cpu wake drawn <50 mA according to Samsung's spec. which is <8% of the screen at full. Our battery is 5100mAh. That means ~ 8hrs. of screen at full. That is >100hrs. if you continuously tap the screen at suspend without waking it up. Of course, there are other consumptions.

Actually in my Nexus7, a deep deep sleep would cause DT2W fail. I can add a wake lock in Nexus7 but seems not worth.

It definitely consume power but doesn't wake the system up if the taps are not within the bound in the pre-set duration.

You can always turn it off if you think it drain your tab. ;)
[Galaxy Tab 7.7 Android Development] Mrxyzl:
Well, the tab was keep awake at 95% at first, then i disable the DT2W and the awake time decrease as in the screenshot. Most of the keep awake is from the kernel .

maybe it was due to dirty flash, i'll try a clean flash again.
[Galaxy Tab 7.7 Android Development] daniel_hk:
I don't think a clean flash would help much.

So this is the screen shot after it's off. Can you attach both screen shot for before and after?

Better with the kmsg too. It would be easier to compare and figure out why. ;)
[Galaxy Tab 7.7 Android Development] thogamer:
I still have a little problem with the build. I can play videos but I can't forward them (so I can't forexample start playing a video at 03:12 but I have to start from 00:00).

I have this problem with the latets omni and DU build. I'm using a p6210.
[Galaxy Tab 7.7 Android Development] Mrxyzl:
How can i get a kmsg? I tried cat /proc/last_kmsg > /sdcard/kmsg.txt on terminal and get no such directory :(

Here is the dmesg and screenshot when I left the tab overnight

And BTW, the last is the screen shot of lockscreen bug some one mentioned above. Step to reproduce:

1. set auto rotate on and lock it at landscape rotation

2. Reboot

3. Afterboot, the tab will be like in the screenshot
[Galaxy Tab 7.7 Android Development] galoneta:
Daniel,

Latest omni is fast on my p6210: the fastest of MM roms tested so far.

Still many reboots specially when installing some apks with total comander from external sdcard.

Rotation bug even on boot is there: "omni" boot screen is displaced on forced reboots.

Camera ratio is wrong, picture is visible but image proportion is not right.

Gallery has no preview of camera video and photo.

Open camera and quickpick solves this all!

A little more stability and this rom will be the best for sure!

Thanks
[Galaxy Tab 7.7 Android Development] Grigoriy60:
Hi Daniel!

Unfortunately can't flash neither OmniROM nor CM...

Tried to do it in TWRP recovery and in CWM recovery.

The result is the same.

What's wrong? Thank you in advance for any advises.
[Galaxy Tab 7.7 Android Development] daniel_hk:
I don't want to embarrass you but clearly, you didn't try TWRP... :(

Most of the people think excuses are the easiest way to get anything. But sadly, a lie is a lie. Simply not worth... :(

This is the last day of a lunar year. I hope everyone could have a new start and be a better himself. This is truly from the bottom of my heart. :)

How to flash is in post#2.

Good luck.
[Galaxy Tab 7.7 Android Development] Grigoriy60:
You say I'm a liar? I've read the posts first of all and use TWRP to flash. But had no result. And after that tried to flash in CWM recovery. The error messages from both recoveries were absolutely the same. I attached the pic of CWM cause haven't one of TWRP. I can repeat the process with TWRP and show u the pic.

Please be accurate with word 'lie'.

Thx for ur advises.
[Galaxy Tab 7.7 Android Development] ktinus:
report on p6200

I did almost the same for p6200 ("odin download mode" says p6201) and finished with success! Thank you very much for this great work.

In detail: I used TWRP 2.8.7.3-p6200.img. Before flashing I wiped cache/dalvik cache and system (because I had different customROMs installed before). Then I followed the order of galoneta except gapps: cm-13.0-20160122-UNOFFICIAL-p6200.zip +cm-13.0boot-20160202-p6200.img +SuperSU-v2.56-20151030013730.zip

wiping cache/dalvik after each step

(it was little time consuming to find BETA-SuperSU-v2.56-20151030013730.zip - to make it easier for others: it's here)

So far WLAN and bluetooth keyboard work. SIM was recognized. Screen flickering is there - I think this is stronger when pushing the "back" button of the menue but it is smoother when using the back button inside an app. In total: GREAT ROM!
[Galaxy Tab 7.7 Android Development] galoneta:
Daniel,

Just reporting my experience as I do in 5.1.1 carbon right now: not "asking for stability" in future builds. I know this depends on Android sources as well!

Thanks again for your brilhant work for our tabs!
[Galaxy Tab 7.7 Android Development] tonygamble:
I'm very new around here ktinus.

Why did you flash the kernel?

I have never been guided to do so.

Tony

London UK
[Galaxy Tab 7.7 Android Development] daniel_hk:
This is because the last cm-13.0 for Tab plus fail to boot. I don't have a Tab plus so I didn't know. After someone report the failure, I rebuilt the kernel which is only for them.

FYR, Tab plus (p6200,p6210 & t869) are almost identical to our Tab 7.7 (p6800,p6810&i815). The major difference are the display resolution (1024x600) and with a 1.2Ghz CPU.
[Galaxy Tab 7.7 Android Development] tonygamble:
Thanks Daniel,

So, as my kernel seems to work, it not something I need to be considering?

Tony
[Galaxy Tab 7.7 Android Development] ptrekcostales:
Hi,newbie here. I want also to try this update but don't know where should I start. Thanks in advance for the help. :)
[Galaxy Tab 7.7 Android Development] daniel_hk:
Sure. It's for tab plus only.

Read post#2 first. It should be enough for you start with.

For the full picture, read all the posts in the thread.

If you don't know how to flash, search your local forums first.

Good luck!
[Galaxy Tab 7.7 Android Development] ptrekcostales:
Thank you very much Daniel! Just want also to make some changes on my Tab.
[Galaxy Tab 7.7 Android Development] flogs:
Bluetooth speaker - not usable

Tab 7.0 Plus P6200 + cm-20160122. With the fix, boot is OK. Screen sometimes flickering. Tablet is unable to hold bluetooth connection to an external bluetooth audio speaker. Error after a couple of seconds and bluetooth disconnects. :(
[Galaxy Tab 7.7 Android Development] Alvin Owen:
youtube crashes.. help?
[Galaxy Tab 7.7 Android Development] Cluey:
The only way you could have made that more useless would be saying something like, "it crashed."

You need to read what Daniel has written in the last few pages. If you want to help fix the problem you need to provide more information.

From what you've written we don't even know which tab you're using, this thread is covering a few now.
[Galaxy Tab 7.7 Android Development] Alvin Owen:
Eventually i reinstall youtube on my p6200 and it was working fine again
[Galaxy Tab 7.7 Android Development] juniorhxcx:
Daniel, good morning!

First thank you for keeping our living devices.

I have a question, for me to install the Android 6.0 (CM, Omni, etc ...), the P6210 Tab Plus I need to perform a PIT file (mandatory)?

If so, you can post me a link to download the right file please!

Thank you!
[Galaxy Tab 7.7 Android Development] Kholargol:
Hello, I flashed my Dad's P6810 to CM13 (january release) and I was surprised by the slowness of disk operations on Internal SD. ROM flash was very slow (like several minutes)

After a day of use, I launched a trim on data, cache and system and it was very slow to proceed (90 seconds)

Is it normal because the table starts to get old or do you think there is a technical problem behind this. I don't know how to investigate furthermore..
[Galaxy Tab 7.7 Android Development] daniel_hk:
I don't know why you asked?

PIT is ONLY required if there is something wrong in flashing (ie. a corrupted partition table) OR if you want to reconfigure the sizes of the partitions (ONLY for advanced users who know how).

Most people might never use it.

Flashing is normal. This is because some of the 7.7 and all tab-plus don't support block mode (something like disk image restore) so I need to use the non-block mode. The post flash actions would take a few minutes for symbols linking and setting permissions. Therefore it might be up to 5-10 minutes to flash a large ROM(approaching 300M now) like CM13.

I don't know why you need to trim cache and system. /cache is a small partition. It always requires a wipe (formatted) after flashing. /system is a read only partition. The data is always packed (~trimmed) while writing.

The only reasonable partition would be /data. Since KK, the /data (and /cache) partition is trimmed automatically. The scheduling of trimming is further fine tuned in early LP. Usually it is done automatically when idled for a period of time after each reboot. It is compulsorily done if trimming was not finished for a few attempts.

It might only help for those heavily use situations when the tab is continuously use until dry up after each reboots.

Hoping these clarify something for you. ;)
[Galaxy Tab 7.7 Android Development] aemee:
Trying out the Feb 4th update for Omni6. Wiped everything and flashed only the rom, pico gapps and supersu.

Finally, browsing with Dolphin is working. Jetpack works as intended which is a huge deal for me and probably the main reason I held on to my P6800.

I have a few reports followed by some questions.

Screen rotation when locked, may cause some rendering issues after a reboot. Usually when reboot is caused by low memory or a manual reboot from hangups.

For example, if locked in landscape, the device will reboot and display the lock screen in portrait but only the top half is rendered/shown. This really isn't much of a problem except that any user input is recognized as being in the landscape mode. Not sure if anyone gets it but to put simply, it shows up as portrait but it thinks its still in landscape mode. It takes a couple tries to unlock with a PIN or password though.

The same occurring problem of low memory reboots still present. Honestly I am not sure why this happens on a freshly flashed rom with pretty much nothing extra installed and with settings still in default. I just find it weird and think its worth mentioning that for some reason, reboots still happen out of the blue.

On to the questions, is it necessary for me to flash the additional fixes from the past? Like the rotation fix/ril patch etc. I used to do that but for this update, I was on mobile and did not have the time to scroll through 30 pages to look for the fixes so I just flashed rom-gapps-supersu.

Just wondering if doing it the simple and lazy way is making me and others miss out on some functionality.

Oh and Tap2Wake?

Awesome. Even with default settings I do not get any accidental wakes when kept in pocket or bag. It was nice to be able to lock without using the power button. But it is very nifty to be able to unlock without touching a button. Would probably save the buttons life a few but I think not many would think of that.

As always, thank you for the great and consistent updates. Cannot wait for your SlimRoms ^^
[Galaxy Tab 7.7 Android Development] juniorhxcx:
Very thanks!

Enviado de meu C6503 usando Tapatalk
[Galaxy Tab 7.7 Android Development] daniel_hk:
1. I'm not sure if Dolphin use webview. If yes, this is another Gapps issues. In any case, a log might give us a clearer picture.

2. I've already mentioned sceen rotation a few post above. In short, I have included the persist.panel.orientation support to turn our landscape default tab to portrait. It would recover itself when the orientation sensor is activated (just pick it put from the flat table top). You may search for my posts for detail.

3. If I attached a patch, I would add a note in post#1 although I might forgot occasionally....
[Galaxy Tab 7.7 Android Development] galoneta:
Daniel,

Flashed with new twrp 3.0 : cm-13.0-20160210-UNOFFICIAL-p6210.zip + BETA-SuperSU-v2.52.zip + open_gapps-arm-6.0-pico-20160211.zip and reboot: runs fine.

Camera now has the right propodtions for photo and video. Gallery preview has distortion for photo only.

This build has a lot more stability than previous builds and speed is very good! Screen flickering is there!

Installed a lot of my usual apks and all fine, no reboots like previojs builds.

Thanks again. Tell me if you need specific tests.
[Galaxy Tab 7.7 Android Development] Kholargol:
Yes, it's clear now. And I trimmed everything because I'm not an expert, that's all! Thanks..
[Galaxy Tab 7.7 Android Development] daniel_hk:
I don't know what's wrong with you? Why edit my reply and twisting my words? What is your agenda?

The first line is for the other question from the other one who asking about PIT. Clearly, that part was deliberately deleted.

I read my answer again. I can't find a single offensive word. I was thinking everyone want to learn the truth, not blindly believed. Am I wrong?

I don't think any parent, teacher and country would teach their children that way. Am I wrong?
[Galaxy Tab 7.7 Android Development] aemee:
Dolphin related, I was just simply happy because in the previous Omni builds, I cannot even stream html5 videos with Jetpack enabled. It seems to be working this time around. Wanted to express my gratitude is all.

I read your post on the screen rotation. Apologies for not reading it beforehand.

But I am not sure if its related to whats affecting me.

This is what I did to reproduce the bug, lock the screen in landscape and manually reboot. The tab will now draw the top half of the screen in portrait but only takes input as landscape which is the rotation that it is locked on. Imagine the tablet standing up in portrait, now if i were to slide up to unlock like you would if it was portrait, nothing happens. If I were to slide left as if I was in landscape, then it would unlock. So if locked on landscape, sliding left to right = sliding down to up.

I will try to upload an image later on when I manage to get the XDA app reinstalled otherwise I just seem like a rambling idiot trying to convince everyone that math is evil.

EDIT:

For some reason I cannot upload the image from my pc nor an online image hosting site. Weird. But I did managed to stumble across a way to reorient the display from the lockscreen. Tapping on "Emergency Call" forces the tab to redraw the keypad in portrait every single time and if you tap on back afterwards, the screen will be redrawn to its locked position be it landscape, reverse landscape or reverse portrait.