MoDaCo is undergoing planned maintenance. Site functionality may be reduced - follow @modaco or @paulobrien on Twitter for updates.

  • Announcements

    • Reminder - MoDaCo position on illegal content

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such software
      Nintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)


      CUSTOM ROMS

      You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not be hosted directly in topic via the MoDaCo attachment system
      ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)
      ROMs must give full credit to the original author
      This decision has been taken in light of the huge amount of interest in this area of device customisation within the community, and member feedback! Please note that custom ROM discussion should be kept in specific device sub-areas, (e.g. Kaiser.MoDaCo.com for Kaiser based devices). ISSUES If you have any issues with this policy, please contact me directly via PM. P
    • Support MoDaCo by signing up to a MoDaCo Silver or Gold membership

      To sign up to an annual MoDaCo Silver subscription which will eliminate all ads from the site (as well as giving you access to the MoDaCo Online Kitchens for Android) for only £9.99 using PayPal, Credit or Debit Card, ensure you are logged in to the site, and then click the link below, which will take you directly to the subscription store! You can also sign up to an annual MoDaCo Gold subscription for £29.99, which adds the benefits listed below! PURCHASE A MODACO SUBSCRIPTION - FREE Titanium Backup Mobile for Android worth $5.99! - FREE 1 year PrivateInternetAccess.com worth $39.95! - FREE 1 year LastPass Premium worth $12! - FREE CalcConvert for Pocket PC from Binaryfish worth $17.95! - FREE Calendar Bar for Pocket PC from OmegaOne worth $9.99! - FREE CamerAware for Pocket PC and Smartphone from MoDaCo worth £19.99 / $30! - FREE Chronos for Pocket PC from ActiveKitten worth $14.95! - FREE CodeWallet Pro for Smartphone and Pocket PC from DeveloperOne worth up to $24.95! - FREE Concentrix for Pocket PC from eSoft Interactive worth $9.95! - FREE FlexMail for Pocket PC and Smartphone from WebIS worth up to $59.90! - FREE FTouchSL for Pocket PC from Vekoff s.r.o. worth 10 euro / $12.50! - FREE Jewel Challenge for Pocket PC from eSoft Interactive worth $9.95! - FREE John Cody's Alerts Pro for Smartphone from Omnisoft worth $14.95! - FREE LingvoSoft Talking Dictionary 2008 English <-> Dutch for Pocket PC from Lingvosoft worth $49.95! - FREE LingvoSoft Talking Dictionary 2008 English <-> French for Pocket PC from Lingvosoft worth $49.95! - FREE LingvoSoft Talking Dictionary 2008 English <-> German for Pocket PC from Lingvosoft worth $49.95! - FREE LingvoSoft Talking Dictionary 2008 English <-> Italian for Pocket PC from Lingvosoft worth $49.95! - FREE LingvoSoft Talking Dictionary 2008 English <-> Spanish for Pocket PC from Lingvosoft worth $49.95! - FREE LingvoSoft Dictionary English <-> Dutch for Smartphone from Lingvosoft worth $49.95! - FREE LingvoSoft Dictionary English <-> French for Smartphone from Lingvosoft worth $49.95! - FREE LingvoSoft Dictionary English <-> German for Smartphone from Lingvosoft worth $49.95! - FREE LingvoSoft Dictionary English <-> Russian for Smartphone from Lingvosoft worth $49.95! - FREE LingvoSoft Dictionary English <-> Turkish for Smartphone from Lingvosoft worth $49.95! - FREE Note2Self for Pocket PC and Smartphone from WebIS worth up to $19.90! - FREE Opera 8.60 for Pocket PC and Smartphone from Opera Software worth up to $48! - FREE Pocket Informant for Pocket PC and Smartphone from WebIS worth up to $59.90! - FREE Pocket Launcher for Pocket PC and Smartphone from Conduits worth $9.95! - FREE PTab for Pocket PC and Smartphone from z4soft worth up to $60! - FREE Resco Explorer for Pocket PC and Smartphone from Resco worth up to $49.90! - FREE Safemode for Pocket PC from monocube worth $12.95 - FREE SplashPhoto for Pocket PC and Smartphone from SplashData worth up to $59.90! - FREE Sprite Backup for Pocket PC and Smartphone from Sprite Software worth $29.95! - FREE Teksoft Glyphs UI for Pocket PC and Smartphone from Teksoft €9.95! - FREE Teksoft HeadsetRemote for Pocket PC and Smartphone from Teksoft €4.95! - FREE Traffic Jam for Pocket PC from eSoft Interactive worth $9.95! - FREE unlock (1 per year) from imei-check.co.uk - DISCOUNT of 10% at MoDaCo FairDeal - DISCOUNT of 10% at Semsons.com - FORUM - AD FREE SITE - FORUM - custom rank / title - FORUM - double competition entries - FORUM - double post attachment space - FORUM - no search flood control - FORUM - priority event registration - FORUM - triple PM space
    • Reminder: Selling items on the forum directly is not allowed

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspensions / ban.

Android AOSP

35 posts in this topic

Posted · Report post

Before I get told I know that ril isn't working so technically ahving an aosp isn't much use, but this is more for teaching purposes so that I can undertsand it better asnd then eventually create my own roms. I ahve set up the android sdk and eclipse and these all work fine (this is for android 2.2.1). I am however finding it difficult to then create a rom for the blade from this. Could someone point me in the direction of guide which is easily tranferable to the blade or perhpas give me some pointers. I am ok on linux and can do some java, but I am trying to teach myself from stracth about android.

thanks

0

Share this post


Link to post
Share on other sites

Posted · Report post

agh. HAVE NOT AHVEN.

0

Share this post


Link to post
Share on other sites

Posted · Report post

From the SDK you can't create a ROM. It is for SOFTWARE (application) development!

You need to download and compile the Android Source code yourself (for that you need Ubuntu x64, read the Android Source page for details).

But, you need a lot of work to build everything right. First of all, setting up the device tree isn't the easiest thing to do.

0

Share this post


Link to post
Share on other sites

Posted · Report post

From the SDK you can't create a ROM. It is for SOFTWARE (application) development!

You need to download and compile the Android Source code yourself (for that you need Ubuntu x64, read the Android Source page for details).

But, you need a lot of work to build everything right. First of all, setting up the device tree isn't the easiest thing to do.

Thanks, i'm looking into it now

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Regarding x64:

Afaik this info is not right. I've built Froyo myself on 32bit x86 Ubuntu 10.10, and yes, it did throw an error like this before it worked, but with a little googling I've found that the failure was something else (something wrong with java I think, but I don't remember it).

Also, the source-page (witch contains a lot(!) of outdated information) states that x64 is experimental and x86 is to be prefered:

http://source.android.com/source/download.html

Just wanted to say it's possible on 32 bit, but I think 64 bit should be preferred if you can use it, although the site tells you something else.

Edited by FelixL
0

Share this post


Link to post
Share on other sites

Posted · Report post

Regarding x64:

Afaik this info is not right. I've built Froyo myself on 32bit x86 Ubuntu 10.10, and yes, it did throw an error like this before it worked, but with a little googling I've found that the failure was something else (something wrong with java I think, but I don't remember it).

Also, the source-page (witch contains a lot(!) of outdated information) states that x64 is experimental and x86 is to be prefered:

http://source.android.com/source/download.html

Just wanted to say it's possible on 32 bit, but I think 64 bit should be preferred if you can use it, although the site tells you something else.

Gingerbread requires a x64bit dev system to build....

I do recall seeing a patch somewhere on google's code site where the patch changes the make files to use 32bit java.....

0

Share this post


Link to post
Share on other sites

Posted · Report post

Regarding x64:

Afaik this info is not right. I've built Froyo myself on 32bit x86 Ubuntu 10.10, and yes, it did throw an error like this before it worked, but with a little googling I've found that the failure was something else (something wrong with java I think, but I don't remember it).

Also, the source-page (witch contains a lot(!) of outdated information) states that x64 is experimental and x86 is to be prefered:

http://source.android.com/source/download.html

Just wanted to say it's possible on 32 bit, but I think 64 bit should be preferred if you can use it, although the site tells you something else.

As it's said, the latest branch (gingerbread) what is checked out by default needs an x64 build system. The Android Source site is so outdated it refers to Android 1.5 infos!

I suggest to take a look at the CyanogenMod wiki, it tells you everything you need :lol:

0

Share this post


Link to post
Share on other sites

Posted · Report post

Okay, it's possible that you really need x64 for Gingerbread. I thought it could be the same thing as with Froyo, and yes, it could have been something with some makefile that needed to be changed. My brain is just like a sponge today. Full off holes :lol:

0

Share this post


Link to post
Share on other sites

Posted · Report post

Okay, it's possible that you really need x64 for Gingerbread. I thought it could be the same thing as with Froyo, and yes, it could have been something with some makefile that needed to be changed. My brain is just like a sponge today. Full off holes :)

But, a sponge can fast suck in everything :lol:

0

Share this post


Link to post
Share on other sites

Posted · Report post

But, a sponge can fast suck in everything :lol:

Yeah, and if it's under pressure, it will lose everything as fast as it was sucked up. I've got exams next week, I hope the pressure doesn't get to high :)

0

Share this post


Link to post
Share on other sites

Posted · Report post

is compile the android kernel same way than compile a linux kernel ?

0

Share this post


Link to post
Share on other sites

Posted · Report post

is compile the android kernel same way than compile a linux kernel ?

Have a look at this thread - it might help you! :lol:

0

Share this post


Link to post
Share on other sites

Posted · Report post

ho haven't seen this post

all answers are here

thank you :lol:

0

Share this post


Link to post
Share on other sites

Posted · Report post

I would recommend starting from codeaurora source. The AOSP source will not boot without modifications (or a modified kernel). You should be able to get a codeaurora rom booting without any modifications, you just need the right device config.

0

Share this post


Link to post
Share on other sites

Posted · Report post

I would recommend starting from codeaurora source. The AOSP source will not boot without modifications (or a modified kernel). You should be able to get a codeaurora rom booting without any modifications, you just need the right device config.

Is aurora easier to get going than CM? I assumed that because CM supports the Legend, which uses the same chipset as the blade that it would also be a good place to start?

0

Share this post


Link to post
Share on other sites

Posted · Report post

Is aurora easier to get going than CM? I assumed that because CM supports the Legend, which uses the same chipset as the blade that it would also be a good place to start?

codeaurora have a gingerbread release available for MSM7627

0

Share this post


Link to post
Share on other sites

Posted · Report post

I would recommend starting from codeaurora source. The AOSP source will not boot without modifications (or a modified kernel). You should be able to get a codeaurora rom booting without any modifications, you just need the right device config.

Tell me more. I just failed booting an rather generic AOSP 2.2 that I built. Can't even get into adb to see what's happening. I didn't expect it to work but I hoped for it to at least get into some kind of upside down mode showing something.

0

Share this post


Link to post
Share on other sites

Posted · Report post

Tell me more. I just failed booting an rather generic AOSP 2.2 that I built. Can't even get into adb to see what's happening. I didn't expect it to work but I hoped for it to at least get into some kind of upside down mode showing something.

codeaurora has support for the 2G VMSPLIT used in the blade kernel. There is an option to set for 2G split in the device config.

With AOSP you need to either use a kernel with a 3G vmsplit (and lose half the ram) or add 2G support. The same for cyanogenmod.

For adb to work you will need /sbin/usbconfig for the kernel version you are using (and include it in the init script).

0

Share this post


Link to post
Share on other sites

Posted · Report post

codeaurora has support for the 2G VMSPLIT used in the blade kernel. There is an option to set for 2G split in the device config.

With AOSP you need to either use a kernel with a 3G vmsplit (and lose half the ram) or add 2G support. The same for cyanogenmod.

For adb to work you will need /sbin/usbconfig for the kernel version you are using (and include it in the init script).

Seems like a good idea to switch to Code Aurora then. I'm using the JJ boot.img so I should have the /sbin/usbconfig in place but I didn't add the USB device id line in build.prop so I suppose it might not work without it.

However with since I'm not using a kernel compiled with 3G vmsplit it's propably the main cause for it not to boot. Oh, well...

Btw, I haven't come that far yet but I suppose I will need to solve the 180 degree rotation issue when/if I get that far. How did you get around that problem? Did you modify PhoneWindowManager.java?

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

..

Edited by rjm2k
0

Share this post


Link to post
Share on other sites

Posted · Report post

Btw, I haven't come that far yet but I suppose I will need to solve the 180 degree rotation issue when/if I get that far. How did you get around that problem? Did you modify PhoneWindowManager.java?

I think it was surfaceflinger

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

From the SDK you can't create a ROM. It is for SOFTWARE (application) development!

You need to download and compile the Android Source code yourself (for that you need Ubuntu x64, read the Android Source page for details).

But, you need a lot of work to build everything right. First of all, setting up the device tree isn't the easiest thing to do.

6.) Compiling Android 2.3.1

To build a final release on a 32bit machine, we must modify some files and use the target option "user" (default is "eng", which is only a debug build for the emulator).

Attention

following code must be run in root of your repo:

source build/envsetup.sh
find . -name '*.mk' | xargs sed -i 's/-m64//g'
export TARGET_BUILD_VARIANT=user
lunch
make[/codebox]

http://forum.xda-developers.com/showpost.p...mp;postcount=10

it is also needed to comment a line in /build/core/main.mk for stop error

$(warning ************************************************** **********)

$(warning You are attempting to build on a 32-bit system.)

$(warning Only 64-bit build environments are supported beyond froyo/2.2.)

$(warning ************************************************** **********)

#$(error stop) <--just add #

Edited by hecatae
0

Share this post


Link to post
Share on other sites

Posted · Report post

6.) Compiling Android 2.3.1

To build a final release on a 32bit machine, we must modify some files and use the target option "user" (default is "eng", which is only a debug build for the emulator).

Attention

following code must be run in root of your repo:

source build/envsetup.sh
find . -name '*.mk' | xargs sed -i 's/-m64//g'
export TARGET_BUILD_VARIANT=user
lunch
make[/codebox]

http://forum.xda-developers.com/showpost.p...mp;postcount=10

I haven't been into this build-stuff too much, so I wasn't looking for a solution (and I'm using x64 Ubuntu any ways :)) that's why I wrote my last info from Cyanogen. That time there were no patch :lol:

0

Share this post


Link to post
Share on other sites

Posted · Report post

I haven't been into this build-stuff too much, so I wasn't looking for a solution (and I'm using x64 Ubuntu any ways :)) that's why I wrote my last info from Cyanogen. That time there were no patch :lol:

just hoping all the people who only have 32 bit cpus realise they can get on board with development.

has anyone released a gingerbread build based on codeaurora yet, want to see if it boots

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.