yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] nshahril:
Yeah.. I'd tried but doesn't work on my tab .. For the 5th times, I reset everything and do the clean install once and for all.. And it's working.

Just have to work extra to install the app from the playstore ?
[Galaxy Tab 7.7 Android Development] CsI_aHm:
Wonderful! The bluetooth speaker now works in Your yesterday's cm13 build. However, the file transfer is not yet operational between 6210 and notebook. More and more work! Thanks for your work Daniel !
[Galaxy Tab 7.7 Android Development] betexino:
how to diseable vibrate on navbar?
[Galaxy Tab 7.7 Android Development] yurius:
On latest CM 20151210 on P6800 got some random "No SIM" - unplug/plug SIM with reboot helps. Is it my hardware bug or CM13 (for now testing CM13 with libril.so from patch to omnirom omni6-ril-patch.zip )? And after every reboot need to switch off/on root in dev options, couse gived last time root permission to app didn't worked after reboot.
[Galaxy Tab 7.7 Android Development] daniel_hk:
Gapps are pre-built (without the source). Changing is almost impossible. There is no Gapps for 6.0.1 yet (not sure?). As I mentioned a few times, I can't access google server locally. I can only have limited tests via VPN so can't help much.

If you (or anyone) have a tested working set, please share. ;)

Which Gapps zip, in what condition etc.

It might ease the life of the others.

Good to know that!

BlueZ only finished the support for Kitkat. LP is not complete yet. I hope it will be available soon.

You may check post#2 for detail.

No. Only the keyboard have such settings. It is not difficult to do but seems not on CM's list.

I'll keep an eye on other ROM for something like that.

1. I think you have bad contact on the SIM and/or the slot. You may clean the contact points of the SIM card and try again. Unplug and re-plug is a kind of scratching the contact point.

2. Omni and CM has minor difference in RIL. The patch for Omni is not necessarily fully working on CM and I don't recommend you to do so.

3. This is rather a leftover from earlier version of Android. The root access in dev. options is not relevant if you have flashed SuperSU. The binary will be replaced. Of course, you have to use the right version of SuperSU (I have tested 2.46, 2.52 and 2.62)

The state shown (just for display) will be resume not just after reboot but after you left Settings.
[Galaxy Tab 7.7 Android Development] nshahril:
My CM13 doesn't even survive for a day with lots of crash and fc after installation of apps.

I also tried the omni but no succeed avail during the trial for my old P6200.. So up to before my bedtime, I'm still trying for the last effort before going back to slims if failure upon my trying.. Hehehehe... I'll do the best I can to stay with this version..
[Galaxy Tab 7.7 Android Development] betexino:
some times auto rotate doesn't work for me need reboot
[Galaxy Tab 7.7 Android Development] nshahril:
Sadly to say, I'm going back to Slim's after numerous efforts to use this lovely ROM.. But I will keep watching the updates and progress of this ROM in future for our old tablet. Cheers all..

---------- Post added at 08:11 PM ---------- Previous post was at 07:41 PM ----------

Hello sir,

The last configuration that might works with CM13 that I'd tried was with the gapps-base-601-20151209 zip which auto rooted through the dev options only...

Its started being weird once I update the root binary with the supersu app and keep on failing and fc and crash often once I keep installing the apps from the playstore...

All other combinations including the open gapps, tkgapps, slims alpha gapps are useless which not even passing the login WiFi with the aosp keyboard failure and so on...

And now I'm going back with slims kk as daily driver while replied this msg ... [emoji29]
[Galaxy Tab 7.7 Android Development] Harrison Le:
My Tab P6800 work well with all CM13's org. apps but it still beside me for work and relax so must run well with my daily used apps as fb, office, pictures...This CM13 really smooth but seem system running heavy and some big data apps no work so after try it I have to back omni 6.0. This rom is best to my p6800 so far!

Sent from my P6800 _ omni marshmallow
[Galaxy Tab 7.7 Android Development] dmjcnd1:
yesterday I have flash with omni-6.0-20151205 and gapps-601-base-20151209-1 for my friend old P6200 Tab's. And he report to me after, that the SIM or Telephone not work (no reading only WiFi).
[Galaxy Tab 7.7 Android Development] betexino:
can't receive or send files or pic with bluetooth or shareit :( , rom rebbot some times when install apk with last build (16\12) , open gapps 6.0 works for me , su v2.46 and xposed installer 78 sdk23 too

gracias daniel_hk , hope u will give a try with RR ROM :p
[Galaxy Tab 7.7 Android Development] Mrxyzl:
Bug report

So after the latest version of omni (16/12), i experienced

1 random reboot a few times,

2 cannot restore app by titanium backup ( titanium stay 0% forever)

3 Cut off sound at low volume (maybe kernel related)

4 Bluetooth cant send or received file
[Galaxy Tab 7.7 Android Development] daniel_hk:
If you ever read the thread, you would know (and how to fix).

Next time, read before you post.

1. I is already mentioned in release note and post#2. Read before you post... ;)

2. System is less stable when Gapps are installed. You may try installing Gapps after all your apps.

3. I had built and posted RR for my Nexus7 2012. I also uploaded a bug fix (they forgot to remove some unused old code) which was already reported a few times. There was no respond at all. The bug was "fixed" by a new code merge (which delete the faulty old code) a few months later.

I think a responsible ROM maker should look into there bugs. I don't want to waste my time. It is just not good enough by my standard and there are many better options. :)
[Galaxy Tab 7.7 Android Development] Harrison Le:
Hi [MENTION=4948627]daniel_hk[/MENTION],

I have no idea about building or fixing rom but have tried all omni 6.0 but final take only build 20151124 because except camera, bt...no work then all other apps running very well ,system works smothly that better than other build which comlete basic apps but os not run well, may you just base on that build to fix separately for camera and some else!

He he sorry for my stupid idea:)
[Galaxy Tab 7.7 Android Development] uli-hh:
I've installed the latest onmi rom, with SuperSu 2.52 and open_gapps-arm-6.0-nano-20151216 on my p6200.

I was able to restore my apps with TI-Backup from ext. SD. So far so good.

But when I try to backup new apps to the TI-BU-folder on ext. SD it says: Batch backup interrupted: insufficient free storage..

and when I look in TI BU settings it says: This folder is not writable.:confused:

Is this a MM- or a SuperSu- or a TI BU-problem?
[Galaxy Tab 7.7 Android Development] Mrxyzl:
Well, I think MM does not allow to write on Extcard like Kitkat. But you can choose Extcard in titanium by preference/backup folder location

In the new popup, above the Detect button there is a "Storage provider" line, select it and Choose Extcard. It works for me.

Cheers!
[Galaxy Tab 7.7 Android Development] uli-hh:
I did that already but as you can see below I can't select "use the current folder". The only possibility is "cancel"!

edit: now I've got it!

At the screen shot above I've had selected the SD card

and

untruly also the folder "TitaniumBackup" within the DocumentProvider storage menu.

But when I only select SD card and then choose the folder "TitaniumBackup" within the Backup folder location window it works!

There was a message that all the backup files are now moved to "external storage".
[Galaxy Tab 7.7 Android Development] hogig:
Hi there,

I tried cm 13 and Omni, the sd card adoption dpes not seem to work. The formatting works for a long time and then the card is indicated as corrupted (which it isn't) or it would go to the prompt re moving of data but settings would then get an error then FC?

Thanks.
[Galaxy Tab 7.7 Android Development] aemee:
Flashed the 14 Dec Omni build, i believe.

Overall performance was better than lollipop like others have stated.

Had no problems with gapps not having permissions at boot. Unsure if its because i am using open gapps or its because i just wipe everything to smithereens before flashing.

Same problem here with downloads except that i am able to download but it lags the heck out of the tab. Permissions seem fine and for some reason, never had to manually set/enable the permissions per app. It just starts to lag really bad whenever a download is in progress.

To those who are using Dolphin HD Browser and are experiencing some sort of slow page loading/lag, try disabling Dolphin Jetpack in the dolphin settings if you have it installed. Do that and you can see a huge difference of loading times. What took seconds to load took about 5 mins to load with Jetpack enabled. Im just assuming that Jetpack is not yet optimized for 6.0

Having similar troubles with wifi dropping its connection. Wifi will constantly disconnect itself whenever the tab is unused/locked for a period of time. Does not drop if i am actively surfing the web/youtube etc. Placing the tab directly beside the router did not change anything. Still drops the connection if not actively used.

The last bit that i have observed is that wifi does not automatically reconnect/connect to saved connections whenever the connection is dropped or reenabled from quick settings. Connecting to an AP is also impossible via wifi quick settings, the AP SSIDs cannot be tapped. It acts like there is no form of possible interaction. There is no highlight when tapping and holding on any of the SSIDs.

Still, i prefer this over lollipop any day. Less lag, smoother response.

Thanks daniel_hk
[Galaxy Tab 7.7 Android Development] nshahril:
[MENTION=4948627]daniel_hk[/MENTION] I wish you have the same 7 plus p6200 instead p6800...
[Galaxy Tab 7.7 Android Development] Mrxyzl:
[MENTION=4948627]daniel_hk[/MENTION] Sorry for the uncertainty in the cut off sound at low volume. It was cut off sound at low volume when using earphone , specifically it was the S3 earphone with every rom you build ( slim 4.4, carbon, omni 5.1....) Now that i thought about it, maybe I will try with other earphone to see if the problem exists.

Edit: Well turns out the problem persist with other earphone. Just listening to some song at the lowest volume and the sound will cut off. For example this song https://www.youtube.com/watch?v=pY9b6jgbNyc
[Galaxy Tab 7.7 Android Development] philipnzw:
I've also had this problem! And yes I'm on most of Daniel's builds too

Tested with few earphones ,sound randomly cuts off at low volume setting too, sometimes softer sounds don't play

I don't understand coding at all so it might be software issue :(

My guess is that when at low volume ,there is not enough electricity supplied to our earbuds, so it just becomes silent

Anyway , I downloaded an exposed module(volume steps) to give me more precise volume, and I just set the volume 1 step louder than the silent step, that way the sound is soft ,but still hearable

Hope this helps
[Galaxy Tab 7.7 Android Development] Mrxyzl:
N7000 useres also had this problem but were fixed in omni http://xdaforums.com/showthread.php?t=2186576

Cyanogen mod also have a patched for this http://forum.cyanogenmod.org/topic/73718-sound-switches-off-below-a-certain-volume/
[Galaxy Tab 7.7 Android Development] daniel_hk:
Sure, It's Christmas. I wish someone could send me one before abandon it in the boxes of warehouse. :D

According to the reports from Tab-plus users, only one issue is on top of those in p6800. It is the green line at preview of Camera. Output is OK. I have put some debug code in the latest Omni6. Wait for someone to send me the log after taking a picture.

I was thinking my builds are more or less the same for Tab plus and 7.7. If otherwise, just report with details. ;)

I only got an earpiece from my Nexus One (Yeah! the great grand father of Android). I seldom use it.

So it is a common and know issue. I just go through the links [MENTION=6642180]Mrxyzl[/MENTION] provided. Seems there are already solutions for this.

I might take a look when return home.

In the mean time, here are what I recalled:

1. The kernel audio driver are from Samsung. They are the same since ICS (may be HC too).

2. Start from JB, we are using the tinyalsa which replace the blobs from Samsung. I don't know if same issue persist in stock ROMs.

3. In other devices, there are settings in Engineer mode for audio including volume.

4. I remember in /system/etc, there is a xml file (tinyalsa...xml). In the <output> section, there are gain and max. volume control for each profile.

1. I add an apk permission script in init.d in the latest build. It will fix the Gapps permissions at boot.

2. For Wifi, if you are using 5G, it is a know issue since JB. Our wifi chip (or antenna) only works on the lower bands of 5G.

Work around: I used the app Wifi analyser scanning for some time. I fixed the channels of my router to those no one use in my coverage. For p6800 (and p6810 I suppose), my final settings are:

Channel 3 for 2.4G and 149 for 5G.

After that, I don't have problem connecting any more.

BUT for i815 (I think the antenna is different), I still can't find a workable setting for 5G so I use 2.4G.

See if the same settings would help you. ;)

Good luck!

Just heard a Christmas carol. Merry Christmas to all
[Galaxy Tab 7.7 Android Development] Harrison Le:
Ha ha ha....all of us make [MENTION=4948627]daniel_hk[/MENTION] be crazy!

Still so early but MERRY CHRISTMAS To YOU, [MENTION=4948627]daniel_hk[/MENTION]!

Post by P6800 with Omni MM 6.0.1
[Galaxy Tab 7.7 Android Development] hogig:
Dear all,

Daniel has indicated that he has tested a single sd micro to work with in adopted mode. I have tested multiple cards, none worked.

Anyone else has adopted sd micro card mode as internal storage working properly?
[Galaxy Tab 7.7 Android Development] galoneta:
Master daniel, reporting about build dec / 16 on my p6210:

1- installed from twrp all 3 files in one step with success: omni-6.0.1-20151216-p6210-HOMEMADE.zip, open_gapps-arm-6.0-pico-20151219.zip and BETA-SuperSU-v2.52.zip.

2- camera works fine

3- lot of random reboots with ligh overclock and extra apps

Saved this build with twrp. Not for my daily driving yet. Tell me if you need some other test/report.

Thanks again.
[Galaxy Tab 7.7 Android Development] p3dboard:
[MENTION=4948627]daniel_hk[/MENTION] - I just tried the CM13 build from 22-Dec on my p6810, and it hangs on the Samsung Logo - I think this happened last time on the initial build, then you updated the rom to fix this.

Thanks - Peter
[Galaxy Tab 7.7 Android Development] Mrxyzl:
Stuck on samsung logo

I installed CM13 on my p6810 and it stucked on samsung logo too
[Galaxy Tab 7.7 Android Development] daniel_hk:
I haven't changed the kernel for a few builds. Last two Omni also use the same kernel so I don't think its the kernel setting as the last cm-13.0.

To verify that, you may replace the kernel (boot.img) with the one in the last build.

In the boot sequence, I only changed the gps daemon which is unlikely the cause.

I just found out that I haven't updated the gpsd in p6810&p6210. Another careless mistake...:o Flash this View attachment gpsd-patch.zip would fix the gps daemon.

The only thing I can think of is the PerformanceControl. If you have select the vpll in previous builds, it might hand the GPU at boot.

In TWRP (or previous builds), see if you find the folder in /sdcard/.PerformanceControl. If yes, delete the .PerformanceControl folder would fix it.

CM handles init.d differently. This might cause the system to hang if you have select the vpll in Omni earlier.

I planned to rewrite that part. Seems it the time now... :silly:

Good luck!

Edit: I just modified the zip for p6810 and flash to my p6800. Yes, it stuck at the Samsung Logo. I then use the old boot.img from 20151210 build. It works. So there is something wrong in the new kernel. Need to find out why.

For the time being, you my replace the boot.img inside the zip with this View attachment boot.img. OR flash the image after the ROM. I'll replace the zip in the hosts shortly.

I just unpacked the boot.img. I know why now. The initramfs for p6810 is corrupted so it can't boot. I just repack and uploading the new file to the hosts now. Sorry for the troubles. ;)
[Galaxy Tab 7.7 Android Development] philipnzw:
Installed 22/12 cm13 on p6800

Everything runs fine but ,Screen flickers randomly ,black lines flash across the screen

Am I the only one ?
[Galaxy Tab 7.7 Android Development] Harrison Le:
[QUOT E=philipnzw;64447765]Installed 22/12 cm13 on p6800

Everything runs fine but ,Screen flickers randomly ,black lines flash across the screen

Am I the only one ?[/QUOTE]

P6800 do not be stucked logo, setting OK but screen be flashing quite open and running seem heavy!
[Galaxy Tab 7.7 Android Development] daniel_hk:
I notice that too. I think it's a CM's bug. I make several builds a day. I noticed that a day or two before I release the 1222 build.

A point to note: After I clean the light sensor (top of the screen), it seems better. Might the the sensor service broken or problem of the adaptive brightness routine. Lost sync might be another possibility.

I'll take a look after Christmas. ;)

Edit: I just turn off the adaptive brightness in Settings > Display & lights. Seems the flickering is better now.
[Galaxy Tab 7.7 Android Development] nshahril:
Hello master [MENTION=4948627]daniel_hk[/MENTION]

My Christmas comes early this year... I am be able to install your rom using your latest build with base gapps of Android M 6.0.1.. Although with some hiccups at the early stage of installation. Pics speak thousands words. ?

View attachment 3585720

View attachment 3585721

View attachment 3585722

The ril ain't working so thus the Bluetooth.. But who cares.. I can use this old chap as an Internet browsing.. That's fine with me.. May be there's some fix.. But I'll do it later... I'm a happy man now.. Merry Christmas to you sir and everyone.. Cheers [emoji41]
[Galaxy Tab 7.7 Android Development] betexino:
Happy Christmas all

Boot up without problems on my 6200

Poor batterie , will report soon if something wrong
[Galaxy Tab 7.7 Android Development] saddhaviro2:
Daniel,

Merry christmas and thx for your hardwork for porting android 6 to our tab.

I just installed your omni 16dec build for P6200.

Tried to take picture and here is the logcat for camera that you ask. Hope it will help you to fixed camera issue for P6200.
[Galaxy Tab 7.7 Android Development] GNUDroid:
Thanks to you [MENTION=550003]Danielhk[/MENTION]!

For months i stock to an old build, discontinued to try newer ones (all had been somehow slow). Now you even supported until mashmallow. Crazy! :)

Comming to mm builds:

- 16. Dec build of omni randomly crashes at hard loads (examp!e google earth some minutes). But its blazing responsive. Very very promising. Tab never had been faster at surfing

- 22. Dec. Build of cm is much laggier.

Just because of curiosity (don't answer if you short of time, no problem!):

1) - I'm just asking why the above behaviour? What is the differences? What do you think: its more the kernel related stuff or has omni the slimer framework?

2) - Also related to speed: does the overclocking of gpu (offered under performance in settings in omni) actually work? Or is it just a residual of o

dder code? At least the vpll option does not work for me (shall be toggled + reboot, but if doing so, its deactivated)

Thank you and have nice days!
[Galaxy Tab 7.7 Android Development] daniel_hk:
I seldom ignore anyone, especially to old friends. :D

1. CM gain a lot of weight I suppose. If you installed Gapps, just leave it for 10 more minutes after the first boot. It might require extra setup in the background. There are few processes in the Play Service not working yet. Need to wait for the timeout and failed. It might be just in my area. I can't verify that...

Omni is surely lighter and closer to AOSP. This might be a trade off for performance and features.

The last Omni doesn't fully working with the latest Gapps. Without it, random reboots would be gone. I fixed the GPS and drm in the last CM. It would be better compatible with Gapps. The log would tell you that.

Both ROM use the same kernel but I forgot to update the gpsd for p6810 in the last CM. Try the gpsd-patch I attached a few posts above. See if it help.

2. I added the GPU control to Omni's PerformanceControl since KK and it is still working. Antutu and similar Apks show the difference. A separate Apk is provided in CM too. I just can't make vpll working yet. It might hang at boot so I disable it. Without vpll, GPU can still reach 400Mhz. Kmsg will show you the current clock. For my tab, 975mV for 100Mhz and 1150mV for 400Mhz would be stable.
[Galaxy Tab 7.7 Android Development] GNUDroid:
Wow, very useful information. Thank you.

First nice to know that i have to keep newer gapps in focus (realy they or also the rom needs more compability adjustments?). Also nice to know about the overclocking voltage / mhz combination.
[Galaxy Tab 7.7 Android Development] galoneta:
Master daniel.

Reporting about latest cm 13 in my p6210.

Tried flashing cm-13.0-20151222-UNOFFICIAL-p6210.zip with and without gapps / super su, but the result is the same: stuck at galaxy boot logo for many minutes!

Reverted back to carbon 5.1.1, rock stable so far.

Thanks
[Galaxy Tab 7.7 Android Development] Mrxyzl:
Sound cut off fix

Hey [MENTION=4948627]daniel_hk[/MENTION], after your suggestions about tinyalsa.xml in etc folder, I've tried to change the value as in attachment and the bug seems gone!

That's awesome suggestion :highfive: now i can use my tab to listen some music before sleep!

Edit: Further testing today, with the "Headphone Playback Volume" at 10 the bug was only reduced (only at the lowest volume, the bug reappear) so i tried to change the value to 5 and now the bug gone for good. I test the tablet all day today and found no problem after changing to 5.
[Galaxy Tab 7.7 Android Development] daniel_hk:
OK, if this is confirmed I'll commit the change. Anyone second the confirmation would be appreciate.

Points to note:

1. "earpiece" means the upper speaker (next to the front camera), I don't think it is related.

2. The difference between "headphone" and "headset" is, "headset" has a mic (input pin)
[Galaxy Tab 7.7 Android Development] theslydog:
cm-13.0-20151222-UNOFFICIAL-p6210.zip with gapps-601-base-20151209-1-signed.zip and Super SU are actually working pretty fine for me. on a P6810 with TWRP 2.8.7.1

Nova launcher with no dock is so far going ok.

Only thing not working that I have tested so far are the Sound in Settings, Device, Sounds. This is a common bug in this rom on other devices as well.

It also on screen buttons after a while - home button etc pulse when touched. Seems to fix after it screen off and back on.

But over all pretty good Daniel
[Galaxy Tab 7.7 Android Development] saddhaviro2:
Camera bug in P6200

[MENTION=4948627]daniel_hk[/MENTION],

I already tested your patch,but result still same.

So i clear data then install your patch then clear dalvik cache.(hope my steps not wrong).

After boot, when i run camera, still see green bar on screen. But when i want to change resolution for rear camera, option for 16:9 ratio was missing.(it was there before i flash the patch)

And here is the logcat.

Thx for your hardwork daniel.