As an app developer, I find b.android.com (Android Issues) to be very valuable even though it isn't really maintained and is quite limited in its capabilities.
The good news is that there are indications that they are good to start maintaining it,e.g.:
http://groups.google.com/forum/?fromgroups#!topic/android-contrib/H1jjtoKjucI
The bad news is that they are making changes to its scope which will make the issues database pretty much useless for app developers.
I'm not surprised to see them close issues that dealt with Google apps or consumer facing issues in general - it was never meant for that and wasn't working. Google is now directing consumers to their product support services, and I think they are simultaneously really working to improve those consumer support services.
I'm much more concerned that they are planning to limit it to AOSP. I think that is in line with its original purpose, and many may applaud this move - but it makes it useless for me as an app developer. Quite simply - I need to know about issues on all Android devices, not just AOSP.
So, I think this could be an opportunity for XDA to expand their developer services. I actually think that the issue database could work much better at XDA then it has at Google. The Android issue tracker was always desperately in need of the kind of care and maintenance that XDA developers could give it. It also needed an appearance of impartiality and separateness from Google - there has always been a certain combativeness and anger on the issue tracker that wasn't productive. Finally, I think it could benefit from being more code and discussion friendly. Issues call for solutions, and the limitations of the current issue tracker meant that while the issue was listed at b.android.com, we had to go to stackoverflow for the discussion and the solution.
Hi guys,
Just curious, anyone uses REALTOR.ca app in Android here?
Because, here's the deal.... I'm actually the analyst for our app development and we're doing some major revamp to that app.
Now, a little disclaimer: the purpose of this thread is solely to discuss feedback on the app (I'm not a REALTOR(R) and will not be able to answer real estate questions), and my posts does not reflect my employer (Canadian Real Estate Association). This is a very non-official thread, so to speak.
A little background; we just rebuild our iPhone app into 2.0 and the feedback has been... lacklustre lol... Some thinks it's awesome, but others (most?) just want their old app back. Now, I personally want to engage the users more to avoid the pain with our Android app, but due to legal issues, business decisions, etc... I cannot create an "official feedback channel". So if you can somehow "forget" I'm an employee with CREA, please feel free to say what you think about the REALTOR.ca app.
Thanks folks
PS: What's in the works for now for Android 2.0
- Google Map (no more Bing Map) (this will solve all you KitKat users issue with the loading crap)(did I just say crap...? No I didn't...)
- Updated layout. More intuitive, side slides menu, better home screen, simplified filters (but advanced still there).
- Tablet support. Auto-detect device and display accordingly.
- New Near Me functions, new Open House functions, notes, notifications, etc...
- a bunch of bugs. Seriously, a lot of it. So much that we're thinking of releasing another update in the interim to address them.
PPS: If anyone in the real estate market and wants to know what I'm talking about, it's this: Play Store
PPPS: I don't think this app is "commercial", since it's free and stuff... but if I'm wrong, please feel free to delete this thread, mod. Thanks.
Hi everyone,
Here is a little history first. In 2014 I helped develop a traffic counting app for an engineering buddy. I designed the UI's, the flow charts and wrote the 275-page illustrated, developers manual. The developer had it working in less than 6 weeks, thanks to, as he said, "to the awesome documentation provided". The app has been in use since then and has worked flawlessly on the original 24 tablets I originally purchased for him.
Recently, we have been asked to bring the app to a wider audience so, my question is, "Is there a way to prepare an image of the Android OS containing only the setup we need, and then clone it to the new tablets?" The app is designed as engineering tool and is not listed through Google Play and as such, it does not require most of the bloatware found on the new tablets. The app does require the use of photos, some file management along with network connectivity to send and receive the various data files required and produced by the app.
I have limited experience in rooting, but I have been successful when I done it on my Samsung phones.
As a certified Graphics Designer/Windows and Mac tech/COVID-19 survivor (nearly killed me, literally...LOL), I am aware of the amount of work that goes into aiding people with their "little" projects. Any help or direction in this matter would be deeply appreciated.
This may be stupid, but I couldn't find any resources regarding this. We have custom recoveries for android devices but why isn't there custom bootloaders like there is for PCs ? Like in the PC space we have the likes of reFind and gnu grub.
Thanks
There are some instances of alternate bootloader projects. Just that they are not popular,
[Bootloader] LK for Xperia T
LK for Xperia T LT30p Only - Unlocked Bootloader Required WARNING 1: This modification makes changes to the devices partition table. I (lilstevie) am not responsible for any damage to your device or data loss that may occur. WARNING 2: ICS...
forum.xda-developers.com
EFIDroid
EFIDroid is a easy to use, powerful 2ndstage-bootloader based on EDKII(UEFI). It can be installed one-click with the EFIDroidManager app. You can add/remove/edit multiboot ROM's. There's no special support needed by ROM's or RecoveryTools(no...
forum.xda-developers.com
The developer of EFIdroid stopped developing in 2019.
efidroid on Android 9 and 10 devices ? · Issue #152 · efidroid/projectmanagement
Hi, I just want to know if efidroid supports devices with 6 GB RAM and 64/128 GB Storage devices running Android 9 and Android 10 ? thanks.
github.com
Not to mention you would need OEM's to cooperate....
Thanks @karandpr for that github comment a lot of info there. Thanks @galaxys too. So a quick summary would be that the reason is that for the bootloader to work smoothly there has to be support from the kernel too, which the OEMs should do and probably would not. But I didn't think about the support in the kernel was an issue. That does seem to be a lot of work and I see the reason now.
al_l_en said:
Thanks @karandpr for that github comment a lot of info there. Thanks @galaxys too. So a quick summary would be that the reason is that for the bootloader to work smoothly there has to be support from the kernel too, which the OEMs should do and probably would not. But I didn't think about the support in the kernel was an issue. That does seem to be a lot of work and I see the reason now.
Click to expand...
Click to collapse
I don't think Google intends to open up android anymore. They want restrictions like iOS but pretend to be open source for the "goodwill". What's the use of AOSP if you cant effectively install it on a device or your important apps don't work?
I believe PinePhones are the ones that can have truly open-source compatible hardware. The specs are underwhelming but the community is really good.
You can get spares easily and the battery is removable.
Only thing is they are mostly out of stock.
karandpr said:
I don't think Google intends to open up android anymore. They want restrictions like iOS but pretend to be open source for the "goodwill". What's the use of AOSP if you cant effectively install it on a device or your important apps don't work?
I believe PinePhones are the ones that can have truly open-source compatible hardware. The specs are underwhelming but the community is really good.
You can get spares easily and the battery is removable.
Only thing is they are mostly out of stock.
Click to expand...
Click to collapse
Yeah those are great but the problem is that they are not usable for "normies" which will prevent mass adoption and hence cannot have a sustainable business model.
But I think google is not the only one to blame, like couldn't the OEMs actually provide bootloaders that can boot signed os images. Or is there any technical or security difficuties in doing that.
al_l_en said:
Yeah those are great but the problem is that they are not usable for "normies" which will prevent mass adoption and hence cannot have a sustainable business model.
But I think google is not the only one to blame, like couldn't the OEMs actually provide bootloaders that can boot signed os images. Or is there any technical or security difficuties in doing that.
Click to expand...
Click to collapse
Normies are afraid to change the default browser, so bootloader is really out of their leagues.
Phone tinkering is a hobby, not a necessity. Phone tinkering itself is not a sustainable model.
Google is to blame primarily. Because they have a stringent list of requirements for devices to pass CTS. You can read the bootloader requirement and judge yourself.
Android 11 Compatibility Definition | Android Open Source Project
source.android.com
Without passing CTS, devices cannot use Google apps, they cannot get push notifications and they cannot pass SafetyNet checks used by most banking apps.
At the end of the day do I want to spend 100s of hours to bring a feature to an android phone which will probably be used by 10 users and deprecated by the time I finish doing it?
or do I want to buy a phone which will allow me to tinker freely in a community and ecosystem which allows modification?
For our tinkering pleasures, Pinephone is the way to go for now. They have support from Manjaro, Debian and KDE. Which is a big thing IMO.
Or else there you can roll your thing in RaspberryPi?
While going through related details I found an article about google probably switching to hardware based safetynet checks which could be ending google play compatibility on custom roms.
It really seems like google is using security as an excuse to make sure that there are no competitors in their business space.
Maybe this is because I have been only doing web development and only started learning app dev, but the reasons google use for CTS like for enforcing DRM, is also handled on websites while allowing openness and being neutral (or maybe the web is not as secure as something like this, so forgive me if I am wrong). Android could really take pages off the web ecosystem for being a neutral platform.
I really appreciate the patience for hearing out and also the references(and the rabbit holes that it was followed by) really taught me a lot about general android architecture.
al_l_en said:
While going through related details I found an article about google probably switching to hardware based safetynet checks which could be ending google play compatibility on custom roms.
It really seems like google is using security as an excuse to make sure that there are no competitors in their business space.
Maybe this is because I have been only doing web development and only started learning app dev, but the reasons google use for CTS like for enforcing DRM, is also handled on websites while allowing openness and being neutral (or maybe the web is not as secure as something like this, so forgive me if I am wrong). Android could really take pages off the web ecosystem for being a neutral platform.
I really appreciate the patience for hearing out and also the references(and the rabbit holes that it was followed by) really taught me a lot about general android architecture.
Click to expand...
Click to collapse
Theoretically, Google can end GPlay compatibility on Custom ROMs anytime they wish. It's just that lot of App Developers don't use SafetyNet the way it is intended and Google doesn't roll out its strict check. They do it once in a while.
They don't have any competitors in their business space. It's a very well-thought monopoly.
CTS restricts Google Play API access to vendor operating systems. So vendors like Samsung, OnePlus and others have to play by their rules. IIRC, the cost of Play API is around 15$ per device but it is subsidized for large quantities.
End users don't really care about Play API. But App Developers do.
Without Play services, there is no easy way to integrate push notifications, ads, maps, analytics, metrics, and so on. Rolling your own thing will take years to develop and won't work as seamlessly as the play service counterparts.
I don't think Google will ever cede their monetary interests for open collaboration.
karandpr said:
I don't think Google will ever cede their monetary interests for open collaboration.
Click to expand...
Click to collapse
Yeah that's for sure. The only way this monopoly can break is when an opensource alternative to google play services and other apis exist and while doing that it must be compatible with the existing google apis. And that is probably not going to happen in a long time. Although microg does solve this to some extent, but still it is a second citizen.
Some of the functionality is already there, like most of the google apps like docs and drive could replaced by nextcloud and then maps could be replaced by osmand. If some company, preferably an OEM, comes and integrates all of these into a package maybe there's hope. I think /e/ os tries to do this to some extent.
You might find this resource useful. As they have gone over a comprehensive set of bootloader software and tried to outline their primary features in detail. Hopefully, you’ll be able to determine the best one for your use case. https://www.ubuntupit.com/best-linux-bootloader-for-home-and-embedded-systems/
Hi, as some will obviously know, google is forcing a change in android development to be more like ios. Some developers and users wont even notice or care. Others may find the changes fundamental and devastating.
Some of the changes have come about in version 11 but will be fully implemented by 12-13. These changes are going to limit access to android file system. The way apps work and limit what you can install, copy, write to external usb etc. Others will mean total lockdown of security from installing apps and google spyware controlling what you can change.
Over the years we have all seen many versions of android in countless devices with as many custom iterations and mods. In a way. Us users and the developers have shown what's possible with imagination skill & ingenuity and happily let google lead us down the garden path making billions in revenue from our devoted support. Not everyone could see the control manipulation, development and exploitation. Not everyone even cared.
But it seems now that free reign google has given us in ability for hacks & mods and and the devices android can can be used on is coming to an end. Google is yanking its chain and reeling us in.
If you think scoped storage, or more play store control will just be an inconvenience think again.
Developers and genuine android experts will know this and will probably already be aware of some solutions. I hope so. As the thread count and discussions on this balloon maybe some will consider a fork of huawei's stripped down versions of android might be an option, however we feel about china. Let's hope some options will come to light soon.