Late bloomer in this issue though, As far as what I have read here from the forums,
- Qualcomm terminated the support for OpenMAX codecs for ARMv6, for ICS
- no one is making a pursuit again on building the codecs
It has been months since this issue broke up. Also, its nearing its 1st birthday :laugh:
Soo, how's it gonna be? Go back to GB? or live with the issue (no camcorder).
I think they got the codecs a while ago....
SunnyChrono6 said:
I think they got the codecs a while ago....
Click to expand...
Click to collapse
could you provide me the link/s?
I've been using cm9.1 (from google, for Wildfire S) lately and the only issue I have is the camcorder...
thanks. that was a relief
There's a Q&A section
B2T: Try MiUi camera.
Gesendet von meinem HTC Sensation Z710e mit Tapatalk 4
I think they did a little hack on CM9 to get all the stuff working; Use modpunk's latest build or even better, compile it yourself
Sent from my Wildfire S A510e using xda app-developers app
that's great guys. thanks! I
'll search for the hack / info on the QnA.
Building it myself... Would be a problem, coz I'm a n00b at this one, even though I have some experiences with Linux (Ubuntu)
artturnip said:
I think they did a little hack on CM9 to get all the stuff working; Use modpunk's latest build or even better, compile it yourself
Sent from my Wildfire S A510e using xda app-developers app
Click to expand...
Click to collapse
you must be talking about this one: libstagefright fix:
http://forum.xda-developers.com/showthread.php?t=1960117
now checking on it. thanks again.
well since I have found the modified omx libraries, and a flashable zip for easy installation, I really dunno why the problem on the camcorder still remains? and some mp4 files (high quality and with resolutions up to 800x480) are not playing anymore unlike the last time, before injecting the omx libraries....
Is there something I should do to fix this? like editing the build.prop or similar to this?
i'm kinda late when it comes to these updating drivers though. thanks.
Related
Hello all,
I just wanted to let you know my experience from some minutes ago.
I successfully boot up CM7 ported to my device.
Everyone is free to do so, but be careful what you do.
I used the kitchen to cook it, so thanks to dsixda for his work.
And also to arco68 and cowithgun whose kernel I was using.
Last but not least KezraPlanes for his Rom I was using as base and for comparison.
Sadly, this is just a quick and dirty port so no downloadlink.
Also there have to be still many bugs and things not working, cause of the cm rom I used.
To state some:
GPS (does not lock)
Audio (both input and output, will be tough)
Camcorder (because of audio)
Storage-related (external SD not working, internal with no USB storage, vold misconfigured)
USB tethering/MTP (will require some programming)
Host access point (similar to USB tethering)
Buttons force feedback
Contacts on SIM card
This was stated by YardE in his thread, about the CM-Rom I used for the Port. So, also credtis to him and the fellow developer.
I just made it for the fun of it and to show some pics, here you have:
Welcome to the club the community awaits you n to those assisting you.
Take your time....
Sent from my GT-I8150 using xda premium
CM7 for our phone? Sounds great I think that will be very useful.
Sent from my GT-I8150
lightwars said:
Sadly, this is just a quick and dirty port so no downloadlink.
Also there have to be still many bugs and things not working, cause of the cm rom I used.
Click to expand...
Click to collapse
Thanks alot for your work, any extra ROM is a gain for the Community.
I have one question and according to your profile you are from the same Country(Germany) and have the same Provider(simyo). Does your data connection work ? Does this ROM has also this "funny SIM card issue". The good thing about this ROM we will have the drivers for Gingerbread isn't ?
greets
THE-E
Yeap according to arco68 all the drivers are available....I think
Should not be a problem it is just a question of time n effort plus patience.......Just the beginning..you are one brave soul
Sent from my GT-I8150 using xda premium
lightwars said:
Also there have to be still many bugs and things not working, cause of the cm rom I used.
To state some:
Light sensor
Click to expand...
Click to collapse
Just one remark, SGW doesn't have light sensor, only proximity sensor.
Sent from rooted GT-I8150 2.3.6 ~ Tapatalk 2.0.1
_jis_ said:
Just one remark, SGW doesn't have light sensor, only proximity sensor.
Sent from rooted GT-I8150 2.3.6 ~ Tapatalk 2.0.1
Click to expand...
Click to collapse
Yes,you are right.I just copied it.
It is edited now.
Gesendet von meinem GT-I8150
Great move. Thanks
Sent from my novo7_ELF using Tapatalk 2 Beta-6
great!
keep up the good work.
more rom = more choices for the community
cheers!
Any news of this? CM7 seems like a good choice in the short run.
Dude....any updates ?
o O From My Ancora o O
I hope there is dev who willing to port CM7 to our galaxy W
i know it's out of date
But CM7 itself still cool
still have a lot of customization
and i want to make some wp clone with it
Okay,okay.To sum some things up.
After my try to port a ROM via the kitchen I had downloaded the sources and try to compile a build.
Sadly I cannot spend so much time in playing around with the code and try things out.
So far I overcome some problems while compiling. - crazy story here-
In the End no boot up and I noticed the small system size, which is definitely to tiny for all the libs.
To say so: still a way to go.
Maybe Arco have time to guide a little bit or someone else will supporting me, like KezraPlanes,...
Gesendet von meinem GT-I8150
Very good news.. good luck so... i would help you if i could
I used to have in my other galaxy
Sent from my GT-I8150 using XDA
May i know which ROM that u used as a porting?
(Q) Porting Rom
Is there anyone out there brave enough to port CM7 and AOSP 2.3.7 from S Plus to our device?
take a look at this thread
http://forum.xda-developers.com/showthread.php?t=1639421
BloodRaven2011 said:
May i know which ROM that u used as a porting?
Click to expand...
Click to collapse
Sorry for the late reply, I didn't found enough time to. Because I wanted to dig out the links. Here you are, that's the one I used:
http://forum.xda-developers.com/showpost.php?p=22969855&postcount=394
But also done it with this AOSP ROM:
http://forum.xda-developers.com/showpost.php?p=25752734&postcount=1
And the first Rom, YardE ROM from here:
http://forum.xda-developers.com/showpost.php?p=22424496&postcount=1
If you don't already know jelly bean was released at Google recently. The source code isn't yet available for the public so I have decided to see what I can get working from the SDK (until the source comes out) as a little project.
On an extreme downside I broke 1/3 (the middle) of my phones touch screen by water damage - so... bummer. :'(
EDIT: It's been in dried rice for a good 4 hours now... time to test :/
EDIT2: THE RICE WORKED! - My touchscreen is now back to it's good, working state
Try porting the sdk? Good luck, it will be compiled for armv7 so pretty much impossible. Only porting via source is possible unless you are some hardcore machine code hacker!
Sent from my Wildfire S using xda app-developers app
VigiDroid said:
Try porting the sdk? Good luck, it will be compiled for armv7 so pretty much impossible. Only porting via source is possible unless you are some hardcore machine code hacker!
Sent from my Wildfire S using xda app-developers app
Click to expand...
Click to collapse
Yeah I've already tried porting it from the sdk image. Got so far then the entire thing collapsed.
I'm going to wait for the source code now though.
Sent from my Wildfire S A510e using xda premium
Hahaha good luck to you on the work once the sources are released jelly bean is a nice upgrade, I espically love the "smart" app updates! Hopefully it shouldn't take too long as most of the base would be ICS which we already have running on our phone with a few minor bugs
Sent from my Wildfire S using xda app-developers app
VigiDroid said:
Hahaha good luck to you on the work once the sources are released jelly bean is a nice upgrade, I espically love the "smart" app updates! Hopefully it shouldn't take too long as most of the base would be ICS which we already have running on our phone with a few minor bugs
Sent from my Wildfire S using xda app-developers app
Click to expand...
Click to collapse
I agree - although the hardware tree would need a bit of hacking to be wildfire s friendly
Sent from my Wildfire S A510e using xda premium
Over at rootzwiki a system dump has been leaked. Maybe some kind of port could be worked from that? Surely not all the apps are compiled for armv7, right?
Sent from my Wildfire S using xda app-developers app
VigiDroid said:
Over at rootzwiki a system dump has been leaked. Maybe some kind of port could be worked from that? Surely not all the apps are compiled for armv7, right?
Sent from my Wildfire S using xda app-developers app
Click to expand...
Click to collapse
I already dumped the system myself. But it refuses to boot. An error system errors out basically. Silly armv7 bins on an armv6 phone don't work so I use ics ones. That causes major errors apparently.
Sent from my Wildfire S A510e using xda premium
Benjamin,i hope this will help u
http://forum.xda-developers.com/showthread.php?t=1739561
It isn't better buy a better an newer phone for Jelly Bean :laugh: .
I like A4.0.4 CM9 with the little bugs but to feel the new feeling of Jelly bean a new phone been better ;-)
I will do this from source in two weeks after the release of robotomod based of alquezs and simons work.
None of modpunks work will be involved.
Sent from my Wildfire S A510e using xda premium
What's going to be new in cm7.3?
My guess is jellybean animations.
Few more devices.
Raft of new bug fixes.
Anything else?
Or just forget cm7.3 and use evolve jellybean?
Sent from my HTC Desire using xda app-developers app
dethrat said:
What's going to be new in cm7.3?
My guess is jellybean animations.
Few more devices.
Raft of new bug fixes.
Anything else?
Or just forget cm7.3 and use evolve jellybean?
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
huh Cyanogenmod 7.3? where did u see this?
jmcclue said:
huh Cyanogenmod 7.3? where did u see this?
Click to expand...
Click to collapse
There is no cm7.3 but cyanogenmod already announced cm7.x will carry on at a slower rate of development.
Just wondering where it will lead to.
Sent from my HTC Desire using xda app-developers app
Just bug fixes... optimizations.. new translations.. code clean up. My phone might be running an old engine but its a well maintained one.
via xda app
keystroke logging in 7.2
stankyou said:
Just bug fixes... optimizations.. new translations.. code clean up. My phone might be running an old engine but its a well maintained one.
via xda app
Click to expand...
Click to collapse
As long as automatic keystroke logs can be read by every application, I personally prefer rather to wait for CM 7.3 than to install CM 7.2
Have a look at this:
code.google.com/p/cyanogenmod/issues/detail?id=4735
When I stumbled over this, I couldn't believe it
They didnt changed anything in the nightly builds since 9 weeks (18th Nov).... looks like they stop developing and 7.3 only will become a big Bugfix-Release.
edit: http://changelog.bbqdroid.org/#bravo/cm7/1353824529
I would love CM10 on Desire, but they dont make it
I have VJ's CM10-ROM (Android 4.1.2, V3.0), whichs is really nice (beside a few minor bugs).
My phone is much smoother and faster with CM10.... i really cant understand why they dont bring CM10 for Desire
maybe android 4 is best choice.
maybe cm7.2 is last release for 7.x.
so..
Sent from my HTC Desire using xda premium
Malk4ever said:
They didnt changed anything in the nightly builds since 9 weeks (18th Nov).... looks like they stop developing and 7.3 only will become a big Bugfix-Release.
edit: http://changelog.bbqdroid.org/#bravo/cm7/1353824529
I would love CM10 on Desire, but they dont make it
I have VJ's CM10-ROM (Android 4.1.2, V3.0), whichs is really nice (beside a few minor bugs).
My phone is much smoother and faster with CM10.... i really cant understand why they dont bring CM10 for Desire
Click to expand...
Click to collapse
Its already been explain by cyanogenmod why they dropped support.
Sent from my HTC Desire using xda app-developers app
dethrat said:
Its already been explain by cyanogenmod why they dropped support.
Click to expand...
Click to collapse
So, a link would be nice... as far as I know they dropped because of the hardware limitation of the Snapdrogen Gen. 1.
But its proven that CM10(.1) works well.
Malk4ever said:
So, a link would be nice... as far as I know they dropped because of the hardware limitation of the Snapdrogen Gen. 1.
But its proven that CM10(.1) works well.
Click to expand...
Click to collapse
http://m.androidcentral.com/cyanogenmod-shelves-icsjelly-bean-support-snapdragon-s1-devices
I have to agree with cm for dropping support.
The general hackiness has always kept me away from jb/cm10 I gave up after 2 weeks as games and the system in general are slower.
For example try jetpack joyride in gb then try it in jb/cm10.
Sent from my HTC Desire using xda app-developers app
bump
any news on this?
jimbob857 said:
bump
any news on this?
Click to expand...
Click to collapse
I highly doubt anything is coming.
Sent from my Nexus 4 using xda app-developers app
Chromium_ said:
I highly doubt anything is coming.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Definitely no. Cyanogen team has moved on to 10.2.
If anyone claims CM7.3, it's his work of little tweaks here and there. Not officially supported.
Sent from my HTC One using Tapatalk 4
Cyanogenmod stopped the releasing nightlies back in March this year...
The most stable 'unofficial' CM 10.1.3 for me is http://forum.xda-developers.com/showthread.php?t=2368911
The latest cm version is 10.2..
Hey everyone,
I found this recently : http://forum.xda-developers.com/showthread.php?t=1485445&page=8
First post is a CM7 kernel for the ZTE Blade(Same MSM7227/ARMv6,but better screen than our Wildfire S.).
The poster mentions that it supports undervolting and GPU overclocking.......I'm going to give it a try later today,but I don't think it will work due to the large resolution difference.
(P.S. I did see this thread http://forum.xda-developers.com/showthread.php?t=710850 but it was last updated 2010,and the post I mentioned above was during the last days of Feb 2012).
+1
Sent from my HTC Wildfire S A510e using xda app-developers app
Can wfs devs make it for our devices
Cool!!!
Good to hear this...Hope it can work.
anyone working on this?
Well....
Dude AFAIK Undervolting and Overclocking are Kernal related stuff! So the screen resolution doesn't come into picture at all!!
Anyways.. All the best!!!
181charan said:
Dude AFAIK Undervolting and Overclocking are Kernal related stuff! So the screen resolution doesn't come into picture at all!!
Anyways.. All the best!!!
Click to expand...
Click to collapse
I know But I'm not a developer(not ATM, anyway), and the only thing stopping this from running on our devices is the different screen resolution. Just need someone to port this to HVGA screens, and it should work.
SunnyChrono6 said:
I know But I'm not a developer(not ATM, anyway), and the only thing stopping this from running on our devices is the different screen resolution. Just need someone to port this to HVGA screens, and it should work.
Click to expand...
Click to collapse
how would one go about doing this?
icu64 said:
how would one go about doing this?
Click to expand...
Click to collapse
I have absolutely no idea.
Really hope we get this
Sent from my Marvelc using Tapatalk 2
Do you think Android KitKat would be compatible with Wildfire? It is designed for lower end devices so would it be possible for a port of that new OS?
KoolKid98189 said:
Do you think Android KitKat would be compatible with Wildfire? It is designed for lower end devices so would it be possible for a port of that new OS?
Click to expand...
Click to collapse
Probably not. while it may technically be possible to achieve it is highly unlikely that anyone will be able to do it successfully, or even partially.
Just my 2 pence.
heavy_metal_man said:
Probably not. while it may technically be possible to achieve it is highly unlikely that anyone will be able to do it successfully, or even partially.
Just my 2 pence.
Click to expand...
Click to collapse
Fair but this could be a chance to breathe new life into our Wildfire, just saying.
KoolKid98189 said:
Fair but this could be a chance to breathe new life into our Wildfire, just saying.
Click to expand...
Click to collapse
I agree that it could be a very good opportunity, im just saying dont get your hopes up i suppose :/ we just about got got 4.1.2 from this dev here . alot of the "main players" have moved on from this device and i dont think we would have the skill to manage this. to start off with we would need a 3.4 kernel i believe, and i dont think they re-introduced support for non gpu devices in 4.3 kitkat so we would need to implement all the hacks that were required to get ics running and port them over to kitkat.
its a nice idea, but to be honest i think the amount of hours it would need to make it function may not actually work towards a stable daily driver
i`m amazed the wildfire got this far to be honest, and im happy i was here for it
heavy_metal_man said:
I agree that it could be a very good opportunity, im just saying dont get your hopes up i suppose :/ we just about got got 4.1.2 from this dev here . alot of the "main players" have moved on from this device and i dont think we would have the skill to manage this. to start off with we would need a 3.4 kernel i believe, and i dont think they re-introduced support for non gpu devices in 4.3 kitkat so we would need to implement all the hacks that were required to get ics running and port them over to kitkat.
its a nice idea, but to be honest i think the amount of hours it would need to make it function may not actually work towards a stable daily driver
i`m amazed the wildfire got this far to be honest, and im happy i was here for it
Click to expand...
Click to collapse
Yeah I to agree, also I wish there was a way to
So when android kitkat is released, I myself will try to port this, even if its not possible! I must still try
Sent from my HTC Wildfire using xda app-developers app
port?
that's not a proper word, we'll have to build it from scratch.
Wasimk32 said:
port?
that's not a proper word, we'll have to build it from scratch.
Click to expand...
Click to collapse
What is scratch ? You may say sources.And i think it's possible if erwin p and all the old dev come back and tried to build an new rom.
Sent from my HTC Wildfire using xda premium
Pator57 said:
What is scratch ? You may say sources.And i think it's possible if erwin p and all the old dev come back and tried to build an new rom.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Scratch is basically start from the beginning, and it's always better to try making a KitKat ROM for Wildfire, you never know what the outcome could be right?
Wasimk32 said:
port?
that's not a proper word, we'll have to build it from scratch.
Click to expand...
Click to collapse
Pator57 said:
What is scratch ? You may say sources.And i think it's possible if erwin p and all the old dev come back and tried to build an new rom.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Both are real words, just used in different context :thumbup: but yeah it would be defiantly a build from scratch job (using our own source code we would have to make specific to the wildfire)
Sent from my HTC Sensation XE with Beatse Audio Z715e using Tapatalk 2
So what we are waiting ?
For bigin, who is able to build or port an 4.2/4.3 kernel for our wildfire.
Sent from my HTC Wildfire using xda premium
Pator57 said:
So what we are waiting ?
For bigin, who is able to build or port an 4.2/4.3 kernel for our wildfire.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Ah, now that is the real question. If the kernel doesn't get made then this is dead before it starts like.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Pator57 said:
So what we are waiting ?
For bigin, who is able to build or port an 4.2/4.3 kernel for our wildfire.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
We are waiting for Android KitKat to be released, we need a device that has a QVGA screen with a resolution of 240 x 320 pixels
AFAIK it would run without a 3.4 or even a 3.8 kernel. But the current 2.6 kernel would slow it down. Only very experienced devs can make properly working kernels. And we have almost no 'real' "i build from source" dev left in this forum. (not offensive, i appreciate the work of any dev/porter/whatever here )
4.1 is also running fine with that old arco - kernel but its really slow maybe because of the hardware maybe because of the kernel. I think its a mix of both components.
I tried with @kylon to get a functioning overclock kernel for the htc wildfire bee, (cdma device) and we couldn't manage to get it stable, and that's the buzz's sister phone. It shares almost all the same hardware :/ so I don't think it will be an easy task.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
miniAndroidian said:
AFAIK it would run without a 3.4 or even a 3.8 kernel. But the current 2.6 kernel would slow it down. Only very experienced devs can make properly working kernels. And we have almost no 'real' "i build from source" dev left in this forum. (not offensive, i appreciate the work of any dev/porter/whatever here )
4.1 is also running fine with that old arco - kernel but its really slow maybe because of the hardware maybe because of the kernel. I think its a mix of both components.
Click to expand...
Click to collapse
Yea i know that all the dev have left the wildfire, but we can always learn and tried to building one.
Sent from my HTC Wildfire using xda premium
Pator57 said:
Yea i know that all the dev have left the wildfire, but we can always learn and tried to building one.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Yeah, hopefully this could be a success
KoolKid98189 said:
Yeah, hopefully this could be a success
Click to expand...
Click to collapse
Just my 2p worth but doesn't kitkat and the kernel associated with it look for integrated GPU's which the wildfire simply doesn't have, so if someone was to create a kernel for kitkat you would have to emulate a GPU on the CPU which would slow down the phone to a unusable piece of crap.
Good idea but i doubt it's viable.
DosKey123 said:
Just my 2p worth but doesn't kitkat and the kernel associated with it look for integrated GPU's which the wildfire simply doesn't have, so if someone was to create a kernel for kitkat you would have to emulate a GPU on the CPU which would slow down the phone to a unusable piece of crap.
Good idea but i doubt it's viable.
Click to expand...
Click to collapse
Agreed. Ics barely ran without the kernel hacks to make it run. Though it is said that kitkat should be less resource hungry.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
heavy_metal_man said:
Agreed. Ics barely ran without the kernel hacks to make it run. Though it is said that kitkat should be less resource hungry.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Click to expand...
Click to collapse
Yeah but did ICS have no GPU support? If it did then try porting the ICS hacks to KitKat and see how it goes.
KoolKid98189 said:
Yeah but did ICS have no GPU support? If it did then try porting the ICS hacks to KitKat and see how it goes.
Click to expand...
Click to collapse
While it's possible I have no idea what hacks were done to make it work. We needed kernel hacks for gingerbread.... The only one that would definitely know would be Arco, as he was the kernel developer for the buzz branch of cyanogenmod. I think most of the work on cm7 and 9 were arcos work, with some help from the guys here of course
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2