yashsingh1/xdaforums huggingface dataset:
[HTC Wildfire S] eoghan2t7:
Ill have a look tomorrow at the marvelc/t configs to see if there's a problem with them.
[HTC Wildfire S] modpunk:
We have working OMX already since quite some time and the camcorder is working just fine too in the meantime.

Our camera code is much more advanced than what they have in P500. Droste rewrote a lot of parts so that we have less errors and memory leaks.
[HTC Wildfire S] Lt.Win:
Hey modpunk! :)

The only bugs we (P500) have remaining are Wi-Fi and USB tethering and Mass storage bug : we need to toggle debugging to use mass storage. Would the fixes be available on your git? We could use a quick fix. :D

Thanks.
[HTC Wildfire S] pongping88:
are the bugs fixed yet????
[HTC Wildfire S] modpunk:
Mass Storage and USB Tethering is working just fine, that's what I use here. I haven't tested wifi tethering yet. If you're a developer we have a channel were we work together on CM9. We work on the kernel and share all the stuff we find. However the git history of marvel should be verbose enough to find the fixes you need.

We started to work on kernel 3.0 now.
[HTC Wildfire S] Lt.Win:
No, no I'm no dev, I'm just trying to help our deevs out to save their time. Thanks. I'll let them know. After fixing everything, I'll try to ask them if they can work on kernel 3.0.
[HTC Wildfire S] Eskuero:
And exactly what's going to be better when we have kernel 3.0 working?

Enviado desde mi HTC Wildfire S A510e usando Tapatalk
[HTC Wildfire S] *se-nsei.:
I've asked that question so many times, and I've never got an answer. xD
[HTC Wildfire S] SanderTheNinja:
Weird news: my friend something from cm that we maybe get official cm9. Dont know if I could trust that article, but still.
[HTC Wildfire S] *se-nsei.:
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. ;)
[HTC Wildfire S] Thrawed:
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.
[HTC Wildfire S] pinkypie:
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.
[HTC Wildfire S] SanderTheNinja:
Oh. In that case, not news for this CM9 thread.

@Modpunk: Sorry for offtopic. I just had to tell this. :)
[HTC Wildfire S] Fikus011:
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)
[HTC Wildfire S] modpunk:
If I tell you we will have more msm kerner device, ion, zram, iptable modules does that tell you anything?
[HTC Wildfire S] dream707:
he was probably meant what it gives to ordinary user, not developer.
[HTC Wildfire S] bingzz:
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.
[HTC Wildfire S] eoghan2t7:
@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 ;)
[HTC Wildfire S] *se-nsei.:
Didn't modpunk say its something in the media XML or something?
[HTC Wildfire S] eoghan2t7:
yeah but as far as i no the media xml is only used by the camera to no what formats it can record in.
[HTC Wildfire S] Eskuero:
Good job, waiting for news(:

Enviado desde mi HTC Wildfire S A510e usando Tapatalk
[HTC Wildfire S] benjamingwynn:
Kind of a noob question here but may I ask does gingerbread have support for 3.0 kernels?
[HTC Wildfire S] eoghan2t7:
no but im sure once the ics one is made the GB one wont to to far behind ;)
[HTC Wildfire S] jardivben:
Any finding as to what was causing the stall out for the marvelc? I dont mean to be naggy i just wondered.

Thanks, Jared
[HTC Wildfire S] eoghan2t7:
Not yet still at it tho ;)
[HTC Wildfire S] jardivben:
Awesome! Keep us updated! ;)
[HTC Wildfire S] modpunk:
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.
[HTC Wildfire S] Eskuero:
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.
[HTC Wildfire S] modpunk:
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 :)
[HTC Wildfire S] jardivben:
Sounds like a plan mate!:) I really want to thank you for everythnig....expect a donation soon.
[HTC Wildfire S] Thrawed:
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.
[HTC Wildfire S] modpunk:
I've set the same values as in the stock rom. I'm not sure if it is a good idea to change that.
[HTC Wildfire S] Thrawed:
I know that they were changed in alquez's CM7 rom, so he would probably have a better idea of if there any repercussions stemming from that. But personally I've never noticed any issues from changing them.
[HTC Wildfire S] Fikus011:
just checked in cm7.2 build.prop

ro.build.user=alquez

ro.build.host=Asgard

ro.build.tags=test-keys

ro.product.model=Wildfire S

ro.product.brand=htc_wwe

ro.product.name=htc_marvel

ro.product.device=marvel

ro.product.board=marvel

thrawed is right about that build...idk about any impact that could have in cm9..doubt it will at all...ill try tomorow and if anyone does not try before me,i will report.
[HTC Wildfire S] benjamingwynn:
Won't make a difference, it's just mainly for error feedback purposes.
[HTC Wildfire S] eoghan2t7:
Ok guys I as you no I am reading like crap over the source code and stagefright is what controls the media codecs and after reading the source I notied a switch call libstagefright_omx I no that it gets built into the rom but maybe its a basic version if we add that switch to marvel.mk maybe that will allow stagefright to talk properly with the omx libs I would test it but its late at the moment and compiling would keep me up late :( so maybe modpunk can tell me if I'm on the right track without out shouting at me like a teacher and student lmao :p
[HTC Wildfire S] Thrawed:
Before:

After:

With no obvious differences in availability.
[HTC Wildfire S] Fikus011:
With no obvious differences in availability.

thanks...i thought so..
[HTC Wildfire S] *se-nsei.:
Yeah but what's the motive in changing it?
[HTC Wildfire S] Thrawed:
Purely cosmetic reasons, I use the play store an awful lot and it just bugs the hell out of me seeing "This app is compatible with your.. HTC HTC Wildfire S.." all the time.
[HTC Wildfire S] Eskuero:
The Play Store didn't restrict app by model and manufacturer, only by the type of cpu, per example our armv6 haven't got access to apps like FlashPlayer in the Market(:

Enviado desde mi HTC Wildfire S A510e usando Tapatalk
[HTC Wildfire S] benjamingwynn:
Probably a bug in the marvel.mk as my first guess
[HTC Wildfire S] Royal King:
Guys, how much is your battery lasting? Like how many hours? I'm an (little above) moderate user..
[HTC Wildfire S] laxsrbija:
My battery was at 60% when I installed the ROM. After an entire night of Deep Sleep and ~3h of usage since this morning, I'm at 20%.
[HTC Wildfire S] dudeman1996:
To be honest, you gotta give more detail if you're talking about battery life. There are loads of factors such as Wi-Fi, mobile data, 2G/3G, auto sync etc. that you have to include
[HTC Wildfire S] laxsrbija:
I was just telling the guy that the battery life is normal, just like on any other ROM for me. Now, the way I said that was a bit weird ;)
[HTC Wildfire S] Nightshadow931:
I wonder, which part of [DEV] in this thread you don't understand ?

There is a reason for two threads on this ROM, one is for DEV, one is for ROM itself.
[HTC Wildfire S] Eskuero:
Anyone can commit a fail...

Enviado desde mi HTC Wildfire S A510e usando Tapatalk
[HTC Wildfire S] *se-nsei.:
@ modpunk : maybe this will help?

http://xdaforums.com/showthread.php?t=1653311
[HTC Wildfire S] Thrawed:
Hasn't it been proven that all those petitions never actually accomplish anything?
[HTC Wildfire S] modpunk:
It is not a software problem, it is a hardware problem. Our device lacks hardware encoders and decoders.
[HTC Wildfire S] dream707:
actually after some of them qcom released ics drivers for armv6, and we got hwa working
[HTC Wildfire S] ScardracS:
I use it a lot and after 4 1/2 hrs battery go from 100% to 3%

Inviato dal mio HTC Wildfire S A510e usando XDA Premium HD app
[HTC Wildfire S] hayanno:
With "easy battery saver", I can play music all the day (7-8 hours) and my battery still 50%...
[HTC Wildfire S] modpunk:
Check with BetterBatteryStats what's going on.

I think we've fixed hotspot tethering.
[HTC Wildfire S] dudeman1996:
modpunk what's "electronbeam screen on animation"?
[HTC Wildfire S] Lt.Win:
That's awesome. Is there any way to lessen the screen's battery usage? It eats or maybe swallows my battery when I'm using Wi-Fi or mobile internet. My experience wasn't so good with third party apps for battery saving on gingerbread. Does it really have a good effect on ics?
[HTC Wildfire S] modpunk:
BetterBatteryStats is a debugging tool not a tool to safe battery.

ElectronBeam Screen On is an animation if you activate the device. You can turn it on now ...
[HTC Wildfire S] Lt.Win:
Actually I was taking to the guy above you. He was talking about easy battery saver. :p

Is the Wi-Fi hotspot fix confirmed?
[HTC Wildfire S] benjamingwynn:
@modpunk

Your camera overlay messes up compiling here, it doesn't like the xml. I have added it directly to the camera package but I will probably send you a fixed up version of it in the future, to keep things cleaner.

Unless I'm doing something wrong :p
[HTC Wildfire S] modpunk:
You are doing something wrong.
[HTC Wildfire S] Lt.Win:
Okay, so I got a list of ARMv6 devices so I could see which ones are our brothers.

Narrowed it down to HTC, found Legend. Here's the important stuff they have working:

Working (stable):

USB tethering

USB mass storage

FM radio, using spirit FM App and setting for msm7x30 Method

Wifi tethering with OpenGarden

Hw Acceleration (Stock Gallery, Live Wallpapers, Video, Youtube, Google Maps App, etc.).

GPS

Camera (photos, preview, panoramic).

Green= We have the problem sorted out.

Bold = Same issue

Red = Not fixed yet.

So, comparing the lists, we don't have panorama working. They do.

I guess this should help: https://github.com/zeubea/android_device_htc_legend/tree/ics/camera

It contains the camera HAL code.

They too, don't have camcorder working fully (like us) because of lack of OMX armv6 codecs.

So that's pretty much it. If I find any more bugs, I'll post them here and edit this post (maybe). :)

Good luck in fixing bugs, I'm trying my best to help.

CyanogenFire S™
[HTC Wildfire S] hayanno:
Open garden use blutooth for tethering, and not wifi...
[HTC Wildfire S] Lt.Win:
Its copied from the legend ics thread. Their fault I guess. :p

CyanogenFire S™
[HTC Wildfire S] asdot:
or he haven't tried I guess :D

Sent from MARVEL
[HTC Wildfire S] Lt.Win:
Quote from the lg p500 cm9 dev.

The fix should be on his github here: https://github.com/lgics

If anyone can check, please do. :)

CyanogenFire S™

_______________________________________

Join the Epic Side, we have Android!
[HTC Wildfire S] modpunk:
I've fixed network changing and added cdma support for marvelc.
[HTC Wildfire S] csoulr666:
you rule man!!!!
[HTC Wildfire S] AceRoom:
https://developer.qualcomm.com/forum/qdevnet-forums/multimedia-optimization-qdsp/13248

Scroll all the way to the bottom. An official from Qualcomm has posted this:

This was found by goodguy25 at http://xdaforums.com/showthread.php?t=1721173

Sounds like bad news for all msm7x27 devices. It seems the OMX libraries required for ICS aren't compatible with the armv6 instruction set and the OMX libraries from gingerbread are on a lower API than required for ICS.
[HTC Wildfire S] dream707:
I know it is hard but maybe it is possible to write some compatibility layer like HAL for gingerbread camera libs?
[HTC Wildfire S] modpunk:
First I need to get libcamera.so working and a 3.0 kernel for better bluetooth support.
[HTC Wildfire S] jardivben:
Good to hear! Btw Im back...i had to take a good chunk of time to prep for finals.

Was this change added to the git? if so ill complie and try on my marvelc
[HTC Wildfire S] modpunk:
Sure. I need logcat if something doesn't work and dmesg. If you have a random reboot I need /proc/last_kmsg. If it doesn't boot at all I need /proc/last_kmsg too, you can get it if you adb in the recovery.
[HTC Wildfire S] modpunk:
I think I really fixed wifi hotspot now. I spent the whole evening in strace and added debug messages to daemons.
[HTC Wildfire S] modpunk:
Ok, for marvelc I need to restructure the whole repo. I wanted to do that anyway to share common code with liberty.
[HTC Wildfire S] csoulr666:
Small question modpunk.........can full video playback and fully functioning camera be achieved without the OpenMAX drivers from Qualcomm?????? Asking it just for knowledge purposes.....
[HTC Wildfire S] modpunk:
I don't think so. We can improve the camera. I've started to work on that already some time ago. I got the latest liboemcamra.so working but the preview only captures one frame an then stops. I haven't found out what's the problem yet.

The code is here:

http://git.cryptomilk.org/projects/marvel/android_device_htc_marvel.git/log/
[HTC Wildfire S] csoulr666:
The code is not my concern........actually i just like to keep info on stuff like this,i don't have time to do any developement(don't have the experience either :) ).......Getting to college is my No.1 priority this year :D

Thanks for the enlightment
[HTC Wildfire S] modpunk:
After the restructuring of the repositories I'm finally back to a working ROM and we have some new nice bugfixes like working barcode/qrcode scanners.
[HTC Wildfire S] Fikus011:
I see you have decided to go with Smartass2 as default,so i beilive you tested the hell out of it...and its probably shown as best one yet.

I took a look at it,agree with you on that now...its better then ondemand cause it scales faster and with no limits when woken up.

Its a shame about OMX,cause you made this ROM working great for given hardware.

Great and enormous work mr.Schneider :good:
[HTC Wildfire S] Lt.Win:
His surname is Schneider? O.o

And, on topic, I have to agree with Fikus on this. Snartass2 is a really good choice. There's a list of info on governers somewhere here. I checked that, and it does seem like a good option. Hoping to see some good stuff in alpha4.

I, personally think its time to go to beta, since most of the stuff is working. Good luck! :D
[HTC Wildfire S] modpunk:
I still want to get the latest liboemcamera.so working. That's the next task.
[HTC Wildfire S] Thrawed:
No no, we need to stay on alpha for as long as possible, beta means feature lock.

Indeed, modpunk uses his real name on git.
[HTC Wildfire S] modpunk:
Oh, I have a marvelc tree now. ALPHA4 will have a marvelc ROM. I hope there are people who can report good bugs cause I don't own the device.
[HTC Wildfire S] csoulr666:
Yeah his name is real name is sorta cool........."Andreas Schnieder"

Good job my friend........you keep going on like this.......just take it slow and steady
[HTC Wildfire S] Nightshadow931:
That's great news, keep up the good work!
[HTC Wildfire S] modpunk:
HELP NEEDED:

I need the logcat output of starting the camera and taking a picture from a HTC STOCK ROM.
[HTC Wildfire S] ogfrier:
Meeeeeee :-).
[HTC Wildfire S] cpie20:
Hold up I can't upload It To xda so ill upload the logcat via box :)

Edit: here is the link

https://www.box.com/shared/041f3550d270ebcea484
[HTC Wildfire S] modpunk:
Thanks for the log. It gave me the right values but the new liboemcamera.so still doesn't work.
[HTC Wildfire S] Fikus011:
I dont know(i did not look into it) did you changed anything in wifi...but i can tell you that i just had great reception in the place where i never did before with stock rom.I am not sure is it your Rom or Router got shot of megawats,did a speed test with no bars at all and it was great.

I am sleepy now..so i couldnt be bothered checking db levels..if you did it then :good:

Whats going on with that ZTE camera,i see you commented (#) bunch of stuff,but to be honest i dont understand half of that.

All is good,maybe some fine tuning of the Rom and its great.Not one FC,it is smoother now,that governor is welcome too

Such a shame for HQ video..not so much for cam as it is for YT or any kind of streaming...keep perfecting what you can with this given hardware.

All the best,cheers!
[HTC Wildfire S] modpunk:
The marvelc ROM needs to be tested.
[HTC Wildfire S] cpie20:
What I noticed is that it doesnt connnect to my network, Iwould send you a logcat but i have no computer access.
[HTC Wildfire S] vbhtt:
In terminal emulator, type

su

logcat > /sdcard/logcat.txt

The you will find a logcat.txt in your sdcard. You can upload that.
[HTC Wildfire S] modpunk:
There is a also a logcat app.

https://play.google.com/store/apps/details?id=org.jtb.alogcat
[HTC Wildfire S] benjamingwynn:
Good find :)
[HTC Wildfire S] WoefulDerelict:
Query...

While working with your code and building the ROM and TWRP recovery I noticed the Kernel version no longer matches the ROM version. Was this intentional or a minor oversight?

---------- Post added at 03:58 PM ---------- Previous post was at 03:42 PM ----------

There are a number of apps that will allow you to view and manipulate the log on your device.

My personal favourite is .Logcat but, I'm a sucker for pretty things... also kitties.
[HTC Wildfire S] Fikus011:
thought you might be interested,although you may have seen it already

https://groups.google.com/forum/#!topic/android-building/XBYeD-bhk1o
[HTC Wildfire S] thelegbra:
modpunk do you have any plans with aosp jb or cm10?

since it's not a major upgrade, it shouldn't be too hard to get a jb rom going. will you take a look at the source code since it's released today? :P
[HTC Wildfire S] modpunk:
I will wait for cm to integrate it. It will take some time. We will see.
[HTC Wildfire S] csoulr666:
I think our first priority should be a fully working CM9................after that CM10 will become easier to make
[HTC Wildfire S] *se-nsei.:
modpunk has done such a brilliant job in getting us CM9 this fast, I'm sure it's helped prepare for a CM10 port. :)
[HTC Wildfire S] modpunk:
CM9 RC2 has been released and the first CM features are hitting the jellybean branches. Looks like next week I could start with CM10 work.
[HTC Wildfire S] thelegbra:
just rename cm9 to beta already, it's feature complete and there ain't any big bugs left. it's too good to be alpha.

any ideas about my touchscreen report on the bugtracker? :angel:
[HTC Wildfire S] modpunk:
It isn't feature complete, the camera isn't fully working and we don't have omx libraries for ICS.
[HTC Wildfire S] thelegbra:
well, they won't be releasing the libraries. i guess you will try and get over it with hacks. but a beta would still have known bugs and video recording isn't that much of a problem for a beta rom :P i've seen worse.

about the touchscreen? :P
[HTC Wildfire S] modpunk:
I have different quality standards ... :)
[HTC Wildfire S] thelegbra:
okay, i respect that :) i don't care what it's named as long as it's awesome :D

i'm kinda spamming here, any comments on my touchscreen complaint? :eek:
[HTC Wildfire S] modpunk:
Well I need to fine the time to dig into the code, check if the build.prop variables exist and do something. Then I need to find the right variables and the corresponding values which fix the problem.

This is really time consuming and my time is limited. I have job, other open source project and a life without computers ;)
[HTC Wildfire S] thelegbra:
aha! then you acknowledge that the touchscreen feel isn't what it should be! even that's enough for me :P thanks! :D
[HTC Wildfire S] thelegbra:
i guess it's not the build.prop variables. it doesn't only feel slow, it's buggy. when you do a fast flick from bottom to top, say when you're scrolling through your contacts, sometimes it misclicks a person. it doesn't happen in stockroms or other ics devices.

could it be the idc file values? or the kernel i2c driver cyttsp?

pardon my noobiness if it doesn't have anything to do with what i'm saying, i'm not really familiar with these.
[Galaxy Tab Q&A, Help & Troubleshooting] the_nox:
Hi,

I flashed CM9 nightly on my galaxy tab,

tried 2012-04-27 and 2012-05-03. Everyhting works great, expect for the 3G transfer speeds. The status icons shows 3G/H, but the speed is still the same as when using 2G mode only. I already tried different modem files. Any advice how to debug the situation? with JPZ (in europe/switzerland) I see the 2g,3g,H icons but only get 2g speed. Speed was fine on Overcome v4.1

Thanks.
[Galaxy Tab Q&A, Help & Troubleshooting] Ponomar:
Try to flash different PRL's. I've expected the same problem when I've downloaded wrong PRL.

I've solve this problem with the flashing the nessesary PRL.

Use AxesstelPst EvDO BSNL for checking your connection.
[LG Optimus Black] androidjel:
how can i have onscreen buttons for ics?
[LG Optimus Black] mullarameez:
By buying galaxy nexus :D
[LG Optimus Black] androidjel:
no im serius i want ics onscreen buttons for p970.

because i like that more.
[LG Optimus Black] wessyh0:
So, then u have 7 buttons, which are 4 too much?