4

[Submitted] Clock widget taking unnecessary space

Thread Status:
Not open for further replies.
  1. chandertalreja Gingerbread Jan 8, 2017

    chandertalreja, Jan 8, 2017 :
    the clock widget is taking unnecessary extra space ,,
     

    #1
  2. chandertalreja Gingerbread Jan 8, 2017


    #2
    F_Yuriy_Tomashun_LLYu likes this.
  3. F_Yuriy_Tomashun_LLYu Cupcake Jan 8, 2017

    F_Yuriy_Tomashun_LLYu, Jan 8, 2017 :
    I have exactly the same! Time widget became for no reason to 3x3 size after I've updated to android 7.
    My friend did the same, but he has 3x2 size for the same widget!

    As well, when my network internet is turned off, it has 'x' near the signal, which is quite annoying...
     

    #3
  4. F_Yuriy_Tomashun_LLYu Cupcake Jan 8, 2017

    F_Yuriy_Tomashun_LLYu, Jan 8, 2017 :
    Found one interesting thing - If I will install Google launcher - time widget becomes to 3x2.... in Oneplus launcher it's 3x3..
     

    #4
  5. G_Itay_Sasson_XInr Cupcake Jan 11, 2017


    #5
  6. DeMichaelis Froyo Jan 18, 2017


    #6
  7. MarshmallowDerp Cupcake Jan 22, 2017

    MarshmallowDerp, Jan 22, 2017 :
    I found that installing the Google clock and using the Google clock widget is almost the exact same as the OnePlus clock, except it is bigger like the one before the system update and is resizable to 3x2. Hope this helps!
     

    #7
  8. amitssj Honeycomb Jan 22, 2017

    amitssj, Jan 22, 2017 :
    have you tried removing the widget and adding it back
     

    #8
  9. chandertalreja Gingerbread Jan 22, 2017


    #9
  10. metalswarm Eclair Jan 22, 2017

    metalswarm, Jan 22, 2017 :
    Yeah even Google Clock widget is a bit oversized as well. I found one way to fix this is use a custom launcher like Nova. Lets you resize everything even more than stock. But at least for me I enjoy the stock launcher so I just deal with it.
     

    #10
  11. Mich O. Ice Cream Sandwich Jul 2, 2018

    Mich O., Jul 2, 2018 :
    Hello @chandertalreja,

    This is from the OnePlus Bug Hunters.

    If this issue persists on the latest build, please raise a new bug report so that we will look into it again. This thread will now be closed.

    Thank you and have a great one.
     

    #11