yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] baldwinguy77:
Hey guys, thanks for updating me about RootzWiki, it's a shame to see what's become of it, and I guess XDA is our only solace now. Anyway, I'm really excited to see that people are still using and even working on the ROM. I'm sure you've all heard, but Lollipop is the biggest overhaul that Android has ever seen, so there's a lot to be taken care of if we want to get it running well on the GNex.

So I can't make any promises, but after finals (which are happening throughout the next couple of weeks), I will start working on it along with the people who have already started. (That is, if you don't get it completely up and running by then!)
[Samsung Galaxy Nexus] gtdriver0036:
I've moved on to a Nexus 6 and would love to see Shiny on that one day. For now i'm enjoying being "stock" (unlocked, unencrypted, rooted, modded a few things in build.prop)

If and when a stable 5.0 hits the Gnex i will for SURE be dusting it off and loading it up. Might even use it for a few days as my primary just to see how it handles.

I know i've said this many times but i can't say it enough, a big thanks to everyone that keeps this alive. in 14 years i've never had a phone longer than 1 straight year until the Gnex came along. I stuck with it for 2 years 11 months thanks to the hard work of a very dedicated dev community. I'm hoping to pick up android development in the future, maybe one day i'll be able to contribute as well. You are all an inspiration to me and i'm sure many others as well.
[Samsung Galaxy Nexus] Winkz7:
Looks like they finally cleared up all the spam from RW. Maybe it is still alive.

I'll keep checking both.

Hope finals go well!
[Samsung Galaxy Nexus] RW-1:
I may check both, but right now how might this assist us all?:

http://www.androidpolice.com/2014/12/02/android-5-0-1-lrx22c-hitting-aosp-now/
[Samsung Galaxy Nexus] RoxRedEye:
Has anyone experienced random reboots when the phone is booting? I have fancy kernel installed. I actually did a clean fresh install last night. My phone reboots when it's booting. It'll make it the lockscreen and then the screen dims. After dimming and falling asleep. It'll reboot.

edit: fancykernel seemed to be the culprit. Hate to admit it but, I flashed the latest franco and everything is fine. No random reboots whatsoever.
[Samsung Galaxy Nexus] RoxRedEye:
nevermind. got it.
[Samsung Galaxy Nexus] baldwinguy77:
Hey guys, so this is slightly off-topic but I'm going to have to get it figured out if I want to try building Android at all anytime soon. So I need to download the source again as I don't have it saved anywhere anymore. Everything is set up and working fine, but I have been having a major problem with all downloads from Google servers for the past two weeks.

I have Verizon FiOS, and for some reason my download speeds have slowed to an absolute crawl in the last couple of weeks. Here is the weird thing, though: this is only happening with data coming from Google servers. Whether it's the Android source, Nexus factory images, YouTube videos, Google Play Music, or apps from the Play Store download speeds are never more than 300 KB/s. I know that's not the worst download speed, but it makes downloading the Android source agonizingly slow, and it doesn't really make any sense when Speedtest is reporting my speeds as 75 Mb/s down and 40 Mb/s up. Also, for reference, before this started happening my download speeds from Google have been around 10 MB/s. So I'm really stumped as to what's going on. This is happening with all of the computers in my house, as well as phones/tablets. Also, my download speeds at school (5 miles away) were normal, so it doesn't seem to be a geographic thing. I also tested my ping to Google and it's about 15ms with 0% packet loss. I'm totally stumped as to what this means and what I can do to fix this.

I've tried resetting routers and some other usual stuff, but nothing is making this better. Could FiOS be throttling Google connections or something like that? Just wanted to see if anyone with some more networking experience could help me out, or if someone else has had this problem in the past. I'm totally stumped and I'm willing to answer any questions to see if we can get it figured out. The other thing that I forgot to mention is that all Google file downloads through Chrome are failing at completion with "Unknown network error." Hopefully I can get this figured out soon so that I can download the source quickly and not have to worry about it being corrupt or anything like that. Thanks so much in advance!
[Samsung Galaxy Nexus] Dirty_Jerz:
Did you get this straightened out?
[Samsung Galaxy Nexus] baldwinguy77:
Not yet, unfortunately. I may just start downloading the source now that I'm almost done with finals. I don't know how long it will take, but I feel like I should definitely start sooner rather than later!
[Samsung Galaxy Nexus] JoeSyr:
This is not something I have personal experience with, but I think that the best way around an ISP throttling a particular connection is to use a VPN. I remember my interest being piqued by TunnelBear and CyberGhost as free options when I was looking into this a while back, but ultimately I didn't have a need to actually set one up so I can't help past that. Free plans may have limits that might not work for a big download like this though; I think TunnelBear's free plan has a low data cap and CyberGhost will disconnect itself after a period of time.

Either way, if it's easy to set up a free one it might be a good way to just confirm Verizon's behaviors and at least give you something to call and complain about.
[Samsung Galaxy Nexus] Dirty_Jerz:
There was also a pretty big thread on Verizon's forums about throttling but I think the people (not Verizon employees, forum users) traced it to a router at the edge between the two's networks (Verizon and Google). Something along the lines of filled up ports or something. I'd set up a VPN for you here but I'm on FiOS as well. PM me if you want to give it a go and setup creds for you though.
[Samsung Galaxy Nexus] gtdriver0036:
hey all. Good to see there is still life in this thread. I have a friend of mine borrowing one of my Galaxy Nexii running FML 5.0 wouldn't mind getting the other one onto some kind of Shiny 5.0 it was really cool seeing that old phone fire up and do all the latest tricks.
[Samsung Galaxy Nexus] RW-1:
Sounds more like an external issue than something in your own gear BWG, but if you want, I would:

Power down modem/router and system.

Power up modem after 10 minutes (if it has a batt in it, remove for the power re-cycling), then after that has stabilized back on, power up router (if separate), then computer system.

Looking forward to any good things ahead shiny or FML, it's all good.
[Samsung Galaxy Nexus] AuroEdge:
On the latest version of ShinyROM, what are the automatic triggers for running TRIM i.e. what has to occur for the OS to run trim? Certain time of day? Plugged in charging?
[Samsung Galaxy Nexus] urphonesux:
Can anyone help me get WiFi tethering working on this ROM? I really need it because the WiFi on my campus is super weak. Thanks!
[Samsung Galaxy Nexus] AuroEdge:
Wi-Fi tethering operates on this ROM as is. I believe trim wasn't being ran. I downloaded lag fix, root required, and ran fstrim. The nand performance is again decent.
[Samsung Galaxy Nexus] urphonesux:
On my phone its stays stuck at "turning on hotspot"
[Samsung Galaxy Nexus] AuroEdge:
Are you on a clean flash of ShinyROM? I haven't ever encountered this problem
[Samsung Galaxy Nexus] afextwin:
[MENTION=2393080]baldwinguy77[/MENTION] Thanks again for your hard work.

I broke my GNex's screen about 9 month's ago and recently purchased a refurb'd GNex because I like it so much more than my S3/S4.

I was playing with FML's 5.0 beta build, and it's a ton of fun, but not good enough to be a daily driver.

So, I ended up pulling the board from my old broken Nexus and swapping it with my new(ish) Nexus.

Boy was I happily surprised when the phone booted up and everything was buttery smooth - just like I remember, running a ShinyROM build from February 2014 :P

Well, I'm on my way to updating recovery and clean flashing the latest build (080914?) and I just wanted to stop by and say thanks, and also, Google hates you.

"ShinyROM_toro... is not a commonly downloaded file, would you like to keep this file?" and only a discard button is present...wtf.

Anyway, I hope you had a good fall break and you get back up n running - I love the superclean, root free ROM you've put together.
[Samsung Galaxy Nexus] baldwinguy77:
Haha, I love the added security in Chrome with features like that, but I've experienced that happening with a few files in the past that weren't truly malicious. I'm not sure why that's happening, but I will definitely look into it. It's funny because based on the IP address reports for downloads, a considerable percentage has always come from IPs registered to Google (Google employees, perhaps?) ;) Anyways, I will try to get that figured out. In the meantime, I could look into mirroring them if anyone needs it, or you can temporarily disable that specific security settings in Chrome settings. I wouldn't personally recommend that, but if you do it just be sure to reenable it. Aside from that, thank you so much for the kind words :D I really appreciate it!

Also, a message for everyone: I think I finally got this Verizon FiOS thing figured out - something about having an outdated ONT, but also as soon as I kept calling and bringing up the speed issue it magically seemed to be fixed. Maybe something was wrong with my account and they fixed it without wanting to admit it. Anyways, I can download things from Google again! (Knock on wood) So, even though school started up again, my schedule is much more manageable and I've been taking a lot more on lately (web development company in my signature) and it's been going well! So I guess I should get off my high horse now, but the point is that I will download the source ASAP and start taking a look for real this time. It's going to be slow development, but sometimes that is the best kind for getting things right! Thanks for your patience!
[Samsung Galaxy Nexus] RW-1:
Gang,

A thank you to BWG, who did terrific work on Shiny for those who are on it, and who may stay on it.

For myself, I'm wrapping up one week on FML 5.0.2 with smitty's R6 kernel on it, and although the ROM/Device itself still has a bit of tweaking to do, I've made the transition to Lollypop.

Shiny still exists as a back up on my device should the need arise.

I'm on the FML thread and the kernel thread, and of course available by PM if need be. And I'll check the thread from time to time .... If BWG comes up with a 5.x version, I'm ready to try it hehehe.
[Samsung Galaxy Nexus] pkgnex:
I actually just reverted to Shiny because I kept experiencing terrible lag with FML / smitty after a few hours of up-time no matter what I did (seems to be memory allocation / flushing issues or something). During normal days I could just reboot, but I need a fast and reliable phone without frequent reboots next week since I'm travelling on a work-related mission, so I had to go back to 4.4.4. Don't get me wrong, MWisBest and Bsmitty83 are doing good work and things are progressing, it's just not nearly as good / fast / stable as Shiny 4.4.4 yet.

I'd love to see what BWG could do with lollipop!
[Samsung Galaxy Nexus] govindadas:
I've been on 4.1.1 forever because I didn't like 4.2. I had all kinds of hacks etc. My phone was getting so buggy... Shiny ROM saved me! Thanks! :good:

I flashed the no CRT mod but got stuck on the colored dot loading animation for about 10min and lost patience so flashed the ROM back over it. CRT was gone until reboot. I'm going to try and manually overwrite framework res via adb to see if that works. I used to play with aosp source and had figured out how to edit the code to remove the CRT. Those were fun days!

I really don't like the new android style with solid bright colors. But I'm gonna stick with it.

Thanks again! I'm so stoked to have dev still happening with this phone! I'm going into year 4 but would love a nexus 6. Gotta wait for a good used deal... Need to keep unlimited data...

* edit 02:

- about a week on the ROM and all good, a little lag in scrolling app drawer and a bit here and there, nothing major

- still can't get noCRT mod to work for the life of me... wiped cache/dalvic etc. just stuck on colored dot loading screen. re-flashing rom fixes it.

* edit 01:

- day 3 still good.

- hotspot works perfectly.

- a few weird random screen flashes, like a jolt of brightness when hitting the power button to turn the screen off. Nothing major.

- camera is quick to respond, flawless; before flashing this rom, I would take a photo and my camera would freeze up. that no longer is a problem!

- still need to figure out a way to get widgetsoid airplane mode toggle to work (android thing, nothing to do with this rom i believe).
[Samsung Galaxy Nexus] irish_711:
Is BWG working on a lollipop AOSP ROM?... I refuse to venture into 5.0 world without him. The couple ROMs I've ran have an incredible battery drain. *fingers crossed* When 5.1 is released, maybe out of his boredom, he releases an update.
[Samsung Galaxy Nexus] past_pluto:
The CM 12 with DDK 1.9 drivers has great battery life. Just make sure you adjust screen brightness down even in auto brightness.

I agree would be awesome to have a shiny lollipop but I do believe he has moved on from our device :(
[Samsung Galaxy Nexus] daytonahemi08:
Shiny-lollipop would be lovely...
[Samsung Galaxy Nexus] cowsquad:
Is anybody using this ROM?
[Samsung Galaxy Nexus] quickdraw86:
I still run it from time to time... You've obviously planned a follow up to your question were anyone to answer... Just ask outright and see if other users wish to respond or are able to help you resolve your issue.
[Samsung Galaxy Nexus] past_pluto:
If I were on my toro still this would be the daily driver. It was until I got the s4 I'm using now.
[Samsung Galaxy Nexus] ethanhunt123:
My Lg G2 died last week and I had to roll back to me old nexus. This ROM gave it new life and is allowing me to rely only my back phone as my daily driver. Thank you !!!
[Samsung Galaxy Nexus] irish_711:
It's my daily driver. I've tried to use some Lollipop builds, but my phone likes to bugger them off. This build has been my goto for quite some time. When I find a 5.+ build that my device agrees with, Shiny will probably fade, but until then, this is the best Kit Kat build.
[Samsung Galaxy Nexus] mastertech007:
I just rolled back to this rom from CM12.1. The lag was killing me. This has been and always will be the best KK rom out there. You will not be disappointed..
[Samsung Galaxy Nexus] hauckk@sfreserves.org:
this may be a stupid question is there any way to get a security update for this rom you'll probably laugh at me

but are you willing to do it over three years of no security commits makes me want to leave still the best rom for toro every other rom i've tried lags terribly
[Samsung Galaxy Nexus] KShion619:
BWG77 afaik is busy/gone, but if you feel like tweaking things a bit, Unlegacy Android KitKat is more stable and a bit quicker and has a recent Security patchset.

KitKat is no longer receiving security patches from google, but Unlegacy Android is the best you'll ever get, requires manual google apps installation.
[Samsung Galaxy Nexus] hauckk@sfreserves.org:
thanks but i don't own this device anymore :eek:
[Samsung Galaxy Nexus] baldwinguy77:
I suggest trying out the method described in the post above. I wish there were more I could do at this point, but I don't have many options beyond making different builds for each individual user :/ Sorry!
[Samsung Galaxy Nexus] RoxRedEye:
I clean flashed the new build on the 9th and everything seems to be just flawless. I flashed the latest franco kernel after the ROMs first initial boot up. My battery life is great, no complaints at all. Since the last build, I can say, I now have a new favorite ROM. Baldwin, again - thanks for this ROM man. You sir - are a gentlemen amongst crack flashers haha. Long live Shiny. I hope you continue to improve upon and keep it running beautifully. Awesome work bro.
[Samsung Galaxy Nexus] cyclingroo:
Which Franco Version?

Which Franco version are you running with the latest Shiny? On the last Shiny rev, I had trouble with Franco kernels (that were downloaded from Franco's site directly). So I've been using tinykernel instead. I would love to switch back to Franco, if possible.
[Samsung Galaxy Nexus] RoxRedEye:
I'm running r395 from the 4.4 folder. r395 from the 4.3 folder will cause a bootloop.

I haven't had a single issue with franco's kernel on this ROM.

Here's the link

http://192.241.177.15/GalaxyNexus/4.4/zips/
[Samsung Galaxy Nexus] jmagsho:
Check your location settings. I clean flashed to the new build today and noticed that location is defaulting to High Accuracy, which will eat your battery like nobody's business. Try setting it to battery saving mode and see how it goes.
[Samsung Galaxy Nexus] klobkelosh:
Yes, definitely defaults to high accuracy, but I won't set to battery saver as I need the gps often. The thing is that high accuracy gps set to on shouldn't result in battery drain when not using location and does not have any ill effect on many other roms. There's something wrong in this build that kills battery. I'm running omni right now, which has the same commits by devortex as shiny, and it doesn't have battery drain. Same with liquid. Something else is the culprit.
[Samsung Galaxy Nexus] jmagsho:
You're right. Something else is up. I'm seeing battery drain running around 16% per hour, most of which was at idle while connected to WiFi.
[Samsung Galaxy Nexus] baldwinguy77:
Did anyone try the build.prop edit that I detailed a few pages ago? The "commits" across ROMs are definitely not all the same, so I really can't go off of anything like that, and battery life is especially difficult because it's at least partially subjective.

Let me know if you guys try that or if you notice any patterns, get logs, etc. Thanks!

Haha thanks so much, glad to hear you're enjoying it! :)
[Samsung Galaxy Nexus] klobkelosh:
I didn't. I had to jump onto something more battery friendly for my $hitastic work Monday, but I intend to clean flash and retry with that change soon. Thanks for all your do baldy.
[Samsung Galaxy Nexus] baldwinguy77:
It's no problem, I understand :) Haha I hope work went well! Thanks for offering to try it out - if you have 7-zip or something similar you may be able to edit the build.prop before you even flash to make it easier, but do it however you want. I don't think the new telephony API and other telephony change would be causing the issue as I think that has fixed the data handoffs for almost everyone so I don't think it would cause battery problems, that seems backwards.
[Samsung Galaxy Nexus] klobkelosh:
Nah, work sucked. Good call on 7zip, I'll try that. I'm actually running omni right now and popped in the build.prop entry to see if I could force bad battery. No such luck. Hopefully I'll get a chance to reflash shiny this weekend. I love it with xposed, better than any other custom Rom, imho.
[Samsung Galaxy Nexus] jmagsho:
I didn't get a chance to try the build.prop change, but FWIW, I did swap out the kernel for pattyboi's Hybrid Remix 14 and battery life was considerably better (3.5-4% drain/hour vs. 14-16%/hour on stock).
[Samsung Galaxy Nexus] DroidOnRoids:
At this point, any custom kernel is better than stock lol Franco Kernel is doing great things for me.
[Samsung Galaxy Nexus] DroidOnRoids:
Update: As other people are reporting in the Shiny Rom Maguro thread, WhatsApp is force closing upon opening. I believe it's the build itself. Using Dalvik Runtime too.
[Samsung Galaxy Nexus] schnob:
I'm having root issues with the latest build. I flash the most recent SuperSU and still get a "no SU binary installed" error. Any suggestions? I've wiped a couple times and tried flashing it multiple different ways. ROM is solid as expected otherwise.
[Samsung Galaxy Nexus] asilentcivilian:
did you flash SU right after installing ROM in recovery?
[Samsung Galaxy Nexus] schnob:
Yeah, should I be flashing it after the first boot?
[Samsung Galaxy Nexus] asilentcivilian:
you can try it. I flashed SU in recovery right after the ROM flash. didn't run into trouble.
[Samsung Galaxy Nexus] crs7:
Running latest build . Everything is running great, not a single problem. Testing out a few kernels but exactly what I've been looking for. Thanks a lot
[Samsung Galaxy Nexus] baldwinguy77:
You can try flashing it after first boot but if that doesn't work you may want to try this progression:

1. Wipe cache

2. Wipe dalvik cache

3. Format /system

4. Flash ROM

5. Flash SuperSU 1.93

6. Reboot

It's either the app needing updated for the new telephony API or something with a new permission is coded improperly in the new telephony API. Is there any way you could get a logcat of the app crashing?
[Samsung Galaxy Nexus] baldwinguy77:
Thanks so much, that helps a lot! So, after looking through it, it's actually a pretty simply explanation. Here's what I've come up with:

With the new telephony API from Google (which definitely seems to improve telephony performance for the GNex), a new permission, android.permission.READ_PRECISE_PHONE_STATE, was added. Since this change is brand new, the WhatsApp developers haven't added that permission to their app yet. Because of this, the app no longer has permission to perform a certain task and crashes. I emailed the WhatsApp developers and informed them about this, so hopefully they will update their app to include the new permission. That is the only truly correct fix since this change will be included in future versions of Android, anyways. If the WhatsApp developers don't respond/can't add the permission (which is understandable), I think there are two options:

I can temporarily remove that change to the system, but removing the whole thing will also remove the benefits that came with the new change. I can try to remove just the permission part, but I'm guessing that will screw up other parts of the change.

I can try to mod the WhatsApp app so that it requests this new permission, but I don't want to go against WhatsApp/make them angry, and I don't know if you guys would like that.

I hope that all makes sense!
[Samsung Galaxy Nexus] wastedlife:
I think the best solution is to leave the change in. If WhatsApp does not update, the best temporary solution might be an Xposed module that forces the permission request. A similar module would be the one for the fitbit app that fakes the device check so that unsupported phones work.

Also, I'd like to say that this is the best 4.4 ROM I've used so far. All of the other ones have had major reboot bugs and other problems like data and MMS not working properly. So far I have not had an issue, thanks!
[Samsung Galaxy Nexus] Shadow Death:
Since you brought this up I decided to flash it again. It is extremely smooth. ?

Don't let phone idle fool you I did whole lot of texting today. That's why hangouts is up there in battery usage. If anyone is curious I haven't even flashed any kernels or made any tweaks. I literally just flashed it and setup the account. That was all.
[Samsung Galaxy Nexus] asilentcivilian:
I probably get like 6 hours of battery lol. lucky you
[Samsung Galaxy Nexus] kinfolk248:
Ok This is the question, which is a better option for this rom: Gravity box or Xposed?
[Samsung Galaxy Nexus] Shadow Death:
The only Gravity Box I know of Installs via Xposed.
[Samsung Galaxy Nexus] AuroEdge:
What type of battery are you using and how old is it?
[Samsung Galaxy Nexus] asilentcivilian:
I think its the stock Samsung battery. 3.7 Li-ion. I have 2 of them. I bought the phone off Craigslist with the batteries because my RAZR died.
[Samsung Galaxy Nexus] kinfolk248:
soooo Xposed and GB are the same? I thought they did the same thing but were two different entities...
[Samsung Galaxy Nexus] Maximinus I:
The Xposed framework is what gravity box uses to do what it does. Gravity box does nothing by itself.