hi i'm not an expert excuse me if the question seems silly:
i own a google nexus one. i've seen a lot of kernels around and i was wondering what is their purpose. besides i wanted to know if the roms (cyano, stock deodexed rom and so on...) come with their own kernel or if it has to be installed separately. in this case how do i know which my stock kernel was?
Think of Kernels as mini ROMs, they are addons that you can install to the System Partition. Common addons are Undervolting (less power consumption), overclocking, and enabling 720p video recording. So yeah, they're like ROM addons. Some even speed up the phone and fix lag and coloration issues, but thats mainly for the Galaxy S line.
an example is the battery driver edits we did to the nexus one. if you want to change how the phone works with the hardware, changes had to be made to the driver, and re-compiled, then install that kernel to the phone.
so all the devs have all sorts of ideas and things they want to change to drivers and cpu voltages and whatnot to get better performance and stuff. so each kernel has different edits like that battery one. and people like to try out different ones to see which works the best. that's the idea.
ok tnz a lot for the explanation
Hi guys, my n910t3 is on Tekxodus 5.1.1 with root and xposed. It always seems to close the background apps. In the task manager, my ram usage rarely ever goes to 2gb/2.72gb. I have my background processes set to the standard limit. I have tried apps like memory locker and ram manger(root), both of them not working :crying:. I tried to do the build.prop fix that the s6 and note 5 use, but I could not find the ro.config.dha file anywhere. I don't think that Tekxodus is the problem because I always had these problems, and thought that installing a custom rom would fix the problem. Any help would help
michaelw911 said:
Hi guys, my n910t3 is on Tekxodus 5.1.1 with root and xposed. It always seems to close the background apps. In the task manager, my ram usage rarely ever goes to 2gb/2.72gb. I have my background processes set to the standard limit. I have tried apps like memory locker and ram manger(root), both of them not working :crying:. I tried to do the build.prop fix that the s6 and note 5 use, but I could not find the ro.config.dha file anywhere. I don't think that Tekxodus is the problem because I always had these problems, and thought that installing a custom rom would fix the problem. Any help would help
Click to expand...
Click to collapse
The build.prop edit you were talking about (ro.config.dha) has to be added as a new line to the build.prop and you can do that with any root editor. I use 3C Toolbox to add the lines and edit the existing ones.
But honestly, if the RAM management apps aren't able to change it I would try going back to stock software and seeing if the RAM issue still happens. If it does it there too you could have bad RAM blocks (more likely) or the T3 may have a totally different memory management routine that we don't know about (unlikely).
I have a T-Mobile Note 4 rooted & running stock MM ver 6.0.1 and I'm using the phone on the AT&T network. Would it be possible to remove the t-mobile apps that can't be un-installed or disabled via normal procedures, by using the build.prop option?
I would like to lose things like the T-mobile hot spot app and the t-mobile startup screen etc., I was wondering if any of the following lines could be altered or deleted to acheive this.
ro.build.flavor=trltetmo-user
ro.product.name=trltemo
ro.product.device=trltetmo
I know I could cause problems doing something like this witout knowing the outcome first. I've done minor stuff like changing dpi but that's about it.
Uuuummmm.....no...start up screen?....your on the fast road to a hard bricked device....there are apps to remove bloteware on the play store but you don't want to just remove any apps....if you want to change your boot logo there are apps for that also...I would stay out of your build props
So, I wonder?
I've been digging through the system files in my unlocked, rooted UA v40, and except for the apps that came installed with the phone, there's also some in the root that didn't come alive, just taking up space? I know, there's no need to clear space, but I still wonder!? And it also seam to exist some dalvik even for the apps that never came alive in the first place?
Following today's Android rules, is it still possible to clear Dalvik?
Say, if I delete the apps in root/system/product that aren't even installed, will it scr.. something up?
I guess there's some kind of script executed while flashing the rom. If I delete apps (in the right place), and factory reset my phone, will that corrupt something? Is there a file (command/script) I can edit in root, that decides what app to install, to make this work?
Back in the days I deleted unvanted apps before flashing the rom, but I understand it's different today...
Not very important, but would be nice to know
Not a dev but thought I'd throw in some thoughts. We don't have any "stock based" dev to bug regarding stock fw really.
From my own digging through newer fw releases, it seems that LG hired some really lazy mofos as coders. Looks like they create new fw from old ones, then updated it to new versions plus some tweaks to suit the target model.
For a programmer that'd make sense since you already have the base code, you just change modules and libs as needed. However, in LG's case, their guys didn't bother to remove anything that was already there. They just kept adding on stuff. That's where you see the unused apps (and also explain why stock fw sizes keep getting bigger). Hell, I even found G8 specific settings in the service menu earlier today. Best I can tell, there aren't any symlinks that tie back to these unused apps, so, technically, removing them won't break anything. But given how sloppy the existing structure is, it wouldn't be surprising if it does either.
Now dalvik on the other hand, that' and interesting point. Since dalvik was dropped when google implemented ART, it theoretically, shouldn't even be on the phone. Where did you find those?
That's just stupid of LG
I mean, what does "Airmotion" do in v40? Hahaha!
Oh, I still say Dalvik, aware of art.
Thanks
This is what I mean
This is one of the apps that wasn't really installed to be used in v40. Is it normal that one of those apps still got art files? So if I was to delete this app, can I delete the linked art files too?
Can anyone port the v40 camera app for lg v30 pie?
This was my main question:
I guess there's some kind of script executed while flashing the rom. If I delete apps (in the right place), and factory reset my phone, will that corrupt something? Is there a file (command/script) I can edit in root, that decides what app to install, to make this work by factory reset?
neocyke said:
Not a dev but thought I'd throw in some thoughts. We don't have any "stock based" dev to bug regarding stock fw really.
From my own digging through newer fw releases, it seems that LG hired some really lazy mofos as coders. Looks like they create new fw from old ones, then updated it to new versions plus some tweaks to suit the target model.
For a programmer that'd make sense since you already have the base code, you just change modules and libs as needed. However, in LG's case, their guys didn't bother to remove anything that was already there. They just kept adding on stuff. That's where you see the unused apps (and also explain why stock fw sizes keep getting bigger). Hell, I even found G8 specific settings in the service menu earlier today. Best I can tell, there aren't any symlinks that tie back to these unused apps, so, technically, removing them won't break anything. But given how sloppy the existing structure is, it wouldn't be surprising if it does either.
Now dalvik on the other hand, that' and interesting point. Since dalvik was dropped when google implemented ART, it theoretically, shouldn't even be on the phone. Where did you find those?
Click to expand...
Click to collapse
I noticed that on the V30 already too.
Settings are enabled/disabled depending on the props set, and which device its running on, some you should even be able to activate/deactivate during runtime...
Makes things way easier to develop that way, yes... but also unneccessarily bloats the whole UI... should have set flags during compilation to fully exclude the code (e.g. how the HALs do that lol)
I'm thinking about changing from an old Google Pixel to the S10.
I want the best from performance and video recording quality.
Other than removing the bloatware and changing some settings, is there anything else I could do to get the best performance out of this device?
Like a custom kernel and/or ROM that is faster than stock. And maybe a better video recording method than the stock camera app.
Depends on WHICH S10 you have. US versions with latest bootloaders don't have root - you need an older BL to get root (and you have to stay on the older version). Non-US versions have more options, but the process is different.
I'm running stock US (G975U1) without any issues... I don't find that "bloat" is an issue in general...