As a curious fellow I decided to edit my build.prop to look like the honeycomb build.prop and it works!!
I went to the market and many xoom apps showed up, I downloaded quite a few and some actually work and I am please to have a few more apps to test. my new favorite are djstudio and mango.
What changes did you make?
Everything above # ro build. . . .
Elaborate please
someone with the xoom system dump (which has been put on the naughty list, can't post it) needs to post the build.prop
This could be bull****, as the Xoom uses a completely different market client.
So....
Post the changes!! Let us try and decide if it works..
When the xoom system dump was leaked moto sent out cease and desist letters to xda, consequently all of it was pulled. If you search though yo will be able to find the build.prop in the xoom dev sub forum.
manikin13 said:
When the xoom system dump was leaked moto sent out cease and desist letters to xda, consequently all of it was pulled. If you search though yo will be able to find the build.prop in the xoom dev sub forum.
Click to expand...
Click to collapse
Thanks.
Did not realize that....
Moved to general.
I wonder if this would versus the mahimahi stuff we currently use. I'll make a mental note.....
Btw, motodev already offers a full HRI39 (orginal Xoom firmware) system.img for free - you just need to sign up. I don't think they're are fanatical about their firmware anymore.
Forgive me for being ignorant, but I thought android is under the gnu license, which can't be withheld from the public. How is moto able to do this?
I'll post the build.prop in about 2 minutes....
http://home.comcast.net/~ibladesi/build-Xoom-3.01.prop
Lets hope a 3.01 build.prop doesn't screw with things.
Yep. 14 minutes is what I meant.
goodintentions said:
Forgive me for being ignorant, but I thought android is under the gnu license, which can't be withheld from the public. How is moto able to do this?
Click to expand...
Click to collapse
How are they able to lock bootloaders and release half baked (send it back to us and we'll add that later, we're tired) devices. Because they're ****s. They also claim their garbage in the system/app folder is worth something .. it's not exactly like an AOSP build.
BilliamB said:
Everything above # ro build. . . .
Click to expand...
Click to collapse
Did you also change the fingerprint? Or just everything above # ro build?
I guess the other question is -- does anything go missing after this change? I already have mahimahi and phone alterations in things like TNT Lite, so altering it further is not a big deal to me. Just want to make sure we don't lose anything in the process.
Nothing appears to be missing from the market. I search 'tegra' and 'xoom' and 'HD' and find lots of software. Google Body downloads, installs, rotates the body and size adjusts the body okay but FC's when trying to go inside the body. I figure it has to with google fragments??
see post #3
Forgive me lack of knowledge, but what does this all mean? Is someone going to be able to port H0n3yc0mb to the G-tab now? I'm trying (really) to not get my hopes up.
lostpilot28 said:
Forgive me lack of knowledge, but what does this all mean? Is someone going to be able to port H0n3yc0mb to the G-tab now? I'm trying (really) to not get my hopes up.
Click to expand...
Click to collapse
Sorry no HC rom just the ability to sample HC ready apps.
Related
Ok, it's my first Droid phone, so these questions are going to seem incredibly stupid, but I'm just not sure what some of these acronyms mean:
RUU
AOSP
WIP
DeOdexed
And if the acronym isn't self-explanatory, a bit of explanation as to what these things are would be appreciated.
I'd like to be able to start contributing from time to time around here, but I often get stumped halfway through a thread trying to figure out what the hell someone's talking about.
James.Q.Campbell said:
Ok, it's my first Droid phone, so these questions are going to seem incredibly stupid, but I'm just not sure what some of these acronyms mean:
RUU
AOSP
WIP
DeOdexed
And if the acronym isn't self-explanatory, a bit of explanation as to what these things are would be appreciated.
I'd like to be able to start contributing from time to time around here, but I often get stumped halfway through a thread trying to figure out what the hell someone's talking about.
Click to expand...
Click to collapse
RUU = Rom Update Utility (ones posted here are usually from the manufacturer to restore your phone in case you mess up)
AOSP = Android Open Source Project (here that usually refers to a ROM that's pure android)
WIP = Work In Progress (usually a ROM or app that's not considered stable yet)
Deodexed = (not sure what it stands for but I know a ROM can be odex which can't be themed and deodexed that can be themed)
Sent from my PG06100
Dread 7us said:
RUU = Rom Update Utility (ones posted here are usually from the manufacturer to restore your phone in case you mess up)
AOSP = Android Open Source Project (here that usually refers to a ROM that's pure android)
WIP = Work In Progress (usually a ROM or app that's not considered stable yet)
Deodexed = (not sure what it stands for but I know a ROM can be odex which can't be themed and deodexed that can be themed)
Sent from my PG06100
Click to expand...
Click to collapse
And odex is a part of an app file that is separate from the app APK (Application installer kit, I believe, essentially is a .exe for android). Having this file allows for slightly faster boots as the boot information is stored in a separate file however it makes themeing very difficult. When a rom is DeOdexed it means the odex file has been merged with APK file hence it has been de-odexed!)
Hope that clears things up!
Ah, thanks.
Appreciate the help.
James.Q.Campbell said:
Ok, it's my first Droid phone, so these questions are going to seem incredibly stupid, but I'm just not sure what some of these acronyms mean:
Click to expand...
Click to collapse
This is your first Android phone. Not a Droid. Droid is by Verizon and is a brand not an OS.
I'm Shifting on 4G.
riggsandroid said:
This is your first Android phone. Not a Droid. Droid is by Verizon and is a brand not an OS.
I'm Shifting on 4G.
Click to expand...
Click to collapse
Was that necessary? A simple
Droid is a line of Android phones on Verizon fyi
Click to expand...
Click to collapse
Would have worked fine.
Also, Droid is not a brand its a LucasArts trademark currently being used by Motorola, HTC, and Verizon for a certain line of Android smartphones. Don't correct people when you're wrong yourself. Bro.
Haha you said bro...
Anyways droid is not being used by HTC. And you know what he means by brand. He is trying to keep you from getting abused later by telling you what is up.
Why do 80% of all forum treads have to contain some sort of cat fight?
Sent from my PG06100 using XDA App
BuddahWolf01 said:
Haha you said bro...
Anyways droid is not being used by HTC. And you know what he means by brand. He is trying to keep you from getting abused later by telling you what is up.
Why do 80% of all forum treads have to contain some sort of cat fight?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
The Droid Eris wasn't made by HTC? How about the Droid Incredible? Gosh you're right neither of those were HTC phones...oh wait, I guess they both were! Again, people really need to know their stuff before telling someone they're wrong =(
My point was that you don't need to be rude in telling someone they're wrong. I'm rude to rude people and nice to people who genuinely ask for help. Those who make assumptions and claims that are based entirely in the fiction of their minds while trying to prove other people wrong.
PS: I said 'bro' as a form of ironic mockery. Look it up sometime!
Oh and the reason "catfights" break out is because people like you two stroll in and act like a**hats!
kenvan19 said:
The Droid Eris wasn't made by HTC? How about the Droid Incredible? Gosh you're right neither of those were HTC phones...oh wait, I guess they both were! Again, people really need to know their stuff before telling someone they're wrong =(
My point was that you don't need to be rude in telling someone they're wrong. I'm rude to rude people and nice to people who genuinely ask for help. Those who make assumptions and claims that are based entirely in the fiction of their minds while trying to prove other people wrong.
PS: I said 'bro' as a form of ironic mockery. Look it up sometime!
Oh and the reason "catfights" break out is because people like you two stroll in and act like a**hats!
Click to expand...
Click to collapse
My post was not rude. While Droid is a trademark owned by Lucas Film (as anyone can see on the fine print on their commercials) it is a BRAND of phones offered by Verizon. HTC and Motorola just call their phones what Verizon wants. Just as much as the EVO is now a brand of phones for Sprint.
Every thread you have posted in has turned into a fight and your posts only look to move the topic of discussion from what the OP intended by turning it personal. Please, if you cant use the forums as intended please refrain from "contributing".
Sorry OP if you think what I wrote was "rude", just trying to help you out with learning the lingo.
You are right about HTC after all, it was pretty late and I wasn't thinking clearly when I posted that. I was just taking up for riggs because I didn't find his post rude at all. He didn't add a smiley or anything... but at most it was just "straight forward." Your post is the first post in this thread that I would consider rude bro.
And he does have a point about alot of your posts being the posts that seem to start things off in a bad direction. (cat fight)
Please keep in friendly in here. We're all just here to develop and help Thank you
Guys,
Have at it ! Here is the Xoom build.prop thanks to thefredelement... Give him a HUGE thanks for sharing this
Just download it; then extract the zip file and there you go!!!
Thanks again thefredelement !!!
Does this mean we will have honeycomb soon or do we still need the drivers from nvidia?
You still need a boot.img. Just so you know people have had access to the xoom for more than a week already and have been working on this.
Thanks, but based on the early indications this fingerprint will actually cause the market to shrink rather than expand. It is interesting to read though as it specifically states nosdcard, and does include the telephony stuff, if nothing else there is potential that once we have a honeycomb port 3G usb modem drivers may become available.
I just posted this so we could take a look at what was in it... it is a good read if nothing else ;-)
thebadfrog said:
You still need a boot.img. Just so you know people have had access to the xoom for more than a week already and have been working on this.
Click to expand...
Click to collapse
I would have thanked you but I've exceeded my max per didn't know there was a maximum. You learn something new everyday.
Anyways, it's also my understanding that to get the boot.img, the Xoom will need to be rooted. Is that correct? So, is that what we should be really looking for? Xoom has been rooted threads?
Look for "Rom based on Honeycomb". And yes it needs root. It will happen people. Posting endless honeycomb threads is not gonna make it any faster.
Ok I'm kind of a noob, please don't slam me 'frog. Since the whole purpose of Android and the whole Open Source thing is to make source available, don't either Motorola, nVidia or Google NEED to release this Honeycomb-Tegra 2 code at some point. I do realize that there may be proprietary pieces but I thought once you used open source code, you were obliged to release your resulting code to the community. Am I missing something here or is all this chatter just an attempt to get it faster?
I hate seeing all of the teaser threads as well, but I also try to keep an open mind and view it more as humorous than obnoxious. I'm sure the real dev's are quite adept at skipping and ignoring the stupid comments by people like me.
I'm just saying ...
thebadfrog said:
Look for "Rom based on Honeycomb". And yes it needs root. It will happen people. Posting endless honeycomb threads is not gonna make it any faster.
Click to expand...
Click to collapse
Lol. I shouldn't have posted the last two sentences. It's not like I was saying that I was being impatient. Just wanted to learn that's all.
I'm assuming we'll see a lot of the bits and pieces of the XOOM system posted in here and just wanted to know what's relevant or not.
Thanks again.
Its all good. I understand people wanna learn.
Yes they have to release anything that is open source but if you use linux you can use the nvidea and ati example. They don't release their proprietary libs for their cards and as a result its quite likely when you upgrade your kernel you break your video drivers. Its not so bad now but a couple years ago I couldnt keep an ati card working.
All the endless threads that are repeats make it nearly impossible for noobs to find good information and it makes it harder for me to link the correct posts for noobs to follow. Everyone was new at one time but you will never learn anything if you keep asking and not looking. This is a developer forum....xda DEVELOPERS.... not a customer service forum. Most devs here go out of their way to answer questions as do a few of us power users. My tirades are not directed at people like the 2 previous posts. Its the ones that dont want help. They want someone to hold there hand and type out each and every command for them and supply them a fix for every problem. And they want it now
sverbanic said:
Ok I'm kind of a noob, please don't slam me 'frog. Since the whole purpose of Android and the whole Open Source thing is to make source available, don't either Motorola, nVidia or Google NEED to release this Honeycomb-Tegra 2 code at some point. I do realize that there may be proprietary pieces but I thought once you used open source code, you were obliged to release your resulting code to the community. Am I missing something here or is all this chatter just an attempt to get it faster?
I hate seeing all of the teaser threads as well, but I also try to keep an open mind and view it more as humorous than obnoxious. I'm sure the real dev's are quite adept at skipping and ignoring the stupid comments by people like me.
I'm just saying ...
Click to expand...
Click to collapse
Typically one week is the lead time afforded the trail blazing device for each generation of Android, and then the plain vanilla source AOSP is posted at source.android.com (read about git first, where the kernel is posted). However none of the proprietary information in specific devices needs to be made available right away.
Will th devs that made the honeynook sdk preview be able to update that if they get a Xoom, amd in turn would that help the g tab devs?
I'm just curious about how much of a problem the fact that the XOOM has a Gig of system ram rather than 512 megs will be. I could see an easy way to protect some exclusivity under the guise of "ensuring compatibility" where one of the first boot steps is to check for enough available ram...
Good thing my Zpad has 1 gig ram then eh
boot img and tegra 2 aosp source here
http://android.modaco.com/content/advent-vega-vega-modaco-com/333138/xoom-rootboot-img/#entry1614605
I think.
Alpha06 said:
boot img and tegra 2 aosp source here
http://android.modaco.com/content/advent-vega-vega-modaco-com/333138/xoom-rootboot-img/#entry1614605
I think.
Click to expand...
Click to collapse
It's a Xoom boot.img, and the (tegra 2) kernel source for honeycomb (2.6.36).
Ok, per Engadget Xoom has been rooted... Next?
Here are the init files as well: http://forum.xda-developers.com/showpost.php?p=11615922&postcount=9
You can get a rooted boot image here: http://www.koushikdutta.com/2011/02/motorola-xoom-rooted.html
Love it when things start moving at nearly the speed of light,... uh oh, getting dizzy... frog, will you hold my hand?
MikeTheSith200 said:
Will th devs that made the honeynook sdk preview be able to update that if they get a Xoom, amd in turn would that help the g tab devs?
Click to expand...
Click to collapse
The Nook is so heavily supported because it's so god damn cheap for a tablet. (it's really an "e-reader")
there was no touch interface released with the version of honeycomb from the preview sdk.
With a real Honeycomb product (and full SDK) full development is possible.
If you wait, They will build it, we will come. =]
Moved Here
Also a notice to the Admins, Mods, and various users at this site:
My personal email address is not to be used to mock, insult, or otherwise argue points made on this forum. The comments made here, despite how offensive they may be interpreted, do not hold a serious tone. If you feel it necessary to send things to my personal address, please have spine to use your own return address. Please respect the fact that I do not invade your personal life by keeping my comments restricted to this site, and I only request I am granted the same common decency.
Wow, haven't seen you in a long time. Thank you for giving this a shot! : )
RjsShadows said:
Wow, haven't seen you in a long time. Thank you for giving this a shot! : )
Click to expand...
Click to collapse
It seems that in some alternate reality it is acceptable to assume that "in your spare time" means cancel all of your plans and get used to fluorescent lighting because daylight is just the glare on your computer screen. Either way, I am downloading some 2 gigs of random ICS stuff and finally received my replacement Macbook, so between projects I will try to get something moving on this.
You rock! Subscribing.
Right now all I have is the sdk version from RootzWiki, which appears was a post of just the modified boot. I have a few Nexus4g builds that claim to work. I have a rebuilt boot image and I am trying to pack all of it together and see what happens so I know where to start.
Sent from my ADR6400L using Tapatalk
twistedumbrella said:
Right now all I have is the sdk version from RootzWiki, which appears was a post and abandon build. I have a few Nexus4g builds that claim to work. I have a rebuilt boot image and I am trying to pack all of it together and see what happens so I know where to start.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Sick, i'm really looking forward to this. Don't overwork yourself though
twistedumbrella said:
Right now all I have is the sdk version from RootzWiki, which appears was a post and abandon build. I have a few Nexus4g builds that claim to work. I have a rebuilt boot image and I am trying to pack all of it together and see what happens so I know where to start.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
i am guessing these first ports will be very alpha due to no real software from google to work with?
Thread cleaned (and it's only a few hours old).
If you have nothing useful to say, DON'T bother posting...
the_scotsman said:
Thread cleaned (and it's only a few hours old).
If you have nothing useful to say, DON'T bother posting...
Click to expand...
Click to collapse
What did I miss? Did the angry beavers try to build another dam? I fell asleep waiting for the new mac to migrate from the old one. Now that everything is moved over I can actually load up what I have and at least move a little closer to posting actual files to play with.
Sent from my ADR6400L using Tapatalk
Real deal? Did source drop and only for you? Cause otherwise this is just another non-working SDK port.
doug piston said:
Real deal? Did source drop and only for you? Cause otherwise this is just another non-working SDK port.
Click to expand...
Click to collapse
I guess if you didn't see the previous thread, which was more or less a rick-roll youtube video that said it isn't possible to get anything running, then an understandable first reaction is to make rude comments...
But if you read the thread you are responding to, you would have seen that on the Nexus it is a working build, capable of being used as more than just a proof-of-concept. Then again, I don't expect people to read these days because they are too busy writing...
http://forum.xda-developers.com/showthread.php?t=1313337
http://forums.androidcentral.com/sprint-nexus-s-4g-rooting-roms-hacks/127806-rom-ics-sdk-port-wip.html
Best leave the developing to the developers and stop back when there is something to load up and complain about
So getting an SDK port working on a Nexus S is the same as getting it to run on the ThunderBolt?
I'm not saying it isn't possible though I highly doubt it will work. I'm saying don't call it the "Real Deal".
doug piston said:
So getting an SDK port working on a Nexus S is the same as getting it to run on the ThunderBolt?
I'm not saying it isn't possible though I highly doubt it will work. I'm saying don't call it the "Real Deal".
Click to expand...
Click to collapse
This is real ICS development, and not a prank so it is as the title says "ICS Development (Real Deal)"
And no, getting a port working on the Nexus S is not the same as getting it to work on the Thunderbolt, which is why there isn't a file in that first post yet. I think you are assuming that the only thing available is the SDK image, though, when the full system dump is out there also.
My previous statement still stands.. Why don't you go shake down some kids for their script source, and come back when there is something here to test.
thatdudebutch said:
Posting threads with no content seems ridiculous. Why not work on the port rather than type sentence after sentence of nonsense in here. Just saying.
Click to expand...
Click to collapse
You do know downloads, packing, transferring, uploading, etc do run in the background right? I remember back when threads like this rallied up support and assistance instead of whatever you call what you're doing... For the record I am waiting on a data wipe and a lot of stuff is still installing since the computer only came yesterday.
I can just toss up every little edit I test and brick phones all day long, or I can document the process and release when it hits milestones. That way I can catch input along the way and prevent a lot of wasted time.
Just swapped the boot on the posted Nexus build, changed over all the apn info, and added in all the keylayout and hardware files. Going through and finding everything that needs to be swapped for a straight port, then if it runs I will post up the progress.
Sent from my ADR6400L using Tapatalk
twistedumbrella said:
You do know downloads, packing, transferring, uploading, etc do run in the background right? I remember back when threads like this rallied up support and assistance instead of whatever you call what you're doing... For the record I am waiting on a data wipe and a lot of stuff is still installing since the computer only came yesterday.
Click to expand...
Click to collapse
Whether you get anywhere or not, good luck
Nothing wrong with doing something just for the challenge of having said you did it and the experience.
I am glad to see someone putting some real effort into getting an ICS port going. And appreciate you posting your progress here along the way. I'm interested in seeing how you get where you get.
Good Luck
As already mentioned, this thread is for relevant discussion of the upcoming port.
If you have nothing constructive to contribute then keep it to yourself.
No *****ing and whining about the probable lack of functionality, no pestering for ETA's and no petty personal playground nonsense.
No more warningsIf this goes off topic again then there will be repercussions.
conantroutman said:
As already mentioned, this thread is for relevant discussion of the upcoming port.
If you have nothing constructive to contribute then keep it to yourself.
No *****ing and whining about the probably lack of functionality, no pestering for ETA's and no petty personal playground nonsense.
No more warningsIf this goes off topic again then there will be repercussions.
Click to expand...
Click to collapse
Thanks. The good news is that I have a shopping list of what has been changed to go from sdk to working port. The bad news is that I also have a project due Thursday that I need to actually spend some time with.
For anyone with the sdk build, make sure before even trying to run it that you replace all the /system/bin files that just say toolbox with real files or set up symlinks for them. Busybox also needs to be added/replaced in /system/xbin
This will get that version to where you can run logcat and see the EGL errors, but it will also be in a condition to start tweaking files to get the touchscreen running.
Sent from my ADR6400L using Tapatalk
I can't waaaaiiiitttt!!
Take as much time as you need! Your life is more important than this.
I am uploading what I have, but not because it is a huge step forward. I fixed all the commands and added the files that should fix the touchscreen, but didn't on this device.
This is still a step forward from the base build we currently have. At least typing a command no longer results in "toolbox" being displayed instead of results. I reverted everything I tested to make sure the only test changes were absolutely necessary to provide a solid base. I will post a link as soon as it is up.
Sent from my ADR6400L using Tapatalk
This may seem like a redundant request but if you are or are GOING to be deving for this device could you post your Twitter or G+ id's here so we can follow your work?
That would be great.
+1 ...we fought for a forum...now no development...kinda disheartening.
I guess I need to get back with it now that I have kernel source...
You could follow me all you want, but you probably won't like where I'll lead. I usually don't bother with twitter, g+, facebook, or any other "social" site. (On the other hand, if you find any anti-social sites, please let me know.)
need to brainwash the tab8.9/10.1 developers to do the custom ROMs for us as well..
btw, what are we looking for in a new custom ROM?
EXT4, i think Samsung already moved to this...
Optimization
- Hardware Acceleration? Already ON by default in Honeycomb, I have done this mod and no difference at all.. it depends on the app to utilize this feature...
Theming ? Once rooted, you can modify the framework files.. should be quite easy, but abit time consuming... and requires creativity...
- Bloat removal? just ROOT and remove those excess fats..
bdigitalstudio said:
need to brainwash the tab8.9/10.1 developers to do the custom ROMs for us as well..
btw, what are we looking for in a new custom ROM?
EXT4, i think Samsung already moved to this...
Optimization
- Hardware Acceleration? Already ON by default in Honeycomb, I have done this mod and no difference at all.. it depends on the app to utilize this feature...
Theming ? Once rooted, you can modify the framework files.. should be quite easy, but abit time consuming... and requires creativity...
- Bloat removal? just ROOT and remove those excess fats..
Click to expand...
Click to collapse
My two yr old son plays fruit ninja and the calculator/calendar/etc opens. I bet a lot ofyou experience the same annoyance of the bottom bar mini apps not having the option to hide or lock on games and other apps on fullscren.
I'm not likely to be getting the device but I'm gonna stop by and help out to get things off the ground.
In terms of speed of development, keep in mind this thing "soft launched" in the US - I didn't even know until a few days ago that it was available at all. It's typical for a device to take a few weeks to get off the ground, the I777 was an unusual exception due to being 95%+ identical to the I9100 and being a majorly anticipated handset launch.
I'm going to start on something here soon, buy this will be my first developing for any device, so you prob won't want to follow anything I do, its gonna be slow and buggy
Sent from my GT-P6210 using xda premium
Bromar said:
its gonna be slow and buggy
Click to expand...
Click to collapse
Do you work for microsoft?
Ha u would think
Sent from my GT-Pd 6210 using xda premium
khel26 said:
My two yr old son plays fruit ninja and the calculator/calendar/etc opens. I bet a lot ofyou experience the same annoyance of the bottom bar mini apps not having the option to hide or lock on games and other apps on fullscren.
Click to expand...
Click to collapse
You can use "Honeybar" ROOT from the Android Market. It lets you hide the bar in Honeycomb.
https://market.android.com/details?id=com.hanhuy.android.hsbm
garyd9 said:
(On the other hand, if you find any anti-social sites, please let me know.)
Click to expand...
Click to collapse
You're already here bro.
Sent from thee Galaxy Tab +
I realize that you are trying to get all the Devs in one spot and thats a great idea in a new forum... however since nothing is being developed here (rom/kernel) Im going to have to move this to the General section.
Red5 said:
I realize that you are trying to get all the Devs in one spot and thats a great idea in a new forum... however since nothing is being developed here (rom/kernel) Im going to have to move this to the General section.
Click to expand...
Click to collapse
ugh. next thing you know, he's going to create a "Q&A" forum for us. That's when I'll start running away.
garyd9 said:
ugh. next thing you know, he's going to create a "Q&A" forum for us. That's when I'll start running away.
Click to expand...
Click to collapse
If it gets big enough then I will. The Dev thread is for development, not asking questions or asking for people to raise their hand.
Red5 said:
If it gets big enough then I will. The Dev thread is for development, not asking questions or asking for people to raise their hand.
Click to expand...
Click to collapse
umm.. but they have to raise their hand in order for you to smell their armpits. How else will you know who is a dev and who isn't? (I think I might have just insulted myself... hrmm)
I just posted this over in the 10.1 community's General section, hopefully someone can help me get started!
Maybe someone here can hep me get the ball rolling as well?
blinksilver said:
Hi all,
I just got my hands on a galaxy tab 7.0 plus and was hoping to build a rom for its community (no one has really built a rom for 7.0, its a small community and we just got CWM).
Ideally I'd like to kang together a stock Honeycomb 3.2 rom, free of touchwiz. I was hoping to port over one of the Google I/O Roms for the 10.1. I figure our devices are close enough that I can try tossing over the build props, make sure to use the boot/recovery images from the 7.0 and maybe, just maybe, get lucky. Or at least have a good start.
The problem is that I can't seem to find any of the Google I/O roms, past 3.1. Do those device not get updates? Is there another Touchwiz free rom I can start from? I remembering reading a while back that TWUX is an optional update for the 10.1. I've been looking around, but I'm have a heck of a time finding links that clearly imply I'm dling a Touchwiz free rom. Most of the just say "Stock" which is a bit ambiguous.
If someone would be kind enough to point me to an ODIN and CWM mod version of the sorta rom I'm looking for I'd be greatly appreciative(and hopefully if I can get this out the door, so will 7.0 community)
Thanks!
-B
Click to expand...
Click to collapse
Anyone got a copy of that? With a shield the app that launches when you hit the shield button I need that exact app.
Looking to try spoofing tegra in my nexus 4 to try streaming with a normal controller
Thanks!
I hope someone makes this happen, due to it streaming I can't see hardware being a limitation.
It could be like the Ouya framework though... Dependent on the actual device.
Sent from my TouchPad using xda app-developers app
I sure hope someone will be able to release the APK. I would be interested in using it on my Galaxy S3.
It's not the same as the TegraZone already on the Play store?
Furyus said:
It's not the same as the TegraZone already on the Play store?
Click to expand...
Click to collapse
No, it is not. And while I can't speak too much about it, it's not just a side-load onto any device. So don't be holding your breath about someone uploading the APK and getting all the features running this week.
right....because it sooo hard to make rudimentary changes to a launcher.
The APK is called Dashboard.apk. It resides in /system/app and can be launched as a normal app.
?? Then why did you say the opposite not 2 posts ago?
LegionTHEFecalExcretion said:
right....because it sooo hard to make rudimentary changes to a launcher.
Click to expand...
Click to collapse
Let me know when you get this working, since you love trolling. One of us has been helping everyone to the largest extent they can. The other is just demanding a bunch of stuff since he doesn't want to buy one himself.
I will personally post the full system image tonight if it isn't already uploaded by then. And you can go to town, I'm seriously curious about how much you can get working this week, since its obviously so easy.
LegionTHEFecalExcretion said:
?? Then why did you say the opposite not 2 posts ago?
Click to expand...
Click to collapse
It won't do anything. It will crash on another device.
Sent from my HTC One using XDA Premium HD app
You're the one going around posting false information. And asking for a system dump is not "demanding a bunch of stuff".
If you want to get into a pissing match about who's done more to help the XDA community, you're gonna lose. I've done alot more than post some roms for the EVO 3D. If anyone's a troll here its you.
And 20x more people have found my comments helpful. So you're still trolling. What false info have I given?
Unlike you i'm not a thanks whore, and the thanks meter wasn't even implemented when I started posting on XDA. I have released numerous firmware images and sbf files that would otherwise have not been obtainable, saving countless devices in the process(See the technician only Xoom recovery file that was the only way to restore a bricked Xoom for months after release). That's a little more important to me than some likes.
Oh and False info? You just said not a few moments ago it runs like a normal app.
Now now boys, calm down.
I must admit I am on legions side on most of his points so far. This is a community forum for the general public and what we do here is Share and Mod. I do believe "agrabren" that as you are part of the Nvidia team you don't want to see parts of your product ported and such, but the product is now in the hands of the user and so now it is up to us what we do with our purchases.
Sent from my C6603 using Tapatalk 2
LegionTHEFecalExcretion said:
Oh and False info? You just said not a few moments ago it runs like a normal app.
Click to expand...
Click to collapse
It didn't occur to me that I might need to explain that in more detail, but in hind-sight, it does need clarification. What I mean, and meant from the beginning, is that the framework doesn't issue any "magic" to launch that app. There's no special "back-door" entry into that APK which makes it work on the device, nor is the Intent anyway modified. My natural instinct is to distrust every aspect of a system app that doesn't sideload correctly. In this case, I gave extra insight into areas of attack on getting the APK to load on other devices by eliminating one method a company could use for an app that has a special method of launch (the center button on the device).
So my statement, properly clarified, is that the APK itself has nothing special about it in regards to Intent launching or its AndroidManifest.xml, but that without some efforts with other components, will not run directly on another device, especially one based on a non-Tegra device.
poo-tang said:
Now now boys, calm down.
I must admit I am on legions side on most of his points so far. This is a community forum for the general public and what we do here is Share and Mod. I do believe "agrabren" that as you are part of the Nvidia team you don't want to see parts of your product ported and such, but the product is now in the hands of the user and so now it is up to us what we do with our purchases.
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
Great, except I've actually been trying to help most people with most parts of ROM sharing and modding. I've already said that I'm going to post the OTA1 system and boot images, in their official entirety, as well as I'll probably post a rooted version as well. I've been helping people prevent bricking their devices.
If you'd rather I just go away, I'm happy to. But I wouldn't expect anyone else from NVIDIA to be reaching out to get CM10.2 up and running on this device, or to get a custom recovery up and running quickly. I've never objected to him getting the system image, I'm all for it being uploaded and even promised to do so. I'm trying to help clarify what will work easily and what won't. I even answered the question that nobody else had, the APK he's asking for (because he didn't know the name of it) is Dashboard.apk, and it resides in /system/app. His contributions right now to the SHIELD forums on XDA are: Give me the system image, give me some APKs that may be on the device! That rubs me the wrong way as a person who has spent plenty of time developing ROMs for different phones, helping fix kernels for multiple CM-supported devices, and who has *always* fought for companies to give to the community. Unlockable bootloader? Yeah, I was part of that push. I'm trying my best to get as much source as possible made public.
Maybe I came off poorly in this thread (because this was after the thread asking for an apk that has only been demoed at tradeshows and special press meetings). So I'm sorry if I came off wrong, but while everyone else is helping each other out, he's just demanding stuff.
I what world do you live in that posting a thread asking for a system image and a possibly pre-loaded app qualifies as "demanding stuff"? Why should I have to have done anything to be worthy of your approval to post such a thread?
There is a huge conflict of interest with you both working for Nvidia and unofficially releasing official firmware and hacks, so frankly no, I don't trust you being involved in this devices xda development.
LegionTHEFecalExcretion said:
I what world do you live in that posting a thread asking for a system image and a possibly pre-loaded app qualifies as "demanding stuff"? Why should I have to have done anything to be worthy of your approval to post such a thread?
There is a huge conflict of interest with you both working for Nvidia and unofficially releasing official firmware and hacks, so frankly no, I don't trust you being involved in this devices xda development.
Click to expand...
Click to collapse
So a guy who doesn't own the device is not going to trust ROMs I make for a device he doesn't own. Oops, no loss to me. You can go back to trolling, I'm done with your thread. You have your system image and boot image in either manner you want it.
Oops, my bad. It wasn't your thread, you just came into this thread to troll me. My mistake.
Raptor, if you check in the Android Development section, you'll find the system images. I'd suggest the ZIP version, because it's both smaller and already extracted. The system.img is an uncompress image to be flashed via fastboot in case someone messes up their system or boot partitions.