Develop Bugs

JIT ENABLED and working

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

JM6 & LCD Density

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.

Square Enix Chaos Rings (Force Close Root Workaround)

Hey, just in case anyone else shelled out the money for SE's new Android release, Chaos Rings and couldn't play due to being rooted...
All you need to do to be able to play is rename your SuperSU.apk/superuser.apk in the /system/app folder (I just added, ".bak" to the filename) and the force close will end. Of course, you will probably want to rename the apk back to normal once finished
EDIT:
Cooldoud has a script on post #5 which, with Script Manager, should offer a widgetable solution to quickly renaming the superuser/supersu apk

rmikulus said:
Hey, just in case anyone else shelled out the money for SE's new Android release, Chaos Rings and couldn't play due to being rooted...
All you need to do to be able to play is rename your SuperSU.apk/superuser.apk in the /system/app folder (I just added, ".bak" to the filename) and the force close will end. Of course, you will probably want to rename the apk back to normal once finished
Click to expand...
Click to collapse
Sounds like a job for a bash script and Anycut. Would hate to have to do that manually all of the time...

garwynn said:
Sounds like a job for a bash script and Anycut. Would hate to have to do that manually all of the time...
Click to expand...
Click to collapse
OOH how difficult is it to do? Would be nice to automate

rmikulus said:
OOH how difficult is it to do? Would be nice to automate
Click to expand...
Click to collapse
Renaming is easy - busybox mv <source> <dest>
It's calling the app that I'm not certain about.

Yep found that out too... Really can't figure out why they went through the hassle of implementing such a lame system... Anyway, I wrote the below script for my gnote, it will toggle supersu so you can use the same widget to enable and disable supers.
After that install script manager, and set the script to be executed as root. You can then just create a widget to easily access the script
Code:
mount -o remount,rw /system
if [ $? -ne 0 ]; then
echo "Failed to remount /system as rw"
exit
fi
if [ -f "/system/app/Superuser.apk" ]; then
echo "Disabling Superuser App..."
mv /system/app/Superuser.apk /system/app/Superuser.bak
mount -o remount,ro /system
echo "All Done"
else
echo "Enabling Superuser App..."
mv /system/app/Superuser.bak /system/app/Superuser.apk
mount -o remount,ro /system
echo "All Done"
fi

I tried making it into a .sh and running it on script manager but it didnt work. kept saying line errors.

Metalshadowx2 said:
I tried making it into a .sh and running it on script manager but it didnt work. kept saying line errors.
Click to expand...
Click to collapse
You must make sure you convert your newline characters to Unix format. Wondows-style newline will cause the error you're getting (well if we're talking about the same error )
You can use notepad++ or Google dos2unix for a command line tool.
Sent from my GT-N7000 using xda app-developers app

Shouldn't this be in the apps section?
Sent from my SPH-D710 using xda premium

Probably yes, might also want to take it out of the Epic 4G section and move it to general Android as this is going to affect all devices

That's what I was just thinking...
Sent from my SPH-D710 using xda premium

cooldoud said:
Yep found that out too... Really can't figure out why they went through the hassle of implementing such a lame system... Anyway, I wrote the below script for my gnote, it will toggle supersu so you can use the same widget to enable and disable supers.
After that install script manager, and set the script to be executed as root. You can then just create a widget to easily access the script
Code:
mount -o remount,rw /system
if [ $? -ne 0 ]; then
echo "Failed to remount /system as rw"
exit
fi
if [ -f "/system/app/Superuser.apk" ]; then
echo "Disabling Superuser App..."
mv /system/app/Superuser.apk /system/app/Superuser.bak
mount -o remount,ro /system
echo "All Done"
else
echo "Enabling Superuser App..."
mv /system/app/Superuser.bak /system/app/Superuser.apk
mount -o remount,ro /system
echo "All Done"
fi
Click to expand...
Click to collapse
Anyway, big ups to cooldaud, your script works great for me! Had to change "Superuser" to "SuperSU" but everything is great! SMWidget ftw as well

Well so ironic SE would punish rooted android users and not GAF on ffxi hackers still -.- Meh I only speed hack moderately anyway...have you tried traveling otherwise? Soooo slow >.<
Sent from my SPH-D710 using XDA

Hi, tried this script on galaxy note 10.1, all went well and tablet acts like non rooted, but still supersu app in the app drawer and the game crashes as usually

cooldoud said:
You must make sure you convert your newline characters to Unix format. Wondows-style newline will cause the error you're getting (well if we're talking about the same error )
You can use notepad++ or Google dos2unix for a command line tool.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
ok i did and now i get this error

Looks like you're not using the busybox binaries. Maybe try replacing "mount" by "busybox mount"? Problem is I don't know what shell you'd be using so that might still not be working. Are you using the international Note? What ROM?
Also double check whether you're using SuperSU.apk or Superuser.apk as your root configuration tool.

I have no idea how all these scripts work, so I just tried to change the name of my superuser.apk, but for the life of me I can't figure out how to do that. My phone insists that I have insufficient privileges to rename it...

It seems that they finally added "*This game cannot be played on rooted devices." to the app description, it was not there yesterday

Well, I went and researched scripts. Got this script to work. (Had to add "busybox" before "mount")
Checked that the app does get renamed to .bak, and yet I still get a force close when i press start. I guess I'll just have wait for SE's patch.

It's important to check that the application is not appearing in your app drawer anymore (if your launcher can detect the app, so can SE... ) . Go there and check, if the app is still appearing it means it is still accessible (not sure whether you then need a reboot for it to disappear or something?), if it's not there... it means SE is also checking some other stuff to determine whether you're rooted, but I have no idea what that would be.

Ah yes, that's it. It still shows in my app drawer. Reboot didn't help. Trying searching the issue, came up with nothing. I guess I'm not meant to play this game just yet lol. Thank for trying to help!

[MOD] Calendar with text in month view (odex/deodex)

Good evening folks,
here is my Calendar text-mod (14.71.8) for having all appointments with text and not as bars in month view. You may apply this mod in every ROM, equal if odexed (stock) or deodexed ROM.
I'll guide you step through step as we got no CWM recovery yet, so you must do it manually.
- download Calendar.apk and move it to your internal SD card with an explorer or via adb:
Code:
adb push Calendar.apk /sdcard/
- after that type in the following commands, beware that su wants you to grant root access (SuperSU popup)
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/Calendar.apk /system/app/
rm /system/app/Calendar.odex
mount -o ro,remount /system/ /system/
reboot
Done! Enjoy this mod
Reminder: Although this mod was tested on my device, I'll take no responsibility if you damage your system, so just do it if you know what you do!
If we have CWM, I will provide a flashable .zip then.

Could you update this post for the new build, greatly appreciated. As well would it be possible to just create an Xposed module instead so that this doesn't need to be updated as frequently?

I haven't updated to the new build so I wait for someone who makes a system dump, odex or deodex is equal to me.
Not interested in Xposed, because when you have AppSettings enabled, you don't need this mod, you only need to set the settings for Calendar to a dpi <= 213 (tablet mode).

shaftenberg said:
I haven't updated to the new build so I wait for someone who makes a system dump, odex or deodex is equal to me.
Not interested in Xposed, because when you have AppSettings enabled, you don't need this mod, you only need to set the settings for Calendar to a dpi <= 213 (tablet mode).
Click to expand...
Click to collapse
I've tried using App Settings for the calendar, however changing the dpi to 320x480 does nothing and manually inputting a dpi of 213 just makes everything bigger.

Try 1280x800, dpi 213

shaftenberg said:
Try 1280x800, dpi 213
Click to expand...
Click to collapse
Just tried that as well, the text version seems to work however everything is too over-sized as seen below.

raddacle said:
Just tried that as well, the text version seems to work however everything is too over-sized as seen below.
Click to expand...
Click to collapse
Man, you should study the AppSettings guide lower the font size and you are done.

shaftenberg said:
Man, you should study the AppSettings guide lower the font size and you are done.
Click to expand...
Click to collapse
Haha thanks, yea I just messed around with it. All figured out!

It would be great if a flashable .zip was uploaded
Thank you for your work

mine shows failed for /system/app/calendar.odex when i type the rm /system/app/Calendar.odex
PS. my device is a xt1033 from brazil, rooted and with stock rom

Just copy file u download to system/priv-app and set right permission and reboot. Done.
Sent from my XT1033

shaftenberg said:
Man, you should study the AppSettings guide lower the font size and you are done.
Click to expand...
Click to collapse
First, thanks for the modified calendar app!
Newbie question: Where can I find this "AppSettings" -- an app, I presume? I tried looking for it on the play store and I can't find it.
THANKS!

[Non-Gapps-Solution] To broken home, statusbar, QT, etc

EDIT: Skip to the bottom EDIT for the short version..
Preamble: I searched for a fix to this recently and over the past 10 months and haven't seen any real solutions to this. Most people have probably experienced this issue at some time flashing roms, especially those people running gapps-free Android :highfive: such as myself. A band-aid for fixing this is running gapps' SetupWizard and/or CM's CMAccounts, I started adding CMAccounts.apk to /system/app some months ago to fix this. I was never satisfied with this workaround though since it doesn't narrow down the actual problem, and I really like sticking to the AOSP experience, open-source, no Stasi-esque permissions, and without the need to taint my installation just to set it up (setupwizard does a lot more than you might think).
Using some additional skills I didn't have 6 months ago, I finally isolated the issue to the SQL database /data/data/com.android.providers.settings/databases/settings.db, table global, value name device_provisioned. It is set to "0" by default which leads to all these ridiculous problems, and setting it to "1" + a reboot fixes all of these problems for me. Setting it back to "0" + reboot breaks everything again, back to "1" fixes, provision.apk present or removed.. I searched for (sqlite3 dump | grep) lots of other provision and setup value differences... tested this a lot.
!!!BACKUP /data/data/com.android.providers.settings/databases/settings.db before attempting this. Use 'busybox cp -p /data/data/com.android.providers.settings/databases/settings.db Your_Backup_Location' to copy and keep correct permissions on it. I would do a nandroid backup maybe anyway. This should be harmless or very helpful, but it's a su'd command in depths of /data so ya never know.
A couple simple ways to get this set right since you can't reliably grep'n'sed here: Get a nice free sql-frontend app off fdroid or xda -very handy- and go to the settings.db file, 'global' table, and then find or add "device_provisioned" in the name column and "1" in the value column. Root Explorer has this built in I think. The better way though is to pull up the 'adb shell' terminal remotely or use a terminal emulator from the phone with free && adfree Jack Palevich's Terminal Emulator, Spartacus Rex' Terminal IDE (recommended ...for everything!), anything using a jni_exec java execute emulation command. Also Ghisler's Total commander file manager has a built-in command line for convenient executions (or cool shell-script shortcuts you can make --it was actually the first tasker).
# Enter each command line by line (after '>'):
Code:
>su
>$(which sqlite3) /data/data/com.android.providers.settings/databases/settings.db
>update global set value="1" where name="device_provisioned";
>.quit
>exit 0
# One-liner
Code:
su && $(which sqlite3) /data/data/com.android.providers.settings/databases/settings.db 'update global set value="1" where name="device_provisioned";'; exit 0
Then just reboot, enjoy that home softkey that takes you to your launcher home.. your notification bar that displays your notifications. lol such basic s***.
Hope this can help someone else out as much as it did me. You don't have to use gapps/setupwizard to fix it! I also want to make sure there isn't another rogue SQL.db value. (btw if you happen to read this and have a broken back softkey/button, your problem is likely the lib file /system/lib/jni_latinime.so. Thought I'd throw that out there.)
EDIT: Heres an update short version. I added another sqlite value that needs correcting in ROMs without gapps setup bla installed. Run these commands in terminal emulator or via adb. Just copy and paste, they need to be exact.
Check that the values on the right are "1" when you fire off:
Code:
su -c '"$(whence -p sqlite3)" /data/data/com.android.providers.settings/databases/settings.db '\''select * from global where name="device_provisioned"; select * from secure where name="user_setup_complete";'\'
Otherwise or just to be safe, fire off this wicked one liner(Warning: reboots when finished):
Code:
su -c '"$(whence -p sqlite3)" /data/data/com.android.providers.settings/databases/settings.db '\''update global set value="1" where name="device_provisioned"; update secure set value="1" where name="user_setup_complete";'\'' && sync && fsync /data; sleep 3; svc power reboot'
Done, 1-2 steps.

Great write up and worked perfectly. Any more tips tricks advice or links for non-gapps users?

namtombout said:
Great write up and worked perfectly. Any more tips tricks advice or links for non-gapps users?
Click to expand...
Click to collapse
Yeah man, glad it worked. Cheers to your cojones for trying it!
What I usually do for a no gapp solution is:
-grab the libjni_latinime lib from microgapps cause its needed for the aosp keyboard swipe usually
-use "gapps browser" for Google related stuff like gmaps.
-or use rmaps (this and gapps browser need the maps api, so you gotta pull the google maps framework jar or use the "no-gapps project" hack api /system/framework/*google*jar. Make sure to add the corresponding /etc/permissions/*google*xml files too)
-instead of gmail I use the standard email client of k9
-instead of play I use fdroid, aptoide sometimes, nextwap.net, or mobilism forums, or a lucky patcher cracked Google play. (careful with the non-fdroid ones)
Sorry bout this 6 month late reply, Jesus I gotta watch my posts more closely.