yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
So alot of people have been having problems with the emulated folders... Where it all you're data is in "0" on top of "0" folders. And I have a fix. Just trying to help out the community.

Fix [1] :

- Download & Install GooManager from the Play Store.

- Open app, click menu and select "Install OpenRecovery" and let it download and install.

All it does is its updating TWRP.

If you have CWM, stay away.

Fix [2] :

If above doesn't work, than follow along...

- Move all the files in the "0" folder and put them on the root of SD card. And delete the "0" folder after placing all files onto root of SD card.

Sorry if its a bad help, im in a rush. I will update this soon. When I have time.

Fix [2] ; will work for CWM. Just not Fix [1] …

If above doesn't work than you're gonna have to format SD card. Make sure to backup if you do that.

Current ROM: Illusion v2.0.

Kernel: BMS. (Latest Version)

Hit the thanks button if I helped. [:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Mine. (: :thumbup:

Current ROM: Illusion v2.0.

Kernel: BMS. (Latest Version)

Hit the thanks button if I helped. [:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BenzE420:
Tried several times. Each time I get the message "unfortunately, Goo Manager has stopped."
[LG Optimus 2x] alex20877:
I think the Headline says everything. I want to know which ebook reader app do you use?

I love the nexus 4 reader app, but don't know the name?

Thank you... :)
[LG Optimus 2x] sprockboy:
I tried every single reader on the Play Store, because I read a lot... And IMHO the best in terms of functionality is Fabrik because it links and synchronizes my dropbox ebook folder with my laptop, pc and tablet. It's quite useful because I have my library stored in dropbox and it also saves bookmarks between devices. I can't deny that Moon Reader and Aldiko shelves are eyecandy and full of options. But I consider Fabrik is simple, elegant. It also works with Google Drive.
[LG Optimus 2x] dev>null:
Moon reader

I like Moon Reader+ but I'll try Fabrik after reading the previous post :laugh:

yes... Fabrik definitely looks clean and functional !!!
[LG Optimus 2x] Litderose:
I'm using Aldiko (see here).

I like it : simple and efficient.
[LG Optimus 2x] alex20877:
Perfect...i will try the apps. The Fabrik seems to be very nice cause of cloud sync.

The Aldiko is in some days the next that i´m going to try...thank you everybody :)
[MDA, XDA, 1010 Software Upgrading] animelover:
It is possible to upgrade the RAM at a HTC Wallaby, specialized the MDA I? When it is possible, can I do it on it by myself? I'm not really happy with 64 MB and want to have about 128 MB! By the way: NO, I haven't enough money for a new HTC Himalaya or BlueAngel (but if can anyone sell me one of these I will be very happy :D)!

Thanks in advance

animelover
[MDA, XDA, 1010 Software Upgrading] dabtran:
www.pocketpctechs.com
[HTC One X] Ali_Nabaa:
I am running SlimBean 4.2.2 build 7 on my HOX

I remembered earlier this morning that I used to have FM radio on my HOX (before I flashed SlimBean)

I looked around and saw that I should place a "fmradio.apk" and "htcradioservice.apk" in /system/app and change their permissions to rw-r-r

I tried that, and I could see the FM radio icon. However, whenever I try to launch the app. It force quits....it crashes...

Here's a logcat:

pastebin.com/A3sv9Z39

Is there anyway to get FM radio to work ?
[HTC One X] robchongke:
sense fm radio will not work on non sense rom.
[Xoom Q&A, Help & Troubleshooting] tech.arthur:
Dear all,

If you haven't updated it, don't do it.

My situation now is:

1. It stucks at the red dual core logo; (I think it shouldn't be called a boot loop)

2. It can't be powered down; (even I press and hold the power button forever!)

3. If I reboot it, I can still press the -vol button to choose between modes, but there are one 3: NvFlash; RSD; and fastboot. No "android recovery" option.

As of now, I put it into Nvflash mode so that the screen will not keep shining with the red logo.

May anyone suggest how I could unbrick it, or the worst case, reinstall everthing to stock?

Thanks very much for your help!
[Xoom Q&A, Help & Troubleshooting] tumpy:
Back to stock is best, For a pure 4.2 JB hassle free try links..

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

http://xdaforums.com/showthread.php?t=1999897
[Xoom Q&A, Help & Troubleshooting] tech.arthur:
Thanks for your reply. But seems that the post doesn't teach me how I could restore it to that stock given my situations?
[Xoom Q&A, Help & Troubleshooting] Asphyx:
If you lost recovery then you need to ADB into the unit to force it into recovery (if you don't know what I'm talking about get a friend who does).

In either case you will need to have the developer tools installed on a computer and connect via USB to be able to flash Stock Rom via fastboot.
[Xoom Q&A, Help & Troubleshooting] phuongnt:
Back to EOS4 203 build!
[Xoom Q&A, Help & Troubleshooting] tech.arthur:
Dear Guys,

Thanks you for your opinions.

1. I would like to flash back to 203. Would any one care to give me some step by step guides how to do that, given my situation, being stucked at the start up and couldn't go into recovery?

2. If I have a friend who is so technically superb, I wouldn't have to come up here to ask for help. As I always think here is where the genius gather.

Looking forward to a solution. Thanks again for all of you who cares.
[Xoom Q&A, Help & Troubleshooting] paultbear:
re-install earlier ROM

Try the power + vol up +vol down reboot... this should get you to a bootloader screen, from there you can select recovery and that should allow you to re-install the 203 nightly. BTW... the problem was noted in the developer forum soon after the 204/205 file were posted.

ADVICE:: you might want to review any files in the forum before jumping on any upgrade.

if the above doesn't work then try -

Re-install your recovery - using the same steps that originally were used to root and install a recovery.

You may have to use ADB to push the files out to the device. (do a search for adb in this forum, or perhaps root kit)

With this it should be simple to recover.

I was fortunate that I was able to return to recovery and install 203 with no issues other than a anxious moments wondering what I did wrong :confused:

hope this helps
[Sony Xperia P, U, Sola, Go] pedromms86:
Now that the sources for Xperia's models are released, some dev could make a CM7 Port, i now its a GB rom, but definety will be fast and stable, and in my opinion will be the best rom for ur device.
[Sony Xperia P, U, Sola, Go] dexxda:
many projects cm7 for XU dead, im think same

+1
[Sony Xperia P, U, Sola, Go] percy_g2:
I will try it on xperia p first ,then later on I will add the support for sola,u and go .
[Sony Xperia P, U, Sola, Go] Ben36:
This is definitely needed on the U. A nice freshly compiled from source cm7 with everything working would be awesome
[Sony Xperia P, U, Sola, Go] aca89:
I have to say +1 :)

CM7 would be perfect for XU for example. Please at least try to build it. Thank you.
[Sony Xperia P, U, Sola, Go] dexxda:
Look this: http://xdaforums.com/showthread.php?t=2163595

maybe this help you to porting xperia u and p and sola :)
[Sony Xperia P, U, Sola, Go] ajain3982:
cm7

Dat would be awesome....!!

Really would be nice to have cm7 on our device....!!

Btw does anyone has the guide to make it....or else just post a link here...i m excited to make one...:p:D

we can team up..!! :P
[Sony Xperia P, U, Sola, Go] optimustrip:
That would be great, CM7 would have best performance with lot of free RAM.
[Sony Xperia P, U, Sola, Go] GEKTHEBOSS:
Afaik we cant do that because we dont have a gb device tree....

Inviato dal mio Nexus 4 con Tapatalk 2
[Sony Xperia P, U, Sola, Go] ajain3982:
Byw has sony released the sources for jb on xperia u..??

Coz I found an open source archive for build no 6.2.A.1.100...:o
[Sony Xperia P, U, Sola, Go] ale467:
CM7 is needed. That's the best for U
[Sony Xperia P, U, Sola, Go] aca89:
Has anything changed on this topic? Is someone maybe able to build cm7?
[Sony Xperia P, U, Sola, Go] GEKTHEBOSS:
We CANT build cm7 for xperia u...we can only pick stock gb and adding al features but all want jb and now kitkat
[Galaxy S III Mini Q&A, Help & Troubleshooting] htruempler:
:confused:Hi together, before i try to use a "last exit" by buying me an "Unbrick - JTAG", i thought if one could may help me, it will be found here or nowhere.

I started with a new S3 Mini (Telekom Branding Android 4.1.2 Germany). Using the SAMSUNG GALAXY S3 MINI TOOLKIT Pro, (mskip) i rooted it and flashed also the CMW Recovery. Within the CMW Recovery i made a Backup before i flashed a CUSTOM-ROM ( "enox reVenge one" ROM ).

Flashing went trough without Errors, afterwards i did a "wipe factory reset", a "wipe cache" and a "wipe dalvik cache". Then after a reboot the "disaster" was there with a permanent bootloop (Samsung starting Screen with model, etc.) and i couldn´t get into Recovery mode anymore. As i found out, the Download mode still worked and i could still flash using ODIN. So i studied some articles here and i followed procedures to re install a common Stock-Rom together with a PIT file for the I8190N (! found also her specific for the "N" option). The flashes went trough without errors, but unfortunately without positive effects to come over the bootloop. I read some articles about ADB, i downloaded the Android SDK, and tried to use some shell commands to get into recovery mode with no success, because i got allways the message "device not found". Within the SDK package also the USB Drivers were installed and when i connected the S3 via USB, Drivers were installed under "WXP" without any errors (I use WXP instead of W7 or W8 which i have also available). At a certain time i recognised that the SAMSUNG GALAXY S3 MINI TOOLKIT Pro, give me an ADB environment just on a selectable menuelevel, which can be used more comfortable as the native ADB environment. I recognised that i could use there just a function like "reboot in recovery mode".

The problem just ist, that of coarse also there the "device not found" problem is just the same (same Environment on Laptop). I just have any idee anymore what to do, and either i can solve the problem finaly here with your support (maybe something else could be tried out using ODIN flashing), or i take the last exit "and buy me the mentioned Unbrick - JTAG.

Instead of this i would more like to buy you a beer or to donate for a beer for someone of you.

We will see what happens, anyway my best wishes to you. :confused:
[Galaxy S III Mini Q&A, Help & Troubleshooting] samersh72:
reflash the firmware (make sure that it is the right firmware for your variant) with pit file.

if you stuck in bootloop, flash param file with odin http://xdaforums.com/attachment.php?attachmentid=1937012&d=1367738404 (it works also for N)
[Galaxy S III Mini Q&A, Help & Troubleshooting] htruempler:
Unfortunately no success

Did it as recommended with no success, files used within flashing:

First ODIN Flash,

I8190NXXAMD3_I8190NOXAAMD3_DBT.zip

i8190N_goldenxx.pit

Second ODIN Flash,

PARAM_I8190.tar.md5

The loop still remains. here the logs (copied in one file) from ODIN (two separate runs):

<ID:0/015> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> I8190XXAMB3_I8190DTMAMB1_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/015> Odin v.3 engine (ID:15)..

<ID:0/015> File analysis..

<ID:0/015> SetupConnection..

<ID:0/015> Initialzation..

<ID:0/015> Set PIT file..

<ID:0/015> DO NOT TURN OFF TARGET!!

<ID:0/015> Get PIT for mapping..

<ID:0/015> Firmware update start..

<ID:0/015> boot.img

<ID:0/015> NAND Write Start!!

<ID:0/015> STE_boot1.img

<ID:0/015> STE_boot2.img

<ID:0/015> modem.bin

<ID:0/015> system.img

<ID:0/015> cache.img

<ID:0/015> hidden.img

<ID:0/015> RQT_CLOSE !!

<ID:0/015> RES OK !!

<ID:0/015> Removed!!

<ID:0/015> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

New Start of ODIN as Admin

<ID:0/015> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> PARAM_I8190.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/015> Odin v.3 engine (ID:15)..

<ID:0/015> File analysis..

<ID:0/015> SetupConnection..

<ID:0/015> Initialzation..

<ID:0/015> Get PIT for mapping..

<ID:0/015> Firmware update start..

<ID:0/015> param.lfs

<ID:0/015> NAND Write Start!!

<ID:0/015> RQT_CLOSE !!

<ID:0/015> RES OK !!

<ID:0/015> Removed!!

K.r. Heinz :crying:
[Galaxy S III Mini Q&A, Help & Troubleshooting] serophia:
Try reflashing param as .tar not .tar.md5
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
md5 is valid so I don't think there would be any difference except from removed security from flashing bad files.

Try to first flash stock recovery then firmware.

Stock recovery
[Galaxy S III Mini Q&A, Help & Troubleshooting] htruempler:
Still no change in Bootloop

Hi, thanks to all of you for your participation and supporting me :good:

Well, did it as recommended, unfortunately still no success.

Three flash runs, first, stock recovery, then Firmware. checking if successfull, bad result. Third flash again param, bad result.

Still bootloop, no opportunity to launch recovery.

First Flash Stock Recovery Log of ODIN:

<ID:0/015> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> I8190_stock-recovery.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/015> Odin v.3 engine (ID:15)..

<ID:0/015> File analysis..

<ID:0/015> SetupConnection..

<ID:0/015> Initialzation..

<ID:0/015> Get PIT for mapping..

<ID:0/015> Firmware update start..

<ID:0/015> recovery.img

<ID:0/015> NAND Write Start!!

<ID:0/015> RQT_CLOSE !!

<ID:0/015> RES OK !!

<ID:0/015> Removed!!

<ID:0/015> Removed!!

<ID:0/015> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

Second Flash Firmware

<ID:0/015> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> I8190XXAMB3_I8190DTMAMB1_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/015> Odin v.3 engine (ID:15)..

<ID:0/015> File analysis..

<ID:0/015> SetupConnection..

<ID:0/015> Initialzation..

<ID:0/015> Get PIT for mapping..

<ID:0/015> Firmware update start..

<ID:0/015> boot.img

<ID:0/015> NAND Write Start!!

<ID:0/015> STE_boot1.img

<ID:0/015> STE_boot2.img

<ID:0/015> modem.bin

<ID:0/015> system.img

<ID:0/015> cache.img

<ID:0/015> hidden.img

<ID:0/015> RQT_CLOSE !!

<ID:0/015> RES OK !!

<ID:0/015> Removed!!

<ID:0/015> Removed!!

<ID:0/015> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

Third Flash PARAM

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> PARAM_I8190.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/015> Added!!

<ID:0/015> Odin v.3 engine (ID:15)..

<ID:0/015> File analysis..

<ID:0/015> SetupConnection..

<ID:0/015> Initialzation..

<ID:0/015> Get PIT for mapping..

<ID:0/015> Firmware update start..

<ID:0/015> param.lfs

<ID:0/015> NAND Write Start!!

<ID:0/015> RQT_CLOSE !!

<ID:0/015> RES OK !!

<ID:0/015> Removed!!

<ID:0/015> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

K.r. Heinz :crying::crying:
[Galaxy S III Mini Q&A, Help & Troubleshooting] samersh72:
if you can not boot into recovery to wipe, flash this .tar.md5 as pda (the same for I8190 and I8190N) http://xdaforums.com/attachment.php?attachmentid=1540051&d=1354753346
[Galaxy S III Mini Q&A, Help & Troubleshooting] htruempler:
No success, Bootloop remains

Many thanks, but no success. I have the impression it might have to do with the bootloader itself. K.r. Heinz :crying:
[Galaxy S III Mini Q&A, Help & Troubleshooting] deconectat:
Did you try the 3 button combo for recovery: http://xdaforums.com/showthread.php?t=2157105?

Start in recovery and do a factory reset after you flash a stock rom in Odin.
[Galaxy S III Mini Q&A, Help & Troubleshooting] htruempler:
Still no success

Hi, i tried the I8190.tar.md5, unfortunately without success, because i´m not sure about the effect and the battery load, i decided not to try as well the I8190 серв. укр.rar package (might be i don´t have enough battery load and within the permanent bootloop, loading doesn´t seem to work). I think i will stop at that stage with this huge amount of attemps and buy me a jtag unbrick as mentioned when i started this thread. In case somebody would know how charge the battery in this stage, i would give the I8190 серв. укр.rar a final try out. Anyway i would like to say thanks to all of you because of your participation and support to me. Great community here!!!
[Galaxy S III Mini Q&A, Help & Troubleshooting] deconectat:
Doesn't the phone charge when it's off? Try to unplug the battery, plug it back in and connect the charger.
[Galaxy S III Mini Q&A, Help & Troubleshooting] KoolKid98189:
Same here! I have TWRP recovery and it shows TeamWin splash screen for 1 second and shuts off!
[Galaxy S III Mini Q&A, Help & Troubleshooting] JackoMJ:
go to download mode and flash param.tar (search in forum).

if this isn´t successful, download This ROM (LaFleur) and follow This Instructions.

After that you can flash every ROM you like :D

I flashed a wrong script one time - nothing worked. So i did it like i described and everything worked
[Galaxy S III Mini Q&A, Help & Troubleshooting] KoolKid98189:
What's so special about the LaFleur ROM though?
[Galaxy S III Mini Q&A, Help & Troubleshooting] uvedovle:
I have the same problem and no way to make get it out of bootloop :(
[Galaxy S III Mini Q&A, Help & Troubleshooting] ImproAptoVictum:
Seems like a soft brick, nothing to worry about as of yet. Try using Unified Android Toolkit to flash stock firmware following the on screen instructions.
[Galaxy S III Mini Q&A, Help & Troubleshooting] KoolKid98189:
Discharge the battery and return it to the seller and get a replacement. This is last resort and that's what I did and got a free replacement in sacrifice of my data.
[Galaxy S III Mini Q&A, Help & Troubleshooting] razorsbk:
Thanks for the WIPE_I8190.zip

I was stuck in bootloop, and after i flashed this file in Odin as PDA, my phone works. Thanks ! :good:
[Galaxy S III Mini Q&A, Help & Troubleshooting] carlossmith71:
resolve

hi mate got one for u to try worked on mine as had same problem dowload odim 3.07 then registure on samfirmware website then look for the uk o2 stock firmware list hope this helps and u get phone back on

let me nw how u get on
[Galaxy S III Mini Q&A, Help & Troubleshooting] Thomast Kotsner:
Hello everybody. Yesterday Im trying to upgrade to my s3 mini to kitkat 4.4.4. but then my phone is on bootloop. And then I try to boot to recovery mode and wipe dalvik cache. but it still not working, and then I tried to flash again with recovery tar md5. And now after samsung logo appear, its only black screen. Can you help me?
[Galaxy S III Mini Q&A, Help & Troubleshooting] sarry86:
Thanks man, God bless you :good:
[Galaxy S III Mini Q&A, Help & Troubleshooting] mark-1978:
http://xdaforums.com/showthread.php?t=2122548 a rom here should help you. You can flash it through odin.
[Galaxy S III Mini Q&A, Help & Troubleshooting] andreizidoro:
Had the same problem today. Fixed flashing stock recovery!
[Galaxy S III Mini Q&A, Help & Troubleshooting] shailuk301:
Useful, hope that it will help me.
[Galaxy S III Mini Q&A, Help & Troubleshooting] cuzquillo:
salutes, I had that reboot problem in a samsung galaxy mini s3 I8200N, I opened the case, clean every dirty inside, but mainly it is caused by the turn on switch, I sprayied some electronic contact cleaner over it while pressing it several times. Now it turned on without rebooting, I know sooner or later I wil have to pay a technician to change that switch though...
[Galaxy S III Mini Q&A, Help & Troubleshooting] Gut47:
this made my phone's condition even worse
[Galaxy S III Mini Q&A, Help & Troubleshooting] Masleyko:
Thank you very much

Thank You very much mate .. this script helped me much

My Friend somehow managed to make fully working lineageos on his phone to be stuck in bootloop :)

No way to get into recovery but this script.

Once again Thank You
[Galaxy S III Mini Q&A, Help & Troubleshooting] spirit_of_the_ocean:
With another phone I had the problem Odin stuck at flashing recovery.img. When changing the USB Port everything was good.:)
[HTC Droid DNA] amit_sen:
[ROM][4.2.2][UNOFFICIAL] ★uXYLON v2.9.5★ | HALO | PIE | HYBRID | RIBBONS | 27-JUL

STANDARD DISCLAIMER:

The rom has been compiled from sources available from uXylon, DNA CM10.1

All credit for the ROM is the uXylon team alone. See credits sections as well.

DONT BLAME me if anything goes wrong with the device after flashing this ROM...

uXylon is a free, community built, firmware distribution of Android 4.2.2 (Jelly Bean), which is designed to increase performance, customization and reliablity over stock Android for your device.

Massive features over various of community are available in uXylon, check our listings below.

uXylon Features

HALO

PIE (Option between Slim or PA Pie)

Hardware key rebinding!

Floating Mode

Per App DPI

Ribbons

Privacy Guard

Dark UI

Breathing SMS

Random Color Toggles

Recommended Installation Steps

Coming from another Custom ROM

1. Wipe Data/Factory Reset (This does not affect your Internal/External storage)

2. Wipe Cache

3. Wipe Dalvik Cache

4. Flash uXylon zip

5. Flash JB GAPPS

6. Reboot

NOTE :-> After initial bootup install crpalmer's aosp kernel from 2nd post, Otherwise WiFi wont work.

IF you are GSM user, then flash GSMPatch v2 from Flyhalf's CM10.1 thread.

How to upgrade uXylon versions:

1. Download uXylon update

2. Flash uXylon update

3. Flash JB GAPPS

4. Wipe Cache (Optional)

5. Wipe Dalvik Cache (Optional)

6. Reboot

DOWNLOAD LINKS

uXylon ROM

Gapps

G+ Community - https://plus.google.com/communities/113055388128726029211

Changelog - https://github.com/UltimatumKang/ChangelogUKG

SOURCES

uXylon

Kernel Sources

CREDITS

- CyanogenMod

- AOKP

- Fruit N Veggies

- ParanoidAndroid

- TeamBAKED

- SlimRoms

- ChameleonOS

- ock

+ CHAD0989

+ CRPALMER

BUGS

*Since its CM10.1 based so all bugs which are present in CM10.1 will be present as well.

It will make it worthwhile if u press THANKS button and rate the thread 5 STARS.
[HTC Droid DNA] amit_sen:
Changelog

27-Jul

https://plus.google.com/102380351666725905576/posts/MGRMsCidvrg

Recommended Kernel

CRpalmer AOSP Kernel

http://d-h.st/KJM

Recomended Settings

CPU : 384- 1728

Governer : Interactive

UV -50mv across range

I/O Scheduler : CFQ

Governer Control ::

Hispeed Load : 80

Hispeed Frq : 1.4 ghz

Timer rate : 20000

Min. Sample Time : 40000

Special Mention :: pio-masaki for helping me in using prebuilt kernel

Screenshots
[HTC Droid DNA] coachcrey:
I shall flash this as soon as the download finishes!
[HTC Droid DNA] tman23:
Ecstatic!!!!!
[HTC Droid DNA] uppon2:
Good work mate! Does this have any PA features as I see it is credited?
[HTC Droid DNA] amit_sen:
Sure it does :)

HALO

PA PIE

Per app DPI

DNA | ⓣⓐⓟⓐⓣⓐⓛⓚ | TF300T
[HTC Droid DNA] tman23:
This ROM is the smoothest I've used to date :) great work man...you just made my weekend at the very least!
[HTC Droid DNA] Donut42:
This rom

This rom is fantastic. I've always wanted to use a Paranoid Android-looking rom on my HTC Droid DNA and this works incredibly well. The Bluetooth audio bug mentioned in CM10 doesn't seem to be affecting me either. However, is there a version of Skype that is compatible with this rom somewhere?
[HTC Droid DNA] Lykarsis:
The newest versions of skype don't seem to be compatible with the DNA in general, it is not a ROM problem
[HTC Droid DNA] thunderbolt33:
I'm trying to download the gapps from the OP but it's taking an awfully long time to download! Any mirrors available or should I just wait it out?
[HTC Droid DNA] uppon2:
I would have said hybrid settings rather then pa lol. I can now see more details on first post. Testing this now. Thanks again