yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9  Questions & Answers] Sobiiboy:
Hi I just upgraded officially my Samsung Galaxy S9 G960W One UI Major PROBLEMS is that:-

1: Whenever you open the camera app by double clicking power button and take instant snaps the camera does not stores any taken picture and simultaneously the camera app freezes and shows 'camera app failed'. Now the camera application is constantly showing this warning and freezes even though I try to open camera normally.

2: The new animations are sometimes fast and snappy just like previous ones but again I feel like these are new and not properly been tested and these animations stuck sometimes in 3rd party applications as INSTAGRAM, Whatsapp, Snap, etc. Honestly, I feel like about this One UI animations as I'm using some cheap 3rd party play store launcher.

Honestly, I want my old Samsung experience (UI) back it's because I never experienced any single problem with that one for 5 months of using this device.

Pros: 1: Experiencing one hour (approximately) improved battery life. 2: Better ram management 3: New animations feel little more snappy than the previous ones. 4: Better notification panel layout and scrolling down of apps for one hand usage.

Final verdict: One UI update desperately needs an update to fix this major camera issue.
[Samsung Galaxy S9  Questions & Answers] jamil aboudaher:
I also updated to one ui in 16 january.

Camera and animations don't have any problem, battery life isn't very good, and I have few things here and there that Samsung should fix. I hope february update will fix all bugs and make One UI more stable...

(Galaxy S9 SM-G960F/DS)
[Samsung Galaxy S9  Questions & Answers] Tel864:
Through none of the Pie betas has a camera problem like that been reported that I know of. I'm not sure your problem requires an update. Have you cleared the system cache since the uodate? That's something that's always recommended after or immediately before an uodate.
[Samsung Galaxy S9  Questions & Answers] Sobiiboy:
Yes I did cleared cachce right after the update.
[Samsung Galaxy S9  Questions & Answers] *Detection*:
Factory reset
[Samsung Galaxy S9  Questions & Answers] Sobiiboy:
Factory reset is not the solution for these problems and I didn't buy the premium product to keep doing factory resets.
[Samsung Galaxy S9  Questions & Answers] *Detection*:
Yes it is after a major OS upgrade, welcome to Android
[Samsung Galaxy S9  Questions & Answers] peachpuff:
No its not.
[Samsung Galaxy S9  Questions & Answers] jamil aboudaher:
Bro factory reset isn't the solution for everything, some people are finding even more bugs after resetting their device... These unnecessary corrupted files from the old software will likely be gone after clearing the cache.
[Xiaomi Poco F1 Questions & Answers] jag1475:
Hi All ,

so my sent MMS are not showing the pic that I've sent also I cannot click on the 3 dots

I'm running stock with Pixel icon pack

if I tap on the spot where the pic should show be I get to see the pic ,

any suggestions
[Google Pixel 3 Questions & Answers] drshitalkiran:
Hi

My pixel 3 xl is charging slowly on pixel stand after root with magisk on stock rom, Please suggest the solution
[Google Pixel 3 Questions & Answers] fury683:
Mine says charging slowly and I'm not rooted. It's been that way for quite a while.
[Google Pixel 3 Questions & Answers] theGekkoST:
Mine did this without root for a while. I ended up fast charging it for a while using the USB port, then put it back on the charger. It would then wirelessly "Charge Rapidly" again. I feel like this is something stupid with Google's insistence on having a proprietary charging stand to fast charge.
[General Accessories] jackokring:
hi

12v powered usb hub, with pocket pc charge and upto 4 device cabled network (or wifi). using smb network share of any plugged in disks, and having a directory set set asside for a print queue and for windows GDI drivers for printers which may be attatched. maybe a cat5 too. useful as a print file station, also with power cable gen of -12 and 5 for supplying disks.

a power efficient mobile office hub. MediaMobileHub.

any ideas??
[General Accessories] Rudegar:
very very few htc pdas have usb host functionality so they can only use usb for charging and being sync'd with by an usb host like a pc
[General Accessories] jackokring:
ideas for min cost max function

things I need to know.

1. does pocket ICS route both ways as this would mean bluetooth and wifi were not needed as standard as a pocket pc could provide this extra connectivity. along with routing of other connected pockets.

2. how standard are GDI driver files.

3. how standard are disk drive enclosure power connectors.

4. active sync between devices would be good, with selection set being done via a cab download. and date criterian.

5. about usb printer scanner combo devices such as this lexmark. the scan button would scan and save to a fixed directory?

6. DVD writer auto do from directory on blank disk?

well more later,
[General Accessories] jackokring:
a master hub yes

sorry for the confusion but the intent is the hub is a bus master.
[General Accessories] jackokring:
when plugged as a slave into a pc

the hub when plugged as a slave into a pc would export a network interface with smb shares and pretend to be a pocket pc (with set name). this would also act as a routing gateway to any device ICS. so a dhcp server and nat would be needed within the device. this would be far better than exporting multiple usb devices. and sync up all pocket pcs with the one desktop, while keeping the need for desktop power consumption to a minimum. chains of hubs would present possible device naming problems, and so mac addresses would be the logical choice for the merged virtual power pc.
[Android General] AeonFlux1603:
[MENTION=8548258]wezroot2k[/MENTION], I just wrote up a full thread for the ROM and hit the post button. It posted the first paragraph and that's it. Two hours of work and my XDA Labs app deleted everything.
[Android General] wezroot2k:
I wonder why that is?

I think you should talk to PW

---------- Post added at 08:49 AM ---------- Previous post was at 08:46 AM ----------

Y would the app do that?

Maybe you would have to create the thread from a PC.
[Android General] AeonFlux1603:
Oh. Did I do something wrong?
[Android General] AeonFlux1603:
I'll redo the work in the morning. That's got me as aggravated as you can get. I posted full sources, credits, instructions, specs, etc. All got erased.
[Android General] wezroot2k:
No man,just saying PW might know why the app would just post part of the thread and not the full thing.

---------- Post added at 09:08 AM ---------- Previous post was at 09:07 AM ----------

Sorry to hear about that man.
[Android General] Hemphiz:
App could've timed out. Similar to chrome. I copy/select all before confirming just incase (with pretty much every hefty message I write)
[Android General] AeonFlux1603:
Oh ok. Between that, copy/pasting and backspacing a lot, that's likely what happened. Working on reworking the thread now. Thanks for the insight. I'm editing in a little at a time to play it safe.
[Android General] pndwal:
Just read this new thread! Well done n many thanks.

As I explained in other thread (not sure if you understood properly - please read it carefully again to avoid heartache), XDA Labs does have a serious fault. Simply put, posts are shortened to a point where '*' symbol occurs, and because copying and pasting often swaps spaces (between words) for this symbol, the post gets truncated and your efforts are lost!

I said:

Sounds like [MENTION=6939319]Hemphiz[/MENTION] and others have all learned the hard way as I did, and take the same precautions.

Hope it helps in future, and bravo for your efforts and hard work for us! Regards, PW
[Android General] wezroot2k:
:highfive: Hey AF just read the thread and I love and thanks for the kudos and well done.

I have installed your LOS 14.1 packages and must say it is stable very smooth and love your installer :highfive: I am using it right now and loving it:svetius:

Also I did notice I minor thing and this for all user of this rom ,this is maybe not the ROM port fault but maybe the specific app bug or compatibility issue. I notice that the Greenify app does not do well with the default SU add-on of this ROM Greenify just does not load. Keeps crashing at getting su root access screen, but it does work with other root method so maybe something to look into.

Also I think you should edit the build.prop values for things like model number should be changed to 850F and not 850m and so fourth.

I have a build.prop file I can send you to look at.

Otherwise everything else is good

Excellent work AF:svetius::svetius:
[Android General] AeonFlux1603:
Yeah. And I did take your advice, but instead of using my notebook, I used Labs again, except this time I posted every time a section was complete, fully copying all my text before hitting the post button. Thank you for the warnings and info. I will know in the future.
[Android General] AeonFlux1603:
That's good to know on Greenify. Flashing a Magisk v18.1 systemless root installer zip via TWRP would likely fix the issue. I have noticed a similar problem using MiXplorer in root file manager mode. The problem like you said is likely the LOS 14.1 su_addon.

Glad you're loving it my friend. After working so hard to help make it possible, you are deserving indeed.
[Android General] pndwal:
Not sure if you're using adoptive storage, or where MiXplorer (or Greenify) loads by default, but generally apps requiring root access lose functionality or won't load at all if installed on SD storage.

I use ES File explorer which installs to SD by default, but it must be moved to internal to enable its inbuilt root explorer, otherwise its root test fails and root explorer toggles off.

This just may be your problem too. - Pays to check SuperUser enabled apps in manager, and ensure each of these is on internal storage. PW.

---------- Post added at 09:49 AM ---------- Previous post was at 09:42 AM ----------

Yet the Labs app does this often :( . I've explained in my last post on page 1. PW

---------- Post added at 09:57 AM ---------- Previous post was at 09:49 AM ----------

My post to AF above re storage may help here, but could be SU used as you say. PW
[Android General] AeonFlux1603:
I'm not running adoptive storage now. I had previously tried it to ensure operability. But, you actually just helped me troubleshoot a problem I was having on my LG G4 with root. It was due to adoptive storage. Haha. Man PW you know your Android for sure. Thanks.

So on our 850F I'm going to try Magisk or phh-superuser systemless root (or maybe SuperSU v2.82-SR5) to see if that fixes root access of the OS.

Also, I'll be posting the stock 6.0 firmware this evening sometime, with fastboot instructions. I was wrong about it being the most current build. It is actually one of the initial builds that shipped with the 850F in mid to late April, 2016. Hard to believe this device is nearly three years old now. So, once installed, the user will be prompted to install a series of OTA updates subsequent to initial boot and setup.
[Android General] pndwal:
I've found even if it times out, or can't connect when sending, things are generally handled properly by Labs app, a message appears that 'send failed', and text is all still there allowing further attempts.

However, the space-substituted-for-*-symbol problem (when copying and pasting) will truncate the post and successful send in one operation. This means a large portion of text is often lost and irretrievable. (Also, the * symbol still shows as a space while editing, so one doesn't realise that the space has been substituted until its too late.)

Great advice to copy all before sending. PW

---------- Post added at 06:17 AM ---------- Previous post was at 05:22 AM ----------

@wezroot2k, [MENTION=9720847]AeonFlux1603[/MENTION]

TB3-850F users are privileged, blessed, ecstatic, proud, happy and very thankful to have two budding (though clearly possessed of valuable experience and practical knowledge) developers on board the Good Ship TB3-850F, and its been a long time coming!

Thank you both especially for Stable and Virtually Bug Free Port to LOS14.1 for TB3-850F, as well as for other valuable resources we are gaining - including this new thread for our brand new Lineage Operating System!

Your sincere expressions of thanks / praise for helpful posts are also much appreciated.

Just a small heads-up (and sorry to spell it out) - Please don't neglect the 'thanks' (thumb up) button when a post is useful, or a sincere attempt to help is made. This is kind of the expected / default expression of thanks around here, and is possibly the most sincere form of flattery as it also elevates a members XDA profile. It's a simple and immediate way to say 'thanks', and often makes further comment unnecessary. (Incidentally, thanked posts are indexed, and are often perused for helpful information.)

Many thanks, and loving your work! PW :good::good::good::good::good:
[Android General] AeonFlux1603:
It looks like I have the Settings UI ironed out, with all mobile networks/SIM options removed in the Settings menu. I'm going to to repackage the Settings apk, implement it back into the /system directory and see if it works. If so I will update the OP with a new build.

Also, Magisk systemless root appears to be a fully stable root protocol on this LOS build. . Oddly, after flashing the Magisk v18.1 systemless root installer zip with TWRP, the Magisk Manager app doesn't appear upon reboot. But, once you manually install Magisk Manager v7.0.0 (185), root shows as properly installed and up to date. Thus far, I have noticed no instabilities or bugs with Magisk.

So, the recommended method of installing Magisk systemless root on this ROM is to first install the latest Magisk Manager v7.0.0 (185) apk, select Install from the app, and choose the direct install option. Reboot and Magisk v18.1 systemless root should be properly installed and stable. Go here to visit the official Magisk release and announcement thread https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 where you can download the latest Magisk Manager apk and systemless root installer zip. Be sure and thank [MENTION=4470081]topjohnwu[/MENTION] if you use Magisk.
[Android General] AeonFlux1603:
Update on Settings UI. After repackaging the Settings apk and framework-res.apk, I am experiencing force closes every time Settings is opened. It is probably something as simple as an encoding issue or an error during repacking but I'll keep progress posted.
[Android General] AeonFlux1603:
Update on the Settings UI. I now realize that my issues were due to my failure to properly encode my edits of the relevant .XML files with UTF-8 encoding prior to repackaging. As I may have mentioned previously, I am interested in bringing this port up to date with the latest upstream sources. So my next build release will hopefully include current LOS sources and have the Settings UI ironed out. While progress is not nearly as quick as I'd like, I am working on it.
[Android General] AeonFlux1603:
I don't know about you guys as far as audio preferences, but I was really partial to the stock Dolby Atmos app that ships preinstalled on this device. I done a little testing to find a comparable audio setup. There is a Magisk Module titled Collective Dolby Atmos (ZTE Axon 7) v1.8 (2.2.1.7_r1), last updated on January 15, 2019, that works great on this ROM, with nearly exactly the same features and UI as the stock Lenovo version of Dolby Atmos. To install it, of course, you can simply download the Module and install it via Magisk Manager or via TWRP. There are several different Dolby ports available. This is the official support and release thread: https://xdaforums.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342
[Android General] pndwal:
Quite like ViPER4AndroidFX ( [MENTION=5357345]ahrion[/MENTION], [MENTION=6037748]Zackptg5[/MENTION]) Magisk module. I think it auto-installs AML - Audio Modification Library - Magisk module (by [MENTION=5357345]ahrion[/MENTION], [MENTION=6037748]Zackptg5[/MENTION]) also. (Used to anyway.)

AML currently supports all these mods too, so its a smörgåsbord:

- AM3D

- AudioWizard

- V4AFX

- V4AXhifi

- Dolby Atmos (ahrion's ports)

- Dolby Atmos Axon 7 Oreo (guitardedhero's port)

-Dolby Digital Plus

-Bang&Olufsen ICEPower (only tested ainur version)

- Arkamys (only tested ainur version)

- Dirac (only tested ainur version)

- Dirac Hexagon (only tested ainur version)

- JamesDSP

- MaxX Audio 3

- Audio Compatibility Patch (formerly universal deep_buffer remover)

- Ainur Sauron

- SquareSound

- DTS Wizard

- Sony Xperia Z2 Sound System

I see Dolby Atmos Axon 7 Oreo in this list too. Haven't tried it, but I know guitardedhero's a bit of a genius with these mods. PW.
[Android General] Crisdax:
hello everyone i have a question ,

work good this room?

thanks
[Android General] albe75:
I too would like to know if this rom works well, I currently have the tablet locked with android 6
[Android General] fobtob387:
Any alternative ROM since the link is dead? Cheers.
[Android General] END3RMITE:
Will it work on 850m?
[Android General] :
Hi, do I have to install TB3850F_MOD_boot.img?
[Android General] pndwal:
No, its included in ROM for TB3-850F. It was necessary when flashing ROM for TB3-850M on TB3-850F. (Shouldn't be a problem if you flashed it however.) PW.
[Android General] wezroot2k:
i must agree AF interms of being partial to Dolby ATMOS and i going to try Collective one in Magisks but i have VIPER4 android install and is working superbly:good:

PS: congrats on the settings UI can't wait till you stabilize it:good:

The Viper4Android HIFI version works even better, well as far as see or hear.
[Android General] AeonFlux1603:
I'm a huge supporter of Viper4Android as well. Good to hear the audio drivers are working on this ROM.

Update: Ok so I also played around with the AM3D Zirene Sound module for Magisk. I always test the full effects of audio mods using a 7 piece JBL speaker system which I connect using either Bluetooth or a wired connection using the 3.5mm audio jack -- it has both options. I was blown away by the results of AM3D! Breathtaking clarity and virtual surround effects like I've never experienced using an Android audio mod. I used it with music and movies with good digital sound. Sitting directly in front of the speaker system (in front are the left & right main speakers, the phantom center, with subwoofer on the floor centered. In the rear are left and right virtual surround and another phantom surround center speaker) and closing my eyes, I cannot pinpoint the source of sound at all. It's as if the audio is literally 360° all around. Anyway, my point is, AM3D was built as a stand-beside mod to other audio mod apps, like Dolby Atmos, Viper4Android, MaxxAudio and Viper4ARISE FX. AM3D does not overwrite your audio_effects.conf file either, but merely patches it while backing up the original ROM-implemented sound configs. I've used both an AM3D + Dolby Atmos and an AM3D + Viper4Android setup, and I can't decide which sounds better. Both amazing audio combos, with AM3D adding exactly what was missing from other sound mod setups.

So I've said all that to say this: do you guys think including baked-in sound mods in this ROM would be a good choice, or merely leaving all audio options up to the individual user (after all, Magisk includes a number of systemless mods for sound)? Another option, and I already have one compiled, is maybe including an Aroma installer for sound mods, letting the user choose which to install and which to exclude during the TWRP install. Not every user wants the systemless audio modules offered by Magisk, but instead a sysrem-wide installation. I'm presently getting our LOS 14.1 ROM up to date with upstream source, and the subject of audio mods has been in my thoughts for the last day or two. I'd love input on this.
[Android General] pndwal:
I like the OPs new motif! - might need a new pseudonym? Lucky-Goldstar-Junkie? :)
[Android General] AeonFlux1603:
??

Lol. Really I'm just particular to LG smartphones.
[Android General] AeonFlux1603:
Hey [MENTION=8548258]wezroot2k[/MENTION] I updated my earlier post when you and I were discussing audio mods. Please read it over, as I'd love you guys' input on this.
[Android General] pndwal:
I'm always in favour of leaving such options to user where possible, and, as I mentioned, I'm partial to AML compatible Magisk audio mods (see list of supported mods I mentioned.) Guys like [MENTION=5357345]ahrion[/MENTION], [MENTION=6037748]Zackptg5[/MENTION] & [MENTION=4445176]guitardedhero[/MENTION] have done amazing work on compatibility, and AML actually fixed audio fx problems on my LOS14.1 custom Y550 phone even before updated commits did. Seem AML will allow the compatible mods to play nicely together, even running simultaneously. PW
[Android General] AeonFlux1603:
Sounds good. Just as root is an option for the user, I'll leave audio mods in the users' hands as well. Our current LOS 14.1 audio does have some minor instabilities (high volume clipping, inadequate max gain, mid-range clarity issues, Bluetooth absolute volume cutoff, etc.) but I'm using logcat to improve upon these, and I'm hoping that updating the audio drivers and libraries with current source will aide also. Thank you for your input as always.
[Android General] wezroot2k:
I agree with PW make it user choice but I would love to test those combo you mentioned.

BTW I am having a problem with Dolby atmos for nougat it keeps closing and i can' t seem to find the version you mentioned earlier ,do you have a link to that specific version?
[Android General] AeonFlux1603:
Yeah, here is the XDA thread for it: https://xdaforums.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342

I use this on my LG V30 also with great results. Here's a direct link to the ZTE Axon 7 port of Dolby Atmos v1.8, https://xdaforums.com/devdb/project/dl/?id=31208, which should work on most ROMs -- stock & custom -- from Android 6.0 and later.
[Android General] wezroot2k:
Hey AF do I need magisk for AM3D to work? I have installed it but doesn't load i get a white screen.
[Android General] AeonFlux1603:
Well, that's a great question. And I'm not sure on the answer. I am running the latest Magisk on both my 850F and my LG V30. When I installed the Dolby Atmos zip via TWRP, Magisk was recognized and Dolby was installed systemless-ly as a Magisk mod. I'm thinking to use it sysrem-wide, without Magisk, be sure you have a current BusyBox binary set installed, and try setting SELinux policy to Permissive. It was my understanding, from reading the Dolby Atmos support thread, that it can be installed sysrem-wide or systemless-ly, and that the determination is made on whether or not TWRP recognizes Magisk in the path of /data/adb/magisk.img. The same goes for installing AM3D using TWRP. But please know that I'm only assuming in this -- my understanding from what I've read on it. Both my devices with the Dolby/AM3D combination are both running Magisk.
[Android General] AeonFlux1603:
I've requested that a forum mod move this thread over to the Lenovo Thinkpad Android Development forum. I have it confirmed that the Thinkpad forums are the dedicated device forums for our device. This will sure make it easier in future to locate and post threads for our device.
[Android General] wezroot2k:
Hey AF you got to tell me how you installed the AM3D on the 850F cause I've tried and I can't seem to make load just freeze at the white screen.

Tell me your setup on 850F what version and so on.