Database Develop

Vodafone v1615/Kaiser hangs at Vodafone logo

One of my superiors wanted me to dispose of his old v1615/Kaiser, saying "...this isn't working. Dispose of it properly." Ever the fiddler, I wanted to know if it could be used again, and in so doing I found xda-dev!
I've been searching around, and reading up - Wikis and forum posts - but I've yet to find a solution to my problem: the Kaiser hangs at the Vodafone logo. I found the MTTY instructions threads etc., so to clarify the situation here is a MTTY dump (first two carriage returns and commands included...):
Cmd>
Cmd>set 16 0
Cmd>boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
Storage start sector=0x9040, total sector=0x12280
Storage start block=598, total block=1162
Total Bad Block in CE: 0
Erase physical block from 886 to 2032
formatstorage Bad block found: 1201
formatstorage Bad block found: 1795
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++
At this point it hangs, and drops the USB connection - presumably while the device is reseting the device tree - rendering MTTY useless.
Has anyone come across this issue?

I've not experienced that but I do recall reading similar posts. What happens when you attempt to hard reset using the soft keys and stylus method (as described in the users manual and wiki)? You need to walk before running and this should be the first step before going anywhere near the device with mtty or similar tools. Make sure it's been charging for a few hours so the battery is full or nearly so and ensure you know which buttons to press and are careful just to press the soft keys only. This operation can be fiddly and a few times my attempts at a soft key induced hard reset have failed because my big fat fingers have also ended up pressing other buttons at the same time.

Before finding xda-developers.com I tried a soft reset, which didn't have any effect whatsoever. I've tried soft resetting four times - probably out of frustration.
After those failed, I did a hard reset, which also had no effect. In fact, the MTTY dump on the original post is what happened directly after the first hard reset.
The device is still functional, but it seems unusable for now.

could be a corrupt rom, try flashing another rom
just remembered it isn't hardspl'

phuedx said:
I did a hard reset, which also had no effect.
Click to expand...
Click to collapse
Precisely what does that mean - what happened? If absolutely nothing happened and it didn't start the hard reset procedure (with a little progress bar displayed on the screen), then try hard resetting again (making sure you're only pressing the correct buttons at the same time as when you poke the stylus in) because it may have been finger trouble (it's easy to get this wrong).

Black Screen, but Recovery Console works

This has been an ongoing problem with my G1, related to modded ROMs from what I can tell.
I suppose I should point out, before going into my problems, that I am indeed a noob.
So, back to when I first got my G1.
Quite quickly, I decide I want to root my phone. I follow Cyanogen's guide through every step, and I am able to boot. Cyanogenmod works fine for about a couple weeks.
Suddenly, while I'm listening to music and on the home screen, the screen seems to tear, I suppose you could call it. I don't know the real term for it; it's a problem that usually occurs when programs use indirect allocation of memory. This causes my screen to freeze. When I hit the power button, followed by the menu button (to turn off and on the screen) the backlight turns on, but there is no display. Restarting does nothing, no G1 screen and no recovery.
Just pulling the battery for a brief amount of time seemed to fix it. This quickly stopped working, forcing me to flash ROMs until I had enough of a screen to go back to scratch. It used to only happen when multitasking on the home screen, but with a modded rom, this has started to occur even on boot. Eventually I had to go back to using unrooted OTAs.
I've had this happen with TheOriginal AOSP 1.6, Cyanogenmod 4.2.14.1, and Super-D 1.9.2. I've tried both Amon's and Cyanogen's recovery images, with and without the Danger SPL. Actually, the Danger SPL would stop the screen after a shutdown.
Does anyone have any idea what's going on or if I can run modded roms on my phone?

Tony_SpaZ said:
This has been an ongoing problem with my G1, related to modded ROMs from what I can tell.
I suppose I should point out, before going into my problems, that I am indeed a noob.
So, back to when I first got my G1.
Quite quickly, I decide I want to root my phone. I follow Cyanogen's guide through every step, and I am able to boot. Cyanogenmod works fine for about a couple weeks.
Suddenly, while I'm listening to music and on the home screen, the screen seems to tear, I suppose you could call it. I don't know the real term for it; it's a problem that usually occurs when programs use indirect allocation of memory. This causes my screen to freeze. When I hit the power button, followed by the menu button (to turn off and on the screen) the backlight turns on, but there is no display. Restarting does nothing, no G1 screen and no recovery.
Just pulling the battery for a brief amount of time seemed to fix it. This quickly stopped working, forcing me to flash ROMs until I had enough of a screen to go back to scratch. It used to only happen when multitasking on the home screen, but with a modded rom, this has started to occur even on boot. Eventually I had to go back to using unrooted OTAs.
I've had this happen with TheOriginal AOSP 1.6, Cyanogenmod 4.2.14.1, and Super-D 1.9.2. I've tried both Amon's and Cyanogen's recovery images, with and without the Danger SPL. Actually, the Danger SPL would stop the screen after a shutdown.
Does anyone have any idea what's going on or if I can run modded roms on my phone?
Click to expand...
Click to collapse
Please post what you have on your SD card, partitions, sizes, like that. Make your self a signature with all that stuff and you'll only have to do it once.
Also include if you are running swap compcache or whatnot. I know some of the roms you tried do some of those by default.

I'm still using the 1gb that comes with the phone with one FAT32 partition, should be getting a 8gb class 6 tomorrow. I had tried using a 256mb ext3 and a 64mb swap, but reformatted in case that was the problem.

Tony_SpaZ said:
I'm still using the 1gb that comes with the phone with one FAT32 partition, should be getting a 8gb class 6 tomorrow. I had tried using a 256mb ext3 and a 64mb swap, but reformatted in case that was the problem.
Click to expand...
Click to collapse
I have to admit, I was thinking the same thing. I have never tried one of the modded roms without the ext partition but it should run fine. Usually slow downs that occur over time are cache (swap) related.
I would get your new card, partition it using amon-ra, wipe everything, and use the newest super D.
If it still fails, you may want to look for a stock version. There should be one here somewhere with only root added.

Alright, just got the new card. Should be done with all installing within a few hours. Fingers crossed, eh?

<crosses fingers> lol

Hmm, phone is acting even weirder than before. As of right now, I get my screen back every reboot, but with a custom rom, it fails on boot. The boot screen will freeze, followed by a backlit black screen. I'll keep trying, but I thought I'd see if anyone had any helpful tips, perchance?
(This is attempting to get Super-D going, although I had tried Cyanogenmod earlier with the same result. Downgrading with the dreaimg.nbh still boots fine, however.)
E: Although I'm not sure what exactly did it, it seems to be working now... for now. The fact that the glitch was similar but still improved gives me hope, however.

Crap, it died again on me using Cyanogenmod with Enoch, both fully updated. Anyone know where one of those stock with root roms are?
E: Actually, better yet, anyone know if there's any way I can tell what I'm doing with my black screen? I'm trying to apply stuff with RA-dream, but it's kinda hard, what with the lack of vision and what-not.

Tony_SpaZ said:
Crap, it died again on me using Cyanogenmod with Enoch, both fully updated. Anyone know where one of those stock with root roms are?
E: Actually, better yet, anyone know if there's any way I can tell what I'm doing with my black screen? I'm trying to apply stuff with RA-dream, but it's kinda hard, what with the lack of vision and what-not.
Click to expand...
Click to collapse
you can do a logcat right before it goes out connect your phone to your comp and do adb logcat and do everything your normally would do and if it goes out again and you see a significant in the log from the phone dying then copy that text and post it here. maybe someone can help out.

Ah, I may have explained badly. I've no display at all; no G1 logo, recovery console, or spl. They still work, though. Alt + T while in the recovery console still throws it into USB mode.

If you install the android sdk on your PC, you can use the USB lead to log all activity on your phone.
You would then see where it is crashing (and with any luck why)
It would be painfull because it seems random and intermittant, but atleast you would know why and have a point to look at.
http://developer.android.com/sdk/index.html
btw, original rom (rooted)
http://forum.xda-developers.com/showthread.php?t=538456

Sadly, it locked up yet again. It seems this is the logcat entry linked to the problem;
W/SurfaceComposerClient( 1297): lock_layer timed out (is the CPU pegged?) layer=0, lcblk=0x
42664020, state=00000042 (was 00000042)
W/SurfaceComposerClient( 101): lock_layer timed out (is the CPU pegged?) layer=3, lcblk=0x
426301a0, state=00000007 (was 00000007)
This is looped until the power button is hit, which then keeps anything from appearing on the screen.

Ah, now I can't boot. It seems my GPU is acting up in some way shape or form.
I/SurfaceFlinger( 110): SurfaceFlinger is starting
I/SurfaceFlinger( 110): SurfaceFlinger's main thread ready to run. Initializing graphics H
/W...
D/SurfaceFlinger( 110): pid 110 requesting gpu core (owner = -1)
W/SurfaceFlinger( 110): couldn't grant gpu core to pid 110
D/EGL ( 110): requestGPU returned -1
E/libEGL ( 110): h/w accelerated eglGetDisplay() failed (EGL_SUCCESS)
Shortly followed by...
E/libEGL ( 110): validate_display_surface:536 error 300d (EGL_BAD_SURFACE)
E/libEGL ( 110): call to OpenGL ES API with no current context
I/SurfaceFlinger( 110): OpenGL informations:
E/libEGL ( 110): call to OpenGL ES API with no current context
Which then throws it into a loop.

I would install the latest Cyanogen and make sure the phone is clean.
Run a logcat from boot, and then when it crashes post the full logcat + info on the bugs cyanogen page.
http://code.google.com/p/cyanogenmod/issues/list
The support seems to be good there, but they will want a clean install etc..

[Question] ext partition causing random reboots?

So I've been using enom roms for a while now without issue and I tried the other day to partition space on my SD to move the apps over. Using amon ra recovery I partitioned my SD with an ext 3 partition. The problem I got from there was that my phone started randomly rebooting. No rhyme or reason. Sometimes it took a day and sometimes it occurred every 5 minutes or so. The odd thing about this is it would even reboot in recovery.. which, as a separate environment is quite odd I think.
Anyway, earlier today I decided to reformat my card and remove the ext partition, then I reinstalled enoms Rom doing a full wipe. Since then it hasn't rebooted (though I still need to wait and see). Does anyone think it could have been a bad partition? Should I bother trying it again? Any ideas at all what could have caused this?

Problem not fixed. Any ideas?

Things I've tried:
-Installing different ROMs including stock FRG83, CM6, MIUI, and Enom... still reboots, leaving it to be a hardware related issue I would think. Which I figured given the reboots occurring in recovery.
-Removed SD card. I've read reports saying that sometimes a corrupt SD card or SD card contacts could cause this. Removing didn't help. And the Android system and recovery can read the contents of my SD card just fine with it in.
-I have a new battery on order in case it's the battery, but it probably won't be here for a week or so, but this is the last hardware solution I can think of before having to call HTC and report a busted Nexus One, something I fear doing as I use the AT&T Nexus One, which we all know doesn't exist anymore, or if they do have some on reserve for warranty issues I hope they aren't the ones with SLCD screens. *sigh* Not entirely sure what will happen.
I don't think it's APP related as I haven't installed any new apps in a log time, aside from aLogcat (to see if I could see anything weird)... which I can't really see anything in the log, but I don't really know what to be looking for either. That and I've restored from Titanium Backup which my last backup was when my phone worked fine... so unless it's a market update for an app causing the issue. I guess I can test by running stock/no apps sometime.
I apologize for the rambling, just sort of keeping a log in case something in here helps someone else out down the road.

we'd need to see your logs to help... could be something quite simple.
adb log tail:
adb logcat
tail kernel messages:
adb shell cat /proc/kmsg
view kernel messages: dmesg

Thank you for your response britoso, I just got home from work and I ran the logcat, dmesg and bugreport (not sure if this one will help, but I figured it was more info either way) The .txt files are too big to upload for that file type so I uploaded them to my dropbox...
logcat:
http://dl.dropbox.com/u/9334051/logcat.txt
kernel messages:
http://dl.dropbox.com/u/9334051/dmesg.txt
bug report:
http://dl.dropbox.com/u/9334051/bugReport.txt
zip of all files:
http://dl.dropbox.com/u/9334051/adbLogs.zip
I appreciate any help at all with this. I don't really expect anyone to dig through these logs for me (though I appreciate it if you do!), but if anyone can tell me what I'm supposed to be looking for it will be a great start! Thanks again!

Yes! I'm actually having similar problems to yours. I just bought a new Kingmax 16gb Class 10 sd micro card (because it's cheaper than the branded ones) and I have problems with reboots and hangs whenever I use ext-partition with it. Copying files to and from the computer using a sd card reader is no problem but many roms keep hanging and crashing for me, especially when I'm trying to install apps from the market or restoring my backups with Titanium Backup.
Also even after full wiping thrice in recovery and installing a fresh rom, I keep getting crashes just after I turn on ext and dalvik to sd.
I have found a temporary solution which fixes my problems everytime I try a new rom. I have to manually reformat my sd card in a card reader with SD Formatter before I partition it with ext2-3 in recovery. Then flashing the rom will work (at least I think it works since I found no problems after a day's usage or so).
You can get SD Formatter here. http://www.sdcard.org/consumers/formatter/
Make sure to turn Flash Erase On and Resize on. It will full format the sd card and delete the ext partition for you.
I also made sure not to remove the card physically from the phone after the rom is up and running. Kinda sucks because the USB interface of the Nexus one is only 2mb/s. Using a card reader would fully maximize the speed of the Class 10 card during file transfers.
And I see that you are using AmonRa's recovery 1.8.0. I was also using this version as well. After some research, I found this http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Recovery_Images
Seems like v1.8.0 have some problems with wiping ext. I don't know if that has any connection but sounds plausible. Also there was once I had problems with repairing ext using this recovery, the repair actually lasted for an hour before I took out the battery out of impatience. Subsequent ext repair took only a min (which should be the case). So my guess is that there is something wrong with this recovery version (or my sd card..)
Well I finally flashed my current rom successfully after doing a full reformat but it gets tiring and I don't feel comfortable reformatting a sd card for so many times. Sometimes I think this card is rather wonky since my old Kingston Class 4 had zero problems with ext partitions. I hope not since it's a brand new card.
Anyway I hope this helps you. I just flashed the latest alpha build of AmonRa which supposedly removes the bugs in 1.8.0. But I'm not going to test it out until something goes wrong with my current rom.

did your phone reboot while you got the log?
I see no signs of a reboot.
Only thing suspicions is
<3>[ 1312.669342] msm_i2c msm_i2c.0: Transaction timed out
<3>[ 1312.669769] msm_i2c msm_i2c.0: Error during data xfer (-110)
<3>[ 1312.670135] tps65023 0-0048: Write for reg 0x6 failed
<3>[ 1312.670562] acpuclock: Unable to drop ACPU VDD.
Click to expand...
Click to collapse
tps65023 is a voltage regulator connected to the i2c bus. Found that here:
http://forum.xda-developers.com/showpost.php?p=7748412&postcount=6
The VDD is the voltage to the CPU. Are you running a undervolted kernel ?
It will be good to get more opinions...

britoso said:
did your phone reboot while you got the log?
I see no signs of a reboot.
Only thing suspicions is
tps65023 is a voltage regulator connected to the i2c bus. Found that here:
http://forum.xda-developers.com/showpost.php?p=7748412&postcount=6
The VDD is the voltage to the CPU. Are you running a undervolted kernel ?
It will be good to get more opinions...
Click to expand...
Click to collapse
It always seems to reboot when I'm not near a comp. It rebooted about 8 times during my shift at work but not on the way home or while I was getting the logs. I am running enoms standard kernel. I run setcpu to control it but I already ruled this out by removing setcpu for a day... reboots still occurred.

@musashiken: that sounds painful and very harmful to your SD card. I envy your patience though lol.

Just rebooted again... I ran alogcat immediately after startup....
Uploaded text file I saved from it...
http://db.tt/nXiM15D

Well I had the same problem a couple of months ago.
Never really found out what was wrong, but I figured the SD card was the problem so I bought a new one and no problems since then.
Maybe the SD card you have has bad sectors or whatever. Hope your problem gets fixed.

lostinbeta said:
@musashiken: that sounds painful and very harmful to your SD card. I envy your patience though lol.
Click to expand...
Click to collapse
Did you reformat your sd card with SD Formatter? You should try it if you haven't as it should clear any corrupted sectors in your ext.
Remember to backup whatever you need to your pc first.
It is an arduous task but it should at least rule out sd card problems.

lostinbeta said:
Just rebooted again... I ran alogcat immediately after startup....
Uploaded text file I saved from it...
http://db.tt/nXiM15D
Click to expand...
Click to collapse
I see it starting up, but the error must have flown by before that.
Keep logcat running via usb and hope it crashes. you will likely see somethingng like this:
I/ServiceManager( 93): service 'usagestats' died
I/ServiceManager( 93): service 'SurfaceFlinger' died
I/ServiceManager( 93): service 'batteryinfo' died
I/ServiceManager( 93): service 'entropy' died
I/ServiceManager( 93): service 'power' died
I/ServiceManager( 93): service 'telephony.registry' died
I/ServiceManager( 93): service 'device_policy' died
I/ServiceManager( 93): service 'meminfo' died
I/ServiceManager( 93): service 'cpuinfo' died
I/ServiceManager( 93): service 'activity' died
I/ServiceManager( 93): service 'permission' died
I/ServiceManager( 93): service 'statusbar' died
I/ServiceManager( 93): service 'clipboard' died
I/ServiceManager( 93): service 'netstat' died
I/ServiceManager( 93): service 'network_management' died
I/ServiceManager( 93): service 'package' died
D/BootAnimation( 138): SurfaceFlinger died, exiting...
E/installd( 101): eof
E/installd( 101): failed to read size
I/installd( 101): closing connection
I/Zygote ( 98): Exit zygote because system server (125) has terminated
I/ServiceManager( 93): service 'media.audio_flinger' died
I/ServiceManager( 93): service 'media.player' died
I/ServiceManager( 93): service 'media.camera' died
I/ServiceManager( 93): service 'media.audio_policy' died
D/AndroidRuntime( 341):
D/AndroidRuntime( 341): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<
Click to expand...
Click to collapse
The 50-100 lines before this will show what caused the restart

musashiken said:
Did you reformat your sd card with SD Formatter? You should try it if you haven't as it should clear any corrupted sectors in your ext.
Remember to backup whatever you need to your pc first.
It is an arduous task but it should at least rule out sd card problems.
Click to expand...
Click to collapse
I ruled SD out when I took it out and left it out but it still kept rebooting.
I'll try hooking it up after work tomorrow and leaving it on Usb with logcat running and see what goes on.

So much for plugging it up after work today, my phone won't boot past the solid nexus 'X' boot screen, won't even go to the animation anymore. UGH!
[edit]This includes when I try to boot into recovery as well[/edit]
[edit2]Well after pulling the battery at least 30 times I got it to boot... running logcat now and i'll wait for it to reboot again[/edit2]

Ok, so ran logcat while phone was booting and waited for it to restart... I got no error message before the reboot... here is the logcat file...
logcat file:
http://dl.dropbox.com/u/9334051/logcat2.txt
My phone appears to be constantly refreshing the weather widget, which is normal, it's in my other logs as well. I didn't touch my phone or do anything with it after boot, just left it plugged in and off to the side. I was watching logcat keep looping the widget refresh and cache clear (at least I'm assuming that's what it's doing after the widget refresh) and my phone rebooted... yet no error message, or any other type of message occured. Terminal ended the session and my phone restarted.
I'm going to vote this is definitely a hardware related issue. I know it's not SD related as my SD card is removed from the device. My new battery is on it's way right now, should hopefully have it in the next day or 2, so I'll see if that fixes the issue. And if not, then it's time to call HTC... knowing I did everything I could to fix it myself. Though it should be fun trying to explain why I have a rooted device with custom recovery installed on my phone as I can't restore to stock (I don't have an unlocked bootloader) without risking bricking the device for good due to a reboot.
[edit]Just tried the same thing with kmsg and the result was the same... it kept showing the charge and temp of my phone in sequence, then phone rebooted and terminal session ended with no errors reported in kmsg[/edit]

Unfortunately you JUST missed the vital lines

britoso said:
Unfortunately you JUST missed the vital lines
Click to expand...
Click to collapse
What do you mean? The log cat was running from the moment I hit the power button to the moment it rebooted. After the reboot it just goes to the X screen without the animation and logcat doesn't recognize it so it ends the terminal session and I have to pull the battery to get it to reboot again. How did I miss the vital lines? I'm confused (I'm really not an idiot, I promise, just new to the whole android dev thing....lol)

The fatal error happened just before the phone rebooted... Your logcat starts from when the phone came back from the crash.

Yeah but the last logcat starts as the phone is booting but ends when the next reboot occurs... no error was thrown. It just ended and started over and the phone booted into the 'x ' boot screen again. But won't go to the animation. I just got my new battery today. We will see how this goes.

[Q] SGS won't stop vibrating

My Captivate won't stop vibrating. Whenever I use the LED touch pad or access any applications it will vibrate for a minute or so with one long vibrate and then two short. I can't get it to stop and its really frustrating. I have the ATT ROM installed on a rogers phone, no issues until now.
It is rooted, OCLF. I have tried removing the SIM, battery, rebooting it, all with no success. In dmesg I see the following when it happens:
[Warning]
[VIBETONZ] enable_vibetonz_from_user : time = 150ms
[Warning]
[VIBETONZ] ENABLE
[Warning]
[VIBETONZ] DISABLE
the only thing I can think of doing prior to this is I installed the SMS time fix but I have since removed it and the problem continues. Anybody have any ideas?

Force closing, flash back to stock and try again.

I was hoping that somebody wouldn't say that.
Edit: I ended up wiping all user data, which has fixed the problem, it avoided having to flash it again, still annoying.

Question Random reboots

Hi there,
I've got OnePlus 10 Pro phone and it came with strange random reboots right after starting to use it. I tried flashing different roms, factory resetting it with no luck. The last thing I've done is checking logs with logcat . The closest one I've got is reboot right after disconnecting cable with active logcat. After reboot I've saved log (attached).
Looks like it is system process but I don't know what to do next. The main message looks like this:
01-19 18:37:24.045 25684 26842 F libc : Fatal signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0x7f0bd91500 in tid 26842 (binder:25684_9), pid 25684 (system_server)
Hope someone could help because OP support is not responding =\
Thanks in advance!

Same thing was happening to my on a daily basis, at least once per day of not two or three times. I noticed it was somehow related to the wifi/data connection, but I couldn't exactly figure out the reason.
I updated to Android 13 ( NE2213_11.C.22 ) on december and that issue went away until today, that I had another random reset. (I say that issue because the Android 13 update comes with some other less annoying bugs, like the notifications bar getting stuck every once in a while)

I've tried every firmware found with no luck.
I've tested hardware with app and it says everything is fine.
I've tried to fill storage fully and it worked with no reboots.
Memory app filled RAM fully and phone still doesn't reboot.
I have no idea what to do next
And the saddest thing is total ignorance from 1+ support.