yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] zingzangripper:
sorry for being incovenient, but any of you experienced camera problems? my camera stops working after some photos. reboot doesn't fix, clear cache doesn't fixe, stop app, etc etc

kudos to all of your efforts towards this super-dope phone and all the android dev. for me this rom is working pretty well except for that camera issue...

thanks!
[Samsung Galaxy Nexus] Nautilus74:
I use Open Camera and I never had problems (yet) on this rom! :)

Only using torch ON for a long time , I no longer able to turn off led and I have to restart the terminal
[Samsung Galaxy Nexus] werty100:
No porblem with the camera provided on rom, 11 shoot at the same time and no problems i have just tested localition disabled
[Samsung Galaxy Nexus] zingzangripper:
:/ don't understand what can cause this..

camera all of a sudden turns impossible to open.

happened the same thing after 2 flashes.
[Samsung Galaxy Nexus] Kf_Umbra:
Has anyone been able to find a solution to the mobile data connectivity problem on toro? I can connect to 3g on the other unified marshmallow builds. It's the only problem I've run into so far.

Other than that, this rom works amazingly well.
[Samsung Galaxy Nexus] AgentSmith:
If you post a logcat others might be able to figure it out.
[Samsung Galaxy Nexus] zingzangripper:
ok i flashed it again yesterday and the error came up once. i deactivated camera's permission to access GPS and it opened back again normally.

will test through the day.
[Samsung Galaxy Nexus] rohitchouhan07:
Can anyone confirm that trickster mod works?

I remember it not working due to some busybox problem, although kernel adiutor worked just fine.
[Samsung Galaxy Nexus] E66666666:
Trickster Mod works fine here, but this kernel doesn't have any extra options.
[Samsung Galaxy Nexus] Ziyan:
interactive gov experiment

Those who feel like they're up to some adventure, please fire up your favorite kernel settings app and change the following interactive governor params, then report back after some usage if there's any difference in general reaction times and/or animations and stutterings (don't let placebo fool you):

target_loads -> 65 920000:75 1200000:90
go_hispeed_load -> 90
above_hispeed_delay -> 20000

Don't draw any conclusions from this, I'd just like to find out if it'd worth updating the interactive governor, as I don't think it's set up optimally right now :)
[Samsung Galaxy Nexus] siealex:
I had a similar freeze several hours after an accidental torch activation. It froze on the lockscreen and did not respond to any actions including hardware buttons.
[Samsung Galaxy Nexus] Ygor Cortes:
Is it possible to enable Ambient Display? It's an AOSP feature, right?
[Samsung Galaxy Nexus] thagringo:
Thanks but i dont think it makes a diffference here.

Cheers

Enviado desde mi Galaxy Nexus mediante Tapatalk

---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------

Would that make sense ? I mean, is it suppposed to work on a device this old ?

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] nikodr:
For those thar need speed, root your phone and install greenify. It is the best thing to do
[Samsung Galaxy Nexus] E66666666:
There have been ROMs with it and plenty of apps doing a similar thing ever since the Moto X was released. Sadly it relies on some power saving modes the CPU has, which old OMAP doesn't have.

I might be wrong though on the power saving bit.
[Samsung Galaxy Nexus] Castro27:
Yup, there's an xposed module for that.
[Samsung Galaxy Nexus] PythonNut:
I'm giving it a spin now. I'll get back in a day or so. I did have trouble setting the governor tunables in Trickster Mod, but Kernel Adiutor worked fine.

Would an optimally tuned interactive be better than dyninteractive?
[Samsung Galaxy Nexus] bamtan2:
In the past when I was testing overclocking with similar settings, the constraint on NORMAL USAGE speed was not really the CPU heat, but instead the governor which was tweaked to save BATTERY LIFE. So I could run the CPU overclocked (and much more often) than normal, and it would be faster and work fine, but it used more battery.

So in this way, the governor settings are very much an artistic balance. A matter of taste. I think, if you use the phone plugged in a lot, you should be able to use the faster governor settings. If you use the phone UNPLUGGED a lot, you should be able to use the more efficient governor settings.

I believe the settings you've listed are good. I also believe that no one governor setting is "perfect" for everyone. Whether or not "perfection" is the goal... that's up to you ;) ;)
[Samsung Galaxy Nexus] PythonNut:
[MENTION=2633638]Ziyan[/MENTION] okay, so I do feel like the new settings feel a bit smoother, although I will admit that there's a wide variance in performance, and that the CPU is definitely not the only bottleneck on this device. :)

Excellent point. I, for example, have three replacement batteries and two external battery chargers, so battery life isn't really a concern for me, but at the same time, I realize that it can be absolutely critical for other people.
[Samsung Galaxy Nexus] AgentSmith:
For the last couple of days WiFi keeps disconnecting in standby mode. Of course it's set to always on. Today it also disconnected in the middle of a sip call. It takes a couple of minutes of standby time before it happens. Does anyone else experience this?

Screen auto rotation also doesn't work.

After about 10 days of use the phone is still quite snappy though which is really nice. I stopped fanatically closing all apps and now apps don't reload anymore most of the time. :)
[Samsung Galaxy Nexus] bamtan2:
It is possible that something is messed up on /system. In TWRP, go to "Wipe" and format the /system partition clean. The flash your ROM and gapps and use the option to "wipe dalvik and cache". You may also need to do a factory reset, I don't know. :)

7.1.2 (unstable) is here: https://builds.unlegacy-android.org/aosp-7.1/tuna/

OpenGapps supposedly support 7.1.2 now. I don't know if anyone has tested the very latest release. There were some other 7.1.2 gapps linked earlier in this thread too.
[Samsung Galaxy Nexus] tylerdurden83:
Can Tuna be flashed over Maguro?
[Samsung Galaxy Nexus] _yen_:
unlegacy android (and slim) are unified build for all tunas so they can be flashed on maguro too.

bye

yen

---------- Post added at 01:06 PM ---------- Previous post was at 01:03 PM ----------

Try the smallest opengapps possible (pico) other the base 7.1.2 (arm) package from this thread: https://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

bye

yen
[Samsung Galaxy Nexus] bwalter:
Most 7.1.2 ROMs give me a force close on the setup wizard with gapps, causing the wizard to relaunch thus creating a loop. The good news is the wizard can be skipped by touching each of the corners (top left, top right, bottom right, bottom left). I haven't tried pure Unlegacy Android in a while, but I've tried some of the Dirty Unicorns builds, and now have the phone on Slim7 which are UA based. I use Open Gapps Aroma and among other things, install the Pixel launcher. To go that route you need to make the system partition bigger.

I also had odd behavior with Open Gapps claiming I needed to use the 6.0 version if I didn't wipe system before flashing the ROM. This happened when coming from a Dirty Unicorn build. Again this was when coming from a DU build so I don't know if it's a problem with UA or Slim7 too. In any case, it seems safest to wipe system before flashing.
[Samsung Galaxy Nexus] n_petr:
I have to confirm your findings with gapps-base-arm-7.1.2-20170420-1-signed.zip. But with open_gapps-arm-7.1-pico-20170429.zip it could be completed well.

---------- Post added at 10:45 PM ---------- Previous post was at 10:43 PM ----------

Yes, you can try open_gapps-arm-7.1-pico-20170429.zip. It worked for me.
[Samsung Galaxy Nexus] edu24lal:
the rom is pretty fast... i like it very much..but theres 1 major issue...after hours of normal usage, the rom uses too much ram that causes a ram hog....1st boot is fine says 300 mb or 200 mb free of ram, after hours of usage it says -10 ram,-130.

pls fix this thats the only problem
[Samsung Galaxy Nexus] The Doctor04:
Thank you for keeping the GNex going strong. Any chance this will make it's way to the toro version of GNex? Thanks!
[Samsung Galaxy Nexus] musafercom:
update over the air

is it possible to get updates over the air for maguro on this rom 7.1.2 release

if yes how please ?

thanks & best regards
[Samsung Galaxy Nexus] Android-Andi:
Not yet

Gesendet von meinem A0001 mit Tapatalk
[Samsung Galaxy Nexus] phaleg:
It's unified project for all tunas

(maguro, toro and so on)
[Samsung Galaxy Nexus] The Doctor04:
So even though the download says tuna it will work for Toro? I'd do I will need to give this a spin!
[Samsung Galaxy Nexus] heartless vegan:
Hi & thank you for the ROM!

I installed Unlegacy-Android 6.0.1 on a tuna and flashed it with GApps & SuperSU. Unfortunately the full-disk encryption does not work for me. As soon as I start the encryption process, the smartphone gets stuck in the soft-reboot splash screen. How do I get the encryption working?
[Samsung Galaxy Nexus] phaleg:
Yes, because Tuna DOES include toro, maguro and so on
[Samsung Galaxy Nexus] The Doctor04:
Got it running last night, thank you! Pretty amazing achievement giving these old devices new life again. I am really liking the simple, clean AOSP feel on the GNex. I thought for sure there would be a little jank just because the device is so old but everything is smooth and works like it should. Very, very impressed
[Samsung Galaxy Nexus] bamtan2:
I think people overestimate how much power is needed. For many years I played games and used the internet on desktop computers slower than this phone! And if we simply had more RAM or faster storage, it would perform even faster. Not everything is about the CPU! Mostly just websites full of advertisements need the CPU! LOL! So we use AdAway! ;)
[Samsung Galaxy Nexus] MrFlashGame:
Hey I have a question about lanchon repit but since the repit thread is closed I don't know where I can ask. I think you guys can answer me my question here too so: Does a repit survive a conplete reset? (twrp -> wipe -> advanced wipe -> all partitions chosen) Sorry for this wrong thread question.
[Samsung Galaxy Nexus] runekock:
Wiping won't change the partitioning that repit has done.

However, installing a rom will cause the system partition to appear to be the standard size. Just resize it after flashing the rom to fix that (also in advanced wipe).
[Samsung Galaxy Nexus] guest4711:
You may ask at https://xdaforums.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036 .

Flashing a normal rom should not change your partitions...
[Samsung Galaxy Nexus] maymage:
I can confirm that bug, i.e. increasing memory usage over time. Cf. post no. 1587. I'm on maguro, UA 20170505, opengapps 20170505.
[Samsung Galaxy Nexus] bamtan2:
[MENTION=2633638]Ziyan[/MENTION] [MENTION=5153662]Android-Andi[/MENTION] I have completed my latest round of testing all the new ROMs. The quality of the android 6 and 7 builds seem equal. If you wanted to migrate to supporting only android 7 instead of 6, I don't see a problem with that. However ALL builds tested had worse multitasking/memory and video performance than android 5.1 (CM12.1). All would close apps that stay open simultaneously with 5.1. All would crash the YouTube and Twitch apps when pausing, stopping, multitasking, or turning the screen off while playing video. To compound this, the system would freeze and require a battrry pull if I let these apps crash enough times before manually resetting.

So the progress on the new code base seems good. 7.1.2 in particular seems miraculously bug free. But because of better daily performance with android 5.1 (and no video crashing), I am back to running CM12.1 daily.

An extra bug report: The only ROM that ever asked me to restore my phone apps and settings from Google is CM12.1. I enabled "backup of settings" with all the ROMs I tested.

Keep up the good work (and donations to developers) everyone! :)
[Samsung Galaxy Nexus] vortex-5:
For the record I don't encounter the memory bug in 6.0 I haven't moved to 7.1.2 yet since a lot of people are saying we're not quite at a good stability level yet. Maybe we can get an update most here seem to say 6.0 is still the best daily driver with better memory management for now.
[Samsung Galaxy Nexus] Sesme:
Last mm and kk builds no have f2fs suport??

Enviado desde mi D5803 mediante Tapatalk
[Samsung Galaxy Nexus] MrFlashGame:
Yes.
[Samsung Galaxy Nexus] Sesme:
Im testing it and change to ext4 my f2fs partitions

Enviado desde mi D5803 mediante Tapatalk
[Samsung Galaxy Nexus] TheFerhatKing:
Does anybody know why miscellaneous is taking very much battery? I already checked my deep sleep and its great and I also use greenify. I'm on the lastest 7.1.2.

Gesendet von meinem SM-G955F mit Tapatalk
[Samsung Galaxy Nexus] vortex-5:
so I've finally made the leap to 7.1.2 have been running it for 3 days now. I don't seem to get the memory leak issues that others seem to be getting.

However I have noticed that once a day I get a no sim card error that seems to go away right after I restart. Not a deal breaker but just in case people are going to 7.1.2 there are still maybe a few tiny issues here and there.
[Samsung Galaxy Nexus] Sesme:
yes is a problem of las twrp 3.0.1 no format good the partitions on f2fs.

installing 2.8.4 and work fine thx
[Samsung Galaxy Nexus] Rastor:
I have been using 7.1.2 on a maguro. I am finding that playing the game C.A.T.S. is a good way to trigger the memory leak. But it is amazing that I can run C.A.T.S. on 7.1.2 on a maguro at all, frankly it kind of blows my mind. Keep up the great work!
[Samsung Galaxy Nexus] hollandais:
Hi,

I tried a clean flash of the last espresso WiFi (20170916) on my tab2 P5110 and each time I should reboot manually in recovery. Once flashed the tab stays under recovery and doesn't ask for reboot. I tried 4 download's and each time same problem.

Has someone else the same problem?

The 20170509 one is fine...

Envoyé de mon Galaxy Tab 2 en utilisant Tapatalk
[Samsung Galaxy Nexus] guest4711:
It would be better to ask at the coresponding thread for espresso. This here is for maguro/tuna (galaxy nexus)... Good luck!
[Samsung Galaxy Nexus] PGHammer:
Indeed It Will

I have an ex-VZW toro that has run mostly it or builds based on it (so far, the only builds I have run this year that are NOT based on Unlegacy are Slim 7 and Lineage, and of those, only Lineage behaves itself - however, the bear with Lineage is that I can't cloud-restore - I have to treat each install as new). Right now, I'm working on a "teething" issue that is only with 7.1.2 Unlegacy and builds based on it - it loses the SIM. Worse, it doesn't always happen - but when it happens, I have to give it a complete wipe and either reinstall or install a different build. However, 7.1.1 is fine IF you don't need SafetyNet (SELinux is set to Permissive in 7.1.1, but to Enforcing in 7.1.2) - hence my trying to deal with this issue.
[Samsung Galaxy Nexus] Android-Andi:
Logcat and dmesg?
[Samsung Galaxy Nexus] musafercom:
hi

is google dialer compatible with this rom for galaxy nexus maguro. if yes how to flash the app.

thanks & best regards
[Samsung Galaxy Nexus] vortex-5:
There's a super SU update from the app store (2.80) it seems to break root for our devices. Can we prevent updates on super SU? anyone have a fix?
[Samsung Galaxy Nexus] osm0sis:
Well obviously you can uncheck auto-update for SuperSU on the Play Store..

As for "a fix," there are already a couple test builds in the SuperSU beta thread that mostly fix things, so I suggest you follow along over there.
[Samsung Galaxy Nexus] vortex-5:
The test build for 2.82 seems to address the issue. Unfortulately it doesn't appear on the SR3-279 front page so you're going to have to go search in the tread for it.
[Samsung Galaxy Nexus] gialakias:
Why don't we use magisksu to avoid these problems? I use it in my 2 gnexes and my 6p without a problem. I would like to know your opinion and the other's also.
[Samsung Galaxy Nexus] osm0sis:
Either works. Bugs will happen, and Magisk is not immune to them either.
[Samsung Galaxy Nexus] gialakias:
I totally agree, nothing is bug free. For the time being magisk gives the no hassle solution. I will stick with it till the next bug! Thank you for your answer and your work.
[Samsung Galaxy Nexus] kamwaikin:
Can latest 7.1 enable the LED light while charging? Since Xposed don't support 6.0 above, I lost my battery indicator...

Thanks
[Samsung Galaxy Nexus] cerrod:
Supersu does not work with current 4.4.4 tuna build (01.06.2017)

On my maguro supersu does not work with the 4.4.4 build from 01.06.2017 (tuna). On install no error message in TWRP, but after reboot the device is unrooted. Has anyone the same problem and maybe a workaround for it?
[Samsung Galaxy Nexus] Android-Andi:
Can someone please Check on 6.0 and/or 7.1 if pictures in portrait are cropped to square?
[Samsung Galaxy Nexus] kb8no:
I have toro on 7.1. Old photo taken in landscape. Gallery displays it in landscape correctly and not square. Don't know the pixels in the photo.
[Samsung Galaxy Nexus] vortex-5:
I've started noticing the memory leak issue others have been talking about. It seems to occur overnight requiring a reboot in the morning.

Haven't found the offending process yet. Just thought I'd report it.
[Samsung Galaxy Nexus] osm0sis:
From the latest ZeeLog Lineage 14.1 Kang:
[Samsung Galaxy Nexus] wavedashdoc:
Latest 7.1.2 release working surprisingly well on Verizon Variant of the Galaxy Nexus. Love the support for this 6 year old phone! Not my main anymore but I great backup device.
[Samsung Galaxy Nexus] phaleg:
Are you using it as a backup phone? I mean, calling, texting and so on?

Anything to report?
[Samsung Galaxy Nexus] wavedashdoc:
No, just on WiFi for now, has my old SIM in there and is showing connected to Verizon.
[Samsung Galaxy Nexus] kb8no:
Have the GNext verizon variant. I too have been using it just on WiFi as a music player and very pleased with how it is working, much better than an earlier Nougat predecessor of this ROM. I have very minimal apps. I notice that it reboots occasionally which is not terrible.

I pretty much leave it on charge and stays fully charged normally. However, I notice that occasionally it is develops unusual battery draw and starts draining despite being on charge. It is fixed by a reboot but if left the battery can run down to zero and shut down. I believe this is a sign of the memory leak issue mentioned.

Regarding data, my experience with previous predecessor ROM's is they have trouble with the speed of acquisition of data. They are notorious for dropping down to 3G with loss of 4G signal and not being able to go back up to 4G despite return of signal. They are also notorious for having to cycle between 3G and 4G or cycling data off and on in settings to coax it to work.

I hijacked the Verizon SIM from my broadband dongle. Just remember that the GNex is unable to register a new SIM on the Verizon network on ROM's after KitKat. I keep a copy of a Jelly Bean ROM backed up just for this purpose only. First I tried this and up came Verizon with 4G/LTE proving the SIM was good. The SIM was already initialized so I don't think it added anything but that is what I did.

Then I restored my latest Unlegacy 7.1.2 ROM that I am using. It initially boots into "no SIM" for a short time (I believe this is normal). Then it comes up with no bars and no data and hangs there. You think you are toast but you will see that you are connected to Verizon. Drop down to 3G CDMA and it will come up 3G / LTE and this is reliable and predictable.

I was able to get 4G / LTE to work and when I got it going it worked well. But it takes various unpredictable combinations of cycling between 3G / CDMA and 4G / LTE, cycling data on and off, and rebooting. So it works but transfers are very glitchy.

Then I tried to make a phone call. The dialer seemed to work fine. It looked up phone numbers in contacts. It dialed and it rang. However, I was directed to a Verizon help desk recording and it did not ring on the dialed phone. I tried to dial from contacts but same effect when it brought me to the dialer. I was able to send texts without a problem.

I then downloaded and installed Hangouts Dialer using my 3G / CDMA data and it installed fine. I then made a Google Voice call and that worked fine. So somehow the dialer is borked. Also, the phone call borked the 4G / LTE data needing a reboot to get data back again but seemed to be fine with 3G / CDMA
[Samsung Galaxy Nexus] musical_chairs:
This is good news! I thought mobile data was completely borked on toro on N. If it works for you on a Verizon SIM, it is probably just the APN's that are borked for me on Page Plus. I believe there is an oldRIL fix that will allow the 4G connection to come up right away, but I was never able to get even 3G working, so I haven't checked as of yet to see if that has been implemented properly on N.

I was able to make phone calls and send and receive texts, but it seemed that after a few hours RIL would kind of lock up. The signal strength indicator would still show that it was working, but no network functions actually worked. Again, I never did much digging into this because I have so far been unable to get mobile data working and that is a bigger issue. Yours is the first report I've seen that it indeed works with a Verizon SIM, so you've given me hope again.
[Samsung Galaxy Nexus] kb8no:
Nice to hear from you. In fact, I am honored that you cared to comment on my post. I've used your ROM's and those of zzpianoman a lot in the past. Maybe you remember my RIL harassments? I was using an AOSP tuna 7.1 from 2016-10-20 until I came to this ROM earlier this month. I just liked being on 7 and it worked but maybe you guys' 6 ROM's were actually better back then. I believe that this 7.1 was somehow a predecessor of this but I just can't remember where I got it but I think zzpianoman. This 7.1.2 is surprisingly good and a big success as far as I am concerned. I'd love to be able to use it as a live usable Verizon phone with fully working data and calling.

The RIL in you guy's 6 ROMs had the exact same problems as this Unlegasy 7.1.2 in that they worked on 3G and couldn't hold LTE. I actually had LTE signal and it's just the same as before and it can't hold LTE. It's hit and miss to get LTE started but it does not start from boot. It is deja vu. And I couldn't get you guy's to engage and you all thought it was a lost project. I remember the RIL locking up and saying you were connected but no data as well. It sure would be nice to fix the RIL once and for all so that when we have to finally retire the GNex we can say that we conquered it. It's not like there is no data, it is how it is handled and handed off.

I'm thinking you guys can fix the dialer easier than the RIL. Throw in the "old RIL fix" and build me something and let me try it! If you guys engage I'll throw my Verizon SIM back in and see if I can find out how to more predictably bring up LTE.
[Samsung Galaxy Nexus] bamtan2:
[MENTION=3390093]MWisBest[/MENTION] knows a lot about the RIL, and he is busy ;(