yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] pintasmapila:
Well...yes. :)
[Nextbit Robin] cell2011:
Experimental or nightly which one for more smoother snappier so far?

---------- Post added at 08:38 PM ---------- Previous post was at 08:35 PM ----------

Experimental or nightly for snappier and smoother?

---------- Post added at 08:51 PM ---------- Previous post was at 08:38 PM ----------

Experimental or nightly which one is snappier and smoother?
[Nextbit Robin] MP9c:
Per lineageos.org/Update-and-Build-Prep/
[Nextbit Robin] cell2011:
Experimental is fast really nice. How is nightly anyone? Update!!! Experimental fly's over nightly I think. If it wasn't for the watermark I'd run it daily
[Nextbit Robin] pintasmapila:
Watermark? Can you take a screenshot?

Experimental is for people who are trying to update over CM14.1 Nightly is meant for a clean install.
[Nextbit Robin] cell2011:
I think it was 1/22 build of experimental after i flashed 1/23 nightly over i cant get back to 1/22 exper
[Nextbit Robin] jimmyzyx:
Tried to update to 1/24 as it was available over OTA updater this morning. But it rebooted to TWRP and no further action was taken. I wasn't able to manually locate the new 1/24 zip file either. Tried to reboot back to system, but booted back into recovery. Now it is in a recovery boot loop unable to boot into System. Someone please help as this is my daily driver.
[Nextbit Robin] pintasmapila:
I was afraid this would happen. We need LineageOS recovery fpr OTA updates, but it wasn't released yet. Maybe CM recovery can fix your problem. Not CWM! Or maybe you can dirty flash 1/24 from TWRP when its available for download.
[Nextbit Robin] jimmyzyx:
Thanks for your quick response! Problem right now is that it won't boot back to OS. I tried dirty flashing 1/23 zip (which i thankfully still had from the last dirty flash), and after reboot it went back to TWRP. I have a feeling I have to do a System wipe and do a clean flash of the 1/23... but I really don't want to have to set everything up again (risking that possibility that even wiping system might not work).
[Nextbit Robin] jimmyzyx:
Same problem here. Were you able to get it to boot back to system?
[Nextbit Robin] pintasmapila:
I've just dirty-flashed it (1/24) over 1/23 and it went fine.

It stuttered after boot for a while, but it's fine now. Need to try fingerprint reader a bit more. For now, its working just fine.

I flashed it over 1/23 with twrp, normal install and cleaned dalvik cache after flash, and just rebooted.

NOTE: OTA updates will clearly not work from TWRP. It didn't work from Cyanogenmod and it will not work from LineageOS. CM needed CM recovery. Maybe it will do for now, but it's much safer to just (dirty) flash from TWRP without updating OTA.
[Nextbit Robin] jimmyzyx:
tlxxxsracer and I are having the same issue... Just wondering where you located the 1/24 zip? I downloaded it with the OTA updater but I can't locate it in the internal storage. Since I'm not able to boot back into the system, I have no other way of loading 1/24 to the storage..
[Nextbit Robin] pintasmapila:
The OTA you downloaded isn't the same as the rom downloaded from https://download.lineageos.org/ether

Download this rom and dirty-flash it:

https://mirrorbits.lineageos.org/full/ether/20170124/lineage-14.1-20170124-nightly-ether-signed.zip
[Nextbit Robin] jimmyzyx:
Just tried it, and still boot looping to TWRP...
[Nextbit Robin] pintasmapila:
That is weird.
[Nextbit Robin] dbearsfootball:
It happened to me too. The only way I was able to fix this was flash cm recovery and it boots and then reflash TWRP hopes this helps guys. I'm sticking to omnirom for now till some of these bugs get sorted out. Otherwise great job so far.
[Nextbit Robin] jimmyzyx:
Can you link the CM recovery you flashed? as well was it flashed with TWRP?
[Nextbit Robin] dbearsfootball:
https://download.cyanogenmod.org/?device=ether

I just used the latest nightly one and I flashed it using fastboot. You can try TWRP I don't what it will do though.
[Nextbit Robin] cell2011:
Anyone experience on the 1/23 nightly screen does not timeout unless you turn off or double to sleep? I have it timed out for 30 secs. Doesnt go to sleep
[Nextbit Robin] adityaksharma:
it says bootloader locked.. urgh for me. lol
[Nextbit Robin] cell2011:
I tried to download 1/24 from my phone. Unsuccessful
[Nextbit Robin] pintasmapila:
I had some issues downloading big files, but i noticed that if you keep the screen on, it downloads perfectly. Try it.
[Nextbit Robin] carguy303:
Interesting thing for me, the toggle for "enhancing" the screen, makes everything look worse to my eyes. Other than that, it works great
[Nextbit Robin] pintasmapila:
Ok, i'm in 1/24 and i've found that Wi-fi only downloads big files only if the screen remains on (happens in AOKP and OMNI); the fingerprint reader is weird (as AOKP and OMNI), sometimes it works, sometimes it doesn't; today my phone rebooted with no apparent reason, and my Titanium Backup isn't opening anymore.
[Nextbit Robin] zibo29:
24/1 so far

Updated by dirty flashing from TWRP the latest build downloaded and rooted again with SU. So far not so much difference with the old build, stable so far, kind of fast. Weird problem with fingerprint reader that sometimes remain active also in homescreen but, as already sad, it's a problem common to all the 7.1 roms as of today. GPS is working normally, and it remains my daily driver.

General question, if i flash the Google Camera app with opengapps will I have HDR (HDR+ will remain a dream, but doesnt' it share the same HW with the nexus 5x that has it)? Because the stock LineageOS doesn't have this feature and I think it's quite useful
[Nextbit Robin] bmac6996:
I flashed google camera using omni 7.11 ROM and it doesn't give me the option for HDR. Probably hardware dependent. The fact that it works much quicker than stock or Snapdragon's is good enough. That shutter lag is unbearable.
[Nextbit Robin] zibo29:
Thanks! You've flashed it from open gapps?

Kind of bug. I've also flashed the stock Google clock, it wasn't opening so I've recovered the apk from the ROM, now it shows as an update on the play store but it's not updating (error 505) - kind of an old bug from Cm 12

Any idea how to fix it?
[Nextbit Robin] bmac6996:
Nah, I just downloaded the apk separately.

Regarding the bug, no idea.
[Nextbit Robin] zibo29:
Thanks! Can you link it to me?
[Nextbit Robin] jimmyzyx:
When i flashed SU 2.71 on the 1/24 nightly, it disconnects my camera (and snapchat). Anyone else have this issue?

---------- Post added at 05:02 PM ---------- Previous post was at 04:30 PM ----------

Cellular data also doesn't work.. anyone else?
[Nextbit Robin] zibo29:
Mine is working perfectly but I have SuperUser 2.79beta, don't know if they're related
[Nextbit Robin] zibo29:
Strange bugs with bad cellular signal on 24/01: apps start opening in landscape (also if u lock the rotation)

Battery still looks ok

No other new bugs
[Nextbit Robin] picaso86:
Anyone experience any lag with this version?
[Nextbit Robin] gparmar76:
Can someone help me get past the setup screen? I flashed new nightly and latest open gapps (1/27/17) and at tap and go it doesn't let me go past to the next screen...very strange.
[Nextbit Robin] zibo29:
It's a problem in the Gapps but if u have the patience to continuously go back and forth to and from the previous screen and sometime you will get a skip button

---------- Post added at 10:48 AM ---------- Previous post was at 10:45 AM ----------

It's a problem in the Gapps but if u have the patience to continuously go back and forth to and from the previous screen and sometime you will get a skip button

Or you can just flash the ROM and set it up, and only after that go back to recovery to flash Gapps
[Nextbit Robin] gparmar76:
I kept trying and couldn't get past...So I reflashed just the ROM and then Gapps separately...That did it.
[Nextbit Robin] XxXPachaXxX:
It's an issue in open gapps, not ready for lineage. Use the aroma version and check the "remove cm initial setup" option during installation.
[Nextbit Robin] Franzferdinan51:
Yes I'm having lag issues along with signal issues on T-Mobile it'll say I have no signal in places where I know I have full bars
[Nextbit Robin] bmac6996:
Can anyone speak to the bluetooth and GPS? Can bluetooth stream without any interruption like it sounds like it's having dropout issues?

GPS can track accurately?

Thanks
[Nextbit Robin] ld626:
today's update

Today's update bricked my phone, nothing would get pass TWRP, flashed stock image, back to square 1, it sucks to be me right now, have to stay awake to fix my phone
[Nextbit Robin] pintasmapila:
Install official rom 1450, do a clean flash with lineage, and don't update ota again until they release a Lineage Recovery
[Nextbit Robin] ld626:
Did that and try other Roms too and nothing gets pass TWRP, my method was: flash TWRP, enable mtp and load su file and flash to decrypt, then load ROM and Gapps and flash it, now I will try root first then install TWRP via oficial app but before that I got a day of work ahead.
[Nextbit Robin] zibo29:
Just flashed the 01/31, no problem with TWRP - report bugs or improvements later
[Nextbit Robin] michael.dice:
Download location?

I did an OTA download and then it booted into TWRP, but I can't find the download to install. Any help?
[Nextbit Robin] pintasmapila:
Keep in mind that the file you downloaded from OTA is not the same as the file you download from their servers.

Download the rom from lineageos; Install stock; unlock the bootloader/decrypt if necessary; install twrp; copy rom to phone; flash rom, SU, Gapps (latest OpenGapps work fine), TitaniumBackup, etc......

Next time (until LineageOS doesn't release a new recovery), download the rom from LineageOS and flash directly through TWRP.
[Nextbit Robin] XxXPachaXxX:
A workaround: boot in fastboot mode, take the boot.img from the rom, boot using "fastboot boot boot.img", the phone boots up normally and no more boots to twrp.
[Nextbit Robin] zibo29:
BEWARE: download from the lineage os site, if you will flash the file downloaded from OTA you will encounter problem, so just download from lineage site, boot into twrp, flash (if u want also superSU), wipe cache, dalvik - it will take more minutes at first boot (or reboot itself 2 times) and you're ready to go!
[Nextbit Robin] ld626:
Like I said did that, in fact install the 1450 rom twice, went back and did the whole process again including downloading all the files again and also tried 2 other roms and now it doesn't get passed TWRP, I am back on the stock rom, maybe later today will try again.

---------- Post added at 06:59 PM ---------- Previous post was at 06:56 PM ----------

can you please be more specific, sorry Im not very good at this...so take the boot.img file put in the same folder as fastboot folder, open comand and type "fastboot boot boot.img"? just like flashing recovery?
[Nextbit Robin] zibo29:
I think that you should try to bypass the TWRP so with the phone connected to a pc with working ADB

"adb reboot-bootloader" then press enter and you should be in bootloader now (you should achieve the same with the menu option available when you first boot a modified nextbit, selectable with volume buttons) - to check that everything is fine write "fastboot devices" and see if your device is recognized and proceed with "fastboot flash boot boot.img" [the boot.img should be in the fastboot folder or in "C:\android\platform-tools" or if u are using a mac just write fastboot flash boot [and then drag the boot img from any location next to the "boot" word and you'll get the same] - and then wait until the end "fastboot reboot" and you should be fine

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

To conclude, this is a way to get rid of the TWRP and get back to stock [you are flashing the stock boot.img] then from there you should try to proceed as sad in the upper post downloading the lineage os and continuing as described in many guides
[Nextbit Robin] ld626:
FINALLY!! Thanks for the help guys, after many tries, back and forth in TWRP I was able to get it back on Lineage OS, I was fine with stock till I tried Lineage, now stock sucks imo, not updating anything for a while now...
[Nextbit Robin] zibo29:
UPDATE on the build 30/01

Random reboots with bad cellular signal

GPS is barely usable (the GPS fix itself takes for ever and out in the wild is almost unusable as navigation device)

The fingerprint reader refuse to work properly (slow sometime to turn on when you turn on the lockscreen and it remains on passed the lockscreen)

The OS itself is definitely usable as it is my daily driver and I would like to stick with LineageOS for future updates as the community grows but thinking now to give a try to OmniRom (also if the community is smaller) or get back to stock when final Nougat willbe available - I will give to LineageOS still two build to impress me
[Nextbit Robin] pintasmapila:
That's generous. :)
[Nextbit Robin] ToHellWithGA:
That's ridiculous. If they're reasonable Lineage OS developers won't release a recovery for each device, but instead will work with TWRP developers to ensure Lineage OS updates work properly with TWRP. CM recovery was a bad joke, a relic of Cyanogen OS needing a stock recovery. After several of us had the same TWRP loop problem on ether on the nightly build from the 30th, a new TWRP was released to fix the glitch.

Edit: the last freeze and reboot ate my wallpaper and reverted me to the default teal, black, and red wallpaper. I don't mind the performance being sluggish since the battery life is good - probably a result of using only the 32 bit cores at low power - but the reboots are a drag.
[Nextbit Robin] pintasmapila:
Any news on the latest release?
[Nextbit Robin] jimmyzyx:
Works well, no issues.
[Nextbit Robin] netxph:
I lost adb/fastboot when I installed LineageOS has anyone have this problem?
[Nextbit Robin] :
I'm liking the 06 Feb build, it seems that the A57's are still inactive however, occasional jitters but nothing I cannot live with while things are ironed out. Thanks muchly for the great work.
[Nextbit Robin] zibo29:
Feb. 06 build is quite stable, still random reboots (1/2 per day) but the GPS is really unreliable as now and that's a deal breaker for me
[Nextbit Robin] Bertusone:
I have the same issue. I can not play any games. all stuttering and laggy.
[Nextbit Robin] pintasmapila:
Well, Lineage has released a new build today with lots of changes apparently. Maybe it solved these issues.

Here's the changelog: https://www.cmxlog.com/14.1/ether/#next_build

Just don't try to update OTA. ;)
[Nextbit Robin] :
Most of this patch insert in this changelog are for common, there's no specific patch for nextbit, atm the best rom for this device is the new Omnirom with new device tree and kernel made for scratch. Atm LineageOS has some problem related to panel
[Nextbit Robin] pintasmapila:
Yes, Galdalf has been an amazing supporter. Omni is very well balanced. My favorite so far.
[Nextbit Robin] jimmyzyx:
What about Slim7? what do you guys think of that?
[Nextbit Robin] VenomMOD:
Guys this thread is for lineage. Not slim nor omni.
[Nextbit Robin] DuelistRaj:
It looks like the 2x A-57 cores are running. I downloaded kernel adiutor and there it shows the two cores to be active. To confirm this, I downloaded L Speed and there too I found all the 6 cores to be up and running. It looks like CPU-Z is unable to detect it. Same goes for the sensors CPU-Z always shows a few sensors which aren't even there on the device when compared to viewing the sensors from the dialer app.
[Nextbit Robin] :
Ah, fair enough. I incorrectly assumed that was the reason for the jitters. :good:
[Nextbit Robin] Saythis:
Try using AIDA64
[Nextbit Robin] socali:
[MENTION=5930634]DuelistRaj[/MENTION] Can you please run Octane benchmark on latest chrome and see what score you get? http://chromium.github.io/octane/

I'm wondering if you'll get about 7000 like I'm getting on cm13 or about 2500 like I got on earlier cm14.1/los14.1 builds.
[Nextbit Robin] DuelistRaj:
Actually I was using LineageOS for a few weeks. I came across some benchmarks which suggests Omni is better. So I switched. Currently, I'm running the latest nightly of official Omni ROM. The Octance benchmark score on the Omni ROM is 7821.

I have attached a benchmark screenshot. Use that to roughly assume the Octane score.:) Or you can wait for someone else to do it. Kudos!
[Nextbit Robin] jimmyzyx:
Good to see people using my benchmarking logs haha :D

Happy to produce more if more people find it useful.
[Nextbit Robin] DuelistRaj:
Yes, thanks to you. I was about to flash cdroid ROM but seeing your benchmarks I changed my mind. :good:
[Nextbit Robin] jimmyzyx:
I've tried all the ROMs for this phone in the process of creating those benchmarks. From memory, crdroid is a good ROM packed with lots of features, but just cannot keep up with the performance and battery life of Omni. I posted in another thread earlier today but currently running the 0216HOMEMADE build of Omni with Electron Kernel v2, the benchmark and battery life is insane.

Also please mention/tag me in the future when referencing my benchmarks as I don't want the wrong information being communicated. Thanks
[Nextbit Robin] DuelistRaj:
Sorry for not tagging you. Honestly, it slipped out of my mind.:p Cdroid indeed is packed with features that's why I wanted to flash it. But as I said the benchmarks changed my mind.

Talking about the Omni homemade build I wanted to know whether you did clean or dirty flash? Moreover, can you provide a link to the electron kernel v2 I would like to try it myself.:)
[Nextbit Robin] jimmyzyx:
Not a problem brother. When performance is not noticeable, I would go with the one with better features too, but all other ROMs other than Omni shows noticeable lags and glitches that affects daily use and that doesn't stand in my books regardless of all its features... but we can always hope for their devs to continue working to get it to a good stage. This is always the case: If you're going from one ROM to another, always CLEAN FLASH. Even if it's going from Official version to an Unofficial version or to Homemade version. Electron kernel is currently the only custom kernel for the 7.1.1 version of our phone developed and maintained by [MENTION=4468902]Saythis[/MENTION], and is not yet released. I am testing it for him. He is however extremely nice and will most likely allow you to test if you PM him. I can confirm that the kernel is very stable from my weeks of use.
[Nextbit Robin] ChackoM:
Really want to try this kernel out. To flash a custom kernel, just to make sure, is flash the homemade build, then the kernel.zip, then gapps correct through TWRP?

EDIT: Also just curious, any noticeable differences between the official and the homemade with the custom kernel?
[Nextbit Robin] jimmyzyx:
Rom->gapps->kernel
[Nextbit Robin] ChackoM:
Man you're a lifesaver! On official one now, do you think the custom kernel with homemade is a lot better than official that I should flash it?
[Nextbit Robin] Saythis:
I'm not the actual maintainer for Electron Kernel, I'm more just working with [MENTION=5051294]frap129[/MENTION] to ensure it's compatibility with the Robin as new features are committed until it's official release. As the current test build is about at it's end, I'm not looking to add anymore testers for feedback until the next build. However, being that this thread is meant for development on LineageOS for the Nextbit Robin I'd appreciate it out of respect if the topic remained toward that however. Thanks! There's good things in the future for the Robin for those who are patient :)
[Nextbit Robin] jimmyzyx:
Not enough for you to switch as an average user.

---------- Post added at 03:57 AM ---------- Previous post was at 03:56 AM ----------

Agreed. This converations should be moved to the Omni thread if you guys are interested.
[Nextbit Robin] XxXPachaXxX:
How is going here? Are fingerprint and performance issues still present?
[Nextbit Robin] tweaked:
I been using the lastest release and the one before it for about a week + and I have noticed nothing beyond the normal. It grabs my print about as often as the stock did.

I have seen no performance issues but I don't like crappy android games so don't play them. It runs solid using it for email, web, and phone. I Have had a random reboot on the lastest twice. But I haven't chased it down to the ROM yet and blame my use.
[Nextbit Robin] RaiderX303:
Running good here so far, only issue i've noticed is performance seems to be a bit below what it should. Antutu only manages 43000 when reviews seem to put stock around 61000

Edit: Run the octane benchmark listed a couple pages back and got 2368

Edit2: Restored to stock and run again, got 4813
[Nextbit Robin] XxXPachaXxX:
Tried it. Big performance issues and no fingerprint fix yet.
[Nextbit Robin] Nintonito:
Has a fix for the inactive A57 cores been proposed/merged? That and the fingerprint issues are the only thing keeping me from trying this.
[Nextbit Robin] chent7:
Nope, still has fingerprint issues on march 21 build
[Nextbit Robin] VenomMOD:
On the build of March 21st, it prompts me to enter a pin when I don't have one, then crashes when I input anything. Now I can't have a fingerprint/secure lockscreen set up because of this issue. Perhaps a reflash will help?
[Nextbit Robin] Saythis:
You failed to follow the steps. Wipe/Format data in TWRP and keep in mind this will wipe your internal storage.
[Nextbit Robin] VenomMOD:
That's exactly what I did before flashing.
[Nextbit Robin] Saythis:
You have to do it after flashing as well if your data partition becomes encrypted. I'd sideload magisk or SuperSu then wipe data. If you have anything to backup I'd do it before anything.
[Nextbit Robin] carlosjcar:
Has Razr released the source for nougat? Now that they released Nougat 7.0 and theres Beta 7.1 Out. That could help with those issues. I got the Beta and is simple awesome it pretty much ready.
[Nextbit Robin] VenomMOD:
It was released not too long ago, I posted a link for the nougat kernel source in the thread. The OP wasn't updated for it, but the Razer forums had the source.
[Nextbit Robin] VenomMOD:
Latest nightly boot for anyone?

EDIT: Robin doesn't boot on the April 10th nightly, it goes into fastboot mode.
[Nextbit Robin] widdershins:
Confirming it definitely gets stuck in fastboot, this also happened to me. If you don't want to waste time fixing it again, skip this one.
[Nextbit Robin] crpalmer:
I have temporarily removed ether from the weekly builds because there are too many problems with it.

On a positive note, we have done some major work on the device tree and are rebasing our kernel on the 7.0 kernel release. When this rebase/refresh is complete, the builds will be started again.

If you build your own builds, the branch cm-14.1-new on my personal github should be working if you want to see how it is coming along.
[Nextbit Robin] ouankou:
Thanks for the update and hard work! Just return the build on Apr 4th and wait for the new rebased one.
[Nextbit Robin] Nintonito:
Does this rebase fix the issues with bringing A57 cores online and the fingerprint not working?
[Nextbit Robin] crpalmer:
I'm not sure what the "issues with bringing A57 cores online" are. I never really ran the official builds or stock, I just went straight to working on rebasing it on the 7.0 release. All 6 cores are online and being used by the system, if that's what was not working right before.

Fingerprint sensor is working well for me.
[Nextbit Robin] Nintonito:
If all 6 cores are online then the issue is fixed. Basically, LOS 14 based on 6.0 kernel source cannot use the A57's. I.e they become completely disabled (if you scroll through this thread's comments or the defunct CM14 thread, you'd see users complaining of dramatically reduced device performance.). This issue was ignored until this rebase inadvertently fixed it.
[Nextbit Robin] SkandaH:
Official builds are temporarily disabled by maintainers until major bugs are addressed.

https://www.lineageos.org/Last-2-Weeks-in-LineageOS-7/
[Nextbit Robin] bmac6996:
Sad, but had to be done. The quality control of it wasn't getting any better. Hopefully the bugs can be figured out.