yashsingh1/xdaforums huggingface dataset:
[Android General] mrshark:
never activated it, even if installed, but the constant FCs were of gmail and calendar... i can't try now, passed 2 hours in testing and now battery is gone and charging :D

do you plan to fix this, if you can? Other gapps packages don't install at all or i've to remove many apps because they fill the system partition (even if i successfully flashed about EVERYTHING using your package)...
[Android General] Rapper_skull:
GApps are meant to be installed on top of AOSP ROMs that do not include already some of the Google Apps. Your ROM is not an AOSP ROM, but my package is meant to be installed on top of Stock ROMs, that already include GApps. The problem is that your ROM not only includes some GApps, but they're also in the wrong location, and installing a GApps package would bring to conflicts. I updated my package to remove the GApps installed in your ROM too, so that there should be no more FCs. Also you'll gain another 34MB of space to include even more GApps to your config (you don't have to exclude TalkBack and Messenger anymore if you want). The updated package is currently uploading and will be available tomorrow or later today, depending on your timezone.
[Android General] mrshark:
thanks a lot, you're great! There's no other packages that allow to keep gapps in rom updated in stock roms that already have them, like OPO cm12s...

i didn't remove those apps for lack of space (there are STILL 136mbs free, even though i flashed the big STOCK package and other personal stuff like franco kernel, mooab adblocker, maxxaudio and supersu, too)... i removed talkback because don't use it, and messenger because i use hangout, instead :)

what do you think of EMAIL? in stock rom it's named EMAIL, but it's really BOXER, the email client made by cyanogen and released as full app just for OPO... do i have to explicit put a line like "+Email" in config or it's left untouched, as email is the stub for the old email client made by google?

tomorrow i'll download and flash your new gapps package, thanks again! :)
[Android General] Rapper_skull:
Boxer will not be removed and +Email is unnecessary. However I added the Boxer keyword to remove the CM Email client if someone wants to.
[8525, TyTN, MDA Vario II, JasJam ROM Development] dextran:
I got headache to choose, to keep my rom up to date!I'm still using custel 2.5. A lot of newer roms nowadays. Very positive growth.... Custel 2.5, Elf 2.1, Faria, Black 3.5 With Live Removed and Extra Storage, Black Dymond, vp3G's, LVSW, dutty's v2. and so many :). Give me advice please.
[8525, TyTN, MDA Vario II, JasJam ROM Development] vp3G:
Well duh, mine of course! ;)

Seriously though, one of the best things about this place is so many ROMs to choose from. Each has it's merits (and it's quirks!). Just pick one, try it on and see how it fits you.

P.S. You missed one flavor in your list. Sleuth255 has put together a very nice LVSW variant as well. When in doubt, check the WIKI. I just updated it today, in fact. :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] pietrucci:
Last weeks I installed almost all of them and (non-scientifically!) benchmarked their performance... See my post: http://xdaforums.com/showpost.php?p=1284362&postcount=15

My conclusion: they all are stabile and have more or less the same performance (I think because they have more or less the same core.... sorry chiefs).

The one you could pick is the one with the extra's and addons you want...

My personal experience: LVSW Sleuth edition is very good!

At the moment I'm trying Faria..
[8525, TyTN, MDA Vario II, JasJam ROM Development] viczena:
i tried every rom (including black dymond). when it comes to stability, nothing compares to lvsw and the derivates. i use elf 2.1. nice combination of features, working bt, fast and STABLE.

what i dont need is a pimp machine with soft reset every two hours...

peter
[8525, TyTN, MDA Vario II, JasJam ROM Development] LegolasTheElf:
I think mine is the best.. Actually, mine is unique in how it's built. I did cook some minor (and vital) things into the rom itself, but most is added via. ExtRom customization with all cab's modified to allow removal :) So, if you want Live, it's there. If you don't, just remove it. etc.. It's a different way to cook, and one that requires a whole lot of CAB modification.

My Live cab is different than any other cab on this site. I hand modified it to install in the way I wanted, and work the way I wanted. Personally, I think it's the best cab around -- and exclusively for Elf 2.1.
[8525, TyTN, MDA Vario II, JasJam ROM Development] dextran:
thank you. Very good benchmarking and very hard work! I'll try LVSW Sleuth edition.
[8525, TyTN, MDA Vario II, JasJam ROM Development] dextran:
I have used Elf 1.0 . It is very nice and marvelous build. But I got problem with battery charging. Then I tried black dymond and faria yesterday. But I have to go back to CUSTEL, because I feel more stable and more memory. Just now I tried Black 3.5 With Live Removed and Extra Storage and now I test Elf 2.1. :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] pietrucci:
Haha, you're proud of your work!

I'll soon give your version 1.2 a (longer) shot...
[8525, TyTN, MDA Vario II, JasJam ROM Development] LegolasTheElf:
I like my ROM. :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] dextran:
CUSTEL still won Program and memory space. Faria, LVSW Sleuth edition and Elf 2.1 won the speed. LSLW based won the most stable. Which one do you prefer most? :cool: Do you agree with this conclusion?
[8525, TyTN, MDA Vario II, JasJam ROM Development] bchau:
Elf V2.1 works for me

I haven't tried all so I can't compare. Indeed I have only flashed my JASJAM yesterday for the first time with Elf V2.1. So far it has been working great for me. For those who has been hesitating to take the plunge, I would say read the WIKI. Make sure you know what you are doing. Then do it. I did that and I am a happy man. And I am sure many of these ROMs are all great. We (and MS) are lucky to have this great community to support this WM platform.

Cheers.
[8525, TyTN, MDA Vario II, JasJam ROM Development] dextran:
I agree with you. Their hard works are very great. Everybody in this forum and out there can't deny this.
[8525, TyTN, MDA Vario II, JasJam ROM Development] dextran:
LVSW 19-05-2007 Sleuth edition and Elf2.1 are very nice to try. So I test Elf 2.1 first. Sleuth still on downloading... rapidshare got a little bit slow.
[8525, TyTN, MDA Vario II, JasJam ROM Development] xit:
cool topic

What a great thread to read peoples summary experiences. This kind of thread would have been previously scoffed at with ' go read for yourself ' replies by some that have left this forum except to throw the odd spot remark.

I am currently using FARIA after trying some of the Black and LVSW variants. I like FARIA a lot because of the addin utils, and am not concerned about only 20Mb free after boot. I make calls and use TomTom, not much more.

The MAJOR thing that I like about FARIA is that now my car charger works, whereas all the other ROMs didn't allow the car charger to work - go figure!

Thanks to all the contributors and chefs who hold true and know when to reply and when to ignore some of the less experienced users questions. Its about COMMUNITY, not superiority. Thanks, and may your sheep be blessed with a thousand lambs. :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] dextran:
I like FARIA especially on startup, date/time finishing and speed. But it's addons take much memory so I have to reset so many times especially after using MAPKING and WIFI. I'll like FARIA if it a lite version with an option addons.
[Droid RAZR M Q&A, Help & Troubleshooting] Don.Patrone:
Hello good people

I currently have Slim Rom 4.1 installed on my verizon XT907 but I have all kinds of issues with bluetooth and mobile data which doesn't seem to work.

I know asking for "the best rom" is forbidden but instead I ask for a fully functional one. That and better battery life is all I need. So far I couldn't find one that meets those requirements.

Thank you.
[Droid RAZR M Q&A, Help & Troubleshooting] xKroniK13x:
If you're looking for 100% functionality, go rooted stock debloated/deodexed. Won't have many features but everything will work.

Sent from my Blissful RAZR M 5.1 from Tapatalk
[Droid RAZR M Q&A, Help & Troubleshooting] Don.Patrone:
Tbh I was (and still) looking for a stock debloated clean rom and that one seemed to be the one. But for some reason essential functions don't seem to work.
[Verizon Samsung Galaxy Note II] ozo012:
Hey guys,

I flashed Cyanide L on Friday morning with a clean install etc.. and my phone seems to have bricked itself while on the charger from Friday night into Saturday morning. I used it most of the day Friday and it seemed fine other than 1 random reboot. My phone will not boot past the Galaxy Note II screen when the phone first turns on, I can boot into recovery (Philz) but I don't see anything on the screen when I do (I get haptic feedback when I touch anywhere on the screen but I can't do anything.)

I tried for about 5 hours to use Odin in download mode and return to either 4.1.1 stock or 4.1.2 (I know using Odin to restore 4.3 will lock my bootloader which I am not interested in doing). However, Odin keeps failing when trying to write the recovery image to the phone. Does anyone have any tips or suggestions for what I could do next?
[Verizon Samsung Galaxy Note II] mattnmag:
Here's an older post with links that might be helpful ( http://xdaforums.com/showthread.php?p=57944591 ).

Make sure you're using the pit file when flashing the appropriate firmware in Odin.

Some common issues with Odin also are to make sure you're using a USB 2.0 port on your computer and use the phone's original USB cable or a good quality one if you don't have the original any longer. Also run Odin with Administrative privileges, make sure that Kies is not running in the background because it interferes with ODIN, and disable antivirus programs when running Odin.
[Verizon Samsung Galaxy Note II] ozo012:
Yeah something went wrong in Odin when I flashed the stock recovery the last time and I corrupted my EMMC as Product Name: (Blank) is showing up now.

RIP Note II it was nice knowing you.
[Verizon Samsung Galaxy Note II] mattnmag:
Man... that sucks! I wonder if it was actually Odin, or if the EMMC chip just died. Either way, it doesn't really matter now. RIP Note 2.
[XDA Assist] XDA Visitor:
My Samsung Note 4 (sprint) is boot looping, and the Download mode crashes so I can't flash it or anything, i think its really broken and I need your guys help to fix it,

Thank you!
[XDA Assist] karandpr:
Hi

You will need to sign up on forums and post in Note 4 section

http://xdaforums.com/note-4/help

Please post in detail about your device in that section, including how you bricked your device .

Good day !
[General Questions and Answers] seandarcy:
I'm looking at the P 6000 and the P 7000. Both look like great phones, but neither has the US LTE bands. These phones have LTE bands 1, 3, 7 and 20 . None these are used in the US.

I'm pretty sure the MTK SoC can use a lot more LTE bands. Why aren't they enabled? This is also true of Qualcomm phones: the qualcomm SoC's can use 20-30 lte bands, why aren't all enabled? Battery ?

And yes I get the market discrimination argument, that this enables the manufacturers to price the phone differently in different markets. But even 2nd tier mnufacturers ? And why not a premium price for a global phone?

Is there a technical reason for limiting LTE bands?

sean
[Nexus 9 Android Development] NYCHitman1:
Great post. This should be helpful for those that desire to begin learning how to compile their own ROMs. :good:

As for the vendor fix, you can find it in Craig's Lollipopalooza thread or mine (DU).
[Nexus 9 Android Development] KedarWolf:
I tried the vendor fix from the Lollipopalooza thread, for some reason it never worked. :rolleyes:

Thanks though, hoping someone will find a working fix.
[Nexus 9 Android Development] mpmilestogo:
First off thanks for the great tutorial. I did this on Debian testing the other day with only minimal changes for the apt-get install part. It took me about 4 hours to sync the repo and about 2 hours to build on my older x220 thinkpad. Well worth it for the learning experience. The best thing however was flashing my very own build.

Thanks for the guide. I had a great time producing my very own ROM.
[Nexus 9 Android Development] KedarWolf:
No trouble. Glad it went well for you.

Peace. :good:
[Nexus 9 Android Development] TemporaryTester:
Hmm, tried this, but Bluetooth seems to be broken for some reason... Any pointers to where I might have screwed up?
[Nexus 9 Android Development] tomkins0752:
Great, Clear, Concise Instructions

Thanks so much for the clear write up. :good:

I've been trying to compile builds for my N4, N5, and N9 for a few days now, but none of them will boot, nor will they go beyond the initial Google splash screen.

They will state that the build has finished, but they don't boot.

Maybe you have a few pointers to share?

My system includes an i7-4770 and 16GB RAM and I'm running 14.04 Ubuntu x64.

It also has a 240GB SSD just for OSs and a 2TB HDD, and is dual booted with W8.1.

:confused:
[Nexus 9 Android Development] KedarWolf:
I never tested bluetooth but apparently there is issue with it. According the the Lollipoppalooza thread there is a GitHub bluetooth fix. I will update the guide when I figure out how to add the GitHub fixes to this build.

http://xdaforums.com/showthread.php?t=2763236 is a thread on how to add GitHub cherry picks to a build and the cherry picks are found in the posts here http://xdaforums.com/nexus-9/develo...r-volantis-t2933831/post57925047#post57925047 if you want to try to do it yourself.

I did have trouble adding the cherry picks but I may be able to figure out a fix and add it to the build. First cherry pick I figured out the problem, just the second one I need to do as well.
[Nexus 9 Android Development] KedarWolf:
Did you wipe your device in Hboot in bootloader mode before installing the zip? The wipe may not be working right in TWRP. If you add this version of TWRP https://basketbuild.com/devs/USBhost/Nexus 9/recovery/TWRP and flash this zip AFTER you install the regular TWRP then the wipe will work correctly and you don't need to boot into bootloader mode and wipe in HBoot. Also if you are trying to use a custom kernel and not have your device encrypted you need to wipe using this TWRP. I had a error in Hboot and the disable encryption wipe didn't work.

Also if you want to see if it's a problem with your build download the zip in the first post of the build I made and see if it works after you wipe in Hboot.

The only other thing I can think may be wrong is a problem with your bootloader. You might want to try the flashing the bootloader from theLRX21R factory image steps found here., just scroll down. http://xdaforums.com/nexus-9/development/rom-lollipopalooza-flounder-volantis-t2933831
[Nexus 9 Android Development] tomkins0752:
Thank you for the reply.

Interestingly enough, nothing compiles into a zip. I don't believe everything is actually being built even though terminal will state it is complete.

Your build works on my N9, but nothing I build works on any of my Nexus devices. I've tried with a N4, N5, and N9.

I included a screencap of each of my different device builds.
[Nexus 9 Android Development] KedarWolf:
Do you have enough space on the drive you're building to? I think when I checked my build AOSP folder is was 80 GBs or something crazy like that.

And did you use 'make -j12 otapackage' it doesn't make the zip without the otapackage on the end, if you don't different process for flashing the files.
[Nexus 9 Android Development] tomkins0752:
Yeah I'm working with 700+GB partitio on my 2TB drive.

I didn't include "otapackage" at the end, so I'm trying that now.

I had followed the instructions from the Android Source page.
[Nexus 9 Android Development] KedarWolf:
Okay, let me know how it goes.
[Nexus 9 Android Development] slebit:
Are you using the binaries files that are required for mako and hammerhead? Flounder have a special partition for vendor files, that is why we don't have to use binaries files from outside...
[Nexus 9 Android Development] KedarWolf:
Yes, that is true, for example for the Nexus 5 add these steps. Do similiar for the Nexus 4 and/or Nexus 7 with the binaries for them.

Now you get the source code etc: repo init -u https://android.googlesource.com/platform/manifest -b android-5.1.1_r1

Followed by: repo sync -j12

Use repo sync -j12 for a quad core CPU or Intel I5 or if you have say an quad core I7 with 8 threads you can use repo sync -j24 to speed things up etc.

I have a I7 3930k with 12 threads so I used repo sync -j36. This gives you three threads per logical CPU and speeds things along quite well.

It may take several hours for the sync to finish.

After the sync finishes go to https://developers.google.com/android/nexus/drivers#hammerheadlmy47i and download the LMY47I (binaries) for the Nexus 5.

If you have closed the Terminal after the sync remember to first do this when you reopen it: cd ~/AOSP

when you open Terminal again before doing the cp and tar commands.

In Terminal: cp ~/Downloads/broadcom-hammerhead-lmy47i-4129297c.tgz ~/AOSP

Then: cp ~/Downloads/lge-hammerhead-lmy47i-1a387ac9.tgz ~/AOSP

And: cp ~/Downloads/qcom-hammerhead-lmy47i-41f93087.tgz ~/AOSP

In Terminal: tar -xvf broadcom-hammerhead-lmy47i-4129297c.tgz

And: tar -xvf/lge-hammerhead-lmy47i-1a387ac9.tgz

then: tar -xvf qcom-hammerhead-lmy47i-41f93087.tgz

They should be the file names of the binaries for LMY47I that you are extracting but if for any reason the file names are different use the Tab key and tab the correct names in after 'tar -xvf'.

If the names ARE different I'd really check to make sure you downloaded the correct hammerhead binaries.

Now also in Terminal: ./extract-broadcom-hammerhead.sh

Then: ./extract-lge-hammerhead.sh

And: ./extract-qcom-hammerhead.sh

Hint: It will show you a really long licence agreement for each binary that you scroll by hitting the Enter key that takes forever to scroll one line at a time, it has 8 sections and several subsections. Hold the Enter key until you just get past Part 8, section D of the licence and stop there. Now hit enter a few more time one key stroke at a time until you finish Part 8 section E and see the 'Type 'I ACCEPT' to agree to the licence.' and type I ACCEPT If you just scroll by holding the Enter key all the way to the bottom of the licence you'll get an error you never accepted the licence. Then close Terminal.

Then follow the rest of the guide.
[Nexus 9 Android Development] KedarWolf:
I'm trying a fix to the build I found and am building the 64 bit AOSP now. When the build is done will test bluetooth and let you know if it worked. :D
[Nexus 9 Android Development] tomkins0752:
I got my build to boot after a couple wipes and such.

Thank you for the guide. It helped clear things up.
[Nexus 9 Android Development] fhem:
You can check out what I'm doing here -------> https://github.com/fwhem/platform_manifest.

BTW I have been running KDE Mint 17.1 64 bit on two machines since it's release with no issues.

also you can manually text edit the vendor build.prop fingerprint to match the system build.prop fingerprint to eliminate the boot error message until we get a new vendor image.
[Nexus 9 Android Development] KedarWolf:
There is a new build out that officially supports the Nexus 9. I updated the guide to include this, basically just change the build to repo init -u https://android.googlesource.com/platform/manifest -b android-5.1.1_r2

Not sure if this fixes the blue-tooth but i'll do a build tonight when I get home from work and check.
[Nexus 9 Android Development] KedarWolf:
Build android- 5.1.1_r3

I'm currently building 5.1.1_r3 to see if it fixes blue-tooth. You just change to this repo init -u https://android.googlesource.com/platform/manifest -b android-5.1.1_r3

Been having trouble fixing conflicts by adding Git repository fixes for blue-tooth or I'd post them in the guide.

In an earlier post is how to use Git and the three repositories someone suggested be used if anyone wants to try them. Someone I messaged privately said you could just use the first repository from the link to that forum and I did seem to get that repository working and added but blue-tooth still never worked

Sorry I haven't figured out a fix, I've spent hours on just that. :(
[Nexus 9 Android Development] akaempf:
Does anyone have a plain ASOP build with Bluetooth and all working they would be willing to share... Seems like their isn't a current 5.1.1 build shared of a stock ASOP without mods... I currently do no have an environment available to build on lacked... Thanks
[Nexus 9 Android Development] fhem:
Here you go https://www.androidfilehost.com/?fid=23991606952608988

Only one commit added for bluetooth https://github.com/fwhem/device_htc_flounder/commit/de462b91ccf2752abf167c82492c6232cf25853e it works.

Also it no longer overwrites recovery YEA!!!!!! :good::D

BTW that message about fingerprints not matching still shows on boot,
[Nexus 9 Android Development] NYCHitman1:
Set a build.prop override in your device tree to match the config from the build.prop on the vendor partition.
[Nexus 9 Android Development] fhem:
Thanks. That will work. I actually do this https://github.com/fwhem/platform_frameworks_base1/commit/a6cb1114b7cd0d6e3ad3203ca04c24d70e42b2e5 for my git builds. The one I posted above was just a clean test build to see what was happening w/o any mods.
[Nexus 9 Android Development] akaempf:
And the test build works terrific... have found no issues and use it about 8 hours daily... thanks again
[Nexus 9 Android Development] KedarWolf:
Android M Preview Available

Hey all,

Actually, this may be bad advice below. I think the Android M Preview doesn't need GAPPS and I know if you root it with SuperSU softbrick your device. I'm testing a build now with and without the blue-tooth GitHub commits to figure out how to get it working right and when I do get it working will say the right way to root it.

The Android M Preview is available to build for the Nexus 9. If you want to try it use repo init -u https://android.googlesource.com/platform/manifest -b android-m-preview Will see if it fixes the blue-tooth issues when I get home from work later tonight.

Peace,

KedarWolf
[Nexus 9 Android Development] KedarWolf:
I just saw where someone found a blue-tooth fix. :D

Not sure why this thread stopped notifying me of new posts. :rolleyes:
[Nexus 9 Android Development] KedarWolf:
Thank you!

I'm going to test that commit tonight on the latest build (not Android M) and if I can get it to work add the steps to my build guide for working blue-tooth. I know commits can be a bit of a pain to get working right.

Thanks for your help!
[Nexus 9 Android Development] fhem:
read this

go to ~/yourbuilddir/device/htc/flounder/ and open terminal or cd to ~/yourbuilddir/device/htc/flounder/

then this

git fetch https://github.com/fwhem/device_htc_flounder.git
git cherry-pick de462b91ccf2752abf167c82492c6232cf25853e

done ---- should pull in with no conflicts

build it
[Nexus 9 Android Development] KedarWolf:
Yeah, I know from exactly that guide how to do commits, I think I linked to the same guide in an earlier post. Conflicts can be trouble though. I'm home doing a new build now. Hope it works okay, I kept getting 'Not on any branch' issues earlier commits and think I figured that out but still no blue-tooth. Different commits then yours though.
[Nexus 9 Android Development] KedarWolf:
I thought about what you said and I'm trying to build without fixing the 'git status' 'Not on any branch' problem'. Trying to fix that may be why my past commits were not working to fix blue-tooth. Just do the cherry pick like you said. Here's hoping.
[Nexus 9 Android Development] KedarWolf:
I now have working blue-tooth AND the boot error is gone.

Thank you. My mistake adding previous commits was attempting to fix the 'Not on any branch' errors. But your commits work great if I just ignore that.

I'm uploading the new build WITH working blue-tooth to my OP. :)