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
Quote:
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)
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.
Quote:
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/show....php?t=1316156
i moved system/app folder to cache/systemapp and symlinked to system due to less space in system partition
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
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
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.
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.
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
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)
ASAP in Android land means at least six months, so if you ask me something don't expext anything earlier
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)
The topic of piracy is always a touchy subject, but I feel that the grass roots style of Android … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?