Database Users

[MOD] Ingress broot mod v1.26.1-broot-0.2.0 (2013.05.26) [CLOSED]

Unfortunately Niantic contacted me to abort this mod. More info: http://forum.xda-developers.com/showthread.php?p=42027875#post42027875
TL;DR version: I have created an Ingress app mod, it is awesome and will make you coffee. You can download it below.
OVERVIEW
Hi,
after more than a 2 years of inactivity in the modding field I'm back with a new mod. This time it's Ingress app. I think and hope it'll be much greater and more advanced than Google Maps mod. There are a lot of things to improve and I think some of them won't be ever added by Niantic, so it's a good idea to mod this app.
First I want to clarify I will never add any kind of cheating to this mod. My goal is to make Ingress game more enjoyable, not less. Questions about location faking, items cloning, etc. are not welcome here. I'm serious. Still if you think this mod is a bad thing and/or if you're from Niantic then please read a section about my motivations below and feel free to ask, suggest or criticize. I make it for Ingress players and I'm very interested in their opinions.
DOWNLOAD
First: you do this at your own risk! I'm sure it won't brick your phone, but remember you may be banned by Niantic. My mod doesn't do any kind of cheating behavior, it doesn't do anything that original app doesn't do, but there is always the risk.
Also if you downloaded apk from different site then check sha1 of this file to make sure it's ok. Unfortunately such mods create good opportunity to inject some malware, because users search for an application in the internet and anyone can redistribute it. I sign this app with my own keys, so if you have installed my mod earlier, now you have downloaded newer version from the internet and Android says it has different certificates then don't install it!
"Mute" variant has all sounds removed, so apk is ~2.5 times smaller and most likely it uses less memory.
ingress-1.26.1-broot-0.2.0-mute.apk
SHA1: 976342081c963998f8a6e56b735fe97581ab335f
ingress-1.26.1-broot-0.2.0.apk
SHA1: dce5399802c8f11287a7cf399c1bb5265f8251e2
Older versions:
ingress-1.26.0-broot-0.1.0.apk
SHA1: ea95d8e36324c6c4a175e0cf254cd65a4797049f
If you have original Ingress app installed then you have to uninstall it first. Same if you want to install original app over a modded one.
FEATURES / TODO LIST
I know simplifying and automation of too many things may be considered cheating, so I have divided all features into several categories: from the most "innocent" ones to some smart assistants. As I stated above, if you think some of them are just too much then feel free to write about it. For me features up to 3. category are ok. Category 4. may be controversial and I'm not sure if I want to implement it. I'm glad for your opinions. Some features (e.g. 2.11., 3.7.) aren't actually related to category descriptions, but I "feel" them as category 2., 3., etc.
I don't want to force people to use every modification, I'll try to make them all opt-in, so modded app will work exactly as the original one until you change this in the mod menu. If you see e.g. "Fullscreen" feature below then read it as "An option to enable fullscreen mode".
Below is just a list of features to make it clear. Descriptions, notes, statuses, implementation proposals, etc. are here.
Legend:
green - completed
orange - not sure about it
red - rejected
black - waiting / todo
1. Changes strictly technical and/or 4fun - they don't affect gameplay at all:
UI for small screens, but this is never ending task
Disable some graphics effects to make it less GPU consuming:
portal particles
xm particles
Fullscreen.
Remove globe intro.
Change colors of factions.
Exit confirmation dialog - it's good for low memory devices.
Keep sceen on.
Disable vibrator.
2. UI changes: new screens, shortcuts, etc. - it makes things easier, but it won't do anything for you:
New screen with mod settings, credits, etc.
New inventory screen with items presented as a clear table.
Number of all items in the inventory - it's very important because of items limit.
New portal keys screen.
Remove original items screen.
Shortcuts to various actions from the main screen.
Modify chat to make it easier to read and harder to accidentally send private message to public channel.
Link to portals from system messages in the chat.
Real-time distance to portal on details and upgrade screen - its necessity is obvious to anyone who played Ingress
Additional info about the portals directly on the map screen.
Logging and statistics.
Circles around the player similar to one at 40m - just for better feeling of the distance.
Number of keys on portal info, upgrade and linking screens.
Config: update interval.
Config: maximum scanner zoom out.
Deploy button uses highest available resonator, not lowest.
3. Automation of some more complicated or repetitive tasks - it delegates multi-clicking to the squad of highly trained monkeys, but it won't think for you:
Dropping/recycling multiple items of the same type at once.
Firing multiple XMP
Picking up all items in the range - with above it's very easy to give items to other agents.
Hacking all portals in range - not very useful because of timers
Auto deploy resonators using a template.
Templates specific to a portal.
Other agents presence detector.
4. Smart assistants:
Hacking timers for each portal: both 5m and 4h ones.
Auto hacking portals in range while moving (using timers).
Smart auto-deploy.
XMP damage assistant.
Linking assistant for optimum CFs in a specific area.
Continuous linking assistant.
Bugs:
The maps are gray when submitting new portals or reporting bad ones.
NEWS
v1.26.1-broot-0.2.0 has been released!
2013.05.26
Updated Ingress to 1.26.1.
Added layouts for small screens: Eugene's 1.26.0.20130526
Added mute version - for smaller size and likely smaller memory usage.
Added fullscreen mode.
Added option to disable portal particles and xm particles.
Added restart button - it's useful for reloading UI changes (fullscreen mode, layouts, etc.).
Fixed gray maps problem.
v1.26.0-broot-0.1.0 has been released!
2013.05.22
Initial version.
New screen with mod settings, credits, etc.
New inventory screen with items presented as a clear table.
Number of all items in the inventory.
CREDITS
Eugene Kartashov - layouts for small screens.
Of course Niantic Project for this awesome game!
Thanks!

FEATURES DESCRIPTION AND NOTES
1.5. Change colors of factions.
I did this before and it's kind of cool: https://plus.google.com/u/0/106080343103638200670/posts/a9krpWApjz5
2.4. New portal keys screen.
I have some ideas, e.g.:
keys grouping/tagging
group/tag keys manually or automatically by their location, name, etc.
filters and sorting by: name, distance, level, owner, etc.
, but I think Niantic want to improve keys management, so I wait for their move.
2.5. Remove original items screen.
For now even if you prefer new items screen the original one is still needed to access portal keys. We can wait for 2.4. or at least add an option to limit original items screen to portal keys and rename it accordingly.
2.6. Shortcuts to various actions from the main screen.
I think it's one of the most important additions, so it has to be well designed. I see it as a HUD-like buttons similar to "FIRE XMP" when you long-press on a map, but much smaller, probably square with icons. Things to consider:
toolbar at the top or the bottom of the screen - I think it's better than left/right
fixed with 5-6 icons (4" screen) or scrolling horizontally
fixed icons or customize them and their positions
an option to open a full semi-transparent menu with all available actions
Actions could be:
fire last XMP
fire highest/lowest XMP
fire XMP of specific level
same for power cubes
hack portal - click button then click portal. This way you don't have to enter portal details screen which is faster and you don't lose the map.
link portal - same as above
set target? It's in a long-press menu already, but we can add it here for consistency and maybe to remove long-press menu.
actions from other mod additions
2.7. Modify chat to make it easier to read and harder to accidentally send private message to the public channel.
Current problems are:
is there anyone who has never sent a private message to the public channel? Is there anyone who did this only once or twice?
it's hard to read conversations between agents, especially public ones, because they're mixed up with system messages
I was considering adding some kind of filters to select which types of messages you want to see, but it doesn't fix first problem. Now I think of something else - 4 tabs/channels:
faction - as normal
public - public conversation only, so system messages won't disturb you and you don't accidentally respond [secure] messages
system - you can't send a message here
all - all above, so it's similar to current "All", but you can't send a message here - you have to choose proper channel intentionally. It can have additional filters to select messages to show.
This feature may be hard to do or even impossible, because most probably Ingress server doesn't have API to filter messages as above. Of course I can read "All" channel and filter it on the app side, but it may not be that good.
Also I won't be surprised if Niantic itself will redesign chat in the near future, because it's definitely wrong.
2.10. Additional info about the portals directly on the map screen.
E.g.: level, if you have a key (how many?), etc. It could be customizable and there could be a shortcut to toggle showing this info.
2.11. Logging and statistics.
I love this one I can log all kind of actions like: hacking, attacking, dropping and picking up items and XM, deploying resonators and portal mods, adding custom "snapshot points" to organize above, etc. and then create a lot of various statistics:
how many hacks did you do (faction, enemy, neutral) today, in last week or month?
how many items did you get from these hacks?
what were the levels of hacked portals and items?
how many XM did you get?
how did you spend this XM?
how many resonators did you deploy and what were their levels?
how many resonators did you destroy, how many portals did you capture?
how many links and CFs did you create/destroy, what were their MU values?
which portals do you hack/attack/build most often?
how much time you was playing?
what items did you spend to build up a farm and what items did you get from it?
Statistics could be tabular, graph, pie and very flexible. I'm also considering two things:
sending some of above statistics to my server to create global statistics for all users. It would let us do some research, e.g.: what is the probability to get L7 item from L6 portal, etc. Of course sending these statistics would be fully optional, you would have to enable it by yourself.
optional paid application to read these statistics - in addition to the free one. It could let you remove ads or just say "thank you" (i.e. it would be the same as free one), but I don't want to piss off someone in Niantic. I think it would be fair, because statistics app would be quite complicated and time consuming and there will be free version, but you never know what's the opinion of other people.
What do you guys think about above two things?
3.5. Auto deploy resonators using a template.
Agent can configure multiple templates and choose one of them when doing an auto-deploy. Template could be defined by:
its name
minimum and maximum level for each resonator
prefer lower/higher level for each resonator
Examples:
"Lowest portal" - each resonator set to L1-L8 and prefer lower for all - it's the same as clicking "deploy" 8 times.
"Highest portal" - L1-L8 and prefer higher for all
"Highest <L7" - L1-L6, prefer higher for all
"Standard L4" - L1-L6, L1-L4, L1-L5, L1-L4, L1-L6, L1-L4, L1-L5, L1-L4, prefer higher for all - it's standard 4xL4 2xL5 2xL6 and it'll use lower resonators if you don't have all of them
another "Standard L4" - same as above, but L6-L6, L5-L5 and L4-L4 - it won't automatically downgrade resonators, but warn you about the lack of resonators
Also some templates could be predefined by default.
It won't work well with existing resonators, it won't choose optimal way to upgrade them, but this is how it should be - it's just: "do it using a template", not: "Calculate optimal situation".
3.6. Templates specific to a portal.
Extension to above: sometimes you know that e.g. NE resonator of some portal is harder to destroy, so you want to place highest resonator there. You can create a template specific to a portal, so it won't mess up main list of templates and it will be auto selected when doing auto deploy for this portal.
3.7. Other agents presence detector.
It read system messages log to find the last actions and positions of other agents (actually positions of portals they've built/attacked). This information could be used to e.g.:
show last position and action of specific agent
show a list of nearby agents: allied or enemy
alert if some other agent will show up below specific distance from you
4.3. Smart auto-deploy.
E.g.:
calculate max level of a portal that you can build alone - depending on your inventory and already deployed resonators
deploy minimum number and optimum resonators to get to specific portal level
prioritize excess resonators and save scarce ones
deploy high and low resonators evenly to make attacking a little harder
if upgrading existent resonators, prefer to upgrade ones with low XM
4.4. XMP damage assistant.
E.g.:
approximate damage dealt using specific XMP in current position
calculate the best spot to fire XMP of some level
4.5. Linking assistant for optimum CFs in a specific area.
You select a group of nearby portals, assistant build links and guide you through place to get as many CFs and AP as possible.
4.6. Continuous linking assistant.
You see an icon near the portal if it's possible to create a link(s) from it to create a CF. It let you create this CF with few clicks.
It may be not possible to do, because it would have to scan big area to know if there are a link between remote portals.

MOTIVATIONS AND FEW WORDS TO NIANTIC
As I stated above my goal is to make Ingress game better and more enjoyable for people. If you think it's evil then please read my motivations and explanation below:
There aren't and never will be features for cheating: location faking, sending same action several times, automatic passcode submitter, etc.
As I said above I have divided mod features into categories of different "dirtness level". I focus on "clean" features and I'm open to suggestions or criticism from players or even from Niantic itself.
I don't share my code and I obfuscate it to not make Ingress easier to hack by other people.
A whole game and world of Ingress is about hacking and reading between lines. I think my mod fits this world perfectly. There are some people who leak Ingress app from NIA and there is some guy somewhere in the internet who tries to get even more from it. It makes perfect sense
I think there are many good features that will be never added by Niantic. I see several reasons: statistics won't be added because it doesn't make much sense for storyline. Why NIA would add such feature? Intro skipping or new items screen won't be added because these features prioritize quick access over a nice look. Niantic can't do the same because Ingress would look like a game for nerds. But there are many people who don't care about the look because... they're nerds ;-P
And finally: I won't fight Niantic, so if they don't like my mod and decide to react then there will be no mod anymore.
If you're from Niantic then please think what is the best for Ingress users. If you don't like one or two of my features then I'll remove them and keep the valuable ones. If you still think this mod isn't good and it's a matter of time before you react then please do it sooner, not later. Mod won't be very popular yet, Ingress players won't be disappointed so much and I won't lose a lot of my time
FINAL NOTES FOR USERS
Once more: feel free to suggest new features or changes to existent ones. You can also criticize a whole mod idea. I want to know what do you guys think about it.
If you get a force close then post a logcat and mod version here.
If something doesn't look ok then post a screenshot. I have a 320x480 and 480x800 devices, but I can't test it on 240x320 and >480x800 resolutions.
You can also report language faults in the app or even here. English isn't my native and I often write something that doesn't seem natural even to me. I would be happy if someone would suggest better names or descriptions for configuration options, etc.
Of course you can redistribute this mod, but please don't do that if you don't have a good reason. I just want to know how popular it is. Also if you redistribute it then please add a link to this thread to give users a full context.
If you want to make a donation then link is in my signature, but remember that this mod may be killed by Niantic at any time.

[RESERVED]

[RESERVED2]

Very amazing
I'm gonna try it out on a new account just to be safe, but I love the work and holy cow you did a lot and I can't believe it.
Niantic better sit down and learn some must needed features and options. The globe one for sure
Sent from my MI 2 using Tapatalk 2

Keep up outstanding work. I just installed this mod and I confirm that it works flawless.
I'm looking forward to future updates.

iBotPeaches: I did a lot? But you have noticed that above features list is mostly a TODO and for now there are just new items screen and intro skipping? I'm not sure if this is clear from above posts.
I wanted to release it early to get some ideas from people.... or be banned

What about a nosound version? It reduces the app size and removes the annoying sounds for people that are tired of hearing those squeaks
Please find attached a nosound version prototype.

it will be possible to have screen: "exit. are you sure?" when accidentally using back button?

Brut.all said:
iBotPeaches: I did a lot? But you have noticed that above features list is mostly a TODO and for now there are just new items screen and intro skipping? I'm not sure if this is clear from above posts.
I wanted to release it early to get some ideas from people.... or be banned
Click to expand...
Click to collapse
Ahh, I thought you did all that stuff that was bolded in the features list Guess I didn't read it well enough.

Hi, on mine HTC Desire it crash suddnly..
EDIT: Reinstalled, work like a charm..

One thing possibly worth pointing out: I think this version will not handle the new push messages, as I believe those are restricted by the certificate used to sign the app. Are you able to confirm this?
Otherwise, very cool work

phyreskull said:
One thing possibly worth pointing out: I think this version will not handle the new push messages, as I believe those are restricted by the certificate used to sign the app. Are you able to confirm this?
Otherwise, very cool work
Click to expand...
Click to collapse
They do work for me, at least the "@" notifications
Needs further testing.

Jackos said:
What about a nosound version? It reduces the app size and removes the annoying sounds for people that are tired of hearing those squeaks
Click to expand...
Click to collapse
Usually more variants = more problems, but I think mute version may be worth it. It's almost 3 times smaller and space is crucial on many devices. It might also use less RAM and start up faster, because sfx are usually preloaded into memory. I'll do some benchmarks.
ataru said:
it will be possible to have screen: "exit. are you sure?" when accidentally using back button?
Click to expand...
Click to collapse
Sure, but what for? If you accidentally exit application, you can return to it in no time.
phyreskull said:
One thing possibly worth pointing out: I think this version will not handle the new push messages, as I believe those are restricted by the certificate used to sign the app. Are you able to confirm this?
Click to expand...
Click to collapse
I'm not sure about it. I got comm notification today, but I was using Ingress just moments earlier, so it might be background service, not push. We'll see.

Brut.all said:
Usually more variants = more problems, but I think mute version may be worth it. It's almost 3 times smaller and space is crucial on many devices. It might also use less RAM and start up faster, because sfx are usually preloaded into memory. I'll do some benchmarks.
Click to expand...
Click to collapse
Exactly my point of view
However it's a pity that the app uses this same amount of RAM. It might get better if you remove corresponding baksmali lines, I just removed the sound files.
Brut.all said:
Sure, but what for? If you accidentally exit application, you can return to it in no time.
Click to expand...
Click to collapse
I guess it's because on low ram devices the app gets closed instantly. So a back fail-safe button would save him the app loading time.

Impressions and suggestions
Nice mod!
I am an addicted Ingress player and I really appreciate your work!
The new item tab is awesome!!
I only want you to know that there is a G+ user that is modding Ingress too:
Have a look here.
He did a version even for 240x320 screen.
Maybe you can have a look at his work
I hope you can keep this up to date

Works perfectly!
I'll keep an eye on that, your features list sounds extremely promising!

ingress-1.26.1-broot-dev1.apk
It's muted and should work on all screen sizes. Layouts for 240x320 and 320x480 were created by Eugene Kartashov (thanks!), but I have integrated them into single universal apk. It's just ~0.5MB larger than Eugene's separate apks. I can't test it on 240x320 because I don't have such device. Please confirm if it's ok or not. I'll add fullscreen feature before 0.2.0 release, so upgrade button won't overflow on some devices.
Also I can confirm sounds are loaded on demand, they aren't preloaded, so muted version shouldn't boot up faster. It should take less memory though.
Is there anyone who miss these sounds? As I said I would like to avoid fragmentation and I think muted version is just better.

And if you have 240x320 device then please tell me if new items screen looks ok, especially if you have 100+ items of one type. 320x480 seems to be ok.

[ROM][5.X] CyanogenMod 12.1 for Hisense Sero 7 Pro [M470BSA][METICULUS]

CyanogenMod 12.1 is a free, community built distribution of Android 5.1 (Lollipop) which greatly extends the capabilities of your phone, tablet or PMP.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear 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 me for messing up your device, I will laugh at you.
*/
These are CM12.1 builds for the Hisense Sero 7 Pro (Enterprise, M470BSA). It may cause all the things in the disclaimer to happen, or steal your girlfriend while you are busy flashing ROMs.
GPL:
Code:
http://github.com/Meticulus/android_kernel_hisense_m470bsa
Warning: Currently, this ROM is in BETA
Download: meticulus.co.vu
Gapps here or here

I'm impressed. I have a Moto G 2nd Gen, which supposedly was one of the first devices to get Lollipop, but you beat them to it

NEW BUILD!
New build posted!
Mitigated a kernel issues causing lag
CM Sources update

Dude, thanks. Sero 7 and Dev's just keeps surprising me.

LOVE IT, minus one killer bug.
Thank you so much for this wonderful ROM. I understand you are a busy man and are working on many things at the same time. But there is one bug that I've noticed in this build, that may or may not apply to more devices, I am not sure. It seems that it is possible to set the brightness to absolute zero, and by that I mean that the backlight goes completely off and you can't do anything. I had to reinstall the ROM because I accidentally did this the first time I adjusted the brightness. Other than that bug though, this runs perfectly from what I've noticed.
I can't seem to log into your website, it wont send me a password in the email when I try and register, so I'm wondering if it's okay if I can post any bugs that I find here rather than in the comments section there.
Thanks for your work

Quickdraw996 said:
Thank you so much for this wonderful ROM. I understand you are a busy man and are working on many things at the same time. But there is one bug that I've noticed in this build, that may or may not apply to more devices, I am not sure. It seems that it is possible to set the brightness to absolute zero, and by that I mean that the backlight goes completely off and you can't do anything. I had to reinstall the ROM because I accidentally did this the first time I adjusted the brightness. Other than that bug though, this runs perfectly from what I've noticed.
I can't seem to log into your website, it wont send me a password in the email when I try and register, so I'm wondering if it's okay if I can post any bugs that I find here rather than in the comments section there.
Thanks for your work
Click to expand...
Click to collapse
My apologies for the sign up issues on my site. I believe I have them worked out and I have cleared your attempt so you can try again if you like.

NEW BUILD!
External SD fixed
SeLinux: enforcing
:highfive:

I tried to install Mounts2SD after installing the latest build and it warned that the device was S-on protected which never happened on the DoPa 2.51 build. Any thoughts on what this would mean?

lichan said:
I tried to install Mounts2SD after installing the latest build and it warned that the device was S-on protected which never happened on the DoPa 2.51 build. Any thoughts on what this would mean?
Click to expand...
Click to collapse
Hmm... S-on is an HTC thing isn't it? Like some sort of bootloader thing I think... Strange. Might be an Sepolicy issue.
I'll look into it... I currently looking into Apps2SD issues on another device ATM...

HTC and something else if I remember correctly.
Sent from my XT1023

A few things I noticed from the latest build (12/29). These are more notes on what I've observed from using the build so others might know ahead what to anticipate:
1 - I know this is alpha and I'm assuming this is more on the Cyanogenmod end but things really drag speed wise. Hopefully once more bug fixes and optimization happens in the CM12 code we'll start seeing better speed.
2 - Titanium Backup does not want to restore at all. I mean it just sits there. I tried to update Busybox and change over to SuperSU with no luck at all. Maybe it's just me.
3 - I'm assuming we'll see theme options further down the road on CM12? I really don't care much for the color scheme that it comes with stock as I prefer a more holo dark/blue look.
4 - From my limited time in use it seems like most basic functions are working fine for an alpha level build. External MicroSD is working perfectly fine now. I installed PowerAMP from Play Store and both mp3 and flac files are playing fine. Didn't have a chance to test BT. GPS, WiFI, headphone port, audio, etc are all working fine. The only thing I noticed is that WiFi passwords do not stick upon reboot. I know we had the same issue on the Verizon Note 3 with 4.4.2 and it was a simple build.prop fix but dang if I can't remember what that fix is offhand.
Thanks Meticulus for the hard work you've put into bringing us CM12. Can't wait for CM12 to mature and hopefully we'll get CarbonROM Lollipop soon as well.

AngryManMLS said:
A few things I noticed from the latest build (12/29). These are more notes on what I've observed from using the build so others might know ahead what to anticipate:
1 - I know this is alpha and I'm assuming this is more on the Cyanogenmod end but things really drag speed wise. Hopefully once more bug fixes and optimization happens in the CM12 code we'll start seeing better speed.
2 - Titanium Backup does not want to restore at all. I mean it just sits there. I tried to update Busybox and change over to SuperSU with no luck at all. Maybe it's just me.
3 - I'm assuming we'll see theme options further down the road on CM12? I really don't care much for the color scheme that it comes with stock as I prefer a more holo dark/blue look.
4 - From my limited time in use it seems like most basic functions are working fine for an alpha level build. External MicroSD is working perfectly fine now. I installed PowerAMP from Play Store and both mp3 and flac files are playing fine. Didn't have a chance to test BT. GPS, WiFI, headphone port, audio, etc are all working fine. The only thing I noticed is that WiFi passwords do not stick upon reboot. I know we had the same issue on the Verizon Note 3 with 4.4.2 and it was a simple build.prop fix but dang if I can't remember what that fix is offhand.
Thanks Meticulus for the hard work you've put into bringing us CM12. Can't wait for CM12 to mature and hopefully we'll get CarbonROM Lollipop soon as well.
Click to expand...
Click to collapse
1. I have noticed the stutter when launching apps and although I wish i could, I can't blame this on the CM team. I have not yet been able to narrow it down but I'll keep working to find it.
2. SeLinux/SePolicy is much more strict in Lollipop/CM12 as compared to KitKat/CM11. If it is an sepolicy issue then avc denials will show up in the audit log (/data/misc/audit/audit.log). If this is the case then it may be that sepolicy will need to be modified to allow TI to work... However making that change may cause security risks.... Then it may be some else entirely. Logs would be helpful....
3. Afaik, CyanogenMod 12 has not been released yet and there aren't even any official builds for "supported" devices. I suspect they still have a lot of work to do. The new "theme chooser" introduced in CM11 is missing. There is no built in "performance" app as there usually is...
4. Bluetooth definitely does not work. I'm going to have to get creative and/or lucky to get that working properly. It's a question mark right now. I do plan to try to find a way to build and maintain more than one ROM. It'll take some time though... Might not be Carbon... might try a different ROM....

Meticulus said:
External SD fixed
SeLinux: enforcing
:highfive:
Click to expand...
Click to collapse
Is it safe to do a dirty flash? Or should I do a clean install?
Quickdraw996
Sent from my P.O.S. LG L34C using XDA mobile app
(Also, please forgive any errors. I use voice typing because I have big hands and a tiny phone)

Quickdraw996 said:
Is it safe to do a dirty flash? Or should I do a clean install?
Quickdraw996
Sent from my P.O.S. LG L34C using XDA mobile app
(Also, please forgive any errors. I use voice typing because I have big hands and a tiny phone)
Click to expand...
Click to collapse
Don't dirty flash this one, the selinux contexts will be messed up if you do....

Alright, thanks!
Quickdraw996
Sent from my P.O.S. LG L34C using XDA mobile app
(Also, please forgive any errors. I use voice typing because I have big hands and a tiny phone)

Meticulus said:
1. I have noticed the stutter when launching apps and although I wish i could, I can't blame this on the CM team. I have not yet been able to narrow it down but I'll keep working to find it.
Click to expand...
Click to collapse
True. It's a matter of optimizing code and what not I'm assuming.
2. SeLinux/SePolicy is much more strict in Lollipop/CM12 as compared to KitKat/CM11. If it is an sepolicy issue then avc denials will show up in the audit log (/data/misc/audit/audit.log). If this is the case then it may be that sepolicy will need to be modified to allow TI to work... However making that change may cause security risks.... Then it may be some else entirely. Logs would be helpful....
Click to expand...
Click to collapse
I'll try to get you a log in the next day or two. I've been busy working on a project on my Verizon Note 3 not to mention I'm still trying to find a recovery that will still let me restore back to my CarbonROM 4.4.2 backup. Seems like the newer recoveries aren't letting me restore back... very weird.
3. Afaik, CyanogenMod 12 has not been released yet and there aren't even any official builds for "supported" devices. I suspect they still have a lot of work to do. The new "theme chooser" introduced in CM11 is missing. There is no built in "performance" app as there usually is...
Click to expand...
Click to collapse
True true. I was more of less noting there being no theme support for those wanting to know more than anything else.
4. Bluetooth definitely does not work. I'm going to have to get creative and/or lucky to get that working properly. It's a question mark right now. I do plan to try to find a way to build and maintain more than one ROM. It'll take some time though... Might not be Carbon... might try a different ROM....
Click to expand...
Click to collapse
I'll try to get you a log of Bluetooth use on my end alongside with the Titanium Backup issue.

And here we go...
http://www.androidpolice.com/2015/0...-built-lollipop-5-0-1-rolling-select-devices/
Official nightlies are coming out now.

NEW BUILD!
CM Sources update
Tweaks to Kernel for latency...
Feels snappier, but might be a placebo effect.
New bug/issue tracker on the download page. Please submit issues/bugs there. :good:

NEW BUILD!
BLUETOOTH FIXED!!!
Graphical Glitch in Navigation bar fixed
Missing schedulers in performance fixed
:victory:

Really want to try this but its my wife's tablet. So she won't let me. She doesn't want to loose everything on her device.

MoKee OS 60.1 [titan] suspicious activity. Brut or personal data flow possible

Today I've investigated suspicious activity from FMRadio.apk on the latest update of the system.
So I followed whois to discover IPs Firewall managed to block.
There are possibilities of brut attacks or personal data flows.
Stay away from this Chinese little present.
That's the answer to out donates guys.
Pissed off.

LoL. That's nice. How you figured out there is some data flow in the background? Just just started capturing the packets?
http://cyberwarzone.com/malicious-history-of-119-90-35-243/

At first I noticed high battery drain and high data usage. Investigation led me to the app that uses much processor time.
So I installed firewall and set an aggregative rules.
And voilà.
Also there are another dark IPs on the list.

PsyClip-R said:
At first I noticed high battery drain and high data usage. Investigation led me to the app that uses much processor time.
So I installed firewall and set an aggregative rules.
And voilà.
Also there are another dark IPs on the list.
Click to expand...
Click to collapse
Wow that's interesting, nice find. I always suspected Chinese OS leaked info through a backdoor, that's why I've never flashed them. Did you report it to the mokee maintainers?

Thanks for pointing this out, this is really weird. To be fair, I had a look and this FM Radio was directly forked off CM. If you want a fair comparison, you might wanna try to check on CM too (with similar setup of course).
EDIT: I did some extra research and AFWall+ did have this: "Q: I see data traffic consumed by application xyz which is blocked by AFWall+, why? A: It's possible false data traffic. AFWall+ uses IPtables which is at kernel level (low-level). Usage data shown by Android is calculated before it gets dropped by firewall."
So to prove that it's really FMRadio's fault (since interference is possible), a way is to do a test with clean install with nothing else. Feel free to voice your opinions, but I am not here to start a flame fest. I am interested in this weird behaviour too.

Ryuinferno said:
Thanks for pointing this out, this is really weird. To be fair, I had a look and this FM Radio was directly forked off CM. If you want a fair comparison, you might wanna try to check on CM too (with similar setup of course).
EDIT: I did some extra research and AFWall+ did have this: "Q: I see data traffic consumed by application xyz which is blocked by AFWall+, why? A: It's possible false data traffic. AFWall+ uses IPtables which is at kernel level (low-level). Usage data shown by Android is calculated before it gets dropped by firewall."
So to prove that it's really FMRadio's fault (since interference is possible), a way is to do a test with clean install with nothing else. Feel free to voice your opinions, but I am not here to start a flame fest. I am interested in this weird behaviour too.
Click to expand...
Click to collapse
Anyway if that's not FM radio, why does kernel / low level software connects to black IPs?
Can not provide in-depth testing 'cause I stopped using MK immediately after that issue.

PsyClip-R said:
Anyway if that's not FM radio, why does kernel / low level software connects to black IPs?
Can not provide in-depth testing 'cause I stopped using MK immediately after that issue.
Click to expand...
Click to collapse
Something else must have triggered the connection (all high level requests gets completed at low level), but I actually checked those IPs, they aren't really blacklisted, most of them are cloud providers/university
For example:
https://urlquery.net/report.php?id=1463689740716
http://www.iplocationtools.com/192.86.14.67.html
http://www.tcpiputils.com/browse/ip-address/23.251.100.132
This as mentioned in a previous post did not appear at all
http://cyberwarzone.com/malicious-history-of-119-90-35-243/

Ryuinferno said:
Something else must have triggered the connection (all high level requests gets completed at low level), but I actually checked those IPs, they aren't really blacklisted, most of them are cloud providers/university
For example:
https://urlquery.net/report.php?id=1463689740716
http://www.iplocationtools.com/192.86.14.67.html
http://www.tcpiputils.com/browse/ip-address/23.251.100.132
This as mentioned in a previous post did not appear at all
http://cyberwarzone.com/malicious-history-of-119-90-35-243/
Click to expand...
Click to collapse
Just fresh installed mokee, just wondering, why does it have to connect to servers to china and singapore all the time?

Another MoKee security issue
Android/AdDisplay.Waps.Q

I determined a lot of FMradio.apk´s in several ROM´s that ask for root privileges and was wondering why a FMradio needs those privileges.
Also firewall loging shows a lot of activity. I don´t use FM and always delete that apk but if someone is using it: Be careful and check out what´s wrong there.
PS; I don't know if that has anything to do with mokee, stating just about FM radio*s behaviour.

Wolfcity said:
I determined a lot of FMradio.apk´s in several ROM´s that ask for root privileges and was wondering why a FMradio needs those privileges.
Also firewall loging shows a lot of activity. I don´t use FM and always delete that apk but if someone is using it: Be careful and check out what´s wrong there.
PS; I don't know if that has anything to do with mokee, stating just about FM radio*s behaviour.
Click to expand...
Click to collapse
This FM radio asking for root rights .. i had this experience with Turbo, Cdroid ROM too .. Then i had thought that they are coz of rooted device in general. .. now i am afraid ..

When We root and flash any ROM, or Modify OS, Or use Cracked apps, We understand every risk of data leaking. So Posting this useless post is useless. Learn something then Say ****.

hoshang.govil12 said:
When We root and flash any ROM, or Modify OS, Or use Cracked apps, We understand every risk of data leaking. So Posting this useless post is useless. Learn something then Say ****.
Click to expand...
Click to collapse
oh really? you so smart? :laugh::laugh::laugh:

omg
the search for 'useless' in this thread only reveals 1 post

PsyClip-R said:
oh really? you so smart? :laugh::laugh::laugh:
Click to expand...
Click to collapse
zitronenmelissa said:
omg
the search for 'useless' in this thread only reveals 1 post
Click to expand...
Click to collapse
When I tell this on Mokee google+ group the other day, that guy straight to insulting me, so I had to just shut up and laughing instead. He so insist that I'm dumb or noob. Hahaha. What a pathetic group.
It's clear that something fishy is going on, and with no privacy guard control over fm apk, we can't do much aside of freeze the fm apk, and watch for other possible sketchy things from the rom. So if we don't want our data going to "that place", well, I'd say no to Mokee.
As for that guy, he apparently like to insist that we have to surrender our private data when using custom rom etc, and he like to insult us if we don't. :laugh: :laugh: :laugh:

Too bad. Unfortunately I am stuck on mokee because its the only one that still provides OTA Updates for the old Redmi 3 (Ido) after LineageOS dropped support.
I am not able to compile Android by myself.
For V500 and some other devices there is still https://www.los-legacy.de/ but nor for our old gem.
I am nor trying my best to restrict spy-activities using AF-Wall
best regards,
Bul

Flyme 8.9.9.4 Daily [Chinese][ROM][1]

Released date: Sep 4 2019
Attention: Please be careful and backup your data before doing this operation.
Get It From Here
https://download.meizu.com/Firmware...4/cn_daily/20190828023528/7219c6af/update.zip
Do Not Forget To Press Thanks If You Like It
Regards

Additional links from community:
https://drive.google.com/file/d/1-03HpbIqFVgQGRy3RgkcnWLMx1FId-Vt/view?usp=sharing

is that good for daily use? what are the major changes? cant wait to update mine ♥

jeffnai said:
is that good for daily use? what are the major changes? cant wait to update mine ♥
Click to expand...
Click to collapse
A problem improvement, the system solves the problem of power consumption abnormality in some scenes. Solving the problem of APN interface flashback. Solving the problem of blocking the infrared sensor, the screen will appear to solve the problem. Abnormal problem of frosted glass brightness Repair Flyme system service status bar icon shows too large a phenomenon to solve the problem of using the floating ball can not switch multitasking Problem Solving notes and calendar part button icon display abnormal problem Solving part of the model installation application will prompt "analysis software The problem occurs when the package occurs. The problem is solved. The problem of the lock screen interface flashing the lock screen pictorial update is described. The internal test system may have abnormal functions, unstable operation, etc., so as to prevent accidents, please make a data backup. And store the backup data to a computer or other device. The internal test system is updated irregularly according to the test conditions. In order to ensure that the device that is included in the internal test is obtained in time, the latest version will be obtained. If the manual update is not performed in time, the system will automatically update at the appropriate time at night. The update log varies depending on the model, system version or network operator. The differences, the functions and optimizations should be based on the actual performance. * If there is a need to explain the update dynamics will be posted in the bulletin board of the system update app. If an abnormal problem is found in the internal testing process, please promptly feedback through the user help app. * Internal users should perform confidentiality obligations, and it is strictly forbidden to include privately transmitted update files and disseminate system updates, and once found, will permanently cancel the internal test qualification.

jeffnai said:
is that good for daily use? what are the major changes? cant wait to update mine ♥
Click to expand...
Click to collapse
See major changes in abow notes. For daily use, it's not recommended. Since it is a daily version, you have to update it daily and if you are not registered before some internal version letters will be on screen.Wait for beta. If you wait a bit more, stable will be released.:fingers-crossed:

...

Torontus said:
Hey guys. Latest firmwares for our beloved Pro 6 Plus. Get in here https://t.me/s/FlymeFirmwares
Chinese version only!
Click to expand...
Click to collapse
You are not allowed to share this link here. Remove it please. Otherwise it's against xda rules.

adarshm4you said:
You are not allowed to share this link here. Remove it please. Otherwise it's against xda rules.
Click to expand...
Click to collapse
Lets rephrase. I have permission if it complies with XDA rules. Its ok, already deleted.

[ROM][UNOFFICIAL][10] LineageOS 17.1 for Samsung Galaxy Tab S 10.5 WiFi (SM-T800 - chagallwifi)

Hello owners of Samsung Galaxy Tab S 10.5 WiFi (chagallwifi) SM-800,
Let's save some more devices from the garbage. Here is a build for LineageOS 17.1 for SM-T800 (tested only on this device).
Tested and working so far
Wifi.
Camera (front and back).
Location.
Touchscreen.
All other sensors.
I am not aware of anything broken.
This is a plain build of LineageOS 17.1, with only minimal SELinux policy modifications to make the device work.
If you prefer to use OpenGApps, download signed-ota_update-plain.zip, if you care more about privacy and prefer a degoogled version, download signed-ota_update-microg.zip which has microG bundled in it.
Special thanks to owners of:
LineageOS: https://github.com/LineageOS
Exynos5420: https://github.com/exynos5420
Kernel source.
microG: https://github.com/microg
Guide to building LineageOS with microG: https://gist.github.com/dic1911/407184ee427c50ad0066af643a20254f
microG Mobile Services: https://github.com/lineageos4microg/android_vendor_partner_gms
You are welcome

Great news, thanks!
Could you please clarify what you wrote about SELinux? Is it active and enforcing? Is encryption supported?

porcino said:
Great news, thanks!
Could you please clarify what you wrote about SELinux? Is it active and enforcing? Is encryption supported?
Click to expand...
Click to collapse
SELinux is active and enforcing, the modifications are because the default SELinux policies in LineageOS contradict with those of the device (probably because the device ones are few years old). The modifications are to remove some strict policies that would break device drivers like the camera and sensors if left enabled.
Encryption is disabled.

minashokry said:
SELinux is active and enforcing, the modifications are because the default SELinux policies in LineageOS contradict with those of the device (probably because the device ones are few years old). The modifications are to remove some strict policies that would break device drivers like the camera and sensors if left enabled.
Encryption is disabled.
Click to expand...
Click to collapse
It's great that SELinux is on, and it is expected to have minor cuts in the policies. They are a pain to develop. It has to be a separate project...
What's going on with encryption? Forgive me for a silly question, I just see this feature missing in LOS17 ROMs for other devices as well... Is it something LOS specific?

porcino said:
It's great that SELinux is on, and it is expected to have minor cuts in the policies. They are a pain to develop. It has to be a separate project...
What's going on with encryption? Forgive me for a silly question, I just see this feature missing in LOS17 ROMs for other devices as well... Is it something LOS specific?
Click to expand...
Click to collapse
Honestly I don't know about encryption. I didn't care about it while building this image.

minashokry said:
Honestly I don't know about encryption. I didn't care about it while building this image.
Click to expand...
Click to collapse
Fair point - it has to be running at all before looking at the advanced features. For the first release it's quite a remarkable result. It would be nice to have encryption on the to do list...
Another silly question: the speakers of this tablet are not very loud. Is it difficult/possible to boost their volume a little?

Will test this out. I had flashed LOS17.1 by @8224Freak, but its SELinux is disabled. Will see if this one works same or better. Does this build contains the most recent security patch?

@minashokry thanks for the build. Camera only works with picture taking. It freezes when video recording is ended.
​

@minashokry I have been using your build on my T800 and likes it a lot. In addition to the camera video recording freeze, mic does not appear to work well. I tried some audio recordings but only hear tiny sound during playback. I was wondering if you are planning on updating the build once awhile to at least include new security patch., or this is it - no more update? Thanks again for build this smooth LOS17 rom for the old tablet.

foolone said:
@minashokry I have been using your build on my T800 and likes it a lot. In addition to the camera video recording freeze, mic does not appear to work well. I tried some audio recordings but only hear tiny sound during playback. I was wondering if you are planning on updating the build once awhile to at least include new security patch., or this is it - no more update? Thanks again for build this smooth LOS17 rom for the old tablet.
Click to expand...
Click to collapse
Bump

Unfortunately did not get very far using either of these builds (plain or microG). In both cases, I'm unable to read or write to the internal storage on the tablet. File manager does not read any contents of the internal storage, fails to create a directory in internal storage, and can't download/save a file from the internet. The LOS 17.1 by @8224Freak does not have this problem, so assume it's something unique to these builds.
I also found that when I formatted an SD card for use as tablet storage (i.e., as an extension of the internal storage), it insists that the card is not inserted every time I power on the tablet. If I eject and reinsert the card while still powered on (no power cycle) it recognizes it and is okay from there.
Don't know if this is related to the above, but the native camera app insists that I must "Insert an SD card before using the camera" even though an SD card is plainly inserted and recognized by the rest of the system.

minashokry said:
Honestly I don't know about encryption. I didn't care about it while building this image.
Click to expand...
Click to collapse
Hello. I've tested your ROM just out of curiosity -- encryption works! This makes your ROM the leader in security! Well done, thanks!
Apart from this... I found a fault with video rendering. At some resolutions the video renders at a wrong scale, larger than the window or the screen. This happens with different websites. I am using Brave browser, which works fine on the same device with LOS-14.1. The same rendering problem is evident in the other LOS-17.1 ROM as well (by 8224Freak). It might be codec related.

Has anyone found a way of dealing with the video rendering fault in Brave/Chrome/Firefox?

What is the link to download this rom? I can't find it anywhere in this thread.

mmaazzaa said:
What is the link to download this rom? I can't find it anywhere in this thread.
Click to expand...
Click to collapse
Use the attachments to the first post "signed-ota...zip".

Thank you. Due to the file name I mistakenly thought it was just an update for the rom, not the rom itself.

Tried this ROM again (signed-ota_update-plain.zip), different screen resolutions, different screen densities - still video playback issues in browsers including Brave. The fault manifests itself as the video being zoomed in, so that only a part of it remains visible. The playback freezes for a fraction of a second occasionally, producing a "metal" screeching sound while doing it. In general this ROM feels a bit laggy. So, going back to lineage-14.1-20220107-UNOFFICIAL-chagallwifi, which feels cleaner, much faster and similar to this one has SELinux+encryption working.
Before anyone asked, the same video playback issues just without freezing I observed in lineage-17.1-20220504-UNOFFICIAL-chagallwifi, which is under active development now. The latter does not have SELinux+encryption though.
So, for now, the benchmark is set by DarkExistence for this device.
[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 - SM-T800
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device. #include /* * Your...
forum.xda-developers.com

Just tried this rom, I'm pretty sure the hitching and video playback issues are because the gpu is sitting at 0% utilisation so it's using the cpu for rendering... which would explain things

I downloaded and installed "signed-ota_update-plain.zip". But Google account is not added. There is no Google Play. Thank you to those who will help.
I installed Gapps and OK.

ahmetdamar said:
I downloaded and installed "signed-ota_update-plain.zip". But Google account is not added. There is no Google Play. Thank you to those who will help.
Click to expand...
Click to collapse
Did you install Gapps or its equivalents?