yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] prisoner881:
I tried grabbing old OpenGapps but it did no good. I went with Jan 20, 2016 and that didn't work. I went with mid-December 2015 and that didn't work. I went with early November 2015 and that didn't work. If you've got a Gapps that works with the latest Dirty Unicorn build then I'd love to get a copy of it or know where I can download it myself. I've tried OmniROM, DU, and Cyanogen 6.0.1 and they all fail exactly the same way. The ROM works fine until you add Gapps and then everything crashes.

I've never had this with any other Android device (and I've got plenty) so I'm thoroughly confused. This is all being flashed from TWRP 3.0.0.2 after doing a COMPLETE wipe of the all partitions, including the MicroSD, then copying the ROM files to the MicroSD, then flashing from there. I do a full boot into the ROM, then reboot to recovery, then flash Gapps. If this is the wrong procedure please somebody say something.
[Galaxy Tab 7.7 Android Development] aemee:
Therein lies my problem.

My cable is charge only and I have been using a card reader to transfer anything between the tab and pc. I have various reasons for not having a data sync cable on hand at the moment but that is why I requested for help with logging from within apps.

I have tried using a Terminal app but it keeps writing empty log files to my device/sdcard for some reason. Using another logging app simply shows me realtime logs and the ability to save them.

Am I right to assume that making logs right after a reboot is all that is required? For example, I encounter a problem forcing the tablet to reboot. Once booted, using anything I can get my hands on, grab some logs and maybe even kmsg and that should be enough?

I have wiped everything again and flashed only the 7th July DU update with pico gapps. After installing a few apps, I no longer get the WiFi reboot issue anymore.

I plan to flash V4A and slowly reinstall all the apps I require and will manually monitor the tablet to see if any of them are the actual culprit.

Only reboots I get so far are what I assume to be due to low memory as it happens 90% of the time when using the YouTube app.

I would appreciate a clarification on the logging so that the next time something happens, I actually know what to do as googling it mostly tells me how to pull logs and not when. Considering that the tablet usually reboots itself or requires a manual reboot, idk if pulling a log after the reboot actually helps with anything.
[Galaxy Tab 7.7 Android Development] prisoner881:
I've been utterly unable to get Gapps installed on this latest DU build (or any 6.0.1 build for that matter). How did you get around this?
[Galaxy Tab 7.7 Android Development] pokazef:
I didn't, I don't use Gapps.

I download APKs with the "APK Downloader" Firefox extension on my PC and then install them manually on my devices.
[Galaxy Tab 7.7 Android Development] prisoner881:
OK, I accidentally stumbled upon a fix for this. Here's a link to the forum, and I'm pasting the fix instructions below to highlight the relevant portions: http://xdaforums.com/galaxy-tab-7-7/development/rom-android-marshmallow-experimental-t3234388

Q: How to fix SetupWizard crash of Gapps?

A: As the above, It is the security again.

The permissions for SetupWizard are "Dangerous" and disabled.

CLICK TO HIDE CONTENT

Note: For CM with Gapps, there will be two SetupWizards. "com.cyanogenmode.setupwizard" and "com.google.android.setupwizard". The one with the blue CyanogenMod icon is from CM. It's the one comes with Gapps crashed.

1. Just flash ROM (+ SuperSU) only and set up the system first.

2. Then flash Gapps.

If SetupWizard crash after reboot:

Method 1:

3. You can still enter Settings via QS. There will be a short time slot after you press OK in the warning dialogue. A bit tricky but doable.

4. Select "Apps" and select "show system" in the advance menu. (top right)

5. Locate can select SetupWizard.

6. Select "Permissions"

7. Enable "Phone" and "Contacts" will stop the crash.

OR

Method 2:

Your device is rooted and you know how to use adb. Use the following commands:-

Code:

3. adb shell

4. $ su

5. # pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE

The crash will stop immediately.

Q: How to fix Google Play service crashes?

A: Again It's the security. Google Play service requires the permissions

ACCESS_FINE_LOCATION & ACCESS_COARSE_LOCATION.

BUT there is nowhere to set it.

CLICK TO HIDE CONTENT

Only a rooted device with adb can fix it:

Code:

1. adb shell

2. $ su

3. # pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION

4. # pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
[Galaxy Tab 7.7 Android Development] p3dboard:
In order to not get the gapps crash on initial boot of the roms, you have to flash the gapps straight after flashing the rom, before you boot the rom for the first time.

I believe Daniel has a script that runs on first boot to give permissions, but after the first boot it no longer runs.
[Galaxy Tab 7.7 Android Development] juniorhxcx:
I tested the latest Roms Omni and DU.

In both'm having various problems, such as:

system crash;

the unlocking device then locks again;

open drawers open last app from scratch;

suddenly the screen lock and unlock;

Finally the device seems to have a life.
[Galaxy Tab 7.7 Android Development] aemee:
Finally figured out what was causing the tablet to reboot whenever wifi managed to get connected to an AP.

Or at least what I believe to be causing it.

After a week of reboots and crashing, I initially thought it was Google Maps offline area setting that likes to update the maps over wifi whenever connected to one causing it. After uninstalling, still got problems. I thought it was possible to be somewhat related to the "crash when sending files using es explorer" so I disabled all sync.

Still crashed. Out of curiosity, I simply removed my google account.

And no more crashes/reboots related to wifi.

To double check, I readded my google account and as soon as it was done, the tablet reboots.

Did it a couple more times and wifi will always cause a crash or reboot after connecting to an AP with my google account added. I'm thinking that the syncing it does over wifi causes the crash/reboot since I have no problems via 3G. Having wifi on but not connected to an AP makes me think that seems to be the case.

Have tried 3 different pico gapps all with the same result. So if I want to use wifi, all I do is remove my google account and readd it after I'm done.
[Galaxy Tab 7.7 Android Development] p3dboard:
What sort of upload speed do you have on your Wifi - Someone reported that if the upload speed goes over 300kb/sec, then the Wifi connection dies and reboots the device. My home ADSL2 connection has a 128kb/sec upload limit, so only if I do a File Transfer between two devices over Wifi can I get over 300kb/sec. Hence I am thinking your crash is occurring as your exceeding the data transfer rate at which the Wifi driver Bug occurs for upload. Download doesn't have this issue.
[Galaxy Tab 7.7 Android Development] aemee:
I am on a 200Mbps fibre plan so my theoretical Up and Down is about 100Mbps-ish and 200Mbps respectively. Obviously that's impossible.

On average, I get about 20Mbps on my upload speeds via wifi.

I don't see what could possibly be uploading at speeds over 300Kbps from my google account. Even with sync disabled it still crashes me. I'm just astonished that removing my google account is the only remedy that has been working for me for a couple of days now.
[Galaxy Tab 7.7 Android Development] wlhon:
Tried it on the Omni ROM and it is working flawlessly. Thanks.
[Galaxy Tab 7.7 Android Development] camelitos:
Flashing with outdated twrp?

hey, how can i flash it? the newest version of twrp for p6800 is 2.6.3.0 (the tar for the p6800 is empty) and i do not know any other custom recovery who would work on this device (except outdated cwm)

thanks in advance
[Galaxy Tab 7.7 Android Development] uli-hh:
Latest TWRP can be found here:

[Recovery][p6800/p6810/i815] (5Apr2016 TWRP 3.0.2-0) Custom Recoveries
[Galaxy Tab 7.7 Android Development] Harrison Le:
Wow! No words to say how fantastic the newest CM13 on P6800 :

- first impression is battery life, device works smooth fast and seems no heat out much this reason may made battery life longer.

- confirmed wifi off during sleeping but my device have 3G so when wake up I see 3G is connecting then change bk to wifi immediately :)

- one thing more found out just function double tap screen to wake up is active on this Rom, really cool![noticed] this function not be reactive well if device sleeping long sometimes it does sometimes doesn't :)
[Galaxy Tab 7.7 Android Development] tnfn:
No performance menu

Sorry, posted in wrong forum after some google searches led me here...
[Galaxy Tab 7.7 Android Development] gage_zheng:
many thx for your share.

i have issue to install TWRP with your tar file by using odin.

<ID:0/005> Added!!

<ID:0/005> Odin engine v(ID:3.1101)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> SingleDownload.

<ID:0/005> recovery.img

<ID:0/005> NAND Write Start!!

<ID:0/005> FAIL!

<ID:0/005>

<ID:0/005> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

my device is the original docomo sc01e. no bootloader and no way to install img by using adb. could you help to figure out what i can do?
[Galaxy Tab 7.7 Android Development] daniel_hk:
I don't think here is the right place to post your question. There is a thread for Recoveries.

Anyway, I never have a sc01e in hand. Not much can help. I guess its has a different bootloader and use a different PIT. I don't suggest you flash anything not for sc01e. You might brick it.
[Galaxy Tab 7.7 Android Development] gage_zheng:
thank you for your reply. i am trying to upgrade to cm 13.

i installed CWM 6 (which is for p6800) before and it was totally fine. do CWM/TWRP use the same way?
[Galaxy Tab 7.7 Android Development] Harrison Le:
[P6800] CM13_20160729 just flash "Leaked Nexus launcher" seems nicer for ferfomance and without app drawer

https://www.androidfilehost.com/?fid=24588232905722237
[Galaxy Tab 7.7 Android Development] Niticha:
DirtyUnicorns is best ROM for me (P6800) ^^
[Galaxy Tab 7.7 Android Development] Harrison Le:
DU have new awesome animation, cool!
[Galaxy Tab 7.7 Android Development] funpig:
P-6210 upgraded from 4.1.2 to CM 13.0

I own a Galaxy Tab 7.0 plus P-6210 which i had flashed to 4.1.2 almost 3 years ago using odin. It has been very reliable and stable, but I needed to upgrade the OS.

With the help of my techy son, we upgraded to CM 13.0 last night. (We did a nandroid backup first) I flashed the ROM first, factory reset, rebooted and then tried to flash the stock gapps in the second step. I kept getting an error 70 (insufficient partition) when i tried to flash the stock gapps. I was able to flash the pico gapps. After re-booting, i kept getting pop ups saying that the google play services application stopped.

We did some reading, re-wiped. We then flashed the ROM, factory reset and without rebooting, flashed the pico gapps. Then i finally rebooted. No more pop ups. I was able to restore all my apps from google.

There was some minor glitches. All of my 44 apps were re-installed, but i kept having a message that the tab was still installing 13 of 44 apps. After about 30 minutes, I just powered off and the message disappeared. Everything seems to work.

Tiny glitch: I lost the sound on each key press in my keyboard after about half an hour of usage. I just had to power off to get it back. And there may or may not be an odd lag. But my important apps all work.

Thanks to daniel_hk.
[Galaxy Tab 7.7 Android Development] uli-hh:
Thanks a lot for the new release!:good:

Installed the latest DU-10.4 rom on my P6200. No problem with installation (rom & nano open-gapps).

Found out that the "double-tap to wake device" function is a real battery drainer. So I switched it off. Adaptive brightness is somehow delayed.
[Galaxy Tab 7.7 Android Development] funpig:
P-6210 on CM 13.0

Some bugs.

1. Playing web (yahoo) videos on my Boat Browser and the stock browser flicker always very badly, sometimes freezes and then force closes, sometimes reboots.

2. Netflix: sometimes difficulty connecting and unable to play movies. Youtube app worked well so far.

3. screen rotation: sometimes it gets stuck in the landscape mode. have to go into settings menu to un-stick it.

4. Double tap to wake: I believe I experienced a big battery drain over night with this enabled. Also, on my device, when I double tap it goes to sleep and straight to lockscreen. I can double tap but then need to re-enter pin which is not convenient. I just disabled it. Disabling may have helped Tab be smoother and may have reduced the amount of force closes and reboots, but I am not sure.

5. SpeedTest: Whenever I run this app, the Tab freezes during the upload and then reboots. My home wifi downloads at about 16.0 Mbps and uploads at about 3.0 Mpbs. I assume that this has to do with the wifi bug that I read about in the earlier posts. Any fix yet? Otherwise the wifi seems to be very stable. I set my wifi during sleep to "never" and have not had any disconnects or need to re-enter my password.

6. Games: Live Holdem, Clash of Clans, Clash of Lords work, sometimes laggy and force closes. Never had this problem while running 4.1.2.

Having updated it, I have reloaded all my apps and have been playing around with it a lot the last 24 hours.. Probably putting too much stress on the underpowered CPU and memory. IMO, there is added functionality, but it is not faster or smoother than before and is definitely less stable. This is a daily driver for me. I have reloaded all of my apps. So far, the most important ones like Calengoo, Yahoo mail, DropBox still function properly as far as I can tell. As long as I can do work with it, I will stick with this ROM and hope for fixes.

I did read all of the posts in this thread and did my best to try to understand them. My son knows the basics but is not familiar with this Tab. If there are any specific fixes, please let me know.

Once again, big thanks to Daniel_hk for developing the rom for these devices (and my kid for walking me through this).

Edit: I deleted my question about how to add SuperSu. I probably don't need it considering i don't really even understand how to use it. The built in root access in CM gives me more than a few ways to screw up this Tab.
[Galaxy Tab 7.7 Android Development] Harrison Le:
May we same problem about "Double tap to wake device", it's sometimes when we do "double tap" but screen is not wake up then we do "double tap" again... This will cause screen stucked in deep sleeping and even cannot on screen by power button :(, keep this stucking a while then can feel device get hotter, this case just can only reboot it.

Normally I flash Daniel's MM roms with Pico gapp but this case I have tried to use nano gapp then see my device P6800 works better because the open gapps project said it has some data files to improve and it really helps as I experienced flashing nexus launcher together if I flash : CM13 + pico gapp + nexus launcher then getting the issues pop-up some as "..... has stopped" while reboot but when I do flash with nano gapps then all these pop-up issues were settled, try it! :)
[Galaxy Tab 7.7 Android Development] funpig:
P-6210 restored to 4.1.2

After a couple of days, I found CM 13.0 a bit too glitchy on my P-6210. The browser was too laggy and forced closed too often. I restored the nandroid backup, mostly because i had never done this before and wanted to just try it.. All of this new to me. When i got back 4.1.2, it was like a breath of fresh air. I am going to wait for more bug fixes before trying CM 13.0 again.

Is there a consensus stable version in lollipop or kitkat that i can try in the meantime?
[Galaxy Tab 7.7 Android Development] p3dboard:
If you look for Daniels Kitkat Rom's there probably the best for you to try out since Android 4.4.4 didn't have as much memory overhead, and behaved better on Low memory then the newer Android 5.x and 6.x builds. I think if you look in the P-6210 thread, look for Carbon Rom, Slimkat or CM11, any of those should help you.

I find using the Android 6.x DU rom's and turning on the Built in Ad Blocking under DU tweaks helps increase the stability especially when using the Browser as AD's tend to consume a lot of Ram and CPU when browsing.
[Galaxy Tab 7.7 Android Development] Harrison Le:
I don't have tab plus but base on my tab P6800 I think recently MM roms such as CM, DU and Omni are better than lollipops and KK previously a lot except carbon KK build 20141212 it's fecfectly.

Roms work well or not most important depending how to flash, just my experience is use newest TWRP 3.0.2.0 + wipe totally clean, I always wipe all before flash a new rom, except SD card + chose reasonable gapp and flash all together.
[Galaxy Tab 7.7 Android Development] funpig:
Harrison, you may be right about using MM instead of going back to KK or LP. The older roms appear to have their bugs and are not actively supported. I may be better off using the newer roms with the active development.

When you flash the rom and gapps together before booting, do you wipe the cache and dalvik between the two flashes?

And, after you install the custom rom, is it possible to update to a newer version or another rom version without having to do a complete wipe or factory reset. ? It took so long for me to download all my apps and to set up all my layout and prefernces and i do not want to repeat the process to play around with all the different roms.

For now, i will stick with restored stock 4.1.2. I am an old dog who finds it hard to learn new tricks. I did a bit more reading and switched from Boat Browser Mini (will be tough to give up on this fave) to Chrome. This has allowed me to access the websites that were previously preventing me from making a secure connection.

When i have some free time, i will restore my backup of Cm 13 or flash a newer rom to play around some more.

Thanks to all.
[Galaxy Tab 7.7 Android Development] funpig:
I tried the DU rom yesterday. For my P6210, DU was a bit more stable than CM13. It occasionally force-closed and rebooted while in the Playstore or while browsing with Chrome. The nice thing about the reboots was that they are much shorter in duration than the CM 13.0 reboots. The DU boot animation looks more professional than the simple CM simple animation. But after about ten reboots, I wish I could just shut it off. The other bugs listed in my CM 13.0 posts were not apparent.

Playing around with these custom roms is fun but time consuming. But with buggy browsing, I restored back to stock Jelly Bean. I don't know why, but my most recent Jelly Bean backup (before flashing DU) would not restore. I kept getting an MD5 verification error. This made me nervous (maybe I am subconsciously hoping that this four year old P6210 actually bricks so I can buy another tablet). Luckily, I was able to restore to my first Jelly Bean backup that I made and kept from last week.
[Galaxy Tab 7.7 Android Development] Harrison Le:
Yeah, DU 10.4 was restarted quite often during open apps or browsing Web, my P6800 feels latest CM13 is most fecfectly so far of course I have considered which app should use because it's old device :) special is no games for this except sukudo :)

Browser use UC, YouTube, Google play music, newsstand, Google photo, keep,SwiftKey, Google maps, Google translate, pdf, other as Gmail, Outlook, Facebook use on Web browser is nice idea because it don't take ram and run also fast and stable.
[Galaxy Tab 7.7 Android Development] rgclaros07:
I agree with funpig that "playing around with these roms is fun but time consuming." I also am back now with 4.1. But will be back to find improvements in the development. The last two CMs for my p6200 proved to be very usable if not for the wifi problem -- hangs the tab. The other roms hang, reboot frequently even without internet or wifi. I agree with the observation that the double tap to wake consumes a lot of battery and heats up the tab -- an explanation can be found by google: sensor had to be awake always. I agree also with the observation that using nexus launcher and in my case, nova launcher, makes CM and DU faster and more stable. Without DTW and performance control (which I do not know how to use) and with nexus/nova launcer and wifi problem solved, I will be very happy to use the next CM if ever there will be.
[Galaxy Tab 7.7 Android Development] Emakiri:
Earpice problem

Master Daniel thank you for youre incredible Roms!

Q: I flash DU 10.4 on my p6800, n so much like it, but have a trouble - don't work earpice (small front speaker), handsfree talking n headphone - ok. Also, I try Omni n CM, but the same problem.

Maybe somebody know solution for this problem?
[Galaxy Tab 7.7 Android Development] Harrison Le:
I totally agree we come here for fun but do not think time consuming although it really time consuming :)

If you seriously think time to play with these roms is consumed then you should better get out this thread without any comments that is the right way to prove you respect your time, we be here because we have passionate about android, device and the modern changing and to get that needs to pay something it's totally fair!

We get fun with some our idle times mean we lost nothing and we have to think about the developers who make fun for us with their knowledge and their times to do fun to everyone without forcing payment so how?

I posted this by Omni_r62 just have flashed and recently confident to erase JB 4.1.2 and it's backup in my SD card because of thinking custom MM from Daniel_HK with build r_5x to up stable and bringing new Android to my device :)
[Galaxy Tab 7.7 Android Development] funpig:
Harrrison, just to be clear, I am NOT suggesting or implying that testing these ROMs are a waste of time. I am just saying that each time I backup, wipe, install custom rom, reload my apps, test and then restore to 4.1.2, a considerable amount of time is consumed. I do need to use this P6210 as my daily driver, so I need to load up everything and see if it works or not. I have no technical ability to fix any bug. I post reports in this thread in hopes that it may help Daniel find the bugs and fix them, and to let other P6210 owners know what to expect if they decide to try that custom rom. I wish other P6210 owners would also post their specific experiences so that I can figure out which ROMs to try or avoid. I rely on my Galaxy Tab Plus and I find 4.1.2 to be very reliable albeit old. I am looking for a stable upgraded rom to see if I can squeeze more life out of this old tablet.

From other posts, a "log report" is usually requested by Daniel. Unfortunately, I am new at this and have not figured out how to do this. If somebody wants to explain, I will try to do it the next time I test a rom.

I wish to thank daniel_hk for these custom roms, particularly for this old Galaxy Tab Plus P6210 which he does not even own. I have made a small donation as token of appreciation. I hope he continues to support the P6210.
[Galaxy Tab 7.7 Android Development] Harrison Le:
Hi [MENTION=5593355]funpig[/MENTION], understood!

May be tab plus is not popular more than tab 7.7 then not much feedback to Daniel about his custom roms for it cause still get issues, I'm lucky with tab 7.7_P6800 and really enjoy with MM r_62 on both CM and Omni, DU still have only one issue base on my tab is restart quite often during working, I respect and appreciate Mr. Daniel_HK for his works
[Galaxy Tab 7.7 Android Development] ppyk:
Bluetooth tab 7.7, I have a problem with ROM CM13.0-20160729 I like it a lot, but I want to fix Bluetooth thank you very much.