[DEV][ROM-AOSP]Htc wildfire icsV0.3 alpha (booting)(port from eris) discontinue

Search This thread

kaassaus

Senior Member
Mar 28, 2011
611
83
Last edited:

Justice™

Senior Member
Jul 3, 2011
932
220
26
Congrats kaassaus! Nice to see you creating the first ICS rom for the wildfire. I'll follow this thread actively from now on!
 

KeiranFTW

Inactive Recognized Developer
Nov 17, 2011
2,637
2,692
28
Sunderland

Formiak

Senior Member
Jan 9, 2011
543
44
Poznań
The most important first is working touchscreen , later everything should be easier to repair (libs from CM7 may work ) .
There are no problems with res ?
Maybe when i'll have a moment gonna flash for a second and have a look by myself :)
 

Justice™

Senior Member
Jul 3, 2011
932
220
26
The most important first is working touchscreen , later everything should be easier to repair (libs from CM7 may work ) .
There are no problems with res ?
Maybe when i'll have a moment gonna flash for a second and have a look by myself :)

Being based on the eris port, and seeing how everything looks on that. Probably not. I guess there might be some resizing here an there. But I doubt it!
 

KeiranFTW

Inactive Recognized Developer
Nov 17, 2011
2,637
2,692
28
Sunderland
eris is 320x480, wildfire 240x320, then i think the rom need resizing

Not necessarily, AOSP supports multiple (if not all) resolutions, the elements of ICS will be sized according to the DPI set in the build.prop.
HTC's Sense UI on the other hand, is only created for one device at a time in mind.

Keiran
 
  • Like
Reactions: djinn0

Formiak

Senior Member
Jan 9, 2011
543
44
Poznań
Yea that sure but I don't know how the building procces is , if there is building only LDPI or MDPI or HDPI or all in one . If so (the last) that would be great . Flashing right now that :)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 15
    Bugs so fare i know:
    Sound dont work.
    Wifi bt and gps dont work.

    chanelog: V0.3 :credits to KeiranFTW for fixing touchscreen.
    now you can call (you have singnal now).

    Downloads:

    V0.3:http://www.multiupload.com/DSOSM3PSKG

    V0.2: tnx to my partner:keiranftw. http://dl.dropbox.com/u/13729847/WildICE.zip

    link: V0.1 : http://www.multiupload.com/RCPXQFDLW8

    Credits to:
    KeiranFTW for fixing the touchscreen and maked a kernel.
    4
    Working on a kernel with working modified touchscreen drivers, wish me luck!

    Keiran
    3
    The "edit" dividers only come in after a certain time period I think...good news it's booting and autoupdating!

    No jokes here either....
    The SOFTKEYS and TOUCHSCREEN is working!
    I can't believe it! A few atmel.c tweaks and its working!
    However, arco was right about the system being laggy, the phone app keeps fc'ing and nothing is smooth.

    Next step, getting data and stuff working.

    Going to make a new thread for this, since kassaaus won't update the first post and I would have more control being an OP.
    2
    Going to try something:
    It appears the new ICS needs an idc (touchscreen configuration maybe?) and so I am going to try this:
    http://xdaforums.com/showthread.php?t=1332605&page=5
    Also, I have added back in some lines (softkeys might now work?): https://github.com/keiranFTW/buzz-kernel-ics/commit/1e5416be2b99c2fee3c5b0eeb3248677ab176eb3
    Hoping all goes well, if touchscreen worked well we could have UI softkeys instead (like on honeycomb) - will add kernel update later today

    Keiran
    2
    This thread should seriously be closed. It's utterly useless running two parallel threads of the ABSOLUTE same thing, and more so, because Kerian has decided to go for his own thread (rightfully). All it leads to is clutter and chaos. I don't know what fun you get by running parallel threads. There is no difference in "Lotusmod S" and Lotusmod apart from cosmetic changes, "Nextsense Revolution" is a 1:1 mirror image of "No Limits" with absolutely no changes, and, this thread is now turning into a mirror image of Kerians ROM.

    Stuff like Build.prop changes and other tweaks / patches can be posted in a post on a thread. I am pretty sure they do not need a dedicated thread of their own.

    But, at the very least, you bothered to credit the OP of the touchscreen fix, so I thank you for that.