Related
Just thought this might be useful to some of the newer users, a list of what I see as the most commonly asked questions, and some misunderstood terms.
What is the difference between Nand, Haret and SD:
Nand; refers to the devices internal memory, which is NAND Flash memory, and is used to hold what is commonly called 'a ROM'. It is this memory which holds the Operating System, and can be 'Flashed' to change the data on it, once flashed it is persistent in memory, meaning that if you remove all power sources it will not lose this data, this is also known as 'Non-volatile Memory'. Nand Flash refers to a specific type of Flash memory, and gets it's name from the way the memory cells are constructed.
SD; Refers to the MicroSD cards we use in our devices, these are also Nand Flash but typically have slower transfer rates than the Nand Flash we have inside the device. typically used to store data, they can also be used to store the Android OS when used with Haret installs.
Haret; often confused with SD. It actually refers to Haret.exe, which is a program used to launch Linux systems from within another OS, such as Windows Mobile, think of it as a Virtual machine system, which allows users to run another OS. In our case, Haret refers to running Android within WM, it does not replace WM in Nand ROM, it does replace it in RAM however, but only until powered down, after that WM will boot from Nand next time the device is powered on.
What is my Panel Type?:
Panel; This refers to the actual LCD panel hardware, there are 3 types in use on Kaiser, and although Type2 seems most common, there are also Types 1 and 3. When running WM the panel type is autodetected and the correct settings are used for the display, however Android has no autodetect, so we must tell the OS which type we are using at boot, in Haret installs this is done with a line in Default.txt, in Nand it is set in the NBH we use to flash the kernel and other boot files needed to run Android. Display issues such as odd pixel colouration, streaks or lines on the display, white screen when exiting sleep, and other noticeable display issues can usually be cured by changing the panel type.
Other useful terms:
NBH; This is the file extension of a file intended for flashing to Nand, most commonly used to flash WM or Android, it can also be used to flash radio or splash screen.
Bootloader/tricolour screen; Both are the same, it refers to the screen display you get if you hold the camera button, and press power, on this screen are a few useful pieces of information, device type, (e.g KAIS130), SPL version, (e.g SPL-3.29.Hard), in the bottom white area it will say 'serial' or if connected to a PC, 'usb'. Remember to remove the SD card before entering Bootloader mode, as the bootloader also scans the SD for a file called KASIimg.nbh, and will run the updater utility if one is found.
HardSPL; This is a specially designed SPL that allows us to flash the Nand with an NBH file that was not signed by HTC, it also prevents itself from being overwritten, so that it is usually possible to reflash as long as we can get into Bootloader mode, this means we can, ( usually ), recover from a bad/corrupt flash.
Build and ROM; In WM terms, a ROM usually refers to a complete, ready to install, single file NBH, custom version of WM. However with Android we do not use the single file approach, and therefore we do not usually use the term ROM. Build is what we usually call a custom Android install. This is roughly equivalent to the WM 'cooked ROM', since each build is designed and built in a particular way, and may be any of the different android 'flavours'.
Flavours; Mostly used to describe the versions of android, these are, in historical order
1.1 - un-named, released feb 2009
1.5 - Cupcake, released april 2009
1.6 - Donut, released sept 2009
2.0/2.1 - Eclair, released as 2.0, oct 2009, and as 2.1, Jan 2010
2.2 - Froyo, released may 2010
3.0 - Gingerbread, scheduled release date, sep-dec 2010.
Odex'ed: As stock, android builds are odex'ed. Odexing involves generating an odex file for each app, which slightly lowers the memory used by the system, and may also speed up execution of apps, the downside is that it is difficult to modify odexed builds in order to tweak or theme them.
DeOdex'ed: a deodexed build is one in which the odex files are moved into the apk's, which slightly increases the memory used by /system, but allows modifications and tweaks to be used.
Deodex Vs Odex: Odex uses less space in /system, boots quicker, especially the initial boot after installation, however themeing is impossible, and various tweaks and modifications probably won't work. Deodexed uses more space in /system, has a slower initial boot, subsequent boots are much quicker, but may be a little slower than odexed, theming is a lot easier, as are modifications and tweaking of the build. ( most custom builds are deodexed due to the ease of theming and modifying ).
Bootsplash/Bootanimation:
The bootsplash is the static picture that appears as soon as you boot the device, usually is stays for 20 seconds or so before being replaced by the scrolling text showing Linux is booting.
The Bootanimation is the animated screen you see after Linux has booted, and usually loops until Android is loaded.
Sim Pin/SIM lock:
SIM Pin is often confused with the SIM lock, the SIM pin is the code you have to enter before using the phone when you start it up, this code is stored on the SIM card itself, and until recently caused a lot of problems, since Android could not decode it properly, this has been fixed in some flavours, Eclair and Froyo, but is still an issue in older flavours, such as Donut.
Sim lock also known as provider lock is a method used my phone service providers to ensure that you only use their service by locking the phone so that it only accepts that providers SIM cards, this lock code is stored on the phone, and may be unlocked by entering a code, or by bypassing it using unlocking software, once unlocked the phone will accept any other providers SIM card.
PUK the PUK is the Personal Unlock Code, and is a code that unblocks a SIM that has been blocked by too many unsuccessful attempts to enter the Sim Pin code, ( usually 3 attempts), this code must be entered to unblock the SIM card, usually the PUK is provided with the SIM Card, however if it is lost then some providers may give you the code, if the SIM has been registered by you.
Please feel free to add to this
Back to Windows Mobile:
If you need to reflash Windows Mobile, for whatever reason, these are my preferred methods:
I recommend using a Card Reader and MicroSD adaptor for working with SD cards, it makes life so much easier than relying on the kaiser to transfer and rename files, since most of us are used to handling files in Windows.
Method 1
1. Download a Stock shipped ROM, do not go crazy getting the latest custom 6.5 ROM, in my experience these often cause problems, if you want to go to Custom ROM's then flash stock first.
2. Extract the RUU_Signed.NBH file from the .exe, ( I use 7zip for this, but other archive utilities my work, winzip, winrar etc), rename the file to KAISimg.nbh and copy to the root of a freshly formatted SD card.
3. Insert the SD card in your Kaiser, pres and hold camera button while pressing power, ( you only need to press power briefly, but keep the camera button pressed until you see the tricoloured screen).
4. Once you get the tricolour screen, ( bootloader ), it should change to a grey screen with blue instructions, basically, press the power button and let it flash.
5. Once flashed, simply pull the battery/press reset and let it go through the first boot process.
Troubleshooting
Common problems with this method are that it will just not recognise the flash file, leaving you at the bootloader screen, this is usually caused by wrongly formatted sd cards, the card must be formatted FAT32. Other reasons are file name issues, make sure you have not accidentally mistyped the filename, or renamed it as kaisimg.nbh.nbh.
Method 2:
If Method 1 fails then the alternative method is USB flashing:
1. Disable Activesync, by unchecking the 'USB' option in Connection settings.
2. Remove the SD and SIM cards from the Kaiser.
3. Press Camera+Power to enter Bootloader.
4 Connect the usb cable, ensure that is says 'USB' at the bottom of the screen.
5. Flash the Stock ROM, usually by double clicking the downloaded stock ROM exe file, allow it to flash, and wait until it is finished before removing the USB Cable.
Troubleshooting
There are a few potential issues with this method also, if this method fails try another stock rom, the last shipped ROM from HTC was Kaiser_HTC_ASIA_HK_WWE_3.34.721.2, this is a generic stock 6.1 rom and should be compatible with most if not all kaiser variants.
Useful Links:
ThoughtlessKyle's Why my Wifi doesn't Work Invaluable Information on recent WiFi Issues, A 'Must Read'......
LCD Panel Information
Tinboot thread ( the thread that launched Nand flashing on kaiser ).
SuperJMN's Android Issues roundup thread ( common problems, as yet unsolved )
Adding language support
Miscellaneous Notes.
Radio Version
Just as in Windows Mobile, Radio Version seems to play as vital a role on Android.
There are a number of problems that may be related to radio version, and just as in WM, the effects are sometimes surprising.
Audio: yes, just like WM the wrong radio version can cause audio issues, ranging from no audio, to more subtle issues such as call audio not working, even though all other audio events work fine.
Wifi: no surprise really, the radio stack controls wifi as well as the more common phone/network activities.
Data/Network: Obvious one, but there are a number of complicating factors here too, geographical location seems to affect radio version, for instance, in the USA, 1.71 radios may offer the best signal, and data rates, while in Europe, using 1.71 may cause a lot of 'No Signal' issues, where the phone seems to drop off the network, the solution is usually an older radio version, in the UK 1.65 seems the best choice for most users, I have also had reports of 1.65 being the best for South Africa, Asis, while Australia seems to do better on 1.70 or 1.71. This may be due to the technology in use in those countries.
GPS Maybe, not sure about this one, had at least one report that a radio downgrade from 1.71 to 1.65 seemed to help with GPS, as far as I am aware the GPS and the Radio stack are not related, but who knows for sure?
Great guide! I was thinking about making similar one myself, but couldn't find free time
I'll maybe try to add something this weekend
hello maybe a stupid question
what is the differents between odex and unodex
sorry for my bad english
kisses
Rose
Not sure if this is a general dumb newbie question but I'm having it across different Android builds. Occasionally I have to reset the phone without shutting Android down. When I restart, any apps that were running at the time have to be uninstalled and re-installed because they now crash on startup (with a "program has stopped working" error.) Is there anything I can do about this?
CassandraN said:
Not sure if this is a general dumb newbie question but I'm having it across different Android builds. Occasionally I have to reset the phone without shutting Android down. When I restart, any apps that were running at the time have to be uninstalled and re-installed because they now crash on startup (with a "program has stopped working" error.) Is there anything I can do about this?
Click to expand...
Click to collapse
Not really a dumb question, however it depends how you are resetting, the reset button is a bad idea, Battery Pull is the preferred method, ( say it with me class, 'Battery Pull Good, Reset Button Bad' ).
However, why do you have to reset without shutdown? This often leads to data corruption, since the OS does not get a chance to synchronise properly before it closes, ( not that a battery pull should be any better, but for some reason it seems to cause fewer problems than resets).
Thanks for the FAQ, it is extremely useful to noob or semi-noob like I am.
Thanks, that's why I decided to start it, and if one person finds it useful, it was worth it
say it with me class
Click to expand...
Click to collapse
This is just hilarious
BTW, I tried some of the reboot apps in the market, non of them seemed to work (on 2.1)
the original reboot menu that you get when you hold the power button did not work at all. it just hangs on the loading circle.
In Froyo however, things are a bit different. the reboot option shuts downs the device instead, I did not try any reboot app yet
Any ideas about this zenity?
zenity said:
Not really a dumb question, however it depends how you are resetting, the reset button is a bad idea, Battery Pull is the preferred method, ( say it with me class, 'Battery Pull Good, Reset Button Bad' ).
However, why do you have to reset without shutdown? This often leads to data corruption, since the OS does not get a chance to synchronise properly before it closes, ( not that a battery pull should be any better, but for some reason it seems to cause fewer problems than resets).
Click to expand...
Click to collapse
I usually battery pull (I lost my stylus and the cheap replacement won't fit in the reset hole ), but I still seem to have problems.
I think my problems are due to a rogue app eating all the CPU. My suspicions are Twitter or Swiftkey. The phone becomes so unresponsive that sometimes a hard reset is the only way to make it useable again. I'll try to avoid it in future if I possibly can.
Tried taskiller? Useful for watching your memory, and killing tasks if needed, osmonitor is also useful for, well monitoring the os
I have noticed that the system does get very unresponsive at times, and it usually means low memory, try an eclair build if you are using a CM6 based one, I usually get about 30+Mb free in normal conditions, and if things start to get too slow, well a tap on the taskiller widget sorts that out
@Duke911:
As far as I am aware there is no real reboot option, in any build, I think it's a kernel issue, or perhaps just not implemented correctly, the safest option is a power off, which performs a proper shutdown, I do know there have been a few issues with data corruption that may be associated with using reboot, or the reset button, since these may cause the system to shutdown to rapidly to sync any data that may be cached, it's similar to pulling an SD card out of the computer, there may be data left unwritten in cache, which is why there is a nice safe removal option
This is a cool wiki for Kaiser Android users! Thank you!
By OP request, I am making this thread a sticky and making some adjustments to the forum. Please PM me if you have any requests. Thanks.
Precious work, Zenity!!!
video call anyone?
Is there any chance of getting a build to support video calling?
Video calling will need working front camera driver at least, which is not supported yet, I do not know if anyone is actively working on this, however, at some time, someone will take up this challenge, just as they have with other things which did not work previously
Sent from my HTC Dream using Tapatalk
hello..
I just want to ask about polymod and cyanogenmod.
what is the function, are they different from eclair or froyo?
thanks ^^
CyanogenMod builds are all Modifications of base android releases, these are complete rebuilds of the system, and include many improvements over the original release.
Polymod is an Eclair Mod based on OpenEclair 1.3 and is modded in a different way to Cyanogen's methods and style.
Most Eclair and Froyo builds are ports and modifications of Cyanogen bases, ( in fact I don't think there are any Froyo builds that are not CM6 based).
For Donut things are different, most builds are modifications and ports of official releases, such as Myn's Warm Donut.
I have two Motorola 820HT Bluetooth headsets. From day one I had no problems with them. (they even worked better on the G2 than my TP2 and EVO 4g) I woke up last Friday to find the G2 trying to update. After the update every thing worked fine until I got a call at work. I listen to a LOT of music/radio/podcast etc.... anyway i was listing to some music and the phone rings, here's where the problems lies. After I hung up the ONLY way a can resume playing music though the headset is to turn them off, then turn them back on. It dose the same thing on both of them. I even tried my friends JBTH710 headset and had the same problem. I can see the numbers moving in the music player, but no audio comes out until I turn off then turn on. Has anyone else had this problem; and if so what did you do to fix it? Taking the phone back to T-mobile for a replacement (to get a phone without the update) is not a answer because without wifi calling I can't use the phone at home.
Just to be clear (I'm not the best typist in the world) If I get a call with Bluetooth parried to my phone and I want to listen to something though my headset after the call, ( it can be five hours after the call) I have to turn off the headset then turn them back on.
Thank you for any feedback that helps me or anyone with this problem solve it.
Having the same problem as you
I think I have figured it out its the new bluetooth 2.2 that was used with the OTA. I think if we can get the old one from the pre-OTA and adb push it to the system it could work. This problem has made my bluetooth radio useless in the car when I get a call and hang up it should go were it left off from the music or podcast but you can see its still playing but no sound. So always have to disconnect bluetooth and reconnect it for it to work again. So if anybody has the pre-OTA please use adb and pull the bluetooth and upload it to rapidshare or whoever you use to were I can try this and see if it fixes the problem.
My parrot evo 3k (Parrot v5.11c) won't connect with my G2. I haven't tried with original rom, but this problem exists on the Ota, CM RC3, and CM RC4. My G1 had a similar problem in some froyo builds, but I think it was fixed in RC1 or the nighties. I know it worked great from dream-sapphire 230 or so on. Can a BT from older builds be pushed in to recent builds?
Tried adb pushing the old bluetooth.apk from the first rom to the new ota and it didn't work. I think its the new radio in the ota that messed up the bluetooth from working right I think I'm going to maybe flash the old radio and see if that works. And if anyone is experiencing this issue and you have solved the problem please let us know how you did it .
Sent from my T-Mobile 7 inch space banana
any updates on this issue
G2 TMOBILE OTA BROKE UP MY BLUETOOTH.. Here is how i fixed it...
I AM SURE THAT EVERYONE ALREADY KNOWS THIS. BUT I WANT TO SAY UP FRONT.. WHENEVER YOU TRY TO ROOT YOUR PHONE AND CHANGE THE ROM, YOU RUN THE RISK OF PERMANENTLY BRICKING YOUR PHONE.
With that being said, I will start my rant.
ISSUE: I would be connected with my stereo headset listening to music. The
phone would ring an the music paused. I was able to take the call on the headset without issue. After hanging up on the call, the music would never resume on the headset. The music was streaming on the device but no music on the headset. I had to toggle Bluetooth off then back on to get it to work again. It seemed that the A2DP bluetooth connection would get corupted everytime a call was replaced or received. I tried 5 different A2DP enabled bluetooth devices and they all did the same thing. These 5 bluetooth devices all worked just fine with my Mytouch and my G1. So it definatelty was the phone. T-mobile tried to tell me that all of my bluetooth devices must have been broken. They are the thing that is broken. On my G2, I have had a lot of connectivity issues with bluetooth and wifi after that stupid OTA update.
QUICK WORKAROUND but at a price : Just go to bluetooth settings and toggle off the phone bluetooth connection but leave the media connected. You will need to take all calls on the phone handset but the music (A2DP) connection will not be broken when a call is placed or received. If you have multiple bluetooth devices, you need to change this setting for each device.
T-mobile claimed that it was the radio firmware From HTC.
T-Mobile tried to tell me that it was an HTC issue and HTC tried to tell me that it was a T-mobile issue.
HTC was correct and T-Mobile is a bunch of morons as usual.
My PERMANENT fix Listed below... 1 I rooted the phone. (Permanent Root) 2I installed Rom Manager and selected "Flash ClockworkMod Recovery" (v2.5.1.3) then I rebooted into recovery and did a backup. That will get you a backup of your stock phone. 3Next, I wiped all data on the phone (from the recovery screen) and then installed Cyanogen 6.1.1 for the G2 (CyanogenMod-6.1.1-vision) 4Rebooted into Recovery and installed google apps.
MY BLUETOOTH NOW ROCKS! WORKS PERFECTLY. The WIFIis also working flawlessly now.
A few issues you should be aware of before changing the ROM. 1 You will lose swype if you don't grab the 2 swype files from your phone right after you root. 2 Before doing ANYTHING,, go into your settings and let Google back up your Data then manually initiate a sync in settings so you know that your app data has been backed up to google, Android will pull the T-Mobile WIFI CALIING app back to the phone automatically after you install the Cyanogen mod and sign into your google account on the phone. I also read somewhere that wifi calling was included in cyanogen. So I am not sure which is the reason it ends back up on your phone with cyanogen but it does. 3 You will also need to install the google package to get all your google apps back.
..........................................................................................................
..........................................................................................................
Exactly what I did. (NO ROOM FOR MISTAKES ON THE ROOTING !!!.. BE CAREFUL, HAVE A FULLY CHARGED BATTERY, TAKE YOUR TIME AND HAVE NO DISTRACTIONS!)
Make sure that you fully read the whole Rooting Procedure 3 times before you attempt it.
ROOTING ........
I rooted from the link below.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
There is a lot of info on the above linked page.. below are the lines from where i started and stopped. I did no more than what is in between the following start and end lines. (you can just search for the text on the page to find quickly)
STARTING FROM THE LINE: Rooting the Vision (G2/DZ) and DHD
ENDING ON THE LINE: Did it work? Here's what you're looking for:
YOUR G2 SHOULD NOW BE ROOTED AT THIS POINT BEFORE CONTINUING ON.
......................................................................................................
......................................................................................................
BACKING UP SWYPE
DOWNLOAD ASTRO FILEMANAGER FROM THE MARKET.
There are 2 files you must copy from phone memory to SD card.
These files are "Swype.apk" and "libSwypeCore.so"
The apk file is located in /system/app and
the so file is located in /system/lib
Both of these locations are in the phone memory an not the SD card.
You just copy and paste to get them to your sd card.
MAKE SURE YOU DO THIS IF YOU DON'T WANT TO LOOSE SWYPE.
BACKUP WI-FI CALLING AND QUICK OFFICE
Both files are located in /system/apps (on phone memory)
Copy the following 2 files to your SD card
WI-FI Calling install file - "MS-HTCVISION-KNT20-02.apk"
QuickOffice install file - "Quickoffice.apk"
......................................................................................................
AFTER THE PHONE HAS BEEN SUCCESSFULLY ROOTED AND YOU REMEBERED TO GRAB THE 2 SWYPE FILES
INSTALL ROM MANAGER....
Go to the market and install ROM Manager. Start Rom Manager.
Select "Flash ClockworkMod Recovery" (v2.5.1.3) when it is done installing
select "Reboot into Recovery" to make sure it works. Once in recovery highlight and select "reboot system now" After phone has booted back up, proceed with steps below.
......................................................................................................
DOWNLOAD CYANOGEN ROM 6.1.1 ......
http://forum.cyanogenmod.com/files/file/186-update-cm-611-vision-signedzip/
DOWNLOAD GOOGLE APPS FILE.....
http://forum.cyanogenmod.com/files/download/152-google-addon-hdpi-20101114/
(I would recommend only downloading this from cyanogen and nowhere else. There is a corrupt version floating around on a few different sites with the same name.)
TO INSTALL CYANOGEN MOD.....
1Connect your phone to PC and mount the SD card. Copy the cyanogen mod file and the google apps file to the root of the G2's SD card.
(update-cm-6.1.1-vision-signed.zip and gapps-hdpi-20101114-signed.zip)
2Boot your phone into Recovery
(While in recovery highlight & select with optical trackball)
3Select "backup and restore" then select "backup"
(This will backup your stock OS, Apps and Data from phone to sd card)
4Select "wipe data/factory reset" Scroll down to "Yes -- delete all user data"
5Select "install zip from sd card" then select "choose zip from sd card"
then scroll to the cyanogen mod file (update-cm-6.1.1-vision-signed.zip) and select it. When the process is complete press the back button to go back to the main recovery menu and select "reboot system now"
6You need to install the google apps now. After the phone boots up with cyanogen, reboot the phone back into recovery. Select "install zip from sd card" then select "choose zip from sd card" then scroll to the google install file (gapps-hdpi-20101114-signed.zip) and select it. When the process is complete press the back button to go back to the main recovery menu and select "reboot system now"
7Restore Swype
Copy from the SD card (it is on your SD card wherever you put it) "libSwypeCore.so" to /system/lib (which is phone memory. I used an app called RootExplorer from the market. I needed to use that to make the /system/lib directory writable. When you first start RootExplorer, the superuser app will pop up a permission box. Make sure you select "allow" or this won't work.)
Then go in astro filemanager, navigate to "Swype.apk" (it is on your SD card wherever you put it) and tap it to install.
Now you need to make Swype active..
- (from the home screen) Select "MENU" then "Settings" then "Language & keyboard"
- Tick on Swype
- Go to your text messaging app (make sure physical phone keyboard is closed)
- Tap in the text box to type a message.
- Long press on text entry box and select "Input method"
- Then select Swype
You will then have your Swype back.
8 Restore WI-FI Calling if it isn't already installed.
go in astro filemanager, navigate to "MS-HTCVISION-KNT20-02.apk" (it is on your SD card wherever you put it) and tap it to install.
9 Restore Quick Office.
go in astro filemanager, navigate to "Quickoffice.apk" (it is on your SD card wherever you put it) and tap it to install.
.........................................................................................................
WHEN YOU HAVE YOUR PHONE ALL SET UP JUST THE WAY YOU WANT, DO YOURSELF A FAVOR..... REBOOT TO RECOVERY AND RUN A BACKUP.
*************************************************
Enjoy your fixed bluetooth
Wow, what a lot of crap to fix someones mistake......
*************************************************
I just flashed a new ROM and now the Bluetooth works like it should. Gingervillian 1.5 awesome.
Sent from my HTC Vision using XDA App
I appreciate your detailed explanation! I am a complete noob. I just rooted my g2 a few days ago and trying to read as much as I can and get up to speed.
I do have a question for you as far as backing up swype and other apps. Can you just use titanium backup to back up your apps like swype, quickoffice etc? Thanks in advance.
I was thinking of doing your method mentioned above as well as using titanium backup just because I'm paranoid about losing apps/bricking my phone, etc. Trying to be as careful as possible.
(Backed up and still running stock rom on rooted g2, have installed oc kernel after backing up)
Well, I've been using InsertCoin-Vision v1.3 ROM (which in my opinion are among the bests) on my T-Mobile G2. With this ROM and with VIRTUOUS FUSION ROM by rmk I have no problems with the bluetooth A2DP.
Nevertheless, I had a A2DP bluetooth problem (reported here forums.t-mobile.com/t5/T-Mobile-G2/Post-OTA-Update-BlueTooth-issue/td-p/542367): when I connect my phone to the car stereo player (JVC AVX-33) thru bluetooth A2DP the audio cuts out and skips all the time when the music is playing (I use PowerAmp application). It happens with almost ALL ROMs, no matter if it's stock, CM6, CM7, xboarders or RMK's (Virtuous G-Lite for example)... except with the VIRTUOUS FUSION and InsertCoin-Vision (v1.2 or 1.3) !!!!
Well, I'm very happy about this fact, but I'd like to know if you could explain to me the difference between Virtuous Fusion or InsertCoin-Vision (where the problem is solved) and Virtuous G-Lite or Cyanogen7 (where the problem occurs) in terms of bluetooth libs, config, etc., that could have solved that problem.
By the way, I used to listen music with the same car stereo and my old Motorola Milestone and I had no problem at all.
Thanks in advance and excuse me to bother you with this kind of question.
Best regards,
Tiago Peixoto.
My problem is that my cars headunit will not automatically connect to my phone or visa versa. i have to manually connect the phone to the car. Its really anoying. Now that I have perm root I have been testing several ROMs and have yet to find one that will actually fix the problem mentioned throughout this post. I just installed the Virtious Unity ROM but have yet to see if the problem is gone. With the Virtious Sense ROM I still had the same problem.
@ iagocpeixoto I've had the same issue with the audio cutting in and out in the past on stock ROM. The problem was that WiFi was also enabled. Its weird but disabling WiFi will eliminate that fading in and out while listening to audio through Bluetooth.
Good afternoon, dear xda-developers forum members.
I really hope to find some help here.
In last two months I had the following issues:
1. This one happened two times already: after using my phone as a flash in windows 7 and "safely removal" of it, all my applications which were installed on SD card were saying that "Application is no longer installed" when I tried to run it, although other documents and files were readable from ASTRO File Manager, i.e. SD card was mounted. In Settings->Applications all these applications had black icons with SD card image on it and rather with package name than regular application name(for example com.navitel instead of regular Navitel, etc.). I've restored all these applications from Titanium Backup, but I'm afraid that there is something more disappeared also which I don't know about.
2. My "Android" folder on sd card became a file with weird contents(this folder was used for NFS Shift data only). I couldn't restore it. Again: if this folder corrupted, then there is definitely something else also corrupted.
After I saw these things for the first time, I used Windows checkdisk with auto-fix errors. It found a lot of files and put it into "FOUND.000" directory. I recognized in these files few apk-files of installed applications from SD and also few images from my SD. Then I restored applications to SD card and for some time it seemed ok. But one time it happened again.
My assumption is that Android fails to re-mount SD card after I disconnect it from PC.
I don't know what to do... is it Android bug or is it Desire bug or what? I swear that I ALWAYS make "safe USB removal" in Windows before disconnect the USB-cable and I ALWAYS wait for the message "It's now safe to disconnect your device".
I'm very disappointed with all that Please, advise me something useful...
P.S.: If needed I can give you any debug information you want, I'm a programmer, so I've been around
You could try to format your SD card, just backup the contents first, see if that works. As for Android, it does a pretty good job of mounting straight after. What version of Android are you running?
GoogleJelly said:
You could try to format your SD card, just backup the contents first, see if that works. As for Android, it does a pretty good job of mounting straight after.
Click to expand...
Click to collapse
I will, but strange that it happened, because I formatted the flash before using it for the first time...
I have two assumptions:
Maybe I shouldn't press power button to switch the screen off just after disconnecting USB cable from PC. I was doing that as a habit, because every time you disconnect your phone from PC, the screen turns on.
Maybe I shouldn't try to run application which is installed on SD just after disconnecting phone from PC. Maybe I should have waited for a minute. I've tried to do it once, because I wanted to see the result as soon as possible, so the phone said that "Application is no longer installed", I though that Android haven't mount SD yet and tried later. It worked. But next time when I used USB cable, all SD-card apps became uninstalled.
GoogleJelly said:
What version of Android are you running?
Click to expand...
Click to collapse
I'm sorry, forgot to mention. I'm using HTC Desire with Android 2.2(2.10.405.2).
Fast Boot option may be the culprit
In case anyone checks this old thread...
CUT TO THE SOLUTION BELOW -- SEARCH FOR ////
Some (not all) of my apps moved to SD (all by Titanium Backup Pro) have begun to disappear and (sometimes) reappear without warning after I began to add and delete large Virtual Machines created in QEMU from my 16GB SanDisc class 10 microSD card on my HTC Droid Incredible running rooted stock Verizon Android Froyo 2.2.3. I know this thread is far from my phone's "home base", but from what I can tell this problem with disappearing apps located on an sdcard is NOT determined by hardware or even Android version.
I also happen to use LauncherPro by Federico Carnales instead of the built-in HTC Sense launcher. I noted elsewhere on XDA that a user had suggested that because at least some (maybe all) launchers start before the SD Card that this may be a problem, especially if changes are made to the sdcard that the launcher did not perform, or was not active during their performance by other apps such as Titanium Backup. That fits my situation, because I unmounted the SD, physically removed it to a PC, and added/deleted large VM files to save (lots) of time. No problems of this sort before I did this, so there must be some connection.
I noted that other users have tried reformatting SD, substituting different brands of SD, using newer/older SD etc. None of these reliably helped. So I skipped these options.
//// The (simple!) solution I tried that SEEMS to work (only time will tell!) is buried in the main Android Settings (accessed from the Menu button while in Home screen). Under "Applications" there is a setting "Fast Boot" that I checked long ago and forgot about (it seemed like a good thing to do at the time). The text warns "Turn off to use some Market apps" (that shows the age of my 2-yr old used phone and Android OS -- ohmygosh!-- because it refers to Market rather than Google Play Store!) Anyway, I unchecked the option and rebooted the phone.
Yes, it took a bit longer to boot (maybe a whole minute!), but after waiting about another minute ALL my home screen apps had normal icons and loaded properly. Titanium Backup Pro batch scenarios confirmed there were no apps in a forced uninstalled state (i.e. I had not done the deed, the system somehow had done it or at least rendered the apps "invisible" to Titanium, which decided they needed reinstallation).
The only odd behaviour was that auto brightness was turned off after I unchecked Fast Boot and rebooted. Going into Android Settings > Display and rechecking "auto brightness" took care of that. No other oddities or strange behaviours thus far (but it has only been about an hour).
I will report back here on this thread only (Samsung Fascinate > Fascinate Q&A > What just happend? apps on sdcard) if anything else requires reporting. Silence implies success!
link: http://forum.xda-developers.com/showthread.php?t=1873670
(I am copying this post to other relevant threads, but will not post anything further elsewhere -- only there. This is a bit arbitrary (although this thread appears to be the most recent active one on this topic), but I hope this approach pleases the XDA sysops/admins) :angel:
[Q] "The application is not registered" error when I launch kindle reader. Ugh.
Very few search results for this error, so I'm out of ideas. It has come up once before but the thread is closed -->
http://forum.xda-developers.com/showthread.php?t=1356441
My reader worked fine for 8 months. Then it updated to version 3.7.0.108.
Now when I click any of the "tabs" such as home, archive, on device, etc... I get this:
"The application is not registered. Trying to register it now. Please try again in a few seconds..."
No book will open, I get an "Invalid Item" error and it suggests I redownload it.
I have a rooted 1st generation KF with GoLauncher on it and ...I dunno if it's a custom rom or what.
I get a blue kindle fire logo when I first power up. I just installed the recommended stuff with the Kindle Fire Utility.
Fixes I've tried:
1. Restarting the device
2. Force stopping the app, then clearing the cache.
3. Going to the play store and choosing "Uninstall". The problem is, this doesn't really uninstall the app, it says something like "this will uninstall all updates to the kindle reader". If I go to settings --> applications, the option to fully uninstall is grayed out.
After doing the google play 'uninstall', the device freezes if I try to launch the reader.
4. Manually reinstalling/updating via the google play store. Now it launches and the device doesn't freeze, but I still get the errors. Also my books are gone but that's no biggie.
I also called tech support. They had me unregister my device from settings --> My Account... and eventually re-register it.
They also had me clear cache. Then those things didn't work they elevated me to level 2 tech support.
I foolishly mentioned I had the go launcher installed, they refused to help any further and insisted the 3rd party launcher was the cause of the problem, and my only fix is to factory reset and stick to the stock software.
So, if you made it this far, thanks for listening... now what?
If you have Root Explorer (or equivelent) for access to system apk files, you could try deleting that app from the /system/app folder, restart the device, go back to the system apps, paste another copy (or version) of that app in there and set permissions to match the other apks in the folder, reboot and hope it might correct the issue. It sounds like a software glitch from the getgo even on un-rooted devices.
howdy, thanks for the idea.
I have root explorer and root access, but when I go to rename or delete anything in that folder, I get "the file cannot be renamed because the file system is read only".
Also, I'm only assuming it's the app called "Kindle for Otter" which is the only one with the traditional kindle reader icon of a dude under a tree reading.
Is there an alternative reader that's still very convenient? Like I don't have to download books via USB or anything, it just monitors the appropriate folders and my freshly-purchased books appear in the list?
CreeDo said:
howdy, thanks for the idea.
I have root explorer and root access, but when I go to rename or delete anything in that folder, I get "the file cannot be renamed because the file system is read only".
Also, I'm only assuming it's the app called "Kindle for Otter" which is the only one with the traditional kindle reader icon of a dude under a tree reading.
Is there an alternative reader that's still very convenient? Like I don't have to download books via USB or anything, it just monitors the appropriate folders and my freshly-purchased books appear in the list?
Click to expand...
Click to collapse
You must just be rooted and not have any custom ROM installed otherwise you could mount the system/app folder as r/w, meaning you probably don't have Superuser installed? Superuser is supposed to be installed when you root the device with the Kindle Utility but I couldn't get it to do it. Since you are rooted then you could try the MoDoCo ROM as it is based on Amazon's own 6.3.1 software and includes the Kindle Reader, Amazon app store and everything that is included with the stock software. In addition it includes the Google services framework and Playstore so you can have the best of both worlds, Google and Amazon. It runs much better than stock and I just flashed it onto my wife's Kindle and she is pretty satisfied with it.
There are plenty of decent reader apps and my suggestion would be try many different ones until you find a suitable one.
Josepho1997 said:
Actually, you just have to click the button on the top of root explorer. It should says "Mount R/W" Click it. Now you should be able to delete it and replace it.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Yes that is true but if Superuser (or equivelent) isnt present it doesnt work to well
Well, the mountR/W thing worked, and since then I've gone through a bunch of stuff.
And I'm back to square one. But read anyway if you're bored.
I'm a the point where I could reluctantly nuke everything and start over, I guess that would involve reflashing the rom
and reinstalling all apps?
Here's what I've tried:
• Replaced kindleforotter.apk, set permissions, and rebooted, when the kindle came back up it went straight to the stock launcher... weird.
Maybe cuz GoLauncher coincidentally updated.
• At this point I should click that APK, right? But, curious, I went to my books tab.
All my books are there but missing covers. Some have a down arrow/download icon, others don't.
• 4 books without the icon successfully redownloaded after an error, and were readable.
Sadly these are all older books and the other 20 or 30 books would not do anything when tapped.
• Next I tried reinstalling the app by clicking the kindleforotter.apk I downloaded. It reinstalled, I rebooted,
clicking the shortcut still doesn't work but I went back to the books tab in my kindle launcher.
Now, none of the items launch. The "Invalid Title" items give that error again, but this time they do not redownload.
• I tried removing everything from sdcard/Books and sdcard/Kindle and rebooting. Now only those 4 'lucky' books show up.
But they no longer open when tapped. Looks like it's trying to launch the reader but it crashes.
• Tried manually resending the latest book to my kindle via Amazon's website. It didn't show up.
• So I clicked Sync under my settings icon, and that really hosed it. The kindle launcher would infinitely crash and reopen.
• Since that's worse than the original issue I just updated the reader via the play store, getting myself back to square one.
Thanks if anyone has any other ideas... or some less painful way to reinstall this app completely without wiping out everything.
Sounds like a big mess.....you might just have to start over from scratch. At least that "should" clear up the misc. errors you're receiving. You'd have to re-root if but that process is simple. Reinstalling apps might take a little time but would be worth it if it corrects the issue. The Kindle's stock software (or any software) is not immune to undesirable performance.
One basic correction attempt with software and operating systems is to wipe it clean and re-install. I've had many PCs that had to be wiped and the OS re-installed to fix messed up stuff. Usually we try to re-install apps first to see if it corrects it......sounds like you've already done that.
You could always just find an alternative reader
Howdy... I went ahead and tried support one more time (sometimes you get lucky) but they had no ideas other than a factory reset. I'm gonna look into modaco.
edit: on the off chance you come back to this thread,
I factory reset, installed modaco via TWRP, have one problem.
Books work fine. But I can't access my apps.
When I click the "Apps" tab at the top, the screen flashes briefly and then I'm right back to the usual home screen
(aka the default kindle launcher screen).
I seem to remember a notification (with an amazon icon) about pending app downloads, in the bar at the top.
I skipped over it to check on my books. Now it's gone, and I can't get it back or view a list of apps on the system.
What gives?
CreeDo said:
Howdy... I went ahead and tried support one more time (sometimes you get lucky) but they had no ideas other than a factory reset. I'm gonna look into modaco.
edit: on the off chance you come back to this thread,
I factory reset, installed modaco via TWRP, have one problem.
Books work fine. But I can't access my apps.
When I click the "Apps" tab at the top, the screen flashes briefly and then I'm right back to the usual home screen
(aka the default kindle launcher screen).
I seem to remember a notification (with an amazon icon) about pending app downloads, in the bar at the top.
I skipped over it to check on my books. Now it's gone, and I can't get it back or view a list of apps on the system.
What gives?
Click to expand...
Click to collapse
That's odd......I never experienced that with MoDaCo. Did you wipe everything before you flashed MoDaCo (cache, dalvik, factory reset and system)? There were slight bugs with MoDaCo I noticed but nothing like that. Try reflashing but dont wipe sd card
guitarman2010 said:
That's odd......I never experienced that with MoDaCo. Did you wipe everything before you flashed MoDaCo (cache, dalvik, factory reset and system)? There were slight bugs with MoDaCo I noticed but nothing like that. Try reflashing but dont wipe sd card
Click to expand...
Click to collapse
I'll see if I can do that. One worry I had... I see modaco is offered in more than one place, and seems to have some options with the installation...
can you point me to a specific zip file that you know for sure is a good working one? Otherwise, I'll assume my zip is good but my wipe wasn't. I just factory reset and never messed with dalvik and the rest, I'm guessing that's all important...
CreeDo said:
Very few search results for this error, so I'm out of ideas. It has come up once before but the thread is closed -->
http://forum.xda-developers.com/showthread.php?t=1356441
My reader worked fine for 8 months. Then it updated to version 3.7.0.108.
?
Click to expand...
Click to collapse
I had the same problem. Solved it by going back to an earlier version of the app.3.6.0.87.
Hey, just wanted to thank you, I reinstalled modaco, but first did the cache wipe and dalvid wipe from the TWRP menus. Apps tab works fine now. Books too.
So far only one minor hiccup... the apps I had formerly installed via GoLauncher. I logged into google play, redownloaded one of them (DrawSomething) and specified that it send the app to my Kindle Fire from the dropdown. It gave me something like "this app will be installed shortly". But I never got anything... no download, no notification. Did it a second time and same deal. Eventually I downloaded it from the Amazon app store, but I'm worried apps from Google Play won't work easily anymore.
Do you know what I should do if I need an app from Google Play?
Had same problem
In case it helps anyone else. I had the same problem. Turns out that the google play store (which remember doesn't come standard with a Fire) had updated the Amazon Kindle application. I went into the play store and uninstalled (un-updated) the Amazon Kindle app and then everything worked.
Good Luck!
Old version solved it!
mochamoo said:
I had the same problem. Solved it by going back to an earlier version of the app.3.6.0.87.
Click to expand...
Click to collapse
I have a rooted 1st gen KF running a cyanogen ICS ROM where the Kindle app had been working fine for a while, but suddenly wasn't registered and I couldn't even get the register dialog to display. Found the 3.6.0.87 apk online, installed it and it works fine now.
FYI 3.6.0.87 works on non rooted
pofigster said:
I have a rooted 1st gen KF running a cyanogen ICS ROM where the Kindle app had been working fine for a while, but suddenly wasn't registered and I couldn't even get the register dialog to display. Found the 3.6.0.87 apk online, installed it and it works fine now.
Click to expand...
Click to collapse
This fixes the same problem for non-rooted Kindle Fires where you are running an sideloaded launcher and the Kindle book app and need to reregister.
Hello,
I have had my HTC One M8 for a while now but I wasn't really happy with the soundquality while playing through my headphones, so I looked for ways to improve it. I found a few methods and finally decided to give it a try. These methods require a root so yesterday I have rooted my phone for the first time. Unfortunately I am experiencing some problems now.
The rooting process went without too much trouble. I used hasoon2000's toolkit and have TWRP version 2.7.0.2 installed as recovery and used it to install the provided SuperSU, which didn't work at first. On the forums I found a newer version and installed that one, updated it and got it to work.
Now this is where I think I messed up: I read somewhere that when rooted, you are able to delete pre-installed apps from the phone. I downloaded SD maid and deleted Kid Mode, Zoe and 7digital. When I deleted Kid Mode I got an error saying it has crashed. I tapped away the error but from this point I couldn't go back to my homescreen anymore because my launcher kept crashing (com.htc.launcher crashed). I rebooted the phone and the launcher worked again, but the phone still seemed to be buggy.
After this I tried to install the snapdragon audio+ (this was my first choice for an equalizer). I downloaded the apk and moved it to the system folder using ES file manager. I installed but when I tried to use it (through settings in google play music app) my phone would crash. I uninstalled it and tried again, but when I tried to move the apk to the system map like before, my phone would crash everytime. I then found out the file I used doesn't work for lollipop so I figured that's what caused the crashes.
My next move was to try and install viper4android. I downloaded it from the Play Store and opened it. It told me it needed an installation of BusyBox so I downloaded that too. But when I opened the BusyBox app and clicked install my phone would crash again. After some searching I found that the HTC One M8 requires BusyBox to be flashed manually so I downloaded the file but when I tried to load it onto my phone I noticed this wasn't possible anymore.
Now when I connect my phone to my PC the PC recognizes it, but when I open the map in Windows Explorer it only shows three maps; .showme, _nero_sync and Ringtones. I know there should be more as they were there before. It also shows my phone's capacity as a total of 10GB (shouldn't this be 16GB?). Also when I try to connect it with Sync Manager it gives me an error everytime I reconnect the phone; Device unavailable. Please reconnect your device [4].
I have tried to reset the phone through settings, wipe with TWRP and fix permissions with TWRP. I also tried reinstalling Sync Manager and the drivers on my PC. What I'm thinking now is I maybe have done something wrong in the ES file explorer that would make the folders unaccessible.
My phone is running stock android 5.0.1 and my PC Windows 7 64-bit.
I hope someone can help me, Thanks.
P.S: Sorry for the long post, I figured I'd give as much info as possible.
@Steef076 First update recovery to the latest one (2.8.6.0)
Second if you go and delete vital or integrated parts of the stock rom you will get a lot of bugs. Third, viper4android requires to write system and you can't write system with the stock kernel, you need an unsecured kernel or unsecure it yourself.
10GB is right since 6 is eaten by android. At this point I would just revert to a backup or install any custom rom around here. Most are close to stock and with no bloatware and come with root. You can even clean them further using a tool called ROM Cleaner. It will most likely solve all your problems
Did the deleted system apps reappear after reboot, or do they remain "uninstalled"? If the system is write protected like TempestZ states, any deleted system apps should reappear after a reboot.
Revert your nandroid to restore the system apps. And you didn't make a nandroid, you really should before making any system modifications for the very reason that it allows you to revert if you run into problems.
Another good practice, is if you don't know what effect deleting a system app will have (such as "safe to delete" lists that can sometimes be found on XDA) you should first freeze the app with Titanium Backup. If freezing doesn't cause any issues, then go ahead and delete. If you do have issues, just unfreeze the app.
Steef076 said:
Now when I connect my phone to my PC the PC recognizes it, but when I open the map in Windows Explorer it only shows three maps; .showme, _nero_sync and Ringtones. I know there should be more as they were there before. It also shows my phone's capacity as a total of 10GB (shouldn't this be 16GB?). Also when I try to connect it with Sync Manager it gives me an error everytime I reconnect the phone; Device unavailable. Please reconnect your device [4].
Click to expand...
Click to collapse
No, Windows will never show 16 GB. It only shows "internal storage" partition, or the user accessible portion of the storage. A good chunk is reserved for the OS.
Does what is shown in Windows differ from what is shown in ES if you browse to internal storage?
Thanks for the replies. @TempestZ @redpoint73
First of all I managed to update twrp to 2.8.6.0 using adb/fastboot.
To answer your question @redpoint73 the system apps I had deleted indeed reappeared after reboot. Also I didn't make a nandroid before I deleted the files, as I did not even know this was possible. Now I have made a nandroid of my stock ROM that is working decently, except for the TV app keeps crashing (I'm not opening it) and the connection to the PC is not working properly (not sure if this is ROM based?). I have noticed when the phone is in recovery I CAN see the folders through windows explorer. HTC sync manager still doesn't find it though. I am working on finding a proper stock ROM or maybe flash a custom one to see if that will fix it.
I understand now that the OS is taking up the storage space. The space windows is showing is the same as ES file manager so I guess this is fine.
HTC Sync is a hot mess. It often causes more troubles than it solves.
One thing you can try (to see if it fixes the USB connectivity) is uninstall HTC Sync and all HTC drivers. Than connect the phone. Don't let it install HTC Sync. Go to Windows Device Manager, find the device. Then pick the option to manually select the drivers, and pick the generic "Android MTP device" (or something to that effect) drivers.
This doesn't work for everyone. But it worked for me to be able to "see" the internal storage of my M8 on my home PC (Win 7). Annoyingly, it seems to vary from one PC to another. My work laptop (also Win 7) works fine with HTC Sync.
Steef076 said:
So if I understand correctly, 'version-main' is the same as 'firmware' and 'software number' (found in settings)? If so, my current firmware seems to be 4.19.114.2.
Now, what you're saying is I should do an OTA but this isn't possible because I have a custom recovery right?
Also, when I want to flash stock rom and stock recovery or do a nand don't I need the files that fit my cidnum? How would your file work for me?
Click to expand...
Click to collapse
If yours already on 4.19.114.2 then no need to do OTA as that the latest.
and my backup will bring back your device back to stock as you first bought it when restore with a full wipe.
Try to solve your problem first, only when you really need the backup then only I will upload ... let me know
ckpv5 said:
If yours already on 4.19.114.2 then no need to do OTA as that the latest.
and my backup will bring back your device back to stock as you first bought it when restore with a full wipe.
Try to solve your problem first, only when you really need the backup then only I will upload ... let me know
Click to expand...
Click to collapse
Hello, sorry for the late reply.
I have decided to give a custom ROM a try. I now have ARHD 41.0 installed and it seems this took care of my problems. All the maps are showing in windows explorer and HTC sync manager is connecting properly with my phone again. Also no more crashing apps. Your backup would still be of much use for me as I am not sure I want to stick with a custom ROM and therefore would like to have a stock ROM backup.
Thanks in advance.