yashsingh1/xdaforums huggingface dataset:
[Wildfire Android Development] core1024:
there is hope in the tunnel

Hi, guys I just tested the new patch.

Results are better. When th phone first boots i actualy can use the touchscreen.

When I tried to unlock the lockscreen, the phone refuses to recognise touches anymore.

Here is the logcat from unlocking the screen

D/MediaProvider( 404): object removed 162
D/MediaProvider( 404): object removed 163
D/MediaProvider( 404): object removed 161
D/MediaProvider( 404): object removed 164
I/dalvikvm( 141): Jit: resizing JitTable from 1024 to 2048
I/power ( 141): *** set_screen_state 0
D/SurfaceFlinger( 141): About to give-up screen, flinger = 0x1cfe88
W/WindowManager( 141): Failure taking screenshot for (90x120) to layer 21000
W/NetworkManagementSocketTagger( 141): setKernelCountSet(10019, 0) failed with
errno -2
D/AK8973 ( 111): Compass CLOSE
D/dalvikvm( 141): GC_EXPLICIT freed 354K, 11% free 7919K/8839K, paused 18ms+16m
s
V/TransportControlView( 141): Create TCV com.android.internal.widget.TransportC
ontrolView@4112a5b0
D/android.widget.GridLayout( 141): vertical constraints: y1 - y0 > 68, y2 - y1
> 15, y3 - y2 > 15, y4 - y3 > 0, y5 - y4 > 0, y6 - y5 > 227, y7 - y6 > 0, y7 - y
0 < 301 are inconsistent; permanently removing: y7 - y0 < 301.
I/power ( 141): *** set_screen_state 1
D/AK8973 ( 111): Compass Start
I/ActivityManager( 141): Displayed com.android.launcher/com.android.launcher2.L
auncher: +1m25s828ms
I/WindowManager( 141): Lock screen displayed!
W/NetworkManagementSocketTagger( 141): setKernelCountSet(10019, 1) failed with
errno -2
D/SurfaceFlinger( 141): Screen about to return, flinger = 0x1cfe88
I/power ( 141): *** set_screen_state 0
D/SurfaceFlinger( 141): About to give-up screen, flinger = 0x1cfe88
W/WindowManager( 141): Failure taking screenshot for (90x120) to layer 21000
W/NetworkManagementSocketTagger( 141): setKernelCountSet(10019, 0) failed with
errno -2
V/TransportControlView( 141): Create TCV com.android.internal.widget.TransportC
ontrolView@4125c8c8
D/android.widget.GridLayout( 141): vertical constraints: y1 - y0 > 68, y2 - y1
> 15, y3 - y2 > 15, y4 - y3 > 0, y5 - y4 > 0, y6 - y5 > 227, y7 - y6 > 0, y7 - y
0 < 301 are inconsistent; permanently removing: y7 - y0 < 301.
D/AK8973 ( 111): Compass CLOSE
D/dalvikvm( 141): GC_CONCURRENT freed 510K, 12% free 7849K/8839K, paused 9ms+14
ms
[Wildfire Android Development] androidino95:
Ok, I was wrong. After some playing around, I managed to get the WiFi working, flashed the superuser package and got root, installed adw launcher, overclocked and voila, rocking ICS! For the keyboard, use the japanese IME. When the sound is fixed its going to be my daily driver. Great job schiznik and keiran!

Sent from my HTC Wildfire
[Wildfire Android Development] scux:
Wifi works, manually add a network.

I use keyboard Smart Keyboard Trial

GAPPS installed and logged market, can not download applications.

All tests without sim card.

With sim card mobile network no work and Wildfire constantly freez and reboot.
[Wildfire Android Development] MattDN93:
When you flash the SU ZIP is that the official SU ZIP? And you guys jsut running without SIM?

---------- Post added at 05:28 PM ---------- Previous post was at 05:27 PM ----------

How did you get overclocking? SetCPU? Cause the kernel is OC ready I know but there's no settings available like CM...

POST-FLASH EDIT: Thanks Keiran and Schiznik it's working fine now, no reboots and WiFi is WORKING! Just I had to remove my SIM card so that I didn't get reboots and stuff...flashed SU fine, will report on apps and the like...anyone got OC yet?

GAPPS EDIT- Which GApps did you flash? Mine installed fine but I can't get past the FC of the Setup Wizard...
[Wildfire Android Development] DarkhShadow:
will this work with boot manager? got a message from them saying ics roms wont work but if this does then i will try this :)
[Wildfire Android Development] scux:
Tiny Gapps http://xdaforums.com/showthread.php?t=1352170
[Wildfire Android Development] MattDN93:
Thanks, does the Setup Manager work OK?
[Wildfire Android Development] scux:
First boot ok.
[Wildfire Android Development] MattDN93:
That worked. So Far what worked for me:

*WiFi

*GApps Install

*Superuser

*Root Explorer

*Google Account Data Sync

*SetCPU settings stick, improves speed

*All internet services

What doesn't work:

*Market download (opens but won't d/l)

*All phone options (apps OK but no SIM card because of issues)

*Gallery is weird, doesn't display properly

*Stock KB, using Japanese IME
[Wildfire Android Development] Scratch0805:
Do you mean using this as an sd rom or as the main phone rom, the 2 previous ports worked for me running from the sd card but the app itself fc'd after installing on ICS.
[Wildfire Android Development] DarkhShadow:
Yeah as a sd card rom, turns out the devs are fixing boot manager to work but if this rom needs sim taken out I will use it just not actively
[Wildfire Android Development] Scratch0805:
It should work fine on your SD card I haven't tried it yet though, if it doesn't work you can just delete the files so no harm in trying.
[Wildfire Android Development] EchoVelocity:
I tried it out and found this:

Receiving and sending texts work.

Scanning for wifi networks doesn't work (don't know about manual connections).

SuperUser app FC's.

Didn't try phone calls.

Didn't try Gapps.

Notification bar always shows no mobile signal/network signal.

3G didn't work for me.

Stock KB needs resizing.

Camera not working.
[Wildfire Android Development] scux:
When the phone freez and reboot, not have to remove the sim card, you only need a Airplane mode.
[Wildfire Android Development] MattDN93:
Doesn't work for me, the phone reboots anyways and the Airplane mode switches on/off continuously.
[Wildfire Android Development] Stefanex92:
yes but i want a ROM which i can use a signal, so i think they have to fix that, get out the sim or go to airplane mode isn't a solution
[Wildfire Android Development] Justice™:
Use cm7 or another ROM. not a in dev ROM
[Wildfire Android Development] Stefanex92:
i know bro, but i told with the other guys -.-, i said my opinion to his message
[Wildfire Android Development] rrbhootham:
Guys i have an issue: ROM after flashing does not boot.it boots into the Bootloader and does nothing.v2 file doesnt change anything.Even if i try to reboot from bootloader it again comes back to bootloader.

I am coming from CM7 nightly 256, with the 20.10.10 Radio flashed. When i flashed the rom CWM5 gave me a message :

Random Offset: 0x144

Any ideas?

EDIT : Problem solved after i flashed the 20.10.10 radio again
[Wildfire Android Development] Ankurcul:
Hats off to u man!!!!flashed ur rom without any problem....touchscreen working alright,I can receive call moreover I can do call..no freeze no reboot tested for continius 3 hours....cellular signal was great....

Gallery crashes,keyboard need resizing,camera not working,no market so no apps....
[Wildfire Android Development] ssvdude:
Looks PROMISING!

Can't wait to see this as fully fledged rom keep up the good work guyz!:D
[Wildfire Android Development] JaegerStriker:
flashed v1 then v2 and home button didn't work

sound doesnt work

wifi doesnt work

might have flashed them wrong so going to retry and will post results

edit:-

re flashed v1 and flashed the button mod from other thread

waited to boot

when booted flashed v2 and flashed tinyGapps

booted up really quick no lag

what works:-

-WiFi works - you have to add them manually

-market works

-gmail works

-screens are a little laggy but don't really notice it

-bottom buttons work but take up too much room and cuts off some of the lock screen - i personally don't use it as much as i thought i would so going to undo it

what doesn't work:-

-camera cant connect

-sound doesn't work

-problems with signal/network - going to re flash v2 again

-cant download from market

-keyboard needs resizing
[Wildfire Android Development] Arbelzapf:
Launcher freezes and reboots here. Restored my backup.

Thanks for the efforts! Can't wait to see it happening. I'll follow this thread closely. ICS is already kinda running on my Nook Color and it's amazing so far
[Wildfire Android Development] schiznik:
:/

I wouldn't expect any further updates to this from me - I've decided not to continue this (due to time constraints mostly).

If you want to attempt to fix this yourself (or anyone else for that matter), I will gladly apply your patches & do a new build.

Maybe someday I will look at it again, but I doubt that will be before there's a CM ICS build.
[Wildfire Android Development] dud3me:
Too bad :( Well anyway thanks for the great work you've done already :)
[Wildfire Android Development] rolks:
seems wildfire reached at the end. too bad
[Wildfire Android Development] Scratch0805:
You're jumping the gun a bit imo, this rom runs perfectly it just needs the kinks ironing out!
[Wildfire Android Development] kaassaus:
We need to wait for cm9
[Wildfire Android Development] jamal2367:
in february ´?

_____________________________

/* SYNAPTICS DRIVER */

input_report_key(ts->input_dev, BTN_TOUCH, finger);

finger2_pressed = finger > 1 && finger != 7;

input_report_key(ts->input_dev, BTN_2, finger2_pressed);
[Wildfire Android Development] KeiranFTW:
@schiznik, can you compile with the flags to use legacy touchscreen?

I think it is in the TeamICS patches.
[Wildfire Android Development] -BULLIT-:
This rom does not work 4 me on my wildfire, boots 2 android logo and goes no further, left 4 30 mins an nothing, any1 help?
[Wildfire Android Development] KeiranFTW:
You need to install schiznik Rom first (to flash ICS ramdisk).

Then flash this.
[Wildfire Android Development] equiliym:
@schiznik just wanted to ask will you re-sync repo for 4.0.3 and recompile? just curious
[Wildfire Android Development] kaassaus:
Wait for cm9 idont think there will be here a new version of this rom
[Wildfire Android Development] -BULLIT-:
Thanx, will try this shortly
[Wildfire Android Development] schiznik:
Have you got a link, I can't work out which commits you're referring to
[Wildfire Android Development] schiznik:
At some point, yes. No idea when I'll get the chance to though.
[Wildfire Android Development] KeiranFTW:
What you should do (because I have little time :))

Add the following line to BoardConfig.mk:

BOARD_USE_LEGACY_TOUCHSCREEN := true

Then integrate the zImage from this ROM with ICS ramdisk for boot.img

Then, copy /system/lib/modules/bcm4329.ko from this ROM's update.zip to your new update.zip

Edit: you could actually use arco's kernel with the touchscreen fix :), try compiling his ICS kernel, it has more stuff done for it.

Or, you could ask me to compile it for you, should I?
[Wildfire Android Development] Stefanex92:
pls schiznik, with the help of Keiran, work to a new update *_*, i'd like to see v3 of this ROM
[Wildfire Android Development] schiznik:
Its already there:

$ grep TOUCH BoardConfig.mk
BOARD_USE_LEGACY_TOUCHSCREEN := true

I've done a build with your kernel already integrated, available here. If you want to build a kernel for this (my kernel skills suck ;)), I'll need the zImage and bcm4329.ko to get that integrated, I've PM'd you my email address to send them to.
[Wildfire Android Development] radeon7:
Hello people,

First sorry for my English.

Do you think CM9 support wildfire? Arco said if CM9 for wildfire development goes good?

Cheers
[Wildfire Android Development] DarkhShadow:
If the G1 gets ics port then we should get one :)
[Wildfire Android Development] radeon7:
I think the same as you but I saw the CM9 progress http://www.cyanogenmod.com/blog/cm9-progress-update and there CM team said that CM9 will support OMAP4, MSM8660/7X30, and Exynos and their goal is to provide continued support to all CM7 devices back to the QSD8250 series of devices such as the Nexus One and they are dropping Droid1 support. seeying this whats do you think?

I must practice my english :)
[Wildfire Android Development] DarkhShadow:
Hmm I'm not sure but I may be upgrading to wildfire s or nexus s i9023(not official in UK, its a nexus s just with out a amoled screen and is considerbly cheaper)

Still gonna keep this phone though ;)
[Wildfire Android Development] radeon7:
I love this phone. Is small and smart :) This phone must have ICS Rom :)
[Wildfire Android Development] DarkhShadow:
I agree this phone has lasted a lot longer than if we left it to HTC who lied about gingerbread -.-
[Wildfire Android Development] radeon7:
In this forum whe have 3 alpha ICS version for wildfire. This is a probe that if Cyanogenmod like the could develop a CM9 version for Wildfire. I prefer this phone like a Galaxy S or iphone because I hate a big smartphones wich I couldnt insert into my jeans :)
[Wildfire Android Development] Justice™:
If we dont officially get a CM9 rom, we always have Shiznick, Arco and jacob to build a rom and add in patches they've made for the wildfire. We will probably get an official CM9, since our device was made in 2010, and they plan on supporting any device from roughly 2010 onwards.

(Sorry for any names butchered, and somewhat false hope given if you're reading this in the future and we dont get ICS.)
[Wildfire Android Development] KeiranFTW:
You already have ICS, just needs sorting out.

Sent from my R800i - Darkforest ROM and Kernel
[Wildfire Android Development] radeon7:
Yes, you are right. we have ICS but not work completely. It is best to wait for surely we wil have CM9 for wildfire. If CM9 wont have wildfire version we could develop I am a software engineer and i have experience in programing software for Linux Beowulf clusters
[Wildfire Android Development] schiznik:
Any chance the general chatter can be moved to a non-Development thread?

I might have found a fix for the keyboard - https://github.com/TeamICS/android_device_htc_heroc/commit/af821957e0a18e2216d4bd6a94f8ddf9f7588b10 - just building a test v with this patch now.

Edit: Bah! that didnt work. I'll see if I can tweak the layout sometime, although I'll be busy with family stuff over christmas
[Wildfire Android Development] schiznik:
Seeing as arco has put a device config online i should have a much better base for this than my current hacked up one.

Depending on free time I'll hopefully have a new build of icyfire online in a week or so.
[Wildfire Android Development] [sito_web]:
good news! we'll hoping, have a good work bro..

oh and merry xmas and happy new year to all!
[Wildfire Android Development] usaff22:
Sorry to hijack the thread... but is the i9023 with S-AMOLED better or the i9020 S-LCD?

I am going to try flashing this one now, see how it goes.

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

Flashed it, I have a problem, this same problem was also on the other ICS ROM:

When it first goes to the lockscreen, I can touch the ring and move it to the unlock and camera functions, but none of them won't open. Touching on the clock or anywhere else on the screen makes the ring go to the outer edge of the circle as close as it can to where I touched. The volume buttons work. Then the screen goes black due to inactivity, and when I power the screen on again, it won't respond to any of my touches. I'm not sure what causes this problem. Any ideas?
[Wildfire Android Development] DarkhShadow:
The i9020 is the amoled version and is better only in terms of screen its just that the i9023 is cheaper

Sent from... somewhere...
[Wildfire Android Development] hexameron:
I was messing about with system.prop in CM9 to try and get all the keyboard on screen :

"ro.sf.lcd_density=100" seems to help a bit.

At least now I can use all the letters, and space/return are tangible.

Obviously there is a better way of fixing that, and I am sure that Arco will tell us in due course.
[Wildfire Android Development] bpye:
The keyboard requires an "overlay" in the device configuration so that it fits the screen correctly. It's mostly an XML layout job.
[Wildfire Android Development] schiznik:
I know :)

Drop me a pm & I'll point you towards the layout file. I'm not the best so any help would be appreciated.
[Wildfire Android Development] Stefanex92:
But u Will work on your ROM or you Will work on arco ROM
[Wildfire Android Development] schiznik:
Arco is part of the CM team, I'm not.
[Wildfire Android Development] Justice™:
I'm guessing Arcos base and libs will be used for the new iceyfire build, since they are pretty complete. But it will still remain iceyfire, not CM9. Features from CM9 might be included, like the new launcher. But who knows?
[Wildfire Android Development] schiznik:
It'd be the stock launcher in my builds. Nothing to stop you installing Trebuchet yourself though.

Sent from my Galaxy S2 running CM9 Alpha
[Wildfire Android Development] usaff22:
Does anyone know why the touchscreen didn't work? Because everyone else says it works and I don't know what goes wrong in all my ICS installations
[Wildfire Android Development] DarkhShadow:
Did you flash the V2 file after? You need to do thar

Sent from... somewhere...
[Wildfire Android Development] schiznik:
here

The build above has all the fixes integrated and doesn't need anything else flashing.

Sent from my Galaxy S2 running CM9 Alpha
[Wildfire Android Development] Stefanex92:
A new version? Or the same?
[Wildfire Android Development] schiznik:
Newer than the builds in the first post. Its 4.0.3 with everything integrated so you don't need to flash multiple zips.

If you flashed it when I originally posted it a few pages ago then no its not newer :)

Sent from my Galaxy S2 running CM9 Alpha
[Wildfire Android Development] kaassaus:
Wifi dont work
[Wildfire Android Development] Stefanex92:
I'll try it

ok, then: touch is good, can be more better there is lag, no signal, no wifi, bluetooth ok
[Wildfire Android Development] Justice™:
Is this based on Arco's device base and stuff? Or not?
[Wildfire Android Development] schiznik:
Nope, its the build I posted a few days before Christmas (as can be seen on the datestamp of the zip......). Haven't had a chance to look at arco's config files yet.

Sent from my Galaxy S2 running CM9 Alpha
[Wildfire Android Development] Stefanex92:
Schiznik did this rom on 20 dec while arco on 23
[Wildfire Android Development] usaff22:
Yeah I flashed everything before, I will try flashing this to see how everything goes.
[Wildfire Android Development] JaegerStriker:
This ics keyboard works on cm7 havent had chance to check on ics rom but it should work

the portrait works perfect!

Hope this helps

tried on arco's cm9 rom and it force closes :(
[Wildfire Android Development] hacktrix2006:
it works for me that file on acro's rc0 cm9 build for buzz.

Apart from that acro's RC0 of CM9 seems to be rock solid a few bugs, mainly the Camera and trackball not working for wake etc. But as a whole its infact a daily rider rom for me.

Music and Video plays

Smooth but can get slightly laggy

Wifi BT GPS 3G EDGE HSPDA works.

GSM network search doesn't yet although you can still make phone calls so it could be config settings there.

Browser seems to white screen but 3rd party ones don't

But overall between acro schiznik KeiranFTW and the rest of the CM9 team working on BUZZ i can safely say i can not wait for a Stable release with all the tweaks CM Team puts in and also schiznik's version from the sources like in the oxy rom he compiled which was great BTW.

Keep up the work and my respect goes out to you all developers of the Good Oldie Wildfire (BUZZ).

Will have a look at the Camera HAL issue via Logcat making a pretty big one ATM just incase that helps anyone.
[Wildfire Android Development] abumaha:
i flashed but can´t unlock home screen
[Wildfire Android Development] Justice™:
Go check out arcos builds in the what's next thread.
[Wildfire Android Development] abumaha:
what exactly?
[Wildfire Android Development] abumaha:
stuck on boot android logo 30 min what´s up
[Wildfire Android Development] abumaha:
now done stuck on bootlogo cant go in recovery mode

pls help what can do now button not work at side
[Wildfire Android Development] procyon-1:
Head towards wildfire general section ,what's next topic,u can find cm9rc0 there dwnld the latest build flash it and u wont have this probs enjoy:)
[Wildfire Android Development] abumaha:
my problem now is cant get in recovery modus

i used to make this with rom manager but now even the phone is stucked at the boot logo and volume button not work how to get on pls
[Wildfire Android Development] procyon-1:
Try removing d battery and then enter recovery mode by using volume down and power button
[Wildfire Android Development] abumaha:
pls told u they don´t work another way over desktop pls

when using unrevoked say device sbin sh getprop not found
[Wildfire Android Development] procyon-1:
Dude I don't have any knowledge to help u get rid of this but this thread might help u try contacting 3xeno.

http://xdaforums.com/archive/index.php/t-1314743.html
[Wildfire Android Development] abumaha:
touch not work after install ?
[Wildfire Android Development] schiznik:
Don't use this rom, there's many things broken in it - use the ics cm builds Erwin is compiling instead.

Could a mod close this thread please?
[Wildfire Android Development] KeiranFTW:
Took the words from my mouth :)

Sent from my R800i using MIUI
[Galaxy S II Q&A, Help & Troubleshooting] cukisan:
Hi guys, I recently took a sgs2 NFC technology. Can I change the rom with a criskelo as well as with the normal?

thank you very much
[Galaxy S II Q&A, Help & Troubleshooting] mr mystery:
Sorry I have no idea what you are asking here, you took an NFC technology????
[Galaxy S II Q&A, Help & Troubleshooting] DrunkFuX666:
Lol... I agree... what does that mean...?? I would also like to take nfc technology on my s2 if possible since mine isn't the Korean version...

Or maybe he is saying he got the Korean version... hmmmmm...

Sent from my Galaxy SII
[Galaxy S II Q&A, Help & Troubleshooting] ambar_hitman:
I think he is saying that he got NFC version of S2 and asking for ROM compatibility.
[Galaxy S II Q&A, Help & Troubleshooting] _Noctis_:
i was thinking about whether to wait for NFC to hit all of SG2, or maybe getting one from the UK (had to wait for a while, since it was rumored they'll get there eventually) ... but eventually decided that even though it's a nice sounding feature, i can probably live without it, and just got mine :)

anyways, assuming you have a korean phone with NFC support, you think it won't work unless you have a ROM built specifically with that support?

i guess it'll take most roms out there out of the question ...
[Galaxy S II Q&A, Help & Troubleshooting] cukisan:
Sorry but maybe I expressed myself badly ... I bought the new i9100p which is the version with the NFC chip to shop (here in Italy this technology isn't coming soon ..: Mad:). I wanted to know if you think the rom for the i9100 normal are compatible. until a short time ago I had the regular version and with the criskelo I was fine ..
[Galaxy S II Q&A, Help & Troubleshooting] DrunkFuX666:
I was going to try to get the nfc version myself but didn't due to this particular confusion whether its compatible or not...

Some people said that with the nfc version all it is, is the nfc chip which is installed in the back cover and the battery but the rest of the phone is essentially the same... if that's the case it should probably work... but again I can't say for sure... the model is still i9100, just adding the P... I think it should work... but I would suggest you maybe ask in the respective rom thread or maybe PM criselko himself and see what he says...
[Eee Pad Transformer General] drebbs:
Are you kidding me? 14 quid from pcworld! Linux needs an antivirus?!!!?
[Eee Pad Transformer General] Dyskmaster:
maybe corprate and government issued android phones need it, but if you have common sense and actually READ the permissions you are giving to an app (and look at the reviews, just to be sure) you should know what is or isn't "poisoning" your system. By "poison", I mean that there are not "viruses" on android, but, rather, apps which are meant to be malicious in nature by acting very similar to how trojans or malware work. Normally, these malware apps aren't very hard to remove yourself (or even discover) especially with root access which is why android users shouldn't concern themselves THAT much with antivirus measures and such.