Oct 29 2014, 06:39 PM
QUOTE(super_evil_alien @ Oct 29 2014, 05:35 PM)
System image might be uploaded on 3rd November but the OTA rollout *might* only be for Nexus WiFi devices.
Why? Probably because American carriers are making d*ck moves again.
The updates should go something like this:
Nexus devices -> Within first 2 weeks
Motorola -> Within a month
HTC -> 2 months for unlocked devices like those in Malaysia
Samsung -> 3 months for S5 & Note 4 (need lots of time to reskin the lolipop stuffs in new touchpiss version) & the other devices in 6 months
Sony -> Honestly I don't know because because their update schedule is all over the place.
okay, Samsung, Sony out. How about LG? Motorola doing good.Why? Probably because American carriers are making d*ck moves again.
The updates should go something like this:
Nexus devices -> Within first 2 weeks
Motorola -> Within a month
HTC -> 2 months for unlocked devices like those in Malaysia
Samsung -> 3 months for S5 & Note 4 (need lots of time to reskin the lolipop stuffs in new touchpiss version) & the other devices in 6 months
Sony -> Honestly I don't know because because their update schedule is all over the place.
QUOTE(super_evil_alien @ Oct 29 2014, 06:11 PM)
Depends.Some may agree but aside from the amount of bugs I think there are some differences between the custom roms.
CM -> Just build a stable stock AOSP build with some additions. The extra additions such as new camera app & theme engine are party to make CM more interesting to OEMS so they will hire CM to maintain OS for their devices.
AOSP -> Lazy build. As long as the base build is stable it's good to go.
PAC -> Just dump all interesting things that PA,CM and others did together in single ROM
PA -> Arguably the most interesting custom rom maker with neat ideas (DSB, Hover, PIE etc2)
Quite lot of custom rom maker still rely on CM team for device upbringing because they are very good at that.
good info. agreed, many rom baker rely much on cm. If future don't want to buy nexus anymore, motorola flagship or OnePlus One are good choice.CM -> Just build a stable stock AOSP build with some additions. The extra additions such as new camera app & theme engine are party to make CM more interesting to OEMS so they will hire CM to maintain OS for their devices.
AOSP -> Lazy build. As long as the base build is stable it's good to go.
PAC -> Just dump all interesting things that PA,CM and others did together in single ROM
PA -> Arguably the most interesting custom rom maker with neat ideas (DSB, Hover, PIE etc2)
Quite lot of custom rom maker still rely on CM team for device upbringing because they are very good at that.
Quote
)
Wipe cache/dalvik cache and reboot then all ok now. From my experience with this phone, cant UV too much ( for my phone 700
Mind sharing any kernel tweak or mostly stocK? 
, wait for N6 then build , topkek 
0.0522sec
0.52
7 queries
GZIP Disabled