Hi,
I created a custom Phone.apk, I changed a bit the behavior, the Dialpad etc.etc so this works great, I compiled it against the Platform and it works on the Emulator.
But now I'm trying to put it on the Wildfire (I did an adb pull from the Emulator) and I've now the Phone.apk, I tried to put it with adb rm and then adb push.
So the Problem is not the installation, the Problem is that I can't get it to work.... on the Wildfire...what's wrong?
Any Ideas would be highly appreciated
Thanks
Does really no-one has clue? In which Direction should I go? What can I try?
Please help-me also if I've not 1000 Posts :-(
I've no logged with adb what happens on the Device, the following Error I get, but this make's no sense for me :-(
FATAL EXCEPTION: main
E/AndroidRuntime( 413): android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.CALL_PRIVILEGED dat=tel:123 flg=0x10000000 }
Any Ideas?
I tried now to flash the Phone.apk with several strategies...
-> update.zip
-> adb & cat
-> custom Rom (cooked)
But i really don't now why it fails...omg...
Upload the file and I will try and install it.
Thanks already, I will do it, but maybe I've found the Error...
I now recompiled the Phone.apk...
And tried it with adb install and terminal was saying that I've an OLD SDK...
Failure [INSTALL_FAILED_OLDER_SDK]
So, on the Device there's running Froyo...so it can't be OLD?
But when I'm compiling it, I'm doing a source envsetup.sh and then a lunch 1.
Could it be that I've to compile it some how different???
Thanks for EVERY reply!
Update:
I'm building with this config:
PLATFORM_VERSION_CODENAME=AOSP
PLATFORM_VERSION=AOSP
TARGET_PRODUCT=generic
TARGET_BUILD_VARIANT=user
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
HOST_ARCH=x86
HOST_OS=darwin
HOST_BUILD_TYPE=release
BUILD_ID=OPENMASTER
So I really don't now why I'm getting the OLDER_SDK message...I was looking in the make files and there's the SDK 8....
So I've uploaded it, maybe someone could help me to go a step further
link to Phone.apk
Problem solved...I updated the use-sdk Version in the AndroidManifest.xml of the Phone app.
Can be closed
link dead. do you have any screenshot of your new phone.apk, what do you change? when you say behavior
It's changed relatively static for my Phone Number and my Voicemail Number...so it isn't handy for others...but I will keep up my Work and try several things and If I've something to give to the XDA-Users I will do it.
Thanks for you interest
Related
Update 8-5-09 12:13am est
I've started a new thread @ http://forum.xda-developers.com/showthread.php?t=544906 this should avoid a lot of confusion since this thread contains a lot of old information about previous builds. Some of the information contained here does apply but read carefully because most of it is old information. If your coming here and your not using a vogue then your questions most likely won't get answered. Right now this works on most vogues and kaisers. I do not know if this works on any other device other than those and I am not going to be porting it over to anything else. If you want to try I suggest you ask in other forums specific to your phone. Before you download anything read the tutorial on the new thread or at http://code.google.com/p/vogue-hero/ follow the directions. If you have general questions related to android on the vogue then post them in the android help desk thread.
The new full build I've been testing the past couple days has been holding up pretty good. Sense UI, GPS, Market, partial SMS, flash, data all work fine for me. I ran it all day with 4 widgets and animations turned on and had no lag on the home screen. It is back to using vilord's regular initrd.gz and rootfs.img. I'm going to do some minor changes and release it sometime tomorrow. After that I will be done with hero for a while. I'm most likely going to take a look at some of the new donut stuff google has been cooking up. Don't expect this release to be feature complete. It's not. It works for what I do with my phone since I use email and IM and I don't rely on sms. I don't have time to test every part of the build. For example I don't use exchange or active sync. If you don't see your city in the weather app or widget then use google maps and turn on gps. Stand outside in a clear area for around 5min until it finds your location. Then switch back to the weather app and tap on my location it should pick up your location and city and give you the option of adding it. This worked for me today. I've sent sms and the person received it even though it said it failed to send. They replied back and I didn't receive the reply this is already a know problem. I've made and received several phone calls and haven't had a problem. I've used market to download apps it works. If you need sms and want a everyday android I suggest you take a look at vilord's Ion builds or mssmision's themed Ion builds or his hero-lite without sense ui. While I use my builds and they work fine for me it's really only a proof of concept and shouldn't be relied on if you need to receive important calls or messages.
Update 8-4-09 7:53am
I'm testing a new build right now. It has all the widgets and apps. The speed is like the current build posted at the site. I'm going to test it for a day or two to see if there are any major bugs. If all goes good I will put out a release. Thanks for testing and thanks to mssmision and vilord for all their help.
Update 8-4-09 3:28am
This isn't a Sense UI theme. This is the real thing. It is a minimal build with some apps and widgets removed to improve speed and stability. It won't void your warranty as nothing is flashed and nothing is permanent. It runs android from your sdcard and only uses the devices memory and doesn't touch devices main storage other than the sdcard. When you boot back into WinMo everything is just the same as it was before. The files featured at the google code site are the latest and most stable. If you want to ask questions or have problems be specific. I'm not going to be following this thread that much as there are users out there that are already experienced enough to take care of the questions for new users. I'll put out a new build sometime in the future to merge back with vilords original initrd.gz and rootfs. It will most likely include some missing widgets and apps that people have been asking for. I hope you enjoy this build as much as I do. Thanks for testing.
Update 8-02-09 8:01pm est
I've uploaded a new Hero build. It uses the new initrd.gz with a modified rootfs.img. The original rootfs.img can be found @ http://code.google.com/p/vogue-android. The Orange logo has been removed and it's sporting the wallpaper from my full build. No widgets loaded up on initial startup except for two toggle switches for Mobile and GPS. It's really fast. Initial startup without a data.img should take less than 5 min. The zip contains everything you need except zImage. Clear out the root of your sdcard. Download Hero-8-2-09.zip and zImage. Extract Hero-8-2-09.zip to the root of your sdcard. Rename system-8-02-09.img to system.img. Copy zImage to the root of your sdcard. Do not use an existing data.img. A new one will be created on first boot. Edit your default.txt to work with your vogue keeping the lcd density at 160 and the resolution at 320x480. If you don't know how to edit your default.txt then read the file it has examples. If your still not sure to then ask around in the vogue android threads. Execute haret and tap run. Wait a couple minutes you will see the HTC/Android boot logo and hear the chime. Wait a little bit more and the setup screen will come up. When the HTC keyboard comes up press the gear icon to the left of the space bar. Tap on Text input. Scroll down and tap on Calibration tool. The Calibration tool will walk you through the rest of the way. Push back (volume rocker up) to get back to the setup screen and continue the setup. I suggest you set up a google account to use market. After setup you are taken to a minimal home screen with two toggle widgets for GPS and Mobile. I suggest you download another messing app like chompSMS or handsentsms if you want sms because the HTC messenger is not 100% it will send sms but it will tell you it failed even though it really went through. I also changed the default home page in the browser to google.com so you don't have to sit and wait for HTC.com to load up. Hope everyone enjoys this as much as I do.
Direct Link to zip: http://vogue-hero.googlecode.com/files/Hero-8-2-09.zip
Direct Link to zImage: http://vogue-hero.googlecode.com/files/zImage
Project Home: http://code.google.com/p/vogue-hero/
Thanks to dzo vilord and mssmision for all their great work.
Internet enabled, I'm assuming?
working on it.
When modem runs it isn't getting the right permissions it seems. What did you change? Have you compared to the cupcake build on the other google code page?
No I haven't. pppd needs to be run as root and i think this might be the problem. As for compairing to the cupcake build there are no parts of it in there. This is a port of a sapphire rom with a modified initrd from the ion build. I'll check and see later what the diffs are between the builds as far as getting pppd to work. Anyway here is the output from the adb shell when setupmodem.sh is executed.
# ./setupmodem.sh
grep: /proc/cmdline: Permission denied
./setupmodem.sh: line 17: can't create /smodem/setupmodem.pid: Permission denied
Initialising Modem:
===================
./setupmodem.sh: line 24: can't create /smodem/ppp.log: Permission denied
grep: /proc/cmdline: Permission denied
grep: /proc/cmdline: Permission denied
grep: /proc/cmdline: Permission denied
Username=
Password=
APN=
./setupmodem.sh: line 37: can't create /smodem/ppp.log: Permission denied
./setupmodem.sh: line 77: can't create /smodem/working: Permission denied
./setupmodem.sh: line 77: can't create /smodem/ppp.log: Permission denied
/bin/pppd: must be root to run /bin/pppd, since it is not setuid-root
./setupmodem.sh: line 77: can't create /smodem/ppp.log: Permission denied
./setupmodem.sh: line 77: can't create /smodem/ppp.log: Permission denied
rm: cannot remove '/smodem/working': No such file or directory
^C./setupmodem.sh: line 77: can't open /smodem/control: Interrupted system call
I'm going to sleep. I'll start back at it tomorrow.
Interesting, thanks for the release. I like some of the new features that hero has, but don't like what they did with the appdrawer bar. I liked the swipe up motion and it was a big target. I'm just happy I finally got to play around with hero a little, thanks again for all the work.
zenulator said:
No I haven't. pppd needs to be run as root and i think this might be the problem. As for compairing to the cupcake build there are no parts of it in there. This is a port of a sapphire rom with a modified initrd from the ion build. I'll check and see later what the diffs are between the builds as far as getting pppd to work. Anyway here is the output from the adb shell when setupmodem.sh is executed.
# ./setupmodem.sh
grep: /proc/cmdline: Permission denied
./setupmodem.sh: line 17: can't create /smodem/setupmodem.pid: Permission denied
Initialising Modem:
===================
./setupmodem.sh: line 24: can't create /smodem/ppp.log: Permission denied
grep: /proc/cmdline: Permission denied
grep: /proc/cmdline: Permission denied
grep: /proc/cmdline: Permission denied
Username=
Password=
APN=
./setupmodem.sh: line 37: can't create /smodem/ppp.log: Permission denied
./setupmodem.sh: line 77: can't create /smodem/working: Permission denied
./setupmodem.sh: line 77: can't create /smodem/ppp.log: Permission denied
/bin/pppd: must be root to run /bin/pppd, since it is not setuid-root
./setupmodem.sh: line 77: can't create /smodem/ppp.log: Permission denied
./setupmodem.sh: line 77: can't create /smodem/ppp.log: Permission denied
rm: cannot remove '/smodem/working': No such file or directory
^C./setupmodem.sh: line 77: can't open /smodem/control: Interrupted system call
I'm going to sleep. I'll start back at it tomorrow.
Click to expand...
Click to collapse
Rather than comparing to the cupcake release, maybe get in touch with mssmison. I've been testing his Hero build for the past 2 days. He's got the network going just fine.
I dunno what kind of feedback you're looking for at this point, but I tried yours, and it hung in the startup wizard. Kept telling me I had no network connection, and I couldn't back out of it to disable the "Auto-sync with Internet" option, or whatever it's called. So I was stuck. I'll try again when you've got the pppd permissions fixed.
Updated Build
I'm testing a new build right now. The problem with pppd is now fixed. I'm going to make sure it will work with a fresh data.img before posting it to the google code site.
does this build have a problem mounting the sdcard
New build up.
The new hero-black build is up at the google code site. No data.img is required. Internet is working now. I'll keep trying to tweak things here and there over the weekend.
sdcard
I haven't had any problem mounting the sdcard or heard of any problems yet.
The version from earlier was missing a lot of widgets and was really slow.
Did you add any widgets back/improve speed?
When you go through the initial boot and set up everything starting from a fresh data image everything is there for me in the new build. The over all initial boot and setup is alot better experience as far as I'm concerned. The only draw back with going this route is that it loads 5 screens full of widgets. The widgets really bog down the system. The max I recomend is maybe 2 widgets at a time until I get the speed and swap sorted out. On my system right now I have a swap file enabled and it's running decient with two widgets and touchflo.
zenulator said:
When you go through the initial boot and set up everything starting from a fresh data image everything is there for me in the new build. The over all initial boot and setup is alot better experience as far as I'm concerned. The only draw back with going this route is that it loads 5 screens full of widgets. The widgets really bog down the system. The max I recomend is maybe 2 widgets at a time until I get the speed and swap sorted out. On my system right now I have a swap file enabled and it's running decient with two widgets and touchflo.
Click to expand...
Click to collapse
yeah I haven't noticed if it used a swap file. that should give it a moderate speed boost.
derekwilkinson said:
yeah I haven't noticed if it used a swap file. that should give it a moderate speed boost.
Click to expand...
Click to collapse
im running zenulator's system with mmsmisons swapfile, it doesnt seem to be too fast
I'm working on another build right now that has more optimizations. Can't really expect much from a build that didn't exist 24 hours ago.
zenulator said:
I'm working on another build right now that has more optimizations. Can't really expect much from a build that didn't exist 24 hours ago.
Click to expand...
Click to collapse
oh no im not trying to put you down or anything im just stating the facts as of now. thanks for your hard work!!!!
It's all good. Just sayin it's only going to get better.
Umm.... anyone else having a problem where the keyboard doesn't appear during the initial setup wizard?
EDIT: Crap, nevermind. I hit submit on this post, and then the KB popped up on my phone. :S Took like 3 or 4 minutes though.
zenulator said:
This is a port from the sapphire rom hero-black.
Click to expand...
Click to collapse
So wait, this is a Hero ROM, or a Sapphire ROM that has TouchFLO included in it?
Would it be possible to set the phone up so that on first boot there are no HTC widgets loaded? After finishing the first-run wizard, it was about 15 minutes before I could do anything with the phone, and even that wasn't easy. As I've (slowly) been able to remove widgets, it's become more usable. It'd be nice if there were no widgets to start, and people could add them as they please.
Hey guys I'm a first time poster here, and I am really hoping someone can help me. I am trying to build a ROM from CyanogenMOD source for the Moto Droid 1. whenever I run the "make" command this is what I get:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=2.2.1
TARGET_PRODUCT=generic
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=FRG83
============================================
Checking build tools versions...
************************************************************
You are attempting to build with the incorrect version
of javac.
Your version is: javac 1.5.0_19.
The correct version is: 1.6.
Please follow the machine setup instructions at
************************************************************
build/core/main.mk:130: *** stop. Stop.
Click to expand...
Click to collapse
Is there something else I should try? I'm a new Dev in training and I'm at my wits end if someone could tell me how to update javac that would be greatly appreciated. And I am also having trouble getting ADB to work when I try to extract the Sholes files from my phone. Any help on that would help too thanks. By the way I am running Ubuntu 10.10, and Cyanogen 6.1RC3
Javac Problem
Android build system is picky about Java versions. I would download and install official JDK 1.6
Before compiling make sure that your PATH points to the newly installed Java 1.6. Also make sure your ANDROID_JAVA_HOME and JAVA_HOME point to your newly installed JDK 1.6
Hi, everyone
I'm now working on a program about flashing roms on PC, and I'd like to call it "Rom Manager" on desktop But now, i get one problem. It's that, how to get the version number of ClockWorkMod Recovery with PC in cmd lines
Any help please?
Thx in advance!
One way I've spotted is to look inside
/data/data/com.koushikdutta.rommanager/databases/settings.db
It's the standard SQLite format:
Code:
0000fa0: 2203 033d 1b63 7572 7265 6e74 5f72 6563 "..=.current_rec
0000fb0: 6f76 6572 795f 7665 7273 696f 6e32 2e35 overy_version[B]2.5[/B]
0000fc0: 2e30 2e37 1602 032b 1569 735f 636c 6f63 .[B]0.7.[/B]..+.is_cloc
0000fd0: 6b77 6f72 6b6d 6f64 7472 7565 2201 0331 kworkmodtrue"..1
You can see 2.5.0.7 (which is my recovery version) in there. I haven't time to debug it further, so I thought I would perhaps offer a way out for you.
Edit:
Probably easier on the eye:
$ sqlite3 settings.db
SQLite version 3.6.22
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> select * from settings where key='current_recovery_version';
current_recovery_version|2.5.0.7
sqlite>
Thank you! Now i can find the recovery version number in the database of android rom manager app. But i think there must be a lot of my users don't have a rom manager app in their phone, and then i can't get it with the database. So, is there another way to get it without the android rom manager app?
Thx anyway!
You'll have to test this if this is true without the app.:
Code:
# cat /sdcard/clockworkmod/.settings
{"paypal_transaction_id":"","is_clockworkmod":true,"readonly_recovery":true,"current_recovery_version":"[B]2.5.0.7[/B]","recovery_timestamp":1284679575253,"detected_device":"bravo","reboot_recovery":""}
My God!! It works!!
I'm sorry that i almost forget this thread, but now it gives me a big surprise!
Thanks Man, you're great!!
Hi guys.
I'm getting problems when I try a make for my aosp build (for my p3113)
I followed this guide: http://forum.xda-developers.com/showthread.php?t=1762641
and I git clone git://github.com/AOKP/android_device_samsung_espressowifi.git -b jb espressowifi
then ./extract-files.sh
when I'm extracting, I get some errors like
remote object '/system/lib/hw/lights.omap4.so' does not exist
341 KB/s (31320 bytes in 0.089s)
remote object '/system/media/battery_batteryerror.qmg' does not exist
remote object '/system/media/battery_charging_0.qmg' does not exist
remote object '/system/media/battery_charging_5.qmg' does not exist
Is this normal?
Btw.. I continue with . build/envsetup.sh which is done successfully
and a lunch done successfully too..
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.2
TARGET_PRODUCT=full_espressowifi
TARGET_BUILD_VARIANT=userdebug
...
HOST_BUILD_TYPE=release
BUILD_ID=JZO54K
OUT_DIR=out
Finally I try a make -j4 otapackage and I got way too much errors and it stops
Can i have help please?
rainfalls said:
Hi guys.
I'm getting problems when I try a make for my aosp build (for my p3113)
I followed this guide: http://forum.xda-developers.com/showthread.php?t=1762641
and I git clone git://github.com/AOKP/android_device_samsung_espressowifi.git -b jb espressowifi
then ./extract-files.sh
when I'm extracting, I get some errors like
remote object '/system/lib/hw/lights.omap4.so' does not exist
341 KB/s (31320 bytes in 0.089s)
remote object '/system/media/battery_batteryerror.qmg' does not exist
remote object '/system/media/battery_charging_0.qmg' does not exist
remote object '/system/media/battery_charging_5.qmg' does not exist
Is this normal?
Btw.. I continue with . build/envsetup.sh which is done successfully
and a lunch done successfully too..
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.2
TARGET_PRODUCT=full_espressowifi
TARGET_BUILD_VARIANT=userdebug
...
HOST_BUILD_TYPE=release
BUILD_ID=JZO54K
OUT_DIR=out
Finally I try a make -j4 otapackage and I got way too much errors and it stops
Can i have help please?
Click to expand...
Click to collapse
To build it proper you need...
https://github.com/AOKP/android_device_samsung_p3100
https://github.com/AOKP/android_device_samsung_p3113
And:
https://github.com/AOKP/vendor_samsung
for the p31xx blobs
That should get you going.
cmenard said:
To build it proper you need...
github.com/AOKP/android_device_samsung_p3100
github.com/AOKP/android_device_samsung_p3113
And:
github.com/AOKP/vendor_samsung
for the p31xx blobs
That should get you going.
Click to expand...
Click to collapse
Thanks for the reply. So if I understand correctly, the samsung_espressowifi isn't the right one I need? so i went into device/samsung/ then I git clone p3100 and p3113 there am I right?
I was wondering where do I have to clone the vendor? directly into the samsung folder?
Thanks again for your help! Greatly appreciated
rainfalls said:
Thanks for the reply. So if I understand correctly, the samsung_espressowifi isn't the right one I need? so i went into device/samsung/ then I git clone p3100 and p3113 there am I right?
I was wondering where do I have to clone the vendor? directly into the samsung folder?
Thanks again for your help! Greatly appreciated
Click to expand...
Click to collapse
Yup. Just use the links I provided and you should be able to build just fine.
cmenard said:
Yup. Just use the links I provided and you should be able to build just fine.
Click to expand...
Click to collapse
Ok. I've started from scratch, deleted all the things in the samsung folders. i git clone p3113, p3100 and vendor. So now I have p3113,p3100 and samsung_vendor folders. Do I have to pull the p31xx folders from vendor and paste it directly into the samsung one?
when I do a ./extract-files.sh, i don't have any error until there ->
180 KB/s (14268 bytes in 0.077s)
453 KB/s (45380 bytes in 0.097s)
remote object '/system/lib/libsec-ril.so' does not exist
120 KB/s (9620 bytes in 0.077s)
172 KB/s (13768 bytes in 0.077s)
My p3113 is connected with usb debugging and appears correctly in adb devices.
Plus, nothing as been added into the p3113 folders at the end of the extract-files. At the end of the extract, should a vendorsetup.sh file supposed to be created?
Sorry but I'm a noob looking to learn something
thanks
EDIT: ok I found what was wrong with the vendor.. it's not going into /device/samsung folder but /vendor/samsung/p31xx right? still having the libsec-ril issue tho..
Do you have any hint cmenard?
You have two problems. One, you need to manually add a vendorsetup.sh file to the p3113 folder. Copy one from one of the other devices, and change its only line to read something like ADD_LUNCH_COMBO_p3113. Also, if extract-files.sh gave any errors, it didn't work. I've never had any luck with the default file, I always change the two lines that have adb pull to read cp /<romlocation>/system $file and extract a JB ROM to a folder on the disk.
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
You have two problems. One, you need to manually add a vendorsetup.sh file to the p3113 folder. Copy one from one of the other devices, and change its only line to read something like ADD_LUNCH_COMBO_p3113. Also, if extract-files.sh gave any errors, it didn't work. I've never had any luck with the default file, I always change the two lines that have adb pull to read cp /<romlocation>/system $file and extract a JB ROM to a folder on the disk.
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
Yeah I already added the vendor setup file manually. I'll resync my jb tonight maybe something went wrong. I'll have to figure out the extract file problem too. All this when I'll get back from work lol
Why are you using extract-files.sh? The reason to use it is if you don't have the vendor files for the device already downloaded, and if you look at the vendor_samsung folder, it has all the stuff you need already. All you need to do is specify the device and build after you have the source downloaded.
imnuts said:
Why are you using extract-files.sh? The reason to use it is if you don't have the vendor files for the device already downloaded, and if you look at the vendor_samsung folder, it has all the stuff you need already. All you need to do is specify the device and build after you have the source downloaded.
Click to expand...
Click to collapse
I was using it because I've followed the guide step by step but I was asking the same question myself. I'll retry again as soon as I go back home
I'm getting a bit farther now. Not compiling yet but.. will do soon.. when I'm trying to do a make -j4 otapackage, I'm getting a series and I wrote them in pastebin
http://pastebin.com/f3UP50ku
I'm using:
[email protected]:~/android$ java -version
java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode)
I'm kinda lost
thanks for your help!
You have java virtual machine, but not java development kit. It's a bit difficult to find for Linux, but you can get it from http://www.cyberciti.biz/faq/howto-ubuntu-linux-install-configure-jdk-jre/
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
You have java virtual machine, but not java development kit. It's a bit difficult to find for Linux, but you can get it from http://www.cyberciti.biz/faq/howto-ubuntu-linux-install-configure-jdk-jre/
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
Well.. this is what I've done so far
1. I downloaded java there http://www.oracle.com/technetwork/java/javase/downloads/jdk6-downloads-1637591.html (jdk-6u34-linux-x64.bin)
2. Went to terminal chmod +x jdk-6u34-linux-x64.bin
3. Then /.jdk-6u34-linux-x64.bin == install successfull
4. sudo update-alternatives --config java -> to choose the last jdk I've installed (by default, OpenJDK is installed with ubuntu instead of java jdk)
still having the same output with java -version
still having same issues
I got the same problem too when I'm trying to compile.
pastebin.co m/wcSZq6wq
it stops there and nothing.
I'm using p3113, p3110 and p3100 folder from /github.co m/AOKP/
Any idea someone?
Thanks
Finally I've been able to compile it through the end. Now time for debugging... I got a bootloop (surprising eh!?)
http ://pastebin.co m/e6STwe0E
Any help will be appreciated!
thanks!
EDIT: I've uploaded my work so far right there:
https ://docs.google.c om/file/d/0B6GzemNaw2dRY3BTT0tPWDdKYnM/edit
REMEMBER it's bootloading!
Nobody have a clue?
I have a Nook Simple Touch, BNRV300, and I have successfully modified uRamdisk to gain root shell access with ADB over USB (Thanks Renate!). I am currently on firmware version 1.2.1.
I know this may seem like heresy to some here, but I really do not want or need to root my NST and add a number of apps I won't use anyway. I have a fully rooted Nexus 7 for that sort of thing.
All I would like to be able to do is turn off the need to swipe to unlock when returning from sleep, and modify the text on the screensaver overlay.
I have discovered, by the way, that sqlite3 does not seem to be available on this NST, as when trying to use it via ADB shell, it says "sqlite3: not found".
SO, there we are... I would greatly appreciate any assistance offered.
MildBill
P.S. I have tried Nook Manager, and while it did what I wanted, there were many things added that I just have no need for. And, battery drain seemed to double.So, it had to go.
Regarding SQLite3.
Since the guts of it (libsqlite.so) is already in the Nook, you only need the command line executable (sqlite3).
It's here: http://forum.xda-developers.com/showthread.php?p=50958855#post50958855
Unzip it, stick it in /system/bin, chmod 755 it.
Renate NST said:
Regarding SQLite3.
Since the guts of it (libsqlite.so) is already in the Nook, you only need the command line executable (sqlite3).
It's here: http://forum.xda-developers.com/showthread.php?p=50958855#post50958855
Unzip it, stick it in /system/bin, chmod 755 it.
Click to expand...
Click to collapse
Ahh, once again, thank you Renate. Now if I can get some idea on my main questions...
There are no simple questions here. Even the answers are complicated.
Many people have created solutions and packed them into these "manager" things.
I finally got around to doing my own minimal one.
It's packaged up in nook121patch.zip (in the signature).
Code:
C:\>adb pull /system/framework/android.policy.jar
C:\>apktool d android.policy.jar \AP
C:\>mergesmali /v C:\AP\smali C:\Nook121Patch\KeyguardViewMediator.smali
C:\>apktool b C:\AP android.policy.jar
C:\>adb shell stop
C:\>adb mount -o rw,remount /dev/block/mmcblk0p5 /system
C:\>adb push android.policy.jar /system/framework/
C:\>adb shell chmod 644 /system/framework/android.policy.jar
C:\>adb shell reboot
Renate NST said:
There are no simple questions here. Even the answers are complicated.
Many people have created solutions and packed them into these "manager" things.
I finally got around to doing my own minimal one.
It's packaged up in nook121patch.zip (in the signature).
Click to expand...
Click to collapse
Well Renate, I hate to complicate your answer any more than necessary, but...
On the Temblast page that clicking on your signature takes me to, I do see mergesmali, one of the two tools I will need based on the instructions you gave. I do not see nook121patch.zip, nor apktool, however. Where can I find these?
Also, can you tell me something about what this will do for me?
I hate to be such a noob, I have just enough knowledge to be dangerous. Thanks again for all your help, sorry I have to keep asking for more.
MildBill
Well, I wasn't that clear.
mergesmali is in the signature, nook121patch.zip is on the mergesmali project page too.
Apktool is detailed and linked here: http://forum.xda-developers.com/wiki/Apktool
There are many patches in the nook121patch.zip
You can apply them selectively.
.jar is easy, they don't need signing.
.apk is trickier they must be signed.
System .apk is even trickier, they must be signed with the system signature.
The KeyguardViewMediator.smali will make that your Nook just opens with a push of the power button and no swipe.
Renate NST said:
Well, I wasn't that clear.
mergesmali is in the signature, nook121patch.zip is on the mergesmali project page too.
Apktool is detailed and linked here: http://forum.xda-developers.com/wiki/Apktool
Click to expand...
Click to collapse
Ahh! Well, my bad, I should have tried harder. And, yet again, thanks. Nook users owe you much, Renate!
MildBill
Renate NST said:
Code:
C:\>adb pull /system/framework/android.policy.jar
Click to expand...
Click to collapse
OK so far, and (I think) I have apktool properly installed, then realized I also needed to install the Java Development Kit as well to use it, which I managed to do. But, when I try to do
Code:
C:\>apktool d android.policy.jar \AP
I get
Code:
Input file (\AP) was not found or was not readable.
as a response.
So, I guess I need to return to the magic well of your knowledge for further assistance and/or instruction.
To which I can only add...
HELP!
EDIT: By the way, I am using an adb.exe implementation from another root kit I have installed, not the standard installation from the SDK. Is this perhaps part of my problem?
Well, something goofy is going on there.
Type just apktool and get the usage and version.
\AP in this case is the destination directory.
It should not already exist or else you get a warning.
Maybe the input file (the jar) can't be found, but the error message is wrong?
Code:
C:\>apktool
Apktool v1.5.2 - a tool for reengineering Android apk files
Copyright 2010 Ryszard Wi?niewski <[email protected]>
with smali v1.4.1, and baksmali v1.4.1
Code:
C:\>apktool d C:\nook121\system\framework\android.policy.jar \AP
I: Baksmaling...
I: Copying assets and libs...
Code:
C:\>apktool d C:\boguspath \BogusDir
Input file (C:\boguspath) was not found or was not readable.
Renate NST said:
Well, something goofy is going on there.
Type just apktool and get the usage and version.
Click to expand...
Click to collapse
Well, there ya go... I got apktool v2.0.0b9.
I can get 1.5.2, but will it work with Java 7? Oh well, live and learn I guess...
MildBill
Oh, well, then the 2.0 probably uses different args.
"apktool" by itself will tell you the order of arguments.
To run anything on the desktop the Java 7 runtime environment is fine.
To compile an Android application you have to use Java 6.0 SDK.
Renate NST said:
Oh, well, then the 2.0 probably uses different args.
"apktool" by itself will tell you the order of arguments.
To run anything on the desktop the Java 7 runtime environment is fine.
To compile an Android application you have to use Java 6.0 SDK.
Click to expand...
Click to collapse
Well then, since it appears from the changes that 2.0 requires the Java 7 SDK, I guess I'll uninstall it all and get 1.5.2 and Java 6.
I'm running desktop applications:
Code:
C:\>java.exe -version
java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode, sharing)
I'm compiling Android applications with:
Code:
C:\>javac.exe -version
javac 1.6.0_38-ea
apktool runs under the JRE, version 1.7 is fine.
OK, finally got around to completing the instructions as posted, and except for having to add the command 'shell' to the mount statement, everything worked fine. And, it accomplishes exactly what I was after.
Next I may look into trying your library and reader apps.
Thanks again!
MildBill
P.S. You might consider rewriting the readme file included in nook121patch.zip to better describe what each patch does.
The readme is admittedly very old.
That's because I forgot that it's even there!
Each of the individual smali files has comments at the head saying what it does.
I'll make something to compile the individual comments into a single readme.
I can also report, at this point, that unlike an other method I have tried to accomplish this simple task, this one does NOT run thru battery life like it was going out of style.
The next most popular option, NookManager, which uses the NookModManager to do this fix, uses an average of 10% battery life every day, even when in in sleep mode the whole time. Turning the option off (I.E. reinstating the swipe to unlock) again reduces battery drain to a more normal point.
But, the fix by Renate seems to use nomorebattery than the stock reader, whether reading, sleeping, with WiFi on or off. I like it!
Once again, Renate, thank you very much for this, and for all you have done for the Nook community.
MildBill