Database Develop

[Q] (Q) Galaxy S OC Kernel flash-ability

With Z4Mod's kernel module flashing ability is it possible to flash an already written Glaxay S variant OC module? I assume voltages and stable frequencies are identical.
I've never flashed a module using Z4Mod but I recently tackled Odin and I'm feeling adventurous
I'm willing to use my Galaxy Tab as the test bed so no one else has to worry about having an expensive paper weight for the holidays.
Thanks a million
-Landon

Simple advice: dont do it.
Never flash anything designed for another device. Yes, the GalaS and the Tab may be similar, but its where theyre not similar that make the big difference.
Sent from my GT-P1000 using XDA App

Thanks for the advice. Maybe I'll try a different route.Is the operating frequency contained in the build.prop? If I try tweeking the frequency w/o flashing a module I believe the worst I could do is freeze the device. Then a fix would be as easy as a reflash from a backup or use rotohammer's .tar.

halftonehero said:
Thanks for the advice. Maybe I'll try a different route.Is the operating frequency contained in the build.prop? If I try tweeking the frequency w/o flashing a module I believe the worst I could do is freeze the device. Then a fix would be as easy as a reflash from a backup or use rotohammer's .tar.
Click to expand...
Click to collapse
no the frequency and voltage settings are set in the kernel! you would need to recompile the kernel and then flash the new kernel from heimdall or odin!
i almost finished an overclock kernel but i dont want to flash it when im done because im afraid to brick the device and i have problems compiling it and i dont have so much time atm because i have to do tests at school so i need to learn! but i can give u the files u need to edit if u want so

Off topic, but I dig your handle. Mixes my name and Android I'll give it a shot. Send them my way and I'll see what I can do. I'll have to brush up on my Linux skills though. I used Ubuntu up until 10.04 when I switched to the (Bill Gates) dark side but I still have Karmic installed on my dual boot machine.

halftonehero said:
Off topic, but I dig your handle. Mixes my name and Android I'll give it a shot. Send them my way and I'll see what I can do. I'll have to brush up on my Linux skills though. I used Ubuntu up until 10.04 when I switched to the (Bill Gates) dark side but I still have Karmic installed on my dual boot machine.
Click to expand...
Click to collapse
so u need to mess around with the kernel source, i can upload it if u want so!
but if u already got 'em, u need to mess with these files:
GT-P1000_kernel.tar/Kernel/drivers/cpufreq/
there is the freq_table and the cpufreq.c and we need to find a way to edit them and speed up our hummingbirds! we should also take a look at the manhattan project! they managed it to overclock the galaxy s!

If you could, post the link for me. I'm at work now so there isn't much I can do but I'll definitely start tinkering when I get home.

Keep us posted! Been waiting for an overclocked kernel!
Sent from my GT-P1000 using Tapatalk

Landroid said:
so u need to mess around with the kernel source, i can upload it if u want so!
but if u already got 'em, u need to mess with these files:
GT-P1000_kernel.tar/Kernel/drivers/cpufreq/
there is the freq_table and the cpufreq.c and we need to find a way to edit them and speed up our hummingbirds! we should also take a look at the manhattan project! they managed it to overclock the galaxy s!
Click to expand...
Click to collapse
I compiled my own kernel...but wasn't brave enough to flash it onto my Tab

Yeah me too but i wonder if we can flash a working kernel ( if we bricked thetab) with heimdall

Landroid said:
Yeah me too but i wonder if we can flash a working kernel ( if we bricked thetab) with heimdall
Click to expand...
Click to collapse
It has an option to flash just zImage by itself. Failing that you could always just reflash the whole thing.

That was my assumption and why I'm not too scared to give this a shot.

Heimdall
I'm having trouble finding a dl for Heimdall. Anyone know of a good link? Odin is fine but I'd like to mess around with Heimdall, broaden my horizons. Most of my Android knowledge comes from HTC devices so this as much a learning experience as it is fun.
EDIT: Never mind. Found it.

Did you flash anything yet?
Sent from my GT-P1000 using Tapatalk

daniel.weck said:
I compiled my own kernel...but wasn't brave enough to flash it onto my Tab
Click to expand...
Click to collapse
Flashing a kernel is not hazardous. If it doest work properly then you just flash back a good one.
Now as for the bootloader, flashing that scares me!

ayman07 said:
Did you flash anything yet?
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Not yet. Work has been kicking my a$$. I haven't time to do laundry, let alone tinker with my tab. I have a rare day off today so I'll get to flashing.

halftonehero said:
Not yet. Work has been kicking my a$$. I haven't time to do laundry, let alone tinker with my tab. I have a rare day off today so I'll get to flashing.
Click to expand...
Click to collapse
That's understandable. If everything goes well then ill be next in line
Sent from my GT-P1000 using Tapatalk

[INT/Bell][CWM]Auto Ram Fixer for unlocked bootloader

Hi,
This is a small CWM zip to add the [email protected] line to your existing boot and recovery partitions to fix the ram issue with the international unlocked bootloader. If the second mem is already there it does nothing.
The point of this is you can have a regular recovery flashed and fix the ram issue without wondering what tegra part you have, it preserves your serial number as well. More useful with stock boot images than custom ones that already have this done.
To use:
Flash with a CWM recovery supporting edify scripting. That means you have an unlocked recovery basically.The program inside the zip can be used on it's own to list the cmdlines already in your phone, or to set them to something else.
As cmdline, it lists, as setcmdline it sets the entire thing, as addcmdline it adds on to the end of the existing cmdline.​Cheers!

Great! Looks like our bell friends are having good development as well.
Sent from my MB860 using XDA Premium App

NF, cheers bro I really appreciate the work from you.
Sent from my MB860 using XDA Premium App

So would i need to flash this once and then any ROM I install will have fixed RAM, or do I need to flash this after every installation?

IUH1991 said:
So would i need to flash this once and then any ROM I install will have fixed RAM, or do I need to flash this after every installation?
Click to expand...
Click to collapse
You can just keep it handy on your sdcard and use when needed, it depends on the "rom" you flash, it may or may not have a ram fix solution built in.
Cheers!

J-Roc said:
NF, cheers bro I really appreciate the work from you.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
You're welcome.
Cheers!

NFHimself said:
You can just keep it handy on your sdcard and use when needed, it depends on the "rom" you flash, it may or may not have a ram fix solution built in.
Cheers!
Click to expand...
Click to collapse
It depends on the Kernel the Rom has within it, nothing else.
Furthermore, no offense. But this is kinda useless now. Did you not know we have unified Kernel's? If someone made a Rom without a unified kernel, they can basically shove that Rom.
I do not see a point in this at all. I guess maybe for testing old Roms.....

NFHimself said:
You can just keep it handy on your sdcard and use when needed, it depends on the "rom" you flash, it may or may not have a ram fix solution built in.
Cheers!
Click to expand...
Click to collapse
So solid man, keep up the good work!

nexxusty said:
It depends on the Kernel the Rom has within it, nothing else.
Furthermore, no offense. But this is kinda useless now. Did you not know we have unified Kernel's? If someone made a Rom without a unified kernel, they can basically shove that Rom.
I do not see a point in this at all. I guess maybe for testing old Roms.....
Click to expand...
Click to collapse
Hi,
I addressed this already in the OP. It's more for use with stock kernels.
Can you compile the motorola kernel source (pick one) and get a binary exact match for the stock Bell kernel?
No offense to the guys working on kernel's here, but I am not really compelled by the added features/bug fixes, and am concerned more about stability, especially when the source seems to be ATT based. Which is fine if you are running an ATT framework "rom/theme" I guess, even better if you have an ATT phone.
Cheers!

NFHimself said:
Hi,
This is a small CWM zip to add the [email protected] line to your existing boot and recovery partitions to fix the ram issue with the international unlocked bootloader. If the second mem is already there it does nothing.
The point of this is you can have a regular recovery flashed and fix the ram issue without wondering what tegra part you have, it preserves your serial number as well. More useful with stock boot images than custom ones that already have this done.
To use:
Flash with a CWM recovery supporting edify scripting. That means you have an unlocked recovery basically.The program inside the zip can be used on it's own to list the cmdlines already in your phone, or to set them to something else.
As cmdline, it lists, as setcmdline it sets the entire thing, as addcmdline it adds on to the end of the existing cmdline.​Cheers!
Click to expand...
Click to collapse
Hi is this fix for when i flash IHOP and get ram problem it fix that or its universal for every kernel (Gb froyo ROMs etc) ?

so does this mean it is actually possible to download more ram??

xateeq said:
Hi is this fix for when i flash IHOP and get ram problem it fix that or its universal for every kernel (Gb froyo ROMs etc) ?
Click to expand...
Click to collapse
Yes, what you said.
Cheers!

geishroy said:
so does this mean it is actually possible to download more ram??
Click to expand...
Click to collapse
Uhm, what?
Cheers!

geishroy said:
so does this mean it is actually possible to download more ram??
Click to expand...
Click to collapse
Download more RAM? Umm...did you even read this before you posted it? or do you know absolutely nothing about what RAM is?

geishroy said:
so does this mean it is actually possible to download more ram??
Click to expand...
Click to collapse
So many people don't understand what Ram actually is *sigh*
You're not the first, I see it EVERYWHERE, google it up!

Thanks a lot, because i was having ram issue with eternity project kernel, and your patch solve it !
Sent from my MB860 using XDA App

dnsdenis said:
Thanks a lot, because i was having ram issue with eternity project kernel, and your patch solve it !
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Glad it worked out!
Cheers!

System Ram lists 816 total, so I should be in the clear or should I apply it anyways? Is there not a gig of ram on this thing or is some gpu/frame buffer dedicated?

drolgnir said:
System Ram lists 816 total, so I should be in the clear or should I apply it anyways? Is there not a gig of ram on this thing or is some gpu/frame buffer dedicated?
Click to expand...
Click to collapse
You are in the clear.
Cheers!

So, if I understand this correctly, when I flash this it will auto-fix any ROM, kernel or custom recovery that I install?

[Help][Port]CyanognMod 9 for SGA Gt-s5830i

Guys port the cyanogen mod 9 Galaxy Y.
Here's a link to a topic.

The original rom is REALLY BUGGY itself...How do you suppose a port will do anything good? A port will add even more bugs to the build.So much that it would become unusable.Not trying to discourage you or anything. Just stating ...
Insert witty sentence here

it would be safer it we tried to port CM9 ourself

shadowsiul said:
it would be safer it we tried to port CM9 ourself
Click to expand...
Click to collapse
I dont hink it wil b possible as cm7 is still miles away frm gettin onto our fones. GPU sources r also nt yet out(fu***** brodcom).

Theres a mini cm9 for the international gt s5830. And works really good. Almost no bugs as i installed it on my gf's ace
Maybe that one would be the right one to port.
Sent from my GT-I9100 using xda premium

sebarg said:
Theres a mini cm9 for the international gt s5830. And works really good. Almost no bugs as i installed it on my gf's ace
Maybe that one would be the right one to port.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
5830 hv different board. Even GPU.

sebarg said:
Theres a mini cm9 for the international gt s5830. And works really good. Almost no bugs as i installed it on my gf's ace
Maybe that one would be the right one to port.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
S5830I = Galaxy Young, but looks like Galaxy Ace S5830
S5830 =/= S5830I except for the look

at least it starts? what would need to change it to at least boot? I do not care problems, she boot is a start.

yoto111 said:
at least it starts? what would need to change it to at least boot? I do not care problems, she boot is a start.
Click to expand...
Click to collapse
I don't understand most of what devs do. I do understand some pieces of code, I know how to do some basic theming, and I can use search engines.
I also know that "she boot" is not a start. Why? Read post#2. It's written by a dev who actually knows more than your "at least it starts?" questions. We already have a CM7.2 that "she boot", but it's very buggy, and not for daily use. If you want it, and "do not care problems, she boot is a start", google it.
EDIT: Oh, forgot to mention why the "she boot" CM7.2 is full of bugs. It's ported from the Galaxy Y as well and even tho "at least it starts" the most crucial features don't work.

GermainZ said:
I don't understand most of what devs do. I do understand some pieces of code, I know how to do some basic theming, and I can use search engines.
I also know that "she boot" is not a start. Why? Read post#2. It's written by a dev who actually knows more than your "at least it starts?" questions. We already have a CM7.2 that "she boot", but it's very buggy, and not for daily use. If you want it, and "do not care problems, she boot is a start", google it.
EDIT: Oh, forgot to mention why the "she boot" CM7.2 is full of bugs. It's ported from the Galaxy Y as well and even tho "at least it starts" the most crucial features don't work.
Click to expand...
Click to collapse
oh I understand this is not exactly "a beginning" significant, but for me it is. I asked this question because I have not had time to test, but if any of you tested could say, so I asked the question. If at least boot, it means a lot to me, I'm already anxious for ace ics running on and can not wait for that to happen.
I understand little about ports, I read a lot but never tried that already do not use linux and do not have time for this, but sorry if you enterpretou bad what i said, it was not the intention.

yoto111 said:
oh I understand this is not exactly "a beginning" significant, but for me it is. I asked this question because I have not had time to test, but if any of you tested could say, so I asked the question. If at least boot, it means a lot to me, I'm already anxious for ace ics running on and can not wait for that to happen.
I understand little about ports, I read a lot but never tried that already do not use linux and do not have time for this, but sorry if you enterpretou bad what i said, it was not the intention.
Click to expand...
Click to collapse
CM7.2 exists and is bootable on the S5830I. Try it if you want. http://forum.xda-developers.com/showthread.php?t=1770498

GermainZ said:
CM7.2 exists and is bootable on the S5830I. Try it if you want. http://forum.xda-developers.com/showthread.php?t=1770498
Click to expand...
Click to collapse
so the cm7.2 came to our phone I installed it. I already know all the bugs, and also follow the topic seeing all fixes. But what i really hope is CM9, at least a version of it bootable.

yoto111 said:
so the cm7.2 came to our phone I installed it. I already know all the bugs, and also follow the topic seeing all fixes. But what i really hope is CM9, at least a version of it bootable.
Click to expand...
Click to collapse
The ROM in the OP will brick the S5830I if installed, so no one can test it unless it's ported, which is useless because:
1- It will even more buggy
2- CM9, even if ported correctly, will be extremely laggy, because the full GPU sources for the S5830I aren't available.
3- CM7 isn't ready yet. CM9 only requires more work.

Dude this is lyk imposible yet v dont have cm7,cm9 is far to go
N other thing is that this cm9 from wich ur portnng is itself bugly its useless to port a rom with bugs !!

rajrocks said:
Dude this is lyk imposible yet v dont have cm7,cm9 is far to go
N other thing is that this cm9 from wich ur portnng is itself bugly its useless to port a rom with bugs !!
Click to expand...
Click to collapse
that true but in theory could we use MaclawStudios/icsgalaxy source to build? i know that i am asking stupid question but i mean there are alot of these question out there.

shadowsiul said:
that true but in theory could we use MaclawStudios/icsgalaxy source to build? i know that i am asking stupid question but i mean there are alot of these question out there.
Click to expand...
Click to collapse
ever read about the differances between S5830 and S5830i ? well Original device have Adreno200 which it has source code released and S5830i have Videocore IV that is made by broadcom even tho broadcom agreed to share some of its device's source code they denied to release VC IV's code without HW Acceleration its an piece of crap with 1ghz(with rafael's latest kernel) cpu and 300mb ram even Galaxy Y is better than this device because there are some ports that already getting done its cheaper if we compare this device to that...

GermainZ said:
The ROM in the OP will brick the S5830I if installed, so no one can test it unless it's ported, which is useless because:
1- It will even more buggy
2- CM9, even if ported correctly, will be extremely laggy, because the full GPU sources for the S5830I aren't available.
3- CM7 isn't ready yet. CM9 only requires more work.
Click to expand...
Click to collapse
I have installed it with ClockworkMod Recovery V5.0.2.6 and it works fine, however, after booting it is stuck at "Updating Android - Starting apps".
But, IT WORKS !!!!!!

RubenStauttener said:
I have installed it with ClockworkMod Recovery V5.0.2.6 and it works fine, however, after booting it is stuck at "Updating Android - Starting apps".
But, IT WORKS !!!!!!
Click to expand...
Click to collapse
You installed an unported Galaxy Y ROM on your phone and it worked? That's dumb. And I'm surprised it booted.

GermainZ said:
You installed an unported Galaxy Y ROM on your phone and it worked? That's dumb. And I'm surprised it booted.
Click to expand...
Click to collapse
Yeah, me too, but actually it doesn't works, I only get/it's now stuck at an orange circle, witch can be moved with your finger like a laptop touchpad (after booting (without/no boot animation)).
Sent from my GT-S5830i using xda premium

RubenStauttener said:
Yeah, me too, but actually it doesn't works, I only get/it's now stuck at an orange circle, witch can be moved with your finger like a laptop touchpad (after booting (without/no boot animation)).
Sent from my GT-S5830i using xda premium
Click to expand...
Click to collapse
Cool. Have fun with your new "Move the orange circle!" game
By the way, you seriously shouldn't flash Galaxy Y ROMs. Your keys may end up not getting recognized (in other words: no recovery/download mode for you anymore).

solution to reduce the lag on your GT7.7

WARNING -- you may try this on Jelly bean only, as ICS and HC are not protected and might lead to BRICK bug
Hey All
I noticed that after we made a factory reset our device is extremely fluid fast and smooth
but after couple of days it starts to lag, and continue to lag more and more.
I found that the problem is Storage performance is decreasing overtime due to not wiping and trimming the blocks that we don't use.
This is a famous problem and discussed here: http://forum.xda-developers.com/showthread.php?t=1971852#fm
even google fixed it on Android 4.3
Just try this application and tell me, how did you find you device state now?
https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix&hl=en
and you can benchmark it before and after
Thanks all

WARNING -- BRICK-BUG
OP, for certain devices, the app developer has stated BrickBug means DEATH of your device if you try LagFix!
http://forum.xda-developers.com/showpost.php?p=37029420&postcount=122#fm
There maybe users with SGT 7.7 models still running stock HC/ICS kernel (edit: unpatched) and recovery, so potentially at risk.
Cheers,
UITA
Sent from my GT-I9500 using XDA Premium 4 mobile app

Anyone try this yet with the 7.7?

UpInTheAir said:
WARNING -- BRICK-BUG
OP, for certain devices, the app developer has stated BrickBug means DEATH of your device if you try LagFix!
http://forum.xda-developers.com/showpost.php?p=37029420&postcount=122#fm
There maybe users with SGT 7.7 models still running stock HC/ICS kernel (edit: unpatched) and recovery, so potentially at risk.
Cheers,
UITA
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm running Jelly bean now, I didn't faced any bricks
do you think it might happen for me too? should i remove the thread?
and why trimming an unused block in memory will lead to brick bug?

bassem.mohsen said:
I'm running Jelly bean now, I didn't faced any bricks
do you think it might happen for me too? should i remove the thread?
and why trimming an unused block in memory will lead to brick bug?
Click to expand...
Click to collapse
As far as I'm aware, JB is not faced with the brick bug. I was warning about previous Android versions. Have a read of the XDA thread I linked, can explain things better than I ever could.
No, I think this thread is ok, but maybe make reference to JB only in thread title etc and possible brick warning if used with other.
Edit: I see you put a warning in OP, thanks.
Sent from my GT-I9500 using XDA Premium 4 mobile app

bassem.mohsen said:
I'm running Jelly bean now, I didn't faced any bricks
do you think it might happen for me too? should i remove the thread?
and why trimming an unused block in memory will lead to brick bug?
Click to expand...
Click to collapse
I am using PA 3.68 on a P6800 - Laxfix will not run - states device not supported for /system /data /cache. this is to bad as looks like could be a helpful feature.thanks for sharing and hope it works for others. I go back to the referenced thread and see if I need to make some other adjustments.:fingers-crossed:

ColBill said:
I am using PA 3.68 on a P6800 - Laxfix will not run - states device not supported for /system /data /cache. this is to bad as looks like could be a helpful feature.thanks for sharing and hope it works for others. I go back to the referenced thread and see if I need to make some other adjustments.:fingers-crossed:
Click to expand...
Click to collapse
for real, and i tried it several time, it restores the speed of the device to the day i made factory reset.
it's not placebo and i benchmarked before and after, and the topic above also shows benchmarking.
and even reviews of Android 4.3 talks about trimming and how he removed sluggish from N7 first Generation.
Anyone with JB are welcome to try it.
I miss PA android BTW and the feel of nexus on my device
when Android 4.3 based ROMS are out, I will flash it.

Does not work. Do we have to be rooted?

vbx said:
Does not work. Do we have to be rooted?
Click to expand...
Click to collapse
yes, the application access the system, data, cache partitions to tell the memory that this block is empty now, don't exert effort in maintaining it.
so you to be rooted yes, and on JB for Safety.

Doesn't work
Im on stock ICS 4.0.4 XXLQ2, rooted, with custom EZYKernel XXLQ1, no brick bug.
LagFix doesn't work because
fstrim: FSTRIM: Operation not supported on transport endpoint
I tried it with /system /data and /cache with no luck.

Sirius-3R said:
Im on stock ICS 4.0.4 XXLQ2, rooted, with custom EZYKernel XXLQ1, no brick bug.
LagFix doesn't work because
fstrim: FSTRIM: Operation not supported on transport endpoint
I tried it with /system /data and /cache with no luck.
Click to expand...
Click to collapse
My friend, you have "b**ls of steel" (if you're a guy). I'm not entirely sure his kernel is entirely safe. In addition to removing the "mmc cap erase", there needs to have a patch applied as well.
https://github.com/UpInTheAir/P681...mit/dfc97a2ed8c9f6b886de1cced2e35a2fd1cdeb91
https://github.com/UpInTheAir/P681...mit/f9d69ae2246571f4cd80337711953acab2d63092
From what I remember,... the brick bug known to occur with unpatched kernel and stock recovery with HC or ICS firmware.
Even with my patched kernel, not sure exactly if it'll be 100% OK....
Edit: just worked up the courage to test with my "protected" SkyHigh kernel v2.9.1, and as thought, app does not work
Sent from my GT-I9500 using XDA Premium 4 mobile app

works good for erobot..
ive been on 2.3 with multiwindow mod and for some reason its been laggy lately.This app works good and faster now.was going to flash back to stock JB kernal again but now looks like this has fixed it..

UpInTheAir said:
My friend, you have "b**ls of steel" (if you're a guy). I'm not entirely sure his kernel is entirely safe. In addition to removing the "mmc cap erase", there needs to have a patch applied as well.
https://github.com/UpInTheAir/P681...mit/dfc97a2ed8c9f6b886de1cced2e35a2fd1cdeb91
https://github.com/UpInTheAir/P681...mit/f9d69ae2246571f4cd80337711953acab2d63092
From what I remember,... the brick bug known to occur with unpatched kernel and stock recovery with HC or ICS firmware.
Even with my patched kernel, not sure exactly if it'll be 100% OK....
Edit: just worked up the courage to test with my "protected" SkyHigh kernel v2.9.1, and as thought, app does not work
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I am male with b**ls of steel and i raped my P6800 many times. I know what I am doing and i'm familiar with my hard and software.
If your Kernel is avaliable with 3G Support, I'll give it a try. My P6800 is my every day Phone/Multimedia device and act also as a laptop replacement, with native Debian on it.
If I wreck it, it was my failure and I didn't cry for my mom
I must say, I tried your app for fun because I don't have any lags on my device. I have no need for "Project Butter", I use ADW Launcher ex, 268 Apps for IT Administration, Produktivity, Games, Multimedia. If I feel an app opens slowly it's time for "fschk" the Partitions. After that everything works fast and smooth as before.
Sent from my Slider SL101 using xda app-developers app

Arobase40 said:
Have you ever been touched by the "brickbug" with stock recovery or kernel/ROM from Samsung with your P6810 ???
Click to expand...
Click to collapse
Not this again..... :beer:
BTW: I've never actually factory reset etc using the stock recovery, and suppose never going to get the chance .The app developer also made reference to various bricks using his app caused by brick-bug affected devices.
Samsung themselves have signed off the patch (amongst others), so good enough for me. Just a shame that I don't have the option of using this app (safely) unless I use daniels custom JB ROM.
Sent from my GT-I9500 using XDA Premium 4 mobile app

I've had this program on my P6800 for some time now. It has been a blessing, and even upgraded to the Pro version.
It certainly feels snappy like Jelly Bean was just installed. I've set it to do a trim once a week.
Using JB 4.1.2

Sirius-3R said:
Yes I am male with b**ls of steel and i raped my P6800 many times. I know what I am doing and i'm familiar with my hard and software.
If your Kernel is avaliable with 3G Support, I'll give it a try. My P6800 is my every day Phone/Multimedia device and act also as a laptop replacement, with native Debian on it.
If I wreck it, it was my failure and I didn't cry for my mom
I must say, I tried your app for fun because I don't have any lags on my device. I have no need for "Project Butter", I use ADW Launcher ex, 268 Apps for IT Administration, Produktivity, Games, Multimedia. If I feel an app opens slowly it's time for "fschk" the Partitions. After that everything works fast and smooth as before.
Sent from my Slider SL101 using xda app-developers app
Click to expand...
Click to collapse
OT:
How are you running native Debian on P6800? Could you post a simple guide how to do it?

coltsmild said:
I've had this program on my P6800 for some time now. It has been a blessing, and even upgraded to the Pro version.
It certainly feels snappy like Jelly Bean was just installed. I've set it to do a trim once a week.
Using JB 4.1.2
Click to expand...
Click to collapse
Android 4.3 do it everyday with the following event:
device is left without activity for one hour
device is charged within 30 - 80 perecent
24 hour from last trim have passed.

its safe if i use this on ur kernel UITA? v 3.3.0 JB

B4R7H said:
its safe if i use this on ur kernel UITA? v 3.3.0 JB
Click to expand...
Click to collapse
SkyHigh kernel for P6800 is built from official JB MD3 source, and because i don't have JB, I can only assume that it is OK and chips aren't affected.
There is a app by dev Chainfire to test and be sure.
[05.09.2012] Got Brickbug ? v1.2
http://forum.xda-developers.com/showthread.php?t=1693704
Sent from my GT-P6810 using xda premium

Arobase40 said:
Tell me if I'm wrong but I think B4R7H's real question was : can he use lagfix (fstrim) with your Skyhigh new kernel version ???
Click to expand...
Click to collapse
Please read my reply more carefully....
But you forgot the most important thing he was asking (or wanting to know), can he use it SAFELY ?
I said "'..... I assume that is it OK".....
Sent from my GT-P6810 using xda premium

[ROM/MOD][WIP]CM for locked BL

Hello guys
First, big fat disclamier:
THIS IS NOT WORKING. Please don't try this for fun, only if you're willing to put in some time to help me get this fixed.
@djolivier and @letama worked out a way to get CM10 running on Xperia S with locked bootloader, loosely based on the work @atis112 did for Xperia U.
For the past couple of days I've been trying to port it to our beloved T.
It does sort of boot but there is nothing on screen. Logcat is working however and so is adb shell (though no su) so we have some way of debugging.
At the moment there is a working recovery (CWM 6.0.4.6 for locked BL by @davidmarco), enter it by pressing vol+ when the led is blue (it will turn green, then red). Here you will have an su shell and you can get dmesg and /proc/last_kmsg.
Please read the thread by djolivier to get an idea of how it works. In the last couple of pages you will find everything I have tried so far and some insightful answers from letama.
So the main thing now is to hunt down which are the libs/drivers we need.
I will try to get some more info into this thread asap but first I wanted to get it up so those of you who think they can help can get going.
Download
cm10_lb_mint_b12.zip - 188.72 MB
This includes the .489 stock kernel, which is probably the best for compatibility.
XDA:DevDB Information
CyanogenMod for Locked Bootloader, a ROM for the Sony Xperia T
Contributors
TiMiN8R, letama, djolivier
ROM OS Version: 4.1.x Jelly Bean
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2014-01-08
Last Updated 2014-01-08

Reserved

I think someone starting this off is a great idea, when i have some free time i'll try to offer you some help mate.
But need to get up to speed with it all from djolivier's thread before anything else. But i'm happy to offer some help when i can, if that be testing, or general de-bugging.

This is awesome.keep up Timn8r
Sent from my LT30p using XDA Premium 4 mobile app

How about asking letama for help? He was the one getting this to work on Xperia S..
By the way, really appreciate you doing this.. Was already waiting for someone to try this on our devices!
When it boots up I will try to flash the 30p to 25i patch and see if it works!
Sent from my LT25i using xda app-developers app

WhiteNeo said:
How about asking letama for help? He was the one getting this to work on Xperia S..
By the way, really appreciate you doing this.. Was already waiting for someone to try this on our devices!
When it boots up I will try to flash the 30p to 25i patch and see if it works!
Sent from my LT25i using xda app-developers app
Click to expand...
Click to collapse
Letama already helped me a lot over in the other thread, getting it up to this point. But now we need to find some very device specific stuff, that's best left to the people who actually have the device to test and debug. My time is limited this week and I don't have a need for this since mine is unlocked, it's just for the sport, so I figured, let's get some other people in on the action
Sent from my Xperia T using XDA Premium 4 mobile app

now im not too sure of this so i maybe completely wrong so please correct me if i am but im sure i read somewhere that the CM kernel drivers and STOCK kernel drivers differ in some way or another ..... again i repeat im not certain on this but if this is the case then certain things in the rom may need redirecting to the STOCK drivers rather than CM drivers as they done exist? ..... if i am right i wouldn't have a clue where to start to be honest but obviously you cant change the drivers in the kernel because then it wouldn't work on LB ..... perhaps ask rimmer for some help or advice as he ported MIUI to stock?

oddeceed said:
now im not too sure of this so i maybe completely wrong so please correct me if i am but im sure i read somewhere that the CM kernel drivers and STOCK kernel drivers differ in some way or another ..... again i repeat im not certain on this but if this is the case then certain things in the rom may need redirecting to the STOCK drivers rather than CM drivers as they done exist? ..... if i am right i wouldn't have a clue where to start to be honest but obviously you cant change the drivers in the kernel because then it wouldn't work on LB ..... perhaps ask rimmer for some help or advice as he ported MIUI to stock?
Click to expand...
Click to collapse
Yes that's just about right. We cannot change the drivers in the kernel but what we can do, and what I've been trying to do, is trying to match the drivers in the rom with the kernel, i.e. swapping out CM drivers for drivers from the stock .489 firmware. But there are quite a lot, that's why we need more people trying, testing, debugging. We could go another way, namely build new CM from source to match the kernel but that's beyond me I'm afraid.
letama said:
There is no easy way to solve that I'm afraid. You can try to play with dlls (check this for a list), but it has big chances to fail. The proper way to do that is to get fxp repo, patch hal to match stock kernel and recompile cm.
Click to expand...
Click to collapse
If @Rimmer1966 wants to help he is welcome of course.

TiMiN8R said:
... there are quite a lot, that's why we need more people trying, testing, debugging. We could go another way, namely build new CM from source to match the kernel but that's beyond me I'm afraid.
Click to expand...
Click to collapse
i know less than you and stuck on windows 8.1 which makes it even harder for me to do anything to help .... i hope that this can get up and running ..... providing you can get screen and touch working its more than enough proof of concept of what can be achieved and if enough different devices get going this way then maybe just maybe teams like CM will revert back from thier custom kernel (which i dont like) and start using stock kernels in builds (we can all dream right?)

Any updates on this? I can help as a beta tester or help with building on my pc.

masterjet said:
Any updates on this? I can help as a beta tester or help with building on my pc.
Click to expand...
Click to collapse
Not much going on on my end. I've been running on the leaked stock 4.3 for the last few days. I did have a little go on using the kernel from that rom to boot CM10.2 but I've not made much progress, seems that SELinux is throwing a spanner in the works.
If anyone wants to have a go, here's what you can do. Get the stock .489 here.
We should try swapping out .so in /system/lib/hw one at a time. You can do this by booting to CWM, mount /system and adb push, chmod 0644 the file and reboot. Get a logcat, reboot to CWM and get dmesg and last_kmsg
Code:
adb logcat > logcat
adb shell cat /proc/last_kmsg > last_kmsg
adb shell dmesg > dmesg
Lather, rinse, repeat. It is a slow and tedious process, so the more the merrier
TiMiN8R said:
I replaced hwcomposer.msm8960.so, that seems yo have fixed it. Also tried a couple of others that didn't work: gralloc.msm8960.so (can't start), copybit.msm8960.so (brought back the camera probs). Still no screen.
Most prominent spam now is
Code:
smd_pkt_open: DATA5_CNTL open failed -19
I also noticed this in logcat
Code:
I/clearpad_fwloader( 681): hanlde_arg: option = [default]
I/clearpad_fwloader( 681): hanlde_arg: saved.module_id = [0x32]
E/clearpad_fwloader( 681): read_sysfs: Unable to open /sys/devices/virtual/input/mice/name
E/clearpad_fwloader( 681): read_sysfs: Unable to open fwfamily
That is the touchscreen. There is indeed no /sys/devices/virtual/input/mice/name. I'm not sure if it is related to the no video issue but it's a problem nonetheless.
Click to expand...
Click to collapse

Thread is dead? No updates, no progress?

masterjet said:
Thread is dead? No updates, no progress?
Click to expand...
Click to collapse
Seems a bit of a dead end. Our stock kernel just seems to be to different from the stock kernel.
No-one else seems to want to pitch in and try some stuff out.
Might have another go with 4.3 when the official Sony's finally out.

it might be a stupid idea but why dont we swap out every .so file from the miui rom witch works with the stock kernel?

like i mentioned before
Why don't we try to do what they did with the moto defy/bravo and run a 2nd init. http://www.google.com/url?sa=t&sour...9ICIDA&usg=AFQjCNHMzrlHTlHC4EjfkhTkZxavJbEJow

lordyka said:
it might be a stupid idea but why dont we swap out every .so file from the miui rom witch works with the stock kernel?
Click to expand...
Click to collapse
If you had read the other thread, you would have known that I've already tried a lot of .so's from stock firmware but nog all of them work. This is the hard part, finding the ones that work.
jewkhok said:
Why don't we try to do what they did with the moto defy/bravo and run a 2nd init. http://www.google.com/url?sa=t&sour...9ICIDA&usg=AFQjCNHMzrlHTlHC4EjfkhTkZxavJbEJow
Click to expand...
Click to collapse
Well the first part, the hijacking, is exactly what does mod is doing. With regards to the 2nd-init program, I'm not sure that init itself is the problem. The "only" problem we have is finding drivers/libs that are compatible with both CM and stock kernel. But I could be off though. If someone wants to build us a 2nd-init go right ahead

Wow just came back to the T forums to see how things were going and I see this! Hopefully Tim can port it I'm sure he can
Sent from my XT1058 using Tapatalk

I honestly don't think 2nd init would make a big difference, as TiMiN8R has already stated, the problems are the drivers. You can now either ask FXP to use drivers from the Sony 4.3 Stock kernel or do it yourself...
Good luck on this, you'll surely make it.
Gesendet von meinem Xperia S mit Tapatalk

got the source codes?
I'm thinking about doing the same with Z1, wouldn't mind take a look at your work

If you asked me: here are the sources.
Gesendet von meinem Xperia S mit Tapatalk