yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Android Development] joshndroid:
Use local manifests rather than room service then force whatever folder structure u want
[Nexus 9 Android Development] Hashbang173:
Why not android_device_htc_flounderlte ?
[Nexus 9 Android Development] ayysir:
alright i was actually able to rename volantis to flounder_lte and have flounder and flounder_lte tree be totally separate from each other

here is the LTE tree: https://github.com/Ayysir/android_device_htc_flounder_lte
[Nexus 9 Android Development] ayysir:
i use jenkins and doing it manually everytime isn't necessary. Anyways already fixed the issue
[Nexus 9 Android Development] xtcdk:
Getting grey hair finding out how to use prebuilt kernel together with source

Dirty Unicorns /Uber / Beanstalk Yuga adm.
[Nexus 9 Android Development] zawata:
i just wrote up a good tutorial on how to build the kernel for a rom for the nexus 9, i didnt post it just in case it would be useless but if you want i will post it
[Nexus 9 Android Development] xtcdk:
That would be nice , thankz

Dirty Unicorns /Uber / Beanstalk Yuga adm.
[Nexus 9 Android Development] zawata:
Currently there's no way to do it during the build process, you have to build the kernel separately then put the boot.IMG in the zip

install this package: libncurses5-dev

Installing the packages but your cross compile should be something like

/prebuilts/GCC/linux-x86/aarch64-android-linux-4.9/bin/aarch64-android-linux-

Confirm that oath is correct and make sure it ends in a dash!

Put

CONFIG_CROSS_COMPILE :="/home/USERNAME/android/ANDROID SOURCE DIRECTORY/prebuilts/GCC/linux-x86/aarch64/aarch64-android-linux-4.9/bin/aarch64-linux-android-"

into arch/arm64/configs/flounder_defconfig to make sure you never have to type that out again

You then need to do these commands(from the root of your kernel directory(kernel/htc/flounder))

export ARCH="arm64"

make flounder_defconfig

make -j8

This will make a file called image.gz-dtb in the directory of arch/arm64/boot/image.gz-dtb

Copy this file to /devices/HTC/flounder-kernel

add these lines to your devices/htc/flounder/device.mk(they may be commented out near the top(line 20ish)just un comment them)

ifeq ($(TARGET_PREBUILT_KERNEL),)
LOCAL_KERNEL := device/htc/flounder-kernel/Image.gz-dtb
else
LOCAL_KERNEL := $(TARGET_PREBUILT_KERNEL)
endif

find this section:

PRODUCT_COPY_FILES := \
#$(LOCAL_KERNEL):kernel \
$(LOCAL_PATH)/init.flounder.rc:root/init.flounder.rc \
$(LOCAL_PATH)/init.flounder.usb.rc:root/init.flounder.usb.rc \
$(LOCAL_PATH)/init.recovery.flounder.rc:root/init.recovery.flounder.rc \
$(LOCAL_FSTAB):root/fstab.flounder \
$(LOCAL_PATH)/ueventd.flounder.rc:root/ueventd.flounder.rc

and uncomment out the commented line

in your device/htc/flounder/BoardConfig.mk

change these lines to look like this(they may be missing or commented, change them as necessary):

#TARGET_KERNEL_SOURCE := kernel/htc/flounder
#TARGET_KERNEL_CONFIG := flounder_defconfig
BOARD_KERNEL_IMAGE_NAME := Image.gz-dtb
BOARD_KERNEL_CMDLINE := androidboot.selinux=permissive
TARGET_PREBUILT_KERNEL := device/htc/flounder-kernel

From the base android directory(~android/dirtyunicorns(or whatever it is)/)

Run these commands

.build/envsetup.sh

Make clean

lunch cm_flounder-userdebug <---------------------this line will vary and you should know what it is supposed to be

Make boot image

Your boot.image will be in the same directory where the ROM would be after it was built

You can either shove this into the ROM zip or flash it separately

do keep in mind that you cannot run the brunch command then after it builds make your kernel, the kernel will use left over peices from the previous build

make clean HAS to be run inbetween using these commands but make sure that if you run brunch firs then remove the .zip file before running make vice versa etc. or will lose the previously built package

If you have any questions or problems you can just quote me and post your error, I encountered quite a bit them while learning how to do this

hoped i helped :D
[Nexus 9 Android Development] xtcdk:
Sweet . thankz

Dirty Unicorns /Uber / Beanstalk Yuga adm.
[Nexus 9 Android Development] dsouleles:
Embedding Supersu in the ROM Build

Hi all -

Has anyone successfully embedded SuperSu? I'm trying to add Chainfire SuperSu directly to my custom AOSP based rom to save a step in flashing.

I grabbed this commit from the LiquidSmooth github:

https://github.com/LiquidSmooth/android_build/commit/637d546c6b42a2dc6e8259c09f13cfe9c5f36aaf

That modifies: ota_from_target_files and edify_generator.py to create the commands for the updater script. But I can't quite figure out what do with supersu.zip. Does anyone know what else needs to be changed to make sure that supersu.zip is included the ota_package zip? Where do we need to put it in the build tree and what build scripts need to be changed?

Thanks,

D
[Nexus 9 Android Development] Hashbang173:
AICP flashes SuperSU during flash.
[Nexus 9 Android Development] dsouleles:
Hi - Thanks. I did a search of the AICP repos and I haven't found the reference. Can you point me to where to start?

Update...

Ok - so I did more poking around - AICP and Liquid Smooth use the same commit. And the supersu.zip in in vendor/aipc/prebuilt/common (and vendor/liquid/prebuilt/common). So it looks like I need to create a vendor tree for my ROM. The AICP commit is 2/2 - haven't found 1/2 yet.

Thanks,

D.
[Nexus 9 Android Development] Hashbang173:
http://gerrit.aicp-rom.com/#/c/4610/

http://gerrit.aicp-rom.com/#/c/4611/
[Nexus 9 Android Development] dsouleles:
Excellent. Thank you for the gerrit links. I had just gotten there. Still trying to figure out a better way to search on github.

D.
[Nexus 9 Android Development] Hashbang173:
The problem is the repository is forked on github.

You could however sync the repo and grep for stuff.
[Nexus 9 Android Development] Surge1223:
Why does it fail in tree? What kind of errors do you see?
[Nexus 9 Android Development] zawata:
Sorry I've been pretty busy with going back to school and trying to fix my laptop

What exactly do you mean by that? Why are we not able to compile the kernel and the rom in the same process?
[Nexus 9 Android Development] Cuzz1369:
Stuck here for a while now, Tryin to build Candy5. I know nothing of prebuilt kernels. Any help is appreciated.

Export includes file: external/tinycompress/Android.mk -- /media/cuzz136/out1/candy5/target/product/flounder/obj_arm/SHARED_LIBRARIES/libtinycompress_intermediates/export_includes

make: *** No rule to make target `/media/cuzz136/out1/candy5/target/product/flounder/obj/KERNEL_OBJ/usr', needed by `/media/cuzz136/out1/candy5/target/product/flounder/obj_arm/SHARED_LIBRARIES/libtinycompress_intermediates/compress.o'. Stop.
[Nexus 9 Android Development] NYCHitman1:
You need to snag this commit http://gerrit.dirtyunicorns.com/#/c/9278/

---------- Post added at 12:54 PM ---------- Previous post was at 12:51 PM ----------

I believe that build repos are not ready for 64-bit support as of yet. Someone around here posted a link to CM's gerrit where they were working on bringing up support for 64-bit, but I don't know where they are at currently as I don't keep track of what they do.

Many of the errors involved revolve around the kernel headers calling for ENDIAN crap. It's been a while since I've tried to compile inline, but I do recall not being able to fix those last few endian errors that I've stumbled across. Kernel stuff isn't generally my forte, so any extra eyes would be appreciated.
[Nexus 9 Android Development] Cuzz1369:
Thank you sir.
[Nexus 9 Android Development] zawata:
Damnit I just typd d out a beautiful long post...so here's the short version

Cm isn't working on 64bit yet theyre preparing for it but here's the commit for those interested :

http://review.cyanogenmod.org/#/c/82838/

You getting endian errors because your compiling the kernel in 32 bit

32 bit architecture(and compilers) don't support little endian flags and so the build errors out

You can cherry pick the above commit and add in the options on the top left to get the kernel to build, but it still doesn't boot, so the kernel has to be compiled seperately
[Nexus 9 Android Development] NYCHitman1:
What determines whether or not the kernel compiles in 64-bit? I was using a 64-bit toolchain (set the flag to use aarch64 4.9).

As an aside, I did take a peek at your post that broke down how to compile the kernel, but I wasn't able to using the aarch64 gcc. It gave me a SLEW of errors - some of which I didn't know how to properly fix. Feel free to drop me a dime on Hangouts. We can discuss further there.
[Nexus 9 Android Development] Cuzz1369:
I'm sure there is a good reasone but it is beyond me why SELinux is disabled. Is it because of the prebuilt kernel?

Anyone know if it can be turned to permissive?
[Nexus 9 Android Development] NYCHitman1:
That's how people have been able to get a bootable build. Personally, I'm not in favor of disabling SELinux to get boot.
[Nexus 9 Android Development] USBhost:
Everytime I tried to make it permissive

The kernel won't even boot

So I went with it disable
[Nexus 9 Android Development] Cuzz1369:
I am just interested with getting it compatible with elementalX
[Nexus 9 Android Development] NYCHitman1:
As in you want your Candy5 builds to be compatible with ElementalX? If so, just remove any flags (device tree) that set SELinux to permissive and/or disabled and you should be ok.
[Nexus 9 Android Development] zawata:
Seriously? i got my kernel to boot with SElinux on permisssive on like my second try? idk what your doing...

apprently it made things diffiult but i seem to have worked around that now

there are so many factors that go into it...one of the major ones is the build scripts for the kernel(themain one is build/core/tasks/kernel.mk) and the commands that are sent to the make command

if anything goes wrong with choosing an architecture then the script defaults to 32 bit to compile

as for your errors, ive got no idea why(mostly because i dont know what errors your having)...actually ive got one idea why

ill send you my email through a pm, send me a test message through hangouts(to confirm) and a picture of you error(because typing it out would be tedious)

and for the all of you. Im currently on break for developing(ill probably start up again in a few days)

school started for me again and the semester hit me like a train carrying several tons of bricks

1. my computer no longer boots into windows(kinda important for school)

2. my manager scheduled me for damn near full time employment(and im a full time student :( )

3. ive got to train the new guys coming into my department(im both relieved thats theres more that 2 people in it now, and stressed because i still have to train them)

4. i started a new netflix series and its really addicting(ok so thats not a very good reason...)

5. ive got to have my tablet in full working condition for taking notes in my classes(had a few close cals last semester with grades, want to make sure it doesnt happen again)
[Nexus 9 Android Development] USBhost:
You did use the kernel command line right?

Well I'm trying to make the kernel it self boot with permisssive

Like no ramdisk changes or without using the command line
[Nexus 9 Android Development] zawata:
not your kernel, i thought you meant a kernel in general but yes i built a kernel straight from the source with selinux enabled
[Nexus 9 Android Development] xtcdk:
Stupid question . in device/HTC/flounder i see diffente asop.mk etc aosp_flounder_only64 and so on . but which is the right to lunch

Dirty Unicorns /Uber / Beanstalk Yuga adm.

---------- Post added at 09:26 AM ---------- Previous post was at 09:24 AM ----------

How did you mange to build it . any instructions whould be apriciated

Dirty Unicorns /Uber / Beanstalk Yuga adm.
[Nexus 9 Android Development] NYCHitman1:
What's the problem, Jonas? I think you're using my device tree, so everything is already set for you. All the makefiles are called from AndroidProducts.
[Nexus 9 Android Development] xtcdk:
Yes . using your device tree ,Im just confused over which flounder userdebug i should use .

Dirty Unicorns /Uber / Beanstalk Yuga adm.
[Nexus 9 Android Development] NYCHitman1:
Nothing should be showing up for you. Just type in . build/envsetup.sh && time brunch flounder.
[Nexus 9 Android Development] xtcdk:
and only thing i need i manifest is >

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="nychitman1/android_device_htc_flounder" path="device/htc/flounder" remote="github" revision="lollipop" />

<project name="nychitman1/android_kernel_htc_flounder" path="kernel/htc/flounder" remote="github" revision="lollipop" />

</manifest>
[Nexus 9 Android Development] Surge1223:
So what happens if you build out of tree? Also disabling SELinux is just a few edits in fs/ and a couple additions and deletions in the defconfig...took me awhile to figure out how to natively have the kernel built with selinux disabled but I had no issues booting, although this was on another device.

Did you guys by chance enable ram console and early printk? If so last kmsg will show useful info on boot failures.

I'm confused...this kernel has SELinux disabled in source by default? If so, enabling it is pretty straight forward...just Google "SELinux config defs" or go here https://android.googlesource.com/kernel/common/+/android-3.10/security/selinux/Kconfig
[Nexus 9 Android Development] NYCHitman1:
No, you asked me this already. I told you that you only needed:

<project name="nychitman1/android_device_htc_flounder" path="device/htc/flounder" remote="github" revision="lollipop" />

<project name="nychitman1/android_device_htc_flounder" path="device/htc/flounder-kernel" remote="github" revision="lollipop" />

Nah, SELinux is not disabled by default. It was made disabled by the users in order to achieve boot.
[Nexus 9 Android Development] xtcdk:
Dont get it . guess its over my skills . used to get the source + my device specific files and it builds fine . well on my nexus 5

build/core/product_config.mk:234: *** Can not locate config makefile for product:confused:
[Nexus 9 Android Development] Hashbang173:
What ROM are you building. This usually only works with ROM with official support for the device. If you try this with aicp for example it will probably work (well it should) since it has official support.
[Nexus 9 Android Development] NYCHitman1:
He's trying to build my stuff for DU (which isn't even on our org yet), but it's not ready for prime time yet. I told him this already. I guess in one ear and out the other.
[Nexus 9 Android Development] xtcdk:
haha :D well.. got i to work now... i cleared my CCache
[Nexus 9 Android Development] xtcdk:
Candyrom

Dirty Unicorns /Uber / Beanstalk Yuga adm.
[Nexus 9 Android Development] xtcdk:
Solved
[Nexus 9 Android Development] joshndroid:
anyone run into this error?

can't seem to get past it -

external/e2fsprogs/lib/ext2fs/tdb.c:3801:71: warning: unused parameter 'level' [-Wunused-parameter]

external/e2fsprogs/lib/ext2fs/tdb.c:3801:90: warning: unused parameter 'fmt' [-Wunused-parameter]

Generated: (/home/joshndroid/teamsource/out/target/product/flounder/android-info.txt)

external/bsdiff/bsdiff.c: In function 'main':

external/bsdiff/bsdiff.c:196:5: warning: 'pos' may be used uninitialized in this function [-Wmaybe-uninitialized]

target C: applypatch_static <= bootable/recovery/applypatch/main.c

make: *** No rule to make target `/home/joshndroid/teamsource/out/target/product/flounder/obj/EXECUTABLES/updater_intermediates/updater', needed by `/home/joshndroid/teamsource/out/target/product/flounder/obj/PACKAGING/target_files_intermediates/cm_flounder-target_files-bbb4ac67e2.zip'. Stop.

make: *** Waiting for unfinished jobs....

target C: check_prereq <= build/tools/check_prereq/check_prereq.c
[Nexus 9 Android Development] joshndroid:
Disregard worked out what the error was
[Nexus 9 Android Development] dumtara:
Please tell, what was the solution?
[Nexus 9 Android Development] joshndroid:
Too many optimizations in my particular rom source.. had to revert a few optimizations back.. the other solution was to more android_build branch back to stock cyanogenmod
[Nexus 9 Android Development] Cuzz1369:
Is NOBODY building for flounderlte?
[Nexus 9 Android Development] seanashmore:
So i've built a rom for flounder now and have added some features etc as part of a learning-project more than anything else. Can anyone point me in the right direction of updating the values that appear in the Settings->About menu? I'd rather have it say something other than 'AOSP on Flounder' for example, and would like to shorten the build name also. Thanks.
[Nexus 9 Android Development] seanashmore:
Just an update, it seems running 'choosevariant' and choosing user has gotten rid of the AOSP on Flounder, but the build id is still the big long winded thing by the look of it. Anybody any experience with this?
[Nexus 9 Android Development] Hashbang173:
look in packages/apps/Settings
[Nexus 9 Android Development] Cuzz1369:
Vendor/config/common.mk
[Nexus 9 Android Development] seanashmore:
Thanks but that folder structure doesn't exist on standard AOSP, looks like it's only in CM-based builds.
[Nexus 9 Android Development] Cuzz1369:
Yuo, sorry never thought if that
[Nexus 9 Android Development] seanashmore:
Found this link which I will try out over the next couple of days:

http://www.kandroid.org/online-pdk/guide/build_new_device.html

Also a very useful tutorial here:

https://www.youtube.com/watch?v=1_H4AlQaNa0 - pt1

https://www.youtube.com/watch?v=rFqELLB1Kk8 - pt2
[Nexus 9 Android Development] bynarie:
RE: Theres an internal problem with your device...

I think everyone is well aware of why this problem happens and if not, its basically a difference in /vendor/build.prop and /system/build.prop. Most of us know how to fix this by editing the vendor/build.props values to match systems build.prop. BUT, how do we get around this security check. I believe its a hassle to have to flash a zip or manually edit the files everytime we flash a rom. What and where is the mechanism thats causing theses values to be checked against each other. Is it in the source somewhere that I have not found. If anyone has an idea on this please let me know. I would like to come up with a permanent fix for this. Thanks
[Motorola Droid RAZR] gonzorn:
it is possible to perform the downgrade 4.1.2 to 2.3.6 ?
[Motorola Droid RAZR] welder73:
No,it isn't.

Sent from my Razr XT910
[Galaxy Grand 2 Q&A, Help & Troubleshooting] android_smater:
there is mod lenevo super camera is available for galaxy grand 2
[Galaxy Grand 2 Q&A, Help & Troubleshooting] rogermax:
here ya go

http://xdaforums.com/showthread.php?t=2665714
[Galaxy Grand 2 Q&A, Help & Troubleshooting] kyriebel:
ALREADY provided the LINK of LENOVO SUPER CAMERA in the other section..
[XDA Assist] XDA Visitor:
RAZR M android 4.4.2 184.46.15.xt907

Build date July 29 2014. Not technically savvy at all but would like to be able to save to external SDcard. Heard "rooting" is the only way but don't know how to do this. Please help!!!
[XDA Assist] Razvan:
Hi there,

Here is the guide for your device where you will find all info about that:

[GUIDE][FAQ][KK] How to Root, Boot Unlock & More - Droid RAZR M

For more questions please register an account on XDA forums and post in the appropriate thread from the forum bellow or start a new thread in the same place:

> Motorola Droid RAZR M > Droid RAZR M Q&A, Help & Troubleshooting

Good luck
[Galaxy Ace II Q&A, Help & Troubleshooting] tomo526:
I just share . no upload
[Galaxy Ace II Q&A, Help & Troubleshooting] fifo171:
-.-"

http://xdaforums.com/galaxy-ace/ace-2-general/cm12-alpha-t2989178

BTW you're running an outdated version. :D
[Galaxy Ace II Q&A, Help & Troubleshooting] namekrronn:
what about using ram? Can we use smoothly?
[Galaxy Ace II Q&A, Help & Troubleshooting] tomo526:
absolutely , :D . ive tried n its great but this rom have some bugs .

The dev " is not for daily use " (polish)
[Galaxy Ace II Q&A, Help & Troubleshooting] tomo526:
Yes yes yes :D . very smoothly .

Oh for more info ,u can visit

http://xdaforums.com/galaxy-ace/ace-2-general/cm12-alpha-t2989178

And

http://forum.android.com.pl/f697/5-0-2-cyanogenmod-12-alpha-2015-01-01-a-491512/
[Other SmartWatches] djkaos:
You'll be my hero if you can make this happen. I bought a zwatch last year and was pretty disappointed with both stock and custom roms. It's been collecting dust since I switched back to my pebble.
[Other SmartWatches] Pulsa:
I always ready to be your tester:D
[Other SmartWatches] drakan_x:
Count me in as a tester :D
[Other SmartWatches] jawwad_shaukat:
Keep up the good work !! Count me in !!
[Other SmartWatches] frtclngr:
I can help you as a tester
[Other SmartWatches] jawwad_shaukat:
any updates....?
[Other SmartWatches] iErp:
Count me in for testing too... The stock rom and its derivates suck :(
[Other SmartWatches] StuDB:
This sounds pretty cool. Ive been on the fence about the Zwatch and I'd be keen to get one to help out!

Question: does anyone think this will work with this ROM?

Also is that watch branded elsewhere for a lower price? Its a bit steep and someone else has to sell it? Other than a metal Weloop, a metal zwatch is what ive been waiting for!

Cheers guys.
[Other SmartWatches] vigarvei:
good notice. i'm waiting for new notices
[Other SmartWatches] Pulsa:
[MENTION=5723969]parrotgeek1[/MENTION] any updates dude? Maybe i can help you port it
[Xperia Z3v General] GigaSPX:
From CES 2015, Mike Fasulo, the CEO of Sony Electronics, announced that the entire Xperia Z series will get Lollipop next month.

Are you guys excited for it or no? With the new Lollipop update, you guys think we will receive the simultaneous voice and data with it too? Will this update also unlock software features that our phone were supposed to have (FM Tuner, Location-based Wi-Fi, etc)?

What do you guys think? :D
[Xperia Z3v General] BrendenDonaher:
Edit.. because i am an idiot and realized what board I was in.. oops.
[Xperia Z3v General] tsachi:
I'd expect Verizon to take a little longer with the update considering their history with other phones.

In terms of features, I doubt you'd see any of the missing features being introduced. If verizon wanted to give us FM radio they would have done it in the original release. Voice and data, on the other hand, are expected to be in this update
[Xperia Z3v General] patience.relax:
Now would the Lollipop update itself fix the issue with simultaneous voice and data? I was under the impression that it would need to be an update on the Verizon end. Verizon will probably delay the Lollipop update by a few weeks to work their software updates into it as well.
[Xperia Z3v General] destrekor:
Technically the VoLTE or Advanced Calling 1.0 feature is a separate update, but it is highly likely Verizon will be working that update into the Lollipop update to minimize OTAs so close together.

Something tells me Sony is also working to get the OTA to start at 5.0.1 right from the start. It would be nice if Verizon is already working with Sony to include all of their junk.

Otherwise, we might expect the other Sony devices to get their update in February and March, and after Verizon takes their sweet time with excessive testing and adding in all of their junk, we might be lucky to see an update by April.
[Xperia Z3v General] 1linuxfreak:
So true, Verizon has a history of impeding updates, adding bloatware and locking the OS.

Funny Verizon adds the bloat and we try and remove it, why waste their time and money adding it if they know we are just going to remove it, makes no sense, but we are talking about Verizon here.

Just think of all the millions Verizon would save if it just stopped adding bloatware in. Knowing how greedy Verizon is you would think they (Verizon) would stop and reap the profits from it.
[Xperia Z3v General] iofractal:
Lollipop being used with the Bravia TV, in one part of the video you see they pull down the lollipop quick settings

https://www.youtube.com/watch?v=lD9mZ1hzQZE