yashsingh1/xdaforums huggingface dataset:
[Sony Xperia M2] harbinfetaii:
Hi there,

I'm getting this error while I'm sharing hotspot. Is anyone else having this issue?
[Sony Xperia M2] f2065:
At me it normally works.

But, I made the adoptaple storage in the old firmware 7.1.2, cleared everything in the TWRP, installed LOS 15 alpha 3 - the old adoptaple storage was preserved and works normally…

At me too this bug.

The access point turns on and works, but with several attempts.
[Sony Xperia M2] basem_ym:
just reboot...
[Sony Xperia M2] mantazzo:
I wonder, will Lineage team add the newly announced Android GO feature... I think it would be great for this phone if it works.

(P.S. As far as I understood, it is a feature of Android 8.1, right?)
[Sony Xperia M2] galaxyfreak:
Android Go consists of 2 parts:

Few new build.prop flags which are supposed to optimize memory usage.

We will definitely enable those.

Lightweight GApps

Not sure how will people (OpenGApps team) get their hands on those until a device with Go is launched.

Yes. As always, Lineage team is working on a merge.

More news soon.
[Sony Xperia M2] f2065:
Problems with alternative sensors…

At D2403 rev5, after 2-3 days of operation, LOS 15 alpha3 start the same problems as in LOS 14 RC3, and the proximity sensor starts working continuously.
[Sony Xperia M2] galaxyfreak:
dmesg output maybe could help. I can't promise anything.
[Sony Xperia M2] basem_ym:
true, I dont know which rev in my hand, but a noticable better performance, less lags, more smoothness happens when autorotation enabled.

even on LOS14 RC3, I used to enable autorotate when phone gets hot and unusable.

as said, autorotate slightly improve performance not fixes anything and I really think this makes no sense but posted anyway.

a dmesg is on its way.
[Sony Xperia M2] f2065:
I began to notice the friezes and the constant flashing of the proximity sensor did not come immediately.

First a few days it was OK!

The problems began after the VPN settings (I need a VPN to connect to their local networks) and setting the PIN.

And now, the proximity sensor starts to glow constantly in all modes after half a day of work.

After the reboot - the first few hours the proximity sensor glows sometimes, not permanently.

When you turn off the screen - does not light up.

And then, after half a day, the sensor glows almost constantly, and when the screen is turned off, it also glows.

At the same time, noticeable lags in programs begin.
[Sony Xperia M2] galaxyfreak:
Not enough scrollback. :( I just see chrome crash.
[Sony Xperia M2] basem_ym:
any tip for pulling a useful dmesg?

anything? :(
[Sony Xperia M2] Konstantinosj77:
Hey guys,

Please, replace /system/etc/sec_config with this and report back.
[Sony Xperia M2] f2065:
Installed, waiting ...

In LOS15 bugs started a little later than in LOS14. In LOS14 by the evening, there were stable bugs, and in LOS15 they grow more slowly, in about 2-3 days.

And why does the proximity sensor work all the time?

The screen is off and the proximity sensor is working.

However, I did not find any actual benefit from his work.

I close it with my finger or I do not close it: the phone is switched on by the power-button the same way, the PIN-code is entered equally.

We can assume that if the proximity sensor sees that something is pressed against it - then the screen should not be pressed.

But this is not so - everything is clicked on the screen.
[Sony Xperia M2] Konstantinosj77:
No Idea why this happens.

It only happens on devices with alternative sensors.
[Sony Xperia M2] basem_ym:
done, seems promising.

Is this supposed to do any thing with freezes?

I was playing coc just before I saw your post and replaced the file.

rebooted and opened coc again, game got faster but I can't confirm if its related to this file or to a ram refresh.

will report more later.

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

Edit: (not related to sec_config file)

I noticed that freezes and heating happens much more often when using 3G than wifi.

Q: in developer options, some thing called like separate webview, I wonder if enabling this can improve thimething :confused:
[Sony Xperia M2] Konstantinosj77:
It's probably due to RAM refresh.

It's a crazy idea/test. Let's see if it brings any changes.

About heating, 3G/4G uses more power than WiFi..it's normal for the device to heat up more.

For Nougat and Oreo we switched from thermanager to a kinda "closed-source" solution. We can always revert back to thermanager.
[Sony Xperia M2] galaxyfreak:
Thermamager config sucked, caused slow charging, thermal throttleing and whatever. I'd much rather prefer not to go back to it
[Sony Xperia M2] Konstantinosj77:
Yeah I remember those problems,althought we kinda fixed them in last CM13.

Anyway I agree,that's why we QCOM solution for so long. ;)
[Sony Xperia M2] basem_ym:
hay boss, seems like it didn't help, or helped a very little bit.

sorry for disappointing feedback :( [MENTION=596047]f2065[/MENTION] did you find any deferences mate?
[Sony Xperia M2] Popov22:
if your power button is broken! how do you power up your phone?:confused:

because me too my power button is broken

can u help me how to power up
[Sony Xperia M2] Billabomb75:
Well my phone automatically reboots it self when its off. But if you want to switch on your phone plug it in on charger. Let the charging battery shows. Then next to your sim card is a small orange dot which says off you use a needle to press it and unplug your phone. Then your phone should boot up

---------- Post added at 07:25 AM ---------- Previous post was at 07:25 AM ----------

Well my phone automatically reboots it self when its off. But if you want to switch on your phone plug it in on charger. Let the charging battery shows. Then next to your sim card is a small orange dot which says off you use a needle to press it and unplug your phone. Then your phone should boot up
[Sony Xperia M2] f2065:
I did not notice any improvements.

Today, heavy lags started when the programs were launched. As usual, 2 days after reboot.

And the proximity sensor works all the time.
[Sony Xperia M2] Billabomb75:
Does alpha 3 have button waking ?? Like vol buttons wake up device
[Sony Xperia M2] harbinfetaii:
No, it doesn't.
[Sony Xperia M2] f2065:
The sensors began to hang after 1-2 days. Presumably, after the new sec_config
[Sony Xperia M2] walkman-610:
the gps leaves much to be desired. during the trip in 15 minutes,the city,the connection was lost 3 times
[Sony Xperia M2] f2065:
At me it has begun in 7.1.2 RC2 or RC3.

But not in all programs: Locus Map is normal, Yandex.Maps - GPS losses…
[Sony Xperia M2] skrubxgt:
[/COLOR]I cannot wait for stable version!

Everything is perfect but camera :\ Footej isn't good as stock Lineage camera
[Sony Xperia M2] walkman-610:
Hello. tell me, is it expected to update soon?
[Sony Xperia M2] f2065:
+1

At LOS 15a3, the battery consumption is high, 20-30% per night. In LOS 14.1 RC3 - consumption was much lower - about 10-15% per night (and in the stock firmware - less than 5%).

And problems with hangs through the day of work. And the programs start to run very slowly…
[Sony Xperia M2] galaxyfreak:
We've seen your report, no need to repeat yourself.

Maybe I wasn't clear enough, we cannot reporoduce, nor we use our M2's daily anymore.

Issues we CAN confirm are ONLY ones that can be reproduced by clear steps.

Like video recording - you click red button, it doesn't work. Bug confirmed.

"But my phone slows down after X time of use with X apps."

Sorry - we don't use the phone, and we don't use the apps, our sensors are different than yours.

My phone is in the drawer without even gapps.

If there's anyone who still actively uses their phone, and wants to take over development, feel free to do so, create your own Lineage 15.1 thread.

So, about new build - it's not coming soon because it's not anything better than what you currently have.
[Sony Xperia M2] f2065:
Identified bugs, but so far I have not found the exact reproduction algorithm:

1. After the reboot, Wi-Fi is turned off. Not always.

2.The sound of connecting the charger often does not sound.

3.If there is a long connection to the computer - then after half an hour the phone sometimes reboots. Sometimes within a few hours after connecting.

Periodically, all sensors (proximity, accelerometer, brightness sensor) stop working.

Here is the dmesg log when all the sensors do not work. Can you understand the reason?
[Sony Xperia M2] JuniorCaesar:
[MENTION=4635923]galaxyfreak[/MENTION] is there any way to disable illumination bar blinking when phone has low battery(and charging)? for notifications it is useful to have, but it drains battery as hell when battery is below 15 percent
[Sony Xperia M2] TrafalgarD:
up for m2 _/\_ still use this phone
[Sony Xperia M2] Billabomb75:
I know we not supposed to ask for ETA. But just wondering when is the next build coming. I use my Sony for everyday use
[Sony Xperia M2] galaxyfreak:
Disable for charging but leave enabled for notifications?

No, could have been done actually with some more code - I didn't make any nodes or props to make it user-controllable. Oops.

If you wanna disable it all together, I believe you know how to do, as you explained to the person in 14.1 thread.

There is no new build planned at this point. Not this month atleast.
[Sony Xperia M2] f2065:
I deleted a lot of applications - and the bug with the proximity sensor disappeared, the slowdown bug also disappeared.

Probably, the problem was not associated with alternative sensors.

I gradually began to install applications, and a bug of constant work of the proximity sensor appeared after installing PingTools Network Utilities by StreamSoft.

This is not the only application in the presence of which there is a bug (previously there was a bug without it), but I have not found the others yet.

In the PingTools settings, there is an option to collect OpenSignal data. If this option is enabled, the proximity sensor flashes periodically. For example, when working in Yandex.Maps. And at the time of launching various applications.

Moreover, at first the sensor flashes rarely, and after a day of use it starts blinking almost constantly.

If the option to collect OpenSignal is turned off - then the proximity sensor does not blink, but still slows down.

So, it is necessary to reproduce the bug:

- Adopted Storage.

- install 100+ different applications (but, it may not be necessary)

- set the PIN to the screen (but, it may not be necessary)

- Install PingTools Network Utilities by StreamSoft with the default settings, start it (accept the agreement).

- install Yandex.Maps (there is an issue best shown).

- use the phone for 1-2 days.

I can stop using PingTools. But, the bug appears gradually and accumulates - obviously a leak of some kind of memory. And this is not the only program, a similar bug was without it, but now it is a convenient example for reproducing a bug.
[Sony Xperia M2] galaxyfreak:
Thanks, this definitely makes more sense than Yandex.Maps itself triggering proximity sensor.

One thing btw - you listed adopted storage as a requirement to reproduce - so is it all good when adopted storage is not used?
[Sony Xperia M2] f2065:
It seems to me that in the case of adopted storage, lags are stronger (more noticeable). But probably this is because SD memory is slower.
[Sony Xperia M2] skrubxgt:
Any update?
[Sony Xperia M2] JuniorCaesar:
i can't understand why people are asking for an update time. no offense, but dev already said a couple posts ago why.
[Sony Xperia M2] Szwajowy:
Is it dead ? No ETA, just is someone still doing something ?
[Sony Xperia M2] Konstantinosj77:
No, it's not dead.
[Sony Xperia M2] f2065:
The program causing the occurrence of lag (PingTools, GPSlogger, OpenSignal) I deleted, and now there is no lag. But it is a problem of this firmware, they work fine in the original firmware.

Sometimes (every few days) there are rebates. Usually, either when viewing the intragram, or soon after connecting to the computer.

I do not know how to save logs during reboot.

High battery consumption. Overnight - from 100% drops to 80%. On stock - 95%.

In the list of consuming applications - Google Play services 16%.

Sometimes (every few days) all the sensors stop working. At the same time, the phone is difficult to unlock - it almost does not light the screen for almost a minute, probably trying to interrogate the sensors.

Logs I posted in the message # 285.
[Sony Xperia M2] basem_ym:
Just a reminder...

M2 is only 1GB Ram

Go to developer options>running services

See ram consumption(its nearly full, always)

Mostly because of Gapps.

See cached procceces too, many many useless apps, I didn't find any way to kill them entirely.

In my opinion, when your phone lags or freeze, in this while exactly: ram gets full and LMK do its work.

When LMK consider which app it should cutt off(it may cut off any app, lets say play store), here you get some free ram, at this while, playstore for example checks for updates, ram gets full again, LMK cuts off......etc, until LMK decides to kill systemui, at this moment, the device becomes useable.

Maybe every thing I said makes no sense, but I couldn't find better(or more reasonable) explanation.

I tried this rom for a couple of days without gapps.

I felt like I have a Sony Z5 in my hands.

One more thing, posting problems without logs is just like reading a white paper (nothing,useless)

Consider using microG.

---------- Post added at 11:20 PM ---------- Previous post was at 10:44 PM ----------

@Oreo_Users

Take a look at this thread:

https://xdaforums.com/android/software-hacking/mod-low-ram-property-patcher-android-t3737373
[Sony Xperia M2] JuniorCaesar:
I tried flashing gapps (just for my curiosity) over clean flash and guess what, my phone just froze for 1 minute and i did nothing when this happened.

It is clear that gapps is slowing down our phone. microG is much safer and takes tiny amount of ram
[Sony Xperia M2] jlpineda.ap:
They do a good job, I would like an update, and I know that the developer is busy waiting for an update without anything in return, a thank you for a good job, is little compared to those who still use this type of smartphone , I add that the errors that have been noticed in a normal use are: Mixer path that can not increase the volume even by changing to 96% The other common error is about that it gets very hot when I use YouTube and of course from the start we hope that the functionality of L will be enabled A camera that Footej is slow and is not compared with the lineage or stock camera, updating some apps that I think are from 4.4.4 no Oreo or something similar, to make this reference is required error logging , but it is not necessary as they are mistakes that would leave me alone.
[Sony Xperia M2] JuniorCaesar:
1-) are you setting mixer-paths for speaker?if so, the glue under the speaker grill is preventing volume a lot so this doesn't make any sense.

2-) about youtube, try to use less apps and force close them. on my side, i get heating only when i play games. also use microg instead of gapps

3-) you can sideload google apps and get rid of them, these apps are compiled from aosp. so it is google's fault
[Sony Xperia M2] f2065:
Again, all the sensors stopped working.

In the log I see that the problem with I2C

Is it just me?

[ 9145.237095] 3,340212,9145237095;qup_i2c f9924000.i2c: Transaction timed out, SL-AD = 0x48
[ 9145.241268] 3,340213,9145241268;qup_i2c f9924000.i2c: I2C Status: c000000
[ 9145.244922] 3,340214,9145244922;qup_i2c f9924000.i2c: QUP Status: 0
[ 9145.248172] 3,340215,9145248172;qup_i2c f9924000.i2c: OP Flags: c0
[ 9145.256281] 3,340216,9145256281;stk3x1x_i2c_read_data: i2c read fail, err=-110
[ 9145.259545] 3,340217,9145259545;stk3x1x_enable_ps: write i2c error, ret=-5
[ 9146.297093] 3,340218,9146297093;qup_i2c f9924000.i2c: Transaction timed out, SL-AD = 0xf
[ 9146.301102] 3,340219,9146301102;qup_i2c f9924000.i2c: I2C Status: c000000
[ 9146.305020] 3,340220,9146305020;qup_i2c f9924000.i2c: QUP Status: 0
[ 9146.308194] 3,340221,9146308194;qup_i2c f9924000.i2c: OP Flags: c0
[ 9147.347117] 3,340222,9147347117;qup_i2c f9924000.i2c: Transaction timed out, SL-AD = 0xf
[ 9147.351126] 3,340223,9147351126;qup_i2c f9924000.i2c: I2C Status: c000000
[ 9147.354856] 3,340224,9147354856;qup_i2c f9924000.i2c: QUP Status: 0
[ 9147.358114] 3,340225,9147358114;qup_i2c f9924000.i2c: OP Flags: c0
[ 9147.362283] 3,340226,9147362283;kxtj2 1-000f: kionix_accel_grp4_report_accel_data: read data output error = -110
[ 9148.407107] 3,340227,9148407107;qup_i2c f9924000.i2c: Transaction timed out, SL-AD = 0xf
[ 9148.411133] 3,340228,9148411133;qup_i2c f9924000.i2c: I2C Status: c000000
[ 9148.414847] 3,340229,9148414847;qup_i2c f9924000.i2c: QUP Status: 0
[ 9148.418122] 3,340230,9148418122;qup_i2c f9924000.i2c: OP Flags: c0
[Sony Xperia M2] sudden36:
You might be onto something. For me, soon after the sensors stop working usually also the screen refuses to turn on when pressing the power button. Only a reboot (or reset) can fix that. Maybe some voltage regulator or I2C interface isn't initialized correctly after wakeup from standby?
[Sony Xperia M2] f2065:
The screen before turning on tries to interrogate the sensors for more than a minute, during this time the screen turns off again (before it is turned on).

To turn on the screen, I press the volume buttons at intervals of a few seconds for several minutes - the screen turns on at that time.

Then you can use the phone, restart it correctly through the menu.

The sensors do not work at this, when running programs to work with sensors - the programs hang for a minute.

I installed Resurrection Remix-N RC 3 - and the sensors also stop working after 2 days.

But earlier in RR this problem was not! There used to be a problem with lags - but I detected the apps that lead to lags with this kernel and do not install them any more.

Maybe the problem is related to new versions of Gapps or new versions of Magisk.

And maybe the problem accumulates for a while, but earlier because of the lags, I rebooted the phone before.
[Sony Xperia M2] f2065:
If the Resurrection Remix-N does not use the "pocket detection" and "accidental touch" modes (with sensors working continuously when the screen is off) - then the sensors stop working in a day like in LOS15.

If you turn on the "pocket detection" and "accidental touch" modes, then the sensors work constantly, and it seems that in this case they do not break after a few days.

Probably that the sensors really have a problem with getting out of sleep mode. And if there is no sleeping mode, then there is no problem.

In LOS15, I did not find similar options for sensors to work constantly...
[Sony Xperia M2] galaxyfreak:
Yeah I've seen log above and i2c error but I have no clue why it happens.

However, pocket mode isn't exactly what you explained. Sensors never work constantly.

Pocket mode is a feature that checks proximity sensor after you turn your phone/display on from sleep. If it detects something close, it turns it back off assuming it was accidentally pressed in your pocket. You can test this by covering proximity with your hand then pressing power button.
[Sony Xperia M2] Jaggerjacquez:
Can this one be used for daily driver?
[Sony Xperia M2] martindroid:
yes, I use this as a daily driver.
[Sony Xperia M2] Jaggerjacquez:
Well, what about the proximity sensor thingy? Any other bugs or something besides the video recording?
[Sony Xperia M2] martindroid:
Proximity sensor work all time,when you are on lockscreen!

Video recording work fine with footej camera!:svetius:
[Sony Xperia M2] Jaggerjacquez:
Can we use another camera app for recording or just footej? Thx
[Sony Xperia M2] martindroid:
Video recording works only with footej camera!:good:
[Sony Xperia M2] OmarValdez:
I test:

$adb shell

$bash

$sysrw

ERROR:mount: '/dev/block/bootdevice/by-name/system'->'/system': Device or resource busy

I resolved:

$adb shell

$mount -o rw,remount /system

And in file /system/etc/bash/bashrc modify:

alias sysro='mount -o ro,remount /system'

alias sysrw='mount -o rw,remount /system'
[Sony Xperia M2] iwantz:
[MENTION=4635923]galaxyfreak[/MENTION]

thank you both,I use d2302 and this Rom goes well since yesterday I flash.I did not find many problems, and I think it is very stable for my daily use .

Even the substratum works perfectly, I appreciate your hard work.

:good:
[Sony Xperia M2] jlpineda.ap:
Here I will be waiting for the new update :(
[Sony Xperia M2] galaxyfreak:
New build coming up, Lineage 15.1 (Android 8.1), color engine called "Berry", Dark mode option, all new Lineage icon pack, many features forward-ported from 14.1 :)

Sensors issue, and video recording, still clueless, doubt they'll ever get fixed honestly.

cc: [MENTION=4550509]Konstantinosj77[/MENTION]
[Sony Xperia M2] iwantz:
The best news of the day, thank you very much :fingers-crossed:
[Sony Xperia M2] oreo02:
I got video recording working with Google camera version 4.1 and making the video resolution lower (back camera 720p, front camera CIF) Hope it helps! :)
[Sony Xperia M2] luigioctaviano:
What a good news!

Wow, I'm so excited to test it. Just installed Alpha 3 today although I experienced some expected bugs [like the battery icon not changing, Package Manager force closes (dunno if that's just me or I installed an incompatible apk)], I think this build is much faster than the 14.1 build. Good job, guys! I'm looking forward on your new build. :)
[Sony Xperia M2] Konstantinosj77:
ALPHA 4

Changelog

- Latest LineageOS/Android sources

- Include Snap camera app

- Many of the cm-14.1 features

- Dark mode

- Colour engine

- New power menu

- New LineageOS adaptable icons

Download
[Sony Xperia M2] Sner98:
Good work :)
[Sony Xperia M2] skrubxgt:
OMG Im so happy!! Thank you very much!!! Wanna go for a beer? :D
[Sony Xperia M2] JuniorCaesar:
Man, what kind of magic did you applied to that colors! Whites are no more yellowish, thank you so much for that!

Also, I love that icons :)
[Sony Xperia M2] leho6694:
What root method work with latest a4 ?
[Sony Xperia M2] JuniorCaesar:
+1 for that, magisk installer zip brokes package installer
[Sony Xperia M2] leho6694:
I've been testing for an hour and work, flash this and turn on root access in developer options.:o
[Sony Xperia M2] JuniorCaesar:
yep, it worked:good:
[Sony Xperia M2] walkman-610:
livedisplay does not work

Sent from my D2302 using

sorry for my English
[Sony Xperia M2] iwantz:
I still use SuperSU 2.8.2 SR3 as before, it's just that I have to install SuperSU app from playstore And update binaries afterwards.

But I have tried for almost 2 hours and work well, even on the substratum and mixplorer.

Unfortunately, advance reboot option to recovery is not working(power menu),Has anyone tried it and succeeded?
[Sony Xperia M2] walkman-610:
I can not install applications from the phone's memory. before that, everything was fine. log attached
[Sony Xperia M2] martindroid:
For live display And night light fix flash this:
[Sony Xperia M2] JuniorCaesar:
format system, data, cache and only flash rom and lineage root addon (also gapps if u want ofc)
[Sony Xperia M2] ghadeerprince:
there is no gapps for 8.1 on opengapps site!!!
[Sony Xperia M2] iwantz:
I use this unofficial gapps(nano) from here :

https://xdaforums.com/android/apps-games/arm-unofficial-opengapps-builds-android-t3743495
[Sony Xperia M2] xazakasrizava:
So far so good, I have a few things to say though:

1) There should be a link to the proper gapps in the first post. It was quite hard to find the proper ones.

2) Is there anyway possible to use the ambient display from Lineage 14.1?

3) charging LED does not work.
[Sony Xperia M2] walkman-610:
the clean install method did not work. Still, applications are not installed from the phone's memory. from the market are downloaded 2 times, but not installed, error 963 appears:crying:
[Sony Xperia M2] leho6694:
2) Read few posts higher

3) Led working fine,both this on top and led bar.