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
Related
Hi all, here I wish to continue porting OmniROM from the P4/P4wifi over to our device the P5/P5wifi.
*Please note that this is simply a port of an already built rom. It was not built from source therefore anything that you may find to be broken will more than likely remain broken until it is fixed in the parent ROM.
-Many thanks to the builder of this rom @AAccount. His hard work made this ROM possible. :good:
-Thanks to @jolinnard whose kernel is being used in these ROMs. :good:
*On first boot the keyboard will not be showing. The fix is simple. Go to settings>Language & Input. Tap on Current Keyboard and flip the toggle next to Hardware. The keyboard should now be fine.
Working:
Everything works on the P5 AFAIK
Not working:
SELinux---------Need a recovery that supports it.
To those looking forward to a P5 3G rom then please note that there will not be one any time soon. AAccount has stopped building for the p4 3g so that means we don't have a 3g rom to port anymore. So unless AAccount starts porting for the p4 again there won't be a P5 rom.
Flash Instructions
Wipe data, system, cache, dalvik if coming from another ROM. If ugrading to a newer build then a simple Dalvik and cache wipe will do
Flash the ROM zip
Flash GAPPs (Thanks to @jolinnard)
Flash SuperSU
Reboot and enjoy
Original ROM thread
Credits
@AAccount - for the ROM
@jolinnard - For the kernel
@decatf - for his work on the p4 kernel which is used here that delivers great performance
If you helped out and I missed you in the credits then send me a PM and you will be credited
This port has been discontinued!!
"See why
Hey! Maybe some day I will back to Omni. I'm planning to erase my Gtab of Google stuff and enjoy a clean Android experience.
jolinnard said:
Hey! Maybe some day I will back to Omni. I'm planning to erase my Gtab of Google stuff and enjoy a clean Android experience.
Click to expand...
Click to collapse
@L3Ron ,i will give it a try.
@jolinnard
If you want to port or start with omni source? Nice to See your work for our Tab 8.9.
jolinnard said:
Hey! Maybe some day I will back to Omni. I'm planning to erase my Gtab of Google stuff and enjoy a clean Android experience.
Click to expand...
Click to collapse
Awesome!! Erased my internal sdcard by accident last week. Luckily I have the same files on my Nexus 9 so I was saved. This port works great for me. Should I even port for the P5? AAccount stopped building for the p4 as of May 23. Reason being that 3G doesn't work but oddly enough it does work on the P5 using our modified KK kernel and your data_on script.
bierma32 said:
@L3R0N ,i will give it a try.
Click to expand...
Click to collapse
Great. Tell me how it works for you.
L3R0N said:
Great. Tell me how it works for you.
Click to expand...
Click to collapse
Installed the Rom with out problems, i done a clean install and wipe / Format system / data / cache and dalvik.
I looks smooth and battery are good, it goes into deepsleep without battery consum.
Onliest Problem is i can not connet with wifi to a network. I can See all avaible network ,but no connection.
bierma32 said:
Installed the Rom with out problems, i done a clean install and wipe / Format system / data / cache and dalvik.
I looks smooth and battery are good, it goes into deepsleep without battery consum.
Onliest Problem is i can not connet with wifi to a network. I can See all avaible network ,but no connection.
Click to expand...
Click to collapse
Did you try with advanced wifi configuration? Try not use dhcp to assign wifi. Use a fixed ip. I had the same issue and that was the solution.
?
Enviado desde mi LG-D855
julen163 said:
Did you try with advanced wifi configuration? Try not use dhcp to assign wifi. Use a fixed ip. I had the same issue and that was the solution.
?
Enviado desde mi LG-D855
Click to expand...
Click to collapse
I tried different setting at the advanced configuration of WLAN settings with out success.
bierma32 said:
I tried different setting at the advanced configuration of WLAN settings with out success.
Click to expand...
Click to collapse
I have no such problems. My WiFi connects just fine. Try turning airplane mode on for a moment then turn it back off and try connecting again. Could it be the kernel? I'll p.m you a kernel to try and see if it fixes anything later on. Any logs?
OP has been updated with links to the new build released by AAccount today. According to him there were no major changes, just the usual Omni sync.
thanks for the unexpected gift! unfortunately i have problems with the zip package, it can't be opened/flashed, redownloaded 4-5 times from pc and tablet, same, checked the MD5 and it matches...am i the only one having troubles with it?
chemicalbuz said:
thanks for the unexpected gift! unfortunately i have problems with the zip package, it can't be opened/flashed, redownloaded 4-5 times from pc and tablet, same, checked the MD5 and it matches...am i the only one having troubles with it?
Click to expand...
Click to collapse
Nope same overhere.
Made a backup but transferred it to pc so I've got a problem! TWRP and no flashable zip on the internal sd...
Edit: used the sideload option with ADB and used the omni-5.1.1-20150706-p5wifi-HOMEMADE ROM
Got also problems with the WiFi connection. My network uses 192.168.2.xx range
chemicalbuz said:
thanks for the unexpected gift! unfortunately i have problems with the zip package, it can't be opened/flashed, redownloaded 4-5 times from pc and tablet, same, checked the MD5 and it matches...am i the only one having troubles with it?
Click to expand...
Click to collapse
No you are not the only one. This was reported to me earlier today by another user. I'm in the process of uploading a new zip to androidfilehost and another to mega. They will be up soon.
Nonomen said:
Nope same overhere.
Made a backup but transferred it to pc so I've got a problem! TWRP and no flashable zip on the internal sd...
Click to expand...
Click to collapse
I'm sorry to hear that. You can use adb to push a zip file to your sdcard for installation.
Use this command
Code:
adb push romname.zip sdcard
Or you could use sideload to install one as well. in twrp go to advanced then select adb sideload and connect your tab to your pc. Open up windows command prompt and type
Code:
adb sideload romname.zip
This should get a rom installed to your tab.
File has been re-uploaded. It opens fine now and should work fine.
L3R0N said:
File has been re-uploaded. It opens fine now and should work fine.
Click to expand...
Click to collapse
tnx for the quick answer. I've been able to sideload your first rom but it has lot of fc when installing or updating the apps from the playstore. Setting cpu to 1.2 had no result.
I will try your new uploaded file tomorrow.
Nonomen said:
tnx for the quick answer. I've been able to sideload your first rom but it has lot of fc when installing or updating the apps from the playstore. Setting cpu to 1.2 had no result.
I will try your new uploaded file tomorrow.
Click to expand...
Click to collapse
I have absolutely no problems with the ROM. No force closes or anything. Can you try a clean install of the 0716 build and see if it fixes anything?
Just before your re-upload I installed aosp-5.1.1-p5wifi-20150513. (Jollinnard). This ROM runs better than the UltraPlus I had before.
What are the advantages of your ROM over Jollinard's?
Nonomen said:
Just before your re-upload I installed aosp-5.1.1-p5wifi-20150513. (Jollinnard). This ROM runs better than the UltraPlus I had before.
What are the advantages of your ROM over Jollinard's?
Click to expand...
Click to collapse
There aren't any huge differences but here are a few notable changes
1) Ability to change battery icon
2) Battery color changes based on charge level
3) Pre rooted
4) Performance settings app included
5) Omniswitch recent
And a few others nothing big. IMO I prefer the browser in the omnirom over the aosp browser and the omni keyboard over the Google keyboard in the aosp ROM. But that's personal preference. Try both and pick a side *twix ad*
how i can use this rom for the p5 ?
thanks
4rch0 said:
how i can use this rom for the p5 ?
thanks
Click to expand...
Click to collapse
Edit the updater script and at the top where you see p5wifi simply delete the "WiFi" part so only p5 remains. Save the file put it back into the ROM zip and flash. Or you could simply flash the p5wifi recovery and you'll no longer have to worry about editing the script.
For future ROMs I think I'll remove the assert lines in the updater script so nobody else will have to worry about them.
For this fix to work you need zip of two different ROMs one with working adopted sd and other is the rom you want to flash ( the one showing corrupted sd card when you try to format it as internal eg- cm).
I recommend you to use orion as the first zip (the one with working adopted sd).
Now follow these steps:-
1- Flash the first zip in which adopted is working fine.
2-format your sd card as internal
3- using any root explorer copy misc folder from data and paste it in your sd card
4-now perform a clean flash of your desired ROM (dont wipe sd card)
5- before rebooting go to file manager of twrp copy misc folder that you copied in step 3 to the data folder.
6- reboot , you will notice you have a working adopted sd (no need to format it again).
Well its long method but it would surely work and you can switch roms without loosing adopted sd data with the same method.
Feel free to ask if you didn't get something.
Hey! bro nevermind This Was very big missunderstanding.......sorry for that...keep going
shyvam said:
Don't create duplicate threads....going to report...
---------- Post added at 09:42 AM ---------- Previous post was at 09:33 AM ----------
Here http://forum.xda-developers.com/moto-e/general/enable-adopted-sdcard-cm-based-roms-t3322415 is same and this thread created before you created your ...read rules here http://forum.xda-developers.com/announcement.php?a=81 and then think to create
I hope you can understand ~
Click to expand...
Click to collapse
this method is different....and the one mentioned in link may give bootloop and is specially for cm
It's the same thing mentioned in here
http://forum.xda-developers.com/moto-e/general/enable-adopted-sdcard-cm-based-roms-t3322415
Either you dirty flash the 2nd rom or copy the misc folder. It's the same thing.
Isn't it's easier to dirty flash rather copying and pasting things?
And success rate with this method is 100 % for every rom
-z3r0- said:
It's the same thing mentioned in here
http://forum.xda-developers.com/moto-e/general/enable-adopted-sdcard-cm-based-roms-t3322415
Either you dirty flash the 2nd rom or copy the misc folder. It's the same thing.
Isn't it's easier to dirty flash rather copying and pasting things?
Click to expand...
Click to collapse
you are gonna get bootloop if you are flashing different rom
Abhimanyu Shekhawat 121 said:
you are gonna get bootloop if you are flashing different rom
Click to expand...
Click to collapse
Maybe.
Since after flashing the first rom, the only thing we're supposed to setup is the google account and no other user apps. Since we are dirty flashing the second rom, there's no messing with data partition. So chances of having bootloop is very low.
-z3r0- said:
Maybe.
Since after flashing the first rom, the only thing we're supposed to setup is the google account and no other user apps. Since we are dirty flashing the second rom, there's no messing with data partition. So chances of having bootloop is very low.
Click to expand...
Click to collapse
i have never been this lucky ...i always get bootloop
Abhimanyu Shekhawat 121 said:
this method is different....and the one mentioned in link may give bootloop and is specially for cm
Click to expand...
Click to collapse
Hey Brother...sorry for that i was thinking this is same......omg Very Big missunderstanding
shyvam said:
Hey Brother...sorry for that i was thinking this is same......omg Very Big missunderstanding
Click to expand...
Click to collapse
it really works man, thanks a lot
Abhimanyu Shekhawat 121 said:
For this fix to work you need zip of two different ROMs one with working adopted sd and other is the rom you want to flash ( the one showing corrupted sd card when you try to format it as internal eg- cm).
I recommend you to use orion as the first zip (the one with working adopted sd).
Now follow these steps:-
1- Flash the first zip in which adopted is working fine.
2-format your sd card as internal
3- using any root explorer copy misc folder from data and paste it in your sd card
4-now perform a clean flash of your desired ROM (dont wipe sd card)
5- before rebooting go to file manager of twrp copy misc folder that you copied in step 3 to the data folder.
6- reboot , you will notice you have a working adopted sd (no need to format it again).
Well its long method but it would surely work and you can switch roms without loosing adopted sd data with the same method.
Feel free to ask if you didn't get something.
Click to expand...
Click to collapse
it really works man, thanks a lot
---------- Post added at 10:40 AM ---------- Previous post was at 10:37 AM ----------
i used misc folder of orion rom and pasted it in the cm13 and the sd card adoption works super fine, after installing many apps, some of the apps couldnt move to sd card like whatsapp, imo, fb
kindly reply any solution for this please
thankyou
rahul casey said:
it really works man, thanks a lot
---------- Post added at 10:40 AM ---------- Previous post was at 10:37 AM ----------
i used misc folder of orion rom and pasted it in the cm13 and the sd card adoption works super fine, after installing many apps, some of the apps couldnt move to sd card like whatsapp, imo, fb
kindly reply any solution for this please
thankyou
Click to expand...
Click to collapse
Moving those apps isnt supported by rom, if you want this feature switch to Orion or Resurrection remix
Hit thanks if i have helped
Abhimanyu Shekhawat 121 said:
Moving those apps isnt supported by rom, if you want this feature switch to Orion or Resurrection remix
Hit thanks if i have helped
Click to expand...
Click to collapse
orion os is hanging here and there and always booting, if i update the cm13 to newer version will this be solved?
rahul casey said:
orion os is hanging here and there and always booting, if i update the cm13 to newer version will this be solved?
Click to expand...
Click to collapse
orion takes a bit more time to boot cause it optimizes apps behind boot animations......and there are three roms which have force move commit that are RR Orion and vrtoxin
Abhimanyu Shekhawat 121 said:
orion takes a bit more time to boot cause it optimizes apps behind boot animations......and there are three roms which have force move commit that are RR Orion and vrtoxin
Click to expand...
Click to collapse
so if i need to update to the latest version of cm13, do i need to do the same procedures with misc folder like copying that folder before flashing the rom???
rahul casey said:
so if i need to update to the latest version of cm13, do i need to do the same procedures with misc folder like copying that folder before flashing the rom???
Click to expand...
Click to collapse
First copy the folder........then first try dirty flash of latest nighlty if it boots you are lucky....if you get boot loop wipe every thing .....flash ROM and then paste misc folder to data
Abhimanyu Shekhawat 121 said:
orion takes a bit more time to boot cause it optimizes apps behind boot animations......and there are three roms which have force move commit that are RR Orion and vrtoxin
Click to expand...
Click to collapse
does rr support force move to sd..i have used it i dont think its there
-Adarsh- said:
does rr support force move to sd..i have used it i dont think its there
Click to expand...
Click to collapse
Its there in latest build ......i have tried it
Abhimanyu Shekhawat 121 said:
Its there in latest build ......i have tried it
Click to expand...
Click to collapse
plz show a screen shot..i am using the latest one..but there isnt a force to sd button..plz help..u are using zeeshan's rom only na?
-Adarsh- said:
plz show a screen shot..i am using the latest one..but there isnt a force to sd button..plz help..u are using zeeshan's rom only na?
Click to expand...
Click to collapse
i have tried that rom .....but now am on cm.....check their github its there...
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.
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.
(My English isn't very practice. If you have any question reading this post, please feel free to ask. I'll try my best to express.)
## 0. Update: 2018/04/16
Some information I got today:
1. OnePlus is doing a repartition in OP5 Open Beta 8 / OP5T Open Beta 6 (or earlier, who knows). It'll split the 1.5GB "last_parti" partition into a 1.0GB "vendor" and a ~500MB "reserve3" partition while booting the system.
2. Yes, the repartition process was done in system, not during OTA in recovery.
3. The official vendor partition is still unused (not formatted). OnePlus will fill it in a future OTA, said their engineer.
4. I think it won't be conflicted with our "homemade" unofficial Treble. I just tested that the stock H2OS/OxygenOS can run on our homemade partition table.
5. It's very easy to undo the unofficial treble. I'll make an undo flashable zip later (through it's unnecessary in this time).
6. Of course, MoKee now (since 20180417) can run on the official partition table too.
==========
The MoKee ROM is now shipping unofficial Treble update for OnePlus 5/5T since 20180411. As the maintainer, I would like to share some information here.
## 1. How is this possible for OP5/5T?
Project Treble requires 2 keys: a standalone /vendor partition, and fully binderized HALs.
In fact, OnePlus have a 1.4GB unused, unformatted partition "sdf6" on OnePlus 3, 3T, 5 and 5T. This partition was possibly left by the ODM company, OPPO. OPPO R11/R11s series have a simular partition layout with OnePlus, and OPPO really did release an OTA update to enable Project Treble for their products.
The other key is binerized HALs. More specifically, the Camera HAL. The good news is, OnePlus recently released OP5 Open Beta 6 and OP5T Open Beta 4, with all fully binerized HALs, including the Camera HAL.
So as these 2 majar problems were solved. Project Treble is possible.
## 2. How did this come true?
To make Project Treble come true for OnePlus 5/5T, these should be done:
1. All vender-specific blobs should be moved to /vendor
2. Some blobs load config files from /system/etc. Just hex-edit them to load from /vendor/etc instead
3. Label and format that unused sdf6 partition as /vendor - this should be automatically done with an OTA script
4. The kernel should mount sdf6 as /vendor as well
## For users - How to enable Treble for OP5/5T?
The most easy way now is, flash the latest MoKee MK81.0 nightly build with latest TWRP (OP5: http://rom.mk/?device=cheeseburger, OP5T: http://rom.mk/?device=dumpling). The updater script will do the job automatically for you.
It's possible to make a flashable zip contains only the kernel and vendor image, without the MoKee system. But I'm busying on some other features. I'll do it later.
Tested fully works with Phh-treble system image, including:
- Audio
- Camera
- Phone & data
- Bluetooth & Wi-Fi
- Fingerprint
## For developers - How to ship Treblize update with my ROM?
(I'm organizing the patch list, I'll updte this section later)
## Can I flash non-Treble ROMs? How to "undo" this change?
You don't need to undo it, I think. For those non-Treble ROMs, including H2OS and OxygenOS, the /vendor partition is invisible. So you can flash back to any other ROMs at any time you want.
This is good news for us, thank you for your hard working!
So, once we flash the Mokee ROM, will we then be able to flash the other treble ROMs like RR and Lineage?
Skeptico said:
So, once we flash the Mokee ROM, will we then be able to flash the other treble ROMs like RR and Lineage?
Click to expand...
Click to collapse
Of course.
Great job!
Any specific instructions to install this or like a normal install ???
Amanpreetsingh said:
Any specific instructions to install this or like a normal install ???
Click to expand...
Click to collapse
Please, read OP message fully
you are awesome, big thank you from every OP5/5t owner
Damn, Oppo enabled Treble but 1+ didn't
What a shame...
Does this mean that the camera quality will be as good as stock on a custom room?
@chenxingyu If we flash Oxygen OS again on the treblized 5/5T, won't it again repartion the device again and create the sdf6 partition again? Just a doubt.
hemant_jeengar said:
@chenxingyu If we flash Oxygen OS again on the treblized 5/5T, won't it again repartion the device again and create the sdf6 partition again? Just a doubt.
Click to expand...
Click to collapse
No, as the normal update packages don't touch that partition. On the other hand, there's no repartitioning involved - the type, filesystem and mount point of /sdf6 are changed.
hemant_jeengar said:
@chenxingyu If we flash Oxygen OS again on the treblized 5/5T, won't it again repartion the device again and create the sdf6 partition again? Just a doubt.
Click to expand...
Click to collapse
No, Oxygen OS doesn't know there's a partition named sdf6.
First of all appreciate your effort for bringing treble support for op5t.. am currently running xxx ROM and decrypted..questions I have is does blu_spark or codeworkx twrp support flashing system image..also if I flash mokee latest update then will it wipe all my internal storage data..also I read no_verity zip doesn't work so when we go back to other non-treble roms then format data is mandatory..am I right..
Can someone who has already installed a treble gsi try and install oneplus camera apk and see what's happens? Or maybe even gcam? Thanks
Jamie_oppo said:
Can someone who has already installed a treble gsi try and install oneplus camera apk and see what's happens? Or maybe even gcam? Thanks
Click to expand...
Click to collapse
Gcam is crashing..tested and confirmed by a user in the group.. thanks
Can someone post a mirror link. For some reason I cant download from the main site, the countdown disappears at 56 seconds.
This is all I see
cubandanger05 said:
Can someone post a mirror link. For some reason I cant download from the main site, the countdown disappears at 56 seconds.
Click to expand...
Click to collapse
Had the same issue, downloading work on internet explorer on PC so maybe Safari on Mac? Give that a shot
BenisMusical said:
Had the same issue, downloading work on internet explorer on PC so maybe Safari on Mac? Give that a shot
Click to expand...
Click to collapse
Tried bunch of different browsers on my phone, desktop mode and all, but nothing, I'm going to have to try on my laptop tonight. Unless someone posts a mirror link.
Not working on the computer at work ?, getting frustrated ?.