yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Compact Q&A, Help & Troubleshooting] MickieH:
Hi all,

I have been running my Z1 Compact on 4.4.4 for the longest time, mainly due to sound issues after updating to Lollipop.

Recently, the battery has been dropping randomly from 60 odd percent to 3 or 4 and then shutting down all within a few seconds. The last time it did this, I tried charging it when I got home but the charging light would not stay on, thus it was not charging. All typical signs of battery failure due to age.

Having already replaced the battery successfully on my Z1, I bought a replacement original Sony battery and replaced it. The problem persisted. On first boot, the phone got to the blue waves then black screen, and power off. Charging screen just showed the battery at about 40%.

I risked it and flashed the latest software with Flashtool, having done a complete wipe. The result of this proved no better, but I did get a different message on the charging screen, a message saying the phone had shut down due to overheating. Picture is attached.

The phone is in no way overheating and I've even booted it while sat on a shelf in the fridge to help dissipate any heat generated but with no luck.

So, the old battery maybe did overheat and caused the phone to shut down, I'll accept that as a probability. It may have even damaged something, but I don't think that's likely.

After changing the battery, I would have expected the problem to resolve itself, but it seems like some kind of hardware 'flag' has been raised that is now not allowing the phone to boot in case it overheats again.

Does anyone know of any way to resolve this, reset the 'flag' per se, other than going to Sony? The phone is definitely out of warranty due to its age, never mind me taking the back off lol

It is a shame because it has been a great phone over the years, and I would like to fix it if possible, even if to give it to one of the grandkids. I have my Z3 still (which I won't part with for anything) and I have an XZ too and both are great phones. I would just like to save the XZ1c if I can.

The phone is not, and has never been modified in any way, no rooting, no bootloader unlocking. Only stock roms have ever been flashed, and then only once or twice, to put it back on 4.4.4.

I have tried reflashing just the kernel, or just the system too, to no avail.

In desperation I even left it in the fridge for a few hours in case the temperature sensor was on the fritz, but that did nothing at all.

I just feel like there's nothing actually wrong with the phone, apart from this trigger that won't reset.

Any help greatly appreciated of course.

Thanks,

Mick
[Xperia Z1 Compact Q&A, Help & Troubleshooting] Daniel Kasep:
Maybe theres lot of consideration:

1. Rom Bugs

2. The Kernel not supported well

3. Battery Issues (But you already change it right)
[Xperia Z1 Compact Q&A, Help & Troubleshooting] ayunatsume:
There are two temperature sensors afaikin our phone. One in the SOC and another one in the battery (hence three pins).

The battery is probably the one giving the high temp report. Try yet another battery.

A bad battery normally heats up very fast inside and the battery temp sensor stops the battery from charging and/or working to protect the phone and the battery.

I changed my battery before when it had symptoms like yours 100-90-0 drop and after replacing with a battery from eBay it was OK. I gave it a full charge then complete discharge and then complete charge to full cycle the battery once and let the phone Guage its full capacity. one year later now my battery is acting funny again (not charging past 30%) and getting so hot when charging it triggers overheat control service in Android.
[Xperia Z1 Compact Q&A, Help & Troubleshooting] Karter Ires:
Any luck?

Apologies for the necro. But did you ever fix this issue, having the same problem
[Xperia Z1 Compact Q&A, Help & Troubleshooting] MickieH:
No, I never did figure it out. I've been loathe to spend more money on another battery when I've got other much newer phones. I really have no idea why it would not reset once the battery was replaced, maybe it's the replacement battery.

Have you tried changing the battery?

I've tried flashing different stock roms, Kit Kat, Lollipop, and it doesn't help.

Short of going to Sony, I'm not sure what else to do.
[Huawei Mate 9 Questions & Answers] tety:
For P9, P9 plus, i can change by Activity Launcher. But for my Mate 9 Pro i can't. Who's know?

Thank you
[Sony Xperia M4 Aqua] thgm21:
i unlocked the boo
[Sony Xperia M4 Aqua] NickMihal:
You can't use fastboot without drivers. What os use on pc?
[Nexus 7 (2013) Android Development] lollyjay:
Thanks will download when I get home
[Nexus 7 (2013) Android Development] followmsi:
Cool .. go for it :)

It seems there are some download issues using mobile devices.

Google Mobile version wants to redirected to some ...mobile... link, which is not working.

At least for me.

Also the import into Google Drive App seems not to work.

If you choose "request desktop version" in Chrome mobile settings it should work.

On normal desktop browsers there are no problems.

This issue occurs since a few days .. for "all" my Google Drive projects :(
[Nexus 7 (2013) Android Development] lollyjay:
Hi I downloaded in Windows 10 and all working atm. More after I test.

---------- Post added at 08:31 PM ---------- Previous post was at 08:01 PM ----------

ROM seems fully functional. Working well with data and dalvik formatted f2fs.

Your recovery is also functioning well, with the the exception that it takes over a minute to load. Not a problem for me though.
[Nexus 7 (2013) Android Development] followmsi:
This is related to F2FS .. if you would have ext4 data it will load much more quickly.
[Nexus 7 (2013) Android Development] boom1982:
After installation, does not go into the recovery (3.0.2)

On version 3.0.3-3, such a problem will not exist?

Which sections have the format f2fs ?, and whether it is possible to add a night mode? :)
[Nexus 7 (2013) Android Development] followmsi:
/system/bin/install-recovery.sh

You loose recovery .. this is normal ... if not rooted ..(SuperSU.zip)

The easiest solution is to install SuperSU.zip via TWRP.

Maybe I can remove it for next build .. not sure.

F2FS .. via TWRP

Wipe - Repair/Change file-system ...

Jus install the ROM and test and play yourself :)

Cheers
[Nexus 7 (2013) Android Development] rajsris:
Does micro gapps work with this ROM, or only nano?

Reason I ask is that some things (Face Unlock) don't come with nano and there is no easy way to add that back in that I've found.
[Nexus 7 (2013) Android Development] miki67:
Micro gapps works! [emoji6]
[Nexus 7 (2013) Android Development] finkbg:
I cannot install Gapps 7.1.1 (tried micro and aroma), message saying I am on Android 6.0.1 and need to use proper version. Deb.
[Nexus 7 (2013) Android Development] lollyjay:
I installed open gapps arm 7.1 pico with no problem. Not enough system available space for micro
[Nexus 7 (2013) Android Development] followmsi:
You can try to resize file system of system partition inside TWRP to get full partition size.

Or use the Update.zip_resizefs_flo.zip inside the download folder.

Works for deb too.

Cheers
[Nexus 7 (2013) Android Development] busdonic:
Hmmm not sure what I'm doing wrong. Tried the process twice, both times after reboot step, TRWP tells me no OS installed. Suggestions?
[Nexus 7 (2013) Android Development] finkbg:
Enough space is available for micro. I managed to install it after a few reboots (no clue how). However, having converted data to f2fs, I now cannot write to data from within the ROM (play store crashes on install of any app, webview cannot start a download and camera cannot save photos). Latest rom from yesterday, haven't installed any fstab patches (thought this rom being the next release would not need any patches, am I correct?). Any suggestions?
[Nexus 7 (2013) Android Development] bgiesing:
Keep in mind that all Open GApps installs can be customized so if you want FaceLock you would chose the lowest package with it and them use the config file to remove the rest of the differences.

Also Face Unlock DOES come with Nano BTW, only package without it is Pico.

(Disclaimer: I'm a former Open GApps team member.)
[Nexus 7 (2013) Android Development] finkbg:
Yes, micro works. It worked with the original ROM by nbehary and it works with this one as well.
[Nexus 7 (2013) Android Development] followmsi:
Did you fix your problems ?

The fstab has been changed ... you can verify yourself.

Open terminal app ..

su -
cat fstab.flo

To see the current partitons and there used/mounted filesystems ..

mount

Pls have a look here ..

https://xdaforums.com/showpost.php?p=71296026&postcount=716

F2FS seems to work fine on data - I still use it on cache only.

If you face strange issues, pls start with a fresh TWRP factory reset first.

Cheers
[Nexus 7 (2013) Android Development] rajsris:
Thanks for the info, I meant pico actually, as all other nougat roms for this device only have space for that package.
[Nexus 7 (2013) Android Development] js89:
Working fine here.
[Nexus 7 (2013) Android Development] TheDigitalSlacker:
I have the rom flashed and everything looks good with cache and data converted to F2FS. However I am experiencing an odd issue. When i first set up the tablet I sign in with my gmail account and everything looks good. I do a clean setup so nothing restores and download the official gmail from the play store. Once it installs and opens it does not seem to notice that my google account is configured. It asks me to add a mail account and if i put the same account in it says the account already exists. I've factory reset this 3 times trying something different each time thinking maybe I did something dumb. Flashed many roms before and never seen this, any ideas?

---------- Post added at 08:07 PM ---------- Previous post was at 08:03 PM ----------

dumb question but what does the partition resize change it to? I was looking to find a stock partitioning sizes vs this script chart or explanation.
[Nexus 7 (2013) Android Development] rajsris:
Will stock gapps fit system partition on Nougat?

For this rom, I've been installing only Micro gapps for this reason
[Nexus 7 (2013) Android Development] followmsi:
Pls read the thread .. we are replacing AOSP apps .. and add a few more.

Yes, the config above works with stock gapps on this ROM.

Tested myself ..:)
[Nexus 7 (2013) Android Development] drewski_1:
A subset with some configuration
[Nexus 7 (2013) Android Development] amujee:
Thank you for this rom. It's given my deb new life.

But I've run into a small problem.

I can't seem to get stock gapps installed on my deb. pico gapps installs fine.

Keep getting error 70, insufficient system parition size. I have the config file in the same place as the gapps file.

According to twrp, system partition size is 827MB, free space after installing rom is 349MB. EXT4 file system.

What could I be doing wrong?
[Nexus 7 (2013) Android Development] drewski_1:
Not enough excluded from install in the config file.

Look at the log file and you'll get info on how over you are and the size of the apps to inform what edits to make.
[Nexus 7 (2013) Android Development] followmsi:
Check your opengapps log file .. first.

If you use the config from the thread it should work.

Did you place the config correctly ?

The log will show if it's used at all .. like here.

Installing GApps Type | stock

Config Type | include

Using gapps-config | /sdcard/Download/.gapps-config

Good luck !
[Nexus 7 (2013) Android Development] amujee:
Got it working!

the opengapps log file showed that the config file wasn't even being used.

then I realized the config file name was missing the period in front. not sure how that happened. but even then I was still getting the same error even though the log file was now showing that the config file was being used.

I decided to just start the tablet without gapps. did a reboot into recovery and tried again. this time gapps installed.

Thank you for your help!
[Nexus 7 (2013) Android Development] TechnicsKuzya:
Hi, friend, yesterday i tested your kernel`s build and find a seriuos bug when I change kernel with using this files:

ElementalX-N7-6.06_AnyKernel2.zip

franco.kernel-flo-deb-r29_kernel-flasher-5.1-20170329.zip

google_msm_lineageos_kernel-flasher-5.1-20170330.zip

Quanta-Flo-v14_AnyKernel2_followmsi.zip

When I reflash new kernel - CPU|GPU frequency, type of Governor and numbers of active and sleep CPU changes randomly!? Your clear ROM have a one active CPU when standby, if I flash Quanta - have a minimum 2 or 4 active CPU with always MAX frequency, Quanta sometimes have ondemand, sometimes perfomancr Governor, etc... Crazy things with this kernels builds... and device works very slow with high battery consumption! Can you delete this files and give only the old variants (with SuperSU reflash) fol all kernels!?

Now I tested your kernels builds from OLD folder (with SuperSU reflash):

Update.ZIP_ElementalX...deb.zip - perfect, like clear ROM, 1 active CPU in standby, etc...

Update.ZIP_Quanta...deb.zip - good, but 2 active CPU in standby, etc...

Update.ZIP_Glitch...deb.zip - bootloop, don`t work....

Update.ZIP_lineageos...deb.zip - no this file :)

Update.ZIP_franco...deb.zip - no this file :)
[Nexus 7 (2013) Android Development] followmsi:
Thanks for your testing ..

Did similar stuff .. but more looking for general compatibility to this ROM.

Working with Glitch on the boot-loop.. this known.

The reason why I actually removed the file from the share.

The "clear" ROM comes with elementalx right now .. seems to work perfect.

The change of the installer should not change the behaviour of the kernel.

Like for quanta .. seems to be the same behaviour on both installers.

The point is that you normally should install the official kernel installer .. like for glitch kernel too.

If you use glitch installer it's booting fine on this ROM too.

All these installer configure the kernel, add special governors .. etc... etc.

As well all the apps to fine-tune the kernel settings .. did you test for quanta ...etc .?

Elementalx app seems to work fine ..

Elementalx seems to have a good "base" config already.. to work with standard AOSP ramdisk - without "special" config.

I have to use the "stock" AOSP ramdisk for this ROM and will not add kernel specific code into the ramdisk.

Still in testing mode .. but there are not much possibilities left right now.

Stock google msm (lineageos sources) like before or elementalx as in the moment.

Cheers

EDIT:

Running the franco kernel since a few days .. seems to run fine as well - without "special" config.
[Nexus 7 (2013) Android Development] TechnicsKuzya:
Your latest kernels installer, IMHO, don`t reflash settings/config (may it mix with previous kernel?), because default governor, frequency, number of active cores changes randomly with the same kernel installer. For example, I flash Quanta, then ElementalX, then Franco, then Quanta, then ElementalX and device is really slow and unstable, then I flash ElementalX (old installer), SuperSU - and all perfect.

Quanta with new installer - by default governor - perfomance abd 1728 Mhz, why?

P.S. I liked ElementalX, but can you by default disable DT2W, S2W and etc. for better battery life? And one more Franco Kernel and ElementalX have a different brightness auto control.
[Nexus 7 (2013) Android Development] followmsi:
Have uploaded ... Update.ZIP_Quanta-Flo-v14-deb.zip again . .for better testing.

Did you test the 2 kernels below as well ?

google_msm_lineageos_kernel-flasher-5.1-20170330.zip

franco.kernel-flo-deb-r29_kernel-flasher-5.1-20170329.zip

I used stock AnyKernel2 installer and stock lazyflasher 5.1 installer.

There are no settings/config which should be reflashed at all - this is the purpose.

As said above, If you install official kernel installer all the settings/configs will be made .. etc.

Here we want to keep "stock" AOSP and see which kernels are running "good" without "special" config.

Both installer are just replacing the kernel binary - no changes to the ramdisk.

The "old" installer did reflash the full boot.img - not extracting and repacking.

For this reason I don't understand the differences ...

Update.ZIP_ElementalX-N7-6.06-deb.zip / Update.ZIP_Quanta-Flo-v14-deb.zip

vs.

ElementalX-N7-6.06_AnyKernel2.zip / Quanta-Flo-v14_AnyKernel2_followmsi.zip

I have tested all the kernels before I have uploaded them .. except for the glitch kernel I did not have issues.

Aa said before .. I did not check all the values like you did.

But the system was always stable and usable .. with all tested kernels.

Yes, on some kernels the battery conumption seems to be higher .. etc.

Did you made a normal reboot after kernel flashing ?

Did the values change again ?

Maybe there are other triggers for the changing values ?

I am not a kernel expert, the idea was just to search a nice replacement for the standard google msm kernel .. :)

In the next release we will have a new full boot.img for deb and flo, like today.

Most probably we will stay on EX.

Here you can see the current kernel for this ROM .. deb andflo.

https://github.com/followmsi/android_device_asus_flo/blob/aosp-nougat/kernel

This is a monthly decision :)

And we still have some time left for testing ... :)

EDIT:
[MENTION=7579463]TechnicsKuzya[/MENTION] .. Thanks again for your input and testing ...

Here are the requested files .. made for you :)

Update.ZIP_google_msm_lineageos_kernel-flo-20170330.zip

Update.ZIP_google_msm_lineageos_kernel-deb-20170330.zip

Update.ZIP_franco.kernel-deb-r29_20170329.zip

Update.ZIP_franco.kernel-flo-r29_20170329.zip

Made a subfolder called "KERNEL" ... https://drive.google.com/drive/folders/0By6p5AdQfavBN0pDMk92ZUdnTTg

Now we have all 4 working kernels in both versions :)

Pls test and report if there are still differences ...

Thanks a lot for your help !
[Nexus 7 (2013) Android Development] m00head:
First of all, this is a great ROM! It is much more stable, faster, and bug-free than the official LineageOS ROM I tried previously.

Using your .gapps-config file when installing the stock Open GApps package, it does not appear to replace the stock AOSP Camera system app with Google Camera equivalent.

The only version of Google Camera which will install for me is version 2.7.008 from APK Mirror here:

http://www.apkmirror.com/apk/google-inc/camera/camera-2-7-008-release/

I have since manually uninstalled the stock AOSP Camera system app, using ES File Explorer Pro.
[Nexus 7 (2013) Android Development] followmsi:
Pls check your opengapps log first.

If you don't have clean data it will not install camera either.

As well you can force it.

https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options

You may need to test different config for automatic camera installation.

I have just one camera app anymore .. version 2.0....

But thanks for the update .. and describing your way.
[Nexus 7 (2013) Android Development] drewski_1:
Camera v2.0 is the AOSP camera :)

the "Legacy" Google Camera that Open GApps installs onto our devices is v2.7

does your picture options look like the first or send screenshot? the one with just Camer & Video is AOSP v2.0 and the one with Panorama etc. is Google Camera v2.7
[Nexus 7 (2013) Android Development] followmsi:
Thanks for the camera update ;)

I'm will check this .. again.

Especially I will check my own flo log again ;)

Did the gapps installation on 3 devices these days .. on dragon I had wiped data and it's also one camera now - but version 4.2.

Cheers
[Nexus 7 (2013) Android Development] followmsi:
Moved to the flo device to check now ..

The logs ....

WARNING: Google Camera has/will not be installed as requested. Google Camera

can only be installed during a Clean Install or as an update to an existing

GApps Installation.

Cheers ;)
[Nexus 7 (2013) Android Development] m00head:
I updated my original post with a link to a slightly newer 2.7.008 version which also works, and has the extra options shown in your 2nd screenshot.

You can easily tell which version of the camera you are using just by looking at it's icon.

AOSP Camera icon looks like this:

Google Camera icon looks like one of the following, depending on whether Pixel Icons are also installed or not:
[Nexus 7 (2013) Android Development] nigelhealy:
So if I want to dirty flash will the backup/restore addon work in your new ROM and so I simply just flash your new ROM?

Or, will it only work after I flash your new ROM for the next flash after?
[Nexus 7 (2013) Android Development] followmsi:
Works in this ROM here .. and in the next one coming ;)

AOSP_7.1.1_r28_N6F26U_flo-ota-eng.followmsi-v4-addon.d.zip

AOSP_7.1.1_r28_N6F26U_deb-ota-eng.followmsi-v4-addon.d.zip

ROM Upgrade Installation -> persistent gapps:

1. Boot into TWRP (3.1.0-4)

2. Install AOSP_7.1.1_r28_N6F26U_flo-ota-eng.followmsi-v4-addon.d.zip

3. Install SuperSU.zip - due to systemless rooting

4. Reboot back into system
[Nexus 7 (2013) Android Development] TechnicsKuzya:
Cool, thx, friend, I will test all kernels today!
[Nexus 7 (2013) Android Development] jhford:
Do you mean I should not flash sysrepart_1280_120.zip?
[Nexus 7 (2013) Android Development] Marko Kre:
After flash sysrepart_1280_120.zip you need immediately reboot into recovery. After that flash the Rom.
[Nexus 7 (2013) Android Development] followmsi:
As mentioned above .. Pls reboot into recovery again - between step 4 and 5 !

Good luck !

Edit:

In your case as you have repartitioned .. Just wipe system and install the ROM.
[Nexus 7 (2013) Android Development] yattodettaman:
You have to add qcom avc decoder and apply gralloc usage bits patch to fix black videos...
[Nexus 7 (2013) Android Development] firepower9966:
Repartitioned and installed pixel experience rom , but had no keyboard input, only voice, had to install Gboard (Google keyboard). This was wipe system but not data. Just like to thank the dev for a great rom I am greatly thankful to have pixel working on my flo.

Also seems to be rebooting every 5 to 10 minutes of use.
[Nexus 7 (2013) Android Development] jhford:
[MENTION=5480152]followmsi[/MENTION]

Thank you. Your edit instructions worked perfectly, except, FYI, I loaded this page immediately after my deb booted to send you a thank you reply and it spontaneously rebooted and I'm sending this reply from that rebooted state. What does that mean? More questions. What is the advantage of pie vis-a-vis oreo? Is Android Auto working; it errored out with oreo because of a Google Play problem and I installed Automate? Was the partition fix a one-time requirement as to future updates/upgrades? I have 2 debs. Does it make sense to do a nandroid backup of this one to my USB OTG micro SD card and do a nandroid restore from the OTG to deb #2? [[Second and third spontaneous reboots]] I have a Samsung Galaxy Note 4 N910T T-Mobile with replaceable batteries. Lots of them out there. I'm running Lineage Oreo unofficial. How about porting this ROM to it? You'd make countless new friends.

Thanks again. Great job.

[Edit]

Android Auto launches but I haven't tested in my car yet. Also, the battery seems to drain super fast.
[Nexus 7 (2013) Android Development] lollyjay:
Sorry... I gave you old method. That zip is much better :p
[Nexus 7 (2013) Android Development] Rockwig:
PixelExperience Flo feedback.

As noted elsewhere, there does seem to be a memory leak somewhere. Device will hang and reboot every so often.

Also, wireless charging does not appear to be working.

Other than those, its amazing that we can have Android P on this device.

Edit: I stand corrected, wireless charging does work.
[Nexus 7 (2013) Android Development] lollyjay:
[MENTION=5480152]followmsi[/MENTION] PixelExperience_flo-9.0-20190118-1104-UNOFFICIAL.zip is very fast and smooth. My only concern is that the microphone fc whenever I try to use it (Google, Speech to text, etc)

[MENTION=295365]Rockwig[/MENTION] my wireless charging is working fine (flo)