Why SGA is a "Legacy or Low Activity Devices" [CMStats] - Galaxy Ace S5830 General

It's said that the SGA is little used, but it's in de Top10 of CyanogenMod Stats
stats.cyanogenmod.com/ (Find "Cooper")
Why Cyanogen not support officially our decive?
I've been keeping the information on that page and it is amazing how many people installed ROMs KANGs
Date Users
17 10.324 ======NOVEMBER
18 10.557
19 10.757
20 11.011
21 11.212
22 11.435
23 11.636
24 11.853
25 12.084
26 12.324
27 12.545
28 12.757
29 13.023
30 13.277
1 13.506 ====== DECEMBER
2 13.750
3 13.965
4 14.197
5 14.386
6 14.703
7 14.918
8 15.174
9 15.374
10 15.632
11 15.823
12 12.767
13 12.976
14 13.216
15 13.465
16 13.721
17 14.057
18 14.264
19 14.485
20 14.727
21 14.993
22 15.159
23 15.396
24 15.535
25 15.768
26 16.012
27 16.242
28 16.523
29 16.786
30 17.038
31 17.214
1 17.487 ====== JANUARY
2 17.820
3 18.082
4 18.311
5 18.621
6 18.940
7 19.234
8 19.501
9 19.792
10 20.096
11 20.397
12 20.696
13 20.980
14 21.290
15 21.586
16 21.948
17 22.268
18 22.538
19 22.799
20
21
...
Click to expand...
Click to collapse

A huge number of people have moved on from CM7 to various 4.0.x firmware. For example I have four phones on ICS builds and one on Gingerbread. As more people move on the devices left on 2.3.x show as a bigger percantage. Do those stats show CM9 numbers yet? As there is no official release yet they may not show. I don't know if that's right but its a possibility. As for it being a legacy device on XDA it is purely a numbers game. Other phones have more users on their section so the Ace gets pushed down the rankings.
Sent from a phone with an app.

Related

Switching to MIR?

Hi, I just wondering when is ubuntu team switching to MIR instead of Android graphical service. I read something but it butI have no clear if this movement its going to suposse any change in the smoothness, if maybe its gonna improve it or not. Any realease date for that?
Thanks!
well... it (XMir) will be on 13.10 (saucy) Desktop along with unity (next). X11 server on touch/phones
milestone proposed dates:
•Alpha 1 – June 20th
•Alpha 2 – July 18th
•Alpha 3 – August 1st
•Beta 1- September 5th
•Final Beta – September 26th
•Release Candidate – October 10th
Final Release - October 17th
Source OmgUbuntu
Sent from thinkpad t420 Ubuntu 13.10

Nexus 9 model by serial number

Hello friends,
I am planning on purchasing a Nexus 9 and from my understanding you can identify if the model is a bad one (light bleeds, bad buttons). I was wondering if anyone knows the starting serial number of the Nexus 9 which does not have any of these issues.
Thanking you.
There is no guarantee, but models starting with "HT5" (meaning built in 2015) are probably recent enough to have all the kinks worked out. (HT51 = Jan, HT52 = Feb, etc.)
Sent from my Nexus 9

For those with bootloop issues: Report your device type and when the problem started.

Hello,
As you may aware the bootloop issue is not limited to Nexus 6p but happened to Nexus 5 onwers as well.
I wanted from this thread to survey If this issue is limited to one type of device or common among all types Nexus 6P devices (32GB/64GB/128GB)
I own two Huawei Google Nexus 6P one with bootloop problem (64 GB), bought in January 2016 and bootloop appeared after approxmitaly one year and the other new (32 GB) just bought recently with no problems so far. I used to read mutliple threads on the bootloop issue before my phone got it. I would suggest for all new onwers to enable the USB debugging and the OEM Unlocking (just in case). I have failed to enable these options in my first Nexus and I was not be able to power up the device even with heating.
You can either vote or type the following:
Device type: Nexus 6p 64 GB
Purchase date: January 2016
Bootloop appeared: approxmitaly after 14 months
Comments: Noticed the low battery performance before the bootloop problem. Device shutdown around 20%
Device Type: Nexus 6p 32GB (Refurbished)
Purchase Date: December 2016
Bootloop Appeared: November 2017
Bricked: May 2018
Comments: Ran custom ROMs, overclocked EX Kernel, used only for social media/texting, browsing and youtube, nothing intensive. Suddenly one morning it was a brick, nothing would respond.
I would like to add, this problem lies with the Snapdragon 810/808 (bad soldering) Chipset, the OP2 has the same issue and so does the LG V10. I don't think the storage size would affect it.
Device type: Nexus 6p 64 GB
Purchase date: Dec 2015
Bootloop appeared: approxmitaly after 17 months
Comments: Noticed the low battery performance before the bootloop problem. Device shutdown around 20% (same as you)
Suprisingly bootloop fix method is not working either.
Device type: Nexus 6P 128gb
Time of purchase: when it first came out at 2015.
CPU detached without bootlooping: I never knew the device only had 4 cores working sometimes.
Bootloop date: around May 30 2018
Flashed quad core: around May 30 2018
Stop bootlooping and 8 core partially working: Around June 7-12. I went to San Francisco at this time. My home is at the other side of the world. Idk how it started working again.
Started bootlooping again: June 12.
Comments:
My battery usually shuts down at 50-60% when I consume so much power at once. When I only listen to music, it can go all the way to 0% without early shutdown. The early shutdown depends on how you are using your phone. Device battery health: around 928- 1064/3450 mAh.
Device type: 6P 128gb
Purchased: October 2016, replaced the fast draining/early shutdown battery myself in May 2018, was much improved.
Bootloop: July 4th 2018
Comment: The day before bootloop I accidently left the phone sitting in the hot sun in vehicle. When I found it the cpu and battery were at 53 degrees C. I got it cooled down and everything seemed to be working fine. At time of bootloop it was under no particular stress. I hit the menu button to close some background apps and it shut down and started bootloop. Can't even get into recovery.
Time of purchase: Device was bought of a friends two weeks ago. (End of June 2018, was originally bought in 2016)
Bootloop date: Around 4-5 July 2018
Fixed Used: heat / draining battery down, then unlocking OEM bootloader, then flashing (still haven't decided to shut down the faulting cpu, too upset about the potential loss of perfs)
Since then, flashed TWRP, Rooted with magisk, made full backup (OS + EFS) and fingers crossed !!
Device type: Nexus 6p 64 GB
Purchase date: Used off Ebay Dec. 2016
Bootloop appeared: Aug 2018
Comments: Replaced the battery shortly after buying it, as it would shut down in the cold, and then randomly when the battery was below 30%. Rooted, running ABC rom 8.1. Unable to enter TWRP.

Honor 10 Updates

It seems updates are very slow for this device? I mean it's still on May security patch and now we are in July.. Also my 2 year old Honor 6X is on June security patch, how come my new 10 isn't

Question Honor 50 mui 6

Hi all.
Looking for info about honor 50 mui 6 for east europe.
Will be there update in the q2 of this year?
AnakinVN said:
Hi all.
Looking for info about honor 50 mui 6 for east europe.
Will be there update in the q2 of this year?
Click to expand...
Click to collapse
We're still 1 month short of Q2 so hang in there. I'm also looking forward to this update to see how 12 would change the experience.
Interesting how this phone is so unpopular. I bought it for 200 euros new/unlocked
Just got the Magic UI 6 update this morning. 1.8GB and it installed in a couple of minutes, actually way faster than the previous security update I got.
Looks the same as the previous, Andoid 11 based version but I did notice some small tweaks here and there and the new animations are nicer.
The bug where you can't swipe across the bottom to switch apps is still there (for me at least).

Categories

Resources