Jump to content

[KERNEL] [Y300/G510] Stock Huawei


Guest

Recommended Posts

Guest Romagnolo1973

cexstel kernel pass from 393 mb to 407 mb free I suppose ram reducing MDP value, because with cexstel 407mb installed Video reproducing was problematic but only for youtube HQ and movie HQ if I remeber well.

If you need some testing reducing ADSP value I can help, I use FM Radio and music player some hours a day so I can catch issue in this area

Link to comment
Share on other sites

Guest fonz93

The MDP (maybe ADSP too?) related thing is one of the things I and H3ROS were talking about here: http://www.modaco.com/topic/372447-kernel-y300g510-stock-huawei/?p=2219769

 

I think is already the minimum value available as there arleady are problems in streaming video with Twitch app (and maybe other apps that use an high quality video), that's why we suggested to increase a little his dedicated RAM

Edited by fonz93
Link to comment
Share on other sites

I've compiled a kernel build with 35 MB MDP_size and it still didn't seem to help. We currently got 28 MB reserved for MDP. CodeAurora's (Qualcomms?) default value is: 27 MB after this commit: https://www.codeaurora.org/cgit/quic/la/kernel/msm/commit/arch/arm/mach-msm/board-msm7x27a.c?h=msm-3.4&id=2655b11a23892f7c9b4c05bd21c0eea969816088

 

The best solution would be, if this cache(s) wouldn't be allocated statically, but instead being available to user-space when not fully in use. I've clue if this is even possible and in case it should: I wouldn't know how to do it, yet.

Link to comment
Share on other sites

Guest atlas.

hi i have problem with wifi sometime when i connected wifi sometime wifi break and lost connection

this wifi spot i use only one. i dont know why thank you

Link to comment
Share on other sites

Guest juanpablocastillo

I've compiled a kernel build with 35 MB MDP_size and it still didn't seem to help. We currently got 28 MB reserved for MDP. CodeAurora's (Qualcomms?) default value is: 27 MB after this commit: https://www.codeaurora.org/cgit/quic/la/kernel/msm/commit/arch/arm/mach-msm/board-msm7x27a.c?h=msm-3.4&id=2655b11a23892f7c9b4c05bd21c0eea969816088

The best solution would be, if this cache(s) wouldn't be allocated statically, but instead being available to user-space when not fully in use. I've clue if this is even possible and in case it should: I wouldn't know how to do it, yet.

Correct me if I'm wrong, but isn't that implemented in K^Kernel by Christopher83? Edited by juanpablocastillo
Link to comment
Share on other sites

In his kernel he add the CMA API to the PMEM allocator.

Since PMEM was never really working like it was supposed to, I simply removed it instead attempting to fix it.

To be honest: I didn't get Christopher's idea so far making use of PMEM+ION at the same time. There are commits on CodeAurora for CMA as well.

Edited by Guest
Link to comment
Share on other sites

Guest juanpablocastillo

I don't reffered to that. PMEM is obsolete. I reffered to the CMA API introduced in ION memory allocator.

Edited by juanpablocastillo
Link to comment
Share on other sites

Guest juanpablocastillo

To be honest: I didn't get Christopher's idea so far making use of PMEM+ION at the same time.

It's because the camera of the S Plus doesn't have native ION drivers, only have the PMEM drivers.

Edited by juanpablocastillo
Link to comment
Share on other sites

Example:
 

# Initialize /dev/block/zram0 with 50MB disksize
echo $((50*1024*1024)) > /sys/block/zram0/disksize

OR:

# Using mem suffixes
echo 256K > /sys/block/zram0/disksize
echo 512M > /sys/block/zram0/disksize
echo 1G > /sys/block/zram0/disksize

 
Activate:

  • mkswap /dev/block/zram0
  • swapon /dev/block/zram0

 

 

You can also browse the PlayStore for an appropiate APP, like this one for example: https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod

Edited by Guest
Link to comment
Share on other sites

Guest squal

@modding33k tnxs for the reply:)

what percent do you preferred in zram??

edit: in the trickrersmod , the zram is only 10% ...

Edited by squal
Link to comment
Share on other sites

Guest juanpablocastillo

It shouldn't be more than 10% of total RAM available in general. For our device I wouldn't recommend more than 50 - 75 MB totally.

Link to comment
Share on other sites

Guest thetonyxx

Did anyone test the undervolting?

I, with kernel ceastel several months ago, but I accidentally turned down too much voltage and performance were too compromised so I had to reflash the rom 
the downvolt so it works but you can not know the voltage, try steps of 0.05 volts until it reduces performance in benchmarks
Link to comment
Share on other sites

Current build: http://www53.zippyshare.com/v/58762926/file.html --> http://www.modaco.com/topic/372447-kernel-y300g510-stock-huawei/#entry2221058

Sry. I'm too lazy to write a changelog at the moment. It would be a technically one only anyway biggrin.png

In short:
- tryed to improve hotplug a little
- updated DMA-mapping APIs
- updated cache flush code
- minor freezer fixes/updates
- updated lockdep, lglock APIs
- …

Edited by Guest
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.