yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] freshgiammi:
Correct.

I'll see what I can do, but I have major stuff to work on kernel right now.

Yes please, if you're building from my source, could you test F2FS?

And thanks for the notifications sound issue, looks like i missed it.. I'll add it in the next build.

As for the other commits yeah, they're mostly leftovers from the testings I've done for the HAL implementation.

I should probably clean the entire device tree, too.... lots of CM stuff that's defined and not needed, or stuff that is not up to date. Not relevant stuff, tho.

Still, thank you! Hit me up on hangouts if you want, it would be nice to work together. Seems like a lot of users are building from this rom or with the commits I have, and nothing could make me happier.
[ONE Android Development] devilsshadow:
Checking on the progress rom has become my favorite thing to do each morning. Keep up the good work and im happy to see more people getting their hands dirty in this thread. Kudos!
[ONE Android Development] lumufei:
Anyone tried 3.10kernel on this ROM ?
[ONE Android Development] se7enlyn:
IMHO, the stock kernel is best;):svetius:
[ONE Android Development] hammer-is:
It's not working. I tried to message you on Hangouts (with a link log files).

If data and cache is formated to F2FS the ROM "detects" it as a EXT4 filesystem with errors and tries to correct it (which it does ...) and the result was that most of my apps and data was still available after my first reboot.

That might also explain why [MENTION=5267387]Evolitist[/MENTION] reported that he succeded in booting the ROM on F2FS.

Rebooting to TWRP would probably show [MENTION=5267387]Evolitist[/MENTION] that data and cache have just being reverted/recovered to EXT4.
[ONE Android Development] Spider-Vice:
Is anyone else having their screen turning on randomly, despite Ambient Display being off? Just updated to the 22nd build today.
[ONE Android Development] LucentBirch:
Three random reboots in two minutes. Started with using Google assistant. It froze and rebooted, then rebooted two times after that -- not using Google assistant. Here's kmsg: https://mega.nz/#!aIMBCaiB!m2V7G3aE14guD7Rub0KzQ-fKfKwQatx7_QL41xoNRHk.
[ONE Android Development] myshakugan:
Same here. Screen sometimes turns on randomly, even when ambient display is off.
[ONE Android Development] freshgiammi:
Try to disable it in Settings -> Moves. I'm not affected, but the last build has no changes regarding this behavior.

Please upload the log to some other hosting site. Mega doesn't work with safari, sadly..
[ONE Android Development] LucentBirch:
What works best for you?
[ONE Android Development] freshgiammi:
Pastebin or Hastebin is fine.
[ONE Android Development] Spider-Vice:
Yes, that seemed to fix it, thanks.
[ONE Android Development] freshgiammi:
No problem. That's where the new dozePulsePickup resides, apparently. I wonder if the one set in Settings -> Display is just a leftover..
[ONE Android Development] devilsshadow:
just a quick question, what's the difference between this build of AOSP and the other one available for the OPO?
[ONE Android Development] LucentBirch:
Using Adiutor creates large kmsg files that I can't use pastebin or hastebin -- is there an app that makes them smaller than 910kb? Anyway, here's my kmsg: https://paste.ee/p/DqxrR
[ONE Android Development] freshgiammi:
We're actually working together. We share the same philosophy, but as for now, my rom is more updated.

I started this rom by myself while kwoktopus continued the work of updateing. Evolitist then took upon the rom when kwoktopus left.

We could say that we're just two different named roms: While he maintains an AOSP rom that comes from the first experimental version from updateing, i'm taking action against all the little bugs that are causing issues. We'll probably get to the point where our roms are the same, however.

But while my rom is getting frequent updates, I can assure you all he's actually doing a tremendous work, behind the scenes.

You should get logs via PC, it's easier and more complete.

adb pull /proc/last_kmsg last_kmsg.txt

I believe this should be the command, if i'm not wrong.

However, the logs aren't showing any errors before crashing, so I can't say.. is that a dmesg or a last_kmsg?
[ONE Android Development] LucentBirch:
It's last kmsg. Can't always get it via PC because it always seems to happen when I'm on the road away from my computer.
[ONE Android Development] devilsshadow:
Thank you for the very detailed answer. Good work to everyone involved and thanks everyone for this great aosp experience.
[ONE Android Development] myshakugan:
Feel pretty stupid for not noticing that option till now. That seems to have fixed it for me too. Thanks for pointing it out. ?
[ONE Android Development] LucentBirch:
Haha two random reboots again while on the road...Not even touching phone. Weirdest stuff man...
[ONE Android Development] freshgiammi:
Weird that last_kmsg has no message about that.. Perhaps it's an app or something else? I doubt it but who knows, I can't replicate... Please try this kernel and let me know if you get other reboots.

Also, [MENTION=6363737]Gawd[/MENTION] could you test if Fast Charging is now working fine?

Tagging another user, [MENTION=4946927]arfasyrf[/MENTION] could you flash this too and see if it fixes your issue with google fit?

Please, also test the video on the bottom of this page and let me know if watching it makes the phone crash and reboot.

http://www.webmfiles.org/demo-files/

EDIT: [MENTION=4219776]indhimaga[/MENTION] please, since you were among those affected by the slow charging issue, see if this kernel fixes charging for you.
[ONE Android Development] LucentBirch:
Yeah, I don't know. Don't have BBS anymore, so that's weird.

Which kernel?
[ONE Android Development] Gawd:
The one attached. Choose install image in TWRP and then choose boot partition.

[MENTION=4986658]freshgiammi[/MENTION] I switched to another ROM, so can't test, sorry.
[ONE Android Development] fabio.pagliuca:
Yes the phone instantly reboots
[ONE Android Development] freshgiammi:
No problem, I'll tag the other affected users later.
[ONE Android Development] freshgiammi:
EDIT: Double post, the XDA app really sucks.
[ONE Android Development] freshgiammi:
Isn't ths original section for ROMs not based on anything? Not really familiar with the two, my ex device forum had a united section.
[ONE Android Development] freshgiammi:
All good here.
[ONE Android Development] Rehank:
Overdrawing my status bar and dock i tried everything its not going :confused:

I also did dirty flash
[ONE Android Development] sabbeer:
can i istall it as a secondary rom?
[ONE Android Development] beatbrot:
Unfortunaetly there is no long-press-home for now-on-tap..would be great to have!

EDIT: Oooops, there is, sorry, my fault
[ONE Android Development] freshgiammi:
Substratum theme applied?

Tried rebooting? Never had this issue.
[ONE Android Development] wozn:
Exactly asop + oms only is perfect. Thanks Dev
[ONE Android Development] Rehank:
I didn't applied any theme and i rebooted also its not going
[ONE Android Development] freshgiammi:
Oh I see you dirty flashed. Clean flash it then, and let me know.
[ONE Android Development] darjwx:
Afaik the original development section is for original works not necessary with a unique base but also with unique features or code. Also the bring ups to newer android versions are there.
[ONE Android Development] freshgiammi:
Well this is a bring up to newer android version... All AOSP Roms are there (such ad AOSParadox or updateing's), i don't see why mine shouldn't.
[ONE Android Development] darjwx:
If this ROM is not based on an existing project, yes it should be I think on original development. If it's based on updaetings work, no. Idk which is the case. Did you move the thread to android development or other did it? If you think this should be in original just show a moderator why and ask him to move the thread.
[ONE Android Development] freshgiammi:
This ROM is based on AOSP. Yes i have based it on updateing's work at first (almost every ROM has his commits) and then moved customizing on my own. An example is HAL, since i have CAF and he has AOSP. Also I have Substratum, I am working on newer camera blobs (which should be included in the next build hopefully), got newer Adreno blobs... I think that's a different ROM. Got moved by a moderator and I've messaged him for clarifications.

I'm not complaining, just trying to understand.. Either section is fine by me.
[ONE Android Development] FSadino:
Every ROM avaliable for OPO is based on CM or AOSP, they are the Jedi Masters :)

Your work is based on [MENTION=4812336]updateing[/MENTION] ORIGINAL work and his ORIGINAL commits. You have substratum and substratum his a ORIGINAL project made by others.

You say you are working on new blobs, and if is not modified ORIGINAL blobs, you can say that is your ORIGINAL work.

In my opinion, this ROM (and this is only my opinion), doesn't belong to ORIGINAL development beside you are doing a very great work.
[ONE Android Development] freshgiammi:
That means I can have these features, but to be in Original I must have something developed by me or something that's unique to my ROM and that no one else has, right? I get that now. My mistake!
[ONE Android Development] crisis_trustee:
Dear freshgiammi,

How often are you going to update your build?

Thank you in advance!
[ONE Android Development] freshgiammi:
When I'll have time, and when they'll be needed. An AOSP ROM Doesn't need many updates. Right now the mission is to fix everything, and when that'll be done, we'll have just mantainement updates.
[ONE Android Development] Rehank:
I did clean flash its still comes up
[ONE Android Development] HamsterHam:
Anyone tried suhide with this?
[ONE Android Development] mp3deviant721:
Did you verify its not your wallpaper?
[ONE Android Development] freshgiammi:
With the latest kernel? It's fixed for my private testers. Check the kernel date in Settings -> About, it should be 30 Jan.
[ONE Android Development] fabio.pagliuca:
No I'm sorry, not latest kernel, I would like to try it though
[ONE Android Development] rdhameja:
Hello everyone.

I'm new to this ROM and absolutely loving the fluidity so far. However, I'm facing a major problem.

When I initiate a call or someone calls me, I don't hear anything from the earpiece. If I switch to loudspeaker, then I can hear the other person and also on the earphones. But no matter what, I absolutely can't hear anything from the earpiece.

Is there anything missing?

I'm on the latest build (just migrated to this ROM today on 2nd Feb). Please help fellas!
[ONE Android Development] freshgiammi:
I have a build which *should* hopefully boot on F2FS. I need you guys to try it out, as I still can't switch.

Are you still available to test?
[ONE Android Development] :
I am up and ready for testing.
[ONE Android Development] freshgiammi:
Cool, thanks. Build is here.

https://www.androidfilehost.com/?fid=745425885120705094
[ONE Android Development] :
Give me a list of things that I have to test, first being boot
[ONE Android Development] freshgiammi:
If it does boot, check with this https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=it that partitions are recognized as F2FS. Then, try to load the video at the bottom of the page and tell me if it crashes and reboot.

http://webmfiles.org/demo-files/
[ONE Android Development] :
It boots fine and webm works fine but sadly f2fs partitions are read as exr4
[ONE Android Development] freshgiammi:
You got any reboot after flashing? If yes, please send me a last_kmsg

If not, reboot your device and send me a dmesg. But take it after the phone has completely loaded.
[ONE Android Development] :
No reboot after flash
[ONE Android Development] freshgiammi:
Yeah, it looks like the kernel detects your partition as EXT4. I'm wondering if they're actually not formatted to F2FS.. Could you format them and test again? Also, I've been informed that versions higher than TWRP 2.8.6.0 have issues formatting to F2FS, but I can't confirm.
[ONE Android Development] :
Holy ****, u r right. Sorry . I confirm twrp 3.0.2 didn't converted right. Sadly I don't have a computer or otg cable for backing up, so I can't convert. Sorry for wasting time, hope you don't mind.

btw charging is slow
[ONE Android Development] freshgiammi:
No problem. If someone else on F2FS could test, I'd be happy.

As for Charging, that will probably need a cycle of battery to see if it's working. My phone shows it's charging at 1900mA, so it should be fine. If the issue persist, then it will probably be something between battery/cable/plug.

It should take around 1.30h to 0-100%.
[ONE Android Development] rdhameja:
Fellas,

Can someone please suggest a workaround for this? :( Just to be informed, I didn't install any sound mods so far.
[ONE Android Development] freshgiammi:
Never had similar issues, or reports. Try and clean flash again, there are no modifications to the earpiece part.
[ONE Android Development] rdhameja:
Not sure what's wrong. Just did a clean flash but the issue persists. Read a few online forums that discussed similar issue and tried (a not so technical workaround) blowing/sucking air through the earpiece but to no good. Tried slightly pushing near the earpiece as suggested and the screen got a crack (cursing myself for doing it).

I came from Darkobas MM rom and was so glad to see this almost stock android in this one. But I don't know what to do now. If it helps, I'm using Open Gapps nano.
[ONE Android Development] freshgiammi:
Try other roms and see if the issue is present there, too. I have no changes here regarding to audo stuff, beside a higher volume on the earpiece. But that's been bundled with almost all roms since M or L, probably.
[ONE Android Development] rdhameja:
Sure. I'll check out another ROM and report back. Any recommendations for another ROM, NitrogenOS/Tuga? Really wanted to keep this one though.
[ONE Android Development] freshgiammi:
There's another AOSP rom you could try. Similar to mine.

Otherwise it depends on what you like. If you want Sultan's Camera HAL, NitrogenOS is the only one that comes with it.

Haven't tried custom roms myself, i've always been on AOSP based ones.
[ONE Android Development] rdhameja:
Thanks dude. I'll probably go to NOS. Sultan's HAL is too good to avoid. Will come back on this one surely after the next release. Which brings up, when do you plan the next release? And thanks again for all the help
[ONE Android Development] crisis_trustee:
Good AOSP build!
[ONE Android Development] Kaar3l:
I tested this F2FS build. After flashing it stays on 1+ logo and no booting. :( So I think it doesn't like the F2FS userdata partition, because the normal build that I tested did exactly the same.

Partitions setup:

/system: ext4

/cache: ext4

/data: f2fs
[ONE Android Development] shubham1120:
The build is not booting. It gets stuck on the 1+ logo:crying:

/system: EXT4

/data and /cache: F2FS.

Waiting for another build:D. Take your time we know you'll get it working soon:cool:
[ONE Android Development] freshgiammi:
Next few days, probably.

Have you guys formatted to F2FS with TWRP 3.0.2.0? It looks like that version of TRWP has issues formatting in F2FS.

I've managed to get it working with these steps:

1. Install TWRP 2.8.6.0 and format /data and /cache to F2FS, also clean your /system partition (Beware, this will clean all your /data partition)

2. Install TWRP 3.0.2.0, push the ROM via usb and flash it.

3. Boot and et-voilà, you're on F2FS.

If you formatted on 2.8.6.0 tho, please give me the output of "adb shell mount".

EDIT: Also, in case you try again.. please send me a dmesg and a last_kmsg (the latter only if you get a reboot), ADB should be working even if data doesn't get mounted. That way I can check what's wrong
[ONE Android Development] shubham1120:
Yes I did format on 3.0.2.0 recovery. But I thought it was formatted correctly. Because I saw on the app(that you gave the link a few posts back), it showed F2FS.

Trying to format using 2.8.6.0 and will report back.

Appreciate your efforts man.

EDIT: Holy sh*t what do you know!!! It booted. Many thanks mannnn
[ONE Android Development] freshgiammi:
Kool, thanks for testing! ;)

It booted by formatting with 2.8.6.0 or it did work with 3.0.2.0?
[ONE Android Development] shubham1120:
It booted by formatting with 2.8.6.0. :):)

Thanks for your your time and effort.
[ONE Android Development] devilsshadow:
Does aosp have any kind of adaptive display function? I know there's a "night light" feature on pixel phones. Is that present in nougat aosp builds? Or is it a pixel specific feature?
[ONE Android Development] simmer14:
no option of advance reboot in dev settings..
[ONE Android Development] myshakugan:
Yes, it's present.
[ONE Android Development] arfasyrf:
Reverting back to this rom after a week using aex. The boot.img provided fix the issues with google fit. No more reboot. The video played perfectly too, no reboot at all. Thanks!
[ONE Android Development] LI GANG:
Open the virtual navigation, hold down the location of the entity key, the other hand can not slide the screen menu , Rom disabled entity key, there is no operating kernel! Can not respond UI interaction time! ? Omni Rom can, God can modify the next kernel, or omni kernel! It is to the power of the ROM! Thank God for their efforts to pay! :good::good::good:
[ONE Android Development] freshgiammi:
Thanks to you for testing. :)

I am aware of that. AOSP doesn't bundle such feature.

Nice to know, thanks for testing! I'll bundle the fix in the next build.

"there is no operating kernel!" ?? I'm not sure I understand what you're saying. Also, i can't use OMNI's kernel since we share different sources. I'm on bacon, they're on find7op.

As for the navbar issue, I am aware of that but there are major issues that need debugging right now.

The next build is pretty much ready. There are two issues however (camera crashing if zooming when recording/ Torch QS not working sometimes) that I haven't been able to fix yet, but I guess it's time for a new build to be released.

ETA is today.
[ONE Android Development] Gawd:
[MENTION=4986658]freshgiammi[/MENTION] we're with you man
[ONE Android Development] lumufei:
I guess he means when i touch hw key then i can't scroll screen .
[ONE Android Development] freshgiammi:
There's a new build out! Get your recoveries ready and flash AOSPlusone_bacon_050217! Link here or on #1.

This build is pretty consistent with changes. A lot of work was put into it. (It works even on F2FS!) You can check the changelog here.

CHANGELOG

[B][B]ROM[/B]: enabled F2FS support[/B]
ROM: Removed leftovers from Camera2
ROM: Re-enabled textiles check (Textiles are not globally allowed anymore)
[B]ROM: Enabled backuptool (thanks to [MENTION=1199844]mandaman2k[/MENTION])
ROM: Fixed ringtone and notifications not being set (thanks to [MENTION=256559]medic[/MENTION])[/B]
ROM: Fixed qti.tetherservice crashing at startup
[B]ROM: Merged some security patches on hardware/qcom/media-caf[/B]

[B]Kernel: Fixed fast-charging not working for some users[/B]
Kernel: Fixed MPDecision not turning off cores 2 and 3
[B]Kernel: Restored CONFIG_MACH_OPPO;.[/B] (This will probably make kernel more stable,
but can cause instabilities. Please report any reboots.)
[B]Kernel: Fixed NULLPointer (kernel panic) when watching WEBM videos or using Google Fit.[/B]
Kernel: Merged the latest patches from LOS

[B]Snap: Fixed crash when resuming a video paused during recording[/B]
Snap/CameraHAL: Merged lastest patches from Sultanxda.

There are still a few bugs left regarding the stagefright hardening that are being issued:

Torch QS not behaving correctly

Cameraserver crashing when zooming while recording

But beside that, everything is rock steady.

There's a few people I need to thank.

[MENTION=5267387]Evolitist[/MENTION] for giving me access to his build server, greatly improving build time and thus allowing an easier and faster development

[MENTION=256559]medic[/MENTION] for spotting out the ringtone/notification sounds issue and helping me with F2FS

[MENTION=1199844]mandaman2k[/MENTION] for bringing up Backuptools (Yes, you don't need to re-flash gapps anymore)

Everyone else who helped me debugging or testing changes!

(I also changed my hosting site, since BasketBuild was constantly giving me issues. Everything is now hosted on AFH)
[ONE Android Development] LucentBirch:
I guess I'm wondering -- what is f2fs offering this phone over ext4? I used to use f2fs on my 1st gen Nexus 7 to improve the speed -- is the impact significant on here? Is it worth it?
[ONE Android Development] Spider-Vice:
Weird, on the previous build I could not use the Torch QS at all, but it seems to work on this one.
[ONE Android Development] lumufei:
Can you add nav bar on camera UI ? I means always display nav bar |･ω･｀)
[ONE Android Development] myshakugan:
Crash report:

Bug: Stock SnapCamera crashes when you enable power shutter.

Logs: Attached.
[ONE Android Development] freshgiammi:
Yeah on older devices it has a noticeable impact.. however, since I've switched to F2FS, I've noticed it being just a bit faster. Faster might not even be the right word, but it fixed the micro-stuttering issue I've been having since when my /data partition was full. I'm on 12gb left and i'm running without lags now. Also, transfer speed via USB looks like it's greatly improved, as expected from F2FS.

TL;DR: Not a change you would see in daily-use scenarios, but you might switch now to be ready for future needs.

This bug is pretty tricky: Sometimes the HAL gets loaded before /dev/video1 is ready, not being able to read the flashlight info. Most of the time a reboot fixes this, but it doesn't seem to have something that's triggering it. Pretty random and hard to track down.

I'll check again, but last time i remember Snap having weird glitches with the nabber on.

And that, ladies and gentlemen, is how a proper crash report is made.

Thanks for being accurate, I've committed a fix and it should be good in the next build.
[ONE Android Development] Gawd:
Good job

Absolutely!
[ONE Android Development] LucentBirch:
Okay, how do I get a log as specific as the one above? I just flashed the lastest version and didn't flash gapps (didn't I read "...bringing up Backuptools (Yes, you don't need to re-flash gapps anymore)" -- that mean we don't need to flash gapps?), but play services was missing and all my google apps crashed and wouldn't open upon reboot. I reflashed the latest along with gapps, and then all the google apps start crashing upon opening. Uninstall/re-install -- they work again. Everything except google fit. The app opens, and then the whole phone freezes and then reboots. I used "adb logcat" and then opened Fit again, and I attached what I believe to be the moment the app opened (right?). Is that the correct way to do it?
[ONE Android Development] freshgiammi:
I believe you need to flash GApps the first time you flash a build with Backuptools. Otherwise it won't be able to backup them. After the first time, you won't need to flash them anymore.

As for Google Fit that's weird, I've fixed it.. Try cleaning you app data.

Also, if you get a reboot, it's better to provide me with a last_kmsg as it's where the error probably is. The path is /proc/last_kmsg (You can pull it with adb)

Logcats are better if you get an app crashing or other issues, because reboots are usually kernel fault.
[ONE Android Development] LucentBirch:
Ohhh gotcha. I did clear the app data -- it still reboots my phone.
[ONE Android Development] freshgiammi:
Weird. Attach me a last_kmsg
[ONE Android Development] LucentBirch:
For some reason, I'm getting "Access is Denied" on ADB now...ugh
[ONE Android Development] freshgiammi:
Disconnect your phone, then reconnect and do

adb root && adb pull /proc/last_kmsg last_kmsg.txt
[ONE Android Development] LucentBirch:
Okay, that did something, but I can't find the file anywhere, haha.
[ONE Android Development] Gawd:
Just giving a heads up, you can use Syslog from the Play store to get last_kmsg
[ONE Android Development] freshgiammi:
haha it's probably where you were with the terminal. You can also do /path/to/where/you/like/last_kmsg.txt

+1, did not know that. Thanks!