yashsingh1/xdaforums huggingface dataset:
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Did you give up on the r1
[BLU R1 HD Guides, News, & Discussion] triggerlord:
The r1 doesn't support Sprint (right?). So rip.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Pop in the sim and find out
[BLU R1 HD Guides, News, & Discussion] triggerlord:
Maybe I'll give this a try later. :D

I have the Moto E now, so I won't be using the r1 as my main phone unless it gets CM. But it would be cool to see if it works.
[BLU R1 HD Guides, News, & Discussion] :
Nope. Unlike Verizon, Sprint doesn't have that weird GSCDMA (or whatever it is) thing, so a Sprint SIM card really is ONLY for LTE. And as far as I know, the SIM won't work unless that phone is also registered on the CDMA network, so no R1 HD on Sprint :)

I severely doubt that it will work on Verizon either, but at least there is a better chance thanks to the GSCDMA thing.
[BLU R1 HD Guides, News, & Discussion] triggerlord:
Lol, maybe the data will only work then. I've popped the sim out before and everything kept working on the Moto E except LTE. The Sprint Moto E does support other GSM/CDMA networks too.
[BLU R1 HD Guides, News, & Discussion] :
Yep. As long as it's not activated on Sprint, the Sprint Moto E should take any old SIM card for a GSM network with no problem.

As for data working with a Sprint SIM, I don't think it will. I believe the SIM requires the IMEI to be registered on Sprint as well to actually work.

Verizon uses SIM cards in LTE phones the same way GSM networks do. It not only activates LTE, but it also activates all the other CDMA features. I have no idea how it works, but I believe it's a technology that is sort of a cross between GSM and CDMA (I believe it's called GSCDMA, correct me if I'm wrong). Sprint does not use this. All the non-LTE radios of your phone are activated the old-fashioned CDMA way (by having your IMEI registered on the network), and the LTE radios are activated with a SIM card. I believe Sprint's LTE network also has a whitelist (like MetroPCS) so you cannot activate a phone on it if it's not activated for CDMA features on Sprint's network.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
And I was a dingus and traded my Sprint Moto E for the Verizon one to use it with T-Mobile. If only you were there 10 months ago.
[BLU R1 HD Guides, News, & Discussion] triggerlord:
Why??? Doesn't the Verizon version have a locked bootloader? The best part of the Moto E is the ROM community.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Didn't know sprint one could be used for GSM till Colton ruined my day
[BLU R1 HD Guides, News, & Discussion] :
All CDMA Moto Es work on GSM network. I forget, maybe one of them requires something basically equating to a carrier unlock first, but I forget which one, and I think it is a trivial unlock.
[BLU R1 HD Guides, News, & Discussion] triggerlord:
I just tried my Sprint sim in the r1 HD. It does detect and display that it's a Sprint sim but nothing works. Not even data.
[BLU R1 HD Guides, News, & Discussion] ramious2012:
The Moto E in need of the unlock is the Tracfone ie straighttalk version the XT830C. . I just ordered my Blu R1 HD today, got the no ads version 16 gig. I can't wait to have it !!!!! I am coming from an LG Treasure from straighttalk the L52VL, and Locked down tight by Tracfone. I have vowed to never purchase a carrier branded phone , I all so excited about the community support this device is receiving, now I have a Reason to crank up my xda app. I look forward to talking with everyone and rejoining the community after two years of no Root. Yey Free At Last!!!!!
[BLU R1 HD Guides, News, & Discussion] :
Yep, Tracfone is really bad about locking down their phones. I suspect that this is due at least in part to them being an AT&T MVNO, because other Tracfone brands such as Net10 and SIMple Mobile aren't as bad about it.
[BLU R1 HD Guides, News, & Discussion] calm_depression:
Any update on cm?
[BLU R1 HD Guides, News, & Discussion] yaconsult:
The Blu R1 HD is way, way, WAY better than the Moto E! And very easy to root and reflash to the non-amazon version. I mean, for $60, I don't think it's worth hassling with the Moto E.

Re cyanogenmod - check out the thread: http://xdaforums.com/r1-hd/development/blu-r1-hd-ready-devs-t3439272 There didn't seem to be a lot of interest from the usual developers, but at least some people are playing with it. Apparently, the MediaTek chipset is not very popular in those circles. I am glad that we have xposed and gravitybox to give us a great degree of customization, even with the stock rom.
[BLU R1 HD Guides, News, & Discussion] triggerlord:
I agree that the R1 HD is better hardware wise. I never said it wasn't. Lol. But if custom ROMs are your thing, the Moto E is the better choice. You just can't beat Qualcomm for custom ROMs. That said, if the phone worked on Sprint, I'd still be using it over the Moto E.
[BLU R1 HD Guides, News, & Discussion] kal250:
Is it just me or does it seem like the hype has slowed down. I hope it's just a lull in activity, I really want to see this thing take off!!!
[BLU R1 HD Guides, News, & Discussion] onlykhaz:
Maybe it's because Nougat thing... I'm also waiting for some good news from the devs :fingers-crossed:
[BLU R1 HD Guides, News, & Discussion] nbpanjwa:
Is it safe to flash baseband of BLU R1 HD on my device?

Is it safe to flash baseband of BLU R1 HD on my device? since it appears to be an incremental update to my baseband version. I have a Mediatek device MT6735 with baseband version MOLY.LR9.W1444.MD.LWTG.MP.V8.P68 where as BLU R1 HD is MT6735 with baseband version MOLY.LR9.W1444.MD.LWTG.MP.V79.P14. I don't know how version numbers are created but I know that Mediatek ARM®Cortex-A53 processors are highly integrated baseband platform incorporating both modem and application processing subsystems to enable LTE smartphone applications. I'm also aware that MT6735 is GSM/ CDMA capable worldphone, only if some expert come up with a utility that can unlock all bands like they have one for Snapdragon, but that is not what I'm looking for right now.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Porting Is Not Going Too Well

Yeah I gave up on Nougat because the only available device tree I could find was for CM13, and I don't think CM and AOSP device trees are cross-compatible.

Anyway, even porting CM13 is giving its own set of troubles. I posted about it in the general Q&A section of XDA, but I'll quote it here in case any of you guys can help.

EDIT: Now that I think about it I'm gonna abandon this CM building for now and jump over to Nougat once again and see if I can get that working

EDIT 2: Porting AOSP isn't as new-device friendly as CM seems to be so for now I'm giving up on Nougat and jumping back over to CM13
[BLU R1 HD Guides, News, & Discussion] :
Ayy but once we get CM 13 running, porting CM 14 should be within reach. Don't give up hope on Nougat yet.

EDIT: That said, CM is a good first step, but I want to get AOSP building too. CyanogenMod used to be great, but lately it hasn't been so good. I would like to get AOSP building so that maybe some day we can have a Candy ROM. :3
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Id stick with AOSP but the device tree made by GitHub user anpage is made for CM13. If you or someone else can make a device tree compatible with AOSP I can certainly try Nougat as well. Of course, first I need to figure out what the hell is wrong with CM not wanting to build.

EDIT: Got lunch to see my device, now it just says there are missing dependencies and it bails out.

Looking for dependencies

Dependencies file not found, bailing out.

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=6.0.1

CM_VERSION=13.0-20160829-UNOFFICIAL-p6601

TARGET_PRODUCT=cm_p6601

TARGET_BUILD_VARIANT=userdebug

TARGET_BUILD_TYPE=release

TARGET_BUILD_APPS=

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a-neon

TARGET_CPU_VARIANT=cortex-a7

TARGET_2ND_ARCH=

TARGET_2ND_ARCH_VARIANT=

TARGET_2ND_CPU_VARIANT=

HOST_ARCH=x86_64

HOST_OS=linux

HOST_OS_EXTRA=Linux-4.4.0-34-generic-x86_64-with-Ubuntu-16.04-xenial

HOST_BUILD_TYPE=release

BUILD_ID=MOB30Z

OUT_DIR=/home/administrator/WORKING_DIRECTORY/out

============================================
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Built CM13 from source, running into compilation errors now. At least it's building.

EDIT: Here's the problem I ran into:

make: *** No rule to make target 'vendor/cm/charger/fonts//font_log.png', needed by '/home/administrator/WORKING_DIRECTORY/out/target/product/p6601/obj/ETC/font_log.png_intermediates/font_log.png'

I'm searching far and wide but can't find anything. What to do?

EDIT 2: Fixed that with a modification of the device.mk file, now I'm running into another error. If this build fails I'll post the error.
[BLU R1 HD Guides, News, & Discussion] onlykhaz:
Wow, thanks for posting this, it gives us hope and it may wake up other devs to play with the kernel and make great things :good::good:
[BLU R1 HD Guides, News, & Discussion] triggerlord:
Maybe this can help? https://wiki.cyanogenmod.org/w/Development#Learning_To_Build_CM

Here's the page with the build errors on it: https://wiki.cyanogenmod.org/w/Doc:_dealing_with_build_errors
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Tried that, tried directly copying the needed file, but it didn't work. I spoke to someone on an IRC board about fixing it and I fixed the initial one, now I'm getting a similar error with a different file.

EDIT: Here's the error:

make: *** No rule to make target '/home/administrator/WORKING_DIRECTORY/out/target/product/p6601/obj/STATIC_LIBRARIES/libminui_intermediates/export_includes', needed by '/home/administrator/WORKING_DIRECTORY/out/target/product/p6601/obj/EXECUTABLES/healthd_intermediates/import_includes'. Stop.
[BLU R1 HD Guides, News, & Discussion] ariesgodofwar:
Anything we can use here? http://xdaforums.com/jiayu-s3/development/rom-unofficial-aosp-n-jiayu-s3-plus-t3448724 I think it is MT6753
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
I'd look into it, but the problem is I have no idea which mk file my problems are arising from. Not even Google seems to know.
[BLU R1 HD Guides, News, & Discussion] Abel Fernández:
Please help me...

I need help i have one error in SP Flash Tool, Say: BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (0x13BE)this error is but the ROM is incompatible.

Please i need the ROM flashable with SP Flash Tool Of BLU R1 HD, the exact model:R0030UU but i brick my Blu R1 with the backup of R0010UU but that is 8GB/1GB and i have 16GB/2GB Amazon version...

If anyone have one of this, PLEASE use a extractor Of ROM and upload it... PLEASE, Thanks.
[BLU R1 HD Guides, News, & Discussion] bullet25:
So this has been my experience trying to build AOSP or CM recently.

Look up guides and info, all outdated from 2014 or eairler. Follow as best as I can. Get errors. Google errors. Find nothing. Ask around. Get, I'm not kidding, "You need to learn the basics of ROM building first." Look at other devices. Modify files to look more inline with the other devices. Get different errors. Google errors. Rinse and repeat until I give up for the month.
[BLU R1 HD Guides, News, & Discussion] kal250:
All of the flashes here are based on R0010UU or R0011UU, honestly I think it came from factory that way. I have the 16/2 prime and using both Coltons ans rootjunkys methods and scatters have worked fine for me and I have done over 5 flashes between the two without error.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Are you getting the same errors as I am?

Also, try the #cyanogenmod-dev freenode irc. There's never anyone around but when there is they're usually helpful.
[BLU R1 HD Guides, News, & Discussion] bullet25:
The last time I was trying I was getting a kernel compile error. Can't remember exact error right now. Work is dying down in the next month or so, so I might try again later.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
I'm not sure if my errors were kernel compilation or general ROM compilation, I'll have to look more closely at the terminal next time. Mine had to do with links not being able to be made between files, pretty much all of them being something along the lines of "There's nothing in any configuration file that tells me what to do with XXX file that's needed by XXX other file". I've solved one about battery font by adding a line in the device.mk that specifies the screen is MDPI resolution, but more arise after that. I guess I'll have to look at other device configs that are similar and just pull from those.
[BLU R1 HD Guides, News, & Discussion] triggerlord:
Are you building with GCC or Clang? Apparently Android can only be built with Clang now.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
I have no idea. I just do "make bacon".
[BLU R1 HD Guides, News, & Discussion] triggerlord:
You're probably building with GCC then as it's the default on Linux.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Do you know off hand how to go to Clang?
[BLU R1 HD Guides, News, & Discussion] triggerlord:
http://llvm.org/releases/download.html then use cmake instead of make.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Tried cmake, requires some additional files. Just gonna stick with make.
[BLU R1 HD Guides, News, & Discussion] bullet25:
I'm pretty sure that "Make Bacon" will make for the One plus One. I think you'd need to use "Make [Device code name you are using]" so "Make R1_HD" or "Make P6601" depending on how you have files set up.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Are. You. ****Ing. Kidding. Me.

I was under the impression that make bacon was used to make a flashable zip for the device you previously specified in lunch. Thanks for clearing that up, you saved me mucho time.
[BLU R1 HD Guides, News, & Discussion] travlock:
Accidentally left twitch open last night which forces the screen on. Might have been idling all night but damn!
[BLU R1 HD Guides, News, & Discussion] bullet25:
I could be wrong but isn't the code name for the One Plus One "Bacon". At least that was the impression I was getting from looking through the stuff.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
I assume the guide I was using was a generic guide, but you are right about the codename being bacon. When you run "make cm_p6601" does it do things?
[BLU R1 HD Guides, News, & Discussion] bullet25:
Now there's the problem because the "Make cm_p6001" won't do anything unless you have the .mk files created correctly. At the time I was doing it myself I had setup the code name as "R1_HD" because that's what I assumed it was. I might try again with the p6001 tree that was posted awhile ago. I have to re-image my laptop back to Ubuntu. I had put the Win10 image back on to update it and haven't gotten back to putting the Ubuntu image back on it.

This is the last guide I was following: https://wiki.cyanogenmod.org/w/Doc:_porting_intro

And its where I got stuck at the Kernel. It didn't seem to want to be accepting the pre-build kernel file and I couldn't figure out at the time how to use the source.

Again as a post note: My knowledge of this is cobbled together from random guides mostly out of date.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Don't you worry, I'm on the same boat as you. I have no experience doing this either.

I was using GitHub user anpage's device tree. I did make one small change in the device.mk file and forked it over to my repo which solved a compilation error regarding font, so if you want you can try mine (username is same as on here). I've got a few errands to run but I'll be back at my desk in a bit.

I'm also trying to compile AOSP Nougat with the CM device tree. I left my PC at home downloading the N source. I read CM trees may not be compatible but I'm going to try anyway.
[BLU R1 HD Guides, News, & Discussion] bullet25:
I know the Zenfone 2 has been useing L source codes for the CM13 build for a long while now with little enough problems to become official. How they do it I don't know.

I know the CM trees need a bit of modifying to work with AOSP. From what I could gather AOSP and CM use different .mk files.

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

I know the Zenfone 2 has been useing L source codes for the CM13 build for a long while now with little enough problems to become official. How they do it I don't know.

I know the CM trees need a bit of modifying to work with AOSP. From what I could gather AOSP and CM use different .mk files.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Now the problem is going to be figuring out how to make mk files for AOSP. The only page I've seen guides for making those are from CM. I'll probably just stick with CM.

I know I'm jumping back and forth a lot but I'm just trying to find some good news to keep me motivated.
[BLU R1 HD Guides, News, & Discussion] bullet25:
I'd personally say stick with CM anyway.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
I think I messed up repo by initializing the AOSP source and syncing that. Do you know the repo init command offhand to set it to the CM13 sources for when I get back home?
[BLU R1 HD Guides, News, & Discussion] bullet25:
repo init -u git://github.com/CyanogenMod/android.git -b cm-13.0

---------- Post added at 12:04 PM ---------- Previous post was at 12:04 PM ----------

repo init -u git://github.com/CyanogenMod/android.git -b cm-13.0
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Checked just now. You do use "make bacon". The other command just says "no rule to make p6601"
[BLU R1 HD Guides, News, & Discussion] wilberzone18:
help

please help how to install TWRP on my blu r1 hd? I'm new just bude unlock the bootloader error but I want to install the recovey
[BLU R1 HD Guides, News, & Discussion] triggerlord:
I'm pretty sure that command is for the OPO. https://wiki.cyanogenmod.org/w/Build_for_bacon#Start_the_build

Here's the build guide for surnia: https://wiki.cyanogenmod.org/w/Build_for_surnia#Start_the_build

You'll notice it says "make surnia".
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
When I run make bacon, the files are built to the folder "out/product/p6601/"
[BLU R1 HD Guides, News, & Discussion] triggerlord:
I made an edit. Read the second part. :D
[BLU R1 HD Guides, News, & Discussion] bullet25:
Okay so when I was doing it with "R1_HD" and ran "Make R1_HD" I got an actual error. I know for the Zenfone if you want to make that you actually run "Make z00a"

You could be getting and output folder for "out/product/p6601" if you modified something from the OpO. Not too sure though.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
UPDATE: Getting a bunch of errors sayimg I'm missing a bunch of .h libraries from a /sys/ subdirectory. I've been downloading them from Google search results from various sites. I'm afraid these files are device-specific, so for now I'm going to put the brakes on ROM development, at least until the other guys update the device tree enough to get a kernel successfully built.
[BLU R1 HD Guides, News, & Discussion] triggerlord:
I get that. But "make bacon" builds the OPO version. It's 100% double confirmed now.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
Well darn this sets me back about 4 days

[MENTION=3471223]bullet25[/MENTION] are you using your own device tree or anpage's? Can you send me your local_manifest file so I can have the same repos as you're using?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
What unlock error are you talking about?

I see you want to install recovery, but what are you stick on.

The guide you are referring to is for non prime version of phone. Do you have non prime version?

If not you need to follow other guide.

This one is for converting to non prime. If you don't know how to do a step or have questions, please post into relevent thread before proceeding.

http://xdaforums.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
[BLU R1 HD Guides, News, & Discussion] bullet25:
I won't be able to get to that until probably Friday at earliest. Summer hours for us at work are 10 hour days Monday to Thursday. This week is the last week of summer hours. Right now I get home and just sleep. I have to pull my Linux image back onto my laptop and until Friday I just don't have the time. I'll see if maybe I can bring my laptop to work and do it if I get some down time. All the files from my Linux install are packed into the Clonezilla image. I don't think I had a local_manifest file because I was trying to work with my own treee I didn't sync to github yet. I could be wrong but I didn't think I needed one in that case.

Looking at your terminal session you're getting a different error than I got but in the same spot but I know my session ran through more things before:

build/core/tasks/kernel.mk:186: ************************************************** ********
build/core/tasks/kernel.mk:187: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:188: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:189: * BoardConfig.mk file *
build/core/tasks/kernel.mk:190: ************************************************** ********

Why? Don't know.

Can you link me to the p6601 trees, yours and the one you forked from again so I can bookmark them for Friday?
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
KERNEL

ANPAGE'S TREE

MY DANDY LITTLE TREE

If by comparison your tree seems more "complete or "fit" for the job of CM porting, then please do sync yours up and I'll be pulling from that instead.
[BLU R1 HD Guides, News, & Discussion] :
Lots of Android building discussion going on here

Shouldn't there be a separate thread for the sake of keeping things organized?
[BLU R1 HD Guides, News, & Discussion] jrk190:
There's a thread in the r1 ROM/dev board
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
I posted a help thread to the CM Forums (too lazy to get a link atm, I'm the same username there that I am here). Got a reply from an experienced ROM developer, who confirmed that the right parameter for make/mka after doing a lunch is bacon.
[BLU R1 HD Guides, News, & Discussion] lee3lions:
Phone Holster

Anyone know of a holster that will fit this phone? The kind that clips on your belt and you can slide the phone in and out.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
I havent seen any for this device specifically. Measure the dimensions and get a generic one that fits.
[BLU R1 HD Guides, News, & Discussion] triggerlord:
Are you sure? WTF, their own wiki says that's not true.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
The codenames in lunch start with a cm_ prefix. To make it for the OPO would be cm_bacon, not bacon.
[BLU R1 HD Guides, News, & Discussion] triggerlord:
That's not what it says on the wiki though. It just says "make [device codename]" to build.
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
My guides say that "make bacon" is the cm codename for making a flashable zip, similar to that of "make otapackage" for AOSP.
[BLU R1 HD Guides, News, & Discussion] triggerlord:
Oh, you need to be specific. I thought you meant to build it not make a flashable image. Lol.
[BLU R1 HD Guides, News, & Discussion] :
The CM wiki does differ on these points. I'm not sure what the experienced user was talking about. I am working on building Android now too (more seriously than before anyway) so I will be joining the fray on this confusing **** too.

make bacon is for building Android for the OnePlus One. I have confirmed this multiple times.

Also, from what I can tell, CyanogenMod makes flashable zip packages as the global default, so again, I really don't know what the user was talking about.
[BLU R1 HD Guides, News, & Discussion] triggerlord:
I wasn't sure. I only know that it's incorrect for building it. But it still sounded wrong that way too. Lol.
[BLU R1 HD Guides, News, & Discussion] RainofOranges:
Looks like the OTA for the non-Prime variants is coming soon.
[BLU R1 HD Guides, News, & Discussion] :
****. Yes.

Edit: Apparently XDA doesn't like it when I use certain words. 'cos apparently it's like a faaaaaaaaaaaaaaammmmmmmmmllllllllyyyyyyyy forum or something. Idfk. **** **** **** **** ****.
[BLU R1 HD Guides, News, & Discussion] triggerlord:
Did everyone die?