yashsingh1/xdaforums huggingface dataset:
[G1 General] vale_arna84:
Here is the device partition layout.

# df -h

Filesystem Size Used Available Use% Mounted on

tmpfs 47.7M 0 47.7M 0% /dev

tmpfs 47.7M 0 47.7M 0% /mnt/asec

/dev/block/mtdblock3 90.0M 75.7M 14.3M 84% /system

/dev/block/mtdblock5 117.8M 25.1M 92.7M 21% /data

/dev/block/loop0 4.0M 4.0M 0 100% /system/xbin

/dev/block/mtdblock5 117.8M 25.1M 92.7M 21% /cache

/dev/block/mtdblock4 2.0M 776.0K 1.2M 38% /dev/cache

/dev/block/vold/179:1

966.6M 106.8M 859.8M 11% /mnt/sdcard

/dev/block/vold/179:1

966.6M 106.8M 859.8M 11% /mnt/secure/asec​

I don't think aosp system is bigger than 90M. In fact the system folder inside my rom is 49.1M.
[G1 General] AndDiSa:
Your partition layout looks good so far. It seems that the mtd-patch is working, so flashing should not be a problem, but when you use the mtd-patch you have to flash the ROM from recovery, otherwise the modified partition layout is not known!
[G1 General] vale_arna84:
Yes, of course, I did it. In fact it worked for CM6 rom. The problem is with aosp froyo rom. Maybe the kernel is different? I've built the rom with the original kernel found on the froyo branch. I can try using a different one. Which kernel does CM6 for dream uses?

Thanks
[G1 General] AndDiSa:
You have problems in flashing, don't you? While you are flashing, the kernel does not matter, except that boot.img is too big and does not fit into the boot partition. Most likely your updater-script is not correct and all your errors are due to that ... (only guessing).
[G1 General] vale_arna84:
Yes, you are right. My problem was in the updater-script. I've added

getprop("ro.bootloader") == "1.33.2005" ||​

and I've successfully flashed the rom.

The problem is that the rom does not boot and I'm stuck on g1 logo.

The updater-script part related to bootloader (before adding 1.33.2005) was as follows:

assert(getprop("ro.bootloader") == "1.33.2004" ||

getprop("ro.bootloader") == "1.33.0004" ||

getprop("ro.bootloader") == "0.95.3000" ||

getprop("ro.bootloader") == "0.95.0000");​

Should I use a different bootloader?
[G1 General] AndDiSa:
I don't think, that using a different bootloader will help to solve your problem. Most likely the kernel itself has some problems. Could be a linking problem, a missing library, ... Did you try to logcat using adb while booting? If you are lucky, the kernel is crashing after the intialization of adb and you can locate the problem.
[G1 General] vale_arna84:
Unfortunately adb does not start. I have no idea on what's going on. Probably nothing. I'll try to use a different kernel and let you know. Thanks;)
[G1 General] jubeh:
You're over-complicating things. Building AOSP should yield a working build. You can bypass the whole headache of having the right radio and SPL (and don't listen to lbcoder, he might be right, but it doesn't mean there's anything horribly wrong with the alternatives) by flashing your build from fastboot.

You didn't specify what you did to the build other than just using CM6 binaries. I'm going to assume all you did was sync a fresh new froyo repo, unzip-files.sh from CM6, lunch whatever-build-you-made, and make.

If that's the case, then I'm guessing it's a problem caused by a cm binary conflicting with the froyo dream kernel.

Make a build with no binary parts (just delete vendor/htc/dream) and see if that will boot, if it does, the kernel is not the problem.

Are you making an user build, if so, then you're probably getting android init and it's spewing out debug info, but since adb is not enabled by default on user builds, you can't see it, so make an eng or userdebug build instead.

Also, if it is the kernel, try unpacking your boot.img, re-pack adding a log dump to your cmdline, and then boot and check the log.
[G1 General] lbcoder:
An AOSP build doesn't come with checks against the SPL version. ONLY CM DOES!!!

It sounds like you are NOT flashing a build of AOSP, but rather some idiot's messed up junk.

And if adding an if 1.33.2005, then you did NOT install 1.33.2003 like I suggested. You instead installed 1.33.2005, which was a terrible mistake that could have bricked you. 75% of newbs brick their phones when they install that SPL!
[G1 General] lbcoder:
You're not making any sense there.

Main point is that 1.33.2003 is safe and strong. All other SPLs are either dangerous or weak and offer ZERO ADVANTAGE... therefore I suggest this specific one.
[G1 General] AndDiSa:
Most likely he didn't install 1.33.2005 but 1.33.2003 and he used the mtd-fake-SPL option, because I suggested so to enable him to install CM6.
[G1 General] vale_arna84:
Ok, I'll try to explain all the things I've done in more details.

I've built aosp from froyo branch without modifying anything. Only repo sync, unzip-files.sh with a CM6 (for dream) rom on the root of aosp tree and make. I haven't changed anything but the proprietary files.

I've used full_dream-userdebug lunch configuration.

The problem must be related to CM6 driver which are (i guess) not compatible with the kernel.

I've flashed a 1.33.2003 spl, not the danger spl. I've put 1.33.2005 inside the patcher-script because I've flashed the rom with the patch used to change mtd size and fake the spl as suggested by AndDiSa. The trick worked well and at least I have a working CM6 on my g1 without much effort.

Where can I find the right drivers for the g1? I've tried using those from htc and also the rom used by dferreira (http://member.america.htc.com/download/RomCode/ADP/signed-google_ion-ota-14721.zip?) but some files are missing for the g1 (dferreira uses a rom for sapphire and the roms on htc dev web site are for donut and cupcake). I don't remember exactly the names of missing drivers (I'm out for some days), but I remember something related to the camera and opengl.

I know I can build a full open source rom, but I need wifi.

Can I build the rom only with some drivers and exclude libcamera.so and the other missing drivers?
[Nexus One Accessories] zkgbz:
I bought the dock about 6 month ago, its a great product but 2 days ago, the piece where top of the phone locks in just cracked in two places, do you think Google or htc will replace it? or I am stuck with a broken dock?
[Nexus One Accessories] narcisco.cruz:
it will definitely be replaced... under one year warranty call htc to verify.
[Nexus One Accessories] bennettm89:
The exact same thing happened to me. I called HTC to warranty it. They need your IMEI from your phone to log it under. It look escalation to get it fixed, but I ended up getting two in the end ;). Just sold one for 110$ on ebay
[Nexus One Accessories] pwvandeursen:
same thing happend to me. unfortunately I live in the netherlands, and ordered it in the states (way before you could get it here...) any idea what I should do?
[Nexus One Accessories] xyellx:
still call htc -> http://www.htc.com/nl/
[Android Software/Hacking General [Developers Only]] madhuranand007:
Hey helper,:confused:

I am a proud owner of Samsung Galaxy and I rooted my phone. And i am enjoying the features after rooting :) But...........

My Question and problem is now my Volume + & - button on side of my phone its got totally unusable. Its hardly do its job. So did the service center entertain me or not.

Is there any solution so that I can fool them and get my Volume button changed.

Plz Plz tell me how to make it normal.

By the way the I installed superuser and after Hard reset it is still there. So how to remove it. :(
[Android Software/Hacking General [Developers Only]] firefox282:
You may need to download the stock Rom off of the internet and reflash the entire thing. There are more complicated ways to unrest but there are possibilities of doing more damage that way. May I ask what route you took to root your phone?
[Android Software/Hacking General [Developers Only]] MagickalShadow:
I know I am possibly going to make myself an unpopular buzz kill....but "fooling" them into warranty service on your phone after you voided the warranty is dishonest. I myself am guilty of voiding all kinds of warranties, my PC and my phone included. However I know that I assume the responsibility if they end up damaged.

If you are not ready to assume the responsibility, then modding may not be for you.
[EVO 4G General] nabbed:
Please add the option of modifying auto-brightness levels, like CM 6.1. I suppose that it would require a kernel modification + an app to do this through gui.

Thanks.
[EVO 4G General] Noxious Ninja:
What can CM do? I've been thinking it would be nice to be able to modify the min and max, and maybe the curve.
[EVO 4G General] nabbed:
It allows one to arbitrarily edit a table of sensor output vs brightness/button brightness.

It's really nifty.

CM6.1 reports these sensor values:

10, 160, 225, 320, 640, 1280, 2600, 10240

10-160 is in dimly lit indoors, 320-640-1280, in moderately to brightly lit indoors, and the rest is outside.

So I set those to brightness something like 50,60,70,80, 110, 140, 180, 255. A it was perfect to my eye. Not too bright, not too dim.

Didn't ever have to mess with brightness after that.
[EVO 4G General] nabbed:
I'd really like to hear from developers like Netarchy and King, as well as from regular users - if they would like that option.
[EVO 4G General] rdwing:
I would love to see this.

I always feel the auto-sensor tends to be too bright, and never adjusts the screen low enough inside.
[EVO 4G General] nabbed:
That's exactly what I think. Plus, the brightness is not at maximum in direct sunlight (although that might be a safety feature).
[EVO 4G General] Hrshycro:
Mine always send to bright, or it won't get bright when I go into a bright area until I sleep and wake it. :|

Sent from my EVO 4Gizzle.
[EVO 4G General] hd54321:
+1 on this. So motivated that I searched for this thread....
[EVO 4G General] nabbed:
Any news?

-----------
[EVO 4G General] Minjin:
The stock auto-brightness is way too bright in completely darkness. This is one of the things I had on my list nearly since the beginning. Nobody else seemed to care.

http://xdaforums.com/showthread.php?t=716547
[EVO 4G General] Minjin:
An article showing how useless auto-brightness is:

http://gizmodo.com/5673444/why-exis...d-brightness-controls-are-effectively-useless

Do people not notice this or do they just not care?
[EVO 4G General] AdamN:
Pretty sure people have given up on this. It's taken me three days of Google searching to find this thread so people probably don't know where to turn.

The lack of adjustments to the auto brightness values is extremely annoying. Even my old Windows mobile 6 phones had this ability.
[EVO 4G General] booyakasha:
There was an application for WM I used to use on my Mogul, cant remember what it was called but it allowed you to calibrate the auto brightness levels. Anyone know what I'm talking about, or if there's an Android version?
[EVO 4G General] JTNiggle:
This can be done with Tasker in the Market. Its a powerful app and there was a thread a while back about this exact thing. I don't remember what it was called, but I posted in it, so you could browse my posts from a month or so ago.

Hey... This thing makes phone calls too!
[Desire Q&A, Help & Troubleshooting] Notor1ouS-:
Ive annoying problems with this voice dailing app which came with froyo 2.2.

everytime i plugin a headset or even my line-in (in my car), my music starts to stutter and that voice recognition app pops up on my screen like 1000 times in a row .... (music still stuttering or even stops).

i tried to uninstall it but it doesnt "allow" me, also tried to disable it somehow.

any suggestion how i can get rid of it? i actually dont need that voice dailing app, its not possible to hear music in my car cause of it.. :P
[Desire Q&A, Help & Troubleshooting] lipsin:
I have the same problem, any solution?
[Desire Q&A, Help & Troubleshooting] hcastillo:
Disable voice services in Android

1. Install Android SDK in a computer.

2. Connect your mobile to the computer.

3. Run a shell using adb:

> adb shell

# _

4. You are now inside your mobile: in my mobile the packages involved with

voice (I have a Droid) are:

com.google.android.voicesearch

com.google.android.voicedialer

5. To verify if in your mobile are the same, run:

# pm list packages | grep voice

6. Whatever you find, run with the desired packages:

pm disable com.android.voicedialer

pm disable com.google.android.voicesearch

Obviously, I believe you will need root access to your mobile to do this.
[Desire Q&A, Help & Troubleshooting] Giiar:
If you have root,(not sure if you need s-off as well) I think you can just uninstall it through Titanium Backup. Another way is to delete the apk with root explorer by going into /system/app. I'm not good with ADB so I use root explorer or TB to remove unwanted apps. Hope it this helps.:D
[Desire Themes and Apps] Peikko:
I found this News and really like the Font shown in the Screenshots:

http://www.omgubuntu.co.uk/2010/10/new-ubuntu-font-meets-android-looks-stunning/

Although it has a step by step guide I wanted to ask if it would be possible for somebody to create an flashable zip?

At the moment I don't have Ubuntu installed because I'm waiting for the final release in 5 Days.
[Desire Themes and Apps] -Mr. X-:
ZOMG! Font!!1111! this is quite the development break through.....
[Desire Themes and Apps] Peikko:
Oh no... sorry ... I thought I was posting in the Themes And Apps Forum. Sorry for that. A Mod will move it. Again ... sorry.

But hey Juggalo atleast it gave you a reason for a very funny and sarcastic joke. You rule, bro. You should comment more threads with useless stuff. :rolleyes:
[Desire Themes and Apps] rolfd:
Moved to Themes and Apps as the OP posted by accident in the wrong forum.
[Desire Themes and Apps] -Mr. X-:
I was serious tho... :(

Dude, **** happens, i saw the opportunity for lolz and took it. If you cant laugh in life then your miserable, and if you cannot laugh at your self in times then you must be a miserable person :)

At any rate, Font = nice, Wrong section = funny and mod moving it = crisis overred.

Carry on.
[Desire Themes and Apps] Peikko:
well then I'm sorry but it only liked a bad joke on a tiny mistake I made. ;)

And thats nothing I larf about.
[Desire Themes and Apps] -Mr. X-:
Guess yah win some, and you lose some eh ;)
[Desire Themes and Apps] Semicuda:
You can download the fonts here:

http://en.fonts2u.com/download/ubuntu.familie

(only Ubuntu and Ubuntu Bold needed)

and apply them with Font Changer:

http://xdaforums.com/showthread.php?t=744363

(you should rename them to Ubuntu.ttf and Ubuntubd.ttf first)

Edit: Yes, they do look awesome :D
[Desire Themes and Apps] martino2k6:
Looks good... but awfully similar to Verdana :/
[Desire Themes and Apps] dmpwd:
it cuts a bit of the numbers in HTC clock... although, all in all, looks great
[Desire Themes and Apps] Enhdojo:
or use this PC Suite/Font Flasher: http://xdaforums.com/showthread.php?t=618019
[Desire Themes and Apps] Peikko:
Sorry ... I completely forgot to thank you. At least for the fonts because I did it with a Terminal Emulator like said in the Guide. :D

I love it ... it looks great.
[Desire Themes and Apps] ravi84m:
can anyone please go to ar.wikipedia.com

are arabic fonts displayed?

thanks in advance
[Desire Themes and Apps] ravi84m:
nevermind just flashed at and it worked fine.
[Desire Themes and Apps] BriEE:
Doesn't show well when there's longer text than can be displayed.
[Desire Themes and Apps] Lennyuk:
There was a thread on this last week, which provided an update.zip to do this for everyone.

Just search
[Desire Themes and Apps] BriEE:
What would the update zip do, I'm using fontchanger to swap fonts, if update zip just has newer .ttf files, I can just overwrite them.. What is new about that update?
[Captivate General] allpick:
Okay,

I traded my iPhone yesterday for the Captivate as soon as I saw I could flash to Froyo 2.2.

I configured my hosted exchange (sherweb.com) and it was pretty sluggish (unbearable to be blunt). I knew I was going to upgrade to 2.2 as I want/need tethering and mobile hot spot so I used one-click Odin and did the upgrade. It went very smoothly.

After reconfiguring for hosted exchange server access, the thing is still unbearable to use on my exchange account. In my task manager, every time I look, the process is using:

45+ MB RAM

80-90% CPU usage

Any ideas what the problem is? FYI, I'm a total newby. This is my first Android device after 2 years on the iPhone. I don't want to go back to the iPhone but this issue is a dealbreaker for me. Ugh.

Thanks!
[Captivate General] bigdessert:
Well I can tell you that I am using 2.2 with exchange 2003 and when in the mail App I show 1% cpu and 10 mb memory.
[Captivate General] ianwood:
Not sure what the particular problem is in your case but it's obviously not right. Keep in mind this Froyo ROM is a leak and it has a number of issues, exchange support being one of them. There is a replacement Email.apk from an I9000 Froyo ROM that I am using in place of the app that was in our leaked ROM. It seems to work pretty well so far. Check the threads on exchange issues with JI6 Froyo and you should find the thread on replacing the Email client.
[Captivate General] joeybear23:
I have mine syncing mail, contacts and calendar, I have it set to 30 days, and it is pointing to Exchange 2003... it is only using 13 MB memory.

I am not sure what is going on with yours. Are you still in the initial sync?
[Captivate General] allpick:
I'm using Exchange 2007. My mailbox is about 2.5GB and I was syncing 2 weeks (10kb, but even tried headers only). I had the same issue before I flashed to Froyo.

Interesting question about the initial sync. Not sure how to tell if/when the initial sync is done. It was running at high CPU usage for several hours and overnight. It is basically unusable like this.
[Captivate General] foxbat121:
The email app Samsung picks (not sure who develops it) is very slow on sync emails. If you have a lot of emails to sync, that's what you probably going to get. I never sync beyond 3 days. And I delete a lot of the emails in inbox as much as possible.

The beauty of Android is that you can try different email apps. For exchange sync, the best option is Touch Down (the UI maybe a little bit old style). There is also K9 for email only.
[Touch CDMA Android Development] SuperJMN:
I have been using the latests builds to see if they mitigate a common problem in our devices (mine is a Polaris). The insufficient memory makes it lag until forever when switching amongst applications, not only the heavy ones, but also the supposed light applications like Messaging, Phone, Contacts, etc.

The system has to work under really hard conditions: 20 - 28 MB when starting up. Every application I run is a fire proof. Applications like Navigation makes our devices literally crawl and bite the dust. Not far away, I was driving and tried to play some music at the same time. It was impossible. The waiting was unbearable and it finally hung like a pro.

My question is: is there any chance to free up memory or use it more efficiently in order to avoid these undesirable situations?
[Touch CDMA Android Development] mrkite38:
Did polaris get back some memory with Froyo kernel like vogue did? From the video buffer or something... what res do you run at?
[Touch CDMA Android Development] SuperJMN:
I'm running at 240x320 - 120 dpi

I made a screenshot of a "free" command in a terminal (see attachment image).

My kernel is this one (converted with Atools):

http://androidhtc.git.sourceforge.n...=2.6.32/VOGUIMG-320-FROYO-10-4-10.NBH;hb=HEAD

Thanks for your interest!
[Touch CDMA Android Development] dertester123:
Im not sure.. but is there a way to use the sd as ram?

I think its not fast enough, but i havent seen any "benchmarks" yet how fast the ram on the polaris works.

Maby its slower but fast enough to work as swap etc?
[Touch CDMA Android Development] n2rjt:
Enabling compcache will help you.

Still, our little devices cannot multitask very well with Android, but I can navigate and play music at the same time, with compcache.

You will need drivers that match your kernel, in /system/lib/modules. I have packaged some in the first post of this thread that should work for each of the two popular kernel versions.
[Touch CDMA Android Development] SuperJMN:
Alright, I'm downloading the modules for 2.6.32. After applying the update, what should I do to enable compcache? Some time ago, this setting was in Spare Parts.
[Touch CDMA Android Development] -Arturo-:
Open terminal

type: Su

and then

compcache.sh enable
[Touch CDMA Android Development] margosmark:
any way to confirm that it worked?
[Touch CDMA Android Development] -Arturo-:
type FREE in terminal and look under swap if it shows zero then it's not active.
[Touch CDMA Android Development] jamezelle:
yea, try doing free from a terminal you should have an amount of memory for the swap row
[Touch CDMA Android Development] manu33xtro:
For testing...

Thank you SuperJMN for this thread : I hope this help us for better use of our phone.

Like you, when I try to use my GPS navigation (Navigon or Igo8) I'm bored that's too slow !! Impossible to change anything if I want...

I try now with Compcache enable, I can see 130024 (total and 104156 used) instead of 104024 : swap = 26000 :)

Cheers.
[Touch CDMA Android Development] jamezelle:
any better luck with comcache on??
[Touch CDMA Android Development] SuperJMN:
Report

I installed this update for my .32 kernel (dated September, the 30th):

http://xdaforums.com/attachment.php?attachmentid=409422&d=1285714954

My build is the latest: http://sourceforge.net/projects/androidhtc/files/system-froyo-01-10-10_16.tgz/download

When I open a terminal and type

su

compcache.sh enable

it states that compcache will be enable in 120 seconds.

After that time, a free command doesn't reveal any change.

I've also tried typing

su

compcache.sh start

When doing this, it processes the command and after 30 seconds or so, some lines are displayed:

insmod: can't insert '/system/lib/modules/lzo_compress.ko': File exist
insmod: can't insert '/system/lib/modules/lzo_decompress.ko': File exist
insmod: can't insert '/system/lib/modules/ramzswap_compress.ko': File exist
swapon: /dev/block/ramzswap0: Function not implemented
vm.swappiness = 30

After that, a free command doesn't reveal any change, too.
[Touch CDMA Android Development] -Arturo-:
Try this one

http://dl.dropbox.com/u/7688082/androidupdate.tar

Also is terminal added to the white list in super user app.?
[Touch CDMA Android Development] l1q1d:
Try with this update...
[Touch CDMA Android Development] SuperJMN:
It worked! Thanks!

By the way, the touchscreen behaves erratically with 4-oct NBH. Test with calibration app and tap the screen. You will notice abrupt lines.

Edit: if you want to see which behavior I'm referring to, watch this video: http://www.youtube.com/watch?v=DPLu41BUB1Y

It happened sometime in the past, but with this one it happens the same (although the abruptness is not as much as in this video).

Edit 2: Strangely enough, it is fixed on reboot, but after some time running the touchscreen starts to behave crappy again. It happens with the newest .NBHs made in October.
[Desire Q&A, Help & Troubleshooting] quimpires:
Why APP2SD don't work on my desire rooted and alpharev stock rom?

Any one can explain that? Thanks
[Desire Q&A, Help & Troubleshooting] EddyOS:
Which A2SD? The stock A2SD in the stock ROM will only allow moving of apps if enabled by the developer. If you want ALL A2SD then you'll need a custom ROM
[Desire Q&A, Help & Troubleshooting] mortenmhp:
Yes what kind of a2sd(froyo native or custom) and what have you tried to make it work?
[Desire Q&A, Help & Troubleshooting] quimpires:
I try APP2SD, but it only moves some apps. The same way with unrooted. :-( I think that I'm loosing something
[Desire Q&A, Help & Troubleshooting] quimpires:
I'll try a2sdfroyo from market, but need busybox, but what I found on the market says it is not compatible with the desire. Damm

Where I can find busybox, that works on desire?