Hello my name is Xan Steel. I've been trying out roms on this forum for my Epic 4G. However I've run across a lot of bugs in this rom "ACS ICS V6". I would love to be able to post them in the development thread pertaining to the rom, but since I'm under the 10 post limit to post in a dev thread. I would like to ask how I go about doing this the correct way without breaking forum rules.
Thanks in advanced
Xan Steel
Tell us what your problems are here.
1st you have to have 10 post. Go to other threads and comment on stuff like the off topic forum. Then you should be able to post on dev threads. Or you can pm them and let them know.
Sent from my SPH-D700 using xda premium
Well as Neckberg has said to post my issues here (Thanks) I shall.
[ROM] ACS ICS V6.
Where to began.
I came from ACS SyndicateFrozen 1.1.1 I could never get 1.2 to run. And this ROM was based on GB. Really wanted to see what GB was like. SO after installing the ROM. Everything started out normal (no issues at that point). It was sluggish which made me wonder if Carrier I.Q. was still in the ROM. It wasn't listed that it was removed.
SO I started trying things out. Everything was going good until I turned on the Wireless WiFi Tether. It crashed outright. Tried again, and crashed. It would open to a black screen and then crash. So I did some digging, and apparently this is a known issue. So I got a different one from the market that worked (Open Garden WiFi Tether).
I installed Opera. I like Opera for it's desktop mode that actually works over Dolphins. I would type in a address, and hit go, and it would act like its going, and then stop and remove what I had typed. Tried again, and it would load a blank page. Tried a third time, and got the HTML header to load the page in a text format. Uninstalled and reinstalled same thing happen. So I left it alone, and about 3 hours later it had uninstalled itself/completely missing on the phone and market stated it wasn't installed. Rebooted phone, still gone. Not idea where it went. After reinstalling it again. it would do the same thing.
So I flashed and wiped X3. And reloaded the ROM. Thinking I have a bad load.
reinstalled all my apps and even though Opera is still doing it's thing I mentioned earlier, it hasn't uninstalled itself... yet.
Now after the reload of the ROM. Last night I lost cell service (couldn't make calls) but I had data. Which was odd to me. Rebooted the phone, and same thing. Had data but not cell service. After about and hour or so, I have cell and data back together. Maybe it was someone working on the tower in the area at 11pm, or maybe the ROM decided it would be funny.
Another thing I noticed. If you hit the menu button to pull menus in apps and on the home screens. They are white on black. White text and image, on a black background. Now if you go into any sub-menu from the main menu, its black on black. You can't read anything unless your lucky to have a bright white page behind it, so that it can try to bleed through some of the transparency.
The battery icon when charging in portrait goes from normal to skinny (blinking), while in landscape mode it goes from normal to fat (blinking).
Also two music apps is not really needed. One is fine. Trimming down on unneeded apps would help save on space. Also remove Carrier I.Q. if it hasn't been yet.
Adding that super brightness, is actually bad. Not thinking about it, it's actually crashed the video HW of the phone. On a plain white screen at max brightness, it starts to artifact, and if what ever your trying to do doesn't complete. The video HW crashes, and you get a pretty rainbow on the screen until you pull the battery. Basically acts like a dying or dead video card in a PC. Also it can (and has happened to me) cause screen burn in. If you want a image of it let me know and I'll post one.
Also Rom Manager does not recognize any ClockWorkMod Recovery, if you manually install the recovery yourself.
If I find anything else buggy I'll post and update here.
Thanks
Xan Steel
Phone: Epic 4G
ROM: ACS ICS V6
Recovery CWM 3.1.0.1 purple
Note, I haven't tried this rom myself.
No, carrierIQ is not removed on this rom, nor has it been removed on any GB rom that I know of. Still, removed or not, it won't make any difference in the performance of the device.
Any apps that you fine are useless can easily be uninstalled, even if they are installed system/app folder. Rom chefs correct attitude about roms is that they build for themselves first. I personally have 3 music players installed.
We don't have official Rom Manager support so that will be an issue on pretty much all non AOSP roms for the epic.
Your lack of service issue it probably a carrier issue and not a rom issue.
shane6374 said:
Note, I haven't tried this rom myself.
No, carrierIQ is not removed on this rom, nor has it been removed on any GB rom that I know of. Still, removed or not, it won't make any difference in the performance of the device.
Click to expand...
Click to collapse
Ah makes sense. It's relatively new, and most likely not been worked on yet.
Any apps that you fine are useless can easily be uninstalled, even if they are installed system/app folder.
Click to expand...
Click to collapse
Ah, then I should be able to remove them myself fairly easily.
We don't have official Rom Manager support so that will be an issue on pretty much all non AOSP roms for the epic.
Click to expand...
Click to collapse
Do you know if that is something being worked on?
Your lack of service issue it probably a carrier issue and not a rom issue.
Click to expand...
Click to collapse
It's a good possibility since it only happened the one time, but since it is a beta, and I'm using it for the first time. I felt it needed to be brought up just in case it wasn't. Heh beta tested a lot of new software, and got into the habit of reporting everything, even if it looks like something else is the issue and not the software.
Many Thanks
Xan Steel
Related
Recently my phone started acting a little unusual. For instance, composed email weren't being sent out while syncing and a wipe and reflash seemed to fix it at first. This problem continued to get worse and at the same time, I started getting SD card ejected notifications seemingly without reason. Now it's to the point that my phone is completely unusable/useless. IF it boots all the way up, it will lock and then just go black. I have to remove the battery for some time to get it to turn on again. This includes loading the SPL and the Recovery interface. The ONLY way my fone will act semi-normal is if I remove the SIM card and boot it. Then eventually it will again just shut-off. I have reverted back to an older SPL with no luck (was using Haykuro's latest one until now). I have loaded multiple radio's with no luck (after reverting the SPL of course). I have tried multiple ROM builds, JF's, Cyanogens and Haykuro with no luck. This really sux. 4 month old fone and seems the radio might be fried. VERY disappointed in the quality. I hope I can get some help and warranty the phone. I am thankful I unlocked my old Blackjack and am able to use it for now. Just though I would share my tale of woe. I am not sure exactly what caused this. Maybe too much flashing? Not sure, but be aware; I feel like maybe I played too much with my phone. That last part REALLY sux cause I love my fone. I LOVE that I can play with it and install all of the great ROMs and themes. Anyway, best of luck to all you Dream owners. I hope I dont have to buy another one (cant afford it )
My fone is not bricked it just seems unstable in every way. Sad day 4 me
[UPDATE]
Before I made this post, I turned on the blue LED (holding trackball and power) and just let my phone sit there. Didn't really have a good reason to do so other than 'why not?'. Anyway, shortly after making this post, I couldn't just leave it alone so I picked up my phone again (I really do love it that much lol). While holding it and just thinking about my less and desirable situation, I noticed the back of the fone was warm like it is when you've been using it for some time. I couldn't help but think that the blue light was indicating that "something" was going on in the background so I just began pushing the buttons on the front and no specific way just randomly and all the sudden my fone rebooted. Sorry I can't say how long it was in "blue light" mode.
Now everything I had experienced and read concerning the "blue light" indicated the only way to get it out of this mode is to 1) remove the battery or 2) let the battery just die on its own. So you can imagine my surprise when the fone just rebooted. It booted up (no SIM inserted) and seem to be fine, but as I mentioned before, this had happened only to lock up and reboot itself. I just began using it as much as I could to see if it would fail again and it seemed to keep going fine so I thought "why not insert the sim again?" So...
With SIM inserted, the fone booted up fine. Again I began to put it through its paces and everything is good so far. Makes call (too late to have someone test call me), browses, downloads market, basically everything with no lockups and no reboots leaving all keys unresponsive. Damn I was happy! But not too much just yet. I'll let it keep going for sometime to make sure it's good, but I can't help but to think that putting my fone into "blue light" mode somehow "fixed" my fone fo lack of a better word. I am perplexed but pleased. Will update later after some decent testing time has gone by. I remain hopeful and regret my earlier comments regarding the fone's quality. I hope I remain regretful of this lol.
Interesting. Can you tell what EXACTLY was on the SDCARD when this happened?
lbcoder:
When this problem first happened on my phone I had folders containing my AppManager backups, ringtones, NES ROMS, camera pix and video files. It's the SD card I always have in there. I don't use apps2sd. I thought maybe there some problem with this card so I tried 2 other SDs I have with the same results; instability. I even tried a clean build with no SD card (as well as with and without SIM); all with the same results. I tried every possibly combination as a form of troubleshooting.
When I put it into blue light mode, the SD card that was installed contained DCIM (pix), appmanager, mp3s, video files, 2 different radios in .zip form (radio 1.22 and the sappire radio; neither with the name update.zip), .footprints folder, ime folder and that's about it. Did u have something in mind?
BTW, I wish I could edit the name of my thread to show there's an update...
The Blue LED has some other purpose and is simply not a "lock". That just seems silly and useless, especially since you'll find if you put it into this 'mode' it will drain your battery fairly quickly for a 'lock' mode (like 12 hours).
There's more than a 'lock' going on here...
I agree. It's doing something in the background other than just being a type of "lock". I'm don't want to claim that it fixed my phone because I have no idea what it's doing when that little blue lights is on. I am saying that it seems a little more than coincidental that my fubared fone (my feeling at the time) began to "magically" work after putting it into this mode and its subsequent reboot. I am really glad I did.
No amount of: fastboot erase "partition name", data wipes, radio/spl/rom flashing helped my fone. I was going to try and get warranty today, but now I don't need to. Back running ION and happy as h3ll! Maybe this will help someone else with a fone that refuses to function correct. Maybe it won't, but I definitely wanted to share my experience with it.
BTW, I was running Cyanogens 3.4 JF mod at the time this began. I understand some other people have had some similar issues as seen here:
http://forum.xda-developers.com/showthread.php?t=525306
These problems are very similar to what I was having, but mine seem irrecoverable even after flashing EVERYTHING. Just food for thought...
I wonder if it found one of those radios and did something with it?
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
hamshu said:
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
This is why I stay on Google Ion. It's clean, stable and fast. All these "optimized" builds seem plauged by bugs and quirks.
lbcoder said:
I wonder if it found one of those radios and did something with it?
Click to expand...
Click to collapse
Interesting thought. But it would have to have parsed the file and made a determination on its own as to whether or not it was a valid radio. Neither were named update.zip at the time. Also, I had already downgraded the radio to one of the versions that existed in file name radio_1.22.zip that was on the SD. That allowed me to downgrade the SPL without bricking because at the time I was running Haykuro's newest SPL (which I have since reflashed to my now functioning fone).
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
Actually I described pretty much the problem quoted below that is in the thread that I referenced earlier:
tearsphere said:
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on.
Click to expand...
Click to collapse
So I guess it could be open to interpretation. I think Cyanogen does amazing work. I have great respect for him and all his efforts that have given us more functionality with our Dream fones. As I said, it's food for thought. I'm not drawing any conclusions as they would be based on conjecture.
I am intrigued by the blue light mode. I really wish we knew exactly what purpose it serves.
Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
patkin said:
Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.
Click to expand...
Click to collapse
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......
kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
I am not positive what A2SD is. I have a new 8MB SD card that came today. If I pop that in what will happen. Should it be partitioned? Thanks.
Chaid said:
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......
Click to expand...
Click to collapse
Thank God I thought I was the only one. I searched but didn't see your thread. Weird problem.
Same problem here too since the new leaked 2.1 test ruu from damaged. The only 2.1 Rom that works for my needs without rebooting every 3rd or 4th time I wake it using the end call/power button is Damagedtrev 2.01, the updated 2.05 Rom in his thread just makes my phone reboot as described above. I don't have a link to his thread, but it would be interesting to see if it worked on your phone too. Other's have claimed a battery shorting might be causing this issue, but I'm not buying that. I've looked at /proc/lastkmsg for clues, but nothing obvious there. I hope the official Sprint update doesn't have this bug or sprint will be giving me a new phone. /end rant
I can't seem to find Damagedtrev 2.01
So I can't test it.
Here's the link to the thread.
I cannot post links, because of some restrictions,but here is the last part of the url.
forum.xda-developers.com/showthread.php?t=653622
here's the link for the full rom
Oops cannot post link to rom on 4shared, look in the bottom of the first post in the thread for a link to the full rom of DamagedTrev_v201
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Ok, downloading......stay tuned.
I really hope this 2.1 ROM works.....I'm kinda sick of 1.5.
Edit:
P.S. I'm reading that there is a battery issue....do you have that?
kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
Hey good news. I put the new SD card in after backing up the other one, partitioned it and copied the files and folders back on then flashed ALOYSIUS and so far so good. I have woken it up about 10 times in a row. Looking good.
I had tried that perticular Rom before with no success.
Interesting.....I'm using the 2 gig sd card that came with the phone....I wonder if that is my problem?
Well it started again. This was right after setting my Gmail and POP3 mail accounts. It shut off on the first sleep after this. Hmmmmm.
I'm re-flashing now and not setting up the mail accounts. Will report back later.
Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.
reboot
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
It's a full reboot. The phone actually turns off when it goes into sleep. You don't know it's off until you hit the button to wake it up and the phone boots up.
Now for the good news. After re-flashing and not setting up the email accounts it was still shutting downconfused so I started looking elsewhere so I opened up what I thought was a likely culprit in Autokiller and none of the presets where selected so I picked Moderate and haven't had a shutdown since which has been over an hour. Fingers are crossed. I'll report back later.
That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.
patkin, dude, I felt the same...I gave up on 2.1.
download, wipe then flash Gumbo-1.5c-BARE-signed.zip after it reboots, download and flash Gumbo-Sense-signed.zip.
You flash Gumbo-Sense-signed.zip over the Gumbo-1.5. No need to wipe or anything, it just adds to the ROM. Fast as hell and works PERFECT.
http://www.4shared.com/file/217809392/5fcf1f5d/Gumbo-15c-BARE-signed.html
http://www.4shared.com/file/217811195/3afb5fcf/Gumbo-Sense-signed.html
Give it a shot....I think you will like it......let me know =)
Gumbo thred so you can read up if you like. http://forum.xda-developers.com/showthread.php?t=630221
Chaid said:
Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.
Click to expand...
Click to collapse
Glad to see your rebooting issue was fixed with this rom even though you went back to gumbo 1.5. In my mind, this just confirms that it is not a battery issue. I never use bluetooth and have never experienced any audio loss with this rom, but apparently even people on the same hardware and firmware versions have different problems.
kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
Full Reboot here too.
patkin said:
That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.
Click to expand...
Click to collapse
Yeah, got my phone beginning of march 2010 and I also think there is something in the 2.1 test ruu or hardware that is keeping the phone from functioning properly with an altered 2.1 rom.
Just wanted to let people know what happened to resolve this. I went back to 1.5 then when 2.1 official came out last week I said what the heck if I can't enjoy a rooted custom 2.1 I'll try the official and guess what. Same problem as the other 2.1's.........phone shuts off randomly! Except this time they are replacing it with a new phone. Yeaaah! I'm probably going Evo now though since I found out I can get a new phone. Anyone need a new Hero?
I'm having the same problem.. One question. Does DarchDroid automatically move dalvik-cache to the sd
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?
So I've tried everything I could think of. Reflashing ROM, using a different ROM, different browser, everything minus a different modem, which I'm not sure would really do anything. But where I'm at is that anytime I go to status on facebook it closes the browser back to the home. I'm on Frozen ROM at the moment, I've tried on stock, same issue. Tried on the ASOP ROM, same issue, tried on those ROM's with Dolphin, Miren, Firefox, Stock Browser, all the same issues.
So will a modem actually make a difference is how the phone handles? Or is it more related to data speeds? I don't know what else to do, this is driving me absoluetely nuts. Thanks Guys.
Try this go into settings / manage application / all application & wipe data from browser & wipe data from Google search then reboot if that doesn't work I don't know
Sent from my Nexus S 4G using xda premium
Figured I would move it to the proper area. Haha. I really appreciate all the help Bro. Tried the other route you said, nothing doing. So I don't know either. It's annoying though. I think I got the phone into a bootloop now tried to install a different ROM see if that would work, and doesn't seem to be working. Piece of crap. Just my luck. Ha.`
What kernals were/are you running?
Okay, so I did ALL that, and nope, same issue. I don't know what the hell the issue is, I thought it might be the kernal, but when I flashed back to stock, had the same issue, with no kernal. So I don't know.....doesn't do this on my Photon.
odin back to stock
and clear out the sd card. redownload everything and rebackup.
Did you uninstall the Facebook app and redownload it? Wipe data in it before uninstalling. Did you try a different browser like Miren or Dolphin?
xTMFxOffshore said:
Okay, so I did ALL that, and nope, same issue. I don't know what the hell the issue is, I thought it might be the kernal, but when I flashed back to stock, had the same issue, with no kernal. So I don't know.....doesn't do this on my Photon.
Click to expand...
Click to collapse
Well, you aren't running without a kernel - the kernel is the core of the Android operating system.
Maybe you're having a hardware issue, such as a touch screen that's acting up (you said it wasn't force closing or anything, right?) - it could be registering false touches in the wrong location... I'm just taking a shot in the dark on this one, since it sounds like you've tried restoring just about everything...
I would suggest reformatting your sd card (copy the contents to your computer first, the card WILL be erased).
Then, Odin a full stock tar (try DI18, you'll get an OTA to EC05 after you boot).
Then use the one click root and recovery - be sure to have the rom on your sd card, especially if you use an ext4 recovery like 3.1.0.1, because of the file system conversion (stock kernel won't boot ext4, so you'll need to flash the rom and an ext4 kernel before rebooting from recovery - Genocide or ACS's twilight zone or vision kernel... I would stick to Genocide for now, under worked the best for me)
You might want to skip the rooting step momentarily, so you can see if the same problem occurs on a completely stock setup.
Finally, I would suggest carefully cleaning your touch screen with something mild - I use eyeglass cleaner (safe for glasses with all the expensive protective coatings), other users here might have other suggestions.
This should cover all of your bases, and if you still have problems, it might be a hardware issue.
I do want to point out that (unless I'm missing something about what you're trying to do) the facebook that you access from the browser is loaded from their servers every time you connect - it isn't software on your phone. It cannot be the older version, not like an app, which has to be updated on your phone. The pandora issue sounds like a different issue, but I still need to test that (had to get to sleep last night, I was passing out mid-sentence, lol)
EDIT: re read the first post... Pandora issue was mentioned in the SRF thread... But it seems you did try stock and other roms...
When you say it closes back to home, I think I misunderstood - I had an issue once or twice where facebook would act up, going back to my facebook home page, but did you mean that the browser simply closes and dumps you back to your phone's home screen?
Because that could be as basic as your capacitive home button registering a false touch (the opposite of the unresponsive button issue we're all used to, lol)... But cleaning the touch surface could still help... Turn the phone off first, and apply whatever cleaner you use VERY lightly... Don't use household cleaners, if you don't have eyeglass cleaner then I would research whether rubbing alcohol is safe for gorilla glass...
Side note - swype suggested "guerilla" glass... made me chuckle...
Sent from my SPH-D700 using XDA App
What he said. ^... Also I would let it
Repartition and reset time when you Odin back to stock. I know most people say not to when flashing some things, but this would be an exception. Also when you flash to stock use the victory.pit file as well as the ROM tar.
Sent from my SPH-D700 using XDA App
All righty. I'm gonna try all that. As really nothing else has worked. I do think it's something with the screen though.....I just can't figure out why it only happens on the NEW facebook. I got her using the APP now she was only using the browser before, but I would punch say four letters it would bump a couple more then close. So you may be onto something with that touch screen registering incorrect keys so would that have anything to do with the contents of the SD card itself? Or is that an actual hardware conflict with the facebook (newer version) of the software? Cause it works fine on the APP. So I guess I'm basically at a loss for how this really makes any sense ,but really appreciate all the help from you guys.
***TL;DR***I know now that 4.3 has this bug and it is something we will deal with. I understand the causes, but the problem is buried in the kernel vs the ROM, you can still read my semi adventure but I wanted to make this edit to save you time if you think I found an answer. Overall WIFI is a huge trigger for screen wakes along with shotty or chattery reception.***
First off SlimBean is pretty much the best ROM I've dealt with, so many options, faster then I've ever experienced, and sharp looking. I've been sharking around these forums for 2 years afraid to ever make a name and post due to my lack of knowledge. I love the search options for finding answers that this forum offers to visitors and I've surely used it to root an old AT&T Atrix 4G and now my current DD the Glacier. Now I feel as though I have a little bit of sense of what the heck I am doing and would like to share my path to figuring out how to make SlimBean 4.3 work for me. Who knows maybe this may help some people that have similar problems.
The problem::: On a SEMI clean install of [UNOFFICIAL]SlimBean 4.3 \\ Nightly \\ 22.08.2013 I noticed the Glacier in standby would suddenly illuminated with light although the screen was black. It was enough to light to catch my eyes as I was starting to fall asleep. I ignored it until morning then paid attention to it happening all day at work on and off constantly with the WIFI off and just mobile network, then mobile network off, reboot, nothing seemed to help and I couldn't bare the thought of the phone's screen just on all the time.
After reading threads about HTC's possibly having bad screen made from Taiwan I was in disbelief that it was the Hardware as coming from a year old version of MIUI, I never had a problem with the screen. Leading to the idea it must be a software issue / user issue in which I must of rushed the install of the ROM or it's a quirk in 4.3.
Prior to reinstalling the same ROM, I went with trying other similar ROM's finding [UNOFFICIAL] Carbon 4.3 \\ Nightly \\ 26.08.2013 literally was just released, also a super customizable fast ROM. Everything went smooth until I played music through headphones and the illuminated black screen was back. Now I'm definitely convinced it's the software so I move on to the source code of these ROM's ev_glacier-nightly-2013.08.27.
Ev_glacier-nightly-2013.08.27 Had no screen wakes after 2 hours idle on mobile network only. I wasn't in a location with WIFI as I believe a network with a lot of information chatter may be causing these standby black illumination wakes. Back to SLIM.
SUPER clean install. 1) Format SD card completely 2) fresh download w/ checked md5 of Slimbean 3) Full Wipe "wipe data factory reset" "wipe cache" 4) format/system & format/cache manually just in case 5) Clear Dalvik 6) And fix permissions since although I believe it has no point but it's just so easy to click just in case. Probably doing things double.
Here I am now.. Slimbean is back and nothing but the .zip has been installed along with updating Nova Launcher. I am waiting to reinstall GAPPS so I can first isolate this problem within the ROM itself. What I am noticing is on just mobile network 2g/3g/2g+3g I do not get the phantom wakes, but with WIFI on it so far is only happening about 20-30 seconds after the phone drops into Standby and at least now it's not long lasting, just a few screen black flashes and it's gone. The entire 20 minutes or so I've been typing this, keeping an eye on the screen it's been quiet. Progress is being made.
Now I have thoroughly read up on and used Better Battery Stats, Wakelock detector, and Greenify to help isolate problems prior to the clean install and am waiting to install any Google apps (play store) up until tomorrow so I can pay more attention to my phone and make sure it's just a WIFI wake lock causing the screen to illuminate black. Also was toying with the idea of installing 3.0.64 kernel. I'm curious as to see if it's not just the WIFI wake lock, but all wake locks that actually wake the screen. Once I'm ready to install the play store I'm going to start combing through the device using these fantastic guides and the aforementioned apps...
[GUIDE] The Total Newb's Guide to Wakelocks ::: [HOW TO] Fix Your Skyrocket's Battery Life ::: [GUIDE] Insanely Better Battery Life When Idle
My goal with this long post is to share my experience and also commended these developers on these awesome ROM's. I will post much shorter updates on how I fixed or found the exact problem. Mainly after searching I saw similar issues but not this direct "random black illuminated screen" problem. Thanks, and be sure to call me out on anything contained in this post.
the waiting game
At 9 hours from 100% charge, I'm at 40% battery with on 1.5 hours of screen time. I went through all my settings and disabled all sounds and haptic feed back. I have yet to install any apps and am running off the bare bones of just the ROM. WiFi & 4g mobile data were on all night with the screen flashing only if I used it then locked it with the power button.
Thinking I can live with these timeout 2-5 flashes, I start browsing the forum from my phone, put it down to get ready for work, look back at the phone as it is flashing black screen rampantly on it's own. Then it holds the black screen for a solid minute or two.
WiFi chatter wake lock must be doing this... Reboot to recovery - wipe dalvik - wipe cache - reboot phone. Now to test just 4g network, flash happens on first screen lock, but not as rampant. Hmmm. My next step will be to wait for full battery drain / charge then I want to try the kernal I mentioned above. 3.0.64 kernel.
Funny stuff
Realizing the Kernel I wanted to flash doesn't work with 4.3, I hope at least some of the 86 people that viewed my post got a laugh. Even the older version of SlimBean causes the random screen flashes and the screen on while charging even with the ROM settings for such off. WiFi seems to be the greatest cause. It's as if wakelocks are actually being represented as screen flashes since the kernel is so powerful.
I just don't want to use the CM ROM...
I'm going to dig around the forums further and type in different key words of my problem just to make sure I didn't miss someone already answering this question. Slim has all the functions I always wanted out of my droid and I'm dead set to make it work...or just live with screen flashes I guess.
Hope this is a comedy for someone.
only other link
I've found on the issue I have.
http://forum.xda-developers.com/showthread.php?t=1148057
Non-Stop ROMS
1) SlimBean 4.2 & 4.3 Both have this black screen flicker / black screen wake / black screen on while charging.
2) Carbon 4.3 Had it black screen on while listening to music / black screen constant while charging
3) Evolve 3.3 based of 4.3 seemed to work fine, but I wasn't a fan of the larger Icons and screen, similair to CM 4.3 so I didn't leave it long enough to test...
4.3 CM 4.3 black screen wake almost constant / black screen on while charging... also didn't last long to really test everything.
I am down the river if I want this to just go away. I have installed all these ROM on a completey clean formated SD card each time
I'm sticking with SlimBean as it has the looks and reacts like I expect my phone to. After doing some more searching and after a little time has passed for more 4.3 development there may be a kernel that will work better for me.
Oh here is another dead end I've found... http://forum.xda-developers.com/showthread.php?t=2185747&page=3 [KERNEL] Fixed the flickering screen problem,CM10,CM10.1,SENSE3.6 4.0 4.1 That goes no where...
wifi
WiFi is the biggest culprit for the random screen wakes. I've just been living with it since I dig the slimbean 4.3 ROM so much. Thought I might pop back on here to make some closure. I worked on removing some apk's from the already minimal gapps I installed and will soon start a separate thread on just that. As long as after searching I don't find the same info I figured out.
I think you've got the screen flicker bug.
Try flashing the .69 kernel, it claims to stop the flicker.
Also I know it's got something to do with the WiFi. I know a little about it though.
Sent from my myTouch 4g using xda app-developers app
thanks for the response
N_otori0us_ said:
I think you've got the screen flicker bug.
Try flashing the .69 kernel, it claims to stop the flicker.
Also I know it's got something to do with the WiFi. I know a little about it though.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
I see you all over the place when it comes to Glacier threads. Today at work I was searching around for a download link. I read through a ton of other ROMS threads hoping it was buried in the comments somewhere. So far I only turned up and old thread with a dead link and a couple of other threads you mentioning to other people to download the .69 KERNEL which I am guessing the full version number is 3.0.69, if it's not then there may be my first problem in finding the link...
*edit
this is the main thread I keep finding, you have so many other kernels on there
http://forum.xda-developers.com/showthread.php?p=43983635&highlight=+69#post43983635
I have a little idea about the screen flicker.
A member called zyGh0st told me. I've pmed Elgin but no response.
I'll pm coderzs too Lil.
Sent from my myTouch 4g using xda app-developers app
reading about kernals
N_otori0us_ said:
I have a little idea about the screen flicker.
A member called zyGh0st told me. I've pmed Elgin but no response.
I'll pm coderzs too Lil.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
All the Kernels in the Glacier Bible page you have been keeping up seem old. I'm nervous to try one since they obviously seem like they won't work. I'm game to try what ever and post on here my progress so if anyone else stumbles upon the issue they can guide their way through it.
I've been searching "kernel 3.0.69", "kernels 4.3 roms", "jb rom kernel", "4.3 jb kernel", sometimes including the term "glacier" or "MT4G" with little to no luck between XDA and just google itself. I always just find ROMS that just mention the kernel but have no downloads.
Reading your older posts I see that youve already tried the kernel.
Sent from my myTouch 4g using xda app-developers app
K is for kernel
N_otori0us_ said:
Reading your older posts I see that youve already tried the kernel.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
I tried 3.0.64 kernel, not this mysterious .69 kernel you have mentioned. If you have a link or mirror of it I'll be glad to give it a go.
___________________________________________________________________________________________________
Found how you added the 2 kernels to the Bible page, I just flashed .64 again and I'm nothing but bootloops. I'll give .62 a chance since now I'll have to re-flash Slim.
___________________________________________________________________________________________________
make the double bootloops with either of those 2 kernels. I waited like 5 minutes, restarted the phone to see if it would boot and it just stayed on the slim splash screen. Of course I wiped dalvik and cache before installing either.
Bottom of your 5th post
Sent from my myTouch 4g using xda app-developers app
addiction
N_otori0us_ said:
Bottom of your 5th post
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
Oh yes, I head that already downloaded on the SD but the name CM_SENSE made me think it was a ROM not a kernel. The .66 kernel link is dead, but the .58 flashed & works but there is still the flicker on 4.22 SlimBean. 4.22 is so lame compared to 4.3. Even if there wasn't a flicker on 4.22 I don't think I'd keep it. Those big ICONS are just too much. I think that's why I like Carbon also. Anywho...
My addiction to messing with my phone is always in conflict with work. As if I don't have enough problem solving to deal with outside of cell phones.
I am going to try out the recovery I see in your signature, Recovery : 4EXT 1.0.0.5 RC8, just to see if it makes a difference. If you have the same phone without the same problem I must then eliminate the different variables to find the true problem. I found a "how to" and am either going to put in the time in a couple of hours or tonight. Then I'm going to start the rounds of testing ROMS / KERNELS all over again and I'll post my findings here.
I appreciate the back and forth, I actually got a can't thank anymore message because I used up my 8 yesterday~
Living with it
I've been just living with the screen flash. The ROM is just to sweet to give up. At some point if there it a completely stable 4.3 I may upgrade.
On a regular work day I don't have any available WIFI, so I toggle it off then reboot the phone every morning. I usually get a random screen flash everytime I manually lock / turn the screen off and that's it. With WIFI on I get random flashes at random rates and for random lengths.
Playing music invokes these random black screen wakes also, I've stuck to my old blackberry as my MP3 player...I know that statement seems extemely wrong and against all sciences, but the 9780 bold works perfect as a music player. They had the long-press song skip in the volume button well before anyone added it to Android.
If ever I find the correct ROM / KERNEL combination, or someone else figures out the problem and I find it, I will post it here. This winter I am going to get more into understanding & compiling roms + digging through code so maybe I'll find it myself...ha!
tonyMEGAphone said:
I've been just living with the screen flash. The ROM is just to sweet to give up. At some point if there it a completely stable 4.3 I may upgrade.
On a regular work day I don't have any available WIFI, so I toggle it off then reboot the phone every morning. I usually get a random screen flash everytime I manually lock / turn the screen off and that's it. With WIFI on I get random flashes at random rates and for random lengths.
Playing music invokes these random black screen wakes also, I've stuck to my old blackberry as my MP3 player...I know that statement seems extemely wrong and against all sciences, but the 9780 bold works perfect as a music player. They had the long-press song skip in the volume button well before anyone added it to Android.
If ever I find the correct ROM / KERNEL combination, or someone else figures out the problem and I find it, I will post it here. This winter I am going to get more into understanding & compiling roms + digging through code so maybe I'll find it myself...ha!
Click to expand...
Click to collapse
Have fun man, and If you ever need help or guidance just tell us, we'll be here