Related
Process
From Wikipedia, the free encyclopedia
Process or processing typically describes the act of taking something through an established and usually routine set of procedures to convert it from one form to another, as a manufacturing or administrative procedure, such as processing milk into cheese, or processing paperwork to grant a mortgage loan, or converting computer data from one form to another.
Ok first off I'm the biggest noob at all things root as could be. I have managed to make some custom clocks for my old LG voyager way back in the day and have even jailbroke some Ipod touch's so I was able to load bootleg games and apps.
But this root thing has got my brain traped in a vortex and I really want to not just know how to root my droid (That info is everywhere) but I want to know how it all works. What terms like kernel mean and how they relate to clock speed. What is the difference between all the custom rom's? What happens when I root my phone and can't figure out what rom I should use? Do I have to reset all my apps and preferences every time i want to try a new rom?
I understand the how-to's I'm sure when I try to root my phone that I will not have much trouble doing so. But there are so many things I want to learn and know before I do anything.
I would like to say I'm not looking for links to tech reports on rom's that I will not understand I'm looking for alink (or someone who knows the things I wish to learn,) something that will explain the terms what they mean, how they relate to my phone and what outcome I should expect from loading custom rom's.
I understand that most users of this forum fall into one of two category's ONE ether super wonder techs that know exactly what they are doing and know how things work, TWO people who can read follow directions and root there phones while trying NOT to sound like noob's when they ask for help.
And then there's me I'm a number two, now I know that kinda makes me sound like **** but I really want to be a number ONE
So who want's to teach me ? Who's got some time to kill or link's to post? I'm even willing to go buy a android programmers book if there's one that would be recommended reading to help me understand the OS better.
I want to learn from the masters and this is where they all live. So will someone apprentice me ?
To close my rant out I would like to say I'm a 37 year old man with a masters in chemistry 119 IQ and ex-stream case of OCD that drive's my compulsive need to learn how things work, So I make for a good student
Thanx
รถ
Thank you so much, I was hoping to be able to reply first, (this sh*t is my crack)
Ok, First off, the kernel is the basic system that controls how the cpu reacts, as well as how programs interact with the hardware on your phone, such as the screen, wifi and bluetooth modules, accelerometer, gps, ambient light and the battery. When a dev wants to overclock their android, add a module for EXT, or TUN, or add wifi support, this is where the magic happens. this is probably the most important part of the firmware. It also controls battery life via voltage, as well as cpu speed.( the average droid can be overclocked to 1200-ish, depending on the randomness of processors, though I've heard of a ridiculous version called OMAP Ti39 or something that could be stable at 2ghz, even 2.3. As I think you may know, Fat32 doesn't support file transfers of more than about 4 gigs at a time, which is why add in ext support is so important, especially since someone made a video player that reads matroska video files (blu-ray) Ive tried it, its beautiful, (V player - on the market) after kernels is framework, the framework is what renders the gui, basically everything that you see on the screen is thanks to the framework-res. We edit it either manually, or through the use of an app called metamorph, which swaps the xml files the framework uses with edited ones, such as one I recently used to give my droid a circular battery, however these xml files can change anything you could need them to visually about your droid, you just have to find what you need. Now on to shell. shell is the engine that is accesible through command prompt and terminal using the android sdk and adb, more on that can be found easily on the google android homepage. however, much use is made through devs and an app called terminal emulator that is basically a straight to shell terminal screen app. Uses for shell may include but are basically limitless, include moving any app to your sd-card to conserve rom (rom is the phones total system memory, apps usually go in there, but before froyo, and ext partition could be used, and with froyo stock support for most apps was allotted, and without the need of an ext partition.) Ram is basically ram, if you use a rom that originally came with a larger ram supported device, something called a swap partition must be implemented, otherwise it won't boot, there is an app or two that will do that for you, manual swap creation is also possible. Swap basically creates virtual ram on the sd-card. Root access, which can be acheived manually through the recovery flashing of specific zip files, or via free apps that do it with one click, basically allows you to flash kernels, change the framework, or allow tethering which I will cover next, is possible because the kernel the phone uses is linux, the unlocking of which is called granting super user access, in ubuntu a linux distribution, typing su, and your admin password will give you access to your computers system files, much in the same way we apply it to android. (However, it is unlikely you would try to flash an alternate kernel to your desktop, as it runs on either ie36 or x64 architecture, whereas phones run altogether seperate architectures , for instance android runs on ARM, and that is the base and primary reason your phone won't run windows.) Since android is free (open-source) there is an x86 version of android, including a froyo port that you can use on laptops and desktops. (Really quickly I would like to interject that recovery is an option on all phones android based that is usually accessible by holding volume up while booting, however the droid requires you press x while booting to get to recovery, which btw is what you flash a custom version of after rooting that allows you to flash roms and kernels. It also allows for backing up all of your phones firmware and data in the event of a problem. Basically its your new best friend, get familiar.) Also there is another form of booting called bootloader, it allows you to flash specific system files that are normally untouched, a guide to using that and a program called rsd lite will help you if you've bricked your phone ( Bricked- term used to describe the state of a phone that is unable to be recovered to an earlier condition and is essentially a brick or "expensive paperweight".) by allowing you to flash a completely untouched sbf (firmware) file. note that you can also use it to change your boring m boot logo with any image that fits 480x182 bytes through a slightly difficult, but fun proccess, a guide to which ,can be found here at xda, including a file that allows for the flashing of just the logo, whereas previously you had to reactivate your phone (you just have to follow the instructions on the phone) reroot, and restore the rom you previously backed up. Now on to tethering, the most important feature available to root users, which, if carriers have anything to do with it, would normally cost an extra 10 dollars a month. (Tethering- using shell or an app with the proper kernel to allow the use of your phones mobile network via usb connection, or the creation of a wifi hotspot with your desktop or laptop.) However thanks to devs who believe that what you pay for should be used how you want, most roms will tether, even in the settings, without carriers any the wiser. Windows 7 and almost all linux will automatically tether, vista is the most difficult, and xp has a quick install init file that works like a charm. The only reason we root is because we believe in the freedom to change our phones to fit us personally, and lets face it, because we can, because its fun, because its not illegal, and it brings a sense of satisfaction and pride in pushing the limits of technology. (P.S. I tried not to take to long so I couldn't really look it over, so sorry for grammatical or vocabulary based errors.)
(P.P.S. I recommend any book to do with android programming, but you'll need programming experience in linux, especially eclipse.)
Oh, and I'm a 17 year old junior with a vocabulary skill level of 139, just in case you wondered.
There are plenty of applications on the market where you can backup apps and data once you root, I personally use titanium, but I never restore system data if I'm flashing roms, only apps n data that comes with apps. Youre gonna have to search around other forums and whatnot to find the right roms.
Sent from my ADR6300 using XDA App
So fennec went alpha this week and wanted to know if anyone tried it yet?I've tried to use it but it keeps crashing, has anyone had this issue?
As much as I like firefox, I'll not get this until they trim this chubby app down some. 31mb?
Sent from my CDMA Hero. I got me some hot froyo on hero action here!
couldnt get this app to work either and the size is crazy if u want a different browser try OPERA thats pretty good if ur looking for some fast net or just wait for a better realese
WOW mY English is Atrocious
Yea I like opera but don't like that you can't really download stuff from it. But yea wanted to try out fennec to see how it runs but it's a no go so kinda disappointment.....eh
Actually, Fennec's quite a few good ideas, expecially for Firefox users. I mean, it can syncs your open tabs (the ones you left open at home before leaving!), bookmarks, search history and site access infos (so you won't type those old pass/user you can't even remember).
Moreover, you get plugins... not a big amount of them available, but this could just a matter of time if this catches up; and tab management is on par with Android browser's.
Main downside is related to page render speed and program open, they just fail before Android stock browser (which I think is quite awesome, I have to admit it, in terms of performances and compatibility).
Definitively still a "to keep an eye on" project, though.
just installed the app, but it wont even open
Junk
I find it unbelievable that this has even been considered for a release to anyone!
After several attempts to install, I finally got this bloated mess to work, slowly and with no features that haven't been done better elsewhere.
I was truely expecting more, Firefox and Thunderbird have become bad enough lately, with this rubbish Mozilla have scored 3 out of three.
Haven't tried this alpha yet, but I played around with an older Version. I also tried the WinMo version and I can tell you that Fennec on Android is much better than the WinMo version. On my HD2(running Froyo) it installed without problems and it didn't crash. But because the UI had no priority over the webpage rendering it wasn't really usable. But I think I read somewhere that in this alpha the UI has priority, so when I can I will give it a try again. But the only reason for using Fennec are the sync features.
You people should READ THE SYSTEM REQUIREMENTS before commenting on whether things are good or not. It CLEARLY states that MSM720xA based phones are NOT COMPATIBLE. Regarding the one who managed to partially get it working.... I don't believe you.
Specifically, the program is built for ARMv7 instruction set. YOUR PHONE SUPPORTS UP TO ARMv6 instruction set ONLY.
To put this very simply.... the program is NOT COMPATIBLE [yet].
lbcoder said:
You people should READ THE SYSTEM REQUIREMENTS before commenting on whether things are good or not. It CLEARLY states that MSM720xA based phones are NOT COMPATIBLE. Regarding the one who managed to partially get it working.... I don't believe you.
Specifically, the program is built for ARMv7 instruction set. YOUR PHONE SUPPORTS UP TO ARMv6 instruction set ONLY.
To put this very simply.... the program is NOT COMPATIBLE [yet].
Click to expand...
Click to collapse
There are nightly builds, which work on Armv6.
I have it running, on a HTC Magic.
http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-android-r7-nothumb/
The main deal breakers are that it takes forever to load and that the GUI doesn't scale and all the buttons are too big.
Finally:
Coming from my standpoint, that really didn't call for caps, as what you believed and clearly read into the announcement didn't eventuate anyway.
I am positively glad about that, I hope you are too xD. So far Armv6 isn't going to be left behind (all too far).
20100905 fennec works on hd2- arm 7
Hi,
Fennec seems to work on HD2 (an ARM 7 device).
Not sure I like the rendering of pages like xda-developers.com - but it works.
Seems like it has potential.
newowner
Definitely has a potencial, but it's too slow and so not usable for normal android experience...waiting for beta release
works on the vibrant but very very laggy. UI is ugly but simple to use.
I'm running jcsullins CM11 (20151116), Kernel 3.0.101 (also TWRP 2.7.1.0)
Then using Kernel Tuner I pushed the max CPU to 1782Mhz
I don't use the tablet for many resource hungry apps (Spotify, Reddit, KLWP) but it's prone to being a bit laggy. I'm just wondering (within the bounds of possibility of a 5 year old tablet) if there's anything else I can do to speed it up a bit.
Seems to me like ART on CM11 isn't much more than a proof of concept. I don't really understand filesystems that well to be honest, and I'm reading conflicting posts about whether L or MM based roms are better or not (Evervolv or jcsullins 12.1)
Ok, so with almost 150 thread views in 3 days and no replies, I've taken it upon myself to try these to see how it goes. I'll continue to edit this post with what I find if anyone is interested.
I'm only interested in my perception, not benchmarks. Especially when benchmarks can be differently optimised across OSes and I intend to bounce around a bit.
Dalvik/Art
First thing I did was nandroid and titanium backups, then enabled ART in Dev options. First boot took a couple thousand years to get past the boot animation and Optimising Apps screens (expected) and then the tablet was slow as molasses (somewhat expected). I let the tablet settle down, then rebooted it. Next I methodically opened each app and played around with some basic functions. I then rebooted and repeated the process.
What I've noticed:
The initial boot, running each app etc is a bit of a painful process, but it's worth it. Everything starts up a little faster. Still a bit of lag, but not bad. No app crashes/incompatibility that I've come across so far.
F2FS
Basically this test failed. Flashed TWRP 3.0.0, changed the filesystems and rebooted. Got past the initial setup but no apps would install or update (even play store). Rebooting is like initial boot every time, going through adding wifi, google account etc. Something somewhere isn't writing to this new FS. Good enough reason to wipe it and move on to MM
For F2FS I think you need to use a rom that supports it, such has evervolv.
I tried out cm12.1 and evervolv(mm 6.0).
cm12.1 play store would always crash for me, tried it twice wiping everything. (I did not try Jcsullins version)
evervolv is very nice, the layout of android 6.0 (and 5.x) looks much better then android 4.x (personal opinion). I had zero problems with things not working/crashing. However if your looking for responsiveness, I think your best bet is kitkat with art and overclocking the cpu to 1.78ghz. Performance and battery usage is better in cm11 then anything else I tried. (my opinion).
For cm I use the milaq builds as they are more recent and incorporate security fixes.
I don't know anything about rooting phones was just curious if maybe someone could take this exploit and use it for good use and we would be able to root our phones. I used a program called Quadrooter By Checkpoint and we are vulnerable to CVE-2016-2059 (Elevation of privilege vulnerability in Qualcomm networking component) and CVE-2016-2504 (The Qualcomm GPU driver devices allows attackers to gain privileges via a crafted application, aka Android internal bug 28026365 and Qualcomm internal bug CR1002974.). I'm on Marshmallow with the latest updates.
The article is here
http://thehackernews.com/2016/08/hack-android-phone.html
That is interesting, im not a developer, so im no help, only to test if someone comes up with something. 5.0 OF3.
Quadrooter is a menace, yes, in short time, around 2 months, the gpu may be destroyed only installing unchevked apks.
They are doing a new kind of apk, that i am searching how to forbid these "new" apk model, named as multi dex system.
This is running binary codes inside the cache of the app.
For example:
The telegram.apk is all disabled, the system is capting that all relative to trlegram.apk, is not running.
When you never imagine, a notification, appears on the bar, showinh a new message, but, why?
The app is disabled, but the cached-dex no.
This is a serious menace, because these cached codes are "temporary".
If some "cached dex" is executing, the ram memory goes down, and the system, does not captures this dex running.
Imagine another worst thing:
Any cached dex is programmed to copy and send some victim's bank password for determinated site, in background, on where the system will never shows the relathive dex process at least the relative apk that created this dex.
Be carefull only with the apks thst you install, and never use if is multidex .
You can check if is multidex or not before installing, if haves zipped or jar classes , don't install.
Or the device may be burned.
That is all
Sent fro SomeFon
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)