Related
So, here is my story.
I have tried Fresh 1.1, and I found that I was getting may too many reboots both on the phone and on Sense for my liking.
So I switched to Modaco 2, and have been very happy for a while...
I just had yet another reboot.
I was listening to some music, when I had a notification for an email. Looked at the email, tried to lock my phone, then tried to unlock, and that's when the music went off, and my phone rebooted itself....
I'm really getting tired of this. I have not loaded any new apps in the past 2 days. I have minimal apps anyway (Facebook, Weatherbug, Handcent, NPR News, Touchdown, Power Manager and Droidswap, that is it)
does anyone have any history of problems with Droidswap ?
I'm really getting frustrated. I hate when this happens, and I'm giving realy consideration into curtailing my brief incursion onto Android and returning back to the iphone....which is a real shame, as I f**king hate ATT
I would recommend taking your phone back to the store. I have not have had one unplanned reboot the entire time I've had my Hero (bought on release date Oct 9). I'm running Fresh 1.1 now, and had 1.0 previously. There is something seriously wrong with your phone.
I have no problem speaking for the entire android community when I say...
"its been nice knowing you, good luck with the iPhone and att"
Honestly...I have never had a full reboot on its own.
I have seen Sense close out and have to reload usually after I play an intensive game, racing or something like that with alot of graphics. I assume it just runs out of ram and does its thing to get resources back.
That's a rare occasion there's not much people that it has happened to from what I seen. Did u try to wipe your phone and cache & whatnot, do some of that and see what happens
(off topic)
Jdog stop trolling because u definitively don't speak for the Android community...
bronxknight28 said:
Jdog stop trolling because u definitively don't speak for the Android community...
Click to expand...
Click to collapse
I think I can speak for the whole Android community when I say. "Please don't go" - The more of us we have the better. Given, I completely understand frustration and disappointment.
bronxknight28 said:
That's a rare occasion there's not much people that it has happened to from what I seen. Did u try to wipe your phone and cache & whatnot, do some of that and see what happens
(off topic)
Jdog stop trolling because u definitively don't speak for the Android community...
Click to expand...
Click to collapse
Bronx,
Myself and many other members of this site and over at modaco's site have given advise on this issue. Griff insulted flipz and other devs in the fresh Rom thread, then went to modaco and started talking trash on the devs here.
Every post is about this reboot problem, that no one can seem to replicate.
I apologize for being rude but if someone doesn't take any of the advise given,then continues to clutter up the forums with new threads about the same thing it ticks me off...
Try TTG. It's made a world of difference for me.
thedudejdog said:
Every post is about this reboot problem, that no one can seem to replicate.
I apologize for being rude but if someone doesn't take any of the advise given,then continues to clutter up the forums with new threads about the same thing it ticks me off...
Click to expand...
Click to collapse
The advice he should be taking is to STOP LOADING APPS.
Out of the apps he has listed, I only use Facebook and Handcent SMS... so I'm willing to vouch for those two as not being the culprit. If he hasn't done a wipe and tried running with minimal apps, then the problem is his own fault.
some people just arn't made for android, and apple's buisness model is "you're too dumb to want to do that" actually applies to some people
EDIT: and there is nothing and I mean NOTHING in the world that gives me more of a nerd-boner than someone "rage-quitting" it puts a beautiful smell in the air... the smell of victory
thedudejdog said:
Bronx,
Myself and many other members of this site and over at modaco's site have given advise on this issue. Griff insulted flipz and other devs in the fresh Rom thread, then went to modaco and started talking trash on the devs here.
Every post is about this reboot problem, that no one can seem to replicate.
I apologize for being rude but if someone doesn't take any of the advise given,then continues to clutter up the forums with new threads about the same thing it ticks me off...
Click to expand...
Click to collapse
Erm, ex-****ing-scuse me, but can you PLEASE copy the link to the post where I insulted Flipz and started talking trash ?
x99percent said:
The advice he should be taking is to STOP LOADING APPS.
Out of the apps he has listed, I only use Facebook and Handcent SMS... so I'm willing to vouch for those two as not being the culprit. If he hasn't done a wipe and tried running with minimal apps, then the problem is his own fault.
Click to expand...
Click to collapse
I haven't got lots of apps loaded.
And I have gone back to stock, wiped, formatted my SD card many times...etc...etc.
All I am saying is that I am experiencing completely random reboots, and I'm desperate to hear if anyone else is.
This dudejdog or whatever he likes to call himself is plain wrong. I have never, and never will trash anyone. I urge him to prove if I have.
Guys, please, I am not into flaming anyone. I paid my subs to Modaco to get his ROM for chrissake.
ALL I am saying is that I am having issues with reboots of sense and phone when running modded ROMS.
I DO NOT HAVE THE SAME ISSUES WITH STOCK.
That's my bottom line here...I do not have issues with stock.
I am going to run stock with all my normal apps for at least a week now to see what happens. I may be back to the boards at a later date because I don't want to give up on this phone.
grifforama said:
Guys, please, I am not into flaming anyone. I paid my subs to Modaco to get his ROM for chrissake.
ALL I am saying is that I am having issues with reboots of sense and phone when running modded ROMS.
I DO NOT HAVE THE SAME ISSUES WITH STOCK.
That's my bottom line here...I do not have issues with stock.
I am going to run stock with all my normal apps for at least a week now to see what happens. I may be back to the boards at a later date because I don't want to give up on this phone.
Click to expand...
Click to collapse
You could try stock and maybe figure out the Apps2SD scripting that way you have both.
grifforama said:
Guys, please, I am not into flaming anyone. I paid my subs to Modaco to get his ROM for chrissake.
ALL I am saying is that I am having issues with reboots of sense and phone when running modded ROMS.
I DO NOT HAVE THE SAME ISSUES WITH STOCK.
That's my bottom line here...I do not have issues with stock.
I am going to run stock with all my normal apps for at least a week now to see what happens. I may be back to the boards at a later date because I don't want to give up on this phone.
Click to expand...
Click to collapse
Did you try removing any partitions you might have set up (for Apps2SD or swapfiles)...just an idea, simply reformatting your SD card will NOT delete partitions.
grifforama said:
I haven't got lots of apps loaded.
And I have gone back to stock, wiped, formatted my SD card many times...etc...etc.
All I am saying is that I am experiencing completely random reboots, and I'm desperate to hear if anyone else is.
This dudejdog or whatever he likes to call himself is plain wrong. I have never, and never will trash anyone. I urge him to prove if I have.
Click to expand...
Click to collapse
Okay...you said you've gone back to stock. When you go back to stock without any other programs loaded, are you still experiencing the issue?
If not, what I suggest is to load each of your programs one at a time, pausing after you load them for at least 12 hours to see if the reboot occurs. I know that's a time consuming process, but it may help to isolate.
If you are having reboot issues with no additional applications loaded and while you are using the stock ROM, I think there maybe something wrong with the hardware and you should take it back to Sprint for replacement.
Hopefully this helps, or at least points you in a direction to go.
grifforama said:
Guys, please, I am not into flaming anyone. I paid my subs to Modaco to get his ROM for chrissake.
ALL I am saying is that I am having issues with reboots of sense and phone when running modded ROMS.
I DO NOT HAVE THE SAME ISSUES WITH STOCK.
That's my bottom line here...I do not have issues with stock.
I am going to run stock with all my normal apps for at least a week now to see what happens. I may be back to the boards at a later date because I don't want to give up on this phone.
Click to expand...
Click to collapse
When you return, let us know your results and we'll try to help you. I'm thinking it is an application. I had this issue when I tried to update the Superuser Permission program. When it tried to update from Android Marketplace, it would reboot the phone (I actually saw "System crash is inevitable" in the trace log when it tried to update the program).
If you don't mind me asking, what version of the Stock ROM are you using? I did have issues when I was running a custom ROM (Modaco) running 1.29 and tried to upgrade to a custom ROM (again, Modaco) with 1.56. My issue was force close issues that I could not fix. The solution was to revert back to stock, let the OTA update upgrade the phone, reroot and apply the new Modaco ROM.
I understand this isn't a force close issue, but your problem may be similar in nature.
ljmeli said:
Did you try removing any partitions you might have set up (for Apps2SD or swapfiles)...just an idea, simply reformatting your SD card will NOT delete partitions.
Click to expand...
Click to collapse
How do I check for partitions ? I thought formatting would get rid of that ?
I remember partitioning a while back, but I have since formatted, and presumed that would have cleared it ?
I'm not back to Stock 1.56.651.2 build CL85027
I took a chance and re-installed pretty much every application I had previously, apart from the obvious rooted apps like droidswap and cachemate.
It's looking fairly stable for now, but I'll report back over the next few days to see how it goes.
I have to say, I've not once slated anyone on this forum. I have total respect for Flipz and I paid Modaco the subs to try his 2.0 beta and then the release. I really would like to use the rooted ROMS, but right now, I just want to see why my phone is doing what it's doing...
thedudejdog said:
I have no problem speaking for the entire android community when I say...
"its been nice knowing you, good luck with the iPhone and att"
Click to expand...
Click to collapse
hahahahahahahahahaha...
awesome..
but ya, no problems here, sorry mate!
(either user error or bad hardware)
thedudejdog said:
I have no problem speaking for the entire android community when I say...
"its been nice knowing you, good luck with the iPhone and att"
Click to expand...
Click to collapse
As jdog says in a few posts below the one I'm quoting... I have done everything I can to try and help him. I have directly worked with him. Along with a ton of other members on this forum. He chose to go to modaco and say that it fixed all his problems and trash fresh. Now here he is saying he's having the same problems.... again.
Edit: With the hard reboots you are getting, I honestly think you need to go exchange your phone.
Hello guys! El im having a weird issue with my screen since a couple of days ago... I m using my tablet as regular. No problem. Then i lock it, and some hours pass by, then when i want to use it again, i press the unlock button, and when i try to move the lock, the screen wont responde to touch, while all the buttons work as if it was unlocked! Its like been trapped within lock and unlocked stages.. Any thoughts?
hold down the power button until it resets, then see if that fixes your issue.
This is yet ANOTHER issue regarding hacked up 3rd party ROMs.
OP has not stated, but I guarantee he is using a 3rd party ROM or kernel as I have seen this issue before on other units with ROMs from this website.
yojosefo, Im going to save you alot of grief and headaches here. Revert back to stock ROM. It is by FAR the most stable and reliable ROM for the tab10.
I cant not stress this enough, people need to stop using these 3rd party ROMs.
5thElement said:
This is yet ANOTHER issue regarding hacked up 3rd party ROMs.
OP has not stated, but I guarantee he is using a 3rd party ROM or kernel as I have seen this issue before on other units with ROMs from this website.
yojosefo, Im going to save you alot of grief and headaches here. Revert back to stock ROM. It is by FAR the most stable and reliable ROM for the tab10.
I cant not stress this enough, people need to stop using these 3rd party ROMs.
Click to expand...
Click to collapse
You are the most uneducated person I've even seen troll these forums. I've heard more intelligent remarks from a retarded infant. I don't think you even own an android device with everything you say. Why are you lurking these threads if you don't think that the work everyone does is worth it. This post is a perfect example of how stupid you are. Hacked up roms? This issue happened to me on stock. Brand new one day old tab. So you can suck it dude. Get some right info, then hit yourself in the nutsack please. You are a disease in this community.
5thElement said:
This is yet ANOTHER issue regarding hacked up 3rd party ROMs.
OP has not stated, but I guarantee he is using a 3rd party ROM or kernel as I have seen this issue before on other units with ROMs from this website.
yojosefo, Im going to save you alot of grief and headaches here. Revert back to stock ROM. It is by FAR the most stable and reliable ROM for the tab10.
I cant not stress this enough, people need to stop using these 3rd party ROMs.
Click to expand...
Click to collapse
you've done it dude. good job!
you have completly eliminated all credibility from yourself, not managed to help the OP at all, are now dabbling in sheer speculation, and have completly alienated yourself from the community here.
i guess ban #1 did not teach you a thing.
sigh. such is life.
yojosefo, try this:
hard reset through the recovery (stock recovery). pull your media off first if you have any, prior to doing so.
clean the screen.
set wifi to never sleep.
now observe...
if you still receive issue, contact samsung and have it swapped, as losing touch so frequently, and blowing through many conditions in the maxtouch driver which attenuate for this sort of thing, could be indicative of a HW fault.
Hi figured we could use our own separate thread to discuss the killswitch Nvidia supposedly put in place on our old Shield tablets and see what has worked for those who have received their replacement units. If you've gotten a replacement please share if your old unit has been destroyed or not...if not please let others know what the old tablet has on it or what you did to attempt to prevent the brick! Thanks for helping us all out here!
As I said in the other thread, I received my new one, and my old one is still usable on rooted latest stock, unlocked bootloader, with the only app missing being Chrome for some reason. Nothing else disabled or uninstalled. Maybe they haven't turned on the server that sends the kill signal yet.
If the company wants the other device back (dunno if that is true), why keep it? You are breaking a deal while making it less appeling for companies to do this type of thing...+its a saftey risk for you and others around you.
Nvidia said they do not need it back
ManualG on the Nvidia forum said they are not requiring you send it back
"We don't require you to send it back to us to receive the replacement and are collecting them only to make it less of a burden on everyone else who dont have drop off locations like that close by." So you can keep it if you want ?
16 gig tablet, got it this morning. My original is still functional, it was stock rom, rooted with xposed on it. That's as much modding as I've done with mine.
does anyone have more informations about this killswitch?
Is it a service that needs to be deactivated or deleted or a kernel feature?
I just want to make sure it doesn't kill my old tablet when I set up the new one.
Alternatively, I could just flash an older factory image or custom firmware.
From what I've read on other forums (i.e. reddit) most have indicated that the killswitch is embedded in the bootloader and will activated on the defective tablet once the replacement tablet is registered on the nvidia side. I of course cannot confirm for this to be the case but just sharing what others have reported.
yea but it must communicate with the server then and that only works when Android is booted up and all communication drivers loaded.
So there must be another service running in Android that gives this information to the bootloader to kill itself.
If it's bootloader based, flash a bootloader from one of the older recovery images.
Will try that. BL from Update 2.2.2 should be fine?
actually if I flash it back to 2.2.2 it should be fine too since the changes to 3.X aren't that big
That should work just fine.
big time noob question but where are you getting the old bootloaders from to flash?
Until somebody's tablet gets deactivated and a log is captured during the deactivation process, everything said here or anywhere else is just speculation.
bluegizmo83 is right, however the discussion has to start somewhere so kudos to the OP for getting this thread started.
chicodelta said:
bluegizmo83 is right, however the discussion has to start somewhere so kudos to the OP for getting this thread started.
Click to expand...
Click to collapse
Oh I completely agree. I'm all for conversion. But I don't want people to get the wrong impression, like trying to flash an older bootloader. That may stop the deactivation, but it also may not. Its only speculation at this point.
bluegizmo83 said:
Oh I completely agree. I'm all for conversion. But I don't want people to get the wrong impression, like trying to flash an older bootloader. That may stop the deactivation, but it also may not. Its only speculation at this point.
Click to expand...
Click to collapse
Well said. I apologize if my post came through as a solution. I was only mentioning that as folks had mentioned a possible bootloader lock.
Any thoughts on whether flashing CM would serve as a way to circumvent the killswitch? I see that release for this tablet is already available http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043. Thoughts?
scorpionx said:
Well said. I apologize if my post came through as a solution. I was only mentioning that as folks had mentioned a possible bootloader lock.
Click to expand...
Click to collapse
No problem. As I said, I'm all for the discussion, I just wanted to make it clear to everyone that its all just speculation at this point.
I think the old bootloaders are in the old full OTA's someone correct me if I'm wrong. You can also extract them from the full OTA
chicodelta said:
Any thoughts on whether flashing CM would serve as a way to circumvent the killswitch? I see that release for this tablet is already available http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043. Thoughts?
Click to expand...
Click to collapse
To me, this is the most logical place to start at this point! Maybe it works, maybe it doesn't, but unlocking the bootloader, rooting, and installing a custom rom seem like a good starting place. If the stock devices are definitely getting wiped anyways, any changes we make now can't hurt the chances of keeping it alive!
Dear forum reader.
I have tried sevey times to get useful help from the human behind oneplus company.
The first try task what they wanted was that I full wipe off my phone.[emoji35] [emoji35] [emoji35] .
I accept this for a custom ROM but not from a company from which I buyed a device.
After I refused to do so and told them that they might think to find another way to solve my issue the start to go rude.
The HW is good but the human behind looks not very customer friendly or orientated.
Have anyone better experience with that company?
May I ask what is wrong with the phone?
Weird because I did talk to them 2 times and they were really kind to me and tried to understand my problem.. Maybe I was just lucky to talk with the good person. Anyway good luck with your issue.
pedrof1991 said:
May I ask what is wrong with the phone?
Click to expand...
Click to collapse
The issue was that from one moment to another the mobile connectivity was gone.
I have reboot, remove and replace the sim but nothing helps.
I asked the support if the oneplus bug with sim connection could be the problem . the answer was very rude.
So at the end I changed the sim. I don't know what the problem was nor if it could happen again. [emoji35]
I don't see what's the big deal with him saying to do a full wipe, that's usuallyusually the best way to fix bugs. Did you update oxygen os through Ota? Update after update without full wipe may end up causing issues. You should really full wipe and flash the latest version (2.2.1)
You need to understand why they do this:
They allow pretty much full software costumization for your phone, that opens the spectrum of debbuging your problem to almost infinite possibilities.
The only way they have to make sure your hardware is not malfunctioning due software incompatibilities is to make sure it is reset to factory defaults, narrowing the scope of the problem, because they have tested their system and know that the factory defaults indeed work, unlike the many many possiblities that come from rom flashing. That is also why they are very quick to tell you that if by full factory wiping your phone doesn't fix your issue, then you've voided your warranty. That being said, they do allow for a lot of customization, but they won't be dealing with problems introduced BY YOU, for not knowing what you're doing(I'm not implying this, rather just trying to understand their rationale).
It might no be the best solution for every single customer, but it's their best approach to garantee your hardware is not faulty in first hand.
That being said it might not be the perfect approach, but it theirs. Be thankful you don't have a Nexus, or google would be asking for you to ship your phone in, do exactly the same thing that oneplus does, but you'd have to pay for the shippings
migueldbr said:
I don't see what's the big deal with him saying to do a full wipe, that's usuallyusually the best way to fix bugs. Did you update oxygen os through Ota? Update after update without full wipe may end up causing issues. You should really full wipe and flash the latest version (2.2.1)
Click to expand...
Click to collapse
The problem is that all the settings are gone after the full wipe.
I only know titanium backup which is able to backup and restore the settings.
This SW required root, which I currently not have.
maybe you know another SW which can do this without root.
Sent from my ONE E1003 using XDA-Developers mobile app
alxdadev said:
The problem is that all the settings are gone after the full wipe.
I only know titanium backup which is able to backup and restore the settings.
This SW required root, which I currently not have.
maybe you know another SW which can do this without root.
Sent from my ONE E1003 using XDA-Developers mobile app
Click to expand...
Click to collapse
there is one app that allows app restore with data without needing root: https://play.google.com/store/apps/details?id=com.koushikdutta.backup&hl=pt_PT
I used it once and it works, but it would be easier if you rooted
aredpanda said:
You need to understand why they do this:
They allow pretty much full software costumization for your phone, that opens the spectrum of debbuging your problem to almost infinite possibilities.
The only way they have to make sure your hardware is not malfunctioning due software incompatibilities is to make sure it is reset to factory defaults, narrowing the scope of the problem, because they have tested their system and know that the factory defaults indeed work, unlike the many many possiblities that come from rom flashing. That is also why they are very quick to tell you that if by full factory wiping your phone doesn't fix your issue, then you've voided your warranty. That being said, they do allow for a lot of customization, but they won't be dealing with problems introduced BY YOU, for not knowing what you're doing(I'm not implying this, rather just trying to understand their rationale).
It might no be the best solution for every single customer, but it's their best approach to garantee your hardware is not faulty in first hand.
That being said it might not be the perfect approach, but it theirs. Be thankful you don't have a Nexus, or google would be asking for you to ship your phone in, do exactly the same thing that oneplus does, but you'd have to pay for the shippings
Click to expand...
Click to collapse
Well I understand there way but you don't need to be rude.
I have keep the original SW on the HW and haven't rooted or done anything as a normal none XDA have done.
I thought this will help to get good support. My fault.
Don't get me wrong. The HW is good and works. The SW is okay. But the support is , let's say "improvable".
I will buy again the HW but then the first task will be unlock/root/titanium backup. [emoji106] [emoji15]
My assumeation:
I think the company may just want to sell the HW and hope that no one request support.
You can see this also in there own forum. Almost only the first entry in a topic is from company. Then no participation from the company. So there community 2.0 is not better then 1.0
If you don't believe just take a look by your own[emoji5]
Sent from my ONE E1003 using XDA-Developers mobile app
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...