Related
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.
I posted this on Oneplus forums but XDA is well... XDA So I wanted to post here too. I'm getting random reboots on the OPT. I just got the phone yesterday and it rebooted randomly 3x while I was on the phone and one time when I put the phone in my pocket. That is 4 random reboots in less than 24hrs.
Anyone experiencing this?
No problem here. Did you try reflashing the OS?
gads83 said:
No problem here. Did you try reflashing the OS?
Click to expand...
Click to collapse
Honestly that never even crossed my mind but that is a good idea. Ironically if this was happening with CM that would've been my first thought lol. I'll try and report back.
Be interested in how you go.
No problem here. Just reflash the complete stock 2.0.2 using TWRP > http://www.technobuzz.net/install-oxygenos-2-0-2-update-on-oneplus-2-android/
I have the same issue, and I have tried to re-flash stock 2.0.2 which didn't solve anything. I wiped everything but storage (can't remember the name, but data was flashed, just not.. storage.)
I issued a ticket to OnePlus who responded tonight that they are working on an update that will resolve this. Not sure that I believe them, but if it solves the problem I'm happy. If not, I'll have to go through RMA-circus and get it replaced.
Could anyone give me a hint as to if and how it would be possible to log random reboots? I have no idea but is there a general core-dump file or something along those lines in android?
Also, OP or TS, did you solve your problems with a re-flash?
To be honest this isn't the first time I've had this issue. I had the same issue with CM on the Oneplus One. Only difference there is that was a nightly. I have no idea why it was happening. I just pushed the OPT off to the side till OxygenOS 2.1 comes out. I'm in Note 5 world now.
I've spoken to OnePlus and they "helped" me with a total reset of the device, but it didn't help so RMA is coming up for me.
2.1 didn't solve it either...
Sent from my ONE A2003 using Tapatalk
Same here.
Reflashed to 2.0.2 and 2.1, totally wiped several times without results, phone is still randomly rebooting (10 - 15 times per day).
Only when in charge the phones not reboot .......
May be the issue is related to the power HW section....
Ticket opened..... .
Which batch is your phone from? Mine is late August iirc.
Sent from my ONE A2003 using Tapatalk
where I can find the batch?
i've got the same problem!!
On 2.0.3 i get sometimes to 4-5 reboots per hour!
2.1 seems more stable on the other hand but still around 2-3 reboots per day is not normal!
production date: 9/11/15
You find the batch on the back of the box the phone came in. Might be another way for it but I don't know.
Sent from my ONE A2003 using Tapatalk
ok found it!!!
2015.09.01
I made a ticket also. I hope they can fix my device
Ok, seems like we can rule out batch. Mine is 2015-08-05, so three different dates on three different persons.
Hopefully the RMA will be quick.
Try to flash the full 2.1 ROM
https://www.androidfilehost.com/?w=file-thanks&fid=24052804347820894&mid=96&download_id=r2rjvacl2lqvjok4sev0ddr347&tid=1443110768&hc=7df587a53335120b686fba548b0c9586b07b05c03f6aecd7a11ced494e1b2911
dgardel said:
Try to flash the full 2.1 ROM
https://www.androidfilehost.com/?w=...fba548b0c9586b07b05c03f6aecd7a11ced494e1b2911
Click to expand...
Click to collapse
I'll try that if RMA bums out. They (OnePlus) flashed 2.0.2 through qc-thingie, and it rebooted shortly after that.
Sent from my ONE A2003 using Tapatalk
may be this is my 3rd and last OP phone and my LAST phone where I cannot have an assistance centre far maximum 15 km (10 miles apron.) from my house!!!!!
Live chat "helped" me doing a factory reset. LOL
Well nothing is working for me
Now i have to wait for my ticket so i can return this awfull device
Hey,
I bought my Moto X Play from Flipkart on November 3rd.
Its 4 days and I haven't experienced any connectivity issues or battery issues.
But half an hour ago, it got rebooted automatically twice.
May I know if there is any fix for this....?
Was it on wifi?
fingerprinted said:
Was it on wifi?
Click to expand...
Click to collapse
Yeah. It was on WiFi, and happened 3 more times after I posted this thread...
nikhilsuresh7 said:
Yeah. It was on WiFi, and happened 3 more times after I posted this thread...
Click to expand...
Click to collapse
It happened to me well, on my old router, the frequency wasn't supported. Random reboots occurred. It was annoying since after each reboot, every app had to optimize again each time. Changed router, or you may tweak your existing one to support the needed frequency. Hasn't happened since. Google wifi causing random reboots android. It may not be the same problem as me, but worth a look
nikhilsuresh7 said:
Hey,
I bought my Moto X Play from Flipkart on November 3rd.
Its 4 days and I haven't experienced any connectivity issues or battery issues.
But half an hour ago, it got rebooted automatically twice.
May I know if there is any fix for this....?
Click to expand...
Click to collapse
I too hit the same issue from past month, when I updated my device.
Please help with fix/resolution.
firoz_nv said:
I too hit the same issue from past month, when I updated my device.
Please help with fix/resolution.
Click to expand...
Click to collapse
Bought my device on Nov 7 and till now no issues.
Sent from my XT1562 using Tapatalk
firoz_nv said:
I too hit the same issue from past month, when I updated my device.
Please help with fix/resolution.
Click to expand...
Click to collapse
wipe it.
nikhilsuresh7 said:
Hey,
I bought my Moto X Play from Flipkart on November 3rd.
Its 4 days and I haven't experienced any connectivity issues or battery issues.
But half an hour ago, it got rebooted automatically twice.
May I know if there is any fix for this....?
Click to expand...
Click to collapse
Do a factory reset. Motorola also advice to do a factory reset on all new devices,because of a bug. When I bought it new I got the problem that moto display didn't worked and only showed a black screen when picking up the phone. After the reset all problems solved.
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.
UPDATED:
released.
ROM thread
so, I've built a buggy cm14 that's good enough to look at and play a little with the features that do work, and watch the eye candy and all.
it has wifi and bluetooth and SMS messaging.
Otherwise broken telephony.
only some of the sound works. no camera, nfc, location.
the idea is a poll.
I figure people like to click buttons, so the poll suits that.
I'm amazed at your skills. And I have learned a lot from reading this thread. More importantly, my VM 816 is still functional.
Sent from my 710C using Tapatalk
I think you can release it whatever people use or not , but 816 is my only 4G phone.I will test it till the Calling Services worked
Ed128 said:
I'm amazed at your skills. And I have learned a lot from reading this thread. More importantly, my VM 816 is still functional.
Sent from my 710C using Tapatalk
Click to expand...
Click to collapse
A lot of what I do is googling errors, borrowing commits from other cm devices with similar chipsets, (and commenting out lines that throw errors in the build until I figure out workarounds... not the most kosher of methods.)
It's fun, but I often lean heavily on stuff that's already been done by others. Grarak put up really nice device trees to work from on this device for example, and my first tweaks at it were just after it had faded from cm nightlies. Made it comparatively easy next to my Optimus or Evo3d.
frank9184 said:
I think you can release it whatever people use or not , but 816 is my only 4G phone.I will test it till the Calling Services worked
Click to expand...
Click to collapse
Odds are the basic call services will be online way before 4G. Especially since my 4G service is still broken and has ben for quite a while. I'll hassle Virgin Mobile about a replacement sim card soon; research and talking with a Ting rep both imply that would fix my issue.
bigsupersquid said:
so, I've built a buggy cm14 that's good enough to look at and play a little with the features that do work, and watch the eye candy and all.
it has wifi and bluetooth, possibly nfc, probably no location, totally broken telephony.
only some of the sound works. no camera.
the idea is a poll.
I figure people like to click buttons, so the poll suits that.
Read this post and you see that clicking the thanks button counts more than voting...
Click to expand...
Click to collapse
I think you should upload the zip. Legacy devices are getting cm 14. Why we are late?
Tim Cook said:
I think you should upload the zip. Legacy devices are getting cm 14. Why we are late?
Click to expand...
Click to collapse
Well, htc certainly won't be releasing N for my a5_chl (Virgin Mobile variant) since they wouldn't even let M out the door for it.
you can partly name lack of manufacturer support.
And I get tired of complaints about nonworking items from people who don't read the OP, so I'm waiting for adequate interest to post it (big upload on poor isp, couple hours.)
Plus there's inability to test dug/dwg and that's twice the upload bandwidth. But few source changes to build for them, and some dual sim owners would enjoy buggy N too.
Several reasons that N isn't out in the wild yet for the a5. But I'll probably set it free to roam soon.
Question about CM14
When you let it roam, I'm ready to try it out. But I have two questions. First, I am delighted with CM13. It was the first time I ever flashed a phone and it is working nearly perfect. A hiccup or two but nothing I cannot handle. It has extended the useful life of my VM 816 A5 and saved me from buying another phone. Here's two questions for CM14 whenever it becomes available. Can I just backup my existing files with TWRP, Wipe and flash CM14? Then, the real question is if I don't like it, can I completely restore what I have now with RESTORE? The last thing I want is to ruin CM13. Thanks for helping this newby.
Ed128 said:
When you let it roam, I'm ready to try it out. But I have two questions. First, I am delighted with CM13. It was the first time I ever flashed a phone and it is working nearly perfect. A hiccup or two but nothing I cannot handle. It has extended the useful life of my VM 816 A5 and saved me from buying another phone. Here's two questions for CM14 whenever it becomes available. Can I just backup my existing files with TWRP, Wipe and flash CM14? Then, the real question is if I don't like it, can I completely restore what I have now with RESTORE? The last thing I want is to ruin CM13. Thanks for helping this newby.
Click to expand...
Click to collapse
yes, and yes. I restore cm13 over messed up cm14 regularly.
Still fighting with ril. location not working at all in spite of the switch working. and nfc probably will work once I get the firmware moved to wherever it's looking. but all the sound seems to be working now.
Ed128 said:
When you let it roam, I'm ready to try it out. But I have two questions. First, I am delighted with CM13. It was the first time I ever flashed a phone and it is working nearly perfect. A hiccup or two but nothing I cannot handle. It has extended the useful life of my VM 816 A5 and saved me from buying another phone. Here's two questions for CM14 whenever it becomes available. Can I just backup my existing files with TWRP, Wipe and flash CM14? Then, the real question is if I don't like it, can I completely restore what I have now with RESTORE? The last thing I want is to ruin CM13. Thanks for helping this newby.
Click to expand...
Click to collapse
Yes you can just Backup and Restore your previous ROM. Just be careful, wipe system and dalvik cache and cache. CM13 has some problems but mostly everything works on 816.
ajones23 said:
Yes you can just Backup and Restore your previous ROM. Just be careful, wipe system and dalvik cache and cache. CM13 has some problems but mostly everything works on 816.
Click to expand...
Click to collapse
ninja'd you this time.
I've been able to dirty flash 14 over 13, but previously installed apps get denied permissions and stuff like that.
bigsupersquid said:
ninja'd you this time.
I've been able to dirty flash 14 over 13, but previously installed apps get denied permissions and stuff like that.
Click to expand...
Click to collapse
Yup you got me, I usually don't dirty flash always clean flash. Since I use Root Essentials as partition of sdcard. When ever you get it to work,I'll be a tester. Let me know.
That's something I can deal with. Just don't want to go too far past my limited "expertise". And, not trying to hurry things. I'm a happy CM13 customer.
Sent from my 710C using Tapatalk
Ed128 said:
That's something I can deal with. Just don't want to go too far past my limited "expertise". And, not trying to hurry things. I'm a happy CM13 customer.
Click to expand...
Click to collapse
If you need help,just ask,I'm always on and off.
bigsupersquid said:
so, I've built a buggy cm14 that's good enough to look at and play a little with the features that do work, and watch the eye candy and all.
it has wifi and bluetooth, possibly nfc, probably no location, totally broken telephony.
only some of the sound works. no camera.
the idea is a poll.
I figure people like to click buttons, so the poll suits that.
Read this post and you see that clicking the thanks button counts more than voting...
Click to expand...
Click to collapse
Love your work!!!
D816w
what could be the estimated date for the first beta? hunger to flash this CM14.....
Naxym said:
what could be the estimated date for the first beta? hunger to flash this CM14.....
Click to expand...
Click to collapse
Its really not a good idea to ask for ETAs. Specially when not many things work.
Naxym said:
what could be the estimated date for the first beta? hunger to flash this CM14.....
Click to expand...
Click to collapse
ajones23 said:
Its really not a good idea to ask for ETAs. Specially when not many things work.
Click to expand...
Click to collapse
It's ok in this thread, since that's kind of what it's about.
If I can stabilize the radio glitches enough that all the telephony stops force-closing constantly I'll release an alpha, there isn't tons of interest but there seems to be enough.
After all, if I were in your shoes I'd want a release to check out.
bigsupersquid said:
It's ok in this thread, since that's kind of what it's about.
If I can stabilize the radio glitches enough that all the telephony stops force-closing constantly I'll release an alpha, there isn't tons of interest but there seems to be enough.
After all, if I were in your shoes I'd want a release to check out.
Click to expand...
Click to collapse
I sorta may get a flashing bug if you put up a alpha. I just thought I would put my 2 cents in about ETAs. Not a good thing sometimes.
ajones23 said:
I sorta may get a flashing bug if you put up a alpha. I just thought I would put my 2 cents in about ETAs. Not a good thing sometimes.
Click to expand...
Click to collapse
A lot of developers get uppity about ETAs.
I imagine with hot new devices and hundreds of posts a week it would get really old.
I usually just warn people that I have too much on my 'real-world' plate for my own taste and that my hobby work (this) ends up on the bottom of my get-er-done list.
Plus I like to put up it's-almost-ready posts and then take forever to upload:angel: and similar annoying delayed releases. Like I rebuilt for the OV a little while ago, posted about it, and never debugged or released it at all.
Bad dev :cyclops:
I put this thread out in general 816 to encourage comments and questions.
Once the alpha is out I'll open a thread in Original Dev (and post a link to it here) since cm14 is definitely original right now.
About to flash another test build!
Test has sms but no phone.
No Bluetooth.
Close to being uploadable.
assuming the next build isn't in any worse shape than this one (should have working BT, and I'm really hoping for at least 3g data and maybe phone service) then I'll try pushing the zip to AFH. If my landline internet stays connected long enough to get it upstream...