yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] saeghe3000:
[Solved] Finally my linux workes fine on my Tab

After a lot of search in web , finally found where is my problem. There is an essential part in "Complete Linux Installer" app, named "update script". and this app connects to net and download that script. I don't know why this item doesn't work in my Tab. for solving this issue I downloaded update script manually from net and copy to where should be exist (/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh)

when i want to run Linux , I use this code in terminal with SuperUser Account:

sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /sdcard/fedora/fedora.img

and my fedora image is in /sdcard/fedora/ .

after run this code you have a Linux with wide capabilities!!

AND THESE ROMS SUPPORT LOOP DEVICES !:good::good::good:

Thanks daniel
[Galaxy Tab 7.7 Android Development] Harrison Le:
Just flash omni 20160323,

After running animation get black screen with error as bellow ficture ,can not close to go setting:
[Galaxy Tab 7.7 Android Development] daniel_hk:
This is not the first time you have that. You must have forgotten. ;)

There is nothing special and weird. An explanation is in post#2 for months. Please read it again.

1. You need to flash ROM and gapps together.

2. If you had flashed gapps before and don't want to flash gapps this time, you need to wipe system before flash.

Good luck!
[Galaxy Tab 7.7 Android Development] rebski:
OmniROM 6.0.1 20160323

I have just installed this and it is superb.

The screen flicker appears to be cured. Everything I have tried works perfectly including

YouTube

Phone calls in and out

Mobile Data

"Tricky" video files

Web browsing with downloading files

My favourite apps including ebook readers

There is the occasional instability and restart, though I haven't been able to spot the provocation
[Galaxy Tab 7.7 Android Development] tonygamble:
Good to hear that Rebski. This morning I decided to abandon my P6810 as it is so lethargic and repeatedly hangs.

A couple of months ago I installed CyanogenMod 12.1-20151006-unofficial-p6810. I liked the fact that it was much kinder to the battery and it did things that the locked in stock rom could not manage..

I use the 7.7 partly as a satnav. It worked but gosh it took ages to find the sats.

It played music with PowerAmp.

It did my emails with Kaiten.

I never found a decent web browser that did not hang from time to time.

And moving from one app to another was a bit like my old DOS based PCs or my Toshiba Libretto. It was so slooooww.

You clearly find the new Marshmallow works smoothly so I'll spend what looks like a rainy weekend giving it a go. If not then, sadly the 7.7 goes to eBay and I'll spend the cash on a Nexus 7 that (and my wife already has one) I know will work. Not anyone's fault around here but I guess making silk purses out of pigs ear out-of-date tablets is not often going to happen.

Tony
[Galaxy Tab 7.7 Android Development] rebski:
You are right, it was the default web browser that triggered the last FC.

Your use is probably more demanding then mine, my main tablet is the 10.1" Sony Z4 and my 7.7 Tab is mainly for ebook reading. Let me know if you have any apps that you would like me try out for you in case that feedback would be useful.
[Galaxy Tab 7.7 Android Development] Harrison Le:
Hi Daniel,

I always follow the orders to flash Roms and 100% succeed so far except this omni 20160323, I really don't know why, already tried again after yr comment but not ok also!

Now back to awesome DU for relaxing :)
[Galaxy Tab 7.7 Android Development] tonygamble:
The Omni Marshmallow is a totally different experience to my previous Lollipop. So much faster. It has rebooted several times but that might be as I installed new apps. I am also using Xposed to improve the screen calibration of my Navigon that was far too small for easy use in the car.

I'll give the 7.7 some use over the weekend and see how it holds up. It also good to have a decent browser as I never found one for the Lolli.

I'll be back with an update as soon as I have anything to add.

Tony
[Galaxy Tab 7.7 Android Development] Kholargol:
Hello!

Is there someone with a P6810 who doesn't have any freeze, reboot or flickering screen ? If yes, could you please tell me what are ROM and Gapps versions ?
[Galaxy Tab 7.7 Android Development] p3dboard:
I have a p6810, omni is the only one currently without the screen flickering issue, Daniel's working on the Cm and Du rom's to fix this and has improved the situation a fair bit.

I get the occasional Rom reboot on all of the Android 6 Rom's. I am not sure if it's low Ram that is causing it, but Android 6 performance is much better than 5.1 was, so hopefully it might eventually be worked out. I use trickster mod to enable Zram, which i feel makes it reboot slightly less. The only thing is trickster mod only has a 10% zram setting and i would like to make it slightly larger for better testing. In Android 5.1 i could put a script in the init.d area to set a custom zram size, but so far on Android 6 i haven't got this working.
[Galaxy Tab 7.7 Android Development] Kholargol:
It's a much more detailed answer than expected thanks! I will try Omni + trickster too. Else I will downgrade to 12.1. My priority is too have a stable tab over a fast one. It's for my father and he's starting to get crazy with all the freezes and reboots !
[Galaxy Tab 7.7 Android Development] tonygamble:
This time yesterday I was about to consign my P6810 to eBay. Totally cheesed off with my Lolli.

Yesterday afternoon I installed the Omni Marshmallow. I had a problem when using the Open Gapps in that the final install failed. With the Gapps 601 Base I succeeded. I have also installed Xposed as I need to tweak Navigon (beware the installer on some of the links does not work beyond Android 4).

I have just used the 7.7 in my car as a satnav and music system. It works fine but I also am getting rom reboot. Could the previous poster explain trickster mod please.

Agreed Android 6 is far better than the 5 I was getting. I have not seen any screen flickering with the Omni.

Lets keep chatting.

Tony

London UK
[Galaxy Tab 7.7 Android Development] tonygamble:
This rebooting problem.

Reading around I see mention of an Xposed app from Wanam.

Might this help us?

Tony
[Galaxy Tab 7.7 Android Development] p3dboard:
Hi Tony,

Trickster Mod is an app from the playstore. Most of its functions are also in the performance App that Daniel includes and can be accessed from the settings area.

However trickster mod also includes the ability to enable zram, which turns a portion of ram into compressed swap space. Currently the app only supports using 10% of ram. Android can place some things in memory that are not in use in the compressed memory. You can set it to re-enable zram at boot so it's on each time you restart in the app as well.
[Galaxy Tab 7.7 Android Development] tonygamble:
Oh, dear. Not a happy user.

10% of my battery gone in an hour and a quarter and a reboot as I tried to access the brightness control in Settings.

I'll report again later.

Tony
[Galaxy Tab 7.7 Android Development] Mrxyzl:
Hello, [MENTION=4948627]daniel_hk[/MENTION]

As you know Marshmallow have another policy for apps to write on sdcard so some older app cannot write on sdcard anymore. In my case it was Moonreader, so could you please look at the following link and add this mod in your build to override the sdcard issue ?

http://xdaforums.com/showpost.php?p=65984609&postcount=655

it was just my suggestion , thankyou for hear me out. :good::good:
[Galaxy Tab 7.7 Android Development] daniel_hk:
I didn't play games but I also want Titanium BU work for my MTK base phone. Actually, I'm testing a similar fix. If it doesn't work out, I would look into the link you provided. ;)
[Galaxy Tab 7.7 Android Development] gaspan:
Hey daniel_hk!

I just wanted to thank you for all the good work you've done!

Flashed Omni-6.01-20160323 on my P6800 this morning and everything is working well :)

Before this I was running your CM12.1 build for a while :cowboy::good:
[Galaxy Tab 7.7 Android Development] tonygamble:
Yes, Daniel, brilliant work and Thank You from me. I do appreciate your efforts. The 7.7 is so much more useable now. And all at no cost than the odd 'gesture of thanks' to Daniel which is well deserved.

Running the 7.7 with the Omni Marsh alongside my brand new Nexus 7 I see that Daniel has offered a control called Performance that is not on the stock Marsh on the Nexus.

It is set at 1400 max and 200 min.

There is 1600 offered as a max. Is there any point in trying this to avoid the reboots. I got several yesterday and even one just as I finished using the 7.7 and put it (gently) on the carpet near my armchair.

Tony
[Galaxy Tab 7.7 Android Development] gaspan:
I think you should _lower_ the max frequency instead if you want stability ;)

However I doubt the crashed are due to the cpu freqency... I've experienced a few random reboots as well. The Omnirom boot logo appears misaligned when that happens (edge of the screen instead of center).

I'm not sure but it might be related to auto-rotate... I turned it off but its too early to say if that fixed anything :angel:

I also get "DSP Manager has stopped working" error when trying to launch it or play music via Apollo (music plays fine but every song change triggers the DSP error).

Other than that, everything is quite peachy. I'm really impressed with the performance of this build :)
[Galaxy Tab 7.7 Android Development] tonygamble:
Yes, I noticed the offset when the machine rebooted. The logo was not central and the lock screen was only covering half the area. I have not noticed the DSP Manager message. PowerAmp worked fine with my list of 3,000 (yes 3,000) tracks - 11gb

I'll drop that other setting down to 1,000 today.

Bye,

Tony
[Galaxy Tab 7.7 Android Development] rauscherxda:
Unfortunately, Setup Wizard has stopped

thanks for everyone's hard work on this, I have a number of i815 tablets that I'm testing out the different builds on.

I'm getting the "Unfortunately, Setup Wizard has stopped" error on the newest omni-6.0.1-20160323-i815-HOMEMADE.zip. I've tried a few variants of the latest open GAPPS (eg, open_gapps-arm-6.0-pico-20160326.zip, open_gapps-arm-6.0-nano-20160326.zip, open_gapps-arm-6.0-micro-20160326.zip) with the same result. I've used previous versions of the OMNI build without issues. Any advise?
[Galaxy Tab 7.7 Android Development] tonygamble:
gapps-601-base-20160323-1-signed.zip worked on my 7.7 after I had the same error with the open gapps.

Tony
[Galaxy Tab 7.7 Android Development] Jarr3:
Hi, I flashed the omni-6.0.1-20160323-P6800-HOMEMADE.zip ROM this morning. After I started to flash SuperSU right after the gapps without booting, I do not have the same problem as you anymore.
[Galaxy Tab 7.7 Android Development] aemee:
Have been testing all 3 roms on my p6800.

I have to say that the DU port is the most stable of the 3 for me. As annoying as it is to have the screen flickers, compared to Omni, the inconsistent flickers are more welcomed than the inconsistent reboots. Plus the flickers are pretty much gone if you leave the current window/screen.

However I would like to confirm the reason for reboots across all 3 roms with regards to multi tasking. Is it persistent issue of memory leaks inherited from the LP or is it something else?

I get regular hangups on all 3 roms especially when it seems that I am multi tasking "memory intensive" apps. Examples would be having Dolphin, Skype and YouTube running. It almost never happens if I have casual apps running.

I do not recall any reboots or hangups on KK and below. Maybe intense lag..maybe..

If anyone could shed some light on this, it would be most helpful since googling "memory leak" for android 5/6 simply links to news about google patching it or reinstalling ram hungry apps.
[Galaxy Tab 7.7 Android Development] rauscherxda:
That worked like a charm thanks! OMNI is looking very polished. I've been testing for an hour or so and its been great. Bluebooth, WiFi are working great, no screen flicker. I'll test cellular Monday. Only problems so far:

1. two random reboots so far, I was installing about 10 apps once and then listening to music and posting this over RDP

2. DSP Manager crashes "Unfortunately, DSP Manager has stopped." during music playback (Google Music today, but I've see others do this). I disabled in Apps but it still popsup, super annoying but doesn't seem to affect anything.
[Galaxy Tab 7.7 Android Development] Abort Retry Fail?:
Alas, I have no advice, but I can confirm identical failure with my i815. I tried two flashes with the same result as you: the first was after a full wipe and then installing the 0323 ROM, the nano open gapps package dated 20160326, and SU 2.52 serially in the same flash. I then tried just the ROM and gapps, figuring I could flash SU later if this tactic succeeded. It was not to be, and like you I had no such problem with the 20160222 Omni build. I am at a loss, but at least I can easily restore the backup I made of my Omni 20160222 installation configuration.
[Galaxy Tab 7.7 Android Development] Harrison Le:
Seem open gapps is not compatible with omni Rom build 20160223!!

Why???
[Galaxy Tab 7.7 Android Development] tonygamble:
Random Boots

On the 7.7 dropping the Performance maximum to 1,000 seems to have helped.

I don't understand what 'ondemand' and 'cfq' mean in that panel so I have left them unaltered.

What does cause a reboot (but certainly not every time) is calling up Settings from the Home page. It is the only identifiable incidence I can report. I have had Chrome locking but it might be poor response from a web URL in the same way that browsers hang on a PC and one has to use the Task Manager to kill it.

Has anyone tried a cache cleaning app? I had one with my Lollipop and then abandoned it.

Tony

London UK
[Galaxy Tab 7.7 Android Development] gaspan:
cfg is the Linux I/O scheduler. You probably do not need to change that.

And if the crashes still occur it sounds like lowering the max cpu freq didnt really help :confused:

Probably something else to it.... at least with the Omni build crashes occur randomly even when you do not have multiple apps running. :rolleyes:

I decided to try out the DU build and indeed it does seem more stable, managed to crash it just once so far :)

Anyway we should get some proper debugging: we need to get some logs about the crashes if we want to get them fixed! :eek: :D

---------- Post added at 09:35 AM ---------- Previous post was at 08:54 AM ----------

I managed to get 'adb logcat' running on my workstation. Sadly the DU build is not so easily crashable so going to reflash Omni later and try get some logs :D

Have a good day everyone! :)
[Galaxy Tab 7.7 Android Development] aemee:
I set the governor to pegasusq and the i/o to sio/cfq simply because it was the recommended combination since FroYo. Thats it.

The last time I tried undervolting and underclocking the cpu/gpu I ended up having to wipe and reflash. Reason = "Apply on boot" was always checked. So I try not to mess with them unless recommended by the experienced.

DU is all hunky dory as long as I have no memory hungry apps running either back or foreground so I do recommend it to anyone who is using the P6800 for simple tasks. Plus DU has an awesome nav bar alternative. Almost as good as having GMD.

I have tried using logcat in the past which failed horribly so I am hesitant to try again.

Greenify used to be so good pre LP. Doesnt seem to do much for LP and MM.

Will try using TricksterMod to see if it helps somewhat as suggested earlier.

*update*

Well, trying to enable zRam via Trickster insta rebooted the device. Not sure if I did something wrong or if it simply isnt supported by DU. Pretty sure I misread or didnt read something, somewhere in here.

Am unable to reproduce a reboot/crash which is frustrating. Maybe I missed out an element crucial to it.

Will keep trying to get some form of advancement.
[Galaxy Tab 7.7 Android Development] tonygamble:
I set the governor to pegasusq and the i/o to sio/cfq simply because it was the recommended combination since FroYo. Thats it.

I take that as a recommendation then !!

And if the crashes still occur it sounds like lowering the max cpu freq didnt really help

I got the impression I was getting fewer crashes. So in my book that was progress !!

The last time I tried undervolting and underclocking the cpu/gpu I ended up having to wipe and reflash.

But with a Nandroid backup I via TRWP I should be OK? Yes?

Sooooo much to learn.

Tony
[Galaxy Tab 7.7 Android Development] aemee:
Well i would not recommend setting up the governor and i/o like I have since that was purely done out of wilfulness, I'd say. :P

With a nandroid, you should be ok. The thing for me is that whenever I restore from a nand backup, it was never the same as when I made it. I have never known the reason but I frequently get more problems restoring nand backups. Either I get bootlooped or I got more force closes. Have not made any nand backups since KK so I would not know how they fare now.

Knowledge is power. Learning is fun.
[Galaxy Tab 7.7 Android Development] saeghe3000:
Hi daniel

I didn't find "move to sdcard" in settings->apps->storage

What is my wrong? or doesn't exist really?
[Galaxy Tab 7.7 Android Development] gaspan:
I'm happy to report that I havent been able to crash the DU build today! :)

I will probably stick with this since I don't really have the time to do serious debug work on the omni release.

ofc DU build Screen tearing/freezing bug is little annoying but not too bad :)

Thanks again for your great work daniel! :good:
[Galaxy Tab 7.7 Android Development] daniel_hk:
M has the different way to handle external sd. Right now, no M ROM, stock or custom (as far as I know) can move app to external storage. If you already have app moved to sd in earlier Androids and you are lucky that factory reset is not required to boot, you may see the button. However, it would only be one way--move back to internal storage.

There is the new adopted mode but doesn't work yet (no ROM I know is working yet). I can manually replace the internal sd with external sd but that is different.

I'm testing an override of the security in external sd but "move app" was not my intent. See if it work as a side product.

I don't know what's the tearing/freezing. If you meant the rotation, it would correct itself when you pick it up. I already explained several times. That was the orientation correction not an issue.

If you meant the flickering, they are limited to the refresh part now. You might observe that the status bar or nav. bar is not affected. Seems it is caused by a different source. For the time being, you may disable the adaptive brightness in Display settings.
[Galaxy Tab 7.7 Android Development] tonygamble:
Thanks again, Daniel.

I have made a modest contribution to the sinking fund....enjoy an equally modest post Easter drink on me!

I said that I'd had a reboot when I put my Omni based 7.7 on the carpet by my chair on Sunday evening. Last night it was on my table and I got an alert caused by a BBC News push notice. I picked up the 7.7 to read it and when I put it back on the table it rebooted.

I am not suggesting that putting the device on a flat surface causes reboots (even I am not wild enough to suggest that) but I reckon that now is the time for me to charge it up, turn it off and put it in a cupboard for a month. I have a Nexus that does what I need but I'll watch this thread with interest and maybe drag the 7.7 out of retirement in a month or so's time.

I have enjoyed exploring the rocky roads of rooting but it is now taking up time that would be better spent on other challenges.

Thank you for your support and interest - and to all the others who have contributed their odd gems of encouragement and advice.

Adieu for a short while.

Tony

London UK
[Galaxy Tab 7.7 Android Development] gaspan:
Yes, this. Status bar and nav are not effected. Sometimes it just seems to miss the last refresh and the GL context window doesnt get drawn (just black screen). Nothing much in the logs about it also... I read everything what you had written in post #1 and its too bad its not just due to simple differences between the OMNI and DU graphics codebases.

Trying to turning off adaptive brightness: I found out I cannot access display settings with DU... attached log.
[Galaxy Tab 7.7 Android Development] daniel_hk:
Thanks Tony. I'm looking forward to seeing you again. :)

I don't know which version you're on. If you are on the last 20160303 build, there was an update in post #1 at 2016/3/5.

I don't know which thread's post#1 you had read. :cyclops:
[Galaxy Tab 7.7 Android Development] gaspan:
Ah yes, you are right! (I thought the fix had already been merged to the latest) :crying:

My bad :angel: Will apply patch.

I'm running DU_p6800_6.0.1_20160303-1603.v10.0-DIRTY-DEEDS.zip

There is a lot of information in this thread but it is somewhat all over the place. I see you valiant efforts replying to the same questions over and over again. Sorry to make you do that :)

You are really doing great work keeping these devices alive. I've been hacking on Linux since the 1990s but Android is a new thing for me. 10 years ago we already had nice "mobile" Linux distro: Maemo from Nokia. But they managed to screw it up and Google picked up the slack with Android and here we are today!

Wishing a great day to everyone!
[Galaxy Tab 7.7 Android Development] GNUDroid:
wow a new du build! thanks so much!

will test tomorrow. du is fastest rom for me.
[Galaxy Tab 7.7 Android Development] Zelote:
OpenGapps Pico (29/03) crash on start with the new DU on P6210 and TWRP3, any clues on this?

Update 1:

So, ive go back till OpenGapps 22/03 and the system booted! Yeah!

I think that the Config app have some delay on P6210, when open it, there is only a blank white screen... then i click to wait to respond and the system promps me to allow root, only then config app works.

I'll do more tests and update this post!

Tks again [MENTION=4948627]daniel_hk[/MENTION] for the excelent work! =)
[Galaxy Tab 7.7 Android Development] Harrison Le:
[P6800]

flashing DU 20160329 +open gapps arm 6.0 20160330 failed

flashing DU 20160329 + gapp 601 base 20160323-1 failed also!

Both issue are same : UNFORTUNATELY, SETUP WIZARD HAS STOPPED

***one thing more, during flash I see build is MMB29M but not MCH19J
[Galaxy Tab 7.7 Android Development] p3dboard:
I have the same force close issue with Setup Wizard on p6810 after flashing gapps (open gapps 20160328 version) on the new DU build, i have tried going into settings, apps, show system apps, setup wizard, app permissions, as suggested by Daniel in the Faq, but only the contacts permission is available, the phone permission is not there. I haven't tried the adb hack yet, which is Daniel's other suggested method.

So far the flickering seems to be gone.

If i flash the rom without gapps, it boots fine. Just need to get a fix for gapps. I am just trying and old gapps build now (20160127 open gapps) that i had on hand as a previous post mentioned older gapps might work

Edit: older open gapps package is working fine, 20160127 build
[Galaxy Tab 7.7 Android Development] tonygamble:
Have you tried gapps-601-base-20160323-1-signed.zip

I could not get Open to work on my p6810.

Tony

[
[Galaxy Tab 7.7 Android Development] Harrison Le:
KKK... Right! Flash with open gapps 20160127 then it work... Going to do more to see how it will be!

I have no store old open gapps but after all founded out way to get link for older open gapps :

https://github.com/opengapps/arm/releases/tag/20160127

***you want what day just change the numbers at the end of link :)
[Galaxy Tab 7.7 Android Development] spsrulez:
install failed

I just wanted to install room to my P6800 tablet and it failed, anyone knows why it failed or how to fix that? Dont know how to put link here with that external link protection, so i have to put it like this link here to tinypic i65.tinypic.co m/zkjy9x.jpg

just merge that link....