yashsingh1/xdaforums huggingface dataset:
[Xperia Z5 Compact Original Android Development] do_salah:
ok i have an issue.

Unlocked bootloader.

Installed MM,

intalled andro v21. (boots fine)

When i install TWRP it wont go to system. Keeps booting in to TWRP. Any suggestions?

thanks.

Ok sorted. i flashed recovery through adb. not flash tool. worked fine, Thanks and great work!
[Xperia Z5 Compact Original Android Development] Arturiuz!:
working fine here as well.. thank you!!!

-device: z5c e5803

-firmware(stock): 32.1.A.1.163 (MM)

-kernel(custom): androplus kernel v21

a couple of screenshots:
[Xperia Z5 Compact Original Android Development] acabreram:
what recovery are you using bro?
[Xperia Z5 Compact Original Android Development] :
Update!

new version released.

This one addresses the issue with device detection, which was broken (ro.product.device was always empty).

Please find the updated recovery.img here
[Xperia Z5 Compact Original Android Development] do_salah:
Hey thanks for the update.
[Xperia Z5 Compact Original Android Development] Arturiuz!:
this ( [MENTION=4819888]oshmoun[/MENTION]'s ) recovery..i'm going to try the latest one as per new update.will report back asap..
[Xperia Z5 Compact Original Android Development] do_salah:
Can the update be flashed through the kernel or do i have to go through the ADB root? i know it only takes a second either way. Asking for knowledge purposes.
[Xperia Z5 Compact Original Android Development] Arturiuz!:
update: yep!it works!thanx a lot sir [MENTION=4819888]oshmoun[/MENTION]!

it would take a bit of work to do so having it flashed through kernel,as far as i know..i mean,it's kinda technically complicated process(if you get what i mean)..so,we stick to the basics for now. cheers!
[Xperia Z5 Compact Original Android Development] do_salah:
Thanks for replying!

Installed update. Works like it supposed to. Thanks again!
[Xperia Z5 Compact Original Android Development] :
Another update!

This one is mainly to fix the wrong time and date, by adding this:

TARGET_RECOVERY_QCOM_RTC_FIX := true

taken from this commit . Thanks [MENTION=6584695]CTXz[/MENTION] and [MENTION=5864662]moonbutt74[/MENTION] :D

link to new recovery.img
[Xperia Z5 Compact Original Android Development] MrMmmkay:
Can you do backups with that TWRP?

I always get an error message that system can not be mountet...

I am on MM with Advanced Stock kernel.
[Xperia Z5 Compact Original Android Development] :
i made 2 backups just yesterday!

could it be that this advanced stock kernel is the issue?

like said in op you might consider using androplus me kernel if you're on stock.
[Xperia Z5 Compact Original Android Development] MrMmmkay:
Okay, so back to Androplus v22 an everything is working fine could find that out by myseld ^^.
[Xperia Z5 Compact Original Android Development] :
Update!

since TWRP now has a new release 3.0.1, I thought I'd publish a new .img for it before anyone asks :D

didn't check if there are big changes, so don't be disappointed if you don't see a difference ;)

recovery link

Oh and if you notice, this time the file is smaller, because of changes done on the way bootable images are created (you can see the commits for that in sonyxperiadev repoes
[Xperia Z5 Compact Original Android Development] farfetch:
Hey guys, I flashed AndroPlus on boot and this TWRP on recovery via ROM Toolbox but my reco doesn't start.

Help?
[Xperia Z5 Compact Original Android Development] :
could it be that rom toolbox is not doing it correctly?

Also, how are you booting to recovery?
[Xperia Z5 Compact Original Android Development] farfetch:
Nevermind, I did that by PC,thanks :)
[Xperia Z5 Compact Original Android Development] Arturiuz!:
yep! it works good,as usual! thank you!
[Xperia Z5 Compact Original Android Development] roke2:
Please help!

I followed the instructions then went on to check Rooting Status. It showed:

Bootloader unlock allowed: No

Why did this happen? I cannot enter Recovery Mode either with Fastboot or Quick Boot.

I've confirmed that I have AndroPlus Kernel.

Kernel Version:

3.10.84-v23

androplus@ubuntu #92

Sat Apr 9 15:38:56 JST 2016

Unfortunately, no root access!
[Xperia Z5 Compact Original Android Development] :
if you flashed androplus kernel then you obviously have unlocked bootloader

that message about bootloader unlock being disallowed is because of the drm fix that androplus included in the kernel.
[Xperia Z5 Compact Original Android Development] roke2:
Well, yeah. Thanks for pointing that out. But why am I not rooted? I've already flashed twrp but still I cannot enter recovery. The green LED blinks, which means I'm recovery right? But all I see is black screen.
[Xperia Z5 Compact Original Android Development] :
root has nothing to do with recovery. flashing a recovery doesn't mean you automatically have root.

and green led? that's weird because afaik androplus kernel doesn't use green to signify entering recovery. are you sure you flashed recovery and androplus kernel correctly?
[Xperia Z5 Compact Original Android Development] roke2:
I can confirm it. I even flashed Androplus and recovery again, the cmd results were good. But the outcome is the same. When I tried the recovery the LED is green but just black screen. Thus, I cannot enter Recovery Mode. The system showed that I have Androplus kernel.

Should I instead install the pre-rooted ROM then flash Androplus Kernel?
[Xperia Z5 Compact Original Android Development] :
like I said, root and recovery are two different things. Flashing pre-rooted ROM is unlikely to help in this case.

Could you please post your fastboot commands here? Oh and also are you running LP or MM? And what is your device's variant, E5823 or E5803?
[Xperia Z5 Compact Original Android Development] BoezeGott:
Nevermind, I just found it on another thread. In case anyone else has an issue at boot when the led turns yellow you push the volume button a bunch, I used volume down but the other instructions didn't specify.

Is there a way to boot to recovery without using adb? So far the only way I've been able to access recovery is to use "adb reboot recovery", nothing else has worked at all. I'm on MM with androplus kernel.
[Xperia Z5 Compact Original Android Development] roke2:
Kernel: fastboot flash boot boot.img

Recovery: fastboot flash recovery recovery.img

Model: E5803

Flavor: MM

SS:
[Xperia Z5 Compact Original Android Development] Arturiuz!:
i only push either volume up or down once & i still can access recovery..same recovery you got(Androplus Kernel v23)..

---------- Post added at 01:59 PM ---------- Previous post was at 01:48 PM ----------

how do try to access recovery,btw?i got the same device model you got & also kernel..do you see an amber/yellow light when Sony logo appears upon booting your device?if so,(try)push either volume up or down once or twice when you see amber/yellow light..it should be able to boot to recovery..i got it working flawlessly.no problem here! [emoji12]
[Xperia Z5 Compact Original Android Development] roke2:
It worked! Thanks
[Xperia Z5 Compact Original Android Development] do_salah:
Hi,

How have you got the temperature working?

Thanks
[Xperia Z5 Compact Original Android Development] Arturiuz!:
it's the TWRP version i'm using that has already fixed battery & temperature reading..it's version 2.

E5803 using XDA-Developers App
[Xperia Z5 Compact Original Android Development] do_salah:
Yeah found it on another thread, thanks
[Xperia Z5 Compact Original Android Development] ric69:
Thank you
[Xperia Z5 Compact Original Android Development] Jono31:
Hey guys please help. I have flashed the latest kernal and the latest recovery on my phone but nothing happens. After reboot the LED flashes green and red and then nothing. Phone is blank. Press the power button and the phone vibrates once and then dies. The bootloader is unlocked.

I am currently on build number 32.2.A.0.224
[Xperia Z5 Compact Original Android Development] :
Try using flashtool to flash a stock ftf.

What kernel were you running before that happened?

EDIT:

This recovery is not maintained anymore because multirom recovery is now available.

You an find multirom recovery here: http://xdaforums.com/z5-compact/orig-development/mod-multirom-v33x-t3395701

Please note that you don't need to install multirom for multirom recovery to work. The recovery will work in both cases.
[Xperia Z5 Compact Original Android Development] bofis:
So that's it, no more TWRP for Z5 Compact? And no fix for the USB issues when using it with AndroPlus? :-\
[Xperia Z5 Compact Original Android Development] :
As mentioned above, you can try multirom recovery.

It is pretty much fully functional.

The issue with androplus kernel is that it didn't disable a problematic mhl driver, which also requires a module to work.

The recovery doesn't have the module, so the driver doesn't work properly and renders usb non-functional, since usb and mhl are obviously related.
[Xperia Z5 Compact Original Android Development] bofis:
Thank you, so what kernel would you recommend to use along with multirom? Or even, would I be able to get USB working again with a different kernel, leaving TWRP in place?
[Xperia Z5 Compact Original Android Development] :
You can try OM5Z ;)

Yes i know, it sounds like self advertisement, but there really isn't that much of a choice when it comes to custom kernels for stock..
[Xperia Z5 Compact Original Android Development] gvo123:
Hi,

usb connection doesn't work after "fastboot boot recovery.img"

May be I use this recovery with Androplus kernel ?

But how can I use this recovery witout ?

thank
[Xperia Z5 Compact Original Android Development] :
yes that seems a bit bugged, you can flash to recovery partition

with nougat bootloader you can boot to recovery directly by pressing vol- and power to turn on device
[T-Mobile Samsung Galaxy Note II] AgentFour20:
Just installed Resurection Remix . Today I got a MMS message and when trying to download the message data connect was lost . I was able to regain data by selecting a T-Mobile APN . I noticed in APN setting MMS info was missing . I ended up entering the APN info for MMS and I was able to receive the Photo but the next MMS text breaks data again .

I've read Nexus devices had a similar issue which turned out to be pushbullet but no app with this name was found . I even seen suggestions to disable app permissions for SMS but this also did not fix the issue .

The dev stopped support and I was wondering if anyone has found a fix .
[8125, K-JAM, P4300, MDA Vario General] joihan777:
Help Please!

My Cingular 8125 won't properly load the official Cingular 2.25 ROM.

It constantly gets stuck loading @ 85%. I think the Splash screen memory address

range in the DOC chip is corrupted. I can only load Button ROM & WM6 ROMs, but

not the official ROMs.

After much, much, much reading I believe re-installing the ROM from an SD card

through the MTTY will be able to 'uncorrupt' the memory address.

Does ANYONE have experience with mini-SD card ROM installs?

If anyone is willing to help, simply copying your ROM to the SD card through

MTTY will create an image to the card. Would you please consider emailing

the image so I can load it into my SD card? Or if you live in the Sacramento, CA

area we can get together? It would be MUCH appreciated

as I don't have the money to but a new phone!!!!!!!!!!!!

Thanks in advance!

Johann
[Verizon Samsung Galaxy S7 Questions & Answers] ironbesterer:
There is a "10198" using battery. I don't know what it is. Does anyone know?
[Verizon Samsung Galaxy S7 Questions & Answers] xboxexpert:
LEGO Star Wars Tantive IV
[Verizon Samsung Galaxy S7 Questions & Answers] DocGlock:
I saw that I had that too. Looked and looked and it appears to be from "com.gsamlabs.bbm". I just upgraded from GSam free to pro last night and it looks like this may be leftover from the free. Don't really know for sure. I didn't remove the free version before the upgrade to pro. What I'm trying is, removing pro, reinstalling free, then properly removing the free, then going back with the pro. That may get rid of what was left over from the free. I'll follow up after this "test" is complete.
[Verizon Samsung Galaxy S7 Questions & Answers] DocGlock:
Charged overnight, unplugged for 3 hours, no recurrence yet of 10198.
[LG G4c Questions & Answers] mmniammm:
Hello everyone,

I'm not sure is it right place for this topic but I just didn't find better so sorry:)

I realize it's not very popular model so its hard to find any info. Maybe you can advice me how to root and update to 6,please?
[LG G4c Questions & Answers] mmniammm:
Really...nobody knows??
[LG G4c Questions & Answers] Stazx:
Up got the same problem i dont find anythings about this phone i dont know how to root or flash

Lg g4c h522y mt6752 4cores 1.5ghz (wtf?)

It seems to be à RU / KZ model :confused:

Thanks
[Samsung Galaxy S7 Questions and Answers] Blazing angel:
I was trying to remove a plastic protector but it looks like there isn't one.

Anyone else have this on their phone?

[IMG="Goo on sensor"]http://i.imgur.com/4w2KVL4.jpg[/IMG]

Thanks!
[Samsung Galaxy S7 Questions and Answers] ixon2001:
There isn't one on the S7 & now you've gone and scratched up the heart rate sensor as it's only plastic not glass on there :(
[Samsung Galaxy Nexus] Ziyan:
GApps

If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.

An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.

In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.

Rooting

You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
[Samsung Galaxy Nexus] bamtan2:
Incredible work! Thank you to ALL the volunteer developers for making this FREE and OPEN SOURCE progress possible! The code is free, but your time is not! Thank you!!!
[Samsung Galaxy Nexus] PythonNut:
Out of curiosity, is aosp_mm_tuna_2016-03-12 running DDK1.9 or DDK1.8? I feel like it's 1.9 from your mention of recording artifacts, but I'm not an android developer, so I can't tell.

I'm running this right now, and it's awesome. Marshmallow in general seems to have much better performance than Lollipop on our device. I do miss some custom kernel flags, but I'm sure that'll come with time.
[Samsung Galaxy Nexus] Master94ga:
[MENTION=2633638]Ziyan[/MENTION] Which recovery do you recommend ?

DRM services not working means also Netflix doesn't work?
[Samsung Galaxy Nexus] Ziyan:
DDK 1.9 of course :)

The latest TWRP should be fine. I might have not mentioned it in the OP, but the ROM supports F2FS as well.

Possibly.
[Samsung Galaxy Nexus] Master94ga:
Thanks, 3.0 unofficial or your last recovery?
[Samsung Galaxy Nexus] diogofd8:
You are a god!

I'm downloading and will be testing this, I'm super excited about this work.

EDIT: So, first thing I've noticed is that the phone is struggling with the configuration in the first boot. Either in the "checking connection" or in the "just a sec..." loading frame, it freezes and doesn't get past it. Is it because of google play services?
[Samsung Galaxy Nexus] Ziyan:
Yes Google Play Services can mess it up - I don't recall how, but I managed to press a skip button or something to easily get past it when it started looping. I guess we should add a mini how-to to the OP about it, as I really don't want to hack the framework for this.
[Samsung Galaxy Nexus] Master94ga:
Yep, I'm stuck in "just a sec..." :(

Edit: I restarted the Phone and now it works.

Netflix works too :D
[Samsung Galaxy Nexus] eternal70:
Big thanks to [MENTION=2633638]Ziyan[/MENTION] and all OMAP4 dev for all your contribution so far ! I'll test this immediately [emoji106]
[Samsung Galaxy Nexus] diogofd8:
Ah, another thing!

When I flash the rom .zip file with all the partitions in f2fs, it auto changes to ext4 and installs. Maybe I'm being noob using TWRP so I'll say what I did here:

1) Full wipe

2) Convert system to f2fs, convert data to f2fs, convert cache to f2fs

3) Adb push rom zip file

4) Flash it

5) Check partition format, it's all on ext4
[Samsung Galaxy Nexus] bamtan2:
There are a couple things going on here. The system ROM is an ext4 image, so it doesn't matter what you format it to, because it'll always become whatever is in the image.

Furthermore, only /data benefits from being F2FS, but it's not you fault for not knowing this because it wasn't mentioned in the documentation! :)

The other thing is that I don't know of a TWRP build that isn't buggy. When I tried to format to F2FS, it didn't work because my particular version of TWRP had a bug. So maybe your /data format failed for the same reason. I personally do not know what version of TWRP will reliably work for this. But this is a discussion for the TWRP thread.
[Samsung Galaxy Nexus] siealex:
Don't do this! F2FS is not supported on /system.
[Samsung Galaxy Nexus] vipelp:
Wifi is extremely slow.

I can't do anything.

Google Play store can't install apps.
[Samsung Galaxy Nexus] rohitchouhan07:
Wifi works perfectly fine here ....with 2.4ghz

you using 5ghz or 2.4 ghz ?
[Samsung Galaxy Nexus] vipelp:
I already tried both and it doesn't matter.

Browser times out opening google.com.

Play store doesn't load images and can't download apps

Wifi automatically disconnects....
[Samsung Galaxy Nexus] PythonNut:
WiFi working fine for me on 5GHz as well.

To other people: when this ROM boots, you may see the Google splash screen, then the screen will go black, and the device will act like it has died. It hasn't. Just give it a minute and the regular Android boot animation will appear.
[Samsung Galaxy Nexus] vipelp:
OK i'm trying a reflash now. Complete wipe.
[Samsung Galaxy Nexus] Master94ga:
For me all work correctly, no problem with google play store or wifi :)
[Samsung Galaxy Nexus] PythonNut:
I captured those logs on an brand new flash. All I did was setup my Google account and install Solid Explorer.

I can try it with some different settings, but did you have any particular ones in mind? Otherwise, the combinatorial explosion looks quite daunting.
[Samsung Galaxy Nexus] PythonNut:
Sure. Here you go.

I'll have to do the logs on the weekend.
[Samsung Galaxy Nexus] AgentSmith:
Interesting. I tried the app as well and I seem to have different mmc memory. The brand is Samsung instead of SanDisk, model VYL00M, and the production date is in July 2012. The tool also reports 13 existing partitions. I mean.. 13!
[Samsung Galaxy Nexus] Nautilus74:
My screenshot :

https://www.dropbox.com/s/ldyww8ciktxng2k/Screenshot_20160331-081441.png?dl=0
[Samsung Galaxy Nexus] phaleg:
Just added my review

If you like to be updated and essential, this is the way to go !

It does not offer many features in this moment (build march 2016), but it is

- stable

- fast

- battery efficient (2 days in my case, use WiFi but almost never 3G)
[Samsung Galaxy Nexus] h4xx0rr:
Is this happening to anyone ? I rebooted phone, after reboot I opened gallery and there is no pictures/videos (same with music), but it show all files in file manager (nothing is deleted). For some reason gallery and music player can't read internal memory :confused:
[Samsung Galaxy Nexus] siealex:
Reboot and wait at least 10 minutes, then reboot again.
[Samsung Galaxy Nexus] massima:
Are you sure? I simply connect it and......nothing!!!!!

I need a suggestion: everytime i install a rom at the first setup android connects to the mobile network (i haven't a internet flat plan) and i loose 4€. So i thought to set up it without the sim, to configure it and re-plug the sim (trying as fast as i can to disable the mobile data) but no success.

So i have 2 options at the first boot, without the sim in the phone:

1) add in the default.prop the string "ro.com.android.mobiledata=false";

2) edit the apns.conf.xml with a wrong apn.

Should they work? Are there other options? It's becaming for me too expensive to try/debug a new rom:(.
[Samsung Galaxy Nexus] thagringo:
cant check, dont have a otg cable anymore.

in case it doesnt work for you grab logs so that Zyan & Co can try to fix it.

Not sure if im missing somehting here : i use my gnex every day without a SIM. Cant you just run the initial setup without a SIM inserted and conce you have finished, turn off the device, plugin your sim and restart the device ?

cheers
[Samsung Galaxy Nexus] massima:
Sure!!! Where can i find logs? perhaps in /var/log (as linux)???

I already tried. I setted up everything without the sim, then powered it off, inserted the sim. When android was loaded, data mobile was active by default (android connects automatically to internet and i lose money). I need an option to keep data mobile OFF by default since the first boot :confused:.

Thank you
[Samsung Galaxy Nexus] thagringo:
android uses a different log system.

You can read more about capturing logs here -> http://xdaforums.com/showthread.php?t=1726238

i see, i think the only option you have is to add what you have mentioned before in build.prop.

Or maybe Zyan can disable it at build time, there are several roms out there that have it disabled by default.

cheers
[Samsung Galaxy Nexus] n76:
After setting the phone up without the SIM, maybe setting airplane mode (which should survive reboot), then powering down and inserting the SIM? Seems like it ought to power up still in airplane mode.

I haven't tried it, just tossing out an idea.
[Samsung Galaxy Nexus] massima:
Yes, the airplane mode survives to the reboot, i'll take a look hoping for a solution. Thank you :good:
[Samsung Galaxy Nexus] coop3r:
I have some problems with power management. Sometimes the phone doesn't want to charge - I need to reboot until it recognizes that charger is plugged on. Also, I'm experiencing frequent screen wake ons from sleeping mode. The battery indicator sometimes behaves like the phone is charging, while its not.

Tried reinstalling, but with no success. Made full wipe, changed data and cache to f2fs.

Does anyone have same problems? Any solutions? Would appreciate any advice.
[Samsung Galaxy Nexus] siealex:
Replace your USB connector, it's damaged.
[Samsung Galaxy Nexus] coop3r:
Thanks for the advice. Have another dead Gnex, will try tonight.

Upd.: Problem solved, many thanks siealex!
[Samsung Galaxy Nexus] Ziyan:
New build up with the following changes - much of these wouldn't have been possible without the help of our mysterious friend, Luden:

- Updated SELinux rules for M

- Keymaster added back to the build - it caused battery drain in the past, so Google removed it years ago - it is now worked round, so we can have hardware accelerated encryption & decryption support - more details in this commit

- Minor CMA related changes - hopefully, they fix the crashes observed while using flashlight with the screen turned off

- The black screen some of you experienced (seen until the filesystem gets mounted) is now gone, with the google logo replacing it (this is the old behavior)

- Enabled video stabilization, exposure and white balance lock support for the camera (these are present in my 5.1 ROMs, but for some reason, we forgot including it in our M codebase)
[Samsung Galaxy Nexus] AutomaticFailure27:
How long does first boot take after installing the rom? It's been around 30 minutes on the android boot screen on Toroplus.

EDIT: Did a battery pull and rebooted, works now.
[Samsung Galaxy Nexus] siealex:
5..7 minutes, then the "optimizing" screen.