Amazing, thank you @bauner. I'm currently running 14.1 and will try this soon to look for bugs and report them. I really appreciate your work with this device. 
[ROM][LineageOS15.1][Oreo][Android 8.1.0] NightOwl Beta3
- Thread starter bauner
- Start date
why the internal share storage is happen? after i install a few apps ,the internal share storage decrease .i already cannot install app because the internal share storage is full.
Hi. Have you tried repatitioning your device? I guess maybe you havent.
Since Lollipop android changed from Dalvik to art so our devices needs more storage---------- Post added at 03:12 PM ---------- Previous post was at 03:08 PM ----------
NOTE:
Because of the ART runtime since Android 5 all Apps will need more space. If you want to install more Apps you should think about repartitioning your internal storage.
You can find a repartition howto in the Howto Install section.
Howto Repartition your device to get more space for apps:
Lanchon has made a tool to make it possible to repartition your device in the recovery after you have installed the rom without loosing your data
Hello Bauner
i noticed that sometimes my contacts disappear suddenly
i don't know why but wanted to let you know about this
* luckily i have a backup
Peace ! ??
i noticed that sometimes my contacts disappear suddenly
i don't know why but wanted to let you know about this
* luckily i have a backup
Peace ! ??
I tried it but I cannot install apks in it. Is it actually possible and more importantly advisable to install F-Droid using adb and a USB cable? Other than that it feels quite fluid and not counting the screen rotation/animation glitches I've found no other issues.
impressions
I played with it a bit after using the lanchon script to repartition (3G system, 10G data, 1G "internal sdcard") and switching storage.xml to use the /data/media scheme.
I set low_ram set to false in buildprops, which uses an extra 100-150MB directly after bootup. I installed everything I normally use for my normal phone use (incl. tasker, titanium backup, k9 and a bit more; open_gapps pico, with google maps, gboard+its handwriting extensions, and also google itself, which is required for speech recognition in gboard).
Things feel ok, but slower than before with upto 100MB used in zram/swap and about 150-250M cached. When more apps are used and zram use increases to >= 140M (still about 200M cached), things get sluggish.
With some tune (not starting apps, reducing background use, maybe swappiness) it's surprisingly stable. zram size could be reduced a bit I think.
It misbehaved only when I tried a more complete open_gapps packages (which easily fit in /system+/data thanx to lanchon): the ram increased to much for sane working.
@bauner, so this is a very nice work and has promise for our N7000.
But there's SHOW STOPPER FOR ME which I only noticed fairly late:
For me, in-app payments seem impossible: settings and apps cannot see IMEI and android ID.
Wifi with H+ and making voice calls is possible. The problem is purely on the android side, this doesn't seem to be the normal LOST_IMEI issue.
As I wish to use boldbeast call recorder (root + alsa) to record calls, and now cannot upgrade to the paid version,
Details on the IMEI issue see next mail. OR NOT - see below..
---------- Post added at 12:52 PM ---------- Previous post was at 12:19 PM ----------
===============
attempt 1:
gingerbread custom rom (abyssnote) directly as per initial post to N7000ZSLR1_N7000OZSLR1_BRI using heimdall. I didn't boot this, but remainded in the recovery (updated with the los13 kernel) and flashed the NightOwl 15.1 zip and pico gapps. Boot up. Lanchon. And this is what I used for the report above.
I only noticed the missing IMEI and android ID very late in the game, as I could make calls and even install my paid titanium backup key without any issues.
Attempts to restore things from backup failed regardless of restoring the partition or just the reboot/copy back imei and nv_data.
ok. FAIL.
attempt 2:
I went back to 2.3.6 and upgraded to N7000XXLTA_N7000BOLT1_N7000DTMLT5 (also 4.1, but in contrast to BRI this lacks PARAM and SBL1 firmware, but it might have been a better fit to my original NOTE firmware, as both are German versions and I use T-mobile). Boot up. IMEI ok.
Onward to CM11 as per @bauner instruction (thanx for keeping the old roms available!). Boot up. IMEI ok.
Onward to CM12. By now I was a bit annoyed and dropped heimdall and just used adb and dd for restoring and backups, and CWM for flashing the zips.
Onward to Nightowl/LOS13.
Onward to Nightowl/LOS14. As usual per @bauner instructions in his LOS14 thread. IMEI is still visible. Might be my choice If we cannot fix my IMEI issue with NightOwl 15.
Onward to Nightowl/LOS15 Nightowl-lineage15.1-go-alpha2-n7000.zip however reliably FAILS:
- I can make calls, and use H+ with the usual data rates of 7.5/1.5Mbit
- settings -> phone -> ... doesn't list android id and neither IMEI
- however in a rooted adb shell, I still see an android_id: settings list secure | grep -i android_id
- apps like boldbeast call recorder cannot see the IMEI (which is required for the apps in-app-paid upgrade, but is now refused "IMEI is not right").
- choice of privacy guard doesn't seem to matter
This doesn't look like the normal LOST IMEI problem, which seems to normally disallow SIM use.
It's more as if the userspace can no longer parse settings.
/efs is absolutely (perms and md5) excluding nv_data.bin / nv_data.bin.md5. Adding chmod ugo+r . nv* and killing/restarting zygote doesn't change anything.
ok. FAIL.
@bauner: can you have a look what exactly differs between your Nightowls 14 wrt 15. And what else I might try?
@bauner: and a special thanx for maintaining and updating your N7000 roms - the only live ones for the N7000!
thanx
Peter
I played with it a bit after using the lanchon script to repartition (3G system, 10G data, 1G "internal sdcard") and switching storage.xml to use the /data/media scheme.
I set low_ram set to false in buildprops, which uses an extra 100-150MB directly after bootup. I installed everything I normally use for my normal phone use (incl. tasker, titanium backup, k9 and a bit more; open_gapps pico, with google maps, gboard+its handwriting extensions, and also google itself, which is required for speech recognition in gboard).
Things feel ok, but slower than before with upto 100MB used in zram/swap and about 150-250M cached. When more apps are used and zram use increases to >= 140M (still about 200M cached), things get sluggish.
With some tune (not starting apps, reducing background use, maybe swappiness) it's surprisingly stable. zram size could be reduced a bit I think.
It misbehaved only when I tried a more complete open_gapps packages (which easily fit in /system+/data thanx to lanchon): the ram increased to much for sane working.
@bauner, so this is a very nice work and has promise for our N7000.
But there's SHOW STOPPER FOR ME which I only noticed fairly late:
For me, in-app payments seem impossible: settings and apps cannot see IMEI and android ID.
Wifi with H+ and making voice calls is possible. The problem is purely on the android side, this doesn't seem to be the normal LOST_IMEI issue.
As I wish to use boldbeast call recorder (root + alsa) to record calls, and now cannot upgrade to the paid version,
Details on the IMEI issue see next mail. OR NOT - see below..
---------- Post added at 12:52 PM ---------- Previous post was at 12:19 PM ----------
===============
attempt 1:
gingerbread custom rom (abyssnote) directly as per initial post to N7000ZSLR1_N7000OZSLR1_BRI using heimdall. I didn't boot this, but remainded in the recovery (updated with the los13 kernel) and flashed the NightOwl 15.1 zip and pico gapps. Boot up. Lanchon. And this is what I used for the report above.
I only noticed the missing IMEI and android ID very late in the game, as I could make calls and even install my paid titanium backup key without any issues.
Attempts to restore things from backup failed regardless of restoring the partition or just the reboot/copy back imei and nv_data.
ok. FAIL.
attempt 2:
I went back to 2.3.6 and upgraded to N7000XXLTA_N7000BOLT1_N7000DTMLT5 (also 4.1, but in contrast to BRI this lacks PARAM and SBL1 firmware, but it might have been a better fit to my original NOTE firmware, as both are German versions and I use T-mobile). Boot up. IMEI ok.
Onward to CM11 as per @bauner instruction (thanx for keeping the old roms available!). Boot up. IMEI ok.
Onward to CM12. By now I was a bit annoyed and dropped heimdall and just used adb and dd for restoring and backups, and CWM for flashing the zips.
Onward to Nightowl/LOS13.
Onward to Nightowl/LOS14. As usual per @bauner instructions in his LOS14 thread. IMEI is still visible. Might be my choice If we cannot fix my IMEI issue with NightOwl 15.
Onward to Nightowl/LOS15 Nightowl-lineage15.1-go-alpha2-n7000.zip however reliably FAILS:
- I can make calls, and use H+ with the usual data rates of 7.5/1.5Mbit
- settings -> phone -> ... doesn't list android id and neither IMEI
- however in a rooted adb shell, I still see an android_id: settings list secure | grep -i android_id
- apps like boldbeast call recorder cannot see the IMEI (which is required for the apps in-app-paid upgrade, but is now refused "IMEI is not right").
- choice of privacy guard doesn't seem to matter
This doesn't look like the normal LOST IMEI problem, which seems to normally disallow SIM use.
It's more as if the userspace can no longer parse settings.
/efs is absolutely (perms and md5) excluding nv_data.bin / nv_data.bin.md5. Adding chmod ugo+r . nv* and killing/restarting zygote doesn't change anything.
ok. FAIL.
@bauner: can you have a look what exactly differs between your Nightowls 14 wrt 15. And what else I might try?
@bauner: and a special thanx for maintaining and updating your N7000 roms - the only live ones for the N7000!
thanx
Peter
Last edited:
Code:
adb install path_to_apkThe imei problem should be fixed in the next version
Been busy the last few days, can't wait to flash the new version.
Thank you so much for keeping this device alive @bauner.
Beta1 Rom is finish
Changes:
* Updated los sources
* June security patches
* Fixed screen glitches
* Default Android build (No GO configuration)
* Lowered zRam to 100MB
* Fixed IMEI
* Power profiles working
Because of a bigger rom size please read the updated installation/repartition parts in the first post
Changes:
* Updated los sources
* June security patches
* Fixed screen glitches
* Default Android build (No GO configuration)
* Lowered zRam to 100MB
* Fixed IMEI
* Power profiles working
Because of a bigger rom size please read the updated installation/repartition parts in the first post
after a dirty flash the ROM keeps rebooting (after about minute since the ROM boots and i unlock the screen )
tried to do factory reset or clean install but even the recover restarts while resting.
*i will try later to flash stock ROM and then flash this update (i have another phone)
Thanks Bauner for the GREAT work!
The rom rebooted for me too, few seconds after start.
After 5 or 6 reboots it now works and doesn't reboot. Sixth time I have booted it up on charger which might be the reason why it now works, but I doubt it.
Using it without system resize and without gapps.
After 5 or 6 reboots it now works and doesn't reboot. Sixth time I have booted it up on charger which might be the reason why it now works, but I doubt it.
Using it without system resize and without gapps.
after 3-4 boots i turned the phone off , after i saw your comment i turned it on and after 2 reboots its OK and without the charger.
So the solution is 6 reboots -that's funny??-
* my phone is repartitioned and gapps are installed*
Repartition again?
I already did the repartition on my device. Do I have to do it again?
I'm on Alpha2 with philz recovery.
I already did the repartition on my device. Do I have to do it again?
I'm on Alpha2 with philz recovery.
If you have installed gapps and you did not use the current repartitioning zip file you will get problems. The older repartitioning files did only enlarge the /data partiton and not the needed enlargement of the /system partition with gapps installed
So I should be fine if I follow all the steps for 'Updating If you are running an earlier NightOwl cm15.1 alpha version:'?
If you have installed gapps you need to follow the suggested install steps
/tmp
Please erase this post, I had a question, but it is solved now.
Please erase this post, I had a question, but it is solved now.
Last edited:
Hello everybody. I use cm14 nightowl, my phone is partitioned 8gb for /data and ~5gb for sdcard0. How can I better install the new cm15 version?
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone