Related
howdy peeps i have an idea of how maybe we could solve the speed issues with the hero rom but my programming skills have not reached java as of yet, i am learning as we speak, but heres my idea...
im thinking of a program that sits in the background that basically controls the priority of certain programs running on android like rosie.apk.
for instance if the home button is pressed not only is the rosie apk brought to the front but is given more cpu priority over other applications running which in affect should speed up delays. a bit like when you do it in task manager on windows.
i am trying to figure out how to write this with java and the android sdk but wondered what your views are on this and if anyone can actually implement this quicker and better than i will be able to lol
look forward to hearing your views
I'm no programmer but this seems plausible so this would be a program that would prioritize all programs running in the foreground and background or all programs?
dont you think running this program in the background would use up alot of cpu usage also?
even in the background apps of rosie already use up alot of power...this would just take up more space and room and slow stuff down.
if it does get made it would have to be extremely lightweight
good luck
looking forward to what develops
redmdc said:
howdy peeps i have an idea of how maybe we could solve the speed issues with the hero rom but my programming skills have not reached java as of yet, i am learning as we speak, but heres my idea...
im thinking of a program that sits in the background that basically controls the priority of certain programs running on android like rosie.apk.
for instance if the home button is pressed not only is the rosie apk brought to the front but is given more cpu priority over other applications running which in affect should speed up delays. a bit like when you do it in task manager on windows.
i am trying to figure out how to write this with java and the android sdk but wondered what your views are on this and if anyone can actually implement this quicker and better than i will be able to lol
look forward to hearing your views
Click to expand...
Click to collapse
If you can figure out a way to edit the fameworks in /system/framework you'll be fine.
This is called cpgroups - and Cy's ROM and xROM already do this.
The problem with Hero/Mytouch is that the framework is odexed and we have no way to unodex them, edit the files, then remake them.
I love this community. i have confidance that this thread will turn into something good.
im running jaxhero 1.2 and it doesnt lag for me at all. im running compcache with a linux swap
I think this problem is partly due to lack of memory and possibly poor coding.
Hero UI on Dream is slow. Hero UI on Hero is faster, but still not smooth. The extra RAM on the Hero obviously helps since it's the same hardware besides more RAM.
There's a lot of work ahead to get it to run faster. Perhaps work with the NDK instead of the SDK. I assume when an application goes into the background it stops and writes data to memory, the services don't stop. I think to make Hero UI work faster, the code needs to be improved for less memory usage and then optimized more for efficient code. Not a simple task.
I'm not sure if prioritizing tasks will make it faster. It may make it faster to get to Home (once), but once you are there and if you want to start another application it will still need to do what it originally needed to done before it got de-prioritized.
Think of it as cooking, each time you cook something and you want to start something else you can clean up dishes or just leave them in the sink. If you clean up your dishes after each project, you take some time before starting the next one. If you don't clean up the dishes, you can start the new project quickly. However, soon afterward you'll have a sink full of dishes and you can't continue and they need to be cleaned and will take a long time. Thats how I view the problem. Get a bigger sink and more dishes (RAM) or optimize the process so it doesn't use as much dishes or it's quicker to wash them..
Maybe it'll be easily solvable when much fast sd cards are out that we can swap out a lot without slowdowns.
Good luck to anybody who is tackling this.
jad011 said:
im running jaxhero 1.2 and it doesnt lag for me at all. im running compcache with a linux swap
Click to expand...
Click to collapse
compcache is not supported in 1.2
You can remove some of the bloat by reducing the home screen to 5 or even 3 desktops. This should be hex editable, but I don't know enough about HTC ROM to do this.
I also see a lot of improvement in responsiveness of the ROM if I install spare parts from market and turn off window animations as well transition animations. This reduces my battery consumption a lot (passes my overnight standy test: thou shall not use more than 5% battery while on standy overnight for 8 hours) because it seems to be using some sort of graphics hardware accelaration and/or CPU, which makes battery deplete faster.
For my usage, I have been observing the swap usage with swappiness of 30 and I seem to need about 30-35MB most of the time. Now, since this ROM runs slow on Hero also, it seems like the RAM is only a part the problem because Hero does provide more than 35MB RAM on top of Dream. So, the conclusion is that its the inherent bloat in the source code and optimizations which need to be done to reduce the CPU usage. But only HTC can do that.
am i the only one not having any issues w/ the speed? Friend of mine has Cy and im able to keep up with him even though i have 6 big widgets. Only issue is getting in and out of contacts.
imbonez9 said:
am i the only one not having any issues w/ the speed? Friend of mine has Cy and im able to keep up with him even though i have 6 big widgets. Only issue is getting in and out of contacts.
Click to expand...
Click to collapse
YES!
Experienced open source fellow about to chime in here,
Speeding up hero is basically poking around in the dark and hoping that we do the right thing. Unfortunately, because hero (and soon to be raphael and blur as well) are closed source and odexed and whatnot. It's just like windows-vs-linux. At first windows was shinier, but linux eventually caught up because they established a big enough codebase. The problem with hero is that most of it is EXTREMELY hard to "code" or "recode" for the average dev. For this reason the "community" that we have faith in can't do very much, as only one or two people have the knowledge required (not me btw), and they have the sense to promote open source instead of hacking closed source.
Bottom line, and this isn't a flame as much as a lifestyle guide, if you want your phone to be better, and have all the nice hero features, develop for ANDROID. Don't try to hack hero. Dev'ing for android makes things better for EVERYBODY involved.
That's my too sense. As shiny as hero may be....I'm never going to install it.
P.S.
If it explains anything, I'm the kind of person who donates to the FSF. Sorry if that makes me polarized.
[edit]
I apologize for disrupting the purpose of this thread. I'm going to take this to q/a where it belongs. Mostly because I have some questions as to the legality of "hero hacking"
Sorry
sha.goyjo said:
Experienced open source fellow about to chime in here,
Speeding up hero is basically poking around in the dark and hoping that we do the right thing. Unfortunately, because hero (and soon to be raphael and blur as well) are closed source and odexed and whatnot. It's just like windows-vs-linux. At first windows was shinier, but linux eventually caught up because they established a big enough codebase. The problem with hero is that most of it is EXTREMELY hard to "code" or "recode" for the average dev. For this reason the "community" that we have faith in can't do very much, as only one or two people have the knowledge required (not me btw), and they have the sense to promote open source instead of hacking closed source.
Bottom line, and this isn't a flame as much as a lifestyle guide, if you want your phone to be better, and have all the nice hero features, develop for ANDROID. Don't try to hack hero. Dev'ing for android makes things better for EVERYBODY involved.
That's my too sense. As shiny as hero may be....I'm never going to install it.
P.S.
If it explains anything, I'm the kind of person who donates to the FSF. Sorry if that makes me polarized.
[edit]
I apologize for disrupting the purpose of this thread. I'm going to take this to q/a where it belongs. Mostly because I have some questions as to the legality of "hero hacking"
Sorry
Click to expand...
Click to collapse
two important things my momma taught me.
1. Don't say anything if you can't say anything nice
2. Don't do anything you are gonna apologize for later.
I, unlike Mr.Negativity who seems to have some underlying hate for life itself, want a faster Hero rom. Thank you all the dev's that have contributed and will contribute to this cause in the future.
Here's what I have done and seen a good pick up in speed with hero builds, I have an 8 gig cl 4 card but I guess you can do this with a 4 gig card too. make your linux swap partion 128
From what I understand the swap runs kinda like ram. I ordered a 8 gig class 6 card and I will try a linux swap of 256, but I think that will hang bad I'll let you all know in a few days.
But try linux swap set at 128 its much better
sha.goyjo said:
Experienced open source fellow about to chime in here,
Speeding up hero is basically poking around in the dark and hoping that we do the right thing. Unfortunately, because hero (and soon to be raphael and blur as well) are closed source and odexed and whatnot. It's just like windows-vs-linux. At first windows was shinier, but linux eventually caught up because they established a big enough codebase. The problem with hero is that most of it is EXTREMELY hard to "code" or "recode" for the average dev. For this reason the "community" that we have faith in can't do very much, as only one or two people have the knowledge required (not me btw), and they have the sense to promote open source instead of hacking closed source.
Bottom line, and this isn't a flame as much as a lifestyle guide, if you want your phone to be better, and have all the nice hero features, develop for ANDROID. Don't try to hack hero. Dev'ing for android makes things better for EVERYBODY involved.
That's my too sense. As shiny as hero may be....I'm never going to install it.
P.S.
If it explains anything, I'm the kind of person who donates to the FSF. Sorry if that makes me polarized.
[edit]
I apologize for disrupting the purpose of this thread. I'm going to take this to q/a where it belongs. Mostly because I have some questions as to the legality of "hero hacking"
Sorry
Click to expand...
Click to collapse
great advice.....is anyone willin to teach me how to make my own rom??
That_Guy_19033 said:
Here's what I have done and seen a good pick up in speed with hero builds, I have an 8 gig cl 4 card but I guess you can do this with a 4 gig card too. make your linux swap partion 128
From what I understand the swap runs kinda like ram. I ordered a 8 gig class 6 card and I will try a linux swap of 256, but I think that will hang bad I'll let you all know in a few days.
But try linux swap set at 128 its much better
Click to expand...
Click to collapse
Hey guy are you running 128 swap on 1.2? I ran 128 on all the others and they ran super smooth. For whatever reason I had lots of lag with 1.2 and lowered it to 96 which made it run smoother
Naw i got 1.2 but didn't flash it i might skip 1.2 and wait on 1.3 but thanks for the reply and input
ccyrowski said:
If you can figure out a way to edit the fameworks in /system/framework you'll be fine.
This is called cpgroups - and Cy's ROM and xROM already do this.
The problem with Hero/Mytouch is that the framework is odexed and we have no way to unodex them, edit the files, then remake them.
Click to expand...
Click to collapse
wouldn't it be possible to baksmali the odexes, then smali them to a dex and put it inside the apk?
jubeh said:
wouldn't it be possible to baksmali the odexes, then smali them to a dex and put it inside the apk?
Click to expand...
Click to collapse
Sadly only baksmali does not work. There is a way to undex but not as simple to compile as a dex when done.
Seoulboy1 said:
two important things my momma taught me.
1. Don't say anything if you can't say anything nice
2. Don't do anything you are gonna apologize for later.
I, unlike Mr.Negativity who seems to have some underlying hate for life itself, want a faster Hero rom. Thank you all the dev's that have contributed and will contribute to this cause in the future.
Click to expand...
Click to collapse
No one needs to apologize, everything that was said is true. You just don't consider it to be "nice" because you want a faster ROM which you know you probably won't get because of the reasons that were stated. Take the blue pill or the red pill, your choice...
I have a question that turns me on the head a few weeks, but there is a real alternative Home? .. I mean, almost two years now I have the hands on my HTC Dream, I must admit that I've seen very few, and try less. The question arises, there really is a programmer who is working on a real alternative to classic and multiple ROM that you see around? or we will always have many copies of already cooked ROM with only small changes that can range from icons, graphics or small settings to improve performance? Well i notice I'm not complaining about the excellent results we are getting our programmers, who try to keep pace with each new release, ported to every device imaginable (almost all with small donations) etc etc. but I doubt that I'll never have a real alternative as it could be TAT Home or easier SlideScreenPro ..
Sorry for my bad English
deleted...
sorry why?..
Good point, wrong section.
You're totally right about devs who only change or pimp Cyanogen's work. I think it's dumb and pointless. I understand amount of work etc, most of android devs on XDA are very talented people, but after trying 34 or 67th custom rom i saw there's nothing better than CM. Of course, there were several awesome roms like SuperD or sth like that, but after all it's just another pimped CM.
Speaking about home replacements - the greatest apps are those which are modified stock launchers. I don't like a fact, there's no really good other home replacement, but i'd rather use perfect-working ADW or LauncherPro than incompatible, slow, unstable, blablablah, etc. home like TAT, SlideScreen or Zune. And of couse most of those super-extra-special-unique home replacements (which don't even work stable) are paid. There's nothing more to say.
in the pre-CM5 era, there were lots of roms not based on cyanogen
anyone remember open eclair? it had the BEST boot animation ever.
Make your own Simple as that. If you're not capable hire someone. Or lastly, learn to code so you may make your own. Don't think any of the three are worth it, then maybe your idea isn't worth it. Just saying. A last option or rather possibility is having someone more talented than you(coding wise) do it out of their own free will because they share your thoughts.
asb123 said:
in the pre-CM5 era, there were lots of roms not based on cyanogen
anyone remember open eclair? it had the BEST boot animation ever.
Click to expand...
Click to collapse
You got that right. The only real reason all our ROMs are based on CM now is because almost everyone has moved on to a better phone. As soon as the N1 came out it started and hasn't stopped. Also, for that reason, this topic is pretty pointless. If this were occurring way back when Android was new and everyone copypasta'd cyanogen then it would make sense. That was never the case.
And there is nothing wrong with tweaking Cyanogen ROMs. Open source is meant for this. Cyanogen modifies AOSP then themers and file pushers share their optimizations on top of that.
And about a real home replacement: ADWLauncher is a real home replacement that kicks major a**. Ander states that his work is open source as well... So you can take his wheel and make your own little bike, dude. Peddle on...
So in case you did did know, Cyanogen has said that they are not dropping D/S support but rather Cyanogen himself was stopping the managing of the D/S branch (he was previously the one in charge of D/S). This is why we are seeing these "unofficial nightlies"
Cwirl has come out and said that the team is looking for someone to manage the D/S branch. They want someone who uses the D/S as their daily.
Has anyone taken this position?
I am hoping Firerat or Ezterry will be the white knight for D/S
Come on some one please.... take charge for D/S
I dont want to make my "Dream" a paper weight which is not wrecked actually ;-)
I believe that Ezterry or Firerat would do that.
A lot of you are familiar (and have asked) why we don't just have/ask Ezterry and Firerat to take over maintainership. While I like this idea, it would be up to them to decide if they wanted to do so, and, personally, I wouldn't want to feel like CM squashed their creativity and personal efforts. They are doing their own thing right now, and deserve all the props to them for it. If they want to take part in CM, then awesome, we'd welcome it. But thats gotta be a choice they make. Their work can be found on XDA, and is currently your best chance of a 100% Gingerbread install for the DS line.
via:ciwrl at CM
Why does etzerry or firerat have to belong to CM?
they are developing there own rom right now. How would belonging to CM officially help them in any way?
konnspiracy said:
Why does etzerry or firerat have to belong to CM?
they are developing there own rom right now. How would belonging to CM officially help them in any way?
Click to expand...
Click to collapse
Not to mention I like their stuff way better than anything CM.
konnspiracy said:
Why does etzerry or firerat have to belong to CM?
they are developing there own rom right now. How would belonging to CM officially help them in any way?
Click to expand...
Click to collapse
Personally, I would love to see etzerry/firehat to work with CM. So far I've observed all they have to do is maintain an overlay and the rest almost happens by magic and by itself (such as AOSP bugfixes, cm-features, etc)
Also, joining forces in a such scenario like it is now would work better for D/S users.
I hope that they commit their progress to CM also because it looks like that ezterry work is working better than current CM D/S development. It would be better for everyone since there are a lot of CM-users that freakly test every CM-nightly. More people = more fun
However, I do understand ezterry and firehat position. I believe that working apart from CM allows faster development and to get away from cyanogen and cyanogenMOD project shadow...
Personally, now ezterry/firehat development away from CM looks to work great, but in the feature I think I trust more in a big, constantly maintained project like CM
luminoso said:
Personally, I would love to see etzerry/firehat to work with CM. So far I've observed all they have to do is maintain an overlay and the rest almost happens by magic and by itself (such as AOSP bugfixes, cm-features, etc)
Personally, now ezterry/firehat development away from CM looks to work great, but in the feature I think I trust more in a big, constantly maintained project like CM
Click to expand...
Click to collapse
I have never been a fan of CM and done all I can to stay away from his roms and bases but that is just personal choice and the base for my next bit.
I hope Terry and Firerat stay away from the CM group and keep as they are which is independent coders that work well together as this offers users an alternative to CM. It appears if the G1 community lost these two fine individuals then what choice would we have on anything? CM bases roms are all over the forums in some incarnation or other but for those of us that prefer a different flavour in ASOP builds or builds not built around CM then we would loose that one thing that makes this phone so great and as they say variety is the spice of life.
@Terry & Firerat - Simply, thank you.
Kinda mixed feelings. i think there's a lot to be gained from joining forces, in terms of faster access to bug reports and bug fixes. More eyes on the code can only be a good thing, particularly at the kernel level. At the user level, with the various customizations, not sure if there's much to be gained.
But I gotta admit, I really like the notification bar power widget, and miss it when I'm on a plain Froyo build. (Which right now is only on my TP2. And if I could get a decent/stable CM6.1 for my TP2, I'd run it happily.)
shadowch31 said:
@Terry & Firerat - Simply, thank you.
Click to expand...
Click to collapse
+1 !
shadowch31 said:
I hope Terry and Firerat stay away from the CM group and keep as they are which is independent coders that work well together as this offers users an alternative to CM. It appears if the G1 community lost these two fine individuals then what choice would we have on anything? CM bases roms are all over the forums in some incarnation or other but for those of us that prefer a different flavour in ASOP builds or builds not built around CM then we would loose that one thing that makes this phone so great and as they say variety is the spice of life.
Click to expand...
Click to collapse
They are all based on CM because CM provides what developers need to do whatever they want. An actively maintained source. That's even one more reason that, independently of Terry/Firehat developing is own ROM or not is always a plus to merge their achievements on CM.
Note that I am not against/favor whatever should Terry/Firehat in particular do. They do whatever they want! I am just using as an example to discuss general android/xda/etc development philosophy
Theres no reason they need to merge. Its not like either team doesn't openly share their source code. New code and bug fixes flow both ways. And in the long run, its always better to have more choices.
Ohsaka said:
Theres no reason they need to merge. Its not like either team doesn't openly share their source code. New code and bug fixes flow both ways. And in the long run, its always better to have more choices.
Click to expand...
Click to collapse
+1 I'm scared if they join CM we will never get their insightful answers to our questions. How many times has Terry or Firerat been the one to shed light on your problem? Most everyone here has benefited or been enlightened by these two devs. I can't speak for everybody but Cyanogen has never wasted his time on my problems. I hope they do whatever they want to do. It's time to buy new phones and I want the phone that these two devs move to next.
I took up Tmobile on their offer for a free G2.....i feel kind of like a traitor.....but i love the phone
hopefully they do keep updating the phone along with cm...im keeping my old one and will continue updating and playing with it.....
and i highly recommend the g2
I agree with shadow... I think the days of CM for the G1 should come to an end. It has been a wonderful run, but yes...it is time for something else for these phones...
Here is what I posted in this thread: http://forum.xda-developers.com/showthread.php?t=916770
"Who cares? I mean really.. I'm not trying to be a douche by any means. But think of this... We have TONS upon TONS of stuff for the G1 already... Metamorphs to make it "look" like Gingerbread, ton of apps, etc...
Why not let the newer phones have their chance too??
I say we take the software that has been bestowed upon us and improve it. Make it fast, more stable, etc. I mean really... Do we honestly need 45 ringtones, 27 notifications, news and weather, and all that extra "bloatware" in these ROMS right out the gate?
I think maybe we should focus on making a ROM or ROMS smaller, faster, nicer, etc. I know I for one don't "need" all that extra stuff in the ROM... And if I did, I could install it my SD card, keeping the ROM lightweight, fast and stable.
Now, I am not developer, but I damn sure am NOT afraid to try new stuff on my phone. Look at my sig... The ROM I'm running is stupid fast and stupid stable, and I still stripped out over 10MB of "extra" stuff, and still have all the functionality that it was meant to have."
**Just an example of some of the "extra" things we could do to these phones... Think of the PSP field... People, including myself, have modded these to the extreme! Lighted triggers, etc... Check out my sig and click on the last link...
Awesome discussion going on here. I really like the ezterry and firerat's work for gingerbread on D/S. These two developers are really superior developers in the android community. They both work at the source level producing totally authentic roms. Also Looking at cm they are also still at the nighlies and we are at alpha. It does take time to port something new and at the speed we are going is really amazing we had basically nothing working at the beginning. Now almost everything works on the ezterry's gingerbread for D/S. What we need now is just some speed enhancement and some bugfixes. I believe over no time we will have a really good gingerbread rom that can be a daily driver. Also there are people working on the CM7 for dream sapphire as well. I am sure we will definately see CM7 stable on our devices as well even if it takes some more time.
shadowch31 said:
I have never been a fan of CM and done all I can to stay away from his roms and bases but that is just personal choice and the base for my next bit.
I hope Terry and Firerat stay away from the CM group and keep as they are which is independent coders that work well together as this offers users an alternative to CM. It appears if the G1 community lost these two fine individuals then what choice would we have on anything? CM bases roms are all over the forums in some incarnation or other but for those of us that prefer a different flavour in ASOP builds or builds not built around CM then we would loose that one thing that makes this phone so great and as they say variety is the spice of life.
@Terry & Firerat - Simply, thank you.
Click to expand...
Click to collapse
I take a whole different approach. Cyanogen really has been here for us for a very long time. He was not the first, nor he will not be the last great modder. But you cannot say that the impact CM made is not significant. May I ask, one year before now, what mod did you run on your phone? Cyanogen? Dwangs? Enoms? Bens? WG-build? Kings? Hero? I'm willing to say that you probably tried all of them. They all had their ups and downs, but do you know which one of them is still on my nandroid? CM4.2.15.1. For me, that was the most stable build.
Many phones came out since then and devs came and went. Some were skilled wonders like cyanogen and some just copied and pasted bits and pieces. I particularly remember Eclair. It was basically kick ass when we had the first builds out even though everything was broken. I used to use king's 1.9 as it was the fastest. Slowly, everything started falling into place. Live wallpapers were taken apart and optimized, features were added, NCommander helped to reverse engineer the camera, 3D drivers came in (which F*cked up the Live Wallpapers, a problem we still have to this day lol, just try to run the nexus LWP on OE and tell me how crazy smooth it is). The only problem left was the camcorder. By then OpenEclair led by Wes Garner was the best. Finally 1.3 came out and it was amazing. Wes opened a new thread on the very promising OE2.0, but that quickly faded. From that point, I can't remember how much time has passed. People were over the thrill of eclair and going back to donut. Then out of nowhere CM comes out with the test builds of CM5.0.7. EVERYTHING WORKED! Noone else was able to do this. He wrote drivers from scratch. Just ask Jubeh, he was never able to make the camcorder work on his AOSP build. The kernel was a much newer 2.6.32, performance was amazing. It really breathed new life into my phone.
By the time of Google IO when Froyo dropped by, CM was at 5.0.8 and he decided to expand his team from just the Nexus, Droid, and G1 to 7 more devices like the desire and the hero. That is probably when our phones started to suffer a little. Instead of being more tailored to our specific device, it became more tailored to the higher end phones. CM6 finally rolled out and everyone was super exited again. The system required more resources than Cyan's hacked together drivers could deliver. People started complaining, and this is when the complaints about Cyanogenmod really started coming in. When the MT3G OTA rolled out a few months later people in the G1 section had a little bit of a sour taste from CM. People complained and moaned, and hell, some guy even cursed him out on twitter for an issue with MMS (who remembers "FIX THE ****ING GODDAMN SMS"). I think that was the last straw for Cyan, he put the G1 more as a backburner than a daily driver, I mean, Who would you invest time with, a community that cares for your work (Nexus) or one that complains and curses him out (G1)? If we were a little more patient and more supportive I'm sure most of you guys complaining now really wouldn't be.
Since then I've got a G2. I love the phone, and I love CM. Gingerbread is awsome, neocore tops at 58 FPS, quadrant easily reaches 3000, the works. I've really been removed from the G1 section since then, so I can't really comment on ezterry's roms (Somehow my G1 has an exploded battery lol, and I haven't used it in weeks).
I really did not mean to write a story, and thanks for those who took the time to read it, and sorry if anything is out of chronological order. I guess the moral of this whole long story, is that you should treat your devs with respect. You guys are sitting with 3 year old hardware, and just because someone isn't here anymore to defend his work doesn't mean you **** on his work.
Lol, I'm too melancholic, so I 'm just gonna list the things I remember most about this section.
-my first time flashing a radio. My phone rebooted and I was going totally crazy
-use the search! Don't post in development! Your mom is ugly! posts
-"bricking my phone" I spazzed out when I accidentally did a fastboot wipe and my phone wouldn't turn on LOL
-first time I saw the droid red eye boot up on my phone and using LWP's
-the whole incident with Kingklick when he used his winzip skills to copy jubeh's rom, and ended up with all his threads closed. Poor guy (where we got "kanged from")
-Using CM6 for the first time with all the extra options under CM parts!
-Before Firerat the genius came up with custom MTD, we had to run hero roms with system apps in both system and data, and everything else on sdcard!
I better stop now, its getting late lol. I guess my sig sums it up best:
"Thanks to all the devs that make me love my phone!"
CONSIDER THIS THREAD CLOSED
Let me first be clear: I think it's awesome that a phone like the MyTouch 4g was released at a 2.2 phone and has ended up being upgraded to 4.0.4. Let me also take the time to thank the developers involved in this effort. It's hard work and sometimes it sucks to be a dev, and I thank you.
That being said, there are something like 10 ICS ROMS in the development section right now with any combination of
Sense 4
Stock ICS
MIUI
Themed variations
and what do they all have in common? The camera doesn't work properly, the bluetooth is sketchy, and the whole thing is a little crashy in the soft-reboot sense of the word.
My question is this: Why are we releasing so many variations of the same problem when the first one didn't work correctly anyway?
Especially ...Awesome... . I think it's awesome that you want to release like 5 different ICS ROMS, but what does one bring to the table that the other one doesn't? If I'm totally off base here, let me know, but this is what I see from a ROM flasher prospective.
Anyway, end rant and I'm sorry if I offended anybody.
jbdubbs said:
Let me first be clear: I think it's awesome that a phone like the MyTouch 4g was released at a 2.2 phone and has ended up being upgraded to 4.0.4. Let me also take the time to thank the developers involved in this effort. It's hard work and sometimes it sucks to be a dev, and I thank you.
That being said, there are something like 10 ICS ROMS in the development section right now with any combination of
Sense 4
Stock ICS
MIUI
Themed variations
and what do they all have in common? The camera doesn't work properly, the bluetooth is sketchy, and the whole thing is a little crashy in the soft-reboot sense of the word.
My question is this: Why are we releasing so many variations of the same problem when the first one didn't work correctly anyway?
Especially ...Awesome... . I think it's awesome that you want to release like 5 different ICS ROMS, but what does one bring to the table that the other one doesn't? If I'm totally off base here, let me know, but this is what I see from a ROM flasher prospective.
Anyway, end rant and I'm sorry if I offended anybody.
Click to expand...
Click to collapse
I realized this too, but hey, they can do whatever they want.
I mean I know why they aren't completely functional and stable, but I'm confused as to why we've became so obsessed with ICS that we have 50 different ICS ROMs and pretty much all of them are the same just with different settings or whatever. That's why I've been on GB sense for like the past week or two.
Sent from my Transformer TF101 using Tapatalk 2
Things in common
As stated-many roms share problems. As a lover of mt4g anything that keeps my phone alive is progress. Sure ics has camera and some other isssues,but as we all should know and have all been told"this is a work in progress". Many folks = many efforts= different outcomes. Not all ics have reboots,not all have "the camera problem" most do but work arounds exist is some cases. We can always go back to gb. Remember when some gb had camera problems? In time all gets worked out. Besides no arm twisting is done to make us use a rom,it's a matter of personal choice. Am content to wait till camera fix is out but will continue to use ics. Thanks to all the fellas who work for free and express their individuality with the work produced. "drive on"
I2IEAILiiTY said:
That's why I've been on GB sense for like the past week or two.
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
Yes. This is me too.
--sent from my glacier.
trofmoc said:
Not all ics have reboots,not all have "the camera problem" most do but work arounds exist is some cases.
Click to expand...
Click to collapse
Actually, every ICS ROM in the development forum has the camera problem. The "camera problem" being the total lack of video capture unless you use a third party program and capture in VGA resolution at less than 10 fps. As far as I'm concerned, that means the video camera doesn't work, and there isn't a ROM that's worked around this.
Also, so far I've used at least five different ICS ROMS and all of them seem to have soft reboot problems of some sort. Some worse than others, but its there. Usually having to do with the browser or programs that use the stock browser.
Since a camera don't mean anything to me...I am using sense 4 hybrid, which is suprisingly very stable, minus the camera of course. But my wife on the other hand, has to have a camera, so I put sense 3.5 on hers, which is basically perfect in functionality.
Sent from my HTC Glacier using xda premium
I literally just flashed that Sense 4 Hybrid, and it about blew my ear off with the music on the boot screen.........
lack of a kernel prevents certain hardware from working correctly
however, i do agree that there are WAY too many SIMILAR roms (and some from the same dev, too). itd be nice to try to put all your resources on one AOSP, one AOKP/CM9, and one ICS-Sense.. teamwork! community! linux!
to each thier own, i guess. lets appreciate all the ROMs.. because if we didnt have any devs still working here wed be a lot more annoyed
On the bright side, as fixes are found/created the existing ROMs can be patched and you'll have more functioning ROMs to choose from. Also, these guys went from ports to compiling and then they started modding framework-res.apk's and SystemUI.apk's for theming. Essentially, if they hadn't done all this work their knowledge would not have progressed like it has. Now they will be able to use those skills to continue to benefit the whole community if they choose.
Wow total lack of respect from a NOBODY! Don't worry ill have all my threads closed and good luck with this phone stay on stock for all I care name 1 single thing u have contributed to this community besides u whinning and complaining about everything good luck to this community and the rest of the devs that are still here... This is the last you guys will have heard from me... GOOD LUCK! !
Sent from my ROOTIE TOOTIE FRESH 'N FRUITY GLACIER
Way to go fellas...say goodbye to Awesome. Anyway, do yo guys read the ICS OPs? Here is a nice quote that explains stuff. Bit seriously. Be thankful for ICS....posts like these make us feel unappreciated.
saranhai said:
FAQ - THE BIG PICTURE
What is ICS?
ICS is Ice Cream Sandwich - Google's latest version of Android.
- Some of the very latest phones on the market already have it installed. e.g HTC One series
- Some slightly older phones will eventually be 'upgraded' to ICS e.g Desire HD, but this may be a number of months away, and promised 'upgrades' have sometimes never been delivered at all.
- If / when it does arrive for Desire HD it may not happen for everybody at the same time, sometimes it's carrier by carrier, and finally 'retail' (non carrier branded) handsets that get the upgrade last!
- If / when it does arrive, it will be overlayed with HTC's Sense (some like it, some don't)
- In the meantime, folks are working on getting ICS on your Desire HD BEFORE it's officially released for the phone, with and without Sense (giving you a choice)
So why don't some features work?
Well, the ICS being used on Desire HD is 'taken' from officially released ICS phones like the HTC One range, or 'leaked' ROMS from similar phones.
However, those phones have slightly different hardware and features than the Desire HD - so they aren't exactly the same. This means that parts of the software have to be 'ported' to work on the Desire HD.
OK, so why is porting so difficult?
The Android O/S is 'open source' meaning that anybody can see the actual source code for themselves, and see how it all works. They can modify it and adapt it to suit their needs (good).
Phone manufacturers USE Android in their phones, but they don't have to make all their own 'extra' software open source too. They like to protect their software by keeping it secret (not so good). There are many reasons why they do this, both good and bad, but it makes porting difficult.
When developers don't have access to the source code for parts of a phone, they have to write their own!... this means they have to have highly detailed knowledge of the phone, its hardware and other software components. Sometimes they can try things by trial and error, sometimes they have knowledge from a similar phone, and sometimes they just don't know.
This is the most common issue for 'ported' ROMS. Things like Power Management, Camera, WiFi, GPS etc are the things that make one manufacturer's phone stand out from another, and therefore end up 'secret'.
This does not mean that they will never work, it only means that they take longer to get working.
Who does the porting?
The actual porting is done by surprisingly few people:
- Some guys who know 'inside secrets'
- Some guys who are just great developers but who don't have the secrets
- Some guys who can develop but need a little guidance
- Some of them are 'great guys' helping the community (and keeping their own skills up to date)
- Some of them have other motives (good and bad)
- Some of them form teams to work on different ports
Why don't all the developers work together?
Developers are people - they have all the same issues as everybody else:
- Some like working alone
- Some feel that other developers standards aren't high enough
- Some are trying to fix a specific problem that THEY want fixed
- Some teams have different goals (one team might be aiming for a port that can work on 5 different phones, whilst another team are focused on a single phone. One team may want a totally 'clean' ROM and another want a ROM with lots of customisation options built in)
- Sometimes, people just don't get along with each other
I thought the ROM makers did all this work?
You'd be wrong.
The ROM developers use the ported code to make their ROMs. Sometimes they can choose different components from the various development teams to build a ROM.
Imagine a motor car:
1) The 'developers' make the engine, wheels, steering, chassis etc
2) The ROM Makers build their car choosing the components they need for their ROM
3) The 'Modders' add custom paint colours, fancy headlights, custom interior etc
The 'developers' are not smarter than the ROM makers, and the ROM makers are not smarter than the modders. They just have different roles (and some people do all three roles!)
Click to expand...
Click to collapse
Sent from my Sense 4.0 Glacier using XDA Premium.
...Awesome... said:
Wow total lack of respect from a NOBODY! Don't worry ill have all my threads closed and good luck with this phone stay on stock for all I care name 1 single thing u have contributed to this community besides u whinning and complaining about everything good luck to this community and the rest of the devs that are still here... This is the last you guys will have heard from me... GOOD LUCK! !
Sent from my ROOTIE TOOTIE FRESH 'N FRUITY GLACIER
Click to expand...
Click to collapse
Though I respect and agree with you I really hope you're kidding because if your not I'm probably gonna cry. How am I supposed to sh*t rainbows now!?
I have half a mind to hurl insults at the OP(Way Off Base) as if I were in a drunken rage. Not only did he offend but he called out a Dev which is uncalled for. You can say sorry for offending someone all you want but your sorrys, and you for a matter of fact haven't done sh*t for our device. I don't believe you have the right to rant seeing as how you have contributed nothing and possibly just cost the MT4G one of its best devs. I hope we still have developers that are not fed up with us.
...Awesome... said:
Wow total lack of respect from a NOBODY! Don't worry ill have all my threads closed and good luck with this phone stay on stock for all I care name 1 single thing u have contributed to this community besides u whinning and complaining about everything good luck to this community and the rest of the devs that are still here... This is the last you guys will have heard from me... GOOD LUCK! !
Sent from my ROOTIE TOOTIE FRESH 'N FRUITY GLACIER
Click to expand...
Click to collapse
Well, damn....
Please mind the collective ego of the Dev's here. It bruises pretty easily. I tried to make the point earlier that all that work is very useful because it hones their skills, but I guess it was already too late. I sincerely hope we haven't lost another one.
Don't forget that, basically the best ICS kernel we have came from a mod that ...Awesome... did on the Tiamat kernel
Also http://forum.xda-developers.com/showthread.php?t=1641147
estallings15 said:
Well, damn....
Please mind the collective ego of the Dev's here. It bruises pretty easily. I tried to make the point earlier that all that work is very useful because it hones their skills, but I guess it was already too late. I sincerely hope we haven't lost another one.
Don't forget that, basically the best ICS kernel we have came from a mod that ...Awesome... did on the Tiamat kernel
Also http://forum.xda-developers.com/showthread.php?t=1641147
Click to expand...
Click to collapse
The point I'm trying to make is non of you guys know what goes on behind the scenes you just have people like the OP to complain about any little thing... For example who here's noticed elginsk8r had his own cyanogen kernel on his cm9 Rom?? Who here knows that THEindian is working on the vkernel? Who here knows blackwing and I are trying to compile a kernel for the camcorder to work? Who here noticed if u flash elginsk8r kernel u get semi working camcorder don't say we aren't working together on fixes if u guys knew all and every little thing we all are doing and don't come out publicly and say it doesn't mean we aren't working together because WE ARE because it benefits all of us not just 1 person
Sent from my HTC Glacier using Tapatalk 2
...Awesome... said:
The point I'm trying to make is non of you guys know what goes on behind the scenes you just have people like the OP to complain about any little thing... For example who here's noticed elginsk8r had his own cyanogen kernel on his cm9 Rom?? Who here knows that THEindian is working on the vkernel? Who here knows blackwing and I are trying to compile a kernel for the camcorder to work? Who here noticed if u flash elginsk8r kernel u get semi working camcorder don't say we aren't working together on fixes if u guys knew all and every little thing we all are doing and don't come out publicly and say it doesn't mean we aren't working together because WE ARE because it benefits all of us not just 1 person
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Amen. Honestly people. Patience...
my 2¢
I personally didn't think the OP was disrespectful. I think a number of devs are probably feeling similar frustrations even if from a different perspective.
I do think it is up to each user to decide to try new ROMs. If they don't work for you, then its a non-starter - go back to what works for you without complaint.
I also think it is important to remember that there are many different types of users - always. I am a software developer and I hit the same thing in my work. Some people are just looking for a solid ROM - and lack much understanding of the underlying complexity. That they're here at all places them way beyond the average smartphone buyer.
Others are Android jockies - here every day (even every minute) with a lot of their life revolving around ROM dev/swapping. It's probably important to them how they're perceived in this community.
Constructive criticism will and can be received differently by everyone within that spectrum.
Personally, I think it's great to have lots of options - it will end up serving everyone. At the level of experience I have (little!), I have gotten confused when the ROM thread titles are cute and don't indicate what they are - or their lineage. When I dig in and read the threads, there's definitely good ICS options there.
HMMMMM
I DON'T PAY BUT I USE, I DON'T FIX,BUT I COMPLAIN - IF IT DON'T WORK I'M READY FOR A QUICK FIX. TOO MANY CHOICES[somethings wrong]. NOT ENOUGH CHOICES[someone's lazy]. go to any other android forum and see how many folks are interested in mt4g. HARDLY ANY. PLEASE BE GLAD FOR WHAT WE HAVE.
I for one would like to say that I feel almost ashamed, that I use these roms, and I don't say thank you enough. Let me be honest, because at my age, its hard to fall asleep at night, having told a lie. I'm struggling right now, keeping my power on, & feeding my family. I'm laid off and looking for work, and while I would love to donate to these devs for their work, I simply don't have the money. But as soon as I do, I will gladly. I'm not looking for pity, just being honest. But a big thanks to all devs, porters, mods, anyone that devotes time here, because that's something I do know, time is a precious thing that shouldn't be taken for granted..
Sent from my HTC Glacier using xda premium
I don't think the OP was being disrespectful or intended to.
I see where he's coming from b/c there are a lot of ICS ROMs with common issues. Like we don't need three different AOKP ROMs for example, and if anything, it's gotta be hard on ...Awesome... to track progress for the fact he has several ICS builds and different threads, at least that's what I think, which is why I agree with the OP when he calls ...Awesome... out like that b/c all of his ROMs are basically the same, just w/ different "flavors" so it seems. If it was me, I'd put out just one ROM and give you guys no choice at all. If you really want all the silly things like themes and stuff, then do it yourself.
The vanilla ROM, is perfect. AOKP is fine. CM9, great. But ****ting Rainbows and Rootie Tootie (which is bloated to the max IMO) are unnecessary, esp. since it doesn't fix any of the core problems such as RR and SoD's and etc. and that only adds more threads to keep up with and distracts you from the things that really do matter. Yea it's cool and neat that you can get a ton of extra add ons into the ROM, but don't put all your work into just trying to make those silly settings and stuff work.
And another thing, ICS is a neat little project for our device, but if you want all that other **** and keep acting like you absolutely need to have ICS fully functional on this old outdated phone, then either A) go back to GB and be content w/ that until ICS is out of BETA or B) get a new damn phone, like everyone else has been doing. We're obsessed w/ ICS when we have perfectly, fully functional GB ROMs that devs have worked hard on too, like sckboy for example. He's still putting out GB ROMs and I bet some of you guys aren't aware of this at all b/c the ICS threads stay at the top of the forums pretty much.
jjbadd385 said:
I for one would like to say that I feel almost ashamed, that I use these roms, and I don't say thank you enough. Let me be honest, because at my age, its hard to fall asleep at night, having told a lie. I'm struggling right now, keeping my power on, & feeding my family. I'm laid off and looking for work, and while I would love to donate to these devs for their work, I simply don't have the money. But as soon as I do, I will gladly. I'm not looking for pity, just being honest. But a big thanks to all devs, porters, mods, anyone that devotes time here, because that's something I do know, time is a precious thing that shouldn't be taken for granted..
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Thanks man and like I've said before nobody here is doing it for money/donations specially me I do it for people to have a variety and its a hobby for me that I love doing...
I have a
Sense rom for all u sense freaks
AOSP & a AOKP rom for u ics fans
Cm9 rom
Variety!!! if it bothered the OP so much that theirs variety don't flash non of my ROMS thank you again and ill say it again as long as in my count 1 person is still using ANY of my roms ill keep updating them ENOUGH with this thread and the OP. Till he contributes 1 thing to this community he should be allowed to complain!!! As far as ANY other person in this community instead of complaining about a feature offer a suggestion the best one ive hear came yesterday when someone said they needed wifi calling for daily use sure they reported the same problem AGAIN but atleast he made a suggestion on how to fix it or try to fix it...
Sent from my ROOTIE TOOTIE FRESH 'N FRUITY GLACIER
Hoping this is the right section since its not device specific.
Experienced or not, it doesn't matter. I've been on XDA for a number of years. And am noticing things from my own experience and talking to others. Its hard to get help sometimes. Not all devs want to talk. Teach. Or help people all the time. Devices are being dropped from support. Maintainers are leaving the scene. Currently I have an Oreo and pie ROM for s6e+ and note 5. With the list of devices being dropped, and surprising amount of people reaching out to me for support, I decided it may be beneficial to recruit a few people who want to develop ROMs. This is a great chance to learn. I would like to pick up at least partial support for several more devices, and need some help to do it. My goal in this endeavor is to continue to provide ROMs to people who need them, while teaching other users to develop. This will help to bring fresh life to the scene, and allow support for more devices to be added. If you are interested reply below or inbox me. There is a google hangouts set up, and other methods of team communication will follow. I also have a home server with a 24/7 connection and no data limits on my internet, and an ftp set up to host files directly and not need third party sites.
so basically you have good intentions, no plan and a home server )
what we really need is a unification of all the different but not really different roms and their devs,
then its possible to see a future for long term support for all devices, or at least many.
anyhting else is jsut another project that will or will not die, based on good will and free time of the maintainer, mostly not even reckognized
due to the chaos of fragmented android and even more fragmented custom rom scene.
godkingofcanada said:
Hoping this is the right section since its not device specific.
Experienced or not, it doesn't matter. I've been on XDA for a number of years. And am noticing things from my own experience and talking to others. Its hard to get help sometimes. Not all devs want to talk. Teach. Or help people all the time. Devices are being dropped from support. Maintainers are leaving the scene. Currently I have an Oreo and pie ROM for s6e+ and note 5. With the list of devices being dropped, and surprising amount of people reaching out to me for support, I decided it may be beneficial to recruit a few people who want to develop ROMs. This is a great chance to learn. I would like to pick up at least partial support for several more devices, and need some help to do it. My goal in this endeavor is to continue to provide ROMs to people who need them, while teaching other users to develop. This will help to bring fresh life to the scene, and allow support for more devices to be added. If you are interested reply below or inbox me. There is a google hangouts set up, and other methods of team communication will follow. I also have a home server with a 24/7 connection and no data limits on my internet, and an ftp set up to host files directly and not need third party sites.
Click to expand...
Click to collapse
I respect your Idea but I don't think something like this is required.You see I had been using linux for 4+ years and was pretty adapted to it when I switched to a Note 3.Recently I discovered the Modding part of it and the huge development of custom roms and kernels.and despite having no clue what I was doing I could easily develop a Kernel without a hassle.I went even one step further and made a halium port for it.Sure it didn't boot the first time but by using methods on xda already discussed in detail I was able to make it work.So,the main thing is that someone like me who has no experience could make a ROM in 3 hours without any complications(Except those who could be solved by googling).Then anybody could do it.Currently there isn't a ROM bug or a issue that hasn't been discussed on either xda or other android development sites.But that doesn't mean we shouldn't help newcomers.But it is rare for someone to look on the other side of development and there is enough documentations for him to do it.Maybe too much.qq
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
I respect your Idea but I don't think something like this is required.You see I had been using linux for 4+ years and was pretty adapted to it when I switched to a Note 3.Recently I discovered the Modding part of it and the huge development of custom roms and kernels.and despite having no clue what I was doing I could easily develop a Kernel without a hassle.I went even one step further and made a halium port for it.Sure it didn't boot the first time but by using methods on xda already discussed in detail I was able to make it work.So,the main thing is that someone like me who has no experience could make a ROM in 3 hours without any complications(Except those who could be solved by googling).Then anybody could do it.Currently there isn't a ROM bug or a issue that hasn't been discussed on either xda or other android development sites.But that doesn't mean we shouldn't help newcomers.But it is rare for someone to look on the other side of development and there is enough documentations for him to do it.Maybe too much.qq
Click to expand...
Click to collapse
You can't just make a ROM for any device is 3 hours. It doesn't always work that way. Especially not if building from source
godkingofcanada said:
You can't just make a ROM for any device is 3 hours. It doesn't always work that way. Especially not if building from source
Click to expand...
Click to collapse
I just followed a guide.On an XL VPS. With maybe 22GB ram and 16 xeon cores
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
I just followed a guide.On an XL VPS. With maybe 22GB ram and 16 xeon cores
Click to expand...
Click to collapse
I don't disagree sometimes it is easy. But what if lineage or GitHub don't have all necessary files for the build? And then you need to extract them from your phone manually, or if build won't boot up and needs modifications to the kernel.. fixing drivers that do not work. It's not always so simple as build, flash and finish.
godkingofcanada said:
I don't disagree sometimes it is easy. But what if lineage or GitHub don't have all necessary files for the build? And then you need to extract them from your phone manually, or if build won't boot up and needs modifications to the kernel.. fixing drivers that do not work. It's not always so simple as build, flash and finish.
Click to expand...
Click to collapse
I did face issues.The End of the guide covered the basics of logging stuff and finding things.They were just as same as debugging a linux OS but yeah you're right as I did face the extracting files(dunno what was supposed to do).So I wrote "extract proprietary vendor code from ROM" and boom lineage gave it to me.Also the guide was only for devices that exist on lineage and sometimes we need to start from scratch.And maybe We both are,Who knows what the future might bring,BTW have you heard about Google's new Boy Fuchisa or something like that.I wanted to talk someone in the field of development about this but nobody was bringing up the non-linux version of Google's OS for smartphones.
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
I did face issues.The End of the guide covered the basics of logging stuff and finding things.They were just as same as debugging a linux OS but yeah you're right as I did face the extracting files(dunno what was supposed to do).So I wrote "extract proprietary vendor code from ROM" and boom lineage gave it to me.Also the guide was only for devices that exist on lineage and sometimes we need to start from scratch.And maybe We both are,Who knows what the future might bring,BTW have you heard about Google's new Boy Fuchisa or something like that.I wanted to talk someone in the field of development about this but nobody was bringing up the non-linux version of Google's OS for smartphones.
Click to expand...
Click to collapse
Yes I heard about it. I stumbled across it by accident looking for a way to shim the s6 edge plus cam on my pie rom. It lead me to reading about vulkan, which showed me a new Google os. It looks nice
godkingofcanada said:
Yes I heard about it. I stumbled across it by accident looking for a way to shim the s6 edge plus cam on my pie rom. It lead me to reading about vulkan, which showed me a new Google os. It looks nice
Click to expand...
Click to collapse
Well It seems that it uses a Different type of kernel "microkernel".For someone as stupid as me I don't get it what was the difference between a microkernel and monolithic one on an android device(or a low powered arm processor based board that has a screen attached to it)Will it be performance,Faster loading,Efficiency.I can find a million articles on microkernel vs monolithic but they are in latin for me.But you can just give me the crash course in maybe 3-4 lines.
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
Well It seems that it uses a Different type of kernel "microkernel".For someone as stupid as me I don't get it what was the difference between a microkernel and monolithic one on an android device(or a low powered arm processor based board that has a screen attached to it)Will it be performance,Faster loading,Efficiency.I can find a million articles on microkernel vs monolithic but they are in latin for me.But you can just give me the crash course in maybe 3-4 lines.
Click to expand...
Click to collapse
Device drivers, protocol, file systems moved from kernel to user. It's got less code, more lightweight. And it was created with embedded systems in mind. In theory it should be faster, and more suited to small devices like phones with embedded systems. Giving devices their own dedicated kernel finally instead of butchering a Linux kernel to suit their device needs. It's also universal in terms of cross platform
godkingofcanada said:
Device drivers, protocol, file systems moved from kernel to user. It's got less code, more lightweight. And it was created with embedded systems in mind. In theory it should be faster, and more suited to small devices like phones with embedded systems. Giving devices their own dedicated kernel finally instead of butchering a Linux kernel to suit their device needs. It's also universal in terms of cross platform
Click to expand...
Click to collapse
Now that's more like it.I was afraid that android was finally going to commit close source(or suicicde).But since it's open source and I hear good things from you and 4 other guys who have experience in doing stuff I think,Hope and Pray that it might be a good change.Also thanks for using plain English and being a Open guy.Currently I am thinking that 5 years from now someone gonna run into this post and have a little smirk on his face for you who is reading this,Quote and tell me was it good?Was we good?
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
Now that's more like it.I was afraid that android was finally going to commit close source(or suicicde).But since it's open source and I hear good things from you and 4 other guys who have experience in doing stuff I think,Hope and Pray that it might be a good change.Also thanks for using plain English and being a Open guy.Currently I am thinking that 5 years from now someone gonna run into this post and have a little smirk on his face for you who is reading this,Quote and tell me was it good?Was we good?
Click to expand...
Click to collapse
I think the changes appear good. Less stuff locked away in private, more easily accessible to all. Treble has the vendor stuff available to roms that aren't stock, this will make the kernel tiny and easy to build. One by one the barriers people have to overcome to build their own roms are being taken away.