Database Develop

whats next?????

so with the impending release of gingerbread and the need for a 1ghz processor, what is in store for us at that point???
any ideas or guesses?

Wait untill its out then we will see if theres a way to make it work smoothly.
I must say that these "OMG something in the future may be bad, lets look for new devices" - posts are a bit annoying.
I personally hope that this specs are only for the regular updatet android devices and that the devs will handle this.

I'm waiting for the wildfire to be cracked, then we could potentially port native froyo sense made for devices similar to ours

piperthedj said:
so with the impending release of gingerbread and the need for a 1ghz processor, what is in store for us at that point???
any ideas or guesses?
Click to expand...
Click to collapse
the 1ghz thing was never confirmed, engadget ran that story and the one guy from google said that they had no plans for minimum hardware requirements

scottter said:
I'm waiting for the wildfire to be cracked, then we could potentially port native froyo sense made for devices similar to ours
Click to expand...
Click to collapse
Pretty sure it still runs Eclair, but either way. The wildfire build would be nice.

how close are we to a custom Rom

I haven't seen any threads likely on custom ROM work. I'm sure someone is working on one. Is the focus on froyO on Gingerbread?

sudermatt said:
I haven't seen any threads likely on custom ROM work. I'm sure someone is working on one. Is the focus on froyO on Gingerbread?
Click to expand...
Click to collapse
I saw a post from Pete on Twitter yesterday. He asked Koush to port clockwork recovery to the Nook Color so he could buy one and start porting ROMs to it. So all we are waiting on is a working recovery from Koush or Amon to start flashing ROMs. I have started working on an AOSP ROM, but I'm with Pete, we need a recovery first. Froyo definitely is the start, Gingerbread ROMs are just surfacing on the higher end processors (1GHz required supposedly). Ill probably offer Gingerbread theming for mine if I have time.
Peter Alfonso
@PeterAlfonso Peter Alfonso
@koush, if you port clockwork to nook color my chances of buying one goes up 99%
15 hours ago via web Favorite Retweet Reply
Retweeted by phaedrus242 and 6 others
Here is the link for petes android dev page:
http://www.peteralfonso.com/

monsterpt said:
I saw a post from Pete on Twitter yesterday. He asked Koush to port clockwork recovery to the Nook Color so he could buy one and start porting ROMs to it. So all we are waiting on is a working recovery from Koush or Amon to start flashing ROMs. I have started working on an AOSP ROM, but I'm with Pete, we need a recovery first. Froyo definitely is the start, Gingerbread ROMs are just surfacing on the higher end processors (1GHz required supposedly). Ill probably offer Gingerbread theming for mine if I have time.
Peter Alfonso
@PeterAlfonso Peter Alfonso
@koush, if you port clockwork to nook color my chances of buying one goes up 99%
15 hours ago via web Favorite Retweet Reply
Retweeted by phaedrus242 and 6 others
Here is the link for petes android dev page:
http://www.peteralfonso.com/
Click to expand...
Click to collapse
The 1ghz CPU requirement for Gingerbread is a myth, just fyi. Google has stated that any phone that currently runs Froyo should have no issues running Gingerbread -- in fact, they should see an increase in performance.
There are plenty of low end phones shipping with Froyo (ie, Huwai's Ideo line), so by that logic, there should be no reason, at least in regards to the CPU, that it Gingerbread couldn't run on the Nook Color.

tokyomonster said:
The 1ghz CPU requirement for Gingerbread is a myth, just fyi. Google has stated that any phone that currently runs Froyo should have no issues running Gingerbread -- in fact, they should see an increase in performance.
There are plenty of low end phones shipping with Froyo (ie, Huwai's Ideo line), so by that logic, there should be no reason, at least in regards to the CPU, that it Gingerbread couldn't run on the Nook Color.
Click to expand...
Click to collapse
Yep, just realized that GBread is already running on sub 1ghz devices. I will track down the GB AOSP and break it down.

monsterpt said:
Yep, just realized that GBread is already running on sub 1ghz devices. I will track down the GB AOSP and break it down.
Click to expand...
Click to collapse
I know JBQ posted it up yesterday, so it should be available straight from google now.

tokyomonster said:
I know JBQ posted it up yesterday, so it should be available straight from google now.
Click to expand...
Click to collapse
It was, thanks.

tokyomonster said:
The 1ghz CPU requirement for Gingerbread is a myth, just fyi. Google has stated that any phone that currently runs Froyo should have no issues running Gingerbread -- in fact, they should see an increase in performance.
There are plenty of low end phones shipping with Froyo (ie, Huwai's Ideo line), so by that logic, there should be no reason, at least in regards to the CPU, that it Gingerbread couldn't run on the Nook Color.
Click to expand...
Click to collapse
I think the confusion started when people were thinking that Gingerbread would be Android 3.0. Honeycomb will probably be considerably more demanding than previous versions, since you can split the screen into "fragments," so Nook Color users might eventually need to O/C to get that version working well.

FrasierCrane said:
I think the confusion started when people were thinking that Gingerbread would be Android 3.0. Honeycomb will probably be considerably more demanding than previous versions, since you can split the screen into "fragments," so Nook Color users might eventually need to O/C to get that version working well.
Click to expand...
Click to collapse
LG is also partly to blame. When asked if the Gingerbread would hit their Optimus line of phones, they made up a 1ghz minimum CPU requirement. They retracted that when Google engineers said no such thing existed.

Donate to cyogenmod in this thread. As soon as we get these guys some nooks, they can get us a custom recovery. Then ROM floodgates will open. Can't wait to see this thing running gingerbread
http://forum.xda-developers.com/showthread.php?t=868868

@op, I think we will see a new custom rom soon, some one will use the new update 1.0.1 with customize files like auto nooter to flash the nookcolor with (updated) modified files...

We still need.CWM ported to flash unsigned zips. I tweeted to koush on what is needed to work on it. I'd like to help where I can so I can begin creating a ROM for.this beautiful tablet.
Time will tell...Koush, Supercurio, and the CM team are busy with Gingerbread ports via the Nexus S.
Im sure we'll be able to get started soon.
Thanks
-h8
Sent from my SAMSUNG-SGH-I897 using XDA App

Will the nook get some honey?

Here is a thread that will be all about speculation..
I saw the honeycomb and it was smoking!!! What are the chances that the guys here will get it on the nook? And if yes, how it will run? Given that it only have a 800Mhz processor (1Ghz overclocked).
Looking forward for any opinions

I hope so, but that's a good bit away. Honeycomb uses on screen buttons, so our hardware button deficiencies would go away, if it were possible.

IIRC, Honey requires a 1Ghz processor. If we can get the overclocked kernels working with the five 9's of accuracy, then its possible. I really would like for there to be a way to strip out the nooks reader and shop apps for B&N so that I can keep the books and magazines that I've purchased. Thats pretty much a prerequisite for me.

10equals2 said:
IIRC, Honey requires a 1Ghz processor. If we can get the overclocked kernels working with the five 9's of accuracy, then its possible. I really would like for there to be a way to strip out the nooks reader and shop apps for B&N so that I can keep the books and magazines that I've purchased. Thats pretty much a prerequisite for me.
Click to expand...
Click to collapse
There are no mandatory hardware requirements for honeycomb, but it will certainly run a lot smoother at 1ghz+
Sent from my Nooted friend...

paleh0rse said:
There are no mandatory hardware requirements for honeycomb, but it will certainly run a lot smoother at 1ghz+
Sent from my Nooted friend...
Click to expand...
Click to collapse
That's true and the more and more limitations are taken away as launch approaches..
I have no doubt it will run well, but also wonder if anyone will create a Nook version..

spikey911 said:
That's true and the more and more limitations are taken away as launch approaches..
I have no doubt it will run well, but also wonder if anyone will create a Nook version..
Click to expand...
Click to collapse
why not......

elcape said:
why not......
Click to expand...
Click to collapse
Well, this is just my opinion of course...
It will still be some time before we even see a 2.3
3.0 will not be out for a while and by the time that happens newer, faster, better, tablets will hit the market and catch everyone eye..
People may flock towards the newer tablets and leave the older ones behind..
I don't want to say it will never happen, but it is possible we won't see a 3.0 if the developers flock to newer tabs..
One thing is for sure, you will not see an official version from B&N.. I have my doubts there will even be an official 2.2 from them.

Is it bringing something amazing to the table? Haven't even bothered looking at honey just because the GUI stuff everyone likes looks ugly as hell.
Nook color was my first android device so I prefer the simple notification bar at the bottom, as well as using a taskmanager to kill/switch apps.
sent from a Nook Color using xda-app

spikey911 said:
Well, this is just my opinion of course...
It will still be some time before we even see a 2.3
3.0 will not be out for a while and by the time that happens newer, faster, better, tablets will hit the market and catch everyone eye..
People may flock towards the newer tablets and leave the older ones behind..
I don't want to say it will never happen, but it is possible we won't see a 3.0 if the developers flock to newer tabs..
One thing is for sure, you will not see an official version from B&N.. I have my doubts there will even be an official 2.2 from them.
Click to expand...
Click to collapse
I hope you realize that the fine folks at Cyanogen are already working on a NC version of CyanogenMOD version 7 -- which is a Gingerbread (2.3) rom. Some of their best devs are on it, and they've even gotten it to boot already!
So, don't be surprised when you see 2.3 sooner, rather than later...
Sent from my Nooted friend.

[App]Netflix for 2.2 Devices

Got this from droidlife and I havent tested it yet since im on 2.3 but wanted the fam to have a crack at it and see if it works or not
http://www.mediafire.com/?4xwncz7doz475tj
We just threw up a post about the latest Netflix update which brought support to the original DROID, but what we failed to originally realize is that the update removed the device check which means in theory, that it should be able to work on all phones. Well, guess what? I loaded it up on my DROIDX2 (which is “not” supported) and it installed just fine and is now streaming a video. I’m loading it up on other devices too, but wanted to make sure you all knew. Feel free to grab it below and install – let us know how it goes!
*Note – this is not a hacked version. This is 100% the market version.
Update: Works on Thunderbolt (rooted 2.3), DROIDX2, DROIDX (2.3), and Xperia PLAY.
Update 2: No XOOM support though.
Update 3: Looks like it’s pretty hit or miss. Definitely sounding like it’s not working on stock Thunderbolt which is a damn shame.
Cheers Brandon!
Click to expand...
Click to collapse
http://www.droid-life.com/2011/05/2...ice-check-should-work-on-all-android-devices/

It didn't work for me... It goes to login screen and then goes back to home screen when trying to login dang I may have to jump to EE03 finally..

Doubt that will work or anything for that matter because they have been trying to get it to work on many devices on the main Android forums of XDA and not many people are having luck.
Seems like we'll just be waiting for now until Netflix releases something. They did just add...
LG Revolution, Motorola Droid and Casio G'zOne Commando
But no Epic 4G yet

For snapdragon 2.2 devices
Did the news get around about a guy named butcher pete?

quickstang said:
Doubt that will work or anything for that matter because they have been trying to get it to work on many devices on the main Android forums of XDA and not many people are having luck.
Seems like we'll just be waiting for now until Netflix releases something. They did just add...
LG Revolution, Motorola Droid and Casio G'zOne Commando
But no Epic 4G yet
Click to expand...
Click to collapse
gotta love verizon huh lol

It is not the epic 4g, it is hummingbird based devices on the 2.2 kernal. Our cm7 isnt built on gingerbread source. It is still on 2.2.1 source. The reason that you need 2.3 because it has better hardware support for the hummingbird processor due to the fist flagship device to have a hummingbird was on 2.3 release not 2.2 release. Also, our software DRM that Samsung gave us in our 2.1 and 2.2 based ROMs sucks/is unable to support Netflix web streaming.
Did the news get around about a guy named butcher pete?

marcusant said:
It is not the epic 4g, it is hummingbird based devices on the 2.2 kernal. Our cm7 isnt built on gingerbread source. It is still on 2.2.1 source. The reason that you need 2.3 because it has better hardware support for the hummingbird processor due to the fist flagship device to have a hummingbird was on 2.3 release not 2.2 release. Also, our software DRM that Samsung gave us in our 2.1 and 2.2 based ROMs sucks/is unable to support Netflix web streaming.
Did the news get around about a guy named butcher pete?
Click to expand...
Click to collapse
So basically we need to get new a new phone already huh? lol

I am just thinking.
quickstang said:
So basically we need to get new a new phone already huh? lol
Click to expand...
Click to collapse
So what would happen if we took the DRM from the leaked gingerbread rom and placed it into a froyo rom? Do you think netflix would work. I am took afraid of trying this out myself for fear of reflashing my entire rom and reconfiguring all my setting again.

marcusant said:
It is not the epic 4g, it is hummingbird based devices on the 2.2 kernal. Our cm7 isnt built on gingerbread source. It is still on 2.2.1 source. The reason that you need 2.3 because it has better hardware support for the hummingbird processor due to the fist flagship device to have a hummingbird was on 2.3 release not 2.2 release. Also, our software DRM that Samsung gave us in our 2.1 and 2.2 based ROMs sucks/is unable to support Netflix web streaming.
Did the news get around about a guy named butcher pete?
Click to expand...
Click to collapse
Thanks for the info.....was'nt aware that 2.3 was built around the Hummingbird processor. Damn....that should really give our Epic's a kick in the ass once it's official. Combined with some overclocked kernels and EXT4, maybe then we will see this phone's full potential.......it only took 8 monthes

jamice4u said:
So what would happen if we took the DRM from the leaked gingerbread rom and placed it into a froyo rom? Do you think netflix would work. I am took afraid of trying this out myself for fear of reflashing my entire rom and reconfiguring all my setting again.
Click to expand...
Click to collapse
No, we need the hummingburd enhancements in the kernal.
Did the news get around about a guy named butcher pete?

netflix on syndicate from epic
i am currently running the syndicate rom on my epic 4g. i downloaded the app that meter 5 posted and updated it and it now works, maybe it might work on the stock rom. I know it is reported to work on the gingerbread rom but apparently it works on mine as well.

Just downloaded Netflix today from the Android Market. Running Bonsai 4.1.1 and I'm already streaming! Woot!

quickstang said:
Doubt that will work or anything for that matter because they have been trying to get it to work on many devices on the main Android forums of XDA and not many people are having luck.
Seems like we'll just be waiting for now until Netflix releases something. They did just add...
LG Revolution, Motorola Droid and Casio G'zOne Commando
But no Epic 4G yet
Click to expand...
Click to collapse
The Commando?! A guy in my class at Boeing has one of those...slowest damn phone ever! That think reminds me of my Treos when they were still stock, yet it gets NetFlix?

elbo450 said:
Just downloaded Netflix today from the Android Market. Running Bonsai 4.1.1 and I'm already streaming! Woot!
Click to expand...
Click to collapse
Ignore my post above...I just downloaded it from the Market and it's working as well. Giggity! Between TV.com, Droid Streamer and now NetFlix, I'm set

m5james said:
Ignore my post above...I just downloaded it from the Market and it's working as well. Giggity! Between TV.com, Droid Streamer and now NetFlix, I'm set
Click to expand...
Click to collapse
There's themed versions already, too.

kexec bootloader bypass coming in a few days

http://forum.xda-developers.com/showthread.php?t=1519448&page=21:D
once we get it ported to the D3 helloooo camcorder and adobe flash!

Huh?
Sent from my XT862 using xda premium

this loads a seperate kernel once the stock locked one loads so we can run a custom kernel for our roms.

GAHH!!!!!!
Sent from my DROID3 using xda premium

fap?

This looks awesome, I can't wait to get chrome loaded up on my XT860 running AOKP.

DoubleYouPee said:
fap?
Click to expand...
Click to collapse
yes, this is worthy of a fap, once its ported my body is ready

ssinisterss said:
yes, this is worthy of a fap, once its ported my body is ready
Click to expand...
Click to collapse
If this works for us, im kicking Bar Refaeli out of my house. This would be better than anything she could provide.

ssinisterss said:
yes, this is worthy of a fap, once its ported my body is ready
Click to expand...
Click to collapse
your body...LMAO!!!!!

Well, we won't necessarily have it in a few days. It will take a lot of work to port it to our devices because of hardware differences, and we would need someone very good at coding these types of things.

Pokelover980 said:
Well, we won't necessarily have it in a few days. It will take a lot of work to port it to our devices because of hardware differences, and we would need someone very good at coding these types of things.
Click to expand...
Click to collapse
it wont be as hard as it seems, we have the same internals as the razr minus the 1gb ram. i dont know if the kexec is the same (it should be for the omap 4430) but the only coding that would be different is getting the kexec to take the modded kernel. once its released for the razr within the week im sure hash is gonna have some fun with this.

ssinisterss said:
it wont be as hard as it seems, we have the same internals as the razr minus the 1gb ram. i dont know if the kexec is the same (it should be for the omap 4430) but the only coding that would be different is getting the kexec to take the modded kernel. once its released for the razr within the week im sure hash is gonna have some fun with this.
Click to expand...
Click to collapse
There was some discussion of this over at the Razr forum in that thread. The differences between the GSM and CDMA versions of the Razr are alone enough to cause major pains in porting it between the two devices, and it was originally developed for the GSM version.

i would think that since its a nice sized topic in our razr forums its gonna work for CDMA too. the dev of the work around won a developer contest and recieved a CDMA razr along with kejar.

Yay gsm!
Sent from my XT860 using xda premium

Pardon my ignorance on the topic, but this allows us to use another kernel on top of the stock one, but not replace it right? Is the only downside a longer boot time? Also will this be relatively easy to port due to similar hardware or will that another challenge in itself.

Yankeefan144 said:
Pardon my ignorance on the topic, but this allows us to use another kernel on top of the stock one, but not replace it right? Is the only downside a longer boot time? Also will this be relatively easy to port due to similar hardware or will that another challenge in itself.
Click to expand...
Click to collapse
so far the longer boot time is the only downside but its not a bad thing considering we reboot only to flash roms or refresh the phone a couple times a week and since it will let us have a fully working rom. this lets the phone boot with the gingerbread kernel behind the bootloader, then after the M splash screen it will boot into the ICS or modified GB kernel that is loaded.
we would have to have hashcode or anyone that has any kind of knowledge of how this really works tell us the time frame. as it stands we dont know anything other than it works on GSM razrs, and the dev has a CDMA razr he is porting it to and its days from release. we need to see the details on how to approach porting this to the D3/D4/bionic. it may not be that hard since its designed to do only 1 thing and hardware is mostly the same.

OP you are being way too optimistic in this thread. Chances of this being ported for D3 is very low as aboves has stated. It won't be anywhere as easy as changing the string "RAZR" to "Droid 3" in the kernels

eXecuter.bin said:
OP you are being way too optimistic in this thread. Chances of this being ported for D3 is very low as aboves has stated. It won't be anywhere as easy as changing the string "RAZR" to "Droid 3" in the kernels
Click to expand...
Click to collapse
like i said we have a few guys in here that have experience with coding. if it could be done with the cdma razr it can be done for the rest of them.

ssinisterss said:
like i said we have a few guys in here that have experience with coding. if it could be done with the cdma razr it can be done for the rest of them.
Click to expand...
Click to collapse
It's taking quite a long time to be ported from the GSM Razr to the CDMA one, though. There aren't many hardware differences between those two devices, but for those differences it's taking a large amount of time. Now imagine how long it will take, and how complicated it will be to port, with all of the hardware differences between the Droid 3 and the Razr (and not to mention the different models of the D3; I assume a kexec module for the XT862 would not work on the XT860 or XT883 without changes). You are being a bit too optimistic here, especially with your thread title. It's less a bootloader bypass and more a "we're just gonna load our own kernel after the bootloader loaded the default one, but we still can't change anything about the boot process."
I hate to be the bearer of bad news and the one to shoot down everyone's hopes and dreams, but at the same time I don't want people to get too worked up over this and then get incredibly disappointed when it doesn't come or takes ungodly forever for it to come to use.

Well, you went to the other extreme and assumed it's impossible to port and that even if it could be done it would suck or something like that.
I'd like to take a more neutral stance on this and
a) be exited that this approach is being taken on locked devices.
b) be exited that a relatively similar device to the D3 is getting this kind of attention. because it could make things easier for D3 devs to port it to this device.
c) wait patiently, with no ETA expectations and offer to help with whatever I can to the devs.
I think it's much better than waiting for someone to crack moto's keys.
It's at least a chance.
Hope devs can ( and want to ) do something with this : )
Pokelover980 said:
It's taking quite a long time to be ported from the GSM Razr to the CDMA one, though. There aren't many hardware differences between those two devices, but for those differences it's taking a large amount of time. Now imagine how long it will take, and how complicated it will be to port, with all of the hardware differences between the Droid 3 and the Razr (and not to mention the different models of the D3; I assume a kexec module for the XT862 would not work on the XT860 or XT883 without changes). You are being a bit too optimistic here, especially with your thread title. It's less a bootloader bypass and more a "we're just gonna load our own kernel after the bootloader loaded the default one, but we still can't change anything about the boot process."
I hate to be the bearer of bad news and the one to shoot down everyone's hopes and dreams, but at the same time I don't want people to get too worked up over this and then get incredibly disappointed when it doesn't come or takes ungodly forever for it to come to use.
Click to expand...
Click to collapse