FORUMS
Remove All Ads from XDA

[ROM][I9100][OFFICIAL][7.1.2] LineageOS 14.1

439 posts
Thanks Meter: 3,246
 
By rINanDO, Senior Member on 13th February 2017, 02:04 PM
Post Reply Email Thread
27th February 2017, 10:46 AM |#501  
MigoMujahid's Avatar
Senior Member
Flag New York
Thanks Meter: 709
 
Donate to Me
More
Quote:
Originally Posted by BrightCGN

Hello,

I'm new to this rom.
I've installed a fresh lineage-14.1-20170226-nightly-i9100-signed.zip.
Also installed SuperSU v2.79 SR3.

But I got no ROOT access.

Did i make something wrong?

You can't use supersu, you have to flash the correct su-addon from LineageOS official site instead.

---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------

Quote:
Originally Posted by Pier_89

Is it possibile to select as internal storage an external SD card in LineageOS 14.1 for our device?
Are there issues doing that in this official rom?

Their should be a way to format the external sdcard as internal storage from storage settings.
 
 
27th February 2017, 11:52 AM |#502  
Junior Member
Flag Köln
Thanks Meter: 3
 
More
Quote:
Originally Posted by MigoMujahid

You can't use supersu, you have to flash the correct su-addon from LineageOS official site instead.

---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------

Yes.
I reinstall the ROM and also addonsu-arm64-signed.zip.
I could enable Root for ADB and Apps under developer-settings, but root-management access stays greyed.
Also ClockSync and FasterGPS tell me, that they can grant root-access.
27th February 2017, 12:11 PM |#503  
Senior Member
Flag Madrid
Thanks Meter: 89
 
More
Hi. What partitions can format with f2fs? Thanks for advanced. How?
27th February 2017, 12:17 PM |#504  
Senior Member
Thanks Meter: 506
 
More
Quote:
Originally Posted by BrightCGN

Yes.
I reinstall the ROM and also addonsu-arm64-signed.zip.
I could enable Root for ADB and Apps under developer-settings, but root-management access stays greyed.
Also ClockSync and FasterGPS tell me, that they can grant root-access.

is i9100 64bit ? NO !
27th February 2017, 12:29 PM |#505  
Senior Member
Flag Erfurt
Thanks Meter: 54
 
More
Quote:
Originally Posted by BrightCGN

Yes.
I reinstall the ROM and also addonsu-arm64-signed.zip.
I could enable Root for ADB and Apps under developer-settings, but root-management access stays greyed.
Also ClockSync and FasterGPS tell me, that they can grant root-access.

See post #4 for a working su version.
Then you must enable developer options and enable su for apps.

---------- Post added at 01:29 PM ---------- Previous post was at 01:26 PM ----------

Quote:
Originally Posted by todonormal

Hi. What partitions can format with f2fs? Thanks for advanced. How?

It makes only sense for data partitionin.
The Following User Says Thank You to kraehetest For This Useful Post: [ View ] Gift kraehetest Ad-Free
27th February 2017, 12:38 PM |#506  
Junior Member
Flag Köln
Thanks Meter: 3
 
More
Quote:
Originally Posted by pix106

is i9100 64bit ? NO !

Quote:
Originally Posted by kraehetest

See post #4 for a working su version.
Then you must enable developer options and enable su for apps.

---------- Post added at 01:29 PM ---------- Previous post was at 01:26 PM ----------


It makes only sense for data partitionin.

That do the trick.
It have to use the modified zip from #4.
Thanks for the help
27th February 2017, 01:05 PM |#507  
Nobby1960's Avatar
Senior Member
Flag Freiburg
Thanks Meter: 365
 
More
Quote:
Originally Posted by kraehetest

If you are on emulated storage, you must change the storage.xml again. (Every time you update lineage os) I’m lazy, so I created a flashable zip file with the changed storage.xml.
Yesterday i update from Feb. 22 to Feb. 26, and everything is running fine.

Exactly, the storage.xml was the problem. I thougt I'm going mad here

---------- Post added at 02:05 PM ---------- Previous post was at 01:58 PM ----------

Quote:
Originally Posted by treysis

btw.: what is emulated storage?

It's a tricky thing Read more about here
The Following User Says Thank You to Nobby1960 For This Useful Post: [ View ] Gift Nobby1960 Ad-Free
27th February 2017, 01:43 PM |#508  
Junior Member
Flag Thuringia
Thanks Meter: 7
 
More
Quote:
Originally Posted by Nobby1960

Exactly, the storage.xml was the problem. I thougt I'm going mad here

That's interesting... was the flag primaryStorageUuid="primary_physical" set again or was something else wrong with your storage.xml?
I really wonder why the update just worked for me while it reverted/ messed up your storage.xml file...
27th February 2017, 01:44 PM |#509  
Senior Member
Flag Erfurt
Thanks Meter: 54
 
More
Quote:
Originally Posted by Nobby1960

Exactly, the storage.xml was the problem. I thougt I'm going mad here [COLOR="Silver"]

@Nobby1960, do you use an emu recovery?
27th February 2017, 02:03 PM |#510  
Member
Flag London
Thanks Meter: 55
 
More
Hi all.

Firstly, a big "thank you" to the devs for keeping my old i9100 running with the latest version of android. I have a couple of spare i9100 phones so I've been playing around installing lineage-14.1-20170222-nightly-i9100-signed.zip and lineage-14.1-20170226-nightly-i9100-signed.zip. A few things to mention...

I've read (in a couple of places) that you need to be running twrp v3 or later to install LOS. My experience is that this is *not* true. My (clean) install procedure (including a *full* wipe) is:

1) Odin back to stock 4.1.2 *with* a stock repit at the same time to make sure that I have a known-good starting point,
2) Boot into stock recovery and flash stock_kernel_twrp_1020-signed.zip from the microsd,
3) Reboot into twrp v2.8.7.0 recovery and flash the lanchon-repit to get a 1GB system partition,
4) "Advanced wipe" Dalvik Cache, Cache, System, Data, eMMC and "Android Secure",
5) Flash the latest nightly LOS and OpenGapps.

This procedure has worked successfully every time that I've tried it, and it does NOT use any TWRP v3.

I also have a bug to report: if I try to "set-up" ("erase & format) a blank (zero'ed-out) microsd card as "portable storage", then I get a toast saying

"command 'nn volume partition disk:179_12 public' failed with '400 11 Command failed'"

Here's the logcat for the error:

Code:
02-27 12:21:28.469  2304  2316 I ActivityManager: START u0 {cmp=com.android.settings/.deviceinfo.StorageWizardFormatProgress (has extras)} from uid 1000 on display 0
02-27 12:21:28.476  1977  2071 D Yamaha-MC1N2-Audio: yamaha_mc1n2_audio_output_start()
02-27 12:21:28.476  1977  2071 D Yamaha-MC1N2-Audio: yamaha_mc1n2_audio_route_start()
02-27 12:21:28.476  1977  2071 D Yamaha-MC1N2-Audio: (yamaha_mc1n2_audio_params_route_find): device = 2, direction = 0
02-27 12:21:28.720  2304  2735 D VoldConnector: SND -> {11 volume partition disk:179_12 public}
02-27 12:21:28.727  1902  1953 V vold    : /system/bin/sgdisk
02-27 12:21:28.727  1902  1953 V vold    :     --android-dump
02-27 12:21:28.727  1902  1953 V vold    :     /dev/block/vold/disk:179_12
02-27 12:21:28.796  1902  1953 E vold    : Failed to pclose /system/bin/sgdisk --android-dump /dev/block/vold/disk:179_12 : No such file or directory
02-27 12:21:28.796  1902  1953 W vold    : sgdisk failed to scan /dev/block/vold/disk:179_12
02-27 12:21:28.796  2304  2419 D VoldConnector: RCV <- {400 11 Command failed}
02-27 12:21:29.143  2701  2701 E StorageSettings: Failed to partition
02-27 12:21:29.143  2701  2701 E StorageSettings: java.lang.IllegalStateException: command '11 volume partition disk:179_12 public' failed with '400 11 Command failed'
02-27 12:21:29.143  2701  2701 E StorageSettings:       at android.os.Parcel.readException(Parcel.java:1692)
02-27 12:21:29.143  2701  2701 E StorageSettings:       at android.os.Parcel.readException(Parcel.java:1637)
02-27 12:21:29.143  2701  2701 E StorageSettings:       at android.os.storage.IMountService$Stub$Proxy.partitionPublic(IMountService.java:1070)
02-27 12:21:29.143  2701  2701 E StorageSettings:       at android.os.storage.StorageManager.partitionPublic(StorageManager.java:742)
02-27 12:21:29.143  2701  2701 E StorageSettings:       at com.android.settings.deviceinfo.StorageWizardFormatProgress$PartitionTask.doInBackground(StorageWizardFormatProgress.java:116)
02-27 12:21:29.143  2701  2701 E StorageSettings:       at com.android.settings.deviceinfo.StorageWizardFormatProgress$PartitionTask.doInBackground(StorageWizardFormatProgress.java:92)
02-27 12:21:29.143  2701  2701 E StorageSettings:       at android.os.AsyncTask$2.call(AsyncTask.java:305)
02-27 12:21:29.143  2701  2701 E StorageSettings:       at java.util.concurrent.FutureTask.run(FutureTask.java:237)
02-27 12:21:29.143  2701  2701 E StorageSettings:       at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:243)
02-27 12:21:29.143  2701  2701 E StorageSettings:       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
02-27 12:21:29.143  2701  2701 E StorageSettings:       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
02-27 12:21:29.143  2701  2701 E StorageSettings:       at java.lang.Thread.run(Thread.java:761)
02-27 12:21:29.166  2304  2316 W ActivityManager: Duplicate finish request for ActivityRecord{2a149ee u0 com.android.settings/.deviceinfo.StorageWizardFormatConfirm t3 f}
02-27 12:21:29.344  2304  3071 I WindowManager: Failed to capture screenshot of Token{596d97f ActivityRecord{96a0a9e u0 com.android.settings/.deviceinfo.StorageWizardFormatProgress t3 f}} appWin=Window{6498e9b u0 com.android.settings/com.android.settings.devi$
02-27 12:21:29.961  3086  3187 W OpenGLRenderer: Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
02-27 12:21:29.961  3086  3187 W OpenGLRenderer: Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
02-27 12:21:31.574  1977  2071 D Yamaha-MC1N2-Audio: yamaha_mc1n2_audio_output_stop()
02-27 12:21:31.575  1977  2071 D Yamaha-MC1N2-Audio: yamaha_mc1n2_audio_route_start()
02-27 12:21:32.716  2304  2304 W WindowManager: Attempted to remove non-existing token: [email protected]
I'm sure this bug will be fixed soon - I'm just letting people know.

I'm also slightly confused as to why we still have two xda threads for this rom - there appears to be more posting about LOS in the old cm14.1 thread than in this thread.

Thanks again to everyone who's put time and effort into this project - this ROM is easily the most stable ROM I've ever run on my i9100 phones.

Jaime
The Following 2 Users Say Thank You to jt12345 For This Useful Post: [ View ] Gift jt12345 Ad-Free
27th February 2017, 02:59 PM |#511  
Junior Member
Thanks Meter: 0
 
More
Can someone tell me if the battery life is good in Los comparing to crdroid RR rom
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes