Related
Basicly when I reboot or turn on my g1 I have to go through reseting my battery widget and my overclock app. I have tried reinstalling and unistalling. I have even deleted the apps and the dalvik for them off me partition. Anyone run into this? I would like to fix without a wipe. I just spent the last 3.5 hours reflashing, setting up wifi and data, and arraging icons. I really dnt feel like doing that again.
Almost for got the names of the apps. The battery widget is from curvefish and the overclock is from billy chu overclock widget. !MODS PLEASE FORGIVE IF I POSED IN THE WRONG SECTION!
pistol4413 said:
Basicly when I reboot or turn on my g1 I have to go through reseting my battery widget and my overclock app. I have tried reinstalling and unistalling. I have even deleted the apps and the dalvik for them off me partition. Anyone run into this? I would like to fix without a wipe. I just spent the last 3.5 hours reflashing, setting up wifi and data, and arraging icons. I really dnt feel like doing that again.
Click to expand...
Click to collapse
Now that you mention it... I've noticed a problem with Locale. I don't use the ones that you mentioned so I can't comment. But with Locale, I use it to send texts to my girl to make sure she's up for work (three alarm clocks aren't enough but a text from me seems to work just fine). I set it up differently almost every day.
The conditions are based on time, which change depending on what time she wants to wake up by my text. So I make the changes, save twice, hit home and I should be done, right? Not always. Several times the condition didn't save and she ends up getting the text either way too early or way too late. Pretty annoying. So to make sure it saves, I have to reboot and check it on the next start up. Sometimes it saved and works, sometimes I have to try it 3 or 4 times to get it to stick. I do nothing different and I consider myself a pretty loyal user of the app. Let's put it this way... if twofourtyfouram decided to charge $20 for the app, it would suck but I wouldn't hesitate to buy it even if it doesn't always save for me. Anymore then $20 I would probably just remind myself to silence my phone so my custom Saw ringtone for my mother doesn't go off in church... again. Damn Meltus v3 audio mod!
Could be a defect in the programs themselves, OR, if you've been messing around (i.e. with apps2sd), then you could have a PERMISSIONS problem. Look around for the fix permissions script and try that.
fix permisions
lbcoder said:
Could be a defect in the programs themselves, OR, if you've been messing around (i.e. with apps2sd), then you could have a PERMISSIONS problem. Look around for the fix permissions script and try that.
Click to expand...
Click to collapse
How would I go about doing that? And use marcus' apps2sd app
lbcoder said:
Could be a defect in the programs themselves, OR, if you've been messing around (i.e. with apps2sd), then you could have a PERMISSIONS problem. Look around for the fix permissions script and try that.
Click to expand...
Click to collapse
I do fix_permissions from terminal everytime I install/update an app.
It may just be Locale, but I've never read about someone else with the same problem as myself. I've even tried removing the app and browsing to /data/ and /dalvik-cache/ to make sure there was nothing left behind.
I still get the issue but not very frequently.
logcat
I have the logcat if anyone thinks they can help. Email me at [email protected] and I will send it to them.
logcat file
its attached to the message. hopefully someone will read this thread and provide a solution to fix this that doesnt envole the words WIPE AND REFLASH! srry it had to be a zip i didnt feel like breaking up the log
problem solved!
Well after numerous emails back and forth with the devs of the apps I was having issues with I found the solution:
$su
#cd /data/data
#rm -rf (enter app name) ex. Com.xxxxxxxx.xxxxxxxxxx
MODE IS.NEED BE U CAN LOCK/CLOSE THREAD!
Hey all i created this thread for ADVANCED users (and some newbies lol) so that i can better help users tweak and improve performance on their eris. My inbox was getting crazy so i thought this would be better i will still take pm questions but it would be better if we can all learn here. This isn't really a place to report bugs as it would be better to contact your respective developer or post in that developers thread. I will try my very best to get the best performance out of your eris and hopefully we will have some fun along the way. So hopefully this can help take some of the load off of the developers threads and reduce noob-age.
I ONLY ASK THAT IF USERS WANT TO TWEAK I STRONGLY RECOMMEND THAT YOU EITHER..........
1) PURCHASE ROOT EXPLORER FROM THE MARKET OR THE FREE ESTRONGS FILE EXPLORER APP FROM THE MARKET WHICH ALSO ALLOWS ROOT ACCESS AS WELL.... BUT I THINK ROOT EXPLORER IS BETTER IMHO.
2) HAVE ADB SET UP FOR YOURSELVES AT HOME OR KNOWLEDGEABLE OF ADB. I WILL NOT HELP YOU SET UP ADB OR THE SDK
ALSO I RECOMEND PURCHING THE FULL VERSION OF TITANIUM BACKUP AS IT IS AN INVALUABLE TOOL FOR ROOTED USERS AND MAKES BACKING UP AND TWEAKING MUCH EASIER FOR NEWBIES PLUS IT HAS SOME REALLY AWSOME FEATURES
so hopefully this will give us fun things to do in between releases from our devs. And always remember to donate to these awesome awesome eris devs for their hard work and commitment to us.
i want to keep an open discussion thread, nothing is off the table.
kernels
kitchens
cooking
roms
tweaks
hacks
apps
fixes
workarounds
you name it lets talk
lets figure it out together while learning along the way
Things are always changing so if you see any errors or things that need to be updated please let me know and i will be more than happy to get the correct information posted.
Moving apks and deleting dulicates...make your system efficient
YOU need either rootexplorer OR be ADB inclined to do the following....
i was thinking while doing some root exploring of ways to make this rom more solid and here are a few tips i thought everyone could use.
IF YOU DONT HAVE DUPLICATES DONT KILL YOURSELF SEARCHING JUST CONSIDER YOURSELF LUCKY. AND YOU DONT NEED THIS POST
FIRST
when i flash a Rom i always do my set up. here is an overview of what i do when i flash........
-i flash the Rom
-then i login to google as normal so i can receive Titanium Backup (TB) and Root Explorer (RE) from the market updates
if someone could be kind enough to give us a sample command to use terminal to install apps from the sd would be a great shortcut for us
-move those two apps from data/app to system/app
-then i do a full wipe (huh a full wipe you say....system files are never wiped....they can only be flashed over, so TB and RE will still be there)
-clean nand (so if you get crazy and screw up you can easily start over)
-Rom surgery
-Restore
-login to google last and sync
-batt tweaks and extras
this process IMHO makes your rom way more efficient than flashing, login and syncing.
OK
first thing i do when i flash a rom is to remove junk
i navigate with either explorer to system/app folder
then i remove all the useless apps i dont use, need or want
AND/OR remove the "ONE USE" apps (like setupwizard.apk only need it once or none at all if your a pro )
this reduces the ROMs footprint making it smaller
the smaller the Rom the better the faster
here are some things i like to rip out of system/app folder....
ADWLauncher.apk (make sure you have another launcher first i use lanucher pro)
Mail.apk (i use gmail)
Twitter.apk (i currently dont tweet)
ProTips.apk
HtcCalibrate.apk (after i calibrate of course)
Launcher2.apk(why have a bunch of other launchers you dont use hogging memory get rid of them)
MagicSmokeWallpapers.apk (this dont work for me but other do)
Carhomegoogle.apk ONLY
etc. there are others you can remove as well depending on you
and we will experiment to find more......
NEXT
i like to move IMPORTANT apks or apps from the data/app folder to the system/app folder epically if your Rom dev has not updated the gapps lately or you cant get access to the latest gapps.zip.
if you do not then you will end up with a lot of duplicate apps installed in your system when ever you receive a gapps update and that wastes memory and will cause memory issues in the future and it screws with autokiller
i like to move my favorite launcher (launcher pro paid) to the same place where launchers go, in the system/app folder (why have your launcher where regular apps go and get killed by autokiller) i think this is better for the system and doesn't hog your app data space plus it adds stability to your launcher.
here are some things i like to move into system/app.....
i like move into system/app are
launchers (stabilze launcher)
keyboards (should speed up keyboard strokes)
root tools and IMPORTANT apps (R.E. T.B.)
security apps (never deleted or wiped in case of theft, hoping thief is not nerdy)
any of the latest gapps update
and some others
this way if any issue occurs wipe and restore is easy as pie
IMPORTANT: APPS IN THE SYSTEM FOLDERS DO NOT GET WIPED OR DELETED DURING A FACTORY DATA WIPE OR DALVIK WIPE.....THEY CAN ONLY BE FLASHED OVER BY A ROM(OVERWRITTEN)
APPS IN THE DATA FOLDERS WILL GET DELETED DURING A FACTORY WIPE......BUT NOT DALVIK
i know we are ALL have at least one pair of identical (double apks in the system)
-but the identical apks have different names
-on is in data/app the other is in system/app
if you have updated ANY google app then chances are that you may have some double apps on your system wasting. when we update these google apks 'think' the rom comes with the apk already and is stored in the protected system/app folder WHILE the actual update is stored in the data/app folder (or where regular apps go) under a different name
EXAMPLE
google maps
-MAPS.apk ........is stored system/app
-com.google.android.app.map-1.apk........is stored in the data/app (this is the latest update of google maps and should replace the older MAPS.apk in system/app)
-these are the SAME APKs
hmmm so think gmaps is 5-6 megs in size and you have 2 of them so thats like 10-12 megs in your system, get rid of the old one.
there are two thing you can do here with two different benefits
-you can either remove the copy from either the data OR system folders depending on what you prefer.
if you remove the old app from system/app that means easier updates with now file moving BUT less app storage
OR move from data/app to system/app which means less FCs, more other app memory, and dealing with future updates and moving each app.
i like to move the new apks to the system/app where they belong
unstable Launcher PRO
my launcher was very unstable for a while wasn't a big deal for me
soo i decided to move my launcher to the system/app folder like all the other launchers....
I think the instability of that launcher was because of AUTOKILLER thinking this is just a regular app in data/app which it was at the moment. i may be wrong but autokiller doesnt kill system apps. so i move my launcher there and guess what now my launcher is much better and faster and stable beacuse you now have lots more memory.
SPEED TIP: in spare parts speed up your transition and animation windows to FAST
MOVING APPS ADVANCED SHORTCUT
i finally figure out a great short cut for moving apps
-first rename and put your favorite file manager (ROOT EXPLO) onto the sd.
to be even faster rename and put your launcher and TB on there too.
-after flashing a rom bypass the setup (touch the android screen) to home screen.
-open terminal
-type
SU
cd sdcard
busybox install yourapp.apk /data/app
-now you have the file explorer ready to go
instead of trying to restore wipe restore.
and hopefully you know what to do next.
so to summarize...
-get rid of junk you dont use and free up that memory
-move apps to the proper locations in system/app AND/OR data/app
-make sure you dont have multiple google apps using different names
"MAPS.apk" and "com.google.android.app.map-1.apk" IS THE SAME APP IN DIFFERENT LOCATIONS. remove the old and put the new in system/app
make sure your main launcher is in system app so it doesn't keep getting killed by auto killer settings and reloading
Replace THESE apps = with THESE apps
system/app = data/app
Gmail.apk = com.google.android.apps.gm-1.apk
ChrometoPhone.apk = com.google.android.apps.chrometophone-1.apk
Maps.apk = com.google.android.apps.maps-1.apk
CarHomeGoogle.apk = com.google.android.carhome-1.apk
GoogleSearch.apk = com.google.android.googlequicksearchbox-1.apk
Googles.apk = com.google.android.appsunveil-1.apk
SuperUser.apk = com.noshufou.android.su-1.apk
AutoKiller = com.rs.autokiller-2.apk
TitaniumBackup = com.keramidas.TitaniumBackup-2.apk
Twittter = (forget)
Voice= com.google.android.apps.gv-1.apk i think
YouTube=
delete OLD in system/app = move NEW from data/app to system/app
YES i did all those with success more memory and speed and a massive increase in overall Rom stability
there may be more
BUT ALL THESE HAVE DUPLICATE APPS USING DIFFERENT NAMES stored in data/app and/or system/app WHEN the latest update should be system/app IMHO to prevent AUTOKILLER from always killing i believe autokiller will try to kill data apps first before system apps.
i still have my auto killer set at optimum and things work even better now
and i gained 25mb of system memory no more Force closes
Batt tweak custom set up process (a 1-2 day process to complete)
How to increase battery life
first off battery life depends on many factors.....
where you live, work, and the daily place you travel to.
im one of the lucky ones who has a cell tower down the street from me here in S. FL.
WARNING: IF you multitask alllllll day on your phone then this is not for you.This is more beneficial when your phone is at rest or in an idle state or screen off state.
Others may not be so lucky and may live in a bad signal area....which causes your phone to constantly search and listen for signals.
Also battery life could depend on the widgets you use or apps that you have active.
Example: Beautiful Widgets beautiful home is a constantly running app that also
-on occasion activates the GPS to acquire location
-on occasion downloads update weather data
Example: Facebook Widget
-by default update statuses every 15 minutes, so every 15 minutes its downloading data
so i usually adjust these settings to my personal liking
Now for the battery calibration process and how it works
Decad3nce port of Colins_ph batt tweak allows us to use some setcpu profiles without setcpu.
Setcpu and its widgets were resource monsters crippling our system and drain battery life as well. kiss setcpu goodbye we wont be needing it anymore.
the batt tweak calibration process takes some patience as the entire process could take 1-3 days to complete depending. Also i highly recommend using the latest CFS kernel by Conap as it provides extra battery savings
we will be running colins batt tweak during the calibration process so that both calibrate together, which makes a lot of sense as opposed to doning them separately.
here is the process and DS's custom settings for batt tweak 1 (the first release)
please remember to prepare yourself not to interrupt the process. the draining process may die while you are at work or during an emergency. so be prepared to have little use of your phone.
-flash latest CFS kernel found here
-flash batt tweak attached at the bottom of this post until its updated and fixed....more info in thread here
-turn off phone and let charge for a few hours or more to ensure that it is full
-when ready boot into recovery mode and wipe the batt stats and power off
-unplug phone and power on (charging cable not needed) you may experience weird battery levels or fast draining (this is normal)
-immediately open TERMINAL and activate colins_ batt tweak
with command batt-cfg and go to option 3 and input these settings........
I think this works much better
this schedueler keeps the cpu much lower
here if anyone want to try it out
underclock
ondemand
anticipatory
19200
710400
19200
710400
19200
710400 (ONLY IF YOU KNOW YOU CAN 768000)
90
15
15
15
- close terminal and operate phone normally if you want...i highly suggest leaving it alone as much as possible until it drains completely dead.
-use a cpu monitoring app just to make sure the cpu is idle i have seen mine dip down 80mhz if not then you need to kill active open apps
-let phone naturally drain completely until its dead (could take a full day or two mine was 48hrs with some usage)
-when dead make sure by pressing power rapidly a few times
-while off let phone recharge for as long as possible maybe four hours or more the mor the better
-when ready unplug phone and turn on
-when powered on reactivate batt tweak using terminal batt-cfg, then option 9 to save and your done (once setup all you need is option 9 to save and reactivate)
-wtf DS my phone is on but reads less than 100% battery. this is normal replug while on and let charge to full
- when full the process is now complete and you can use phone as normal
REMEMBER THAT SOME ROMS DO NOT ACTIVATE THE TWEAK AND YOU WILL NEED TO DO SO UNTIL YOUR DEV AS ADD THE SCRIPT TO ACTIVATE ON A REBOOT. SO UNTIL THEN OPTION 9 IN BATT TWEAK WILL DO THIS
use an app like system panel or seepu to look at cpu speeds make sure the cpu isnt running at 100%.
try to close apps if you see this but a reboot usually fixes this.
these settings allow for the cpu to use lower clock speeds when idle. much lower than the stock 245000 settings yes were going to the minimum 19200 with little to no side effects or slow downs, but the benefits are more when in a idle state. But it WILL drain at about same rate when your using it heavily.
make sure the tweak is running by either opening terminal and enter pidof batt.sh you should see the processing id number if its running.
OR for a full read out of stats do batt-diag
and observe the time in state read out at the bottom. if you see values next to the 19200 clock speeds........SUCCESS!
PS if you screen on time is 3 hours and your phone is dead, DONT BLAME THE BATT TWEAK....BLAME YOURSELF !
ENJOY
alright now lets get some real stuff in here....lol
jdog94 said:
alright now lets get some real stuff in here....lol
Click to expand...
Click to collapse
just trying to a make a nice neat place to put all my post on past tweaks for users and to do some advanced stuff in the future stay tuned
DS36 said:
just trying to a make a nice neat place to put all my post on past tweaks for users and to do some advanced stuff in the future stay tuned
Click to expand...
Click to collapse
good, i need this!
Great idea"!"!!
HAI! Hau do i route mai fone? I wantz haxorz warez an wireles heatherin fo free intanetz!
So seriously, is this a fan-club for DS? I'm totally in if it is.
sticktodrum said:
HAI! Hau do i route mai fone? I wantz haxorz warez an wireles heatherin fo free intanetz!
So seriously, is this a fan-club for DS? I'm totally in if it is.
Click to expand...
Click to collapse
LMAO can you please please be my threads personal comedian
Keep this thread development related or Ill move it to General, Is this a support thread or something? Something about tweaks?
Its all about me
Captainkrtek said:
Keep this thread development related or Ill move it to General, Is this a support thread or something? Something about tweaks?
Click to expand...
Click to collapse
this is a thread to help old and new users tweak and mod their phones and other advanced stuff
trying to put all the knowledgeable stuff in to one easy thread and it will be dev related
im just started this thread im not done i have lots to do here
my in box is getting a little crazy
this should benefit all and provides basic dev techniques and instruction
this is the beginning stages
plus should reduce the number of faqs for everyone
less fights
less arguments
and less captainrtek (but thats not a bad thing)
DS36 said:
this is a thread to help old and new users tweak and mod their phones and other advanced stuff
trying to put all the knowledgeable stuff in to one easy thread and it will be dev related
im just started this thread im not done i have lots to do here
my in box is getting a little crazy
this should benefit all and provides basic dev techniques and instruction
this is the beginning stages
plus should reduce the number of faqs for everyone
less fights
less arguments
and less captainrtek (but thats not a bad thing)
Click to expand...
Click to collapse
Haha gotcha, and thanks
Thanks in advance, DS.
roirraW "edor" ehT said:
Thanks in advance, DS.
Click to expand...
Click to collapse
Looking forward to working together with everyone learning along the way.
Will be post new batt tweak setting in the morn keep an eye out
Do not up date to the latest version of batt tweak it doesn't work.
Sent from my FroyoEris using XDA App
Brilliant.
sticktodrum said:
HAI! Hau do i route mai fone? I wantz haxorz warez an wireles heatherin fo free intanetz!
So seriously, is this a fan-club for DS? I'm totally in if it is.
Click to expand...
Click to collapse
Lol I haz cheez burger
Sent from my FroyoEris using XDA App
rick311 said:
good, i need this!
Click to expand...
Click to collapse
hey man are you ready
im going to post in the third POST what i have written down so far
but its NOT complete yet....so take a gander
DS36 said:
hey man are you ready
im going to post in the third POST what i have written down so far
but its NOT complete yet....so take a gander
Click to expand...
Click to collapse
ok, i did all the setting tweaks that you recommend. do i have to input them every time i reboot? i dont see a setting that restores my previous settings.
Hey DS,
Great idea to help newbs like me! So after reading your first two posts I looked where my apps are, and every one of them seems to be in system/app... I checked in data/ and can't see anything in there (unless it's sdcard/data, in which case I have folders for Beautiful Widgets and Titanium). I'm using the EStrongs FE, although I don't think that would make a difference. Also, couldn't find any of the duplicate apps you were talking about either (I only have com.google.android.apps.maps.apk, for example). I'm on xtrROM 4.6 and used Titanium Backup to restore my apps.
First off, I cannot take credit for finding this, I was referred to a bug report thread on the Google Android site by XDA user aweaver33, who I thank VERY much for pointing me on the right direction.
So, several of us have had this issue with various custom kernels, where after typically 24-48 hours, the phone would slow to a crawl. If you were to open an app like System Panel, you would see that the CPU load was pegged at 95%+, and speed would be maxed out. You would also see that the process using all the CPU is Android System.
The problem has to do with the file "time_in_state", which literally keeps track of how much time the CPU spends at any given speed in MHz. There is a limit to the size this file is supposed to reach, 256 bytes. Once it exceeds this size, the next time Android tries to access it, it flips out and gets stuck trying, and pegs the CPU. A lot of devs and users blamed SetCPU, and it is true that SetCPU does have an EFFECT on this issue, it does NOT cause it, and indeed the issue can occur whether SetCPU is installed or not.
The issue is brought on by custom kernels that add additional frequency steps for the CPU to choose from, which causes that log file to grow. Which is why older or stock kernels will not cause this. Some ROMS incorporate a workaround so you may not have this issue.
Anyways, the issue is explained better in the link aweaver33 gave me. I will link to the original thread I posted with the conversation we had and the link he gave. I can confirm that, using the info he gave me, the issue has been fixed. I am currently just over 120 hours of uptime with no problems.
Here is the link: http://forum.xda-developers.com/showthread.php?t=1082363&highlight=stock+kernel+gpu+
EDIT: attached the script files for those who want them. You can drop one or the other (NOT BOTH) in /etc/init.d if your rom has this folder already (creating the folder and adding it won't work), or you can download Autostart (root) from the market for free, and drop the file in /data/opt (create the opt folder). This difference between the two is one runs only once at boot, the other runs every five minutes. If you use SetCPU, you need the one that runs every five mins, as every time you open SetCPU it resets permissions on the time_in_state file.
flashable zip? not everyone is comfortable with code and scripts
If I knew how, I would. I wasn't even comfortable with it. But I was so tired of the locking up, I was willing to try anything (after a Nandroid of course). I'm not sure you *could* do this in a flashable zip. I can post the script I'm using. It only runs once after reboot, unlike aweaver's, which runs every five mins (good if you're using SetCPU, as opening SetCPU resets the permissions of the time in state file).
This script should work if dropped into /etc/init.d. *If* your ROM has that folder by default. Mine does not, so I had to download a free app from the market called Autostart which is free and very small. For that app you create a folder in /data/ and drop the script in there.
Sorry guys but I'm no dev so this is the best I can do, maybe someone else can make it flashable?
would it also be fixed by simply deleteing the log file as well rather than setting it to unreadable
It can't be deleted. System instantly replaces it.
bast525 said:
It can't be deleted. System instantly replaces it.
Click to expand...
Click to collapse
:/ i suppose when it is replaced it would be with a fresh one deleting would fix it for 24-48 hours till it got filled again humm i wonder if a script could be auto executed every 12 hours to delete it rather than just make it unreadable.
Do you know if it is a problem in gingerbread as well?
mirrin said:
:/ i suppose when it is replaced it would be with a fresh one deleting would fix it for 24-48 hours till it got filled again humm i wonder if a script could be auto executed every 12 hours to delete it rather than just make it unreadable.
Click to expand...
Click to collapse
I don't think you can delete it. I can't figure out how to.
mirrin said:
Do you know if it is a problem in gingerbread as well?
Click to expand...
Click to collapse
Issue 9733 is still listed as New, so either Google hasn't fixed it in Gingerbread or they just don't bother statusing their bug reports.
Why do you feel the need to delete it? If you are trying to delete it, you are likely using Root Explorer. Why not just use that to change the permissions of the file? Tap and hold, select permissions, and unchecked all permissions except for the top left one. This will stop the bug, but the permissions will be reset after a reboot, or after opening SetCPU.
I imagine that deleting the file might actually cause FC's or may cause the same bug but I dunno since it wont delete.
dyetheskin said:
flashable zip? not everyone is comfortable with code and scripts
Click to expand...
Click to collapse
I've never created a flashable zip before, but I'd be willing to look into it if the demand is really there. The problem I see is that I'd have to make certain assumptions about how everybody's ROMs are configured. It looks like the most portable approach would be to append a line to the end of /bootcomplete.inc.rc. Do people really find it easier to boot into recovery and flash a zip than to add one line to a file themselves? Personally, I'm always hesitant to flash a zip other than a full ROM because I'd be uncertain how it interacts with other changes I've made to my system.
Inc is
not bad
But. 48hours?
Sent overrow from my Optimized Inc using XDA App
ive gathered some things and did a few tests on my MotoActv since ive gotten it and did some tweaks here and there and i added the following features to mine and put them into a flashable zip for u all
-init.d support (plus some scripts to make it faster then ever) (tested and working (makes two files in sdcard on boot to show it) (picks and chooses when to work now for some reason, so i put an app i made that loads scripts when onCreate()'d and sometimes on-boot)
-Viper4Android sound system (only works for bluetooth headsets if enabled, but its sounds better with good settings)(see credits)
-OpenVPN (idk if theres a use for us but i added the required files (no GUI)
-UsbEnabler.apk (see credits)
-Adblock host (hopefully it works i havent been able to test yet)
-lag-free entropy (so far seems to work, as im not lagging switching launchers anymore)
-MotoActv DPI (my own personall app i made for Changing dpi from 90,100, and stock(120)
-Sqlite3 + init.d sqlite3 optimizer
-Busybox Run-parts (for init.d, still picks and chooses when to work)
-100 Dpi When-Flashed (can be changed back to stock with the MotoActv DPI app i made)
-minor-to-major tweaks from init.d scripts and other methods
-DalvikCache2Sd (not sure if it truly tested working, but i do have a tiny bit more space+no lag like other 2SD methods
soon to be added:
I take bare minimum credit for these, i mostly used this personal zip for when i update my MotoActv's rom, this can be universal for other androids, but it was initially made to the MotoActv watch running custom roms
Credits to give:
(will edit when i get forum post urls and OP's names)
Viper4Android:
OP = @zhuhang
Thread = http://forum.xda-developers.com/showthread.php?t=2191223
UsbEnabler:
OP = @fagalto
Thread = http://forum.xda-developers.com/showthread.php?t=2396138
init.d scripts, OpenVpn, Entropy:
i extracted from the rom on my phone so idk where they originally came from
Init.d App(unreleased w/o mod_pack)+MotoActv DPI:
OP:me @jkok for developing and publishing
Thread (MotoActv DPI):
http://forum.xda-developers.com/showthread.php?t=2435370
Gallery+Live Wallapapers:
Google, But @ClearD for giving me the zip with the script+apks
the zip:
i put together, made the script, signed+released for general use for others:
future credits will be made when i add more things.
Download:
Reusable Download Link
Awesome!
Here's a zip (with changed mounting, again; this time using the exact same one that I use for the rom) of the Live Wallpapers + Gallery apks. Hopefully, this one will work fine.
ClearD said:
Awesome!
Here's a zip (with changed mounting, again; this time using the exact same one that I use for the rom) of the Live Wallpapers + Gallery apks. Hopefully, this one will work fine.
Click to expand...
Click to collapse
well thanks ClearD i can do the script just fine, some of the mountpoints are universal like what i use
umount("/system");
or
run_program("xbin/mount", "/system"); (might be wrong on the xbin part, just going by memory
run_program("xbin/umount", "/system");
but the resolution on the galery on your motoactv rom is too big for it, it resizes dont get me wrong, but it needs to do a single horizontal row cause if u overscroll to the farest right u see there is second or more rows going down, imma fine the sourcecode for the galery2.apk, and make a single-row version when i find it =)
jkok said:
well thanks ClearD i can do the script just fine, some of the mountpoints are universal like what i use
umount("/system");
or
run_program("xbin/mount", "/system"); (might be wrong on the xbin part, just going by memory
run_program("xbin/umount", "/system");
but the resolution on the galery on your motoactv rom is too big for it, it resizes dont get me wrong, but it needs to do a single horizontal row cause if u overscroll to the farest right u see there is second or more rows going down, imma fine the sourcecode for the galery2.apk, and make a single-row version when i find it =)
Click to expand...
Click to collapse
Ah, sweet! That sounds good. I couldn't get it to mount properly any other way so far, but it could have been something as simple as a typo. If it does actually work, then I might use that in the future. That's the one I tried with the last iteration.
ClearD said:
Ah, sweet! That sounds good. I couldn't get it to mount properly any other way so far, but it could have been something as simple as a typo. If it does actually work, then I might use that in the future.
Click to expand...
Click to collapse
the universal way i do my scripts is
mount("ext3", "MTD", "system", "/system");
unmount("/system");
and it always seemed to work for me, so thats why i call it universal anyways
but the other ways i posted seemed to work for me when i tried em, i just used this way cause it was in a zip for a motoactv rom (i think it was yours or the battery mod)
Opps! i was wrong, its not
run_program("xbin/mount", "system");
its
run_program("sbin/mount", "system");
lol i had to check my other mod zips lol
jkok said:
the universal way i do my scripts is
mount("ext3", "MTD", "system", "/system");
unmount("/system");
and it always seemed to work for me, so thats why i call it universal anyways
but the other ways i posted seemed to work for me when i tried em, i just used this way cause it was in a zip for a motoactv rom (i think it was yours or the battery mod)
Click to expand...
Click to collapse
Lol no doubt, I went through the same thing with the battery mod, looking over and over for one that worked better. I'd prefer the xbin/mount method, but for some reason, it was hit and miss on my end with end users. Not sure why, unless busybox wasn't set up right somehow.
Just updated the mod_pack with more features!
Sorry but the only thing i havent really been able to fix that well way the init.d it seemed to workwhen i first released this mod_pack, but it seems to pick+choose when to work, so i added 2 other methods for init.d (one of which is an app i made, yet to release that loads the scripts when the app is onCreate()'d and sometimes on-boot when SuperUser allows it)
but there are some great new features that WILL work, along with some of my own personall apps, tweaks, and clock faces =)
Again: this mod_pack is meant for MotoActv's running a custom rom, and Not meant for AOSP based MotoActv Roms
Tested and confirmed working (except init.d that picks and chooses) on @ClearD 's ClearRom 1.2.0 T2 (and my own personal (un)Official 1.2.1 T1 i made for him)
For some reason all of the mods are being denied superuser, any ideas? I am setup to automatically allow all requests
Edit: Installed SuperSU and my problem has been resolved
Has there been anything definitive about the entropy thing? The last consensus I saw by anyone not potentially making money from a fix is that at best it's just forcing the processor to stay awake, decreasing battery life.
Saeviomage said:
Has there been anything definitive about the entropy thing? The last consensus I saw by anyone not potentially making money from a fix is that at best it's just forcing the processor to stay awake, decreasing battery life.
Click to expand...
Click to collapse
well by my testing before my motoactv went kaput it didnt affect the battery any noticeable amount, but it did solve some-to-all of the lag from switching launchers on the ClearDroid 1.2.0_T2 rom, i cannot make or update this mod-pack anymore because i dont like submitting a mod-pack that is untested, and since my motoactv went kaput i cannot test it anymore but if u have any questions feel free to ask and ill try to answer the best i can for now =)
not sure what is the right place to ask this... How does DPI change work? Does it mean the "system" screen resolution is changed? Let say, what is the "Full Screen" resolutions in 90/100/stock(120?) dpi's??? Where to read about it if it is not so simple???
yuiop0 said:
not sure what is the right place to ask this... How does DPI change work? Does it mean the "system" screen resolution is changed? Let say, what is the "Full Screen" resolutions in 90/100/stock(120?) dpi's??? Where to read about it if it is not so simple???
Click to expand...
Click to collapse
Dont worry its ok to ask here, since i made this app after all , i might as well answer how this works =)
well to make it shorter and more understandable to alot more people:
Yes, it is the overall resolution of the screen:
DPI (dots-per-inch) is more like the size range to view images/displays/graphics on ANY of your LCD/LED Screened devices including androids, I-craps(iPhones/ipods )(sorry i dont like apple too much, bad excperiences, dont get offended if u like it as its just my personal preferences), blackberries, windows phones, TV's, computer Monitors, etc:
the stock setting for HDPI phones (the more common screened ones now) is 240, say if u lower it, the images get smaller, if u raise it it gets bigger (maybe even too big for the screen to handle correctly);
but since the MOTOACTV has a smaller screen as u can obviously see (if u have one that is, as i dont know others posesions =P), its default for the stock rom is 120 (1/2 of HDPI if u notice the math) and 120 is as big as it should go cause say for example 130 dpi, it makes the images slightly too big for the screen, but slightly smaller values (100 is usually smallest for alot of peoples eyes for the watch, but for some people like me that like them a tad smaller for sharp small details, i put 90), but literally the smaller the amounts go, the smaller the images(and possible errors, i.e ES File Explorer crashes below 120 DPI untill u restore to 120+) , and for the smaller screen we have u cant go too big (121+), or too small (>=90-100), so i put those details of 90,100,and 120 (no 110 as it doesnt make too much of a difference by what i saw)
but there is (a) way(s) to check what DPI u are at currently:
METHOD1.check your build.prop file under /system/build.prop by doin these ADB commands (**new line is a new command**) (commands stop at <EOC>)
adb remount
adb pull /system/build.prop
<EOC>
check somewhere using notepad for this line (NOTE: if u want to edit to push to your device use notepad++, search for it on google if u dont already have it, as regular notepad corrupts it)
ro.sf.lcd_density=(your current DPI is displayed here)
if u decide to change it that way and want to apply it MAKE A BACKUP!!!, then change it in notepad++ and save it, then goto the directory it is in in the terminal/command prompt and do (**new line is a new command**) (commands stop at <EOC>)
adb remount
adb push build.prop /system/build.prop
adb shell chmod 644 /system/app/build.prop
adb reboot
<EOC>
METHOD 2: Any DPI Checking/changer app (there might be some good free ones, i.e. pimpmyrom has a density changer (DPI changer) that works the same as mine i think, it changes the DPI value in the Build.prop and it WILL stick over reboots, just not rom flashes (as it overwrites it and my change)
if u want to see how i did this(if u understand java/android applications) u can check This app on my github, its acually fairly easy and lightweight compared to others
https://github.com/kittleapps/MotoActvDPI
and the exact class that does this (using a library), is this
https://github.com/kittleapps/MotoA...om/KittleApps/app/motoactvdpi/MainScreen.java
as u can see it changes it to 90,100, and 120 quite simply (with root access of course)
and sorry for this long message but it explains not only your question, but possible future questions on how this app works =)
jkok said:
but there is (a) way(s) to check what DPI u are at currently:
METHOD1.check your build.prop file under /system/build.prop by doin these ADB commands (**new line is a new command**) (commands stop at <EOC>)
adb remount
adb pull /system/build.prop
<EOC>
check somewhere using notepad for this line (NOTE: if u want to edit to push to your device use notepad++, search for it on google if u dont already have it, as regular notepad corrupts it)
ro.sf.lcd_density=(your current DPI is displayed here)
if u decide to change it that way and want to apply it MAKE A BACKUP!!!, then change it in notepad++ and save it, then goto the directory it is in in the terminal/command prompt and do (**new line is a new command**) (commands stop at <EOC>)
adb remount
adb push build.prop /system/build.prop
adb shell chmod 644 /system/app/build.prop
adb reboot
<EOC>
METHOD 2: Any DPI Checking/changer app (there might be some good free ones, i.e. pimpmyrom has a density changer (DPI changer) that works the same as mine i think, it changes the DPI value in the Build.prop and it WILL stick over reboots, just not rom flashes (as it overwrites it and my change)
if u want to see how i did this(if u understand java/android applications) u can check This app on my github, its acually fairly easy and lightweight compared to others
https://github.com/kittleapps/MotoActvDPI
and the exact class that does this (using a library), is this
https://github.com/kittleapps/MotoA...om/KittleApps/app/motoactvdpi/MainScreen.java
as u can see it changes it to 90,100, and 120 quite simply (with root access of course)
and sorry for this long message but it explains not only your question, but possible future questions on how this app works =)
Click to expand...
Click to collapse
There is a 3rd method as well.
Method 3 = Install the Xposed framework and app settings apk found here: http://forum.xda-developers.com/showpost.php?p=44034334&postcount=2315
This will allow per app DPI settings rather than one global setting.
In order for this to work correctly, make sure you move both the Xposed Installer and App Settings apks to the phone after installation and reboot as well.
I like running some apps at 120, others at 100, 90, and even 70 w/ modded font sizes and this allows for all those combinations.
Artimis said:
There is a 3rd method as well.
Method 3 = Install the Xposed framework and app settings apk found here: http://forum.xda-developers.com/showpost.php?p=44034334&postcount=2315
This will allow per app DPI settings rather than one global setting.
In order for this to work correctly, make sure you move both the Xposed Installer and App Settings apks to the phone after installation and reboot as well.
I like running some apps at 120, others at 100, 90, and even 70 w/ modded font sizes and this allows for all those combinations.
Click to expand...
Click to collapse
that is true, but i didnt include that cause i was seeing people having issues with xposed-framework on the MOTOACTV on a few threads, and tbh i made this app+inlcuded in modpack before that method was usable for MOTOACTV (or gingerbread in general), thats kinda why i havent updated the modpack in a while (including the fact mine is damaged for some time now), i managed to fix mine up somewhat but it only turns on the backlight and no button combos work but to turn on backlight XD, so no fastboot recovery, boot-to-system, or quickboot :S and since the device is discontinued i cant get a real fix XD, so unless i personally test the things i put in this modpack, i cant make new versions to distribute for device stability reasons (e.g. in case it is corrupted and breaks someone elses device, as it is un-tested, since i dont have a device to test it on)
jkok said:
that is true, but i didnt include that cause i was seeing people having issues with xposed-framework on the MOTOACTV on a few threads, and tbh i made this app+inlcuded in modpack before that method was usable for MOTOACTV (or gingerbread in general), thats kinda why i havent updated the modpack in a while (including the fact mine is damaged for some time now), i managed to fix mine up somewhat but it only turns on the backlight and no button combos work but to turn on backlight XD, so no fastboot recovery, boot-to-system, or quickboot :S and since the device is discontinued i cant get a real fix XD, so unless i personally test the things i put in this modpack, i cant make new versions to distribute for device stability reasons (e.g. in case it is corrupted and breaks someone elses device, as it is un-tested, since i dont have a device to test it on)
Click to expand...
Click to collapse
Sorry to hear that. I personally haven't loaded the mod pack yet. Was looking into cherry picking parts of it when I saw the question on DPI. I thought it was a general question.
In any case, I personally have not had any issues with Xposed on my actv. What issues have you heard about?
jkok - thank you so much for the explanations. It's become more clear for me but I'm not so experienced in android/development so I have some more questions related to dpi on actv.
My practical interest in this is - to investigate the possibility to run igo primo on this device (for route planning/voice navigation) because I'm not happy with Motorola map application (walk/run outdoor mode). I have some ideas how to modify igo's data.zip for specific screen resolutions (at least I managed to make "custom 640x480" data.zip for primo 2.4.0 WM for htc DIAM100) but I need to know what is the "Full Screen" resoluton (for igo and other applications) in different dpi modes on actv (ClearD 1.2.0 rom currently, just in case). Is it the same - 176x220 for all dpi's (I don't think so as the size of icons/fonts/etc are different). So, the real question is - what is the screen resolution I need to set up in data.zip to try to run igo primo on motoactv. To know that I need to understand if dpi change affects the "full screen resolution" in motoactv/android. And, once more, sorry if the question looks stupid (already explained etc) as I'm not developer...
yuiop0 said:
jkok - thank you so much for the explanations. It's become more clear for me but I'm not so experienced in android/development so I have some more questions related to dpi on actv.
My practical interest in this is - to investigate the possibility to run igo primo on this device (for route planning/voice navigation) because I'm not happy with Motorola map application (walk/run outdoor mode). I have some ideas how to modify igo's data.zip for specific screen resolutions (at least I managed to make "custom 640x480" data.zip for primo 2.4.0 WM for htc DIAM100) but I need to know what is the "Full Screen" resoluton (for igo and other applications) in different dpi modes on actv (ClearD 1.2.0 rom currently, just in case). Is it the same - 176x220 for all dpi's (I don't think so as the size of icons/fonts/etc are different). So, the real question is - what is the screen resolution I need to set up in data.zip to try to run igo primo on motoactv. To know that I need to understand if dpi change affects the "full screen resolution" in motoactv/android. And, once more, sorry if the question looks stupid (already explained etc) as I'm not developer...
Click to expand...
Click to collapse
well im not familiar with those apps, as for the resolutions/dpi im not sure of that :S it could possible be found on google, as basic hdpi (240 dpi), usually is around 480*800, and 120 dpi is like the motoactv 220*176, so i guess there isnt a ratio it follows, just sizing of images maybee :S, but i also just became a developer more resently withing the last 2 years so im still learning
So, i have a G6 with a lot of "mods" like kernel, root, etc...
one thing i still miss is the editing of thermal-engine-8996.conf like i used to do with other phones, messing a little to put the phone at my taste and limit some frequency's to save battery life.
BUT, this phone is different since my V10 can open the file and i can see the content of it with G6 the file seems to be encrypted because when i open it there's some characters random all across the file i cannot understand nothing.
i try open it with some apps like Ultra Editor, Notepad++ but NONE works so, im here to ask if some developer or programer or so can give me a tip to kind of open this file as they should be without that messing characters??!
Thanks in advice...
I'd also like to know this