Related
Please stay ON TOPIC to kernel DEV and missing code. Don't report every bug the Android build your using is having or it will be deleted as OFF TOPIC
As you all might be knowing that hd2 is pretty much a android native device now. Its just like any another snapdragon device. The current kernel code we are using in HD2 is pretty obsolete and missing a lot of things. It more like something working at its minimal efficiency. While i was porting over all the HD2 board files getting it on par with the other snapdragon devices I found out a lot of code was missing and some was obsolete. Eg. The gsensor code from microp was pretty minimal, a lot of things were missing in microp code. I suspect that it isnt the only code, a lot of bluetooth related stuff was missing and much more. I am not really gonna work on backporting the stuff to .32 kernel so i would like the kernel devs here to backport the stuff to the .32 kernel so a lot of bugs can be fixed and stuff can be made more stable until the .37 kernel is ready. All the commits can be found here
https://github.com/charansingh/cm-kernel/tree/master
There might be some bravo or passion instances in there cuz i am comparing the code with these two devices and taking what is necessary and sometimes i have to leave my work due to some other work and forget which file i was working on so would appreciate the more bugs.
Also Mods can we get this a sticky so we can track the progress here
Yap.. i'm not a really pro developer but i suspected those bugs before.. finally a real developer suspected that.. eager to see who's going to help fixing them
charnsingh_online said:
Also Mods can we get this a sticky so we can track the progress here
Click to expand...
Click to collapse
Ok sticky for the moment to see if it helps.
@charnsingh_online
I am really happy that you put so much power in this project big respect for that.
The reason for the missing code is because most of the drivers are reversed engineerd from winmo by cotulla. Wich make it possible to make working android parts but they don't work optimal by that. Also we miss some skilled active coders. After cotulla almost everything is created by markinus he did a incredible part big credit to him but looks like he isn't that active anymore..
Current development are mostly little things a guy who sees a little part from that and a little part from that like : you, tytung, darkstone, gauner,letama, the guy from the bluetooth fix.
We probaly don't have so much real kernel programmers because they buy a native linux / android phone.
The last two major things left with HD2 Android are buggy speakerphone and missing assisted-gps function.
Speakerphone mode is not usable because mic gain does not change when speakerphone is enabled. Info here:
http://forum.xda-developers.com/showpost.php?p=12698204&postcount=22
GPS works but without assistance so most locks take 1 minute instead of like 15 seconds. Info here: (please read all 25 pages)
http://forum.xda-developers.com/showthread.php?t=1008252
memin1857 said:
The last two major things left with HD2 Android are buggy speakerphone and missing assisted-gps function.
Speakerphone mode is not usable because mic gain does not change when speakerphone is enabled. Info here:
http://forum.xda-developers.com/showpost.php?p=12698204&postcount=22
GPS works but without assistance so most locks take 1 minute instead of like 15 seconds. Info here: (please read all 25 pages)
http://forum.xda-developers.com/showthread.php?t=1008252
Click to expand...
Click to collapse
actually i think the gpu drivers are kinda unstable when comparing to the performance of other phones that carry the similar gpu...
@charnsingh_online
Good start.
After reading the github commits, I still don't understand what kernel devs can do so far.
Just see the microp stuff I added to the file. Also I have updated the board files. See wats the difference between the files. A lot of updated code
hi charansingh,
i am willing to help, but i think it would be helpfull to define packets to take over.
By looking in the kernelsources it looks good to me, but i know from own expiriences with porting that i have to look deep...
best regards
trilu
charnsingh_online said:
Just see the microp stuff I added to the file. Also I have updated the board files. See wats the difference between the files. A lot of updated code
Click to expand...
Click to collapse
It's better to start/clone from pure CM 2.6.37 kernel, then add new commits when adding any new functions.
Would you please add a new commit when adding a new function?
Otherwise, it's very easy to lost the way in the source code.
A commit "Update some board files" doesn't tell the whole story. I want to know why to change.
Comparing the source code manually and guessing its function is not convenient for any kernel devs.
For me, I won't add any code in my 2.6.32 kernel until I know the meaning of the changes of the source code.
Thanks.
Ok I'll do it tomorrow n also maintain the list in the op
I may be wrong, but this thread is not supposed to become a bug fix request thread. It is aimed at developpers, so that they collaborate on a merging of HD2 specific stuff onto a cyanogen 2.6.37 kernel...
This would most likely result in the resolution of a lot of our issues, but in the mean time, [DEV] in the thread title means it is for devs only......
Keep this thread clean please.. there are only a select few devs who actually work on kernels around here. Let them use this as a way of communication to generate a complete kernel, then we can test it for bugs.
Very excited about the prospects of this, if you guys get a working kernel with all the new commits shoot it over and I'll test it out on one of my HD2's.
I looked pushed code and it's ok, at least for first few commits. But it needs some deep cleaning an optimization, also there is some bravo naming convention used in leo specific files. You should put this tree on gitorious so we can do more work on it, but anyway i will clone tree and do some cleaning and porting new stuff.
This could be of interest, and not too much off-topic.
This kernel: http://forum.xda-developers.com/showthread.php?t=966786
is being abandoned and it had some patches for performance that I think are valuable. It had linpack scores that can be achieved only with heavy overclocks on other kernels... The problem is, the source is being distributed by a .zip, no commits, nothing... the only way to get those would be to issue a diff with... something and guess where they are. Staying on topic, I've already adapted cm-kernel for another device so I think I'll be able to help when I get enough free time to spare.
D4rk50ul said:
Keep this thread clean please.. there are only a select few devs who actually work on kernels around here. Let them use this as a way of communication to generate a complete kernel, then we can test it for bugs.
Very excited about the prospects of this, if you guys get a working kernel with all the new commits shoot it over and I'll test it out on one of my HD2's.
Click to expand...
Click to collapse
Yes you are right. Unfortunately many threads like this one get's filled with off topic chatter, complaints etc. I will try to keep my eye on this thread so the dev's can communicate. If your not contributing to the DEV work on the HD2 kernel's, please don't post your wishes and thanks post as this will quickly clog up the thread. I'd hate to lose progress due to this. That's why many DEV's end up not using XDA and reverting to IRC only. Thanks
noellenchris
Hi,
Few days back there are some conversation about libsurfaceflinger.so for color banding issue http://forum.xda-developers.com/showthread.php?t=1012278 . Since Rom is changing continuesly with libs can we port the change for color issue.
HD2 GB-2.33-SENSE-2.1 LOCKSCREEN SENSE-3
tytung said:
It's better to start/clone from pure CM 2.6.37 kernel, then add new commits when adding any new functions.
Would you please add a new commit when adding a new function?
Otherwise, it's very easy to lost the way in the source code.
A commit "Update some board files" doesn't tell the whole story. I want to know why to change.
Comparing the source code manually and guessing its function is not convenient for any kernel devs.
For me, I won't add any code in my 2.6.32 kernel until I know the meaning of the changes of the source code.
Thanks.
Click to expand...
Click to collapse
tytung, has any1 of you done so? please let us know..
g30rg10u said:
tytung, has any1 of you done so? please let us know..
Click to expand...
Click to collapse
No, I didn't work on 2.6.37 kernel so far.
I didn't see that charnsingh_online added a TODO list in the OP.
Fried my laptop charger. New one on way. Hd2 arrived
# I am not responsible for anything that happens to your phone
# Please keep in mind that many of these roms have ideas from other developers, so you will see some of the same tweaks. This is a learning process
# for me. I intend to keep learning with your constructive criticism. If you think I stole something from you, please pm me and I will either remove it or
# give you credit. If you have something that you think will help me, please feel free to tell me. This is just my way of sharing my current progress with
# the development community. If you know more about something than me,
# let me know.
This is a stock looking Rom with lots of tweaks. It runs smoothly. I would use it with Go Launcher. I have tested it with Synergy kernel and recommend it. This Rom comes with a new feature that is not completely ready. You can run it in terminal:
Code:
su
cd /etc/init.d
sh start.sh
sh fkturbo1.sh
This is not a completed rom but all the bugs I found have to do with the added scripts. All of the tweaks should work. Others will be added when I have time. I was hoping to get more done, but I started out in Notepad. It took me a day to remember that's why the script doesn't work. I hate Win 7. lol
Also, themes will be included when it is out of beta.
#NEW# FKTurbo v.2b
This feature allows you have a turbo in your phone. The higher the frequency goes, the faster and more powerful it will be. When completed, this will increase multiple settings towards performance when your phone is used heavily. It will automatically set them back to save power. It will be improved to remove all bugs and errors and work seamlessly with your phone. It is in beta, so I know there are some bugs that will be fixed. It will not activate on boot until it runs perfectly. I will add code to make it activate in a much smoother way in the next release.
Advantages:
-Easily switch to max power when you absolutely need it, automatically.
-Easily switch to power saver mode when you need good battery life, automatically.
-Go longer between charging by using extra power only when you need it.
-No more adjusting multiple settings to go from max power to max saver.
More new features as soon as this gets running right!
GB.6.tweak v.1b (Removed due to problems.)
fktweakedv0.2b (name changed)
fktweakedv0.4:
All features listed below.
Lightly themed.
Improved fkturbo.
Base on Mr.X's CIQ free 2.3.6
In the rom:
CIQ free 2.3.6
WiFi Calling
Deodexed and Zipaligned
SU
BusyBox
Init.d support
Kernel tweaks
VM tweaks
Data tweaks
Scrolling responsiveness tweak
Zipalign at boot
launcher in memory
UI with GPU
Delvik increased to 64mb
Wifi interval increased and other tweaks for better battery life
JPEG quality at 100%
Defrag database at boot
Touchscreen sensitivity increase
deadline scheduler tweaks
Sdcard cache increased
Lots of other tweaks
Team Kang's Toggle Buttons
Loopy smoothness
#NEW#FKTurbo#NEW# *
*not completed
Installation with CWM:
1. Download the Rom and your favorite kernel. (Synergy,Bullet,Faux,Darkside) (fkturbo works in synergy, but I haven't checked others yet)
2. Boot into recovery. (Hold Volume Up/Down and power on)
3. Install the Rom first and then the kernel.
4. Reboot and allow it a few minutes on the first boot, then reboot. *No boot animation means that it will go blank for a long time at first boot.
Link to the ROM (4shared):
http://www.4shared.com/zip/qzMe7f6n/fktweakedv04.html
Looks great. I love the MIUI battery gauge. I'll give it a try after v-day.
Thanks Buddy
Looks Nice! Ill report after I flash Thanks man!
Does this rom come with a custom kernal or a stock kernal out of the box
What do u mean of data tweaks and scrolling tweaks ?
Sent from my SGH-T989 using xda premium
fallenmk4 said:
Does this rom come with a custom kernal or a stock kernal out of the box
Click to expand...
Click to collapse
It has a stock kernel, but it will have other available kernels very soon. I plan to update this with the current version I'm running by this weekend. You can use any modified stock kernel. Not AOSP kernels.
ymcmbforever said:
What do u mean of data tweaks and scrolling tweaks ?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
It is a very rough estimate of all the stuff that's in it. Data speed tweaks can potentially increase speed on networks. Scrolling tweaks makes scrolling smoother. Look in /etc/init.d/new2 or /system/build.prop for many of the tweaks. This is the old version, so the new one will have more stuff and a better explanation. Not all the tweaks are listed. There are many more to come!
Im doing this at work, so I don't have the time right now to list everything properly.
system rebooted, please keep the virus away
hit the report button for anyone off topic
Thank you Json. we are waiting for tje new rom coming.
@ Allgamer thank you for cleaning the thread.
New rom. Lightly themed. Almost done with the new feature!
Json'Smyth said:
New rom. Lightly themed. Almost done with the new feature!
Click to expand...
Click to collapse
So the rom is not complete???
Im a little lost
So is the rom in the op the updated or are you in the process of updating?
Not asking for an eta just wondering what rom is in the link.
tdizzle404 said:
Im a little lost
So is the rom in the op the updated or are you in the process of updating?
Not asking for an eta just wondering what rom is in the link.
Click to expand...
Click to collapse
The rest of the rom is working. It is version .4. I am still trying to perfect the code the new feature. I have lots of tests coming up (Bio, Chem, etc.), but I will try to get it perfected by the end of this week. This code is just a teaser that may have bugs in it. It will be updated. Thank you for your patience. Feel free to try it, but keep in mind that it may not work right just yet. If it messes up something, just run fkpower1.sh or powersaver.sh. fkpower1.sh is the better choice.
Code:
su
sh fkpower1.sh
bbobarino said:
Wow what a dousche. Rom control is beast absolutely brilliant and as for the 20 roms we have are awesome and the development in this forum is great. Only thing missing is an operational miui
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Everybody has a right to an opinion, even if it not something you agree with. Please try to keep the thread clean by posting your personal attacks to a different location. I understand that all original work takes lots of time and effort, but name calling is not necessary. Thanks.
Ill give it a whirl. there are a couple features I haven't seen advertised in other roms. _I thought all the haters had left the sgh-t989 tread. Must have just been at the haters ball instead of reading up on the Android kitchen. There is a link some where in the dev thread. Build something better and stop being an ass douché.
superuser696 said:
Ill give it a whirl. there are a couple features I haven't seen advertised in other roms. _I thought all the haters had left the sgh-t989 tread. Must have just been at the haters ball instead of reading up on the Android kitchen. There is a link some where in the dev thread. Build something better and stop being an ass douché.
Click to expand...
Click to collapse
I like your statement. very impressive.
Yes i pm you not posted in the thread posted in your pm rookie keep it to the pm *****
LOL he so butt hurt over. Rom control .....get a life man...[/QUOTE]
Sent from my SGH-T989 using Tapatalk
How about we don't ruin this devs thread for a second time?!? Thanks for your work jasn.
Sent from my SGH-T989 using Tapatalk
So in the sake of getting back to the point at hand what is this feature and what does it do for us?
Edubyah said:
So in the sake of getting back to the point at hand what is this feature and what does it do for us?
Click to expand...
Click to collapse
Good question!
This feature, which still needs some polishing, will allow you to save power when you are not using the phone heavily. It does this by modding the governor settings, which need some tweaking, and the voltage settings, which are being tested today.
When it senses that you are using the phone heavily, it will automatically increase the settings towards performance. As soon as the phone is no longer used heavily, it will automatically change all the settings to favor battery life.
This allows for a perfect balance between the power savings of undervolting, underclocking, and stiffening up the governor and the performance benefits of overclocking, etc.
This eliminates the need to decide between the full power of the phone and the ability to use the phone for longer between charging.
By the end of this week, I will have the settings tested (to make the power change smooth) and more steps between full power and full economy will be added. More settings will be adjusted by fkturbo by the end of the week. It may also be made more universal, but that will take longer than this weekend.
It is being updated to v0.5 for the rom and v0.3 for the feature.
So I was reading through the dev. thread started by Cl3Kener regarding the ROMs hes working on and the age old topic of build.prop changes came up. Someone mentioned a tweak that increased performance prompting the question "Why don't devs include the build.prop changes?". A reply back basically said that most build.prop changes don't actually do anything which is why they aren't included in the ROM. We all know that SOME build.prop changes can improve performance but most do not. I just wanted to share these articles with everyone regarding which tweaks do something and which don't. He does a good job explaining each entry. I learned a lot from it and thought I would share:
jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1
jeffmixon.com/examining-build-prop-tweaks-android-ics-comprehensive-guide-part-2
I wanted to get some opinions on what he says as well.
A big thank you to all those who put in all the hard work making this device so much damn fun to own. :good:
Why don't we have any kernels yet? There's plenty of development... is it a source issue? It's depressing that we're only 53% compatible with Kernel Tuner. I don't know much about kernels, but a few tweaks could go a long way, and I know anything custom wouldn't fly with a CM build kernel.
We really need to get someone to start pumping out custom kernels for this phone. I have no clue where to start or I'd definitely invest the time.
Someone go poke Snuzzo on the ReZound forum and get him on board. *Cough FlyHalf*
Features we need-
Logo to Menu (turns the HTC logo into a menu button)
Govs! -LionHeart, -SmartAss, etc
MPDecision
Audio Buffer Tweaks (improved quality from DSP)
Fast Charge (USB=1A draw)
Thermal tweaks (This phone gets almost too hot when gaming on CM10.2)
Anything Else I haven't thought of...
You have some strong points but in the mean time, I use this one.
http://forum.xda-developers.com/showthread.php?t=2236121
Interesting post....you might want to search the forum for three threads already discussing this. And you come off as demanding.
Yes it is a source issue. We don't have it. I am working on porting one for sense, but it is really difficult.
Sent from my Oney Bone.
jerrycycle said:
You have some strong points but in the mean time, I use this one.
http://forum.xda-developers.com/showthread.php?t=2236121
Click to expand...
Click to collapse
That kernel works on VZW One? Interesting. Anything broken with it? Thanks for the info, awaiting future reply before attempting to flash =)
I like the idea of reclaiming GN's reserved RAM, but we all understand there is no free lunch, those threads only mention 1080p record or playback support, what drawbacks of those RAM hack brought to us exactly?
I don't think most users who flash those kernel or even some kernel developer was acknowledged that. (especially who don't own a GN themself)
I keep seeing phase like "no known negative effects", "The ram being freed comes from things like 1080p playback/recording and other such things that keep ram even when not being used" .
They are wrong.
I test with a few video, show that all RAM hack has more or less backfire to GN's HW play-back ability, quick conclusion:
1. ASRAM is better than BigMEM. ( I just quote them by name, which I read in kernel thread, not pretent knowing what they are...).
2. Stock 693MB is better than ASRAM.
Two chopped video is attached,
When I said "better", I mean the kernel can allow more video files decode in hardware acceleration mode, aka, HW or HW+. Basically there is no video can play in HW mode with BigMem kernel. ASRAM can't play output.mp4 in HW mode, while outputb.mp4 is fine.
If by any chance you don't understand what is the difference between HW & SW playback...
Well, in short, HW will use less CPU to play a video, which lead to better battery performance, much better. I also tested that, it depends on you screen backlight and specific video parameter, in my test, SW mode will consume 2-3 times battery compare to HW mode.
Final conclusion:
If you watch video a lot (most online video is code by AVC1 ), avoid BigMEN hack kernel like superRAM, it's up to you whether use ASRAM though.
NOTICE: all 4.3 or later ROM may need another fix to play video without lag.
http://forum.xda-developers.com/showthread.php?t=2559138
This fix was discovered by @oubeichen
For the record, none of the test video is 1080p
So that's why some videos won't play smoothly on my gnex..
I guess i'll reserve such functions to my n7.
But when i was using no ASRAM/BigMem types like Trinity Kernel the HD playback was choppy too, since the 4.3.x + update everything messed up .
Ashtrix said:
But when i was using no ASRAM/BigMem types like Trinity Kernel the HD playback was choppy too, since the 4.3.x + update everything messed up .
Click to expand...
Click to collapse
Exactly.
I have a 1080p video and it was playing smoothly on 4.2.x but it shutters in 4.3+ Roms.
Sent from my Galaxy Nexus using xda premium
Ashtrix said:
But when i was using no ASRAM/BigMem types like Trinity Kernel the HD playback was choppy too, since the 4.3.x + update everything messed up .
Click to expand...
Click to collapse
That is another issue, and the fix is in the OP too, please refer to this link:good:
http://forum.xda-developers.com/showthread.php?t=2559138
seriousia said:
Exactly.
I have a 1080p video and it was playing smoothly on 4.2.x but it shutters in 4.3+ Roms.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That is another issue, and the fix is in the OP too, please refer to this link:good:
http://forum.xda-developers.com/showthread.php?t=2559138
Mach3.2 said:
So that's why some videos won't play smoothly on my gnex..
I guess i'll reserve such functions to my n7.
Click to expand...
Click to collapse
No, not exactly. The decoder binary has problem since Android 4.3, there is a fix by reverting to 4.2.2 binary, as I said in OP or you can refer to this link:
http://forum.xda-developers.com/showthread.php?t=2559138
SW does the decode thing all by CPU, and GN's 1.2G CPU is OK to deal with many video, you won't notice difference between HW from SW except the battery drain in most of the case.
I've read the source of BigMEM and ASRAM, they are the same thing. They just used try & error way to "find out" that took 50MB from the heap_tiler instead of the more aggressive 70MB will keep the carama 1080p work, nothing sophisticated. Those developer didn't realize this heap not only relates to the ability video can play or not, but also hardware decode ability.
Honestly, I hope they don't realize that, or they were lying and put the blame on application
randommmm said:
I've read the source of BigMEM and ASRAM, they are the same thing. They just used try & error way to "find out" that took 50MB from the heap_tiler instead of the more aggressive 70MB will keep the carama 1080p work, nothing sophisticated. Those developer didn't realize this heap not only relates to the ability video can play or not, but also hardware decode ability.
Honestly, I hope they don't realize that, or they were lying and put the blame on application
Click to expand...
Click to collapse
How did you come to a conclusion that they were lying? And some developers DID realise that video playback is also broken and even has that mentioned in their threads. Or indirectly mentioned that things may break by making different variants for different users.
And by the way if you want 100% stable and working phone, xda or any other place that encourages you to tweak your phone is a complete no-no for you.
Sent from my Galaxy Nexus using Tapatalk
Most devs mention that this "hack" breaks "things".
The matter is how important to a certain user is the ability to play flawlessly every video available.
Most users aren't bothered at all...
"Bigmem" and "ASRAM" and bull****. They aren't anything special.
They do the same thing to a different amount. "Bigmem" reclaims more than "ASRAM" and "SuperRam" reclaims even more than "Bigmem".
Mpokwsths invented the technique and others just decreased the amount of reclaimed RAM.
The source is available, you could build your kernel with less RAM reclaiming and try to find the sweet spot for you.
Or if you are a hotshot try and build a kernel that gives back 900MB of RAM and keeps the video playback perfect.
Otherwise ... seal your lips and be more kind to the "developers".
@mods: This thread should be closed or at least moved to the appropriate section.
akash3656 said:
How did you come to a conclusion that they were lying? And some developers DID realise that video playback is also broken and even has that mentioned in their threads. Or indirectly mentioned that things may break by making different variants for different users.
And by the way if you want 100% stable and working phone, xda or any other place that encourages you to tweak your phone is a complete no-no for you.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Do you read? I said If they know what they're doing, still claim "just some rare app will not work" , that is a lie in every definition. Did you ever read a line of source of any kernel or rom? Please shut-up before you've finished reading.(thumb down)
double post
antypas said:
Most devs mention that this "hack" breaks "things".
The matter is how important to a certain user is the ability to play flawlessly every video available.
Most users aren't bothered at all...
"Bigmem" and "ASRAM" and bull****. They aren't anything special.
They do the same thing to a different amount. "Bigmem" reclaims more than "ASRAM" and "SuperRam" reclaims even more than "Bigmem".
Mpokwsths invented the technique and others just decreased the amount of reclaimed RAM.
The source is available, you could build your kernel with less RAM reclaiming and try to find the sweet spot for you.
Or if you are a hotshot try and build a kernel that gives back 900MB of RAM and keeps the video playback perfect.
Otherwise ... seal your lips and be more kind to the "developers".
@mods: This thread should be closed or at least moved to the appropriate section.
Click to expand...
Click to collapse
Thankyou, XDA need more retard like you two, rate the thread 1 star? I don't care, did you read? Did you know the 4.2.2 fix? I post this topic is for those who read those OP like great CM, say goodie, goodie, and backfire? Sorry, we don't cover that, or we won't get some "donate", wow, bravo.
The most interesting thing is someone who don't own the phone can "create" a kernel for it , and still some stupid stand in the defense line for them. I like it. It worth a watch.:laugh:
@mods
I am totally fine if you feel like you should close this thread, I feel sorry for those user who using kernel not function as they'd expected. I feel even sorry for those developers who follow these BigMEM, ASRAM commits, making kernel they believe their kernel breaks nothing or just something rare use( like 1080p).
randommmm said:
Thankyou, XDA need more retard like you two, rate the thread 1 star? I don't care, did you read? Did you know the 4.2.2 fix? I post this topic is for those who read those OP like great CM, say goodie, goodie, and backfire? Sorry, we don't cover that, or we won't get some "donate", wow, bravo.
The most interesting thing is someone who don't own the phone can "create" a kernel for it , and still some stupid stand in the defense line for them. I like it. It worth a watch.:laugh:
Click to expand...
Click to collapse
I did know about the 4.2.2 Ducati engine fix... It was posted a few days ago.
So that doesn't make me a retard after all???
You are not only ungrateful to the devs that do things for free but you are a ***** that calls names as well...
I suggest that devs make memory-reclaimed kernel versions optional, and the stable version should use the stock ROM allocation to avoid any function impairment.
Or the users that don't want the extra RAM can build whichever kernel they desire from source after changing the RAM reclaiming values...
Simple as that.
randommmm said:
Do you read? I said If they know what they're doing, still claim "just some rare app will not work" , that is a lie in every definition. Did you ever read a line of source of any kernel or rom? Please shut-up before you've finished reading.(thumb down)
Click to expand...
Click to collapse
Even if I have read, android is God knows how many million lines of code and thousands of commits. They (kernel developers) never mentioned some rare app, they say it as a general thing. And please, even if I do not read github like a story book, I read OP and try my best to follow threads. And clearly most if not all made variants without RAM hacks or made variants that worked with most things. If that weird app doesn't work, screw it flash a kernel that doesn't mod with RAM. Or go fastboot flash to stock 4.3.
As pointed by others, you could make your own ram hack that is *better* or appreciate their work and accept the fact Galaxy Nexus sucked from day 1 in terms of RAM.
Seriously, if you're gonna rant you're also at the wrong section of the forum too. Have you read xda rules?
Sent from my Galaxy Nexus using Tapatalk
I think kernel with 40MB RAM reclaimed is safe for most 720p video.
Kernel with ASRAM(50MB) cannot play 720p video that ref > 7 with HW nor HW+ decoder.
And with 40MB declaimed can up to ref = 9.
Sent from my Galaxy Nexus using xda premium
This whole thread is just a giant ragefest, honestly it should be removed. I don't feel OP is correct in outright calling people liars, it's just not the appropriate way to get a point across in an adult developer community. Just because one individual has an issue with a particular app or a certain function properly working does not mean others will guaranteed have this same issue. With android we all do different tweaks, use different apps, kernels roms etc. This means that just because the particular apps you choose to use are not working because of Bigmem, Superram ASram blah blah blah, it doesn't mean it's an epidemic on all of our devices.
I have had no issues using MX Player or Youtube on HQ video setting with Superram, I haven't had a single reboot, freeze, app fc or anything else do to the SuperRam kernel, I've been using it since it first was released on 4.3. I use my custom settings with it as well. I am not trying to bag on randommmm, what I am merely doing here is saying that no one is right or wrong and the developers are certainly not liars.
On my custom kernel thread I have a poll on which kernel people prefer the most, as of right now 49 out of 73 people on there are using MPOkang superram kernel, none of them are complaining about it causing all these issues.
The OP of the Kernel clearly states that 1080p video playback/recording will not work, that is the only thing that is guaranteed to not work for sure, if you need 1080p on your device then simply do not use the kernel, quite simple.
With any kernel there is a chance of issues, but guess what? With any kernel settings there is a chance of problems too, just because people have certain issues with SuperRam kernel flashed does not mean it's superram, not everyone knows what they are doing when adjusting the kernel settings. Not to mention not every rom, especially 4.4.x roms, are going to work perfect.
I read randommmm's post about this on whatever thread he posted about it on, I personally do not feel this subject warranted it's own thread.
randommmm, I am in no way saying you don't know what you are talking about but..... until you have developed a kernel yourself you really should not be namecalling people that have. If this were as extreme of an issue as you are making it out to be there would not be so many using SuperRam kernel without complaint and there certainly would not be the vast amount of other kernel developers adding free ram modifications to their own kernels.
I sincerely mean no offence to anyone on this thread. I've been following it for a bit now and felt it was time to put my opinion in.
That is all.
Neph