Database Info

[Tutorial] Lockscreen, Home Key, Power Menu not working

This guide attempts to solve the following problems:-
1. The menu and home buttons' keypresses are detected but the respective actions aren't executed.
2. The lockscreen doesn't get activated.
3. The power menu has only reboot and power off as options. The rest of the options like Airplane Mode and Profiles.
PREREQUISITES:
1. ADB
2. SQLITE3
FIX:
1-Copy sqlite3 to /system/bin
2- chmod 777 /system/bin/sqlite3
3-Type following command in ADB or Terminal Emulator
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name,value) VALUES ('device_provisioned','1');"
4- Reboot
5- Done
This guide is based upon this post.

Have you tested this? Does this fix the anoying bug when you press menu and nothing happens so you have to press 2-3 times? Will the phone wake on back/menu press? Mine takes 2-3 clicks to wake with menu/back key, this is not the case with eclair.
2. The lockscreen doesn't get activated. - What do you mean by this? Is it when the lockscreen takes 1-2 seconds to appear after waking the phone? - this doesn't happen to me anymore thankfully.

ka'cipeder said:
Have you tested this? Does this fix the anoying bug when you press menu and nothing happens so you have to press 2-3 times? Will the phone wake on back/menu press? Mine takes 2-3 clicks to wake with menu/back key, this is not the case with eclair.
2. The lockscreen doesn't get activated. - What do you mean by this? Is it when the lockscreen takes 1-2 seconds to appear after waking the phone? - this doesn't happen to me anymore thankfully.
Click to expand...
Click to collapse
I think u misunderstood...
*Sometimes due to a weired bug in android, there are only 4 options in extended power menu..Power Off,Reboot,Recovery n Download.
*Home button does not works at all.
*Lock-screen is completely gone.
*Power menu just turns on the screen
*Sleep mode is gone.
U can search for the same problem over google but there was no sure shot solution... But now there is..
I myself faced it few times while cooking the roms and each time u face this bug, there is no other way than start from zero again....

Had the same problem ages ago.
It occurs if you remove SetupWizard.apk.
Leave it be, do a factory reset and all will be well.

ka'cipeder said:
Have you tested this? Does this fix the anoying bug when you press menu and nothing happens so you have to press 2-3 times? Will the phone wake on back/menu press? Mine takes 2-3 clicks to wake with menu/back key, this is not the case with eclair.
Click to expand...
Click to collapse
that's no bug. it's the normal behavior of froyo that you have to do a double click on the "outside buttons" to wake up the phone.
sent from the desert

Had this exact same problem yesterday. had to reflasb. And this happens after you switch roms with g3mod multiboot.
Sent from my GT-I5800 using XDA App

dilzo said:
Had this exact same problem yesterday. had to reflasb. And this happens after you switch roms with g3mod multiboot.
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
Exactly! thats why i prefer triboot/dualboot

Is it possible to include this fix in a rom?
Or to do it in recovery with a update.zip?

this is not even needed thomas You have deleted setupwizard.apk from system/app I think. If you delete that apk this happens just place it back. If you apply this but do not have the setupwizard.apk in your system it will come back after a while

I dont deleted it but maybe it is because i deodexed the rom... I wil try to replace it
Sent from my GT-I5800 using XDA App

Thanks Werker. It worked!
Sent from my GT-I5800 using Tapatalk

no problem

This tutorial worked for me. Thanks for the re-post and the shell script!

thanks a lot. i had this the 4th time while using cm9 before i came to this thread. and never had this in any other rom except cm9.
does anyone know what causes this bug?

arnab321 said:
thanks a lot. i had this the 4th time while using cm9 before i came to this thread. and never had this in any other rom except cm9.
does anyone know what causes this bug?
Click to expand...
Click to collapse
no, im still having the same problem on CM 7.2, after you remove Setup Wizard this problem occurs

Thanks a lot, I had this problem so many times, but this is the first time I am handling this without reflashing ROM. Thanks again.

Where can I find setupwizard.apk in not present in system/app
? Can u upload for cm7 a 8.3
Sent from my GT-I5800 using xda app-developers app

thanks! this totally saved my @ss.
I am on a SE Xperia Arc, rooted with CWM recovery, and a generic firmware 4.1.B.0.431.
I went into recovery mode and reset the phone, wiping everything. After that, this exact same problem appeared (home button non-functioning, no lock screen, etc...) Also, the phone would not receive calls! Data was working and was able to receive messages that way, and was able to dial out.
A few tips for people running this fix to save some time.
How to run an ADB terminal command line? Don't bother.
1. Just install something like Root Explorer.
2. copy sqlite3 to the /system/bin directory ON YOUR PHONE
3. change the permissions (that's that chmod 777 means)
4. give owner and group read and write permissions
5. IMPORTANT. copy the fix.sh (it's a script) to the ROOT of the phone. not /sdcard, but ROOT
6. just click on the fix.sh and select "excute) and the script will run and you will see output saying (done, reboot) or something.
good luck! and thanks for everybody's help!

rooted device
Hallo, in advance - sorry for my English (haven't spoke nor written for long time)
Do I need rooted device to go through arunmcops's procedure? I have galaxy Y pro (b5510) and after rooting then unrooting and factory reset, I have the same issue when home button doesn't react... Thanx in advance for any response.

Hi!
I have just encountered this bug (on my I9300) and tried to apply your fix, but sqlite crashes saying
Code:
soinfo_relocate(linker.cpp:1013): cannot locate symbol "sqlite3_load_extension" referenced by "sqlite3" ... CANNOT LINK EXECUTABLE
... what can I do?
I am sure all files have the right permissions, but apart from that I wasn't even able to find that error on google :/
hahaha nevermind... It worked the first time I tried it, I just had to reboot and actually turn the lockscreen on

How to/Solution to disable proximity sensor incall

**Standard Disclaimer applies here: If you screw up your device trying the following steps in this thread, I cant be responsible. But thats old news**
If your phone stays black after a call you can fix it by a couple of ways.
First:
Code:
[B]Q[/B]:Where is the proximity sensor?
[B]A[/B]:Top left of the screen in opposite place to led, if you tily screen under the light you should see the sensor reflect back at you.
Install this app and test your proximity sensor to be sure, that it is not broken: Proximity Sensor Finder
Options you need to try first.
The screen protector, yes it might be transparent but the sensor detects it. Using a sensor testing app from the market it suggested the sensor was covered almost all the time.
So the solution was replace the protector with new one but cut an arc at the top just big enough around the sensor at the top left, easy fix now in call screen is more responsive.
With a vacuum cleaner vacuum over the top area of the phone. This must suck all the dust out of there.
<-------------------------------------->
1 of the other option would be an app called Anyunlock which seems to have solved the problem for me. It seems to be able to wake up when the screen turns off after a call. The app allows you to unlock with the volume key and replaces the lock screen with its own screen.
This option works on my Desire S
<-------------------------------------->
If it's broken, you'll see 0.0 cm all the time.
Solution to disable proximity sensor incall is to put this line into build.prop and reboot:
you can edit the build.prop by pulling it first from the device by doing:
Code:
adb pull /system/build.prop c:\where\you\want\to\put\it\
open with wordpad and add the following line
Code:
gsm.proximity.enable=false
Then
Code:
adb remount
adb push c:\where\you\want\to\put\it\build.prop /system/
reboot so that the settings take effect
This option works on my Desire S
Credits
For disabling the proximity sensor in call go to Matri}{
Rest of the credits go to all the people that figured the other stuff out. (to many post on the net so I don't know who made them but thanks)
Thanks to myself for making this tutorial. (It's my first on xda)
If you have any other idea's just pm me or drop a post.
Thanks

Reserved

Thanks for the guide, it seems that there are quite some people affected by this and I find it much useful. Just a suggestion - IMO more proper place for it will be the General section, so you can request moving it there from the moderators and also adding it to the Index thread (PM ben_pyett)
Sent from my Desire S

Hey,
I just tried your fix but it didn't work for me. Screen still goes black when receiving a call and only reacts when I plug it in through USB. Could it be because my ROM is ICS?
Also tried removing the screen cover & sucking out the dust on the top.
The Anyunlock app works, but that's not ideal of course.

Yes it could be that it's Rom related. I use Endymion. And matri}{ extracted it from the Rom.
Wich Rom do you use. I can take a look for you tonight when I get home.
The anylock works most off as between solution.
Sent from my HTC Desire S using Tapatalk 2

Hey,
I tried it on MIUI ICS, Endymion which both failed. Now I'm using the Reaper ROM but it still doesn't work.

It should work on Endymion. I used it and I even checked if it's the same proximity line in de file of update 3.5.
Did you changed it on the phone or with a text editor on the computer?
I tested it on Endymion just 5 min ago and it worked.
Does your screen still stays black after hanging up? If so can you only unlock with USB cable or power cable?
Sent from my HTC Desire S using Tapatalk 2

Hm, you're right, it does work on Endymion (sorry). I'm having some stability problems with that ROM though...
Do you know how to enable it on MIUI or Reaper (CM based)?

I'm going to check for you tomorrow ok. I'll get back to you.

I just discovered that there is a setting in the MIUI dialer to disable the proximity sensor! This also works, sorry for taking up your time.
But maybe a new suggestion for people who don't want to edit the build file ? Try MIUI!

Solution to disable proximity sensor incall is to put this line into build.prop and reboot:
you can edit the build.prop by pulling it first from the device by doing:
Code:
adb pull /system/build.prop c:\where\you\want\to\put\it\
open with wordpad and add the following line
Code:
gsm.proximity.enable=false
Then
Code:
adb remount
adb push c:\where\you\want\to\put\it\build.prop /system/
reboot so that the settings take effect
This option works on my Desire S
Click to expand...
Click to collapse
if anyone could explain this in noob terms it would be much apprecited

New kid on the block
papaganz said:
I just discovered that there is a setting in the MIUI dialer to disable the proximity sensor! This also works, sorry for taking up your time.
But maybe a new suggestion for people who don't want to edit the build file ? Try MIUI!
Click to expand...
Click to collapse
Hey, I'm a TOTAL rookie at this stuff guys...........can you talk me through this process step by step. The sensor is banjaxed (tested it) and I need to turn the thing off.
Thanks in advance!

Larpogue said:
Hey, I'm a TOTAL rookie at this stuff guys...........can you talk me through this process step by step. The sensor is banjaxed (tested it) and I need to turn the thing off.
Thanks in advance!
Click to expand...
Click to collapse
Well, if you install a MIUI-based ROM (check the android development forum here), you can just go to your dialer settings and select the option.

rolfharris said:
if anyone could explain this in noob terms it would be much apprecited
Click to expand...
Click to collapse
it works good.
the easiest way is to install rom toolbox app on a rooted phone, go to buildprop editor and add the line, click save and reboot
---------- Post added at 10:15 PM ---------- Previous post was at 10:12 PM ----------
papaganz said:
Well, if you install a MIUI-based ROM (check the android development forum here), you can just go to your dialer settings and select the option.
Click to expand...
Click to collapse
---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------
papaganz said:
Well, if you install a MIUI-based ROM (check the android development forum here), you can just go to your dialer settings and select the option.
Click to expand...
Click to collapse
the easiest way is to install rom toolbox app on a rooted phone, go to buildprop editor and add the line gsm.proximity.enable=false
click save and reboot

Aprentice_ said:
it works good.
the easiest way is to install rom toolbox app on a rooted phone, go to buildprop editor and add the line, click save and reboot
---------- Post added at 10:15 PM ---------- Previous post was at 10:12 PM ----------
---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------
the easiest way is to install rom toolbox app on a rooted phone, go to buildprop editor and add the line gsm.proximity.enable=false
click save and reboot
Click to expand...
Click to collapse
Thanks man for your advise but how do u root a phone (he asks cringeing!) Soory dude but I did say I was a rookie

papaganz said:
Well, if you install a MIUI-based ROM (check the android development forum here), you can just go to your dialer settings and select the option.
Click to expand...
Click to collapse
Larpogue said:
Thanks man for your advise but how do u root a phone (he asks cringeing!) Soory dude but I did say I was a rookie
Click to expand...
Click to collapse
Since you're flashing a custom ROM than it's already rooted

Aprentice_ said:
Since you're flashing a custom ROM than it's already rooted
Click to expand...
Click to collapse
Nope don't think so, "Root Check Failed" hits me when i open the app.

Oh..umm...download this zip file, unzip anywhere on your computer, connect the USB cable to your phone and run the bat file.
http://forum.xda-developers.com/attachment.php?attachmentid=841876&d=1325678726

Aprentice_ said:
Oh..umm...download this zip file, unzip anywhere on your computer, connect the USB cable to your phone and run the bat file.
http://forum.xda-developers.com/attachment.php?attachmentid=841876&d=1325678726
Click to expand...
Click to collapse
Ok bud will do, I'll let you know how I get on

Aprentice_ said:
the easiest way is to install rom toolbox app on a rooted phone, go to buildprop editor and add the line gsm.proximity.enable=false
click save and reboot
Click to expand...
Click to collapse
That's not true. In my experience this line only works in Sense ROMs...

[MOD] MDPI Phone apk for CM9/AOKP 160dpi

I'm fairly new to the xda community... So I'm hoping this works for others like it worked for me. I tried about 20 different modded phone apks that were supposedly designed to work for 160dpi setting on AOKP and CM9 roms and I was just about to give up when I stumbled across one that actually works!!! Directions are pretty simple...
1. Download phone.apk file from below
2. move to root of sd card
3. In root explorer (or any file browser with root access) go to /system/app and rename original phone.apk to phone.apk.bak
4. Copy and paste new phone.apk in /system/app
5. Reboot phone and enjoy
No need to change app permissions to -rw-r--r--
UPDATE!!!! For those of you that prefer a flashable zip, Mr. Apocalypse was kind enough to upload one in post #12 of this thread
If you run into any problems let me know and I'll try to help with troubleshooting.

Wat exactly does it do?
Sent from my LG-P999 using XDA

GD3tyrone said:
Wat exactly does it do?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
It replaces the stock phone app... The stock phone app will crash on any LCD density below 200 dpi. This modded phone app will run on the lower densities so you can use the 160 dpi setting and still be able to make/receive phone calls without a FC error.

jmack89 said:
It replaces the stock phone app... The stock phone app will crash on any LCD density below 200 dpi. This modded phone app will run on the lower densities so you can use the 160 dpi setting and still be able to make/receive phone calls without a FC error.
Click to expand...
Click to collapse
What he's asking.is how does this help us? What purpose does it serve the phone? Speed up? Better battery life? Etc etc etc
Sent from my LG-P999 using XDA

djimpulsion said:
What he's asking.is how does this help us? What purpose does it serve the phone? Speed up? Better battery life? Etc etc etc
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
It's nothing major... Just a fix for a force close error when using the phone app on different LCD densities. A lot of ppl like the look of 160 dpi and 128 dpi (tablet mode) but you lose call functionality as a consequence... This fixes that issue.

Also... If you decide to return the phone to stock LCD density there's no need to revert back to the old phone apk... This one will work in all densities from 128-240 dpi. (I haven't tried anything larger than 240 yet... IDK why anyone would though )

Ah, okay got it..
Sent from my LG-P999 using XDA

thankyou so much! fixed my issue wondered why it kept crashing when it was lower than 200 lol

I'll try it out. That FC pop up gets annoyings as stopping and clearing data after every reboot gets annoying lol.
Does this permanently replace the stock phone apk?

I can't get anything to work. Not the rename, not the copy and past. Nothing.

aaCotyaa said:
I'll try it out. That FC pop up gets annoyings as stopping and clearing data after every reboot gets annoying lol.
Does this permanently replace the stock phone apk?
Click to expand...
Click to collapse
Yes it permanently replaces the stock phone apk.
aaCotyaa said:
I can't get anything to work. Not the rename, not the copy and past. Nothing.
Click to expand...
Click to collapse
Make sure the /system folder is mounted as read/write before you do this... If your file explorer app doesn't have the option to give you root access you can mount /system by using terminal emulator.
Use the following commands:
su
busybox mount -o remount,rw /system

[TROLL]You know, a flashable would really help [/TROLL]
Lol, jk, attached is a flashable, uses the same Phone.apk in the OP for those who's having trouble with the push process.
I personally haven't tested it, but it should help with those who are.

Thanks I'll give that a go. Can I flash this directly to the appropriate file or do I need to move it after flashing?

aaCotyaa said:
Thanks I'll give that a go. Can I flash this directly to the appropriate file or do I need to move it after flashing?
Click to expand...
Click to collapse
Flash it and it will replace whatever Phone.apk you have with the one in the OP.

Mr. Apocalypse said:
Flash it and it will replace whatever Phone.apk you have with the one in the OP.
Click to expand...
Click to collapse
OK Thanks a lot.

Mr. Apocalypse said:
[TROLL]You know, a flashable would really help [/TROLL]
Lol, jk, attached is a flashable, uses the same Phone.apk in the OP for those who's having trouble with the push process.
I personally haven't tested it, but it should help with those who are.
Click to expand...
Click to collapse
Thanks for that! Yea I'm not quite skilled with these things as of yet... Hopefully I'll get there soon though.

The file flash fine, but I'm still experiencing a problem. Fortunately, I think I've narrowed down the problem to Wfi Calling. I started a new thread in search for an answer. Eith way, thanks for the effort guys!

Does this fix the issue where the slider to answer the call is off the screen?

navjot94 said:
Does this fix the issue where the slider to answer the call is off the screen?
Click to expand...
Click to collapse
No, unfortunately not.
I just ran in this issue, looking for a fix right now.

LuHe said:
No, unfortunately not.
I just ran in this issue, looking for a fix right now.
Click to expand...
Click to collapse
Didn't find any working package so I started browsing the Android source.
I think I found the root of this problem:
https://github.com/AOKP/packages_apps_Phone/blob/ics/res/layout/incall_touch_ui.xml#L52
Code:
<!--
(1) incomingCallWidget: the UI displayed while an incoming call is ringing.
See InCallTouchUi.showIncomingCallWidget().
Layout notes:
- Use an opaque black background since we need to cover up
a bit of the bottom of the contact photo
- The verticalOffset value gets us a little extra space above
the topmost "Respond by SMS" icon
- [b]The negative layout_marginBottom shifts us slightly downward;
we're already aligned with the bottom of the screen, but we
don't have an icon in the downward direction so the whole
bottom area of this widget is just wasted space.[/b]
-->
<com.android.internal.widget.multiwaveview.MultiWaveView
android:id="@+id/incomingCallWidget"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_alignParentBottom="true"
[b]android:layout_marginBottom="-46dp"[/b]
android:background="@android:color/black"
android:visibility="gone"
I guess this -46dp is too much and needs to be lowered a bit.
Downloading AOKP source right now and trying to rebuild the Phone.apk

[Q] No disable soft keys backlight settings?

How can I disable soft keys backlight without power saving? Is no longer in the settings of the Galaxy s6.

I don't believe theres a setting for it, I've looked and looked, I like to set it to 6 seconds but its nowhere to be found.

Yeah I think you need to root and install a custom Rom or xposed (if that's possible yet)

Please refer to my earlier post at http://forum.xda-developers.com/showpost.php?p=60009456&postcount=12 and/or use the search function.

The ATT version has this setting under Display. It's weird that the other versions don't have that setting.

How can I run adb for this fix? Can some one help me to run adb..

The post above has instructions on how to to that

I just ran terminal emulator from my phone and entered "settings put system button_key_light 0" and they are disable for good.

Capacitive Lights Off
Two ways ,
1. The observe the power saving mode turns it off by default.
2. This message is from the user/developer @Averix in one of the S6 thread,
"That thread covers the ADB method. I wrote an app that doesn't require root to set the values to whatever you want from .5 - 10 seconds on, off/on all the time."
Galaxy Button Lights
Hope this helps

nappent said:
I just ran terminal emulator from my phone and entered "settings put system button_key_light 0" and they are disable for good.
Click to expand...
Click to collapse
Are you rooted? Doesn't work for me.

knitler said:
Are you rooted? Doesn't work for me.
Click to expand...
Click to collapse
Does the app not work on your device?

knitler said:
Are you rooted? Doesn't work for me.
Click to expand...
Click to collapse
Use the app in the post above yours, I'm not rooted and it worked fine for me
Sent from my Verizon S6,
formerly abdel12345

LG g4 and V10 Bootloop Fix Permanent 100% Assurity

Dear Friends!
I Just Got Bootlooped on my device (V10). I was desperately need to fix my phone. I tried every method heat sink cooling all other methods which i found online...
I just posted a video link from which you can see tutorial to fix ypur cell phone.
as you all know the main reason of bootloop in v10 or g4 is cpu big cores connection problem when phone got heat or more heat it will cause bubbles b/w mobo and qualcomm chip and it cause bootloop.
i just did below in simple words...
remove the chip from motherboard clean it with ethin and place it again on the board
do it at your own risk fellas///
my phone is working now since 4 months all okay............
https://www.youtube.com/watch?v=lYOGnWA-xU4

what about a fix without soldering or replacing parts is there a chance

thnx

Would be easier to just replace the whole motherboard. This could be useful though if you didn't backup your stuff before. But if you have a G4 or V10 and don't do that by now...

Hi mate if i removed the cpu completly without putting it back is it going to work or not please respond and sorry for my bad english

Deadmeat02 said:
Hi mate if i removed the cpu completly without putting it back is it going to work or not please respond and sorry for my bad english
Click to expand...
Click to collapse
lol, if you dont put the cpu back in...the phone doesnt work! LOLOLOLOL
BIIIIGGGG LOOOOOL
are you noob?! i see so, because is worthless question from you, didnt deserve the answer but, i just want to tell you i just laught very very very loud when i see the question you made!!! LOOOOL

sun_is_shinning said:
lol, if you dont put the cpu back in...the phone doesnt work! LOLOLOLOL
BIIIIGGGG LOOOOOL
are you noob?! i see so, because is worthless question from you, didnt deserve the answer but, i just want to tell you i just laught very very very loud when i see the question you made!!! LOOOOL
Click to expand...
Click to collapse
Lmao thats becuase i read that i can disable the big cores i thought that cpu was the big cores and there is another cpu that has the rest of the cores hahahahhah iam a noob so please be easy on me
I want to ask a question please is there any files that i can use for my vs990 to disable the big cores because i didn't find any thank you for replaying and sorry for the stupid question up there

Deadmeat02 said:
Lmao thats becuase i read that i can disable the big cores i thought that cpu was the big cores and there is another cpu that has the rest of the cores hahahahhah iam a noob so please be easy on me
I want to ask a question please is there any files that i can use for my vs990 to disable the big cores because i didn't find any thank you for replaying and sorry for the stupid question up there
Click to expand...
Click to collapse
there's a way to disable big cores, you need root at first, if you are rooted then install terminal emulator, then write:
su
- do enter, and write:
echo "0" > sys/devices/system/cpu/cpu4/online
- enter again and the follow:
echo "0" > sys/devices/system/cpu/cpu5/online
- enter again and the big cores will be disabled, install CPU-Z and see if last 2 cores of the list are Stopped.
thats it.

sun_is_shinning said:
there's a way to disable big cores, you need root at first, if you are rooted then install terminal emulator, then write:
su
- do enter, and write:
echo "0" > sys/devices/system/cpu/cpu4/online
- enter again and the follow:
echo "0" > sys/devices/system/cpu/cpu5/online
- enter again and the big cores will be disabled, install CPU-Z and see if last 2 cores of the list are Stopped.
thats it.
Click to expand...
Click to collapse
Thank you for replaying sir is there any root for the verizon lg v10 i searched a lot for it but i didn't find any iam on mm i was hoping for a file that can disable the big cores but there is none for verizon

You don't need to remove the CPU. You just have to redo the connection.
It might feel funny but when I faced this issue I serched alot and then i found a video on Youtube that helped me, I just removed the steel covers on the motherboard(the one's which cover the CPU) and put it under normal Iron. Got it out after 5 minutes and placed it in the phone and the phone is working perfectly from almost a month.
Try that before removing the cpu or Replacing the motherboard.

sun_is_shinning said:
there's a way to disable big cores, you need root at first, if you are rooted then install terminal emulator, then write:
su
- do enter, and write:
echo "0" > sys/devices/system/cpu/cpu4/online
- enter again and the follow:
echo "0" > sys/devices/system/cpu/cpu5/online
- enter again and the big cores will be disabled, install CPU-Z and see if last 2 cores of the list are Stopped.
thats it.
Click to expand...
Click to collapse
i managed to disable 4th core but i am getting "permission denied" error while disabling 5th core.

Raj_The_Ripper said:
i managed to disable 4th core but i am getting "permission denied" error while disabling 5th core.
Click to expand...
Click to collapse
how you got your phone rooted ?

samy2015 said:
how you got your phone rooted ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=75602401&postcount=1821

sun_is_shinning said:
there's a way to disable big cores, you need root at first, if you are rooted then install terminal emulator, then write:
su
- do enter, and write:
echo "0" > sys/devices/system/cpu/cpu4/online
- enter again and the follow:
echo "0" > sys/devices/system/cpu/cpu5/online
- enter again and the big cores will be disabled, install CPU-Z and see if last 2 cores of the list are Stopped.
thats it.
Click to expand...
Click to collapse
Hi,
I have Flex2 and after 2 years of awesomeness it just decided to bootloop today. I had root installed via TOT method so I tried your method of disabling cores. I did as you said and CPUZ shows CPU4/5/7 stopped but CPU6 still running. It still bootloops. Any further resolution?
Update: Kernel auditor shows CPU 5 and 8 offline only. So I tried disabling the remaining two big cores from kernel auditor itself but no success.
Update2: All cores came online on their own. Now I get 'permission denied' when executing the above commands again.

n00b_dr0id said:
Hi,
I have Flex2 and after 2 years of awesomeness it just decided to bootloop today. I had root installed via TOT method so I tried your method of disabling cores. I did as you said and CPUZ shows CPU4/5/7 stopped but CPU6 still running. It still bootloops. Any further resolution?
Update: Kernel auditor shows CPU 5 and 8 offline only. So I tried disabling the remaining two big cores from kernel auditor itself but no success.
Click to expand...
Click to collapse
then you need to do other line in terminal emulator wich in your case is:
echo "0" > sys/devices/system/cpu/cpu6/online
so the "cpu6" is the core you want to disable, just check the cpu-z info of number of core and change it in the line acording of what core you need to disable.

sun_is_shinning said:
then you need to do other line in terminal emulator wich in your case is:
echo "0" > sys/devices/system/cpu/cpu6/online
so the "cpu6" is the core you want to disable, just check the cpu-z info of number of core and change it in the line acording of what core you need to disable.
Click to expand...
Click to collapse
Now all core came online on it's own and I get 'permission denied' when tried to execute the codes again.
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
sun_is_shinning said:
then you need to do other line in terminal emulator wich in your case is:
echo "0" > sys/devices/system/cpu/cpu6/online
so the "cpu6" is the core you want to disable, just check the cpu-z info of number of core and change it in the line acording of what core you need to disable.
Click to expand...
Click to collapse
All the core online on it's own and I get 'permission denied' when trying to execute the commands again.

n00b_dr0id said:
Now all core came online on it's own and I get 'permission denied' when tried to execute the codes again.
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
All the core online on it's own and I get 'permission denied' when trying to execute the commands again.
Click to expand...
Click to collapse
That phone (i belive because i already have one too) have something that doesnt allow to disable come of the cores because the SoC is a problematic one so, i think LG have done something to not allow controlling the cores as people would like.

sun_is_shinning said:
That phone (i belive because i already have one too) have something that doesnt allow to disable come of the cores because the SoC is a problematic one so, i think LG have done something to not allow controlling the cores as people would like.
Click to expand...
Click to collapse
I noticed one weird thing that battery was working alright before bootloop but now battery percentage shows high or low abnormally. Changing battery will solve anything or is this normal in this condition too?

n00b_dr0id said:
I noticed one weird thing that battery was working alright before bootloop but now battery percentage shows high or low abnormally. Changing battery will solve anything or is this normal in this condition too?
Click to expand...
Click to collapse
i cant say for sure because i didnt have the bootloop in any LG phone that i have, as i lucky?! no, i just go ahead, dissasembly the phone and put thermal compoud between the processor and display frame and i run fine, my V10 have 2 years with me and still running and no bootloop whatsoever.
maybe the problem of your bootloop is the battery and not the phone...i see some people with the same problem and they say if you replace the battery the bootloop on G Flex2 fixed with that.

sun_is_shinning said:
i cant say for sure because i didnt have the bootloop in any LG phone that i have, as i lucky?! no, i just go ahead, dissasembly the phone and put thermal compoud between the processor and display frame and i run fine, my V10 have 2 years with me and still running and no bootloop whatsoever.
maybe the problem of your bootloop is the battery and not the phone...i see some people with the same problem and they say if you replace the battery the bootloop on G Flex2 fixed with that.
Click to expand...
Click to collapse
Thermal compound is pretty much the only way to prevent bootloop. Wise decision man. Does it still worsk?