yashsingh1/xdaforums huggingface dataset:
[HTC Wildfire S] eoghan2t7:
If you want I can try and get the graphics acceleration going just send me to rom in its current form ;)
[HTC Wildfire S] insink71:
team

Next big thing for me is building that htc kernel source and seeing if it works for the marvelc'ers [which will allow them a slight upgrade to 2.3.5] and making a sleek custom rom for them. Then I can help; probably be freed up by end of Jan 2012. :) Besides, I always like it when the heavyweights go first [like CM team], gives me hope that I'll find some answers when roadblocks occur. Bleeding edge roadblocks make you crazy... You are truly alone when they occur. If the AOSP has ICS[which it does] and someone else has built it [stable;like CM team], I know it's possible; so, I'll stumble on in behind them, read all I can to avoid pitfalls they ran into, and generally, I've been lucky that way. :) In the meantime, I am always reading up, but I can't get in on the doing part until a bit later.

Rob
[HTC Wildfire S] benjamingwynn:
I uploaded the rom about 4 hours ago if nobody saw it. I also changed the first post (about 17 times ;-) )
[HTC Wildfire S] :
Well heres what i noticed: Its for gsm and wont boot on CDMA. Im going to replace your kernel with my kernel test it some. I probably can get it to boot. Other than that, i may be able to get by with adding libs to get it to work. i know touchscreen is a kernel problem for you. try using the one from the CM port
[HTC Wildfire S] benjamingwynn:
I am playing about with the kernel to get touch to work.
[HTC Wildfire S] d33ps1x:
Hdow big do the cache and system partitions need to be.

Hoping I don't have to touch my custom partitions to test. My 16 GB card is free now for testing. Promoted CM7x nightlys to my daily 32 GB card.

I've got 167 mb for system and 20 for cache right now. Enough B?
[HTC Wildfire S] benjamingwynn:
Yes that will be enough. It fits on my normal partitioned WFS. It's 90MB big. :)

Does anybody have any idea how to open boot-kernel.img and boot-ramdisk.gz.img?
[HTC Wildfire S] :
I have a dev who does my kernels. GB kernel would boot and work with most hardware for ICS. If your in the porting buisness, the way to go is use a working kernel, and then work on a true ics kernel after you get the OS perfected
[HTC Wildfire S] benjamingwynn:
I need to add the touch support into the kernel. It's on the first thread at the bottom (in raw code from github)

With the correct adjustments we could make this work on the WFS, we may not even need to change it!
[HTC Wildfire S] benjamingwynn:
click for touch screen fix I want to apply

Oh and this is my hundredth post in XDA. So I'm going to add a lot of smilies at the bottom to celebrate this.

:o:):(:confused::mad::p;):D:rolleyes::cool::eek:
​
[HTC Wildfire S] d33ps1x:
If you just want to get at the files and not put them back together you could use this tool windoze

Would love to know how to re-yaff to a yaff image.

Windows Binary:

http://androidforums.com/samsung-i7500/136176-how-extract-files-nandroid-backup-windows.html

Project Site:

http://code.google.com/p/unyaffs/downloads/list
[HTC Wildfire S] benjamingwynn:
Thanks! But to put them back together I have to....................
[HTC Wildfire S] :
Try using the android kitchen. It will do it for you and even recompile it.
[HTC Wildfire S] d33ps1x:
http://en.wikipedia.org/wiki/YAFFS

http://code.google.com/p/yaffs2utils/ (Linux only)

Google. Love it.
[HTC Wildfire S] benjamingwynn:
Thanks. I haven't got kitchen yet (WinRAR FTW!) but I will check it out.
[HTC Wildfire S] benjamingwynn:
1) Is it this?

2) If it is how do I add the WFS to the list. It says I need to do something like change the configuration files :eek:
[HTC Wildfire S] :
thats it but thats an old article. Look for it on the forums here for the newest one. The newest just works, lol. Stick your zip in and do what you want
[HTC Wildfire S] d33ps1x:
Here I Believe
[HTC Wildfire S] :
yeepp thats it
[HTC Wildfire S] benjamingwynn:
Anybody have anything new? Fixes, etc. I'm still working on the touch.
[HTC Wildfire S] eoghan2t7:
Not yet still working on graphics acceleration I hope to get it working tomorrow ;)
[HTC Wildfire S] benjamingwynn:
Cool. I have cygwin running on windows now so its time to use the kitchen to start recompiling that boot.img and hope for a working touchscreen.

Best of luck with your graphics acceleration! :)

P.S. are you using marvel or a different type of marvel?
[HTC Wildfire S] eoghan2t7:
I'm using a marvel from Carphone Warehouse ;)
[HTC Wildfire S] dudong:
all the same, thank you for your hark work , im looking forward to seeing this , you take us the hope.
[HTC Wildfire S] benjamingwynn:
I have been Googling for 2 days now and I can't find how to add ATMEL.C to the rom! It's a driver for the touchscreen on github that fixes most HTC touchscreens running ICS.

The link is here - if anybody knows how let me know and I will add it immediately.

P.S. I know the buzz is the Wildfire but it can be used on other devices and apparently it works. :)
[HTC Wildfire S] benjamingwynn:
But how do we get these files into the rom? I have extracted boot.img and can't see them there. I can't extract zImage because there aren't any tools for it (as far as I could find)

Without somebody who has ported stuff before we can't do this ( ;) at alquez :) )

https://github.com/keiranFTW/buzz-k...dbf979912da/drivers/input/touchscreen/atmel.c

https://github.com/CyanogenMod/htc-...m7227-2.6.35/arch/arm/mach-msm/board-marvel.c
[HTC Wildfire S] (IwaN):
Great, guys!! Hope it will be finished to 100% fully working ROM :)
[HTC Wildfire S] :
You would add that file in the kernel my friend. That means you must recompile your kernel (AKA rebuild from scratch, dont know how because i have someone who does my kernel for me) Its something you have to do in Linux
[HTC Wildfire S] benjamingwynn:
Is this what I'm looking for?

http://forums.androidcentral.com/ht...how-build-your-own-kernel-package-source.html
[HTC Wildfire S] :
Well, thats a good place to start but its a little out dated. You will need your kernel source, from htc, and you should probably just use the AOSP kernel source for ICS if you dont mind testing. Then you just got to add files into the folder and set up the configs correctly. THats about all i know, as i have my own dev lol. Its really nice
[HTC Wildfire S] eoghan2t7:
im going to download the ics repo later and see if i can build it from source correctly ;)
[HTC Wildfire S] :
Whoever's doing the porting can strip the Android Beam function 'cos we won't need it, unless someone changes the hardware, or makes Instant Bluetooth.
[HTC Wildfire S] eoghan2t7:
whats android beam?
[HTC Wildfire S] insink71:
guide(s)

That is indeed a good guide.. I read one quite similar with adding the HTC source in, but that would be for the current [gingerbread] kernel [it also specified to use Ubuntu 9.04]... Seems to contain the necessary elements; Here's another guy I read [develops for bravoc; dastin1015] about compiling ICS.

Regards,

Rob
[HTC Wildfire S] *se-nsei.:
The Near-Field Technology™ bumpin' stuff.
[HTC Wildfire S] benjamingwynn:
- this post is long but try to read it all! -

Good point about the beam stuff. I have been busy today and I might be doing stuff tomorrow so I might not be able to build a kernal from source. If anybody beats me too doing this then build from alquez's cm7 port kernal as it boots from that. If you know what your doing then attempt to add the file from the last link in the first post (touch fix) and then build. After that test. If it works then upload your boot.img here and I will add it.

I may be a noob at porting. But I am up for a challenge. Someone has to start somewhere. Try to help me help you. The quicker somebody helps me by uploading/giving advice/testing the quicker this gets fixed.

And I think I have fixed this to run on cdma devices ;)
[HTC Wildfire S] d33ps1x:
Good news. Perhaps Insink can give it a spin...
[HTC Wildfire S] benjamingwynn:
Hopefully. But the touch is still dogey. I would like to know if it just booted though.

I don't have access to marvelc or marvelct devices

Edit : typo! Changed marvel to marvelc
[HTC Wildfire S] insink71:
If the OP's link is to the marvelc fixed, latest and greatest version, I'm about to give it a whirl.

Rob

Sent from my HTC Wilfire S A510c
[HTC Wildfire S] csoulr666:
Android beam won't work on the wildfire s....An NFC chip is needed for it which the WFS lacks...
[HTC Wildfire S] insink71:
Ok. Tested [sort of].

It boots :)

Touchscreen challenge

Hard buttons [volume/power] work

Lockscreen works

I really couldn't test too much without the touchscreen, but from a developer's standpoint... It does look promising :)

Sent from my HTC Wilfire S A510c
[HTC Wildfire S] benjamingwynn:
Does anybody know how fast android beam is? Could hack it to use Bluetooth instead. Bluetooth 3.0 (what the wfs runs) is fairly fast.

Anyway back to development of touch. We will focus on extras later.

Any progress?

Sent from somewhere too far away from my computer
[HTC Wildfire S] alexyie:
It would be Bluetooth file transfer then

Sent from my A953
[HTC Wildfire S] benjamingwynn:
Yeah. But we could allow it to intergrate with the system and use the api's.

Sent from somewhere too far away from my computer
[HTC Wildfire S] aparici:
I think that we need a team that with the support of cm could make oficial versions of CM. What do you think devs?
[HTC Wildfire S] benjamingwynn:
CM9? We need the aira to be officaly ported first. Then we can use alquez's cm7 files on his github, port them and then build from both sources.

If you mean make cm on our phones alquez has a port.

Or did I totally mistake your words?

Sent from somewhere too far away from my computer
[HTC Wildfire S] benjamingwynn:
Okay here's my plan for tomorrow.

1) eat breakfast then install ubuntu - DONE, TOO BUSY FOR BREAKFAST. USED LINUX MINT BECAUSE I HAD A DISK LYING ABOUT

2) download alquez's kernel from github - DONE, GITHUB IS CONFUSING.

3) add files for touch fix in kernel -DONE, WAITING FOR COMPILE >.<

4) recompile kernel - DONE. IT'S IN ROM NOW...

5) add compatible libs - DOING LATER. MAYBE NOT TODAY

6) change build.props - DONE

7) build rom - DONE.

8) Test. Moment of hope... - in case of failure revert to step 3/4

9) screenshoot

10) upload to xda as well as editing post

11) watch the happy comments come in

12) [optional] play minecraft ;) - DONE [I know! I should have done Kernel first ;)]

Sent from somewhere too far away from my computer
[HTC Wildfire S] benjamingwynn:
^^^^^^^^^^^^^^^^^^^^^^^^

above post

I'm so exited about ICS!! I hope it boots. If not I will have to edit this post and put a slimly or a unhappy face. Who will see the face first??

Grin = Everything works. (very, very unlikely)

Smiley = Booted. ICS touch fixed

Un-smiley= Booted. ICS touch not fixed

MAD = Didn't boot

MADx100 = Bricked phone

:(
[HTC Wildfire S] benjamingwynn:
Okay. I replaced the atmel.c with the new ics one and....well.... the same. ****ty touch screen.

Sent from somewhere too far away from my computer
[HTC Wildfire S] modpunk:
Anything in the kernel ring buffer about it?
[HTC Wildfire S] benjamingwynn:
I've uploaded it with new build.prop amongst other things. Go ahead and download it.

I think I still have an idea on the touch... it's just applying it to zImage that's the problem for me.
[HTC Wildfire S] modpunk:
A binary blob without the source code doesn't help me to understand what's going on or wrong :)
[HTC Wildfire S] benjamingwynn:
I used alquez's CM7 kernel. Overclockable and clean. Works on all marvel* devices

and Boots.

Link to the github repo is here
[HTC Wildfire S] benjamingwynn:
Updated post to include logcat from boot to home. I also launched a few apps, managed to get to the home screen and then attempted to apply a live wallpaper.
[HTC Wildfire S] benjamingwynn:
I have (possibly) built a full ics rom with camera and touch fix. I can't flash it because of an error : "error 7 - could not access /tmp/boot.img"

Tried in RZR and CWM recovery. Tried fixing permissions. Yes I wiped everything.

Help!!!!!!!!!!! Also my laptop is in for repair for the next two weeks so I wont be testing for a while.

Sent from somewhere too far away from my computer
[HTC Wildfire S] eoghan2t7:
send e your updater-binary fro the meta folder in the update.zip sounds like the update.zip have got messed up or if you can upload the complete package for repackaging that would be easier ;)

p.s. i currently porting sense 3.5 just hope she boots lol
[HTC Wildfire S] aparici:
If you build it, upload and i could try flash.

Enviado desde mi HTC Wildfire S A510e usando Tapatalk
[HTC Wildfire S] benjamingwynn:
Jikintaru managed to boot it. Nothing worked though. He didn't upload it as well. I don't have my PC.

Sent from somewhere too far away from my computer
[HTC Wildfire S] benjamingwynn:
Can you build roms on phones? I didn't think so. :)

My laptop is in for repair for (what they say will be) two weeks

Sent from somewhere too far away from my computer
[HTC Wildfire S] aparici:
Sorry man i didn't read that you didn't have the computer. I understood that you hadn't the phone.
[HTC Wildfire S] benjamingwynn:
Its fine I was only messing. Btw I do have phone just not PC.

Sent from somewhere too far away from my computer
[HTC Wildfire S] InsaneDDay69:
I am tinkering with this, as I do not want to see this project die off. I tried inserting the kernel from the newest CM7 version and got a full boot, but painfully challenging touch. I am trying with a kernel from another from now, hopefully it installs and works better. If someone can link me to the CM source and drivers for the marvel, I will try to build one from scratch. I will search on Google for them as well, so don't think I'm asking for links to be lazy lol

*edit* 2nd attempt wouldn't install, error status 7. I'll try again with a new kernel.

Sent from my ICDroid X
[HTC Wildfire S] intel007:
https://github.com/alquez

Maybe this will help

Also check these latest reply's by alquez

http://xdaforums.com/showthread.php?t=1226765
[HTC Wildfire S] benjamingwynn:
I have been building a kernel to fix touch... but I don't have my laptop for about 2 weeks so I can't build it now - it's in repair.

Sent from somewhere too far away from my computer
[HTC Wildfire S] InsaneDDay69:
I'm having trouble compiling the kernel. The tool chain runs, but it doesn't create the zimage. Anyone have any tips for this? I've read a how to on here and rootzwiki and neither one had any answers.

Sent from my ICDroid X
[HTC Wildfire S] :
Try adding zimage in there. I can't remember where. I'm working on fixing stock right now then ill try ics. Maybe build a true ics kernel. Pull in things u need n use the prebuilt or ndk tool chain.
[HTC Wildfire S] InsaneDDay69:
Hadn't thought of the NDK tools. Thanks for reminding me.

Sent from my ICDroid X
[HTC Wildfire S] :
No problem. Thought is help as I fix the sense kernel sources.
[HTC Wildfire S] InsaneDDay69:
I have read a dozen "how to compiles" and tried every trick I could find. I've tried the NDK and it tells me that the gcc command can't be found. Basically my kernel was alquez's CM port with a HTC ICS touch fix replacing the CM atmel.c. I can't figure out what is going wrong, so if anyone can point me in the right direction I would appreciate it greatly and hopefully we can get ICS running. I have used it on an Incredible, and run it daily on my Droid X "tablet," and I love it.

edit- here are my terminal outputs, amybe that will explain a bit better lol.

that was from the NDK

that was with sourcery and hikari toolchain 4.4.4

Sent from my ICDroid X
[HTC Wildfire S] benjamingwynn:
My kernel came out at /arm or something in the source directory. I can't really remember off the top of my head.

Sent from somewhere too far away from my computer
[HTC Wildfire S] InsaneDDay69:
I would have something if my compilers weren't stubbing up lol

Sent from my ICDroid X
[HTC Wildfire S] anryl:
In u'r ~/android-ndk-r7/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-eabi-gcc

or ~/android-ndk-r7/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/gcc

then u have to do CROSS_COMPILE=arm-eabi- or CROSS_COMPILE= it is just the command that is wrong

he didnt found make: arm-linux-androideabi-gcc: Command not found

this means the file ~/android-ndk-r7/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc was not found

the zImage will be then in / arch / arm / boot
[HTC Wildfire S] benjamingwynn:
When I get my laptop back I will work on fixing the touch and soft buttons. My kernel is a slightly modified version of alquez's one on his github, it allows us to overclock and is cleaned up to work with ics nicely.

Does anybody know how to fix the touch problem? I replaced atmel.c but the problem still remains.

Sent from somewhere too far away from my computer
[HTC Wildfire S] eoghan2t7:
What are the touch problems again I can ask the gt540 ics developer for ideas?
[HTC Wildfire S] benjamingwynn:
Off target, soft buttons act as part as screen and screen is not recognised as a touchscreen but a pointer (shows circle where it's tapping)

Sent from somewhere too far away from my computer
[HTC Wildfire S] brandonhun:
Screenshots + Info

So I have flashed this ROM to my MarvelC, it wouldn't boot at first until I flashed a separate Kernel, but then it worked.

I have also found that the camera is not "connecting" to the device. I Wish I had some sort of help other than just taking screenshots,but that's almost all I know how to do. xD
[HTC Wildfire S] benjamingwynn:
I'm guessing you had the touchscreen problem too. Camera is to do with the libs. Anybody got anywhere with the touchscreen problem yet? I am going to ask some other ics porters if they know what the problem is.

Oh and can you upload that rom with the new kernel in it? I would do it myself but with no pc I can't.

Sent from somewhere too far away from my computer
[HTC Wildfire S] benjamingwynn:
Expect a touch fix this week :-)

Sent from somewhere too far away from my computer
[HTC Wildfire S] brandonhun:
I didn't put the kernel into the ROM itself, I had trouble powering the device on (would get stuck at splash screen), so I went back into recovery and flashed this kernel (being for the CM7 port)

*seeing that the original file isn't valid anymore, I have re-uploaded it HERE*
[HTC Wildfire S] eoghan2t7:
I'm going to try something tomorrow with the gt540 ics port.
[HTC Wildfire S] InsaneDDay69:
Can't wait to see it, I'm still having compiler issues lol

Sent from my ICDroid X
[HTC Wildfire S] :
Try lookin at your tool chain. You need the proper links and permissions. I know there are problems with the stock kernel source
[HTC Wildfire S] InsaneDDay69:
I think the source is what's causing my problem. I'm getting "errors" caused by files in the kernel source itself. I've tried fixing the files based on a stock kernel, but either new ones come up, or the same come back again. I'm continuing to do research to try and fix the problems.

Sent from my ICDroid X
[HTC Wildfire S] benjamingwynn:
Good work. And good luck! I need someone to try adding the following to the rom for me. I don't have a pc and with only my wildfire S I need help. The link is bellow.

If you need to compile from source use alquez's kernel. It's on his github. It's the only thing that boots ics as far as I know.

http://xdaforums.com/showthread.php?t=1332605

Sent from somewhere too far away from my computer
[HTC Wildfire S] InsaneDDay69:
Thank you! I'll take a look at adding that in a bit. I have been using alquez's sources, but I've tried 2 different kernels even without modifying them I get errors. I'll keep on it because I have used his kernel to boot the rom, so it seems to be the best start point.

Sent from my ICDroid X
[HTC Wildfire S] :
Try this.

Make clean

Make -j ARCH=arm CROSS_COMPILE=(YOUR TOOL CHAIN)
[HTC Wildfire S] InsaneDDay69:
that done the trick. I got it to compile alquez's wildfire s kernel with the addition above. Boots, is not in pointer mode, but touch doesn't work at all. I will be reinstalling my ubuntu later, but I saw another fix I will try once I get running again.

Sent from my ICDroid X
[HTC Wildfire S] benjamingwynn:
Shame. Don't use the first post. There's better fixes and stuff on the last pages of the thread.

Again good luck.

Sent from somewhere too far away from my computer
[HTC Wildfire S] InsaneDDay69:
https://github.com/TwistedUmbrella/l...screen/atmel.c

https://github.com/TwistedUmbrella/a...ouchscreen.idc

are those the ones you are referring to?
[HTC Wildfire S] benjamingwynn:
Yep! But there's better ones for a more similar phone - wildfire - over in kerianftw's github.

Sent from somewhere too far away from my computer
[HTC Wildfire S] benjamingwynn:
Any luck?

Sent from somewhere too far away from my computer
[HTC Wildfire S] InsaneDDay69:
I'll check there, the .idc link doesn't work anymore. Seems like the wildfire used a different TS driver though. Either way I'll look into it :)

Sent from my ICDroid X
[HTC Wildfire S] benjamingwynn:
Can't wait for my laptop to be fixed. I would fix it myself but the warranty is two years and I've only had it one so I don't want to void the thing.

Tell me if you get luck with the touchscreen please! There's one file you must place: tochscreen-atmel.imc and you must replace atmel.c ---- these are both inside the kernel.

Sent from somewhere too far away from my computer
[HTC Wildfire S] InsaneDDay69:
i need to find the other file and where it goes. the link for twistedumbrella's idc is broken now (i assume he removed the file or moved it to another location). kieran's only has the atmel.c, but no other file similar to the one you are looking for. i'm still on the hunt for them though, and will report back with anything i find or achieve/fail. we will get the screen working, then the fun begins with getting the rest going lol.
[HTC Wildfire S] eoghan2t7:
Not yet I'm in the process of replacing files etc for WiFi and stuff I hope it works lol
[HTC Wildfire S] :
Glad my Command helped. Im lookin into this for the cdma side. Happy hunting every one.
[HTC Wildfire S] InsaneDDay69:
that's what I'm on, VM CDMA. Fresh install on my pc, compiler is acting up again, but I'll get it.

Sent from my ICDroid X
[HTC Wildfire S] InsaneDDay69:
i think we have the same phone. is yours the VM marvelc? if it is, could you possibly do an adb pull of your config file and send it to me? i have the SDK installed and running, but my adb says "command not found." i think having an actual .config to base the kernel build on may help solve my newly rediscovered compiling pains. i guess terminal or ubuntu just hate me lol.
[HTC Wildfire S] benjamingwynn:
Linux hates everyone. How's touch comming on? Remember that this is for all marvel* devices.

Sent from somewhere too far away from my computer
[HTC Wildfire S] benjamingwynn:
I know I said this week but I wondered if anyone beat me to it. :-)

Sent from somewhere too far away from my computer
[HTC Wildfire S] :
Yeah I can pull the config. I may have one. I just got to flash cm and pull that and we will have the cdma config.

Further setup required however. Must run defconfig and menuconfig command as well.
[HTC Wildfire S] InsaneDDay69:
I'm hoping that it will run on all marvels, I only have a marvelc to test on though. I am using CM7 as the kernel base and will only tweak what is needed for touch.

Sent from my ICDroid X
[HTC Wildfire S] benjamingwynn:
I've got a pc now so I better get cygwin and get started!

Sent from somewhere too far away from my computer
[HTC Wildfire S] d33ps1x:
Cool. Looking forward to it.
[HTC Wildfire S] :
Cygwin won't work. Just make a vm, and use like mint Linux. Windows will only work with a virtual machine cause of the ntfs partitioning.
[HTC Wildfire S] benjamingwynn:
Cygwin worked last time ;)

Sent from somewhere too far away from my computer