[PARANOIDANDROID JB/CS] Developers only: Porting, Support and Maintanance - Android Software/Hacking General [Developers Only]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
disclaimer:
it shouldnt be necessary to mention but well, Paranoid-Settings is meant for official paranoid android only or ports that stay true to our vision. it is not meant to be included in other roms or kangs - unless we give permission. this is our good name that people pull through the mud when they mix it with conflicting source like aokp. hybrid engine and dpi changer will only result in a crappy user experience for the end-user. Hybrid relies on a clean system and does not change its DPI, thats the whole point of it. furthermore hybrid engine is huge and complicated to kang because it grew over half a year and hundreds of commits, resets, reverts, rewrites. the only real hybrid engine is the result of a clean repo init and . rom-build.sh devicename.
kangs and roms that dont have our permission can either write their own implementation (its really just a text file reader/writer) or adapt on the old paprefs version in the ICS branch, which is 100% opensource. hybrid engine is 100% open source aswell of course.
Some of you may have heard of tablet mode and if you have tried it you know well that it smashes your phone. Apps are small, their layout is screwed, things overlap, crash or stop working, Google Play forbids you to download, if you tried AOKP you cant even use launcher and phone. In short, it is a mess.
PARANOIDANDROID changed that. It does not "heal" tablet mode, it obliterates the boundaries. You define how big or small apps are, you define in which UI they display, no matter if your phone runs in tablet or phone mode, which also you can define. Customize every single entity on your phone, lockscreen, navigationbar, system-components, widgets, apps. If you prefer stay with your three bearpaw buttons + drop-down curtain or switch to a combined navigationbar + drop-up notificationcenter, enjoy Youtube in 3D, Gmail and settings in 2-columns, Chrome in its better mobile UI, etc. Nothing overlaps, nothing crashes, everything works as you'd expect. This is completely new ground and has never been realized before, it is lightyears from tablet mode.
We created it to establish the idea that tablet/hybrid mode can indeed work and that is was an error on Googles side to use the same layout for high resolution devices that is used on tiny little things like htc wildfire. We saw how badly build.prop tablet-mode was milked so we decided to remain closedsource until the codebase is mature enough to publish. Our first repos went public last week and the rest will follow soon, i will personally commit the hybrid sourcetree into CM9. Until then, do not ask us for sources, we have good reason to do it like this and when it's out people will know why, they will see something that works, not features for show. We are still fully open to ports. As long as they stay true to our vision and base on CM9.
As the sheer amount of porting requests needed to be addressed somehow we open this topic so maintainers can help each other and it'll be easy for us to take a look once in awhile as our pm-boxes are exploding. We understand that setting up PA can be quite confusing since it introduces must-have configurations that are unique.
​
GUIDE FOR PORTING PA 1.6 and higher (JELLYBEAN/CM10)
the bad news is, everything has changed. the good news is, porting will be way less troublesome. (-;
look at the ICS guide for more info, this ones onna be straight forward.
1. pad.prop no more. you'll have to look in /system/etc/paranoid/properties.conf. dont forget to supply the same file twice, as backup.conf, its a sefety net for users who screw their properties.
you dont need to worry about this file anymore. rom_min/max are arbitrary values. choose something that makes sense for your device. the GUI will pick it up and load its sliders with these values.
rom default dpi is a simple fallback value, used by the GUI aswell. rom default mode is the same. notice though that modes are not hardcoded, Youre targeting the actual layout containers. the GUI can even extract them from any apk. layouts for sysUI are: 360 (phone mode), 600 (phablet mode) and 720 (tablet mode). apps can define these tresholds as they want. thats the reason you couldnt get tabUI for playmarket for instance, because its containers sits at 800dp. "tabletUI" was hardcoded to 720. so thats no problem anymore.
the rest is clear, find a couple of good values for standard apps. make sure you dont create a spotty experience. and do set tabUI for the interesting apps. i have seen PA reviews on youtube and the guy browses the phone and everythings stock ... that kinda sucks. you dont need to boot into tablet mode right away, but at least take the time to find good values for settings, gmail, etc.
Code:
###################
# PARANOIDANDROID #
###################
## CONFIGURATION
%rom_dpi_min=160
%rom_dpi_max=320
%rom_default_dpi=320
%rom_default_layout=360
## CONFIGURATION
%hybrid_mode=1
%system_default_layout=0
%user_default_layout=0
%system_default_dpi=0
%user_default_dpi=0
## WORKSPACE PREFERENCES
android.dpi=0
android.layout=0
com.android.systemui.dpi=%rom_default_dpi
com.android.systemui.layout=%rom_default_layout
## SYSTEM PREFERENCES
com.paranoid.preferences.dpi=270
com.android.chrome.dpi=%rom_default_dpi
com.android.chrome.layout=%rom_default_layout
com.android.contacts.dpi=%rom_default_dpi
com.android.contacts.layout=%rom_default_layout
com.android.settings.dpi=245
com.android.settings.layout=720
com.android.calendar.dpi=260
com.android.browser.dpi=260
com.android.browser.layout=600
com.android.calculator2.dpi=160
com.android.calculator2.layout=600
com.android.email.dpi=230
com.android.email.layout=600
com.android.vending.dpi=220
com.android.vending.layout=1000
com.google.android.gm.dpi=250
com.google.android.gm.layout=600
com.google.android.talk.dpi=260
com.google.android.talk.layout=360
com.google.android.youtube.dpi=240
com.google.android.youtube.layout=800
com.google.android.apps.docs.dpi=240
com.google.android.apps.docs.layout=600
## USER PREFERENCES
well, thats it. i told you it was easy.
for those who port for legacy devices, we included a hide softscreenbuttons option in settings/system/navigationbar.
and then theres the speed dial preferences in the PA panel. thats a little bit compliated right now because the xml files that drive it are in the app itself. im not sure if you can backsmali it, it has a rom fingerprint. i need to ask jesus. one thing more, then that is resolved you will be able to create your own configurations, and those can not only contain hybrid data but ANY setting you can make in the entire android system.
example: on nexus we dont have much space in portrait mode, so the android standard of 5 notificationicons in tabletUI overlaps. so in one of those prefs i simply say: sysUI.dpi=240, that makes the systembar pretty big, sysUI.layout=720, that drops it into tabletUI, clock=0, that hides the android clock, notificationnumber=2, that limits the icons to two. i guess most of you will switch off softbuttons, and with these prefs you can do it, or even create several and let your users choose.
i know jesus has already completed the code to load user presets, i will add the information when i have it.
and dont forget this in your build.prop
Code:
ro.cm.version=PARANOIDANDROID
ro.modversion=PARANOIDANDROID
ro.pa.version=PARANOIDANDROID-pa_YOURDEVICE-1.XXa-DDMMMYYYY
oh, and do not, under any circumstance, touch build.prop dpi. system dpi runs always in default dpi.

GUIDE FOR PA 1.5 and lower (ICS)
1. Unlock Tablet Mode for all devices
This has been already stuffend into the framework by us and if you use our files you wont need it, but i will include it nonetheless. Legacy devices crippled with hardware buttons need hacks to make tablet mode work. I dont know exactly whom to thank for this find, names that pop up in my head are Xylograph and evilisto. Ics compilant devices simply need one more entry in their build.prop: qemu.hw.mainkeys=1. You can include both, doesnt hurt.
Code:
--- a/services/java/com/android/server/wm/WindowManagerService.java
+++ b/services/java/com/android/server/wm/WindowManagerService.java
@@ -5962,7 +5962,7 @@ public class WindowManagerService extends IWindowManager.S
unrotDw = dw;
unrotDh = dh;
}
- int sw = reduceConfigWidthSize(unrotDw, Surface.ROTATION_0, density, un
+ int sw = reduceConfigWidthSize((int)(unrotDw / density), Surface.ROTATI
sw = reduceConfigWidthSize(sw, Surface.ROTATION_90, density, unrotDh, u
sw = reduceConfigWidthSize(sw, Surface.ROTATION_180, density, unrotDw,
sw = reduceConfigWidthSize(sw, Surface.ROTATION_270, density, unrotDh,
build.prop
Code:
###################
# PARANOIDANDROID #
###################
ro.sf.lcd_density=192
qemu.hw.mainkeys=1
2. Find out tabletmode DPI treshold value
Tablet mode is AOSP standard functionality. ICS is will drop into tablet mode if it acknowledges a certain treshold DPI, depending on your devices screen. Changing ro.sf.lcd_density in /system/build.prop will do. You can calculate that value as follows, here's a snippet of the ICS code that decides if your UI runs in tablet mode or phone mode.
Code:
int shortSizeDp = shortSize * DisplayMetrics.DENSITY_DEFAULT / DisplayMetrics.DENSITY_DEVICE;
mStatusBarCanHide = shortSizeDp < 600;
In short, you need to reach a short-side device-independend pixel number of 600. Example: Nexus has a width of 720 and a height of 1280, shortest side is 720, default density is 320. shortSizeDp = 720 * 160 / 320 = 360. lower than 600, phone mode. We need to lower the Dpi: shortSizeDp = 720 * 160 / 192 = 600. Thats it, tablet mode!
The formula is:
Code:
treshold_dpi = shortest-side-dp * 160 / 600
3. Setting up pad.prop and build.prop
/system/pad.prop is the file that defines how apps scale and in which UI they display. You should provide your users with a nice selection of everyday apps and define the system-apps well. Users should not be shocked when the phone boots up, what they are supposed to see is something that drops their jaws.
For Galaxy Nexus it looks like this:
Code:
###################
# PARANOIDANDROID #
###################
## DEFAULTS
%rom_tablet_base=192
%rom_phone_base=320
%rom_mid_base=260
%rom_mid_high_base=290
%rom_framework_dpi=250
%rom_systemui_dpi=220
%rom_launcher_dpi=290
%screen_default_width=360
%screen_default_height=567
%screen_default_layout=268435474
%screen_opposite_width=600
%screen_opposite_height=1018
%screen_opposite_layout=268435491
## CONFIGURATION
%hybrid_mode=1
%system_default_dpi=%rom_mid_base
%user_default_dpi=%rom_mid_base
%user_default_mode=1
android.dpi=%rom_framework_dpi
com.android.systemui.dpi=%rom_systemui_dpi
## PREFERENCES
com.android.phone.mode=1
com.android.inputmethod.dpi=%rom_phone_base
com.android.inputmethod.latin.mode=1
com.android.inputmethod.dpi=%rom_phone_base
com.android.camera.mode=2
com.android.camera.dpi=%rom_tablet_base
com.cyanogenmod.trebuchet.mode=1
com.cyanogenmod.trebuchet.dpi=%rom_launcher_dpi
com.anddoes.launcher.mode=1
com.anddoes.launcher.dpi=%rom_launcher_dpi
com.teslacoilsw.launcher.mode=1
com.teslacoilsw.launcher.dpi=%rom_launcher_dpi
com.android.chrome.mode=1
com.android.chrome.dpi=%rom_mid_high_base
com.android.calendar.mode=2
com.android.contacts.mode=2
com.android.email.mode=2
com.android.htmlviewer.mode=1
com.android.mms.mode=1
com.android.settings.mode=2
com.android.vending.mode=2
com.google.android.gm.mode=2
com.google.android.googlequicksearchbox.mode=2
com.google.android.talk.mode=1
com.google.android.youtube.mode=2
What is important here is that you need to set it up first with device specific informations. Here's a small rundown of these values:
%rom_tablet_base=xxx - table mode treshold dpi
%rom_phone_base=xxx - default device dpi
%rom_mid_base=xxx - a good middle value that works both for tabUI & phoneUI apps, for nexus its ~260
%rom_mid_high_base=xxx - a little bit higher than middle
%rom_framework_dpi=xxx - a good value for the lockscreen
%rom_systemui_dpi=xxx - good value for navigationbar
%rom_launcher_dpi=xxx - default value for trebuchet
%system_default_dpi=0 - sets the global density for system apps. 0 means undefined. We will probably make it obsolete soon.
%user_default_dpi=xxx - sets the global density for non-system apps, set it to default dpi as this will guarantee that all of your users apps will look stock
%user_default_mode=1 - sets the global UI for non-system apps. 1 = phoneUI, 2 = tablet UI. set it to 1, all user apps will display in mobileUI. If the user has tablet ready apps he can switch himself in the settings panel
## P.A.L PARAMETERS - these are extremely important. you get them by logging the output of Configuration in tablet mode (_opposite) and phonemode (_default) kevdliu wrote a nice little helper to make it easier for you, look here
make dead sure you get pad.prop right or you'll get bootloops or crashes!
notice that we use packagenames for apps, if you dont know the name of an app open up your shell and type:
Code:
adb shell
pm list packages -f
android - framework-res, applies to lockscreen, dialogs, powermenu, toasts
systemUI - applies to the navigationbar, makes it bigger or smaller. DO NOT APPLY an UI to these two apps. everything else is fine, set it to tablet or phoneUI all you want, but not these two!
Configuration in phone mode and tablet mode
build.prop needs to be configures like this:
Code:
###################
# PARANOIDANDROID #
###################
ro.sf.lcd_density=192
ro.cm.version=PARANOIDANDROID
ro.modversion=PARANOIDANDROID
ro.pa.version=PARANOIDANDROID-pa_maguro-1.5a-28JUN2012-180025
density to tablet treshold. versions to PA and version in that exact format because internal functions are relying on it (OTA for example). change the name of your device and the date. the last numbers, i have no idea what they are, came from the buildscript.
4. Check our sourcetrees
More and more source will be published soon. Right now we have three projects out, OTA, Backup and Trebuchet (optimized for tabletmode with cool features). Hybrid code will come out soon. Use what you can get from there: http://betadan.com/paranoid/sources/
5. Port the rom
You are ready to go. Do what you always do when porting roms. I have zero experience with that. Again, use CM9. Do not even think about using AOKP.
Check out Xylopgraph's PA porting guide
6. Link to our Google Apps
Google policy forbids you to use their market if you change your DPI. The only values allowed are 160, 240, 320. Why? No one knows why. There have been workaroundw, wiping cache, using a valid DPI, open market, reboot back, blablabla, forget it, its rubbish. It will work for a minute and then it will cease to. In our package Phonesky and GoogleServicesFramework were hacked. It has other additions aswell: http://4ndr01d.com/drcmda/common/
7. Post your port link and help out others
We will include you in our webpage and when our repo's are open you are invited to compile from source and/or submit patches and additions. We might even work together as theres still much to do. Be sure to help out others here.
​

-----------------------------reserved

Thanks Moles, this will continue to help us on the Vivow Port till we can build from source.

Thanks for this innovation. Salute!

I just thanked all post ,if yo had one more I woudl have thanked it to ,
in other words , thanks !

Awesome! Thanks for this awesome contribution!

Thanks for opening up this thread, I actually have a question for you professionals. I have been trying to figure out how to enable audio during the boot animation. I have been searching like crazy to figure it out. I have tried adding the following to /system/customize/CID/default.xml. And also ading a android_audio.mp3 to /data/local.
Code:
audio="/system/customize/resource/android_audio.mp3"
I have also tried placing the android_audio.mp3 and the bootanimation in /system/media but no love.
My buddy GROGG88 even made a zip file for me to flash that added some files to /system/bin but still no luck. Here is the zip if you would like to take a look at it.
I plan on making some more bootanimations for the Paranoid Android ROM for the Sensation and would really like to be able to include audio with them. Any assistance you can give will be very much appreciated.

What files does ParanoidOTA depend on, (/system/framework or others)? I get it copied over, but it crashes on me when I try to open it.

sgtkwol said:
What files does ParanoidOTA depend on, (/system/framework or others)? I get it copied over, but it crashes on me when I try to open it.
Click to expand...
Click to collapse
Only settings are used (but settings depends on OTA not OTA on settings), you must be sure the right intent is sent via Settings > About > Check for updates. Also we need first to setup environment if some device is gonna add OTA.

D4rKn3sSyS said:
Only settings are used (but settings depends on OTA not OTA on settings), you must be sure the right intent is sent via Settings > About > Check for updates. Also we need first to setup environment if some device is gonna add OTA.
Click to expand...
Click to collapse
I'm porting from Crespo4g to Epic4g which are very similar devices.
Paranoid OTA and Paranoid Settings showing in Settings.apk I pulled from Crespo4g must be different, then. Not seeing a ParanoidSettings.apk, am I missing something? I have "Paranoid Settings" showing, but clicking it or "System" crash Settings.apk that I pulled from Crespo. No Paranoid Settings when I compile from source. Unable to local pad or pal within existing builds, either.

made an app that displays the needed PAL information and tablet dpi threshold and thought i would share it here for other developers
its attached to this post

kevdliu said:
made an app that displays the needed PAL information and thought i would share it here for other developers
its attached to this post
Click to expand...
Click to collapse
thanks! is there a way to make it calculate the treshold dpi aswell?

molesarecoming said:
thanks! is there a way to make it calculate the treshold dpi aswell?
Click to expand...
Click to collapse
yup im going to update it shortly
uploaded

mole: ive got my port on i717 almost running flawlessly now, few minor issues
http://forum.xda-developers.com/showthread.php?t=1686320

Thinking about porting this..

I am ported it to HTC Desire HD..
http://forum.xda-developers.com/showthread.php?p=26929079
Sent from my Desire HD using Tapatalk 2

JamieD81 said:
mole: ive got my port on i717 almost running flawlessly now, few minor issues
http://forum.xda-developers.com/showthread.php?t=1686320
Click to expand...
Click to collapse
need your problems here dude, thats why i opened the topic.
if somethings not working post logcats, etc.

@molesarecoming
I totally forgot my skills of compiling kangs, can you guide me a bit through pm... Wifi Tethering is not fully working....
My computer specs, already had external HDD to compile...
-Intel i7-2760qm (8 cores, 2.4ghz)
-8 GB Ram
-1 TB HDD SATA (Internal HDD)
-500 GB HDD 3x faster writing...

DaXmax said:
@molesarecoming
I totally forgot my skills of compiling kangs, can you guide me a bit through pm... Wifi Tethering is not fully working....
My computer specs, already had external HDD to compile...
-Intel i7-2760qm (8 cores, 2.4ghz)
-8 GB Ram
-1 TB HDD SATA (Internal HDD)
-500 GB HDD 3x faster writing...
Click to expand...
Click to collapse
what i do is mostly hacking. i have never ported a rom before. i guess what i would do is taking a nightly or compiling a build, test if everything works and then add pa's additions. i cant remember all components but from mind they are: framework.jar, framework-res.apk, android.policy.jar, services.jar, maybe core.jar. the apps are not so important, you can compile our trebuchet fork from source, try making settings.apk run, if not i think that ones coming out today and if not today than very soon.
it would be cool if one of the guys who's made it writes a small rundown and i would put it up.

Related

4/27-DConfig 1.2-NEED TESTERS! GUI for custom Apps2SD,New Dalvik Tweaks,JIT,Swap,more

I decided to start a new thread for sanity purposes, the last one is already getting too big to scroll through. Here is the first release of my GUI + updated script that easily configs rom options. I tried to write this as generic as possible so we have the most room for upgrade in the future. Right now its pretty ugly but alot works. I need testers to play around with this, theres no way i can test every possible rom and every possible switch.
This should work with any kernel that runs app2sd, just needs a slight tweak to the init.rc to make sure apps2sd directorys are setup before launching the rom. This takes alittle bit more time to do it properly. Ill be posting a few different flavors for various roms out there. If you have a bug, please adb logcat _really_ helps. Also rom version you are on, and a copy of your /data/data/com.treve.dconfig/dc.conf & dcbannedapp.conf, i also have started to implement logging, /data/dcboot.log will help. sorry for files all around next version will fix alot. This requires toolbox (needs getprop/setprop) everything else should be included.
pretty much flash the right version over your rom, set your options, save, reboot & enjoy. shouldnt be much more to it. if you get forcecloses upgrading or after restoring apps wipe your /data/app-private/* some apps dont play nice. first boot will take _forevor_
Defaults are apps2sd with apps & app-private moved, dalvik on phone, swap to SD, JIT off. **it does not read back options saved so use other methods to tell if its working till next build **
Contact me if you want to put this in your rom or help me out!
Downloads:
v1.2 -
-Adds in dalvik VM heapsize settings
-fixes permissions a bit
-backend work for audio move underway
v1.2 downloads-
Damage/Fresh2.0d/Sushi/Aloysis kernel - http://www.4shared.com/file/d2UVEYLJ/treveDConfigDCKERNELv12.html
v1.1 -
Adds in restoring of configs capability. Need to manually hit the button to restore for now.
sets by default to "safe" settings. Should increase compatibility. Users of previous versions once you save your settings once they should stick on upgrades until you wipe the device
V1.1 Download (tested flashing ontop of damagecontrol & pancake 0.1)
Damage/Fresh2.0d/Aloysis (2.6.29-d30020a8) - http://www.4shared.com/file/vFIOghLT/treveDConfigDCKERNELv11.html
v1.5 gumbo (2.6.27GK-0.32) - http://www.4shared.com/file/4KolEQTJ/treveDConfiggumbo15ckernelv11.html
v1- first release
-newer a2sd then previous release
-set config options in gui
-initial configs write to /system/etc/ for now my GUI writes to /data/data/com.treve.dconfig/ a2sd will prefer the ones in data/data/ if they exist. this should allow for rom cookers to put in there recommended settings, but if your flashing over a existing rom without a wipe it will keep all your preferences. This is nice because we get stuff like auto remove of apps we dont use without romcookers putting out over 9000 roms.
-GUI DOES NOT READ BACK CONFIGS YET. This will come next version. For now once you exit form it will revert to defaults so you will not beable to see what you have set once you exit. (main settings & banned apps are on 2 different configs, you do not need to save both pages when making changes.)
-No icon or package name. Deal with it - you get functional or pretty. Ill clean stuff up later.
v1 downloads-
Damage kernel(2.6.29-d30020a8) - http://www.4shared.com/file/P_IlAvUs/treveDConfigDCKERNEL.html
Fresh kernel from 2.0d (untested by me) http://www.4shared.com/file/FQYFsuJa/treveDConfigfresh20dkernel.html
Gumbo 1.5c (realllly untested) http://www.4shared.com/file/hK9k7g-Q/treveDConfiggumbo15ckernel.html
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is the backend settings that are possible. This stuff might be jibberish to most but with gui now it shouldnt matter to more than rom cookers or people who like to tinker.
**NOTE COMMENTS STILL HAVE 0 AND 1 NEW VERSION USES TRUE/FALSE**
/system/etc/dc.conf is the heart of this mod now. Dont try to delete variables or the conf file, scripts not smart enuf to check for that yet.
Code:
#DC Config file
#Hacked up by TrevE @ xda for damagedrom
#
#dc.a2sd.active - disables all a2sd
#dc.a2sd.apps.active - 0 moves all files to /data/ - 1 moves to /sdcard/data/ can be controlled seperate from a2sd.active
#dc.a2sd.dalvikcache.active - 0 keeps files on /data/ - 1 moves to /sdcard/dalvik-cache/
#
#dc.swap.active - 1 auto mounts sd card partition mmcblk0p3 for swapping. 0 keeeps it at mtdblock4
#dc.swap.swappiness - Range: 0 - 100, larger number = more likely to swap
#dc.jit.active - 1 to enable JIT next boot (make sure to switch to lancher as a defalt home first) 0 to disable.
#dc.bannedapp.active - 1 enables ban list (renames .apks to .dcbanned) defaults are set to programs that interfere with JIT
#dc.firstboot.active - check for firsboot script in /data/ on boot
#dc.zipalign.active - zipalign anything that needs it in /data/ on boot
#
# scaling_governor has 2 settings with HTC Perflock "ondemand" or "performance"
# lowmemkiller default rom settings - 1536,2048,4096,5120,5632,6144
# lowmemkiller less agressive settings - 1536,2048,4096,5120,15360,23040
# lowmemkiller more agressive setting - 1536,3072,4096,21000,23000,25000
#A2SD specific stuff script
setprop dc.a2sd.active true;
setprop dc.a2sd.apps.active true;
setprop dc.a2sd.dalvikcache.active true;
#Other system parms
setprop dc.swap.active false;
setprop dc.swap.swappiness 30;
setprop dc.jit.active false;
setprop dc.bannedapp.active false;
setprop dc.firstboot.active true;
setprop dc.zipalign.active true;
#Former gumbo.sh settings
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "1536,3072,4096,21000,23000,25000" > /sys/module/lowmemorykiller/parameters/minfree
==================="Basic" Options===================
Apps2SD
-Default is dalvik & apps are moved to sd. (Does not hurt to leave enabled if you are not using it.)
-if you have a slower SD card it might be better moving dalvik back to internal memory.
You can enable/disable dalvik & app move separately. To move dalvik back to SD:
Changing any options are easy. For example - To turn just dalvik sd cache off:
start -> run -> cmd
defaults are in:
adb pull /system/etc/dc.conf .
if you used dc tool use the one in data data:
adb pull /data/data/com.treve.dconfig/dc.conf .
open up dc.conf in notepad. Change the one line
setprop dc.a2sd.dalvikcache.active false;
to
setprop dc.a2sd.dalvikcache.active true;
push it back to phone
adb remount
adb push dc.conf /system/etc/
Click to expand...
Click to collapse
-New users any time just format ext(2 or 3) in recovery to enable. Next boot it will automatically move your apps. If you get any FC after a new enable of a2sd try Fix apk UUID option in recovery
AutoZipalign
-On by default.
anything written with newer dev kits should do this automatically, but there are still a buncha market apps that arent. This just goes through /data/app/ on boot and checks that everythings aligned and fixes what it needs to. Fixes some of the rosie lag loading the icons.
more here http://developer.android.com/guide/developing/tools/zipalign.html
scaling_governor
-Set to ondemand by default
Just change word in quotes. With HTCs 2.6.29 kernel we have two options (until someone gets us source)
-performance
-ondemand
lowmemkiller
-Set to more aggressive by default.
To change just edit numbers in double quotes on the lowmemkiller line in dc.conf.
Common values: (included at top of conf but here again for reference)
Code:
# lowmemkiller default rom settings - 1536,2048,4096,5120,5632,6144
# lowmemkiller less agressive settings - 1536,2048,4096,5120,15360,23040
# lowmemkiller more agressive setting - 1536,3072,4096,21000,23000,25000
DCBannedapp.conf
-default is off
*If this "banned app" flag is set it will rename any file in /system/etc/dcbannedapp.conf to .banned. When its set back to 0 it will "re-enable" them. Right now dcbannedapp.conf cannot have anything but a full filename (/system/app/Rosie.apk), one per line.
*if the delete banned app flag is on anything in this list will be deleted instead of renamed. No going back.
This is useful in a few ways-
-if you enable JIT we can put a list of banned apps (htc stuff) to increase stability. If you want to disable JIT just flip to flags and you have sense again.
-rom cookers can just post config files to have several different versions of a rom from one download (for ex: sense/no sense version)
Here is an example of dcbannedapp.conf I have been playing with. This strips sense out & gets you down pretty bare bones. (Yes there is more we can remove, i trimmed this list up a bit when we were having issues. now that things seem stable its time to cut out more )
Code:
/system/app/com.htc.MusicWidget.apk
/system/app/com.htc.TwitterWidget.apk
/system/app/com.htc.StockWidget.apk
/system/app/com.htc.WeatherWidget.apk
/system/app/DCSStock.apk
/system/app/Facebook.apk
/system/app/Flickr.apk
/system/app/HtcAddProgramWidget.apk
/system/app/htccalendarwidgets.apk
/system/app/htccontactwidgets.apk
/system/app/HtcClockWidget.apk
/system/app/HtcLockScreen.apk
/system/app/htcmailwidgets.apk
/system/app/htcmsgwidgets.apk
/system/app/HtcNaviPanel.apk
/system/app/HtcRingtoneTrimmer.apk
/system/app/htcsearchwiddgets.apk
/system/app/HtcSoundRecorder.apk
/system/app/HtcTwitter.apk
/system/app/IM.apk
/system/app/IQRD.apk
/system/app/OMADM.apk
/system/app/Rosie.apk
/system/app/SDSA.apk
/system/app/Sprint_Core.apk
/system/app/Sprint_NFL.apk
/system/app/Sprint_Nscar.apk
/system/app/Sprint_TV.apk
/system/app/Sprint_TVWidget.apk
/system/app/Stock.apk
/system/app/VoiceSearch.apk
/system/app/WidgetDownloadManager.apk
/system/app/WorldClock.apk
firstboot
-default is on
script in /data/firstboot.sh will run automatically on nextboot if it exists. Auto deletes when done right now (new flag soon)
===================Advanced Options===================
Handle with care
Swapping
-Swap is disabled by default.
-If you have a fast card you can turn it on by pulling /system/etc/dc.conf and changing
setprop dc.swap.active false;
to
setprop dc.swap.active true;
More about swapping here (in same article as compcahe, not the same) http://wiki.cyanogenmod.com/index.php/Compcache
If you look at benchmarks below my guess is the lower swap is better with quick burst reads but when you swap moree and more out the card (or the bus) hits a limit a starts to choke. Went back down to 30 an result were right around 4.6 for copy mb again.
JIT
**JIT does not play nice with rosie or HTC lockscreen**
Enable bannedapp flag & put any conflicting files in /system/etc/dcbannedapp.conf This will let you switch between JIT compatible stuff/ non JIT on the fly.
To enable JIT:
-first use homeswitcher to switch to anything becides rosie and make it default (included lancher.apk in update).
-Now you must adb shell rm /system/app/HtcLockScreen.apk
-Now pull /etc/dc.conf and change
setprop dc.jit.active false;
to
setprop dc.jit.active true;
reboot & enjoy
===================Fixes===================
-Avaulaunches modded AudioRC fix to work with this. Flash the latest mod above then this ontop of it right after.
http://www.4shared.com/file/9mEpJR-0/AvalaunchRCFix_ForTrevEMod.html
-If you get bootloops upgrading try whacking private apps
Code:
adb remount
adb shell rm /data/app-private/*
adb shell reboot
-If you want to stick with JIT & have no use to ever enable the banned apps again you can delete em
Code:
adb remount
adb shell rm /system/app/*.dcbanned
===================Benchmarks===================
linkpack/membench seem relevant here, neocore doesnt really fluxuate in fps doesnt seem worth it.
(post yours & any tweaks you make!)
Here is with a2sd app & dalvik moved
Swap off, Swap @30, Swap @ 60(in order left-> right, yes 60 is worst.)
A2sd app/Dalvik/[email protected]/JIT on
JIT off /on:
finally a aps2sd I understand! This us amazing. Testing....
apps2sd working great on aloysis! You rock
Do I flash this over my Rom now. I am using Regaw.
redram38 said:
Do I flash this over my Rom now. I am using Regaw.
Click to expand...
Click to collapse
the damage control should flash over regaw fine. once you flash go into the app & tweak things how you want, then save & reboot for it to take effect. If you have a fast SD card the most common mods are moving dalvik to SD and swapping. JIT adds a nice speed boost as you can see by the benchmarks but isn't quite working in sense yet so make sure to disable sense in banned apps.
Going without sense is a bit weird at first but theres a buncha nice apps out there. check out helix launcher, beautiful widgets and bookmarks2. That with the android power widget & genie weather widget im pretty happy.
redram38 said:
Do I flash this over my Rom now. I am using Regaw.
Click to expand...
Click to collapse
That's what I'm about to do
I'm pretty sure he built this to run with "any" sprint based release
THANKS TrevE!!!
This is amazing. It's been awesome watching this come together, I can't believe you built this into an app. You sir are officially THE MAN
been playing around tweaking my settings. cant wait for it to save settings its wierd without it.
I appreaciate the work and all but it really needs an icon lawlz
thanx
sorry for the app being a bit crude still i wanted features to work rather than look good. Itll get better in time remember this is only a few days work i got alot more planned
Hopefully later on well have some kinda icon. Im close to being done with restoring states from a config now, probably wont see something till later tongiht though. Unless anyone finds bugs with the actual script itself it will ust be a new APK to push. Keep the reports coming in of successes or any issues!
TrevE said:
Going without sense is a bit weird at first
Click to expand...
Click to collapse
Do you know of any mobile data toggle widgets that actually work as a toggle and don't just take you to the mobile data settings when launched? I spent a few hours last night trying to find one.
Have you tried the htc settings widgets?
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
"fixes some of the rosie lag loading the icons.."
When I flash some ROMS, and my phone 'falls asleep', when I wake it back up, i get a black screen for a second, and then everything loads, is this what your talking about?
jAm-0 said:
Have you tried the htc settings widgets?
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
that's the widget i'd like to have emulated in helix
so how is this working out for people? Is everything working ok or are we crashing and burning? i got a new version that should keep your settings displayed even if you close out of the program. its looking like it will just be an APK because i havent had any bug reports (yet) dunno i thats a good thing or not...
HarveyStyles said:
"fixes some of the rosie lag loading the icons.."
When I flash some ROMS, and my phone 'falls asleep', when I wake it back up, i get a black screen for a second, and then everything loads, is this what your talking about?
Click to expand...
Click to collapse
the rosie lag i was talking about is if you pull up an app tray and quickly scroll down. I can usually tell you the non zipaligned apps because it pauses for a second loading their icons usually. everything feels generally faster though JIT makes a nice difference. Try it and see
aiwetir said:
that's the widget i'd like to have emulated in helix
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=652626&highlight=manup+widgets
Gregalous said:
http://forum.xda-developers.com/showthread.php?t=652626&highlight=manup+widgets
Click to expand...
Click to collapse
those are a pretty damn close match to HTCs good find im sure some people will like that. JIT is def worth ditching sense, the phone feels so much faster senseless anyway and the added megaflop JIT gives is always nice. I went with the android power widget, kinda like having it all one one strip saves some space.
thanks for the link!!
i like the 1x5 power widget but it's not got every toggle i want.
why am I getting reboots?
Everything appears to be working, then I plug my phone into the PC vis usb and that screen freezes on me then reboots. Or I'm checking space on the phone and my sdcard, and that screen freezes and reboots on me.
I partioned my card to ext2 -- ext3... with 32swap and 512...
Help, not really sure what is going on, just keeps rebooting on me over and over again now.
Ok, this sucks! I did a nandroid back to before I had my sd card partioned, and now I get constant reboots (phone goes asleep, then will not awake right away, but instead awakes in a reboot).
How do I unpartition my card?
Which one of these would I use on Aloysius 2.0.5b?

[APP][2.2+]Holo File Explorer (Update 4-11-2012)

Now on Google+ !
https://plus.google....615763333814534
Update 5-27-2012
This update replaces the text based view pager indicator with a sliding bar that looks just like the stock launcher's indicator. I'm still not satisfied with the contrast between the bar and the surrounding elements, because it isn't easy to see at this point. I'll keep tinkering with it, and would welcome suggestions. In addition, I have figured out how to allow viewing of read protected directories like /data/. My implementation isn't perfect, which leads me to my next point. I have come to realize that there are some fundamental shortcomings to a few of the apps underpinnings, and I need to find a way to fix them. I have yet to figure out how to make the root process persist so that root functionality doesn't throw up a toast every time it does something, and I seriously need to clean my code.
Therefore, my plan is thus: I'm going to take a crack at helping the dev of OpenExplorer figure out how to enable full root functionality. His code is the only resource I have been able to glean much useful info from, and his own implementation is still half-baked. (seriously, why are there no robust root related resources out there?) Then, (tentatively) I'm going to fork his repo and replace the look and feel of his app with that of Holo File Explorer, while retaining what appears to be a vastly superior back end. The downside to this is that we're looking at something of a rabbit hole, so you guys may not hear from me for a bit. The upside is that forking OpenExplorer will provide a less buggy experience, plus lots of extras like network folder, dropbox and box.net access.
I'm also hopeful that at the end of this process, I'll have my own code hosted on GitHub and ready for collaboration. If I can get interested parties to help with development, It'll speed up the rate of releases. Because to be honest, my rate of release hasn't exactly been timely of late, and you guys deserve better than that. This is the best answer I can come up with to solve the problem. What does everyone think?
Original Rootz thread: http://rootzwiki.com/topic/17572-ap...er-formerly-ics-styledswipe-update-3-29-2012/
Hello Everyone. I've been working on a new file explorer app for phones since the beginning of the year, and I would like to present what I have accomplished so far in order to get some feedback. The reason why I decided to make this app is that most (if not all) of the file explorers out there have clunky/unoptimized user interfaces and/or lackluster feature sets.
I recently purchased a Galaxy Nexus and had decided that I needed a file browser to match the aesthetic appeal of the rest of the system. After hours of searching through several dozen of the market's best browsers, the only one I could find with any degree of stock visual polish was inKa file browser. Unfortunately, the app was too basic for my needs. No root features at all, etc. This prompted me to build my own file browser (although it is still far from complete).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What the app has thus far:
1) Swipable pages. There are 2 (for now - hoping to enable "new tabs/pages") swipable views that can be navigated independantly (just like you would on a desktop computer with 2+ explorer windows open.
2) Files can be cut, copied and then pasted within or across the swipable pages. (long press anywhere on an item or check the boxes in order to bring up the "contextual action mode" (screenshot 3)
3) The drop down at the top of the page displays the folder hierarchy for the currently selected folder view.
4) The start of a file details screen (Screenshot 5). There are a lot of functions that people can perform on files (MD5 checking roms is a big one in my mind) and I just don't like the idea of relegating those functions to dialog boxes or menus. I know that this kind of view isn't something that any of the other file explorers have, but I think there is value in departing from that convention. Note: MD5 and permissions aren't implemented yet. Soon though.
5) MD5 summer and checker is now working! I tested it on a 100+mb rom and it ran pretty quickly (5 or 6 seconds) on my Galaxy Nexus, so Rom Flashers might enjoy using this one. I don't have the UI polished to my satisfaction yet, but the functionality is there.
6) Sharing files is now enabled. The updated ShareActionProvider for 4.0+ will be coming at some point.
7) Opening/installing files/apks! Bugs aside, the app now handles almost all of the usual file explorer functions.
8) Themes! Switch them under general settings, and then exit if switching between dark and light or darkactionbar to get the text colors to reload properly. Working on fixing this.
What isn't done yet:
1) Root actions. This is a biggie, as I want this app to satisfy both power users and casual users at the same time. Feel free to comment on your most desired root functions.
2) File summary views. This would open if you clicked on a file, and would present a summary of the meta information. This view would also provide functions like md5 comparison, opening in external apps, permission setting, etc...
3) Themes. As you can see, the app is currently built on Holo Light (one of the ICS stock system themes). I plan on adding an option for Holo (dark) and maybe more. Depends on the demand.
4) A robust data summary view, including something similar to what you find in the DiskUsage app in the market, as well as some other metrics. Maybe even an miui-like file type size summary.
5) I'm considering a view (linked to from a button in the top right corner of the app) that displays currently running and finished file operations. I think this might be better than throwing up a dialog box for big file copy/paste tasks and having it keep the user from doing anything until the operation is done.
6) Bookmarks
7) Search. Not sure if this will be a basic file search or a grander attempt at indexing and speed.
8) A text editor.
9) Other basic things like an actual settings page, polished action mode icons, image previews and apk icons, an actual app icon, proper folder and file icons (the one's in place now look terrible and are improperly sized, but I'd rather focus on other things first), and general UI polish.
10) Image previews And there you are. Please provide any and all feedback/criticism/praise/trolling that you can. I'd really like to build this into something that works for everyone. Thanks!
The Story of my Progress Thus Far:
UPDATE - 2/9/2012:
Jake Wharton just released beta 6 of Action Bar Sherlock last night, so I'll hopefully have a backwards compatible version of the app out soon (maybe within the next day or so? Depends on how many things are broken in Gingerbread and beyond.) Done as of "alpha 2". I have an old Droid X, so I just need to do some flashing to test both Froyo and Gingerbread. I've also made incremental progress in a lot of areas. A basic settings screen is in place, "new folder" and "refresh" action buttons have been implemented, and I have the start of the file properties screen together. Things are moving along quickly!
UPDATE - 2/14/2012
New stuff:
*A placeholder settings menu now appears when users click settings
*See screenshot 5 for a look at the file info screen. Currently accessed by clicking on a file. Not sure if this is how things will stay, since this is a departure from the ususal "click to open in another app" behavior.
*Gingerbread compatibility! May be a few bugs here and there, but I have the thing running on my old Droid X with CM7. Theme is a little rough for GB devices, so I have some work to do there.
*Buttons more clearly indicate whether they have been implemented.
UPDATE - 2/15/2012
New stuff:
*A whole bunch of bug fixes dealing with copy, cut and paste. Things are still a little broken, but way better than they were before. Remaining issues deal with the UI not properly reflecting paste status - nothing sinister.
*Blue dividers between each page of the viewPager
*Sharing files now works! Select 1 or more files and send them via 3rd party app.
*Files can now be opened in 3rd party apps from the file view screen *Files can be MD5 summed and compared in the file view screen
*I did some checking and things seem to work in Froyo too
*Tinkered with the file icon logic a little bit, and in addition to some less obvious things I got apk icons working. *Based on some of the name suggestions, I renamed the app to "File Swipe." Name still isn't final, but someone mentioned that "Swipe" was a bit confusing. I'm listening to your name suggestions, so please keep em' coming.
*Polished up the action bar icons a tad bit (Search used to be a little too fuzzy, Data summary was too small, add didn't reflect that it was for adding folders, and bookmarks was too dark.)
UPDATE - 2/27/2012
New stuff:
*Themes! In addition to the original ICS Holo Light theme, we now have a dark and light-with-dark-actionbar theme. (You need to exit the app using the new exit button in order to get the themes to switch properly. Working on fixing this.) CAVEAT: There is currently a bug in ActionBarSherlock which prevents the loading of action bar icons when they are referenced via theme. Therefore, for now we are stuck with text instead of icons on the action bar. According to Jake Wharton's github bug tracker, we are about 9 days away from another Release Candidate, and the bug should be fixed then. Until then, don't freak out! (fixed now)
*A lot of internal refactoring and housecleaning. Not that interesting to you guys, but it had to be done in order to make themes work.
*App now handles reopening and orientation changes without crapping out (used to stop updating the navigation dropdown and would sometimes force close on actions). Learned some interesting things about viewpagers (the swipey pages as found in the market) in the last few days, so I'm hoping to be able to share that info with other coders out there in some fashion.
*The beginnings of a settings page (whoooo!)
*Settings includes the theme switcher and a popup to update the default directory. Haven't gotten it to verify directory input yet, so don't go too crazy.
*A new exit button. As mentioned earlier, you need to exit in order to get the themes to load properly. May disappear later. Not sure.
UPDATE - 3/5/2012
New stuff:
*Nothing show-stopping. Just little tweaks and fixes here and there
*After talking with some of you guys, tapping on a file now opens the file instead of a details screen. Details are now reached via the menu. The option will only present itself when a single file item is selected. Keep up the feedback (because I listen)!
*Tweaked some of the colors a little to provide contrast between file names and file details.
*Pulled in the latest code base from Jake Wharton's ActionBarSherlock. Therein lies the real bounty of changes. (This guy is a beast)
*Pre-3.0 users now get a proper ICS navigation dropdown, instead of that bloody spinner list.
*Icons are back, so things are looking normal again.
UPDATE - 3/28/2012
Holy bugger this has been a crazy month. Since the last update, I moved from PA to NC and started a new job. It's been a while but thanks for your patience.
New stuff:
*I'm back! (whoooooooo!)
*A hopefully bug-free scroll position/history stack. Essentially this means that instead of taking you up a level, the back button returns you to the previous folder you were at (each scroll pane gets its own history too), and it also remembers your scroll position when you go back. It's a small touch, but it really makes the whole thing more natural.
*Moved the pagertitlestrip from the bottom to the top and changed the styling a bit (as inspired by today's google maps/navigation update today). You'll all have to let me know if you like the change. Haven't figured out how to shrink the text size on it either, so those caps should be less obnoxiously large sometime soon. I'll try and make sure you don't have to wait another month before the next update Maybe sometime this weekend. Depends on how ambitious I am.
Update 4-11-2012
The most obvious change for today is the the theme. I've switched the default over to the app's "Identity" theme. The new goods are pictured in the updated screenshots. I've also fixed the app so that it displays the navigation dropdown at load time, and I figured out the bug that was making everyone's root file location only display one folder. There are probably some other small visual tweaks, but nothing that important.
Download "Alpha 9" apk here: http://goo.gl/olMcn
have been following the development on rootz for a while now but never tested the app for more than a few minutes. 95% of the stuff I need a file explorer for requires root, so really looking forward to that
XlAfbk said:
have been following the development on rootz for a while now but never tested the app for more than a few minutes. 95% of the stuff I need a file explorer for requires root, so really looking forward to that
Click to expand...
Click to collapse
Just curious, what are the root functions that you engage in most often?
bkensey said:
Just curious, what are the root functions that you engage in most often?
Click to expand...
Click to collapse
I think the most used, for most users, are copy/cut/paste/delete files on /system, and set permissions for files there.
Sent from my X10 Mini Pro using Tapatalk
Felimenta97 said:
I think the most used, for most users, are copy/cut/paste/delete files on /system, and set permissions for files there.
Sent from my X10 Mini Pro using Tapatalk
Click to expand...
Click to collapse
That's what I figured. As soon as I can get my file operation scheduler hammered out, I can start on the root file operations. The ones you mentioned are at the top of my list.
the ones mentioned + change owner, create softlink, run .sh script (basicly it's just "busybox sh script.sh")
No root here. I but zip unzip show/hide hidden files would be awesome
blackbearblanc said:
No root here. I but zip unzip show/hide hidden files would be awesome
Click to expand...
Click to collapse
Yeah, and that too still keep me on Root Explorer. But if you do what I said + what the guy I quoted said, I move to Holo File Explorer.
Sent from my X10 Mini Pro using Tapatalk
Agree with all the requests features so far, but for the record, the UI looks immaculate. Can't wait for it to get full root functionality.
dialmformostyn said:
Agree with all the requests features so far, but for the record, the UI looks immaculate. Can't wait for it to get full root functionality.
Click to expand...
Click to collapse
Immaculate is what I was going for
Just posted a new update with file sorting included. Useful if you're checking the download folder.
Archive is what compared to delete?
blackbearblanc said:
Archive is what compared to delete?
Click to expand...
Click to collapse
That would be zip/tar/etc. I do recognize that the label "archive" should be changed (since it does have gmail/deletion meaning attached to it), but I didn't want to just use zip either because zip only refers to one kind of file compression. Any ideas on how to handle that? Should I label it "compress" or just say screw it and use "zip" to initiate zips and tars?
looks amazing! Probably gonna move over to this file explorer when root features are added.
I'd go for "zip". While technically it's not correct everyone knows what it means with zip being the most known archive format.
XlAfbk said:
I'd go for "zip". While technically it's not correct everyone knows what it means with zip being the most known archive format.
Click to expand...
Click to collapse
Fair enough. I'll switch the label over for the next update. I'll look at a better icon too. I don't think the current one is very good for "zip," especially since there is a pretty cohesive icon design language out there for Zip already.
bkensey said:
Fair enough. I'll switch the label over for the next update. I'll look at a better icon too. I don't think the current one is very good for "zip," especially since there is a pretty cohesive icon design language out there for Zip already.
Click to expand...
Click to collapse
Yeah. Just the icon. Looks like Gmail archive as u said
Looking really good, I will be following closely, once it has root stuff I will swap from root explorer in a heartbeat, actually, I will install it, and let you know what I normally can do with root explorer but is missing from this, as I am not 100% sure what you need root access todo.
Main root (I think?) stuff I do:
Accessing the root dir, messing with system files permissions, and pasting apks into the system dirs.
This might become my primary file tool once it gains root powers. Looking very great.
-Root with mount system as writable and change permissions;
-LAN/FTP;
-Dropbox.
With these Holo File Explorer would have no rival. Would be PERFECT!
Looks really nice, but unfortunately it shows only the LOST.DIR folder from my sd, nothing additional.
Running a desire s with cm9.

[ROM][ICS:CM9/JB:CM10 hybrid]ParanoidAndroid 1.5/2.10[1Jul/08Sep2012]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*Screenshot 1: SystemUI.apk in TabletUI/230DPI, Launcher PhoneUI/320DPI, System running in 320DPI
*Screenshot 2: SystemUI.apk in PhabletUI/220DPI, Launcher PhoneUI/320DPI, System running in 320DPI
*Screenshot 3: SystemUI.apk in PhoneUI/320DPI, Launcher PhoneUI/320DPI, System running in 320DPI
Find any combination you like, scale and project apps, widgets and system components! Modes and DPI will differ for the Epic.
To be honest, this is not tablet mode at all, it has nothing to do with silly build.prop hacks. This is the first and only Android rom to feature true Hybrid mode. This rom lets you scale and project every app, every widget, even systemcomponents individually. Remember, android is modular, everything is an app: Lockscreen, navigationbar, dialogs, popups, keyboards, widgets, and your regular apps of course. Apps have the capability to switch into various designs or layouts according to the device they run on. This can result in a complete new experience as many apps will transform to the better.
Now for every element that you like chose a mode (PhoneUI, Phablet/Nexus-7UI, TabletUI) and/or a size. You are 100% independent of the system DPI which runs nicely in whatever value it has been assigned to. You do not need to boot your phone into a certain DPI. Neither will most of the changes you apply require a reboot. You will not suffer from the myriads of troubles which normally haunt you under build.prop tablet mode. Your market, phone, etc. will all work, apps won't shrink on you unless you shrink them yourself. This project will entirely transform your device, but retain the aesthetics and the feel of your phone.
Donations to molesarecoming
to D4rKn3sSyS
to Cyanogenmod
​
CWM: PA 1.7 onwards needs no Wipe Cache / Factory Reset, everything else does!
CWM: Install Zip: Rom: Download
md5sum is ce08fbb97b572fead0f90713defecaf9
CWM: Install Zip: Gapps: Download Or your preferred Gapps.
CWM: Wipe Cache Partition
CWM: Advanced/Wipe Dalvik Cache
OPTIONAL http://forum.xda-developers.com/showthread.php?t=1842037 Install a kernel with Nexus S 4G support, reported major increases in 3g speed and call reliability. Please note what kernel you are using, if you go this route and experience issues.
Reboot and edit your Apps Dpi & Layout under Settings/Paranoid Settings
If you want to explore the various phone modes, tap "Configuration," chose an option, wait for it to finish, then do a manual reboot
Video tutorial: http://www.youtube.com/watch?v=72Ow-YQeex4
Our webpage: http://www.paranoid-rom.com/
You want to port PA? Take a look here: http://forum.xda-developers.com/showthread.php?p=27558806
Themes and other goodies you can find here: http://forum.xda-developers.com/showthread.php?t=1646034
Go to Settings, System, Font size, set it to NORMAL
Check "Auto Hide" in Settings, System, Statusbar, to finally get Fullscreen
If you have an issue and you want to call our attention, here's what you do:
1. Try everything you can, find solutions for yourself. Wipe caches, revert all your settings you have made, go back to your stock Kernel, factory reset if you have to or reflash the rom. Assume that the issue is on your side and try your best to isolate it.
2. Search this thread and Cyanogenmods aswell (its our base) for possible reoccurences of your issue and hopefully solutions that may have come up.
3. If you think the issue is important enough that we should cease our work and look into it, post your issue, BUT ...
... stay friendly, do not demand anything, do not threaten
... explain your issue as precise as you can, name the exact apps and conditions that cause trouble, help us to replicate the issue right away. If we can't there's no way we can fix it and your post will simply clutter the thread
... collect evidence, keep in mind this is a developer thread so even if you are not one, do us the favor and research how to record logcat. logcat is the single most important help you can give us to resolve your issue.
ParanoidAndroid team sources
Tina: http://krebsmilk.de/
Cyanogenmod Team sources
EpicCM Team Donate
Marcusant- hosting/CM10 preview help
Xboxfanj- CM10 preview help/early porting help, Nexus S modem support
Epicnoob- help with early porting
All the help I've had with this thread along the way, and those of you who suffered through the rough versions with me
CM9/ICS based for the less bold
Flash CM9 first, let it boot, then dirty flash this...
http://marcusant.com/sgtkwol/PARANOIDANDROID-epicmtd-1.5a-30JUN2012-1400.zip
Flash this Gapps http://4ndr01d.com/drcmda/common/
My github, merging CM9 release source with PA/ICS source https://github.com/sgtkwol If you wish to continue this work, have at it. I personally feel that the JB base is the best place to concentrate efforts.
20120810v1.9.8alpha
Project butter recents in tabUI (2/2)
Quick access hybrid properties by longpressing a recent app
More refined hybrid algorithm to reveal more layout containers
TabletUI toggles
All recent cm merges (Trebuchet, googles 4.1.1 r4 with a whole bunch of fixes for memory leaks, etc)
20120806v1.9.7alpha
New option: "large" to trick an app thinking the device has a real big screen. some need it, like amazon kindle to jump into tabUI. some even react on it, gdrive will slightly adapt its layout - makes only sense if you give it a small dpi though.
The algorithm to extract the actual layout containers from apk files works more precise and can reveal more than before. there will still be a few apps left who do that layout stuff in java - we will add an override button for that, but in the meantime you can edit /system/etc/paranoid/properties.conf .layout=360 for phone-like UI, 600 for phablet, 720 = tablet, 1280 = super huge tablet
Several bugfixes from us and cm
20120805v1.9.6alpha
Breakthrough: We can finally target the actual layout containers inside the apk. If an app brings only phoneUI, you see it right away as you only have one UI option. If it brings ten, you will be able to pick each one of em. We're finally away from this Phone/Phab/Tab nonsense.
Total Hybrid engine revamp, alot less clutter, many bugfixes, apps wont make jumps when you load them up because their actual size is calculated by the engine.
Panel is still growing. It brings new options and new preferences that can even change android system settings.
All recent cm10 patches and fixes
20120801v1.95alpha
Finally hardware accelerated recents in TabUI, as fluid as ever. The ugly gradient is gone aswell
Paranoid got its own dir in /system/etc/paranoid - pad.prop is not properties.conf
A clean backup properties file is shipped, you can make a full reset in the panel in case you lost it with all the settings you made
Force option can be activated in the panel, good for widget scaling
The DPI sliders in the panel read min/max props from properties.conf, define them as you like
TabUI Recents are back to a bigger size, this is temporary, i'll look for ways to port the phone implementation as project butter skipped the tabUI code
CM fixed alot of features again, we included them all
20120730v1.9.2-4alpha
Keeping up with CM10
Bugfixes
More descriptions and images in the panel
20120725v1.9.1alpha
Hybrid bugfix, finally keyboard/facebook scaling works on JB again without sideeffects
Layout fix for notificationcenter gap in tabUI
Layout fix for recents in phabUI
Speed prefs ask for reboot
New bootani thx to nasaorc
CM10 patches
20120722v1.9alpha
Newest CM10 patches (powertoggles for phoneUI, lockscreen options, etc,)
Definable number of notifications for navbar shaping
Hide clock wont cut it out of the notification center aswell
Lockscreen tutorial overlap *should* be fixed
Notificationcenter in TabUI has a draghandle like phablet and phone have
New gapps
20120719v1.8alpha
Bluetooth was not working in 1.6, now it does
Selection in landscape was botched, now it isn't
Hide statusbar/navbar is back
A whole bunch of CM features and powermenu options
Corrected the way JB displays sw720 TabUI apps (it wasted almost 40% of the screen with margins)
Dreadful CM-default ringtones are out
Some other stuff i cant remember right now
20120717v1.7alpha
SysUI bugfixes, all three modes work by simply dropping it into a mode, no more navbar height issues
Recents/menu merge
ParanoidPreferences panel, barebones stripped down version, no bug reports please, we know its not stable yet
new bootanimation, thx nasaorc
20120712v1.6prealpha
JELLYBEAN
New hybrid codebase, won't touch build.prop and changign build.prop wont ever be necessary
Can drop apps and system into three modes: Tablet, Phablet and PhoneUI
It is VERY raw and basically a preview. Much code has to be merged, the framework will have to be adjusted as JB introduces crazy overlappings again, just like ICS did
There will be no panel to control it, you can take an editor and edit /system/pad.prop yourself in the meantime.
Expect updates soon
20120625v1.5beta
Hybrid speedup, less lag, considerably faster list scrolling when pad/pal is in action
Keyboard scaling, an androids first
PAD/PAL bugfixes for apps that still crop images in lower dpis
Settings revamp, speed preferences to switch between modes without having to set up anything, less clutter
Trebuchet extras: 3x4 widgets, speed dial menu button, ... and some weird rocket button which im sure will be very useful to most of you
Pad.prop revamp, new preferences that should pretty much nail it. Im sorry but this trashes your old settings again, do not attempt to restore them unless you do it in a text editor
A warning: if you need to scale keyboards, do close their hosts first (that is, if you have the keyboard running in chrome, close chrome, then attempt to change the size). Otherwise you run into caching problems. Also not that some keyboards use fixed layouts and others dont. Should one of your keyboards not scale, just leave it at PhoneUI/DPI and be happy about those that do scale.
20120618v1.4beta
New Hybrid code, keyboard troubles should be gone, apps that crop images or display weird, that should be gone aswell
PAD/PAL work in phonemode 100%, no weird toggles and stuff like that. you get full tablet apps without caveats
Settings cleanup, most of the garbage dpi options are gone, should be more intuitive - i ask you to not bring your old pad.props though some things changed. if you know what you do take a look and edit by hand
Trashed our LatinIME repo - not needed anymore
20120615v1.3beta
Navigationbuttons in phone mode are fixed
Franco kernel smashed games, storage, bootmanager - i switched to cm's default kernel
Settings panel had a bug, you couldnt set android.dpi, decriptions sucked, too
Speed improvements, all launchers are buttersmooth now
Force option for widget scaling works again
20120614v1.2beta
Compiled from a unified GIT that is shared by a growing number of devices
Has all the latest CM9 additions
Completely revamped hybrid code-base, should be better overall
New PAD/PAL code allows system-scaling finally, that means you can scale the lockscreen, dialogs, toasts, etc.
Trebuchet comes with new menu options: 4x4 grid grid folders, options for backgrounds, tablet effects
New cool backup app for pad.prop, *maybe* even an OTA app, either 1.2 or 1.3
New panel options and descriptions
Hide status-bar clock doesnt hide HOLO clock in notification center
Number of notification icons definable in settings
Tons of fixes and improvements
20120530v1.1beta
.Force option that allows apps to push their custom DPI through hosts, this effectively allows to scale widgets again, only this time without breaking anything
Menu button has been merged with recents button. Three dots will appear if an old gingerbread app needs it, longpress it to access the menu. This will allow more notification symbols in future releases
New option to scale navigationbar without reboot
Trebuchet has been forked again, this will be the smoothest launcher you have ever tried. its projected into phoneUI but it brings all the cool tablet features like tab controls in the corners and those cool blue outlines when you scroll homescreens. Try the effects, rotate_down is awesome!
Fixed ICS standard keyboard, no cutoff anymore
All you toggle lovers, todays your day. customize them in settings/system/notification drawer
Dynamic prop values that work in phone and tablet UI
More descriptive captions and settings
CM is turning into such a beast, you'll find tons of new goodies, especially in phoneUI
20120521v0.9beta: P.A.L., PROBABLY THE MOST AWESOME FEATURE EVER
First time in Android history that Per-App-Layout has been realized
Comes with a better panel
Allows you to switch between Phone mode (with curtain and bear paw buttons) and tablet UI seamlessly. PAD & PAL work in both domains. That means you can have 3d Youtube in 320 dpi standard Phone mode or mobile Chrome without those horrible tabs in 192 Dpi Tablet mode.
Since PAL solved all scaling issues our Trebuchet fork is now obsolete. It comes with Nova 1.1.4 projected into mobile layout.
20120517v0.6beta: Bugfixes, new PAD panel, Fullscreen-toggle
Fresh cm9 repo
Franco Milestone 3
Bugfixes for PAD preventing it from screwing up some apps (notification icons were bigger for some apps, launchers would display icons bigger or smaller, etc.)
New PAD panel, lists DPI's, can delete values again
Powermenu Fullscreen-toggle, this finally allows you to play games without navigationbar!
20120512v0.5beta: Control per-app-density via Settings Panel!
Fresh cm9 repo, build IMM76I + non broken theming engine
Franco Milestone 3
Several fixes for p-a-d
Settings Panel, its the one with a droids eye. Still in the making but a start - /system/pad.prop is still there if you need it
20120505v0.4preview-add-on: Apps were too small? Problem solved!
Define the scale of your apps, system-apps, framework-components and even widgets in /system/pad.prop
31 character limitation gone
No Reboot required, restart your app and it should pick up fresh values
Also contains a hacked version of Google Talk, messages use up the full screen now, you don't get these awful stretched message windows anymore
20120504v0.4preview: Apps were too small? Problem solved!
First ever Android ROM with Per-App-Density feature, it once and for all solves the problem that was tablet mode. You never, ever have to deal with apps that are too small again since now you can decide how apps, systemapps, framework-elements and even widgets are scaled by defining their native dpi seperately from the system DPI. Its an experimental feature and for now these values are defined in your /system/build.prop - it has drawbacks (maily notifications can look a bit strange), but that will be fixed in time. Warning: Keyboards MUST run in system DPI!
A list of apps and predefined values is included, this should include most of what you need. everything else is blown up to 210 dpi per standard. if you still need apps to be bigger, get a build.prop editor from the market, edit and reboot.
Trebuchet fixes: Folder Name cut-off, landscape name cut-off, divider bars
Please set your Font to "Normal" in the System Settings, you won't need "Huge" anymore and all this does now is provoke overlapping.
20120430v0.3alpha:
Freshest CM9 Repo
Forked Trebuchet and rewrote its layout and parts of its code to adapt it to tablet mode. I went for stock look plus tablet controls and changed the number of icons/widgets shown in the drawer. It's butter-smooth aswell. It has kinks left, those will be solved in the coming days!
100% fixed android standard keyboard
Better Bootanimation
Fixed Gapps package based on 20120429 including Gmail and a working Market
20120427v0.2pre-alpha-gapps:
Fixed Gapps package based on 20120422 including Gmail and a working Market
20120427v0.2pre-alpha:
PARANOIDANDROID custom bootanimation, still has some kinks - first sketch though
crystall clear thumbnails in the recents window, pixel mush no more!
brightness setting easier accessable
ICS toggle button fixes
20120425v0.1pre-alpha:
freshest CM9/nightly repo build (25/04)
recents window way nicer than before. close to stock. i only need to get rid of that darn gradient
keyboard looks like stock now
new bootanimation
camera works
comes with cm9 repo kernel, no color tint
notification clock is smaller, won't overlap so easy
20120425v0.0pre-alpha:
freshest CM9/nightly repo build set to tablet mode
Hacked Nova. I know 1.1 is out, but this one is still closer to stock
Androids keyboard reacts hellish in tablet mode. I fixed it but its still too large, tomorrow i'll fix it proper
I was trying make to recents window look more like stock. COULD be the thumbnails are a tad bigger than before but i'll get to that don't worry
2 notifications icons max in portrait for now to prevent overlapping
Settings comes as the first item in the notification panel, hated to scroll down every time
ALOT will follow, please be patient, i made all that stuff blind because it needed ~13 hours to compile. now compiling is alot faster and i'll see to it that we will have true hybrid mode very soon
First-ish
iSaint and such
Sweet. Still running ur build from the kang thread n it rocks. Got themes to work now too. I think it may have been the particular themes I was trying to use. Good to see you're working on this, pa looks dope.
Sent from my SPH-D700 using xda premium
really? yeahhh
It looks promising! Can't hardly wait for a full Rom to test it out...keep up the great work!
Great Job! Haven't run the ROM yet, but I plan to. My suggestion to fix carrier name is open up system/framework/framework-res.apk of both paranoid and cm9 with your archiver and navigate to res/xml in both. Then drag and drop eri.xml from cm9 to paranoid and then save that and keep going back out to system until it asks you if you want to save. Say yes and that should fix the issue.
Thanks for bringing this to our epics!!!
Sent from my SPH-D700 using Tapatalk 2
COOL ... looking forward to trying this out
Anyone got this working yet? Install fails for me. Tried 4 different downloads, 2 from my desktop, 2 from phone , TWRP and CWM.... So sad...
Sent from my Galaxy Nexus using xda premium
Shermanballz said:
Anyone got this working yet? Install fails for me. Tried 4 different downloads, 2 from my desktop, 2 from phone , TWRP and CWM.... So sad...
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Anyone else with this issue? I might need to switch up to Dropbox or something else for distribution. I'll have a couple of sources and MD5 checksum for the next release.
sgtkwol said:
Anyone else with this issue? I might need to switch up to Dropbox or something else for distribution. I'll have a couple of sources and MD5 checksum for the next release.
Click to expand...
Click to collapse
I did.
sgtkwol said:
Anyone else with this issue? I might need to switch up to Dropbox or something else for distribution. I'll have a couple of sources and MD5 checksum for the next release.
Click to expand...
Click to collapse
Devhost bud
Sent From My Sprint Galaxy Nexus
I can't wait to try this.
sgtkwol said:
Anyone else with this issue? I might need to switch up to Dropbox or something else for distribution. I'll have a couple of sources and MD5 checksum for the next release.
Click to expand...
Click to collapse
I'll pm you in a sec
YES! Downloaded from DevHost.
Thanks!
IT'S FLASHINGGGGG
PARANOIDANDROID-epicmtd-1.4a-21JUN2012-0000 posted on OP, make sure you back up your pap.prop with ParanoidAndroid Backup before flashing.
Bug fixes:
service provider tag works
about phone works
Trebuchet works in landscape
better hosting
Generally, everything works. Mostly visual cleanup needed. Going to get the OP set up with the PA format tomorrow.
sgtkwol said:
PARANOIDANDROID-epicmtd-1.4a-21JUN2012-0000 posted on OP, make sure you back up your pap.prop with ParanoidAndroid Backup before flashing.
Bug fixes:
service provider tag works
about phone works
Trebuchet works in landscape
better hosting
Generally, everything works. Mostly visual cleanup needed. Going to get the OP set up with the PA format tomorrow.
Click to expand...
Click to collapse
We're in 2012 lol. Your title says u made this a year ago lol.
Sent from my SPH-D700 using XDA App
does the charging light work?
Sent from my SPH-D700 using XDA
Any screenshots? What exactly is this? Not a lot of info in the OP really describing it and I've never heard of it.
Sent from my SPH-D700 CM9 ANDROID 4.0.4
Zeinzu said:
Any screenshots? What exactly is this? Not a lot of info in the OP really describing it and I've never heard of it.
Sent from my SPH-D700 CM9 ANDROID 4.0.4
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1712910
Sent From My Sprint Galaxy Nexus

[GUIDE][PARANOIDANDROID] A Complete Compendium on ParanoidPreferences [PA-Settings]

WELCOME TO PARANOIDANDROID
Noob's Guide to PA Settings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Integrated somewhere deep within the ParanoidAndroid source, is a Hybrid Engine. The Engine that makes PA stand out of the crowd. The feature of Per-App-Density & Per-App-Layout. (PAD & PAL)
Now, it has expanded beyond, & offers independent customization of even more visual elements, such as Lockscreen, Widgets, StatusBar/NavBar etc.
The Hybrid Engine, is the source that powers it all. But to implement it we need something much more simpler, something that allows High-Level Control.
This is where ParanoidPreferences app comes in. (Abbv: PAPref)
This handy app interacts with the Configuration files, & allows to control any & all elements easily.
This guide for those who might need it. The App in itself is pretty self-explanatory, but to make it easier to understand, I've made a visual guide, explaining each & every part of the app in detail.
Feel free to ask any questions that you might have
--------------------Jargons--------------------​
You might come across some terms that are commonly used across the app, & all over the threads & blogs.
I'll try to explain them briefly.
DPI: Dots Per Inch. As the name defines, DPI is the number of dots per inch of a screen.
In PA, we can modify DPI of any & every app or service independently (PAD).
Lower DPI value, would cause a general shrinkage, & higher DPI value, would cause the app to get bigger.
In general, we have a few standard DPI values:
xHDPI: 320 DPI | HDPI: 240 DPI | MDPI: 160 DPI | LDPI: 120 DPI
DP: DP, or DIP, is Device Independent Pixel.
On an Android device of 160 DPI screen,
Code:
1dp = 1px (pixel)
Hence, for a 320 DPI screen,
Code:
1dp= 1/2 px
& so on.
DP (or px) can be used to customize the layout of the app used. PAL is where we make changes in px of any app or service, & change its layout to Phone/Phablet/Tablet or any custom layout (wherever applicable).
We use some standard px values as: 360px: Phone Mode | 600px: Phablet Mode | 720px: Tablet Mode
NOTE: The examples used below & in all subsequent posts is of a screen with standard 320 DPI (xHDPI). Some values might differ for other standard DPI screens, but the theory remains same.
To access the ParanoidAndroid Settings, Navigate to Settings -> ParanoidSettings
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--Move on to Post 2--
This is the main Interface of PAPref.
Lets explore the sub-menus in detail:​
1)
2)
3)
4)
5)
For educational purpose, I'm selecting a random app, say 'GMail', to explain the available customization option to the users:​
1)
2)
3)
4)
​
Example results of GMail modification:​
The result of modifying Lockscreen Size:​
PS: And no. Changing DPI does NOT change the time on the lockscreen.
The 3 standard Workspace UIs:​
CREDITS:
molesarecoming
D4rKn3sSyS
First
Nice guide as always goku :good:
I will link it in my builds' thread, and I think every maintainer should do so
great guide
i was wondering if its possible to have a paranoid gb? my device already has ics and jb, but not gingerbread, which is the most stable, so im not sure if its possible
i changed Paranoid settings for some apps Layout to 360Px and Phone Mod successfully but after rebooting device except Home Screen every other app and settings menu screen dimensions out from top and bottom :s after which i changed those settings again but unable to change DPI from 0 to anyother value then reboot but no effect so kindly guide me how to resolve this issue.
HTC DESIRE
rashidshahzad said:
i changed Paranoid settings for some apps Layout to 360Px and Phone Mod successfully but after rebooting device except Home Screen every other app and settings menu screen dimensions out from top and bottom :s after which i changed those settings again but unable to change DPI from 0 to anyother value then reboot but no effect so kindly guide me how to resolve this issue.
HTC DESIRE
Click to expand...
Click to collapse
always compile paranoidandroid with . rom-build.sh devicename, or tell your dev to do that. make/lunch/brunch will not result in a functional rom. when youre done, try not to change your build.prop, the script does all that for you.
another thing is, hybrid engine needs a healthy system DPI. if you go and change ro.blabla.density it will simply shut down and refuse to work. this ones actually strange because i have seen many people so hung up on build.prop dpi they just cant stop themselves - hybrid engine can do all that regular tablet mode could in the past, even dropping all your apps into tabUI at once if you so desire - it does that without harming your system though (read, not changing the system dpi).
if its stillnot working then it can be fingerprint and signing issues. in that case only a fullwipe helps. when the rom is built clean from the beginning though all will work right out of the box, issues like that are born from wrong compiling.
Default size Default UI
Hi,
I am new to Paranoid Android but that hasn't stopped me from recognizing the innumerable possibilities it offers. I have a galaxy nexus International version and I was experimenting with almost everything, As you said, the Hybrid Engine needs a healthy UI rather than just any random number. Hence my launcher went into a crashloop upon changing orientation.
Another thing I would like to know is the basic difference between the System App Default Size and Default UI.
Also what are the safe values for the Galaxy Nexus.
What if I want to reset everything back to normal? I tried doing that through the given option but certain values remain overridden. Will I have to perform a full wipe?
molesarecoming said:
always compile paranoidandroid with . rom-build.sh devicename, or tell your dev to do that. make/lunch/brunch will not result in a functional rom. when youre done, try not to change your build.prop, the script does all that for you.
another thing is, hybrid engine needs a healthy system DPI. if you go and change ro.blabla.density it will simply shut down and refuse to work. this ones actually strange because i have seen many people so hung up on build.prop dpi they just cant stop themselves - hybrid engine can do all that regular tablet mode could in the past, even dropping all your apps into tabUI at once if you so desire - it does that without harming your system though (read, not changing the system dpi).
if its stillnot working then it can be fingerprint and signing issues. in that case only a fullwipe helps. when the rom is built clean from the beginning though all will work right out of the box, issues like that are born from wrong compiling.
Click to expand...
Click to collapse
Thanks for your reply but all above is very technical information can u please guide me that except full wipe how can i restore to noram phone mod and laso please check attached screenshot for better understanding of the current status of the issue.
YouTube app can't go any higher than 600px without crash
Hi
Thanks for the guide.
However, something disturbes me a bit when I use my Nexus 7 tablet. I have seen all those cool reviews with the YouTube app in tablet mode 800px-1200px, but mine can firstly only go to 800px - and when I choose it or 720px, it crashes!
600px is the only one I can choose - the phone app, which kinda sucks.
Can someone help me?
Nice guide Bidyut! Will help many first timer PA users!
Orr.Penn.18 said:
Nice guide Bidyut! Will help many first timer PA users!
Click to expand...
Click to collapse
Being a first time PA user - this did help me a lot and I am quickly realizing just how powerful this hybrid engine is.
I appreciate the examples of how changing UI settings per app can change the layout (gmail, youtube).
Is there an ongoing list of apps that are affected by particular layout settings AND what the "recommended" or common UI settings per app are?
Thanks!
Try this
Ham duden said:
Hi
Thanks for the guide.
However, something disturbes me a bit when I use my Nexus 7 tablet. I have seen all those cool reviews with the YouTube app in tablet mode 800px-1200px, but mine can firstly only go to 800px - and when I choose it or 720px, it crashes!
600px is the only one I can choose - the phone app, which kinda sucks.
Can someone help me?
Click to expand...
Click to collapse
Hey! i had the same issue and I know how frustrating it was. Here's what to do. Go to Settings;Paranoid settings;INTERFACE...and on the right hand side you'll see:- Workspace UI, System Apps UI, User Apps default UI,...all of them being "Phone Mode". You have to change the last one, "User Apps Default UI" to TABLET MODE and reboot. Voila! Youtube in 3d!!
rashidshahzad said:
i changed Paranoid settings for some apps Layout to 360Px and Phone Mod successfully but after rebooting device except Home Screen every other app and settings menu screen dimensions out from top and bottom :s after which i changed those settings again but unable to change DPI from 0 to anyother value then reboot but no effect so kindly guide me how to resolve this issue.
HTC DESIRE
Click to expand...
Click to collapse
having the exact same issue on 2.54 ! :S
Was ok on 5.52 !? why ?!
if anybody can tell !
Thx
Hello, I love this ROM but I am trying to fine tune a little. I have everything in tablet mode, which works very well for me and I have my System apps default size DPI set to 196. This makes the icons a good size and fits them nicely on the screen but, I am not able to take advantage of all of the usable space on the screen. There is area at the top and bottom that I am unable to use, how can I maximize the space of the entire screen in tablet mode?
I've attached a pic to show the range of where I am allowed to place apps. There is a whole unused space at the top and bottom.
Great, great guide...
A must read to all who uses this rom.

[ROM][KK 4.4.4] [ KatKiss-KitKat #036 ] [Stable] [MultiWindow]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
KatKiss ROM - Asus TF101
​KitKat 4.4.4​MultiWindow + Floating & Resizable Windows​
This rom is an aosp based rom with my own additions on top.
The main motto of the rom being Kiss. Even though the Meerkat could give you a kiss, it stands for Keeps it Sweet and Simple too
Which means that just like the other K.A.T stuff, the rom's main goal is efficiency, speed/responsiveness,
while not adding bloated features that will slow things down
​
DOWNLOADS:
Latest Dev Version:KatKiss-4.4.4_036.zip | Mirror1 | Mirror2
Latest Stable Version: KatKiss-4.4.4_036.zip
Latest NonLinaro Version: KatKiss-4.4.4_036-NonLinaro.zip (Slower but higher compatibility with some apps & games ...)
SL101 AddOn Compatibility Pack: KatKiss-4.4.4-sl101-compat-V7.zip | Older Versions (to flash after the rom & after rebooting once into the rom)
To get both Hardware & Software keyboard, deactivate asusec in settings.
TF101G AddOn Kernel: KatKiss-4.4_AddOn_TF101G_Kernel_01.zip (default rom kernel tends to reboot with TF101G this one is not as fast but more stable)
You then need to use PPPWidget for 3G connection.
Right Click Behavior Change: 4.4.3_RightClick.zip (default rom behavior is to send the back command, if you want it to send right click, flash this)
FSYNC: fsync_on.zip (fsync is off by default in the rom, if you want it on just flash this after the rom)
fsync off will make i/o run faster, but in case your tablet reboots or shutdown unexpectedly you might lose data more often than with fsync on.
So if your tablet tends to be unstable /reboots, if you overclock too much or that you tend to let it run out of battery, you might be better to turn fsync back on
Latest Gapps Package: gapps-KatKiss-4.4.4_20140913.zip | Mirror1
Google Home Launcher (optional): gapps-GoogleLauncher_20140110.zip
Please note that this version is made for and tested on the TF101 model.
As to not clutter the thread, no support will be given here for other devices​
ChangeLog: http://public.timduru.org/Android/KatKiss/4.4/ChangeLog.html
Source: https://github.com/timduru (branch katkiss-4.4)
--
Main Features:
Rooted
Floating & Multiwindow support (see post #3)
High speed and responsive oriented
High performance and overclockable KatKernel included see dedicated KatKernel thread for more info
Built with Linaro GCC 4.8.3, -O3, strict-aliasing, c++11...
Hardware accelerated video & Camera support
Full Dock keyboard Support with special keys with additional CTRL + Menu shortcut for recents apps
Global Keyboard Shortcuts / KeyOverride Macro association (See post #2 for more info)
Battery Level Indicator & Dock Battery support + Mods (icon/Text/%)
HDMI out options: center, crop, scale
CIFS, ext4, NTFS & Exfat support
Native 4.3 FSTRIM + Manual scripts for Database optimization and fstrim (see post #2)
Media Scanner Filters
Advanced per application permission management (AppOps)
Advanced power menu with reboot options.
Expanded Desktop with the option to hide only the NavBar
Choice between PhabletUI with left or middle aligned nav buttons, and multiple NavBar height.
Trebuchet
Wifi channels regulatory domains
Integrated cpu & io performance settings panel
Custom Navbars buttons long press actions
Ethernet support with settings panel
Custom Quick Settings tiles
ART
Installation Notes:
These builds are designed to be installed from your favorite recovery. MAKE SURE TO INSTALL A COMPATIBLE ANDROID 4.2/4.3 RECOVERY!
TWRP >= 2.3.2.3 is recommended, new TWRP available here
Backup everything !
Go to recovery
[*]Make a full wipe / factory reset (you can skip this step if you're already on KatKiss-4.4, if ever you encounter a problem do the full wipe and try again before reporting )
Format /system (only if Version<026)
Flash the rom
Flash KatKiss gapps
Wipe cache/dalvik
Reboot
Credits:
Thanks to the original TeamEos, Cyanogenmod & Omni for the work on their roms, Banks, Guillaume Lesniak, jteagle, MWisBest, D4rKn3sSyS and Yanuar Harry.
YebYen for the mirror.
Original banner concept by i9apps, Bootanimation by mgeniusm, original drawing by BBF
WebPage
Tips
How to report
What to include in the report
Disclaimer: The usual
Use at your own risk, I won't be responsible for any damages caused to your Transformer or to yourself.
In most cases if something breaks, flashing a rom on top should fix it.
​
XDA:DevDB Information
KatKiss-KitKat, ROM for the Asus Eee Pad Transformer
Contributors
timduru
Source Code: https://github.com/timduru
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 2.6.x
Version Information
Status: Stable
Created 2014-01-01
Last Updated 2014-12-21
Additional info & links
Youtube
Latest youtube will work ok with res < 720p.
720p might work if autoselected directly, but will most likely fail / stutter.
Using an older version of Youtube like 5.0.21 fixes these issues.
Flash & HTML5 Video
Flash is not supported by default on KitKat, you can still use it with Dolphin Dolphin Browser:
Install Dolphin Browser, install or activate Dolphin JetPack in settings, install the latest flash plugin.
HTML5 video will only play full screen in the default browser & other browsers using the default webview.
If Chrome crashes on playing the video, try the beta or another older version(29.x)
Skype Calling
Version 5.x broke calling support.
If you need calls, you have to use an older version like 4.9.0.45564
http://skype.en.uptodown.com/android/old
Plant vs Zombies - Black Screen
Game issue seems to be related to different roms / devices with 1280x800 resolution.
Workaround to avoid the black screen after launch:
- install NOMone Resolution changer
- change resolution to 1280x768 160 dpi
- click apply
- launch game
After playing, restore resolution .
Wallpaper Modes:
Different Wallpaper modes have been added in Settings => Display
** Normal (regular android mode)
** Disable System Wallpaper rendering (set as default)
** Disable Wallpaper service
2nd setting will prevent the wallpaper being rendered by the system (system rendering is not good with the asus graphic hal) and also freeing resources
That's the recommended setting you want to use if you are using a launcher that has internal wallpaper rendering
You will see a black wallpaper if you're not using a launcher that can do internal rendering
If wallpaper is important and that you want to keep your current launcher, then switch back to the 1st setting
same if you want wallpaper to display on the lock screen.
3rd setting disables wallpaper completely, depending on your launcher it might be better.
Global Key Override/Shorcut Mecanism
Available in Settings => Language & Input => Add Key Override Actions
or in Dock Settings
This will allow you not only to redefine function keys assignment, and other special keys actions,
but you'll also be able to assign global macro actions / app launch to any key + Meta key combination (shift Left or Right , ctrl..)
You can also add multiple actions to one key combination, simply click again on the "+" button for the same key combination.
For example if you want to assign to one key combination a list of action to run before going to bed for example, like: turn wifi off, bluetooth off, mute sound, and turn screen off, you can do that
Note that starting multiple applications with one key is kinda a miss and hit for the moment due to some mecanism in android that seems to prevent applications to start too close to each others.
Wifi channels:
Choose which channels are available based on your country in Settings => Wifi => Advanced => Change wifi regulatory domain
Google search:
If the version you're using is crashing when you open Google Now,
go to Settings => Language & Input => Voice Search
then uncheck Hotword Detection.
CIFS & 3rd party Mount Apps:
The Rom/Kernel have native support for them as long as you mount it outside or /storage/ and /mnt/shell/emulated/
GPS:
if it is taking a long time to get a lock or no lock, follow this:
Install the latest K.A.T app
Then follow precisely this procedure:
1) Location Settings
- Go to Settings => Location => turn OFF (top right switch)
- Turn it back ON
- Make sure you agree to let google access the location.
- Make sure the current selected mode is High accuracy
2) Launch the new K.A.T app
- make sure you grant it root access
- make sure you have internet access
- go to the install menu, Check the "Install GPS quicker fix + Assistance
- Click the Install button
- Make sure it says "Install Finished"
3) Reboot
4) Wait that it has finished booting and launching all the stuff you have starting at boot
5) Start your GPS app outside with a clear sky line, to speed things up stay in range of the wifi / internet connection.
Do not let the gps app loose focus when it is trying to get a fix.
Do not let your tablet sleep / turn off the screen either.
Doing that here, the first time and with a cold gps start, and even staying in my house,
I get a 6 sat fix within 30 seconds and 11 sat fix in 1min 15seconds.
From there subsequent fixes takes about 3 seconds to grab 7 sats and about 10 seconds to reach the 10-11 sat fix
(you still want to let it sit outside for a bit after the 1st fix, so that the ephemeris data gets consolidated and updated to help faster fix later on)
Hardware keyboard layouts
More languages have been added in the default asusec keyboard
Set the keyboard layout through Settings => Language & Input => asusec => setup keyboard layouts
These also allow live switching without reboot with ctrl + space
Window Animation Scale & Immersive mode:
If you want to be able to drop down from the top to display the status bar while in immersive mode,
the Window Animation Scale must be different than zero.
ART:
ART is not supported for the moment, if ever you tried it, to go back to a working state you can either:
- remove the file /data/property/persist.sys.dalvik.vm.lib + clean cache & dalvik-cache & reboot in your recovery
- or do a full wipe
Storage (fstrim) and Database optimization:
Fstrim is native in 4.3 and will happen in the background if your tablet is idle / sleeping and that your battery is > 70%
There is also a script to run it manually in the rom: /etc/kat/optimizestorage
To optimize the Database: /etc/kat/optimizedb
To run both, open a terminal and run:
su
/etc/kat/optimize
Be warned that the optimize storage can take from a few minutes to hours.
But the speed / lag will be greatly improved afterward
Slow downs & Battery drain after a full wipe ? :
Things to keep in mind after flashing with a full wipe:
- Media scanner will need to scan everything again, it can take from a few minutes to hours or days if you have a lot of medias or medias that it doesn't like.
During that process it'll use a lot of cpu and disk, and so can make things lag a bit and drain the battery until it's done.
You can use the Media Scanner filters to speed things up and make it scan only parts that are really containing your medias
- After a wipe, it wipes your battery stats, if you don't flash while you are with a 100% full battery, the battery stats will be inaccurate for a while until it learns again your battery capacity.
The battery can appear to drain faster because it doesn't know where your 100% is.
(see here for tips on how to speed up the learning process)
- Check that you don't have a rogue process eating cpu in the background. (run the top command)
- Check that you don't have a process keeping your tablet awake
Disabling ext4 journaling : :
This procedure will increase speed and responsiveness of the internal memory by disabling journaling
Disabling journaling will give a big speed/responsiveness increase especially on /data where writing occurs
but the risk of corruption in case of crashes, reboots, running out of battery... is also higher.
Make sure you have a backup handy and you understand what you are doing !
If you prefer to play it safe you can use the 2nd disabling zip, which will only disable on /system and /cache which don't contain user data
Corruption is unlikely to occur on /system as it's read only, and /cache is just volatile non user data, so you can simply just format it from recovery if ever something wrong happens.
To disable journaling on /system /cache /data download: dis_journaling.zip
To disable journaling only on /system and /cache : dis_journaling_system_cache_only.zip
To enable journaling back download: ena_journaling.zip
0) Put the zip on your microsd card
1) Boot into recovery
2) unmount everything but the microsd card (that means /system, /cache /data ... )
(the script will also try to unmount these, but better be safe in case the script doesn't succeeds)
3) flash zip
4) reboot
Note: Disabling journaling should only take a few seconds unless your filesystem is already dirty (fsck will take place before and after the journaling change)
Enabling journaling can take longer, especially on /data (mmcblk0p7)
Just be patient.
To disable journaling you will need to reflash the zip after you format /cache /data or /system (that means after installing the rom or after wiping cache if you do that after installing the rom)
Storage inversion(inverts microSD and internal storage) : :
This procedure will allow you to use your MicroSD as the internal /data partition (which means /data, /sdcard, /data/media ...)
So you can now have whatever extra space for "Android internal storage" you like (ie what your physical microSD size is)
And your old internal storage will be used as /storage/sdcard1/
Not that I care much about the extra space myself, but the good thing is that if you use a good MicroSD, things will also be much faster,
and for example it doesn't lag anymore when installing apps and such.
Make sure you understand what it means and what you are doing.
And backup everything first of course !
As reference:
Physical Internal partition is /dev/block/mmcblk0p7
Physical MicroSD partition is /dev/block/mmcblk1p1
These won't change, only the mount points are changing.
The commands can be typed directly from twrp command line thingie, or you can run them through adb
(just add adb shell in front of the command in that case)
One thing to note is that the standard recoveries don't know at all that your mount points are swapped, so it will still show them to you the "old non swapped way"
It won't know how to make a factory reset while retaining your data for example.
Sidneyk has made a specific TWRP version that will support inverted storage, make sure to use that one after you've inverted the storage if you want to wipe from recovery
(if you use it for this procedure, then adjust the commands accordingly)
The commands below are for the non inverted recovery.
1) Boot into TWRP (I use v2.3.2.3, it might differ if using another version)
2) WIPE MicroSD content (that means it will be empty afterwards)
unmount your microsd
Code:
/sbin/make_ext4fs /dev/block/mmcblk1p1
If you still need to transfer your data from the internal storage you can go to step 4) then come back later to do step 3) only
3) If you have transferred your data from your internal storage, you can format it too:
unmount /data and /sdcard
Code:
/sbin/make_ext4fs /dev/block/mmcblk0p7
remount /data
then
4)
Code:
/sbin/chmod -R 777 /data
5) Flash the KatKernel (JB4.4) for the rom marked with _invertstorage
6) Reboot.
Unless you transferred your old /data into your physical new microsd partition, it'll be like if you did a factory reset,
so you will just need to go through the setup again.
And of course, From now on your microsd must be inserted before booting up the system, and NEVER remove your microsd card while the system is running.
Enjoy the extra space & speed
MultiWindow + Floating & Resizable Windows
Multiwindow allows you to split the screen in 2 vertically (while in landscape) or horizontally, you can switch an app back and forth between multiwindow mode and regular mode while it's running.
Floating & Resizable window mode allows you to freely position the window and resize as many of them as you like.
(memory will be the limit though)
MultiWindow
NavBar:
- To switch between full screen and split View you can use the
NavBar Button
(It will lay apps alternatively in one SplitView spot then the other.)
- To change focus simply Tap on the app or use the
NavBar Button
Recents:
- Clicking on the app Thumbnail works as before and displays the app fullscreen
- Clicking on the app icon or the
icon will switch the app to splitview and lay it in "automode"
(If you use automode when an application was set in a SplitView slot it'll be recalled to that previous spot.)
- Clicking on the other icons will force the app to the 1st or 2nd SplitView slot.
Actions
Actions to switch the app between fullscreen / splitview, switch between the 2 most recent apps and to force the splitview slot have been added
so you can bind them to a key / key combination with the Global KeyOverride or long press action too.
Note: Most apps works ok in splitview mode, but some of them might not refresh correctly sometime.
Same when rotating the screen while in splitview mode.
To force a refresh simply tap the app or if you have 2 apps in split, just click twice on the switch to last app button:
Floating & Resizable Window
.
One Difference with the MultiWindow mode is that an app has to be relaunched to switch between Floating and non floating mode
(you can however maximize the app through the button to get it full screen and click on the minimize button to get it back to floating mode)
Also note that all apps might not behave correctly while put in floating mode, it kinda depends on the app.
To relaunch the Top Running application between floating and non floating mode, click on the new NavBar Button:
Long pressing on the button will show/hide all apps currently running into floating mode. (makes it easy to bring them back and forth as needed)
Global Actions have also been added so you can bind these 2 actions on other long pressing or Dock/Keyboard Key override in Settings
With these icons you can maximize the floating app to full screen , minimize it back to floating mode, and close it.
Using the menu button in the top left corner of the app, you can dock the app half size to the top,bottom,left,right side.
To move the app drag the top bar around, it will auto dock to the sides when you drop it close to them.
To resize an app freely, use 2 fingers pinch (like when you are zooming / unzooming) If the app is docked to the side, you need to undock it first by moving it away from the side.
To switch between apps you can also go through the recents screen, use alt right+tab, or the switch to previous app button.
Clicking on the app icon in the launcher will bring it foreground too. (same if you associated a run application shortcut to the keyboard for example)
Banners
​
Thanks. Happy new year.
Sent from my Nexus 4 using Tapatalk
Thanks for your work.
Can we expect every rom specific feature we had on jelly beans here? (once there's a stable version)
Choo Choo! Happy new year
Regards
Happy New Year!!!!! Thanks for this great new year present Tim, love the Meerkat master
Edit: Tim You are the most incredible person i've ever known. Installed ROM and everything (expect from the strike items) just works, i could not believe it. Thx Man, you ARE the greatest.
Sent from my Transformer TF101 using XDA Premium 4 mobile app
Will try as soon as I get home.
Happy new year!
thanks
Enviado desde mi Nexus 5 mediante Tapatalk
Happy New Year! Seems much faster for some things. Thanks for keeping it lean.
Really love the 4.2.2, big hope for KitKat with Art, I know Kat Master can do it
WOW finnally kitkatkis LOL
Fantastic! Working well here, looking forward to these updates! Great work
Sent from my GT-I8190 using Tapatalk
YayYouFixedIt said:
Happy New Year! Seems much faster for some things. Thanks for keeping it lean.
Click to expand...
Click to collapse
Yep it's already faster than 4.3 imho , which is good as I've not even put back all the optimization flags & linaro.
pemain cadangan said:
Really love the 4.2.2, big hope for KitKat with Art, I know Kat Master can do it
Click to expand...
Click to collapse
I'm currently facing a build setup issue with art I think, same with Bluetooth.
I already had that issue in 4.3 with bluetooth, that's why I got ShevT Bluetooth build in KK4.3
which uses the exact same code, so I know it's not the code itself that is the issue, but mostly my build environment for some reason.
and it might actually haave been the same kind of issue that got Office suite pro to crash in libskia in 4.3.
In KatKiss 4.4, my build setup generates a working libskia with Office suit pro at least,
so all those who have been wanting to use Office suit pro, you can in KatKissKitKat
But I'm still facing the same issue with Bluetooth, and with art it seems to be allergic to something in my build setup that gets it to crash for some reason.
I might have to try to install a new build setup or once I clean/ push things to github, see if ShevT's KatKiss build generates a functionnal art & bluetooth.
I'm pretty sure it will, as I've changed nothing in art source code, it's the pure aosp source.
I could also most likely use art & bt binaries from another rom as a workaround in the meantime too, as I KatKiss doesn't really require any modifications from those.
timduru said:
In KatKiss 4.4, my build setup generates a working libskia with Office suit pro at least,
so all those who have been wanting to use Office suit pro, you can in KatKissKitKat
Click to expand...
Click to collapse
Just finished the KK 4.4 upgrade: Office suite Pro works fine. Thank you Tim! Everything looks very nice in this update
New Year, New ROM!
Thanks a lot!
This rom in its current state is enough for my daily use, thanks tim
For you to notice a small drop in the battery life, you can disable adding new options google.
Sent from my Transformer TF101 using Tapatalk 4
Happy New Year Tim and thanks for the KitKat version of your famous KatKiss rom.
It is running very smooth and responsive on my TF101 B60. Everything I am actually using is working fine.
The only issue I recognised so far is the ability to boot into recovery. This doesn't work neither from the power menu option nor from e.g. Goo.im entry. The tablet always just reboots normally. Only working alternative was shutting it down and use the power and volume button.
Great work Tim and thanks for keeping our TF101 still alive! :good:
Guichinga said:
Happy New Year Tim and thanks for the KitKat version of your famous KatKiss rom.
It is running very smooth and responsive on my TF101 B60. Everything I am actually using is working fine.
The only issue I recognised so far is the ability to boot into recovery. This doesn't work neither from the power menu option nor from e.g. Goo.im entry. The tablet always just reboots normally. Only working alternative was shutting it down and use the power and volume button.
Great work Tim and thanks for keeping our TF101 still alive! :good:
Click to expand...
Click to collapse
Ah yep, forgot to add the recovery command back
It'll be fixed in the next version.
timduru said:
Yep it's already faster than 4.3 imho , which is good as I've not even put back all the optimization flags & linaro.
I'm currently facing a build setup issue with art I think, same with Bluetooth.
I already had that issue in 4.3 with bluetooth, that's why I got ShevT Bluetooth build in KK4.3
which uses the exact same code, so I know it's not the code itself that is the issue, but mostly my build environment for some reason.
and it might actually haave been the same kind of issue that got Office suite pro to crash in libskia in 4.3.
In KatKiss 4.4, my build setup generates a working libskia with Office suit pro at least,
so all those who have been wanting to use Office suit pro, you can in KatKissKitKat
But I'm still facing the same issue with Bluetooth, and with art it seems to be allergic to something in my build setup that gets it to crash for some reason.
I might have to try to install a new build setup or once I clean/ push things to github, see if ShevT's KatKiss build generates a functionnal art & bluetooth.
I'm pretty sure it will, as I've changed nothing in art source code, it's the pure aosp source.
I could also most likely use art & bt binaries from another rom as a workaround in the meantime too, as I KatKiss doesn't really require any modifications from those.
Click to expand...
Click to collapse
I've got OmniROM builds going on, as you probably already knew, and until yesterday when I brought in a cherry-pick to fix screen shots, I had made no changes to the base source code for 4.4.2. Only changes were in the device tree with mainly certain build flags in BoardConfig.mk (?) and a modified kernel config using your kernel source tree. I have nowhere near your experience or expertise with the coding side which is why I've tried to avoid changing anything there if I didn't have to. But, with my current setup, art seems to function very well, once enabled. I'm not noticing any reboots, crashes or otherwise that I wasn't seeing in the Dalvik mode, and maybe less, with a seemingly better performance (at least felt like it). That's not to say that everything else is working perfectly, just that art seems to work pretty well in OmniROM. Just sharing this to help you in your troubleshooting, not trying to hijack your thread. Good luck because I know you can do some magic for this machine.

Categories

Resources