hi guys, one month ago i had a custom rom on my i9003 but the notification bar bug annoying me, it became black and doesn't show nothing some times...is there a fix for it or not? thanks
I never had this issue on any cm9 rom, do a clean install and wipes (data / dalvik) after and before flashing cm9 .zip
Notification pull down going blank at times is a known cm9 bug since alpha 9 or 10.
Sent from my GT-I9003
I don't experience it too frapeti.
Must be because of lag or something.
I used to get it a lot on earlier CM9 alpha builds. It happened on recent builds as well, but very rare.
I'd stay it still is a bug, a minor one.
well, i'm not the one that find that bug. I've flashed always with full wipe, maybe it needs another base?
I had the same issue, often on the latest cm9a11
Nemed said:
I had the same issue, often on the latest cm9a11
Click to expand...
Click to collapse
maybe it comes with not fully hw composer?
coolpix90 said:
maybe it comes with not fully hw composer?
Click to expand...
Click to collapse
I don't really know...
its becouse you push your phone too much when its loading and you are causing the bug, of course its not your fault, maybe it has to be fixed upstream (cyanogenmod repo) but most of newest phones comes with min 1ghz, next time try flashing and booting well, give the phone at least 5 mins to boot up, and do what it have to do, then use your phone as normally.
frapeti said:
its becouse you push your phone too much when its loading and you are causing the bug, of course its not your fault, maybe it has to be fixed upstream (cyanogenmod repo) but most of newest phones comes with min 1ghz, next time try flashing and booting well, give the phone at least 5 mins to boot up, and do what it have to do, then use your phone as normally.
Click to expand...
Click to collapse
this is not my bug... i've installed with full wipe ( before and after ) as always, and i don't push my phone when loading, it shows occasionally when drop down the notification bar
coolpix90 said:
this is not my bug... i've installed with full wipe ( before and after ) as always, and i don't push my phone when loading, it shows occasionally when drop down the notification bar
Click to expand...
Click to collapse
"This is not my bug". Alright we know.
In my point of view, it happens when you are doing many things at the same time, or the phone is laggy at that point of time.
And that causes some delay.
As i said it's the only way i can explain since it doesn't happen to me anymore.. you'll have to wait for someone to give a technical explanation.
frapeti said:
its becouse you push your phone too much when its loading and you are causing the bug, of course its not your fault, maybe it has to be fixed upstream (cyanogenmod repo) but most of newest phones comes with min 1ghz, next time try flashing and booting well, give the phone at least 5 mins to boot up, and do what it have to do, then use your phone as normally.
Click to expand...
Click to collapse
honestly it happens randomly, not after boot ...and i flashed on a clean kpu...
Related
hello, i have uploaded my rom to ICS and have it been using for the past 4 months
last week i came in to the issue of the battery status being unknown, 999% or 1000% battery power
i've fixed this issue in the past by flashing the rom
but this time i have trouble, it seems that ever time now that the phone is powered off and powered back on the battery status returns to 999%
i have uploaded the rom egb-nightly-2012-07-01-signed on my phone and no matter how many times i flash the battery status is lost
so i am here wondering if there is a simple fix to this, downloading a apk file or anther way to configure the phone so it will read my battery status or do i have to simply buy a new battery?
please help and thank you in advance
You sure you did the flash right?
Sent from my G2X using EaglesBlood build 5
Did you reset batt stats in recovery?
Also when this did happen to me, i was always told to just cycle AP mode, and it did work.
Yours seems more persistant though.
I would make sure batt is fully charged (charge it with phone off if your that unsure) and than first boot goto cwm and clear batt stats.
Sent via G2x on temasek CM7 b135.2, Trinity TD158 kernel on xda premium
TMK216 said:
You sure you did the flash right?
Sent from my G2X using EaglesBlood build 5
Click to expand...
Click to collapse
ok im flashing right now as we speak, this is what i am doing
wiped data/factroy reset - Done
wipe cache partition - Done
wipe dalvike cache - Done
and this time im also wiping battery stats - Done
installing egb-nightly-2012-07-01.zip - Done
wiped again in rom install file
installing gapps-ics-20120420=signed.zip - Done
phones first boot----battery status set 100%
unplugging phone now and rebooting - battery still reading 100%
reboot #2 - battery reading 100%
reboot #3 - battery reading 100% problem maybe fixed
if issue continue i will carry on with this forum
i seem to be having trouble with the quick reboot now... seems to be just powering down my phone....
I've had trouble with the reboot before in eaglesblood and to be frank I think its normal to some degree for most roms. As for the battery problem I've noticed in my experiences that if something like that were to occur it usually dealt with my kernel but I mostly run 7.2 and not ICS so there maybe some differences here.
deathmaker06 said:
I've had trouble with the reboot before in eaglesblood and to be frank I think its normal to some degree for most roms. As for the battery problem I've noticed in my experiences that if something like that were to occur it usually dealt with my kernel but I mostly run 7.2 and not ICS so there maybe some differences here.
Click to expand...
Click to collapse
thank you for the response
last night i modded the dpi and installed the market mods and rebooted the phone and the phone battery info crashed again...
anyways today i flashed my phone loaded a older version of ICS, reboot my device and the battery status is still working after i changed my dpi, for some reason i feel the issue is fixed now but i will post in the future if this issue carries on
thank you
ok i was updating framework animations and yet my battery went back to 999%... WTF
why is it doing this?
ive never had so much trouble with my phone
what am i doing to the phone that it makes it do this
i ask again could this be just battery issues?
I had a lot of issues with the phone reboot myself. That sounds crazy. My only issue I had was the date and time would not sync off my Sim card. Seems like a lot of people don't like the eb rom and I don't know why cuz I love it.
Sent from my G2X using EaglesBlood build 5
The battery shows you 999%?, maybe a baseband problem...
but like iron man would say... 999%??? cool....
CyanogenMod 9 is a free, community built distribution of Android 4.0 (Ice Cream Sandwich) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This phone isn't my daily driver, so I only tested a few things, and only slightly:
Known Bugs:
BLN is wonky. This is a CM9 thing and applies pretty much to all the msm8660 devices that use the cypress-touchkey BLN driver. Unlikely to be fixed
Other things maybe? Discuss in the thread...
How to get it:
Download: http://get.cm/?device=t769 (ChangeLog)
Or download it directly through ROM Manager or CM Updater.
Google Apps:
Make sure to download and install the ICS GApps
http://goo.im/gapps/gapps-ics-20120429-signed.zip
IF YOU ARE COMING FROM ANOTHER ROM, PLEASE MAKE SURE TO DO A FACTORY/DATA RESET BEFORE USING THIS. This isn't up for debate. A reset of the dalvik cache helps too. If you do a dirty flash, please make sure to do a dalvik cache wipe. If you have searched this forum for a problem and haven't found it, please do a nandroid backup, then a full factory/data reset and check to see if you still have the problem. If it still persists AFTER the factory/data reset, then report it here.
Thank You!
CyanogenMod Team (all of you, seriously, you guys are awesome)
SGH-T989 Devs (all of you, cuz I basically stole all your configs)
ShabbyPenguin & PlayfulGod for encouraging me when times looked grim.
UberPinguin and others on #jb-dev-e4gt for helping me get all of this work into CM proper
Oreo, my dog, for licking me whenever I needed it.
Older/Unofficial Versions (don't use if you can help it).
For older/legacy/test/unofficial versions of my work, you can find them (for a while at least) here: My Funhouse. Please take care and all necessary steps to verify MD5 sums before installing any zips.
Since CM9 is not a moving target like CM10, it may be some time before we get a point release. Therefore the occassional CM9 Nightly will have to do.
I'm not creating a Q&A thread for this one. Please behave yourselves and be nice to your neighbors.
That is all
Nice work getting it official man
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol
erikmm said:
Nice work getting it official man
Click to expand...
Click to collapse
Thanks. This should be fairly complete too. There isn't much else I can do for it. People feel it's stable and like it.
Also, it's good that the repos are up. That means people can build/maintain roms for some of the cm derivatives. I'm actually curious to see what ParanoidAndroid looks like on this device. Been meaning to load up thomas.raines work
does cm9 have wifi calling?
Bradlees said:
does cm9 have wifi calling?
Click to expand...
Click to collapse
no it doesnt.
dr4stic said:
Thanks. This should be fairly complete too. There isn't much else I can do for it. People feel it's stable and like it.
Also, it's good that the repos are up. That means people can build/maintain roms for some of the cm derivatives. I'm actually curious to see what ParanoidAndroid looks like on this device. Been meaning to load up thomas.raines work
Click to expand...
Click to collapse
Lol yea that's true I got aokp-jb and ics almost complete so again thanks for the work
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol
I've been using this due to the stability over cm10. Good stuff!
Hardkeys illumination
Been wondering what changed from cm-9-20121025-UNOFFICIAL-t769 to cm-9-20121030-NIGHTLY-t769? I did a dirty flash (wiping dalvik only) coming from unofficial to nightly and I notice the hardkeys won't illuminate after screen timeout / unlock. After I wait off the set button light timeout (mine is set to 6s) the keys once again illuminate and this doesn't reoccur until the screen goes out again. Anyone else experiencing this?
lnxzilla said:
Been wondering what changed from cm-9-20121025-UNOFFICIAL-t769 to cm-9-20121030-NIGHTLY-t769? I did a dirty flash (wiping dalvik only) coming from unofficial to nightly and I notice the hardkeys won't illuminate after screen timeout / unlock. After I wait off the set button light timeout (mine is set to 6s) the keys once again illuminate and this doesn't reoccur until the screen goes out again. Anyone else experiencing this?
Click to expand...
Click to collapse
Yeah, that's the BLN (button lights notification) bug listed at the top. Incidently, the driver/kernel should be identical from 10/25 to 10/30, which is where that bug lives.
dr4stic said:
Yeah, that's the BLN (button lights notification) bug listed at the top. Incidently, the driver/kernel should be identical from 10/25 to 10/30, which is where that bug lives.
Click to expand...
Click to collapse
I see, tnx for the clarification as it was my understanding the issue only occurs when the lights are actually used for notifications hence the BLN name. Oddly enough I didn't notice this happening when I was running the unofficial build, must have been a coincidence then I suppose.
CM9 after 11/2 will contain WiFi Random MAC fix
Folks,
The next nightly build (they happen weekly) for CM9 will contain the WiFi Random MAC bug fix. This will
This completes the list of bugs to be fixed for CM9.
The change went in after 11/2, so pick up the nightly that comes out after that. Otherwise I'm also posting a flashable zip file in my funhouse to hold you guys over till a new nightly for CM9 is available. I'm not actually sure when they run
dr4stic said:
Folks,
The next nightly build (they happen weekly) for CM9 will contain the WiFi Random MAC bug fix. This will
This completes the list of bugs to be fixed for CM9.
The change went in after 11/2, so pick up the nightly that comes out after that. Otherwise I'm also posting a flashable zip file in my funhouse to hold you guys over till a new nightly for CM9 is available. I'm not actually sure when they run
Click to expand...
Click to collapse
I am using an external SD card for my apps rather than the internal flash. After I applied the kernel zip, my memory change to internal. No big deal I thought, so I changed it to external, and did a reboot. After reboot, the check box is unchecked, but looking at the app manager, it still shows the internal flash first. Thankfully, I did a backup first, so I am restoring now. Is this a know issue? Sorry if it has been asked before but I did not see it in the thread. Thanks again for your work......
boulos said:
I am using an external SD card for my apps rather than the internal flash. After I applied the kernel zip, my memory change to internal. No big deal I thought, so I changed it to external, and did a reboot. After reboot, the check box is unchecked, but looking at the app manager, it still shows the internal flash first. Thankfully, I did a backup first, so I am restoring now. Is this a know issue? Sorry if it has been asked before but I did not see it in the thread. Thanks again for your work......
Click to expand...
Click to collapse
This is why swiching mounts is not great. The kernel flash replaces the boot.img.
Your best bet might be to wait till the next CM9 nightly comes out and modify that one.
Nightly build
CM9 downloads seem to go to internal storage but CWM was directed to perform update from external sd (ie microsd card). Unless I'm missing something, it doesn't look like the location can be changed manually.
Can someone please explain what the BLN bug is? I understand that the led back lights do not function 100% correctly, but in what ways do they malfunction?
creeve4 said:
Can someone please explain what the BLN bug is? I understand that the led back lights do not function 100% correctly, but in what ways do they malfunction?
Click to expand...
Click to collapse
I've been wondering the same thing, from what I experienced so far it seems that the button lights won't come on after screen lock/timeout. The actual BLN notifications seem fine to me, probably worth mentioning the actual notification light option needs to be enabled otherwise BLN won't work.
Does anyone have issues with mobile data connection dying with CM9? For whatever reason mine randomly quits working almost daily and the only way to recover is a reboot, turning data on/off or airplane mode doesn't fix it... Inconvenient to say the least, WiFi still works fine... Oh and BTW I didn't had this issue with the debloated/deodexed stock GB or ICS.
Which cm9 version are you using?
Sent from my SAMSUNG-SGH-T769 using xda premium
lnxzilla said:
I've been wondering the same thing, from what I experienced so far it seems that the button lights won't come on after screen lock/timeout. The actual BLN notifications seem fine to me, probably worth mentioning the actual notification light option needs to be enabled otherwise BLN won't work.
Does anyone have issues with mobile data connection dying with CM9? For whatever reason mine randomly quits working almost daily and the only way to recover is a reboot, turning data on/off or airplane mode doesn't fix it... Inconvenient to say the least, WiFi still works fine... Oh and BTW I didn't had this issue with the debloated/deodexed stock GB or ICS.
Click to expand...
Click to collapse
I've found that CLEAN flashes eliminate this for me on all ROMS. I think multiple dirty flashes like flashing updates over previous versions will eventually mess things up expecially when changes r made to the kernel
-I'm not a Dev, I just flash alot-
-If I've helped you the Thanks button is only 2 clicks away!
@woodzx67: Currently latest official cm9 20121125
@johnb380: Started fresh with a full wipe a few times already, makes no difference in this case as the data connection issue has always been there for me with cm9 in particular. I've only used cm10 briefly, don't recall that happening but then again the SOD issue prevented it from running for too long.
I've installed cyanogenmod 9.1 a couple of weeks back and it seems I have a wifi problem. At first it worked ok but lately it seems that the wifi freezes in "enabeling wifi" mode. It works fine if I reboot the phone but I'm tired of doing that evrey time I want to connect to my wifi. I've also tried something with "echo murata > /data/.cid.info...etc" that I found is used for fixing this for samsung galaxy s3, it worked at first use but then nothing.
A solution could be keeping the wifi always on but this drains the batery.
Hope someone can help me with this...Thanks in advance.
chrisszz said:
I've installed cyanogenmod 9.1 a couple of weeks back and it seems I have a wifi problem. At first it worked ok but lately it seems that the wifi freezes in "enabeling wifi" mode. It works fine if I reboot the phone but I'm tired of doing that evrey time I want to connect to my wifi. I've also tried something with "echo murata > /data/.cid.info...etc" that I found is used for fixing this for samsung galaxy s3, it worked at first use but then nothing.
A solution could be keeping the wifi always on but this drains the batery.
Hope someone can help me with this...Thanks in advance.
Click to expand...
Click to collapse
Hi, the reason for this is unknown.. but upgrading to Android 4.2.2 + seems to fix the issue. It was fixed in the kernel for those ROMs.. So only possible workaround is to upgrade to 4.3.1.. which is bugfree..
Edit .. : Now I recall that it was an issue with the wifi drivers in the kernel. If you can .. search for the wifi fix by Immortalyash .. He had done it in cm9.. as well as in minicm9. check it out.
Red Devil said:
Hi, the reason for this is unknown.. but upgrading to Android 4.2.2 + seems to fix the issue. It was fixed in the kernel for those ROMs.. So only possible workaround is to upgrade to 4.3.1.. which is bugfree..
Edit .. : Now I recall that it was an issue with the wifi drivers in the kernel. If you can .. search for the wifi fix by Immortalyash .. He had done it in cm9.. as well as in minicm9. check it out.
Click to expand...
Click to collapse
Thank's for the suggestion...will try one or the other this evening.
chrisszz said:
I've installed cyanogenmod 9.1 a couple of weeks back and it seems I have a wifi problem. At first it worked ok but lately it seems that the wifi freezes in "enabeling wifi" mode. It works fine if I reboot the phone but I'm tired of doing that evrey time I want to connect to my wifi. I've also tried something with "echo murata > /data/.cid.info...etc" that I found is used for fixing this for samsung galaxy s3, it worked at first use but then nothing.
A solution could be keeping the wifi always on but this drains the batery.
Hope someone can help me with this...Thanks in advance.
Click to expand...
Click to collapse
this is a common bug in cm9 & minicm9 roms..4.3 roms don't have this issue. I'm using minicm9 with aries kernel oc & no wifi toggle issue yet..you should try aries kernel too maybe it'll solve your problem.
Affangta said:
this is a common bug in cm9 & minicm9 roms..4.3 roms don't have this issue. I'm using minicm9 with aries kernel oc & no wifi toggle issue yet..you should try aries kernel too maybe it'll solve your problem.
Click to expand...
Click to collapse
And what is the difference between cm9 and minicm9?
New problems...
So i've tried a bunch of different kernels starting with pandora r3...that didn't do anything, then i installed garuda v5 that fixed the wifi problem but made another one...that being it can't recognize the sd card anymore, i can see the second partition but sd card appears removed and when i take the card out i can still see the message sd card unexpectedly removed, so most of the apps are crashing, and also when i go to Settings->Storage i get "Settings has stopped". This also happens for Settings->Apps.
Now i've reflashed pandora but i think something from garuda remains because i still get the errors from it even with pandora installed. And i know this because every time i reboot, after the cm9 logo i get "Android is upgrading. Optimizing xx from xx apps". I've only seen this with garuda.
I wanted to try aries kernel now but cannot download it because i cannot see the card and i'm also at work so i'm not able to connect the phone to the pc and copy the kernel from recovery mode because of the restrictions on the computer....It's really messing my day...Should I do a clean install when I go home? What is the best cm version for this phone? I've also had 10.1 but this had problems with the alarm...like it only rang after i woke up and unlocked the phone...never at the hour selected...and also it drained the battery faster...Waiting for a good suggestion for this letter ...Thanks in advance!
chrisszz said:
So i've tried a bunch of different kernels starting with pandora r3...that didn't do anything, then i installed garuda v5 that fixed the wifi problem but made another one...that being it can't recognize the sd card anymore, i can see the second partition but sd card appears removed and when i take the card out i can still see the message sd card unexpectedly removed, so most of the apps are crashing, and also when i go to Settings->Storage i get "Settings has stopped". This also happens for Settings->Apps.
Now i've reflashed pandora but i think something from garuda remains because i still get the errors from it even with pandora installed. And i know this because every time i reboot, after the cm9 logo i get "Android is upgrading. Optimizing xx from xx apps". I've only seen this with garuda.
I wanted to try aries kernel now but cannot download it because i cannot see the card and i'm also at work so i'm not able to connect the phone to the pc and copy the kernel from recovery mode because of the restrictions on the computer....It's really messing my day...Should I do a clean install when I go home? What is the best cm version for this phone? I've also had 10.1 but this had problems with the alarm...like it only rang after i woke up and unlocked the phone...never at the hour selected...and also it drained the battery faster...Waiting for a good suggestion for this letter ...Thanks in advance!
Click to expand...
Click to collapse
For the sd card issue you can try multimount from the playstore
Also check the 4.3 roms as they are very stable and don't have any issues.
And before flashing any rom just do a factory reset, thats all...
Hit THANKS if I helped
SSKSSK said:
For the sd card issue you can try multimount from the playstore
Also check the 4.3 roms as they are very stable and don't have any issues.
And before flashing any rom just do a factory reset, thats all...
Hit THANKS if I helped
Click to expand...
Click to collapse
Tried the multimount app...didn't work...will check 4.3 roms later today.
Thanks for the response
android.process.media has stopped
So after installing CM10.2 weekly 7 every time i try to download something from play that is what I get...
chrisszz said:
So after installing CM10.2 weekly 7 every time i try to download something from play that is what I get...
Click to expand...
Click to collapse
Weekly 7 has some sort of issues.. read the thread before you flash anything. You can try weekly 6.. it doesnt have any known issues.
chrisszz said:
So after installing CM10.2 weekly 7 every time i try to download something from play that is what I get...
Click to expand...
Click to collapse
You can try Carbon 4.3 rom or the TriumphHD 4.1 rom as they r stable
Try Carbon 4.3
chrisszz said:
And what is the difference between cm9 and minicm9?
Click to expand...
Click to collapse
not much..cm9 is build for hdpi devices & minicm9 is for mdpi devices so it flies better on our pico.
I've installed cm10.2 weekly 6 and it works fine...a bit laggy sometimes but it's stable...now i'm having trouble increasing internal memory. I tried mounts2sd but it messed things up...
chrisszz said:
I've installed cm10.2 weekly 6 and it works fine...a bit laggy sometimes but it's stable...now i'm having trouble increasing internal memory. I tried mounts2sd but it messed things up...
Click to expand...
Click to collapse
You can try int2ext+.. it works fine.. just backup your apps using titanium backup or helium or similar and reflash the ROM with int2ext
Ok so finally I've managed to make everything work. First I tried to increase the memory using int2ext+ but it got stuck in cm logo loop, or I didn't wait enough I don't now, but then i reflashed using int4ext+ and it worked like a charm . So thanks everyone for the feedback and have a nice day...Cheers!
my experiences for htc explorer roms
more than 40 different rom and kernel for a long time I did try.
1-original stock rom-telephone conversations is extremely slow and sometimes do not sound or sound from the other side
2- CM7 - do not even need to comment ... very very impractical .
3- cm9 do not have any problems except for the opening of wifi for everyday use . There are original rum they use a much more streamlined and spacious
Everything was excellent but the 4- cm -10 is based on telephone interviews with purpose robot voice problem. solved the problem with different kernel installations
5- cm - 1.10 robotic voice problem ..
6 - cm 10.2 ( 4.3.1) and freezes a lot of memory problems programmer jobs Even though there is a friend that is useful for cm9 combinations up there and he's coming rom with different kernels .
Result : the value to be used as a result I have seen many times rom Trials following : Vanir AOSP (thanks 7alvi ) + sakindia aries 767 mhz oc kernel 3.5 stable and smooth with use .. If I find a single fault for making a phone call notification panel wide-screen mode by turning itself down opening.its got a lead on the issue .:good:
fromturkey said:
more than 40 different rom and kernel for a long time I did try.
1-original stock rom-telephone conversations is extremely slow and sometimes do not sound or sound from the other side
2- CM7 - do not even need to comment ... very very impractical .
3- cm9 do not have any problems except for the opening of wifi for everyday use . There are original rum they use a much more streamlined and spacious
Everything was excellent but the 4- cm -10 is based on telephone interviews with purpose robot voice problem. solved the problem with different kernel installations
5- cm - 1.10 robotic voice problem ..
6 - cm 10.2 ( 4.3.1) and freezes a lot of memory problems programmer jobs Even though there is a friend that is useful for cm9 combinations up there and he's coming rom with different kernels .
Result : the value to be used as a result I have seen many times rom Trials following : Vanir AOSP (thanks 7alvi ) + sakindia aries 767 mhz oc kernel 3.5 stable and smooth with use .. If I find a single fault for making a phone call notification panel wide-screen mode by turning itself down opening.its got a lead on the issue .:good:
Click to expand...
Click to collapse
I don't know why you faced so much issues because for me there are no such problems..only cm9 wifi toggle issue was there before using aries kernel & ofcourse cm10.1 bluetooth toggle issue. I never faced robotic call or freezing problem on any rom.
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Infused4life said:
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Click to expand...
Click to collapse
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
joel.maxuel said:
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
Click to expand...
Click to collapse
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Infused4life said:
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Click to expand...
Click to collapse
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
5529
joel.maxuel said:
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
Click to expand...
Click to collapse
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Infused4life said:
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Click to expand...
Click to collapse
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
joel.maxuel said:
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
Click to expand...
Click to collapse
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Infused4life said:
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Click to expand...
Click to collapse
I am not sure if you are still facing the same issue but if you are facing reboots, then considering doing a fresh install after cleaning your internal storage as well since the remnants of the apps from previous installs have caused me problems. Ever since I started doing a fresh install (Factory reset, wiping the cache, wiping the dalvik cache and even the cache partition along with the wiping of the internal storage), there have been no reboot issues.
Hello.
My problem is that sometimes, when I receive a notification, ambient display turns screen on to show it (as it should do normally), but then, when it is supposed to turn screen off again, it only goes black, but the backlight is still on. It's hard to notice, but I don't want the backlight on, using battery, when I think it's off.
The only way to turn it off is by activating ambient display again (moving the phone, waving in front of proximity sensor, pressing power button), and then it would show my normal lock screen and then turn off, until "something" makes it leave the backlight on again.
Anyone have/had/knows this issue? I've used Mokee ROM, now I'm on RR and it happened on both, I don't remember if it happened in CM. Could it be something app related?
Thanks.
Yeah same happened with cm 12.1 latest nightly too.....just checked it now...
The Answer
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
That's strange! I guess it may be something like the drivers you said, because just one user said that have the same problem, but I'll have to wait until I have some free time to flash stock and root and flash CM and restore all apps and that again... I hate that part of installing another ROM.
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Secuential said:
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Click to expand...
Click to collapse
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
therealduff1 said:
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
Click to expand...
Click to collapse
Thanks!
1)I can't tell if it occurs on stock, because on stock I use moto display (which doesn't have this issue).
2) I'm almost sure, because I've used 2 ROMs and both do the same. Maybe I'll have to try with CM nightlies?
3)I followed the guide in "general" section to flash stock using fastboot and android sdk. After that, I booted on stock, then rebooted to bootloader, flashed TWRP, entered to recovery, wiped data and then flashed RR ROM with it's gapps and then flashed moto camera and gallery. After that, wipe dalvik and cache and rebooted to system.
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
therealduff1 said:
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
Click to expand...
Click to collapse
Well, the other user that commented on this post was also using latest CM nightly, so I'm not very positive about it, but I may try it when I have time.
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
therealduff1 said:
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
Click to expand...
Click to collapse
Thanks! I have a lot of work right now, so I can't work with this now, but I'll email you when I have more free time!