Database Develop

[Question] Gingerbread on Tattoo?

Hey guys,
Now that Gingerbread is out, I think most questions on people's minds are: Can it happen? What's needed?
Sent from my Tattoo using XDA App

I'm trying to do something about it stay tuned...

i just saw a youtube video about a wildfire running an early built,
so i thinks its not a matter of resolution.

I just hope the CM can be work on ROM.

We need AOSP sources before it can be built properly. The ones on Wildfire etc are just hacked together from an emulator image, and they run quite slowly. For the Tattoo, I'm a bit uncertain if it can be used with kernel 2.6.29, or if 2.6.32 or higher is required.

It will eventually - Froyo took a while but is here. But I can't wait for the new UI and it will be speedy if Google are telling the truth

I was WAITING for someone to ask this question
Anyway, fingers crossed

It has to be possible: http://androinica.com/2010/12/07/go...droinica+(Androinica+-++A+Google+Android+Blog)

I guess gingerbread will take some time to come on tattoo, but there is a full gingerbread theme for tattoo available here.

aliwaqas said:
I guess gingerbread will take some time to come on tattoo, but there is a full gingerbread theme for tattoo available here.
Click to expand...
Click to collapse
I guess it will be pretty soon, because Gingerbread AOSP is already available to create ROMs like fyodor's or spartm's, and Cyanogen is working on modded Gingerbread too already

gingerbread on tattoo would be GREAT
Sent from my HTC Tattoo using XDA App

@those who try to port 2.3 for tattoo: If you're successfull, plz change the icon for mobile data... it's just too tiny for our small screen!

the source code for the nexus one is out, i dont know how difficult it is to port it to another device but i hope someone tries it already

I'm trying to compile gingerbread, if somebody(or more) wants to collaborate making vendor files, we can put up a github start a collaborate rom for our tattoo
I've triend changed fyodor files, but for now i'm stuck (something wrong with libstagefright)
Somebody?

Aaroneke said:
I'm trying to compile gingerbread, if somebody(or more) wants to collaborate making vendor files, we can put up a github start a collaborate rom for our tattoo
I've triend changed fyodor files, but for now i'm stuck (something wrong with libstagefright)
Somebody?
Click to expand...
Click to collapse
Stuck when compiling or when booting?

Compiling i've managed this problem, but i changed some stuff and now i got it again, i'm trying to make new vendor files step by step using fyodor,..etc (and google ref) files just for reference, but it can take a while(if i'll get it working..)

Milestone + Cyanogenmod is compatible with ADK?

I have the latest Cyanongemod (Android 2.3.4) and i wish to know if it is compatible with Android Open Accessory Development Kit (ADK).
ADK is compatible only with Android 2.3.4 and 3.1 but im not sure if Cyanomgemod include the required libraries.

Hi!
I´ve been searching this for a while, and yes, cyanogenmod (at least nightly builds) support - you might have trouble getting other customs roms.
You need 2.3.4+ and 2.6.35+ kernel with CONFIG_USB_ANDROID_ACCESSORY flag set. Instructions about xml, permissions, here (sorry, cant post full urls):
github.com/ezterry/manifest-gingerbread-DS/issues/32
Push nexus files from here:
forum.cyanogenmod.com/topic/26339-usb-accessory-mode-is-adk-supported-in-cm-7/
And upload demokit via eclipse.
Regards
Robson

robsondantas said:
You need 2.3.4+ and 2.6.35+ kernel with CONFIG_USB_ANDROID_ACCESSORY flag set. Instructions about xml, permissions, here (sorry, cant post full urls):
github.com/ezterry/manifest-gingerbread-DS/issues/32
Click to expand...
Click to collapse
There is one problem - you cannot flash custom kernel on Milestone that is not signed by Motorola (locked bootloader). And the latest kernel that we have is 2.6.32.9, so that will not work.
If you want custom kernel (but without radio) you can try to have a fun with 2nd boot - http://droid-developers.org/wiki/2ndboot

[Q] kernel 2.6.32 ??

look im a n00b(still learning android stuff),
so this question is just out of curosity
why cant we have kernel 2.6.32 ??
well google said froyo needs atleast 2.6.32 to run
but we here are running gingerbread smoothly on 2.6.29(thnaks to all the awsoms devs )
can someone knowledgble reply
thank you ;p

Simply because the kernel drivers needed for the X8 only exist in Linux 2.6.29 as published by Sony Ericsson.
If you would want to use a newer Kernel release (i.e. the ones Google is using for their Android builds) you need to port the drivers to that kernel version - read: make them fit the kernel.
That's a very tedious process, so it's easier for the ROM and Kernel developers to base their work upon the original SEMC Linux 2.6.29 sources.

on short: its easier to port drivers from 2.6.32 or 35 or 38 than make the base 2.6.32.... working on our phone

as b.jay said, porting kernels takes a long time, and if you recive only a couple of errors in the middle of it, BOOM, you gotta go back to the sart and track what wrong command you typed or what code is wrong etc. thats why no one has ported 2.6.32 kernel.
to many drivers to cope with, to much errors that you will recive. porting roms is easyer

thanks guyz for the answers....in short it is possible to have kernel 2.6.32....maybe nAa can port it....he has already backported some stuff.

It is possibe given someone wants to spend an insane amount of time (edit: we're talking several weeks to several months here) in forward-porting the Shakira specific drivers and additions to the ARM Linux code base.
I don't see it happen as it's a enormous undertaking for a single developer to port the whole stuff - that would require a medium-sized team of coders a) knowing what to port / b) well versed in Linux Kernel hacking / c) knowing how to code for ARM (edit: as the existing sources most likely need to be adapted to the Kernel ABI (in this case 2.6.3.x), which is not exactly stable in Linux and changes erratically as Linus' maintainers see fit. Also, don't forget that the changes need to be tested to see if the kernel boots and works flawlessly).
Don't hang your hopes too high.

need to much time to update linux version of kernel

But for instance lg optimus p350 has almost same specs but runs .32 kernel.it has same qualcomm 600 mhz cpu,ardeno 200,and 140 mb ram.so x8 has even better specs.so i dont se why this wouldnt be possible.
Sent from my GT-I5800 using xda premium

[Q] Can't build CM6 from sources. Help please!

Hi,
I'm trying to build cyanogenmod 6 (froyo) from sources on github for G1.
Sidenote. The reason I'm trying to do this is i'd like to modify kernel parameters. I'm trying to make the phone talk to external device using built in serial port. I can do it with my current CM6, but it looks like serial debugger engages and starts responding to the device and also steals some of the data being sent to phone.
To build I used instruction posted at cyanogen wiki "HTC Dream & Magic: Compile CyanogenMod (OS X)" which covers gingerbread but checked out froyo-stable branch at first. I know that gingerbread version stopped supporting G1 at some point last year.
Without much success even after fixing manifest to point to updated repo urls from kernel.org to googles repo etc. The problem is that apache-http seems incompatible with old sources and it is referenced by head.
I also tried froyo branch, but it doesn't build as well because something seem to be broken for dream_sapphire, and it is not present in the devices anymore.
I've tried searching for compilation errors, and general build questions/instructions here and on cyanogen's forum, but looks like CM6 is not very active these days.
Can someone point me into right direction where to search for relevant info on building it? Would getting a proper revision help or should I combine stuff from several branches to make it work?
I've already spent quite a lot of time figuring out how build is being configured and how things stitch together but without much progress on the actual build.
And with times required to sync a whole repo and build it, it is becoming frustrating.
Any help would be muchly appreciated!
Regards,
Oleg

It's dead.
I also wanted to make a cm6 rom, but I couldn't get anything to work.
I got the addresses all updated but it looks like a bunch of the files have completely dissappeared. You may be able to make it skip those, but then it may not work completely.
Go for AOSP?

Now that's a shame. I wanted to build CM because I'm familiar with it and the other thing is that they have reasonable instructions about building it. But at least I don't need to waste my time trying to figure out how to fix it.
In fact I don't need any extras they provide, a bare android would suffice to me if all the sensors and connectivity would be available. But I'm not familiar with internals of building vendor specific stuff. My understanding was that I need proprietary parts together with AOSP to build a working ROM and that's one of the things CM guys did. Correct me if I'm wrong.

aliher1911 said:
Now that's a shame. I wanted to build CM because I'm familiar with it and the other thing is that they have reasonable instructions about building it. But at least I don't need to waste my time trying to figure out how to fix it.
In fact I don't need any extras they provide, a bare android would suffice to me if all the sensors and connectivity would be available. But I'm not familiar with internals of building vendor specific stuff. My understanding was that I need proprietary parts together with AOSP to build a working ROM and that's one of the things CM guys did. Correct me if I'm wrong.
Click to expand...
Click to collapse
Nope AOSP is as easy to build now
Go to the android site and follow directions
Google for "build android"
At the part when doing repo init you need to get the right branch
Go to "build for devices" then scroll down for recommended branches and look for the dream
One thing you'll need to do differently is do "make otapackage" instead of plain "make"
And once that's done you'll need to tweak the zip and get rid of the "recovery" folder and tweak the updater-script
Oh yeah, and I don't know exactly how you would do this part, but you'll need to get the source for a newer kernel in there, like ezterry kernel and use it with 2708+ radio/spl
Unless you wanna use the AOSP kernel & spl & radio which is old
What I did is just flash his kernel after the rom, but you want to do kernel stuff so yeah...
Sent from my HTC Dream using Tapatalk

CM7 on New Bootloader - Feasible?

Hi All
I am not really a developer at all but I have had loads of experience messing around with ROMs to improve them (such as changing rils manually, using my own updater scripts, creating my own nvflash layouts and images, etc).
Recently I have been trying out CM10.1 again (mivvs ROM) on the new bootloader and also paranoid android. But both are too buggy for me and the battery life is really bad. So I am thinking to revert back to CM7 again.
I am planning to *TRY* and build my own CM7 rom from source using these fixes by Pengus (http://forum.xda-developers.com/showpost.php?p=35661482&postcount=100) to try and make it boot and run on the new bootloader. I know the advantages are very little but its just a "to see if I can" thing. It will also mean others wanting to go back to CM7 won't have to flash the old bootloader again.
I am planning just a one-time build as CM7 has pretty much reached completion.
I am posting this up to:
Make sure no-one else has already done it
Make sure one of the devs doesn't know of a reason this 100% will fail
To see if anyone else would be interested in such a ROM
To know if its possible to build from Windows (if I need Linux then so be it)
Let me know what you think

hy
I have mivvs rom and the battery life in not bad.
however, your idea is interesting .. good job!

Well, I think this is quite interesting. However, I am a big fan of PA10 and Pengus work... for me they beat GB in all aspects at the moment. However, one of the greatest pro's of having a CM7 on the new bootloader is the ability to have dual boot with CM7 + CM10.1 (or something else), since dual boot only works for roms with the same bootloader.

So far I have:
Set up Ubuntu x64 VirtualPC
Installed Android SDK and all Dependancies
Sync'd the CyanogenMod 7 Source
Sorted out the P990 Proprietary libs
Made MOST of the changes Pengus lists (although some bits are in different files)
It turns out the kernel source isn't downloaded automatically with CM7 so I need to find out how to build the kernel from source (in order to make the rest of the changes on the list Pengus made) but I think its looking good..
CM7 also doesn't have fstab.p990 but these lines can be found in init.p990.rc. Until I have the kernel source I am stuck on point 6
And I didn't mean to knock Pengus/TonyP/Mivv's work. They have helped this phone come a really long way especially now acree seems to have dropped support for it.

Just FYI
I tried this, making all the changes above, compiled the build.... but it doesn't boot.
Just gets stuck on the red lg logo.
I think the old CM kernel will not run on the new boot loader at all.
Was worth a try!

rlees85 said:
Just FYI
I tried this, making all the changes above, compiled the build.... but it doesn't boot.
Just gets stuck on the red lg logo.
I think the old CM kernel will not run on the new boot loader at all.
Was worth a try!
Click to expand...
Click to collapse
Maybe your last resort, try the excellent CM7 ETaNa kernel (link is in my signature).
But, I guess it won't work; kernels are bootloader specific.