Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,739,676 Members 51,365 Now Online
XDA Developers Android and Mobile Development Forum
View Poll Results: Did the 270 MHz frequency step increase your battery life ?
Yes 37 34.91%
No 9 8.49%
I don't know 36 33.96%
I don't use this step 24 22.64%
Voters: 106. You may not vote on this poll

[KERNEL][Sony JB 4.3][20.07.14] Williams kernel v5.1

Tip us?
 
Vivaz90197
Old
#241  
Vivaz90197's Avatar
Senior Member
Thanks Meter 16
Posts: 105
Join Date: May 2014
Location: Warsaw
Quote:
Originally Posted by noahvt View Post
Maybe your battery is dead

Sent from my C5303 using XDA Free mobile app
Why fastboot/flashtool not work? This is not battery.
The Following User Says Thank You to Vivaz90197 For This Useful Post: [ Click to Expand ]
 
pec0ra
Old
#242  
pec0ra's Avatar
Senior Member - OP
Thanks Meter 373
Posts: 456
Join Date: Jan 2012

 
DONATE TO ME
Quote:
Originally Posted by noahvt View Post
Maybe your battery is dead

Sent from my C5303 using XDA Free mobile app
Quote:
Originally Posted by Vivaz90197 View Post
Why fastboot/flashtool not work? This is not battery.
He might be right. I once had an empty battery without offline charging mode (you also don't have one now because you have kernel problems) and I think it looked like this.
Try to let it charge on the red led (preferably on wall charger) until it disappears. Take a look in other thread too. I remember explaining how to recover in another thread, probably the cm11 one.
 
DjowBr
Old
(Last edited by DjowBr; 21st July 2014 at 06:50 PM.)
#243  
DjowBr's Avatar
Senior Member
Thanks Meter 37
Posts: 221
Join Date: Dec 2010
Location: Santos, São Paulo
Quote:
Originally Posted by Vivaz90197 View Post
Why fastboot/flashtool not work? This is not battery.
Conect it to PC and will show red led... This means your phone is charging the critical level of battery.. Try to conect it using the flash mode in PC companion or flashtool and flash a stock kernel.. When the led turn off your phone will conect and try to flash in flash mode.

When this occoured to me.. I conected in fast boot mode... When the led turned of i flashed the doom kernel e did a little charge on recovery, after 15 minutes i did a clean install and done.. My phone back working

Ensure to keep the vol button pressed until the red led turn off and got in the fastboot or flashmode

Another tip is.. Try to put in fast boot but instead of using the flash comand use boot.. It will boot the device in new kernel without flashing and removing the cable, keep pressing the vol button and it will load the recovery and let it charge some minutes

Sent from my Xperia SP using XDA Free mobile app
Sony Ericsson W580i > Sony Ericsson Xperia X10 mini > Sony Ericsson Xperia Neo > Sony Xperia SP
 
ApolloLive
Old
#244  
Junior Member
Thanks Meter 0
Posts: 12
Join Date: May 2013
Default v5.1 KernelWilliams

I have a question for all whether this kernel can be easily fitted to the SP because of what I see is an attempt after installation of other users: (
 
noahvt
Old
#245  
noahvt's Avatar
Senior Member
Thanks Meter 294
Posts: 1,074
Join Date: Jan 2013
Quote:
Originally Posted by Vivaz90197 View Post
Why fastboot/flashtool not work? This is not battery.
If your battery is completely dead it's obviously not going to do anything and even if you plug it into a pc it would take a while before it starts doing anything because of the slow charging that a PC offers! Plug it into the mains and leave it there for a day or so

Sent from my C5303 using XDA Free mobile app
MY DEVICES:

XPERIA SP (C5303)
-CPU: 1.7ghz(DUAL) QUALCOMM SNAPDRAGON S4 PRO
-RAM: 1GB
-BOARD: MSM8960T
-GPU: Adreno 320
-ROM: [KK 4.4.3] OFFICIAL CM11 Nightly
-KERNEL: [CM11]Williams kernel V2


Asus Transformer tf300t (CARDHU)
-CPU: 1.8GHz( QUAD, OC ) TEGRA3 T30L
-RAM: 1GB
-BOARD: Cardhu
-GPU: TEGRA3
-ROM: MULTIBOOT: Xubuntu, ubuntu touch, cm11, Cromi-X, omni, Dirty Unicorns
 
francescohtc
Old
#246  
francescohtc's Avatar
Senior Member
Thanks Meter 73
Posts: 330
Join Date: Nov 2008
i flashed in stock rom and i'm experiencing bootloop...
had to revert to stock kernel...

Don't flash guys...
Device:
  • Sony Xperia SP

Owned Phones: HTC Touch Find, Iphone 3G, LG Optimus 7, Samsung Galaxy S, Samsung Galaxy S Plus, Sony Xperia V, Sony Xperia SP.
Owned Tablets: Galaxy Tab 1, iPad, Galaxy Tab 2 10.1
The Following User Says Thank You to francescohtc For This Useful Post: [ Click to Expand ]
 
jahanzaib khan
Old
(Last edited by jahanzaib khan; 26th July 2014 at 02:44 PM.) Reason: forgot something
#247  
jahanzaib khan's Avatar
Junior Member
Thanks Meter 0
Posts: 19
Join Date: Sep 2013
Location: Lahore
Lightbulb For those who are experiencing blackscreens and reboots

For those who are experiencing black screens and reboots ask the dev to Please Disable OVERCLOCKING and all these things will be fixed. Please it's a request, try it. I told doomlord which helped doomlord in this regard too. Look at his changelog.
 
ironshadow2
Old
#248  
Senior Member
Thanks Meter 19
Posts: 221
Join Date: May 2014
hey man, I tried version 5.1 but didnt work (bootloop) can u help me?
 
prabhav.3892
Old
#249  
Member
Thanks Meter 4
Posts: 50
Join Date: Sep 2012
Location: Jaipur
Can you please release updated and fixed kernel.
With DOOMKERNEL on hold this could be the only lifeline for the stock users.
 
pec0ra
Old
#250  
pec0ra's Avatar
Senior Member - OP
Thanks Meter 373
Posts: 456
Join Date: Jan 2012

 
DONATE TO ME
Quote:
Originally Posted by ironshadow2 View Post
hey man, I tried version 5.1 but didnt work (bootloop) can u help me?
Just fastboot flash another kernel and you are done. If you can't go to fastboot just plug your device into computer, press volume key and press hard reboot button without releasing the volume button until you are in fastboot mode.

Quote:
Originally Posted by jahanzaib khan View Post
For those who are experiencing black screens and reboots ask the dev to Please Disable OVERCLOCKING and all these things will be fixed. Please it's a request, try it. I told doomlord which helped doomlord in this regard too. Look at his changelog.
Quote:
Originally Posted by prabhav.3892 View Post
Can you please release updated and fixed kernel.
With DOOMKERNEL on hold this could be the only lifeline for the stock users.
I'm sorry but this kernel is also on hold because of my revisions. As jahanzaib said, overclock (or maybe mpdecision) is causing reboots to some devices. At the end of august I'll make some test and try to find where the problem comes from and to fix it. Unfortunately I don't have time to do that know.

Until then if you want to help you can try to find a pattern to when the phones don't work and when they work. I don't have an explanation for that but just some possible causes which could be for example :
  • Different chips finition / "default" (every chip is a little different)
  • Different models (C50X) (This is little probable because I think some people with C5303 like me had bootloops)
  • Different use (light / heavy use of the phone)
  • Different climates (I find this one cool ! ) (if the problem is linked to some overheat then the problem won't appear as much in north russia as in india)
  • Different settings (disabling stock mpdecision for example reduces the reboots a lot !)
  • You tell me

If you have another idea or have found a proof that one or another reason is involved, please tell me. It will probably help in finding a solution. Just give a good explanation and NOT just a "It's overclocking bro, please fix it".


If you wan't a more detailed explanation of what I suspect being the problem :
There are some informations for each frequency in the table (arch/arm/mach-msm/acpuclock-8960ab.c). Each frequency has an entry which looks like that :
Code:
Select Code
{ 1, {  1350000, HFPLL, 1, 0x32 }, L2(9),  1000000 + VOLTAGE_TUNE, AVS(0x0) },
It has information about the frequency (1350000), the voltage (1000000 + <some variable value>) and some information which I don't really know. Apparently some of them tell that a frequency is the lowest or the highest. To build my new table I could only base it on tables from other devices (moto X) and some patterns that I found. This means I tried many possibilities until it worked.
So I went from this :
Code:
Select Code
        { 1, {   384000, PLL_8, 0, 0x00 }, L2(0),   850000 + VOLTAGE_TUNE, AVS(0x70001F) },
	{ 1, {   486000, HFPLL, 2, 0x24 }, L2(4),   850000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {   594000, HFPLL, 1, 0x16 }, L2(4),   850000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {   702000, HFPLL, 1, 0x1A }, L2(4),   850000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {   810000, HFPLL, 1, 0x1E }, L2(4),   875000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {   918000, HFPLL, 1, 0x22 }, L2(4),   900000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {  1026000, HFPLL, 1, 0x26 }, L2(4),   925000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {  1134000, HFPLL, 1, 0x2A }, L2(9),   950000 + VOLTAGE_TUNE, AVS(0x70000D) },
	{ 1, {  1242000, HFPLL, 1, 0x2E }, L2(9),   975000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {  1350000, HFPLL, 1, 0x32 }, L2(9),  1000000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {  1458000, HFPLL, 1, 0x36 }, L2(9),  1025000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {  1566000, HFPLL, 1, 0x3A }, L2(9),  1050000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {  1674000, HFPLL, 1, 0x3E }, L2(9),  1075000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {  1728000, HFPLL, 1, 0x40 }, L2(9),  1100000 + VOLTAGE_TUNE
		+ TURBO_FREQ_VOLTAGE_TUNE, AVS(0x70000B) },
	{ 0, { 0 }
To this :
Code:
Select Code
	{ 1, {   281000, PLL_8, 0, 0x00 }, L2(0),   825000 + VOLTAGE_TUNE, AVS(0x70001F) },
	{ 1, {   384000, HFPLL, 2, 0x24 }, L2(4),   850000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {   487000, HFPLL, 1, 0x16 }, L2(4),   850000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {   590000, HFPLL, 1, 0x1A }, L2(4),   850000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {   693000, HFPLL, 1, 0x1E }, L2(4),   850000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {   796000, HFPLL, 1, 0x22 }, L2(4),   875000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {   899000, HFPLL, 1, 0x26 }, L2(4),   900000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {  1002000, HFPLL, 1, 0x2A }, L2(4),   925000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {  1105000, HFPLL, 1, 0x2E }, L2(9),   950000 + VOLTAGE_TUNE, AVS(0x70000D) },
	{ 1, {  1204000, HFPLL, 1, 0x32 }, L2(9),   975000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {  1312000, HFPLL, 1, 0x36 }, L2(9),  1000000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {  1416000, HFPLL, 1, 0x3A }, L2(9),  1025000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {  1520000, HFPLL, 1, 0x3E }, L2(9),  1050000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {  1624000, HFPLL, 1, 0x42 }, L2(9),  1075000 + VOLTAGE_TUNE, AVS(0x0) },
	{ 1, {  1728000, HFPLL, 1, 0x46 }, L2(9),  1100000 + VOLTAGE_TUNE
		+ TURBO_FREQ_VOLTAGE_TUNE, AVS(0x70000B) },
	{ 1, {  1832000, HFPLL, 1, 0x48 }, L2(9),  1125000 + VOLTAGE_TUNE
		+ TURBO_FREQ_VOLTAGE_TUNE, AVS(0x0) },
	{ 0, { 0 }
These L2(0) / L2(4) / L2(9) and AVS(0x70000D) must mean something but I don't know where to put / change them, as well as the PLL_8. They might be at the wrong place and this is sufficient to make the phone reboot. For example I used different values for 0x42, 0x46 and 0x48 at the beginning and they made my phone always reboot at antutu test. Changing them made it work (apparently only for my phone )

If you have any knowledge about these frequency tables, what are their informations or how to build them, I would be pleased if you can contact me.

The Following 3 Users Say Thank You to pec0ra For This Useful Post: [ Click to Expand ]
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes