Hey Guys!!!
Ever heard of BOOT TO GECKO?!
Mozilla created Firefox, Seamonkey, Thunderbird, and now a smartphone operating system, known as Boot To Gecko, or Mozilla OS...
I am planning on working to port this amazing operating system to our smartphone, it will probably be a BIG project; which is another topic.
Is any developers here in our LG Optimus One area of XDA willing to work with me to get Boot To Gecko on our P500s? It would be amazing, even if it is on a linux/android based port (or themed ROM maybe... port itself is better)
So yeah
Also, I have not a lot of spare time during day between 9am-6pm because of work, so around nighttime I am free, so is on weekends...
I would love to see this on our phones, even sideloaded (multiboot) capability would be amazing, then we could have endless possibilities! I would have DoozzzedUIv4 and Mozilla B2G, and it would be amazing.
I would say good luck, but I'm the one to be working on it
CJ
8-year bump just for add information that may be relevant to anyone reading this post:
on B2G GitHub, there's a pull request for adding support for the P500 in the build process, so it should be compatible if someone compiles it.
Sent from my Galaxy S5 using XDA Labs
MLX said:
8-year bump just for add information that may be relevant to anyone reading this post:
on B2G GitHub, there's a pull request for adding support for the P500 in the build process, so it should be compatible if someone compiles it.
Sent from my Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Man someone did all that work only for it to never see the light of day, its been so long that not only the phone died but the os too. Hard to believe that my 150 dollar phone is more than 16 times more powerful than this.
Fandroid Tech said:
Man someone did all that work only for it to never see the light of day, its been so long that not only the phone died but the os too. Hard to believe that my 150 dollar phone is more than 16 times more powerful than this.
Click to expand...
Click to collapse
Yeah, funny enough I have a LG P350 (not a p500), I would have tried to build it nowadays (just for the sake of trying) lol
MLX said:
Yeah, funny enough I have a LG P350 (not a p500), I would have tried to build it nowadays (just for the sake of trying) lol
Click to expand...
Click to collapse
I used to have an LG P500, the battery bloated a few years ago so I got rid of it thinking I wont miss it. Oh well that was a mistake. There is cyanogen os for the LG P350 so it would be easy to port firefox os overlay to the phone, it should run great as all the applications are minimalist. I am currantly trying to port Lineage 18.1 for my Samsung A11 but I am having issues with the camera, phone calls, etc. Android porting used to be so much more simpler back then, or I am just too unfamiliar with the new environment. The phone is armv6 so the maximum android version it can run without being extremely slow is android 4.4. I could get the lastest twrp version working but it would be useless on it. Postmarketos should run nicely on it.
Fandroid Tech said:
I used to have an LG P500, the battery bloated a few years ago so I got rid of it thinking I wont miss it. Oh well that was a mistake. There is cyanogen os for the LG P350 so it would be easy to port firefox os overlay to the phone, it should run great as all the applications are minimalist. I am currantly trying to port Lineage 18.1 for my Samsung A11 but I am having issues with the camera, phone calls, etc. Android porting used to be so much more simpler back then, or I am just too unfamiliar with the new environment. The phone is armv6 so the maximum android version it can run without being extremely slow is android 4.4. I could get the lastest twrp version working but it would be useless on it. Postmarketos should run nicely on it.
Click to expand...
Click to collapse
actually b2g can't be even built because of the repositories being down, while archives exist you need to patch the source to use the correct paths and that's something most people won't do to run an outdated os
btw I also got twrp3 on some armv6 devices, a nice but useless things indeed
Hi! This is my first post on XDA.
As a user of CM for more than a year ago on my i9300, and after enduring a lot of bugs, I wonder: What happens to CM?
It's a known fact that the Exynos platform is a headache for developers because there is no documentation or open sources from Samsung. So, things like the camera, the sound system, the HDMI output and the GPU do not work as they should.
However, here are many good developers who have fixed these bugs, or at least improve them a bit. And most of these fixes are open source and accessible by everyone on Github.
So, what is waiting CM to implement them? Giving credit to their authors, obviously.
CyanogenMod announces itself as an alternative to the stock firmware that lets you take full advantage of your smartphone, making it better and more stable. Now they are also a company: Cyanogen Inc. As a reputable brand, it should offer a higher quality firmware. ROMs like Nameless (I'm using it right now) works better even being "not official".
This is just an opinion as a user. I'm not criticizing or forcing anyone to do anything. But if there are hundreds of people using a ROM with bugs that were fixed, why not implement them? I would be the first to help, but my skills are just about webdev.
Respect and thanks for i9300 developers on XDA, and sorry about my bad English. When I use my native language I express myself MUCH better. Trust me. lol
Thanks for reading.
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
That's a real shame the device is in such a mess.
Actually, to be fair, using Omnirom 4.4.4, I'm finding that the only thing that doesn't work properly is the notification led (no one seems to know why it only works 3 times out of 4).
I'll probably end up buying a new phone next year, anyway, since buy this time next year the i9300 will be almost 4 years old. In smartphone terms, that means it's getting along a bit.
(oh, and thanks for all your work on it, JustArchi!)
JustArchi said:
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
Click to expand...
Click to collapse
Thanks for answering my topic. The opinion of a developer like you is very appreciated.
This situation only seems to give more reasons for not buy a Samsung phone again. This lack of support from the manufacturer is a disrespect to the user's investment. And fragmentation strikes again. Sad but true.
Thanks again for your great work of keeping this device alive for all of us.
StephenJSweeney said:
That's a real shame the device is in such a mess.
Actually, to be fair, using Omnirom 4.4.4, I'm finding that the only thing that doesn't work properly is the notification led (no one seems to know why it only works 3 times out of 4).
I'll probably end up buying a new phone next year, anyway, since buy this time next year the i9300 will be almost 4 years old. In smartphone terms, that means it's getting along a bit.
(oh, and thanks for all your work on it, JustArchi!)
Click to expand...
Click to collapse
I tried OmniROM few months ago, but it had some annoying bugs (like camera crashes) and I missed some customizations of CyanogenMod. Anyway, I'll try it again. My next buy might be a Motorola phone. The AOSP support is priceless.
ouch01 said:
I tried OmniROM few months ago, but it had some annoying bugs (like camera crashes) and I missed some customizations of CyanogenMod. Anyway, I'll try it again. My next buy might be a Motorola phone. The AOSP support is priceless.
Click to expand...
Click to collapse
I had the camera crash on CM11 M11, and switched over to Omnirom shortly after that. I'm using Google Camera with an Omnirom nightly from November, and I've never had a camera crash.
Agree with you about getting a Motorola. I'd love it if the next Moto G refresh (if there is one) came with some more RAM, increased storage (16GB instead of 8), 4G, and a multicolour led. Being able to customize the colours to suit the category of app is something I love about custom ROMs. That should be baked into Android, to be honest (but at least there's LightFlow).
JustArchi said:
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
Click to expand...
Click to collapse
i feel you
SlimRoms is the answer
unlike CM, Slim has a I9300 maintainer, has support, every weekly update works properly.
Devs should really take a look at Slim's Gerrit and Freenode/#SlimDev
StephenJSweeney said:
I had the camera crash on CM11 M11, and switched over to Omnirom shortly after that. I'm using Google Camera with an Omnirom nightly from November, and I've never had a camera crash.
Agree with you about getting a Motorola. I'd love it if the next Moto G refresh (if there is one) came with some more RAM, increased storage (16GB instead of 8), 4G, and a multicolour led. Being able to customize the colours to suit the category of app is something I love about custom ROMs. That should be baked into Android, to be honest (but at least there's LightFlow).
Click to expand...
Click to collapse
The thing with Motorola is that their stock roms are basically just stock android. No laggy touchwiz skins, just a google launcher. Bloatware is at a minimum. A low spec phone like the moto G still is great because of how vanilla its experience is.
Rumours have it that the galaxy S6 international variant will have an exynos processor. I found a thread comparing the leaked info of the snapdragon 810 vs the next exynos processor and it seems that the exynos is getting a lot of popularity from users on the thread and it ain't no slouch. As it is now, phone's are so fast, that it's very hard to find a way of improving them. Like who compares app opening times nowadays? That will be much the case for 2015's flagships as well. I doubt I'd be disappointed if I had the next Samsung release if I thought I'd be in for a laggy UI, it's just whether I can tolerate the touchwiz experience or if I wanna switch to a vanilla aosp rom. That's where the problem arises.
arashvenus said:
SlimRoms is the answer
unlike CM, Slim has a I9300 maintainer, has support, every weekly update works properly.
Devs should really take a look at Slim's Gerrit and Freenode/#SlimDev
Click to expand...
Click to collapse
But only in your imagination. There is noone at slimrom. Just check their gerrit.
whatsgood said:
Rumours have it that the galaxy S6 international variant will have an exynos processor .... I found a thread comparing the leaked info of the snapdragon 810 vs the next exynos processor and it seems that the exynos is getting a lot of popularity from users on the thread and it ain't no slouch.
Click to expand...
Click to collapse
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
StephenJSweeney said:
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
Click to expand...
Click to collapse
Correct.
Eleve11 said:
Correct.
Click to expand...
Click to collapse
Well then, no more Samsung phones for me, then. Not unless they use Qualcomm..!
StephenJSweeney said:
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
Click to expand...
Click to collapse
Yes, that's what i thought but people are showing interests due to how powerful the processor is. I think they're saying it's more powerful than the snapdragon 810. I'm not that techy but they were mentioning that the new exynos will be smaller in size or something, whilst the snapdragon will be bigger. Apparently smaller is better, but yes the problem is open sourcing. If you want to install a stock android custom rom, it will be difficult for developers to build a rom that can push your phone to it's full potential. Snapdragon doesn't have this problem.
Basically if you love flashing different roms that are fully functional a snapdragon 810 phone is for you. If you like what Samsung offers in it's next flagship and won't be tempted to flash other roms then the exynos is for you
whatsgood said:
Yes, that's what i thought but people are showing interests due to how powerful the processor is. I think they're saying it's more powerful than the snapdragon 810. I'm not that techy but they were mentioning that the new exynos will be smaller in size or something, whilst the snapdragon will be bigger. Apparently smaller is better, but yes the problem is open sourcing. If you want to install a stock android custom rom, it will be difficult for developers to build a rom that can push your phone to it's full potential. Snapdragon doesn't have this problem.
Basically if you love flashing different roms that are fully functional a snapdragon 810 phone is for you. If you like what Samsung offers in it's next flagship and won't be tempted to flash other roms then the exynos is for you
Click to expand...
Click to collapse
I prefer to have less powerful processor, with full documentation how it works, rather than exynos and big giant hackish black box, which noone understands.
The problem is not with the exynos, but with Samsung. Judging from Exynos4, their kernel sources and own experience, exynos may look like it works, but amount of hacks and dirty workarounds to make it work, is too damn high. This could all be solved if Samsung changed their policy from "respect GPL, f*ck the rest" to "respect developers, show them that our SoC can be developer-friendly, too".
The problem is that we're not even 0.01% of Samsung sales, so why should they care. I'm not going to buy Samsung phone again, regardless if it has Snapdragon inside or not. The problem is not with the Exynos, the problem is in Samsung's policy.
JustArchi said:
I prefer to have less powerful processor, with full documentation how it works, rather than exynos and big giant hackish black box, which noone understands.
The problem is not with the exynos, but with Samsung. Judging from Exynos4, their kernel sources and own experience, exynos may look like it works, but amount of hacks and dirty workarounds to make it work, is too damn high. This could all be solved if Samsung changed their policy from "respect GPL, f*ck the rest" to "respect developers, show them that our SoC can be developer-friendly, too".
The problem is that we're not even 0.01% of Samsung sales, so why should they care. I'm not going to buy Samsung phone again, regardless if it has Snapdragon inside or not. The problem is not with the Exynos, the problem is in Samsung's policy.
Click to expand...
Click to collapse
Yeah +1 for that. My next Phone will be definitly a Sony or a One plus. I think both are the developer friendliest in android ...
what for get android with huge ram but still lag? i won't go for android for sure. just stick with ios better. with android 8gb & asop, cm etc still can't fix the bugs. android received update so slow than ios.
khanmein said:
what for get android with huge ram but still lag? i won't go for android for sure. just stick with ios better. with android 8gb & asop, cm etc still can't fix the bugs. android received update so slow than ios.
Click to expand...
Click to collapse
Yeah you are right but i think the most decent phone is the htc one......i would buy a windows phone rather than an iPhone
http://www.reddit.com/r/Android/comments/2qn8s4/new_impressive_lollipop_touchwiz_gives_nexus_line/
This is an interesting article on the new touchwiz that appears in android lollipop on the galaxy note 3. Surprisingly I can see nothing but praise from this person, apparently it seems to be running very well in comparison to touchwiz on KitKat. Is Samsung finally doing something good?
whatsgood said:
http://www.reddit.com/r/Android/comments/2qn8s4/new_impressive_lollipop_touchwiz_gives_nexus_line/
This is an interesting article on the new touchwiz that appears in android lollipop on the galaxy note 3. Surprisingly I can see nothing but praise from this person, apparently it seems to be running very well in comparison to touchwiz on KitKat. Is Samsung finally doing something good?
Click to expand...
Click to collapse
its useless even if they port it to our i9300..1gb of ram..maybe its time to upgrade to more stronger phone..
I am a device maintainer for Xperia SP's Temasek's Unofficial Build now and is considering getting an Xperia M5 for my next device. There are a few questions i would like to ask about MTK devices.
1. Possibility of Custom ROMs?
Would i be able to build custom ROMs? I have searched around on Github and found M9+ kernel sources released (or rather leaked?) by others. (This device uses MTK Helio X10 btw) However, i don't think they have got it booting.
2. Reliability (Patches and Software Updates)
Would i be able to get Software Updates and Patches from Sony say at least up to Android M?
3. Unlocking BL
Would I be able to unlock BL if Custom ROM could be compiled and booted?
+1
Upcoming Helio X20 is very interesting
Most media tech devices never see full kernel source and if it is leaked it is broken beyond repair. This is why no developer will touch these devices. The best you will be able to hope for is a simple port.
zelendel said:
Most media tech devices never see full kernel source and if it is leaked it is broken beyond repair. This is why no developer will touch these devices. The best you will be able to hope for is a simple port.
Click to expand...
Click to collapse
I'm really like in the middle of nowhere cos this is like the determining factor. I have used Sony since Sony Ericsson 2011 series, never used any other brand so i'm really stuck between Android and Microsoft. If simply i can't flash custom roms and do custom stuff, i'm better off with a Microsoft phone or something.
boylush said:
I'm really like in the middle of nowhere cos this is like the determining factor. I have used Sony since Sony Ericsson 2011 series, never used any other brand so i'm really stuck between Android and Microsoft. If simply i can't flash custom roms and do custom stuff, i'm better off with a Microsoft phone or something.
Click to expand...
Click to collapse
Just make sure it is not using the mediatech chip and you will be fine. Those chips are normally used in knock off devices and some China based devices where copyright laws don't hold much weight.
zelendel said:
Just make sure it is not using the mediatech chip and you will be fine. Those chips are normally used in knock off devices and some China based devices where copyright laws don't hold much weight.
Click to expand...
Click to collapse
Might be considering intel chips (Asus Zenfone 2 ZE551ML)
Oneplus x is a really nice phone , i especially like its form factor which is why i brought one just today , but i read a thread where oneplus did not release MM kernel sources and this phone's production stopped. Now i am thinking about giving it back as it would be nearly impossible for future development.
What would anyone who is a present owner suggest in such a situation ? I am only getting this phone because of its 5 inch form factor and good development team.
P.s i know onyx got some top class dev's and Nougat is already on its way, i do not doubt their potential but just this phones future development progress.
Thank you.
We don't need OnePlus for further development. We are perfectly capable of keeping it up to spec. You'll be fine. Enjoy your new toy
It's a phone. You aren't buying it for its future development, you buying it for its features and the fact that they satisfy you. Don't fall in such buyer loop.
Sent from my ONE E1001
sniper20 said:
It's a phone. You aren't buying it for its future development, you buying it for its features and the fact that they satisfy you. Don't fall in such buyer loop.
Sent from my ONE E1001
Click to expand...
Click to collapse
I am a person who is easily bored out using the same rom , i like aosp but i tend to move between different roms (once a week) just because of that . The fact that this phone has CM13 , MIUI (WIP) , SAILFISH OS excited me the most. This is the only reason i look for a phone with good dev community in it which partially require OEM & Chipset supplier support to release drivers.
Of course the phone excites me but I've looped through so many phones that the phone hardware alone does not excite me anymore.
Thank you for the advise tho.
RJDTWO said:
We don't need OnePlus for further development. We are perfectly capable of keeping it up to spec. You'll be fine. Enjoy your new toy
Click to expand...
Click to collapse
thank you for the reply , but might i ask why . I always thought OEM's have to release the kernel sources or the phone will have less chance to be supported by next android version because dev's have to depend on hacks to get things working which is never ideal.
tufli said:
thank you for the reply , but might i ask why . I always thought OEM's have to release the kernel sources or the phone will have less chance to be supported by next android version because dev's have to depend on hacks to get things working which is never ideal.
Click to expand...
Click to collapse
No. Theoretically the only thing we need kernel wise is the DTS and a few drivers. We can pull the source for the 801 from Qualcomm themselves. We don't need an OEM outside of that