Related
As per the title says, just so happen to check the Lenovo forums today after reading here they released TPT source yesterday and sure enough the K1 source was released this morning!
Direct Link
http://download.lenovo.com/lenovo/content/sm/IdeaPadTablet-K1.zip
Link to the Thread
http://forums.lenovo.com/t5/IdeaPad-Slate-Tablets/Android-Source-Code/td-p/610273/page/5
Hopefully our humble and dedicated developers can tear this apart and start on some custom ROMS, maybe even kernels?? (I have high hopes clearly!)
On a side note, might not be worth mentioning, but I did notice that the source for the K1 was roughly 72mb in size while the TPT source was in upwards of 202mb?? Same compression for both, food for thought...
Robert
Great news ....the building blocks have arrived
Sent from my HTC Evo 3D with Beats Audio X515m using XDA App
Now hoping for some love, the stock android is pretty slow and painful.....
Will be nice once the custom kernels come.. hopefully they will..
Sent from my GT-I9100 using XDA App
Thats awesome news, man!!!!!!! I didnt think lenovo would do it but wow, its a start.
Hopefully we can get some sweet roms and kernels on this bad boy (k1).
Just based on this news alone, I have ordered for one..
Sent from my HTC Vision
rezapatel said:
Just based on this news alone, I have ordered for one..
Sent from my HTC Vision
Click to expand...
Click to collapse
Bad choice, hardly any support and current android 3.2.1 on it is buggy for the two that we own, stutters a lot.
Be Prepared for this lengthy response!
twe69 said:
Bad choice, hardly any support and current android 3.2.1 on it is buggy for the two that we own, stutters a lot.
Click to expand...
Click to collapse
I agree even with the latest update, there are still bugs in the OS Lenovo loads on this tablet but this should not be a driving force with not buying one. Every tablet I've owned (K1 and the GTablet) or had the chance to tinker with (Xoom, Prime, etc...) have had their flaws, but I also feel this is also based on the user and their personal preferences with using their tablet. Not to mention, what that user would be using the device for (as a toy, or daily driver) has a huge amount to do with it.
What's important here is that they are all running on some form of an Android OS, and if you are willing to tinker and sometimes even experiment with your tablet, you will be able to get to some middle ground (depending on the device, its release date, the community following it has, and when/if the source code is released) based on what you are trying to get out of that particular device to where there are little to no issues.
http://rootzwiki.com/topic/13407-alpha-ideapad-k1-cwm-stock-rooted-rom-120109-build/
For me, I'm currently running the Alpha 3 CWM rom from rootzwiki (link above) and besides I think 1-2 FC's (ONLY happened upon uninstalling pre-loaded apps) it's ran smooth as silk! Granted, I use my K1 as mainly a 'toy' for experimenting with Android SDK, flashing ROM's and general tinkering but still...
Now, you could just drop the $400-$600 on an iPad and not have to worry about FC's and other bugs but then you're left with not only an extremely restricted device but a restricted device that you paid way more for when compared to the K1 for example. Don't get me wrong, after getting my first tablet (GTablet) I quickly realized the quality of the products Apple releases to the consumer public, and if you are a member of that 90%+ percentile of the public that just wants a device to work and doesn't plan on doing anything else to it (and possibly not being as computer savvy as that 5-10% percentile) Apple is the way to go. However atleast from my experiences with the iPad/iPhone, if you plan on doing any modifications remotely resembling base mod's that can be done on an Android device, you're either threatening your warranty or simply SOL.
In short, when I buy an Android phone/tablet I will never expect it to run flawlessly out of the box because A. I'm personally anal/picky/OCD with my hardware and B. I bought it for that initial time investment in order to have a device strictly tuned to my lifestyle and means of use. For this reason alone, an Apple product will never satisfy me (again nothing against anyone who does use Apple, just my 0.02).
I'd rather have a device that is cheaper to buy with arguably the same hardware specs or comparable and is finicky (to say the least at times), but has the potential to run whatever I can throw at it smoothly and most importantly to personalize it on levels that Apple would never allow on their products simply for fear of creating instabilities.
For the K1 however, Lenovo releasing the source is the 1st step towards achieving your own perfectly tuned and personalized device however long it might take. Afterall, one crucial characteristic of an Android user that majority of the members on this forum share is patience! It's what separates us from the rest!
Sorry for the long post, I just felt like expressing my opinion and I was in the typing mood.
Dueces99 said:
I agree even with the latest update, there are still bugs in the OS Lenovo loads on this tablet but this should not be a driving force with not buying one. Every tablet I've owned (K1 and the GTablet) or had the chance to tinker with (Xoom, Prime, etc...) have had their flaws, but I also feel this is also based on the user and their personal preferences with using their tablet. Not to mention, what that user would be using the device for (as a toy, or daily driver) has a huge amount to do with it.
What's important here is that they are all running on some form of an Android OS, and if you are willing to tinker and sometimes even experiment with your tablet, you will be able to get to some middle ground (depending on the device, its release date, the community following it has, and when/if the source code is released) based on what you are trying to get out of that particular device to where there are little to no issues.
http://rootzwiki.com/topic/13407-alpha-ideapad-k1-cwm-stock-rooted-rom-120109-build/
For me, I'm currently running the Alpha 3 CWM rom from rootzwiki (link above) and besides I think 1-2 FC's (ONLY happened upon uninstalling pre-loaded apps) it's ran smooth as silk! Granted, I use my K1 as mainly a 'toy' for experimenting with Android SDK, flashing ROM's and general tinkering but still...
Now, you could just drop the $400-$600 on an iPad and not have to worry about FC's and other bugs but then you're left with not only an extremely restricted device but a restricted device that you paid way more for when compared to the K1 for example. Don't get me wrong, after getting my first tablet (GTablet) I quickly realized the quality of the products Apple releases to the consumer public, and if you are a member of that 90%+ percentile of the public that just wants a device to work and doesn't plan on doing anything else to it (and possibly not being as computer savvy as that 5-10% percentile) Apple is the way to go. However atleast from my experiences with the iPad/iPhone, if you plan on doing any modifications remotely resembling base mod's that can be done on an Android device, you're either threatening your warranty or simply SOL.
In short, when I buy an Android phone/tablet I will never expect it to run flawlessly out of the box because A. I'm personally anal/picky/OCD with my hardware and B. I bought it for that initial time investment in order to have a device strictly tuned to my lifestyle and means of use. For this reason alone, an Apple product will never satisfy me (again nothing against anyone who does use Apple, just my 0.02).
I'd rather have a device that is cheaper to buy with arguably the same hardware specs or comparable and is finicky (to say the least at times), but has the potential to run whatever I can throw at it smoothly and most importantly to personalize it on levels that Apple would never allow on their products simply for fear of creating instabilities.
For the K1 however, Lenovo releasing the source is the 1st step towards achieving your own perfectly tuned and personalized device however long it might take. Afterall, one crucial characteristic of an Android user that majority of the members on this forum share is patience! It's what separates us from the rest!
Sorry for the long post, I just felt like expressing my opinion and I was in the typing mood.
Click to expand...
Click to collapse
great read excellent points
Sent from my Galaxy Nexus using Tapatalk
Dueces99 I shall check out that rom, will see if its possible for me since I am on the latest official version....
I did have a Blackberry Playbook with the original OS in December and that was much better for web browsing etc. Just hoping that Android 4 will have less issues on the tablet since I will be keeping the Lenovo....
Oh and I have been with Android for over 2 years since Android 1.5 and about 5 android phones..... So yeh I am patient
Will definitely pay attention to the next iteration of Windows Mobile though when I upgrade at the end of the year since I like the responsiveness of Windows Mobile 7/7.5.....
this is great news.. really think of selling mine for 300 or so.... if it still worth that ( 32 gb model) .. i might hold on to it now that the source is release and ( cross fingers) someone ports CM9 to it...
we can only wish...
lenovo said they will release ics for k1
http://forums.lenovo.com/t5/IdeaPad...m-Sandwich-for-Ideapad-K1/td-p/638437/page/17
Apologies for the radio silence on this... we have been in discussion with our product teams and shared all the interest and feedback received here.
I believe the current outlook is that a plain version (sounds like it will not include the Lenovo customizations ) of ICS will be made available for download sometime in June. This is a bit later than the original May schedule and will not be pushed as an OTA (over the air update).
I appreciate everyone's patience - I know you have been waiting a while for an update on this.
Thanks
Mark
Alot of Developers have bought this phone!! development for Xperia T / TX and V is going to be good! so far we have 2 elite developers 2 recog developers,, correct me if i am wrong
FXP have 4 members
Bin4ry, Defer, Kali, Jerpelea
Codeworkx!
Tilal6991 too for paranoid android
Gok for kernel is gonna be beast.
Lol @ 4. Good start but not exactly a lot. Yet.
...
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
well this is my first sony device, but looks promising, if sony stays open and doesn't screw up like samsung did, even if they are on updates, we'll have CM team for regural updates. actually, i hope this is first device i'll have for more than a year.
we'll see.
Sent from my Xperia T
Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
Support is looking good for devs to get started and this can be seen from the speed CM10 has become available and is progressing on this device. I don't see the lack of activity in this forum as a bad thing and for a dev it's a good thing because they're not hassled every 2 mins with the same repeated support questions or for ETA's (don't do it ). Devs don't choose devices because they're popular, they choose them because they're good to work on and because they personally like the device as remember this is a hobby after all. I for one, if I do get this phone will hope for it to remain as one of the quieter forums but once people start finishing their contracts I can see it attracting a number of people. I finish mine end of this month so that's when I'll be choosing but that choice is based on how easy it'll be to work with as I like to have a play with compiling myself but only for myself really.
I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.
^aha your right
hello developer!
i think xperia t will get popular because it is the bond phone and the tx looks great in terms of design so it will get popular
Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
TL developer support is going to highly depend on the bootloader locking situation.
As I understand it, AT&T has a bad habit of forcing bootloader locks. I refuse to support any device that has a locked bootloader which is not officially unlockable - even if the lock gets broken unofficially, it's the principle of the thing.
tilal6991 said:
I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.
Click to expand...
Click to collapse
Yeah. The Infuse was a less popular device, and as a result, the developer community was highly cooperative for a while. Unfortunately, the device itself was a nightmare to work with so it was ditched by many. Although, interestingly enough, now that some of the worst aspects of this device development-wise have been identified, the Infuse is becoming kind of fun to work with again.
In the case of the T - all evidence seems to indicate that it's going to be a highly pleasant device to work with, AND if it's not a super-popular device, it may have a more pleasant development community than some of the more popular devices.
There's an existing well-established team of developers with Sony experience, AND there are also a number of Samsung Exynos refugees that have already made the jump or (in my case) are just waiting to see what their local version of the T has to offer.
That said - based on the developers I've seen hopping over, things are going to be heavily weighed in the AOSP-based firmware side of things. Sony's recent devices have become very attractive to developers of AOSP derivatives due to:
Sony's cooperation with the community in terms of technical information and source releases (see DASH)
Most Sony devices are based on Qualcomm chipsets, and over the past year, CodeAurora has emerged as a high quality reference codebase. (CAF has existed for a long time, but it's not really until this year that I saw people using it heavily.)
Sony's explicit AOSP support, both in terms of binary releases to support JBQ's Xperia S project, and frequent commits to AOSP. In fact, they have one developer working part-time on the AOSP Xperia S tree!
However, going back to Snow_fox's comments - if you want a device that is guaranteed not to be dropped early, purchase a Nexus. With any non-Nexus device, you are always taking risks.
Look at the Samsung Exynos situation - A year ago, Samsung devices were looking like your best bet for ongoing developer support. However, over the past year, a variety of things have changed:
Samsung constantly releases broken HALs that require all sorts of workarounds, and don't play nicely with backwards-compatibility solutions that work on other devices. ICS and JB bringup on Exynos4 devices has been an utter nightmare, leading to the entire team of CM on Exynos devices burning out or coming damn close to it
Samsung decided to use their phones as an outlet for gigantic batches of defective eMMC flash chips. They put workarounds in their firmware but didn't tell anyone. The end result is that you have to tread carefully with any 2011-model Samsung device. Their poor handling of the eMMC disaster has left a sour taste in many developers' mouths.
As a result, many developers are leaving, not necessarily for a device that is flashier, but one that is at least more developer-friendly. I think that in many cases, the Xperia TL will be a downgrade for me compared to my Galaxy Note... But dealing with the Exynos in the Note is driving me utterly insane.
AvRS said:
Support is looking good for devs to get started and this can be seen from the speed CM10 has become available and is progressing on this device. I don't see the lack of activity in this forum as a bad thing and for a dev it's a good thing because they're not hassled every 2 mins with the same repeated support questions or for ETA's (don't do it ). Devs don't choose devices because they're popular, they choose them because they're good to work on and because they personally like the device as remember this is a hobby after all. I for one, if I do get this phone will hope for it to remain as one of the quieter forums but once people start finishing their contracts I can see it attracting a number of people. I finish mine end of this month so that's when I'll be choosing but that choice is based on how easy it'll be to work with as I like to have a play with compiling myself but only for myself really.
Click to expand...
Click to collapse
I will have to decide on December 1st what phone I'm going to myself.
I personally understand the appeal of a quieter forum where the same issues aren't asked every couple of minutes.. Once or twice, I've actually had trouble finding a solution wading through the, "How do I ________" and most of them had the response, "do a search" :silly:
tilal6991 said:
I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.
Click to expand...
Click to collapse
Yeah.... there are a lot of ungrateful members. I find myself in an awkward position because, I'm not skilled enough to develop a ROM but, I'm know I'm reliant on whatever XDA puts out to stay up to date with the latest ROMs.
Entropy512 said:
TL developer support is going to highly depend on the bootloader locking situation.
As I understand it, AT&T has a bad habit of forcing bootloader locks. I refuse to support any device that has a locked bootloader which is not officially unlockable - even if the lock gets broken unofficially, it's the principle of the thing.
Click to expand...
Click to collapse
If I were in a position to take that stance, I would myself.
[/QUOTE]
There's an existing well-established team of developers with Sony experience, AND there are also a number of Samsung Exynos refugees that have already made the jump or (in my case) are just waiting to see what their local version of the T has to offer.
That said - based on the developers I've seen hopping over, things are going to be heavily weighed in the AOSP-based firmware side of things. Sony's recent devices have become very attractive to developers of AOSP derivatives due to:
Sony's cooperation with the community in terms of technical information and source releases (see DASH)
Most Sony devices are based on Qualcomm chipsets, and over the past year, CodeAurora has emerged as a high quality reference codebase. (CAF has existed for a long time, but it's not really until this year that I saw people using it heavily.)
Sony's explicit AOSP support, both in terms of binary releases to support JBQ's Xperia S project, and frequent commits to AOSP. In fact, they have one developer working part-time on the AOSP Xperia S tree!
However, going back to Snow_fox's comments - if you want a device that is guaranteed not to be dropped early, purchase a Nexus. With any non-Nexus device, you are always taking risks.
[/Quote]
That unfortunately isn't really entirely an option for me. I'm on a family plan and have no capability of getting out of it at the moment. I don't have enough data to make 16 gigs with no SD card feasible.
I really got lucky when my Captivate had identical hardware to the Nexus S and Samsung was actually good about supporting the devs.
Look at the Samsung Exynos situation - A year ago, Samsung devices were looking like your best bet for ongoing developer support. However, over the past year, a variety of things have changed:
Samsung constantly releases broken HALs that require all sorts of workarounds, and don't play nicely with backwards-compatibility solutions that work on other devices. ICS and JB bringup on Exynos4 devices has been an utter nightmare, leading to the entire team of CM on Exynos devices burning out or coming damn close to it
Samsung decided to use their phones as an outlet for gigantic batches of defective eMMC flash chips. They put workarounds in their firmware but didn't tell anyone. The end result is that you have to tread carefully with any 2011-model Samsung device. Their poor handling of the eMMC disaster has left a sour taste in many developers' mouths.
As a result, many developers are leaving, not necessarily for a device that is flashier, but one that is at least more developer-friendly. I think that in many cases, the Xperia TL will be a downgrade for me compared to my Galaxy Note... But dealing with the Exynos in the Note is driving me utterly insane.
Click to expand...
Click to collapse
Do you think that may have some weight on why Google decided to hop to LG for a Nexus device?
Either way, it sounds like I'll be on the Xperia TL or LG Optimus G this upgrade. The decision isn't exactly becoming easier to make though. At least I managed to scratch off the HOX+
i chose xperia phones becase developers say they are not hard to develop , i have an xperia ray and i have a buttload of roms to choose from... i cant decide so i need to fash every 2week!! (flashaholic :l)
also because sony provides solution for bootloader unlock
Here's what I know so far for the TL. Keep in mind none of this is official, and it is preliminary, so could change.
1) The bootloader will NOT be unlockable on any device that has an active SIMlock. e.g. any device sold on AT&T with a contract subsidy is not going to have an unlockable bootloader. This is almost 100% definite.
2) The bootloader should be unlockable for users who pay full price for the device from AT&T, e.g. anyone who can receive an immediate SIM unlock with AT&T's policies. That said, while AT&T says that any person with a full-price device should be able to immediately remove SIMlocks, often it's a major hassle, and I worry that the bootloader unlock "allowability" process will be even less integrated. Don't count on unlocking your bootloader if you purchase full-price directly from AT&T.
3) Sony may sell the device directly (again - they MAY do it, it's not guaranteed), direct-purchase devices will almost surely have an unlockable bootloader (Not guaranteed, but very likely).
Well,TX seems doesn't support for the rom made to T:crying:
niuzhd said:
Well,TX seems doesn't support for the rom made to T:crying:
Click to expand...
Click to collapse
of course not. It's a different device
Coming from laggy XS, now holding TX,
Sony is doing it right this time, TX design and ICS are so smooth, fast and bug free( at least haven't encounter any yet), TBH I don't have any intention to flash Rom or wait for update (JB).
Sent from my LT29i using xda app-developers app
Waiting for my first room tanks all
Envoyé depuis mon LT30p avec Tapatalk
The 1+3 dev forum lists nearly 50 ROMs.
Is there a general sense how many of them are planning on adding support for the 3T?
Do you think we can expect a similar breadth of ROMs for the 3T, since (I'm reading that) the devices are not compatible?
Thanks.
(I noticed that the Axon 7, which has been out for about as long as the 1+3, has many fewer ROMs.)
No one really knows. Seems unlikely to have nearly as many roms as the OP3 because it's a different processor and the device trees are a mess according to several developers. They would have to start from scratch or close to it and put in a lot of work to maintain their work on both devices. Many developers already have OP3's and do not want to buy another device. OnePlus has said they have some sort of surprise for developers in the pipeline but no one really knows yet what that will be. Time will tell.
I've been using custom roms since 2009 on windows mobile and for the first time ever, I'm actually quite happy staying stock. I haven't even unlocked the bootloader or rooted yet. Really depends on what you want out of the phone. Hope this helps.
I wouldn't expect the same amount of support, but I also wouldn't really expect it to be dry either. The 3T seems like it is going to be a fairly popular phone (at least within enthusiasts), and with that comes a developer community 99% of the time.
I think it will also depend a lot on when the OnePlus 4 (or whatever the next device is called) is released. If the 3T is only their flagship for a few months, similar to the 3, I would expect a pretty big drop-off in ROM support.
By the amount of sales and interest in this phone and the timing near the holidays I say we will see more developers and development from a wide range of newcomers to developers getting an upgrade.
(I have no permissions for ROMs sections so posting this here)
So it looks things are slowly moving , and we are able to unlock bootloader and root our devices.
User @auras76 was kind enough to bring as the first ROM available, but I guess I am not the only one looking forward to get rid of EMUI and its poor customisation layer
I hope once firm .173 hits general release we start getting more dev interest, but the goal of this thread is to find out if any dev could be potentially interested (or already planning) to work on a non-EMUI ROM
I can imagine a bounty could be organised for users to support financially this action.
What are everyone's thoughts on this?
Doubt you will see much development of any major Rom's if there is not a free way to unlock your bootloader as there just won't be that many unlocked devices
I am fully aware of that, however let´s hope that changes if/when .171 FW is generally available and allows bootloader unlock.
I just wanted to check if there would be a way to attract some devs here, even by supporting their work (purchasing a device? 10$ per person???)
If you like custom ROMs so much buy a One Plus phone. Lots of custom ROMs and every custom ROM has bugs. There is no build of any custom ROM that doesn't have bugs and sometimes the bugs on "stable" versions of custom ROMs are so serious they impact the basic functionality of the phone.
If you think I'm exaggerating pick a custom ROM for the OP5, 5T, OP6 or 6T and look at the last several pages of user posts.
They will be users reporting bugs-often very serious ones.
If you pick an OP5 or 5T ROM many will no longer be in development. The last several pages before the ROM was abandoned will be users still reporting bugs that will never get fixed.
And that is on phones that are supposedly very development friendly.
The days of custom ROMs that improve a phone's functionality, speed and stability over the stock ROM died with Nexus phones but if you want to run a custom ROM anyway buying this phone makes pretty much no sense because Huawei is not developer friendly. They don't want owners of Huawei phones to unlock their bootloaders or run custom ROMs on Huawei devices. The same is true for Xiaomi and Samsung phones.
For that matter Google, the company behind Nexus phones which were the most developed friendly phones anyone could buy no longer wants people to use custom ROMs which is why they came up with the ROM certification program and safety net.
Apps that help phone owners bypass safety net are automatically banned from the Play Store. Whatever method Magisk uses to bypass Safety Net gets plugged by Google forcing the developer to come up with a new method that will stop working when it also gets plugged by Google.
The developer behind SuperSu said the writing was on the wall for original Android development several years ago and he knew what he was talking about.
Well, I thought XDA was exactly the place where people "like custom ROMS" and tinker with their phones.
I am coming exactly from OP phone so I know how scene works there.
OP phones are dev-friendly but not many people try different ROMs as Oxygen is probably the smoothest implementation layer of all manufacturers, so there is no need other to change other than fun.
But we are not talking about OP but Huawei here, which is the opposite case. Lousy software implementation, from battery management (see the Powergenie issues threads), to Huawei bloatware, notification handling, little customisation allowed.... So Huawei is not like OP but more like Xiaomi, heavily (not for good) customised Android version. And there might be not many OP ROMS, but check in Xiaomi land... many super stable versions that improve almost any Xiaomi device with AOSP or LOS versions.
As I said, maybe all it takes is to support a dev with a device for ROM release... I know I wouldn't be the only one looking forward to this.
Alright let's clear up what XDA is about.
It's a hub for developers. It's not a hub for people coming in with no knowledge demanding/posting hundreds of threads asking for ROMs for a device which is bootloader locked in most cases. Attitude like this steers developers away from devices because of noob communities. Look at the Samsung community on XDA.
Huwaei is still an infant when it comes to Android so they are learning the ins and outs of what works and what doesn't. Give em a break. They produce amazing devices with amazing technology. Just because it's locked doesn't mean you have to get your nickers in a twist because no one wants to develop for a new company on the Android scene. Give it some time. Maybe someone will come along and get the ball rolling for everyone and find a nice little backdoor in the bootloader and make it possible for everyone. Till then don't hold your breath and stamp your feet. Do your research before you flog out a grand on a device that might not have unofficial development for.
I really hope we can open this device up for more development, what could we do with unbridled access to the NPU, 3 rear cameras and the front 3d point cloud camera array
jhs39 said:
If you like custom ROMs so much buy a One Plus phone. Lots of custom ROMs and every custom ROM has bugs. There is no build of any custom ROM that doesn't have bugs and sometimes the bugs on "stable" versions of custom ROMs are so serious they impact the basic functionality of the phone. .
Click to expand...
Click to collapse
Had to pop in here to tell you you're completely wrong on that one.
Off the top of my head. No limits xXx for the OnePlus 5, not a single bug.
From Oreo 8.1 anyway.
A lot for devices have ROMs which surpass stock in more ways than one and have zero bugs
Further to my point and @ the OP.
The p20 pro has only seen ROMs because of the last few users / developers who have committed to Huawei/Honor devices and the fact that Honor view 10 ROMs work on the pro, in light of the changes made by Huawei IE: bootloader lock down, you will not see a lot of ROMs at all for your device in fact anyone who wants to root / flash / unlock their phones should not touch Huawei or Honor ever again, maybe (and that's a big maybe) the greedy pair of OEMs will see sense. But I doubt it.
Advice in short, dont buy their phones, I certainly won't ever again. They don't deserve it after what they've done.
I'm wondering is there no capable developer here who can build custom rom for Nokia 8?I don't have the proper programming language skill to deal with maintaining source codes to develop a proper custom rom for Nokia 8.If someone has skill in programming language but doesn't have a powerful machine I can collaborate with that. I could request some developer I know to build rom for this phone but someone has to donate a Nokia 8 to them to do that,oh well...
Guess I'll have to sell this Phone if nothing happens for this heavenly neglected phone.
Thing is, Nokia 8 is not a popular device. Just look at our forum, it's almost dead.
So even if there is a good chef owning a Nokia 8, that's probably his secondary device.
Devs circulate around popular devices, so there's a crowd to build for. Here we're just a few people, so there's no point.
If modding is important to you, always choose a popular device, that allows or even encourages modding. Nokia 8 is not that kind of device.
exactly, Nokia 8 is minimalistic and has no any additions. Nokia 8 is simply to work quickly and efficiently.
Can I ask a question? Why you need custom ROM? at this time Phone is up to date.
mati5000 said:
exactly, Nokia 8 is minimalistic and has no any additions. Nokia 8 is simply to work quickly and efficiently.
Can I ask a question? Why you need custom ROM? at this time Phone is up to date.
Click to expand...
Click to collapse
Why some phone gets custom rom and other modding facilities after a few month from release?(Guess that phones i'm talking about) Even after having kernel source codes and bootloader unlock option we haven't seen any development in custom rom project for 8.Don't think 8 got stable OS or any kind of feature improvement in that half baked OS that we have asked for.This is is a lot cheaper phone with a great hardware spec but still none of the dev showed any interest on this phone.Glad to see a guy is trying to do something for this device(T-Virus project) but Anyway,not interested into custom rom or even into this phone anymore. This post is a month older.Nor I can close the thread unless I PM to moderator.:silly:
I believe that something can be improved with custom rom but unfortunately It's hard to determine what anything more might be needed at this time.
my friends prefer piece of junk Xiaomi because is cheap. When i start talking about Nokia they tend to frown.
I Love my Nokia 8
i think there will be no developers or atleast very few, cause Nokia was lagging to unlock booloader, there is very small community which have small amount of Nokia 8's (comparing with other brands most popular phones). This phone is dead, sadly.