yashsingh1/xdaforums huggingface dataset:
[Wildfire Android Development] Justice™:
None, assuming your nandroid backup went ok. Nandroid backups are a complete backup of everything on all your phones partitions.

On a side note. Congrats on sorting out touchscreen and souch. Waiting on the idc file. Will try this out with a MTD partition tonight/tommorow just to confirm it working!
[Wildfire Android Development] MattDN93:
Haha you guys are lucky I got 50mins ;) 0.38mbps internet :(
[Wildfire Android Development] djinn0:
need to flash other things like infinityice kernel? or only install this? thank you keiran
[Wildfire Android Development] Formiak:
Such slow internet all over the RSA ?
[Wildfire Android Development] Justice™:
Just this rom.

/11char/
[Wildfire Android Development] KeiranFTW:
This is what I am currently using for the amtel-touchscreen.idc file

# Copyright (C) 2010 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

#
# Input Device Calibration File for the Bravo touch screen.
#
# These calibration values are derived from empirical measurements
# and may not be appropriate for use with other touch screens.
# Refer to the input device calibration documentation for more details.
#

# Touch Size
touch.touchSize.calibration = pressure

# Tool Size
# Driver reports tool size as a linear width measurement summed over
# all contact points.
#
# Raw width field measures approx. 1 unit per millimeter
# of tool size on the surface where a raw width of 1 corresponds
# to about 17mm of physical size. Given that the display resolution
# is 10px per mm we obtain a scale factor of 10 pixels / unit and
# a bias of 160 pixels. In addition, the raw width represents a
# sum of all contact area so we note this fact in the calibration.
touch.toolSize.calibration = linear
touch.toolSize.linearScale = 10
touch.toolSize.linearBias = 120
touch.toolSize.isSummed = 1

# Pressure
# Driver reports signal strength as pressure.
#
# A normal thumb touch while touching the back of the device
# typically registers about 100 signal strength units although
# this value is highly variable and is sensitive to contact area,
# manner of contact and environmental conditions. We set the
# scale so that a normal touch with good signal strength will be
# reported as having a pressure somewhere in the vicinity of 1.0,
# a featherlight touch will be below 1.0 and a heavy or large touch
# will be above 1.0. We don't expect these values to be accurate.
touch.pressure.calibration = amplitude
touch.pressure.source = default
touch.pressure.scale = 0.01

# Size
touch.size.calibration = normalized

# Orientation
touch.orientation.calibration = none

Here is another one I found:

ouch.deviceType = touchScreen
touch.orientationAware = 1

# Touch Size
touch.touchSize.calibration = pressure

# Tool Size
touch.toolSize.calibration = linear
touch.toolSize.linearScale = 10
touch.toolSize.linearBias = 0
touch.toolSize.isSummed = 0

# Pressure
touch.pressure.calibration = amplitude
touch.pressure.source = touch
touch.pressure.scale = 0.01

# Size
touch.size.calibration = diameter
touch.size.scale = 10
touch.size.bias = 0
touch.size.isSummed = 0

Touchscreen works without IDC file, but only as a pointer...
[Wildfire Android Development] MattDN93:
Nah if you're lucky and can afford it 4mbps or 10mbps is standard, but it's really expensive. Can't afford it at the moment so hoping ISP will upgrade speed for free, they've been doing data cap increases already :)
[Wildfire Android Development] Justice™:
I'll assume you've tried both..? If you havent. Me or someone else will have to compile a version with the second idc file in it to see if it has any changes. About to flash your rom on a MTD partition wildfire. Is it roughly the size a normal AOSP or more?
[Wildfire Android Development] djinn0:
i have try but only touchscreen in status bar working. when the next update with working touchscreen?
[Wildfire Android Development] androidino95:
Tried it, good start! Good luck with further development.

Nice to see ICS on the Wildfire.
[Wildfire Android Development] KeiranFTW:
Roughly AOSP, about 90MB

For making IDC (touchscreen config files):

Open notepad, paste the code into notepad (edit it a little if you want), then save as atmel-touchscreen.idc in your ADB folder.

Open the command prompt and CD into your adb folder, eg.

cd android-sdk-windows/platform-tools/

Now, when you have done that, boot into recovery on the phone (adb in ICS is very experimental), mount /system/ (in CWM) on the phone and then type these commands into the opened command prompt:

adb devices

adb push atmel-touchscreen.idc /system/usr/idc/atmel-touchscreen.idc

unmount /system/ then:

adb reboot

now your phone should boot and you can test to see if the touchscreen works.
[Wildfire Android Development] Justice™:
Booted and installed fine, stuck at lockscreen as expected. Seems to look allright. While it might not be a great idea to say this as its the only the lockscreen, but animations look great (lock ripple and such, lovely and smooth!)

Basically, we need to get the drivers from another HTC device with a amtel touchscreen. (Hero, eris, possibly desire)

Impressed though at how the gpu isnt a requirement for ICS.
[Wildfire Android Development] Karting06:
you can see for the buttons here http://xdaforums.com/showthread.php?t=1354267

if you found anything as apk or something else.
[Wildfire Android Development] MattDN93:
Cool :) Flashing now, I'm assuming you restored your original Nandroid via Recovery?
[Wildfire Android Development] KeiranFTW:
Going to replace some of the LIBS with CM7 ones.

I have the source code drivers, and I am watching this thread: http://xdaforums.com/showthread.php?t=1332605&page=13
[Wildfire Android Development] kaassaus:
I try the version but ones the touchscreen works and than not working
[Wildfire Android Development] KeiranFTW:
It picks up the first touch, but I don't think it recognizing you letting go...
[Wildfire Android Development] Justice™:
Nice. I believe kaassaus tried some of the CM7 libs on his source build and it didnt work. But maybe it will work on a eris port.

Still running on ICS to try out fixes mentioned by Keiran...
[Wildfire Android Development] Karting06:
What do you mean. I don't understand it :(
[Wildfire Android Development] kaassaus:
My rom is a port from the eris ;) and yes i have try the libs but itdidnt works
[Wildfire Android Development] MattDN93:
Hmmm...I'm getting bootloops, not cool...any ideas?
[Wildfire Android Development] Karting06:
Wipe (data/cache/dalvik)

Install the ROM

Then the kernel.
[Wildfire Android Development] MattDN93:
I thought the latest version of the ROM didn't require the kernel?
[Wildfire Android Development] KeiranFTW:
Correct, installing it has no effect because it is built in.
[Wildfire Android Development] Karting06:
Ah, it's possible.

So no kernel :D
[Wildfire Android Development] kaassaus:
Required
[Wildfire Android Development] Karting06:
Euh, not logical !
[Wildfire Android Development] KeiranFTW:
Negative, I pushed my kernel installing script into your zip, removed your boot.img script and boot.img and added my zImage. Then added changes.

Testing a one with all of CM7 libs now.

Dang, can't get touchscreen to work properly. Maybe back to pointer mode :///

Might have to rebuild samsung drivers for the wildfire, sounds fun.

ReEdit:

http://dl.dropbox.com/u/13729847/InfinityPLAY/WildICE.zip <- has CM7 libs.

as for signal and stuff, that is to do with the build.prop

Also, might go down the line (if I can) and try to edit mxt224.c to work on the buzz, and then touchscreen should work fully!

If anyone can do test IDC's, I would appreciate it.
[Wildfire Android Development] Justice™:
Returned back to CM7. Found out power off doesn't work
[Wildfire Android Development] KeiranFTW:
That might be because the touchscreen recognises your press, but not when you let go...

This will probably fixed (htc?) because I think the Sensation has an atmel screen.
[Wildfire Android Development] arco68:
Guys, I know I can't stop you messing around with this "zipfile developing" (which btw have been too much of around here lately, imo), but what exactly are you expecting to accomplish? You just can't go around replacing various files with ones from gingerbread, and magically expect it to work. The code is just too different for that. Where the real work has to be done is in the source, as right now it's missing a lot of stuff for old hardware, and especially for armv6. It's gonna take a while, if it's doable, so you just need to be patient. Right now I have a device config that compiles and boots fine, with working touchscreen. But there's still lot's of things to implement. Things like button backlight, compass, audio, camera and gps doesn't work. It's also butt slow due to missing optimization for software GL. Sorry for sounding a bit harsh, but I just want you to know what the reality is.
[Wildfire Android Development] kaassaus:
You have a worked version why dont you post that :)?
[Wildfire Android Development] KeiranFTW:
I understand completely, but I am not, nor do I claim to be an experienced developer.

My last zip doesn't boot, so I am just going to stop here, you have touchscreen working and a correct device config so there is no point me messing about with binaries when you have working source.

Is your source on GitHub? And could we have a tutorial? I only started with android development last week and I am still learning.

Because you have working source, I feel there is no need for me to continue on this rom.

You didn't sound harsh at all, but I ask one thing.

If you start the ROM with source, and tell us how to compile and set it up, then we can all contribute.

Regards,

Keiran
[Wildfire Android Development] Justice™:
Very true. Allthough I have one thing to say about zipfile developing. It happens in other parts on this site, people see the responses on thosse "roms" and think. "Hey, why not make my own rom like this, and gain respect". And post a version of a already released rom with some UI changes on this part of xda..
[Wildfire Android Development] KeiranFTW:
Wasn't my rom, I was just helping out with the touchscreen, but now we find out lord arco has already done it nicely for us, all we need to do is sit back and relax :)

Restoring my CM7 now.

Some "zipfile" development is okay (SenseOnFire) as it is new, and of course stock.

But some is just repackaged goods.
[Wildfire Android Development] kaassaus:
Pfff and now.....
[Wildfire Android Development] Justice™:
Yeah, I must say that your rom is not repackaged goods considering the patches you'be added. As Arco seems to be working on the ICS source, I guess its time to sit and wait!
[Wildfire Android Development] KeiranFTW:
It would be great if he gave us a beta. But then I think I would rather wait if it would be better at the end.

So - No ICS for me, well, for now that is.
[Wildfire Android Development] :
Pfff? Pfff that Arco did something you couldn't?
[Wildfire Android Development] kaassaus:
No :s ihave school and have other things to do so...

And i'm happy that he working on it.

Only icant wait for trying his version
[Wildfire Android Development] Justice™:
The closest we'll get to a open beta of Arco's ICS rom, is the early CM8/9 nightlys. Which should be a worthwhile wait!
[Wildfire Android Development] arco68:
I could upload a copy, but it's not very useful for anything else than poking around. I'll work a bit more on it, and then we'll see.
[Wildfire Android Development] KeiranFTW:
Now, now, don't tease :)

A beta would be nice!

You could have it seperate from CM9 (like you did with nFinity-GB for the tattoo :)

Keiran
[Wildfire Android Development] kaassaus:
A copy will be greath:)

But if you realy dont want to upload it i underdstand.
[Wildfire Android Development] :
Oh... ok ;D
[Wildfire Android Development] MattDN93:
Thanks Arco, I guess we can take out our early ICS cravings on what you release and then chill till the real job comes out:) however messing around on Kieran's zip in pointer mode last night I managed to unlock the phone, open the menu and some apps, which didn't lag at all...just the soft keyboard needs resizing ...and I powered off fine by holding the power button and clicking "power off"
[Wildfire Android Development] Zorkman:
Hi Arco,

thanks for voicing your opinion in this thread and especially the news that you're working on ICS for buzz.

if you need any eager testers you know where to find us

The fact that in this alpha rom there doesn't seem to be a significant lag, does give me a bit of hope for the future of ICS on our buzz
[Wildfire Android Development] Karting06:
We must to search for a .idc driver for the touchscreen. That must we set on /system/usr/idc.
[Wildfire Android Development] MattDN93:
Arco has mentioned his ROM has a functioning touchscreen:

If the whole point was for everyone to suspend ICS porting because Arco has already achieved what you've been trying, why would you want to find an .idc? Just wait for Arco's ROM.
[Wildfire Android Development] schiznik:
Hey arco, are the sources for this online anywhere? I've been trying to get ICS built too, would be good to compare the two to see if I've missed anything - havent even managed to get mine built yet :-(
[Wildfire Android Development] i859:
any news about porting? i am waiting ics too :)
[Wildfire Android Development] MattDN93:
We're waiting for arco's ICS ROM but if you want try these ROMs in progress (no touchscreen yet):

http://xdaforums.com/showpost.php?p=19529114&postcount=1

http://xdaforums.com/showpost.php?p=18567292&postcount=1
[Wildfire Android Development] arco68:
No, not yet.
[Wildfire Android Development] kaassaus:
Can you share youre build?

Than whe maby can learn thing from ics.
[Wildfire Android Development] fifarunnerr:
Guys, stop freaking nagging arco!

Let him continue on CM9, let him take a break, let him get some sleep. Don't start nagging about releasing. And don't ask for ETA's.

You guys can't learn anything from ICS source, because you guys don't understand C.
[Wildfire Android Development] kaassaus:
Are you dutch?
[Wildfire Android Development] i859:
we only want to test arco's rom, nothing more
[Wildfire Android Development] Justice™:
Looks like you'll have to wait for early CM9 nightlies.
[Wildfire Android Development] fifarunnerr:
Yes, why do you want to know? I'm not going to translate it for you.
[Wildfire Android Development] kaassaus:
Iam only asking man.
[Wildfire Android Development] Formiak:
I have the same opinion as fifarunnerr , guys stop nagging him.If arco don't want to release he won't do it.

Read with comprehensive , he said "not yet " so it means in future he can but not necessarily .

I suppose arco doesn't like uploading not finished or not working fully rom's.

I think it's good ,we can shelter from ****ty roms in this way.

Better will be to have a look and learn as fifarunerr said some of C+ ,C# etc..

(I'm not trying to offend people who know a bit)
[Wildfire Android Development] Scratch0805:
Agreed take the time to learn while we wait!!
[Wildfire Android Development] Justice™:
+1

I'm sure most people here are annoyed by threads being bumped by people wanting someone like arco to release his work. As well as whole new threads being created for CM renames and such.
[Wildfire Android Development] Formiak:
Arco won't upload this because he is working under CM9 and adding some patches into ics branch.
[Wildfire Android Development] Justice™:
Looks interesting. But I'm slightly worried about this:
[Wildfire Android Development] Formiak:
Don't contemplate whether it will be implemented or not , good is that good devs are working on it :-)
[Wildfire Android Development] Justice™:
True, If we dont get ICS in the form of CyanogenMOD (or any ARMv6 device if they reject this patch.) I'lll know we'll get it somehow from the ARMv6 devs like Arco.
[Wildfire Android Development] JaegerStriker:
is this any help

i would see if it works but i dont know where to put this

https://github.com/kornyone/htc-ker...7f4735140086cb6d98e5329566e7acae11d453#diff-0
[Wildfire Android Development] Justice™:
looks like the idc file keiran posted a few pages back. Could possibly be diffent.
[Wildfire Android Development] JaegerStriker:
do you know where i would put this im a complete noob at this
[Wildfire Android Development] MattDN93:
What's interesting there is the fact that they don't want him submitting this code, it will help ICS and ARMv6 devices so why are they saying he shouldn't post it?
[Wildfire Android Development] Justice™:
Follow the guide posted a fewe pages back. Basically what you get from that is, you need to save the file you found as a idc file in notepad. use adb to get it over to your phone by mounting the system partition in CWM and then using /adb push or something like that. The tutorial a few pages back will give you a better idea than this.

---------- Post added at 11:33 PM ---------- Previous post was at 11:30 PM ----------

I was saying it was interesting that it got to CyanogenMOD so fast. I was worried mainly about it getting downvoted by one of the CM team. Meaning that they possibly dont want CM on older devices?
[Wildfire Android Development] MattDN93:
Oh right:) well that's how the real devs roll, we speculate in the forums and they just get on with the code...

it would be a shame if they refused, but surely there are some newish devices (Droid Eris etc) with ARMv6 CPUs plus GPUs which could justify this patch and indirectly help the Wildfire people like us;)
[Wildfire Android Development] Stefanex92:
what is changed in the v0.2?
[Wildfire Android Development] KeiranFTW:
People, I think the reason it got a -1 is because maybe that person thought that the patch might break elements of other code?

They wouldn't do it just because the devices are old.

Sent from my HTC Wildfire
[Wildfire Android Development] Stefanex92:
i flashed the v.02 with the correct kernel but it's staing always on bootanimation (android), why it doesn't go forward?
[Wildfire Android Development] Karting06:
Go to CWM;

Wipe data + dalvik

Install the alpha 2

Reboot

(no kernel)
[Wildfire Android Development] Stefanex92:
doesn't work, it stayed for whole night on bootanimation -.-
[Wildfire Android Development] Bwfclew07:
Just a small idea, i think it would be good if you do end up making this rom to run well on the wildfire that maybe you could make a clean version of your custom rom for example with no third party apps or modificstions apart from the nesesary ones like super user and device reliant software so users can download it and customise it to their liking as well as your link to your rom that you are developing, just an idea :)
[Wildfire Android Development] i859:
we are waiting for arco68's rom, then we can work with it
[Wildfire Android Development] MattDN93:
Wipe the dalvik first, do a full user + data wipe and then install ROM...use your Recovery CWM not the one from ROM Manager, mine bootlooped like that too!

---------- Post added at 04:38 PM ---------- Previous post was at 04:20 PM ----------

I think Arco knows what he's doing enough to add code to the project that won't simultaneously self-destruct the rest of it...I hope :)

Anyone have any ideas why this change on CM Code Review is different to this one?
[Wildfire Android Development] schiznik:
Because one is a path to android_build, and the other is a patch to android_dalvik?

Both are needed to build ICS for armv6 devices.
[Wildfire Android Development] Stefanex92:
doesn't work -.-, how many times i have to say?
[Wildfire Android Development] Justice™:
Then its time you give up and go back to CM whilst you wait.
[Wildfire Android Development] Stefanex92:
isn't rom that don't run, but the installation because during the power it arrive alone the bootanimation , i didn't say that the rom don't work, read all before -.-
[Wildfire Android Development] eagleofdeath13:
Which version of CWM do you have? If less than 5.0, you know what's wrong ;)
[Eee Pad Transformer Q&A, Help & Troubleshooting] twistedsixty4:
hey everyone,

so i finally got the dock for my TF a couple weeks ago.. i have several friends that are not as tech savvy as i am, but still like android, well i want to offer to root their devices for them. more out of curiosity then need i was wondering if it is possible to unlock and push the recovery from a TF? i know that the TF has ADB on it, but i havent really started any development on the TF its more for fun, i use my nexus 1 for development.. any light you can share on this would be appreciated.
[Eee Pad Transformer Q&A, Help & Troubleshooting] jesseibiza:
Interesting...

Nice thread i hope some one comes up with further info about this idea i would like to do this too!!!! I have sold mi laptop TF can do everything... And soon W8 will be possible on it and STABLE Ubuntu!!!
[Eee Pad Transformer Q&A, Help & Troubleshooting] brando56894:
I was contemplating this also since a girl I work with wanted me to root her Galaxy S1 but I only had my TF with me and we can't install drivers on the work computers.

I assume it should be possible, you just may need more of the Linux binaries, for example you may need to do it via a chroot install of Ubuntu or as a native (dual-boot) system. Look at the shell scripts and see what binary tools they require (cp, mv, cd etc...), you may be able to do it with Android's toolchain.
[Eee Pad Transformer Q&A, Help & Troubleshooting] hachamacha:
There's something in the market called "remote adb" which "might" be of use, but I kind of doubt it. It could also be one of those adbwireless versions of adb where you still do the heavy lifting from the PC.

My take would be to look at the results of google "+source +adb +android" and you'll get a couple of hits that point at adb repos in git format.

Then use a linux box to clone one and point it at some crossbuild tools (see for example the howto build kernel threads that are here and there) and built it for our architecture (arm{le}). I've done this for the bash shell and a few other things I liked in linux and it should be possible. One built, push it into /system/xbin, chmod 755 adb and see how things go.

I don't have the keyboard dock or the OTG dongle so no point in my doing it since I can't test.

Good luck -

edit: http://lackingrhoticity.blogspot.com/2010/02/how-to-build-adb-android-debugger.html seems like as good a place as any since it has source, instructions, etc. So probably all you have to do (if this nutty project will work at all) would be to modify the Makefile so that it's pointing to the toolchain for armv7le (or that's what uname -a shows on my eeepad).

edit: Another one that's already been built for android (I tested it), is sshd or dropbear and here is a link: http://jhulst.com/c/dropbear-ssh-android .

The main thing is being able to hit the device you want to setup using either ssh or scp, and functionally this'll do most if not all or more than adb will. What won't work are any scripts written that are already using adb commands.
[Eee Pad Transformer Q&A, Help & Troubleshooting] twistedsixty4:
thanks for the input originally i was thinking being able to use terminal inside honeycomb, but i suppose the easier (or perhaps better stated, the "road more traveled") route would be dual booting linux and just setting up the dev kit on there..
[Eee Pad Transformer Q&A, Help & Troubleshooting] Danzano:
Latest version of ubuntu by little stevie is your best bet :)
[Samsung Epic 4G Touch] AestenD:
I'm trying to access the ## settings, data and 72786. However when I type the codes into my dialer, the code disappears from the screen, but nothing pops up. I have quite alot frozen in Titanium, but I went through any that looked like they might be the culprit and nothing changed.

Any suggestions?