yashsingh1/xdaforums huggingface dataset:
[Nextbit Robin] xBane_:
What kind of apps are you running? I'm always at 30% by 4pm with only 2~hrs of sot. 83 apps installed, with aroma gapps with all the Google apps I normally use. (My day does start at 6am tho)

---------- Post added at 11:30 AM ---------- Previous post was at 11:28 AM ----------

Whenever I turn on ambient display (it's convenient) raise to wake gets turned on. However, raise to wake is not available to turn on or off in the gestures section, even though it shows up if you search 'wake' in settings search. How can I turn off raise to wake?
[Nextbit Robin] /root:
Interesting battery life. Its been less than 24hrs since I flashed.

For me phone usage started at 7am, now 25% at 6pm. SOT ~2hrs, Voice calls 2hrs20-30mins

No idea if raise to wake can be disabled. Ambient display is quite convenient, so I've kept it ON for now.

If you search there are a lot of other gesture based settings which can't be seen anywhere in Settings page.
[Nextbit Robin] tlxxxsracer:
I guess I shouldve prefaced: I use naptime, servicely, adaway. I have wifi turn off when screen turns off. Disable wifi and BT scanning. GPS on battery saving when not really needed.

I use swipe pro for facebook
[Nextbit Robin] /root:
How is adaway for you? I used adaway and it only blocked 30-40% of ads, very terrible for me for some reason.

I am back to DNS666 which blocks about 80-90% of ads.

Not sure why adaway didn't work, when both do identical thing anyway.
[Nextbit Robin] xWolf13:
Anyone else having issues with Android Pay? I've verified my card and it's all set up, but it's not letting me pay up at the terminal. Weird..
[Nextbit Robin] xBane_:
Any fix yet on the audio stuttering?

---------- Post added at 11:20 AM ---------- Previous post was at 11:14 AM ----------

Hey, naptime isn't working for me. Yesterday, it wasn't even opening. Today, it opens but then immediately​ freezes and crashes.
[Nextbit Robin] PRGUY85:
Audio stuttering still happening.

Will the Google Camera mod released by XDA work with the Robin? I have tried installing it but it won't since the ROM already has a package with same name.
[Nextbit Robin] pixLzd:
Use google camera mod from kenzo device forum, hdr+ working greats:laugh:
[Nextbit Robin] /root:
Using the original one or the latest updated Gcamera pro?
[Nextbit Robin] pixLzd:
Latest gcam pro:)
[Nextbit Robin] PRGUY85:
Do you here a link for this Kenzo device forum? Can't find it.
[Nextbit Robin] pixLzd:
Here you go : https://xdaforums.com/redmi-note-3/themes/google-camera-hdr-t3656174/page15:)
[Nextbit Robin] xBane_:
Fix yet for the audio stuttering? It's getting very bad, frequent, and even more interrupting now that I'm trying to carry multiple sms/mms conversations at once.
[Nextbit Robin] /root:
Been using the latest 7.3.0 for about 10 days now. Issues I'v faced so far.

- If I am on data for quite long and turn ON WiFi, it will show the saved networks but won't connect to them. Restart fixes it.

- Since flashing, I had 2-3 random app crashes.

- I've set the Face Unlock feature along with Fingerprint. 3-4 charge cycles later, I see Trusted Face crashed message.

- In last 10 days, there were 2 random reboots while using the device.

- Battery life is decent. I get ~3hrs SOT with moderate usage (LTE connected)

- Loudspeaker volume is low, the issue is similar to what the stock had last year.

- I am not certain the 'Pocket Detection' function works.

- I think Robin only has 1 color LED at the bottom, the settings on multi-color is useless.

I wish the back LED could be configured, that would look amazing.

Overall its very much stable and have no major issues apart from the WiFi problem.

Correct me if I am wrong, so there won't be any new updates to this build? Next update would probably be Oreo?
[Nextbit Robin] Swag1Flamelem:
Hello, OG.

I am using Jio sim in India and this ROM is not able to detect my sim card. My sim card works in other ROMS and other sim cards work in this ROM. Is there is a solution to this problem, can you fix it?
[Nextbit Robin] PRGUY85:
I have been trying to use Android Pay on several pay terminals with this ROM, but it doesn't work. Is this a known issue or am I doing something wrong?

I
[Nextbit Robin] Kaleshwar:
Honestly I've never gotten android pay to work with any other rom including PA.
[Nextbit Robin] clu1688:
It happened to me also during my Toronto trip this summer. I researched and it seems to be phone hardware issue (chip not certified?). I was running stock at the time, it has very similar behavior, it saw local carrier and displayed the carrie name on lock screen, voice and sms were ok, but no data roaming. My other tmobile phones could get data no problem.
[Nextbit Robin] johnwazhere:
Nice

Everything seems to work flawlessly been using this ROM for roughly 2 weeks and its been great. Only thing that kinda bugs me is that the charging LED doesn't go on and maybe we can get the rear leds to work and a light mint theme ;). How do i get the nextbit apps installed? is there is a zip somewhere?
[Nextbit Robin] seedofriots:
Any good Sound Mode That work on Ether AOSPA with Magisk and busy box installed?
[Nextbit Robin] DJ_SpaRky:
I use Viper4Android, works just fine, once you set SElinux to permissive. I believe that there is a Magisk version.
[Nextbit Robin] hobbit19:
7.3.0

nfc not working
[Nextbit Robin] TheCrazyLex:
Could you give detailed information on your issue including logs?
[Nextbit Robin] HeaDekBatHblu:
Viper4Android, but it doesn't help with speakers
[Nextbit Robin] xBane_:
Does this fix the audio stuttering issues?
[Nextbit Robin] jabashque:
For what it's worth, I end up noticing that the stutters seem to, well, stutter entire apps. For example, when running AnTuTu 3D, both the audio and the 3D rendering stutter. Also interesting to note is that the bundled Shuttle+ app and another music app I downloaded (which I can't remember the name of) doesn't have the same stuttering issues. Not sure if it's because they both depend on AudioService for media playback.

Unfortunately, I don't know what logs would be relevant for this. I've switched to using another rom because I really can't tolerate the stuttering.
[Nextbit Robin] HeaDekBatHblu:
No
[Nextbit Robin] /root:
REVIEW UPDATE :

Roaming doesn't work.

Once your mobile network goes outside your home network, com.android.phone keeps crashing.
[Nextbit Robin] disizjay:
There is an issue with Bluetooth and Android auto connectivity. Everytime I have to restart the phone in order to have audio streamed to the car while connected thru Android auto.
[Nextbit Robin] soulife:
Nfc tags can't be read by my Tasker plugin for example.

Several other apps I downloaded from the play store (just to test if it was a bad update for the plugin) won't work either.. it's not an application related permission issue..

I don't have any writable tags, so I can't test writing them.

this might explain why nobody can get android pay to work, no nfc..

Also, nfc isn't toggled off and on via airplane mode, even though nfc is included in the airplane_mode_radios global variable..

I'll try to see if toggling nfc off and on gives anything useful in the logs. Other than that, I don't know how to get you logs that say anything different than every other robin. I'd imagine they would on logs generated during debugging the development of PA 7.3 for Robin..

Haven't found anything other issues yet.. No fc of system or google apps, no reboots, just nfc
[Nextbit Robin] TheCrazyLex:
Many people have Android Pay working.
[Nextbit Robin] soulife:
sorry, i didn't read the whole 24 pages, i just skimmed to see what i should expect before flashing.. I only saw 3 or so people mention pay in that skimming, and they said it wasn't functioning so i thought it was broken for everyone..

I donno, but im loving this rom, i've been waiting for something like this that is stable and up to date to finally leave stock, every other rom seemed to have some decent bugs, so ill try to get those logs looked at and submitted soon for the nfc.. I've got nfc tags tied in to my home automation, and i really don't want to go back to stock, so Probably monday or tuesday..
[Nextbit Robin] xWolf13:
Just wondering if there has been any progress on the roaming issue that has been present in the ROM for a while.
[Nextbit Robin] pablomancera:
I can't listen 24bit flac music with this ROM, neither with shuttle nor play music
[Nextbit Robin] TheCrazyLex:
Paranoid Android 7.3.1

Hey guys!

We are releasing Version 7.3.1 which fixes some serious issues for this device.

The full release post is here: https://plus.google.com/b/107979589566958860409/+ParanoidAndroidCorner/posts/Yj4kqx7X6p1

Alex
[Nextbit Robin] /root:
Thank you for the patch, much appreciated.

There is no mention of the fix for roaming or did I miss it?
[Nextbit Robin] tlxxxsracer:
Installed. running smooth so far
[Nextbit Robin] Diaz1999:
could u tell me whether the camera autofocus problem's been fixed??
[Nextbit Robin] stefanthehuman:
It has been fixed. I took 3 consecutive pictures with no issues, where as before it would go downhill after 1.:good:
[Nextbit Robin] Sparubens:
No mention of the stutter bug. It's still there I guess?
[Nextbit Robin] demeez:
Is audio stutter still prevalent?
[Nextbit Robin] xWolf13:
Audio stutter is still there
[Nextbit Robin] pablomancera:
If I touch the screen to focus an objective, focus and taking photos freezes until I switch mode (video or panorama) or I exit and open again the app

---------- Post added at 06:45 AM ---------- Previous post was at 06:38 AM ----------

And I'm still unable to listen to my 24bits 48000Hz flac music :(
[Nextbit Robin] js.juju:
The WiFi keeps droping on Nextbit Robin
[Nextbit Robin] mbchc:
I'm new to custom rom here, may I ask if it is possible to have android pay back on paranoid?
[Nextbit Robin] divbyinfinity:
Anyone got bluetooth problem? I cannot turn on bluetooth. The weird thing is it says that my bluetooth is already on (in notification) but it say otherwise on bluetooth setting.

Already tried to wipe dalvik and cache, still no go.
[Nextbit Robin] GuyIncognito721:
Hi there,

I just installed the latest version and I have a question regarding the camera. Every time I take a picture with HDR mode enabled, two pictures get saved to my photos. I don't see any options to correct this. Is this a feature or a bug and is there anything I can do to remedy it? Thanks.
[Nextbit Robin] sridharans:
Been a victim of it recently. !
[Nextbit Robin] shunjou:
A bug that has been reported but never addressed in any version (like many others). Look for the modded google camera thread in the apps forum for this device, it should work with this rom as well.
[Nextbit Robin] Darkstar_Devil17:
Volte Issue!

I'm facing Volte issues with the 7.3.1 release of this aospa and same on carbon too. I'm using Jio4g & Call doesn't connect directly from dialer, and in Jio4gVoice app, it shows "this handset is Volte supported, you can make call directly from your dialer"

Is there any way to solve or fix that??

Plz help!!!
[Nextbit Robin] shooreek:
Andriod Pay

Hi there,

I tried to find description of issue and solution I faced, but witout any seccess. May be someone can help.

I've got Nextbit Robin with ParanoidAndriod 7.3.1 and Magisk 5.4.3 installed. Everything works fine except Android Pay. It allows me to attach cards, but when I put my phone close to the card reader in a supermarket nothing happens. I tried to install app from Tinkoff bank that also allowes to pay with beam, but the result is the same.

It looks like android beam is switched off, but it's on. Beam also works fine when I share information between other phones.

It worked good on Stock ROM anf Lineage OS 14.1.

Is it a phone issue or ROM? Do you have Andriod Pay working?

[IMG="PA 7.3.1"]http://i.yapx.ru/j2L7.jpg[/IMG]

[IMG="Magisk SafetyNet"]http://i.yapx.ru/j2L5.jpg[/IMG]

[IMG="Android Pay"]http://i.yapx.ru/j2L6.jpg[/IMG]
[Nextbit Robin] ipowyourface:
It's the ROM, NFC is broken with the current kernel. Some users have reported that if you go back and flash an earlier kernel of the ROM, around July I think, it works again.
[Nextbit Robin] jabashque:
Wrong ROM. You're thinking about OmniROM, which has that issue. AOSPA doesn't have the NFC kernel issue.
[Nextbit Robin] montypablo:
Got into the same issue last october, then I had to revert back to stock nextbit rom since I needed to use my robin abroad.

Did someone found a fix to this problem or know if it's fixed in the 7.3.1?
[Nextbit Robin] js.juju:
I have the same issue too
[Nextbit Robin] /root:
Ya this is a documented/discussed but unacknowledged bug. The only reason I stopped using this ROM.
[Nextbit Robin] DiePirate:
Present...

The only bug for me...
[Nextbit Robin] thorpeyt:
Call Forwarding

I am using Consumer Cellular and I'm trying to use call forwarding to forward calls under the conditions Busy, Unavailable, Unreachable to another number.

I go to the phone app>multi button>settings>calls>GSM call settings>call forwarding>voice [Exhibit 1-5]

Once I get that far I receive an error saying "Network or SIM card error" [Exhibit 6]

After i realized that that wouldn't work, I tried contacting my service provider (Consumer Cellular) and they said to go the the phone app and dial **21*[Forwarding Number]# When I did this I got this error: Call Forwarding connection problem or invalid MMI code. [Exhibit 6]

All Exhibits mentions in the above page can be found here:drive.google.com/drive/folders/1hd684pINcUYTAavfRTkA32uTy2UmuzHg?usp=sharing
[Nextbit Robin] witnit:
I ran into this problem myself. I am not on Consumer Cellular, though I am on another MVNO that resells AT&T service.

I'm guessing you've checked whether or not Consumer Cellular allows you to change these options. Assuming that's the case, try taking your SIM card out and putting it into another compatible phone, and then try the procedures for changing your forwarding options that you already mentioned. The dialing sequence I used was: **004*xxxxxxxxxxx# (where the x's are replaced with my forwarding number), and it worked just fine without error. The dialing sequence you listed I'm not as familiar with. Swap the SIM back into the problematic phone and you're good to go.

One other possible solution is to call your carrier and ask them to change the settings for you.

I don't know why this issue exists, but at least there is a workaround. I guess it won't be too helpful if your alternate phone also produces the same errors. The little bit of info I found seemed to suggest that this is particular issue with certain phones on AT&T MVNOs.
[Nextbit Robin] Jacobwitt:
Well hello there trent!

I'm the previous owner of the phone, and to my knowledge while I was running paranoid w/ t-mobile I was able to change the forwarding number via your method so it works under another carrier.

So I'm assuming that his carrier will have to change the setting manually for him.

Funny running into you here Trenton! Haha!
[Nextbit Robin] witnit:
Calling the carrier is worth a try and that others have been successful via this route. But let me clarify as I think there might have been a slight misunderstanding: if he has another phone that works with Consumer Cellular, he could do the whole swap the SIM thing I mentioned and see if the second phone would let him have access to the forwarding options on Consumer Cellular. Provided either the dialer settings method or the dialing sequence works with that alt phone, then just swap the SIM back to the first phone and everything should continue working. If you need to switch the settings around again, you would have to repeat the phone swap routine.

As an aside, I'm currently on Stock 7.1.1, and I had this trouble, so it isn't necessarily related to Paranoid Android.

Who be this Trent of which you speak? He be not I or me, unless he likes receiving gifts of money and phones, then that's me, Sir Trent, Lord of treasure. Forgive my word goofs, though I am still not Trent, at least not the last I checked ;)
[Nextbit Robin] Igorperrotta:
Are the cloud leds usable?
[Nextbit Robin] Jacobwitt:
AFAIK, they only work for displaying charging status.

Thats about it.
[Nextbit Robin] Igorperrotta:
Would it be possible to show notifications, or anything else? one of the coolest and stupidiest thing about this phone are the leds
[Nextbit Robin] Jacobwitt:
Not without some heavy modification.

I've never really messed with it, because I never even saw the LED's on the back of the phone due to my case covering them up.

I'm assuming you've tried using lightflow to attempt to control them, but when I tried it didn't work.
[Nextbit Robin] Prospero.X-3:
I could quickly write a simple app to activate the rear leds for notifications, would people find that useful?
[Nextbit Robin] NurKeinNeid:
Yes, that sounds great. Would that app work with any Rom?
[Nextbit Robin] Prospero.X-3:
Yep.
[Nextbit Robin] NurKeinNeid:
Cool, I would be very happy about that. That is really useful. :victory:
[Nextbit Robin] Igorperrotta:
i would put a picture of you on my wall and worship you as a god
[Nextbit Robin] montypablo:
Any news about crashing com.android.phone process in roaming?
[Nextbit Robin] BearOfXDA:
The notification light is on the bottom of the device
[Nextbit Robin] xWolf13:
Highly doubt it. Issue has been highlighted so many times by users, however, we still do not get a response from the developers.
[Nextbit Robin] /root:
I don't know how many times other people reported it but I reported it in October and there was no response from devs at all. At that time it was 7.3.0 build and soon after that 7.3.1 came out. At this point they announced that no more N builds will be coming and this will be the last stable build.

So I don't think they will fix it in now but might probably fix it in the Oreo builds if those are coming.
[Nextbit Robin] C0D3FRE@K:
hey new to the community here on XDA this is gonna be my first custom ROM install, wish me luck :)

btw by your reply it seems that there's hope for an Oreo build for the device, are you assuming this or has any developer confirmed that they're working on the Oreo build for this device?. Because I've reading these forums for quite a while. I didn't have any thought that someone could be working on Oreo for this device, that would be real cool. I'm keeping my fingers crossed for now
[Nextbit Robin] /root:
Are you asking in general or just PA?

If you're reading the forum then you should have read CarbonROM and OmniROM are being worked on and devs have been posting about its update in their respective threads.
[Nextbit Robin] C0D3FRE@K:
Major Calling Issued[Reliance Jio]

PA had a lot of issues for me.

1.My games lagged alot(Game-critical ops, i got good FPS on stock but it lagged alot in this ROM)

2.Couldn't get MTP to work on PC when developer settings were turned on, kinda sucked but was bearable.As soon as I turned off developer settings everything seemed fine and smooth.

3.Battery Life wasn't any better if worse than the stock ROM

4.THIS WAS THE DEALBREAKER FOR ME No matter what I tried I couldn't get a stable LTE connection for calls, let alone data. It always kept losing signal then reconnecting and this just went all day long for me.THE BIGGEST PROBLEM WASThat I couldn't make/receive any Calls whatsoever(Reliance Jio User from India). As soon as I got a call it automatically got disconnected same story with Outgoing calls disconnected as soon as I made a call.

I do really appreciate the efforts by [MENTION=5986135]TheCrazyLex[/MENTION] and everyone else, Hope this calling issue can get resolved in the next update.

Thanks for reading
[Nextbit Robin] /root:
- Not a big mobile gamer so can't comment on games but most small puzzle based games I sometimes play worked fine for me.

- For battery you need to give it a few days for regular usage and the OS to run fine with your usage, make this a point for every ROM or every new factory reset or every new phone you start using. Battery for me was similar to what I got with stock, nothing changed that much.

- Weird, data transfer worked fine for me. But if just turn off dev settings worked, this shouldn't be problem. Its okay.

- I did use Jio for 2 days, I never had issues with disconnections once a call was made but I did have problem with getting LTE indoors. But that happens to me in general with Jio. I can't say this was a ROM problem for me. Also you have to understand you not getting signal in Jio means you ain't getting LTE, for other networks this isn't correlated but for Jio it is. As unfortunately, Jio is just a 4G only network. On other networks things work fine.
[Nextbit Robin] C0D3FRE@K:
Thanks for those tips, really appreciate them,

I tested the Jio issue by putting it in a Redmi Note 3 and Mi A1 aswell, same issue no signal whatsoever, but i know for sure when I was on Stock ROM that I had atleast 1-2bars of network all the time in my house. After that I went outside to check the issue and Voila!, the network is magically better.

I'm pretty sure that there isn't any chance by installing a custom ROM I did something to the SIM card, but I'm still surprised how I suddenly lost all connection to Jio in my home. Guess I'll wait a few days and see what happens. Thanks for replying.:fingers-crossed:
[Nextbit Robin] Prospero.X-3:
As promised

[MENTION=7402024]Igorperrotta[/MENTION] [MENTION=5974762]NurKeinNeid[/MENTION] [App][Root] Nextlit: control the Robin's segmented LEDs :)
[Nextbit Robin] NurKeinNeid:
WTF! You have it really done?! I'll try it immediately.

Thank you very much! :victory:
[Nextbit Robin] Prospero.X-3:
:D

No problem! I hope it lives up to the hype.
[Nextbit Robin] DiePirate:
How to fix the battery drain? Battery is better or worse than stock?
[Nextbit Robin] /root:
That surprising, for me PA was almost the same as stock in terms of battery.

Anyway, when it comes to battery optimization I will be honest there is no magic switch to turn ON to solve everything what works for me might not work and there are some things that work for some ROMs (stock & custom) and don't work that effectively for others. Its a trial and error thing. You have to test.

First you have to do the basic stuff to optimise the battery, notification restrictions, ambient display, location restrictions, basic battery optimisation for apps so as to restrict background running apps etc. Also if you use a task killing app or have a habit of killing every background app, STOP it. Don't do it.

Then setup greenify, if you have literally no idea how to do that then this is a good easy start guide by How-To Geek. Make sure you set it up properly for all your installed apps. This will take time but worth it.

Try only the above for 2-3 days and see if that improves the battery.

Once that is done and you still need more juice, NapTime helps a lot with decreasing your standby drain.

Now both the apps don't really need root but root would ease the way they work. Greenify does work with root but for NapTime you need to setup with adb commands, it easy and the App itself tell you how to do it.

Then for rooted there is [L speed](https://xdaforums.com/apps/l-speed/tweak-l-speed-v1-0-02-02-2015-t3020138), now this didn't work much for me it was good but not that great for me for some reason but for many it does work well. So try this one too.

Whatever you try give each solution a few days independently and then try them to together and give it few days to work and show results. Nothing really gives you proper results in 1 day usage, you have to let it run a few days to understand. First try them individually and then combinations and see what works and stick with it.

Good luck.