yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] maxwen:
No maintainer for the code therefore it had to go. Furthermore messing with sensors is always a PITA across devices. So no plans to add it back.

And ambient works as expected on this device since it doesn't have a pickup sensor so you can shake as much as you want ?
[ONE Original Android Development] payne_307:
Ok, understand the thing around code maintainer. However I can this link with you to see what's implemented (http://xdaforums.com/moto-g/themes-apps/c-apps-cm13-motodoze-ambient-display-t3312681 - MotoDoze.zip).

Though its for a CM base I can confirm that that this works on OPO without issues and without any significant drain on the battery.

Regarding pickup sensor, I will need to disagree a bit. It works 60%-70% of the time on CM. I can always pickup my phone with notification LEDs blinking since a long time and as soon as I pick it, after a gap of 1-3 secs (this has been a recent delay. In 5.1.1 this was almost instantaneous) the ambient display shows up. Anyhow as I said, it still has a mind of its own and will work at times and sometimes it won't so even though CM implementation on POP works better, its a neither here nor there kind of situation. The proximity sensor hand wave gesture works more reliably as there is a definite action to trigger it.
[ONE Original Android Development] firenxe:
I'm having an issue with the phone going into qshusb bulk mode randomly. It also happened on slimsaber. I've tried changing the filesystem from f2fs to ext4 and clean flashing and it kept occurring. My set up: Omnirom nightly 0504 + open pico gapps + stock kernel and settings. Here's a logcat and dmesg. Thanks!
[ONE Original Android Development] darkobas:
just install pushbullet or join. much more handy and efficient.
[ONE Original Android Development] payne_307:
Too big a battery hog compared to just triggering Ambient Display via Proximity Wakeup + extra data when not on WiFi. SD801 is perfectly capable of not loosing too much due to proximity wakeup vs. other older siblings. With pushbullet / join I have seen nasty wakelocks even when not using it like the facebook app. So not venturing there again. Will hope Omni brings this as a feature. In the end turning it on/off is optional. It still up to the user to make the choice which. May be someone/many will still use pushbullet/ join after this feature. But it's out there will be a good thing to have.
[ONE Original Android Development] darkobas:
what are you smoking?
[ONE Original Android Development] :
Powerfull indeed.

I use Join, and I have to say, I know it is still young but it doesn't feel as polished as Pushbullet. Not that I will go back to pushbullet and their extravagant prices.
[ONE Original Android Development] :
[MENTION=4683552]maxwen[/MENTION] any chance you can add to the Statusbar icon settings the ability to block the change keyboard icon?
[ONE Original Android Development] darjwx:
I guess he means if you can add a way to delete the icon that appears in the status bar when you open the keyboard
[ONE Original Android Development] :
What firmware do you guys use for this ROM? Or does it automatically flash the right firmware?
[ONE Original Android Development] :
The icon in the top left.
[ONE Original Android Development] maxwen:
Will be gone with L for free
[ONE Original Android Development] :
? N or am I not understanding?
[ONE Original Android Development] maxwen:
LOL

---------- Post added at 09:06 PM ---------- Previous post was at 08:42 PM ----------

In L it was moved into the navigation bar but only if you have one :)
[ONE Original Android Development] JaylanPHNX:
Honestly, it being in the nav bar is even worse. I occasionally hit it by accident with the meaty part of my thumb when reaching all the way across the phone to select something. It would be convenient to be able to disable it for those who hardly ever switch keyboards.

From my SlimTab Pro 8.4
[ONE Original Android Development] maxwen:
Just wait and see
[ONE Original Android Development] :
Thanks for the commit!!!
[ONE Original Android Development] iVAn94fi:
Tried both, none of them works for me. Well actually the modem is properly flashed, and it works in any other rom but this one. It works even in fusionjack's build. So I tried almost every combination of different twrps ( in particular: official 2.8.6-0, 3.0.0-0, 3.0.0-1, 3.0.2-0 and unofficial 2.0.7-0) and firmwares, but the issue remains. No H+ at all ( although in settings/About Phone/Status/SIM status/Cellular network type now HASPA+ briefly appears and then goes away, but H+ NEVER appears in the status bar icon) and LTE connects in some places (almost never) and it does not in other areas where with other roms it works flawlessy.

I attached the logcats i just saved to this post. Hope they help :good::good:
[ONE Original Android Development] riazsgs2:
Stuck at Checking Connection

Coming from Sultan's cm13. TWRP 3.0.2

Omni latest nightly

Banks GApps

Installs perfect. No bootloops. However stuck at Checking connection after entering wifi details. Been 20 min already.

Restoring cm13 backup for now.. Can anyone please let help me understand what is the exact problem.
[ONE Original Android Development] Renosh:
Wrong password. Forget network and confirm the password is right
[ONE Original Android Development] ajeevlal:
i am having the same problem too.
[ONE Original Android Development] :
Does your router filter mac addresses?

Just asking because I had the same issue a long time ago and it was because of this.
[ONE Original Android Development] ajeevlal:
I believe the problem is with Gapps, i had a same problem with Banks Gapps and it got solved when i dont install banks gapps
[ONE Original Android Development] webore:
Update translations please .
[ONE Original Android Development] chrcol:
I dont know what to say.

Was running 5.1 omnirom reasonably well. But then noticed omnirom devs just jumped without reason to 6.0 so held off for a while.

I updated today and chaos.

So before hand I did the nandroid backup (thank god)

Uninstalled xposed

Then installed the newer nightly.

Wiped dalvik cache and booted.

First warning was only 38 apps had to be optimised instead of 120+ (all settings lost?)

Second sounds etc. activated when was mute.

But I cannot even see what has been lost because the phone is looping with systemui crashing and restarting non stop. :(
[ONE Original Android Development] JaylanPHNX:
Am I reading this wrong, or did you try to dirty flash from one Android version to another? Because if you did, that's why the chaos. Verify your zips and clean flash.

From my SlimTab Pro 8.4
[ONE Original Android Development] chrcol:
I didnt specifically dirty flash, the omnirom updater did.

I thought it was silly to have that upgrade path in place hence my nandroid backup prior to going ahead of it.

Sadly I am not prepared to wipe everything clean, reconfigure etc for now so will still with the now unsupported 5.1 omnirom and maybe try again in a few weeks.
[ONE Original Android Development] maxwen:
So if someone tells you - "jump" - you do it? :)

Yes the 5.1 updater was missing a check to make it impossible to do what you did

so it was relying on testing common sense - and not a lot of people missed that test :)

But yes - update from 5.x to 6.0 must be a clean flash - especially because of gapps
[ONE Original Android Development] chrcol:
To be fair vendor updates maintain settings across android updates. So with that taken into consideration and combined with the fact the official updater was offfering the update I thought yeah it might work. But I wasnt convinced hence the backup.

Is a shame the updates stopped for 5.1 and they only seem to be supporting 1 code branch.
[ONE Original Android Development] maxwen:
"They" don't really care what you think is a shame ?
[ONE Original Android Development] surajrv6:
I am waiting for the developers to implement hardware button mapping. After they do so, I'll flash this rom :)
[ONE Original Android Development] fmc000:
Be sure not to hold your breath, then. :)
[ONE Original Android Development] :
Lol, Opendelta can go as far as automatically downloading the newest nightly, but you still need to press FLASH in order for it to apply.
[ONE Original Android Development] Nalin12:
I think this is one of the most underrated rom on this forum. It deserves more attention.

Can someone tell me how can i preserve the systemless root after flashing the open delta update ? This is the only issue i faced so far although i tried to find that setting to add super su zip but couldn't find it.
[ONE Original Android Development] Phyrene:
Put supersu zip in opendelta/FlashAfterUpdate

Then in opendelta go to settings and uncheck security mode
[ONE Original Android Development] maxwen:
Not sure if we really want attention cause the bright light will also bring in all those flies :D:D:D
[ONE Original Android Development] Nalin12:
Those flies are surely not what i meant by attention :p
[ONE Original Android Development] Keksdroid:
What exactly does the "Google are you drunk?" commit fix? Is it finally the Wifi drain fix??
[ONE Original Android Development] maxwen:
LOL - no

BTW there is no WiFi drain
[ONE Original Android Development] Keksdroid:
Yeah right, the high drain I used to have is actually gone by now, but it's just not possible to turn off wifi (according to battery statistic). Its always shown as on in battery statistics unless I reboot after I turned it off.

And yes, Wifi search in Location Settings is turned off.
[ONE Original Android Development] ghmail2:
i really like omni, it is way stable than the cm. the only problem is that omni on bacon is not that smooth, on the other hand omni on the nexus 4 is smooth like a butter. omni kernel on the nexus also uses the ondemand. strange
[ONE Original Android Development] maxwen:
That happens if you call your device by the wrong name
[ONE Original Android Development] Renosh:
I've been noticing this bug for some time now

The arrow that allows me to choose media volume/alarm volume disappears from time to time. The conditions for replication aren't clear cut either. I was watching a YouTube video and went to home screen and wanted to reduce media volume but couldn't. Doing the same procedure after doesn't reproduce it
[ONE Original Android Development] maxwen:
Known AOSP bug but google doesn't care that much to include a fix for now. You can only hope for N. You can reproduce it playing with rotation.

---------- Post added at 04:47 PM ---------- Previous post was at 04:00 PM ----------

BTW here is the google reference https://code.google.com/p/android/issues/detail?id=188918 so you see its marked fixed but not released
[ONE Original Android Development] fusionjack:
here is the fix: https://android-review.googlesource.com/#/c/187400/
[ONE Original Android Development] maxwen:
Thanks for the link - Yeah I know there is a fix but why should I do googles work of releasing it :)

I mean - come on - 4 months with updates every month now and this was

not important enough to include it???
[ONE Original Android Development] animefans:
Thanks for the link!

And I have a good LOL on your sig...
[ONE Original Android Development] wq2020wdm:
Hi,if I want the pro mode of color os camera, do I still need flash the camera hal with find7 blobs？
[ONE Original Android Development] maxwen:
whatever pro mode is?
[ONE Original Android Development] darjwx:
Probably he means the mode with all the options. If you install the apk you don't have all the modes and stuff, for that you need to install a patch blobs, color blobs or something like that.
[ONE Original Android Development] wq2020wdm:
​

It should be manual force. Here is the link:http://xdaforums.com/oneplus-one/themes-apps/port-coloros-camera-cm11s-t3030369
[ONE Original Android Development] maxwen:
"manual force"? this gets better every time :D
[ONE Original Android Development] darjwx:
Mode *
[ONE Original Android Development] maxwen:
Well - that plugin never worked for me

But to answer your initial question - you dont need to flash what you already have :)
[ONE Original Android Development] darjwx:
It wasn't my question :) I was just explaining his post haha
[ONE Original Android Development] maxwen:
"your" was used as a global reference ?
[ONE Original Android Development] maxwen:
Just as a heads-up

To stay inline with AOSP and reduce merge problems in the future

we will use the same default double tap to wake setting as Nexus devices

under Settings -> Display from now on.

(Whoever at google thinks this is the right place for it :p )
[ONE Original Android Development] aliffaminuddin:
does omnirom good?
[ONE Original Android Development] pu3cyg:
will you believe me and flash it if i say yes?
[ONE Original Android Development] aliffaminuddin:
nevermind running latest omnirom already
[ONE Original Android Development] maxwen:
*deleted*
[ONE Original Android Development] Mich2027:
Hi guys any solution for the inverted camera?

I'm using CamScanner a lot as a student and on this ROM the image is inverted in this app, how can I fix it?
[ONE Original Android Development] maxwen:
short answer: its a app problem not using sensor orientation information to rotate correctly

as you can see in other apps (e.g. camera) if you use this correctly it will be correct :)
[ONE Original Android Development] Mich2027:
Thanks for the explanation,

Any ideas for apps that do the same shoots to PDF and work properly on this ROM?
[ONE Original Android Development] kvaju:
Genius Scan?
[ONE Original Android Development] THUNDERASS:
My device got scroll stuttering with this rom. Chrome, Firefox, google play. What causes this. Any idea? Maybe image cache i don't know. After page loaded i scrolling down page and scrolling up again loaded image etc loading again it cause stuttering.

i found myself entropy cause this. i changed default now no problem
[ONE Original Android Development] theCroh:
Is anyone else experiencing accelerometer issues on the April 24th build? I occasionally get an "Error: no accelerometer sensor" toast message and the accelerometer doesn't seem to work at all.

Lähetetty OnePlus Onesta Tapatalkilla
[ONE Original Android Development] akash4357:
I just flashed this rom, I have no encryption or anything, but after the first boot it keeps asking me for password.. what do I do?

Edit: Nevermind, I had to format data partition to ext4.
[ONE Original Android Development] baddelay:
ATTENTION! The 24th nightly seems to have some sensor issues. I have installed the 22th afterwards. Everything's fine there.
[ONE Original Android Development] baddelay:
All fine with the 25th nightly.
[ONE Original Android Development] payne_307:
I apologies in advance for posting something that everyone would say doesn't belong here - Xposed. But I have to tell you, I want to really come back to this ROM. And no I don't need Xposed for some snarky feature. In fact I need it for 1 and 1 reason only - http://xdaforums.com/showthread.php?t=2040163. Yes my company uses this app and this bloody app doesn't allow root. Though this ROM doesn't have full root but it still has busybox and debuggable root enabled, hence the app detects root on it. My issue is the module and the app apk recommended in the thread (http://xdaforums.com/showthread.php?t=2040163) do not work on this ROM. If I go a version behind both on the app and the Xposed module it works, but since those older versions are not optimized for Lollipop/Marshmallow they never work correctly (get killed in the background even though a persistent notification is still there making emails to stop flowing unless being restarted). I have seen the same behavior on Oxygen OS 2.1.4 (5.1.1) and Darkobas. But all CM13 ROMs and SlimSaber by fusionjack works fine. Can someone or maxwen suggest possible solution or specify the kind of logs they need from me. I tried troubleshooting on the other thread with the OP (via PM) but since this behavior was ROM dependent he asked me to check it on the ROM thread. Please help me with a solution.
[ONE Original Android Development] vorcers:
Hello,

I hope you can help me out.

I tried to install Omnirom on my Oneplus One with the find7op Image. Version from 05.05.

I can flash the Image, and the system boots up and is working. Then I reboot to recovery again and want to flash SuperSU

or

gapps (banks). Then I try to reboot and get stuck at oneplus logo.

It also get stuck if I flash gapps/supersu rightaway after I installed the system.

I tried TWRP 2.8.6.0 and 3.0.2. The stuck at boot occurs always and I need to reflash the boot.img image per fastboot from the omnirom-Zip to make it work again.

Any ideas?

Thanks for your help

vorcers

Edit: I tried omni-6.0.1-20160422-find7op-NIGHTLY.zip, which works as it should. If I flash omni-6.0.1-20160505-find7op-NIGHTLY.zip and SuperSU the phone gets stuck at the OnePlus Logo. If I flash 20160422 and SuperSU again it boots up. This is strange. Maybe someone else can try 20160505? I did the flashing with official TWRP 3.0.2-0.
[ONE Original Android Development] sax0406:
Try flashing rom+gapps+supersu in one go, and then boot to the system. And make sure the SuperSU version is 2.67+
[ONE Original Android Development] vorcers:
Thank you for your answer, but this didn't change anything. Have you seen my edit:
[ONE Original Android Development] maxwen:
Anyone here tried a nightly after 0503 and can confirm that sensors are working correctly?

If yes - have you dirty flashed or clean flashed?

Thanks
[ONE Original Android Development] Renosh:
I'm on 05/04 nightly and everything works great. Clean flashed 05/03 with Opengapps then dirty 05/04
[ONE Original Android Development] maxwen:
thanks
[ONE Original Android Development] fmc000:
I don't know it this may be significant for you but I user SlimSaber ROM and the latest version has all the new sensors commits and blob stuff from the OmniROM tree: the proximity sensor does not work anymore (dirty flash).
[ONE Original Android Development] Renosh:
Works perfectly for me on 05/06 nightly of Omnirom. I'm running 241 firmware
[ONE Original Android Development] fmc000:
Thanks, so it works at least with the old 241. It would be nice to know if anyone with the newer versions (c7 or c1.11-0004) would chime in.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] sax0406:
Proximity sensor doesn't work with c1.11-00004 modem and 04/05 nightly. Will check once with the latest nightly and update the result.

Edit: proximity sensor doesn't work with the 06/05 nightly and c1.11-00004 modem too.
[ONE Original Android Development] fmc000:
Thanks. Judging from what I read here and on the slimsaber thread the new blobs and commits broke the compatibility with every firmware pack apart from the old 241.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] maxwen:
try replacing sensor_def_qcomdev.conf with the CM one and report back

Edit:

and ofc as usual - FULL logcat from boot - adb only - not from an app!!!

This is my kingdom - I make the rules!
[ONE Original Android Development] GasLoop:
I couldn't get OmniROM to boot, stuck at bootanimation. Tried everything. TWRP 3.0.2. Could the kernel be missing?
[ONE Original Android Development] Renosh:
Check if you have F2FS partitions. Download File Explorer from play store. Click 3 dot menu and check Filesystem. This ROM only works with ext4
[ONE Original Android Development] saenanme:
Yes. That happened to me when I changed from cm13 to omni

If it is this case, save all your important files from data before to change to ext4

Regards

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] Renosh:
You should quote the guy who originally asked the question. I don't need this info
[ONE Original Android Development] GasLoop:
That would've been good to read on the first page... Yeah cache is most likely f2fs. I'm on VanillaUnicorn now, let's see how it goes. If I don't like it I'll switch to OmniROM. Is there anything else I need to know?
[ONE Original Android Development] maxwen:
Use the right firmware :)
[ONE Original Android Development] GasLoop:
Will the 241 do the job?
[ONE Original Android Development] payne_307:
[MENTION=4683552]maxwen[/MENTION] Several threads back you had mentioned that OPO doesn't have motion sensors to wake the device to show ambient display notifications so nudging the device won't help. I stayed on CM for 2 months, through snapshots, nightlies and the official COS13 to test if the point made by you is actually true. Unfortunately its not. Well AD (Ambient Display) does have a mind of its own in many cases where it doesn't work when you expect it to be and lights up probably a few secs later or doesn't light up or lights when you didn't want it to light up. But on CM it works reliably almost 70%+ times. If my OPO is lying flat on my desk for say 10 mins or so, I lift it and bam - the screen shows the AD. Now that I have confirmed that at the hardware level it does work, could you take a look at why it doesn't work with the motion sensors on Omni? In Omni it lights up only once when the notification arrives but does do anything fater that which I think you are already aware of.
[ONE Original Android Development] maxwen:
I have already told you that the behaviour is as we want it.

AOSP without motion sensor and only pulse on incoming notifications and thats it.
[ONE Original Android Development] payne_307:
Ok. Now its clear. I thought you said it isn't possible. If you want it that way its a different story.
[ONE Original Android Development] anuraag.neo:
[MENTION=4683552]maxwen[/MENTION]

Please enable Snapdragon camera for opo.
[ONE Original Android Development] darjwx:
If you look his gerrit, they are working in snapdragon camera so I guess we have to have just patience.
[ONE Original Android Development] Renosh:
I'm also waiting and really anticipating if it's the modded one by herna (or a better one). It worked and looked better than current CM version. Still, patience is key. I'm sure he's gonna enable it when it's ready
[ONE Original Android Development] stranostrano:
Sorry but, what's wrong with the snapdragon camera? I've it on 05/11 build andit's working good apart panorama mode.

Sorry, my fault. I'm using a modded version
[ONE Original Android Development] maxwen:
well - even if you will get it one day be aware that there wont be anything better then the oppo cam if you just want to make good pictures without fuzz

The snapdragon camera project runs under "minimal life support"

So we will try to make it mostly functional but wont guarantee anything

This is my kingdom - I make the rules!
[ONE Original Android Development] stranostrano:
Hi maxwen,

could you confirm issue on panorama mode in color os camera?
[ONE Original Android Development] maxwen:
No idea - I only take pics and dont use weired childish stuff like panorama mode ☺

But there is a reason why this mode has been removed in our build.

This is my kingdom - I make the rules!

---------- Post added at 12:47 PM ---------- Previous post was at 12:43 PM ----------

You can also just download n3 nightly and exract from there ☺

This is my kingdom - I make the rules!
[ONE Original Android Development] Renosh:
I'm not expecting any additional features just a good looking camera UI that takes pics and I can slide left to view pics. The one by herna looked really nice, when I said better I meant the UI design, not functionality.
[ONE Original Android Development] maxwen:
You will get what CAF provides ?

This is my kingdom - I make the rules!
[ONE Original Android Development] stranostrano:
Oh sure! Me too. And I agree that the pics taked with color Os camera results much better than pics taked with other apps (Snapdragon camera, new google camera, etc.) specially in low light ambient without flash. It results more detailed and clear. Anyway, if someone interested in panorama mode, can use new google camera that have it working.

The only feature that I find interesting in Snapdragon ability is the slow motion feature but there isn't audio then it's completely unusable, almost for my needs.

have fun. ...always!