yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Hacker432:
[MENTION=7237874]NepoRood[/MENTION]

Ubuntu 16.10 has a problem with clang I've experienced similar problems on 16.10 with CyanogenMod too

(From what I read it should be a problem with binutils)

I reinstalled Ubuntu 14.10, I think that it is the most stable distro for android development

(I use Ubuntu 15.10 too and I haven't problems of any sort)

Inviato dal mio HUAWEI Y550-L03 utilizzando Tapatalk
[Android Software Development] MSF Jarvis:
He's on BBQLinux
[Android Software Development] Hacker432:
I used latest distro of BBQLinux too and I had same problems

Inviato dal mio HUAWEI Y550-L03 utilizzando Tapatalk
[Android Software Development] MSF Jarvis:
I've said it before, BBQ Linux is not a recommended Android development platform. Stick to Ubuntu. I just retired two of my build servers, one with Ubuntu 16.04 and another with Ubuntu 15.10 . Never had a hitch.
[Android Software Development] NepoRood:
Seems like I had an error of some sort when I was using Ubuntu as well, but, that was several months ago. BBQLinux is a "good" distro, so, maybe we (ie: [MENTION=4478781]yuweng[/MENTION]) can get [MENTION=3208754]codeworkx[/MENTION] to fix this problem?

I really hate to switch again, lol (but will, if need be) I'd really like to build Omni for my X10, but, if I can't build a working recovery...

PS, I really appreciate all input from you folks :good:
[Android Software Development] lj50036:
LOL, I am still on 14.04 :D
[Android Software Development] NepoRood:
I started out with 14.04 LTS, ran into "issues" with the twrp script, and switched to BBQ (I wanted to help [MENTION=4478781]yuweng[/MENTION] with it). I really like BBQ, but that's probably more on the DE than the distro itself ;)

I can always switch my Tower PC distro, wouldn't lose as much info as my laptop would...
[Android Software Development] codeworkx:
sudo pacman -S ncurses5-compat-libs lib32-ncurses5-compat-libs libtinfo
[Android Software Development] NepoRood:
First and foremost, thank you for your hard work and valuable time! I really didn't expect to get such a quick response, however, I got this on both PC's:

[nepo@bbqlinux ~]$ sudo pacman -S ncurses5-compat-libs lib32-ncurses5-compat-libs libtinfo
[sudo] password for nepo:
resolving dependencies...
looking for conflicting packages...
:: lib32-ncurses5-compat-libs and lib32-ncurses are in conflict. Remove lib32-ncurses? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: lib32-libxml2: removing lib32-ncurses breaks dependency 'lib32-ncurses>=5.7'
[nepo@bbqlinux ~]$ sudo pacman -S ncurses5-compat-libs lib32-ncurses5-compat-libs libtinfo
resolving dependencies...
looking for conflicting packages...
:: lib32-ncurses5-compat-libs and lib32-ncurses are in conflict. Remove lib32-ncurses? [y/N] N
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: lib32-ncurses5-compat-libs and lib32-ncurses are in conflict
[Android Software Development] MSF Jarvis:
/me giggles weirdly, codeworkx!!!!
[Android Software Development] codeworkx:
Sorry, my fault.

sudo pacman -S lib32-ncurses ncurses ncurses5-compat-libs libtinfo
[Android Software Development] NepoRood:
That did the trick! Now I don't have to change distros :D

(I could only hit the button once, so here's another: Thanks :good:)
[Android Software Development] MSF Jarvis:
I'm already outta thanks today :(
[Android Software Development] yuweng:
Been very busy in real life, no time for Android thingy, just got an email notification when my name was mentioned, late to the party... :o

Every day there is improvement to Android, every distro will gonna have problems with it when using the latest, just look at the build error & fix it accordingly... :cowboy: Every distro will gonna need maven when building Android M or the latest N, for BBQLinux its sudo pacman -S maven... :cool:

Updates

Further digging seems that ONLY cm13 is using it... :o
[Android Software Development] NepoRood:
Real Life can be like that sometimes, kinda sucks :p

When I "mentioned" you, I knew you would answer eventually, you are on the other side of the world after all.

I was totally blown away (Jarvis, we should compare "weird giggles", lol) when THE Developer of BBQLinux posted, and I'm so glad he took the time, cause I just built my first TWRP with Omni source. And thanks to you guys, and your valuable info, it built, flashed and booted properly :good:

As far as "Keeping up with Android and Linux", I'll probably be behind on that for a while...
[Android Software Development] NepoRood:
CM13 and Omni 6 Causing bootloops

No matter which I build TWRP with, or which distro I use (BBQ/Ubuntu), it's the same result :confused:

CM11 and 12 work fine, with and without the AIO, I haven't tested earlier Omni, and probably won't lol

Anyway, I'm just ranting (or whining, whichever :p )

Regards,

Nepo
[Android Software Development] MSF Jarvis:
I'll call this a rant :p

OT : I've pulled down my ZNC server for a while so you may face 404 kind of errors trying to connect to it. I'm fixing that issue up and everything should be fine tomorrow afternoon, i.e. 4PM IST

CC : [MENTION=4752536]FLooDW[/MENTION]
[Android Software Development] kirito9:
Hello guys :D.. I was late in joining the discussion with Omni not booting and CM is better ...but I think I've a problem. I'm not sure if it's as [MENTION=7237874]NepoRood[/MENTION] said and he couldn't build with Omni before or what. My compiled TWRP won't boot no matter what I do (I didn't do more than one builds, I just unpacked the recovery and changed kernel).

I've attached the compiled.log and my device tree is below as well. I'm new to building TWRP with [MENTION=4478781]yuweng[/MENTION]'s script and I would like some help. Thank you for this awesome thread [MENTION=6552280]MSF Jarvis[/MENTION] and all others who made their contribution. :D :D.

https://github.com/kirito96/device_Alcatel_4032

PS: My device is the Alcatel 4032A running a custom kernel 3.4.112, KK ROM. I already have a TWRP recovery but I would like to compile as this seems to be the fun way of doing things :silly:. My working TWRP is roughly 6MB while this compiled TWRP is 8MB.

PPS: I'm using this source by [MENTION=5325978]regalstreak[/MENTION] [TWRP 6.0.1 (No Repo Folder Included) | Size: 0.5GB]

EDIT:

My compiled TWRP boots now (I decided to read through the entire thread to see what could help) and it only works because of that dirty trick [MENTION=4478781]yuweng[/MENTION] mentioned on post #45.

My question is now, what do I do? I think my problem could be in the way this recovery is unpacked/repacked :confused:.
[Android Software Development] NepoRood:
Welcome, and yes, this is the fun way of doing things :good:

I have no way to prove it, but I think Android 6 (CM13/Omni6) is not compatible with older kernels. My X10 has kernel 3.4.39, and TWRP will build and boot just fine using older Android branches.

I suggest you give it a shot using KK or LP source (CM or Omni, doesn't really matter), also, when building for my MT8127, TWRP wouldn't boot until I copied everything in the recovery ramdisk along with it.

Regards,

Nepo

PS, I couldn't unpack your recovery image with MTK tools :confused:
[Android Software Development] kirito9:
Hi, thanks for your quick reply. I'm currently downloading CM11 non repo source as I write this post and will give it a shot. I have a MT6572 device btw which has a limited recovery partition of 6MB but I'm using a modified ROM not meant for my phone which increased the recovery partition to 20MB(a little OT).

I used this awesome unpack/repack tool by [MENTION=5186178]carliv[/MENTION] to unpack my recovery image.

http://xdaforums.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658
[Android Software Development] NepoRood:
I've got the Carliv kitchen, but, I'd have to reboot into Windows to use it (I spend most of my time on Linux ;) )

These other guys will probably beat me to it, but, I'll unpack it when I get back from work, and have a look around...
[Android Software Development] kirito9:
No need to switch, carliv has made it for Linux as well. I'm on BBQLinux atm ;)
[Android Software Development] NepoRood:
Thanks for the info, I'd forgot about that, lol.

From what I can see:

1) init.rc is the one supplied by TWRP, it should be the one from your stock recovery, and look kinda like this (don't forget to add the highlighted line)

2) It's possible your recovery.fstab could be using wrong partitions, do this with adb/terminal emulator to verify:

cat /proc/dumchar_info

Hope this helps,

Nepo
[Android Software Development] kirito9:
I'll perform these changes and see if it helps. I ran out of thanks for today btw, will thank you tomorrow :p
[Android Software Development] NepoRood:
No worries, and good luck :D
[Android Software Development] raimondomartire:
everyone know what mean this flag and how calculate dim

BOARD_FLASH_BLOCK_SIZE =
[Android Software Development] NepoRood:
Use: 131072

Seems to be best way to go (hasn't failed me yet)
[Android Software Development] Van.Fanel:
Finally got my TWRP working! Huge thanks to [MENTION=4478781]yuweng[/MENTION] for that wonderful AIO script. Also to [MENTION=6552280]MSF Jarvis[/MENTION]' source and this thread. Took me a long while to get the right CM source. That saved me a lot of time. Also thanks to the friendly [MENTION=7237874]NepoRood[/MENTION].

Now I want to port CM13 for my device. I just don't have the kernel source for my MT6753. Sad.
[Android Software Development] MSF Jarvis:
No kernel source available
[Android Software Development] Van.Fanel:
How did you manage to get the kernel source for the Pixel V1 if I may ask? Did Google release it? Because I've been reading and I found out Mediatek sources are hard to come by.
[Android Software Development] MSF Jarvis:
I'm using a prebuilt kernel.
[Android Software Development] Van.Fanel:
Sorry, but what is a prebuilt kernel?
[Android Software Development] MSF Jarvis:
Prebuilt kernel is inside the boot.img of you device, it's the output of the kernel source compilation
[Android Software Development] NepoRood:
Glad you got it going :good:

If you're using the AIO, then your "prebuilt" kernel will be in your device tree already ;)
[Android Software Development] bigsupersquid:
so I've got a weird one.

lost my working device folder with poor backup habits, and trying to reconstruct it, I've got twrp mostly functional again.

it builds better for me in cm13 than omni... not much luck for me messing with omni so far.

that twrp will boot and works, except it refuses to mount anything on an initial pass, then mounts fine except the internal sd which it ignores the path to. it's browsable though. if i pkill recovery in the terminal, it restarts with all partitions functionally mounted, no errors, and the internal sd is recognized in the right place.

that's just something I'm curious about and not my real question though.

the weird part, is that if i fastboot boot the recovery built with cm13, mtp works. if i actually flash the recovery and start it up, mtp says error 2 in the log and won't connect. adb works either way.

no more log info to refer to and I'm not seeing anything odd in dmesg (though i should probably compare it to a working run connecting to mtp.)

if nobody has experienced anything similar I'll try getting logcat going in the recovery (i read you can do that, right?) so i can get more information.

thanks for looking at my overly verbose odd little issue.
[Android Software Development] Van.Fanel:
Oooh... That sounds promising! Glad I didn't delete my VM box after compiling TWRP. :D

Is there a guide somewhere here? I've been reading the Cyanogenmod wiki but would like to get more ideas. I hope [MENTION=4478781]yuweng[/MENTION] can come up with an AIO too if that's possible. :p
[Android Software Development] MSF Jarvis:
http://xdaforums.com/chef-central/android/guide-android-rom-development-t2814763

This is as easy as it can get. All thanks to [MENTION=5216756]jackeagle[/MENTION] and people like [MENTION=6049586]Arvind7352[/MENTION] (and me? :p ) who help so willingly :)
[Android Software Development] Van.Fanel:
Thanks! Guess I'll have a lot to read on.

So for CM13, I have to download the repo and non repo file you uploaded on regalstreak's thread?
[Android Software Development] Hacker432:
You can try to follow this guide to build environment and repo sync of the sources

http://xdaforums.com/showthread.php?t=3404024
[Android Software Development] MSF Jarvis:
Either of them, not necessarily both.
[Android Software Development] kirito9:
Sorry for taking to long to reply back but I finally did it! I compiled TWRP not using the AIO script but the traditional method. I've had a lot of help from [MENTION=5186178]carliv[/MENTION] who helped me from scratch compiling CWM. [MENTION=4478781]yuweng[/MENTION] also inspired me to start building TWRP so thanks to him as well ;) [MENTION=6552280]MSF Jarvis[/MENTION] for this thread and all the awesome developers out there :D.

It isn't perfect as yet but it's nothing I can't fix.

Again thanks to everyone for getting me involved in building from source xD.
[Android Software Development] Van.Fanel:
So... it looks like I'm gonna have trouble with the device tree. I don't have it and my phone manufacturer (Alcatel) didn't release it publicly. The AIO script did create a device tree for my device but in my own understanding, it is only 'minimal'. :confused:
[Android Software Development] MSF Jarvis:
You can build upon it, make it "fatter" ;)
[Android Software Development] Van.Fanel:
Ha. What sort of food should I feed it to fatten it? :laugh:

By the way, is Ubuntu 16.04 LTS ideal to build upon?
[Android Software Development] MSF Jarvis:
Ubuntu 16.04 is good provided you follow the right guide. Nathanpfry.com has a good one for this. What food to give is too broad a subject, so I don't feel I or anyone can _teach_ it
[Android Software Development] Van.Fanel:
Which OS do you personally use?

Now I can see my CM13 dream crumble. :(
[Android Software Development] MSF Jarvis:
I used to rock Ubuntu 16.04 on my previous server but this new (and arguably better, [MENTION=5618023]SlimShady's[/MENTION] and [MENTION=6622051]Startrek852[/MENTION] can confirm:D) one is running 14.04
[Android Software Development] kirito9:
Not necessarily, if you can find a similar device tree, you can look at the contents and try to modify as your own, although it won't be complete as somethings you'll have to use from the forked device tree.

P.S: I've no experience in this field, it's just what I heard and saw many MTK developers do (those that didn't get a complete device tree)
[Android Software Development] Van.Fanel:
Thanks! I'll use 14.04 then.

I think I'll just play around while learning even without a complete device tree. *starts feeling self-pity* :cyclops:
[Android Software Development] NepoRood:
Don't let it crumble just yet, you've got a "base" to start with. May not work, but prowl about Github and look for similar devices and see what they did.

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

Glad you got it going! :good:
[Android Software Development] Van.Fanel:
Thanks guys! Although it's quite daunting for a total newbie like me, it gives me great hope.

I'm looking at the Elephone P8000 right now. It has the same MT6753 chip as mine (Alcatel Flash 2). Found out they released the source code on github. But I don't know what to look for here. :laugh:
[Android Software Development] kirito9:
Here you can find the device tree for the Elepone P8000

Seems like it can build CM12.1, so give this thread a look when you're ready
[Android Software Development] pelostiesos:
Thanks a lot for your post.

Sorry, but I have a message when I select "1) Sync source code base repository" and after a select 1 (Use OmniROM repo) or 2 (Use CM repo.).

The message says: "Internet status: Down!" :confused:

Please could you tell why? I'm using Oracle VM VirtualBox, and It has Internet, because when I open "Firefox" I can navigate without problems.

Thanks for your help.

1
[Android Software Development] kirito9:
[MENTION=6552280]MSF Jarvis[/MENTION] [MENTION=7237874]NepoRood[/MENTION] [MENTION=4478781]yuweng[/MENTION]

The recovery works great except for one minor bug, I can't get adb to work with my device nor can I use MTP nor USB storage.

I wonder if it's related to my init.rc or my flags

TARGET_USE_CUSTOM_LUN_FILE_PATH := "/sys/devices/platform/mt_usb/gadget/lun%d/file"
TW_INTERNAL_STORAGE_PATH := "/storage/sdcard1"
TW_INTERNAL_STORAGE_MOUNT_POINT := "sdcard1"
TW_EXTERNAL_STORAGE_PATH := "/storage/sdcard2"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "sdcard2"

I tried my stock init.rc with the flag pointing to it but nothing. Before when I only modified recovery.fstab and used the init.rc from TWRP ( back when it wasn't booting). I was able to get both MTP and adb working. If you have any thing that can help that'd be great.
[Android Software Development] NepoRood:
Try a manual download with repo init, I'll explain in a bit, you want full source or part source?

---------- Post added at 01:45 PM ---------- Previous post was at 01:41 PM ----------

Just thought of this, after answering your pm. In your default.prop file, look for this line:

persist.sys.usb.config=adb,mtp
[Android Software Development] kirito9:
Mine says persist.sys.usb.config=mass_storage,adb

Device tree: https://github.com/kirito96/device_twrp_4032a
[Android Software Development] NepoRood:
Hmm, adb (at least) should be working. Do you have a stock recovery.img? You may need to put more files inside your /recovery/root folder...
[Android Software Development] kirito9:
Yeah I do have the stock recovery and more files like? Use your device tree for reference?
[Android Software Development] NepoRood:
My device probably has too many, lol, but yes. I included everything in stock ramdisk (excluding sepolicy related). All mine is located in "rootdir" but you should put your files in "recovery/root", along with your init.rc as well. Then you can drop the target_initrc flag in boardconfig (everything in the recovery/root folder will be copied anyway)
[Android Software Development] kirito9:
Ahh ok, I'll give that a try :)
[Android Software Development] kirito9:
Recovery is almost perfect. I got USB storage working now :). I was using the wrong lun_file_path although my device is MT6572

MTP was once working but not anymore :'). Fixed one bug created 21 more.

Android is awesome!! lol

EDIT: Btw, can someone guide me on faster builds? I don't think I'm using the CCACHE correctly. I created a script to automatically compile recovery based on [MENTION=4478781]yuweng[/MENTION]'s AIO TWRP script but lol builds are like 25+ mins everytime. [MENTION=6552280]MSF Jarvis[/MENTION] [MENTION=7237874]NepoRood[/MENTION]

Here it is

cd ~/cm12
make clean
export USE_CCACHE=1
export LC_ALL=C
prebuilts/misc/linux-x86/ccache/ccache -M 25G
source build/envsetup.sh
lunch cm_4032a-eng
make -j4 recoveryimage
[Android Software Development] NepoRood:
Yes, it most certainly is, lol

Try this for your script:

make clean
. build/envsetup.sh
lunch cm_4032a-eng
mka recoveryimage

Once you set ccache, it's set until you delete the folder, no need to set it "every time". Average build on my pitiful laptop takes 25-30 minutes for first build, 9 or less for sequential builds.

Laptop specs:

Dual-core @1Mhz (yes, I did say pitiful)

4Gb ram

ccache @ 50G (if you're only building for one device, 25 is probably fine)
[Android Software Development] kirito9:
Thanks once again, the former noob is now helping the noob :).
[Android Software Development] MSF Jarvis:
NepoN00b lol :D
[Android Software Development] kirito9:
Hahaha genius! [MENTION=7237874]NepoRood[/MENTION] :silly:

P.S Everything is working now with my TWRP :cool:
[Android Software Development] MSF Jarvis:
Kewl! Thread on XDA incoming :fingers-crossed:
[Android Software Development] NepoRood:
Glad you got it working correctly

Regards,

NepoN00b
[Android Software Development] MSF Jarvis:
Number one, DO NOT USE THOSE BLITHERING HIDE TAGS FOR LOGS. Secondly, your error is 100% clear in the log and even a cursory glance will show you what it is. No spoonfeeding here.
[Android Software Development] Van.Fanel:
I noticed that [MENTION=4478781]yuweng[/MENTION]'s AIO script does not compile TWRP if your device codename has a dash to it. Example: lion-5 (that's actually my device codename in build.prop)

It gives out an invalid lunch combo error.
[Asus ZenWatch] johnsmithgt55:
One Of the our Best Free Dynamic Watch faces Awakening (*)

“Time changes everything except something within us which is always surprised by change -Thomas Hardy”. Likely, Awakening watch face surprised you by its changes. It is like solving a puzzle, It awakens you.

https://goo.gl/A475wR

What you feel:

★ Every time you look at it, you have to take a moment to decipher the location of the arms to know the time.

★ It reminds you that you have to learn more and change yourself as often as possible

★ It motivates you to stay aware all the time and to keep moving forward.

★ It reminds you that the moment you stop changing, the world runs ahead leaving you behind.

★ It Supports Both Round and Square Watches (cool)

[IMG="Awakening Watch Faces"]http://i.imgur.com/beXlylN.jpg[/IMG]
[Asus ZenWatch] johnsmithgt55:
Cool Watch Faces For Free:https://goo.gl/77MmNo

Right from the apparels we wear to the gadgets we use, everything speaks a lot about us to the people around. ”Staying Cool Bring out the Best”. So stay cool with Cool Watch Face

What you feel:

★	Theme or face of your wearable based on your mood and occasion.

★	Beauty of the modern tech wearable’s is that you can choose as many themes as you like and install those in a single gadget

[IMG="Cool Watch faces"]http://i.imgur.com/WCN4NBX.jpg[/IMG]

[IMG="Cool for asus"]http://i.imgur.com/L8R6EXs.png[/IMG]
[G2 Q&A, Help & Troubleshooting] kamel-kgb:
Hi

I have LG G2

I bought it as D802 but after the update to lollipop I have had an issue with the screen and discovered that it is LS980 by looking to the motherboard , anyway , I fixed the issue by flashing the right rom (which supposed to be the official rom of LS980) , but the network didn’t work ! no sim card would work on it !

After that I tried almost all the roms that comes with the LG G2 (D800 , D801 , D805 , VS980 ,…etc)

Now I am running the Phone on VS980 (Verizon) and still have an issue with the network (it works for some sim cards an doesn’t for another :/ and the signal is so weak (I think it works only with 3G network) It is not possible to use it as it is :/

Please anyone have a solution for this?

Thanks in advance 
[G2 Q&A, Help & Troubleshooting] kamel-kgb:
no one has an answer to this :(
[G2 Q&A, Help & Troubleshooting] dark_prince:
Which rom are u using with it? Also, do u have root/custom recovery on it or is it running completely stock. Atleast u have figured out which rom works for your phone.
[G2 Q&A, Help & Troubleshooting] reyad0606:
Facing the same issue.
[G2 Q&A, Help & Troubleshooting] raptorddd:
i believe if am not mistaken so am not so sure, but dont they run on wcdms networks? not sure where you guys are. but some places dont have wdmc bands. not so sure wich is the verizpn pne or sprint. could this be it.?
[G2 Q&A, Help & Troubleshooting] zhjackss:
Just sim unlock and enable wcdma bands by using qpst and qxdm softwares.
[Sony Cross-Device Development Themes and Apps] eliasba:
Hi Guys I'm proud to Provide My New Concept Theme From ANTP Series But it contains some Bugs but You can try it

What I Themed :

_Status Bar (Red Style)

_NavBar (SWORD Png Style/ white Backgrond)

_Some Apps Themes To (White And Red Colors)

_FHD Wallpapers

_Red Xperia Home SideBar

Bugs :

_Navbar Not Working in Some Devices

_NavBar Png Bugs In Screen Rotation

_Tell Me If You Find More Bugs

Download :

_Here

Theme version : 1.0 Alpha

Last update : Mar/11/2016
[Sony Cross-Device Development Themes and Apps] n78 shadow:
Good work bro :)

keep up the good work :good:
[Sony Cross-Device Development Themes and Apps] Meo15:
Nice bro
[Sony Cross-Device Development Themes and Apps] AkemiKaito:
Wow

How did you do that *^*