yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] pa1281:
Hi [MENTION=2225255]herna[/MENTION]

Can you remove that icon?or provide a switch to enable/dusable that?or a flashable zip to remove it?

Please do reply..thank you..
[ONE Original Android Development] :
Awesome ROM, the launcher3 however settings still don't open for me :)

Charging also doesn't work.

The rest is sweeeet
[ONE Original Android Development] deepaklunked:
Thanks for your response. Waiting for your next build. Also, I am on Tapatalk, so I dunno how to hide images. ;)

Also, can you shed some more light on custom header panels. Like, how to make one, or where to find the existing packs, how to apply them (i.e., where to place them so that it is detected in settings)..
[ONE Original Android Development] Jsalinger:
Charging Issues 12-11 ROM

I installed this ROM for the first time last night (6.0.1-2015-12-11). Everything was fantastic (really great ROM, even my GPS works again)!

However, when I unplugged from a full night of charging, today, the phone was still at 15%. I charge my One Plus One on an older Samsung charger (750mA), but it's always been able to charge the phone fully overnight. This morning, I turned it on, and plugged the charger in again to see if it was a loose connection. Indicator showed a charge, but percentage did not increase after 10 minutes, in fact, with screen on, percentage dropped a few points.

I took a look at the charge rate through the Ampere app, and, while charging, it showed a drop of -30mA while the screen was on and the charger was plugged in. It showed -300mA while the charger was unplugged.

I have since plugged the One Plus into an Apple iPad 2A charger, and the phone is taking a charge, and battery is increasing. Ampere shows 1A being pushed to the battery with that charger.

It does appear that something isn't quite right with charging in this latest release though. I have never had any charge issues on this phone with the lower amperage chargers (and have run stock, and 10 other custom ROMs).

Hope this helps with any diagnosis!
[ONE Original Android Development] the Doctor:
My carrier in Cambodia just got 4G. (Yes, we are behind the times a wee bit!) When I changed SIMs this AM, I was on Omni 6.0 and could only get H+. Flashing back to CM OS 12.1, 4G came on right away. I haven't had time to research modem issues yet, so I'll just leave this here for now.
[ONE Original Android Development] xtremez:
What you can do to check is

1. *#*#4636#*#*

2. Click "Phone Info"

3. Look for "Set Preferred Network Type" it should be showing LTE/GSM (Auto)

For me I had that issue too, you have to go back to a 5.1.1 ROM and then change it, the flash to 6.0 again. That was what i did, not sure if there's a better way or easier way now.

Using TWRP, make a Nandroid Backup so that you can easily restore your phone after doing that. Hope this helps!
[ONE Original Android Development] thenessus:
Something changed somewhere since the late November releases and the recent December releases.

"Mobile Radio Active" bug re-appeared where it was resolved in the November releases.

To explain: this bug represents itself by showing only when using Mobile data and not Wifi. Power consumption shows very high usage for any app you use, even if only used that app for just 1 minute.

You can reproduce the issue by making a completely clean install, using Chrome for 1 minute and then leave your phone alone. Come back to it after 1 hour and you will see that "radio active" is active for an hour, and takes and continues to take more power than anything else.

That is an extreme example but you can play with it however you want, will still be the same. On Wifi it will be completely different.

So, back on November builds "mobile radio active" was GONE! it was same as on Wifi!

Since December builds something made it come back. Do you know what changed?

this is the same in the other Omni thread, so it's an general Omni issue and not just [MENTION=2225255]herna[/MENTION] 's build.
[ONE Original Android Development] anbinhv:
Thanks [MENTION=2225255]herna[/MENTION] for the rom: very stable and very good battery life!

May I request some features: double tap to sleep on lock screen, hard key custom actions, phone vibrate when connected, camera 4:3 preview. It would be nice to have these useful features. If not, it's no big deal. Thanks again!
[ONE Original Android Development] ogrillion:
I saw people complaining of this in other threads to, not just omni. So I believe it's more of an aosp issue.

I haven't seen anyone say that it's a December issue though - that's interesting. Maybe it popped up again when things were updated to 6.0.1.? I have seen people say that they got better battery in 6.0 builds, that would make sense. Hrm
[ONE Original Android Development] SreeCR7:
Kind of wished if these were available.

Is it just for me?

1.) Gesture typing on AOSP Keyboard is not working and I believe the word suggestions are messed up as well. :rolleyes:

2.) Bluetooth visibility timeout is not available? :confused:

3.) The CM12.1 SultanXDA ROM had the option to change host-name inside the developer options, could it be possible to add that. :)

I miss these three things badly. :(

If these were addressed here, then pardon me. :)

btw, simply awesome ROM, no other probs so far :highfive: :good: :victory:
[ONE Original Android Development] herna:
Give a look here: https://github.com/maxwen/DaylightHeaderSample

No. This is an icon from an Omni feature and we don´t plain on add just a switch for hiding an icon, it makes no sense.

If you want to use the Automatic Brightness press the button, if not press it again, but we are not going to make a switch for it, we like it that way, as well as it does not disturb.

I already found the issue of Settings crashing, as well as forgot to add the fix for charging issues in the last build.

Actually we have a commit which mainly fixes all those issues, just I forgot to add it on the latest build. Anyway, as an official answer, if you don´t use the stock OnePlus charge we probably will not put attention or effort to solving other kind of issues with other chargers. We will try if we can, but this is something OnePlus has to fix, not us.

Is the second time you ask ... Can not you wait me to tell about it or reply your old one? Two posts for the same thing, that´s not the way.

Double tap on lockscreen, not sure if we will add, probably not, is not something needed, as well it does not make a lot of sense.

Hardware key custom actions, they will come soon, but we don´t have an exactly date for that. Once it´s added I will tell, so don´t ask for it again in weeks.

Phone vibrate when connected, not.

4:3 camera preview, maybe, but is not something extremely needed.

Hi!

1. Yes, AOSP keyboard has been broken in Omni for months, we had issues even with 5.0, maybe even 4.4. I guess we need a little update.

2. Why do you need this? It´s not added on AOSP, so why confused? We will not add it, if you want to be visible, just open Bluetooth settings as every nexus owner does, is how Google wanted it, and we don´t think it´s bad.

3. Nope, never. We are not allowing users to change stuff which is related partially to build.prop. Maybe CM or Sultan did, we will not.
[ONE Original Android Development] SreeCR7:
1. Ohh, didn't know. I understand :)

2. Neither do I, think its bad. :) It was easier to just leave it on. Guess habit had the better of me. :D

3. Alright, I get it :)
[ONE Original Android Development] anbinhv:
1. My bad! Sorry for the second time ask. I did't read your reply to me and it's all my fault.

2. Just my personal opinion, the rom is almost perfect itself, I love the stability, smothness and battery life of the rom, they are always priority to me. Btw xposed work fine with the rom and I can add the features I want ( except the camera one, but I can install Oppo camera). No lags, no bugs, no battery drain.

Ps: really appreciate your work dev!
[ONE Original Android Development] thenessus:
[MENTION=2225255]herna[/MENTION] Of course it makes a lot of sense.

Double tap to wake to see what time it is/new messages, and another double tap to close the screen and forget about it.

tap tap, tap tap, and that's it. All while the phone is sitting on your desk without the need to pick it up, swipe, or do anything else really.

It's the essence of sense-making :)

but that doesn't matter to me though.

Staying on latest November build as it does not have mobile radio active bug

double tap to sleep can be enabled on xposed.

thank you for everything! :)
[ONE Original Android Development] saiwala:
[MENTION=2225255]herna[/MENTION] help, please, not the first time of asking: with recent updates, headset buttons only work at reducing the sound! how to regain control of track switching and etc.

thanks in advance:o
[ONE Original Android Development] HenryLee80:
As these two users I have quoted, I can also confirm I had no mobile radio active bug in November's builds but I do have the mobile radio active bug now, to be precise it appeared on the 11th of December build.

(Same GAPPS: Opengapps).

It could be related in some changes Google added recently, or I don't know: this bug was an annoying one in Lollipop and I really hoped Marshmallow would have squashed it for once and for all.
[ONE Original Android Development] thenessus:
Not GAPPs

Installed November again with latest open gapps, no bug.

Installed same gapps on latest Omni - bug
[ONE Original Android Development] HenryLee80:
Yes, sure, I didn't mean to say the bug is related to the GAPPS: as you also wrote, I meant to say I tested Omni November build and Omni December build (with the same OpenGapps, as you did) and the bug was there only in the Dec build.

So, I didn't change any variable: same TWRP, same GAPPS, and the mobile radio active appeared in Dec.

Basically, we agree.

(P.S: it might not be only OmniROM related, I've experienced this bug also in other MM ROMs: but I don't wanna go OT - also, I think it's up to Google and Google alone to fix, as no developer yet could find a real definitive fix to this bug).
[ONE Original Android Development] abhibnl:
Guys this bug is not fixed as of now in marshmallow. So if you'll use mobile data, phone's standby drain will take a hit. Google has only acknowledged the bug and it should be fixed in a future android update. Unless ofcourse someone from omni team has free time enough to debug this annoying issue, this bug is still available in MM.

Sent from OnePlus One
[ONE Original Android Development] thenessus:
According to this

https://code.google.com/p/android/issues/detail?id=190396

The bug is a small defect, and won't be fixed on next release, no such priority on their minds.
[ONE Original Android Development] josera06:
if it was not a bug in LP, in MM neither :crying:
[ONE Original Android Development] k3vink3vin:
Does anyone occasionally encounter an unresponsive lock screen when you wake the device, and the only fix is to reboot?

Happens to me once every few days
[ONE Original Android Development] Lupin The Third:
That download count is evil...
[ONE Original Android Development] deepaklunked:
Lol [emoji23]
[ONE Original Android Development] tofu:
Aosp keyboard swype / gesture type issue solution

Mr [MENTION=4954496]musklor[/MENTION] at slimsaber thread found a (temporary) solution for aosp keyboard swype / gesture typing issue: he copied Sultan's rom's latinime.apk from /system/app/latinime/ and just installed it.

And it really works!

You can download it from here: http://www.2shared.com/file/sSeYVUmR/LatinIME.html
[ONE Original Android Development] fards:
Where does it say (other than someone complaining) that it is a small defect and wont be fixed?

I can see one response from a Google employee that is been passed onto the developers.

The issue type says it's a defect, and the priority is small, which compared to a zero day exploit it is.
[ONE Original Android Development] herna:
Hello guys!

A new update is here. This update was not planned since I was working on some features, but at the moment and even with the so little changes it has, they are really so important, more than even some features, so here goes the changelog:

* Fixed issues with non booting OnePlus One devices: One of my teammates discovered what was the issue for this, so now everyone which was unable to boot or pass OnePlus logo will can enjoy OmniRom, finally! This also applies for 5.1.1 nightlies!! Time to enjoy!

* Fixed network switching issues: now we can switch between LTE/3G/2G without issues.

* Documents UI: fix selected items: add a background for selected items in DocumentsUI, somehow we lost it before.

* Improve recents-view: Now when there are no tasks on recents, if we touch on the screen the recents screen will go to Launcher. Faster than touching any navbar button for going back.

* Rework Find7Parts: Added permissions for camera to open directly when we use the gesture at Settings->Advanced

* Added Lockscreen settings icon: now I´ve added an icon for those who were confused about it not having any icon.

As always, download at OP!
[ONE Original Android Development] wozn:
Herna did you consider adding all extra layers/rro commits to your ROM, or has omni looked at it. Or are you happy to stay stock mm in regards to layers?

Thanks for updates
[ONE Original Android Development] ashwanikoul:
Switching between networks was so much required, the only reason for me to be trying other ROMs.

Now I can peacefully install 17/12 build and forget about any other ROM. It's perfect now..

Thank you Herna
[ONE Original Android Development] Renosh:
Yup network switching works, God bless Omni devs for this. Happy holidays
[ONE Original Android Development] wingedpanther:
[MENTION=2225255]herna[/MENTION]

THANKS

---------- Post added at 05:05 AM ---------- Previous post was at 05:04 AM ----------

Same here :good:
[ONE Original Android Development] Renosh:
Can anyone else confirm for me if pressing the hardware back key (software back works fine) while in Snapdragon Camera causes the camera to freeze and crash and become unusable until reboot? Might have to do a clean flash as I dirty flashed from Samstone build to [MENTION=2225255]herna[/MENTION] build. No mods are in use
[ONE Original Android Development] KenjiHannya:
If u pressing hardware back key, u kill the camera.

Tested now.

Clean flash
[ONE Original Android Development] thenessus:
Simple - its been a small defect since the first bug tracker raised by users for lollipop.

Each time Google are like "oh? OK, interesting, but not a priority". And each release users bring it up again, and Google are surprised with the same boring reaction.

Once my phone dies (I hope it won't) I am ditching Android. It is unbearable.
[ONE Original Android Development] black_hole:
Last build boots for me now !

:)
[ONE Original Android Development] theviper:
For me snapchat fcs .. Anyone else facing this too?
[ONE Original Android Development] abhibnl:
God bless [MENTION=2225255]herna[/MENTION] [MENTION=4683552]maxwen[/MENTION]

Finally i can use omni and roms based on it. Thanks alot for fixing network switching guys.

Sent from OnePlus One
[ONE Original Android Development] skad:
Greats finely booting :D

Very thank you [MENTION=2225255]herna[/MENTION] and your team mate
[ONE Original Android Development] Midzuel:
Do I need to flash some kind of firmware/modem before?
[ONE Original Android Development] deepaklunked:
What ROM are you coming from?
[ONE Original Android Development] Midzuel:
Im on jgcaaps
[ONE Original Android Development] deepaklunked:
Cm13 or cm12?

Anyways, you may just flash Omni. You wouldn't need to update your firmware.. Just go ahead and enjoy Omni.
[ONE Original Android Development] Midzuel:
delete
[ONE Original Android Development] webore:
Well done ! will try your build later for the network switching function.

samestone says he will be on vacation till middle January.

Will you keep updating?

And as a non English user ,I miss the T9 dialer very much but maxwen said he will hardly add it .can you help with this ?
[ONE Original Android Development] Midzuel:
Any way to get the gamma setting working from Synapse or other way to apply the amoled settings? Colors seems so washed out
[ONE Original Android Development] CBpbxEcmecmBeH:
hey guys, what GApps are you using? For me opengapps 6.0 pico failed to boot. Thanks!
[ONE Original Android Development] black_hole:
No problem with slim zero gapps ;)
[ONE Original Android Development] sapphirecoupe:
WiFi is unusable.... I have to disable WiFi just to get a data connection at all.

This happens on every version of omni I've tried, including slim.

I never had this issue on lolipop, but is quickly turning into a deal breaker...

Firmware 241.
[ONE Original Android Development] Midzuel:
Overall a good smooth rom, no hiccups. But I dont think I will stay too long because of that washed screencolor and snapchat front camera has weird quality,dunno why.
[ONE Original Android Development] black_hole:
Since I am using this rom I have the screen flickers.

Have you ever encountered this problem?
[ONE Original Android Development] :
Flash Donkey Kernel and get a kernel mod app, (example Kernel Adiutor)

---------- Post added at 10:18 AM ---------- Previous post was at 10:16 AM ----------

Not happening here. Latest update and Donkey 14. Though I did not have issues with stock kernel neither.

---------- Post added at 10:19 AM ---------- Previous post was at 10:18 AM ----------

I only get glitches, and it is like once a day on Chrome beta, it will do a red box and then just resume as normal.
[ONE Original Android Development] Midzuel:
Ty, do you use Omni with darkobas in multirom? How?
[ONE Original Android Development] :
Nope, don't like Multirom, so I switch from one to the other from time to time. I'm mainly on Omni these days though.
[ONE Original Android Development] Midzuel:
What keeps you with Omni? If I can ask ofc
[ONE Original Android Development] CBpbxEcmecmBeH:
again, SetupWizard FC... :(

Slim_zero_gapps.BETA.6.0.build.0.x-20151215-2013.zip

this is what I used
[ONE Original Android Development] black_hole:
Try with 20151212 maybe, like me?
[ONE Original Android Development] :
[MENTION=4683552]maxwen[/MENTION] 's jokes:p

Also, I feel it is better supported, and is a lot more stable since darkobass likes to try a lot of new things (which is great, but not for my DD)
[ONE Original Android Development] skad:
Hi [MENTION=2225255]herna[/MENTION]

i'm in front off something weird:

sometime (there isn't fixe time) the phone goes into SOD. i can't wake up the screen, adb doesn't go log anything BUT my desktop manager mount 6 partions:

lsblk of my phone

sdc 8:32 0 58,2G 0 disk
├─sdc1 8:33 0 64M 0 part /run/media/skad/00BC-614E
├─sdc2 8:34 0 512K 0 part
├─sdc3 8:35 0 32K 0 part
├─sdc4 8:36 0 32K 0 part
├─sdc5 8:37 0 1M 0 part
├─sdc6 8:38 0 500K 0 part
├─sdc7 8:39 0 16M 0 part
├─sdc8 8:40 0 500K 0 part
├─sdc9 8:41 0 1M 0 part
├─sdc10 8:42 0 1,5M 0 part
├─sdc11 8:43 0 1,5M 0 part
├─sdc12 8:44 0 10M 0 part
├─sdc13 8:45 0 10M 0 part
├─sdc14 8:46 0 1,3G 0 part /run/media/skad/57f8f4bc-abf4-655f-bf67-946fc0f9f25b2
├─sdc15 8:47 0 32M 0 part /run/media/skad/57f8f4bc-abf4-655f-bf67-946fc0f9f25b1
├─sdc16 259:0 0 512M 0 part /run/media/skad/57f8f4bc-abf4-655f-bf67-946fc0f9f25b3
├─sdc17 259:1 0 16M 0 part
├─sdc18 259:2 0 1,5M 0 part
├─sdc19 259:3 0 1K 0 part
├─sdc20 259:4 0 8K 0 part
├─sdc21 259:5 0 1M 0 part
├─sdc22 259:6 0 16M 0 part
├─sdc23 259:7 0 32M 0 part /run/media/skad/ColorOS DRIVER
├─sdc24 259:8 0 32M 0 part
├─sdc25 259:9 0 16M 0 part
├─sdc26 259:10 0 8M 0 part
├─sdc27 259:11 0 64M 0 part
├─sdc28 259:12 0 55,8G 0 part /run/media/skad/57f8f4bc-abf4-655f-bf67-946fc0f9f25b4
└─sdc29 259:13 0 288M 0 part

The log from my adb shell before SOD is in attachement

The log from my last_ksmg is in attachement

Just for the point, my phone only boot with the last build, before i was stuck into the one+ logo

Thank
[ONE Original Android Development] Midzuel:
Any way to stop auto updates for Snapchat only? I want the rest to be up to date
[ONE Original Android Development] deepaklunked:
You can do it in play store..
[ONE Original Android Development] indian84:
Open Play Store and search Snapchat. Click on three dots on top right and untick Auto Update.
[ONE Original Android Development] theviper:
Same thing happnd wid me too ie not able to wake up d screen ..
[ONE Original Android Development] drexciya:
With third party camera applications like F-V5 and Vingnette the image is upside. However the picture created has the correct orientation.

Is this a known bug or am I missing something?
[ONE Original Android Development] 69gm:
Sorry if this is a little off topic but what is the best alternative to change the battery icon? I don't find just a little bar very helpful in letting me know how much charge is left.

Other than that little, minor thing, I am find this to be very stable and fast! And without CM's stupid mistakes!!! LOL!

Thanks for all your hard work in deving!!!
[ONE Original Android Development] deepaklunked:
A better alternative is to use xposed with gravitybox..
[ONE Original Android Development] Mich2027:
Dirty flashed omni-6.0.1-20151217 over omni-6.0-20151202 with just cache/dalvic cache cleaned and everything works fine.

WIFI to LTE swich works fast, thanks for the fix.

Great work [MENTION=2225255]herna[/MENTION] thank you very much.
[ONE Original Android Development] ryanismo:
Was having issues with CM13 Nightlies so I have decided to try this one out. Clean flashed 12/17 with Open GApps, set up as a new device. Took 2 photos using the Snapdragon Camera. Forced Close and I'm not able to use the camera again. Reverted to CM12.1S. ?
[ONE Original Android Development] HenryLee80:
The weirdest of Google's bug: Mobile Radio Active bug was present in the 11th of Dec build and it is

not

there anymore in the 17th of Dec build: I don't know what the devs have changed in the \system partition, but the bug is gone for me on the 17th of Dec build.

Again, thanks you herna! Great ROM you've cooked for us!
[ONE Original Android Development] stranostrano:
This rom works really good. Fast and power friendly.

Anyway, I've a fc when I try to record in slowmotion with camera and if I try to re-open camera app, I've a non working blank screen and I need to reboot phone. It happen with BootMGR ColorOs port v 2.6 and with CameraNextMod.

I dunno if it's related to MM or to rom.

Anyone can try to record in slowmotion and report if it work?
[ONE Original Android Development] 69gm:
Yeah I've thought about that too. I was just hoping to avoid Xposed for the time being. Thanks though!

---------- Post added at 09:53 AM ---------- Previous post was at 09:52 AM ----------

Sorry I meant to hit this... Didn't quote...
[ONE Original Android Development] 69gm:
Sorry I meant to hit this... Didn't quote...
[ONE Original Android Development] Midzuel:
Can confirm that bug on mine device too but all you had to do was reboot and use alternative camera.
[ONE Original Android Development] ryanismo:
Oh, okay. I just thought if I'm encountering issues with just built-in apps, what more if I decided to install 3rd-party apps and make it as my daily driver? Been looking for that daily-driver-MM-ROM for quite a while now. Always ends up reverting to Lollipop because of random reboots and force closes.

I understand this is in development stage but I couldn't tolerate such issues that will affect some basic functions of the phone.

But this ROM looks nice and better than other MM ROMs. ?
[ONE Original Android Development] saiwala:
Everything is fine in this ROM, but even at high frequencies CPU (min. 1190-1497\max 2470, smartmax, ondemand...) - observed retardation and jerky scrolling almost in any app, despite the fact that I basically don't use any kind of the "improvers" of the system....

of course, a special thank you [MENTION=2225255]herna[/MENTION] for the update!!!:good:
[ONE Original Android Development] ogrillion:
This latest build is pretty awesome. I have absolutely no battery drain when off wifi.

I been on lte only all day and still have tons of battery left. Haven't seen this since kitkat. Awesome stuff, thanks for this rom
[ONE Original Android Development] deepaklunked:
True. I've been digging the latest build too..