yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] mopartonyg:
downloading now,will report back in the am. Thanks
[HTC Droid DNA] amit_sen:
Running very good bro. Loving it :thumbup:

Using xposed module for button remap.

DNA | ⓣⓐⓟⓐⓣⓐⓛⓚ | TF300T
[HTC Droid DNA] walther1337:
Is anyone else losing wifi and data when dirty flashing from the 10/14 build?
[HTC Droid DNA] mopartonyg:
I agree completely with Amit. used Aokp on my droid X and loved it. Great job thank you
[HTC Droid DNA] TheDanimal:
I always clean flash. Titanium backup works fine with this build. It pops up a message about the binary but it works.
[HTC Droid DNA] jwhood:
Can i use this on gsm??

Sent from......
[HTC Droid DNA] walther1337:
Updating the su binary seems to fix the issue with TB. If I've got time tonight I'll clean flash and let you know if I run into any bugs.
[HTC Droid DNA] TheDanimal:
I'm not 100% sure, sorry. Has anyone tested Bluetooth audio? I haven't had a chance to test it yet and I haven't been following cm development lately to see if it's been 100% fixed yet

Edit: it works
[HTC Droid DNA] TheDanimal:
Has anyone seen SU issues? I was able to run titanium backup fine this time around.
[HTC Droid DNA] walther1337:
I got a message about SU in TB that said the binary might not work, but I had no issues with root access in any apps. Is there any way of changing the timeout for active display? It seems pretty short.

EDIT: Has anyone seen any effects on battery life with pocket mode enabled?
[HTC Droid DNA] TheDanimal:
Not that I've seen.
[HTC Droid DNA] MSmithXDA:
All the Gapps download links on the AOKP site are dead. Does anyone have the true download link?
[HTC Droid DNA] walther1337:
I've been using the mirror in the official CM thread because goo.im says the file is missing.

EDIT: Goo.im gapps are back up.
[HTC Droid DNA] MSmithXDA:
Installed this Rom on Friday and love it! Excellent job with the port. I did encounter a few issues which I wanted to report. Despite the issues, I think I'll be keeping it as my daily driver for a bit, and possibly forever if they could get fixed. Great job!

1) Phone Dialer crashes often when a call ends. I think it might have to do with orientation (i.e. being in landscape when a call ends), because if I use the app "Set Orientation" and allow it to go into Landscape, then the phone dialer can't even start...it'll crash every time. Had to stop using the app because of it, which kind of stinks because I have a car dock. The crashing wasn't present on other roms though.

2) Bluetooth Audio gets choppy. It'll frequently cut out for a few milliseconds and also sound a little garbled at times.

3) BeatsAudio isn't present. Not sure if it can be added, but you can hear the absence of it (flat and little tinny). GPE rom has it so maybe it can be pulled from there?

4) When I first installed PlayStore had some trouble downloading apps. Then it corrected itself about 10 minutes later. After installing 20 or so apps, it could no longer download any apps at all and always error'ed out. Had to wipe cache and dalvik cache to correct it, which it did. Works fine now.

Thanks again! Great job!
[HTC Droid DNA] walther1337:
1) I haven't had any issues with the dialer. It doesn't rotate to landscape, so trying to force it to will only cause issues.

2) Until Bluetooth is fixed on CM, don't expect it to work on any AOSP based ROM.

3) Audio sounds far better than with beats audio. If you want beats, go to a Sense ROM.

4) Make sure your on the right gapps. I haven't had any problems with the play store.
[HTC Droid DNA] MSmithXDA:
It does rotate successfully on other roms. But that's an aside point anyway. Even if I don't use the app Set Rotation, dialer still crashes at the end of every phone call.

Bummer

My point here was that it's on the GPE rom, which is just Stock Android + Beats Audio (no Sense), so I mentioned it with the possibility that it could be easily pulled (trying to pull it from a Sense rom would be much harder).

But, I'm curious to your statement about it sounding far better. The first thing I noticed when playing a song was how the low end was missing and there was no power behind it. That's what caused me to look for Beats Audio and see it was missing. Do you have some equalizer you're using to make it sound better?

Used the one linked to from the AOKP site. Problem went away after doing a wipe of Cache and Dalvik Cache anyway, but just worth mentioning. I did do a wipe after the initial flash, but this occurred anyway.

---------- Post added at 09:21 AM ---------- Previous post was at 09:14 AM ----------

How do you get the three dot menu to appear? I've been messing with the AOKP settings regarding the 3 dot menu, but I can't get it to appear. The only way I can get it to show up is to enable the entire navigation bar, which includes Home, Back, and Recent Apps, but since we have capacitive buttons, that's redundant.

I'm sure it's just a settings thing, but not sure what the right setting is. Any idea?
[HTC Droid DNA] TheDanimal:
In ROM control under general UI
[HTC Droid DNA] walther1337:
I could be wrong, but I think GPE uses the Sense kernel. I don't use any equalizer, just good quality music and a set of great headphones.

To enable the 3-dot menu: settings > rom control > show menu ui overflow

EDIT: Quality here meaning high bit rate, ie 320kb/s
[HTC Droid DNA] MSmithXDA:
That's checked for me (tried it both checked and unchecked), but no menu for me. The only way I can get it to appear is to enable the entire navigation bar. That could be an AOKP bug though and not a bug of this particular rom.

---------- Post added at 08:20 AM ---------- Previous post was at 08:18 AM ----------

Received a PM from mrlolli regarding the dialer crashing. I'll give his suggestion a shot but thought I'd post it here for others:
[HTC Droid DNA] skynet11:
Do you think you'll be able to post a KitKat build for the DNA whenever AOKP releases one? I'm still running one of the 4.3 builds because I'm still partial to AOKP and I like my customizable navbar too much to jump to 4.4 yet.
[HTC Droid DNA] TheDanimal:
I won't be making anymore DNA builds because my son dropped and broke my DNA. I have the LG G2 now.
[HTC Droid DNA] spaziod:
we thank you for all your hard work...Merry Christmas!
[HTC Droid DNA] TheDanimal:
Merry Christmas to you too. I still have the AOKP source so I might try to make a build when they move to 4.4
[HTC Droid DNA] skynet11:
Edit: nvm
[HTC Droid DNA] jamiethemorris:
4.4 is out. I'm working on an aokp build right now, i don't really know what I'm doing though. I've never built a ROM for an unsupported device

[MENTION=3052863]skynet11[/MENTION] you know there's exposed modules for that right? I think gravitybox and blast tools both have it. I don't know if they're as good as the aokp one though.
[HTC Droid DNA] tdizzle404:
Really looking forward to for some unicorn love! lol

Been waiting forever for the 4.4 merge :good:
[HTC Droid DNA] jamiethemorris:
I think it's the same story as other kitkat ROMs, meaning they're more or less starting from scratch. But still... It's aokp.

---------- Post added at 12:53 AM ---------- Previous post was at 12:51 AM ----------

Just an update on the 4.4 build... It was building fine for a while, looked like it was almost done, but it ran into this:

Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/run/media/jamiethemorris/LinuxExternal/android/aokp_kk/kernel/htc/m7'
build/core/tasks/kernel.mk:161: recipe for target 'TARGET_KERNEL_BINARIES' failed
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
target StaticLib: libc (/run/media/jamiethemorris/LinuxExternal/android/aokp_kk/out/target/product/dlx/obj/STATIC_LIBRARIES/libc_intermediates/libc.a)

I'm going to be in Oregon until the 30th, but I'm going to try and figure it out after I get back.
[HTC Droid DNA] danjull:
What kernel source are you using? Looks like you had ways to go though, if it was still compiling from the kernel dir.
[HTC Droid DNA] jamiethemorris:
I'm not sure, I've never done this before. I just put the cm11 dlx device tree and vendor tree files in the correct places and made dlx.mk in vendor/aokp from m7vzw.mk. There also may have been some files I still need to get from the cm source. I was kind of confused cause I didn't see any way to point it to the kernel source, but it looks like it tried to use the m7 one anyway, which from what I can tell has been kept up to date with cm.
[HTC Droid DNA] danjull:
boardconfig.mk in device/htc/dlx points to the kernel. It should be the m7 kernel. AOKP's m7 kernel looks to be a little behind CM's though. Might want to remove it and try git cloning the CM M7 kernel and use it instead.
[HTC Droid DNA] danjull:
Had to be the kernel. Pooped this one out with very little modifying. Let me know of you need the stuff to get it going.
[HTC Droid DNA] zawata:
Your building AOKP?

Im sorry I didn't realize that, I'm syncing it right now to build

I just build slimkat and I figured AOKP wasn't here yet so I would do it

Are you planning to release it when you finish?
[HTC Droid DNA] jamiethemorris:
I wasn't sure yet, but go for it. I'm mostly just trying to learn. If it build and boots properly, let me know what you did. You can go ahead and build aokp I think I'll go for PA
[HTC Droid DNA] danjull:
I got a working build. Not planning on maintaining it though if anyone needs any pointers.
[HTC Droid DNA] zawata:
Yeah i did the same thing with slimkat

If youre really not getting anything to work, i can probably help you through it

Alright that's good to know

I probably will get it in the first few tries

Got all my building noobness out through slimkat(go check amit's 4.3 slimbean thread for proof haha)
[HTC Droid DNA] danjull:
It's pretty straight forward. The only thing aokp has that differs from cm is the products folder in vendor/aokp. All I did was not using the aokp m7 kernel, just used the one from cm's git. Add the dlx.mk in the vendor product folder, which is basically cm.mk from the device tree. Look at the m7vzw. Add dlx to the vendorsetup.sh in the vendor folder, and then the same overlay removals as slimkat.
[HTC Droid DNA] zawata:
yeah i had quite a fun time(sarcasm) dealing with AOKP and their F***ing /vendor/aokp folder

i just tried to build and errored out after about 30sec through kernel errrors

i also had to include CM's msm8960-common folder because aokp doesnt include it by defualt

overlay removals was pretty obvious, idk that anything supports them but CM

hopefully i can get a build and upload by tonight

EDIT:

ok this is getting difficult

what did you do for the vendor/aokp situation

so far ive dumped cm.mk into vendor/aokp/products

and changed every instance of cm to aokp

and since cm.mk calls to common_full_phone.mk and nfc_enhanced.mk, i copied those from slimkat

howver common_full_phone.xml calls to xml files that dont exist and i cant find them

so i changed it to call to vendor/aokp/configs/common.mk instead and completely left out nfc_enhanced and erased it from vendor/aokp/products/dlx.mk

right now its building, and im sure it wont work

EDIT2:

surpirsed even myself, started building it(same as mentioned above) and its currently odexing the applications(last step of build process) if it boots it will be uploaded tonight :D

EDIT3: booted :D

really lacking in features, cant wait for them too add more too it

will be creating a new devdb project/thread shortly

[MENTION=5053434]jamiethemorris[/MENTION]

if you have problems building, PM me or post in this thread or something(tagme so i will know) and i will do the best i can to help you

remember sometimes the best way to continue is to start over completely(thats how i built slimkat)
[HTC Droid DNA] tdizzle404:
That would be awesome
[HTC Droid DNA] jamiethemorris:
I didn't even do that last part... I saw that it needed those, but decided to try and build without them. I just modified the vzwm7.mk instead. I'm not sure which way is the correct way because I don't know what those files do. But I'm assuming at least that common_full_phone is for global instead of having to flash a gsm patch and modify the apn's. Could be totally wrong though.
[HTC Droid DNA] danjull:
Usually the common_full_phone.mk is fairly lean in content. It usually contains a call for common.mk or common_full.mk, a few ring tones, boot animation, and cm calls some telephony specifics. A lot of roms just have the common file. Guess it's useful if you're also supporting tablets.

Here's my dlx.mk:

# Inherit device configuration
$(call inherit-product, device/htc/dlx/full_dlx.mk)

$(call inherit-product, vendor/aokp/configs/cdma.mk)

$(call inherit-product, vendor/aokp/configs/vzw.mk)

$(call inherit-product, vendor/aokp/configs/common.mk)

PRODUCT_COPY_FILES += \
vendor/aokp/prebuilt/bootanimation/bootanimation_1080_1920.zip:system/media/bootanimation-alt.zip

# Set build fingerprint / ID / Product Name etc.
PRODUCT_BUILD_PROP_OVERRIDES += \
PRODUCT_NAME=dlx \
BUILD_ID=JDQ39 \
BUILD_FINGERPRINT=htc/verizon_wwe/dlx:4.2.2/JDQ39/277065.4:user/release-keys \
PRIVATE_BUILD_DESC="3.06.605.4 CL277065 release-keys"

PRODUCT_GMS_CLIENTID_BASE := android-verizon

# Device naming
PRODUCT_DEVICE := dlx
PRODUCT_NAME := aokp_dlx
PRODUCT_BRAND := Verizon
PRODUCT_MODEL := HTC6435LVW
PRODUCT_MANUFACTURER := HTC

It built fine with that. I didn't touch the device tree besides the lines 225 and 228 in the overlay file. Add aokp_dlx-userdebug to the vendorsetup.sh in vendor/aokp and you should be set. I used msm8960-common from aokp. Did you specify vendor and device when you did your repo init? If not it won't download any device tree, kernel or vendor.
[HTC Droid DNA] zawata:
lol i didnt include VZW.mk or CDMA.mk and it built just fine

and no i didnt specify anything(on purpose)

and yeah i didnt touch most of the device tree either

im gonna take a look to see that my data and cdma arent broken lol

EDIT: they arent it works just fine

im gonna post it but tell people to watch for errors then build it your way if they pop up
[HTC Droid DNA] jamiethemorris:
[MENTION=5285997]zawata[/MENTION] thanks, I'll do that. Did you guys sync the entire repo for all devices? Cause I did that and afterwards realized it was completely unnecessary. I probably should have just synced the m7. What is the usual/most efficient way to do that?
[HTC Droid DNA] zawata:
yeah i would just take cm.mk from cm's DLX repo and rename it dlx.mk and put it in the same directory then modify it the way i did(take out missing files, fix broken paths) because that's what worked for me

also include the needed repo's and modify the few device tree files

also build this rom before you move onto PA as you are already working on this one

pretty sure you're not absolutely correct about common_full_phone.mk(only about half-right)

flyhalf's gsm patch only modifies the build prop

yeah completely unneccessary haha

when i port a rom, i start from the rom then add the dlx sources from CM

the way to do that is through your local_manifest.xml(i am going to assume you dont know about it for the sake of my explanation)

it overrides your .repo/manifests.xml

in it you can reference different repo's instead of one included by default

such as using the DLX device tree instead of M7

or using CM's M7 kernel instead of AOKP's

to use a local manifest, create

/.repo/local_manifests/dlx.xml

this is your local manifest

hrere is an example of it and a better explanation

http://wiki.cyanogenmod.org/w/Doc:_Using_local_manifests

and here is mine(for AOKP, they should be different for each rom)

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="cm-github"
fetch=".."
review="review.cyanogenmod.org" />

<project path="device/htc/dlx" name="CyanogenMod/android_device_htc_dlx.git" remote="cm-github" revision="cm-11.0" /> <!--DLX device tree-->
<project path="vendor/htc" name="TheMuppets/proprietary_vendor_htc" remote="cm-github" revision="cm-11.0" /> <!--DLX device blobs-->

<project path="device/htc/msm8960-common" name="SlimRoms/device_htc_msm8960-common" remote="github" revision="kk4.4"/> <!--CPU configs and drivers-->
<project path="kernel/htc/m7" name="SlimRoms/kernel_htc_m7" remote="github" revision="kk4.4"/> <!--DLX kernel->
<project path="hardware/qcom/audio-caf" name="SlimRoms/hardware_qcom_audio-caf" remote="github" revision="kk4.4" /> <!--QCOM specific audio drivers-->
<project path="hardware/qcom/display-caf" name="SlimRoms/hardware_qcom_display-caf" remote="github" revision="kk4.4" /> <!--QCOM specific display drivers-->
<project path="hardware/qcom/media-caf" name="SlimRoms/hardware_qcom_media-caf" remote="github" revision="kk4.4" /> <!--QCOM specific media drivers-->
</manifest>
[HTC Droid DNA] jamiethemorris:
[MENTION=5285997]zawata[/MENTION] thank you, that's very very helpful.
[HTC Droid DNA] zawata:
Anytime :)
[HTC Droid DNA] danjull:
You shouldn't need the qcom stuff for aokp. Just the dlx device, cm m7 kernel, and the muppets' vendor. If you run

repo init -u https://github.com/AOKP/platform_manifest.git -b kitkat -g all,-notdefault,m7vzw,HTC

as your first repo init it'll pull the msm8960 stuff for you. And the m7 kernel from aokp, but I can't get it to work yet.
[HTC Droid DNA] zawata:
this is definitly the better way to do it
[HTC Droid DNA] jamiethemorris:
I've noticed that build instructions for a several roms, including AOKP and PA, instruct you to do this:

sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so

What's that about? Is that a Ubuntu-specific thing (I use Arch)? I just don't see how it has anything to do with building anything.

I'm also wondering if you guys think it's a good idea to have a general rom-building/q&a thread? There's probably already a general xda one I'm assuming, but perhaps it would be good to have a dna-specific one which would keep us from having to hijack existing threads, and maybe inspire others to start building as well (the more the merrier, right?).

---------- Post added at 07:56 AM ---------- Previous post was at 07:52 AM ----------

I'm also considering building codename android: http://xdaforums.com/showthread.php?t=2589104 github: https://github.com/codenamedroid?tab=repositories I don't see any manifest though so idk.
[HTC Droid DNA] skynet11:
Is anyone interested in building the latest AOKP KitKat nightly for the DNA?
[HTC Droid DNA] GrzlyAdms:
Have you checked out [MENTION=5285997]zawata[/MENTION]'s AOKP build?

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

I don't think it's based of the latest nightly, but it is 4.4.2 and has been updated once or twice.

Edit: forgot to mention that I ran the initial release for a few days and had no real issues/bug show up. It ran smooth just was lacking some of the features I've gotten used to (plus I went through a compulsive flashing stage), so I moved on to something else.
[HTC Droid DNA] skynet11:
Somehow I must have missed that thread when I scrolled through the Original Android Development section in Tapatalk. I'll probably just wait for a newer build and stay on AOKP Jelly Bean for now. Thanks for pointing it out though :D
[HTC Droid DNA] zawata:
i havent updated AOKP in a while though ive been meaning too

their didnt seem to be much demand for it so i shelved for a little bit but i was gonna wait until about the 31 because thats when AOKP said they were gonna get serious but ill update it tomorrow, gotta resync the whole repo

as of right now its about 3 weeks behind
[HTC Droid DNA] amit_sen:
Checkout thread in Orig. Android Dev for an updated build of mine. Let me know if all works well or not :cool:

Tapatalked from TF300T - Dirty
[HTC Droid DNA] GrzlyAdms:
Sweet! Thanks! I'll give it a try tonight or tomorrow and let you know how it goes.
[G2 Q&A, Help & Troubleshooting] wasssabi5:
so now its stuck on the LG boot screen and it wont turn off. I NEED HELP ASAP! im at around 70 % battery. is there a way to access recovery without ADB?adb wont recognize it in this state.
[G2 Q&A, Help & Troubleshooting] canecbr600:
Look in the development section, all ur answers are there...
[G2 Q&A, Help & Troubleshooting] wasssabi5:
doh, thanks, how do i delete this thread?
[G2 Q&A, Help & Troubleshooting] WizeGuyDezignz:
I've looked over there but I'm still confused what to do if you can't get adb to recognize your phone when it won't boot. Can someone please let me know?
[Verizon Samsung Galaxy S III] bmeek:
The AOSP browser (or whatever's in CM10.2) does a great job of letting one zoom on HTML text to a comfortable size, then double-tap the text to have it reflow to fit the display and scroll for easy reading.

I can't find a browser for TouchWiz that behaves like this... Any suggestions?

I also miss cm10.2's integrated WiFi hotspot and a hundred other fine points that I've grown used to...

But with CM10.2, incoming calls won't ring out loud when an A2DP Bluetooth device is connected, and the overall robustness of wireless data and voice seems flakey by comparison to the TouchWiz ROMs...
[G2 Q&A, Help & Troubleshooting] xwonic:
Is it possible to port the Samsung's Multi Window mode into the G2?

cause i think the slide apps has not the same functionality.
[G2 Q&A, Help & Troubleshooting] Tx Redneck:
Why not just get a Samsung?
[G2 Q&A, Help & Troubleshooting] Trevino07:
Let me know how that works out for ya!
[G2 Q&A, Help & Troubleshooting] sansart:
Nope!
[G2 Q&A, Help & Troubleshooting] ericdabbs:
I wonder if there can be a mod in a custom rom to allow all apps to run with QSlide just like how there is a mod to run Samsung multiwindow with all apps in custom rom
[G2 Q&A, Help & Troubleshooting] th3taman:
If this could happen I would buy the G2 in an instant!
[G2 Q&A, Help & Troubleshooting] DesertHawk:
There is one BIG gaveaway that it wont work. The fact this is an LG and that is a Samsung.
[Nokia Lumia 920] raujaku:
An update for access point showed up. I know that touching anything in AP will turn off my free tethering, but will updating it also turn it off?
[Nokia Lumia 920] raujaku:
Decided to bite the bullet and go for it. Updating the access point app didn't affect my free tethering.
[Nokia Lumia 920] Solarenemy68:
The only question I have is if it is something you don't use, then why even bother to update it? I mean the entire question and insecurity could have been avoided simply by not updating becuase as you said you don't use it, so there is no need to update an unused app.

I have several my phone wants to update, but I don't let it since I don't use them. Makes no since to me to have something up and current if I am never going to use it.
[Nokia Lumia 920] raujaku:
OCD? it being there in in that spot always wanting to update bothers me for some reason.
[Micromax A110] Dark Nexus:
Hello everybody, two new (Duel core)smart phones from Micromax having android 4.2.2 are available online and there ROMs are available at need ROM, I think it these two ROMs help us for solving the camera issue in our ROM, so I request to all Deva please take a look at this download link a76 http://www.needrom.com/mobile/micromax-a76/, download link a74 http://www.needrom.com/mobile/micromax-a74/

Dark Nexus
[Micromax A110] Dark Nexus:
Cellkon a112 (duel core) 4.2.2 ROM available http://www.needrom.com/mobile/celkon-a112/

Dark Nexus
[Micromax A110] Dark Nexus:
Specs of both phones http://specifications.tablets-help.com/micromax-canvas-fun-a76-specifications-and-features/, http://specifications.tablets-help.com/micromax-canvas-fun-a74-specifications-and-features/

Dark Nexus
[Micromax A110] sagarwep:
But this is 6572 dualcore
[Micromax A110] Dark Nexus:
I know but I think we can take cam libs from these two ROMs and checkout in our ROM for solving cam issue(I am only trying to help Devs)

Dark Nexus
[Micromax A110] darkangel1016:
another source for all Stock ROMs

hi, there is another source for all stock ROMs

http://www.moulnisky.com/index.php?dir=Micromax/
[Micromax A110] mufti.arfan:
Cam working now, as everyone knew it was kernel related issue.

Check android development section for 4.2 rom (dark nexus) tonight.
[Micromax A110] mandar91:
that is a good news
[Micromax A110] itssandeep:
cwm recovery for micromax a76

please make an cwm revovery for micromaax a76 pls doi it fast .....requsting to you plss