Related
I was wondering if dual booting would be possible on our phone? I've seen that the HD2 got winmo + android boot... But having some kind of Stable partition and a second "dev" one would be quite amazing...
Thanks!
I asked the same question, and my post was moved to Q and A. Most responses were that WinMo is not worthy of the hardware. WP7 didn't attract quite the same disdain.
I would really love to run WP7 on the captivate, and I think eventually someone will make it happen. I think WinMo would run amazingly smooth, but I doubt we'll ever find out.
The HD2 won't quite run android ROMs, you have to boot into WinMo, then restart in Android, but it is really easy to swap what "ROM" you are using. If the HD2 was capable of AT&T 3G, I would have one by now.
Sent from my SAMSUNG-SGH-I897 using XDA App
Yes please to WP7 on Captivate. If nothing else i want to be able to run it for a few days to see how I like that new software. And check out the Xbox Live integration
yes, i only have one phone but would like to learn to do some basic development and it would be nice to have a stable rom to switch back to on the fly. i've had problems using nandroid and titanium backup. if anyone knows of a way to change to or add a secondary boot loader so multiple os's can be launched that would be awesome.
minmo might be a bit impractical but multiple android installations would be cool sweet.
Ok.. well get a checklist started on what you would need:
A custom bootloader that would work with the Captivate.. And I'm sure people would want the choice to pick the OS upon bootup instead of having to go into the recovery screen and booting up from there.
It would also have to be compatible with working Android and Win7
Someone would then have to find the source code to Win7 - or at least the SDK for it and develop in whatever language its written in.
Then someone would have to code the drivers for the Captivate and Win7 mobile.
Pretty much.. it wouldn't be any type of "take n' bake" task and would be quite the project involving a ton of work.
I'm sure someone out there in the world will come up with it.. I mean someone took the time to port Android to the iPhone - so it "could" happen.. but most likely won't due to the huge amount of work it will take.
avgjoegeek said:
Ok.. well get a checklist started on what you would need:
A custom bootloader that would work with the Captivate.. And I'm sure people would want the choice to pick the OS upon bootup instead of having to go into the recovery screen and booting up from there.
It would also have to be compatible with working Android and Win7
Someone would then have to find the source code to Win7 - or at least the SDK for it and develop in whatever language its written in.
Then someone would have to code the drivers for the Captivate and Win7 mobile.
Pretty much.. it wouldn't be any type of "take n' bake" task and would be quite the project involving a ton of work.
I'm sure someone out there in the world will come up with it.. I mean someone took the time to port Android to the iPhone - so it "could" happen.. but most likely won't due to the huge amount of work it will take.
Click to expand...
Click to collapse
At least there's a Samsung Omnia 7. It has a 4" SAMOLED like ours. I hope it has more in common with us as well so it would make the process easier.
JayPhill89 said:
At least there's a Samsung Omnia 7. It has a 4" SAMOLED like ours. I hope it has more in common with us as well so it would make the process easier.
Click to expand...
Click to collapse
if winmo gets ported great, if not oh well, if you read the op it was not to get winmo but just used the hd2 as an example of dual boot on a phone. a boot loader is a starting point so can the topic go in that direction? i just dont want naysayers to get confused and tell us every reason we wont get or dont want winmo.
You cannot just take the source code for WP7. It is not open source. You can port android to things, but not the other way around.
nbs11 said:
You cannot just take the source code for WP7. It is not open source. You can port android to things, but not the other way around.
Click to expand...
Click to collapse
As Dani897 said, the thread is not about porting WP7 to our phone, but just having dual boot to be able to have (lets say) one stable rom and one dev rom on the same phone...
seriously want this to happen figure it out
I know I am probably going to get some heat for posting a "Question" in the Devs section, but I did attempt to ask it in the Q&A section, but have not received any responses from any of the developers (not sure if they regular that section).
My question is why none of the Captivate developers utilize ROM manager as a place to download (and update) their custom ROMs? I know many of us have purchased the premium license, and wonder why you haven't utilized this feature? Is it more of a hassle? Is there costs involved that inhibit Devs from wanting to post there? I know EVO owners have a wide variety of ROMs on their device available for download right from manager.
Thanks in advance, and if this tread needs to be moved or deleted after, I won't be offended.
........and thank you Devs for your AWESOME Roms!
I, too, was disappointed after purchasing ROM Manager Premium that there were no ROMs available to download. I was under the impression that this would open up a load of ROMs for me to download and try out.
Personally, I think the purchase was well worth it considering how much I've used it. I did it to support the guy. I can find roms on my own.
Sent from my GT-I9000M using XDA App
majinzen said:
Personally, I think the purchase was well worth it considering how much I've used it. I did it to support the guy. I can find roms on my own.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Oh, I completely agree. I was just wondering why our devs haven't utilized it. Maybe it has to do with the file type system that the Galaxy S's use? I know it is probably safer using Odin to flash back to stock first, but maybe there was another reason? Or maybe that isn't even a reason?
Gr8Danes said:
Oh, I completely agree. I was just wondering why our devs haven't utilized it. Maybe it has to do with the file type system that the Galaxy S's use? I know it is probably safer using Odin to flash back to stock first, but maybe there was another reason? Or maybe that isn't even a reason?
Click to expand...
Click to collapse
I am not an expert but I think it has a lot to do with the fact that rom manager does not work with the captivate as it does with other devices such as the evo. For whatever reason when you simply try to flash a new rom, old remnants remain and you often experience problems especially when the new rom is based on a different build/kernel, etc. That is the reason everyone recommends flashing stock using odin first as it eliminates all remnants of the previous rom.
It is nice to be able to use the full functionality of rom manager on my evo but honestly I usually research here on xda first anyway.
I have yet to see a full explanation as to why we have the issue on the captivate and hopefully someone who understands the exact reason will take the time to explain.
It's related mainly to the Kernel and Modem I'm sure. The evo community doesn't use a kernel and modem file designed for an entirely different (albeit very similar) device; we do.
Rom manager needs to be more clear on how many ROMS will be available before purchase. The way it's worded makes it seem like you'll have roms to choose from regardless of your device.
I also upgraded to premium and spent time"trouble shooting" trying to figure out what was wrong.
I knew every popular rom wouldn't necessarily be listed but I certainly expected something.
Sent from my SAMSUNG-SGH-I896 using XDA App
Well atleast u helped out the dev who created this recovery that makes flashing incredibly easier for all of us.
sent from my cappy running Di11igafs Rom 2.5 overclocked at 1280 with JK4 modem!!!
For sure. I just came to my SGS frim an htc legend and have gotten more than my moneys worth from them. It is a good app, for sure.
Sent from my SAMSUNG-SGH-I896 using XDA App
Meant to quote just about everyone...
silverslotcar said:
Well atleast u helped out the dev who created this recovery that makes flashing incredibly easier for all of us.
sent from my cappy running Di11igafs Rom 2.5 overclocked at 1280 with JK4 modem!!!
Click to expand...
Click to collapse
Not the point of the question. Incase it needs to be reiterated, what he wants to ask is: Developers. Why are your ROMs not available via Rom Manager directly?
If there is a reason why you don't use it, it would be nice of you could elaborate. Not everyone has money to throw at something that they don't see beneficial. (Paid vs unpaid.) Donations are nice, but they are donations for a reason. Any "Oh, but you should contribute to Rom Manager creaters anyway." chat is beside the point and not the focus of this thread, so please keep your opinion on purchasing donate versions out of the equation.
I cant say why but it is their chose as if they want to use it or not. Please dont open more then one thread on the same subject.
I deem this thread closed
I have several smart phones and I have been able to root and flash roms now so far it seems like working on the tab is not as easy.... Is this true? im afraid of bricking it.... But is it worth rooting it?
Sent from my SPH-P100 using XDA App
from what I can gather on these boards thus far is that we went with the wrong carrier (sprint) for the tab, since tmobile seems to have more development going for it, AND at this point I am not seeing much advantage to rooting anyways. Let me know if you digested the boards differently as this is the only thing that is stopping me from rooting as well
well its because sprint is cdma and tmobile is gms which is found everywhere in the world... i am still within 30 days so i could return it, and I am thinking about switching to tmo anyway maybe going with the streak 7 as it has the tegra 2 processor
Thanks for replying buddy.
Hey guys, this might help you. Did a quick video on it and tested it myself on a Sprint tab, worked fine
How To Root -
http://theunlockr.com/2010/11/29/how-to-root-the-samsung-galaxy-tab/
Flash a Custom Recovery Image -
http://theunlockr.com/2010/11/29/how-to-flash-a-custom-recovery-image-on-the-samsung-galaxy-tab/
Good luck guys!
Awesome, but...
dcogen said:
Hey guys, this might help you. Did a quick video on it and tested it myself on a Sprint tab, worked fine
How To Root -
http://theunlockr.com/2010/11/29/how-to-root-the-samsung-galaxy-tab/
Flash a Custom Recovery Image -
http://theunlockr.com/2010/11/29/how-to-flash-a-custom-recovery-image-on-the-samsung-galaxy-tab/
Good luck guys!
Click to expand...
Click to collapse
Those How To's are AWESOME! Thanks! NO ONE has broken it down for we (the sad and lonely) CDMA SGT owners...
The question remains, however: Is it worth it?
So far, my answer is hell to thuh naw... With so many reports of brickage, and so little dev work being done, keeping the CDMA SGT stock seems to be the only way to go. I received my Tab for Christmas from a gorgeous santa (who also recently gave me another gift, my daughter (haven't rooted that device yet, either)) against my suggestions to wait (to get me a Tab, not to have my daughter). A few short months later, here we are:
XOOM dominates, SGT 2 and 10.1 (along with TONS of other Tabs) are announced and with Samsung's reputation for damn near NEVER updating their device's OS' (KIES SUCKS!), I'm thinking the SGT will never see the light of Honeycomb, which really is the only worthwhile upgrade for the device. As other tabs gain popularity, the dev work for the SGT decreases, with more and more messages like "This is the last update to this ROM, as I just got a XOOM".
So here I sit, with an oversized phone that can't make calls, watching Tron Legacy over and over while flashin' anything and everything on my EVO, longing for a XOOM...
That being said, anyone HATE the XOOM, and wanna' trade for an SGT? The SGT RULES!
For god's sake STOP POSTING QUESTIONS IN THE DEVELOPMENT FORUM. And search beofre posting. Thread reported.
dcogen said:
Hey guys, this might help you. Did a quick video on it and tested it myself on a Sprint tab, worked fine
How To Root -
http://theunlockr.com/2010/11/29/how-to-root-the-samsung-galaxy-tab/
Flash a Custom Recovery Image -
http://theunlockr.com/2010/11/29/how-to-flash-a-custom-recovery-image-on-the-samsung-galaxy-tab/
Good luck guys!
Click to expand...
Click to collapse
thanks for the links, this makes a lot of sense to me, its just like flash an android phone. Thanks a bunch
so general question, when doing the custom recovery on the sprint tab, if samsung/sprint releases the upgrade to 2.4 / 3.0 (god willing), will that upgrade have any impact on the custom recovery, or are the mutually exclusive?
So far, this has been a bust for me since I've been completely incapable of syncing with Kies. I've searched and tried every possible solution I could find to no avail.
dcogen said:
Hey guys, this might help you. Did a quick video on it and tested it myself on a Sprint tab, worked fine
How To Root -
http://theunlockr.com/2010/11/29/how-to-root-the-samsung-galaxy-tab/
Flash a Custom Recovery Image -
http://theunlockr.com/2010/11/29/how-to-flash-a-custom-recovery-image-on-the-samsung-galaxy-tab/
Good luck guys!
Click to expand...
Click to collapse
Dear dcogen,
I was able to verify that I have an adb connection, now when I downloaded the sprint kernel the file says flash_image_VZW_zImage.zip is this the correct one?
Also your guide says to install CWM for your tab version but I didnt find one for sprint, there are version for Verizon, ATT and TMO thats it.
I just dont want to end up with a brick
Thanks for your help
jcaf77 said:
well its because sprint is cdma and tmobile is gms which is found everywhere in the world... i am still within 30 days so i could return it, and I am thinking about switching to tmo anyway maybe going with the streak 7 as it has the tegra 2 processor
Thanks for replying buddy.
Click to expand...
Click to collapse
lolwut
....
Anybody follow this and have success? Are there any worthy ROMs out for our tab?
Sent from my SPH-P100 using XDA App
AlpineM3 said:
Anybody follow this and have success? Are there any worthy ROMs out for our tab?
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
can we use roms from other models if we find a way to not flash the wrong modem as part of the process?
+ 1 for working roms for sprint?
Help wanted!
Ice cream/beer money on me!!
+2 i want a sprint tab rom to use it on cricket and enable the phone portion.
It's the phone portion I need to figure out.
I rooted but not sure why no real reason to on a sprint tab to root cant find any wireless tether apps that will work
i rooted to get rid of some sprint crap bloatware
On the Sprint SGT you need to use New PC Studio instead of Kies. Follow the instruction exactly, but replace with NPC. Worked like a charm!
Pardon me for coming late to the party. Have been trying to root my Sprint (CDMA) tab for months. All fail for one reason or another (Z4Root doesn't work, Kies doesn't work on my Win 7 PC, SuperOneClick comes up as a virus and requires the use of Kies, PCStudio can be downloaded from a site that Firefox says is untrustworthy). I've spent endless hours reading msg boards and how-tos. i'm a resonably savy computer user. Is there a set of intnructions to root a Sprint-branded Tab anywhere???
MrZeroo00 said:
For god's sake STOP POSTING QUESTIONS IN THE DEVELOPMENT FORUM. And search beofre posting. Thread reported.
Click to expand...
Click to collapse
This isnt the DEV Forum... It is Q&A. Retard.
If you guys follow dj-steve on twitter then you will know he got honeycomb to boot on the s7. Great news. But to get it stable we need too have the kernel ported too 2.6.36. And maybe have the touch driver modified if that wasn't addressed in 2.6.36.
If you guys can ask around and see if anyone is willing to help with this you will be that much closer to hc. His twitter is @DMonsterProd follow him. And if you have any further questions regarding what needs to be done ask him through twitter he will respond.
Lets get some honeycomb small little step holding us back atm. Thanks peoples
http://www.youtube.com/watch?v=zrt8qGax91U&feature=youtube_gdata_player
sent from a tower
Hellzya said:
If you guys follow dj-steve on twitter then you will know he got honeycomb to boot on the s7. Great news. But to get it stable we need too have the kernel ported too 2.6.36. And maybe have the touch driver modified if that wasn't addressed in 2.6.36.
If you guys can ask around and see if anyone is willing to help with this you will be that much closer to hc. His twitter is @DMonsterProd follow him. And if you have any further questions regarding what needs to be done ask him through twitter he will respond.
Lets get some honeycomb small little step holding us back atm. Thanks peoples
sent from a tower
Click to expand...
Click to collapse
i have been trying hard myself , without trying to bugg dj-steve to much lol but its hard since he seems to be the only one willing
Reach out to your phone kernel devs its what I'm going to do. We need to start some kind of bounty to get some interest in porting the kernel.
sent from a tower
well we need to find whoever is basically working on hc ports already but we might need to send another device to someone in the xoom threads
I think pershoot is the man to ask since he is the kernel king in the game imo. The only problem is he can't do much without a device to try it on.
Sent from my HTC Vision using XDA App
Beta testers my friend pass the word on
sent from a tower
Booted the hc earlier and I must say its awesome. Lack of screen scrolling and such but it looks so good
sent from a tower
Already write to faux123. Lets see!
Sent from my HTC Glacier using XDA App
Yep folks contact as many users as pos. Throw it out on twitter etc. remember we have a near unbrickable device here so reflashing after a failed kernel attempt is as simple as hitting reset and loading into fastboot. And as hellzya said above the most critical issue preventing me releasing a prealpha build is touch screen driver being a bodgejob and not working properly. So if anyones got c coding skills that could be a place to start. Remember im working on 3 tabs and the ni adam is the base for my hc port which works accross most tegra 2 devices it would appear so updates are coming thick and fast.
Sent from my Dell Streak using Tapatalk
I have been working on porting CM9 to the VS910. So far I have gotten it to boot to the lock screen.
What Works
Boot animation
Lock screen
SurfaceFlinger
logcat/adb shell
3d accel is half working. I have gotten SurfaceFlinger to load up and interface the proprietary drivers (from GB) correctly, but HardwareRenderer (java framework) fails because the drivers don't give up a valid config.
What Doesn't Work
Touch screen
HardwareRenderer (fails because HardwareRenderer.chooseEglConfig() returns null value)
Everything else
Currently this ROM is totally unusuable for anything except for development. At this point, I do believe it is possible to get CM9 running, but it will take a good bit of developer effort. It would be helpful for any other developers around here to give some insight on the errors that come up in the adb logs.
How To Build
Follow Google's instructions for setting up a Linux system or VM for Android AOSP building
Follow CM9 build instructions up to brunch command
git clone git://github.com/andyichr/makerom.git to a location, such as ~/android/makerom
Overlay the files in ~/android/makerom/cm9-system/overlay onto the cm9/system directory (this adds vs910 brunch)
Adjust values in makerom.sh to match your own paths (MAKE SURE TO POINT IT AT A VALID KERNEL --I didn't include instructions for building a kernel)
Adjust values in makecm9.sh to match your own paths
Run ~/android/makerom/makecm9.sh to build cm9 (this takes a long time, depending on your system)
If build is successful, run ~/makerom/makerom.sh which will output a ROM which may be flashed to the device for testing
This is very rough work, but it proves that the basic parts of CM9/ICS do function on the Revolution. The cyanogenmod developers have already added some patches to the android source which allow ICS to run using video drivers from Gingerbread. This means it should be possible to get things working.
The current major problem with this ROM is that the HardwareRenderer does not initialize. Immediately after this, the main trebuchet process is killed and the system reboots itself after a while.
I will be happy to do what I can to support the process of porting CM9 to our phones. I read that a couple of other devs may be looking into porting CM7, but I think focusing on 9 might be more worth the effort, since we already have Gingerbread.
I have also attached a logcat to this post which should give developers some idea about what exactly is broken, which will lead to the first steps of debugging and porting.
Any interested developers should fork my repo on github (git://github.com/andyichr/makerom.git) which has the build scripts and patches.
That's about it for now. I very well may have left out some steps along the way. If you try to follow this process and it doesn't work out, let me know and I'll help you out.
ROM Download (very broken --only use for testing and development)
http://www.multiupload.com/GI0MLQYTE0 - Flash this if you want to see ICS boot to the lock screen or help test/debug. It's not useful for much else at this point.
We're getting there! I've already patched the android egl framework code slightly and built a kernel. CM team already patched frameworks/base for 2.3 video drivers. We'll patch what we have to to get this thing running! I am pretty busy but I will follow this thread and I hope for this to be a collaborative, transparent porting process! Good luck!
Nice, get with Mtmichaelson and Cubed, they are working on Cm9 also!
Sent from my VS910 4G using Tapatalk
Great! I saw in the CM7 thread that thecubed put up a git repo. I'm not sure exactly what his development plan is, but I'd be happy to fork his repo and trade patches, logs, etc. The more devs we have on this, the better... it's not a trivial task and I'm sure my wife hates me by now for spending so many hrs on it so far.
If I read correctly, thecubed just got a master repository set up for the revolution, so maybe the files that are needed could be lurking in there? I'll see if I can find the link and post it here.
Here's the link: https://github.com/thecubed
BLITZ ledded adshot nitro supercharged Gingerlution
I know in irc tonight cubed was talking about it. Guess they have to work on a few things but it's coming along. Wish I knew more so I could help out in this to. Guess I could be the Guinea pig.
Sent from my VS910 4G using Tapatalk
aichrist said:
Great! I saw in the CM7 thread that thecubed put up a git repo. I'm not sure exactly what his development plan is, but I'd be happy to fork his repo and trade patches, logs, etc. The more devs we have on this, the better... it's not a trivial task and I'm sure my wife hates me by now for spending so many hrs on it so far.
Click to expand...
Click to collapse
Awesome job so far! For a lot of things to work correctly, it's my understanding that you'll need a new kernel. For at least the touchscreen issues, you need the "idc" file in the "/system/usr/idc" directory (not sure if you have that or not, I didn't get a chance to check yet)
Either way, if you'd like to get in contact with me, hop on IRC and I'd be happy to answer any questions you may have.
Excellent work!
indyred99 said:
I know in irc tonight cubed was talking about it. Guess they have to work on a few things but it's coming along. Wish I knew more so I could help out in this to. Guess I could be the Guinea pig.
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
Yeah I see thecube's repo at https://github.com/thecubed/android_device_lge_revolution. His CM files are a lot cleaner than mine... I just copied the crespo config and haven't had time to clean it up yet. I'll do some diffs of his vs mine and see about getting things merged. My github repo has some additional files so what I could do is replace my vs910 device folder with a fork of thecube's repo.
I'm not sure whether his files are for CM7 or CM9 (or if it doesn't matter). I'm new to CM porting, but I'm not new to linux or android app development.
thecubed said:
Awesome job so far! For a lot of things to work correctly, it's my understanding that you'll need a new kernel. For at least the touchscreen issues, you need the "idc" file in the "/system/usr/idc" directory (not sure if you have that or not, I didn't get a chance to check yet)
Either way, if you'd like to get in contact with me, hop on IRC and I'd be happy to answer any questions you may have.
Excellent work!
Click to expand...
Click to collapse
Thanks for the tip. I'll check that out. So far I've mainly been banging my head on getting the adreno205 drivers working, but it sure would be nice to have touch working. That'd be the next priority.
I'm tempted to switch of 3d acceleration but I am focusing on one thing at a time.
I'll hop on IRC. Which channel are you on specifically?
As always guys, I'm happy to assist in testing. Nor very knowledgeable on coding or porting, but I can definitely put my phone at risk
BLITZ ledded adshot nitro supercharged Gingerlution
wish I knew more about this stuff so I could help
keep up the great work!
crossing fingers, hoping I'll get the chance to start making themes for CM9!
aichrist said:
Thanks for the tip. I'll check that out. So far I've mainly been banging my head on getting the adreno205 drivers working, but it sure would be nice to have touch working. That'd be the next priority.
I'm tempted to switch of 3d acceleration but I am focusing on one thing at a time.
I'll hop on IRC. Which channel are you on specifically?
Click to expand...
Click to collapse
Head over to #lgrevolution and I'll be there as IOMonster.
Yep, for ICS we need a lot of work in the KGSL department in kernel for getting proper Adreno support working... Tiamat is working on adding the new KGSL/USB/Genlock support to his MSM7X30 repo here ( http://git.tiamat-dev.com/7x30/htc-kernel-msm7x30/ ) and after that we need to merge our kernel sources with his (boardfiles, includes, configs, etc)
Booting to lockscreen is great, but there's a LOT of work to be done before we can have a "working" ICS by any stretch of the imagination... ICS is a whole new beast, unfortunately...
Cubed beat me to it.
Sent from my VS910 4G using xda premium
thecubed said:
Head over to #lgrevolution and I'll be there as IOMonster.
Yep, for ICS we need a lot of work in the KGSL department in kernel for getting proper Adreno support working... Tiamat is working on adding the new KGSL/USB/Genlock support to his MSM7X30 repo here ( http://git.tiamat-dev.com/7x30/htc-kernel-msm7x30/ ) and after that we need to merge our kernel sources with his (boardfiles, includes, configs, etc)
Booting to lockscreen is great, but there's a LOT of work to be done before we can have a "working" ICS by any stretch of the imagination... ICS is a whole new beast, unfortunately...
Click to expand...
Click to collapse
Great --I'll be on the channel as achristianson or achristi.
Thanks so much for all that info.
I'm sure it is a long road to a fully working ICS. I see it as a challenge and will just keep fixing the next broken thing...
I'd be happy to test this. I got a spare revo cuz I had a warranty and this dent on the outer corner was driving me nuts.
Gingerfused Gingervolt 1.3 + Blitz
It's really awesome to see everyone working on this. I really wish I knew more about this stuff to be able to help. All this is really making me wanna read up on this stuff and learn how to do some of it. Until that happens, I'll be more than happy to help out with any testing or in any other way within my capabilities. I got a Revo just sitting there deactived waiting for that ICS goodness.
Thanks a lot for everyone working on this. Those of us that aren't as gifted really aprreciate the work you guys are putting in.
Grizzy3 said:
It's really awesome to see everyone working on this. I really wish I knew more about this stuff to be able to help. All this is really making me wanna read up on this stuff and learn how to do some of it. Until that happens, I'll be more than happy to help out with any testing or in any other way within my capabilities. I got a Revo just sitting there deactived waiting for that ICS goodness.
Thanks a lot for everyone working on this. Those of us that aren't as gifted really aprreciate the work you guys are putting in.
Click to expand...
Click to collapse
If you've noticed my post in the CM7 Thread, which somehow 'feels' like it's sparked something off here (maybe just timing, lol), I am beginning to work on this stuff.
Anyone can do it, but the problem is motivation and the willingness to learn something new. You will never learn this stuff unless you're willing to fail and fail again. You learn by mistakes and mistakes sometimes turn into innovation for new things and ideas.
There is a lot of Dev's all of a sudden and I do agree, it's great to see. I was almost about to start looking at the Nexus. When I realized I would lose out on the $130 of extra accessories for my Revo (Car Dock, home dock, extra battery, car charge, etc.), And the fact the the Nexus had no External SD Card, I was like... Nah.. Time to step up and see what I can do to make the Revo a well-supported, up to date, kick-ass device. If LG and Verizon wanna sit on their asses, let'em. We make the phone better anyhow, right? MT, Cubed, and anyone else who has already contributed so much, has made this phone 10X's what it ever was out of the box. And, unlike LG and Verizon, Dev's like MT (and others) don't give us the run around on the next release, but a timeline.
-Cybie
Cybie257 said:
If you've noticed my post in the CM7 Thread, which somehow 'feels' like it's sparked something off here (maybe just timing, lol), I am beginning to work on this stuff.
Anyone can do it, but the problem is motivation and the willingness to learn something new. You will never learn this stuff unless you're willing to fail and fail again. You learn by mistakes and mistakes sometimes turn into innovation for new things and ideas.
There is a lot of Dev's all of a sudden and I do agree, it's great to see. I was almost about to start looking at the Nexus. When I realized I would lose out on the $130 of extra accessories for my Revo (Car Dock, home dock, extra battery, car charge, etc.), And the fact the the Nexus had no External SD Card, I was like... Nah.. Time to step up and see what I can do to make the Revo a well-supported, up to date, kick-ass device. If LG and Verizon wanna sit on their asses, let'em. We make the phone better anyhow, right? MT, Cubed, and anyone else who has already contributed so much, has made this phone 10X's what it ever was out of the box. And, unlike LG and Verizon, Dev's like MT (and others) don't give us the run around on the next release, but a timeline.
-Cybie
Click to expand...
Click to collapse
Exactly how i feel. Forget LG and Verizon. You guys are the ones taking these average phones into something great. I definitely gave up on getting any real support from either of them.
I really want to start getting into this. I have a little bit of time on my hands and will definitely be reading up on all this. I think you sparked something with your post lol. I know other people like MT and theCubed were already working on some things but I think you definitely added a little spark lol. Very happy to see other people jumping on board to help out. Hopefully I can too
Grizzy3 said:
Exactly how i feel. Forget LG and Verizon. You guys are the ones taking these average phones into something great. I definitely gave up on getting any real support from either of them.
I really want to start getting into this. I have a little bit of time on my hands and will definitely be reading up on all this. I think you sparked something with your post lol. I know other people like MT and theCubed were already working on some things but I think you definitely added a little spark lol. Very happy to see other people jumping on board to help out. Hopefully I can too
Click to expand...
Click to collapse
Yup! The motivation for me has been that support by LG and VZ is diminishing. This is the beauty of open source, though. Now the community can support it.
I believe the Revolution really is a good phone. It's got a good GPU and CPU. It's not dual-core, no, but with a good ROM on there, it can be much more efficient than a dual-core phone that is loaded with crapware.
Cybie did inspire me to put my work up sooner so that we can all focus on it and not duplicate our efforts as much.
thecubed said:
Head over to #lgrevolution and I'll be there as IOMonster.
Yep, for ICS we need a lot of work in the KGSL department in kernel for getting proper Adreno support working... Tiamat is working on adding the new KGSL/USB/Genlock support to his MSM7X30 repo here ( http://git.tiamat-dev.com/7x30/htc-kernel-msm7x30/ ) and after that we need to merge our kernel sources with his (boardfiles, includes, configs, etc)
Booting to lockscreen is great, but there's a LOT of work to be done before we can have a "working" ICS by any stretch of the imagination... ICS is a whole new beast, unfortunately...
Click to expand...
Click to collapse
OK so I was doing more debugging last night in the EGL/SurfaceFlinger/HardwareRenderer code. I also looked at some of Tiamat's work on the MSM7X30 kernel.
I can see now what you mean with regard to merging parts of that kernel into our own. I am assuming that kernel is being crafted to work with ICS-friendly EGL blobs for the adreno205. Is that correct? If so, then that kernel would have code that would be required to talk to the binary blob EGL drivers for Adreno205 that we would pull from some device that has the same chip and has official proprietary drivers for ICS available. I believe the HTC Droid Incredible 2 is one such device. Is this roughly what you were thinking?
I initially had thought of going down a different path: Instead of using newer ICS proprietary drivers and updating our kernel to support it, I was planning on keeping the kernel we have and the binary drivers we have, which are already made to work with each other. The work then required to get ICS working would be to change parts of the ICS userspace code such that they'd work with our older drivers. I don't have the links on hand, but I believe this is possible because I read about others taking this strategy on other devices that do not have ICS support officially but do have proper GB support. It also makes sense to me logically that the userspace code could be changed to our heart's content to work with older drivers, since we have full access to that source code. One option that I read about that we could potentially do is write a wrapper for the *adreno200*so librares that would implement the newer API that ICS is expecting and would translate the calls into the older API that is supported in our GB proprietary drivers.
It looks to me like we have two possible ways forward with regard to getting hardware acceleration working: upgrading the kernel and drivers to have "proper" ICS support, or patching ICS userspace code to work with GB drivers and kernel. I believe that patching the ICS userspace code would get us up and running faster while upgrading the kernel and adding newer drivers would be the better long-term solution.
Here are a couple of patches that people have already implemented to support older EGL blobs/kernels:
https://github.com/VorkTeam/android_frameworks_base/commit/429e922fb6f2660fc40472e939175688af52b1d2
https://gist.github.com/CyanogenMod...mmit/5d689bd02531f8ff256b3b1eddcaa8040c9f3559
https://gist.github.com/CyanogenMod...mmit/f8e2430be2d6b3e88afd7190f6712f3bc1df0cbf
Let me know what you think.
Also, what do you think about using the BOARD_USES_QCOM_HARDWARE := true directive to our CM board configuration? I noticed references to the QCOM_HARDWARE flags all over the video code. It seems we would want this since we are using a QCOM video chip. The only problem is the build failed for me when I added this flag. There's an issue about it on github: https://github.com/CyanogenMod/android_hardware_qcom_display/issues/3#issuecomment-3457179.
aichrist said:
OK so I was doing more debugging last night in the EGL/SurfaceFlinger/HardwareRenderer code. I also looked at some of Tiamat's work on the MSM7X30 kernel.
I can see now what you mean with regard to merging parts of that kernel into our own. I am assuming that kernel is being crafted to work with ICS-friendly EGL blobs for the adreno205. Is that correct? If so, then that kernel would have code that would be required to talk to the binary blob EGL drivers for Adreno205 that we would pull from some device that has the same chip and has official proprietary drivers for ICS available. I believe the HTC Droid Incredible 2 is one such device. Is this roughly what you were thinking?
I initially had thought of going down a different path: Instead of using newer ICS proprietary drivers and updating our kernel to support it, I was planning on keeping the kernel we have and the binary drivers we have, which are already made to work with each other. The work then required to get ICS working would be to change parts of the ICS userspace code such that they'd work with our older drivers. I don't have the links on hand, but I believe this is possible because I read about others taking this strategy on other devices that do not have ICS support officially but do have proper GB support. It also makes sense to me logically that the userspace code could be changed to our heart's content to work with older drivers, since we have full access to that source code. One option that I read about that we could potentially do is write a wrapper for the *adreno200*so librares that would implement the newer API that ICS is expecting and would translate the calls into the older API that is supported in our GB proprietary drivers.
It looks to me like we have two possible ways forward with regard to getting hardware acceleration working: upgrading the kernel and drivers to have "proper" ICS support, or patching ICS userspace code to work with GB drivers and kernel. I believe that patching the ICS userspace code would get us up and running faster while upgrading the kernel and adding newer drivers would be the better long-term solution.
Here are a couple of patches that people have already implemented to support older EGL blobs/kernels:
https://github.com/VorkTeam/android_frameworks_base/commit/429e922fb6f2660fc40472e939175688af52b1d2
https://gist.github.com/CyanogenMod...mmit/5d689bd02531f8ff256b3b1eddcaa8040c9f3559
https://gist.github.com/CyanogenMod...mmit/f8e2430be2d6b3e88afd7190f6712f3bc1df0cbf
Let me know what you think.
Also, what do you think about using the BOARD_USES_QCOM_HARDWARE := true directive to our CM board configuration? I noticed references to the QCOM_HARDWARE flags all over the video code. It seems we would want this since we are using a QCOM video chip. The only problem is the build failed for me when I added this flag. There's an issue about it on github: https://github.com/CyanogenMod/android_hardware_qcom_display/issues/3#issuecomment-3457179.
Click to expand...
Click to collapse
You guys are great! I hope this is doable, keep up the hard work..
Sent from my Nexus S 4G using XDA App