Database Develop

how can i rebuild 'libhtcgeneric-ril.so'?

previous i posted about korean sms.. but no response.
So i can find a way rebuild '.so' file. but i couldnt..
i must add this code in libhtcgeneric-ril.so
msg = new String( inData, "KSC5601" );
'----------------------------------------------------------
void decode_cdma_sms(char *pdu, char *from, char *message, int *is_vm,int *msg_len) {
unsigned int i=1;
int code,length;
strcpy(from,"000000"); // in case something fails
strcpy(message,"UNKNOWN");
if (is_vm)
*is_vm = 0;
while(i*2<strlen(pdu)) {
get_code_and_length(pdu+i*2,&code,&length);
if(code==2) // from
decode_number(pdu+i*2+4,length,from);
if(code==8) // bearer_data
// probably code add. msg = new String( inData, "KSC5601" );
decode_bearer_data(pdu+i*2+4,length,message,is_vm,msg_len); i+=length+2;
}
}
please.. help me.

You need to have an Android source tree to rebuild any components. The xdandroid guide would be the quickest:
http://xdandroid.com/wiki/Getting_the_Source
Any rebuilds of the RIL need to be placed in /lib/froyo/ of the rootfs rather than /system/lib where Android puts it.
BTW htcgeneric-ril.so is C, while the line you want to add is Java. Are you sure thats the right place to patch it?

Thanks Tremere.
Tremere said:
You need to have an Android source tree to rebuild any components. The xdandroid guide would be the quickest:
http://xdandroid.com/wiki/Getting_the_Source
Any rebuilds of the RIL need to be placed in /lib/froyo/ of the rootfs rather than /system/lib where Android puts it.
BTW htcgeneric-ril.so is C, while the line you want to add is Java. Are you sure thats the right place to patch it?
Click to expand...
Click to collapse
i am newbie in C and java.
So i can not figure out this code is wrong.
i am sure that postion of code is right.
but just android source is download and make then compile is complete ?
must compile whole android source but only 'libhtcgeneric-ril.so' ?
that's too difficult to me. i am newbie at linux, C .

Sorry i am totally wrong.
thas is too difficult.
mmmmm......
I am give up..

[Java]Programming Help

So I'm learning Java right now, starting off with simple programs. I need to make a program that displays "1-10" when the user inputs one of the numbers and ""11-20" if it's one of those. I have no idea what lines I'm missing, and I'm sure someone here can help me.
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/
package coinflip2;
/**
*
* @author Class
*/
import java.util.Scanner;
public class Main {
/**
* @param args the command line arguments
*/
public static void main(String[] args)
{
Scanner scan = new Scanner(System.in);
System.out.print("Input a Number from 1-20: ");
int num = scan.nextInt();
while (num < 1 || num > 20)
{
System.out.print ("Not in range. Please enter a number from 1 to 20. ");
{
if (num >= 1 || num <=10)
System.out.print("1-10");
else
System.out.print("11-20");
}
}
}
}
Click to expand...
Click to collapse

im also really new to java im kinda self teaching. when u tried to compile what were ur error messages

Wait, I messed something up. before I posted it I was able to actually input a number. Let me take a look at it and I'll edit the first post.

Ok so I edited the first post.
I get no errors. It prompts me to input a number, and after I do it just says "Build Successful" and if I put in a number less than 1 or greater than 20 it prompts me to input a different number. So the first part I got right, I just need to get the print functions to work in the if/else statements.

EDIT!!! Ok I got it to work. This is now the final version if you want to know, even though it's very simple.
Just an update on what I have so far. Everything works but no matter what number between 1 and 20 I put I still get the same answer.
Also sorry for spamming like that, but I'm sure someone can actually learn from my mistakes .
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/
package coinflip2;
/**
*
* @author Class
*/
import java.util.Scanner;
public class Main {
/**
* @param args the command line arguments
*/
public static void main(String[] args)
{
Scanner scan = new Scanner(System.in);
System.out.print("Input a Number from 1-20: ");
int num = scan.nextInt();
while (num < 1 || num > 20)
{
System.out.print ("Not in range. Please enter a number from 1 to 20. ");
num = scan.nextInt();
}
{
if (num >= 1 && num <=10)
System.out.println("1-10");
else
System.out.println("11-20");
}
}
}
Click to expand...
Click to collapse

Development team V2

Hello everyone,
I want to start again with a development team. After miroslav decided to finish the project on his own, I want to try it again. But this time with a real team Only with people who want to participate, and not just type make. Who wants to join?

miroslav_mm said:
So, I opened your eyes and showed real face our "superstar"!?
Ok! Let's stop this stupid discussion and continuous develop ROM.
At this moment I have main part:
Torchscreen +
BT (BT-calling) +
WiFi (need to test) +
Sensor +
GSM (Waiting call) +
Mobile Data +
Audio +
Vibrate +
HW + 3D ??? (need new kernel or port new 3D kernel driver (kgsl) (in progress))
usb storage ??? (only with special app (native in progress))
Camera ??? (in progress)
Video codec ??? (in progress)
Anyone doing something? Maybe fix some stuff?
Click to expand...
Click to collapse
He just want to clean his topic. Send him a PM.

I understand that but there is still no team. He just made his project open for patches. And I think, personally, a team could help the speed on development of a ROM So please join
Sent from my GT540 using Tapatalk

So join his team , and start patching?

wwenigma said:
So join his team , and start patching?
Click to expand...
Click to collapse
Since when does he have a team? What I know about it, is that he just made some kind of open-source project where you can add your own updates and where he gets no credit.
Sent from my GT540 using Tapatalk

I can help you with Java stuff!

I think miroslav_mm wants to release ICS under name of SWIFT-TEAM, with developer names in credits.... may you ask him about it?
Do not split guys...

Miroslav said that it's only him on the team...so i don't see any team there..if we are more than 1 guy in a team we can get faster a daily ROM for our Phones

rexes13 said:
Miroslav said that it's only him on the team
Click to expand...
Click to collapse
Jep, because PCF+MGP join then leave and jasper580 cant make neccessary steps... ask him. All two, ask him about it.

wwenigma said:
Jep, because PCF+MGP join then leave and jasper580 cant make neccessary steps... ask him. All two, ask him about it.
Click to expand...
Click to collapse
I can make nesseccary steps if I want, but I don't want to. I want to start cleaned up. That's why I created this topic. So:
If you want to join: welcome.
If you don't want to: stop spamming
@rexes13 Welcome to the team!
Sent from my GT540 using Tapatalk

Good news.
Yesterday I successfully ported 3d kernel driver (kgsl) from 35, so now we have full functionality kernel with OpenGL ES-CM 1.1.
So HW, 3D and other stuff with support OpenGL working, not excellent but working, need improve source code Surfaceflinger and HardwareDisplay.
Maybe next weak I will make new thread and publish first public test version, but all development moments we can discus here.
Before I need redownload all sources CM9 again. Yesterday I had the same error like in wwenigma and aaa801
Code:
target thumb C: libhardware_legacy <= hardware/libhardware_legacy/power/power.c
arm-linux-androideabi-gcc: ": No such file or directory
<command-line>: warning: missing terminating " character
and I dont know WTF, so delete all source tree. Maybe today will try download again and build again.

hell yeah! im just another non-dev member LOL sry

Need help!
Look on code:
Code:
//static int32_t msm_tscal_scaler = 65536;
static int32_t msm_tscal_xscale = 70046;
static int32_t msm_tscal_xoffset = -4191987;
static int32_t msm_tscal_yscale = 71735;
static int32_t msm_tscal_yoffset = -3004437;
this pointers for torch 320*240. So when I using that I need tap on 2mm high on icon for open something. This pointer need for screen calibration. Need find right pointer.
I can't find a logic in this numbers.

miroslav_mm said:
Need help!
Look on code:
Code:
//static int32_t msm_tscal_scaler = 65536;
static int32_t msm_tscal_xscale = 70046;
static int32_t msm_tscal_xoffset = -4191987;
static int32_t msm_tscal_yscale = 71735;
static int32_t msm_tscal_yoffset = -3004437;
this pointers for torch 320*240. So when I using that I need tap on 2mm high on icon for open something. This pointer need for screen calibration. Need find right pointer.
I can't find a logic in this numbers.
Click to expand...
Click to collapse
The offsets appear to have a ~4:3 ratio. It doesn't make sense though why it's x:y=4:3, and not the other way around, since the screen is usually 3:4(e.g. 320x480 or 240x320). Also, considering our screen is 320x480, which is a ratio of 1,5 and not 1,(3), I think those would be totally wrong for our phone. Maybe try to modify one of the two to match 1,5 ratio. E.g. make xoffset=-4506655. I don't know. :/

Please discuss development on your page. I want to make a dev team here
Sent from my GT540 using Tapatalk

deleted
10 character

This numbers working with this java code together:
]
Code:
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
// Read current values
final int xoffset = (readValue("xoffset")*240+480)/960;
final int yoffset = (readValue("yoffset")*320+460)/920;
final int xscale = readValue("xscale");
final int yscale = readValue("yscale");
view = new View(this) {
private int step = 1;
private int rawx1;
private int rawy1;
private int rawx2;
private int rawy2;
private void writeValue(String parameter, int value) {
try {
FileOutputStream fos = new FileOutputStream(new File("/sys/module/msm_touch/parameters/tscal_" + parameter));
fos.write(String.valueOf(value).getBytes());
fos.flush();
fos.getFD().sync();
fos.close();
} catch (FileNotFoundException e) {
e.printStackTrace();
} catch (IOException e) {
e.printStackTrace();
}
}
@Override
public boolean onTouchEvent(MotionEvent ev) {
if (ev.getAction() != MotionEvent.ACTION_UP)
return true;
if(step==1) {
rawx1 = ((int)ev.getRawX()*65536-xoffset+32768)/xscale;
rawy1 = ((int)ev.getRawY()*65536-yoffset+32768)/yscale;
if(rawx1<100 && rawy1<100)
step = 2;
} else if(step==2) {
rawx2 = ((int)ev.getRawX()*65536-xoffset+32768)/xscale;
rawy2 = ((int)ev.getRawY()*65536-yoffset+32768)/yscale;
if(rawx2>140 && rawy2>220)
step = 3;
} else {
int distx = rawx2 - rawx1;
int new_xscale = (140*65536 + distx/2)/distx;
int disty = rawy2 - rawy1;
int new_yscale = (220*65536 + disty/2)/disty;
int new_xoffset = 1;
new_xoffset += 50*65536-rawx1*new_xscale;
new_xoffset += 190*65536-rawx2*new_xscale;
new_xoffset /= 2;
new_xoffset = (new_xoffset*960+120)/240;
int new_yoffset = 1;
new_yoffset += 50*65536-rawy1*new_yscale;
new_yoffset += 270*65536-rawy2*new_yscale;
new_yoffset /= 2;
new_yoffset = (new_yoffset*920+160)/320;
// Pass new calibration to kernel
writeValue("xoffset", new_xoffset);
writeValue("yoffset", new_yoffset);
writeValue("xscale", new_xscale);
writeValue("yscale", new_yscale);
// Save calibraiton data to /data/system/pointercal
StringBuilder sb = new StringBuilder();
sb.append(new_xscale);
sb.append(" ");
sb.append(0);
sb.append(" ");
sb.append(new_xoffset);
sb.append(" ");
sb.append(0);
sb.append(" ");
sb.append(new_yscale);
sb.append(" ");
sb.append(new_yoffset);
sb.append(" ");
sb.append(65536);
App + ui input framework + kernel working together.
App - creation poinercal
ui input framework - reading pointercal send correct info to kernel
kernel touch driver - doing move.

Öhm, the touchscreen driver use a virtual square (320*320) to detect touch, stretched to a rectangle(320*480)?
mod: about calibration, http://code.google.com/p/openeve/issues/detail?id=91

jasper580 said:
Please discuss development on your page. I want to make a dev team here
Click to expand...
Click to collapse
I cant understand you! What do you mean? Do you wanna make new dev team? Working on my sources but without me?

I exactly want to ask that. Maybe he start from scratch, his github is near empty.

[EXPERIMENTAL][androidarmv6/android_kernel_lge_msm7x27-3.0.x]WiFi Voltage Reduction

Experimental test of wifi voltage reduction, and activate commented out msm-7627 regulator for ldo12 (wlan)
Read: EXPERIMENTAL.
It has been flashed to one thunderg p500 which seems to still be completely functional (which I don't own one of unfortunately, but I've been testing this patch on the thunderc with basically the same kernel for a while with no ill effects.)
Use at your own risk, of course, but this is an experiment to try to reduce the wifi power drain with the 3.0 kernel. Needs testers to give opinions or evaluation.
If it actually can be verified to cut power consumption noticeably, I'd like to send it upstream, but first it needs tested to be more than a placebo.
For androidarmv6 kitkat (muklsoni's or jenkins nightly)
dunno how it'll get along with other kitkat ROMS. Doubt it'll work on anything under Jellybean.
source:
https://github.com/androidarmv6/android_kernel_lge_msm7x27-3.0.x branch cm-11.0
with this patch
Code:
Subject: [PATCH] wifi regulator and voltage reduction test
---
arch/arm/mach-msm/board-msm7627-regulator.c | 3 ++-
arch/arm/mach-msm/lge/board-thunderg-mmc.c | 27 ++++++++++++++-------------
2 files changed, 16 insertions(+), 14 deletions(-)
diff --git a/arch/arm/mach-msm/board-msm7627-regulator.c b/arch/arm/mach-msm/board-msm7627-regulator.c
index 6ab2977..4540e6e 100644
--- a/arch/arm/mach-msm/board-msm7627-regulator.c
+++ b/arch/arm/mach-msm/board-msm7627-regulator.c
@@ -226,7 +226,8 @@ static struct proccomm_regulator_info msm7627_pcom_vreg_info[] = {
PCOM_VREG_LDO(ldo09, 8, NULL, 1800000, 1800000, 0, -1, 0, 0, 0, 0),
PCOM_VREG_LDO(ldo10, 7, NULL, 2600000, 2600000, 0, -1, 0, 0, 0, 0),
PCOM_VREG_LDO(ldo11, 21, NULL, 2800000, 2800000, 0, -1, 0, 0, 0, 0),
- PCOM_VREG_LDO(ldo12, 11, NULL, 1800000, 1800000, 0, -1, 0, 0, 0, 0),
+// PCOM_VREG_LDO(ldo12, 11, NULL, 1800000, 1800000, 0, -1, 0, 0, 0, 0),
+ PCOM_VREG_LDO(ldo12, 11, NULL, 1800000, 2400000, 0, -1, 0, 0, 0, 0),
PCOM_VREG_LDO(ldo13, 15, NULL, 2850000, 3000000, 0, -1, 0, 0, 0, 0),
PCOM_VREG_LDO(ldo14, 24, NULL, 2700000, 2700000, 0, -1, 0, 0, 0, 0),
PCOM_VREG_LDO(ldo15, 23, NULL, 2800000, 2800000, 0, -1, 0, 0, 0, 0),
diff --git a/arch/arm/mach-msm/lge/board-thunderg-mmc.c b/arch/arm/mach-msm/lge/board-thunderg-mmc.c
index 056bcfa..20f9575 100644
--- a/arch/arm/mach-msm/lge/board-thunderg-mmc.c
+++ b/arch/arm/mach-msm/lge/board-thunderg-mmc.c
@@ -181,8 +181,8 @@ static unsigned sdcc_cfg_data[][6] = {
static unsigned long vreg_sts, gpio_sts;
static unsigned mpp_mmc = 2;
-static struct vreg *vreg_mmc;
-//static struct regulator *vreg_mmc;
+//static struct vreg *vreg_mmc;
+static struct regulator *vreg_mmc;
static void msm_sdcc_setup_gpio(int dev_id, unsigned int enable)
{
@@ -226,8 +226,8 @@ static uint32_t msm_sdcc_setup_power(struct device *dv, unsigned int vdd)
MPP_CFG(MPP_DLOGIC_LVL_MSMP,
MPP_DLOGIC_OUT_CTRL_LOW));
} else
- rc = vreg_disable(vreg_mmc);
-// rc = regulator_disable(vreg_mmc);
+// rc = vreg_disable(vreg_mmc);
+ rc = regulator_disable(vreg_mmc);
if (rc)
printk(KERN_ERR "%s: return val: %d \n",
__func__, rc);
@@ -242,15 +242,16 @@ static uint32_t msm_sdcc_setup_power(struct device *dv, unsigned int vdd)
MPP_DLOGIC_OUT_CTRL_HIGH));
} else {
#ifdef CONFIG_MMC_MSM_CARD_HW_DETECTION
- rc = vreg_set_level(vreg_mmc, VREG_SD_LEVEL);
-// rc = regulator_set_voltage(vreg_mmc, VREG_SD_LEVEL*1000, VREG_SD_LEVEL*1000);
+// rc = vreg_set_level(vreg_mmc, VREG_SD_LEVEL);
+ rc = regulator_set_voltage(vreg_mmc, VREG_SD_LEVEL*1000, VREG_SD_LEVEL*1000);
#else
- rc = vreg_set_level(vreg_mmc, 2850);
+// rc = vreg_set_level(vreg_mmc, 2850);
// rc = regulator_set_voltage(vreg_mmc, 2850000, 2850000);
+ rc = regulator_set_voltage(vreg_mmc, 1800000, 2400000);
#endif
if (!rc)
- rc = vreg_enable(vreg_mmc);
-// rc = regulator_enable(vreg_mmc);
+// rc = vreg_enable(vreg_mmc);
+ rc = regulator_enable(vreg_mmc);
}
if (rc)
printk(KERN_ERR "%s: return val: %d \n",
@@ -313,11 +314,11 @@ static struct mmc_platform_data msm7x2x_sdc1_data = {
static void __init msm7x2x_init_mmc(void)
{
if (!machine_is_msm7x25_ffa() && !machine_is_msm7x27_ffa()) {
- vreg_mmc = vreg_get(NULL, "wlan");
-// vreg_mmc = regulator_get(NULL, "wlan");
+// vreg_mmc = vreg_get(NULL, "wlan");
+ vreg_mmc = regulator_get(NULL, "wlan");
if (IS_ERR(vreg_mmc)) {
-// printk(KERN_ERR "%s: regulator get failed (%ld)\n",
- printk(KERN_ERR "%s: vreg get failed (%ld)\n",
+ printk(KERN_ERR "%s: regulator get failed (%ld)\n",
+// printk(KERN_ERR "%s: vreg get failed (%ld)\n",
__func__, PTR_ERR(vreg_mmc));
return;
}
--
1.7.9.5
This enables the regulator instead of vreg for ldo12 (wlan) like the other board devices.
It also reduces wlan voltage from 2.85V to 2.4V max and allows a low setting of 1.8V instead of the original off/2.85V mode
built with custom ct-ng linaro 4.7 armv6k toolchain branch 4.7.4
(the few v6k instructions in the toolchain should be no issue for your msm7227, especially compared to the armv7 ones in the 4.8 and newer toolchains I've tried.)
Download link in 2nd post.

Download here
Feedback appreciated, and the test will go nowhere without your information.

iwconfig can be placed on xbin, used to set lower txpower. Tasker script to redo this whenever WIFI comes on.

Dovidhalevi said:
iwconfig can be placed on xbin, used to set lower txpower. Tasker script to redo this whenever WIFI comes on.
Click to expand...
Click to collapse
Nice to have another way to reduce drain. Thanks. Maybe that can be incorporated into ROM without too much hassle.
My thought was that many users need something transparent that you install once and it's done, or even built in, and that wifi drain on this kernel has been a common complaint across both thunderg and thunderc builds for a long time.
I like to play around with new things. Don't know about the Optimus One, but an activatable Optimus V is now down to under $25 shipped, so I am not worried about messing mine up anymore. Trying experiments with low level parameters, like tweaking voltages, is the best way I know of to find the usable lower limits of things so that function is maximized.
If this type of thing can fix it...
Also, Broadcom specs say the voltage can go even lower, down to 2.3V. I can't find good data on its low power mode. But I don't know why it's set way up to 2.85V on the thunder* board (Same with stock 2.6.35,) when it definitely still works at 2.4V.

bigsupersquid said:
Nice to have another way to reduce drain. Thanks. Maybe that can be incorporated into ROM without too much hassle.
My thought was that many users need something transparent that you install once and it's done, or even built in, and that wifi drain on this kernel has been a common complaint across both thunderg and thunderc builds for a long time.
I like to play around with new things. Don't know about the Optimus One, but an activatable Optimus V is now down to under $25 shipped, so I am not worried about messing mine up anymore. Trying experiments with low level parameters, like tweaking voltages, is the best way I know of to find the usable lower limits of things so that function is maximized.
If this type of thing can fix it...
Also, Broadcom specs say the voltage can go even lower, down to 2.3V. I can't find good data on its low power mode. But I don't know why it's set way up to 2.85V on the thunder* board (Same with stock 2.6.35,) when it definitely still works at 2.4V.
Click to expand...
Click to collapse
iwconfig is easily pushed, could/should come with the ROM.
The ROM's startup would set the default txpower to say, 11 instead of 32. That would be transparent, no need to think about it.
I need a startup script and a tasker script because every time WIFI comes on, the txpower gets back to 32.
How much battery I really save by all this, I really cannot document (but a little less EM radiation around cannot hurt).
With iwconfig, I can reset things should I so desire. I am not bound by the kernel to a given voltage or power. BTW, sweetnsour's kernels (dont use them now, out-of-date) had lower CPU voltage to save battery. Did notice.

Dovidhalevi said:
iwconfig is easily pushed, could/should come with the ROM.
The ROM's startup would set the default txpower to say, 11 instead of 32. That would be transparent, no need to think about it.
I need a startup script and a tasker script because every time WIFI comes on, the txpower gets back to 32.
How much battery I really save by all this, I really cannot document (but a little less EM radiation around cannot hurt).
With iwconfig, I can reset things should I so desire. I am not bound by the kernel to a given voltage or power. BTW, sweetnsour's kernels (dont use them now, out-of-date) had lower CPU voltage to save battery. Did notice.
Click to expand...
Click to collapse
I'll test the bigsupersquid patch, i've a 2nd p500 now i think it's simple apply a patch (also in jenkins repo) and then forget it.
no 3rd app needed (tasker) = space for other apps
1st test on os2sd:
flashed as is, boot loop (i think is the different mount point of the /system folder, i'll put files directly in the rom and then reflash the entire rom)
meanwhile
2nd test with rhar**** omega rom: with bigsupersquid patch 5h 30 @ 25%, probably 6h 30 @10%
i've to keep my 2nd p500 in aereo, because i haven't a 2nd sim. without a sim or aereo mode on the rom lag a lot

bigsupersquid said:
Download here
Feedback appreciated, and the test will go nowhere without your information.
Click to expand...
Click to collapse
Does Spirit radio free work on this kernel.

samade123 said:
Does Spirit radio free work on this kernel.
Click to expand...
Click to collapse
dunno, no p500 to test with.
if it works with the androidarmv6 chocolate+perf kernel, it should. This is that plus the patch.
fm doesn't work at all on the thunderc. never has.

bigsupersquid said:
dunno, no p500 to test with.
if it works with the androidarmv6 chocolate+perf kernel, it should. This is that plus the patch.
fm doesn't work at all on the thunderc. never has.
Click to expand...
Click to collapse
Spirit radio does work on Omni rom

samade123 said:
Spirit radio does work on Omni rom
Click to expand...
Click to collapse
and from what I've read it doesn't on cm11.
make a backup to try the kernel in omni.

bigsupersquid said:
and from what I've read it doesn't on cm11.
make a backup to try the kernel in omni.
Click to expand...
Click to collapse
I have already tried it on Omni and Spirit Free doesn't work.

samade123 said:
I have already tried it on Omni and Spirit Free doesn't work.
Click to expand...
Click to collapse
please can you confirm that in omni (7.1 or pre8) with wifi connected&aereo on, the battery endurance (100%->0%) is ~ 8,5h

I can try to build a kernel for omni too using the patch.
BTW, you have changed the voltage according to patch, right? Isn't there any other way to implement the older drivers in the newer kernel?
Sent from my Xperia M using XDA Premium 4 mobile app

rhar**** said:
I can try to build a kernel for omni too using the patch.
BTW, you have changed the voltage according to patch, right? Isn't there any other way to implement the older drivers in the newer kernel?
Sent from my Xperia M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the patch cuts voltage and switches wlan to regulator instead of vreg.
the 2.6 kernel uses the same voltage as before my patch.
i hadn't tried to cram the old drivers into the new kernel, and other than changing txpower like suggested earlier, this patch was all i could think of to cut wlan power usage.

xdema said:
please can you confirm that in omni (7.1 or pre8) with wifi connected&aereo on, the battery endurance (100%->0%) is ~ 8,5h
Click to expand...
Click to collapse
I think your getting confused between Omni rom and Omega rom(A CM11 variation). And sorry I can't because my primary phone is going for repair so I don't want to mess with this phone till my other gets repaired

bigsupersquid said:
the patch cuts voltage and switches wlan to regulator instead of vreg.
the 2.6 kernel uses the same voltage as before my patch.
i hadn't tried to cram the old drivers into the new kernel, and other than changing txpower like suggested earlier, this patch was all i could think of to cut wlan power usage.
Click to expand...
Click to collapse
Ok. I get it. Nice work. Keep it up!
samade123 said:
I think your getting confused between Omni rom and Omega rom(A CM11 variation). And sorry I can't because my primary phone is going for repair so I don't want to mess with this phone till my other gets repaired
Click to expand...
Click to collapse
Well, Omega ROM is omni based, and not cm11. Previously it was CM based but beta5 onwards, its Omni based. And that's the reason why I'll even try to build it for omni.
Sent from my LG-P500 using XDA Premium 4 mobile app

rhar**** said:
Ok. I get it. Nice work. Keep it up!
Well, Omega ROM is omni based, and not cm11. Previously it was CM based but beta5 onwards, its Omni based. And that's the reason why I'll even try to build it for omni.
Sent from my LG-P500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh ok fair enough then it would be good to get this on Omega then the battery will last longer.

bigsupersquid said:
the patch cuts voltage and switches wlan to regulator instead of vreg.
the 2.6 kernel uses the same voltage as before my patch.
i hadn't tried to cram the old drivers into the new kernel, and other than changing txpower like suggested earlier, this patch was all i could think of to cut wlan power usage.
Click to expand...
Click to collapse
Please, could you make a patch for the os2sd roms?
i tried to apply the patch to an os2sd rom (hardlight's KK) but the result was a bootloop after the LG logo
however it's ok on the omega 7.1 and mukulsoni's KK

xdema said:
Please, could you make a patch for the os2sd roms?
i tried to apply the patch to an os2sd rom (hardlight's KK) but the result was a bootloop after the LG logo
however it's ok on the omega 7.1 and mukulsoni's KK
Click to expand...
Click to collapse
it's too old for the TLS-enabled ROMs and needs rebuilt for that.
The rebuild won't work on the ROMs that the current version works on.
plus the comments in HardLight's thread indicate the battery holds up pretty well in his version anyway...
you can apply my patch to the current androidarmv6source and build a kernel that should work with the TLS-enabled ROMs.

Spirit free
After a second attempt of flashing this patch to Omni, It seems Spirit free works well. Brilliant patch. :good:

[HELP] Some questions about building errors!

Hey all, what's up?
I got a problem, and I'm going crazy xD
I've successfully done a repo sync of AOSPA Legacy and successfully downloaded:
-Device Tree: https://github.com/CyanogenMod/android_device_lge_w7
-Kernel: https://github.com/CyanogenMod/android_kernel_lge_msm8226
-Vendor: https://github.com/Quarx2k/proprietary_vendor_lge
Now I'm following this guide: http://forum.xda-developers.com/showthread.php?t=1863547
In a step it tells me to extract "proprietary-files.sh" from my device folder.
Our "proprietary-files.sh" is called "setup-makefiles.sh"?
This is the first question.
The second question is that I must follow this tip.
"# Create /manifest/<device>.adds:
I'll give you two examples of .adds, to show the general extent of variation between devices:
For i9300:
Code:
Code:
[
{
"remote": "github",
"account": "CyanogenMod",
"repository": "android_frameworks_av",
"target_path": "frameworks/av",
"revision": "cm-10.1"
},
{
"remote": "github",
"account": "CyanogenMod",
"repository": "android_frameworks_native",
"target_path": "frameworks/native",
"revision": "cm-10.1"
Where I can find this kind of repos? D: I tried Googling but with no luck.
3rd question: Where I can find also this kind of things? >_<
"# Create /manifest/<device>.removes:
For i9300:
Code:
Code:
{
"name": "platform/frameworks/av",
"path": "frameworks/av"
},
{
"name": "ParanoidAndroid/android_frameworks_native",
"path": "frameworks/native"
},
{
"name": "platform/hardware/libhardware",
"path": "hardware/libhardware"
},
{
"name": "platform/hardware/libhardware_legacy",
"path": "hardware/libhardware_legacy"
},
{
"name": "device/common",
"path": "device/common"
},
{
"name": "ParanoidAndroid/android_frameworks_opt_telephony",
"path": "frameworks/opt/telephony"
}
]
Help me out
Last question: When I try to build..After 5 min the terminal gives me this.
Code:
"No private recovery resources for TARGET_DEVICE w7
make: *** Nessuna regola per generare l'obiettivo "external/chromium_org/v8/tools/gyp/generate_trig_table.host.linux-arm.mk". Arresto."
And also before this errors, there are other errors like:
Code:
"external/chromium_org/v8/tools/gyp/generate_trig_table.host.linux-arm.mk: File o directory non esistente
find: "phone/java": File o directory non esistente
find: "phone/java": File o directory non esistente
find: "dummy": File o directory non esistente"
If anyone can help me, please answer!
Thank you!!

You don't need to run that command, the proprietary_vendor_lge folder that you added to the manifest is what houses all of those files. Also, you will need to do quite a bit of file editing to get a cm device tree to build properly on AOSP. With that being said, there are much better/easier guides out there to set up your build environment. I'll find a couple and post them here for you to check out

CaptivateKing said:
You don't need to run that command, the proprietary_vendor_lge folder that you added to the manifest is what houses all of those files. Also, you will need to do quite a bit of file editing to get a cm device tree to build properly on AOSP. With that being said, there are much better/easier guides out there to set up your build environment. I'll find a couple and post them here for you to check out
Click to expand...
Click to collapse
I don't want to build a AOSP. I wanna build an AOSPA/Paranoid
Anyways thank you for your answer.

SlimShady's said:
I don't want to build a AOSP. I wanna build an AOSPA/Paranoid
Anyways thank you for your answer.
Click to expand...
Click to collapse
I meant to type AOSPA, but the same goes for building anything that isn't cm, or cm based. You will have to edit a few make files for it to compile correctly with a cm device tree

CaptivateKing said:
I meant to type AOSPA, but the same goes for building anything that isn't cm, or cm based. You will have to edit a few make files for it to compile correctly with a cm device tree
Click to expand...
Click to collapse
And how can I do it?