[ROM][LineageOS14.1][Nougat][Android 7.1.2] NightOwl 20180824

[bauner]

I guess i did wrong in the first time. Hopefully with your command lines it shoul be all there now. Tks again!

It looks all ok except that it will not detect your sim card

02-21 11:38:28.697  3080  3924 D TelephonyManager: getSimState: default sim:-1, all SIMs absent, return state as absent
02-21 11:38:28.843  3313  3558 D SubscriptionController: [getSlotId]- subId invalid
02-21 11:38:28.856  4106  4487 D TelephonyManager: getSimState: default sim:-1, all SIMs absent, return state as absent
02-21 11:38:28.920  3313  3572 D SubscriptionController: [getSlotId]- subId invalid
02-21 11:38:28.960  3080  3924 D TelephonyManager: getSimState: default sim:-1, all SIMs absent, return state as absent
02-21 11:38:29.906  3313  3572 D SubscriptionController: [getSlotId]- subId invalid
02-21 11:38:29.925  3080  3924 D TelephonyManager: getSimState: default sim:-1, all SIMs absent, return state as absent

maybe it is really the sim slot

did you also try it with another sim card?

 

[Mr.AndroidExperimental]

you can try to backup the data from both sdcards to your pc then boot into recovery and format both sdcards as (v)fat

Okay i will do that

 

[Nanda51]

It looks all ok except that it will not detect your sim card

02-21 11:38:28.697  3080  3924 D TelephonyManager: getSimState: default sim:-1, all SIMs absent, return state as absent
02-21 11:38:28.843  3313  3558 D SubscriptionController: [getSlotId]- subId invalid
02-21 11:38:28.856  4106  4487 D TelephonyManager: getSimState: default sim:-1, all SIMs absent, return state as absent
02-21 11:38:28.920  3313  3572 D SubscriptionController: [getSlotId]- subId invalid
02-21 11:38:28.960  3080  3924 D TelephonyManager: getSimState: default sim:-1, all SIMs absent, return state as absent
02-21 11:38:29.906  3313  3572 D SubscriptionController: [getSlotId]- subId invalid
02-21 11:38:29.925  3080  3924 D TelephonyManager: getSimState: default sim:-1, all SIMs absent, return state as absent

maybe it is really the sim slot

did you also try it with another sim card?

Yes... none works on it. sigh... but tks a lot for your help! I wish i can use your rom again someday! My other phone (samsung E7) doesn't have anything for it yet. You are the best, @bauner!

 

[SoulSlayer69]

Yes... none works on it. sigh... but tks a lot for your help! I wish i can use your rom again someday! My other phone (samsung E7) doesn't have anything for it yet. You are the best, @bauner!

It's sim slot for sure, just repair it, 20€ here (Italy), dunno in Brazil but it's a cheap repair for sure:good:

 

[Mr.AndroidExperimental]

I formatted them both and now i can access them without any error thx for the tip @bauner:highfive:

 

[philip_rhoades]

Getting file manager (Ghost Commander) access to /storage/sdcard?

People,

I have searched the whole of this thread but I can't see that the problem with getting access to the sdcards from the UI has been resolved / worked around? I can ssh into the running system and have no problems creating files as root but the UI can't do this?

Thanks,
Phil.

 

[wandro]

Beta 3: Toggling lockscreen on/off doesn't work correctly

If I turn the lockscreen off in the first entry of the system settings, then this first entry disappears, and so I am unable to turn it on again.

---------- Post added at 09:52 AM ---------- Previous post was at 09:47 AM ----------

Beta 3: Titanium Backup doesn't save backups.

Has TB not yet been adapted to Android 7.1.1, or is it a problem of Beta 3?

 

[bauner]

People,

I have searched the whole of this thread but I can't see that the problem with getting access to the sdcards from the UI has been resolved / worked around? I can ssh into the running system and have no problems creating files as root but the UI can't do this?

Thanks,
Phil.

It seems to have permission problems with android 7 and the problem is that you can only choose the storage access framework location 1 time then you would need to delete the app data to select the other sdcard.

The default filemanager, es file explorer and maybe many other filemanagers too should work

If I turn the lockscreen off in the first entry of the system settings, then this first entry disappears, and so I am unable to turn it on again.

---------- Post added at 09:52 AM ---------- Previous post was at 09:47 AM ----------

Beta 3: Titanium Backup doesn't save backups.

Has TB not yet been adapted to Android 7.1.1, or is it a problem of Beta 3?

You can enable the lockscreen again in settings-security-device lock
The first entry which disappears is only a hint for settings which you may want to customize after a new installation/factory reset

for me titanium backup can access the sdcard0 directly but it has no permission for the sdcard1.

You should get it working if you enter titanium backup preferences-backup folder location and then select DocumentProvider storage and select your sdcard (if you press on the 3 dot menu you can also see the sdcard0)

 

[philip_rhoades]

bauner,

It seems to have permission problems with android 7 and the problem is that you can only choose the storage access framework location 1 time then you would need to delete the app data to select the other sdcard.

The default filemanager, es file explorer and maybe many other filemanagers too should work

I didn't really understand the first paragraph - I knew there were problems with newer versions of Android and sdcards - but I just installed ES FM and then everything magically became accessible - including through Ghost Commander!

Thanks!

 

[bauner]

bauner,



I didn't really understand the first paragraph - I knew there were problems with newer versions of Android and sdcards - but I just installed ES FM and then everything magically became accessible - including through Ghost Commander!

Thanks!

Android have storage access framework to access external storage.
With this you can access the sdcard0, sdcard1 and otg devices.
You also have the option to use the storage access framework in ghost commander.
But if you select it it asks you which sdcard you want to use.
After this you will come directly to the selected sdcard and I did not find an option in ghost commander to change it to the other sdcard without deleting the ghost commander app data in settings-apps-ghost commander

But you are right after opening the es file manager I also can access both sdcars with ghost commander. But I have only write acces to sdcard0

 

[bauner]

While using WhatsApp video call the display shows blue color

It will work in the next version @rINanDO has fixed the problem.

 

[philip_rhoades]

Android have storage access framework to access external storage.
With this you can access the sdcard0, sdcard1 and otg devices.
You also have the option to use the storage access framework in ghost commander.
But if you select it it asks you which sdcard you want to use.
After this you will come directly to the selected sdcard and I did not find an option in ghost commander to change it to the other sdcard without deleting the ghost commander app data in settings-apps-ghost commander

OK, I get it now - thanks1

But you are right after opening the es file manager I also can access both sdcars with ghost commander. But I have only write acces to sdcard0

Ah, yes . . you are correct - I can read sdcard1 but not save files to it with my Ted text editor . .

 

[dvadvadva]

I´m on beta 3.
What is the best way to go back to stock ROM (JB 4.1.2.)?
I did a nandroid backup of the stock ROM when I started my adventure with custom ROMS.
Tnx

 

[tamaraxxx]

It will work in the next version @rINanDO has fixed the problem.

Will this also work on your cm13?
When you create the next update?

 

[bauner]

I´m on beta 3.
What is the best way to go back to stock ROM (JB 4.1.2.)?
I did a nandroid backup of the stock ROM when I started my adventure with custom ROMS.
Tnx

then you should only need to restore your nandroid backup

Will this also work on your cm13?
When you create the next update?

Yes it should also work in the next lineage 13 rom.

Because of a lineageos 14.1 code rebase (http://lineageos.org/Last-Week-in-LineageOS-2/) there was an delay in merging the february security patches.

Now they are merged into 14.1.
I will make a new 14.1 rom in the next days.
After the new 14.1 rom is finish I will start the work on the next 13 rom

 

[wandro]

Lock screen: How to correctly unlock by a swipe gesture

NightOwl Beta 3 on N7000: I have big problems unlocking the lock screen by swiping from bottom to top. In most cases it succeeds only after several attempts. Launching the camera app from the lock screen by swiping: same effect.

On my LG G4 and Nexus 7 (2012) I don't have such difficulties.

UPDATE:
The problem seems to occur only if the device is plugged to the charger.

 

[daedric]

NightOwl Beta 3 on N7000: I have big problems unlocking the lock screen by swiping from bottom to top. In most cases it succeeds only after several attempts. Launching the camera app from the lock screen by swiping: same effect.

On my LG G4 and Nexus 7 (2012) I don't have such difficulties.

UPDATE:
The problem seems to occur only if the device is plugged to the charger.

Try this:

put one bare foot , without sock, on the floor.
If the touch screen problem goes away, you have bad earthing in your house.

 

[shyvanna]

LineageOS14.1 Beta 3: Issues im having so far:

- Greenify with aggressive doze setting hard resets the phone

- Due to the hard resets, /storage/sdcard0 got renamed to /storage/M-^IPNG^M^J^Z^J
- issue got fixed somehow though after a few reboots

 

[bauner]

LineageOS14.1 Beta 3: Issues im having so far:

- Greenify with aggressive doze setting hard resets the phone

- Due to the hard resets, /storage/sdcard0 got renamed to /storage/M-^IPNG^M^J^Z^J
- issue got fixed somehow though after a few reboots

If you can reproduce it please send me a logcat of it.
And after the reboot please post also the file /proc/last_kmsg

 

[wandro]

Try this:

put one bare foot , without sock, on the floor.
If the touch screen problem goes away, you have bad earthing in your house.

Many thanks, but the bare foot trick didn't help.

And: I don't have the problem on my LG G4 and on my Nexus 7 (2012), nor did I observe it on many former ROMs that I had installed on my N7000 before migrating to NightOwl 14.1.