Related
ok, so im running cm7(void # forever) on my optimus one with the latest market 3.4.4 & since something i tried out worked for me & my wife(running stock 2.3.4 on her samsung galaxy fit(GT-S5670)@100dpi) thought i should share this in case it helps.did not see it anywhere on xda when i searched so hoping that i did not post a already done topic in a new thread.
this is my first post so if i screw this up feel free to bash me
this is what u need to do step by step:
a)use root explorer or any other similar file explorer to go to the root of your device
b)scroll down to find the "system" directory & select to enter the folder
c)once inside remount system directory from read/only(r/o) to read/write(r/w)....(as shown in image 1 & 2)
d)scroll down to the build.prop file & long press for options and then select "open in text editor" (as shown in image 3 & 4)
e)once inside your build.prop,scroll down to find the line "ro.sf.lcd_density" (as shown in image 5)
f)my device has a default density of 160 and as you can see i changed it to 140 so go ahead & set the density you want for your device
g)now just save the changes & exit(image 6)
h)as you exit you will be notified that your original build.prop has been backed up to a file named "build.prop.bak" & you will find it right there in the system directory(image 7)
i did move this file out of the system directory & placed it on my sdcard!! didnt want any extra files or backups with the default settings in them just lying there you know!!!! just in case!!!! dont really know whether that matters any bit at all
now reboot your device & your dpi has changed. go into market & see if all the apps that are compatible with your device are still showing so.
note: the only catch is that apps(e.g ZIP Themer) that do not scale well will NOT,as the whole "compatibility mode on/off" option in LCD density changer app is ignored here. just gotta make your peace with that.
i attached some screenshots of the market showing apps in full & functional compatibility on my device running @ 140dpi
(UPDATE) Apps Installing despite market showing incompatibility
Ok, so my wife was fidgeting around in the market & she showed me something amazing. apps that should be compatible but are not can be still installed. apparently my precious hack was not 100% effective A few apps still showed incompatibility. But they can be installed too. Here's how you do it.
a)go to settings, select applications & then select manage applications.
b)find and select market & then select clear cache(trust me its needed)
Now you can go & search your desired app in the market
c)Choose the app and hit install before the whole app page loads,as in, the screenshots, reviews & details etc.
d)Choose accept & install and voila!!!!!!!!!!!!!!! You are installing an incompatible.
Attached some screenshots for proof!!!!!!!!!!!
This doesnt work anymore so if any of u wanna fix market compatibility issues please refer this link:
http://forum.xda-developers.com/showpost.php?p=20624277&postcount=13
its not my work so please thank the op for his efforts on this if & when it worls for u
If you have a rooted phone, you can change LCD density using nitrality app
available in the market.
JohnstonF said:
If you have a rooted phone, you can change LCD density using nitrality app
available in the market.
Click to expand...
Click to collapse
didnt know of it, thanks!!! but are market apps still compatible after you change the dpi settings on the new market?
I don't understand how this is a workaround. All that's done in OP is the dpi's changed in build.prop (which is what most apps/custom roms do anyway). Any apps that would be incompatible still are. Am I missing something?
synergye said:
I don't understand how this is a workaround. All that's done in OP is the dpi's changed in build.prop (which is what most apps/custom roms do anyway). Any apps that would be incompatible still are. Am I missing something?
Click to expand...
Click to collapse
i was talking about market apps that are compatible with a particular device becoming incompatible once you change your device's default display density to any other value.
synergye said:
I don't understand how this is a workaround. All that's done in OP is the dpi's changed in build.prop (which is what most apps/custom roms do anyway). Any apps that would be incompatible still are. Am I missing something?
Click to expand...
Click to collapse
I don't understand how it works but it works great for me! No more problems installing updates or new apps... Only did my updates that weren't working before and tried installing a few things so not sure it works for everything, but for what I wanted it's great!
OMG - someone fixed the market compatibility issue with non-standard LCD resolutions!!
well HALLELUJAH!!
below is the market app for the fix - this developer is apparently a GENIUS, being the first person on EARTH to SOLVE this frustrating issue! - I have tested it out on my G2 and it ROCKS!!
LCD Density Modder Pro
this doesnt work anymore so if any of u wanna fix market compatibility issues please refer this link:
http://forum.xda-developers.com/showpost.php?p=20624277&postcount=13
it works 100% for me so please thank the op for his efforts if it works for u as well (trust me it will work)
Just a small quick and dirty app that let you change some of the GTA3 default settings.
Original settings are backed up to (GTA3 Folder)/files/GTA3/gta3.gtsettingslauncher.set. If the app completely fails or you want to use the original settings after uninstalling the app, just copy this file back to (...)/gta3.set.
When your gta3.set is missing, please start the game and go to the display options. Change some settings and then hit "restore defaults". Then try again and start the settings app.
If there is still no settings file, get one from this forum (e.g. http://forum.xda-developers.com/showpost.php?p=20950484&postcount=29) or google. After launching the game with the downloaded settings file go to the in-game display settings an click "restore defaults". That should fix some problems with screen width and height.
Available Settings:
Shadows: On/Off
Lighting: On/Off
Resolution: High/Low
Rendering Distance: 18 Steps
Blur: On/Off *
* Blur is not working for me. The setting is always disabled when starting the game. Maybe it is working on other devices (Tegra?).
Currently only tested on I9100 with GTA3 German. Please let me know if it is working or not.
Changes:
2012/01/03 - v1.4:
catch more exceptions
changed launcher, it now hopefully will find the target more often
2012/01/02 - v1.3:
added another external_sd path (now searching in "/mnt/sdcard/external_sd/Android/data/", "/mnt/sdcard/Android/data/", "/mnt/sdcard/external_sd/data/" for package)
2011/12/31 - v1.2:
added launcher icon
added blur setting (which might have no effect)
changed namespace - please uninstall the old version manually. I used an example package found on the internet as skeleton and forgot to change it, sry
2011/12/29 - v1.1:
added external_sd to search path
Make sure to download the LATEST version.
Thankyou excellent work dev,works great.
My device is zte skate
And at 900Mhz on Atomic 2.5 rom,
Chainfire reduce texture size and quality,
With this app you have created,
It is running good now.
I just get instant force close when trying to run this. I was looking to try the lower resolution for performance increase.
I'm using a rooted vibrant (t959), with a custom 2.2 rom
kxlling said:
I just get instant force close when trying to run this. I was looking to try the lower resolution for performance increase.
I'm using a rooted vibrant (t959), with a custom 2.2 rom
Click to expand...
Click to collapse
Can you please post the full path to the original gta3.set? I think the path can't be found.
hacksteak25 said:
Can you please post the full path to the original gta3.set? I think the path can't be found.
Click to expand...
Click to collapse
http://i2.photobucket.com/albums/y8/kxlling/2011-12-29_130706.png
The path is in that screen shot.
Added "external_sd" to search path. Please try again with the new version.
+ 1
Works great now, thanks for the fix. Almost lag free now. Thanks!
thanks for sharing, i hope this is worked on my device
Works perfect on the HTC Desire HD! Thank you! :>
Sent from my loved HTC Desire [email protected] <3
Works perfect on my Sensation! Thank you!
I've attached two screenshots. One with defaultsettings and one with tweaked settings.
I get forced close also on zte blade (orange san fran)
But the game runs any ideas?
arnookie said:
I get forced close also on zte blade (orange san fran)
But the game runs any ideas?
Click to expand...
Click to collapse
When does it crash? Right after starting the settings app or when you try to "Save and Start"?
Can you please also post the path to your gta3.set? Maybe it is a path problem again.
Awesome!
Work perfectly on Xperia play!
It crashes just after starting app.
I fixed it I had to download and copy the file called gta3.set into the correct folder as no file of that name was in the data folder. After I did that the patcher worked fine. :O)
Seems some phones don't create the gta3.set file. Maybe you could include one with the patch or make it auto generate one for people like me. Thanks for the patch. ;0)
Awesome app. I was wondering though, is it possible to integrate more features/mods in the app?
Theres a post on the main page of xda showing mods, also another thread in this same section for gta mods like lamborghini/audi/VW cars, coca cola machines, better texture packs, etc. That would be crazy if you can add those features so we have a all in one mod app for the gta game and can apply them without much messing around. Hopefully that would even help more people add more content to make the game experience even better.
This worked great on my Asus Transformer!
I was surprised to find out the default settings were set so low. Even on my Tegra 2 device. It looks SO much better now.
Thanks for this - works great on my Desire Hd and Haipad M7S - draw distance on low means I can have the effects on and it runs fine on the Desire!
where should i paste this file?anywhere in my sdcard?anyone?plss..
edit: got it work..thanks OP.. ^^
Added a launcher icon and the blur setting. Bluring is not working on my i9100 (it is just disabled by the game while launching), but maybe it will work on other chipsets.
Download is appended to first post.
{
"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.
Nick's Phone V1.0 Based on Oxygen and Built From Roalex Sources
First of all, big thanks to AdamG, _thalamus, Roalex, everyone at Cyanogen, ihlades and everyone else who helps the desire! (And others I've forgot!)
I wasn't going to build Android from source because I knew it would grip me and consume me but I couldn't help it! I've been building Oxygen and Roalex from source and have added in my own changes in to both. I've settled on Roalex because it has more patches and updates than I can be bothered to add in manually! (I don't use github, all my changes are done offline etc)
Anyway, the ROM is based on Roalex's source code for his Wip branch as of the beginning of August with:
Lockscreen calendar - with the next 3 appointments shown up to 1 week in advance
Lockscreen Music controls - appear when music is playing and screen is locked, ONLY WORK WITH STOCK GINGERBREAD MUSIC PLAYER! (for some reason). They do work with Winamp but it sometimes mixes up play / pause modes. Not sure why but I prefer the stock player as it's lightweight and themed with my own mods
Lockscreen Torch - long press the home button to enable the torch (I use this so much I had to have it!)
Swipe Away Last Notification and Close Notification Tab - Bit of a gimmick but I liked it!
Fix alarm snooze / dismiss unlocking the screen - Cyanogenmod has this but Oxygen didn't, so I added it. Basically when you dismiss your alarm it unlocks your screen! Which is annoying!
+ My own ICS based theme I've done. Please see screenshots.
All my changes are hard coded in and CANNOT be turned off. Sorry, I could add in the ability to turn them off but this is based on what I want and use so I didn't want the ability to turn them off because I don't want to!
I've also added my own Go Launcher ICS theme, Go Widgets Theme and my calendar ICS theme for Android Pro Widgets.
I've used Holo Launcher as the default launcher and have modified this also, with some graphical changes I prefer!
I've also added in a modified stopwatch & timer app themed by me.
There's also:
720p HW Playback
Trackpad to wake (NOT to unlock)
SDCard buffer modified to 1024KB
T9 Dialler
I've decided not to add in any build.prop tweaks as I'm not convinced they do anything! Or do very little, so I've done none of those this time but anyone is welcome to add them in if you choose to.
As with all my ROMS, this is provided "as is" and no warranty is given or implied, so you can use at your own risk.
If anyone notices any bugs / issues then please let me know or post here!
Anyway, enjoy!
MD5 is: 429DC097B7E9FB3E05808F67025B8D18
Download is here: [Updated version with 1.20.2 BusyBox binary]
http://www.mediafire.com/?b8dyx3b2hbeu8an
FULL WIPE IS RECOMMENDED!
There's about 30MB of unused space in /system if you use the CM7r2 HBoot so you can either fill it up with your own applications or use the following custom HBoot created by schalmers to give you a system 125 / cache 5 / data 307 partition setup.
http://forum.xda-developers.com/showpost.php?p=30405300&postcount=34
APPS2SD Support / Enabling - Please see the quote below:
MrUrgit said:
Looks good so far.
You can choose where to install your apps (same as Mildwild V4.3).
As per the instructions for MW's ROM (thanks SydBarret55), If you want apps on sd-ext:
1. Activate sd-ext:
Go to Setting>Applications>Development
Check SD-EXT
Reboot phone
2. Choose the default location for applications:
Go to Settings > Applications > Preferred install location
Choose sd-ext
Or go here: http://forum.xda-developers.com/showpost.php?p=25430232&postcount=3812
You can also move apps individually:
Settings > Applications > Manage applications
Touch the app you want to move, and then touch where you want the app to go e.g. Move to Phone, Move to SD-Ext (EXT3 or EXT4 partition) or Move to SD card (Fat 32 partition).
Again, the link above has screenshots to show you what to do.
Click to expand...
Click to collapse
Downloading as we speak. Will give this a try.
*edit*
Has this rom got any sort of A2SD built in?
Looks great! I'm about to try. Thank you!
Looks good and pretty!
What ICS theme are you using?
Thanks
biron_w said:
Downloading as we speak. Will give this a try.
*edit*
Has this rom got any sort of A2SD built in?
Click to expand...
Click to collapse
Looks good so far.
You can choose where to install your apps (same as Mildwild V4.3).
As per the instructions for MW's ROM (thanks SydBarret55), If you want apps on sd-ext:
1. Activate sd-ext:
Go to Setting>Applications>Development
Check SD-EXT
Reboot phone
2. Choose the default location for applications:
Go to Settings > Applications > Preferred install location
Choose sd-ext
Or go here: http://forum.xda-developers.com/showpost.php?p=25430232&postcount=3812
You can also move apps individually:
Settings > Applications > Manage applications
Touch the app you want to move, and then touch where you want the app to go e.g. Move to Phone, Move to SD-Ext (EXT3 or EXT4 partition) or Move to SD card (Fat 32 partition).
Again, the link above has screenshots to show you what to do.
MrUrgit said:
SNIP!
Click to expand...
Click to collapse
Those instructions worked. Cheers
Sent from my HTC Desire using xda app-developers app
biron_w said:
Downloading as we speak. Will give this a try.
*edit*
Has this rom got any sort of A2SD built in?
Click to expand...
Click to collapse
It has yeah, please see the post from MrUrgit below:
MrUrgit said:
Looks good so far.
You can choose where to install your apps (same as Mildwild V4.3).
As per the instructions for MW's ROM (thanks SydBarret55), If you want apps on sd-ext:
1. Activate sd-ext:
Go to Setting>Applications>Development
Check SD-EXT
Reboot phone
2. Choose the default location for applications:
Go to Settings > Applications > Preferred install location
Choose sd-ext
Or go here: http://forum.xda-developers.com/showpost.php?p=25430232&postcount=3812
You can also move apps individually:
Settings > Applications > Manage applications
Touch the app you want to move, and then touch where you want the app to go e.g. Move to Phone, Move to SD-Ext (EXT3 or EXT4 partition) or Move to SD card (Fat 32 partition).
Again, the link above has screenshots to show you what to do.
Click to expand...
Click to collapse
Thanks for the post, I'll add it to the bottom of the first post.
carval2k said:
Looks good and pretty!
What ICS theme are you using?
Thanks
Click to expand...
Click to collapse
It's basically a mix from the original ICS ROM, Sonny's amazing CM7 theme and some of my own work from all over the place! Like the circle battery mod is taken from the online kitchen (or from dGB by SUroot, can't remember where!) and modified to blue and grey by me. Most the notifications have been colour coded to blue by me and when you press menu, I've tried to colour code all those icons to white as well.
It's taken a long time to get to where it is but like I've posted before, I'm keeping my desire for another 8 months or more so want it to be the way I like it (and hopefully others do as well!)
Nick
Flashed this last night and i'm really impressed with it.
It's super quick. Even booting it up only takes about 10 seconds!
*edit*
Is there any way to change the clock colour to white? I've done theme using the UOT Kitchen and the blue clock doesn't look right.
biron_w said:
Flashed this last night and i'm really impressed with it.
It's super quick. Even booting it up only takes about 10 seconds!
*edit*
Is there any way to change the clock colour to white? I've done theme using the UOT Kitchen and the blue clock doesn't look right.
Click to expand...
Click to collapse
I would have thought there's a way to do it in the Kitchen but if not you will need to use APKtool to decompile the framework-res.apk file unfortunately.
You can decompile it and edit the following bit in styles: (under res\values\styles.xml)
<style name="TextAppearance.StatusBar" parent="@android:style/Theme">
<item name="android:textSize">14.0sp</item>
<item name="android:textStyle">normal</item>
<item name="android:textColor">#ff39b6e7</item> <--------------- change this to ffffffff
</style>
Or you can do it this way:
http://forum.xda-developers.com/showthread.php?p=9978779#post9978779
You just need to follow the bit that says notification, date and time (decompiling the systemui.apk file).
Cheers,
Nick
nickabbott said:
I would have thought there's a way to do it in the Kitchen but if not you will need to use APKtool to decompile the framework-res.apk file unfortunately.
You can decompile it and edit the following bit in styles: (under res\values\styles.xml)
<style name="TextAppearance.StatusBar" parent="@android:style/Theme">
<item name="android:textSize">14.0sp</item>
<item name="android:textStyle">normal</item>
<item name="android:textColor">#ff39b6e7</item> <--------------- change this to ffffffff
</style>
Or you can do it this way:
http://forum.xda-developers.com/showthread.php?p=9978779#post9978779
You just need to follow the bit that says notification, date and time (decompiling the systemui.apk file).
Cheers,
Nick
Click to expand...
Click to collapse
Far too complicated for me :silly: i'll leave it how it is.
Excellent work.
I love the symbols of the notification power widget. Just out of curiosity, what exactly did you change/theme regarding the "Holo Launcher"? I've been using the launcher for several weeks now but can't notice any difference.
Great work!
Is there a stand alone Lockscreen Music Control patch for oxygen 2.3.2?
Thanks!
Tanks for this new Rom and for your work . I try it now.
Is your Rom multi-langages ?
Sent from my HTC Desire using xda app-developers app
Can't wait to try it out !
i'm still running your previous rom, and i'm super happy with it. still super quick and rock stable. i hope this new rom is the same. :fingers-crossed:
charliebigpot said:
Excellent work.
I love the symbols of the notification power widget. Just out of curiosity, what exactly did you change/theme regarding the "Holo Launcher"? I've been using the launcher for several weeks now but can't notice any difference.
Click to expand...
Click to collapse
I've only really changed a few things, mainly when you press menu the screen is transparent with a white border, instead of solid grey. Also when you press and hold on an icon, thats transparent and has a white border instead of just being solid grey and also when you go into a folder that's transparent with a white border. I've also made the return to desktop icon in the launcher brighter white and changed the play icon to ics blue instead of the semi-transparent white.
Not big changes but I prefer consistency!
_cino said:
Great work!
Is there a stand alone Lockscreen Music Control patch for oxygen 2.3.2?
Thanks!
Click to expand...
Click to collapse
I've not created one no, sorry. But it would be possible to do I'm sure. I think all the changes I made for lockscreen controls are in the framework-res location so a patch would be possible, but I won't be doing one, sorry.
FROGDIVISION said:
Tanks for this new Rom and for your work . I try it now.
Is your Rom multi-langages ?
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
It should be as it's based on the original oxygen / roalex sources and they are multi-language. Please let me know how the lock screen calendar looks because there's a string I changed in values for how the date is displayed, such as:
core/res/res/values/donottranslate-cldr.xml
<string name="abbrev_wday_month_day_no_year">E MMM d</string>
But I ONLY added this to values, not values-es and values-it etc etc so I hope Android will default to english and not crash if there's no language specific change. EG:
core/res/res/values-de/donottranslate-cldr.xml
<string name="abbrev_wday_month_day_no_year">E, d. MMM</string>
I presume it just means the date will be formated in UK format and not Spanish, but should still display correctly. Hopefully someone can let me know or post a screenshot to see if there's any issues.
EDIT: Just changed my language a few times and the lockscreen didn't crash or anything it displayed the date but I'm not sure if it's doing it wrong, but it looked OK but I only speak English unfortunately!
nafdroid said:
Can't wait to try it out !
i'm still running your previous rom, and i'm super happy with it. still super quick and rock stable. i hope this new rom is the same. :fingers-crossed:
Click to expand...
Click to collapse
Thanks for your comments, hopefully it doesn't disappoint you!
Nick
You will update ROM periodicaly, right ? What kernel you recommend ?
Sent from my HTC Desire using xda premium
Robi959 said:
You will update ROM periodicaly, right ? What kernel you recommend ?
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
If there's a serious bug or update and there's a need to update the Tom then I will do yeah. But I wont be releasing minor graphical changes because the rom is pretty much where I want it graphically.
As for the kernel, I recommend the one that's in the rom as its thalamus' r4 release which is the latest one but has roalex's patch for call recording. If you want things neat you could flash thalamus' standard kernel on top but I expect that would break KSM if you use it (I don't)
Nick
Ok. Im staying on this rom i like it ! Tnx
Sent from my HTC Desire using xda premium
nickabbott said:
If there's a serious bug or update and there's a need to update the Tom then I will do yeah. But I wont be releasing minor graphical changes because the rom is pretty much where I want it graphically.
As for the kernel, I recommend the one that's in the rom as its thalamus' r4 release which is the latest one but has roalex's patch for call recording. If you want things neat you could flash thalamus' standard kernel on top but I expect that would break KSM if you use it (I don't)
Nick
Click to expand...
Click to collapse
Now that you've mentioned it, what are the benefits or using KSM?
I've read a bit about it but, as with compcache, swap and that kind of things, I never find to understand the "pros and cons", and usually dind't feel big differences when enabling and disabling.
Thanks!
blackhawk_LA said:
Now that you've mentioned it, what are the benefits or using KSM?
I've read a bit about it but, as with compcache, swap and that kind of things, I never find to understand the "pros and cons", and usually dind't feel big differences when enabling and disabling.
Thanks!
Click to expand...
Click to collapse
I don't use it to be honest and I would doubt you would find much benefit from turning it on. I think it's mainly for when you're running virtual machines on a single host or if you run lots of similar processes on the same host.
So I imagine if you could make 2 calls at once and put one on hold while talking to the other etc then KSM might be able to use parts of that process and merge them in memory, potentially saving memory (totally hyperthetical here!). However, it's probably very minimal gains versus the time it takes for your phone to keep analysing memory pages to merge them!
And in theory, your phone should release memory used for processes once they've finished so even if you did save memory by using KSM in this hyperthetical situation, when you end both calls you should get the memory used released and back available anyway!
I think it only helps to run / do more things at once rather than get speed benefits because if 2 processes need the same memory page again it will create a copy and you have 2 un-merged pages again and more memory used up.
Someone more techy might provide a better insight but in a phone I would say it's not necessary. On a hyperV server running 20 virtual hosts I would say yes!
Hi all,
This works with all devices on 8.1 without round corners. Oreo 8.1 by default has statusbar padding enabled for devices with round corners, but this device among a few others doesn't have round corners and the padding seems like a waste of space to me (and a few other users too)
A simple ADB shell command fixes it and removes the padding.
Requirements:
- Mi A1 or any near stock Android device
- Should be on 8.1
- A brain and should be able to read and follow the written instructions.
- Platform Tools along with ADB drivers
Steps:
- Assuming it's your first day at XDA, enable Developer Options in Settings by opening Settings > System > About device and tap the Build Number 7 times. You'll be promoted to enter your lockscreen password, do so.
- You'll see a new sub menu, Settings > System > Developer Options.
Tap and scroll down to USB Debugging and enable it.
- Connect your phone to your PC. Download the latest Platform Tools and run the ADB.exe file.
- Hover over an empty space in the Platform Tools folder, Hold Shift + Right Click > Open Command/PowerShell window here.
- Run <adb devices> and it will pop up a dialogue on your phone screen asking for access to your phone. Grant the permission.
- Run the above command again, and you'll see an alpha numerical code (will be different to each user)
- Run <adb shell settings put secure sysui_rounded_content_padding 0>
- Voila!
Works on:
Mi A1 (tested personally by me)
Pixel
Pixel XL
Pixel 2
Will update this list frequenty. Suggestions on how to improve this thread are always welcome.
Did not worked for me
ADB seems to accept the command, but the padding is always there
This setting doesn't seem to be available on Mi A1 by default.
Before trying I wanted to take a note of stock value, but:
command: adb shell settings get secure sysui_rounded_content_padding
response: "none", but it should be some number instead
_mysiak_ said:
This setting doesn't seem to be available on Mi A1 by default.
Before trying I wanted to take a note of stock value, but:
command: adb shell settings get secure sysui_rounded_content_padding
response: "none", but it should be some number instead
Click to expand...
Click to collapse
Weird, there is padding present in the stock 8.1 build. Another user confirmed that this worked for them. This is specifically for stock ROMs, most custom ROMs have the padding disabled by default.
works like a charm voilaaaaa
when i enter the adb shell settings put secure sysui_rounded_content_padding 0 line in PowerShell nothing happens, so i can say it does'nt work for me at least.
---
Edit:
But when i change the 0 to 0.1 or 0.5, it says: System UI has stopped, and AGAIN nothing happens.
it works for me, thanks!
It worked for me too. Thanks.
Sent from my Mi A1 using Tapatalk
worked nicely thanks! this bugged me quite a bit
I really like the added padding but for the testing I tried it and it works perfectly (on A1 and Pixel 2)...
Is there a space between "secure" and "sysui"?
Worked for me, thanks!
I found out as well that you can put negative values to save even a bit more space, although did not test extensively to make sure it doesn't get buggy at some stage.
settings put secure sysui_rounded_content_padding -8 seemed to be the max to me, but I have tweaked DPI and font size, so not sure what works for who
I'll stick with the 0 though, don't want to take risk to have to change it every 5 minutes...
nananonoka said:
Is there a space between "secure" and "sysui"?
Click to expand...
Click to collapse
Yep
BtB said:
Worked for me, thanks!
I found out as well that you can put negative values to save even a bit more space, although did not test extensively to make sure it doesn't get buggy at some stage.
settings put secure sysui_rounded_content_padding -8 seemed to be the max to me, but I have tweaked DPI and font size, so not sure what works for who
I'll stick with the 0 though, don't want to take risk to have to change it every 5 minutes...
Click to expand...
Click to collapse
many thanks, now it works perfectly with negative value for me. :highfive:
Ron1209 said:
Yep
Click to expand...
Click to collapse
Well, I tried it and it wasn't working except in Spotify app. I wonder why.
Thanks for the tutorial mate. I really hate this padding then you solved this! Working perfectly.
Does this works to enable padding in 8.1 pixel experience rom in any device?
I think round corners is removed in July patch.
HidekiRyuga said:
I think round corners is removed in July patch.
Click to expand...
Click to collapse
Your DPI makes it seem so, but it isn't. I'm on the latest July Stock ROM and padding is present.
M1810 said:
Does this works to enable padding in 8.1 pixel experience rom in any device?
Click to expand...
Click to collapse
Should work in theory, you'll need to change the input value though