Related
OK so my G Tablet is on the way and I've been reading and came across a comment on another forum that the ROM's that exist are built on the original stock software and that the most recent update may be causing problems with CWM? I will be getting my G Tablet on Wednesday, should I not do the update if I am going to be flashing a custom ROM? Thanks in advance!
drum747,
I believe everyone should make their own decisions. But if you ask me -- I'd tell you to simply stick with a stock G-Tablet right now.
When you get yours and go to Settings/About you can see the version -- something
like 1.1.xxxx -- probably 3588. If not, just about as soon as you get wifi connected
it will offer you an OTA (on the air) update to 3588. That's the current working version, and compared to the crud we had back last November it really isn't bad software.
It will lack the Market and some other things...you may have to be patient there.
But you can still side-load apps and download apps directly from a number of places.
But we are waiting. Our devs have found that there is software for a possible
Update 3991. The hope is that OTA 3991 will come down in the next few weeks.
If so, at 3588 stock you will be in perfect shape for that update. And then once you
have worked with it a while, you will be able to decide whether to stick with it -- or look at other options.
It seems like everyone who come in here looks at the ROMs available like a "all-you-can-eat" buffet. The immediately start flashing ROMs and moving around software
until something goes wrong and they are stuck. Indigestion!
With a good 3588 tablet, you can read and interact here and find out the biggest and
the best, and you can learn what you need to that when you are ready you can
move up to whatever you want without problems.
Do what you want. Enjoy the G-Tablet. I think it pretty darn good!
Rev
I agree.........
Stick with the most current stock version 3588. The next update officially available from viewsonic should be very soon, but I don't think it will be 3991 as advertised
3558 was different than what it started as, or it would seem based on what I have gathered from reading old threads.
ale
You know, I have a Droid X and have really enjoyed rooting it and trying different ROM's and was really looking forward to the same type of experience on this tablet. What is the advantage of waiting until the next update? Can't I update, do a full backup and go back to that if I want? Once I install a different ROM, I am then stuck at whatever update and no further updates? Is that why you are saying to wait? Are you saying there will be even better ROM's down the road based on the new update that is coming? Or just that the new update coming might have all the things we would like?
The next update might have some cool stuff... might even be as good or better than the custom stuff here... maybe...
Question is... did you buy the tablet to use it for media consumption or tinkering?
Answer that and you'll know what to do. Just don't forget to make nvflash to factory stock your best friend ;-)
A little of both I guess. Part of the reason I chose this tablet over others is because of the support and customization (and price!) I will try to wait for the next update before I tweak it (if I can!) Heh!! Thanks for the responses guys!! I appreciate the input!
K J Rad said:
The next update might have some cool stuff... might even be as good or better than the custom stuff here... maybe...
Question is... did you buy the tablet to use it for media consumption or tinkering?
Answer that and you'll know what to do. )
Click to expand...
Click to collapse
This is without the best quote I could image. Tinkering without first using the tab and getting to realize it's not a giant phone is the first step I think everyone should understand.
And if you do tinker then you should expect it to have opportunities (problems ).
drum747,
Not addressing your abilities or anything about you.
But read all the crash and burn threads on this forum.
IMHO, to many people are trying to do to much too fast and are
messing up their tabs and have to be bailed out.
I'm just saying be cautious, move slowly and carefully and
don't get into trouble.
However, my advice still stands. If you move on to other
ROMS, etc. now, you will cut off access to offline updates.
Then you will have to go back to stock, etc. And
sometimes going back is as much as problem as going up!
It still would be easier to stay stock now and if an update
doesn't come down soon -- you will have read and learned
and be ready to make choices.
IMHO.
Rev
IMHO... if it ain't powering your pacemaker then learn how to nvflash and have fun.
Be part of the revolution or watch it happen... ;-)
Thanks guys! I get what you're saying!
Sent from my DROIDX using XDA App
K J Rad said:
... learn how to nvflash and have fun.
Click to expand...
Click to collapse
QFT.
nvflash is not hard to get working. With a properly set up nvflash procedure and all the info on these forums, the gTab is an unbrickable as it gets.
updates
I upgraded to the vegan 7, gingerbread, how do I go back to the original stock to get the latest updates from viewsonic when update arrives?
Second that
I absolutely agree to stick with the stock ROM and play for a while. The 3588 update is very stable and usable when you change to Classic Home. I have been using it till now, side loading apps and enjoying a lot without having to worry about custom ROMS and such.
The people who are saying stay stock for the updates are glossing over the fact that the Vs updates will just make the stock UI suck a little less.
Before I bought my G tab I had never had any experience with tablets or smart phones or even android for that matter. I have flashed 4 or 5 roms onto my tablet without incident, no boot loops, no dead tab, no anything that anyone would consider a bad experience. I'm using Vegan 5.1.1 for the record, for the third time.
Read a few of the reflash to stock with nvflash threads to prepare yourself in case something does go wrong, but there is no reason to stay stock on this tablet theres to much dev goodness and too much customizationability ( is that even a word?) not to try different things.
Roxxas049 said:
The people who are saying stay stock for the updates are glossing over the fact that the Vs updates will just make the stock UI suck a little less.
Before I bought my G tab I had never had any experience with tablets or smart phones or even android for that matter. I have flashed 4 or 5 roms onto my tablet without incident, no boot loops, no dead tab, no anything that anyone would consider a bad experience. I'm using Vegan 5.1.1 for the record, for the third time.
Read a few of the reflash to stock with nvflash threads to prepare yourself in case something does go wrong, but there is no reason to stay stock on this tablet theres to much dev goodness and too much customizationability ( is that even a word?) not to try different things.
Click to expand...
Click to collapse
Yeah I think it all boils down to what the individual wants and is willing to risk..this forum makes it easy and there are plenty of options to try just always prepare for the unexpected and dealing with the experimentals expect anything to happen!!
Who am I kidding?! There is no way I will be able to wait for the next update. I already have a ton of files set up to load on my G tablet. I will be Modding within hours of my full charge! Guess its just my nature! Thanks guys!
Butch, thanks I will be reading everything to make sure I do it right Thanks for the advice everyone!
Sent from my DROIDX using XDA App
Closing Word...
Everyone that has contributed to this thread--
I have tried to voice the side of conservatism and restraint and
good judgement in this thread. My intention was not to hurt any
feeliings or pick on anyone or rain on anyone's parade.
But if you read what's going on in these forums, there are a lot
of folks having problems. A lot of them are in over their heads and
some have been careless and others made honest mistakes.
I know for my part, I have been working hard to try to help folks
find the tools and make the decisions to get back on track. I'm sure
I have made mistakes and my opinions are mine!
But I speak for myself in saying that even though I am semi-retired
and have more time than most -- I can't keep up this pace. And I've
heard others of the helpers say the same thing.
I also call your attention to the "TwoTapsX" thread and the fact that
the moderators are aware of the problems people are having. Roebeet
has put together a splendid ROM that many think will be the next
generation of G-Tablet software. But because of the complexity of the
mods folks already have had in the tablets, and because of the human
factors listed above -- a lot of folks have messed up their tablets.
In My Humble Opinion: Somebody has got to say that in spite of all the
"opportunities" for mods in these forums -- folks have got to start
exercising more restraint, more good judgement, more common sense in
what they do.
The devs and the folks who are helpers here can't be expected to carry the
load of keeping everyone up and running with the current problem rates. I
sometimes don't agree with the moderators, but this time I see their point.
We users have a good thing here, but if it keeps being abused......
********
Having said that, I am done here. I wish you well.
Rev
/EOT
Just an update. Within an hour of booting up I had installed CWM and Vegan. It was an easy process and now I love my g tablet!
Sent from my DROIDX using XDA App
Welcome! Enjoy the koolaid... ;-)
Nice responce
so im sorry for bringing this up (i read the sticky) but i am not sure what the latest update means about honeycomb video drivers from nvidia. does that mean that there are no video drivers that are going to be released for the gtab from now on? does that mean its impossible to port honeycomb to the gtab? i dont know how to interpret their response and that is going to help me decide what to do with it (since i just got it). thanks!
From what I can read into it, nVidia has stated that they will continue dev and support for the gtab for as long as Viewsonic requests them to do so. And Viewsonic has stated that they are going to continue dev and support. So, in short, yes. We will most likely see Honeycomb at some point in the future. We just don't know when.
Sent from my Desire HD using Tapatalk
so their message wasnt saying "f u gtab, u get nothing" ? its only for as long as viewsonic continues to support it?
joshtb86 said:
so their message wasnt saying "f u gtab, u get nothing" ? its only for as long as viewsonic continues to support it?
Click to expand...
Click to collapse
Yes, up until they decide the Gtab is old news and they determine that it would not be cost efficient to do so. After all of those tablets sold on woot (over 10,000) I can't imagine that would be any time soon.
Myself, I could care less if Honeycomb makes it to the Gtab. It would be nice, but CM7 is serving me very well for anything I need to do with it. There is a bit of choppiness in videos using the YouTube app, but if viewed via the web browser (I use Skyfire) they are as smooth as can be over wifi or with a good 3g signal. Native video drivers for even Gingerbread would be very helpful and I feel that we will see them long before anything of the Honeycomb flavor.
I wouldn't dump my Gtab just yet, there's way too many ways to have fun with it considering all of the dev work that's still being done by GoJimi, Calkulin, rothnic, roebeet, clemsyn, pershoot and many others.
MOD Alert! - You may want to move this thread to G-tab General or Q&A since this is not Developmental.
okay. so what exactly did nvidia mean? and if they stop supporting the gtab, what does that mean for the gtab? and video acceleration - is that just video watching, or does that mean 3d acceleration for video games as well?
I can't point you to the exact news release but Nvidia did officially say last week what hitekredneck said about continuing to support the Ginger chip. They indicated that the previous statement about not continuing to support the Ginger was in error by an unofficial spokesman (I think I am remembering this correctly).
I kinda agree with hitekredneck about Gingerbread on the Gtablet. I bet we see those hardware video drivers released by Nvidia for Gingerbread soon making GB a complete ROM.
what exactly do these video drivers do?
Has the Viewsonic Gtablet development become a standstill?
Thoughts?
Opinions?
No.... I believe not.
Now everyone's holding their breath for HC.
Here somewhere is a post about latest development (sorry can't find it now).
HC is already booting on G-tab. Hopefully devs will get everything they need to get it going.
Keep my fingers crossed!!!!
You have a cyanogen tag in your sig and yet you ask that? They are releasing nightlies at least once a week. As far as Honeycomb goes it may be booting but its completely worthless to use.
I think I'll keep my thoughts and opinions to myself as anything negative about the wonderous GTab is not tolerated here
thebadfrog said:
You have a cyanogen tag in your sig and yet you ask that? They are releasing nightlies at least once a week. As far as Honeycomb goes it may be booting but its completely worthless to use.
I think I'll keep my thoughts and opinions to myself as anything negative about the wonderous GTab is not tolerated here
Click to expand...
Click to collapse
LMFAO, you can always talk about the "horrible viewing angle" everybody CAN agree on!
Kenfly, there is actual progress reported that I believe involves a dump of an ASUS Honeycomb box that has been ported to the Adam and there is a picture of it on a G-tab. I just read about actual WPA2 support too.
Here is the thread: http://forum.xda-developers.com/showthread.php?t=1065220
The good news is, Roebeet has taken an interest too, so there are some VERY clever guys working on this!
Yes there is but it is completely unuseable at this point.
I was told the viewing angles are not horrible and to expressing my opinion of that as well
http://forum.xda-developers.com/showthread.php?t=1064775
Follow that thread. Oozura is doing a great job keeping everyone up to date with cm nightlies and releases with bugs and bug fixes. They are making huge progress on major issues right now. It means at some point Gojimi will update VeganGinger as well.
If you follow that thread keep mashing that thanks button for him so people know there is interest and he keeps posting
I see it slowing down as more turn towards the newer tablets on the market. Updates wont be as frequent...
If you have it setup good now then you'll be ok. Its not like the internet, video or audio will stop working because of this.
kenfly said:
Has the Viewsonic Gtablet development become a standstill?
Thoughts?
Opinions?
Click to expand...
Click to collapse
No?
Looks like tons of action to me - pershoot and others have delivered stable overclocked/undervolted kernels in the past week, and the CM7 team has cranked out two stable and about 10 nightly revs in the past week, going from "yes, it sorta works" to functional camera and some hardware acceleration for video playback.
What projects are you working on?
there are more forums to search than the ones here (hint)
There's a lot going on, in early (VERY EARLY) stages.
While some might believe that the Gtab is worthless, I would argue that the hardware itself is not at all. The company that put their name on it, and their "support" might very well be as worthless as a batteries to the Amish.
There are experiments going on utilizing The Notion Ink Adam, and porting it's software to the G-tab. There's a rumor that they are getting an official GB update, and if portable to the G-tab, then we could essentially have an "official" GB Rom (including drivers from Nvidea), without VS needing to get their hands dirty. There are a few comparable (in hardware) tablets out there that are getting the support from their manufacturers that we would like to get from VS. If we can't get VS to update, then the next best thing is to borrow updates from other systems.
If it all works out, it will definitely not be a quick release. Lots of testing would be needed, since the code being worked on is not "made" for the G-tablet.
The reason that it seems like development has halted, or at best, slowed down, is because nothing new is coming from the allmighty VS. Nothing can be developed from the nothing that they are constantly providing. The only development that can be done is using existing Roms, and tweaking them. The bottom line, though, is that unless VS comes out with a GB Rom WITH hardware drivers, the current batch of custom Roms, Vegan-Tab, VeganGinger, CM7, TNT, etc. are dead in the water, and will never have hardware acceleration, since they are all based off of old code, that doesn't include it.
So, simple answer, there are developments that are ongoing, there are tweaks and fixes, possibly additions to some of the existing roms, but there will never be any development on new VS rom, until VS actually releases a new VS rom.
Only one person is building off VS firmware. Everyone else is using Google source and from the commits that Nvidia is making to git. VeganGinger and CM7 are under constant development and CM gets closer everyday to finalizing hardware acceleration. Vegan-Tab is froyo and based off vega firmware and has hardware acceleration as does TNTlite.
Depending on Notion Ink, the king of stretching the truth, for something is knuts
And yes there are some half ass non useful ports of Honeycomb posted on other sites. Nothing works. Its a honeycomb gui hacked into an old kernel
TJEvans said:
While some might believe that the Gtab is worthless, I would argue that the hardware itself is not at all. The company that put their name on it, and their "support" might very well be as worthless as a batteries to the Amish.
Click to expand...
Click to collapse
Great analogy. =)
TJEvans said:
There are experiments going on utilizing The Notion Ink Adam, and porting it's software to the G-tab. There's a rumor that they are getting an official GB update, and if portable to the G-tab, then we could essentially have an "official" GB Rom (including drivers from Nvidea), without VS needing to get their hands dirty. There are a few comparable (in hardware) tablets out there that are getting the support from their manufacturers that we would like to get from VS. If we can't get VS to update, then the next best thing is to borrow updates from other systems.
Click to expand...
Click to collapse
The NI software release, if they do in fact follow through with something for once, will be utilizing the exact same GB-compatible drivers that we already have. We already have "official" GB ROMs with the same level of HW accel that anything from NI would come out with. We already have those drivers from nVidia. =)
But you're right in implying that VS won't have to get their hands dirty. =)
TJEvans said:
Nothing can be developed from the nothing that they are constantly providing. The only development that can be done is using existing Roms, and tweaking them. The bottom line, though, is that unless VS comes out with a GB Rom WITH hardware drivers, the current batch of custom Roms, Vegan-Tab, VeganGinger, CM7, TNT, etc. are dead in the water, and will never have hardware acceleration, since they are all based off of old code, that doesn't include it.
So, simple answer, there are developments that are ongoing, there are tweaks and fixes, possibly additions to some of the existing roms, but there will never be any development on new VS rom, until VS actually releases a new VS rom.
Click to expand...
Click to collapse
Actually.... you're incorrect here. New development is being done completely independent of VS. It's called CyanogenMod-based and AOSP-based ROMs and they are completely different than those based on VS or NI-based ROMs which anything based on those are in fact MODs and tweaks. CM and AOSP ROMs are based on newer code and do include the foundation for hw acceleration.
So to summarize - development is not dead if you're not based on a locked bootloader and stock ROM from VS. If you're based on Google and nVidia then there is definitely development going on. It's all in what your base is.
We already have "official" GB ROMs with the same level of HW accel that anything from NI would come out with. We already have those drivers from nVidia.
Click to expand...
Click to collapse
You'll have to excuse my ignorance on this issue, as all I've used so far is Vegan-Tab. I love it, it's stable, and I've not seen any inherent problems with it, so I figure, why change?
But, I thought that CM7 and VeganGinger had issues with video playback and 3d video acceleration, since Nvidea is "no longer going to support the Harmony Tegra 2 chipset." I don't know much about CM7, but from reading their website, and observing some of the experimental posts, it doesn't seem that they've been able to truly replicate the drivers that, I believe, Nvidea owes us. Nvidea said that they will provide support and updates if manufacturers requested it. As far as I know, Viewsonic only had one update since they made that statement, and it didn't include anything new from NVidea.
I had assumed that since this rumored NI GB update was official from the manufacturer, that they wouldn't have done it without getting official drivers from Nvidea.
I'm sorry, is there something I'm missing? I thought that it was a big deal that NVidea hasn't provided driver updates for true hardware acceleration, and that it can't be achieved without informaiton from them, and that they've decided ot no longer support...
it's a confusing world in the land of G-Tab.
TJEvans said:
You'll have to excuse my ignorance on this issue, as all I've used so far is Vegan-Tab. I love it, it's stable, and I've not seen any inherent problems with it, so I figure, why change?
But, I thought that CM7 and VeganGinger had issues with video playback and 3d video acceleration, since Nvidea is "no longer going to support the Harmony Tegra 2 chipset." I don't know much about CM7, but from reading their website, and observing some of the experimental posts, it doesn't seem that they've been able to truly replicate the drivers that, I believe, Nvidea owes us. Nvidea said that they will provide support and updates if manufacturers requested it. As far as I know, Viewsonic only had one update since they made that statement, and it didn't include anything new from NVidea.
I had assumed that since this rumored NI GB update was official from the manufacturer, that they wouldn't have done it without getting official drivers from Nvidea.
I'm sorry, is there something I'm missing? I thought that it was a big deal that NVidea hasn't provided driver updates for true hardware acceleration, and that it can't be achieved without informaiton from them, and that they've decided ot no longer support...
it's a confusing world in the land of G-Tab.
Click to expand...
Click to collapse
The rumored NI GB update is just that - rumor just like all the other NI rumors. We'll see what happens.
As to nVidia - the 3991 update that was later pulled from VS contained updated GB-compatible libs that were from the Gingerbread Ventana system image from nVidia. Those libs were (and still are) in CM7 and AOSP and VEGAn-TAB. Hacks and mods have been inserted to make CM7 work with them and hw accel is functioning much better after pershoot's kernel overclocking.
thank you for the clarification
I attempted to flash my gtab with Android OS 3.0. I am not a noob to flashing a new FW so I am not sure what happened. But now my gtab sits at the viewsonic screen and that's it. I try to boot into CW but when I press the Vol+ key I get the message at the top:
"Detect a recovery key pressed"
"Booting recovery kernel image"
And that is it. So I can't boot into CWM to mount my storage. Can ANYBODY please help me?!?!?! I'm freakin out that I have ruined my gtab.
Thanks
-Buddah
You tried to jump a cliff and fell down the great chasm. What you need to do is visit my website (just put it up today) and follow the procedure to nvflash. It's written for beginners like yourself so I'm sure you won't have any problem with it.
http://viewsonic-gtablet-for-dummies.webs.com/nvflash.htm
What happened was you tried tried to use the wrong CWM. Just read my website and you'll see what I mean.
Added by edit.
Also, visit my ROM page for the appropriate way to flash a ROM.
Assuming you used Bottle of Smoke, were you on a 1.1 ROM (ie. 3588 stock, VEGAn-TAB or CM7) and then flashed with cwm? If so, that's your root cause (1.1 ROM jumping to a 1.2 ROM with cwm = soft brick).
As mentioned, you need nvflash to fix it. It's most likely a soft-brick, not a hard brick.
dun dun dun....another one bites the dust, da da dun dun dun
Many many thanks! I NVflashed my gtab and I am back up and running.
There's been a wave of people soft-bricking their gtab because they were not aware of the 1.1 - 1.2 issue. Wonder if that has anything to do with the recent woot and tigerdirect sales...
buddah77 said:
Many many thanks! I NVflashed my gtab and I am back up and running.
Click to expand...
Click to collapse
Just curious. Did you use my nvflash instructions or the ones in this forum? I just want to get a feel of if my site is helpful to beginners at all. I've simplified the instructions as much as I could without giving up the technical stuff.
goodintentions said:
There's been a wave of people soft-bricking their gtab because they were not aware of the 1.1 - 1.2 issue. Wonder if that has anything to do with the recent woot and tigerdirect sales...
Click to expand...
Click to collapse
I, for one, want to again thank the power users here for their excellent user support. YOU have the hardest job of all and I appreciate anyone who helps do post-support for my own ROMs. It is very much appreciated.
goodintentions said:
There's been a wave of people soft-bricking their gtab because they were not aware of the 1.1 - 1.2 issue. Wonder if that has anything to do with the recent woot and tigerdirect sales...
Click to expand...
Click to collapse
*raises her hand slowly*
I got a gtab from woot. I soft-bricked it because it came with the 1.2 bootloader and I installed CWM on it (wanted to install CM7) Luckily the instructions on this forum got me back up and running with nvflash.
P.S. Wish I would've know about your website good intentions. The post I followed was very good, but I always like to see more than one set of instructions before doing something I'm not comfortable with. Acutally I wish I would've seen that stuff before I soft-bricked my gtab :-(
I will say this, once you know how to use NVFlash you can do a lot more experimenting...the worst case is you lose a configuration and have to re-load apps.
I think its sad to know so many GTabs are out in the wild running stock, with people going "These Android tabs are Crap!"....
@goodintentions:
I followed your instructions to the letter and that is what did it for me. It was very accurately detailed and left no room for interpretation. I work in IT Support so I have a fair amount of experience reading crappy instructions. Yours was very helpful and again, thank you for saving me so much time and frustration.
HeadRusch1 said:
I will say this, once you know how to use NVFlash you can do a lot more experimenting...the worst case is you lose a configuration and have to re-load apps.
I think its sad to know so many GTabs are out in the wild running stock, with people going "These Android tabs are Crap!"....
Click to expand...
Click to collapse
That's one of the problems with Android vs *gasp* Ipads, the fragmentation and butchering by some vendors leave a bad taste in some peoples mouths, so to speak.
If not for the developers working on the Gtab, I would have probably taken mine back way before now. Some people aren't all that tech savvy and even me, having worked with PC and various gadgets hardware and software wise for many years, and I still scratch my head from time to time.
I've never had stock but keep testing ROMS. Even the more stable ones had bugs. I wish there was a really good stable Honeycomb out I'm considering the Asus tablet but want to wait for Kal-El. Partly because of the better screen/ram. Things that will never get fixed/upgraded with software.
I think part of the problem is that a lot of the times communication is hard between the tech savy and the not-so tech savy.
In the android world, we say "flash" instead of "install". Believe it or not, but this is a source of confusion for a lot of people out there. For kicks, I did a search and couldn't find a single explanation that says something like flash = install. Remember that we're dealing with people who came from the PC world.
The confusion gets progressively worse from there. What's clockworkmod? What's recovery? What's nvflash? Try searching for these terms and you will find explanations that only induce more questions.
I regularly have to instruct totally tech-illiterate people how to use their devices. This has given me an insight into how to communicate with people who are not tech savy.
I remember my first PDA (a DELL AXIM) and had a hard time wrapping my head around how the OS and firmware were integrated. I was used to the the whole hardware / OS separation on PC's and this was hard to ween myself off of. My DAP's were the same way as my PDA, and so when I started messing with Android it at least made some sense to me.
goodintentions said:
In the android world, we say "flash" instead of "install". Believe it or not, but this is a source of confusion for a lot of people out there.
Click to expand...
Click to collapse
This did confuse me at first, but something dawned on me as to why it may be like this. In the android world, we do install apps. So saying that we are installing a rom would possibly lead to more confusion. "where's the APK for me to install Brilliant Corners?" etc.
Seems we use Flash when speaking of operating systems, but install when speaking of applications.
But we don't ever hear people say "I flashed windows 7 last night."
goodintentions said:
But we don't ever hear people say "I flashed windows 7 last night."
Click to expand...
Click to collapse
Updates to hardware devices (BIOS, video firmware, cdroms, etc) usually are refered to as flash... pretty much forever
goodintentions said:
But we don't ever hear people say "I flashed windows 7 last night."
Click to expand...
Click to collapse
fortunately (or unfortunately ependong on your outlook) we don't have 17 different interpretations of one Windows OS version. And most lay users really don't repetatively install different operating systems, either.
TJEvans said:
fortunately (or unfortunately ependong on your outlook) we don't have 17 different interpretations of one Windows OS version. And most lay users really don't repetatively install different operating systems, either.
Click to expand...
Click to collapse
Haha, back in my youthful days (before I turned 103) I tried out every operating system in existant at the time. This included all the windows versions and linux distros. I also tried (sometimes succesful) to flash mac os into pc platform. Fun times.
Hey guys, So I made an attempt to port 3.2 sdk to nook and i had a minor success with it.
Basically i have used Divine-Madcat's modifications from 3.0 sdk with 3.2 sdk image from Google, and after a very few changes it worked!!
But there are a lot of problems right now, for ex-
It takes a lot of time to load up and screen remains blank unless i use power button,
Display just goes blank randomly but comes back on using power button,
Android seems to take touch input as a mouse input and displays a round pointer,
laggy as hell(sometimes, randomly it goes smooth), probably displays one frame per second, and usually hangs up after a minute of use.
Wifi-not working
sd-card- not working
This is in no way usable right now, but i am posting the zip file anyway, hoping that someone will come out of no-where and help me fix this(thinking of this as an opportunity to learn)
So try it if you are feeling adventurous and want to fix things up.
Format data before u proceed.
DO NOT FORMAT BOOT.
MEDIAFIRE LINK
Disclaimer: I am not responsible for what happens to your nook, if you decide to flash this zip(though it likely won't do any damage).
reserved for future
Good luck to you, kind sir.
Looks good, but not even close to daily driver. Screenies?
None of the SDKs, including my own, are daily drivers. Until we can compile code, they will never be daily drivers.
Well, your SDK 11 port is pretty functional, just a little graphics lag.
ikingblack said:
Well, your SDK 11 port is pretty functional, just a little graphics lag.
Click to expand...
Click to collapse
Yes, it booted, but by no means was it a driver. It wasn't just graphics lag, it was overall lag. hardware acceleration was a no go... Look, it was fun to play with, but never a driver.
Unless deeper blue comes in with something (not saying he can), these will always be experiments; there is just too much code that needs to be compiled for our device for it to really work...
If you say so.
ikingblack said:
If you say so.
Click to expand...
Click to collapse
Given our respective success in porting things, i think i will value my opinion just a bit more, sorry.
Divine_Madcat said:
Yes, it booted, but by no means was it a driver. It wasn't just graphics lag, it was overall lag. hardware acceleration was a no go... Look, it was fun to play with, but never a driver.
Unless deeper blue comes in with something (not saying he can), these will always be experiments; there is just too much code that needs to be compiled for our device for it to really work...
Click to expand...
Click to collapse
Well you are right, this pretty much is an experiment and its a good way for me to learn things, but u never know maybe someone will get their hands on that latest driver, or maybe someone will figure a workaround, those guys at notion ink Adam have a very good honeycomb port which people use as a daily driver.
Progress is progress. At the same time, I'm starting to feel like we're hitting a brick wall without any type of hardware acceleration. The SDK ports themselves usually run next to fine functionality wise, but the lack of hardware acceleration means that virtually all of honeycomb is unstable without massive tweaking.
rigy73 said:
Well you are right, this pretty much is an experiment and its a good way for me to learn things, but u never know maybe someone will get their hands on that latest driver, or maybe someone will figure a workaround, those guys at notion ink Adam have a very good honeycomb port which people use as a daily driver.
Click to expand...
Click to collapse
That isn't too surprising, since the hardware is the same as every other tablet (Tegra2), and most of the acceleration should work without needing a recompile. On the other hand, we have to use the SDK code, which is compiled very generically, and we don't have that luxury.
Divine_Madcat said:
Given our respective success in porting things, i think i will value my opinion just a bit more, sorry.
Click to expand...
Click to collapse
Of course.
I still really appreciate the random efforts at a Honeycomb ports - it's unfortunate there isn't a larger Honeycomb dev community looking at this device, but at the same time completely understandable when you read the struggles of DB, DMC, etc., and the relatively dim outlook without a proper 3.0/.1/.2 source release.
For a long time I just thought it'd be a matter of time and folks would be right back at it - but now that it's taking a long while, there's real concern that if/when a proper source is released, will people still be interested in developing for the NC?
So yeah - I appreciate seeing any efforts pop up. It reminds me people are trying, and that's awesome.
CM based roms work just fine - but there's something decidedly underwhelming about the 2.x experience on a tablet.
arrjaytea -
I could guarantee, with the AOSP code, the nook would be an even neater device. Frankly, assuming we dont lose a dev base, i see great things for our device when ICS hits. As it is, from everything i have heard form our CM7 brethren, CM7's efforts are not for waste; many lessons and fixes learned here will help future efforts..
Assuming el goog keeps their word, the nook is still living the high life.
I really hope the current devs stick around long enough to dev a great ICS rom. I cannot wait for that at all. Finally, a proper HC-"based" rom for it.
In my opinion we let Google get to big by adopting their "free" services. They are as evil as Microsoft was/is in my eyes now. Not releasing code that they basically said would be open and public until it is "end of life" goes against the foundation of what android was supposed to be about. They are like Walmart in that they undercut the little guy to drive them under and then piss on us. Had it not been for android, alot of us would probably be running Openmoko on our phones and maybe tablets. Flames away
foltz61 said:
In my opinion we let Google get to big by adopting their "free" services. They are as evil as Microsoft was/is in my eyes now. Not releasing code that they basically said would be open and public until it is "end of life" goes against the foundation of what android was supposed to be about. They are like Walmart in that they undercut the little guy to drive them under and then piss on us. Had it not been for android, alot of us would probably be running Openmoko on our phones and maybe tablets. Flames away
Click to expand...
Click to collapse
If they release the code, there's a chance that the Android brand will be further fragmented and destroyed by improper use of it. Blame the Chineese tablet makers for stuffing 1.6 on tablets, that's what this is a result of.
arrjaytea said:
I still really appreciate the random efforts at a Honeycomb ports - it's unfortunate there isn't a larger Honeycomb dev community looking at this device, but at the same time completely understandable when you read the struggles of DB, DMC, etc., and the relatively dim outlook without a proper 3.0/.1/.2 source release.
For a long time I just thought it'd be a matter of time and folks would be right back at it - but now that it's taking a long while, there's real concern that if/when a proper source is released, will people still be interested in developing for the NC?
So yeah - I appreciate seeing any efforts pop up. It reminds me people are trying, and that's awesome.
CM based roms work just fine - but there's something decidedly underwhelming about the 2.x experience on a tablet.
Click to expand...
Click to collapse
After working a lot more with honeycomb port, i think i am happy that a lot more developers are actually working on cm7 than on honeycomb ports, these ports are a good way to try honeycomb on nook and have a little fun but, i don't think that even if we solve the video drivers issue honeycomb sdk could be used as a daily driver. The problems are just too much and the amount of tweaking it would require to get a good usable rom would not be worth it. Even functionality wise, sdk's have lots of problem. As for when source it released i think we will get at least one more CM port simply because the no of nook owners is just a lot right now.
nicatronTg said:
If they release the code, there's a chance that the Android brand will be further fragmented and destroyed by improper use of it. Blame the Chineese tablet makers for stuffing 1.6 on tablets, that's what this is a result of.
Click to expand...
Click to collapse
That's the inherent risk involved in adopting the open source model. You have a chance of fragmentation because you have so many manufacturers developing device or brand specific code and you have many developers developing codes specific to their roms, but what some see as fragmentation others see as variety, accessibility, and community driven problem solving. Android is probably on twice as many devices as Apples iOS. In my opinion a little fragmentation is worth the price.
I am disappointed that Google didn't release the source code. Anybody who has the ability to do some crazy like run honeycomb on their G1 phone or any other phone for that matter should be prepared for an experimental experience.
As for manufactures the Chinese putting Donut on their tablets--perhaps would have been easier for them to put Honeycomb on it if Google would have released the source codes. A lot of us are running phone OSes on our tablet albeit most of us are running Gingerbread on our Nook colors, but it would be nice to get a tablet OS like Honeycomb. Ice Cream Sandwich is suppose to be a Q4 release, but we'll see if that still happens. At least their is some hope. Just my humble 2 cents.