Database Develop

[rom] -tattoo eclair 2.1 [wip]

Status:
Working:
-Dialpad
-Bluetooth
-GPS
-Wifi
-Tattoo Buttons
-Touchscreen
-3g
-sensors
Not working:
-Fm Radio
-Camera
-Some Icns have wrong Size
-Some issues with graphics (mainly 3d)
Roms:
1) http://forum.xda-developers.com/showpost.php?p=5961430&postcount=50
Updated: 2) http://forum.xda-developers.com/showpost.php?p=6000675&postcount=103
better HTC-IME.apk http://forum.xda-developers.com/showpost.php?p=6089811&postcount=154
nexus launcher: http://forum.xda-developers.com/showpost.php?p=6100769&postcount=160
3) update 3 sensors working ) http://forum.xda-developers.com/showpost.php?p=6139158&postcount=197
4)V5 http://forum.xda-developers.com/showpost.php?p=6229047&postcount=300
thanx to : rhoa,ivendor,spartm and terminal 7
ps. sorry for the late update but I didn't have net connection.

ALL FROM THIS THREAD 5. april 2000 hours dk time
great ...reserved for future use
THX
Marsdroid

Is there any progress about porting android 2.1 to tattoo?

I have an OpenEclair port that works on Kaiser, with the edits to make the phone usable for QVGA. I'm sure there's a way to get OpenEclair working for Tattoo... the main problem I expect you'll face is enabling the new 3D drivers in the kernel.

can you please share it ?

I have an OpenEclair port that works on Kaiser, with the edits to make the phone usable for QVGA. I'm sure there's a way to get OpenEclair working for Tattoo... the main problem I expect you'll face is enabling the new 3D drivers in the kernel.
Click to expand...
Click to collapse
But tattoo doesn't have GPU :\

That's OK, 2.1 will run fast enough with only software rendering, we didn't have 3D working for a while. Having the 528Mhz proc (we only have 400Mhz) will help too. I will say that my build doesn't have SenseUI, 2.1 SenseUI doesn't work on QVGA yet AFAIK.

So we have to find the way to run 3d driver in the kernel and then we'll can use 2.1 rom? Awesome

No, if you don't have a GPU don't worry about 3D
Here's how I think you can do it:
Download OpenEclair 1.2.2 (http://openeclair.net)
replace the kernel with your kernel
(we use a different kernel for Kaiser and it works just fine)
Merge OE's build.sapphire.prop into OE's build.prop so Android uses the MSM7K drivers
(You can change in build.prop the 'sapphire' texts into 'tattoo', but it really doesn't matter)
Diff the init.rc's to check for differences and fix any important ones
(and you'll probably want to fix this minor bug in OE's init.rc)
Check the /system/ folder of OE 1.2.2, it might be too big for Tattoo's system partition. If it is, move some apps from /system/ into /data/app_s/ until /system/ is small enough.
Pack it up and flash it
The dialer doesn't fit perfectly on QVGA, but I have the .apks to fix that. First someone'll have to be brave enough to try to port a ROM and boot it

Me will do that later...

I'll be brave enough to test it. But I'm lacking the skills to try to port it myself.

Hi,
I've try this wrokarround, rewrite a updater-script, modify kernel for boot.img and init.rc.
But !!!! My device hang at "Tattoo" logo when he start, there is a solution for debug this step ?

I find
I used a boot.img from 5faif ROM and just change init.rc, not a good solution but device boot for this time
Now I have rom boot ok in 2.1 but screen resolution is bad ... next try maybe

--> you're my hero

If you manage to make a working 2.1 rom for the Tattoo you will become my new God ...

lgstoian said:
If you manage to make a working 2.1 rom for the Tattoo you will become my new God ...
Click to expand...
Click to collapse
I said the same

rhoa said:
I find
I used a boot.img from 5faif ROM and just change init.rc, not a good solution but device boot for this time
Now I have rom boot ok in 2.1 but screen resolution is bad ... next try maybe
Click to expand...
Click to collapse
Oh sorry, forgot to mention. In build.prop change:
Code:
ro.sf.lcd_density = 160
to
Code:
ro.sf.lcd_density = 120
That should fix it

I wish i could help in some way but i've only had my tattoo for an hour! Will love it if you guys get 2.1 working properly. Great stuff.

polyrhythmic said:
Oh sorry, forgot to mention. In build.prop change:
Code:
ro.sf.lcd_density = 160
to
Code:
ro.sf.lcd_density = 120
That should fix it
Click to expand...
Click to collapse
Uh.. plus you're going to need libs for audio/ gps and the ril for eclair. They're not the same as donut. Kaiser/vogue dev and tattoo dev are alot different.

you are the best

[ROM] SpeedLegend v0.6 [Senseless]

[DISCONTINUED!]
There are so many good roms out there, no need for this one. I nowadays prefer CyanogenMod6 and will stick to it, with small modifications. I suggest you do the same ;-)
So, here it is! My first cooking
The ROM is VERY stable. About 170MB free ram standard. When using a task killer (kill ALL) the RAM boosts up to 225MB. So this is my first public release, been tweaking and trying out different combinations of apps, more changes will come!
SpeedLegend v0.6 - Update Base 2.03.405.3
Changelog:
Boot sound removed!
Facebook sync loop fixed!
Bluetooth fixed! (Successfully transfered pics between my nokia and legend both ways)
Flickr re-added.
LauncherPro, ROM Manager, XDA-App, EStrong File Manager removed (d/l what you want from market! customize yourself!)
Full changelog of ALL removed files coming up at a later point. Right now? I'm too tired!
No more A2SD version as it didn't seem to work properly.
SpeedLegend v0.511 - Minor update Base 2.03.405.3
Changelog:
Dialer One re-added (sorry about that)
HTC Lockscreen removed (Now using Vanilla Lockscreen)
HTC Peep Removed (now using Official Twitter, uninstallable)
Removed some more useless HTC stuff (nuff said! )
Home Switcher removed (just get it from market if you want it)
SpeedLegend v0.51 - Minor update Base 2.03.405.3
Changelog:
Added XDA-App (uninstallable)
Added ROM Manager (Uninstallable)
Removed HtcMusic (Replaced by Eclair Music)
Removed HtcWorldClock (Replaced by DeskClock)
Removed some more useless HTC stuff
Deodex'd!
Without and with a2sd (a2sd untested! Please report!)
SpeedLegend v0.5 - Initial Release Base 2.03.405.3
What is Removed
Startup Wizard -> No wizard at first boot! (Useless?) Add accounts by Settings -> Accounts & Sync!
Sense UI (Rosie)
All HTC Widgets (or at least most of, until I know what all htc-files do. WIP!)
HTC Dialer (Replacement: Dialer One)
Weather (and all there is to it)
FieldTest (what is it?)
HTC Flickr
Footprints
PicoTts (text to speech)
And possibly alot more I've forgotten all about...
Moved to Uninstallable:
Calculator
Facebook
FriendStream
Peep (Twitter)
Voice Recorder
PDF Viewer
Maps
QuickOffice
Teeter
YouTube
Added to System:
ROOT (of course)
Dialer One (check out the screenshot)
Added (Uninstallable)
LauncherPro 7.1.0
Home Switcher
EStrong File Manager
USB Switcher
Other:
Facebook support remains intact! Syncing contacts with pics perfectly!
Download v0.6 - 4shared
Download v0.511 - 4shared
Download v0.511 a2sd - 4shared
Download v0.51 - Link removed!
Download v0.51 a2sd - Link removed!
Download v0.5 (no waiting time)
Download v0.5 a2sd (no waiting time) [UNTESTED! Can't test it myself due to class2 sd-card! (min class4 required!)]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Known Issues/ToDo (v0.511)
No popup when connecting the phone to a computer, eg. no disk drive. Added USB Switcher (widget) until I manage to fix this (probably removed somthing that is needed). Add USB-widget to homescreen, connect phone to USB, press the widget - Now you have a disk drive connected.
Some options in Settings (Personalize, Text to Speech, Connect tp PC) cause FC because of Rosie and Tts-services removed.
Not ROM-related:
Want Live Wallpapers? Go Here!

Looks good : D
But I'll wait, as I haven't been doing any flashing with my phone yet, and I kind of like it as it is.
If possible without too much hassle, why not remove the messaging-app and install handcent(or something) instead?
And btw, why are you using the 2.03 ROM now when the 2.05 is out?

Looks good
no-one has released a 2.05 to use as base is pretty much the answer, i will use 2.05 as a base for my rom when someone releases it

jonaseg said:
If possible without too much hassle, why not remove the messaging-app and install handcent(or something) instead??
Click to expand...
Click to collapse
It's very possible, I just like the stock HTC messaging app I have never tried hanscent, maybe I should check what it's all about..

I liked it too, until they made it unusable(doesn't scroll all the way down when opening a thread..) in 2.05..

jonaseg said:
I liked it too, until they made it unusable(doesn't scroll all the way down when opening a thread..) in 2.05..
Click to expand...
Click to collapse
When base 2.05 comes, and if that bug still persists - I will definetly change the app to something else. But I'm trying to keep the memory usage minimal, I will have a look at handcent and compare it to the standard Eclair app. But as long as the base is 2.03 I'm guessing I'll keep it stock..
Still trying to deodex the ROM. damnit.. boot loop persists :<

Hi...
Thanks for your release and efforts..
Now I am using RODRIGUEZ STYLE v 2.3 and it works good...
But today I faced with a problem that the nexus start page repeated after restarting the phone and the phone did not log in, I tried many ways but that was not fixed, so I decide to choose another ROm, I am not sure which rom should I use, but yours looks good.
I have some questions, then I am going to start installing it..
MY PHONE DATA:
Baseband: 47.26.35.04U_7.05.35.26.L
Build number: 1.31.405.4
-----------------------------------
Can I use your rom without any problems???
My phone was rooted with r4 modaco.
But Can I Unroot it after installing your rom and get the FROYO UPDATE that HTC is gong to release..???
I dont want to brick my phone because of wrong Radio version,and I dont know how can I find that, which rom is suitable for my phone and which one is not.,would you please tell me that, is this rom suitbale for my phone and i am not going to brick it?..
And, Does this Rom contain Persian or Arabic characters support for reading SMS and Web Browsing..???
Is the bluetooth works smoothly with this rom..??
Thanks for your answer...

efex said:
When base 2.05 comes, and if that bug still persists - I will definetly change the app to something else. But I'm trying to keep the memory usage minimal, I will have a look at handcent and compare it to the standard Eclair app. But as long as the base is 2.03 I'm guessing I'll keep it stock..
Still trying to deodex the ROM. damnit.. boot loop persists :<
Click to expand...
Click to collapse
Did you remember to sign the apk's after the deodexing? That can be what is causing the bootloop... always sign all apk's when making a change..

mercury700ir said:
Can I use your rom without any problems???
My phone was rooted with r4 modaco.
But Can I Unroot it after installing your rom and get the FROYO UPDATE that HTC is gong to release..???
I dont want to brick my phone because of wrong Radio version,and I dont know how can I find that, which rom is suitable for my phone and which one is not.,would you please tell me that, is this rom suitbale for my phone and i am not going to brick it?..
And, Does this Rom contain Persian or Arabic characters support for reading SMS and Web Browsing..???
Is the bluetooth works smoothly with this rom..??
Thanks for your answer...
Click to expand...
Click to collapse
Yes, since your phone is rooted you can install this, and it will remain rooted. You can unroot the same way as with r4, eg. just install the RUU and it's done.
Persian/arabic did not work, neither menues or keyboard. I can look into that, see if I can find the solution for it.

whitetigerdk said:
Did you remember to sign the apk's after the deodexing? That can be what is causing the bootloop... always sign all apk's when making a change..
Click to expand...
Click to collapse
Oh, thats why then.. I signed the apk:s BEFORE deodexing.. wondered why it worked yesterday, but not today (guess I managed to change the order somehow.. shame on me!) Thank you!

efex said:
Yes, since your phone is rooted you can install this, and it will remain rooted. You can unroot the same way as with r4, eg. just install the RUU and it's done.
Persian/arabic did not work, neither menues or keyboard. I can look into that, see if I can find the solution for it.
Click to expand...
Click to collapse
thanks man...
I am really a fan of you....
Now I am downloading the rom..
My ROM ver is 1.31, if I upgrade it with your rom to 2.03, Can I install 1.31 RUU again?? or I should find a 2.03 RUU..??
And, I know that KYOSA add persian characters support to his ROM, maybe it can help you to do this for your next release...

mercury700ir said:
My ROM ver is 1.31, if I upgrade it with your rom to 2.03, Can I install 1.31 RUU again?? or I should find a 2.03 RUU..??
And, I know that KYOSA add persian characters support to his ROM, maybe it can help you to do this for your next release...
Click to expand...
Click to collapse
You can unroot with any stock RUU, 1.31 if you want, or 2.03 if you prefer that. The RUU updater wont care which version of a rooted ROM you have.
I'll see what I can find about the languages. Found a way for G1 that should work for Legend roms too, but I'll se if I can find anything else.

Okay, found this one update that should give arabic support to any ROM. I don't have a chance to test myself (I cant read arabic so I wouldn't know if it's right?). I did not make this file, I don't know who did, but I'm not taking any creds for it.
Download
Install the rom, then (without wiping), update with this. Please let us know if it works as it should.

Ok, this looks very nice. Ill try iy out.
oh btw, does this rom have app2SD ?

efex said:
Okay, found this one update that should give arabic support to any ROM. I don't have a chance to test myself (I cant read arabic so I wouldn't know if it's right?). I did not make this file, I don't know who did, but I'm not taking any creds for it.
Download
Install the rom, then (without wiping), update with this. Please let us know if it works as it should.
Click to expand...
Click to collapse
Ok, Thanks...
Tomorrow I'll try...
The internet connection bandwidth here is dead I think, the download speed is about 14 KB/Sec now..
I don't know why...
But tomorrow absolutely I'll give you the result.

nafnist said:
Ok, this looks very nice. Ill try iy out.
oh btw, does this rom have app2SD ?
Click to expand...
Click to collapse
No A2SD on this ROM (I dont have my class10 sd anymore, running on a class2 so cant use a2sd). I can make one with a2sd, but I can not test it myself..
EDIT: Added A2SD version in first post. Untested, feel free to try it and please report any problems!

arh kom så, viking! 200 dkr for 8gb class4!! hehe
This needs app2SD hehe
anyhow,
First boot was really fast, and noticed that after scrap'in all HTC on this ROM you forgot to replace the Screen-Lock !
Im personally fond of this vanilla one; http://forum.xda-developers.com/showthread.php?t=709183
needs a deodexed rom tho ;-(

i left the lockscreen on purpose, and the htc music player (they are connected). i should change both, just havent really checked in to it yet. Still lots and lots of htc-files in the system/app, needs cleaning, but I'm working on it.
About the deodex, Im running into problems there.. Deodex (+ sign apk's) = reboot loop. Can't seem to figure it out!
I liked that lockscreen btw. I'll probably change to it, remove htc world clock (replace with eclair clock) and change the music player.

whitetigerdk said:
Did you remember to sign the apk's after the deodexing? That can be what is causing the bootloop... always sign all apk's when making a change..
Click to expand...
Click to collapse
Short: Don't sign the apks, it's not necessary, even dangerous. And it breaks your precious ROMs.
Long explanation:
If you compile the sources yourself, the scripts will at a certain point create your private and public platform keys, store them in /etc and also sign all apks with it. So this wouldn't be a problem if you could compile Sense.
If you blindly re-sign every package you run into a problem: You use a key that differs from the one in the key-storage (the one HTC uses to build and sign). And there's nothing you can do about that.
Eventually you will face the biggest troubles with four packages.
Vending:
Resign it and no paid apps will available at all (which is obviously caused by replacing Google's signature with yours).
GoogleCheckin, GoogleSubscribedFeedsProvider and NetworkLocation (and some non proprietary ones I don't remember):
Now these are even trickier as they require access to features that the platform strictly locks away from apps.
No app, downloaded or pre-installed is granted these rights except for when it was signed with the platform key. This was done to protect the users.
Resign these and you will see "Package xyz has no signatures that match those in shared user android.uid.system; ignoring!" in your log-files.
That being said there are lot's of reasons why odexing could fail. I've had a few unsuccessful attempts of using dexopt-wrapper on my device without any obvious reasons - I know for sure that bootclasspath and everything else was correct.
But, there's a nice little trick to make it work: Don't do it (yourself)!
Instead you can grab the files from /cache/dalvik-cache, they are exactly the same.

CFH [Wildfire] v1.0 - Newb rom

Hi
I had the day off, and decided to have a play with the Kitchen to see what I could come up with. After following the instructions on theunlockr.com I decided to base my rom on the OpenFire v.2.3 rom. Any issues that rom had, mine will have.
I have added a few things and changed a couple of things, but in the end, this is my first rom for a device I do not have myself. I have an HTC Desire, but noticed that the Wildfire isn't getting as much love, hence that choice. I hope to get a better understanding of what it takes to make a proper custom rom at some time in the future.
Removed:
Launcher2
Added:
Launcher Pro
Titanium Backup
Rom Manager
Fancy Widget
From the OpenFire v.2.3 post:
NO HTC APPS DO NOT WORK ON THIS ROM AND I WONT TRY TO PORT THEM (but if you try and suceed please tell me and I will maybe include them!)
This ROM is from the android source there is no HTC apps or extra apps from the start it do come with spareparts and dev tools from android source. At the moment it seems a bit slow I think that is due to animations, animations can be turned of in spareparts or in the settings menu.
Features:
- Froyo aosp 2.2.1
- Root + superuser app
- Busybox
- No htc apps!
- Some google apps
- Multi language
- Darktremor Apps2SD
- Patched market
- Usb & WIFI-thetering
- JIT
- 3 in 1 reboot menu
- It may make your phone explode! (You have been warned)
Bugs / Not working:
- Video recording working (but, bad quality)
- Cant import contacts from SIM ? no read/write acess to SIM ? (can anyone confirm or deny this?)
TODO:
- Get rid of above bugs
- HTC-camera (maybe)
Thanks to:
HCDR.Jacob - for the kernel and vendor
Yopsi - for sharing package with google apps.
danne_jo - for APN stuff, and for hosting to my ROM
Sympnotic - For his patched market app
AnantK123 - For pointing out a fix for the camera app
acavella - For hosting / making a homepage dedicated just for OpenFire
Notes:
NO HTC APPS DO NOT WORK ON THIS ROM AND I WONT TRY TO PORT THEM (but if you try and suceed please tell me and I will maybe include them!)
To get app2sd to work you need an ext partition when you have that you might have todo a full wipe and reflash the ROM to get app2sd to work
When you boot up first time choose "com.android.provision"
Anything you want to know about OpenFire can be found at the OpenFire website.
CFH [Wildfire] v1.0 Fault Log
Download:
CFH [Wildfire] v1.0.zip (58 MB)
Due to posting restrictions, I am unable to post links to the Rom. I will post it as soon as possible.
In the mean time, please leave comments below.
Thanks
Chronicfathead

Reserved for future use
Reserved for future use

What did you change? We don't need roms like those. Everyone can customize his installed rom like he wants.
Why don't you stick to a phone you have and help projects that just need help instead of reinventing the wheel over and over again?
no offense, just my personal oppinion

bl1nkk said:
What did you change? We don't need roms like those. Everyone can customize his installed rom like he wants.
Why don't you stick to a phone you have and help projects that just need help instead of reinventing the wheel over and over again?
no offense, just my personal oppinion
Click to expand...
Click to collapse
None taken.
I've had my desire for a while, and decided to root it about a month ago. I have now installed a custom rom, and I'm enjoying the fiddling around. I don't have too much knowledge, apart from experiences gained in the last week or so.
I tried talking a colleague into installing a custom rom, but he said there weren't too many for the Wildfire, so I said I'd have a play. I'm treating it as a learning curve, as I've always been interested in programming, but never really had the time. I have created a (very) small program for the Mac, and have written a few batch files but thats as far as I've taken it.
In an afternoon I've set up a Linux VM, installed all the needed software and had a play to see what I can realistically do. I see this as a first step. I'm trying to talk the wife into a Wildfire so I can have one to play with!
If the consensus is I should delete the thread, then so be it.
Chronicfathead.

[DEV/help is needed][ROM] GB Sense 2.3.3 [v1.2.1 in the second post]

SebastianFM has kindly agreed to provide support to fix issues.
That i think is a fantastic news
so please show your appreciation by thanking for the SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1 ROM
Click to expand...
Click to collapse
I REQUEST/ENCOURAGE ANY DEV OUT THERE WHO WOULD LIKE TO TAKE OVER
OR START A FRESH TO BUILD GB-SENSE ROM PLEASE DO SO,
THIS THREAD IS MAINLY FOR INFORMATION PURPOSE
Click to expand...
Click to collapse
warning/disclaimer:
I am not maintaining this ROM, i have only transported this from SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1
initial attempt was on SenseonFire ROM from wildfire
please don't bother this thread with trivial questions
this ROM is only for testing purpose and inspiration for further development only
I started this, with intention of porting the ROM, only to realize that I am not smart enough to fix most things.
I am not claiming to be dev as i am not, so posting the info for you to proceed or dump the project.
WIP <- working in pause (not work in progress)
I thank
SebastianFM for the first porting, which made possible most of the other device ROMs SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1
all those involved in SenseonFire ROM project on wildfire especially VigiDroid,
and Arco for building an awesome kernel and nFinityGB v1.13 ROM for tattoo and some of the files were taken from this ROM
and dsixda's Android Kitchen
Click to expand...
Click to collapse
The main reason I have opened this thread is, to make you aware of the promising future out there for sense lovers using tattoo
and sow some seeds of inspiration for a dev out there who could fix this for us.
What i did
I took the SFM 3.0.2 Magic|Android 2.3.3|Sense 2.1 ROM used dsixda's Android Kitchen utility to transport and then adjusted few libs and binaries to get the phone started
Used Arco's 2.6.35.14 kernel and files from his nFinityGB v1.13 ROM
and added Robot font from following thread http://forum.xda-developers.com/showthread.php?t=1316156
i moved system/app folder to cache/systemapp and symlinked to system due to less space in system partition
Click to expand...
Click to collapse
things like gps, fm and camera are not working on tattoo, many apps need resizing or font size needs reducing.
when i did benchmarking using cf-bench apk, the score i got was more than 500 close twice to what i got with tatfroyosense. Benchmark done at 633 Mhz max cpu

rom link and snapshots
Download links
SFM port version 1.2.1
mediafire
4shared
Changelog
V1.2.1
Pooled all patches together and few minor changes
V1.2
Few apks resized
ROM is by default Overclocked
framework symlinked from cache partition
wipe cache, data before flashing the ROM
First boot takes about 5-10 mins
Main issues:
GPS
Camera
FM
Media player sound OK - video is white
no notification lights (but button lights OK)
Battery drain - if wifi on
and other issues from user (??)
old versions
SFMportv1.2
http://www.mediafire.com/?uzutj2tura75oyr
SFMportv1.1
http://www.megaupload.com/?d=KXLUD91K
SenseonFire port link
http://www.megaupload.com/?d=UYZ4V0WJ
the rom has edify scripting and is unsigned, could be installed with clockworkmod recovery
Click to expand...
Click to collapse

This is cool. I never expected Tattoo to run anything heavy like this.
Feeling proud of you, man! With tears in my eyes.
Sent from my HTC HD2 with my fast fingers.

Waiting for news!!

Umm well, regarding eth0 and tiwlan0, they are just hardware access points for the required device. The Unix/Linux system often puts all devices as files in /dev/. So when it needs to call a particular device, it calls that file and output to that device is piped back into the file.
So eth0 refers to the Ethernet (Wired LAN) interface, while tiwlan0 is the WiFi (Wireless LAN). The problem with older kernels (ralle.gade) is that they list WiFi as standard wired LAN device. Newer kernels list them properly (Arco's kernel). So its just a matter of changing /dev/eth0 to /dev/tiwlan0 in the wpa_supplicant and other wifi config files and wifi will run as needed. i am saying this as far as what i know about configuring desktop linux.
and about camera and videorecorder, u can get the drivers from CM7 and merge with this. For FM, u could get get drivers from CM7 and replace the HTC FM app with the one from CodeAurora or MIUI.
I am interested to help. But it seems I have got some other priorities to attend to. I will be free after April 2012. Then I will brush up my C++ skills and see if I can help u all.

...
too bad,this rom would be perfect if bt, gps, wifi, camera would working on tattoo...

sunitknandi said:
Umm well, regarding eth0 and tiwlan0, they are just hardware access points for the required device. The Unix/Linux system often puts all devices as files in /dev/. So when it needs to call a particular device, it calls that file and output to that device is piped back into the file.
So eth0 refers to the Ethernet (Wired LAN) interface, while tiwlan0 is the WiFi (Wireless LAN). The problem with older kernels (ralle.gade) is that they list WiFi as standard wired LAN device. Newer kernels list them properly (Arco's kernel). So its just a matter of changing /dev/eth0 to /dev/tiwlan0 in the wpa_supplicant and other wifi config files and wifi will run as needed. i am saying this as far as what i know about configuring desktop linux.
Click to expand...
Click to collapse
I dont think this is issues with old and new kernel, they all had access points as tiwlan0 (fyodor, ralle.gade and arco).
So far to my understanding it is device specific (see below).
Dexter seems to have tweaked the module and wpa_supplicant from ralle.gade's kernel to work with Froyo, i dont know what was changed. to get wifi working
EDIT: eth0 limitation is with hardware used in the device
Devices like: Wildfire, Wildfire S, Icon-G and Explorer -have their the access point setup as eth0 and they all have broadcom chip
while Tattoo, Magic and Hero -have tiwlan0 as the access point and they all seem to TI chip

in that case, lets ask dexter. he can help.

sunitknandi said:
in that case, lets ask dexter. he can help.
Click to expand...
Click to collapse
I asked him, he still hasn't responded...
P.S.
i get this from the logcat: " wifi_load_driver end error 2" and from dmesg i get something like: "firmware_path unknown value"
I researched and foundout that the deire had similar problems, but they had a previously working dirver and just couldn't conect....
So that leaves me nowhere again... (sadface)

Few things that i have't mentioned earlier:
Following are the commands in wpa_supplicant script for tatfroyosense
Code:
/system/bin/insmod /system/lib/modules/wlan.ko
/system/bin/wlan_loader -f /system/etc/wifi/Fw1251r1c.bin -e /proc/calibration -i /system/etc/wifi/tiwlan.ini
/system/bin/wpa_supplicant.bin -Deth0 -ieth0 -c/data/misc/wifi/wpa_supplicant.conf
As it is tiwlan0 interface in Arco's kernel, i have copied wlan_loader, wlan_cu, wpa_supplicant, wpa_cli binaries from nFinityGB rom along with /system/etc/dhcpcd folder and the wifi module. (These are already in the ROM attached)
As some of you might have noticed:
module wont load at boot
so i have tried to execute following commands from shell (they are in the init.rc script except insmod of module)
Code:
/system/bin/insmod /system/lib/modules/wlan.ko
/system/bin/wlan_loader -f /system/etc/firmware/Fw1251r1c.bin -e /proc/calibration -i /system/etc/wifi/tiwlan.ini
/system/bin/wpa_supplicant -Dwext -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf
module loads fine but then wlan_loader give following error
Code:
rtnl_open: Protocol not supported

Hello mate. Is it possible to provide a github repository with the code?

ntenisOT1948 said:
Hello mate. Is it possible to provide a github repository with the code?
Click to expand...
Click to collapse
I dont think HTC source code out there for sense andriod phones.
The time line for this ROM is as follows:
HTC Salsa was ported to Sapphire
http://forum.xda-developers.com/showthread.php?t=1025330
From Sapphire to wildfire
http://forum.xda-developers.com/showthread.php?t=1067868#13557996
wildfire then updated to this
http://forum.xda-developers.com/showthread.php?t=1269485
From above ROM to this ROM
Following files were taken from nFinityGB v1.13 ROM to this ROM
Code:
Filename Folder
wlan_loader system\bin
wpa_cli system\bin
wpa_supplicant system\bin
vold.fstab system\etc
dhcpcd.conf system\etc\dhcpcd
brf6300.bin system\etc\firmware
brf6350.bin system\etc\firmware
Fw1251r1c.bin system\etc\firmware
tiwlan.ini system\etc\wifi
wpa_supplicant.conf system\etc\wifi
Clockopia.ttf system\fonts
DroidSans-Bold.ttf system\fonts
DroidSans.ttf system\fonts
libwpa_client.so system\lib
copybit.bahamas.so system\lib\hw
gps.bahamas.so system\lib\hw
gps.goldfish.so system\lib\hw
gralloc.bahamas.so system\lib\hw
gralloc.default.so system\lib\hw
lights.bahamas.so system\lib\hw
sensors.bahamas.so system\lib\hw
sensors.goldfish.so system\lib\hw
wlan.ko system\lib\modules
bahamas-keypad.kcm.bin system\usr\keychars
bahamas-keypad.kl system\usr\keylayout
AVRCP.kl system\usr\keylayout
vim system\usr\share
colors system\usr\share\vim
filetype.vim system\usr\share\vim
ftoff.vim system\usr\share\vim
indent.vim system\usr\share\vim
indoff.vim system\usr\share\vim
scripts.vim system\usr\share\vim
blue.vim system\usr\share\vim\colors
darkblue.vim system\usr\share\vim\colors
default.vim system\usr\share\vim\colors
delek.vim system\usr\share\vim\colors
desert.vim system\usr\share\vim\colors
elflord.vim system\usr\share\vim\colors
evening.vim system\usr\share\vim\colors
koehler.vim system\usr\share\vim\colors
morning.vim system\usr\share\vim\colors
murphy.vim system\usr\share\vim\colors
pablo.vim system\usr\share\vim\colors
peachpuff.vim system\usr\share\vim\colors
ron.vim system\usr\share\vim\colors
shine.vim system\usr\share\vim\colors
slate.vim system\usr\share\vim\colors
torte.vim system\usr\share\vim\colors
zellner.vim system\usr\share\vim\colors
VoiceDialer.g2g system\usr\srec\config\en.us\grammars
wlan_cu system\xbin

Great news guys
I got wifi and bluetooth working
As i mentioned the history of the ROM in previous post,
It occured to me, may be i can start fresh from Sapphire ROM
So i went to the follwoing post and started with SFM 3.0.2
http://forum.xda-developers.com/showthread.php?t=1025330
and with rough porting i could get wifi and bluetooth working and i bet gps would also work.
you know it was quick and dirty port (huge size and bad layout),
now we can do proper port with relayout and resizing the framework and would be better ROM

Cool... Keep up the hard work. Once u finish the port, we can get someone to optimise it.

Have you updated the download link? Iwould like to have a look to graphics to know if I can do anything about them.
Edit: I can see you don't. But I'm going to start trying to resize some graphics as a practice for future.

2nd post updated with new rom port
some of the applications are not working and poor layout.
Alternative launcher like adw working fine

I't seems there's many other people waiting for news: http://bbs.hiapk.com/thread-2741601-1-1.html
I don't know if it's chinese, or what!
Enviado desde mi HTC Tattoo usando Tapatalk

sense zero on tattoo
Now that i could port (transport) GB sense, i wanted to have a crack at sense zero (it was to decide which one would be best carry on)
so I did try port Hintay Zero 0.14 (Sense 3.5 Android 2.3.5)
and i could get it booted on Tattoo,
but have to set lcd density to 100, so that you can see launcher work.
But most of other things look decent if it is set to 120.
And you can see that layout and size are bad.
but i have to say it takes lot of memory and gets very slow.
framework moved to cache to make space in system.
takes 10 mins on first boot
here the link
http://www.megaupload.com/?d=X1B721BZ
and snapshots

GbermuG said:
I't seems there's many other people waiting for news: http://bbs.hiapk.com/thread-2741601-1-1.html
I don't know if it's chinese, or what!
Enviado desde mi HTC Tattoo usando Tapatalk
Click to expand...
Click to collapse
Yes, its a chinese forum. Gave a try using BabelFish and Google Translate, but it is very messy.
Text like HTC Tattoo intelligent handset gets HTC Sence 3.0 on Peace Outstanding 2.3. (read as smartphone gets htc sense on android version 2.3)
F**k translators. I preferred to read no more.

sunitknandi said:
Yes, its a chinese forum. Gave a try using BabelFish and Google Translate, but it is very messy.
Text like HTC Tattoo intelligent handset gets HTC Sence 3.0 on Peace Outstanding 2.3. (read as smartphone gets htc sense on android version 2.3)
F**k translators. I preferred to read no more.
Click to expand...
Click to collapse
That's what I can understand using translators: they've tried it, and like it. They thik is smooth and powerfull, but ram memory is low. Someone is asking about Sense 3.0, but the tread is not updated, so they only tried SenseonFire (first port). Simply (as I said), they're waiting.

[Q] [WIP] ICS on IncS

I've been trying to port over ICS from DHD but no success(ROM doesn't boot, stuck at HTC splash screen)
Since I'm a noob to ROM porting any help would be appreciated.
I followed a simple guide which told me to replace certain files in the boot.img and system folder along with a couple of files more.
I used the ICS rom of DHD and MIUI ICS rom for IncS.

cooljais said:
I've been trying to port over ICS from DHD but no success(ROM doesn't boot, stuck at HTC splash screen)
Since I'm a noob to ROM porting any help would be appreciated.
I followed a simple guide which told me to replace certain files in the boot.img and system folder along with a couple of files more.
I used the ICS rom of DHD and MIUI ICS rom for IncS.
Click to expand...
Click to collapse
a suggestion for you...try the cm7 rom instead of miui ics build.
thanks for your effort. i will also dig about it but after my last exam. i request everyone who could contribute....its for our phone.
keep trying bro.

If it is simple enough I could give it a try, any moderate to advanced programming I wouldnt have a clue

I have been working on this over the last couple of days and so far my port has touchscreen, audio, RIL, wifi, 2D HW acceleration, notification LED and proxy sensor working (pretty much the same as the DHD port I think). Last I tried the microphone wasn't working for calls but it should be fixed in my new build.
I will post it up in the next couple of days once it's ready to be used. I've been busy with other things so haven't had a chance, plus I don't have access to the developer section yet.

st.matt said:
I have been working on this over the last couple of days and so far my port has touchscreen, audio, RIL, wifi, 2D HW acceleration, notification LED and proxy sensor working (pretty much the same as the DHD port I think). Last I tried the microphone wasn't working for calls but it should be fixed in my new build.
I will post it up in the next couple of days once it's ready to be used. I've been busy with other things so haven't had a chance, plus I don't have access to the developer section yet.
Click to expand...
Click to collapse
good job. if you need any help just let us know. i will try to look into it today night positively.

Anyone got any guides/tutorials kinda stuff for this?

Nopes, no tuts as such... just small guides....

Any links??
Keen to see how much of your port is working so far as well
EDIT: just tried it myself using a guide in other thread. used the DHD beta 3 and vivo latest CM7 nightly and is stuck at htc splashscreen
EDIT2: didnt sign the rom before, lets try that again...
EDIT3: still stuck on splashscreen

I will post my port up later tonight. I had a chance to do a bit of work on it and it's pretty good right now but the market is broken for some reason.
Once I get that working (and hopefully bluetooth as that shouldn't be hard) then I will upload it.

st.matt said:
I will post my port up later tonight. I had a chance to do a bit of work on it and it's pretty good right now but the market is broken for some reason.
Once I get that working (and hopefully bluetooth as that shouldn't be hard) then I will upload it.
Click to expand...
Click to collapse
Sounds good, what ROMs did you use to port it?

st.matt said:
I will post my port up later tonight. I had a chance to do a bit of work on it and it's pretty good right now but the market is broken for some reason.
Once I get that working (and hopefully bluetooth as that shouldn't be hard) then I will upload it.
Click to expand...
Click to collapse
Looks like a nice birthday gift... ;D

Unfortunately I wasn't able to get market working.. but anyway here is the first Alpha.
It is based on a combination of the Desire HD build and using the kernel by TwistedUmbrella. I have a device setup to work with TwistedUmbrella's ICS tree but I don't know if it will 100% build successfully at this stage (takes forever to build on my 5 year old computer..). All credits go to the DHD guys as they have done basically everything, I've just made it work (or at least, most of it) on the vivo.
Working:
- Hardware 2D/3D Hacks
- Touchscreen
- Bluetooth
- Wifi (not tethering)
- RIL
- Data
- Sound
- Sensors
- Rotation
- Status LED
Not Working:
- Hardware video acceleration
- Tethering
- UMS (use adb instead)
- USB tethering
- Camera
- Google account (so Gmail, Market all not working)
The account error seems to be something to do with xt_qtaguid.. here is the log info:
Code:
I/qtaguid ( 3029): Failed write_ctrl(u -1) res=-1 errno=9
I/qtaguid ( 3029): Untagging socket -1 failed errno=-9
I/GLSUser ( 3029): GLS error: NetworkError
Might be a problem with the kernel, but I'm not really sure. Any help would be nice, I've spent about 5 hours on this and gotten nowhere.
Link: http://www.multiupload.com/Z4JKSC1JK2
Please don't post bugs reports just yet. This is the first alpha, it's not really a daily driver and I know that there are bugs. Post fixes instead.

Sounds awesome Matt! what are you using to break down and build the rom??
Will give it a go in the morning and post any other feedback

Nice work you got slot further than I did! I will see if I can contribute anything to your build once I have it installed.
The Desire S version is pretty good, and the hardware is almost identical to the Inc S, maybe that would make for a better base?
Sent from my HTC Incredible S using xda premium

l0st.prophet said:
Nice work you got slot further than I did! I will see if I can contribute anything to your build once I have it installed.
The Desire S version is pretty good, and the hardware is almost identical to the Inc S, maybe that would make for a better base?
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
That's probably not a bad idea. I will see if I have time tonight to try and see if I can get market working by using some of the desire s stuff.. or maybe someone else could try as well.
For anyone that gives it a go, just keep in mind that the button backlight levels are in framework-res.apk, and will need to be recompiled from source or decompiled and edited to get the levels right.
P1n3apqlExpr3ss said:
Sounds awesome Matt! what are you using to break down and build the rom??
Will give it a go in the morning and post any other feedback
Click to expand...
Click to collapse
Well so I have checked out TwistedUmbrella's ICS tree and 7x30 kernel, and have made a vivo config for both. I've then used the prebuilt DHD ICS rom and taken out the DHD stuff and put in stuff from the vivo Miui.us rom. Then I've just gone through and fixed the boot ramdisk, built the kernel and put it together for the boot image.
In future I will try building from source, but as I said it takes a very long time for me.

st.matt said:
Well so I have checked out TwistedUmbrella's ICS tree and 7x30 kernel, and have made a vivo config for both. I've then used the prebuilt DHD ICS rom and taken out the DHD stuff and put in stuff from the vivo Miui.us rom. Then I've just gone through and fixed the boot ramdisk, built the kernel and put it together for the boot image.
In future I will try building from source, but as I said it takes a very long time for me.
Click to expand...
Click to collapse
This sounds WAY over my head, all I tried was unzipping CM nightly 146 and the DHD build and changing files, rezipping and signing it. No wonder I got stuck at the HTC splashscreen...
Keep up the good work

st.matt said:
Unfortunately I wasn't able to get market working.. but anyway here is the first Alpha.
It is based on a combination of the Desire HD build and using the kernel by TwistedUmbrella. I have a device setup to work with TwistedUmbrella's ICS tree but I don't know if it will 100% build successfully at this stage (takes forever to build on my 5 year old computer..). All credits go to the DHD guys as they have done basically everything, I've just made it work (or at least, most of it) on the vivo.
Working:
- Hardware 2D/3D Hacks
- Touchscreen
- Bluetooth
- Wifi (not tethering)
- RIL
- Data
- Sound
- Sensors
- Rotation
- Status LED
Not Working:
- Hardware video acceleration
- Tethering
- UMS (use adb instead)
- USB tethering
- Camera
- Google account (so Gmail, Market all not working)
The account error seems to be something to do with xt_qtaguid.. here is the log info:
Code:
I/qtaguid ( 3029): Failed write_ctrl(u -1) res=-1 errno=9
I/qtaguid ( 3029): Untagging socket -1 failed errno=-9
I/GLSUser ( 3029): GLS error: NetworkError
Might be a problem with the kernel, but I'm not really sure. Any help would be nice, I've spent about 5 hours on this and gotten nowhere.
Link: http://dl.dropbox.com/u/52030869/vivo_ics.zip
Please don't post bugs reports just yet. This is the first alpha, it's not really a daily driver and I know that there are bugs. Post fixes instead.
Click to expand...
Click to collapse
great job bro! just need the camera and gmail account. rest everything is perfect ! i will try it today and see. thanks for your efforts

Download link not working... Too much traffic :/
Sent from my Incredible S using XDA App

Splux said:
Download link not working... Too much traffic :/
Sent from my Incredible S using XDA App
Click to expand...
Click to collapse
yes its not working. can we get other links please?

Yeah sorry I didn't realise dropbox imposed download limits. Here is another download link: http://www.multiupload.com/Z4JKSC1JK2
I think I may have fixed Google accounts though, so there might be another download in another 30 minutes or so.