yashsingh1/xdaforums huggingface dataset:
[HD2 General] henv:
Is it possible that the exchange admins put a policy to your telephone that its not possible to install software. ,Maybe that is the problem. Then when you delete email, also delete this policy and then its possible to install progs
[HD2 General] gnash.s:
It looks like it, before & after deleting the exchange sync it asks me to restart. after deleting the problem goes away. Is there anyway to change exchange's behaviour/policy?

The main problem is not just the installation, even the installed apps don't open anymore. Like the "Arkswtich" task manager which I use all the time or any unsigned apps I think. Opera works fine.

could you tell me, what/how I should ask my admins?
[HD2 General] gnash.s:
Hello All,

It looks like the policies are being updated and I cannot run or install the any unsigned app. I tried to install the cabs to "Remove app lock, unsigned app, etc..", but I can't seem to install these cabs too. Now, I can't even open the registry and update the policies key manually as I can't open a regsitry editor app.

I tried the registry editor from PC (CeRegEdit) and it won't let me update from that too. I totally stuck with this problem now.

Is there way to sign an app (cab file) or make it trusted?

Thanks
[HD2 General] gnash.s:
I'll continue to update this thread as no one else seem to have this problem.

I used "msigner.cab" to sign couple of cab files and tried to install and it still failed saying "untrusted...". So, I spoke to my admins, those guys plainly said they don't support windows mobile. Now, I don't have an option.

I wonder, why microsoft would enforce a policy on a wm6.5 devices?

Next step.. I reflashed again, installed all the cabs I needed and setup my device. this time, I'm hoping that I don't have to reboot (I know it's tough ) after syncing up with exchange. I'll sync only the emails (in Exchange) and others through the pc (contacts, tasks, calendar).
[HD2 General] gnash.s:
Finally, I installed all the reg editors before connecting to exchange. Then I synced only the emails with the exchange server and before rebooting the phone, I used the reg editor to change the key (HKLM\Security\Policies\Policy) values as mentioned in other forums (sdkcerts) to 0. Now it looks like its permanent and not changing even after the reboot!

Thanks
[HD2 General] aash05:
What Values do we change??? Policies and Policy are two different folders
[HD2 General] neitin:
Yes I too need to know, I am suffering with the same problem :mad:

Thanks in advance

Update I think http://blogs.microsoft.co.il/blogs/...curity-policy-for-windows-mobile-devices.aspx can help in resolving, never tried it though
[HD2 General] gnash.s:
sorry, it is in the "HKLM\Security\Policies\Policies" folder.

I changed the following keys..

00001005 to 1

00001006 to 1

Let me know if it doesn't work, I can export and email you the policies key from the registry.
[G1 Android Development] zachattack052:
Sounds sweet, but is it real this time? however if it is, its going in my new kernel
[G1 Android Development] jubeh:
It had already been established before that this won't work on Dream because the chip's PLL is set to a clock where the maximum stable speed you can get is 528 Mhz and the next, acceptable speed (not placebo like the one tried before) crashes the phone.
[G1 Android Development] jad011:
i thought the PLL was written in software?
[G1 Android Development] xaueious:
I was doubting this too, but there's indication that it is different this time.

This is what this patch does differently.

Someone try this!
[G1 Android Development] zachattack052:
not bricking my phone today (:
[G1 Android Development] xaueious:
Dude you can't brick your phone with a patched kernel like this.

No devs willing to try it? The patch might be quick one. Just take a look.

The diff might not apply as is since it was made for CDMA Hero. In any case, I'm not worried because I'm sure that we will figure something out.
[G1 Android Development] jubeh:
http://xdaforums.com/showthread.php?t=557863

http://xdaforums.com/showthread.php?t=631810

http://xdaforums.com/showthread.php?t=630236

it's been tried, turned out to be duds
[G1 Android Development] xaueious:
I know. I asked the dev about the exact same thing with the exact same threads!!!

Here was his reply: http://xdaforums.com/showpost.php?p=6234015&postcount=91

Do me and everyone else a favor and go to the thread in the OP and READ

If not just look at the diff file. You'll see what I mean. This HAS NOT been done before.
[G1 Android Development] OG:
Better be for real. This'll defiently help the myTouch Slide ROMs run.
[G1 Android Development] kristoff123:
If this is real, I'm going to buy the slim extended battery for g1 and flog another 6 months or so out of this bad boy.
[G1 Android Development] erlern:
I really wish I knew how to use this patch. I would be very willing to flash this on my device :) Can someone who knows how to do it for the sake of our curiosity, instead of just ignoring it? Unless things are tested, every solution proposed is a possibility :) Thanks in advance guys!
[G1 Android Development] h.nocturna:
If anyone wants to post up a build/boot.img with this hacked on, I'd be willing to risk my spare G1 to test the results.
[G1 Android Development] jad011:
this isnt going to brick your phone
[G1 Android Development] domenukk:
The guys over ad cdma hero forum have a rom with 746mhz... :eek:

Who can tell if it works? not me...

for me the speed is fast enough already with 512 mhz fix... but clocking from 128 to 746 mhz on demand would be epic :D

and then the new mytouch slide rom... rocking it at the moment. love my phone like never before :cool:

Update can wait :P
[G1 Android Development] Audinator:
AWESOME!

This is great! I was hoping someone would find a way to OC this processor! There's a Hero Rom with it confirmed working with benchmarks that look really promising. I can't wait for it to be built into a rom for us G1 users!
[G1 Android Development] MattKilla:
..so why doesn't someone just patch it in and give it a shot?
[G1 Android Development] xaueious:
Well I am trying to boot it and my phone freezes with the stock patch after displaying the bootscreen. Trying one more time and lowering the multiplier from 37 to 34.

34 * 19.2 = 652.8 MHz -> FAILED

Didn't boot properly either. It stopped with the line "D/BT HSHFP( 706): Starting BluetoothHeadsetService" in logcat for me. Phone freezes after video goes on. The entire boot seems fine otherwise, even building dalvik-cache and everything.

Boots with what I think is 614.4 MHz, for a 16% overclock, CM-kernel patched:

My Linpack on Super D without JIT is about

2.04 seconds with 2.647 Mflops after multiple runs.

My Super D install is really choppy on CM-kernel though. Until I figure out how to build wg-kernel I wont be keeping this.

2.35 seconds with 2.308 Mflops after multiple runs

The improvement of 15% is inline with theoretical values!

Anyways I think this proves that this OC is doing something!

Proof of concept kernels for Super D 1.10.2 (should work on some other ROMs)

Based on cm-kernel

Should be running at 614 MHz. BogoMIPS wont report it, and the kernel is not going to report the frequency it is running at since the change is internal. But the benchmark shows an improvement so I'd say this works.

EBI1 version is for 32A or people on 3.x radios only! (aka me)

G1/32B version is coming.

(ramzswap.ko is in there but you might not even need it. I left it there because I was too lazy to take it out)

Notes

No point of building this unless this is done with wg-kernel with RAMHack for me. This is a proof of concept rather than something you should use as an everyday kernel. I found wg-kernel at 528MHz with RAMHACK to be smoother despite the higher benchmarks of the 614 MHz kernel.

Someone can try different frequencies...
[G1 Android Development] erlern:
Sounds great... I am a bit surprised why people are not more enthusiastic about this? Just because the previous OC was found to be wrong doesn't mean that we give up right?

Anyway, how do we apply this to our devices? Just flash it from recovery? Or ? Sorry, am a noob, but would like to test it out :) Btw, Thanks for the good news :)
[G1 Android Development] xaueious:
To be honest it doesn't look that useful for the G1. But I would still like to see a dev pick this up for reaping the little benefits that this does promise.

I'm at least hopeful that we can get stable 576 MHz for all roms from now on.
[G1 Android Development] dumfuq:
here's a boot.img for cy-4.2.15.1 with the ramhack applied as well. It's using the modified patch from damien667 posted earlier.
[G1 Android Development] kristoff123:
Ramhack version tested and working brilliantly on the cyanogen's newest!

This is like having a new phone - I am going to go ahead and order the slim extended battery from fommy! I now have a ram, processor, and battery upgrade. Screw the mytouch slide! :p

Instructions:

1. flash cyanogen as per his wiki

2. download the .img above to your sdcard , rename it to boot.img

3. open terminal emulator, then type 'su'

then

flash_image boot /sdcard/boot.img

reboot

4. (quote)

you need to do a "custom" device in setCPU (for some reason, the autodetect feature is not working for our phones... even though it should...)

this requires you to make a file in /sdcard called setcpu.txt with the following code inside of it:

Code:

19200,122880,128000,245760,384000,528000,614400

then you configure setCPU for a custom device and it should allow you to go up to 614.4 :-)
[G1 Android Development] Sik-1:
so after i set up my swap and all the rest then i flash this and reboot???
[G1 Android Development] Sik-1:
do i turn on jit after or b4?????
[G1 Android Development] kristoff123:
I have no idea. I don't mess with JIT, it sounds gross :p

I am running on just a stock cyanogen, then flashed the boot.img 3 posts above. No problems so far. The phone is super smooth!
[G1 Android Development] Ace42:
Has anyone tried this with an eclair rom?

Perhaps cannon's 2.1?
[G1 Android Development] sd2649:
after 3 days, I am still loving this patch, very little effect on battery life. I haven't had any stability issues or wifi issues, however, my wifes identical G1 is another story. we both are running cyanogens latest with a2sd, no ram hack (wich would be overwritten anyway) no jit, same swap siz, same exact sd cards even. I put it on hers and it is unstable, random reboots VERY often. I am wondering if it just a software issue, but she won't let me do a wipe and clean install. Is anyone trying a clean wipe? Maybe this is causing our random stability issues???? I didnt wipe and got lucky, anyone up to the challenge? someone who had stability issues ready to wipe?
[G1 Android Development] kristoff123:
You should just redo it with a full wipe, reset, cache, battery, sdcard.
[G1 Android Development] Sik-1:
yea i was using it on super d b4, i think ima go back since it was faster than cyan from the get-go:D
[G1 Android Development] Sik-1:
i full wipe all new changes, exept for ext:D just fix permissions after a nice reboot
[G1 Android Development] goofyog:
Will this work for 2.1 or sense ui??
[G1 Android Development] IConrad01:
Gonna have to play with this more once I get home... tried this at work and I couldn't do anything without having the phone lock up and soft reboot. (Revert to splash screen but not to G1 screen.) Everything that *did* work took 2x as long, and I couldn't get sound to my bluetooth.

I'll try wiping my Dalvik-cache and re-flashing and see how that goes.
[G1 Android Development] dumfuq:
changed the patch to not override 528 at all.

won't overclock unless you use setcpu or whatnot.

previous version 528 was really 614

cm-4.2.15.1 w/ramhack boot.img
[G1 Android Development] ivanmmj:
Not all CPU's can handle the same overclock frequencies.
[G1 Android Development] phhusson:
Sorry, bad memory then :p
[G1 Android Development] erlern:
Any fix for the broken wifi? :) Thanks!
[G1 Android Development] tnpapadakos:
currently #1

took the plunge, flashed it and, well ... check the attached png...
[G1 Android Development] G1ForFun:
If only you knew how to post a link to the full screen version.;)
[G1 Android Development] tnpapadakos:
how right you are sir, my first imgur upload

http://imgur.com/HuTxu.png

also link to linpack site (while its still current)

http://www.greenecomputing.com/apps/linpack/linpack-by-device/
[G1 Android Development] G1ForFun:
nice...top score I see. :D
[G1 Android Development] gadget421:
look again

Im no.1

Beat this!!
[G1 Android Development] erlern:
You do know that we G1/Dream users are way above you guys right? :P

4.3 :P Beat that! hahaha
[G1 Android Development] Dyonas:
I'm having a little trouble with getting this to work. I've restored a Cyanogen image I use, his 4.2.15.1 ROM and while the ROM runs normally, as soon as I flash the boot image and reboot it will run for about 10 - 30 seconds before locking up. I end up having to pull the battery to reboot and reflash too.

Order of doing things...

Flash Cyanogen's ROM

Terminal to flash the OC boot image

Reboot

Loads and then locks up shortly after

Anything I'm missing? I have a custom SetCPU file ready but I don't even get that far, it locks up before I get a chance to run it.
[G1 Android Development] tnpapadakos:
it was nice while it lasted:(

OOOOPS! I spoke too soon
[G1 Android Development] tuffCookie:
i'm experiencing the same issue and i've tried Cyanogen, Super D, and ZachAttack 2.2.1
[G1 Android Development] gadget421:
nice.. how are you hitting 4.3? using ramhack?
[G1 Android Development] erlern:
Mine is the 4.29... nothing actually... just using JIT with OC. That's it... no ramhack. Does ramhack actually improve performance?
[G1 Android Development] gadget421:
using fasttest 3.1.1 w/oc614 without ramhack 4.19 max(runs great)

using an old oc boot.img

trying the new boot.img with ramhack..will see
[G1 Android Development] gadget421:
with ramhack 4.23

mytouch 32b
[G1 Android Development] damien667:
new boot.img to try

I made a change to see if it would help with lag. Now it doesn't mess with the divider for both 528.8 and 614.4 when it sets the speed to either. It only messes with it when it's >528.8, not >=. I get more consistent benchmark results now and phone seems more responsive :D

THIS ONLY WORKS WITH CM 4.2.15.1 NON ROGERS G1's.

TO ALL THE NEWBS THAT COMPLAIN ABOUT YOUR WIFI NOT WORKING, THAT IS WHY.

Once the patch is confirmed to be stable, all the ports to all the other ROM kernels will be trivial... if someone wants to cross compile a kernel for another ROM, here's my patch so you can apply it on your own:

http://www.mediafire.com/?ntttnucnxo2

diff --git a/arch/arm/mach-msm/acpuclock.c b/arch/arm/mach-msm/acpuclock.c
index 7a413e3..0d2522d 100644
--- a/arch/arm/mach-msm/acpuclock.c
+++ b/arch/arm/mach-msm/acpuclock.c
@@ -115,6 +115,7 @@ static struct clkctl_acpu_speed acpu_freq_tbl[] = {
{ 352000, ACPU_PLL_2, 2, 2, 88000, 3, VDD_5, 128000, 0, 3, 7 },
{ 384000, ACPU_PLL_1, 1, 1, 128000, 2, VDD_6, 128000, 0, 2, -1 },
{ 528000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },
+ { 614400, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 160000, 0, 5, -1 },
{ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 },
};
#endif
@@ -127,7 +128,8 @@ static struct cpufreq_frequency_table freq_table[] = {
{ 3, 245760 },
{ 4, 384000 },
{ 5, 528000 },
- { 6, CPUFREQ_TABLE_END },
+ { 6, 614400 },
+ { 7, CPUFREQ_TABLE_END },
};
#endif

@@ -200,10 +202,23 @@ static int acpuclk_set_vdd_level(int vdd)

/* Set proper dividers for the given clock speed. */
static void acpuclk_set_div(const struct clkctl_acpu_speed *hunt_s) {
- uint32_t reg_clkctl, reg_clksel, clk_div;
-
+ //OC HACK uint32_t reg_clkctl, reg_clksel, clk_div;
+ uint32_t reg_clkctl, reg_clksel, clk_div, a11_div;
+
/* AHB_CLK_DIV */
clk_div = (readl(A11S_CLK_SEL_ADDR) >> 1) & 0x03;
+
+ //OC HACK
+ a11_div=hunt_s->a11clk_src_div;
+
+ //if clock is more than 528000, set it to (19.2 x (0x20) = 614.4)
+ // all_clock_source_divider is always 0 for 614400
+ if (hunt_s->a11clk_khz>528000) {
+ a11_div=0;
+ writel(0x20, MSM_CLK_CTL_BASE+0x33C);
+ udelay(50);
+ }
+
/*
* If the new clock divider is higher than the previous, then
* program the divider before switching the clock
@@ -226,7 +241,8 @@ static void acpuclk_set_div(const struct clkctl_acpu_speed *hunt_s) {
/* Program clock divider */
reg_clkctl = readl(A11S_CLK_CNTL_ADDR);
reg_clkctl &= ~0xf;
- reg_clkctl |= hunt_s->a11clk_src_div;
+ //OC HACK reg_clkctl |= hunt_s->a11clk_src_div;
+ reg_clkctl |= a11_div;
writel(reg_clkctl, A11S_CLK_CNTL_ADDR);

/* Program clock source selection */
@@ -245,7 +261,8 @@ static void acpuclk_set_div(const struct clkctl_acpu_speed *hunt_s) {
/* Program clock divider */
reg_clkctl = readl(A11S_CLK_CNTL_ADDR);
reg_clkctl &= ~(0xf << 8);
- reg_clkctl |= (hunt_s->a11clk_src_div << 8);
+ //OC HACK reg_clkctl |= (hunt_s->a11clk_src_div << 8);
+ reg_clkctl |= (a11_div << 8);
writel(reg_clkctl, A11S_CLK_CNTL_ADDR);

/* Program clock source selection */
[G1 Android Development] Barsa75:
4.3 is my score without ramhack, cm 4.2.15.1 + jit + oc 614.4 + swap + compcache, only 2 reboot on 24h.
[G1 Android Development] erlern:
I'll try to beat your score Barsa :P Good score btw :)
[G1 Android Development] gadget421:
ok

mytouch

fasttest3.1.1+ oc(with ramhack)+jit+swap and compcache on(32mb)..4.23best
[G1 Android Development] Barsa75:
Obtain 4.3 with a fresh cm reinstall (all 5 wipe), without any tweaks, only cc/swap and jit enabled.

Isn't better for benchmark with ramhack, but i think memory usage, specialy for multitask will be much responsive.

Waiting for a patch with rh/oc & wlan working ;)
[G1 Android Development] erlern:
Actually I used the same, but my wifi is ok. I reinstalled everything as well. :) But no RH.
[G1 Android Development] G1ForFun:
Same issue here...not every device is going to overclock the same. Keep that in mind.

Makes sense to me....plus my G1 can't handle this patch...it soft reboots and freezes constantly.

Edit: No dev should include this in their rom....unless its optional with a toggle switch of some kind.
[G1 Android Development] xillius200:
lol htc magic 32b is a bit useless with OC keeps soft rebooting only every now and again after 2 hours or so XD added it to ZX Donut but taking it out for next build till this is stable not stable enough lol anyway good work man keep it up :P
[G1 Android Development] Dyonas:
Yeah I'm aware of that, it'll be the same as with computer CPUs. Some will overclock to infinity (and beyond! ... sorry) but others won't budge. I posted to ask if I was missing something before coming to this conclusion, nothing more :) Seeing that you and a few others have it too I'm clinging to that glimmer of hope that with it being so few it may be a small issue that can be worked out.

If it isn't fixable then it isn't a huge issue ... yeah I'll keep lying to myself until October when I can upgrade to whatever is newest and highest rated or Cyanogen punts out a new release to distract me.
[G1 Android Development] Daneshm90:
Hey guys so whats the latest 32a patched kernel for this overclock ? i used the one in the first post but barely got any improvement (like .7 more in linpack). Saw that you guys are compiling new ones for dream. Wondering if you could do the same for 32a as well :)
[G1 Android Development] alutastisch:
well guys, i tried this rom on my cyanogen 32B Magic. and i dont see any differences.
[G1 Android Development] phhusson:
Change cpufreq high limit....
[G1 Android Development] damien667:
Yeah, check your kernel's .config and change 528000 to 614400
[G1 Android Development] erlern:
okay, correct me if I am wrong but whether the cpu is overclock can be known from its linpack benchmark performance right? Is that a good enough test or that can be faked?

Anyway, I have tested numerous times using SetCPU to adjust the clock speed from 128 to 614 and the performance goes hand in hand with what we expect to see. At 128 Mhz I get a score of 0.76, 528 of 3.2+ and 614 of 4.1+ (of course this is also because I have JIT in it).

So it is a real overclock right?
[G1 Android Development] farmatito:
I did this in the kernel config.

CONFIG_MSM_CPU_FREQ=y
CONFIG_MSM_CPU_FREQ_ONDEMAND=y
# CONFIG_MSM_CPU_FREQ_SCREEN is not set
CONFIG_MSM_CPU_FREQ_ONDEMAND_MAX=614400
CONFIG_MSM_CPU_FREQ_ONDEMAND_MIN=245760
CONFIG_MSM_HW3D=y
CONFIG_MSM_ADSP=y

and to be sure in my userinit.sh:

# Overclock CPU when in use, put at lower freq when idle.
echo 384000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 614400 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

and if you look at the first patch posted in this thread you'll see

that it has also if(hunt_s->a11clk_khz>=528000).

diff --git a/arch/arm/mach-msm/acpuclock.c b/arch/arm/mach-msm/acpuclock.c
index 0eda940..29a669f 100644
--- a/arch/arm/mach-msm/acpuclock.c
+++ b/arch/arm/mach-msm/acpuclock.c
@@ -248,10 +248,18 @@ static int acpuclk_set_vdd_level(int vdd)

/* Set proper dividers for the given clock speed. */
static void acpuclk_set_div(const struct clkctl_acpu_speed *hunt_s) {
-	uint32_t reg_clkctl, reg_clksel, clk_div;
+	uint32_t reg_clkctl, reg_clksel, clk_div, a11_div;

/* AHB_CLK_DIV */
clk_div = (readl(A11S_CLK_SEL_ADDR) >> 1) & 0x03;
+
+	a11_div=hunt_s->a11clk_src_div;
+
+	if(hunt_s->a11clk_khz>=528000) {
+	a11_div=0;
+	writel(0x25, MSM_CLK_CTL_BASE+0x33C);
+	udelay(50);
+	}
/*
* If the new clock divider is higher than the previous, then
* program the divider before switching the clock
@@ -274,7 +282,7 @@ static void acpuclk_set_div(const struct clkctl_acpu_speed *hunt_s) {
/* Program clock divider */
reg_clkctl = readl(A11S_CLK_CNTL_ADDR);
reg_clkctl &= ~0xf;
-	reg_clkctl |= hunt_s->a11clk_src_div;
+	reg_clkctl |= a11_div;
writel(reg_clkctl, A11S_CLK_CNTL_ADDR);

/* Program clock source selection */
@@ -293,7 +301,7 @@ static void acpuclk_set_div(const struct clkctl_acpu_speed *hunt_s) {
/* Program clock divider */
reg_clkctl = readl(A11S_CLK_CNTL_ADDR);
reg_clkctl &= ~(0xf << 8);
-	reg_clkctl |= (hunt_s->a11clk_src_div << 8);
+	reg_clkctl |= (a11_div << 8);
writel(reg_clkctl, A11S_CLK_CNTL_ADDR);

/* Program clock source selection */
[G1 Android Development] phhusson:
It's >= because I haven't added another frequency than 528MHz in the cpufreq table ...
[G1 Android Development] gophergun:
Booting gets stuck at

I/SystemServer( 1864): Battery Service

with EBI0 boot.img.

Not complaining or anything, just posting in case any devs find it useful. Thanks for continuing the work on squeezing the last bit of life out of our tired G1s :D
[G1 Android Development] farmatito:
So you agree that

if (hunt_s->a11clk_khz > 528000)

is wrong as this will never be executed because a11clk_khz

will in the current code never be greater than 528000 and that you need

at least

if (hunt_s->a11clk_khz >= 528000) {

or more correctly in relation to the value of a11clk_khz

if (hunt_s->a11clk_khz == 528000) {

to trigger the overclock. You can easily check this if you stick

some debug statement in the if code block. Maybe you could try

the patch attached to the previous post as it already has debugging

statements and debug turned on.
[G1 Android Development] damien667:
My patch has 614400 in the freq table and hence why i changed the if statement to > instead of >=... however, neither way is stable enough for me and have since abandoned hope... i'll just buy a Nexus Two when they come out :-P

Your assertion that the code never runs is incorrect, how do you explain better scored with benchmarkpi and linpack? SOMETHING is going faster...
[G1 Android Development] farmatito:
It is not an assertion as i took the time the add debug statements inside the if

code block and because the value at MSM_CLK_CTL_BASE+0x33C never gets changed to 0x22.
[G1 Android Development] beidl:
Reverted my phones radio back to EBI0, tried the new kernel on my G1 with CM (JIT enabled) and it's very impressive, there is a speed increase, definitely.

But I'd like to try it on some eclair based ROMs. These are in need of a OC'ed kernel.

Could somebody please apply the patch to a eclair based kernel (wesgarners kernel for example) and compile it?

I would have done it myself already but I wasn't able to because of school and other stuff so i just wanted to ask kindly. ;)