Related
Everytime I try flashing Anything with toasts custom kernel my phone just wants to up and die, If play with the phone and am patient enough I can sometimes get one boot, that eventually crashes and never comes back as I just see a solid HTC logo.
I'm also finding every-time I try booting, while looked up to the computer trying to get a logcat or at least something it appears my phone is malfunctioning to the point it only appears as an unknown device if it even shows.
I've tried Freshtoast, IC3rom and the newest Darchdroid to no avail.
I'm thinking i just got cursed with subpar chips from htc and that perhaps it doesn't even like the lower 710 mhz overclock, anyone else experiencing this?
Just frustrated, if anyone would be willing to give input or plain help it'd appreciated knowing that time is valuable, There is great work at foot here.
Edit: Just about had to shove my foot in my mouth, got a boot started right before I posted, Saddly it isn't booting reliably let it set up
logged into my google account and tried to restart the phone, same luck I've been having has decided to hard reset? "Vibrates and screen flash" 4 Times in the past 5 minutes
well I am not sure what you have and havent tried, but a few things to check first. Is your sdcard setup for apps2sd? if so did you wipe that also when you are switching roms?.
Did you wipe your data between roms?
Have you tried just a stock rom, such as http://forum.xda-developers.com/showthread.php?t=681697 . this is completely stock of the final 2.1 release. Wipe everything including your ext partion on your sdcard, if you have one.
Thats at least a starting point to see if you dont have faulty hardware. You honostly should have no problem getting that to work.
Try Zen's slide rom. I too could not boot a single overclocked rom, until I tried that one. Is overclocked, but boots up at 480, and no bfs or compcache, so I don't know what makes it work, but it does. Once in, I was able to overclock to 691 (stock is 528), and I get neocore scores of 32-33 fps consistently, linpacks at 2.9-3.1, so almost right there with those going to 767, definite improvement over stock. Anyways, try it, my favorite sense rom by far.
I'm having these issues too... I want DarchDroid....
Actually, darch's latest booted finally for me! It's a new update, go try it!
-------------------------------------
Sent via the XDA Tapatalk App
danaff37 said:
Actually, darch's latest booted finally for me! It's a new update, go try it!
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
You're right!!!!
Lol Looks like alot of people were having the similar, Ironcily after flashing to the newest recovery darch posted updating from Godspeed darchdroid booted right up for me, Haven't tried any of the other roms with the newer kernel but darch hauls serious arse
danaff37 said:
Try Zen's slide rom. I too could not boot a single overclocked rom, until I tried that one. Is overclocked, but boots up at 480, and no bfs or compcache, so I don't know what makes it work, but it does. Once in, I was able to overclock to 691 (stock is 528), and I get neocore scores of 32-33 fps consistently, linpacks at 2.9-3.1, so almost right there with those going to 767, definite improvement over stock. Anyways, try it, my favorite sense rom by far.
Click to expand...
Click to collapse
Aye Zen did a pretty sweet job on it, If I have to use sense thats the rom with the goodies I really like, more so when he managed to get rid of all the purple and pink from it.
I had the same issues. I loaded the overclock widget and set it to 480 then updated the kernel to .29. Seemed to work. I got it up to 691 before I had lock up issues. 768 is 3 seconds.
jrbooth3 said:
I had the same issues. I loaded the overclock widget and set it to 480 then updated the kernel to .29. Seemed to work. I got it up to 691 before I had lock up issues. 768 is 3 seconds.
Click to expand...
Click to collapse
That's an interesting fix. I'm going to try that, as I've had issues flashing any rom that is OC'd (trying DC 2.08.1 .29 kernel right now using your suggestion)
Edit: That still did not work for me for DC. I'm at a loss.
murdocthc said:
That's an interesting fix. I'm going to try that, as I've had issues flashing any rom that is OC'd (trying DC 2.08.1 .29 kernel right now using your suggestion)
Edit: That still did not work for me for DC. I'm at a loss.
Click to expand...
Click to collapse
Did you set it to run on boot?
A_Guy71 said:
Did you set it to run on boot?
Click to expand...
Click to collapse
I did. My phone will not boot any OC'd ROM. I've been trying for about a week now...not sure what else to try.
As of DarchDroid 2.6.5, it is no longer working on our "sub-par" phones.
If anyone needs 2.6.4 and the dl link is not up, just let me know.
And he added bfs back in, I know it doesn't make sense, but I wonder if that's what is doing it, it's one of the few similarities between darch droid and zen slide that is different in all others.
-------------------------------------
Sent via the XDA Tapatalk App
Hello!
I am using CM6 and I got some gliches after this instruction Nexus one hack - How to overclock nexus one
- Camera and flashlight led wont work any more
- SD card is crazy, it works then it wont work
- Same for youtube application
- Wlan bugs, stop working and then works.
I can continue this list for ever...
So now I thing that I installed too old version of zimage.
How to flash newer version where to get it and how and will it help?
Don't overclock, and generally don't do things until you understand what you're doing. Return to the regular build of CM6 by flashing it through recovery. It won't erase your data.
Jack_R1 said:
Don't overclock, and generally don't do things until you understand what you're doing. Return to the regular build of CM6 by flashing it through recovery. It won't erase your data.
Click to expand...
Click to collapse
Wipe Is not needed?
No, not needed unless you want to lose all data.
YAY! The camera is working again, but I am sad cuz I lost my 1,113.
Maybe there is a better kernel with camera working?
Because i liked that 1,113 so mutch.
elkyur said:
YAY! The camera is working again, but I am sad cuz I lost my 1,113.
Maybe there is a better kernel with camera working?
Because i liked that 1,113 so mutch.
Click to expand...
Click to collapse
Seriously? Please enlighten us, what are you missing. Benchmark numbers?
khaytsus said:
Seriously? Please enlighten us, what are you missing. Benchmark numbers?
Click to expand...
Click to collapse
i could show the power of nexus one to iphone fans.
The phone loaded settings and calendar very fast.
It always does. I don't think this 10% boost suddenly turned it into super-duper-lightning-fast?
why the hell its only 10percent, while evo 4g with same proccessor almost 30%.
You need to push overclock to 1267 MHz for it to be ~30%. Easy math. 1113 / 998 ~= 1.10 ~= 10% overclock.
elkyur said:
i could show the power of nexus one to iphone fans.
The phone loaded settings and calendar very fast.
Click to expand...
Click to collapse
There's a word for that: MOAR.
In most contexts, this word means that someone wants "more" of some random thing for no reason or for a nonsense reason. Except when paired with bacon. MOAR BACON is acceptable.
MOAR GIGGITYHURTZ, not acceptable.
default CM6 kernel allows you the OC to 1113.
yes ty! I can over clock it without that stupid kernel,
Why can't I overclock my nexus to 1.3 when you can with dvi 4h
To stop wasting everyone time just update to a latest kernel by pershoot or be on the original cm kernel. Both are almost same n both overclock
Latest Cyanogenmod nightly number 97 (10/3/2010) has the new ril baked in. No need to use this patch if you are running it or a newer one.
Back Story
Long story short, the Chinese group Miui mananged to get / build (not really sure) a new Radio Interface Layer for our HTC devices... I pulled this file out of the Nexus one build that they released and it works perfectly. Link to the Nexus1 version
Over in the Nexus one forum a few people have questioned where this Chinese group got some of the files they're using, as they're really bleeding edge (at least thats what they say in the N1 forum). This newer / different RIL file seems to fix the issues we're facing with random phantom reboots while wifi is on. Also included in this is the issue where the signal bars show an "x" for a second or two after connecting to a wifi hotspot. Also fixed are issues where the radio signal drops before / after receiving a call that plagues AOSP builds (ruby and CM for sure).
Cyanogenmod 6.xx
This works on the 6.xx versions as well as the Nightlies.
NOTICE: As of Oct 2nd this has been "committed" so I assume the nightly that comes out this evening will have the fix built in. Check it out
Latest nightly number 97 has the new ril baked in. No need to use this patch.
Ruby 1.1.1
This works for Ruby. If you are wanting the BT Media Streaming audio fix as well, please see this thread. They are two separate installs.
Shadowrom
It has been confirmed that this also works for Shadowrom.
Bugs
I honestly don't know of any yet... but that doesn't mean there aren't any. Only a handful of us have been testing this thing out on the inc so far. Figured more people might want to check it out.
Credit
I take no credit for the fix. The Miui group built/got it(not sure which), I simply happened to be playing around with some files and noticed the side effects. Thanks again to Jermaine for letting me know more about the rom (and the fact that they weren't plagued by our reboot issues) in the first place so I could start digging...
Of course thanks go out to the entire ruby and cyanogenmod teams, without them we wouldn't have these fun roms. Lastly, IncredibleDoes for doing the Inc port of miui that opened our eyes to it.
Installation
- Download the file and place it on your SD card.
- Load up Rom Manager and hit "Install rom from SD card," select the file.
- I'd probably make a nandroid backup if you haven't recently just in case... no wipe has been needed.
Disclaimer
If this messes up your phone, not my fault Was tested by about 30 people so far, and no issues that we've seen. Please make a nandoid backup just in case.
THIS IS FOR AOSP roms listed above ONLY. Please do NOT install it on any sense based roms.
Downloads
see below
Latest Cyanogenmod nightly number 97 (10/3/2010) has the new ril baked in. No need to use this patch if you are running it or a newer nightly .
dnoyeb said:
Also included in this is the issue where the signal bars show an "x" for a second or two after connecting to a wifi hotspot.
Click to expand...
Click to collapse
Isn't this just cosmetic? Or because the phone is switching from 3G to 1x? I've never dropped a call while toggling WiFi on...
larsrya8 said:
Isn't this just cosmetic? Or because the phone is switching from 3G to 1x? I've never dropped a call while toggling WiFi on...
Click to expand...
Click to collapse
Not that I can tell... so far the mere fact that the wifi isn't causing reboots anymore is the main reason I'm putting this out there...
anything else is just gravy.
dnoyeb said:
Not that I can tell... so far the mere fact that the wifi isn't causing reboots anymore is the main reason I'm putting this out there...
anything else is just gravy.
Click to expand...
Click to collapse
Fixing the WiFi reboots would be great. Though, strangely, I'm at 110 hours uptime with the WiFi on... I guess it'll take a while to verify this fix works.
larsrya8 said:
Fixing the WiFi reboots would be great. Though, strangely, I'm at 110 hours uptime with the WiFi on... I guess it'll take a while to verify this fix works.
Click to expand...
Click to collapse
sounds good. in all reality the one person who can really verify is koush... sending him the idea as well...
(wish I could make it 110 hours! hah... at my office i'm lucky if I get more than 3 hours) so today will be a major test of it. so far so good.
dnoyeb said:
sounds good. in all reality the one person who can really verify is koush... sending him the idea as well...
(wish I could make it 110 hours! hah... at my office i'm lucky if I get more than 3 hours) so today will be a major test of it. so far so good.
Click to expand...
Click to collapse
Good job! I hope that solves it since we've determined the kernels don't.
jermaine151 said:
Good job! I hope that solves it since we've determined the kernels don't.
Click to expand...
Click to collapse
all thanks to you bud will update credits with backstory if all goes well.
dnoyeb said:
all thanks to you bud will update credits with backstory if all goes well.
Click to expand...
Click to collapse
Totally thanks to you! I'm just glad that you were persistent on resolving it.
Please please let Koush know about this, too. Nice work man.
Asterdroid said:
Please please let Koush know about this, too. Nice work man.
Click to expand...
Click to collapse
if it works, sure going to send out the links shortly... testing the installer on another phone really quick.
YGPM.
I'll guinea pig my phone for a few days if it means getting CM running w/o locks or reboots.
I'll try out the ruby one!
Sent from my ADR6300 using XDA App
I'd be more than happy to help test either CM or Ruby (Ruby preferred). Just PM me the info!
Installed the fix on Ruby 1.1.1. Running stock Ruby Kernal (This kernal has been the best overall performance Kernal for me on Ruby). Will report back results
I've installed the file you sent me... and holy crap. It seems to work. Really hope this does it or at least puts koush in the right direction.
Sent from my ADR6300 using XDA App
ncwildcat said:
Installed the fix on Ruby 1.1.1. Running stock Ruby Kernal (This kernal has been the best overall performance Kernal for me on Ruby). Will report back results
Click to expand...
Click to collapse
I am very interested to see the results on the stock one... I forget, does the stock kernel have working wifi tether?
I am packing up a BT-Fix for Ruby right now but will keep it separate, to not complicate things.
camalus said:
I've installed the file you sent me... and holy crap. It seems to work. Really hope this does it or at least puts koush in the right direction.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
You and me both man... if most testers go a good 24 hours with no wifi caused reboots / drops etc, maybe he'll look at it...
Keep us informed of the progress! thanks for testing.
Just in case you are curious.. I'm running koush test 2 kernel. No setcpu installed.
Sent from my ADR6300 using XDA App
I have had good luck with wifi teather on the stock kernal...didn't work on any of the king kernals.
Sent from my personal space
I really dont believe its the wifi. Its when the 3g turns on or off when the issues happen, which is when you leave or enter a wifi area. I turned 3g off and didnt use it for 2 days with wifi on the whole time with no reboots. I've have the lockup with just 3g on as others have noted. Also I believe that the lockups and the reboots are a separate issue. I have yet to see where any dev said it was the wifi directly, and with the known issues of 3g+froyo it points to 3g not wifi.
So, if you turn wifi off and are in a good 3g area then you will unlikely lose 3g much if at all, but if you have signal issues then the reboots still exist.
If we are going to find out what the problem is we need to setup test groups.
1 - no wifi, no 3g
2 - no wifi, 3g on
3 - wifi on, no 3g
4 - wifi on, 3g on
Make sure everyone is using the same rom/radio.
nfiniti9 said:
So, if you turn wifi off and are in a good 3g area then you will unlikely lose 3g much if at all, but if you have signal issues then the reboots still exist.
Click to expand...
Click to collapse
That's a possibility, but I think I'm in a good 3G area, and the majority of my movements are in a pretty small geographic area. I'll get reboots when my phone is just sitting on a table or in my pocket though in an area w/ strong signal.
Make sure everyone is using the same rom/radio.
Click to expand...
Click to collapse
I think what we'd really need is for the testers to check all 4 combinations. There's too much geographic variance to have a bunch of different people testing these combinations unless some lived very close to each other.
Hey guys,
Just to let you know there is an application out there now to take care of force recalibration of the screen.
When I first got my nook I know it didn't register touch properly, so I ran some commands and it started working fine.
Decided I should make my first app something that helps people, so here you go. Checkout "nook screen recalibrate". It's a simple minimalistic application the re calibrates then reboots
Updated Version 2.0
* Better GUI
* Button to start process
* Lowered MinSDK to support froyo (untested)
Here's the market link.
Helpful since you don't have enough posts to post links yet. But thanks for this app!
Ironically when I go to the link and try to push it to my NC, it says it's not compatible. :X
Fine print mentions that is only works with GB (android 2.3 and above).
yep.. i dont think any rom uses anything lower than that
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
assid2 said:
yep.. i dont think any rom uses anything lower than that
Click to expand...
Click to collapse
The nookie froyo is based on 2.2.
If your software doesn't require 2.3 functionality, can you lower the required API to '7', which is the stock Android API level (2.2/Froyo)?
nolook said:
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
Click to expand...
Click to collapse
Not sure what exactly that application does.so can't comment.
Sent from my Nexus One
byronczimmer said:
The nookie froyo is based on 2.2.
If your software doesn't require 2.3 functionality, can you lower the required API to '7', which is the stock Android API level (2.2/Froyo)?
Click to expand...
Click to collapse
I think it should work. I shall reduce the requirements.
However there is no way to check cause my touch is working perfect now
However I find it performs better slightly if I do this once a week
Sent from my Nexus One
Updated release v2.0
Updated to version 2.0
* Better GUI
* Button to start process
* Lowered MinSDK to support froyo (untested)
Force closes on nookie 2.2
cowballz69 said:
Force closes on nookie 2.2
Click to expand...
Click to collapse
Strange, I had reduced the minimum requirements
I have no other froyo device to test on, let me check once again against an emulator
Sent from my Nexus One
Ok maybe this is in my head, but if I run this every couple nightlies, touch feels slightly better and responsive.
Maybe it's the nightly, maybe the way it interacts, maybe the screen de sensitises over time, maybe it's all in my head
If anyone cares to do some testing, that would be great
Sent from my Nexus One
cowballz69 said:
Force closes on nookie 2.2
Click to expand...
Click to collapse
Let me know if you wanna try this so I can publish to the market
Sent from my NookColor using Tapatalk
This may sound crazy but after running this I think that the screen is actually leases responsive and now shows the "ghost" touches so badly that the on screen keyboard isn't usable. Is there something to do to fix this?
Try cleaning your screen prior to running the application, make sure you don't touch the screen prior to restarting
Sent from my Nexus One using Tapatalk
kruuth said:
This may sound crazy but after running this I think that the screen is actually leases responsive and now shows the "ghost" touches so badly that the on screen keyboard isn't usable. Is there something to do to fix this?
Click to expand...
Click to collapse
same thing on my end. I ended up reflashing the latest cm7 nightly and its back to the way it was
Sent from my NookColor using Tapatalk
That's extremely strange. First time I've heard issues like this crop up. Do you have a screen guard or something
Sent from my NookColor using Tapatalk
For those who would want to try, scews the S2.
But the link from nolook actually fixes it.
nolook said:
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
Click to expand...
Click to collapse
edit: only fixed it for a short time. i'm back with some bad touch.
can you attach the .apk i cant go to market to download!! plsss
Any good 2.3 ROM or later with both Camera and HDMI working?
baastrup said:
Any good 2.3 ROM or later with both Camera and HDMI working?
Click to expand...
Click to collapse
I think that the Sharp rom has hdmi and camera and Radio working, it is 2.3.5. But you will have to revert to stock to uninstall. However it is not AOSP. It is a stock rom.
http://forum.xda-developers.com/showthread.php?t=1437512
Thanks for the reply.
The Sharp ROM made endless bootloop, so im back on Aplha4.
baastrup said:
Thanks for the reply.
The Sharp ROM made endless bootloop, so im back on Aplha4.
Click to expand...
Click to collapse
Either you had bad upgrade or you hardware is slightly different than my u9000-81 Sorry.
I grabbed my Huawei U9000 and flashed to Taiwanese Sharp ROM.
Seems to be running smoothly except the speakerphone is strangely soft and blur in a phone call. It works loud and clear in YouTube/video playback.
Also, I find the touch screen a bit funny as it may not response to anything at random... then I switch off the screen and turn back again, everything's back to normal.
Could this be a hardware issue or a software/driver one?
Second bug is that the camera does not save saturation/sharpness/contrast settings.
Also, apart from the Taiwanese Sharp ROM, any modded ROM can make use of HDMI connection?
I've made this on YouTube, hope you guys enjoy it.
conradwu said:
I grabbed my Huawei U9000 and flashed to Taiwanese Sharp ROM.
Seems to be running smoothly except the speakerphone is strangely soft and blur in a phone call. It works loud and clear in YouTube/video playback.
Also, I find the touch screen a bit funny as it may not response to anything at random... then I switch off the screen and turn back again, everything's back to normal.
Could this be a hardware issue or a software/driver one?
Second bug is that the camera does not save saturation/sharpness/contrast settings.
Also, apart from the Taiwanese Sharp ROM, any modded ROM can make use of HDMI connection?
I've made this on YouTube, hope you guys enjoy it.
Click to expand...
Click to collapse
I had the same experience thats why i used Volume+ to increase dB
Dont set to full extend +12dB is like the limit. Going over would make no changes or may also result to distorted audio.
since we're on the same topic of 2.3 ROMs with camera and HDMI.. id like to ask, which rom has HDMI and can be overclocked?
As far as I have found so far, overclocking is kernel dependant. And so is HDMI.. that means I can't have a kernel that allows overclocking and has HDMI function right?
cheezzzz said:
since we're on the same topic of 2.3 ROMs with camera and HDMI.. id like to ask, which rom has HDMI and can be overclocked?
As far as I have found so far, overclocking is kernel dependant. And so is HDMI.. that means I can't have a kernel that allows overclocking and has HDMI function right?
Click to expand...
Click to collapse
The older UC kernels for the android RC 2 supported overclocking / HDMI AFAIK
Sent from my CSL-MI410 using XDA
whyzee said:
The older UC kernels for the android RC 2 supported overclocking / HDMI AFAIK
Sent from my CSL-MI410 using XDA
Click to expand...
Click to collapse
ooh but I've heard bad things about that RC2 kernel lolol..
mehh.. ima see how my phone performs on 1ghz for now.. if its the same then i may just go back to Maclite heh