Related
Hello there!
I've been using my Desire Z for a long time but found the trackpad pretty useless. This is because i found the sensitivity for it pretty low so if i want to scroll down on a page it's taking forever. I also noticed if i scroll using a piece of cloth (like my shirt) the scrolling is alot faster and usable. But it's not that nice using cloth all the time.
My girlfriend has just got an new phone the Samsung Galaxy Y Pro. It also has an optical trackpad which is alot faster and usable. Also in the settings there is an option to make the trackpad faster more sensitive.
Is there any kind of application or modification to make the trackpad faster sensitiver or so?
Please let me now .
Regards
Edit: whoops i forgot to add [Q] in the topics name and i have no idea how to edit this.
Finally a topic regarding this issue!
I noticed that using certain (mostly newer, modded - CM7 for example) ROMs, the trackpad responsivess is great.
However, recently I flashed to modded stock ROM (Virtuous G-Lite) and I also find the trackpad quite useless :/
Been searching the internet for reason or solution, but found nothing
Hope to find the answer!
So if the sensitivity differs in different ROMS it's editable in a file or so. So i think it would be possible for an smart developer to create an app that edit's the values in the file to change the sensitivity with a nice slider as GUI.
Hopes it will be there someday .
I could not agree more about the trackpad, it makes me want the responsiveness of my old G1 with the trackball (but that design is prone to fail because moisture/foreign objects can easily get underneath the ball).
Would love to see some sort of customization for trackpad sensitivity become mainstream for custom roms.
I've experienced the same problem with the following ROMs:
CM 7.1.0 Stable
Virtuous v2.0.0
Virtuous G-Lite 1.6
So it's happening on AOSP and Sense based ROMs.
Just flashed G2-Slim 1.2 (see my sig for link), which seems to be the same AOSP ROM as Virtuous G-lite, but the sensitivity responsiviness seems much better.
I have no idea how the hell can it be different..
Maybe different kernels affect this?
I'm also using the G-slim ROM for a couple of days now and besides I really like the ROM the trackpad is indeed faster. But still not as fast as I would like. Let's hope some dev. Check this thread out an can help us what makes the difference in sensitivity for the trackpad!
I remember before back on android 2.2 when using the trackpad through texts depending on how fast I swiped would determine how many letters or words it would move. But now especially with roms like cm7 no matter what it'll only move over 1 letter =/ a setting to adjust sensitivity in future roms would be amazing
Sent from my HTC Vision using XDA Premium
AntSmoove said:
I remember before back on android 2.2 when using the trackpad through texts depending on how fast I swiped would determine how many letters or words it would move. But now especially with roms like cm7 no matter what it'll only move over 1 letter =/ a setting to adjust sensitivity in future roms would be amazing
Click to expand...
Click to collapse
That's exactly my problem! I don't want to move one letter if i like to i want to move 5 letters or scroll (fast) to the beginning with the trackpad. Just like it is on blackberry's or on the Samsung Galaxy Y PRO. My girlfriend get's the galaxy y pro on her birthday (27th of December) it runs gingerbread stock and has got an sensitivity option in the settings. Maybe i can break that functionality and put it in our phones. I don't know if it will work tho because the trackpad maybe differs. Still hoping a developer will look at this thread and help us out!
Ive read that the One X tends to run a lot brighter for the equivalent setting on phones like the SII.
Is it possible to tune the brightness level that the Auto setting provides, and the external light at which it "ups" the brightness - as in my opinion, HTC's setting, although wonderful, is overkill in many situations, and screen on time needs all the help it can get.
Cheers.
slvrarrow said:
Ive read that the One X tends to run a lot brighter for the equivalent setting on phones like the SII.
Is it possible to tune the brightness level that the Auto setting provides, and the external light at which it "ups" the brightness - as in my opinion, HTC's setting, although wonderful, is overkill in many situations, and screen on time needs all the help it can get.
Cheers.
Click to expand...
Click to collapse
if things aren't changed in ICS, you can decompile the /system/framework/framework-res.apk and then edit some xml's in it. Compile it again with the modified xml's and at last adb push it into the system partition. and this procedure requires a unlocked system partition.
if you don't want to unlock / don't know how to edit the stuff, the most feasible way is to put a brightness widget on homescreen and change it manually.
slvrarrow said:
Ive read that the One X tends to run a lot brighter for the equivalent setting on phones like the SII.
Is it possible to tune the brightness level that the Auto setting provides, and the external light at which it "ups" the brightness - as in my opinion, HTC's setting, although wonderful, is overkill in many situations, and screen on time needs all the help it can get.
Cheers.
Click to expand...
Click to collapse
leedroid, insertcoin and a few of the other roms here have the option to lower the brightness in their tweak settings. If you search for it, j4n87 also created a flashable xml mod that lowers the brightness as well.
Cheers, I saw one on XDA for what I thought was the One S but it must be what youve just mentioned above I think.
www.youtube.com/watch?v=oXJhJSAq3ig&feature=related#t=11m03s
That shows what I'm on about.
slvrarrow said:
www.youtube.com/watch?v=oXJhJSAq3ig&feature=related#t=11m03s
That shows what I'm on about.
Click to expand...
Click to collapse
Yes, we're on the same page although I don't understand italian . The mods I'm referring to all alter the baseline brightness as opposed to just the regular screen brightness based on ambient levels.
I'm running CM9 which allows you to edit baselines for screen and softkeys, but the roms and mods I referred you to do the same thing with less granular control. j4n87's mod is pretty dim but worked well for me until I switched to CM9. You could always crack open his zip and change the levels yourself before flashing.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=1595559
Yeh haha I don't speak Italian either just stumbled upon that on featured videos! Erm I knew CM9 had it working, can you point me in the direction of the best build? I need HDMI out but can live without Hotspot (which I believe is the only problem causer?). What's CM9 battery overall before these screen modifications?
I've tried about 6-7 of the roms here, they're all pretty much the same with varying levels of tweaks. I'm pretty sure that HDMI is working on the majority of them.
I love the hardware on this phone but not fond of Sense at all. Looking forward to more AOSP/AOKP based roms. The only available CM9 rom still has some bugs that need to be addressed (Phone, GPS, Camera - all working but with flaws) Battery life is excellent though I'm getting 4.5-5+ hours of screen on with heavy to moderate use using Faux123's kernel.
Is that the CM9 over at Modaco? Or is there an active one here?
That's great screen on time by the way.
Ideally I want one based on CM9 but with the sense Camera, that's all I can see thats worth keeping. Sense just isn't worth the performance hit IMO. It looks pretty cheap, especially with all the colourful busy icons...
Yes I'm using the build from modaco, jdroid is apparently working on a AOSP version and is beta testing. He said that they may release something this week.
How are you finding Screen on times for video playback/streaming by any chance?
Also, have you tried to see if the force dual core app helps?
Ill know myself tomorrow, the phone arrives...!
Im curently running jellybam 6.7 and i was wondering if anybody can give me as much info as possible on what exactly frameworks and dpi are and what exactly they do. Im also wondering about the kernals i kno there are other compatable kernals that could be flashed with jellybam but i honestly know nothing about them or wat it changrs. Im a noob to most of this and im just trying to make sure i completely avaoid bricking my phone. Any help or info would be much appreciated.
Sent from my SPH-L710 using xda app-developers app
Roni P. said:
Im curently running jellybam 6.7 and i was wondering if anybody can give me as much info as possible on what exactly frameworks and dpi are and what exactly they do. Im also wondering about the kernals i kno there are other compatable kernals that could be flashed with jellybam but i honestly know nothing about them or wat it changrs. Im a noob to most of this and im just trying to make sure i completely avaoid bricking my phone. Any help or info would be much appreciated.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I have more experience with messing with DPIs than I do with kernels, so I'll let someone else answer your question about kernels.
DPI normally stands for Dots per Inch. When it comes to printer, the higher the dpi the smaller the dots and, therefore, the higher "resolution" you get. For Android, though, DPI talks more about the pixel density (I think it's Density Pixel Index, I could be wrong, though). If you really want to get into Android uses this value in their code, the first comment in this post does a good job (IMO) of showing where it comes into play. After all that, the basic correlation is this: lowering the DPI will shrink your icons/apps/etc and effect the way certain apps appear on your phone. The stock GS3 setting for DPI is 320.
The reason people (like myself, running 241 dpi) choose lower DPIs is that certain apps (like calendar, Hulu, Netflix, etc.) have better interfaces on tablets than they do on phones, so we want to "force" them to think our GS3 is a tablet. The "official" way of doing this is by modifying the build.prop file. There's a semi-guide here that you can follow. The main problem with changing this value is that the Google Play Store looks at it to verify your phone. If the phone type does not match the the DPI value, you won't be able to download any apps! There are various fixes to this, but my preferred choice is just to download and install a modified Play Store which allows multi-DPI. Here is the thread for the one that I use (see post #2 for downloads).
Some ROMs also allow you to change the DPI "on the fly" without having to modify the build.prop. I'm currently running LiquidSmooth and in my Settings --> Interface --> LCD Density looks like this. It also has steps that you need to take to make your Play Store work. Having the multi-DPI play store that I linked previously will prevent you from havign to do the "clean up" work, but it doesn't hurt to follow the steps.
Now that you know a bit more about that, there are ways to get the advantage of a lower DPI on certain apps without havinn to mess with the build.prop or a Multi-DPI play store. ParanoidAndroid is a ROM that has "per-app DPI settings" built into it. Some other ROMs have the "Xposed DPI application," which serves a similar purpose. Per-app DPI systems like these two can "force" any app to see your device at a DPI that is not the current System DPI. For instance, I can have my system DPI as standard (320), but when I run Hulu, it sees my device as 241 DPI, so the layout will be similar to what I would see on my tablet (which I prefer for Hulu). This is nice because if you mess up a setting for an app, you can just revert the changes and clear the app cache and it'll be good to go again.
Hopefully this is a good primer to see the purpose of DPI and how it's used to customize your experience with your phone.
Let me talk about frameworks and kernels now...
A kernel is the powerhouse of an OS altogether. It is this layer that provides all interfacing with hardware that the OS can then use to implement things like network toggles and such
Everything is defined in the kernel...if something is not defined there, then you cannot use it
This is the reason why building newer roms (from source and not yet supported officially) is difficult because you gotta build the kernel from the ground up. You gotta implement things like Wifi, Power management (voltages, CPU, and proper shutdown and booting up sequences), 4G (if applicable), and 3G
So in summary, the kernel is what provides the software (in this case the Android OS) access to hardware components through this intermediate layer
Now the reason people flash other kernels is because some may manage power better (resulting in better battery life), may implement more features (have more CPU governors or IO schedulers), or provide some extra quality (could be something important like 4G or something as aesthetic as enabling boot animations)
Now frameworks. Each proprietary interface has its own frameworks. AOSP is normally not mentioned when discussing frameworks because it is the "vanilla" or "stock" interface provided by google straight from the original AOSP source that all other proprietary frameworks are built on top of
HTC has its own interface, so does Motorola, Samsung, and LG
HTC's interface is called Sense, Samsungs is called Touchwiz and LG's is called LG UI (very creative, i know ), and i believe, but I may be mistaken, that Motorals interface is called MotoBlur
And each of these proprietary interfaces is primarily defined in the frameworks-res.apk and SystemUI.apk. It is these additions (addition being used in reference to what Google provides) that give each interface its unique spin on things. This is what causes the weather to animate on an HTC phone as soon as you unlock it, what gives the apps a different icon and more features, what changes the icons for the different things in the status bar, what shows recent apps and quicksettings when you slide down the status bar. In touchwiz its the same thing, different icons and other proprietary features like multiview and a more unique keyboard
Basically, the "frameworks" that you keep hearing about is what defines a proprietary interface. It is because of these interfaces that you cannot install proprietary apps or enable proprietary features on AOSP. These things are dependent on the frameworks of their respective interfaces and since AOSP has a different frameworks, then you'll just get FCs and such.
Now I'm not saying its impossible to port proprietary features over to AOSP. It can be done. But its extremely difficult because first you need to track down where exactly these features are defined, and then condense them into either a standalone app, or a series of standalone apps that will behave the same way.
Thanks guys... So now where does the exposed settings come into play? Is it honestly worth messing with or is going to open a whole new world like rooting rooting my phone? Lol
Sent from my SPH-L710 using xda app-developers app
Roni P. said:
Thanks guys... So now where does the exposed settings come into play? Is it honestly worth messing with or is going to open a whole new world like rooting rooting my phone? Lol
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I touched upon this in my reply.
Now that you know a bit more about that, there are ways to get the advantage of a lower DPI on certain apps without havinn to mess with the build.prop or a Multi-DPI play store. ParanoidAndroid is a ROM that has "per-app DPI settings" built into it. Some other ROMs have the "Xposed DPI application," which serves a similar purpose. Per-app DPI systems like these two can "force" any app to see your device at a DPI that is not the current System DPI. For instance, I can have my system DPI as standard (320), but when I run Hulu, it sees my device as 241 DPI, so the layout will be similar to what I would see on my tablet (which I prefer for Hulu). This is nice because if you mess up a setting for an app, you can just revert the changes and clear the app cache and it'll be good to go again.
Click to expand...
Click to collapse
So basically, the Xposed DPI application allows you to control the DPI on a per-app basis. You can tell Hulu to use 241 dpi and Netflix to use 190 DPI (or whatever you want), even if you have your phone's "default" to be the standard 320 DPI.
In terms of functionality, it'll affect different apps in different ways. A lot of the time, apps won't change at all. Some will stop working, so you'll just have to revert the settings and clear cache and you'll be good to go. It's really up to you which apps you want to modify. A lot of people don't mess with this stuff for fear of breaking things, but Xposed shouldn't have "lasting" effects.
Back when I was using ParanoidAndroid, I had toyed with the idea with creating a Thread in the General forum about which apps look best with modified DPIs. I eventually gave up the idea (was a huge effort while I was creating screenshots of each app before and after), but it might be good to start one up now that XPosed is being included in a lot more ROMs. Meh, maybe once I have a bit of free time.
At the moment there is no stable and reliable Android 4.4 ROM yet, but I hope this will soon change.
Perhaps we can compare the different ROMs here. Please note that I am not asking for best performance or lowest RAM requirement. These are secondary issues. The most critical issue is reliability.
The Google ROMs have always been the most stable and reliable. They were never perfect, but at least we could expect them to run for a week or longer without any significant error and without rebooting. In my experience, other ROMs, like the admirable CyanogenMod, came close, but never quite reached that same level of reliability. Given that the CyanogenMod crew works for free and in their free time, the quality they delivered has been astounding and admirable.
Nonetheless, reliability remains the biggest issue among the third-party ROMs.
So, if you install any of the Android 4.4 ROMs on your Galaxy Nexus, please report what you find. Please try to judge whether that ROM can be recommended for general use or whether the newbies had better stand back and wait for the next version.
Another question is: How user-friendly is the install procedure? Can you keep your apps and app data?
It is very unfortunate that the gnex community is not supported anymore due to 'hardware issues' or the 18 month timeframe. It is true that the ROMs made these days are not so 'reliable' and they may be buggy and cause force closes on certain applications. The new roms may never support cleanly and as stable as stock factory images by Google but its all the Gnex community can rely on from now. Personally, I feel the slimkat 4.4 ROM is acceptable considering it is only about less than a week old. They have been fixing bugs such as GPS tracking and such. I will be using it as my daily driver from now and just hope that the developers can make it as stable as the stock android ROM.
Sent from my Galaxy Nexus using xda app-developers app
a taste of kitkat perfect aosp leaked rom
i''ve installed yesterday a taste of kitkat with mpokang 1080p kernel.. some glitches when rotate screen but only one reboot using google now (i don't use gnow so it's not a problem for me) and i've a crash only on fifa14... battery good performance, no lags, no problems, trickstermod overclock to 1.4ghz no problems, facebook, whatsapp, viber, tango, hangout, 3G, Wifi, Bluetooth, GPS alla working without problems.. and now i'm testing battery..
Toro Plus
For us sprint (or Ting) users the 4.4 ROMs are not even installable. There have been two threads started and each one was locked after it became apparent that the developers did not have booting builds. I appreciate all the work devs do, but this keeps getting my hopes up. Hopefully, someone will get one working soon and we won't have any more false starts.
They are just alpha builds, experimental builds. Most of them have some glitches. They are not for daily use.
If you do not have necessary knowledge and do not have time to report bug, then I suggest you should back out on those alpha builds.
They're not even a week old. Give time and reap miracles afterwards
Sent from Samsung Galaxy Nexus @ CM10.2
It's a Nexus device. Things will improve over time.
I've been running the most recent SlimKat alpha build and it's been pretty solid. Phone feels rejuvenated. It is my work phone and worked flawlessly all day. The only restarts were Hangouts last night and when I was fiddling around with wallpaper settings after work, and forgivable graphics glitch during screen rotation. Otherwise, it has has felt like a new-ish phone today.
Thanks for the good information!
I think, when the builds go from alpha to beta and there are no obvious glitches any more, then would be the time to do some more thorough testing, particularly:
GPS, including track recording with My Tracks, Locus, or a similar app
Cameras with all their functions
Compass, gravity, and other sensors
Tethering via USB, Wi-Fi, and Bluetooth
Radio functions, particularly LTE and the general behavior with a weak or frequently interrupted signal
OTG with USB mass storage device, keyboard, etc.
I would recommend to report all defects not only here, but also to the maker of the ROM.
For now, they are pretty unstable, but I would keep an eye out for linaro's builds as well:
http://www.cnx-software.com/2013/11/06/android-4-4-kitkat-on-galaxy-nexus-rom-linaro-and-petition/
idk what you're talking about OP. i've run these custom roms more tha n week and they've been good. only reason the counter will reset is because I flash a new rom or flash an update or a mod.
These ROMs are very stable.
4.4 ROMs. give it some time. it's amazing that in less than 24 hours after the release of 4.4, we got a semi daily usable ROM from people that don't even work for Google.
I've been on SlimKat for a couple hours now. Clearly a ton of the SlimRom features are missing but considering that its an Alpha its not that bad.
Other than some graphical glitches here and there, which are very rare actually, there arent any other instabilities that I can see. Everything works fine. I dont know who is starting this rumor about 4.4 being unstable. Some ROMs may work better than others but thats due to different developers working at different paces. Bottom line is, 4.4 is perfectly fine for a daily driver. It just needs some ironing out.
Yeah, I'm running the SlimKat ROM, and its beautiful
Sent from my Galaxy Nexus running the Forbidden Update using xda app-developers app
Running Shiny 4.4. Good taste of KitKat. Sounds crazy, but I'm using it to test stuff out before it goes on the N5.
Biggest glitch seems to be with graphics, in that overlays of menus and random black boxes over some text in gmail and Chrome, make things unreadable and useless. Not to mention the random reboots when you can tell something happened that the GNex doesn't like.
IMO, they are not ready for use on a primary device. As in, at the end of the day, when I'm home, I pop my simcard out of my MotoX and out it in my GNex/3.4 to tinker. No maps to crash at the wrong time, I have other devices at the low-ready to surf on and more time to tinker. My gf loves me for this routine I've made for myself
Definitely a good taste of KitKat. Considering today would mark 1 week since release, on an unsupported device - its actually pretty stable.
LCD Density
I'm on SlimKat and my old eyes can't deal w/ the tiny text - even when changing default system font to HUGE in the display settings. build.prop has a value of 240 but I can't edit in ES Explorer even though the file props say it's writable. Tried an app but it loops and doesn't make any changes. Any ideas?
xMoment said:
I'm on SlimKat and my old eyes can't deal w/ the tiny text - even when changing default system font to HUGE in the display settings. build.prop has a value of 240 but I can't edit in ES Explorer even though the file props say it's writable. Tried an app but it loops and doesn't make any changes. Any ideas?
Click to expand...
Click to collapse
use rom toolbox, it worked for me
Inviato dal mio Nexus 7 con Tapatalk 4
xMoment said:
I'm on SlimKat and my old eyes can't deal w/ the tiny text - even when changing default system font to HUGE in the display settings. build.prop has a value of 240 but I can't edit in ES Explorer even though the file props say it's writable. Tried an app but it loops and doesn't make any changes. Any ideas?
Click to expand...
Click to collapse
1.Root first using chainfire SuperSU v1.65
2.Install RE(Root Explorer)
3.Hit Mount R/W
4.Open build.prop and change density to 320.:highfive:
Thanks - I was rooted already and made sure root explorer was on. Tried to change permissions in terminal, didn't work. Booted into recovery and mounted system, rebooted and hung at the google logo...so flashed FML and the DPI is 320 so I'm fixed
joytsay said:
1.Root first using chainfire SuperSU v1.65
2.Install RE(Root Explorer)
3.Hit Mount R/W
4.Open build.prop and change density to 320.:highfive:
Click to expand...
Click to collapse
Hey,
I have a small question again.
My wife has the LG P700 and used until recently one of Rome SlimBean.
There it was, that's all been somehow smaller, which had more space on the desktop.
I do not know how to describe it .... on the PC, I would say that the resolution has been changed.
Well anyway, I did like the totally good and I wonder if you can also transfer it somehow to the DHD / apply.
Does anyone know what?
Normally I would say DHD has smaller DPI, but they both have the same screen size and same resolution.
The solution would be to set smaller fonts in setting or change ROM (generally AOSP ROMS (or Sense3.6) have smaller UI elements than Sense4)
Some roms have custom DPI options, if you're finding that your rom is too big/small ParanoidAndroid might be a good bet.
Hey,
Thanks for the replies.
Has anyone had experience with TEXTDROIDER_DPI?
This is probably the one to change.
Currently I have 240 DPI. The app hits me 220 DPI ago. I get displayed I definitely want to make a backup of what I have done.
According app it can happen that you get a Bootloop and then have to change a file.
Now before I try out, I prefer to ask ... maybe someone has done it already experiences.
CyanogenMod version:
20,131,022-4.3-beta6-Ace
changing DPI may look tempting, but in most cases it will mess up graphics by making UI elements look blurry. Moreover, you may have problems with apps compatibility.