yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Thank you for the suggestions. Anyone tried Mobilicity? I Heard that they are good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Galloway:
I've been with Telus since 1996. I haven't had any major issues with them. Their coverage is great when not in a major center. I think all the carriers have good and bad. I have friends on Wind and they love it but they also don't regularly travel to rural areas where I need service to be reliable. I have a couple issues with customer service but I think that could just be isolated to the individuals I was dealing with on those particular occasions. Overall I am happy with Telus and have no reason to change at this time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Devhux:
Been very happy with Koodo since switching to them a few months ago (was paying too much with Bell for what I was using the phone for).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Please cast your vote.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lutinx:
Rogers......never

I was with Rogers for 3 years and i accpet another 3 years contract .......the 5 first month i got major prob with the billing.....Never the same amount ( was told to be 76$per month....then they charge me 268$)

And after 5 months, my S3 crash cannot reboot....so i ask them for a repai , they told me it was the mother board..so 300$ after few calls the price drops at 250$.....and they offer me to broke the contract for 300$ if i want...

So i broke the contract and after few weeks , a little repair cellphone open near ..i ask them how much to repair the phone ...they charge me 60$ and unlock....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Wow. :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
No contract with fido for the past 5 years. No complaints. I find if you don't sign a contract and the carrier knows you can walk away at any given time, they tend to be more flexible and helpful if/when you have billing issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Sounds pretty good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Wonder why so many Telus votes.... Most people I know hate them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kevindee:
I've been with Rogers for a while, and they are okay. Still have the 6GB/$30 data plan from a couple years back. Sad thing is I pay $65/month and don't even have caller ID. But the coverage and LTE speeds are great in my area.

My dad is currently with Mobilicity using a Note 2, and it is HORRIBLE! The coverage is absolute garbage (we live in the GTA). In the house, he has 2 bars, where normal phones have full. He complains about all the dropped calls he gets. Plan comes with "unlimited data" but its only hspa, and since the signal is so bad, the highest speed he gets is like 1 Mbps if lucky. He's gonna leave, and go back to Fido or try Koodo.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Is Fido or Koodo any good?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kevindee:
My dad was happy with Fido for years until he went to a trip overseas and he came back to a $1000 bill due to roaming, even though he never used the phone with the Fido sim inside. Other than that incident, it's pretty good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Did he get a refund?
[Nexus 4 Q&A, Help & Troubleshooting] bleuwave:
So I love android but I hate the dark everything ui and I am wondering if there's a much lighter theme with white and brighter colors

I am running the latest aokp based pacman rom.

Tks

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] randomnoob83:
Cm 10.1 holowhite theme
[Nook Color Android Development] mateorod:
How about something new?

I am pleased to present, three years after the device's release...

AOSP 4.2.2 r1.2 for Nook Color

For this first release, I wanted to keep this as close to straight AOSP as I could. The device and kernel tree are identical to the the one in the CM10.1 release. There is a three year history of maintainance and improvement from the NookieDevs. Without that group of gentlemen, we would all be using ManualNooter, so be thankful. This project, and AOSPA as well, are not possible without them.

This is a straight a port to AOSP as a device with our boot parameters could hope for. Let me know what you think. The deviations from stock AOSP are minimal and almost wholly hardware related...a list is on a following post.

Note: these are random Google image results, not screenshots. I have not enabled native screenshots yet, and have no intention of buying an app to do it now. It's AOSP, you guys are familiar.

The only thing I added to this build that wasn't necessary or direct from AOSP was that I embedded Superuser, because ROOT! (and things just work more smoothly if it ships with the SU stuff handled.)

I think the performance is actually really nice, let me know.

Bug List

Nothing jumps out at me. Let me know. (Please check if you are reporting a bug with this build, or one from AOSP upstream. Google helps.)

Downloads

Rom is here.

Gapps are here.

I may decide to enable update notifications from Goo Manager...I haven't decided. I don't expect to update this as often as PA, not until 4.3 drops anyhow. But an update or two is for sure coming.

The Future

We can add some common-sense extras to this rom...but I do not want to spend a bunch of time and effort skirting the line between this and CyanogenMod. We already have CyanogenMod...it's awesome. Having said that, I am willing to add some basic extras. Post your thoughts about this issue in the thread...the more we add, the further from AOSP we go. Options include:

Performance Settings

MTP/PTP

Screenshots

Power menu (reboot etc.)

Requests may be considered (no promises...my plate is already pretty full. But contributions from the community are treasured...see the next post for source code info)

Thanks

NookieDevs (fat_tire, nemith, eyeballer and steven676 especially)

TeamWin for the vast amount of free hosting they provide me (and so many others)

inportb, koush

Leapinlar and RedneckReg for the replacement device.
[Nook Color Android Development] mateorod:
Scroll down for build guide

Technical info for source code enthusiasts

.

https://github.com/mateor/android/tree/aosp-4.2

CM projects used:

build

system/extras

vold

The above are all related to either the Nook's unique boot (having a uboot and MLO) or the partitioning scheme in the emmc. I intend to change to using the AOSP versions of those projects with the needed changes cherry-picked. Almost all of the commits we need were written by our own nemith and dalingrin.

hardware/ti/*

frameworks/av

frameworks/native

I have not decided what I will do with frameworks/av(whether I will pull out the OMAP stuff from that project or leave it as is), but the other hardware/ti handling will likely remain as the CM versions. I will peek at a diff, but the odds are high that we will stick with CM version there.

android_device_bn_encore

android_kernel_bn_encore

These two will 100% closely mirror the CM versions. I had to make some no-brainer changes to device before building...that will likely be the end. Thanks and credit to NookieDevs, especially Steven676 for 4.2.2.

Omap aside, my experience showed me that we only needed 15-20 changes to AOSP to port. So we will try and dial it back to just the barest changes necessary as an intellectual exercise.

Contributions from the community are welcome...the branch naming is all over the map right now...look at the manifest linked above for definitive answers about the source code used.

Thanks.

Build Guide

(perfect for first-timers. Support can be requested in the thread)

These instructions are for 64 bit Linux environments, try VirtualBox if you don't use Linux normally.

Take 15 minutes and follow the beginning of this guide. if you don't have ADB set-up, it will take longer, but that is just for downloading the SDK.

If you need help installing the JDK on Ubuntu (or another system with apt-get) do this (the absolute easiest way)

cd ~/
wget https://github.com/flexiondotorg/oab-java6/raw/0.2.7/oab-java.sh -O oab-java.sh
chmod +x oab-java.sh
sudo ./oab-java.sh
sudo apt-get install sun-java6-jdk

When it gets to the step to intialize the repo (repo init -u ETC.) STOP, and come back here, You are done with that guide, forever. Those steps only need to be done once.

Enter:

[FONT="Courier New"]repo init -u git://github.com/mateor/android.git -b aosp-4.2[/FONT]
[FONT="Courier New"]repo sync[/FONT]

If you experience fetch errors during the repo sync, change the command to repo sync -j4 -f. If they still occur, then repo sync -j1 -f.

This will take a long time, do it before bed, or family time, or go eat.

When the sync is done

. build/envsetup.sh
lunch full_encore-userdebug
make otapackage

You're done!

When it is done compiling, your ROM will be waiting for you at out/target/product/encore.

Fat-tire says building your on rom makes you an Android ninja, so you know it must be true. That means that if you don't try, you are admitting you don't want to be a ninja. Which reveals you to be the geek you already are but with loser rubbed all over you. Why else are you on XDA if not to learn?
[Nook Color Android Development] eyeballer:
Wow! Amazing work mateorod! I know we personally have discussed this project many many times and I'm glad you were able to dedicate some time to pulling it off, sorry I haven't been around as much lately.. life in the way but will definitely give this a look :)

Congrats!
[Nook Color Android Development] cammykool:
badass!!!!!

coulkd you add the option to edit quiccktoggles
[Nook Color Android Development] racks11479:
Wow! Awesome stuff mateorod! Looks like you've been pretty busy here. Gonna give this a go for sure!

Thank you for keeping our little device still alive, kicking and fresh! :)
[Nook Color Android Development] SCrid2000:
Intriguing.

Not only am I checking this out, but the goo.im link wasn't working so I'm building a rom from source for the first time :)
[Nook Color Android Development] AgentCherryColla:
Would an AOSP base be good for a AOKP port, or would Cyanogenmod be better?
[Nook Color Android Development] mateorod:
Use AOSP, for sure. AOKP is AOSP-based now, except for the hardware implementation (I.e. the hard stuff) done by CM and their device maintainers. But definitely use my aosp-4.2 manifest as your base. All the changes are very specific...you must use my forks of those CM projects not simply the CM-10.1 versions. (that probably goes for the device tree as well).

A good example is vold. CM-10.1 vold is not backwards compatible with the AOSP repos...there is some undocumented dependency in another project. I could go on and on...deviate from my choices at your peril.

However, swapping out the AOSP repos (I.e. anything straight from aosp) with AOKP repos should work fine. Krylon stalled out on an AOKP build for the Nook...I think this manifest will allow you to be successful. Ask any questions you like...if I can answer I will.
[Nook Color Android Development] AgentCherryColla:
All this is really missing is battery percentage, and performance settings. I like built in performance settings, I feel it take up less ram (vs setcpu).

::-::-::-::-::-::-::-::-::-::-::-::-::-::
[Nook Color Android Development] geeve420:
Okay, I have to ask. Any guides on flashing this to emmc? I was running CM7 on emmc (Got stale), went back to stock 1.4.3, tried rooting but could never get full market, Then saw this and it looks awesome and would love to go for a spin on it. I have the zip files ready to go and a CWM sd card, but I need to know how to get it installed on emmc.

I am on pure stock 1.4.3

Thanks

Geeve
[Nook Color Android Development] eyeballer:
If you have everything on a CWM sd card then just flash it :)

You can follow my (slightly outdated but mostly valid) guide over here: http://xdaforums.com/showthread.php?t=1030227 Just replace the CM stuff with the stuff from this thread.
[Nook Color Android Development] geeve420:
Thanks! Gonna give it a go when I get home...

Geeve
[Nook Color Android Development] xflier:
I gave it a try with a clean install. It is actually very impressive. it has smaller foot print, boot up quicker, runs smoother and faster. I think it is perfect for such old device compared to CM10.1, I would have it for daily usage after try it for few days.

I installed it in SD card (EMMC has CM10.1 RC5), and I don't see upgrading android even when I boot from this ROM to CM10.1 (not sure why).

One thing might need some attention is the storage in settings crashes. Again, not sure if it is due to installed in SD card or not. However, it is not a big deal to me.

Another couple of things noticed, it has color band, and youtube won't play HD videos. I really don't care that much compared to the speed of this rom.

Thanks a lot for this great ROM. it is a better choice for my Nook Color.
[Nook Color Android Development] geeve420:
Not just you. Have it installed on emmc and storage crashes in settings for me as well. I have the color bands too. Haven't tested YouTube yet though....

Great ROM so far! Good job devs! Fast, stable, and runs great!

Thanks

Geeve

Edit: I have the same YouTube problem. Could it be the kernel not using the display correctly? I am by no means a Dev, it just leads me to believe with the color bands and lack of HD that either the driver or kernel isn't doing its thing. Just a thought. Are there any other kernels we can flash to test?
[Nook Color Android Development] AKross:
The installation was a breeze, excellent ROM!

I can confirm the crash on Storage settings.

The performance is horrible though. Could it be because of the SD card? I have a 16G SanDIsk, should I go with class 4-10?
[Nook Color Android Development] mateorod:
Thanks for the heads up on the settings crash...I just grabbed a log cat from it myself. I haven't looked into it, but it shouldn't be too hard. The banding that you mention, that is the background in holo dark, correct? That is actually an upstream AOSP issue. I don't understand how it has lingered so long...it certainly hasn't made it's way to the stock production builds. CM already fixed it back in ICS...http://review.cyanogenmod.org/#/c/14945/. I will add it here as well.

We don't have HD YouTube for PA either. Is that working on CM10.1? I thought not but I have spent very little time on CM10.1 for the Nook (due to my development commitments only...CM is the best.)

I have also been really pleased with the performance of this ROM. I will probably add in CM performance settings, just to make it easy to add our standard 200mhz over clock. There are a couple other small things I will cherry-pick in from other ROMs to make things a little easier. But I don't want to add too much. Like I said in the OP, I want to try and keep this as close to stock AOSP as is reasonable. We already have CM10.1 for this device...no reason to mimic all of it's features. I also think the small footprint is inemof this ROM's best features.

Performance settings, gradient fix for sure. Quick toggles editing has been requested and will be considered. Anything else?
[Nook Color Android Development] xflier:
yes, HD Youtube is working on CM10.1. I don't care if it plays HD videos or not, even it plays, it is not perfectly smooth. However, HQ videos have HD video as ads in the front, so most of time, it can't play HQ videos without playing the HD ads ahead.

I totally agree that we shouldn't have all of CM10.1 features, and keep it small footprint. Currently in my opinion, it is better than CM10.1 on Nook color (due to hardware limits). I feel less laggy compared to CM10.1. A full feature ROM like CM10.1 maybe better for new hardwares. for nook color, this rom is almost perfect. It will be perfect after the minor issues fixed.

thanks a lot for your excellent work!
[Nook Color Android Development] steven676:
Via the AOSP 4.2 port for the Nexus S:

https://github.com/diclusial/platfo...mmit/16edc0f2b53c6713952e297c941ec2aeae1b9adb
[Nook Color Android Development] mateorod:
Thanks steven! I would guess that you have the actual attribution correct from your find...I am building with an identical commit but with different authorship from the CM project.

https://github.com/CyanogenMod/andr...viceinfo/StorageVolumePreferenceCategory.java

That has pretty much been the method for all bugs here and at AOSPA...how did CM solve it (usually back in cm7, by nemith or dal). Thanks a bunch for the tip.
[Nook Color Android Development] steven676:
Actually, I'd bet the reverse ... note one has "Merge ..." on the title, which implies that someone at some point merged it into another tree.
[Nook Color Android Development] mateorod:
Yeah...but I think the diclusial merge is of the jsharkey commit...who judging by where I see his work in the tree I believe to be an Android engineer. I think pawit is a CM core member, maybe?
[Nook Color Android Development] steven676:
It looks like the change was merged into AOSP master by Jeff Sharkey, but credited to Pawit:

https://android-review.googlesource.com/#/c/46782/

https://android.googlesource.com/pl...gs/+/2ea50e2b5ba495895768505070fcd01574ba20ad

I'd guess diclusial picked in the merge commit https://android.googlesource.com/pl...gs/+/59ee3889088eb40ab6d8b0f4f9f11f51a89c0f76 instead of the original.

(This has been today in mostly pointless Git archaeology ...)
[Nook Color Android Development] mateorod:
But that's what makes us such a fun bunch! Thanks Steven.
[Nook Color Android Development] boggsie:
After flash, the mac address is all zeros except for 1 in the last digit.

My wifi connection filters by mac address so I'm not able to connect with this mac address.

Can I do something on the Nook to get the hardware mac address to update into the rom?
[Nook Color Android Development] steven676:
I think the store-mac-addr.sh script that we use to take care of setting the WLAN MAC requires command-line utilities that AOSP doesn't ship -- it works in CyanogenMod because we have BusyBox available. I did write a version using only tools and shell constructs available in AOSP, but it's kind of ugly -- I can post it if someone wants to try it.
[Nook Color Android Development] mateorod:
Yeah, please post it. I had never read the original before now...I guess I can either tinker with your version or perhaps just add busybox to the build...I would prefer to try your script and add busybox if we decide to in an unrelated capacity. Because I am stubborn.

I just realized that I owe you guys a build...I have had one running on my machine for almost a week, but couldn't upload it because I was out of town. Let me tinker with this issue and then I will push up something new.

To the reporting user...did you try installing busybox?

Thanks steven.
[Nook Color Android Development] steven676:
https://gist.github.com/steven676/5828997

I'm not particularly proud of the substr() function in that script ... if someone comes up with a smarter way of doing this using just tools in AOSP, please jump in!
[Nook Color Android Development] mateorod:
works perfectly. I will commit it from your gist later tonight. I don't see a need to rewrite anything, not that I have any better ideas anyway.

We are also going to take a flyer at integrating some of the surfaceflinger stuff from CM's frameworks/native, targeting the dithering issues.
[Nook Color Android Development] mateorod:
Update is here

FULL wipe needed- sorry, but I replaced some of the frameworks, and I experienced some FCs/malfunctions until I wiped. I anticipate this being just the one time thing.

Improvements include

Fixed dithering (color banding)(and no, it isn't just the check box in settings, lol)

FlashPlayer now works

Fixed crash in storage settings

MAC address will now resolve (thanks sluo)

Added CM's Performance Settings

Setting scheduler or governor does not work--I have barely looked at this. It does work with 3rd party stuff like TricksterMod, although I would prefer to fix it for you and cut the need for an app.

Added Email.apk to keep system happy (lots of errors in logcat w/o an email...I am assuming they are checking the bug reporting framework, sending pictures to NSA, etc.)

Update Notifications from Goo Manager (starts next update)

Goo and Team Win offer hosting to me and many other XDA members, free of charge or obligation. I chose not to include Goo Manager in this rom for ideaological reasons...but you could make worse choices than installing it from the market.

SDCard install script should now work with this rom

As a purveyor of some pretty dirty hacks in my day, this goes down as one of the worst. But the SDCard install scripts never thought the Nook would ever have a rom that wasn't CyanogenMod. I have now had to employ this trick on both of my releases, and it makes me shiver a little. I could release my own version of the SDCard script but honestly, most people aren't going to stop using a script that has served them well for almost three years. Especially because if I just suck it up and add this commit, it works out of the box.

(Of course, it breaks things like my very own Autopatcher, and I would be killing any dev who did this in that thread....life is funny, isn't it?)

To try: Netflix works on PA with this trick, perhaps it will work here as well.

I added CM's frameworks/native...I will not say I am particularly proud about that. My goal is to cut down our reliance on the CM frameworks to as little as possible (as it stands we are using av and native whole cloth). But they are very good at what they do and adding their projects just works....hopefully I will have some time to devote to that...it is only for curiosity's sake that I try to keep as close to AOSP as possible. CM is great and fills a vital hole in the Android ecosystem.

This release's features are pretty much brought to you courtesy of steven676..the MAC address fix is his, he discussed the settings crash with me and the flash player fix was brought to my attention by him as well.

Is there any other light weight stuff you guys want? I intend to look at fixing the governor/scheduler stuff...but unless I get any other decent requests, I will be start concentrating on cutting the rom down from now on.
[Nook Color Android Development] xflier:
First thanks a lot for the update. It works like you said except flash video which works on some websites ( like androidcentral.com), and not on some others ( like cnn.com). CM10.1 works on cnn.com though.

I can confirm the color banding is gone, storage in setting is fixed. Governor works via TricksterMod.

My nook color never worked this good before. I installed this rom on EMMC, Governor set to INTERACTIVE, cpu set to 1100. Installed with seeder, and lagfix.. For example, web browsing never been so good, no lag at all. Scrolling is effortless.

4.2.2 on Nook color has low volume issue. I installed XHiFi. it seems much better now.

Most important, CM10.1 has issues with some apps, like Nook, startup manager in ES Task Manager, and etc. they were very slow. However, these issues are gone in this ROM. This is one of the reasons I was looking for a ROM other than CM10.1.

Finally, a couple of wishes ( not big deals to me, but nice to have). if possible, can power menu have a reboot option? Second, in stock browser, is it possible to set the Agent? like 7.2 did, set Agent as ipad or other tablet. Mobile won't see the full web page, using desktop, the flashvideo won't play. setting as some tablet like ipad might be perfect. :fingers-crossed:

Oh, regarding performance setting, either fix it or remove it since TricksterMod works :)

:good:Well done. Thanks again
[Nook Color Android Development] unibroker:
I am having trouble flashing this. I am using the most recent download. After I do a complete wipe in TWRP and then try to install I'm taken back to the start screen for TWRP. I'm coming from MiRaGe and mrom neither of which I had any trouble flashing using TWRP. Thanks in advance for any assistance.
[Nook Color Android Development] deboyz1014:
lagfix doesn't run on this version, how did you get it to work?