Related
for some reason, the 2 times ive flashed custom roms on my phone modaco 1.1 and 1.2 the internet stops working. everything else works perfectly find and the evdo sign shows up, but the internet just does not work. any work around?
and why is it that everytime i try and restore from recovery on my phone, it says
error : run 'nandroid-mobile.sh
restore' via adb!
im guessing i have to run it via my computer and if i do what do i type in??
Joecrack305 said:
for some reason, the 2 times ive flashed custom roms on my phone modaco 1.1 and 1.2 the internet stops working. everything else works perfectly find and the evdo sign shows up, but the internet just does not work. any work around?
Click to expand...
Click to collapse
Several people have reported this, have you tried Fresh rom? Not saying anything against MoDaCo at all, but it seems people have intermitent data issues.
Joecrack305 said:
and why is it that everytime i try and restore from recovery on my phone, it says
error : run 'nandroid-mobile.sh
restore' via adb!
im guessing i have to run it via my computer and if i do what do i type in??
Click to expand...
Click to collapse
This thread may help but I haven't read through it all. Don't know if the answer is there or not.
http://forum.xda-developers.com/showthread.php?t=532719
thanks ill try that and for some reason restore never ever works on my damn phone and the backups are on my phone pretty weird but thanks again
I am running the new Fresh 1.0, he released it last night or this morning. It is GLORIOUS! I LOVE IT. Except, I think the lock screen is a little ugly, I can deal with it though. There are ways to change the lock screen which I may do later today.
i want to use clear as a bell but that doest work yet on 1.0 correct?
post back a link to it and I will load it up and see if it works. Saves you the effort, and i was planning on trying other stuff anyways. Who knows I may like it.
http://forum.xda-developers.com/showthread.php?t=594274
ok just downloaded fresh 0.7 everything works again except internet calls sms everything but no internet???
Just looking back through previous threads of yours. You have run RUU and everything havn't you?
I am at a loss if you have done the RUU and still get no data.
idk what the hell is the problem i ran the ruu back to stock internet is fine i rooted internet still fine flash recovery internet fine install rom internet dead lol
Yeah, thats really odd. Do you have any Root apps installed? Other than maybe WiFi Tether. DroidWall? App manager? anything that could be killing or blocking 3G?
i had droid wall just uninstalled and rebooted i also have overclock widget does that effect it? shouldnt right?
Droid Wall definetly woudl break internet. Maybe it left some stuff behind on the uninstall? A setting or something? Apps2SD is on, it may still have stuff on the SD card. You could try to format it again since you cant actually see that partition...long shot though.
Does the Over Clock widget work? See a difference?
it was droid wall you my friend are the ****! (in a good way of course) lol
might sound stupid but yea overclock does feel like it really work lol. going thru the menu seems so much faster! and when your not using the phone you dial it all the way down, and it really saves the batter
Android 200456, Karl +1 SCORE!
Glad you got it fixed.
people at work are going to hate me lol, i had a customer come in and he was like =O ill pay you lol.i might have to do a side business lol
tethering doesnt work for me on 0.7 =/ it says start tethering stays there then it says su request but it doesnt let me hit always allow because the options dont even show up =/
You should have a Super USer Permisions app in the app drawer. See if the permisions for the app are in there. If they are, long press and delete them. If not, you may have to get the APK for the latest build and push it. Make sure that you Allow all, its the only way mine works at least, otherwise i dont get access.
sorry the reply took so long I didnt get an email that you posted back.
Hi All,
I have a problem where my phone crashes and reboots when I launch an app that uses the camera in any way, for example layar, barcode scanner, camera etc. This only happens in Android 2.1, I've tried various ROMs and always the same issue. I've tested Android 1.5 and there are no problems with that at all.
I've noticed the crashes only occur when I'm on battery power, it never happens when the phone is plugged in so I cannot get logs to see what is going on, unless someone knows a way to get the logs from a crash.
I was wondering if anyone else has seen this problem and if so, if they've found a resolution to it.
Since updating with the OTA 2.1 update I have been experiencing this problem too. Phone reboots when it uses the camera, Layar, Yelp, AugSatNav all seem to cause the problem.
I get this problem too, with the camera, and also sometimes when I put the volume down it freezes and reboots
Sent from my HTC Hero using XDA App
I've got the same problem. Restarting when launching apps using the camera.. Im glad that's not a HW problem but "only" SW bug.. I hope
It could (and probably is) a radio issue....Happens on the N1 and Desire if you try to use the camera too and seeing as the GPS,Camera both are dependant on the radio id say that is it! Find the radio reccomended with the rom you use and flash it( Beware of orange users being locked down though,you need a specific radio)
Just to add that I'm getting the same problem too running FroydVillain 1.2.2 and baseband 6.35.15.14, should point out that been having the problem for quite a while on a multitude of ROMs :-(
I'm not - did you full wipe?
Multiple wipes...
try 1.3 i guess
I had this problem when I was on stock 2. 1 I would recommend rooting and flashing froydvillain.
Sent from my HTC Hero using XDA App
Tried multiple ROMs and multiple Radios with no change :-(
Unless theres a second secret wipe button hidden in recovery I don't know what else I can do :-/
try to disable "automatic brightness"...
Gynjanynja said:
I had this problem when I was on stock 2. 1 I would recommend rooting and flashing froydvillain.
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
Hi,
I have had this problem since i went to 2.1 also, i have also flashed several rom's since villainrom 12 and have even used rcmix 1.0b which is a great 2.1 imo.
Have flashed 2.2 roms, and i am still having the same problem.
This is how i can replicate this problem and how it occurs, to the letter.
1.Bring phone out of lockscreen.
2.Open camera.
3.Take pic, in dark or light lighting with brightness on any setting.
4.Save pic.
5.Close camera.
6.Lock phone and wait for 10 seconds.
7.Bring phone out of lockscreen.
8.Open camera.
9.Phones lights all go out and the hero name flashes up onto the screen.
10.Full reboot.
This happens everytime no matter what.
Some things to consider.
The phone will never reboot if it is plugged in to a usb / electric plug Charger and is actually charging.
The phone will remain on and will carry on taking pictures IF you don't close out of the camera the first time around.
No task killer was installed on my phone at the time of this test, although i have had task killers before with the same results.
Lighting effects and brightness can sometimes have an effect on the ratio and probablility of a reboot, with brightness on full in a dark room being the most probable.
I am using the newest froyd rom 1.4.3 although i have tried pretty much every rom out there, I NEVER have this error when i installed a 1.5 rom which does not have apps2sd (weird that) which tells me that it is NOT a hardware fault.
I am using villains no logo kernel 19mhz - 691mhz
63.18.55.06PH_6.35.15.14 Radio
HTC Hero on Orage UK.
IF anybody can shed any light on this rather annoying matter resulting in this problem being erradicated will earn my eternal respect and a big clock. : )
dladz said:
This is how i can replicate this problem and how it occurs, to the letter.
1.Bring phone out of lockscreen.
2.Open camera.
3.Take pic, in dark or light lighting with brightness on any setting.
4.Save pic.
5.Close camera.
6.Lock phone and wait for 10 seconds.
7.Bring phone out of lockscreen.
8.Open camera.
9.Phones lights all go out and the hero name flashes up onto the screen.
10.Full reboot.
This happens everytime no matter what.
Click to expand...
Click to collapse
I can confirm that this isn't a bug on every install of 2.1 or 2.1 as I am unable to replicate the issue as described. Also if you've tried mutiple software and the bug is occurring across many that would suggest it is something hardware related or you are not performing a full wipe. Have you tried backing up the data on your sd card and formatting that then putting back only the necessary data (pics / music etc)?
btdag said:
I can confirm that this isn't a bug on every install of 2.1 or 2.1 as I am unable to replicate the issue as described. Also if you've tried mutiple software and the bug is occurring across many that would suggest it is something hardware related or you are not performing a full wipe. Have you tried backing up the data on your sd card and formatting that then putting back only the necessary data (pics / music etc)?
Click to expand...
Click to collapse
I originally posted this issue and the descriptions from everyone else with the problem match mine pretty much perfectly.
I've taken all info off the sd card and performed a complete wipe of data, ext and davlik before formatting the sd card. I've put the blank SD card (apart from the ROM I'm about to flash) back into the phone and flashed. After config and before any new apps are installed on the phone I launch the camera and within 4 attempts at start the camera the phone will crash. This has happened across every 2.1 ROM I've tried, but doesn't happen on 1.5 ROMs.
Using the stock camera app? Have you tried without installing any of your own apps at all?
This is very odd. No matter what I try I can't get the camera app to crash. Though I am using v2.2 of android. Have you tried official 2.1? Vanilla and Sense?
btdag said:
Using the stock camera app? Have you tried without installing any of your own apps at all?
This is very odd. No matter what I try I can't get the camera app to crash. Though I am using v2.2 of android. Have you tried official 2.1? Vanilla and Sense?
Click to expand...
Click to collapse
Yep, it crashes using the stock app.
I've tried a rooted version of the offical but not the actual OTA update. I've not tried vanilla as I don't really want to run vanilla on it.
I've managed to take some logcat logs of the problem happening but there's nothing really specifc happening over a few crashes that would point to anything. .
I'm going to try to unroot my hero and downgrade to stock to start again. Just have to find a way to downgrade my bootloader first so I can put on the original RRU. I tried to downgrade before but got an invalid bootloader error.
The camera crash doesn't really affect me day to day as I don't really use the camera, where it is annoying is it stops you using apps that use the camera like goggles and layar.
Ahh - so its not the camera app that is crashing but other apps too which are using the camera. Very odd.
And FYI - you don't need to touch your bootloader - just change the driver in windows to My HTC instead of HTC Bootloader and the rru will work.
btdag said:
I can confirm that this isn't a bug on every install of 2.1 or 2.1 as I am unable to replicate the issue as described. Also if you've tried mutiple software and the bug is occurring across many that would suggest it is something hardware related or you are not performing a full wipe. Have you tried backing up the data on your sd card and formatting that then putting back only the necessary data (pics / music etc)?
Click to expand...
Click to collapse
I have formatted and re partitioned my sd card to a T and it still occurs and thats with everytime i install a new rom, i don't use titanium i go the long way around every time and re set up all my programs, I know i can replicate this error like i said and like i also said this does not occur in 1.5 roms.
I have also have this problem with vanilla, modaco's new one, villain rom, rcmix, froyd, it appears that ever since the phone was updated to 2.1 there is a problem when using the camera app.
I have tried to install a rom and replicate the issue without installing any apps at all and it still persists, the only thing i can say is that it doesn't happen when i'm either on 1.5 OR the phone is charging?
It sounds like the the phone is requesting access for use of the camera and then not putting back what it requested in the first place, like a cache or something, and it simply make the phone reboot when it is called upon again.
I don't believe it is a hardware fault, i know this sounds like wishful thinking but the phone does not have this error in 1.5 roms. Thus, it cannot be hardware. Simple!
Also a logcat does not show anything, i was only able to replicate the error once whilst my phone was plugged in, it just won't do it again, and when i posted my findings on villainroms bug report section, a few of the lads still didn't know what it was so i don't know what else to say.
I'm due for an upgrade in October so for me at least it's not that much of a deal but i'm planning on giving this phone to my daughter so it would be good to get it working for her.
Would save me a lot of earache.
If u need to know anything else then please let me know, oh and i am using a class 2 sd card, which i have been unable to change, however just today my girlfriend has just had a class six delivered and her old one will be up for grabs so i will test with that too. Has anyone else tried with multiple cards??? Also how do i find out what boot loader i am using (recover) as maybe the problem resides there.
btdag said:
Ahh - so its not the camera app that is crashing but other apps too which are using the camera. Very odd.
And FYI - you don't need to touch your bootloader - just change the driver in windows to My HTC instead of HTC Bootloader and the rru will work.
Click to expand...
Click to collapse
Thats right, its any app which accesses the camera.
What could be the correlation between connecting the charger and not connecting the charger, could that be a power issue and the battery is delivering too low a power output on it's own to run the camera? Hence it works with the charger plugged in ?? Either way i think that is the only real clue there is to be honest, unless your phones still restart when the phone is plugged in, in which case it's not much use.
Anyone here seeing some data issues on the D2 running Fission? I am in a major city, and it seem like I am kind of having some data issues since I starting running Fusion, specially when browsing the web. The internet seems to lag a bit, and connection seems a bit slow(good bit slower than normal). I got a message few times relating to the data connection. I want to say this could be a network issue, but my sister with a Droid Inc, says here data is fine? Any ideas?
Called VZW today up asking if there was an issue on their end, and they said no. Tech then told me to take out the battery for 10-15 seconds and they try the internet when back on. Tech said it could be due to the phone not properly switching from one tower to another. It did work, but about 2 hours latter I was having the same connection issue where pages would no open up, and data was a bit on the slow side. Did the same method again, and that worked. I didn't have this issue on the stock D2 rom, or with my Eris(well that always dropped 3G reception, this is full bars with connection problem). Could this be due to me being on Fission 2.2.2, or is it whole different matter not due to being in Fission? Thanks
tbaker077 said:
Called VZW today up asking if there was an issue on their end, and they said no. Tech then told me to take out the battery for 10-15 seconds and they try the internet when back on. Tech said it could be due to the phone not properly switching from one tower to another. It did work, but about 2 hours latter I was having the same connection issue where pages would no open up, and data was a bit on the slow side. Did the same method again, and that worked. I didn't have this issue on the stock D2 rom, or with my Eris(well that always dropped 3G reception, this is full bars with connection problem). Could this be due to me being on Fission 2.2.2, or is it whole different matter not due to being in Fission? Thanks
Click to expand...
Click to collapse
Im running 2.2.2 and im not having that issue. My girl has a D1 and she gets the same crappy service i get i really dont think its the rom. And i dont think there is enough of a difference between 2.2.1 and 2.2.2 to have one get different reception than the other
Shot from my level 60 crossbow of awesomness!
Maybe it just my phone then? I guess will see what I can do.
Have your tried a root reset with a reinstall?
I have been having this problem, Data will just stop working all together. Text messages won't get sent or delivered. The 3G icon just shows uploading and not downloading or stops showing anything at all. I can't fix it unless I turn on Airplane Mode then back off or reboot the phone. Right now I'm running Fission 2.1 but I ran into Data issues with the default R2D2 rom.
volcanomike said:
I have been having this problem, Data will just stop working all together. Text messages won't get sent or delivered. The 3G icon just shows uploading and not downloading or stops showing anything at all. I can't fix it unless I turn on Airplane Mode then back off or reboot the phone. Right now I'm running Fission 2.1 but I ran into Data issues with the default R2D2 rom.
Click to expand...
Click to collapse
So the issue your having is not related to a fission rom...
So, I may have solved the issue. I started clean again; cleared all data and status and stuff, then reinstalled 2.2.2, and then hard rested. Only thing I did different was not install the black status bar and all seems fine, and data seems normal.
tbaker077 said:
So, I may have solved the issue. I started clean again; cleared all data and status and stuff, then reinstalled 2.2.2, and then hard rested. Only thing I did different was not install the black status bar and all seems fine, and data seems normal.
Click to expand...
Click to collapse
I hate to say this man, but from my experience, the more "stuff" you throw on top of a rom, the more bugs your gonna encounter. And youll never have the same bug twice...
Why is that?
Mackattack said:
Why is that?
Click to expand...
Click to collapse
Why is what?
The issue may have arisen again, but I was on the market, so it not clear if that was the market issue many people are facing or it was a data issue.
mikeyinid said:
Why is what?
Click to expand...
Click to collapse
More stuff you put in the more bugs you encounter.
Mackattack said:
More stuff you put in the more bugs you encounter.
Click to expand...
Click to collapse
Im not a dev or anything, but here is an example. I was having problems with a rom i was running last night, reboots and such. The very first thing the dev who made the rom asked me was if i was running a theme. Now, im not saying you shouldnt use custom themes or addons with these roms, but every device is different and will react different. And when your flashing 3-4 different themes over a rom trying to find one you like, or flashing addons then trying to undo them your gonna create some issues. Of course, and i remind you again that im not a dev, this is completely based on my experience, and opinion
I guess with themes that can make sense. I wonder what team defused has to say about this?
Hi
Being a passive user I am not allowed to post in the developers section even if this clearly is a bug report.
Anyway: Installed the new CM7 which was flying - and great in every way for about a day (http://forum.xda-developers.com/showthread.php?t=1068766)
Then I tried the wifi tether which also worked fine. However, when I came home and turned off the tether and on the wifi it looked for networks for about a minute before closing down the wifi again without having found any networks. The only mention of a problem looking like this one in that thread advices to delete /data/misc/wifi/wpa_supplicant.conf - a file that I do not have after the latest upgrade.
Anyone have a hint of what to try? I could of reinstall, but it seems kind of stupid. I have tried deleting dalvik. Have tried to take out battery for a minute and have tried to go back to a system backup from titanium.
Strange huh?
Ketil
Deleting data "solved" it
Hi again
I decided to delete data/reset the phone from the boot menu and it now works again. I will not attempt the wifi tether function again for a while though...
Does it work for others?
all the best
Ketil
Hm - with no apparent reason it fails again... Annoying!
Ketil
Ok
Just in case anyone else experience the same problem: It was finally solved after hours of irritation by manually installing from market rather than through titanium backup. It must have been some old settings from oxygen that conflicted with cm7 that screwed it up for me. Now I am a happy cm7 user!
Ketil
My nexus 6p has worked fine for months however I woke up yesterday morning to find it would not play a video on YouTube. Continuing to use it I noticed the following symptoms:
Wont play videos of any kind (youtube, Facebook etc)
Speakers do not work at all
phone hangs and will not connect during incoming or outgoing calls. The call may connect after several minutes of the screen hanging on the blue calling screen however speakers don't work anyway.
Phone restarts itself randomly
I have tried a hard reset from recovery, wiped cache, booted to safe mode etc with no change.
The phone is bone stock and has not been rooted.
Any suggestions?
At this point I'd try rooting and just flashing stock ROM, don't install anything and see where it goes. If it survives, then maybe it was a rogue app, but that's a lot for an app to do - so it could be a hardware issue.
Same problem here.
teh roxxorz said:
At this point I'd try rooting and just flashing stock ROM, don't install anything and see where it goes. If it survives, then maybe it was a rogue app, but that's a lot for an app to do - so it could be a hardware issue.
Click to expand...
Click to collapse
I've got the same problem, but it happens only on stock, when I've got Chroma installed, everything is fine. One time it happened under Chroma. I don't know what causes it. Reinstalling factory images or even 7.0 doesn't help. Custom kernels didn't bring any improvement either.
Maybe there are some music drivers or something.
Yakksiek said:
I've got the same problem, but it happens only on stock, when I've got Chroma installed, everything is fine. One time it happened under Chroma. I don't know what causes it. Reinstalling factory images or even 7.0 doesn't help. Custom kernels didn't bring any improvement either.
Maybe there are some music drivers or something.
Click to expand...
Click to collapse
It could be a driver thing. Didn't look like a device issue, as it'd be constant. I would go back to stock and note when it happens and then flash a custom ROM and repeat the steps, to perform a controlled test. While doing so, take logcats so Beans / others can review them.
Gone to the service becuase even on a custom ROM I couldn't get any sound. They said that it was a hardware problem (I don't agree but we will see).