yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] jenaplisken:
Always use this app (https://play.google.com/store/apps/details?id=com.kober.headsetbutton) because Android does not natively support the headset button to launch google voice search. (with iphone with a single headset button click i can launch siri).

if you try to use google voice search (eg: "Call mom at cellphone") the app recognizes the command and

only after the TextToSpeech repeats the command the call starts

the problem now is.

OMNIROM (Screen off with lock screen or screen on with lockcreen) I use the headset button -> google voice start -> recognizes my command -> but after that textospeech don't repeat the command and don't start the calling.

OMNIROM (Without lockscreen or with lockscreen bui if i use the lockscreen voice command shortcut) I use the headset button -> google voice start -> recognizes my command -> after that textospeech repeat the command and start the calling.

With other MMrom i not have this different behavior. No problem at all.

I noticed This thing happened to me right from when it was inserted the possibility to replace the phone shrotcut with the voice search on the lockscreen
[ONE Original Android Development] maxwen:
logcat for both cases
[ONE Original Android Development] maxwen:
Long press HS button works fine to launch voice search - I don't need an extra app ? And issuing a call with it works fine here also on the lock screen or screen off

Have you enabled voice commands on lock screen for wired headsets in google app settings?

Voice - hands-free - for wired HS
[ONE Original Android Development] payne_307:
Hey [MENTION=4683552]maxwen[/MENTION]... Can you respond to this thread where I quoted you and fusionjack as the experts on Omni builds for Bacon. It will be a great help for Jorge who is trying hard to improve CM builds for OPO. I'm not the expert on what Jorge wants to know.

http://xdaforums.com/showpost.php?p=65965646&postcount=13093
[ONE Original Android Development] thenessus:
Do you see this beautiful nearly flat line?

That's in the 20th build, with all Google features fully on (voice, location, Google Now, smart lock... You name it), with Smartmax governor, wifi location scanning, and only on 4G. Yesterday I hit a respectable 4.5 SOT. No greenify or other stuff of the sort.

I can barely get that on other ROMs with all Google stuff off and location off, with greenify.

As a flashoholic... I think I'll take a time off to enjoy this amazing ROM (and it's cool battery percentage text font).

Kudos.
[ONE Original Android Development] jenaplisken:
Long press Hs launch voice search only without lockscreen. With lock screen or screen off and lockscreen, long press start a black screen with the word 'initializing... ' and stop; no voice search.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] maxwen:
I can only tell you that it works fine here - EOM :)
[ONE Original Android Development] :
SOT seems a little low, as I usually hit 6 hours and that is with everything syncing, my work mail set to push and playing CoC.

Just saying to check as you may be able to squeeze more with little to no hit to performance.
[ONE Original Android Development] jenaplisken:
Do you use Bluetooth headset or cable?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] maxwen:
Works fine with both ?
[ONE Original Android Development] Renosh:
Do you use custom performance profiles or just use stock kernel settings? I also get 6 hrs or more with a lot of COC
[ONE Original Android Development] :
Smartmax, and ultra power profile for everything except Chrome, YouTube and CoC.
[ONE Original Android Development] Renosh:
I mean like this

Check the values for Ultra that I put, I use this for screen off and COC. Otherwise I use default ondemand during normal use
[ONE Original Android Development] thenessus:
I never used profiles. I'll give it a shot.

4.5 hours SOT is still a lot considering I get 1-2 on other ROMs.
[ONE Original Android Development] jenaplisken:
Can you better explain were i can find this setting?

Thanks
[ONE Original Android Development] payne_307:
Dude, you are wasting too much precious time of a busy Dev by quoting him or his post. A little exploring things on your own might as well help given the power of Google search bestowed upon you.

Here's the spoon feeding for you and this should end any posts from your side in this regard. If still not works for you, go to Google search forums, do not spam here.

Google Now --> Settings --> Voice --> Hands-free --> Toggle for wired and/or bluetooth devices as desired.
[ONE Original Android Development] binzianer:
Is there or will there be a possibility to reverse the order of navigation bar symbols? I can only En- or disable it.
[ONE Original Android Development] SumanthBv:
Trying now. Will review the ROM shortly. :)
[ONE Original Android Development] Gliuk_er:
It must be, since samstone is the official maintainer for bacon
[ONE Original Android Development] SumanthBv:
WiFi gets connected and disconnected once in a while.

Is there any workaround?

---------- Post added at 12:01 PM ---------- Previous post was at 11:32 AM ----------

WiFi keeps connecting and disconnecting once in a while.

Is there any workaround?
[ONE Original Android Development] astrall:
Does this rom supports Layers RRO themes?
[ONE Original Android Development] deepaklunked:
Yes.

Sent from my OmniBacon powered by [MENTION=1228651]fusionjack[/MENTION]
[ONE Original Android Development] gaja22:
Release from 6th : 280Mb, 6.0. Release from 8th : 240Mb, 6.0.1. Less 40Mb. What's happened ?
[ONE Original Android Development] newarkoz:
I think that the reason to this is the removal of chromium browser.

---------- Post added at 10:34 AM ---------- Previous post was at 10:32 AM ----------

[MENTION=5965253]samstone86[/MENTION] do you know when the DT2S in statusbar and lockscreen will be added to the rom?

I saw in omni gerrit the commits related to this, however it isn't merged yet.

This is one of the features I miss the most! Thanks! :)
[ONE Original Android Development] samstone86:
As I mentioned some posts before ... My builds are the reference for what's going into later nightly builds
[ONE Original Android Development] samstone86:
You only have to READ the OP and the next two posts to get your information :P
[ONE Original Android Development] samstone86:
Sorry I don't know when ?
[ONE Original Android Development] fermasia:
I didn't read that, sorry & thanks again :good:
[ONE Original Android Development] smartAgent47:
Canu link me to vendor binaries ? I need the binaries please !
[ONE Original Android Development] AndreIrawan97:
Is it okay if i dirty flash the 12/08 (6.0.1) over the 12/06 (6.0) ?
[ONE Original Android Development] samstone86:
I did it :P
[ONE Original Android Development] samstone86:
I think not :) but you have the binarys on your Phone too ;) so for now not :)
[ONE Original Android Development] AndreIrawan97:
What is the difference anyway ?

Is there any battery improvement or new feature?
[ONE Original Android Development] samstone86:
google is your friend ;)

http://www.androidpolice.com/2015/12/08/aosp-changelogs-posted-for-android-6-0-1-and-december-security-updates/
[ONE Original Android Development] gaja22:
Yes, you're right. I'm sorry ! :good:
[ONE Original Android Development] batwingnz:
Running 12/06 for three days without issue until today.

Phone turned off instantly while browsing reddit and listening to google music about five mins ago, no force close just immediately off.

Booted and tried to post about it, soft reboot while typing in xda labs.

Listened to music and browsed reddit every day this week so far and this is the first time I've seen this.

Will try and replicate and log later.
[ONE Original Android Development] Renosh:
Just seen this

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

Personal opinion from my testing on this ROM is Smartmax is good in most situations but is stuttery in some website and apps like Google+ during scrolling. A site I regularly visit AndroidAuthority I fling the page and Smartmax seems to be step behind, the fling is registered slower than it should be (Chrome Stable). Ondemand handles the same operations much better. There was a time ondemand had issues of lagging over time but its perfect now and is the better OOTB. Smartmax is definitely better for battery. Either way I can change back to whichever governor just thought I'd contribute
[ONE Original Android Development] :
So, from what you are saying, switching to ondemand from Smartmax may yield an increase in battery drain. I honestly don't experience any significant downside to using smartmax, I have Chrome/Youtube/Clash all running the default profile, so it may be the reason why i don't experience much stutter.

Question, with the modified Ultra profile you shared, does your phone get really hot playing CoC?
[ONE Original Android Development] Renosh:
Not really sure but Smartmax is very conservative in terms of CPU frequency it ramps up to while ondemand ramps up to max on touch input so I judged it may be better for battery life. I always use ondemand governor.

Phone doesn't heat up while playing COC (with my settings) stays cool and I can literally stay on for 30 mins without issue
[ONE Original Android Development] payne_307:
[MENTION=4683552]maxwen[/MENTION] [MENTION=2225255]herna[/MENTION] [MENTION=5965253]samstone86[/MENTION] ... Guys I checked with fusionjack but he didn't quite know if this commit can be a possibility for Omni? Looking forward to your expert opinion on how this can get included in Omni, because this one change can make a terrific upgrade in call quality. Would request y'all to not ignore this even if its a bit of a 1 time work.

http://review.cyanogenmod.org/#/c/137753/
[ONE Original Android Development] maxwen:
not really applicable to what we use

we stopped long time ago to follow the acdb changes CM is doing

also only partly interessting cause we dont support call recording

and I have not heard of problems with voice recognition either
[ONE Original Android Development] payne_307:
I have always tried to avoid keep "Ok Google" detection on any screen off ever since the infamous bug with causes pathetic garbled voice over the mic when enabled. Are you saying on this ROM there is no such issue? I'm sorry I haven't tested. I'm also not interested in Call recording but in "Ok Google" detection from any screen/lockscreen - Yes. It is very very handy when driving for me.
[ONE Original Android Development] jenaplisken:
Ok google work only with phone unlocked. For locked phone you have to use the hands free mode of Google Now. You can start a voice search with the button of wired/bluetooth earphone. But you have this option only if the system language is english. I use Italian language and i not have it. If i change system language in English it appears.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] payne_307:
I know. I have used it for years. I normally just double tap to wake up my screen to allow the phone to start receiving voice commands when driving. So apart from the double tap I don't need to keep looking at the phone while I dictate it what to do. Somehow it works pretty accurately for me. And yes I use English - US

But stopped doing it since OPO started having issues with fluence and mic. The current process is something I would want to get rid of as early as I can.
[ONE Original Android Development] maxwen:
I dont know - except for cursing I never speak to my phone
[ONE Original Android Development] Vintage144:
Do i need to treat this as a new rom if i havent flashed in a while? I was dirty flashing until beginning january? I havent had time to do any nightlies until now , dont want to just go through them can i do it from this build or clean flash?
[ONE Original Android Development] maxwen:
You must do a clean flash if it is your first nightly
[ONE Original Android Development] payne_307:
OK. The issue is there. While it may not affect everyone but people like me who have to make calls or send short emails/texts while driving, going hands free is so important. And I can't avoid it as the traffic in my city is one of the worst in the whole country. Will you still take a look and see if something can be done. People on CM after this commit are experiencing better call quality regardless of OK Google detection being on or off, so it's an improvement in any sense you may look at it.
[ONE Original Android Development] maxwen:
No
[ONE Original Android Development] payne_307:
Ok
[ONE Original Android Development] maxwen:
You have to understand that we are very very very very conservative with changes like this. Before we change blobs hell must freeze ?
[ONE Original Android Development] payne_307:
I wasn't aware that Omni doesn't use the same blobs as CM for audio. I knew it for camera but wasn't sure about audio. I can understand what you mean. Its a pain that the answer to a working OPO in all departments means a mixed bag of drivers and blobs from all different places (CM, COS, ColorOS, Oxygen OS, Hydrogen OS, phew !!). However, after patiently waiting till eternity for CM/1+ to fix things and ending up disappointed, Devs are now slowly starting to begin experimenting with bringing blobs from a different source than their base branch. As you recently saw after I mentioned it to jgcaap he is now working to get the ColorOS based blobs working in CM kernel. Darkobas Dev just recently announced and moved his ROM to start using ColorOS blobs moving from those of Sultan's (I guess he also heavily uses the Omni base in his ROM). So basically the point here is everyone is fed up of CM & 1+ to resolve these issues for the OPO. Now its up to the Devs like you to evaluate whether its worth their time & effort. Some are working on some adjustments (porting blobs, firmware, etc.) to give OPO some more legs in its controversial life cycle, while others are just maintaining things as is (AOSP + CAF/CM updates) and rather looking at developing for the next Dev friendly device of 2016.
[ONE Original Android Development] maxwen:
Its way more complex then you think cause we also have to think about Oppo find7 and n3 too

cause they share 99.9% of everything :)
[ONE Original Android Development] thenessus:
You can use a navigation map (sound on or off, however u wan) so the screen is always on so that "OK Google" will work fine if you choose voice from any screen. Works wonders for me, and it makes it truly hands free (no need to tap anything).

If just set screen to be always on without an app doing it, in dev options.
[ONE Original Android Development] payne_307:
Ummm.. Too much battery drain for a simple feature to run. Will pass on this one. If I can run it just by double tapping the screen, I'll be more than happy.
[ONE Original Android Development] killer520:
Oneplus one user here. I have tried to flash this rom for the entire day with open gapps nano and it always get stuck at the boot logo this really annoying has anybody had this issue before? I user tarp 2.8.6.0 and did a full wipe but still no luck :(
[ONE Original Android Development] jkmangang:
Make sure data, system and cache partitions are ext4 format. F2FS is not supported.
[ONE Original Android Development] surajrv6:
Why does this rom does not support hardware key mapping? :(
[ONE Original Android Development] fmc000:
Probably you meant f2fs ?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] jkmangang:
Sorry..it was a mistake.
[ONE Original Android Development] killer520:
I figured it out the issue flashing SuperSu gave me the bootloop. I am unsure how to get root now since whenever I try to flash it later Omni keeps having a bootloop, just tried dirty flashing a more reent version on top of it but no dice. Anybody had the same issue?

---------- Post added at 07:58 PM ---------- Previous post was at 07:47 PM ----------

It has been 3 hours now and omni still refuses to run because of this annoying bootloop issue regarding the supersu binaries. I am very disappointed since I supposed a solid rom like omni would not have such an issue. Could anybody advise me a better rom for OPO?
[ONE Original Android Development] fmc000:
You're probably using the wrong SuperSU. Please be sure to go for beta 2.67+ or RC 2.70, avoid the stable versions because they won't work.
[ONE Original Android Development] maxwen:
Just so that you can ask ...
[ONE Original Android Development] killer520:
Yea that seemed to fix it, I just got annoyed od being stuck on the bootlogo. Thanks a bunch mate. Cheers!
[ONE Original Android Development] saenanme:
The same for me, but I noticed that /data and /cache were f2fs formatted.

I changed both to ext4 and the device booted normally.

Regards
[ONE Original Android Development] randallstevens:
H.265 Decoding

Hello [MENTION=4683552]maxwen[/MENTION], I'm not sure if you've tested this but I can confirm the stock Omni kernel does not support h.265 (HEVC) decoding which CM's stock kernel can handle. Can you take a look?
[ONE Original Android Development] maxwen:
No I have not tested and will hardly have the time to do so soon.
[ONE Original Android Development] maxwen:
and as usual - a logcat would help
[ONE Original Android Development] fmc000:
I wonder if / when the English-only parts of the "Settings" app will be translated.
[ONE Original Android Development] iVAn94fi:
Hi anyone having issues with network signal?? I am still not able to connect to LTE or H+. I was having the same issue a month ago, and after trying other roms in the meanwhile, i came back to omni to see if the problem was solved, but had no luck. Actually no one has even responded my previous post. The strange thing is that everything works with other roms (fusionjack omni, jcaap cm, sultan cm, RR M, SAOSP,..).

Hope someone tries to help me this time :good::good:

Previous post:

Good evening guys, I have to report something here.

I' am having signal stregth/network switching issues. More precisely I'm not getting H+ or LTE anymore, but H and E seem to work properly (maybe a tiny bit less signal strength, but that's not the issue).

I tried changing network preferences with #*#*4636#*#* "secret" dialer code and it didn't help. Network remains fixed in GSM/LTE, even if LTE is not working. Besides, changing this setting in other roms works.

I am running on 05/15/2015 firmware ( DI.3.0.c6 baseband ) and everything worked fine in 5.1.1 (slimrom) and any other Marshmallow roms I've tried (including fusionjack's omni). Actually I am re-trying fusionjack's slim 6.0.1 right now and H+ works well.

I flashed everything using TWRP 3.0.0-0 (which i installed through 2.4.6.0 TWRP itself), and since I have never had proximity problems, I suppose I am using the right TWRP-Firmwares set up.

Ok I have tried to explain everything, could someone help me? Maybe another firmware? Maybe another recovery?.. Please help.

Thank you.
[ONE Original Android Development] :
Recovery has nothing to do with proximity. If you've noticed, no one else seems to have reported this issue, and I would this would be a deal breaker for a lot of people, including me.

I have zero connection issues, currently have LTE.

Only recommendations,

switch modem, try the modem included in the latest CM nightly.

Try changing APN in 5.1.1 Omni would screw up my APN, so it is worth checking.
[ONE Original Android Development] iVAn94fi:
Thank you for your answer. I will try to change modem. How can i install the latest cm modem? Can i just flash latest cm nightly and then flash omni on top of that (obviusly not dirty flash) or should i download latest modem from modem collection topic and install it with fastboot?
[ONE Original Android Development] Galactus:
I still have the issue of not being able to change to 2G in the settings menu. No amount of clean flashing will work lol
[ONE Original Android Development] :
Honestly for me it is usually easier to flash latest CM nightly so I don't have to hunt the forum for the modem link.

Yes, flash CM, no need to reboot, wipe everything and flash Omni.
[ONE Original Android Development] iVAn94fi:
Neither am I.. I see all the options, but no matter what i select, it will always stay in GSM/LTE, even if it doesn't connect to LTE.. But it connects to 2g.. :eek:

EDIT: [MENTION=3920726]jibust[/MENTION] flashed latest cm nightly, but the baseband hasn't changed. Mmh.. I'll try to fastboot bacon_firmware_update_2016_1-25_.4.0.1.c7-00011 and see what happens..

RE-EDIT: No luck. Neither latest cm nightly, nor c7 modem from modem thread solved the issue. Now I am going to flash 2.8.7.0 unofficial twrp, which is recognized as fully working, and I will try to repeat the whole process.
[ONE Original Android Development] animefans:
adb on PC does not see phone

Today I build my own OMNI 601 user build

lunch omni_find7op-user

The build ran without error

I can flash it just fine

However, when phone is connected to PC, adb.exe on PC does not see the phone

In another word, adb devices show nothing

And I installed Android USB driver from

android-sdk-windows\extras\google\usb_driver

I make sure USB debugging is on, it's not in charger mode, etc

The same phone and PC (windows 7) has no problem with adb when I had OMNI 5.1.1 user build installed

Can anyone give me some idea how to troubleshoot and resolve this issue?

Thanks!

PS: right now MTP works, but I am a command line junkie, so prefer to connect to phone via adb shell. Besides, running adb shell allow me to run scripts
[ONE Original Android Development] kvaju:
2.8.6.0 or 3.0.0.1 will flash modems correctly.
[ONE Original Android Development] Renosh:
Just noticed a bug with screen record. There is no sound in recorded videos and the video is laggy. I used default profile to do the recording (game play recording).
[ONE Original Android Development] payne_307:
[MENTION=4683552]maxwen[/MENTION] .. Just a question.. In the advanced section you have gestures for the device. Can a proximity wake-up gesture be thought about? I saw something like that on XDA in a thread for falcon with CM13 and someone using a flashable zip that can be used on CM13 for Bacon to include an option to activate that gesture in gestures section of CM (same thing that came in Oxygen OS for OPO in v2.1.4) Since the default ambient display is a hit or a miss, this one seems more useful in certain scenarios. I know it will account for some more battery drain but the option can be provided by default as off, with a small description that turning it on may increase battery consumption. But at least we can have an option. What's your thoughts?
[ONE Original Android Development] maxwen:
Sound was never supported in 6.x

---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------

No thoughts on that
[ONE Original Android Development] Renosh:
It used to be available in 5.1.1 Omni builds under Ambient Display but seems it hasn't made its way to 6.0. There was an option to use proximity sensor to trigger Ambient Display and show clock or notifications. So you wave hand over proximity sensor and the screen shows clock or remove the phone from the pocket it immediately shows that dark ambient view etc.
[ONE Original Android Development] payne_307:
Ok. Didn't use Omni on 5.1.1 so didn't know about the history. This makes me wonder what caused the feature to be removed in 6.0? It is a mighty helpful feature especially when you have desk job (with your phone on the desk) and you don't wish to either power the screen on or wish Ambient Display actually worked when you nudge your phone (which simply rarely happens on Omni). Somehow on CM the success ratio with AD is a lot higher vs Omni. In Omni the screen lights up when notification arrives but hardly ever wakes up again when you nudge the phone after a while the notification arrived. And hence that proximity wakeup is a great option. Most people who disagree to the feature are the ones that mostly keep their phones in pockets and do not work for extended duration on their desk for works other than Android (Because I know the Devs do stay on desk for long, but that's still related to the phone).