yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Dhalsim43:
For me, LOS and Google cameras are working well. LOS camera icon was not there immediately at first boot but at second boot it was fine. Never gone then. The rom is working very well. I've dirty flahed on LOS 16.0. Thanks for the very good job.
[Nexus 6  Original Android Development] Danzic59:
I'm working fne. Google camera needed settings adjusted manually ...N6 Fridays build ...Just having minor issues with Paypay Prepaid app. I installed it before I did any Magisk ...
[Nexus 6  Original Android Development] SteveYoungs:
This made me chuckle...
[Nexus 6  Original Android Development] Gysper:
The camera is there, just no home icon. The fix is the double press the power button for me.

Also, I mentioned it before but I'll mention it again because this is how I got the camera to work. I rooted with Magisk Canary, then installed Google Camera from the play store. Also installed Kill Camera app from the play store. Open Kill Camera App and press the Kill button which requires root. Then the camera will launch.
[Nexus 6  Original Android Development] TotalChen:
Totally agree, exactly non-app-relative. 3 things don't come up with the right timing is the reason why we're facing the camera problem, I've no idea how cold reboots indubitably do the magic. May this be a clue to the puzzle?
[Nexus 6  Original Android Development] JaimeZX:
Just wanted to say it's been several days since flashing and the phone is working flawlessly. Thanks much! :)
[Nexus 6  Original Android Development] dvdram:
About the camera trouble:

First time I noticed this was in LOS 16: the camera did not work after rebooting, it crashed instantly. And it also did not matter which camera app I used. Soon I discovered that this crash was not related to flashing a new LOS version, it also happened whenever I just rebooted my N6.

Then, by pure accident, I discovered that the camera did start flawlessly, when I did not use the camera before I had used any app that needs GPS coordinates!

I know this sounds crazy, but that is my experience on my N6, and I can even reproduce it now running LOS 17.1: after rebooting, I need to wait for a few seconds, then I can start any GPS app to let it calculate my position for half a minute, I can close the app, and then I can start any camera app I want without any trouble.

If I start the camera as first app right after rebooting, it crashes and will not work, and I have to reboot again, wipe the cache again, and then I can follow the procedure as described above.

I am not trying to wind you up, I am really experiencing this on my N6!
[Nexus 6  Original Android Development] olmeca:
After reboot I must disable and then reenable the radios to got mobil data.
[Nexus 6  Original Android Development] Elektroschmock:
Do you really think the information you gave me is enough for me to work with?

We even have a guide on how to properly report a bug: https://wiki.lineageos.org/bugreport-howto.html

Usually I am not so strict and also accept bug reports written here. If and only IF enough information is given. If not I'll happily ignore them.

But as you are new you probably didn't know that.

Just put yourself into my position. How should I know which build you have installed, if you used the right installation method, or which provider you use ...
[Nexus 6  Original Android Development] gettes:
trying to build 17.1 for shamu

I have been trying to build for 17.1 shamu. I have tried varying levels of OS/java. Running in docker container on a mac - so i can reconfigure the software however necessary. i also extraced device files via adb connect within the container. still the error happens.

breakfast shamu produces:

Device shamu not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).

Found repository: android_device_moto_shamu

Default revision: lineage-17.1

Checking branch info

Checking if device/moto/shamu is fetched from android_device_moto_shamu

LineageOS/android_device_moto_shamu already fetched to device/moto/shamu

Syncing repository to retrieve project.

Fetching projects: 100% (1/1), done.

repo sync has finished successfully.

Repository synced!

Looking for dependencies in device/moto/shamu

Looking for dependencies in kernel/moto/shamu

kernel/moto/shamu has no additional dependencies.

Done

** Don't have a product spec for: 'lineage_shamu'

** Do you have the right repo manifest?

from looking around i have set my roomservice.xml file as:

<manifest>

<project name="LineageOS/android_device_moto_shamu" path="device/moto/shamu" remote="github" revision="lineage-17.1" />

<project name="LineageOS/android_kernel_moto_shamu" path="kernel/moto/shamu" remote="github" revision="lineage-17.1" />

<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="lineage-17.1" />

</manifest>

any help is appreciated. i know i am missing something. i just don't see it. i have looked at a great many web pages of reports related to this error and nothing seems to change the outcome.
[Nexus 6  Original Android Development] SteveYoungs:
I'm looking forward to the automatic "Update Recovery" feature being turned on. The toggle has been there in Developer Options for the last couple of LOS versions but I don't think it is live yet, is it?

Speaking of recoveries, is version info (of the recovery) available from the OS? And if it is, where?
[Nexus 6  Original Android Development] Elektroschmock:
Don't extract AND add the muppets repo at the same time. Guess that messed something up.

I guess removing all files under vendor/motorola and do a 'repo sync' should fix it.
[Nexus 6  Original Android Development] Eazy:
I also have problem with mobile data. I have had it since Android 9 roms. It is kind of impossible to find the reason as it comes and goes. A reboot have always helped. I was hoping this problem should disappear on LOS 17.1. Today even a reboot and clear dalvik and cache didn't help. I was on first release of LOS 17.1 so I updated to 19:e release (already had it downloaded) and now mobile data works again. Don't know for how long... Don't know if this is a hardware problem, provider, software problem.

Can I try with a different radio, or must i use the latest radio for LOS to work?
[Nexus 6  Original Android Development] Elektroschmock:
As the radio images are proprietary it's hard to say if one image is okay and the other is not okay.

You can extract all radio.img from here https://developers.google.com/android/images#shamu

There are special Builds for T-Mobile and Verizon. I nerver tested the radio images from those builds as I'm not on one of those providers.

But actually it's more likely that it's a:

- apn problem

- sim card problem

- provider problem
[Nexus 6  Original Android Development] mahir555:
i am on the latest nightly 21-4 and i have this issue since the 1st one.

I enabled the freeform window feature from the developer options . when i activate it on any app the floating window forms but trying to move it cause app force close and trying to resize it cause a sudden system reboot.

attaching a log file .

can any one confirm this pls.
[Nexus 6  Original Android Development] gettes:
Tried what you suggested. No joy. I still get the same messages. I tried various permutations of what you suggested. Still get the same error.

I even cleared the out directory and re-ran breakfast shamu and still get the same errors.

when looking for lineage_shamu the only file name with that string in the name is: ./device/moto/shamu/lineage_shamu.mk

---------- Post added at 20:38 ---------- Previous post was at 20:36 ----------

Tried what you suggested. No joy. I still get the same messages. I tried various permutations of what you suggested.

Still get the same error.

I even cleared the out directory and re-ran breakfast shamu and still get the same errors.

when looking for lineage_shamu the only file name with that string in the name is: ./device/moto/shamu/lineage_shamu.mk
[Nexus 6  Original Android Development] BootloopedMillennials:
I don't use profiles but decided to setup two to test. One if on home WiFi, it disables lockscreen. Off home WiFi, it reenables the lockscreen security. I noticed that sitting on home WiFi, it'd eventually go back to enabling the lockscreen security. Troubleshooting, I disabled power button instantly locks in settings. Everything seems to be working as intended now.

Edit- I spoke too soon, it went back to locking even though on home WiFi.
[Nexus 6  Original Android Development] maddog3030:
Is there anybody else not getting Wi-Fi calling to work

On this ROM I'm on T-Mobile?
[Nexus 6  Original Android Development] gpatm:
Hi all, a quick note on the camera issues.

Without extensive experimentation, I have noticed that my chances for the camera to work after a restart are significantly higher if the performance profile is set to "quick" (settings->battery->battery saver and performance->device performance).

If there is some merit to this, I am assuming setting it to "performance" will be even better and maybe setting it to a higher performance setting could be automated before a restart and reset to "balanced" or anything else following boot up.

I am assuming someone that knows when the profile comes to play during the boot sequence could tell if there is a chance of this having merit.

I will update if I confirm this, sorry if I am adding just another theory to the pile.
[Nexus 6  Original Android Development] Dhalsim43:
Wi-Fi calling doesn't work after LOS 15.1
[Nexus 6  Original Android Development] Elektroschmock:
It has been added some days ago. No there is no way to see from OS which recovery you have currently installed.
[Nexus 6  Original Android Development] esysfound:
Hi - planning on the migration to this. One question; as build updates become available, can these be dirty flashed vs. needing to wipe especially Data? Uneasy about Titanium's abilities with Android 10 and it surely will require some reinstalling. I don't mind a bit of this but I surely don't want to have to periodically, repeatedly install and configure my 30 apps that need tweaking.

If the full wipe and flash of 17.1 and installing all apps 1 time is all that's needed, and the Nightlies or other subsequent 17.1 builds can then be dirty flashed, that would be great. Could you clarify, please.

Thanks and thanks again for the hard work on the ROM.
[Nexus 6  Original Android Development] Elektroschmock:
What you call 'dirty flashing' is the usual update process. If that needed a wipe every time we would do something very wrong.

You just need to setup Lineage-17.1 once. Even upgrading from any official Lineage 14.1, 15.0, 16.0 build should work without wipe. But to be honest I only tested upgrading from 16.0.
[Nexus 6  Original Android Development] esysfound:
Hi- Just wanted to be sure; this is good news. Thanks
[Nexus 6  Original Android Development] maddog3030:
thanks for the info and here I was blaming T-Mobile appreciate it and stop banging my head up against the wall.
[Nexus 6  Original Android Development] woodsticks:
Updated to 17.1-20200421-NIGHTLY-shamu from 17.1-20200418-NIGHTLY-shamu. Now the Pixel launcher & camera are broken, in addition to very laggy. Has anyone else updated to "0421" and have any suggestions?

I will most likely rollback to (0418), it worked really well and camera worked.

Thanks in advance.
[Nexus 6  Original Android Development] Gysper:
If you're rooted, download the Kill Camera app and press the Kill button and the camera will work again. Can't comment on the pixel launcher.
[Nexus 6  Original Android Development] Elektroschmock:
Update to the newest nightly!
[Nexus 6  Original Android Development] zzenyoo:
Just updated 04.21 -> 04.22. For the first time sins... ever camera works (for me) from the first boot (btw, I'm using 'quick' setting phone speed).

Edit: 4.22 -> 4.23 crashing again, back to Kill Camera workaround.
[Nexus 6  Original Android Development] dvdram:
Thanks for testing!

I changed the setting like you described, and like on your side, it did not work.

Is it possible that the lock screen activates every time the wifi changes channel or every time there is some kind of interference from some other radio signals, or some thing like that? If there's even just a micro second of missing wifi signal, that could trigger the locking.

---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------

I followed your idea and set performance to maximum before I flashed the latest nightly 0422. This time the camera worked right away, I even did not have to fiddle around with GPS like before. Could be a coincident, but I will use the same setting next time!
[Nexus 6  Original Android Development] Elektroschmock:
Should work on 0422 regardless of the power profile.
[Nexus 6  Original Android Development] dvdram:
So it was a coincident? :)

Curious: did you find the reason for the camera crashes and is it explainable to noobs?
[Nexus 6  Original Android Development] Elektroschmock:
The app crashed because camera HAL was reporting no camera devices.

For the HAL to work properly there are two services needed. 1. cameraserver and 2. qcamerasvr.

Cameraserver needs qcamerasvr running to work.

So we started qcamerasvr and then cameraserver in the init. At least this was the plan.

But init is not synchronus which means it can reschedule the starting of those services which could lead to switched starting order.

See:

https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/273010

https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/273406
[Nexus 6  Original Android Development] BootloopedMillennials:
I think it's just broken because other options work as expected. Another weird one is if you choose say completely disable lockscreen on WiFi, the home button no longer works when unlocked in that state.

IIRC System Profiles was going to be removed completely for LOS 17.1 but they decided to keep it last minute. So maybe it still has bugs that need to be worked out.
[Nexus 6  Original Android Development] wrsg:
Should the camera problem be completely resolved in the 20200423 build? Because Google Camera still crashes out when I try to open it.
[Nexus 6  Original Android Development] Elektroschmock:
Do other cameras work? If yes it's a different problem.
[Xiaomi Mi 2] FreddieFrog:
Would it be possible for someone to add the latest security patch to the last MIUI 9 rom for the Xiaomi Mi 2/S? It runs so smooth on my Mi 2, however I'm afraid to use it since it has a very outdated security patch. Thanx
[Galaxy S 5 Q&A, Help & Troubleshooting] marc.knuckle:
Hi guys

I have a spare phone now my son upgraded, the S5 SM-G901F. I thought it wound be fun to install another software, possibly more up to date. So I first set out to root it but I haven't played around much with this sort of thing for long while.

I googled and found it seemed to be Odin to use so I downloaded 3.10. Also downloaded cf root. I went into download mode and when I plugged it in, the light in Odin lit up showing successfully connected. When I added the cf file and clicked start it went through some steps but stuck at Recovery. Img and wouldn't progress further.

I tried multiple times, tried a different cable and USB port and also Odin 3.07 and a different cf file even though I think it was the same one but from a different site. All no better.

Originally I bought it a few years back, used from a colleague. I think it was a carrier phone, EE iirc, and I had to get a code to unlock the SIM to use with mine. Maybe that also means it's software is locked?

Any help much appreciated

Thanks, marc
[Galaxy S 5 Q&A, Help & Troubleshooting] marc.knuckle:
No one guys?

Please help

Marc
[Galaxy S 5 Q&A, Help & Troubleshooting] marc.knuckle:
Please help
[Galaxy S 5 Q&A, Help & Troubleshooting] godofsalt:
well to be honest, i would need to spend some time, "Googling" your model .... . I believe , your S5 is a Dev phone, meaning, it was not set up for any carrier, just for running demo's and such. IF this is true, I have no true answer for you.

Odin yes, you need that, that is true! (Believe 3.07, 3.09 and 3.10 work the best for these phones. Had tried a very newer version, several month back, and it did not do the job.. something like 3.14 or 16)

I recommend going to Sam Mobile, and run your model # through them. They will give you all the info about your model and possibly the latest firmware for it.

Sorry that I can not give you all that you are needing. I just don't know a ton about those S5 Plus models. (( I had to even look 'em up too) the plus has a slight better chip was well as graphics, but again, I dont know of any that actually work on a modern carrier like sprint, Verizon, T-Mobile , etc.)
[Galaxy S 5 Q&A, Help & Troubleshooting] marc.knuckle:
Thanks for the reply mate.

It definitely isn't a Dev phone, my colleague definitely had it on contact from a carrier initially.

I hadn't actually realised or noticed it being a Plus model as some sites mention the Plus and some don't.

Any other help from anyone appreciated
[Galaxy S 5 Q&A, Help & Troubleshooting] godofsalt:
OK, Was only going off your model # you had given.

Did check... Odin and a good copy of CF auto root... That should be that.

Then of course, get away from a really old non sucure os (6.01 MM was their last made) .

Other than those 2 pieces, you should be good to root

Not pushing, or anything but LineageOS is rather good and does run well on these!

Plus, get a monthly security injection!
[Galaxy S 5 Q&A, Help & Troubleshooting] marc.knuckle:
That's the problem as i mentioned in the first post, I've tried with odin and cf root and it doesn't work. That's why i posted on here. I wondered whether the phone was locked to the carrier.
[Galaxy S 5 Q&A, Help & Troubleshooting] godofsalt:
Well, I would have to say NOPE!

Well only trying to keep your Q, on the top, so folks that might know, could help!

BTW, when I looked your model up, totally different CPU and GPU, which might need a different CF auto root zip, or a different one to actually work... Since hardware is different.

Just guessing on that, but, could be wrong. Rather busy at the moment, but will look up your specs again, and see if I find something for ya.

Mean time, Hopefully someone could chime in and point you towards the correct path to take...

OH

Q- What sort Recovery do you currently have? (Stock or custom (e.g. TWRP))

Might want to check for one for your phone.

I would actually start with TWRP, see what they have for ya.

( Will need Odin for this! BUT, once you have a Recovery in/on the phone, then you could use Magisk to root ot try CF and see 8f that works for you (I use Majisk) Plus add in the fact that you should make a Back up, of your current system! In case of issues, you can always jump back to Stock. )
[Galaxy S 5 Q&A, Help & Troubleshooting] marc.knuckle:
Cheers mate

It's stock recovery at the minute
[Galaxy S 5 Q&A, Help & Troubleshooting] godofsalt:
Sorry, that I have not gotten back sooner. Issues to deal with.... Just like many others these days...

That said, I take it, that you have a custom Recovery, and also Root?

Hope so, if not, I'm still here for ya
[Galaxy S 5 Q&A, Help & Troubleshooting] marc.knuckle:
Cheers mate. So, some progression.

Firstly i didn't have a custom recovery or root. I was getting stopped at the first hurdle.

So, i figured it had something to do with it using a carrier firmware, EE, in the UK. So i found a stock European firmware and successfully used odin to flash it. Then i flashed CF root and TWRP. All good.

So with new confidence i flashed Resurrection Remix Android 9. Although it seemed to have worked, each time i tried to complete set up, straight after imputting my gmail address, the screen was black. Not BSOD type though, if i pressed home it went back to the home screen to i just couldn't complete set up.

So i tried Lineage and that was a boot loop.

Not sure if part of the issue was Gapps but i was definitely using the correct version. ARM, Android 9, stock.

I gave up, reinstalled the stock Android marshmallow and rooted again and installed TWRP. that's where i am now.

Shame really as i fancied a more up to date OS.

Thanks, Marc
[Galaxy S 5 Q&A, Help & Troubleshooting] godofsalt:
Wait, isn't what you were wanting?

Well at least you now have a Recovery installed! Now, with that of course you can now make a back up of your stock!!!

( other words,.. MAKE A BACK UP! That way, you only have to wipe the system, data, cache and BAM, in the Flash of zip, your back at square one...)

OK, not sure if you picked up a new info about LineageOS, across the pond....

But

They ran into some issues, (soon and hopefully sooner, it will be fixed). Now, after that, they will be dropping LineageOS 17.1 Official!! Yes, for Galaxy S5 too

So, keep an eye out for that, cause am in same Boat, waiting for the Official release.

( personal, I run LineageOS, Magisk (Root and some goodies.. Unfortunately I do tend to add Ggogle, but like Pico, nothing larger. Do flash a kernel also. That said, rather stable, and most everything works) at least for me.... Just waiting for Official 17.1 to roll out! (like just about anyone left that has these phones...)
[Galaxy S 5 Q&A, Help & Troubleshooting] marc.knuckle:
Thanks mate
[Nokia 6.1 Plus (X6) Questions & Answers] Nishantkjha:
As the title suggests my device have been randomly restarting after the March update. this has been happening at least 5 to 10 times per day. Anyone else also facing this issue ?
[Nokia 6.1 Plus (X6) Questions & Answers] PaperPlane217:
Me too but mine ain't that frequent

First the screen starts flickering/blinking then shows up android one boot logo or nokia logo and the phone just restarted

It happens like 2-4 times a week
[Nokia 6.1 Plus (X6) Questions & Answers] Nishantkjha:
After March or from earlier also You are facing this ?
[Nokia 6.1 Plus (X6) Questions & Answers] gopu5:
Never faced restarting issue after March 2020 update working normally...
[Nokia 6.1 Plus (X6) Questions & Answers] PaperPlane217:
I think since march
[Nokia 6.1 Plus (X6) Questions & Answers] Don271:
Front camera not working in any application

Since march patch update from camera option is not there in camera application. It is not working in other application too like whatsapp. Does anybody faces same issue?
[Nokia 6.1 Plus (X6) Questions & Answers] KelvinCrag:
Have you tried factory resetting?
[Nokia 6.1 Plus (X6) Questions & Answers] Don271:
No I haven't.... I wanted solution without factory reset.

I tried resetting camera application, even tried with deleting app data but nothing works.
[Nokia 6.1 Plus (X6) Questions & Answers] Nishantkjha:
Try to clear The app data and cache and see if it helps.
[Nokia 6.1 Plus (X6) Questions & Answers] Don271:
No it didn't help. I guess i left with only factory reset now.
[Samsung Galaxy Fold ROMs, Kernels, Recoveries, & O] tudo1994:
In case you guys know already, the android 10 has been released for the F907N

I cant find any thread for the F907N so I just opened a new one so that you guys can come and discuss!!!

Thanks!!!:cool::cool::cool:
[Samsung Galaxy Fold ROMs, Kernels, Recoveries, & O] liggerz87:
what you think of the update so far
[Samsung Galaxy Fold ROMs, Kernels, Recoveries, & O] tudo1994:
I can tell its good!!!

Very smooth, stable!!!

Especially the full screen gesture!!! No you can access the phone from any corner, any side of the phone (thanks to the One UI 2.1)

For the other aspects, android 9 is good already so this one just somehow improved it!!!
[Samsung Galaxy Fold ROMs, Kernels, Recoveries, & O] deadlyheart4u:
yes the performance is good, phone has become smoother and more buttery. I just wish I could have managed to get Samsung members for India and Samsung pay, I am in India and Korean language is something I dont understand,
[Samsung Galaxy Fold ROMs, Kernels, Recoveries, & O] tanipat:
anybody guide for rebrand 900n to inter rom, or just debloat korean apps is quite annoying