yashsingh1/xdaforums huggingface dataset:
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] recoba23:
Please, read OP. I made for you.
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] aliensmille:
Oh, sorry, I am blind :)

Gesendet von meinem ZUK Z2121 mit Tapatalk
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] Luca95ambro:
there is safe center in this rom?
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] jppsousa:
I'm having troubles to donwload de files!

I already disable the adblock and pop-up blocker but i still can't download the files. Where I have to click to download the file?
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] lubikem01:
I have the same problem, also disabled antivirus, but not working to download anything

Odoslané z Redmi Pro pomocou Tapatalku
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] TheChuckIII:
Also need mirror

Link to download is not working at all.

Could you provide a mirror or someone who has already downloaded, could you provide a mirror.
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] recoba23:
There is not safe center in v2.1, but probably will come back in next version, seems necessary for some options.

I have added an alternate link to download, you can try.
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] iliakele:
the alternative link is not working
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] lubikem01:
i figured out, you have to put https:// before it and .nz after mega, here it is: https://mega.nz/#!rMNxACLK!ByrmCMazMkqjf8BLpdnjA0b0UNGfq2yx6CJFoRpP4Dk
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] recoba23:
Sorry, try again, I updated link.
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] iliakele:
hi there is no a safe senter but i have Notification problem i dont get the mass whan the whatsapp dont runing.

there is a solution?
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] CaptainHarIock:
is that rom have to which languages?
[Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth] nnamen:
Can't receive or make calls with this rom, there's no sound , the caller can't hear the receiver, neither can the receiver hear the caller, this is a huge bug that requires immediate fix.
[G Pad 8.3 Q&A, Help & Troubleshooting] oldzealand:
I have an old LG G Pad 8.3 running 4.4.2 and am trying to flash Marshmallow with the steps shown (using Windows 10) at the AC Forums. I'm not allowed to post links so the forum post is titled: Rooting and installing Marshmallow AOSP on LG GPad 8.3.

At the part where you have to use the command “adb sideload kk_root.zip” the command prompt says "error: device not found" even though I have installed the correct USB drivers for the tablet (I think).

I went into device manager with the tablet still in recovery (after selecting "apply update from adb"); there's no yellow icon next to a device (no android or other device shows up)

Please can you help me figure out what's going on? :)
[Sailfish General] AceT2213:
This might be off-topic, but I don't believe XDA has a Symbian thread.

I know a lot of people might disagree with me, but I grew up with Nokia. I followed them and their new devices religiously. I owned or at least played with every Nokia device I could get my hands on. I watched Symbian OS mature, only to die an untimely death, thanks to the iPhone.

Today I came across the Nokia 216 and the 230, and the nostalgia of Symbian absolutely captivated me, even though it's only series 30. Digging into the specs, I was blown away by the reported 19 and 22 DAYS of standby time, respectively, powered by 1020 and 1200mAh batteries, respectively.

And this got me thinking. My first gen Moto E has a 1980mAh battery. If we assumed that series 60 Symbian (their flagship offering, with Java app support) consumed twice as much power as series 30, I would still be getting about 3 weeks of standby time on a single charge, which is mindblowing for a smartphone.

I have scoured the interwebs and found 3 Symbian SDKs. I have zero knowledge regarding ROM porting but I'm pretty technical and I'm a fast learner. Is there anyone willing to help me breathe new life into old hardware? I believe Symbian would run unbelievably fast on this hardware while still having exceptional battery life. I also believe that not a lot would be sacrificed in switching from Android to Symbian, especially since most people only use like 3 apps anyway. And I don't see why Android app support can't be built into Symbian, since most Android apps are written in Java anyway.

So who's gonna help me change the world (of cheap old smartphones) and revive the glory of Symbian? I don't expect anyone to use it as a daily driver, not at first anyway. But I absolutely believe that it could develop to where it could be used as a daily driver, especially for those who don't demand much out of their phones but still want snappy performance and incredible battery life.
[Sailfish General] BalfourLee:
Good thinking, but for one single person , it's a great challenge
[Sailfish General] AceT2213:
That's why I'm reaching out for help from those more experienced than me. I can't even get the SDKs to work, I've been at it all day yesterday.
[Sailfish General] JoshDaWhite:
Well ask some famous developers, maybe they will listen. Maybe [MENTION=4800121]Sultanxda[/MENTION] or [MENTION=4277844]chenxiaolong[/MENTION], or [MENTION=7163930]francisco.fran[/MENTION]co.
[Sailfish General] AceT2213:
I'm assuming they will see this now that you've tagged them. Here's hoping they'll see my vision.
[Sailfish General] Zenzfum000:
Symbian is closed source, i think this is impossible, i have a nokia 700 i'm ok

Zenzero XT1068
[Sailfish General] JoshDaWhite:
[MENTION=3279788]ZaneZam[/MENTION] what do you think?
[Sailfish General] AceT2213:
According to Wikipedia, Symbian became open-source in 2010.

What software is your Nokia 700 running? Do you still use it and if so, how's the battery life?
[Sailfish General] Zenzfum000:
I don't use it anymore, it has original symbian belle fp2
[Sailfish General] AceT2213:
Bump. No one who was tagged showed up
[Sailfish General] triggerlord:
This isn't possible. Linux drivers that Android and Sailfish use aren't compatible with Symbian. You'd have to remake all the drivers from scratch. Also, Android apps are more then just java. They have lots of os api calls.
[Sailfish General] Tataarujin:
Well, some folks made NITDroid possible, I guess they reverse engineered and rewrited all drivers from N900 to android compatible ones. Why vice versa is not possible?

Anyway, that sound interesting. I'd like to see Symbian refreshed for modern times.

BTW, why Sailfish forum?
[Sailfish General] triggerlord:
Dude, the n900 ran Linux. It had Linux drivers.
[Sailfish General] Tataarujin:
Oops, sorry. I miscalculated.
[Sailfish General] KaushikMajumdar:
It's like you're saying you'd build Windows OS into Android. Yes it's possible, and it has already been done. No offense, but for a man with little to no knowledge of Java and Symbian coding and programming languages, you can't just simply port Symbian into Android smartphones. It'd require a lot of different coding in the kernel, camera support, display, sound, processor and other hardware. It'd be like building a new OS from scratch, since both might be running on Java but I think they are vastly different for different devices.

For your motivation, I can advice you that you can already try to figure some way out. Look deep into Symbian SDK and Android SDK, what is similar, what is different, how do both send instructions to the hardware and much more in-depth topics. Figure out the things, compare them, and one day, you might even develop Symbian into Android Smartphones. All I can say is that is going to take a lot of devotion and effort.
[Sailfish General] 4ngl09669:
If I understand correctly you want to bring Symbian on an Android smartphone. This is a nice idea. I suggest you direct your attention on Symbian ^ 3. I have never done such a thing, my knowledge is limited to the PC programming of very simple games. But they are available for this project. But, you need people with this knowledge to do such a thing. You'll need the SDK for Symbian and its source code. I am in possession of the source code.

P.s. Sorry for my bad English, but I'm italian
[Sailfish General] enga018:
please do this
[Sailfish General] pisarz1958:
Few things. What you really need is not an SDK, but a PDK (platform development kit), sources, toolchains etc. Quite a lot of stuff. Some of it was saved here:

https //www mediafire com/folder/79jhy594xb3uk/Symbian_Development#79jhy594xb3uk

You also need compilers, toolchains, quite a lot of stuff to be honest, not sure if you could find everything here. There was a project called Wild Ducks that tried to port the thing to a BeagleBoard. They actually got the thing to run, but as you'd expect, the project is really dead at this point.
[Sailfish General] 4ngl09669:
Yes, I have Carbide.c ++ v3.2 ( view Wikipedia for info ) and a SDK for all Symbian OS version
[Sailfish General] unknown:
When [MENTION=600525]Cotulla[/MENTION] here , he will help you . :):):):):)
[Sailfish General] piko1bg:
this is the best idea by the way i would use Symbian today hell i still use my Nokia E5 (the one that can run gazilions of apps at the same time) its 2017 and Android lacks many of the symbian features that were great (like 2 weeks standby ) better ram management and etc

---------- Post added at 09:47 PM ---------- Previous post was at 09:24 PM ----------

now only if they give us rollback tool like on the P9 lite so we can join the official update schedule
[Sailfish General] trax7:
[MENTION=6570468]AceT2213[/MENTION]

I strongly disagree with the "better RAM management" thing above. Symbian is very very old... It uses a very old pseudo microkernel version, was designed to run on limited resources and from my experience was laggy as hell anyway (I had a Nokia E7, was supposed to be one of the last and best Symbian phones). It therefore misses out on all the improvements made from years time. Compatibility will be even worse. You will have to deal with tons of limitations and will need to change the fundamental ways in which the OS works...

Now... Granted you find all the things you need to build the OS, you would only be able to have any progress on 6-7 year old Nokia hardware. Why? Because that's the only thing you have drivers for. For anything else you're gonna need to write them yourself. Granted you want to use it on modern hardware, of course. What's the point if we have to use 7 year old hardware to get the OS? None. :laugh:

So, we need to rewrite the kernel, drivers, system files, everything. Piece of cake, right? Hold on bro, the ecosystem itself is dead. That means no apps, updates, customization etc. So you will need to create all the most essential apps to make the OS useable. However you can't do that because of licencing, for example third-party Facebook apps can only be wrappers around the mobile version of the site. Also, signing your own apps restricts you a lot, but let's say you bypassed that when you rewrote the system. :p

And Symbian didn't have a lot of apps to begin with, it's not that developer friendly. This is why Android and IOS had an easy time replacing it. Apps were made to be tightly integrated with the system which made it hard for devs. To quote: "All native Symbian C++ applications are built up from three framework classes defined by the application architecture: an application class, a document class and an application user interface class. These classes create the fundamental application behaviour. The remaining needed functions, the application view, data model and data interface, are created independently and interact solely through their APIs with the other classes." And I haven't even begin about security...

Honestly I think you might have more luck with Maemo or MeeGo since they are at least Linux based...

At least Qt is still around but the new versions are definitely gonna cause a lot of compatibility issues with Symbian.

Sorry if I bored you with my long post :) I will follow the thread anyway as it sparked some interest in me... :p
[Sailfish General] AceT2213:
[MENTION=4644172]trax7[/MENTION] thank you for your long and detailed response. You're obviously informed on the topic and I very much appreciate your input.

There are certain facts we must admit if we are to remain motivated about this project (which I am):

First, there will obviously be no updates, no support, and probably very little security.

Second, there will be no wide variety of apps and in most cases, like Facebook, it would be nothing but a wrapper of the mobile site at best.

Third, it will not be the fastest system or the most versatile, and absolutely not the most popular.

Now, with all of that out of the way, I have to say that I've never used the E series. Never liked it, honestly. I've used series S60 that started with the 3650, which wasn't a very popular device. Soon after, the 6600, with a slightly updated version of the same system (to support themes) started the Nokia "smartphone" era, as I call it. This era continued, with slight tweaks, through the first official "smartphone", the 6630 (no front facing camera until the 6680 but with 3G) and eventually the N Series. After that, I believe Nokia screwed up their software, when they got into the touchscreen market. Those touchscreen Nokia systems felt like the dumbed down simplified S40, not at all on the same level of the phones before it. Yes, S60 didn't have the most or the best apps, but it was ridiculously simple to share those apps. Just copy the files to system/apps/appname and the app magically worked. This method was even possible if you received the app files via Bluetooth. Such a simple yet truly memorable experience. And personally, getjar.com never let me down in terms of app selection (at least until I wanted a real Facebook app).

So, with all of that in mind, I ask again. Is it possible to accomplish this goal? Imperfections aside, and maintaining that it's not for everyone, not even in this community, but rather as an option for those willing to make those small sacrifices in return for a drastic improvement in battery life.
[Sailfish General] AceT2213:
The main issue you highlighted would have to be drivers. How would we go about making Qualcomm drives for the outdated system? I very much doubt that either of those companies would help us in this endeavor, so how can we do it ourselves?
[Sailfish General] trax7:
Yes, no help is expected whatsoever. It will be near impossible to do (especially alone). Even if the code itself is already there it's sometimes much easier and cleaner to write from scratch instead of trying to work around legacy software.

In the end, I doubt an increase in battery will be seen anyway due to the fact that the system will be terribly inefficient. Also, no matter the OS, heavy tasks will consume lots of energy, things like Camera and such.

Nevertheless, if you want to consider it as a learning experience, you are welcome to try. I could try and make some small contri from time to time if I feel like it :D

I remembered the thread began as a sort of a complaint for the 'inefficiency' of Android. The Java VM makes it run considerably slower, that is true. The trade-off however for compatibility is huge, we have an OS which runs on lots of CPUs on more than one architecture (x86, ARM, MIPS) and is able to use the same apps on all of them without big hits in performance or the need to recompile for every architecture. This is very big and the reason why Java is used.

There was a project to translate the whole Android to C (XobotOS, I think there was smth else too tho...), thus benefiting from the more mature language and eliminating the eternal bottleneck - the VM. You can search for it if you're interested - I physically think way more can be had from that than rewriting Symbian...

Edit: Forgot about the drivers... You can look into CAF sources, however I doubt that you can make anything since bootloaders are very hard to break and they are strictly proprietary, almost no documentation exists for them (how r u gonna call the kernel when the bootloader won't recognise it, know what I mean?) You will need to hijack the boot process using an working kernel and bridge the two or make the first /compatible one/ boot the second Symbian based one. Bridging Android/Linux and Symbian will need so much hackery... Once boot is complete tho u should be with only second kernel... Kexec-Hardboot? No, kernel still needs to be compatible with bootloader...:rolleyes:

You need to think about partition schemes, how would you make them compatible. Port Symbian to Android partition scheme or? This will make the bootloader go nuts! :p Every action in the boot chain needs to be verified or the bootloader won't execute the kernel and without the kernel u r as naked as a potato :silly: Also, Symbian has a two kernel implementation so that needs to be unified or smth, u cant walk around calling kernels all day lol.

In the end, you can probably see where I'm going with this... :D:D
[Sailfish General] AceT2213:
I was thinking more that the simpler ecosystem of Symbian would be easier on battery, precisely due to all of the abovementioned sacrifices that some people might be okay with. The problem with all current-gen OS's, I think, is that they're all high-performing, making them heavy on battery. But you're right. Unless the port is perfect, there wouldn't be a noticeable increase in battery life. And the newer hardware itself probably uses more power than that of the now-10-year-old Nokia devices.

You've successfully killed my dream lol I'll leave this thread open though in case it inspires someone one day.
[Sailfish General] trax7:
No! Don't give up yet :crying:! I edited my post, go see it :D I urge you to look at Android to C. It's pretty close to what you want to achieve but is more streamlined, less stuff needs wild hax and the results if successful are amazing! Try it! :cowboy:
[Sailfish General] culiacanazo:
You've killed the man's dream! After all this!
[Sailfish General] discourse:
I just charged up my old Nokia N8 and listened to music I still have on there from years back and I've been poking around to see which apps still work and I was able to get the Podcatcher app to subscribe to some of the podcasts I listen to on my Android and iOS devices. On new hardware this OS would be awesome. Maybe a libhybris type solution would work.
[Sailfish General] Dush4711:
Off topic:

Symbian was god at multitasking.

(Nokia C6-01) (256 MB RAM)

You can run at least 20(minimum)apps and can switch between them easily and no app will restarts,it resumes where you left it.

I remember I minimized dungeon hunter and opened it after 4-5 days and when I opened,

It resumes at same state and without loading or reopening.

In its time (2011) no other phones OSs was able to that.

(Sorry if English is bad)
[Sailfish General] trax7:
It could do that because apps and everything in general was smaller in size and less resource intensive. The system as a whole was made to work with scarce resources, that was one of the pillars it revolved around.

Also, some apps will have dumped their state in swap space, making the transition slow but doable.

If you remember, Symbian was very slow with tasks such as web browsing. This is because elements on the page actually had to stay in RAM to ensure any kind of tolerable user experience. And moving them to swap because of low RAM makes everything run extremely slowly, while in the case of switching apps this could more easily be masked behind smartly made animations and delays. :)

Also, Symbian didn't have a lot of things to do behind the scenes... Imagine your Android device without things such as push notifications. Blasphemy! :D All those things that are fast, look good and are so convenient are possible because of better resources. Make better hardware and you will be able to run better and more sophisticated software. Bring back old software on new hardware and watch it fail miserably :silly:
[Sailfish General] madb1lly:
Having gone back to my trusty N8 after Lumia 925 kicked the bucket I found myself wondering about the same thing as the OP. Here's a few thoughts of mine:

1. Focusing on a single target device is the best way to start. Open hardware is obviously the best bet, but is there something available that's more similar to existing phones that used Symbian? The 808 Pureview was the last Symbian so the one most likely to still have similar hardware available.

1a. Since Symbian's strengths are low power usage what about a Symbian band/watch?!....

2. Nothing wrong with "wrappers" for websites - look at Firefox OS. Websites often have way more functionality than apps anyway, that's why I much prefer websites to apps most of the time.

3. Little of the source code was made public and then it was closed up again so improvements made after 2010 are hidden again I think. Who has the rights to Symbian now? I assume that Nokia sold it to Microsoft, and Accenture had the contract to "maintain" it until 2016 (not that they did). MS sold it's feature phone business to HMD Global, did they also sell the rights to Symbian (and what about MeeGo/Harmattan?).

4. I think battery life will always be improved running code natively rather than through a VM, regardless of how optimal the compiler is.

You have source for what? The SDK? Or Symbian itself? Which version?
[Sailfish General] trax7:
You are absolutely right! I wouldn't make a watch out of it, you'd have to remake it in order to be usable or ergonomic. It simply wasn't made with this in mind... (it's not impossible of course, just not worth the effort)

I also don't think any changes have been done even a few years back - it's just an old system and managing/mantaining it is pointless and only costs money.

That said, making a new OS with the same choices in mind would arguably be a better undertaking than fixing or patching old foreign code :)