AOSP - Android Nougat - 7.1.2 - NZH54D
This is a pure build of AOSP Android 7.1 Nougat, the goal is to have a pure AOSP rom for Samsung T705, so it is not the objective of this project to include any functionality that is not native to Android AOSP.
Download:
ROM: Mega, AndroidFileHost
Modem(OJ1): Mega, AndroidFileHost
Gapps:
OpenGapps: http://opengapps.org/
Choose ARM platform
Root:
SuperSU: http://www.supersu.com/download
Credits:
Kernel is based on LineageOS's Exynos5420 kernel, device tree is based on @Schischu, @deadman96385 and his Exynos5420 team's marvelous works.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Code:
2017-09-12
- Latest AOSP (NZH54D) Android 7.1.2_r33
- Screen rotating glitches fixed
- New Bluetooth HAL, distortion fixed
- Rework RIL, more stable phone calling and receiving
- IR blaster fixed with new IR HAL
- This might well be the last Nougat release, I will work on Oreo from now on
2017-06-19
- Latest AOSP (NJH47B) Android 7.1.2_r17
- Some kernel tweaks
2017-06-14
- AOSP (N2G47O) Android 7.1.2_r8
- Kernel 3.4.113
- Baseband version OJ1 (see download link above for modem file)
- Fingerprint disabled, everything else work, [B]including mobile data[/B]
Flashing instructions:
Flash TWRP 3.0.2 or higher
Reboot into recovery. Go into wipe menu. Select "Advanced Wipe". Check
Dalvik Cache
System
Cache
Data
and wipe them. Don't reboot just yet.
Go into install menu
Select and flash rom file aosp-XXX.zip
Select and flash SM-T705_OJ1_MODEM.zip if needed. You might need to change the file name to modem.zip
Wipe cache/dalvik cache and reboot to system. Due to some bugs, we can't flash opengapps alone with this rom
After the successful first boot, boot back into recovery and flash gapps and supersu.
Reboot to system
Contributors:
@scubajeff
Source Code: https://github.com/scubajeff/
ROM OS Version: 7.1.2 Nougat NZH54D
ROM Kernel: Linux 3.4.113
Based On: AOSP
Status: Stable
Created: 2017-06-14
Last Updated: 2017-09-12
Reserved.
UI Screenshot please
Waaaaww.. Another klimtlte AOSP.. Really amazing works.. Could you give us partial screnshoot please..
And do you have a plan to continue to maintain this build..?
Thankssss in advance :good::good:
maz izaackovich said:
Waaaaww.. Another klimtlte AOSP.. Really amazing works.. Could you give us partial screnshoot please..
And do you have a plan to continue to maintain this build..?
Thankssss in advance :good::good:
Click to expand...
Click to collapse
Of course I will maintain this build and I'm planing for a Android O update in the near future.
scubajeff said:
Of course I will maintain this build and I'm planing for a Android O update in the near future.
Click to expand...
Click to collapse
Nice..!! Android O . Glad to see another dev like you maintain this AOSP, since schisu and maloshasa has stopped their project, in AOSP based on MM os. Downloading now, I'll report back if there's some bug..
Currently using latest RR Nougat
Thankssss sir..
___________________________________________________________________
hy sir.. come again to report some issues
1. there's glitches in every opening apps or recent apps, ie. : i opened browser and then i opened COC or others, so i found there was glitches between switching that apps, and nearly happened in every swtching or opening apps ( i guess this aint my screen problem, never have been happened before)
2. ext sdcard issue: when i copied file from internal sdcard to external sdcard, i couldnt access my copied file immediately via my laptop, it must be unmounted fisrt (ext sdcard) then mounted back to make it accessible.
3. in owner user setting: i got my picture placing upside down than it supposed to be.
over all it works smooth and light. i hope i dont bother you with my issues report
thaannnnkkss..
Sorry, I'm english short.
When I'm calling with bluetooth, voice distorted. Please fix this problem. Thank you.
Ssanmai man said:
Sorry, I'm english short.
When I'm calling with bluetooth, voice distorted. Please fix this problem. Thank you.
Click to expand...
Click to collapse
Distortion happen on your side or the other side can't hear your voice clear enough?
Sent from my Samsung SM-T705 using XDA Labs
maz izaackovich said:
Nice..!! Android O . Glad to see another dev like you maintain this AOSP, since schisu and maloshasa has stopped their project, in AOSP based on MM os. Downloading now, I'll report back if there's some bug..
Currently using latest RR Nougat
Thankssss sir..
___________________________________________________________________
hy sir.. come again to report some issues
1. there's glitches in every opening apps or recent apps, ie. : i opened browser and then i opened COC or others, so i found there was glitches between switching that apps, and nearly happened in every swtching or opening apps ( i guess this aint my screen problem, never have been happened before)
2. ext sdcard issue: when i copied file from internal sdcard to external sdcard, i couldnt access my copied file immediately via my laptop, it must be unmounted fisrt (ext sdcard) then mounted back to make it accessible.
3. in owner user setting: i got my picture placing upside down than it supposed to be.
over all it works smooth and light. i hope i dont bother you with my issues report
thaannnnkkss..
Click to expand...
Click to collapse
1. I have glitches when rotating the screen, but never see them when switching apps, even when using double tapping of recent app button to fast switch between 2 most recent apps.
2. I will look into this one, however could you kindly be more elaborate that during all those steps, was your t705 mounted to you laptop thru. MTP ?
3. I could not reproduct this one neither, my avatar in owner profile now is clearly showing that the nose is below the eyes.
Thx for reporting. Keep them coming.
Sent from my Samsung SM-T705 using XDA Labs
scubajeff said:
1. I have glitches when rotating the screen, but never see them when switching apps, even when using double tapping of recent app button to fast switch between 2 most recent apps.
2. I will look into this one, however could you kindly be more elaborate that during all those steps, was your t705 mounted to you laptop thru. MTP ?
3. I could not reproduct this one neither, my avatar in owner profile now is clearly showing that the nose is below the eyes.
Thx for reporting. Keep them coming.
Sent from my Samsung SM-T705 using XDA Labs
Click to expand...
Click to collapse
1 yes.. . Glitches in opening apps, and rotating it.
2. Yah, thru MTP. I can't see my file, but ext sdcard is accesible thru my laptop, but not a copied file. When i look for it into "file explorer" in my tablet, it's there. So I have to unmount-remount my ext sdcard, and even worst i have to restart my tablet then i plug in back thru my laptop to get "my copied file" accessible..
Thaannkksss...
maz izaackovich said:
1 yes.. . Glitches in opening apps, and rotating it.
2. Yah, thru MTP. I can't see my file, but ext sdcard is accesible thru my laptop, but not a copied file. When i look for it into "file explorer" in my tablet, it's there. So I have to unmount-remount my ext sdcard, and even worst i have to restart my tablet then i plug in back thru my laptop to get "my copied file" accessible..
Thaannkksss...
Click to expand...
Click to collapse
Do you mean that the list of file is not refreshed on the laptop side?
Sent from my Samsung SM-T705 using XDA Labs
scubajeff said:
Do you mean that the list of file is not refreshed on the laptop side?
Sent from my Samsung SM-T705 using XDA Labs
Click to expand...
Click to collapse
Yeessss.. Thats right.. Sorry for my bad english
maz izaackovich said:
2. ext sdcard issue: when i copied file from internal sdcard to external sdcard, i couldnt access my copied file immediately via my laptop, it must be unmounted fisrt (ext sdcard) then mounted back to make it accessible.
Click to expand...
Click to collapse
I can reproduct this one, seems to me it's an long overdue bug of Google's implementation of MTP, related to media rescan. It happened under many circumstances, see this bug report --> https://issuetracker.google.com/issues/37071807
Sadly, Google refuse to acknowledge it as a bug.
Hi Scubajeff
I am experiencing an issue with com.android.phone and android.process.acore keeps failing to respond and its having a detremental effect on the battery life.
Any ideas how to fix this ?
ypmud said:
Hi Scubajeff
I am experiencing an issue with com.android.phone and android.process.acore keeps failing to respond and its having a detremental effect on the battery life.
Any ideas how to fix this ?
Click to expand...
Click to collapse
I ever had that issue, when i unisntalled google stock contact "Contacts.apk and ContactsProvider.apk" to replace with "zenui dialer and contact"
I guessed your issue it's related with, that your stock contact isnt installed properly
Try to flash these two .apks (Contacts.apk and ContactsProvider.apk) taken from your rom thru trwp or cwm recovery . It's solved my problem.
is there a way i can disable both phone and contacts ?
I am not on a rooted device
---------- Post added at 07:20 PM ---------- Previous post was at 06:49 PM ----------
Its ok I have figured it out that I needed to wipe the device due to it using my previous apk's
ypmud said:
---------- Post added at 07:20 PM ---------- Previous post was at 06:49 PM ----------
Its ok I have figured it out that I needed to wipe the device due to it using my previous apk's
Click to expand...
Click to collapse
Yes, if you are coming from other ROM, it's really, truly, absolutely important to WIPE ALL before flashing.
scubajeff said:
Distortion happen on your side or the other side can't hear your voice clear enough?
Click to expand...
Click to collapse
First, I confirm that my side distorted.
So far not bad. Both my 3G and LTE data are working fine, not sure about calls yet as I haven't tried. I do get those weird artifacts when I rotate the screen, but I've seen that on most of the Nougat 7.1 based ROMs. Nice work with the Kernel. It seems to be VERY customisable in Deathly Adiutor which is great for me. As with all Nougat based ROMs, the audio input latency is the best it's ever been. I would like the ability to enable software keys and to be able to bypass the hardware keys because as you most certainly know they have a strong tendency to interfere with this device (I keep catching them with my hand). Also, the IR blaster doesn't work AT ALL. I would like that to be fixed as Peel Smart Remote is an everyday app for me and I can't use it with this ROM.
simonjonnemeth said:
So far not bad. Both my 3G and LTE data are working fine, not sure about calls yet as I haven't tried. I do get those weird artifacts when I rotate the screen, but I've seen that on most of the Nougat 7.1 based ROMs. Nice work with the Kernel. It seems to be VERY customisable in Deathly Adiutor which is great for me. As with all Nougat based ROMs, the audio input latency is the best it's ever been. I would like the ability to enable software keys and to be able to bypass the hardware keys because as you most certainly know they have a strong tendency to interfere with this device (I keep catching them with my hand). Also, the IR blaster doesn't work AT ALL. I would like that to be fixed as Peel Smart Remote is an everyday app for me and I can't use it with this ROM.
Click to expand...
Click to collapse
I have to admitted that I didn't test the IR at all. Will give it a run asap. Sorry.
Sent from my Samsung SM-T705 using XDA Labs
I can now say I can only just make a phone call with this ROM. It's echoey and almost unmanageable when it does work, but it doesn't always work (no sound, normally causes the phone to lock up and force reset upon hanging up). I really want a non-stock ROM that works, preferably Android Nougat 7.1.2 but everyone seems to get the half finished, get fed up and leave us in the dark, and then finally after 6 months mark it as discontinued (cough cough LiquidDeath). I hope you don't do that because this ROM is promising.
Edit: The locking up may have been my fault for overclocking too high.
Related
Since I am not allowed to post in the developer thread, I want to thank this way for the great gift Omnirom 4.4.
You have breathed new life into my n7000. :crying:
Thanks to chasmodo, herna, AA1973 and all the developers involved in the project for the hard work, patience and humor.
I hope the error report in the new version today (omni-4.4.1-20131208-NIGHTLY-n7000) can help the project to continuously improve.
Awesome ROM indeed
Sent from my GT-N7000 using xda app-developers app
can you show how smooth its running with a video or so?
Same here.. Even I can't post in that thread.
Its a awesome rom, smooth, new features etc. But I have to share some bugs which I thought may be shared here:
1. Can't move apps to sd card.
2. Bluetooth when connected through car (for phone and audio), disconnects and reconnect in every 11-12 mins.
3. Google search and google play services are consuming too much of battery. I guess its a Kitkat issue.
I am currently on 8th Dec rom. Rest is pretty good. No problem at all.
You can't post in a development thread until you reach the number of 10 posts... But you can search the thread without posting..
If you use hot word recognition in GLE, then it will drain battery.
Kernel > herna posted a Kernel which enables apps to be moved. Although Google deprecated this AFAIK.
Last, but not least, thanks for being mentioned, flatters me - but I am *not* a developer!
GALAXY NOTE N7000 // KITKAT 4.4.1 // OMNI
AA1973 said:
You can't post in a development thread until you reach the number of 10 posts... But you can search the thread without posting..
If you use hot word recognition in GLE, then it will drain battery.
Kernel > herna posted a Kernel which enables apps to be moved. Although Google deprecated this AFAIK.
Last, but not least, thanks for being mentioned, flatters me - but I am *not* a developer!
GALAXY NOTE N7000 // KITKAT 4.4.1 // OMNI
Click to expand...
Click to collapse
Even when I switched off the hot word recognition in GLE, location services off, no auto sync, etc still Google search or google play services is the most battery drainer when the phone is not used overnight.
OmniROM is really a real gift for the N7000. It's much better than Cyanogemod for me, because the performance is better. But i also had some trouble and i'm not able to post in the developers thread. Here are my problems:
- external SD card isn't mounted properly, so i have to take some detours to open it with ES explorer
- when i enable ART i can't lock the screen anymore (omni-4.4.1-20131208-NIGHTLY-n7000)
- OpenDelta is able to reduce the update size, but when it boots into TWRP the update fails because the script is searching /sdcard which is the external SD, but the update.zip is stored in the internal SD which is mounted as /emmc, so you have to update manually
Do you have the same issues ?
G4liant said:
OmniROM is really a real gift for the N7000. It's much better than Cyanogemod for me, because the performance is better. But i also had some trouble and i'm not able to post in the developers thread. Here are my problems:
- external SD card isn't mounted properly, so i have to take some detours to open it with ES explorer
- when i enable ART i can't lock the screen anymore (omni-4.4.1-20131208-NIGHTLY-n7000)
- OpenDelta is able to reduce the update size, but when it boots into TWRP the update fails because the script is searching /sdcard which is the external SD, but the update.zip is stored in the internal SD which is mounted as /emmc, so you have to update manually
Do you have the same issues ?
Click to expand...
Click to collapse
No issues with me as you have mentioned. All three options are available to me.
Saurabh4255 said:
Same here.. Even I can't post in that thread.
3. Google search and google play services are consuming too much of battery. I guess its a Kitkat issue.
Click to expand...
Click to collapse
in expanded wifi settings disable "google search if wifi is deaktivated"
updater worked for me today
prinzkazimir said:
in expanded wifi settings disable "google search if wifi is deaktivated"
updater worked for me today
Click to expand...
Click to collapse
Have done that but no success. But yes.. Bcoz of disabling this the footprint of google search on battery consumption is less as compare to previous settings. But other culprit Google play services remains the same.
Just to update on continuous bluetooth disconnection, I unpaired my car connection and also deleted the phone from car and reconnect it. As for now it is paring up nicely for more than 20 mins. Lets see how it reacts if connected for more than this.
My battery is doing fine now, btw.
G4liant said:
- external SD card isn't mounted properly, so i have to take some detours to open it with ES explorer
- when i enable ART i can't lock the screen anymore (omni-4.4.1-20131208-NIGHTLY-n7000)
- OpenDelta is able to reduce the update size, but when it boots into TWRP the update fails because the script is searching /sdcard which is the external SD, but the update.zip is stored in the internal SD which is mounted as /emmc, so you have to update manually
Do you have the same issues ?
Click to expand...
Click to collapse
Use another file explorer. Might be also an issue of es file explorer. Or a mixture of both, as es expects the external in mnt/media_rw
Don't enable ART. It is experimental and has to be treated as such. Hence it is hidden in developer options.
Didn't have such an issue with OpenDelta. In any case. Please remember that
A) Omni is a very "young" firmware
B) OpenDelta has been introduced 2 nightlies ago. Be gentle and patient
For me, OpenDelta worked this morning.
Did you enable SuperSU backup script within SuperSU app, too?
GALAXY NOTE N7000 // KITKAT 4.4.1 // OMNI
AA1973 said:
For me, OpenDelta worked this morning.
Click to expand...
Click to collapse
I will find it out tomorrow.
AA1973 said:
Did you enable SuperSU backup script within SuperSU app, too?
Click to expand...
Click to collapse
For now i haven't activated the backup script. EDIT: It's activated now.
Then do it.
GALAXY NOTE N7000 // KITKAT 4.4.1 // OMNI
Update: Regarding the google search and play service battery consumption, I tried cache and dalvik cache wipe through recovery mode and now batery is giving good backup.
OpenDelta worked good for me! Also running ART! Thanks!
Wonder what boot shows on asylum
prinzkazimir said:
OpenDelta worked good for me! Also running ART! Thanks!
Wonder what boot shows on asylum
Click to expand...
Click to collapse
Well, there is only one way to find out.
But be careful, don't do it if you have a hearth condition or are prone to epilepsy.
Azeazezar said:
Well, there is only one way to find out.
But be careful, don't do it if you have a hearth condition or are prone to epilepsy.
Click to expand...
Click to collapse
Had I listened to you!
As a precaution I have taken the 9/12. I look in here again when I'm back from the sanatorium.
Thank you so much Omni team. I was waiting this ROM. It’s really great user friendly and smooth.
Query: Do the active display in display setting uses the moto x like feature of only activating the pixels where the display is required and not the whole screen?
Want to try Ubuntu Touch but don't wanna lose your data or get into the hassless of flashing it through Ubuntu on PC? Well, I got you covered . Although, do note that it is basically a backup of the ROM, which i just booted into and backed up. So you will be setting it up from scratch just like a fresh install/flash.
A message from the UBPorts Community Manager:-
Hi, Community manager for Ubports.
We have calls and headphones working internally but we aren't sending that out yet, the reason why is because the device over heats, currently the device is usable for hours, if we uploaded the code for calls you wouldn't want to put it too your ear.
We are trying to get it fixed though, before the end of this month is what we're aiming for, GPS, Bluetooth etcetera still wont work for a little while but it'll be useable for calls at least.
Also this port isnt just a consept, the port is real and in time will work with all of the hardware.
Its something to note that only this month has the developer decided to take time of work to work on ubports, so he hasn't had much time before now.
Thank you for the feedback.
Obviously some of the feedback doesn't fall on us such as slow app times and how many apps are in the app store, but we are hoping that porting ubuntu to alternative devices may get more developers looking at and creating apps for ubuntu phones.
I hear if this bug was fixed then apps would start much quicker https://bugs.launchpad.net/apparmor/ bug/1552341
Source: https://forums.oneplus.net/threads/...on-opo-using-twrp.431640/page-2#post-14642747
Now, I've personally tested it by switching to an Android ROM, wiping the 4 Partitions and then restoring this backup, so yes I can confirm that it works!
What you need:-
TWRP 2.8.6.0
The TWRP Backup
WinRAR (32 bit or 64 bit)
Instructions:-
1. Download the Backup and TWRP
2. Flash TWRP, I'd recommend using the official TWRP 2.8.6.0 to avoid any issues.
3. After downloading the backup(5 Files), copy them all in the same folder and extract the one without any .z extension. I splitted them to avoid any issues with files bigger than 4GB, because the backup is 4.01GB in size.
4. After extracting you'll find a single TWRP folder, connect you device and copy it to the main directory of your device's storage, Click "Yes" if it asks for replacing any files.
5. Boot into TWRP and Backup your ROM(Optional)
6. Go back to the main TWRP Home screen->Press Wipe->Advanced Wipe->Mark Dalvik Cache,System,Data and Cache (Make sure you don't tick Internal Storage or USB-OTG).
7. While in TWRP, go to the main home screen and press Restore, there select "Ubuntu Touch" and leave all the 4 Boxes checked. Then, Swipe the button on the bottom and wait. The Numbers won't get updated but don't worry, it is getting restored and can take around 3-5 minutes.
7. Restore the backup. It will stay on the 1+ logo for a while so have some patience.
Disclaimer: I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. YOU are choosing to make these modifications, so don't point the finger at me for messing up your device.
Screenshots: http://goo.gl/dNgCgd
A little Review:-
UI: 8/10. I was really bored with the same old UI of Android, and Ubuntu Touch's UI felt like a good change. The "No buttons required" thing where there's no Home, Back or Menu button might feel weird at first and takes a little getting used to, but in the end provides a refreshing experience.
Stability: 9/10. Its as stable as it gets, No random reboots, No Apps crashing(cause there wasn't any app to use).
Performance: 7/10. Well, there's actually nothing on the App Store to assess the performance but general swiping through apps and menus with more than 8 of em open was smooth for the most part. Webpages load up really quick in the stock browser that comes with it. Although I did notice the phone heating up way too much, reaching temperatures equivalent to what my phone is at after playing heavy games like Asphalt 8, etc. for over 30 mins.
Features: 5/10. Since this is just like a 'Demo' to showcase that Ubuntu Touch running on an Android Device is possible, there aren't many things that work. The Camer, Bluetooth, Calling, 4G(Couldn't test 3G but 2G works), Audio via Headphones(Speakers work fine). Calling doesn't work, Calls fail from my side and when I call from the other side, it keeps ringing, indicating that the call is going on but nothing shows up on the device, where does the call go? I don't know..
Miscellaneous Features: 5/10. The App store on Ubuntu Touch is worse than that of Windows Phone, and believe me when I say that cause I've used Windows Phone as my only device for more than an year. Surprisingly, it has the option to just add a Google Account without having to flash any GApps or something. Then, there's no way you can copy files back and forth without using ADB, so this doesn't feel like an everyday Joe would love to have.
Battery Life: 2/10. Its terrible. Period. I went to sleep with battery at 43%(No flight mode and with Wi-Fi on) and woke up in 4hrs just to find sitting at 5% with the phone switching off in the next few seconds. So yeah, its terrible even with normal usage you'll find it worse than any other Android ROM.
Conclusion: Its still a Work In Progress but at least it boots up, this shows that they might be a little serious about it cause they also have 'Developer' builds uploaded on their website daily. Anyways, I like the concept of having something different from Android, I like where its going and I hope it reaches there..
do you know if this will work with multirom ?
the_mentor said:
do you know if this will work with multirom ?
Click to expand...
Click to collapse
I never really tried it on MultiROM..
@ojaswinsingh
hi.. can i use this backup if my cache and data formated to f2fs ?
Cannot extract twrp.zip what did you zip it with. Also where do the other 4 files go that ate in the folder?
fezzy102 said:
Cannot extract twrp.zip what did you zip it with. Also where do the other 4 files go that ate in the folder?
Click to expand...
Click to collapse
when you open link (for download) you see 5 file (4 of them have name TWRP.z0* and TWRP.zip ) download all of them and extract by Winrar!
lapapunk said:
@ojaswinsingh
hi.. can i use this backup if my cache and data formated to f2fs ?
Click to expand...
Click to collapse
Nope, I won't recommend doing that cause I was on Jgcaap's CM13 before it and had data and cache on F2FS but it never went past the 1+ logo, so I had to come back to ext4 to make it work..
ojaswinsingh said:
Nope, I won't recommend doing that cause I was on Jgcaap's CM13 before it and had data and cache on F2FS but it never went past the 1+ logo, so I had to come back to ext4 to make it work..
Click to expand...
Click to collapse
Thanks) now I'm too on Jgcaap's. CM13
I cant get the backup to show in TWRP any suggestions?
fezzy102 said:
I cant get the backup to show in TWRP any suggestions?
Click to expand...
Click to collapse
Yep. Go to twrp folder on you internal storage. Then if you already copy Ubuntu backup, you can see two folder named like "2628482"(in twrp-BACKUPS). Now you must cut Ubuntu folder and paste to folder with your backups.. It's all )
A message from the UBPorts Community Manager:-
Hi, Community manager for Ubports.
We have calls and headphones working internally but we aren't sending that out yet, the reason why is because the device over heats, currently the device is usable for hours, if we uploaded the code for calls you wouldn't want to put it too your ear.
We are trying to get it fixed though, before the end of this month is what we're aiming for, GPS, Bluetooth etcetera still wont work for a little while but it'll be useable for calls at least.
Also this port isnt just a consept, the port is real and in time will work with all of the hardware.
Its something to note that only this month has the developer decided to take time of work to work on ubports, so he hasn't had much time before now.
Thank you for the feedback.
Obviously some of the feedback doesn't fall on us such as slow app times and how many apps are in the app store, but we are hoping that porting ubuntu to alternative devices may get more developers looking at and creating apps for ubuntu phones.
I hear if this bug was fixed then apps would start much quicker https://bugs.launchpad.net/apparmor/ bug/1552341
Source: https://forums.oneplus.net/threads/...on-opo-using-twrp.431640/page-2#post-14642747
No os installed
After restoring your backup..when tried to reboot it said no os installed..twrp version:2.8.6.0
any help???
the_mentor said:
do you know if this will work with multirom ?
Click to expand...
Click to collapse
You can actually let multirom app to install it for you! Search multirom thread.
Hi, if I make the backup and then the system wants to start, he tells me that no os is installed. What is the reason for this?
Link for Backup is down.
The Wileyfox Storm is now built for by the LineageOS project. Please use the official downloads rather than my build.
Anyone wishing to run my build and modifications is welcome to download them from here with the usual disclaimers about no liability for lost data or exploding kittens. I have also stuck the last released radio firmware in the same directory but please only use this if you have absolutely no other choice.
Cool, will give it a go at some point. Thanks
Hi.
Looks pretty good.
I saw the OTA update for the 260Mb update from Wileyfox. I was fetching the most recent CyanogenOS image to put over mine (I root my device, which kills the OTA updates) and I saw yours.
I thought I'd have a play, and it installed OK, and appears to function well.
Thanks.
I have yet to run into any problems running this. Glad to hear it looks good to you, too. The stock kernel seems to work fine with the lower cpufreq limits, so I'll track that.
THX for work! Two problems found: Can not install gapps with cmrecovery (insufficient disk space), after changing to twrp no problem and sometimes the phone takes a reboot while don't using it. Otherwise everything seems to be all right.
Gapps issue is an odd one. Plenty of space on the /system partition:
Code:
/dev/block/bootdevice/by-name/system 1523568 865944 641240 58% /system
In the past, this was caused by toybox missing awk support. I suspect more of the same, as the Gapps script needs awk to calculate the free space of the /system partition. Stick with TWRP.
Will any updates have to be downloaded and installed via recovery manually while in test builds period please?
Found another problem: Can't make screenshots, the phone claims, there is also to less memory. ???
Gesendet von meinem Lenovo YT3-X50F mit Tapatalk
Updates are via recovery, manual or sideloaded methods. It may well be that a future update will need a wipe as LineageOS are likely to move from test-keys to their own signing key in the near future. Please note I am not the device maintainer for the Storm, I'm just making my own build available for those who may need it. Until LineageOS gets an official build, I will try to update this post when monthly AOSP vulns are fixed in the main repo.
Screenshots: Press and hold power and volume down for a second or so. Works on my handset.
Chron0s said:
Screenshots: Press and hold power and volume down for a second or so. Works on my handset.
Click to expand...
Click to collapse
Thx for reply. Yes i know, but everytime i try, it get this error. There also seems to be no option in nougat to change the path for saving or i can't found it.
---------- Post added at 09:15 AM ---------- Previous post was at 08:18 AM ----------
I found the reason, the Pictures folder have other rights then all other (no x ) but there are 3 Screenshots with date 1970.. inside. Maybe i took some shots with twrp (three screens of home screen from older twrp 2.8 version, now i changed to the newer one) before the installation of rom or between the installation of the two versions. So the folder have got the strong rights from twrp.
Solution: Deleting the /Pictures folder with the file manager of twrp and restart the phone! Deleting or changing rights with the filemanager of lineage doesn't work, also with root.
Now the rom is very useable for me, thx, thx, thx ... LineageOS Nougat on Storm ))
Glad to hear you got it sorted. I should add that you do need to format userdata when coming from Marshmallow or Lollipop for just this sort of problem. 1970 (if that's Jan 1st 1970) is the Unix epoch, which means your device hadn't set its time correctly from a cellular network. NTPsync will help here, using one of the ntp.org pool servers or ntp1.npl.co.uk.
As I said, I'll try to keep on top of vulnerabilities until there's an official LineageOS build with similar functionality.
Chron0s said:
Updates are via recovery, manual or sideloaded methods. It may well be that a future update will need a wipe as LineageOS are likely to move from test-keys to their own signing key in the near future. Please note I am not the device maintainer for the Storm, I'm just making my own build available for those who may need it. Until LineageOS gets an official build, I will try to update this post when monthly AOSP vulns are fixed in the main repo.
Screenshots: Press and hold power and volume down for a second or so. Works on my handset.
Click to expand...
Click to collapse
Does the new 14.1 change the system partitions much from the 13.0 cyanogen mod nightly?
Also what size gapps package is recommended please eg platform ARM64 Android 7.1 variant aroma, stock, mini etc.
Thanks
Chron0s said:
I should add that you do need to format userdata when coming from Marshmallow or Lollipop for just this sort of problem. 1970 (if that's Jan 1st 1970) is the Unix epoch, which means your device hadn't set its time correctly from a cellular network.
Click to expand...
Click to collapse
Yes i know and wiped everything before install, then i took the screenshots with twrp, there i is no network connection at this moment and so no regular time (so the unix start time).
But now a complete different issue, can you make videos with your phone? I can't do it with cam-app of the rom, opencamera or whatsapp inside cam . Pictures, Panoramas works fine and there seems to be everything ok with the rights for apps and folders.
Partitions: No change from 12.1/13.
Gapps: There is room for any of the available OpenGapps packages. arm64 7.1 is the correct architecture.
Camera video recording: Quite right, it doesn't work. I'm looking into it ASAP.
Please could you try this build:
lineage-14.1-20170102-UNOFFICIAL-kipper.zip
md5sum 33062d6d628a1f3102e809bb82efb0b2
This works on my handset now. Please accept my sincere apologies for not noticing this bug.
Chron0s said:
Please could you try this build:
lineage-14.1-20170102-UNOFFICIAL-kipper.zip
md5sum 33062d6d628a1f3102e809bb82efb0b2
This works on my handset now. Please accept my sincere apologies for not noticing this bug.
Click to expand...
Click to collapse
Seems to be all right, videorecording is working now, that was fast
No apologies please, a test-build is for testing i think.
Gesendet von meinem Wileyfox Storm mit Tapatalk
Thanks for testing. I'll update the OP.
I would appreciate some feedback on battery life for this build, please. I have lowered the cpufreq limits from the default 960MHz/800MHz which should, in theory, allow the CPU to spend more time in a lower power state when not particularly taxed. Battery life is one of the bugbears of this device, although I suspect the power required to drive the FHD display far outweighs any savings you get from idling the CPU at a lower state.
I have noticed that mine lasts a damned sight longer in standby, though. This may alleviate some of the "can't charge or turn on when completely flat" reports when people have found their handsets drained dry in standby.
Chron0s said:
I would appreciate some feedback on battery life for this build, please. I have lowered the cpufreq limits from the default 960MHz/800MHz which should, in theory, allow the CPU to spend more time in a lower power state when not particularly taxed. Battery life is one of the bugbears of this device, although I suspect the power required to drive the FHD display far outweighs any savings you get from idling the CPU at a lower state.
I have noticed that mine lasts a damned sight longer in standby, though. This may alleviate some of the "can't charge or turn on when completely flat" reports when people have found their handsets drained dry in standby.
Click to expand...
Click to collapse
Hard to say for me, i think it isn't really other then before (cm13) on my handset. Maybe a little bit better in standby, but not while using it. The battery life on storm is generally not the best :/
But i still have the reboots randomly along the day and don't know why. Could be the lower minimal frequency the reason for such a problem?
At the moment i have deactivated the pin-question of my simcard, so i stay reachable.
It could possibly be the lower frequencies, although mine isn't rebooting.
Code:
kipper:/ $ uptime
12:33:47 up 18:33, 0 users, load average: 4.91, 4.26, 1.91
I'll try the stock settings on the next build when we get January's AOSP updates.
Moto G3 2015 Osprey XT1541 1GB Ram.32bit(ARM)
AFAIK these roms cover other Moto G3 versions but investigate more for yourself.
Always keep Nandroid backups using TWRP of your running Rom. I keep copies of my latest Android 10 Chli360/Lineage running Roms on my Phone's portable SD card in the phone and also on my Laptop.
https://twrp.me
Warning!
I've never bothered with any Android 8 Oreo roms on my G3 2015 Osprey. I went straight to Android 9(PIE).
https://chil360.github.io
I've tried most and now I'm only interested in the Lineage versions and the Havoc versions of Android 10 as these keep the Hardware FM radio that I like to use.
Havoc version,
Havoc-OS-v3.3-20200306-osprey-Unofficial.zip
Working fine and
Lineage,
ineage-17.1-20200308-UNOFFICIAL-osprey.zip
Working fine.
Note: If I recall correctly Chil360 Havoc Android 10 Rom does not need Gapps installing. If Lineage does I use Arm_10_Pico,
Note:
When setting up the phone I never let the phone install backups automatically I have my apps backed up on my SD card and re-install them from there. Google photos will not not clone-Install and a few others so I just re-download those.
Contacts:
Although Google backs up contacts lists to be safe I keep an,"Old School" backup using the Contact's apps Import/Export option and save them to a .vcf file. This will look like contacts.vcf or 000001.vcf on the phone wherever you have chosen to save it. This can be imported into any contacts app,Even on APPLE phones!
I send a copy of this .vcf file to myself attached to an Email. This means I can download my contacts to any phone anywhere in the World if I ever need to.
Note:
I never encrypt my phones so cannot answer any questions on this subject.
If you want to,"Root" the phone then install the .zip version of Magisk from your phone's Internal Memory and keep it on your phone's Internal memory. You install the .zip using TWRP's install option and always take it's advice on clearing Dalvik Cache and Cache.
Then once the phone is booted update both it and it's manager via an Internet connection.
Note: Some,"Pay/Money" apps will detect that you are running a non-stock rom. You can hide these apps using,"Magisk Hide" and in some cases you need to Hide the app AND then use Magisk option to rename itself. You can call it anything you like but keep it simple like Osprey.
HTH
Moto G3 2015 Osprey XT1541 1GB Ram.32bit(ARM)
Chil360 has updated the April 2020 Havoc 3.4 and it now installs on the Above phone. I am testing it as I post.
Havoc-OS-v3.4-20200417-osprey-Unofficial.zip. Does not require Gapps installing.
BTW I do like the AOSP_Pizza Android 9 rom for Chil360 as well(Still has FM RAdio).
https://www.androidfilehost.com/?fid=4349826312261742008
I go back to it sometimes as it has some features others don't have like showing local temp on the Lockscreen and also allows me to install a Custom boot animation logo. I like the old,"Stitch" Moto Logo
The Android 10 roms won't let me change the animated loading logos(They will let me change the static boot logo) or I need to find versions that will work with Android 10
Moto G3 2015 Osprey XT1541 1GB Ram.32bit(ARM)
Just thought I'd update.
Started to install Chil's latest Paranoid Android and it installed fine but stopped as I realized it doesn't have as many tweaks as Havoc 3.4.
Things I like about Havoc 3 series.
I can have,
Date and time in the notification bar.
Battery percentage next to Battery icon and time left when Notification bar is swiped down.
Easy to swap software buttons(I'm right handed so like my Back button on the right).
It still lets me use my old version of Holo Launcher.
You can assign functions to the Software buttons like Long press to Lockscreen. Can't seem to get Long press to enable the Flashlight tho
Advanced Restart on Power button.
Loads more tweaks to explore.
One thing I would like but I'm not sure if the Motos are capable but I have a cheap China phone that lets me double tap the screen to wake it up and I don't mean just at the Top of the phone I mean anywhere on the screen.
I can't see myself using any other version except as stated AOSP Pizza for a bit of a change now and then
PS
Continued thanks to CHIL his work is much appreciated keeping these Classic little phones going
Latest Chil360 roms are out. I'm running Havoc(May Security updated) but FM radio not working
Has anybody else had issues with the FM radio not working after upgrading to v3.5-20200508 version of Havoc Android 10 for Moto G3 2015? I found after upgrading to this version, the FM radio would no longer work, it would just freeze. Downgrading to v3.4-20200417, it would work perfectly again. Upgrading again to v3.5-20200508, it no longer would work. Has anything been changed that would cause this? Other than this issue, I believe that the ROM is excellent.
Gord
Glad you found this. Checking the FM radio is usually one of the first things I do but didn't this time
Yes you are right it's not working for me as well in Havoc 3.5.
Gone back to 3.4 with no problems :good:
Gordster
Thank you for responding to my reply and addressing the FM radio issue. I have found one other ongoing problem with the camera app. This has been occurring with all custom roms that I have tried whether Android 9 or 10. When photos or videos are saved to the internal phone, they go to the "main storage\DCIM\Camera" directory. I however like to save my photos and videos directly to the SD card.
With Android 6 they could be directed to "sdcard\DCIM\Camera" directory but with all custom roms I've tried when directed to the SD card, they wind up in "sdcard\Android\data\org.lineageos.snap\files" directory. Can this be changed so they go directly to the default location "sdcard\DCIM\Camera" directory?
Thanks
Gord
Gordster said:
Thank you for responding to my reply and addressing the FM radio issue. I have found one other ongoing problem with the camera app. This has been occurring with all custom roms that I have tried whether Android 9 or 10. When photos or videos are saved to the internal phone, they go to the "main storage\DCIM\Camera" directory. I however like to save my photos and videos directly to the SD card.
With Android 6 they could be directed to "sdcard\DCIM\Camera" directory but with all custom roms I've tried when directed to the SD card, they wind up in "sdcard\Android\data\org.lineageos.snap\files" directory. Can this be changed so they go directly to the default location "sdcard\DCIM\Camera" directory?
Thanks
Gord
Click to expand...
Click to collapse
I haven't used a Stock android Camera for years. I use the way better,"Open Camera" .You can set it to save to the SD card by enabling it's framework option and then pointing it to the SD card. It now says it contains ads but It used to be ad-free but I haven't seen any ads even in the latest version.
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en_GB
Open Camera > Gear icon(settings) More Camera controls and Use Storage Access Framework and then Save location and say yes to permissions asked
R1ffR4ff said:
I haven't used a Stock android Camera for years. I use the way better,"Open Camera" .You can set it to save to the SD card by enabling it's framework option and then pointing it to the SD card. It now says it contains ads but It used to be ad-free but I haven't seen any ads even in the latest version.
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en_GB
Open Camera > Gear icon(settings) More Camera controls and Use Storage Access Framework and then Save location and say yes to permissions asked
Click to expand...
Click to collapse
How can you use the OpenCamera? I try that but the photo with flash are blur, only Moto Camera can do photo with flash without the blur effect.
stukdev said:
How can you use the OpenCamera? I try that but the photo with flash are blur, only Moto Camera can do photo with flash without the blur effect.
Click to expand...
Click to collapse
Open camera has worked on all the roms I've tested.
Try another Camera app and if it does it with that you may have a hardware fault
Make a Nandroid backup and then do a Factory reset from Recovery mode but when setting up the phone don't let Google auto install any apps and just get to the Stock camera as soon as you can and see if it works. There may be an app you install that is causing the problem.
BTW.
Check back through this thread on how I install custom roms. I do it clean and add my apps back after I've got into the phone from .apk backups.
R1ffR4ff said:
Open camera has worked on all the roms I've tested.
Try another Camera app and if it does it with that you may have a hardware fault
Make a Nandroid backup and then do a Factory reset from Recovery mode but when setting up the phone don't let Google auto install any apps and just get to the Stock camera as soon as you can and see if it works. There may be an app you install that is causing the problem.
BTW.
Check back through this thread on how I install custom roms. I do it clean and add my apps back after I've got into the phone from .apk backups.
Click to expand...
Click to collapse
Maybe its an hardware fault, but with the Moto App i haven't any problem
stukdev said:
Maybe its an hardware fault, but with the Moto App i haven't any problem
Click to expand...
Click to collapse
See previous reply and also I don't know if you know the,"Soft Reset" trick on Moto phones that can clear some problems.
Press and hold the Power button in for around 10/15 seconds until the phone restarts. This emulates taking the Battery out and can clear clogged RAM of old data that can prevent correct operation
I've been running the latest May AOSP PIZZA
AOSiP-9.0-Pizza-osprey-20200517.zip
Since yesterday and all seems fine so far. Only thing missing is the local Temp on the lock screen unless I'm missing a setting. This was the same with the last version
Not a deal breaker
Installed Chil360's latest AOSP_QUICHE Android 10 June updates(Clean install).
AOSiP-10-Quiche-osprey-20200605.zip
All working well including FM Radio. Updated TWRP using the APP to 3.3.1 as the TWRP clock and date went funky but may not be related.
Phone is still rooted with Magisk and Root removed before installing clean and then re-rooted and Magisk updated.
Nice editing option to move Software buttons around in the AOSP roms. When texting I have a habit of hitting the Home button making my SMS app disappear. I've moved my Home button a little off-centre more to the right(I'm right handed) and this has cured that
Update. The Rom is working well but it's doesn't feel as slick as the AOSP_PIZZA version(May version) so I've gone back to that for now just out of personal preference.
So presently my faves are Havoc 3.4 and Havoc 3.6(Android 10) 2020 and AOSP_PIZZA Android 9 May 2020 version(Moto Stitch Boot animation).
Again my ongoing thanks for CHIL360's work in keeping these great little phones updated
Latest Android 10 Havoc 3.6 released by Chil360 with June 2020 updates,
https://chil360.github.io/ten.html
Gapps included.
Installed and all working e.g Text/Calls/GPS/FM Radio/ WiFi/WiFi Hotspot/Camera/Bluetooth etc.
Very fast booting and really slick
One possible glitch is the Stock Camera has the option to Save to SD but it doesn't seem to work. As I rarely use the Stock Camera preferring the much better,"Open Camera" from the Playstore this is not an issue for me
PS
Because of the dedication of the Android Developers on here we have an old 2015 Phone/s with more up-to-date software than many brand new phones
Chil360 has released a first and new Rom to his collection. Android 10 PixelExperience Plus 10.0,
https://chil360.github.io
If you like Google I think you will like this
I wonder if he might be looking to work on the new Android 11 if it can be used on the Moto G3
Then install Gapps if required.
Then do another Factory reset for good measure.
If ever there's a problem when first setting up after the first boot-up has loaded just press and hold the Power Button in for around 10/15 seconds and the phone will reboot(Soft Reset) which emulates taking the Battery out. [/B]
Chil360 has released a new Rom,
potato_osprey-10-20200619-croquette.v3.2.0+15.Community.zip
Unfortunately I cannot test it as it boot-loops.
Tried all my tricks but no good
Gone back to Havoc 3.6
Latest POSP Croquette v3.2.0-hotfix+16 loads but no FM radio so no good to me
Back to Havoc 3.6(Android 10)/ AOSP_PIZZA Android 9 May version
July 2020 Havoc 3.7 released by Chil360.
Installed clean and running well
The Havoc 3.7 July 2020 release by Chil360 IMO is the best and most stable custom rom I've tested for Moto g3 2015 (osprey) and is highly customizable. I especially like the "smart battery charger" feature which allows the charger to be set at a maximum percentage in my case 92%. I have not found any other custom rom with this feature. This will help prolong the battery life by not charging it to 100% every time. The July 2020 release installed fine and is running with no apparent problems. I tried the latest "official" lineageos version July 3 2020 but had problems with random spontaneous reboots.
ive used Lineage OS' device tree for the htc one m8 to port Resurrection Remix Q to the HTC one m8.
thought i better post it here, seeing as there seems to be no other RR Q ports for this phone anywhere else.
just flash it via TWRP.
please let me know if you find anything thats broken. im rather new to ROM making.
note: this rom isn't pre-odexed so first-boot might take a bit.
this is the kernel source i used: https://github.com/LineageOS/android_kernel_htc_msm8974/tree/lineage-17.1
and this is the device tree: https://github.com/LineageOS/android_device_htc_m8/tree/lineage-17.1
all i did was copy&paste the kernel and dev tree into RR's source directory, rewritethe references to lineage inside the device files to reference RR, fixed some SELinux compatibility issues, and then proceeded as normal to build RR.
UPDATE: 03-02-2021
fixed boot failure after restoring TWRP backup
i have been made aware that this does not boot upon restoring a TWRP backup.
i have updated the zip in the original post to fix this.
Any plans to get on official RR?
fela4 said:
Any plans to get on official RR?
Click to expand...
Click to collapse
likely not. RR hasnt supported the m8 in a few years now.
mathew2214 said:
ive used Lineage OS' device tree for the htc one m8 to port Resurrection Remix Q to the HTC one m8.
thought i better post it here, seeing as there seems to be no other RR Q ports for this phone anywhere else.
just flash it via TWRP.
please let me know if you find anything thats broken. im rather new to ROM making.
note: this rom isn't pre-odexed so first-boot might take a bit.
this is the kernel source i used: https://github.com/LineageOS/android_kernel_htc_msm8974/tree/lineage-17.1
and this is the device tree: https://github.com/LineageOS/android_device_htc_m8/tree/lineage-17.1
all i did was copy&paste the kernel and dev tree into RR's source directory, rewritethe references to lineage inside the device files to reference RR, fixed some SELinux compatibility issues, and then proceeded as normal to build RR.
UPDATE: 03-02-2021
fixed boot failure after restoring TWRP backup
Click to expand...
Click to collapse
The ROM itself is excellent,I have one on Samsung, but this one does not work at all, the interface freezes constantly.Very sorry...
try formtatting data to f2fs and then clean-flashing the rom.
mathew2214 said:
try formtatting data to f2fs and then clean-flashing the rom.
Click to expand...
Click to collapse
Does this ROM work well for you?
@[email protected] said:
Does this ROM work well for you?
Click to expand...
Click to collapse
yes! it works rather well. most of the issues i run into are magisk bugs. other than that there's only the occasional systemui lag that lasts for maybe a second or two, and this only happens maybe once a day. i should be noted that i reboot my phone several times a day, and i dont use Gapps.
mathew2214 said:
yes! it works rather well. most of the issues i run into are magisk bugs. other than that there's only the occasional systemui lag that lasts for maybe a second or two, and this only happens maybe once a day. i should be noted that i reboot my phone several times a day, and i dont use Gapps.
Click to expand...
Click to collapse
I don't use Gapps,I use MicroG and I have a system freeze in almost every application.
@[email protected] said:
I don't use Gapps,I use MicroG and I have a system freeze in almost every application.
Click to expand...
Click to collapse
sounds like a storage operation issues. see if switching the system partition format to ext4, cache to ext4. userdata and internal storage to f2fs helps at all. clean-flash after you change formats. if that does nothing, please tell me if the presence (or lack of) an external SD card affects this in any way.
mathew2214 said:
sounds like a storage operation issues. see if switching the system partition format to ext4, cache to ext4. userdata and internal storage to f2fs helps at all. clean-flash after you change formats. if that does nothing, please tell me if the presence (or lack of) an external SD card affects this in any way.
Click to expand...
Click to collapse
I tried to use this ROM in various ways, switching the system partition to ext4 and to f2fs, both with an sd card and without sd. Nothing helps - constant freezes of the smartphone, yesterday I installed Lineage 17.1-it works smoothly and without delays. And so I wanted Resurrection Remix Q, sorry...
I tried to do a clean install ,and then I tried to flash over RR-P-v7. 0. 2-20190507-m8-Release, nothing helps.It freezes so that you have to press the off button and the volume rocker with two fingers until a full reboot.
update rom
miyqwx said:
update rom
Click to expand...
Click to collapse
sorry but i cannot. i am no longer in possession of a functioning m8.
mathew2214 said:
sorry but i cannot. i am no longer in possession of a functioning m8.
Click to expand...
Click to collapse
If you post a video on how to port a rom, maybe I can add non-ROMs to the device, example havoc
mathew2214 said:
sorry but i cannot. i am no longer in possession of a functioning m8.
Click to expand...
Click to collapse
i tried various tests and i found a working rom on the device but the screen was not working there was a mouse as if using a computer
-
The processor in the rom I ported is the same as the processor of the m8