yashsingh1/xdaforums huggingface dataset:
[Click Android Development] djemm1996:
why when i start boot it stucks on this girl?

I wait 5 min. and nothin' doing. :(
[Click Android Development] djemm1996:
I need WI-FI. :(

WHY WI-FI can't start with AzusaROM v1.03-1 Kernel Update?? :mad::mad:

:confused:

EDIT : camera too don't work. :(

EDIT II : camcorder too dont work [black screen]
[Click Android Development] frere-jack:
where is the AzusaROM v1.03-1 Kernel Update ?

thanks
[Click Android Development] djemm1996:
download here ! (dont work. ;) )
[Click Android Development] frere-jack:
AzusaROM13052010.zip it this the old ROM ?

Or the ROM is repack with patch ?

Thanks for help :)
[Click Android Development] djemm1996:
this is new rom with working camera and wi-fi [but on my tattoo dont work] :(
[Click Android Development] liderzr:
Re: [ROM] AzusaROM v1.03 - Redhot Firespitting Firecrackers - 13/05/10

Why ":(" ?

-------------------------------------

Sent via the XDA Tapatalk App
[Click Android Development] djemm1996:
not work wi-fi and camera. ;(
[Click Android Development] liderzre:
Any1 else confim wifi and camera working?

TY
[Click Android Development] frere-jack:
Not work wifi and cam for me :( :(
[Click Android Development] liderzre:
Then where is link for AzusaROM v1.03-1 Kernel Update ??
[Click Android Development] Coburn64:
Will be done within a few hours. Currently it's cold and I can't code when it's freezing. Brrr...

I can confirm Wifi and Camera/Camcorder is fully working with v1.03-1.
[Click Android Development] djemm1996:
Re: [ROM] AzusaROM v1.03 - Redhot Firespitting Firecrackers - 13/05/10

Camera not work.

-------------------------------------

Sent from my HTC Tattoo
[Click Android Development] liderzre:
@djemm1996

how do you know that the camera does not work when it is not yet released (v1.03-1)?
[Click Android Development] djemm1996:
this?

AzusaROM v1.03.13052010 - Available
[Click Android Development] liderzre:
I think "AzusaROM v1.03.13052010 - Available " is not v1.03-1.

Read Coburn latest post...
[Click Android Development] svprm:
SetCPU also not working.

Due to no root access.

Others having the same problem.
[Click Android Development] Coburn64:
If you're using SetCPU, please wait until a version CoburnKernel comes out with built-in Overclocking mods. SetCPU is kinda risky.

Also, I have uploaded a unsigned version of the kernel update to my Coburn's Domain forum thread, available here. You will need to use the testsign tool to sign the file BEFORE flashing it from recovery, OTHERWISE YOU WILL NOT BE ABLE TO INSTALL THE KERNEL AS THE RECOVERY WILL REPORT THERE IS NO SIGNATURE!

I will sign the file tonight and upload to my main website server. Coburn's Domain is the home of AzusaROM, and deserves some lovin'. :)
[Click Android Development] alberto88a:
hi coburn, what about app2sd in your rom? I really need it and i'd like to flash your rom 'cause it seems to be really good...this is my only problem...I need to install many apps 'cause I'm studyng android programming at a university course and I should be able to install remove and reinstall as fast as I can and the internal memory is really small...

thank you for the answer :)
[Click Android Development] Coburn64:
I'm working on Apps2SD. It shouldn't be too hard to implement, just time is the killer. :)

I'm not delaying it, it's on the Todo list. From what I've heard, it should be pretty straight forward. (a few binaries and bang, Apps2SD is running or something like that).
[Click Android Development] alberto88a:
so will you implement it in the next release? :rolleyes:
[Click Android Development] nebster:
FLAC support?

Hey, would you be able to add flac support?

It's got all the information for the kernel patch here:

the-b.org/FLAC_on_Android

This is all I'm waiting for before switching from the stock kernel
[Click Android Development] ralle.gade:
dude it's not in the kernel it's in the system itself

the only way to implement it (as i see) is if Coburn switched to AOSP system, which is build from the source and therefore easier to modify
[Click Android Development] djemm1996:
New vesion is out - But how to install unsigned version?

It know, i can install with testsign tool . but where i can get it?
[Click Android Development] Coburn64:
I just got an email from my kernel cooker, he's got another kernel ready. Will test and upload it tonight for you guys (and girls)

I am also doing a "source tree" so people who want to see AzusaROM's internals can do so. I will not switch (at this moment in time) to the AOSP build from source method, while this may be a good approach:

1) It costs 2GB of bandwidth to download all the sources for Android

2) It costs 8GB of space on my HDD

3) I can't see the point of using it for only one ROM.

The thing is that I like building from RUU ROMs. That way, it's easier to work with and you know it'll work at the end of the day. If I decide to make a lot of ROMs, then again, I might use that method. Then again, there's also the kitchens that do the hard work for me. There is a slim chance for me to build a Android 2.2 ROM for the Tattoo if I decide to proceed down that path...

Just that time is the killer at the moment, and having to compile from source is a PITA - it's not all ready to rock (it takes a while to compile) unlike editing a RUU ROM files.
[Click Android Development] alberto88a:
*_* really?
[Click Android Development] TheSSJ:
It's difficult to say this, since there is no info about the compatibility of this ROM with our devices...at least for booting it up, otherwise it becomes more complicated developing a ROM for the Tattoo...:/
[Click Android Development] Coburn64:
Yeah, that's why I'm building from a RUU base, I know it works, I'm just customizing it and adding our own spices and whatnot.

The thing is, that Android 2.2 may only be device-specific - it may require a better config than our HTC Tattoo can provide. And also, 2.2 has a JIT compiler built-in.

I'm working on a vanilla 1.6 (ie. using no HTC RUU update) AzusaROM for anyone interested, at this rate, it'll be v1.05.
[Click Android Development] alberto88a:
but the htc wildfire has almost the same hardware configuration...the cpu is the same as for the screen resolution...the differences are the camera that is of 5mp with a led flash and for the ram that is over 300 MB...and the capacitive (but 2.8" QVGA) display..and it has ANDROID 2.1 upgradeable to 2.2...can you do something starting from this ruu rom? :o
[Click Android Development] ralle.gade:
That's no problem!! :) we can at least get 2.1 up running without problems

But now we'll see if it even comes out cross your fingers
[Click Android Development] alberto88a:
yes but i'd like to have camera and radio working in 2.1...:'(
[Click Android Development] ralle.gade:
the problem is wee need libs for the camera to get it to work
[Click Android Development] alberto88a:
we should use the wildfire's ones :o
[Click Android Development] ralle.gade:
you can't cause they are different since it has another camera
[Click Android Development] alberto88a:
mmm so we may try with the magic one that is maybe the same camera and the magic works fine with the 2.1...
[Click Android Development] Coburn64:
Isn't the camera controlled by a little chip or is it all software controlled?

If I don't see an update to 2.1 from HTC soon, it's curtains for my tattoo.

I have tweeted them a reply asking if the Tattoo will get 2.1, but they seem to be dodging the question. My HTC Tattoo is deeply scratched but still functional (I blame my USB Drives), and I'm getting the feeling that HTC isn't supporting their devices - so, if I don't see any updates for my Tattoo soon, I'll be jumping off the Tattoo ship and onto the Liquid/Nexus/Desire/Legend/XPERIA ship. I've got my eye on a Wildfire and it looks good, but I'm thinking of getting the X10 - the screen is huge and perfect for my use.

I love working on AzusaROM, but I am grasping the final straws with HTC - they just make me feel like "Thank you for buying, you have no support now".
[Click Android Development] alberto88a:
oh nooooo :'( dont leave us alone :'(
[Click Android Development] TheSSJ:
+1!!!

It's just about telling the users about features this phone does not have (like AutoFocus) and then leaving them alone with their problems...that the HTC way! x(

Don't know, since I don't want to spend too much money on mobile phones (as this is the 2nd in half a year, I had an LG KU990 before) I'll stay with my Tattoo...trying to find a solution to get that f***ing BT file transfer to work or just getting used to the fact that HTC tricked me and many other dudes..........
[Click Android Development] Coburn64:
I've been doing some kitchen rebuilding, and I'm working on AzusaROM 1.04. It will be a very barebones build, with lotsa pasta.... Er... Space for you to store internal apps and whatnot.

It will also feature CoburnKernel v7.0-experimental under the bonnet for the kernel. Stay tuned, don't rush me though - I'm quite busy with real-life stuffs. X(
[Click Android Development] Sargeros:
Stop spamming every thread...
[Click Android Development] aarat:
This is not a spam... I am notifying all the developers who are mainly subscribed to the forums where i have posted.
[Click Android Development] TheSSJ:
Then just open a new topic with your information, this should be sufficient...But since xPeria 10 and Tattoo have different BT chips I don't think that something can be done to achieve BT file TX...
[Click Android Development] NeXTWay:
Hi guys

Does anybody know where I can find the WiFi Fix for 1.03?

This Page (http://azusa.coburndomain.org/tmp2/AzusaROMKernelUpdate-v1.03.1-unsigned.zip) gives me a 404 Error >_<
[Click Android Development] Coburn64:
Just wait until AzusaROM 1.04 comes out.

I have stated that AzusaROM 1.05 will be my last version of AzusaROM. The timeline is hazy from that point on. I may continue development, I may not.

I am currently trimming the fat; does anyone know how I can zipalign APKs? Is there a tool to do so, or what?
[Click Android Development] TheSSJ:
On the premise that you have the 1.6 SDK, go to the tools folder and find the zipaling binary. Here's the syntax:

zipalign [-f] [-v] <alignment> infile.apk outfile.apk

The <alignment> is an integer that defines the byte-alignment boundaries. This must always be 4 (which provides 32-bit alignment) or else it effectively does nothing.
Flags:

[LIST]
[*]-f : overwrite existing outfile.zip
[*]-v : verbose output
[*]-c : confirm the alignment of the given file
[/LIST]
[Click Android Development] Coburn64:
Nice. Trimmed about ~10MB from the APKs on the stock base. This ROM is really gonna fly... Hehehe. :)
[Click Android Development] :
Coburn64 : When are you going to release the 1.04 version of Azura ?
[Click Android Development] kartoffel1212:
Your ROM is very fast but the camera makes problems :(
[Click Android Development] vidarb:
Tested 1.03, camera works perfectly but no wifi. Waiting for 1.04 :)

Thanks for your work!
[Click Android Development] kartoffel1212:
if i install various Apps (i think) after this freeze the cam
[Click Android Development] Coburn64:
Camera is a tad unstable - it works but sometimes can't take photos. 5% of the time in my tests it works.

I've been lazy and playing my Wii too much, lol. I should have AzusaROM 1.04 ready this week sometime.
[Click Android Development] kartoffel1212:
Hope so.. i think your ROM is the fastes 1.6
[Click Android Development] kartoffel1212:
Yo Coburn... dont watch Football pls release the 1.04 with stable Cam ;)
[Click Android Development] Coburn64:
Still cooking away as per usual!

I'm cooking AzusaROM 1.04 with 2 kernel versions. One is a vanilla kernel, which is a stock 2.6.29 with minor optimizations - This kernel is CoburnKernel v6.1. It's got camera working and all that stuff.

I have made CoburnKernel v7.1-experimental available. I will release two versions of the ROM, one turbo and one light.

Also, I have cleaned up 20MB out of the apps folder in the system partition. The ROM weighs in at 104MB right at this moment (when flashed), so yeah.

I understand that you'd like a lot of apps, but this ROM is intended to make a Android version that is minimal bloat. If you want Apps2SD and all that juicy goodness, be my guest and download another 1.6/2.1 ROM.

Due to my grudge against HTC, it is possible that I'll be selling my HTC Tattoo. If this is the case, I won't be leaving AzusaROM to rest in peace, I'll be building upon the fundamentals that I have made. All the AzusaROM files are in the Coburn's Domain Android Project File Browser (CD-APFB). I am also working on a stock rooted ROM with CoburnKernel v6.1 under the bonnet.

Pop me a tweet on my twitter if you'd like the latest info on the ROMs.
[Click Android Development] :
A release please <3
[Click Android Development] BmwStreetRacer:
Hi Coburn, great work!

While you finish Azusa 1.04 could you give me a help on how to apply the kernel update on 1.03?

Thank's & keep up the good work
[Click Android Development] alberto88a:
waiting for 1.4
[Click Android Development] Coburn64:
Just a quick update; I'm 99% done on AzusaROM 1.04. Sadly, I think something's gone a miss, as I can't seem to boot back into Android 1.6 after installing KiljackenROM v1.2.

I'm on school holidays and also got a new laptop, so I can work on it faster now. (My Macbook had linux on it, but it was buggy, so I sold it and got a ASUS PRO59L instead).
[Click Android Development] dancer_69:
I downloaded this version:

AzusaROM v1.03.13052010 - Available (Download Here!)

but wifi cannot start. Is this the latest version?
[Click Android Development] toushiro:
Yes, and I can't use wifi too...
[Click Android Development] BmwStreetRacer:
Not Quite

The last version is a kernel update, with the kernel applyed the wifi works.
[Click Android Development] gain_:
Can you tell us how to apply the kernel update for making wifi working?
[Click Android Development] Coburn64:
Just try out 1.04 - everything works.

EDIT: I'm uploading v1.04 as we speak. It's codenamed "Speed Demon", it's been optimized with zipalign and features a kernel that makes everything work (CoburnKernel 6.2 Vanilla).
[Click Android Development] kongkows:
i'm try to download, but how come it's tell me that the link was broken?

http://cdn.coburndomain.net/android/azusa/AzusaROM_1.04_29062010.zip
[Click Android Development] nonoheran:
Any native FLAC support ?

Without a 3rd part APP ?? that s good to implement it i think
[Click Android Development] loverde1:
interface has the sense ?
[Click Android Development] Makarboy:
Do radio and led works on this rom?
[Click Android Development] Z1CkY:
no sense..

dont work wifi for me :(
[Click Android Development] TheSSJ:
Since based on stock ROM with speed improvements radio and LED should work, since I don't think that any driver was removed...
[Click Android Development] dom_b:
WiFi doesn't work on Orange UK Tattoo (all other ROMs do)

Worst boot screen ever!
[Click Android Development] TheSSJ:
You can change the bootscreen - don't criticize the taste of others! Search in the forum and enlighten yourself - if you want the nexus one bootscreen, just get it and put it into /system/media/bootscreen
[Click Android Development] RevengeITA:
this rom seems great, while waiting for an eclair porting..

what are pros and cons of this rom comparing with tho original one?

wifi, video, bluetooth fully work?

what about battery duration?

tnx;)
[Click Android Development] Makarboy:
Bluetooth file transfers work? Thanks
[Click Android Development] banafaen:
No wifi here either. Tried WPA2-PSK

Stuck on getting IP address.

Bluetooth: Connected to PC, but cant transfer anything. No services available

-bana
[Click Android Development] Coburn64:
I'm looking into the WiFi issues.

The ROM doesn't have BT File Transfer, nor do I have the apks to add to enable that function. Can someone link me to a copy of the apks that I need to install for BT File Transfers to work?

@Bootscreen issue: So, you don't like a girl in a maid outfit on boot? Like TheSSJ said, you can replace it easily. At least it's not porn. And the bootscreen that I included is family-safe.

@Battery Life: It lasts longer. I can roughly get 2 days out of a full charge, with GPS on (but no maps open) and Wifi on with light use.
[Click Android Development] Da9L:
Will this ever get sense ? And maybe iam not seeing it but does this run android 1.6 or 2.1 ?
[Click Android Development] Coburn64:
It runs the Android 1.6 core from an HTC RUU update.

Sense UI is possible for v1.05. I'll prepare the APKs and optimise them, Sense UI should work smoothly after that.
[Click Android Development] htcuser69:
wifi don't work

boot image how to remove it
[Click Android Development] Coburn64:
@htcuser69: That's very helpful just stating that WiFi doesn't work. >_<

Just flash a boot screen like this one: http://xdaforums.com/showthread.php?t=649925
[Click Android Development] liderzre:
So much work, and no rom with working wifi...

and then "good bye" thread?

:confused:

Good bye :(
[Click Android Development] Coburn64:
I haven't given up completely, I've just stated that my days with my HTC Tattoo are coming to an end, as I'm going to sell it. I'm working on the WiFi issue. :)
[Click Android Development] suoko:
Wanted to sell it too but need to revert it to original rom first.

did u find an update.zip to do that?

or must use nand ?
[Click Android Development] francians:
I think you should follow this to rollback:

http://xdaforums.com/showthread.php?t=603286
[Click Android Development] DeeFolt:
Hi Coburn, Any update on wifi issue?
[Click Android Development] tso4ev:
pls make ap2sd
[Click Android Development] tso4ev:
this rom is rubish first I instal it and now I cant change it with onother rom give me instalation aborted what I neet to do .. :@
[Click Android Development] mrigesh:
@ipaq114 this rom as such do not give such problems as u say it does.....did u flash the amon-ra recovery image? As it lets you to flash a rom with ease
[Click Android Development] francians:
First of all, you can't say this is rubbish! It's a flamer thing.

It's your tattoo that give the pb..

Now you shoud check the md5 or download again the other ROM.

if don't work you have to change recovery.. if you have the Amon install maverix, if you have maverix install Amon.

Then if you have always the same pb, create the gold card and follow this thread:

http://xdaforums.com/showthread.php?t=603286
[Click Android Development] ariewtf:
i think your the first one who finished a rom
[Click Android Development] schwarzlichtkind:
Is anybody ever looking into the Wi-Fi issue??? I also had the problem and for me this is really a dealbreaker... :(:(:(
[Click Android Development] RevengeITA:
So everything works in this rom? Bluetooth file transfer tio?
[Click Android Development] schwarzlichtkind:
No one´s ever going to look into the WiFi-issue?????

Sad....
[Android Software/Hacking General [Developers Only]] siddyb:
can i load any rom on my dstl1 and get android market or does it have to be rooted if so can someone tell me how to do it
[HD2 Windows Mobile 6.5 Themes and Apps] de Wolfe:
Hi. I just saw on HTC-SEA-page that they are offering Sprite-Backup for HD-Mini. Now I'd like to know if this version is brouht via HTC for free and maybe if it is compatible to our HD2. By any chance, has anybody a SEA-serial of any HD-Mini or is anybody able to download it via some direct-link? Just curious. :)

EDIT: it is also offered on Thai-HTC, and HK-En-HTC and general SEA-HTC.
[HD2 Windows Mobile 6.5 Themes and Apps] alex fung:
For HK versions of HD2, the Sprite Backup is included on the SD card, but it is not documented (at least I can't find it mentioned anywhere on the web site or on the printed material).
[HD2 Windows Mobile 6.5 Themes and Apps] de Wolfe:
Is it full-version or only a trial like CoPilot in Europe?
[Omnia II Themes and Apps] neato4u:
Guys, I just bought Omnia 2 and it seems the GPS lag so much that it's totally useless. I use Garmin XT and the GPS lags about a couple of minutes. Is it a phone issue or what?:confused:
[Omnia II Themes and Apps] nuelo:
This is what I have done, and it work's (at least for me Omnia i8000):

Change these settings in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver\Drivers\Samsung GPS Hardware\InputBufferSize: set from 4096 to 512

HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver\Drivers\Samsung GPS Hardware\OutputBufferSize: set from 4096 to 512

HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver\Drivers\Samsung GPS Hardware\SleepOnNoData: set from 100 to 0

HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver\Multiplexer\MaxBufferSize: set from 16384 to 1024

The rest is the same as the usual GPS and TomTom settings. I used com port 4 (and 9 for hardware), but you can probably use any other port that hasn't been assigned yet.
[Omnia II Themes and Apps] kingchicky:
Is this really working? somebody can also give a hint?
[Omnia II Themes and Apps] 1sokel:
[HKEY_LOCAL_MACHINE\Software\Samsung\RIL\GPS\XTRA]

"Enable"=dword:1

"AutoDownload"=dword:1

"AutoDownloadActiveSync"=dword:1

HKEY_LOCAL_MACHINE\Software\Samsung\RIL\GPS

Accuracy=1 or 4 old 19

Vaccuracy=1 or 4 old 0

ResponseTime=0 old 2

QOPDelay=0 or 1 old 12

MaxLocationAge =0

ServerAddress=

xtra1.gpsonextra.net:80

Timesync= 1 old 0

do that after buck up your reg with a regeditor

and then you have a top class GPS

first time update your extra first time locks in about 2 min in clear sky

and after that in a couple of seconds:)
[Omnia II Themes and Apps] passion_streak:
does that work .. can any one confirm ?? coz i m having same trouble .. .plzz help !!!!
[Omnia II Themes and Apps] Nordic7770:
The one and only FULLY OPERATIONAL Navigation Software is:

IGO8

Try it and find it out :D
[Omnia II Themes and Apps] dawo5010:
GPS fix

Hi i'm using AGIS NAVFone (Asia), but should work for all GPS devices

First:

Go to Settings>Connectivity>GPS (or something like that)

My phone's in servicing now... sad

Set COM9 to hardware port

COM7 to GPS

Baud Rate: 9600

Gives me a fix ~2min

To make it quicker: Install GPSModDriver here:

forum[.]xda-developers[dot]com/showthread.php?t=571266

What it does:

Follow the instructions there to install, and Garmin Mobile XT requires QueStub

So get QueStub 3.10,

and GPSModDriver 3.10

With this you can get ~3s Fix (For me)

Take time to read through that post and feel free to ask any questions.
[Omnia II Themes and Apps] msurg:
Anyone tried this?
[Omnia II Themes and Apps] flopyro:
you can test your GPS dialing " *#1472365# "

and there u can change these values to.
[Omnia II Themes and Apps] fofos:
nothing appears in the screen when typing these neumbers