Xoom 4G EOS ICS 4.0.3 Nightly (Stingray) - Xoom Q&A, Help & Troubleshooting

I have been updating my Xoom with the nightly builds since it started and have never had anything but awesome results with it.
I applied build 27 and started getting the coma sleep issue. I waited and applied build 28 and the same result. I rolled back to #26 and it has been smooth sailing again like all of the previous builds.
I was wondering if anyone else has been getting the coma sleep starting with #27 or if my Xoom is an island unto itself.
I know builds 27 ans 28 have been centered around getting NFS working and include an updated kernel for it. I am hoping I am not stuck at #26 because my Xoom is a NFS prude.
I will apply the next build and see what happens. I will start logging and see what it shows if forever sleeps again.

Oh and to all of the devs and others posting in the development thread for this build....I am not able to post there because I am under 10 posts still. Though I believe this is my tenth post, so I will click on over and see if I can post there now.

Related

[Q] Team Kang ICS Wingray and Stingray Builds

Anybody try either of these yet? I've tried the Droid Inc2 (Vivow) build and it's great. Thats how I found the Xoom builds. I haven't seen anyone officially post them in the Xoom Development section. Milestone build date is 2/7/2012 . Might have to give it a try.
https://sites.google.com/site/androidopenkangproject/downloads-1/milestones
slacka-vt said:
Anybody try either of these yet? I've tried the Droid Inc2 (Vivow) build and it's great. Thats how I found the Xoom builds. I haven't seen anyone officially post them in the Xoom Development section. Milestone build date is 2/7/2012 . Might have to give it a try.
https://sites.google.com/site/androidopenkangproject/downloads-1/milestones
Click to expand...
Click to collapse
I have used their crespo (Nexus S) daily for awhile now and it is the best ROM I have ever used period.
The wingray version however needed some work...I say needed because the version I tried still had 3G icons etc in the status bar and other issues. These guys (Roman) are
frikkin OCD on perfection so when this was overlooked I stayed away til now. I dont even think he has a Xoom.
I'm sure they will get it caught up and then will simply kick ass like the rest of their work. I am about to try the latest build 25 and will report back.
nadiros said:
I have used their crespo (Nexus S) daily for awhile now and it is the best ROM I have ever used period.
The wingray version however needed some work...I say needed because the version I tried still had 3G icons etc in the status bar and other issues. These guys (Roman) are
frikkin OCD on perfection so when this was overlooked I stayed away til now. I dont even think he has a Xoom.
I'm sure they will get it caught up and then will simply kick ass like the rest of their work. I am about to try the latest build 25 and will report back.
Click to expand...
Click to collapse
I'm glad to see I wasn't the only one bugged by the 3G signal showing in the status bar on Wingray. It wasn't a huge deal, but one of those little things you always notice once you see it the first time. There were a few other things, but overall it's a nice build.
I also use AOKP on my Nexus S as a daily driver and I'm very happy with it. No big issues to call out. Once the wingray builds progress a bit more and those few little bugs are worked out, I'll most likely switch to it as my main rom.
Build 25 - 3G icon bars still there.... feels superficial however I didn't test much further . I will continue to periodically check in on them... but like I said - for this aspect to be overlooked then they're not paying attention to wingray for some reason
I am used the Kang rom for a while primarily because it has volume button wake built in. But after a while that tweak just stopped working so now I'm back on Bugless Beast for Xoom.. There's still plenty room for improvement for the Kang rom so I'll try it again at a later stage.
I've built from source and removed the 3G radio icon. It's something I'm sure they'll get to. I noticed someone posted a bug report on that to them already. I posted what they need to do to get rid of it. I might post my build but only after getting permission to do so from them. Run's great with my oc kernel.
Well from what I see they (Team Kang) have discontinued their Wingray builds. Rootz wiki has a pitiful thread that has dwindled and I see only a Stingray release for Xoom as far as the latest build 30.
WTF !
Anyone know whats up?
Great so far but one question to those using it.
Allow apps to write to SD card is in the feature list.
How do I access this? Using various apps I can only write to media memory. Even if I change the path to /mnt/external1/. It just creates that folder within the internal memory.
Any help would be appreciated.

CM7 Nightly's back in action :D

While it's no cm9, it looks like there's still a lil og love going on in the nightly section
http://download.cyanogenmod.com/?type=nightly&device=sholes
Is there a place where I can view nightly change logs?
A2Aegis said:
Is there a place where I can view nightly change logs?
Click to expand...
Click to collapse
http://cm-nightlies.appspot.com/?device=sholes
Oops - this is not for Droid X
taptaptouch said:
http://cm-nightlies.appspot.com/?device=sholes
Click to expand...
Click to collapse
Sadly, that link isn't working anymore and the site that is suggested is only for CM9 updates.
The good news is that nightlies for CM7.2 continue!
Wish I had a changelog to read, though.
-CM7 on DInc2
New July 8 nightly is out.
I flashed it last night, but without a changelog I can't tell what's improved.
Mostly my OG just sits on the table. :'(
-CM7 on DInc2
7-22
-CM7 on DInc2
I'm getting wifi crashing/rebooting the phone on the latest nightly.
Any version of CM7 that doesn't? Looks like cm 7.1 rc1 does it as well (steel droid).
need wifi. Fail?
pkopalek said:
I'm getting wifi crashing/rebooting the phone on the latest nightly.
Any version of CM7 that doesn't? Looks like cm 7.1 rc1 does it as well (steel droid).
need wifi. Fail?
Click to expand...
Click to collapse
I have no problem with wifi. Do you wipe dalvic and cache when you flash updates?
That's the minimum to do. If you are coming from a different ROM entirely then anything less than a full wipe is risky.
-CM7 on DInc2
Nightly 9-30 has borked my D1 and my DInc2.
D1 would not even begin the update in recovery, just froze. Battery pull and now it won't boot. Stuck on M logo.
Booting into recovery gets me the top level menu, but any selection leads to a blank screen. Press power from the blank screen and you're back at the menu.
Managed to get the Dinc2 restored, but now have no network available, only wifi.
Crap.
-CM7 on DInc2
phonetool said:
Nightly 9-30 has borked my D1 and my DInc2.
D1 would not even begin the update in recovery, just froze. Battery pull and now it won't boot. Stuck on M logo.
Booting into recovery gets me the top level menu, but any selection leads to a blank screen. Press power from the blank screen and you're back at the menu.
Managed to get the Dinc2 restored, but now have no network available, only wifi.
Crap.
-CM7 on DInc2
Click to expand...
Click to collapse
Try this for your D1 (second section)
Hi, thanks much for the reply.
After more fooling around with the D1 I found that the recovery menus would respond properly from the keyboard enter button. I was able to restore the previous version of the nightly.
I tried flashing the latest cm nightly from two different download sources for the DInc2, but neither would install.
So, I am sufficiently recovered but not running the latest version. :'(
The lack of network on the DInc2 was me being dumb- the battery cover is the phone antenna. Doing lots of battery pulls? Don't expect network with the cover off. Sigh.
sent via DInc2 on ICS
---------- Post added at 09:15 AM ---------- Previous post was at 09:04 AM ----------
A2Aegis said:
Is there a place where I can view nightly change logs?
Click to expand...
Click to collapse
This is the best I have found
http://review.cyanogenmod.com/#/q/status:merged+branch:gingerbread,n,z
sent via DInc2 on ICS
A2Aegis said:
Is there a place where I can view nightly change logs?
Click to expand...
Click to collapse
This link will work, as well.
http://changelog.bbqdroid.org/#sholes/cm7/next
-CM7 on DInc2
The "weeklies" continue, but I haven't pulled out my old D1 from the desk drawer in a while. :-[
-CM7 on DInc2
phonetool said:
Hi, thanks much for the reply.
After more fooling around with the D1 I found that the recovery menus would respond properly from the keyboard enter button. I was able to restore the previous version of the nightly.
I tried flashing the latest cm nightly from two different download sources for the DInc2, but neither would install.
So, I am sufficiently recovered but not running the latest version. :'(
The lack of network on the DInc2 was me being dumb- the battery cover is the phone antenna. Doing lots of battery pulls? Don't expect network with the cover off. Sigh.
sent via DInc2 on ICS
---------- Post added at 09:15 AM ---------- Previous post was at 09:04 AM ----------
This is the best I have found
http://review.cyanogenmod.com/#/q/status:merged+branch:gingerbread,n,z
sent via DInc2 on ICS
Click to expand...
Click to collapse
Which build are you using? Thinking about updating my droid1. Haven't updated in a long time.
Cheers,
Rich
Sent from my Transformer TF101 using Tapatalk HD
rholm said:
Which build are you using? Thinking about updating my droid1. Haven't updated in a long time.
Cheers,
Rich
Sent from my Transformer TF101 using Tapatalk HD
Click to expand...
Click to collapse
Hi-
My droid is semi-retired. It comes out of the drawer every couple of weeks for some play time.
I always ran CM7 nightlies on it. There's so little going on with CM7 that they are now on a "monthly" release schedule. Very reliable, no issues for me. I also ran Prime's kernel and overclocked a bit. Also the V6 SuperCharger script from zeppelinrox.
The ROM that gets a little bit more attention is Steeldroid. I never tried it, but certainly would. Lots of good responses on it.
Good luck with your OG Droid!
-MROM on DInc2
phonetool said:
Hi-
My droid is semi-retired. It comes out of the drawer every couple of weeks for some play time.
I always ran CM7 nightlies on it. There's so little going on with CM7 that they are now on a "monthly" release schedule. Very reliable, no issues for me. I also ran Prime's kernel and overclocked a bit. Also the V6 SuperCharger script from zeppelinrox.
The ROM that gets a little bit more attention is Steeldroid. I never tried it, but certainly would. Lots of good responses on it.
Good luck with your OG Droid!
-MROM on DInc2
Click to expand...
Click to collapse
Yeah, I got the last Nightly running on my trusty HTC Incredible. There's been one more new cm7 nightly (20130301) but there hasn't been one released thus far since. I wonder if CM is going to announce a closure on CM7 channel, or it'll just be longer gaps between nightlies? Honesty the CM7 nightlies have been extremely stable
nokiabolt said:
Yeah, I got the last Nightly running on my trusty HTC Incredible. There's been one more new cm7 nightly (20130301) but there hasn't been one released thus far since. I wonder if CM is going to announce a closure on CM7 channel, or it'll just be longer gaps between nightlies? Honesty the CM7 nightlies have been extremely stable
Click to expand...
Click to collapse
Seems that there are still some fixes sifting down to CM7 once in a while. I expect they will stop working on it at some point, who knows when. It won't get any further features, that's for sure.
It's a fantastic piece of work - very robust and stable, and the root source for countless custom ROMs.
Gingerbread still holds a large percentage of the android OS currently in use. Of course this will continue to slowly decline as devices are replaced.
Such is life.
-MROM on DInc2
The device that is just too good to die.
It's nice to see deprimed mentioned after all this time
I'm trying to get my friend to find his OG Droid so I can tinker with it. Was such a classic.
Sent from my RM-860_nam_usa_100 using Tapatalk

Who had CM9 before going to ten?

Long story short.
When SGS3 first came out and there were CM9 Betas, I tried them out, no major issues until I lost my IMEI, Odined back to stock, Restored no big deal. Fast forward to two days ago. I tried a CM10 Nightly, in which I F'ed up bigtime, Leaving me in the middle of work, with an inaccessible internal SD. Luckily, I still had a CM-9 20120719 Unofficial and a gapps-ics 20120429 on my external. Flashed them both had CM9 again. First thing I did was get Rom Manager, DL the 09-01 Nightly and gapps 4.1. Dirtly flashed it right over ( I intended on ODIN'ing when I got back home anyway) Boots up....
STABLE AS EVER. IMHO just as stable as CM7 on my Droid X (incredibly stable), better yet, no major bugs that many people have been reporting. Only minor issue I noticed was music being paused via notifications and currently that isn't an issue, but I've been playing with settings and apps all day, not sure what fixed it.
The reason I pose this question, is because in the Dev forums (which I'm not allowed to post in...) there are many people who say this is stable and clean, and many other people complaining about everything under the sun. My theory is that because I had to flash CM10 over CM9 I am seeing stability and no issues. 2 Days of love
Has anyone else flashed 10 over 9, and running stable? Has anyone else done so and had major issues? Am I just a lucky SOB?
I already tried finding out the status of cm9 but apparently it's a ghost ROM and nobody gave me an answer. There isn't even a thread in the dev section for it. The only thing I could find was 1 post saying it was a stable release but no links or any other info. That's it. Everybody seems to be drooling over cutting edge bugged filled nightlies of cm10 to care.
Yeah, I ran AOKP M6.1 until things started rolling on Jelly Bean. Only issue I had was no MMS.
If you google search CM9 for SGS3 there is a ton of info for it.
" To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
so I can't post links. but look for Droid Life, there is an install guide on it/
there are also install vids on youtube.

[Q] CM 10.1 Nightly Force Closes

I'm not sure if this is the right place for me to post it... On the Tab 2 forum there is an area for this in the development area, but I couldn't find it. Sorry in advance if this doesn't go here.
I just installed the nightly for the 20th of CM10.1 and I'm getting a lot of SystemUI force closes. Wondering if anyone else was having this issue or if it was just me?
I know... It is a nightly so I'm not fussed about it but if it is just me, I'll look into fixing it on my end but if others are having issues with that ROM then I"ll probably flash back to the 18th or something.
Thanks.
titanshadow said:
I'm not sure if this is the right place for me to post it... On the Tab 2 forum there is an area for this in the development area, but I couldn't find it. Sorry in advance if this doesn't go here.
I just installed the nightly for the 20th of CM10.1 and I'm getting a lot of SystemUI force closes. Wondering if anyone else was having this issue or if it was just me?
I know... It is a nightly so I'm not fussed about it but if it is just me, I'll look into fixing it on my end but if others are having issues with that ROM then I"ll probably flash back to the 18th or something.
Thanks.
Click to expand...
Click to collapse
There is another thread for cm10.1 issues and whatnot, its not a big deal to me, but I've seen people freak out! Haha
Anyways, lately there's been a lot of issues with the nightlies lately. The new CM (around march 18th) came with a new kernel version, from version 3.0ish or something to 3.43 ish?? Anyways, the new kernel fixed some issues, but also caused some new issues since its still fairly new from my understanding. I've had one system ui force close, and MANY freezes. Also, there for a while it would freeze during calls, but I haven't had one of those for a while now.
Sent from my SCH-I535 using xda app-developers app
XdrummerXboy said:
There is another thread for cm10.1 issues and whatnot, its not a big deal to me, but I've seen people freak out! Haha
Anyways, lately there's been a lot of issues with the nightlies lately. The new CM (around march 18th) came with a new kernel version, from version 3.0ish or something to 3.43 ish?? Anyways, the new kernel fixed some issues, but also caused some new issues since its still fairly new from my understanding. I've had one system ui force close, and MANY freezes. Also, there for a while it would freeze during calls, but I haven't had one of those for a while now.
Click to expand...
Click to collapse
Thanks for the information... Yeah, I actually had more freezing when I was stock then with the CM builds. Where might I find the other thread? I must be blind to not have seen it.

End of CM - options?

It's pretty clear that the road forward for CyanogenMod is a dead end at this point. While it's no huge loss for me (been running a stock Stylo 2 Plus lately, and my Relay is just a backup and occasional wireless camera controller at this point), I wouldn't mind switching out ROMs on the Relay, at least if there's something still maintained.
I was afraid something like this would happen to CM once Microsoft got its grubby little paws into the picture. Looks like Cyanogen effectively got Elop'd just like Nokia did.
A month or so back, I was getting ready to buy my wife and myself a pair of new phones to replace our Relays. I was basing my selection on CM-14.1 support. Things got confusing, and I postponed the whole matter until some time next year. Boy, and I glad I delayed.
Of course I still have to select a replacement for the Relay - one that is really supported for the long run - which may still push me into something CM-like. Now to figure out what that is.
Well if you want to be safe just go Nexus, only the Nexus one and Nexus s have lost support, galaxy Nexus and up still has developers not to mention google will support each for 2 years plus
Other safe bets are the real popular devices such as galaxies and even the OnePlus community
If you want a hardware keyboard I would suggest to learn development as you will always be limited and haven't seen one with good support since HTC g2
Hi there, why not port Ubuntu Touch? I did read that it is quite easy to port ubuntu touch to cyanogenmod supported phones...
I'm still in the process of learning how to do that... but there are no real reference on doing that and building/brewing a rom would be my first.
You certainly could but I'm not sure if that ever works too well with a HW keyboard, at that point may as well move on.
There are many of options on what to bring over but few still use phones like these, in truth i haven't touched any of my 5 hw keyboard phones in at least two/three years, i miss them but have learned to live without...
But i did just read BlackBerry has a new one soon, may not get much support though, priv was a bit of a bust...
*sigh* i know you are right. Beginning this year i started using the Nokia e7 Communicator again on custom Symbian ROM. After a few not solveable problems i imported the Relay short after as my last ray of hope. Is it that dificult as a manufacturer to build a landscape slider with 5 key rows? Just one decent powered would be enough. I don't care if i use QNX, Android, iOS or Windows Mobile, the phone is just a phone for me. I don't need 5 thousand sounboard fart apps..... god damn...
Make last Relay build available???
It appears that Cyanogenmod is offline, so nothing new is coming - ever. That said, I'd seen that things were going to go offline at the end of the year, and was rather hoping to pick up the "auto-integration" of the final AOSP merges into CM-11. I'm assuming this happens, because I don't believe any person has touched this since TDM left at the end of July.
I'm currently running a nightly I built on Dec 3 of this on my wife's and my phones, and have had no problems. I'm willing to make this build available for anyone who wants a small update for their Relay.
There's another question... How do I find out the date of the final update? I ran my build script again this morning, and got a result, but since the CM servers are dead, I suspect it just ran through its paces. I know that the Dec 3 built I'm running carries a date of 20161126 and an Android security patch level of November 1, 2016.
My last builds are very little different in file sizes, but as I sift through the build directory, I see a bunch of stuff with a Dec 15 date, so I believe I may have picked up some fixes on that build. I see that the servers actually went offline apparently on Dec 25, which also matches some of the date stamps I see in my build tree.
So - Can someone tell me a distinctive spot in my build tree where I can find out what the actual date of this stuff is? I suppose I'm going to try flashing this build one of these days, to see if there is anything better than what I've got on the phone now. If so this will be the last, best build of CM-11 for the Relay.
I will make one or both of these builds available, if there is interest. I'm not quite sure how to do that, where, etc. I have a basic Dropbox account, though I see that they will be phasing out the Public folder in April. That's a start, or I'm open to suggestions.
phred14 said:
Make last Relay build available???
It appears that Cyanogenmod is offline, so nothing new is coming - ever. That said, I'd seen that things were going to go offline at the end of the year, and was rather hoping to pick up the "auto-integration" of the final AOSP merges into CM-11. I'm assuming this happens, because I don't believe any person has touched this since TDM left at the end of July.
I'm currently running a nightly I built on Dec 3 of this on my wife's and my phones, and have had no problems. I'm willing to make this build available for anyone who wants a small update for their Relay.
There's another question... How do I find out the date of the final update? I ran my build script again this morning, and got a result, but since the CM servers are dead, I suspect it just ran through its paces. I know that the Dec 3 built I'm running carries a date of 20161126 and an Android security patch level of November 1, 2016.
My last builds are very little different in file sizes, but as I sift through the build directory, I see a bunch of stuff with a Dec 15 date, so I believe I may have picked up some fixes on that build. I see that the servers actually went offline apparently on Dec 25, which also matches some of the date stamps I see in my build tree.
So - Can someone tell me a distinctive spot in my build tree where I can find out what the actual date of this stuff is? I suppose I'm going to try flashing this build one of these days, to see if there is anything better than what I've got on the phone now. If so this will be the last, best build of CM-11 for the Relay.
I will make one or both of these builds available, if there is interest. I'm not quite sure how to do that, where, etc. I have a basic Dropbox account, though I see that they will be phasing out the Public folder in April. That's a start, or I'm open to suggestions.
Click to expand...
Click to collapse
I think we all as the last battalion of the Galaxy S Relay 4g would really appreciate if you could share your build. :fingers-crossed:
I just loaded today's build, though I haven't tested it much yet.
The Cyanogenmod version is 11-20161129-UNOFFICIAL-apexqtmo
The Android security patch level is Nov 1, 2016
The Kernel version is Sat Dec 24 15:10:38 EST 2016
So I guess I didn't get a new AOSP, nor new CM-11. But I did get a new kernel? I'd built a few times between then and now, so it looks like that's that.
I'll do a bit of testing with this one, then see if I can get it up to Dropbox Public, even if only for a quarter.
phred14 said:
I just loaded today's build, though I haven't tested it much yet.
The Cyanogenmod version is 11-20161129-UNOFFICIAL-apexqtmo
The Android security patch level is Nov 1, 2016
The Kernel version is Sat Dec 24 15:10:38 EST 2016
So I guess I didn't get a new AOSP, nor new CM-11. But I did get a new kernel? I'd built a few times between then and now, so it looks like that's that.
I'll do a bit of testing with this one, then see if I can get it up to Dropbox Public, even if only for a quarter.
Click to expand...
Click to collapse
Hi phred14, sorry to bother. Did you manage to upload that last nighly? Can you tell me if everything you test works? In the past I tried CM and was having issues with Mic, GPS and Camera, so i revert to stock.
Thanks in advance!
ninguno2 said:
Hi phred14, sorry to bother. Did you manage to upload that last nighly? Can you tell me if everything you test works? In the past I tried CM and was having issues with Mic, GPS and Camera, so i revert to stock.
Thanks in advance!
Click to expand...
Click to collapse
Yes, it's uploaded to my Google Drive with public access. I uploaded both Dec 4 and Dec 29 versions. I did a bit of specific testing with GPS and Camera on the Dec 4 version, but have not tested those functions on the Dec 29. I'm running Dec 29 now, so it does what I need - acts like a phone, texts, does wifi, and does stuff over data - and I don't know that any other functions don't work.
Do you have GPS working now? I believe that there was a specific "era" that borked the GPS in a persistent way. If you did that, which I did, you need to backflash to stock, or at least JB, then there is a procedure for flashing new. I've done this, and have working GPS.
The links to my stuff are on a separate thread under "Development", titled "Lineage OS", which is the successor to CM. We can discuss more if you're still interested. I can also take my current flash and do a bit more testing, when I have time. (Maybe not soon - we're getting work done on the house, and are in the process of moving out for a few weeks.)
phred14 said:
Yes, it's uploaded to my Google Drive with public access. I uploaded both Dec 4 and Dec 29 versions. I did a bit of specific testing with GPS and Camera on the Dec 4 version, but have not tested those functions on the Dec 29. I'm running Dec 29 now, so it does what I need - acts like a phone, texts, does wifi, and does stuff over data - and I don't know that any other functions don't work.
Do you have GPS working now? I believe that there was a specific "era" that borked the GPS in a persistent way. If you did that, which I did, you need to backflash to stock, or at least JB, then there is a procedure for flashing new. I've done this, and have working GPS.
The links to my stuff are on a separate thread under "Development", titled "Lineage OS", which is the successor to CM. We can discuss more if you're still interested. I can also take my current flash and do a bit more testing, when I have time. (Maybe not soon - we're getting work done on the house, and are in the process of moving out for a few weeks.)
Click to expand...
Click to collapse
Hi phred14, thanks for the quick answer.
Yes, my GPS is working great in JB (I'm using the last offical stock 4.1.2 T699UVBOH1_T699TMBBOH1_TMB), so I suppose i don't need a special procedure for the gps, right?
I already found the links you mention, as I understand from your answer, the camera works ok with the Dec 4 version? Can you tell me if the mic works ok with the version you're running? I remember that when using CM in the past, voice notes that i sent with whatsapp were muted (or tooo quiet) showing that the mic wasn't working. Reverting back to JB fix that too, as with the GPS.
Do you have some kind of updated guide/procedure/backup you follow before flashing CM, being I'm still at stock rom (i remember there was one on the old CM wiki)? I would really like to test your CM following the right steps.
Besides, i found another post you made about modem fixes (https://forum.xda-developers.com/showpost.php?p=63925086&postcount=20) is that still needed? As the link for RelayMC5modem.zip file is not working.
Best,
phred14 said:
A month or so back, I was getting ready to buy my wife and myself a pair of new phones to replace our Relays. I was basing my selection on CM-14.1 support. Things got confusing, and I postponed the whole matter until some time next year. Boy, and I glad I delayed.
Of course I still have to select a replacement for the Relay - one that is really supported for the long run - which may still push me into something CM-like. Now to figure out what that is.
Click to expand...
Click to collapse
Try going for something that's supported by LiquidSmooth or other custom ROMs. CM was the best, no doubt. There will always be options.
That's the beauty of Android as an OS. I'm proud of my contribution and maybe I might do more in the future. Albeit in a lesser light than FB, I see Google as a info hog.
Among devices, you should try either Nexus or older, unlocked Samsung devices.

Categories

Resources