yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Ashu7397:
I had this same issue. Its not rom related.

I think its a magisk adblock module or some Xposed module which causes this issue. I don't remember what it was exactly, but probably some magisk module. Try disabling modules until you find the rogue one. I completely removed magisk and reinstalled again to make this issue disappear.
[ONE Original Android Development] markitosd:
You can just use Root Explorer and search por LatinIME in /system/app and delete it. (I guess it was in that folder, I'm not sure. It can also be at /system/priv-app)
[ONE Original Android Development] tb79:
That works :good:
[ONE Original Android Development] avaholic:
Phone has no dial tone

Anyone else having issues with the phone dialer not making or receiving calls? I have tried several other dialer apps as well as other radio firmwares. I hear nothing in the earpiece and no one can hear me on the other end either.
[ONE Original Android Development] giaur:
No problems for me:
[ONE Original Android Development] Gawd:
I don't know why but one of Oreo's most anticipated features' isn't working (for me). I'm talking about the contextually aware text selection dialog.

Any thoughts?
[ONE Original Android Development] sk coolstar:
face unlock is unlocking my phone even when my eyes are closed
[ONE Original Android Development] uudruid74:
The title says "Phone has no dial tone". Since when did cell phones use a dial tone? WTF
[ONE Original Android Development] avaholic:
Thanks for the helpful post! Gracious.
[ONE Original Android Development] uudruid74:
First, the ROM author didn't write Face Unlock.

Second, how is this a problem? If it works with someone else's face, discuss it with Google. If it works with your eyes closed, so much the better. I don't suddenly fail to recognize people because they close their eyes, so why should your phone? Why would you even post this?
[ONE Original Android Development] sk coolstar:
i was just helping developer
[ONE Original Android Development] uudruid74:
Start at the beginning. Is it connecting to the network? Swapping out dialers is pointless. Start with the #*#*4636*#*# and see what your signals look like, make sure your IMEI is still there and hasn't been clobbered, etc. Start with the SIM and your signals, not the dialer app.

And cell phones don't actually use dial tones nor DTMF. The tones you hear when dialing numbers are just for your own benefit, totally useless, and that's not the "dial tone" anyway.
[ONE Original Android Development] avaholic:
I understand that cell phones are not analog devices and do have dial tone. I think **MOST** people knew what I meant...

The phone app works on other ROMs with no issues. Resurrection Remix nougat and jhalayashraj's [ROM][8.1.0_r4][OMS] LineageOS-15.1 for instance. I've re-flashed this AOSP several times for good measure and the phone app just does not work, period.

ATM, I'm back to LOS 15.1 because I actually need my phone to make and receive calls. That LOS works but the camera is buggy as h*ll and the phone blasts my eardrum no matter how the volume is set. It's like its always at max volume. I have say 'hang on' to turn the dang thing down before I put it up to my ear. I was hoping to get a clean AOSP experience that I can then customize to my liking.
[ONE Original Android Development] uudruid74:
how is this helping?
[ONE Original Android Development] sk coolstar:
what problem do you have..!! i kept for developer so it is none of ur business.!!
[ONE Original Android Development] uudruid74:
Yes, this does appear to be broken on this ROM. I'm not sure why. I tested the same way on this ROM and on a 3T running latest Beta OOS and the same exact input works as expected on OOS.
[ONE Original Android Development] Timmmmaaahh!:
Damn, that means your retinal scanner is malfunctioning. Install the Eye Scanner Lock Screen module to fix it!
[ONE Original Android Development] sconebranch:
Many appear to be having this issue. Try using the speakerphone or a bluetooth device to pair with your phone. That works for me, although the handset speaker and microphone do not.
[ONE Original Android Development] sk coolstar:
thanks bro
[ONE Original Android Development] avaholic:
AHH! Thanks for the confirmation. I thought I was going crazy!

That's a bit disappointing. This was really one of the more fluid ROMs I've tried as of late. I guess I'll wait and see if the dev can get it worked out.

My 'phone' has got to be able to 'phone.' nowutimean? :laugh:
[ONE Original Android Development] JaY_III:
It does for me. However it seems to have difficulty exiting charge only mode for some reason.

Goto dev options and set USB to MTP and AA works perfectly
[ONE Original Android Development] truekasun:
I'm using this rom from the release date of last stable release to today as a daily driver and I'm able to make calls. Before flash this rom, I've flashed the stock OS and then wiped system,data and other partitions except the internal storage. Then I've flashed the rom and it's working perfectly so far.

I use Google dialer (if you disable the default phone app, you won't see the in-call screen despite what dialer you are using)

All the default applications comes with Nexus 5X has been installed at the first boot. Everything's pretty cool. I don't know why some devices have such an issue and others don't.
[ONE Original Android Development] avaholic:
When you say stock OS, are you referring to CyMod 13?

I had been using Resurrection Remix for so long and it was working perfectly. I was just getting anxious about trying/using Oreo and jumped the gun I guess. When I flash any NEW ROM, I always wipe System, Data, Dalvik, and Cache so my phone should be as clean as possible. before trying a new ROM.

Isn't the dialer included in this AOSP build the google dialer?

Thanks!
[ONE Original Android Development] ixdinfinity:
Ever since 4.4 KitKat my mic doesn't work if I don't change the following:

I've used adb to push it, but I'm not exactly sure what the above does. I don't use root anymore and it's been working in two other 8.1 roms.

However in this one it restarts my phone during boot and put it back in TWRP. I've tried with and without Gapps, I've done clean installs, tried wipe cache/dalvik after pushing the edited files but nothings works.

I would provide logcat but not exactly sure how and just wanted to throw this out here if anyone got a solution?

Edit: To clarify, if I don't change the above my mic only works when put in speaker and not during "regular" calls.
[ONE Original Android Development] truekasun:
I meant the Oxygen OS by stock. I've came through various roms previously so I needed a clean start for this rom.

As per my experience, sometimes cleaning all partitions doesn't make the phone clean but stock firmware has some unaccessible (on the recovery) partitions updating. I may be wrong but I've similar experiences on Samsung, Nexus and Nexus, so Everytime I need a clean start I flash the stock os and then clear the system, data and cache etc.

AOSP dialer is similar to the Google dialer at the first glance but but for me some features such as long press actions (like Apple's 3D touch) is working with the Google dialer. N I like the Nexus experience very much. The Google messenger has notification that can Mark as read feature included. Those are really small differences but it comes handy when we use the phone day to day.
[ONE Original Android Development] sconebranch:
When I tried to use Google Dialer I was told that the device wasn't compatible with GDialer, and flashing the Dialer Framework didn't fix that. Can anyone else confirm they're using Google Dialer successfully?

I went straight from Slim7 to this OS and am experiencing this problem. I had previously flashed a firmware update dating to 10-15-2015, which I thought was the last CM13 firmware update.
[ONE Original Android Development] krikz:
Yes! I'm here too
[ONE Original Android Development] mcflurryXD:
I'm running this on the One Plus One, flashed gapps and magisk for root, and a few times per hour when I'm typing (using GBoard) the system bugs out and I have to reboot to fix it. Anyone else with this problem?

Edit: I have traced this issue to f.lux. I run it with root privileges and it doesn't seem to play well with Oreo. I have the device rooted with Magisk and I have not had an issue since removing f.lux.
[ONE Original Android Development] truekasun:
I use the attached version with no device incompatible message. No framework needed.

Use this link (Attachments doesn't work)

http://www.droidbin.com/p1c697q6ej18c0153s1hfj1mm3dnm3
[ONE Original Android Development] tb79:
I came from slim7 too and all fine here.
[ONE Original Android Development] Rui31:
Just in case: does it happen only when your mobile is plugged in for charging?

This is what happened to me last week. The keyboard (AOSP or GBoard) went crazy and many key were pressed at the same time.

When the device was unplugged, all worked nicely.

It was caused by a charger I have borrowed. Going back to my usual charger fixed that.

Searching the web I have seen that some other people have also met that.
[ONE Original Android Development] uudruid74:
If I remember, it means one of your mics used for echo cancellation or beam forming or some such nonsense has died and that change turns off the feature so you now have a single (but working) mic. Seems to be common on older OnePlus ones. People used to get it all the time. A real "fix" means replacing the dead mic.
[ONE Original Android Development] karantGoldstein:
Damn wasn't it $5 and everything basically unltd? Mine is cheaper than the one you now said, I get 20 GB 4G each month+carry forward from last month, 100 SMS per day(so 3000 per month) and unltd national calling for ~$7
[ONE Original Android Development] sconebranch:
I had similar issues with GBoard on Slim7. Memory footprint for GBoard is yuuuge - 100+ MB.

I switched to SwiftKey and have no regrets. Memory footprint is about half. You can go much smaller than that, but you lose predictive typing and swiping.
[ONE Original Android Development] ixdinfinity:
Thanks for the answer!

I'm a complete novice when it comes to Android file-systems but it seems as "/system/etc/audio_platform_info.xml" was removed in Oreo, or at least moved from /system/etc.

I'm pretty sure it's the thing that caused the bootloop when pushing that file, so nothing ROM related (and I hope I don't go off-topic here). But do you know what the specific change does?

Would it be necessary or can "ro.qc.sdk.audio.fluencetype=none" work by itself to fix the mic issue? I've tried searching but can't find anything related to 8.0.
[ONE Original Android Development] sconebranch:
I tried this already and it didn't fix the mic issue.
[ONE Original Android Development] Niyaven:
I flashed the ROM 20180123 yesterday, and also have call issues. Everything's perfect on my side, but on the other person has a terrible echo when speaking. It's like the wrong mic is used.

However, if we call over Whatsapp or Discord, everything's fine. No echo. So everything seems okay the hardware.

I tried switching to other dialer applications, without success. Any idea?
[ONE Original Android Development] sconebranch:
If that's your problem, then try making the edits in #2968. I think that'll fix it. There's also a Magisk module ("bacon-mic-fix") that does the same thing if that's easier for you.
[ONE Original Android Development] ixdinfinity:
I can confirm that "ro.qc.sdk.audio.fluencetype=fluence" changed to "ro.qc.sdk.audio.fluencetype=none" in build.prop at least worked for me :)
[ONE Original Android Development] mcflurryXD:
This is about the low mic volume issue: I was messing with it yesterday and this seemed to work for me, or so I've been told by the people I called to test it. Although I'm having other issues with the rom.

http://moodyrepublic.com/oneplus-one-mic-fix/
[ONE Original Android Development] sconebranch:
There are two mic issues going around. There's the low mic problem caused by bad noise cancellation that has been a problem with the OnePlus One for ages now that's corrected by the build.prop and audio path edits, and then there's "no handset mic, no handset speaker" problem that I've only ever seen in connection with this ROM.

Which problem did you have and fix?, as you've managed to quote my two posts discussing the separate problems

Flashing OxygenOS now as a prelude to flashing this rom to see if it fixes the "no handset mic, no handset speaker" problem.
[ONE Original Android Development] sconebranch:
And it does not, but flashing Oxygen did manage to blow away my data/media folder. I expected this sort of thing and moved a nandroid and my Titanium Backup folder off the phone before flashing.
[ONE Original Android Development] avaholic:
Anxiously awaiting your results because I suffered with the "no handset mic, no handset speaker" problem on this ROM as well... I'm currently using Lineage 15 but the call quality stinks.

Is this the Oxygen OS to which you refer?

https://forums.oneplus.net/threads/oxygenos-2-1-4-for-the-oneplus-one.425544/

Man that was quick! ^^^

Well Darn. I was hoping it would work.
[ONE Original Android Development] sconebranch:
Can't install this app. Thanks for trying.

---------- Post added at 05:06 AM ---------- Previous post was at 05:01 AM ----------

If you read the install instructions, they tell you not to flash 2.1.4 with TWRP. There's a 2.1.4 flashable with TWRP floating around, but I wanted to replicate truekasun's scenario exactly, so I started by flashing OxygenOS 1.0.3 (also available from downloads.oneplus.net), and then using OnePlus Recovery to flash OO 2.1.4. Then I wiped system/data/cache and flashed the stable build of AOSP Oreo. Same problem with "no handset mic, no handset speaker."

I reverted to my nandroid at this point, because I didn't feel like setting everything up again.
[ONE Original Android Development] se7enlyn:
deleted
[ONE Original Android Development] balavigneshs:
+1
[ONE Original Android Development] uudruid74:
honestly, I've never had the issue myself so I haven't dug very deeply into that. I do know that often the problem can be as simple as dirt in the mic holes, or causing the headphone Jack to appear as if something is plugged in. I'm guessing the acdb_id is the sound device to use. Maybe Oreo's kernel uses a different numbering.

---------- Post added at 10:46 AM ---------- Previous post was at 10:38 AM ----------

I think Fabulous-Oreo/device_oneplus_bacon would be the new stuff.

[MENTION=5834335]Agent_fabulous[/MENTION]

your tree calls device/oppo from it's makefile. Is this from CM? Can you give a link to the exact source you used?

thanks!

edit: One more question. Has anything else been changed from pure AOSP? Or are all changes in the device tree? I'm particularly wondering how Face Unlock is so fast in this ROM. It's just like the version from OnePlus, but without the Tasker hack.
[ONE Original Android Development] sconebranch:
After installation, Titanium Backup reports that my device has a new Android ID and asks me if I want to replace it with the old ID. This is pretty standard. However, TB can't seem to actually restore the old ID, and it prompts me every time I launch.

Moreover, "adb settings get secure android_id" tells me that my device still has its old ID, and Google insists on treating this like a new device with its own backup.

Can anyone else confirm? Anyone find a resolution for this?
[ONE Original Android Development] Xcaliber219:
OKAY PEOPLE, PLEASE USE YOUR TWO BEAUTIFUL EYES AND READ BACK A LITTLE BEFORE ASKING ANY QUESTIONS!

You'll most likely find all the answers you need!

Stop spamming the comments with the same repetitive questions. It disrupts the flow of the forum.

And for the people who still don't give a **** about reading the posts, here's a little treat for you :

Camera? : Doesn't work/ No proper working HAL has been installed yet

Stability? : The ROM is kind of stable but you might experience some reboots if you've installed the wrong GApps package.

Does it lag? : Hell yes, it does. It's in beta and switching from one app to another, the ROM does exhibit some lag and sluggishness.

Custom kernels? : Avoid using any custom kernel for now. The system already has enough problems of it's own.

Which GApps? :

Pico :

http://downloadmirror.co/W95/open_gapps-arm-8.0-pico-20170902-UNOFFICIAL.zip

Nano :

http://downloadmirror.co/W96/open_gapps-arm-8.0-nano-20170902-UNOFFICIAL.zip

Micro :

http://downloadmirror.co/W94/open_gapps-arm-8.0-micro-20170902-UNOFFICIAL.zip

Is the dev still working on this ROM ? : Yes.

Is flashlight a part of camera? : Yes. It needs the necessary camera permissions to work. It is integrated with camera on a hardware level.

VoLTE for OPO? : You can forget that. It totally depends on Oneplus. They are the only ones capable of pushing out an update which can enable VoLTE in OPO. But that would've happened by now if it were to happen. So no "volte pl0x" PLEASE!

Does God exist? : Maybe.

I hope I answered all your questions.

New and LOGICAL, GENUINE questions will be entertained. Baseless and already answered questions should not be answered again. Let the person do some reading and find the answers on his/er own.

I hope we can have a better discussion from now on. :)
[ONE Original Android Development] Timmmmaaahh!:
You're too kind *blush*

Thank you for that enlightening post. Even though I do read and search, it's nice to see it all summarized. I have one question that doesn't seem to have been asked before (may the flying spaghetti monster be merciful if I missed it).

What would be recommended for Oreo on OPO, Ext4 or F2FS?

The reason I'm asking is because I've switched to F2FS - where possible - ages ago but in Franco's interview on the portal it became clear to me that it doesn't really have any benefits. Switch back to Ext4 before giving this baby a test run, better stick with F2FS or does it just not matter?

Sizzled with Bacon ?
[ONE Original Android Development] Xcaliber219:
Some people prefer F2FS and some people prefer EXT4. But there is a reason why EXT4 was chosen as the more reliable filesystem for Android.

F2FS can give you short-term boosts in performance but it kind of loses the speed overtime, Plus ROMs flashed on F2FS filesystem are prone to crashes, noticeable bugs and corupt data's. But for some phones F2FS didn't even give the initial boost in performance like it was supposed to. In fact, it reduced the overall performance by atleast 15-20%.

EXT4 on the other hand is more stable and reliable.

Android was made around the EXT4 initially and that should be enough reason to opt for EXT4.

In addition to that, EXT4 gives you long time stable performance and is less prone to bugs and crashes.

EXT4 also has way better write speeds compared to F2FS which has almost 20% less write speeds compared to EXT4.

Lastly, OnePlus used F2FS filesystem in OP3 and it caused a lot of problems for them, so they switched back to traditional EXT4 filesystem on OP5.

That should clarify some of your doubts.

I hope I was of help to you! :)
[ONE Original Android Development] Link_of_Hyrule:
Also, F2FS makes TWRP boot up really really slow.
[ONE Original Android Development] bdwilk:
[MENTION=4841620]Timmmmaaahh[/MENTION] I agree with [MENTION=8372649]Xcaliber219[/MENTION]. In my own opinion most of the legit bug reports start off with "so I'm running f2fs....." Just saying, the goods do not outweigh the bads when talking about f2fs. Like you said about Franco, even the big name devs say the average user will never know the difference between the two, until there's an issue.
[ONE Original Android Development] pankspoo:
I am using f2fs from the day we got it no problem at all its more innovative to use new things than to stick with old things which is stable enough
[ONE Original Android Development] ilfrick:
Hi all. Quick question: what fw are you using? I am in Italy with Vodafone, 4g coverage, but with current fw (last cos official) I only get 3g and poor connectivity.

Thanks!
[ONE Original Android Development] Gawd:
Would you people call me late if I join the Oreo bandwagon now?
[ONE Original Android Development] Timmmmaaahh!:
[MENTION=8372649]Xcaliber219[/MENTION] [MENTION=3045671]Link_of_Hyrule[/MENTION] [MENTION=7478074]bdwilk[/MENTION] That was most clarifying indeed! I should've known Samsung was up to no good ^_^ [MENTION=5326976]pankspoo[/MENTION] You should read the interview with Francisco Franco on the portal, he compelling arguments on F2FS vs. Ext4 (spoiler: Ext4 wins). Francisco is a well known and respected kernel developer, I have no reason to doubt him. I'll be converting back my partitions to Ext4 when I got the time to flash some O flavour (probably this weekend) and hop in on the testing. Thanks!

And to [MENTION=5834335]Agent_fabulous[/MENTION]: you're mega-awesome for doing this!
[ONE Original Android Development] Xcaliber219:
I've used both and here I am, using EXT4.

Preference is what counts. For me personally EXT4 outweighs the benefits given by F2FS.

You're lucky to not have come across any problems, but majority says otherwise.

I'm a very extensive user and F2FS never worked for me that well. EXT4 is innovative and more reliable so i'll stick to that :)

Cheers!

---------- Post added at 08:14 AM ---------- Previous post was at 08:13 AM ----------

Glad I could help you!

EXT4 is the way to go.

:)
[ONE Original Android Development] pankspoo:
O ya i read that but i don't think all the things he told are correct he also stated that 99% of ROM developers are doing what they don't know just copying codes etc...... Again he is against of sdcardfs and i have already tested that one too and not faced any issue. All the things have there own pro and cons but if we just avoid them how can we get innovative things for Android development.

And every one has there own points of view we can't neglect them.
[ONE Original Android Development] Mr.Ak:
Yes,you should have joined earlier.I guess you were busy with idprophecy's lineage os. *crai*

---------- Post added at 10:30 AM ---------- Previous post was at 10:29 AM ----------

I'm using idprophecy's modified firmware and it works good so far.
[ONE Original Android Development] matt4321:
Tidied up a bit. Have a good day all :D

Matt

Senior Moderator
[ONE Original Android Development] ashutoshmn:
Is it c6_11_00006 you talking about? Does proximity sensor work fine with this?
[ONE Original Android Development] Inferillum:
0.1.c.1.11-00006
[ONE Original Android Development] Salamandar3500:
Tried to flash without wiping Data… Lots of app crashes and no GSM. Sounds normal.

Wiped Data, installed Supersu, seems to work like a charm ! Did not lose my files/music/downloads.

But… I can't start PlayStore. Stuck on "checking informations" (like if I wanted to create an account).
[ONE Original Android Development] Mr.Ak:
Which gapps you used?

---------- Post added at 02:52 PM ---------- Previous post was at 02:51 PM ----------

Just what [MENTION=7871457]Inferillum[/MENTION] said and proximity sensor works fine.
[ONE Original Android Development] A$h!$h:
try lighting kernel v34r .. mine oreo booted as sec rom
[ONE Original Android Development] Timmmmaaahh!:
What! No OMS support? Worthless! Lol, kidding of course. This runs pretty stable on my end! I did throw about 25 apps at it and it's gotten a bit laggy. Unofficial pico Gapps flashed after unmount/mount system. Magisk 14 flashed without any problems. Got strange SafetyNet results though...

Restoring Snapchat with TiBu reboots every time, I'll try updating this post with a log on that..

Edit: Failed to capture anything. Reboots were getting more frequent and it was getting late. Had to revert to a backup for now.

Sizzled with Bacon ?
[ONE Original Android Development] #utkarsh:
One more question, when will official OpenGApps be available for Oreo, any idea? (I hope that's not a repeated ques)