yashsingh1/xdaforums huggingface dataset:
[General Topics] Vedoo:
Hello.. I have a problem or is it normal.. When i enter still camera in fujitsu f-05d and switch to video camera the flash blinks constantly ,does anyone know how to turn it of ??? please help me ...
[Android Q&A, Help & Troubleshooting] PenguinxEnjoi:
I've searched this, but all the ones I found talk about the app being opened, being opened in their app. I want to make an app that has nothing in it, no user interface, or anything, all that I want it to do is redirect to an app I have installed
[Android Q&A, Help & Troubleshooting] PenguinxEnjoi:
Anyone ? ¿ ?
[Android Q&A, Help & Troubleshooting] zelendel:
The way android is set up doesn't allow one app to control another. It is a security feature

Wayne Tech S-III
[Android Q&A, Help & Troubleshooting] kuisma:
Read up on Intents.
[Android Q&A, Help & Troubleshooting] PenguinxEnjoi:
Oh, thanks for telling me. I just wanted to make an app that had a different icon than the app i was using and had a different name too

Thanks, I thought there was an easier way, sorta like; 'open "insert package name here" '
[Android Q&A, Help & Troubleshooting] nikwen:
There actually IS a way to do that:

String packageName = "com.example.test" //enter your package name here

startActivity(getPackageManager().getLaunchIntentForPackage(packageName));

(add it to your Activity)

You would maybe need to stop your activity after that with finish();
[Nexus One Q&A, Help & Troubleshooting] darbz15:
My HTC Nexus One will not allow me to turn on my Bluetooth, When I try it acts like it is trying then goes back to OFF position. :(

Android Version 2.3.7

CyanogenMod 7.1.0-N1

Kernel Version 2.6.37.6-cyanogenmod

any idea how to fix this bluetooth issue?
[Nexus One Q&A, Help & Troubleshooting] taodan:
Are you trying to use a Bluetooth headset? If yes, then you need to pair them first.
[Nexus One Q&A, Help & Troubleshooting] darbz15:
:

nope, the main bluetooth will not turning ON, it goes OFF automatically.
[Nexus One Q&A, Help & Troubleshooting] darbz15:
.

upppp. pls. help. :(
[Nexus One Q&A, Help & Troubleshooting] darbz15:
.

uppppppppppp!
[Nexus One Q&A, Help & Troubleshooting] sphinxcs898:
Why don't you just try updating to a latest CM version? 7.2 ?
[T-Mobile Samsung Galaxy Note II] Dopadron:
Since the recent time change...my factory clock changed over and when I set my alarm to the time I need to get up it states the proper amount of hours before the alarm should go off but the hours on the main screen are plus an hour. Its already caused me to be late to work once and didnt know if anyone had any ideas. I am not rooted and on the latest firmware. Thanks in advance
[T-Mobile Samsung Galaxy Note II] Warrior1975:
Did you check your date and time settings to make sure you are using network time? I don't know, maybe turning on and off will help? Can't hurt to try.

Sent from my SGH-T889 using Xparent Skyblue Tapatalk 2
[T-Mobile Samsung Galaxy Note II] Dopadron:
I appreciate it apparently it took twenty four hrs for the phone to recognize the time change. Thanks again and mod feel free to close this thread
[HTC Droid DNA] chad0989:
This is for developers only. No builds will be posted in this thread.

https://github.com/CM10DNA

For those who would like to work on it. I would recommend using a combination of the current HTC devices that have cm10.1 and the nexus 4 as a guide.

Any valid development related discussion can be posted here. Please no posts that aren't directly related to development (i.e. comments, thanks, etc.).

Currently working:

Display

Data (3g/4g)

SMS, MMS should work also but I haven't tested

WiFi

adb

MTP

Sensors (compass, gyro etc)

Vibration

LEDs

Audio

GPS

Bluetooth

Camera (FFC still has some issues with face detect)

Not working:

BT headset audio

Bugreport spreadsheet:

https://docs.google.com/spreadsheet/ccc?key=0AltBJkYoAZNLdEtQVTFoVkdxcWFfYXFJd05zcFYzUHc&usp=sharing
[HTC Droid DNA] rainabba:
I'm all for more development and would never want to sound ungrateful for any community contributions, but I get the impression (since I've been watching closely on XDA and IRC) that you're not working with drewx2 at all on THIS project even though it's been in the works for a while. If you were to contribute there instead of starting from scratch, we'd likely have it fully running in not time. He's only got a couple issues left and I'm not sure the framebuffer is one, but if his code-base falls short there, then you could at least improve on that.

I'd happily donate to you also if you were making contributions toward his project. Please consider that instead of going solo.
[HTC Droid DNA] chad0989:
This is CM10.1, not CM10. Completely different animals even though one would think otherwise by the numbering. I have no desire to work on CM10. I appreciate your concern but please keep discussion on topic.
[HTC Droid DNA] Flyhalf205:
For anyone who is familiar with building CM if not Google is your friend. I have set up everything for you already. The default branch will pull cm-10.1-chad.

https://github.com/CM10DNA/android

repo init -u git://github.com/CM10DNA/android.git -b cm-10.1-chad

If you fix anything. Be sure to send a pull request back and we will take a look at it. Thank you.
[HTC Droid DNA] Sjflowerhorn:
I would love to take a look at, and for the guy above who thinks this is seperating the process I forked drews hub but could never get it to sync no matter what( I also have very little experience with github so it could be me). Best of wishes to you and yours on your trip. Have fun, be safe, and well. And thanks for making a new hub to play with. Last of my off topic-ness. More on topic what were your last efforts towards? It may make a good starting point.
[HTC Droid DNA] Flyhalf205:
Right now it just gets to the boot logo screen. Maybe pulling a log finding out what's making it now boot fully.
[HTC Droid DNA] E.Cadro:
^^^^This^^^^

This is the second time in 24 hours I've had to come in this thread and clean it.

Please abide by the op's request.
[HTC Droid DNA] chad0989:
I do want to mention for anyone working on this that CM10.1 is distinctly different than CM10. It uses an updated display HAL, audio HAL, GPS HAL, and telephony is significantly different. You can't simply patch up from CM10.

The good news though is that our phone uses the same SOC as the nexus 4. There is no support for the n4 and the newer SoC (apq8064) in CM10, only the older msm8960 which most other HTC devices use. Hence why I keep stressing that its a much better idea to work on 10.1. Most anything we need to update we can pull almost directly from the n4.

I hope now everyone has resolved their differences and this can be worked on as a group. Like I've said anyone can pull anything from my tree and I dont care nor do I need to be credited. I just want fully working AOSP. It should be quite reasonable to achieve now that the display is working. Especially because of our similarities to the nexus.
[HTC Droid DNA] amit_sen:
Finally a noteworthy post on this topic. :highfive:

When we work as a team , the total is worth more than the sum of individuals.

Iam sure with devs like you and drew, DNA community will get fully working AOSP at the earliest.
[HTC Droid DNA] EmericanX:
I have the CM10DLX stuff synced already so when I get home tonight I'll switch to the -chad branch.. lol.. sorry I just thing the branch name is a little comical. Either way, have a safe trip man! BTW: Another device I was wondering may help shed some light is the Moto Droid Razr HD. While only dual core it looks like the primary difference is the gpu.. so there may be some helpful stuff in there as well.

Edit, is adb functional?
[HTC Droid DNA] crpalmer:
I just built and booted this and was happy to see that it got as far as upgrading my apps (but then hung when "starting apps"). Very nice.

However, I couldn't get adb to connect. I tried editing the initrd.img to set the property ro.adb.secure=0 in case is was related to securing adb, but that didn't help.

Is there some magic that you need to do? If not, how do you start to debug this?

FYI, in case someone else hits the same error that I did, I also had to do:

mkdir -p out/target/product/dlx/obj/SHARED_LIBRARIES/libmmjpeg_intermediates/
touch out/target/product/dlx/obj/SHARED_LIBRARIES/libmmjpeg_intermediates/export_includes

to get it to build.
[HTC Droid DNA] renzo.olivares:
Do you think disabling the old ion api would do much? Pretty sure mako and other 3.4 kernels use new
[HTC Droid DNA] chad0989:
I think it could potentially break some of our proprietary libs. Audio and camera most likely. I think we should keep it the way it is for now. Once everything is working we can give it a shot to see.
[HTC Droid DNA] EmericanX:
Finally finished sync over night. Started a build before I left for work. I guess the first thing we need to sort out is getting adb working... I wonder if usb debugging is disabled by default..
[HTC Droid DNA] chad0989:
adb was working on my build originally. It may have gotten messed up when I pulled the init scripts into the tree. Maybe try messing with the init.usb also.
[HTC Droid DNA] EmericanX:
Lack of ADB seems to be kernel related. I flashed a different kernel and was able to pickup adb... of coarse it did't play well with libs but atleast its some sort of progress! lol.
[HTC Droid DNA] chad0989:
It's something in the ramdisk I'm sure. I'll fix it when I get back this weekend if someone doesn't before then.
[HTC Droid DNA] EmericanX:
I've started looking around ramdisk but I'm crashing for the night. I'll do some more looking around tomorrow.
[HTC Droid DNA] crpalmer:
I don't have time to do any real work on this (this is my daily driver, use heavily for work phone and it's a time sink to backup/restore/fix /sdcard/0) today,but I took the boot.img and changed init.rc to include init.dlx.usb.rc instead of init.usb.rc and I believe that should get adb up and running for you.

To test, I booted viper 1.1.3 with the old kernel (no adb ever, but amazingly enough the display works enough for the boot animation) and booted it with the changed kernel which give me adb access.
[HTC Droid DNA] chad0989:
Audio itself works pretty much 100% (playback and recording work great). It's routing voice from the baseband that is giving us issues. Since we're not setting q6 effect, it defaults to the default topology. I tested in sense and using the default topology instead of HTCs and works fine, so the issue isn't there. We can also use the mako acdbloader without issue so any beats references only seem to be used when beats is enabled.

One thing I haven't tested yet is switching the RT5501 amplifier. I'm not sure on how the hardware is setup, but if audio is routed from the baseband through it that could be our issue. I feel as that its only used for the external speaker though.
[HTC Droid DNA] drewX2:
[/COLOR]

Ah I see. Well, are you sure you can use Mako's acdbloader? Although most APQ8064 boards are the same, the Mako is different.

Nonetheless, why would acdbloader be the problem? I think it would be something with libcsd-client. There is also a RT5501 file in system/etc on stock roms
[HTC Droid DNA] chad0989:
Got it. :D
[HTC Droid DNA] mike_augie:
holly heck ... you mean audio is working /// this is very good
[HTC Droid DNA] chad0989:
Audio has been working, in call audio is now working. Needs some more tweaking though before I push it. It ended up just being a routing issue in the config.
[HTC Droid DNA] mike_augie:
thats what i meant :victory::D
[HTC Droid DNA] amit_sen:
You guys r genius, Sir :thumbup::thumbup:

Sent from my HTC 'One' DNA
[HTC Droid DNA] azndan2:
:good: Chad you are prosauce :good:
[HTC Droid DNA] Argumentation:
Confirmation number: 6VC02356SK182194G

Two beers on the way, you deserve it man. :highfive:
[HTC Droid DNA] t1gartist:
Well that's awesome news in call audio working my favorite Rom is almost possible for a daily driver
[HTC Droid DNA] chad0989:
Still trying to tweak some things. Normal calls work fine, but no speakerphone yet. Going to see if I can get that sorted out before I push. If I don't get it by the end of tonight I'll push what I have anyway.

That and I need to decide if I should use the mako based HAL or the CAF based one...

Then I'll see if I can get GPS and BT working. Camera will be last and will likely take a good amount of work. I need to clean up the init stuff some more too.

I'd like to rebase the kernel on the newly released source too. If anyone is feeling up to it that would be great.
[HTC Droid DNA] t1gartist:
when i start on a miui v5 port can i use your cyanogenmod as a base?
[HTC Droid DNA] jellydroid13:
You can't base miui of of 4.2 that's why the nexus 4 doesn't have a miui port
[HTC Droid DNA] KyJelly69:
You could ask drew if you could use his.
[HTC Droid DNA] crpalmer:
I just pulled the chad-audio branch (for the device tree) and I'm having this compilation error:

In file included from device/htc/dlx/audio-caf/mm-audio/aenc-amrnb/qdsp6/src/omx_amr_aenc.cpp:41:0:

device/htc/dlx/audio-caf/mm-audio/aenc-amrnb/qdsp6/inc/omx_amr_aenc.h:62:35: fatal error: linux/msm_audio_amrnb.h: No such file or directory

compilation terminated.

I have concerns about the whole system being a scary composite of "orphaned" patches. By that, I mean that we have code that happens to be working for us and no-one is taking care to keep it up-to-date with the mainline. That's mildly scary for a single component, but when we start pulling different pieces from different repos at different times, it becomes very frightening.

Having said that, my vote would be to do whichever seems more likely to work now.

We're going to end up with some monster commits that will bite us in the ass later. Personally, I can live with that because switching between CM10.1 and another ROM is very painful for me. I have to continue to switch until we have working phone (audio), bt (work phone calls) and camera (children). The monster commits at least remind you that you'd better go back and fix them when they are stable,

I looked at the BT awhile ago. I see that you've gotten some good things in there (using the right device). I think that the mako might be doing something very different for the hci-attach though.

I had been looking at trying to cherry-pick some commits onto the 2.04 source to fix the video, but having explained that we should leave the monster commits for now I guess I could take a look at this instead.
[HTC Droid DNA] chad0989:
You need the msm8960 common repo too. It has the extra includes.

That's another thing I need to do. Merge those two repos. Our msm8960 is far from having anything in common with other devices.

As for the audio, once everything is working the way we want I may be able to make it work with mainline. Although I was debating adding in q6 effect support. We could always submit patches upstream once everything settles.
[HTC Droid DNA] Flyhalf205:
Merging the two probably be the best. We can cherry-pick or patch in any from the mainline if any commits helps us. The kernel. Should we hold off on rebasing the new kernel source "if" the new update to fix the sim card detect will have a new kernel? That would be the kernel we need if the update comes with a new one. Of course new source would take forever to get released.
[HTC Droid DNA] crpalmer:
I'm not sure whether or not there will be any kernel changes for the sim card issue. If there are, I would expect any change to the kernel for the SIM card fix would be very localized and easy to add later on.

This kernel release is (very obnoxiously) painful because HTC stripped comments from a lot of the source files and that causes a lot of merge conflicts and then makes it harder to cherry-pick/merge new commits in the future. Dealing with it now rather than later is probably good and (I'm very biased because I already tried to add back as many comments as possible and will try to add this into the CM10.1 kernel). Dealing with it sooner, rather than later, seems like a good idea to me.
[HTC Droid DNA] chad0989:
I have speakerphone working now. Going to push the current config but it's going to need some more work for other audio sources (headset, bt when we get it working).

Edit: Apparently I'm in the dark on this one, what's the sim card detect issue?
[HTC Droid DNA] chad0989:
I noticed that they stripped a lot of comments in my quick skim. Not a fan of that to be honest, they were pretty useful at times.
[HTC Droid DNA] Flyhalf205:
Few devices have issues where the sim card can't be detected. I hope this update helps me. But I can't even build right now :( Hangs in hardware somewhere..

It continues for pages....
[HTC Droid DNA] chad0989:
Hmm. Mine had some SIM issues in the beginning. I attributed it to hardware though. It appeared as though my SIM tray was pushed too far in, so I popped it out and pushed it in only far enough to be flush with the outside of the phone and I haven't had an issue since.

I'm sure that probably won't help you, but maybe it could help some others.
[HTC Droid DNA] chad0989:
Try re-syncing?
[HTC Droid DNA] Flyhalf205:
No luck. Probably something I need to revert that cm committed. Guess I better start looking :(
[HTC Droid DNA] chad0989:
I'll take a look too. I haven't synced in a week or so, but I do see a couple suspect commits.
[HTC Droid DNA] renzo.olivares:
no more kernel headers edits check android_device_htc_msm8960 probably has the commits to fix
[HTC Droid DNA] chad0989:
Good. I welcome that change for sure :good:. I'll fix it up in the morning.
[HTC Droid DNA] Argumentation:
Chad, I'm sure you don't want bug reports yet, but I've found a few that I wanted to post so I don't forget. I won't be able to grab logs till tomorrow if you want them.

1. When toggling Wi-Fi from on to off in settings menu or quick settings, the phone reboots.

2. Paid apps give an error about not installing to the USB storage or SD card.

3. Video playback works, but landscape video doesn't, regardless of the app.

Like I said, not many, but just wanted to let you know, keep up the good work. :good:
[HTC Droid DNA] pio_masaki:
Took some tinkering, but GSM users will be glad to know I got mobile data working on T-mobile as well as APN settings to show, took me awhile, building a fresh tester and I'll update when anything else useful happens.

To chad: the tinkering will break LTE/CDMA, I'm not sure if its actually going to get along as both in one build, it may need to be seperate, for now. Small changes, easy enough to implement, though. I can't test it as a dual mode setup as I have no vzw service, sorry. Maybe I can have a buddy take it for a spin on vzw and see what happens.
[HTC Droid DNA] Nirvana Rules:
Thanks man, I've been waiting for gsm to work. I was able to get data to work for like a minute. I'll be waiting for your Rom :D
[HTC Droid DNA] renzo.olivares:
here are the specific commits http://review.cyanogenmod.org/#/c/35722/ http://review.cyanogenmod.org/#/c/35721/ i like that change as well =)
[HTC Droid DNA] Flyhalf205:
I am able to turn NFC off and on now. Was just keeping on and unresponsive.

EDIT: Well it was until I did a reboot. lol
[HTC Droid DNA] rjd584:
I have 2 of these phones on my account. both had SIM issues. One wouldnt work at all, the other worked sometimes but would lose the SIM frequently. I polished the contacts on the SIM card of both phones with neverdull. Have not had a single SIM issue since.
[HTC Droid DNA] skmpowdjy:
Yeah, in the latest version that you built, the NFC "sticking" issue comes and goes.. I'm not a dev, so I don't know if anything's changed with regards to NFC, but the behavior is the same in the latest build.

EDIT: Actually, you posted a new build last night :P Well, the NFC behavior was similar in the 04-09 build is what I meant.
[HTC Droid DNA] chad0989:
Here is a bugreport spreadsheet. Its open to anyone to edit. Please put the issues here to keep everything centralized and to keep clutter out of the threads.

https://docs.google.com/spreadsheet/ccc?key=0AltBJkYoAZNLdEtQVTFoVkdxcWFfYXFJd05zcFYzUHc&usp=sharing
[HTC Droid DNA] crpalmer:
Chad,

Here's a repo/branch which is the stock 2.04 kernel with many of the comments restored to which I then cherry-picked the commits from the cm-10.1-chad branch of your kernel.

If you want to use it, you'll need to delete your branch and push this up in its place.

I left a build configuration file that I use for building it outside of the regular CM build process. Feel free to delete it if it bugs you.
[HTC Droid DNA] chad0989:
I keep getting a bunch of cgroup permission errors with it.
[HTC Droid DNA] chad0989:
Hmm this wifi crash issue didn't used to be there. I wonder what broke it.
[HTC Droid DNA] crpalmer:
Are you sure you're using the "stock-cm" branch. I just realized that there is also a "stock+upstream+cm-10.1-chad" which is something different that I did for flyhalf when he was working to update to the latest linux version. I'm not seeing any cgroup errors on my build.

What's your kernel version number?

What wifi crash?
[HTC Droid DNA] chad0989:
Ah. I was using the upstream+cm-10.1-chad branch. I'll try the other one. Thanks.

When wifi is toggled off it causes a crash. It appears to be when the module is unloaded as I just tried to manually unload the module and it replicated it exactly.

Edit: With the new kernel it doesn't crash but it never unloads.
[HTC Droid DNA] crpalmer:
"Good" news is that it doesn't crash on the kernel I built off the code I pushed up. It just fails to unload the module... Going back to the kernel I built on Friday from your source, I do see the same crash.
[HTC Droid DNA] chad0989:
Yeah. Odd. I can work around it if need be, but I'd prefer we find the cause.
[HTC Droid DNA] aFancyTickler:
Ive finally managed to pull a logcat for the music being choppy and not working. http://goo.gl/LIMaO

kept seeing this error

E/alsa_pcm( 214): cannot open device '/dev/snd/pcmC0D0p', errno 16
[HTC Droid DNA] chad0989:
In what scenario? Need to be able to replicate it myself to test/fix.
[HTC Droid DNA] aFancyTickler:
when using google play music . play a song thats on the device and the sound would be choppy and glitchy . i was using headphones when ii pulled the log
[HTC Droid DNA] chad0989:
Okay. Fixed it. I'll push it in a few min.

Edit: Nevermind. Only fixed one case, still does it under another.
[HTC Droid DNA] aFancyTickler:
wonderful :) i also pulled a log for paid app issue if you wish to take a look

http://goo.gl/aMXbd

just try to install any paid app and youll get a error saying cant install on usb or sd card
[HTC Droid DNA] chad0989:
It appears it has to do with playing a notification sound while music is playing. For some reason the sound system tries to enable whatever device is currently already in use and causes a crash. I'll keep working on it.

Edit: Actually fixed it this time. Pushing in a minute.
[HTC Droid DNA] aFancyTickler:
Thanks abunch :). i posted a few logcats of some other issues on the bug tracker too
[HTC Droid DNA] Flyhalf205:
@Chad or crpalmer

So the cm-10.1-chad branch is the new kernel?
[HTC Droid DNA] crpalmer:
Yes, that's the kernel rebased onto the 2.04 source drop.
[HTC Droid DNA] orangekid:
Thread cleaned for off topic.

Please keep in mind that while in some threads, even ROM threads and such, a little off topic is tolerated, but this one specifically says no off-topic in the OP, so we really need to keep this on the rails.

If you want Jim, Bob, Jose, Vinnie, or Hannah Montana to help or collaborate, let's take it to PM.

Thanks :)
[HTC Droid DNA] chad0989:
Fixed paid app issue
[HTC Droid DNA] myfishbear:
good job!
[HTC Droid DNA] jonesin:
I don't know if it had been discussed but WiFi ap is non functional. Also have had no success with any third party tether apps. Generally they will all start fine all though no signal is transmitted then when closing the app it causes a reboot.
[HTC Droid DNA] aFancyTickler:
add your issue to the bug tracker for wifi ap. https://docs.google.com/spreadsheet/ccc?key=0AltBJkYoAZNLdEtQVTFoVkdxcWFfYXFJd05zcFYzUHc#gid=0

as far as tethering apps try this app http://goo.gl/ycXYt and change device profile to generic ics/jb (wlan0) and enable routing fix. if that doesnt work then idk :P