yashsingh1/xdaforums huggingface dataset:
[Xperia Arc Themes and Apps] ferhat67_38:
one more by me

Segoe Font

Segoe Font's file DOWNLOAD
[Xperia Arc Themes and Apps] MarcSinger:
Pretty neat. You could've had the same font as bold, though, as opposed to Roboto.
[Xperia Arc Themes and Apps] katrinaismyname:
thanks!! i love b-house font :)
[Xperia Arc Themes and Apps] rod555:
thanks marc, great job!!
[Xperia Arc Themes and Apps] nedunilavan:
Awesome fonts...

MarcSinger u r g8...

Thanks for keep updating new fonts n ur hardwork...:good:
[Xperia Arc Themes and Apps] Ahmed_vip:
thank you all
[Xperia Arc Themes and Apps] tommy900210:
Hey man, may I ask how to hide the name tags on dock??
[Xperia Arc Themes and Apps] MarcSinger:
Updates, April 12, 2013...

Sorry, mates. Have been a bit busy with work and my new toy. Here's what I'd promised and an additional font.

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

AMARANTH

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

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

HELVETICA NEUE

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

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

NEUTRATEXT

-------------------------------------------------------
[Xperia Arc Themes and Apps] rezarivani:
Thank you so much for neutra and other.. Am so lucky find this thread!

Bless for you..

Just one more request please.

Pacifico and Comforta sir? :)
[Xperia Arc Themes and Apps] Killawave:
Very good job. I will test ALL the fonts. ^^

Not complicated to copy the fonts manually but the packages are easier.

Thanks.

Phone: Sony Xperia Miro (ST23i)

Kernel: Stock

ROM: Stock + Modded APK
[Xperia Arc Themes and Apps] jacksace:
thanks for the font...gonna give a try
[Xperia Arc Themes and Apps] arcdorable:
now I'm using roboto slim..

umm, is it possible to use 2 fonts at one time? for example, default font is arial, but when it comes in message, it uses times new roman... :victory:
[Xperia Arc Themes and Apps] DroidBoy22:
Fonts

sir, can you please upload veggie burger medium? i love that font. Thanks! :)
[Xperia Arc Themes and Apps] sPEADy:
Hi there,

First of all I would like to thank you for your good work. Second I want to request you if you could please make a flashable font file from this very zip file attached to this post.

Thanks.
[Xperia Arc Themes and Apps] black_shot099:
can someone work for it??

http://www.animesubscorner.com/2012/03/font-anime-bleach-naruto-fairy-tail-one.html?m=1

this font is cool . for anime lover !!

both for ics and gb thx
[Xperia Arc Themes and Apps] MarcSinger:
Sorry, mate. A lot of the glyphs are missing.
[Xperia Arc Themes and Apps] MarcSinger:
Sorry for the delayed response. Have been a bit busy of late. Here's your font.
[Xperia Arc Themes and Apps] black_shot099:
ahm . thx sir

http://www.fontspace.com/phantom-king-graphics/one-piece

Im a girl 20yrs old and really really fan of this. I hope you could work for it ..

by the way thanks . I love you .

sorry if my english is bad .
[Xperia Arc Themes and Apps] invince2:
Screenshots please
[Xperia Arc Themes and Apps] sPEADy:
Hi there big thanks for your time and effort worked like a charm......thanks again bro.:good:

Here are some screen shots.
[Xperia Arc Themes and Apps] zoytie:
help!

how to install this..?

thank you...

i downloaded rosemary...

but i dont know how to intall this?
[Xperia Arc Themes and Apps] :
Flash via recovery(cwm)
[Xperia Arc Themes and Apps] funky_mukka:
working great on UHD 4 with stock kernel
[Xperia Arc Themes and Apps] droidking777:
Nokia Sans working!

Nokia sans working perfectly on viper Xperia 5:good:
[Xperia Arc Themes and Apps] zoytie:
great job..

awesome...

rosemary font looks great on my arc s..

thank you...
[Xperia Arc Themes and Apps] gius321:
Please Tell ME...

You mention that > "make sure you take a CWM backup before you flash any of these fonts so you'd be able to recover in case you were to end up in a boot loop" so if i get bootloop can i restore backup from titanium from CWM?
[Xperia Arc Themes and Apps] saifssj6:
Help

not working on uhd 5.0 for some reason

Update:it does work..but in very few places,can the creator please look into this?using b house
[Xperia Arc Themes and Apps] chiyaanchinnu:
Your device restarts repeatedly if you ran into a boot loop. So, there is no way for Titanium so the only option left is ClockworkMod. Makes sense?

Hit "Thanks" if my post helped you, it won't hurt!!! :p
[Xperia Arc Themes and Apps] stanlin salu:
Nice font....
[Xperia Arc Themes and Apps] smileymatt:
I also use uhd 5.0 . It only appears in lock screen and in status bar, also the clock. But on others it doesn't change., ><

edit: works on play store, dialler/contacts, other apps
[Xperia Arc Themes and Apps] akashkatkar22:
Nice work

Nokia Pure
[Xperia Arc Themes and Apps] hackerkeng:
oh,that's wonderful!!
[Xperia Arc Themes and Apps] saifssj6:
hey

thanx for the great work man,really changes the experience.Can you make this work on viper xperia?really want to try out a jelly bean rom,really bored using a ics rom for such a long time.

p.s. i did make it mork on uhd 5.0 y changing the launcher to v3.5
[Xperia Arc Themes and Apps] Slick101:
Awesome :) thanks for sharing dude!
[Xperia Arc Themes and Apps] nightwing_sw:
Nice fonts,,, gotta try em out
[Xperia Arc Themes and Apps] pROAddicts:
One Piece Font

Requesting the attached font zip for Xperia on JellyBean, Please!!! I shall appreciate your effort! :D
[Galaxy S III Q&A, Help & Troubleshooting] nikctsh:
I have a double shock controller that I used for my laptop. Yesterday I bought an OTG and I tried to connect it with my S3. I ran a test on Dead Trigger, I found that only the axis controller (the up down left right control) works, others like the L1 R1 and the 4 action buttons (triangle, round...) doesn't work. So, I can only move around. Can someone tell me what actually happen, I saw on a video before that all the buttons should work, but why not with my double shock controller? Thank you!
[Desire HD Q&A, Help & Troubleshooting] jawadahmadd67:
hey guyss,, i have tried many custom roms but always find alot of bugs and battery drain issues,, i tried custom gb roms too but didn't satisfy completely,, custom roms always help you to experience new ui and new features , i salute to effort of the developers, but if you need your phone just for basic funtions not for some cool features,, then here is a method to get the best rom.

1- first install a latest official rom(stock kernel). here is the link,,, http://xdaforums.com/showthread.php?t=1382235

2- now download the rom cleaner tool and run that with any recovery and select the option rom cleaner and then no sense and choose any launcher. here is the link for rom cleaner tool ( remember rom cleaner tool is in zip file so you have to flash that zip through any recovery) ,,, http://xdaforums.com/showthread.php?t=1050283

3- download and install daemon controller,,, http://xdaforums.com/showthread.php?t=1949502

download and enjoy the fastest rom with stock kernal.

thank you.

sorry for my bad english,
[Desire HD Q&A, Help & Troubleshooting] syjan1212:
I recommend viperDHD
[Desire HD Q&A, Help & Troubleshooting] Muikkuman:
ViperDHD for sense and Codefire X for AOSP/AOKP.

sent from my Desire HD while waiting for my Nexus 4.
[Desire HD Q&A, Help & Troubleshooting] NiCk.JaY:
Please, there is no best ROM, everyone has their own preferences. Other similar threads have been closed by the moderators, I won't be surprised if this one gets closed too.
[Desire HD Q&A, Help & Troubleshooting] mobidor:
Jb 4.2.1 (cm 10.1)
[Desire HD Q&A, Help & Troubleshooting] shifted-is:
Everyone is different.

I'm running randomblame's Jelly Time R1 (soon to be R2) Jelly Bean.

Check the Dev section - usually the most popular one will tell the answer (and for newbies it's probably the best one).
[Desire HD Q&A, Help & Troubleshooting] catandroid:
I change the ROM often to get the last and best of everyone. Now I'm using Codefirex JB 4.2 and it's very good.

I prefer no SENSE ROMs.
[Desire HD Q&A, Help & Troubleshooting] serzenus:
i am on Blackout v3.2

i trimmed sense with no-sense script

and finally using w8 launcher

free ram is about 250MB

so it is fine
[Desire HD Q&A, Help & Troubleshooting] 24ky:
Sabsa Prime v12.0

Bringing Life To Droid Incredible 4g And The Almighty Vivid 4g
[Desire HD Q&A, Help & Troubleshooting] Reinaldo33897:
There is no best rom what may be great to one may be total crap to another. Only you can tell what's best for you and what you need it to do.

Only advice anyone can tell you is

1. Gingerbreads are solid.

2. ICS have minor issues though close to solid.

3. Jelly Bean also has minor issues though they are becoming solids as well.

Read the last few pages of all roms and you will get somewhat of an idea what issues users are having. This is a search and learn sight we all did it. No one will hold your hand and lead you along the way.
[Desire HD Q&A, Help & Troubleshooting] GuyInTheCorner:
Agreed, but ICS ROMs are essentially solid now.

4.1.2 ROMS are stable(ish)
[Desire HD Q&A, Help & Troubleshooting] snp88:
I use MIUI and it's work like a charm base on JB
[Desire HD Q&A, Help & Troubleshooting] alb0603:
viper DHD is amazing
[Desire HD Q&A, Help & Troubleshooting] akkiekhandelwal:
currently, jb 4.2.1 codefireX is awesome with tons of tweaks and viperDHD for sense.
[Desire HD Q&A, Help & Troubleshooting] Melobrokeit:
Its true. Everyone is different. A lot of people have moved on from this phone, including developers. Its said, but this is why I went back to iPhone 5. I still like to poke my head back in here for a look once in a while. I know this doesn't help you at all, but its midnight and i'm bored. Cheers.
[Desire HD Q&A, Help & Troubleshooting] jotha:
Thread closed

This is not a place to post because you are bored. Go to OT-Forum for that.

We do not accept "Best rom" threads, as every user makes different experiences and thos threads almost always end in either flaming or Off-Topic posting as you might see here.
[Desire Q&A, Help & Troubleshooting] aaaaaaahhhhhhhh:
I performed a search and but nothing specific to my problem!

I am looking for a program which works to unlock my HTC Desire. I did download a program which contained a few files, i've attached the picture.

The program wouldn't run because adb wasn't running. I held down shift and did a right-click and selected Open command window here, typed in adb shell which worked then ran the program by double clicking and the same message came up. Can't win!

I even went to my Three network website to request the unlocking code but it didn't recognise the imei code lol.

Cheers
[Nexus 7 Q&A, Help & Troubleshooting] warpek:
My Nexus 7 wifi tablet was working flawlessly for a few months since buying.

It was rooted, unlocked with stock android 4.2.1 and Team Win Recovery 2.3.2.1

Yesterday morning after charging all the night I saw that it was completely turned off. It didn't bother me, because it happened a couple of times before.

But this time, after I'd switched it on it hung on google color logo.

I waited half an hour but to no avail.

So at first I booted to recovery and wiped cache and the like. But the problem remained. Factory reset didn't help either.

So as a last resort I formated everything (including system).

Then I saw surprisingly in fastboot mode that lock state is: LOCKED.

I've tried to unlock it but it ended with an error:

C:\Users\Warp\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlock

...

(bootloader) erasing userdata...

(bootloader) erasing userdata done

(bootloader) erasing cache...

FAILED (remote: (Unknown error code))

finished. total time: 7.241s

After I'd pressed "yes" to the question "unlock bootloader" on tablet it was displaying text "Neither USP nor CAC patition found" in a loop.

Because there is still TWR installed and I can't wipe it out i think I've lost the guarantee.

I can see my device in fastboot mode:

C:\Users\Warp\AppData\Local\Android\android-sdk\platform-tools>fastboot getvar all

(bootloader) version-bootloader: 4.13

(bootloader) version-baseband: N/A

(bootloader) version-hardware: ER3

(bootloader) version-cdma: N/A

(bootloader) variant: grouper

(bootloader) serialno: XXXXXXXXXXXXXXXXXXXXXX

(bootloader) product: grouper

(bootloader) secure: yes

(bootloader) unlocked: no

(bootloader) uart-on: no

(bootloader) partition-size:bootloader: 0x0000000000600000

(bootloader) partition-type:bootloader: emmc

(bootloader) partition-size:recovery: 0x0000000000c00000

(bootloader) partition-type:recovery: emmc

(bootloader) partition-size:boot: 0x0000000000800000

(bootloader) partition-type:boot: emmc

(bootloader) partition-size:system: 0x0000000028a00000

(bootloader) partition-type:system: ext4

(bootloader) partition-size:cache: 0x000000001bb00000

(bootloader) partition-type:cache: ext4

(bootloader) partition-size:userdata: 0x0000000364700000

(bootloader) partition-type:userdata: ext4

all:

finished. total time: 0.193s

Is there anything left I can try?
[Nexus 7 Q&A, Help & Troubleshooting] mihahn:
AW: No way to unlock device. Is it bricked?

Have you tried reflashing stock rom? Maybe this rewrites recovery, too :)

Sent from my SK17i running Android 4.1.2
[Nexus 7 Q&A, Help & Troubleshooting] warpek:
Yes, but it can't be done because the device is locked.
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
Before you do anything drastic, realize that you still have (in TWRP) a privileged execution environment (a root shell).

That means at a minimum you have a root-privileged shell available and some tools for fooling with partitions known to the TWRP kernel.

By drastic, I mean specifically: don't overflash the recovery partition at the command line from the root shell using /sbin/flash_image. Keep "root" until you are sure that nothing else can be done.

Back in a couple minutes - booting my N7 into TWRP right now to have a look at some things.

[ Edit ] From your post I see you have fastboot drivers set up - can you connect to TWRP via ADB?
[Nexus 7 Q&A, Help & Troubleshooting] warpek:
Thank you for your reply.

Yes, I can see my device using: adb devices

adb shell also works.

[Edit] One more odd thing, when TWRP starts it asks me to enter my password. I think it's related to data encrypted partition but I've never done it for sure.
[Nexus 7 Q&A, Help & Troubleshooting] warpek:
Yes it mounts it and it is empty (besides TWRP directory). I don't have backup either but it is no problem for me. I just want to start with stock Android 4.2.1 or if it's not possible - wipe out TWRP and send nexus for repairing.

Everything went smoothly, no errors here.

I was trying to install a few roms this way, but the flashing never ends. On nexus I can see all the time: Flashing file 1 of 1 /sdcard/aokp_grouper_jb-mr1_build-1.zip

As I saw in recovery.log the problem is at the moment when filesystem is created:

C:\Users\Warp\AppData\Local\Android\android-sdk\platform-tools>adb shell cat /tmp/recovery.log

[cut]

I:Set page: 'main2'

I:Set page: 'install'

I:Set page: 'flash_confirm'

I:Set page: 'flash_zip'

I:Set page: 'flash_zip'

Installing '/sdcard/aokp_grouper_jb-mr1_build-1.zip'...

Checking for MD5 file...

Skipping MD5 check: no MD5 file found.

Creating filesystem with parameters:

Size: 681574400

Block size: 4096

Blocks per group: 32768

Inodes per group: 6944

Inode size: 256

Journal blocks: 2600

Label:

Blocks: 166400

Block groups: 6

Reserved block group size: 47

Created filesystem with 11/41664 inodes and 5415/166400 blocks

and it stops here.

Ok, done. I've checked they are identical.

Great I'm waiting impatiently.

Regards
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
Arrgh - you never made any backups?. I was hoping you had a TWRP backup - they are just tar files, so you can manually untar them into mounted partitions at the command line... and that way see if any errors occur on an individual partition you are working with. But I'll come back to this in a little bit.

OK, got it.

Well, 650 MB (=681574400 bytes) is the /system partition, and the "Created filesystem" message probably indicates success with a mke2fs operation. But mke2fs does not wipe all the blocks, so it is still possible that the *restore to /system* operation is hanging on a media failure.

Just out of curiosity, do you get a md5sum of 3039dc3a07a56d0392d48787e4a202a1 for your part5.img and part8.img files? In principle, yours should not be identical to mine - especially if there is something unusual in the BCB (Boot Control Block), but there is a chance they are the same as these partitions seem to contain multiple backups of partitioning information. (My N7 appears to have been made in December)

OK, lets try something innocuous - raw read tests on all of your partitions. Let's see if you have a bunch of bad pages in one partition.

With TWRP running

C:\foo> adb shell

# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0boot0

# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0boot1

# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0p1

# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0p2

# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0p3

# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0p4

# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0p5

# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0p6

# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0p7

# dd of=/dev/null bs=4096 if=/dev/block/mmcblk0p8

These should all go through pretty quickly - I omitted the /data partition (p9) because it is huge. The next largest (system/p3) should take about 20 seconds for a successful raw read. If you get a read failure, repeat the command on the offending partition with the "conv=noerror" option, as in

dd of=/dev/null bs=4096 conv=noerror if=/dev/block/mmcblk0p8

Basically I'm just looking for you to narrow down the search to a problem partition. The next step is to try to manually unpack files into /system, /cache, and /data to see if there is a flash media problem in one of those partitions. Unfortunately, this is where TWRP backup files would have been useful: ROM files are not useful for this, and the google factory images e.g. nakasi-jop40d-factory-6ac58a1a.tgz contain image files which are not archives - they are "sparse ext4 images".

Even though you observed no failures with the mke2fs operations, you might want to also try to repeat that process (only for p3, p4, and p9 !) , but this time using the partition erase command first.

# /sbin/erase_image /dev/block/mmcblk0pN

prior to the mke2fs operation.

OK, standing by.
[Nexus 7 Q&A, Help & Troubleshooting] warpek:
I always do, but I though that because there are no important files for me on the nexus and everything else can be downloaded (system image, twrp) there is no need. Obviously I was mistaken.

I used md5sum to co compare those files, here is mine:

part5.img 59071590099d21dd439896592338bf95

part8.img 59071590099d21dd439896592338bf95

Everything looks ok here. No errors and no long time reads.

Is there anything I can I do then?

Ok, done, still no errors.

I've also tried writing test using dd if=/dev/zero of=/dev/block/partition bs=4096 (for partition p3 and p4) and again without any errors.
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
Hmmmm. I did a little more looking at my own misc partition images, and they each contain 64 repeated (and identical!) blocks of information that are 1280 bytes long - a group of 8 (at minor offsets of 0x4000, 0x5000, 0x6000, 0x7000, 0xc000, 0xd000, 0xe000, 0xf000) that repeat 8 times every 64kB (major offset of 0x10000). If you want to attach one of your misc partition images, I can have a look at it for comparison (it is small - 512 kB, and should not contain any private data). Wait, I just realized: I have a 32GB WiFi N7 - is yours a 16GB?

I could shove a (near stock) boot.img and system.img backup from TWRP someplace, but the system image is huge. I don't have a convenient place to drop it - got any suggestions? In principle - barring any other errors - that should boot correctly so long as the ext4 filesystems on /data and /cache are intact and operating correctly.

Barring a tar or other archive file which we could unpack directly into (mounted) /system, that was going to be my next suggestion. Rats.

Maybe it is time to try the read/write tests with the /data partition?

Actually, before you do that, what were the dump lengths you got for each of your partitions? Here are mine (using bs=4096):

/dev/block/mmcblk0boot0 512 ( 2097152 bytes - 2.0MB)
/dev/block/mmcblk0boot1 512 ( 2097152 bytes - 2.0MB)

/dev/block/mmcblk0p1 3072 ( 12582912 bytes - 12.0MB) recovery
/dev/block/mmcblk0p2 2048 ( 8388608 bytes - 8.0MB) boot
/dev/block/mmcblk0p3 166400 (681574400 bytes - 650.0MB) system
/dev/block/mmcblk0p4 113408 (464519168 bytes - 443.0MB) cache
/dev/block/mmcblk0p5 128 ( 524288 bytes - 512kB) misc1?
/dev/block/mmcblk0p6 2560 ( 10485760 bytes - 10.0MB) -WTF?- "staging?"
/dev/block/mmcblk0p7 1280 ( 5242880 bytes - 5.0MB) mfg
/dev/block/mmcblk0p8 128 ( 524288 bytes - 512kB) misc2?
/dev/block/mmcblk0p9 ?? ( ?? bytes - ??MB) data

Note I didn't do my /data partition - I have a 32GB N7, so I suppose that means that /data is 30+ GB in size. Lazy and didn't want to wait.

---------- Post added at 01:40 PM ---------- Previous post was at 12:55 PM ----------

FYI,

shoving some TWRP backup images (system, boot) to my dropbox right now. Lightly-rooted stock. (Added su and SuperSu in /system, and altered default.prop in the boot image so that the secure flag is disabled and the adb daemon starts up straight away). Other than those changes, 100% stock, including kernel.

I'll send a PM when I figure out how Dropbox works.
[Nexus 7 Q&A, Help & Troubleshooting] warpek:
Yes, I've got 16GB version.

I can create ftp account on and send you login data in a private message. Will it be convenient for you?

Yea, but ... now something really strange happened.

All partitions have disappeared. _I'm sure_ that I didn't zeroed the whole mmcblk0 device. Just the partition I mentioned before.

ls /dev/block
loop0 loop2 loop4 loop6 mmcblk0 mmcblk0bo
loop1 loop3 loop5 loop7 mmcblk0boot0 platform

fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 15.7 GB, 15762194432 bytes
4 heads, 16 sectors/track, 481024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0 doesn't contain a valid partition table

TWRP still starts but it takes more time.

I don't have partition table now so I it is useless. But for the future use, can you tell me please how I can see this kind of dump?

Edit: I'd be grateful if anyone having Nexus 7 16GB paste output of command:

adb shell /sbin/fdisk -l /dev/block/mmcblk0

I hope I will be able to create proper partitions on my device then.

But I'm afraid of using fdisk to create partitions because this can lead to destroy current recovery which still starts.