Related
I tried a very simple thing and it worked!
Just replace the tnetwln.dll by one comming from an AKU 3.3 ROM like Faria's (or the one in the attached .ZIP file). It's as simple as 1-2-3:
1. copy the attached tnetwln.zip to your Wizard,
2. explode tnetwln.dll and copy itto \Windows with Total Commander,
3. soft reboot your machine (with psShutXP or equivalent).
At the next reboot you will support WPA2 and WPA2-PSK with AES encryption!
I tested this on the original Orwell1984 crossbow ROM.
Enjoy!
eluth.
it works!! thanks! i tested this with wpa2-psk and it connected flawlessly. time to integrate into my rom...
notyourdaddy,
I'm about to do that too (integrate it in my own ROM).
So far I was successfull in replacing the tnetwln.dll module (aka directory as output of viewimgfs) by the tnetwln.dll file (in the attached zip) and rebuild the ROM.
This works, however I don't know how to re-create a module and relocate it.
Is there a tool to do so? I check on the forums but could not find something compelling...
damn this is so simple, i wonder why faria didnt tell abt that no1.
WPA2-PSK is working anyway without your fix for me, is this a problem with specific Crossbow ROMs?
Using Orwell's at the moment.
neonkoala said:
WPA2-PSK is working anyway without your fix for me, is this a problem with specific Crossbow ROMs?
Using Orwell's at the moment.
Click to expand...
Click to collapse
seems that u have dll from aku 3.3 integrated in wm6 rom, i prefer clean roms.
This was the main reason I haven't taken the plunge and installed Crossbow on my Wizard, excellent news this works
I have had a quick look at how to cook my own ROM but I have so far left it alone. Ideally I would like all the nice parts from Faria's AKU 3.3 ROM but with the Crossbow base - any takers
Andy
Hi
I was wondering if anyone can post the version of tnetwln.dll of a pre AKU 3.3 rom? I have Core2.0n on my Wizard and I am having trouble with my Wi-Fi. before I declare my wi-fi radio completely an utterly crippled I would like to attemt rolling back to the older version of tnetwln.dll
The 1 in Core 2.0n is the same as the 1 posted in the first post..
Any help is greatly appreciated.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
BEFORE REPORTING ANYTHING PLEASE SPECIFY KITCHEN VERSION AND LANGUAGE
I CAN NOT TRACK PROBLEMS WITHOUT THIS
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Download WWE kitchen005(OLD ONE 24.04.09)
http://rapidshare.de/files/46885174/KITCHEN_Breeze_21040_21040_6.1_0.005.rar.html
Download WWE kitchen 006(NEW ONE 27.04.09)
http://www.sendspace.com/file/3ddkoz
Download WWE 007 ROM4.05.09 (fixes for all bugs)
http://www.sendspace.com/file/bssdyi
big thanks to bepe,duttythroy and all other that made this possible for their work in this comunity
and itje for all his contributions
Oem contents
OEM.cer
OEMAPPS
OEMCamera
OEMDrivers
OEMMISC
OEMOPERATORS
OEMVersion
OEM_DPI_131
OEM_Lang_0409
OperatorPkg
PACKAGE_APP_AutoKeylock
PACKAGE_APP_CHomeConfigurator 1
PACKAGE_APP_PHMRegistryEditor
PACKAGE_APP_Reboot
PACKAGE_APP_RSSHub
PACKAGE_APP_Slick
PACKAGE_Breeze_HTCColdBoot
PACKAGE_Captain_Arcsoft_MMS
PACKAGE_Captain_BandSelect
PACKAGE_Captain_BandSelect_0409
PACKAGE_Captain_BluetoothSecurity
PACKAGE_Captain_BluetoothSecurity_0409
PACKAGE_Captain_BootLauncher
PACKAGE_Captain_BootLauncher_0409
PACKAGE_Captain_CallBarringPassword
PACKAGE_Captain_CallBarringPassword_0409
PACKAGE_Captain_ClearStorage
PACKAGE_Captain_ClearStorage_0409
PACKAGE_Captain_CommManager
PACKAGE_Captain_CommManager_0409
PACKAGE_Captain_ConcurrenceMgr
PACKAGE_Captain_ConcurrenceMgr_0409
PACKAGE_Captain_ContactUtilityEngine
PACKAGE_Captain_ContactUtilityEngine_0409
PACKAGE_Captain_DataDisconnect
PACKAGE_Captain_DataDisconnect_0409
PACKAGE_Captain_DRMMiddleware
PACKAGE_Captain_DRMMiddleware_0409
PACKAGE_Captain_DShow
PACKAGE_Captain_DShow_0409
PACKAGE_Captain_Enroll
PACKAGE_Captain_Enroll_0409
PACKAGE_Captain_FDN
PACKAGE_Captain_FDN_0409
PACKAGE_Captain_FlashLiteShareDLL
PACKAGE_Captain_FlashLiteShareDLL_0409
PACKAGE_Captain_GoogleMaps
PACKAGE_Captain_GPRSAuth
PACKAGE_Captain_GPRSAuth_0409
PACKAGE_Captain_HSDPASwitch
PACKAGE_Captain_HSDPASwitch_0409
PACKAGE_Captain_HTCAnimation
PACKAGE_Captain_HTCAnimation_0409
PACKAGE_Captain_HTCMessage
PACKAGE_Captain_HTCMessage_0409
PACKAGE_Captain_HTCSlidingPanel
PACKAGE_Captain_HTCSlidingPanel_0409
PACKAGE_Captain_IME_Smartphone_Western_TMOUS
PACKAGE_Captain_InvokeSIMMgr
PACKAGE_Captain_InvokeSIMMgr_0409
PACKAGE_Captain_JBlendJava_6_1_TMOUS_ALL
PACKAGE_Captain_LockStreamDRM
PACKAGE_Captain_LockStreamDRM_0409
PACKAGE_Captain_mHubVO
PACKAGE_Captain_mHubVO_0409
PACKAGE_Captain_MS_AdobeReaderLE
PACKAGE_Captain_Mute
PACKAGE_Captain_Mute_0409
PACKAGE_Captain_MyCPL
PACKAGE_Captain_MyCPL_0409
PACKAGE_Captain_NewMailAccount
PACKAGE_Captain_NewMailAccount_0409
PACKAGE_Captain_PhoneCanvas_TMUS
PACKAGE_Captain_PhoneCanvas_TMUS_0409
PACKAGE_Captain_PictureEnhancement
PACKAGE_Captain_PictureEnhancement_0409
PACKAGE_Captain_PKG
PACKAGE_Captain_PKG_0409
PACKAGE_Captain_PowerInformation
PACKAGE_Captain_PowerInformation_0409
PACKAGE_Captain_PowerManagement
PACKAGE_Captain_PowerManagement_0409
PACKAGE_Captain_Redial
PACKAGE_Captain_Redial_0409
PACKAGE_Captain_RingtonePlugin
PACKAGE_Captain_RingtonePlugin_0409
PACKAGE_Captain_SharedModules
PACKAGE_Captain_SharedModules_0409
PACKAGE_Captain_SIMLock
PACKAGE_Captain_SIMLock_0409
PACKAGE_Captain_SIM_MGR
PACKAGE_Captain_SIM_MGR_0409
PACKAGE_Captain_STK_Service
PACKAGE_Captain_STK_Service_0409
PACKAGE_Captain_STK_UISP
PACKAGE_Captain_STK_UISP_0409
PACKAGE_Captain_StorageLow
PACKAGE_Captain_StorageLow_0409
PACKAGE_Captain_SystemInfo
PACKAGE_Captain_SystemInfo_0409
PACKAGE_Captain_USSD_Service
PACKAGE_Captain_USSD_Service_0409
PACKAGE_Captain_VisibilityTimeout
PACKAGE_Captain_VisibilityTimeout_0409
PACKAGE_Captain_VoiceRecorder_AudioPostcard
PACKAGE_Captain_VoiceRecorder_AudioPostcard_0409
PACKAGE_Captain_VolumeControl
PACKAGE_Captain_VolumeControl_0409
PACKAGE_Captain_YouTube
PACKAGE_Captain_YouTube_0409
Registry_Hide SIM Contacts
Registry_Ring_Tone
Registry_SecurityOff
Eagerly anticipating...
rom is almost ready
i am searching for bugs
youtube is unusable (maybe just for now)
using Rose dialer
control pannel having unusable links
camera not working yet
in 1-2 days i will release an final rom and kitchen
br
jerpelea said:
rom is almost ready
i am searching for bugs
youtube is unusable (maybe just for now)
using Rose dialer
control pannel having unusable links
camera not working yet
in 1-2 days i will release an final rom and kitchen
br
Click to expand...
Click to collapse
thank you!
first alpha rom is up
search for bugs
thanks
br
-In setting Menu --> the connections link does not work. "The Setting could not be opened."
-Then under Settings/Power the "Power information" is unavailable.
-Google Maps link in the menu does not work.(components missing)
Then I tried installing HardSPL before this rom and ran into some problems,
went though the guide and got up to "SPL 1.10 and CID HTC__A07" with the "RUU_MTeoR_1.34.251.1_1.38.00.10_HTCEUR_SHIP" rom. Then Application unlocked. That all went well.
Then in Step 8,"check for spl if it sais 2.05 you can go further if not read the fisrt guide" I don't have SPL2.05.
I ignored this, since the current SPL 1.10 is newer, and copied the HardSPL files to the Phone root and the Breeming to the SD card. If I run SPL then and hold Power+Camera It does say "SPL-1.01 " but after reboot there are no onscreen instructions to follow. And the SPL goes back to 1.10.
Any Ideas on what I am missing?
Thanks
Bad_German said:
-In setting Menu --> the connections link does not work. "The Setting could not be opened."
-Then under Settings/Power the "Power information" is unavailable.
-Google Maps link in the menu does not work.(components missing)
Then I tried installing HardSPL before this rom and ran into some problems,
went though the guide and got up to "SPL 1.10 and CID HTC__A07" with the "RUU_MTeoR_1.34.251.1_1.38.00.10_HTCEUR_SHIP" rom. Then Application unlocked. That all went well.
Then in Step 8,"check for spl if it sais 2.05 you can go further if not read the fisrt guide" I don't have SPL2.05.
I ignored this, since the current SPL 1.10 is newer, and copied the HardSPL files to the Phone root and the Breeming to the SD card. If I run SPL then and hold Power+Camera It does say "SPL-1.01 " but after reboot there are no onscreen instructions to follow. And the SPL goes back to 1.10.
Any Ideas on what I am missing?
Thanks
Click to expand...
Click to collapse
thanks for bugs i will solve them and release the kitchen
i cant help you with the other problem just follow the guide
br
all found bugs solved
rom and kitchen uploaded
br
jerpelea said:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
BEFORE REPORTING ANYTHING PLEASE SPECIFY KITCHEN VERSION AND LANGUAGE
I CAN NOT TRACK PROBLEMS WITHOUT THIS
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Download WWE kitchen
http://www.megaupload.com/?d=NS38YRCW
Download WWE 001 ROM13.04.09
http://www.megaupload.com/?d=WGHF9P17
big thanks to bepe,duttythroy and all other that made this possible for their work in this comunity
and itje for all his contributions
Click to expand...
Click to collapse
i can not open this web site?why?
I need to read chinese sms,does it support chinese well ?
or I need to wait for the chinese version that translated by some one
thanx
Thank you for your work, jerpelea
I have a htc breeze device, just flashed this 21040.16.0 rom
This rom is way faster than futureshock`s rom I have used previously.
I like a new touch (don`t remember if it was in the rose rom also) that it vibrates when beeps end and you can speak.
If anyone is troubled with t9 absence here is the solution
The only left problem is non-working camera. I wonder if there might be a solution.
Regards.
Hi J, Excellent work, besides the missing camera app I picked up another "bug", in Kitchen 21040(Build 21040.1.6.0). I find the Start menu items do not show, i can browse through them and open them but cant see them... sounds strange to describe but the bottom line is that it looks like the start menu's font and icons are white and the background is also white...
BTW, this was from the Kitchen, have just brought down the ROM, will try use that, perhaps I changed something in the kitchen by accident.
I flashed ROM cooked by J. Start menu is visible. Everything is ok.
tehre are still 2 bugs
camera and bluetooth bug
i will solve them when i will have time
i hope this week
br
Some more bugs
1. Each time I try to change home screen from the settings ,menu I get "Unable to save settings" error. HTC Home is the only working option. Now I am allowed to change Color scheme but yesterday I was not.
2. There ara also troubles with establishing internet connection from 3d party software like slick or jblend java machine (it doen`t start the internet connection, reporting an error and works ok when connection is established by other program) while weather application from HTC home works ok and establishes connection itself.
The good thing is that battery seems to last longer comparing to futureshocks 6.1 rom I used previously.
karmacoma7 said:
Some more bugs
1. Each time I try to change home screen from the settings ,menu I get "Unable to save settings" error. HTC Home is the only working option. Now I am allowed to change Color scheme but yesterday I was not.
2. There ara also troubles with establishing internet connection from 3d party software like slick or jblend java machine (it doen`t start the internet connection, reporting an error and works ok when connection is established by other program) while weather application from HTC home works ok and establishes connection itself.
The good thing is that battery seems to last longer comparing to futureshocks 6.1 rom I used previously.
Click to expand...
Click to collapse
1.you have the first alpha rom / that problem is fixed for some time
2.i will check
br
I can not access this web site?
Would you like to upload the rom kittchen to another site?
thank you!
bugs status
infrared solved
bluetooth solved
internet is working
camera is working
a new kitchen and rom will follow soon
br
Did you get the Youtube app to work? It only starts correctly in landscape mode, but after a couple of seconds it exits...
AzusaROM Android Custom ROM Series
Cooked by Coburn64.
>>> Access the Coburn's Domain version of this AzusaROM topic here <<<
What's this?
AzusaROM is a version of Android that is faster, sleeker and breathes new life into your HTC Tattoo. Named after Azusa in the K-ON Anime, the ROM is powered by a custom kernel and has a lot of the bloat removed from it's 1.67.405.6 RUU Update base. Android 1.6 is at the core of the ROM.
AzusaROM is not really intended to be a CyanogenMod for HTC Tattoo. But, you could look at it that way. Please note that AzusaROM will not be based on Android 2.x bases until later on in it's development cycles. While there are 2.1 ROMs for the Tattoo available, they aren't fully completed and/or working.
ROM Status
AzusaROM is currently in public beta. It has been tested and it can be used as a every day-to-day ROM on your HTC Tattoo. Everything works on the v1.04 CoburnKernel, which is version v6.2vanillla. If you have a suggestion or an improvement, please share it and I'll see what I can do.
Current Version: v1.04
Current Version (In-Dev): Unknown
How do I use this?
You will need a HTC Tattoo that has been rooted and has a custom recovery installed. You can find tutorials about rooting the Tattoo and installing custom recovery images in this threads' forum.
Copy the file onto your HTC Tattoo's MicroSD Card, reboot into the custom recovery (I recommend Amon_RA Recovery) and choose "Apply update from ZIP." Select "AzusaROM_v1.XX_Y.zip" (where XX is the version number, and Y is a build timestamp). Watch the screen, AzusaROM will tell you what's going on.
Where do I get help?
I can be either Private Messaged on the Coburn's Domain Message Forums, XDA-Developers, emailed or you can reply to this thread. I prefer either posts in this thread or Coburn's Domain, I have both threads here and at Coburn's Domain under my watch list, which will send out daily emails of new posts in those threads.
Credits
HTC (Making the Tattoo), Optus Australia (best. Australian. Telco. Ever.) ralle.gade (I'm in his debt!), Maxisma (you rock), Benocharm (support), Cyanogen (for CyanogenMod), Donators (for all the coffee), XDA-Developers (rock solid forums, best smartphone dev forums that I've ever been to), and all other developers that I've saved from losing their sanity. And you - for using AzusaROM.
Support The Coburn!
I can't do this without funding. I'm a part-time Android Hacker and I'm also a High School student. By donating, you'll help me get better gear to continue cooking ROMs and making them better. You can always get a Coburn's Domain Plus/Pro Account and support me that way, which in turn also allows you to use Coburn's Domain services.
Can I upgrade my ROM? Eg. AzusaROM v1.01 to v1.03?
In theory, yes, but I've found it will break a few things. Please backup your data and wipe before flashing newer ROMs.
Stuff that Coburn needs to fix/do
Everything works. Yay.
See posts to follow. Space reserved for future use.
Downloads
(OLD) AzusaROM v1.0.07042010 - Not Available (Old Build)
(OLD) AzusaROM v1.01.08042010 - Available (Download Here!)
(OLD) AzusaROM v1.02.27042010 - Not Available/Unstable (See AzusaROM v1.02-1)
(OLD) AzusaROM v1.02-1.28042010 - Available (Download Here! Or Download it here (Mirror)!)
(OLD) AzusaROM v1.02-2.28042010 (UNOFFICAL BUGFIX RELEASE BY TheSSJ) - Available (Download Here!)
(RETIRED) AzusaROM v1.03.13052010 - Available (Download Here!)
(NEW) AzusaROM 1.04.29062010 - Available (Download here)
Changelog
AzusaROM v1.04 "Speed Demon"
Final AzusaROM Release unless a bug crops up.
Camera and Camcorder fully working.
WiFi is working.
BlueTooth works (can sync to my GPS, etc etc).
Busybox installed in /system/xbin
Look in /system/xbin for an easter egg.
AzusaROM v1.03-1 Kernel Update
WiFi now works.
Camera actually takes pictures.
Camcorder works fine.
AzusaROM v1.03 "Red-Hot Fireball Spitting Firecrackers"
CoburnKernel v6 custom kernel
New Theme
Rolled back to working ROM base
Tattoo-hack.ko installed along with wifi.ko in /system/lib/modules
AzusaROM v1.02-2 "Even Coburn makes mistakes..." Bugfix Release 2
Unoffical Build, but boots now!
AzusaROM v1.02-1 "Oh sh*t the kernel spazzed out" Bugfix Release
Fixed Very bad kernel black screen fault on boot - rolled back the kernel.
WiFi broke.
Quick and dirty fixes.
AzusaROM v1.02 "Popcorn"
Very basic firstaid kit script (lol)
Trimmed down the fat.
Scripts in /system/xbin
Kernel has ext4 for backwards compatibility with ext3 and ext2 partitions.
SPEED SPEED SPEED.
Sense UI trashed, replaced with aHome Mini
Most HTC Apps Removed THAT MEANS NO HTC PEEP - SORRY FANS!
"Friday" ringtone is default ringtone
Azusa now greets you at boot (new bootscreen)
AzusaROM v1.01 "Meteor"
Removed some sounds, ringtones, etc
Tested it with swap file, bullet speed!
Uses CoburnROM v1.6 core with boot from miki's ROM
New Boot Screen (Azusa in Maid outfit from K-ON anime)
Dream Theme (from HTC Dream/G1) default ringtone
Flash-proof (no bricks on flash!)
Sense UI enabled by default (may be removed in future releases)
If someone would like to mirror them or make BitTorrent torrents of them, please let me know! (My server gets about 5-10GB just from my Android ROMs, and I have 1TB to fill... )
Screenshots
Taken using my mum's camera.
what are the features and what about app2sd on this rom? :O
I haven't thought of that, I think it would be better if apps where loaded on Internal NAND Flash, faster and more reliable. If there's a lot of need for it, I'll make it available.
I'll love you if you do that
anyway what about the general features of this rom? what are the differences among yours and other roms or the official one?
the tattoo is my first android device
The differences at the moment are just some removal of some stock apps and other tidbits that I tidied up. I also got swap file working, and busybox is installed in /system/xbin.
Coburn64 said:
The differences at the moment are just some removal of some stock apps and other tidbits that I tidied up. I also got swap file working, and busybox is installed in /system/xbin.
Click to expand...
Click to collapse
I actually have a modaco r1 with a2sd but I can stay without it...i partitioned my microsd with the amon-ra recovery in 32mb swap 512 ext3 and then fat32...
do I need to repartition? Do I need the ext3 partition with your rom? what about root access?
I prefer to cook my own ROMs, I don't like to use online kitchens. It's better the trial and error way!
I read you are going to do the update for the swap...why don't you think app2sd is necessary? I don't install more than 10-15 applications but without a2sd my rom was full
Can you give me a rough estimate of what app sizes you were installing? Like Bubble Blast may be 21.04MB. Just a range, like 1MB to 10MB will also do.
EDIT: Added swap instructions to Post #2.
Coburn64 said:
Can you give me a rough estimate of what app sizes you were installing? Like Bubble Blast may be 21.04MB. Just a range, like 1MB to 10MB will also do.
EDIT: Added swap instructions to Post #2.
Click to expand...
Click to collapse
I know that after installing every app I need I tried installing raging thunder 2 (that is really slow on the tattoo) and it told me there were no space enough
I may committ suicide if this appens again
Thanks!!
Downloading it...will post comments after testing..
could you please post some screenshots? it would be really appreciated
Nice to see AzusaROM again.
Suggestion:Add app2sd.
It would be nice.
ambuj said:
Thanks!!
Downloading it...will post comments after testing..
Click to expand...
Click to collapse
Ok..So I have downloaded and installed, boot up without any problem.
However, while doing the initial seeting, it could not connect to my wi-fi router.
I tried for 30 mins, changing this and that, refreshing router but could not succeed.
So, I have reverted back to my old Modaco ROM.
may be this wi-fi is problem for me only.
If someone has done it successfully please post it here.
alberto88a said:
could you please post some screenshots? it would be really appreciated
Click to expand...
Click to collapse
Screenshots will not be of any use as visually there is no difference between stock ROM and Azuas ROM.
Can anyone tells me if AzusaROM is based on stock ROM?
or taken by a vanilla or other ROM?
Thanks.
Thanks
Hello!
I just installed this ROM... it's running fine. But, now I'm not able to get the wireless to work. It detects my network, but it's not connecting
I can see this with logcat:
I/wpa_supplicant( 709): wpa_driver_tista_driver_cmd POWERMODE 0
I/wpa_supplicant( 709): wpa_driver_tista_driver_cmd BTCOEXMODE 2
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
I/wpa_supplicant( 709): CTRL-EVENT-STATE-CHANGE id=10 state=8
V/WifiMonitor( 77): Event [CTRL-EVENT-STATE-CHANGE id=10 state=8]
V/WifiStateTracker( 77): Changing supplicant state: COMPLETED ==> DORMANT
D/WifiStateTracker( 77): Deconfiguring interface and stopping DHCP
I/wpa_supplicant( 709): CTRL-EVENT-DISCONNECTED - Disconnect event - remove key
s
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
I/wpa_supplicant( 709): CTRL-EVENT-STATE-CHANGE id=-1 state=8
Click to expand...
Click to collapse
How can I solve that?
Thanks anyway for you work ;D
weren't u working
on openeclair 1.3 or latest ?
i thought you could take me to a full working eclair planet
@Above: Yes, I was working on OpenEcliar 1.3, but I decided to roll back to v1.6 to give it some lovin'. For the fun of it, I might even do a cupcake build!
But don't worry, the AzusaROM 2.x series will be using Android 2.x bases.
casidiablo said:
Hello!
I just installed this ROM... it's running fine. But, now I'm not able to get the wireless to work. It detects my network, but it's not connecting
I can see this with logcat:
[..snip..]
How can I solve that?
Thanks anyway for you work ;D
Click to expand...
Click to collapse
Hm, that may be a permissions issue. I'll look into that later - thanks for reminding me.
Glad to hear that everything else works apart from the wifi bug. I'll update the post when I get on my development oven tonight - Gotta update it to Ubuntu 10.04 64bit Beta 2.
I found out the hard way that apparently the WPA2 implementation in Android is faulty. This means it can not connect to WPA2 secured APs which enforce strict specs:
https://forum.openwrt.org/viewtopic.php?id=25870
Would it be possible to fix that in CM ?
Cheers,
Karl
Android is using wpa_supplicant, it doesn't implement the protocols on its own.
So you are saying the bug is actually in wpa_supplicant ?
Should i try to make them aware of the problem ?
First time I hear that, although I have at home WPA2 personal and my Legend connects with it normally.
I have a WPA2 personal network both at home and at my dorm, and my HeroC has been able to connect to them fine no matter what ROM I've used (stock, Sense 2.1 custom ROMS, and CM6/7)
According to the openwrt link i posted above it seems to be a problem with the drivers on openwrt enforcing strict RFC compliance and the wpa_supplicant not sticking to it. So it might just be a problem for a specific setup.
However, the question now is if that should be fixed in android or if openwrt should relax its rules.
I just try to find out which community would be the right one to address...
Hey AliBa !
People at openwrt think its a problem of the TI wireless drivers, and that it could be fixed in CM:
This is not a problem with OpenWRT, hostapd, or wpa_supplicant (the latter two are the same project, and mostly written by one person). This is a bug with Android wifi drivers that do not properly follow spec.
The TI Wilink driver I referred to is particularly at fault, and disabling WMM on the router is a band-aid to the problem - not a fix or a real solution. wpa_supplicant is not even involved in this process since the Wilink driver generates the RSN on its own.
The people who need to address this are TI, not openwrt or CM or someone else (or CM can put in a patch to fix the TI Wilink driver, which is probably a good idea anyway).
Click to expand...
Click to collapse
https://forum.openwrt.org/viewtopic.php?id=25870
There are two RSN settings in tiwlan.ini:
Code:
RSNPreAuthentication
RSNExternalMode
...try setting latter to external.
Hey BlaY0 !
This .ini file is in the build tree, not on the phone, right ? Or can i set that on my phone ?
If its a part of the build files, do you think I should file a bug at CM ?
It's on the phone... /system/etc/wifi/tiwlan.ini. It's configuration file for driver itself.
Might be a noob-problem, but i am unable to write to the file.
I tried terminal emulator, su, vi /etc/wifi/tiwlan.ini, but its read-only.
Any other way i can try this ?
Use recovery to do that or you can use system overlay.
Sent from my HTC Legend
Tried switching the RSN..-config to external as mentioned, but it's not working here.
Hmm, anything else we can do ?
AliBa, are you sure you could not fix this ?
People at openwrt think it could be patched in CM:
https://forum.openwrt.org/viewtopic.php?id=25870
Cheers,
Karl
Yes, I'm sure I can't fix that.
If it's not caused by wpa_supplicant then there's nothing we can do. Sources for neither firmware nor kernel module are open sourced so there's no way to patch them.
Hey !
ali ba said:
Yes, I'm sure I can't fix that.
If it's not caused by wpa_supplicant then there's nothing we can do. Sources for neither firmware nor kernel module are open sourced so there's no way to patch them.
Click to expand...
Click to collapse
Too bad. Didnt know that some (?) kernel modules are closed source in android. What a shame !
Anyway, thanks for trying to help !
karl_k said:
Hey !
Too bad. Didnt know that some (?) kernel modules are closed source in android. What a shame !
Anyway, thanks for trying to help !
Click to expand...
Click to collapse
It's a royal PITA, and we all dislike HTC, Motorola, Samsung etc. for doing it. That said, the CM team do an unbelievable job of dealing with it as well as they do
karl_k said:
Too bad. Didnt know that some (?) kernel modules are closed source in android. What a shame !
Click to expand...
Click to collapse
Every Google device was as close to open source as possible with all kernel sources being released. It's companies like HTC that corrupt that whenever they can. For example they put code into the framework that would normally go into the kernel just to not having to release it.
Moreover, the sources for wl12xx were open sourced by TI using a BSD-like license. The even sadder problem is that HTC modified them and then deliberately removed those modifications (headers) from the kernel sources they released.
So its a dead end, and really nothing can be done about it?
Can't believe that!
Anyone knows how to change "regulatory domain" on 2.0 rom ?
Need to change channels to see my offices rooter.
I checked now 1.9 and it can see this rooter.
Installed also cyanogenmod and changed under "regulatory domain" to 14 channels and can see my rooter.
Anyone knows how to change this manualy on 2.0 rom ?
Or which file is it, so I can maybe copy from 1.9 rom?
DeMar27 said:
Anyone knows how to change "regulatory domain" on 2.0 rom ?
Need to change channels to see my offices rooter.
I checked now 1.9 and it can see this rooter.
Installed also cyanogenmod and changed under "regulatory domain" to 14 channels and can see my rooter.
Anyone knows how to change this manualy on 2.0 rom ?
Or which file is it, so I can maybe copy from 1.9 rom?
Click to expand...
Click to collapse
Hi Demar, I'm currently on GR4, but it should be the same on TP2.
I just tested with my own setup, I set the wi-fi channel on the router to channel 13, and the phone was unable to connect.
Then I changed the property "ro.wifi.channels" in build.prop to 13. After a reboot it connected fine.
So it seems that's all you need to do, either edit or add the line
"ro.wifi.channels=14"
to your build.prop.
Yeah. I know this. I tried, but without results..
DeMar27 said:
Yeah. I know this. I tried, but without results..
Click to expand...
Click to collapse
Which kernel are you using? I'm on HP-RC4.
Problem solved.
I'm not sure with what ?
I changed following:
ro.product.locale.region=EU
ro.wifi.channels=14
And installed some script that I found on forum
No I can choose regulatory domain
Wifi channels enable for both 11g/11n networks
DeMar27 said:
Problem solved.
... installed some script that I found on forum
Click to expand...
Click to collapse
Hmm... What script do you mean?
Anyway, to enable last (14) channel for .11g, without the script,
you need to set "wifi_country_code=JP" in the "secure" table in the following database:
"/data/data/com.android.providers.settings/databases/settings.db".
(It may be easily done with RootExplorer and SQLite editor installed).
Also, it may help for 5GHz .11n too, by default (for USA) very few channels are available,
Most channels in .11n become active with EU code in the field above.
And, there is no need to reboot the phone after change - just switch WiFi off/on!
alanber said:
"/data/data/com.android.providers.settings/databases/settings.db"
Click to expand...
Click to collapse
In my case there is no .db file
But it's a Samsung Galaxy A5 (2017) of course...