Related
Hello all, I have installed in my wildfire the latest (gingerbread) cyanogenmod rom. When I open FM Radio it opens bluetooth in order to work and the sound is not that clear.
Can someone propose a custom rom (don't care about sense or not) that has FM Radio working properly? Also note that the second requirement is smooth scrolling for it's launcher and if possible the ability to overclock.
panagath said:
Hello all, I have installed in my wildfire the latest (gingerbread) cyanogenmod rom. When I open FM Radio it opens bluetooth in order to work and the sound is not that clear.
Can someone propose a custom rom (don't care about sense or not) that has FM Radio working properly? Also note that the second requirement is smooth scrolling for it's launcher and if possible the ability to overclock.
Click to expand...
Click to collapse
Hi. 1st off. I don't think I've ever had any issues with FM radio on cm7 or any other rom I've used. The Bluetooth turning on is a necessity and even on sense Roms I believe it occurs but is just hidden to our eyes. Are you listening from phone speaker or headphones? If headphones then you could try the beatsaudio zip http://db.tt/3RlOw5bz to enhance sounds. The dsp app found in cm7 is also for adjusting sound pfofiles etc etc so you could play around with these settings too.
As for home launcher smoothness,people have there own preferences so its trial and error. Search market for home launcher etc etc to find alternative launchers,just install as normal test and when you find one you like then set it to default by pressing your home button tick the box then choose the desired launcher as default home.then delete/uninstall the ones you don't want.
I personally swear by ADW ex as I find it has most customizing options.this is a paid app.
Holo launcher is free and would be my 2nd choice.
As for Roms to use again this is personal preference related.at this moment in time my choices are.
1.lewaos
2.cm7 rc3
3.rempuzzle (sense rom)
I've tried virtually all the roms on xda for wildfire and even others from external sources and these 3 are my favorites.
insert ....... here
slymobi said:
The Bluetooth turning on is a necessity
Click to expand...
Click to collapse
I've always wondered about that - anybody know why this is? I'm assuming some kind of hardware limitation, but it would be nice to know for sure...
I'm an X ios user, pun intended In a Jailbroken ios environment all 3rd party/unsigned app development is housed under an app called Cydia. Within Cydia you can add developer repositories that host their apps,tweaks etc... Cydia takes all your repositories and creates a directory where you can search or browse by category. Essentially, all tweaks/apps are available for all phones; you just need cydia.
After fiddling around with custom roms like Android Revolution HD and ViperX, I'm starting to see access to tweaks universally is not a reality in the droid world. Though I'm hoping that I'm completely wrong and somebody can show me the light.
Am I able to install the following features on ARHD? or are they solely available in ViperX? are there other tweaks or apps that offer these features?
-Remapping capacitive keys for short hold
The recent HTC update enables this for the menu key, however viper enables all 3 keys.
-Quick Setting, and the ability to move and remove quick settings items.
-Disabling the HTC script that buggers the wi-fi and network between 12am-7am
-Quad Core Cpu usage info Notifications
-Quick theming abilities
Any help is much appreciated!
It's all tweaks, especially the WiFi-killing one that was first developed by J4n87, which also makes the ViperX ROMS. It's also available as a separate app in the Themes and App forums
For Home and Back, maybe why many ROMS don't offer fully costomizable remapping is cos many are satisfied with what those buttons already do, while the ViperX team just gives you everything to mess with, and you gotta help yourself if you mess it up.
ArmedandDangerous said:
It's all tweaks, especially the WiFi-killing one that was first developed by J4n87, which also makes the ViperX ROMS. It's also available as a separate app in the Themes and App forums
For Home and Back, maybe why many ROMS don't offer fully costomizable remapping is cos many are satisfied with what those buttons already do, while the ViperX team just gives you everything to mess with, and you gotta help yourself if you mess it up.
Click to expand...
Click to collapse
Are there ways to achieve this tweaks without a custom rom?
mattswart said:
Are there ways to achieve this tweaks without a custom rom?
Click to expand...
Click to collapse
If by 'without a custom rom' you mean you want these tweaks on the Stock rom then as per my knowledge the answer is No. I might be wrong. But
I had suggest flash the new version of Viper i.e. 2.0.1 . In my opinion it is as stable as the stock ROM and definitely much better with all the tweaks you get. It looks just like the stock rom with no visible changes. Has just an addition 'Viper tweaks' section in the settings where the extra tweaks are available. It never crashes or gets stuck, is much more smooth than the stock rom and the battery life is also much better.
Let me know if I helped by clicking thanks
mattswart said:
Are there ways to achieve this tweaks without a custom rom?
Click to expand...
Click to collapse
If by 'without a custom rom' you mean you want these tweaks on the Stock rom then as per my knowledge the answer is No. I might be wrong. But
I had suggest flash the new version of Viper i.e. 2.0.1 . In my opinion it is as stable as the stock ROM and definitely much better with all the tweaks you get. It looks just like the stock rom with no visible changes. Has just an addition 'Viper tweaks' section in the settings where the extra tweaks are available. It never crashes or gets stuck, is much more smooth than the stock rom and the battery life is also much better.
Let me know if I helped by clicking thanks
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.
Does Xposed slow down the phone or is it the combination of certain modules?
I've been using a T-Mobile H811 since launch and so does my girlfriend. The biggest difference between our two phones is that I've rooted mine as soon as I was able to and also installed Xposed Frameworks along with a few modules. For the most part, I've been pretty happy with the performance of my phone and have been able to shrug off the occasional performance stutter.
Recently, I was playing around with my girlfriend's phone and I noticed that it was a lot smoother than mine. I put our phones side by side and it was plain as day that her phone was a lot smoother when just swiping through panels in the settings menu. After that, I couldn't unsee how slow my phone actually was. Because of this, I concluded that it must be something Xposed related as that's the main difference between our two phones.
So that brings me to my big question: is it the presence of Xposed being installed that may have an adverse affect on a phone performance or is it having certain modules installed that affect the performance? Or maybe, just maybe, it was even the combination of apps that I keep installed that were at fault?
If you have any insight or opinions to share, I'd love to hear it. If you've been forever on Xposed like I have, maybe you don't notice the performance being any better or worse since that's just what you're used to seeing, but if you've use it on and off, maybe you'll have better insight into it?
I recently did a factory reset and opted not to install Xposed. For the couple of days, I think it's safe to say that my phone is running a lot better, but there are definitely a few modules that I miss. Most notably G4 TweaksBox and also Restore Notifications Ticker, though I'm also very fond of Flat Style Colored Bars (but if modules impact performance, I can see how this one might be the culprit.
Thanks!
My guess is that the number of modules and what modules you have would affect performance. In my opinion i think the modules that theme parts of the phone use the most memory. I used to have xposed and the tiny lag never really bothered me at but xposed just isnt for me. Maybe a list of modules you use would make the question a little but easier to answer.
It was explained by rovo89, that if you use modules, which are not updated to the latest xposed, the phone will lag, because of xposed using up the resources and your logcat will be also filled with errors. I think he wrote about this on his GutHub or the XDA thread. That said, I am using only 5 correct modules and the phone is fast as on stock.
theming modules like stana or fsb or others causing lag imo....but others which have single usage arent so power hungry...im not sure about gravitybox style modules...
Eddiekool12 said:
My guess is that the number of modules and what modules you have would affect performance. In my opinion i think the modules that theme parts of the phone use the most memory. I used to have xposed and the tiny lag never really bothered me at but xposed just isnt for me. Maybe a list of modules you use would make the question a little but easier to answer.
Click to expand...
Click to collapse
The modules that I used where Restore Notifications Ticker, Flat Style Color Bars, G4 TweaksBox, SNAPPREFS, Spotify Skip, Pandora Patcher, Swap Volume Keys, and then enabled the Greenify Xposed options. Other than FSCB and the tweaks box, most aren’t changing much, but those are also my two favorite modules and probably do the most heavy lifting. And, like I said, the lag never really bothered me (since it’s what I was used to), but then I used my girlfriend’s phone without Xposed and immediately noticed the difference.
davebugyi said:
It was explained by rovo89, that if you use modules, which are not updated to the latest xposed, the phone will lag, because of xposed using up the resources and your logcat will be also filled with errors. I think he wrote about this on his GutHub or the XDA thread. That said, I am using only 5 correct modules and the phone is fast as on stock.
Click to expand...
Click to collapse
Which modules are you using? And how could I read the log to see which, if any, modules are the ones causing issue?
pikachukaki said:
theming modules like stana or fsb or others causing lag imo....but others which have single usage arent so power hungry...im not sure about gravitybox style modules...
Click to expand...
Click to collapse
I kind of figured that FSCB might be doing resource intensive since it themes on demand based on the app. I really wish the tinted bars were a part of the stock experience… it looks so good.
---
So you’d all agree that it’s safe to say just having Xposed installed is fine and should prevent no problems and that I should just test the modules individually or together and see how things perform?
Giving up Xposed completely isn’t so bad, but there are a few things I’ll really miss, especially the notifications ticker and being able to hold the recent key to open the last app. I kind of want to ween myself off it, though, knowing that it may not always be an option in the future.
partylikeaninjastar said:
The modules that I used where Restore Notifications Ticker, Flat Style Color Bars, G4 TweaksBox, SNAPPREFS, Spotify Skip, Pandora Patcher, Swap Volume Keys, and then enabled the Greenify Xposed options. Other than FSCB and the tweaks box, most aren’t changing much, but those are also my two favorite modules and probably do the most heavy lifting. And, like I said, the lag never really bothered me (since it’s what I was used to), but then I used my girlfriend’s phone without Xposed and immediately noticed the difference.
Which modules are you using? And how could I read the log to see which, if any, modules are the ones causing issue?
I kind of figured that FSCB might be doing resource intensive since it themes on demand based on the app. I really wish the tinted bars were a part of the stock experience… it looks so good.
---
So you’d all agree that it’s safe to say just having Xposed installed is fine and should prevent no problems and that I should just test the modules individually or together and see how things perform?
Giving up Xposed completely isn’t so bad, but there are a few things I’ll really miss, especially the notifications ticker and being able to hold the recent key to open the last app. I kind of want to ween myself off it, though, knowing that it may not always be an option in the future.
Click to expand...
Click to collapse
g4 toolbox have tinted status bar and nav bar....
pikachukaki said:
g4 toolbox have tinted status bar and nav bar....
Click to expand...
Click to collapse
Flat Style Color Bars works better and is more customizable.
Sent from my LG-H811 using Tapatalk
My lg g4 bootlooped recently so I sent it in and got another. I also got a Samsung S7. I have not rooted the new G4, but I have rooted and installed XPosed on the S7.
First thing that's immediately noticeable is how fast the stock LG G4 is. The LG G4 slaughters the rooted Xposed S7 in both performance and battery life. The G4 when it was rooted + Xposed was very laggy. This has prompted me to begin looking into the possibility that Xposed kills performance.
I'm only using 3 modules. MinMinGuard, Snapprefs, and YouTube AdAway. I think the issue is with the Xposed framework itself.
Hello, I've been experiencing lots of lag with both OxygenOS (and OOS ROMs) and custom ROMS.
I honestly don't know what's causing it, this is what I have installed that could ruin my performance:
So I made a list of all the apps I have installed, so you could help me figure out what's causing it.
Here's the list.
Don't use xposed or pirated apps.
Skeptico said:
Don't use xposed or pirated apps.
Click to expand...
Click to collapse
I usually buy everything I have and I use Lucky Patcher only for apps with intrusive nonremovable ads
And I'm pretty sure Xposed is not the problem as I'm not tweaking Android's UI in any way.
Try without greenify.
Use background restrictor from XDA labs instead.
I would also remove xposed. Xposed causes a lot of errors. This device does not lagg. On OOS with stock kernel. U cannot make it lag unless ur making it lag. Like messing around with the kernel etc. Custom ROMs are even smoother with flash kernel
Jamie_oppo said:
Try without greenify.
Use background restrictor from XDA labs instead.
I would also remove xposed. Xposed causes a lot of errors. This device does not lagg. On OOS with stock kernel. U cannot make it lag unless ur making it lag. Like messing around with the kernel etc. Custom ROMs are even smoother with flash kernel
Click to expand...
Click to collapse
Uninstalled greenify and installed backgroundrestrictor, I got a nice performance boost.
But I really need Xposed for XInsta so I'm gonna keep it unless I find an alternative.
Or can I just disable Lucky Patcher within Xposed and just keep the normal version, will it impact the system performance-wise?
MarcoReckless said:
Uninstalled greenify and installed backgroundrestrictor, I got a nice performance boost.
But I really need Xposed for XInsta so I'm gonna keep it unless I find an alternative.
Or can I just disable Lucky Patcher within Xposed and just keep the normal version, will it impact the system performance-wise?
Click to expand...
Click to collapse
If u can. Remove lucky patcher or at least from xposed.
If u need ad blocker. Use ad away. 0 performance impact.
I stopped using Lucky Patcher 2 years ago, when the official Xposed was released for every phone. Lucky Patcher itself contains many mods and tweaks, may conflict with user apps and system apps so Im sure it's no go for me.
lemonade747 said:
I stopped using Lucky Patcher 2 years ago, when the official Xposed was released for every phone. Lucky Patcher itself contains many mods and tweaks, may conflict with user apps and system apps so Im sure it's no go for me.
Click to expand...
Click to collapse
I played around with the toggles (keep legit licenses, etc.) and found a happy spot, that's why I kept it.
I have this issue too. Doesnt matter what rom I try, I've tried 90% of them. Even on a clean flash, with just a few google apps, like on G+ it laggs like heck scrolling through the posts. Some roms are slightly better than others, also when trying custom kernels, if I install kernel auditor and just make 1 change, doesnt matter what, its like input boost gets enabled for all cpu's and they all jump to 1800mhz when i touch the screen. only way to get it to stop is to change the governor to conservative. It just seems like this phone is laggy by nature. lol that sounded funny.