Database Info

[PRJ]EBI0/EBI1 single kernel idea

I was going through the process of patching a kernel for EBI1 and I got to looking at the code for the patch.
To summarize.
Its the addition of an offset
Code:
* physical offset of RAM */
+#if defined(CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1)
+#define PHYS_OFFSET UL(0x19200000)
+#else
#define PHYS_OFFSET UL(0x10000000)
+#endif
2 Memory maps decided upon by an IF statement in board-troat.h
Code:
#if defined(CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1)
3. Changes to board-troat.c to work with new memory map values.
Shouldnt we be able to:
1. Add a little list to the header file defining which radios are EBI0/1.
2. Read the command line from the SPL for "androidboot.baseband=".
3. Alter the memory map accordingly, possibly having all Dreams use an offset?
4. Be a one kernel community

Ive been doing more reading and see how my comment about all dreams using the same offset is.. wrong. My current cobbled understanding is that, the radio sends commands to the cpu setting up hardware addresses for the sdram. Im open to correction though.
I put together these maps using the board-troat.h files. I'll post them to see if anyone finds them useful/interesting. If they're incorrect let me know and I'll fix them or take them down.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why does an EBI1 phone have double the camera memory? and that extra memory on a EBI0 phone is unmapped? Why would an EBI1 framebuffer be shrunk down? Cam anyone shed some light on the situation. Ram Hackers Maybe.
More importantly though, can any logic or command line be applied to zreladdr-y, params_phys-y and initrd_phys-y so the kernel can know off the hop where to start in ram?
OR
Can we use enough SMI to boot a kernel since the addressing seems unified?

I've been continuing my reading in my bits of spare time and heres where im at.
-The SPL Reads the boot Image from nand.
-Examines its base address from the header and copies the image to that location.
-The Decompressor runs and extracts to zreladdr
-?? ram drive is extracted (by arch/arm/boot/bootp/init.S ?)
-kernel is executed at zreladdr
Is the Base address that mkbootimg puts into the boot image header pass to the decompressor? It seems to me it must to function.
If it is than this patch seems like it is close to what would be needed, accept I dont think it would handle the initial ramdrive.
This bases on work done earlier by Lennert Buytenhek and Mark A. Greer.
Compared to their approach zreladdr isn't guessed based on the pc
register but the bootloader is expected to pass PHYS_OFFSET in r3. If
that value doesn't look right (e.g. isn't aligned) it is guessed based
on the value of sp. This should work for CONFIG_ZBOOT_ROM, too.
To use it for your machine removing the definition of PHYS_OFFSET from
<mach/memory.h> and selecting CONFIG_RUNTIME_PHYS_OFFSET should be
enough.
Click to expand...
Click to collapse
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-January/008994.html
Im not even sure whether posting as I go is the right approach. I dont know if I havent gotten a comment because the concept is just flawed, in a way that im not realizing, or its just such large amount of work noone has found it worth while. I Do realize that my comments show that I don't have the skills to complete this on my own but as I read more and more It just keeps looking like it should be possible. So I will continue to conceptualize this idea until I'm told why its not possible/practical, and hopefully someone with coding skills sees the value and takes the lead.

There's not a whole lot of interest for some reason. I'm on a Rogers Dream with EBI1 kernel so this does affect me. But most xda user are American and don't care about EBI1 since they only have the mt3g1.2

xaueious said:
There's not a whole lot of interest for some reason. I'm on a Rogers Dream with EBI1 kernel so this does affect me. But most xda user are American and don't care about EBI1 since they only have the mt3g1.2
Click to expand...
Click to collapse
Your phone is perfectly compatible with EBI0 radios. Why not just fix it?

lbcoder said:
Your phone is perfectly compatible with EBI0 radios. Why not just fix it?
Click to expand...
Click to collapse
as I have.

Significant Battery Drain, High CPU Load when Idle

I just got my Thunderbolt yesterday, and so far, I love it. But I've been seeing the battery drain far too fast. According to the stats, it's been awake for a little over 2 hours, not doing anything significant, and the battery is at 60%.
I think this might have something to do with the CPU usage.
If you look at this top screen on the device:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The CPU is mostly idle, but the load is >6. I'm not sure what would case this, but I suspect it's related to the power drain.
Anyone have any ideas?

quick q. do you use a lockscreen with pattern lock or PIN or something?

your best bet would be to use system panel, the paid version unfortunately, to analyze a period of a few hours and it will show you a break down of each and every process that hits the CPU, and how much it used, etc all in a very nice graphical view. its similar to the top command, but much more helpful.

ddarvish said:
quick q. do you use a lockscreen with pattern lock or PIN or something?
Click to expand...
Click to collapse
I do (enforced by company policy). Do you think that's related?

Ahhh, I've seen stuff like this on Linux servers before.
In one case, all the system processes were idle, but the load spiked to 25.00 during intensive disk writes. As it turns out, all of this processing was packed invisibly into the kernel; I was using software RAID at the time, and the RAID5 subsystem has to calculate parity bits for written data. So that's what was hogging CPU -- that, and the fact that my stripe width was 1 MB, probably way too big.
In another case, there was a kernel bug with the development kernel I was using (I think it was an -rc of 2.6.32) where something in the kernel core was constantly awake -- an infinite loop or livelock or something.
There's certainly the possibility that HTC and Verizon might have both missed something as glaring as that, but then their testing would have revealed markedly low battery life -- could they ship the device in good conscience in that state? WOULD they?
Basically, you can get high "load" in top even when it doesn't correspond to a userspace process or a labeled kernel thread. Things that contribute to load include:
1. Context switches (between user and kernel)
2. I/O (i.e., network, disk)
3. Kernel activity, both within the main kernel binary and in modules
4. CPU activity in userspace processes
Unfortunately, the process list in top doesn't always jive with the numbers in the load, because not all of the things that contribute to load can be attributed to a single process.
For example, if there's a kernel bug, and a single syscall from a userspace process foo.bin costs an unreasonable number of context switches, the CPU will spend as much time as it can trying to context switch to satisfy the syscall. I suppose if there were a "kernel" task in top, you could attribute the CPU time to that, but it wouldn't be fair to blame it on "foo.bin" because all the work (the context switches themselves) is being done in the kernel. That's just one possible example.
Oh, I forgot to ask: are you root? If not, you may not see processes reported in top that are owned by other users. So you might not even be getting the full picture of the userspace processes running on the device, let alone kernel tasks and other less tangible effects.

Before I rooted, I had System Panel installed and everytime I checked my CPU was at 99% and full 1024 on the clock.
After root, my CPU drops into the 1 digit %'s all the time, CPU speed runs between 600 - 1000mhz.
edit: this is on the stock RUU and stock kernel

Adam B. said:
I do (enforced by company policy). Do you think that's related?
Click to expand...
Click to collapse
i dunno.. it may be. read the thread i started here on why..http://forum.xda-developers.com/showthread.php?p=12301209#post12301209
i am trying to run a couple experiments in the next day or two to figure it out. its crazy that battery life varies SO much for people.

allquixotic said:
Ahhh, I've seen stuff like this on Linux servers before.
In one case, all the system processes were idle, but the load spiked to 25.00 during intensive disk writes. As it turns out, all of this processing was packed invisibly into the kernel; I was using software RAID at the time, and the RAID5 subsystem has to calculate parity bits for written data. So that's what was hogging CPU -- that, and the fact that my stripe width was 1 MB, probably way too big.
In another case, there was a kernel bug with the development kernel I was using (I think it was an -rc of 2.6.32) where something in the kernel core was constantly awake -- an infinite loop or livelock or something.
There's certainly the possibility that HTC and Verizon might have both missed something as glaring as that, but then their testing would have revealed markedly low battery life -- could they ship the device in good conscience in that state? WOULD they?
Basically, you can get high "load" in top even when it doesn't correspond to a userspace process or a labeled kernel thread. Things that contribute to load include:
1. Context switches (between user and kernel)
2. I/O (i.e., network, disk)
3. Kernel activity, both within the main kernel binary and in modules
4. CPU activity in userspace processes
Unfortunately, the process list in top doesn't always jive with the numbers in the load, because not all of the things that contribute to load can be attributed to a single process.
For example, if there's a kernel bug, and a single syscall from a userspace process foo.bin costs an unreasonable number of context switches, the CPU will spend as much time as it can trying to context switch to satisfy the syscall. I suppose if there were a "kernel" task in top, you could attribute the CPU time to that, but it wouldn't be fair to blame it on "foo.bin" because all the work (the context switches themselves) is being done in the kernel. That's just one possible example.
Oh, I forgot to ask: are you root? If not, you may not see processes reported in top that are owned by other users. So you might not even be getting the full picture of the userspace processes running on the device, let alone kernel tasks and other less tangible effects.
Click to expand...
Click to collapse
Interesting info. I'm also a Linux admin, but I haven't really run into situations like this.
It is very odd that I see nothing in the user space that would cause this. http://pastebin.com/J4PwuMeZ Every process is sleeping, and nothing seems to be waiting on IO.
I suppose it could be an issue with the kernel. We'll have to wait and see what happens when the source is released and people start to release new updates.
I am root, btw.

[ROM] pffmod Revoke permissions & Privacy mode

Long time no see.
Any way there is a new build this one is based on the latest and greatest from CM 7.1. the download link is below.
Spoofed permissions:
READ_PHONE_STATE - You can now make your device return spoofed data from the methods protected with READ_PHONE_STATE permission. There is a demo app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
you can use to see the effect of spoofing and revoking READ_PHONE_STATE permission. Run the app revoke or spoof run the app again.
Since majority of time spend on READ_PHONE_STATE spoofing was about laying the needed infrastructure for spoofing in general, expect new spoofed permissions shortly.
ROM info:
This is a preview build bases on CM7 nightly builds. Some things may not work some features may be missing.
Some applications may not work properly with revoked permissions.
You can revoke permission of SYSTEM applications!!! DON'T DO IT UNLESS YOU KNOW WHAT YOU ARE DOING.. However reboot resets the permissions of the system applications so you probably can recover.
If an application is running changing some permissions like say INTERNET will not be fully applied until the application is restarted.
If you come from CM7 nightly or CM7 RCx you probably don't need to wipe. I something is not working do a wipe.
Google apps are not included. You need to download them separately and flash them right after the ROM.
It will probably require ClockworkMod 3.x to flash properly.
You uses it at your own risk and I cannot be held responsible for the consequences.
Some technical stuff:
If an application checks for its permissions it will appear that all required permissions are granted. This is done to keep some ad networks code happy. As far as I've tested this is safe since the permission check is done at the remote end of the call when protected method is invoked. Please report your findings.
Screen shot:
This is the extended Manage application screen.​
Download:
update-pffmod-7.1.0-Desire-KANG-signed.zip
old builds:
direct link: update-pffmod-0.9.1-Desire-DEV-20110418-signed.zip storage provided by: http://onlinestoragesolution.com
direct link: update-pffmod-0.9.0-DESIRE-DEV-20110328-signed.zip storage provided by: http://onlinestoragesolution.com

Wow, This is so quick, I read about it in Reddit day back. Thanks! Still there are lot of discussion about this between developers.
Details here
http://www.androidpolice.com/2011/0...rmissions-cue-mass-force-closing-as-a-result/

ukanth said:
Wow, This is so quick, I read about it in Reddit day back. Thanks! Still there are lot of discussion about this between developers.
Details here
http://www.androidpolice.com/2011/0...rmissions-cue-mass-force-closing-as-a-result/
Click to expand...
Click to collapse
Actually I've submitted this to CM
here is the original thread for Desire HD http://forum.xda-developers.com/showthread.php?p=12161601#post12161601

Great patch though Personally I feel this is great addition.Thanks for this! I'll try this and let you know.

new build with data spoofing see the first post.

Neat!
Is this based on something close to nightly 41? There's been a major bug recently, which caused many issues, it's fixen in #41.
http://cm-nightlies.appspot.com/?device=bravo
p.s.
Please add this to the CM branch...

JDima said:
Neat!
Is this based on something close to nightly 41? There's been a major bug recently, which caused many issues, it's fixen in #41.
http://cm-nightlies.appspot.com/?device=bravo
p.s.
Please add this to the CM branch...
Click to expand...
Click to collapse
This is like current git

Swapping real IDs for the word "spoofed" is quite obvious, and, IMHO, might cause problems if an application stores it as an integer value. Why don't you just return random numbers?

I'm working on something that will generate plausible data from the calling app package name. I'm just too impatient and decided to release it early.
The other thing is that it's bean too long since the last release

And a final request. Please do something with the usability Maybe a dropbox underneath each of the permissions. Best if colored - red for "revoked", yellow for "spoofed" and "granted" without highlighting. Currently, a brief view at the list of permissions totally misses their states.
Yes, I do understand the engine is far more important than bells&whistles, but as for me, the mod is quite ready for everyday use, and I'd be happy to see it more user-faced.

JDima said:
And a final request. Please do something with the usability Maybe a dropbox underneath each of the permissions. Best if colored - red for "revoked", yellow for "spoofed" and "granted" without highlighting. Currently, a brief view at the list of permissions totally misses their states.
Yes, I do understand the engine is far more important than bells&whistles, but as for me, the mod is quite ready for everyday use, and I'd be happy to see it more user-faced.
Click to expand...
Click to collapse
Interested in helping with that?
Just grab AppSecurityEditablePermissions.java, app_editable_permission.xml and app_editable_permission_item.xml from http://review.cyanogenmod.com/4055 and start hacking

New build... Link in the first post.

[APP]Voltage Control - control OC/UV for OC kernels

I take no responsibility for ANY damage / data loss may occur. Use this at your own risk. Beta quality software!/Alpha quality features!
The app has its roots in Samsung i9000 (Galaxy S) and i9100 (Galaxy S2).
Now its time for wider audience, I think its ready for use on many more devices.
Stats:
It has over 100.000 market downloads and over 50.000 active users!
I know its been posted elsewhere, but I've seen some similar apps posted in this forum, I think that my app is worth it.
ICS compatible
(lol ofc)
Look for kernels with this label:
Kernel developers who added VC support please show this image in your topic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features:
- minimum/maximum CPU frequency choosing
- selecting IO scheduler
- selecting CPU governor
* changing voltage per frequency
* chosing which frequencies should be used and which shouldnt
- saving settings to be automatically applied at boot (init.d script, startup service)
- save/load 1 profile (lite)
- Widget with profile switcher and app launcher (passive, little to no resources used!)
- well designed and highly optimised UI (I hope..)
- robust kernel detection, support of not-so-well-working kernels
- device info page
- Siyah SGS2 kernel interfaces (Charging current and GPU OC/UV, bus frequency)
- (extreme) CPU usage history page
- (extreme) multiple profiles support
About donations:
This software is available free of charge.
It cooperates with OC kernel by raspdeep.
It uses some code from: MarketEnabler (Fool your market to make all apps visible!)
If you find this software useful, please consider funding a beer and pizza. There is a "Donate to me" link just over my avatar.
Donator list:
nitr8
kalpik
laststufo
glitterballs
screwyluie
Gembol
Coreym
...
many, many more (1000+) users from Android Market!
Thanks!
How to?
Generally idea is simple: make changes and hit apply. If any changes have been made apply/discard buttons appear on bottom.
The first tab, "General" allows to change scheduler, governor/min and max frequencies.
Everything is easy and straightforward, if You need help ask here.
You can always discard changes before applying if you want start from loaded settings.
Profile support:
To save as boot -> press menu key, then select "Save as boot settings".
Boot settings are automatically loaded on every device boot.
RECOVERY
If Your device freezes after boot because of too agressive boot settings (init.d):
Just use vcremoveboot.zip which is placed on /sdcard/. App will ask you to place it, I recommend to do so.
To avoid problems use startup service; its safer and more realiable.
FAQ:
Q: Extreme version?
Yes, I wanted to give some extras for people that support my work.
For now features exclusive to Extreme version are:
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
+ CPU usage history page
+ multiple profiles support
Basic functionality will allways remain free. This relies on work of multiple kernel developers, so I really cant ask money for what they have done!
Q: What is it?
Its voltage control app for undervolt and overclocking kernels providing sysfs interface.
More and more developers are releasing wonderful kernels with customisation options. My goal is to make it user-friendly, easily and safe to use them.
Q: What does it mean to undevolt, and what is overclocking?
Read more in "OC / UV 101" section That is a detailed(sort of) explanation what UV/OC means.
Check this great overclocking/undervolting guide by shaolin95 (thanks!) and discussion topic!
Prerequisites:
-root (superuser + su)
-busybox
-OC kernel supporting either UVLF and UVHF
Voltage Control Extreme unlock Key on Android Market!
For now features exclusive to Extreme version are:
+ More than two profiles
+ CPU History page
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Click to expand...
Click to collapse

-----reserved-----

good one! thanks

How ca I set profiles? I have valid Extreme license.
Edit: Ok, I found it. But is there some tasker to set profiles depending of time or screen state for example?

Go to profiles menu by pressing on the app title, then press + button on the end of the list, enter a name, select it from list, apply
//edit: no there is no such functionality yet.
I can do that, but I'm not sure it shoud be present. I dont want the app to consume any resources when not running.

I think it would be nice feature, but it's just my opinion... Maybe some poll?

I just downloaded SleeperRom on my Epic 4g and this app came in with the rom. I'm curious and want to play around with it, since I am new to rooting. I see that there are few different cpu governors, but I do not know anything about it. So I'm wondering to see if you could list and explain what those are? Any help will be appreciated!

Here you go:
http://forum.xda-developers.com/showthread.php?t=1369817

[APP][ROOT][4.1+] Kernel Toolkit Kernel Settings

Kernel Toolkit allows you to manage kernel settings on your rooted device. This app is a solo effort, my main goal is to simplify kernel tuning and provide a clean looking modern UI with the lovely new material design.
The app is stable, however not entirely feature complete. Expect frequent updates with new features. I wanted to get the basics working and published as soon as possible, to get feedback and all bugs worked out.
Currently it provides all the fundamental settings for kernel tuning. There are several other features that are currently in development that will be added very soon.
Development Update
- The app is ready to be translated to other languages. If you'd like to see the app in your language, please let me know via posting or PM. I will send a auto-translated set of strings to someone who speaks the language to make revisions. The process is very fast and the app will be updated promptly. new
- Before you leave a poor rating in play store, please let me know what I can do to improve the app. This app is the result of listening and responding to feedback and criticism, I take all recent feedback into consideration during every update.
Features
- Live device stats
- Time in cpu states with custom references
- Adjust kernel settings:
- Cpu governor
- Cpu governor parameter control
- Gpu governor/max frequency
- I/O scheduler
- I/O scheduler parameters
- Read ahead buffer
- Voltage table control / global adjustment
- Enabled/disable system executables including Mpdecision, Pnpmgr
- Apply settings on boot
- Intelliplug settings
- USB fast charge toggle
- Screen wake control
- Big and small core separate control new
- And many more
Features in development
- Per app profiles new
- CPU, RAM, device stat widgets new
- Thermal threshold settings
- 4.0 ICS compatibility
- You tell me
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bug reports
Please send bug reports via email @ [email protected] or by PM on xda. Please include your device name and android version.
Feature requests
Please do not hesitate to send feature requests (via email @ [email protected] or by PM on xda). Always open to new ideas and features.
Download
Download via Play Store: https://play.google.com/store/apps/details?id=com.dsmartapps.root.kerneltweaker
Support with donation
Credits
- Google for SlidingTabLayout
- Pnikosis for material indeterminate progress bars on pre-lollipop > https://github.com/pnikosis/materialish-progress
- @haqanguven for Turkish translation
- @RASTAVIPER for Greek translation
- @ChiDi9901 for German translation
- @neytireyqa for Czech translation

Guide to kernel settings
http://forum.xda-developers.com/lg-g2/help/test-t3032171
http://www.androidcentral.com/fine-tuning-minfree-settings-improving-androids-multi-tasking
https://android.googlesource.com/ke...7aebe08b/Documentation/cpu-freq/governors.txt
Recommended settings for Lollipop
The following are changes I made on the stock kernel on my GPE m8
- multicore power savings: enabled (1)
- minfree settings: medium
Default minfree settings on lollipop are very aggressive. If you have at least 1 GB of RAM you should lower the values.

This looks nice man!

I get FC upon the opening of the app and I tried to clear cache and data for it and it's not working for me.
I send the report through the google, if you didn't received it let me know how and I try to redo it again, might help you find the problem.
Nexus 6 - BlissRom 2.0 - Despair Kernel

Nice attempt..looking forward to this

Hi there.
thank you for your app,but i keep getting Fc on my m8 running ARH34 and elementalx kernel.
pls fix this.
thanks.

ForceCloses too on my mtk6592..with Team Force Kernel

The UI is pretty Cool .. Will try asap (Y)

doesn't start on my phone FC, very time.
Phone: LG E975 running cm12 nightly
log link

Force close on my M8 with ARHD 34.0 and Elemental X kernel.

Looks nice brah! Thanks for the application!

Force closes on my MTK6592 device (octa-core)
Exception class name: java.lang.NullPointerException
Source file: LinuxSystem.java
Source class: com.dsmartapps.root.kerneltweaker.LinuxSystem$StatsPoller
Source method: onReadCores
Line number: 647.
I'm guessing this is because of the 8 core processor?

Force close Nexus 5 euphoria OS 29th build

Nice
Looks great, I'm gonna try it right when I get home

Hey guys, thank you guys for reporting the FCs.
These are very simple bugs to fix i'll try to get an update out later today.
This was sort of expected with release as this app can't be tested on an emulator since the emulator has no kernel files. Please bear with me and don't give any bad ratings in the play store just yet!

aksclusive said:
Read this post and save money on 3G data
http://forum.xda-developers.com-limit-mod-t3021683
Click to expand...
Click to collapse
Your SPAM is not needed here.

FC in Moto G 2013 with Lollipop 5.0.2 stock (stock kernel too), after giving root permitions...
More here:
Exception class name:
java.lang.NullPointerException
Source file:
LinuxSystem.java
Source class:
com.dsmartapps.root.kerneltweaker.LinuxSystem
Source method:
getExecutableState
Line:
565
Stack trace:
java.land.RuntimeException: An error occoured while executing doInBackground()

Just tested on my Galaxy S4 running CM12 and it FC'd. Hopefully fixed in next update, looks good from the screenshots though!

Okay update has been pushed out. Should be in the play store within an hour or so.
Most FCs have been fixed. In some cases I did a temporary work around until I figure out whats going on on some devices system files.
There is one issue on some devices thats causing a crash when reading the min/max frequencies which is strange because they should be the same on all devices. Its possible this is caused by missing busybox installation. You can install it via playstore if your rooted. If your still getting FCs and are familiar with ADB cmds, I may need your help by running a few cmds to look at your device files. I might make a debugging apk that reads your system files if anyones willing to help out. I'll keep you guys posted.
Until then stay with me my #1 priority right now is to get this working on all devices!

Heisenberg420 said:
Okay update has been pushed out. Should be in the play store within an hour or so.
Most FCs have been fixed. In some cases I did a temporary work around until I figure out whats going on on some devices system files.
There is one issue on some devices thats causing a crash when reading the min/max frequencies which is strange because they should be the same on all devices. Its possible this is caused by missing busybox installation. You can install it via playstore if your rooted. If your still getting FCs and are familiar with ADB cmds, I may need your help by running a few cmds to look at your device files. I might make a debugging apk that reads your system files if anyones willing to help out. I'll keep you guys posted.
Until then stay with me my #1 priority right now is to get this working on all devices!
Click to expand...
Click to collapse
Updated and working. Very nice UI. Thank you.