yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Hello there. I did unfreeze Eleven app (it was frozen, since I don't use it). And yes, there are problems with the flack, ogg and alac files. No settings at all, so frozing it again.

Hope this kind of answer is usable.

Regards.
[OnePlus 3 & 3T Cross Device Development] tfae:
I probably didn't understood that you were referring to the MMS APN. Sorry.

I have some improvements.

Here's what I've done right now on RR (based on LOS 15.1 so I didn't bother to change to LOS):

Applied the apns-config.xml and rebooted into the system

Checked the Network name and it was NOS.

Checked the APNs and they were the same 2 as always.

Manually deleted all the APNs and rebooted. After the reboot there were still no APNs configured.

On the APN's menu selected "Reset to Default". 4 APNs appeared and the Network name is now WTF!

MMS is now working!

But the hotspot still doesn't.

These are the APNs: View attachment new_apns.zip
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Hi,

sorry, I misunderstood the first time.

I just tried on this example ogg file: http://file-examples.com/index.php/sample-audio-files/sample-ogg-download/

I can play it in the browser (Chrome), but not in Eleven / Music.
[OnePlus 3 & 3T Cross Device Development] :
I'm still completely clueless. If the same configuration, which has resulted in working hotspot and broken mms yesterday, results in broken hotspot and working mms today, I have no idea to offer - in deed I don't understand this at all. I have no idea what to do, to look for or whatever. I'm still thinking of it, but atm the complete scenario has stopped making any sense to me.
[OnePlus 3 & 3T Cross Device Development] tfae:
Yeah, I must be missing something too. I don't know wth I've changed in order to the Wi-Fi hotspot stop working. :confused:
[OnePlus 3 & 3T Cross Device Development] iron@ss:
Wakey! Wakey!	lineage-15.1-20180926-nightly-oneplus3-signed.zip is up. :D
[OnePlus 3 & 3T Cross Device Development] :
It could have been the firmware version: if you come from ob30 without flashing any other firmware, you have the ob30 fw installed, when coming from 5.0.5...

Maybe - crossing fingers - with 5.0.5 and the original 15.1 apns-conf.xml everything is working... ...or with the modified...
[OnePlus 3 & 3T Cross Device Development] tfae:
Even though I was using OB30, I'm using 5.0.5 FW on every Oreo ROM because it is the most recent FW version. And I've tried OB30 FW too just to be sure it wasn't FW related, with no success. :(

Now I got MMS working but no Wi-Fi Tethering. I was expecting to have at least the opposite, but hey, at least we fixed something :laugh:

I think you can submit the changes anyway to LOS, maybe with a clean flash with the new apns-conf.xml the thing starts working.

And it doesn't break anything anyway. ;)
[OnePlus 3 & 3T Cross Device Development] :
The problem is that the three additions are NOT used. Both of the apns shown in your config are UNTOUCHED. I guess the working hotspot was some timely coincidence with changing the apns-conf.xml. If I would push that change, it will never be merged.
[OnePlus 3 & 3T Cross Device Development] tfae:
It surely changed something. I had made the APN reset before exposing the issue and the APNs kept the same 2 and both problems persisted.

With the new apns-config.xml I now have 4 APNs after the APN reset and the MMS are working.
[OnePlus 3 & 3T Cross Device Development] :
But in the screenshots you've posted (15.1_APNs.zip) only the two NOS apns are shown. That's why I've stated, that not a single one of the three readded apns are shown. :confused::confused:
[OnePlus 3 & 3T Cross Device Development] tfae:
Did you check the APNs of my last post after I did the APN reset?

https://xdaforums.com/showpost.php?p=77716049&postcount=3804
[OnePlus 3 & 3T Cross Device Development] :
Ah, ok.

Can you try switching from "Optimus" to "NOS Internet", and check hotspot and mms, please?
[OnePlus 3 & 3T Cross Device Development] tfae:
Sure. I'm now testing on LOS 15.1, not on RR.

MMS is working, hotspot doesn't.

One thing I've noticed is that none of them have the "dun" type.

---------- Post added at 12:16 PM ---------- Previous post was at 11:27 AM ----------

The OGG file given as exemple on the bug ticket plays fine on Eleven on the 20180925 15.1 LOS (latest).

The track is awful though :P

I can't download the ALAC example to test.
[OnePlus 3 & 3T Cross Device Development] gruntyoldbag:
A few weeks ago my phone was hit by the "Low in-call speaker volume" -'bug'.

I think it began after I had upgraded the ROM or upgraded to OB39 firmware.

I have tried to find OB30 firmware to try to correct the problem, but I can't find it.

Today I have reset my phone to factory settings (running OB39 firmware + nightly from last night) but no luck again.

The volume is still low.

And no, the speaker it not unclean.

Any ideas what I can do about it?

Thanks!

EDIT:

Fixed by editing mixer_paths_tasha.xml in the new location ;)
[OnePlus 3 & 3T Cross Device Development] :
I was surprised when you reported dun in APN-Type, because I havn't changed anything to dun. The 14.1 apns-conf I've used as source for my editings had NO dun it it. That's why I guessed the file definitions would be "aggregated" with the carriers respons.

Now I guess, if you had dun on the first attempt with the edited apns-conf.xml had some artifacts from what you tried just before.
[OnePlus 3 & 3T Cross Device Development] tfae:
Why do you want to go from OB39 to (specifically) OB30?

OB30 is the latest OB firmware for OP3T.

OB39 is the latest OB firmware for OP3.

Now I am confused. If you didn't change anything related to "dun", how did dun appeared on the APN config when Hotspot was working? :confused:

Don't tell me that I mistakenly tested it on OOS…… LOOOOOL

I'll add the dun type to the apns-config.xml and test if it does the trick.

EDIT: BINGO!! I've added the dun type to the apns-config.xml, reseted APNs and MMS and Wi-Fi Hotspot are working!!!!
[OnePlus 3 & 3T Cross Device Development] :
The latest firmware for op3t is 5.0.5.

The latest firmware for op3 is 5.0.5.

It also seems to me, that if the file is edited (or replaced for that matter) the net settings needs to be reseted.

If you have both working, persisting reboots and dirty flashes (aka updates), would you post the apns-conf.xml, please?
[OnePlus 3 & 3T Cross Device Development] gruntyoldbag:
OB30 was more or less a guess of what firmware I had installed before I upgraded to OB39 ;)

But I have fixed it - read my edit above ;)

(I have a OnePlus3-nonT)

Thx but I fixed it - I thought we were supposed to use OB firmware - isn't that the same thing?
[OnePlus 3 & 3T Cross Device Development] :
Theoretically every oreo fw (>=ob16/ob25) should work. But if you read through the thread, older fws may have some issues. Practically the least problems occur if you use the fw, the blobs are taken from, which is currently 5.0.4. The open beta program has ended for op3/t. 5.0.5 seems to work, too. 5.0.5 and 5.0.4 are both more current the the last open neta fws (ob30/ob39).

IMPORTANT: though the version numbering is the same for both devices, it's mandatory to flash the correct model type to avoid bricking! (op3 and op3t versions of 5.0.[45] ARE DIFFERENT).
[OnePlus 3 & 3T Cross Device Development] gruntyoldbag:
Thx for the clarification!
[OnePlus 3 & 3T Cross Device Development] tfae:
That's why I've said the "latest

OB

firmware"… :P

Sure. Here you have: View attachment apns-conf.xml

I don't know if it is necessary to have the dun type on all the 3 APNs that I've edited, but idc…

I will make one final test though: I'll copy OOS apns-conf.xml APNs for WTF/NOS and check if they work on LOS. If affirmative, why not use them instead of the current ones?
[OnePlus 3 & 3T Cross Device Development] tfae:
Or if you use Magisk you can use the module I made for that so you don't have to do it every time you upgrade. ;)
[OnePlus 3 & 3T Cross Device Development] :
Because you would need to reformat oos version of the file. Also: If you remember one of my first comparisons, it had been proofed that 5.0.5 only has the exact same definitions as los has currently (don't get confused by the line breaks in oos version - it's the very same).

https://review.lineageos.org/#/c/LineageOS/android_vendor_lineage/+/230186/
[OnePlus 3 & 3T Cross Device Development] :
Lagging

Has anyone expirienced the lagging when using the no-swap boot image?
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Using nlos latest edition without clue what settings you have applied :)

The less you know, better sleep you're having.

Neither I had lag issues you're talking about.
[OnePlus 3 & 3T Cross Device Development] :
My bad. My question wasn't precise enough:

The following question is only for lineageos 15.1 users, who's devices had suffered from bad lagging until the device completely freezes. It's not for users, who never suffered from this, nor for users using custom keenel, nor for users using nlos, nor for users on any different rom then lineageos-15.1. It's only about the issue I always entilted "Lagging" when posting on it.

Does the lagging issue reappeared for users of no-swap boot image?

I just want to know if it makes sense to push the MEMCG_SWAP revert to solve https://jira.lineageos.org/browse/B....1 AND text ~ "lagging" AND Device = oneplus3 ?

I hope this time the question is clear and precise enough.
[OnePlus 3 & 3T Cross Device Development] :
NOS APNs

[MENTION=6415870]tfae[/MENTION]: would you please check this one:

https://raw.githubusercontent.com/L...3c7c0479f5e/prebuilt/common/etc/apns-conf.xml
[OnePlus 3 & 3T Cross Device Development] MagnusT:
I haven't had any problems with lag after I started using the no-swap boot image.
[OnePlus 3 & 3T Cross Device Development] Xzorg6:
I never experienced the lagging with no-swap boot image. 2 weeks uptime.
[OnePlus 3 & 3T Cross Device Development] tashimotor:
Me too. 2 weeks, no lags!
[OnePlus 3 & 3T Cross Device Development] the00guy:
I just flashed boot-no-swap, I can reproduce the lag issue fairly consistently so I will do some testing with that today. Thanks for the work, this issue has been driving me nuts lol
[OnePlus 3 & 3T Cross Device Development] :
What do you mean by "reproduce the lag issue fairly constantly"? Does it appear out of the void? Or can you intentionally reproduce it by certain steps?

I don't want to split hairs, but if it's the latter, it would be outstanding helpful, if you share those steps!
[OnePlus 3 & 3T Cross Device Development] the00guy:
It's hard to pin down exactly a specific formula, but from what I've seen, it's always happened while using certain resource intensive apps such as snapchat, pokemon go, or google maps navigation. So I intend on trying to cause this lag issue while using these apps heavily to try to induce it.
[OnePlus 3 & 3T Cross Device Development] ciarpame:
A few hours after the last time I reported here my 183+ hours uptime with the "no swap boot image", about a one week ago, I found my mobile stuck with a black screen, with the the notification led permanently lit. It was a few minutes after heavy Amazon Shopping app usage. I can guess that the black screen was related to a lagging. Anyway, I rebooted the device and, since then, my uptime is 163+ hours.

In my opinion the "no swap boot image" solved the issue in almost all cases and improved my device stability at least tenfold, so it's worth to apply this fix to LOS.

And now a couple of stupid questions, put the blame on my ignorance and my curiosity:

1. it's a bad idea to flash the latest LOS build and then your no-swap boot img? I will not to that, just want to know how the boot image is related to the rest of the ROM

2. If I'm not wrong, I see that the no-swap boot img modification was just a one line configuration value change. Is that a setting in system partition that can be changed with root permission or is it something that need to be compiled and flashed?

And now for something completely different: I read somewhere that is a bad idea to replace the default LOS dialer with the Google dialer and I never did it with LOS 15.1. Anyway the new Google dialer has been redesigned and it's nicer, in my opinion. So I'm tempted to install the Google dialer and freeze the LOS dialer. Will I just loose the ability to record conversation or to dial an emergency number in some limited network coverage scenario?

Thank you
[OnePlus 3 & 3T Cross Device Development] :
Thanx for this detailed feedback!

As long as we can't pinpoint a reproducable way to trigger this issue, everything is possible: it could be the very same issue, just triggered later, or it could be something new (we just havn't run into, because the first lagging issue doesn't allow the device lomg enough to hit tne new one).

Whatever it is, I agree that reverting the MEMCG_SWAP config is an improvement.

The boot image contains two very essetial os parts: the kernel and the rootfs. The function of the kernel should be known. The root fs has mainly two purposes: it's the basic fs layout with mount points for i.e. /system and /data, but also holds a "mini" os containing basic configurations (i.e. /init.*.rc, /default.prop) and some basic binaries needed to be present before /systen is mounted in order to boot the device.

The boot image has the kernel and a cpio archive of the root fs. These two parts are "packed" with the mkbootimage command to an image file (i.e. boot-no-swap.img).

For the no-swap bootimage I have changed two compile time kernel configs (https://github.com/nvertigo/android...5ebb99f#diff-48fd9979dd83cbe029b960983aff90e7 ).

The cleaner solution would have been using the anykernel2 template as flashable zip. While flashing anykernel2 gets the boot.img from the boot partition with dd, unpacks it, changes something (for this case only the kernel itself), repacks the chaged content and flashing it back to the boot partition.

Flashing Magisk does something similar, but doesn't exchange the kernel. Instead some init*rc files are edited and added.

Since I was to lazy to make an anykernel2 flashable zip, I've just provided the boot image with the recompiled (build time config changed) kernel: for that I just need to type "mka bootimage"... ;) lazy me... ;)

Neither my altered boot image, nor anykernel2 flashable zips (or Magisk for that matter - remember it's systemless) do anything to the system partition.

I hope this answers your second question.

For your first question: I think neither the kernel sources nor something in the rootfs has changed. So, go ahead. If you have any issues after doing so (though I dosn't expect that) just dirty flash the current rom and drop me a note. I'll update the no-swap boot image.

It's - in deed - a bad idea to replace the dialer - but it's worth a try to install gdialer and use it as default dialer.

If you flash i.e. opengapps stock the los shipped dialer gets replaced - this can lead to some trouble. But if you install gdialer from playstore it's a complete different story: the shipped dialer is still in place and you can easily switch the default dialer, and gdialer is NOT installed as previledged app (which is very important, since user apps can't do as much harm to your setup as a previleged app can do).
[OnePlus 3 & 3T Cross Device Development] BRDigung:
MindTheGapps or OpenGapps, which is recommanded?
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
I'm using OpenGapps and it's working fine...
[OnePlus 3 & 3T Cross Device Development] Fritzy62:
Just wanted to let you know that the boot-no-swap solution worked wonders here. No lag for days already.
[OnePlus 3 & 3T Cross Device Development] geogaddi47:
Whereabouts do I find this 'no swap boot image', will it be included in the main ROM if it's decided that it fixes the lag and are custom kernels affected? Thanks
[OnePlus 3 & 3T Cross Device Development] :
Thanx for the feedback.

I've pushed this to gerrit: https://review.lineageos.org/#/c/LineageOS/android_kernel_oneplus_msm8996/+/230413/

As stated in the comments of this change, I would suggest to enable the kernel's lowmemorykiller: https://github.com/nvertigo/android...mmit/29e5494d5e9bc5ccab1d7e03c2659af924e32884

Attached you find a stock los root fs with a stock los kernel with both patches applied. Unzip boot-no-swap-lmk.zip. In twrp flash the comtained boot-no-swap-lmk.img as boot image. Don't forget to reflash all boot image altering packages lile magisk, wipe cache and dalvik. Reboot to system.

Feedback appreciated!
[OnePlus 3 & 3T Cross Device Development] Fritzy62:
Flashed. Rebooting as we speak. Will keep you posted. Thanks a million for the excellent work.
[OnePlus 3 & 3T Cross Device Development] Xzorg6:
Flashed too. Thanks

But I'm not using my 3T as intensive as before, not sure to rapidly reproduce lags. I'll keep you informed.
[OnePlus 3 & 3T Cross Device Development] albundy2010:
Is the info in the OP still current on the recommended FW to use?

If not, what is the recommended FW?
[OnePlus 3 & 3T Cross Device Development] :
I'd recommend to use the fw the other blobs in the rom are taken from: OxygenOS 5.0.4.
[OnePlus 3 & 3T Cross Device Development] dimon2242:
With this wallpaper I have strange behavior

It's bug?
[OnePlus 3 & 3T Cross Device Development] vinoxflame:
what strange behavior?
[OnePlus 3 & 3T Cross Device Development] dimon2242:
Black fill when notification drawer is down with this wallpaper.
[OnePlus 3 & 3T Cross Device Development] veeroohre:
All good for me since I flashed your boot image.
[OnePlus 3 & 3T Cross Device Development] :
Lagging

Tomorrow's build wil have https://review.lineageos.org/#/c/LineageOS/android_kernel_oneplus_msm8996/+/230413/ . Which is basically a combination of https://github.com/nvertigo/android...mmit/d7a31478bdc0778a1eda773022958ab91d1386e6 and https://github.com/nvertigo/android...mmit/29e5494d5e9bc5ccab1d7e03c2659af924e32884 .

This should fix the lagging issue from https://jira.lineageos.org/browse/B....1 AND text ~ "lagging" AND Device = oneplus3 .

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Noob question : those updates are pushed to all future lineage builds and devices in general or certain device only?
[OnePlus 3 & 3T Cross Device Development] Racpu_:
If anyone wants to test the unofficial version already with these changes here it is: https://nyyu.tk/builds
[OnePlus 3 & 3T Cross Device Development] :
For the device independent projects (if not inside conditional code) changes will effect all builds. For the device dependent projects changes will only effect the device the changes are made for. Quite selfexplaining.
[OnePlus 3 & 3T Cross Device Development] SqueezyCheez:
Cool! My crashing and lagging came back after the factory reset. I just didn't test it enough before I thought it was "solved".
[OnePlus 3 & 3T Cross Device Development] :
Lagging

After which uptime the lagging reoccurs?

How many time elapses between lagging and crashing?

If it's crashing and not freezing, can you get something out of /sys/fs/pstore (first(!!!) boot after crash!)?

What build are you using?

Which bootimage are you using?

Did you grab a logcat and a dmesg while lagging?

Have you checked the resources (mainly cpu and resident memory) with top or htop while lagging?

What exactly have you done since the factory reset?

Installed any apk?

Restored any apk?

Restored with or w/o data?
[OnePlus 3 & 3T Cross Device Development] SqueezyCheez:
Hard to say what the uptime is. It's almost random. I can go for hours and not have it crash or lag. I do know that using Maps and Bluetooth seems to cause it to crash much more frequently. Also... Apps like Amazon and Pizza Hut will force close constantly until I switch from Android System WebView to Chrome in the developer options.

I haven't grabbed a log car during the crashing. The phone will either reset itself, or I'll have to force a hard reset by holding down the power button for 15 seconds. I've also checked the resources when the lagging occurs... The CPU usage spiked while RAM does not. No particular process is abnormally higher than another though.

Since the factory reset I've reinstalled all my usual apps. I'm using the 5.0.5 firmware with regular Lineage 15.1. I use the Lineage root package. Prior to the factory reset I formatted all partitions and "started from scratch" so to say. I tried the "no-swap" boot image. It didn't do anything.

I'll wait for this next LineageOS update and then start looking into the issue more and report back.
[OnePlus 3 & 3T Cross Device Development] Racpu_:
New Build: https://ftp.acc.umu.se/mirror/linea...age-15.1-20181002-nightly-oneplus3-signed.zip
[OnePlus 3 & 3T Cross Device Development] BRDigung:
I have a problem with the dual Sim.

When I call the first Sim everything is fine but when I try to call the second Sim the phone ring but I can't see the dialer and the screen is still black. When I unlock the display by my own the phone still ring but I can't see the dialer too.
[OnePlus 3 & 3T Cross Device Development] Fritzy62:
So far so very good with the zip you provided. Will flash tomorrow's build when it's there. [emoji106]
[OnePlus 3 & 3T Cross Device Development] jmadiaga:
if flashing to the latest build (2018-10-2) does this mean that i no longer need the no-swap img flash solution to the lagging issue?

if so, how should i remove or delete the no-swap img in the boot sector?

thanks.
[OnePlus 3 & 3T Cross Device Development] mk_1996:
Just dirty flash the rom
[OnePlus 3 & 3T Cross Device Development] tfae:
What's this no-swap img thing? Is it to fix lag in what? It is only for OP3 (my 3T has no lag)?

Sorry if there's already a post answering these questions, but I'm in Africa right now and Internet sucks. It's awful to search here :(
[OnePlus 3 & 3T Cross Device Development] mk_1996:
Yes. nvertigo67 made a patch for those with lag on their device. I guess it was not specific to op3(could be wrong). I also didn't face any issue and i have a op3. But the required fixes were merged by him on the latest build and everything is fine now
[OnePlus 3 & 3T Cross Device Development] the00guy:
Reporting back on the no swap image, over a week and no freezing! Thank you for all the hard work!
[OnePlus 3 & 3T Cross Device Development] Zsebibaba:
Google maps and music player bugs

I've been using LoS 15.1 since it is available, and everything was working fine until the last couple weeks. I updated it weekly without checking what the actual changes were, and i started experiencing some weird phenomena.

The first issue i noticed is related to google maps : when i try to set a route from my actual location to a given point, it does not load anything, even though the progress bar is getting filled (extremely slowly) still no result at the end. Then i reboot my phone, and it works properly again when i open the app for the first time after the reboot.

The second problem - which cannot be solved temporarily by rebooting my device - is that the music player has some bugs :

- when i unplug my earphones the music is keep going on

- the widget does not work at all, cant stop the music there, i have to stop it using the app,then i cant start the music, not even from the app, i have to shut it down and open to get it functional again

- i tried other music players, such as poweramp, and suprisingly there are similar bugs, but not the same : i cant use its module in the notification bar, the whole thing is white, the buttons are disfunctional, cant stop/switch music when my screen is locked

After unsuccesfully searching for solutions i decided to wipe my whole system, storage and everything from my phone using TWRP, and installed the oldest available LoS 15.1 version (09.04) but nothing changed so far.

Is there anybody who experienced similar problems?

Even if not, i would really appreciate if somebody sent me an older LoS 15.1 version (possibly from april or sth like that)
[OnePlus 3 & 3T Cross Device Development] jmadiaga:
got it.

thanks.
[OnePlus 3 & 3T Cross Device Development] xpissio:
So... The update for fixing lag is working, right? I'm staying on OOS for that reason. But if lag has been fixed, I can come back to Lineage. :)