Hey guys!
Im a first time rooter but somehow managed to root my Dell, flash Streakmod on it and install the DSC 2.0 ROM and then upgrade it to 2.3.
My problem is that the moment I unlock the screen after rebooting the phone I get a wall of notifications telling me that googlewhateversystem stopped working along with other applications. It seems that somewhow the whole introduction part of the phone went to ****.
Help?
Did you do both resets for DSC, namely Option 1 from the main menu and the reset option in StreakMod?
Strephon Alkhalikoi said:
Did you do both resets for DSC, namely Option 1 from the main menu and the reset option in StreakMod?
Click to expand...
Click to collapse
Yes. I installed DSC and after that made a factory reset, wipe cache, wipe dalvik etc... then I rebooted and did another factory reset on the dell standard recovery.
EDIT: I restored a backup and installed DSC again but this time I didnt do a factory reset and just wiped the cache. I managed to get on the phone but now I get constant notifications that android.phone has crashed. Any ideas?
EDIT2: I removed my sim card and restarted the phone. Everything works fine now. Seems like the Rom doesnt like my simcard. Well I guess I wont use it then. The keyboard is way to small anyway. I just wish that there would be a good ROM for me to use.
Pardon my english im from germany
It's odd that you're having such issues. I use DSC myself and have not had any problems using it. In fact, switching back to DSC solved a pair of annoyances that appear in the CM7 ROMs for the Streak: no camera zoom and the dialpad buttons being too small. If you're willing to put up with those annoyances, try using CM7 with _n0p_'s Phoenix kernel or one of the CM7 derivatives like Longhorn. Just be aware that other than DSC none of the Gingerbread ROMs are being actively maintained.
I honestly dont know what the problem is myself... I flashed it with ams and dps and then the recovery, installed the zip, wiped everything, fixed permissions and rebooted.
I tried this several times and everytime it has these crashes that make it unable to use the phone. Also after restoring my backup after the install the buttons on the bottom of the phones flash every minute or so.
Geez... why does it have to be so complicated xD?
EDIT: I decided to take a deep breath and try the whole procedure again. Flashed the phone, installed the zip, installed the update, wiped everything, rebooted, after the boot waited 10 mins and voila! It works like a charm!
If you Strephon now would be able to tell me how to change the keyboard to the default one then I'll gladly give you my thanks!
If you mean the Swype Keyboard...
Settings > Language & Keyboard. Make sure Swype is checked. Tap OK on any popups that appear and exit settings.
When you go to type something, e.g. a response to this post, press and hold the input area (the spot where you type). The menu that pops up should have an option labeled "Input Method". Tap on Input Method to change keyboards.
No I mean the standard big fat keyboard from the original Dell Streak 5 Rom. The DSC one is way to small for my fingers to type fast AND accurate.
The "big fat keyboard" is the Swype keyboard. The only other option is the default Android keyboard, with much smaller keys.
Hello,
I would like to apologize in advance if the question was posted before, the description is too brief or anything like that since it is my first post here (although I had searched for similar questions but didn't find any with a proper solution).
After installing CM10.2 with GApps on my Galaxy S2 i9100 (actually, before that I tried Firefox OS which messed up my /data, had to repartition manually and it helped then) I tried to install - and run - Triangle Away, but it froze. Then I made a terrible mistake imo: I rebooted. After that (I mean, after flashing CM again since it didn't work at all) I got an issue with the screen going black after unlocking the phone or apps freezing (running launcher, going to 'system settings' etc; tested on Trebuchet, haven't tried any other launcher so far). I also had a problem (again) with broken datafs, but used patched PIT from somewhere in here, I will edit out that post and paste the url to the thread.
Another thing that should be mentioned is that that status/notification bar is working without any problems when the launcher freezes, and when the screen goes black the 'back' and 'menu' buttons give feedback when pressed (they make the phone vibrate but when I press volume up/down there is no sound).
I've already tried doing wipe data/factory reset, cleaning cache and dalvik and wiping system with flashing CM again but without any progress. Also wanted to check adb logcat, but I cannot get into usb debugging settings (launcher freezes when 'system settings' is pressed).
What could be the solution?
Thank you very much for any answers!
Im Argentinean first of all and I'd bought my new GS2 3 days ago on mercadolibre.com.ar (a site like ebay.com) to a guy that imports it from factory. After of almost 50 days of waiting, i did got my new mobile phone, when i got it i'd upgraded to JellyBean with the official samsung rom, and that's when the problems showed up, the top left corner come overheat turning off the device, over and over again. So after some failed testing I'd chosed to change the kernel to Siyah expecting some performance improve but it become kind of worst because when the screen blackout the device just reboot itself, but if i keep doing something on it nothing happens, just when the screen comes black.
So i guessed that it may was related to the kernel, so downloaded another official rom jelly bean, this one was a Pre-Release rom, that some time ago i'd installed on a friend's galaxy s2 and it worked fine (despite the increased battery drain). This wasn't any solution though, because it keeps rebooting when the screen comes black.
I did tested to turning on without the simcard and microsd card, with the same results.
Another fact is that if i left the music playing and turn of the screen with the power button, nothing happens, it works perfectly.
It seems that is some kind of trigger when the mobile actually suspend itself doing really nothing.
Now i dont know what to do, should i test some custome rom/kernel?? should i get the chances to use the warranty? (implies to send again the device to china i guess ¬¬)
Please help, and thanks in advance.
hackkpo said:
Im Argentinean first of all and I'd bought my new GS2 3 days ago on mercadolibre.com.ar (a site like ebay.com) to a guy that imports it from factory. After of almost 50 days of waiting, i did got my new mobile phone, when i got it i'd upgraded to JellyBean with the official samsung rom, and that's when the problems showed up, the top left corner come overheat turning off the device, over and over again. So after some failed testing I'd chosed to change the kernel to Siyah expecting some performance improve but it become kind of worst because when the screen blackout the device just reboot itself, but if i keep doing something on it nothing happens, just when the screen comes black.
So i guessed that it may was related to the kernel, so downloaded another official rom jelly bean, this one was a Pre-Release rom, that some time ago i'd installed on a friend's galaxy s2 and it worked fine (despite the increased battery drain). This wasn't any solution though, because it keeps rebooting when the screen comes black.
I did tested to turning on without the simcard and microsd card, with the same results.
Another fact is that if i left the music playing and turn of the screen with the power button, nothing happens, it works perfectly.
It seems that is some kind of trigger when the mobile actually suspend itself doing really nothing.
Now i dont know what to do, should i test some custome rom/kernel?? should i get the chances to use the warranty? (implies to send again the device to china i guess ¬¬)
Please help, and thanks in advance.
Click to expand...
Click to collapse
You should try custom rom. Try to Flash Neatrom or any stock custom rom.
Hope it solves your problem.
Sent from my iPhone using Tapatalk
Firstly, you need to verify that it's a genuine S2. Turn the phone off, take the battery out and post on here EXACTLY what you see on the sticker in the battery compartment.... Just don't post the IMEI number...
Sent from my GT-I9100 using xda app-developers app
Model: GT-I9100
SSN: -I9100GSMH
RATED: 3.7V ------- : 1000 mA
FCC ID: A3LGTI9100
MADE IN KOREA BY SAMSUNG
IMEI: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
S/N: R5XA73828F1
That's all, its seems original, right?
i'd just installed the last samsung official Rom, form nordic countrys, and it seems to work just fine. I'll keep updated if it goes wrong again. Im so happy.
EDIT: Ok so i just leave it chargin the battery and it reboot itself 3 times again and 1 time just it turned off. I didnt tried leave it without the charger because it didnt have any charge. So im in trouble again >.<
hackkpo said:
i'd just installed the last samsung official Rom, form nordic countrys, and it seems to work just fine. I'll keep updated if it goes wrong again. Im so happy.
EDIT: Ok so i just leave it chargin the battery and it reboot itself 3 times again and 1 time just it turned off. I didnt tried leave it without the charger because it didnt have any charge. So im in trouble again >.<
Click to expand...
Click to collapse
Go to recovery and do wipe data/ factory restet and wipe cache . Reboot . Phone will start working again.
Sent from my iPhone using Tapatalk
Jeetu said:
Go to recovery and do wipe data/ factory restet and wipe cache . Reboot . Phone will start working again.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Ok since that post i'd installed cyanogenmod 10.1.3 with JB 4.2.2 and it rebooted itself like 4 times and finally it keeped on like 10 minutes now.
hackkpo said:
Ok since that post i'd installed cyanogenmod 10.1.3 with JB 4.2.2 and it rebooted itself like 4 times and finally it keeped on like 10 minutes now.
Click to expand...
Click to collapse
Yes do the same what i posted above and then flash your rom again.
Sent from my iPhone using Tapatalk
Jeetu said:
Yes do the same what i posted above and then flash your rom again.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Why would i reflash again? i dont get it
hackkpo said:
Why would i reflash again? i dont get it
Click to expand...
Click to collapse
Because your phone is now in Bootloop.
Bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence.
Think of system apps that are compiled incorrectly, permissions that are not set correctly, files from other devices and even an init.d script, everything is possible.
To find the cause of a bootloop you have to think about what you did before getting the bootloop.
Choose one of the following reasons that caused the bootloop for you and try out its solution.
– After flashing a new rom
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Jeetu said:
Because your phone is now in Bootloop.
Bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence.
Think of system apps that are compiled incorrectly, permissions that are not set correctly, files from other devices and even an init.d script, everything is possible.
To find the cause of a bootloop you have to think about what you did before getting the bootloop.
Choose one of the following reasons that caused the bootloop for you and try out its solution.
– After flashing a new rom
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Click to expand...
Click to collapse
No is not, the cellphone starts normal, and while im using it nothing wear happens, but when i left it the screen goes black and the device reboot itselfs. But now im seeing that doesnt happen anymore, i dont know why.
Still with cyanogenmod rom, i connected the phone to charge the battery, and i saw a tendency of reboots and turnings off while the percentaje comes to 100% and a increasing overheat on the left-top of the phone, i suspect that the problem may be related with the amount of charge from battery and the overheating... Hardware problem?
Well... After all this time my cellphone went through the argentinean official service of samsung and the tech guy told me that he couldn't do anything on my device because he tried installing a lot of samsung official roms and the device was still malfunctioning. So he gave up on it, so i'd tooked it to another service (non official this time) and that guy told me that it may be a non official device, so he wouldnt do nothing on it, because i couldnt get the hardware that possible was malfunctioning. So here im now, with the all money spent for nothing.
My question is, what can i do to know if is or isnt an ORIGINAL samsung device? Knowing that i'll choose how to proceed. Txs!
I'm really hoping someone can help me. My back and menu buttons stopped working today, and I'm pretty sure it has to do with a failed Swype install.
I'm running AOKP 4.4.2 (1/25 build) on my VZW Galaxy S4 (jfltevzw). The phone has been running great, but I can't stand the new kitkat keyboard. I decided to try Swype again, after dumping it a few years back.
I installed the free Swype (which obnoxiously comes with Dragon also), but I couldn't get past step two (select default keyboard). The wizard just wouldn't progress further. I went into the menu to try switch manually, but I trying to type would just bring up the installer again. I tried switching back to the stock keyboard via Settings>Language, but nothing would happen when I tried to type. The only thing I could do was reboot.
When I booted back up, the menu and back buttons would no longer work. I tried clearing dalvik and cache, resetting permissions, reinstalling AOKP and Gapps, and so on and so forth. I'm backing everything up to do a hard wipe, but I'm not holding my breath.
Has anyone seen this problem before? Is it failing during the Swype install just coincidence? I can't see how it could be....
After a hard-reset / factory wipe, everything is working again.
I will not be installing Swype on AOKP/KitKat again, hehe.
Hi!
I just updated some apps from google play, I think it was google search, text to speech and some apps and a game that I have on my phone. I later get a phone call from a friend and when I hang up I get this message that gapps have been crashed. I pressed okay and thought nothing more than that. But then I get this warning signs about more and more things are crashing. I decide to turn my phone off and now it is stuck on the kernel screen (DorimanX Kernel)
I use ReVolt v4.3 and I have done nothing else with the phone except updating some apps. I can boot to recovery so I tried to clean the dalvik cache and the regular cache but it still wont start.
EDIT: I solved it by also using the fix permission that is an option in CWM. It is working alright for now. I guess it was some issues with the new apps permission that made the phone stuck on boot screen!