Root Where are all the devs at?

[death2all110]

yeah i emailed them directly and got:

[FONT=&quot]We are very sorry to hear that you’ve been trouble with problem.[/FONT]
[FONT=&quot]Could you give us build error log you faced to check it. [/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]We hope this information will help you. [/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]Thank you.[/FONT]

 

[tdm]

I just got AOKP 4.1 built but I ran into a strange issue. Any devs want to try to figure this out?

There's an error building audio.primary.goldfish due to custom Qualcomm stuff (header mismatch, which causes failure to instantiate an object due to pure virtual function).

In the CM10 build, audio.primary.goldfish is not built at all. I've even added junk to the top of device/generic/goldfish/audio/Android.mk to cause a build failure and there's no failure, so obviously this file is not even read.

I diff'd build/ and vendor/ in the two trees and nothing obvious stands out.

Why would AOKP 4.1 be building this module?

I've searched all over the code and can't find any reasonable explanation. It's an optional module and nothing seems to depend on it.

For now I just nuked device/generic/goldfish/audio. But that's not a satisfactory solution.

 

[tdm]

Found it. rmcc added an Android.mk to device/generic/goldfish and another in development/tools/emulator/system that blocks building these components.

 

[tdm]

So now I have both CM10 and AOKP41 builds. Next is to fire them up and see how badly they crash and burn....

 

[Lykarsis]

So now I have both CM10 and AOKP41 builds. Next is to fire them up and see how badly they crash and burn....

Good luck, be happy to give them a try when you're comfortable posting them

 

[ortrigger]

Good luck, be happy to give them a try when you're comfortable posting them

Same here. Even if they're super alpha and nothing works, it would be cool to see jb on my spec.

 

[azoller1]

Thanks so much tdm for stickin around to make this! Maybe someone will make an aosp build in the future

 

[admn81]

So now I have both CM10 and AOKP41 builds. Next is to fire them up and see how badly they crash and burn....

Thats badass tdm!!! This is exactly we never want you to leave Spectrum land lol. Wish I could help you more , but I guess I can provide encouragement..lol

 

[tdm]

So now I have both CM10 and AOKP41 builds. Next is to fire them up and see how badly they crash and burn....

Round 1 results for CM10:

D/libEGL ( 560): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 560): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 560): loaded /system/lib/egl/libGLESv2_adreno200.so
I/Adreno200-EGLSUB( 560): <ConfigWindowMatch:2078>: Format RGBA_8888.
I/Adreno ( 560): ioctl_kgsl_context_create_priority: not implemented
E/Adreno200-EGL( 560): <qeglDrvAPI_eglCreateContext:2266>: EGL_BAD_ALLOC
E/libEGL ( 560): eglMakeCurrent:495 error 3009 (EGL_BAD_MATCH)
E/SurfaceFlinger( 560): Couldn't create a working GLES context. check logs. exiting...

Round 2 coming up soon...

 

[tdm]

Headsup for CM 10.1 on the Spectrum, Nitro, etc.: BOARD_RAMDISK_ADDR is deprecated.

https://github.com/CyanogenMod/android_build/commit/26f1b2ba4618de170e2577db3bbf0391ffa30566

 

[tdm]

Round 2 results:

Got CM10 to boot, but it's definitely not happy yet.

The screen is flashing between normal and some weird magnified/overlapped thing about once per second.

The radio is not available.

Wifi is not working.

 

[tdm]

do have any plans for this kernel? like OC'ing or voltage control some added governers or schedulers?

Clocking looks very similar to the MSM 7x27 SoC (which I have some experience with). I might play with OC a little. Two cores means twice the probability of failure to overclock your device though.

I'm still not planning to play with governors or schedulers at all.

Oh, BTW, I saw a supposedly tweaked kernel on XDA called LightningZap. I looked through the github and some (most) of the changes seem really sketchy to me. So I'm not planning to use that at all.

 

[tdm]

Found a couple potential sources for overclock code:

46910c75a2fe - bricked - Custom Android kernel - Google Project Hosting

https://github.com/SebastianFM/HTC-...mmit/46b2098355a55cc3602d67cd5c98066241fefd8e

 

[tdm]

Hmm .. checking "disable hw overlays" in developer settings gets rid of the screen funkiness. Need to investigate what's going on ... anyone have a clue?

 

[ortrigger]

Hmm .. checking "disable hw overlays" in developer settings gets rid of the screen funkiness. Need to investigate what's going on ... anyone have a clue?

Possibly something in the adreno files not jiving with JB. HW overlays is basically gpu rendering the display right? It would kind of make sense. adreno 200 is kinda dated now.

 

[tdm]

Looks like it might be pretty trivial to enable overclock to 1674mhz. Not a huge speed bump but easy is good.

 

[tdm]

Possibly something in the adreno files not jiving with JB. HW overlays is basically gpu rendering the display right? It would kind of make sense. adreno 200 is kinda dated now.

Yeah I'll check that out.

Thing is, I have both the adreno libs and kernel changes from the CM p930 jb ROM. I'll doublecheck these.

 

[Neph81]

Hmm .. checking "disable hw overlays" in developer settings gets rid of the screen funkiness. Need to investigate what's going on ... anyone have a clue?

Seems like you're not the only one having issues with HWComposer.

https://plus.google.com/+CyanogenMod/posts/SSirbPcD1Lf

 

[tdm]

Got my nitro today. Waiting on a sim to be free from VM and CDMA. Yay!

The loaner spectrum should be here Monday. I hope to be able to make progress quickly on cm10 with a p930 to use as a reference.

 

[IMUcarmen]

Got my nitro today. Waiting on a sim to be free from VM and CDMA. Yay!

The loaner spectrum should be here Monday. I hope to be able to make progress quickly on cm10 with a p930 to use as a reference.

congrats on your new toy, and thank you for helping us tdm, I'm sure you already know, but, I wanted to personally say, so many people in this "community" really do appreciate your work and efforts.

 

[reeseboy]

congrats on your new toy, and thank you for helping us tdm, I'm sure you already know, but, I wanted to personally say, so many people in this "community" really do appreciate your work and efforts.

^^^ what he said.

 

[tdm]

I'm looking for ways to identify various i-project (p930/nitro/spectrum) variants so that I can build a "multi-ROM" for them. A "multi-ROM" is my own invention. It installs a set of base files common to all devices, then installs specific files based on the actual device. This drastically cuts down on build time, bandwidth, and storage space.

The good old standby from the MSM 7x27 based Optimus One is to use /sys/devices/system/soc/soc0/build_id. This file is present in the i-project devices, so I'd like to collect a list of possible values. Here's a start:

VZW VS920 with ZV6 baseband: 8660-AAABQNBYA-3161H
ATT p930 with V10f baseband: 8660-AAABQNBYA-30552040

I'm looking for the proper value for VS920 ZV4, VS920 ZV7, and any other variations.

 

[ortrigger]

ZV7 baseband is M8660A-AABQNSZM-3.6.2421

 

[1linuxfreak]

Wasn't ZV4 the same baseband as ZV6?

 

[droid-man]

congrats on your new toy, and thank you for helping us tdm, I'm sure you already know, but, I wanted to personally say, so many people in this "community" really do appreciate your work and efforts.

Hear, hear!