Related
Hi!
Sorry I'm not sure if i searched properly the forums, but I'm wondering if anyone else haves problems with the original rom ( I think its called stock ) 4.1 from HTC One S. I own the phone from 6 months and before updating the g-sensor randomly stopped working it would only start working again with factory reset ( later I found out with restart also worked, because shutdown doesn't clean memory? ).
I was patient for the update and since I updated I noticed that the phone seems slower, already factory reseted, deleted everything, it no longer seems to bug the g-sensor, but it seems to bug quiet often notification bar stuck at mid screen.
Anyway I was wondering if anyone else haves this kind of problems? should I just send it to the factory, it is still on the guarantee.
Thanks for any answers
Edit: by the way, can't seem to use Swift Key, after a while starts blinking
" ( later I found out with restart also worked, because shutdown doesn't clean memory? )."
You probably have fastboot enabled. Its roughly the same as windows sleep-mode, it saves everything in memory to provide almost instant start up.
There seems to be quite a lot of random problems with the official JB rom. I'd suggest you to try one of the many custom roms available here.
Goatshocker said:
" ( later I found out with restart also worked, because shutdown doesn't clean memory? )."
You probably have fastboot enabled. Its roughly the same as windows sleep-mode, it saves everything in memory to provide almost instant start up.
There seems to be quite a lot of random problems with the official JB rom. I'd suggest you to try one of the many custom roms available here.
Click to expand...
Click to collapse
I tought of getting it rooted, but I still have 1 year and half of guarantee so I don't want to lose it , i have my other phone desire rooted through
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.
Rather than do that, I reset the phone, wiped Davlik cache and Fixed Permissions (took a long time!), then rebooted.
That sort of worked, but a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
What's the way-ahead here? Am I stuck doing a factory reset? Or even formatting the SD card?
Thanks in advance.
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
jeffsf said:
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
Click to expand...
Click to collapse
Okay, thanks!
Anything else on the SD card I should back up besides DCIM / Media-> Ringtones/MP3s / "ui" / TitaniumBackup?
(Got about an hour while this stuff goes off to my HD...)
Hoo! Thought I effed myself for a sec - from CWM I was wiping all partitions... including /sdcard.
Then I realized... $#¡+... my ROM is on there!
Fortunately CWM has the "mount USB storage" option.
*whew!*
I was going to add format the sdcard from the phone. But you did that. Typically when what happened to you would happen to me it would be from some app updating and for whatever reason got corrupted during install and fouled the phone up. If you use TiB I highly suggest setting a automated task to back up your TiB backups to drop box, google drive or box.net. Then in these situations you have a recent TiB to fall back on.
JaimeZX said:
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.[...]...a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
Click to expand...
Click to collapse
Hi JaimeZX,
I am curious if you have recently rooted, flashed to stock, or installed the VB or Basic w/a twist kernel? I am running the exact same setup as you list (minus the modem) and this *exact* same scenario happened to me on the exact same day. March 12th, at about 10pm.
Detail as much information as you can, I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel. Perhaps there is an issue with the stock packages, or the USB driver ghosts (I've deleted all USB assigns at all ports and reinstalled for device detection in Heimdall). Hopefully we can get a good list of information to help us fix an issue that is apparently quite catastrophic (in that /data seems to corrupt) and save others from a future headache.
I have searched the dev threads to no avail, and as a general rule it seems that if problems are brought up they are usually met with "try flashing back to stock," "gremlins," "no one else is having problem 'X'," etc. even in cases of users with multiple complaints of the same issue. Both the DSP Sound force close upon EQ preset select and the issue that some had with the Messages, Phone Dialer, Search, Call Logs closing to homescreen are issues that I've seen this with. I believe this is a real issue, and I need to get it fixed without wasting time on messaging replies to anyone advising "try this," "Try that," etc.
My hope is that between the two of us we can address any of the common responses from developers before taking the issue to them and reporting it. I personally cannot today get my phone to boot without freezing (after boot cycle completes - not bootlooping or freezing during the bootleader seq) and am currently attempting to get into d'l mode without much luck.
When this happened to me on Tuesday night I was able to reboot to recovery, reflash the final-fixed.zip first without wiping data (which failed-/data is corrupted somehow here) and then *with* wipe/data and it booted, ran fine, so I then re-flashed BasicWithaTwist Kernel and was fine until late last night again.
I had been using the phone for some fairly constant web searching and the screen went black, appeared to soft reboot, and then froze. I pulled the battery, waited a few mins, reinstalled battery, once again, Freeze after boot.
No indication that an app crashes, phone just completely freezes, remains screen on, capkeys lit, power button does not respond, nor do softkeys or touchscreen. Makes it though the scan device and scan SD processes *sometimes* and other times freezes before it completes them.
I pulled the both the SD and the SIM and booted up, same issue, though it makes it through the scan device processes everytime since it's not scanning 18gb of data on an SD. This tells me it is not SD or SIM related, and is most likely software related, either ROM or Kernel. I've also ruled out the possibility of an old app/data package by reformatting the SD (long format - wipe all containers to "o,") let Android rebuild menu structure on SD, redownloaded a short list of commonly used apps and installed fresh - *NO* TiBackup apps were restored and the actual backup folder was not replaced to the SD after flashing.
I've tried both the Odin (Fb KJ6 back to stock) and the one click (lumin's tutorial) back to stock. Checked the download of Final-Fixed, MD5 checksum is correct. Cannot find MD5 on the sms-T959V-KJ6-antsvx.v1.1.3.zip file. Doesn't seem to be listed on Anton's github site, perhaps I don't know how to find it there. That is the only puzzle piece I haven't double checked.
All for now, looking forward to yours or anyone's replies or suggestions for anything I may be overlooking. Thanks.
0
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
devlinandersen said:
Hi JaimeZX,
... I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel....
0
Click to expand...
Click to collapse
I should add that I have been on Valhalla Black Edition since it was in beta and have been quite happy with it. I only did a back to stock flash to try to (one more time) see if I could get a cooperative DSP sound manager. No such luck, and now a few headaches, and this issue on Tuesday coupled with yours in the exact same timeframe...I'm just thinking there is a problem somewhere in the chain of attack and hope to find it with the help of others.
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
devlinandersen said:
No indication that an app crashes
[...]
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
Click to expand...
Click to collapse
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
jeffsf said:
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Click to expand...
Click to collapse
I will try in a bit, collecting files for another fresh install, different ROM.
jeffsf said:
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
Click to expand...
Click to collapse
This is false logic and is just what I was trying to avoid. I will attempt to explain to hopefully help build a stronger environment that is conducive to problem solving. It still very well could be a dev issue if say, a certain ROM or Kernel begins to wrestle with an app that has recently updated. Is it the apps or the rom's fault? Maybe it is a seldom used feature of an app that just missed all the users testing until now, it's well within the realm of possibilities and would just like to see helpful comments (such as the first portion directly above) to help solve issues. Truth is, I don't know *what* is wrong and neither do you, so a focus on constructive commentary would just help everyone out.
Logs or it didn't happen.
Update...
After a factory reset/data wipe, wipe cache, wipe dalvik cache I had to let the battery charge for a bit. Came back and decided to just try to boot phone, still freezes after boot sequence. I decide that I will flash a different kernel and a different ROM in order to see if I can make a difference. Before flashing Blastoff v2.5 Kernel I decided to factory wipe/data wipe, wipe cache and dalvik again...I am not sure if this is news, but when doing the Dalvik cache wipe in CWM it returned no result, perhaps because I had previously performed and is empty, but I thought it strange that there was *no* communication that it was already empty/wiped, etc.
Installed Blastoff v2.5 and was able to boot without freezing. Something else was damaged with the Rom as well, would not load home screen, only had pulldown menu. Rebooted to Recovery and flashed Unnamed RC-2.zip and have been charging the battery, talking on the phone and reinstalling apps from market.
Same error happened twice to me and once with Jaime. Both of us on VB and Basic+Twist. After installing new kernel i'd point towards kernel. Also uninstalled DSP and installed voodoo sound on VB, but had that on previous version as well. If I had to start somewhere, I'd start right around there.
Hope this helps, will provide logs from SD backup I made before reflash of new kernel/rom. Gotta run. Adios...
-devil.
I had to get my phone going today, it appears to be working without freezing, though on this new app the phone dialer/phone caller force closes on outgoing calls (I am only mentioning here, I will visit the Q&A for the ROM if I need assistance). Unfortunately I was unable to replicate the problem without flashing back to my previous nandroid. I have it saved and given some time I will do my due diligence and get a logcat **if** Jaime doesn't do it before me...because I kinda have a feeling that something was updated in the market on Tuesday evening that is now fighting with the kernel somehow. But again...I didn't run a logcat so it's not even happening...yet...
...to be continued...
Devlin - sorry for the delayed reply.
I did notice that I'd had more and more apps FCing on me in the week leading up to the Über-crash. Unfortunately I don't have any more "background" to add than that.
I backed up everything I wanted on the SD card and then formatted that, plus /data, /system /everythingelsethatwasanoptioninCWM. Then did my installs.
FORTUNATELY (knock on wood) I have not had any recurrence of the major issue.
Device: Note 10.1 N8013 (Wi-Fi Only Model)
The Problem:
The device randomly reboots itself- it's happened while I was scrolling between pages on the launcher, connecting to a WiFi network, and sometimes even when the device was just sitting on its own.
So far, it's happened on every custom ROM I've tried (Omni, IOKP, IOAP and CM), and even Stock TW flashed via Odin with and without a PIT File.
The duration between reboots is inconsistent, but it's always a full reboot- suddenly back to the Samsung logo and then the ROM logo, beore the system loads up normally.
Probable Causes (my best guesses):
Apps are almost definitely not a cause, because I only install a handful (ES File Explorer, GoldenDict, AnyMemo, Mantano Reader, Skype, Manga Watcher, Opera Browser, MXPlayer, AdAway, Greenify and Helium backup).
***One particular event sticks out to me though: early on when I first got the device, the battery ran out, and I had to leave it as is for 2 weeks, due to some family issues.
My Questions:
1.) How would I go about diagnosing the cause of the random reboots?
2.) Could the extended Battery depletion described above be the cause of my instability issues?
3.) If my current battery is indeed the problem, should I buy a replacement from NewPower99? I am worried that since the Note 10.1 is a 2-year old device, a Li-Ion Battery sitting on a store shelf for such a long duration would be no better than the stock one I have now.
Note: Unfortunately, I waited too long and the tablet is beyond its Warranty Date, so sending it in for repair/replacement is not an option.
Thank you for taking the time to read this. I'd really appreciate any help/advice you can give!
same here
mowgli_writes said:
Device: Note 10.1 N8013 (Wi-Fi Only Model)
The Problem:
The device randomly reboots itself- it's happened while I was scrolling between pages on the launcher, connecting to a WiFi network, and sometimes even when the device was just sitting on its own.
So far, it's happened on every custom ROM I've tried (Omni, IOKP, IOAP and CM), and even Stock TW flashed via Odin with and without a PIT File.
The duration between reboots is inconsistent, but it's always a full reboot- suddenly back to the Samsung logo and then the ROM logo, beore the system loads up normally.
Probable Causes (my best guesses):
Apps are almost definitely not a cause, because I only install a handful (ES File Explorer, GoldenDict, AnyMemo, Mantano Reader, Skype, Manga Watcher, Opera Browser, MXPlayer, AdAway, Greenify and Helium backup).
***One particular event sticks out to me though: early on when I first got the device, the battery ran out, and I had to leave it as is for 2 weeks, due to some family issues.
My Questions:
1.) How would I go about diagnosing the cause of the random reboots?
2.) Could the extended Battery depletion described above be the cause of my instability issues?
3.) If my current battery is indeed the problem, should I buy a replacement from NewPower99? I am worried that since the Note 10.1 is a 2-year old device, a Li-Ion Battery sitting on a store shelf for such a long duration would be no better than the stock one I have now.
Note: Unfortunately, I waited too long and the tablet is beyond its Warranty Date, so sending it in for repair/replacement is not an option.
Thank you for taking the time to read this. I'd really appreciate any help/advice you can give!
Click to expand...
Click to collapse
I have the same problem The device randomly reboots itself
but the battery life is better that the stock ROM for me and the sound too
replace the battery that my advice for you
goodluck
"sorry for my bad english"
Thank you
badralamoudy said:
I have the same problem The device randomly reboots itself
but the battery life is better that the stock ROM for me and the sound too
replace the battery that my advice for you
goodluck
"sorry for my bad english"
Click to expand...
Click to collapse
Thank you, badralamoudy. It's nice to know I'm not alone with this problem. Two quick follow-ups though:
1.) Which ROM are you using right now?
2.) Have you replaced the battery on your device? If you have, did it fix the random reboot problem?
Thank you for trying to help.
I am a noooob
mowgli_writes said:
Thank you, badralamoudy. It's nice to know I'm not alone with this problem. Two quick follow-ups though:
1.) Which ROM are you using right now?
2.) Have you replaced the battery on your device? If you have, did it fix the random reboot problem?
Thank you for trying to help.
Click to expand...
Click to collapse
1- omni rom
2- no
my battery is good and still reboot randomly
I used Omega ROM before omni and it was stable
when you flash back to stock. Do you let google play reinstall your apps and data.
My Suggestion is flashing back to the latest Samsung full firmware . Then Do not let google play reinstall your apps or app data..
Install only one at one day See how it does . another the next day and so on
OHH After you flash the new stock firmware . Reboot and do a factory restore .
I have had this issue with my nexus and other devices when i flashed alot. I think its just left over data or something corrupt you are restoring
i just got my note pro 12.2 wifi version (international) a few days ago and already experiencing problems, firstly the wifi was so slow so i updated it OTA to the latest stock firmware i can't remember what it is but it's the latest official 4.4.2 they have and that improved the wifi but now i'm encountering issues of rebooting randomly after using facebook app. it's always after i lock the screen it suddenly reboots after 2 mins or something especially if i have say been using a lot of memory for it.. ie if i scroll down 4000 friends that's when it always reboots once i lock the screen. is this liekly to be hardware or software issue or an app issue?
i have only had it a few days so haven't managed to play with it enough to test it to the max.
just now it rebooted and i played one youtube HD video and used multi window to use the facebook app (old version 7.0 - i like this version).. but i hadn't used the facebook app that much while on, the only thing i did different was i plugged in my samsung s3 charger into the note pro to test how long it would take to charge using a usb 2.0 connection instead. it's official charger official cable, is that likely to cause reboot issues?
previously it was just after using facebook for a long time for a ram intensive amount, i also tested it after reboot and using facebook a bit and locking screen and it didn't reboot so it made me think ok it's just when facebook is being used a lot and all the ram and memory is exhausted caching 4000 friends viewing so i didn't think anything of it.
is this likely to be hardware or software issue? are hardware issues ever the main problem with rebooting?
I know the usual tests, having to use odin to flash official firmware, trying a different facebook version, removing and not using facebook at all and see if it still reboots and lastly factory reset.
ideally i'd like to avoid all of those things as it is a major hassle and i can live with the reboot issue provided it isn't a hardware problem. is there anyway to test it to know for certain it is hardware and not software and the app?
edit: it keeps rebooting even if i dont use the app
seems to happen when i lock the screen sometimes it just reboots randomly.
anyone else have this?
You could try to remove that facebook app and see if that fixes the problem.
does anyone know what is causing this?? is it hardware?
i've factory reset removed all apps, then added one app at a time then added about 6gb of videos and added wakelock detector. all seemed fine
then i tried to unmount the sd card and then it rebooted.. why is it doing this??
pete101 said:
does anyone know what is causing this?? is it hardware?
i've factory reset removed all apps, then added one app at a time then added about 6gb of videos and added wakelock detector. all seemed fine
then i tried to unmount the sd card and then it rebooted.. why is it doing this??
Click to expand...
Click to collapse
Could it be a bad sector on the SD card? I'd long format it using a pc to be sure.
Sent from my SM-P900 using Tapatalk
it's not the faceboook k app i've realised now it just coincidentally seemed to be that as it is ram intensive.
i factory reseted and then put the app back on but didn't log in. 3 times it has rebooted by itself over different scenarios.. 1 plugging in a samsung usb 2.0 charger from a samsung s3, 2 when unmounting sd card, 3 when closing the screen when any ram intensive app is in the background (there's still like 500mb of ram left!! i dont know why it's rebooting like this.
i can't figure it out. is anyone else having these issues? im not sure if it's a kitkat 4.4.2 issue.. reading forums from other users with different devices i'm seeing the reboot issue coming up alot especially on the s4.
http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046/page22
but i dont know for certain if it's a hardware issue.
my next steps which i really want to avoid is to factory reset AGAIN and not load any apps (the problem with this is it requires a certain amount of ram intensity to be used before it randomly happens.. if i dont add any apps like instagram or facebook or tumblr i can't get it back to the state where it reboots randomly)
i've also enabled all apps (i usually disable all the bloatware i can without being rooted) but it does bring up errors of android.core.process has stopped etc and some gapps errors (im hoping this is the cause of the reboot) and see if it reboots. it's difficult recreating the scenario consistently.
i udnerstand it might reboot if you've overused the memory but it clearly shows lots is free so i can't figure out what is causing it?
my next step after all this is to flash the latest version of stock so i can't put it down to the OTA updates that is causing it. if that fails i revert to odin to flash the original 4.4.2 it came with.. and failing that i'll have to return it
does anyone have any ideas whether it is hardware (maybe the power button is slightly off so when you press down it in a certain angle it triggers a restart?)
or is the motherboard or corrupted sector of the memory which when it writes over it causes the reboot?
i always assumed reboot issues were normally always firmware issues and not hardware.. surely samsungs quality control is a bit better than that??
If it were me I would yank the microsd card out, factory reset, set up just my gmail without allowing auto backup/restore and apply all updates. I'd then let the tablet run for a full day and use it just for web browsing and Youtube to see if the problem is still there. I would not install anything for at least a day, including the microsd card. This would be as stock as one could get and rule out the possibility of it being any software that I installed or the microsd that I was using.
I suspect it's software but the only way to know is to be patient and test it out for sure.
Sent from my SM-P900 using Tapatalk
Hi,
same tablet, bought there is 3 weeks. I installed the latest firmware update (XXUANI1)
I rooted the tablet (to allow sd-card writing).
and that's it.
like some of you, I have random reboot.
I can't remember if it happened before the root or not. I think that yes, but I am not 100% sure.
I don't see anyone reported that the root cause random reboot...
it is really random. sometime, the tablet stay one night without reboot, sometime, I can have 3 reboot in one hour.
I don't find what kind of application is causing that issue.
I really believe that it is software. before the firmware update, I stayed 2 weeks without any issue.
I tried to reboot in recovery mode, and wipe the cache, without success.
I will probably try to do a factory reset...
Olivier
orobin said:
Hi,
same tablet, bought there is 3 weeks. I installed the latest firmware update (XXUANI1)
I rooted the tablet (to allow sd-card writing).
and that's it.
like some of you, I have random reboot.
I can't remember if it happened before the root or not. I think that yes, but I am not 100% sure.
I don't see anyone reported that the root cause random reboot...
it is really random. sometime, the tablet stay one night without reboot, sometime, I can have 3 reboot in one hour.
I don't find what kind of application is causing that issue.
I really believe that it is software. before the firmware update, I stayed 2 weeks without any issue.
I tried to reboot in recovery mode, and wipe the cache, without success.
I will probably try to do a factory reset...
Olivier
Click to expand...
Click to collapse
Assuming you have custom recovery installed as well; have you tried wiping dalvic? It will force applications to recompile and possibly fix a corrupted application or its associated files.
Hi,
I just checke.…
I was thinking that the root method was not setting the knox flag, so i was thinking there is no recovery in the file flashed… .
I was wrong.
My waranty is void, knox is set. I still have no custom recovery : in the file provided by chainfire, there is a recovery which is probably coming from samsunG…
So i will install a new recovery and try to wipe all caches dalvik.etc.
Hi,
since my knox is set now :
I tried to install TWRP recovery, which allow me to do a wipe of the cache AND dalvik Cache.
it did not resolved anything. the tablet still reboots randomly.
then, I decided to restart from scratch :
I flashed the same firmware I had, using ODIN, and do not root it.
this is this firmware : http://www.sammobile.com/firmwares/database/SM-P900/XEF/
I will keep you updated if it solve the reboot issue or not.
thanks
Olivier
pete101 said:
i always assumed reboot issues were normally always firmware issues and not hardware.. surely samsungs quality control is a bit better than that??
Click to expand...
Click to collapse
Hi
I had the same problem and also thought it was the power button that was faulty but then I flashed the previous firmware then tried to use it a bit and no reboots since so I guess samsung released a new firmware that solved the slow wifi problem but then boosted it a little too much or so it seems judging by the reboots whenever there's too much overload.
So I guess for now I will stick with an older firmware
oops... it rebooted while I was surfing the play store so I guess I spoke too soon
Hi folks, I know what i'm doing, so I flashed the images and it all worked...BUT some major things are missing. I cant drop down the notification drawer (nor do I get any notifications) Also, nothing Google syncs. I tried manually syncing/logging out and logging back in and nothing seems to work, so 1) Suggestions? 2) Is there a dedicated forum for this? I cant seem to find anything online. I also tried flashing it again and to no avail.
Help me XDA, you're my only hope to not going mad on my phone.
JustinMorinC said:
Hi folks, I know what i'm doing, so I flashed the images and it all worked...BUT some major things are missing. I cant drop down the notification drawer (nor do I get any notifications) Also, nothing Google syncs. I tried manually syncing/logging out and logging back in and nothing seems to work, so 1) Suggestions? 2) Is there a dedicated forum for this? I cant seem to find anything online. I also tried flashing it again and to no avail.
Help me XDA, you're my only hope to not going mad on my phone.
Click to expand...
Click to collapse
Try downloading the image again and use the back ports, the ones directly connected to the motherboard. If you can't fix it and/or find an answer anywhere, remember that android M is beta; report it to the android developers and wait.
Just some personal history on this kind of occurrence (tl;dr some times the same hardware can behave differently on the same conditions):
My brother and I had once the same phone, the LG Optimus 2X. We bought the same phone, at the same store, on the same day, a promotion; quite the upgrade from my motorola milestone (droid). His would always have problems with custom roms that mine never did, some times was the other way around, but the developers fixed over time given the pertinent logs. It also happened Installing mac on my assembled pc, I got to have problems other people with the exact same hardware configuration never did and I didn't had problems that other people had.
mikeszf said:
Try downloading the image again and use the back ports, the ones directly connected to the motherboard. If you can't fix it and/or find an answer anywhere, remember that android M is beta; report it to the android developers and wait.
Just some personal history on this kind of occurrence (tl;dr some times the same hardware can behave differently on the same conditions):
My brother and I had once the same phone, the LG Optimus 2X. We bought the same phone, at the same store, on the same day, a promotion; quite the upgrade from my motorola milestone (droid). His would always have problems with custom roms that mine never did, some times was the other way around, but the developers fixed over time given the pertinent logs. It also happened Installing mac on my assembled pc, I got to have problems other people with the exact same hardware configuration never did and I didn't had problems that other people had.
Click to expand...
Click to collapse
Thats a great idea! I'm using a laptop so I will change ports. Does it make a difference when it says that ...exceeded maximum size... or what ever it said, id that normal? Update should be out this week I think as well!