Related
Ok, i have a fully rooted incredible with SetCPU installed. I have profiles enabled and setup but when i change the main profile the current clockspeed is always higher. Also, the min/max at the top right never change from 998mhz max and 250 min. Do i need a special kernel or something to use setcpu? i have it under the nexus one/snapdragon profile btw. and its 1.5.4
mikerulez121 said:
Ok, i have a fully rooted incredible with SetCPU installed. I have profiles enabled and setup but when i change the main profile the current clockspeed is always higher. Also, the min/max at the top right never change from 998mhz max and 250 min. Do i need a special kernel or something to use setcpu? i have it under the nexus one/snapdragon profile btw. and its 1.5.4
Click to expand...
Click to collapse
Looks like only simple switches like "performance, userspace, etc" and for some reason advanced settings will make a difference. I believe persistent/kernel-level switches not provided for in the UI cannot work at present because we can't write to the build.prop, user.conf, or init.rc.
P.S., the DI's processor is upgraded from N1's. Same product line, newer model.
So im out of luck until a new kernel is out? Ok. But if i get a new kernel, will i be able to keep the default os or does that require a new rom?
Give 1.6 a try. Maybe it works for you.
larsdennert said:
Give 1.6 a try. Maybe it works for you.
Click to expand...
Click to collapse
Nope, even in 1.6 direct throttling still does/can not work, but seems like selecting userdata, performance, or ondemand has an effect on where the processor speed averages
You will need a overclocked kernal for SetCPU to work.
You DO NOT need an overclock kernel for it to work. The problem is the /system partition is not writable from within Android which is how SetCPU works. Once we get the nand unlock, it'll work.
from my understanding is you will need an unlocked kernel and RW NAND
Berzerker7 said:
You DO NOT need an overclock kernel for it to work. The problem is the /system partition is not writable from within Android which is how SetCPU works. Once we get the nand unlock, it'll work.
Click to expand...
Click to collapse
Now THAT makes sense. I'm not sure I want a Nand unlock; but I'd like an easier way to push stuff in recovery so I can make intentional tweaks and protect the OS the rest of the time.
I downloaded Dalingrin's 5/23 Kernel for stock/froyo, put it on my SD and installed the zip, but I can't clock it past 800Mhz...did I do something wrong??
Omega Ra said:
I downloaded Dalingrin's 5/23 Kernel for stock/froyo, put it on my SD and installed the zip, but I can't clock it past 800Mhz...did I do something wrong??
Click to expand...
Click to collapse
It doesn't give you the option or it freezes/crashes, etc when you clock higher than 800Mhz?
ivanmmj said:
It doesn't give you the option or it freezes/crashes, etc when you clock higher than 800Mhz?
Click to expand...
Click to collapse
it doesn't give me the option. I open setcpu and I can't put the slider any higher than 800
Omega Ra said:
it doesn't give me the option. I open setcpu and I can't put the slider any higher than 800
Click to expand...
Click to collapse
Have setcpu automatically detect the speeds again to see the new speeds.
ivanmmj said:
Have setcpu automatically detect the speeds again to see the new speeds.
Click to expand...
Click to collapse
tried that, still only shows 800Mhz. I even re-downloaded the kernel zip and re-installed it...nothing.
problem solved, used wrong kernel.
/thread
Hello everyone,
My question is about Throttling. We know in stock Nexus 4 kernel, throttling starts when battery temperature hits 37C. CPU throttling is fine, but problem comes when it starts throttling GPU. Is there a way we can stop it from throttling GPU? Can we edit the stock thermald.conf file? Is it safe to edit it and remove GPU option from it and make it throttle when the battery temperature reaches 40C?
TheRebel said:
Hello everyone,
My question is about Throttling. We know in stock Nexus 4 kernel, throttling starts when battery temperature hits 37C. CPU throttling is fine, but problem comes when it starts throttling GPU. Is there a way we can stop it from throttling GPU? Can we edit the stock thermald.conf file? Is it safe to edit it and remove GPU option from it and make it throttle when the battery temperature reaches 40C?
Click to expand...
Click to collapse
should work and should be safe. why dont you try it?
vollmilch said:
should work and should be safe. why dont you try it?
Click to expand...
Click to collapse
Thank bro
Lol, I thought I might hard brick my phone. Do you know anyone else tried it?
I know we can get rid of this gpu throttling (which happens so early) by using some custom kernel, but i've tried many custom kernels, but they don't seem to have same smoothness as stock kernel.
TheRebel said:
Thank bro
Lol, I thought I might hard brick my phone. Do you know anyone else tried it?
I know we can get rid of this gpu throttling (which happens so early) by using some custom kernel, but i've tried many custom kernels, but they don't seem to have same smoothness as stock kernel.
Click to expand...
Click to collapse
trinity kernel has battery temp throttle disable, and its extremely smooth.
simms22 said:
trinity kernel has battery temp throttle disable, and its extremely smooth.
Click to expand...
Click to collapse
thanks!!!
does trinity kernel throttles on CPU temperature? thermal throttling?
And do you have any idea about my question in first post? Is it safe to edit the stock kernel's thermald.conf file?
TheRebel said:
thanks!!!
does trinity kernel throttles on CPU temperature? thermal throttling?
And do you have any idea about my question in first post? Is it safe the stock kernel's thermald.conf file?
Click to expand...
Click to collapse
it has its cpu throttle temp raised. but there is a simple script you can run in a terminal emulator app or go to tbe location with a root file explorer and exit manually. in a terminal emulator app..
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled(press enter)
i always run with thermal throttle disabled. tbe cpu safty temp is still intact, if you hit it, youll automatically shut down to cool off. the only way that you will hit it is if you try to hit it.
about editing the thermald.conf file.. is it safe modding your phone in the first place?
i believe that faux's kernel uses a modded thermald file (cpu throttle temp raised, gpu throttle disabled). i used to keep a copy of the file on my dropbox and i would post it here for you but I deleted it some time ago. why dont you ask someone in his thread to share it with you so you can just replace yours.
but keep a backup of your original just in case
simms22 said:
it has its cpu throttle temp raised. but there is a simple script you can run in a terminal emulator app or go to tbe location with a root file explorer and exit manually. in a terminal emulator app..
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled(press enter)
i always run with thermal throttle disabled. tbe cpu safty temp is still intact, if you hit it, youll automatically shut down to cool off. the only way that you will hit it is if you try to hit it.
about editing the thermald.conf file.. is it safe modding your phone in the first place?
Click to expand...
Click to collapse
Thanks for this! you're awesome
I know modding phone is not safe, that's why I was asking.
Anyway if I want to give try to trinity kernel, which one should I install? I'm currently on CM stable.
there are two links in trinity thread
one at the top (i'm not allowed to post links here of the OP) the link of homepage
Second says, stock/aosp + CM
vollmilch said:
i believe that faux's kernel uses a modded thermald file (cpu throttle temp raised, gpu throttle disabled). i used to keep a copy of the file on my dropbox and i would post it here for you but I deleted it some time ago. why dont you ask someone in his thread to share it with you so you can just replace yours.
but keep a backup of your original just in case
Click to expand...
Click to collapse
Thanks for the reply. I've faux123 thermald.conf file. But I dont' know whether I should replace stock thermald.conf with faux thermald.conf. Because faux has used Sampling 1500 (while in stock the sampling value is 5000). I don't know about sampling though , just the values were different so i didn't replace the file, thought it might hard brick the phone
TheRebel said:
Thanks for this! you're awesome
I know modding phone is not safe, that's why I was asking.
Anyway if I want to give try to trinity kernel, which one should I install? I'm currently on CM stable.
there are two links in trinity thread
one at the top (i'm not allowed to post links here of the OP) the link of homepage
Second says, stock/aosp + CM
Click to expand...
Click to collapse
go to http://www.derkernel.com/mako.php , click on "experimental" and download the first one (TF133).
if your rom doesnt use a modded ramdisk, just reboot into recovery, flash it, wipe cache and dalvik, reboot
TheRebel said:
Thanks for this! you're awesome
I know modding phone is not safe, that's why I was asking.
Anyway if I want to give try to trinity kernel, which one should I install? I'm currently on CM stable.
there are two links in trinity thread
one at the top (i'm not allowed to post links here of the OP) the link of homepage
Second says, stock/aosp + CM
Click to expand...
Click to collapse
theres only one link for downloads, tf133 is the latest http://derkernel.com/jb-mako.php
simms22 said:
theres only one link for downloads, tf133 is the latest http://derkernel.com/jb-mako.php
Click to expand...
Click to collapse
is there any difference in throttling based on battery temp and CPU temp? which one exactly are modifying using the echo command?
CPU temp threshold can be raised easily in faux app, so what about battery temp threshold? can we change it?
Update: I found an even better solution. Instead of setting "dalvik.vm.heapsize=256m" use "dalvik.vm.heapsize=128m"
Warning! Please make a backup of your /system partition using recovery incase you get a bootloop from changing vm heapsize. Don't go below 128m as it may cause a bootloop.
If you want additional memory you can download "Ram Manager Free" from the Google playstore and set up a disk swap. Within the app, go to swap and delete the given directory and set it to "/cache and use a value of 256 MB. It won't steal from your already limited storage as it will use the cache partition which goes mainly unused. Warning though as it may degrade your internal storage from constant writing. If you ask me I don't care about degradation of my Moto G as I plan to get a better phone soon. I only recommend you use swap with the stock kernel as there is virtually no lag. I tested with other kernels and there is noticeable lag.... Aero Kernel lags noticeably and so does faux kernel. Oh! and make sure you set it to balanced and check the apply at boot option to stick. I stopped using swap, but you can try for yourself to see if you like it.
This is for the Moto G XT1034 as I don't know if the build.prop is different for the other variants, but you can always check if you have the duplicate entries.
While going through the build.prop of the stock 4.4.4 ROM I found duplicate entries of the same value with different parameters. The culprit being "dalvik.vm.heapsize" seemed to have been causing my music apps force closing when there was "insufficient" RAM. Other apps running in the background can also be killed like night screen filters while browsing the web using Chrome just to name another. You'll find two entries called "dalvik.vm.heapsize=36 and dalvik.vm.heapsize=256." They are the same value, but with different parameters. I deleted the one for "36m" and my multitasking issues disappeared without changing the MINFREE TASKKILLER values. I used Performance Control that can be found here on XDA to edit the build.prop. When you delete "dalvik.vm.heapsize=36m" make sure you re-add the value "dalvik.vm.heapsize=256m" because deleting one deletes BOTH! My screen filter app "EasyEyes" has yet to be killed by low memory situations.
Why would Motorola include duplicate entries of the heapsize? I'd like to be enlightened on why they included both.
NOW, your music app may be killed if you run very low on memory, this happens when you use chrome and view heavy pages, so modifying your MINFREE TASKKILLER values may be of additional assistance. I attached a screenshot of MINFREE values if you want to use my values, although I'm not using them since I'm using stock values. At the end of the day you have to understand that 1GB is now "low-end" and is simply not enough for multitasking anymore on Android. Apps are becoming larger and browsers and websites are becoming more complex; more RAM is needed. As soon as you open Chrome expect your apps to be killed since it needs at least 200 MB to run adequately.
Any reports of success with this? I just sold my Moto G last week because of the multi tasking issue... if this solves 90% of the problem, that would be pretty awesome.
I updated this with an even better solution. Set dalvik.vm.heapsize=256m to dalvik.vm.heapsize=128m to make the phone much less likely to kill apps in general.
Also, can anyone please tell me what the storage is like with stock lollypop? I've used art runtime on my 8GB moto g and reverted back to dalvik because my storage was nearly full. If that's still the case then I will keep my moto G running 4.4.4 forever... well until it dies.
Jorge_007 said:
I updated this with an even better solution. Set dalvik.vm.heapsize=256m to dalvik.vm.heapsize=128m to make the phone much less likely to kill apps in general.
Also, can anyone please tell me what the storage is like with stock lollypop? I've used art runtime on my 8GB moto g and reverted back to dalvik because my storage was nearly full. If that's still the case then I will keep my moto G running 4.4.4 forever... well until it dies.
Click to expand...
Click to collapse
My phone isnt booting up can you plz tell me how to fix this, i changed it to 128m and its not booting up
NextGenGTR said:
My phone isnt booting up can you plz tell me how to fix this, i changed it to 128m and its not booting up
Click to expand...
Click to collapse
Did you follow the direction? Using Performance control edit build.prop. Delete "dalvik.vm.heapsize=256m and re-add the value "dalvik.vm.heapsize=128m" and click apply? Anyways what phone model are you using?
Anyways, I assume you followed accordingly, so you should have made a backup of your system partition using your preferred recovery. To undo the changes made boot into recovery and restore system partition. That will make the phone boot. If you didn't, then if you know can always restore using this guide: http://forum.xda-developers.com/showthread.php?t=2542219
OR you can flash a stock rom zip from here "http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Jorge_007 said:
Did you follow the direction? Using Performance control edit build.prop. Delete "dalvik.vm.heapsize=256m and re-add the value "dalvik.vm.heapsize=128m" and click apply? Anyways what phone model are you using?
Anyways, I assume you followed accordingly, so you should have made a backup of your system partition using your preferred recovery. To undo the changes made boot into recovery and restore system partition. That will make the phone boot. If you didn't, then if you know can always restore using this guide: http://forum.xda-developers.com/showthread.php?t=2542219
OR you can flash a stock rom zip from here "http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Click to expand...
Click to collapse
Can you get your stock build.prop with the heapszie 256m and then plz go into recovery and then use adb pull /system/build.prop c:\ and the give it to me so i can flash it through recovery, i think that would work because i have a flashable zip with a build.prop but its not for this phone so i need to replace it with another, i have the stock moto g build . prop but i cant edit it with windows.
NextGenGTR said:
Can you get your stock build.prop with the heapszie 256m and then plz go into recovery and then use adb pull /system/build.prop c:\ and the give it to me so i can flash it through recovery, i think that would work because i have a flashable zip with a build.prop but its not for this phone so i need to replace it with another, i have the stock moto g build . prop but i cant edit it with windows.
Click to expand...
Click to collapse
This is the stock build.prop untouched for my Moto G XT1034 AWS firmware
It's not flashable, you'll have to make it a flashable zip
Jorge_007 said:
This is the stock build.prop untouched for my Moto G XT1034 AWS firmware
It's not flashable, you'll have to make it a flashable zip
Click to expand...
Click to collapse
The phone refused to boot up so now i am trying another step to only flash system files 0 1 2 and hopefully that will work!!!
Suprisingly enough that worked and nothing has been deleted and everything is how it is suppose to be! I have all my applications and my backgrounds and files intact!!! Add this in your tutorial if anyone faces the issue, flash the system files.
NextGenGTR said:
The phone refused to boot up so now i am trying another step to only flash system files 0 1 2 and hopefully that will work
Click to expand...
Click to collapse
That will definitely work. Remember to always make a backup of your system when making changes to /system.
Jorge_007 said:
That will definitely work. Remember to always make a backup of your system when making changes to /system.
Click to expand...
Click to collapse
Also may i ask if you can possibly clear up your tutorial please since it confused me a lot and i must of done something wrong to f my phone. Thanks. Im just confused i have the build editor from Jrummy apps and it has the two 36m and 256m, now i deleted the 256m and then edited the 36m to 128m is that correct ?
NextGenGTR said:
Also may i ask if you can possibly clear up your tutorial please since it confused me a lot and i must of done something wrong to f my phone. Thanks. Im just confused i have the build editor from Jrummy apps and it has the two 36m and 256m, now i deleted the 256m and then edited the 36m to 128m is that correct ?
Click to expand...
Click to collapse
Don't use the ones on the playstore. I had trouble with them in the past when it came to editing the build.prop on this phone. Use Performance Control from XDA http://forum.xda-developers.com/devdb/project/?id=600#downloads Make sure you install busy box from the playstore as it is needed for the app to work. Make sure you make a backup of you /system in recovery first. Once performance control is installed, swipe left until you get to the tools tab. Scroll down until you see "Edit build prop" Delete both entries for 36m and 256m. To delete press and hold and it will ask if you want to delete. Press apply values to save. Now click on the menu button that has three dots and select "add parameter" and enter "dalvik.vm.heapsize" for Name and enter "128m" for value and press save. Make sure you press on apply values and reboot.
Jorge_007 said:
Don't use the ones on the playstore. I had trouble with them in the past when it came to editing the build.prop on this phone. Use Performance Control from XDA http://forum.xda-developers.com/devdb/project/?id=600#downloads Make sure you install busy box from the playstore as it is needed for the app to work. Make sure you make a backup of you /system in recovery first. Once performance control is installed, swipe left until you get to the tools tab. Scroll down until you see "Edit build prop" Delete both entries for 36m and 256m. To delete press and hold and it will ask if you want to delete. Press apply values to save. Now click on the menu button that has three dots and select "add parameter" and enter "dalvik.vm.heapsize" for Name and enter "128m" for value and press save. Make sure you press on apply values and reboot.
Click to expand...
Click to collapse
Thank you so much for the help! I think i have finally did it! I only have the 128m when i check with es file explorer and i guess it is all fine! Is there a way i can confirm my thing is 128m ?
NextGenGTR said:
Thank you so much for the help! I think i have finally did it! I only have the 128m when i check with es file explorer and i guess it is all fine! Is there a way i can confirm my thing is 128m ?
Click to expand...
Click to collapse
Well you can install RAM Manager free from Playstore https://play.google.com/store/apps/details?id=com.smartprojects.RAMOptimizationFree&hl=en Go to "Extra" and select VM Heap Size it should read 128m. Also, listening to music should not be killed when multi-tasking. Apps such as iHeartRadio would always get killed when browsing the internet with Chrome. It doesn't happen anymore on my end. Also if you're not worried about your phones internal ssd from degrading you can set up a swap file to disk. Under Extra select swap file and delete the default directory and type "/cache" without quotes and set it to 256mb. It'll use the cache partition, so you'll still have your disk space for apps. It may degrade the life of your Moto G because of the constant writes, so it's up to you if you want to set up a swap. AND set it on Balanced on the main tab and check set on boot. Only do this on the stock kernel as I noticed lag on other kernels. Anyways you don't have to use swap or the ram manager app after your verify vm heap is 128m. I don't use it as just setting 128m vm heap no longer kills my music apps.
NextGenGTR said:
Thank you so much for the help! I think i have finally did it! I only have the 128m when i check with es file explorer and i guess it is all fine! Is there a way i can confirm my thing is 128m ?
Click to expand...
Click to collapse
I think I found the real problem of the aggressive app killing. Go back to build.prop in performance control and change 128m back to 256m. Apply to save. Now go back and look for this value "ro.MAX_HIDDEN_APPS=12" and delete it; press and hold to delete. I'm testing it as of today, so if you can test it too let me know if it reduces the frequency of app killing aggressiveness. iHeartRadio has not been killed while browsing in Chrome for me. Thanks.
Jorge_007 said:
I think I found the real problem of the aggressive app killing. Go back to build.prop in performance control and change 128m back to 256m. Apply to save. Now go back and look for this value "ro.MAX_HIDDEN_APPS=12" and delete it; press and hold to delete. I'm testing it as of today, so if you can test it too let me know if it reduces the frequency of app killing aggressiveness. iHeartRadio has not been killed while browsing in Chrome for me. Thanks.
Click to expand...
Click to collapse
Changed it and let me do a few tests, I usually get SoundCloud to crash
When I load clash of clans...
NextGenGTR said:
Changed it and let me do a few tests, I usually get SoundCloud to crash
When I load clash of clans...
Click to expand...
Click to collapse
Okay, let me know how thing go
Jorge_007 said:
Okay, let me know how thing go
Click to expand...
Click to collapse
Listening to SoundCloud and playing clash of clans caused home screen to reload icons when pressing home button.
NextGenGTR said:
Listening to SoundCloud and playing clash of clans caused home screen to reload icons when pressing home button.
Click to expand...
Click to collapse
Oh a launcher redraw is to be expected if you're playing a game and listening to music. 1GB is just not enough to maintain everything in memory. Did soundcloud close though? Last time I checked it was a RAM heavy application.
Jorge_007 said:
Oh a launcher redraw is to be expected if you're playing a game and listening to music. 1GB is just not enough to maintain everything in memory. Did soundcloud close though? Last time I checked it was a RAM heavy application.
Click to expand...
Click to collapse
Currently with your settings + a build.prop code for the launcher to keep it in ram i am not experiencing any issues, also i have installed Rom toolbox pro which comes with build.prop editor and many other cool features, one being the minfree value changer, others have reported using the aggressive min free values from minfreemanager helps out so i am using that in romtoolbox and everything is in one single app so its nice and tidy, i recomend you give it a shot
Seems to work on lollipop as well!
Sent from my XT1032 using XDA Free mobile app
I have the Verizon Pixel XL and can now toggle the oem unlock switch in developers settings. Annoyed with the "grey out" I have done several things to make the switch useable. Well... Something worked. Now it's time to figure out what did the trick.
Solved. Using a root file explorer, got to /data/system/users/ 0.xml Open it up and edit it to reflect no restrictions. Or clone mine, might wanna remove my name though.. One requirement for this to work, all testing shows it will not work on stock kernel. Not sure if its a selinux issue or not but the modified ElementalX I made does boot up permissive and removes forceencryption. And using it Confirmed working..
I am decrypted and running permissive. All done through kernel editing. Not sure that made a difference or not but did notice any changes beforehand.
So you added the supercid through the kernel editing?
blueyes said:
I am decrypted and running permissive. All done through kernel editing. Not sure that made a difference or not but did notice any changes beforehand.
Click to expand...
Click to collapse
Sorry to be a bit off-topic but do you plan to document how you did the decrypt and permissive mode anywhere?
I'm guessing one of the unlock properties is what did it. I think something on the phone is recognizing it as a VZW model and is setting one of the properties to 0 and graying it out. I'll do some digging this weekend
dualityim said:
Sorry to be a bit off-topic but do you plan to document how you did the decrypt and permissive mode anywhere?
Click to expand...
Click to collapse
To decrypt you must fastboot format userdata. Flash a kernel the does NOT force encryption. Don't know if any are available so I edited the radial my self , on both kernel and boot-to-root images. To run permissive you simply add androidboot.selinux=permissive. I can upload the edited images later if your unfamiliar with modifications
jjayzx said:
So you added the supercid through the kernel editing?
Click to expand...
Click to collapse
Just added it to the kernel cmdline
blueyes said:
Just added it to the kernel cmdline
Click to expand...
Click to collapse
Thanks. I'll be back in a moment.
Update: It didn't work that way. Trying something a little different.
Update 2: Managed to change cid but still 0 for unlock support and grey. Going to try 1 more thing.
jjayzx said:
Thanks. I'll be back in a moment.
Update: It didn't work that way. Trying something a little different.
Update 2: Managed to change cid but still 0 for unlock support and grey. Going to try 1 more thing.
Click to expand...
Click to collapse
The kernel cmdline has to be edited before flashing. Try adding the persist.sys.oem_unlock... Line. Before run su , then set enforce 0
Why is being able to toggle it a big deal? If your unlocked then why does that matter ?
Rootuser3.0 said:
Why is being able to toggle it a big deal? If your unlocked then why does that matter ?
Click to expand...
Click to collapse
Who said it was a big deal. I clearly stated in op that it annoyed me. If you've got nothing positive to say then don't say anything.
blueyes said:
Who said it was a big deal. I clearly stated in op that it annoyed me. If you've got nothing positive to say then don't say anything.
Click to expand...
Click to collapse
And it's not just about being greyed out. I can now lock my bootloader and unlock it without any exploits. Simply using fastboot. Which sir, I do find to be a nice feature...
blueyes said:
Who said it was a big deal. I clearly stated in op that it annoyed me. If you've got nothing positive to say then don't say anything.
Click to expand...
Click to collapse
I never said you said" it was a big deal" I said that. Go kick rocks
I lost my ability of changing the cid but then i remembered it was after i had did the supercid. So when i put them both back my cid is now changed but my unlock support is still 0. I tried adding persist to default.prop but it didn't take or i did it wrong.
blueyes said:
To decrypt you must fastboot format userdata. Flash a kernel the does NOT force encryption. Don't know if any are available so I edited the radial my self , on both kernel and boot-to-root images. To run permissive you simply add androidboot.selinux=permissive. I can upload the edited images later if your unfamiliar with modifications
Click to expand...
Click to collapse
Did you do the kernel command on the phone? How do I edit default. Prop? I feel like that's where the transformation takes place since it's not editable like the build prop
jjayzx said:
I lost my ability of changing the cid but then i remembered it was after i had did the supercid. So when i put them both back my cid is now changed but my unlock support is still 0. I tried adding persist to default.prop but it didn't take or i did it wrong.
Click to expand...
Click to collapse
Did you add the line persist.sys.oem_unlock_supported=1.
Persists seems to be equivalent to a system override
Rootuser3.0 said:
I never said you said" it was a big deal" I said that. Go kick rocks
Click to expand...
Click to collapse
Go troll somewhere else.
blueyes said:
Did you add the line persist.sys.oem_unlock_supported=1.
Persists seems to be equivalent to a system override
Click to expand...
Click to collapse
Here's my build.prop
https://www.dropbox.com/s/bxgrk7ug66jiuz1/logs.zip?dl=0
cam30era said:
Use Android Image Kitchen > http://forum.xda-developers.com/showthread.php?t=2073775
Click to expand...
Click to collapse
Ok thank you and is this done through terminal or pc
cam30era said:
There are Windows and Linux versions (which I use). There's also a mobile version, but I've never used it.. Read @osm0sis thread. Very helpful.
Click to expand...
Click to collapse
That may be over my head as far as my abilities and I hate to create a new brick