Related
Goodevening,
I'm a proud user from the TP2 from the first day it came in holland. Just got everything with SPB Backup from my old HTC Herald to my TP2 and everything works fine! Fast GPS, no extra mouse anymore... eaven de sound when I call sounds perfect!!!! TomTom takes the Mapshare updates automaticly come on my phone with the new update of tomtom home! I Like it!!! I did modify the phone to my hand, but with the original stock ROM.
But still I have a few questions about the phone, I did try everything, searcht but no resulst... Because i've got the most of the tweaks for my TP2 from here, I thaught I will ask it here!
1. My brother said there was a new Opera browser availble, this is true. 9.7 beta (running on 9.5 stable) my quistion is how I can update the build in opera in TF3D2.
2. Are there updates for TF3D2, when yes... where can I download these?
3. When I try to run Windows Update, I get the following message:
Code:
Error
The Connection with the updateserver isn't availble. Check your dataconnectionsettings and check if the date and time of the device are setted right.
NOTE: Translated from Dutch language.
So I sync my time with my PC, so my device time is right, but stil id doesn't work. The strange thing, a few days before I did buy the phone they did update windows on 17-04-09 23:09 says my screen on the last check. How can I update?
4. How do I get the battery info (and maybe other information) in my notification screen? (Seems like the screen I added)
Now only my provider is standing there, and the message: "no new notifications". And some time from my messenger. I think thats waist of space, so I want more there (like BT on and making of or that kind of stuf!)
5. How can I delete 1 entry in my call history from TF3D2? I know you can delete the entire call history from 1 contact by your contact, but some time I want to delete 1 entry in there. A long press doesn't work, then it's going to call the contact back.
That was it for now I think!
Wainting for the beautifull answers to make my TP2 really mine
Hope you guys can read my crapy English!
Already thanks!
1) Yep you can install it as normal
2) Dont know...
3) I also get that, and would like to know how to fix.
4) http://forum.xda-developers.com/showthread.php?t=530281&highlight=monx install MONX_RHODIUM_LARGE_TITLEBAR.ZIP
5) You tried holding your finger on the entry for the options to come up?
elliott_stocks said:
1) Yep you can install it as normal
2) Dont know...
3) I also get that, and would like to know how to fix.
4) http://forum.xda-developers.com/showthread.php?t=530281&highlight=monx install MONX_RHODIUM_LARGE_TITLEBAR.ZIP
5) You tried holding your finger on the entry for the options to come up?
Click to expand...
Click to collapse
1. Alright I will try when i've got some time!
2. Someone else?
3. Someone else?
4. Nice it works thanks!
5. Yes, when I tap it long, it's going to call... that's still the same whith the time a make my first post Read back and see that I sayd that! It's going to call, and no options menu coming up!
rolfie23 said:
Goodevening,
[....]
3. When I try to run Windows Update, I get the following message:
Code:
Error
The Connection with the updateserver isn't availble. Check your dataconnectionsettings and check if the date and time of the device are setted right.
NOTE: Translated from Dutch language.
So I sync my time with my PC, so my device time is right, but stil id doesn't work. The strange thing, a few days before I did buy the phone they did update windows on 17-04-09 23:09 says my screen on the last check. How can I update?
[.....]
Click to expand...
Click to collapse
Go see this page:
http://social.microsoft.com/Forums/...p/thread/c5914a56-1f81-4b01-9446-0c041d6f66d6
...doesn't give a solution to your (actually, our ) problem but is quite informational...
Why can't we insert the owner's info in the newest roms (23025-23028)?
Remind that some software can´t be registered without that info...
I don't have one of these versions flashed right now, but check your registry under :
HKEY_CURRENT_USER\ControlPanel\Owner
ricardo1976 said:
Why can't we insert the owner's info in the newest roms (23025-23028)?
Remind that some software can´t be registered without that info...
Click to expand...
Click to collapse
One other thing you could do is start Notepad on you desktop computer and put the following in there (this works on 6.1, and "hopefully" might work on 6.5 but I can't verify it as never tried)
20#ctlpnl cplmain.cpl,2
Save the file, rename it to have a .lnk extension to the end of it (i.e. myfile.txt now becomes myfile.lnk). Copy this to your device (c:\windows\Start Menu\Programs) and try and open it off your Start menu. I would recommend if it's something you'll use often (as a workround) because the Owner Icon under Settings, Personal is gone (which is bizarre!) use Restart (credit to Showaco) to give it a better icon (search for Restart in forums).
You can do it the registry way but a couple of the fields might give you a problem as they're binary fields although it might be fine!
I did a search and found a thread on it here : http://forum.xda-developers.com/showthread.php?p=1646851#post1646851
Hey all,
I own an unlocked ATT Tilt 1 (Kaiser 8925). It is currently running windows mobile which is extremely slow. I have read all over the internet that you can put the Android 2.2 OS on this phone and have seen youtube videos on this topic also.
Ideally I need to be able to buy apps from the android marketplace.
Since I'm not a phone hacker I'd like to find a professional cel phone service company that can do this for me.
I searched extensively on Google and can't seem to find one. So who can do this and what is the normal charge for something like this.
Just trying make my old phone useful in wifi mode.
Any advice would be great.
Regards Henry
I don't think there is a company that provides such a service especially if we take in to account that kaiser/tilt is a 3 year old device and the android port is not official. There are plenty of topics in the forum describing how to replace winmo with Android. You don't have to be a hacker to run Android on your phone. Just read the stickies and you wil be able to flash ityourself in no time
There are phone dealers out there (in the USA anyway), that will do this for a fee on the Kaiser, but trust me, with what has gone into the development of this, almost anyone can do it. Save yourself the money and try it yourself. The worst I've heard about is a mis-flashed phone needing some master reset.
The question is who?
I live here in the Orlando area and have called a number of cel phone companies.
I was treated like King Gidorah Three Headed Space Monster. They didn't have a clue this could be done.
Henrykjr said:
I live here in the Orlando area and have called a number of cel phone companies.
I was treated like King Gidorah Three Headed Space Monster. They didn't have a clue this could be done.
Click to expand...
Click to collapse
Listen HenrykJR there are about dozens of android builds on this forum + many different versions of two kernels, not all of those will work correctly for you. You might experience different issues with one setup but the other will work correctly for you. So even if there was a company that could flash it for you, you might end up with an unstable device. Also how could a company gain knowledge on flashing android builds to a phone that was originally shipped with windows mobile??? You seem to be looking for Nessy....in woods.
Your best bet now is to find someone in the forums to help you flash your device....maybe even use skype to show you how to do it. It really isn't that hard.
Hehe, i don´t think you´ll find a Company that will do it for you. Maybe you find some guys that do it for Money (me to ). But if you spend a little time with reading through this forum you could do it yourself and save the money.
Preparing:
1.) You need a SD card (mandatory for android on Kaiser). And you need a Google Mail Account for syncing your contacts etc. and access the android market.
2.) You have to "unlock" your Phone (with HSPL/HardSPL). Only after that you are able to flash things (Cusom WinMo ROMs, Radio, Android) to your Kaiser. So read through this guide and follow step 1-4.
3.) Now you have an unlocked phone an you should be able to flash everything. And the first thing you flash should be the latest "radio". The "radio" for Kaiser is similar to the BIOS for your PC. Like the subsystem and responsible for GSM chipset etc... So look & read in this Radio-Thread, download the latest Radio (it is 1.71.09.01) an follow the guide "Flashing Radio from microSD"
4.) Now your Phone is up-to-date and ready for flashing Android (or WinMo custom roms). YOU NEVER HAVE TO DO THE STEPS 1-3 AGAIN! Your Phone is now completely prepared!
Flashing Android:
For Android on Kaiser you always need 2 Parts. The Kernel (this part initialize the hardware so its similar to "driver" on PC) and the Built (the Android OS itself). But Both should work together so you´ll may find in some kernel suggestions in Built-threads because not ever kernel work with every built. For your beginning i whould suggest you some things:
First the kernel:
DZO is the most popular (the father of android on Kaiser) Kernel-Developer for Kaiser. So go to his repository and download "voguimg-240x320-2.6.32-froyo-09-10-10_23.nbh". Because Vouge and kaiser have almost the same hardware we all could use this kernel. But everyone have to modify this kernel to make phone related optimizations. You can do thy by hand (not recommended for you) or with a tool called "Atools". This tool is writthen in "Python" so mac and linux user could use it too. But you need to install Python. But that is all described in the Atools thread. Read through it and follow the guide.
Modifing Kernel:
We will only modify the madatory things. Not more at the moment...
So run Atools, klick on the "folder" Button and load the "voguimg-240x320-2.6.32-froyo-09-10-10_23.nbh".
Device: "Kaiser" should be checked
Resolution: 240x320 should be checked (native resolution of Kaiser display). Everything else will give blurry optic.
Version: "Froyo" should be checked, because we will flash a Froyo built (thats android 2.2). If you want to flash an older built like a Donut one (1.6) you have to modify & flash your kernel again.
Panel Type: Try "auto" or "1" first. But if you have a fuzzy screen or artifacts you have to try out which paneltype fits best for your device. HTC has built in 3 different displays in the Kaiser and the only way to find out which one is builtin is trial & error.
Keymap: Depends on which hardware keyboard layout you have. Here in Germeny i have to use "qwertz".
We leave the other options as they are an klick on the "Disk" button to save our modificated kernel now. it save it as "KAISIMG.nbh".
Now we need the Built:
I suggest "Fat Free Froyo" at the moment. Fast, stable, an looks good. So go to this thread and download "ODEX DOWNLOAD RLS5 ALL LANG-ODEX" on the bottom of the post.
then unzip/unrar this file...
Flashing your first Android:
1.) You should have a fat32 formatted SD card
2.) put the Kernel (the modified KAISIMG.nbh) to the root of SD card
3.) Create a folder named "andboot" on SD card
4.) Put the unzipped file (androidinstall.tar or .tgz) in the folder "andboot"
5.) Remove SIMcard and any cables from phone and put the SD card in your phone. Battery should be 50% carged or more...
6.) go to bootloader-mode (press and hold camera button and powerbutton). the KAISIMG should be loaded and it will show you "press powerbutton to update" or something similar. Do that... Now a progressbar will appear. When it is at 100% wait a few seconds an then pull the battery. Wait 10 seconds an insert it again. Voila! You flashed your first android kernel!
7.) Now we have to install android itself. So Power on the phone. In the moment when you see small white text on black background you have to press and hold the d-pad button. This one in the middle. Now you get in the install menu.
8.) Leave the options "System on nand" and "DATA on nand" as it is. Navigate to "install system" an press dpad. It ask "format system" and "format data". Both "YES". after this procedure you enter the menu again. navigate to "quit".
9.) Yeah! The first Bootup of Android! The first bootup takes longer as the following ones because now the system prepares for bootup and do a lot of optimisations. Even if you enter the lockscreen you should give it 10 minutes time to finish this optimization process in backround.
10.) Finish! You have flashed your first android completely! Now you can play around and make your settings. Remember: You have to sign in to your google account befor you can access the market or syncronize your contacts etc.!
Sounds more complicated as it is. Try it!
And if you´ll dig in deeper in this stuff you have to read here! Especially the Stickies/Refs/Tutorials! We´ve all done that!
have fun!
Henrykjr said:
Hey all,
I own an unlocked ATT Tilt 1 (Kaiser 8925). It is currently running windows mobile which is extremely slow. I have read all over the internet that you can put the Android 2.2 OS on this phone and have seen youtube videos on this topic also.
Ideally I need to be able to buy apps from the android marketplace.
Since I'm not a phone hacker I'd like to find a professional cel phone service company that can do this for me.
I searched extensively on Google and can't seem to find one. So who can do this and what is the normal charge for something like this.
Just trying make my old phone useful in wifi mode.
Any advice would be great.
Regards Henry
Click to expand...
Click to collapse
Brother, You can do it yourself, I can assure you. Regarding any ambiguity, you can contact me through PM. (I can guide you complete on voice over skype / msn). Its a TIDEOUS job but EASY to do since there is no MEANS OF BRICKING your kaiser (unless you flash something else than what u have do to install android).
I am here to help you in this community. And you can do this thing yourself.
Your device is At&t Tilt. The bad thing about installing android is getting a RIGHT kernel that suits your LCD type and enables wifi in the android build u install. (maybe in 1st try, maybe takes almost 10 tries like it happened for me)
Hi,
Finally got my galaxy tab to work after 6 hours. Now it is running well.
As it is 4 am here, i will post a guide for Singapore users once i wake up as i have meet with problems during the whole process.
Luckily, all information can be found on this forum but just that you will have to read through 20 plus pages from different topic in order to get the answer.
Super happy with my phone now!
*just another newbie* =)
Sent from my GT-P1000 using XDA App
Sorry to steal your thread. Singaporean tab user here as well. I think we should constantly update this thread for singapore users. I was running dxjm4 up til this morning when i decided to flash to roto-jme. spent the last few days reading the thread and considering whether to upgrade or not because of the lack of information for singapore users. so i decided to take the plunge and just go for the upgrade no risk no gain. my tab got stucked at the samsung logo after it auto rebooted but it was fine after i manually rebooted it
what i did was to upgrade from jm4 instead full flashing my tab. it turned out fine so far but there's one thing that puzzles me. the apps that roto mentioned were removed are still in my tab such as daily briefing etc.. do u have this problem as well?
Not Too Sure... I am new to Galaxy Tab or rather Android =P
But i suggest you do a full flash again.
i wasn't ready to even root my device initially as i only gotten my Tab on Saturday 7th Jan 2011.
One thing that actually forced me to root and flash the rom is the stock version whether bug or not i just couldn't sync with my company exchange 2010, which is critical for me.
Nonetheless, i haven't tried the jme v4 as yet (I suppose) as i did not know how to get it to work.
All i did was follow:
http://forum.xda-developers.com/showthread.php?t=895827
And all went well, except that Data doesn't work.
Thoughout the whole process i did not use the file name "Roto-JME-Full-v4"
which set me thinking whether did i actually do the right thing.
One thing is most of the stock app was gone, baseband was change to I9000UGJK3, Kernel Version 2.6.32.9 [email protected] #1 and Build number is Froyo.XXJME.
HCgoh said:
Not Too Sure... I am new to Galaxy Tab or rather Android =P
But i suggest you do a full flash again.
i wasn't ready to even root my device initially as i only gotten my Tab on Saturday 7th Jan 2011.
One thing that actually forced me to root and flash the rom is the stock version whether bug or not i just couldn't sync with my company exchange 2010, which is critical for me.
Nonetheless, i haven't tried the jme v4 as yet (I suppose) as i did not know how to get it to work.
All i did was follow:
http://forum.xda-developers.com/showthread.php?t=895827
And all went well, except that Data doesn't work.
Thoughout the whole process i did not use the file name "Roto-JME-Full-v4"
which set me thinking whether did i actually do the right thing.
One thing is most of the stock app was gone, baseband was change to I9000UGJK3, Kernel Version 2.6.32.9 [email protected] #1 and Build number is Froyo.XXJME.
Click to expand...
Click to collapse
i am new to android too and this is my first android device. your baseband is weird? I9000? which firmware did u flash???
Root devices *Important Points
And Yes i woke up...
Anyway i do not gain credit from the guide itself as everything can be found in this forum. If you want to thank people, please thank the people that writes the program and the trial & error people if you find my thread useful. I am just consolidating all the steps that i used to flash my Tab, important things to take note of and etc...
Step by step guide to Rooting:
Please read
http://forum.xda-developers.com/showthread.php?t=812367
*Important points to Note when Rooting"
Process:
1) Connect your galaxy tab with debugging mode disabled and sync with Kies even once - You must be damn sure Kies can connect to your phone
2) Disconnect it and enable debugging mode from Settings>Applications>Development>USB Debugging
3) Connect the tab again to PC and click on home button so that Tab comes out of Kies connection - I found that after USB Debugging is turn off, Kies can still find your phone but it will just appear as Connecting... on the top left hand side of Kies. (I left my Kies on throughout the process)
4) Launch SuperOneClick.exe
5) Click on root and wait for 5-10 Mins - it stated 5 - 10 min but it took like 5 - 10 sec for SuperOneClick to prompt me saying that device is rooted.
And that all for Rooting whole process took me about 5 min Including all the reading. (Simple Great Job by SuperOneClick!)
Now comes the slightly complicated part: Flashing New Roms
Below is the thread that is used
1) http://forum.xda-developers.com/showthread.php?t=894763
2) http://forum.xda-developers.com/showthread.php?t=895827
What i did was:
1) Download OdinV3 1.7 (Provided in the thread 895827)
2) Download Addon-JME-Modem.zip (http://files.deodexed.com/ModADroid-Galaxy-Tablet/Rotohammer/JME/)
3) Download P1_add_hidden.pit (http://files.deodexed.com/ModADroid-Galaxy-Tablet/Rotohammer/JME/)
4) Download Roto-JME-FmtIntSD.zip (http://files.deodexed.com/ModADroid-Galaxy-Tablet/Rotohammer/JME/archive/)
Additional:
I also downloaded (But till now i have not use any of the file below)
1) Roto-JME-FmtIntSD-v2.zip ( http://files.deodexed.com/ModADroid-Galaxy-Tablet/Rotohammer/JME/archive/)
2) Roto-JME-Upgrade-v4.zip ( http://files.deodexed.com/ModADroid-Galaxy-Tablet/Rotohammer/JME/)
Why is it not used, i myself is not too sure. For FmtIntSD alot of people is asking which is it to use as there are 2 different version 1 & 2 (i Suppose).
I have used the Version 1, as the time posted in the FTP link seem to be later than Version 2.
Also as thread http://forum.xda-developers.com/showthread.php?t=895827 shows in the screenshot, under tab CSC: Addon-JME-Hidden.Tar, this file is missing plus confirmation from the thread saying that it will fine without it.
Once downloaded, it is time to get to business =)
Steps i took:
1) Startup Odin
2) Connect Galaxy Tab to Kies make sure Kies is able to connect to the device and is able to Sync with device (Toggle with the USB Debugging option Either On or OFF) *My kies is never turn off from the start Rooting to Flashing* i think in order for Odin to work properly, Kies must be able to detect the device is been plugged in. (Just my Thought)
3) At this point of time Odin will also detect the device been plugged in as show in the screenshot provided in thread 895827. The yellow box will appear stating COM10 or 11 or 12 (DOesn't matter what com Number)..... Left hand bottom of ordin will also show Added!
Checked Make sure and double checked.... Yeah the next part!!!
4) Unplugged my phone from the USB
5) Off my phone
5) On my phone to get to the downloading mode (Hold Power Button and Volume Down Button)
6) Checked my Odin, Bottom left log shows REMOVED!
Hell Ya exactly the same as the sceenshot.....
7) Plugged in my phone with the Downloading screen....
8) Waited.... Waited..... 5 min pass..... Windows 7 is still searching for "Gadget Serial Port" Odin didn't detect the device connected.... don't have to worry Windows 7 will eventually find the driver, just got to give it sometime (Just in case you meet with the same problem like i did, Windows 7 took almost 10 min for the device to be ready)
9) Check Odin, Bottom left hand log.... ADDED!
Almost there.....
10) Plant in all the .Tar file as show in screenshot (Thread 895827)
*Please make sure you unzip the .rar file the logo is similar to winrar icon once you unzip. Can get a little messy, what i did was unzip and delete the original zip file that i downloaded. Remember JME-Hidden.Tar is not needed, just leave it blank*
11) Tick the "Re-partition" in Odin
Now you are all ready to start, double check all the setting and click the "Start" in Odin... =)
12) Pray.... Pray... Pray....
Whole process took me about 5 min, Odin will show you the details as it is flashing, Installing and Bla Bla Bla.... Once it is ready, Odin will prompt you either Successful or Failed...
Phone will automatically restart. Just leave it till you see the main screen comes out.
* I Succeed on my first try, so if you fail i guess you got more reading to do than me, but i am sorry that i am unable to help if you fail at this point*
Now then all good, checked my phone all seem well... did a call to my house number, Working....
Now the complication that i faced: My 3G (data Services) is NOT RUNNING!!!!
Did a search on the forum and found a few threads that is helpful:
1) http://forum.xda-developers.com/showthread.php?t=901021
2) http://forum.xda-developers.com/showthread.php?t=845263&highlight=modem.bin&page=3
3) http://forum.xda-developers.com/showthread.php?t=847273&highlight=modem_bell_i9000
* I Have attached the modem.bin that i use to get my 3G working, but before you download the attachment please do a few check as stated below.Things to check if your 3G (Data Service) is not working:
1) APNs setting
Setting>Wireless and Network>Mobile Networks>Access Point Names
2) Select the Access Point Names and see if there is any setting inside.
3) If it shows "No Setting"
4) Tab on the bottom left hand corner of your galaxy tab, "MENU" button beside the "Home" buttom
5) select "Add APN"
6) Use the information below, key in whatever is there. Those that you don't know just leave it blank. (As long as your are in Singapore i believe you know which telco you are with)
StarHub (Singapore)
APN: shwap or shwapint
Leave user/pass blank.
M1 (Singapore)
APN: sunsurf
user: 65 pass:
user123
swirlyMMS :
MMSC and Proxy server settings MMSC : http://mmsgw:8002/
Proxy : 172.16.14.10:8080
MMS-specific APN Settings
APN: miworld
username:65
password:user123
SingTel (Singapore)
APN: internet
Username: 65IDEAS (or blank)
Password: IDEAS (or blank)
Once Key-in "MENU" button again and safe the setting, now go back to your APNs and check to see if you have selected the setting you key-in (Button on the right hand side will be "GREEN"
Now Wait & Pray that the logo "3G" or "H" appear on the top beside your signal strenght bar.
if no launch your dialer (Press Phone) and Dial *#2263# select "automatic" 1st option. (Select it once and exit by pressing "HOME" or "BACK")
Wait & Pray....
I believe this should get it going as under JME-Modem.zip, the modem should already be in.
__________________ I sincerely hope that you do not have to do the step below________________________________________________
If the 3G or H is still not showing after you tried the above step. Download the modem.bin (Attachment in this thread modem_bell_i9000.zip)
Then follow the step below:
1) Unzip the file
2) startup Odin
3) Browse for the Modem.bin, using Odin "Phone" Tab (File you unzip from the attachment downloaded from here)
4) off your phone and boot it up to the "DOWNLOADING SCREEN"
Checklist:
5) Re-partition is NOT tick
6) Odin detect your device
Hit "Start" and wait for your phone to reboot.
*I succeed with this flashing of modem, if you fail all i can say is good luck*
Once your phone is up, check on the APNs setting again (Key-in the details is there is nothing in the list) Check on *#2263# and set it as automatic.
Then End.....
Conclusion:
I use the exact same step for my phone, and get it going. I hope it helps you.
Again i would want to highlight that none of the above is by me, all information can be found in thread posted by other users. Please give thanks to them as they are the one doing the job, taking risk to try ROMs, Root and etc...
=) i hope my thread helps anyone with the same problem as me...
PS: DO NOT HOLD ME RESPONSIBLE IF THE ABOVE GUIDE DOESN"T WORK FOR YOU.
Hi Kay Kiat,
I Seriously don't know. See the steps i posted, i believe it is because i flash a i9000 modem in that is why my baseband is weird. =p
i believe all i need to do is to re-flash the Jme modem in, and it should be right.
But currently at work no time to try. haha
Best Regards
Hi guys, Singapore GT user here also. Looking forward to try out your guide.
EDIT: Just flashed Roto's JME-Full-v4 with repartition. All works fine. No modem flash required.
HCgoh said:
Hi Kay Kiat,
I Seriously don't know. See the steps i posted, i believe it is because i flash a i9000 modem in that is why my baseband is weird. =p
i believe all i need to do is to re-flash the Jme modem in, and it should be right.
But currently at work no time to try. haha
Best Regards
Click to expand...
Click to collapse
hmmm. my 3g/gprs seems okay.. i went from jj1->jm4 via kies then jm4->rotojme via flash.. my baseband is p1000dxjm2 (i believe this is from jm4 as i did not flash modem when i upgraded to rotojme). hmmm.. did u set your apn correctly?
Sg user here as well
Anyone managed to get chinese input up?
Sent from my GT-P1000 using XDA App
junchen said:
Sg user here as well
Anyone managed to get chinese input up?
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
are you talking about the keyboard?
Hi,
wanted to share my experience from flashing this Rom.
The way I've done it is download the latest full version find in the ftp site (not the archive) directory and using Odin to fladh my tab. I also downloaded all the other files but did not use them.
Overall, this rom is good. It solved my exchange problem but i've lost a few things as well. There's no more chinese input and i'm no longer able to zoom and pinch on dolphin browser. Does anubody has any solutions to these problems?
Thx.
Sent from my GT-P1000 using XDA App
中文鍵盤及手寫
This is what I've been using in a US T-mobile Tab with Roto-JME & it's working fine! Enjoy
junchen said:
Sg user here as well
Anyone managed to get chinese input up?
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
xenomage said:
i'm no longer able to zoom and pinch on dolphin browser.
Click to expand...
Click to collapse
This was solved in another thread, maybe the Roto-JME one itself. Theres a new version from Dolphin with the fix. You'll find it
xenomage said:
The way I've done it is download the latest full version find in the ftp site (not the archive) directory and using Odin to fladh my tab.
Click to expand...
Click to collapse
The Roto-JME-Full-v4 will format the internal sdcard only if it is corrupted. So you can shorten the steps to just flashing that one firmware. The ones in the archive are there just in case we needed to test something.
APN settings
Hi
Did you guys copy down the APN settings and did you manage to get your MMS working? I only have my 3G working. Was trying out the different settings to get MMS working too.
ps: for chinese input, can just install google pinyin. been using it since Im only android. swype does have chinese input but the one on the tab doesnt have it. I was testing the beta using my hero and i can do chinese input using the swype keyboard. i wonder if there is anyway to update the swype version to the latest one released by them.
Chinese input
xpgroup said:
This is what I've been using in a US T-mobile Tab with Roto-JME & it's working fine! Enjoy
Click to expand...
Click to collapse
Hi,
this may sound kinda dumb but after i download and install the attached APK, nothing happens on the keyboard.
How is it supposed to work?
Thanks.
go to settings > locale and text > enable whatever keyboard you want. then rmb to change your input method whenever u wanna use the new keyboard
xenomage said:
Hi,
this may sound kinda dumb but after i download and install the attached APK, nothing happens on the keyboard.
How is it supposed to work?
Thanks.
Click to expand...
Click to collapse
You'll need to goto Setting-Locale and text, check the Penpower Input Method. After that, at any input screen, press & hold - then select the input method.
xpgroup said:
This is what I've been using in a US T-mobile Tab with Roto-JME & it's working fine! Enjoy
Click to expand...
Click to collapse
Thanks for the file, it works fine. Just the right hand side part of the keyboard is emtpy. I wonder if there is anything to adjust the scale.
Thanks.
If anyone has an old UK device at the bottom of a drawer somewhere which they recollect has a non-English language dictionary from B&N on it, please contact me before trying this.
Spoiler: How I did it
While looking at the CWM Region Changer with someone from the UK trying to get their old NST up and running, it occurred to me that we might be able to do better. Several days and a few out-of-order epiphanies later, I had a rough idea of what needed to happen.
The most important discovery was that the "UK ROM" was still there in the US FW 1.2.2 update. That is to say, if you copied over the splash screens from the UK 1.2.1 update and the Oxford dictionary, you had nearly everything that was different between the two. Except it didn't work. It looked different on boot, but was still the US version (you can tell by looking at Settings which are different in the two versions).
Eventually I took at look at the update script in the B&N zip and saw that it was checking build.prop before doing anything else. I compared that file on the UK 1.2.1 and US 1.2.2 zips and found the major difference was in localization. In two entries "GB" was used instead of "US". Was it that simple?
Yes!
Ah...but it refused to register. In fact, it refused to authenticate, so it never got to asking about your account. The final discovery was the result of a completely idle-brained attempt (because I was out of ideas). I had rooted an instance after skipping OOBE. In the launcher app drawer I saw the familiar junk, including DeviceRegistrator (anyone who has rooted an NST knows this app with the smiley-face icon). I've always thought it was just cyber-detritus, an early version or mock-up left by B&N developers. They were not very tidy, after all. But maybe intents of the app are used in the current registration process. Who knows? Anyway, I tapped on the icon and proceeded to successfully authenticate the device. That got my attention! Then I tried to register with my existing B&N account and password. BINGO! I could see my device on the B&N website under my account and I was able to "buy" a free book using the Shop app (you need a credit card on file with B&N to get even a free book).
So it works for me, in the US.
Because of the changes I made to the original US 1.2.2 update zip, the internal signature is broken, so it cannot be used as an auto-update zip. Hence the need for CWM.
To avoid the necessity to root (for those who would rather not), I removed the broken Lancher.apk in /system/app and replaced it with a simple launcher in the Gingerbread style that is able to run as a system app. So when the device gets to displaying "home", it asks how you want to do that. Initially, the Launcher app is selected so that you have access to an app drawer and the DeviceRegistrator app. After registration, a reboot will present the "home" option choice again. This time the "always" box can be ticked and the B&N "Home" app selected. The Launcher.apk will never be heard from again. Those who go on to root can remove it from /system/app if they wish.
Outstanding issue to be explored: dictionaries. There seems to be a capability for adding different language dictionaries. The User Guide refers to this also. I have not been successful in doing this and don't know whether there ever were any other dictionaries. Since this was not a US option, I'm guessing that the only hard-coded URLs for the dictionary downloads are to non-existent UK servers. I still haven't tracked down where those URLs are. The Nook app for Android is reputed to have the same capability, but when I installed it on one of my rooted tablets, it only had an English dictionary. The format of this db file seemed to be exactly the same as the Oxford dictionary on the UK ROM. I got a Spanish book from B&N and tried to look up a word from there. This gives an option to download a dictionary (as the user guide says) but the result just sends you to the Settings where the only dictionary visible is the default English. So maybe you have to be in another country? Anyway, I could not get the NST to recognize the English dictionary offloaded from the Nook app, despite the apparent structure similarity with the Oxford already onboard. Perhaps there is a database somewhere that would keep track of the dictionaries on the device if the download function were still working. I have not found it. Or, perhaps additional "downloaded" dictionaries have a special place to be (Edit: YES! They go into /data/media/B&N Downloads/Dictionary). Someone with a long memory who has experience with the UK ROM but is not primarily an English speaker might hold the key.
Spoiler: Q&A
--Is this the same thing as the Region Changer?
No. The region changer procedure gives you a device running US firmware (although it looks like B&N still knows it's a UK device based on the serial number and their own records--or they might be identifying its point of origin by the internet connection). This update zip will give you a true UK ROM: the different splash screens, the different settings options (including language) and the ability to enter letters with diacritical marks from the keyboard. It also features the Oxford dictionary. However, it will contact US B&N servers, not the non-existent UK ones.
--Do I need to have an existing B&N account?
I think so. The back door we are using to authenticate and register the device does not have an option for creating a new account.
--Should I deregister my device before doing this?
If you did a region change and are currently running registered US FW 1.2.2, I would recommend deregistering the device before converting to the UK ROM, just to avoid potential conflicts. You can use the same account to register the new ROM. If you have B&N content, it might even show up since it's the same account (mine did).
--Can I purchase books from B&N using the Shop app?
Maybe. I was able to "buy" a free book from B&N and have it appear on my device (note: to purchase even a free book you need to have a credit card on file for your B&N account). But, I am in the US. The B&N Terms of Service says that you have to use (or have on file) a credit card with a US address. There appear to be workarounds like purchasing a US-based cash card, etc. Seems like a lot of extra effort, but apparently some people have done it.
--I live in the US but this sounds interesting. Can I try it too?
Well, I did! The ROM is interesting in a number of ways. It really is a Western European variant, not just UK. German, English, French, Italian and Spanish are the available languages. If your primary language is not English but instead one of these, this might be an attraction. However, there is at least one unexpected consequence. Some external servers will be absolutely convinced you are outside the US. I found this out by trial-and-error when I could not get my Today's Comics app to work. When I changed the region to English (US), it began to work, so I guess the content was region-blocked. I jiggered the Settings app of the UK ROM slightly so it would display the English(US) option.
--I see "Chinese" among the languages! Can my NST display Chinese?
Well, no. Unfortunately the only way to get English(US) to display is to display all of the "development" languages. I tried to suppress "Chinese" but had no luck. There are Chinese characters in DroidSansFallback but the strings for the B&N system were never fully translated (maybe not at all). There is a lot that is translated (appears to be Taiwanese Chinese), probably left from the original phone ROM they used to make the NST OS. However, if you select Chinese any apps you may have installed that are correctly localized for Chinese will display appropriately.
How to do it
Note: I did this on a deregistered device. It does not matter whether your device is currently US FW 1.2.2 or a UK FW 1.2.1.
1. Prepare a CWM card (if you don't already have one, use one of the two sdcard versions). If you've never done this sort of thing before it's probably easiest to download the zip for the Nook Region Changer and follow the instructions there for making the sdcard (steps 1-3). You don't need the two update zips that are on the card, but it's still CWM. If you already have a Region Changer card, you can use it as-is.
2. Download a copy of my 1.2.2 UK update zip. Copy the update zip to the CWM card (the card should be in the card-reader slot of your PC, not in the Nook)
3. Power down your Nook.
4. Insert the CWM card into your Nook and power up. You'll see the logo and maybe the opening menu.
CWM is a little wobbly on the NST. Sometimes it seems to get stuck on a white screen after the logo. If that happens to you, press the lower right hardware button. That generally wakes it up.
Navigating in CWM involves using the upper left hardware button (go back to the previous menu), the two right hardware buttons (go up and down a menu) and the "n" button (do what is highlighted).
5. Move down to "backup and restore". Press "n".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6. The menu should show "backup" at the top. Press "n". This will backup your current configuration onto the sdcard.
7. At the conclusion of the backup you should be returned to the top of the menu.
8. Move down (or one step "up") to "advanced". Press "n".
9. Move down one step to "wipe dalvik cache". Press "n".
Then move way down (or a little up) to "yes". Press "n".
Here you may run into another CWM issue. At least for me, CWM has a tendency to freeze after any kind of wipe. If that happens to you, don't panic. If the buttons don't seem to be responsive, press and hold the power button. If the device does not reboot back into CWM, release the power button and press and hold again. Eventually the device will reboot, taking you to the top of the menu again.
10. From the top of the menu move down to "wipe data/factory reset". This option is just like the previous one, including the potential freeze. Do it.
11. From the top of the menu, move down to "install zip from sdcard". Press "n".
12. The top of the next menu says "choose zip from sdcard". Press "n".
13. Move to select the nook_1_2_2_UK_update_CWM.zip and press "n", etc.
14. After the update is complete you need to return to the top of the menu where it says "reboot now" (if you are not already there). At that point, remove the CWM card from the device and press "n" to reboot.
15. Your Nook will boot into the UK ROM setup. You'll see the familiar multi-lingual splash screen, the marching dots, and finally come to a Language choice screen.
Select whichever language you prefer. You can change this later from Settings.
16. The next screen is the "Welcome" screen.
You are now going to execute a "skip OOBE". Since registration fails in the usual setup wizard, we will have to go in the back door, so to speak. At the "Welcome" screen, press and hold the upper right hardware button and swipe your finger across the top of the screen from left to right. You should see a "Factory" button appear in the upper left corner of the screen. Tap it.
17. Now you are on the Factory screen.
Again, press and hold the upper right hardware button and tap the screen in the lower right corner. You should see a "Skip OOBE" button appear on the screen. Tap it.
18. OK, so now you are faced with a choice which I have added to the ROM in order to finesse the registration issue without needing to root the device. There should be two options listed on the screen: Home (the B&N home screen) and Launcher (I added this). For now tap on "Home". The B&N home screen loads up with the infinite spinner in the lower half (no registration, no wi-fi, no data).
19. Press the "n" button and select "Settings". Set up a wi-fi connection and set the time zone and time display format. Leave wi-fi on. Use the power button to shut the device off.
20. Power up your Nook. When it has passed the marching dots it will ask you again whether you want "Home" or "Launcher". This time, choose "Launcher".
A simple Android launcher screen is displayed. All you care about is the app drawer, that little square of tiny squares in the center of the bottom of the screen. Tap it.
21. There is a bunch of stuff (mostly junk) in the app drawer. Resist the impulse to fool around there. Keep your eyes on the prize! Locate the DeviceRegistrator app (stupid smiley-face icon). Tap it. Check to be sure your wi-fi is on.
22. You need to do two things here.
First, register (authenticate) the device itself. That's the first button on the left in the first row. Tap that. If all is going well (and your wi-fi is on) you should get a confirmation alert. After that, type in your username (email) and password for your B&N account. There is no option here to create an account, so you need to have one already established for this to work. After you've typed in the information, tap on "Register User". You should get a confirmation alert. You can now turn off wi-fi. Press the "n" button and select "Settings". Check Device Info>About your NOOK. If everything went according to plan you should see that it is registered.
23. Shut down the Nook. Power up one more time. After the marching dots you are again faced with the choice of "Home" or "Launcher". Before you make your selection, tap on the little (empty) checkbox. This will make your next move permanent. Now tap on "Home".
You'll never hear from "Launcher" again. It will just languish in /system/app with all the other unused apps and your Nook is now registered and good to go!
If you want to root and further customize your Nook, select one of the updated NookManager packages. I strongly recommend using NookManager to make a backup of your device before rooting. The CWM backup you made at the beginning of this process is not a complete nandroid backup and you'd be better off with one before you make any more changes. If you are not interested in rooting, you may want to make another backup with the CWM card at this point and then put it away somewhere safe. Just in case.
I've just followed these instructions on my 1.2.0 UK Nook Simple Touch. In the UK, and it works perfectly. Thanks very much!
ashh87 said:
I've just followed these instructions on my 1.2.0 UK Nook Simple Touch. In the UK, and it works perfectly. Thanks very much!
Click to expand...
Click to collapse
Thanks a lot for the feedback. Now we know it was not just a one-time fluke for me. I'm glad it worked for you as well.
Also worked for me. After registering I used NookManager to root it, then installed the latuk kernel from this post with CWM and it's now UK 1.2.2 and external keyboard supporting. That's all I was looking for. Another thumbs up for the repeatability of your method. Thanks for the detailed instructions.
A quick question - in step 23 ("never hear from Launcher again") above, if I accidentally make the wrong one the default, how would I get the launcher selection screen back again on startup?
markeq said:
A quick question - in step 23 ("never hear from Launcher again") above, if I accidentally make the wrong one the default, how would I get the launcher selection screen back again on startup?
Click to expand...
Click to collapse
Let's say--hypothetically, of course--that you did that. There are two ways around it.
1. If you rooted with the "traditional" or "stealth" versions of NookManager, you have ES File Explorer. You can use it to access the App Manager and remove the defaults from the "Launcher" (or "Home", or whatever). After doing this, a reboot will present you with the choices again. Screenshots for a likely sequence below.
2. A more general quick-and-dirty method that will work in any situation: install yet another launcher app. When you reboot, the activity picker will see a new option and give you your choices again. When you've got it right, just uninstall the additional launcher (which you never have to run for this method to work). Here's a link to another simple and relatively useless launcher that will fit the bill.
nmyshkin said:
Move to select the nook_1_2_2_UK_update_CWM.zip and press "n", etc.
Click to expand...
Click to collapse
@nmyshkin have you ever seen an issue where CWM freezes on this step under opening update package... ?
i have left it on this step for 2-3 hours - im guessing it doesnt normally take this long ?
i also had the same problem in the exactt same place when i tried running the nook_1_2_update_US_CWM.zip region changer
any ideas on what i could try different to get working ? otherwise im stuck on a de-registered 1.2.1uk so my only option might be to nuke all b&n and go custom ereader route (which is probably fine tbh)
A couple of minutes is all it should take.
Check out the update using a desktop zip utility.
Does it look normal?
Renate said:
A couple of minutes is all it should take.
Check out the update using a desktop zip utility.
Does it look normal?
Click to expand...
Click to collapse
yeah it looks normal on my computer (im running popos although i cant see how that would change anything)
Well, you can always do it semi-manually, at least you'll get feedback.
Extract META-INF\com\google\android\update-binary
Go to TWRP and use ADB to push both the (original) zip and the (extracted) update-binary somewhere useful.
Use ADB (you do have a rooted prompt?)
Code:
# chmod 755 update-binary
# ./update-binary 2 1 whatever.zip
You'll get text out of this and maybe figure out what the problem is.
cyberboy666 said:
@nmyshkin have you ever seen an issue where CWM freezes on this step under opening update package... ?
i have left it on this step for 2-3 hours - im guessing it doesnt normally take this long ?
i also had the same problem in the exactt same place when i tried running the nook_1_2_update_US_CWM.zip region changer
Click to expand...
Click to collapse
Hmm...
Well, two things come to mind. First, the zip package is NOT an update. You're just supposed to choose "install zip from sdcard". So if you chose an update zip instead, that could be a problem, although I would expect CWM to say it couldn't find an update zip rather than just hang. At least that's what it has done with me before when I've made the wrong choice.
Second, since you have the same problem with the "region changer" zip, is it possible that your CWM card is bad? You might want to go straight to the source: https://forum.xda-developers.com/t/...od-based-recovery-fixed-backup-issue.1360994/. Either sdcard version should work fine, depending on the size of your card.
FWIW, these are the MD5 values for the various files in question, just in case you've got a file corruption problem somewhere:
2 gb CWM zip: 61a9cfea527a81e17c9b5bc751af27ce
128 gb CWM zip: 670bccc38737a722eaed75871bb36d35
Unofficial UK 1.2.2 FWzip: fbaaac9957483850cb723d46a518c064
Region changer zip: bca752409c8cc6da43658c7d537dfdf1
nmyshkin said:
Hmm...
Well, two things come to mind. First, the zip package is NOT an update. You're just supposed to choose "install zip from sdcard". So if you chose an update zip instead, that could be a problem, although I would expect CWM to say it couldn't find an update zip rather than just hang. At least that's what it has done with me before when I've made the wrong choice.
Second, since you have the same problem with the "region changer" zip, is it possible that your CWM card is bad? You might want to go straight to the source: https://forum.xda-developers.com/t/...od-based-recovery-fixed-backup-issue.1360994/. Either sdcard version should work fine, depending on the size of your card.
FWIW, these are the MD5 values for the various files in question, jus tin case you've got a file corruption problem somewhere:
2 gb CWM zip: 61a9cfea527a81e17c9b5bc751af27ce
128 gb CWM zip: 670bccc38737a722eaed75871bb36d35
Unofficial UK 1.2.2 FWzip: fbaaac9957483850cb723d46a518c064
Region changer zip: bca752409c8cc6da43658c7d537dfdf1
Click to expand...
Click to collapse
omg thanks ! yes i think issue was with CWM card - i flashed a new one from the link you gave and now it is working
and also thanks for the advice @Renate - i want to get set up/learn to send ADB anyway so this is helpful
Hmm, well, I didn't know that.
OTOH, you would have seen that you couldn't find an update-binary in that zip.
nmyshkin said:
While looking at the CWM Region Changer with someone from the UK trying to get their old NST up and running, it occurred to me that we might be able to do better. Several days and a few out-of-order epiphanies later, I had a rough idea of what needed to happen.
Click to expand...
Click to collapse
Another success, from UK 1.2.1 to your pseudo-UK 1.2.2.
It halted, as in your examples, after both wipes.
Great step-by-step instructions. Spot on. I wouldn't say I'm a complete novice at such things, but it's always great to have such detailed instructions to make sure I don't go and do something daft.
Thanks so much! Do you have any kind of buy-me-a-coffee link?
(Now to work out what my battery issues were, if they come back, 'cos I know from disassembling the hardware and testing the battery that it's not the battery!)
jewelie said:
Another success, from UK 1.2.1 to your pseudo-UK 1.2.2.
It halted, as in your examples, after both wipes.
Great step-by-step instructions. Spot on. I wouldn't say I'm a complete novice at such things, but it's always great to have such detailed instructions to make sure I don't go and do something daft.
Thanks so much! Do you have any kind of buy-me-a-coffee link?
(Now to work out what my battery issues were, if they come back, 'cos I know from disassembling the hardware and testing the battery that it's not the battery!)
Click to expand...
Click to collapse
I'm glad it worked for you. That's my reward
Unless your glowlight is not turning off completely, I can't think of any other factor on a stock system that would drain the battery fast, barring some unknown hardware issue.
Hopefully this sorts it out.
On top of the running an unregistered device, I've read that manually tapping the power button to force it to sleep can cause battery issues, which is what I had been doing. Other possibilities that have been suggested to me are corrupt books, and maybe having the WiFi off.
I did notice that the internal disk was seen by windows and Linux as having an fs error, and windows couldn't fix it. That actually persisted following the instructions you gave above, it seems it didn't actually wipe the 240Mb internal disk so some files and settings and of course the corruption remained, which was a surprise, so I an erase and deregister to go properly from scratch. That did clean in!
Device is now on sleep with wifi off and no books after the fresh start. I also hacked the cover I was using to make sure it wasn't touching the screens or buttons. It's at 79% now, let's see what the percentage goes to over the next few days...
EDIT: BTW The reason I know it's not the battery itself is because I disassembled it and tested the battery through a few 0.5A charge & discharge cycles and gave it a week to see if there was any significant self discharge - madly, it still has almost the full 1500mAh capacity - impressive for a device that's been going for 10yrs now!
jewelie said:
I've read that manually tapping the power button to force it to sleep can cause battery issues, which is what I had been doing.
Click to expand...
Click to collapse
I think this has been debunked in the distant past although I can't put my finger on the particular post.
jewelie said:
I did notice that the internal disk was seen by windows and Linux as having an fs error, and windows couldn't fix it. That actually persisted following the instructions you gave above, it seems it didn't actually wipe the 240Mb internal disk so some files and settings and of course the corruption remained, which was a surprise, so I an erase and deregister to go properly from scratch. That did clean in!
Click to expand...
Click to collapse
That part is interesting and the initial result is not surprising. Unfortunately CWM cannot do a thorough wipe unlike, say, TWRP. A factory re-image is the most thorough cleaning I'm aware of, followed by the deregister/erase, then with CWM bringing up the rear. The reason I didn't include a factory re-image at the beginning of the process is that I wanted to keep it simple and not scare away those averse to anything approaching root. The 8-failed-boot-attempts method for a factory re-image is tremendously tedious and involves close timing and dexterity. OTOH, a NookManager card can initiate the process with the push of one hardware button. But that means making yet another card and flirting with the whole root thing (not necessary to root just to do the factory re-image).
The internal disk error may or may not have something to do with the battery drain. You'll find out. When I was doing a lot of testing with battery life a long time ago I found that a loss of 1% was typical overnight if the device was just sleeping. Of course, that's with whatever I had going on my system at the time.
@nmyshkin Thank you so much for the detailed guide.
I followed all the steps without any issue. I even got the freezing bug after clearing the Dalvik cache. But followed your steps, pressed on the power button twice and it restarted.
I used a 2Gb memory card and used the sd_2gb_clockwork-rc2.zip and I've written the image with WinImage 8.50.
nmyshkin said:
The internal disk error may or may not have something to do with the battery drain. You'll find out. When I was doing a lot of testing with battery life a long time ago I found that a loss of 1% was typical overnight if the device was just sleeping. Of course, that's with whatever I had going on my system at the time.
Click to expand...
Click to collapse
I'm seeing about 3% drop (as seen in settings -> about) every two days, which sounds about in the right ball park?
jewelie said:
I'm seeing about 3% drop (as seen in settings -> about) every two days, which sounds about in the right ball park?
Click to expand...
Click to collapse
I'd say so, especially if you've been doing any reading at all.
nmyshkin said:
I'd say so, especially if you've been doing any reading at all.
Click to expand...
Click to collapse
Update: It's over a month later, battery is still on 26%. Touch wood, it's fixed. THANK YOU!