yashsingh1/xdaforums huggingface dataset:
[HTC Wildfire S] jmz:
I would suggest using a sense 3.5 kernel dumping it and comparing the ramdisk to the sense 4 stock one. I say sense 3.5 because it has been modded already so there should only be minor changes to make. Specifically looking at init.rc and prolly device.init.rc
[HTC Wildfire S] dudeman1996:
This I'm gonna try now, that's if no one else beat me to it :p
[HTC Wildfire S] Eskuero:
Did you think the we must to delete the word "golfu" for every .rc file, and "marvel"?:D

Like por example:

ueventd.golfu.rc

---------------------------

ueventd.marvel.rc
[HTC Wildfire S] jmz:
No. I would diff theirs with yours and see if there is any ics specific changes. Ignore hardware changes
[HTC Wildfire S] benjamingwynn:
Done, modded.

Problem: adb doesn't see the device.

Q. Binarys in ramdisk should be from

A. Cm9

B. Sense 3.5

C. Sense 4
[HTC Wildfire S] Eskuero:
Builded with Sense 3.5 bins, and pushed, waiting for dudeman test:D
[HTC Wildfire S] jmz:
Device specific.
[HTC Wildfire S] benjamingwynn:
What are you saying are device specific? The bins?
[HTC Wildfire S] Eskuero:
I think that he means Sense4 original

Enviado desde mi HTC Wildfire S A510e usando Tapatalk
[HTC Wildfire S] jmz:
Well more like CPU type dependent
[HTC Wildfire S] Eskuero:
We have add ones from Sense3.5 port from Pico, must work?

Enviado desde mi HTC Wildfire S A510e usando Tapatalk
[HTC Wildfire S] benjamingwynn:
No they are the ones from marvel.
[HTC Wildfire S] cloudzxz:
Can you get this rom boot atm ben ?:)
[HTC Wildfire S] Eskuero:
It's possible, but difficult(:

Enviado desde mi HTC Wildfire S A510e usando Tapatalk
[HTC Wildfire S] jmz:
Btw new leak posted on op
[HTC Wildfire S] benjamingwynn:
"Sorry, you are limited to 8 thanks per day"
[HTC Wildfire S] csoulr666:
Don't worry........i thanked him for you :D
[HTC Wildfire S] Eskuero:
I think that we didn't must to update now, first we must to get logcat working(?

Enviado desde mi HTC Wildfire S A510e usando Tapatalk
[HTC Wildfire S] dudeman1996:
We're trying...
[HTC Wildfire S] seaskyways:
Guys , I just wanted to tell you that I took my hand out of this forum = I won't be contributing in anything , so the Sense 4.0 clock and lockscreen project that i made was a nice job but almost nobody looked at it although it was great ... Now I went to the Desire HD forum since I might be buying one so soon , plus , I ported a ROM and my work was greatly appreciated , so I was happy that there are some people that are seeing what I do (I don't mean that you guys are dumb , but that this phone is not held as much as the Desire HD , so there is more attention) ... For now , I will be looking at your progress guys and I wish all the good luck , PEACE OUT !!
[HTC Wildfire S] island3r:
Guys the Golf has an armv7 soc which compared to the wfs' armv6 uses a different instruction set. So while apks from that RUU might work with some modding, anything else (kernel/libs/bins) certainly won't. So what you need to even get logcat to work is a donor ICS rom to get the necessary files. Most probably an aosp based one.
[HTC Wildfire S] dudeman1996:
Aware of this. We're trying to get a kernel with logcat working, but it's taking a while.
[HTC Wildfire S] benjamingwynn:
Indeed. Heroc (or hero, i cant remember) have it booting from our sources, if dudeman1996 fails on the next test with kernel then I will say proudly that it is not kernel.
[HTC Wildfire S] jmz:
Statistically 90% of logcat issues on ports is kernel
[HTC Wildfire S] benjamingwynn:
Indeed, but kernel is pretty worn out in testing. I'm hoping this commit will fix a lot of issues as the person above said:

https://github.com/wfsdev/marvel-golf-port/commit/5cb2644d3388b682a74d0ba04a5859309969c1ab

- Benjamin
[HTC Wildfire S] *se-nsei.:
What is your kernel based off? Have you tried the CM9 2.6.35?
[HTC Wildfire S] benjamingwynn:
Sense 3.5 - We have tried a bunch of different zimage's but none have gotten us a full boot. I now blame the xbin folder for not having many things in it, including some shell stuff.
[HTC Wildfire S] Coentje44:
Im porting Sense 4.0 roms for Galaxy Nexus and Nexus s.

Add me on gtalk: androidwoz@gmail.com
[HTC Wildfire S] Eskuero:
Logcat is working now...:D:D:D:D:D:D:D:D:
[HTC Wildfire S] jmz:
What was it?
[HTC Wildfire S] dudeman1996:
Oliver used stock CM9 kernel with ARMv6 libs :D
[HTC Wildfire S] benjamingwynn:
libs, bins and xbins that I added lol :)

Oliver had the brains to try a different kernel with the combination and well... booted it. I am jealous of him booting it first though :D

I can't keep my excitement contained.. must...not...troll :D :D :D
[HTC Wildfire S] Eskuero:
I've add logcat.txt on sources, you can read it:D

I'm excited, this night I can't sleep:D:D:D:D:D:D:D
[HTC Wildfire S] benjamingwynn:
Heres a list of things failing

/system/lib/hw/camera.marvel.so (camera)

/system/lib/libc (graphics)

I'm guessing wifi will fail because the modules aren't built for the kernel we're using.
[HTC Wildfire S] Eskuero:
btw now we need to fix graphics, for test if any other thing is working...(:
[HTC Wildfire S] benjamingwynn:
Silly me, after using Google it is not libc's fault. It is surfaceflinger
[HTC Wildfire S] Eskuero:
That are the graphic giltches:

https://github.com/wfsdev/marvel-go...17f908b88f69a2b1941d4/2012-05-23 22.29.46.jpg
[HTC Wildfire S] eoghan2t7:
Have you swapped out the egl folder from cm9 into this port?
[HTC Wildfire S] benjamingwynn:
Yep. Lemme double check that though...

EDIT: Yep the same.
[HTC Wildfire S] *se-nsei.:
Heheyy, what did I just say hm? :D :D Joking, one step forward!
[HTC Wildfire S] eoghan2t7:
I would download it and check stuff but I'm getting my sh1t together for the funeral tomorrow.
[HTC Wildfire S] benjamingwynn:
Hm okay. I think it may be something kernel related, since this is a non sense kernel we are using.
[HTC Wildfire S] Eskuero:
btw that's the big problem, seems like surface flinger can't start graphics lib... I'm going to test that now with Sense 3.5 kernel stufff, and with libc from CM9 port... :D

I/SurfaceFlinger( 2033): SurfaceFlinger is starting

I/SurfaceFlinger( 2033): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...

F/libc ( 2033): Fatal signal 8 (SIGFPE) at 0x000007f1 (code=0)

F/libc ( 2035): Fatal signal 11 (SIGSEGV) at 0x00000004 (code=1)

I/ ( 2053): ServiceManager: 0xf958
[HTC Wildfire S] benjamingwynn:
We are already using the one from cm9. Surface flinger isn't the problem. It's in the kernel. ;)
[HTC Wildfire S] Eskuero:
In our resources we isn't be using libc from CM9, in latest build you change surfaceflinger.so and libc.so, but if it's possible that Surface Flinger can't bot again that... btw I'm going to test, if not works, we can delete this possibility...:D
[HTC Wildfire S] benjamingwynn:
I actually rolled back the change ;)
[HTC Wildfire S] benjamingwynn:
Hehe, look what I made :D
[HTC Wildfire S] davidang:
Not bad
[HTC Wildfire S] Eskuero:
Loooool, don't waste your time on ****:mad:
[HTC Wildfire S] benjamingwynn:
Lol, I was waiting for you to test it :D
[HTC Wildfire S] benjamingwynn:
Fixed graphics :D
[HTC Wildfire S] Eskuero:
We've fixed the loading of HW Graphics, didn't say nothing wrong on LOgcat, but the Screen stay on black color...:(
[HTC Wildfire S] dudeman1996:
It felt so awesome when I turned on the phone and it went to a black screen. I thought it was gonna boot...
[HTC Wildfire S] jmz:
Does logcat just stop too?
[HTC Wildfire S] dudeman1996:
No logcat keeps bootlooping. I think it gets to the bootanimation but we can't see it for some reason. The screen's just black.
[HTC Wildfire S] jmz:
So logcat has to error on something to bootloop
[HTC Wildfire S] dudeman1996:
Yeah, afaik it's error-ing on audio
[HTC Wildfire S] Eskuero:
The biggest errors on logcat are now that:

E/HTC Acoustic( 81): Fail to open /system/etc/AudioPara_HTC-WWE.csv -1

-------------------------------------------------------

I/CameraService( 81): CameraService started (pid=81)

E/HAL ( 81): load: module=/system/lib/hw/camera.marvel.so

E/HAL ( 81): Cannot load library: link_image[1965]: 81 could not load needed library 'libcamera.so' for 'camera.marvel.so' (reloc_library[1314]: 81 cannot locate '_debug_pthread_create'...

E/HAL ( 81): )

E/CameraService( 81): Could not load camera HAL module

-------------------------------------------------------

I/AudioPolicyService( 81): Loaded audio policy from LEGACY Audio Policy HAL (audio_policy)

W/dalvikvm( 80): Unable to register: not native: Landroid/graphics/Paint;.setColor:(I)V

E/JNIHelp ( 80): RegisterNatives failed for 'android/graphics/Paint', aborting

Possible the latest one is which is producing bootloops, and gives us black screen...:confused:
[HTC Wildfire S] jmz:
Try just deleting boot ani and sound. See if that gives diff results. First one is pretty selfexplantory. Use the marvel csv files
[HTC Wildfire S] dudeman1996:
Anyone got any ideas on this? Apparently it's a framework.jar error.

+W/dalvikvm( 80): Unable to register: not native: Landroid/graphics/Paint;.setColor:(I)V
+E/JNIHelp ( 80): RegisterNatives failed for 'android/graphics/Paint', aborting
+F/libc ( 80): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
[HTC Wildfire S] benjamingwynn:
Yep, that's our main problem now. We will be working on this tomorrow too.
[HTC Wildfire S] jmz:
Sorry just had to mention the error hex code. Dead bad....lol
[HTC Wildfire S] ajrty33:
Yay!!

This is where i'm bootlooping :)

try replacing Paint.smali in framework.jar with cm9's
[HTC Wildfire S] dudeman1996:
"We work hard to ensure each of our products has the optimal user experience and therefore some products will remain at their current version of Android. In general, devices with 512MB ROM or less will not be upgraded to Android 4.0. These devices include the HTC ChaCha, HTC Salsa, HTC Wildfire S, HTC Explorer, and others."

Just thought I'd share that from the HTC website.
[HTC Wildfire S] dudeman1996:
I tried replacing framework.jar with sense4 one. But it just gave worse errors. I've got 2 zips ready, one just cm9's framework.jar and one with sense3.5's, I'll be trying them both after school today and if it doesn't work then I'll try this :)
[HTC Wildfire S] dudeman1996:
Okay the framwork.jar's from sense3.5 and CM9 don't work. Just throws fatal errors in logcat. Henry_01 extracted the paint smali files from CM9's framwork.jar, we both tried to decompile sense4's framework.jar but it's just not working - apktool gives us an error.
[HTC Wildfire S] dudeman1996:
I decompiled classes.dex from framework.jar and fixed up the paint.smali files. I had to do it manually using a newer version of baksmali - apktool uses an old version. Anyone know how to recompile it into a framework.jar?
[HTC Wildfire S] Eskuero:
I've compile already it into framework, without problems, pushed into git then, but I don't know if it works...:confused:

I'm building ROM now...:D

---------- Post added at 08:06 PM ---------- Previous post was at 07:47 PM ----------

Oks, now the problems while loading Paint from framework.jar is fixed already, but now, we can't pass HTC white Screen, because system is bootlooiping around that:

http://pastebin.com/DhatGdRd
[HTC Wildfire S] dudeman1996:
Goddamn surfaceflinger.. We will stop at nothing until this is fixed! :D
[HTC Wildfire S] Eskuero:
btw, It's possible that one problem is that.. the ****ing surface flinger now...:(

I/DEBUG ( 77): pid: 117, tid: 117 >>> /system/bin/surfaceflinger <<<

I/DEBUG ( 77): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 01c60020
[HTC Wildfire S] whoqwerty:
hope this works, good luck guys!
[HTC Wildfire S] benjamingwynn:
It's not surfaceflinger dummy ;)

Like I've said before, look through the traces, you will find that: /system/lib/libpixelflinger.so and /system/bin/mediaserver are the problems (as far as I can see) - at the moment I'm having trouble pulling because of the (80mb+ big) decompiled file that we don't even need any more.

I think that looking into these files and replacing them from other places should fix it. Somebody else could have a look at the logcat oliver posted above if they think they have a better lead on what's going on of course :D
[HTC Wildfire S] dudeman1996:
Hey hey I said I'll delete it when I get home...
[HTC Wildfire S] eoghan2t7:
Guys in ics msm7k does not exist so change

ro.board.platform=msm7k

To

ro.board.platform=msm7x27

And see what happens.
[HTC Wildfire S] Eskuero:
Ok, that's build.prop, i'm going to test(:

Edit: dudeman1996 have tested that yet, nothing change on logcat...

Enviado desde mi HTC Wildfire S A510e usando Tapatalk
[HTC Wildfire S] benjamingwynn:
Last logcat is basically the same. Again, ignore some stuff that catches your eye instantly, like surfaceflinger - and look whats causing them:

Surfaceflinger (a run time for what comes up on the screen next) traces back to:

/system/lib/libnetutils.so

/system/lib/libui.so (probably nothing to worry about - libui is obviously going to need this - and think it may have caused something to do with the crash)(=

/system/lib/libsurfaceflinger.so (it's own library)

/system/lib/libgenlock.so

/system/lib/libpixelflinger.so

/system/bin/linker

Mediaserver traces back to:

/system/lib/libui.so (but for some odd reason it gives us this:"(_ZN7android14InputPublisher18appendMotionSampleExPKNS_13PointerCoordsE)" after the trace)

/system/lib/libbinder.so

/system/bin/linker

/system/lib/libmedia.so

PLEASE NOTE THAT I CHANGED SOME OF THE FILES ABOVE AND IT GAVE THE SAME RESULT: https://github.com/wfsdev/marvel-golf-port/commit/439a48ac12111614a477c102c84619e675aedd87

Now - if we bring out whats failing between both we can see that the following fail:

/system/bin/linker

/system/lib/libui.so

However - we can cross off linker because (i guess) it just handles symbolic links in the system (i'll need somebody to confirm this)

So this must be libui.so if the same thing is causing both bootloops (if the are causing both) - but why??

EDIT: I will swap em' back to CM9's files now from here: https://github.com/wfsdev/marvel-golf-port/commit/439a48ac12111614a477c102c84619e675aedd87. But expect the same thing.
[HTC Wildfire S] Eskuero:
Loool, we got bootanimation, old Android bootanimation...:D

http://dl.dropbox.com/u/65311062/Capturas de pantalla/Animación de Inicio.png

Now, surfaceflinger didn't gave us any problem, btw new bugs appeared, like DexOpt:

I/dalvikvm( 136): DexOpt: not resolving ambiguous class 'Lcom/htc/htcjavaflag/HtcBuildFlag;'
[HTC Wildfire S] jmz:
Did you remove the HTC one? That's why. Also that error means a method is being called from buildflag that can't be found. It isn't a nonbooting issue unless it is repeating
[HTC Wildfire S] benjamingwynn:
No we didn't :) It's probably some lib from CM pointing to somewhere else, also could be to do with HTC removing bootanimation bin from their xbin folder - in that case we will add the bootanimation from CM9 for it to work, as a small test I duplicated the file (twice) and called them bootanimation.zip and hTC_bootanimation.zip
[HTC Wildfire S] Fikus011:
I got nothing realy smart to say,i just came by to click one thanks per each of you guys...Thumbs up for trying,hope it works ;)
[HTC Wildfire S] Eskuero:
OH MY GOD!:eek:

http://dl.dropbox.com/u/33393320/P1010859.JPG
[HTC Wildfire S] *se-nsei.:
what he said !!!!!!!!!!
[HTC Wildfire S] rioachim:
More, more, show me more... I cannot look away
[HTC Wildfire S] benjamingwynn:
I broke that

...

I then fixed it

...

Then, after moar ramdisk editing i may have even got it booting waiting for oliver to test :)
[HTC Wildfire S] Eskuero:
benjamingwynn loves to broke every that I fix.... LOL:D:D
[HTC Wildfire S] 181charan:
Feels soo good seeing you all working together on something!!! :')

Without all the petty fights n stuff...

Hope you guys figure this out!!!

:)
[HTC Wildfire S] jmz:
You have incompatible libs/bins. Incompatible with each other. I would take a better look at what all you replaced
[HTC Wildfire S] dudeman1996:
Just a question, how come you're not in irc and git with us when you keep giving us pointers on how to fix things? :)
[HTC Wildfire S] benjamingwynn:
I quoted this so people can see in case they missed it, since it was the last post on the page before :)
[HTC Wildfire S] jmz:
Because I don't like messing with stuff I don't own unless I know for 100% what the issue is.
[HTC Wildfire S] dudeman1996:
None of us really "own" it, and I'm pretty sure we don't always know EXACTLY what the issue is, but we try things out and if it doesn't work we try to find another solution :D
[HTC Wildfire S] jmz:
As in I don't have a wfs that's useable.
[HTC Wildfire S] eoghan2t7:
tomorrow i will download the rom and have a look at it, its most likely a lib file that needs changed etc for it to boot or there is lib files inside apks that run during boot preventing a complete boot.
[HTC Wildfire S] benjamingwynn:
I think that this next build should work fine. There were some bad lines in build.prop that the HTC audio lib may not have liked.

We have a problem with the sense 4 libs as they don't support armv6. What I have done to bypass this and boot the system to shell is use the libs from Sense 3.5 over the current Sense 4 ones, then normal ics ones over that. This gives us armv6 sense libs and armv6 ics libs.

There may, however be a problem with this as some libs from sense 3.5 don't play nice with ics, and could error out.

As said before about audio, I think It could be the HTC acoustic library failing due to us using sense 3.5s. I don't have a solution yet on what to do with this, as we don't have an ics friendly library for this compiled for armv6.
[HTC Wildfire S] Fikus011:
I was wondering why are the HTC giving only sense 3.6 to desire s,sensation,etc with ICS update...clearly desire s is much better device then ONE C or ONE V...beats me.

I hope u going to succeed in your plans m8...i realy do...i dont care much for ICS per se...but i like sense 4 overlay..UI looks much nicer...

@Eoghan...it was about time for you to join m8 :D...these guys are making nice cooperative project here...glad to see that :)
[HTC Wildfire S] dudeman1996:
Ben's in the same situation really. He makes some changes and wait for me and/or Oliver to test it
[Samsung Infuse 4G] CZ Eddie:
There are a few dozen of us Skyrocket (GS II LTE) guys using the Infuse car dock (OEM Samsung version) because there are no docks made for the Skyrocket.

And it works great.... except for one problem.

Once you plug the phone into the docks USB port, it does not deliver audio out of the 3.5mm jack on the dock.

Am hoping there is a dev who will know how this function works on the Infuse, so we can possibly port that capability over to the Skyrocket?

Here is the Infuse car dock thread in the Skyrocket forum.

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

Thanks for any tips or suggestions!!!
[Samsung Infuse 4G] mg2195:
Try pming entropy...he's our kernel dev/CM9 and fixed the dock problem with CM9....so I believe he should know how it works
[Samsung Infuse 4G] wayzata:
Yes, he knows how to make it work for the Infuse.
[Samsung Infuse 4G] martinnr:
I check the other link and nobody knows so far how to make it work, when you said "he knows" you mean he did actually tell you "how to" make it work?

Thks
[Samsung Infuse 4G] mg2195:
He was saying that yes entropy know how to make it work...he got it working on the infuse...so if anyone can provide help it would be entropy or another kernel dev...
[Samsung Infuse 4G] Entropy512:
Can't help you with ****rocket... COMPLETELY different hardware architecture including, I believe, a completely different USB port switching IC.

This is about all the help I can give you:

If the kernel properly supports docks, /sys/class/switch/dock/state will be 2 when a cardock is attached

Samsung Car Home sends the proper intents to Samsung's framework to change the dock audio routing. If you've tried Samsung Car Home and its dock audio routing isn't working - you're SOL on Touchwizz firmwares.
[AT&T, Rogers HTC One X, Telstra One XL] patstock11:
I constantly hear people talk about LTE and they're data useage. And basically I see that people generally gloat/brag/complain about the amount of data they can burn thru using LTE. Am I missing something ? Why would u use more, I get that it's faster but isn't the same amount of data being transferred ? Or does the quicker speeds make u habitually use more data. I've been wondering bc I see the general idea on the forum lately. I wouldn't know bc awesome AT&T hasn't brought LTE to the desolate rural long island (sarcasm).
[AT&T, Rogers HTC One X, Telstra One XL] ChongoDroid:
It doesn't take more data, but streaming hd video and big downloads drain it pretty quick. For instance my home WiFi will get around 10-20mbits down and 1-2 up.

On LTE I'll get 20- 45 down and 12-30 up.. so when I upload all my pics to dropbox or download a podcast I'll often switch to LTE.
[HTC Rezound] troy7548:
When I am running the s-off procedure I get done with the wire trick, it looks for device, but after it findes the device it is says

"Please wait

Cannot find Bear..... Is bar closed.. push enter to exit"

I have all the files in the adb folder (C:/Android), Ran control bear as Admin

and I have checked all the MD5's Any Ideas
[HTC Rezound] tekhna:
Did the s-off succeed? Is your phone rebooted into recovery?
[HTC Rezound] troy7548:
No the screen was completly black. So I flashed the PH98img and reinstalled amon ra because I tried for 30min to get it to work maybe I will try again tomorrow. But I haven't seen anybody mention that error before but I haven't been through 600 posts and the Search is down.
[HTC Rezound] thatsricci:
but what does your hboot screen say? still s-on?
[HTC Rezound] troy7548:
still says Vigor PVT ship S-ON RL

HBOOT 2.21.0000
[HTC Rezound] taptaptouch:
Did you battery pull and disconnect reconect all cables? I had to do that multiple times. Dont remember all the errors tho
[HTC Rezound] troy7548:
I pulled the battery and cable about 5 times trying to get this to work and I got pass the wire trick a couple times then I get to the error where it can't find Bear and the bar is closed. I will try again tomorrow if I get time and see if it happens again. I am running CleanRom 4.3 Should I go to a stock rom or should it work from CleanRom?

thanks for all the help.
[HTC Rezound] destro158:
I only was able to get S-Off to work from a rooted stock rom (Scott has one on his site). CleanROM 4.2.2 and 4.3 wouldn't work for me. However, my error was different than yours. ControlBear complained about not being able to find the device and told me to reinstall drivers. Overall, if you're flashing a ROM anyways, it probably can't hurt to go with a stock ROM.
[Desire General] WeeDab1x:
So i messed up pretty bad! Heres what happened. I partitioned my phone using clockwork and then installed s2e to move the apps but i didnt tick the right boxes as the images in this guide said in addictivetips guide /mobile/transfer-apps-app-data-to-sd-ext-and-back-in-cyanogenmod-7-android/ (hate that it wont let me link grrr)

i ticked all of them in the left image! and nothing from the right image... rebooted and now almost almost every app is missing like clockwork and etc. Even my home button doesnt work! Its like i have a half rooted phone or something its really bad. Is this fixable? Please help! Im new this rooting thing. I rooted my phone and installed CM7 just a week ago... Cant believe i messed it up! Im getting a computer science degree in a month! IM SUCH A FAIL LOL
[Desire General] EazyLuke:
If you can still access s2e you can try to tick the boxes. If not, power off your phone, then turn it on with the volume down button pressed. In bootloader use the volume buttons for navigation and select recovery. Then wipe data. Remember that you'll have to reinstall all your apps

Gesendet von meinem HTC Desire mit Tapatalk 2
[Desire General] WeeDab1x:
S2e wasnt working but its all good i formate in recovery and everythings back to normal. I had a freakout that i had permanently ruined the installation and everything lol. Thanks man everythings working great now!