Hi all,
I've been a faithful WM user until I saw the beautiful work that matt (xandroid) has been doing. I followed his work since August of last year, and had Android on my touch pro2 (sprint).
I love everything about the work, but low battery part is just a killer for me. The latest Tiad version of froyo only lasts about 8 hours top (with minimum use - just email sync). I think Xandroid (FRX04) is lasting about 9 hours.
I keep going back and forth between FRX03/04 and Froyo work made by Tiad8. What are the relationship between these two work? I know the kernel is the same, but which is the one to go?
Battery life wise, are they any different (one better than the other)? or is that a kernel problem still? Has anybody been successful to run android on rhodium for all day with specific (old) kernel? As you can see, I don't care about camera, bluetooth, and etc.
As a user, I just want my phone to last a day for me. I work from 7 AM to 5 PM. As of right now, my phone won't last unless I charge it through USB during the day.
Let me know! Thanks all.
Mike
Well I dont think that we can compare the job of this 2 guys, tiad is triying to give us the missing parts like a good 3d and camera. and mathews is working righ know on stability and a ported version, both works are great, and im testing rightnow the FRX04 the battery last much longer than other builds. and i haven´t to hardreset the phone even once. on my rhod 500. working with GSM.
Sorry if I came out like comparing two works. I just wanted your two cents on battery; that's all.
Thanks!
There really is no difference with tiad8's build AFAIK. He just takes the latest and bundles them together for newbies. I wish he wouldn't name it different, as that makes it seem like it's completely different - when in reality the differences are minor - you can achieve the same build by dropping in the appropriate files.
With that said, battery life improvements are all going to happen at the kernel level. So you can take whatever build, and drop in a different kernel to improve battery life.
At this time, WisTilt2's test kernel is going to get you the best battery life. He's working on the rest of the devices so he can commit his code (basically our phone's are not sleeping correctly, the panel is still getting/sucking power even tho the screen appears to be off)
See the test kernel thread here.
Thanks for the post, Arrrghhh. You are talking about the wistilt2 kernel stripped version right?
I will try that with FRX04.
Thanks.
mike92585 said:
Thanks for the post, Arrrghhh. You are talking about the wistilt2 kernel stripped version right?
I will try that with FRX04.
Thanks.
Click to expand...
Click to collapse
Not sure what you mean by stripped version. I see now... that's down below in F22's post - focus on the first post . Just download the kernel-pack that's attached to the first post.
There was a discrepancy on the modules that needed to be included. It was sorted out, and the first post has the newest test kernel that WisTilt2 has provided me with.
I think they are "similar", but I must say that I always have issues with XDAndroid... It hangs when appears the Android home screen and I must reboot like 50 times before it works ok, also it's a little slow...In contrast, FroyoX always worked from the first time and is super fast without overclocking...That's my opinion!
nickleby said:
I think they are "similar", but I must say that I always have issues with XDAndroid... It hangs when appears the Android home screen and I must reboot like 50 times before it works ok, also it's a little slow...In contrast, FroyoX always worked from the first time and is super fast without overclocking...That's my opinion!
Click to expand...
Click to collapse
I'd honestly want to know the difference between the system image FRX04 and the 'Froyo X' system image. If there is a tangible difference, we need to change whatever tiad8 changed!
I wish that dude would work with us instead of in parallel to our work....
mike92585 said:
Hi all,
I've been a faithful WM user until I saw the beautiful work that matt (xandroid) has been doing. I followed his work since August of last year, and had Android on my touch pro2 (sprint).
I love everything about the work, but low battery part is just a killer for me. The latest Tiad version of froyo only lasts about 8 hours top (with minimum use - just email sync). I think Xandroid (FRX04) is lasting about 9 hours.
I keep going back and forth between FRX03/04 and Froyo work made by Tiad8. What are the relationship between these two work? I know the kernel is the same, but which is the one to go?
Battery life wise, are they any different (one better than the other)? or is that a kernel problem still? Has anybody been successful to run android on rhodium for all day with specific (old) kernel? As you can see, I don't care about camera, bluetooth, and etc.
As a user, I just want my phone to last a day for me. I work from 7 AM to 5 PM. As of right now, my phone won't last unless I charge it through USB during the day.
Let me know! Thanks all.
Mike
Click to expand...
Click to collapse
I was having a similar experience with my Sprint TP2. I updated to FRX04 and then the camera testing kernel but my battery life was about 6-8 hours.
I had it set to disable satellites but left "Use Wireless Networks" enabled and then last night I turned off all of the location options. Today I'm at 8 hours and the battery is only down to 68%. The other thing I looked at is that if you have Facebook, Twitter, Fourquare or any other apps running that any auto-refresh/updates/notifications are disabled.
Hopefully this helps you out. I've gone from hating my phone with it's constant lag in WM to loving using my phone with Android.
Mizofizo, let me see what you exactly did.
Since you use sprint and also in boston, we are pretty much on the same boat. However, no matter what I do, I can't get my battery to last all day. I always have both use wireless networks off and location options off as well. No facebook or nothing.
I am now at a point where I am even afraid to turn the screen on because of the battery drain.
Could you email me the startup.txt or pm me the detail? So you are using the stock FRX04 with which kernel are you running? Are you running the latest 1253?
This is my startup.txt that I have been using.
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 force_cdma=1 physkeyboard=rhod210 hw3d.force=1 htc_battery_smem.fake=1 north_am_dialing=1 pm.sleep_mode=1"
boot
Note pm.sleep_mode=1.
Thanks in advance.
Mike
mike92585 said:
Mizofizo, let me see what you exactly did.
Since you use sprint and also in boston, we are pretty much on the same boat. However, no matter what I do, I can't get my battery to last all day. I always have both use wireless networks off and location options off as well. No facebook or nothing.
I am now at a point where I am even afraid to turn the screen on because of the battery drain.
My email is . Could you email me the startup.txt or pm me the detail? So you are using the stock FRX04 with which kernel are you running? Are you running the latest 1253?
This is my startup.txt that I have been using.
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 [color=red][b]msmts_calib=0x9f.0x39a.0x35c.0x78[/color][/b] msmvkeyb_toggle=off [color=red][b]pmem.extra=1[/color][/b] gsensor_axis=2,1,3 force_cdma=1 [color=blue][b]physkeyboard=rhod400[/color][/b] hw3d.force=1 [color=red][b]htc_battery_smem.fake=1[/color][/b] north_am_dialing=1 pm.sleep_mode=1"
boot
Note pm.sleep_mode=1.
Thanks in advance.
Mike
Click to expand...
Click to collapse
I'd remove your email from the post - trust me, you'll get a ton of spam because of it. Just do <email> at <domain> dot com if you ever feel the need to put your email address into a forum (which I wouldn't do either )
Anyhoo, I highlighted in red/bold some of the commands you should consider removing. Especially the htc_battery_smem.fake!
Oh, and if you're on Sprint - is it a Sprint-branded phone? If so, that's a RHOD400. RHOD210 wouldn't even work on Sprint, as there's no CDMA radio in that device .
mike92585 said:
Mizofizo, let me see what you exactly did.
Since you use sprint and also in boston, we are pretty much on the same boat. However, no matter what I do, I can't get my battery to last all day. I always have both use wireless networks off and location options off as well. No facebook or nothing.
I am now at a point where I am even afraid to turn the screen on because of the battery drain.
Could you email me the startup.txt or pm me the detail? So you are using the stock FRX04 with which kernel are you running? Are you running the latest 1253?
This is my startup.txt that I have been using.
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 force_cdma=1 physkeyboard=rhod210 hw3d.force=1 htc_battery_smem.fake=1 north_am_dialing=1 pm.sleep_mode=1"
boot
Note pm.sleep_mode=1.
Thanks in advance.
Mike
Click to expand...
Click to collapse
I would delete the options that arrrghhh specified.
I'm running FRX04 with the camera testing kernel. My startup.txt is as follows:
set RAMSIZE 0x10000000
set RAMADDR 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off force_cdma=1 gsensor_axis=2,1,3 pm.sleep_mode=1 hw3d.force=1 physkeyboard=rhod400 board-htcrhodium.is_cdma=1"
boot
Note that I don't have a rel_path since I put everything in the root of my SD card.
With my current config, yesterday at about 16 hours of use (including wifi and gps) I had about 38% battery left.
Thanks to both.
I finally see the green led light on my tp2. =D
Hopefully I will get some long battery life now... I will post back once I do!
I have used the startup.txt details above but I still have issues with my phone waking up! The light never turns green and it will not wake up after a while of not being used.... any suggestions?
Using XDAndroid FRX04 1/23/2011
AT&T Tilt2
Kernel 1250
scattaman said:
I have used the startup.txt details above but I still have issues with my phone waking up! The light never turns green and it will not wake up after a while of not being used.... any suggestions?
Using XDAndroid FRX04 1/23/2011
AT&T Tilt2
Kernel 1250
Click to expand...
Click to collapse
Why are you using kernel 1250 instead of 1253 or the one included in FRX04? I'd try just using FRX04 as is. Make sure that all unneeded syncing/services are turned off.
scattaman said:
I have used the startup.txt details above but I still have issues with my phone waking up! The light never turns green and it will not wake up after a while of not being used.... any suggestions?
Using XDAndroid FRX04 1/23/2011
AT&T Tilt2
Kernel 1250
Click to expand...
Click to collapse
SoD issues still ensue - devs are looking into a potential resolution/root cause.
mizofizo said:
Why are you using kernel 1250 instead of 1253 or the one included in FRX04? I'd try just using FRX04 as is. Make sure that all unneeded syncing/services are turned off.
Click to expand...
Click to collapse
Thanks but I've tried all the available kernels... including the one that came with FRX04... its just really annoying because it happens almost everytime I pput my phone down for 5 minutes
arrrghhh said:
SoD issues still ensue - devs are looking into a potential resolution/root cause.
Click to expand...
Click to collapse
Well its good to know that I'm not the only one...
scattaman said:
Thanks but I've tried all the available kernels... including the one that came with FRX04... its just really annoying because it happens almost everytime I pput my phone down for 5 minutes
Click to expand...
Click to collapse
It does happen, but it shouldn't be that frequent. Are you running any apps when you put your phone down...? Post your startup.txt too, just to make sure there's nothing funky in it.
Also, have you tried NOT OC'ing? Are you on pm.sleep_mode=1?
For those of you with decent battery life, how do you setup android when running for the first time?
slapshot30 said:
For those of you with decent battery life, how do you setup android when running for the first time?
Click to expand...
Click to collapse
What do you mean? I formatted my SD card, unrared FRX04 to the root of my SD card. Changed the conf file to point to the root and configured my startup.txt. Afterward, I setup the camera kernel as well. That's about it.
Related
wifi working with patch.
http://forum.xda-developers.com/attachment.php?attachmentid=325161&d=1273647492
http://forum.xda-developers.com/showthread.php?t=679680
could someone resize it to 240x320 please? cant wait to try this
Heads up! New Kaiser Wifi update: http://forum.xda-developers.com/showpost.php?p=6456191&postcount=33
Old one replaced build.prop with wrong version. Reinstall and use the new Wifi update.
Also to get rid of android-rebooting-problems with GPS Test application do the following:
1. Start terminal emulator
2. su
3. cd system/lib/hw
4. rwsystem
5. rm sensors.msm7k.so
6. rosystem
7. exit
8. exit
9. restart phone
So how is it? I'm too lazy to install it.
Dukenukemx said:
So how is it? I'm too lazy to install it.
Click to expand...
Click to collapse
Seems like a really nice build. I'm using 320x428 with 144 dpi. A bit slow because I'm currently not running in NAND but I would expect it to perform quite well once I go back to running NAND again.
I haven't tested it very much yet as I'm doing some experiments in WinMO at the moment.
just tried
hey
i just downloaded this and i have to say im impressed about this.
as i love the eclair design and everything and the donut speed i have to say this is impressing because it is FAST! not as fast as donut but pretty much the same. that could be due to the 500 mHz OC but i just like that build.
just needs to be optimized a bit, maybe a few apps like astro and others
and as the developer has a new phone we need a new one.
But i have to say its awesome!
i love it already and just tried it for 9 min.
just the OC needs to be removed i noticed right now and is there any way to set another value for the screen sensebility because quiet often it does not react on a touch.
so keep updating this!
nick
nice rom but it chews through battery like crazy. With a full charge battery will drop from 99 to 75(battery fix removed OC and set 1400 value) with just a 10min phone call and a couple txts. I think what we need is a new kernel highly optimized for battery life using the latest patches. Judging from the name alone of the kernel its running right now 2.6.25-01051-gc362ac-dirty and the fact that 2.6.25 was released in jul 2008 i think theres room for tons for improvement.
Does anyone know how to adjust the microphone gain? my friends complain they cant hear me..
The wifi scan interval is set to 15 seconds by default in this release. That will have a negative effect on battery life if you are out of range of a known network and have wifi enabled. I'll put together an update to change this when time allows. I use 120 seconds myself.
kallt_kaffe said:
The wifi scan interval is set to 15 seconds by default in this release. That will have a negative effect on battery life if you are out of range of a known network and have wifi enabled. I'll put together an update to change this when time allows. I use 120 seconds myself.
Click to expand...
Click to collapse
Thanks to update.
It working good on Polaris.
Also i change interval to 180 and density to 120 in .prop
Here's an update that changes the wifi scan delay to 120 seconds and also (not tested yet) changes the model name from Vogue to Kaiser.
i'm still trying to figure out if it's possible, somehow, to flash an update.zip file (to be able to use the cyanogenmod skins) with the nomorootfs we're using, instead of converting the skins to metamorph format
does anyone know if it's possible or how to do it?
Can't get wifi to work with updates, which one should I need?
kallt_kaffe's works for me. If something isn't working like it should, power off the phone and remove the battery. Then hold down the power button to remove any remaining power left. Place batter back in and try again.
Also, make sure to always fix permissions when you apply updates, even for wifi.
Dukenukemx said:
kallt_kaffe's works for me. If something isn't working like it should, power off the phone and remove the battery. Then hold down the power button to remove any remaining power left. Place batter back in and try again.
Also, make sure to always fix permissions when you apply updates, even for wifi.
Click to expand...
Click to collapse
edit: how stupid can I be? I've bought another phone and forgot to add the mac adress.
Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power. A lot of pop ups to force close apps. A lot of apps are running that I don't use.
mssmison didn't say he was going to put any more effort into it either. Hopefully, someone will pick it up.
Dukenukemx said:
Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power.
Click to expand...
Click to collapse
Try deleting /data/system/batterystats.bin. That usually helps when the batterymeter has gone bad.
A lot of pop ups to force close apps. A lot of apps are running that I don't use.
Click to expand...
Click to collapse
Have you removed or renamed /lib/modules/hw/sensors.msm7k.so? After I removed that it runs very stable for me.
kallt_kaffe how do you do it?
I'm new to the androidinstall.tar method. I'm tyring to run from haret but it seems impossible.
You said you where experimenting with something in winmo, so that implies you're using haret? Are you running from haret?
When I try, Polymod, and Mssmission they don't show an install option, when I try myn and incubus I get it installed but I get no sound. It was actually your gps kernel that let me get things installed all other kernels i tried had non-functional dpads within the installer environment. Also, trying another kernel once installed didn't fix the sound issue.
Anyhow just let me know if you're using Haret. I wonder whats up with the sound and missing install option. I tried the install two different ways one with a 2gb fat32 partition, and then another attempt using three primary partitions 1.3gb fat32, 300mb ext, 300mb ext. All installers then would give me options beside's fat, but not all intallers would have an install option.. I'm using radio 1.71.09.01.eMo, model: kais100, os: wm6.5 (shifu v.3)
kallt_kaffe said:
Have you removed or renamed /lib/modules/hw/sensors.msm7k.so? After I removed that it runs very stable for me.
Click to expand...
Click to collapse
I try start Skyforce game, but it forceclose.
It can work after i added "sensors.sapphire.so" into /lib/modules/hw/
I've installed the cyanogenMod updater from the marketplace, but it can only find older versions, no experimental versions, whatever option I set in the program.Anyone?
Dukenukemx said:
Certainly think mod needs work. So far the battery meter is off, and all this time I thought it drained less power. A lot of pop ups to force close apps. A lot of apps are running that I don't use.
Click to expand...
Click to collapse
battery life has been fantastic for me on this build...
although I reverted back to 400mhz and got rid of compcache.
I am sure that OCing to 500 by default is draining the battery faster.
I would rather a usable phone than a fast one...(although it still seems very fast to me)
I add into cmdline of startup.txt value "acpuclock.oc_freq_khz=700000" and after this android work like a charm! Very fast! So is it safe to use overclock when work at android? Can i brick my phone using this ?
I suppose it's pretty much safe.
The chips in our touch pro's are made for low power consumption. That means small heat dissipation as well.
That usually means they've got some headroom for overclocking.
As with a normal PC, overclocking is mostly harmless, unless components overheat.
The worst thing that might happen, is a frozen device that needs a softreset.
It might warm up your device though. And will also drain your battery somewhat more.
I would advice returning to stock clocks when your device is warm a lot, or when you experience random crashes.
i just tried adding that cmd line and got an error unrecognized acpuclock word
*edit*
durf... i didn't put "set cmdline"
got so excited to overclock
Which version of the Raph are you using?
I2es
Thanks for the tip ;-)
Just tested "acpuclock.oc_freq_khz=700000" on a RAPH100, managed to use 691khz.
Benchmark went from 2.313MFLOPS (Linpak for android) to 2.958MFLOPS
Thanks will try this out.
Ceasar
I just gave it a go and it wouldnt go past the HaRET loading.
Startup:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 1910
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmts_calib=0x7a.0x5e.0x35a.0x37f clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-1,-2,3 board-htcraphael-navi.wake=0 physkeyboard=raph acpuclock.oc_freq_khz=700000"
boot
how do you no what ur running at the moment?
if your running at full or stock?
Here's my startup.txt
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 1910
set KERNEL zImage.20100606_150404
set initrd initrd-20100328-d4cd3e8
set cmdline "acpuclock.oc_freq_khz=700000 lcd.density=210 msmts_calib=0x7a.0x5e.0x35a.0x37f clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-1,-2,3 board-htcraphael-navi.wake=0 physkeyboard=raph"
boot
I'm using the overclockwidget app from android market, it's showing and can set CPU speed.
I needed to do a Detect frequencies before I could use 691200
a Nice feature is also that you can set lower CPU speed during sleep/standby limiting the standby battery usage.
/C
CeasarRAPH100 said:
Here's my startup.txt
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 1910
set KERNEL zImage.20100606_150404
set initrd initrd-20100328-d4cd3e8
set cmdline "acpuclock.oc_freq_khz=700000 lcd.density=210 msmts_calib=0x7a.0x5e.0x35a.0x37f clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-1,-2,3 board-htcraphael-navi.wake=0 physkeyboard=raph"
boot
I'm using the overclockwidget app from android market, it's showing and can set CPU speed.
I needed to do a Detect frequencies before I could use 691200
a Nice feature is also that you can set lower CPU speed during sleep/standby limiting the standby battery usage.
/C
Click to expand...
Click to collapse
Have you tried activating "turbo" mode? I did and it does seem a bit speedier. I also downloaded the overclockwidget but I don't quite understand how to set the values.
I've tried android on higher clocks as well.
As first I was sceptic, but using the overclock widget I found out the clockspeed was indeed up to 691 Mhz.
After using the phone for a while it was running pretty hot.
So referring to my first post in this thread:
I don't think it's a good idea to run this overclock 24/7 if you plan to use your phone for more than a year or so.
It also interfered with the sleep mode, so battery life whent from already bad (android isn't very battery friendly yet) to a lot worse.
Just my findings.
are you sure it was the overclock and not the gps?
A slight warning ;-)
Have removed the overclocking again it made the phone very unstable for me, and occationally corrupted the rootfs.img during shutdown.
Had to copy a fresh rootfs to be able to boot it up again.
I lowered to 600000 but still kind of unstable, I'm not sure if it was only the overclocking causing it.
It could also have been the new kernel(htc-msm-linux @ 20100614_211737) it seems to freeze the phone when using 3G data randomly without any overclocking at all.
But it's really fun it's even possible to do.
/C
Even at 700000, my phone runs fine without crashing or any bugs but drains battery quick and heats up fast.
Found a nice trade off between battery drain,stability & speed at 614400 (4.296 MFLOPS)
At idle or screen off I force 256000 (1.829 MFLOPS) throu "overclock widget".
I'm not sure if its a problem so i named this thread an "issue"...
Something really odd happened to me right now, i used l1qu1d's latest kernel and latest fat free, installed everything on nand, cleared davlik, waited 5 mins after initian boot, installed and configured my apps, signed in, added some widgets and oced to 490 (a good balance using my 1600 mHa batt), and then i realized my screen was fuzzy, not like when u set a non qvga res to the kernel but like when u set a really low refresh rate on a crt monitor.. and minutes later it dissapeared... could be an external source of "interference"? or a kernel issue? UFO abductions? ive never expirienced this till now, does anyone had?
i haven't seen this before, i simple restart fix the problem?
l1q1d said:
i haven't seen this before, i simple restart fix the problem?
Click to expand...
Click to collapse
didnt even need to... just like it appeated it vanished away....
This is stock ROM.
Every time I flash bacon bits to overclock my phone I always noticed that my screen flickers when I turn off the phone's screen or press the button to wake up.
Sometimes it just gets stuck and it stats flickering like crazy and I can't unlock my phone because of it.
This only happens when I OC my phone. When I wipe the phone it works fine but no OC which is what I want.
Any way to fix this issue?
I don't use Bacon Bits, but I have experienced the flickering you speak of. It seems that happen when you go too far with the OC process. What happens if you were to lower your clockspeed a bit? Does it continue to happen for you?
dustrho said:
I don't use Bacon Bits, but I have experienced the flickering you speak of. It seems that happen when you go too far with the OC process. What happens if you were to lower your clockspeed a bit? Does it continue to happen for you?
Click to expand...
Click to collapse
Actually I OC my phone, but it's still set on 806MHz so even at lower clockspeed it still flickers. It's bugging the hell out of me.
EDIT:
Switched over to pershoot's kernel: http://forum.xda-developers.com/showthread.php?t=847672 I can now overclock to 1.5 gHz with no problems anywhere. Aweseome.
I have this same problem and am bumping this thread.
I'm running stock rom with bacon bits v 0.3 - and my screen flickers when turning off so much that it won't turn off fully and opens the lock screen. I have to just try and try repeatedly to get it to work.
Any suggestions?
captainreynolds said:
EDIT:
Switched over to pershoot's kernel: http://forum.xda-developers.com/showthread.php?t=847672 I can now overclock to 1.5 gHz with no problems anywhere. Aweseome.
I have this same problem and am bumping this thread.
I'm running stock rom with bacon bits v 0.3 - and my screen flickers when turning off so much that it won't turn off fully and opens the lock screen. I have to just try and try repeatedly to get it to work.
Any suggestions?
Click to expand...
Click to collapse
Yeah, I have flashed all the kernels even pershoot's and it still flickers. I'm using the original ROM that came with the phone not the original one posted on the forums. Maybe if I use the one posted on the forums that will work?
I have the stock rom as well - I first flashed baconbits kernel, but when that flickered, I flashed pershoots most recent kernel in recovery. No flickering anymore - sorry to say I don't know what's wrong. Try posting in the thread of the kernel you are currently running!
Sent from my T-Mobile G2 using XDA Premium App
captainreynolds said:
I have the stock rom as well - I first flashed baconbits kernel, but when that flickered, I flashed pershoots most recent kernel in recovery. No flickering anymore - sorry to say I don't know what's wrong. Try posting in the thread of the kernel you are currently running!
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
Well you know what I flashed an older version of pershoot mayeb I should try the newer one. I'll let you know what happens...
I had trouble flashing it with ROM Manager. Clockworkmod it. Here's the link to pershoots blog with the latest update links: http://droidbasement.com/db-blog/
Good luck!
Sent from my T-Mobile G2 using XDA Premium App
Just tried it and nope... it's still doing it maybe it's just my phone.
Bring it up in this thread:
http://forum.xda-developers.com/showthread.php?t=847672&page=103
Pershoot is always monitoring it along with a bunch of other smart devs. Maybe they'll have a better idea - don't give up hope!
what app are you guys using to manage your OC?
if it's setCPU, set your scaling to Interactive on the main screen and in any profiles you're using.
also, if you are using any screen on/off animations, disable them (just to see, for troubleshooting purposes, if that might be the culprit)
pmcqueen said:
what app are you guys using to manage your OC?
if it's setCPU, set your scaling to Interactive on the main screen and in any profiles you're using.
also, if you are using any screen on/off animations, disable them (just to see, for troubleshooting purposes, if that might be the culprit)
Click to expand...
Click to collapse
Yeah, it's set on Interactive and so are the profiles. As for the screen on and off animation I believe that's in the CM7 RC1 ROM. I'm using the stock ROM so there's no option for that.
jjuice525 said:
Yeah, it's set on Interactive and so are the profiles. As for the screen on and off animation I believe that's in the CM7 RC1 ROM. I'm using the stock ROM so there's no option for that.
Click to expand...
Click to collapse
hehe, didn't even read what rom you were using. my bad.
kernels aside, it is very possible, as you mentioned earlier, that you guys got the chips in the stash that don't take to overclocking very well. even on a device like the G2/DZ that seems to take to higher clock speeds relatively easily, there are bound to be some that aren't as happy with the increased workload.
if I think of any other bright ideas, I'll let you know. I haven't played with baconbits a lot.
pmcqueen said:
hehe, didn't even read what rom you were using. my bad.
kernels aside, it is very possible, as you mentioned earlier, that you guys got the chips in the stash that don't take to overclocking very well. even on a device like the G2/DZ that seems to take to higher clock speeds relatively easily, there are bound to be some that aren't as happy with the increased workload.
if I think of any other bright ideas, I'll let you know. I haven't played with baconbits a lot.
Click to expand...
Click to collapse
Actually, after installing Pershoot's most recent kernel, I have no problems. Maybe I just got lucky here.
Because I suffer some problems in the vision, I bought a Nook Simple Touch to perform some of the functions performed with my asus transformer but with an electronic ink display. I must say I'm quite satisfied with its functionalty, but despite having to severely limit my hours in front of screens, I could not resist to modify the kernel.
The kernel adds frequencies of 1GHz and 1.1GHz, besides being modified to compile using gcc 4.7 from Linaro. I've also changed some compilation options.
The kernel includes the modifications for multitouch.
Attached the patch for the original source code 1.1 and my build.
Don't forget to rename the uImage.img to uImage (renamed it to allow the uploading)
Since version 2, the kernel support the normal and glow versions.
REMOVED temporarily
Very nice to see you Guevor. I am currently still running one of your kernels for the Transformer. Hopefully you can do the same magic over here.
@All, Guevor knows what he is doing and is always willing to help and troubleshoot with you. Above all, if you have bugs, Logcats are best but detailed explanations are almost just as helpful.
whoa! guevor here!!! :good:
Thanks, but a question
Can voltage control be added? The nook would probably benefit hugely from undervolt.
notriddle said:
Can voltage control be added? The nook would probably benefit hugely from undervolt.
Click to expand...
Click to collapse
from everything I've read, undervolting provides only a very minimal gain in battery life (we're talking about max a couple of procent)
The voltage is not fixed for each frequency, so it is modified while working, and the only thing that is fixed is the nominal value.
I have looked very little about this board, but that is what I have seen so far.
I made a compilation reducing the nominal value, but do not think it changes much.
I've also tweaked some latencies and have limited the overclocking to 1Ghz (better relation).
I've done some testing and I can see that using ondemand, the lower rate (300Mhz) is much more used, so consumption should be reduced.
can someone explain how to install this kernel?
pet4a said:
can someone explain how to install this kernel?
Click to expand...
Click to collapse
You first need to rename the uImage.img to uImage
Then you need adb on your computer and be connected on the same net (computer and nook).
After that, you can use these instructions.
http://forum.xda-developers.com/showpost.php?p=24168019&postcount=21
I hope it will be helpful
Thank you for this uImage Hmm...is it really to have USB host support too in this kernel? And support for the NST Glowlight? Thanks.
Filippios said:
Thank you for this uImage Hmm...is it really to have USB host support too in this kernel? And support for the NST Glowlight? Thanks.
Click to expand...
Click to collapse
bump for USB host.
also.. at 1000 MHz system seems to be working noticeably faster (placebo effect?). Thanks for compiling this kernel.
Zorkman said:
from everything I've read, undervolting provides only a very minimal gain in battery life (we're talking about max a couple of procent)
Click to expand...
Click to collapse
This is true on smartphones because most of the battery life is consumed by the display and the cell radio. There is no cell radio on the NST, and the display consumes far less, so a larger percent of the battery consumption is from the CPU and undervolting should be more effective. (let me know if I'm wrong here)
Please clarify re:Glow
Could someone please clarify whether this kernel includes support for the Glow?
I found a mt kernel for the glow from mali100 here: http://forum.xda-developers.com/showthread.php?t=1679036
so i know the nst kernels can be patched for the glow: but I'm unclear whether this kernel, which I'd much rather use for the overclock, has been so patched.
Thanks!
Oh, and my vote is to keep the usb host support in a separate kernel due to battery drain.
-Alley
guevor said:
You first need to rename the uImage.img to uImage
Then you need adb on your computer and be connected on the same net (computer and nook).
After that, you can use these instructions.
http://forum.xda-developers.com/showpost.php?p=24168019&postcount=21
I hope it will be helpful
Click to expand...
Click to collapse
fallowed the instruction but after i reboot the device its freezes on read forever screen
am i missing something?
a7t7d said:
Could someone please clarify whether this kernel includes support for the Glow?
Click to expand...
Click to collapse
I don't think it supports the glowlight, but you can just try it. The worst that could happen, is that the screen light doesn't work as long as this kernel is installed.
I found a mt kernel for the glow from mali100 here: http://forum.xda-developers.com/showthread.php?t=1679036
so i know the nst kernels can be patched for the glow: but I'm unclear whether this kernel, which I'd much rather use for the overclock, has been so patched.
Click to expand...
Click to collapse
That's not a patched nst kernel, it's a glowlight kernel (based on the 1.1.5 nook software). Glowlight kernels work just fine on the old nst.
So what I'm trying to say is:
nst kernel on a glowlight -> works fine, just no support for the screenlight
glowlight kernel on a nst -> works perfect, no issues.
Oh, and my vote is to keep the usb host support in a separate kernel due to battery drain.
Click to expand...
Click to collapse
I second that, usb host is just not stable enough to be a default for everyone, particularly because a lot of people have no use for it.
pet4a said:
fallowed the instruction but after i reboot the device its freezes on read forever screen
am i missing something?
Click to expand...
Click to collapse
Maybe your device does not support the overclocking or may need more voltage.
What version did you use? The original post had a nominal voltage slightly higher.
mali100 said:
I don't think it supports the glowlight, but you can just try it. The worst that could happen, is that the screen light doesn't work as long as this kernel is installed.
That's not a patched nst kernel, it's a glowlight kernel (based on the 1.1.5 nook software). Glowlight kernels work just fine on the old nst.
So what I'm trying to say is:
nst kernel on a glowlight -> works fine, just no support for the screenlight
glowlight kernel on a nst -> works perfect, no issues.
I second that, usb host is just not stable enough to be a default for everyone, particularly because a lot of people have no use for it.
Click to expand...
Click to collapse
Good to know. I'll take a look and if I find no problem, I'll do a single kernel for both.
About the usb host had not even tried, but if you say it is not stable, better to keep two versions.
As a novelty, I have been making tests with the display and I'll upload a new version. I am also uploading a video I have just done to show how it works.
New version with a new fast display mode
I've been testing the epaper's driver, both to see how it work and to testing if I could get something new.
I added a parameter (/ sys/devices/platform/omap3epfb.0/graphics/fb0/fmode) that can enable a new fast mode.
By default starts at 0, so it works very much as always (although I modified some behavior, I have to do more tests), and if we put it to 1 enables a new faster mode.
To not extend much (and avoid being too much in front of the computer screen), I recorded a video showing the new mode, and also put a couple of images to compare the normal mode with the new one.
I have also created a small program that will allow us to switch between the two modes (I use the Reading now button for it)
Hope you are interested.
Thanks for the kernel.
However, I've installed the new version (in the previous post) using clockwork recovery (zipfile) but seems that overclock is inactive. Checked with "Android System Info" app.
EDIT: Reflashed using ADBWireless, now 1 GHz is recognized. And "Fast Mode" is far better than "No Refresh" when browsing web and testing games.
guevor said:
Maybe your device does not support the overclocking or may need more voltage.
What version did you use? The original post had a nominal voltage slightly higher.
works.
Click to expand...
Click to collapse
nook ver 1.1.2 rooted using touchnooter.
i used B&N update to revive my nook.
enrsil1983 said:
Thanks for the kernel.
However, I've installed the new version (in the previous post) using clockwork recovery (zipfile) but seems that overclock is inactive. Checked with "Android System Info" app.
Click to expand...
Click to collapse
"CPU Master Free" shows 1000 MHz in Performance mode.
- Can you add USB HOST support to this Kernel? It would make this one the best kernel available.
Thanks
- from time to time while the wifi is on, Nook freezes.
Hi Guevor,
This is really cool stuff! Thanks!
BTW some people tried to upgrade from Eclair to Froyo but all them got stuck at some point, apparently there are problems with the drivers that are closed source, but I dont see why can't we take the drivers for a similar device that uses Froyo. What is your opinion on this?
I'd be happy to help so you can minimize the amount of time in front of the computer
Gracias!