yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] the.gangster:
If you only read the correct thread: I did already earlier today...

(and by the way [MENTION=8075440]gm0[/MENTION]: you should nevertheless also resign such a zip before going public...)
[Galaxy S II Android Development] gm0:
The reference was actually to your name still being in and on it but sure, if you care - TWRP has signature verification disabled by default so most users probably won't care.
[Galaxy S II Android Development] the.gangster:
I understood your shout-warning already. As before already I didn't comment on that, as IMHO nobody should upload modified files of other users anyway without making it obvious to anyone in the filename...

The hint to sign it was rather on your instructions to make kind of sense at all. As TWRP recovery has (as you already wrote correctly) native support for flashing .IMG files, the .ZIP obviously is not targeting users who simply want to update from TWRP to TWRP, but those who want to flash direcly to latest build from a non-TWRP recovery (or to have such a version inplace for such a use-case). And those usually depend on files being properly signed.
[Galaxy S II Android Development] gm0:
Fair enough, didn't think of that. The only other recoveries I ever used were CWM and PhilZ and both worked fine with unsigned archives so I never bothered with signing for my personal needs. Plus I never felt the need to flash TWRP as a .zip, anyway.
[Galaxy S II Android Development] laptopu:
Using latest nightly is proximity sensor working properly? During phone calls the black screen doesn't turn on when i move phone away from my ear and GPS status app isn't showing roll of pitch movements properly.
[Galaxy S II Android Development] gm0:
All sensors working fine here, might be a hardware issue. If it's the GPS Status app I know then you can also calibrate pitch and roll there, try resetting that maybe.

The screen staying black during calls even when not "near" has been like that for me since I first installed LOS, it's a bit annoying but I thought it was a feature. Screen proximity based sleep/wake during calls actually works correctly as well.
[Galaxy S II Android Development] laptopu:
I think it's a software not hardware issue. Gps status app doesn't need calibrating, the pitch and roll are not displayed properly and the compass isn't working.
[Galaxy S II Android Development] gm0:
Possible but since I'm not having your issues it's unlikely a LOS issue, more likely due to your apps. Also I just made a call and the screen wakes up correctly during a call when not "near", so strike what I previously said, must have misremembered it.
[Galaxy S II Android Development] s2l9100:
I just made a test with my car and navigated, using google maps, to the next town. Everything went fine with gps, pointer, compass and etc.

Just sharing...

The only problem i have is with SuperSU - can't update the binaries but that is for another part of the forum. :)
[Galaxy S II Android Development] ale5000:
Does TWRP 3.1.0-0 work fine or there are problems?
[Galaxy S II Android Development] gm0:
Meanwhile the supported su package works fine: https://download.lineageos.org/extras

For me the new adb backup feature doesn't work at all and trying to use it reproducibly breaks the recovery to the point where it needs to be rebooted. Also trying to downgrade to 3.0.2-1 from 3.1.0-0 failed to the point where I needed to re-flash the recovery in download mode - have not tried to reproduce that one yet. The rest seems to work fine so far.
[Galaxy S II Android Development] the.gangster:
Maybe you are not doing it correctly?

I tested the new backup feature as well as flashing back to 3.0.2-1 successfully already before I posted in the TWRP-thread.

Did you really use the correct syntax to trigger the streamed backups? It worked with no problems. The only thing I don't like yet, is the fact, that you don't see which partitions were backed up if you triggered it by commandline and select the backup's local copy in the recovery-menu. So if you backed three partitions and only want to recover one of them, this is not possible so far. But even that is documented behavior.

Anyway, all this should be discussed in the TWRP-thread in my opinion. So in case of further problems, please post there.
[Galaxy S II Android Development] gm0:
Yarly. But it always fails basically like this:

Sending TWIMG to adb
I:Reading '/dev/block/mmcblk0p5', writing '/tmp/twadbbackup'
I:Error writing destination fd (Broken pipe)
Backup Failed. Cleaning Backup Folder.

after which adb dies:

Cannot write to adb control channelError with ADB Backup. Quitting..."

(the errors in the error message are theirs)

Well that's trivially worked around by not backing up everything into a single file but instead into separate files using the -f parameter.
[Galaxy S II Android Development] laptopu:
With respect your advice isn't really substantive more an opinion in line with a lot of your recent'advice' others have also disagreed with.
[Galaxy S II Android Development] gm0:
Lol, sorry not sorry my LineageOS is working correctly, my bad for mentioning it, now let me find that /ignore function and let's leave it at that.
[Galaxy S II Android Development] laptopu:
That's exactly what I'm talking about. Reading some of the stuff you have said to others you seem to think you have the perfect answer then when someone disagrees with you it's either your system is fine or you don't care. Not particularly community spirited especially for a relatively new forum member as you are to behave like this.
[Galaxy S II Android Development] MigoMujahid:
Take it easy guys, we all make mistakes, and we all have lack of Knowledge, no one knows everything, no body is perfect, but we cooperate together to fix our problems, don't we? :)
[Galaxy S II Android Development] Doc73:
Dear All,

just a question: I've noticed a very fast battery drain with LOS.

Some data:

- I never use the phone (it's now a secondary phone) and wifi and 3g are always off;

- There are very few apps installed;

- It loses 30%-40% of battery in five or six hours.

I switched to LOS for a short time and with CM13 I did 3 or 4 days with battery.

Could you, please, confirm this behaviour? Thanks in advance!
[Galaxy S II Android Development] laptopu:
Totally agree :)
[Galaxy S II Android Development] gm0:
My battery consumption is slightly higher with LOS than it was with CM13 but only slighty, nowhere near your experience. There are way too many factors involved to make comparing actual battery duration between users useful in any way so I won't give you numbers.

I suggest you go through your settings and disable all background processes that you do not need. Do you need to have your device wake on proximity for example? If you don't, disable it and the proximity sensor won't have to be permanently enabled. Do you have voice input features like "Ok Google" enabled that constantly use the microphone? Things like that.

You can find battery stats apps that give you a more detailed analysis of what is active on your device and using your battery.
[Galaxy S II Android Development] Doc73:
Thank you very much for your quick response.

I'll give a look at settings. Wakelock Detector reports use an excessive use by google system. :(
[Galaxy S II Android Development] gm0:
No problem. Seems you figured it out then.

The easiest way to get rid of some things google is to simply flash a smaller opengapps package by the way. Personally I'm running the pico package which only gives you the essentials. If you flashed a bigger package but are not using any of the added functionality you could downgrade. To do so download the smaller package, wipe only the system partition in recovery then flash LOS, gapps and (if needed) addon-su again. You won't lose any of your data.

Personally even with the pico package I have a lot of google services disabled in addition. Most of them are just about sending telemetry data back to google, anyway, and in no way relevant to your system.
[Galaxy S II Android Development] Doc73:
I also use the pico gapps! ;)
[Galaxy S II Android Development] gm0:
Oh good then. So it must be one of the settings. I don't know that Wakelock Detector app but does it not tell you what google service exactly holds the problematic wakelocks? That should help you narrow it down. Good luck! :)
[Galaxy S II Android Development] the.gangster:
I had no problem to backup the boot partition (tested on CM13+this one). What commandline did you trigger exactly?

And for the workaround: you didn't get what I mean: sure it is key to name the files accordingly with the -f parameter anyway. But I was hinting on the fact, that the backup is also stored displayed locally on the phone. And if you select that backup on the phone for restoring, it doesn't give you that information. So it's kind of useless to keep them on the phone, if you have to compare them to your properly named files on your PC first to have the reference to its content. (The phone's folder only contains the log, the content is stored only on the PC)
[Galaxy S II Android Development] gm0:
Oh, these stay stored on the phone? That's peculiar and doesn't sound like how it should be. From the instructions I was thinking the backup would be streamed back to the phone on a restore since they say:

I thought that was the entire point of this feature. I'm already automatically moving twrp backups from phone to desktop, I thought this feature would allow me to skip the step of adb pushing them back when needed.

Anyway, the command I used for that log snippet I posted was adb backup --twrp boot but I've tried other combinations including simply adb backup --twrp which is supposed to bring up the gui and allow you to choose partitions from the backup page - none of that ever happens, it just fails instantly.

If you have an idea about what I should try I'd be happy to give it a go but as long as I remain the only one with the problem I don't think it's worth losing sleep over. Thanks for trying to help either way.

PS: Since it might matter, I used this adb version (should be the latest) on Win10 x64:
[Galaxy S II Android Development] s2l9100:
Hello,

I can't confirm your report - about 5% battery lost after 8 hours sleep - and i have much more apps than you.

I started with nano gapps and then installed ca 20 more apps.

I have a new battery "Polarcell" - i kept strictly its manufacturer instructions about first time use.

About the battery levels i'm using few methods on my rooted phone:

- "Power save" profile all the time.

- one program for apps hibernation in which i added many apps to take care of( i don't really know whether that helps ).

- In the "Kernel Adiutor" i changed on boot three options - CPU Governor "Pegasusq", I/O Sheduler "Noop" and TCP Algorithm "Reno"

- With another app i disabled "starting on boot" most of the programs which i don't see a reason to be active right after rebooting.

- i don't know whether this is relevant to you but check if google voice is using your mic all the time - i had that problem with my guitar tuner app.

Of all 7.1.1 ROMs this one works best for me in all aspects and i'm very thankful to the LOS team.

Btw: I have tested other most popular 7.1.1 N roms and with one of them after i woke up my phone was shut down - 0% battery.

I'm new when it comes t android OS but i read carefully what the Pros are writing about stuff that i'm interested in.

Have a nice day! :good:
[Galaxy S II Android Development] the.gangster:
Just to finalize the recovery discussion here:

Yes this feature allows you to skip pulling the backups from the phone to your desktop and pushing them back manually when needed, as the data is streamed to and from your PC.

It's just that on top of that, a copy of the backup is also kept on the device without telling you anything about its contents. That's what I consider to have potential for further development.

And your quoted commands do exactly what you expected from the documentation already.

Tested here with adb versions: 1.0.31, 1.0.36 (Revision 84e3321d5db3-android), 1.0.36 (Revision 0e9850346394-android). W7x64 (with Android Composite ADB Interface driver from leshcatlabs.net)

EDIT: Looking at it once more I realized that on the phone there actually is no copy of the backup left behind but only a folder with nothing more than just the recovery log. That's why the GUI shows it in the recovery-menu but fails to give any details of its content. So the backup is only streamed to and from the PC and nothing else than that.
[Galaxy S II Android Development] gm0:
[MENTION=6560258]the.gangster[/MENTION] since it doesn't work for me I couldn't know what it's actually doing when it does. but you're quite right, let's end the off-topic discussion here. thanks though. :)
[Galaxy S II Android Development] dumdidum123:
I have still hudge problems with bluetooth control keys. I tried very long time and i got it working for a few minutes. After a reboot it worked fine but just for a few minutes. Then the keys stopped working -.-

When I connect the bluetooth speaker to another device, no problem, so its definitively something about LOS (because in CM13 it worked fine and I have only apps, which i already used under CM13)

Any suggestion how I could figure out whats the problem. As I am the only one with this problem, I think I have to solve the problem by myself
[Galaxy S II Android Development] gm0:
Checking the logs would be a good start (adb logcat), note the time your keys stop working and then check the log messages on and before that timestamp.
[Galaxy S II Android Development] darkRd:
Hi,

finally I succeeded to upgrade to lineage-14.1-20170226-nightly-i9100-signed.zip by first flashing lineage-14.1-20170226-experimental-i9100-signed.zip.

I swear I did the samething for more than 10 times but suprisingly latest trial worked, I dont know why :)

Now, I am trying to flash	lineage-14.1-20170307-nightly-i9100-signed.zip but it says:

"Can't install this package on the top of incompatible data. Please try another package or run a factory reset"

I do not want to wipe data. is it same for everyone? how did you upgrade to 20170307?

did you wipe your data or there were no problem for you?

another question is about TWRP.

If I use TWRP 3.0.2.0 (or 3.1.0.0, newest one) I cant not flash lineageos Roms. after swipe for flash, animation bar is displayed for a while without any increase in the bar percentage and suddenly TWRP home page is displayed without any warning or error.

I always have to go back TWRP 2.8.x.x, Which TWRP version do you use? is there any body succeeded with TWRP version > 3.x.x.x ?

Now I have different problem, I could not flash 20170307 and my device not starting now, no any boot animation and never starts. I can go into recovery mode but system reboot not working. I even dont see boot animation.

I tried to flash lineage-14.1-20170226-nightly-i9100-signed.zip and it gave to the same error "Can't install this package on the top of incompatible data".

Therefore I flashed experimental version once again, it flashed succesfully. than tried nightly 20170226 and error still continues. So what I said in the first sentence of this post gone to trash.

Very annoying.

Unofficial builds were better than official ones. I wish they continue to produce unofficial ones :)
[Galaxy S II Android Development] gm0:
[MENTION=2314916]darkRd[/MENTION] I'd say simply making a backup of your data/settings followed by a clean install and a restore of your data/settings would be the much faster solution to your problem. Or compile your own unofficial builds. Or remove the sigcheck from the official build's updater-script before flashing it.

Also I don't know what problem you're having with TWRP, I never even used a version < 3 ever, yours is ancient and not fully compatible with Android N. But you can check the recovery.log for clues as to what's wrong.
[Galaxy S II Android Development] Nobby1960:
Volume steps?

Is it possible to integrate volume steps into the sound settings like in AICP? For myself this is a helpful feature, because the default steps are too coarse, even if you want to adjust the music volume fine.
[Galaxy S II Android Development] MigoMujahid:
I don't think they would do that, Cyanogenmod has been always a features-clean project and same for LineageOS, maybe in an unofficial build :rolleyes:
[Galaxy S II Android Development] HutchGuy:
Can anyone help me please? I have a problem!!

I had CWM-KitKatCompatible-i9100 on my phone, wiped system+data and flashed experimental+nightly rom along with GAPPS but I can't seem to get root access!! When I flash it, it gives an error (0), no other special specification for me to search about.

I tried the both root packages in #1 and #4 posts but both gave the same error.

I read in one of the topic that I must have TWRP recovery in order to flash the root package (weird, because its the first time I face this) BUT now i'm stuck because for TWRP I need either HeimdallSuite (which gives an error during process) or IsoRec (I'm confused which file to download).

IsoRec thread url: https://xdaforums.com/galaxy-s2/orig-development/isorec-isolated-recovery-galaxy-s2-t3291176

Can anyone suggest me what should I do? I got a very bad headache... I'M CONFUSED.
[Galaxy S II Android Development] Nobby1960:
Flash the TWRP recovery, it's better than CWM - here you find it as a zip file. To get root access, you must flash this file.
[Galaxy S II Android Development] HutchGuy:
Hi, Thanks for giving me the TWRP recovery file, you are awesome!! But even the addonsu-arm-signed.zip which you provided gives error in TWRP!!!! Omg, I'm just 1 step away from breaking my phone... here is the error details in recovery:

Installing su addon...

Done

Updater process ended with signal: 4

Error installing zip file '/sdcard/lineage/addonsu-arm-signed.zip'

Updating partition details...

...done

:crying::crying::crying::crying:
[Galaxy S II Android Development] freecaster:
3 weeks ago, I've installed Lineage OS on my i9100, but not I noticed that the phone is slower than before the installation; I used Ccleaner to remove all caches and other rubbish. But even easy videos from Internet and with VLC-Player are played with delays or slow. How to solve the problem? When I have installed Lineage OS, I done repartition /system 1GB and the rest 7GB for data. What do you think?
[Galaxy S II Android Development] the.gangster:
[MENTION=6139217]HutchGuy[/MENTION]

don't trust that message!

That's more or less a status message being interpreted as an error. Everything is fine though.

If you boot into the ROM you can now assign the root rights to adb+apps in developer settings!
[Galaxy S II Android Development] s2l9100:
Try the attached one for root
[Galaxy S II Android Development] HutchGuy:
Yes you are right!!! Well actually I wish I could see your message sooner because I have to use my phone data (hotspot) to come and post here but after having a hard wrestling match against TWRP and Lineage, I got the stupid root access!! :D Oh man, it feels so good you have no idea.

Thanks a lot :good:

You just showed the right way, I was too noob to figure it out.

Thank you Nobby1960, the.gangster and s2l9100, you guys are amazing :highfive: XDA must be so proud to have you
[Galaxy S II Android Development] winone1208:
I use this rom

https://www.sammobile.com/firmwares/download/29852/I9100XXMS7_I9100OXAMS7_XEO/

and this app

https://play.google.com/store/apps/details?id=com.pierwiastek.gpsdata&hl=pl

I install your app and see(no fix) 4 satellites after 5 min.
[Galaxy S II Android Development] Boolian:
Check the Battery Saver & Performance Profile in Settings.

I noticed similar, but it was staying on 'Powersave' after a battery swap when I had the 'Saver feature activated'

It's actually still a good profile, especially with 'Auto Optimise' also activated, So I only noticed occassionally when the phone was under load.

Also, it would reset itself back to original 'Balanced or Performance profile' if it was on a charger next time the Battery Saver kicked in - so it was an intermittent annoyance. I've only just realised the cause recently...
[Galaxy S II Android Development] Nobby1960:
Here comes a new "power profile" to hold the CPU on 1200 MHz - the phone is noticeably faster, especially when scrolling. In next build the built-in CPU governor is modified as I read in a posted commit link here, the fallback issue to 800 MHz in performance profile if you need power is gone.

You need this modded Kernel Adiutor. Look at the changed "ondemand" values in my screenshots, tested with the latest official build from LOS. The battery consumption is not much higher.
[Galaxy S II Android Development] Boolian:
You reckon the modded Adiutor is still needed,

or is it only needed to "lock" to 1200 permanently with no idle?

I thought the OS system "Power Profile" would now properly and automatically give 1200 when called for , the commit fixed the fallback to 800 at "idle" and failure to ramp back up to 1200.

Or am I missing something?
[Galaxy S II Android Development] ale5000:
[MENTION=2222292]rINanDO[/MENTION]: Any update on this? https://xdaforums.com/showpost.php?p=71350123&postcount=641

I just ask because we are near a new build.
[Galaxy S II Android Development] liquidraver:
Hi!

This is what I'm battling with too, installed pico + a lot of apps (messenger, two mail profile, etc.)

Battery Stat apps doesn't show any apps / system apps using battery, but still 4-5%/hour, and around 2 hour wake in a 10 hour period.

"Keep wifi on during sleep" menu doesn't work, wifi is always on even if I set ti to switch off during sleep.

With wifi switched off, it's a little better, but it's a lot worse than CM13.

Even when I use it it drains battery much faster than CM13.

My profile is balanced, I don't use Power saver, because it restricts background data, and... well.. it's a smartphone, I expect it to notify me of incoming messages and emails.

I'll make a clean install every time a new nightly comes out, and test it further.
[Galaxy S II Android Development] todonormal:
Hi, Do you testing this TWRP Backup & Restore Tool ?
[Galaxy S II Android Development] dumdidum123:
Yeah, I did that.

Anyways, if bluetooth is enabled and then I restart the device, so my gt-i9100 automatically connects on boot, the bluetooth keys work.

Just an example, when I hit the Play Button a few minutes after final boot up to start Poweramp (I also did this with the built-in music player, same behavior in every step).

First log: everything is fine! see attached file gti9100working.txt

Now part 2: The failure

I detected when the problem is happening. When I have bluetooth enabled on boot, everything is fine.

If I disable bluetooth and reenable it again, it's not working anymore. Trying to capture this procress via logcat: (see attached file gti9100NOTworking.txt)

I am sorry, this is so much.

Explanation what I did, I disabled bluetooth at 15:54:50, waited and reenabled bluetooth again. At 15:55:12 my device was reconnected to the bluetooth speaker, but for now the bluetooth control keys arent working anymore. I just kept pushing the buttons after 155512 till the end of the log extract.

I will try to find out what is happening there, but my skills in android developing are quite low, so if ANYONE finds the problematic log entry, I would be pleased.
[Galaxy S II Android Development] lolloandroid:
Hi guys can you help me? So I installed lineage os 14.1. On whatsapp when I send voice messages are very low, how can I fix? Ps Also, what is the best kernel? Thank you!:o
[Galaxy S II Android Development] Nobby1960:
The next coming official build should have no more issue with the fallback to 800 MHz, if you need performance and change to the performance profile. The method with the Kernel Adiutor is just a workaround.