Related
Thank you for all of your hard work on the D2. With the X, the competition is stiff, and it seems/feels like there are more of us that "ended up" with a D2 out of a warranty replacement than actually made the decision to buy one.
With that said, I am formally starting a bandwagon for an actual "stock" Android OS ROM. None of this color changing, applications because i like them, better home screen, etc., etc., stuff. I want to see an "actual" Android vanilla ROM for the D2.
I can't be the minority in this request.
I appreciate all of the work that you guys do, I really do. If I had the time to invest in this, I'd build the damn thing myself, but I dont, so I have to rely on you guys.
Thanks.
I'm on the bandwagon.
I believe doing this would require cracking m-shield/efuse in order to get a custom kernel in place, which to my knowledge hasn't been done, nor am I even sure if anyone is actively working on it.
psionicalpha said:
I believe doing this would require cracking m-shield/efuse in order to get a custom kernel in place, which to my knowledge hasn't been done, nor am I even sure if anyone is actively working on it.
Click to expand...
Click to collapse
i'm not asking for a kernel. i'm asking the ROM developers to go stock with their approach as opposed to customizing. That's why i used quotes on "OS". I want a clean ROM that reflects as much as the actual Android OS as possible.
640k said:
i'm not asking for a kernel. i'm asking the ROM developers to go stock with their approach as opposed to customizing. That's why i used quotes on "OS". I want a clean ROM that reflects as much as the actual Android OS as possible.
Click to expand...
Click to collapse
If you root your device you can clean out the stock rom yourself. Follow the remove bloatware guide. Once you clean it out you can install launcherpro which IMO is the best home replacement out there. I believe it will be some time before there is a vanilla rom for the d2. We will always need the dialer and a few other apps that are tied into other blur apps.
MotoBoy said:
If you root your device you can clean out the stock rom yourself. Follow the remove bloatware guide. Once you clean it out you can install launcherpro which IMO is the best home replacement out there. I believe it will be some time before there is a vanilla rom for the d2. We will always need the dialer and a few other apps that are tied into other blur apps.
Click to expand...
Click to collapse
removing "bloat" doesn't cut it for me. i'm already running launcherpro without root and it gets me by. the ROM devs are working hard to bring things back to normal and they're doing a good job. i just don't want to have to pick between a broken phone icon and a black notification bar.
i'm not asking for miracles. i recognize that most of blur is limiting this activity. that's why i'm asking for just a clean ROM. as apks become available and more of blur can be replaced, the ROM will get better.
640k said:
i'm not asking for a kernel. i'm asking the ROM developers to go stock with their approach as opposed to customizing. That's why i used quotes on "OS". I want a clean ROM that reflects as much as the actual Android OS as possible.
Click to expand...
Click to collapse
It is harder than you think. Moto modified many services that build with dependencies on the kernel. If we had access to Motos kernel source, then we could just build the vanilla rom directly with google source and be done. Since this is not currently an option, you need to have services that happen to be compatible with the kernal and Motos current structure which is also difficult. Its easy for simple apps that can be switched out like mail and such. But not everything is that easy to swap out. Pull and replace some services on your phone and your phone won't start, because an alternative will not work because the blur service is expressly called, or expected to function in a very "Moto way".
I don't think people are avoiding the stock approach because they don't want stock, I think it hasn't happened (yet) because Moto has made it difficult. Right now its like a Jenga tower. We keep pulling blocks to see which one won't cause the tower to fall. Pull the wrong one...oops we won't pull that one next time. If we could rebuild it from scratch, it would be much easier, because you could build it in the image you wanted opposed to doing surgery to mimic what you want.
facelessuser said:
It is harder than you think. Moto modified many services that build with dependencies on the kernel. If we had access to Motos kernel source, then we could just build the vanilla rom directly with google source and be done. Since this is not currently an option, you need to have services that happen to be compatible with the kernal and Motos current structure which is also difficult. Its easy for simple apps that can be switched out like mail and such. But not everything is that easy to swap out. Pull and replace some services on your phone and your phone won't start, because an alternative will not work because the blur service is expressly called, or expected to function in a very "Moto way".
I don't think people are avoiding the stock approach because they don't want stock, I think it hasn't happened (yet) because Moto has made it difficult. Right now its like a Jenga tower. We keep pulling blocks to see which one won't cause the tower to fall. Pull the wrong one...oops we won't pull that one next time. If we could rebuild it from scratch, it would be much easier, because you could build it in the image you wanted opposed to doing surgery to mimic what you want.
Click to expand...
Click to collapse
this i get, and recognize. but if you read through current ROMs (all two of them), there ARE tweaks that i just don't want/agree with.
i dealt with this alot with WinMo and i've avoided putting ANY ROM on my D1. blur is so terrible, all i want is my D1 one back.. but in my D2's body.
I think these ROM developers simply have no choice but to do the tweaks they've done because Moto services can't just be taken out, they have to be replaced instead of the original so the phone would still work.
We just have to wait, time solves everything, even Moto
facelessuser said:
It is harder than you think. Moto modified many services that build with dependencies on the kernel. If we had access to Motos kernel source, then we could just build the vanilla rom directly with google source and be done. Since this is not currently an option, you need to have services that happen to be compatible with the kernal and Motos current structure which is also difficult. Its easy for simple apps that can be switched out like mail and such. But not everything is that easy to swap out. Pull and replace some services on your phone and your phone won't start, because an alternative will not work because the blur service is expressly called, or expected to function in a very "Moto way".
I don't think people are avoiding the stock approach because they don't want stock, I think it hasn't happened (yet) because Moto has made it difficult. Right now its like a Jenga tower. We keep pulling blocks to see which one won't cause the tower to fall. Pull the wrong one...oops we won't pull that one next time. If we could rebuild it from scratch, it would be much easier, because you could build it in the image you wanted opposed to doing surgery to mimic what you want.
Click to expand...
Click to collapse
640k said:
this i get, and recognize. but if you read through current ROMs (all two of them), there ARE tweaks that i just don't want/agree with.
Click to expand...
Click to collapse
Apparently you don't get it. As stated, stock Android will require the kernel source, which we don't have.
As a former Ion and Nexus One owner who flashed probably a hundred ROMs, I can honestly say Froyo and root is enough to make me happy. Many of the tweaks custom ROMs offered are now built in (they came from AOSP to begin with) and the hardware has advanced to the point that swapper and overclocking aren't necessary. Frankly I'm not sure what more you could want that isn't possible without root and launcher replacements.
640k said:
this i get, and recognize. but if you read through current ROMs (all two of them), there ARE tweaks that i just don't want/agree with.
i dealt with this alot with WinMo and i've avoided putting ANY ROM on my D1. blur is so terrible, all i want is my D1 one back.. but in my D2's body.
Click to expand...
Click to collapse
I am like you. On my D1 I only used OEM ROMs that I modifed myself. I did the same to my D2 and it runs just like my D1. Their are only two differences. Backup assistant services is still running in the backgroud and I still have the messaging app. I removed all blur widgets and all the bloatware I don't need. If I can get rid of the backup assistant I would be very close to plain ROM. Once you remove everything you can safely you are not too far away from a vanilla ROM.
karnovaran said:
Apparently you don't get it. As stated, stock Android will require the kernel source, which we don't have and likely never will.
As a former Ion and Nexus One owner who flashed probably a hundred ROMs, I can honestly say Froyo and root is enough to make me happy. Many of the tweaks custom ROMs offered are now built in (they came from AOSP to begin with) and the hardware has advanced to the point that swapper and overclocking aren't necessary. Frankly I'm not sure what more you could want that isn't possible without root and launcher replacements.
Click to expand...
Click to collapse
Well said. This is not my first android phone either. I have also used Cyanogen and others. Root is more than enough for me.
Back in the day, the custom Roms were pushing us into new territories, giving us features we didn't already have; that was why I wanted them. Now I have everything I need with stock and root. There are so many replacement launchers, lockscreens, etc. Going vanilla is just icing on the the cake; if it ever happens at all.
All of blur's UI flaws and app quirks hardly bug me much at all; I can happily live with them if I have to. Overall, the Droid 2 is a great phone as it is ( with root of course ).
I think i might get my head bitten off for this but id be happy with a stock deoxed rom with the stupid bloat apps removed.
I've come to like the blur widgets and features, well except for the contacts sync issue with facebook.
jerseyh22accord said:
I think i might get my head bitten off for this but id be happy with a stock deoxed rom with the stupid bloat apps removed.
I've come to like the blur widgets and features, well except for the contacts sync issue with facebook.
Click to expand...
Click to collapse
If you goto droidforums.net and in the Xeudoxus ROM section you will see the xultimate thread which is what you need to deodex a rom yourself. If you have the android sdk installed already it is not much work to do. Just follow the instructions and read through the thread for problems that may pop up.
karnovaran said:
Apparently you don't get it. As stated, stock Android will require the kernel source, which we don't have.
As a former Ion and Nexus One owner who flashed probably a hundred ROMs, I can honestly say Froyo and root is enough to make me happy. Many of the tweaks custom ROMs offered are now built in (they came from AOSP to begin with) and the hardware has advanced to the point that swapper and overclocking aren't necessary. Frankly I'm not sure what more you could want that isn't possible without root and launcher replacements.
Click to expand...
Click to collapse
apparently you don't get it.
you're not reading what i'm asking. there are ROM devs out now, doing the work. they can debloat and use as many stock apps as possible (or as available). i'm not asking for miracles. i'm asking devs not to customize what they're doing.
i'm asking for standard looks, not black themes. i'm asking for stock apps, where possible. i'm asking for it to work.
don't come in here and thread crap because you don't understand what i'm saying/asking.
MotoBoy said:
If you goto droidforums.net and in the Xeudoxus ROM section you will see the xultimate thread which is what you need to deodex a rom yourself. If you have the android sdk installed already it is not much work to do. Just follow the instructions and read through the thread for problems that may pop up.
Click to expand...
Click to collapse
I know, i did it before i ran 928droid's theme and epic's rom to change the text to white in the notification bar. Lost it when i restored my nandroid of stock but i could do it again. Just saying if i flash a rom i want it deoxed
I am working on this. Please just wait.
Newbie here. I have rooted my D2, but I haven't yet installed a new ROM. Is there any way that I can use a D1 ROM in my D2?
Sent from my DROID2 using XDA App
640k said:
apparently you don't get it.
you're not reading what i'm asking. there are ROM devs out now, doing the work. they can debloat and use as many stock apps as possible (or as available). i'm not asking for miracles. i'm asking devs not to customize what they're doing.
i'm asking for standard looks, not black themes. i'm asking for stock apps, where possible. i'm asking for it to work.
don't come in here and thread crap because you don't understand what i'm saying/asking.
Click to expand...
Click to collapse
Maybe I (and others) misinterpreted, but you said stock and vanilla multiple times.
Sorry, but I just don't take well to people starting threads like this. Either do the work yourself, contact a developer directly to inquire about their intentions, or sit tight and wait. It's this kind of "gimme" attitude in forums that scares away talented people.
What the hell? Do it yourself. Are you really acting like this because you don't like black notification bars? If it upsets you so much, learn how to change it. Requests are fine. Acting indignant because you don't know what "I want a vanilla ROM" means is rude.
I have a question is it possible to disable or uninstall touchwiz for android stock ? thanks
Unfortunately I do not think this is possible, you can install a launcher of your preference, but the rest of the interface will be Touchwiz. We will have to wait for an AOSP rom to come out, or for CM13 to become stable for daily use and available for all variants of the S6.
With the S6's in-house built Exynos and Samsungs lack of documentation on it, it could be a while before you see any stable AOSP based roms, I'm hoping someone will find a way soon
thommasnd said:
I have a question is it possible to disable or uninstall touchwiz for android stock ? thanks
Click to expand...
Click to collapse
Touchwiz is part of the system setup, so unless someone builds a fully working cyanogen build which is very difficult as Samsung don't release chips chipset sources you won't see complete removal of Touchwiz, you can change the launcher that's it.
sofir786 said:
Touchwiz is part of the system setup, so unless someone builds a fully working cyanogen build which is very difficult as Samsung don't release chips chipset sources you won't see complete removal of Touchwiz, you can change the launcher that's it.
Click to expand...
Click to collapse
ok thanks
Samsung have become (have they ever?) somewhat open source unfriendly. Being a big competitor against Apple may have something to do with it (don't want them stealing ideas or anything ?).
But yes, as the others said, because of so much proprietary shizzle under the hood, a lot of hardware specific code needs reverse engineering and testing intensively. Very time consuming for the guys that do it (so if/when they succeed, be kind and donate for the work).
To further complicate matters, Touchwiz isn't just a bolted on addition to provide something to look at. It is deeply integrated into some of the base code of the android system. Which is a p.i.t.a. for those of us that like to customise etc. Try to remove one part at the whole thing collapses into a mess.
Just so you know, work on a CyanogenMod 13 release is underway. But due to the undocumented hardware modules, the development is barely even beta status and only recommended for developers. But it is happening ?
(I really should sleep before posting, as I waffle a lot when I'm tired ?)
Hi there,
I know Ive asked this question before, and got some good help, though the thread was a much too long read so here a shorter version hoping to get more responses
Is it safe to use an old Android version? And if it isnt, is it safer to install Gapps so I can get some Google updates (for instance Stagefright fix)?
This tut says to keep 4.2 on your device which makes me wonder what to do: http://forum.xda-developers.com/general/security/tuto-how-to-secure-phone-t2960077
FYI I have a HTC Desire Z (there are some 5.x alfas), Sony Xperia T (pain in the ### to update so prefer not to update to newer Android with the risk of not being able to use my phone for some days if it needs some fixing) and a Gigaset 4.2 tablet.
Thanks a lot.
ruben112 said:
Hi there,
I know Ive asked this question before, and got some good help, though the thread was a much too long read so here a shorter version hoping to get more responses
Is it safe to use an old Android version? And if it isnt, is it safer to install Gapps so I can get some Google updates (for instance Stagefright fix)?
This tut says to keep 4.2 on your device which makes me wonder what to do: http://forum.xda-developers.com/general/security/tuto-how-to-secure-phone-t2960077
FYI I have a HTC Desire Z (there are some 5.x alfas), Sony Xperia T (pain in the ### to update so prefer not to update to newer Android with the risk of not being able to use my phone for some days if it needs some fixing) and a Gigaset 4.2 tablet.
Thanks a lot.
Click to expand...
Click to collapse
Safe..
Safe as in as safe as it gets? Dont the Android updates do nothing at the security front?
I think that the object behind the linked post is not the same as what most people consider "secure". I only looked at it briefly but I think the guide you list is more for "how to make sure that the Big Brother cannot find you". The security that newer versions of Android fix are things like exploits that malware can use to steal your info.
If you're worried about the "malware" type of security, then AFAIK the latest version of Android for your device is the best choice. If you're trying to keep absolutely anyone from tracking you... I guess you can follow that guide... but that's really outside of my area of expertise.
in my view older versions of Android are not sure, because of uncorrected publicized flaws on older android vertions.
for the rest it's up to you.
KitKat was released about the same time as Windows XP end of support. Do you think it would be safe running XP right now? Many would not.
Firefox's ssl/tls is also FAR superior to stock/webview browsers, especially on KitKat and earlier.
Even in the new androids (5.0.0 and above) have vulnerabilities in proprietary libs.
All who know about the vulnerabilities, just silent.
Hi fellow xdains. I was wondering if any developer would build fuschia OS for our phone. If any Dev can comment on the feasibility of development ATM, and related info would be great.
Your thoughts?
i would have to guess no considering nobody will unlock the bootloader for the verizon variant. i really don't see a major port like this coming.
NoobInToto said:
Hi fellow xdains. I was wondering if any developer would build fuschia OS for our phone. If any Dev can comment on the feasibility of development ATM, and related info would be great.
Your thoughts?
Click to expand...
Click to collapse
I can comment. Fuschia OS is a toy and not a fully baked OS.
it would be rather useless on your phone. it's pretty much a demo, with no real applications that only recently could even run on bare metal / real hardware... it can run on the pixelbook (which is an x86 intel cpu laptop) and a few other devices...
it doesn't tun on our phone and you wouldn't want to run it, even if it did - unless you aren't interested in being able to make phone calls, browse the internet or do just about anything that you would normally need or want to do. lol
go watch some YouTube videos on it. you'll see for yourself that it's currently pretty useless...
I hope it fails hard, personally. I believe Google's biggest motivation for developing fuschia OS has more to do with licensing and wanting more control than anything else...
it's still an interesting project, but I can guarantee you, if it ever replaces android or chromeOS - your google device is going to be locked down compared to what it is now.
nine7nine said:
I can comment. Fuschia OS is a toy and not a fully baked OS.
it would be rather useless on your phone. it's pretty much a demo, with no real applications that only recently could even run on bare metal / real hardware... it can run on the pixelbook (which is an x86 intel cpu laptop) and a few other devices...
it doesn't tun on our phone and you wouldn't want to run it, even if it did - unless you aren't interested in being able to make phone calls, browse the internet or do just about anything that you would normally need or want to do. lol
go watch some YouTube videos on it. you'll see for yourself that it's currently pretty useless...
I hope it fails hard, personally. I believe Google's biggest motivation for developing fuschia OS has more to do with licensing and wanting more control than anything else...
it's still an interesting project, but I can guarantee you, if it ever replaces android or chromeOS - your google device is going to be locked down compared to what it is now.
Click to expand...
Click to collapse
I agree with you, but since pixel, google has been moving more and more towards locking more things up. At some point it will be like iOS I guess.
NoobInToto said:
I agree with you, but since pixel, google has been moving more and more towards locking more things up. At some point it will be like iOS I guess.
Click to expand...
Click to collapse
how so? what is more locked up since the Pixel?
google has always had their closed source apps and services, but beyond that the pixel is far more open than most android phones I've owned... there are security enhancements, but i don't see that as being locked up... so i'm not sure what ur talking about, in this regard.
the source code for the pixel is included in AOSP, google and the vast majority of retailers sell pixels with OEM unlocking, etc... it's just crappy carriers like Verizon that don't...
I think fuschia OS could be a sign of them going more in the direction of a permissive or more contolled and closed platform, but i'm not sure they'll be able to get it off the ground (many google projects fail or they drop them)...
I don't think the pixel is very closed or locked down though.
nine7nine said:
how so? what is more locked up since the Pixel?
google has always had their closed source apps and services, but beyond that the pixel is far more open than most android phones I've owned... there are security enhancements, but i don't see that as being locked up... so i'm not sure what ur talking about, in this regard.
the source code for the pixel is included in AOSP, google and the vast majority of retailers sell pixels with OEM unlocking, etc... it's just crappy carriers like Verizon that don't...
I think fuschia OS could be a sign of them going more in the direction of a permissive or more contolled and closed platform, but i'm not sure they'll be able to get it off the ground (many google projects fail or they drop them)...
I don't think the pixel is very closed or locked down though.
Click to expand...
Click to collapse
I'm no expert in this ,but I believe with pixel, google moved away a bit from aosp. It introduced more proprietary elements?
Usage wise I am not bothered with it. I'm happy with stock roms, I quit customizing.
NoobInToto said:
I'm no expert in this ,but I believe with pixel, google moved away a bit from aosp. It introduced more proprietary elements?
Usage wise I am not bothered with it. I'm happy with stock roms, I quit customizing.
Click to expand...
Click to collapse
well, they may have added in their typical proprietary soup, plus introduced some new bits, but I don't think they've moved away from aosp, anymore than would be typical... aosp is just the base system, after all... I've built aosp for the pixel in the past and added gapps.... sure, there are differences vs. stock, but not overly drastic...
the pixel 2 likely has more of a gap, but at the same time, once u drop gapps intoplace; i'm sure it's far less noticeable on aosp...
ya, i'm mostly happy with stock too. but I still use magisk, my own kernel, I tweak android a bit... and have been tinkering with xposed, since it was recently released for Oreo (although, it's currently a bit lack-luster due to lack of Oreo plugins).
nine7nine said:
well, they may have added in their typical proprietary soup, plus introduced some new bits, but I don't think they've moved away from aosp, anymore than would be typical... aosp is just the base system, after all... I've built aosp for the pixel in the past and added gapps.... sure, there are differences vs. stock, but not overly drastic...
the pixel 2 likely has more of a gap, but at the same time, once u drop gapps intoplace; i'm sure it's far less noticeable on aosp...
ya, i'm mostly happy with stock too. but I still use magisk, my own kernel, I tweak android a bit... and have been tinkering with xposed, since it was recently released for Oreo (although, it's currently a bit lack-luster due to lack of Oreo plugins).
Click to expand...
Click to collapse
Has there been any progress with xposed being compatible with safetynet? I loved using gravitybox with stock rom since it always seemed to be the most stable, feature-rich, customizable option of the custom roms, but xposed trips safetynet (last I checked) and imo that makes it unusable.
uodii said:
Has there been any progress with xposed being compatible with safetynet? I loved using gravitybox with stock rom since it always seemed to be the most stable, feature-rich, customizable option of the custom roms, but xposed trips safetynet (last I checked) and imo that makes it unusable.
Click to expand...
Click to collapse
That will probably never happen, as far as I know, there is no "progress"
Sent from my Pixel using XDA-Developers Legacy app
I wonder why after roughly 3 years Still no one showing interest in developing a custom rom for our first grade phone? Before they claimed that it is on pause because no has the kernel source code, but now we have access to the official source code and yet no one developed a brand new custom rom for Nokia phone.
Please if anyone could help write a comment below.
to be honest, at this point i simply dont care whatever is happening in this community. If you have knowledge of building a custom rom then why not giving it a go?
i simply dont possess the knowledge at the same time i am also not complaining.
Ok, so first: Nokia 8 launched in September 2017. According to my calculator, thats roughly one and a half year since it came out. Not three.
Then, regarding kernel sources: The official kernel sources for our phone are from the Oreo 8.0 release. It's possible to use older kernels for newer ROMs, but it is really not recommended. And I am not even speaking of the fact that those official kernel sources still require edits to even work. There is no support from Nokia / HMD for development on this phone. Even their unlocker app doesn't work on the majority of versions and completely broke after 2 security patches.
I would be suprised if you can find any developer who is willing to spend their time fighting the stuff that gets thrown between our feet. (broken kernel source, not being able to temporary boot images and having to flash them instead, no working kernel sources from hmd, no reliable bootloader unlock, no official rescue tool etc. etc.) And usually, developers make things because their either need them themselves, or for the joy of creating something and sharing it with people who appreciate it. And when you can port a ROM, you can make the edits you want for yourself with Magisk, so reason 1 is already not applicable.
And as hard as it might sound, this community is by no means large enough to justify porting a ROM you dont need and risking your device stability / userdata in the process.
So the TL;DR; is probably: Either do it yourself, or expect it to never actually happen, as harsh as it sounds, sadly.
THMSP said:
Ok, so first: Nokia 8 launched in September 2017. According to my calculator, thats roughly one and a half year since it came out. Not three.
Then, regarding kernel sources: The official kernel sources for our phone are from the Oreo 8.0 release. It's possible to use older kernels for newer ROMs, but it is really not recommended. And I am not even speaking of the fact that those official kernel sources still require edits to even work. There is no support from Nokia / HMD for development on this phone. Even their unlocker app doesn't work on the majority of versions and completely broke after 2 security patches.
I would be suprised if you can find any developer who is willing to spend their time fighting the stuff that gets thrown between our feet. (broken kernel source, not being able to temporary boot images and having to flash them instead, no working kernel sources from hmd, no reliable bootloader unlock, no official rescue tool etc. etc.) And usually, developers make things because their either need them themselves, or for the joy of creating something and sharing it with people who appreciate it. And when you can port a ROM, you can make the edits you want for yourself with Magisk, so reason 1 is already not applicable.
And as hard as it might sound, this community is by no means large enough to justify porting a ROM you dont need and risking your device stability / userdata in the process.
So the TL;DR; is probably: Either do it yourself, or expect it to never actually happen, as harsh as it sounds, sadly.
Click to expand...
Click to collapse
I can't agree with you more, I was just wondered how this newly released phone still has no custom rom while my LG G3 still after those years received many from lots of developers.
So sad to see our beloved NOKIA has no juice to compete in this race.
error748 said:
I can't agree with you more, I was just wondered how this newly released phone still has no custom rom while my LG G3 still after those years received many from lots of developers.
So sad to see our beloved NOKIA has no juice to compete in this race.
Click to expand...
Click to collapse
We all found out the hard way what Nokia was about by being early adopters. To me they are only interested in pushing their next device and Android One is making that easier for them. So much so the 8 is long since off their radar. It was an 'OK' phone for the money, but there's better now and it's them I'll be looking to this year.
At this point its best to just modify the current stock rom yourself by debloating it, installing kernel tweking modules via magisk, installing themes via substratum and customizing the interface using GravityBox and Xposed Edge. Thats the closest we will come to having a custom rom experience. Ive accepted that no developer will bother with this phone given all the devices that have come out since its release.
Its a lesson learnt. I love this phone but I will never buy another Nokia phone ever again. Im currently saving up for a Xiaomi phone and will use this Nokia 8 as a secondary phone in due time.
MDV106 said:
At this point its best to just modify the current stock rom yourself by debloating it, installing kernel tweking modules via magisk, installing themes via substratum and customizing the interface using GravityBox and Xposed Edge. Thats the closest we will come to having a custom rom experience. Ive accepted that no developer will bother with this phone given all the devices that have come out since its release.
Its a lesson learnt. I love this phone but I will never buy another Nokia phone ever again. Im currently saving up for a Xiaomi phone and will use this Nokia 8 as a secondary phone in due time.
Click to expand...
Click to collapse
Poco or 1+ here
MDV106 said:
At this point its best to just modify the current stock rom yourself by debloating it, installing kernel tweking modules via magisk, installing themes via substratum and customizing the interface using GravityBox and Xposed Edge. Thats the closest we will come to having a custom rom experience. Ive accepted that no developer will bother with this phone given all the devices that have come out since its release.
Its a lesson learnt. I love this phone but I will never buy another Nokia phone ever again. Im currently saving up for a Xiaomi phone and will use this Nokia 8 as a secondary phone in due time.
Click to expand...
Click to collapse
Me too, my next phone would be OnePlus 6T or Oppo.
Never ever ever go around nokia phones again