hi all
for those impatient and dare to try, plus able to handle problems ON YOUR OWN as i cannot offer any help at this point:
anyone interested to test an updated version of BeastMode Kernel R154 by @freeza with the latest samsung firmware N960FXXU8FUD1?
please be noted that:
- this might be EXTREMELY DANGEROUS or could BRICK YOUR PHONE in a few seconds, and I am not responsible for bricked devices or any damages which may arise. so, you have been WARNED
- I have NOT TESTED on my n960f yet (just updated to TH4 from pie but not rooted yet for some reasons). SO THINK TWICE!!
- chances the phone may not boot up properly (boot loop or hang) due to the toolchains used to compile the kernel. I have encoutered this before with only one of the four or five gcc i had which booted up the phone successfully
ideal situation to minimize uncertainties:
- already on ud1
- data/cache partition is ext4 formatted (ideally NOT f2fs as supported by bm kernel)
- capable of diagnostic/identify the problems by examining the logcat/last_kmsg and the like would defintely a plus
to be continued...
Hello, Is this gonna work on newer BL version? FUE5 version, also @CyderXDA would wanna try it, but he's on newer BL. We also have Exynos9810 Telegram Chat, there's N9/S9/S9+ users in there that maybe could test for you and stuff if you're interested
JC1126 said:
Hello, Is this gonna work on newer BL version? FUE5 version, also @CyderXDA would wanna try it, but he's on newer BL. We also have Exynos9810 Telegram Chat, there's N9/S9/S9+ users in there that maybe could test for you and stuff if you're interested
Click to expand...
Click to collapse
hi
samsung has just posted a newer firmware N960FXXS8FUE5, probably hours ago, i am going to update it first. will let you guys know
thanks for your interests
ykkfive said:
hi
samsung has just posted a newer firmware N960FXXS8FUE5, probably hours ago, i am going to update it first. will let you guys know
thanks for your interests
Click to expand...
Click to collapse
Alright Goodluck!
JC1126 said:
Alright Goodluck!
Click to expand...
Click to collapse
update 20160616
updated to samsung ue5 sources
i have built 2 different versions, one with gcc 4.9 and the other with gcc 12. there will be only one version in the future (either gcc4 or 12). the reason i built 2 versions this time is in case one of the gcc used doesnt boot probably there's another one to try
differences between @freeza 's R154:
- kernel sources updated (N960F) without any fix or new feature
- not pre-rooted/pre-patched by magisk since the magisk version may differs from what u r using
- NOTE: other devices preiously supported are not recommeded yet, although you may try, i cant make any promise it will work since i didnt look at other devices sources
thinking if i should release it for testing now or wait until i have time to test it myself coz i don want to brick anyone's phone, including mine of coz
ykkfive said:
update 20160616
updated to samsung ue5 sources
i have built 2 different versions, one with gcc 4.9 and the other with gcc 12. there will be only one version in the future (either gcc4 or 12). the reason i built 2 versions this time is in case one of the gcc used doesnt boot probably there's another one to try
differences between @freeza 's R154:
- kernel sources updated without any fix or new feature
- not pre-rooted/pre-patched by magisk since the magisk version may differs from what u r using
- f2fs supported as R154 (cache/data)
thinking if i should release it for testing now or wait until i have time to test it myself coz i don want to brick anyone's phone, including mine of coz
Click to expand...
Click to collapse
Holy that's insane, you added f2fs that's exciting, wonder if it supports AOSP because most of n9 users use aosp, some use noblerom
JC1126 said:
Holy that's insane, you added f2fs that's exciting, wonder if it supports AOSP because most of n9 users use aosp, some use noblerom
Click to expand...
Click to collapse
i didnt add anything new, but i found in his fstab, f2fs is ready. i didnt examine the kernel sources yet. this it true for aosp etc also
so in case f2fs/aosp etc was supported in his R154, it should be, i believe...
sorry, but NO f2fs there in his kernel!!
ykkfive said:
i didnt add anything new, but i found in his fstab, f2fs is ready. i didnt examine the kernel sources yet. this it true for aosp etc also
so in case f2fs/aosp etc was supported in his R154, it should be, i believe...
Click to expand...
Click to collapse
that's cool, can't wait to try it out in lineage a11 lol
JC1126 said:
that's cool, can't wait to try it out in lineage a11 lol
Click to expand...
Click to collapse
i just checked the output, there's no f2fs unfortunately but i can add it later after test
ykkfive said:
i just checked the output, there's no f2fs unfortunately
Click to expand...
Click to collapse
that's still fine tbh, not much difference on ext4, good thing is it works on aosp, idk if it'll boot on oneui3.1 because it needs a permissive kernel to boot so yeah
JC1126 said:
that's still fine tbh, not much difference on ext4, good thing is it works on aosp, idk if it'll boot on oneui3.1 because it needs a permissive kernel to boot so yeah
Click to expand...
Click to collapse
tbf i have not built one with both sammy and aosp supported kernel, and i even don't know his kernel supports aosp
for the one ui 3.1 thing, u mean the ported one? i believe he's made it to run on existing kernel so it should be fine. of coz it needs to be tested first
ykkfive said:
tbf i have not built one with both sammy and aosp supported kernel, and i even don't know his kernel supports aosp
for the one ui 3.1 thing, u mean the ported one? i believe he's made it to run on existing kernel so it should be fine. of coz it needs to be tested first
Click to expand...
Click to collapse
Ohh alright then
update 20210618
the ue5 kernel works properly so far, tested on stock rom only due to unable to get a ue5 custom rom atm
will be released soon
thanks a lot
released, closed
Related
THIS OP IS OUTDATED! WIP!
Hello everybody!
You might or might not have already heard of MultiROM, THE multi-boot mod for the Nexus 7. I have recently found it and have decided to port it for our device.
First of all, it is a very initial release now. Though I have tested multiple cases and didn't find any problem except those in the bug list, bugs can arise. Do have a backup! Also, do read through the whole OP and 2nd post! If you don't understand something, rather read again and/or ask!
For more information on how it works and what it does, I suggest that you read the first few posts in the original thread. Those are very detailed and well-written posts that explain MultiROM in general. Installing roms to USB and Ubuntu/Ubuntu Touch of course doesn't work for our device atm.
Installation
The device must not be encrypted!
You need to flash the modified TWRP recovery that has MultiROM extensions. My version is based on the latest sources with gordon0001's device-specific modifications included. You can keep this recovery if you don't want to use MultiROM anymore and you like TWRP, because the MultiROM extensions don't interfere with other functions, even if the boot sector is not injected.
You have to flash a kernel that is capable of Kexec-hardboot. I compiled iodak's v07 CM kernel and official CM kernel with the patch, choose one of them. I have noticed an approx. 3 sec. vibration at boot with iodak, that's why I have included official CM kernel too.
Finally you have to flash MultiROM.
Links
You can find everything at http://d-h.st/users/Adam77Root/?fld_id=22980#files.
MultiROM_TWRP_X3.zip: The modified TWRP recovery from latest sources with gordon0001's device-specific changes and MultiROM support.
CM_kernel_patched.zip and iodakX3_v07CM_patched.zip: Official and iodak CM kernels with Kexec-hardboot patch.
iodakX3_v07_patched.zip: iodak stock kernel with Kexec-hardboot patch.
MultiROM_P880_v12.zip: The actual MultiROM package. Contains the latest version of Trampoline (the init binary of the system) and MultiROM binaries with all the needed device-specific changes. Even Pong works pretty smooth.
x3_hardboot.diff: Kexec-hardboot patch for 3.1.10 kernel.
mrom_p880.patch: Device-specific changes for Trampoline and MultiROM.
ui.xml: UI layout definition for TWRP for 720x1280 screens with MultiROM additions.
Known bugs
Reboot to recovery doesn't work.
USB tab doesn't do anything. This is because USB host mode (OTG) doesn't work on our device. Will reach out to kholk regarding this.
Sometimes in landscape mode, the default selected rom gets booted on the first touch. This is yet to be investigated.
Changelog
14 August 2013: Initial release
Credits
@Tasssadar for MultiROM, Kexec-hardboot for Nexus 7 and his help with debugging and porting
@mkasick for original Kexec-hardboot implementation
@iodak for his kernel
@gordon0001 for the device-specific TWRP modifications
Every custom modification to devices have risks. Flash these at your own risk!
Have fun and enjoy!
General use
Some notes and instructions regarding general use
For now, I have only provided patched 4.2.2 CM kernels. This means, you have to be on CM or CM-based rom with Android version 4.2.2. Don't try it with stock at the moment in any way. It won't work, but is on the to-do list. As Kexec-hardboot will reach out to devs, it will be supported in every rom ultimately.
In the next two examples, I will refer any official, unofficial, or CM-based roms as CM. Keep this in mind.
I use the word 'injected', because MultiROM is actually injected into the boot partition. It works on any kernel that is capable of doing Kexec-hardboot (and if you don't want to use different kernel (i.e. you will use kernel sharing), it will work on unpatched kernels as well).
I may refer to non-shared kernel method as Kexec(-hardboot) method.
Example scenario of multi-booting CM with CM and kernel sharing
You are on CM with MultiROM-capable recovery, patched kernel and MultiROM-injected and you want to install e.g. CarbonRom as second.
Boot into TWRP, navigate to Advanced->MultiROM and select 'Add ROM'. Since the base rom is CM, you can share the same kernel. It will be faster as there will be no hardboot needed.
The installation steps are easy and it doesn't take more time than a normal installation.
Example scenario of multi-booting CM with CM and different kernel
You are on CM with MultiROM-capable recovery, patched kernel and MultiROM-injected and you want to install e.g. CarbonRom as second.
Boot into TWRP, navigate to Advanced->MultiROM and select 'Add ROM'. Select 'Don't share'.
Continue with installation.
Now, since the target kernel (that is installed with the rom) is very likely not patched, you will have to flash one of my linked kernels to that rom. Do this by selecting 'List roms', selecting the desired rom, than 'Flash ZIP' and flashing one of the kernels I have patched.
You can only share the kernels between the same Android version (i.e. stock base->only stock rom can use shared kernel, 4.2 base->only 4.2 rom can use shared kernel, 4.3 base->only 4.3 rom can use shared kernel, etc.), but this is not the case with the Kexec method. Just keep in mind that for example even if your base rom is CM, for a stock secondary rom you have to flash a stock patched kernel.
The build
Some notes about the build
x3_hardboot.diff: This is the Kexec-hardboot patch for the 3.1.10 kernel. Since it is needed for target kernels as well, I would like to reach out in this post to @arararagi, @demetris_I, @iodak, @kholk, @laufersteppenwolf and @Pesach85 (in no particular order, this is how your threads are in order in Original Android Development forum right now). I and fellow users would be grateful if you could include the patch in the kernel so they can be used as both host and target kernels as well. UPDATE: It doesn't reserve one more megabyte before ram_console from now on.
mrom_p880.patch: This contains all the device-specific patches that are needed to get MultiROM booting and working on the P880. It is built on top of the latest git changes as of today. It also contains some comments about multiple devices compatibility, those are reminders for Tasssadar.
ui.xml: UI layout definition for TWRP for 720x1280 screens with MultiROM additions. Needs to be put into TWRPdir/gui/devices/720x1280/res/. The recovery I have created is based on the latest MultiROM TWRP with @gordon0001's device-specific changes.
You can find links to the upstream MultiROM and MultiROM TWRP in the original thread.
Simply incredible!!! :thumbup:thanks a lot man. I always wanted to try dualboot
Sent from my LG-P880 using xda premium
Awaiting the Patched Stock Kernel to dual boot stock and AOSP Good Work man, hopefully @iodak will be able to patch his kernel by today so i can get modding :3
Nice work man! I have also seen hardboot kernels in the N7 section, but got into the hospital then....
But i will include it for sure when i'm back home
Sent from my Nexus 7 using XDA Premium HD app
tnx for your very nice work
how i can flash twrp ?
i want to flash it on cwm but i cant
edite : thats my fault i am so sorry
penguin449 said:
Awaiting the Patched Stock Kernel to dual boot stock and AOSP Good Work man, hopefully @iodak will be able to patch his kernel by today so i can get modding :3
Click to expand...
Click to collapse
If anybody won't be faster, I will provide it tomorrow.
laufersteppenwolf said:
Nice work man! I have also seen hardboot kernels in the N7 section, but got into the hospital then....
But i will include it for sure when i'm back home
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! Take your time, rest and get better!
Sent from my LG-P880
Adam77Root said:
If anybody won't be faster, I will provide it tomorrow.
Sent from my LG-P880
Click to expand...
Click to collapse
Don't get me wrong, i would be more then Happy to do it myself, however till my new PC Arrives i wont be able to use a Linux Distro for some time, if there's a method to do this on windows (Natively, can't even run anything in VM's) then point me in the right direction! Sorry for the inconvenience!
penguin449 said:
Don't get me wrong, i would be more then Happy to do it myself, however till my new PC Arrives i wont be able to use a Linux Distro for some time, if there's a method to do this on windows (Natively, can't even run anything in VM's) then point me in the right direction! Sorry for the inconvenience!
Click to expand...
Click to collapse
I didn't get you wrong buddy. I have no problems with making a stock version, just didn't have time for that today.
Sent from my LG-P880
giantic hack
ohhh well the one big giantic hack is coming to our O4X! that`s very nice
thank you for this port and thank you for your fast work? tomorrow with stock and on saturday with android 4.3 ?
Donation sent
Whaaaaaattt?
Just were browsing N7 forum few days ago and saw MultiROM and thought "Ahh these lucky nexus guys, I wanna have it to! " and here we go hahahah
Sent from my OptimusX4HD using xda app-developers app
how can install rom to ext-sd ?
in next version can we have stock rom and miui rom or other custom rom?
tnx
Hey guys, heres iodak stock kernel with kexec patch: https://www.dropbox.com/s/ko752pu1akuvfzh/iodakX3_v07-realms.zip
Btw i theres a problem with the twrp zip package, im gonna try fastboot flash it. Has anyone had success?
Say Whut?
@Adam77Root, you just made me wanna flashing and flashing and flashing one day before I go into vacation, I will try to get some time today and test it!
Thanks so much!
Afro said:
Say Whut?
Adam77Root, you just made me wanna flashing and flashing and flashing one day before I go into vacation, I will try to get some time today and test it!
Thanks so much!
Click to expand...
Click to collapse
You can flash 10 different roms and play with them over your vacation. Thats what vacations are right?
Hehe @JoinTheRealms , you understand me
Wow, I just saw your Iodak Stock Kernel with Kexec patch, verrry nice, now I can use Stock ROMs, too!
Did you already test it?
JoinTheRealms said:
Donation sent
Click to expand...
Click to collapse
Thanks very much!
m.homauon said:
how can install rom to ext-sd ?
in next version can we have stock rom and miui rom or other custom rom?
tnx
Click to expand...
Click to collapse
You can't install to external SD. It could be modified to allow it, but there would be a huge performance decrease. Literally, roms would be lagging too much.
JoinTheRealms said:
Hey guys, heres iodak stock kernel with kexec patch: https://www.dropbox.com/s/ko752pu1akuvfzh/iodakX3_v07-realms.zip
Btw i theres a problem with the twrp zip package, im gonna try fastboot flash it. Has anyone had success?
Click to expand...
Click to collapse
Just was about to reply to your PM.
What kind of problem is with the zip package?
I will update the first posts in the afternoon.
Afro said:
Hehe @JoinTheRealms , you understand me
Wow, I just saw your Iodak Stock Kernel with Kexec patch, verrry nice, now I can use Stock ROMs, too!
Did you already test it?
Click to expand...
Click to collapse
Nah i couldnt get the twrp package to flash so im gonna try with fastboot. But the kernel works, i just swapped the ramdisk from Adam77roots patched kernel with iodak's stock kernel, it should work though
---------- Post added at 07:21 PM ---------- Previous post was at 07:19 PM ----------
Adam77Root said:
Just was about to reply to your PM.
What kind of problem is with the zip package?
I will update the first posts in the afternoon.
Click to expand...
Click to collapse
My twrp failed to flash your twrp.zip package, most likely something on my end though, no one else has reported issues
Featuring a new cpufreq interface, AbyssplugV2, intelliplug and a whole host of new additions that are not available in any other kernel for the x3.
Among them are updates only found in this kernel, saner defaults via config, better optimizations for the actual code and a rewritten version of devfreq.
It also have an updated baseband configuration and built in rather than to keep a module as it makes no sense to have a vital function as a module.
https://bitbucket.org/mourta/liquid_kernel_lge_p880-stable/
Kernel: http://www.mediafire.com/download/viy5a3dtaccd0gm/mourta-stable-08-23.zip
If there is a request for it i also have a ROM available based on grouper blobs, AD optimizations and a build around this kernel with a new dev tree.
For kernel install, it's anykernel, you can install it on any custom ROM, for stock and the lastest updates you will have to head over to Modaco and my original thread.
Note that this is a one time release, if you like it you'll have to head over to modaco to get updates.
it should be noted that the recommended settings is using intelliplug (you may need to use kernel tweaker or trickster mod for that if you're not running my ROM, and abyssplugv2, i also recommend ROW for a sheduler and Westwood for your congestion handling.
Note that you can now overclock to any frequency and it will feed the GPU chip with the needed volatage, this is great for cooking a roast beef but not for any practical use.
Quadrant scores are 8k and the last Antutu was at 16487, no overclocking but you won't reach that without using my ROM.
And with that... i'm done.
Thanks to the IODAK, Fransico, Adam77Root, Faux123 and others that provided code and/or input.
Oh, what I see here? The awesome kernel I'm testing with @ottomanhero and lucaarx and the great dev and friend @IcanhasLG coming back on xda? Let's rock hard&heavy, right now!
peppethustra said:
Oh, what I see here? The awesome kernel I'm testing with @ottomanhero and lucaarx and the great dev and friend @IcanhasLG coming back on xda? Let's rock hard&heavy, right now!
Click to expand...
Click to collapse
We'll see how this goes.
Thankfully i am in touch with a mod that will keep this drama free,
And for anyone wondering, peppethustra is head of my testing crew, you get stable releases because of them.
It should be noted that i'm still going to prefer the forum that greeted me over the one that shunned me from the get go, updates here will be sporadic at best but on time on the other forum.
It's great to see your work on XDA.Now everyone can experience your awesome work
P.S. you can find neccessary links in my signature
Great work, running your kernel now.
But Iodak was not updated since long ago and its sources does not contain many great fixes from cm11 kernel.
Thats why Demetris relased Cyodak kernel in Android development section. It's Iodak brought up to date with latest cm 11 kernel .
It would great to see Muorta Kernel based on Cyodak instead of old Iodak. We would have your exclusive features with up to date cm11 kernel upgrades. But maybe you already upgraded iodak's source, let us know
FunkyRasta said:
Great work, running your kernel now.
But Iodak was not updated since long ago and its sources does not contain many great fixes from cm11 kernel.
Thats why Demetris relased Cyodak kernel in Android development section. It's Iodak brought up to date with latest cm 11 kernel .
It would great to see Muorta Kernel based on Cyodak instead of old Iodak. We would have your exclusive features with up to date cm11 kernel upgrades. But maybe you already upgraded iodak's source, let us know
Click to expand...
Click to collapse
Obviously, the real necessary updated patches have been implemented yet ("continuation" means this, too), so it's not necessary nor in Mourta's plans to base it on cyodak (which really isn't the only way to find updated code for our device)
peppethustra said:
Obviously, the real necessary updated patches have been implemented yet ("continuation" means this, too), so it's not necessary nor in Mourta's plans to base it on cyodak (which really isn't the only way to find updated code for our device)
Click to expand...
Click to collapse
That's what I wanted to know, as OP didn't explicitly stated it. Thanks
FunkyRasta said:
That's what I wanted to know, as OP didn't explicitly stated it. Thanks
Click to expand...
Click to collapse
Outdated sources never are a good base for developing a fresh new kernel or ROM, if there is a new compatible code implementation ready to be merged into the code That's the first thing a good developer checks (and if you can, look at Mourta's bitbucket linked in the OP to view his commits, there will be all the principal news about new code implementations)
Tried this but I loose my modem every now and then and the screen won't wake sometimes.
baxtex said:
Tried this but I loose my modem every now and then and the screen won't wake sometimes.
Click to expand...
Click to collapse
Go to Modaco and find newer version (26/8/2014) . It will resolve problems like yours
Okay will do.
How's the deep sleep ?
Written from my Optimus 4X powered by Omni 4.4
LGaljo said:
Go to Modaco and find newer version (26/8/2014) . It will resolve problems like yours
Click to expand...
Click to collapse
this version, according to trickster mod, does not use deep sleep state and still screen won't wake up sometimes. so i dropped it for now.
greetings
peter
peter_altherr said:
this version, according to trickster mod, does not use deep sleep state and still screen won't wake up sometimes. so i dropped it for now.
greetings
peter
Click to expand...
Click to collapse
Can you give more info about your ROM, kernel settings, setup etc. and provide a logcat if possible? That's a rare issue you're having there.I've used my phone for 20 hours now, (%3 battery left) and it slept for about 15 hours, same version.
I suggest you to try flashing the kernel twice.I had such problems with iodak kernel back in the time and flashing it twice had fixed the deep sleep issue.
ottomanhero said:
Can you give more info about your ROM, kernel settings, setup etc. and provide a logcat if possible? That's a rare issue you're having there.I've used my phone for 20 hours now, (%3 battery left) and it slept for about 15 hours, same version.
I suggest you to try flashing the kernel twice.I had such problems with iodak kernel back in the time and flashing it twice had fixed the deep sleep issue.
Click to expand...
Click to collapse
+1
@peter_altherr And more important thing: have you at least wiped cache and dalvik before flashing the kernel? If yes, try wiping system partition too (no factory reset, you can leave /data partiton intact) then reflash ROM, gapps and kernel, and see how it goes..wait 3 or 4 minutes before trying to wake up device, after the first boot, and deep sleep would start without problems
I have tried the 26/8 version but that still gives me RIL problems, I get no signal whatsoever. I cannot grab a logcat as I need my phone to work right now but I'm Running latest beanstalk version.
baxtex said:
I have tried the 26/8 version but that still gives me RIL problems, I get no signal whatsoever. I cannot grab a logcat as I need my phone to work right now but I'm Running latest beanstalk version.
Click to expand...
Click to collapse
Wait for next version, great changes will come even about this issue
@peter_altherr you should unplug it from charger and try unplugged.
when charging cpu never reaching deepsleep.
@ whoever had freeze/sod problems with last kernel version: a new fixed release has been uploaded (it's a minor release: reverted GPU OC, which was causing the problem). Check official thread for the download link
my phone does not see SD card with 0902
and yes im 100% sure its kernel problem....recovery sees my sd, and so iodak kernel
Flashable fix for call audio that is kernel independent and will patch International based ROMS to work on your T/W8 variant.
You still need a kernel that is T/W8 compatible flashed for this patch to work.
Code:
You can get it [URL="https://www.androidfilehost.com/?fid=23991606952614440"][B]Here[/B][/URL] for 5.0.2
And you can get it [URL="https://www.androidfilehost.com/?fid=24052804347831878"]Here[/URL] for 5.1.1
Updated 5.1.1 package to BOI6
This patch can also be implemented by ROM builders who wish to build a F based rom for their T or W8 devices Just remember to give credit where it is due. This was a bigger pain in the butt to track down then it appears.
Let me know if you find any issues that may be relative to the fix. Tested and working by my self and a few others.
This patch can also be implemented by ROM builders who wish to build a F based rom for their T or W8 devices. In that regard it *should* also work on Edge variants as well.
Rom builders: you can also use this to build a truly universal ROM one flash to cover it all.
Download my kernel and examine its structure. specificallt look at the scripts that probe device variant and then copy the required files and kernel. You can adapt this to work the other way . But always run it *at the end* of the installation script so anything it patches does not get overwritten by your usual installer code
g.lewarne said:
This patch can also be implemented by ROM builders who wish to build a F based rom for their T or W8 devices. In that regard it *should* also work on Edge variants as well.
Click to expand...
Click to collapse
Ah yes i should mention that!
this patch goes hand in hand with the above as well. will fix GPS with AOE3 based kernels >> https://www.androidfilehost.com/?fid=23991606952608763
again feel free to rip / implement it as you see fit
Will this work on the AT&T G920A ?
Thanks!
rectangle said:
Will this work on the AT&T G920A ?
Thanks!
Click to expand...
Click to collapse
It should, as I was able to flash an A rom and call audio worked. so they audio bits appear to be the same.
-Mr. X- said:
It should, as I was able to flash an A rom and call audio worked. so they audio bits appear to be the same.
Click to expand...
Click to collapse
Do you mean you flashed an F rom on A device?
Thank you.
rectangle said:
Do you mean you flashed an F rom on A device?
Thank you.
Click to expand...
Click to collapse
I i mean I've flashed a A rom on my W* and didn't have to change anything to get the audio working. therefore it uses the same audio bits.
Thabks for yoyr hard work on this! Not working on my s6 tmobile after flashing Alliance Rom.
sumguyatvt1128 said:
Thabks for yoyr hard work on this! Not working on my s6 tmobile after flashing Alliance Rom.
Click to expand...
Click to collapse
What kernel are you on? You still need a kernel that is T/W8 compatible flashed for this patch to work. . I thought i had mentioned that, but it was in a different thread sorry.
Small update, to latest AOE1 bits. same link.
Works great tried a rom earlier. Know any ways to port wifi calling to an international rom tho?
I get really ****ty service at home.
Maqical said:
Works great tried a rom earlier. Know any ways to port wifi calling to an international rom tho?
I get really ****ty service at home.
Click to expand...
Click to collapse
That is up to the ROM guys.
Maqical said:
Works great tried a rom earlier. Know any ways to port wifi calling to an international rom tho?
I get really ****ty service at home.
Click to expand...
Click to collapse
i could probably get it working if my carrier wasn't archaic and supported it them selves lol sorry i can ask a few of my other dev biddies and get some heads together possibly.
g.lewarne said:
That is up to the ROM guys.
Everyone.....I may have misses a variant , I thought I got them all. So there is also an A for att?
I'll have to patch up the kernel for that we should also be able to support it.
Click to expand...
Click to collapse
Gav, the A is a T/W8 variant but has a locked bootloader. don't waste your time they cannot flash kernels. But thy can flash roms and my fix will work since they will be on a stock kernel. well *work* hopefully lol
Edit: Never mind Google+ was keeping the device from sleeping. Please disregard.
NJGSII said:
Ive noticed that flashing either the full kernel with the fix or just the fix itself ontop of ktoonez's kernel, my device doesnt enter deep sleep. I did a test where i just reflashed ktoonez's kernel without the fix and sure enough the device enters deep sleep again.
In better battery stats Android is at the top of Alarms with android.content.syncmanager.SYNC_ALARM having all the wakeups.
Click to expand...
Click to collapse
I'd try chearing caches possible. as i have been flashing non stop for the past 12 days on the simpl kernel and my fix and have always verified deep sleep is working and it is as it should.
-Mr. X- said:
I'd try chearing caches possible. as i have been flashing non stop for the past 12 days on the simpl kernel and my fix and have always verified deep sleep is working and it is as it should.
Click to expand...
Click to collapse
True. Found out what the problem was and it had nothing to do with this. You guys are good!
I've tried this on the G925T (The TMo S6 Edge), but it didn't seem to work with ktoonz kernel. Not complaining, just letting you know. Thanks for your hard work and assistance (both of you).
*Edit*
Installed Simpl Kernel with this mod and it worked. I'm using XtreStoLite ROM, but didn't work with ktoonz at all (with the fix). Flashing Simpl with with the fix worked just fine. Still need to get used to the Intl ROM.
My apologies beforehand, would you mind clarifying what this patch allows us to do. Can we patch Roms from other providers, I'm just a little confused.
Hello,
As some of you already notice I'm working on AOSPA 7.1.x for Nexus 5. When this project becomes stable AOSPA Team will consider about supporting it officially with me as maintainer of course.
So, I will share with you, my progress so far.
To-do List:
Fix audio effects problem
Rework device repo [need to cleanup]
Fix camera not saving photos
Device specific features:
Switch from mpdecision to autosmp (better battery life)
cpu-boost optimizations
implement task's adj rbtree (LMK improvement)
disabled cpu retention (hh bugfix)
vsync workaround (hh bugfix)
This looks very promising!
this is CAF? can i instal custom kernel like franco kernel?
irfanhutomo said:
this is CAF? can i instal custom kernel like franco kernel?
Click to expand...
Click to collapse
It's caf based like LineageOS. But no, you can't install franco kernel. only the ones who supports caf roms.
YES, YES! It looks really tempting. Right now, a CAF base is much better for the Nexus 5 than an Aosp one. It's very nice to see something new based on CAF. Hope you will continue this project. Thanks and good luck.
I need someone who has Nexus 5 as second device to test and generate logs when I need as I'm using my n5 as main phone and have to backup and restore every single time.
marcomarinho said:
I need someone who has Nexus 5 as second device to test and generate logs when I need as I'm using my n5 as main phone and have to backup and restore every single time.
Click to expand...
Click to collapse
I can help you. Can't wait for this to be complete.
marcomarinho said:
I need someone who has Nexus 5 as second device to test and generate logs when I need as I'm using my n5 as main phone and have to backup and restore every single time.
Click to expand...
Click to collapse
I just got my 6P screen replaced today so my N5 is once again a backup. I know how to pull logs. If you need a tester I'm all in, send me a PM.
A tester here, as soon as it's ready.
Can't wait :good: good job :highfive:
I've been testing this for Marco during the past 2 weeks and everything works great. You guys have a reason to be excited and I know you won't be disappointed once it is released, which should be soon. I want to thank Marco for letting me be a part of his team and I praise all the hard work he has put into the ROM so it runs perfectly on our device.
I also want to test it, has someone have the latest build link? PM me, thanks
esemyuron said:
I also want to test it, has someone have the latest build link? PM me, thanks
Click to expand...
Click to collapse
The ROM is stable already, we don't need any testers. you have to wait until the official release :fingers-crossed:
marcomarinho said:
The ROM is stable already, we don't need any testers. you have to wait until the official release :fingers-crossed:
Click to expand...
Click to collapse
cant wait, cant wait thanks
Hey! I read in the Dark ROM CAF threads that a CAF ROM won't work if the screen is replaced by a non-OEM screen. Since PA is based off CAF now, I suppose it will be true for PA too? Can anyone confirm and is yes, is there a workaround or something?
prateektaneja said:
Hey! I read in the Dark ROM CAF threads that a CAF ROM won't work if the screen is replaced by a non-OEM screen. Since PA is based off CAF now, I suppose it will be true for PA too? Can anyone confirm and is yes, is there a workaround or something?
Click to expand...
Click to collapse
Yes. The fact is true.
Do we need to flash CAF recovery before installing this caf based rom ?
Thanks for all the hard work you guys, this rom has been one of the bests in the history of custom roms and this is a great comeback.
Is it going to be released this week? once again thanks, can't even wait!
marcomarinho said:
The ROM is stable already, we don't need any testers. you have to wait until the official release :fingers-crossed:
Click to expand...
Click to collapse
You know if there'll be monthly security updates? I've loved PA for PIE and i'd install it if something like that'll be available
Sent from my Nexus 5 using Tapatalk
Will it's stock kernel be true [email protected]
The phone been released for 2 months now and yet not even an official TWRP recovery. not a single custom rom too.
i've been looking at Mi 8 forums and it has much better support. at least they have pixel experience rom
do you think it's still early for custom roms to be released or this device really has poor support?
Give it some time. Mi 8 and Mix 3 also took a while before the first ROM came.
SirTAVARES said:
then you have time to learn how to build for us
Click to expand...
Click to collapse
i am sorry i didn't mean to be rude. i am just asking cause i've been waiting so long for a pixel rom and i was kinda concerned. the mi 9 would shine with it.
It took almost 7 months for custom roms to be usable on OnePlus 6
Just chill
I think sm8150 source code just got released not even a week ago, now developers get their first real look and can start working on builds. Really tho, unless the phone you are looking at already has strong developer support don't assume one without it will get it.
Just use GSIs meanwhile? They work very well...
Mohammed779 said:
Just use GSIs meanwhile? They work very well...
Click to expand...
Click to collapse
I think that depends on your individual set up. I use TMobile and have 2 sims, 1 for work and one for personal, granted I've only tried floko but I can't use them both with LTE selected, only manage to get edge working. When switching to LTE, I get constant disconnects every few seconds. Sms only seems to work properly with GSM as well. Might be a TMobile US issue, dual SIM issue or dual SIM on same network. Not real sure.
The Mi9 is out for months. Normal whene coming custom roms this comes in the first month. I think we will not see any custom rom now but Miui is also good with custom launcher. I missing nothing.
The device doesn't have "really poor support", the interest and capable people are and will be there. The problem is just the drop of sources. This was to be expected when you have one of the first devices with a new SD SoC. Threads like this really add to the increasing stupidness on XDA.
Sources are out for weeks.
Hot-Proton said:
Sources are out for weeks.
Click to expand...
Click to collapse
You clearly have no idea what you're talking about. Xiaomi kernel source code has been out indeed.. but go look at CAF
CrazyBeaver2377 said:
The device doesn't have "really poor support", the interest and capable people are and will be there. The problem is just the drop of sources. This was to be expected when you have one of the first devices with a new SD SoC. Threads like this really add to the increasing stupidness on XDA.
Click to expand...
Click to collapse
Thanks for clarifying this for all of us "not so much into all technical details" people. I can understand your frustration, but I think for most people eagerly waiting for something else then MIUI, (who are not willing or knowing where to start with GSI Roms) its good to have one of these threads out there (maybe even pinned on top).
As you are stating it's only a matter of time, and that is good to know for all of us. It would also be great to have some DEVs that are planning on building for the MI 9 in such a thread to even built more confidence.
Just a word from another Dutchmen. Have a good weekend y'all! And try (just as I am about to) not to check XDA MI 9 forum every 6 hours every day. Just wait some weeks. Things are probably about to become very Pixely soon.
I've already dumped an obscene amount of time into this device, we have only had caf source for a couple days. It's a brand new soc no one is building working roms for it yet on any device. System as root has caused a lot of issues as well. Up to this point my work has been focused on the kernel and recovery and now I have lineage building with the new hals and the kernel updated to use them and ramoops working so I can actually debug init. It's not as easy as we make it look I'm already a couple hundred hours in and I work for free
randomblame said:
I've already dumped an obscene amount of time into this device, we have only had caf source for a couple days. It's a brand new soc no one is building working roms for it yet on any device. System as root has caused a lot of issues as well. Up to this point my work has been focused on the kernel and recovery and now I have lineage building with the new hals and the kernel updated to use them and ramoops working so I can actually debug init. It's not as easy as we make it look I'm already a couple hundred hours in and I work for free
Click to expand...
Click to collapse
Thanks Kelsi For your hard work.
And don't let these idiots pressure you!
Don't they get you work for FREE and you probably have
a life also Lol.
randomblame said:
I've already dumped an obscene amount of time into this device, we have only had caf source for a couple days. It's a brand new soc no one is building working roms for it yet on any device. System as root has caused a lot of issues as well. Up to this point my work has been focused on the kernel and recovery and now I have lineage building with the new hals and the kernel updated to use them and ramoops working so I can actually debug init. It's not as easy as we make it look I'm already a couple hundred hours in and I work for free
Click to expand...
Click to collapse
You are making a really good work.
Unfortunately i have not the device so i can't make a good work fast, maybe in another month i will fix recovery
mauronofrio said:
You are making a really good work.
Unfortunately i have not the device so i can't make a good work fast, maybe in another month i will fix recovery
Click to expand...
Click to collapse
Yeah it's good enough for now for my purposes but needs improvement. The big question is how do we make it compatible across different dtbos
randomblame said:
Yeah it's good enough for now for my purposes but needs improvement. The big question is how do we make it compatible across different dtbos
Click to expand...
Click to collapse
Can't you include a dtbo in the rom zip?
Can i ask you if i can use your kernel in my TWRP?
mauronofrio said:
Can't you include a dtbo in the rom zip?
Can i ask you if i can use your kernel in my TWRP?
Click to expand...
Click to collapse
You can use my kernel of course, pstore works with it so it's actually possible to debug init with some effort pressing both volume buttons and ai button sends a soft reset to recovery signal which is the only way to keep the ramoops info in memory. The problem is if you flash a dtbo then the boot.img may be incompatible. Recovery boot and dtbo all have to be matching unless there's a way to make recovery work off the existing kernel in /boot
I cant understand the Problem here. Just Look at phhusson the god of devs for GSIs. The Day He posted on xda that his New Main device is the mi9 was the Day my next device was also the mi9 (just arrived today). His aosp gsi is working on mi9 for weeks with just some realy small Bugs and i think it wont last long until He has fixed all Bugs. And from that Day on we will have every custom Rom thats available as a gsi with their next Update.
https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Mi-9
https://github.com/phhusson/treble_experimentations/releases
https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
I dont like gsi. For flashing need a PC. Gsi is for me not a custom rom. I need a custom rom what i can flash with twrp, without pc.