Related
Greeting guys,
The guys at Milestone & Droid's forum had successfully ported CM7 to their phone. Due to the locked bootloader and no official froyo update, the lease we can do is porting CM6 to our phone.
Due to my limited experience on rom cooking, i would like to seek guide and help from the experts. thank you.
Build from source: http://android.doshaska.net/cm6build
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Sholes
Wiki page: https://www.droid-developers.org/
I saw a video of it in youtube for the milestone. This would be cool if someone could make this work for our phone and it would be stable. I like the time and effort that is put into these froyo builds, but they are not stable like eclair.
Brian5475E said:
I saw a video of it in youtube for the milestone. This would be cool if someone could make this work for our phone and it would be stable. I like the time and effort that is put into these froyo builds, but they are not stable like eclair.
Click to expand...
Click to collapse
Dexter 1.3 vanilla and Dexter 1.3 with bugfix v2 and 3 is rock solid here, so dunno what you're talking about.
IMHO, If you just want a stable ROM,we should give our devs some time so they can iron out the issues-in-hand. They're not working with team as CM guys, so please be patient.
But on the other hand, you're a great big fan of CM and currently stuck with XT which can't get CM out of the box, you may try.
spiderx_mm said:
IMHO, If you just want a stable ROM,we should give our devs some time so they can iron out the issues-in-hand. They're not working with team as CM guys, so please be patient.
But on the other hand, you're a great big fan of CM and currently stuck with XT which can't get CM out of the box, you may try.
Click to expand...
Click to collapse
Getting an unofficial CM on XT720 is my ultimate goal, but I don't know how to do it yet. I'm learning about Android by fixing bugs/tweaking Dexter's ROM.
I pulled the CM6 sources and tried to build and follow the instructions on nadlabak's website. It seems like CM6 hasn't been built in a while so there are some bit-rot problems. For example it can't pull down the rom-manager stuff. I don't know if we need that or not. We don't (yet?) have rom-manager for XT720. Then there's the issue of the proprietary files. The proprietary files that need to be saved for Milestone (nadlabak's extract-files.sh script) doesn't match the files on XT720. So we'll have to work that out as well.
Mioze7Ae said:
Getting an unofficial CM on XT720 is my ultimate goal, but I don't know how to do it yet. I'm learning about Android by fixing bugs/tweaking Dexter's ROM.
I pulled the CM6 sources and tried to build and follow the instructions on nadlabak's website. It seems like CM6 hasn't been built in a while so there are some bit-rot problems. For example it can't pull down the rom-manager stuff. I don't know if we need that or not. We don't (yet?) have rom-manager for XT720. Then there's the issue of the proprietary files. The proprietary files that need to be saved for Milestone (nadlabak's extract-files.sh script) doesn't match the files on XT720. So we'll have to work that out as well.
Click to expand...
Click to collapse
I think they use Androidiani Open recover instead of Rom Manager on Milestone's CM.
I feel that the more people involve on this project the better. Just my thought.
helmi666 said:
I think they use Androidiani Open recover instead of Rom Manager on Milestone's CM.
I feel that the more people involve on this project the better. Just my thought.
Click to expand...
Click to collapse
What I meant was that compiling cm2mm 6 requires the ROM-Manager source code, but the download of that source fails. I think the git just moved, but I haven't tried chasing it down yet.
Mioze7Ae said:
What I meant was that compiling cm2mm 6 requires the ROM-Manager source code, but the download of that source fails. I think the git just moved, but I haven't tried chasing it down yet.
Click to expand...
Click to collapse
Just let me know what you need. I'll try my best to ask around. I really hope more people will join this 'Quest'
helmi666 said:
Just let me know what you need. I'll try my best to ask around. I really hope more people will join this 'Quest'
Click to expand...
Click to collapse
ROM-Manager source code,
Mioze7Ae said:
What I meant was that compiling cm2mm 6 requires the ROM-Manager source code, but the download of that source fails. I think the git just moved, but I haven't tried chasing it down yet.
Click to expand...
Click to collapse
svn checkout http://svn.codespot.com/a/eclipselabs.org/rom-manager/trunk/ rom-manager-read-only
WE HAVE MOVED TO A NEW THREAD IN THE DEVELOPMENT SECTION... THIS THREAD WILL BE LOCKED REALLY SOON.
What does the Official MIUI ICS look like? *A little unrelated treat*
Click Here To Find Out
Official Source (Chinese)
Note from Nvidia about drivers
Hello Android Development Community
We appreciate all the interest and passion surrounding the NVIDIA Tegra Platform and we take our support for the development community seriously. NVIDIA has been working with Google and Motorola to provide the open source community with the required drivers and other binary code to build full Android OS images for the Tegra 2 powered "Motorola Xoom". We expect Google to make those components available as part of the Android Open Source Project soon.
In addition, NVIDIA is working on a full release of Ice Cream Sandwich (ICS) for our Tegra 2 Dual Core and Tegra 3 Quad Core reference devices to be made available early next year. This release package will comprise of binary code, drivers developed on our reference platforms and any patches necessary to ensure stability & performance with ICS. We hope the open source community can leverage this release for their work on all Tegra devices.
Andrew Edelsten
Click to expand...
Click to collapse
Developers Working on ICS:
ttabbal (Recognized Developer / Kernel Dev)
Morfic (Recognized Developer / Kernel Dev)
Dameon87 (Recognized Developer)
chuckhriczko
doniqcc
teleknEsis
enoch861
King-Nai
What can I do to help?
What you guys can do to help is create a twitter or use your own twitter account and post the following to get the attention of LG about the lack of support for developers. Reword it how you want but include all the hash tags so we can get LG to help us out. We support THEM! They are nothing without the consumer base or Click here for direct contact links
Help #boycottLG! Lack of developer support on the @NVIDIATegra #g2x. #WENEEDSOURCE to utilize all of its power #android #ics
Click to expand...
Click to collapse
*NEW* Response From LG
*New* ANOTHER Response from LG
Pictures & Video
List Of Dumps & Useful Files:
Both Gingerbread and Froyo Source Codes for G2X
Galaxy Nexus Dump (Recovery, System, Boot) *Reupped*
Official Nvidia Github (Source Codes and Kernel Files)
IRC Channel (Limit to questions only and don't ask for ETA's)
Tell Nvidia to release the source code!
G2X Tegra Compile Patch Created by ttabbal (Dev's Only - Click for explanation)
Just WOW!
Sent from my LG-P999 using XDA App
Awesome
Sent from my LG-P999 using XDA App
This looks promising! I wish I was a dev and could do things with this.
Downloaded it anyways...
So does this really mean ics roms?
Sent from my LG-P999 using XDA App
ZeroT| Demented said:
So does this really mean ics roms?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Nowhere near fully functional ones.
Azuske said:
http://evervolv.turnertechrepair.info/Clark44/Android4.0-System-Dump.zip
Get to work devs... make it happen for us if possible
Click to expand...
Click to collapse
its the galaxy nexus dump or the sdk system image? (just to clarify)
andQlimax said:
its the galaxy nexus dump or the sdk system image? (just to clarify)
Click to expand...
Click to collapse
Just a system dump
omarsalmin said:
Just a system dump
Click to expand...
Click to collapse
system dump from the phone, or the system dump from the sdk..that what i mean and are not the same..i know its the system dump..but from where?
andQlimax said:
system dump from the phone, or the system dump from the sdk..that what i mean and are not the same..i know its the system dump..but from where?
Click to expand...
Click to collapse
Just a system dump from the phone.
On another note: I just pulled the new fonts from this and pushed them to my phone. I must say, the new Roboto front is GORGEOUS. A real upgrade to the default android font we've become so familiar with.
andQlimax said:
system dump from the phone, or the system dump from the sdk..that what i mean and are not the same..i know its the system dump..but from where?
Click to expand...
Click to collapse
to my knowledge its the System Dump from the Galaxy Nexus.
Azuske said:
to my knowledge its the System Dump from the Galaxy Nexus.
Click to expand...
Click to collapse
just extracted it..its the system image of the sdk 4.0..not from the phone..also no google apps
Mind sharing the font?
AOSP ROMS ftw!
It'll make some nice ICS themes for now. Need source code for much more than that.
athanos said:
It'll make some nice ICS themes for now. Need source code for much more than that.
Click to expand...
Click to collapse
Exactly, which is why Cyanogenmod is not doing anything with it until the source comes out. I hope that it is soon.
ICS would be fantastic on this device. Eventually we'll get it, I have faith in our developers!
But Dec seems so far away, after watching the preview videos of ics it was clear that it's a worthy upgrade. Miles ahead of ios5
I don't know anyone else's results but I made up a hybrid of this and the stock rom (basically combined the two without overwriting files. So any LGE proprietary files were still there) but it didn't work. Bootloops after the initial LG screen. I'm thinking boot.img for some reason but haven't unpacked it yet. Anyone else have any ideas?
chuckhriczko said:
I don't know anyone else's results but I made up a hybrid of this and the stock rom (basically combined the two without overwriting files. So any LGE proprietary files were still there) but it didn't work. Bootloops after the initial LG screen. I'm thinking boot.img for some reason but haven't unpacked it yet. Anyone else have any ideas?
Click to expand...
Click to collapse
You mean you placed the new ICS system apps and combined it with the stock GB?
I think the system apps from ICS would use API's not supported in GB and hence would bootloop.
barqers said:
You mean you placed the new ICS system apps and combined it with the stock GB?
I think the system apps from ICS would use API's not supported in GB and hence would bootloop.
Click to expand...
Click to collapse
No. I extracted the stock Tom and the system dump. I modified the 4.0 build.prop, used the stock boot image and then.merged the stock rom into the 4.0 rom, not overwriting existing files. basically just adding stock files. this gives it the ril specified in build.prop, etc. I was hoping to at least get to the second boot screen so I could use logcat but no go.
Hi,
Nvidia has just release binary and tools to build ICS ROM for Tegar2 plateforme...
http://developer.nvidia.com/tegra-resources
Bye
looks like (a lot of) the stuff needed to get our own built AOSP image running properly on the TF101.
Who knows, we might see a proper ICS rom before Asus releases their own .
I cant wait to see a ics-rom on my TF101!
Sent from my Galaxy Nexus using xda premium
Ohhhh... Nice.... I'm new around here does the transformer have a dev that build aosp roms from source (not kanged)
That page has been around forever and doesn't have what is necessary to get AOSP on pretty much anything.
There's been a few accounts posting that all around the same time frame the last few days all over the Tegra based device forums.....hmmmmmm.
thanks for this!reading ics 3ad it seems that it isn't so usefull...(http://forum.xda-developers.com/showpost.php?p=21768082&postcount=361)what are you think about that?
They posted an ICS device image for ventana. We can pull the required binaries from there as a starting point rather than trying to get ICS to work with the binaries pulled from honeycomb.
I'm downloading it now.
Thanks for the post!
daoist said:
They posted an ICS device image for ventana. We can pull the required binaries from there as a starting point rather than trying to get ICS to work with the binaries pulled from honeycomb.
I'm downloading it now.
Thanks for the post!
Click to expand...
Click to collapse
...we already have binaries that work with ICS, I've had builds in the public with working (and very smooth) graphics for weeks. If these ones are comparable then it'll be a nice source to pull them from, build a ROM without having to pull from a device etc. but they don't make anything any easier as you suggest.
paulburton said:
...we already have binaries that work with ICS, I've had builds in the public with working (and very smooth) graphics for weeks. If these ones are comparable then it'll be a nice source to pull them from, build a ROM without having to pull from a device etc. but they don't make anything any easier as you suggest.
Click to expand...
Click to collapse
But isn't there a new kernel in there or something to help with the (deep) sleep problems? Or is the reference board too diferent from our TF101 board?
It's all quite helpful. Cribbing stuff from a working compile is going to be easier than doing it from scratch.
dipje said:
But isn't there a new kernel in there or something to help with the (deep) sleep problems? Or is the reference board too diferent from our TF101 board?
Click to expand...
Click to collapse
There's a kernel binary, sure. It won't run on the TF101 though because as you mention it's not the same board. Ok, maybe it would run, but if it does then it'll have all the wrong peripheral setup etc. The source for the kernel is (presumably) the same nvidia source that's been available for a while and is the basis of the TF101 kernel I've been working on, so it shouldn't be significantly different.
daoist said:
It's all quite helpful. Cribbing stuff from a working compile is going to be easier than doing it from scratch.
Click to expand...
Click to collapse
'Cribbing' what exactly? I'm not sure what you think you can usefully take from this.
paulburton said:
There's a kernel binary, sure. It won't run on the TF101 though because as you mention it's not the same board. Ok, maybe it would run, but if it does then it'll have all the wrong peripheral setup etc. The source for the kernel is (presumably) the same nvidia source that's been available for a while and is the basis of the TF101 kernel I've been working on, so it shouldn't be significantly different.
'Cribbing' what exactly? I'm not sure what you think you can usefully take from this.
Click to expand...
Click to collapse
All the proprietary binaries/configs/etc. The sort of stuff we'd pull via extract-files.sh. Right now you've done an excellent job building it up from what we had in honeycomb. Now we have known-good files from ICS.
daoist said:
All the proprietary binaries/configs/etc. The sort of stuff we'd pull via extract-files.sh. Right now you've done an excellent job building it up from what we had in honeycomb. Now we have known-good files from ICS.
Click to expand...
Click to collapse
Well, no. The _only_ things that I intend to use binaries for are the graphics drivers and bluetooth firmware. Bluetooth firmware doesn't care at all which version of android you're running, so we can ignore that. Which just leaves graphics drivers, which are already taken from an ICS ROM (fortunately the TF101 isn't the only tegra 2 tablet!).
i read here:http://forum.xda-developers.com/showthread.php?t=1598713 and now i wanna try to port jelly bean,but s plus dont have same processor with nexus.need help....:laugh:
It won't work by simply porting. You need to edit boot.img. the init.rc and init.traces.rc inside boot.img need modification. also several other patches inside kernel is required. I believe that kernel 3.08 is required to port jb. the 2.6.35.14 won't do. So,first we need kernel. then someone experienced like oisis,arco,brood,etc. or,you can wait for the sources. they will be released by mid july.
Doomsday94 said:
It won't work by simply porting. You need to edit boot.img. the init.rc and init.traces.rc inside boot.img need modification. also several other patches inside kernel is required. I believe that kernel 3.08 is required to port jb. the 2.6.35.14 won't do. So,first we need kernel. then someone experienced like oisis,arco,brood,etc. or,you can wait for the sources. they will be released by mid july.
Click to expand...
Click to collapse
in weekend 3.0.8,i think will be finished.all can make this rom easy...
Doomsday94 said:
then someone experienced like oisis,arco,brood,etc. or,you can wait for the sources. they will be released by mid july.
Click to expand...
Click to collapse
Exactly. First Google needs to release the source code!
Trying to hack together some kind of SDK port now with the files from the Nexus is completely useless. Some people on XDA have tried it for other devices and it's buggy and you can't even get basic phone functionality such as calling.
EDIT: You can also read the official statement on the subject by the CyanogenMod team here: https://plus.google.com/117962666888533781522/posts/PNJutPNhixo
k....
Discussions about JB goes here... http://forum.xda-developers.com/showthread.php?t=1742827
Closing thread
[SAMSUNG OSRC COMMENTS DELIVERY NOTIFICATION]
♦ classification : mobile_phone ♦
♦ model name : SCH-I535_NA_JB ♦
Hello,
MD3 FOTA service was stopped recently because the sw version has data issue.
So we'll release the new binary fixed the issue soon.
And the opensource for new version will be posted.
Thanks.
Click to expand...
Click to collapse
Got this email a few minutes ago. Guess this explains why the source request was taking so long.
well good to know at least there on top of things
just now how long till it's fixed
LLStarks said:
Got this email a few minutes ago. Guess this explains why the source request was taking so long.
Click to expand...
Click to collapse
I was just checking out that site...so the link it has for MB1 for SCH-i535 is the full MB1 OTA you can flash basically?
No, you can't flash anything from that site.
Aaaaaaand this is why we want an unlocked bootloader, Verizon.
Sent from my SCH-I535 using Tapatalk 4 Beta
NinCaptain said:
well good to know at least there on top of things
just now how long till it's fixed
Click to expand...
Click to collapse
One day for Samsung to fix and 3 months for Verizon to test and approve.
LLStarks said:
Guess this explains why the source request was taking so long.
Click to expand...
Click to collapse
Source for what ? I'm new to Samsung devices, but not Android, and they only have to release source for the kernel. This recent update didn't include a new kernel, did it ? If Samsung uses other open-source code, I didn't know.
hallstevenson said:
Source for what ? I'm new to Samsung devices, but not Android, and they only have to release source for the kernel. This recent update didn't include a new kernel, did it ? If Samsung uses other open-source code, I didn't know.
Click to expand...
Click to collapse
I'm not sure what the OP is talking about . The radio/modem is not open source, its Verizon proprietary. So unless the bug is in the Samsung portion open source does not apply
hallstevenson said:
Source for what ? I'm new to Samsung devices, but not Android, and they only have to release source for the kernel. This recent update didn't include a new kernel, did it ? If Samsung uses other open-source code, I didn't know.
Click to expand...
Click to collapse
Kernel source, there's a new kernel with each update. At least there is when referencing the date it was compiled. I won't claim to say I read code/source but there's definitely a few adjustments between one compiled OTA kernel and the next.
DigitalMD said:
I'm not sure what the OP is talking about . The radio/modem is not open source, its Verizon proprietary. So unless the bug is in the Samsung portion open source does not apply
Click to expand...
Click to collapse
The modem being proprietary isn't the main concern. If what OP has posted is true, Samsung is just withholding VRBMD3 kernel source to push another OTA after which they'll provide kernel source for that newer OTA.
Llstarks just wants source and there's nothing wrong with that. Just means we have to wait a little longer is all.
Sent from my SCH-I535 using Tapatalk 4 Beta
Well, we wanted the source so we could figure out what was going on between the camera blob and the trust zone partition.
Camera wasn't loading with a MD3 tz.