yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] dr.m0x:
As far as I know Heimdall for Linux isn't compatible with this tablet so I'd be surprised if it works on Mac either.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] tylerholbrook:
Sucks. Every one I know has a mac. Only reason I got one was for graphic design. Gotta buy a pc because I love tinkering with android so much.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] QuantumPSI:
Not having a PC is the only thing standing between me and the true AWESOMENESS of this tablet... just a few more weeks!
[Sony Xperia T, TL, TX, V] bamdadkhan:
hi all,

i'm experiencing a weird problem. i've been flashing lots of roms (cm10.x, omni, stock-based ones), and suddenly my phone's camera started not working. however, if i turn the device off completely, start charging it, and turn it back on, the camera is fine until a reboot (even after unplugging from the charger). removing the sim card and rebooting also helps sometimes.

i've tried:

- factory reset

- flashing different roms

- revering to stock

- some forum post on the 'net about deleting the 'dcim' folder on both sd cards (wtf lol)

- disassembling the phone (my warranty is void anyways) and checking the main, battery and the camera's ribbon cable connection (they're fine)

i'm pretty sure it's not a hardware problem, but i can't be certain, of course.

anyone had this issue before? any suggestions? something else i forgot and should try?

thanks,

bamdad
[Sony Xperia T, TL, TX, V] bamdadkhan:
update: somehow, after installing the new 4.3 firmware, it was alright for a while, then it started happening again. since my back cover was in quite a rough shape, i ordered a new one; after putting it on, the camera started working normally.

now i really don't get this, because i've taken the device apart dozens of times. it might have something to do with those little copper contacts being corroded on the old back cover, someone correct me if i'm wrong. the strange thing is that the camera seemed to work fine with the back cover off.

well, it's fixed now, but for how long? :/
[Sony Xperia T, TL, TX, V] bamdadkhan:
this is just insane. yesterday i tried omnirom again, played around with it, then restored my backup of the official .199 firmware, and some time later tried to take a photo - boom, camera and flash hasn't worked since. now that i think of it, i distinctly remember trying a previous build of omnirom before the last time my phone went bonkers.

now i'm not hinting at that it's omnirom's fault directly, since apparently lots of people are using it without similar issues, and at the end of the day custom roms aren't responsible for damaging a device, but it's strange.

if someone has any pointers as to what should i do, i'd be really appreciative. i'm going to try flashing from an original ftf file, maybe this has to do with some firmware stuff that's reeeally over my head. fingers crossed..
[Sony Xperia T, TL, TX, V] bamdadkhan:
the funny thing is that it works great after restoring my backup of omni. bloody hell. : ) i mean what am i missing here? : )
[Sony Xperia T, TL, TX, V] bamdadkhan:
okay, so i managed to (maybe) fix it. the trick was to *not* use omnirom's cwm recovery to restore the stock rom, rather flash the stock kernel with philz touch, *then* restore the backup. man.. hope this lasts.
[Sony Xperia T, TL, TX, V] bamdadkhan:
started again this morning on dark lord's blackxt (stock .199-based), torch went too. rebooting and the other tricks didn't do diddly-squat. however, a trip to recovery and back fixed it. i did install doomkernel, but it's probably not the one that helped, because i've been using that last time the problem started.

btw, i know i'm spamming this topic all alone, but maybe someday this will prove useful to, or someone who knows what's going on will laugh and tell me to idk reformat the whole device or flash some obscure firmware file or something.
[HTC Droid DNA] danjull:
Thought I'd start up a general thread where we can come to ask and answer general android building questions. I've been guilty myself of high jacking threads for questions and answering questions regarding porting, compiling, building, etc. Figured I'd try to start up a general thread for just that topic.
[HTC Droid DNA] danjull:
I'll start. Having some issues with external/jpeg.

external/jpeg/jddctmgr.c:350: error: undefined reference to 'jpeg_idct_islow'
external/jpeg/jddctmgr.c:340: error: undefined reference to 'jpeg_idct_ifast'

Have never seen that error before, I'm comparing it to other ROMs that I've built and the file is exactly the same. Not sure what else is linked to it.
[HTC Droid DNA] jamiethemorris:
[MENTION=3721563]danjull[/MENTION] Did you ever find the solution to this? How do you go about troubleshooting build errors (in general)? Do you usually look at what other files that file calls for or so you just kind of stumble through the while source looking for clues?
[HTC Droid DNA] danjull:
I haven't yet.

It's a mix. Sometimes it's luck, sometimes it's clear enough so you can just follow the paths. I usually compare the problem source file to CM or another source I know works. Look at commits that happen after a known good build.
[HTC Droid DNA] jamiethemorris:
Okay, cool. That's pretty much what I've been doing. I've also been doing diff -r between the cm11 source and the rom I'm building for folders that I think may be problematic and printing it to a file. So if you have the cm11 source locally you could try using that for external/jpeg or just external. I tried meld for this sort of thing too, but it didn't seem to be to helpful when it comes to entire directories.
[HTC Droid DNA] t1gartist:
isnt that gcc related as in the variable isnt defined as used?
[HTC Droid DNA] zawata:
figured i should post somewhere where i can find other devs(rather than the omni thread lol)

i got these errors today while building slimkat and after searching every line of code in the whole source, it was only reference once and that was the line that through the error

it makes it more difficult because this is the out/ folder so i really cant compare to CM11:

/home/zach/android.SlimKat/system/out/target/product/dlx/obj/GYP/shared_intermediates/blink/bindings/V8SVGAElement.cpp:71: error: undefined reference to 'WebCore::SVGAElement::svgTarget()'
/home/zach/android.SlimKat/system/out/target/product/dlx/obj/GYP/shared_intermediates/blink/bindings/V8SVGAElement.cpp:99: error: undefined reference to 'WebCore::SVGAElement::href()'
/home/zach/android.SlimKat/system/out/target/product/dlx/obj/GYP/shared_intermediates/blink/bindings/V8SVGAElement.cpp:85: error: undefined reference to 'WebCore::SVGAElement::externalResourcesRequired()'
/home/zach/android.SlimKat/system/out/target/product/dlx/obj/STATIC_LIBRARIES/third_party_WebKit_Source_core_webcore_derived_gyp_intermediates/SVGElementFactory.cpp:134: error: undefined reference to 'WebCore::SVGAElement::create(WebCore::QualifiedName const&, WebCore::Document*)'

i havent had any success with this

EDIT: nuketown 2025 population slimkat (da fuq did i just say?)

anyways resyncing the repos tonight, maybe it will be better to just start over

EDIT: nuking solves all problems :D
[HTC Droid DNA] danjull:
What have java version are you using?
[HTC Droid DNA] jamiethemorris:
I'll have to check when I get home. I'm pretty sure I'm using open jdk6 though.

---------- Post added at 07:23 PM ---------- Previous post was at 06:57 PM ----------

java version "1.6.0_51"

Java(TM) SE Runtime Environment (build 1.6.0_51-b09)

Java HotSpot(TM) 64-Bit Server VM (build 20.51-b01, mixed mode)
[HTC Droid DNA] jamiethemorris:
I'm giving up on tripndroid for now... I'm trying to build liquidsmooth now and I'm running into a kernel error. I couldn't see what it was because it happened too far back when it stopped. So I tried to build the kernel individually using linaro 4.8 and it stopped in the same place so I'm pretty sure it's the same error:

drivers/video/msm/mdp.c: In function 'mdp_hist_lut_write_off':
drivers/video/msm/mdp.c:400:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
error, forbidden warning: mdp.c:400

I think it has to do with linaro because I didn't have any problems building ProBam today with the same kernel... I also tried building the ProBam kernel by itself and it gave me the same error.

EDIT: Well, I used crpalmer's kernel instead and it built perfectly fine... Not the perfect solution though.
[HTC Droid DNA] jamiethemorris:
Liquid won't flash. No idea why. It just reboots instantly as soon as it starts flashing.
[HTC Droid DNA] crpalmer:
Search for 1024 in the kernel defconfig that is used. There is an config named something with FRAME that sets the size to warn on. You can change it to 2048 to fix the build.

---------- Post added at 06:13 AM ---------- Previous post was at 06:10 AM ----------

Also, run

brunch dlx 2>&1 | tee /tmp/build.txt

After the build, that tmp file should hold all the text from the build.
[HTC Droid DNA] jamiethemorris:
Thank you. Do you think that has anything to do with why it won't flash?
[HTC Droid DNA] crpalmer:
No, the frame size warning is just there to ensure people don't accidentally so something stupid and breaks the build to let them know. 1K is arbitrary so 2K is also fine.
[HTC Droid DNA] jamiethemorris:
Can someone give me a little explanation on how the manifest works? Like how it knows which branches to pull of each git project? I'm trying to build carbon and it's running into an issue about BluetoothLwPwrProximityMonitor being undefined. For whatever reason the BluetoothLwPwrProximityMonitor.java file was deleted in the cm11 BluetoothExt repo. This was several months ago though. Both CM11 and ProBam build fine, and they don't have any of the pxpmonitorservice stuff. So it looks like they're using the cm-10.2 or stable/cm-11.0 branch. But it the manifests I don't see anything that differentiates which branch they pull from. Basically, I think I need to have Carbon use stable/cm-11.0 instead of cm-11.0 and then I think it will build, but I just want to make sure I'm doing it right.

EDIT: I tried that, but it doesn't matter now because it gives me this all of a sudden:

make: *** No rule to make target `/run/media/jamiethemorris/LinuxExternal/android/carbon_kk/out/host/linux-x86/bin/mkbootimg', needed by `/run/media/jamiethemorris/LinuxExternal/android/carbon_kk/out/target/product/dlx/boot.img'. Stop.

Really weird. I'm guessing it's misleading. I tried putting BluetoothExt back to how it was but I get the same error. It got way further than this before.

find -name mkbootimg*
./system/core/mkbootimg
./system/core/mkbootimg/mkbootimg.c
./external/genext2fs/mkbootimg_ext2.sh

Also, liquid is now hitting this kernel error:

liquidsmooth_kk/kernel/htc/m7/drivers/video/msm/mipi_novatek.c:569:37: warning: argument to ‘sizeof’ in ‘snprintf’ call is the same expression as the destination; did you mean to provide an explicit length? [-Wsizeof-pointer-memaccess]
error, forbidden warning: mipi_novatek.c:569

I don't know why it's having so much trouble. I'm guessing I will find this in the defconfig as well?

Maybe building ROMs is just not for me...
[HTC Droid DNA] armydog13:
Don't get discouraged. I'm fixing to start learning, and I need you to figure it all out so I can ask you all my noob questions. :P
[HTC Droid DNA] jamiethemorris:
Thanks. :) For starters, read this http://xda-university.com/as-a-developer/getting-started-building-android-from-source and this http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code also this link is helpful because you will need to sync CM's repos at the same time for the device tree and kernel, and sometimes other repos http://xda-university.com/as-a-developer/repo-tips-tricks
[HTC Droid DNA] DREWHAMM974:
I came here to ask some questions about building liquid myself but since you got it booting guess i might as well give on up huh? I guess I should bring up what im doing anyways so I dont accidentally start on a port one of the pros is starting on lol
[HTC Droid DNA] jamiethemorris:
No, don't give up, nothing wrong with teamwork and some learning experience. I don't have it booting, it fails when I flash it and I can't get it to build with the stock kernel
[HTC Droid DNA] DREWHAMM974:
Well I can do what little I know. I was going to try because I didn't see a KitKat Liquid and I love that rom but I've honestly built very little and mostly all I know is from xda-university. Not sure how much help I'll be but anything I can try to help with I more than gladly will. Also, where can I go to learn a little more. I know xda-university can't be the only place online yall go to to learn this stuff.
[HTC Droid DNA] jamiethemorris:
Idk that's where I've learned the most useful stuff. CyanogenMod wiki is useful too. That's about all I've found really. I don't know any programming or anything aside from supercollider
[HTC Droid DNA] DREWHAMM974:
Okay well I'll go ahead and get at it, if you think of anything that I can help you do let me know.
[HTC Droid DNA] jamiethemorris:
Will do.
[HTC Droid DNA] jamiethemorris:
Well, apparently github just changed their layout. Nothing happens when I search through repos anymore unless I know the exact name of what I'm looking for. It just won't search... So say if I'm looking for any repo with m7 in the name, it won't find anything, i have to type in android_kernel_htc_m7 or something similar.
[HTC Droid DNA] armydog13:
Android Runtime

Any ideas? Attempting to open Carbon Fibers>Interface causes Carbon Fibers to FC. logcat shows NullPointerException for AndroidRuntime even though the phone is running the DalvikVM.

http://pastebin.com/tDvjBuc6
[HTC Droid DNA] jamiethemorris:
Does the same thing happen using ART? the last crdroid build also had an interface settings crash, I wonder if it's the same problem. Interesting that both of them happened on ROMs where the builders do not have a test device.
[HTC Droid DNA] DREWHAMM974:
Quick question, and sorry if it's an absolutely noobish one, but if I build a Rom built only for the Nexus 4 since it's only gsm how can I get cdma working or should it work out the box? I'm sorry but I'm just learning and I'm not sure what will happen
[HTC Droid DNA] jamiethemorris:
You could try importing the vendor/cm/config/CDMA.mk and vzw.mk files from CyanogenMod and putting them in that ROM's config or configs folder, and then include them in the dlx device tree's (romname).mk.

---------- Post added at 11:18 AM ---------- Previous post was at 11:11 AM ----------

Are the other ROM builders subscribed to this thread? It would make it more useful I think even though most of us asking questions are total n00bs.

I have another issue. I'm trying to port multirom over to the DNA. The recovery builds fine, but it gets to the twrp screen and just flashes the splash screen infinitely. Has anybody seen this happen before with any twrp builds or know what could cause this? I could have sworn I got everything right, the mmc blocks and everything. I'm wondering if I shouldn't be building it against cm11. I built twrp against cm11 though, which worked fine. Any ideas?

This would be awesome if I can get it to work, I know we don't have much room on our device, but multirom doess have the ability to boot from USB and of you're like me it is possible to clear just enough room for 2 roms on the internal storage.

Edit: this is my multirom device tree https://github.com/jamiethemorris/multirom_device_dlx
[HTC Droid DNA] armydog13:
Just ordered my computer. Should have my parts in the next 2 weeks
[HTC Droid DNA] jamiethemorris:
Turns out the multirom problem was really simple. I had renamed the recovery.fstab to twrp.fstab just because the htc one port had it named that. changed it back and multirom is working now (the recovery, at least).

EDIT: The boot menu is working. Unfortunately I only have a crappy iPad picture. Now for the hard part... The kernel patch.
[HTC Droid DNA] jamiethemorris:
I got it! I patched crpalmer's kernel with this patch https://gist.github.com/Tasssadar/6733940 I had to make a few modifications but I got it working. Right now I am dual-booting ProBam and Carbon. I haven't been able to get it to flash a ROM onto a usb drive yet (I'm using fat32), idk if that's operator error or something wrong with the device configuration.

EDIT: Looks like the USB problem was a fat32 problem. I added an ext4 partition to my usb drive and I Carbon flashed to it just fine. I had to share the main ROM's kernel for it to boot properly though.
[HTC Droid DNA] armydog13:
Wow dude
[HTC Droid DNA] jamiethemorris:
[MENTION=3721563]danjull[/MENTION] [MENTION=3866229]amit_sen[/MENTION] do either of you guys know how to view multi-part commits in github? Meaning where it says [2/4] or something like that, view the other parts of the commit without fishing around for them? I ran into a java error building liquid, it turned out it was because it was a commit to multiple git projects and it was incomplete because they hadn't forked one of the git projects with the necessary changes, in this case it was android_packages_apps_InCallUI. So I had to find another ROM with the same commit and search through their github for all the necessary changes and make them manually.

EDIT: Liquid still doesn't boot. No idea why. Just goes to a black screen.
[HTC Droid DNA] danjull:
Any ideas on this one?

device/htc/dlx/gps/utils/loc_cfg.cpp:206:10: error: no matching literal operator for call to 'operator "" __VA_ARGS__' with arguments of types 'const char *' and 'unsigned int', and no matching literal operator template
[HTC Droid DNA] jamiethemorris:
This looks like it should fix it http://stackoverflow.com/questions/18068006/why-is-clang-parsing-this-as-a-user-defined-literal
[HTC Droid DNA] jamiethemorris:
What is this?

/run/media/jamiethemorris/LinuxExternal/android/probam_kk/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: error: /run/media/jamiethemorris/LinuxExternal/android/probam_kk/out/target/product/dlx/obj/EXECUTABLES/recovery_intermediates/install.o: file is empty
/run/media/jamiethemorris/LinuxExternal/android/probam_kk/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: error: /run/media/jamiethemorris/LinuxExternal/android/probam_kk/out/target/product/dlx/obj/EXECUTABLES/recovery_intermediates/roots.o: file is empty
/run/media/jamiethemorris/LinuxExternal/android/probam_kk/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7/bin/../lib/gcc/arm-linux-androideabi/4.7/../../../../arm-linux-androideabi/bin/ld: error: /run/media/jamiethemorris/LinuxExternal/android/probam_kk/out/target/product/dlx/obj/EXECUTABLES/recovery_intermediates/extendedcommands.o: file is empty
bootable/recovery/recovery.c:872: error: undefined reference to 'ensure_path_mounted'
bootable/recovery/recovery.c:892: error: undefined reference to 'ignore_data_media_workaround'
bootable/recovery/recovery.c:893: error: undefined reference to 'ensure_path_unmounted'
bootable/recovery/recovery.c:894: error: undefined reference to 'ignore_data_media_workaround'
bootable/recovery/recovery.c:148: error: undefined reference to 'ensure_path_mounted'

etc etc and it keeps spitting out a bunch of those "undefined reference" errors
[HTC Droid DNA] crpalmer:
Did you run out of disk space? Maybe on /tmp? I'd just do a make clean and try again after checking disk space.
[HTC Droid DNA] jamiethemorris:
Hmm... I very well might have. If I did I'm embarrassed that I didn't notice lol
[HTC Droid DNA] jamiethemorris:
Nope, I still have some disk space. I think there's some half-finished commits going on or something, it's been a few days since the official release
[HTC Droid DNA] crpalmer:
The reason I suspected disk space is that you have errors like:

recovery_intermediates/install.o: file is empty

it's very unlikely for a commit to make these files empty.
[HTC Droid DNA] armydog13:
Error during build

Corrected a problem with the proprietary vendor files and about 90 minutes into build, it stops with the following error:

make: *** [/home/jewtoo613/android/CM11/out/target/product/dlx/obj/STATIC_LIBRARIES/third_party_WebKit_Source_core_webcore_derived_gyp_intermediates/third_party/WebKit/Source/bindings/v8/custom/V8DocumentCustom.o] Error 1

I saw someone post about this in the Beanstalk development thread somewhere but couldn't find the solution. Any ideas?
[HTC Droid DNA] jamiethemorris:
Yeah, I don't really understand how that's possible, install.c and the other 2 files look fine as far as I can tell. I'm assuming all the errors that follow are because of those files being empty, right? Anyway I have like 64 gigs free and it's giving me the same error. I'm doing a test build of cm11 to see if I get the same error... Is there any way my ccache is corrupted? Or it's trying to do too many jobs at once or something? I'm just using regular old brunch dlx. I honestly can't find anything that looks out of place so I'm wondering if it's some oddball thing like that.

[MENTION=4867661]armydog13[/MENTION] That's not the actual error, you should have something more specific before that.
[HTC Droid DNA] armydog13:
Did make clean and got a successful build. booted about 15 minutes ago. Everything working. Felt good to build a ROM even if someone else had already done all the hard work.

Looks like I can do under 2hr builds. Time to try something no one else is doing yet.

Thanks [MENTION=5053434]jamiethemorris[/MENTION]
[HTC Droid DNA] jamiethemorris:
Just a tip, if you use ccache you can do builds after that much quicker.
[HTC Droid DNA] armydog13:
I have ccache set up

---------- Post added at 08:24 PM ---------- Previous post was at 08:24 PM ----------

Should I do another build too see how long it really takes?
[HTC Droid DNA] .torrented:
With ccache my builds for Roms are about 25~30 minutes, kernels few minutes tops
[HTC Droid DNA] armydog13:
Okay. I need some realtime help. Someone hit me up on Hangouts (jewtoo613@gmail.com) when they have some free time. lol. "free time." I crack myself up.
[HTC Droid DNA] jamiethemorris:
I found my problem. I'm pretty sure the ccache was corrupted because after rebooting and then clearing it the ROM built properly.
[HTC Droid DNA] jamiethemorris:
I got this error trying to build thinkingbridge...

frameworks/av/media/libstagefright/AudioPlayer.cpp: In member function 'virtual android::status_t android::AudioPlayer::start(bool)':
frameworks/av/media/libstagefright/AudioPlayer.cpp:152:31: error: 'AUDIO_FORMAT_PCM_16_BIT_OFFLOAD' was not declared in this scope

Wouldn't this error be happening in CM as well? This is the commit that causes it: https://github.com/CyanogenMod/android_frameworks_av/commit/b3f9ff4e1579c3263687de33d532ab2dc3fbab0f so I reset to the prevous commit and it's building fine so far, but I don't like doing something like that when I don't know why it's happening...
[HTC Droid DNA] jamiethemorris:
Thinking bridge doesn't boot, just like just about every other ROM I've built... Tried setting SELinux to permissive as well as building with Linaro 4.7. No luck.
[HTC Droid DNA] danjull:
Ok, so I've run into a road block with Vanir. Starting with nightly 3/6 the internal sd card won't mount. Here's the changelog for 3/6

Any suggestions or ideas?

Edit: I might, just maybe, have found the moment of derp. If it is what I think it is, I'm gonna feel rather foolish.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] ldougherty:
I installed Cyanogenmod 10.2 on my KFHD7 over the weekend and all appears to have worked out well. The only problem or concern I have so far is that I can not seem to enable speech to text on any keyboard I download. I've tried the stock Android keyboard, the Google Keyboard, and Swiftkey, none show the voice control option.

Am I missing something here?
[Samsung Galaxy Mega] RandyLoDaGod:
Can anyone pls help me with sim unlocking my mega 6.3 sgh- m819n . I'm in the military and will very soon be headed back overseas.