Related
I just flashed the 1.6 ROM from here:
http://forum.xda-developers.com/showthread.php?t=565929
And have listed the first part of this post in that thread, but I was interested in getting some answers to the second part of this post (I thought it might be relevant to re-post the first part here, just for reference).
My issues with this ROM (I have a rooted MT3G):
- Can't seem to get Touch Input (HTC_IME) working, and just waiting on someone to post a link to a working apk & files (with instructions). The versions I have will install, but causes a force close. TouchPal (an old favorite from my Windows Mobild days) installs and works fine, but isn't that much better than the stock keyboard (although for the 20-key qwerty keyboard, it's better than the stock in that way).
- I get a force close when I go to edit a contact
- I get a force close when trying to use the PhoneBook app (as a contacts alternative)
- Not sure if this is related to this ROM, but I get a force close with Snap Photo Pro when trying to take a photo. It wasn't really usable on Hero ROM's so I hadn't played with it much, so not sure about this one. The non-pro version is fine (and really is sufficient for my needs).
- Installed apps do not show up in AppManager (even if installed with AppManager). They also don't show up in aTrackDog. But they do appear in GPhoneManager and Advanced Task Manager.
- Get the "Problems loading widget" for the calendar widget, but I never use that so no worries for me. Power Control does not seem to give me any issues.
Also, for those that are having trouble using Wireless Tether For Root Users, I got aNetShare working fine - well, at least it runs, doesn't give any errors, but I can't seem to get internet access with my PC yet. I don't recall what ROM I had pulled it from now.
Overall, I think this is a nice and speedy ROM and would use it, but still prefer some of the "core" things found in Hero ROM's, which include:
- The photo/gallery browser. I'm not sure how to block directories of images in the ROM like I do with the ".nomedia" fix used with the Hero photo viewer). Interestingly, the ".nomedia" fix seems to work fine with the Music Player. If there's a good photo viewer in the market (or a "simple" way to block directories), I'd appreciate someone pointing it out.
- I like the contacts program in Hero ROM's, specifically the ability to sync with Facebook.
- Would be nice to take pictures in portrait mode, but not a major thing (I mean, I can take them, but then they'll get rotated wrong when viewing photos).
- The look and feel of the Hero Calendar is nicer, and I haven't really checked any of the available calendars from the market, so not sure if there's a decent alternative to the stock one.
- Multi touch. Not something I use often due to general lag, but would be nice to use on a zippy stock ROM. I mean device-wide, not just for the browser (like for images).
Everything else that is "nicer" in a Hero ROM, I can find alternatives for (like using Handcent for SMS, or Lock 2.0 for a "slide to unlock" thing, etc). I don't need Rosie (and can always get a home alternative if I wanted more than 3 screens) or TouchFlo - unless, of course, that's what the above apps are tied to.
And finally, what might be nice is a list of core apps that can be removed without affecting the system.
Edit: Volume Stepping Mod fixed! More Mods Added!! See second post for new Mods.
Hello, my name is Doc....and I am a recovering lurker!
First post ever here! (Would that be Step 2 or 3 in the recovery program???)
Anyhow, I have been lurking around XDA for quite some time now, mostly just absorbing A LOT of fantastic information, and although it is not much I thought it was time I shared back!
Please keep in mind, that I can offer no promise of support. (These are mods I did for myself and figured others may appreciate them.) The main reason I have never participated here before is time, as in I don't have much of it! (Single Dad, 2 jobs, and all that jazz) I will do my best to help out (and keep contributing), but there will often be periods of time where I simply will not be around to respond. I am not trying to be an ass, just honest and up front. If there are any issues with what I share, I don't want people getting angry because the OP wasn't around to fix his stuff!
I have been using these for a few weeks now and have had no real problems, so I am fairly confident that they should work for the rest of you. Once I reach my 10 post limit I will move these into the Development section since it seems that very few people even vist these other areas anymore. I will also post links to the original threads where I got the mods.
If any of these have already been done for our phones please let me know. And of course, if anyone knows of a better way, or has any ideas, please do share!
Link to downloads are at bottom of post.
Remember, these are for STOCK FROYO!
NANDROID, NANDROID, NANDROID!!!
Remap Faves button to Settings (Rosie.apk) -(Thanks/Credit to the1wingedangel)-
I know there are quite a few of these already out there, but have not seen one made to go into Settings. I find I use it quite often and it has been very convenient for me. Hopefully someone else may find it usefull as well.
Smooth Spinners (Framework-res.apk) -(Thanks/Credit to D.O.C)-
This is simple eye-candy, but I like it a lot! It does what it implies...Smooths out the rotation of the spinning circles displayed while loading.
(NOTE: This mod is in Framework-res.apk, so if you are themed, you may not want to flash this) (I will post the modded smali files later on so you can do a simple copy paste and keep your themes intact)
Volume Stepping Increase and Smooth Scroll (Framework.jar) -(Thanks/Credit to AndroidON)-
The Smooth Scroll portion of this will disable ScrollingCache for the whole system. Apparently it was not implemented as well as it should have been and I find my Slide really likes having it disabled. (i.e. Under Settings > Applications > Manage Apps - when scrolling through the list of apps, it is very very smooth! No more skipping or hesitating!)
The volume portion will not increase the max volume of your Slide, but will allow finer control over the volume. It changes:
Media, Bluetooth and TTS from 15 to 30 volume steps;
Ringtone from 7 to 15 volume steps;
Voice Call from 5 to 10 volume steps. (I am uncertain what this changed, as in-call and speakerphone volume remains unchanged. I assume this may be overridden by another setting or it is not applicable to the custom ROM I am using. If anyone knows more about this, please share your knowledge!)
Download: min.us/mEspresso < copy/paste in browser
Thanks to everyone here at XDA!
ENJOY!
Extended Power Menu - All In One Zip - Decompiled files for Framework-res.apk
Here are a couple of more Mods...
All mods are flashable through CWM.
Extended Power Menu (Reboot) (android.policy.jar and com.htc.resources.apk) -(Thanks/Credit to ca1ne)-
My personal fave! This will add an extended power menu...Long press the power button and you will see an extra option, Reboot! Select this and you will get a second menu to choose the type of reboot. Choose from Normal, Hot Restart, Bootloader, or Recovery.
I do plan on uploading one without the htc.resources.apk for those that have already modded this file. The only reason it is included is for the Reboot icon. I made this icon for myself, but it is possible to default it to the generic Settings Gear icon you may have seen on similar mods, which would remove the need for including the extra file.
AllMods.zip - This is all of the mods I have listed so far, in one flashable file.
In my download folder, you will notice a few other items:
SmoothSpinnersMod_Themed.zip and AllMods_Themed.zip - These are the exact same mods, only the framework-res.apk is the one I personally use. (Others provided have not been themed). It isn't much, but I used UOT (Thanks to them of course!!) to spice up my Status Bar a little. Replaced many of the white status icons with prettier colored ones, changed the stock spinner to a Radar spinner, and included the Circle Battery with %.
I had it, so I figured I'd share it!
SmoothSpinners Files.zip - If your framework-res is already modded/themed, this is for you. Unzip the files, decompile your framework-res and copy/paste the files from my zip to: framework-res.apk/res/drawable/ Recompile. Thats it.
I know these are fairly minor mods, but I wanted to put them out there anyway in case someone is interested. I do hope someone finds some good use in these.
There are a few other mods I have attempted, but could not get to work on Froyo. I will likely be making the move to SalsaSlide sometime this week. (Finally, right??) Anyway, I plan to bring all of these over to GB as well as a few others I have been working on, so stay tuned!
Downloads: min.us/mEspresso < copy/paste in browser.
I know that these are for Froyo, which is probably not being used by very many people here anymore, but I am curious if anyone has even tried any of them and if so what did you think?
Sent from my custom MT3gS
Wow! It seems I am a bit more behind the times than I realized! I guess it is time to move on, eh? Ah well, Gingerbread here I come!
DocHoliday77 said:
Wow! It seems I am a bit more behind the times than I realized! I guess it is time to move on, eh? Ah well, Gingerbread here I come!
Click to expand...
Click to collapse
Don't be so quick, I end up coming back to my favorite froyo rom because things just work. I loved your reboot mod. I have a request, I have seen other froyo phones with power control widgets on the notification, do you think that's possible on sense?
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
Modifications for stock 4.4.2
drakeheart77 said:
Modifications for stock 4.4.2
Click to expand...
Click to collapse
I have found that custom ROMS/Kernels and much else for this phone to be sorely lacking. This is by no means an attack on my respected dev peers, simply an observation.
Throughout the woes of our limited forums I see a trend in the gripes about this little wonder.
I am offering my personal settings & preferences that MAY unleash what we can do here.
FIRST THINGS FIRST- Just forget needing buggy builds of TWRP for KK+ rom flashing. There's not much to flash, and TWRP 2.7.1.0 forced me to dl the KK stock firmware & start from square zero.
*NOTE FOR REASONS STILL UNKNOWN EVERY SINGLE PARTITION WOULD RESTORE- EXCEPT THE SYSTEM.
Enough said.
I am using CWM 6.0.2 for stability reasons, and have no issues.
Now I will begin the good stuff.
After my mods/tweaks etc, I am running about 97 apps with 3.9GB internal memory remaining, can go about 11hrs without needing to charge, give or take, and can multitask seemlessly with around 410mb free RAM at stationary.
Obviously, one needs to utilise the KK SD card fix. After this, begin:
Install /system/app/mover from Play Store & BE CAREFUL!!
I proceeded to begin moving bloatware preinstalled apps from being system apps to User apps, freeing essential system rom space & allowing for safe uninstall and transfer to ext sd.
Now on to build.prop.
Unleash what we can do here.
Here is the link to my build.prop zip. Please note all mods & adds specifically, as they are unique to the likings of this phone.
https://docs.google.com/file/d/0B-a-fg6mIteHakZfYXk1eklla3M/edit?usp=docslist_api
Next, I HIGHLY suggest the Override DNS for KitKat. Only one that works for 4.4 & above. Set to Google, which is also feasable in bud.prop, but my experience has been iffy with that, and this app flushes DNS cache w/o reboot and sets DNS KitKat specific.
GPS- FasterGPS.
Here is the link to the Advanced Settings data after basic configuration. The results speak for themselves.
https://docs.google.com/file/d/0B-a-fg6mIteHellndldvUG5Eb1k/edit?usp=docslist_api
Dl and rename to .txt to view.
I use RAM Manager Pro for memcleaning & management.
Use default option, the select custom afterwards to fine tune settings to preference.
If ANYONE needs recovery files for any soft brick needs AND has CWM, please PM me & I will upload mine.
Hope this gives some insight on how to begin using this guy properly.
Open forum. Ask/request away, add to it please!
Screenshots
RAM Manager Pro Custom settings that I use:
NOTE: Notice custom launcher in screenshots- by using /system/app/mover to convert Touchwiz to user, I freed up substantial rom space, mem, and performance. I use Apex Pro.
App Tools
Link to some utilities
Dl, unzip, rest is easy to figure out.
https://docs.google.com/file/d/0B-a-fg6mIteHeXowU1hTakRrZTA/edit?usp=docslist_api
I've begun modding my stock sgh t399 and I was wondering if u could talk with me a lil. I've seen massive potential over cost n this phone. Mainly don't understand build prop yet. Don't wanna brick it
Sent from my SGH-T399N using xda Forum
drakeheart77 said:
Screenshots
RAM Manager Pro Custom settings that I use:
NOTE: Notice custom launcher in screenshots- by using /system/app/mover to convert Touchwiz to user, I freed up substantial rom space, mem, and performance. I use Apex Pro.
Click to expand...
Click to collapse
You guys are in luck. .. the gods had pity and sent someone to steal my galaxy s3 and 5 and Tablet 7.0... so, I ended up with this phone. . But there's little to no development, especially for the metro variant. .. sooo... I'm doing a little work. ... look up .. team rejects.... you'll understand soon. ..good things coming. .
timmetal6669 said:
You guys are in luck. .. the gods had pity and sent someone to steal my galaxy s3 and 5 and Tablet 7.0... so, I ended up with this phone. . But there's little to no development, especially for the metro variant. .. sooo... I'm doing a little work. ... look up .. team rejects.... you'll understand soon. ..good things coming. .
Click to expand...
Click to collapse
Unjustified Dev is working on CM12 for this phone, but he's pretty much the only one. Whether you team up with him or you work independently, it'll certainly be good to have more people working on this phone. Bummer you had to lose your other devices though.
A different route
Hey all, thanx for the attention & activity in getting this thread moving.
I readily & always tell all I am not a Dev, I assist true devs here & there to work towards
stables, patches, fixing kernels, and so on.
That's out of the way, now on to the progress.
I have been using an AOSP deodexed stock 4.4.2 ROM, and praises to the efforts of
the community member, and much to my discredit I can't readily recall who this person
is to post a link to that thread, as is proper. oh well.
While the AOSP stock build is a big showing of progress, I say with a heavy heart that
it is very, very buggy.
What the positive effort was: It is debloated to such a level that upon a fresh install,
the user still has 4.2GB Internal Storage.
This, I've found, is the single most common misdirected goal and focus of efforts with
throw-away-yet-kinda-quality nocontract phone.
After I installed TB Premium, I discovered that the system ROM had around 182Mb available.
I now come to reports.
Every Stock 4.4.2 system app was still there, however the writer replaced a few (ie Camera
with Google Camera, for one) that completely eat up what precious limited RAM/
ROM performance we do have.
The build.prop showed only a few mods/edits, less than five.
The dalvik.vm.heapsize was 128m, heapstart was 8m, and growth limit 256mb.
That was same as stock. Speaking only for me, that was the biggest oversight that
tainted almost all efforts. Those sizes are entirely TOO big for this phone's britches.
If I seem like I just will not stfu, I can't blame you.
I feel I have to be as thorough as possible out of respect for my colleagues.
Now, since I am using Chrome from my device for all of this, you all will find up look oads
and images following this reply, fyi.
My first inspection was to install SetCPU, in small hopes that a customized kernel
had magically came. I am BEGGING for more governors and I/O schedulers, our less-than-
primitive 5/3 is downright insulting.
Kernel supports absolutely no tweaks, VM swap, O/C or min freq. U/C.
My goal is to take the only alternative given on 4.4.2 at all, and make lemonade.
System/app mover from Play Store.
There are countless threads on what is & isn't safe, my mods on that are my prefs.
In the end, I was able to free ROM up to just over 406MB. I can't begin to describe
the difference.
On to build.prop
To compliment my new device I just got, I set dalvik.vm sizes to a less audacious level.
I chose the more conservative of 8m, 64m, 128m. *Note any less on any 3 values, your FCs
will never cease.
Next, I made a few other edits I've favored on several devices, will upload my .txt.
Use of SD Fix for KitKat, along with Force2SD paid, I have 104 apps, many being very large
games, as well as the evil Chrome and FB storage rapists, all Google offenders at that.
I have a smug 4.32 GB Internal Storage available, saving me much embarassment by killing all my ROM wins.
AdAway 2.9 for KitKat, Override DNS for Root Users, the ONLY DNS mod that works on
KitKat, FasterGPS, Seeder 2.0, Root Explorer paid, TB Pro, NG Cache Cleaner, SignalGuardPro
and SD Booster make up my arsenal.
Touchwiz & Trebuchet are gone, I use Nova Launcher Premium.
Restoring TB app backups from external SD put my phone into bootloop.
I am clueless as to any reason why.
Using ANY root sysApp delete to debloat will also softbrick.
System/App Mover seems to be the only way. I speak from a few experiences and Nandroid
system part. restores.
I COMPLETELY CONDEMN MY PRIOR CONVICTION TO CWM.
I completely f*"$ed that up.
TWRP 2.8.0
NOTHING ELSE.
I even attempted a rash Aroma Installer to compensate for MusicFX being gone.
Ac!D Sound Mod.
Worked. And Improved.
RAM Manager Pro is gone too. I've found my build.prop edits are just right.
Any app tweak mucks it up.
Battery Callibrate Root, free on Store. Another win on battery life.
This is the most I can really do now.
Without a custom kernel, we'll be left behind like nearly all Prepaids, non flagships.
That's MY report, I beg for input/feedback/comments/criticism/ridicule, whatever.
Next Replies will be build.prop.txt, gps.conf, screenshots.
Follow up links scrnshots
My modded gps.conf, using FasterGPS
https://docs.google.com/file/d/0B-a-fg6mIteHellndldvUG5Eb1k/edit?usp=docslist_api
My build.prop txt
https://docs.google.com/file/d/0B-a-fg6mIteHWEd1U2pFNUJ5emc/edit?usp=docslist_api
some srcnshots are attached as well.
Plz PM or Reply if I can provide anything else.
DISREGARD BUILD.PROP UPLOAD FROM PREVIOUS.
I missed some critical errors & edits that will negatively impact the phones performance and memory allocation, dang my bad all!
I've been at this phone non stop it seems since my previous post. Need to be less trigger-happy with reporting progress smh.
I'm uploading what I promise is my finished build.prop, for real this time.
Since I am sticking with this stock AOSP build, I was able to successfully flash an Aroma recovery installer mod, the Ac!d Sound Engine.
I should note that the only EQ offered that will work is Nooxide. Awesome Beats EQ is not designed for 4.4 platform.
The Ac!d enhancement and Dolby Mod both have made positive enhancements.
The Play Store that is built in to the .zip install MUST be replaced. Initially the writer included that Play Store will FC upon install, but clearing cache/data in app manager would fix, and was correct.
I can't assume that I'm the only one who has caught this, but I am reposting in writer's thread that Play Store will update to 5.4 build, and it becomes all but unusable.
Any Play Store update beyond 5.2... has never functioned properly for me, it seems Google is making a path for Lollipop migration, and the Play Store versions 5.3 and above are, I believe, geared for 5.0 platform, but still giving it to 4.4 users.
I downloaded a Play Store 5.2 apk from a third party site, saved to my external.
What I now believe is the present solution to this situation is this;
Get 5.2.** apk, keep it on External, or readily available.
Get System/app mover
Root Explorer
After flashing, use System/app mover, and convert Play Store from system to user app.
Reboot. Uninstall Play Store as regular user app. Install 5.2.** apk. open System/app mover & convert Play Store to system app. Hit "cancel" on reboot prompt in app. Go to app manager, Google Play Services, clear cache and ALL data under "Manage Storage". Then reboot.
This has fixed, for good, my issues.
As stated before, use System/app mover at your own discretion and what is your preference, just make a backup first and understand what you are doing.
I am satisfied with what I've worked out, and do not have any other work to do that I can see.
Thanks all.
Next reply is RIGHT build.prop
apologies again.
Drakeheart77
https://docs.google.com/file/d/0B-a-fg6mIteHU081Uko0MU9ENms/edit?usp=docslist_api
Update- have recently corrected setting dalvik heapsize and limit to lower settings, causes many MANY problems, fc's etc.
Set to 8m, 64m, 256m.
Absolutely primed.
Further system mods gave me 433Mb free ROM space, and around 4.1Gb internal storage free.
Happy thus far.
If anyone is keeping up on CM12 build, share to this forum please.
I wish to aid the dev in any way possible.
drakeheart77 said:
Update- have recently corrected setting dalvik heapsize and limit to lower settings, causes many MANY problems, fc's etc.
Set to 8m, 64m, 256m.
Absolutely primed.
Further system mods gave me 433Mb free ROM space, and around 4.1Gb internal storage free.
Happy thus far.
If anyone is keeping up on CM12 build, share to this forum please.
I wish to aid the dev in any way possible.
Click to expand...
Click to collapse
I am using the CM12 build and its pretty good. If you havent tried it yourself you should its pretty stable. I do like to see that you are working on the stock rom though. I like that one too just too much bloatware and not enough free space, so this is good!
I've tried keeping tabs on that here & there, can't seem to find dl link for latest/stable build. I've given up on this stock ASOP, just flashed back to stock 4.4.2. Added all those mods I've been posting, runs 110% better.
Would you be so kind as to point me the right way to dl this CM12? I'm looking again, but it would help a lot lol.
Ty for your participation.
drakeheart77 said:
I've tried keeping tabs on that here & there, can't seem to find dl link for latest/stable build. I've given up on this stock ASOP, just flashed back to stock 4.4.2. Added all those mods I've been posting, runs 110% better.
Would you be so kind as to point me the right way to dl this CM12? I'm looking again, but it would help a lot lol.
Ty for your participation.
Click to expand...
Click to collapse
Here's a link to the cm12 development thread http://forum.xda-developers.com/android/development/dev-cyanogenmod-porting-t2918432
And here's the link to unjustified dev's samsung galaxy light folder that has the latest cm12 build http://forum.xda-developers.com/android/development/dev-cyanogenmod-porting-t2918432
Thanks
Ty I actually found it shortly after I requested that from you.
Been running it since then, a LOT of trial-and-error runs, but I've
managed to get it running just right for me, almost...
Fixed constant soft reboots by setting location to device only
Have no issues at all with phone calls, only the persistent
proximity during a call, I must position my phone a certain way,
my cheek kept touching the speaker and mute icons.
Any advice on that is welcome, I've tried the build.prop edit:
ro.lge.proximity. delay=25
mot.proximity.delay=25
without much luck lol.
And, the MMS issue. I'm on MetroPCS, so I have set the default
APN accordingly.
After researching CM Mod forums & searches, the only
solution anyone has ever provided is to use third-party SMS,
Textra was the specific example.
It seems to be arbitrary, I've had continuous successful deliveries,
then shortly after they fail every time..rebooting has AND has
not fixed this...too random of success/failures to pinpoint myself,
but I by no means am a master at this ☺.
Any help or ideas are most welcome!
Did you clean install? I set my APN to metro fast or whatever its called and have had no problems with texting. The only issues I have other than the proximity that you mentioned, is that videos don't always play. Plus the newest Netflix doesn't work and neither does play TV and movies. Both force close when I try to open
Sent from my SGH-T399N using XDA Free mobile app
Yeah when I had cm12 installed I had no problems with mms after changing the apn to metropcs lte or whatever it's called.
Well, I've since returned to Stock KitKat w/ root & modifications. The Cm12 was nifty at first, but in the end I desire functionality over custom.
Too many apps/features that I want & use often just didn't work unfortunately. Oh well, I'm still willing to pitch in & help out devs!
Maybe you could help develop the cm12 rom. Unjust lent his galaxy light out, and idk if he got it back yet
Sent from my SGH-T399N using XDA Free mobile app
Hi all!
As many of you have noticed, the multitasking on Stock ROMs is not that great, especially if you are coming from some custom ROMs like CM, etc. The thing is that if you want to recall an app that was closed 5 minutes ago, it has to be started again. To change this it's very easy by editing the build.prop file.
Requirements:
- Stock ROM or stock based, maybe others but I doubt that this isn't included within
- Root
- File manager/ Root explorer with text editor
Instructions:
1. Navigate to /system, find the build.prop file and copy it to /data (just as a backup).
<<Later on if you will face any bootloop/troubles, restart the phone in TWRP, go to file manager and simply copy the original build.prop from /data to /system and overwrite it.>>
2. Open the build.prop in /system with a text editor and at the bottom, add the following lines:
sys.config.spcm_enable=false
ro.config.fha_enable=true
3. Save your modifications to the file and before restarting, check the permissions again to be correct (rw-r--r--).
4. Reboot.
That's it. Enjoy and report if you notice any strange behavior. Normally it shouldn't be any, but who knows...
DISCLAIMER: Do this at your own risk. I will not be responsible if something bad will happen.
Can you explain wat exactly those lines doing? What is different in the multitask experience / behavior? Many thanks
If you'll open up Chrome, go to a webpage, then press the home button and go back to Chrome again. In most cases you'll notice that it starts reloading the page. I've noticed that a lot of apps are restarted/refreshed after a short time if I leave them in the background and mostly you never get to the same point where you left off in the app.
I'm not a programmer and I just saw in S6 edge+ forums how to improve multitasking: http://forum.xda-developers.com/s6-edge-plus/general/root-ram-management-multitasking-fix-t3228917. As you can read there, the guys are changing plenty of values, but at the suggestion of member @citytrader who changed only 2 lines, I tried this in my Le Max 2 and it worked pretty well. Somehow I don't have the redraws that I had before. Battery life seems unchanged. No lag (there was none before as well), but the most important thing no more redraws (with some small exceptions but in any case, far less than before).
You can find articles/threads on xda about spcm and fha/dha.
I think the reason for that is that EUI is pretty agressive in closing apps to save battery.
Did you try to lock the app so its doesnt close.
Locking the app does not help. As you said, EUI is pretty aggressive at RAM management. I'm pretty sure that you have viber/whatsapp locked but if you switch to 2-3 apps and then come back to viber for instance, the app is redrawing.