12.19 3d package with better performance for testing - Touch Diamond2, Pure Android Development

12.19 3D PACKAGE WITH BETTER PERFORMANCE FOR TESTING
http://forum.xda-developers.com/showthread.php?t=852937
-----------------------------------------------------------------------------------
GIVES THANKS TO "djdafreund" FOR DOING THIS FOR US. THANKS
----------------------------------------------------------------------------------------
Latest Kernel
Commit# 1238
Commit Date: Sat Dec 18 20:44:32 2010
Commit ID: 43f0a96
Pushed by: ACL (on behalf of WisTilt2)
Commit Messages:
•1238 - Speakerphone mic fix.
http://forum.xda-developers.com/showthread.php?t=869992
or
http://www.megaupload.com/?d=MVUZIME1 .....zimage and modules
=====================================
http://forum.xda-developers.com/showthread.php?t=852937
1 - Grab the "zImage and Module's" download
2 - Grab the "all 3d drivers and gralloc" download
3 - Grab the "build.2.prop. and froyo.user.conf.zip"
Extract the 3 following files from the downloaded files into the main directory of your SD card
--------------------------------------------------------------------------------------------------------------
- libGLES_qcom.so
- gralloc.msm7k.so
- build.prop
Just edit "froyo.user.conf" and add these 3 commands below.(Should be close to the end of this file, located in your (android dir)\CONF\ directory"
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
mount bind/sdcard/libGLES_qcom.so /system/lib/egl/libGLES_qcom.so
mount bind/sdcard/gralloc.msm7k.so /system/lib/hw/gralloc.msm7k.so
mount bind/sdcard/build.prop /system/build.prop
Finally, unzip the "zImage" and "modules.xxxxx" files you downloaded also in your main android directory, (replacing zImage when asked, and deleting your previous module.xxxxx file)
Then, download the 2 APK file's, "fps2d" and "com.adobe.air.xx" file, and try installing them within Android (double click on the file's within Android), run fps2 3 time's to get a good average.)
Hope this is helpful, that's me!! The more user's we get to help this, making it easy to understand and follow, the more we can help your progress with this.

will test in a bit, thanks for link.
It appears that this isn't compatible with the phone (AT&T Pure) it hangs whatever application tries to use the 3d driver.
edit- nevermind, seems to be functional, speed increase isn't really that noticeable though.
edit2- problem is file was named .so.so in original zip, mount path only includes .so

device: HTC Touch Diamond 2 T5353 528MHz
SPL radio: 4.49.25.91
version of Android: system-FRX03(FINAL)
kernel version: htc-msm-linux-20101124_215731
so far very responsive....
manage too run angry birds with good graphics but lag maybe coz of the our phone processor....
good job mate

kjtan said:
device: HTC Touch Diamond 2 T5353 528MHz
SPL radio: 4.49.25.91
version of Android: system-FRX03(FINAL)
kernel version: htc-msm-linux-20101124_215731
so far very responsive....
manage too run angry birds with good graphics but lag maybe coz of the our phone processor....
good job mate
Click to expand...
Click to collapse
Good. Stay tune, we still tweaking it. It getting better. Thanks
sprint htc touch pro 2 (rhod400)

My scores with HTC Touch Diamond 2 T5353 528MH
17,6 in neocore and 445 in Quadrant.

tiad8 said:
forum.xda-developers.com/showthread.php?t=852937
hey guys i have this 3d driver. i want people to
test it. i already post it over PPCGEEKS .
with this driver im getting better graphics ,
smoother speed . anything that used 3d works
great for me . 3d gallery loads in seconds . games
have better graphics . angry birds lite beta plays
great .
Speed is good on games .
Just mount this file ( libGLES_qcom . so) . Thanks
to ACL. We have a way to mount this
using froyo conf. Just edit froyo conf and add
this command.
mount - -bind / sdcard / libGLES_qcom . so /
system / lib / egl/ libGLES_qcom . so
Or download this one
Click to expand...
Click to collapse
sprint htc touch pro 2 (rhod400)

works great
hello i tested this with qoudcom 3d bencmarking and it works well on htc diamond 2 frx03 latest kernels thanks

How to install it in XDAndroid??

instructions
download this file (3d driver) libGLES_qcom . so and put it on your SD card. Then download my froyo. Conf and replace the one that you have. in config on sd Good look. Thanks you
here is the link http://forum.xda-developers.com/showthread.php?t=852937

What's my froyo??

zooster said:
What's my froyo??
Click to expand...
Click to collapse
devi fare download di libGLES_qcom.so.11.29.10.ZIP.zip e froyo.user.conf.zip
qui http://forum.xda-developers.com/showthread.php?t=852937
apri libGLES_qcom.so.11.29.10.ZIP.zip e metti libGLES_qcom.so dentro il primo livello della carta SD.
apri froyo.user.conf.zip e metti froyo.user.conf dentro la cartella con il nome "conf"

froyo
my froyo is a file on sd card by map config /froyo.user.conf

will this 3d lib work on LENINred's Eclair(2.1) ?

Hi, Guys, I used a folder "Andboot" to booting Andriod, so how can use the driver?
Many THX!

brafun said:
will this 3d lib work on LENINred's Eclair(2.1) ?
Click to expand...
Click to collapse
ok figured it out myself! downloaded the .so placed it in the root folder of the SD and put in andboot/conf/eclair.user.conf the mount string bit... got 18.2 FPS
Next question is will this drain the battery faster?

xrshwy said:
Hi, Guys, I used a folder "Andboot" to booting Andriod, so how can use the driver?
Many THX!
Click to expand...
Click to collapse
just the same
place the .so on root of ur sd card
and replace the conf file inside andboot/conf

Hi, Tommy,
I have put the .so on SDCARD, the andriod didn't work at all, and I have put the .so in folder andboot, the andriod can start but slowly. and I didn't know the 3D driver had been instilled correct or not. where can I find this information?
Thanks.

brafun said:
will this 3d lib work on LENINred's Eclair(2.1) ?
Click to expand...
Click to collapse
yes it worked for me. i already test his build with 3d driver and is smoother. thanks

first post updated. test and report please.
3d driver for testing with gralloc. UPDATED 11.29.10

1.open up the froyo.user.conf
2.make sure this line is at the bottom
mount --bind /sdcard/andboot/libGLES_qcom.so /system/lib/egl/libGLES_qcom.so
3.dump it replace the file in the andboot/conf
4.then place ur libGLES_qcom.so under ur andboot folder
all above is base on the following folder structure
-sdcard
-andboot
-AndroidApps
-conf
-media
-STARTUP CONFIG

Related

[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

Windows 7 Netbook Edition Build 7264 x86

Just FYI ive got the touchscreen working on this striped down version of a RC branch build of 7. Its very snappy and memory usage is down to 400MB after booting and it takes up 4GB of HDD space.
Id definitely recommend it to anyone with a shift, To get the touchscreen working set the Tablet PC and Human Interface Device Access services to automatic startup at first boot
Enjoy, Don't ask about where to find it or how to activate it or things that would get this thread deleted as its a must have for all shift users.
Is everything working ok? Wifi, shift control center, screen resolution?
Same as usual yeah it only takes up 4GB of disk space
Ok, thanks. I'll try.
Seems the only problem i could find is Office 2010 not installing because of error 1903, It can be fixed by copying the c:\windows\fonts folder from another instalation and not overwriting whats already there
Thanks for the find kashifsiddique!
I'm currently downloading this Build 7264 x86 I was wondering how big is the fonts folder? Would it be possible to post a link just in case other don't have another windows installation.
Looks like the fonts folder is about 350MB. I'll just back this folder up that I have before I reinstall. =)
Thanks again!
HI all -
I vill test windows 7 Netbook but i can not fin the download link,can you post the link where vi can download
sorlei said:
I vill test windows 7 Netbook but i can not fin the download link,can you post the link where vi can download
Click to expand...
Click to collapse
forum rules don't allow direct linking, try usenet or bt
Ciao Dannyt84 non riesco a mandarti la mail
se puoi mi invii il link
Grazieeeeeeeeeeeeee

Guide:How to store multiple android builds in your SD card

If u want to store more than one android build in ur SD card u just have to make folders and put the build in there.example:
u want the gingerbread 2.3.1 bulld and the FRX04 build in your sd card
make a folder in ur SD named BUILDS(or anything that u want)
in this make a folder named ginger(for tha 2.3.1 build) and one frx04(for tha xdadroid frx04)
then edit the startup.txt from each built.add "rel_path=BUILDS/ginger"to the gingerbread build and "rel_path=BUILDS/frx04" for the frx04
"rel_path=xxx" this command changes the boot folder
Hmmmm...good....then how to choose it?? When we use GenY Dual Boot.
Sent from my SuperFroyo by Neopeek using XDA App
i think that tou have to change the registry....look at this(http://forum.xda-developers.com/showthread.php?t=623792)i personaly don't use bual boot....just run haret.exe manualy...
thanks. Do we use the same Haret.exe + intrd + etc. for all builds ? i mean, they still stay in the root of the SD card right ?
working with two neopeek builds
Working with two neopeek builds in etx2 install?
Regards
morocomolr said:
Working with two neopeek builds in etx2 install?
Regards
Click to expand...
Click to collapse
I Think it work!
When you edit startup.txt root=/dev/mmcblk0p3, it will...??
nice info!
thanks! ^_^
Multiple ext2 builds needs editing init file
morocomolr said:
Working with two neopeek builds in etx2 install?
Regards
Click to expand...
Click to collapse
As far as I know, it needs editing of at least the init file at root.
Maybe an experienced user can confirm that.
I have had success at booting multiple ext2 installs, but it is very buggy for me.
Just started looking at Android.

Camera Confirmed to work on Topaz!

Hi All
Today I found a combination (which might have been out there for a while) how the Camera actually is working for Topaz Android
1. Download the FRX04 version
2. http://forum.xda-developers.com/showthread.php?t=883966 check there for section "Topaz Users"
3. Don't forget the post "[23/01/2011] :" to dissable 2 rows in froyo.conf file
The Camera was able to startup and I took one Picture
The speed of the Cam.. well.. don't be to happy.. but it is working anyway
/olme
Yeah,works fine, but only 3 MP and without auto-focus,but it works more quick than im windows mobile.
Oh,but programm(name forgotten) in FRX04 for Rhodium(23.01.11) is more usable,you can make photo by pressing on volume keys
yes indeed WinMo is quicker.. but one step at the time This is the first time I ever on my Topaz and Android was able to even see that it was "connected" and that I could take a picture.
The next development will be that the rest of the goodies will appear such as speed and autofocus etc etc..
GOOD job Android Devs!
/olme
Please, keep in mind that it's in debug state, a branch of XDAndroid code made by viruscrazy.
If you want to help test it, follow the instructions in the first post and leave your logs there.
Thanks.
Somebody tested camera on FRX04(23.01.11)?
saneksem said:
Somebody tested camera on FRX04(23.01.11)?
Click to expand...
Click to collapse
yes with provided topaz test kernel it's working till 3mp pictures
@5mp camera crashed... but this is allready known and developer asked for dmesg log files to finetune the driver...
-bl4ckb1rd
p.s. camera driver did not work with latest 01253 kernel
can any1 pls upload the conf file? because i couldn't find the 2 rows......
[23/01/2011] :
Updated Lib_package to fix the froyo.user.conf file (thanks to arrrghhh again, you're the "conf file" specialist) and the Blackstone picture crash (I hope...). If you are using latest FRX04 build and rootfs, you may have to disable the two following lines (add a "#" at the begginnning of the line) :
Code:
mount --bind /sdcard/lib_camera/libGLES_qcom.so /system/lib/egl/libGLES_qcom.so
mount --bind /sdcard/lib_camera/gralloc.msm7k.so /system/lib/hw/gralloc.msm7k.so
Could DEVs add camera to Gingerbread?
There is a new fix for 5MP. It works. You need the Kernel from 28.01.11 and the new attached Haret Version. Do not use the attached kernels and don't forget to write the line:
set INITRD_OFFSET 0x608000
under "set initrd initrd.gz" (Startup.txt)
http://forum.xda-developers.com/showthread.php?t=883966
CameraWorks
Erikson89 said:
There is a new fix for 5MP. It works. You need the Kernel from 28.01.11 and the new attached Haret Version. Do not use the attached kernels and don't forget to write the line:
set INITRD_OFFSET 0x608000
under "set initrd initrd.gz" (Startup.txt)
http://forum.xda-developers.com/showthread.php?t=883966
Click to expand...
Click to collapse
I also confirm it works
Here it doesn't. New haret makes the topaz reboot in winmo...
Well, it doesn't seem to work with Froyo X...
What doesn't seems to work?
The Camera is working but as the forum said.. only stable up to 3Mpixels...
olme said:
Hi All
Today I found a combination (which might have been out there for a while) how the Camera actually is working for Topaz Android
1. Download the FRX04 version
2. http://forum.xda-developers.com/showthread.php?t=883966 check there for section "Topaz Users"
3. Don't forget the post "[23/01/2011] :" to dissable 2 rows in froyo.conf file
The Camera was able to startup and I took one Picture
The speed of the Cam.. well.. don't be to happy.. but it is working anyway
/olme
Click to expand...
Click to collapse
Place a files hire!
Brain-brick with your link
sorry I don't understand what you want me to do..
Do you want me to place a link to my files I used to get the Camera running or what?
cheers
/Olme
olme said:
sorry I don't understand what you want me to do..
Do you want me to place a link to my files I used to get the Camera running or what?
cheers
/Olme
Click to expand...
Click to collapse
Yes! Yes and Yes!
check this link where I have uploaded my andboot.
1. Download it and extraxt it anywhere
2. put the 2 folders on the root of your SD Card.
3. Start Haret.exe
hotfile .com /dl/101065742/b00ae64/andboot.rar.html
Thanks for you effort uploading the file
I think someone needs to thank you also , but i think he's "cooking" right now
olme said:
check this link where I have uploaded my andboot.
1. Download it and extraxt it anywhere
2. put the 2 folders on the root of your SD Card.
3. Start Haret.exe
hotfile .com /dl/101065742/b00ae64/andboot.rar.html
Click to expand...
Click to collapse
wow
thx, cam is working for me, but only up to 2 Mpix,
but in this version wifi error after reconnect... :-(
yes i think cooking can be started ;-)

[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.

Categories

Resources