• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [5.1.1][UNOFFICIAL] Paranoid Android 5.1 [12.30.2015]

Does anyone know if this ROM has the same problem as the cm 12.1 Roms where whenever you use a 3rd party viop type app such as WhatsApp or Facebook messenger voice that the other person can't hear you? On cm roms for some reason the mic doesn't work if your using those.
 
Mine right now.

Screenshot_2015-05-20-13-52-44.png
 
Seraph08 said:
IMO, themes are gross.
Click to expand...
Agreed. They needed a theme engine for 1.5-2.2...since GB forward Android's not been horrible looking(would love a native toggle between material light/dark like that's present in some apps) . My one and only gripe is that app devs should be forced to use new GUI guidelines and stop using deprecated images and styles from Froyo lol...and Google could stand to do some cleaning themselves in framework etc.
 
starkraving said:
Agreed. They needed a theme engine for 1.5-2.2...since GB forward Android's not been horrible looking(would love a native toggle between material light/dark like that's present in some apps) . My one and only gripe is that app devs should be forced to use new GUI guidelines and stop using deprecated images and styles from Froyo lol...and Google could stand to do some cleaning themselves in framework etc.
Click to expand...

This is just me, but I'm tired of hearing about errors in my builds, due to a theme the end user applied. Which has nothing to do with my work. And everything to do with your themes developer.
 
Seraph08 said:
This is just me, but I'm tired of hearing about errors in my builds, due to a theme the end user applied. Which has nothing to do with my work. And everything to do with your themes developer.
Click to expand...
Not to mention the 20-30+ mb ram theme engine uses...As far as custom kernels go I've not used one on the Moto G that didn't break something or have an issue of some kind. (like wake from sleep/deep sleep issues)
 
Seraph08 said:
What I absolutely despise is hearing about kernels being flashed, then coming to me like it's my builds fault.
Click to expand...
Long time gripe from developers and no doubt a justified one...
When people report bugs they fail to report they're on a custom kernel, using various scripts, xposed modules etc.
When reporting bugs users should be on a clean ROM (no mods, modules or kernels) state what build your using (by build date) describe your install method did you verify your download md5, what recovery was used, was it a normal update (dirty flash), clean install, what ROM you came from, what GApps did you use...did you restore data from a nandroid or from a app like TiB? All this plus of course the key thing... logcats and can you duplicate the bug...or was it a one time fluke.
Anyway that's how I was taught...oh and guys since there's different bootloaders being used probably should state your bootloader version too. All this information will help the developer identify issues more quickly and in the end give us end users a more polished build. He can't do it alone, not everyone uses their devices the same way and an eclectic testing pool of users providing good and accurate info helps all of us.
 
You must log in or register to reply here.
Back
Top Bottom