yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Q&A, Help & Troubleshooting] optimumpro:
I don't think that's entirely correct. Sony released blobs have never worked for AOSP camera. They have also not released anything for 3.10 kernel. I also don't think that jb blobs were used in up to LP5.1.1, as 4.3 camera never fully worked. If you look at CM gerrit, they say that they were able to have camera work once on MM with 3.4 kernel, but then they couldn't repeat it. Then, out of frustration and because they know Sonyxpdevs have abandoned 3.4 for good, CM have decided to switch to 3.10 kernel and wait for Sony to fix it. Good luck: Sonyxpdevs couldn't have camera work on ANY aosp rom...

So, the answer is, in my view: (i) potentially, we can have camera in MM with 3.4 kernel, but nobody is working on it in favor of 3.10; and (ii) not in our lifetime on 3.10. This is a pity and really has very little sense: Both 3.4 and 3.10 are hopelessly outdated (Linux is using 4.x already), so, why not to try to have it with 3.4, which worked fine up to MM? One of the reasons is that many developers just don't like CM (jealousy?), and CM isn't going to lift a finger for 2 devices (Z1 and Z1c), which they consider legacy devices. So, no luck. But in my view, M is crap (LP is crap too) LOL... Kitkat is still a lot more preferable...
[Xperia Z1 Q&A, Help & Troubleshooting] SuperLamic:
well, you're not watching community here so much :) alviteri is woring on Z1 even he doesn't have the device and here you go.

And yes, they made camera working like two months ago on Lollipop on 3.10 kernel with aosp blobs and now - a few days ago even on marshmallow. It's only matter of time when it will work.

Check this: https://github.com/SonyAosp (there you have blobs and everything from alviteri)
[Xperia Z1 Q&A, Help & Troubleshooting] optimumpro:
Well. As I said before, no one is working on making camera work with 3.4. Also, as far as blobs, according to davitery, "there is nothing to do" because of Sony: http://xdaforums.com/showpost.php?p=64582482&postcount=33
[Xperia Z1 Q&A, Help & Troubleshooting] SuperLamic:
yes, this post was right on 31st December, but now is 6th February and the blobs ARE now available as I said before (and you can see screen with working camera in my previous post)

https://github.com/SonyAosp/platform_vendor_sony/commit/4f7409446779f371973035720935c36dbd09d7cc
[Xperia Z1 Q&A, Help & Troubleshooting] optimumpro:
I think the picture about camera is for Z3, which is not rhine. Also, if you look at the new blobs, there is nothing new for rhine devices; they just took out some older binaries, which are useless anyway. And this is consistent with Sony saying there won't be M for Z1. We will see, but I am not holding my breath.

Edit: I just downloaded the latest M blobs and everything in rhine and honami folders is dated August 2015. So, there is definitely nothing new for our device...
[Xperia Z1 Q&A, Help & Troubleshooting] SuperLamic:
Well, I didn't test it, so I don't know. But does it even make sense to release camera for Z3 and not for Z1 in the same package?

Anyway why do you think that they are useless? I tried that crdroid rom and it's not that bad (except for touchscreen driver and camera). And AOSP camera was definitely working on Lollipop (I personally tried it on build from erikcas), so it wouldn't make sense not to update it too when it requires only update their wrapper - and they can even use the one from Z3. (I don't really understand CM developers why they can't use Lollipop camera AOSP blob with simple wrapper to fit on Marshmallow, but I understand that it's more work and it's easier to wait)

I'm not that optimistic about Marshmallow officially, but I do think that they will release at least a bit usable blobs.
[Xperia Z1 Q&A, Help & Troubleshooting] optimumpro:
"make sense to release camera for Z3 and not for Z1 in the same package"

No, it doesn't, because Sony engineers do work on Z3 and NOT on rhine (Z1 and Z1c) devices.

You are confusing several things: the fact that camera worked with LP AOSP has nothing to do with M blobs, but rather the fact that Sony released a crippled AOSP camera for lollipop. This camera has nothing to do with M. And note, Sony released LP camera only after Android has moved to M.

Now, about M. The reason I think real blobs are not coming is that first Sony engineers must create stock M for rhine devices (and it ain't coming, because Sony said so). Then, they dumb stock down for custom roms. That's the usual way. But because M isn't coming to rhine devices, there is nothing to dumb down, unfortunately. And rhine is a different platform, as compared to Z3 and up. Not to mention that 3.10 kernel is the whole new deal on top of that. So, if there is a chance we could have a fully functional camera on M, it would rather be with 3.4, but no one seems to be working on 3.4 in favor of 3.10...
[Xperia Z1 Q&A, Help & Troubleshooting] SuperLamic:
Ok I understand. But it's still android, isn't it? So camera API is not changed that much and there must be some way how to put another layer between the blob and kernel (the wrapper). Every time I see another device's tree updated to Marshmallow I see updated camera wrapper (only one or two lines changed). So I'm wondering why this isn't possible on our device, especially when CM was using a wrapper on stock blob.
[Xperia Z1 Q&A, Help & Troubleshooting] optimumpro:
Current stock blobs don't work on 3.10, and there is no stock for 3.10. So, there is nothing to wrap...

You should ask the devs why they prefer to bang their heads (in the dark) on a totally foreign to Sony 3.10, when they can work on adapting 3.4 to work with August M blobs.
[Xperia Z1 Q&A, Help & Troubleshooting] SuperLamic:
so what's this? http://www.cas-online.nl/author/erikcas/

edit: my bad, I ment why is not possible to wrap aosp ones
[Xperia Z1 Q&A, Help & Troubleshooting] optimumpro:
Sony has opened the entire camera (not just blobs) for Lollipop, so, because it is open and you know your "addresses", it will work with other kernels (like 3.10). This is different from having closed source blobs (with uknown addresses) wrap around for a particular kernel. When they release crippled camera for M, then it would be possible. But why would Sony release crippled camera for M if M isn't coming to Z1?
[Xperia Z1 Q&A, Help & Troubleshooting] user822:
So anything AOSP 6.0 with working camera will never come to Z1 :( ?
[Xperia Z1 Q&A, Help & Troubleshooting] drakonizer:
Camera works, (of course with poor quality) in the latest cRDroid 6.0.1 build.
[Xperia Z1 Q&A, Help & Troubleshooting] SuperLamic:
hey [MENTION=5075064]optimumpro[/MENTION]

have you seen this? https://github.com/SonyAosp/platform_vendor_sony/commit/43c92897de18e71d40aa4fe3da350ea19c5c7ba9

I can see there some new camera blobs for honami, what do you think?
[Xperia Z1 Q&A, Help & Troubleshooting] DectonX:
[MENTION=4311238]SuperLamic[/MENTION] i hope it's have deal with kernel 3.10

from i read the discussion the old blobs can deal with 3.4 and not 3.10 but all favor 3.10

what do you think?

:confused:
[Xperia Z1 Q&A, Help & Troubleshooting] SuperLamic:
huh, I'm not really sure that I understand.

But - yes new blobs should not be compatible with old 3.4 kernel (though I didn't test it and I'm not planning on to)

so now all 6.0-MM roms use 3.10 kernel and new blobs. I don't think that it's that bad as optimumpro says. Many things improved, but it's true that we have to wait for it because of still ongoing development.
[Xperia Z1 Q&A, Help & Troubleshooting] optimumpro:
Here is a fact: sonyxpdev team has NEVER had camera fully working on any aosp rom. So, what makes anyone think things are going to be different on MM? They won't. The only chance was to have it work with cm device trees and 3.4 kernel, but that ain't coming, because CM and everyone else switched to aosp trees and 3.10.

So, if you want MM, buy a new device.
[LG G Flex 2] zia_g7:
Does any one know how to get this G4 power menu in G Flex 2, I have been searching all over the internet but no use.

[IMG="LG G4 Power Menu"]http://images.tapatalk-cdn.com/15/07/25/a6c85f0f876a053a2c0c72fad9129c5b.jpg[/IMG]

Thanks in advance for the help to all.
[LG G Flex 2] zia_g7:
Anyone ???
[LG G Flex 2] zeoos:
Just wait for 6.0, we may get it then on Flex 2.
[LG G Flex 2] zia_g7:
It's strange that I haven't been able to mod the power menu on Flex2, it remains stock. I tried by different xposed modules and other power menu apps from playstore. Apply the module and restart the phone but still the power menu is stock.
[LG G Flex 2] epofhouston:
G4 tweak box?
[LG G Flex 2] superdioz:
it hasnt that feature :(
[LG G Flex 2] enzo_cz:
It is logical as that screen being a part of built in system environment and the g4 tool is just a modifier. You would need to hack it on your own with uncertain result, bro :(
[LG G Flex 2] zia_g7:
Most of the features from G4 Tweaksbox, I am using on my G Flex 2, but none of the power menu mod is working :(
[LG G Flex 2] bigmelwalter:
Yeah that sucks
[LG G Flex 2] enzo_cz:
Not G4Tweaksbox fault. You need to port G4 framework to have it.
[LG G Flex 2] bigmelwalter:
Where can I find it? And is it safe for the G Flex 2 LS699 ZV9?
[Framaroot] Anuragthapa:
How To Root It ? please Help I Don't Have Any Computer

..I Am in a Remote Place Of India .

and Please Help.Me I Need 1,Click Root Too
[OnePlus X General] Aashay:
Tipsy Os test build is out. If anyone's interested can test the build and report to the developer at the link below. If anyone is not on google plus can test the build and report the bugs here. It'll be communicated to the developer.

THIS ROM IS NOT MADE BY ME. THE ORIGINAL DEVELOPER IS LOOKING FOR SOME TESTERS AND I'M MERELY HELPING HIM.

LINK: https://plus.google.com/+martincoulon/posts/DiyBrzU8Ycr
[OnePlus X General] CertifiedBlyndGuy:
I'll get back to you in a few
[OnePlus X General] CertifiedBlyndGuy:
Can't even get it to boot.
[OnePlus X General] Zoeriva:
Got it to boot, really fast.
[OnePlus X General] CertifiedBlyndGuy:
How? I just get the logo
[OnePlus X General] jonrodz:
are you flashing supersu? if so, don't flash it.

also besides doing factory wipe,

wipe:

data

cache

dalvik

system
[OnePlus X General] CertifiedBlyndGuy:
Oh. Flashing SuperSU is where I went wrong
[OnePlus X General] dsnreddy:
working very smooth probably the best build in 6 now
[OnePlus X General] saurabh40629:
what a beautiful ROM. Loving it. GPS is not working for me. What gapps you guys are using? Also how can i apply stock holo theme?
[OnePlus X General] sankarshan:
Where is the setting to assign a function for short press and long press of recents hardware button?﻿
[OnePlus X General] Drakorcarnis0:
Since this rom seems not to be based on cyanogenmod, what device tree did ya use ?
[OnePlus X General] sarthakspiker:
Might have made changes to CM tree
[One (M9) Q&A, Help & Troubleshooting] warren.walker:
So i was using a Telus M9 with unlocked bootloader and TWRP.

I tried to do factory reset to start totally fresh and now it seems my phone has no os and is "stuck" on a boot screen

How do I get it working?
[One (M9) Q&A, Help & Troubleshooting] Mr Troop:
Are you S-Off ?

You could try hard reset by booting the phone as normal then hold all three buttons till black screen then let go all but vol down

it should get you to download mode

Get yourself to recovery re-flash your nandroid or custom rom from your SD card
[One (M9) Q&A, Help & Troubleshooting] warren.walker:
I am S-On so I am not sure how to fix this...I need me phone..
[One (M9) Q&A, Help & Troubleshooting] Mr Troop:
Did you try to boot to recovery ?
[One (M9) Q&A, Help & Troubleshooting] warren.walker:
Yes

Can anyone tell me where to download the official Telus RUU that will get me back to 5.1 stock?
[One (M9) Q&A, Help & Troubleshooting] gregsarg:
http://bfy.tw/4FY2
[One (M9) Q&A, Help & Troubleshooting] warren.walker:
Very creative thanx
[Android Q&A, Help & Troubleshooting] loler1999:
Can somebody please send a link for me to download pac rom for my SM-G800H(SAMSUNG S5 MINI)
[Galaxy S II Q&A, Help & Troubleshooting] LyQi:
GT-I9100 International

Is there any rom / kernel you could recommend for top output for 24hour constant calculation. (Specifically the "boinc" app)

I would like max CPU output and i wouldn't want heat throttling since temperature and battery wont matter.

also freezing would suck since i probably wont be looking at it much so i might not notice for a few days.

Also i have a stock battery and stock charger (eu 210). I wouldnt want the drain to overpower the charger leading to downtime.

Ive got neatrom with the roms included kernel but it seems to lower cpu frequencies quite aggressively.

thinking about slimsaber

also with most governors i was getting 800mhz which was kind of annoying. Performance gov would reduce to 200 after a while, i believe because of heating.

Finally slp stays at 1200 and doesnt seem to downclock. Still i feel there is room for improvement.
[General Questions and Answers] koaghine:
Hi Guys!

I am new to xda today, and this is my first post! :)

I am looking for an app or xposed module that shows the name (not logos!) of carrier I am currently using.

I previously used an app called "Phono." But I am bad at memorizing the logos....so....

I loved Carrier Name Customization feature on G3 Tweaksbox, but I bought a Nexus 5X. G3 Tweaksbox doesn't work on Nexus.

Thanks!

-- The reason why I am looking for this is because I often go abroad. We have a plan called Unlimited Data Overseas for $10 a day. The plan only works on certain networks (In Canada, for example, Telus). Otherwise, the carrier applies normal roaming plan. Even I manually set it up, I want to constantly check whether I am on the right track.
[MTCB Android Head Units Q&A] igorski:
I have entered factory setting several times before, but now when I try I just get wrong password. I'm entering 126, same as before. Any idea? I have rooted it with the hct command and installed SuperSU... but haven't changed anything...
[MTCB Android Head Units Q&A] pa.ko:
That happened to me when I upgraded from KGL v2.80 to 2.83. After reboot I was able again to get in with 126. So I concluded that something is wrong with that ne MCU. After reverting to old one, never again I had a problem..
[MTCB Android Head Units Q&A] igorski:
solved.... it worked with 1688.... strange... whe did it change from 126?
[One (M8) Q&A, Help & Troubleshooting] HollowLeon:
Hi Guys,

I need urgent help with this. My friend's phone suddenly won't turn on and shows "Encryption unsuccessful". Tried factory reset but shows error triangle, tried wipe cache and all but to no avail. As I have uploaded you can see below. Never rooted. I hope you guys will help because I'm at my wits end here since the phone have no custom rom if I rooted it. So no point. Please help me ASAP!

View attachment 3636256

View attachment 3636257
[One (M8) Q&A, Help & Troubleshooting] MuminMohamed:
how well are you with adb? coz i need to know where to start from
[One (M8) Q&A, Help & Troubleshooting] HollowLeon:
I'm good with it, simple coding would be great if you have a solution for this
[One (M8) Q&A, Help & Troubleshooting] MuminMohamed:
download twrp from https://drive.google.com/file/d/0B3wzFG_FuEb3UzVKWHJSekZuQTQ/view?usp=sharing

install it via fastboot [fastboot flash recovery twrp-m8eye-2.8.0.3 (1).img] use the command inside the bracket, download this backup from http://1drv.ms/1WkbudN now for the back to work well i suggest that you create a backup of your cache on your sd card so that you can have the correct directories to copy the backup to, usually its TWRP/BACKUPS/YOUR SERIAL NUMBER/BACKUP FILES, if you wish to root flash supersu zip from chainfire,
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
Stop doing this when you don't read and you don't know what option that you offered. This is for India version .. won't work for him and not for his problem
[One (M8) Q&A, Help & Troubleshooting] HollowLeon:
Is there any solution? Trying to find solution for this problem
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
If it still under warranty then send it in ... this usually means the data partition is corrupted.

If it is unlocked, formatting data partition in TWRP recovery will fix it but this is non-rooted stock device, so the best option is HTC service centre.
[P3300, MDA Compact III  Accessories] rikardo:
where i can found new cover housing for orbit?

thanks
[P3300, MDA Compact III  Accessories] varvocel:
How about this one:

http://cgi.ebay.com/OEM-T-MOBILE-Do...ryZ15039QQssPageNameZWDVWQQrdZ1QQcmdZViewItem
[P3300, MDA Compact III  Accessories] rikardo:
thanks!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Blu Pure XL] bemolx:
​

TeamWin's TWRP Touch Recovery for BLU Pure XL (and clones)​

https://twrp.me/​

TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.​

A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom ROM like OmniROM.​

Source to build TWRP you can find here.​

SCREENSHOTS: HERE

Bugs:

If you find any bug I haven't noticed, please go here and send me bug report. It would help me solving most problems in further builds.

Flashing instructions:

Use Flashify, TWRP Manager or follow this thread.

WARNING!

This is custom recovery image.
Wait for progress but don't ask for ETA - I have my own life too.
You are flashing it at your own risk - don't do it if you don't know what it's used for!
I'm not responsible for earthquake, thermonuclear war or any damage on your phone. If you point finger at me for messing up your phone I'll laugh at you.

Changelog:

[B]3.1.0[/B] 2017-03-18[LIST]
[*]Release notes: [URL="https://twrp.me/site/update/2017/03/10/twrp-3.1.0-0-released.html"][link][/URL]
[*]Fixed partitioning problems.
[*]Added support for more partitions (/logo, /nvram etc.)
[*]Fixed restoring backups.
[*]Fixed CPU temp indicator.[/LIST]
[B]3.0.2-0 Official [/B] 2016-04-05
[LIST]
[*]Release notes: [URL="https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html"][link][/URL]
[/LIST]
[B]3.0.1-0 Official[/B] 2016-04-01
[LIST]
[*]Release notes: [URL="https://twrp.me/site/update/2016/04/01/twrp-3.0.1-0-released.html"][link][/URL]
[/LIST]
[B]3.0.0-1 Official[/B] 2016-02-26 (on AndroidFileHost)
[LIST]
[*][B]Recovery is now STABLE in usage![/B]
[*]Restoring backups is now [B]FIXED![/B]
[*]Mounting to PC should be now [B]FIXED![/B]
[*]Some improvments to code
[/LIST]
[B]3.0.0-0 Official[/B] 2016-02-20
[LIST]
[*]Added official support for this device
[*]Nothing changed since last build
[/LIST]
[B]3.0.0-beta3[/B] 2016-02-07
[LIST]
[*][STRIKE]Fixed backup restoring issue[/STRIKE] Seems not to be fixed, will be working on it
[*]Some iprovements
[/LIST]
[B]3.0.0-beta2[/B] 2016-02-07
[LIST]
[*]Fixed partitions problem - TWRP sees & mounts them now
[*]Fixed battery percentage indicator
[/LIST]
[B]3.0.0-beta1[/B] 2016-02-06
[LIST]
[*]Initial release
[*]TWRP can't mount partitions, doesn't read storage
[*]Any other bugs are related to problem mentioned above
[*]TWRP boots and reboots correctly
[/LIST]

Donwload: here (SourceForge)

Device tree: device_x2xtreme

Credits: Ethan Yonker aka Dees_Troy & whole TWRP Dev Team

XDA:DevDB Information

TWRP 3.1.0, Tool/Utility for the Blu Pure XL

Contributors

bemolx

Source Code: https://github.com/TeamWin

Version Information

Status: Stable

Current Stable Version: v3.1.0-0

Stable Release Date: 2017-03-18

Created 2016-02-06

Last Updated 2017-04-03
[Blu Pure XL] bemolx:
Bugs & changelogs

What does work:

Everything.

What doesn't work:

Look at changelog. Thank you
[Blu Pure XL] T-Macgnolia:
No disrespect, bit did you compile this? I ask cause I am trying to compile the new TWRP for my device wich is a LG G Stylo and my touch input does not work. So I was wondering if you had this issue and if so how did you fix it?
[Blu Pure XL] bemolx:
Yes, Ive compiled it without any errors at first time. I don't know how to help you at this moment. Ask TeamWin Devs

Cheers

Wysłane z mojego X2_Soul_Xtreme
[Blu Pure XL] eualex:
Olá, estou com problema em montar "cache" não consigo restaurar a rom stock... Backup feito com o novo twrp 3.0 beta 2... Alguma dicas.....
[Blu Pure XL] bemolx:
Can you provide me logcat or at least error shown while restoring your backup? It would help much.

PS. Next time write in English because it's better for me and other users in this forum to understand what's your problem.

Update: Yeah... I've bricked my device too. Now I know the problem and I am working on it. Wait for beta3

Wysłane z mojego X2_Soul_Xtreme
[Blu Pure XL] eualex:
The error was with TWRP 3.0 beta 3. Could not mount the cache for that reason did not finish the restoration, I reinstalled TWRP 2.8 per adb and got a mont in the cache. Now all ok with TWRP 2.8. Thank you for your attention, I am waiting for the first custom for blu pure xl. Summary error was to assemble cache error does not happen with TWRP 2.8.
[Blu Pure XL] bemolx:
Okay, I see :) In beta3 everything has beed updated - in beta1 you couldn't mount any partition because of bad recovery.fstab which is already fixed

Cheers

Sent from Nexus 5
[Blu Pure XL] eualex:
Edit, was using the TWRP 3.0 beta 3 ...... So I could settle with TWRP 2.8. Thank you
[Blu Pure XL] AlexDC2013:
beta restore fail

Same issue at me. When I tried to restore the backup in twrp 3.0.0 beta 3 it stopped. And briked my phone.

I was needed to install twrp 2.8.6.0 back and restore the backup to boot again the phone.
[Blu Pure XL] bemolx:
Restoring backup problems have been solved in v3.0.0-1. Please wait for upload at the official download page. Thank you

Wysłane z mojego X2_Soul_Xtreme
[Blu Pure XL] KingKe:
Help!! My BLU Pure XL will not go into Recovery

I try to go into recovery mode and the phone just reboots. I hold the

power and Vol up key like I did when I originally rooted it but now it will not go into recovery any longer. I'm trying to revert back to stock and upgrade to the latest release. Can someone please assist?

---------- Post added at 02:27 PM ---------- Previous post was at 02:23 PM ----------

I can not get my phone into ecovery mode. I did the buttons as I have in the past but the phone just reboots. It's like my recovery mode was deleted and the phone just resets. Help!!!!
[Blu Pure XL] bemolx:
Try to reflash the recovery img using fastboot method.

Wysłane z mojego X2_Soul_Xtreme
[Blu Pure XL] KingKe:
I would by I do not have root access.
[Blu Pure XL] bemolx:
You don't have to. Follow this thread.

Wysłane z mojego X2_Soul_Xtreme
[Blu Pure XL] KingKe:
I started with this link.

Let me restate my issue and shed light on my environment.

Power Button + Vol up does not go to Recovery mode - My phone just goes to a black screen and reboots. So, if any procedure requires that I can not execute right now. I need recovery mode back.

I am running Windows 10 Professional 64Bit variant. My BlU Pure XL connects via MPT so I can not assign a drive letter to it so that I can navigate to it via CMD prompt.

Fastboot command comes and stating 'waiting for device' because I can not get my device into recovery mode. So, can someone walk me through this issue and get my recovery mode reinstalled/repaired (Also I am not rooted)?