DREAMteam Froyo source code - G1 General

Hi there,
I'm trying to build some froyo rom for g1 from source. The problem is that lot of stuff lying here is old, unusable slow or hopelessly broken. The only rom that seems to work is hxxp://forum.xda-developers.com/showthread.php?t=1273549
[Rom][2.2.3 AOSP] DREAMteam Froyo v2.0.0 [9/3/2012]
The kernel source can be easy found by Ezterry
hxxps://github.com/ezterry/kernel-biff-testing/tree/ezgb-2636-v1.5.2-20111106
but I can't find any (git) repo or hint how the "DREAMteam" guys built it. :crying:
Thanks in advance for any hints,
ptau

pm the devs
Sent from my HTC Vision using xda premium

All you need for building the kernel is here at this url:
https://github.com/ezterry/manifest-gingerbread-DS/blob/gingerbread/README.mkdn
It used to be on the ezgingerbread rom thread but seems he has a link to the guide which is now on github ^_^
Sent from my GT-I9300 using xda app-developers app

xillius200 said:
All you need for building the kernel is here at this url:
https://github.com/ezterry/manifest-gingerbread-DS/blob/gingerbread/README.mkdn
It used to be on the ezgingerbread rom thread but seems he has a link to the guide which is now on github ^_^
Click to expand...
Click to collapse
Building the kernel for froyo or building the ezgingerbread rom is no problem:
http://forum.xda-developers.com/showthread.php?t=882356
Unfortunately (Ez)gingerbread is an overkill for the tiny G1
My problem is to find out how to build a froyo rom that is not
broken (e.g. cm6). The DREAMteam's
http://forum.xda-developers.com/showthread.php?t=1273549
rom seems to have the most bugs fixed, but again I don't know
how to build it. I need the right android manifest, git repo, etc.
The DREAMteam changelog is astonishingly sparse:
V2.0.0 - 2012-03-09
Update to android 2.2.3. Some changes from 1.9.2 included.
Thanks ptau

ptau said:
Building the kernel for froyo or building the ezgingerbread rom is no problem:
http://forum.xda-developers.com/showthread.php?t=882356
Unfortunately (Ez)gingerbread is an overkill for the tiny G1
My problem is to find out how to build a froyo rom that is not
broken (e.g. cm6). The DREAMteam's
http://forum.xda-developers.com/showthread.php?t=1273549
rom seems to have the most bugs fixed, but again I don't know
how to build it. I need the right android manifest, git repo, etc.
The DREAMteam changelog is astonishingly sparse:
V2.0.0 - 2012-03-09
Update to android 2.2.3. Some changes from 1.9.2 included.
Thanks ptau
Click to expand...
Click to collapse
Well I got in touch with tval aint spoke to him for a while. He said a repo was never made for DREAMteam froyo and the way in which it was created some by pushing files not everything was coding, there was not much point in a repo and he has not got around to it lol and I totally agree with him. So best thing would be to compile a rom from plain AOSP and begin to modify it yourself, this way you learn and better understand rom creation. Plus doing it straight from AOSP will give you the updates you want and in most ways will actually be better ^^ If you want any help I could always introduce you to a few devs see if they would be willing to help ^^
PS: From how you worded your first post it sounded like you were trying to compile just the ezterry kernel xD so I apologise that I misunderstood ^^

99%
xillius200 said:
As far as I remember when it was first started they never had a repository and unless it has changed they still do not lol ill email tvall later lol seems Ldrifta is gone.... :'( if not you can always just compile a normal aosp and then customize it to your liking and speed helps you learn on how to speed up roms that way unlike having an already fast rom of which you learn less from.
Click to expand...
Click to collapse
Thanks. After I looked in the zip, I thought something like that.
Seriously, you don't need speed with this hardware.
Think of cheap, stable, not battery eating
and hackable ARM11 development platform
After that incident with kernel.org they removed all the old android repos
so I have hard times to find the G1 pieces again. ezterry rocks. The kernel
changes are in his git, I could tweak+build the kernel with all the
modules I needed.
Let's see how to get the aosp together ...
(any hints greatly appreciated
PS: From how you worded your first post it sounded like you were trying to compile just the ezterry kernel xD so I apologise that I misunderstood ^^
Click to expand...
Click to collapse
I know, but my German is much better, I swear :angel:

Well.. I'd be happy to help rebuild my rom. Been wanting to set up a repo, but I'm lazy..

tvall said:
Well.. I'd be happy to help rebuild my rom. Been wanting to set up a repo, but I'm lazy..
Click to expand...
Click to collapse
Thanks for the email with tips.
I try to document the building process here:
hxxps://sites.google.com/site/aospdream/
As always, any hints or help from anybody are greatly appreciated ...
Thanks,
ptau

Related

anyone know how to build from aosp?

im trying to learn how to build i am a complete noob to linux but i learn quick already installed ubuntu 11.04 and have jdk 5 already installed for froyo as i would like to make a 100% working froyo build. the repo sync is still running and after that i am installing sdk for linux i just need a starting point to making the roms and kernels into a flashable.zip and other pointers that would be helpful. any advice is welcomed thanks in advance
host Executable: acp (out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/acp)
/usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.5.2/libstdc++.so when searching for -lstdc++
/usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.5.2/libstdc++.a when searching for -lstdc++
/usr/bin/ld: cannot find -lstdc++
collect2: ld returned 1 exit status
make: *** [out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/acp] Error 1
i get this error when trying to "make"
fixed it have to use this sudo apt-get install gcc-multilib g++-multilib zlib1g-dev lib32z1-dev lib32ncurses5-dev gperf
compiling now
skater4690 said:
all the stuff you said...
Click to expand...
Click to collapse
You're trying to build an aosp rom for the vibrant with 2.2 code? You do know there's a reason we don't have a build like that, correct?
The closest aosp 2.2 we got was CM6 partially functioning. Besides, gingerbread is what people want.
Sent from my SGH-T959 using XDA App
geoffcorey said:
You're trying to build an aosp rom for the vibrant with 2.2 code? You do know there's a reason we don't have a build like that, correct?
The closest aosp 2.2 we got was CM6 partially functioning. Besides, gingerbread is what people want.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yes that's what I'm gonna try to do whether everyone wants gb doesn't matter to me I'm doing it for myself and to learn
This is a great reference that got me started. A lot of basics are covered in rom building, and it might answer some questions you don't even know you have yet.
Good luck.
http://forum.androidcentral.com/hacking/6037-general-rom-faq.html
Br1cK'd said:
This is a great reference that got me started. A lot of basics are covered in rom building, and it might answer some questions you don't even know you have yet.
Good luck.
http://forum.androidcentral.com/hacking/6037-general-rom-faq.html
Click to expand...
Click to collapse
Thanks ill take a look at it when I get home I have a 15 page guide lol but ill look through that too never too much info
You might want to start with the CM7 source. Far as I know, that's the most stable code tree you can find for the Vibrant - the raw AOSP code will not work out of the box.
Starting from 2.2 AOSP you won't even know if it's a missing driver, bad compile, bug you introduced, bad build environment, etc when it doesn't work. Start with something that does work, and you can learn and try things out in a more controlled environment.
Saiboogu said:
You might want to start with the CM7 source. Far as I know, that's the most stable code tree you can find for the Vibrant - the raw AOSP code will not work out of the box.
Starting from 2.2 AOSP you won't even know if it's a missing driver, bad compile, bug you introduced, bad build environment, etc when it doesn't work. Start with something that does work, and you can learn and try things out in a more controlled environment.
Click to expand...
Click to collapse
Well I wanted to do a froyo build and I don't think there was much for cm6 on the vibrant
But if you wanna toss me a link for cm6 then ill give that a shot
Side note this is my 666 post lol
skater4690 said:
Well I wanted to do a froyo build and I don't think there was much for cm6 on the vibrant
But if you wanna toss me a link for cm6 then ill give that a shot
Side note this is my 666 post lol
Click to expand...
Click to collapse
I suggested CM7 because it works. Don't think CM6 ever did, very well, so it doesn't really tie in with my suggestion to start from a functional build..
Here's CM7 code checkout and build instructions: http://cmsgs.com/mediawiki/index.php?title=Building_and_Installing_Gingerbread_from_Source_vibrant
I can't find the CM6 code in my quick search, sorry.
Saiboogu said:
I suggested CM7 because it works. Don't think CM6 ever did, very well, so it doesn't really tie in with my suggestion to start from a functional build..
Here's CM7 code checkout and build instructions: http://cmsgs.com/mediawiki/index.php?title=Building_and_Installing_Gingerbread_from_Source_vibrant
I can't find the CM6 code in my quick search, sorry.
Click to expand...
Click to collapse
Its cool Eugene has a nice cm6 rom but its not finished ill ask whoever made a aosp froyo rom for the fascinate for some pointers and cant do gb cause I set my jdk for froyo which uses jdk 5 I'm trying to learn everything all at once lol Linux and building Roms lol I'm familiar with how android works system files and such just needs tobhurry up so I can get out of work and get on doing some things
If you are trying to build a 100% working AOSP ROM for the vibrant you are waiting your time. Without source code for the drivers is not possible. Unless you know somebody that works in the development team in Samsung that can give you access to the source code you are out of luck...If you just want to mess around to learn then go for it...

[SOURCE] Gingerbread sources released by Samsung

Samsung has released sources for Gingerbread update:
https://opensource.samsung.com/reception/reception_main.do?method=reception_search&searchValue=5830
gr8 news... )
Any new stuff over leaked rom?
XDA ♥
Really? By what do you make sure it is gingerbread?
fzn0268 said:
Really? By what do you make sure it is gingerbread?
Click to expand...
Click to collapse
GT-S5570_S5670_S5830_Opensource_GB.zip
It is indeed gingerbread.
Great news! My cygwin setup waiting for this. I have Linux but do something with different way always excited
i've dowloaded it... how do I install this?
plotinus said:
i've dowloaded it... how do I install this?
Click to expand...
Click to collapse
You don't install it, The source code is needed to build a custom kernel, but either enable overclocking or generally tweaking it to improve performance. You need the Android SDK to compile a kernel.
But, can we get the OS from this source or it's just the kernel?
Sent from my GT-S5830B using XDA App
Install Linux eg Ubuntu, down it, build it directly or git AOSP source then build.
My computer is unstable, or I can use it to port CyangenMod. But I have git AOSP source, I might try to build one. However, how to flash the built is a big trouble...
been trying to dowload this for a whole day. each time only got 10kBps speed, and resulting in timeout. also cannot resume. wth samsung????
Went well for me so here's my upload
http://www.multiupload.com/KR566WYN13
Help
Guys,
I have difficulties in understanding the given tutorial by Samsung. Do you any link to more comprehensible tutorial in order to make this update work?
Thank you so much.
Guys wht is this for?
Cant understand about this..im from sourh east asia..
What should i do?
geraldgeron said:
Guys wht is this for?
Cant understand about this..im from sourh east asia..
What should i do?
Click to expand...
Click to collapse
this is the Gingerbread source code for Samsung GT-S5830. It is primarily for those who wants to build custom ROMs.
chinoyray said:
this is the Gingerbread source code for Samsung GT-S5830. It is primarily for those who wants to build custom ROMs.
Click to expand...
Click to collapse
and custom kernels

Ice Cream Source Build?

Hi,
i know that the build would be slow as hell but has anyone compiled ICS for the G1? just for trying it ?
i would like to try it myself but i have no clue on how and from hat i`ve heard my computer would take ages to build it
It's done for droid eris, it can be ported to G1.
http://forum.xda-developers.com/showthread.php?t=1352170
Porting would be inefficient when it can be built from source.
Unfortunately I can't do neither
Sent from my GT-I9100 using XDA App
Ice Cream Sandwich Build Help
As soon as the source was released I was thinking about trying to build it for "old reliable" (my nickname for my old G1). I know it would be slow as mud but I still want to give it a try. Problem is I've never compiled the source of Android before so I would be going in blind. I've read the info at source.android.com so I have somewhere to start. If anyone has any other guides/tutorials on how to build Android for a device then I would be really appreciative. I'm a Computer Science major so don't be afraid to throw a little code at me either. I'll include the details of my phone below in case anyone needs it.
HTC Dream
SPL: HBOOT-1.33.2005 (DangerSPL)
Radio: 2.22.19.261
OS: CyanogenMod 6.1 (Android 2.2.1)
You can have a look at Terry' ezGingerbread thread. Here he explains what to do to compile his ezGingerbread from the sources. Principally compiling ICS is the same, but you need to exchange / modify the manifest to your needs.
Sent from my Gingerbread on Dream using XDA App
Thanks, I looked it up and it was really helpful. Just a couple of quick questions. Do you know how far from stock ezGingerbread is? What do you mean when you say manifest? When people port a new version to a new device how is it normally done?
Thanks for your help. If I manage to get anything useful I'll be sure to share it here first.
Sent from my DROID3 using XDA App
hyperspace290 said:
Thanks, I looked it up and it was really helpful. Just a couple of quick questions. Do you know how far from stock ezGingerbread is? What do you mean when you say manifest? When people port a new version to a new device how is it normally done?
Thanks for your help. If I manage to get anything useful I'll be sure to share it here first.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
It's almost stock, but there are some projects from CM included and some he cloned from CM or from other sites and manages them by himself. Details you can see it in his manifest.xml located in the .repo directory. The manifest defines, what projects are to be included and what branch you want to use for these projects.
You will not want my manifest for ICS (at least unless I make an ICS branch myself)
The reason is you will want to use the ICS git repos and not the GB git repos (original or cloned by me)
That said if you are new to building an android rom look at the structure using ezgb some, and build ezgb, then when you understand the structure clone ICS from aosp (see info on source.android.com) and create your own manifest from that including cloned git repos you need from ezgb with any addtl modifications required.
The first thing is:
* Git is the source control for all parts of android, however many (well over 200) git repos are used in ICS
* Repo is a tool (python script with plugins pulled from its own git repo) for maintaining all of the git repos used in an android build, and creating the true tree of repos needed for the work directoy.
* Manifest is a special git repository with default.xml (and sometimes other manifest xmls) used by the repo script to find all the projects other git repositories, as well as what branch/commit to checkout to the work directory.
Thanks for the advice guys. Glad to see the little G1 is still getting some love. I think I'll start by building ezGingerbread to get the handle on the build process for Android and at least get up to 2.3.
If anyone knows what kinds of modifications are normally needed for a port like this then I would appreciate the help. Is it normally just editing some config files or would I have to dive into the code? Thanks again.
Sent from my DROID3 using XDA App
Looks like someone has beaten me to the punch. Anyone interested shout go have a look at this thread: http://forum.xda-developers.com/showthread.php?p=19648827
not exactly.
that is a port from a source-build for the hero
but very close
looks like the dev is trying to make a source build for the dream.
you could contact him so you can work together
Really get the cm9 source, pull forward the dream/sapphire device trees from cm7 (or firerats port of that) and it ought to be alright.
There seems little in the way of true cm bits at current (sure to change soon) but most of the hardware backwards compatibility patches are alredy in cm9 from the looks of it.. for all I know this is a cm9 build since aosp has no hero device tree out of box.
I was going to reply to that thread but since I'm still considered new I can't post to development threads. I guess I will PM the dev later to let him know I'm interested in helping him out.
Why would you build for another device if the dream has built into AOSP? Doesn't make a whole lot of sense to me unless they flat out took out the board file in ICS but you could easily put it back by pulling it from an earlier revision.
Sent from my DROID3 using XDA App

[ROM: DEV] CM7.2 .35 kernel

Ok, this is just something I have been playing with and thought I would share.
It is CyanogenMod 7.2, as close to stock as I can make it. I have taken a lot from Ezet and some stuff from Forumber.
This is not source based as I do not have a grunty enough system to build CyanogenMod from source.
Most importantly, I have started on a new kernel based on the TomGiordano source here:
https://github.com/TomGiordano/kernel_huawei
My Kernel Source:
https://github.com/PaulMilbank/kernel_huawei/tree/cm7-u8800-35
Will upload my source once I can sort out the sources on my computer. I am doing some mods on Aurora kernel too which I will release at some point.
After a few false starts, I compiled the source with their cyanogenmod_u8800_defconfig and it works pretty well for CM7.2.
I fixed atmel vibration using DZOs aurora commits as a guide.
Probably most broken stuff is defconfig related.
Bugs:
Keypad LED's do not work
Autobrightness does not work
Light sensors do not work- probably the cause of the above problems.
Camera force closes
You tell me
Working:
Wifi works
RIL works
Screen/video drivers work well, screen does not suffer annoying no wakeup for me like other kernels.
Atmel Virtual Key vibration works
You tell me
Get It Here:
http://www.mediafire.com/?b2dc7kdmixvas18
I will try and fix all these bugs, but I would be keen for some help too. I don't have time to be a full time dev.
As always, I am not responsible for any bricks, fires or nuclear wars that come about from installing this rom.
Please, please backup with CWM before flashing this.
Paul
PaulMilbank said:
Ok, this is just something I have been playing with and thought I would share.
It is CyanogenMod 7.2, as close to stock as I can make it. I have taken a lot from Ezet and some stuff from Forumber.
This is not source based as I do not have a grunty enough system to build CyanogenMod from source.
Most importantly, I have started on a new kernel based on the TomGiordano source here:
https://github.com/TomGiordano/kernel_huawei.git
Will upload my source once I can sort out the sources on my computer. I am doing some mods on Aurora kernel too which I will release at some point.
After a few false starts, I compiled the source with their cyanogenmod_u8800_defconfig and it works pretty well for CM7.2.
I fixed atmel vibration using DZOs aurora commits as a guide.
Probably most broken stuff is defconfig related.
Bugs:
Keypad LED's do not work
Autobrightness does not work
Light sensors do not work- probably the cause of the above problems.
Camera force closes
You tell me
Working:
Wifi works
RIL works
Screen/video drivers work well, screen does not suffer annoying no wakeup for me like other kernels.
Atmel Virtual Key vibration works
You tell me
Get It Here:
http://www.mediafire.com/?b2dc7kdmixvas18
I will try and fix all these bugs, but I would be keen for some help too. I don't have time to be a full time dev.
As always, I am not responsible for any bricks, fires or nuclear wars that come about from installing this rom.
Please, please backup with CWM before flashing this.
Paul
Click to expand...
Click to collapse
Camera issue??? Please, any issues but camera
»»Sent From My U8800««
This is just to see if I can get people interested in development. I will try document as much as possible what I do and see if we can get some people interested in building a kernel and getting a really good gingerbread cyanogenmod build out. If this goes nowhere, I will just focus on Aurora kernel and ICS. There are a few things I would like to try and include in Aurora to add some features.
We need good 2.6.35 source and this is a good source with a few small bugs, probably due to the config not being completely right. Hopefully they are minor and easily fixed. We have a lot of kernel development going on around the place and we can learn from commits to make a really good build hopefully.
Will try their 7x30_defconfig to make a kernel for my B528 rom too and see what works.
If you replace the boot.img in this rom with the boot.img in Forumber's latest cm7.2 build, it sould all work and give a 2.6.35 experience close to Ezet's 2.6.32 build. It will likely not be as stable because LEWA kernel on my phone at least, is crap.
PaulMilbank said:
This is just to see if I can get people interested in development. I will try document as much as possible what I do and see if we can get some people interested in building a kernel and getting a really good gingerbread cyanogenmod build out. If this goes nowhere, I will just focus on Aurora kernel and ICS. There are a few things I would like to try and include in Aurora to add some features.
We need good 2.6.35 source and this is a good source with a few small bugs, probably due to the config not being completely right. Hopefully they are minor and easily fixed. We have a lot of kernel development going on around the place and we can learn from commits to make a really good build hopefully.
Will try their 7x30_defconfig to make a kernel for my B528 rom too and see what works.
If you replace the boot.img in this rom with the boot.img in Forumber's latest cm7.2 build, it sould all work and give a 2.6.35 experience close to Ezet's 2.6.32 build. It will likely not be as stable because LEWA kernel on my phone at least, is crap.
Click to expand...
Click to collapse
You can use VictorTeam's source.
forumber2 said:
You can use VictorTeam's source.
Click to expand...
Click to collapse
Do you know where it is, I have not been able to find it. Thanks very much man. Keen top take a look at what they have been doing.
PaulMilbank said:
Do you know where it is, I have not been able to find it. Thanks very much man. Keen top take a look at what they have been doing.
Click to expand...
Click to collapse
They have github group https://github.com/Victor-android
.35 kernel based CM7.2 would be pretty dope to me, especially if tethering works
PaulMilbank said:
Do you know where it is, I have not been able to find it. Thanks very much man. Keen top take a look at what they have been doing.
Click to expand...
Click to collapse
here:https://github.com/Victor-android/kernel_huawei/tree/2.6.35-cm-u8800
Thanks, this will likely take a while longer than I thought it would as I am having trouble getting my sources synced locally and on github. If we can pull together all the sources into a kick ass kernel, we should have a really good CM7.2, I would like a rom with built in tethering too. It will just take some time. Running through DZOs excellent repo with a readymade .config and then making small changes is a lot easier than having to make it all up as we go and sort out sources and configs. Maybe I should not have been so cocky at the start!
PaulMilbank said:
Thanks, this will likely take a while longer than I thought it would as I am having trouble getting my sources synced locally and on github. If we can pull together all the sources into a kick ass kernel, we should have a really good CM7.2, I would like a rom with built in tethering too. It will just take some time. Running through DZOs excellent repo with a readymade .config and then making small changes is a lot easier than having to make it all up as we go and sort out sources and configs. Maybe I should not have been so cocky at the start!
Click to expand...
Click to collapse
Nice to hear that someone's still working on U8800's .35 kernel. Good job so far!
PaulMilbank said:
Thanks, this will likely take a while longer than I thought it would as I am having trouble getting my sources synced locally and on github. If we can pull together all the sources into a kick ass kernel, we should have a really good CM7.2, I would like a rom with built in tethering too. It will just take some time. Running through DZOs excellent repo with a readymade .config and then making small changes is a lot easier than having to make it all up as we go and sort out sources and configs. Maybe I should not have been so cocky at the start!
Click to expand...
Click to collapse
Do you use your vendor files for compiling CM7?
forumber2 said:
Do you use your vendor files for compiling CM7?
Click to expand...
Click to collapse
No, I am just using your and Ezets prebuilt binaries and apk's. I do not have the computer power or skill to build from source!
PaulMilbank said:
No, I am just using your and Ezets prebuilt binaries and apk's. I do not have the computer power or skill to build from source!
Click to expand...
Click to collapse
But you could compile kernel?
Compiling and downloading kernel is much smaller and faster. Also their are a lot of comments and files to follow.
Compiling cyanogenmod from source is a huge download and would take forever to compile on my computer. Plus nobody documents the process well and it us specialized to the phone.
Maybe if I can get a good kernel going, others can build cyanogenmod sources for .35 kernel. It all just takes time.
Sent from my U8800 using xda premium
PaulMilbank said:
Compiling and downloading kernel is much smaller and faster. Also their are a lot of comments and files to follow.
Compiling cyanogenmod from source is a huge download and would take forever to compile on my computer. Plus nobody documents the process well and it us specialized to the phone.
Maybe if I can get a good kernel going, others can build cyanogenmod sources for .35 kernel. It all just takes time.
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
Will you try your luck with cm9/10?
PaulMilbank said:
Compiling and downloading kernel is much smaller and faster. Also their are a lot of comments and files to follow.
Compiling cyanogenmod from source is a huge download and would take forever to compile on my computer. Plus nobody documents the process well and it us specialized to the phone.
Maybe if I can get a good kernel going, others can build cyanogenmod sources for .35 kernel. It all just takes time.
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
if you send vendor files to me,i can compile in my free time
forumber2 said:
if you send vendor files to me,i can compile in my free time
Click to expand...
Click to collapse
Maybe Ezets here:
https://github.com/ezeteze/android_device_huawei_u8800.
Not sure otherwise. I don't have any vendor files sorry.
Use these vendor files: click. I built CM 7.2 yesterday and it works just fine with those vendor files.
Unrealized said:
Use these vendor files: click. I built CM 7.2 yesterday and it works just fine with those vendor files.
Click to expand...
Click to collapse
but in this vendor,GPU can't run fully,has a little lag. If we solve this problem,we can make a good cm7 :good:
forumber2 said:
but in this vendor,GPU can't run fully,has a little lag. If we solve this problem,we can make a good cm7 :good:
Click to expand...
Click to collapse
Guess it has something to with the "new" Adreno drivers. Might do some benchmarking later with the older ones. I haven't really experienced lagging myself though. it's kinda the same as w/ .32 based CM7 (especially when using ADWLauncher)

[DEVELEOPMENT][DISCUSSION]HTC Wildfire Buzz

As we discussed much in my CM10.1 thread I thought to make a discussion thread for further development.I hope this is not against forum rules and if please tell me and I'll change/delete it.
Rules:
-Don't ask noob question like: "How to root,...!"
-Don's spam this thread
-Only use this for development purpose
Now feel free to post everything about development for our HTC Buzz!
for cyanogenmod 10+ look at this ----> http://review.cyanogenmod.org/#/c/12089/2/services/surfaceflinger/SurfaceFlinger.cpp
This is the commit that fixed screenshot, task previews and other openGL es related stuff in ICS
Just found out my cpu is 64-bit, so im installing ubuntu 13.10 64-bit and then syncing up CM10.1 to fix errors with you sasa
Thanks for the link and all the best while fixing bugs.Anyways yesterday my hard disk got broken so all my data is lost so my source is lost!
I need to sync it again now!
I will also begin now and then try to fix the bugs too!
Yeah this thread should be not deleted at all
Also I'm going to install ubuntu for my new laptop, now that I've got my own i can start developing even further more
And I'm going to start helping fixing bugs in cm9
Also i'll try make a new kernal for HTC buzz cm9
Stone. Cold said:
Yeah this thread should be not deleted at all
Also I'm going to install ubuntu for my new laptop, now that I've got my own i can start developing even further more
And I'm going to start helping fixing bugs in cm9
Also i'll try make a new kernal for HTC buzz cm9
Click to expand...
Click to collapse
Kernel development is harder than you think... ive been trying this past week to update the kernel, no lck, i cant find the right sources to base the kernel on:/
faZevoLv said:
Kernel development is harder than you think... ive been trying this past week to update the kernel, no lck, i cant find the right sources to base the kernel on:/
Click to expand...
Click to collapse
How hard exactly? Then in that case, i'll still try. If no luck then
Yes, Kernel Development is harder than compiling ROMs.The first build is a pain.If it boots up it's pretty good.Then only adding the features is over.But if you don't have proper source like for the Buzz(We don't have 3.x Source), you have to search for alternate source.Like me I found a source from LG Optimus Me!
It has same Chipset as our Buzz and is also ARM-V6.So when we use our config of Buzz it should compile and boot up!
found a good kernel source as mentioned by you sasa ----> https://github.com/PecanCM/lge-kernel-pecan/tree/android-msm-3.0-jb
Ill try it after building PAC cm10
faZevoLv said:
found a good kernel source as mentioned by you sasa ----> https://github.com/PecanCM/lge-kernel-pecan/tree/android-msm-3.0-jb
Ill try it after building PAC cm10
Click to expand...
Click to collapse
Thanks!
faZevoLv said:
found a good kernel source as mentioned by you sasa ----> https://github.com/PecanCM/lge-kernel-pecan/tree/android-msm-3.0-jb
Ill try it after building PAC cm10
Click to expand...
Click to collapse
Yes this one I meant.Sorry for not giving the link but thanks that you mentioned.
Building PAC cm10 now!!!!
faZevoLv said:
Building PAC cm10 now!!!!
Click to expand...
Click to collapse
All the best, friend!
Waiting for it.But the name isn't PAC CM10, it's only PAC Jelly Bean
SasaKovacic said:
All the best, friend!
Waiting for it.But the name isn't PAC CM10, it's only PAC Jelly Bean
Click to expand...
Click to collapse
I know, but its based on CM10, that's why I said it
Oh and I used a CM9 patch to fix task previews and other stuff, probably some speedup too!
faZevoLv said:
I know, but its based on CM10, that's why I said it
Oh and I used a CM9 patch to fix task previews and other stuff, probably some speedup too!
Click to expand...
Click to collapse
That's good to know, also all is well and going good?
Stone. Cold said:
That's good to know, also all is well and going good?
Click to expand...
Click to collapse
Yep nearly finished compiling Jellybean 4.1.2 should be ~3 times faster with my patch
faZevoLv said:
Yep nearly finished compiling Jellybean 4.1.2 should be ~3 times faster with my patch
Click to expand...
Click to collapse
Awesome!
Glad to know, also it will be the first ever PAC MAN rom
Thanks jord, everyone must appreciate your work
faZevoLv said:
Building PAC cm10 now!!!!
Click to expand...
Click to collapse
Is not better to make a port ? Is easier no ?
Sent from my HTC Wildfire using xda premium
Pator57 said:
Is not better to make a port ? Is easier no ?
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Porting jelly bean roms is much much much harder than ICS or GB!! They always reboot and bootloop with many errors:/
I built PAC and it boots!!!!!
but paranoid preferences don't work:/ I know how to fix it but ill have to recompile which will take another day:/

Categories

Resources