Database Users

How do I "completely" remove Sense/Rosie from FreshToast 1.1?

I have so far only deleted Rosie.apk and all of the HTC widgets.
I do not like the AOSP look of say... DarchDroid, I like the HTC touches here and there, but without Sense UI.
I'm getting Force Closes now. I can't find the apk associated with the FC'es.
HTC Widget Download Manager (process com.htc.RosieUtility)

poor_red_neck said:
process com.htc.RosieUtility
Click to expand...
Click to collapse
im not sure, but didnt you just answer your own question? im probably wrong, but i think thats it. use root explorer and go on a deleting spree...

I wish it were that easy! lol
I searched all the directories for that file (com.htc.rosieutility) and its nowhere to be found.

I actually searched for *rosie* and all it came up with was:
/sdcard/rosie_scroll
/sdcard/download/Rosie_Icons.zip

Jesus ive searched the phone high and low. I am so ****ing lost. I dont know wtf is going on here.

was your search global? it seems you only searched your sd card...
why not just leave rosie and use helix? seems to me itd be the most stable.

The rom without rosie is very stable.. The only issue you will have is when you boot up, youll have 1 force close. After that the only time it comes up is if you are downloading something from the market. Which it doesnt even always come up.
For the most part the force close doesnt even mean much. I just got used to it being there. I never cared to look into it. But i will now.
Edit: also comes up when uninstalling something. but i dont do that much

Have you tried deleting
HtcAddProgramWidget.apk

hey fyi ic3 is completely aosp, and has fixed the utility issue. check his thread out, ppl seem satisfied.

Im pretty sure i figured it out
delete these
HtcAddProgramWidget.apk <-- If you havent already
com.android.launcher2.apk <-- I think this is what did it
I read the ice rom thread and all he did was use an older version of Launcher, so I just deleted it and rebooted without getting a force close (first time its worked)

I think that did it!
Sweet!
Yeah, I was getting the one FC at boot, and sometimes in the market, but I was also getting it while in the browser, sometimes in People, other times just at random.
I am using Helix.
So far so good.
Thank you!!!

mountaindont said:
hey fyi ic3 is completely aosp, and has fixed the utility issue. check his thread out, ppl seem satisfied.
Click to expand...
Click to collapse
I tried ic3....
I'm just not a fan of completely AOSP. I like the touch of HTC apps here and there.
I'm slowly getting FreshToast exactly how I want it.
Its super fast, and getting more and more stable even with JIT.
The only other thing I'm trying to narrow down is this memory leak type issue.
Sometimes with NO active running services or apps, the available RAM will drop as low as 55MB, then withing a few minutes I'll check it and it'll go back up to 70-80MB. Doesn't seem to affect performance too much, and I'm COMPLETELY taking a stab in the dark here but maybe has something to do with JIT?
I dunno. I'm going to try and disable JIT and see if the available RAM stays in the 60-70 range.
I just removed the HTC Mms.apk with the AOSP Mms.apk to try and cut back on keyboard lag.
I tried going with the AOSP/standard keyboard... I think ive just been typing on the HTC_IME keyboard for way too long that my muscle memory has been trained to it. I keep screwing up with the vanialla keyboard. Also the spell correct doesn't seem to work as well as it does the HTC keyboard. I have no vibration or sound, as well as no key preview to try and cut back on lag.
It seems that the actual spell correction is what is lagging the keyboard down so bad. If I turn off all spell correct/auto complete it seems to be much snappier.

poor_red_neck said:
I tried ic3....
I'm just not a fan of completely AOSP. I like the touch of HTC apps here and there.
I'm slowly getting FreshToast exactly how I want it.
Its super fast, and getting more and more stable even with JIT.
The only other thing I'm trying to narrow down is this memory leak type issue.
Sometimes with NO active running services or apps, the available RAM will drop as low as 55MB, then withing a few minutes I'll check it and it'll go back up to 70-80MB. Doesn't seem to affect performance too much, and I'm COMPLETELY taking a stab in the dark here but maybe has something to do with JIT?
I dunno. I'm going to try and disable JIT and see if the available RAM stays in the 60-70 range.
I just removed the HTC Mms.apk with the AOSP Mms.apk to try and cut back on keyboard lag.
I tried going with the AOSP/standard keyboard... I think ive just been typing on the HTC_IME keyboard for way too long that my muscle memory has been trained to it. I keep screwing up with the vanialla keyboard. Also the spell correct doesn't seem to work as well as it does the HTC keyboard. I have no vibration or sound, as well as no key preview to try and cut back on lag.
It seems that the actual spell correction is what is lagging the keyboard down so bad. If I turn off all spell correct/auto complete it seems to be much snappier.
Click to expand...
Click to collapse
it sounds like compcache is working

So is the memory increase a result of compcache compressing the data to the ramz swap space? Or the opposite? Ive been reading on google code about compcache and of course, I cant wrap my redneck head around it.
I seem to def. like this better than autokiller. ROMs with autokiller seem to kill active running apps too much, especially with the browser if there were a few flash ads on the site. It would just randomly close.
The only thing I'm doing now is going through the com.htc.resources.apk and changing the green to blue. I'm hoping its easy enough of just editing the pngs to blue. Im sure though, somewhere Im going to have to edit some xml files somewhere that have a color hex associated with it. Im just not a fan of green, and am getting sick of it hah. I like blue

is there any way you can compile a signed update that i can flash, that is exactly what you have, Fresh Toast 1.1 with no Sense and JIT enabled..?

I'd be more than happy to, if I knew how to!
I assume it would just be an update script, but i've never done that before.

poor_red_neck said:
I'd be more than happy to, if I knew how to!
I assume it would just be an update script, but i've never done that before.
Click to expand...
Click to collapse
Just make a nandroid of your rom.. Dont include the ext partition. And maybe delete some personal stuff. lol
You could make a nandroid.. Then boot up again, delete all personal stuff and sign out of everything. Make another nandroid (the one you can send to people). And then flash back to your nandroid of all your personal stuff back on it.

I think it would be easier to just make a tutorial as I didn't really do anything that hard. Just removed some files here, replaced some there, and re-configure some stuff.
As a matter of fact it may be easier to just zip a bunch of files, and make a batch file to do it, as pretty much everything was done through ADB.
I don't like the idea of nandroid, wouldn't want to accidents include some paid app, or risk personal data getting in there.
Actually I'm going to read up on making update zips. Sent from my HERO200 using the XDA mobile application powered by Tapatalk

[FIX] Tnt mod based orientation fix for games

Weeds2000 fixed the orientation on our Folio100 to work with games like Asphalt5 and now its possible to play, although graphics are still kinda messed up. but other games like the 3d tilt works nearly perfect now too.
you might find it useful, and VEGAn mod might be able to include this as my FolioTntMod is based of the TNT framework...
Find the download patch i made for our folio in this thread.
it also include a full 360 rotation fix, if you need it
As we all share the same Tegra2 platform and can nearly swap experience here, im posting this to share the fixes weeds2000 made for us...
Hope you find it useful..
Note:
The patch i made might actually work fine as update.zip on your tablet as well, or might need minor adjust to install, but let g tablet modders fix this if needed.
at least now you know its available.

Thank you! One question - do you know what file(s) were altered for the 360 rotation fix? Was it a lib file, for example?
EDIT: Also, to any other modders looking at this, the system.img is a ext2 filesystem image, NOT a yaffs2 image.

roebeet said:
Thank you! One question - do you know what file(s) were altered for the 360 rotation fix? Was it a lib file, for example?
EDIT: Also, to any other modders looking at this, the system.img is a ext2 filesystem image, NOT a yaffs2 image.
Click to expand...
Click to collapse
Roeby wan Kanobi, is this something that could work and be added to TnT Lite? My Clockwork back up just completed

Yes, I can package it as a supplement - I just need to know what to package.
Getting my dev unit ready with TnT Lite 3.1.2. There's also a new music player apk I need to test out.

roebeet said:
Yes, I can package it as a supplement - I just need to know what to package.
Getting my dev unit ready with TnT Lite 3.1.2. There's also a new music player apk I need to test out.
Click to expand...
Click to collapse
This could be another watershed update Also- with the accelerometer corrected, folks will be getting exercise by holding up the G while playing games
added:
Perhaps the one extra update that would be nice is a DSP manager so dB level or gain increases can be made. Modders released a DSP manager on the Incredible that allows increases to 3.5mm and speaker output. Hardware based EQ too.
Perhaps being too picky, but louder speakers would be nice.

Did you see.. they provided the SOURCE!!!!! This is what we need!
roebeet said:
Yes, I can package it as a supplement - I just need to know what to package.
Getting my dev unit ready with TnT Lite 3.1.2. There's also a new music player apk I need to test out.
Click to expand...
Click to collapse

What does the patch change? Would is break things when the application developer fixes the orientation code in their game.
We saw this problem fixed in the application in the Gallery 3D application by google, not in framework. http://android-developers.blogspot.com/2010/09/one-screen-turn-deserves-another.html

roebeet said:
Yes, I can package it as a supplement - I just need to know what to package.
Click to expand...
Click to collapse
okay here are some details.
the framework.jar modified comes from this file: update-smb_a1002-3338-user.zip
the library should be generic, but is required for the gsensor/rotation/orientation fix as part of the new framework.jar changes.
the 2 primary folders in the framework.jar changed are /android/hardware /android/view
you should be able to easily spot the differences in filesizes..
do note: there is another change android\os\Environment.smali as i modified it to work with /mnt/sdcard and /mnt/sdcard/sdcard-disk0 and /mnt/usbdisk-disk0 for compatibility with folio mount functionality.
here is the "vold" also different but works fine with the tap'n'tap framework.
remember that /etc/vold.fstab needs changed to support the more new mount devices if you wish to use that one too.
360 rotation fix is in android\view\WindowOrientationListener$SensorEventListenerImpl.smali
orientation fix is
android\hardware\SensorManager*.smali
but again, the framework.jar is Tap'n'Tap based, so works directly on top of r3338 edition.. and i made a patch in my section with just framework + lib files included.

rothnic said:
We saw this problem fixed in the application in the Gallery 3D application by google, not in framework. http://android-developers.blogspot.com/2010/09/one-screen-turn-deserves-another.html
Click to expand...
Click to collapse
No, as far as i understand, weeds2000 only made the hardware swap sensor reading, so now it acts like a portrait mobile phone, where our Tegra2 has the chip rotated once 90degree.

Dexter_nlb said:
No, as far as i understand, weeds2000 only made the hardware swap sensor reading, so now it acts like a portrait mobile phone, where our Tegra2 has the chip rotated once 90degree.
Click to expand...
Click to collapse
Hmm, so it does a 90 degree rotation. And the device is still a default landscape device. We definitely need to make sure there are no negative effects on games that utilize the acceleromether and worked fine before.
I would assume that the android developers would recommend making this change to framework, instead of handling it in applications if there weren't implications.

Thanks for the explanation - this is something I suspected would fix it, but it's good to see that someone had pushed the idea all the way through to an actual fix.
So, I suspect that when the device boots up, it should be in portrait mode initially (until the sensor kicks in).

roebeet said:
So, I suspect that when the device boots up, it should be in portrait mode initially (until the sensor kicks in).
Click to expand...
Click to collapse
That makes more sense to me if that is true.

I read through the code ... Prior to the code change they were performing the rotation either for Acceleration minus Gy on the y-axis
or Acceleration minus Gz on the z-axis and NOT Acceleration minus Gx on the x-axis. Now the axis swap is always occurring... under all 3 conditions irregardless of sensor.
Dont know why there was an exclusion in the first place for Acceleration minus Gx on the x-axis...
When I get back I will look through the code some more...
rothnic said:
Hmm, so it does a 90 degree rotation. And the device is still a default landscape device. We definitely need to make sure there are no negative effects on games that utilize the acceleromether and worked fine before.
I would assume that the android developers would recommend making this change to framework, instead of handling it in applications if there weren't implications.
Click to expand...
Click to collapse

rothnic said:
I would assume that the android developers would recommend making this change to framework, instead of handling it in applications if there weren't implications.
Click to expand...
Click to collapse
if Google didn't "invent" the different way of reading sensors, there would only be one way of doing it, so developers would not be able to see it, so an update to like 2.2 or higher is now an requirement, right? but if older games do not check, it would work with them, so this fix solves it as i see it.
putting back androidos orientation handling to its original state, as many developers should be reading it.

I have ported the fix for both TnT stock and lite. As well as Vegan beta 4.
http://forum.xda-developers.com/showthread.php?t=892345

gojimi said:
I have ported the fix for both TnT stock and lite. As well as Vegan beta 4.
http://forum.xda-developers.com/showthread.php?t=892345
Click to expand...
Click to collapse
remember its all done by weeds2000 , i cannot/will not take credits for his effort here, i am just sharing the good work done on this fix.

I have released a new version of the fix, this should clean up all the remaining issues with the accelerometer/compass. Code is also much cleaner now. Some weird hacks you may have seen were caused by the legacy API which was used by my test game.
Only known issue up to now is that the mouse coordinates are also rotated.
The source can be found in the zip file attached to the original post, I hope that all changes are prefixed with // XXX:
The source files are based on the nvidia-froyo tree.
Link:
http://forum.xda-developers.com/showpost.php?p=10209624&postcount=38

Doodle jump doesn't work. Game loads upside-down with home buttons on top. If you tilt left you go right...Any fix for this?

Does this work for the VegaN Ginger Edition, or is that fix built into the ROM, I think I am having issues with some games on that ROM.

bmw4aaron said:
Doodle jump doesn't work. Game loads upside-down with home buttons on top. If you tilt left you go right...Any fix for this?
Click to expand...
Click to collapse
I think you can write the developer and tell , that the games is not working normally.. all other games work fine, so why would one game stand out, only reason, bad programming, or misunderstanding of androidOS and orientation. maybe developer thought he should fix the "orientation" in his game on tablet, and forgot other trying to make it reverse.. so: bad programming and choice of developer..he should follow guidelines and not his ideas.

CPU maxing @ full speed, 100% load after 24-48 hrs? FIX FOUND!

First off, I cannot take credit for finding this, I was referred to a bug report thread on the Google Android site by XDA user aweaver33, who I thank VERY much for pointing me on the right direction.
So, several of us have had this issue with various custom kernels, where after typically 24-48 hours, the phone would slow to a crawl. If you were to open an app like System Panel, you would see that the CPU load was pegged at 95%+, and speed would be maxed out. You would also see that the process using all the CPU is Android System.
The problem has to do with the file "time_in_state", which literally keeps track of how much time the CPU spends at any given speed in MHz. There is a limit to the size this file is supposed to reach, 256 bytes. Once it exceeds this size, the next time Android tries to access it, it flips out and gets stuck trying, and pegs the CPU. A lot of devs and users blamed SetCPU, and it is true that SetCPU does have an EFFECT on this issue, it does NOT cause it, and indeed the issue can occur whether SetCPU is installed or not.
The issue is brought on by custom kernels that add additional frequency steps for the CPU to choose from, which causes that log file to grow. Which is why older or stock kernels will not cause this. Some ROMS incorporate a workaround so you may not have this issue.
Anyways, the issue is explained better in the link aweaver33 gave me. I will link to the original thread I posted with the conversation we had and the link he gave. I can confirm that, using the info he gave me, the issue has been fixed. I am currently just over 120 hours of uptime with no problems.
Here is the link: http://forum.xda-developers.com/showthread.php?t=1082363&highlight=stock+kernel+gpu+
EDIT: attached the script files for those who want them. You can drop one or the other (NOT BOTH) in /etc/init.d if your rom has this folder already (creating the folder and adding it won't work), or you can download Autostart (root) from the market for free, and drop the file in /data/opt (create the opt folder). This difference between the two is one runs only once at boot, the other runs every five minutes. If you use SetCPU, you need the one that runs every five mins, as every time you open SetCPU it resets permissions on the time_in_state file.

flashable zip? not everyone is comfortable with code and scripts

If I knew how, I would. I wasn't even comfortable with it. But I was so tired of the locking up, I was willing to try anything (after a Nandroid of course). I'm not sure you *could* do this in a flashable zip. I can post the script I'm using. It only runs once after reboot, unlike aweaver's, which runs every five mins (good if you're using SetCPU, as opening SetCPU resets the permissions of the time in state file).
This script should work if dropped into /etc/init.d. *If* your ROM has that folder by default. Mine does not, so I had to download a free app from the market called Autostart which is free and very small. For that app you create a folder in /data/ and drop the script in there.
Sorry guys but I'm no dev so this is the best I can do, maybe someone else can make it flashable?

would it also be fixed by simply deleteing the log file as well rather than setting it to unreadable

It can't be deleted. System instantly replaces it.

bast525 said:
It can't be deleted. System instantly replaces it.
Click to expand...
Click to collapse
:/ i suppose when it is replaced it would be with a fresh one deleting would fix it for 24-48 hours till it got filled again humm i wonder if a script could be auto executed every 12 hours to delete it rather than just make it unreadable.
Do you know if it is a problem in gingerbread as well?

mirrin said:
:/ i suppose when it is replaced it would be with a fresh one deleting would fix it for 24-48 hours till it got filled again humm i wonder if a script could be auto executed every 12 hours to delete it rather than just make it unreadable.
Click to expand...
Click to collapse
I don't think you can delete it. I can't figure out how to.
mirrin said:
Do you know if it is a problem in gingerbread as well?
Click to expand...
Click to collapse
Issue 9733 is still listed as New, so either Google hasn't fixed it in Gingerbread or they just don't bother statusing their bug reports.

Why do you feel the need to delete it? If you are trying to delete it, you are likely using Root Explorer. Why not just use that to change the permissions of the file? Tap and hold, select permissions, and unchecked all permissions except for the top left one. This will stop the bug, but the permissions will be reset after a reboot, or after opening SetCPU.
I imagine that deleting the file might actually cause FC's or may cause the same bug but I dunno since it wont delete.

dyetheskin said:
flashable zip? not everyone is comfortable with code and scripts
Click to expand...
Click to collapse
I've never created a flashable zip before, but I'd be willing to look into it if the demand is really there. The problem I see is that I'd have to make certain assumptions about how everybody's ROMs are configured. It looks like the most portable approach would be to append a line to the end of /bootcomplete.inc.rc. Do people really find it easier to boot into recovery and flash a zip than to add one line to a file themselves? Personally, I'm always hesitant to flash a zip other than a full ROM because I'd be uncertain how it interacts with other changes I've made to my system.

Inc is
not bad
But. 48hours?
Sent overrow from my Optimized Inc using XDA App

Hiding virtual keys (reframe method) and UD 1.5b3

So I just updated to UD 1.5b3. This reset my settings back to having the double sized notification bar, which annoys the crap out of me, so I used Reditus2's method:
http://forum.xda-developers.com/showthread.php?t=1114069
I used this method for UD 1.0 and it worked wonders. After running this on 1.5b3 however I am now unable to boot up as usual (can still get to recovery mode and thus was able to fix, but wanted to share this). I get as far as the UrukDroid Loading... page, trys to load for about 5-10 seconds, goes black for about 1 second, and then shows the Loading page again. I have allowed it to sit on this screen for 10+ min to no avail. Just wondering if anyone has any ideas on how to keep UD 1.5b3 without having the huge notification bar. Also wanted to give Reditus2 a chance to see this and maybe there's just an update needed to the scripting to resolve this.

I had the same problem with rc1
i gave up on reframing
at least the bar disapear when you lunch a full screen app

I'll try as well - but right, full screen works at least.

working like a charm for me on UD 1.5

have you tried this? - http://forum.xda-developers.com/showthread.php?t=1139882

I've created UD 1.5 package with smaller top buttons.
http://code.google.com/p/urukdroid/wiki/Download

enricogrim said:
Hi $aur0n I installed UrukDroid 1.5 and all worked perfectly! but today I installed package with smaler top buttons and now Urukdroid freeze while booting, it stops when in the botton of the display appears : UrukDroid 1.5 boot: switching to rootfs... How can I do? I don't want to reinstall the system from scratch.
Click to expand...
Click to collapse
Did update went ok? What has the message on top of the bar during update? What messaged you have seen during startup of device?
Anyway best/fastest/easiest etc. way is to restore rootfs from backup (RescueMenu) if you had one. Second is just to do quick reinstall of rootfs (your data will stay untouch).

@$auron:
As i never use it the search button, is there any chance of switching it off?
And wouldn't be 32 px a better solution, as normally everything alligned to 4 or 8 gets better scaled and painted on normal devices?
Otherwise, nice.

fzelle said:
@$auron:
As i never use it the search button, is there any chance of switching it off?
And wouldn't be 32 px a better solution, as normally everything alligned to 4 or 8 gets better scaled and painted on normal devices?
Otherwise, nice.
Click to expand...
Click to collapse
Hmm I've started with 28px but it looked a bit too small. I can try 32. I also don't use search button at all. I'll remove it...

enricogrim said:
Thank you very much for your quick answer. My update went ok, at the end of it on the top bar the message told me to reboot the device. But while rebooting my device (A43) freezed with the above message: UrukDroid 1.5 boot: switching to rootfs...
As I hadn't a backup I did a quick reinstall and now it seems to work well!
thank you again
Enrico
Click to expand...
Click to collapse
How long did you wait?
I remember the first time I updated the framework with Fisha21's one, it took a while to boot up on the first boot. Apparently android was rebuilding the dalvik cache with the new framework.

$aur0n said:
I've created UD 1.5 package with smaller top buttons
Click to expand...
Click to collapse
Thank you for this package ! I was trying to make my own framework-res but I always fail

fzelle said:
@$auron:
As i never use it the search button, is there any chance of switching it off?
And wouldn't be 32 px a better solution, as normally everything alligned to 4 or 8 gets better scaled and painted on normal devices?
Click to expand...
Click to collapse
32px height buttons, I've also made them shorter - 70px instead of 80px. Sadly removing search is not so easy (I don't know if I will have time to look further).
UrukDroid-1.5-32pxButtons.tbz2

Thanks for trying.
Don't hurry.

$aur0n said:
32px height buttons, I've also made them shorter - 70px instead of 80px. Sadly removing search is not so easy (I don't know if I will have time to look further).
UrukDroid-1.5-32pxButtons.tbz2
Click to expand...
Click to collapse
It's probably easier and quicker to remove them all and use button savior

sibere said:
It's probably easier and quicker to remove them all and use button savior
Click to expand...
Click to collapse
Yes (I still use ButonSavior - even with buttons on top, because they can disappear on some apps) - but less universal..
ps. I know where to remove search button (or any other) but system refuses to accept new framework - probably once again this ****ty certificates issue !

Thanks aur0n, the button package works great! !!!

@$auron
32px work better, as now batterie and wifi are next to each other instead of ontop.
Have deinstalled buttonsaior, as this together with std buttonmode (longpress power) is enough for me.
Thaks again.

Hey $aur0n, thanks for the link to the package! Definatly going to try it as soon as I figure out what happened to my /data/urukupdate folder. Just disappeared on me. Whole /data folder is empty.

kurigami said:
Hey $aur0n, thanks for the link to the package! Definatly going to try it as soon as I figure out what happened to my /data/urukupdate folder. Just disappeared on me. Whole /data folder is empty.
Click to expand...
Click to collapse
That's kind of unlikely - device would not work with empty /data (it would write a lot of new stuff in it during boot...)

I agree, that's why I was so confused. Did manage to find an answer on that one though. For some reason lost my SU permission for my file explorer so that's resolved. Don't suppose you might know why the kernel file isn't doing the auto-update/install once dropped into the urukupdate folder? The modified top bar you listed worked perfectly, but the Kernel file isn't automatically updating, and it looks like the new UrukConfig doesn't allow me to force the update.

Aurora Performance Tips/Tricks/Tweaks

In this thread we should share our own little tweaks to this amazing ROM.
I'll add to this first post any stuff that is proven to increase speed or makes using the ROM easier or more enjoyable
Note, this isn't intended to include mods and addons, as there is already a great thread for that
IMPORTANT:
Always backup stuff! And reboot after teaking!
Please note that, the ones I've found more useful, I add a USEFUL tag in front of them
____________________________________
BUILD.PROP tweaks
With root explorer or any other method of your liking, go to /system/ and edit the file build.prop.
- To increase max fps limit possible, add:
Code:
windowsmgr.max_events_per_sec=150
I'm not sure this one is really useful, I think android already sets this already to around 1.5x screen refresh rate. The gains could be negligible.
- Disable error checking, add:
Code:
ro.kernel.android.checkjni=0
- USEFUL Stop debugging icon from appearing in status bar (doesn't disable adb), add:
Code:
persist.adb.notify=0
- USEFUL Force home launcher into memory, add:
Code:
ro.HOME_APP_ADJ=1
_______________________________________________
OTHER TWEAKS AND TRICKS
- VERY, Extremely, Mega-USEFUL - Go to:
Code:
/system/lib/elg
Open egl.cfg and delete the 1st line (0 0 android), reboot the phone.
Everything should be much smoother, I notice this especially opening folders with a lot of icons in Apex Launcher. I think this disables the default android software rendering method and uses only GPU. Don't ask me if this is different than setting composition mode to gpu in build.prop, I don't know, I just know everything is much faster
USEFUL - Only works with Aurora 2.07+ and synaptics screen - Tweak your screen duplicate filter, like in x5settings for .32 kernels.
Go to:
sys/module/synaptics_i2c_rmi_1564/parameters/sensitivity
Open the file "sensitivity" and tweak the value. Default is 4. Higher values reduce screen flickering/jitter but screen can become less sensitive, lower values, the contrary. Personally I use 8, works very good for my fingers, adjust you value accordingly. Note, this takes effect immediately, but doesn't stick after a reboot. To make it stick after a reboot, go to "/system/etc/", open one of the scripts, I recommend "ini.qcom.post_boot.sh", and add this at the end:
Code:
echo 8 > sys/module/synaptics_i2c_rmi_1564/parameters/sensitivity
where 8 is the value you want. Save, reboot and check is the value is there, in the "sensitivity" file.
- USEFUL - Great tips on how to save battery without turning everything off (bonus, doesn't use BS calibration myth):
http://www.androidcentral.com/keeping-your-charge-how-improve-battery-life-your-android-phone

Works AMAZINGLY thank you
Edit1: Also may i ask what CPU settings do you use? any overclocks/governor?
Edit2: I got that funny text glitch just before, i decided to wipe cache and dalvik and i haven't had it again yet. Ill get a screen shot if it happens again but im pretty sure you know what i mean, all the text for apps look like squiggly lines/really odd ive seen this happen normally in previous versions of aurora but oh well ill come back with more info if anything else happens thanks again!

thank you mate. Two quick questions. If i disable kernel debugging will this affect logcat? And what cpu composition does?
Cheers
Sent from my U8800 using xda premium

spirosbond said:
thank you mate. Two quick questions. If i disable kernel debugging will this affect logcat? And what cpu composition does?
Cheers
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
Regarding the logcat, yes, probably disables that functionality, I've read in other sites, it just disables checking for errors, thus performance improvements. When I have time, I'll check if logcat is still there... the composition thing I think it tells the OS to always use GPU no matter what, I see a great improvement with that one, don't know if anything is affected, but so far, everything is great
EDIT: these tweaks were from here:
http://forum.xda-developers.com/showthread.php?t=1578065
Sent from my U8800
Here are some more:
http://www.freeyourandroid.com/guide/build-prop-modifications
If you try some, please post results, to add to first post.

spirosbond said:
thank you mate. Two quick questions. If i disable kernel debugging will this affect logcat? And what cpu composition does?
Cheers
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
Logcat still works

Added synaptics TS setting like there was in X5settings app (Touchscreen Filter).

fjsferreira said:
Added synaptics TS setting like there was in X5settings app (Touchscreen Filter).
Click to expand...
Click to collapse
hi there, i have changed it right now to value 10 and its the same, its trembling...
i have kernel v3 from Dzo 2.0.5 rom.
and have restart the phone too

r1c4rd0 said:
hi there, i have changed it right now to value 10 and its the same, its trembling...
i have kernel v3 from Dzo 2.0.5 rom.
and have restart the phone too
Click to expand...
Click to collapse
Yes, I think so, maybe it was just placebo... also, it doesn't stick after a reboot, the ROM would need init.d startup script support and a script to change the value everytime... try change it to 40 or something, and report, it it still trembles, I'll remove from the first post...

fjsferreira said:
Yes, I think so, maybe it was just placebo... also, it doesn't stick after a reboot, the ROM would need init.d startup script support and a script to change the value everytime... try change it to 40 or something, and report, it it still trembles, I'll remove from the first post...
Click to expand...
Click to collapse
will try it right now
edit: changed the value and no diference... then i restart and no diference too...

I think it doesn't work... I've changed it to 1 and notice no difference... I'll remove that thing from front post and post here if anyone wants to study it...

- Something to try, it seems not to work... - Improve synaptics screen sensitivity!
Do you miss x5Settings setting about touchscreen filter? I've been studying x5settings source code and found out what file needs to be changed to achieve the same result in Aurora. Go to:
- sys/module/synaptics_i2c_rmi_1564/parameters/
Edit the file "sensitivity" and set a value appropriate for you. I've set it to 8 and touchscreen seems better now. Maximum value I think is 64, and that works great too. I think this isn't placebo Pinch to zoom in pics doesn't "tremble" when holding the fingers on the screen as it did before, here.
EDIT: it doesn't stick after a reboot! And values change by itself, don't know why, maybe it doesn't even work... Try it for your self

fjsferreira said:
- Something to try, it seems not to work... - Improve synaptics screen sensitivity!
Do you miss x5Settings setting about touchscreen filter? I've been studying x5settings source code and found out what file needs to be changed to achieve the same result in Aurora. Go to:
- sys/module/synaptics_i2c_rmi_1564/parameters/
Edit the file "sensitivity" and set a value appropriate for you. I've set it to 8 and touchscreen seems better now. Maximum value I think is 64, and that works great too. I think this isn't placebo Pinch to zoom in pics doesn't "tremble" when holding the fingers on the screen as it did before, here.
EDIT: it doesn't stick after a reboot! And values change by itself, don't know why, maybe it doesn't even work... Try it for your self
Click to expand...
Click to collapse
hey fjsferreira if you want stick after a reboot, you must to paste this command "echo 8 > /sys/module/synaptics_i2c_rmi_1564/parameters/sensitivity" (without the quotes) into 1 of the files in /etc/init.d
number 8 is choise by us... but make 8 for this example

r1c4rd0 said:
hey fjsferreira if you want stick after a reboot, you must to paste this command "echo 8 > /sys/module/synaptics_i2c_rmi_1564/parameters/sensitivity" (without the quotes) into 1 of the files in /etc/init.d
number 8 is choise by us... but make 8 for this example
Click to expand...
Click to collapse
The problem is, there isn't an /etc/init.d :S maybe it can be added to one of the scripts in /etc/

fjsferreira said:
The problem is, there isn't an /etc/init.d :S maybe it can be added to one of the scripts in /etc/
Click to expand...
Click to collapse
yes it can...

r1c4rd0 said:
yes it can...
Click to expand...
Click to collapse
Yes, it did, thank you... now I'm waiting to see if dzo responds in Aurora thread confirming this is working. I have a sense it works somehow, damn placebo is powerful!

fjsferreira said:
Yes, it did, thank you... now I'm waiting to see if dzo responds in Aurora thread confirming this is working. I have a sense it works somehow, damn placebo is powerful!
Click to expand...
Click to collapse
yes it works, but i think its related to his new v3.0 kernel...
in .35 kernel, if i´m not worng, we can change that value.
i think placebo dont work with me lol

fjsferreira said:
Yes, it did, thank you... now I'm waiting to see if dzo responds in Aurora thread confirming this is working. I have a sense it works somehow, damn placebo is powerful!
Click to expand...
Click to collapse
I tried 8 and 10 but the flickering didn't reduce. Thanks for the tip though. I hope you get it working...
Question:
What is the difference between the mod:" get rid of cpu composition" and setting the line
debug.composition.type=gpu
at build.prop?
By making the above change doolde jump graphics where improved
Cheers

You have ro.HOME_APP_ADJ=0 to force the launcher into the memory, but wouldn't the right value be 1?

FlashTH said:
You have ro.HOME_APP_ADJ=0 to force the launcher into the memory, but wouldn't the right value be 1?
Click to expand...
Click to collapse
Correct. I've fixed it, thank you!
Sent from my U8800

i dont know if you notice, but wen the phone is charging touchscreen feels more jumpy...
can anyone confirm this?
maybe this will interest dzo in the ics port? in this site there are the amtel and synaptics drivers:
port ics input drivers
drivers from HTC Legend touch the same as desire:
drivers synaptics from htc
thanks