yashsingh1/xdaforums huggingface dataset:
[Click Android Development] rallapag:
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
[Click Android Development] sunitknandi:
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 Android Development] KingCreole:
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.
[Click Android Development] KingCreole:
KrisInfinity

At [RUU][DEVS ONLY][For Porting] HTC Pico [Sense 3.5][Android 2.3.5][Sense Zero] , you said: "I'm interested on working on this but I have never worked on a rom before. I just have experience in java/c++ and some android app programming. Can anybody point me to the right direction? I think i can devote much time to this project."

Have you tried it? As another option.

Edit: I've tried to install the kitchen, but this is my sister's pc, and doesn't have free HD enough.
[Click Android Development] rallapag:
Sorry it wasn't clear, you mean has he (KrisInfinity) tried porting

sense zero.
[Click Android Development] KingCreole:
Sorry, but I thought it was you who said that. It's my fault. Sorry again.

Enviado desde mi HTC Tattoo usando Tapatalk
[Click Android Development] rallapag:
but, i did try porting it

check following post from previous page

http://xdaforums.com/showpost.php?p=19673472&postcount=18
[Click Android Development] KingCreole:
I thought i't was a different rom. Thanx.:D

Enviado desde mi HTC Tattoo usando Tapatalk
[Click Android Development] (IwaN):
So will you continue on developing Sense Zero or you will return to Android 2.3.3 with Sense 3.0? I am bored of this 1.6 and I want something new but I want Sense ROM which is fast and stable. I'm counting to you!
[Click Android Development] rallapag:
Please don't count on me.

I am not a dev and i haven't got much progress lately

At the moment i am only working on 2.3.3 (not sense zero) as it seems decent.

But they do need some tweaking to improve performance

I am just hoping for a dev out there with tattoo, do the improvements for us

So far i have resized following apks (some elements are looking fine now)

com.htc.resources.apk

framework-res.apk

HtcDialer.apk

HtcSoundRecorder.apk

PCSCII.apk

Phone.apk

Settings.apk

SystemUI.apk

WorldClock.apk

HTCSetupWizard.apk

and is adjusted to look while shutting down

htc_downanimation.zip

Rosie.apk should be resized to get a good launcher experience, will work when i have time.
[Click Android Development] rallapag:
This looks good

I have resized rosie and clock widget.

here is how it looks

will update the second post with the all the resized (so far) apks, possibly tomorrow
[Click Android Development] rallapag:
I have a bug to solve in this ROM (even though still use for test)

Phone signal dies as soon as the screen is locked.

Phone calls get disconnected as soon as screen is locked.

any one knows, how to stop it??
[Click Android Development] KingCreole:
It sounds as locking is going to plane mode---:(
[Click Android Development] rallapag:
sorry, i meant it's killed and restarted

you can receive calls, when phone is locked and screen is off.

it appears to have associated with screen on/off state.
[Click Android Development] rallapag:
updated ROM in the second post

for the phone signal die problem: it is caused by screen off/on condition

( i tested it using apps to prevent locking and display turn off)

so for the moment i am using KeepScreen app and selected phone to be watched.

This app prevents the screen turning off, while the selected app is in use.

it's now fixed with help from SebastianFM
[Click Android Development] rallapag:
2nd post attached with the phone signal patch,

please flash it from recovery to get the phone signal issue fixed

EDIT: There was a mistake in the attached patch updater script, so new patch attached
[Click Android Development] luxb:
Well...

Mobile network works and so does Wifi.

Camera still doesn't work tho :(

How can I help?
[Click Android Development] rallapag:
Camera is not fixed yet.

Please check known issues in the second post

and report if you find more bugs.
[Click Android Development] KingCreole:
Really good news on first post. Thanks, SebastianFM.
[Click Android Development] luxb:
Cyanogen 7 publicly posted their libcamera (cam drivers). I think you can use that.

https://github.com/CyanogenMod/android_device_htc_click
[Click Android Development] alcatel444:
Please Fix Camera

Hello ,

Please fix camera and i am in . thanks alot
[Click Android Development] rallapag:
Sorry guys I am not a dev,

that means things would take time to get fixed

At the moment I am trying to understand, how I can take CM7 drivers and use in this ROM.

If any one knows, please do this for us or direct me to such resources.

Being a holiday time, I can't expect devs to answer my queries, so please be patient.

Mean while, I have fixed the Music and weather apk and widget layouts, so will update a patch later tonight.

EDIT: 2nd post updated with the music-weather-patch.zip

let me know if you have problem with it
[Click Android Development] KingCreole:
Well, I've installed it, and works ok.

I've tried to use "Spirit Fm" app, and I think it's very near to work (but I could'nt ear anything, of course).

Wheather and music are working ok.

When I tried to link contacts from google with the ones from facebook or twitter, it FC.

FriendStream's widget needs to be resized, but works ok when you install facebook for android app.

Edit 1: Maybe it's possible to make it work with ext partition in the future.

Edit 2: When I tried to change the wallpaper on HTCWallpapers, I got a FC.

Keep on this good work. :D
[Click Android Development] MaffyRain:
100 lcd density .

Why not set 100 dpi in build.prop ? On 100 dpi rosie.apk works great . Wallpaper,animated screens HTC applications. Only HTC IME need to be resized. Because now was ported to 120dpi. All htc widget (like sms widget or contacts) work good and also All apps works good so...why not 100 dpi? ;) the gps, bluetooth , camera bug still alive. So please set to 100 and the ROM will work better than now (gps bluetooth camera excluded).with this change you do not have to resize all the apps and widgets (not to mention that downloading other would not work if you do not shrink IF you use 120 lcd density if you use 100 no matters all apps works). this upgrade solve 90% of the porting problems related to graphics. after the release at 100 dpi (perhaps even deploying patches in update.zip we can focus on bug fix like camera, GPS and bluetooth.
[Click Android Development] rallapag:
Yes i did saw that changing to 100dpi, few graphics issues are fixed and few widgets and calculator as well show up.

But then you have quite few messed up layouts, for the moment it is not the best option ( at least i think), i have to change layouts again.

instead i am trying to see if we can change apk code to ignore system dpi. (some thing that was done for patching market a while back).

but thanks for the feedback.

I did not face any download issues with 120dpi. any how if people want to try this out use apps like LCD Resoultion or LCDDensity from market to change it to 100

_____________________________

by the way "Happy New Year" to all
[Click Android Development] MaffyRain:
ok, if you need help ask as well.for problems i meaning that the new app dowloaded from marketplaceHTC not work at 120 dpi. however, the system loads at first start, the app with the correct dpi, or not? ROMs with sense are more difficult to change...I hope to see this rom running at 100% soon.

if you need help ask..i'll try to be helpfull.

excuse my awful english
[Click Android Development] rallapag:
Yes we need help.

So please if you can pitch in some support that will be good

EDIT: it appeared you were not happy with my reply, but then i thought may be it was just how i read it
[Click Android Development] MaffyRain:
don't worry, your answer has nothing wrong :D you have all my support as I can. I have followed this thread from the first page. so I'm really happy with everything you're doing and I hope to help you ;) . if you need me to do something specific, send me a private message so we do not deal with too many posts.
[Click Android Development] MaffyRain:
Rallapag what method do you use to resize apps & widgets ? So i will use the same and not other ways. P.s. have you seen bug errors in logcat? In the next release i think you could add terminal (i ve not find it installed in this release). It's useful
[Click Android Development] rallapag:
my phone is down at the moment

I am using apktool to modify apks:

This is how i do mostly:

I am using wildpuzzled froyo apks as a reference; they have almost same widgets and appearance as sense 2.1 apps

(on a different note, you could replace framework and apps folder of project sense ROM to get them working for tattoo)

decompile both apks (using respective frameworks for respective apps)

changed ldpi folder names to mdpi under resources of froyo apk

Use any diff tool (i use winmerge on windows) compare xml files in both resources folder

Then change all dimens.xml file values to those as in froyo

recompile and check if the layout is better

If not, it's a bit repeating job,

go through each xml file which are different between two and try to change them accordingly (you will get the idea which one to choose from the name of the file)

and check how the layout looks

PS: As you can see from the title my phone is in coma at the moment,

so i have to wait and see if it can survive otherwise i wont be able to play anymore on android.

I am just hoping that it will pull through
[Click Android Development] MaffyRain:
thank you;) at the moment I can not help, because they are swamped with other activities so my work with the Rom goes slow, I'm focusing on 'HTC IME to run animated wallpapers and improve layouts, rosie continues to crash with 120 dpi :S , I'll let you know if I can make them work better.
[Click Android Development] chimnmay_chelios:
WOW...i am very late here...but this is something really amazing...cant wait to test it ;) great work devs :)
[Click Android Development] rallapag:
update the second post with working ROM download link
[Click Android Development] rallapag:
Testing libs for camera and gps

Hi

Can some one would mind testing following libstest.zip

I just want to know if it makes camera and gps work.

Flash from recovery and post logcat once you boot after flashing.

If device fails to boot, please flash attached libsoriginal.zip

Let me know
[Click Android Development] KingCreole:
How can I get the logcat? I got time enough to do it tomorrow morning.

Espero que la borrachera me haya permitido enviarlo desde mi HTC Tattoo con Tapatalk.
[Click Android Development] rallapag:
Sorry I wrote too quickly.

If your phone is booting fine and you get camera working that is good.

If booting failed then please post logcat.

if you have adb setup once phone boots type

adb logcat > logcat.txt

Press ctrl+C to stop writing log

Thanks KingCreole
[Click Android Development] KingCreole:
Ok, I'll tell you tomorrow. Sorry for my english.

Espero que la borrachera me haya permitido enviarlo desde mi HTC Tattoo con Tapatalk.
[Click Android Development] rallapag:
so far 44 test libs download and 18 original lib download,

so i assume it's not working, can any body confirm this??
[Click Android Development] KingCreole:
Well, it's done. Libtest is not working.

I've got a problem with my pc. I can't install usb drivers, so I can't get the logcat.

I'm gonna try in other way to make it work.

Another thing I've noticed: when you flash libtest.zip and, after it, you flash liboriginal.zip, usb is not working.
[Click Android Development] rallapag:
Did it struck at the HTC boot logo or has it stopped at boot animation??

Regarding usb, you cant charge or mount or it is not detecting the SD card??

sorry mate, with out a tattoo at hand, i am useless in dealing with such issues.
[Click Android Development] KingCreole:
It stuck at Tattoo logo (I wait about 5 min.). And about USB, it was charging but, in fact, you don't have to matter about it, cause it's a problem on my PC, not in the rom or the phone (my Pc doesn't still recognize it, even I've changed the rom to previous CM7).
[Click Android Development] MaffyRain:
hi i'm back online ..i'll check it and help to dev it . now i've lots of time. someone can post the logcat plz ?or i 'll flash the lib and do it. rallapag if you have the log can you send it to me with PM?
[Click Android Development] KingCreole:
Rallapag's phone is out of service, and I couldn't send the logcat cause my pc doesn't recognize my phone.
[Click Android Development] MaffyRain:
ok...so i'll reinstall linux on my new PC and post the logcat:p
[Click Android Development] rallapag:
Regarding libs

My logic behind the previous libtest zip

Following libs were different from Salsa to SFM ROM (SFM was ported from Salsa ROM)

and i have added few more libs from Work on buzz SFM port.

libaudio.so
libaudioflinger.so
libbluedroid.so
libbluetooth.so
libbluetoothd.so
libdvm.so
libhardware_legacy.so
libhtc_acoustic.so
libjpeg.so
libm.so
libnativehelper.so
libOmxH264Dec.so
libOmxMpeg4Dec.so
libOmxVidEnc.so
libskia.so
libstagefrighthw.so
libttssynthproxy.so
libwpa_client.so

And SebastianFM, has added libSFM_runtime.so lib

I tried to contact him couple of times about this, but so far I haven't got reply about where got these libs from and what is libSFM_runtime.so function

but Dexter_nlb has provided some insights, thanks very much to him, here is my communication with him (start to read from bottom)

With all the info above, here are some test one could do

Since we have bt file transfers and wifi working, i think we could only replace following libs with the ones from nFinityGB v1.13

libdvm.so

libhardware_legacy.so

libgps.so

libjpeg.so

libm.so

libnativehelper.so

libOmxH264Dec.so

libOmxMpeg4Dec.so

libOmxVidEnc.so

libskia.so

libstagefrighthw.so

libttssynthproxy.so

and test if the camera and gps work.

Could some one try to remove just libSFM_runtime.so and see if the ROM boots.

Well those are some ideas for the moment.
[Click Android Development] rallapag:
Hi MaffyRain

Can you push iptables and Netd binaries from GB CM roms in to this ROM try to reboot the ROM.

They are in /system/bin/

Change permissions to 755

Let me know if you need more info.

Keep going mate.
[Click Android Development] MaffyRain:
2) I deleted libSFM_runtime.so and I reflashed the ROM containing testlibs then I waited for about 10 minutes then I made ​​the logcat, this is the last part before I'd stop it.

I//system/bin/iptables( 950): Flushing chain `POSTROUTING'

I/Netd ( 973): Netd 1.0 starting

I//system/bin/iptables( 973): Flushing chain `INPUT'

I//system/bin/iptables( 973): Flushing chain `OUTPUT'

I//system/bin/iptables( 973): Flushing chain `FORWARD'

I//system/bin/iptables( 973): Flushing chain `PREROUTING'

I//system/bin/iptables( 973): Flushing chain `OUTPUT'

I//system/bin/iptables( 973): Flushing chain `POSTROUTING'

I/Netd ( 993): Netd 1.0 starting

I//system/bin/iptables( 993): Flushing chain `INPUT'

I//system/bin/iptables( 993): Flushing chain `OUTPUT'

I//system/bin/iptables( 993): Flushing chain `FORWARD'

I//system/bin/iptables( 993): Flushing chain `PREROUTING'

I//system/bin/iptables( 993): Flushing chain `OUTPUT'

I//system/bin/iptables( 993): Flushing chain `POSTROUTING'

I/Netd ( 1016): Netd 1.0 starting

I//system/bin/iptables( 1016): Flushing chain `INPUT'

I//system/bin/iptables( 1016): Flushing chain `OUTPUT'

I//system/bin/iptables( 1016): Flushing chain `FORWARD'

I//system/bin/iptables( 1016): Flushing chain `PREROUTING'

I//system/bin/iptables( 1016): Flushing chain `OUTPUT'

I//system/bin/iptables( 1016): Flushing chain `POSTROUTING'

3) I took the libs indicated by rallapag, from the ROM nfinityGB1.13, WITHOUT using libstest (rallapag you meant to do so, right?) And I replaced those already in the original 1.2 ROM ported therefore libSFM_runtime.so

---------- Post added at 04:11 PM ---------- Previous post was at 04:08 PM ----------

sorry I have not seen my post and I'm just waiting for the result of Step 3. I'll try as soon as you say.
[Click Android Development] rallapag:
For test 3 above, you are right

Yes just replace the indicated libs at the end of post 62 (libgps.so might also be needed so please add it from nfinityGB rom)

with those in the 1.2 version of the ROM. so you still be having libSFM_runtime.so.

About deleting libSFM_runtime.so, could you do this on 1.2 ROM only and see if we get Tattoo booted.

And about netd and iptables binaries, you could do this on test 3 above if you see the same logcat as in test1 and test2.

It would be nice if any experienced dev out there, checks if we are in the right direction.
[Click Android Development] MaffyRain:
Also in case 3) I get this logcat

I / / system / bin / iptables (82) Flushing chain `OUTPUT '

I / / system / bin / iptables (82) Flushing chain `FORWARD '

I / / system / bin / iptables (82) Flushing chain `PREROUTING '

I / / system / bin / iptables (82) Flushing chain `OUTPUT '

I / / system / bin / iptables (82) Flushing chain `POSTROUTING '

I / Netd (132): 1.0 Netd starting

I / / system / bin / iptables (132): Flushing chain `INPUT '

I / / system / bin / iptables (132): Flushing chain `OUTPUT '

I / / system / bin / iptables (132): Flushing chain `FORWARD '

I / / system / bin / iptables (132): Flushing chain `PREROUTING '

I / / system / bin / iptables (132): Flushing chain `OUTPUT '

I / / system / bin / iptables (132): Flushing chain `POSTROUTING '

I / Netd (155): 1.0 Netd starting

I / / system / bin / iptables (155): Flushing chain `INPUT '

I / / system / bin / iptables (155): Flushing chain `OUTPUT '

I / / system / bin / iptables (155): Flushing chain `FORWARD '

I / / system / bin / iptables (155): Flushing chain `PREROUTING '

I / / system / bin / iptables (155): Flushing chain `OUTPUT '

I / / system / bin / iptables (155): Flushing chain `POSTROUTING '

rallapag then proceed as you suggested.

I have some questions: are OK nfinityGB1.13 bin files taken from the ROM and copied to the rom downloaded 1.2 from the second post? how to change the permissions (currently I'm working on windows)? I copy only the xinetd and iptables in the bin folder? sorry but with windows I do not know, I think the procedures are different. I am more skilled with linux.
[Click Android Development] rallapag:
if you have already copied the binaries, then use following commands,

adb shell chmod 755 /system/bin/iptables
adb shell chmod 755 /system/bin/netd
[Click Android Development] MaffyRain:
So I try to do so:

a) take the Sapphiresense Tattoo1.2-sign-ROM and unzip

b) add (override those of Sapphiresense 1.2) from the 1.13 NfinityGB these libs

libdvm.so

libhardware_legacy.so

libgps.so

libjpeg.so

libm.so

libnativehelper.so

libOmxH264Dec.so

libOmxMpeg4Dec.so

libOmxVidEnc.so

libskia.so

libstagefrighthw.so

libttssynthproxy.so

c) I override netd and iptables binaries of the Sapphiresense 1.2 with those of the NfinityGB 1:13

d) re compress everything, install and add the patch (kernel-radio etc..)

e) without rebooting, from the recovery, change the permissions of the files as you said

f) reboot

forgotten anything? check please, then I'll try.
[Click Android Development] rallapag:
Perfect

Hope it works
[Click Android Development] MaffyRain:
ok I installed the rom and the patch I had to restart the cell otherwise the system folder / bin there was still nothing and gave no such file or directory. after I could Always Changing their permissions entering in recovery.

~ # chmod 755 /system/bin/iptables

chmod 755 /system/bin/iptables

~ # chmod 755 /system/bin/netd

chmod 755 /system/bin/netd

~ #

exit

adb reboot

and now I'm waiting ... if nothing happens again I put the logcat
[Click Android Development] rallapag:
Sorry my mistake, you dont need to change permissions if you are replacing the ROM zip files.

Because update script will add the relevant permissions.

You only need to change the permissions if you are pushing files in to ROM.
[Click Android Development] MaffyRain:
this is the only thing that appears when I start the logcat

--------- beginning of /dev/log/main

D/AK8973 ( 93): AK8973 daemon 1.3.4 Start

D/AK8973 ( 93): (Library version : 1.2.1.620)

W/HtcEbdLog( 96): open /devlog/.htc_ebdlog.daemon.pid: Read-only file system

W/HtcEbdLog( 96): write /devlog/.htc_ebdlog.daemon.pid: Bad file number

--------- beginning of /dev/log/system

I/Vold ( 81): Vold 2.1 (the revenge) firing up

D/Vold ( 81): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media

)

W/Vold ( 81): Ignoring unknown switch 'usb_connected'

D/VoldDirectVolume( 81): device name = mmcblk0

D/Vold ( 81): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)

D/Vold ( 81): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted

)

E/Vold ( 81): Cannot open CDROM lunfile

D/Vold ( 81): USB connected

D/Vold ( 81): Share method ums now available

I/DEBUG ( 83): debuggerd: May 19 2011 21:58:13

^C

---------- Post added at 06:44 PM ---------- Previous post was at 06:32 PM ----------

I also tried without changing the permissions but it's still on the screen and the TATTOO logcat says:

--------- beginning of /dev/log/main

D/AK8973 ( 93): AK8973 daemon 1.3.4 Start

D/AK8973 ( 93): (Library version : 1.2.1.620)

W/HtcEbdLog( 95): open /devlog/.htc_ebdlog.daemon.pid: Read-only file system

W/HtcEbdLog( 95): write /devlog/.htc_ebdlog.daemon.pid: Bad file number

--------- beginning of /dev/log/system

I/Vold ( 81): Vold 2.1 (the revenge) firing up

D/Vold ( 81): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media

)

D/VoldDirectVolume( 81): device name = mmcblk0

D/Vold ( 81): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)

D/Vold ( 81): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted

)

E/Vold ( 81): Cannot open CDROM lunfile

D/Vold ( 81): USB connected

D/Vold ( 81): Share method ums now available

I/DEBUG ( 83): debuggerd: May 19 2011 21:58:13
[Click Android Development] rallapag:
Well something has changed.

I will try to ask around what we could do.

Thanks for all your efforts MaffyRain.

__________________________________

By the way could you just try to boot 1.2 version (with out libSFM_runtime.so)

Thanks
[Click Android Development] MaffyRain:
well, maybe I was planning to implement patches in the release at least you will not have to do three flashes every time but only one. I have three full days of free time,then I log in every day, so if I can help you as much as I can, ask as well. I wait new post to continue the development. P. S. Also maybe try to ask general questions in the section Section HTC tattoo.
[Click Android Development] MaffyRain:
great, now that the patches are implemented we can focus on solving the bug system, then we will think the graphics, what do you think?

now have much free time so I'll do a little 'test for what's wrong vedrere leave a logcat Standard 1.2.1 as well as the rom then I'll see what's wrong in the bedroom gps etc..

the results this evening (20:30 approx) Italian time.