yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] AlexVallat:
Apart from Google Translate (from the Gapps that you linked to in the first post), another one you can try is Barcode Scanner

Maybe I've just been unlucky in which apps I've tried, but it seems that the only thing that can access the camera successfully is the camera app.

Thanks for looking into it!
[Galaxy Tab 7.7 Android Development] daniel_hk:
I already mentioned that barcode apks might have problem. They use a preview format which our tab no longer supported since LP. I just checked. Google Translate use the same format too.

You would get "E exynos_camera: exynos_camera_preview_start: s fmt failed!" in the log.

I remember my Kitkat or earlier support that. You may try the Kitkat's and JB's.

I might restore the old source later but it is years old and might not working now.

For QR code, Firefox has a built in scanner which works fine for me. Apks like instagram, Whatsapp, etc. don't have problem too.

Frankly, there is little I can do for other apk not running. I simply don't have their source and have no idea how they are operate inside. There are just too many apks. For the time being, just pick the one working or flash another ROM. ;)

Good luck!
[Galaxy Tab 7.7 Android Development] AlexVallat:
Confirmed, that log entry does appear.

I've tried back as far as your SlimKat 4.4.4r2 ROM, but it has the same problem. It's a shame to miss out on the cool translation camera thing, but not worth going back further to JB, I think.
[Galaxy Tab 7.7 Android Development] Harrison Le:
Hi Daniel_hk,

Have reinstall Omni 6.0.1 20150115 with video patch, it run well in youtube app but can not play youtube and video in websites , it crashes and website was close, I have tried to play video in some websites but same problem.

CM 13 videos play well in all app and website.
[Galaxy Tab 7.7 Android Development] daniel_hk:
I don't have problem playing YouTube with the built-in browser (Chromium now).
[Galaxy Tab 7.7 Android Development] greinedo:
Hi,

I experience exactly same problem than Harrison Le since several Omni roms. Video playback sometimes work with some websites in windowed mode but not in fullscreen or just freeze after time jump wich is annoying. With time I managed by using Dolphin Browser that allows external video player instead of system player. By selecting fullscreen in video and then quickly selecting external player (Bsplayer) it works very smooth. But it's a bit tricky.

Again, many thanks to Daniel for his amazing work. Installed with success latest Omni 20160113, Delta gapps 20151114-1, modified kernel 17/01/2016, ril3 and video patch. Had just some trouble configuring F2FS. It seems, but may be a mistake, that Factory Reset in TWRP is formatting /data back to EXT4 format, even if previously formatted F2FS !
[Galaxy Tab 7.7 Android Development] hogig:
Installed latest omni and patch yesterday, full wipe. Everything works except the following:

Brand new SD card formatting as internal storage and during the move data to new storage phase, ends with "settings has stopped". Card is recognized as corrupted... rinse and repeat.

Anyway for me to log this error for your analysis?

Thanks.
[Galaxy Tab 7.7 Android Development] daniel_hk:
I think adopted mode still have issue. I can only test it briefly in the early stage. After your report earlier, I tried it again right before my hard drive crash. It failed as what you said. I don't have another device with ext. sd and having stock MM for me to verify and compare. Haven't heard any device report success yet. I might take another look after things are settle. ;)
[Galaxy Tab 7.7 Android Development] philipnzw:
Used 22jan cm13 for few days now

Screen flicker almost gone ,only happens every 20-30 mins

Only crashed once when downloading app from google play

Fingers crossed :)
[Galaxy Tab 7.7 Android Development] jasonhs:
Hi guys, has anyone tried to play asphalt 8 on tab 7.7 with CM13? Mine stucked at the gameloft logo and the game is not loading, anyone has a solution for that? Or is it our phone not able to handle the game instead?
[Galaxy Tab 7.7 Android Development] p3dboard:
Asphalt 8 is heavy on Ram usage, plus the default OpenGL setting in /system/build.prop in the roms from Android 5 and later is set to a wrong value for the Google Play store to download the right version of the app for our tablet. The OpenGL es value needs to be set to Es 2.0 which is what our mali 400 gpu supports, ro.opengles.version=131072 - after that you need to clear the playstore data, and google play services data and reboot the rom. Then it should download the correct Asphalt 8 build. To edit the file you need to have root access. In the SlimLp rom builds i made last year i had the value adjusted, along with the Google Play movies fix for this tablet. I haven't tested Daniels latest cm13 build, but i think he's added the Play Movies fix, but not sure about the build.prop setting, but you can do it manually.
[Galaxy Tab 7.7 Android Development] wlhon:
Hi,

I'm on the latest omni-6.0.1-20160115-p6800-HOMEMADE.zip + OpenGapps + omni-boot-20160117-p6800.img.

(my data, cache is formated to F2FS using the latest TWRP).

Did a clean install, wipe system and cache, flash omni+opengapps + bootinage.img first,

reboot to system and configure the GAPPS startup to prevent GAPPS hanging.

Then apply the omni6-ril-patch-3.zip + omni6-video-patch-21060118.zip +SuperSu 2.52 to enable the phone and video playback.

Used the buildprop editor to change ro.opengles.version=131072, and ro.sf.lcd_density=160 (default ) for Google MAP zoom out bug.

1. Able to configure Viper4AndriodFX . (the DSP Manager is not working as daniel mentioned).

Able to load Asphalt 8, pass thru the Gameloft logo, download data... still not able to play as it mentioned there is not hardware keyboard and hangs..

Daniel, Is there a patch to fix the camera for the Barcode Scanner and Google Translator ?. I will be willing to test on the Omni 6 and provide feedback.

Tried CM13, the screen flickers upon setting up the GAPPs, using the SuperSu 2.5.2 , but when tried to load Viper4AndroidFX, keep on asking for

BusyBox eventhough I install it from the Google Play...

Felt that the Omni6 is closer to being a daily driver, although the MXVideo hangs and lose control when playing some video formats..
[Galaxy Tab 7.7 Android Development] GNUDroid:
[MENTION=301977]wlhon[/MENTION]. nice, details explanation of your setup. - I have same combination running.

still having troubles with oc GPU (even 330 MHz). Daniel once posted his voltages and CPU settings. could you share yours?
[Galaxy Tab 7.7 Android Development] daniel_hk:
1. I don't play games so I can't help much. In our local forum, someone said Asphalt8 can't run in M. He has tried 5 different devices from Samsung, Asus and LG. I don't know if its true but I have tried it in my Nexus 7. It failed in a few ROMs (only one from myself) too. I only tried it briefly and I can't pass the verification(or license? forgot) even with VPN. I don't know if I have miss something. I might study it later when I have time.

2. I had answered [MENTION=5495967]p3dboard[/MENTION] a few times. I don't know why he still obsess about the version number. May be he didn't read my answers to his questions again...:cyclops:

3. CM had removed busybox a while ago, don't know why. I just reinstate it in the source. it will be available in the next build. For the time being, you may copy the one from Omni in /syetem/xbin with a root browser.

4. I apologize that there are so many patches for the last Omni... :o: For the camera fix, you can get the file from my last CM build. Just copy the file /system/lib/hw/camera.smdk4210.so with a root browser to the same place. It will be available in the next build anyway.

Can you tell me what's wrong exactly?

If its CM-13.0, you need to copy the busybox from Omni. See point 3 above.

Good luck.
[Galaxy Tab 7.7 Android Development] p3dboard:
The keyboard issue with Asphalt 8 is caused because of a fault with the docking station driver from what research i was able to do when building the Slimlp rom, it was why i had the issue where you had to turn on the hardware setting in input with my Slimlp rom's,otherwise the touch keyboard would not show up. [MENTION=4948627]daniel_hk[/MENTION] has a little patch he applies for this, but the underlying bug is still there, the tablet thinks it has a physical keyboard. Asphalt 8 supports physical keyboard input, so it turns it on and you can't turn it off. The Galaxy Tab 2 developers disabled the keyboard dock driver in the kernel build to stop the bug, as they said not many used it anyway.

As for the opengl es setting [MENTION=4948627]daniel_hk[/MENTION], you are right that we have Opengl Es 3 libraries in the rom, but our hardware, the Mali 400 gpu doesn't implement that. Check the official Galaxy s2 cm 12.1, they all use the Open Gl Es 2.0 value which is what our device supports. Asphalt 8 is a Game that has different builds for Open gl es 3.0 and Open gl es 2.0 hardware and our device needs the opengl es 2 version otherwise its graphics don't render properly. I hadn't bothered pushing the point as its easy to manually fix the value to the Opengl es 2 value.

Mali 400 GPU - http://www.arm.com/products/multimedia/mali-gpu/ultra-low-power/mali-400.php

Example of an Andriod 5.0.2 build.prop for i9100 (Galaxy s2) with Mali 400 GPU - http://xdaforums.com/galaxy-s2/general/noob-friendly-build-prop-tweaks-t2993761 - if you go to his last code sample you can see his complete Build.prop
[Galaxy Tab 7.7 Android Development] p3dboard:
High Daniel,

Asphalt 8 starts fine on KK, and with the build.prop change on Android 5.x and 6.x it loads when it starts fine when the right build is installed from the Google Play store.

However from about one or two versions ago (they update it every few months), the Hardware Keyboard detection support that they added has made an issue for our tablet so you can't actually get beyond the screen, unless you plug in an external keyboard (I have put one in via USB OTG cable as a test) and you can get beyond that point.

All I can say about the build.prop change is that i know if it's set to the 131072 value, the playstore downloads the version that is compatible with our tablet. If its set to the OpenGL es 3.0 value, the APK it downloads from the play store doesn't work properly with our tablet.

Edit: The reason i compare with the Galaxy s2 phone is it has a Exynos4 4210 chip with Mali 400 GPU. I also understand you don't have google play store access, so you rely on our testing. You do amazing work for our old tablet, i am just passing on my observations on anything that i find to try help you to fix any bugs. You certainly know a lot more about the coding, so i might not be right about some of my guesses.

Is the sec keyboard driver part of the dock driver? I think it might have been where i was last looking to try figure out the hardware keyboard issue. I know the slimlp rom builds would be have as if a keyboard was plugged in and it would simply offer word predictions, but no touch keyboard, but if you turned on the hardware switch in input, then the touch keyboard would show.

Peter

---------- Post added at 02:56 AM ---------- Previous post was at 02:02 AM ----------

Hi [MENTION=4948627]daniel_hk[/MENTION],

Google Play Movies fix not working - i have tested the L3 update that you put in Cm 13, just letting you know that the playback comes up with a licence error. Maybe the L3 libraries only fix Android 5.x,and newer files are needed for Android 6.x? I checked logcat and it didn't have anything obvious, like before when i saw it was looking for missing library files.

Edit: i have done some more testing with Asphalt 8 as they recently separated the Apk from the content download. Before it was about 1Gb to test each time. Anyway it turns out that the Apk file is the same, but with a build.prop value of 131072 for opengl, the game content download is different, with this setting it's 763mb, with the 196609, the content is 802mb.

So in the past it was the playstore application content that was downloading incorrectly,but the end result is if it's not got opengles set to 131072, Asphalt 8 downloads the wrong content

Edit - i have attached screen shots from Daniel's latest cm13, showing the keyboard input detection as well as the content download size with the Opengl Es 2 build.prop setting, just so you can see that it downloads a slightly smaller package.
[Galaxy Tab 7.7 Android Development] jasonhs:
I somehow managed to get Asphalt8 to work once again! What i did was to flash Omni 5.1.1, changed the openGL to 2.0 in build. prop, wipe cache and dalvik then reboot, viola Asphalt8 runs smoothly. I have also tested N.O.V.A 3 and it works well too.
[Galaxy Tab 7.7 Android Development] Mrxyzl:
Have to say that DU rom is amazing, fast smooth, ram hadle well. Only yhe flickering screen is annoying

Thank you Daniel for an amazing rom
[Galaxy Tab 7.7 Android Development] galoneta:
Master Daniel,

About P6210, first flahed twrp-2.8.7.3-p6210.tar then reboot and made backup of carbon 5.1.1, my actual rom.

Then flashed omni-6.0.1-20160115-p6210-HOMEMADE.zip +omni6-video-patch-21060118.zip +open_gapps-arm-6.0-pico-20160127.zip +omni-boot-20160117-p6210.img then reboot

Then flashed BETA-SuperSU-v2.52.zip and reboot.

Speed us very good in this build. Only restarted once when connected in my wifi phone router (motorola xt1040 connected in 4G network). Since 5.1, my p6210 has the same reboot bug when connected to a wifi router sharing a 4G network, the same does not happens when sharing a 3G network in the same phone.

Photo preview in gallery has distortion. Video is fine.

EDIT: Using QuickPic solves this all: video and even photo preview is fine!

EDIT2: Had some reboots using office software like wps office.

Tell me if you need aditional testing.

This rom is getting better, congratulations to you master!

Thanks.
[Galaxy Tab 7.7 Android Development] galoneta:
Master Daniel.

About CM13 in P6210: flashed cm-13.0-20160122-UNOFFICIAL-p6210.zip with and without gapps with and without supersu and the result is the same: after samsung logo nothing else goes on....

Does the previous patch (cm-13-20160106-p6210-patch2.zip) for proper boot in P6210 needs to be flashed or it is included in this build?

Reflashed carbon 5.1.1 back for now.

Thanks
[Galaxy Tab 7.7 Android Development] Ruza:
in DU v10 when sending files via WiFi (SpeedTest) tab was rebooted
[Galaxy Tab 7.7 Android Development] so_ang:
DU10 is not Bad

I think it smooth but still has some problem
[Galaxy Tab 7.7 Android Development] rezaswandira:
Nice job daniel, this is better than ypur lollipop ROMs imo. I think it would be great if you continue the development of 3.4 kernel for these tablets as it gives a lot of performance boost for my old xperia device.

And a little bit of suggestion; i dont have any credit card and it would be great if you consider making an app in play store to donate to you :)
[Galaxy Tab 7.7 Android Development] F R Harris:
Tested DU on P6200, whenever trying to access the apn menu, com.telephony always crash, and simcard became undetected, flickering are reduced by disabling auto brightness and disable HW overlays at dev options. The rom itself are smooth and stable, but can't test mobile connectivity due to the issue above, thanks daniel
[Galaxy Tab 7.7 Android Development] daniel_hk:
I don't know that. Thanks for your report. Let me check what's wrong and PM you later. ;)

The wifi driver and HAL are the same for all my ROMs. It might be the same as ES file explorer. Should I have their source, I might take a look. I think you should report to the apk's author.

I don't know what happen in Xperia but I'm quite sure there won't be "a lot of" performance boost. It might just be the difference in the system or our imagination. :cyclops:

There are a few "new" (also years old now) features in 3.4 for sure. 90% of the code are the same even comparing with the 4.x kernel. Most of the hardware drivers are from manufacturers and its optimize for the existing kernel. I had already backport a few drivers from 3.18. Bluetooth, part of the net and a few more are 3.18 now. Even backport is already a really tough job.

I have a real test on my Nexus 7. There is a 3.4 kernel released for Tegra. Someone have port the drivers to it. For two years now, I can't see a real fully working one yet. I had tested myself. The "difference" is not observable. I simply can't tell the difference but only the number in About. All the performance apks tell the same too.

Starting a new kernel is not a simple thing. It just won't boot and blank if anything went wrong. AND there is no log. For Nexus', we can have a console at the headphone jack. I have searched, dig and tried many ways. After broken a few connectors, I still have no idea how to get a console for our tab. Without it, we are blind and dumb. Just can't tell if anything work and/or what's wrong.

Actually, I had tried 3.10 and 3.14 for my tab. I believe there are always someone better than me so I can't said impossible. I can only tell you it is not worth and the chance is really low. :(

Well, I don't have any new idea for an Apk. Seems every doable thing is already done by many good developers. Thanks for the donations and supportive PMs. A "thank", a report or just read my thread would be good enough for me. :D

Thanks for the report. I think the default apn-list xml is missing. I might pack a patch later. ;)

Edit: here is the View attachment du-apn-patch.zip
[Galaxy Tab 7.7 Android Development] henry08:
dirty unicorn setup issue

dear sifu daniel,

my p6800 stuck after logo..saying setup cannot be completed..

i have instal du rom , gapps and the patch...then wipe cache..then reboot..

correct me if i did wrong..
[Galaxy Tab 7.7 Android Development] daniel_hk:
How to flash is in Post#2. Nothing special. If you didn't read the thread, do it now.

To be honest, this kind of "report" can only waste your time and my time. Can anyone tell me what he meant?

I really don't understand, sorry... :confused:

I never see any message at the boot logo?

Where did you see "setup can not be completed"?

I can't recall I have seen this message before in anywhere too...??

Usually I would ignore these kind of post but I'm interested. Can you take a picture to show me where it appeared?

Good luck.
[Galaxy Tab 7.7 Android Development] rezaswandira:
I know that porting it is a big deal daniel. Sorry for OOT but back in the day when my 2011 xperia got a new 3.4 kernel is like having a new phone. Sony had abandoned us with unfinished gingerbread kernel ported to ICS that makes the phone sluggish as hell and a lot of unsolvable bugs. After 3.4 kernel is ported, every scrolling and animation are smooth and executed properly.

Its not that perfect, but even simplest bug are solved woth that kernel so i think we need 3.4 in order to have a near-flawless experience with the ROM
[Galaxy Tab 7.7 Android Development] henry08:
dirty unicorn booting issue

Lol. I wont waste my time and your time as well sifu daniel..

Below is the link of the box that pop up on my screen after booting..

If click ok, then the same box appear again.

i have cleaned format my tablet, install DU rom, followed by gapps, then the patch.

end with wipe the cache before rebooting.
[Galaxy Tab 7.7 Android Development] daniel_hk:
So it is not stuck at Samsung logo and a different message... :cyclops:

It's been posts for many times. Your answer is in post#2 too. Read it.
[Galaxy Tab 7.7 Android Development] txtyb:
作者大大你好，首先我必须要感谢您带来的rom，然后呢我不得不反馈几个bug。

1，使用QQ发送图片时，有很大几率会直接造成重启。

2，应用横屏时无法通过传感器转向右侧。

因为这个rom还很不稳定，经常重启，卡死，所以我又刷了您的cm12.1 rom，但是发现bug1仍旧存在，所以我恳请您修复此bug后也发布一个cm12.1的修复版本。谢谢！
[Galaxy Tab 7.7 Android Development] galoneta:
Daniel,

As you suggested in your PM.

1- MD5 of my file is correct as yours

2- using just cm-13.0-20160122-UNOFFICIAL-p6210.zip +/- open_gapps-arm-6.0-pico-20160127.zip +/- BETA-SuperSU-v2.52.zip and restarting stops at samsung logo

3- doing the same as step 2 but adding omni-boot-20160117-p6210.img goes ahead to blue CM13 pulsar logo for + 5min and nothing else goes on!

Will try DU ASAP.

Thanks again.
[Galaxy Tab 7.7 Android Development] galoneta:
Daniel,

About DU 10:

Installed DU_p6210_6.0.1_20160128-1613.v10.0-DIRTY-DEEDS.zip + open_gapps-arm-6.0-pico-20160127.zip + du-apn-patch.zip and reboot: runs fine, there is flickering on the screen , feels slower than OMNI.

No reboot so far.

Thanks
[Galaxy Tab 7.7 Android Development] Wachicamo:
So far, omni runs OK on P6210, but the infrared sensor doesn't work. Any ideas?
[Galaxy Tab 7.7 Android Development] F R Harris:
Report of DU v10,

Mobile data working, indeed feels slower than omni but more stable, didn't get any random reboot ye.

Bluetooth can send files only (test with BB Onyx, does not matter since i rarely use it).

When making phone calls, upper ear speaker not working, but using the phone speaker button the sound came out from the buttom phone speaker (where the mic is), in CM and OMNI phone working properly.

Earphones/headset (the thingy with the long cable and connector) working properly with phone and media.

Thanks Daniel
[Galaxy Tab 7.7 Android Development] galoneta:
Daniel,

Flashed cm-13.0-20160122-UNOFFICIAL-p6210.zip +open_gapps-arm-6.0-pico-20160127.zip +cm-13.0boot-20160202-p6210.img +SuperSU-v2.56-20151030013730.zip : reboot and start fine, speed is very good, no reboots so far, performance feels better than DU. Screen flickering is there!

Had to install busybox for proper operation of performance control.

Tried super su 2.49 and 2.52 : works fine but performance control did not find busybox for proper operation. Tried 2.56 too and installed busybox finally. Using this build so far no reboots.

Thanks.
[Galaxy Tab 7.7 Android Development] msnote8:
Dear Daniel,

First and foremost, a BIG thank you for all your hard work and effort to keep the old Tab Plus alive. :) :good:

I tried to download the latest kernel for P6200: cm-13.0boot-20160202-p6200.img but unfortunately when I tried to open the file

I got the message : The disc image file is corrupted. I triedto load from the main server and mirrors but the result is the same.

Would appreciate your help in probably uploading a new file for P6200.

Thank you.
[Galaxy Tab 7.7 Android Development] daniel_hk:
Why open the img file?

It can be flash directly in TWRP.

In case you don't know, there is an flash image option in the install page of TWRP.

Good luck!
[Galaxy Tab 7.7 Android Development] msnote8:
Hi Daniel,

Yes my mistake. Manage to flash the image using TWRP. Then did a

1. clean install of CM using just cm-13.0-20160122-UNOFFICIAL-p6210.zip + open_gapps-arm-6.0-pico-20160122.zip +ril patch + BETA-SuperSU-v2.52.zip.

2. system boots to cm13 logo and message says starting applications. However after starting applications, it reverts back to cm13 logo and seems to be looping or stuck at the cm13 logo.

3. Have tried a number of times but result still the same stuck/loop at CM13 logo.

Any suggestions would be appreciated.

TQ
[Galaxy Tab 7.7 Android Development] daniel_hk:
Why flash the ril-patch? I'm quite curious where did you get the idea?

If you had read the posts, it is for omni and it is for the phone versions (p6800, p6200 etc.).

You must have get it from the thread since it is an attachment. You just search for the link and refuse to waste your precious time to read the text. And yet, you have time to post and waste my time.... What can I say? :eek:

If you are out to describe the truth, leave elegance to the tailor. -Albert Einstein.
[Galaxy Tab 7.7 Android Development] dcervi:
As I understand, you did a clean CM13 install AFTER flashing the kernel image, so you overwrote the New kernel image with the old one included in the firmware. Try to do a clean install, and then flash the newest kernel image.

Enviat des del meu D5803 usant Tapatalk
[Galaxy Tab 7.7 Android Development] msnote8:
Dear Dcervi,

I did as suggested by you and YES, it worked:) :good:. Thank you for your suggestion.

Regards.