Related
Hey, a question...
I flashed the 2.8v, which I thought included the EB16 kernal, but the phone still says EB01 on the "About phone" thingie in Settings. Now, I just flashed the EB16 voodoo zip file on the first page of Adrynl's thread...it still says EB01.
I'm running fine, GREAT, really, but justr wondering where to look so I know I have the EB16 running, and if I am still on EB01, then....why?
Thanks guys, and thanks Adrynl for the fantastic work.
Jeff
You are on EB16 unless you flashed the EB01 kernal after installing SC2.8v.
The only way to check which kernel you are on is by running a command.
Check out post 2178 in the superclean thread (page 218).
bltl211 said:
You are on EB16 unless you flashed the EB01 kernal after installing SC2.8v.
The only way to check which kernel you are on is by running a command.
Check out post 2178 in the superclean thread (page 218).
Click to expand...
Click to collapse
I flashed sc2.8v yesterday, and I also still has EB01, and i didnt install eb01 kernal after installing sc2.8, i checked it following the command, shows sat Jan 2, which i assume eb01.
not having any problem so i am not complaining, just curious.
kundoc said:
I flashed sc2.8v yesterday, and I also still has EB01, and i didnt install eb01 kernal after installing sc2.8, i checked it following the command, shows sat Jan 2, which i assume eb01.
not having any problem so i am not complaining, just curious.
Click to expand...
Click to collapse
Jan 2... that would be closer to DL30. Did you come from a DL30 version of Super Clean?
Just to make it confusing for you all:
There are currently 6 kernels floating around. EB01 voodoo and non-voodoo, EB16 voodoo and non-voodoo (included with SC2.8), and another set of EB16 voodoo and non-voodoo kernels that were an attempt to fix all the conversion problems (but at the same time introduced a BT bug).
Depending on which kernel you have, you might be getting a different result for the date. It depends on which files they used for that kernel.
If you find that you aren't on the kernel you thought you were, but you are happy with its performance, you might want to think about just sticking with the kernel you have since there isn't a huge difference between them. Everything will get sorted out soon enough.
I'm currently running EB01 with stoc EC10 with no problems. I want to either run EC10 undervolt or the new standard volt over clocKed. This issue is the only way i can flash them is with SGS Kernel flasher. CWM (Red) will not let me flash the new Kernels. After I install any new Kernel with SGS it runns fine and then freezes the device.
How do i relsolve?
I would suggest stepping back and figuring out why cwm isn't working. Do you have the new CWM that JT released(works with all kernels and voodoo)- linked here I think is the newest one http://forum.xda-developers.com/showthread.php?t=948722 ?
If not that may be your issue. If you do then that's odd because I have it and don't have the problem with flashing EC10 kernels.
Your not the first. I was fine on adrynlynns kernal then I went to JTs kernal and thats what happened. Went back to adrynlynns kernal and im fine again.
Stock EC10 = adryn's or jt's from source?
Also, do you have voodoo enabled? Are you flashing voodoo or nonvoodoo kernels?
BUt yeah, I think the first step would be to figure out why your CWM is messed up.
If all fails maybe follow one of the tutorials and Odin/Heimdall back to the basics. And go step by step from there.
From EB01 with SC 2.9.2 to EC10
I've checked around and can't seem to find why I'm not able to flash the EC10 kernel. As stated in the title, I'm currently running EB10 with Superclean 2.9.2.
When I boot into recovery, install from SD Card, and select the EC10 ROM from my SD Card (this one from JT - http://forum.xda-developers.com/showthread.php?t=1010102), it appears to install, says complete, but after rebooting I still show EB10.
Any help greatly appreciated!
You might actually be running the kernel
go into terminal (or download one from market)
type:
su
{Press enter}
cat /proc/version
{press Enter}
You will see:
Linux Version 2.6.32.9 (kernel author@virtualbox) (gcc version 4.4.1 (yada yada yada) COMPILE DATE
If that compile date is the date the the author released the kernel you are running it. If not....sorry but someone else is going to have to help because I'm sleepy and going to bed =)
bobloblaw1 said:
You might actually be running the kernel
Click to expand...
Click to collapse
You are correct Sir! Thanks for your help! I guess I'll ignore the reading then.
What's getting me lately is battery life. I've been through the fully drain, fully charge stuff and still seem to lose about 40-50% overnight while the phone sits idle for 7-8 hours. Yes, it's a little off topic, but it seems like 10 or 15% loss overnight would be normal, correct?
Hey quick question, Running my streak with Streakdroid 1.9, only background apps are widgetlocker, twitter/facebook sync updates (even though they only seem to update properly when i tell them to.
Average use, few texts throughout the day, screen brightness on about 30%, no phone calls and minimal wifi or 3G data use as i'm around computers all day. I never use it for music/movies either.
Took off charge at 9.12AM, 86% at 12.28, after no use other use than sending 2 texts and receiving one. I got this phone in November last year, is the battery literally just this shocking or should i email DELL about getting a replacement?
TLR = Original battery dies faster than the person that says they'll brb in horror films, what do? (Also what's the correct email address to ask for?)
-Sean
Maybe you should try a new baseband?
Sent from my Dell Streak using XDA App
valest said:
Maybe you should try a new baseband?
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
See i've asked this many times, what is a baseband and what does it do? I've never upgraded it due to the fact no one has answered this question
Also how would a baseband affect battery life? My phone says: GAUSB1A131921-EU
Seanyftw said:
See i've asked this many times, what is a baseband and what does it do? I've never upgraded it due to the fact no one has answered this question
Also how would a baseband affect battery life? My phone says: GAUSB1A131921-EU
Click to expand...
Click to collapse
IIRC, baseband is a separate ARM CPU running a real time operating system that handles the actual business of communicating with the mobile phone network. When flashing the phone, 'baseband' = operating system image for this CPU. You need a baseband version compatible with the version of Android you're running (what exactly is compatible in this context depends on the phone + version of Android)
Different baseband could affect battery due to different mobile radio use pattern or maybe by keeping Android awake for longer or by different power saving behavior on baseband CPU etc.
Not Relevant said:
IIRC, baseband is a separate ARM CPU running a real time operating system that handles the actual business of communicating with the mobile phone network. When flashing the phone, 'baseband' = operating system image for this CPU. You need a baseband version compatible with the version of Android you're running (what exactly is compatible in this context depends on the phone + version of Android)
Different baseband could affect battery due to different mobile radio use pattern or maybe by keeping Android awake for longer or by different power saving behavior on baseband CPU etc.
Click to expand...
Click to collapse
I see, thank you Anyone know if it's worth looking for the best one for 1.9 Streakdroid or if i should try out DJ Steve's Streakdroid 2.0? I understand that's WIP and the baseband is completely different or something?
-Sean
Seanyftw said:
I see, thank you Anyone know if it's worth looking for the best one for 1.9 Streakdroid or if i should try out DJ Steve's Streakdroid 2.0? I understand that's WIP and the baseband is completely different or something?
-Sean
Click to expand...
Click to collapse
351 AMSS.mbn
Retail 00
353 AMSS.mbn
USA AT&T Region 31
354 AMSS.mbn
Hong Kong Region 11
Code:
fastboot -i 0x413c flash amss amss.mbn
fastboot -i 0x413c reboot
Seanyftw said:
I see, thank you Anyone know if it's worth looking for the best one for 1.9 Streakdroid or if i should try out DJ Steve's Streakdroid 2.0? I understand that's WIP and the baseband is completely different or something?
-Sean
Click to expand...
Click to collapse
Be advised,SD2.0 is still a working progress,not stable release!
Seanyftw said:
I see, thank you Anyone know if it's worth looking for the best one for 1.9 Streakdroid or if i should try out DJ Steve's Streakdroid 2.0? I understand that's WIP and the baseband is completely different or something?
-Sean
Click to expand...
Click to collapse
I'm afraid I don't know. I'm on the same baseband as you and I want to know if it's safe to install retail 351 on it. I know that the wrong baseband could stop your phone booting, might make Android unstable, prevent you making phone calls or accessing internet over 3G so I'm not keen on risking it...
nickshertzer said:
351 AMSS.mbn
Retail 00
353 AMSS.mbn
USA AT&T Region 31
354 AMSS.mbn
Hong Kong Region 11
Code:
fastboot -i 0x413c flash amss amss.mbn
fastboot -i 0x413c reboot
Click to expand...
Click to collapse
Thanks for this but which one should i use? I'm using Streakdroid 1.9
-Sean
Seanyftw said:
Hey quick question, Running my streak with Streakdroid 1.9, only background apps are widgetlocker, twitter/facebook sync updates (even though they only seem to update properly when i tell them to.
Average use, few texts throughout the day, screen brightness on about 30%, no phone calls and minimal wifi or 3G data use as i'm around computers all day. I never use it for music/movies either.
Took off charge at 9.12AM, 86% at 12.28, after no use other use than sending 2 texts and receiving one. I got this phone in November last year, is the battery literally just this shocking or should i email DELL about getting a replacement?
TLR = Original battery dies faster than the person that says they'll brb in horror films, what do? (Also what's the correct email address to ask for?)
-Sean
Click to expand...
Click to collapse
I run 1.9.1 and finally, my battery will last me over 24 hours. And thats with moderate use, trip to three hours of phone use on a bluetooth headset, and even some video from youtube or crackle. What I did this time was to install the stock 354, then 1.9.1 over that. I had bounced around between different roms so much that I'm sure my firmware files were all mismatched. Installing a stock rom from an update.pkg, not update.zip, installs several firmwares. The bandana off only one of these, albeit the most popular.
After the install I started using apps such as spare parts and cpu spy to help me figure put what was using up my battery the most. I turned my notifications to every two hours for Tweetcaster Pro and turned off notifications for Facebook. The facebook app seemed to be one of the biggest culprits.
It takes a little bit of work and patience to figure it out, but it makes a huge difference in the end. I no longer worry about my battery not making it through my day anymore.
Sent from my Dell Streak using Tapatalk
The hong kong and retail one you can try! for your question,I think the kernel is,more affect the efficiency of you phone related to battrry life.
lordmorphous said:
What I did this time was to install the stock 354, then 1.9.1 over that. I had bounced around between different roms so much that I'm sure my firmware files were all mismatched. Installing a stock rom from an update.pkg, not update.zip, installs several firmwares. The bandana off only one of these, albeit the most popular.
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
So what method did you use to accomplish that. I am interested in trying flashing stock (probably either 351, or 353) and then putting SimpleStreak 1.2 back over top. When I got some free time today and tried to do it I realized that Clockworkmod recovery replaces the option that would let me flash an *.pkg file. Did you flash the stock recovery, flash the stock rom, then reflash clockworkmod?
Thanks for the help.
cwegga said:
Did you flash the stock recovery, flash the stock rom, then reflash clockworkmod?
Thanks for the help.
Click to expand...
Click to collapse
Correct. Except use StreakMod and not Clockwork.
That's what I did this time. Though in the past I was using Clockwork because the previous versions of Streakmod I had tried didn't agree with my phone. I used Multirecovery flasher and it worked great. The only snag I went into is none of my nandroid backups would restore.* It made the whole thing more of a headache than it needed to be. From now on I guess I'll have to try restoring right after I back up to make sure everything is working.
*I tried to restore them through the same version of Clockworkmod that I had before and they all failed with the checksum error.
cwegga said:
. . . . .
*I tried to restore them through the same version of Clockworkmod that I had before and they all failed with the checksum error.
Click to expand...
Click to collapse
Did you rename the folder the backup was in? Spaces and some otjher characters can cause issues, search and you will find posts relating to this (see the clockwork and streakmod threads).
You can also manually check the md5 sums of the backup to see if the values in the file agree. There is a file named nandroid.md5 that is just a text file with the checksums, compare these values with the checksums for the files in the backup. I use hashcheck in WinXP to add the checksums to the properties dialog in the file explorer.
marvin02 said:
Did you rename the folder the backup was in? Spaces and some otjher characters can cause issues, search and you will find posts relating to this (see the clockwork and streakmod threads).
Click to expand...
Click to collapse
Nope, I didn't change a thing. At first I flashed the wrong recovery(Streakmod) and it said it couldn't find them. But I dug through my computer and flashed what I believe is the same version of Clockworkmod (should be the same, It's the only non-stock recovery I had saved) that gave me the md5 errors. No biggy though, after some hours of work and playing most of Cut the Rope again I'm pretty much back where I was.
I'm sorry for being a noob, but i tried searching for anything similar and i couldn't find it. I have the weirdest problem, i flashed openOptimus today and it booted up just fine (i did the official gingerbread update so i was on new baseband). I checked the software version, it was v20 after the flash. After a few reboots settings.apk crashed on boot, and the software version was back to v10c-OCT-12-2010. I tried re-flashing after wiping absolutely everything, 2 times,same thing. I tried ciaox's guide for updating baseband with LGMDP tool as posted on his thread, did not update the baseband (even tho the process was finished successfully). If anyone had or has a similar problem, please enlighten me with a solution, if not any suggestion is welcome, thanks
1. rom downgrading by itself? r u insane? lolz
2. Read dr. notor's thread from start to beggining here. check which baseband version u're on using lg hidden menu cuz i'm almost sure u're using a baseband that's incompatible with your current rom.
3. do u have gsm signal?
edit: it's most definitely not open optimus' fault cuz i've used that rom w/o any problems, u proly screwed something up during the upgrade/flash process. but have no fear, with some patience and forum digging u can fix it hehe
bl4ck0p5 said:
1. rom downgrading by itself? r u insane? lolz
2. Read dr. notor's thread from start to beggining here. check which baseband version u're on using lg hidden menu cuz i'm almost sure u're using a baseband that's incompatible with your current rom.
3. do u have gsm signal?
edit: it's most definitely not open optimus' fault cuz i've used that rom w/o any problems, u proly screwed something up during the upgrade/flash process. but have no fear, with some patience and forum digging u can fix it hehe
Click to expand...
Click to collapse
Yes i am aware that its not openOptimus's fault, and that i probably messed up somewhere along the line. I read dr. notor's thread from start to begining, its the same process from ciaox's openOptimus thread, with screenshots added. As i said, after a few reboots settings.apk crashed and when i checked settings>about phone, in the Software Version field it said 10c, as opposed to the 20c it said prior to the reboot, i am not sure how or why this happened, but i am wiping everything, reflashing the rom, and reflashing the baseband now to see what happens. Also, i did have a gsm signal. Thank you for the reply
Ok, then u prolly should pay attention to this part where he says
Q: How do I know it worked?
A: If everything worked, you will have a working GSM (calls, 2G/3G data) with the proper ROM installed.. On stock ROMs, you can check the baseband version via hidden LG menu. It will show AMSS6150 if you flashed v20G baseband. If you see AMSS6038, then you have a baseband from v20[ABCD...] versions. If you see anything else, you have a baseband from v10? ROM. LGMDP utility also shows which ROM version does the baseband come from (see screenshot attached). Note (CM7 users): V07u-000-000-MAR-23-2009 is NOT your baseband version but some irrelevant CM7 crap.
Click to expand...
Click to collapse
Like I said, check your baseband version using LG Hidden Menu (dial 3845#*500#).
Hey, its strange it seems to be just a bug, it happened again after i changed the settings icon and rebooted, but lg hidden menu reported baseband as AMSS6038, while settings > about phone said 10c, after a reboot it was v20 again. Im stumped, its fine now tho,thanks
filiprox said:
Hey, its strange it seems to be just a bug, it happened again after i changed the settings icon and rebooted, but lg hidden menu reported baseband as AMSS6038, while settings > about phone said 10c, after a reboot it was v20 again. Im stumped, its fine now tho,thanks
Click to expand...
Click to collapse
Certainly does not sound like a sane behaviour.
Sent from my LG-P500 using XDA App
I am a T-Mobile client using their ROM. I upgraded on KIES suggestion the Kernel to the most recent version:
PDA KF1
Phone KG2
CSC KF3
I am running in Android 2.3.3.
Phone is rooted.
I used busy box 1.17.2 and 1.19. Currently, it is 1.18.4
Everything runs fine, however, shortly after SMS usages (Messages) or telephone calls the phone either goes in a loop of MEssage - FritzBox App - Firefox. I can close the last apps while the first stays alive. No usage of anything else is possible before reboot. Sometimes telephone calls are terminated and phone shuts down.
I hope I could explain a little bit what happens. I tried to look for an error log to be more specific.
My question now is:
What causes these problems, my best guess is that the kernel is the source as it it happens only after "Communications". Is this a known issue or is there more wrong to the phone? Too many apps or a specific app?
Teddybear2 said:
I am a T-Mobile client using their ROM. I upgraded on KIES suggestion the Kernel to the most recent version:
PDA KF1
Phone KG2
CSC KF3
I am running in Android 2.3.3.
Phone is rooted.
I used busy box 1.17.2 and 1.19. Currently, it is 1.18.4
Everything runs fine, however, shortly after SMS usages (Messages) or telephone calls the phone either goes in a loop of MEssage - FritzBox App - Firefox. I can close the last apps while the first stays alive. No usage of anything else is possible before reboot. Sometimes telephone calls are terminated and phone shuts down.
I hope I could explain a little bit what happens. I tried to look for an error log to be more specific.
My question now is:
What causes these problems, my best guess is that the kernel is the source as it it happens only after "Communications". Is this a known issue or is there more wrong to the phone? Too many apps or a specific app?
Click to expand...
Click to collapse
Does sound quite odd, try clearing cache, should the issue still exist, try flashing back to stock kernel and see if it still has the same problems. Is your root kernel source same as the original?
0semaj0 said:
Does sound quite odd, try clearing cache, should the issue still exist, try flashing back to stock kernel and see if it still has the same problems. Is your root kernel source same as the original?[/QUOTE
Root Kernel is KG1 from Odia. Happened before with the other Kernel as well. I already cleared cache. There is no insecure KG2 for T-Mobile available. Any idea how to make the Kernel rootable/ insecure. I suspect it must have something to do with the Kernel. For rooting, I try always to get the insecure version of the branded one. Different kernels (insecure/ secure) that do not completely match could cause this?
Maybe I have done something wrong which is the solution. Let's start from scratch how I rooted the phone.
I had original Kernel on the phone. From this one, I upgraded straight to the insecure, rooted and than just put one the most recent one.
Is this causing the problems? So better upgrade to the next official one, than use the insecure to root and than put the official one back on. All done via ODIN? Would this be the solution?
Click to expand...
Click to collapse
I used KIES to get the orginal KERNEL on the phone. So far no problems there. I want to test it over a couple of days and then root it again. Hope this fixed it.
2 Hours later
Okay, after roughly 2 hours I came back in this loop with Internet/ Messages. I cleaned the RAM and now it works fine. Why does this happen? Never had this before. Is this an App causing or just the Kernel. I could use ODIN to get back to the first Kernel that was preinstalled. Phone is currently not rooted. However, when I use ANDROID system Info (App), under BuidlINfo I see Type: USer and USer: Root. Should I probably unroot first as the system is confused and thus these errors appear?
Hope some could help here to clarify.
Need help and advice to fix problem!!!!!
Is this what I did wrong?
I had Kernel KF3 on the phone and put straight the insecure Kernel KG1 via Odin to the phone, rooted and then had original KG2 on it. This was the time when things got worse. Had the problem with KF3 already altough I first went to KF3 via KIES and then ODIN/ SuperOneclick/ ODIN for original firmware.
Does someone have an idea how to fix it? Going back to the first firmware and upgrade then to the most recent one? Anything to check in ODIN apart from the ususal ticks in F.Reset and AutoReboot?
Please help as it is get really annoying to reboot every now and then during the day.
0semaj0 said:
Does sound quite odd, try clearing cache, should the issue still exist, try flashing back to stock kernel and see if it still has the same problems. Is your root kernel source same as the original?
Click to expand...
Click to collapse
I always thought power on/off is similar to Reboot. I was proven wrong. I just rebooted with volume up+home+power. Since then phone is stable. Sometimes TWLauncher crashes and reloads.
Thanks for the support. I think this has been fixed....hopefully.
Teddybear2 said:
Is this what I did wrong?
I had Kernel KF3 on the phone and put straight the insecure Kernel KG1 via Odin to the phone, rooted and then had original KG2 on it. This was the time when things got worse. Had the problem with KF3 already altough I first went to KF3 via KIES and then ODIN/ SuperOneclick/ ODIN for original firmware.
Does someone have an idea how to fix it? Going back to the first firmware and upgrade then to the most recent one? Anything to check in ODIN apart from the ususal ticks in F.Reset and AutoReboot?
Please help as it is get really annoying to reboot every now and then during the day.
Click to expand...
Click to collapse
KF3 and KG1 is very different...since the F and G is well, obviously different. Usually if you matched a KF4 with KF3, it should be ok but KG1 is quite different. As with anything at this point in time for you is to flash to a stable ROM currently released, which is KG5 since there are root kernel available for KG5. It is the most recent Kies official release. KH3 is newer but not official Kies. If you update to KH3, you may not be able to gain update through Kies, therefore stick with KG5. Both are Android 2.3.4 for you information, hope that solves the issue and remember to clear all Cache and Dalvik in your case since you already have issues...
0semaj0 said:
KF3 and KG1 is very different...since the F and G is well, obviously different. Usually if you matched a KF4 with KF3, it should be ok but KG1 is quite different. As with anything at this point in time for you is to flash to a stable ROM currently released, which is KG5 since there are root kernel available for KG5. It is the most recent Kies official release. KH3 is newer but not official Kies. If you update to KH3, you may not be able to gain update through Kies, therefore stick with KG5. Both are Android 2.3.4 for you information, hope that solves the issue and remember to clear all Cache and Dalvik in your case since you already have issues...
Click to expand...
Click to collapse
Problem was that a system file for synchronisation (syncmldstmo.apk) was deleted. I do not know how, but I could restore it with Titanium. Since then, all my problems seem to have vanished.
My Apps does not work. I do not see any downloaded app. Seems to be a Google problem since I stumbled over several threads.....no solution so far. I asked them directly. No solution.