yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Giocarro:
Thank you! (I run out of official thanks for today...)
[ONE Android Development] antisocialbratt:
That is a stock feature that much i know. But the problem is that none of the roms here on L support headsup notifications except mokee rom. I've tried them all. Thus asking.
[ONE Android Development] nicksmizzle:
this is built from aosp, it's not cm12, that issue is in cm12
[ONE Android Development] K Rich:
Look's like I'll be flashing this tonight :silly:
[ONE Android Development] ek69:
Same question in temasek thread...

Temasek also supports heads up, that much I know since I get them myself :)

Try a clean install or do a test install as a third ROM or whatever number you're at, and try calling yourself.

PS I just installed Tapatalk, i think it gives you unlimited thank you lol and IMO makes browsing XDA much easier on your phone after you setup subscriptions to specific forums (I have all opo forums subscribed, they all show up under subscriptions in Tapatalk - much easier than chrome and seems better than XDA app so far)

Sent From Lollipopified Bacon Goodness!
[ONE Android Development] Giocarro:
So in the end I flashed this build, but something didn't work well...

- didn't manage to get root, neither with SuperSU 2.39 beta nor with 2.37

- center clock option is not there

- OmniSwitch do work properly and is a real pleasure to use.

To wrap up, there is much development to be done before this ROM get a similar level of customization of other Lollipop ROMs; patience is a virtue we know.
[ONE Android Development] lolzballs:
2.39 should work...

Does it say SU binary is not installed?
[ONE Android Development] lolzballs:
So I've been trying to get OmniGears up to 5.0 tonight, at least the on screen nav bar part of it. Since there were no major changes since yesterday's build, I won't be building tonight, unless I get this working.
[ONE Android Development] Giocarro:
Nope, it said something like "no SU present".
[ONE Android Development] scanno:
It should be working. It would be nice if you can provide a logcat after trying to re-download supersu and reflash
[ONE Android Development] Giocarro:
Apologize but I had to flash my backup in a hurry because I need root. Will surely follow further OmniROM development and get back for sure when they'll add some spice in.
[ONE Android Development] vincent219:
Camera Problem

Everything look nice on 1+1, but i found that the camera is quite weird. It looks darker on HDR and feels so much noise. can't figure out why, I tried to download Google Camera, but the result is the same.

Anyways, Thank you so much Devs :)
[ONE Android Development] NuLLV01D:
Try Camera-FV5 with ISO400 and 0.5lighting
[ONE Android Development] vincent219:
Camera FV-5

I purchased the full version of Camera FV-5 and I set to ISO 400 with +0.5 lighting. Taking the pic in the same condition.

The results are the same as the Google Camera (Noise, Yellow Tone, and Look-Dark on HDR Mode)

But Thank you anyways for your answer. :D

Sorry, I want to show you the comparison picture but I can't attach the link since I'm just register.
[ONE Android Development] Aphang22:
Is there a Kill all app ?
[ONE Android Development] Sincide:
How about opendelta/ota updates, is that implemented?

/M
[ONE Android Development] lolzballs:
No, sorry. But the good news is hw/sw keys might come tonight! I have it semi working right now. It just requires a reboot to get soft keys on, but hardware keys still function.
[ONE Android Development] Giocarro:
[MENTION=4961401]lolzballs[/MENTION] any news on upcoming builds?

I had a look at github but was not able to grasp it at all: I see a list of repositories but not a list of commits that could give a clue on what's coming next...
[ONE Android Development] lolzballs:
Next build will be in a week, I'm on a cruise.
[ONE Android Development] jousa11:
Thank you

Thank you very much been waiting for omni lollipop
[ONE Android Development] lolzballs:
Ok, new build uploaded! It is a clean build using no cherry picks, and has been updated to 5.0.2. I shall continue with double tap to wake and stuff.
[ONE Android Development] scanno:
What is wrong with double tap to wake.?? It is in for a long time now.
[ONE Android Development] godabes:
Dounle tap 2 sleep

What about double tap to sleep? I tried this rom today and it didn't work. Can i use it? if yes, how?
[ONE Android Development] ghul21:
Just double tap on the statusbar ;)

Sent from my A0001
[ONE Android Development] vette95:
Flashing now

What's the best GAPPS for this rom?

Anyone?
[ONE Android Development] lolzballs:
Whoops sorry! I meant on screen buttons and stuff.
[ONE Android Development] lolzballs:
I'm just using the basketbuild one. Works well.
[ONE Android Development] pu3cyg:
thanks for compiling the rom :) tested it with PA gapps for a while last night coming from CM12, these are some of my random observations:

- ROM is smooth and stable, at least during my few hours of testing

- "integrated" SuperSU into system settings is nice :)

- there was no default file explorer, so I had to use adb to install TiBu and restore my backup

- restoring SMS/Phone backup from CM12 caused the dialer and sms app to FC all the time

- capacitive buttons didn't light up, although they were functioning well

- double-tap to wake worked, double-tap to sleep didn't

- can't select google account for backup and restore, only "private cache" available

- can't change AppOps settings for system apps, and permissions listed were fewer than in CM12

- cannot configure notification light for individual app

too bad OPO is my only phone so I have to revert back to CM12 for the moment, will definitely keep testing this build whenever I can. Keep up the good work!
[ONE Android Development] lolzballs:
About the capacitive button thing, that was my bad. One of my test changes didn't get overwritten by repo sync.
[ONE Android Development] Trashabwoy:
Cant find the power control widget.. Did you guys leave it out for a reason?
[ONE Android Development] lolzballs:
What do you mean? Performance Control? It should be in Settings.
[ONE Android Development] Trashabwoy:
Not performance control.. The 4x1 power control widget that have the WiFi, Bluetooth, Location, Sync and Brightness control.
[ONE Android Development] OmegaBlaze:
Latest build working great!

Bugs: Camera is way too sharp when processing pics..

Youtube doesn't work. You can open the app up, but when it's time to play videos it says something about problem while playing.
[ONE Android Development] tmotard:
Hi, i've installed the 12/23 build.

1 - Got the youtube problem too..(with or without Nuplayer checked in dev options)

2 - Email app crashed with my imap (SSL with self signed certificate) account (i've too use gmail app instead)

3 - Gesture keyboard crash

do you need log for 2 and 3 ?

thanks a lot for this ROM, i like omnirom very much.
[ONE Android Development] lolzballs:
Logs for 2 and 3 would be helpful. I do know why YouTube isn't working. I forgot to add the other cherry-picks that fix it.
[ONE Android Development] tmotard:
I've to go back to KK omnirom today 'cause 'l going to travel for 10 days and got problem with BT when avcrp. I loose sound when using the pause button of my Sony btn-200...

Will reinstall this ROM after my travel..
[ONE Android Development] OmegaBlaze:
Cherry picks for Youtube: Please add. Please add. ?

And the gesture crash is a gapps or wiping error. No crash for me full wiping & using 12-6 minimal gapps.✔
[ONE Android Development] tmotard:
Full wiped as i was coming from KK.

Keyboard is in gapps ? Not in ROM?
[ONE Android Development] lolzballs:
Sorry was busy(Christmas related stuff) and was unable to upload the build I did on the 25th. I'm compiling with media player fixes and stuff as I'm typing and should be up tomorrow at around 10 am EST, depending on when I wake up.
[ONE Android Development] anishz:
I read through the whole thread, can anyone please tell me if this one has the audio glitches/skips found on all lollipop roms. I can live with other bugs but music is important.

Still named find7op :P.

If possible can anyone upload this to basketbuild or mega, AFH is terrible for me [21kb-52kb download speed].
[ONE Android Development] tobitege:
[MENTION=3229064]anishmahadikz[/MENTION]: Just read post of OP above yours, should be a good clue to your answer regarding audio.
[ONE Android Development] anishz:
Read it but thought it maybe related to the Youtube issue. Anyways if it fixes audio issue then great.
[ONE Android Development] tobitege:
Yeah, sorry if I sounded snappy. ;) Was trying to say that there are more to come, though your Youtube issue may just be with the app itself.
[ONE Android Development] woolmonkey:
Two questions is it possible to increase the brightness of the capacitive buttons? Also is it possible to move long press to menu button for recents instead of home button? I know I can echo a value to brightness for buttons but it isn't permeant it changes back whenever the buttons timeout.
[ONE Android Development] JacK_Sparr0W:
Same questions.. ;)

I've a bug with Textra too.. I've some lag on the app.. How to fix ?

And someone can explain to me the configuration of kernel for best battery and performance ?

Thanks for the work, OmniRom is better than CM for me.. ;)
[ONE Android Development] lolzballs:
I'm going to be trying to implement the capactive key stuff today. Also its not a YouTube app issue, I have it fixed, just uploading right now.
[ONE Android Development] JacK_Sparr0W:
Thanks for your work ;)

I've a bug too with Aptoid (I use it for beta version) and at each download, the One reboot.. :confused:
[ONE Android Development] lolzballs:
Do you know how to provide logcats? That would help.
[ONE Android Development] JacK_Sparr0W:
Oh, ì forgot this step, I will make it :good:
[ONE Android Development] tobitege:
Try using either "Catlog" (Logcat only) or "Andy Log" (export of Logcat, Kmsg, Last_kmesg, Dmesg, Sysctl etc.) for free from Play store, easy to use.
[ONE Android Development] anishz:
Just updated to the latest built [Dirty flashed on previous one]. Offscreen gestures not working and options are grayed out. But audio seems fine for me.
[ONE Android Development] OmegaBlaze:
Youtube problem still present in the latest build?
[ONE Android Development] JacK_Sparr0W:
No, working fine ;)

But gesture off screen are disable in this build…*:confused:
[ONE Android Development] OmegaBlaze:
Thanks! Gestures are usually kernel related. Try TYR,AK, or another kernel of your choice.
[ONE Android Development] JacK_Sparr0W:
No, I flash kernel and phone don't boot…*

Back to wipe all and flash again…*:(
[ONE Android Development] Criticalstriker:
Double tap to wake or gestures are not working, I didnt understand
[ONE Android Development] OmegaBlaze:
Good news guys. Gestures work!

You have to install Synapse from the play store and enable them via the app.
[ONE Android Development] OmegaBlaze:
Anyone got DSP Manger to work?
[ONE Android Development] JacK_Sparr0W:
I got "No UCI support detected"… Why ? :confused:
[ONE Android Development] OmegaBlaze:
You have to install UKM from the AK Kernel thread.
[ONE Android Development] Criticalstriker:
Guys double tap to wake is working. I don't care about the camera and flash things so
[ONE Android Development] lolzballs:
Uhh, no. OmniROM doesn't work with CM kernels because CM uses weird and crappy CAF. Omni has their own version of caf.
[ONE Android Development] OmegaBlaze:
True. But I already found out how to correct the gesture problem without using flashing a kernel. Edited the post as well.

---------- Post added at 10:05 PM ---------- Previous post was at 09:23 PM ----------

Double tap is working.. Read above.
[ONE Android Development] Criticalstriker:
Youtube doesnt work?

Or its my internet ?

edit: Its not working on chrome browser as well. Weird.
[ONE Android Development] OmegaBlaze:
Download the latest version..

12/26..

Youtube working fine for me.
[ONE Android Development] CtlAltDefeat:
Thanks for all this.

When can we expect being able to customize the HW buttons (the way OmniROM does it, allowing all the options as opposed to other ROMs) and being able to launch OmniSwitch with those custom actions?
[ONE Android Development] lolzballs:
I'm going to be starting to implement that when I stop procrastinating ;)
[ONE Android Development] fermasia:
First of all, congrats and thanks for these builds, [MENTION=4961401]lolzballs[/MENTION].

What kernel source (just kernel) are you building from, would you mind pointing me into the right direction? Many thanks. :good:

(is this the one? https://github.com/omnirom/android_kernel_oppo_msm8974)
[ONE Android Development] CtlAltDefeat:
Thanks, this is literally the reason I use Omni lol.

I setup menu button to launch omniswitch, long press menu for last app, and define apps to use software (overflow) menus (implement that too please :P).

Perfect setup as far as I'm concerned.
[ONE Android Development] lolzballs:
Yep using default kernel. I'm not aware of any custom kernel that works atm. I have a feeling you are going to make one. :P If you are good luck and thanks!

Yep just started implementing the basic stuff.
[ONE Android Development] lolzballs:
Ok half of that is implemented. Uploading build right now. https://gerrit.omnirom.org/#/c/11117/
[ONE Android Development] CtlAltDefeat:
Sick, man. Like how you wrote it on the gerrit and not just your own github.

What is meant by half though?
[ONE Android Development] K Rich:
How is this ROM for daily use? I'm running Omni KK on my OPO right now.
[ONE Android Development] störte:
Hi

Does this rom has the dark theme? And is it block based or file based?

As soon as I have time I like to test the rom

Send by Hyperdrive on one+One
[ONE Android Development] fermasia:
I've never tried building something for Omni before.... so no promises :good: But I'm curious and will definately have a good look at that.
[ONE Android Development] lolzballs:
Sorry for the delay, but new build uploaded! Adds screen recording via power + volume up. Also some hardware key enhancements.
[ONE Android Development] woolmonkey:
Great rom I have a couple of problems though the carrier comes through wrong for me shows up a Telus when it should be Koodo Telus owns Koodo so not a problem except that my cell signal well drop to zero unexpectedly and I'll have to do airplane mode or reboot to get it back. I'm not sure if those are related in anyway though.
[ONE Android Development] lolzballs:
Hmm, I'm on Rogers and it's fine. Maybe you could try flashing another radio.
[ONE Android Development] anishz:
Flashed and restored data from Tibu, everything working fine for me till now.

Thanks for posting this.

Edit: NFC not working.
[ONE Android Development] guinnes.s:
nfc switch seems not working ?just me ?
[ONE Android Development] daryelv:
I used to run Omni (KitKat) on my LG G2 and tablets. I'm going to have to try out this ROM on my One+.
[ONE Android Development] lolzballs:
Yep, I'm aware that the nfc isn't working. I'm trying to figure it out.
[ONE Android Development] guinnes.s:
btw wile you there checking .....network operator shown is the wrong one , thanx for your hard work
[ONE Android Development] anishz:
Network operator shown is the correct one for me no issues there.
[ONE Android Development] woolmonkey:
Also have problem with phone not charging it shows that it is plugged in but it never charges.
[ONE Android Development] CtlAltDefeat:
Bug: the binding for "Home button" normal press doesn't work, it just goes to home no matter what.

Also, would like to see "Force overflow software button".
[ONE Android Development] JacK_Sparr0W:
I don't understand why I get some lag on Textra (Sms app) and not with another.. :( :confused:
[ONE Android Development] lolzballs:
So it's been awhile, since I've been busy with school stuff. I'm currently trying a fix for nfc, and I'll be looking into the home binding issue as well.

When I finish that, if it works or not, I will be trying to implement hardware key backlighting stuff. After that, software keys!
[ONE Android Development] OmegaBlaze:
Very very stable build. However, I can't get MTP to work or get my phone to connect to my computer. Any help?
[ONE Android Development] tobitege:
[MENTION=2238538]OmegaBlaze[/MENTION]: already tried switching on/off USB debugging in Developer options while connected?
[ONE Android Development] OmniFicent:
[MENTION=4961401]lolzballs[/MENTION]

scanno added NFC fixes in gerrit, check them out; haven't been able to test it out just yet, but I"m assuming it works.
[ONE Android Development] OmegaBlaze:
Yes. It's been unable to connect to my computer since the first build of OmniRom (lollipop).
[ONE Android Development] K Rich:
[MENTION=2238538]OmegaBlaze[/MENTION] I had this issue with OmniKK and I had to update the drivers in Device Manager... don't know what, but it was coming up as some Acer product??
[ONE Android Development] OmegaBlaze:
It does not show up at all. My drivers are up to date. All other lollipop ROMs work fine. I'm on SlimLP now.
[ONE Android Development] störte:
No more F2FS for you ?

Send by Hyperdrive on one+One
[ONE Android Development] OmegaBlaze:
No more f2fs for me lol.. It made my system very buggy.
[ONE Android Development] lolzballs:
Yep, I know. It wasn't working before, but I added some other commits, and we've got nfc working. Uploading now...
[ONE Android Development] lolzballs:
Try turning off MTP and then turning it on again.
[ONE Android Development] lolzballs:
Yay! New build with NFC fix uploaded. If you turned on NFC before, and seen misc battery usage, this should fix that battery drain and make NFC work again.
[ONE Android Development] JacK_Sparr0W:
Yeah, NFC fixed, now, I've perfect ROM on my One. Thanks for your work guy. That's perfect ;)

Possibly to include one killer button on multitasking ?

That's only one the thing is missing

Possibly screen color calibration ?
[ONE Android Development] treffer:
disk encryption

FYI, here is how to enable disk encryption.... Use at your own risk!

In your recovery, unmount /data and run

mke2fs -T ext4 -L data /dev/block/mmcblk0p28 58510500

This will wipe your data! And it will cost you ~4MB of /data (that's the reason why encryption doesn't work, /data is defined to be as large as the partition, 58510540, you can check the partition size with cat /proc/partitions).

On your phone do

su
vdc cryptfs enablecrypto inplace pin hex-of-your-pin

BOOM! (you can use password instead of pin for passwords, but make sure to hex encode your password).
[ONE Android Development] zard:
Hi, how can I run that command in recovery? I figured that in Recovery (I'm using CWMR), unmounted data, and with my OPO connected to my computer, I ran the command. Below is the output. Looks like the command failed. Can you tell me what went wrong?

G:\1+1\platform-tools>adb shell
~ # mke2fs -T ext4 -L data /dev/block/mmcblk0p28 58510500
mke2fs -T ext4 -L data /dev/block/mmcblk0p28 58510500
mke2fs 1.41.14 (22-Dec-2010)
mke2fs: Filesystem larger than apparent device size.
Proceed anyway? (y,n) y
y
Filesystem label=data
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
3661824 inodes, 14627625 blocks
731381 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
447 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,

4096000, 7962624, 11239424

mke2fs: Invalid argument while zeroing block 14627600 at end of filesystem
Writing inode tables: done
Creating journal (32768 blocks): mke2fs: Invalid argument
while trying to create journal
~ #

On phone, am I right that the command is to be run with terminal?
[ONE Android Development] Giocarro:
Apologize for bringing this topic on from time to time but I read the changelog and searched the thread without getting any update: is the center clock implemented in the last build?
[ONE Android Development] treffer:
It looks like you have a different partition table. Perform a cat /proc/partitions, this will tell you the size of the partition, subtract a few MB and you are safe. You should not get a "larger than partition" warning.
[ONE Android Development] zard:
Thanks. Did as suggested and first command went through. Partition size was 12960399, so in the command, I used 12960300.

Rebooted and on phone, did the second command, device rebooted.

Setup "pin", then I tried "Encrypt phone", it rebooted but encryption didn't work.

This behavior was the same before I tried the first command in recovery.
[ONE Android Development] treffer:
Can you give me an "adb logcat"? Any output of "vdc" is especially usefull. Note that hex-of-your-pin is a placeholder, for 0000 you'd have to use 30303030.

Here is a small html page you could use to convert anything ascii to hex (save it with a text editor as something.html and open it with e.g. firefox)

<html><head><script>
function convertToHex() {
var str = document.getElementById('intext').value;
var hex = '';
for(var i=0;i<str.length;i++) {
hex += ''+str.charCodeAt(i).toString(16);
}
alert(hex);
}
</script></head><body>
<input type="text" id="intext" />
<button type="button" onClick="convertToHex()">convert</button>
</body></html>
[ONE Android Development] treffer:
We are on the same page, that screen means your phone is encrypted. Congratulations :)

If you no longer have to type a pin on reboot go to the lock settings, change the pin (or password) and enable the setting saying "require pin for bootup" (not sure about the exact wording).

If you don't believe me try this:

pc$ adb shell
A0001 $ su -
A0001 # grep device-mapper /proc/devices
254 device-mapper
A0001 # cat /sys/dev/block/254\:0/dm/name
userdata

(Step by step: We need to know the major id of device mapper devices, in this case 254. Device mapper is used for lvm, crypto and some less common tools, in this case it's crypto. Anyway, we can then look what name the devices have. You could contiune to dig deeper and double check what's there)
[ONE Android Development] zard:
Thanks for your guidance.

1. Firstly, you didn't respond to this clarification. Hope you can shade some light. In my case, it seems that the encryption PIN has not been successfully converted to accept hex, so my risk is higher. So since it didn't work, this step is redundant. Am I correct?

This runs as before, after carriage return, the command is repeated on screen, followed by a reboot. After sometime, I will see the prompt to enter pin. I enter in hex, not accepted. I enter in numbers, it was accepted.

2. Now back to your respond below, I'm using PIN, and tested enabling and disabling that "Require PIN to start device", and upon reboot, I'm still asked for PIN, and I had to key in my PIN (not in hex). That setting doesn't make any difference for me. So I'm still wondering what behavior was supposed to be with enabling and disabling it.

If you no longer have to type a pin on reboot go to the lock settings, change the pin (or password) and enable the setting saying "require pin for bootup" (not sure about the exact wording).

3. Lastly, I tried out the steps and device-mapper, and on my device, it shows exactly the same as what you shared. I'm not sure what is the significance about this. My interpretation of the commands and output, i.e. device-mapper is "254", and it is the "userdata" partition.
[ONE Android Development] Consty509:
First impression daily use

Thanks for posting!

Running fine for daily use, flashed it few days ago!

One issue I experience is that Google authenticator makes a fc when trying to configure.

Uses a lot of battery also , but this is the same as with the stock kernel/rom. Maybe a kernel related issue, trying to figure that out right now.

Really nice to have lollipop running on my 1+1 for which thanx to the OP.