Related
READ BEFORE TRYING
I am cdma hero user and it works very well for me. This should work on gsm hero. I pulled this from HERE, it was for the Milestone Android phone which is a GSM phone.
Before enabling
*Change home laucher
*Delete htc lock screen
see below if you dont no how
Jit does not work with htc sense, it will give you many problems. I suggest using Helix launcher from market (free and its what i use daily with no issues). You can also try GDE and nexus launcher, or really anything other then sense.
To change launchers go to setting>applications>manage apps>htc sense And clear defaults. Press home and choose a different launcher.
OR download "Home Switcher" from market.. Its a free app that lets you change between launchers.
JIT does not like any HTC apps.. So delete your HtcLockScreen by doing this.
Code:
adb remount
adb shell rm /system/app/HtcLockScreen.apk
Here is the htc lock screen if you want it back
HtcLockScreen
JIT is in no way perfect on our htc hero's so MAKE A BACKUP before trying.
And you could very well run into TONS of problems, its just something to test out.
Though if used right, you wont have any problems. I use this daily.
THIS IS FOR JIT
Download: *View attachment vmlibs.zip*
Then follow these steps:
•Create 2 folders on your sdcard: “jit” & “dalbk”
•Extract the vmlibs.zip to the “jit” folder on your sdcard
•Using ADB pull your build.prop
Code:
adb remount
ADB pull /system/build.prop build.prop
-It will place the file in your c:/android/tools folder
-Edit this using notepad or similiar program.
•Add the following line to the end of the build.prop: dalvik.vm.execution-mode=int:jit
-Save the changes and move it to the directory c:/
•Push it back to your “jit” folder on the sdcard
Code:
ADB push C:\build.prop /sdcard/jit/build.prop
This will back up your current files. So you can disable jit.
Code:
ADB shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
cp /system/build.prop /sdcard/dalbk/
cp /system/bin/dalvikvm /sdcard/dalbk/
cp /system/lib/libdvm.so /sdcard/dalbk/
cp /system/lib/libnativehelper.so /sdcard/dalbk/
This will enable jit on your phone.
Code:
cd /sdcard/jit/bin
cp -f dalvikvm /system/bin/
busybox chmod 755 /system/bin/dalvikvm
cd /sdcard/jit
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
cat build.prop >/system/build.prop
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot
WIPE DALVIK CACHE AFTER ENABLING JIT.. This will cause your phone from sometimes going into a boot loop.
You dont have to wipe your whole phone.. Only dalvik cache. Your phone will take awhile to reboot since its rebuilding dalvik. Be patient. If it eventually freezes then reboot and it should go through fine after that.
TO DISABLE:
This should disable JIT and return phone back to defualt
Code:
adb remount
adb shell
su
cd /sdcard/dalbk/
cat build.prop >/system/build.prop
cp -f dalvikvm /system/bin
busybox chmod 755 /system/bin/dalvikvm
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot
Post For help if the disabling gives you any problems.. If it does you can always do back up of your rom that you should of made.
Original site http://sholes.id.au/how-to/
Awesome.. I really hope that some of the hero devs can optimize this for the hero.
madsborelli said:
Awesome.. I really hope that some of the hero devs can optimize this for the hero.
Click to expand...
Click to collapse
I am hoping this also. Most devs dont work on things like this, or know enough about it to fix it.
The only real problem I have had was using htc widgets, htc sense, and htc lockscreen. When I use other home screens, and delete the htc lockscreen, I can run error free with JIT enabled.
Jus10o said:
I am hoping this also. Most devs dont work on things like this, or know enough about it to fix it.
The only real problem I have had was using htc widgets, htc sense, and htc lockscreen. When I use other home screens, and delete the htc lockscreen, I can run error free with JIT enabled.
Click to expand...
Click to collapse
Can you feel the difference in speed?
madsborelli said:
Can you feel the difference in speed?
Click to expand...
Click to collapse
Everything is really instant. I clicked and then closed and clicked and closed multiple apps on my screen and it never hung up or lagged.
Before jit, it was pretty quick but every once in a while would slow up on opening or closing, or switching apps specialy when recieving a call or text at the same time.
One example is. Before jit I was using the yellowpages app with voice command and it would take forever loading voice and then entering what i said into the text box. I tested with jit and it was all pretty instant and never paused or lagged after multiple test.
I posted this on cdma hero and this hero, it gets alot of views but no one seems to actually been trying it and posting about it.
I would like to know what kind of improvements its makes from JIT disabled and JIT enabled for other people.
I understand you all have completely different roms so the numbers can't be directly compared. But the improvement between stock and JIT should show some resemblance from my rom and gsm roms.
Jus10o said:
I posted this on cdma hero and this hero, it gets alot of views but no one seems to actually been trying it and posting about it.
Click to expand...
Click to collapse
OK, I'm also one of the readers
The most important thing why I do not try it to use is, that I wanna held the "Sense UI".
Thats would be also the main reason for the other readers
regards
Dominic
derDominic said:
OK, I'm also one of the readers
The most important thing why I do not try it to use is, that I wanna held the "Sense UI".
Thats would be also the main reason for the other readers
regards
Dominic
Click to expand...
Click to collapse
Yeah I understand. I was one of those people. But I have come to like the helix launcher and beautiful widgets combination. I dont use any of the htc widgets other then the clock, which has a replacement for it.
Also over in cdma hero, many of the people use other launchers and dont use htc sense. Just for speed or personal favorites. I dont know how it is with here.
You can also disable jit very easily by changing the build.prop and having all htc widgets and sense usable agian.
when i do this "mount -o remount,ro /dev/mtd/mtdblock6 /system" it says
mount: device or resource busy
Also how does one get the $ sign whenever i type adb shell it automatically goes to the next line showing me #
Also after running these commands my hero boots but get stuck when i try to unlock the screen by dragging it down, is this not compatible with roise? im running Be hero 1.2.6 which is an ERIS port(2.1).
eldrid said:
when i do this "mount -o remount,ro /dev/mtd/mtdblock6 /system" it says
mount: device or resource busy
Click to expand...
Click to collapse
should be remounted when you reboot anyway.
eldrid said:
Also how does one get the $ sign whenever i type adb shell it automatically goes to the next line showing me #
Click to expand...
Click to collapse
then $ means you are logged in as an unprivileged user, the # indicates that you are root. so if you get # after opening adb shell that is fine, you can skip the 'su' command then.
eldrid said:
Also after running these commands my hero boots but get stuck when i try to unlock the screen by dragging it down, is this not compatible with roise? im running Be hero 1.2.6 which is an ERIS port(2.1).
Click to expand...
Click to collapse
second line of the first post should clarify that...
eldrid said:
when i do this "mount -o remount,ro /dev/mtd/mtdblock6 /system" it says
mount: device or resource busy
Also how does one get the $ sign whenever i type adb shell it automatically goes to the next line showing me #
Also after running these commands my hero boots but get stuck when i try to unlock the screen by dragging it down, is this not compatible with roise? im running Be hero 1.2.6 which is an ERIS port(2.1).
Click to expand...
Click to collapse
The error i received to, dont worry about it.
Yes mine goes to #, ill edit the instructions.
And after it reboots to the screen. Press menu to unlock your phone, DO NOT SLIDE.. It rarely works sliding.
And once you press menu, go to settings, applications, manage applications. Find htc sense, and CLEAR DEFAULT...
Then go to the market and download helix launcher.. You need to do all of this if you want NO force closes and no problems. Once its installed you can press home and select helix as default. Reverse the step to put htc sense back on.
If you really want to use sense ui, you must disable JIT.. Boot up your phone, let it load to the lockscreen. Dont touch anything. Do the steps to edit build.prop and do
TO DISABLE:
CHANGING THIS IN build.prop... This should disable JIT (I have not tested this yet, will post if this works later)
dalvik.vm.execution-mode=int:jit
To:
dalvik.vm.execution-mode=int:fast
push it back to your phone, and reboot
Thank you Kendong2 for replying, I was typing it out when you posted. I didnt know you had helped already.
If anyone does try this, feel free to post what home screen launcher and what errors you come across. Other then htc related things.
I just enabled JIT. Doing some tests now.
---
Alright, this are the results in a "real world" environment:
JIT DISABLED/JIT ENABLED:
NeoCore with sound: 24.4/24.4
NeoCore without sound: 28.8/28.8
Softweg GPU test: 117/116
Lag test: 41/40
Linpack: 2.312/3.663
The only noticeable result was with Linpack, let's say, RAW processing power. All the graphics benchmarks show same performance with JIT enabled. I guess it's a good thing then right?
Just enabled it as well... will test and report
now running alright and seems to be stable. can't tell too much of a difference at the moment but here is the result from linpack.
ahero v0.71 with 64MB swap
Configured with: debugger profiler hprof with_jit show_exception=1
BSK
Is an update.zip possible ? I'm at work, can't use adb right now
ok, im trying to disable it but cannot?
where do i have to change from jit to fast? in the build.prop from sd card right?
@Arkymedes
if you edit build.props in /sdcard/jit then whilst your in that directory do a :
cat build.prop >/system/build.prop
chmod 666 /system/build.prop
sync
reboot
once you have rebooted, it might be worthwhile going back into adb shell and typing this :
dalvikvm -h
i think you should not see "with_jit" in the last line.
BSK
bluescreenkid said:
@Arkymedes
if you edit build.props in /sdcard/jit then whilst your in that directory do a :
cat build.prop >/system/build.prop
chmod 666 /system/build.prop
sync
reboot
once you have rebooted, it might be worthwhile going back into adb shell and typing this :
dalvikvm -h
i think you should not see "with_jit" in the last line.
BSK
Click to expand...
Click to collapse
Followed every step that you mentioned...
After reboot that's what I get in the last line after "dalvikvm -h":
Configured with: debugger profiler hprof with_jit show_exception=1
PS: anyway, I think it's disabled since the scores in Linpack are the normal ones, around 2.250 or something.
Well well...
I just enabled this and after first reboot absolutely everything crashes and I can't get past the lockscreen. Rebooting again now.
EDIT: Same again next reboot. Am on Androbin 2.1 Vanilla ROM
@Arkymedes
if you followed the instructions you should have backups in the /sdcard/dalbk/ folder. just use the instructions again to put them all back.
but it looks like it's not now using the JIT you just copied across anyway.
BSK
I'm trying to install Thai font onto my Desire.
Setup: HTC Desire w/Pays Desire 2.1 RockSolid v1.5 ROM
I'v tried 3 metods so far (see below):
Metod 1 & 2 results in the fonts going to /systems/fonts, while Metod 3 says allready exists (although does not list with 'ls'...). I also tried to copy the fonts to /systems/font (without 's' at the end).
In any case so far, I can't see thai font's while sms'ing / browsing.
And sorry, new poster, so can't link (but the below is easy to find with google, along with the fonts).
Anyone got any more ideas to how to get thai fonts (probably same with other fonts also), without going to froyo rom (I like sense ui 2.1 and no mic-echo...)
1) desire normal boot, and connect with adb-recovery.bat
adb remount
adb shell
cat /sdcard/fonts/DroidSans.ttf > /system/fonts/DroidSans.ttf
cat /sdcard/fonts/DroidSans-Bold.ttf > /system/fonts/DroidSans-Bold.ttf
cat /sdcard/fonts/DroidSerif-Regular.ttf > /system/fonts/DroidSerif-Regular.ttf
cat /sdcard/fonts/DroidSerif-Bold.ttf > /system/fonts/DroidSerif-Bold.ttf
cat /sdcard/fonts/DroidSerif-BoldItalic.ttf > /system/fonts/DroidSerif-BoldItalic.ttf
cat /sdcard/fonts/DroidSerif-Italic.ttf > /system/fonts/DroidSerif-Italic.ttf
reboot
2) same as 1) but from recovery
3) Terminal Emulator w/BusyBox
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# mkdir /data/busybox
# cat /sdcard/busybox > /data/busybox/busybox
# chmod 755 /data/busybox/busybox
# mkdir /data/local
# cd /data/busybox
# ./busybox –install
# cp /sdcard/fonts/* /system/fonts
You can run pushfonts.bat in attached file via recovery mode to push thai fonts.
Credit for someone in pdamobiz.com that I cannot remembered.
Felys said:
You can run pushfonts.bat in attached file via recovery mode to push thai fonts.
Credit for someone in pdamobiz.com that I cannot remembered.
Click to expand...
Click to collapse
using that zip file in recovery resulted in:
"E:No signature (52 files)
E:Verification failed
Installation aborted"
I might have done it wrong (installed as the zip file in recovery).
Anyway, I saw that this zip file contained more font files than the two other locations I have downloaded the thai fonts from. So I went to recovery and pushed all the font files manually to system/fonts (adb shell commands).
and now.....IT'S WORKING!!!!! thx
Hello all,
I've got a very similar problem. I would like to install Georgian font into my defrost 16c system. For example I got DejavuSans.ttf (from Dejavu project) and I've allready tried to push it into /system/fonts (in recovery mode ofcourse). Pushing went well... but after reboot, no luck. Appear squares not georgian letters.
Anybody have some Idea?
Sent from my HTC Desire using XDA App
alinuxos said:
Hello all,
I've got a very similar problem. I would like to install Georgian font into my defrost 16c system. For example I got DejavuSans.ttf (from Dejavu project) and I've allready tried to push it into /system/fonts (in recovery mode ofcourse). Pushing went well... but after reboot, no luck. Appear squares not georgian letters.
Anybody have some Idea?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Which recovery state you are in? If you still in red triangle screen, the push will not be succeed (yeah it still say in cmd that they already pushed file to phone). I have run AM recovery, and then pushed the font via adb and it works.
Make sure you have all fonts. First times I tried I was missing mono and callback font files of the Thai font files. Not sure if dejavu has those fonts. I did it successfully in recovery at Ted triangle.
Sent from my HTC Desire using XDA App
Felys said:
Which recovery state you are in? If you still in red triangle screen, the push will not be succeed (yeah it still say in cmd that they already pushed file to phone). I have run AM recovery, and then pushed the font via adb and it works.
Click to expand...
Click to collapse
I've tried as you said with AM Recovery, but I got the same result:
alinux$ ./adb-mac push /Users/alinux/Downloads/dejavu-fonts-ttf-2.31/ttf/DejaVuSans.ttf /system/fonts
786 KB/s (633604 bytes in 0.786s)
After reboot there is no DejaVuSans.ttf in /system/fonts directory.
What is recovery mode?
Is it required to root the phone prior to using the puchfont.bat utility?
Hi all!
After searching the wide web of the world I didn't find anyone who cared to program the special characters for nordic keyboards (æ,ø and å). The norwegian stock ROM has got these mapped to own keys, but I've never liked to use stock ROM, so I was stuck with the "long press method".
If you screw up your phone trying to adb push, cp -f these files I'm not responsible yada yada yada (nothing wrong should happend, really)
What I've done is taking the modified files from teferi, and added my own editing for the quick keys (as I had to make place for the chars I removed from jkl) and the special chars of course.
Confirmed on my G2 (running the CM and Sense ROMs)
Code:
*Norwegian*
version 0.3:
-Fixed issue with , and ; didn't work on hardware keyboard.
version 0.2:
Quick change to the "Z" button, since "`" is used in command substitutions.
-alt-z is still "^", alt-shift-z = "`"
version 0.1:
-alt+j,k,l = æ,ø,å (alt+shift gives capitol letter).
- make ".com" a TAB key, as it ought to be
- left softkey is now "\" "|" "/"
- right softkeys are now "[" "(" "<" and "]" ")" ">"
- alt-z is now "^"
INSRUCTIONS:
- download file
- unzip g2-nordic_01.zip
- adb push vision-keypad.kl /sdcard/
- adb push vision-keypad.kcm.bin /sdcard/
- adb shell
- su (if you don't have ro.secure turned off)
- mount -o remount,rw /dev/block/mmcblk0p25 /system
- cp -f /sdcard/vision-keypad.kl /system/usr/keylayout/
- cp -f /sdcard/vision-keypad.kcm.bin /system/usr/keychars/
- reboot
Btw... backup of original keymapping is included... just rename them without .orig, and follow the procedure above
Code:
Guide to make your own keys:
Download a hex editor (i prefer xvi32), open the "kcm.bin", and alter the symbols shown in the attached .jpg. If you wish to alter the "main" char of the key, you can change that in the .kl file with notepad. You can find the original untouched files in the nordic...zip
Thanks to teferi for the base files
adb shell
I keep getting this, im sure the files on are on the sdcard
Code:
# cp -f /sdcard/vision-keypad.kl /system/usr/keylayout/
cp -f /sdcard/vision-keypad.kl /system/usr/keylayout/
cp: not found
#
Make sure you have busybox installed (to get the cp function)... easiest way
I'll also update that in the OP.
You can also just copy it over to the respective folders with root explorer etc.
Sent from my HTC Vision using XDA App
won't quite work on DZ - the keyboard device name is vision-keypad-wwe on that model. renaming them ought to work, but I don't have something to test it on.
teferi said:
won't quite work on DZ - the keyboard device name is vision-keypad-wwe on that model. renaming them ought to work, but I don't have something to test it on.
Click to expand...
Click to collapse
Renaming the bin/kl still don't "trick" the system into using the files. At least from my experience. I'm just trying to get the original g2 layout that includes www/.com, along with the 3 user keys to work on the z rom.
eViL D: said:
Renaming the bin/kl still don't "trick" the system into using the files. At least from my experience. I'm just trying to get the original g2 layout that includes www/.com, along with the 3 user keys to work on the z rom.
Click to expand...
Click to collapse
I've used the kl./.kcm files from G2 to make the G2-norwegian layout, and DZ files to make the esp-version... which is why I removed the esp from this thread...
I think it should be possible to port the keys if you use the base files from each device, and edit the .kl/.kcm files the way you want them. Then add them both to the ROM... G2 will use the vision-keypad.* files, DZ will use vision-keypad-wwe.* files (but I think you already know this)
There's occasional all-caps ÄÖÅ problem with hardware keyboard, but closing keyboard and opening software keyboard and back to hardware keyboard fixes that. Or you can try this.
Update: This seems to fix irssi connectbot and all caps scandinavian characters problem also. Fixed Norwegian AE and O with dash.
This is what I did:
First you have to get root, I used these instructions and they worked for me (Finland, Saunalahti):
http://forum.xda-developers.com/showthread.php?t=843014
Want to know more about modifying keymaps, see here:
http://forum.xda-developers.com/showthread.php?t=837002
And this old post is still valid for modifying keymaps-file with hexeditor:
http://forum.xda-developers.com/archive/index.php/t-504710.html
And that's basically what I did.
After you have root:
Download the attachment vision-keypad-nor.kcm.bin.zip and unzip it.
On PC run:
adb pull /system/usr/keychars/vision-keypad-nor.kcm.bin /tmp (for backup, store the file somewhere safe)
Copy modified version to /sdcard (the file you downloaded)
adb push vision-keypad-nor.kcm.bin /sdcard/
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
cp -f /sdcard/vision-keypad-nor.kcm.bin /system/usr/keychars/
sync
reboot
(few finnish words for finnish googlers: desire z ääkköset skandit)
when i try this part:
"adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
cp -f /sdcard/vision-keypad-nor.kcm.bin /system/usr/keychars/
sync
reboot"
i get "Permission Denied" when i write SU. my phone IS rooted and have S-off.. any clue on what can cause this problem?
what state should the phone be in? "disk drive" right?
Problem solved: i had to open my super user application on my phone to allow before i could continue
Did everything like in instructions, and now my touchscreen is mirrored!
If I push the left side of the screen it registers it on the right side and vice versa. And worst thing is that I don't have the original file anymore
edit: I found the original backed up file, thank god! Nice gag
Samusalo, are you serious? Shouldn't have anything to do with touchscreen calibration.
Exanimus, did it work for you after all?
Should not have anything to do with touchscreen calibration.
Also fixes wrong keyboard mapping or capacitive buttons not working in G2 based roms.
I posted a repaired file somewhere alrdy, and this is 5th thread after mine
thanks for getting this started
more than the scandinavian characters i was annoyed by the total LACK of certain keys on the keyboard
as a linux user <, > and | are essential!
so i cobbled this together (also fixes the capital char issue)
changes;
æ -> [
æ +shift -> {
æ +shift+fn -> æ
ø -> ]
ø +shift -> }
ø +shift+fn -> ø
ä +fn -> <
ö +fn -> >
å +fn -> \
å +shift+fn -> ^
. +shift+fn -> | (pipe)
these remain the same;
æ +fn = ?
ø +fn = !
it appears we can still add shift+fn keys for the whole keyboard if more are needed
any suggestions?
installation;
adb push vision-keypad-nor.kcm.bin /sdcard/
adb push vision-keypad-nor.kl /sdcard/
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
cp -f /sdcard/vision-keypad-nor.kl /system/usr/keylayout/
cp -f /sdcard/vision-keypad-nor.kcm.bin /system/usr/keychars/
sync
reboot
be sure to backup originals
Shole, great stuff! Thanks. Will try your keymaps.
shole, you're awesome! Thank you, Jusii too.
I would be more interested in changing Æ or Ø to a second fn.
Is that easy to fix?
Sent from my HTC Vision using Tapatalk
shole said:
it appears we can still add shift+fn keys for the whole keyboard if more are needed
any suggestions?
Click to expand...
Click to collapse
Shortcut for "~" would be awesome to have too. I've got no idea what shortcut to use tho, since your layout seems awesome already and it's taking pretty much all the spare combinations available.
~ is at [email protected] already in the stock phone, and these mods
a second fn would be trivial to add to replace, say, å, but you would lose that button entirely for fn role only
the keyboard is already short of keys and the fn and shift keys are sticky by default so i don't really see it as a need at all
the menu key on the physical keyboard is entirely redundant though(you need it rarely and the other one is only a short thumb move away on the screen half), but it's right next to the existing fn-key so that's not much use
right side shift key would be redundant if it wasn't used by connectbot as tab
tattevajoo said:
Shortcut for "~" would be awesome to have too. I've got no idea what shortcut to use tho, since your layout seems awesome already and it's taking pretty much all the spare combinations available.
Click to expand...
Click to collapse
I'd map it to [email protected] ...
EDIT: Oops, I was late.
Ahhh my bad, should of looked more carefully ~ thanksss (again).
Sent from my HTC Vision using XDA App
Any way to add back key to layout? Taking gloves off allways when need to use back button is annoying...
Fubaaarrr said:
Any way to add back key to layout? Taking gloves off allways when need to use back button is annoying...
Click to expand...
Click to collapse
That would be one helluva improvement to this phone. Adding left and right arrows and it would complete for my use.
this looks nice...
did anyone so far start working on a German version of this, and would mind sharing?
the stock Desire Z German version annoys me as hell.
I set the phone to English, but use the German keyboard layout.
first of all, I can't input capital Umlaute (ÄÖÜ), no combination of Fn+shift+j/k/l works. especially bad if i want to input a new word.
changing the keymap should fix my woes here, right?
also for general use, I'm lacking <, >, ~, | and some others - maybe someone modified the german keyboard for this already?
on the other hand - the phone specifically has a combination (Fn+search -> Symbols) - why does this only contain like 1/3 of the 2 pages available in the soft keyboard?
does anyone know a way to add the whole bunch from the soft keyboard to the selection screen that pops up when hitting fn+search?
kind regards,
sub
Irssi connectbot does not need rooting it has a fix for scandinavian characters of its own, just enable it in the settings. The fix also repairs ~
It also contains ^ < > | etc characters in its longpress-menu
Thanks for the fix! It works on Gingervillain 1.4.
I prefer using adb push:
Code:
adb remount
adb push /vision-keypad-nor.kcm.bin /system/usr/keychars
adb reboot
Thanks Jusii for the fix!
rollex said:
Thanks Jusii for the fix!
Click to expand...
Click to collapse
Jusii's fix worked me for a long time in Froyo (Virtuous 1.0.2), but then I updated to Gingerbread and Virtuous 2.0.0 and got problems shole described. Installed shole's keypad fixed all the problems.
I would thank you all participated but for some reason there is no THANKS -button below your messages. So once I again I thank here. Thank you!
Hi there,
anyone could confirm?
Tab fw JM6 rooted ok with SuperOneClick
If I try to change LCD density with LCD Density Changer, nothing happens, it doesn't work
Same issue with Spare Parts, the program starts but then force close
Is there any other sw out there to change LCD density that works with JM6?
thanks
It's because BusyBox isn't installed. Go to LCD Density - Settings - Select make LCD my system density. As soon as you tick the box, it will say Cannot complete without busybox and will direct you to the market.
Download Busybox and all root apps will work.
Unlike Z4root, SuperOneClick doesn't install busybox, you need to do it manually.
great, thanks!
Or alternatively you can edit the build.prop and select the density you want in there, without adding any 3rd party programs.
I've set lcd density to 180
I've also installed LauncherPro with all widgets
The People widget is very big, is there any chance to resize it or put more than one widget in the same page (ex. People and Facebook widget)
spanky said:
I've set lcd density to 180
I've also installed LauncherPro with all widgets
The People widget is very big, is there any chance to resize it or put more than one widget in the same page (ex. People and Facebook widget)
Click to expand...
Click to collapse
Launcher pro paid version (sounds like you have it) has the ability to resize the widgets. Click and hold it in position, as if you are moving it, then release and you should be given the option to resize. Not sure how well it will work with changes to LCD density though.
bisto321 said:
Launcher pro paid version (sounds like you have it) has the ability to resize the widgets. Click and hold it in position, as if you are moving it, then release and you should be given the option to resize. Not sure how well it will work with changes to LCD density though.
Click to expand...
Click to collapse
Some widgets react OK to being sized differently than their expected size, but in my experience most get fairly mangled. What I think you actually need is to increase the number of rows and columns on your desktop to accommodate the increased screen real estate. You will need to switch to Launcher Pro or ADW though. I'm running a density of 200, with 6 rows and 7 columns which works well. A lot of the Samsung widgets seem to come in at 3 rows wide, which means that with a 6 row desktop you can now put 2 of them side by side.
I'm using ADW.Launcher with 200 instead of 240 LCD density, it works beautifully well in both portrait and landscape orientations !
Sent from my GT-P1000 using XDA App
Never had any issuewith widgets not working after changing the density, especially LPP widgets. They worked perfectly at 200 on the Tab and my Desire
Sent from my GT-P1000 using XDA App
If I change it to anything below 240 and open the stock email app, I get a little gap in the bottom when its in landscape. That's the only reason I don't use it
Sent from my GT-P1000 using Tapatalk
ayman07 said:
If I change it to anything below 240 and open the stock email app, I get a little gap in the bottom when its in landscape. That's the only reason I don't use it
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Agree that's a pitty, but then again I'm pleased to notice that most Galaxy Tab apps works without to much scaling problems on all densities. That's a big difference with the Galaxy S phone variants. On the Galaxy S variants most Samsung apps get all f'ed up with a different density.
I hope Google will support variable densities in the upcoming Android versions.
While a friend was using my tab, they changed the density to 100 (Thanks!). This caused my tab to reboot constantly and I cannot keep it on long enough to change LCD Density back.
Can anyone give me the files need to push from adb to change my density back to normal? Is it build.prop or something like that?
EDIT: I managed to adb pull my build.prop and edit it, but when I try to push it back I get permission denied.
when trying to mount with adb shell using mount /system -o rw,remount I get a usage error.
ninja4hire said:
While a friend was using my tab, they changed the density to 100 (Thanks!). This caused my tab to reboot constantly and I cannot keep it on long enough to change LCD Density back.
Can anyone give me the files need to push from adb to change my density back to normal? Is it build.prop or something like that?
EDIT: I managed to adb pull my build.prop and edit it, but when I try to push it back I get permission denied.
when trying to mount with adb shell using mount /system -o rw,remount I get a usage error.
Click to expand...
Click to collapse
Not sure why your remount isn't working assuming you have root permissions. I presume you've typed something like this?
Code:
# su
# mount -o remount,ro -t rfs /dev/block/stl9 /system
(apologies if I'm teaching you to suck eggs), or are you trying to do it directly via adb? If so then you could always copy the build.prop file from /system to something writeable like /mnt/sdcard - edit it (or pull it with adb and edit it) then remount /system as rw and copy it back. Lots of ways really.
An alternative which I often use when not near a computer is to just edit the file using Root Explorer - a very useful tool though may not be an option for you right now if you can't actually launch the device . btw - I had issues with LCD Density app after the flash of the latest EU JM6 FW and found the manual edit was the only way it would persist over reboots. Not sure if that's just local to me as no-one else seems to have issues, but something to bear in mind if it happens to anyone else.
paulshields said:
Not sure why your remount isn't working assuming you have root permissions. I presume you've typed something like this?
Code:
# su
# mount -o remount,ro -t rfs /dev/block/stl9 /system
(apologies if I'm teaching you to suck eggs), or are you trying to do it directly via adb? If so then you could always copy the build.prop file from /system to something writeable like /mnt/sdcard - edit it (or pull it with adb and edit it) then remount /system as rw and copy it back. Lots of ways really.
An alternative which I often use when not near a computer is to just edit the file using Root Explorer - a very useful tool though may not be an option for you right now if you can't actually launch the device . btw - I had issues with LCD Density app after the flash of the latest EU JM6 FW and found the manual edit was the only way it would persist over reboots. Not sure if that's just local to me as no-one else seems to have issues, but something to bear in mind if it happens to anyone else.
Click to expand...
Click to collapse
yeah the problem goes deeper. So I figured out that my tab is no longer rooted, and I can't root it again because I cannot put it back into debug mode. The system restarts itself before I can get to that screen.
I managed to adb pull, but I can't push back because I cannot gain permission. This may be the second tab I return for a new one.
ninja4hire said:
yeah the problem goes deeper. So I figured out that my tab is no longer rooted, and I can't root it again because I cannot put it back into debug mode. The system restarts itself before I can get to that screen.
I managed to adb pull, but I can't push back because I cannot gain permission. This may be the second tab I return for a new one.
Click to expand...
Click to collapse
Are you able to launch an app before your tab reboots?
unfortuately not really. I have been able to get to the launcher menu for a second, but then it reboots.
ninja4hire said:
yeah the problem goes deeper. So I figured out that my tab is no longer rooted, and I can't root it again because I cannot put it back into debug mode. The system restarts itself before I can get to that screen.
I managed to adb pull, but I can't push back because I cannot gain permission. This may be the second tab I return for a new one.
Click to expand...
Click to collapse
If you can get an adb pull then you should be able to run a root script. There is a script posted in this section for installing clockworkmod via a Windows bat file or a Linux/OSX shell script. I personally had issues with the recovery part of the script and would not recommend running the whole process, but the bits that do the rooting worked well for me. It was simply a case of removing the section that added the recovery files and then it rooted fine. You could try that. Edit the run.sh or run.bat file and remove the section that pushes the recovery files. For run.sh you'd delete
Code:
if [ "$buildid" == "FROYO" ]; then
echo Push clockworkmod redirector files to device
echo
$adb push bin /system/bin/
echo Set permissions on clockworkmod redirector files
$adb shell chmod 755 /system/bin/recovery
$adb shell chmod 755 /system/bin/recoveryfiles
$adb shell chmod 755 /system/bin/recoveryfiles/*
$adb shell chmod 755 /system/bin/recoveryres
$adb shell chmod 755 /system/bin/recoveryres/*
echo
fi
or for run.bat remove
Code:
IF "%buildid%"=="FROYO" (
echo Push clockworkmod redirector files to phone
echo.
adb push bin /system/bin/
echo Set permissions on clockworkmod redirector files
adb shell chmod 755 /system/bin/recovery
adb shell chmod 755 /system/bin/recoveryfiles
adb shell chmod 755 /system/bin/recoveryfiles/*
adb shell chmod 755 /system/bin/recoveryres
adb shell chmod 755 /system/bin/recoveryres/*
echo.
)
Your mileage may vary and I take no responsibility etc etc (I've only tested the Mac/Linux script and not the Windows batch file), but may be worth a punt before you look at returning it.
ninja4hire said:
unfortuately not really. I have been able to get to the launcher menu for a second, but then it reboots.
Click to expand...
Click to collapse
****, I know the problem. That's why I advice users in the help (i'm the developer of LCD Density Changer) to first do a preview before changing the system density. I used to have a so called boot monitor exactly for these problems.
I will put up an extra warning in the app or maybe force a preview before users can safe the density. Anyway, sorry for the trouble.
But why don't you flash some new firmware with odin or with kies?
Thanks paulshields, I'll try what you said and post my results.
appelflap said:
****, I know the problem. That's why I advice users in the help (i'm the developer of LCD Density Changer) to first do a preview before changing the system density. I used to have a so called boot monitor exactly for these problems.
I will put up an extra warning in the app or maybe force a preview before users can safe the density. Anyway, sorry for the trouble.
But why don't you flash some new firmware with odin or with kies?
Click to expand...
Click to collapse
Unfortunately I am using the VZW tab and there is no firmware yet. If all else fails I can wait, for something to come out for my the my tab. Also don't worry I am not blaming you or anyone for that matter. Hopefully I get this fixed!
The script doesn't seem to be working. I think it's because I'm not in debug mode (which I can't get to). Thanks anyway.