Related
Hi,
I installed 2 weeks ago the latest Beanstalk 4.4.4010 CM-based and I really liked it, it is a very nice ROM and increased the life and performance of my phone by a lot.
At the beginning everything was fine, but now after 2 weeks I am having again the same network problems (losing connectivity, not being able to recover signal, and so on) that I had with my old CM ROM.
After reading a bit around in the forum, I found that there is this RIL change solution http://forum.xda-developers.com/showthread.php?t=2496075
But since this is a bit older, I don't know if it has been already implemented or not in the recent Beanstalk updates or if I still have to do it. And also if this only works with the P880-dev based ROMs or also with the CM based ones. It is difficult to say when one has to read so many threads.
Also an user uploaded a flashable zip fix of the RIL for the AD version. Does this mean that I can flash the P880-dev based ROM with AD and then just flash this zip and would avoid having to do the procedure of the above tutorial?
Is there another flashable alternative for me?
I also read somewhere that NamelessRom wasn't having this issue, so do you recommend to switch?
Thanks,
SC.
there are still several versions of RIL; i recommend you try a few of them till you find out the one that works.
the zip that was made for the AD version of rom works only and only with that specific rom, made on that specific date. any rom that was built after (or before) needs to have different flashable zip.
i do recommend you try nameless rom first (take a backup of beanstalk). take it for a spin for a few hours/days and see if you have any network issues. if you do not, you can extract RIL from nameless rom & implement it in beanstalk. good luck
Flying_Bear said:
there are still several versions of RIL; i recommend you try a few of them till you find out the one that works.
i do recommend you try nameless rom first (take a backup of beanstalk). take it for a spin for a few hours/days and see if you have any network issues. if you do not, you can extract RIL from nameless rom & implement it in beanstalk. good luck
Click to expand...
Click to collapse
:good:
Thanks, then I'll try my luck with Nameless. I hope I will not miss it much.
There isn't yet something like dual booting in Android, no?
Cheers,
S
There is for our device, search for twrp multirom. Its a bit of a hassle to set up properly thoguh
Hi,
since the official maintainer "solk2" for the GT-I9506 moved on to CM12 before providing a final build incorporating his latest fixes I decided to make my own builds.
According to my personal experience the battery life has vastly improved. In particular the power consumption while the display is off has decreased substantially. Solk2 has apparently fixed some issues with the kernel so the battery issues are gone. So for everyone not yet willing to transition to CM12 (in my case inter alia due to the currently unstable state and the lack of a stable Xposed framework in Android 5) this might be a good alternative.
I will gladly share my unofficial ROMs, however I would need someone to host the files in order to do that. If anyone would be so kind as to host ROMs please let me know.
If any relevant code changes to CM11 will appear I will most certainly compile a new version.
* IMPORTANT *
Please note that these builds are based on nothing else than the unchanged official code from Cyanogenmod, solk2 and others. So every credit goes to them.
I will not and cannot make any changes to the code. The only thing I can do and will do is build a ROM thereof in case some interesting fixes etc. appear. However, since CM11 is becoming outdated there will most probably not be a lot of changes to come.
Also, it should be understood that I take no responsibilities whatsoever if anything goes wrong when you install the ROM. Like the original ROM this is completely at your own risk!
However, you can expect that any ROM I share has been installed on my own GT-I9506 (with Samsung firmware of 4.4.2 nordic countries) and runs without obvious issues. Your mileage may vary.
Here is the current version, including the CM-11.0 code base up to http://review.cyanogenmod.org/#/c/97688/ :
https://www.mediafire.com/folder/j0jynk3en95j5n1,soag9jcmrcajdhq/shared
* Note *
At least some of the issues with solk2's latest official builds were apparently caused by preceding changes to the kernel code. My builds use the latest code base of February 16 incorporating solk2's latest fixes (see https://github.com/CyanogenMod/android_kernel_samsung_ks01lte/commits/cm-11.0).
Unless solk2 will make further changes to the kernel (which I doubt as he has turned his attention to CM-12) the changes in my builds are only related to merged changes in the official Cyanogenmod code for CM-11.0 (see http://review.cyanogenmod.org/#/q/status:merged+branch:+cm-11.0). In other words the kernel will remain the same, even if the build date thereof may change.
Thank You. Perfect rom. in 2015-05-20 mms is working by default I have not find any bugs.
I'm on arter97 CM12.1 and I'd like to try this one. I can imagine a such install procedure:
-flash kk stock firmware (CNJ1 nordic) from odin
-reboot
-flash custom recovery from odin
-reboot
-flash your rom from custom recovery
Is that right?
ilfavi said:
I'm on arter97 CM12.1 and I'd like to try this one. I can imagine a such install procedure:
-flash kk stock firmware (CNJ1 nordic) from odin
-reboot
-flash custom recovery from odin
-reboot
-flash your rom from custom recovery
Is that right?
Click to expand...
Click to collapse
You do not need flash any stock. Just flash TWRP, make full wipe and flash this rom + gapps
Why is this rom so ignored? I flashed it a few days ago and I find it's great. Very very fast and absolutely rock solid. No bugs, no fc, no reboots.
ilfavi said:
Why is this rom so ignored? I flashed it a few days ago and I find it's great. Very very fast and absolutely rock solid. No bugs, no fc, no reboots.
Click to expand...
Click to collapse
I do not know how many have installed this ROM (anyone having done so please leave a reply here).
I see only a very limited number of reasons to transition to a new version of a ROM or Android in general:
1. If the new version provides functionality that I want or need (and material design isn't one of those); or
2. If the new version fixes a bug or security flaw (there is none that I know of).
At the moment CM-12 does not fulfill any of these criteria, instead I would lose the solidly working Xposed framework for an alpha version thereof.
I'm not intending to advertise this ROM, inter alia because the only thing I did was build it, so the credits should still go to solk2. But if anyone hears that someone has issues with the latest "official" version of CM-11, please direct them here.
HI !
This rom is awsome (smooth fast and stable) but is lacking of functionality...
@NeuDLi do you think I can use this rom for patchrom miui v5 or v6 on ? (as base)
And thanks for your work !
3lambda said:
HI !
This rom is awsome (smooth fast and stable) but is lacking of functionality...
@NeuDLi do you think I can use this rom for patchrom miui v5 or v6 on ? (as base)
Click to expand...
Click to collapse
I suppose so... Since it does use the official CM sources, just go ahead and try it.
Thanks for the reply
Do you have some knowledge on building stuff ? (via linux command, problem etc)
What should happen if I update via OTA as it ask me to do?
edit: I realized that the updates suggested are cm12 so can be ignored
I had one strange bug in this rom (maybe reason was in gapps): Go to SMS app, push new and write name in address line from above: phone getting list of contacts to chise. You choisew one and see wrong number (without region code) in address line.
If you push on contacts button and choise contacts here everything will be ok.
NeuDLi said:
I do not know how many have installed this ROM (anyone having done so please leave a reply here).
I see only a very limited number of reasons to transition to a new version of a ROM or Android in general:
1. If the new version provides functionality that I want or need (and material design isn't one of those); or
2. If the new version fixes a bug or security flaw (there is none that I know of).
At the moment CM-12 does not fulfill any of these criteria, instead I would lose the solidly working Xposed framework for an alpha version thereof.
I'm not intending to advertise this ROM, inter alia because the only thing I did was build it, so the credits should still go to solk2. But if anyone hears that someone has issues with the latest "official" version of CM-11, please direct them here.
Click to expand...
Click to collapse
Do you know to make compatible with this ROM, the Arter97 kernel?
Alexyerga said:
Do you know to make compatible with this ROM, the Arter97 kernel?
Click to expand...
Click to collapse
No, as stated I'm not a coder. And also why use Arter97 kernel anyway?
NeuDLi said:
No, as stated I'm not a coder. And also why use Arter97 kernel anyway?
Click to expand...
Click to collapse
Because the Solk2 kernel causes random reboots sometimes
Alexyerga said:
Because the Solk2 kernel causes random reboots sometimes
Click to expand...
Click to collapse
Then maybe you should ask Arter97 what's different in his kernel... Without any hint what difference causes this no-one has a realistic chance to find out. Or ask him to adapt his kernel to CM-based ROMs. I didn't know that his kernel does not work with CM, is that so?
Also, on my S4 I do not have frequent reboots. However, I once activate the advanced option "kernel samepage merging" and then had two reboots in 1-2 days. After resetting to deactivated no more reboots since about 2 weeks... Worth a try to check.
I would like to help, but I simply do not have anywhere near the experience and knowledge to find a kernel bug that apparently solk has not found himself!
NeuDLi said:
Then maybe you should ask Arter97 what's different in his kernel... Without any hint what difference causes this no-one has a realistic chance to find out. Or ask him to adapt his kernel to CM-based ROMs. I didn't know that his kernel does not work with CM, is that so?
Also, on my S4 I do not have frequent reboots. However, I once activate the advanced option "kernel samepage merging" and then had two reboots in 1-2 days. After resetting to deactivated no more reboots since about 2 weeks... Worth a try to check.
I would like to help, but I simply do not have anywhere near the experience and knowledge to find a kernel bug that apparently solk has not found himself!
Click to expand...
Click to collapse
Last time ago arter's kernel was compatible but he removed the support because he didn't have time to maintain two kernels.
Thanks anyway NeuDLi, i will tray the option "kernel samepage merging", it cames activated or deactivated by default? Because when I tried, I didn't change any option
Alexyerga said:
i will tray the option "kernel samepage merging", it cames activated or deactivated by default? Because when I tried, I didn't change any option
Click to expand...
Click to collapse
Well, another problem... I'm not sure if it is a bug in settings.apk or only in connection with our device. However, when you check the option is always ON, and upon leaving the settings.apk it will always return to being ON. So at least I can say that turning if OFF cannot have had an effect because it was never turned OFF.
However, I will try with KSM disabled now. For the time being you can manually disable it and lock this state (well at least until next reboot) by doing the following in an adb session or the terminal:
echo 0 > /sys/kernel/mm/ksm/run
chmod 444 /sys/kernel/mm/ksm/run
Another way would be to recompile the kernel with the option disabled. It would be far better to fix the issue in settings.apk. However, to file a bug report one would have to check if the behaviour is the same in the official nightlies... I read that someone reported this as a bug for the Oneplus One, but it was never resolved.
As an somewhat veteran in other xda-like forums, I advertised link to neudlis reply with his/her first build because it has been rock stable and fast. With my I9506 nordic.
No other customs have been this solid for 3 weeks straight, and I have been trying roms since december !
iBuu said:
As an somewhat veteran in other xda-like forums, I advertised link to neudlis reply with his/her first build because it has been rock stable and fast. With my I9506 nordic.
No other customs have been this solid for 3 weeks straight, and I have been trying roms since december !
Click to expand...
Click to collapse
Although I cannot often enough remind everyone that I did not provide or change any code but just build it that's still not too bad for the first build of a guy not that much into coding .
After a weekend with not much use but some hours of listening to audio books I was left with 21% charge after more than 3 days (see attached screenshot). That's just awesome! So I believe it can safely be said that any power consumption bug was resolved by solk2's latest patches to the kernel.
Also I believe that turning off kernel samepage merging might have helped additionally, so I encourage everyone to try it as well (see above post for manual way to turn it off as bug in settings.apk won't let you otherwise). In my opinion this option should default to off as it is said to be potentially unstable and the I9506 surely has enough RAM not to need it. So I prefer to lessen CPU load for longer battery life in exchange for potentially increased RAM occupation.
My MI3w is currently on MIUI 7 5.12.4 KK Dev ROM & I want to upgrade.
I need the basics to be reliably working, Camera, Calls, GPS, Gaming, Battery-life, etc.
So what is more stable/bugfree, an MM or lollipop rom? From what I have read, it seems like the marshmallow roms are fairly good at this point so I have been leaning towards either CM13 or Ivan's AOSP or possibly BeanStalk, any recommendations?
I have read a couple of posts that say the gaming & camera performance are better on lollipop, is that true?
I am also a bit confused on the whole partition resizing thing... Does that need to be done to use MM roms or can I flash as is? I read some things that seem to say CM13 works with the stock partition setup & Ivan's/MIUI MM requires expanding it, is that correct?
Also, I am still on the stock recovery so TWRP or CWM?
And can anyone suggest the best guide for upgrading from MIUI 7 KK? Some guides seem to assume you are already on a newer rom with custom recovery installed. And some seem to do the partition expansion while others don't mention it (I would prefer not to if it is not necessary).
Beanstalk 20-Jan build is pretty stable and can be used as daily driver.
AOSP/CAF based MM ROMs are the best. Ivan's one is good too. Though among all the ROMs I found CAF, CandySix great
Haven't used Ivan's rom but Beanstalk and Mokee latest build are pretty good.
Nintoad said:
My MI3w is currently on MIUI 7 5.12.4 KK Dev ROM & I want to upgrade.
I need the basics to be reliably working, Camera, Calls, GPS, Gaming, Battery-life, etc.
So what is more stable/bugfree, an MM or lollipop rom? From what I have read, it seems like the marshmallow roms are fairly good at this point so I have been leaning towards either CM13 or Ivan's AOSP or possibly BeanStalk, any recommendations?
I have read a couple of posts that say the gaming & camera performance are better on lollipop, is that true?
I am also a bit confused on the whole partition resizing thing... Does that need to be done to use MM roms or can I flash as is? I read some things that seem to say CM13 works with the stock partition setup & Ivan's/MIUI MM requires expanding it, is that correct?
Also, I am still on the stock recovery so TWRP or CWM?
And can anyone suggest the best guide for upgrading from MIUI 7 KK? Some guides seem to assume you are already on a newer rom with custom recovery installed. And some seem to do the partition expansion while others don't mention it (I would prefer not to if it is not necessary).
Click to expand...
Click to collapse
1. from the MM roms I've seen, the base is already quite stable and matured, so the basics work on a decent maturity level. (I wouldn't know about the gaming performance though). In general the camera performance should not differ whether you use LP or MM, you can use the camera libs and apps with the same hardware.
I could recommend CAF, Slimbit, Beanstalk as daily drivers. The choice depends more on the additional features you would like to have. CAF and Slimbit has only the AOSP features, so I use Gravitybox to add what I like. But that's just personal preference.
2. the resizing: many roms need the "resized" system partitions already, the MM MIUI/ Ivan's MM AOSP need the "merged" partitions, an important difference in the update procedure.
I'd suggest you update to MIUI 7 5.12.17 CN Dev ROM, this should merge the partitions (better make a backup first). After that you can install any rom or recovery you prefer. (see also http://forum.xda-developers.com/xiaomi-mi-3/general/mi3-4-marshmallow-6-0-5-12-24-alpha-t3280037)
Thanks for all the info! I did not know that installing MIUI MM rom would take care of the partition merging for me. All I have to do is just flash it in recovery in the usual way? I decided to just go ahead and dive in last night & installed TWRP & the latest CM13 nightly. But the main reason I choose CM13 was its support for the older partition setup.
I am stupid happy with the speed & snappiness vs MIUI KK, night & day difference is not strong enough, day & the center of a black hole is a more fitting contrast. The only issue I am having is the camera. Google camera is a buggy unusable mess, it constantly is freezing up and most features like lens blur just cause it to crash, is it the same on other MM roms? Or maybe does it have something to do with me having to flash the gapps pico pack because it is all that would fit with unmerged partitions?
I am also not a fan of the CM13 native camera app, it does not seem to have a way adjust the preview size from 16:9 so you don't know what is actually in frame before you snap. I use my phone for pics & video a lot & I have read some things saying that the camera quality on MIUI is a lot better than other roms, how true is that?
I haven't found a all in one solution for the camera, typically I use "a better camera" or "lenovo super camera" (http://forum.xda-developers.com/showthread.php?t=2665714)
Nintoad said:
Thanks for all the info! I did not know that installing MIUI MM rom would take care of the partition merging for me. All I have to do is just flash it in recovery in the usual way? I decided to just go ahead and dive in last night & installed TWRP & the latest CM13 nightly. But the main reason I choose CM13 was its support for the older partition setup.
I am stupid happy with the speed & snappiness vs MIUI KK, night & day difference is not strong enough, day & the center of a black hole is a more fitting contrast. The only issue I am having is the camera. Google camera is a buggy unusable mess, it constantly is freezing up and most features like lens blur just cause it to crash, is it the same on other MM roms? Or maybe does it have something to do with me having to flash the gapps pico pack because it is all that would fit with unmerged partitions?
I am also not a fan of the CM13 native camera app, it does not seem to have a way adjust the preview size from 16:9 so you don't know what is actually in frame before you snap. I use my phone for pics & video a lot & I have read some things saying that the camera quality on MIUI is a lot better than other roms, how true is that?
Click to expand...
Click to collapse
Alright First thing first... You'll need a extended partition table to install MM roms. The gapps packages are bit bulky so you need to be on extended partition table. Here you can find how to make extended partition table. As for beanstalk rom there is a tweak for the extended partition table, I'm not sure about other MM roms need that tweak or not, because I haven't tried those . AS for camera Beanstalk comes with new snapdragon camera comes with it's own tweak and it's pretty good and yes it's true that MIUI camera is good because of it's secret sauce, unfortunately the source is closed so developers are unable to port that sh*t. As for gapps open gapps pico or banks gapps are good. Rest is upto you and TWRP is recommended recovery.
As far as extending partition is concerned, use this method http://en.miui.com/thread-209941-1-1.html
This method is very easy and reliable and the partition table supports both miui and other mm roms.
Installing miui mm will give same partition table, but the process is cumbersome and you might face soft bricks if not done properly
I am mostly happy with CM13 but it is down to two issues that have me ready to try another rom. I am leaning towards giving BeanStalk a go.
CM13 issues
1. Google Camera is not usable. Can anyone confirm if it is working on BeanStalk or other roms?
2. Bluetooth does not consistently work. It will work a little while & then audio starts skipping & gamepads will not stay connected. The only fix seems to be rebooting but it soon stops working again. So can anyone confirm BT working on Beanstalk or another rom?
Nintoad said:
I am mostly happy with CM13 but it is down to two issues that have me ready to try another rom. I am leaning towards giving BeanStalk a go.
CM13 issues
1. Google Camera is not usable. Can anyone confirm if it is working on BeanStalk or other roms?
2. Bluetooth does not consistently work. It will work a little while & then audio starts skipping & gamepads will not stay connected. The only fix seems to be rebooting but it soon stops working again. So can anyone confirm BT working on Beanstalk or another rom?
Click to expand...
Click to collapse
Yup!! It's Goole camera on Beanstalk but sometimes it's crashes during mode change.That is due to CM source code I guess, because it was working with previous builds. Bluetooth is also ,but Haven't checked with any gamepad though. It's working with normal file transfer. NFC is broken.
Beanstalk is my daily driver, it is pretty stable so far this is the best android 6.0 rom I have tried.
Hey guys, I suppose some of you have had a xiaomi in the past and I have two questions for you and maybe someone that has some knowledge about xiaomi.
1) Currently how's Xiomi dealing with privacy? I remember 1 or 2 years ago Xiaomi has hit with strong reports of leaking information to their government (chinese) and everything we did on the phone would be seeded to their servers, even SMS's and other stuff..
2) How's the ROM support usually for Xiaomi? Do they usually get a stock based ROM, which has no bloatware and some nice tweaks?
Thanks everyone!
Afaik, being a mi3 user, they had a "data sharing" option on by default in miui which is now changed to be off. Personally i never considered it much as there were already devs who had made custom rom for the device, i think over the last two years i might only have used miui for about 4 to 8 months.
No bloatware, but if u r not a previous user, u might find some apps useless (it has its own clean master replacement app). So yeah, there are a lot of options for tweaks n stuff by default too. Hopefully this answers your questions. (and add a question mark to the title, it looks like u r going to rant about Xiaomi by reading the title, lol)
arnabbiswasalsodeep said:
Afaik, being a mi3 user, they had a "data sharing" option on by default in miui which is now changed to be off. Personally i never considered it much as there were already devs who had made custom rom for the device, i think over the last two years i might only have used miui for about 4 to 8 months.
No bloatware, but if u r not a previous user, u might find some apps useless (it has its own clean master replacement app). So yeah, there are a lot of options for tweaks n stuff by default too. Hopefully this answers your questions. (and add a question mark to the title, it looks like u r going to rant about Xiaomi by reading the title, lol)
Click to expand...
Click to collapse
Do you think there will be much custom rom/kernel support for the Mi 5 (or does this depend on Xiaomi allowing for an unlocked bootloader together with release of kernel sources) ?
SlyUK said:
Do you think there will be much custom rom/kernel support for the Mi 5 (or does this depend on Xiaomi allowing for an unlocked bootloader together with release of kernel sources) ?
Click to expand...
Click to collapse
There will sure be support for custom roms even when the kernel source isn't there, my device had custom roms even before kernel source was released, although there were a bit bugs due to it and only a few (like 5 to 10) custom roms were there, bit with the release of sources, it jumped to 50+. And my device had the bootloader unlocked by default, which even i didn't knew until i rebooted to it. Although the fastboot wasn't able to get the info about the bootloader (like version, etc). IDK if any new devices require to unlock it but i don't think it should be hard as they support it, so that won't be a barrier for development.
TL;DR- less n buggy roms w/o kernel source, floods of roms and custom kernels after source, nothing to concern about bootloader.
There maybe some rom development from a few people that get the device and maybe from cm. But that's about it. Non of the big name team roms will have official versions, just maybe ports.
As for the security and privacy. That is up in the air as it seems even on custom roms they some how have managed to still keep track of the devices. One person on the MI note found that even while not on miui for months that they still had a current backup of all his apps and info.
Website signature
zelendel said:
There maybe some rom development from a few people that get the device and maybe from cm. But that's about it. Non of the big name team roms will have official versions, just maybe ports.
As for the security and privacy. That is up in the air as it seems even on custom roms they some how have managed to still keep track of the devices. One person on the MI note found that even while not on miui for months that they still had a current backup of all his apps and info.
Website signature
Click to expand...
Click to collapse
With regards to porting an official rom, I suppose these would be regarded as Unofficial versions. If that is the case is there any real disadvantage in having the "Port" as opposed to have the "Official" version ?
Ports normally will have some bugs as this happens due to not having some things for device built into the code.
Data leak & Software development
Yes I also heard that even with a custom ROM on the device they still found a way to make the device connected and synching information with their servers, which I don't find that funny..
I wanted to know if this data leak is still present in the previous flagship, anyone tested it recently?
It's good to know that it has nearly no bloatware from what you are saying me, but if it has something I don't find useful I may just freeze the app.
Also does anyone know if Xiaomi usually takes long times to update the software of their devices (I heard that they were an exception in relation to other Chinese manufacturers) and release the kernel sources for the ROM developing community or are they pretty good on this area?
Thanks!
:good: :good: :good:
No they are terrible about it. Normally when they post the kernel source it is incomplete and broken.
As for updating. Until very recently they based their os on 4.4 and when asked why they said they didn't care about official android versions.
As for bloat that depends on how you look at it. Miui is about as bloated as TW or HTC Sense.
@zelendel In terms of big name team roms having official versions, would kindly give a few examples ?
SlyUK said:
@zelendel In terms of big name team roms having official versions, would kindly give a few examples ?
Click to expand...
Click to collapse
The biggest are the one or two devices (cant remember their names off the top of my head) that were able to get/fix the kernel source and device trees which CM picked up. So some of the teams that use CM source as a base like AICP also picked up Official versions for the devices.
Then you have the Roms that are based on AOSP instead of CM. As they dont use CM as a base ( Maybe some parts) These roms like Slim or Dirty Unicorns seldom see official versions of the rom. Normally you might get a port here and there. It all depends on if the one of the devs gets the device as most teams don't offer official support for devices they do not own.
i can only find one derpest download here
https://sourceforge.net/projects/derpfest/files/
can a custom rom like this be loaded onto a samsung note 4 SM910F, if someone has to try and its not suitable will it just not load, bits of it not work, or brick the fone. I nhave twrp installed so as long as I can get back to twrp I can go back to another rom.
Senior member please help, my knowledge is low, and really trying to understand this.
.....Has anyone loaded ANY pie style rom onto note 4 sm910F which is as fast as the original android 6.01, and where everything important, CAMERA bluetooth etc all work. If so may I have a link please. THANKyOOOOOO
I doubt it will be compatible with the Galaxy Note 4 but you could do a search from the link below. Good luck
https://derpfest.org/devices
gwm121 said:
i can only find one derpest download here
https://sourceforge.net/projects/derpfest/files/
can a custom rom like this be loaded onto a samsung note 4 SM910F, if someone has to try and its not suitable will it just not load, bits of it not work, or brick the fone. I nhave twrp installed so as long as I can get back to twrp I can go back to another rom.
Senior member please help, my knowledge is low, and really trying to understand this.
.....Has anyone loaded ANY pie style rom onto note 4 sm910F which is as fast as the original android 6.01, and where everything important, CAMERA bluetooth etc all work. If so may I have a link please. THANKyOOOOOO
Click to expand...
Click to collapse
There are 2 types of ROMS for the 910F:
a. stock - original mage by Samsung
b. custom roms AOSP based
Type b can be also divided in 2 -
b1. custom ROMs AOSP based
b2. custom ROMs ported from stock from other Samsung devices - but that involves HUGE amount of knowledge, time and resources spent to get them to work.
I suggest you go and READ and get as much info as you can to be able to understand these terms.
It's not hard, depending on your time and will.
As for your questions of derfest - it is an AOSP based ROM, but if no developer has built it on the official site, it's pretty hard to ask for it for the 910F. I saw no Samsung there.
"can a custom rom like this be loaded onto a samsung note 4 SM910F" - yes, there is Lineage, RR, Havoc, AEX, etc - go check them in the dedicated section of the forum for your device.
"Has anyone loaded ANY pie style rom onto note 4 sm910F which is as fast as the original android 6.01"
There are pie style ROMs (as said above, go check them) faster than android 6. Android 6 was whatever you want, but not fast.
However, there's no pie ROMs ported from other Samsung devices to 910F.
Good luck.
note 4 sm910F custom roms fast stable .. and thankyou
Thank you for reply, appreciated. yes reading as much as possible.
I have rooted, loaded twrp, via odin,
and loaded threee of the four custom roms you mention, Lineage, RR, Havoc, and will look for AEX,
rr res remix is running now, however is slower than android 6.01, 55 seconds for cold start and generally a little laggy, and the camera intermiitntly freezes. Im reading everything I can, but dont understand if the camera problem is , ... a bug on rr, a bug on some camera apps including the one supplied with pico gapps,, an app ive loaded interfering with it or what. Ive seen comments about dirty load and clean load, and wipe with twrp default suggestions before loading rr,.
The reason for wanting a custom rom, is its nice to have both my fones with similar operating systems, the method of getting to app draw, unlocking fone swpe direction, accessing swype down shade are so different android 6 to pie,
and having apps like sonos being able to run
and possibly volte running tho no rom so far has done this.
If the disadvantages of a custom rom outweigh android 6 Ill look at going back to stock, Samsung wont supply the firmware but will do it at their shop!!
Android 6 had one feature better than pie I think, shade accessed by one sype down, and the initial screan names like wifi data in words beneath each item, thats so helpful no pie type rom so far has this
Again big thankyou for reply.
w41ru5 said:
There are 2 types of ROMS for the 910F:
a. stock - original mage by Samsung
b. custom roms AOSP based
Type b can be also divided in 2 -
b1. custom ROMs AOSP based
b2. custom ROMs ported from stock from other Samsung devices - but that involves HUGE amount of knowledge, time and resources spent to get them to work.
I suggest you go and READ and get as much info as you can to be able to understand these terms.
It's not hard, depending on your time and will.
As for your questions of derfest - it is an AOSP based ROM, but if no developer has built it on the official site, it's pretty hard to ask for it for the 910F. I saw no Samsung there.
"can a custom rom like this be loaded onto a samsung note 4 SM910F" - yes, there is Lineage, RR, Havoc, AEX, etc - go check them in the dedicated section of the forum for your device.
"Has anyone loaded ANY pie style rom onto note 4 sm910F which is as fast as the original android 6.01"
There are pie style ROMs (as said above, go check them) faster than android 6. Android 6 was whatever you want, but not fast.
However, there's no pie ROMs ported from other Samsung devices to 910F.
Good luck.
Click to expand...
Click to collapse
gwm121 said:
Thank you for reply, appreciated. yes reading as much as possible.
I have rooted, loaded twrp, via odin,
and loaded threee of the four custom roms you mention, Lineage, RR, Havoc, and will look for AEX,
rr res remix is running now, however is slower than android 6.01, 55 seconds for cold start and generally a little laggy, and the camera intermiitntly freezes. Im reading everything I can, but dont understand if the camera problem is , ... a bug on rr, a bug on some camera apps including the one supplied with pico gapps,, an app ive loaded interfering with it or what. Ive seen comments about dirty load and clean load, and wipe with twrp default suggestions before loading rr,.
1. camera can't be as stock - original blobs (coding) of the app are Samsung proprietary, not open source, it's very difficult to have the same quality
2. coming from stock to custom ROM it's always recommended to format data (wipe is not enough) - that includes the internal storage, so save it before you do it
The reason for wanting a custom rom, is its nice to have both my fones with similar operating systems, the method of getting to app draw, unlocking fone swpe direction, accessing swype down shade are so different android 6 to pie, and having apps like sonos being able to run and possibly volte running tho no rom so far has done this.
these are your preferences, no comment here - however, volte is quite a specific thing, not all developers are bothered/care about it - so again, take it or leave it
If the disadvantages of a custom rom outweigh android 6 Ill look at going back to stock, Samsung wont supply the firmware but will do it at their shop!!
you can go back to stock if you would have made a back-up of stock with the fresh installed TWRP
or use Odin to flash with PC
Android 6 had one feature better than pie I think, shade accessed by one sype down, and the initial screan names like wifi data in words beneath each item, thats so helpful, no pie type rom so far has this
Again big thank you for reply.
Click to expand...
Click to collapse
No problem glad I could help.
Have a nice day.