I think I may have read it requires dual core, but if not...what are the odds of us getting this bad boy (Google Body) on NC. I also wonder if any of the Galaxy S devices would run it?
Sent from my SPH-D700 using XDA App
abowlby said:
I think I may have read it requires dual core, but if not...what are the odds of us getting this bad boy (Google Body) on NC. I also wonder if any of the Galaxy S devices would run it?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
http://dl.dropbox.com/u/15218297/Body_1.0.apk
Tried but failed, but it looks like it requires HC sadly.
I'm sure it'll run once we have HC set up. The NC has a powerful (for an android device) GPU.
gallahad2000 said:
I'm sure it'll run once we have HC set up. The NC has a powerful (for an android device) GPU.
Click to expand...
Click to collapse
I wouldn't go as far as to say it's "powerful"
It's got the same GPU as the Moto Droid, which benchmarks just a tad bit below the Nexus One. Considering the Nexus One is significantly below the Galaxy S/Tegra 2 phones, we're basically at the low end of the GPU spectrum.
Which isn't too bad considering this is an E-reader
MrOtsKrad said:
http://dl.dropbox.com/u/15218297/Body_1.0.apk
Tried but failed, but it looks like it requires HC sadly.
Click to expand...
Click to collapse
mirror please. that poor dropbox account is a top hit in google and has been temporarily shut down LoL
Link3737 said:
I wouldn't go as far as to say it's "powerful"
It's got the same GPU as the Moto Droid, which benchmarks just a tad bit below the Nexus One. Considering the Nexus One is significantly below the Galaxy S/Tegra 2 phones, we're basically at the low end of the GPU spectrum.
Which isn't too bad considering this is an E-reader
Click to expand...
Click to collapse
try owning a hero if you want low end. nook blows it away. not nearly as high performance as my galaxy tab mind you, but nook color is definitely sufficient for most 3d operations.
I too have been wondering WHY body needs honeycomb... will be interesting to see if it can possibly run on something other than the xoom.
Please ... where exactly do I put that xoom fingerprint in my android os to make it appear as a legit honeycomb device in the market?
"ro.build.fingerprint=verizon/trygon/stingray:3.0/HRI39/101999:user/release-keys
xoom market fingerprint"
edit: oh nevermind - I'm going to assume it goes into build.prop. let me play wtih that a minute...
edit2: still can't see the body app on the market with that fingerprint in build.prop.
dkelley said:
edit: oh nevermind - I'm going to assume it goes into build.prop. let me play wtih that a minute...
Click to expand...
Click to collapse
I'm also wondering can those of us on the Honeycomb preview change our SDK version to 11 in the build.prop to allow us to install some of the Xoom apps? Might have issues I know but worth a shot.
I'll try it on my NC when I get home. Just curious if anyone else has tried it.
Link3737 said:
I wouldn't go as far as to say it's "powerful"
It's got the same GPU as the Moto Droid, which benchmarks just a tad bit below the Nexus One. Considering the Nexus One is significantly below the Galaxy S/Tegra 2 phones, we're basically at the low end of the GPU spectrum.
Which isn't too bad considering this is an E-reader
Click to expand...
Click to collapse
It's run every game I've thrown at it (other than ones with compatibility issues, e.g. Mystique). I'm sure there will eventually be apps it's not powerful enough to run but I don't think there's any currently.
I have the apk i can shoot someone to mirror
Post Removed.
Any chance you can email it to me? I'd like to try it out also....
dan
at
lantzer
dot
org
Thanks!
I have a modified HC sdk image that it shows up as a XOOM to Google. It's more than just a simple fingerprint change but nothing too complicated either. I actually have a Market ID too so I can see my NC's HC device when logged into the web based market. I also modified things so that it appears to apps that I've API level 11 installed since that's why the Google Body app was failing to install (parsing error). So now it installed and I've got the Google Body app icon showing in my launcher. However, it just force closes when run. I'm think it's the difference in the APIs, etc between the SDK preview and the final build that might be holding it back. Perhaps updating some of the "Lib SOs" would improve things, I don't know. If not that, then it's might be because it only supports the Tegra platform. In that case, it's probably hopeless unless Google to expand on that?
epakrat75 said:
I have a modified HC sdk image that it shows up as a XOOM to Google. It's more than just a simple fingerprint change but nothing too complicated either. I actually have a Market ID too so I can see my NC's HC device when logged into the web based market. I also modified things so that it appears to apps that I've API level 11 installed since that's why the Google Body app was failing to install (parsing error). So now it installed and I've got the Google Body app icon showing in my launcher. However, it just force closes when run. I'm think it's the difference in the APIs, etc between the SDK preview and the final build that might be holding it back. Perhaps updating some of the "Lib SOs" would improve things, I don't know. If not that, then it's might be because it only supports the Tegra platform. In that case, it's probably hopeless unless Google to expand on that?
Click to expand...
Click to collapse
Can you please post the details of what you did for other changes to your NC, besides the fingerprint. I downloaded the 'build.prop' for the Xoom already, but only changed a couple of lines in my NC's .prop file. However, I do not see Google Body in the Market.
I would like to get my NC to look as much like a Honeycomb device as possible.
Thanks!
360Razir said:
However, I do not see Google Body in the Market.
Click to expand...
Click to collapse
Sorry, I wasn't clear. Google Body still doesn't show. I expect that's because the Market may be looking at the fact the NC's build.prop doesn't say "Tegra" like the XOOM does. Can't change this since the device won't boot that way. However, pushing the APK via ADB worked. It previously failed to even do that with the stock HC v4. If it would help several others out, perhaps I should create a new thread offering a mod, etc to automate some of the changes since I had to do more than the modify build.prop itself. There will likely still be some manual steps and the patch will require working adb (even though many commands already run automatically).
epakrat75 said:
Sorry, I wasn't clear. Google Body still doesn't show. I expect that's because the Market may be looking at the fact the NC's build.prop doesn't say "Tegra" like the XOOM does. Can't change this since the device won't boot that way. However, pushing the APK via ADB worked. It previously failed to even do that with the stock HC v4. If it would help several others out, perhaps I should create a new thread offering a mod, etc to automate some of the changes since I had to do more than the modify build.prop itself. There will likely still be some manual steps and the patch will require working adb (even though many commands already run automatically).
Click to expand...
Click to collapse
can you post what steps you did? doesn't have to be automated, but I would like to know how to get google body on my NC, right now i'm running Honeycomb off of the SD card.
Also for people wanting the link to google body, tinpusher posted a link here http://forum.xda-developers.com/showpost.php?p=11788921&postcount=50
it's multiupload.com/PFJZDK11I0
we need real sdk level 11, with the honeycomb APIs either from aosp, the final SDK, or reversed engineered from the xoom.
Sent from my Nexus One using XDA App
hey guys... ok im a complete noob and have no idea what all this Xoom and Honeycomb and bla bla is... bottom line tho is i was wondering if there is anyway to run google body on my Galaxy S... Currently im running darkys v9.2...
any light on the topic will be highly appreciated as i really need such an app professionally...
thanks!
Any progress on this? Not being able to run Google Body is the one thing holding me back from purchasing a Nook Color.
Related
weibo.com/chomper
t.cn/aDdv3E
Getting closer...
Looks okay , But was hoping for more a Honeycomb GUI , as ive just got rid of a 2.3 Tablet to get the HP touch pad to flash to 3.0 but will 3.0 ever happen for the Touch pad ?
The general consensus seems to be that HC will not appear on the TP; as the source code was never released by Google.
What is more likely to happen is that 2.3.5 will be on the initial CM release for the Pad; with ICS being the next logical step, once it's released.
I may be wrong,
But I believe that is the long and short of it.
Hope this helps.
ugh! I would settle for 1.6 just so it is not the ugly webOS cripple.
I actually kind of like WebOS.
The not-having-multiple-screens-to-swipe-left-or-right thing takese a bit of getting used to (I'm not sued to it yet).
But I do like bouncing apps away, to close them.
That being said,
I definitely favor Android over all other O/S.
kienz said:
i actually kind of like webos.
The not-having-multiple-screens-to-swipe-left-or-right thing takese a bit of getting used to (i'm not sued to it yet).
But i do like bouncing apps away, to close them.
That being said,
i definitely favor android over all other o/s.
Click to expand...
Click to collapse
weeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee!!!
the fact that it boots properly and shuts down will tie me over until cm7 comes out. even though i cant really do much on this. lol
thanks to OP for finding this, and to the chinese dudes who created this.
Silver_172 said:
Looks okay , But was hoping for more a Honeycomb GUI , as ive just got rid of a 2.3 Tablet to get the HP touch pad to flash to 3.0 but will 3.0 ever happen for the Touch pad ?
Click to expand...
Click to collapse
Nope
..
But 4.0 will!!
I tried it, very buggy but does not affect your system so feel free to play
Sent from my Nexus S 4G using xda premium
I am really hoping this progresses fast and works well. I actually enjoy webOS card system but the lack of apps is disappointing. I would much rather be able to run android on a card.
Either way though, I plan on installing android whether it's dual boot or via card.
goTouchGo said:
weibo.com/chomper
t.cn/aDdv3E
Click to expand...
Click to collapse
The preware twitter feed, states that this app installs another kernel and that the un-instal option doesn't remove it.
Be warned!
Fon22
I installed it and it works fine (for what works at least). Anyone know how to actually install another app into it? I downloaded an APK and put it in the apks folder (in webOS) but I don't know where to look for it within chroid. Is this even possible? The guide says you can do it.
Fon22 said:
The preware twitter feed, states that this app installs another kernel and that the un-instal option doesn't remove it.
Be warned!
Fon22
Click to expand...
Click to collapse
Edit: I just checked back in WebOS and Govnah doesn't show the overclock kernal. Uninstal/Reinstall the stock or overclock kernals doesn't change it. Max Freq. is 1.2 ghz ... uh oh
mountaindewmi said:
I installed it and it works fine (for what works at least). Anyone know how to actually install another app into it? I downloaded an APK and put it in the apks folder (in webOS) but I don't know where to look for it within chroid. Is this even possible? The guide says you can do it.
Edit: I just checked back in WebOS and Govnah doesn't show the overclock kernal. Uninstal/Reinstall the stock or overclock kernals doesn't change it. Max Freq. is 1.2 ghz ... uh oh
Click to expand...
Click to collapse
if you want to O/C again, you have to doctor 3.0.2 back on, then redo the preware etc.
as for the apps, put them in that folder and they will auto install, thats what i did, and got titanium installed (even tho its useless/keeps crashing, i had it available)
3.0.3
Sent from my Nexus S 4G using xda premium
ghostzyden said:
When you install chroid, don't go into govnah while its installed, when you uninstall chroid, you should be fine and not have to worry. That way you wont have to doctor all the time
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
wow, thanks for quoting me almost line for line from the other thread :/
i figured this out last night after many hours of testing
http://forum.xda-developers.com/showpost.php?p=18270362&postcount=127
Solidus_n313 said:
wow, thanks for quoting me almost line for line from the other thread :/
i figured this out last night after many hours of testing
http://forum.xda-developers.com/showpost.php?p=18270362&postcount=127
Click to expand...
Click to collapse
My apologies, just trying to help get the word out. I know you spent time on figuring out and did not know if you would post it here. I saw people didn't know, so I thought I'd help. Again, my apologies.
Sent from my Nexus S 4G using xda premium
Hi, didn't want to clutter the "bad news" thread nontechnical noob questions. If the tablet won't boot from SD
1) Will it still possibly be rootable where I could side load apps? I could live with the stock ROM if I could sideload apks, maybe.
2) Am I right to assume even if it is rootable where I can add apps, it is much more likely that I could brick it somehow?
Dang, just really crappy timing. I actually bought gift cards to get it (so I could get some cash-back deals). I can't return the cards. I guess if this thing isn't worth it, I can use them to get a refurb color.
Very surprised and disappointed they went this route (if they really did).
Damn
Same here, I could live with side-loading. But I think it's a bit early to write off bootable SD. Hopefully it's here relatively soon as I'd like to leave the stock experience in place for family members.
As an aside, I've got the original Nook Color (rooted of course), as well as the Transformer. Even without the benefit of ICS, I found that I still resorted to grabbing the NC for my bedtime reading (Google Reader and articles in RIL, rather than actual books). 7" is perfect, 10" a bit unwieldy for me.
I picked up the NT today and am very happy I did. It's a nail in the coffin for the Transformer, gonna sell it as the NT will meet all my needs. I'm saying this based on the stock experience with the expectation that we'll have ROMs at some point.
But soon enough we'll have a) root and b) ICS on the NT. It's gonna be sweet!
Well, correct me if I'm wrong, but I'm yet to see an Android device that XDA geniouses couldn't root.
Including the crazy-ass encrypted Craporola devices.
Rooting might be doable, but if the bootloader is encrypted, then installing a custom ROM like CM7 might be out of the question.
Case and point: look at how much agony the owner of the Motorola Milestone (the GSM version of the Droid) went through. Far as i know, they just got the official Froyo ROM within last few month, and most likely won't get GB, ever.
DarkDvr said:
Well, correct me if I'm wrong, but I'm yet to see an Android device that XDA geniouses couldn't root.
Including the crazy-ass encrypted Craporola devices.
Click to expand...
Click to collapse
Yeah i figured as much but wasn't sure if there was something out there I wasn't aware of. I'm using an Atrix. Despite Motorola's best efforts, the community eventually got into this thing.
gordon1hd1 said:
Rooting might be doable, but if the bootloader is encrypted, then installing a custom ROM like CM7 might be out of the question.
Case and point: look at how much agony the owner of the Motorola Milestone (the GSM version of the Droid) went through. Far as i know, they just got the official Froyo ROM within last few month, and most likely won't get GB, ever.
Click to expand...
Click to collapse
That would suck but I think I could live with it. I just noticed that some of the nook apps are the tablet version rather than the phone versions. Evernote and Netflix, for example. Root and sideloading would probably suffice, although B&N would lose some goodwill.
Sent from my MB860 using XDA Premium App
I could honestly care less about custom roms or anything like that. I'm fine with the NT stock experience.
But sideloading would be a very very good thing, just so I can get the few apps I'd like to use onto the thing. I'm only gonna use it to consume media- but I'd like to decide which apps I use to do that.
Rooting will get most users far, but compare to a full blown CM7 rom, there still many short coming with just root.
Example:
1. Tablet soft buttons, the CM7 tablet soft key are vital in making a lot of side loaded application work in NC.
2. Custom keyboard. one of my favorite app on NC is the thumb keyboard, which make typing on the NC in landscape orientation feel natural. With Root, the user can install the keyboard, but won't be able to enable the keyboard, since B&N remove some of the menus settings.
3. Honeycomb and ICS, with the source code for ICS just came out, CM9 is on the horizon, without unlocking the bootloader, NT won't get a taste of either.
So Root is a great start, but for many android hackers and purist, it is not enough.
1. Tablet soft buttons, the CM7 tablet soft key are vital in making a lot of side loaded application work in NC.
I have button savior on my manually rooted NC. Works fine. Am I missing something?
2. Custom keyboard. one of my favorite app on NC is the thumb keyboard, which make typing on the NC in landscape orientation feel natural. With Root, the user can install the keyboard, but won't be able to enable the keyboard, since B&N remove some of the menus settings.
I got the Palm input keyboard working on my rooted NC. Worked great. I forget what I swapped it out for, but it wasn't a problem - you just have to tell the device that your preferred keyboard just happens to be named the same as its preferred keyboard and lives in the same place.
3. Honeycomb and ICS, with the source code for ICS just came out, CM9 is on the horizon, without unlocking the bootloader, NT won't get a taste of either.
This may be for the best.
I'm looking at Honeycomb now on a 10 incher, and I'm not as happy with what I'm seeing as I'd hoped. ADB is more challenging, and putting files on the device via mass storage device is right out, which means a lot of my tools for managing content on it are gone, too - manually copy over stuff that Calibre used to just take care of? Bleargh.
Honeycomb pretty much requires your real, fast computer talk to your honeycomb device, aka a ****ty slow computer, over a serial link as if it were a peer, rather than just being able to get the storage and write files to it.
And if you use linux, your good, fast computer can't even talk to the ****ty, slow one that google's deliivered because they didn't bothered to warn anyone about this far enough ahead of time for the linux folks to really get working on trying to port over that stupid set of media player commands. Who knew that anyone would all of a sudden decide they were going to pronounce a brain-dead media player communications interface as workable?
Once you unplug and being passively consuming your pr0n again, the tablet's all good and pretty.
http://soledadpenades.com/2011/06/12/honeycomb-mtp-and-linux/
Not to second guess anyone here, but there always OTHER ways of doing things. Witness the Droid X where even with an encrypted bootloader an exploit was found called 2nd Init (http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works) which allowed the Droid X to get custom roms (albeit with the stock kernel) such as CM7 and MIUI.
jhanford said:
Not to second guess anyone here, but there always OTHER ways of doing things. Witness the Droid X where even with an encrypted bootloader an exploit was found called 2nd Init (http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works) which allowed the Droid X to get custom roms (albeit with the stock kernel) such as CM7 and MIUI.
Click to expand...
Click to collapse
I truly hope that it won't be such an involved process for us, but still... very cool to read what the genius devs put together as a workaround on other devices. We just need to hope that they jump on the Nook Tablet like they did the NC.
jhanford said:
Not to second guess anyone here, but there always OTHER ways of doing things. Witness the Droid X where even with an encrypted bootloader an exploit was found called 2nd Init (http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works) which allowed the Droid X to get custom roms (albeit with the stock kernel) such as CM7 and MIUI.
Click to expand...
Click to collapse
I have a Defy, and it need too 2ndInit to start custom rom like CM7/MIUI.
I hope that NT will be no boot-locked, but if it's the sadly truth I think that port 2ndInit will be not too much hard.
well we already figured out how to side load apps. they dont pop up in NT's GUI, but with 2 buttons you can launch Go Launcher and within there you can see everything you installed.
I would actual prefer to have the stock Rom, just rooted. I had CM 7.1 on my NC but removed it because I actually do use the NC as bookreader and that would the primary use for a NT. I have a TF and soon a TF Prime for the full tablet experience, which IMHO really needs a 10 inch or bigger screen.
anyone else here notice a lag in the keyboard typing especially on browser, say like replying in a forum...plus the accuracy does not seem to be very good.
Same here! It was fine for a while after I disabled the ripple effect. But starts slowing down again. Its one of the main reasons I keep getting back to android. WebOS has nice interface.
Sent from my Touchpad using XDA Premium App
Yea but until wifi issues are fixed (unless I didn't read enough) on cm7 I may hold off bbefore putting android on it. Web os is sweet but its plain left out when it comes to apps. I feel ripped off actually lol.
There's an android app called sign my pad its awesome and may be what my wife needs for her work.
Sent from my SGH-T989 using XDA App
tackleberry said:
Yea but until wifi issues are fixed (unless I didn't read enough) on cm7 I may hold off bbefore putting android on it. Web os is sweet but its plain left out when it comes to apps. I feel ripped off actually lol.
There's an android app called sign my pad its awesome and may be what my wife needs for her work.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Wi fi is not perfect on cm7 but is working well enough to not have to use web os. You are missing out since Android is working great even in an alpha stage. There is no reason to not give it a try since there is no risk in doing so.
HTC Vision(G2)/meXdroidmod
Ghost Chili AIO
No problems on WebOS keyboard; I kind of like it better than the stock android keyboards.
As for CM7 Android, it's definitely still an alpha product; it is great if you don't have any problems, but if you do, you are just out of luck. I had no problems with Alpha 2 with Xron's great package 1.37, but alpha 3 with Xron's 3.3 package gives me wifi nightmares. I've seen a few posts with problems like mine - the wifi has to be re-enabled after every boot - also, my wifi drops the connection after 3 or 4 minutes. Kills me because otherwise it is so great. I'd recommend trying it - maybe you'll be like most people and won't have any of the wifi problems.
iirc the breif reading i did so far its a dual boot? so i dont really lose webos at all and can boot into either OS?
tackleberry said:
iirc the breif reading i did so far its a dual boot? so i dont really lose webos at all and can boot into either OS?
Click to expand...
Click to collapse
Correct. You do not lose web os if you install cm7. That is the beauty of the touchpad. Two operating systems available in one tablet. You have a choice on which to use on demand.
Sent from my Touchpad using xda premium
One of the things I like about the webOS keyboard is the accuracy of it, but there is indeed some lag when typing in some forms.
Also, Shift + Enter actually works on the webOS keyboard unlike all Android soft keyboards it's useful for the facebook site or entering a new line
And the webOS browser renders full pages better than most Android browsers as well
I've noticed that android keyboard works ligtyears better for me and typing and zero lag.
Typing seems good for me on WebOS. Sometimes taps seem a little off, but I'm not sure if it's me or not. Anywho, you may want to check out some of the patches in preware. There are some to address scrolling speed and you can disable the ripple effect on clicks.
Personally, I really like WebOS and haven't bothered with the CM7 alpha's yet (I do have two other Android devices in the house though -- one a Nook running CM7, so I know what's out there).
Is anyone working on a way to remove WebOS completely from our devices? I mean for those of us who have no desire to retain any part of the system, nor use it ever. It seems like an awful waste of space.
Sent from my cm_tenderloin
unsivil_audio said:
Is anyone working on a way to remove WebOS completely from our devices? I mean for those of us who have no desire to retain any part of the system, nor use it ever. It seems like an awful waste of space.
Sent from my cm_tenderloin
Click to expand...
Click to collapse
I think this will be done once we have a very stable port of android running.
Right now webos isn't taking up that much space and its nice to have a backup just in case. I'm with you though in wanting to eventually remove it completely.
Sent from my SPH-D700 using XDA App
muyoso said:
I think this will be done once we have a very stable port of android running.
Right now webos isn't taking up that much space and its nice to have a backup just in case. I'm with you though in wanting to eventually remove it completely.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I believe it needs to be there for Android to work. Plus a lot of people like it including dalingrin
Sent from my HTC Desire Saga using xda premium
I believe dalingrin stated in one of the earlier release notes for one of the alphas that he does not plan on finding a way to remove webos entirely (He likes it, and it can serve as a backup in case android turns to poo). But who knows, maybe some dev will find a way, only time will tell
Sent from my SCH-I500 using XDA App
I would prefer to have it as well. Just want to play with open source webOS.
Sent from HP Touch pad ICS alpha 0.6
I just see no point in keeping it. I haven't used it since I got cm9 on my TP. Also it would be nice to only boot into moboot with a button combination, like recovery on other devices.
Sent from my cm_tenderloin
I have a few questions.
What are you putting on your touchpad that those ~2 GB are such a big deal? Also, if space was a concern why didn't you buy a 32GB model. I have 8 of the 10.5 storage available, and 1.1 of the system 1.5 free. I have all the apps I could want. Until last week there was no point putting movies on there, but now Netflix works I don't see a point anyway.
You can change the moboot delay to 1 sec (changing the delay to 0 will remove the auto boot, it just sits at moboot). Is a 5 second delay really such a big inconvenience every time you power cycle the device? How often are you power cycling the device anyway? At my check before I installed alpha 2 I had over a week of up time. I see no need to reboot the device unless I am flashing something.
While I almost never boot into webOS since CM9, I still see the value in a back up OS. And webOS is an elegant, smooth, intuitive experience. It would be one thing if CM7 was the back up, then i would be all over removing it. Yeah, the webOS app selection is bad, but so is tablet optimized android app selection. A solid web browser is 80%+ of my use on the TP. webOS had better browsers than gingerbread.
I just don't see the point of a new "how do I remove webOS?" thread every two weeks. Especially when the resounding response is generally "why?"
Sent from my Galaxy S II (i777)
I have a 32gb version, and with no expandable storage every gig on that thing is precious. IDK about you, but I have wayyyyy more than 32gb of music. Also as long as we have an ability to boot into clockworkmod, there is absolutely no reason to retain a "backup" os as you call it. As for power cycling my device, it just depends on whether or not I want to save battery; or if I encounter a bug (like touchscreen unresponsiveness or SOD).
IDK why, but to me this seems like it should be a trivial task to streamline this into a full fledged android device at this point. Also, I wasn't aware there were any threads about how to remove WebOS, I looked at the main page and expected to find one but didn't. Ergo, this thread.
Not trying to be rude-
I was forced to see this thread when I tried to open a new thread titled "Remove webOS":
http://forum.xda-developers.com/showthread.php?t=1453930
A search for "Remove webOS" also found that thread in the general section and the following in just the first page of results on the Q&A forum:
http://forum.xda-developers.com/showthread.php?t=1461517&highlight=remove+webos
http://forum.xda-developers.com/showthread.php?t=1490575&highlight=remove+webos
I found those with less than 5 minutes of searching on xda.
A google search returned this as the first result (searched "remove webos"):
http://rootzwiki.com/topic/8571-anyway-to-remove-webos/
Again, I know this sounds condescending, but it's frustrating to see this question constantly. Maybe it's because on the Galaxy S II forum we are flooding with the same questions at least weekly; "How do I install an i9100 ROM?", "Where is ICS?", "I installed a i9100 ROM without reading the instructions, my phone is acting weird".
You weren't the first to ask this question, and you won't be the last to ask it. I bet we'll see another thread before February is over. Outside of the threads dedicated solely to this question there has been a lot of discussion of this topic. On twitter, Rootzwiki, and here on xda. There is more to it than just a penchant for webOS. I am fairly certain the android system could not function without some of the webOS architecture or files. I cannot find where I saw that off hand, but I am pretty sure that currently it's not possible, even if some of the devs wanted to do it. I didn't respond with this the first time, because I could not find the source.
I also have much more than 32GB of music. But with Google Music, Pandora, Slacker, and other similar apps I don't see the need to put music on my device. If you played all your music non-stop how long would it run before repeating? Days? I only have 500MB on my phone because there is no need for an artist discography when I only want 3 of their songs.
CWM is not a backup OS. It's a utility. Yes, i have never borked CWM, but if you have too many moboot entries how can you fix that from CWM? You can't. You have to either be in webOS or Android. When switching from one ROM to another often both entries are there, and for me more often than not neither will boot. I just get boot failures. Without webOS I would have to use webOS doctor to completely wipe the device and start over, and reinstall android completly fresh. This happened to me at least 5 times in the past two months.
I posted from the android app, you don't see suggestions of similar threads.
Sent from my cm_tenderloin
unsivil_audio said:
I posted from the android app, you don't see suggestions of similar threads.
Sent from my cm_tenderloin
Click to expand...
Click to collapse
That brings up an interesting point. How did you get the xda app to run on the touchpad? Are you using tapatalk? I could not get the xda app to run on any CM7 or CM9 variant. Judging by the market comments the xda app doesnt run on any tablets, even legit ones.
Personally for that reason I don't think the mobile app should have the ability to create threads. Also the search function on the app is beyond useless.
Sent from my Galaxy S II (i777)
I've just been restoring it with titanium. As you can see it works fine on my nook color with ICS as well. ---v
Sent from my NookColor
https://wiki.ubuntu.com/Touch/Porting
Any Devs wanna start? I don't have the experience to even know where to begin
I hope someone does try, this could be really cool.
I can probably make this work, considering it's based of CyanogenMod 10.1. Now I just need to hope repo sync works with this, because it always breaks in the middle when I try to sync with paranoid 3.
I'm not at a computer right now, but I will let you know how it goes once I can get on one.
Sent from my NookColor using xda app-developers app
thejrcrafter2 said:
I can probably make this work, considering it's based of CyanogenMod 10.1. Now I just need to hope repo sync works with this, because it always breaks in the middle when I try to sync with paranoid 3.
I'm not at a computer right now, but I will let you know how it goes once I can get on one.
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
They have a switch to continue if failed in the middle.
Downloading repo now.
You guys probably know this...but just in case.
I installed this on my Nexus 7 yesterday. There are no apps, just screenshots of what the apps will be when they are ready. You can supposedly still make phone calls but that won't matter here. The UI was beautiful (I thought) but that is all they have done at this point.
Just saying, it is not even close to functioning as even a media device. I actually couldn't even get wireless up, although I think that is technically supposed to work. I never used it, but I would expect the NookBuntu to be way more functional at this point.
Not to rain on anyone's parade, porting new OS is a great way to learn new things, no matter your skill level. But don't expect much return on your investment at this point.
(Also, just because, make sure that there is a kernel and ramdisk and uboot and not a boot.img in whatever you build. The device tree should take care of that for you, but it didn't on AOSP for me, and I suffered as a result.)
mateorod said:
You guys probably know this...but just in case.
I installed this on my Nexus 7 yesterday. There are no apps, just screenshots of what the apps will be when they are ready. You can supposedly still make phone calls but that won't matter here. The UI was beautiful (I thought) but that is all they have done at this point.
Just saying, it is not even close to functioning as even a media device. I actually couldn't even get wireless up, although I think that is technically supposed to work. I never used it, but I would expect the NookBuntu to be way more functional at this point.
Not to rain on anyone's parade, porting new OS is a great way to learn new things, no matter your skill level. But don't expect much return on your investment at this point.
(Also, just because, make sure that there is a kernel and ramdisk and uboot and not a boot.img in whatever you build. The device tree should take care of that for you, but it didn't on AOSP for me, and I suffered as a result.)
Click to expand...
Click to collapse
What are the app extentions?
Gonna see what I can do to get it running anyway, since I have the entire repo.
moocow1452 said:
Gonna see what I can do to get it running anyway, since I have the entire repo.
Click to expand...
Click to collapse
That's awesome Moocow, let me know if you need any help testing.
I'm not terribly educated in the art of Android OS compiling, but if there's anything I can do to help, let me know.
tsukisan said:
That's awesome Moocow, let me know if you need any help testing.
I'm not terribly educated in the art of Android OS compiling, but if there's anything I can do to help, let me know.
Click to expand...
Click to collapse
And now I got to finish it, don't I? Get into XDA's Ubuntu Touch section, and start rooting around for porting tools, walkthroughs, and whatnot and we'll compare notes if one of us finds something the other doesn't.
I worked on building the phablet for the nook. I stopped because all reports were it works very badly with only 500 mb ram. Hashcode has ported it to the kindle fire and found he could only open a couple apps before it froze up. However, he did good work on porting and put the changes on github at https://github.com/KFire-Android . You can look for phablet branches on the otter branches. The kernel changes are also present in some of his repos. Look around those repos for good hints on getting started.The kindle fire is also an omap processor, albeit omap4, so it is close to ours. The changes should be similar.
Good luck.
drmarble said:
I worked on building the phablet for the nook. I stopped because all reports were it works very badly with only 500 mb ram. Hashcode has ported it to the kindle fire and found he could only open a couple apps before it froze up. However, he did good work on porting and put the changes on github at https://github.com/KFire-Android . You can look for phablet branches on the otter branches. The kernel changes are also present in some of his repos. Look around those repos for good hints on getting started.The kindle fire is also an omap processor, albeit omap4, so it is close to ours. The changes should be similar.
Good luck.
Click to expand...
Click to collapse
So the thing that's supposed to work better with lower grade hardware doesn't work better with lower grade hardware? Ain't that hysterical? :good:
It works somehow... on samsug 9003
voit said:
It works somehow... on samsug 9003
Click to expand...
Click to collapse
Well that's good. Right now, I'm trying to incorperate NookieDev source into the Manifest.xml to get it to properly build. It doesn't seem to be as easy as the fill in the blank I thought it was, but, progress is being made, I think.
Any progress on this?
Sent from my Nexus 4 using xda premium
Good news, I've gotten it to the point where I can brunch encore to try and make a new build.
Bad news, Brunch chokes up on mkimage, for reasons unknown to me. Seems like a problem for building an Android like image, but it escaped me thus far, and the irc on freenode is... of varying quality help to say the least.
Code:
make: *** No rule to make target `/home/user/Nook/out/host/linux-x86/bin/mkimage', needed by `/home/user/Nook/out/target/product/encore/ramdisk.ub'. Stop.
make: *** Waiting for unfinished jobs....
EDIT: Just figured out that I needed to patch the main.mk in build/core to specify a mkimage, now the compiler seems to be churning. Will update once something happens.
Well, it's something.
Anyway, have not had a chance to test this out on my own Nook yet, since it picked an excellent time to flake out on me. You do need to backup and completely wipe the device, assuming it even installs. (Did not work on just a Data/Cache wipe, anyway, and I need to recover my Nook after wiping emmc along with everything else, whoops.)
Anyway, it's like radioactive juice at this point, might kill your Nook, give it superpowers, or not really much of anything. YMMV.
https://docs.google.com/file/d/0B0iHVj8OqCAmMmhvMTY2d2cwbFk/edit
EDIT: It does install, but power on goes from Cyanoboot -> Backlight on -> Backlight off -> Device Off within a couple seconds, so more work is required. le sigh
EDIT2: Turns out that was because I only had the bootstrap on the device, no phablet-flash-preinstall that actually makes it work. :silly:
With both of them flashed, I get to Cyanoboot -> persistent black screen until I cut power. Common error, so I've heard and adb works, so there may be hope yet.
Ladies and Gentlemen, Children of All Ages. I give you Ubuntu Touch for the Nook Color!!
Conditionals:
1. I had to flash my homemade bootloader first (https://www.dropbox.com/s/q5g7mnadvkdmy8k/cm-10.1-20130511-UNOFFICIAL-encore.zip), then the Mobile World Congress Build of Ubuntu Touch. http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/ (quantal-preinstalled-phablet-armhf.zip)
2. Rotation is mismatched, so that it cannot recognize that it's trying to use the portrait setup in landscape, should be an easy enough fix. Jossed, as this is the MWC build, it's not really built for tablets, and the Nook gets confused on how to display thing
3. The big one. TOUCH SCREEN IS BROKEN. Granted, it makes it more of a clock than anything useful, but Ubuntu has been built and runs on the Nook Color. Built a new bootstrap based on CM 10.1 RC2, works like a glove. Still not all that much more useful compared to a clock, but that's by design.
Super duper special thanks for the guys in the Ubuntu-Touch mailing list and irc.freenode.net #ubuntu-touch and #nookcolor, who I could not have done this without.
moocow1452 said:
Ladies and Gentlemen, Children of All Ages. I give you Ubuntu Touch for the Nook Color!!
Conditionals:
1. I had to flash my homemade bootloader first (https://www.dropbox.com/s/eaxcz91x7rm36tg/cm-10.1-20130508-UNOFFICIAL-encore.zip), then the Mobile World Congress Build of Ubuntu Touch. http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/ (quantal-preinstalled-phablet-armhf.zip)
2. Rotation is mismatched, so that it cannot recognize that it's trying to use the portrait setup in landscape, should be an easy enough fix.
3. The big one. TOUCH SCREEN IS BROKEN. Granted, it makes it more of a clock than anything useful, but Ubuntu has been built and runs on the Nook Color.
So, what next?
Click to expand...
Click to collapse
Looks cool. What's next? fixing touchscreen and fix rotation.. the rotation bit, depending on what the issue is, might be fixed by a change to the kernel config or drivers-- see https://github.com/NookieDevs/andro...mmit/7894401f916eb90b08f113a0cedf4f4d12a1ed77 and https://github.com/NookieDevs/andro...mmit/297a7593c56a75691eb7a7ea4aabab4a052273c3
that's a kernel config flag sluo added. You can also play with the peripheral board file for more control... https://github.com/NookieDevs/andro...rch/arm/mach-omap2/board-encore-peripherals.c
Sweet Tiitties!
Sent from my NookColor using xda app-developers app
AgentCherryColla said:
Sweet Tiitties!
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
Indeed. Especially now that with the latest get of CM for Encore, I got touch screen working for the MWC demo. (Somehow) Turns out that rotation isn't so much the issue as is resolution, everything being too big to properly fit on the Nook Screen, and it looking more like a phone than anything, but it effing works like the half assed demo it's supposed to be.
https://www.dropbox.com/s/q5g7mnadvkdmy8k/cm-10.1-20130511-UNOFFICIAL-encore.zip
EDIT: Do any of you guys want me to do a write up or a Youtube video on how to patch and build your own version of encore for your Nook machine?