Related
So i started building this rom for my AT&T Tilt a few days ago and i have run into a few issues i was wondering if anyone else has encounterd them and knows a fix. Ive been doing alot of searching and googleing and haven't found alot of answers.
1st i started out using alex's 3.03 winmo 6.1 htc rom. I had issues with the camera not working with radio 1.65 so i flashed to radio 1.64. But i was still having a problem with the device not doing a soft reset unless i physically push the button. So i searched around and my findings lead me to believe there is no fix for this so i need to use version 3.02. Then i went and got version 3.02 and when i rebuilt the rom everything seemed fine but there is no links to the hardware buttons in the settings applet for buttons. Is this a common issue i cant find anything about this anywhere??!
2nd when building packages sometimes they dont work... Ive built a few packages and they all turn out fine Ive run into some problems with the shortcuts but editing the initflash by hand fixes it everytime. Some packages ive made though just dont work, they install fine but when i run the app i get a component missing error, the weird thing is the cabs i used to intall these packages have no issues what so ever, an example would be frNotepad 1.2 if anyone has ever tried to turn that into a package.
Last question i have is how do you set up a defualt theme I noticed the htc theme package in alexs oem packs sets its self up as the defualt theme i looked through it did a search on cusTSK didnt find much info. So i tried to rename my theme to htc.tsk and just replace the theme file in the htc theme package but that just screwed the whole theme up.
1st i started out using alex's 3.03 winmo 6.1 htc rom. I had issues with the camera not working with radio 1.65 so i flashed to radio 1.64. But i was still having a problem with the device not doing a soft reset unless i physically push the button. So i searched around and my findings lead me to believe there is no fix for this so i need to use version 3.02. Then i went and got version 3.02 and when i rebuilt the rom everything seemed fine but there is no links to the hardware buttons in the settings applet for buttons. Is this a common issue i cant find anything about this anywhere??!
Click to expand...
Click to collapse
Look for the file 47d2a96e-f0dd-40e1-8f5b-a8cdc083a165.rgu and in it is the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Keys. This contains which application the hardware button will launch when pressed.
For the reset issue, 3.03 ROM have some problems. Upgrade to a more newer ROM. I created my own LITE ROM Folder similar to Alex. You can check my post at http://forum.xda-developers.com/showthread.php?t=399733. It is based on 3.28 official ROM.
2nd when building packages sometimes they dont work... Ive built a few packages and they all turn out fine Ive run into some problems with the shortcuts but editing the initflash by hand fixes it everytime. Some packages ive made though just dont work, they install fine but when i run the app i get a component missing error, the weird thing is the cabs i used to intall these packages have no issues what so ever, an example would be frNotepad 1.2 if anyone has ever tried to turn that into a package.
Click to expand...
Click to collapse
When building packages, double check the initflashfiles.txt to make sure the shortcuts are correct. For the component missing error, CAB and ROM Packages is not entire identical. In CAB, you can create the shortcuts without the need for the included LNK in the packages and initflashfiles.txt, but for ROM Packages, you need both files. So basically if the CAB works, it doesn't mean the ROM Package will also work.
For some reason I can't get my Polaris to run the latest Android version (i.e. Froyo).
1. Downloaded latest kernel (polaimg-panel3-320-froyo-07-07-10.nbh)
2. Downloaded last build (Incubus26Jc's Super FroYo RLS10)
3. Put last build (.tar or .tgz file) on SD card in directory /andboot
4. Flashed by using NBH file together with RUU Update Utility
Now it gets tricky:
a) or the system reboots, vibrates twice, I see a red and blue line and then a black screen and nothing;
b) or the system reboots, I get the Android installation menu after pressing middle button, install, but after soft reset I get a "No such file found" kind of system error
Can someone help me getting Android on my old Polaris? Thanks!
SnoopThaDoctor said:
For some reason I can't get my Polaris to run the latest Android version (i.e. Froyo).
1. Downloaded latest kernel (polaimg-panel3-320-froyo-07-07-10.nbh)
2. Downloaded last build (Incubus26Jc's Super FroYo RLS10)
3. Put last build (.tar or .tgz file) on SD card in directory /andboot
4. Flashed by using NBH file together with RUU Update Utility
Now it gets tricky:
a) or the system reboots, vibrates twice, I see a red and blue line and then a black screen and nothing;
b) or the system reboots, I get the Android installation menu after pressing middle button, install, but after soft reset I get a "No such file found" kind of system error
Can someone help me getting Android on my old Polaris? Thanks!
Click to expand...
Click to collapse
Same for me with polaimg-panel3-320, but it works great with polaimg-panel1-320-24-05-10.nbh
Thanks! Got it working with the older NBH file. Not completely flawless, but it works!
Don't use the old polaris panel 1 nbh, instead download the latest and then use this utility to change it to panel 1.
http://forum.xda-developers.com/showthread.php?t=689812
Thanks!!! Got it working with the latest NBH files! Great!!!
Hey, Could anybody unswer me on two questions.
1. why we have to change from panel3 to panel1 in this nbh file?
2. what is that mean panel3 or 1? why DZO do this type of the nbh (with panel3 i mean)?
thanks a lot, ithin it will helps not only me but everyone in future who didn't know about this modification
skydemon said:
Hey, Could anybody unswer me on two questions.
1. why we have to change from panel3 to panel1 in this nbh file?
2. what is that mean panel3 or 1? why DZO do this type of the nbh (with panel3 i mean)?
thanks a lot, ithin it will helps not only me but everyone in future who didn't know about this modification
Click to expand...
Click to collapse
The panel type depends on revision of your polaris, more specifically the make of the lcd panel, see here. I just tried every panel until I found one that works, I use panel 1.
Thanks a lot, but could you please answer me again. How i will know what kind of LCD panel in my Polaris and which number i should use?
these parameters is placed in my start-up file for the haret launcher
#alloctest 0x2000
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
set cmdline "board-htcpolaris.panel_type=1 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51 hw3d.version=1"
boot
can i use panel type from here?
i have opened this polaimg-panel3-320-froyo-07-07-10.nbh file in NBH editor and saw that the HW3D is set in Eclair. Should i change this to Froyo or left as is?
Thanks a lot for the conception)))
pannel type 1...
Did I brick my Polaris?
Well, it makes me laugh looking at the last post dated back July 2010 but I decide to post anyway because I feel somebody might have passed through my problems and might help.
Following indications on this forum:
1. I downloaded:
- Kernel: polaimg-panel3-240x320-2.6.32-froyo-09-09-10_21.nbh
- Last build: Incubus26Jc's Super FroYo RLS16 All Languages
2. Put last build (androidinstall.tgz) on SD card in directory /andboot
3. Used RUU Update Utility to flash the nbh file
Everything when smoothly. When it reboots, it vibrates, "Smart Mobility" message shows up, vibrates twice and then a blank screen is displayed.
Going through this forum I think I might have used the wrong type of panel and should have used Panel 1 instead of 3. So I downloaded Windows NBH Editor and managed to change the nbh into Panel 1. Then I shall try again.
This time my Windows 7 is unable to recognize my Polaris and all it can see is a new Disk Drive with no ADB device displayed. So I installed PdaNet302.exe to implement the USB driver for HTC Android Phone but it still cannot see my device and the process aborted.
What worries me is that one step of the process requested to change a setting on the Polaris (On your phone, click Settings > Applications > Development and make sure USB Debugging is on.). Obviously I can't do that as the screen is completely white!
I believe if I can manage to have my PC talking with my device then the problem will be fixed with the panel1-based flash. But every attempt to install the USB driver for Android Phone regularly fails on my PC.
All that time the Polaris remains with the lighted blank screen and there is no way to turn it off as the on/off switch refuses to work.
Shall I buy a new phone? Thanks for your help.
Did you try flashing the phone with a regular oficial HTC rom? just try it. Put the phone in the boot mode (press camera button and another one, dont recall which one) It will change to the tri color screen. Then connect it and try it.
Also there is a modified nbh rom which includes nothing, just the tool to recover your rom. Do a search to the forum.
I recently tried to install on my Polaris and it went really wrong. And finally could recover. The file is called ROMUpdateUtility_task29. I will erase everything on the phone but later you will be able to recover it
Form that point no more experiments. Polaris was made to work with Windows Mobile. It's really unstable, video camera is useless. And so on.
PC Carvalhon rom and I can use my phone as I want.
regards.
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
With this you can recover your phone: http://forum.xda-developers.com/showpost.php?p=6227425&postcount=7160
A second life for my Polaris
Kafkacell,
1. Following your suggestions, I successfully started the bootloader (camera touch while reset), the 3-colour screen appeared, Windows 7 recognised the device. I then flashed the offcicial RUU_Polaris_HKCSL_WWE_3.19.831.3_radio_sign_25.85.30.07_1.59.42.15_Ship and everything successfully completed. With enormous pleasure I see again my Polaris back to activity. Thanks for giving my Polaris a second life.
2. Back to Feb 2009, I flashed a pcarvalho eXtreme ROM. I don't recall any longer the version of this ROM but it was very stable and never ever crashed. Recently I downloaded and flashed most recent ROMs. From that moment on, I have no peace. It crashed 2, 3 times a week. Now I wish I could go back to the old version but couldn't find it. Perhaps pcarvalho removed them to save space? May I ask you which pcarvalho eXtreme ROM version do you currently run. Thanks.
Im currently running 29022 version (latest update from PCCarvalho).
Notes:
UPDATE:
29022 is up
this is a fix release...sound issues should be gone...had to remove htc volume control is it still has issues...fixes minor gfx glitches...updated to lastest and probably final leak version of wm6.5.3 (29022)...will from now on work on unresolved issues and finalize rom...this will still take some time due to work...
updated physics engine and utask app by ultrashot...my thanks to him...
patched htc album to novsync, faster scrolling once cache is made...
removed no longer supported apps (my phone and marketplace)...if u need them install via cab...
Here is the link for the rom: http://forum.xda-developers.com/showpost.php?p=15707730&postcount=8079
it was posted on July of this year, and so far it runs great. The trick is to not install a lot of apps in your main memory. Do it on your SD card. Also a hard reset is a must to avoid all kind of problems.
regards and glad you have your phone back to life
Well, it does seem we didn't have to wait that long.
I have just tested the 8500 froyo pre-release on the 8300 and everything works except for the gyro. This means that the screen is always displayed in portrait.
I know, thats not good on a phone designed to display in landscape. But hopefully someone will port the gyro drivers from the 2.6.29 kernel and we'll have a real improvement on our hands! Or someone will find a solution that forces landscape, which is almost as good.
You'll find the instructions on installing froyo here:
http://forum.xda-developers.com/showthread.php?t=942971
And rooting here:
http://forum.xda-developers.com/showthread.php?t=966624
This is surely a treat!
And if someone has any working solution for the "landscape" problems please let me know on this thread. I'll keep looking for a solution.
/Peter
Edit:
Oh, yeah, forgot one thing. The initial splash screen looks terrible (green background with a blue and red square), so if someone has any idea on how to change that for a nice xda logo or something. I would be most greatful!
Doesn't seem like gps is working either...
/Edit
Well, i can't do any programming. But some things i can acutally improve.
It seems that the keyboard layout that came with the 8500 doesn't match the layout on the 8300.
So here's an updated keyboard layout. Just replace the file named:
qwerty.kcm.bin
located in:
/system/usr/keychars/
With the one attached to this post. Root explorer will (apparently) do that for you. I haven't tried doing it with root exporer (did it with adb). But i have tested the keyboard layout and it works just fine.
Hope that helps anyone!
Please let me know if you have any problems installing replacing the file!
/Peter
Oh yeah, almost forgot, adw launcher lets you set the layout (portrait) of your desktop screens. Thats at least a little help.
edit
Forgot again... The source for 8500 is available on the huawei download site.
http://www.huaweidevice.com/worldwi...d=list&flay=software&directoryId=20&treeId=0#
/edit
I flashed this rom, had alot of trouble with phone connection and such
did a nand backup using recovery-RA-pulsemini-v1.6.2.img reflashed my Boost stock updata.app then restored the nand backup, everything is working great and i have the Boost mobile splash instead of the odd one, didn't fix the gyro though
edit: GPS seems to be working fine, so fixing the gyro or a locked landscape mode is the only bug left.
I'll be following this thread very closely, with any results I get I'll be sharing them here.
I can't seem to get USB debug to work, it's either a CD emulator with the Huawei device programs or mounting the SD card. Anyone else having this issue, or is there a workaround?
OK, some progress; I've just rooted using z4root (sideload) and it appears to be working - Just backed up apps and settings with Titanium Backup.
I just downloaded the stock U8300 so now I've got something to fall back on in case of emergency. It's not listed on the Huawei website though.
So now forwards, to Froyo!
Current progress:
Downloaded U8500 Froyo ROM and installed as per instructions above, twice.
Rooted with Z4Root installed from my SD card.
Had trouble trying to get the keyboard settings over; I tried using Ghost Commander to copy it into place with root access without success. Any other options, lugiber?
I'm not really interested in using Android Dev programs, nor buying apps... is it possible to use terminal commands to copy it into place instead?
Still got the sideways screen issue as expected. GPS works, Wifi works, gyro and compass work somewhat (even the original U8300 caused some issues with North to the 'right' of the phone ie 90degrees off).
google root explorer apk download it to your sd card, install it and just remember to mount the file system as rw, theres a button at the top in root explorer then copy it over
Hmmm, no dice.
Clicked 'mount R/W' but still said /system/usr/keychrs directory didn't have permissions, tried editing manually which didn't apply either.
Are there any other similar ROMs (eg CM6 or the like) that may also be closely compatible? i can put up with the keyboard until I get the screen rotate working, and I read somewhere that some has done so... I'll get back if it works.
I just received and email from Huawei saying they have now released the source code for the U8300 on their website!! It's the eclair kernel, I presume; I haven't downloaded it to check yet.
They also have the 'Normal' (presumably generic) Froyo source code there too, if that is useful to anyone.
ginger rom here if u want to try -> http://forum.xda-developers.com/showthread.php?t=1091159
hi
anyone have fix the portrait problem ?
cuz this is really annoying for me...
Thanks
TuoNonno said:
ginger rom here if u want to try -> http://forum.xda-developers.com/showthread.php?t=1091159
Click to expand...
Click to collapse
Hi
is this rom in landscape mode?
Ty
Speed?
Hello,
I am interested too in landscape mode.
But I am more interested in speed: is it faster than stock firmware?
Thanks in advance!
Mario
ICS - Android 4 - Ice Cream Sandwich on U8300
Anyone know if ICS - Android 4 - Ice Cream Sandwich is going to work on our U8300?
Will the trick of using the U8500 rom work, IF it gets the new rom?
does someone stil use this rom?
i want to try it but links don't work...can someone help me?
I was working on a ICS based hoppy rom. Unfortunately I just had a catastrophic screen failure, apparently when my laptop bag fell last night, it landed with enough force to shatter the screen on my nextbook! Oh well. it may be a while before I can work on anything to further the version I was working on.
FYI- Due to work, my time is very limited for working on the next version of Hoppy Rom. I apologize in advance. The company I work for is
setting up new engine test cells in China, and my self and 2 other people are main points of support! again Sorry for anything new taking so long!
DOCHOPPY HAS BEEN SIGHTED (Other than on a DAYZ server...Stay tuned.
Ok I have decided to pass along what I have been working on.
Warning***
This is for the Nextbook 7 premium ONLY!
Known working on Nextbook 7 premium tablets with serial numbers starting:YF1011
DocHoppy Presents!
DocHoppyRom Full On Root v2.0
and
DocHoppy Cramfs Style 3.0
Based off the official update image released by nextbook.
Major thanks to FINLESS BOB!!! GREAT HELPFUL GUY!
PRESENTING DOC HOPPY ROM
CRAMFS STYLE 3.0
AND
FULL ON ROOT v2.0
Disclaimer: I am not responsible for Bricked Tablets. This is known to work on tablet with SN starting with YF1011, and some YF1211.
First you will need to decide which version of the Rom you are going to load. The CRAMFS Style version has SU but you CANNOT write to the /system directory. This is a good all around Rom for those who may need SU but do not need to write to /system.
Full On Root is just that, you have full read write to the /system and can customize the Rom to your hreats content.
HOW TO INSTALL:
TO FLASH CRAMFS STYLE 3.0 Put the UPDATE.IMG file from the Cramfstyle Folder onto your SD card, while tablet is on and follow the on screen instructions.
After running the self extracting Zip file you will have a directory containing the following folders and files.
Drivers (folder)
CramfsStyle(folder)
FullonRoot(folder)
Log(folder)
Language(folder)
Readmefirst.txt
Rkusb.log
RkusbComm.dll
Setting.ini
RK29update.exe
TO FLASH CRAMFS STYLE 3.0 Put the UPDATE.IMG file from the Cramfstyle Folder onto your SD card, while tablet is on and follow the on screen instructions.
To flash Full On ROOT, Plug your nextbook into your PC via usb cable. Turn your nextbook over and with a safety pin or something of similar size, press and hold the reset button for 2 to 3 seconds.
Run the RK29update.exe
Select your Rom files via the boxes containing the .... And navigate to the correct directory for the rom you want to install.
Insert eache file in order according to the update tool.
Clear IDB. (this is like a lowlevel format for the Rom tool:
After the Tool says OK. Select Run. This will begin to load the Rom onto your tablet. It will go through loading and then checking the Rom install.
After the Rom loads and the tool comes back with an OK, patiently wait for the tablet to reboot, and load the new ROM. If the tablet is still connected to the pc via USB when the rom boots it will show the screen allowing you to select weather or not to turn on USB storage. Press the home key and you will be given a choice of Golauncher or Rklauncher. (go lock is a screen lock program.)
Enjoy the Rom!
Disclaimer: I am not responsible for Bricked Tablets. This is known to work on tablet with SN starting with YF1011, and some YF1211.
Features for both Roms:
Complete and correctly working market. It now correctly associates the tablet to your gmail account allowing purchases from market.
Launcher 3.0 as well as Go launcher ex. Launcher 3.0 was pulled from an rk2918 firmware3.0 update and put into this rom.
Google Calendar is now back and working correctly.
Original Email is back and working correctly.
Included Kindle App
Included Estrongs file explorer.
Both have SU though the Cramfs version cannot write to SW.
Removed Apps Added in last release and return to more of a original rom state.
Rom is pretty clean. And seems speedy.
Cramfs Style 3.0 Rom has 200mb internal Ram +/-
Full On Root 2.0 has 894MB of Free Internal Ram.
Cheers!
DocHoppy
www.freaktab.com
Keep in mind this is the first version of this ROM. There will be updates and changes made.
FUTURE CHANGES:
Custom Theme Changes.
More Tweaks to the system.
Long Term Wants:
Power Menu change to include recovery boot.
Power Menu change to include restart.
This is a work in progress.
Known working on Nextbook 7 premium tablets with serial numbers starting:YF1011
Linked here for image.
Non Add Showing Link.
DocHoppyFullOnRoot2.0
New Cramfs style Rom is still Available Here.
DocHoppyCramfsstyle3.0
To install DocHoppyRomv3.0, rename .img file to update.img, download update.img file, copy to SD card, and follow the prompt.
DocHoppyCramfsstyle3.0
Enjoy.
Disclaimer:
Not responsible for bricked tablets.
Enjoy!
Also visit www.freaktab.com
So freaking sweet, great work on RW!
I used Wendal's tool to decompress the cramfs file system.
As for the /system, Because the device uses cramfs, and based on everything I have read, using Wendal's tool to decompress the file system, make the changes, and compress is the only way I can see to be able to
customize the rom for the device. The image is rooted, but after the update.img is compressed, the /system file remains read only. I tested this using root explorer, but anything requiring su works fine. But all hope may not be lost, I was reading on a chumby forum someone suggested using mkfs.jffs to make it writable, but further down it notes that you would need to change the kernel (easy enough to recompile I think), to utilize a different file system. The boot loader would also need to be modified, something I am not ready to try and tackle just yet, I think I would be bricking my nextbook pretty quickly.
It is a start and I am actually learning a lot as I go.
Any thoughts or suggestions are welcome.
I am definitely a long time user / cyanogenmod / aosp fan, but as far as ripping open .img files its definitely new territory, I tried to find an internal SD card like the nook has, to maybe dump it, but I cannot find such a beast. Any progress you make is awesome. So do things like root explorer work, just not on /system due to cramfs?
Correct, root explorer does work, but due to cramfs, it does not allow you to toggle to rw from ro on the /system.
Working on taking apart apk's and customizing and rebuilding and resigning next.
just flashed this rom and it works great!
How would I go about doing a custom boot animation or image?
... even if it means flashing a new rom from clean?
This is great. Thanks. The only question I have is why do I see so few items in Market? Does it have anyhting to do with compatability?
Calendar & Sync Access
First, thank you for your work.
Before I update by Next7P, have you included Google Calendar and Sync access in this update?
I use MyPhoneExplorer and will need calendar sync to work so I can fully use for business.
Thanks.
There is another method to get Google Market on the Next7P, I am a new user so I can not post the link, but google , forums Whirlpool net au archive 1756859
, very easy and works great, but cannot get sync to work.
Dan,
Thanks for the responses!
sgtfoo : You can use Wendal's rk29xx tool to take a copy of my rom image, or the original update downloadable from nextbookusa.com, and
unpack it. You then have access to the system directory in an editable format. you can go into the system folder /system/media and replace the bootanimation.zip file with another one. Just be sure the image format is 480x 800 and that the zip file has 0% compression ratio. After you make the changes, just repack .img file via Wendal's tool and reflash.
dodoclub : Not sure why. I have a full market. You might try clearing the data and cache for the market. My market shows pretty full, I.E. I got 31050 entries when I searched for facebook in the market.
Danno65: Actually that is something I have been working on. I can get my google calendar to sync, currently I am using a calendar from the market called Jorte, which works great, how ever, googles actual calendar.apk closes unexpectedly, I am thinking it is just a version problem with the calendar, but haven't had a lot of time to follow up on it.
FYI here is the link to Wendal's tool, which makes it much easier to work on the update.img file.
https://docs.google.com/leaf?id=0B8hUXYDeoy_hNTc1YTVkYTMtNTNjZS00YjI2LTgyNDYtYjRjZjFmODdiZTQ1&pli=1
Cheers!
If you have any request or questions please feel free to ask, I will help anyway I can.
Thanks Dochoppy
Got one of these tablets for Christmass to replace an old broken tablet I use for work.
Google hosts our work email, so I still need to get Contacts and Appointments going, but I maybe able to side load them.
Noticed build.prop still has ro.secure=1. This prevents adb from having root access??
Calendar & Sync Access
DocHoppy,
I came across a post where the "Calendar.apk" and "CalendarProvider.apk" files must be in the "system/app" directory to work properly, I tried to copy these files to the above directory but found it to be read/only, will wendalls tool have to be used to get access to the directory?
Also, did you get your google calendars on your desktop to sync with Jorte on the Next7P, I tried but no luck.
Thanks
Dan
The updated image file worked great, thanks again
Thank you so much for your work in building a new rom for this thing. I am anxiously awaiting a new filesystem so we can have true root. How do we manage to recompile the kernel for ext4 support and change the /system fs?
Hello, first of all, thanks for your work!
I am having trouble loading this rom. it says there's an invalid image file in my sd card and if I want to delete.
Now, I don't know if my tablet is a never or older version of what you guys have...
Next7p
2.3.1
kernel: 2.6.32.27
build: v2.0.7.....
my serial is also different from alot..it starts with YF0511
any help or tips?
markmatters said:
Hello, first of all, thanks for your work!
I am having trouble loading this rom. it says there's an invalid image file in my sd card and if I want to delete.
Now, I don't know if my tablet is a never or older version of what you guys have...
Next7p
2.3.1
kernel: 2.6.32.27
build: v2.0.7.....
my serial is also different from alot..it starts with YF0511
any help or tips?
Click to expand...
Click to collapse
I would say the serial number would have something to do with it, check on the site for nextbook and see if your serial is in the same *batch* as ours, if the original serial is in a different group, im assuming the hardware may be slightly different? If so, you can always use his method to repack the original with root.
First off I would like to say that I was very pleased when I came across this thread from another one. I haven't flashed this ROM yet, but plan to. Thank you for your work on this as I have been searching the whole internet since I got this thing [4 weeks now] for some sort of custom ROM. It is hard to use this tablet when I have ICS on my Captivate and Vibrant. GB just isn't as cool.
One thing I hope we can work on is root access, so we then can use Titanium Backup. Then we won't have to manually reload everything when new releases come out.
With all that being said, if there is anything I can do to help, I would love to. Like I said, I plan on flashing this probably tomorrow or Tuesday. Thanks again.
For the record, I got titanium backup working fine on this rooted rom. it is capable. You just need to reboot after it restores a backup.
i'm new to android. glad to see rooted rom finally, keep it up!!!
i have a clarification, any improvement in the booting time? my device took 1min30sec (power ON to ready to use, for me, 90sec seem like not fast enough).
Good luck on improving boot time. And besides a tablet is best used when on all the time... try using the suspend state to quickly wake it. We're just starting with the early versions of this rom... give it time to grow.
Sent from my N7p using XDA App
Build.prop editing
Okay so observation:
Our tablet is not recognized as a "tablet" by the Android market, only and android device.
What prop would I have to edit in order to have us recognized as I tablet. I noticed this when:
I finally managed (through some internet tutorial before this rom) get the market working (the first version, not 3.1+). And when I downloaded apps (I'll use Minecraft Pro as an example) I noticed that the way mine looked and the way the tablet version looked via android market photos and Youtube, ours looks like an enlarged phone version rather than a tablet optimized version. What can I edit to fix this?
Flashed this today... so for it works great. Love the new boot animation. Great work and can not wait for future releases!
Sent from my Nextbook Premium 7 (Doc Hoppy's Rom v02) from the XDA app.
---------- Post added at 12:16 PM ---------- Previous post was at 12:03 PM ----------
One thing that would be great on a future release [not sure if it is possible yet with out r/w], would be a bigger data partition for apps. Moving everything large to the SD is ok, just takes longer to boot those apps. A kernel that would allow voltage control app [like CPU Master] to work also. Just a thought!
hey, just testing out a few of the stripped down ICS 4.0.3 roms. theyre really great, but the devs always take out the htc_ime. i really like to have that cause of the language selection.
i know i saw somewhere a .zip to flash it back in, but i cant find it now that i need it! anyone know where it is??
thanks!
I heard that HTC_IME is not compatible with ICS...
It is compatible - im using it with no problems. Even HTC trace works fine.
What you need to do (sorry i cant make a flashable zip)
download the zip from HERE
Extract the zip file
Push the HTC_IME.apk (from app folder) to /system/app (I use ES file explorer) and change permissions to RW-R-R
Then push the libs (from lib folder) to /system/lib and change permission to RW-R-R - there should be 5 in total.
Then reboot. I also wiped cache & Dalvik cache just to be sure.
NOTE: if you are using virtuous inquision the lib files are already present. This is the rom im using and since it is based from the HTC leak, the dev has not removed the libs. So all you need is the HTC_IME.apk into /system/app and then you should be able to select the HTC touch input in the keyboard list.
I hope this helps
Doesn't work. Even after copying all the files to their proper folders, ensuring permissions are correct, and wiping cache and dalvik... It still force closes as soon as Touch Input is selected. Just tried it on CM7.
I'm going to try to investigate this problem and see what I can come up with. I know everybody used to say that Clicker.apk was needed. But if you look at most of the ROMs out there, you'll see that they somehow use the HTC_IME keyboard without having Clicker.apk. So what's missing?
Edit: I feel like I'm going to give myself a headache trying to figure this out. The logcat for the FC said (amongst other things) that there is a ClassNotFoundException for KeyboardSettings. There's also a lot of ActivityThread errors which don't really mean much to me. A Google search revealed that it may be related to the AndroidManifest.xml in the APK file, but unfortunately it's not a standard XML file (try opening it to see what I mean). Not to mention, the APK is obviously fine, because I pulled it right from the ROM.
So basically, we need to somehow figure out what other files are needed by HTC_IME.apk, besides the libraries mentioned already in this thread. I assume that it worked for beady_uk because the ROM he was using already had the rest of the required files without him knowing. I'm going to continue looking to see if I can find more information, but I would definitely appreciate if anybody has any technical input into this situation. I can provide logcat information if needed.
Gamesoul Master said:
Doesn't work. Even after copying all the files to their proper folders, ensuring permissions are correct, and wiping cache and dalvik... It still force closes as soon as Touch Input is selected. Just tried it on CM7.
I'm going to try to investigate this problem and see what I can come up with. I know everybody used to say that Clicker.apk was needed. But if you look at most of the ROMs out there, you'll see that they somehow use the HTC_IME keyboard without having Clicker.apk. So what's missing?
Edit: I feel like I'm going to give myself a headache trying to figure this out. The logcat for the FC said (amongst other things) that there is a ClassNotFoundException for KeyboardSettings. There's also a lot of ActivityThread errors which don't really mean much to me. A Google search revealed that it may be related to the AndroidManifest.xml in the APK file, but unfortunately it's not a standard XML file (try opening it to see what I mean). Not to mention, the APK is obviously fine, because I pulled it right from the ROM.
So basically, we need to somehow figure out what other files are needed by HTC_IME.apk, besides the libraries mentioned already in this thread. I assume that it worked for beady_uk because the ROM he was using already had the rest of the required files without him knowing. I'm going to continue looking to see if I can find more information, but I would definitely appreciate if anybody has any technical input into this situation. I can provide logcat information if needed.
Click to expand...
Click to collapse
I believe that you have mis-read the 1st post.
The OP asked how to re-add the HTC_IME to a stripped down rom that the dev had removed.
This is what i have done and it worked - possibly because the roms are sense-based framework.
You have tried to install this on CM7 with is CM based framework so i think you will need more 'files' but that is beyond my knowledge.
Sorry i cant help further
You are correct. I was in a deep search for anything revolving around installing it, so I missed that part. I saw your post (which is the only place I've seen anybody mention installing those lib files), and I guess that caused further oversight on my part.
I do imagine this may not work on all the stripped down ROMs though, if any of the cooks stripped their ROMs like I stripped my old Win98 PC that had a 1GB hard drive in it... that is to say, remove every possible file that wouldn't cause stability issues