Related
Hi guys
I want to build an ICS ROM for the htc flyer.
I tried different ics repos on github, but some of them were not complete or gave me compiling errors.
So my question: Does anyone know a working ics repo? (i tried evervolv and the one from lordclockan).
Thx for every tip
Maybe checkout the Cyanogen readme for their ICS branch? https://github.com/CyanogenMod/android/blob/ics/README.mkdn
Basically use repo to get the entire source and you'll be able to build and compile (hopefully fine), just make sure that you have whatever pre-req's are required.
Though, note that you're nto gonna be able to flash that to your device immediately, you're gonna have to get vendor/device files specific to the device.
nickiberli said:
Hi guys
I want to build an ICS ROM for the htc flyer.
I tried different ics repos on github, but some of them were not complete or gave me compiling errors.
So my question: Does anyone know a working ics repo? (i tried evervolv and the one from lordclockan).
Thx for every tip
Click to expand...
Click to collapse
Some don't look complete because they call on other repos as well. They give you compilation errors because you need to configure your device repo to work with ICS source. You can't expect everything to work out of the box. All sources work, its all about getting your device to work with it.
私のEVO 3Dから送信される。
Yeah I know. I also tried to compile it with a device that came with the repo.
I think i configured my device tree that it should compile..
Which ics repo would you take?
Sent from my HTC EVO 3D X515m using xda premium
I compiled well with AOPS one but what's the problem with CM repo? There's port for my device what's based on CM one.
Right, first beta build will come soon, I am working on it.
To do:
Sync CM7 repository [x]
Compile CDMA CM7 with VMSPLIT_3G [x]
Modify Verizon kernel for miui [x - didn't work out so good]
Modified SEMC .145 kernel for MIUI (works with CDMA and GSM) and it boots MIUI (my GSM version of it) but there are a few graphical problems. If I can't solve this, then I will clean out defconfigs using fxp's as a base
Merge CM7 and MIUI into a ROM [not done]
Might need to hack RIL into framework [not done - might not be needed]
How you can help:
Click the thanks button, it will help me work towards getting recognition on xda.
I don't have an R800x, so testing will have to be done by you
CURRENT STATUS
I have successfully booted MIUI (GSM) on a R800x capable kernel, but there are graphical issues such as home screen not loading and other screens not loading. I am looking into a fix for this.
I'd love to have MIUI on my R800x. Greatly appreciated for when you make it happen!
CrimsonKnight13 said:
I'd love to have MIUI on my R800x. Greatly appreciated for when you make it happen!
Click to expand...
Click to collapse
Quick question, do you know where freexperia post there CDMA CM7 kernel source?
But then as the Verizon ROM is true stock, I should be able to make an MIUI kernel easily.
Just looking for an MSM7x30 CDMA with MIUI now.
Will start porting kernel tomorrow.
Sent from my R800i using MIUI
KeiranFTW said:
Quick question, do you know where freexperia post there CDMA CM7 kernel source?
But then as the Verizon ROM is true stock, I should be able to make an MIUI kernel easily.
Just looking for an MSM7x30 CDMA with MIUI now.
Will start porting kernel tomorrow.
Sent from my R800i using MIUI
Click to expand...
Click to collapse
There should be source for stock 2.3.3
But I think FXP has sources on github.
Sent from R800x
Thank-you soo soo much! Ive wanted to try Miui since I got my first android phone, and have never had the chance. In any event, I truly appreciate the effort and moreover the thought.
Sent from my R800x using xda premium
KeiranFTW said:
Quick question, do you know where freexperia post there CDMA CM7 kernel source?
But then as the Verizon ROM is true stock, I should be able to make an MIUI kernel easily.
Just looking for an MSM7x30 CDMA with MIUI now.
Will start porting kernel tomorrow.
Sent from my R800i using MIUI
Click to expand...
Click to collapse
https://github.com/freexperia/semc-kernel-msm7x30/tags
3.0.1.A.0.145.zip — Initial import of SEMC 3.0.1.A.0.145 ZIP TAR.GZ
Click to expand...
Click to collapse
I posted a "bug" about the source not being there & they wound up saying to find it in the tags. I guess the whole semc-kernel-msm7x30 folder might be a fully updated kernel for CDMA & GSM.
Right, that is probably it then.
Just found out how to hack RIL into framework.jar if data does not work.
The only problem I had when porting the semc GSM kernel to MIUI was a few graphical glitches, so I used the freexperia one instead.
Sent from my R800i using MIUI
Hey, hope this works out, Keiran - we can always use another ROM to fool with. I very much anticipate good things here!
KeiranFTW said:
The R800x users seemed a little neglected to me, so I am going to try and port MIUI over to the R800x.
What I need to do:
Port MIUI from over to the R800x from either the desire HD or the Inspire 4G (Inspire has a CDMA radio?) or any other msm7x30 CDMA phone.
Port over stock kernel to MIUI.
Keiran
Sent from my R800i using MIUI
Click to expand...
Click to collapse
You could try the evo shift 4g rom
Evo shift 4g runs similar specs (7x30 @ 1ghz) and is CDMA
If you need help with testing/development, i'm here
paxChristos said:
You could try the evo shift 4g rom
Evo shift 4g runs similar specs (7x30 @ 1ghz) and is CDMA
If you need help with testing/development, i'm here
Click to expand...
Click to collapse
Right, going to try that, just syncing (or attempting to sync) the CM7 repos so I can compile them to be MIUI compatible.
I'm willing to test it out as well.
CrimsonKnight13 said:
I'm willing to test it out as well.
Click to expand...
Click to collapse
Got a few testers then.
Finally! The repo synced!
Now time to set up the build
KeiranFTW said:
Got a few testers then.
Finally! The repo synced!
Now time to set up the build
Click to expand...
Click to collapse
Am also willing to test
Leraeniesh said:
Am also willing to test
Click to expand...
Click to collapse
Okay, got plenty of testers now.
Right, doing a nandroid backup, then going to flash CDMA kernel and rom to set up build environment.
Then going to compile with VMSPLIT_3G
EDIT:
Have flashed CDMA kernel and CDMA CM7 on my R800i, going to set up CM7 build environment for R800x then compile with VMSPLIT_3G
And now I am compiling CyanogenMod with VMSPLIT_3G for the R800x
hoping it does not error out :O
Now, for the kernel
Id like to test also!!!!
If it works can you compile cm9?
Sent from my R800x using XDA App
anyone know how to resolve this error:
make: *** No rule to make target `out/target/product/zeusc/kernel', needed by `out/target/product/zeusc/boot.img'. Stop.
it is stopping me from compiling....
Keiran
I belive it says that there are no building instructions for the kernel.
HearthC0re said:
I belive it says that there are no building instructions for the kernel.
Click to expand...
Click to collapse
Trying to recompile with built in kernel source, will let you know how it goes.
Whoa... seems to work now, fluke of the year imo.
Never compiled with any Unix system, or make for that matter.
Love my Analytic Thought patterns though Oo
Hi there
I'm Chaosz-X, known from some kernel work for the HTC Desire, and my custom ROM, and one of the first people (with Texasice, Sandvold, and Shaky153) to get ICS running on the Desire. Since it wouldn't be a bad idea at all to update the kernels of our devices to 3.0, as that is the recommended version for 4.0.3 of ICS, I decided to work ono that.
I took the Tiamat 8x50 source as a base, and applied all the changes of 2.6.39.4. Once this version is up and running, we should be able to download a brand new version of the kernel as 1 patchset, and apply it within a couple of minutes. And more importantly, it will make the work on porting of drivers (e.g. HWA) easier as our kernel isn't a bottleneck anymore. I just finished uploading the source code of this 2.6.39 kernel, and with a few modifications, it should run on the Nexus One too I think. So here is the link:
http://api2.ge.tt/0/8XflAuC/0/blob/download
The file in the root called 'RENAME THIS TO (DOT)config', you can remove it. It is the .config of the Desire. Instead, copy \arch\arm\config\tiamat_mahimahi_defconfig to the root of the folder, and rename it to .config
Edit the MAKEFILE in the root to redirect to the place of the toolchain. The line that has to be edited for this is:
CROSS_COMPILE ?= arm-eabi-
Get Linaro Toolchain for Android, and replace this arm-eabi- with the location of the Linaro toolchain. Enter the terminal, get root access, and type:
make menuconfig
And press EXIT, and YES to save. Then enter
make -j2 -i (if you have 2 cores, if you have 4, you can try -j4)
And it should compile. It will tell you where it put the WiFi 4329 drivers, and you should find a zImage in /arch/arm/boot/. I never checked how the Nexus One has to be flashed with a new kernel, but this zImage is the one you need to get on your device (pretty sure some people here can take care of this ).
And then, report in this topic how it works, what works and what doesn't, etc. I haven't tried compiling this yet as I don't have my Linux machine here atm, so you may run into errors and it can stop compiling: if so, tell me.
(and make sure you got all the dependencies to build a kernel, if you don't know which one you need, Google it)
Sounds promising. Is everything from desire thread working for N1?
You mean in the kernel? This kernel is based on Tiamat, and that was the one we were using for ICS, and only tethering through USB (natively) and real HWA without hacks wasn't working, and I applied modifications from 2.6.39 source to get the kernel to new standards, so it should work better on ICS. I don't know whether it really fixes the issue, because I haven't tested it yet (don't have a N1 around here, and I don't have a Linux machine with me here atm).
I hope to update it once again to Linux 3.0 kernel in one or two weeks, along with modifications from CodeAurora which got everything running on the DHD too. But for now, this kernel may already fix the issues, but we don't know until we flash 'em
Chaosz-X said:
You mean in the kernel? This kernel is based on Tiamat, and that was the one we were using for ICS, and only tethering through USB (natively) and real HWA without hacks wasn't working, and I applied modifications from 2.6.39 source to get the kernel to new standards, so it should work better on ICS. I don't know whether it really fixes the issue, because I haven't tested it yet (don't have a N1 around here, and I don't have a Linux machine with me here atm).
I hope to update it once again to Linux 3.0 kernel in one or two weeks, along with modifications from CodeAurora which got everything running on the DHD too. But for now, this kernel may already fix the issues, but we don't know until we flash 'em
Click to expand...
Click to collapse
AMAZING news for us N1 owners. We've been waiting for a 3.0 kernel for some time now. True HW Acceleration on ICS ROMs puts a BIG smile on my face!
Great job man.
Sent from my Nexus One using xda premium
Yeah
Now, who wanna try it ?
Sounds very promising, Chaos-X!
What we would need now, however, is for someone to pack this into a boot.img (or flashable zip) for easy installation.
xeloni said:
Now, who wanna try it ?
Click to expand...
Click to collapse
If someone will compile and pack into a flashable zip....I'll test it.
Sent from my Nexus One using xda premium
PHP:
include/linux/types.h:156: error: redefinition of typedef 'dma_addr_t'
/home/zyr3x/android/kernel/222/arch/arm/include/asm/types.h:23: note: previous declaration of 'dma_addr_t' was here
no make
Remove the declaration on line 156 then, seems pretty obvious to me ;p And make sure you're building with -i
this not help, mass errors
This news is great to hear. If I read correctly, hopefully a 3.0 kernel will be on it's way. Finally we will be able to get ICS in full hardware acceleration mode! Long live the N1 and the devs here on XDA!
No luck compiling I assume? :/
Sent from my Nexus One using xda premium
- If you are able to build a zImage, I believe, it is pretty simple to convert it to boot.img. Android provides a host side utility mkbootimg.
- It is build during Android compilation process. It takes the zImage, ram-disk and concatenates them to form boot.img which has a header to identify where kernel starts, where ram-disk starts etc embedded into the boot.img.
Its syntax is:
mkbootimg --kernel <path_of_zImage>/zImage --ramdisk <path_of_ramdisk>
The only thing that needs to be checked is, will the default ramdisk (from any working boot.img) work with new kernel?
From Desire topic:
Think it's almost done... The BCM4329 module caused an error, which took some time to fix, and atm there's an issue in 80211 functionality, and when that's done I think we're pretty close to getting final image
Click to expand...
Click to collapse
Still working on it
This is so exciting, is this all that's standing in the way of full Hardware acceleration?
Well, theoretically no. You could port over all stuff from a 3.0 kernel to a 2.6 kernel regarding HWA, and it could simply work. However, ICS is recommended to work with a 3.0 kernel, and a later version of Android maybe won't even work anymore with a 2.6 kernel, so the earlier we move on to the latest kernel, the better. Even if HWA wouldn't be working in this new build, it certainly will be much easier to fix it, because the entire environment is now ready for a patch for a 3.0 kernel.
Example:
You want the HWA fix from 3.0 in 2.6. You port it (which takes time), and then you see it depends on something else > port that over too. Oh wait, that conflicts with this old snippet of code, fix that...etcetera.
In our new build: the fix is already there and working, or we can simply fix it once, and don't have to worry about 50 other files which got broken dependencies.
BTW, build finished for Desire, uploading it now. If it boots for a Desire, I'm compiling it for the Nexus One too today or tomorrow. Though I will need someone from your community with a CM7 running device, but more info on that coming
Chaosz-X said:
Well, theoretically no. You could port over all stuff from a 3.0 kernel to a 2.6 kernel regarding HWA, and it could simply work. However, ICS is recommended to work with a 3.0 kernel, and a later version of Android maybe won't even work anymore with a 2.6 kernel, so the earlier we move on to the latest kernel, the better. Even if HWA wouldn't be working in this new build, it certainly will be much easier to fix it, because the entire environment is now ready for a patch for a 3.0 kernel.
Example:
You want the HWA fix from 3.0 in 2.6. You port it (which takes time), and then you see it depends on something else > port that over too. Oh wait, that conflicts with this old snippet of code, fix that...etcetera.
In our new build: the fix is already there and working, or we can simply fix it once, and don't have to worry about 50 other files which got broken dependencies.
BTW, build finished for Desire, uploading it now. If it boots for a Desire, I'm compiling it for the Nexus One too today or tomorrow. Though I will need someone from your community with a CM7 running device, but more info on that coming
Click to expand...
Click to collapse
I can try it with MeDroid ICS 4.0.3 V6 if the kernel's theoretically supported.
woozyking said:
I can try it with MeDroid ICS 4.0.3 V6 if the kernel's theoretically supported.
Click to expand...
Click to collapse
Ditto from me.
Sent from my Nexus One using xda premium
theoretically it will work on all devices. In fact, just wait )
i can also test kernel if needed, on any rom suggested by Chaosz-X
Does the galaxy player line have a github repo? I have picked to build an aosp gingerbread rom for an independent study at my school and the rules are that it has to be pure aosp and I figured that building from scratch would be the easiest way because touchwiz is deeply integrated into the software in the device. If I can't do it from the github, does anyone have experience for building aosp?
Sparx639 said:
Does the galaxy player line have a github repo? I have picked to build an aosp gingerbread rom for an independent study at my school and the rules are that it has to be pure aosp and I figured that building from scratch would be the easiest way because touchwiz is deeply integrated into the software in the device. If I can't do it from the github, does anyone have experience for building aosp?
Click to expand...
Click to collapse
which galaxy player ? the 4.0 and the 5.0 have cm9 and cm7 which are essentially aosp so you'll need to contact the developers...look at the development forum to see who they are
Its for the 5.0, the ROM I need to build can not already exist and must be a nexus-like ROM with gapps installed such as the nexus s gingerbread ROM. Nothing more nothing less and everything must work
Sparx639 said:
everything must work
Click to expand...
Click to collapse
that's the problem, the current cm7 rom has some issues and no one is working on them because cm9 is a bigger priority, you should ask gmillz for help as he seems one of the main 5.0 devs at the moment
I just want aosp such as the apex rom for the droid x or something similar, it cant be a cyanogenmod rom because those are already being worked on and I cant use generic ginger because its not mine and its not fully aosp
Try building AOSP from source. Use gmillz's device tree as it is the most stable atm. I'm also working on an experimental device tree which may or may not fix some issues so you could also use that if you want
Sent from my Nexus 7 using XDA Premium HD app
And this is for gingerbread without having cm7 or aokp tweaks?
Sent from my Galaxy Nexus using xda app-developers app
Sparx639 said:
And this is for gingerbread without having cm7 or aokp tweaks?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Oh right sorry. I didn't read your initial post properly. These github repos are for CM9. You can build CM7 pretty easily as it doesn't require any propriety files as hardware acceleration is not usually enabled in GB roms. Sorry for the confusion
I can't do any cyanogenmod Roms, it has to be a nexus like ROM. As in stock 2.3.3 you would find on the nexus s
Sparx639 said:
I can't do any cyanogenmod Roms, it has to be a nexus like ROM. As in stock 2.3.3 you would find on the nexus s
Click to expand...
Click to collapse
In that case try building AOSP gingerbread. I'm fairly certain that there are some instructions from Google on how to do so
Sent from my Nexus 7 using XDA Premium HD app
Thank you, I am really new so I don't completely understand googles directions for building aosp, the part I don't understand is how the kernel and ROM is built after you sync the repos. Don't you need drivers and to link the kernel with the ROM? It just doesn't make sense to me yet
Sent from my Galaxy Nexus using xda app-developers app
Sparx639 said:
Thank you, I am really new so I don't completely understand googles directions for building aosp, the part I don't understand is how the kernel and ROM is built after you sync the repos. Don't you need drivers and to link the kernel with the ROM? It just doesn't make sense to me yet
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Hello,
I want a github for the Galaxy Player 3.6.
Can you help me?
thank you
h2o64 said:
Hello,
I want a github for the Galaxy Player 3.6.
Can you help me?
thank you
Click to expand...
Click to collapse
You have to create the device tree by yourself mate
Sent from my HTC One S using Tapatalk 2
Excuse me in fact i wont to say "i search "
Sent from my YP-GS1 using xda app-developers app
Hello,
I did some research and I discovered that Player 3.6 has the same CPU as:
-Motorola DEFY + (MB526)
-Motorola Droid 2
However, the Defy + a:
- CyanogenMod + CWM: http://forum.xda-developers.com/showthread.php?t=1795647
and
- http://forum.xda-developers.com/showthread.php?t=1566861
And Droid 2: http://www.clockworkmod.com/rommanager/developers/droid2?name=Motorola% 202% 20Droid
Is that this could help to advance the device tree?
thank you
h2o64 said:
Hello,
I did some research and I discovered that Player 3.6 has the same CPU as:
-Motorola DEFY + (MB526)
-Motorola Droid 2
However, the Defy + a:
- CyanogenMod + CWM: http://forum.xda-developers.com/showthread.php?t=1795647
and
- http://forum.xda-developers.com/showthread.php?t=1566861
And Droid 2: http://www.clockworkmod.com/rommanager/developers/droid2?name=Motorola% 202% 20Droid
Is that this could help to advance the device tree?
thank you
Click to expand...
Click to collapse
It would need to have the same board, not only the same CPU, if it does have any other similar hardware then it may help.
Board ?
I saw this :
http://www.glbenchmark.com/phonedet...ro25&D=Samsung+Galaxy+Player&testgroup=system
and
http://www.glbenchmark.com/phonedet...sung+YP-G1+Galaxy+Player+4.0&testgroup=system
--> the Player 3.6 has the same board as the Player 4.0
Intressting ?
Update :
The Player Player 3.6 and 4.0 are almost identical except for the CPU and screen size!
Then the two might be able to help each other out such as graphics drivers/WiFi drivers etc.
Originally Posted by x2kjosh
Hey
So I was able to get the new kernel to build per those directions I posted. It made a bunch of modules too. I'm wondering if with this kernel and the modules it creates if we can port to the CM10 build the EVO 4G lte uses. A thought. It may require further tweaking but it could be a start. I packaged the kernel up with a CM10 HTC ramdisk to make a boot.img file. Ported it to the EVO 4g LTE CM10 ROM and got to the CM Splash screen. I googled the errors I was getting from the logcat and found others had same problems going from ICS to JB so I attempted to add those fixes in but the zip file didnt make correctly
We need help! There has been plenty of talk about aosp but no action! Thanks to mdmower for providing this http://forum.xda-developers.com/showpost.php?p=36523562&postcount=27
Would it be easier to build cm9.1 from source since our latest ota source dropped?
Linch89 said:
Originally Posted by x2kjosh
Hey
So I was able to get the new kernel to build per those directions I posted. It made a bunch of modules too. I'm wondering if with this kernel and the modules it creates if we can port to the CM10 build the EVO 4G lte uses. A thought. It may require further tweaking but it could be a start. I packaged the kernel up with a CM10 HTC ramdisk to make a boot.img file. Ported it to the EVO 4g LTE CM10 ROM and got to the CM Splash screen. I googled the errors I was getting from the logcat and found others had same problems going from ICS to JB so I attempted to add those fixes in but the zip file didnt make correctly
We need help! There has been plenty of talk about aosp but no action! Thanks to mdmower for providing this http://forum.xda-developers.com/showpost.php?p=36523562&postcount=27
Would it be easier to build cm9.1 from source since our latest ota source dropped?
Click to expand...
Click to collapse
If we can find the CM9 source for an HTC MSM8960 based phone, yes, and I'd prefer that first personally...
https://github.com/htc-msm8960
Sent from my Motorola Galaxy s3 using Tapatalk 2
You got a splash screen great ill mix our builds since they are at the same level uf you dont mind
Sent from my ADR6410LVW using xda app-developers app
Josh has it what we're trying to start with is a stable cm9.1 port from another phone the International one x has it same 8960 tree
Anyone want to try and work on this with me?
Yes I want to what do you need I am new but I can learn anything. You need me to and fast
Sent from my ADR6410LVW using xda premium