yashsingh1/xdaforums huggingface dataset:
[HTC Wildfire S] samuel2706:
Oh and the size is 190 when zipped or unzipped? all of the system partition needs to be under 290mb i think.
[HTC Wildfire S] thehacka1:
Is it possible to port sense 4 over sense 3.5 using your guide?

190MB when unzipped. 133MB when zipped. Beat that :p
[HTC Wildfire S] 4ndaKava:
Maybe we should start from scratch..

Because the pico is more like our device, maybe we could try to port sense 4 from them:

Sense 4.1: http://xdaforums.com/showthread.php?t=2312175

Sense 4.0a: http://xdaforums.com/showthread.php?t=1943775

And if this works we could even port miui v5 from them:

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

Don't like the idea to start from scratch that much, but maybe it is necessary.. :)

Edit:

And I think we should work with a ext Partition just for making it boot. Later we can Slim the Rom down.

Else it would be so much unnecessary work again, which maybe doesn't even helped.

(The guys from the pico used partions, too)
[HTC Wildfire S] thehacka1:
Guys I know this isn't the right thread but can I have some help with the following logcat. http://pastebin.com/1REs5tBc
[HTC Wildfire S] thehacka1:
Guys what if we radio-log the sense 4 rom? That could tell us something.

PS: A radio-log is:

adb logcat -b radio
[HTC Wildfire S] benjamingwynn:
Might wanna read through Henry's stuff: https://github.com/benjamingwynn/marvel-miui4/commits/master
[HTC Wildfire S] 4ndaKava:
Are there any new plans on this [MENTION=4960614]thehacka1[/MENTION]?
[HTC Wildfire S] SpaceCaker:
what i see from here there are some errors

E/overlay ( 127): ERROR: MSMFB_MIXER_INFO ioctl failed

E/HTC Acoustic( 130): Fail to open /system/etc/AudioPara_unknown.csv -1.

E/HTC Acoustic( 130): set mbadrc filter error.

E/Trace ( 222): error opening trace file: No such file or directory (2)

E/SQLiteLog( 314): (1) no such table: secure

W/ResourceType( 314): Failure getting entry for 0x7f090002 (t=8 e=2) in package 0 (error -75)

W/ResourceType( 314): Failure getting entry for 0x7f090002 (t=8 e=2) in package 0 (error -75)

W/ResourceType( 314): Failure getting entry for 0x7f070003 (t=6 e=3) in package 0 (error -75)

W/ResourceType( 314): Failure getting entry for 0x7f070003 (t=6 e=3) in package 0 (error -75)

E/filemap ( 314): mmap(0,4096) failed: No such device

and i see some more errors

butt these are the ones i saw that must be looked upon atleast i think ?
[HTC Wildfire S] izi501:
Just connected with a bit of 3G on holidays... I just wanted to say, about the Network thing error, as we can see no L, maybe the smali file is in the wrong framework file. Sorry if somebody already said that, but I didn't read all the new messages in the thread ;)

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] 4ndaKava:
Yeah, it is somehow linked to the wrong place or is in the wrong directory. Or maybe it is wrong declared.

There are many options.
[HTC Wildfire S] thehacka1:
Yes but if these were the errors then the Fatal signal would have come straight after them. Instead The bootloop starts after starting up the connectivity service.
[HTC Wildfire S] thehacka1:
I put those files in the same directory of every single jar file. It didn't work.
[HTC Wildfire S] 4ndaKava:
Could it be that we have to use AOSP as base? Cause sense and miui are based on AOSP..

But we don't have AOSP..
[HTC Wildfire S] Kevinjoa:
Every Rom is based on aosp :p

Gesendet von meinem Nexus 7 mit Tapatalk 4 Beta
[HTC Wildfire S] 4ndaKava:
Ah right.. CM too :D
[HTC Wildfire S] benjamingwynn:
Including Firefox OS. Just saying.
[HTC Wildfire S] thehacka1:
It is? WOW. What version of AOSP is it based on? GB,ICS or JB ?
[HTC Wildfire S] benjamingwynn:
ICS

Edit: its past 3AM, excuse the off topic ness.
[HTC Wildfire S] thehacka1:
It's past 10PM here in America. We are practically drunk. Are you saying Firefox OS can be ported over ICS?
[HTC Wildfire S] thehacka1:
Since I was bored I unpacked FireFox OS Nexus S system.img and it looks awesome. Going to look around inside it.
[HTC Wildfire S] thehacka1:
Everything seems to makes sense except a folder called b2g. :p I'm guessing that is FireFox's files. Gonna do some more exploring and will report back.
[HTC Wildfire S] thehacka1:
Guys how do you repack a system image?
[HTC Wildfire S] cyb3r.pr3dat0r:
Including Ubuntu Touch but it's more suitable for multi-core devices :(
[HTC Wildfire S] izi501:
So as none of us could fix the error, we just have to wait for JDevs to come back, and then we have to hope that he knows the solution :)

Maybe we could do as the guy in the other thread proposed : replace all the main libs that usually go together, I don't exactly remember the names...

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] thehacka1:
I'm still waiting for Jdevs. For now I'm looking to other things such as:

FireFox OS

MIUI V5
[HTC Wildfire S] csoulr666:
If you want to work with Firefox OS.....you'll have to wait for Firefox to add patches for ARMv6
[HTC Wildfire S] Guitarfreak12:
And facebook home or something? Or doesnt facebook has an os?

Good luck with firefox os, miui v5 aaaand sense 4 :p

Sent from my WFS
[HTC Wildfire S] thehacka1:
No need TBH. I've ported many roms from the NS before. Why not now?
[HTC Wildfire S] Olivier:
Facebook Home is a launcher, lol.
[HTC Wildfire S] csoulr666:
That's the thing.......it is an OS

based on android

,just like ubuntu touch(currently)......Plus it is based on AOSP ICS,which isn't available for our device
[HTC Wildfire S] thehacka1:
I've ported AOSP ICS over CM9 before for this device. http://xdaforums.com/showthread.php?t=2244230
[HTC Wildfire S] Guitarfreak12:
XD

Sent from my WFS
[HTC Wildfire S] benjamingwynn:
They already exist by some third party if I remember.
[HTC Wildfire S] izi501:
What do you think about a Sense 3.6 port ? It has all the Sense features, but moreover it is based on ICS, which is quite good.
[HTC Wildfire S] thehacka1:
But it is HDPI. Also it's bigger than Sense 4a. Much bigger.
[HTC Wildfire S] Guitarfreak12:
From the desire s etc?

Sent from my WFS
[HTC Wildfire S] izi501:
You can mount /sd-ext to /system/app... Or even mod the kernel directly.

For the size of the images, one thing is possible : to automagically resize all of them. That should be easy, something with find.
[HTC Wildfire S] Mazer.one:
Yes there is an app (on xda) wich resize automagically all the images and support .9.png files.

I never tried but if you need it I'll search the link...
[HTC Wildfire S] izi501:
Why not, it would be wonderful ;)

And then, by mounting /sd-ext to /system (or just linking), we could try to port Sense 5 :P :mad:
[HTC Wildfire S] thehacka1:
Well we could try. Right now I'm helping to port sense 5 to the HTC Sensation.
[HTC Wildfire S] Mazer.one:
Sense 3.6 , Sense 4 or Sense 5 for our Wfs will be wonderful :)

I'm just waiting for a new Sense ROM for playing with it :D

Keep up the good and hard work :thumbup:
[HTC Wildfire S] izi501:
The tool is Android Resizer Tool.

I'll try something with symlinks to see if it could work... symlinking /system/app to /sd-ext/system/app should be enough. Or I think that modifying the ramdisk could work too.
[HTC Wildfire S] FAtfcK:
sense 4 odexed is like 300-380mb :o that would need a hell lotta resizing. imma try port it too :D
[HTC Wildfire S] Mazer.one:
This tool looks good too

http://xdaforums.com/showthread.php?t=2219584
[HTC Wildfire S] cyb3r.pr3dat0r:
sense 5 is very big and i think it will be near impossible to port to wfs but sense 4 is possible btw i love your sense themes please

theme also for cm 10.1 :laugh:
[HTC Wildfire S] izi501:
The link I gave you

is a fork of this app ;)

Sense 5 is big but if you mount /sd-ext to /system everything should be ok, except that the rom will be a bit laggy.

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] Kevinjoa:
Why porting sense 4 ? Sorry I can't understand. It'll be lot more work then sense 4, sense 3.6 oder touchwiz from the ace. When some ports will boot there will be lot of work getting ril, wifi, bluetooth sound etc working.
[HTC Wildfire S] izi501:
You meant Sense 5 I guess :)

I don't think it would be more work than Sense 4... In both cases it has to be ported from armv7, and in both cases we have stable base rom. But we also have stable AOSP 4.2.2, and Sense 5 is based on AOSP (and not on CyanogenMod).

But to my mind the rom that would be the most interesting to port is Sense 3.6, because it is certainly a lot easier than Sense 4/5.
[HTC Wildfire S] thehacka1:
Yep.
[HTC Wildfire S] csoulr666:
So basically what you did is backport apps to GB or themed it???
[HTC Wildfire S] thehacka1:
Stopped upload. Adding test apps.
[HTC Wildfire S] thehacka1:
Backported and much more. Also the launcher is not themed it is fused with the original sense 4 Rosie.
[HTC Wildfire S] csoulr666:
Would like that....... I know we can't port the original sense 4 without some EXTREMELY SERIOUS development...... So back porting is the way to go
[HTC Wildfire S] thehacka1:
I tried making a new sense supported kernel and it nearly hard bricked my phone.
[HTC Wildfire S] Mazer.one:
I can't believe, it , Big Thanks for your work :thumbup:

Could it be possible to try this amazing ROM ?
[HTC Wildfire S] Kevinjoa:
I am too and keep up your great work.
[HTC Wildfire S] thehacka1:
Will release rom along with thread. Will send link of alpha build to Kevimjoa's PM.
[HTC Wildfire S] Kevinjoa:
Tested it and sense 4 lovkscreen works but launcher is only the modded launcherpro with their widget and I can't find sense analog clock .
[HTC Wildfire S] thehacka1:
The launcher has added Rosie features from the official sense 4 launcher.
[HTC Wildfire S] Kevinjoa:
I already have implented it in my cm7 sense buil and marvelloussense not released yet. :) is sense 4 lockscreen working on cm ?
[HTC Wildfire S] thehacka1:
No but I am working on it.
[HTC Wildfire S] Cup_Cake:
Hope you can get it to work:)

---------- Post added at 06:54 PM ---------- Previous post was at 06:21 PM ----------

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

You can check this thread, this dev has shown a preview of sense lockscreen on ics:)
[HTC Wildfire S] Larvitarrr:
I know that you have lot of worries now due to a broken computer, but what is that clock widget?
[HTC Wildfire S] cyb3r.pr3dat0r:
:D thanks for not letting our great device die
[HTC Wildfire S] JDevs:
How are you here things? Need some help?
[HTC Wildfire S] Kevinjoa:
I think wie cannot port sense 4 but you can try Tod help .
[HTC Wildfire S] JDevs:
hehe. me somehow managed to run it. but the device may circle-restart. I'm deleted accidentally the sources files...
[HTC Wildfire S] izi501:
You mean it bootloops ? Or you can access the pin screen?

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :D
[HTC Wildfire S] Mazer.one:
Thanks mate, I think during my holiday (in 2 weeks :) ) i'll try to make a theme for cm10.1 ;)
[HTC Wildfire S] thehacka1:
[MENTION=4960219]xizt1boy[/MENTION] or [MENTION=4749032]izi501[/MENTION] could you mod the init.rc's BOOTCLASSPATH for the boot.img's in the attachments, Replace the BOOTCLASSPATH in boot_cm9 with the one in boot_stock. Thanks in advance. I need it urgently.

https://docs.google.com/file/d/0By-IixC-6PWXb0NNVlViZWRpS0E/edit?usp=sharing - boot_cm9

https://docs.google.com/file/d/0By-IixC-6PWXUXNaRDBjQzB1Vmc/edit?usp=sharing - boot_stock
[HTC Wildfire S] izi501:
Here you are.
[HTC Wildfire S] Guitarfreak12:
Still the same error? If so, i really hope you can fix this

Sent from HTC "Marvellous" WFS
[HTC Wildfire S] izi501:
We're waiting for JDevs...

But there are many good roms in progress. I'm trying to port Sense 5 but I'll certainly need [MENTION=4960614]thehacka1[/MENTION] patching talent to fix most of the errors :)

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] 4ndaKava:
What are the errors? Maybe I can help too :)
[HTC Wildfire S] izi501:
It is still the same... with NetworkManagementSocketTagger... I had an idea, but the guy who could help me to realize it never replied.

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] Guitarfreak12:
Oh okey, and im using wonderful marvellous sense3.5 now. But i may sound very very very negative now, but dont you think it was a lie? Because he 'made' it, and accidentally deleted it... By his dev skills, i believe him, but on the other side not...

Sent from HTC "Marvellous" WFS
[HTC Wildfire S] izi501:
Maybe yes, maybe not, but it didn't matter :P What is important is that we think he did it.

In fact [MENTION=4494075]Andy_nu[/MENTION] gave me the name of the libs linked together, so certainly we should definitely try to take them from sense 4. Maybe I'll try it tomorrow ;)

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] Andy_nu:
dont know how i found ya here, but before you try the libs:

unpack boot.img and add sense init.rc

repack

and add all the device specific files from vendor and the device mk
[HTC Wildfire S] thehacka1:
We already did the init.rc thing. What do you mean vendor and and device mk?
[HTC Wildfire S] Andy_nu:
/system/vendor from base to sense port
[HTC Wildfire S] thehacka1:
We used marvel system/vendor so we did that too.
[HTC Wildfire S] Andy_nu:
does your base boot on this phone? if not you need a working/ booting base to continue

when you swap the libs post another logcat and maybe we can get a better look at whats going wrong
[HTC Wildfire S] thehacka1:
Our base booted. Usually when we swap libs it gets stuck on HTC screen.
[HTC Wildfire S] izi501:
Yes, but that's because we do not change all the libs that are linked together... So we should definitely try ;)

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] 4ndaKava:
Looks like improvement :)
[HTC Wildfire S] Andy_nu:
thats because you might have merge the sense init to the base init(win merge is a great tool for this), i seen that the kernel is bootlooping, give me a dmsg and a logcat, i will no longer reply on the other thread.

thanks
[HTC Wildfire S] izi501:
dmsg gives either device not found or nothing. It once gave protocol fault (no status) but I don't know if it the error detected by dmsg or an error because the phone rebooted at this moment.

logcat give nothing too.
[HTC Wildfire S] Guitarfreak12:
Just an idea. What if you can port AOSP 4.0.x dunno which, and then place the sense files in it?

Sent from my HTC "Marvellous" WFS
[HTC Wildfire S] izi501:
We're doing that with CyanogenMod. That's true, it would be better with AOSP... But we don't have AOSP, so we should compile it.
[HTC Wildfire S] Guitarfreak12:
Okey, but if i may ask. What is the difference between cm and aosp?

Sent from my HTC "Marvellous" WFS
[HTC Wildfire S] izi501:
Cm is based of AOSP but has a lot more features everywhere. You can see it if you want : try JDevs' CM10.1 and thehacka1's AOSP, you'll see immediately the difference :P
[HTC Wildfire S] Guitarfreak12:
But it doesn't makes sense for sense 4 then?

Sent from my HTC "Marvellous" WFS
[HTC Wildfire S] izi501:
Sense 4 is based on AOSP, but we do not have AOSP 4.0.x. That's true, it would be better to port it from AOSP... CyanogenMod isn't the best rom to use as a base but it is the only one we have :)
[HTC Wildfire S] benjamingwynn:
Compiling a stable AOSP for the Wildfire S is quite difficult. I remember dudeman1996 stopped supporting Paranoid Android for this phone because it was too difficult to port AOSP without using so many patches it made it not AOSP anymore.
[HTC Wildfire S] Olivier:
However, some guys managed to compile it for the Samsung Galaxy Ace. :p
[HTC Wildfire S] SpaceCaker:
Aosp GB

Aosp ICS

Aosp JB 4.1.2

Aosp JB 4.2.2 Galaxy ace has them xD

and AOSPA 3.69

pac

cm10.1 etc
[HTC Wildfire S] Guitarfreak12:
Does the ace has aosp ics? Hacka a new project for you :p

Sent from my HTC "Marvellous" WFS

---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------

Okey! Good luck then

Sent from my HTC "Marvellous" WFS

---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------

But can you explain the comiling problems? Is it the space or something?

Sent from my HTC "Marvellous" WFS

---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------

Well ask them how they did it xD

Sent from my HTC "Marvellous" WFS
[HTC Wildfire S] izi501:
We have stable AOSP 4.2.2 by JDevs, but it is useless for Sense 4.

Envoyé depuis mon HTC FeuSauvage S avec Touchwiz 5 et Tapatalk 4 :)
[HTC Wildfire S] thehacka1:
That's a nice way of comparing roms. :p

We have AOSPA which is pretty much AOSP and we are getting source-built AOSP 4.2.2.

That's the rom I ported.

And also [MENTION=4661068]Guitarfreak12[/MENTION] I already ported that: http://xdaforums.com/showthread.php?t=2244230 It was a long time ago though.
[HTC Wildfire S] benjamingwynn:
You cannot port pure AOSP. You need to patch it. You may as well just use CM9 as you'll get the same outcome.

Google dropped support for ARMv6 after 2.3. If I remember correctly a lot of stuff in external has to be patched including bionic and webrc. And they're mostly hacks.
[HTC Wildfire S] thehacka1:
Also display_legacy and media_legacy is required.
[HTC Wildfire S] cyb3r.pr3dat0r:
say that to jdevs ;)
[HTC Wildfire S] Guitarfreak12:
Can't you use that port then?

Sent from my HTC "Marvellous" WFS

---------- Post added at 06:31 AM ---------- Previous post was at 06:30 AM ----------

But it is for sense 5 if you all can make it small enough right?

Sent from my HTC "Marvellous" WFS
[HTC Wildfire S] Andy_nu:
will not work since sense is so dependent on its own framework.

---------- Post added at 12:17 AM ---------- Previous post was at 12:15 AM ----------

im suprised the egl drivers will even boot with sense. lol
[HTC Wildfire S] cyb3r.pr3dat0r:
we are far far away from sense , first it needs to resized htc one is xxhdpi and ours is mdpi then we may remove some bloatware

and lastly we're gonna use /sd-ext for handling large size rom
[HTC Wildfire S] izi501:
We're working on it... you should see some progress soon.

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] cyb3r.pr3dat0r:
if you are able to conquer that sense 5 mountain then i will hug you :victory:

---------- Post added at 12:25 PM ---------- Previous post was at 12:20 PM ----------
[HTC Wildfire S] Guitarfreak12:
Maybe he lives on the other side of the world :o

Ontopic any update about sense 4?

Sent from my HTC "Marvellous" WFS
[HTC Wildfire S] izi501:
Nope, we tried everything we could think about :-\ Now we're waiting for help from other devs. [MENTION=4494075]Andy_nu[/MENTION] seemed to have some ideas... and maybe [MENTION=5262848]JDevs[/MENTION] could help us too.

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 et Tapatalk 4 ;)
[HTC Wildfire S] Guitarfreak12:
Okey but he didn't respond on his pm's?

Sent from my HTC "Marvellous" WFS
[HTC Wildfire S] izi501:
He is in travel, for his job if I remember well. He comes back about the 10 or 11 of august.
[HTC Wildfire S] Guitarfreak12:
Okey, his job is always more important than sense 4 :sly:

Sent from my HTC "Marvellous" WFS
[HTC Wildfire S] Guitarfreak12:
Maybe you all can start on sense 5 till jdevs is back...

Sent from my HTC "Marvellous" WFS
[HTC Wildfire S] thehacka1:
Someone's a bit behind. :p Me and izi started on that quite a while ago.
[HTC Wildfire S] izi501:
Now it flashes but doesn't reach the bootanimation. I know why, it is because of my kernel that I didn't mod correctly. So tomorrow it will normally reach the bootanimation and we will be able to get a log :) And then to start the real port.

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 et Tapatalk 4 ;)
[HTC Wildfire S] 4ndaKava:
Post your results here too :) I help where I can :)
[HTC Wildfire S] thehacka1:
We are actually thinking of making a new dev thread. This will still be kept for sense 4 as we wait for the arrival of JDevs.
[HTC Wildfire S] Guitarfreak12:
Lol

Sent from my HTC "Marvellous" WFS
[HTC Wildfire S] DrRammel:
So this thing is dead.

Sent from HTC Sensation with various Android versions.
[HTC Wildfire S] izi501:
I guess so... The error we get is unsolvable I think. It would need deeper editing, or some things like that. Maybe if we're lucky somebody will once find a fix, but I think it requires editing binaries, which is quite a painful task !

Anyway, even if it boots, there will be a huge amount of bugs.
[HTC Wildfire S] thehacka1:
It looks like you brought it back to life.
[HTC Wildfire S] DrRammel:
Thanks to me haha

Sent from HTC Sensation with various Android versions.
[HTC Wildfire S] cyb3r.pr3dat0r:
Hows sense 5 working for sensation ?

Sup buddy , any new projects ? Chaos?
[HTC Wildfire S] DrRammel:
Sense 5 is working great, I am thinking of not changing the rom anymore.. Maybe I'll make a video soon, if I have time.

Sent from HTC Sensation with various Android versions.
[HTC Wildfire S] Taikun hearth:
maybe hack is busy in this days
[HTC Wildfire S] thehacka1:
Yes I am so I can't work with this device any more.
[HTC Wildfire S] benjamingwynn:
https://www.youtube.com/watch?v=9E-WasNzVpI&feature=youtube_gdata_player
[HTC Wildfire S] polfrank:
lol
[HTC Wildfire S] JDevs:
true.
[HTC Wildfire S] thehacka1:
Upload that rom now. :p
[HTC Wildfire S] izi501:
Errr true that it boots? o_O I agree with thehacka1 upload it right now! :)

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :D
[HTC Wildfire S] NikSalsa:
Hmm, its strange and very cool! upload it please!! :D
[HTC Wildfire S] izi501:
JDevs told me he really managed to boot Sense 4, but there were many bugs with apps. Unfortunately he deleted the work, but it means that it's possible to port Sense 4 :) thehacka1 maybe you could ask him how he did it and try again!

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :D
[HTC Wildfire S] thehacka1:
I'm back! Just had a major breakthrough! See OP for details.
[HTC Wildfire S] xizt1boy:
Bootloop. Logcat help you?
[HTC Wildfire S] thehacka1:
I think I know how to fix this. Don't be too hopeful. It still might not work.
[HTC Wildfire S] izi501:
How did you free all this space ?

Envoyé depuis mon HTC FeuSauvage S avec CyanogenMod 10.1 (et Tapatalk 4) :D
[HTC Wildfire S] thehacka1:
Surprised? Just removed all blpatware.
[HTC Wildfire S] ardiyan_ie08:
after i installed the rom,the phone can't boot (bootloop).. :(
[HTC Wildfire S] izi501:
Which files are bloatware and whiwh are not ? I'm trying to port Sense 3.6 and my system folder is quite big : 415 Mb :P I'll remove bloatware too, but I don't know which files I can delete safely...
[HTC Wildfire S] kirmaniarslan:
Deleted :p
[HTC Wildfire S] izi501:
What is the problem ?

EDIT : method for Bluetooth missing in framework.jar ?

Envoyé depuis mon HTC FeuSauvage S avec PAC-man v23.0.0 (et Tapatalk 4) :D
[HTC Wildfire S] thehacka1:
No its not that. I've ported it in the wrong way. I'll make a new version and see how it goes.
[HTC Wildfire S] izi501:
There is this error though.
[HTC Wildfire S] izi501:
In this guide, the guy explains how to fix such errors :) But it takes a lot of time...
[HTC Wildfire S] josans:
well

im interested in! or sense 5
[HTC Wildfire S] thehacka1:
Sense 5 = Instantaneous death. The HTC One stock ROM is about 1 GB.
[HTC Wildfire S] izi501:
This summer, if I have time, I'll make a script to fix these space problems : it will change the zip file to install some files in sd-ext partition. It will come with a modded Int2ExtV2+ to work with a third SD partition :)

Anyway, did you try the guide I gave you ?

Envoyé depuis mon HTC FeuSauvage S avec PAC-man v23.0.0 (et Tapatalk 4) :D
[HTC Wildfire S] thehacka1:
I tried but I got the same bootloop. WAAAAAAAAAAHHHHHHHHHHHHHHH!!! I found a different porting method by [MENTION=2623456]GalaxyUser[/MENTION]. I'm going to try his. Also good luck with that script of yours.
[HTC Wildfire S] izi501:
Thanks !

If you did everything correctly, the very error I gave you should have disappeared. But there will be other errors like that ! So good luck then ;)

Envoyé depuis mon HTC FeuSauvage S avec PAC-man v23.0.0 (et Tapatalk 4) :D
[HTC Wildfire S] thehacka1:
Almost finished build attempt 4. A question to you guys. Does it matter if I remove drawable-hdpi and drawable-xhdpi folders for more space? I mean it won't affect anything since the Desire C is MDPI right?