[Q] Vendor for Froyo AOSP - XPERIA X8 Q&A, Help & Troubleshooting

Hey there,
I want to try myself to build a Froyo AOSP rom, so i'm facing a problem, i need the vendor files.
So, Theres any Vendor source already for Froyo for our device? Or rather, is it possible to use GingerBread vendor from CyanogenMod7 Sources?
Thanks

You could use repo init -u git://github.com/CyanogenMod/android.git -b froyo This should have CM6 vendor.

i want to make a aosp build, and I need the device specific files, android_device_semc_shakira and msm7x27 for our device for froyo
cyannogenmod sources for x8 are only for cm7
Sent from my E15i using Opera

You mean CM AOSP or Google AOSP? ;p
If I were you, I would try with CM7 source.

eagleeyetom said:
You mean CM AOSP or Google AOSP? ;p
If I were you, I would try with CM7 source.
Click to expand...
Click to collapse
man,
For our device there is cyanogenmod official sources only for CM7
I had the Cm7 source and i built one time just to see how it works, and i flashed into x8 and blabla.
But there isn't Cyanogenmod official sources for Cm6 froyo.
And there isn't also any Google AOSP sources (i think, that's why i'm opening this thread) for Froyo. So i'm asking if any dev have sources for this, or, rather, sources for CM6 that i can use to build Google AOSP ROM

anyone?
please, i want somebody to give me some "directions"
anything, please

Related

[Q] I9000 Eclair source code

For school project, I need to build from source on eclair (NOT Froyo) and run on I9000.
Does anyone had repo that builds eclair for Galaxy S? I already had eclair source from android.com and got all environment setup. This version lack of hw drivers, so ng for any demo.
Thanks in advance for any help.
http://opensource.samsung.com/
Kernel sources there and its only 'open source' package available for i9000.
I think you should grab this:
GT-I9000_eclair_update.tar.gz
and this:
GT-I9000_eclair_update.tar.gz, since this is a patch for latest Eclair firmwares.
Those sources are also mirrored on voodoo github:
https://github.com/project-voodoo
If you want to build 'all' from scratch -> like Android for i9000, its probably bad news for ya: its not easy and some people are trying to do it for 2 months+ (Cyanogenmod)

[Q] why do ,,primehd and gingerdx cooperate??

it would be nice if primehd and gdx combine i mean a devs of that rom to make a rom for stock ....
sorry for the bad english
kind regards pls just want to share
Gingerdx is alredy for stock!
Sent from my E15i using xda premium
PrimeHD is for stock too!
that's the point dude both do have stock incompatibilities and originated to doxah I mean primehd use the gdx doxah work setting..
Maybe he means combined-ultra-super-rom for stock.
rezzen25 said:
that's the point dude both do have stock incompatibilities and originated to doxah I mean primehd use the gdx doxah work setting..
Click to expand...
Click to collapse
compatibilities i mean
lokibg said:
Maybe he means combined-ultra-super-rom for stock.
Click to expand...
Click to collapse
yes thats the main point ,,,,cause the both do have same goal to make a clean lightweight rom its just to make a fast improvement for our x8 or w8
Prime hd uses shakira source, while gdx is built from hero....
Sent from my E15i using Tapatalk
soumyasree said:
Prime hd uses shakira source, while gdx is built from hero....
Sent from my E15i using Tapatalk
Click to expand...
Click to collapse
no im not ,, talking about the source but the benefits of what stock rom can achieve if both developers on both side combine! a great rom .,,,
rezzen25 said:
no im not ,, talking about the source but the benefits of what stock rom can achieve if both developers on both side combine! a great rom .,,,
Click to expand...
Click to collapse
But you should actually talk "source" as that's the major difference at hand ...
HAKA's PrimeHD (for Stock Kernel) bases upon MiniCM7 while GingerDX, as laid out above, is based on the CM7 HTC Hero source combined with racht's hackDROID as the ROM's base.
HAKA, as he's a developer building from source, already got my permission to use whatever parts of GingerDX he likes to use, and as you can see he actually uses parts of the Cyanogenmod settings package in his stock kernel PrimeHD ROM.
However, since I think it's good, and only benefits the user base, to have a choice of different ROMs NOT being based on the same sources I don't see why we should produce yet another MiniCM7 fork (there are already countless mCM7 knock-offs from an army of c/p "devs") or merge into a single ROM.
In short: each one of us follows his own goal, and GingerDX is only one of three Gingerbread ROMs that are based on a unique platform ... like ... PrimeHD is based on MiniCM7, KuyaDROID spin-offs are based on the HTC Legend sources, and ours is based on the HTC Hero sources. Again: Choice and variety.
B.Jay said:
But you should actually talk "source" as that's the major difference at hand ...
HAKA's PrimeHD (for Stock Kernel) bases upon MiniCM7 while GingerDX, as laid out above, is based on the CM7 HTC Hero source combined with racht's hackDROID as the ROM's base.
HAKA, as he's a developer building from source, already got my permission to use whatever parts of GingerDX he likes to use, and as you can see he actually uses parts of the Cyanogenmod settings package in his stock kernel PrimeHD ROM.
However, since I think it's good, and only benefits the user base, to have a choice of different ROMs NOT being based on the same sources I don't see why we should produce yet another MiniCM7 fork (there are already countless mCM7 knock-offs from an army of c/p "devs") or merge into a single ROM.
In short: each one of us follows his own goal, and GingerDX is only one of three Gingerbread ROMs that are based on a unique platform ... like ... PrimeHD is based on MiniCM7, KuyaDROID spin-offs are based on the HTC Legend sources, and ours is based on the HTC Hero sources. Again: Choice and variety.
Click to expand...
Click to collapse
I totally agree with you B.Jay
Sent from my X8 using XDA
since Bjay reply about it,, then the q&a is done haha ,,,its my first post in xda so Thank you for the comments,, Cause I'm a big fan of gDX and prime so i just wrote about a suggestion that I hope to happen XD
cause I cant unlock my BL so I have my Gratitude for the devs who continue the development of roms on stock Thank man

[Q] CM9 on stock kernel?

Realy sorry for my noob question, I have a locked bootloader
I was researching a bit about the ICS for xperia x8, seeing that only custom roms based on AVD run on stock kernel, because the AVD is based on the same kernel version.
But, isn't possible to adapt the CM9 to run on stock kernel?
Why the CM9 don't have support for X8 on Cyanogenmod website? How developers made Roms based on it?
Moreover, why all the custom kernels are based on version 2.6.29.6? It is impossible or unnecessary to create a custom kernel based on 2.6.32 or up?
Sorry for my bad English.
So ics can't run on stock kernel.Stock kernel miss a lot of components from 3.0 kernel.The kernel is 2.6.29.6 but to have 2.6.32 need to port a lot of stuff so this mean need a lot of time.The nAa kernel's and alfs' kernel is pathed to 2.6.29.6 For now we have ported some components from 32,35,38 and 3.0 kernels.
We do have ics for stock but it is not for daily use. And the development has stopped so don't expect updates/fixes.
As naa said, stock kernel really can't support ics.
Sent from my rooted tomato using xda app
yes ics or jb on stock kernel is impossible and trying to port it is pointless.
We have ics for stock kernel, but gods sake its laggy, buggy. Its not good for daily use. U can find roms like ics. X8 is now old. But u can unlock bootloader by paid method. Next time please search.
Really thanks for your answers.
Interesting, I did not know that the custom kernels had several other superior features.
Actually run on ICS stock kernel is impossible, but there is very buggy roms projects based on avd can i run. What I was wondering is whether it is possible to install the CM9 on stock kernel. I do not think it was just out of curiosity noob ... :laugh:
jucazastrow said:
Really thanks for your answers.
Interesting, I did not know that the custom kernels had several other superior features.
Actually run on ICS stock kernel is impossible, but there is very buggy roms projects based on avd can i run. What I was wondering is whether it is possible to install the CM9 on stock kernel. I do not think it was just out of curiosity noob ... :laugh:
Click to expand...
Click to collapse
Yeah. Its possible, check in development section.
Sent from my X8 using Tapatalk 2
I've tried the only two ics roms for the x8 stock kernel, and I know it's possible to INSTALL, but did not to use, because there are more bugs than fixes.
My doubt is if I can INSTALL CM9 in stock kernel, since I tested these roms are pure android, not CyanogenMod, they are based in AVD, android debug bridge. :fingers-crossed:

[Q] How to make my custom rom support nAa 14 kernel

Guys I have made a custom rom based on CM7.nAa 14 kernel is compatible with CM7.But I want my custom rom also to support it.http://forum.xda-developers.com/images/smilies/crying.gifI have downloaded the .ftf kernel file and I have also extracted it.What changes do I have to do in my rom to make my rom work with the kernel?
Please give a detailed answer.
@OP
Well kudos to you for finding the right section. And what CM7 ROM exactly have you based your ROM on?
It already started working.But thanks for you trying to help.
What I want to know is that there is no networking in my rom.
Please help me fix it.I am talking about a custom rom developed by me based on cm 7.1.
What CM7.1 ROM have you based this on? I'm asking whether you have based your work on any existing ROM or not and the name of that ROM. If that ROM supports nAa-14 kernel, then your ROM will support nAa-14 kernel too.
My rom is supporting the nAa 14 kernel,I have tested it I have a bug in the network. It has no network at the moment. Do you know a fix for this bug ? I am running a rom that is developed by me and I am now testing it.
I haven't released the from here yet.
Sent from my X8 using xda app-developers app
Network bug? I don't even know if logcats can be used to debug. Can you try re-flashing the kernel and the ROM?
Basically you not need to change anything in the kernel. You need change the userspace drivers in the rom to match with the kernel level drivers. Both active x8 gb kernel (nAa and alfs) use similar drivers, except the proximity sensor (nAa use a modded one, alfs use the stock driver), you can use both with the correct libsensorservice and hw libs. And not 100% sure, but nAa use the older kgsl driver (1.1) alfs use newer (1.2), need to change the driver in the rom (libgsl.so).
To solve the network errors, you need to check the RIL related binaries and settings. Better if you give more detailed infos your base rom, the "cm7.1 rom" is not enough. CM7 but the origins? CM7 exists on thousands of phones. Better if you use x8 rom, or rom from a phone what use same hardware (msm7x27 like lg p500, galaxy mini, htc legend, etc...)
Sent from my E15i using xda app-developers app
What more should I add to"cm 7.1"? Please make it clear. Its downloaded from the cyanogen mod download center. It is used as my base rom. I modded it with certain tweaks and replaced many apps and also added many other mods
Sent from my X8 using xda app-developers app
You could have said that it was downloaded directly from cyanogenmod.com for a start. It's pretty confusing when you say just CM7.1 because there are hundreds of CM7.1 ROMs lying around the Development forum, some for stock kernel, some for nAa-gb and others for alfs-gb.
Let me give you a tip if you're just adding tweaks and other mods, and not modifying it on a large scale. Instead of releasing a ROM, why not release a flashable-zip that will make required changes to the existing ROM that users are on. It will be unique and if you want, I can help you with it.
Summary: Why waste time releasing a ROM (~80MB) when you can release a flashable-zip (~10-15MB)?
Cheers.
sgt. meow
I just asked what is your base rom because we not have official cyanogenmod support. If you use only the cm repo to build a complete rom, it will be really hard, due the missing device specific parts. So, the question again (I hope it is clear): you use only the cm repo as base OR use unofficial cm repo from nAa (with working device specific settings/codes) OR use prebuild cm7.1 rom from x8 OR use prebuild cm7.1 rom from other phone. All options is a cm7.1 rom, but all need different works.
From the best to the worst:
1. Use the minicm repo from nAa (nothing to do to get fully working rom)
2. Use prebuilt x8 rom as base (basically not need to do anything)
3. Use the official cm repo (need lot of work because missing a lot of thing)
4. Use any non x8 prebuilt rom (basically the hardest way, need large amount of work with hw related things)
Sent from my E15i using xda app-developers app
@pilu1978
We used to have official CM support till CM7.2 (I guess). It's stated in the CM Shakira page. And you can build CM7 from source as EET has explained in his tutorial. But in any case his best option (if he's going to compile from source) is to use MiniCM7 repo. It's the most updated one.
Plus it will support nAa-14 without any modifications.
The OP wrote this is cm7.1, not 7.2 As I know the official cm7 support is not complete, but my knowledge is NOT unlimited And we not have cm kernel.
Sent from my E15i using xda app-developers app
pilu1978 said:
I just asked what is your base rom because we not have official cyanogenmod support. If you use only the cm repo to build a complete rom, it will be really hard, due the missing device specific parts. So, the question again (I hope it is clear): you use only the cm repo as base OR use unofficial cm repo from nAa (with working device specific settings/codes) OR use prebuild cm7.1 rom from x8 OR use prebuild cm7.1 rom from other phone. All options is a cm7.1 rom, but all need different works.
From the best to the worst:
1. Use the minicm repo from nAa (nothing to do to get fully working rom)
2. Use prebuilt x8 rom as base (basically not need to do anything)
3. Use the official cm repo (need lot of work because missing a lot of thing)
4. Use any non x8 prebuilt rom (basically the hardest way, need large amount of work with hw related things)
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
I am using a prebuild x8 rom and modding it
And what is the original rom, what you use as base rom? If it is a stock kernel based rom, you need to change the drivers (sensors, gsl, egl, etc) to work with nAa kernels, if it is a minicm based rom, nothing need to do it will work with nAa kernel.
Sent from my E15i using xda app-developers app
I think he got over that problem by now. LOL.
No man its not working.
See I will explain my question once more. I am using this rom as my base rom: http://download.cyanogenmod.org/?type=stable&device=shakira
I want to make this rom compatible with custom kernels like nAa 14 and alfs etc so what should I do exactly?
If I have to change my drivers then please explain to me how to change my driver to these kernels and also tell me where to find the driver files in the rom and also tell me the download link for the drivers please.
I will be very grateful!
THANKS in advance. Please someone help me.

[Q] CM Kernel?

The question probably doesn't belong here but unfortunately I couldn't find what I wanted to know elsewhere. I've seen that there is a CM port kernel in the kernel list but what does a CM port kernel actually do? Can you install Cyanogenmod ROM with it? Sorry for the basic question but it would very nice if somebody could help me out here!
The kernal fixes some problems in the Roms is what I read? I'm not sure if you can install it with or without it.
You can use the kernel, if you have installed the T700 cm-11.0 build from eousphoros:
http://forum.xda-developers.com/galaxy-tab-s/orig-development/unofficial-cyanogenmod-11-android-4-4-4-t2835170
BG, Nvertigo
Thanks guys!
So I need to flash the ROM first and then the Kernel?
Yes. You will also need to root again the rom isn't rooted.
45 - Alba gu brĂ¡th

Categories

Resources