So I found the following 2 lines when running getprop in a shell, which point to the Eco mode that may or may not be left inside the source code since the Optimus G:
[ro.lge.ps.eco.pv]: [0]
[ro.lge.ps.freqlowlimit]: [1036800]
On the G it seems ro.lge.ps.eco.pv is set to 322, whatever that means. Anyone brave enough to keep digging for clues?
Related
Hi there,
I recently bought the wonderful Samsung Note 10.1 2014 and am looking to add loop device support to the kernel for the sake of booting *nix using the good old VLC trick. Even though I'm a software engineer and no stranger to Linux (or fstab), I'm very green when it comes to Android development.
When trying to run the bootup script, I recieve "mknod /dev/block/loop255 b 7 0". I.E my kernel doesn't support loopback devices.
I have extracted the kernel contents (ramdisk and init img) but was wondering whether anyone can give me a shove in the right direction when it comes to setting up the device.
So far, after a brief investigation, I have found the fstab.goldfish file which strikes me as looking just as I'd expect to see it on a normal box. Can anyone provide a quick shove in the right direction for knowledge (preferred) or even has a snippet from an existing unpacked kernel I may "borrow", Google was not my friend in such pursuit.
--Edit--
Looking through the build.prop, would simply disabling selinux give root permission to create a loop device? This again boils down to my warped inherent knowledge of Linux in general, sorry if it seems a poor question.
--Update--
I guess if the kernel wasn't compiled with support (as it appears it wasn't) there is no hope of modifying the stock ROM to achieve my goal? On the Samsung OSC, they have SM-P605_HK SM-P605_HK_JB_Opensource.zip so, I'm taking a look in there and will keep you posted just in case anyone is the least bit interested.
--Resolution--
I guess this thread can be ignored now, I'm pulling the config from my tablet, changing the kernel compile config and will test it out tomorrow. If in doubt, compile
symbal said:
Hi there,
I recently bought the wonderful Samsung Note 10.1 2014 and am looking to add loop device support to the kernel for the sake of booting *nix using the good old VLC trick. Even though I'm a software engineer and no stranger to Linux (or fstab), I'm very green when it comes to Android development.
When trying to run the bootup script, I recieve "mknod /dev/block/loop255 b 7 0". I.E my kernel doesn't support loopback devices.
I have extracted the kernel contents (ramdisk and init img) but was wondering whether anyone can give me a shove in the right direction when it comes to setting up the device.
So far, after a brief investigation, I have found the fstab.goldfish file which strikes me as looking just as I'd expect to see it on a normal box. Can anyone provide a quick shove in the right direction for knowledge (preferred) or even has a snippet from an existing unpacked kernel I may "borrow", Google was not my friend in such pursuit.
--Edit--
Looking through the build.prop, would simply disabling selinux give root permission to create a loop device? This again boils down to my warped inherent knowledge of Linux in general, sorry if it seems a poor question.
--Update--
I guess if the kernel wasn't compiled with support (as it appears it wasn't) there is no hope of modifying the stock ROM to achieve my goal? On the Samsung OSC, they have SM-P605_HK SM-P605_HK_JB_Opensource.zip so, I'm taking a look in there and will keep you posted just in case anyone is the least bit interested.
--Resolution--
I guess this thread can be ignored now, I'm pulling the config from my tablet, changing the kernel compile config and will test it out tomorrow. If in doubt, compile
Click to expand...
Click to collapse
I believe "CONFIG_BLK_DEV_LOOP" is the config option you are looking for.
Posted this in the wrong place, i guess this is the right
Hi everyone,
I have a 10.1'' chinese tablet with a rk3066 chip, suddenly the firmware got damagend, there is no way to find the original, i've tried with over 100 different firmwares from here or rockchipfirmware, nothing worked, but there is 1 version that barely works (PlayerMomo12 release 3) but the screen is inverted in both axis (X and Y), i've tried different methods to fix it, with apks, with usb debugging, and nothing worked, the apps just doesn't works, even one of them dissapeared and i was unable to install it again, using my laptop doesnt works because the directory that should mount doesn't exist, i don't know why but i've tried all the methods, even mounting with a terminal inside the tablet (you can imagine how hard was writting with the screen like a mirror), then i thought the only solution was using the kitchen to modify the file script.bin, but again, a lot of problems, i couldn't open the image, found this thread:
http://forum.xda-developers.com/show...33246&page=555
-------------------------------------
Originally Posted by biglcny
just running sysrw and sysro would return this:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
rather than no output as usual. I believe there may be another version of mount that takes different parameters. When a rom is flashed and you connect to it with adb shell there is a version of mount in /system/bin that is different and accepts options in a different format.
simply typing running mount at the command line or in a shell script uses that one instead of the busybox one.
dr.notor replied:
Well, the above is an example of totally screwed up mount binary, dunno which phone and ROM you are using but the guy who produced the above would deserve a bit hit with a cluebat into their head.
If you have similar broken crap, simply edit the scripts to call busybox mount and not mount.
-------------------------------------
well, this is the point (after a lot of days working on this) when i give up, this tablet was bought in China and the company (scope) doesn't sell it anymore, and they don't reply the emails, even the webpage is half empty, this is the point when i ask, if someone can help me sending a working kernel based on this rom (PlayerMomo12 release 3) or the firmware with the script.bin modified to invert both axis, if no one can, then it's the moment to smash the tablet with a giant hammer and send it back to China
i could bought 2 galaxy tab 4 if i wasn't wasted so much time on this
here is the firmware if someone wanna to try
http://www.rockchipfirmware.com/cont...-tnt-release-3
hi yall, i'm in need of some help here. recently i've ran into a wall and i'm im unable to fix it, i've spent countless hours trying to work around it and or even proceed with anything beyond basic functions of my chromebook (device info at bottom of thread.) well about 2 weeks ago i went to terminal with
Code:
ctrl-alt-t
then typing
Code:
shell
and after tpying
Code:
Sudo help
to get a general idea of some other commands as i'm trying to build my on console. but i was hit with
[email protected] / $ sudo help
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
Password:
Click to expand...
Click to collapse
now I have tried every user password ever put on this device, case sensitive also several others like
chromeos-setdevpasswd, facepunch, toor, root, ENTER, Passwd,Password,
Click to expand...
Click to collapse
any and all variation possible over countless hours researching till my eyes bled trying to figure out how to get back sudo, i mean countless upon countless hours.. I can't do anything with out this access,please help its affecting my personal business, and my income, i can't code i can't do anything please, idc if i have to remounting my whole system and anything short of buying a new motherboard. something ive power washed over 100 times.
device info
Google Chrome 48.0.2564.8 (Official Build) dev (32-bit)
Revision 0
Platform 7647.1.0 (Official Build) dev-channel daisy
Blink 537.36 (@0)
JavaScript V8 4.8.271.3
Flash 20.0.0.203-r1
User Agent Mozilla/5.0 (X11; CrOS armv7l 7647.1.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.8 Safari/537.36
Click to expand...
Click to collapse
Hi, I have a problem changing my device model from "ONE E1003" to "X" on Nougat.
Some ROMs like AOSIP,Tesla,Citrus can just simply add/edit "ro.product.model=X" on build.prop and the device name will change just like that.
But on another ROMs like RR,AICP,AEX(my current rom), editing like that won't change the device model. I also tried to use adb command, (adb shell settings put global device_name "X") but it still won't change anything.
Actually it is not really important but seeing my device name on certain apps and in the google play as "OnePlus ONE E1003" sometime really annoy me
If anyone have a better solution, feel free to share with me. Thank you.
Recently, I had to repair a Yoga Tab 3 Plus and needed a way to test all of the Components like Sensors, Battery, Speakers...
On most phones, there are secret codes that can be entered in the Dialer App to launch a so called Factory Test Menu, where you can run all sorts of tests on the internal components.
If you have the Wifi-only version of the Tablet, you dont have the Dialer App so you need to launch the Menu otherwise.
After a bit of poking around, here's what I came up with:
At first, you will need to connect your tablet to a PC via USB and get ADB working. Please refer to the following XDA guide on how to do so:
How to Install ADB on Windows, macOS, and Linux
Once all of that is set up, you will need to run the adb shell with the following command:
adb shell
If everything worked, you should see something like this:
YT-X703F:/ $
Now you can type in the following command to launch the menu:
am start -n com.tools.cit/.HomeActivity
Be aware that all of the options are written in Chinese so you have to use another phone to translate it, or use the following translation:
Spoiler: Translation
显示Display MenuLCDLCD透明度Transparency背光Backlight双色灯Dual color light闪光灯Flash light触屏Touch screen
电源Power Menu电池Battery
插槽Slot MenuSIM卡SIM cardSD卡SD card
录音Audio Menu录音Microphone耳机Earphone震动Vibrate顶部扬声器Top Speaker底部扬声器Bottom Speaker
摄像头Camera Menu前置摄像头Front Camera后置摄像头Rear Camera
传感器Sensor Menu距离传感器Distance sensor罗盘传感器Compass sensor加速度传感器Acceleration sensor光传感器Light sensors霍尔感应器Hall sensorsSar感应器SAR sensor
按键Button Menu按键Pushbuttons
连接Connections Menu无线网Wifi蓝牙Bluetooth
网络Network MenuGPS定位GPS Location收音机Radio
版本Versions Menu软件版本Software Versions
RunInRunIn MenuRunInRunIn
This guide works for the Lenovo Yoga Tab 3 Plus (Model: YT-X703F) but might work for other Qualcomm based Lenovo Tablets as well (not tested).
Note: The app can apparently also be launched with the secret code *#*#7388#*#* but this did not work out for me