Root [Discussion - Developers _ONLY_] Building ICS from source (Isaac's github).

[isaacj87]

Ya i noticed that my bad.



EDIT: well its building pretty good so far im making a nandroid of my miui.

Also while your here I have a question when using a boot image to install a freshly built kernel what module is needed for the wifi?
Sometimes when i try a few little things in a kernel one cant turn the wifi on.

The WIFI modules are already being packed into the userspace. They are here: https://github.com/ikarosdev/android_device_motorola_triumph/tree/ics/modules

Anything with "libra" in the name. I'd need to see the error as to why the WIFI can't turn on.

 

[konspiracy]

The WIFI modules are already being packed into the userspace. They are here: https://github.com/ikarosdev/android_device_motorola_triumph/tree/ics/modules

Anything with "libra" in the name. I'd need to see the error as to why the WIFI can't turn on.

Okay I will have to build the kernel, but thats for another day.

Also I just passed target DEX settingsprovider so im getting close to finishing.

creating filesystem

Build completed. copying over.
It boot looped im trying to find and error

rename the .doc to .txt the file was to big for a .txt

 

[isaacj87]

Okay I will have to build the kernel, but thats for another day.

Also I just passed target DEX settingsprovider so im getting close to finishing.

creating filesystem

Build completed. copying over.
It boot looped im trying to find and error

rename the .doc to .txt the file was to big for a .txt

Alright, I'll have a new kernel for you to try in a little bit.

 

[konspiracy]

Alright, I'll have a new kernel for you to try in a little bit.

Ya I can test things for you but I wont be able to build I will be leaving my computer.
So just upload wherever and I can try again.
Also I wish it was easier to set up a desktop sharing program through ubuntu without having to set up a ssh server. Although I am happy with the progress of gnome shell, I can even use themes and stuff. Its still not as usable as a workstation.

 

[isaacj87]

Ya I can test things for you but I wont be able to build I will be leaving my computer.
So just upload wherever and I can try again.
Also I wish it was easier to set up a desktop sharing program through ubuntu without having to set up a ssh server. Although I am happy with the progress of gnome shell, I can even use themes and stuff. Its still not as usable as a workstation.

Yeah, I like gnome-shell, but can't use it as a workstation. I use Unity/Ubuntu 11.10 on my recreational laptop, but wouldn't dare use it for development. I stick to Xubuntu/XFCE because it's lightweight and no-frills.

 

[FroyoShark]

Hey Isaac, would it be possible for you to make a flashable zip?

 

[isaacj87]

Alright, here it is...

I've done some experimental stuff that I haven't found another 2.6.32.9 kernel to do. Since HW3D wasn't a big deal in Froyo, it was never really added to the 2.6.32 kernel series. I went ahead and added it to our kernel. I turned off mmu page faulting which should hopefully shut up kgsl bitching about faulting on unmapped regions.

Link: https://github.com/downloads/ikarosdev/triumph-kernel-msm7x30/zImage.zip

Relevant commit: https://github.com/ikarosdev/triumph-kernel-msm7x30/commit/5d1eb20b613a3b29b27d04662423851ca20b4e40

 

[isaacj87]

Hey Isaac, would it be possible for you to make a flashable zip?

If I had something to share, I would share it. This isn't a ROM thread. This is a thread about building ICS.

 

[rb64]

Alright, here it is...

I've done some experimental stuff that I haven't found another 2.6.32.9 kernel to do. Since HW3D wasn't a big deal in Froyo, it was never really added to the 2.6.32 kernel series. I went ahead and added it to our kernel. I turned off mmu page faulting which should hopefully shut up kgsl bitching about faulting on unmapped regions.

Link: https://github.com/downloads/ikarosdev/triumph-kernel-msm7x30/zImage.zip

Relevant commit: https://github.com/ikarosdev/triumph-kernel-msm7x30/commit/5d1eb20b613a3b29b27d04662423851ca20b4e40

Can I just unzip the zImage.zip file, copy it as
device/motorola/triumph/kernel, and then do another "brunch triumph"
to package it all up? Or what is the easiest way to get the kernel on the phone?

 

[konspiracy]

Alright, here it is...

I've done some experimental stuff that I haven't found another 2.6.32.9 kernel to do. Since HW3D wasn't a big deal in Froyo, it was never really added to the 2.6.32 kernel series. I went ahead and added it to our kernel. I turned off mmu page faulting which should hopefully shut up kgsl bitching about faulting on unmapped regions.

Link: https://github.com/downloads/ikarosdev/triumph-kernel-msm7x30/zImage.zip

Relevant commit: https://github.com/ikarosdev/triumph-kernel-msm7x30/commit/5d1eb20b613a3b29b27d04662423851ca20b4e40

Alright im ziping it up to another zimage kernel installer i hope i dont need to package it as a boot.img?

Alright I did a fresh install of my last build and installed the kernel with the any kernel extractor and it still is boot looping. My gf family doesnt have adb on there comp so I cant tell you the error messages. Mantera will have to get them for ya.

 

[spdlmt150]

After a few failed build attempts, my poor old Dell 700m let out a mushroom cloud. Picked up a new laptop this evening and am picking up a ssd to set up dual boot tomorrow. If all goes as I'm figuring, a flashable zip will appear right about the time I get everything up & running!

 

[ziggy46]

After a few failed build attempts, my poor old Dell 700m let out a mushroom cloud.

lol thats about what happened to my old thinkpad t42

 

[progmanos]

Has anyone else encountered this problem? I get a blank screen, and then the system reboots.

I/InputReader( 160): Device added: id=10, name='fbx_kybd', sources=0x00000101
I/InputReader( 160): Touch device 'bi041p' could not query the properties of its associated display 0. The device will be inoperable until the display size becomes available.
I/InputReader( 160): Device added: id=9, name='bi041p', sources=0x00001103
I/InputReader( 160): Device added: id=4, name='fih_ringswitch', sources=0x00000101
I/InputReader( 160): Device added: id=3, name='7k_handset', sources=0x80000101
I/bluedroid( 160): Starting hciattach daemon
I/bluedroid( 160): bt_enable: ret: -1, errno: 19
W/ResourceType( 160): Failure getting entry for 0x7f060000 (t=5 e=0) in package 0 (error -75)
I/SystemServer( 160): Accessibility Manager
I/InputReader( 160): Reconfiguring input devices. changes=0x00000004
I/InputReader( 160): Device reconfigured: id=9, name='bi041p', surface size is now 480x800, mode is 1
I/ActivityManager( 160): Config changed: {1.0 0mcc0mnc en_US layoutdir=0 sw320dp w320dp h460dp nrml port ?uimode ?night finger -keyb/v/h -nav/h s.2}
D/PermissionCache( 93): checking android.permission.ACCESS_SURFACE_FLINGER for uid=1000 => granted (335 us)
D/dalvikvm( 160): DexOpt: incorrect opt magic number (0xff ff ff ff)
I/PackageManager( 160): Running dexopt on: com.android.systemui
I/bluedroid( 160): bt_enable: ret: -1, errno: 19

 

[progmanos]

So you mean there might be ICS on the Triumph that we can flash?

You can flash it, but the touchscreen driver doesn't work at the moment. So you will only get a blank screen.

 

[agentc13]

So you mean there might be ICS on the Triumph that we can flash?

If you want to build it from source. Nothing is going to be released until it gets to where most things work and people won't be complaining about bugs. There seems to be a number of issues for people that have a good concept of what they are doing, making a flashable zip for people that don't know this would just lead to a ton of issues that are not necessary at this point in time.

 

[konspiracy]

You can flash it, but the touchscreen driver doesn't work at the moment. So you will only get a blank screen.
img, #cubbies-overlay{ -moz-transition-property: margin, box-shadow, z-index; -moz-transition-duration: 0.1s; -webkit-transition-property: margin, box-shadow, z-index; -webkit-transition-duration: 0.1s; } .cubbies-selected{ z-index: 9999; box-shadow: 3px 3px 8px -1px blue !important; cursor: pointer !important; margin: -3px 3px 3px -3px; } .cubbies-selected:active{ box-shadow: 2px 2px 5px -1px darkblue !important; margin: -1px 1px 1px -1px; } #cubbies-overlay{ position: fixed; z-index: 9999; bottom: 30px; left: 30px; box-shadow: 0 2px 3px rgba(0,0,0,0.8); border: none; } #cubbies-overlay:hover{ box-shadow: 0 2px 3px rgb(0,0,0); }

The touch screen driver works fine?
we are working on hardware acceleration. have had 3 different builds with awesome touch response.
So in other word your doing it wrong.

 

[progmanos]

The touch screen driver works fine?
we are working on hardware acceleration. have had 3 different builds with awesome touch response.
So in other word your doing it wrong.

Interesting. I grabbed a fresh copy of the build files today. I've been doing exactly the same thing before I encountered this problem. I'm not sure what's wrong, but I'll figure it out.

 

[EarlyMon]

In an effort to hopefully cut down on non-compliant posts, I've changed the thread title.

And I'm sorry to even post this much here, just letting you all know to PM me if I did it wrong.

 

[lifeblows10]

Anyone know why I am getting this build error?

device/motorola/triumph/overlay/packages/apps/Camera/res/values/config.xml:27: error: Resource at ffc_supportedEffects appears in overlay but not in the base package; use <add-resource> to add.
make: *** [out/target/common/obj/APPS/Camera_intermediates/src/R.stamp] Error 1
make: *** Waiting for unfinished jobs....

 

[RedAnt]

I ran the script with the full path like shown on post #2, and it failed. Here's a quick change that makes it work when run from any directory (like the post implies). The full script is simpler than the diff would be.

( 
cd  `dirname $0`
mkdir -p proprietary
# Get ROM Manager
curl -L -o ./proprietary/RomManager.apk -O -L [url]http://download.clockworkmod.com/re[/url]
coveries/RomManager.apk

# Get Android Terminal Emulator (we use a prebuilt so it can update from the Mark
et)
curl -L -o ./proprietary/Term.apk -O -L [url]https://github.com/downloads/jackpal/Andr[/url]
oid-Terminal-Emulator/Term.apk
unzip -o -d ./proprietary proprietary/Term.apk lib/armeabi/libjackpal-androidterm
3.so
)

It shouldn't have any side effects. It works on bash, and it should be fine on any sh shell.

Please let me know if there was a better way to submit this back.

 

[isaacj87]

You can flash it, but the touchscreen driver doesn't work at the moment. So you will only get a blank screen.

Touchscreen != GPU drivers. I've had the touchscreen driver working well before I even started building ICS from source.

I have a new kernel for you guys to test in a little while. I'm going to try and backport some stuff from a msm7x30 "gingerbread" kernel.

 

[Whyzor]

Touchscreen != GPU drivers. I've had the touchscreen driver working well before I even started building ICS from source.

I have a new kernel for you guys to test in a little while. I'm going to try and backport some stuff from a msm7x30 "gingerbread" kernel.

Thanks Isaac, say while you're in there looking at touchscreen kernel code, can you keep an eye out for why sometimes touchs are ignored, & other times it's perfectly smooth, sensitivity is great. I have a poll in this thread, and it seems pretty widespread problem.

I have a couple of theories:

1) Android is doing some stuff that just ignores or throws away touch interrupts

2) The screen is too sensitive in registering nearby pixels, so a slight movement on a touch is registered as a swipe instead of a point release (like sometimes when a keyboard key press registers as a nearby key press). But some apps require a swipe to have a minimum length before it registers, so it ends up being in an "unrecognized touch event".

 

[RedAnt]

Anyone know why I am getting this build error?

device/motorola/triumph/overlay/packages/apps/Camera/res/values/config.xml:27: error: Resource at ffc_supportedEffects appears in overlay but not in the base package; use <add-resource> to add.
make: *** [out/target/common/obj/APPS/Camera_intermediates/src/R.stamp] Error 1
make: *** Waiting for unfinished jobs....

I have the same error in my build. I suspect they might be moving targets? I'll try another synce later tonight and see if the issue goes away.


I'm really just trying to get things setup so that I can really spend some time next week. I know that there are going to be a lot of hours spent tracking down how all this stuff works. My goal is to be able to build to the point of being able to test both cm7 and cm9 by the time my new system shows up next week.

I suppose it's hard to know what each others skills are, but if we had some sort of todo list perhaps be we could focus on different areas?

I have not tested my cm7 ROM yet, or completed a ics build, but I think I have captured what was needed to do both of these on FedoraCore14. When my new system comes in next week I'll be redoing it all on FC16. After I have tested that I can build functional ROM images, I'll post the setup environment for Fedora. If anyone is waiting, let me know.

 

[NateMckn]

Hey Isaac,

First of all, thank you for everything you've done for this phone and this community. I really appreciate the work and I'll be throwing you a donation sometime after the Christmas expenses settle.

Look back at the road to ICS thread, I saw that you got the radio partially working, but it doesn't look like anyone who has built from your github (myself included) got a working radio. Any idea what happened to that? Were the changes not pushed or did somthing new break it?

A working radio (even partially) would be a huge step towards a usable ROM.

 

[lifeblows10]

I have the same error in my build. I suspect they might be moving targets? I'll try another sync later tonight and see if the issue goes away.

I am just about to do a sync/build. Hopefully I can get through one. (With out error.) Let me know how yours goes. (Or if anyone else has something to share...)