yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] thotwielder:
I have flashed twrp 3.2.1 via odin 3.12.3, but why I didn't see twrp interface when I boot into recovery? It says something like this:

Android Recovery

MMB29M.G900FXXU1CRA2

samsung/kltexx/klte

6.0.1/MMB29M/G900FXXU1CRA2

user/release-keys

Use volume up/down and power

Reboot system now

Reboot to bootloader

Apply update from ADB

Apply update from SD card

....

...

Power off

Based on what i have seen on youtube, it's not the twrp interface? It's G900F, un-rooted, not sure other status.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] thotwielder:
ok, after rooting, and re flash twrp, it now boots into twrp.
[8125, K-JAM, P4300, MDA Vario General] theoneeye:
I have GENPP and POCKET SNES on my K jam but they run too slow. Are there any emulators out there that run at a good speed on my phone?
[8125, K-JAM, P4300, MDA Vario General] decknologist:
For information on SNES emulators have a look here http://xdaforums.com/showthread.php?t=306444&highlight=snes

or for more general information here http://xdaforums.com/showthread.php?t=307165&highlight=snes
[8125, K-JAM, P4300, MDA Vario General] xtr3m3:
Try MorphGear..
[8125, K-JAM, P4300, MDA Vario General] nothin:
try changing device... ;s

or turn sound off(its rather MUST on wizard...).

and use frameskip =>3..

and forget about morphgear..

here's fastest snes emu so far for wiz..

http://www.modaco.com/content/Smartphone-Software-Games/237589/PocketSNES-1-53/

picodrive is fastest megadrive emu..
[Samsung Galaxy S7 Edge Questions and Answers] kingshine2017:
Hello everybody, seriously i think I broke my phone but i did it to learn a bit, basically what happened, I installed TWRP Recovery and routed my phone everything gone well. after i have seen a guy talking about ROMs And stuff. I go Samsung Galaxy s7 edge SM-G935F Exynos. I tried to install The ROm via TRWP like everyone do, i followed all steps. on this thread :

http://xdaforums.com/s7-edge/development/rom-bobcatrom-mm-6-0-1-t3404008

I installd this ROM : [ROM][SM-G935/930F]{~BoBCaTROM~}[v.1.0.4][APF2] ~MM 6.0.1~

after the phone stuck booting up and booting up again stuck on samsung logo and then turn off and boot up again, wont finish. after i tried to do the installation again. ive done it 4 times. but still stuck on booting. it made me crazy i thought if i wipe everything gonna work, i made it worse i wiped everything lol even the back up, and the ROM. Im newbie, so maybe i will learn from that. could someone tell me, if i can make the phone like it was ? and how about the efs is it important, how can get it back ? and can i install other ROMs, or thats it im stuck on the original Firmware. thank you.
[Samsung Galaxy S7 Edge Questions and Answers] malek777:
Just use Odin to flash a stock rom.
[Samsung Galaxy S7 Edge Questions and Answers] dave7802:
Install stock via Odin and try again.

If at first you do not succeeded, try and try again.

Out of interest, When you installed the ROM, how long did you wait before restarting the device.

(How long did you leave it on the Samsung Startup logo)

I know Stock modded ROMS when first install can sometimes take upto 10 - 15 minutes to Boot for the first time.

(I remember waiting 20 minutes one time on my note 3)
[Samsung Galaxy S7 Edge Questions and Answers] dannybee1:
Delete
[Samsung Galaxy S7 Edge Questions and Answers] kingshine2017:
Thank you

My phone come back to normal thank you very much guys
[Samsung Galaxy S7 Edge Questions and Answers] GuestD0608:
The way to fix this is pretty straight forward and there are many tutorials online on how to do this.

You will need your stock rom (can be acquired from SamMobile) and Odin (i recommend using 3.0.7) and then plugging your device in to your windows computer (does not work on any other os) and reflashing back to your stock rom. This will 100% work and you should just go to YouTube and search for "How to reflash stock Galaxy S7" after downloading your stock rom.
[Samsung Galaxy S7 Edge Questions and Answers] jcpineda:
i have a question, how do i know what firmware to get

i mean there are a lot of them from different countries and different pda csc numbers

do i have to choose one that matches my base band or something like that?
[Samsung Galaxy S7 Edge Questions and Answers] GuestD0608:
You must choose the firmware that is correct for your model for example if I had a Galaxy S7 and the model number for it is SM-G9358 i'd then choose the one that says its for the SM-G9358 as well as my carrier for example Optus if there is no correct carrier version then just choose one that is from your country it wont make a huge difference you'll be fine.

If you do not know how to find the model number for your phone it should be somewhere in Settings>About or when you are booting on your device.

Let me know if you need any further assistance.
[XDA Assist] :
Greetings,

Thank you for using XDA Assist.

First, you'll need to create an account so you can post in the other sections.

After you have done that, you can post your questions and ask the experts here:

http://xdaforums.com/android/help

You're sure to receive quality answers there.

Good luck and welcome to XDA!
[Huawei GX8] matangii:
Anyone have this device and have successfully installed stock marshmallow or cyanogen? Would like to know if there are any major issues before flashing. ;)
[Huawei GX8] sirgroh:
i have rio-l01 udated last night. no issue at all. check ur custom version if it matches with update go for it build number is not an issue.
[Huawei GX8] lavib:
When this device model (rio l02 b130) should get mm update ?

Title
[MTCB Android Head Units Q&A] mr-mo7ammad:
Is this rom only for screens from Joying company or is it ok to have it in any other screens company ?

my car 's system is mtcp ksp, can I installed this rom?

if any one can explain this briefly i would really appreciate that.

the second thing is

i have another screen 5.1.1 i wolud like to have Launcher like this :

http://dl-1.va.us.xda-developers.com...&ts=1468972793
[MTCB Android Head Units Q&A] Marmalux:
If you could read the wiki you will have all your answers.

Here's some hints :

When flashing a rom the only thing you need to know is : The type (MTCB, MTCC, MTCD...), processor (Rk 3066 or Rk 3188) and screen resolution (800x480 or 1024x600). Regardind the MCU, just don't touch it (there is no custom MCU yet). Flashing a MCU is the best way to brick your device.

The launcher is actualy a app. Just search Google play and install what ever launcher you want.
[Nextbit Robin] Gandalf:
OmniROM
​

#include <std_disclaimer.h>
/*
* 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. Hard. A lot.
*/

Introduction

Installation instructions

Downloads

Changelog

Source

XDA:DevDB Information

Omni for Nextbit Robin, ROM for the Nextbit Robin

Contributors

Gandalf

ROM OS Version: 8.x Oreo

ROM Kernel: Linux 3.10.x

ROM Firmware Required: Lastest Bootloader (unlocked) and partitions from most recent factory image

Based On: AOSP

Version Information

Status: Stable

Created 2016-07-22

Last Updated 2018-06-19
[Nextbit Robin] Gandalf:
Reserved
[Nextbit Robin] Nextbit_Khang:
I can't wait to test this out!
[Nextbit Robin] laidbackcloud:
Will give this a try as soon as i get my replacement phone. Will this become official?
[Nextbit Robin] Nextbit_Khang:
It is official, just an alpha build at the moment.
[Nextbit Robin] freddd1:
Everything works fine as far as I can tell. Only DSP Manager crashes when I try to open it.

Looking forward to seeing this getting picked up by the OmniROM official nightlies.
[Nextbit Robin] Gandalf:
Yea, I need to add the libraries to the audio_effects file that DSPManager relies on. I have been focusing on getting the ROM base up to android-7.0.0_r1 lately, and nothing can be done for any non-nexus devices until CAF releases its magic. At the present time, Omni's source yields successful builds, although untested.
[Nextbit Robin] agriculture:
Waiting ... Thanks great work op
[Nextbit Robin] Gandalf:
android-7.0 (sporting a brand new kernel!) is almost a go! Just a few minor bugs to iron out
[Nextbit Robin] :
Have you merged the latest nextbit kernel source ?
[Nextbit Robin] Gandalf:
Yes.
[Nextbit Robin] Gandalf:
Almost ready
[Nextbit Robin] sabresfan:
If you need a tester let me know. Thank you for working on this.
[Nextbit Robin] freddd1:
Your work is incredibly appreciated. Thank you so much!
[Nextbit Robin] Gandalf:
Mobile data should be working now..just need to fix wifi, bt, nfc

Wifi should no longer be a module by release
[Nextbit Robin] willyboi:
When you make the nougat update, will you make a new thread, or update this one?
[Nextbit Robin] Gandalf:
OP updated with a link to an android-7.0 test build (and, from what I can tell, the first Nougat build for Robin available ANYWHERE! :D)

DOWNLOAD HERE

You must flash the 1450 stock firmware to get the updated partitions on your device prior to flashing this.

I recommend using OpenGapps (package of your choosing)

What's still broken:

- Camera will force-close when you try to zoom in

- Camcorder is actually recording the "recording start" tone

- I think GPS is flaky (haven't tested it)

- Wifi Calling (it doesn't work on stock 1450 either)

- Probably some other stuff I haven't noticed yet

These are mainly minor annoyances that I will fix in the next day or so.

Notable changes:

- This is using my [new] kernel, not based on CyanogenMod's kernel whatsoever.

- The device tree is an ugly hybrid derived from the CyanogenMod tree. I will eventually roll into my own device tree when I have the energy to do so

- Wifi is no longer a module, but a built-in kernel driver (qcacld-2.0 wlan, like the Nexus 5X)

Kernel source

Device Tree

Omnirom Source
[Nextbit Robin] Mingventador:
Great! thanks. but it can't work camera. not only zoom. And crash DSP Manager.
[Nextbit Robin] sabresfan:
Great job. Very smooth. Will report anything I find.
[Nextbit Robin] valhallen.282:
Device is smooth. GPS works like a dream with gapps(will test without later). All accounts signed in no stutter or lag so far. Excellent work. Thank you for your time and patience!
[Nextbit Robin] Gandalf:
Official builds are going now with the January security bulletin merged
[Nextbit Robin] sykomaniac:
Time to move off of stock! What are you guys thinking with the theme engine?
[Nextbit Robin] wecameasjesse:
The built in equilizer app constantly force closes in the background when I play music from a Spotify. Had to disable it in the settings, but other than that flawless ROM.
[Nextbit Robin] Gandalf:
Supposedly themes work according to my Nexus 5x thread but I haven't tried any myself.

Can you get a logcat please?
[Nextbit Robin] wecameasjesse:
I would but i disabled the app to stop the error, and now that I've re enabled it i cannot recreate the error anymore.
[Nextbit Robin] Gandalf:
Force close Spotify and equalizer and then reboot with the app re-enabled.

update: first official build is posted @ https://dl.omnirom.org/ether

All future bug reports MUST include a logcat and dmesg, and steps to reproduce.
[Nextbit Robin] Akoolive:
This ROM require Gapps? If so can I be pointed to the right direction. Also do I need to take any additional steps before or after I flash ROM?
[Nextbit Robin] gr3y_:
I just installed using OpenGaps (ARM64) and it's looking good so far!
[Nextbit Robin] Akoolive:
Rom is stable thx dev

Anyone having issues receiving text messages? I'll get messages after a reboot then they stop.
[Nextbit Robin] Gandalf:
Texting works fine here, T-Mobile US and using both the AOSP and Google Messenger
[Nextbit Robin] Akoolive:
I'm on T-Mobile as well. I wiped everything, installed rom, gapps and latest SuperSU.
[Nextbit Robin] Akoolive:
Found the culprit. It was a root app that wasn't updated to android 7.1.1. The app was blocking all SMS incoming:confused:
[Nextbit Robin] ohad129:
Is it pre rooted this rom?
[Nextbit Robin] gr3y_:
My Wi-Fi MAC address has changed after flashing the rom; is there some kind of MAC address spoofing enabled?
[Nextbit Robin] GigahurtzUK:
Root

Doesn't appear to be but I prefer this to be honest. I have installed Magisk, PHH Superuser and Magisk Manager and all working fine.

With Magisk Autohide turned on the Safetynet API passes tests.

---------- Post added at 03:54 PM ---------- Previous post was at 03:52 PM ----------

Great ROM Gandalf. Thank you for your work.

Once again thanks for your time. Keep them Balrog's at bay.
[Nextbit Robin] fahrul:
Can I Change the fingerprint detecting method?

I always accidentally unlocking the phone when trying to lock the phone by pressing power button
[Nextbit Robin] ld626:
wow!!

WOW!! How did you guys manage to get this thing running so good and the latest 7.1.1 version??!! All the features, wifi calling on tmo, equalizer...and this phone is actually good!! minor flaws here and there but with all the support it's receiving it's a kepper!! thanks for this awesome rom!!

I got a question though, I don't use any root needed apps, should I root it(flash supersu)? keep boot unlocked?
[Nextbit Robin] fahrul:
Is Hotspot running well on ur device??
[Nextbit Robin] ld626:
nope, no hotspot here,
[Nextbit Robin] Gandalf:
everyone,

I have made an example JIRA ticket that EVERYONE should be following for bug reports, includes log(s) , and steps to reproduce, as well as:

1) assigned to me for the device

2) all relevant information is provided

http://jira.omnirom.org/browse/OMNI-1351

Thanks.
[Nextbit Robin] gr3y_:
My phone's WiFi adapter MAC address has changed flashing this ROM... Should I submit a bug report? Or is it a "feature"?
[Nextbit Robin] adeelmysore:
Finally got Directvnow to work. Rooted with magisk and phh and turn on magiskhide. Had to change build prop to release-keys from test-keys and all userdebug to user and more directvnow works.
[Nextbit Robin] Gandalf:
the method of obtaining the MAC address from the hardware is still from LineageOS (previously CM), but i am going to migrate this over to how stock does it. A different MAC address is most likely a side-effect of this, but I need to look into it.
[Nextbit Robin] shaggy5991:
Any ideas still getting cannot connect to camera after a fresh install of 1450 and new update
[Nextbit Robin] gr3y_:
Got it, thanks for the explanation :)

One last thing, I'm getting a lot of battery consumption listed under "Miscellaneous", is it normal or do I have something set up wrong? Battery life itself isn't bad, I get something like 30% less than with stock Nougat beta but to me it's more than enough; just wondering if there's something wrong on my end.

Thanks a lot for the time and effort you've put into this ROM, it's really great :)
[Nextbit Robin] Gandalf:
no, i need to fix this :rolleyes:

I need to look into this more.

camera works fine here.. and like i said just a few posts up, PROVIDE LOGS.
[Nextbit Robin] ohad129:
I got talon as my twitter and i got problem i cant open the link and i got force shutdown also from FB the same problem any solution??
[Nextbit Robin] Gandalf:
I'm just going to completely ignore any bug reports that don't HAVE LOGS
[Nextbit Robin] substanceneil:
I see a Jan 8th build posted on dl.omnirom.org/ether... excited to try it, although it's still Jan 7th where I am. Ok to dirty flash?
[Nextbit Robin] modernbummer:
Seriously, folks. Respect the developer's time and READ. In my opinion, this is the best ROM available for this device. I would hate for Gandalf to get burned out by reported "bugs" without the documentation he needs to fix them. If you don't know how to report it correctly, do some research. Thank you.

---------- Post added at 03:51 AM ---------- Previous post was at 03:49 AM ----------

Clean flash is always the recommended procedure. Most devs will tell you not to report bugs if you've dirty flashed.
[Nextbit Robin] Gandalf:
If it's on the OmniROM website you can just use the OTA updater and it updates automatically. No need to wipe anything.

The server is in Germany, weeklies build at 00:00 every Sunday UTC+6
[Nextbit Robin] sykomaniac:
Just a thought but could the misc drain be due to the fingerprint sensor? On stock builds it's disabled when the screen is off to conserve battery.

Hi idea if this could be a cause just throwing out suggestions
[Nextbit Robin] CertifiedBlyndGuy:
[MENTION=3878813]Gandalf[/MENTION] I plan to pick up this device soon to use with Omni. I am a kernel developer with a bit of experience under my belt, and recently, I did a massive overhaul to Franco's driver for Hammerhead. I made VADC support and TSENS optional for whatever sensor is best used on a device, I made it to where it can shut down cores, even more specifically, clusters. This may been incredibly useful on the Robin though I am stuck on a OnePlus X so I can not test. I was just wondering if out of curiosity, you could for yourself, and get back to me. I can create the PR with everything needed. I just need you or anyone to test. It could be really beneficial on the Robin. Here is the driver I wrote if you would like a closer look:

https://github.com/CertifiedBlyndGu...a7e42bbc5aca706/drivers/thermal/msm_thermal.c

You may need to add power efficient worqueue's into the kernel if they are not there already. If not, just replace the PEWQ call with thermal_wq (a generic worqueue struct until later in the driver).

I might just upload a test build for everyone here and see how it goes
[Nextbit Robin] Gandalf:
Sounds good. Just submit a patch to gerrit and I'll check it out. Thanks.

The kernel right now is simply NBQ source diffchunked onto CAF 8x92 kernel tag.
[Nextbit Robin] CertifiedBlyndGuy:
Will do :)
[Nextbit Robin] adeelmysore:
I agree with this, fingerprint unlock is very erratic with the ROM. Didn't think it was a feature. I like how stock does not read your fingerprint unless you press the power button and wake up the phone.
[Nextbit Robin] Gandalf:
I'll change it for the next build
[Nextbit Robin] GigahurtzUK:
Sign of a great Dev. Listens and responds.
[Nextbit Robin] valhallen.282:
Erm maybe it could be a switcher? I rather like the tap to unlock. It's quite useful. Device unlocks coming out of my pocket before I look at it. Pressing the button is for me an unnecessary step. Main reason why I loved the custom ROM. Or maybe I'll find another way to flip that switch.
[Nextbit Robin] Gandalf:
yea, I am going to leave it as-is for now and make it a toggle in Settings. Good idea :highfive:
[Nextbit Robin] FlamieFox:
Agree, tap to unlock is very nice.

Main and only problem I have with it is that when I lock the device with the power button if I don't lift it up fast enough it'll turn on again. Could a very small timer be implemented just after the screen goes off before the sensor turns on? Like ,25 seconds

Best custom rom dev for this phone ?
[Nextbit Robin] voilamos:
[MENTION=3878813]Gandalf[/MENTION] There's a bit of delay when one tries to unlock the screen. In the sense, it takes a second or two for the screen to turn on when the power button is pressed. It'd be great if you could look into that too.

Cheers!
[Nextbit Robin] gr3y_:
I think that's due to Doze, I've seen it in all phones with a Nougat rom... I could be wrong though.
[Nextbit Robin] picaso86:
I tried to Root by flashing the SUPERSU zip and nothing happened. Also, I can't rearrange the navigation buttons. Any ideas?
[Nextbit Robin] Gandalf:
i haven't rooted in ages, can't be much help here.

we don't have the option to rearrange navbar (yet)

update: since this is mostly stable minus a few minor things here and there, I have begun rewriting the entire device configuration from scratch to go with my kernel

Update 2: new tree is coming along nicely. Boot image flashed over latest official and works well enough so far.
[Nextbit Robin] gr3y_:
Which version did you flash? I had no problem with 2.79
[Nextbit Robin] substanceneil:
Thanks, Gandalf, for making our phones fly!

Someone previously had asked about the "Miscellaneous" entry in the battery stats, which on many Omni/Robin phones seems to be the highest user of battery. I found this thread that explains how this is a calculation issue, not an actual process using power nor a bug: https://xdaforums.com/google-nexus-5/help/miscellaneous-battery-drain-t3002598

From that explanation:

Summary

There is no such thing as a "misc bug" or "WiFi bug".* Android tries to calculate the amount of battery used by each device element, based on a very finite list of values.* Since the values are pre-determined in a file, it is not an accurate refelection of reality.* When these values in reality are higher than the file, it makes the Battery Stats show a lower % than reality being used by the elements (most easily seen in wifi).* To make the elements total match the actual % used from the battery, Misc was created to fill in that discrepancy - However, since people thought it was a bug due to lack of understanding, it has since been hidden.* But it is not a bug.

I hope this helps.

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

Unrelated: can anyone confirm that NFC/Android Pay is working? I can't seem to get NFC to work either with Android Pay or Android Beam. I have it turned on in the settings.
[Nextbit Robin] bmac6996:
Thanks to the OP for your hard work.

Installed and looking good so far. I had 14.1 Lineage which is still kinda rough but install this and there is a noticeable difference in polish.

To answer some questions/thoughts here:

Just installing Omni with opengapps, SafetyNet/Android pay did not pass.

Went the route with Magisk/phh for root. With magisk hide I was able to pass safety net. Will add card and try AP later.

Haven't setup fingerprint reader yet, but heard it's still kinda "laggy"

Thanks again!
[Nextbit Robin] anh4xeo:
Camera app keep getting disconnected, I cannot seem to use camera after a day. is there any fix for this?
[Nextbit Robin] pierremtb:
Same here, I can't provide any logs though, sorry about that.

Congrats for this awesome ROM anyway! :)
[Nextbit Robin] bmac6996:
In the car using Google play. . Bluetooth doesn't cut out prese, but sounds like a slight interruption from the stream. Happens with or without the EQ turned off. Will try to test more on a different bluetooth speaker and a difference source and provide logs. Anyone encountered this?
[Nextbit Robin] keredini:
I have similar issues ... Connected to a bluetooth speaker, the audio sounds slowed down slightly and distorted (as you said, with or without EQ) and i get occasional cut outs (the connection doesn't drop, just a 1/4-1/2 second of silence and then it comes back).
[Nextbit Robin] valhallen.282:
To everyone with Audio issues - this is common over Bluetooth. Compression/delay is a factor of the drivers in there. Gandalf is in the process of replacing and reworking them. While aptX is supported it needs to be put in to the driver for it to work correctly. If you own Poweramp I'd suggest using the beta they have at the moment and switching audio routing to their experimental ones. That seems to work. The stutter is also a byproduct of Low power state. You can look it up.

The powerHAL is being rewritten along with a new device tree as mentioned earlier. A little more patience so it can be tested out correctly! All thanks to the Dev :D
[Nextbit Robin] keredini:
Great news ... Hopefully that didn't come off as ungrateful, overall I think this is a great rom and I'm sure it will keep improving. And I'm always up for testing if need be. Thanks again to Gandalf and all the devs who help.
[Nextbit Robin] valhallen.282:
I'm using open camera. Running 72 hours still works pretty well. Snapchat also works. Please provide logs.

Logs sir. At least recreate the issue and pull the log.

He tests as hard as he codes :D I'm no Dev. I'm just a mouth piece that goes off by itself.