yashsingh1/xdaforums huggingface dataset:
[8525, TyTN, MDA Vario II, JasJam General] cbk.o4:
I've had my unlocked Cingular 8525 for about 3-4 months now, and never really had a problem with it. At first it worked great, but recently more and more when i have it open to text and then close it the screen would get garbled and messed up, easy fix of just hittin the end call button a few times and it would clear right up. Well friday my phone apparently decides it has had enough of me.. It froze up. So as a fix all on my part i just ripped the battery out and put it back in, worked fine for a few seconds then froze again. So i thought maybe it was because i had so many text on my phone (over 8000 in my inbox and around 7300 in my outbox), so i started deleting all of those. After doing all that it continued to freeze and lock up in the middle of doing things. It has been doing it since friday morning now, and i have no idea what to do to fix it. It had all the original 8525 rom and os and everything on it, i just flashed to Windows Mobile VI - Black Edition 3.0.1 a few hours ago, and it worked perfectly...for like 45 minutes. Then it went right back to freezing all the time, when it freezes it doesnt have to be in standby, i could be writing a text, or clicking through a menu, or changing a setting, ANYTHING. I love the phone but idk what made it start doing this, i didnt change a single setting and i have never uploaded any programs or anything, just the stock progs from cingular and i uploaded a few ringtones. I have read that it could be the storage card, but it seems odd that it would just start doing it after the card i have has been in for months now (Sandisk2.0G). Idk what it could be, im at a loss..
[8525, TyTN, MDA Vario II, JasJam General] cbk.o4:
ok guess my phone is just jacked then...
[8525, TyTN, MDA Vario II, JasJam General] christopherwoods:
My old Alpine used to freeze up with TomTom (before they patched it to 5.21) because of the SD card problem, but I don't think it's related to the problem you're having.

It sounds more to me like a hardware problem - do you get any other symptoms exhibited by the handset when you get the freezing issue, or does it just happen without any warning?

Have you tried installing something like acbTaskMan to monitor your CPU usage and maybe log to a file to see if there's any excessive CPU usage before a freeze?
[Sprint Note 7  ROMs, Kernels, Recoveries, & Other ] Stryke_the_Orc:
I know we all have busy lives and don't have time to go through a list of long winded rules, so here's a shortened version to make your life easier

Only the following topics are allowed in DEVELOPMENT area:

[DEV] - Development for any special projects or Apps

[ROM] - Custom ROMs

[KERNEL] - Custom Kernels (usually found in Original Development)

[MOD] - Hack & Modifications for the phone with code only, zips go in themes and apps

[FIX] - Fixes for known issues & bugs

[R&D] - Research & Development for Devs only, when gathering data for a new projects

[HOWTO] / [GUIDE] - How to instructions and Guides (Most of the time should be in General)

Note: If you are unsure where your new topic should go, then please post it to General

Please Include Screen Shots for ROM / MOD / THEME / Apps & Games, when possible as it's expected by our members

DEV Support for ROM / KERNEL / MOD / THEME must be provided within XDA thread posted by the Developer, otherwise it won't count as a Development, and in turn it'll be considered [INFO]rmation / [REF]erence and moved to General

Unmodified Stock ROM and Source Codes does not count as a DEVELOPMENT project unless it's part of an active project you have already started

Password must be provided for all password protected files

Direct download links preferred, due to stipulations stated in forum rule #11

Extra emphasis on rule #12

All ROM / MOD / DEV / etc... found in the DEV section not created by the DEV themselves does not qualify as a development, and it'll be moved to General, it should be properly tag as [INFO] or [REF], with links to the source website were it was found

Please keep all non Development relevant chatter off the DEV project topics, feel free to create a new topic in General for non Development comments about specific ROM / MOD / THEME / etc... valid replies within a DEV project are: BUG Reports, Problem, Troubleshooting Steps & Logs.

... and Please! keep all your personal bickering via PMs, do not pollute the forum with your personal indifferences.

If you have a problem with a specific member please contact the Moderators for help, that's what we're here for, but we are not babysitters, we are here to gather, organize and provide useful information for our over priced phones ;)

...for additional details please read the full Forum & Marketplace Rules

Thanks for your cooperation

Your Moderation Team
[T-Mobile Note 7  ROMs, Kernels, Recoveries, & Othe] Stryke_the_Orc:
I know we all have busy lives and don't have time to go through a list of long winded rules, so here's a shortened version to make your life easier

Only the following topics are allowed in DEVELOPMENT area:

[DEV] - Development for any special projects or Apps

[ROM] - Custom ROMs

[KERNEL] - Custom Kernels (usually found in Original Development)

[MOD] - Hack & Modifications for the phone with code only, zips go in themes and apps

[FIX] - Fixes for known issues & bugs

[R&D] - Research & Development for Devs only, when gathering data for a new projects

[HOWTO] / [GUIDE] - How to instructions and Guides (Most of the time should be in General)

Note: If you are unsure where your new topic should go, then please post it to General

Please Include Screen Shots for ROM / MOD / THEME / Apps & Games, when possible as it's expected by our members

DEV Support for ROM / KERNEL / MOD / THEME must be provided within XDA thread posted by the Developer, otherwise it won't count as a Development, and in turn it'll be considered [INFO]rmation / [REF]erence and moved to General

Unmodified Stock ROM and Source Codes does not count as a DEVELOPMENT project unless it's part of an active project you have already started

Password must be provided for all password protected files

Direct download links preferred, due to stipulations stated in forum rule #11

Extra emphasis on rule #12

All ROM / MOD / DEV / etc... found in the DEV section not created by the DEV themselves does not qualify as a development, and it'll be moved to General, it should be properly tag as [INFO] or [REF], with links to the source website were it was found

Please keep all non Development relevant chatter off the DEV project topics, feel free to create a new topic in General for non Development comments about specific ROM / MOD / THEME / etc... valid replies within a DEV project are: BUG Reports, Problem, Troubleshooting Steps & Logs.

... and Please! keep all your personal bickering via PMs, do not pollute the forum with your personal indifferences.

If you have a problem with a specific member please contact the Moderators for help, that's what we're here for, but we are not babysitters, we are here to gather, organize and provide useful information for our over priced phones ;)

...for additional details please read the full Forum & Marketplace Rules

Thanks for your cooperation

Your Moderation Team
[BLU R1 HD Guides, News, & Discussion] onlykhaz:
BLU R1 HD

The R1's slogan is "The Rebel In You"

​

Hi there!

As you may know, there is a 60$ phone in amazon that's pretty much the best budget phone right there with the advantage that amazon is updating security flaws.

We where waiting for the release of the kernel, and after a month of a lot of fighting they release it. Now devs can do their awesome work.

Update 9/11/2016:

KERNEL

[*]BLULLET25 TREE ***

[*]ANPAGE'S TREE

[*]JASONMERC TREE

There's no other BLU device with this chipset and kernel combo. You'll be pretty much pioneers, paving the way for future MT6735 devices with 3.18 kernel.

You'll be gods, cheap gods but still gods!.

So, bring your talent and your friends, we'll be happy to test out your amazing work :good:

Here is the Index of the device w/o the kernel

http://xdaforums.com/r1-hd/how-to/index-blu-r1-hd-amazon-oem-variants-t3426087

​

Peace!
[BLU R1 HD Guides, News, & Discussion] Gytole:
Blu R1 HD's Rom's, Kernel's, recoveries & other Development and The Top XDA Forum Discussions!

And after I meant to hit return and not send AM I THE ONLY ONE EXCITED ABOUT THIS PHONE!?

My little $55 non nexus...nexus...
[BLU R1 HD Guides, News, & Discussion] _MartyMan_:
Wow i'm impressed with the price/hardware combo :0 Good phone, even with MediaTek. :good:
[BLU R1 HD Guides, News, & Discussion] Gytole:
Faster than my Verizon S7 Edge. No joke.

The only thing that loads slower on my R1 is Riptide GP2...
[BLU R1 HD Guides, News, & Discussion] twilighttony:
I'm not the brightest with all of this stuff, but does this mean we can now make cyanogenmod for this phone?
[BLU R1 HD Guides, News, & Discussion] _MartyMan_:
I always thought that Exynos is the most powerful, then Snapdragon, then HiSilicon, then the MediaTek... I believe you because of TW... :-|

---------- Post added at 10:06 PM ---------- Previous post was at 10:03 PM ----------

If the devs can make it work, sure, there'll be :) And in my opinion, there will be unofficials in the next month.
[BLU R1 HD Guides, News, & Discussion] BlueFlame4:
Well, it means a lot more. You can now change clock speeds or build fancy stuff into the kernel (e.g. doubletap2wake). Also it is possible in theory to update the kernel to match newer Android versions. If you don't have kernel sources you are "caught" with the Android version (and derivates) the device ships with.

Since Team M.A.D released a lot of MTK code, it should be reasonably easy to bring up CM for this. I neither have time at the moment to do this nor do I own the phone, lol. Otherwise I would do it since MTK SoCs are quite well known to me. Good luck to you guys!

Edit: I downloaded the source to play around a bit, but it does not yet compile... Let's see....
[BLU R1 HD Guides, News, & Discussion] simplyme2908:
I think they have only released the sources partially. Doesn't compile for me with stock toolchain.
[BLU R1 HD Guides, News, & Discussion] BlueFlame4:
Well, it's "normal" for mtk kernel code to not compile out of the box. You have to fix some includes and patches because mtk uses a weird toolchain when building ROMs including kernels to they don't get these errors. I'm gonna upload my device tree once it compiles :)
[BLU R1 HD Guides, News, & Discussion] limjh16:
Then comes TWRP... Even though I don't have the phone it's nice to see MTK development blooming!
[BLU R1 HD Guides, News, & Discussion] BlueFlame4:
Well the sources seem to be REALLY borked, so there is more than the usual fixes needed. I'll mess around with it a bit. In the meantime, here is the kernel tree with some fixes from my side already included:

https://github.com/visi0nary/android_kernel_blu_r1_hd

Still not compiling but I got further ;)
[BLU R1 HD Guides, News, & Discussion] superdragonpt:
YUP

They lefted out a couple of important things

EDIT:

can someone give the the .prop build fingerprint?

need to check something

i wonder if i can order this one to Europe...

-The M.A.D. team
[BLU R1 HD Guides, News, & Discussion] Arathergreendroid:
Definitely considering this phone now. Big future for mediatek devices.
[BLU R1 HD Guides, News, & Discussion] BlueFlame4:
[MENTION=5238428]superdragonpt[/MENTION]: If I see this correctly, it's an m0 release? I thought m1 is state of the art, or am I mixing up things?
[BLU R1 HD Guides, News, & Discussion] Dark_Balor:
The fingerprint is: BLU/full_p6601/p6601:6.0/MRA58K/1467008010:user/release-keys

You should be able to buy it off eBay. Amazon.com doesn't even ship it to Canada ... it's a US exclusive for now. (Got mine through eBay)
[BLU R1 HD Guides, News, & Discussion] ss2man44:
Nah, the kernel's fine.

This commit allows it to compile and boot and operate normally. It looks like someone tried to implement a new feature in the MMC driver and left a header out. This code and that header aren't present in any other kernel that I've seen, so I assumed it was safe to revert. Both the internal MMC and the external SD card still work, so :good:

Also, to those of you putting the kernel into a git repo, make sure you delete the broken .git folders strewn about or everything you do in git will take twice as long.

The script that's supposed to append the DTB to the end of the kernel isn't working for me, so I had to append it myself to get it to boot. I'm investigating why this isn't automated now.
[BLU R1 HD Guides, News, & Discussion] superdragonpt:
It's m0 release

I've only checked the other kernel repo

I was referring to the broken targets

The nand commit you reverted was exported from the full build environment, it's meant to be used on compiling options

This source with the symlinks in place will compile just fine within the full source/environment from TINNO ( the ODM, that makes the devices)

Cheers, happy builds

PS:

If I find this cheap of eBay ( Europe ) I'll get one

The taxes I would had to pay shipping from US would probably be twice the device's value ...

Also this will be release (if not already) on Europe / Philippines with another brand name ( as always)

BLU Mediatek products are not a world exclusive ( even if they say otherwise)
[BLU R1 HD Guides, News, & Discussion] ss2man44:
You mean the targets in Android.mk? We don't need those if we're building AOSP or CM, right?

Even if that's the case, for now we really don't need to see flash info in the *#0661# screen, and that seems to be the only thing broken outside of their environment when building for p6601. Also, using symlinks in the kernel source sounds like a bad idea. I appreciate the insight. I hadn't considered that possibility.
[BLU R1 HD Guides, News, & Discussion] simplyme2908:
Now that the source is fixed I could try compiling twrp now.
[BLU R1 HD Guides, News, & Discussion] limjh16:
Source fixed? Where?
[BLU R1 HD Guides, News, & Discussion] calm_depression:
Tldr on status atm?
[BLU R1 HD Guides, News, & Discussion] jrk190:
People are working on it, but development is slow because they have busy lives. Cm 13 was built, but hasn't managed to boot. Additional bands can only be unlocked by Blu, and it seems that we're only using 32 bit arm instead of 64 bit. There's several trees of coffee available to be used, is just a matter of time.
[BLU R1 HD Guides, News, & Discussion] theredbaron1834:
Yeah, these things take time. In fact, I am impressed with the speed as is. Its just a few people working in their free time on this, as well as other things going on with this phone (like amazons 6.6 update screwing things up). Add that to all the little things that can make things hard with a port, and it just takes time.

Makes me wish I knew anything about this. I know a bit about bash scripting, and can ./configure / make but that is about it sadly.

So while I would LOVE to have CM on this phone, I am content to wait, and hope that blu/amazon doesn't mess anything up in the mean time. :) Till then, Xposed and root work well enough.
[BLU R1 HD Guides, News, & Discussion] AndroidBR:
I think [MENTION=3117667]pawitp[/MENTION] or [MENTION=4684315]flar2[/MENTION] or [MENTION=2784807]DooMLoRD[/MENTION] would be knowledgeable enough to give you some insight about these hiccups. These are some of the best developers I've been blessed with in my Galaxy S i9000, Xperia ZL and currently with my Nexus 5.

I'm really diggin' my R1 HD!

Good luck to us all!
[BLU R1 HD Guides, News, & Discussion] vampirefo:
What command are you using to build? Your error is saying out of space, how much space do you have? free up several GB of space, you are building in to small of space.

I use mka bacon -j10

Below is my build script.

#!/usr/bin/env bash

export USE_CCACHE=1
export CCACHE_DIR=/home/vampirefo/Desktop/cache/.ccache
prebuilts/misc/linux-x86/ccache/ccache -M 50G

make clobber

source build/envsetup.sh

lunch cm_p6601-userdebug

mka bacon -j10

a quick google of your error says you need to resysnc.

https://www.tapatalk.com/topic/4119...3-for-lenovo-p1-out-of-space-the-tree-size-of
[BLU R1 HD Guides, News, & Discussion] bullet25:
I have 200GBs free. and I have tried resyncing. I was just using 'mka' I will try the 'mka bacon -j10' command
[BLU R1 HD Guides, News, & Discussion] DarkBlood.:
Building cm 13 and mediatek's 3.18 kernel takes around 50 gb then another 30 gb are required through the build process that are afterwards freed up
[BLU R1 HD Guides, News, & Discussion] Dark_Balor:
By googling a little and asking some help to other MTK dev, I found this: https://github.com/mtker/MT6735_Longcheer

This is not for our device, but it's a full setup for another device with the same chipset. Now I have no idea if it's android 6 or 5
[BLU R1 HD Guides, News, & Discussion] jasonmerc:
If anything maybe we can acquire these "secret patches" vampire is talking about from another 6735 CM tree. Good find, I'll keep it in reference.
[BLU R1 HD Guides, News, & Discussion] Dark_Balor:
You can see here a tutorial on how to build for MTK.

the post does provide some patches to be applied on the Android Tree. I doubt those patches are up-to-date with anything else than android 5 or even 4.4

http://xdaforums.com/showthread.php?t=2754145
[BLU R1 HD Guides, News, & Discussion] mumbel:
I'm back porting a few things from various repos into https://github.com/mumbel/android_kernel_mediatek_mt6735 but wasn't able to boot my own custom kernel using 'fastboot boot boot.img' and gets into a boot loop with 'fastboot flash boot boot.img' (with or without my commits). Maybe this is covered in another thread here in R1 or in MTK dev threads, but

for the custom kernel builds, is anyone adding or tried adding a boot wrapper to the compressed kernel? I noticed it was likely there in their boot.img based on strings found in the p6601.dtsi. I don't know much about it, or why/if its needed (something like https://git.linaro.org/arm/models/boot-wrapper.git).

Also noticed that trustzone is likely arm trusted firmware (https://github.com/ARM-software/arm-trusted-firmware) based on strings of trustzone.bin.

I guess for either of these, it just matters how much code was changed and how its used.

Also based on symbols, they added CONFIG_MTK_BMA222E_NEW=y to their config

anyone getting around "$(warning --PROJECT_NAME -is null--please--do--lunch--$(TARGET_PRODUCT)-$(TARGET_BUILD_VARIANT)---)" or just general defines that aren't set. I'm just using a setup like make p6601_defconfig ; make zImage
[BLU R1 HD Guides, News, & Discussion] AtomicFizzle:
http://xdaforums.com/showthread.php?p=68467831
[BLU R1 HD Guides, News, & Discussion] Dark_Balor:
By following the advice of superdragonpt, you should check this devices tree:

https://github.com/MediatekAndroidDevelopers/android_kernel_jiayu_s3plus_n560a

https://github.com/MediatekAndroidDevelopers/android_device_jiayu_s3plus_n560a

and last

https://github.com/MediatekAndroidDevelopers/android_vendor_jiayu_s3plus_n560a

He said both device are mostly the same moreover MAD team has always delivered WHEN they have something stable and usable. In other words, they can be trusted.

[MENTION=3471223]bullet25[/MENTION] I'm pretty sure those 3 trees will help you build a working rom and kernel for the BLU.

Our BLU use a MTK6735 which is the same architecture as the MTK6755, only a dumb down version where we get 4 cores, a camera max 13 Mpx and a max resolution of 720p. Other than that there the same.

Source: http://4pda.ru/2014/10/27/182880/

http://www.gizbeat.com/6352/mediatek-update-mt6753-mid-ranger-and-mt6735/
[BLU R1 HD Guides, News, & Discussion] bullet25:
The kernel you link is not for the R1HD, it doesn't even have the defconfig files for it. I have looked in the device tree but there is not a whole lot I can actually use from there and as for the vendor tree nearly 50% of the blobs do not exist on the R1HD.

For as slimier as they are they are also equally as different.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
The kernel source in this thread is now out of date, hopefully Blu will release current kernel source.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
Is it safe to compile the R1 kernel using another mt6735 kernel source by just adding the p6601_defconfig to the arm/config dir?
[BLU R1 HD Guides, News, & Discussion] xWolf13:
My build of Cyanogenmod has just finished, however, I haven't tested it. If anyone would like to see if it boots or not here is the link. I based the device tree off of the Jiayu S3 Plus and used the stock kernel. Time to do my last final exam :P

Disclaimer: I am not responsible for whatever happens to your device. Flash at your own risk.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Isn't that device 64bit?
[BLU R1 HD Guides, News, & Discussion] xWolf13:
I made sure that it was directed towards 32-bit. The BoardConfig had bits of 64bit so this is what I did:

# CPU
FORCE_32_BIT= true
ifeq ($(FORCE_32_BIT),true)
TARGET_ARCH := arm
TARGET_ARCH_VARIANT := armv7-a-neon
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_CPU_VARIANT := cortex-a53
else
TARGET_ARCH := arm64
TARGET_ARCH_VARIANT := armv8-a
TARGET_CPU_ABI := arm64-v8a
TARGET_CPU_ABI2 :=
TARGET_CPU_VARIANT := cortex-a53
TARGET_CPU_CORTEX_A53 := true
endif

In the device_<device> file, I also changed the first line from core_64_bit.mk to just core.mk.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Yes, that's not what I meant the blobs are for 64bit, the problem has always been trying to get a blob list for 32bit that would boot.

If your ROM boots I will be completely surprised, R1HD requires an unknown combination of stock files to boot.

I wish you luck, but very doubtful your ROM will boot, finding a true 32bit tree would be a great find.

Or finding a method to determine exactly what stock files are needed would be a great find, looking at others blob list helps very little, as they are different devices and use different stock file combinations to boot.

All I have seen are 64bit blobs lists, just excluding the 64bit blobs doesn't work, R1HD needs more than that.
[BLU R1 HD Guides, News, & Discussion] xWolf13:
I merely added the ones that came with the device. https://github.com/xWolf13/android_vendor_blu_p6601
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I looked at your boot.img it's not close to correct for R1HD, so the answer is your rom won't boot.

A quick check for you is

adb reboot bootloader

fastboot boot boot.img

if it doesn't boot, it won't boot with rom either.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
Quick question , if a kernel ( just the kernel a.k.a boot.img-kernel from the other device's boot.img ) from another device (clone) was ported to the R1 and that booted our R1 , is that a good kernel source to use? also that same device has a defconfig for building a x64 kernel as well , and in arch/arm it has p6601_defconfig.
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Should be able to use it, first thing to do would be build using the p6601_defconfig if that builds and works correctly source is a good source.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
Thanks for your feedback , i will go and build it now using that other device's kernel source

---------- Post added at 02:13 PM ---------- Previous post was at 02:09 PM ----------

But looking at the other sources p6601 its exactly the same as ours even down to the lcm drivers and the imgsensors and touchscreen drivers.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
Just compiled and flash it to the R1 , it boots but idk where i need to go in the sorce kernel to switch the driver for the sim cards , besides that everything works as it should
[BLU R1 HD Guides, News, & Discussion] vampirefo:
Driver for SIM card? Never heard of that.
[BLU R1 HD Guides, News, & Discussion] moriel5:
He means for the SIM reader.

So the system can read your SIMs.
[BLU R1 HD Guides, News, & Discussion] KazuDante:
+1
[BLU R1 HD Guides, News, & Discussion] vampirefo:
I am not following you, your pick shows baseband version unknown so you wouldn't have any modem so no sim cards could be detected, that's software not kernel.

Can you post a link to the kernel source?