[DEV] CyanogenMod 10 marvel-ALPHA

SanderTheNinja · May 10, 2012

*se-nsei. said:
http://www.cyanogenmod.com/blog/the-future-of-cyanogenmod-7

You're friend is probably getting mixed up a little. Wildfire S is getting official CM7.2 support very soon, when it is released. The maintainer will probably be Alquez as he has promised us this.

Oh. In that case, not news for this CM9 thread.

Thrawed said:
Oh wow, they actually mention Wildfire S. I had lost hope that we would get official status after alquez mentioned that he hadn't heard back from them.

pinkypie said:
what difference does it make? im using alquez's cm7.2 unffocial builds quite some time now and they are rock solid and feels "official" to me lols. sorry modpunk for the ot.

@Modpunk: Sorry for offtopic. I just had to tell this.

Fikus011 · May 10, 2012

*se-nsei. said:
I've asked that question so many times, and I've never got an answer. xD

i posted this in general section too....google,google,google
-- SGX Video Acceleration (in principle, it was available in kernels after 2.6.35, while CM7 has stuck on 2.6.32);
-- DSP, a (better) support is offered in kernels after 2.6.38;
-- Better OMAP Frame Buffer drivers (omapfb): for the Beagleboard development platform they talk in favor of using more software-optimized driver based on NEON extensions, than a SGX hardware accelerated renderer (fbdev).
(info from elinux.org on Beagleboard Debian)

modpunk · May 10, 2012

OliverG96 said:
And exactly what's going to be better when we have kernel 3.0 working?

Enviado desde mi HTC Wildfire S A510e usando Tapatalk

If I tell you we will have more msm kerner device, ion, zram, iptable modules does that tell you anything?

dream707 · May 10, 2012

modpunk said:
If I tell you we will have more msm kerner device, ion, zram, iptable modules does that tell you anything?

he was probably meant what it gives to ordinary user, not developer.

bingzz · May 10, 2012

He means there is no point asking unless you know what you're doing. wow. Why don't you guys wait rather than keep demanding eta's or new features off him. You'll know when it's released.

eoghan2t7 · May 10, 2012

@modpunk i have been reading the OMX source and seeing what files get compiled compared to yours and there are more omx files in the rom i built also i tink i no way there is no hq youtube playback i have gathered this from my reading in the omx folder i.e. here

android/system/vendor/qcom/opensource/omx/mm-video in the android.mk files i have noticed this the
omx files are from the p500 developer that modded it to compile on msm2x27 i see this

ifeq ($(TARGET_BOARD_PLATFORM),msm7x27)
libmm-venc-def += -DMAX_RES_720P
endif

if that is correct then when playing HQ youtube videos etc the broswer or youtube app will thinks the phone can play 720p HD instead of it being

ifeq ($(TARGET_BOARD_PLATFORM),msm7x27)
libmm-venc-def += -DMAX_RES_480P
endif

for it plays HQ 480p format i have modded the file to say its 480p but then there are loads of compile errors etc so i am going to print out all the omx files in the folder above and see what else needs modded. i hope im getting there with the problem hunting and providing helpfull information this time

*se-nsei. · May 11, 2012

eoghan2t7 said:
@modpunk i have been reading the OMX source and seeing what files get compiled compared to yours and there are more omx files in the rom i built also i tink i no way there is no hq youtube playback i have gathered this from my reading in the omx folder i.e. here

android/system/vendor/qcom/opensource/omx/mm-video in the android.mk files i have noticed this the
omx files are from the p500 developer that modded it to compile on msm2x27 i see this

ifeq ($(TARGET_BOARD_PLATFORM),msm7x27)
libmm-venc-def += -DMAX_RES_720P
endif

if that is correct then when playing HQ youtube videos etc the broswer or youtube app will thinks the phone can play 720p HD instead of it being

ifeq ($(TARGET_BOARD_PLATFORM),msm7x27)
libmm-venc-def += -DMAX_RES_480P
endif

for it plays HQ 480p format i have modded the file to say its 480p but then there are loads of compile errors etc so i am going to print out all the omx files in the folder above and see what else needs modded. i hope im getting there with the problem hunting and providing helpfull information this time

Didn't modpunk say its something in the media XML or something?

eoghan2t7 · May 11, 2012

*se-nsei. said:
Didn't modpunk say its something in the media XML or something?

yeah but as far as i no the media xml is only used by the camera to no what formats it can record in.

Eskuero · May 11, 2012

eoghan2t7 said:
@modpunk i have been reading the OMX source and seeing what files get compiled compared to yours and there are more omx files in the rom i built also i tink i no way there is no hq youtube playback i have gathered this from my reading in the omx folder i.e. here

android/system/vendor/qcom/opensource/omx/mm-video in the android.mk files i have noticed this the
omx files are from the p500 developer that modded it to compile on msm2x27 i see this

ifeq ($(TARGET_BOARD_PLATFORM),msm7x27)
libmm-venc-def += -DMAX_RES_720P
endif

if that is correct then when playing HQ youtube videos etc the broswer or youtube app will thinks the phone can play 720p HD instead of it being

ifeq ($(TARGET_BOARD_PLATFORM),msm7x27)
libmm-venc-def += -DMAX_RES_480P
endif

for it plays HQ 480p format i have modded the file to say its 480p but then there are loads of compile errors etc so i am going to print out all the omx files in the folder above and see what else needs modded. i hope im getting there with the problem hunting and providing helpfull information this time

Good job, waiting for news

Enviado desde mi HTC Wildfire S A510e usando Tapatalk

benjamingwynn · May 11, 2012

Kind of a noob question here but may I ask does gingerbread have support for 3.0 kernels?

Sent from my HTC Wildfire S A510e using xda premium

eoghan2t7 · May 11, 2012

benjamingwynn said:
Kind of a noob question here but may I ask does gingerbread have support for 3.0 kernels?

Sent from my HTC Wildfire S A510e using xda premium

no but im sure once the ics one is made the GB one wont to to far behind

jardivben · May 11, 2012

Any finding as to what was causing the stall out for the marvelc? I dont mean to be naggy i just wondered.

Thanks, Jared

eoghan2t7 · May 11, 2012

jardivben said:
Any finding as to what was causing the stall out for the marvelc? I dont mean to be naggy i just wondered.

Thanks, Jared

Not yet still at it tho

Sent from my Wildfire S using Tapatalk 2

jardivben · May 11, 2012

eoghan2t7 said:
Not yet still at it tho

Sent from my Wildfire S using Tapatalk 2

Awesome! Keep us updated!

modpunk · May 11, 2012

eoghan2t7 said:
@modpunk i have been reading the OMX source and seeing what files get compiled compared to yours and there are more omx files in the rom i built also i tink i no way there is no hq youtube playback i have gathered this from my reading in the omx folder i.e. here

android/system/vendor/qcom/opensource/omx/mm-video in the android.mk files i have noticed this the
omx files are from the p500 developer that modded it to compile on msm2x27 i see this

ifeq ($(TARGET_BOARD_PLATFORM),msm7x27)
libmm-venc-def += -DMAX_RES_720P
endif

if that is correct then when playing HQ youtube videos etc the broswer or youtube app will thinks the phone can play 720p HD instead of it being

ifeq ($(TARGET_BOARD_PLATFORM),msm7x27)
libmm-venc-def += -DMAX_RES_480P
endif

for it plays HQ 480p format i have modded the file to say its 480p but then there are loads of compile errors etc so i am going to print out all the omx files in the folder above and see what else needs modded. i hope im getting there with the problem hunting and providing helpfull information this time

Just enabling this doesn't work, you need support for it in the kenrel too. We have already the patches for the kernel and testing it. However the OMX codecs we have don't have hardware/kernel support. I don't think that it will actually help. We will see.

Eskuero · May 12, 2012

SWAP partition is not working

What steps will reproduce the problem?
1. Install Data2SD
2. Test SWAP partition from Terminal Emulator
3. SWAP partition is not detected

What is the expected output? What do you see instead?
I wait to see different numbers with the free and used memory from SWAP partition, but I only get a lot of zeros.

Do you see erros in the log files (logcat, dmesg)?
No logcats problems, I think that's because is not a system error, simplicy a kernel fail

What version of the product are you using? (See System Settings -> About
Phone)

Number Model: HTC Wildfire S A510e
Android version: 4.0.4
BaseBand Version: 47.23a.35.3035H_7.53.39.03M
Kernel Version: 2.6.35.13-cryptomilk-alquez.r11-ga45b885asn@magrathea #1

Please provide any additional information below.

I think that's a kernel issue, because un latest version of CM7, alquez says:

- new kernel with swap on

Because of that I think that you can put SWAP on, by only editing the kernel...

I add a little picture of Terminal Emulator too.

modpunk · May 12, 2012

jardivben said:
Any finding as to what was causing the stall out for the marvelc? I dont mean to be naggy i just wondered.

Thanks, Jared

Pat and I started to work on a 3.0 kernel tree based on caf ics_chocolate. I will port the board files soon and we will have a kernel with boot console output on the screen. I will give you a testing kernel so we can see what's going wrong.

This will take one, two or three weeks, but we will get there

jardivben · May 12, 2012

modpunk said:
Pat and I started to work on a 3.0 kernel tree based on caf ics_chocolate. I will port the board files soon and we will have a kernel with boot console output on the screen. I will give you a testing kernel so we can see what's going wrong.

This will take one, two or three weeks, but we will get there

Sounds like a plan mate!

I really want to thank you for everythnig....expect a donation soon.

Sent from my HTC_A510c using xda premium

Thrawed · May 12, 2012

Modpunk, in the build.prop, could you change ro.product.model from "HTC Wildfire S A510e" to "Wildfire S" as this is what the play store uses for your device name. So at the moment it is displayed as "HTC HTC Wildfire S A510e" because the store already pulls the manufacturer name from ro.product.manufacturer.

modpunk · May 12, 2012

I've set the same values as in the stock rom. I'm not sure if it is a good idea to change that.

[DEV] CyanogenMod 10 marvel-ALPHA

Senior Member

Senior Member

Inactive Recognized Contributor

Member

Senior Member

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Recognized Developer

Inactive Recognized Developer

Inactive Recognized Contributor

Member

Inactive Recognized Contributor

Member

Inactive Recognized Contributor

Recognized Developer

Attachments

Inactive Recognized Contributor

Member

Senior Member

Inactive Recognized Contributor

Similar threads

Top Liked Posts