yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] /root:
14.1 builds are switched to monthly updates and the nightly(15.1) builds are now daily updates.

https://review.lineageos.org/c/LineageOS/hudson/+/234086

https://www.lineageoslog.com/build/scheduler

Updating has always been user choice, you can choose not to update everyday. changelog has nothing means the build has no changes from previous one. But auto builds will happen daily for 15.1.

I personally have disabled auto check and I am on 19th November build as of now. I check once in two-three days the changelog and only update if there is a critical patch to update. So far nothing so lets see how long the jump is going to be.

[MENTION=1539908]freddii[/MENTION]

You don't need to update everyday or that order. either. You can flash any build at any time on any earlier release. So don't worry about it.

You reported about website policy is bug report, which technically is not a bug but a change in the release cycle. Not the best place to do and you were suggesting build releases in dev channel. Devs work on the OS and not when its released. They do the necessary changes and push it to the code, when is release is not upto them.

Some would argue daily auto builds are good, instead of a too many changes in weekly or monthly builds there is small changes in the build and bugs could be fixed very quickly. So you can just update weekly or monthly, now the choice is yours.
[Nextbit Robin] freddd1:
Manually checking for updates? I think the last time I had to do this for an operating system was back with Windows 98 before the automatic update introduction with Windows XP. Even then the updates were usually small module update downloads, not an entire operating system download.

I do not know how enthusiastic the regular LineageOS user is about manual operating system maintenance but I just use my phone for calling, messaging, third-party applications, etc ...

Checking change logs for important changes or security updates to see if I have to download the entire operating system again is not one of the things I would like to do.
[Nextbit Robin] /root:
I told you what I do and did not suggest everyone should do. For most people automatic update check is available and its recommended to do it just like Windows update, everyone is told to keep your system updated and the non technie ones always fail to do that. But techies like you and me we know when its necessary to update.

You talk like an enthusiast but solving a problem that only exists for a novice user which you clearly aren't. Flashing ROM has always been for advanced users like us.
[Nextbit Robin] hafiz_binshah:
My phone gets hang and eventually reboot it happens at least 1 time in a day. So, am I the only one having this issue?
[Nextbit Robin] oshane126(jamaican):
I also am having that issue
[Nextbit Robin] hafiz_binshah:
Getting update on every day but, no fix for the root issue!!
[Nextbit Robin] boxes:
Official lineage 14.1 builds would be better for stability.
[Nextbit Robin] AnierinB:
Glad you're putting that Robin to good use [MENTION=5795145]javelinanddart[/MENTION]! keep it up
[Nextbit Robin] mkstevo:
I bought a Robin for my wife which had LineageOS 15 installed on it. It too suddenly stalls, does nothing for about 5 minutes and then reboots. It seems to do this once a day, maybe once every two days. So no, you are not the only one having this problem.

Is it possible to downgrade to LineageOS 14 without formatting the device totally? (Assuming 14 doesn't have the random reboots issue)

I'm tempted to try to install stock software as I have a Nextbit Robin running stock and I rather like the stock software with Lean Launcher, but again don't really want to format the device if I can avoid it.
[Nextbit Robin] oshane126(jamaican):
just tried flashing stock and it seems my phone died, during the transfer everything stopped. I plugged out the usb and try rebooting fastboot and now its a dead phone
[Nextbit Robin] AnierinB:
Hold down power and volume down for 60 seconds.. hopefully you'll go into a reboot or fastboot.

It's never a good idea flashing when the battery is low
[Nextbit Robin] oshane126(jamaican):
tried that, its gone for good
[Nextbit Robin] AnierinB:
Wait until the battery dies fully. I've had this issue on several robins. Is it showing qcom 9008 on Windows? There may still be hope.... If so, try the same keys after attempting to charge. This device is very abnormal when it comes to these issues. I once almost sent a return to Amazon before attempting my fixes one more time.
[Nextbit Robin] oshane126(jamaican):
So what do a do after it shows qcom 9008? There actually a flash tool for flashing dead qualcomm devices but a dont have the necessary files to use iton the robin
[Nextbit Robin] AnierinB:
I held down vol + and power for 60+ seconds. Maybe let it discharge for a night, plug it in for a bit and then attempt it again. I once fixed it by plugging it in with a op3t dash charger. It's definitely an odd issue for sure

And yeah you're talking about qpst/qxdm? I doubt there's a firehose file and programmer.xml for ether so that's not an option here.
[Nextbit Robin] oshane126(jamaican):
i need someone to do an emmc dump for me
[Nextbit Robin] AnierinB:
Even with an emmc dump of mmcblk0 you'd still need those 2 files that I mentioned in order to flash with qpst/qxdm
[Nextbit Robin] oshane126(jamaican):
Well i have the programmer files but not the firehose and im hearing that i need to get that from manufacturer
[Nextbit Robin] nabicat:
Clean flash from stock Nougat, and so far have been rock solid after 3 days. Only installation issue occurred when in fastboot the universal ADB driver did not load for the Robin. Installed the stock driver, listed on the Razer forum and driver loaded for fastboot mode.
[Nextbit Robin] vandyswa:
Updated to January 8th 15.1 after a couple months with an older ROM. Background playing from Firefox Beta

keeps stopping, exactly like when Google first inflicted "doze" on us, although Firefox is definitely listed as

"don't optimize battery". Playback will stop, and continue when you turn on the screen. Interestingly, if there's

a notification from the web browser pending, dozing doesn't happen.

On AC power background playing works fine.
[Nextbit Robin] MP9c:
Anyone else experience freezing then immediate reboot while doing some reddit browsing or taking photos?

Should I do a clean install?
[Nextbit Robin] iluvatrix:
Anyone noticed the last 2 updates were sized at 487mb but all previous versions were 506mb? What is the reason?
[Nextbit Robin] javelinanddart:
Newer updates should fix that.
[Nextbit Robin] -R47-:
I've been using this ROM for a few months, and I just wanted to say thanks [MENTION=5795145]javelinanddart[/MENTION] , it's been great, no major bugs, and really breathed some new life into my Robin.
[Nextbit Robin] iluvatrix:
is there something i could flash with TWRP to get the VoLTE settings to appear?
[Nextbit Robin] drspinderwalf:
Yeah, how do we get VoLTE working? The device wiki entry says it has support...
[Nextbit Robin] LieDanG:
Updated from LOS 14.1 with a clean flash but noticed that now it doesn't detect 5ghz wifi, it's a bug from latest release?

Edit: Updated now to LOS 16 and 5ghz wifi works fine there, so it seems it's a bug from 15.1
[Nextbit Robin] iluvatrix:
I'm using Opengapps now, if I wish to use Mindthegapps how should I go about it?

Thank you
[Nextbit Robin] JayAbbhi:
The latest August 15th update is busted. Everytime I try to update from a prior build it is extremely sluggish and slow to respond to button presses, ending with the screen going completely black and the phone not responding to any button combo other than booting into fastboot.
[Nextbit Robin] EsoteRIcalfreaK:
Hello all. Thank you javelinanddart for creating this thread and supporting us (dying) Nextbit Robin fans!

I just flashed TWRP recovery and the latest Lineage 15.1 OS (as well as Gapps 8.1 Super for ARM64), and every single thing works perfectly except for the fact that the WiFi Calling toggle option disappeared entirely.

I'm on T-Mobile. Both T-Mobile and Nextbit Robin support WiFi Calling, and I had it on the stock ROM before flashing LineageOS. I have searched for days and I can't seem to find anything on the topic. I followed the LineageOS installation instructions from the official website to the t. I tried reflashing everything just in case (originally flashed with Gapps 8.1 Pico for ARM64, then flashed again with the Gapps 8.1 Super version), but no dice.

When I search in the settings, it comes up in the results, and when I click it, it takes me to the Mobile network settings page, but there is no mention of WiFi Calling anywhere in order for me to switch it on or off.

Anybody having similar issues? Is there a workaround? Any help or guidance will be greatly appreciated. Thanks in advance!

EDIT: only thing I didn't do was create a backup. Was that my mistake? I don't think that would have anything to do with anything, but I'm mentioning it just in case

EDIT 2: I was on the stock 7.1.1 ROM before doing this venture
[Nextbit Robin] jabashque:
Last I recall, whatever IMS-related blobs that were being used for 15.1 only supported VoLTE, not wifi calling. javelinanddart couldn't get wifi calling to work at the end.
[Nextbit Robin] EsoteRIcalfreaK:
I've search near and far..where is this discussed?

Only reason I flashed 15.1 over 16.0 is because of ANT+ and IMS support (as stated in this Ether Lineage OS wiki in the yellow exclamation marked section, as well as in the Known Bugs section of the official 16.0 XDA page)
[Nextbit Robin] jabashque:
I'm not sure if this ever got mentioned in any place other than javelinanddart's old Hangouts group.
[Nextbit Robin] EsoteRIcalfreaK:
So then what other purpose is there to continuing 15.1 and 16.0 if the sole reason they continued 15.1 was because of ANT+ and IMS support...?

....and why does it say everywhere that is the sole reason of continuing 15.1 if it's not..?

So confused here. Please somebody shed some light on this issue or point in a direction of a solution to this problem [or as a last resort recommend another (fairly stable for daily use) custom ROM with WiFi Calling support]
[Nextbit Robin] jabashque:
Well, IMS doesn't work at all on 16.0, so you don't even get VoLTE as a result. IMS works partially on 15.1 and at least allows VoLTE, but not wifi calling.

As for a custom rom with wifi calling support, I'm afraid you'll have to stick with Nougat for that.
[Nextbit Robin] yourguitarist:
Did you happen to ever get these files? I have a phone I'm trying to unbrick as well but I'm struggling to find anything
[Nextbit Robin] oshane126(jamaican):
Yes i have, check my thread https://xdaforums.com/nextbit-robin/help/qualcomm-hs-usb-qdloader-9008-t3952686
[Nextbit Robin] feydakin:
Does someone has the latest available 15.1 Rom by any chance and can upload it? (should be lineage-15.1-20200217-nightly-ether-signed.zip if my research is correct)
[Nextbit Robin] javelinanddart:
[COLOR="Blue"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Blue"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/COLOR]

Installation:

If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the official installation instructions link below.

If you are coming from stock or other ROMs, you need to make a factory reset.

As always, make sure to backup before installing this ROM.

More detailed instructions at:

Install LineageOS on ether

Download link:

LineageOS Downloads

Official root addon

LineageOS Extras

Changelog:

Changes for ether

Bug reports:

How to submit a bug report

LineageOS JIRA

Donate to support development:

Donate via PayPal to javelinanddart

Donate via PayPal to LineageOS

XDA:DevDB Information

LineageOS 15.1 for Nextbit Robin (ether), ROM for the Nextbit Robin

Contributors

javelinanddart, javelinanddart

Source Code: https://github.com/LineageOS

ROM OS Version: 8.x Oreo

ROM Kernel: Linux 3.10.x

Based On: LineageOS

Version Information

Status: Nightly

Created 2018-08-21

Last Updated 2018-08-21
[Nextbit Robin] javelinanddart:
Ugh. Duplicate thread.
[Huawei Watch 2] tattoohead:
I'm wondering if I set the watch up right or if this is the behavior of the watch.

When my phone rings (pixel 2 XL) and I try to answer it from the phone, the call is picked up but on my watch. I have to turn off the option in the watch's settings when I carry my phone around.

What I'd like to have it do is, when there's a call - pick up on the phone if answered from the phone and pick up on the watch when answered from the watch.

Is this possible?

Thanx...
[Huawei Watch 2] dudaka:
I believe it works like that for me.

Last time I picked up the call from phone I was able to speak on the phone straight away, but I'm not sure if it was also calling on the watch.

I get that delay sometimes for call notification on watch.
[Huawei Watch 2] featureza8336:
It is possible.

Be sure that under BT settings for your watch on your phone, Call Audio is turned off. On your watch, make sure Use for Call Audio is turned on. (not sure if that's the correct wording for the watch settings)
[Huawei Watch 2] MrWhite0429:
If you go under Connections, Bluetooth, you can toggle the option "answer voice calls on watch"
[Huawei Mate 9 Guides, News, & Discussion] fairyland4ever:
My mate 9 originally is C567. I rebrand it to MHA-Al00C00 and upgrade to mha-al00c00b360. I used twrp rebrand to C567, after rebranding, I run factory reset. Then terrible things happened! When I tried to root again, I found Phone Locked and FRP lock.

Mate 9 still can log into system, but the system version became very weird, which is System 8.0.0.046(0EA7), it should be mha-al00c00b360!

I tried to login google account and logout, I found the OEM unlock in the developer options was still greyed out.

i tried E-recovery, it failed too, can not find the package!

I tried Hisuite, it can not recover the system too.

What should I do now, since FRP lock, I can not use twrp.
[Droid Maxx 2 Q&A, Help & Troubleshooting] rye2053:
I tried to flash the stock firmware through mfastboot, but it keeps failing. I assume it's because my bootloader isn't unlocked. I tried to unlock it through Motorola's website but it just told me that my device couldn't be unlocked. I need to flash this recovery and I don't know what to do!!! Someone please help me!!!
[Off-topic] Jose11290:
Removed by moderator.

You'll need to find another solution. Also, posting your imei number publicly is a bad idea.

Thread closed.
[Touch Cruise General] btsanev:
Hi,

Since today I have a new problem - when trying to start the camera by pressing the camera button or via rograms I got the message "Unable to initialize camera. Failed to set up the camera device."

I have the original ROM, nothing modified. Some days ago I was making pictures with the phone, worked well. I have not installed any programs since then.

Any ideas for workaround?

Also sorry if I'm repeating another thread, tried to search but found nothing.

Thanks,

Boyan
[Touch Cruise General] btsanev:
Guys, am I the only one who has experienced this???
[Touch Cruise General] hambola:
Yeah I haven't had this issue before. Have you tried a soft-reset? Maybe a backup of your ROM when the camera used to work? As a last resort, I hate to say it but you could always try a hard-reset?
[Touch Cruise General] tittula:
http://xdaforums.com/showthread.php?t=375474&highlight=CAMERA
[Touch Cruise General] rvgpoi:
I have the same problem

Exactly the same behaviour

when I try to start the camera I get an error box (rotated) with white square : " camera

impossible to initialize the camera.Failure of camera peripheral configuration"

it was working OK 10 days ago and I didn't change anything from this date except making a sprite backup.

Loading a 1 month backup didn't help neither a full hard reset (same behaviour just after the hard reset)

Looks like a harware failure, Ilook for a hardware test software for the camera ????

Trying to solve, I looked at the camera launching process, I've found a link like:

_camera.lnk

that contains:

21#"\Windows\Camera.exe" ?CameraRc_Grey.dll,-1106

any idea if that is normal content, looks curious for a link especially the interrogation point mark?

What about the -1106 figure ?

Is it possible that this link being corrupted ?

Otherwise, I phone to HTC technical support and the fact that the error stays just after a hard reset lead to think its a hardware failure; however loks teribly like a software pb....or a dry soldering point? They told me to bring the phone to a fixing office in Paris area delay announced to repair between 1 and 7 days

Any other help welcomed
[Touch Cruise General] btsanev:
problem disappear

hi rvgpoi,

the good news are that the problem disappear, the bad news are that I have no idea why...

I have not made hard reset (in fact, never), just couple of soft resets... but after that the camera was NOT working... couple of days later, i just wanted to show the problem to a friend of mine - and it was working...

I'm pretty pissed from HTC support - I have mailed them for this problem, and still no answer (1 week). This is not acceptable for a decent company.

In order to try to see where the problem is - can you tell me how to look at that:

_camera.lnk

that contains:

21#"\Windows\Camera.exe" ?CameraRc_Grey.dll,-1106

to see what is the value (while camera working)...

Good luck with your camera
[Touch Cruise General] htc4350:
Yes, same for me.

I am using Start->Program --> Camera.

I think that we should wait HTC support center for this problem.
[Touch Cruise General] Glassnerf:
Camera fails to initialize

Hello all,

I have the same problem exactly. I have the device for 6 weeks. Camera worked for two weeks. Stopped working for a week and then returned for a few days then failed again with the same message you guys got. I have done a number of hard resets- does not help. I am in a country with NO HTC service center and sending it to Europe will deprive me of my only phone for a long time. HTC Europe has NOT replied to my email from 3 weeks ago.

Any ideas? Rom update-if exists? Reinstall Rom? Any other ideas???

Jeremy
[Touch Cruise General] btsanev:
Solution, maybe

Guys,

my camera suddenly started to work again, I was extremly happy, activated GPS photo, took some pictures with coordinates, when i tried the camera later that day - it did not worked again. restarts, resets - nothing helped.

the next day I took out the battery for 10-15 minutes - and when I put it back, the camera worked!!!

Today the camera is not working again - and currently my battery is out. Let's see what will be the result.

Good hunting
[Touch Cruise General] Glassnerf:
Camera fails to initialize

I should have mentioned other problems that might be releavant- Bleutooth does not turn on from the momeent I purchased, touch pad is sometimes very slow for initial reaction. I have NO added programs beyond manafacturer originals.
[Touch Cruise General] alfredo.marchini:
Same problem...

Hi,

I'm a newbie, I didn't think that there was a so big and interesting forum about pdas and, especially, for my htc polaris...

I've got the same problem with the cam...

When I turn on the device, cam works fine...

After a while, it continue working...

After some hours, it stops working.

I have a full original firmware on it:

ROM: 1.25.408.1 12/12/2007

Radio: 1.58.21.23

Proto: 26.65.30.04H

I also tried to contact support, but with no responses, at the moment...

I also searched for a original upgrade (for the warranty), but nothing...

I think the problem is in apmd (or similar else) os daemon.

I think the os turn off cam device for power savings, and after it is not able to restart it before launch camera.exe program, that returns that strange message...

I searched in registry with ceregeditor if it is possible to disable power saving for a single device, to make a test, but I'm not a so good mobile engineer.

A newbie question:

The upgrade WM 6.1 bepe 0.67 can resolve this problem?

And again: if I upgrade anyway, I lose my warranty?
[Touch Cruise General] Glassnerf:
Camera fails to initialize

I called up the UK support center. After going over the problem with them I was told to return the device for servicing. Seems they will have to do a new Flash Rom. Two weeks without the device at least and I have to pay for international courier.
[Touch Cruise General] btsanev:
the problem still stays... this time removing the battery didn't help.So I'm again camera-less. Still no reply from HTC.

I'm also with original firmware:

ROM: 1.25.405.1 12/12/2007

Radio: 1.58.21.23

Proto: 26.65.30.04H

as you see the rom is different, same problem. In my case turning off the device does not help - the camera is not working even after switching it back on.
[Touch Cruise General] alfredo.marchini:
Are you able to deactivate power savings for cam?
[Touch Cruise General] alfredo.marchini:
Another think:

Your rom version is older than mine,

Perhaps a new rom version resolve the problem,

but is not original version, and we should ask to cooked new rom developer if they have found something wrong in cam device apmd functions...
[Touch Cruise General] w000ter:
I have the same problem, but for my TC it is simply resolved by doing a soft-reset and starting the camera after it's ready..

still annoying though.. :p
[Touch Cruise General] aleph305:
same problem here,

sometimes cam will work but it to often will not. :/

sure ift the cam even dont in factory default config (hard reset) it is broken.

I got longest working duration in factory default, approx one to two weeks.

using third party binaries the failure appears randomly.

Im pretty sure this is a software issue, else a soft rest wont fix it, eh ?!

workaround:

one but very poor solution is, once the cam starts, _never_ quit it, just minimize.

yep, I know ... but the only way I found atm.

// update //

approx one day without any probs and I used nearly every feature of my device....

Im not familiar with the CCD chip technology, I dont know if there is any possibility for burn-in effects, therefore I switched to the front cam for "stand by" and got the good old failed to ini ... error immediately when I tried to switch back to the rear cam.

now I will test if the front cam is got the same error ...

and I'll get some info if 24/7 on can harm the ccd chip

// update //

I have my cam now approx one week always on and have no problems at all.
[Touch Cruise General] alfredo.marchini:
I have got no news about cam.

I called htc support, they told me to install a fix for camera that I found in htc e-club.

But that fix is not for our problems, is for camera quality.

I installed it but the problem still remain.

Sometimes it goes, sometimes no...
[Touch Cruise General] boldbull:
try that :

http://xdaforums.com/showthread.php?t=391455
[Touch Cruise General] alfredo.marchini:
don't work

The sd memory isn't a solution,

because I have 1985MB free of 2GB.

If you soft-reset and don't work again,

Take the pda off without the battery for some minutes.

The cam will works again,

but after some time goes down again!!!

:confused::confused::confused:
[Touch Cruise General] grgomes:
don´t work either.

I also have been experiencing this issue for a month already.

Started with the "unable to initialize" problem, then I:

- soft-reset few times, no deal

- took off the battery one full day, no deal

- Formatted the SC, no deal. My exe file wouldn´t give any reaction.

- hard-reset, no deal. "unable to initialize" problem came back.

- tried all fixes and Camera versions (including Nadavi), no deal.

Called the support and they told me to send back to servicing. The problem is that I live in Brazil and would have to post it to UK. not that easy...

The cam is still dead and my hopes are vanishing away...

Hey glassnerf, did you have to post it internationally too? Where are you at?