Give us BATTERY_STATS back - Android General

If you already got your Nexus 5 or installed a custom Kitkat ROM you already have noticed that your favorite battery stats tool, whether it is BetterBatteryStats, GSam of wakelock detector, does not work.
Well it is not uncommon for some API to be changed so when a new Android version comes out it usually takes us a few days to get hands on a device and fix things.
But this time is different and important enough for me to take time to summarize the situation.
A little history
Android has a service called 'batteryinfo' that collects a lot of info about what goes on on your phone. That service is not perfect but it provides some pretty important information about what is important to our battery monitoring apps: an insight into what drains our battery.
Our apps communicate with that service and therefore claim the android.permission.BATTERY_STATS permission protecting the access to that service. This permission is of the category "dangerous", notifying users of the fact that they should check why an app requires that permission. For a battery monitoring app it is logical to require it.
This change of course impacts devs as their apps became unusable with that release with no perspective for a fix without an expensive workaround (as e.g. already implemented in BetterBatteryStats 1.15+).
But more alarming, it prevents users to get an insight in what drains their battery and make decisions to keep or drop apps depending on the 'cost' in terms of battery life!
If I was a conspiration theorist I may believe that this change was made on purpose to prevent users from seeing how all the pre-installed apps - including those from google - affect their user experience by reducing the battery life / usability.
What happened
With kitkat starting to ship things happened pretty fast and first feedbacks started to emerge reporting that the service could not be contacted. It took me some time to get hands on a kitkat phone (in fact I flashed my gnex with an inofficial ROM and had to make sure that the errors I got were not cause by that ROM and corresponded to the behavior on a Nexus 5.
After some research two changes in 4.4 are responsible for the problem:
1. batteryinfo was renamed to batterystats
2. the BATTERY_STATS permission has been unavailable to apps (moved from protectionLevel 'dangerous' to 'signature|system'
This is the change preventing apps to be granted that permission: https://android.googlesource.com/pl...it/+/3714141d287c965ea3451831dd5167f63f8db87b
As you can see the change refers to an issue number but this issue is not documented in the public tracker (welcome to not-really-open-source).
I have posted a request on the android-platform forum to request a clarification on why that change was made (https://groups.google.com/forum/#!topic/android-platform/f-7Td9aeFKY) but DID NOT GET ANY satisfying feedback. Therefore I have filed an issue in the public bug tracker for this change to be rolled back (https://code.google.com/p/android/issues/detail?id=61975&thanks=61975&ts=1383910497).
I kindly invite you to upvote this request by staring it.
Please star it, adding a comment "I vote for this" or "Please undo this" to the thread does not do any good:
- comments are not counted, only stars
- that forum is not there to express opinions, it's for bug reports and requests. Unrelated matters like opinion will have no other result than annying the reader.
What devs should know
1. BATTERY_STATS has been moved to protectionLevel=18 (signature|system) and is not accessible to apps anymore
2. On KitKat copying an app to /system/app does not grant protectionLevel=18 anymore. This has been changed in KitKat and the target directory to gain those rights is /system/priv-apps
3. The service delivering battery stats was called 'batteryinfo' in previous Android version and is called 'batterystats' in KitKat
[update 2013-11-16]
*dream out loud*
In an open source world the community owns the source right? Wouldn't it be cool if some senior android devs would review this change and - assuming there is no good reason for it - would revert it in their fork to provide their users with what I believe is an important feature?
[/update]

I really would like to hear from some senior devs maintaining a repo about the idea of taking control and reverting that change

Google has release 4.4_r1.2 and still no joy.
Changes are here:
https://android.googlesource.com/platform/frameworks/base/+/android-4.4_r1.2

Re-enable BATTERY_STATS in a custom ROM
I wrote up a post in another thread about what a ROM developer can do to re-enable Battery Stats (non-root) in a custom Rom. Very simple, but wanted to point it out should anybody be wondering...
http://forum.xda-developers.com/showpost.php?p=48029013&postcount=26

For CM2016' KitKats only
chamonix said:
I really would like to hear from some senior devs maintaining a repo about the idea of taking control and reverting that change
Click to expand...
Click to collapse
http://forum.xda-developers.com/and...kelock-blocker-official-2016-nightly-t3393825
Does it make sense ?
Thanks for any help.

oF2pks said:
http://forum.xda-developers.com/and...kelock-blocker-official-2016-nightly-t3393825
Does it make sense ?
Thanks for any help.
Click to expand...
Click to collapse
Can you help me understanding what this mod/change is about? My suggestion was about reverting a change that was made by google to restrict the access to a certain permission. You link is to a post with a title suggesting something like blocking the ability for apps to hold wakelocks. Such a stunt would be a really bad idea IMHO but maybe I missed an important point

idea of taking control
chamonix said:
suggesting something like blocking the ability for apps to hold wakelocks. Such a stunt would be a really bad idea IMHO
Click to expand...
Click to collapse
Thanks for feedback; i'm real fan of wakelock-blocker's theory, and was wondering if :
- is it useful ?
- can it help user to take control on any kind of restriction ?
I found that completely awesome under KK (static use) but i was very disappointed on testing with LP (anarchic behaviour). BetterbatteryStats was the best observer i found around, and i thought that both were complementary; indeed Beanstalk did use use both with KK: wakelock-blocker' mod and performance/wakelock(similar to your top-app) from Omnirom. But with Omnirom, the mod was rejected : https://gerrit.omnirom.org/#/c/9266/ ; to quote you ("some senior devs maintaining a repo about the idea of taking control"), this link show how much they do ?
Recently, I discover that Beanstalk (6?) was pushing this complementary further forward: https://github.com/scotthartbti/and...mmit/5fb687ae0940a12c8f7c9e457b6d5f12f028736b
I hope there was not too much confusion or loose in my first post and i believe BetterBatteryStats is a better option that can be toggled at any time. (I won't get a lot of thanks with my KK thread....)

Related

Tips about a good customer support

No matter if the app is free or paid, as a developer you want to offer a good support to the end users. Why? Because as long as they are happy they will continue to use your app and they will recommend it to others. So it is in your best interest to do your best and resolve issues that customers are reporting, implement requested features and solve as many bugs as possible.
To that end, you must ensure you provide easy to access means of communication between you as a developer and the end users. There are many ways you can achieve that and I will list a few I am using and the more you can provide the better so we can put together a list:
Create an email address or use one you already have (I prefer the former) and provide links on Google Play and inside the app. It is nice if you add an accessible menu item that says (Suggestions/Bug report/Support/Etc) that will start an intent chooser for sending emails to this email address
Use forums (XDA ) and post your app and frequently visit and answer suggestions/questions. There are a lot of helpful users there that will test the app and discover bugs, suggest new features and it is very good if you can keep the thread hot so you keep the interest up. Users like feedback and makes them feel important (which they are) so try to answer as many posts as possible even though you don't have a solution to the problem yet
Get social! Social networking is very helpful these days both for spreading the word about your app but also for customer support. Create profiles for the app on all major social networks (Facebook, Google +, Twitter, etc) and try to get as many users as possible. Post as many updates as possible and keep the users informed about changes to the app, answer to their comments and implement suggestions
Prioritization - build yourself a TODO list with priorities: for each update try to solve major bugs first that are heavily reported or that are causing big problems. Always find some room for improvements and user suggestions. Then fix small bugs and try to improve UI.
Localization is an important part of today's apps. Try to support as many languages as possible making easy for the users to understand the app and to better communicate their findings
Use the publish console to check for crash reports. Many users use this feature and send crash reports along with the stack trace and it is very helpful to keep track of major crashes and identify the root cause
Please reply with more tips so we can create a big list for everyone
Email is the number 1 way people ( from my experience ) contact the developer to ask questions, recommendations, etc. What I did in addition to all the things in the op was create a cheap 5 page website with Godaddy website tonight its like $100 bucks a year or something. They also auto optimize your site for mobile viewing!Then made a contact us page, were users can choose a reason for contacting us. This works really well and you can set up an auto responder to send them a message letting them know you got the email.
I always try to answer emails immediately (during business hours) but always within 24 hours. Having a great customer service program even if your a solo dev like I am will translate into 5 star ratings based solely on customer service!
Have a lax customer service program and you will see the negative 1 or 2 star ratings pop up again based solely on customer service. It shouldn't take anyone more than say 48 hours to re connect with someone and at least start the process of answering their concern.
You can see the contact us page here
Good policy will turn into good reviews and good downloads!
:good:
I've put a feedback page in all my apps.
You don't even need to create a new email address. Just use your personal email address and create an alias. That way it looks formal on the outside but messages go to same inbox as your personal one, only have to check one inbox everyday.
HMMMMMM!
FIRST OF ALLL EMAIL AND AFTER THAT XDA POSTS.........:victory:
email or the message box is very important. But it's also important to reply to their questions promptly.
Free Customer Service SDK
Replying promptly to customers is essentially the first step towards good customer service. If you are an iOS app developer, looking to impress your customers with excellent customer support, try out Freshdesk's Mobihelp SDK ( [freshdesk.com/mobihelp) you can snap-in to your app and start communicating with your customers from right within your app. I'm sure it will be of great help in your customer service efforts!
Thanks for the tips! Just a question: I have got one Crash report in google play console very early, but since then nothing. I have put email in the game and on the play store. But nobody used it. I do not have many installs, but I wonder what is the usual percentage of people who actually report bugs?
kulisgames said:
Thanks for the tips! Just a question: I have got one Crash report in google play console very early, but since then nothing. I have put email in the game and on the play store. But nobody used it. I do not have many installs, but I wonder what is the usual percentage of people who actually report bugs?
Click to expand...
Click to collapse
In my experience, if the app is something people desperately need (e.g. utility) or want (e.g. game) but it isn't working quite as they expected, they will be vocal. Not hearing anything from users is usually a warning sign that nobody was too excited about the app in the first place, or that not that many people downloaded the app in the first place.
If I see a crash on Google Play I assume that the same crash occured for 10 others who didn't bother reporting it. So I try to fix it ASAP.
You could use Google Analytics to report crashes without user prompt.
Regardless of the above, it sounds like you have a general marketing challange which is much more critical than that crash report, so you should investigate marketing and promotions in general.
kulisgames said:
Thanks for the tips! Just a question: I have got one Crash report in google play console very early, but since then nothing. I have put email in the game and on the play store. But nobody used it. I do not have many installs, but I wonder what is the usual percentage of people who actually report bugs?
Click to expand...
Click to collapse
Bad reviews on google play
slackydroid said:
No matter if the app is free or paid, as a developer you want to offer a good support to the end users. Why? Because as long as they are happy they will continue to use your app and they will recommend it to others. So it is in your best interest to do your best and resolve issues that customers are reporting, implement requested features and solve as many bugs as possible.
To that end, you must ensure you provide easy to access means of communication between you as a developer and the end users. There are many ways you can achieve that and I will list a few I am using and the more you can provide the better so we can put together a list:
Create an email address or use one you already have (I prefer the former) and provide links on Google Play and inside the app. It is nice if you add an accessible menu item that says (Suggestions/Bug report/Support/Etc) that will start an intent chooser for sending emails to this email address
Use forums (XDA ) and post your app and frequently visit and answer suggestions/questions. There are a lot of helpful users there that will test the app and discover bugs, suggest new features and it is very good if you can keep the thread hot so you keep the interest up. Users like feedback and makes them feel important (which they are) so try to answer as many posts as possible even though you don't have a solution to the problem yet
Get social! Social networking is very helpful these days both for spreading the word about your app but also for customer support. Create profiles for the app on all major social networks (Facebook, Google +, Twitter, etc) and try to get as many users as possible. Post as many updates as possible and keep the users informed about changes to the app, answer to their comments and implement suggestions
Prioritization - build yourself a TODO list with priorities: for each update try to solve major bugs first that are heavily reported or that are causing big problems. Always find some room for improvements and user suggestions. Then fix small bugs and try to improve UI.
Localization is an important part of today's apps. Try to support as many languages as possible making easy for the users to understand the app and to better communicate their findings
Use the publish console to check for crash reports. Many users use this feature and send crash reports along with the stack trace and it is very helpful to keep track of major crashes and identify the root cause
Please reply with more tips so we can create a big list for everyone
Click to expand...
Click to collapse
Hi,
how can we deal with bad reviews on google play, reviews that comes from pepole that didn't understand the meaning of the app?
Thanks.
If you're looking for app support best practices, contact a big startup like Buffer or Squarespace and see how they respond to your question. Notice the friendly tone of voice, the detailed answers they try to give you, and the call for action at the end of every support ticket - whether it's to try and recreate the event that caused the bug or read a FAQ section. Do that a dozen times and you'll learn more about 'proper' support than any how-to article can teach you.
dimnikolov said:
If you're looking for app support best practices, contact a big startup like Buffer or Squarespace and see how they respond to your question. Notice the friendly tone of voice, the detailed answers they try to give you, and the call for action at the end of every support ticket - whether it's to try and recreate the event that caused the bug or read a FAQ section. Do that a dozen times and you'll learn more about 'proper' support than any how-to article can teach you.
Click to expand...
Click to collapse
Yep makes sense in my experience - personalise as much as possible and reflect the tone of voice of your app. Users will really appreciate it. Stay social.
Why not have some kind of in-app help?
Having a suggestions/feedback menu item seems to be the common thread here to provide good customer support.
But wondering - why not some kind of in app help itself? Sort of a Whatsapp inside the app? I feel email being a separate channel breaks the context - help within the app itself and in context would be so much easier for the end user.
Thoughts?
I know it is an old thread but there are SDKs that help you integrate a support chat right within the app. I have seen zomato use one of these.
Thank you for a list!

Custom ROM comparison database 2.0 (open to edit for public now!!!)

UPDATE: Database 3.0 can now be found here
Someone asked me to create a thread here for my custom ROM comparison database, so that's what I'm doing here now.
A few words from my side so you know what to expect of it and clear things up.
This is the original text I posted on my blog, so I'll just put it up here as well.
At the end of last week, I asked on G+ what to do next, an app comparison or a new custom ROM review. On of the first answers that got my attention was someone asking for a custom ROM comparison instead. I thought about it for a while how this could works since I can’t show them off side by side and it would be difficult no matter what. While thinking along I also remembered one post on YouTube where a viewer gave me the constructive criticism on the videos getting too long, especially the part where I listed all the features in the video review. I told him I am aware of that fact but I still haven’t found the right solution to make the videos shorter without missing any important specs. After some more thinking the idea of the comparison database was born.
The idea behind the database
Creating a database that contains all the available features clearly visible and quickly to access for everybody was actually the hopefully right solution. Using it I don’t need to waste anymore time on rattling down the whole list in my video… this saves me a whole lot of time but of course also you. And if someone wants to know if a specific feature is available in the reviewed ROM he can just quickly check the database and look for it, it’s as easy as that. Of course this method also allows me to focus more on the important aspects of the ROM itself.
Creating the database itself took quite some time for sure but in the end I think this is the cleaner and smarter solution for everyone. I hope this to get a helpful tool for everyone to easily find the right ROM for himself that suites him the most.
I did 2 videos, one quickly explaining the purpose of the database itself and an additional one explaining some of the more important custom ROM features so that people who are maybe new to custom ROM flashing know what to look for. If you see any feature in my database and wanna know what it is for or what it does, leave me a comment. I will then either quickly explain it if possible or collect some of the requests and make another “features explained” video.
Here is the link for the database (it will also be attached to every upcoming custom ROM video as well as the matching article), it will be updated with every upcoming custom ROM video review. I am no professional in text editing, so if someone is maybe bored or wants to help me out in making a better and more professional appearing database to improve it, please contact me, I’d really appreciate it.
Click to expand...
Click to collapse
Features of the database
--------------------------------------------------
- detailed list of all possible custom ROM feaures (~100 at the moment, constantly growing)
- containing 13 of the most popular ROMs + stock Android ROM + Xposed Framework to compare with each other (list is still growing)
- a lot of useful additional informations like links to downloads, ROM's websites, G+ communities and much more
- everything is sorted logically and color coded for fast and easy comparison
- all features have a quick explanation, expecially helpful for custom ROM beginners
- a lot of maintainers to keep it updated as good as possible (12 maintainers at the moment) - always looking for more, feel free to join
- constantly working on improving and enhancing the database
here is the link to the database 2.0 - thx to @parker09
some additional videos to explain the whole thing again...
Please feel free to leave any comments.
I'm a real Google docs noob so if someone maybe wants to help me clean it up and polish the style, just contact me.
And if this thread is posted in the wrong section, please just let me know.
UPDATE new host
Updates
Update
I read the posts here and on the portal and wanna set some things straight.
I do the database including the reviews in my free time, but besides that I´m also blogging,doing app/device reviews, how to´s and similar stuff so time for the database is therefore limited. That´s the reason I can´t progress with the database as fast as I would like to, also my way of testing takes up a lot of time.
I will of course try to do it as frequently as possible and of course ROMs like AOKP and Omni will follow in time.
That´s it for that.
Regarding mistakes and such, I know the database isn´t flawless but I´m not doing errors on purpose. About missing features of certain ROMs, it is possible some ROMs now have features that weren´t available at my time reviewing it but it´s almost impossible for me to keep track of all changes since I use different ROMs all the time and can´t always go back to already reviewed ones.
Update 2
Big change, after all what I read, I finally decided to make the database open to edit for public. Everyone can add ROMs and changes as he wishes to. I only ask users to be resposible and keep everything clean. Feel free to make new entries or correct errors if found. I think this is the best way for the database to grow.
The 2nd change is the move to another design made by @parker09 that is way nicer and better in my opinion.
The old one will still stay but won´t be updated anymore I think. So don´t forget to change your current link to the new one.
BIG THX to everyone in advance who decides to particate on working on the database, I hope the new way is a win for everyone.
Update 3
Sorry to say but the open to public idea wasn't the best it seems since the database somehow got messed up a bit. I want to prevent this from happening that's why I have some rules now to hopefully keep things clean and right this time.
Everyone is still welcome to participate in maintaining the database but has to do following now in order to get permissions to edit.
This reason for the rules is so I can better keep track of what gets changed by who and I know which parts are getting updated and which not.
How to get permission to edit?
Please contact me via PM on xda with the following title...
maintain custom ROM database "your email adress" "your google name" (the name that will appear when editing the document)
- Please also write down your name and email again within the pm just to be sure
- Please tell me which ROM(s) you would like to maintain or what you plan to edit.
- Please tell me if it is ok to add you to hangouts, this would make the teamwork faster and easier
Rules for maintainers
can now be found directly in the database
I want this so I have a list of all the maintainer and know who does what, so things don't get mixed up like 2 people editing one rom at the same time getting each other between in their way. This gives me a better overview so I can track the changes.
THANKS TO
-----------------------------------------------
n3ocort3x - AICP Team member
owain94 - PACman Team member
vedantgp - CyanFox Team member - Special thanks for a lot of groundwork&more
josegalre - Special thanks for a lot of groundwork&more
jrudyk
msn.debord
louisjms
lordbalmon
septigation
l3v14n
Thank your for publishing it here as well. This will be helpful for all of us. :good:
SlimBean has Breathing SMS. I should know I ported it (its in MMS settings)
cordell12 said:
SlimBean has Breathing SMS. I should know I ported it (its in MMS settings)
Click to expand...
Click to collapse
Maybe it didn't have it back when I reviewed it or I missed it. Will change it later. Thanks for the heads up
Can you add what you can do with stock+GravityBox? Then people can see which benefits they can get without flashing roms.
Hi nimrodity,
please make it available as a online tool for all ROM makers, so that they can update it as and when possible. and then there's no need you to update it.
Nice I did a column for Paranoid Android (as best I can - some features I don't know what they do) but did as best I could so if you want to copy & paste it.
https://docs.google.com/spreadsheet...VoZ1l0bWxoYnVzek9oNnhlWXc&usp=drive_web#gid=1
On the second sheet I started one ages ago and that's the style I went with, and you hover over for what their options are.
Interesting, but what I would really love to see is developers from cross-ROM platforms joining hands
Lastest Carbon have got Paranoid PIE.
Small adjustments
You had a really great idea by doing this. I once search for something similar to this spredsheet and didn't find anything useful...till now!!
You did a wonderful job!
I just noticed 1 small thing and my other point is a suggestion:
1. In CM10.2 you have an option for the vibration intensity only, so maybe you could add to the "vibration" section: yes, but limited.
2. My suggestion would be to add another "spec" for the ROM. It would be "screen color/gamma calibration". It's a very interesting feature and CM10.2 (latest nightly) has it.
What do you think?
Thanks
Keep up the good work!:good:
maxver0 said:
Lastest Carbon have got Paranoid PIE.
Click to expand...
Click to collapse
I know but it didn't back then when I reviewed it. I can't always update the database especially with the old review build date. It would be too hard to keep track of all.
Thanks for Your work... Hope You will add more ROMs to this database and I hope other members will help You to get the info You need for awesome ROMs like:
Purity...
crdroid
XenonHD
Liquid Smooth
Vanir
Carbon
Illusion
beanstalk
Jellybam
... and more AOSPs
... ... ... ... OMNI
Purity, Vanir, Jellybam and XenonHD should be simple to track because devs keep the same MODs&features... little changes on every new build
More difficult to track other ROMs that add&remove features very often
I can't help You because I'm a Stockish man and I won't try AOSPs for now
Thanks for useful database, It will sure help me when I will going to flash new rom
felix1234 said:
Can you add what you can do with stock+GravityBox? Then people can see which benefits they can get without flashing roms.
Click to expand...
Click to collapse
Doesn't really make sense since it's all about custom Roms but I already thought about doing a separate review for the blog.
Not sure about your idea, will think about it though
itechengine said:
Hi nimrodity,
please make it available as a online tool for all ROM makers, so that they can update it as and when possible. and then there's no need you to update it.
Click to expand...
Click to collapse
As you can see by my simple list I don't know much higher about docs and I have no clue how to do such a tool. The idea sounds really cool if someone knows how to do that and wants to help out just contact me
parker09 said:
Nice I did a column for Paranoid Android (as best I can - some features I don't know what they do) but did as best I could so if you want to copy & paste it.
https://docs.google.com/spreadsheet...VoZ1l0bWxoYnVzek9oNnhlWXc&usp=drive_web#gid=1
On the second sheet I started one ages ago and that's the style I went with, and you hover over for what their options are.
Click to expand...
Click to collapse
Will check it later. If you see my YouTube channel you see my PA rant. I don't really have that much interest updating the database with PA since I'm not really a big fan of the to work. Nothing personal but I just can't get warm with their Rom
@nimrodity
Great work. Important factors when choosing rom could besides features be "RAM usage on clean install and no tweaks/installed apps" and benchmarks based on the same conditions.
But anyways, awesome work :thumbup:
pemell said:
@nimrodity
Great work. Important factors when choosing rom could besides features be "RAM usage on clean install and no tweaks/installed apps" and benchmarks based on the same conditions.
But anyways, awesome work :thumbup:
Click to expand...
Click to collapse
Sorry I won't including benchmarks since they have nothing to say about performance in daily use. They are no important factor for me. Same for the rest, also I mention performance and such in my video reviews, don't plan on adding that stuff directly into the database though
On Cyanogenmod it says :
Volume Music Controls : music controls visible only but not with volume buttons.
You can control the music with the Volume buttons whilst being locked.
And if Poweroptions refer to the "menu" that shows when pressing the power button, you can en/disable airplane mode and select "Screenshot". And you can switch between Silent/Vibrate/Sound Profile.
Why no MIUI?
Great work! Just one little nag - why no mention of MIUI? It's distinct feature set should surely warrant a review, but that's just my opinion.
jwchips said:
Great work! Just one little nag - why no mention of MIUI? It's distinct feature set should surely warrant a review, but that's just my opinion.
Click to expand...
Click to collapse
My database is far from being complete, I just started . I chose my Roms randomly until now. Miui is still possible to come

[APP] Pikik 7.9 (Modified Kik Messenger with AntiLag)

Hello XDA,
I'm releasing a modified version of Kik to the public. This is version 7.9 - without video playback support. I created this in January after discovering an exploit within Kik Messenger that allowed me to crash other users. This gave birth to what are known as "lag codes", which are long strings that cause instability within Kik.
If you're on kik and people post strings like:
0la.3p.snai7.eo.490.0la.3p.snai7.eo.490.0la.3p.snai7.eo.490.0la.3p.snai7.eo.490.(etc)(shout out to TL1 for his work in this area)
you will lag, ios and android are affected by this.
I have modified the parser within Kik to stop those short lag codes from causing lag.
I issued these Pikik clients to only a handful of individuals (hardcoded their usernames and disabled editing) , typically being used to crash pedophile chatrooms. Someone in this handful decided to leak the file. They attached AndroRat and distributed it under my credibility and name and I don't appreciate that.
The exploit (along with other exploits I've discovered) and suggested fixes have been emailed to Kik without reply.
This is version 7.9 without video support. You can do the same with 8.0+ as I have done but I don't want to distribute that yet. as I'd like to make a menu via smali to add additional features to Kik. (Confirmed fake camera is possible among other things) Hopefully within that time, Kik will patch the exploits I've emailed them about.
Please be respectful to one another with Pikik, it can cause issues for other users without Pikik if you so choose.
I will create additional links if necessary. Happy Easter.
May 6 update:
Added Kik 8.0apk for video playback. Added another layer of lag protection.
-gunther210
Admin note: APK has been removed due to legal complaint from Kik. Do not re-upload. https://github.com/xda/Notices/blob/master/2015/Kik-20150624.md
Warning, I would not recommend trusting. The app was leaked. Gunther stated that he would release the application to the public in the month of July.
424aca said:
Warning, I would not recommend trusting. The app was leaked. Gunther stated that he would release the application to the public in the month of July.
Click to expand...
Click to collapse
Hey mate, that wasn't the case.
I planned to publish the technical details of the xss exploit within kik.com in July but that also leaked.
I encourage anyone to decompile this apk and look for anything malicious or suspicious if they don't trust it. It isn't my style to do that.
I understand you're just looking out for the community.
Take care mate.
Apologies and Results
Yah sorry to come out as aggressive or as if I was pointing fingers. If you are truly gunther, then you are very much aware of the presence of individuals on kik who post links which intercept IP's and I see a new exploit regarding a phishing link "video" with your name on it etc. I just want individuals to be careful. Because I made seemingly false accusations, I have done the task of running a scan on the app in a virtual machine (genymotion) running a various security scans on it. Only avast gave a security warning, but upon rescan it was gone. I have uploaded four images of four different tests. Please, proceed with caution for this application is as wonderful as you anticipate it to be. To those that have root and xposed, i would advise using I believe xprivacy to block any SMS or call log interaction which this app may present if the proof supplied below does not suffice your paranoia which I seem to be having right now.
-424aca
View attachment 3247779
View attachment 3247780
View attachment 3247781
View attachment 3247782
Thx for the tests.
I'm aware of the games being played on Kik. That's not likely to go away but their lack of willingness to correct the problems leaves everyone vulnerable. At least this protects a regular user from another regular user being annoying. The xss exploit needs to be patched immediately. The amount of people getting phished is amazing. I regret sharing info about that exploit.
As I mentioned long ago to anyone on Kik who asks the status quo kik hacker question "can you get ips thru kik?" My response has always been the image handler. The way kik handles their images has been exploitable forever but I'm not yet certain to what degree. After reporting the 2 "main" exploits to Kik, I moved onto checking out my suspicions and getting some confirmation/vindication.
The entire handler for images is a wreck. It's possible to create corrupt image headers (see my pastebin) which will crash Android upon receiving said picture. It's possible to create corrupt image headers to get IP addresses via images (confirmed on iOS by Host 4/6/2015). It's possible to create corrupt image headers to crash Android for lack of associated action.
It's possible to send videos as Gallery, Gallery as Camera, Camera as "Gunther", custom icons, and most likely offsite pngs (apache log taps). It is possible to build a card that exploits these same flaws but with more parameters. The card:// handler is probably only "more secure" because less people use it.
The fact that I can send you a picture that crashes your kik is absurd and it was obvious to me this style of attack would be possible from the first glance at it.
I like Kik but it is a dangerous hangout lately.
424aca said:
Yah sorry to come out as aggressive or as if I was pointing fingers. If you are truly gunther, then you are very much aware of the presence of individuals on kik who post links which intercept IP's and I see a new exploit regarding a phishing link "video" with your name on it etc. I just want individuals to be careful. Because I made seemingly false accusations, I have done the task of running a scan on the app in a virtual machine (genymotion) running a various security scans on it. Only avast gave a security warning, but upon rescan it was gone. I have uploaded four images of four different tests. Please, proceed with caution for this application is as wonderful as you anticipate it to be. To those that have root and xposed, i would advise using I believe xprivacy to block any SMS or call log interaction which this app may present if the proof supplied below does not suffice your paranoia which I seem to be having right now.
-424aca
View attachment 3247779
View attachment 3247780
View attachment 3247781
View attachment 3247782
Click to expand...
Click to collapse
So is it safe or not?
I don't like its dark background. Fix it
PrinceCoc said:
I don't like its dark background. Fix it
Click to expand...
Click to collapse
I changed mine to white.
I recommended you do not try this app. Probably the maker of this modified version add some malicious things. Or something for stealing personal infos
GreekDragon said:
I recommended you do not try this app. Probably the maker of this modified version add some malicious things. Or something for stealing personal infos
Click to expand...
Click to collapse
Damn I've already been using it
GreekDragon said:
I recommended you do not try this app. Probably the maker of this modified version add some malicious things. Or something for stealing personal infos
Click to expand...
Click to collapse
I didn't. Instead of talking dumb ****, why don't you decompile it and check for yourself. I have no desire to take anyone's info.
ODSTZ3RO said:
Damn I've already been using it
Click to expand...
Click to collapse
You're fine mate.
Me Host and Link have been working together on adding several features for pikik2 and their similar releases.
For now pikik2 will be:
Based on 8.1.x
Probable:
Turn off read receipts (Host)
Turn off typing notification (Host)
AntiLagV2 (Gunther)
Fake-Camera Mod (Gunther)
AntiLagv2 secondary check (Link)
(Theme choices by download if below doesn't work)
Possible:
Turning links on/off
AntiLagv2 override by conditional regex by input
Selectable Theme by input
Selectable Image background (Link/Host)*
*This works now but needs some more tweaking.
If you or someone you know is a smali pro, please PM me.
We are hoping to build these ideas as switches from a panel within kik
Also. If you're interested in building an Xposed Module to do these things, please PM me and I will help point to where the above things are taking place.
All credits will be given
If someone wants to reach us on kik. Check in #pikik
Appreciative said:
I didn't. Instead of talking dumb ****, why don't you decompile it and check for yourself. I have no desire to take anyone's info.
You're fine mate.
Me Host and Link have been working together on adding several features for pikik2 and their similar releases.
For now pikik2 will be:
Based on 8.1.x
Probable:
Turn off read receipts (Host)
Turn off typing notification (Host)
AntiLagV2 (Gunther)
Fake-Camera Mod (Gunther)
AntiLagv2 secondary check (Link)
(Theme choices by download if below doesn't work)
Possible:
Turning links on/off
AntiLagv2 override by conditional regex by input
Selectable Theme by input
Selectable Image background (Link)
If you or someone you know is a smali pro, please PM me.
We are hoping to build these ideas as switches from a panel within kik
Also. If you're interested in building an Xposed Module to do these things, please PM me and I will help point to where the above things are taking place.
All credits will be given
If someone wants to reach us on kik. Check in #pikik
Click to expand...
Click to collapse
OK I wasn't going to delete it I just changed its appearance a bit.
NOT working?
I have tried to download the File but i keep getting an error saying I don't have the app installed when I do? Maybe it's because a recent update that I did yesterday April 14, 2016. Any help?
Delete the kik you already have
INTRUTHS said:
I have tried to download the File but i keep getting an error saying I don't have the app installed when I do? Maybe it's because a recent update that I did yesterday April 14, 2016. Any help?
Click to expand...
Click to collapse
Yeah man your in the future, please tell us what its like in 2016
I reeeaally enjoy this app. Buuuut I like the new material design update (8.2.0) more. Pls update.
gallowsArisen said:
I reeeaally enjoy this app. Buuuut I like the new material design update (8.2.0) more. Pls update.
Click to expand...
Click to collapse
Didn't you read the post, their working on it, if you know someone that's good with smali tell them to contact us at #pikik
theattackingdildo said:
Didn't you read the post, their working on it, if you know someone that's good with smali teller them to contact us at #pikik
Click to expand...
Click to collapse
Sorry. I'll look out for anyone with experience. I'm in a few good groups so I'll ask around.
gallowsArisen said:
Sorry. I'll look out for anyone with experience. I'm in a few good groups so I'll ask around.
Click to expand...
Click to collapse
I'll ask some people about it.
First, let me/us say thanks for all the support. It helps keep us motivated to get pikik2 how we want it.
Updates:
We have pretty much narrowed down all the future feature locations.
We are still stuck in the same spot however.
We need a little advice or guidance on how to use toggles and inputs.
We can build the toggles, we can associate them in the places they need to be. But, we aren't sure how to do the following:
We need a generic or simple way to write and read toggle values into the database or preferences. We need to be able to pull these into smali. We are getting progress on Smali knowledge and may be able to import the values ourselves but we need to have a better understanding of how to implement this.
We want to create a check box, no problem. How do we add the value of check box (or inputs) into the db or prefs in the simplest way?
Next, how do we then read the value out of these?
We are reading to use <checkboxprefs but that's not working easy for us so far. We have tried literally hundreds of tests at this point.
My last test was duplicating the widget check box and associating it.
We need help. Someone. Give us a run down of the fastest way to what we need, please. As always, credits will be given.
Thanks mates,
gunther210
I will make a thread asking for more direct help when I have enough posts to do so. Anyone out there who has any advice, we will investigate.
Thanks again.

Custom/reliable rom/operating system

So I am going to post this here, because the development section is ferboten to people trying to offer useful suggestions. Geez, I hope this is the right section.
Let me set it up. ANDROID IS BASED ON THE LINUX KERNEL. Everything, and I mean everything after that fact becomes android and bloat. Given this as the basis of all things android, I have a simple set of guidelines that should be used to create a solid, reliable, bullet proof operating system for devices able to use the android operating system.
#1. Create the kernel boot section of the basic platform that supports the very basic hardware features, including touch screen, radios, power/charging/battery management, wifi, bluetooth, nearfield, audio, microphone, s-pen,etc. Basics only. Root access is standard and can be turnd on/off just like developwer functions. No special tricks or addon hoops to jump through.
#2 At this point STOP. Every single process or service to be run on the device from this point forward should be able to be individually selectable - or not. Yes, I understand that individual services or apps may have dependancies to other processes and that thouse need to be functional in order for a particular app to work. That is why, each additional service or app must list the dependencies and in the selection process, the installion will be required to verify you have the proper services installed and functioning, if not to list them and allow you to make the decision to proceed. Viola, we have NO MORE BLOAT WARE.
#3 Make selecting additional services/apps selection process a menu driven, tag selectable process. Make the unselection process smart to verify and identify the other apps dependant on the item you are killing/removing.
#4 Allow a built in snapshot option to capture the entire system as you have customized it for yourself and allow it to be backed up to external memory with the ability to bring it back, AT WILL. With no big hassles.
Those 4 items are a good start. By themselves alone, it would put all of us in the drivers seat of controlling and living with our devices.
I am aware that such a system is not for everyone. It does require some basic technical understanding of the process. But for the vast majority of users, I am certain, that an a la carte system is far superior to the bloated monstrosities being forced down our devices.
I would appreciate any refinements to my suggestions.
The silence is deafening. It has been days. Kind of says something, don't you think?
I am so very happy (not) that these boards a compartmentalized to the point where you can't get through.
Pretty much a waste of my valuable time, especially considering the fact that if my suggestions where applied, people would be clamoring for an installation with those features. I guess there is not much true "developer" in xdadevelopers anymore.
Funny guys, with the pay to remove ads spam here. Really? Why? For what.
I leave here disappointed. Not angry. Just sad.
I'm not a developer so I have nothing valuable to contribute to your suggestions in your original post but I can offer an observation regarding your perception of the level of contribution to your thread and that is the fact that is particular area of the forums probably isn't the ideal spot to have a discussion such as this. You figured that out already so sure you can call me Capt. Obvious if you wish but I'm just pointing out that yes the forums are compartmentalized (as you've stated) in such a way that development for each device is separated out. This development is centered around AOSP based ROMs or "stock" ROMs (using manufacturer released source) so if you're looking to have higher level discussions about what AOSP should look like then deep down at this device specific level probably isn't where you want to be. So there's that . . . then there's the fact that for this particular device you can basically hear a pin drop in the sub-forums as it is since nothing much is going on by way of development.
Where specifically such a discussion would see more input I'm not sure, perhaps the main general discussion section?
Thank you for your sobering reply. I get frustrated. Already had my post bounced out of "wrong" forum while trying to speak directly to "developers" (i wanted air quotes because the term does not accuratly describe its target) So I tried this. The note pro 12.0 is still the best hardware giving the ipad a run for its money. The problem its monkeyshines kiddie software running it, or not running, or barely running it. ANDROID, indian word for crappy wannabe software, developed by clueless kids.
Again, thanks for the gentle nudge. I appreciate someone willing to conduct a conversation
Are you looking for an Ubuntu or SUSE type of setup?
I think what you are looking for is similar to apt-get type of installs, I could be wrong of course. This might be helpful for many "users". I think one of the barriers is that there are slight differences between the models of tablets, and creating the logic to put in for the sub-dependencies might prove problematic. You might get more answers to this possibility by asking one of the developers directly and sharing with them. Not a developer myself.

Bugless ROM(s)

I'm really appreciated for ROM developers' work! All these guys working really hard and give to all of us ROMs, with useful features and tuning. But...
Take a look on every first post for almost every ROM. Long-long-long list with huge banners like DISCLAIMER, CREDITS, FEATURES, etc. Are you really sure that your users can estimate your work looking on this "(des)infographics"?!
I'm personally, like thousands of other visitors, are looking for ROM, at first - without bugs, which may be vital for them. For example, ROM with excellent design and unique features is absolutely useless for me if there is a sim switching bug is exists in it. Just imagine situation: I switched off one of my sims and found that the only one way to return it back to work, is "reflash ROM"!!! Why? Bcz it's "a well known bug". Relay great case to get this knowledge, for example, right during going out of a plane in unknown country which you decide to visit first time in you life and left without any communication channel! )))
May I suggest to all ROM developers and regular ROM users list on ROM's first page or here in this thread very short text list with list of ROM's bugs and possible solutions for them, if any exists?
As I know, now there are following bugs that may be critical for lot of users:
fast charge - not working or working but haven't indicator in status bar.
root - buil-in or must be installed separately? Which one SuperSU, Magisk, or other one?
NFC & safetynet test - can this ROM provide wireless payments?
VOLTE - is it working?
sim switch off/on - you switching off one sim and then can't bring it alive even after reboot.
flight mode - after switching it off you must reboot your phone to make new calls.
led indicator - it may not work at all, may partially work with one blue color, can be tuned by LightFlow or other app
double tap to wake up - is it working from the box or required external app?
one key (energy saving switcher on left side) - is it working?
dark video - when switching from photo mode to video, picture and video itself becomes noticeable darker than photo.
finger print actions - don't work, work after reswitching navigation buttons, work with registered FP only.
huge bluetooth power consuming - showing more than 10% while in fact the weren't any device connected and BT wasn't in use.
Please review all above in my list ant type for us short report about their current state in your ROM.
And one more point: dear ROM builders, please do not use bugs descriptions like "same as lineage OS 14 from ....". When you publish your ROM some bugs may be present in other ROMs too. But later, in those other ROMs their authors may fix some of them, while in your ROM they still may left, because you haven't update it. Please don't confuse your customers and don't force them to scan all threads trying to find answers. You know your bugs - please simply list them. And maybe community will give you advice how to fix them (like in case with FP from HigwaySatr).
ViperOS lacks updates. Otherwise, it's a great rom really
Egyptiandroid said:
ViperOS lacks updates. Otherwise, it's a great rom really
Click to expand...
Click to collapse
unfortunately "great" - it's only your emotion. To get facts - try to check every item from my list in your "great rom" and you will find at least "sim switch of/on" and "dark video" issues.
DotOS looks similar to ViperOS but it haven't "sim switch of/on" issues. but DotOS development already stopped (
comunity said:
unfortunately "great" - it's only your emotion. To get facts - try to check every item from my list in your "great rom" and you will find at least "sim switch of/on" and "dark video" issues.
DotOS looks similar to ViperOS but it haven't "sim switch of/on" issues. but DotOS development already stopped (
Click to expand...
Click to collapse
Then, can you suggest a ROM that has the fewest bugs, besides great battery backup?
Egyptiandroid said:
can you suggest a ROM that has the fewest bugs
Click to expand...
Click to collapse
it was done in my previous message - DotOS. One more choice - LOS from HigwayStar. As I found these twos are both without "sim switch off/on" bug. But they have some other bugs (f.e. dark video).
Now I switched from DotOS to HigwayStar because HWS still working on it, and DotOS is freezed.
comunity said:
I'm really appreciated for ROM developers' work! All these guys working really hard and give to all of us ROMs, with useful features and tuning. But...
Take a look on every first post for almost every ROM. Long-long-long list with huge banners like DISCLAIMER, CREDITS, FEATURES, etc. Are you really sure that your users can estimate your work looking on this "(des)infographics"?!
I'm personally, like thousands of other visitors, are looking for ROM, at first - without bugs, which may be vital for them. For example, ROM with excellent design and unique features is absolutely useless for me if there is a sim switching bug is exists in it. Just imagine situation: I switched off one of my sims and found that the only one way to return it back to work, is "reflash ROM"!!! Why? Bcz it's "a well known bug". Relay great case to get this knowledge, for example, right during going out of a plane in unknown country which you decide to visit first time in you life and left without any communication channel! )))
May I suggest to all ROM developers and regular ROM users list on ROM's first page or here in this thread very short text list with list of ROM's bugs and possible solutions for them, if any exists?
As I know, now there are following bugs that may be critical for lot of users:
fast charge - not working or working but haven't indicator in status bar.
root - buil-in or must be installed separately? Which one SuperSU, Magisk, or other one?
NFC & safetynet test - can this ROM provide wireless payments?
VOLTE - is it working?
sim switch of/on - you switching of one sim and that can't bring it alive.
flight mode - after switching it off you must reboot your phone to make new calls.
led indicator - it may not work at all, may partially work with one blue color, can be tuned by LightFlow or other app
double tap to wake up - is it working from the box or required external app?
one key (energy saving switcher on left side) - is it working?
dark video - when switching from photo mode to video, picture and video itself becomes noticeable darker than photo.
finger print actions - don't work, work after reswitching navigation buttons, work with registered FP only.
huge bluetooth power consuming - showing more than 10% while in fact the weren't any device connected and BT wasn't in use.
Please review all above in my list ant type for us short report about their current state in your ROM.
And one more point: dear ROM builders, please do not use bugs descriptions like "same as lineage OS 14 from ....". When you publish your ROM some bugs may be present in other ROMs too. But later, in those other ROMs their authors may fix some of them, while in your ROM they still may left, because you haven't update it. Please don't confuse your customers and don't force them to scan all threads trying to find answers. You know your bugs - please simply list them. And maybe community will give you advice how to fix them (like in case with FP from HigwaySatr).
Click to expand...
Click to collapse
It amazes me how anyone can post anything on this forum...
Can't you just dislike this post?
It amazes me how anyone can post anything on this forum.
Click to expand...
Click to collapse
can't understand - are you serious or ironic? but it seems to me - the last one.
if so - let me tell you: I'm really tired of the same dumb process:
discover "new" ROM at this forum -> backup currently running OS -> install new ROM -> make primary setup for it -> test that vital for me feature isn't work -> say 1-2-3 (un)censored words or sentences -> reboot to recovery -> wipe all installed stuff -> restore previous ROM with less bugs inside it -> one more time promise to myself no more trying unknown ROMs -> but... still watch for new releases.
ROM developers have enough time to draw useless first post dividing images, but appears so busy, to spent 2-3 mins for test above mentioned bugs and with real proud post their ROMs with the comment like "my ROM contains the only 3 bugs of total 12"? ))
comunity said:
can't understand - are you serious or ironic? but it seems to me - the last one.
if so - let me tell you: I'm really tired of the same dumb process:
discover "new" ROM at this forum -> backup currently running OS -> install new ROM -> make primary setup for it -> test that vital for me feature isn't work -> say 1-2-3 (un)censored words or sentences -> reboot to recovery -> wipe all installed stuff -> restore previous ROM with less bugs inside it -> one more time promise to myself no more trying unknown ROMs -> but... still watch for new releases.
ROM developers have enough time to draw useless first post dividing images, but appears so busy, to spent 2-3 mins for test above mentioned bugs and with real proud post their ROMs with the comment like "my ROM contains the only 3 bugs of total 12"? ))
Click to expand...
Click to collapse
If you're so dissatisfied, don't change ROM's then.
Hey. There's a good bugless(ughh) ROM it's called stock ROM. If you're not satisfied You can actually tell anything to them cuz you have paid for it. Have you tried that?
If you're so dissatisfied, don't...
Click to expand...
Click to collapse
my question was not about my satisfaction. it was about statistics - how many bugs from my list and which ones have every ROM published here.
I don't required recommendations or suggestions. I will be glad to see simple answers about each of 12 item - bugs exist or not. from anyone who had test them by himself )
Let me show answer example that I'm expected on:
LOS 14 from HigwayStar
fast charge - working but haven't indicator in status bar.
root - Magisk 16 built in ROM installation script
NFC & safetynet test - working, my payments were accepted lot of times. installing xposed module broke safetynet test (
VOLTE - supported, but I can't test bcz of absence 4G
sim switch of/on - working.
flight mode - after switching it off you can make new calls without any bodymovements.
led indicator - working out of the box. you can setup 16 mln colors, blinking speed and delays.
double tap to wake up - working from the box.
one key (energy saving switcher on left side) - may work, but ROM author decided to switch it off in latest release
dark video - when switching from photo mode to video, picture and video itself becomes noticeable darker than photo especially for dark scenes.
finger print actions - work after reswitching navigation buttons, even without registering FP.
huge bluetooth power consuming - showing more than 10% while in fact the weren't any device connected and BT wasn't in use. simply calculation issue, bcz battery isn't really draining by sleeping BT.
it's not an example. it's my real report about ROM that I'm currently using.
this report may be also about my DotOS usage, but i switched from DotOS to HWS because DotOS - frezed, and HWS - still under development.
Do you know what all bugs(super annoying) the stock ROM have? Did you bust into Lenovo forum and post things like this?
If yes then wait for their update (rip in advance)
If no then go try that and tell me if somebody gives a #@!*
This ROM development is nothing you own. It's developer's hobby which they do in their free time. So creating a thread like this with such a demanding attitude is crossing the line.
You said about the long post on every ROM like intro and blah. Blah. You should read them.
* We are not responsible for bricked devices, dead SD cards,
* Third World War, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
If you think you can make something better do it by contributing towards ROM development.
Wow! So much angriness for one simple question! )))
Dear Senior Member Siva Mk, let me ask you why you are wasting your time and writing to me one more "long post",
You said about the long post on every ROM like intro and blah. Blah. You should read them.....
Click to expand...
Click to collapse
instead of provide us answers for my question, if you have any one?
You are right - no one owes nothing to nobody! at this and all other forums.
I DON'T REQUIRE from somebody, and from ROM developers especially - any warranties and immediately fixing all existing and not existing bugs. Please reread my very first sentence in first post.
I'm really appreciated for ROM developers' work! All these guys working really hard and give to all of us ROMs, with useful features and tuning.
Click to expand...
Click to collapse
I simply want to get help from other users (or ROMs' authors) and collect in one place info about ROMs critical bugs, which maybe helpful for all of us here, to choose ROM, most appropriate for himself.
I have a question - I had asked it. On my previous post I gave an example of answer that I expected. If you haven't such answer - please don't grow Universe entropy and simply ignore my posts and topics. Let we all stop this flooding, and will concentrate on help one to another
How many threads like this are going to be opened ? And who are you to tell developers what to do or bemoan the lack of bugless ROMs ? Ask a mod to close this thread because it's useless as no developer cares about your opinion. This is one of the reasons why there should be a down vote button on XDA like there is on reddit.
medwatt said:
How many threads like this are going to be opened ? And who are you to tell developers what to do or bemoan the lack of bugless ROMs ? Ask a mod to close this thread because it's useless as no developer cares about your opinion. This is one of the reasons why there should be a down vote button on XDA like there is on reddit.
Click to expand...
Click to collapse
He's just another one who wants attention
medwatt said:
And who are you
Click to expand...
Click to collapse
I'm one of the users legion. I'm those who use ROMs which developers creating not for their own using. As far as developer decided to publish his ROM in the Internet, he MUST be ready to answer the questions about his ROM.
Let me repeat once more to be completely clear:
1) I don't want to test on my own phone ALL published here ROMs.
2) I asked ROMs' users or their authors help in checking and reporting existing of some vital for lot of users bugs, that MAY be present in these ROMs.
Why did you all pounce on me (instead of check and report bugs existing)?
Am I asking anywhere at least one ROM developer to immediately FIX bugs in his ROM?!!
One simple question with pre-prepared themplate to make answer as easy as it possible. Are any criminal in my 12 items bugs list?
Once more I'm urging all to switch from hollywaring to finding bugless ROM or at least clarifying which bugs are exists in each ROM.
Nice thread, Sorry there is no bug-less rom available for P2 right now ?
For me the only rom that has no bugs is stock mm 6 even stock nougat for me has a bug that Lenovo can't solve till now linegue os by HWS is the best with minor bugs that does not affect daily drive
comunity said:
I'm one of the users legion. I'm those who use ROMs which developers creating not for their own using. As far as developer decided to publish his ROM in the Internet, he MUST be ready to answer the questions about his ROM.
Let me repeat once more to be completely clear:
1) I don't want to test on my own phone ALL published here ROMs.
2) I asked ROMs' users or their authors help in checking and reporting existing of some vital for lot of users bugs, that MAY be present in these ROMs.
Why did you all pounce on me (instead of check and report bugs existing)?
Am I asking anywhere at least one ROM developer to immediately FIX bugs in his ROM?!!
One simple question with pre-prepared themplate to make answer as easy as it possible. Are any criminal in my 12 items bugs list?
Once more I'm urging all to switch from hollywaring to finding bugless ROM or at least clarifying which bugs are exists in each ROM.
Click to expand...
Click to collapse
Dude seriously if all people have a attitude like yours developers will just stop building roms altogether.

Categories

Resources