Hi,
I've recently put Awesome ICS 3.6 into my Glacier and aside from a few tweaks, the ROM is very good. Probably the most complete ICS rom available for this device.
However, there is only one issue that I've been having. Japanese Characters will not display anywhere throughout the ROM or in Applications.
I'm not sure if this is a ROM issue or a Kernel issue. I was hoping that someone could point me in the right direction for resolving this.
Thanks.
For anyone else having issues displaying Japanese or Chinese text, I found a similar posting in the Awesome ICS Dev thread:
http://forum.xda-developers.com/showthread.php?p=26848771&highlight=japanese#post26848771
Yes sorry I had taken a lot of stuff out the rom to make it lighter didn't think that would make a difference but I see it does will re add it next time
Sent from my HTC Glacier using Tapatalk 2
Above posting worked, but the author didn't post the file required. I've attached it to this post. ADB the file in the archive (inclusive of path) to the phone and restart.
This file should work with just about any ROM since it is only a TTF file.
Not a problem. I think this ROM really is amazing. I had to work out a couple kinks.
- Japanese font support (had to add the aforementioned TTF font)
- CPU Clock Management "AX Control" in system panel doesn't work, workaround is to use "ROM Toolbox" for changing frequencies and govenors
- Tried Tiamat V2 kernel, but stability was a problem with a few applications ie. PowerAMP. MDEEJAYs Kernel has been stable. I'm not sure why but problems went away after the kernel switch.
And thank you for your reply. I think you guys have done good work here. Given the age of the MT4G (Glacier), I expect this to be the only ICS ROM that will reach full completion. I think many others have moved on for development.
{
"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.
Before my Asus tf700 Infinity, I owned a Samsung Galaxy Tab. I purchased some programs and games for it, and all was well until it was stolen. The problem? Now I've downloaded and used those same apps on my tf700 Infinity, and the orientation is off by ninety degrees on quite a few. It has to do with Android's API and Honeycomb, and how the default base orientation is set in the framework policy. Before tablets, the default orientation for the Android API was portrait, but tablets made landscape defaults a possible better default. Apps not written to accommodate this would have the sensors read 90 degrees skewed for landscape default devices (like my tf700), because the sensor data is being read from landscape (regardless of orientation), but interpreted as portrait by the app. Even though my Galaxy Tab was a tablet, it's default orientation was portrait, so there was no 90 degre skew. I have read enough to know that it's possible to change the Android system default value, but it has to be changed in the framework . . . No easy task, especially if the rom is ODEXed.
So . . . anyone have any advice or fix so my paid apps aren't wasted money? I don't think emailing every single developer is the key, when I could modify a single system value to fix the problem for all apps. Thanks in advance, any help is appreciated.
Doesnt ever gyro-based app/game have a recalibration setting? Have you tried that?
Send From My Samsung Galaxy S3 Using Tapatalk 2
GrayHat137 said:
So . . . anyone have any advice or fix so my paid apps aren't wasted money?
Click to expand...
Click to collapse
You could try Ultimate Rotation Control. It can have an individual setting for each application (Forced Portrait/Forced Landscape/Forced Auto).
ShadowLea said:
Doesnt ever gyro-based app/game have a recalibration setting? Have you tried that?
Send From My Samsung Galaxy S3 Using Tapatalk 2
Click to expand...
Click to collapse
The problem is that the data the app is getting is from the sensors is rotated 90 degrees. For example, if the app assumes the tilt data it is getting is from the left and right: tilt left, go left. On my tablet, it's default boot state is landscape, so if the app is asking for the sensor info the wrong way (a deprecated way - from before the Honeycomb API), it's getting the tilt axis from the top and bottom, so: tilt up, go left. I can calibrate, but I still have to tilt up to go left.
Sounds like badly programmed apps to me. Have you tried asking the devs to update based on the correct APIs?
HeartWare42 said:
You could try Ultimate Rotation Control[/URL]. It can have an individual setting for each application (Forced Portrait/Forced Landscape/Forced Auto).
Click to expand...
Click to collapse
I had hoped it would override the default framework, but apps were still polling the sensors wrong no matter which orientation they were displayed in. The sensor data was rotating the same amount as the app, but the original sensor data was still originally off by 90%.
Thanks for the tip; Ultimate Rotation Control is a good app that solved another issue I had, just not this one.
sbdags said:
Sounds like badly programmed apps to me. Have you tried asking the devs to update based on the correct APIs?
Click to expand...
Click to collapse
Yes, that's the consensus. Some I've asked, others are no longer in active development (nostalgia for holding onto these apps). I stumbled upon a web hit while googling for answers, the solution was about changing a simple setting in the android framework, but I'm a not experienced with ADB, and things like ODEXing and DeODEXing are nerve-wracking while I learn and experiment.
Also, thanks for coming sbdags. Running Xenogenesis since late April, fantastic job! :good:
GrayHat137 said:
Yes, that's the consensus. Some I've asked, others are no longer in active development (nostalgia for holding onto these apps). I stumbled upon a web hit while googling for answers, the solution was about changing a simple setting in the android framework, but I'm a not experienced with ADB, and things like ODEXing and DeODEXing are nerve-wracking while I learn and experiment.
Also, thanks for coming sbdags. Running Xenogenesis since late April, fantastic job! :good:
Click to expand...
Click to collapse
Which part of the framework do you need to change?
sbdags said:
Which part of the framework do you need to change?
Click to expand...
Click to collapse
Navigate to the androidpolicy\com\android\internal\policy\impl folder and open PhoneWindowManager.smali in your favorite text editor (Notepad++ is my favorite)
Search for the method "rotationfororientation"
(Picture of code here)
Make note of the variables (v#) for portrait and landscape (in my case portrait is v5)
Scroll to the end of the method and you should find something like:
"move v2, v5" (make sure it's the last move command before the end of the method)
Change the second variable (in this case v5) to whatever orientation you wish to be default. In my case I have set portrait as the default orientation.
Click to expand...
Click to collapse
There are other steps, but this is the only variable changed. I can't post links yet, and I didn't want to copy all of the text there, but that's it. The attached picture is the picture of the code.
Eureka!
GrayHat137 said:
There are other steps, but this is the only variable changed. I can't post links yet, and I didn't want to copy all of the text there, but that's it. The attached picture is the picture of the code.
Click to expand...
Click to collapse
Dear friends,
As I was also facing the same problem in my Ubislate 7C+(EDGE) tab by DATAWIND. While reading your post an idea struck to my mind. With the help of Root Browser app I navigated to /system/build.prop, opened it in text editor and in "ADDITIONAL_BUILD_PROPERTIES" changed the value of "ro.sf.hwrotation=270" 270 to 180 saved it and rebooted the tablet. Yes! the problem was solved but it created a new problem that the orientation of animation while boot and camera orientation has changed now but in order to rectify it I pulled bootanimation.zip to my computer and after unzipping it changed the orientation of animation files from portrait to landscape. Changed the orientation in 'desc.txt' from 480 800 to 800 400 and zipped both without any compression. Pushed it back to /system/media and changed the permission, user,group to original one with the help of root browser. Then for camera orientation with the help of root browser I navigated to /system/etc/camera.cfg opened it in RB text editor and changed camera orientation from 90 to 0, saved it and rebooted my tablet and now all the games using gsensor tilt are working fine.
Thanks,:good:
rotation gyro off
I had the same problemen, i resolved it by going to setting, location and then status (only GPS) then i started GPS tools , just waited a min or so . now everthing is oké again.
I hope thuis helps you