[Q] Is the bot that compiles nightlies broken? - Nook Color Q&A, Help & Troubleshooting

Noticed there are no new builds since 4/25/11. Anyone know what's going on?
Must....flash.....new....build.......

No one knows, eh?
Figured other people would be concerned that we aren't getting updates...oh well!

I'm about to build a myself one here soon. I will PM you the link if you care. Hopefully this isn't against the rules.
Edit: Nvm, not worth it as it still seems to have mounting issue.

Related

Camera Problems Compilation

Hey there everyone, I was not sure if I should post this here or in the upgrading forums, so I decided to post on both.
I'm really happy about my Artemis, but as I've seen around the forums, everyone ends saying the camera is a crap, tho it's the best on HTC's phones.
I checked the fix on post
HTML:
http://forum.xda-developers.com/showthread.php?t=302293&highlight=camera+software
but since my Artemis is being fixed (the touchscreen broke, but it was still on warranty), I cannot test it right now. I saw most people said it is a great fix, but I'm still not sure if it's gonna solve what I think of it.
I'm up to try to program a JavaME software for the camera, IF someone wants to help me with it AND knows how to do it.
Also, if anyone wants to give a hand, again, I'm willing to start to compile all the programs and fixes for the camera on a single thread.
What do ya all think? Wanna go for it?
Let's make Artemis's camera worth being called a 2mp camera!

aospGBMod v0.1.2 | AOSP 2.3.1 (Gingerbread) lounge for talking about this ROM

Since the other thread seems to be getting off topic, what topic? Im not sure since there is no development collaboration in the topic...I have created this thread for us to talk about whatever we want (pertaining to this ROM) SO go ahead and cry and whine all you want here, because afterall, thats the topic.
(MOD> PLEASE MOVE THIS TOPIC TO THE CORRECT FORUM, by MISTAKE I ADDED IT HERE)
Thread moved to General.
I'm afraid to see this thread in a day or two.
Anyways, does anybody know where AOSP and his all-knowing powers stand with this? There's plenty of chatter about what version he's on and all, but does anybody know for sure what he has so far?
I say give it some time. It took a while for Froyo to be fully functional. I'm not too keen on rushing the progress.
But as for GB, it looks really neat. Has anybody got any benchmarks data on it and compared it to the latest Froyo release?
i almost got a 5 on linpack, jit enabled. if u enable jit in gb though ive found video playback is screwey and dont work all the time. or maybe thats just the rom itself cause ive been having video playback problems with jit off to
mdhscanes24 said:
Anyways, does anybody know where AOSP and his all-knowing powers stand with this? There's plenty of chatter about what version he's on and all, but does anybody know for sure what he has so far?
Click to expand...
Click to collapse
Haven't been following the IRC. I don't much like the web based one. I follow 3 from Trillian, but I can't access the one he uses (only tried twice).
I do have hunches as to the slience. A lot of things have changed recently I think he might be working out.
-Root issues - being wiped out because of binary update
-ClockworkMOD - change to 3.0.0.2 supporting the new image methods
-gmail - critical to some, he's probably working on this over..
-camera. not critical to next update, but long run would be nice to have working, even to aosp i'm sure.
oohaylima said:
I say give it some time. It took a while for Froyo to be fully functional. I'm not too keen on rushing the progress.
But as for GB, it looks really neat. Has anybody got any benchmarks data on it and compared it to the latest Froyo release?
Click to expand...
Click to collapse
Rest assured I'm not looking to try and rush things. Hell, it's my daily as is.

Wonk Fix Donations

I thought I would post a thread listing the Paypal address for those who would like to donate to the developer who helped bring about a fix for the dreaded wonk.
I think this guy deserves a couple bucks thrown his way by most of us who use and enjoy ASOP based firmwares.
The last couple of cyanogenmod nightlies have had ZERO wonk.
Lets keep in mind that this issue was starred with Google a couple of times and we couldnt get Google to even recognize that a problem exists!
The problem was so bad that cyanogen was releasing roms marked as stable that still had the wonk because it was an ASOP bug...
Anyway, send this dude a couple of bucks if you can. All of us running a N1 with ASOP based firmwares are benefiting from the wonk fix.
His paypal address is: [email protected]
Thanks!
-Dweebs
Ok, I just sent the guy $10 USD. Its not much but every little bit helps.
Umm what?
Google acknowledged the issue and even fixed it, which is probably why it is working in CM roms now.
GldRush98 said:
Umm what?
Google acknowledged the issue and even fixed it, which is probably why it is working in CM roms now.
Click to expand...
Click to collapse
Dunno if the email is the right guy, but it was fixed independently of asop.
Two different forms of wonk ..
One is the call delay bug
The other is the black screen bug
I "think" he found the issue for the call delay
Not sure about status of black screen bug
Google said the delay bug was not across all devices and only specific to Nexus so they closed the report. Last time i heard about it
Again i might have my bugs mixed up but ehhh
http://forum.xda-developers.com/showthread.php?t=1080147
This is the thread where you can see the results of the guys work. All I know for sure is that for several iterations of Cyanogenmod there was a "call delay". People would call me and not be able to hear me for several seconds. Very annoying bug. I resorted to using a CM Froyo build for a while and then a rooted OTA build of Gingerbread. It was acknowledged as an ASOP bug but wasnt present in the OTA builds of Gingerbread. This guy took the time and tracked the issue down and repaired it with a simple patch.
@Devastatin: The email is the right developer if you follow the above link you can see the name of the guy who I contacted via PM.
@GldRush98: You may have never seen this bug because I remember you commenting in a thread where you stated you only used OTA builds and not "janky custom builds like Cyanogenmod" which I am sure ruffled a few feathers.
But regardless it was a very real problem and there were a couple of threads in which people were asked to "star the issue" on Google forums. The first starred thread was closed, Google said it was hardware specific on the N1 and didnt address it. I dont know what happened with the second thread.
If you guys dont want to donate to the guy, nobody is forcing you. I just felt like the guy deserved some props for fixing an issue that noone else was addressing.
-D
I'm not actively soliciting donations, but if anyone wants to donate to me, I appreciate it. I just thought I'd post here to confirm my identity.
My changes to cyanogenmod are listed here:
http://review.cyanogenmod.com/#dashboard,1030
The a1026 suspend commit deals with the wonk, the call delay commit is obvious. If you click any of the commits, you'll see my email address there, as well.
jyxent said:
I'm not actively soliciting donations, but if anyone wants to donate to me, I appreciate it. I just thought I'd post here to confirm my identity.
My changes to cyanogenmod are listed here:
http://review.cyanogenmod.com/#dashboard,1030
The a1026 suspend commit deals with the wonk, the call delay commit is obvious. If you click any of the commits, you'll see my email address there, as well.
Click to expand...
Click to collapse
The other fixes were for a CM related issue due to merging of 2.3.3 with 2.3.4 which broke receiving MMS from certain other phones. All bugs were a major source of complaints on both the xda nightly thread (along with Fitsnugly's Gigglebread build) and the CM nightly thread with who knows how many countless other threads in both forums.
And AFAIK, google has not fixed the call-delay bug (the wonk didn't exist on the stock ROM) from everything I have read. It still existed on various 2.3.4 builds that I tested.
jyxent fixed some of the major bugs that were plauging N1 users (and who knows how much sleep cyanogen lost due to the wonk). If I can come up with some money on this next paycheck, he will be getting some... Until then, I will just sing his praises
Gonna give this thread a final bump in the hope that the N1 users out there will show this guy some love.
I realize fixing broken code and releasing it to the community is in the spirit of open source software but every once in a while I like to give credit where credit is due. My N1 is perfect (again)!!
I'm on CM7.0.3 and am still having to use dewonkificator because of phone delays. Is this for real or is someone trying to get some free $$?
Estimated Prophet Hawk said:
I'm on CM7.0.3 and am still having to use dewonkificator because of phone delays. Is this for real or is someone trying to get some free $$?
Click to expand...
Click to collapse
It's for real, and also seems to have side effect of greatly increasing battery life as well. Bit the fix is only in the nightlies which is why you don't have it.
You could apply the fix to the stable firmware. The dewonkificator was just a band-aid as this actually corrects the bug.
And the guys not trying to make any money off the code, it's freely available. I just think he deserves a few bucks for fixing a huge problem with our phones.
Sent from my Nexus One using XDA App
I believe that this was truly fixed for most devices and the developer who solved it deserves the credit for it, but I'm sorry to say that I'm also still experiencing that call delay occasionally on my N1 running CM 7.0.3...
Edit: just after posting I saw the comment that this is only available on the nightly builds... thought this was already included in 7.0.3. Anyone has a clue on when it will be included on the stable versions ?
I would think it would be included in 7.1 (or the next stable release (candidate) but I'm most likely wrong.
Oh, and the call delay exists in stock OTA builds. My husband has an N1 that is completely stock and not rooted, He has the call delay bug.
I didn't write that. Prove it!!!
this patch can be applied to another ROM like stock GB 2.3.4?
I'll wait for the next stable CM
If the next stable CM has fixed the call delay, wonk, and has better battery life you can be sure I'll be sending out some donations! I flamed on the google thread about this issue; it was clearly an AOSP bug because I experienced it on CM *and* vanilla AOSP. I'm looking forward to the upgrade back to gingerbread but until CM drops another stable I'll be rocking Froyo
This problem is completely fixed in the latest nightly builds. You can apply the fix to the 7.03 build by pushing over the fixed libaudio.so file. Step by step directions are available here if you are uncomfortable using adb, search the forum. I attached the corrected file to this post. The fix was made by jyxent and he deserves the credit for fixing this problem.
Just so everyone is clear...the call delay bug is not just AOSP. I had it right from the get go in OTA 2.3.3 and it continued to 2.3.4. I am now using an AOSP build and don't have it . I may have the MMS bug though as I can't receive certain MMS pics from certain phones/carriers. Have not narrowed down the exact issue yet.
Estimated Prophet Hawk said:
I'm on CM7.0.3 and am still having to use dewonkificator because of phone delays. Is this for real or is someone trying to get some free $$?
Click to expand...
Click to collapse
CM7.0.3 is ancient compare to the latest nightly.

[Q] Recommendations for a ROM ICS or JB

I'm currently running Toasted Marshmallow but the camera issue is killing me. Is there a daily driver out there with a working camera? I don't really care if it is ICS or JB I just need my camera/instagram to work again. I'm also hoping I can retain my apps/data as I have been running this for a bit. I did a search and could nothing definitive. If I overlooked something please let me know. Thanks for any help!
Synthetic AospX. Also, we have plenty of threads on this so you should have looked before you posted
I did a search. This was the most relevant thing and it was posted in July. Just sayin' Anyway thanks for the heads up.
Even if there is nothing titles "best ics roms", you could have just looked at the rom threads and found which ones had rave reviews. Most of the ICS and JB roms are at the top. I am not mad at you, slightly annoyed, i just want to tell you what to do for next time.
These are the threads I cannot f*cking stand. Test out the ROMs if you want to know which one is best for you! We don't know what you like. You do. So don't be that noob that asks all the questions in the general forum (like you did) and post ROM related problems as new threads.
Also, what's this? On the 2nd page?! No way someone would dare look there.. http://forum.xda-developers.com/showthread.php?t=1494680
Have a nice day.
Sent from my HTC One S running ViperOneS!
jennster said:
I'm currently running Toasted Marshmallow but the camera issue is killing me. Is there a daily driver out there with a working camera? I don't really care if it is ICS or JB I just need my camera/instagram to work again. I'm also hoping I can retain my apps/data as I have been running this for a bit. I did a search and could nothing definitive. If I overlooked something please let me know. Thanks for any help!
Click to expand...
Click to collapse
What is searching? Searching is definitely NOT looking something up on Google and skimming through everything. Searching CANNOT be done with shortcuts.
Now if you had really done a full search, you would've found that like you said, there is nothing "definitive", or good out there. So what does that mean..? If you don't find it out there, it probably means it doesn't exist. Like in this case right here, a great example. I, like Invasion2 hate threads like these because nobody knows what's the best for your phone, nobody knows your taste. Only you do. Sure, we can give you suggestions and stuff, but why don't you just save everyone's time and try the ROMs yourself? Does it really take that long and that much effort? It doesn't hurt to try.
You should honestly be thankful that we even have ICS and JB ROMs...HTC and T-Mobile left us on the Gingerbread side. And here you are complaining about things not working. Well no duh...you can't expect a OS that wasn't meant to be on our phone to work 100% do you? Cause if you do, then you set impossible expectations for developers.
Another thing: have you ever thought about how much effort, time, and energy were put into the development of these ROMs? Developers work hard, spend countless hours, sometimes giving up sleep to get something to just boot, and the last thing we want to hear and read in our threads is someone who thinks he deserves the work we put out to complain about this or that not working. We know it's not working, we don't need you to tell us that! Trust us, we're working hard on trying to figure out the bugs and fix them, it's not easy.
Lastly...what's wrong with Gingerbread? It's working perfectly fine for our phone. If you want to have everything "perfect and working" why not stay with Gingerbread, where everything is guaranteed to work? I'm on MIUI GB, and can't love it more. If you just want the look of ICS or JB, it's not that hard to theme Cyanogenmod 7 to look like them. And if you want to be on ICS or JB just cause it's cooler or whatever, well be prepared to sacrifice somethings, like the camera. Gingerbread is a OS that was meant to be on our device, ICS and JB weren't.
Thanks.
invasion2 said:
These are the threads I cannot f*cking stand. Test out the ROMs if you want to know which one is best for you! We don't know what you like. You do. So don't be that noob that asks all the questions in the general forum (like you did) and post ROM related problems as new threads.
Also, what's this? On the 2nd page?! No way someone would dare look there.. http://forum.xda-developers.com/showthread.php?t=1494680
Have a nice day.
Sent from my HTC One S running ViperOneS!
Click to expand...
Click to collapse
MFW I saw this post.
Also, TL: DR.
Oh FFS
I didn't ask what was the BEST. That would be opinion and I am certainly not soliciting that. I could read all day and get a million. I asked what had a WORKING CAMERA. Seems like an easy enough question for such well versed people. That being said that renders the link you so condescendingly offered completely irrelevant. So that you know the query was here on XDA for working camera mytouch4G. I wasn't complaining. I said, for my needs I need a working camera. Did I post this on the ROMs thread? No. I didn't. I was looking for a suggestion that would meet my needs, i.e. a working camera.
What happened to people on forums being decent and helpful if not nice too?
You know what I can't stand? A$$holes like you people that think that any of this makes a $hit in the big picture. You know what *I* hate? Taking care of my dad with Parkinsons and my mother that can't leave the house because she has COPD all while working two jobs. Really next to that an extraneous thread doesn't seem that bad. "$hit I have to scroll over this thread that someone who actually looked posted!"
A lot of people work hard. Some not in front of computers in the air conditioning. I appreciate that this stuff is available but please do not hang yourself on a cross. If you hate it, find work elsewhere. If you don't get out of my a$$. I'm not going to suck your d1ck either way and I doubt anyone else is either with your sunny disposition.
And good evening.
jennster said:
Oh FFS
I didn't ask what was the BEST. That would be opinion and I am certainly not soliciting that. I could read all day and get a million. I asked what had a WORKING CAMERA. Seems like an easy enough question for such well versed people. That being said that renders the link you so condescendingly offered completely irrelevant. So that you know the query was here on XDA for working camera mytouch4G. I wasn't complaining. I said, for my needs I need a working camera. Did I post this on the ROMs thread? No. I didn't. I was looking for a suggestion that would meet my needs, i.e. a working camera.
What happened to people on forums being decent and helpful if not nice too?
You know what I can't stand? A$$holes like you people that think that any of this makes a $hit in the big picture. You know what *I* hate? Taking care of my dad with Parkinsons and my mother that can't leave the house because she has COPD all while working two jobs. Really next to that an extraneous thread doesn't seem that bad. "$hit I have to scroll over this thread that someone who actually looked posted!"
A lot of people work hard. Some not in front of computers in the air conditioning. I appreciate that this stuff is available but please do not hang yourself on a cross. If you hate it, find work elsewhere. If you don't get out of my a$$. I'm not going to suck your d1ck either way and I doubt anyone else is either with your sunny disposition.
And good evening.
Click to expand...
Click to collapse
I thought you'd searched around already? And since you already searched, you should've known that there wasn't a fully working camera yet. So why are you still asking this question if you know the answer already? Seriously...
You don't expect people to be nice if you rub them the wrong way do you? It's sorta your fault we're "not nice" to you...you should check out the other forums when noobs post questions like this, oh man...sh*t breaks apart the fan.
Did you guys actually read his OP ,it wasnt really that bad.He did say he searched ,granted he could of tried a bit harder,but help a guy out once in a while!I am not knockin anybody but ,not everyone knows there way around these threads like some of us do..I mean if he was being a lazy dumb ass that one thing ,but he didnt come off like that to me when i read his OP
anyways. search harder next time dude and you wont get flamed!!!
jennster said:
I'm currently running Toasted Marshmallow but the camera issue is killing me. Is there a daily driver out there with a working camera? I don't really care if it is ICS or JB I just need my camera/instagram to work again. I'm also hoping I can retain my apps/data as I have been running this for a bit. I did a search and could nothing definitive. If I overlooked something please let me know. Thanks for any help!
Click to expand...
Click to collapse
I don't get why you're getting so much flac. It's not like the MT4G is flying. Most threads about ROMs are months old.
The only answer I seem to see too is Synthetic's ROM.
"If you don't have anything nice to say don't say anything at all"
I also didn't feel as if the op was a lazy dumb ass. To each his own
Sent from my MyTouch 4G using xda app-developers app
---------- Post added at 04:45 PM ---------- Previous post was at 04:42 PM ----------
Deathwish238 said:
I don't get why you're getting so much flac. It's not like the MT4G is flying. Most threads about ROMs are months old.
The only answer I seem to see too is Synthetic's ROM.
Click to expand...
Click to collapse
Sorry to double post but I don't agree with this. Most roms are NOT months old and are updated. Granted some old ones aren't but for an old phone we hold our ground
Sent from my MyTouch 4G using xda app-developers app
rockstarar said:
Sorry to double post but I don't agree with this. Most roms are NOT months old and are updated. Granted some old ones aren't but for an old phone we hold our ground
Sent from my MyTouch 4G using xda app-developers app
Click to expand...
Click to collapse
Yeah. Ignore the troll. Development for this ancient phone that was only released on one continent is still moving nicely.
Sent from my myTouch 4g using xda app-developers app
Synthetic's AospX for sure. Very smooth and I use it as my daily driver.
I really, really hate people who just want to flame someone for asking a question, especially like this. Me, myself, I'VE been searching for a perfect rom for myself, and it's a PAIN to spend countless of hours when you are not experienced in messing with the phones, and you asking a simple question, than all these teenie boppers decide to start a flame war thinking they are the all-knowing, just because they design some ROMs and ports.
Now, personally the best ROM I have found so far that suits me is the CoreDroid ROM.
http://forum.xda-developers.com/showthread.php?t=1434887
This seems to be the most stable ROM with best battery life that I have found after using many that keeps the original android feel to it. I have yet to find any real problems with it, seems to be the perfect one for me.
I'm currently going through most of the ROMs trying to find something else, instead of just upgrading my phone. I've tested out PacMan Glacier ROM, and honestly I'm liking that the most so far.
http://forum.xda-developers.com/showthread.php?t=1933896
But again, problem is Camera freezing, panoramic does not work either, at least for me, may work for you. I'd look into that first to see how you like it. Has extensive customization options as well, so the settings screen is a little cluttered so to speak, but good for customization. I would REALLY LOVE to get this to work perfectly, cuz I will indefinitely use this (haven't tested out battery life though).
The next one from that I would check out (even though Saranhai is the one who pretty much crapped on you first) is MyTouchUX.
http://forum.xda-developers.com/showthread.php?t=1826792
I would love to post what problems I've encountered in the thread, but I need to post at least 10 times or something or another before I can post in those forums. But anyways, problem I've had was that the Camera button does not work to get the camera on (but still can access the camera through the app itself), and the LockScreen still is not working in V3, at least for me. BUT panoramic does work with his, and it is really sweet. Less customization options on this ROM, but seems to be REALLY clean (couldn't get swype either, might just be me though.)
Ardanza said:
I really, really hate people who just want to flame someone for asking a question, especially like this. Me, myself, I'VE been searching for a perfect rom for myself, and it's a PAIN to spend countless of hours when you are not experienced in messing with the phones, and you asking a simple question, than all these teenie boppers decide to start a flame war thinking they are the all-knowing, just because they design some ROMs and ports.
Now, personally the best ROM I have found so far that suits me is the CoreDroid ROM.
http://forum.xda-developers.com/showthread.php?t=1434887
This seems to be the most stable ROM with best battery life that I have found after using many that keeps the original android feel to it. I have yet to find any real problems with it, seems to be the perfect one for me.
I'm currently going through most of the ROMs trying to find something else, instead of just upgrading my phone. I've tested out PacMan Glacier ROM, and honestly I'm liking that the most so far.
http://forum.xda-developers.com/showthread.php?t=1933896
But again, problem is Camera freezing, panoramic does not work either, at least for me, may work for you. I'd look into that first to see how you like it. Has extensive customization options as well, so the settings screen is a little cluttered so to speak, but good for customization. I would REALLY LOVE to get this to work perfectly, cuz I will indefinitely use this (haven't tested out battery life though).
The next one from that I would check out (even though Saranhai is the one who pretty much crapped on you first) is MyTouchUX.
http://forum.xda-developers.com/showthread.php?t=1826792
I would love to post what problems I've encountered in the thread, but I need to post at least 10 times or something or another before I can post in those forums. But anyways, problem I've had was that the Camera button does not work to get the camera on (but still can access the camera through the app itself), and the LockScreen still is not working in V3, at least for me. BUT panoramic does work with his, and it is really sweet. Less customization options on this ROM, but seems to be REALLY clean (couldn't get swype either, might just be me though.)
Click to expand...
Click to collapse
Have you noticed when the op last posted? Appreciate the efforts though
THEindian said:
Have you noticed when the op last posted? Appreciate the efforts though
Click to expand...
Click to collapse
Bah, no I didn't even notice that... oh well...

https://jira.cyanogenmod.org - Really uncool behavior(WARNING)

So in the past I've mention that OnePlus One had issues if you try to charge it while it's turned off, the charging led(red) isn't on and I went here to tell my story:
https://forum.cyanogenmod.org/topic/114705-oneplus-one-charge-when-turned-off-charging-and-led/
Well not much people got interested in this so I still persuit this and open a case in the "famous" jira cyanogenmod reporting system and open this thread:
https://jira.cyanogenmod.org/browse/BACON-4187
So even since CM12.1 this issue exist and maybe from previous android versions, now I saw today that it's been solved, so I update my phone to the latest official "cm-13.1-ZNH2KAS1KN" and check it out ...guess what, no resolve so I tried to post on JIRA Cyanogenmod that the ZNH2KAS1KN still has the issue
When I figure out that the "RESOLVED" from "Pat Erley" which was assigned to fix it was to make my account "inactive" - great resolve
P.S. When I open this issue one of the cyanogen guys told me "I can't add votes and I'm not going to advertise the issue (and I would rather you not either). The activity would have been me assigning the issue"
He didn't want to "advertise" the issue, why? ...why he wanted this to be quiet? (this is visible from the jira cyanogenmod link I've mention in the second link
P.S.2 Share this to as many OnePlus One users possible, cyanogenmod jira is useless(and they mute you if they don't like what you are saying)
evronetwork said:
So in the past I've mention that OnePlus One had issues if you try to charge it while it's turned off, the charging led(red) isn't on and I went here to tell my story:
https://forum.cyanogenmod.org/topic/114705-oneplus-one-charge-when-turned-off-charging-and-led/
Well not much people got interested in this so I still persuit this and open a case in the "famous" jira cyanogenmod reporting system and open this thread:
https://jira.cyanogenmod.org/browse/BACON-4187
So even since CM12.1 this issue exist and maybe from previous android versions, now I saw today that it's been solved, so I update my phone to the latest official "cm-13.1-ZNH2KAS1KN" and check it out ...guess what, no resolve so I tried to post on JIRA Cyanogenmod that the ZNH2KAS1KN still has the issue
When I figure out that the "RESOLVED" from "Pat Erley" which was assigned to fix it was to make my account "inactive" - great resolve [emoji14]
P.S. When I open this issue one of the cyanogen guys told me "I can't add votes and I'm not going to advertise the issue (and I would rather you not either). The activity would have been me assigning the issue"
He didn't want to "advertise" the issue, why? ...why he wanted this to be quiet? (this is visible from the jira cyanogenmod link I've mention in the second link
P.S.2 Share this to as many OnePlus One users possible, cyanogenmod jira is useless(and they mute you if they don't like what you are saying)
Click to expand...
Click to collapse
The build released in July when he closed the issue ticket is ZNH2KAS254. Check by flashing that build first if it's actually fixed. I don't personally ever charge with screen off and I'm on Omni right now so can't confirm for you at the moment.
Renosh said:
The build released in July when he closed the issue ticket is ZNH2KAS254. Check by flashing that build first if it's actually fixed. I don't personally ever charge with screen off and I'm on Omni right now so can't confirm for you at the moment.
Click to expand...
Click to collapse
Flashed ZNH2KAS254 (same issue) also the newer fix ZNH2KAS2X1 (same issue )
Did the flashes but forgot to update it here ...the issue exist and never beeing fixed since CM12.1(or maybe earlier I'm not sure when this started but it was there since CM12.1 for sure)
P.S. In omni as in CyanogenMOD the charging experiance while turned off is even worse, in Cyanogen you don't have red led lit but the screen has a BIG battery, the CM, omni etc etc have a tiny tiny small white battery that reminds me of the year 2000 ...also no red led lit(same issue)
I'm using the cm nightlies and it lights up fine when charging while powered off. No percent number but the light is there. I stopped using the official software months ago because of bluetooth spotify audio stuttering which also no one cared about to fix. Nightlies are running fine but without gimmicks like slow shutter and raw (but slow motion is there)
evronetwork said:
So in the past I've mention that OnePlus One had issues if you try to charge it while it's turned off, the charging led(red) isn't on and I went here to tell my story:
https://forum.cyanogenmod.org/topic/114705-oneplus-one-charge-when-turned-off-charging-and-led/
Well not much people got interested in this so I still persuit this and open a case in the "famous" jira cyanogenmod reporting system and open this thread:
https://jira.cyanogenmod.org/browse/BACON-4187
So even since CM12.1 this issue exist and maybe from previous android versions, now I saw today that it's been solved, so I update my phone to the latest official "cm-13.1-ZNH2KAS1KN" and check it out ...guess what, no resolve so I tried to post on JIRA Cyanogenmod that the ZNH2KAS1KN still has the issue
When I figure out that the "RESOLVED" from "Pat Erley" which was assigned to fix it was to make my account "inactive" - great resolve [emoji14]
P.S. When I open this issue one of the cyanogen guys told me "I can't add votes and I'm not going to advertise the issue (and I would rather you not either). The activity would have been me assigning the issue"
He didn't want to "advertise" the issue, why? ...why he wanted this to be quiet? (this is visible from the jira cyanogenmod link I've mention in the second link
P.S.2 Share this to as many OnePlus One users possible, cyanogenmod jira is useless(and they mute you if they don't like what you are saying)
Click to expand...
Click to collapse
Try latest nightly, charging led is Woking in or while powered off.
Sent from my A0001 using Tapatalk
Abhinav_Rakesh said:
Try latest nightly, charging led is Woking in or while powered off.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Currently on COS13.1.1 ..and issue the report based on COS not CM(had CM in the past but there still was this issue while the phone was turned off - didn't check CM for a while as I'm on COS since COS13)
It's unacceptable the official rom for this device to have a broken rom, charging led works if the phone is on but that's a different matter
evronetwork said:
Currently on COS13.1.1 ..and issue the report based on COS not CM(had CM in the past but there still was this issue while the phone was turned off - didn't check CM for a while as I'm on COS since COS13)
It's unacceptable the official rom for this device to have a broken rom, charging led works if the phone is on but that's a different matter
Click to expand...
Click to collapse
You do realize CM Nightlies are months ahead development wise than COS. It'll get to official COS after some months so just have to be patient. I checked and it works on latest nightlies as the other user mentioned
Renosh said:
You do realize CM Nightlies are months ahead development wise than COS. It'll get to official COS after some months so just have to be patient. I checked and it works on latest nightlies as the other user mentioned
Click to expand...
Click to collapse
You do realise that I reported this since COS12 right?
Do you understand, your problems been fixed, just flash a damn nightly. No one at Cyanogen is gonna apologize to you or say you were wronged. Get over it and flash a damn nightly.
xdiable said:
Do you understand, your problems been fixed, just flash a damn nightly. No one at Cyanogen is gonna apologize to you or say you were wronged. Get over it and flash a damn nightly.
Click to expand...
Click to collapse
Problem not fix with the OFFICIAL rom, I really don't care about nightlies or made by papajohn ReMixERrSZzz or whoever, currently I don't feel like playing with roms, I do have a simple root in my COS(look what I wrote, CyanogenOS aka Cyanogen)
P.S. Try to be more polite, everyone can talk badly without even trying - It's unacceptable the official rom to have such a huge bug since COS12(or maybe even before that while I've mention it)
evronetwork said:
Problem not fix with the OFFICIAL rom, I really don't care about nightlies or made by papajohn ReMixERrSZzz or whoever, currently I don't feel like playing with roms, I do have a simple root in my COS(look what I wrote, CyanogenOS aka Cyanogen)
P.S. Try to be more polite, everyone can talk badly without even trying - It's unacceptable the official rom to have such a huge bug since COS12(or maybe even before that while I've mention it)
Click to expand...
Click to collapse
Official Nightlies are the same code made by the same guys who make the stock OS, COS just has some closed source apps and comes bundled with gapps. Can't wait to see your dumb comments when you realize you'll never get Nougat COS update but people using CM Nightlies will
evronetwork said:
Problem not fix with the OFFICIAL rom, I really don't care about nightlies or made by papajohn ReMixERrSZzz or whoever, currently I don't feel like playing with roms, I do have a simple root in my COS(look what I wrote, CyanogenOS aka Cyanogen)
P.S. Try to be more polite, everyone can talk badly without even trying - It's unacceptable the official rom to have such a huge bug since COS12(or maybe even before that while I've mention it)
Click to expand...
Click to collapse
Why don't u just charge with the device turned on? Airplane mode on and plug in charger there you go. I wouldn't be happy to wait for a boot every morning.

Categories

Resources