Related
Important - Read First!
First of all you must know that everything you do is on your own risk. Your device was not designed to run GNU/Linux or Android and that's why you shouldn't expect everything to be perfectly safe. If you don't want any troubles then simply don't tamper with your phone. On the other hand, installing Rhobuntu is probably less dangerous than installing alternative ROM's, because it doesn't touch your ROM and runs completely from the SD card. If something goes wrong and the system would hang up, you always can remove the battery and boot into Windows Mobile. Still, we can't guarantee you anything and we won't be liable for any damage that might happen to your device. If you don't accept this, don't install Rhobuntu.
At the moment two problems are known to occur when using Rhobuntu. They are, however, not Rhobuntu specific and may also occur when using Android.
1- After booting back into WinMo, you can't install or run unsigned apps. This problem probably has something to do with the way haret kicks WinMo out of the RAM. It also seems to occur only in combination with the use of Exchange Server. The only known solution at the moment is Hard Reset. Some users also reported that it can be fixed by using Visual Studio 2008. Check out this threads:
o Not digitally signed with a Trusted certificate/ Activesync keeps UNINSTALLING!
o Program... is not digitally signed with trusted certificate. HELP!
2- Since we still have no proper battery charge indicator working, you might not notice that your battery is completely drained. Deep discharge is, however, not good for batteries and may in some cases even damage them. Here is a thread dealing with this problem when running Android
o Android killed my USB connection, please help
The majority of Rhobuntu users doesn't face these problems, but just in case, you've been warned.
WIKI http://wiki.xda-developers.com/index.php?pagename=RhodiumUbuntu
WEBSITE https://sites.google.com/site/rhobuntu/
This build by Walter79 and the Rhobuntu team:
Rhobuntu 9.04 19.09.2010
changelog:
- zimage update (Xandroid Build 16/09)
- sphone 0.04 (thanks AmiPro)
- 3G scripts update (thanks AmiPro)
- sound works partial (thanks to phhuson) !!! run /sdcard/ubuntu/playwav2 after boot !!!
- alsaplayer added
Download:
Link1: http://www.megaupload.com/?f=RWDJWUN0
Link2: http://rhobuntu.4shared.com
Debian Squeeze Test 19.09.2010
For more information please look at this post http://forum.xda-developers.com/showpost.php?p=8186181&postcount=1208
Download:
link1: http://www.4shared.com/dir/n-2ObqP_/pro2-debian.html
Old Build (27/06/2010)
*http://www.megaupload.com/?f=RWDJWUN0
*http://rhobuntu.4shared.com
Old Build (13/05/2010)
*http://www.megaupload.com/?f=RWDJWUN0
*http://rhobuntu.4shared.com
Old Build (14/04/2010)
*part one:http://rapidshare.com/files/375930803/Jaunty_14_04_2010.7z.001 MD5 77430e728bb17277e671cc55ae03161f and part two: http://rapidshare.com/files/375939439/Jaunty_14_04_2010.7z.002 MD5 523589000dcd5d1dcea668bbe51253af
* http://rhobuntu.4shared.com
* http://www.megaupload.com/?f=RWDJWUN0
Old Build (11/04/2010)
* http://rs427.rapidshare.com/files/374730149/Jaunty_11_04_2010.7z
* http://rhobuntu.4shared.com
* http://www.megaupload.com/?f=RWDJWUN0
Old Build (10/04/2010)
*http://rapidshare.com/files/374138895/Jaunty_10_04_2010.7z
*http://rhobuntu.4shared.com
Pretty cool idea, keep us posted!
Definitely an awesome idea, and one I had been thinking about myself since my original Touch Pro days. An embedded version of Linux should run great on these devices. Hopefully momentum will grow surrounding this.
thats very interesting. any pictures of this running? maybe things can be pulled from android.
THANKS!!!! downloading now!
tried it on my Touch Pro 2 (AT&T Tilt2), No luck. Started to boot, Complained about /etc/init then poof reboot after 7 seconds. Am I missing something.
aq3e said:
tried it on my Touch Pro 2 (AT&T Tilt2), No luck. Started to boot, Complained about /etc/init then poof reboot after 7 seconds. Am I missing something.
Click to expand...
Click to collapse
Did you change the mtype in the sartup script to the tilt2, the one i used is set for the rhod100, i hope that helps. Is anyone else's not working btw?
Help!
I extracted all the files on to a newly formatted 2GB card.
Ran haret and everything ran fine. Bit 'interesting' navigating round the screen but got there in the end.
However, since rebooting my phone back into WM I cannot run any unsigned programs such as haret that worked fine before.
The error says "The file blah cannot be opened either it is not signed with a trusted certificate..."
Any idea what's changed and how I can get my phone back to how it was?
R.
dicko99 said:
I extracted all the files on to a newly formatted 2GB card.
Ran haret and everything ran fine. Bit 'interesting' navigating round the screen but got there in the end.
However, since rebooting my phone back into WM I cannot run any unsigned programs such as haret that worked fine before.
The error says "The file blah cannot be opened either it is not signed with a trusted certificate..."
Any idea what's changed and how I can get my phone back to how it was?
R.
Click to expand...
Click to collapse
Wierd, my winmo works find, minus the calibration issue, it's brilliant, we need some linux Devs to look into this. as a windows user, i have no idea on what to do
Thanks (All we need now is win XP )
Badwolve1
I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.
dicko99 said:
I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.
Click to expand...
Click to collapse
did you install anything recently, could try uninstalling it
dicko99 said:
I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.
Click to expand...
Click to collapse
try installing SdkCerts.cab
http://forum.xda-developers.com/showthread.php?t=554240
the cab is included with the rhodium keymapper zip file. (keymapper app is worth installing as well )
sdkcerts won't install. It has the same problem as other cabs where it prompts to say the program is from an unknown publisher and when I tap Yes to continue it still fails with "Installation of SdkCerts.CAB was unsuccessful."
Tried booting it up on my Verizon TP2 and all it does is run haret and then freeze.
Thanks for putting this together, sebbo90. It boots nicely, and actually performs quite well on my Tilt2. I hope some of the developers take notice of this project and consider fixing the major usability issues like the front keys and the display calibration.
After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.
spdweb said:
After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.
Click to expand...
Click to collapse
How did you even get it to boot?
EDIT: Do you think it will not boot for me since you all are using GSM and i am using a CDMA phone? Some settings may need to be changed i guess. I have been messing around but no luck.
spdweb said:
After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.
Click to expand...
Click to collapse
I had this problem what i did to fix it was to was to do a full reformat on my sd card (not a quick one) this then helped and now it boots everytime. Hope this helps
sebbo90 said:
Did you change the mtype in the sartup script to the tilt2, the one i used is set for the rhod100, i hope that helps. Is anyone else's not working btw?
Click to expand...
Click to collapse
If the mtype needs to be changed, what should it be instead of the default 2292, forgive my ignorance.
EDIT: must be a fluke, it booted now, did not change a thing. Re-extracted the ubuntu rar and shoved it back on the SD and booted. Great Job. All we need now is calibration to get started.
sebbo90 said:
I had this problem what i did to fix it was to was to do a full reformat on my sd card (not a quick one) this then helped and now it boots everytime. Hope this helps
Click to expand...
Click to collapse
I got it working now. It was the directory structure I was using. I spent about 2 hours last night working on the calibration issue. If I could get that working it would be sweet. Tried a newer version of haret and tweaked the startup.txt a bit but the calibration still goes out of range.
On a brighter note, the calibration works fine when booting xdandroid with haret though it is a manual calibration there is hope anyway.
Hi XDA geeks , pros and fans !
I'd like to start this new threadline concerning the freshly-appeared TCT MOVE handheld device marketed for the budget segment.As i understand it appeared in march or later this year and has quite good specs for the approx. 100 euro category.
Some details can be found on
http://alcatelonetouch.com/products/smartphones/move
Contrarily to some beliefs IT IS NOT a branded OT-908 ,rather a cosmetized one .It comes in black or silver / white , a bit heavy for it's size , and higher specs than the OT-908.
Concerning the hardware specs, i'll be coming back later with some accurate chipset and sensor details.For now
OS is Android Froyo v2.2.2.Looks like there will be official ROM updates,at the time being there is the OneTouch Upgrade v1.2 ,which downloads about 540 Mb chunked firmware files, and exits with error.
Memory is 512 Mb RAM , for user space is available about 300 Mb
512 Mb ROM flash, available to user about 160Mb.
SD card slot supports up to 32Gb MicroSD, the phone comes with a 2Gb one.
Camera is a 2.1Mpixel one.There is no secondary one,but the main camera is available for video calls,with Yahoo! Messenger i tested it myself.How to use it this way i will explain later.
GPS is amazing , if assistance software is used , the lock-on takes only seconds.
Sensors - linear acceleration sensor
- 3 axis orientation sensor
- 3 channel magnetic field sensor (digital compass)
- light sensor for illuminance detection
- optical proximity sensor , it seems not in use by operating system(or rather poorly)
Processor - 600 MHz Qualcomm ARMv6 compatible, min frequency is 122 Mhz, and deep sleep capability.Qualcomm MSM 7627 chipset
rooting ?
hi djada80.i should like to ask if you managed to root your phone ?
Yeah , it's quite simple.There are in the Android Market some free apps , i think the best which i also use is the one named Ginger Break.Just download and install it.Detailed usage info can be found here
http://forum.xda-developers.com/showthread.php?t=1044765
firmware upgrade
it seems that the branded ones somehow cannot be upgraded ! at this point i need assistance , so PLEASE , if there is anybody experienced in debranding Acatel smartphones, then YOU ARE MOST WELCOME !.I saw guys having problem with debranding T-Mobile Move , so let's DO IT !
cannot sync with windows
i cannot sync my tmobile move with windows.have a toshiba satellite c665 with win 7 .pls help !
connect phone to computer,enable usb tethering.install alcatel android manager on computer. Can be found here
alcatelonetouch.com/contents/download/T-Mobile_AndroidManager_2.2.1108.1645.rar
This should work,instead of Android Sync Manager WiFi ,the last has some issues with this phone ,do not use it.
Yahoo! messenger front camera
Contrarily to some beliefs THERE IS POSSIBLE TO MAKE VIDEO CALLS with front camera only on Froyo 2.2.It is quite simple:
1.) if you have any version of yahoo apps , remove them all
2.) install Y!Messenger v1.3.2 , the afferent audio and video plugin and
optionally Y!Mail v1.3.2
Nothing fancy with it , just works.Remember, DO NOT UPDATE from Market.
Might also check this,if it doesn't work
http://forum.xda-developers.com/showthread.php?t=1087769
remove bundled apps ?
Hi !
Is there a way to remove some of the unnecessary factory shipped apps ?
RE
Yes , there is. So the smart method vould be to remove them from phone memory , and eventually install it on SD Card , if they are (and they are) UNMOVABLE.
Or just leave them ,anyway a factory reset will restore all the shipped applications.
1.) [optional] install Android SDK with platform 2.2 , sdk tools and eventually drivers.Enable USB debugging on device.On PC launch command prompt and change directory to \Android\android-sdk\platform-tools\.Run command
adb shell pm setInstallLocation 2
This enables SDCARD installation by default.Prerequisits to have ROOT ACCESS.
2.) with RootExplorer simply delete unwanted applications from \custpack\apps\ on device.Optionally you can make backups.
3.) if you made backups , the backed-up apk can be used to be reinstalled , NOW ON SD CARD
Good luck.
RE again
A reboot of the device is required to cleanup the junk after a forced delete.Or it can be done manually , BUT USE CAUTION.
i have an alcatel move branded Cosmote Move, i like this phone very much but i`ve managed to brick it the second time, first time i bricked and took it to waranty, they reinstall the software free of charge, now it has the same simptoms (pass the carrier logo and get stuck to carrier animation) and i need to send it to waranty again. i dont manage to get it unbricked. i`ve root it with gingerbreak but this phone doesnt go to recovery mode. i`ve searched the internet and google it for hours, but nothing.
if anyone knows how to do it please tell me, in the user manual says hard reset vol - and power, get stuck whit touch buttons light up and screen black!!
thanks in advance
re Themaster
it's not a brick yet i suppose , though you didn't specify how you managed to "brick" your phone.a nice clean reflash would solve the problem , probably you deleted some system files while in root mode.again did you use root explorer or something similar ?
try a factory reset as it follows:
1.) turn off the phone
2.) press vol up and the power on and hold the buttons pressed for about 1 minute
3.) the phone boots up , android logo appears and then an animation with some sort of thrashcan or whatever
4.)wait until it finishes , then the phone shuts down automatically.power on the phone and it will be restored
Beware ,battery must be at least 70 % charged or kept in charger , NOT USB connected to PC.
This restores phone to factory state , but not all the applications from /custpack/apps
Best regards !
Useful Key Combinations
These keypress modes apply on a shut down phone
Hard Reset - reinstalls android core system from ROM , deletes user data and misconfig
key combo : vol up + power on long pressed until trashcan animation appears
Flash Mode - used for ROM update , useless momentarily
key combo: vol down + power on long pressed , black screen appears and touch buttons lit up
Root access , mount filesystem with root access ,DANGEROUS !
key combo : home + power on long pressed until boot
build environment under Ubuntu
Lately, there has been some problems setting up an Android build environment under Lucid Lynx, as i've seen many have been complained for the missing java5 jdk.
For Romanian users: seems to be a problem with the Romtelecom DNS servers , when adding Jaunty or Dapper repositories to Lucid.
Use Google DNS as alternatives 8.8.8.8 and 8.8.4.4.This works.
From what I've been able to determine. The move and 908(s) are the same hardware with with only cosmetic differences. Something is different in software, I've been unable to root my 908s with ANY tools I've found.
I was also unable to use ADB under windows. The handset apparently requires four drivers, I was only able to find three of them. I got the Alcatel tools to work, as well as tethering, but no ADB. i didn't have any such issues under Ubuntu, but without root it isn't helpful.
I could not locate a stock rom or source anywhere on the Alcatel sites, so I sent a GPL request, i'm waiting to hear back.
UPDATE
After a long night I managed to root my 908s. I'll write out the jist of it, but I was flying by the seat of my pants, fueled by caffeine and sleep depervation. DON'T consider this a HOWTO.
First off, to the best of my knowlage there is no one click solution as of yet. As I said before still missing the driver that makes ADB work in windows, and handset based solutions didn't pan out. A little reasearch showed that the OT-990 has the same chip/ram and ROM space as ours. The screen is bigger, and I don't know what board is in it, but on a hunch I figured it was close enough. So I went here: http://forum.xda-developers.com/showthread.php?t=1164391 in the hopes that some sort of combined effort in future ROM development would be possible.
Yes that's right folks its a guide to MANUALLY root you handset with ADB. So not for the faint of heart. I didn't have high hopes, as issuing ls -l on either the sqlite folder or data threw a permission denied. So blindly I tried to push psneuter, busybox and su to /data/local. I almost fell off my chair when it worked! from there I used psneuter to get ADB into root, and managed to get the su binary to /system/xbin, and Superuser into /system/app. Superuser was installed, but still no root. So I checked out Root Checker to see what was going on. There are three places that su typically lives; /system/xbin, /system/bin, and /sbin. So I tried to put su in those folders. I got it into /system/bin but sbin is mounted read-only. I did not remount any directories, as the instructions are lacking syntax (I'm a little rusty with advanced mounting commands). I think things are mapped a little differently anyway. I still did not have root on the handset, so I then fired up Superuser to see what it could see. It saw the su binary, even though it wasn't working right. Then I thought well if it can see it, then maybe it can update and fix it. Sure enough after running the update to su in Superuser, (drumroll please...) I had working root.
So that's my story so far, I'm gonna give Alcatel a week or so to reply to my request. Then we'll take it from there. (Hey it worked on Huewei right?)
If a real dev should come across this, feel free to jump in. Its a solid little phone and has the potential to work on a range of handsets.
Gratitude
Thanks snkiz for your attention ! I am pleased that someone 'heavy' noticed my efforts of dedicating this threadline to the newcomer ! Indeed a small little phone with potential , maybe in time we get it gingerbread , cupcake ( or whatever ),even wm6.5 or 7 ...
As of ADB drivers , i had ADB from the first by these steps:
1.) http://www.alcatelonetouch.com/contents/download/move upgrade 1.2 Setup.rar , package contains the drivers
Now i noticed that when i try firmware upgrade , the utility downloads about half a giga of *.bin files and then exits with 'download failed error'.
2.) installed Android SDK , platform tools and Google drivers (i am not sure if necessary), the 2.2 platform (api 8)
Under Win7 cmd in platform tools , adb shell , su and on device pops up 'unknown has been granted superuser rights' and voila! in cmd shell i have '#'.Previously installed Gingerbreak.
My device is a Cosmote Move.
Ya, no I got that file too. I think they are "consumer drivers" because like I said I got all the Alcatel tools running but on my win 7 one driver was still missing, and I have pretty good googlefu. effin hate windows, this is why. I'm by no means a "heavy" but I am comfortable in a Linux environment, that helps alot. As to you being able to get gingerbreak to work, i'd bet that comes down to carrier firmware.
---------- Post added at 06:53 PM ---------- Previous post was at 06:39 PM ----------
djada, seeing as your the op could you please re-tag the thread with the model numbers to make it easier to find? cosmote, 908, 908s, and qualcom should do.
perhaps a mod could move this thread to the android hacking forum where it can get the proper attention please?
ADB driver
Driver files are from WHATEVER.\android-sdk\extras\google\usb_driver\ , if does not install automatically , can be forced.Anyway Win$ux 7 detects ADB interface , installs some sh.t from windows update server , and you'll have an ADB interface in Device Manager (working or not).Try to force the google drivers.
On the other hand ,i'm sorry but dunno how to move the thread , maybe i should start a new one in
http://forum.xda-developers.com/forumdisplay.php?f=565&order=desc&page=552
Just looked at it and they don't have Alcatel
Mod
Just started workin on a Cyanogen build , if i manage to build at least a kernal img , maybe i can lure in the Koush guy from github.We are in need of flash , backup , recovery tools.Not as lucky as the Samsung or HTC guys ...
AS ALWAYS I AM NOT RESPONSIBLE FOR WHAT YOU CHOOSE TO DO WITH YOUR PERSONAL DEVICE, PERIOD.
Battery Calibration and Other Tips from RealPariah
To save space on the post I am moving to spoiler type Q/A. Just click the SHOW CONTENT button for a given guide or answer to show the related information
Folks seem to keep asking a lot of the same questions so I have begun this thread at first to answer the Battery Calibration [Manually] and now I am going to keep adding things I find users keep asking about. Hopefully this will help alleviate the Dev Threads and please feel free to Link here in ROM directions I will try to break up things in to posts so you can link to a certain post for a certain item.
RealPariah's Manual Battery Calibration Methods
First is just whenever; Below that will be how to calibrate on flash of new ROM.
When I talk of charging it is highly highly recommended you use the AC adaptor and charge with phone off for absolute best results.
Calibrate Anytime
[Reminder: To save space on the post I am moving to spoiler type Q/A. Just click the SHOW CONTENT button right below to see the steps in battery calibration]
-> Charge phone to 100%
-> Restart phone [to be sure it isn't off by some amount (if phone off just unplug AC adapter for 30 secs and plug back in)]
-> Wait 20 min after you are sure it is 100% (phone should stay plugged in)
-> Boot in to recovery
-> wipe battery stats (advanced)
-> Get ready to pull battery and unplug phone and do so after the screen goes black after tapping restart device (pull AC adaptor first)
-> Wait 30 seconds and replace battery
-> Allow phone to boot
-> run through ENTIRE CHARGE (COMPLETELY DISCHARGE) the battery (whether normal usage or looped media files whatever you have time for)
-> restart phone to be sure it is totally dead
-> Charge fully one more time
You should be good to go!
Just remember it may take several days for phone to generate statistics and for this to fully settle in.
Calibrate Battery at ROM Install
Just be sure your battery to 100% as above and wipe battery stats right before you flash ROM zip.
Then be sure to fully kill the device and do one full phone off charge
You should be good to go!
as above it takes several days for battery stays to fully generate and settle in!
Hope they helps, and in my multiple tests seems to really make sure you get best performance!
Device: Samsung Tmobile S2 [SGH-T989]
ROM: Paranoid Android 2.52
Tweak Script: Newest Supercharger V6 with modified services.jar+KaK+3G Turbo Boost
Battery Calibration and other USEFUL ANDROID INFORMATION as answers to repeated ??s
JB AND ICS ROM Installation Procedure [or any ROM really]
**If You Follow the steps below it should clear any residual files and should leave you with a totally blank slate for the ROM to install on. So, be sure to do Nandroid and/or Titanium Backup as your scenario dictates**
First, to be thorough you should have 100% battery before flashing for best battery life.
Supplies:(links will be added)
Darkside Cache Wipe [OPTIONAL]
Darkside Super Wipe Script[Optional if using CWM more mandatory if using TWRP but it can be optional]
Kernel Cleanser Script [Very optional and only needed if you change kernels a lot and worry about residual files really]
Fix Permissions V2 by Minotauri Zip [yes v2 and v3 are different get v2]
Fix Permissions V3 Zip [edified again by Minotauri] [OPTIONAL]
*NEW* SEE Section BELOW INSTALL STEPS FOR HOW TO CHECK A ZIP FILES MD5 Signature via an ANDROID PHONE
ROM Installation Guide
Download The ROM of your choice using your WiFi Connection or Transfer it from your computer. Do not use the cell data connection [E, 3g, 4g] as there are more errors in data downloads this way. Also, some users report that they get the best results when they save the things they flash to their External SDCards. Myself, I use either the Internal Storage [EMMC] or the External SDCard interchangeably.
Reboot Phone in to Recovery
Choose Wipe Dalvick Cache [Advanced Menu]
Back at Main Menu, Tap Mounts and Storage
Tap to Wipe /cache /data and /system [Do each twice in a row]
Back at Main Menu Tap Install From SDCard and choose where you saved the kernel cleanser script and tap it to flash it [I suggest 2x again]
Do same thing for Darkside Superwipe Script [2x]
Restart Recovery [Advanced Menu]
Install From SD choosing your ROM zip file (just as above script zips)
Restart Device and allow to boot [skip account setup for now if it prompts we'll come back] wait 3 min from initial lock screen if unsure.
Restart in to Recovery
Clear Cache [Main Menu] and Dalvick Cache [Advanced Menu]
*(NEW) You can use Darkside Cache wipe here you should not need to clear any caches or to run fix perms separately if you flash Darkside cache wipe skip the above line, flash add-ons as stated in line below AND THEN flash darkside cache wipe (you can manually also skip cache wipes until after add-ons are installed the point is you clear both caches [before or after add-ons] and fix perms AFTER installing everything so adjust according to your tastes
Install any add-ons like super user, toggle zip installing custom radio and kernel last in that order [if nothing to add no worries that's cool]
Install From SDCard and find Fix Permissions v2 and flash it
or if you wish substitute Darkside cache wip here again subbing out the line right above this text
Restart Device and allow to boot [we cleared Dalvick Cache so yes it will be another longer boot]
You are done [unless you choose to fix ROM Manager so it doesn't freeze partially through fixing permissions while OS is running, but totally optional] Skip to Notes below and onward if not wanting ROM Manager fix
[OPTIONAL For ROM Manager FIX]
Once phone boots install [if it was not already apart of the ROM] ROM Manager [Premium License install will not affect anything do it now or later either way works]
Restart Device in to recovery
Flash the Fix Permissions V3 [YES VERSION 3 THIS TIME (Won't be needed again after this unless you install a new ROM, or uninstall ROM Manager when you re-install run this again) Just Like you installed the Zips above]
Once Done, Restart Device and let it fully boot and settle [give it 10 min after seeing initial lockscreen if unsure]
Open ROM Manager and Tap the Fix Permissions shortcut and let it do it's magic and it should not freeze on you now [best practice is to keep screen on in ICS it appears ICS sleeps deeper than GB and some apps haven't corrected for this so they stop processing just because device is in deep sleep not because the script is in error!]
DONE, Notes:
This method seems to ensure the best installation of ROM with least chance of cross contamination from the previous resident. I do find rarely even with this method I have to do this whole thing 2x in a row. This can happen when the data is transferred to the phone during install even if you do everything right. Once you run through it once or twice it gets easy and just throw those scripts and current ROM zip on Internal Storage if you find flashes from there work for you, because you should NEVER format EMMC [Internal Storage] as this will brick your phone [recoverable if you send it to Samsung or buy a $150 box and take your phone apart to connect it up [or if lucky know someone you trust that has one]]; and therefore as long as you have that and access to recovery you can flash your phone.
New Addition 2012.07.10
UPGRADING YOUR ROM WITHOUT WIPING USER DATA AND APPS!
This can only be done when upgrading from a previous to a new version of of your current ROM OR if you go from a ROM's base to the ROM [ie Paranoid Android is based on CM10 and you should be able to install Paranoid if you have CM10 without formatting your storage. This does also include how many changes exist between your current version and the one you are installing [ie you have Paranoid 2.2 installed and you try to install 2.52 you are more apt to have issues and/or errors than if you went from 2.51 to 2.52, so I can't account for EVERY scenario, use your best judgement please]. If this is your FIRST FLASH OF CM9 FOLLOW ABOVE INSTRUCTIONS AND USE TITANIUM BACKUP OR LIKE APP TO CARRY OVER USER APPS ONLY!
*BEFORE THE POSTING BEGINS YES I HAVE TESTED THIS USING NIGHTLY BUILDS AND HAVE DONE THIS OH ONLY ABOUT 12 TIMES IN THE LAST 14 DAYS! IT WORKS EVERY TIME!* I have also done this with both Clockwork Recovery 5.0.2.7 AND Clockwork TOUCH RECOVERY 5.8.1.3. I have not tried and will not risk using the Open Source Recovery [you can tell you are using it if the touch buttons are up and down and the enter key on the bottom of LCD screen and Clockwork Touch is the one the menu options themselves are tappable [If not sure install ROM Manager and have it install one or the other]]
Supplies
---------
** = Required
* = Optional
[/I]** You can use ROM Manager to Download the ROM file just don't have it start the flashing process automatically.
You can also visit Cyanogen Download Page
If you Happen to use the T-Mobile Galaxy S2 so do I so here is a direct link: Cyanogen T-Mobile S2 Download Section
** GApps
Click the top-most link labeled for CyanogenMod 9.0.x in the table at top of the page
* Chainfire SuperSU
I recommend Chainfire SuperSU as opposed to Original SuperUser included in CM9. It has some extra features, and its binary has been built better soo far. Well, Original Super User USED to Seg Fault All over ICS, but that has been fixed in the newest release. Chainfire has been built MUCH more recently geared towards ICS moreso [it works in Gingerbread just fine too] so I have stuck with it. If you like it PLEASE donate by buying SuperSU Pro on market. It is not my product, but it is well worth checking out and donating to if you find it useful.
Upgrade Guide
NOTE: It usually takes until AFTER the SDCard checks run through [2 if you installed ext SD] before the cell data even starts to connect, be PATIENT. If you have BEEN PATIENT AND ARE SURE THE RADIO IS ACTING UP FOLLOW ABOVE INSTRUCTIONS TO FLASH A ROM FROM SCRATCH [I recommend Paranoid Android].
Upgrading From a previous CM9 version to a Newer one
Gather the files you downloaded above and throw them on either your internal storage or your SDCard either will do just fine, just make 'em easy to find.
Don't forget to run the MD5 check as explained BELOW to ensure no data corruption during file download if you choose to do so.
FIRST RUN A NANDROID BACKUP [boot in to recovery, and use the backup feature provided in Recovery Menu] Step-by-Step Procedure on that coming soon . Of course, if you are an advanced user and do not feel this is needed then skip it, but if not is saving a few minutes skipping it worth rebuilding all your apps and settings if something goes wrong? You decide ...
Boot In To Recovery [Hold middle of Vol buttons so both are in while powering on and release them as soon as you see first Samsung Logo]
Now This is the order I do things, if you are comfortable or as you get comfortable you can change up exact order
Clear Cache [Main Menu]
Clear Dalvick Cache [Advanced Menu]
Now You can either go in to Mounts and Storage and Format the System Partition for a safer flash [I found not doing this on some Nightlys caused the touch screen to stop responding a lot, now that does seem to be fixed, just noting this incase you start wondering why the power, and vol keys work but the screen stops paying attention to you and how I fixed it go back in to recovery Wipe Storage and flash again from start [meaning dont skip re-flashing the following things as mentioned]]
Go to Install Zip from SDCard and Navigate to the CM Nightly you downloaded and flash it [remember to choose internal storage or SDCard as it applies to where you saved the files
WITHOUT RESTARTING
Install Zip and Now choose the Gapps zip [no worries your account info is retained but still flash it or Market and other Gapps will fail to work]
WITHOUT RESTARTING
IF you CHOSE to use Chainfire; Install Zip and Now choose the SuperSU zip
Now Run Fix Permissions [in Advanced Menu] IT WORKS FROM RECOVERY WITHOUT A FLASH PACK WHEN USING CM Based ROMs! [When they are installed to begin with if this is your FIRST CM flash then it still will bomb out and not run right] You can also skip this again if comfortable doing so
Once you are done those cache wipes and installs now Restart...
Be patient as anytime you wipe the Dalvick Cache you are on the hook for a LONG boot [~5 min]
Once the OS loads and you give it the 10 min to settle in and setup stats and all that background stuff [again use your judgement if comfortable skipping this]
Be sure to Open SuperSU from App Drawer and tap the button to update the binary when the pop-up prompts you to do so [if you did decide to use it]
Now you are good to go!
Now, THIS WAY you don't have to restore any USER APPs OR DATA [if you didn't wipe System before flash MOST of those settings should remain as well] and you only have your system settings to worry about!
--------------------------------------------------------------------------------------------------------------------------------
How To Run MD5 Check on Downloaded Zips Before Flashing
Screenshots will be added also (please bear with me as I have time). This will be via phone so it helps the most people it can I will add a Windows version as well soon, but this will work even if you have no computer.
Supplies and the Basics
An Android Phone
An MD5 checking App [I will use Android File Verifier (AFV) which is free and available on market and free]
A Zip to verify and
a known MD5 number for the zip [usually posted as a line of text with zip (something like MD5: MD5-NUMBER-WHICH-IS-MIX-OF-LETTERS-AND-NUMBERS (Hexadecimal) in thread near download zip [or sometimes changelogs] just copy it to a text file or bookmark thread to refer back once we generate the MD5 signature on the file when we complete downloading it.
Checking a Downloaded Zip's MD5 Signature on an Android Device Guide
[ANY ROM doesn't need to be specifically Gingerbread or ICS]
-> Download Zip you wish to check to some form of storage [Internal or External SD or even USB drive if you have USB host support and adapter doesn't matter where as long as you have enough storage to store the downloaded file.
-> Open Market and Install Android File Verifier [AFV]
-> If first install of AFV then click on return button on pop-up to see main window
-> Now, tap Select File and navigate to where you saved your zip
-> LONGPRESS the zip file [or any really] you want to check and choose calculate MD5 signature from the menu
-> Wait while it calculates the MD5 signature [this takes roughly 2 min with a 275MB ROM zip]
-> Once it is done you will see pop-up stating it is done, what the MD5 is and if you hit return the main window will now list the last checked zip's location with its MD5 checksum. The App also auto copies the number to your clipboard meaning if you saved the OPs MD5 in to a text file you can re-open it hit enter for a clean line, longpress screen and choose paste and it will paste the MD signature there for you to verify together with original signature.
-> You can go back and hit select file again and repeat for any files you would like and AFV supports following file signatures [incase OP likes to use more accurate checks [the longer the signature the more thorough the check, but also the longer it takes to process a file and generate that check]
AFV Supports FOLLOWING FILE SIGNATURE FORMATS:
* MD-5
* SHA-1
* Jar signing
* Verify Nandroid [MD-5]
* SHA-224
* SHA-256 [what I normally use to generate signatures when I release zips as it is more thorough than MD-5]
* SHA-512
Device: Samsung Tmobile S2 [SGH-T989]
ROM: Newest Paranoid Android [Currently 2.52]
Tweak Script: Newest Supercharger V6 with modified services.jar+KaK+3G Turbocharger
FAQs and Links to Other Useful Informational Threads
[size ="3"] How do I know when it is time to try and recalibrate my battery?
You can tell when if your phone says 0 battery and shuts down yet you can still power it on for any length of time. Basically, the OS uses statistics to judge what the exact battery level is when displaying in status bar as well as when to alert you to low battery. Have you ever gotten low battery warning and then a min later it rebounds and alerts again? I have and that again demonstrates the OS is not always dead on. Also, switching batteries usually aggravated this as well. I have also had users who have used same ROM for long periods of time and it degraded so slowly they hardly noticed then after it is re-calibrated it helps a lot. All that to say there are a few indicators, but using your judgment (*gasp*) if you feel it may be off give this a shot. I do not recommend running it every day or every boot but once every several weeks or roughly 30 charge cycles (whichever comes first (kinda like oil changes in cars use judgment and changing the oil does not mean you gain 100 miles to the gallon poor a million horsepower, you instead website the car (or battery here) is in top shape and runs the best it can.
Everyone keeps asking me to search for my questions/answers before posting but that is a lot of scrolling, how do I save time searching for the information I need?
CTRL+F [Windows or Linux] or Command Key+F [OS X] should allow you to search the webpage currently in view [all text not just what you can see, but all text on page period]
OR using:
" Site:forums.xda-developers.com" (without quotes unless you want the results to include every word just how you typed it search to be in the results shown, also, try different variations of your error or question not just a long written out sentence) at http://www.google.com and this will limit your results to only those pages on xda forums (you could copy/paste URL from inside any sub-forum to further limit searches [i.e. site:http://forum.xda-developers.com/forumdisplay.php?f=1332 would limit you to the Galaxy S2 T989 DEV forum only for results]
What is with some ROMs asking for me to use CWM Touch [OR NON-Touch]?
I have been using CWM Touch latest for sometime [Current: 5.8.1.3] (being since it first released)
and I have used it to flash EVERYTHING whether it is a Gingerbread or ICS ROM whether the thread said not to or to specifically use Touch doesn't matter.
Also, I can flash anything from either internal or external SD with really no difference [I seem to get an occasional flash error via external SD and have to flash a 2nd time but I use an old SD so prolly more the cells slowly going]
From my own testing it seems to be either user error or bad flash [keep in mind EVEN if you download the file right and it is read right sometimes you can have a bad flash because during the file copy process a random hiccup happened so rarely RARELY I have to re-flash and/or re-download the zip. JUST BE SURE TO DOWNLOAD ALL ZIPs VIA WIFI YOU INTEND TO FLASH as this will have less errors during data transfers as opposed to a cellular data connection like 4G. You could also use an MD5 signature checker [versions for android and desktop pcs are available easily by searching] and if OP posts MD5 signature you can verify your download before you even try to flash which can help. Of course MD5 checks on the phone will most likely take longer than if you use a computer, but if on comp be sure TO COPY ZIP TO SOME KIND OF PHONE STORAGE BEFORE CHECKING MD5 AS THE XFER FROM THE COMPUTER TO THE PHONE COULD CAUSE AN ERROR NOT CAUGHT IF YOU RUN MD5 CHECK BEFORE COPYING ZIP TO THE PHONE. I will be posting a quick how to check MD5 guide hopefully today.
After I Install my New ROM I am getting errors no one else seems to have, WHAT GIVES?!
I keep seeing users say I have FCs all this stuff doesn't work, while in OP it clearly states all the issues they post of are all working. In my experience of helping users in these spots one of the following is normally to blame...
>> Did you Download ROM over WiFi Only? If No, you need to do so it causes less errors in file to download via WiFi and not Cellular Data [2g, 3g, 4g, etc.]
>> Did You Run MD5 Check on ROM ZIP AFTER download? If No, You really should even if using WiFi only you could possibly have a transfer error [rare but happens due to many factors]. I have posted guide below install steps on how to verify MD5 on downloaded files
>> Did you use Kernel Cleanser, Darkside Super Wipe, and Fix Permissions v2 [my flash zip]? If NO, You really need to follow the guide and be sure you fully wipe data [DO NOT WIPE EMMC OR INTERNAL SD PERIOD] FULLY [just hitting format won't do it especially if installing ICS, hopefully will change soon, but until then you need a clean slate to install ANY ICS ROM EVER, YES EVEN UPGRADES].
>> Did you skip restart allow boot THEN Restart in to recovery Clear Dalvick cache and cache run fix perms v2 and restart? IF YES, you should stop now and do that restart recovery clear cache, clear Dalvick cache and run fix perms [built-in fix perms wont work must use flash pack]
>> I FOLLOWED Everything and Still have a problem, What now, genius?
Well, sadly, like everything computer and tech SOMETIMES [albeit rare] if you MD5 checked your download and did EVERYTHING right SOMETIMES there may still have been an error when copying files, setting symlinks, or setting permissions during install that while it didn't cause major problem still caused issues. I have had to flash ICS ROMs twice before to get things to fully take [Seems better now on T-mobile based leak than the Skyrocket based leak [imagine that], but can still happen even if EVERYTHING was done right. Just be sure to follow directions again to make sure you didn't gloss over something small and flash again.
I am getting weird errors out of any GAPPS [GMail, GTalk, Market com.google.gapps, etc] After installing a ROM [Darkside evolution is one I BELIEVE], How do I fix that one?
I found that when I removed apks from /system/app in Darkside 2b1 [tw launcher, snstw (twitter) snsli [LinkedIn], Mini Diary, Mini Notes, the Yahoo Stock watching apps, etc] that I got FCs from Google Talk [even though i never touched it, and com.google.gapps [again removed google quick search box but otherwise should never have had an error]. I tried MANY different fixes over many restarts [clear caches fix perms, put the removed apps back everything].
Then I flashed Newest Gapps from http://goo.im/gapps [I believe it is 2012.04.03 [should be newest for CM9 at top of page and no you dont need separate facelock pack as that is included since 2012.0.23 pack so DONT flash facelock ICS labeled pack I had to re-install a different ROM after I accidentally pulled that one myself.
How do I mount my external_sdcard as /sdcard?
I have found the following guide on how to do just that! Mostly useful only if your micro sd is larger than the 11G internal sd the phone already has. As always, be careful, read entire post before starting, run a full nandroid backup. This is not my work, and ask you to thank the OP if you find this useful.
http://forum.xda-developers.com/showthread.php?t=1454753
OH NO, I am getting Bad Connection to Battery Error Messgae [and/or] When in charging screen [phone off battery grapic on display] and I see a yellow caution sign with a broken battery [and in some cases a rapid vibrate] IS MY PHONE DEAD?!
I ran across this myself not too long ago... First the Basics of how/why this happens the the rundown of how I fixed it
How/Why
---
Ok, so you are getting an error message stating bad connection to battery, or your phone is constantly restarting [this is not the only cause] and/or I got a weird yellow caution icon in the charge only screen [the screen seen when phone is off but plugged in to charger] [you may also get a series of quick vibrates as well in charge only screen with this as well].
From my research this seems to be caused by shutdown hangs when phone turns off when OS states 0% battery and goes to auto shutdown [may also happen if like 0 - 1% and you hit shutdown]. When the phone is about dead and goes to shutdown the capacitive lights [that bottom row of menu, home, back, search] stay off. The problem comes in if the ROM you are using hangs during this time. Contrary to popular belief when the OS says 0% and shuts down THIS DOES NOT MEAN THE BATTERY ITSELF IS AT FULLY 0% CHARGE. ANY BATTERY [not taking in to account so new experimental tech that may be out or come along come on lets be reasonable here] CAN NEVER BE TRULY FULLY DRAINED. If this were to occur you would need a special deep trickle charge device to breathe life back in to the battery. So now that's explained...
If shutdown hangs when the battery was already as dead as it can be unless you have that special device if it stays hung then it will very slowly take the battery past this safe point and you run the risk of killing it in such a way you cant revive it with a normal fast charger. Now of course since the phone is in a shutdown state it will hardly use any power at all and this should take hours [if not a couple days; I dunno as I dont want to test this and see how far you can push it] to get to the point of absolutely no return.
So when you go to even plug in to charge Android detects this and assumes the battery is damaged and is truly dead or close to it and warns you.
THE FIX
---
So after that happened when I went ot plug it in to charge the next morning [as I forgot to try to do it before bed and that would have shown a hang and I would have reseated battery and it would have been fine] I got to charge only with the yellow caution symbol and it was constantly quick vibrating so I hurried and pulled the battery and tried to put it back and got no boot vibrate and could not get charge only screen so I called Tmo and went through the motions and they agreed it was the battery and since they only replace phones referred me to Samsung
I called Samsung and to get a new battery they have A CRAZY RMA Policy [to force you to buy a battery rather than get a replacement] where you need the ORIGINAL receipt and then to wait for them to ship you a label [not next day; 5 business days], send it to them, wait for testing, and wait for them to send a new one back [again the SLOW way]. Since I dont have my receipt and refused to wait the crazy 4ish weeks it prolly would turn out to be I called them crazy and hung up. What I did was to leave the battery out of my phone for roughly 12 hours - 1 day [trying to just reseat the battery turned out to do no good the phone would not even boot vibrate even after a couple tries] then when I put it back I got it to boot to charge only screen with the warning and no constant vibrate this time]. I then waited a few min to try and ensure the battery got some charge and then pulled it out and reseated it and plugged phone back in [if you leave charger plugged in phone stays kinda on have to unplug charger AND reseat battery then plug it back in EVERY TIME].
THIS TIME I GOT TO CHARGE ONLY WITH NO WARNINGS! I let it sit for 12 hours [ENSURE it is FULLY CHARGED AS BEST YOU CAN] and I was able to boot the phone. For the next several days I would get random restarts and on occasion I would get an error stating Bad connection to battery. When that happened I had to pull battery reseat it and restart the phone [sometimes a few good times in a row stick with it] and over those few days I CAREFULLY monitored the battery to be sure I did full charge cycles [charged it fully in charge only and as soon as it auto shutdown I made sure to get it RIGHT on the charger [and pulled battery and made sure to see charge only screen to ensure another hang up didnt get me].
After those few days, I felt comfortable to CHARGE IT FULLY IN CHARGE ONLY and ran through calibrating the battery. After the calibration I no longer got random restarts or errors saying Bad Connection to Battery and ever since it has been good to go.
I know that was a little long winded but trying to get all the info in there as I AM NOT TESTING THE CONDITIONS THAT BROUGHT THIS ON TO FURTHER REFINE THE STEPS. Unless someone wants to buy me a couple spare batteries to test this and I know I have a good spare to fall back on.
Device: Samsung Tmobile S2 [SGH-T989]
ROM: Paranoid Android 2.52
Tweak Script: Newest Supercharger V6 with modified services.jar+KaK+3G Turbocharger
Which Android versions? So people aren't confused
Sent from my SAMSUNG-SGH-T989 using xda premium
Locksmith81 said:
Which Android versions? So people aren't confused
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
All Android versions apply I would specify in title of my thread if it were limited just tailored to be best method with our device regardless of OS as long as you have cwm or most other custom recoveries.
Device: Samsung Tmobile S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze 4g ICS Radio
Tweak Script: Newest Supercharger V6 ICS with modified services.jar
Superchargers 3g turbo boost
(specific T989 pack as next project)
I agree with what Google said about battery calibration and conditioning, it is a placebo effect. I have never calibrated nor conditioned my battery and always get anywhere from 15 hours to 2 days use out of my battery depending on use.
Sent from my SGH-T989 using xda premium
DannyB513 said:
I agree with what Google said about battery calibration and conditioning, it is a placebo effect. I have never calibrated nor conditioned my battery and always get anywhere from 15 hours to 2 days use out of my battery depending on use.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
LoL and if you abuse battery by leaving it plugged in our never fully charging discharging battery and statistics are messed up or a bad flash corrupts them what you get new battery?
All I can say is I have seen huge gains on devices doing this, yes it won't help to do it all the time that is a placebo, but trust me in real world with folks not always using devices per manufacturers guidelines (cough rooting and custom ROMs cough) it can really help.
Trust me I don't post info unless I exhaustively test something and can vouch for results myself on multiple devices and with multiple user feedbacks (just ask mysticfrog if it is worth reading what I post )
To each his own though you don't have to follow my advice if you choose not to I ain't gonna show up at your house or anything )
Sent from my SAMSUNG-SGH-T989 using Xparent Green Tapatalk 2
This method works not because u wipe battery stats, but because u reset the battery memory, which is built into the battery itself. Google has confirmed the myth, wipe battery stats simply deletes a bin file that android creates on each reboot that track your app usage per charge, that is all.
It should also be noted that doing the method frequently will actually have ADVERSE affects on your battery. Completely discharging newer lithium batteries can result in dead cells, so be careful.
icenight89 said:
This method works not because u wipe battery stats, but because u reset the battery memory, which is built into the battery itself. Google has confirmed the myth, wipe battery stats simply deletes a bin file that android creates on each reboot that track your app usage per charge, that is all.
It should also be noted that doing the method frequently will actually have ADVERSE affects on your battery. Completely discharging newer lithium batteries can result in dead cells, so be careful.
Click to expand...
Click to collapse
Well FYI, there is actually no way to FULLY discharge a battery UNLESS you left it without charging for days or weeks by fully discharging we mean until phone wont turn back on which leaves plenty of charge for a couple weeks still there. If battery EVER FULLY discharged you would need a special deep slow charger to revive it. You can trust I have been on computers and technically minded since I was VERY young [over 20+ years experience in computers and related devices]
Keep in mind Google engineers may not want to say admit there could ever be a battery issue that could be blamed on something like a stats file as that could open them to lawsuits since they do not disclose that at time of sale so sometimes what google may say on something while not an out right lie by any means will be shaded to benefit them every time [they have to make money can't blame them too much ] LLike they just got caught overriding browser privacy settings be exploiting an old loophole in cookie code so even if you said to deny google based cookies they were still getting all the tracking info they needed from you, or in UK [and here but under investigation] when they had the street cars for maps out and got caught gathering unencrypted wireless data to include passwords, emails, internet traffic, etc.] or how they just released that they are now spending 5 BILLION in lobbying in Washington up 5 fold from only a couple years ago. Not trying to say you cant listen to what they have to say just saying maybe you could investigate what they say just like you read my post and were not satisfied and went looking for information.
CORRECT, you wipe the statistics file SAVED ON THE DEVICE that saves your statistical information about your usage as battery charge changes [the file on the battery is actually just for dating, # of charge cycles, and current charge level you cant mess with that]. BUT, the statistics file ON the phone can be erased. By doing this you wipe away the files if they are corrupt OR have outdated information for say a differnt ROM with DIFFERENT usage conditions.
I already said you shouldn't do this everyday there is no gain from that, but if you say are home body and leave it plugged in all day everyday for a month and then go to go on a trip your battery will die too fast as the statistics Android is using are based on being plugged in all the time [NOT RECCOMENDED as again device chargers are fast chargers meaning they throttle between slow and fast charge and you DONT want the top 25% of a battery to be charged quickly as that can really hurt the battery and leaving it plugged in will increase the chances the charger accidentally throttles to fast during a time it should not as time goes on] so you would wipe those and have it restart stats while it is now being used off charger instead of on and that does and will get extra life [not more than the battery is physically capable of just the MAX it is capable of.
The only proof you need is to see when the phone shutsdown saying no more battery and then if you can boot it up and it says 10% left and stays running for another 15 min then the statistics are off and you can reset them to gain that time BACK instead of having the device shutdown earlier than it should have.
Dude I did not say this will give you more battery life than the battery is capable of, it is like chkdsk for your phone as you use NTFS it journals [albeit poorly and half ass] and should not suffer from corruption, BUT users who shutdown the machine incorrectly for instance will find when they run chkdsk on occasion they gain free space back due to errors caused by incorrect usage. The philosophy is the same here.
or EXT3 which is fully journalized should NEVER need to be checked yet they have e2fsck to fix errors due to corruption [again due to incorrect usage [ie forced power outtages that the FS can't account for] because even though it shouldn't happen in the real world nothing goes to plan.
sorry, gotta be said, stupidest post ever, clearing battery stats is pointless, and STORES NO INFORMATION ABOUT CELL CAPACITY/OR ANYTHING OF THE SORT, all that is actually on the board inside the cell.. also, check the location, gets wiped installing a new rom anyways? Also, with cell phones (keyword, CELL) Which use lithium ion cells, there is NO POSSIBLE WAY to "calibrate" the cell through the device, please at least research befor posting "how tos" u more or less are wasting peoples time
@buddy saying killing a lithionum cell will ruin it, also bull****, that. Control board inside is designed to actually stop or "die" around 100mAh meaning its impossible to kill a lithium ion cell without screwing with the board, or leaving it in device, empty, for over 6months.. PLZ PPL, CHECK UR FACTS BEFORE POSTING
doug36 said:
sorry, gotta be said, stupidest post ever, clearing battery stats is pointless, and STORES NO INFORMATION ABOUT CELL CAPACITY/OR ANYTHING OF THE SORT, all that is actually on the board inside the cell.. also, check the location, gets wiped installing a new rom anyways? Also, with cell phones (keyword, CELL) Which use lithium ion cells, there is NO POSSIBLE WAY to "calibrate" the cell through the device, please at least research befor posting "how tos" u more or less are wasting peoples time
@buddy saying killing a lithionum cell will ruin it, also bull****, that. Control board inside is designed to actually stop or "die" around 100mAh meaning its impossible to kill a lithium ion cell without screwing with the board, or leaving it in device, empty, for over 6months.. PLZ PPL, CHECK UR FACTS BEFORE POSTING
Click to expand...
Click to collapse
Before being so abrasive, it should also be said that you stated facts without providing correlating evidence. I'm here to learn just like everyone else, and if something was said in error it is only based on information i have read or learned elsewhere. If you look at my thanks meter you will see i am an EXTREMELY helpful user on this forum.
Although uncalled for in the way you stated it, I would be interested to see where you obtained this information. Perhaps some links?
icenight89 said:
Before being so abrasive, it should also be said that you stated facts without providing correlating evidence. I'm here to learn just like everyone else, and if something was said in error it is only based on information i have read or learned elsewhere. If you look at my thanks meter you will see i am an EXTREMELY helpful user on this forum.
Although uncalled for in the way you stated it, I would be interested to see where you obtained this information. Perhaps some links?
Click to expand...
Click to collapse
I am sorry if I hurt you're feelings, I can't account for local customs, I am here to pass along info. When I get time I will post links if needed you can google things like google cookies bypass browser settings, google street car suits, etc to double check me. Right now I have a dislocated ankle and getting dental work done so it may take a day or 2 before I can sit down and index the information for you.
Sent from my SGH-T989 using Xparent Green Tapatalk 2
RealPariah said:
I am sorry if I hurt you're feelings, I can't account for local customs, I am here to pass along info. When I get time I will post links if needed you can google things like google cookies bypass browser settings, google street car suits, etc to double check me. Right now I have a dislocated ankle and getting dental work done so it may take a day or 2 before I can sit down and index the information for you.
Sent from my SGH-T989 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Not you RealPariah, you posted an informative thread with information based on your testing and results, and nothing is wrong with that, health debate is good and you provided some good arguments. I was making reference to doug36, and his rather uncalled for comments.
This would be what your looking for, quick google search,
Click a result and read the specifications.
http://elithion.com/lithiumate-pro-cell-boards.php
Ofc none really compare to the one in these batteries, but you should get the idea
They all have a preset for min (Isolation voltage apparently xD google rocks)
as other variables, and ofc with OEM cells, and boards,
Are actually able to store a WIDE variety of data to the cell, and the device doesn't have write access to this board...
So how can you calibrate it?
Also, google debunked this a while ago (batterystats)
And stated EXACTLY what its used for IT DOESNT STORE THE CURRENT PERCENT
batterystats.bin is located in "/data/system"
And 99% of roms wipe data/system/cache partition
Last point.
Its deleted/redone on boot, REGARDLESS OF POST STATE
meaning, its new every time anyway.
You are totally missing the point the below copied conversation may help:
The batt stats is a file under data, and it attempts to keep a good record of your usage to accurately predict your battery use. It's good to wipe this, if you're able, every two weeks or so. This file can also get messed up if you flash a rom on a non full battery, hence why battery can be worse after flashing a new rom.
Sent from my Droid using Tapatalk
Tank, *where* under data do I look for the battery stats - what's it called?
-Mike
It is the batterystats.bin under /data/system.
Oh and yes file is replaced at install and that's what causes you to have to then remove it while battery at totally full so file starts correctly thus fixing the problem. The same goes with usage the file may get corrupted if phone shutdown incorrectly, or app did something, or storage has an issue causing data loss, etc. Or be totally wrong because you swapped out the battery (whether it dies or you have spares what matters is it is a physically different battery you should wipe) and why I posted how to do it best on this phone.
I am not saying you are doing anything to the battery itself. You are working with the Android system and what it is doing (not changing it just restarting it).
I have seen this personally help at least 20 unique Android based devices personally and to varying degrees of success (depends how far off the estimation has gotten) so I know it can help.
Sent from my SGH-T989 using Xparent Green Tapatalk 2
Ok, and u didnt read my post, ITS RECREATED ON BOOT REGARDLESS OF POST STATE,
Try this if you wanna test
Usng root explorer find the file, mod permissions 777 (rwxrwxrwx)
Edit it in text editor probly wont open it all, who cares.
Add anything at top or bottem, save, restore perms, and battery pull
Reboot and see if that lines there.
If it helped some devices it was probably the reboot.
Again please test this if your actually making a "guide".
Also, HOW CAN IF EFFECT A ROM INSTALL IF ITS A SYSTEM FUNCTION AND DOESNT EVEN CALL CURRENT %
Its main purpose is show a timeline in >SETTINGS>APPLICATIONS>battery use (I believe that's wherre) on GB
And >SETTINGS>battery on ics..
the file can't get messed from rom install..
Alls it does in a short sentance:
Stores information regarding uptime/cpu on running APPLICATIONS,not services.
This information is then calculated from the info from the cell board, such as
Max mAh and Isolation voltage, to get a estimation of the percentage of the battery use used by that application
COMPARED WITH THE SYSTEM. This file IN NO WAY DOES ANY SORT OF CALCULATIONS ITSELF
IT IS:
NOT a binary
NOT a configuration
NOT an executable
A list of references that the system should gather calculations for.
Recreated on boot
Read/write on system no perms on group/others
A temp file.
You brought up another useless. point, data corruption from incorrect shut down is rare to say the least that's what buffers are for
Android, like most full OSs (linux also, duh) use multiple countermeasures to stop this
If The system stored the mah levels of the cell WE COULDNT USE EXTENDED BATTERYS
as I said a few posts back RESEARCH BEFORE MAKING STUPID TOPICS
Its not recreated on boot if it were there would be even more problems that file should only be created when battery at 100%.
ALSO CACHES ARE USELESS IF SHUTDOWN INCORRECTLY (power loss due to not enough power a user pulling a battery during a freeze, etc can happen anytime you are thinking of journal which should eliminate errors (in theory) but really only help, if that ass umption were correct (that ext file systems gave no errors) then why does a file system repair tool exist (e2fsck) if errors never needed fixing?
Look you obviously have your head in a book, try something out in practice and stop quoting theory and corporate lackeys I have read all the same things before too. I am not new to Linux or Android.
Also statistics are not hard set to one mah level or they would have to do stats for every new battery the system takes basic info such as full mah from battery and current level (so if charger plugged in it is not fried) and generates a new stats file on boot if none exsists, but if you day have stock battery in it does then you plug in extended battery you would see when it"supposedly"did you can turn phone back in. if estimation was never wrong then once it dies saying 0% you couldn't turn it back on because you were already tools battery did not have enough power to continue to run phone. If it does turn on for any length of time the OS got it wrong.
you don't want to calibrate your battery don't this is last time I reply to this tangent.
Sent from my SGH-T989 using Xparent Green Tapatalk 2
icenight89 said:
Not you RealPariah, you posted an informative thread with information based on your testing and results, and nothing is wrong with that, health debate is good and you provided some good arguments. I was making reference to doug36, and his rather uncalled for comments.
Click to expand...
Click to collapse
I am sorry I misread you, and sorry you got lost in the mix there., thank you, but you can only lead a horse to water I guess. I just love how he says research and then says that cache helps save you from bad shutdowns when in fact cache is set aside fast access memory [usually a chip on the device or could be provisioned RAM] and that is what causes the problems on bad shutdowns [since it is in a form of memory dependent on power an you lose power that data is lost and how to try to mitigate that on power loss or bad shutdowns is half the battle. I think he was talking about the journaling found in the EXT file systems I think which is supposed to help re-create corrupted data if it happens, but as with everything computer nothing is ever 100% in practice, and is why you have need for error checking with things like e2fsck.
Also, I hope he realizes Google ASSUMES THE FOLLOWING CASE WITH ALL SUBSCRIBERS When dealing with anything: You buy your Android Device, You turn it on, you use it (maybe with some accessories like headset and bluetooth), and you never change anything the OS, the Battery, anything inside the case. They enjoy modders and developers, BUT they always call anything modified [EVEN EXTENDED BATTERIES] outside the normal and therefore outside of warranty and outside of the scope of any support they offer.
I do my best volunteering my time giving information learned from countless hours of love poured in to a craft that I love, working on a MULTITUDE of devices [I have co-workers, neighbors, and even sometimes strangers approach me and have me help them do any number of things]
FOR INSTANCE THIS METHOD OF CALIBRATION was thought of, sorted out and gathered AFTER my boss had an issue with his phone lasting like 6 hours on a charge and he wondered why when using 3 different batteries the phone would behave differently even though they were all the same make and size. I then went out and researched why that could be and gathered information and learned what was happening, was able to re-create it and then I fixed it. That was back in Android 1.5 LoL. Now when I got the S2 and had the same things happening several years later I researched that it was still an issue and went about fine tuning a method for fixing it best on the T989. Since initially learning how to do this and when and why I have helped COUNTLESS users who always complain their batteries die too quickly and who have never rooted, modified their phones or otherwise knew they could and when I went about getting custom recoveries and running variations of this method they all came back the next day or several days later and profusely thank me that they magically gained anywhere from an extra hour to 6. So I have to laugh when folks who read the first couple paid for results and quote the theory written in text books that I have already found through further research and practical use while not intentionally wrong did not take in to account certain things [be that apps can freeze a phone to the point you pull the battery or that a phone never loses power in such a way to cause data loss is just speaking in absolutes which is always an absurd thing in the technological realm.
Sounds like it's boiling over!
sent from a Android device
I'm always on!
axne1 said:
Sounds like it's boiling over!
sent from a Android device
I'm always on!
Click to expand...
Click to collapse
I know right is why I am done I posted more than enough on that and more than enough folks vouch for it that's the last I pay attention and reply to that.
Sent from my SGH-T989 using Xparent Green Tapatalk 2
Since this Defy Forum is getting a bit old, I thought I'd give my recent experience with my defy. This is quite a lengthy thread but there is so much information on this forum that it becomes confusing so thought I'd share my experience so you can cut through a lot of the information. I've had my defy for over 5 years with the stock froyo 2.2.2 and its served me well until recently its beginning to bug me with how laggy it is. Also I wasn't sure if the battery was running out a faster than it used to.
The first thing I thought I'd do is do a factory reset which I successfully did however when I went to put back on some of the apps that I had before such as Runkeeper, Telstra 24/7 and RSA Security token, none of them were compatible with my old phone. I was able to find old versions of some of the apps but not Telstra 24/7 which I use to recharge. At this point I decided on installing a custom rom which I'd done before on other devices. If it didn't work out then phones with the same specs were selling for $29 at a local supermarket so no real damage if I get it wrong.
The first thing was to root the phone which I found something called Superoneclick. I had to turn off my antivirus on my PC use it as there are some files that appear corrupt but doing some searching gave me confidence it was just an overzealous AVG and appeared safe.
Once this was done it was a matter of picking a Rom which I went for CM11 Kit Kat it seemed ok but not heaps better. The thing was I'd now picked up a real battery problem. I tried various Calibration apps to no avail. My battery was experiencing quite large drops of 20% ie it would go from 89% to 50% and then later from about 35% to 20%. It would then stay on 1% for quite some time.
Thinking this was due to the ROM, I tried several ROMs but they all had the same problem. Eventually i found a thread on the battery problem and although I didn't change all the permissions as advised I did so some of the other stuff to no avail.
At this stage I thought my main issue was now the battery and thought I'd read someone that perhaps a stock based rom might sort it out. I installed MS4Ginger which was really smooth however was still a bit laggy at times. Also I noticed that it wasn't able to support various apps being Android 2.3. After a bit more reading, my minimum requirement was Jellybean 4.1 and I'd read that the more recent the ROM the more RAM intensive so I decided to try ROMs with my minimum requirement ie 4.1
I'm not a fan particularly the way the Cyanogen type rom look so was looking for something with a different look and feel. The main ones were:-
Miui based ones (Wiui, Jiui) which I quite liked however lag was still there and the occasional sudden reboot. Battery problem still there.
Xperia ROM which was also nice but also did a sudden reboot then stuck in a bootloop.
There was still lag which I couldn't really understand.
Last Rom I tried was Motor Gun Ice 4.1, it still had the Cyanogen look about it but seemed to run pretty smooth. One thing I had to do was change the Baseband to Telstra in the 'Advanced' section of settings. This made the phone and internet connection work faster.
At this point I ordered a new battery. While I was waiting for that to arrive I read that Facebook app is really bad at taking up RAM. In found another app called Facebook lite and uninstalled the standard Facebook app. All of a sudden Lag Fixed.
This got me searching other 'Lite' apps. Now for web browsing i use Opera Mini and the launcher I now use is Holo Launcher. I also tried to find a replacement for Messenger but no luck and its not been an issue.
So now my phone is running better than ever. Web searching is fast and apps are running well, not that I use my phone for much more than a phone.
A few days later my new battery arrived and comparing to the old one, it appeared that the old one had a slight bulge. I charged the new one right up, discharged and charged again and now no more battery drops.
One last tweak I wanted was to try change the status bar icons. I found Xposed Installer and was able to change the icon colours to white but not the icon pictures. Good enough for me.
So now I'm very happy with my 5 year old defy, took a bit of trial and error but got there in the end. So in a nutshell: -
- If your battery is dropping upon installation of a Rom, likely need a new battery.
- If you phone is lagging, look what is taking all the Ram and look for a lite option or uninstall. Facebook is bad for that.
Note that there are many old links to roms and other mods so finding things that work was at times a challenge but here's the process that I found worked for me and works if bricked as well, which I did a couple of times.
If Bricked or to get back to stock
Download RSD Lite
Install drivers for the phone
Download an SBF for your region, I used Telstra with 2.2.2
To install custom rom
Install and use Superoneclick to root (may need to turn off antivirus)
Install 2ndinit.apk then run it. May need to reboot phone first
Download the Rom and Gapps and put on SD card of phone
Get into custom recovery
Wipe Data and Cache
Install Rom and Gapps
Wipe Cache and Dalvik Cache (for all but one Rom, I forget which one, read instructions)
Reboot and enjoy.
the gun rom link is down, where you downloaded it?
That was one of the few that worked. I accessed from the defy wiki page then I think downloaded from the XDA thread.
Yep, there some links in the last post of the MG ROM thread. Post #222.
Good someone still use defy. I give up after digitizer gone mad. Time run over this device... Uuuh, just if it had 1 gb ram and dual core...
Good to hear that someone else still have this cute little thing. I have too, as my second device. The ROMs I tried on this device! Man, it's countless. I had dropped it on all the different terrains you can think of, yet it's still fully healthy (save the jack and usb covers - they are loose now) without a single crack. I didn't have any covers or screen guards. It stayed true to its name. I will never regret spending money to buy this, it is one of Moto's legendary devices. I think I'm drunk, but it feels good to say all this. I'll keep this device forever with me - a product from a time when smartphones weren't made in an oven, but carefully and delicately cooked up.
Digitizer gone mad me too, the upper line is not working, but it is a good phone, for kids.
Which seller you order the battery?
Can you suggest ROMs to watch videos on Kodi, or Youtube?
I liked this phone, this is the best size phone, what i ever had.
Why the companys not make phone like this size, one hand controlled, with 2GB/32GB, and quad cpu??
Now i have Samsung S4 mini, and it is big for me
Battery was off eBay, can't remember seller but was Australian selling genuine batteries.
Just try all the roms possible, that's part of the fun
Sent from my SM-T210 using Tapatalk
I've been wanting to play around w/ my old defy again. This thread may have got the ball rolling. What do you all use as your daily driver? I've got a xperia z3 compact, but want a new phone. unfortunately, I think my best bet is to just get another z3 compact cheap and save it as a backup?
Hi tronjojo, I was still using my Defy until recently I found an old 4 year old Samsung Galaxy SII of my wife's. The problem for her was that it was switching off all the time so she got an S5. I've now flashed various roms and fixed the random reboot issue. The only thing I wish it has is the notification LED.
Sent from my SM-T210 using Tapatalk
I bougnt a Defy + battery on my Defy Red Lens, made my own BL7 fixed SBF and nandroid with 720p patch which made it a Defy Plus, then I rooted it and repartitioned to install CM11 and has made it very usable in 2016.
Make that Defy in 2018
I'm still using a Defy, since 2011. The battery still lasts longer than that in my wife's new Sony Experia X Compact, about as long as in my daughter's Xiaomi Redmi 4X. I will probably have to move to another device somewhere in 2018 as one of the more important apps - the Swedish BankID app - will cease support for Android 4.4 but that is more or less the only reason. For the rest the thing still does what it did 7 years ago so were it not for this I'd keep on using it until it gave up from sheer old age or electron migration or whatnot.
Make that Defy in 2020
I've recently tried if my Defy+ could learn some new tricks and I thought I'd share my findings.
CM11 build
I tried to build CM11 from Quarx repository, but it seems that many of its dependencies no longer exist and whole project is no longer buildable.
3.0 kernel
This one builds fine, however I was unable to boot it - there's one frame or random pixels followed by a reboot. I checked many branches and put the output into most probable directories. I wish there were any instructions as to what actually do with a built kernel. TWRP zips found here didn't work either. Anyone?
SD card size
Defy supposedly shouldn't work with SD cards larger than 32GB. But did anyone try bigger cards? My Defy mounts 256GB cards without any problems.
Debian on chroot
I set up a Debian environment with debootstrap. Unfortunately outdated kernel puts a limit on a Debian version that could be run. For 2.6.32.9 it is Debian Jessie.
With XServer XSDL it is possible to run a full graphical environment.
2.6.32.9 kernel modules
I also succeeded with building kernel modules for the old kernel. These are mostly filesystem modules and cryptographic ciphers. Now I could use whole Debian Jessie repository (49GB) locally from a squashfs filesystem.
Another nice feature is encryption with dm-crypt/LUKS.
I uploaded modules that insmod loads without any error.
CA certificates
These should be updated with system updates, but we won't have new CM/Lineage/stock releases anymore, so I did it by hand. If you want to try it for yourself, remount /system as writable, remove contents of /system/etc/security/cacerts/ (they could be expired) and copy certificates from the archive. Certificates are same as Debian's ca-certificates version 20200601.
Mirror
I also uploaded tools and images - self contained with instructions to go back and forth between stock and CM11, because many links here are spread across many threads or simply dead. Kernel modules and certificates are for CM11. I didn't try them with anything else.
I can't post a link to these files, because this is my first post. Search for ybea in Motorola Defy section at AndroidFileHost.
Another 2020 Defy warrior
ybea said:
3.0 kernel
This one builds fine, however I was unable to boot it - there's one frame or random pixels followed by a reboot. I checked many branches and put the output into most probable directories. I wish there were any instructions as to what actually do with a built kernel. TWRP zips found here didn't work either. Anyone?
Click to expand...
Click to collapse
Hello! Did you check on /bootstrap/bootstrap/binary and other folders? There seem to be a zImage (and the recovery one).
I tried to flash and boot the ROM at http://blechdose-live.de/download/kernel/3.0.x/:
Tried flashing from TWRP 2.8: failed.
Extracted the update-binary, copied it to /tmp and executed it from ADB shell (/tmp/update-binary 3 0 /sdcard/cm11-blah.zip) and flashed with some things, mostly partition related errors. After rebooting, it stays on black screen (turned on), ADB available but unauthorised (just look on Github how to enable ADB from recovery to solve that) and that's all; the ROM doesn't work. I'll try debugging this to check if I can do something.
ybea said:
CM11 build
I tried to build CM11 from Quarx repository, but it seems that many of its dependencies no longer exist and whole project is no longer buildable.
Click to expand...
Click to collapse
What a sad thing, this year even quarx2k.ru became offline...
MaicoLinuX said:
Hello! Did you check on /bootstrap/bootstrap/binary and other folders?
Click to expand...
Click to collapse
Files extracted from 20131213 version did not work for me. I tried swapping /bootstrap/ (and /system/bootstrap/) zImages, binaries, edited cmdline, anything I could think of. Always with the same outcome - black screen.
Flashing in TWRP (v2.6.3.0) initially also failed. Fix_TWRP_and_boot_kernel3.0_v2.zip (on AndroidFileHost) makes it succeed. It is 3.0.8 kernel. It froze during the boot, restarted and finished eventually.
ybea said:
Files extracted from 20131213 version did not work for me. I tried swapping /bootstrap/ (and /system/bootstrap/) zImages, binaries, edited cmdline, anything I could think of. Always with the same outcome - black screen.
Yeah, it did the same for me. Did you read the logcat while device was in that screen? I saw something crashing there (can't remember), anyway that's not so useful if you need a whole new ROM just for the new kernel version. Maybe modules are causing problems?
Pretty offtopic, did you try the OTG function? I can't get it to work, most people say it should work out of the box but I wasn't able to use my USB mouse. Didn't check dmesg, though.
Click to expand...
Click to collapse
MaicoLinuX said:
ybea said:
Always with the same outcome - black screen.
Click to expand...
Click to collapse
Did you read the logcat while device was in that screen?
Click to expand...
Click to collapse
How could I? Android isn't running yet. It it Linux that either fails to load or silently panics. That is my understanding anyway.
The right thing to do would be to check how cm11 build compiles the kernel and the 2nd-init (or whatever it is), but I am not knowledgeable enough, nor keen enough to do that.
OTG is buggy, but usable. If it doesn't work, unplug and plug it again. It is quite normal for my defy to recognize a device on a second or third attempt. No problems with mice, keyboards, flash drives, usb hubs. On the picture in the previous post you can see it with a wireless keyboard+touchpad. If I remember correctly, the driver is set to output 200mAh max. Maybe you mouse draws more (rather unlikely for a mouse). It works for me with cm11-20161124. Also, I think the port outputs 5V even after a device is disconnected, so it unnecessary drains power, but I am not so sure about it.
dmesg should definitely log any new device. Even if android stays quiet. If there's silence, perhaps your cable may of wrong type. USB A to USB micro varies with resistancy across two pins. I don't remember the details. If it is OTG cable, then it should work.
Or simply you have dirty socket/plug pins.
ybea said:
How could I? Android isn't running yet. It it Linux that either fails to load or silently panics. That is my understanding anyway.
Click to expand...
Click to collapse
AFAIK 2ndInit keeps adbd running so you can take a logcat/dmesg from there, also faced the same issue while flashing CM10.2 OTG kernel on CM11 (what was I thinking?) and from there was able to see that something was crashing.
ybea said:
The right thing to do would be to check how cm11 build compiles the kernel and the 2nd-init (or whatever it is), but I am not knowledgeable enough, nor keen enough to do that.
Click to expand...
Click to collapse
Nah, I think just taking some time to understand the 2ndInit boot process is enough, anyway when I get some free time I'll check about this all.
About OTG things, now will install CM11 3.0 kernel and see how it works (I expect some unstability) but don't really need to use the Defy, it's just there for experiments
Anyway, my main goal now is to install Debian natively (on /data partition because of the size) and get X running. As you said, the 2.6.32 kernel puts the limit at Jessie, but that's not a problem as it's still mantained IIRC. I'm using a prebuilt rootfs but it keeps throwing Segmentation Fault whenever I try to chroot there, don't know what happens with this.
I'm doing the same on other 2 phones (Galaxy Y and Pocket Plus, ARMv6 and v7 respectively) but one doesn't boot my compiled kernels (?) and the other complains about the buggy framebuffer driver (thanks Samsung/Broadcom). I went pretty offtopic...
PD: tried to flash some JB Ice Gun Edition v2.02 from CWM and after reboot the phone just is stuck on boot splash, but WIUI runs fine. Maybe the JB IGE BootMenu is broken or something like that.
MaicoLinuX said:
About OTG things, now will install CM11 3.0 kernel and see how it works (I expect some unstability)
Click to expand...
Click to collapse
I didn't have any luck with flashing zips with only the kernel. This 20131213 rom is the only way i know of. But frankly, there's more instability then stability in it. For example only home and power buttons work. OTG also non functional.
MaicoLinuX said:
As you said, the 2.6.32 kernel puts the limit at Jessie, but that's not a problem as it's still mantained IIRC. I'm using a prebuilt rootfs but it keeps throwing Segmentation Fault whenever I try to chroot there, don't know what happens with this.
Click to expand...
Click to collapse
Jessie is no longer maintained. It stopped being oldstable about a month ago. AFAIK it changes little - apt continues to work; unless your applications have dependencies to newer libc, they should at least compile.
I build Debian root with debootstrap. On host machine:
Code:
debootstrap --arch armhf --foreign stable /debian http://http.debian.net/debian
Then mounting on Defy:
Code:
# Mount an sd card partition
mount -o remount,rw /
mkdir -p /debian
mount -o remount,ro /
mount -t ext3 -o noatime,suid,exec /dev/block/mmcblk0p2 /debian
mkdir -p /dev/shm
mount -t tmpfs -o rw,nosuid,nodev,noexec none /dev/shm
mount -t proc proc /debian/proc
mount -t sysfs sysfs /debian/sys
mount -o bind /dev /debian/dev
mount -o bind /dev/pts /debian/dev/pts
mount -o bind /dev/socket /debian/dev/socket
mount -o bind /dev/shm /debian/dev/shm
Then debootstrap second stage:
Code:
LD_PRELOAD= TMPDIR= PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin HOME=/root SHELL=/bin/bash /system/bin/chroot /debian /debootstrap/debootstrap --second-stage
Done. To login:
Code:
chroot /debian /bin/su -
Don't chroot into bash. It will leak Android's shell environment into Debian's.
Android has its own groups and users. To make Debian adapt:
Code:
dpkg -i android-permissions_0.2_all.deb
Edit /etc/group, so that it contains:
Code:
inet:x:3003:root,_apt
net_raw:x:3004:root
Edit /etc/passwd/:
Code:
-_apt:x:104:65534::/nonexistent:/bin/false
+_apt:x:0:65534::/nonexistent:/bin/false
Edit /etc/adduser.conf:
Code:
-LAST_SYSTEM_UID=999
+LAST_SYSTEM_UID=99900
-LAST_SYSTEM_GID=999
+LAST_SYSTEM_GID=99900
-FIRST_UID=5000
+FIRST_UID=500000
-LAST_UID=8999
+LAST_UID=899900
-FIRST_GID=5000
+FIRST_GID=500000
-LAST_GID=8999
+LAST_GID=899900
Then:
Code:
apt-get update
apt-get install dialog
apt-get install locales
dpkg-reconfigure locales
apt-get install less man
If apt can't resolve hostnames select a nameserver in /etc/resolv.conf.
This how I setup Debian on chroot. Some of these steps may be unnecessary - they got accumuated over the years and I don't fully remember reasoning behind them. Debian inside /data/ should work too. I can imagine there would be problems with permissions on fat32 /sdcard, but /data/ is ext3.
Hi
Since installing the December 2018 update to Android Pie last week my phone has become unusable. It freezes for 5-10s period all the time while using. Sometime, when it wakes back up again, there is a message on the lock screen that says 'you need to unlock using pattern after reboot' which makes me think the phone is crashing and rebooting itself while the screen stays frozen.
I have done a factory reset twice. In fact, directly after the December 2018 update, the phone got stuck in a boot loop and I had to factory reset then, as well.
Anyway I did some research on here and have run Androbench as people seem to be blaming poor write performance. See image.
Please - what can I do? Roll back to an earlier version of Android? The phone has worked perfectly for months until last week.
Many thanks.
you could try to reflash the latest pie rom with miflashtool. if you tick "flash all expect storage" you wont 't lose any data
download the latest rom from website, extract the image folder with contents inside and add this flashall.bat to the image folder contents, https://1drv.ms/u/s!AqlJY73bUA7rhokx5kWL6MAtXYDRTg . This will completely flash the whole phone without relocking the bootloader. I had exact same issue after using twrp to make a nand, its had something to do with accessing firmware while making backup, i think this will sort your phone out, dont use miflashtool its a total mess. Dont mess with flash order, ppl may say it doesnt matter what order its done, but it does matter. Instructions are, assuming you have adbtools, to use admin cmd prompt to the image folder and type flashall.bat, you need to add adb platformtools to windows system variables path.
Brilliant - thanks for the reply. What you suggest is probably on the limit of my skills and experience, so I have a few questions if that is OK:
boe323 said:
download the latest rom from website,
Click to expand...
Click to collapse
So, this? https://en.miui.com/download-354.html
boe323 said:
extract the image folder with contents inside and add this flashall.bat to the image folder contents, https://1drv.ms/u/s!AqlJY73bUA7rhokx5kWL6MAtXYDRTg .
Click to expand...
Click to collapse
I assume just copy & paste this file into the main folder?
boe323 said:
Instructions are, assuming you have adbtools, to use admin cmd prompt to the image folder and type flashall.bat, you need to add adb platformtools to windows system variables path.
Click to expand...
Click to collapse
Thanks, I will check that platform tools is in the system variables path. Maybe it will become clear, but I can't remember if the rom image needs to be stored on the phone or PC before I start?
Thanks
After fixing itself last time (with a factory reset), my phone's performance has gone absolutely again since the September update. It hangs constantly, takes 10 mins to turn on, and is generally unusable. Memory logs below.
This time nothing I have tried will fix it, I have tried: factory reset from bootloader, miflash to latest rom, using fastboot to flash latest rom, using the modified flash_all.bat from boe323 (thanks for your help last time).
Still the performance is dreadful.
Is there anything else I can try before I throw this phone away?
Thanks anyone for helping
Flash lastest stock (10.0.13.0) with no flash but use: fastboot oem edl , u can search in you tube how to do is easy
Hi, thanks for idea, I did this last night (new memory logs attached)
Still I get the same issues. system UI hangs and crashes basically make the device slow and unusable, especially in Chrome.
Any ideas on what I could do next?
Ideas gratefully received
Thanks
yeahdisk said:
Hi, thanks for idea, I did this last night (new memory logs attached)
Still I get the same issues. system UI hangs and crashes basically make the device slow and unusable, especially in Chrome.
Any ideas on what I could do next?
Ideas gratefully received
Thanks
Click to expand...
Click to collapse
If nothing helps , just use MiFlash , and don't use clear all , use clear all_lock.Relock your bootloader and test if everything is working ok. If it doesn't - then I hope you have warranty. Relocking and unlocking the bootloader is so easy , so you don't have to be worried about nothing. Then you will be sure , if the problem presists with totally stock firnware , then you have only one choice.
thanks - trying this now
Downloaded your app and tested it on my perfectly working device. No problems at all, no hangs, fluid, etc.
I attached the results.
If you flashed stock ROM and the speeds are that horrible... you should check if any apps are causing the hangs. Reboot in SafeMode and check the speeds. If the phone behaves normally in SafeMode, than something you installed/configured is causing the said problems.
The last solution would be... checking the NAND chip, I don't quite know if there are apps that could check the sectors in the NAND memory. Maybe you are experiencing a bad nand/multiple bad sectors slowing down everything... But from my knowledge this shouldn't be a problem in current technology, since Android has auto-trim and bad sectors should be ignored, not affecting performance.
From my experience August update fixed the problems and September brought a system speed-up. I feel the phone even more snappy now.
Thank you for this. My phone is fine in Safe Mode! I didn't think of this, as when I was relfashing the Rom I wasn't installing any additional apps - just the Androbench to check performance (always after checking that the problem was happening).
So, what to do? Does this mean that one of the Stock ROM apps? is causing the issue? How to fix?
Many thanks for your help
yeahdisk said:
Thank you for this. My phone is fine in Safe Mode! I didn't think of this, as when I was relfashing the Rom I wasn't installing any additional apps - just the Androbench to check performance (always after checking that the problem was happening).
So, what to do? Does this mean that one of the Stock ROM apps? is causing the issue? How to fix?
Many thanks for your help
Click to expand...
Click to collapse
Get an app like System Panel 2. Set it to monitor all apps/system activity and check where the hangs comes from. Maybe even AndroBench is the culprit in your case.
Anyway, get a system monitor app that can log all app activity individually and see which app has the most cpu usage and which app has the most disk usage.
But by the fact that your phone is running extremely slow after reflash, I suspect the back-up/restore system. Maybe it downloads some corrupt data and hangs the system. If that is the case, a new Google Account may fix the problem. Start fresh.
OMG I took the memory card out and everything is working fantastic again
yeahdisk said:
OMG I took the memory card out and everything is working fantastic again
Click to expand...
Click to collapse
If the SD was your problem, check out the solution I found here: https://forum.xda-developers.com/showpost.php?p=80172348&postcount=19