Related
I'm having a problem porting android market over to a absolutely vanillia AOSP 2.1r2. The files I'm using come from "GoogleBits-sdk7-v1.9" If you google search it you will find what I'm talking about. It is supposedly compatible with any aosp 2.1 running sdk 7 api's regardless of device... this doesn't seem to be the case.
Anyway the problem I'm having is an "unable to connect to server" error. I'm able to open android market, agree to the ToS, market loads, but fails when attempting to connect.
Gmail, & Google maps, Phone, Messageing, Lockscreen all work
Google talk, & Youtube force close, but not my main concern ATM.
Anyone that has experience building off of AOSP, your words of wisdom would be much appreciated. I'm also ruling out the idea of modifying another rom so please don't suggest it. Any changes to AOSP will be placed in the update.zip and tested on other devices for compatibility.
----------------
Background on my project if you're interested
----------------
I'm going for a "building block" rom, I'm wanting something that is 100% plug and play with any enhancement update.zips you want... GoogleBits, SenceUI, Blur, Cyanogen mod... etc etc. from something you can compile yourself if you wanted to from the android website. I'm wanting something that will be universally compatible regardless of handset in the future as long as someone compiles the current AOSP for it.
My understanding is that GoogleTalk interacts directly with the Market.
That could be your problem.
After perusing the forums for a while I'm considering loading a new ROM/Kernel. Maybe I'm to much of a noob to know but I can't find a thread that lays out the structure of Android. The stuff I can find assumes that I am already on intimate terms with this stuff, but I'm not.
I flashed CWM 3.1.0.1 which allowed me to clear caches and reset the battery gauge which has really helped. In trying to go further I'd like to piece the structure of the system together so I know where I am in the bigger scheme of things. I rely on the Epic for work. I can't afford to go down the wrong path and find myself in a far away town relying on a hotel internet connection to get back up off the ground. The picture I have is this:
Root lets me do the things I have mentioned before. Namely clear caches, backup my phone, reset battery meter, run some utilities to aid in device management. Similar to root or SU on *nix systems.
ROM drives the hardware and basic user interface, seems to me to be equivalent to the boot ROM and some lower level of OS functionality
Kernel is the actual software that runs on the device. This would be some OS and phone system overlay and the basic applications that show up in your applications folder. This provides your Sprint connection, network interface and the like
Applications are the other things that you actually run on the phone like games, social media programs GPS etc. Some come wrapped with a kernel, or they could be pick and choose.
I'm a bit fuzzy on where the ROM leaves off and the Kernel begins, maybe someone can clarify this.
Which leaves me here:
I see stuff that makes flashing new kernels and ROMs sound as if they are a magic elixir. I see posts that make it sound as if its a playground for folks who are hobbyists. Some posts talk about things that don't work any more with this flash or that. Where is the list of stuff that works and does not work for various mods?
My needs are very basic.
I need a reliable phone.
I need reliable Google mail & calendar (there are a few advantages to outsourcing corporate email to google).
Usable but not mission critical texting and GPS.
Better battery life.
This phone is for business. I do not need: social media, games, gadgets, widgets, toys.
Any light you can shed on the subject to help a brother out is appreciated.
Root = Elevated privilege access.
Kernel = The software that drives the phone.
Rom = The files on the phone's storage.
Apps = Also files on the phone's storage.
Root gives you the ability to do things the phone manufacturer did not intend for you to be able to do. (Think limited user account on Windows/Linux).
The Kernel is like the "engine" of the phone, w/o it the phone does nothing.
The Rom is the files on the phone, some are used by the kernel in order to make the phone work.
Apps... you know what these are. =]
The kernel controls the device, it has the drivers for hardware to make that hardware work.
The kernel is a Linux kernel built specifically for the device (phone) it will be run on.
The Rom is a collection of files to be installed onto the phone.
The Rom contains the operating system (the part that makes it an "android").
A Rom also includes apps, might include a theme (modifications to images, colors), and possibly numerous other modifications to the "stock" files.
The "stock" files, or a "stock" Rom, is what we are given by Sprint.
The different custom Roms you see available here on XDA are basically the stock files, modified by someone to their liking.
Some include a theme to give a custom look, most include modifications to make things "better" (ie hacked Sprint Hotspot, the 6 or 8 Lockscreen mod, etc).
There are many other aspects at play here, and much more that could be said about each item you listed, but the above is a generalized rundown.
Android runs on top of Linux, so the more familiar you are with Linux the better off you will be.
Do yourself a favor and take the time to read as much as you can, Google is your best friend.
=]
All features, full flexibility, no bloat -- one simple solution!
On the one hand, it is frequently being suggested to build into Lineage various apps and features. Most of these suggestions are required by some users only, would bloat the core ROM, or have other downsides. On the other hand, these apps and features are usually already implemented somewhere, most users want incremental updates and many would prefer a fully-featured ROM without GApps installed.
To satisfy those wishes and yet avoid the downsides, I suggest simply supporting F-Droid and microG instead:
Idea outline:
Provide API for and build in F-Droid Privileged Extension
Thus have a Store, with automatic updates, and all bells and whistles
Ship with (rebranded fork of) F-Droid pre-installed and a custom LineageOS repository pre-configured (like Guardian Project in F-Droid)
Add AOSP apps, Lineage apps and Lineage-specific versions / branches of apps to LineageOS repository
Use "unstable update" marker in F-Droid to beta test new versions, e.g. of launcher, locker, ...
For additional, bloating apps and features, have users install what's already there (for instance, Location Services: UnifiedNLP with LocalWifiNlpBackend)
Add to Lineage Wiki a curated list of well-tested app suggestions for basic tasks (for instance, WebDAV: DAVdroid, Tasker, Etar, ...).
Key Advantages:
Developer effort most efficiently used
Faster time to market, because much is already implemented
Higher quality, less bloat, more features by referring users to existing apps and joining efforts
Easier innovation, because versions of pre-installed / system apps are publishable like regular apps
Developers happy, because LineageOS is clean at its core
Enthusiasts happy, because they can built on a minimal ROM
End Users happy, because they can easily use ROM, using curated list of apps
Regular, normal app updates for all system apps and pre-installed apps through Lineage repository
Does not prevent using GApps, but improves life without
Major step towards fully featured ROM, and yet without any proprietary apps or services
For good reasons, it's what Google does, it's what GNU/Linux distributions do.
One framework will solve most problems, provide most features ever suggested.
This will make everybody happy.
tldr
Bump!!!!
1, 2, 3 - Fully agree. If I had a proper Play Store alternative I wouldn't need Gapps at all.
4 - Essential in what way? I'd say its best to have only AOSP apps and to let every user download the apps he uses.
There would be practically no bloatware available and the ROM would truly give users the best choices.
8 - Additional preinstalled apps? Rather not.
9 - Rather AOSP mail. Someone might not want to use K-9, but for those who do they can always download it.
10 - Same as 9, avoid preinstalling apps that are already provided by AOSP.
11 - Eleven is OK for me, but still I find it somehow way underpowered. I really miss Apollo from early CM days...
14, 15 - I agree on ROM type. Allow users to select nightly, weekly or stable update channel through settings. Regarding basic preloaded apps, it would be OK only by means of AROMA installer where you could choose which ones you actually want/need.
Cheers!
In this thread it is being suggested to build into Lineage various Launchers, Themes, Widgets, Apps, WebDAV support, et cetera. As a contrasting response to that, I suggest simply supporting F-Droid and microG instead. A Lineage repository for F-Droid could include all AOSP apps; F-Droids own repository would supplement this.
It appears to me, almost everything which has been popularly requested would thereby be solved.
dj_chapz said:
4 - Essential in what way? I'd say its best to have only AOSP apps and to let every user download the apps he uses.
There would be practically no bloatware available and the ROM would truly give users the best choices.
Click to expand...
Click to collapse
Here, "essential" refers to, more or less, what's needed to install other apps (launcher, browser, file manager),
but could be thought of as to include functions, which were typical for feature phones, too (basic messenger, dailer, calendar).
dj_chapz said:
8 - Additional preinstalled apps? Rather not.
9 - Rather AOSP mail. Someone might not want to use K-9, but for those who do they can always download it.
10 - Same as 9, avoid preinstalling apps that are already provided by AOSP.
11 - Eleven is OK for me, but still I find it somehow way underpowered. I really miss Apollo from early CM days...
Click to expand...
Click to collapse
These were just written-out to illustrate what would be possible.
I'll adjust the original post for clarity.
Anybody can fork it and add their ideas. Some people do not want to support fdroid. Keep it clean + gapps.
goorek said:
Anybody can fork it and add their ideas. Some people do not want to support fdroid. Keep it clean + gapps.
Click to expand...
Click to collapse
Even if F-droid wasn't preinstalled, could be a Lineage repo for it?
LineageOS IMHO should really seek to become the ROM for professional PIM, self-employed, small-business or even big-business device users which seek to avoid GApps and rely on a clean slim ROM. So I like many of grefnab's ideas but currently have no clear idea what the stakeholders of LineageOS have as main goals for the midterm.
Having everything App based in an "FOSS App Package" (as GApps and commercial/device App replacement) with advanced support by LineageOS and/or other main CustomROMs would be geat. See my post in What features would you like to see in Lineage that CM didn't have?
support 1-3
I really hope that this thread will get recognition. I really like the idea of having priviliged F-Droid build into the ROM.
That would make everything much easier.
I fully support the three first points
Provide API for and build in F-Droid Privileged Extensio
Thus have a Store, with automatic updates, and all bells and whistles
Ship with F-Droid pre-installed and a custom LineageOS repository (like Guardian Project) pre-configured
Click to expand...
Click to collapse
The rest is nice but I would put emphasis on the first three points. They seem like a real advantage to have.
Rephrased some sentences to clarify
This seems like a very good idea to me :good:
I mean it is basically the same procedure Google has in place to keep its apps up-to-date without people having to update their firmwares. Being able to update the apps independently from the rom would be a huge benefit in my opinion. While I don't use gapps on my phone at all, I understand, that some people find it essential. Therefore it would be a bad idea if this interfered with installing gapps in any way.
herrritschwumm said:
While I don't use gapps on my phone at all, I understand, that some people find it essential. Therefore it would be a bad idea if this interfered with installing gapps in any way.
Click to expand...
Click to collapse
This would not prevent installing GApps, it would simplify and improve usage without them, though.
+1 for having LOS F-droid repo and bundling F-droid and having fewer other preinstalled apps.
I think this thread is a very good idea!
Just a clarification on technicalities:
microG kinda requires signature spoofing. More specifically MicroG effectively has two principal frameworks inside -- location services and GCM. Location services would work regardless, but iirc for GCM to work properly the ROM itself would need a signature spoofing support. All other ways to enable spoofing employing needlepatch or whatever are ridiculously impractical and one cannot expect normal users to bother with them.
I have two phones (OP1 and OP3) and for both the choice is of exactly ONE custom rom only (based on LineageOS14.1) with a spoofing patch. Therefore applying spoofing patch into the main code base would be great. However the caveat here is that any app or framework like SafetyNET would most likely stop working. Since the developers decided to push for compatibility, I seriously doubt that they would implement signature spoofing.
They could try to implement the patch in a flashable zip like with root but I don't know if it is possible.
fully agree for spoofing support since we are out ot cm
Sent from my Nexus 5 CAF using Tapatalk
I would like to see signature spoofing built into lineageOS or an optional flashible zip, too. But right now a flashible zip could take a long time to flash. See: https://github.com/microg/android_packages_apps_GmsCore/issues/196
Sounds great.
dj_chapz said:
If I had a proper Play Store alternative I wouldn't need Gapps at all.
Click to expand...
Click to collapse
You could try Yalp Store, it's there in the F-Droid repository.
@grefnab: My flashable zip help those that want to automatically without any effort: remove GApps, install microG and F-Droid Privileged Extension.
1plus said:
Just a clarification on technicalities:
microG kinda requires signature spoofing. More specifically MicroG effectively has two principal frameworks inside -- location services and GCM. Location services would work regardless, but iirc for GCM to work properly the ROM itself would need a signature spoofing support. All other ways to enable spoofing employing needlepatch or whatever are ridiculously impractical and one cannot expect normal users to bother with them.
However the caveat here is that any app or framework like SafetyNET would most likely stop working. Since the developers decided to push for compatibility, I seriously doubt that they would implement signature spoofing.
Click to expand...
Click to collapse
Tingle is very easy to use, if you find something impratical just tell me.
SafetyNet do pass for me.
Hi all,
just wanted to provide some user experience.
I have solid experience in debloating the roms on all devices I use (Samsung phones in last 4 years, Shield TV) but one thing I came accross in Phoenix OS that looks very strange is
CZStatisticsProvider in system/priv-app folder. (I use rooted 2.2.1 OS)
Disabling this one causes Phoenix OS to act very unstable - refusing to install the app (soft reboot), constant error reports, to refusing to continue reboot/shutdown.
I guess I dont like the name of it - as for me purpose of debloating (incl. removing gapps if needed) is also to avoid collection of user data, and I would be happy to live with some negative effects (like missing Playstore).
However - this one refuses to leave the system.
Any thoughts?
Its very clumsy when you think that it has aosp like look and features but internally a lot of codes are bonded with every stock apps than the vendor ones only.
1.This is done intentionally to make it really difficult to port usps of such free but potential aftermarket OS.(like Task bar and notification bar,)
2.Genuinely ,it can be so Intents are bonded to various native apps to gather analytics from different devices for more bug-free and stable performance.
Otherwise ,there is nothing more in Phoenix OS than taskbar,drawer and notification bar (side bar).
Do you speak on behalf of development team?
One thing is the need to protect the app from porting - but we are speaking about the app which cannot be safely removed from the system, and is called Statistics Provider...
I am quite familiar with Android essential components, and this app is not there..
Have a great day!
That's What i told
@phnikola
As i said ,various ROMS have that (statistical Provider)like in Ressurection Remix to collect various data from various system apps to provide more stability ,and intentionally necessary.
like in miui ,a lot of apps are just junk but your system may go in loop when its not available there.It is there to protect Maker's interest .
Got it ?. Its not AOSP or Individual Freeroam developer project .Its a company investment so they always try to put collar upon there products
BTW ,the root official devs dont reply even on their forum ,so u cant expect them here,when i raised voice ,they banned me on phoenix forum with spam charge.
Hello everyone,
I've got a Smart TV with stock Android TV (v 11, can't disclose client , at the moment).
Is there any way to add a super minor customization to android tv ?
It's literally minor, it's adding an entry point for an App, which is not an App Icon Launcher, because they want it to look like integral part of the OS.
It could be anything like an Icon (next to the other system icons like settings, input, profile), or an Entry in system settings menu' , or something like that, to launch the Application.
It's so minor that redo all the work and get into AOSP is way too overkill, it would start a completely different project.
No, the client exclude the option to just have the App installed, they want the App as it was integral part of the Operating System.
I've read several documentations :
- Aosp : Way too many cons for such a small customization.
- Android Operator Tier with Custom Launcher : Could be viable to do a custom launcher, but the Smart TV is not eligible for operator tier (Not sold in leasing, do not sell any pay/linear channel, it's just a plain Smart TV)
- Custom Launcher on stock Android TV : Not viable, it would still be an Application with its launcher or would need some tricky configuration which wouldn't look like integral part of the OS at all.
- TIF (TV Input Framework) : Would just modify and recompile the TV App work ? I'm not sure if it is possible and how difficult it would be and if it is possible to "overwrite" just the TV System App on a Stock Android TV OS.
Do you have any suggestions how to achieve the desired "customization" without loosing all the built in supports/services that come with stock Android TV OS ? The simpler the better.
Thank you so much in advance!
from what you're explaining isn't a minor customization.
what you want is to customize the android tv launcher, however that launcher is an app just like everything else on the tvbox including your iptv app, youtube app, netflix app, etc...
so for your to achieve what you want, you'll need to have some dev knowledge, and you'll need to disassemble, modify and reassemble the launcher app + do whatever customization you need done.
it's not impossible, however it's not easy at all.
option2: you can hire a developer to develop your own tv launcher with whatever customization you want, probably won't be cheap, but will achieve exactly what you want.
option3: find an open-source tv launcher, use it, customize it as you like, you may or may-not need to hire a developer to do extra customizations, your cheapest, easiest, and quickest way to achieve what you're looking for. just google open source tv launcher, i'm sure you'll land on a few.
example:
Code:
https://gitlab.com/flauncher/flauncher
donmega_icecube said:
from what you're explaining isn't a minor customization.
what you want is to customize the android tv launcher, however that launcher is an app just like everything else on the tvbox including your iptv app, youtube app, netflix app, etc...
so for your to achieve what you want, you'll need to have some dev knowledge, and you'll need to disassemble, modify and reassemble the launcher app + do whatever customization you need done.
it's not impossible, however it's not easy at all.
option2: you can hire a developer to develop your own tv launcher with whatever customization you want, probably won't be cheap, but will achieve exactly what you want.
option3: find an open-source tv launcher, use it, customize it as you like, you may or may-not need to hire a developer to do extra customizations, your cheapest, easiest, and quickest way to achieve what you're looking for. just google open source tv launcher, i'm sure you'll land on a few.
example:
Code:
https://gitlab.com/flauncher/flauncher
Click to expand...
Click to collapse
Hello!
Thanks so much for the answer, Don Mega.
Damn i hope there was an easier way to add an icon.
I see...
No need to hire a developer.
I'm a Senior android engineering and I got a skilled team but we never had to work on the android TV OS system itself tho ( we're specialized on mobile apps and iot solutions, not tvs).
Btw .. I could develop a custom launcher but it may take time and as I said as far as I've read on documentation, a custom launcher would still need AOSP if the manufacturer want to override the system one.
Doesn't it ?
I ask 'cause AOSP is too much of an effort (at least just for an icon!) and several manufacturer who started on aosp and various customizations are now abandoning it (I already worked on a STB for British telecom and yeah, i didn't work on their custom OS specifically but i know they changed their mind in the end).
Probably because once you go that route, you loose all the support and services out of the box, and you need to take care of too many things to keep it up to date.
So they usually prefer to stick to Android tv stock version (wise choice).
If that's the case I suppose the manufacturer will be better find a more standard way to launch their app
Nimx said:
Btw .. I could develop a custom launcher but it may take time and as I said as far as I've read on documentation, a custom launcher would still need AOSP if the manufacturer want to override the system one.
Doesn't it ?
Click to expand...
Click to collapse
no need for flashing a different OS or Custom Rom to be able to install a custom developed app.
so if you make your own apk, all you need to do on the existing tvbox, enable unknown sources, to be able to install your own apk on there, it should be pretty straight forward.
put the apk on a usb stick, plug it into your box and navigate to any file manager app, you'll be able to find your apk, click on it and install, on your remote control press the HOME button, it should popup a msg asking which launcher you want to load, since now you developed your own launcher and the old launcher is still there, choose which launcher you want to be default. you can always go into settings > apps and disable the old launcher so if anyone presses the HOME button again, it always defaults to the new one you developed.
so short answer, no you don't need AOSP or any type of Custom Rom
donmega_icecube said:
no need for flashing a different OS or Custom Rom to be able to install a custom developed app.
so if you make your own apk, all you need to do on the existing tvbox, enable unknown sources, to be able to install your own apk on there, it should be pretty straight forward.
put the apk on a usb stick, plug it into your box and navigate to any file manager app, you'll be able to find your apk, click on it and install, on your remote control press the HOME button, it should popup a msg asking which launcher you want to load, since now you developed your own launcher and the old launcher is still there, choose which launcher you want to be default. you can always go into settings > apps and disable the old launcher so if anyone presses the HOME button again, it always defaults to the new one you developed.
so short answer, no you don't need AOSP or any type of Custom Rom
Click to expand...
Click to collapse
The manufacturer obviously don't want users to do this procedure to choose the new launcher, but should be able to persistently active it overriding the system one. And that's why I thought custom ROM was needed.
If that's not true then your solution is the perfect one
donmega_icecube said:
no need for flashing a different OS or Custom Rom to be able to install a custom developed app.
so if you make your own apk, all you need to do on the existing tvbox, enable unknown sources, to be able to install your own apk on there, it should be pretty straight forward.
put the apk on a usb stick, plug it into your box and navigate to any file manager app, you'll be able to find your apk, click on it and install, on your remote control press the HOME button, it should popup a msg asking which launcher you want to load, since now you developed your own launcher and the old launcher is still there, choose which launcher you want to be default. you can always go into settings > apps and disable the old launcher so if anyone presses the HOME button again, it always defaults to the new one you developed.
so short answer, no you don't need AOSP or any type of Custom Rom
Click to expand...
Click to collapse
Just to keep you updated.
Custom launcher need user to set the new one.
But we found a possible solution without the burden to do a custom Rom.
Adding a new Ad-Hoc button on the Remote controller to launch their ecosystem settings app and/or a custom launcher (since this Smart Tv is a new model that will initially be delivered to several europe countries).
In this way it will look quite integrated in the android tv system, and the android TV OS will be always kept up to date from regular google updates, without all the issues plaguing custom roms like it does for other manufacturers.
Thank for your help
Nimx said:
Just to keep you updated.
Custom launcher need user to set the new one.
But we found a possible solution without the burden to do a custom Rom.
Adding a new Ad-Hoc button on the Remote controller to launch their ecosystem settings app and/or a custom launcher (since this Smart Tv is a new model that will initially be delivered to several europe countries).
In this way it will look quite integrated in the android tv system, and the android TV OS will be always kept up to date from regular google updates, without all the issues plaguing custom roms like it does for other manufacturers.
Thank for your help
Click to expand...
Click to collapse
sometimes i wish i was a developer, glad you found an easy solution.
thank you
It's still quite easy to become a developer due to high demand.
Not sure how old are you but I started when I was 34 yo by myself with no prior experience.
Nowadays, 5 years later, I Interview many candidates and I can tell the discriminating factor is not prior studies but dedication, high IQ (logic and abstraction wise) and learning speed.
Good luck if you'll ever decide to get into it
i'm 44 i have no patience for programming in general, I never did, I'm a full time network admin, and really into hardware a lot more than software.
but when it came to Android, i got my hands dirty flashing custom roms on all my phones. i started to customize my own roms for tv boxes.
but I kinda wish I did have some android dev skills, it's the only thing i end up outsourcing when needed.
thank you