New update cm-10.2-20131102-SNAPSHOT-M1 - Nook HD, HD+ General

So should I download this on my 10.1 hybrid version?
If I do, do I need to do anything specific or will the update happen automatically?

You cannot run this on your hybrid. It is intended to be installed directly on the internal memory. If you decide to do it, abandon the hybrid SD and follow the dummies guide for installing to internal memory.
Sent from my BN NookHD+ using xda premium

leapinlar said:
You cannot run this on your hybrid. It is intended to be installed directly on the internal memory. If you decide to do it, abandon the hybrid SD and follow the dummies guide for installing to internal memory.
Sent from my BN NookHD+ using xda premium
Click to expand...
Click to collapse
so has cm 10.2 become stable?

mynookhd said:
so has cm 10.2 become stable?
Click to expand...
Click to collapse
CM10.2 for the Nook HD and HD+ is NOT stable.
However, CyanogenMod have released M1 (milestone 1) of the CM10.2 for our Nooks. It's more stable than Nightly builds, but not as stable as a Release Candidate, or an actual stable version. Of course, one CyanogenMod staff member stated it's just as good, based off his opinion.
It's completely you're call if you want to use CM10.2; but remember TRIM, and whether you have one of the Samsung made internal-memory chips.

HiddenG said:
CM10.2 for the Nook HD and HD+ is NOT stable.
However, CyanogenMod have released M1 (milestone 1) of the CM10.2 for our Nooks. It's more stable than Nightly builds, but not as stable as a Release Candidate, or an actual stable version. Of course, one CyanogenMod staff member stated it's just as good, based off his opinion.
It's completely you're call if you want to use CM10.2; but remember TRIM, and whether you have one of the Samsung made internal-memory chips.
Click to expand...
Click to collapse
Is there a list somewhere showing the various emmc chips? One of mine is MBG4GA - any idea where I can check this out?
---------- Post added at 09:48 PM ---------- Previous post was at 09:37 PM ----------
Just found this info - looks like I'm OK - is it just the MAG2GA chips?

Don't need to worry about trim. Verygreen disabled it after some users reported bricked devices.

Related

The Unofficial CyanogenMod Series - added aokp-jellybean test build

Hi all I will be working this a little. But don't expect anything to great. I don't have a whole lot of time to work on this. I bricked my phone and not having much luck getting it replaced. So I won't be working on this to much until I can get a new phone as I will be spending all my time working.
Most stuff posted here is probably gonna be untested.
I will be posting cm7, cm9, and cm10 builds here.
Idk if any of these work.
Don't get mad at me if they brick your device. Infact treat them with a high chance of brickage, unless otherwise noted.
CyanogenMod 7:
Code:
[CENTER]
[B][U][COLOR="Blue"][SIZE="2"]Download:[/SIZE][/COLOR][/U][/B]
[URL="https://www.dropbox.com/s/1ct15i6fxbprpjj/cm-7-20120720-UNOFFICIAL-captivatemtd.zip"]cm-7-20120720-UNOFFICIAL-captivatemtd.zip[/URL]
[B][U][SIZE="2"][COLOR="Blue"]Google Apps for Gingerbread:[/COLOR][/SIZE][/U][/B]
[URL="http://goo.im/gapps/gapps-gb-20110828-signed.zip"]gapps-gb-20110828-signed.zip[/URL][/CENTER]
CyanogenMod 9:
Code:
[CENTER][B][U][COLOR="Blue"][SIZE="2"]Downloads:[/SIZE][/COLOR][/U][/B]
[URL="https://www.dropbox.com/s/p0n6myyedm7pyx4/cm-9-20120720-UNOFFICIAL-captivatemtd.zip"]cm-9-20120720-UNOFFICIAL-captivatemtd.zip[/URL]
[B][U][SIZE="2"][COLOR="Blue"]Google Apps for ICS:[/COLOR][/SIZE][/U][/B]
[URL="http://goo.im/gapps/gapps-ics-20120429-signed.zip"]gapps-ics-20120429-signed.zip[/URL][/CENTER]
CyanogenMod 10:
Code:
[CENTER][B][U][COLOR="Blue"][SIZE="2"]Download:[/SIZE][/COLOR][/U][/B]
[URL="http://www.mediafire.com/?ndt440n4ux0ctaz"]cm-10-20120727-UNOFFICIAL-captivatemtd.zip[/URL]
[B][U][COLOR="Blue"][SIZE="2"]Old builds:[/SIZE][/COLOR][/U][/B]
[URL="http://www.mediafire.com/?2n75vev3qvcl417"]cm-10-20120723-UNOFFICIAL-captivatemtd.zip[/URL]
[URL="http://www.mediafire.com/?d89z35acc2cpaxr"]cm-10-FIXED_RECOVERY-captivatemtd.zip[/URL]
[SIZE="2"][B][U][COLOR="Blue"]Google Apps for JellyBean:[/COLOR][/U][/B][/SIZE]
[URL="http://goo.im/gapps/gapps-jb-20120726-signed.zip"]gapps-jb-20120726-signed.zip[/URL]
[URL="http://www.mediafire.com/?xje9p4hl1qv56qz"]inverted_gapps2-jb-20120715.zip[/URL]
[/CENTER]
Recovery:
Code:
[CENTER][B][U][SIZE="2"][COLOR="Blue"]Fake Flashes:[/COLOR][/SIZE][/U][/B]
Touch recovery 6 Fake flash: [URL="http://www.mediafire.com/?k240g28o332apgy"]touch_recovery_fake_flash.zip[/URL]
This is a preview most ways to navigate doesn't work. Normal recovery functions work though
Thanks to:
[URL="http://forum.xda-developers.com/member.php?u=2492461"]sk8erwitskil[/URL] for the source
[/CENTER]
Install instructions:
Code:
[CENTER]Make a backup......
Factory reset........
Mounts and storage > format system.......
Advanced > Wipe Dalvik Cache.......
Install Rom......
Install gapps.....
Reboot......
Go to Rom Manager and fix permissions......
Reboot......
Your all set.........[/CENTER]
Upgrading From a Previous Version:
Code:
[CENTER]Reboot to Recovery
Go to mounts and storage and format system...
Flash latest rom....
If coming from a different build like from cm9 to cm10
then follow the install instructions
When going from cm10 to cm10 flash latest cm10 zip
When going from cm9 to cm9 flash latest cm9 zip[/CENTER]
AOKP- JellyBean test build
Code:
[CENTER][SIZE="3"][B][U]Download:[/U][/B][/SIZE] [URL="http://www.mediafire.com/?9eud3x8c4pq4atd"]
AOKP-JB-captivate-b1.zip[/URL]
[SIZE="3"][B][U]Doesn't work:[/U][/B][/SIZE]
Rom Control force closes Settings
Messaging force closes
Still being tested. Please provide feedback[/CENTER]
cm7 builds:
cm-7-20120720-UNOFFICIAL-captivatemtd.zip
gapps-gb-20110828-signed.zip
Click to expand...
Click to collapse
what's different from Official version this unofficial version?
p.s: sorry for my english
Someone please confirm but I thought releases weren't supposed to be put on xda without the op having a device to test it on? Just curious...
Sent from my SGH-I897 using xda premium
I have this device. I bricked my skyrocket
Sent from my SGH-I897 using Tapatalk 2
levanr said:
what's different from Official version this unofficial version?
p.s: sorry for my english
Click to expand...
Click to collapse
I'm not sure. I just like making my own builds and I figured I'd post them.
Sent from my SGH-I897 using Tapatalk 2
levanr said:
what's different from Official version this unofficial version?
p.s: sorry for my english
Click to expand...
Click to collapse
"unofficial" is beta version that has some problem, "official" is perfect version that has no problem.
gmillz said:
Hi all I will be working this a little. But don't expect anything to great. I don't have a whole lot of time to work on this. I bricked my phone and not having much luck getting it replaced. So I won't be working on this to much until I can get a new phone as I will be spending all my time working.
Most stuff posted here is probably gonna be untested.
I will be posting cm7, cm9, and cm10 builds here.
Idk if any of these work.
Don't get mad at me if they brick your device. Infact treat them with a high chance of brickage, unless otherwise noted.
Click to expand...
Click to collapse
-Downloading
If they wont work... you need a logcat or something .. am I right ?
How to install: ?
Features: ?
Sent from my GT-I9000 using xda premium
Are these the same available on get.cm?
unnecessary (sorry)
Sent from my GT-I9000 using Tapatalk 2
Gore785 said:
How to install: ?
Features: ?
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
if you dont understand how to install please leave the area lol
What's the point of this thread?
CheesyNutz said:
if you dont understand how to install please leave the area lol
Click to expand...
Click to collapse
I've honestly lost count of all your posts that offer absolutely nothing helpful or relevant to the discussion.
I understand theres not much of a point to this. The main reason for this thread is cm10 as all the other cm10 roms don't have the stock cm kernel. But since I build the other ones anyways i figured I'd post them. And I'll post install instructions.
kevinnol said:
-Downloading
If they wont work... you need a logcat or something .. am I right ?
Click to expand...
Click to collapse
Definitely. Logcats would be great
CheesyNutz said:
if you dont understand how to install please leave the area lol
Click to expand...
Click to collapse
Meant that as in anything we should do in specific before, during, or after install Like fix permissions?
Sent from my GT-I9000 using xda premium
johnnyrichter said:
What's the point of this thread?
I've honestly lost count of all your posts that offer absolutely nothing helpful or relevant to the discussion.
Click to expand...
Click to collapse
gmillz said:
I understand theres not much of a point to this. The main reason for this thread is cm10 as all the other cm10 roms don't have the stock cm kernel. But since I build the other ones anyways i figured I'd post them. And I'll post install instructions.
Click to expand...
Click to collapse
So...if you understand there's not much of a point, why post at all? Also, FYI, in regard to your OP: "to" is not the same as "too", and "infact" is not a word. Just sayin'.
adzidek said:
So...if you understand there's not much of a point, why post at all? Also, FYI, in regard to your OP: "to" is not the same as "too", and "infact" is not a word. Just sayin'.
Click to expand...
Click to collapse
Because this is the only cm10 rom with the stock cm kernel. I meant there was not much reason to post any of the other builds
gmillz said:
Because this is the only cm10 rom with the stock cm kernel. I meant there was not much reason to post any of the other builds
Click to expand...
Click to collapse
You'll likely receive a lot of flak over re-hosting/posting stuff as you've seen thus far, but if you're offering something you've re-worked in any way(which is what I understand you're doing) then I'd stick with just that and link to other threads in your OP if necessary.
If you compiled from CM10 source here we have CM10 kernel for Captivate (no datadata partition).
This is very interesting.
Thank you very much: if compiling went well this is really an important step for JB on Cappy and now we can run also official Pawitp builds.
Monfro said:
If you compiled from CM10 source here we have CM10 kernel for Captivate (no datadata partition).
This is very interesting.
Thank you very much: if compiling went well this is really an important step for JB on Cappy and now we can run also official Pawitp builds.
Click to expand...
Click to collapse
Yes this is compiled from source specifically for the captivate.
And compiles with no errors

Nexus S CM 10.1 BBQ log

At BBQ log changes for the cyanogenmod 10.1 version are already available!!
link: http://changelog.bbqdroid.org/#crespo/cm10.1/1355380185
id dont know if the nightlies by cm are downloadabel(not on their homepage!) but there is an unofficial rom here
link: http://forum.xda-developers.com/showthread.php?t=2041851
say thanks:good:
nero17 said:
At BBQ log changes for the cyanogenmod 10.1 version are already available!!
link: http://changelog.bbqdroid.org/#crespo/cm10.1/1355380185
id dont know if the nightlies by cm are downloadabel(not on their homepage!) but there is an unofficial rom here
link: http://forum.xda-developers.com/showthread.php?t=2041851
say thanks:good:
Click to expand...
Click to collapse
Nope, no official build available yet for crespo.
Cominggggg CM10.1 Experimental
They also have it running for Crespo4G. I'm running Jellyshot right now, but looking forward to seeing what the CM team does with this phone!
Hells yeah. I can't wait for the first nightlies to hit.
I have never done this before, so take this with a grain of salt, but I am currently syncing with the cm10.1 repo. Hoping to have a build for the Crespo4G soon.
That being said, syncing has been going on for about 6 hours. Damn 3mbps.
Update:
9.3GB takes a long time to download on a horrible connection. The bun is officially in the over. I'll report back when I have any news.
Just a question regarding cm 10.1. I am running cm10 now. I have installed the 4.2 camera and gallery from a post on here awhile back. If and when I update to 10.1, Well the new camera app change or will I need to manually replace it?
Sent from my Nexus S using xda app-developers app
123go! said:
Just a question regarding cm 10.1. I am running cm10 now. I have installed the 4.2 camera and gallery from a post on here awhile back. If and when I update to 10.1, Well the new camera app change or will I need to manually replace it?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
When flshing the gapps package from goo.im, all google apps will be replace!.. maybe the apps will be twice on your your device, but you can disable the former gallery and camera in your apps settings..
and i would say do a full wipe befor 10.1.. or between every bigger system update
Sorry, but this is a false alarm. The person who coded this webpage has automatically (and incorrectly) coded all nightlys as cm10.1. Check out all of the links - surely nightlys from September and October are not cm10.1? There are no cm10.1 nightlies for crespo / nexus s yet. See link: http://get.cm/crespo.
nero17 said:
At BBQ log changes for the cyanogenmod 10.1 version are already available!!
link: http://changelog.bbqdroid.org/#crespo/cm10.1/1355380185
id dont know if the nightlies by cm are downloadabel(not on their homepage!) but there is an unofficial rom here
link: http://forum.xda-developers.com/showthread.php?t=2041851
say thanks:good:
Click to expand...
Click to collapse
Yes that is true.. the official build is not out yet.. i have heard that its gonna be out in early 2013.. (that is if the world doesn't end )...
Here's the link to the unofficial build posted on the forums.. http://forum.xda-developers.com/showthread.php?t=2041851
ROM Manager
Uhm ... I've just launched Rom Manager and in the CyanogenMod Nightlies I found 10.1 ... of yesterday
To post an update on the status of my NS4g build:
I got to the point where it goes to build, then sat there. For 20 hours. No files were written even though my CPU was at 100% all day/night.
Anyways, I'm also running out of space, 5.6GB free which isn't enough, so I'm going to load ubuntu on my desktop and try it on there.
Have you tried flashing it? I am on my way to office right now, can't wait, will probably flash it in office today
Sent from my Nexus S using Tapatalk 2
---------- Post added at 10:17 AM ---------- Previous post was at 10:15 AM ----------
AndroidWolf59 said:
Uhm ... I've just launched Rom Manager and in the CyanogenMod Nightlies I found 10.1 ... of yesterday
Click to expand...
Click to collapse
Have you tried flashing it? I am on my way to office right now, can't wait to flash it, will probably flash it in office today
Sent from my Nexus S using Tapatalk 2
AndroidWolf59 said:
Uhm ... I've just launched Rom Manager and in the CyanogenMod Nightlies I found 10.1 ... of yesterday
Click to expand...
Click to collapse
I try it!! All work for now
That is a bit funny how the 17Dec12 nightly for 10.1 is in ROM Manager, but not on the get.cm website nor on the cyanogenmod updater in settings...
AndroidWolf59 said:
Uhm ... I've just launched Rom Manager and in the CyanogenMod Nightlies I found 10.1 ... of yesterday
Click to expand...
Click to collapse
Can somebody upload it on mediafire or smthng?
Will click thanks of course!
arun_vj said:
Have you tried flashing it? I am on my way to office right now, can't wait, will probably flash it in office today
Sent from my Nexus S using Tapatalk 2
---------- Post added at 10:17 AM ---------- Previous post was at 10:15 AM ----------
Have you tried flashing it? I am on my way to office right now, can't wait to flash it, will probably flash it in office today
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Awesome ROM, was waiting for it from the time Google announced end of updates for Nexus S. Great job from CyanogenMod team!!
Sent from my Nexus S using Tapatalk 2
http://www.clockworkmod.com/rommana...anogenMod Nightlies&deviceName=Google Nexus S
here is the CyanogenMod 10.1 20121217
enjoy if you're not using ROM manager
jahlovePL said:
http://www.clockworkmod.com/rommana...anogenMod Nightlies&deviceName=Google Nexus S
here is the CyanogenMod 10.1 20121217
enjoy if you're not using ROM manager
Click to expand...
Click to collapse
what the bug ???
For those that are following this thread... http://download.cyanogenmod.org/get/jenkins/15757/cm-10.1-20121221-NIGHTLY-crespo4g.zip

Aosp roms discussion thread. [Minor FAQ inside]

This thread is for discussing aosp roms, like Slim, Carbon, etc. except for CM though since it has its own thread. This is meant to keep the unhelping chit-chatter out of the development threads where bug reports best reside. When posting here, clarify what aosp rom you're on. Do not post bug reports here, post them in their respective development threads!
One more thing! While this thread progresses, use search and/or read the faq to see if your question has already been posted before, to avoid repetitiveness and us older lads becoming grumpy.
F.A.Q: (frequently asked questions)
I would like to dualboot, what should I do?
Flash siyah kernel
Help! I flashed siyah and now my rom doesn't boot!
It's because whatever rom you use has a newer mali driver which most kernels aren't updated for. Especially siyah which hasn't seen some dev love in ages.
What rom should I flash?
We don't know, you have to try them out yourself!
What's gapps, and is this inside xx rom?
Gapps is short for google apps, which is the Play store and some other apps you sorely need. Go too http://goo.im/gapps and download the gapps package for whatever version you have. Newer aosp roms are most certainly 4.2.2. Some roms, like Slim, have their own separate gapps packages specially made for those roms. In those cases, the standard gapps from goo.im will not work!
Help! I flashed xx rom but now it doesn't boot!
Try making a factory reset in the recovery and reflash whatever rom you were on. Also, in most cases, CWM works better for rom installations. Twrp craps out for unknown reasons.
Help! I wiped data and reflashed the rom but it still doesn't boot!
That sounds like a rom issue. Try flashing an earlier version of the rom.
Help! Something screwed up and now my phone doesn't boot anymore!
Well, reboot into recovery and see if a reflash helps. It is always recommended to regularly keep your system backed up in case something nasty happens. Perform a nandroid backup every once in a while.
What is a nandroid backup?
It's like a screenshot of your current state which you can return to if something bad happens. A nandroid backup backs up the system, boot (kernel) and data and, if specified/selectable, it also backs up cache and recovery. Maybe even efs (in twrp). However, it doesn't back up the modem!
I flashed xx kernel and I now get a black screen upon reboot!
That is because the rom you flashed has the new mali driver from the 4.2.1 leak and the kernel you flashed isn't updated with this driver. Stay on the provided kernel for now.
Thanks to:
I forgot to give thanks where due, and I'm so sorry for that. If I got an advice from you, hit me up and your name goes on this list.
C_tho; for mentioning the mali driver stuff.
Noble Sir Slaphead20; for suggesting I'd maintain an FAQ and suggesting I'd make an entry covering gapps.
great..let me fire up first noob ?...other than siyah any other kernel supports dual boot of cm & sammy rom/ cm or aokp...
edit i know its kernel ? but still related to cm or aokp...
Re: Aosp roms discussion thread.
kevinarjun said:
great..let me fire up first noob ?...other than siyah any other kernel supports dual boot of cm & sammy rom/ cm or aokp...
edit i know its kernel ? but still related to cm or aokp...
Click to expand...
Click to collapse
Nope, only siyah
---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------
@Theshawty....maybe as the thread develops you can add a FAQ?
kevinarjun said:
great..let me fire up first noob ?...other than siyah any other kernel supports dual boot of cm & sammy rom/ cm or aokp...
edit i know its kernel ? but still related to cm or aokp...
Click to expand...
Click to collapse
Only Siyah, and Siyah only supports the older aosp roms.
Speaking of aosp, I just had an urge to flash Carbon. Think I'll do it, because I'm a bit bored of running touchwiz and I've run CM for so long I need change. I didn't like RootBox that much (too many settings, lol. I like a "leaner" setup) and there's no official aokp for our device. I also didn't like Slim, so I'll give Carbon another go.
slaphead20 said:
Nope, only siyah
---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------
@Theshawty....maybe as the thread develops you can add a FAQ?
Click to expand...
Click to collapse
Yeah, I had in mind to add a smaller faq.
would suggest you also try JellyBam...
kevinarjun said:
would suggest you also try JellyBam...
Click to expand...
Click to collapse
not gonna happen
jellybam isnt a welcome rom here
kevinarjun said:
would suggest you also try JellyBam...
Click to expand...
Click to collapse
DSA said:
not gonna happen
jellybam isnt a welcome rom here
Click to expand...
Click to collapse
What DSA said. We do not welcome JellyBam here anymore because the developer broke a lot of rules of XDA. Plagiarism and violating the gpl, amongst others.
----------
I updated the op with a small faq. More to come in the following days.
In the Faqs it might be worth mentioning in the gapps bit that some Roms ie slim, have their own gapps, and others won't work
Just flashed Carbon 1.5, not regretting it thus far! This ROM gives the word buttery smooth a whole new meaning!
Sent from my GT-I9300 using Tapatalk 2
Not sure this goes here, but ill give it a go anyways.
In the Slimbean thread there was a lot of talk about mali drivers. Now could someone please give me some info on the matter cause seems like I missed something.
Basicly what im wondering is whats up with the mali drivers and why do I want them?
Sorry if this is off-topic or has been answered somewhere else.
Sent from my GT-I9300 using Tapatalk HD
looking to switch to a AOSP ROM, what do you think about Super Nexus? Seems like the definition of AOSP
Glebun said:
looking to switch to a AOSP ROM, what do you think about Super Nexus? Seems like the definition of AOSP
Click to expand...
Click to collapse
Slim is definitely worth a go as well
slaphead20 said:
Slim is definitely worth a go as well
Click to expand...
Click to collapse
Agreed, running it now with no problems.
Carbon is nice as well..
Sent from my GT-I9300 using xda app-developers app
Jns said:
Not sure this goes here, but ill give it a go anyways.
In the Slimbean thread there was a lot of talk about mali drivers. Now could someone please give me some info on the matter cause seems like I missed something.
Basicly what im wondering is whats up with the mali drivers and why do I want them?
Sorry if this is off-topic or has been answered somewhere else.
Sent from my GT-I9300 using Tapatalk HD
Click to expand...
Click to collapse
They fix the graphics glitches and completely without memory leaks.
Glebun said:
looking to switch to a AOSP ROM, what do you think about Super Nexus? Seems like the definition of AOSP
Click to expand...
Click to collapse
I think you should give Carbon a try, it's THE definition of buttery smooth and come with some neat customization.
Sent from my GT-I9300 using Tapatalk 2
Glebun said:
looking to switch to a AOSP ROM, what do you think about Super Nexus? Seems like the definition of AOSP
Click to expand...
Click to collapse
The only problem with SuperNexus is it is updated very slowly. Also Faryaab has exams to do now, so it will not get updated at least until he is done with them.
If you want a super light rom I would reccomend SlimBean it's fast, and light, battery is acceptable, and it's easy to change settings like screen density and navbar settings without having to edit build.prop and decompile framework-res.apk, which you will have to do on SuperNexus.
what about the smoothness of it?
Another one there to vouch for Carbon, running it on both phone and tablet
Sent from my Nexus 7 using xda app-developers app
I love AOSP Roms and thank you for starting this thread. Unfortunately I am afraid that I can't use such Roms as a daily driver because of the camera problems. Bluetooth also seems to be a problem for some users.
Guys I am facing Memory leak problem with the Slim bean 4.2.2.....is it normal? cant seems to find any solution....
you'd be better off asking in the slim thread

Nook HD/HD+ officially supported by Cyanogen!

Source: https://plus.google.com/117962666888533781522/posts/hHKqw4zU3vZ
Break out the bubbly, we have successfully been merged in. Congrats, Verygreen, for all your hard work!
woot!
wonder when the first official nightly is ready. anyone has an idea from past experiences, how long it takes them from announcing the device, to first nightly?
The merge is not fully complete yet.
We most likely missed today's nightly window too. Hopefully tomorrow we'll be fully ready.
That is way awesome. CM 10.2 here we come
Thanks for the update. If you don't mind me asking, what's causing the delay?
Sent from my SPH-L720 using xda app-developers app
Seraphnox said:
Thanks for the update. If you don't mind me asking, what's causing the delay?
Click to expand...
Click to collapse
Some internal references to supportng repos are broken due to them being renamed + kernel tree somehow failed to upload it seems.
Thanks for this (official cm), great work!
Break out the bubbly, we have successfully been merged in. Congrats, Verygreen, for all your hard work!
Click to expand...
Click to collapse
This is great news. I have a Nook HD and hope this will mean that soon more bluetooth keyboards will work with it! (In particular the Anker Ultra-slim). I was interested in verygreen's own updated CM, but was unclear whether this works on the HD or just the HD+.
Perhaps we will also be able to use some planetarium/star charting apps. Invariably I am told that they are incompatible with my device.
Paul
Suthers said:
This is great news. I have a Nook HD and hope this will mean that soon more bluetooth keyboards will work with it! (In particular the Anker Ultra-slim). I was interested in verygreen's own updated CM, but was unclear whether this works on the HD or just the HD+.
Perhaps we will also be able to use some planetarium/star charting apps. Invariably I am told that they are incompatible with my device.
Paul
Click to expand...
Click to collapse
My Anker bluetooth kb K1280C (can't remember what it's called) works fine with CM. Whereas bluetooth keyboards don't seem to work on stock. But, bt mice work on stock, and don't work on CM. Go figure.
This sounds like great news & a testament to verygreen's tireless efforts into transforming this crippled color e-reader into the best deal out there for android tablets. I'm excited about this development but can somebody explain what it means to be CM official as opposed to unofficial? & maybe how things will change? (for the better I'm assuming)
I used to have an official CM8 ROM on my old Nexus S 4G a while back & this unofficial CM rom by verygreen runs so much better & more stable than that one did.
Sent from my BN NookHD+ using Tapatalk HD
Hi,
I bought a Nook HD+ sometime back and have been reading up a lot about rooting and installing custom ROM' on the forum of late. I had planned to install the currently available custom ROM today, but I bumped across this thread.
Being a newbie, from what I can gather, Cyanogen would officially be supporting Nook HD+ ROM', so we can expect an official release soon. So my question is, if it's better to wait for the official CM release or go ahead and install the currently available unofficial version?
Thanks in advance.
sibot said:
Hi,
I bought a Nook HD+ sometime back and have been reading up a lot about rooting and installing custom ROM' on the forum of late. I had planned to install the currently available custom ROM today, but I bumped across this thread.
Being a newbie, from what I can gather, Cyanogen would officially be supporting Nook HD+ ROM', so we can expect an official release soon. So my question is, if it's better to wait for the official CM release or go ahead and install the currently available unofficial version?
Thanks in advance.
Click to expand...
Click to collapse
go with unofficial, and just update as they release new builds. It will be quite a while until we will see official RC not to mention stable release...
wow this is awesome news, I made a gamble 2 weeks ago to import the nook HD+ to europe hoping that cyanogenmod would support the HD+ in the coming weeks. Now running verygreen's emmc 10.1
Great Work
This is fantastic news. I join everyone in thanking Verygreen.
I hope an official build means easier modifications when using things like autopatcher to create a tabletui. There hasn't been much of an update in a few weeks in that thread.
Awesome news! Thanks again for all your hard work, Verygreen.
Outstanding! Congrats to all involved.
This is due to verygreens hard work, and is a testament to the quality of his code. It is my understanding he will still be doing all the work for CM, but now it will be "blessed" as an official CM port instead of unofficial. The state of the port will still depend on the (excellent) work that verygreen puts into this rom.
Thanks again verygreen for making my Nook HD+ a decent tablet instead of a marginal one.
Melven1 said:
This is due to verygreens hard work, and is a testament to the quality of his code. It is my understanding he will still be doing all the work for CM, but now it will be "blessed" as an official CM port instead of unofficial. The state of the port will still depend on the (excellent) work that verygreen puts into this rom.
Thanks again verygreen for making my Nook HD+ a decent tablet instead of a marginal one.
Click to expand...
Click to collapse
Will I be able to get the first nightlie from the the unofficial rom I have installed under updates? Or will I need to do a fersh install when this rolls out? Thanks again!

[Q] Building OmniRom from resources for i9100

OK, so I am not a dev.
And iam completely newbie
I saw some people saying that if you have aosp on your device it's much easier to port omnirom for your device
So can I use CyanogenMod 10.2 that is available for the i9100
To build omni
And is there any detailed instruction on how to build it !!
Sent from my GT-I9100 using Tapatalk 4
I9100 needs some work because of its unified kernel, building it right now is pretty much useless if you don't know where to put your hands to solve some issues; I want to try it too but this project is in a early stage so I'll wait
Sent from my GT-I9100 using xda app-developers app
filllob said:
I9100 needs some work because of its unified kernel, building it right now is pretty much useless if you don't know where to put your hands to solve some issues; I want to try it too but this project is in a early stage so I'll wait
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yup. There are two MAJOR blockers right now:
1) We haven't merged and tested the implementation of BOARD_SUPPRESS_EMMC_WIPE yet. So if someone were to build for a Superbrick-vulnerable device, they would have a a build that risks triggering Superbrick. While I normally don't like having moderators take down builds for something, if I see builds for Superbrick-vulnerable devices show up, I'm going to work with the mods to have them taken down until EMMC wipe suppression can be verified.
2) The build system needs some changes to permit TWRP to be built on userdebug builds. Right now, the only way you'll have a chance of working recovery is with an eng build.
Entropy512 said:
Yup. There are two MAJOR blockers right now:
1) We haven't merged and tested the implementation of BOARD_SUPPRESS_EMMC_WIPE yet. So if someone were to build for a Superbrick-vulnerable device, they would have a a build that risks triggering Superbrick. While I normally don't like having moderators take down builds for something, if I see builds for Superbrick-vulnerable devices show up, I'm going to work with the mods to have them taken down until EMMC wipe suppression can be verified.
2) The build system needs some changes to permit TWRP to be built on userdebug builds. Right now, the only way you'll have a chance of working recovery is with an eng build.
Click to expand...
Click to collapse
Can we not use cm10.2 smdk4412 kernel, @Entropy512? EMMC_WIPE is disabled there?
Also, would there be any problems if one were to remove Omni bootable project and replace it with cm10.2's?
chasmodo said:
Can we not use cm10.2 smdk4412 kernel, @Entropy512? EMMC_WIPE is disabled there?
Also, would there be any problems if one were to remove Omni bootable project and replace it with cm10.2's?
Click to expand...
Click to collapse
No, because it could still cause damage if flashing from an old "unsafe" kernel (see the first few CM10 builds as an example...). These are far rarer now than they used to be, but there are, believe it or not, occasionally people who are flashing stuff starting from TW ICS.
And CWM has tentacles throughout the CM source tree to get it to build. It requires too many hacks in too many places. TWRP is more standalone, the limitation being that on devices with standalone recovery, Dees_Troy always built using the "eng" variant instead of "userdebug".
There's a patch that allows for TWRP to build properly on userdebug using "make recoveryimage" but it fails to allow building of TWRP into unified-recovery devices like Sony pollux_windy/yuga. (Samsung requires even more hacks...)
Even the Sonys which are "sort of" working aren't ready for builds yet - for them to work they're dependent on the FOTAKernel trick Dees_Troy developed to allow for alternate recoveries to be put on a device.
Does the above apply also to the i9100g? It has an OMAP4 processor instead of Exynos so it should be easier to build for.
aidfarh said:
Does the above apply also to the i9100g? It has an OMAP4 processor instead of Exynos so it should be easier to build for.
Click to expand...
Click to collapse
I'm fairly certain the G has unified kernel/recovery just like most of the rest of the galaxys2 family (exception being the Qualcomm-based ones).
So it might build, but recovery will not function at all until the build system is fixed to properly support TWRP on devices with unified kernel/recovery.
It has nothing to do with Qualcomm vs. OMAP vs. Exynos, except that for whatever reason, Samsung actually allowed the recovery partition to serve its normal purpose on the Skyrocket and Hercules. Actually, the Straight Talk variant of the SGH-I777 might work, as that oddball device actually DID use its recovery partition.
Entropy512 said:
I'm fairly certain the G has unified kernel/recovery just like most of the rest of the galaxys2 family (exception being the Qualcomm-based ones).
So it might build, but recovery will not function at all until the build system is fixed to properly support TWRP on devices with unified kernel/recovery.
It has nothing to do with Qualcomm vs. OMAP vs. Exynos, except that for whatever reason, Samsung actually allowed the recovery partition to serve its normal purpose on the Skyrocket and Hercules. Actually, the Straight Talk variant of the SGH-I777 might work, as that oddball device actually DID use its recovery partition.
Click to expand...
Click to collapse
Is there anything I can do to help? Maybe if I can make it work on my device?
So the I9000 got a build of OmniRom, I thought it has also a unified kernel !!!
I was searching on Google today
and I suddenly found this
http://forum.xda-developers.com/showthread.php?t=2494127
that's an alpha build for I9100
it's using the CM10 kernel and it uses CWM not TWRP
Iam testing it right now
Jiangyi had some success getting i9100g working last night
I'm attempting to build for n7000 to see if it works at all... Who knows. Although I still need to merge in BOARD_SUPPRESS_EMMC_WIPE...
Entropy512 said:
Jiangyi had some success getting i9100g working last night
I'm attempting to build for n7000 to see if it works at all... Who knows. Although I still need to merge in BOARD_SUPPRESS_EMMC_WIPE...
Click to expand...
Click to collapse
I built it for Note already
http://forum.xda-developers.com/showthread.php?t=2495930
Sent from my GT-N7000 using Tapatalk
Yes @herna,you built it without a working recovery and without further testing. Nonetheless, it is running flawlessly, quicksand fluid with Raw kernel r3 and it's Cwm recovery.
Would you mind having a look at this commit.
http://review.cyanogenmod.org/#/c/50800/
Fixed the mobile data drop while calling. Thanks
GALAXY NOTE N7000 // OMNI ROM // JLS36I
AA1973 said:
Yes @herna,you built it without a working recovery and without further testing. Nonetheless, it is running flawlessly, quicksand fluid with Raw kernel r3 and it's Cwm recovery.
Would you mind having a look at this commit.
http://review.cyanogenmod.org/#/c/50800/
Fixed the mobile data drop while calling. Thanks
GALAXY NOTE N7000 // OMNI ROM // JLS36I
Click to expand...
Click to collapse
Yeah I know. Entropy and me are looking for the error, but is not beeing easy to fix. Okey, will add in a few hours and release new one. And I correct you, except the latest version, I tried all versions I released and some others I didn't release. I always do but that day I needed phone for important family things and couldn't test
Also I went to release with a prebuilt TWRP 3.0.101 kernel but XplodWilD say me that this will get Semi-Official maybe, and only compiled non-touched ROMs will be released.
Sent from my GT-N7000 using Tapatalk
@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Sent from my GT-I9100 using xda app-developers app
filllob said:
@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Click to expand...
Click to collapse
n7000 bringup would be easier, methinks.
filllob said:
@Entropy512 just wondering if your commit "i777 bringup" can be applied (obviously with some changes) to i9100
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Ask some DEV to try and see if works
Enviado desde mi GT-N7000 mediante Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
chasmodo said:
n7000 bringup would be easier, methinks.
Click to expand...
Click to collapse
N7000 is gonna be up as soon as XplodWild get free and merge it and change something I said him. Idk why my Gerrit is not working. I am gonna install Ubunt 13.10 for clean and will set up all again for try if I can get Gerrit working again
Enviado desde mi GT-N7000 mediante Tapatalk
I'd like to try it myself, just want to know if it's legit or not
Sent from my GT-I9100 using xda app-developers app
filllob said:
I'd like to try it myself, just want to know if it's legit or not
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
If is legit what? I cannot understand you, sorry. You want to try, to compile...?
i am a noob to compiling etc, only followed cm instructions.
I want to know if the changes in the commit I mentioned can be applied to i9100 too, obviously with some adjustments, and if there is something more to do to compile omni for i9100
I hope I explained myself right( English is not my language)
Sent from my GT-I9100 using xda app-developers app

Categories

Resources