Database Users

[FW] New Firmware 2.3.26

So I was trying to get the new 2.3.20 firmware and I went to the Archos website. But it looks like there was a new firmware posted this morning. 2.3.26.
I don't know how to direct link, but i'll try.
http://update.archos.com/8/gen8/gen8_2.3.26/firmware_archos_android_gen8.aos

Version 2.3.26 - April 21st, 2011
Wi-Fi: fix cannot scan on an access point above channel 11 regression
Phone tethering: fix TCP/IP header compression setting crash
System stability: avoid Android reboot in case of missing audio
Media library: fix media libray not updated on hard drive based A70
Notification: decrease low battery notification volume
Application: attempt to solve Pandora application not able to switch songs
Application: solve music lag in applications using OGG format
Bluetooth GPS: increase compatibility with 3rd party applications
Display: avoid white/black screen happening sometimes when switching back the display on

Thx jknut, i'm such a noob I forgot to post the changelog. I usually wait till theres a uruk version, but i'm gonna install now cause i'm fairly sure we'll get uruk in a couple of days.

Techngro said:
Thx jknut, i'm such a noob I forgot to post the changelog. I usually wait till theres a uruk version, but i'm gonna install now cause i'm fairly sure we'll get uruk in a couple of days.
Click to expand...
Click to collapse
Not that much of a noob, you posted the link to the firmware that should end my buggy horrors
Thanks jknut for the changelog

Hi, I have one question.
If I have the permanent root from churli (I'm sorry if I miss-spelled it..), do I just updated it regularly? I used to update all the firmwares by just downloading the firmware right on my A70 and install it right away.. but will that work if I have the root? I just rooted my A70 yesterday...and I'm a newbie haha

sw6lee said:
Hi, I have one question.
If I have the permanent root from churli (I'm sorry if I miss-spelled it..), do I just updated it regularly? I used to update all the firmwares by just downloading the firmware right on my A70 and install it right away.. but will that work if I have the root? I just rooted my A70 yesterday...and I'm a newbie haha
Click to expand...
Click to collapse
I just followed Steps 2, 3, 4 of Chulri's post. Chulri already has the new files for "fw 2.3.26 +rw" for Step 3. I like the optional Step 4 because I don't have to worry about holding down the volume button everytime I boot to get root.

Hi,
Has somebody tested this new release?
I updated to version 3.2.20 last week and I was very happy when I realized that cinema plugin was not required to play all the formats which I was not able to before the update (AAC, AC3, MPEG2, etc)
Can somebody confirm if this has not been "fixed"?
Thank you.

Well I have tried this new release and all I can say is bootloop, oh and to top it off I think that my right speaker has blown.
Archos I hope you're reading this, you need to sort your firmware releases out. Whilst you're at it Gingerbread would be nice. If you can put it on the Arnova with inferior hardware you have no excuse but to port it to the 101.

toyface said:
Well I have tried this new release and all I can say is bootloop, oh and to top it off I think that my right speaker has blown.
Archos I hope you're reading this, you need to sort your firmware releases out. Whilst you're at it Gingerbread would be nice. If you can put it on the Arnova with inferior hardware you have no excuse but to port it to the 101.
Click to expand...
Click to collapse
I just noticed the update when I went to the archosfans 2.3.20 bugs thread to report wifi drop powersave disabled while running tunein radio...
OTA update went fine, just waiting for A43 to charge up, then I'm going to do the A32 as well...
[EDIT]
Power LED blinking -> UI batt meter (and About Device) say 98% charge...
had this once with 2.3.20 showing 97% when LED blinking but next charge and thereafter showed 100% when LED blinking...
[/EDIT]

I had this Problem from the first day.
LED blinks and the battery show around 90%.
If i unplug the power the status goes to 98-100%, most 100%.
If i reboot the device with plugged power, the status is 75-90% after restart.
Sometimes the status falls to 87-91% if i plugged the power in.
I can live with it, but it is annoying.

did they remove bluetooth PAN tether ? I had dun/pan option while setting up BT tether with 2.3.20. but now no more that option. the probken for me is, i am using cdma phone(bell htc touch) but with BT DUN the Archos cannot dial CDMA number #777. I set bell APN (pda.bell.ca) it's not working. Actully even if it works I worry about it because it may charge me more.
Before with 2.3.20 , it worked perfect with BT PAN and my phone set to Internet sharing.

This update cleared up my waking-up issue.
It's pretty much an instant on now after the monitor idles off. Before, (after being off for more than a few minutes) it was a crap-shoot as to whether or not the screen would come on and I often had to fight with it and double, triple, quadruple tap the power button to get things alive. No longer.

still reboot cycles problems when charging the 101..problem started with these last 2 updates.

twit.tv app FCs all of the time with this fw...
I wonder why they released this one OTA as it seems to be more broken than .20 was...

youtube and many other flash video played in the browser hangs after about 15 seconds or so. Soemtime this causes the whole system to freeze requiring forced reboot.
This is the worse build so far, my A70 was most stable at 2.1.08.

Wow. I am having the exact opposite experience with this firmware. I find the browser and flash to be very solid. Before I could never play even youtube mobile in HD without it freezing and forcing a hard reboot.
Also, i'm having less general freezes.
I am still having absolutely no luck whatsoever with tethering to my Android phone (cliq). It's driving me crazy cause this was one of the main reasons I went with Archos.
Have you guys done a full reinitialization? That's what I did and, even though it's a pain to reload all your files, it might help with many of the problems you are having.

Techngro said:
Wow. I am having the exact opposite experience with this firmware. I find the browser and flash to be very solid. Before I could never play even youtube mobile in HD without it freezing and forcing a hard reboot.
Also, i'm having less general freezes.
I am still having absolutely no luck whatsoever with tethering to my Android phone (cliq). It's driving me crazy cause this was one of the main reasons I went with Archos.
Have you guys done a full reinitialization? That's what I did and, even though it's a pain to reload all your files, it might help with many of the problems you are having.
Click to expand...
Click to collapse
As a matter of fact I did an Android reset to get away from some of the problems I was having with bootloops and such. This has helped with the general performance of the 101, which I'd say is down to the 64mb swap file I now enjoy.
I did have a couple bootloops until I enabled a lock screen pattern unlock and I have now experienced nothing but fairly good performance

It seems that 2.3.26 is different from vesions before

Need more language for External Keyboard Layout such as Thai

jakkrith said:
Need more language for External Keyboard Layout such as Thai
Click to expand...
Click to collapse
You'd probably be better off posting in the archosfans.com forum's bug list thread for 2.3.26 as Archos employees actually monitor that site and have actually even started some of the buglist/fw release threads... i.e. I'm not sure that they're even aware of the xda-devs gen8 section and even if they were would they bother to read it...

[Q] Unique Nexus One power up issue

Hi Moderators,
Please feel to delete or move this thread, if you find it repetitive. Apologies for starting a new thread.
Hi All,
I have a unique issue with my Nexus one. Sometimes it fails to reboot and then does not start even pressing power button multiple times. Sometimes it starts but then screen does not come up after the display time expires. Whenever it is ON, power button works good, ALWAYS. When it goes into the weird state, I am not able to put it in recovery mode as well. Whenever, I am able to put it in recovery mode, power button ALWYAS works good. Also I have seen that sometimes, even after boot-up it is not able to detect the SD card even when battery is at around 30%.
I have tried all the methods I could find related to "Nexus One power issue" here on XDA as well as via Google search. Sometimes the "remove battery multiple times while plugged into AC" works but at times it also does not help either.
I visited the local HTC service station. The guy there showed me that the small strip of Litmus paper on battery and phone has turned reddish. For normal phone it should be white. This indicates that phone was in contact with something acidic in nature. I tried swapping batteries with my friends and colleagues, but no luck. I have replaced the power button strip of my phone which seems to be trouble some as per the discussions here.
I have tried CM7.x, RCADS, MM super hybrid, eVil's desire port and of course stock 2.3.x ROMs. All seem to have similar issue one or another time. I have also tried Amon_RA's 2.2.0 and 2.2.1. Somebody told me to try with CM6.1 which I will try now if I am able to boot it in recovery.
My warranty is long gone, BTW. Also I bought my phone from US and it is not possible for me to go there again in near future. This issue cropped up approximately 3/4 weeks back. I have default radio.
Having said that, does anybody know what could be the issue with my phone? Has anyone faced such an issue?

chota_shivaji said:
Hi Moderators,
Please feel to delete or move this thread, if you find it repetitive. Apologies for starting a new thread.
Hi All,
I have a unique issue with my Nexus one. Sometimes it fails to reboot and then does not start even pressing power button multiple times. Sometimes it starts but then screen does not come up after the display time expires. Whenever it is ON, power button works good, ALWAYS. When it goes into the weird state, I am not able to put it in recovery mode as well. Whenever, I am able to put it in recovery mode, power button ALWYAS works good. Also I have seen that sometimes, even after boot-up it is not able to detect the SD card even when battery is at around 30%.
I have tried all the methods I could find related to "Nexus One power issue" here on XDA as well as via Google search. Sometimes the "remove battery multiple times while plugged into AC" works but at times it also does not help either.
I visited the local HTC service station. The guy there showed me that the small strip of Litmus paper on battery and phone has turned reddish. For normal phone it should be white. This indicates that phone was in contact with something acidic in nature. I tried swapping batteries with my friends and colleagues, but no luck. I have replaced the power button strip of my phone which seems to be trouble some as per the discussions here.
I have tried CM7.x, RCADS, MM super hybrid, eVil's desire port and of course stock 2.3.x ROMs. All seem to have similar issue one or another time. I have also tried Amon_RA's 2.2.0 and 2.2.1. Somebody told me to try with CM6.1 which I will try now if I am able to boot it in recovery.
My warranty is long gone, BTW. Also I bought my phone from US and it is not possible for me to go there again in near future. This issue cropped up approximately 3/4 weeks back. I have default radio.
Having said that, does anybody know what could be the issue with my phone? Has anyone faced such an issue?
Click to expand...
Click to collapse
Hi Moderators,
Apologies for posting this thread in this sub-forum. I forgot that question threads should be in Q&A section. Having said that, if its not too much to ask, can you please move this thread to Nexus One's Q&A sub-forum?

Just update d firmware wit any of the ones which r available here...m pretty sure this ll solve yor issue as I think its related to software not hardware...
Sent from my GT-S5830 using XDA Premium App

Firmware update lol seriously ...try updating your radio to the 5.08 or 5.12 then flashing a stock rom and go from there
shreyasvb said:
Just update d firmware wit any of the ones which r available here...m pretty sure this ll solve yor issue as I think its related to software not hardware..
Sent from my GT-S5830 using XDA Premium App
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App

b1337 said:
Firmware update lol seriously ...try updating your radio to the 5.08 or 5.12 then flashing a stock rom and go from there
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks a lot for your suggestions. I somehow manage to put my Nexus one in recovery mode by pressing power + volume down buttons multiple times. Then flashed the radio 5.08 on it. I already have CM 7.x ROM.
With this combination, my phone is working good so far. The power down issue would have reoccured by now. So it looks like my issue is resolved. I will use it for 24 more hours and come back if I am able to hit the power down issue again.
Once again thanks for the suggestions. As usual, XDA rocks. Had been experiencing this since good old Windows Mobile + HTC Touch days :-D.

chota_shivaji said:
Thanks a lot for your suggestions. I somehow manage to put my Nexus one in recovery mode by pressing power + volume down buttons multiple times. Then flashed the radio 5.08 on it. I already have CM 7.x ROM.
With this combination, my phone is working good so far. The power down issue would have reoccured by now. So it looks like my issue is resolved. I will use it for 24 more hours and come back if I am able to hit the power down issue again.
Once again thanks for the suggestions. As usual, XDA rocks. Had been experiencing this since good old Windows Mobile + HTC Touch days :-D.
Click to expand...
Click to collapse
I tested my Nexus one for past approx ~36 hours. In this time, I was hit by the issue mentioned in this thread twice.
Out of those 2, 1 was probably caused due to a soft reboot as I was able to get some output from cat /proc/last_kmsg but could not save it for sharing. The other one did not had last_kmsg entry so I am not sure what caused the phone to go haywire. The battery charge was ~30% when I booted it next time.
Now, I am on CM 7.x stable + 5.08 radio + Amon_Ra' 2.0.0 recovery and I explicitly have wiped the cache and Dalvik-cache via recovery. Since then, phone seems to be working OK. I will keep this thread updated if I am again able to get into the "Not able to power-on with power button" issue.

[Q] CM11 half blacked out screen while getting incoming calls with latest

I get a half blacked out screen while getting incoming calls with the ROM from 20.01.2014 from quarx (look: quarx2k.ru/cm11.0-nightly-defy+/?C=M;O=A). Someone else too? What can I do about it? Maybe change an apk within the ROM?

x53 said:
I get a half blacked out screen while getting incoming calls with the ROM from 20.01.2014 from quarx (look: quarx2k.ru/cm11.0-nightly-defy+/?C=M;O=A). Someone else too? What can I do about it? Maybe change an apk within the ROM?
Click to expand...
Click to collapse
Me too. I have to say that I still experience call delay bug (possibly even worse) with this release.

I did a clean install of ROM 20140120 (wiped system and data, too), but with no luck. When I install the ROM 20140117 the square is transparent again, but back to ROM 20140120 it's black. I dont understand how other defy users haven't this problem? Are defy devices so different? OK, dont use GApps?!?
wolfie05 said:
Me too. I have to say that I still experience call delay bug (possibly even worse) with this release.
Click to expand...
Click to collapse
For 2 seconds or 2 times ringing and screen shows up. However you could use the power key to wake up your phone earlier, I know a bad and impractical workaround.

screen delay
x53 said:
I did a clean install of ROM 20140120 (wiped system and data, too), but with no luck. When I install the ROM 20140117 the square is transparent again, but back to ROM 20140120 it's black. I dont understand how other defy users haven't this problem? Are defy devices so different? OK, dont use GApps?!?
For 2 seconds or 2 times ringing and screen shows up. However you could use the power key to wake up your phone earlier, I know a bad and impractical workaround.
Click to expand...
Click to collapse
same here!! any solution yet for this??

I too am fighting with this bug, on the latest firmware of Quarx , 08/02/2014 , the firmware is satisfies me, but the response of the screen during incoming ringing still existents delayed , although the waiting time decreased, But this is not enough for full use of the device
I managed to slightly accelerate the reaction of the display by changing the frequency on the CPU
Four steps of processor : Vsel 300/17,600/35,900/50,1255/63
Also I replace the kernel in firmware of Quarx, I integrate SlimKat kernel , despite the fact that the kernel slim is almost copy of the Quarx kernel, operation of the device is improved .
You can try my steps and decide to test and decide own conclusions.
If someone tries to leave me your comment.

Atrix 4g kitkat ROM{by Zn7mkUKzN1r8aCIV} ROM problems and fix

Atrix 4g ROM Developer Zn7mkUKzN1r8aCIV's new ROM v2 gets you Android 4.4.4 KitKat and also fixes the battery percentage problem that is affecting most Atrix 4g users. check out his Development Thread here:
http://forum.xda-developers.com/atrix-4g/development/rom-cm-11-android-4-4-4-atrix-bigpart-t2847281
However, after flashing his ROM, most of you will get a "Setup Wizard has stopped" problem. Here's the fix I found:
1)On the screen that says "Choose language:" choose your language
2)On the screen that says"Insert sim card", you will find that when you press "next" or "skip", the setup wizard will stop. At that point, swipe down the status bar.
3)Touch the date at the top left corner of the status bar
4)It will then ask you to sign in to your Google account and WiFi.
5)After you do all that, you will be taken back to the calender screen.
6)Triple click fast on the back button or home button.
7)You will be taken back to the language selection screen.
8)Choose language
9)Now you will find that when you press skip on the "Insert sim card screen, it won't force close anymore.
10)Sign in to WiFi again, and you will then successfully finish the setup and can start using your phone.
The second problem, is that your phone most likely will not detect the sim card. Here's how to fix:
1)Go to settings
2)Turn on then off the mobile network.(MUST!)
3)Power off your phone, do not take sim card out.
4)Power your phone back on.
5)Your phone should now detect the sim card.
[EDIT]:New problems and fixes:
This problem is very rare and will probably not happen to your problem at all, but just in case, here's how:
After flashing ANY new ROM, some of you will probably get a black screen instead of the boot animation. DO NOT WORRY, you're phone is NOT bricked, it's just that the boot animation will work randomly sometimes and sometimes not. Just power on your phone and wait until the navigation bar buttons at the bottom of the phone light up, then you will know that the phone has finished booting up, and then simply just press the power button to open the screen.
AGAIN, this will most likely never happen to your phone, so far, I think I was the only one experiencing this problem.
Another problem that came up: Google Now voice search in the Google now launcher doesn't work. This should fix the problem:
1)Download the Google Now lib from this link (thanks to XDA Developer Jesco): http://d-h.st/EH1
2)Go to file manager and move it into /system/libs.
3)Now the Google Now voice search should work.
Ask any questions that you have and I will be happy to help you ASAP.

HackerXmaster said:
Atrix 4g ROM Developer Zn7mkUKzN1r8aCIV's new ROM v2 gets you Android 4.4.4 KitKat and also fixes the battery percentage problem that is affecting most Atrix 4g users. check out his Development Thread here:
http://forum.xda-developers.com/atrix-4g/development/rom-cm-11-android-4-4-4-atrix-bigpart-t2847281
However, after flashing his ROM, most of you will get a "Setup Wizard has stopped" problem. Here's the fix I found:
1)On the screen that says "Choose language:" choose your language
2)On the screen that says"Insert sim card", you will find that when you press "next" or "skip", the setup wizard will stop. At that point, swipe down the status bar.
3)Touch the date at the top left corner of the status bar
4)It will then ask you to sign in to your Google account and WiFi.
5)After you do all that, you will be taken back to the calender screen.
6)Triple click fast on the back button or home button.
7)You will be taken back to the language selection screen.
8)Choose language
9)Now you will find that when you press skip on the "Insert sim card screen, it won't force close anymore.
10)Sign in to WiFi again, and you will then successfully finish the setup and can start using your phone.
The second problem, is that your phone most likely will not detect the sim card. Here's how to fix:
1)Go to settings
2)Turn on then off the mobile network.(MUST!)
3)Power off your phone, do not take sim card out.
4)Power your phone back on.
5)Your phone should now detect the sim card.
[EDIT]:New problem and fix:
This problem is very rare and will probably not happen to your problem at all, but just in case, here's how:
After flashing ANY new ROM, some of you will probably get a black screen instead of the boot animation. DO NOT WORRY, you're phone is NOT bricked, it's just that the boot animation will work randomly sometimes and sometimes not. Just power on your phone and wait until the navigation bar buttons at the bottom of the phone light up, then you will know that the phone has finished booting up, and then simply just press the power button to open the screen.
AGAIN, this will most likely never happen to your phone, so far, I think I was the only one experiencing this problem.
Ask any questions that you have and I will be happy to help you ASAP.
Click to expand...
Click to collapse
Common fixes on most, if not all, devices. Nothing new reported.

palmbeach05 said:
Common fixes on most, if not all, devices. Nothing new reported.
Click to expand...
Click to collapse
I installed the ROM as follows:
1 - I installed CWM via fastboot;
2 - I made all the necessary WIPES;
3 - I installed the ROM,
4 - I installed the BASENBAND N_01.100.00R BELL,
5 - I started the phone because the first time it started not recognizing the operator,
6 - I rebooted again and installed GAPPS, then started normally,
bugs:
1 - YouTube closes alone
2 - I had a few reboots,
3 - Battery with this little income
4 - Flash does not work automatically, you have to touch the screen to activate the focus and the flash works well,
Work:
1 - GPS is working well,
2 - Telephone network is good,
3 - Games are running normally
4 - Wifi is working,
5 - Back and front camera is working well, taking pictures with good resolution.

working youtube
lucasrafael07 said:
I installed the ROM as follows:
1 - I installed CWM via fastboot;
2 - I made all the necessary WIPES;
3 - I installed the ROM,
4 - I installed the BASENBAND N_01.100.00R BELL,
5 - I started the phone because the first time it started not recognizing the operator,
6 - I rebooted again and installed GAPPS, then started normally,
bugs:
1 - YouTube closes alone
2 - I had a few reboots,
3 - Battery with this little income
4 - Flash does not work automatically, you have to touch the screen to activate the focus and the flash works well,
Work:
1 - GPS is working well,
2 - Telephone network is good,
3 - Games are running normally
4 - Wifi is working,
5 - Back and front camera is working well, taking pictures with good resolution.
Click to expand...
Click to collapse
http://forum.xda-developers.com/show....php?t=1529715 This youtube should work, never had any problems with it
---------- Post added at 10:18 AM ---------- Previous post was at 10:14 AM ----------
http://forum.xda-developers.com/showthread.php?t=1529715 link above doesnt work, this should be good

lucasrafael07 said:
I installed the ROM as follows:
1 - I installed CWM via fastboot;
2 - I made all the necessary WIPES;
3 - I installed the ROM,
4 - I installed the BASENBAND N_01.100.00R BELL,
5 - I started the phone because the first time it started not recognizing the operator,
6 - I rebooted again and installed GAPPS, then started normally,
bugs:
1 - YouTube closes alone
2 - I had a few reboots,
3 - Battery with this little income
4 - Flash does not work automatically, you have to touch the screen to activate the focus and the flash works well,
Work:
1 - GPS is working well,
2 - Telephone network is good,
3 - Games are running normally
4 - Wifi is working,
5 - Back and front camera is working well, taking pictures with good resolution.
Click to expand...
Click to collapse
For the Camera problem: Install the Cyanogenmod CameraNext.apk
GalleryNext
CM 11 Volume Mod attached below.

Is there a fix for YouTube app crashing when you try to watch a video?

Jacte said:
Is there a fix for YouTube app crashing when you try to watch a video?
Click to expand...
Click to collapse
idk, maybe if you learned how to search for youtube within Z's CM11 thread, you might have been able to find a link on page 35. But its ok, you're just like a lot of users who don't know how to use that simple feature known as a search bar.

palmbeach05 said:
idk, maybe if you learned how to search for youtube within Z's CM11 thread, you might have been able to find a link on page 35. But its ok, you're just like a lot of users who don't know how to use that simple feature known as a search bar.
Click to expand...
Click to collapse
I'm not one of those people you described, I searched on that thread but I didn't see because I was looking for Z's posts about YouTube problem. But thank you for information.
I downloaded that link, tried to install but I can't install it, It says "App not installed". How can I fix that?
I fixed the problem by renaming YouTube.apk in system/app folder and installing the new one. But there should be another, simple solution?
PS: Another question about that YouTube situation; the link that guy posted on CM11 thread is 5.2.27th version of YouTube, and I looked at "About" section of YouTube on my phone it says I installed 5.1.1.5 which is older. Why don't our phones update YouTube to latest version? Is this about the compatibility thing? Should we always follow the updates on somewhere else?

youtube
This might give some insight. My youtube has been working however ive never installed google play services even once, there may be a chance that gapps is causing the problem but i cant say for sure

hi kitkat user
could you confirm with this rom and last kernel that fonction bellow work fine (and without hang or problem when using it) :
- call (i think yes)
- sms
- gps
- video recording
- photos
thanls

However, after flashing his ROM, most of you will get a "Setup Wizard has stopped" problem. Here's the fix I found:
Click to expand...
Click to collapse
Another option would be, press top left, top right, bottom right, bottom left.
Setup wizard will quit.

Since i installed kk ROM in my atrix i didn't have troubles with my cellphone, the only problem came when i tried to download The gapps

J.M. Schatten said:
Since i installed kk ROM in my atrix i didn't have troubles with my cellphone, the only problem came when i tried to download The gapps
Click to expand...
Click to collapse
That's not a problem or a fix about the ROM....

palmbeach05 said:
That's not a problem or a fix about the ROM....
Click to expand...
Click to collapse
Well i have not found bugs yet... But i read about a lot of people who have bugs with the camera, WiFi or baseband or Radio... Maybe i only had a bit of lucky

Hi
My phone seems to be extremely sluggish when doing common tasks like opening or closing apps, opening app drawer, etc.
Also, any games I play on my phone seem to freeze for 0.5-3 seconds on touch input.
Is this a problem with my phone, or this ROM, or all CM ROMs on Atrix?

Send SMS
Hi There,
Is it only me or anyone else got problem when sending SMS? My Atrix on Z's KK is working great except the mentioned issue. I can receive SMS properly but could not send any SMS out.
Any helps would be appreciate!!!
Thanks.

txtsd said:
Hi
My phone seems to be extremely sluggish when doing common tasks like opening or closing apps, opening app drawer, etc.
Also, any games I play on my phone seem to freeze for 0.5-3 seconds on touch input.
Is this a problem with my phone, or this ROM, or all CM ROMs on Atrix?
Click to expand...
Click to collapse
Have you tried a different CPU governor? Or have you even unlocked the performance menu? There are some tweaks that you could apply and maybe you're missing them.

[Solved]
Hey guys, first of all, thank you Z and P! my atrix is now revived and I can enjoy it once more! what a great job. So far, really stable (although the screen don't light up until de end of some calls). Battery is doing great!
After some reasearch I found out I should be using the hporch32 recovery. Turns out I also needed to flash the hporch32 boot with "fastboot flash boot boot_olympus_kitkat_bigpart_hporch32_finalv2". I know it was silly, but the guides don't really cover this situation....
Anyways, thank you very much for this gift! Hope this helps other noobs!

leeco pro 3 x727 shuts down after few minutes

This happens only when I install any custom rom...the phone works fine with x720 5.8.018s version...anything apart from that device will shut down every 2-3 minutes ...very strange behaviour ...any one has any idea ?

any custom rom , android 6 or 7 , AOSP or stock based, it will boot fine and after initial setup , it will work for 3-4 minutes and then suddenly device shuts down. .. when i boot it up again , same thing happens, in one minute shuts down.
if i flash 5.8.018s stock rom , everything works fine....and it doesnt shut down...

After device bugs, my phone finally was restored into x720 stock ROM (i have x720). On boot it worked below 1 minute and reboots. I had to do clean data. Also booting x720 ROM into x727 is not too good idea. Maybe you should try to do more wipes?

marik1 said:
After device bugs, my phone finally was restored into x720 stock ROM (i have x720). On boot it worked below 1 minute and reboots. I had to do clean data. Also booting x720 ROM into x727 is not too good idea. Maybe you should try to do more wipes?
Click to expand...
Click to collapse
I did all the wipes i could , cleaned all kinds of data... it was US version 5.8.018s originally and i tried to flash Omni ROm first , and other ROMS , all had same issues, so i thought going back to the stock US rom , but since US version of 018s is not available anywhere, i went to chinese version , and it works perfectly , no reboot/shutdown...... I have used number of phones and installed 100s of ROMS , i have never faced soemthing like this...i hve even used leeco pro 3 before, with all custom roms and no problems.

Manan79 said:
I did all the wipes i could , cleaned all kinds of data... it was US version 5.8.018s originally and i tried to flash Omni ROm first , and other ROMS , all had same issues, so i thought going back to the stock US rom , but since US version of 018s is not available anywhere, i went to chinese version , and it works perfectly , no reboot/shutdown...... I have used number of phones and installed 100s of ROMS , i have never faced soemthing like this...i hve even used leeco pro 3 before, with all custom roms and no problems.
Click to expand...
Click to collapse
Ok update...i downloaded x720 021S and 023S and updated using in build update option..(local update) , and it worked, 23S is working without any shut down...so i guess, it is problem only with roms flashed thru TWRP

Manan79 said:
Ok update...i downloaded x720 021S and 023S and updated using in build update option..(local update) , and it worked, 23S is working without any shut down...so i guess, it is problem only with roms flashed thru TWRP
Click to expand...
Click to collapse
Usefull information, thank you very much.
Nearly the same problem here: My X720 is only rebooting sometimes, but more often switching off directly (vibrates one time and switches off). While the phone is in that status, the battery is discharging. I can only reboot the phone by holding the power button for about 10sec or to TWRP. Two times I was rebooting the phone and some (not all) settings were restored to default - reflashed the rom... Another time rebooting the phone it hangs in the booting display, did not get it booted completely again - reflashed the rom.... Very strange behaviour and don't know why this happens.
But for about the last month, the phone is only switching off and I can reboot and use it for an unspecific time.
That all happens with several ROMs - currently I'm on ResurrectionRemix 5.8.5. This is the most stable custom rom I have tested, but anyways the phone switches off in irregular periods. Sometimes the phone is about a day alive, sometimes only a few hours, sometimes below an hour. When I'm playing HQ games I think the phones switches off much faster, but not sure.
I'm also not sure - I do not have used the stock rom really long after I get this phone (was CN 5.8.018s I think) - but my feeling is, that the phone was definetely more stable with the stock rom.
Now after finding this thread, I will give the stock rom another try. Would you be so kind as to describe the process of going to the stock 023S a bit more in detail? First flashing the 5.9.021S for the x720 ROM throught TWRP and after that using the build in update option (rename file to update.zip into root folder)?
Thanks!

peed_neslo said:
Usefull information, thank you very much.
Nearly the same problem here: My X720 is only rebooting sometimes, but more often switching off directly (vibrates one time and switches off). While the phone is in that status, the battery is discharging. I can only reboot the phone by holding the power button for about 10sec or to TWRP. Two times I was rebooting the phone and some (not all) settings were restored to default - reflashed the rom... Another time rebooting the phone it hangs in the booting display, did not get it booted completely again - reflashed the rom.... Very strange behaviour and don't know why this happens.
But for about the last month, the phone is only switching off and I can reboot and use it for an unspecific time.
That all happens with several ROMs - currently I'm on ResurrectionRemix 5.8.5. This is the most stable custom rom I have tested, but anyways the phone switches off in irregular periods. Sometimes the phone is about a day alive, sometimes only a few hours, sometimes below an hour. When I'm playing HQ games I think the phones switches off much faster, but not sure.
I'm also not sure - I do not have used the stock rom really long after I get this phone (was CN 5.8.018s I think) - but my feeling is, that the phone was definetely more stable with the stock rom.
Now after finding this thread, I will give the stock rom another try. Would you be so kind as to describe the process of going to the stock 023S a bit more in detail? First flashing the 5.9.021S for the x720 ROM throught TWRP and after that using the build in update option (rename file to update.zip into root folder)?
Thanks!
Click to expand...
Click to collapse
On my equipment too !!

Andresdsr said:
On my equipment too !!
Click to expand...
Click to collapse
You do not flash a 21s update twrp that may brick you.
You have to go stock and flash with stock recovery.
Their threads already on this.
Sent from my LEX727 using xda premium

mchlbenner said:
You do not flash a 21s update twrp that may brick you.
You have to go stock and flash with stock recovery.
Their threads already on this.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
it was the same with the ROM that came from the factory.
I experienced 21s and 23s beta Tars, 23s original Chinese...

Andresdsr said:
it was the same with the ROM that came from the factory.
I experienced 21s and 23s beta Tars, 23s original Chinese...
Click to expand...
Click to collapse
Does anyone completely solved the shutting down issue on x720? I remember the same issue with the stock rom when i was getting the phone (5.8.018). but this rom could have been a shop rom, cant remember.
For me it seems that the issue happens more often whenever the phone uses more performance. Playing HQ games let the phone shut down after about 1-3min. doing nothing on the phone, it remains for about a day. Weird behaviour... will try to flash the stock recovery via fastboot and then a stock rom (no shop rom). hopefully it will improve the behaviour or even better solving the issue.

Sounds like a hardware issue. As for me, I have a couple of screen issues--I usually have my LeEco Pro3 Elite connected to a charger, and I sometimes don't use it for long stretches of time (say, 8 hours) because I have another phone as well. Once in a while, during those times the screen refuses to turn on. Sometimes the fingerprint scanner wakes it up, other times I have to straight up reboot the phone using the power button (I have to keep it pressed for two whole minutes for it to wake up the phone). Pretty annoying, dunno why it's happening. Could be a loose screen cable.
Now, if your phone is shutting down every few minutes no matter what, it could be a battery issue. I say this because I had a similar issue with an old iPod Color from 2005. The iPod would shut off every few minutes even when plugged into a charger. I changed the battery and it stopped shutting down.
Hopefully it's not a motherboard issue because replacing a phone's motherboard is never easy.
For me it seems that the issue happens more often whenever the phone uses more performance. Playing HQ games let the phone shut down after about 1-3min. doing nothing on the phone, it remains for about a day. Weird behaviour... will try to flash the stock recovery via fastboot and then a stock rom (no shop rom). hopefully it will improve the behaviour or even better solving the issue.
Click to expand...
Click to collapse
I don't think gameplay should affect the phone negatively at all. Especially a phone with a Snapdragon 821, a 14nm processor with efficient cores, for crying out loud. I play Fate Grand Order, a pretty intense 2D online game with 1080p graphics for 5 hours straight on my LeEco Pro3 Elite (Snapdragon 820) without it heating up at all.
Again, seems like a hardware issue because no phone with a Snapdragon 821 or 820 should be doing that. Especially while gaming.

sk8223 said:
Sounds like a hardware issue. As for me, I have a couple of screen issues--I usually have my LeEco Pro3 Elite connected to a charger, and I sometimes don't use it for long stretches of time (say, 8 hours) because I have another phone as well. Once in a while, during those times the screen refuses to turn on. Sometimes the fingerprint scanner wakes it up, other times I have to straight up reboot the phone using the power button (I have to keep it pressed for two whole minutes for it to wake up the phone). Pretty annoying, dunno why it's happening. Could be a loose screen cable.
Now, if your phone is shutting down every few minutes no matter what, it could be a battery issue. I say this because I had a similar issue with an old iPod Color from 2005. The iPod would shut off every few minutes even when plugged into a charger. I changed the battery and it stopped shutting down.
Hopefully it's not a motherboard issue because replacing a phone's motherboard is never easy.
I don't think gameplay should affect the phone negatively at all. Especially a phone with a Snapdragon 821, a 14nm processor with efficient cores, for crying out loud. I play Fate Grand Order, a pretty intense 2D online game with 1080p graphics for 5 hours straight on my LeEco Pro3 Elite (Snapdragon 820) without it heating up at all.
Again, seems like a hardware issue because no phone with a Snapdragon 821 or 820 should be doing that. Especially while gaming.
Click to expand...
Click to collapse
Thanks for the information.
Could be possible... If I'm shaking the phone like a cocktail-mixer, it feels something loose inside it and this could be the battery of course which could be not fixed correctly. But I am sure, that this issue has also something to do what is happening on the phone currently. Sometimes I am going to bed and the phone does not move for 8hrs, it simply lays on the table. In the morning, it is shutted down. Need to hold the power button for about 10sec to restart the phone (usually hold 2sec to power on). Sometimes (not really often) it warm-starts automatically.
I think this could be also a memory issue or internal storage. Yesterday I was playing a game (Bowling by Jason Belmonte) and after 3min, the phone hung up, display remains on, no reaction on pressing the hardware buttons, waiting 5min... nothing happens. So I pressed the power button 10sec, phone seems to reboot normally, but it take a bit more time in my oppinion. Now after entering the pin, some phone configurations were resetted to default, but not all. Playing this came, it sometimes happened, that the phone switches off (with one vibration). Rebooting with a 10sec press and it runs again normally. This time phone hung up and some configurations were resetted to default. WTF?
Today I have played Hmmsim 2. Phone hung up again, pressing the power button 10sec, phone begins to reboot, but rebooting never finished (waiting for about 1-2hrs). Long Press power button (10sec) to try to reboot again - same behaviour, never ending ROM loading screen. Wiped to factory via TWRP and the phone reboots again, but all configurations lost, like freshly installed rom. OK, whatever, using the google backup for apps and so on... when installing the apps in the background, the phone reboots about 3-4 times, app installations not finished. Cancelled and shutting the phone down to TWRP, where I am now...
What I will try to say is, that whenever the storage or memory is used to much or something like that, the phone begins with that behaviour.
And now I am thining about what to try next. I think I will try to flash the stock recovery via TOOL ALL IN ONE then flashing a stock rom like 5.9.023S.
I am still not sure of a hardware issue...

peed_neslo said:
I am still not sure of a hardware issue...
Click to expand...
Click to collapse
The easiest way to tell is if the issues were occurring before you flashed TWRP. Were they? This is why you always wait a couple of months before modding your device. Otherwise you'll be stuck in a loop of doubts. By this I mean you'll be convinced that the issue has to do with your custom ROM or kernel rather than your device's hardware, but you have no way of knowing for sure because you never used the phone enough on stock firmware.
I was like you... my unmodified Zenfone 3 had a screen flicker issue and a headphone jack issue that I was convinced was a Nougat problem. I upgraded from Marshmallow to Nougat immediately after getting the phone. After a lot of research and posting threads on the Zenfone forums, I realized I had a hardware issue on my hands. The screen had to be replaced for the flickering to stop, and the headphone jack had been gimped to 0.3v by ASUS for some reason. I quickly sold the phone and got my LeEco.
Here's a thread I made on XDA about my screen flickering issue. It's a hardware issue: https://forum.xda-developers.com/zenfone-3/help/ze552kl-screen-flickering-lowest-t3660643
I've learned some important things from that experience: it's easy for your brain to trick you into thinking you've got an easy-to-solve software issue on your hands, when in reality you've got a hardware issue. You need to start making arrangements for a replacement device and get video evidence of your problems to show to the seller ASAP. Because that behaviour isn't normal. Now I hope you do have a software issue on your hands that the stock firmware will solve, but who knows. Be prepared for anything.

sk8223 said:
The easiest way to tell is if the issues were occurring before you flashed TWRP. Were they? This is why you always wait a couple of months before modding your device. Otherwise you'll be stuck in a loop of doubts. By this I mean you'll be convinced that the issue has to do with your custom ROM or kernel rather than your device's hardware, but you have no way of knowing for sure because you never used the phone enough on stock firmware.
I was like you... my unmodified Zenfone 3 had a screen flicker issue and a headphone jack issue that I was convinced was a Nougat problem. I upgraded from Marshmallow to Nougat immediately after getting the phone. After a lot of research and posting threads on the Zenfone forums, I realized I had a hardware issue on my hands. The screen had to be replaced for the flickering to stop, and the headphone jack had been gimped to 0.3v by ASUS for some reason. I quickly sold the phone and got my LeEco.
Here's a thread I made on XDA about my screen flickering issue. It's a hardware issue: https://forum.xda-developers.com/zenfone-3/help/ze552kl-screen-flickering-lowest-t3660643
I've learned some important things from that experience: it's easy for your brain to trick you into thinking you've got an easy-to-solve software issue on your hands, when in reality you've got a hardware issue. You need to start making arrangements for a replacement device and get video evidence of your problems to show to the seller ASAP. Because that behaviour isn't normal. Now I hope you do have a software issue on your hands that the stock firmware will solve, but who knows. Be prepared for anything.
Click to expand...
Click to collapse
Thank you very much!
I am sure that the phone was doing the same on stock rom, but maybe fewer times. I have flashed a stock based rom now (Turbos mini 5.9.023s) and the issue still exists, but now the phone reboots normally more often than going into edl mode (emergency mode). I have found an old thread here on XDA and the issues described there sounds nearly the same. Finally the user in this thread also had hardware issue.
I believe also in a hardware issue, but I am still not sure. If I am looking to other threads regarding similar problems, there is always some regularity in the behaviour or the reported issues. In my case these rebootings (usual reboot or reboot to EDL mode) are definetely very unregular. On the TURBO Rom, these reboots happen definetely more often when the display is off and the phone sleeps. On the TURBO Rom, playing games seems to be helping lasting the phone a bit longer, the completely differnce to ResurrectionRemix Rom, where the phone was lasting longer when doing preferabely nothing. The issues are so inconsistant and this is making it hard to believe, that this is a hardware issue. Why the hell is the phone behaving different on every ROM - if it's a hardware issue, the occurred problems should have some regularity.
As I didn't have an OTA update option on the stock rom, I'd found out that this could be a "shop rom" (5.8.018), which is not the best choice nor for the first month(s).
I'm from Germany and I do not really want to return the phone to china or east asia for repairing (bought at banggood). This could take a very very long time. Changing to a new one could be also difficult because there are hardly any more devices out on the market and I need to return it for the change too.
But I am slowly at my wit's end and before these issues are making me more and more crazy, I will accept a problem with the hardware.

peed_neslo said:
I believe also in a hardware issue, but I am still not sure. If I am looking to other threads regarding similar problems, there is always some regularity in the behaviour or the reported issues. In my case these rebootings (usual reboot or reboot to EDL mode) are definetely very unregular. On the TURBO Rom, these reboots happen definetely more often when the display is off and the phone sleeps. On the TURBO Rom, playing games seems to be helping lasting the phone a bit longer, the completely differnce to ResurrectionRemix Rom, where the phone was lasting longer when doing preferabely nothing. The issues are so inconsistant and this is making it hard to believe, that this is a hardware issue. Why the hell is the phone behaving different on every ROM - if it's a hardware issue, the occurred problems should have some regularity.
As I didn't have an OTA update option on the stock rom, I'd found out that this could be a "shop rom" (5.8.018), which is not the best choice nor for the first month(s).
Click to expand...
Click to collapse
If your issues were occurring from the moment you got the phone, you know it's a hardware problem. Your seller sent you a defective phone and you should at least try fighting for a partial refund. If you paid through PayPal, open a dispute. If you paid with a credit card, ask for a chargeback. Now, the shop you bought it from might ban you for initiating a chargeback, but it's probably worth it. Or you could just cut your losses and move on. Maybe donate your phone to a dev who wants to try something crazy. :good:
I'm from Germany and I do not really want to return the phone to china or east asia for repairing (bought at banggood). This could take a very very long time. Changing to a new one could be also difficult because there are hardly any more devices out on the market and I need to return it for the change too.
But I am slowly at my wit's end and before these issues are making me more and more crazy, I will accept a problem with the hardware.
Click to expand...
Click to collapse
Oh snap, it's a Banggood phone? I bought my x722 from Banggood. No glaring issues other than the screen one so far, but this does worry me for the future. How long have you had it?
This is the problem with Chinaphones. They're cheap, they've got good specs, but you can't guarantee quality. Especially with now close-to-defunct brands like LeEco. If you're still okay with Chinaphones, get a Xiaomi next. Probably the most reliable Chinaphone brand out there, next to Huawei. And try to buy from an official source. I heard The Solution Shop in Europe sells Xiaomi phones for cheap (?). And always remember to record your unboxings and document all issues from now on.

sk8223 said:
If your issues were occurring from the moment you got the phone, you know it's a hardware problem. Your seller sent you a defective phone and you should at least try fighting for a partial refund. If you paid through PayPal, open a dispute. If you paid with a credit card, ask for a chargeback. Now, the shop you bought it from might ban you for initiating a chargeback, but it's probably worth it. Or you could just cut your losses and move on. Maybe donate your phone to a dev who wants to try something crazy. :good:
Oh snap, it's a Banggood phone? I bought my x722 from Banggood. No glaring issues other than the screen one so far, but this does worry me for the future. How long have you had it?
This is the problem with Chinaphones. They're cheap, they've got good specs, but you can't guarantee quality. Especially with now close-to-defunct brands like LeEco. If you're still okay with Chinaphones, get a Xiaomi next. Probably the most reliable Chinaphone brand out there, next to Huawei. And try to buy from an official source. I heard The Solution Shop in Europe sells Xiaomi phones for cheap (?). And always remember to record your unboxings and document all issues from now on.
Click to expand...
Click to collapse
Admittedly I'm not sure at all if this issue was already present after starting the phone for the first time. One of the first things I have done during the initial setup wizard was using the integrated data transfer app by LeEco (scanning a QR code with the old Xperia Z, downloading app to transfer data to the x720). This app establishes a Wifi direct connection between both phones to transfer the data like apps and other stuff. This transfer process takes at least 6-7 hours and during that process I am sure that the phone was not rebooting a single time. Maybe a specific app or background process of an app causes this irregular rebootings. I have not testet this. I have installed the most common of my apps also using different custom ROMs later.
On the current ROM (Turbos mini 5.19.023s) I have now looked into the last_kmsg.log file severel times after the phone was hard-rebooting (not to emergency mode - the phone is switching down to emergence mode really rarely since I have flashed the stock based ROM) to debug for a kernel problem and the power off reason seems to be ""Triggered from PS_HOLD (PS_HOLD/MSM controlled shutdown)". In the log file I could also find some "kernel panic" entries. So I have a little gleam of hope that the issue is not a hardware problem. I have to test a bit more with the stock recovery/ROMto gain a better knowledge of the issue. I think I will post this into the ROM topic to ask a developer.

sk8223 said:
If your issues were occurring from the moment you got the phone, you know it's a hardware problem. Your seller sent you a defective phone and you should at least try fighting for a partial refund. If you paid through PayPal, open a dispute. If you paid with a credit card, ask for a chargeback. Now, the shop you bought it from might ban you for initiating a chargeback, but it's probably worth it. Or you could just cut your losses and move on. Maybe donate your phone to a dev who wants to try something crazy. :good:
Oh snap, it's a Banggood phone? I bought my x722 from Banggood. No glaring issues other than the screen one so far, but this does worry me for the future. How long have you had it?
This is the problem with Chinaphones. They're cheap, they've got good specs, but you can't guarantee quality. Especially with now close-to-defunct brands like LeEco. If you're still okay with Chinaphones, get a Xiaomi next. Probably the most reliable Chinaphone brand out there, next to Huawei. And try to buy from an official source. I heard The Solution Shop in Europe sells Xiaomi phones for cheap (?). And always remember to record your unboxings and document all issues from now on.
Click to expand...
Click to collapse
Finally - I got it working without any problems now!
Happily it seems to be not a hardware issue. I have flashed the Grossoshop ROM and Recovery via a provided .bat file. This .bat file has flashed the recovery first via fastboot, then the ROM via fastboot. This Grossoshop ROM was based on 5.8.018s I think. Then I have updated TWRP Recovery to the latest version via TWRP itself (flashed the new image). Then I have flashed Mauro's 2.2 (which is based on 5.9.023s) and it is running great! Super performance, no extrem battery drain, no reboots, all is working (except the chinese design downloads as I cannot create a Leeco account from Germany). But now I'm satisfied. :good::laugh:

peed_neslo said:
Usefull information, thank you very much.
Nearly the same problem here: My X720 is only rebooting sometimes, but more often switching off directly (vibrates one time and switches off). While the phone is in that status, the battery is discharging. I can only reboot the phone by holding the power button for about 10sec or to TWRP. Two times I was rebooting the phone and some (not all) settings were restored to default - reflashed the rom... Another time rebooting the phone it hangs in the booting display, did not get it booted completely again - reflashed the rom.... Very strange behaviour and don't know why this happens.
But for about the last month, the phone is only switching off and I can reboot and use it for an unspecific time.
Thanks!
Click to expand...
Click to collapse
My x720 has done the same to me a couple of times now, Vibrates once and turns off and I have to hold the power button for a few seconds longer to turn it back on again which is odd.
The battery was charged over 50% % 70% at the times it happened and I wasn't even using the phone, It was just sat on the table in front of me.
I didn't have any problems at all until a few days ago when it first shut down.
I'm using Oreo - AICP 13.1 from here - https://forum.xda-developers.com/le-pro3/development/rom-aicp-13-0-pro3-aka-zl1-x727-x720-t3698058
The problem now is I don't know where to start troubleshooting When I get time I am planning on a clean wipe and fresh install of AICP again to see if that solves the problem

When using this ROM does your phone heat up a lot.
Sent from my LEX727 using xda premium

Did you manage to fix the problem somehow?