Related
Hey,
Why is there no android version for the N8?
Could anyone create it? There is enough animo for it.
If i read some forums I see that some people want it. Why not?
Also it has the best mobile camera in the world.
If someone can run android on it it would be the best device ever. (I think)
I could find an answer on this forum. But I think this is already changed.
(That there isn't enough animo for it. But there is!)
I'm also a newb in this world. But I like android and the compatibility that the most devices already have with it.
Kevin
I dont know if its that simple. I dont rly know if the android suitable for N8, anyway would be nice to have it (even though that i have HD2, which i think that is much better than N8.) If its possible, my friends will have android too! xD
indeed!
I think an android developer must buy an n8.. that he can see it's a wonderfull device.
And then create android for it.
Not all phones are like hd2, where you can have different os
Sent from HTC HD2 with Android
Not all people wants a HD2
you are not alone my friend!
I too wish the N8 had Android.
It is a much better device than the HD2, screen size isn't everything.
coldest~~~ said:
Not all phones are like hd2, where you can have different os
Sent from HTC HD2 with Android
Click to expand...
Click to collapse
anything is possible, it just takes time.
and in the HD2's favor, it had hardware that was common across different platforms.
plus a big userbase
Isnt the N8 nokia soft based on Debian? couldn't drivers be ported my friend has this device and yes the camera is amazing on it
I thougt it was only meego and maemo wich is debian based?
i was thinking to get a nokia n8 untill ive found out that nokia had very low quality development for that new symbian version, and that they moved torwards windows mobile... i never liked windows mobile and since they were not going for android i said whats the point, on paper the nokia n8 is amazing, but it has some problems aswell, for example the cpu is only 625mhz, while its arguably enough to run android, im not entirely sure it has all the instruction sets compatible with it, emulation is out of the question too, the android code would have to be natively changed to work for it, and then there had to be the matter of games, they also had to be coded properly for that specific gpu,cpu and sound chip, accelerometer and so on.
So thats why ppl dont usually port phones to android, its a mess to code and most of the drivers they have to code them from scratch.
TheWarKeeper said:
i was thinking to get a nokia n8 untill ive found out that nokia had very low quality development for that new symbian version, and that they moved torwards windows mobile... i never liked windows mobile and since they were not going for android i said whats the point, on paper the nokia n8 is amazing, but it has some problems aswell, for example the cpu is only 625mhz, while its arguably enough to run android, im not entirely sure it has all the instruction sets compatible with it, emulation is out of the question too, the android code would have to be natively changed to work for it, and then there had to be the matter of games, they also had to be coded properly for that specific gpu,cpu and sound chip, accelerometer and so on.
So thats why ppl dont usually port phones to android, its a mess to code and most of the drivers they have to code them from scratch.
Click to expand...
Click to collapse
The CPU is official build for 750mhz. So it can run faster.. Also i heard that the new version of android (3.0?) has hardware acceleration for the UI. So the GPU can be used for it.
cpu for android need nore juice and ram.
battery life will be hunger for more to join android.
nokia seem battery effective device.low power consumption
under18 said:
cpu for android need nore juice and ram.
battery life will be hunger for more to join android.
nokia seem battery effective device.low power consumption
Click to expand...
Click to collapse
Why?
The HTC ChaCha and Salsa has a 600 mhz processor... And still Android runs on it.
Indeed the ram is littlebit low 256 mb...
Chacha is 800Mhz, 512 of ram..
yeah i wish that someone would find a way to port android to n8 i recently got one and dont like symbian os, any way i'll keep on searching if no luck, guess i have to get an android phone
Edit: forgot to say i had a sony ericsson x8 which had 600 Mhz processor and 256mb ram and i was even able to run android 4.0 on it dunno why n8 would not run on this device
The question is why port android to N8? The N8 is a wonderful device as is. If you have an N8 you probably bought it for it's camera prowess. Bonus: you get a very long battery life (compared to droids). Now if you want to port android on it then it will become power hungry and will be full of glitches since it has poor dev support. Also, you wouldn't want a slow droid. 600mhz for a droid is quite slow, and as stated, the RAM is low. You're better off buying an affordable Galaxy Y. Believe me it's quite fast, if you can live with it's low res screen.
Cheers,
Cezar
kevinwalter said:
Hey,
Why is there no android version for the N8?
Could anyone create it? There is enough animo for it.
If i read some forums I see that some people want it. Why not?
Also it has the best mobile camera in the world.
If someone can run android on it it would be the best device ever. (I think)
I could find an answer on this forum. But I think this is already changed.
(That there isn't enough animo for it. But there is!)
I'm also a newb in this world. But I like android and the compatibility that the most devices already have with it.
Kevin
Click to expand...
Click to collapse
it's not possible to port Android or any other OS to symbian phones because of locked bootloaders by Nokia
Nokia n9 is running meego OS which is with unlocked bootloaders and that's why this phone can have dual boot or just one OS like Android 4.x.x ICS
I want it too
I have an Nokia N8 too and i would love to run android on it.
So if there is any way to install android on it....
I also have nokia n8, it was really a great phone,hi quality build, superb. And I fine with symbian^3 but what bothering me was that the nokia apps store is getting useless. I need BBM and can't find any.
Hi folks,
I am a owner of a SGS+ (i9001) which chipped with the chipset MSM8255T.
Now I've seen that are out some ICS-ROMs working with the Desire HD already which contains the (estimated) previous version MSM8255.
Unfortunately I could not find any useful information at Qualcomm, which shows the differences between these two chipsets.
May I use one of these ROMs as a base for my development for an MSM8255T or differ the chipsets too much?
There is an Alpha-Release from SE for the Arc S (4.0.1) which has the same Chipset as the i9001 ... but this lacks the basic functions including the modem and wifi ...
not a good starting point when i have the chance to start behind this limitations.
Nice holidays
Hi hirnwunde!
Funny nick )
I own a SGH-T679 (Exhibit II) witch is a half brother of the GT-I8150 (Galaxy Wonder).
What I can state that my phone works with SGW roms, issues are with the keys and the camera.
The SOC seem to be the same on different clock speed.
I don't know if there is a way to safely boot SE or HTC roms on Samsung phones.
hirnwunde said:
Hi folks,
I am a owner of a SGS+ (i9001) which chipped with the chipset MSM8255T.
Now I've seen that are out some ICS-ROMs working with the Desire HD already which contains the (estimated) previous version MSM8255.
Unfortunately I could not find any useful information at Qualcomm, which shows the differences between these two chipsets.
May I use one of these ROMs as a base for my development for an MSM8255T or differ the chipsets too much?
There is an Alpha-Release from SE for the Arc S (4.0.1) which has the same Chipset as the i9001 ... but this lacks the basic functions including the modem and wifi ...
not a good starting point when i have the chance to start behind this limitations.
Nice holidays
Click to expand...
Click to collapse
You have to watch for other device though, for instance the screen and camera needs different drivers. that by itself prevents direct usage from other phones even though the cpu is the same..
Is there any rhyme or reason to them? For example, I just got a Sony Xperia XZ1 compact...it appears to be referred to as "lilac" ...who/what makes these designations? The manufacturer? ROM-makers? Many of the builds of LineageOS don't seem entirely arbitrary.
Or are they distinct and I've got the wrong idea? Is "lilac" only the name of the Android build for a particular phone model?
I guess it's manufacturer's choice.
Honestly codenames for Xperia's sounds like a names for me (Anzu, Ayame, Honami, Suzu, Huashan, etc).
OzzyFyshmaster said:
Is there any rhyme or reason to them? For example, I just got a Sony Xperia XZ1 compact...it appears to be referred to as "lilac" ...who/what makes these designations? The manufacturer? ROM-makers? Many of the builds of LineageOS don't seem entirely arbitrary.
Or are they distinct and I've got the wrong idea? Is "lilac" only the name of the Android build for a particular phone model?
Click to expand...
Click to collapse
The manufacturer or their hardware R&D team designates the name, probably the primary engineer that comes up with the device design, whoever that may be at the time for that device. The names usually follow a theme, such as Google devices using types of fish as the codename. Btw, operating systems also use codenames such as Linux distros using names such as Rebecca or Google using candies and cakes for the name of each android version.
Sent from my LGL84VL using Tapatalk
I don't see any updates for Cusrom, are these XZs outdated? I do not understand
its not specific for XZs,
over all SONY has same treatment from developer side!
reasons?
there are many but one MAJOR reason in my view is
sony xperia is not popular device and low sales, less users, lower the intent to develop anything
if they market well today and boost their customer base! , Xperia Z days will come back!
Miss Old Days :crying:
Miss back on Owned X10 Mini Pro great days, when Kitkat and JB was coming, many Develop is there...
also the when Owned Xperia SP, when Lolipop and Marshmellow was coming, many Dev is there...
I dont understand, since Nougat coming and now Oreo and Pie exist... Sony Dev one by one start going rest and gone...
:crying:
Sony still provides AOSP Pie version for Xperia XZs despite Sony will never giving out any official upgrades for this device.
Right now, I'm currently working with AOSP Pie for XZs and I managed to boot the device with Android Pie version. Building with Linux on Windows 10 could be really pain because Linux on Win10 is not fully virtual environment where some building progress will be stalled at the middle of the progress while I'm thinking to reinstall Ubuntu back on my PC after using Arch Linux for a while.
Anyway, I can't post the Pie ROM here right now because I want to rebuild it to make it better without progress stalling issues.
Hi everyone.
Every year millions of phones and tablets are produced. Because hardware makers don't worry about updating them, those devices are often dumped. However, lots of them are very capable machines.
As I've read these forums for years, I've seen a lot of work from a lot of people trying to bring those forgotten devices to life again by making unofficial ROMs with tons of customization, new features, and great efforts like LineageOS and PostmarketOS. However, those lack the resources to bring an updated OS for the majority of those binned and obsolete phones.
If I'm not wrong, the biggest issue about replacing the original OS on those devices are the bootloaders and drivers/blobs for the large amount of different hardware configurations. There are multiple workarounds, shims, ports that solve those problems for one or other device.
It might be quite naive, but i'd like to ask a question I've been thinking about lately. AFAIK, if I have the blobs/drivers for a camera, wifi, bluetooth, GPS or other "peripheral" for a devices' original ROM running Android 4.4, I can make it work on AOSP 4.4. I know this might be crazy, but:
As long as I have the blobs for a certain chipset and display/touch, why can't we use a VM running a nano version of AOSP that matches the devices' original ROM that bridges the device IO to the main ROM?
As an example, imagine wifi. I could network bridge AOSP 9 to a VM running AOSP 4, which would then have the drivers so network would work. The same for bluetooth or camera or GPS, maybe? Is this absolutely unfeasible?
Thank you for your time!
wasserprojekt said:
Hi everyone.
Every year millions of phones and tablets are produced. Because hardware makers don't worry about updating them, those devices are often dumped. However, lots of them are very capable machines.
As I've read these forums for years, I've seen a lot of work from a lot of people trying to bring those forgotten devices to life again by making unofficial ROMs with tons of customization, new features, and great efforts like LineageOS and PostmarketOS. However, those lack the resources to bring an updated OS for the majority of those binned and obsolete phones.
If I'm not wrong, the biggest issue about replacing the original OS on those devices are the bootloaders and drivers/blobs for the large amount of different hardware configurations. There are multiple workarounds, shims, ports that solve those problems for one or other device.
It might be quite naive, but i'd like to ask a question I've been thinking about lately. AFAIK, if I have the blobs/drivers for a camera, wifi, bluetooth, GPS or other "peripheral" for a devices' original ROM running Android 4.4, I can make it work on AOSP 4.4. I know this might be crazy, but:
As long as I have the blobs for a certain chipset and display/touch, why can't we use a VM running a nano version of AOSP that matches the devices' original ROM that bridges the device IO to the main ROM?
As an example, imagine wifi. I could network bridge AOSP 9 to a VM running AOSP 4, which would then have the drivers so network would work. The same for bluetooth or camera or GPS, maybe? Is this absolutely unfeasible?
Thank you for your time!
Click to expand...
Click to collapse
That's sort of what project treble is.
Project Treble
The Android 8.0 release includes Project Treble, a major re-architect of the Android OS framework designed to make it easier, faster, and less costly for manufacturers to update devices to a new version of Android. Treble is for all new devices launching with Android 8.0 and beyond.
forum.xda-developers.com
I was reading about it and it seems like treble is not very seccessful. I imagine Google isn't very interested on this, as they want phones to be sold every year. Anyway, I was asking about this specific method of making phones and tablets compatible with today's OS or, who knows, even linux.
wasserprojekt said:
I was reading about it and it seems like treble is not very seccessful. I imagine Google isn't very interested on this, as they want phones to be sold every year. Anyway, I was asking about this specific method of making phones and tablets compatible with today's OS or, who knows, even linux.
Click to expand...
Click to collapse
Yes and the only way it might work is trebel. Because treble handles lot of the problems involved with booting newer androids on older systems.
You can run linux on older Androids or even Windows XP.
How to install a Linux desktop on your Android device
Get even more from your Android device by running a desktop OS! Lots of options including Debian (no root), Ubuntu, and Kali Linux.
www.androidauthority.com
Running Windows XP on Android
No rooting or custom modifications needed, we’re going to do this with stock Android and a few free (but high-quality) apps.
centerorbit.medium.com
Also, it's not that the OS gets deprecated, it's that the applications like Google Play services which become heavier as years go by.
Degoogled-Android on my Android ICS phone worked fine till it's screen got busted. With Google Play services, it was impossible to install any app since its paltry 400MB storage was extended/
Thanks for your answers!
Running other OSes via VNC is just meant to use the devices as mere thin clients, and that was not the objective.
The Project Treble will never be as widespread as it should be, because Google is obviously not interested in making phones last longer (they want more devices to be sold). Of course I was not talking about devices 10 years old, more about 5yrs. They have specs good enough to run contemporary Android and most of non-entertainment apps.
The obstacles to being able to do this are artificial. The problem is there are no drivers and project Treble does not address this in any meaningful way. Manufacturers aren't interested in this too because they want to sell more chips. So the only way it came to my mind it could work was by running a very light VM with an older Android for which the components' drivers were available. Of course main components would still have to be compatible with newer Android, such as the SOC. But things such as wi-fi, camera... could be bridged from a VM, I believe.
Not sure, but I'd guess the low-level interface would have to be outside the VM.
That is, to be able to run the VM you'd have to have some drivers already in place. I'm also not sure everything can be virtualized. For example, desktop VMs couldn't so easily passthru PCIe or USB to VMs, at least in the past.
There's some EU push to make fixing and servicing some non-phone devices easier, and to mandate labeling phones (and other devices) with repairability scores. Maybe eventually they could mandate, under certain conditions, the logical separation of hardware and software?
Well, after a long time, for those who where curious about this thread: the project Halium is exactly what was in my mind. If I'm not wrong, it basically consists in a minimal Android rom running on a Virtual Machine which then interfaces with any Linux distro, effectively giving the phone the ability to run a (more or less) updated version of Linux kernel and, therefore, many Linux distros. https://docs.halium.org/en/latest/project/Scope.html
hkjo said:
Not sure, but I'd guess the low-level interface would have to be outside the VM.
That is, to be able to run the VM you'd have to have some drivers already in place. I'm also not sure everything can be virtualized. For example, desktop VMs couldn't so easily passthru PCIe or USB to VMs, at least in the past.
There's some EU push to make fixing and servicing some non-phone devices easier, and to mandate labeling phones (and other devices) with repairability scores. Maybe eventually they could mandate, under certain conditions, the logical separation of hardware and software?
Click to expand...
Click to collapse
You are right, and I believe Halium just works on phones which are minimally supported by Linux kernel drivers (like basic SoCs). But all those other hardware parts, like GPS, Wi-Fi, Camera... can be brought to life this way, I think.
Thanks for your insight!