yashsingh1/xdaforums huggingface dataset:
[Galaxy Note5 Accessories] xdaguyb:
Confused

The data above seems better than Quick Charge 2.0 speed:eek:
[Remix OS for PC] total777:
i get error when remix start first time install in kernel boot

"ata3: softreset failed (device not ready)"

after search found its that error come from my AMD motherboard chip SB750 and to make it work must re-compile kernel configuration with that

CONFIG_SATA_PMP=n (default is CONFIG_SATA_PMP=y)

can some one help me to edit its and re-upload it again

and its the original kernel without edit

mega.nz/#!lpIw3CaY!eeRST25NP5G3z-8FfCtNcL4iwEe2TGZTyZncVG24ySk
[Remix OS for PC] total777:
No one can help me with that??
[Remix OS for PC] speculatrix:
Hi,

Once I've figured out how to actually build a kernel for remixos and then rebuild the USB image, I'll let you know.
[Remix OS for PC] total777:
thank you for reply
[Nexus 5X Q&A, Help & Troubleshooting] szucsgf:
Does anyone know what happened to Cataclysm? Just saw the moderator message that thread was closed.

http://xdaforums.com/showthread.php?p=65000356
[Nexus 5X Q&A, Help & Troubleshooting] draggehn:
http://xdaforums.com/showpost.php?p=65000035&postcount=5226

and

http://xdaforums.com/showpost.php?p=65000336&postcount=5227
[Nexus 5X Q&A, Help & Troubleshooting] martyfried:
Pretty confusing: This post

http://xdaforums.com/showpost.php?p=65000035&postcount=5226

is the same as this one,

http://xdaforums.com/showpost.php?p=65000035&postcount=5227

but the numbers are different.
[Nexus 5X Q&A, Help & Troubleshooting] PiousInquisitor:
There is a glitch in the matrix. lol.
[Nexus 5X Q&A, Help & Troubleshooting] draggehn:
That was me trying to be speedy; if you look closely, the number that follows the "?p" is the same on both links. I tried to link a different post but forgot that you need the post ID to be modified, not the post count. Fixed in my post above. Oops!
[Nexus 5X Q&A, Help & Troubleshooting] HiM@L:
troll got upper hand in whole thing...and wont stop until everyone realizes the same...been going on for a while now.
[Nexus 5X Q&A, Help & Troubleshooting] kurruptor:
Can you clarify what happened?

The posts linked above talk about there isn't a need for android dev. vs original android dev., which I understand... but what is the status of Catalclysm? Is it not being worked on anymore?
[Nexus 5X Q&A, Help & Troubleshooting] PiousInquisitor:
You can put it together by reading some of the posts from here:

https://plus.google.com/communities/110330751890850674087
[Nexus 5X Q&A, Help & Troubleshooting] Puzzlegirl:
Alas, Cataclysm has "died" before in the days of the Galaxy Nexus and Nexus 4. Atl4ntis disappeared for a year or more then and reappeared magically for the N5 and gained a large number of users. However, if he can't hack the stress, it was hardly fair to build up an even larger keen collection of users on FOUR different devices. I'm bitterly disappointed, but sadly not surprised. At least he gave his reasons on Pushbullet.
[Nexus 5X Q&A, Help & Troubleshooting] peltus:
This is a sad day...... for me and the rest of Cataclysm users.
[Nexus 5X Q&A, Help & Troubleshooting] martyfried:
Thanks for that link. But after reading most of the discussion, I think I need a drink (it must be 5:00 somewhere). It turned into a toxic lovefest/hatefest pretty quickly.
[Nexus 5X Q&A, Help & Troubleshooting] mistermojorizin:
seems like this was the source of our misery: https://plus.google.com/+AlexCruz/posts/FVbxmtyop7W
[Nexus 5X Q&A, Help & Troubleshooting] martyfried:
Thanks. I think I see his point about fairness, but man, does he have to be so nasty about it? Seems like he didn't really need to insult anyone, except maybe the XDA mods that he felt were unfair to him. But perhaps he feels it's a race thing (who knows, perhaps it is).

Anyway, it's too bad they couldn't solve the problems without going ballistic. Hope it turns out to do something positive.
[Nexus 5X Q&A, Help & Troubleshooting] stay-down:
This is all just sad...
[Nexus 5X Q&A, Help & Troubleshooting] NLBeev:
When I read that post of Alex Cruz and the words he is using, I think there is jealousy involved. Why moderators wanted to move a thread is not clear to me.
[Nexus 5X Q&A, Help & Troubleshooting] gmi78:
i dont understand because the best are always under attack:confused::confused::confused::confused:
[Nexus 5X Q&A, Help & Troubleshooting] NLBeev:
Yes, and there is a fact. His method 'cata-mod' is and was very original. So I am confused too, and do not understand the moderators concerned. Especially because a thread with discussions about the 'why' is also closed.

This is not a simple 'not following the rules question'. Apparently we are dispirited to talk further.
[Nexus 5X Q&A, Help & Troubleshooting] olivercervera:
I'm very sorry for Atl4ntis and Cataclysm.

He's been a very kind guy, always keen to answer help and fix bugs,

His ROM has been the best I've ever seen so far: a lot a customization, great features, great stability. A great balance.

I hope he will eventually be back, but he will be always remembered as one of the best guys and modder here!
[Nexus 5X Q&A, Help & Troubleshooting] NLBeev:
I agree with you. He was also creative. The 'cata-mod' is unique. It's a black day the Cataclysm thread is closed.
[Nexus 5X Q&A, Help & Troubleshooting] olivercervera:
For those about to roms, we salute you Atl4ntis!
[Samsung Gear S2] JohnnyCanuck:
So I am trying to develop a watchface that will change background and hands on a double tap of the watch's logo. I have figured out inside GWD how to do that for the background image (pretty simple) but there is no way to do with the hands inside GWD. I know the .xml needs to be edited but I am not enough of a coder to figure it out myself. Hoping someone can help me get started. Here's the code snippet for the action on tap:

<group height="360" name="__DEFAULT_GROUP__0.2518321910068403" width="360" x="0" y="0">
<part height="360" id="Image0_0_0" type="image" width="360" x="0" y="0">
<metadata id="Image0_0_0"/><image-set>
<image>TargetResized.png</image>
<image>action/image/basefullblack.png</image></image-set></part>
<action on_event="tap" target_part_id="Image0_0_0" type="image-set-show-next"/>
</group>

Where "TargetResized.png is the blank image tapped to make the change and "basefullblank.png" is the image file swapped into the watchface to be the new background.

Here's the code snippet for the hour hand of the normal watch face:

<group height="360" name="__DEFAULT_GROUP__0.7909505539679654" width="360" x="0" y="0">
<part height="246" type="image" width="246" x="57" y="57"><metadata id="Hands1"/>
<metadata type="hands"/><image>.img228.png</image><rotation center_x="123" center_y="123" end_angle="720.0" end_value="24" source="hour0-23.minute" start_angle="0.0" start_value="0"/>
</part></group>

Where ".img225.png" is the hour hand. If my new hour hand image was called "HoursAlt.png" I figure I need to import a piece of the second snippet above into the first somehow. Am I even on the right track?
[Samsung Gear S2] molexguy:
How to add script for do "double tap" event ?
[Samsung Gear S2] vitusdoom:
there's a trick to that ;) you need to add a type image on the back of the hand

sample:

<group ....>

<part ....>

<metadata ....>

<image>shadow.png</image>

.....

</part>

then you put your action. here's a sample. (there are others you can use. just from top of my head sorry)

<action on_event="tap" target_part_id="..." type="image-set-show-next"/>

(or something similar to what you have for your logo)

Hope it helps. cheers
[Nexus 6 Q&A, Help & Troubleshooting] DroidManIc:
I just got my very first straight from Motorola N6 last week. I did some looking around before hand to make sure I would be able to root (came from ATT note 4 which is unrootable). While I was researching I noticed there are several noticeable issues w Android 6.x on the N6. From your experience, should I take the ota or stay 5.1.1 and root? I won't be able to update via OTA after root right?Thanks.
[Nexus 6 Q&A, Help & Troubleshooting] StykerB:
This should be in Q&A but what issues are you referring to because I don't really have any marshmallow specific issues.
[Nexus 6 Q&A, Help & Troubleshooting] sansnil:
No issues with 6.0.1 on my N6 here either.
[Nexus 6 Q&A, Help & Troubleshooting] DroidManIc:
I've seen several threads/posts regarding issues w being unable to root as well as problems w speaker distortion so I was wondering if it's a common issue or maybe a couple of isolated incidents...
[Nexus 6 Q&A, Help & Troubleshooting] motomotomotoG:
I've tried out PureNexus and AOSiP and DirtyUnicorn, no issues with any of them other than afwall++ rules don't stick. So if you use a firewall, you might want to wait a little while until an update comes around.
[Nexus 6 Q&A, Help & Troubleshooting] StykerB:
root is pretty simple now with chainfire's systemless root method. Just flash the latest (I think its ver. 2.67) from the marshmallow WIP thread over on the SuperSU forums. It will intelligently detect whether you're running software capable of either systemless (stock android style) or system modding root (most up to date custom roms) I've seen a couple people freak because it bootloops once on them and they immediately come here only to have the device boot up next to them because the new SuperSU.zip is intended to bootloop once or twice while its settings things up. Neat thing about this new systemless root is that you can take an ota as long as you don't let TWRP mount /system as R/W and use the unroot function in the supersu app before installing the ota. (If you ever clear cache in recovery this however won't work because thats where the boot.img backup is stored iirc)

As for speaker distortion I notice you can overdrive the speakers when using equalizers like dolby, beats or viper due to them having a built in amp but with all that stuff off and not maxing out the volume they sound pretty decent really. This wasn't any different in 5.1 so no worries there. There was something that was fixed with slight hardware revision back soon after the phone was released relating to the speakers as well but the 5.1 kernel update helped the pre revisions as well and these changes are carried over to marshmallow.

and as for stuff like cpu cores underclocking and unplugging and speakers going quieter is the kernel lowering these things in order to try and prevent a voltage droop when the battery gets lower causing random reboots that can sometimes be seen in some custom kernels which disable these power-saving measures or don't account for them in some other fashion.

All in all if you like 5.1 you can stay at it. I'm all for people getting their devices going in a way that works and satisfies them. No need to update unless you really want the latest and greatest which honestly is kinda why I bought a nexus in the first place. But with every android update I've ever put on this phone it's just gotten better and better.
[Nexus 6 Q&A, Help & Troubleshooting] DroidManIc:
No firewalls, my main concern was with speaker issues and not being able to root but looks like maybe just a couple ppl having issues.
[Nexus 6 Q&A, Help & Troubleshooting] DroidManIc:
Cool stuff man thanks. Took the update my main concern was not being able to root but sounds like I should be good!
[Nexus 6 Q&A, Help & Troubleshooting] doitright:
Some people are just idiots. Don't use "random internet postings" as evidence.

This is a GOOGLE NEXUS. Root is its middle name.
[XDA Assist] KronuZ:
I want to know if is I could flash other carrier rom to Huawei Phones, for example:

Lets say I have a Jazztel Y550, and I already unlocked it, but I need to flash it and only have the Open Market Y550, can I flash it??

Open Market Y550

http://consumer.huawei.com/es/support/downloads/detail/index.htm?id=69643

And Jazztel T550

http://consumer.huawei.com/es/support/downloads/detail/index.htm?id=69603
[Android General] zijin_cheng:
[YOUTUBE]wEWsEPT4Lso[/YOUTUBE]

[YOUTUBE]YT8EXNZWWO0[/YOUTUBE]

Hey guys, this is the Ulefone Be Touch 3 review and unboxing! I review all aspects of the Ulefone Be Touch 3!

Ulefone Be Touch 3 Specs:

5.5" 1920x1080 IPS Display, Gorilla Glass 3, 2.5D

MTK6753 Octacore 1.3GHz

3GB RAM, 16GB ROM

13MP, 8MP Camera

Fingerprint Sensor

2550mAh Battery

2G: GSM 850/900/1800/1900MHz

3G: WCDMA 850/900/1900/2100MHz

4G: FDD-LTE 1800/2100/2600MHz

FAQs

Will this phone work in my country? http://www.willmyphonework.net/

Rooting Info:

Instructions on how to root your phone are below (mods, if linking is not for outside rooting instructions let me know and I'll painfull copy it word by word :)):

http://blog.ulefone.com/how-to-ulefone-be-touch-3/
[Android General] Borkuz:
Great phone, but have some wifi speed problems. Anyone else with the same problem or anyone knows how to fix this?
[Android General] dinci:
Try to go in enineering mode, type *#*#3646633#*#* and then find Connectivity/wifi display/Quality Enhacement and then enable auto channel selection... im not sure but i think it has a bug, it doesnt switch automaticly between 2,4 and 5ghz... When you restart the phone it turning off this function.

---------- Post added at 11:47 PM ---------- Previous post was at 11:40 PM ----------

Hello, i have flashed my be touch3 few times, and later i have noticed that gps is not good, i have tryed with many apps and instructions but it doesnt get better, also ihave noticed finger print sensor is also not working good after flashing. I have tryed all rom versions that i have found and now its flashed with third version from ulefone website, it shouldbe original but my previously rom hadbetter finger print and gps :(

i dont know what is the problem, phone is not bad, camera is great but these problems are forcing me to buy something new...
[Android General] ad4xda:
Very first LK.BIN for ulefone Be Touch 3 needed

SOLVED

Hi,

I flashed my Ulefone Be Touch 3 device with Ulefone's ROM and ... big mistake : soft bricked.

The device still works except the screen : a dark blue one with no logo, no icon, etc.

From what I read, I can get screen back to normal with the very first lk.bin file but i can only find recent (and thus faulty) ROMs.

Could someone help me ?

Thanks in advance.

Best regards.

---

SOLVED : there are 4 different ROMs from Ulefone for this device.

Downloaded each one (mega links so use Tor browser if you're blocked in your country) and tested them all.

Screen is now back.

Also check this for Be Touch 3 goodies :

- xda --> there's a new "boot.img" and other tweaks

- http://www.htcmania.com/forumdisplay.php?f=2049 --> here you can get some beta ROMs

Cheers :emoji_laughing:
[Android General] id example:
Yes, I have the same. Someone has experience and can suggest the best Rom?

Some applications think it is rooted but I cannot find it.

For batteries, is there a common Samsung aftermarket that works and is compatible?

In Aliexpress the Ulefone be touch battery 1 2 and 3 are 5 British pounds.
[Android General] ad4xda:
Hi,

This one worked on my phone and in my country (Belgium) :

20151208_ulefone_be_touch_3_Option 2(WSHLY55)

Please note this rom does not grant root access, it's an original rom from Ulefone, only.

For custom beta roms, please check this link :

https://xdaforums.com/android/gener...-available-t3320971/post71701494#post71701494

For batteries, i found these links :

http://www.banggood.com/fr/Original...Battery-For-Ulefone-be-Touch-3-p-1038499.html

http://www.ebay.com/itm/NEW-100-Ori...604628?hash=item3f655e1694:g:TooAAOSwMNxXa-hs

Kindest regards.
[Android General] olucniottor:
Hello everyone, If it may be useful finally I was able to install "Simplified rom" ,everything work perfectly(I ran SP Flash Tool). I tried first of all to flash "simplified ROM" whitout lk.bin and the second time doing the same with lk.bin from the stock ROM. Thanks ad4xda for the suggestion!:D:good:
[XDA Assist] XDA Visitor:
Hi,

I'm automating my tablet for use in my car.

Here is the situation, I'm using app tasker for every time I turn on the device, they will do after boot

1- Launch app " Fm Transmitter"

2- wait 5 seconds

3- option 1 (here I want to make the tasker automatic click over the button"on", but the AutoInput By joaomgcd just work on a 4.4 android device, and I have a TB 120 stuck on 4.0.4, and have no other rom for it.) Option 2 create a shortcut for I open it with tasker and automatic turn it on.

4- Launch app Autoboy Blackbox (for recording all route, automatic after it open the app)

5- launch app car dashdroid

6- "finish"

If any here have any idea how I can made it work, please share with me... (step 3)

ps: I also trying to make it script "#!/system/bin/sh /system/bin/reboot" for every time it conect on charge, turn device on automatic (and than the magic of tasker after), but have no success to (I'm on mtk device and already put the lines in ipod paste).
[XDA Assist] GuestK0087:
Greetings,

Thank you for using XDA Assist. First, please create an account so you can post in other forums. After you've done that, please post your question here:

Questions and Answers

You'll receive expert advice there. Good luck and welcome to XDA!
[One (M8) Q&A, Help & Troubleshooting] bonongvodoi:
Hi all,

I'm a new one,

I flash the latest version of S.ROM at: http://xdaforums.com/htc-one-m8/development/romthe-worlds-first100-m9-port-m8upload-t3064838

This rom is good, but:

- The Quick Setting when i pull down the status bar, is the original Quick Setting in android MM, is there any way to change to the Sense 7's Quick Setting?

- If not, how can I add/remove or change the order of items in Quick Setting

Thanks
[One (M8) Q&A, Help & Troubleshooting] xunholyx:
I haven't used S.ROM, but with ViperOneM8 there is what looks like a notepad and a pen or something like that. Click on it, click the three line thingy on the left, and drag what you want and don't want into position. You can move the tiles to wherever you want.

Maybe something similar with S.ROM?
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
I don't use that ROM either but based on experience on my own A9 port that I used to run before, the quick settings is different as it is a GPE quick settings (that's why it is called Sense_7.0g) and it uses SystemUI Tuner to edit not like the normal/full Sense 7.
[Fire Q&A, Help & Troubleshooting] bibikalka:
On Fire HD 2014 I started looking at md5sum for partitions for different OS versions, and it seems that on Fire 2015 one can figure out which partition gets screwed up by 5.1.1 bootloaders, and perhaps restore it to pre-5.1.1 state. If this fails, the warranty should kick in (all of the Fire 2015s are still under warranty !!!)

Please see this link for some details :

http://xdaforums.com/fire-hd/help/trying-to-undo-bricking-5-2-2u2-t3301374

Basically, the idea is simple. First one captures all the partitions while running 5.0.1 bootloaders. Then the bootloaders are updated to 5.1.1 version. At this point the partitions are captured again. This is the code to capture partitions to be run on PC via adb:

adb shell
su
mkdir /sdcard/tmp/
dd if=/dev/block/mmcblk0p1 of=/sdcard/tmp/01_kb.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/tmp/02_dkb.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/tmp/03_expdb.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/tmp/07_misc.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/tmp/08_logo.img
cd /sdcard/tmp
md5 *.img

Then one can simply exit, and do "adb pull /sdcard/tmp/" to get all these *.img files off the device.

Then those partitions that changed (KB,DKB,EXPDB,MISC) are dd'ed back under 5.1.1, and bootloaders are dd'ed back to 5.0.1 versions. If it reboots OK, this means that the device is effectively restored to pre-5.1.1 state. If failure, warranty return.

The next step to try would be to transplant this offending partition from a different Fire to a device with 5.1.1, along with 5.0.1 bootloaders.

Here is the list of partitions for reference:

http://xdaforums.com/amazon-fire/development/partitions-list-t3236213
[Fire Q&A, Help & Troubleshooting] blueberry.sky:
When one tires to downgrade to 5.0.1, it's the preloader stage which the Fire keeps cycling at. We have already tried flashing the 5.0.1 bootloader & preloader onto a 5.1.1 Fire.
[Fire Q&A, Help & Troubleshooting] bibikalka:
But this would not make sense. Are you saying that the preloader does not even try to call the 5.0.1 bootloaders ? But then why ?

Since the preloader stays the same, the only difference is that 5.0.1 bootloaders are trying to run after 5.1.1 bootloaders already ran on the device. At this stage 5.0.1 cannot proceed normally, which must be due to some changes sitting on some of the partitions that the bootloaders are reading early on.

We have no indication that 5.0.1 bootloaders do not run at all, they may run a bit, and then crash, and the device is back at the preloader stage.

So restoring additional partitions together with 5.0.1 bootloaders may enable 5.0.1 to function again after 5.1.1, as per my original post.
[Fire Q&A, Help & Troubleshooting] blueberry.sky:
Have you verified that the 5.0.1 and 5.1.1 preloaders are the same?

Just know that when plugged into a pc you will see the preloader cycle endlessly. Connect, disconnect, repeat. And someone did try to flash the both the bootloader & preloader extracted from 5.0.1.

It could be that 5.1.1 is blowing a fuse which tell older versions to refuse to boot.
[Fire Q&A, Help & Troubleshooting] rongweiss:
Thanks Bibikalpa. The problem is, to try your solution we have to be able to use adb. We are stuck at fastboot. :crying:
[Fire Q&A, Help & Troubleshooting] blueberry.sky:
What he is proposing is not a solution for people who are bricked. Rather it would help prevent people on 5.1.1 from getting bricked in the first place. It would allow downgrading to 5.0.1, restoring the ability to load twrp recovery from fastboot.

---------- Post added at 09:53 PM ---------- Previous post was at 09:11 PM ----------

Here are the md5 checksums from my 5.0.1 Fire

e1c2e27a6dae694cbf14594b6d963f11 ./01_kb.img
175ec1eea0b65b15ea6ee455531f154d ./02_dkb.img
1d837a219b515afae6c19d9126168f5c ./03_expdb.img
00ff461906b45fc4af74f81839a30069 ./07_misc.img
c414b0be43b26efb5009639be06a74e2 ./08_logo.img
926c891ba8bc265d5dfeabe1ba3838c8 ./09_tee1.img
926c891ba8bc265d5dfeabe1ba3838c8 ./10_tee2.img

Perhaps some of them are the same even between different Fires.

I've already had to get a warranty replacement for my Fire due to a cluster of stuck pixels. Don't want to try upgrading to 5.1.1, risk having to try for a 2nd replacement.
[Fire Q&A, Help & Troubleshooting] DoLooper:
Here are my md5 checksums from 5.1.1 (with 5.1,0 bootloaders, so may not help much, but you didn't ask for bootloaders)

d47ae72b30dd03c08d0c41883ac219f4 01_kb.img
8b50c460e75aef889840a9077b12c20a 02_dkb.img
4af5655b4a4f2b36ffb81b20605bb75d 03_expdb.img
00ff461906b45fc4af74f81839a30069 07_misc.img
c414b0be43b26efb5009639be06a74e2 08_logo.img
926c891ba8bc265d5dfeabe1ba3838c8 09_tee1.img
926c891ba8bc265d5dfeabe1ba3838c8 10_tee2.img
83b74c9782b889e246bc7b7cfa184d64 04_uboot.img

I'm OK with testing, starting from scratch and rooting my unadultered 5.1.0.
[Fire Q&A, Help & Troubleshooting] bibikalka:
These look like 5.0.1 checksums for TEE1/TEE2, the same as [MENTION=5997572]blueberry.sky[/MENTION] post.

Only the 1st 3 partitions seem to differ. If you run "adb shell; idme print" with root, it actually prints the first few lines of KB & DKB, at least on Fire HD 2014. Does this work on Fire 2015 ?
[Fire Q&A, Help & Troubleshooting] DoLooper:
As said, I'm running 5.0.1 bootloaders.

I get no output with either "idme print /dev/block/kb.img" or "idme print /dev/block/dkb.img" while in su. I assume this is correct syntax.
[Fire Q&A, Help & Troubleshooting] bibikalka:
It's just straight "idme print", nothing else after that.
[Fire Q&A, Help & Troubleshooting] DoLooper:
Cool!

root@ford:/ # idme print
. . .
KB:
4b 42 50 46 18 0e 00 00 28 0e
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
DKB:
30 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
. . .