yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] humberos:
Why do you want newest cwm version?

You can flash Omni ROM using any custom recovery version.
[Galaxy Tab  Android Development] Ichijoe:
I'm not pressing with this, as I've since moved on to using pair of BlueTooth Cans, that have their own problems.

Namely In-band Ring. But, I gather this is a general core bug, in Android. Its not like my Galaxy S (GT-9000) with its stock Gingerbread 2.3.3 is any different, 'cause its not.

But, the wired Phones (that is the Call / Hold Button), is still not working in the current 4.4.3 -10140606-p1 build.

I'm not sure if you had done anything yet or not though. But, if you can keep me informed of any "changes" I'd be more then happy to test them out for you...
[Galaxy Tab  Android Development] ulev:
First impression 4.4.3

I have tested the first 4.4.3 version for 48 hours by now. Everything seems to be a bit more stable in my heavily loaded environment.

I have noticed 1 bug though: whenever I create a third page in Launcher3 for an extra group of app shortcuts that page disappears with the next reboot and I am back to the initial 2 pages...
[Galaxy Tab  Android Development] Ichijoe:
Sometimes I to have ran into a similar problem, but with the Google Now Launcher. It'll start with One of my Widgets disappearing for no explainable reasons, and then the rest of my "Widgets" (spread across 4 (or 5), Pages, also getting wiped clean on the subsequent boot.

It has happened with such regularity that I really haven't been to arsed about fighting it. I think I have a singe Beautiful Widgets (Weather & Clock) Widget kicking, as well as the Facebook, and Google Sound Search Widgets installed.

Perhaps its a RAM limitation, and, having all those "Widgets" open is eating up to much of it?
[Galaxy Tab  Android Development] priyana:
For me, on Google Now Launcher, so far only the free XDA App that can't stick on the page. No matter where I stick it, it is gone after reboot. Doesn't happen to other apps, even if I stick them after XDA.
[Galaxy Tab  Android Development] leleobhz:
My earphone works with my Razr D3. Its a Phillips for cellphones. Also, in storm31 ROM, the button works like a glove, just the phone call volume is very low. But omni does not really recognize the button function. So now its 2 issues about earphones.
[Galaxy Tab  Android Development] humberos:
patch 1: low in-call volume bug:

https://gerrit.omnirom.org/#/c/6832/

patch 2: headset button

http://I_will_check_when_I_get_free_time.com
[Galaxy Tab  Android Development] leleobhz:
404, time not found. Please use TARDIS as time proxy.

About patch 1, its in the latest binary update or just in nightly? Im with 4.4.3-20140609-p1-NIGHTLY running now (But call not tested yet in this version).

EDIT: Call volume still low in this version BUT DTMF tones sounds relatively high! Just the call is low.
[Galaxy Tab  Android Development] humberos:
Oh!

Nice to know! So, It works!!!! LOL

The status of this patch is the main secret... (by Dungeon Master)
[Galaxy Tab  Android Development] alessandronip:
Hi all.

I have casual blocks of some sensors.

The screen rotation does not work anymore and I have to reset.

Attached logs.
[Galaxy Tab  Android Development] Ichijoe:
I see from your "Picture" that an Update was available at the time you took it.

Running that Update 20140610? Everything has registered on my P1000 (Int'l GSM), on AndroSensor. Sans the GPS which I leave off to save the Battery.
[Galaxy Tab  Android Development] humberos:
TV -> out

FYI

https://gerrit.omnirom.org/#/c/7926/

Unfortunately TV -> Out
[Galaxy Tab  Android Development] thesniffer:
Do i need to restock to flash last nightly version?

I'm still on 27 of april nightly build.

Thanks in advance ;)
[Galaxy Tab  Android Development] humberos:
Nope!

Just wipe cache (also dalvik) and system partitions before install.

I advise you to installing 20140611(next build).

Enjoy!
[Galaxy Tab  Android Development] Ichijoe:
I might be missing something here, but isn't the "current" (as of my writing this)... 20140610?

No doubt 20140611 is coming.... Soon but, its not to my knowledge out yet...
[Galaxy Tab  Android Development] humberos:
I "advised" to installing 20140611... and yes it is coming.

So, no problem if he want to install 20140610.

Sorry, but really not matter to discuss this point.

http://jenkins.omnirom.org:8080/job/nightly/
[Galaxy Tab  Android Development] valtlfelipe:
Hi Guys,

Sorry asking, but i couldn't found an answer for that. Does this work for the P1000N version?

Thanks in advance.
[Galaxy Tab  Android Development] storm31:
Probably this can help, it does work for my rom (cm11 based): http://xdaforums.com/showpost.php?p=53314277&postcount=2902 or here: http://review.cyanogenmod.org/#/c/65608/
[Galaxy Tab  Android Development] humberos:
Nice!

I will pick it.

Thank you!
[Galaxy Tab  Android Development] humberos:
FYI

I got wired headset fixed.

I am just testing kernel stability right now.

https://gerrit.omnirom.org/7967/
[Galaxy Tab  Android Development] humberos:
Wired headset

Hi [MENTION=535343]all[/MENTION]

As I said before, I am working on wired headset driver.

I want to get Next|Previous song by button hold|release events, but I don't have this headset for tests reasons.

So, can somebody test it?

Thanks!
[Galaxy Tab  Android Development] leleobhz:
I do. What i need? I van compile things too but i need to know how Android/omni environment works (since i only know how to crosscomp linux and netbsd pure binaries)

Tks!
[Galaxy Tab  Android Development] humberos:
[MENTION=1624729]leleobhz[/MENTION]

Here you go.

http://goo.gl/s7M0Cj

Just install this build and let me know.
[Galaxy Tab  Android Development] Mjoelnir77:
dirty flashed it on top latest official omni

first tried it with an original Notes 3 headset - did not work

i then tried it with the original tab headset after digging down several cubic meters of paper on my table^^ - works

after that tried the notes headset again and that now also works, even all 3 buttons (+ and - do not control volume but jump back and forth in Google Music)

I do not know whether i first did not connect the plug correctly or "our" headset triggers a proper initialization, but anyway - your patch works

Thank you!
[Galaxy Tab  Android Development] humberos:
Nice!

Are you meant that you have a headset with volume keys?

At least I worked only on 3 events:

Play/Pause Media

Next Media

Previous Media

So, I can work on volume keys. I just want to know what adc values the kernel shows (by /proc/kmsg) when you using these buttons.

I want to know about Voice Dialer or Google Now, did you have test it too?

Just hold the Play/Pause Media button for a few seconds.

I think that we can merge the first one with 3 events at moment and will try to work on volume events later.

Edited:

should we use Volume events instead Next/Previous media events?
[Galaxy Tab  Android Development] humberos:
Poll - For Headset events

So, I think that we'll need another poll for headset events.

Actually the original Galaxy Tab headset have only one button (KEY_MEDIA) for Media Play/Stop (voice dialler and Google Now).

BUT we can use another kind of headset (using compat adc values) with 3 buttons.

I want to know what functions will be more useful to us.

We have these options below:

First

KEY_MEDIA

KEY_PREVIOUSSONG

KEY_NEXTSONG
​

Second

KEY_MEDIA

KEY_VOLUMEDOWN

KEY_VOLUMEUP
​

________________________________________________________________________________________________

FYI (adc values)

{
/* 0 <= adc <=110, stable zone */
.code = KEY_MEDIA,
.adc_low = 0,
.adc_high = 110,
},
{
/* 130 <= adc <= 365, stable zone */
.code = KEY_PREVIOUSSONG, //KEY_VOLUMEDOWN ?
.adc_low = 130,
.adc_high = 365,
},
{
/* 385 <= adc <= 870, stable zone */
.code = KEY_NEXTSONG, //KEY_VOLUMEUP ?
.adc_low = 385,
.adc_high = 870,
},
[Galaxy Tab  Android Development] alessandronip:
Audio issue

Hi all.

I have the following error. If I connect the TV cable (RCA) audio disappears and I have to reset.

The fault is present with the rom 20140610 and 20140612.

I also have problems charging the battery, sometimes it charge quickly and sometimes not in a totally random.

Tested with various cables and power supplies, even the originals.

Attached logs.
[Galaxy Tab  Android Development] safety1st:
RNGD Starup failed during Seeder instalation

I know its a bit off topic, i been testing Omni rom on my old tab P1 (from previous to latest build) but i always got this error "RNGD Startup failed" during Seeder installation, (Seeder is a big help for me, it reduces lag during heavy games on P1) I never got this problem on CM Rom or other CM device tree user. Can anyone help me out on this one:confused:

Thanks....
[Galaxy Tab  Android Development] leleobhz:
Confirming, button works. I dont have a earphone with volume control but i can try with some cheap earphone just to get the values, will not kill me buy one.

EDIT: Call volume issue still exists.
[Galaxy Tab  Android Development] humberos:
What TV cable are you using?

About charging, I checked your logs but can't find any error from them.

Sorry I can't reproduce this issue.
[Galaxy Tab  Android Development] alessandronip:
The cable is a generic analog AV adapter with three RCA connectors used as a battery charger.

Regarding the second issue, I have no errors, seem to be unable always to determine the power of the charger.
[Galaxy Tab  Android Development] humberos:
From 30pin to RCA & USB are you meant?

I asked because we have another kind of Tvout cable. It works from headset to RCA. But I never used thid cable.
[Galaxy Tab  Android Development] alessandronip:
Yes, is the 30 pin to 3 RCA and USB.

----edit

I did a test now.

The first time I showed not in charge but the audio worked.

The second time I showed charging but the audio was gone.

I'm confused!
[Galaxy Tab  Android Development] Mjoelnir77:
I am not really experienced with the logging stuff, hope the attachement helps which is the output from dmesg directly after i pressed the three buttons a couple of times. If you need more please tell me what i have to do.
[Galaxy Tab  Android Development] humberos:
Oh! No problem!

I was thinking that if the volume keys from your headset is changing music tracks then the values are the same....

But I didn't understand if your headset have 3 or 5 buttons.
[Galaxy Tab  Android Development] humberos:
Thanks [MENTION=4430830]alessandronip[/MENTION]

It is enough for me.

I will work on this cable at weekend and let you know about.
[Galaxy Tab  Android Development] safety1st:
No display during call when tab is locked

I just noticed that during incoming call display is not responding when tab is locked:confused:
[Galaxy Tab  Android Development] Mjoelnir77:
http://ecx.images-amazon.com/images/I/611WOQnvJVL._SL1500_.jpg It is this.

Btw, default behaviour of the buttons and additional behaviour of multiple clicks can be controlled by https://play.google.com/store/apps/details?id=com.shengande.degausslabs

Just tested it to set "+" and "-" to vol up and down and double click to back and forth (like your current ROM standard for single clicks) and it works.
[Galaxy Tab  Android Development] humberos:
Nice to know!

So I will merge the patch adding native support to Next and Previous song.

If any user will want to change this behaviour then just install the headset buttons app control.

Thank you!
[Galaxy Tab  Android Development] safety1st:
Its weird, on your Homemade rom my skullcandy headset is working to change the next song, but when i clean install latest build (20140613) changing next song is no longer working
[Galaxy Tab  Android Development] humberos:
I merged all patches last night and it will available at 20140614 (next build) .
[Galaxy Tab  Android Development] safety1st:
Custom ROMs, assemble!﻿

[MENTION=3031478]humberos[/MENTION] Android 4.4.3 Now Live In AOSP checked: http://www.androidpolice.com/2014/06/02/android-4-4-3-now-live-in-aosp/ :confused:
[Galaxy Tab  Android Development] humberos:
June 2th isn't now.
[Galaxy Tab  Android Development] alessandronip:
Apparently the charge issue is solved with the build 20140615.

Remains the problem of the audio.

Two additional small errors.

Many sounds are duplicated in the list as you can see from the screenshot.

This happens from the Build 20140610.

Check for updates not showing me the build 20140615.

After you have installed manually now tells me that there is an update and proposes me the build 20140613.

Thanks. Paolo.
[Galaxy Tab  Android Development] priyana:
No sound duplicates issue on 20140615 here.
[Galaxy Tab  Android Development] alessandronip:
I found the cause.

The sounds are in an old rom CM10.1, I unpacked the ZIP file.

Deleted the directory duplicates are gone.
[Galaxy Tab  Android Development] humberos:
Yup.

I got it fixed.

Thanks!
[Galaxy Tab  Android Development] leleobhz:
Do we have some light in the end of the tunnel about the call volume issue?
[Galaxy Tab  Android Development] humberos:
I did some change in kernel and increase volume (in call) when headset is plugged.

The kernel shows support at 30db as max. But I think that it is not true. I can't increase it at 30db, but I did the the light in the end of the tunnel for now by increasing the volume a little more.
[Galaxy Tab  Android Development] leleobhz:
I dont know if the call subsystem is the same of the entire sound subsystem but Voodoo Patches does not help anything? Also, in the background, Android appears to use ALSA in kernel and some other sound server for android subsystem. Its right?
[Galaxy Tab  Android Development] humberos:
Voodoo is present in kernel but it is using "wm8994 extensions" name.

I found a kernel #ifdef error on sound extensions driver and I am working on it right now.

I will let you know asap.
[Galaxy Tab  Android Development] white-energy:
Guys.. what about the camera/video issues seen on other 4.4 roms.. are they present on this one?
[Galaxy Tab  Android Development] humberos:
No.

It isn't mandatory.

you can use gapps from this:

http://docs.omnirom.org/Installing_Omni_on_your_device

Enjoy!
[Galaxy Tab  Android Development] white-energy:
Well, i've decided to try it on my own and... it seems like the video recording issue is still present.
[Galaxy Tab  Android Development] adi6262:
This is just brilliant! Many thanks to all devs :D

Could you merge advance settings from sgt7 into this? Or any method to disable capacitive keys? Thanks again!
[Galaxy Tab  Android Development] Ukitaki:
Yes, Video recording is not working yet, but if you need it, try snap camera for this. But be attention, do not make fotos, because it turn off your Tab.

Issues i found:

- HDMI is not working (i gues it is not support at this time, here is logcat View attachment 2559993)

- then i change music in Appolo DSP manager is FC (here is logcat View attachment Log_2014-02-05_10-05-11.txt)
[Galaxy Tab  Android Development] stimpz0r:
i assume you tried to enable Stereo Widening? your issue with DSP Manager should be fixed soon... https://gerrit.omnirom.org/#/c/5343/

as for HDMI, it has been disabled for now, but [MENTION=3031478]humberos[/MENTION] will probably work on that one when he gets the chance again (if he has a HDMI cable to test with).

oh - p1c users, your official builds will start as soon as i can confirm i have a working build... since i don't have the tablet yet, this might still be a little while off (but test builds so far have proven to be working). keep watching in here. ;)
[Galaxy Tab  Android Development] Ukitaki:
Default file manager (documents) can not open any apk. Is it normal or issue?
[Galaxy Tab  Android Development] salahmed:
I think it's for security reasons. And it is the same as Omni ROM on other devices.
[Galaxy Tab  Android Development] adi6262:
Is it possible to avoid formatting system for every nightly?

Because then I have to reflash gapps after every update...
[Galaxy Tab  Android Development] maihuuquan:
How can I root it?

I installed but I could not use sd-card with rootexplorer. It said need root.

Thanks
[Galaxy Tab  Android Development] salahmed:
The ROM comes with no root. After flashing the ROM and Gapps. Flash SuperSU zip. The link in the first post.
[Galaxy Tab  Android Development] maihuuquan:
Thanks. I"ll do it :good:
[Galaxy Tab  Android Development] Ukitaki:
I made update from nightly 04.02.14 to 05.02.14 and all my apps (and gapps also) were restored automatically. I use micro gapps
[Galaxy Tab  Android Development] maihuuquan:
I have 3G but can not use 3G.

Please fix it. Thanks
[Galaxy Tab  Android Development] salahmed:
First check your imei to see it is correct. And which Nightly date you are using. There is a new one dated 6 Feb and by the way also a new Gapps.
[Galaxy Tab  Android Development] Ukitaki:
3G works fine! I'm on 06.02.14 build
[Galaxy Tab  Android Development] Cleverfish:
usually i didn't format system when updating, just wipe cache and dalvik cache.

---------- Post added at 01:29 PM ---------- Previous post was at 01:24 PM ----------

did you lost your imei number? check in Settings>About tablet>Status. if your imei is generic number (starting with 0000..), you have to restore backup of your EFS folder.
[Galaxy Tab  Android Development] Ukitaki:
sorry for my English, i try to explain what settings i want to see in OnmiSwitch

I like OnmiSwitch very much! it is very easy to switch apps with one big finger then driving a car, but i`m a right-hand person, and it is a big problem tap on the first app, because apps-aling is left. Is it possible to add settings it OnmiSwitch that makes apps-aling to right
[Galaxy Tab  Android Development] storm31:
[MENTION=3031478]humberos[/MENTION], maybe you can solve this: http://xdaforums.com/showpost.php?p=50002480&postcount=62, pawitp can't help us: http://xdaforums.com/showpost.php?p=50031299&postcount=2033 and http://xdaforums.com/showpost.php?p=50032293&postcount=2034.
[Galaxy Tab  Android Development] Mjoelnir77:
Tried to dirty flash (no factory reset/restock, only format /system etc) the Rom coming from CM11 on ART. It did boot to the "Enter SIM Pin" screen but rebooted instantly. Removing SIM and extSD did not change the instant reboot effect. I then switched to the latest P1000 storm31 CM11 as i did no want to recreate everything back from Titanium backups after a factory reset. Will probably try sometime later again.
[Galaxy Tab  Android Development] leleobhz:
I know, i use the Voodoo APP to control Audio direct DAC/ADC. Bit i dont know if Voodoo patch can also controll call process.

Ill stay tuned and available to test.
[Galaxy Tab  Android Development] humberos:
in call volume - issue?

Please, could another user confirm in call volume (low) issue when headset is plugged.

I am testing it (on P1000L) here and I can't reproduce this issue.

I mean, it is working fine for me. The volume is good.

Thanks!
[Galaxy Tab  Android Development] leleobhz:
Humberto, mine is P1000N with P1000NUBJP3 baseband modem. If you recommend, i can try to get more logs or other flashes, including modem.
[Galaxy Tab  Android Development] alessandronip:
Audio issue and email internal error

I found what caused the audio error.

When connected to the TV OUT cable, the audio output is redirected to tv.

Even if the TV output is disabled.

Even if the cable is removed.

I also have another error, this time with the email.

If I try to send an email program gives me an internal error.

The mail server is exchange.

I have attached the logs.
[Galaxy Tab  Android Development] humberos:
Yes, I changed the audio routing when we plug TVOut cable or lineout from DeskDock.

Commit reference: http://migre.me/jTnbO

Are you meant that audio routing isn't working when you remove the cable, right?

Sorry, could you open a JIRA ticket for Omni Team with this issue related?

http://jira.omnirom.org/
[Galaxy Tab  Android Development] alessandronip:
Yes, after removing the cable the sound still does not work.

For the issue of email I will open a ticket.

-----Edit

I'm trying to open a ticket on JIRA but the P1000 is not present between the devices.

How do I open a ticket?
[Galaxy Tab  Android Development] humberos:
Sorry, just for sure.... But it works when you get tvout cable plugged, right?

I've tested here and I got Tab sound routed to TV by RCA cables... I mean the audio routing worked when cable is plugged.

But I didn't test it if the audio routing back to speakers when cable is unplugged.... let me test this situation.

I saw your ticket.

http://jira.omnirom.org/browse/OMNI-1014

I will let Omni Team know about devices list.

Thank you!
[Galaxy Tab  Android Development] humberos:
Fixed!

https://gerrit.omnirom.org/8106

Please, just wait next nightly build.

Thank you!
[Galaxy Tab  Android Development] Mjoelnir77:
Iirc we had 1300Mhz in the past, since about 4.4.3 we lost it. Any chance to get it back or even 1400 Mhz (usually was stable for me)?

Changing kernel voltage within omnirom settings does not work for me, but using "Pimp my ROM" app it does. On my side (too many dirty flashes?) or do others have that problem too?
[Galaxy Tab  Android Development] humberos:
Actually 1.3 and 1.4MHz cpu steps are unstable at moment for some users.

Although the kernel sysfs already supports voltage changes but I think the Omni performance options don't persist these values.

And yes, I think the Omni team won't worry about this at moment.

Sorry!
[Galaxy Tab  Android Development] alessandronip:
I am anxiously waiting for the new build to test it.

Thank you very much.
[Galaxy Tab  Android Development] humberos:
Just a tip.

First of all, this feature isn't present at stock kernel. I think the audio routing doesn't works for TVOut cable or Deskdock (at stock).

The audio routing only works using HDMI output.

This change is a kernel adaptation for 30pin events.

Pay attention, the audio routing will not works if you change cables during sound reproducing.

You will need to stop the sound reproducing then change the connector and then play sound using your current setup.

I know, it isn't the better of the worlds but it works.
[Galaxy Tab  Android Development] alessandronip:
UMS can be integrated only into recovery?

In TWRP you can not see the storage via USB.

Or even this must be accepted by the team OmniRom?
[Galaxy Tab  Android Development] humberos:
Yes. UMS is present only at recovery mode.

You need to mount the storage manually.

[MENTION=535343]all[/MENTION]

I've opened a thread about UMS and you can check all discussion about it here:

https://lists.omnirom.org/pipermail/maintainers/2014-June/000040.html

I think that UMS will be deprecated by Omni Team and also I think the Team have important points about it.
[Galaxy Tab  Android Development] humberos:
Oh! If you want I can attach the kernel to you by PM, just let me know what your tab version is.
[Galaxy Tab  Android Development] safety1st:
Android 4.4.4 more Security fix, & ART... hmmm

http://www.xda-developers.com/andro...finally-remove-dalvik-and-set-art-as-default/

http://www.xda-developers.com/android/heres-everything-thats-changed-in-android-4-4-4-ktu84p/
[Galaxy Tab  Android Development] aalvico:
Will we get 4.4.4 update ?
[Galaxy Tab  Android Development] alessandronip:
To me it does not work.

In recovery if I connect the cable I see two disks unmounted.

If I give the command mount disks disappear altogether.

Using Windows 7 and the drivers are the standard ones.

The UMS it may be activated in the developer options.

I was joking, I can wait for the official build, so I can only test in the evening at home.
[Galaxy Tab  Android Development] leleobhz:
Being honest, i think the UMS support must be present at least with a warning about Woms (but i cant see any sense in this because mtp van also transfer files).

But a good point about UMS is MTP does not work in my car sound and PS3 and my TV AMD a looooot of another devices that reads well a pendrive but not mtp.

And i like my 32+15Gb pendrive with screen and music/video player ?
[Galaxy Tab  Android Development] humberos:
4.4.4 android version was merged.

Just wait next nightly build.
[Galaxy Tab  Android Development] humberos:
Android 4.4.4
[Galaxy Tab  Android Development] thesniffer:
Thank you mate for all your efforts ;)