• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Over Clocking Kernel for SPH-M930BST

johnny424 said:
never thought the day would come that the screen issue would be fixed..truly a beautiful thing..cant stop draging icons around the screen..thanks for all your hard work Bob
Click to expand...

Stop teasing me lmao still dont have my phone back yet. Cant wait to flash this new kernel when i get it next week.
 
chevanlol360 said:
Stop teasing me lmao still dont have my phone back yet. Cant wait to flash this new kernel when i get it next week.
Click to expand...

Omfg you don't even know! YOU DON'T EVEN KNOW!!! Thank you thank you thank you bob! And props to samsung for listening to us even if it took awhile... (it is their fix right?) I finally have the phone I paid for!

Ps thanks to andy and chev for facilitating this fix! :D
 
Loota said:
Omfg you don't even know! YOU DON'T EVEN KNOW!!! Thank you thank you thank you bob! And props to samsung for listening to us even if it took awhile... (it is their fix right?) I finally have the phone I paid for!

Ps thanks to andy and chev for facilitating this fix! :D
Click to expand...

lol its deffinetly weird..my wife is using my TU right now because i had to take her prevail to finish CM9..once i flashed Bobs new kernel and work i was really regreting letting the wife borrow my TU :D
 
This: SAMSUNG
says that the Transform Ultra has an INAND chip in it which i think presents itself to the linux kernel as an MMC block device. This suggests that UBIFS will not be possible on the TU. I have researched this and this seems to be the conclusion I have come up with given that UBIFS uses raw flash and can not be attached to block devices. Can anyone verify this?
 
bads3ctor said:
This: SAMSUNG
says that the Transform Ultra has an INAND chip in it which i think presents itself to the linux kernel as an MMC block device. This suggests that UBIFS will not be possible on the TU. I have researched this and this seems to be the conclusion I have come up with given that UBIFS uses raw flash and can not be attached to block devices. Can anyone verify this?
Click to expand...

Can't confirm but i looked at the samsung link, I thought the Ultra only had 370 MB of RAM???? why does it it say 512 on the link?
 
chevanlol360 said:
Can't confirm but i looked at the samsung link, I thought the Ultra only had 370 MB of RAM???? why does it it say 512 on the link?
Click to expand...
Yes..the TU has 512mb ram but I read someplace that part of it is used by something else...but I forget what.

# free -m
total used free shared buffers
Mem: 370 256 113 0 9

dmesg:
[ 0.000000] Memory: 58MB 134MB 256MB = 448MB total
[ 0.000000] Memory: 378168k/378168k available, 80584k reserved, 0K highmem

Maybe the GPU uses the rest. Just a guess.
 
i was wondering i did went and updated to $hEvRoN 5.3.0 then afterward put the overclocking kernel. once it finished i restarted my phone my phone vibrated on boot. Then i got a crash message saying application android system(process system) has stopped. Is there any way to fix it?
 
ak47bluntz said:
i was wondering i did went and updated to $hEvRoN 5.3.0 then afterward put the overclocking kernel. once it finished i restarted my phone my phone vibrated on boot. Then i got a crash message saying application android system(process system) has stopped. Is there any way to fix it?
Click to expand...

I got that at first too, I rebooted and it seemed to go away.

Edit: problem has reoccured for me, I won't say this is the only way to make it occur but I can trigger the bug consistently by going to home screen and opening stockk phone or contacts the included paste bin is from logthis with the process system tag...

http://pastebin.com/zR6Btt1p

This is on a non overclocked phone running shevron rom 5.3.0
 
Loota said:
I got that at first too, I rebooted and it seemed to go away.

Edit: problem has reoccured for me, I won't say this is the only way to make it occur but I can trigger the bug consistently by going to home screen and opening stockk phone or contacts the included paste bin is from logthis with the process system tag...

process system bobzhome kernel 2.3.6 - Pastebin.com

This is on a non overclocked phone running shevron rom 5.3.0
Click to expand...

im getting the same crash on 5.30 also, no wiping cache, dalvik or fixing permissions fixes it either. i have never once been able to run this rom without irreparable crash messages on startup - even if it works fine to start with, eventually, as i restore my apps, even if im really careful and just restore one or two at the time, i eventually start getting the crash message, and it can never be fixed, so i loop back, and start trying over again .

the stock rom with bobs overclocking kernel doesnt give me errors of any kind, just for note.

anyway, all these guys put in a ton of hard work to bring us these roms, and i would like to thank them all for their hard work, and for giving me somethin new to learn :D
 
is this OC reversible?

meaning if i make a back now before using this kernel.....will i be able to completely revert everything back (including kernel)?

thanks in advance
 
janathan said:
is this OC reversible?

meaning if i make a back now before using this kernel.....will i be able to completely revert everything back (including kernel)?

thanks in advance
Click to expand...

Or you can use odin... or ask someone for stock boot.img

But like you annd Chev said... make a backup first... its the easiest way to go
 
Loota said:
I got that at first too, I rebooted and it seemed to go away.

Edit: problem has reoccured for me, I won't say this is the only way to make it occur but I can trigger the bug consistently by going to home screen and opening stockk phone or contacts the included paste bin is from logthis with the process system tag...

process system bobzhome kernel 2.3.6 - Pastebin.com

This is on a non overclocked phone running shevron rom 5.3.0
Click to expand...

By looking at the pastebin link i would say the FC is caused by the system looking for carrier iq but can't find it. Once samsung releases 2.3.6 where there is no carrier iq in the system apps and frameworks you will no longer have this FC.
 
I thought I flashed version 2.2 of this kernel, but it is showing up as 2.1. Is it just me???
614b84f5-8e1e-e4f8.jpg
 
I also noticed the same thing says im running version 2.1, however i'm not having any problems with the touch screen or the wifi so who knows....
 
2.1 is a build number in a kernel config file that Bob just forgot to change when he made his new 2.2 kernel. I sent him a pm about it a week ago but he is probably too busy with real life to fix it right now.
 
bads3ctor said:
2.1 is a build number in a kernel config file that Bob just forgot to change when he made his new 2.2 kernel. I sent him a pm about it a week ago but he is probably too busy with real life to fix it right now.
Click to expand...

REAL LIFE???? Are you telling me that you guys aren't all volunteers?? You actually have lives outside of this forum??? You aren't waiting for our next complaint about a fc or bug fix??? HOW ABSURD!!! :mad::mad:

Edit: In case people can't recognize sarcasm...that was supposed to be humorous. You guys are doing a great job. :thumbup:
 
You must log in or register to reply here.
Back
Top Bottom