i tink that LG was waiting for cooking a stock rom based on android 2.4 (instead of the 2.3 promised) because of their similarities, in fact the gpu accelerations for 2D, rumored for the 2.4, can only help our P500 performance.
i hope this, and you?
Ps: i tink that a P500 at 150$ with 2.4 in the very next month can bring android for many doubtful people..
I'm not really keeping my hopes up. I bet the last official update we'll receive is Gingerbread. Most companies focus on their flagship phones, and despite the O1's popularity, I don't think it'll receive much.
Also, IMHO, Google is going too fast. Manufacturers are having a hard time catching up and stuff.
But if you ask me, I'm contented with Froyo. Unless, of course, there's a really badass killer feature available only to future releases.
And I think this should be in the General category
kpbotbot- It's more like manufacturers use the differente Android os'es for marketing uses . Look at samsung , they're waiting to release the native 2.3 devices and bearly then will they release gingerbread for their current flagship : Galaxy S . It's a dirty world .
Yeah. Here's a super thank-able screenshot I took weeks ago
LG and Samsung seem like very different companies. The Optimus line is a very good buy for most carriers. It will convert a lot of users to the Android world like me. LG seems to catter to their users too.
The manufacturers should understand Android devices should follow Googles releases. It seems like most manufacturers just barely make the software and communities like xda do the actual bug fixing and create a more robust system with the custom kernel & ROM releases.
Sent from my VM670 using XDA App
why would companies spend money and time in the software when
communities like xda do the actual bug fixing and create a more robust system with the custom kernel & ROM releases.
Click to expand...
Click to collapse
@orlox - Imagine buying a phone that doesn't come with an operating system.
I prefer if companies release only the lifeless phone, and xda would give life to it.
So androids will be much cheaper
ccdreadcc said:
I prefer if companies release only the lifeless phone, and xda would give life to it.
So androids will be much cheaper
Click to expand...
Click to collapse
I like the idea!
Post delivered via piece of paper tied to a brick... sorry 'bout the window! XD
The reason I chose this phone is because, for me, it's a small portable computer. If only every bit of hardware of this phone had a corresponding device driver (that we can get hold of), I think there's nothing stopping us from using a full Linux desktop, or other operating systems capable of running on the ARM architecture.
Not so relevant note: Some say the bootloader is locked. True?
kpbotbot said:
The reason I chose this phone is because, for me, it's a small portable computer.
Click to expand...
Click to collapse
So true!
I am very satisfied with my first Android experience, in spite of all the bugs and hardware limitations of this cheap phone. Almost anything I needed but couldn't do before on my "dumb" phone became possible with this micro computer. So I don't really care if it's running Eclair, Froyo, Gingerbread, Ice Cream or Milk & Toast & Honey.
You would care if it was running Cupcake.
P.S There really is a possibility for us to get 2.4 on our phones. It is still called Gingerbread but it will support Honeycomb apps.
Sent from my LG-P500 using XDA App
there are some questions to answer, why people buy a smartphone in general. We must see the differences between users who "use" the mobile as a daily instrument, users who use the mobile to play 3D games, users who read in the internet and communicate with it and users who are tweaking/hacking (not so sad as i write here). Most of users are using their device for communication, and so the manufacturers can say "why we should develop so fast as google? Our users doesn't need the new features like NFC or other". When communities like XDA, Cyanogen,CodeAurora,androidcentral or others develop their ROMs to their needs, they should do that - they are users who "want" the features. So, manufacturers can invest more time and money in new devices for more experience and for advanced users (like technical freaks). We (users who are lucky for while) can buy the "new" device at a later time, so we can save some money. Nothing other does LG,Samsung or HTC - they are developing for the feature. The money and time to invest in updates or bugfixes are too much for the most - this could be one reason for hold back updates or dont develop. As a developer i can say, the time to spend for Gingerbread development is not small - i have needed 3 monthes to develop a rom, that have just some bugs, and i've do that for fun. for a manufacturer this is not fun
kpbotbot said:
Yeah. Here's a super thank-able screenshot I took weeks ago
Click to expand...
Click to collapse
This makes perfect sense from the carrier's perspective. If people had to pay to upgrade to the next version the carriers might have more incentive; as it is now they aren't seeing any more money so why bother investing time on something that could blow up in their face.
andy572 said:
there are some questions to answer, why people buy a smartphone in general. We must see the differences between users who "use" the mobile as a daily instrument, users who use the mobile to play 3D games, users who read in the internet and communicate with it and users who are tweaking/hacking (not so sad as i write here). Most of users are using their device for communication, and so the manufacturers can say "why we should develop so fast as google? Our users doesn't need the new features like NFC or other". When communities like XDA, Cyanogen,CodeAurora,androidcentral or others develop their ROMs to their needs, they should do that - they are users who "want" the features. So, manufacturers can invest more time and money in new devices for more experience and for advanced users (like technical freaks). We (users who are lucky for while) can buy the "new" device at a later time, so we can save some money. Nothing other does LG,Samsung or HTC - they are developing for the feature. The money and time to invest in updates or bugfixes are too much for the most - this could be one reason for hold back updates or dont develop. As a developer i can say, the time to spend for Gingerbread development is not small - i have needed 3 monthes to develop a rom, that have just some bugs, and i've do that for fun. for a manufacturer this is not fun
Click to expand...
Click to collapse
Yeah , bro , but you're one man fighting against the tides . It's bound that LG has at least a reminder of 5 man cell team working on getting gingerbread out . And besides they have other ways of getting info and ironing out bugs faster then you can .
Sad that they didn't place on the internet a god damn ETA by now .... thus I guess may or june might a realistic launch date
Oh and to be on-topic with the thread , I guess we'll see 2.4 by CM7 if any of the legendary devs still take interest in this phone ofc
+1 i second that...plus i heard that not all the code used is even OPEN..I mean mik somewhere mentioned that some libraries had no corresponding code in the source code archive....thats gotta stink plus porting of android is different than developiing Linux Distro..I mean no mailing lists and not such a big community of "porters"....but tahts just my take..
sarfaraz1989 said:
+1 i second that...plus i heard that not all the code used is even OPEN..I mean mik somewhere mentioned that some libraries had no corresponding code in the source code archive....thats gotta stink plus porting of android is different than developiing Linux Distro..I mean no mailing lists and not such a big community of "porters"....but tahts just my take..
Click to expand...
Click to collapse
you're right:
many libraries are closed source, it's like a driver from nvidia for Linux X.org.
The only way to port it to a new android version is to test if it works - if not, we have a problem. manufacturer does not support communities, so we have to build many workarounds or rewrite the code so that it works. i would wish, the manufacturers opens their drivers and codecs for playing audio and video - so we can develop faster, more stable and uncomplicated:/
back to topic:
i've readed the last days that gingerbread 2.4 is the internal 2.3.3 - let's check, if apps for honeycomb work on this version: in 2.4 there should be compatibility for the honeycomb apps^^
andy572 said:
you're right:
many libraries are closed source, it's like a driver from nvidia for Linux X.org.
The only way to port it to a new android version is to test if it works - if not, we have a problem. manufacturer does not support communities, so we have to build many workarounds or rewrite the code so that it works. i would wish, the manufacturers opens their drivers and codecs for playing audio and video - so we can develop faster, more stable and uncomplicated:/
back to topic:
i've readed the last days that gingerbread 2.4 is the internal 2.3.3 - let's check, if apps for honeycomb work on this version: in 2.4 there should be compatibility for the honeycomb apps^^
Click to expand...
Click to collapse
if everything's open then it is unlikely they make money. Then they close down and there won't be any phone.
Sent from my LG-P500 using XDA App
@yanuk... seems to be like u have not used linux before...Let me tell you how it works...Theres tons of companies (apart from thousands of enthusiasts) that write OPEN SOURCE DRIVERS for their hardware and submit it to the LINUX KERNEL maintainers(Linus torvalds included) example INTEL..If i m buying an ANDROID phone, i only want to pay for the hardware and not software..All drivers developed by the manufacturer shud be open source ..BUt instead its more like an abuse of the OPEN SOURCE community ..HOw CAn devs go ahead and hack the crap out of their phones, when they have trouble even porting newer OSes because of "some f****** proprietary driver" ...Screw the manufacturers ..I wish OPENMOKO had taken off when it had the chance..OPENMOKO = OPEN SOURCE OS +OPEN SOURCE HARDWARE with all datasheets, spec, circuit diagrams available..RUn whatever u possible can run on an it !!! My dream of having a completely Open (gtk runnin) geek device is still very distant..
sarfaraz1989 said:
@yanuk... seems to be like u have not used linux before...Let me tell you how it works...Theres tons of companies (apart from thousands of enthusiasts) that write OPEN SOURCE DRIVERS for their hardware and submit it to the LINUX KERNEL maintainers(Linus torvalds included) example INTEL..If i m buying an ANDROID phone, i only want to pay for the hardware and not software..All drivers developed by the manufacturer shud be open source ..BUt instead its more like an abuse of the OPEN SOURCE community ..HOw CAn devs go ahead and hack the crap out of their phones, when they have trouble even porting newer OSes because of "some f****** proprietary driver" ...Screw the manufacturers ..I wish OPENMOKO had taken off when it had the chance..OPENMOKO = OPEN SOURCE OS +OPEN SOURCE HARDWARE with all datasheets, spec, circuit diagrams available..RUn whatever u possible can run on an it !!! My dream of having a completely Open (gtk runnin) geek device is still very distant..
Click to expand...
Click to collapse
Seems like you have not worked in and managed any technology firms before.
I'm sincerely hoping your dream come true where you will own a successful openmoko company develop cutting edge technology with over 100 staff and offer your sw and hw for free with no claims to patent rights. All the best!
Sent from my LG-P500 using XDA App
Many phones like the 3d get the camera modded to improve resolution and unlock features. Why do the manufactures not have these capabilities open when sold if they are capable of them? Just curious
From the Best : Galaxy Note
sprintuser1977 said:
Many phones like the 3d get the camera modded to improve resolution and unlock features. Why do the manufactures not have these capabilities open when sold if they are capable of them? Just curious
From the Best : Galaxy Note
Click to expand...
Click to collapse
In the absense of official statements from the Carriers/Manufacturers to address this question, the only form of answer is left to speculation on the intents/motivations behind Manufacturers in undertaking specific actions.
I'll give it a shot off the top of my head:
1) Features were not thorougly tested (not signed off by management, not documented properly, not originally approved, not reviewed by the correct team, etc.)
2) Different hardware revisions of the device (Features might not work on all hardware revisions, hardware revision options weren't all known at the time of development, etc.)
3) Not under contract (Manufacturer hadn't agreed to develop or provide such features to the Carrier, Developers weren't contracted to work on these features, etc.)
4) Features are not official (A subset of any of the above possible situations. Developers added the features in but did not notify anybody, etc.)
I'm sure I've missed a few .. but hope that helps articulate some of the possibilties in the corporate software development world!
Thanks
From the giant: Galaxy Note
Hi! I've been developing apps for BB10 using cascades lately, and I would like to know if anybody is interested in that topic, and if you think it would be agood idea to have a thread for that (Sorry if I'm breaking any rules, I don't even know if BB10 devices are something xda users are inerested in)
Thanks in advance for your time and your attention.
ClowReedd.
Anyone interested in this?
... I don't know if nobody is interested in this platform, or if it is against the rules to request a forum for another platfomr as I did... I hope it is just against the rules, as it would be great to have more developers working on BB10 and cascades. The more competition there is, the better apps the final user will get
Thankd for your attention, and sorry if I'm doing something against the rules.
ClowReedd.
BB10 ? i think BB is so difficult to dev
bb
android is better than bb os
BB10 is awesome for devs!
I explored bb10 platform and it's awesome.People who develop for android can feel home here as they provide tools to port the apps with little or no coding.They support Native c++,adobe air,html5 apps.
The thing that interests me is they are very supportive giving away devices to devs and bounty promotions.
U guys have to understand that BB10 is evolving with time,see 10.2 is coming this or nxt month and it upgrades the Android runtime upgrades to 4.2.2
BB10 has android like in an emulated environment but can be easily usable with launcher app but currently it restricts many things like rooting and other but don't know abt that cause most devs and modders for bb10 are all-time bb users.So android hackers and modders may be able to root it.
Don't complain abt low app support,like bloatware on android phones which can be removed by custom roms.BB10 can use android app which are converted by tools which can be found everywhere.
I use most of the apps on my Z10 LE-instagram,snapseed,xda app,all....even games like NFS MW:victory:
Anyway just go through BB10 dev site and have a good time!
https://developer.blackberry.com/
Yes! I'm interested! The best thing of BB10 is that it natively allows Qt development!
Hi everyone,
I see so much hype about the Gcam and everyone trying to get it ported but it will never work as it should especially on Exynos devices.
I am wondering why does nobody try to port the S10 camera app? It has some benefits and features (software) that would come handy in our devices and it would be much easier to port as it is something like an updated version of the app which we already have.
I am also wondering why there is no S10 custom roms or S10 ROM ports for S9/S9+? The development for earlier phones is much more active, example S7/edge, but for S9/S9+ the scene seems dead? Maybe because everyone is loosing too much time on porting gcam?
Also if some of you know some telegram groups which have the above mentioned topics I would be thankful if you could post the links to join those groups. It seems that most of the devs are now using telegram instead of forums.
arnes_king said:
Hi everyone,
I see so much hype about the Gcam and everyone trying to get it ported but it will never work as it should especially on Exynos devices.
I am wondering why does nobody try to port the S10 camera app? It has some benefits and features (software) that would come handy in our devices and it would be much easier to port as it is something like an updated version of the app which we already have.
I am also wondering why there is no S10 custom roms or S10 ROM ports for S9/S9+? The development for earlier phones is much more active, example S7/edge, but for S9/S9+ the scene seems dead? Maybe because everyone is loosing too much time on porting gcam?
Also if some of you know some telegram groups which have the above mentioned topics I would be thankful if you could post the links to join those groups. It seems that most of the devs are now using telegram instead of forums.
Click to expand...
Click to collapse
Part of the problem is that for the last couple of years, Samsung has locked the America-bound phones, which puts a BIG damper on the whole development process. Locked bootloader= iOS knockoff. At least you can still install a camera APK, though. If you want a custom Sammy ROM now, gotta look overseas, and so many of those are just clones.
We are excited to announce the launch of our new GitHub project 'GCAM-Configuration-Collaborative', which aims to provide a base configuration for SGC GCam 8.8 port that can be easily modified and improved by developers and users alike.
With this project, we hope to create a collaborative community where individuals can share their knowledge and expertise to enhance the photography experience for everyone. By providing a solid starting point for SGC GCam users, we believe that we can empower individuals to take control of their camera settings and capture stunning photos in any lighting condition. Our project is open to anyone who wants to contribute, and we welcome feedback and suggestions from all members of the community.
Join us today and let's make SGC GCam even better together!
Join our ***Link removed by moderator***
We are setting just a few ground rules:
Changes must be applied to the most recent version of the approved configuration file that is available on GitHub. This will help ensure that the project is kept up-to-date and that contributors are working with the latest version.
When submitting changes, contributors should provide "before" and "after" photos to showcase the improvements made to the configuration file. This will help other users understand the impact of the changes and provide a visual representation of the differences.
All changes must be documented and described in the commit message or pull request. This will help other contributors understand the purpose and intent of the changes and make it easier to review and approve them.
Contributors should test their changes thoroughly before submitting them to the project. This will help ensure that the changes are working as intended and that they do not introduce any new issues or bugs.
Any changes submitted to the project should be respectful and follow the community guidelines. This includes avoiding offensive language, adhering to copyright laws, and respecting the opinions and contributions of other members of the community.
By establishing those clear rules and guidelines for contributing to our GitHub project, we hope you can help us creating a collaborative and productive community that is focused on improving the quality and performance of SGC GCam on S23/U but not limited to SGC as well.
To Maintainers, her's some benefits for your hard work!
Access to a community of like-minded individuals who are passionate about photography and optimizing camera settings.
Exposure to different perspectives and approaches to configuring camera apps, which can lead to new insights and techniques for improving photo quality.
The opportunity to share knowledge and expertise with others, and learn from their experiences.
Recognition and exposure for their work, as their contributions will be visible and available to other users who are interested in improving their camera settings.
The satisfaction of making a tangible impact on the photography experience of others, and contributing to a project that has the potential to benefit many people.
By emphasizing the benefits of collaboration and highlighting the potential impact of your contributions, we are inviting maintainers who are passionate about photography and eager to share their knowledge and expertise with each others and working as one to provide a decent experience with GCAM for our community.
Let's not forget that by committing your personal hard work into our GCAM-CONFIGURATION-COLLABORATIVE your changes and signature of picture style is shared widely to users that respects you and are eager to test experimental changes or use the latest stable config.
Initial release for SGC 8.8
- Just a base config, don't except anything fancy. It's open for tweaks and changes.
(Users or other maintainers can report here in XDA or make pull requests on Github.)
So this means better Gcam support on S23 and better configs for better pics and image quality?
iamnotkurtcobain said:
So this means better Gcam support on S23 and better configs for better pics and image quality?
Click to expand...
Click to collapse
Yes, the main goal is to enhance the experience and quality of pictures with GCAM. But it will initially depeneds on users, maintainers interested to work together.
Does this cover all series of S23? Or all Samsung flagships?
What's the best version of gcam out now? I'm on lmc 8.4. And javasabr-lmc15-v14.xml
@farovitus I have removed the Telegram link from your post per the XDA Telegram Policy. We do not allow the use of XDA to divert users to another platform. A project such as this posted on XDA must use XDA as its primary method of communication. Please read the Policy for more details.
Dead project?
Klaudas said:
Dead project?
Click to expand...
Click to collapse
Yeah. lol
No one bothers with this and XDA. Most of them are doing this on Telegram and have their own communities.