Database Info

Kaiser performance: Slowing down few days after flashing

Hello,
Almost a year ago I purchased my Kaiser (an Orange Kaiser) ans started to flash my phone.
I have already used several ROM avaiable here: Dutty (sevearl versions), L26 (SEVERAL Versions), Hyperdragon, Mobile vista, etc, etc, etc. Have already tryed several versions of the Radio firmwares. 1.24, 1.57. etc. Also, have already tried almost EVERY Hard SPL avaiable and so far I had the same problem:
Few days after flashing the Kaiser starts do slow down its performence. For ex: I press the Call button and it takes 40 to 50 seconds to enter in the touchpad screen. Sometimes it don't even enter the the call screen.
It get worst: sometimes I get no signam from the phone even if i'm side by side to a antena (where any other phone have a strong signal).
The only solution: HARD RESET. I mean, after a hard reset it looks like its other phone. Strong signal, fast response.
I can't possible imagine that I'm the only one here with this kind of problem. Does anyone knows how to solve? Does anyone here knows ehy it happens?
PS: I have already tried configurations with diferent programs. I have already tried with and without S2L2, With or without HTC Home (most without), With and without pocket launcher, with and without today agenda and SPB calendar. Can only think that this is problem with something in the ROM or the radio since every single configuration had the same performance issues.
Can someone please help me?
Thanks
Dandare

I had a faulty SD card that was giving me similar problems to this. I think it was due to Coreplayer and Audio Manager scanning the faulty SD card for music and the read speed was really really slow on the card. Everything would grind to a halt. I bought a new card and everything was fine after that. You could also try formatting or removing the SD card to eliminate the card being the source of the issue.... but you'll probably turn around a say you don't have an SD card
Good luck...

Yeah recently I got this issue. The filesystem on my SD card for corrupt somehow, and I was unable to access anything on it via activesync (my pc) and my phone.
So I just installed some prob( i forget the name) and formatted the SD card, then re-flashed. And since then it's been quick as can be

Hey guys,
I've been having this issue as well. I have not found it to be my storage card as i have tried 4 different cards. i have put the cards on my BJII and it works without issues. I also have found that with some of my early L26 Flashes i would just ride it out and it would work again.
However i have not had my HDIII Pro for that long but i'm hoping that it would would do the same.
If someone does find a link to what is really going on i would greatly appreciate the advice.
Thanks

Also, I actually believe if you text message a lot (i mean basically excessivly) as my brother does, the device will slow down.
He has my older Hermes, and he has unlimited texting, but within 2 weeks he would have sent 1500-2000 text messages and recieved about the same ammount.
By that time his phone would start lagging and being a pain, so I would usually just do a new flash (or hard reset), since deleting that many texts normally would probably take 48 hours haha.
Anyway when it gets re-flashed everything runs normal and fine. But whenever the phone gets cleared everything is smooth again
So maybe it's the amount of text/emails you have? Idk

Going to test the SD card. I have a 4Gb SD card but I'm actually only using 1,4 Gb, so I can use a 2Gb with no problem.
This going to take a while since the phone starts to slow down after three or four days, but I'll let you guys know if it solved.
Thanks!!!!

stuff said:
Yeah recently I got this issue. The filesystem on my SD card for corrupt somehow, and I was unable to access anything on it via activesync (my pc) and my phone.
So I just installed some prob( i forget the name) and formatted the SD card, then re-flashed. And since then it's been quick as can be
Click to expand...
Click to collapse
If you have a vista based machine, It will correct the filesystem errors automatically, and you wont have to reformat...
Works great for me, My desktop is VU64, and my lappy is MCE2005. All the flashing happens on the laptop, and transferring files to the SD (Music & Movies) via WMP happens on the desktop.

Idem
I have same problem.
I try to found confirmation in italian dedicated forum , nobody has had the same problem.
After any minutes where the kaiser freeze , i do not have the same problem.
As is autoconfigured.
Now i used selfmade rom (by official italian rom, and hardSPL 3.29).
Sorry for my bad english

Three Very Important Technical Questions

My phone was acting weird (programs that were installed were not being found) so I soft reset. THe phone became infinitely paused at the touch pro flash screen. So i tried reflashing with my SD card. I flashed 2 different roms, both with filesizes greater than 110 megs. They would get stuck infinitely flashing through the SD card. Finally I flashed a rom (Mighty 6) which was under 100 megs and it worked.
1) It almost sounds like I had a device filesystem corruption or something. How would I determine if a portion of my device's filesystem is corrupt?
2) If part of the file system is corrupt, is there a way to mark the corrupt portions?
3) If it's not a corrupt filesystem, what else could it be?
Thanks guys, I'd appreciate any help!

Have you tried flashing using activesync? or a different SD card?
If so and you still have the same problem, then its quite probable you have some corrupted memory on the phone (sry, i dont know how to block use of the corrupted parts) - if not i'd say you have a corrupted SD card, and everytime you use it, it screws the flash.
Did you not try a hard reset between a softreset and a new flash??

Beeble said:
Have you tried flashing using activesync? or a different SD card?
If so and you still have the same problem, then its quite probable you have some corrupted memory on the phone (sry, i dont know how to block use of the corrupted parts) - if not i'd say you have a corrupted SD card, and everytime you use it, it screws the flash.
Did you not try a hard reset between a softreset and a new flash??
Click to expand...
Click to collapse
Hey, thanks for the reply...I could not get an activesync connection since the OS wouldn't load. I tried two different cards same result. I formatted both cards. I tried hard reset, at the time the phone would not even hard reset. Fortunately I have yet to encounter any issues with since I flashed Mighty's Rom.
I have a thread about this on ppcgeeks as well. I mentioned there it would be nice to have a utility such as chkdsk on windows mobile. I guess I'll take it as it goes, since it seems my phone is functioning correctly right now.

A few notes about Flash (the hardware type) and flashing (the 'firmware' type).
Flash memory isn't permanent. Writing to the flash memory itself is a (slightly) destructive process. Older chips used to have only a few hundred re-writes; newer flash devices support millions (and some of the newer ones, billions) of rewrites. This is important to your question because the hardware that controls the flash itself is designed to deal with the possibility of bad blocks.
Just like a normal HDD can develop bad sectors, Flash memory can develop bad 'blocks'. In fact, most flash chips actually ship with several bad blocks from the factory. Knowing the manufacturing process is imperfect, manufacturers which would design a flash chip meant to store 600 blocks might actually develop one with 650 blocks; factory testing is then performed to ensure that the amount of valid blocks is greater than or equal to 600.
The hardware/firmware controller that controls read/writes to the flash chip is designed to catalog all invalid bytes- bytes which, for example, after being written retain their previous value. It then automatically reroutes data writing around the bad block.
More succinctly, you shouldn't have to mark bad portions of the NAND flash- the device should be doing it by itself.
As a second note, you don't actually need a real ActiveSync connection to flash 'via ActiveSync.' A connection to the bootloader using the activesync drivers works fine most of the time- this is the device's "recovery mode."

ktemkin said:
A few notes about Flash (the hardware type) and flashing (the 'firmware' type).
Flash memory isn't permanent. Writing to the flash memory itself is a (slightly) destructive process. Older chips used to have only a few hundred re-writes; newer flash devices support millions (and some of the newer ones, billions) of rewrites. This is important to your question because the hardware that controls the flash itself is designed to deal with the possibility of bad blocks.
Just like a normal HDD can develop bad sectors, Flash memory can develop bad 'blocks'. In fact, most flash chips actually ship with several bad blocks from the factory. Knowing the manufacturing process is imperfect, manufacturers which would design a flash chip meant to store 600 blocks might actually develop one with 650 blocks; factory testing is then performed to ensure that the amount of valid blocks is greater than or equal to 600.
The hardware/firmware controller that controls read/writes to the flash chip is designed to catalog all invalid bytes- bytes which, for example, after being written retain their previous value. It then automatically reroutes data writing around the bad block.
More succinctly, you shouldn't have to mark bad portions of the NAND flash- the device should be doing it by itself.
As a second note, you don't actually need a real ActiveSync connection to flash 'via ActiveSync.' A connection to the bootloader using the activesync drivers works fine most of the time- this is the device's "recovery mode."
Click to expand...
Click to collapse
Excellent information, much of what I was too lazy to look up . Considering the information about bad sectors on flash-based memory that you have given me, do you have any ideas as to what the issue may(is) have been?
The only other explanation (albeit in my limited knowledge lol) that I can come up with is that the data within the roms I used somehow became corrupted, either during the download process, or the process of transferring the data to the card. I was in linux when I transferred the data to the card. Although I find this highly unlikely, I guess it could be a driver implementation issue with my cardreader and linux. I have not had a problem thus far though.

Data loss but not completely.

Hi,
Few days back, my phone started randomly rebooting and it got stuck on boot. When I checked logcat, I got some fatal error in java. I tried fix_permissions and all but nothing seemed to work, so I just restored a recent Nandroid backup. However, in attempts to fix the issue, I must rebooted around 50-60 times. So, anyway, the problem was fixed. This was 3 days back.
Today I check the photos, and I see only 30-40 photos are remaining of around 500-600 photos which I had. I've done a thorough search on my phone but they haven't been moved anywhere else. AFAIK, if there is a data loss, it should take down everything not just selective items, no?
Is there any solution to this problem? I don't want to have all those 1 year's worth of photos gone.
Can I use 'dd' to make an image and mount it as ext and run ext data recovery tools? Or is there anything else I can do? Would really appreciate some help here.
Thanks

Also, what is the partition mounted as in Nexus S, ext or fat?

FAT32, so it retains compatibility with all OS.
And no, you're not right. If there is data loss, it doesn't necessarily mean you will lose everything at once. The memory can be partially corrupted either by a physical problem with the chip(s) itself or the connections or by a software problem.

[Q] EXT vs FAT

Is it possible to use EXT on the main partition instead of fat? It may improve stability and CM7 already supports EXT

it is theoretically possible to make tho whole sd card to ext, but if you use windows it wouldnt be clever to do that bacause windows can only read data from Fat or NTFS as far as i know

I know about the incompatibility issues, but I prefer a better phone and airdroid-like software may solve the problem of transfering files from and to the phone. Today I tried this but the phone froze on the lockscreen after boot. Is there anything to set?

I succesfully mounted a folder from my EXT partition and is really faster than the FAT partition, but the media process keeps force closing because of the permissions.
Is there anyway to solve this? The problem is visible with the camera, sometimes it works sometimes not, but when it does is really snappy and when you change the permissions of the photos the problem is solved; as far as I've been testing I haven't seen any other issue

Data recovery mystery (from HTC One M7 / micro sd card)

Hey folks,
Bit of a long story, short version is "Phone seems wiped, did I mess up? If not how is it possible?"
I've been passed a device with a report that it had an important video file on it that was accidentally deleted, and tasked with seeing if the file was recoverable. I was also later passed the only SD card (2gb) in the owner's possession.
Phone first. I followed instructions to root the device and rip an image of the data partition. This did mean uploading the root zip to the phone, a risk I undertook before discovering you can get a temporary root. I don't think that act accounts for what I found.
I used these two [1] [2] links for guidance. Ripping the data took many attempts but I did eventually get a 32gb-ish image down the wire. The image seemed to mostly be zeroes viewed in hex editor. Video-wise, recovery software found only operating system background videos of clouds. There didn't seem to be any user data on there at all. Recovery seemed to run very quickly with image stored on an SSD. As I say, even if I'd overwritten the video file header with the root zip, there'd have been other data on there, seems to me. Other photos. Other videos. Perhaps I ripped it wrong. Ripped on a windows machine. Is ripped even the right word, I'm not very good at this and a bit stressed
Did I get the wrong partition? Wouldn't be 32gb then though, right? I ripped mmcblk0 and mmcblk0p37 or whatever seemed to be mounted as the data partition, various times, and got similar results regardless of the resultant file size (i.e. stop half way through, data is mostly zeroes, get the whole image, it's mostly zeroes, all ripped images contain the OS video files).
Did rooting / flashing recovery wipe the data? Seems unlikely. I did start the phone by accident at one point (reboot from recovery seemed not to acknowledge my holding down the volume / power combo to get back into recovery) and OS claimed to be "upgrading all the apps" so I powered it down straight away. This is the terrifying moment for me, did something I do kick off an OS process that wiped the phone?
Owner claims never to have done a factory reset, and in any case that doesn't wipe data anyway right? Only file table. So data would still be there. But like I say they don't claim to have wiped phone, only accidentally deleted files. Even automatic OS upgrade would leave data intact. Flashing a mod would do it I guess but that's not happened.
SD card next, it's labelled "BLACKBERRY" and owner did have a bb once. They say the card was in the phone, I figured maybe phone was using sdcard instead of internal memory for user data but the card is essentially blank, it's like it has never been used since it was formatted by the blackberry. No data on it, just 6 folders. Recovery software finds literally nothing. Seems like a dead end. Ripped on a mac using dd.
Possible that the owner had another sdcard at some point but they cannot recall having one.
Also possible I ripped the data wrong? I used sudo dd to get it, then ran Disk Drill on the mounted .dmg, which is 2gb, the size of the sd card.
dd would not substitute zeroes for unallocated filetable areas, right?
So this leaves me with so many questions about how we got to this point with no data, but mainly I want to sanity check what I've done here so I can be more confident I haven't wiped the data I'm trying to recover myself. Then it'll be a case of digging deeper into what happened to this phone between the video being taken, the video being deleted, and the phone arriving in my hands.
Thanks in advance to anyone for literally any input!!

I've asked the owner to trawl their cloud drives for HTC backups, hopefully they had daily backup linked to one of their clouds. Otherwise, I guess I'm at a loss...

If the lost data cannot be scanned by the recovery tool, they has been overwritten. But fortunately, the owner to cloud drives for HTC has backup file.

Thanks bobii. What's confusing is that the data I retrieved seems mostly to be zeroes, which wouldn't be the case if it had been overwritten. Unless it was overwritten with zeroes, which as far as I know would only happen if you flashed a brand new OS or intentionally wiped the data partition, both processes I think that the owner would remember doing.