Closed
Bug 1018142
Opened 10 years ago
Closed 10 years ago
[flatfish][TCP] Everything.me not available on home screen
Categories
(Firefox OS Graveyard :: Gaia::Everything.me, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: steve, Unassigned)
References
Details
(Whiteboard: [flatfish][TCP] )
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release) Build ID: 20140527133511 Steps to reproduce: Got to the home screen 1st page. Actual results: There are no everythingMe groups as are usually provided (Social, Games, Music, Showbiz) Expected results: The icons should be there.
Updated•10 years ago
|
Whiteboard: [TCP]
Updated•10 years ago
|
Blocks: flatfish
Status: UNCONFIRMED → NEW
Component: Gaia::Homescreen → Gaia::Everything.me
Ever confirmed: true
OS: All → Gonk (Firefox OS)
Hardware: All → ARM
Summary: [flatfish] there are no group icons on first home screen → [flatfish][TCP] Everything.me not available on home screen
Whiteboard: [TCP] → [flatfish][TCP]
Comment 1•10 years ago
|
||
EverythingMe Collections ("groups") are defined in the build configuration. If no Collections are specified, none will be available on the homescreen. Can you confirm your build config contains Collections?
Flags: needinfo?(steve)
@amirn This build was provided by the tablet supplier so I don't have access to their config. If you give me a pointer I'll look at the defaults as supplied by Mo for flatfish
Flags: needinfo?(steve)
Comment 3•10 years ago
|
||
(In reply to Steve Lee from comment #2) > @amirn This build was provided by the tablet supplier so I don't have access > to their config. If you give me a pointer I'll look at the defaults as > supplied by Mo for flatfish Then it is possible that the supplier disabled E.me features. The homescreen configuration is in homescreen/build.js: https://github.com/mozilla-b2g/gaia/blob/master/apps/homescreen/build/build.js#L198 Jason will probably have more information about which devices ship what.
Flags: needinfo?(jsmith)
Comment 4•10 years ago
|
||
I actually don't know much about configurations in regards to flatfish.
Flags: needinfo?(jsmith)
Comment 5•10 years ago
|
||
(In reply to Amir Nissim (:amirn) from comment #3) > (In reply to Steve Lee from comment #contacted@amirn This build was provided by the tablet supplier so I don't have access > > to their config. If you give me a pointer I'll look at the defaults as > > supplied by Mo for flatfish > > Then it is possible that the supplier disabled E.me features. The homescreen > configuration is in homescreen/build.js: > > https://github.com/mozilla-b2g/gaia/blob/master/apps/homescreen/build/build. > js#L198 > > Jason will probably have more information about which devices ship what. FYI, the configuration was determined by Mozilla. Francis, do you remember whom should be contacted to for this?
Flags: needinfo?(frlee)
Comment 6•10 years ago
|
||
hi All, in Flatfish, everything.me was removed due to Flatfish was targeted to sell in China market. and everything.me couldn't full fill Chinese market need. loop Fred and EJ who made this change.
Flags: needinfo?(frlee)
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Comment 7•10 years ago
|
||
Personal opinion. Flatfish is currently not a product, yet, in the general market. From the perspective of TCP, most of contributors came from everywhere around the world. Should we reconsider to pull back Everything.me, despite of the 'target market'? This could be good for the development of the 'pure' FxOS. Thanks.
Comment 8•10 years ago
|
||
(In reply to William Liang from comment #7) > Personal opinion. Flatfish is currently not a product, yet, in the general > market. From the perspective of TCP, most of contributors came from > everywhere around the world. Should we reconsider to pull back > Everything.me, despite of the 'target market'? This could be good for the > development of the 'pure' FxOS. Thanks. This solely depends on where consumer devices launch and where it be be mainly used.
You need to log in
before you can comment on or make changes to this bug.
Description
•